From de17707be0cc0dacd3a6770696f77d451830a1a0 Mon Sep 17 00:00:00 2001
From: kpsingh <kpsingh@cloudflare.com>
Date: Wed, 27 May 2026 11:11:20 +0530
Subject: [PATCH 1/8] [RealtimeKit]: add realtimekit track recording docs

---
 .../realtimekit/recording-guide/index.mdx     |  13 +-
 .../recording-guide/track-recording.mdx       | 146 ++++++++++++++++++
 2 files changed, 153 insertions(+), 6 deletions(-)
 create mode 100644 src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx

diff --git a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
index fa48c574748d4e8..0818278555efc44 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
@@ -1,7 +1,7 @@
 ---
 pcx_content_type: navigation
 title: Recording
-description: Record audio and video from RealtimeKit meetings using composite recording mode.
+description: Record RealtimeKit meetings as composite recordings or separate participant audio tracks.
 sidebar:
   order: 8
   label: Overview
@@ -11,18 +11,17 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-Learn how RealtimeKit records the audio and video of multiple users in a meeting, as well as interacts with RealtimeKit plugins, in a single file using composite recording mode.
+Learn how RealtimeKit records meetings as a single composite file or as separate participant audio tracks.
 
 Visit the following pages to learn more about recording meetings:
 
 <DirectoryListing />
 
-RealtimeKit records the audio and video of multiple users in a meeting, as well as
-interactions with RealtimeKit plugins, in a single file using composite recording mode.
+RealtimeKit can record the audio and video of multiple users in a meeting, as well as interactions with RealtimeKit plugins, in a single file using composite recording mode. RealtimeKit can also record separate participant audio tracks using track recording.
 
-## How does RealtimeKit recording work?
+## How does composite recording work?
 
-RealtimeKit recordings are powered by anonymous virtual bot users who join your
+Composite recordings are powered by anonymous virtual bot users who join your
 meeting, record it, and then upload it to RealtimeKit's Cloudflare R2 bucket. For video files,
 we currently support the
 [H.264](https://en.wikipedia.org/wiki/Advanced_Video_Coding) and
@@ -60,3 +59,5 @@ A typical workflow for recording a meeting involves the following steps:
 1. Start a recording using the [Start Recording API](/api/resources/realtime_kit/subresources/recordings/methods/start_recordings/) or client side SDK.
 2. Manage the recording using the [Pause, resume, or stop recording API](/api/resources/realtime_kit/subresources/recordings/methods/pause_resume_stop_recording/) or client side SDK.
 3. Fetch the download URL for downloading the recording using the [Fetch details of a recording API](/api/resources/realtime_kit/subresources/recordings/methods/get_one_recording/), webhook, or from the Developer Portal.
+
+For separate participant audio files, refer to [Track recording](/realtime/realtimekit/recording-guide/track-recording/).
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
new file mode 100644
index 000000000000000..de327c04520daca
--- /dev/null
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -0,0 +1,146 @@
+---
+title: Track recording
+description: Record separate audio tracks for selected RealtimeKit participants and download per-participant WebM files.
+pcx_content_type: how-to
+sidebar:
+  order: 9
+products:
+  - realtime
+---
+
+Track recording records each participant's audio as a separate WebM file in RealtimeKit's Cloudflare R2 bucket. Use track recording when you need isolated speaker tracks for post-processing, transcription, compliance workflows, or audio analysis.
+
+Composite recording creates one mixed meeting recording. Track recording creates one file per recorded participant peer.
+
+:::note
+
+Track recording currently supports audio tracks only. Video track recording is in development.
+
+:::
+
+## Availability and limits
+
+Track recording has the following requirements and limits:
+
+| Limit                 | Description                                           |
+| --------------------- | ----------------------------------------------------- |
+| Active meeting        | The meeting must have an active live session.         |
+| Media kind            | Only `audio` layers are recorded.                     |
+| Participant selection | Pass up to `100` values in `user_ids`.                |
+| Storage               | Files are uploaded to the RealtimeKit bucket.         |
+| File retention        | RealtimeKit bucket download URLs expire after 7 days. |
+
+## Start track recording
+
+To start track recording, call `POST /recordings/track` with the meeting ID.
+
+If you omit `layers`, RealtimeKit records all participant audio. You can pass an audio layer to set a file name prefix for generated files.
+
+```bash
+curl --request POST \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a"
+}'
+```
+
+The response includes a recording ID. Use this ID to stop or fetch the recording.
+
+```json
+{
+	"success": true,
+	"data": {
+		"recording": {
+			"id": "fff40c6a-140b-40a9-9499-b23fd7a3868a",
+			"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+			"status": "INVOKED",
+			"type": "TRACK",
+			"output_file_name": "{{file_name_prefix}}_{{user_id}}_{{peer_id}}_{{stream_kind}}_{{media_kind}}_{{date_time}}.webm"
+		}
+	}
+}
+```
+
+## Record selected participants
+
+Pass `user_ids` to record only specific participants. RealtimeKit records current and future participant peers whose `user_id` matches the allowlist.
+
+:::caution
+
+To use selective track recording with `user_ids`, contact your Cloudflare account team or RealtimeKit support.
+
+:::
+
+```json
+{
+	"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+	"user_ids": ["user-123", "user-456"]
+}
+```
+
+## Set file name prefix
+
+Use `file_name_prefix` to prefix every generated track recording file.
+
+```json
+{
+	"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+	"layers": {
+		"default": {
+			"media_kind": "audio",
+			"file_name_prefix": "speaker"
+		}
+	}
+}
+```
+
+If you omit `layers`, RealtimeKit uses `default` as the file name prefix.
+
+## Stop track recording
+
+Use the recording update endpoint to stop a track recording.
+
+```bash
+curl --request PUT \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/<recording_id> \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "action": "stop"
+}'
+```
+
+Track recording also stops when the meeting session ends.
+
+After track recording stops, RealtimeKit uploads the per-participant WebM files and moves the recording to `UPLOADED`.
+
+## Download track files
+
+Track recording uses the same recording status lifecycle as composite recording. To monitor status, refer to [Monitor Recording Status](/realtime/realtimekit/recording-guide/monitor-status/).
+
+When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. The `download_url` field contains the recorded WebM files for participant peers.
+
+```json
+{
+	"download_url": [
+		{
+			"layer_name": "default",
+			"download_urls": {
+				"speaker_user-123_peer-456_peer_audio_1760000000000.webm": {
+					"download_url": "https://example.com/presigned-url"
+				}
+			}
+		}
+	]
+}
+```
+
+File names use this format:
+
+```txt
+{{file_name_prefix}}_{{user_id}}_{{peer_id}}_{{stream_kind}}_{{media_kind}}_{{date_time}}.webm
+```
+
+The `date_time` value is the Unix timestamp in milliseconds when the file was generated.

From a277e97a5321cde84a73a09d5ad2bde14933c5a3 Mon Sep 17 00:00:00 2001
From: Kunwar Pratap Singh <ksingh2001.dev@gmail.com>
Date: Wed, 27 May 2026 23:36:59 +0530
Subject: [PATCH 2/8] Update
 src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx

Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
---
 .../realtime/realtimekit/recording-guide/track-recording.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
index de327c04520daca..50d601987d14693 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -28,7 +28,7 @@ Track recording has the following requirements and limits:
 | Media kind            | Only `audio` layers are recorded.                     |
 | Participant selection | Pass up to `100` values in `user_ids`.                |
 | Storage               | Files are uploaded to the RealtimeKit bucket.         |
-| File retention        | RealtimeKit bucket download URLs expire after 7 days. |
+| File retention        | RealtimeKit bucket download URLs expire after seven days. |
 
 ## Start track recording
 

From b11ab7c8ad455913644e8b2c0f3dff0125b1a955 Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 06:07:18 +0000
Subject: [PATCH 3/8] Applied 10 edits + changelog entry, validated

Co-authored-by: korinne <korinne@users.noreply.github.com>
---
 .agents/references/procedures.md              |   20 +-
 .agents/skills/dependabot-review/SKILL.md     |   18 +-
 .agents/skills/docs-review/SKILL.md           |   26 +-
 .agents/skills/eli5/SKILL.md                  |   45 +-
 .../internal-dns/index.eli5.mdx               |    1 +
 .../eli5/references/EXAMPLES_REFERENCE.md     |  517 ++++----
 .../eli5/references/content-type-guide.md     |  105 +-
 .../skills/eli5/references/pattern-library.md |  202 +--
 .github/review-template.md                    |    3 +-
 .opencode/command/styleguide.md               |    1 +
 .windsurf/rules/general-rules.md              |    2 +-
 CONTRIBUTING.md                               |    3 +-
 MIGRATION.md                                  |    4 +-
 src/components/AutoconfigDiagram.astro        |  157 ++-
 src/components/ComponentUsage.astro           |    3 +-
 src/components/FeatureTable.astro             |   44 +-
 src/components/LayerCard.astro                |    8 +-
 src/components/LlmsTxtDirective.astro         |    6 +-
 src/components/PagesBuildPresetsTable.astro   |   15 +-
 src/components/ProductReleaseNotes.astro      |    7 +-
 src/components/R2LocalUploadsdiagram.astro    |  404 ++++--
 src/components/WranglerCommand.astro          |    2 +-
 src/components/WranglerConfig.astro           |    4 +-
 src/components/WranglerNamespace.astro        |    2 +-
 .../agent-setup/AgentComparison.astro         |   12 +-
 src/components/agent-setup/AgentHeader.astro  |    4 +-
 src/components/agent-setup/AgentPrimer.astro  |    6 +-
 .../agent-setup/BuildAgentsCallout.astro      |    4 +-
 .../agent-setup/CloudflareToolsBanner.astro   |   35 +-
 .../agent-setup/PlatformAccessSection.astro   |    7 +-
 src/components/ai-gateway/code-examples.astro |  329 +++--
 src/components/changelog/Pagination.astro     |    7 +-
 src/components/models/CopyableCode.astro      |   11 +-
 src/components/models/ModelDetailPage.astro   |  220 +++-
 src/components/models/SchemaDisplay.astro     |   16 +-
 src/components/models/code/DeepgramFlux.astro |   15 +-
 .../OpenAIResponsesTextGenerationCode.astro   |    4 +-
 src/components/overrides/Page.astro           |    6 +-
 ...ss-Supports-Customer-Metadata-Boundary.mdx |    4 +-
 .../access/2025-08-26-mcp-server-portals.mdx  |    1 -
 ...-17-clientless-access-for-private-apps.mdx |    4 +-
 .../2025-12-22-agents-sdk-ai-sdk-v6.mdx       |   40 +-
 .../2026-04-15-agentlee-writeops-genui.mdx    |   14 +-
 .../ai-search/2025-09-19-autorag-metrics.mdx  |    2 +-
 .../2025-09-25-ai-search-more-models.mdx      |   31 +-
 ...add-extra-headers-for-website-crawling.mdx |    7 +-
 ...2026-04-16-ai-search-namespace-binding.mdx |    4 +-
 .../2025-10-01-confidence-intervals.mdx       |    8 +-
 .../2026-02-18-cfworker-server-timing.mdx     |    8 +-
 .../2026-03-09-vulnerability-scanner.mdx      |    4 +-
 .../2026-05-19-event-subscriptions.mdx        |   10 +-
 .../2024-09-05-cache-rules-templates.mdx      |    1 -
 .../2024-11-07-shard-cache-by-cache-key.mdx   |   16 +-
 ...-11-07-cache-keys-for-cloudflare-trace.mdx |   26 +-
 ...1-25-audit-logs-for-cache-purge-events.mdx |   44 +-
 .../cache/2026-03-24-cache-response-rules.mdx |    2 +-
 .../changelog/casb/2025-10-28-casb-roles.mdx  |    4 +-
 .../2025-08-29-warp-AI-diag-analyzer.mdx      |    1 -
 ...nabled-search-for-zero-trust-dashboard.mdx |    4 +-
 ...for-supported-cloudflare-one-resources.mdx |   10 +-
 .../cloudflare-one/new-applications-71825.mdx |    2 +-
 ...-01-27-configure-cloudflare-source-ips.mdx |    2 +-
 ...025-10-01-new-container-instance-types.mdx |    2 +-
 .../containers/2025-11-21-new-cpu-pricing.mdx |    6 +-
 ...02-25-higher-container-resource-limits.mdx |    2 +-
 .../2026-03-24-docker-hub-images.mdx          |    2 +-
 .../2026-04-05-regional-placement.mdx         |    8 +-
 ...4-13-sandbox-outbound-workers-tls-auth.mdx |    2 +-
 .../2026-05-12-ssh-enabled-by-default.mdx     |    2 +-
 .../dex/2025-11-12-dex-logpush-jobs.mdx       |    4 +-
 .../dex/2026-02-19-dex-supports-cmb-eu.mdx    |    1 -
 ...04-28-dex-internet-outage-notification.mdx |    2 +-
 .../dex/2026-04-28-dex-speed-test.mdx         |    3 +-
 .../dex/2026-04-29-dex-tests-to-auth.mdx      |    3 +-
 .../2025-04-14-account-level-dlp-settings.mdx |    1 +
 .../dlp/2025-07-17-document-matching.mdx      |    5 +-
 .../dlp/2025-08-25-ai-prompt-protection.mdx   |   12 +-
 ...25-har-file-detection-and-sanitization.mdx |    2 +-
 ...-04-14-cloudflare-api-token-detections.mdx |   16 +-
 .../dlp/2026-04-28-pii-record-profile.mdx     |    2 +-
 .../dns/2026-03-31-internal-dns-open-beta.mdx |    1 +
 .../dns/2026-04-28-enforce-dns-only.mdx       |    1 +
 ...2025-08-21-durable-objects-get-by-name.mdx |    8 +-
 ...2025-10-16-durable-objects-data-studio.mdx |    2 +-
 ...durable-objects-sqlite-storage-billing.mdx |    3 +-
 .../2026-03-15-durable-object-id-name.mdx     |   18 +-
 .../2025-07-21-subaddressing.mdx              |    2 +-
 .../2024-12-19-escalate-user-submissions.mdx  |    2 +-
 .../2025-10-16-on-demand-security-report.mdx  |    1 -
 ...adjustment-to-final-disposition-column.mdx |    3 +-
 ...25-12-03-submission-terminology-update.mdx |   11 +-
 ...anced-visibility-post-delivery-actions.mdx |    9 +-
 ...ed-accessibility-search-for-monitoring.mdx |   26 +-
 ...6-03-15-infinite-paging-investigations.mdx |   12 +-
 ...2026-04-06-dane-support-mx-deployments.mdx |   12 +-
 .../2026-04-07-triage-status-tracking.mdx     |    2 +
 ...5-06-cloudy-summaries-in-phishnet_o365.mdx |    1 +
 .../2025-06-23-user-groups-ga.mdx             |    4 +-
 .../2025-09-03-rate-limiting-improvement.mdx  |   21 +-
 ...two-factor-authentication-backup-codes.mdx |    3 +-
 .../2025-09-25-sign-in-with-github.mdx        |    3 +-
 .../fundamentals/2025-10-01-md-returned.mdx   |    2 +-
 .../2025-10-14-sso-self-service-ux.mdx        |    1 -
 .../fundamentals/2025-10-30-email-2FA.mdx     |    6 +-
 ...5-10-30-member-management-improvements.mdx |   14 +-
 .../2026-01-23-New-2FA-Experience.mdx         |    9 +-
 .../2026-02-12-markdown-for-agents.mdx        |    3 +-
 ...02-16-markdown-for-agents-improvements.mdx |    2 +-
 ...json-rfc9457-responses-for-1xxx-errors.mdx |    1 +
 ...-12-retry-after-header-for-1xxx-errors.mdx |   19 +-
 .../2026-03-17-scim-authentik-support.mdx     |    2 +-
 .../2026-03-18-scim-audit-logging.mdx         |    4 +-
 .../2026-04-06-organizations-public-beta.mdx  |    2 +-
 .../2026-04-10-secret-scanning-support.mdx    |    2 +-
 .../2026-04-14-oauth-consent-and-revoke.mdx   |   22 +-
 ...27-structured-responses-for-5xx-errors.mdx |    1 +
 .../2026-05-04-keyboard-shortcuts.mdx         |   54 +-
 ...025-07-24-HTTP-Inspection-on-all-ports.mdx |    4 +-
 ...-07-28-Spam-domain-category-introduced.mdx |   12 +-
 ...08-15-gemini-application-replaces-bard.mdx |    3 +-
 .../2025-10-10-new-domain-categories.mdx      |   10 +-
 ...-11-06-Applications-recategorised-plan.mdx |    6 +-
 ...02-27-new-protocol-detection-protocols.mdx |   14 +-
 .../Gateway-application-categories-added.mdx  |    4 +-
 ...4-hyperdrive-remote-database-local-dev.mdx |   14 +-
 src/content/changelog/images/heic-support.mdx |    1 +
 ...2025-08-22-kv-performance-improvements.mdx |    2 -
 .../2025-06-04-account-load-balancing-ui.mdx  |    3 +-
 .../2025-07-09-usage-tracking.mdx             |    2 +-
 .../2025-08-15-extended-retention.mdx         |    2 +-
 .../2025-09-03-log-headers-and-cookies.mdx    |    2 -
 .../2025-09-11-contextual-pivots.mdx          |    4 +-
 .../2025-09-11-new-results-table-view.mdx     |    4 +-
 .../2025-11-04-query-cancellation.mdx         |    2 +-
 .../2025-11-11-resize-sql-window.mdx          |    2 +-
 .../2025-11-13-fixed-custom-date.mdx          |    2 +-
 .../log-explorer/2025-11-13-new-datasets.mdx  |    5 +-
 .../2026-03-11-ingest-field-selection.mdx     |   20 +-
 .../logs/2024-10-08-new-gateway-fields.mdx    |    2 +-
 .../logs/2026-03-09-log-fields-updated.mdx    |    1 -
 ...26-04-20-pipelines-logpush-destination.mdx |    2 +-
 ...2026-04-21-logpush-subrequests-merging.mdx |    4 +-
 ...-03-24-interconnects-navigation-update.mdx |    2 +-
 .../pages/2025-05-30-pages-build-image-v3.mdx |    2 +-
 .../queues/2025-03-25-pause-purge-queues.mdx  |    8 +-
 .../2025-04-17-pull-consumer-limits.mdx       |    3 +
 .../2025-05-09-publish-to-queues-via-http.mdx |    2 +-
 .../queues/2025-08-19-event-subscriptions.mdx |   26 +-
 ...2025-09-25-announcing-r2-sql-open-beta.mdx |    2 +-
 ...ql-functions-expressions-complex-types.mdx |    1 -
 ...0-r2-sql-json-functions-explain-format.mdx |    2 +
 .../radar/2025-08-04-radar-ct-insights.mdx    |    2 +-
 .../radar/2025-09-29-radar-regional-data.mdx  |    2 +-
 .../radar/2026-02-25-radar-aspa-insights.mdx  |    2 +-
 .../2026-04-01-radar-routing-section.mdx      |    2 +-
 ...2026-05-28-realtimekit-track-recording.mdx |   36 +
 .../2026-1-15-crowdstrike-score.mdx           |    1 +
 .../2025-10-30-tcp-rtt-and-tcp-fields.mdx     |    8 +-
 .../rules/2026-01-12-dma-metro-code-field.mdx |    4 +-
 .../rules/2026-01-20-array-map-functions.mdx  |   12 +-
 .../2026-01-27-body-buffering-settings.mdx    |   26 +-
 .../rules/2026-03-18-worker-timing-field.mdx  |    4 +-
 .../rules/2026-03-25-rfc9440-mtls-fields.mdx  |    2 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   12 +-
 ...20-cloudflare-typescript-v6.0.0-beta.1.mdx |   70 +-
 ...-02-13-cloudflare-python-v5.0.0-beta.1.mdx |   13 +-
 .../2025-07-18-brand-protection-api.mdx       |   14 +-
 .../2025-10-27-RFI-Tokens-in-Dash.mdx         |    2 +-
 ...protection-logo-dashboard-report-abuse.mdx |    4 +-
 ...Threat-Events-now-show-events-insights.mdx |    6 +-
 ...-01-14-Download-URL-Scanner-Report-PDF.mdx |    8 +-
 .../2026-02-19-threat-events-graphs.mdx       |    1 +
 ...026-02-23-Saved-views-in-threat-events.mdx |    5 +-
 .../2026-04-08-threat-events-notification.mdx |   20 +-
 .../2026-05-07-CSV-export-for-RFIs.mdx        |    1 +
 ...-12-URL-scanner-report-agent-readiness.mdx |   17 +-
 ...archive-and-audit-security-action-items.md |    5 +-
 .../2025-08-25-secrets-store-ai-gateway.mdx   |   20 +-
 ...07-22-media-transformations-audio-mode.mdx |    2 +-
 .../2026-04-06-redesigned-support-portal.mdx  |    1 +
 .../2026-04-28-direct-support-navigation.mdx  |    4 +-
 .../2025-02-03-terraform-v5-provider.mdx      |    6 +-
 .../2025-05-19-terraform-v5.5.0-provider.mdx  |   13 +-
 .../2025-06-17-terraform-v5.6.0-provider.mdx  |    3 +-
 .../2025-07-11-terraform-v5.7.0-provider.mdx  |    3 +-
 .../2025-08-01-terraform-v5.8.2-provider.mdx  |    6 +-
 .../2025-08-15-terraform-v5.8.4-provider.mdx  |    6 +-
 .../2025-08-29-terrform-v5.9-provider.mdx     |    3 +-
 .../2025-11-20-terraform-v5.13.0-provider.mdx |   63 +-
 .../2025-12-05-terraform-v5.14.0-provider.mdx |   22 +-
 .../2025-12-19-terraform-v5.15.0-provider.mdx |   36 +-
 .../2026-01-20-terraform-v5.16.0-provider.mdx |   55 +-
 .../2026-02-12-terraform-v5.17.0-provider.mdx |   91 +-
 .../2026-04-24-terraform-v5.19.0-provider.mdx |    1 +
 .../2026-04-24-tf-migrate-tool-released.mdx   |    6 +-
 .../tunnel/2025-07-15-udp-improvements.mdx    |    3 +-
 ...el-networks-list-endpoints-new-default.mdx |   28 +-
 .../2025-09-18-tunnel-hostname-routing.mdx    |    3 +-
 ...2026-01-15-warp-connector-ping-support.mdx |    2 +-
 .../changelog/waf/2025-07-14-waf-release.mdx  |    1 -
 .../changelog/waf/2025-07-21-emergency.mdx    |   30 +-
 .../changelog/waf/2025-07-28-waf-release.mdx  |   11 +-
 .../changelog/waf/2025-08-04-waf-release.mdx  |  207 +--
 .../waf/2025-08-07-emergency-waf-release.mdx  |   75 +-
 .../changelog/waf/2025-08-11-waf-release.mdx  |  460 ++++---
 .../changelog/waf/2025-08-18-waf-release.mdx  |  275 ++--
 .../changelog/waf/2025-08-25-waf-release.mdx  |   98 +-
 .../waf/2025-08-29-emergency-waf-release.mdx  |   72 +-
 .../changelog/waf/2025-09-01-waf-release.mdx  |   78 +-
 .../waf/2025-09-04-emergency-waf-release.mdx  |   95 +-
 .../changelog/waf/2025-09-08-waf-release.mdx  |  250 ++--
 .../changelog/waf/2025-09-15-waf-release.mdx  |  100 +-
 .../changelog/waf/2025-09-22-waf-release.mdx  |  221 ++--
 .../waf/2025-09-24-emergency-waf-release.mdx  |   52 +-
 .../changelog/waf/2025-09-26-waf-release.mdx  |  268 ++--
 .../waf/2025-09-28-emergency-waf-release.mdx  |   80 +-
 .../changelog/waf/2025-09-29-waf-release.mdx  |  135 +-
 .../changelog/waf/2025-10-03-waf-release.mdx  |  488 +++----
 .../changelog/waf/2025-10-06-waf-release.mdx  |  220 ++--
 .../waf/2025-10-07-emergency-waf-release.mdx  |   55 +-
 .../waf/2025-10-17-emergency-waf-release.mdx  |   82 +-
 .../changelog/waf/2025-10-20-waf-release.mdx  |   16 +-
 .../waf/2025-10-23-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-24-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-30-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-11-05-emergency-waf-release.mdx  |   50 +-
 .../changelog/waf/2025-11-10-waf-release.mdx  |    4 +-
 .../changelog/waf/2025-11-17-waf-release.mdx  |    2 +-
 .../waf/2025-11-21-emergency-waf-release.mdx  |    2 +-
 .../changelog/waf/2025-11-24-waf-release.mdx  |   16 +-
 .../changelog/waf/2025-12-01-waf-release.mdx  |    9 +-
 .../waf/2025-12-02-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-03-emergency-waf-release.mdx  |    3 +-
 .../waf/2025-12-10-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-11-emergency-waf-release.mdx  |   14 +-
 .../changelog/waf/2025-12-18-waf-release.mdx  |  225 ++--
 .../changelog/waf/2026-01-12-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-15-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-20-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-26-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-02-02-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-03-02-waf-release.mdx  |    7 +-
 .../waf/2026-03-12-emergency-waf-release.mdx  |    6 +-
 .../changelog/waf/2026-03-23-waf-release.mdx  |  104 +-
 .../changelog/waf/2026-03-30-waf-release.mdx  |  116 +-
 .../changelog/waf/2026-04-15-waf-release.mdx  |  144 ++-
 .../changelog/waf/2026-04-21-waf-release.mdx  |  339 +++--
 .../changelog/waf/2026-04-27-waf-release.mdx  |  343 ++---
 .../waf/2026-05-07-emergency-waf-release.mdx  |   12 +-
 .../changelog/waf/2026-05-11-waf-release.mdx  |    9 +-
 .../waf/2026-05-15-emergency-waf-release.mdx  |   16 +-
 .../changelog/waf/2026-05-20-waf-release.mdx  |   12 +-
 .../2026-04-30-rum-navigation-types.mdx       |    4 +-
 .../2025-08-05-openai-open-models.mdx         |    5 +-
 .../workers-ai/2025-08-27-partner-models.mdx  |    3 +-
 .../workers-ai/2025-09-05-embeddinggemma.mdx  |    3 +-
 .../workers-vpc/2025-09-25-workers-vpc.mdx    |    4 +-
 ...-07-new-ways-to-get-started-on-workers.mdx |   12 +-
 .../workers/2025-03-25-higher-cpu-limits.mdx  |    2 +-
 ...2025-04-08-deploy-to-cloudflare-button.mdx |   18 +-
 .../workers/2025-04-09-qb-workers-logs-ga.mdx |    4 +-
 ...2025-04-22-python-worker-cron-triggers.mdx |    2 +-
 ...025-05-14-python-worker-durable-object.mdx |    2 +-
 .../workers/2025-06-05-open-next-size.mdx     |    2 +-
 .../2025-07-23-workers-preview-urls.mdx       |   12 +-
 .../2025-08-04-builds-increased-disk-size.mdx |    8 +-
 ...08-08-add-waituntil-cloudflare-workers.mdx |    2 +-
 ...port-long-branch-names-preview-aliases.mdx |    4 +-
 .../workers/2025-08-11-messagechannel.mdx     |   16 +-
 .../2025-08-14-new-python-handlers.mdx        |    2 +-
 ...workers-terraform-and-sdk-improvements.mdx |   39 +-
 .../2025-08-15-static-assets-redirect-url.mdx |    6 +-
 ...5-08-19-improved-wrangler-error-screen.mdx |    4 +-
 .../workers/2025-09-03-new-workers-api.mdx    |   86 +-
 .../2025-09-07-builds-increased-cpu-paid.mdx  |   17 +-
 ...2025-09-09-interactive-wrangler-assets.mdx |    5 +-
 ...025-09-10-built-with-cloudflare-button.mdx |    2 +-
 ...09-11-increased-version-rollback-limit.mdx |    9 +-
 .../2025-09-17-update-preview-url-setting.mdx |    6 +-
 .../2025-09-19-ratelimit-workers-ga.mdx       |    4 +-
 ...dev-multi-config-cross-command-support.mdx |   19 +-
 ...9-26-analytics-engine-sql-enhancements.mdx |   21 +-
 .../workers/2025-09-26-ctx-exports.md         |   16 +-
 .../workers/2025-10-09-assets-terraform.mdx   |   10 +-
 .../2025-10-09-workflows-terraform.mdx        |    8 +-
 ...025-10-23-preview-url-default-behavior.mdx |    7 +-
 ...-10-24-automatic-resource-provisioning.mdx |    2 +-
 .../workers/2025-10-30-builds-preview.mdx     |    8 +-
 .../2025-11-09-cloudflare-env-variable.mdx    |    1 +
 ...lytics-engine-further-sql-enhancements.mdx |   12 +-
 ...25-12-01-build-image-policies-dev-plat.mdx |    2 +-
 ...5-12-08-python-cold-start-improvements.mdx |   10 +-
 .../workers/2025-12-08-python-pywrangler.mdx  |    1 -
 .../2025-12-08-vite-optional-config.mdx       |    2 +-
 .../2025-12-08-vite-programmatic-config.mdx   |    2 +-
 .../2025-12-16-vitest-ctx-exports-support.mdx |   10 +-
 ...2025-12-19-tanstack-start-prerendering.mdx |   20 +-
 .../2026-02-15-workers-best-practices.mdx     |    1 +
 .../2026-03-27-rfc9440-mtls-fields.mdx        |   45 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   34 +-
 ...026-05-06-react-nextjs-vulnerabilities.mdx |    2 +-
 .../2025-01-15-workflows-more-steps.mdx       |    6 +-
 .../workflows/2025-10-28-raising-limits.mdx   |    6 +-
 .../2026-03-23-local-dev-instance-methods.mdx |    2 +-
 .../2026-05-01-dynamic-workflows.mdx          |    6 +-
 .../compatibility-flags/allow-custom-ports.md |    1 +
 .../enable-nodejs-http-modules.md             |    8 +-
 .../enable-nodejs-http-server-modules.md      |    8 +-
 .../fetcher-no-get-put-delete.md              |    1 -
 .../compatibility-flags/js-weak-refs.md       |    3 +-
 .../new-url-parser-implementation.md          |    8 +-
 .../compatibility-flags/nodejs-compat.md      |   12 +-
 .../queue-consumer-no-wait-waituntil.md       |   29 +-
 .../queues-json-messages.md                   |    2 +-
 .../compatibility-flags/request-signal.md     |    2 +-
 .../streams-byob-reader-detaches-buffer.md    |   12 +-
 .../compatibility-flags/strict-crypto.md      |    1 +
 .../throw-on-unrecognized-import-assertion.md |    1 -
 .../compatibility-flags/to-string-tag.md      |    2 +-
 .../urlsearchparams-deletehasvalue.md         |    6 +-
 .../web-socket-auto-reply-to-close.md         |   38 +-
 .../web-socket-compression.md                 |    2 +-
 .../websocket-standard-binary-type.md         |    4 +-
 ...ws-preserve-non-retryable-error-message.md |   14 +-
 .../mpp/charge-for-http-content.mdx           |   10 +-
 .../agents/agentic-payments/x402/index.mdx    |    4 +-
 .../ai-crawl-control-with-bots.mdx            |    2 +-
 .../ai-crawl-control-with-waf.mdx             |   10 +-
 .../features/analyze-ai-traffic.mdx           |   22 +-
 .../features/manage-ai-crawlers.mdx           |   24 +-
 .../set-up-cloudflare-account.mdx             |    2 +-
 .../features/track-robots-txt.mdx             |   10 +-
 .../reference/redirects-for-ai-training.mdx   |   16 +-
 .../configuration/authentication.mdx          |    2 +-
 .../configuration/custom-providers.mdx        |   69 +-
 .../evaluations/add-human-feedback.mdx        |    1 +
 .../docs/ai-gateway/features/dlp/index.mdx    |   10 +-
 .../features/dynamic-routing/usage.mdx        |    3 +-
 .../integrations/aig-workers-ai-binding.mdx   |    2 +-
 src/content/docs/ai-gateway/mcp-server.mdx    |    2 +-
 .../observability/logging/index.mdx           |    6 +-
 .../docs/ai-gateway/reference/audit-logs.mdx  |   71 +-
 .../docs/ai-gateway/reference/limits.mdx      |   13 +-
 .../ai-gateway/tutorials/pruna-p-video.mdx    |   14 +-
 .../docs/ai-gateway/usage/chat-completion.mdx |    6 +-
 .../ai-gateway/usage/providers/anthropic.mdx  |   17 +-
 .../usage/providers/azureopenai.mdx           |   12 +-
 .../ai-gateway/usage/providers/baseten.mdx    |   40 +-
 .../ai-gateway/usage/providers/bedrock.mdx    |   10 +-
 .../docs/ai-gateway/usage/providers/fal.mdx   |   26 +-
 .../usage/providers/google-ai-studio.mdx      |   15 +-
 .../ai-gateway/usage/providers/ideogram.mdx   |   20 +-
 .../docs/ai-gateway/usage/rest-api.mdx        |   70 +-
 .../usage/websockets-api/non-realtime-api.mdx |    2 +-
 .../usage/websockets-api/realtime-api.mdx     |    2 +-
 .../docs/ai-search/api/instances/rest-api.mdx |    4 +-
 .../docs/ai-search/api/items/rest-api.mdx     |    4 +-
 .../ai-search/configuration/models/index.mdx  |    2 -
 src/content/docs/ai-search/how-to/nlweb.mdx   |   34 +-
 .../docs/ai-search/wrangler-commands.mdx      |    2 +-
 .../docs/ai/related-products/ai-gateway.mdx   |    2 +-
 .../account-analytics.mdx                     |   28 +-
 .../analytics-with-workers.mdx                |   10 +-
 .../account-and-zone-analytics/index.mdx      |    2 +-
 .../analytics/analytics-engine/grafana.mdx    |   12 +-
 .../docs/analytics/analytics-engine/index.mdx |   14 +-
 .../analytics/analytics-engine/limits.mdx     |    8 +-
 .../analytics/analytics-engine/pricing.mdx    |    2 +-
 .../analytics-engine/recipes/index.mdx        |    2 +-
 .../analytics/analytics-engine/sampling.mdx   |   62 +-
 .../analytics/analytics-engine/sql-api.mdx    |   10 +-
 .../sql-reference/aggregate-functions.mdx     |    2 +-
 .../sql-reference/bit-functions.mdx           |    2 +-
 .../sql-reference/date-time-functions.mdx     |    2 +-
 .../sql-reference/encoding-functions.mdx      |    2 +-
 .../analytics-engine/sql-reference/index.mdx  |    2 +-
 .../sql-reference/mathematical-functions.mdx  |    2 +-
 .../sql-reference/string-functions.mdx        |    2 +-
 .../type-conversion-functions.mdx             |    2 +-
 .../analytics-engine/worker-querying.mdx      |    1 -
 .../analytics-integrations/datadog.mdx        |    1 -
 .../analytics-integrations/index.mdx          |    2 +-
 .../analytics-integrations/prometheus.mdx     |   75 +-
 .../docs/analytics/custom-dashboards.mdx      |   38 +-
 .../docs/analytics/faq/about-analytics.mdx    |   16 +-
 src/content/docs/analytics/faq/index.mdx      |    2 +-
 src/content/docs/analytics/faq/other-faqs.mdx |   12 +-
 src/content/docs/analytics/faq/wae-faqs.mdx   |    9 +-
 .../docs/analytics/graphql-api/errors.mdx     |   64 +-
 .../features/confidence-intervals.mdx         |  102 +-
 .../graphql-api/features/discovery/index.mdx  |    1 -
 .../analytics/graphql-api/features/index.mdx  |    2 +-
 .../authentication/graphql-client-headers.mdx |    6 +-
 .../getting-started/authentication/index.mdx  |   52 +-
 .../getting-started/compose-graphql-query.mdx |   15 -
 .../getting-started/execute-graphql-query.mdx |    4 +-
 .../explore-graphql-schema.mdx                |   17 +-
 .../graphql-api/getting-started/index.mdx     |   20 +-
 .../docs/analytics/graphql-api/limits.mdx     |   18 +-
 .../docs/analytics/graphql-api/mcp-server.mdx |    2 +-
 .../graphql-api/migration-guides/index.mdx    |    4 +-
 .../network-analytics-v2/schema-map.mdx       |    1 -
 .../docs/analytics/graphql-api/sampling.mdx   |    4 -
 .../tutorials/end-customer-analytics.mdx      |  218 ++--
 .../analytics/graphql-api/tutorials/index.mdx |    2 +-
 .../querying-access-login-events.mdx          |   72 +-
 .../tutorials/querying-email-routing.mdx      |  352 ++---
 ...c-transit-endpoint-healthcheck-results.mdx |    5 +-
 ...gic-transit-tunnel-bandwidth-analytics.mdx |    8 +-
 ...gic-transit-tunnel-healthcheck-results.mdx |    5 +-
 src/content/docs/analytics/index.mdx          |   36 +-
 .../network-analytics/configure/index.mdx     |    2 +-
 .../configure/share-export.mdx                |    2 +-
 .../configure/time-range.mdx                  |    2 +-
 .../analytics/network-analytics/index.mdx     |   12 +-
 .../network-analytics/reference/index.mdx     |    2 +-
 .../network-analytics/understand/index.mdx    |    2 +-
 src/content/docs/analytics/sampling.mdx       |   23 +-
 .../docs/analytics/types-of-analytics.mdx     |   27 +-
 src/content/docs/api-shield/api-gateway.mdx   |    1 -
 src/content/docs/api-shield/glossary.mdx      |    3 +-
 src/content/docs/api-shield/index.mdx         |   30 +-
 .../management-and-monitoring/index.mdx       |    5 +-
 .../session-identifiers.mdx                   |    4 +-
 src/content/docs/api-shield/plans.mdx         |   15 +-
 .../reference/classic-schema-validation.mdx   |   14 +-
 .../docs/api-shield/reference/index.mdx       |    5 +-
 .../docs/api-shield/reference/terraform.mdx   |   11 +-
 .../security/graphql-protection/index.mdx     |    1 -
 .../docs/api-shield/security/index.mdx        |   45 +-
 .../security/jwt-validation/jwt-worker.mdx    |    2 +-
 .../jwt-validation/transform-rules.mdx        |    4 +-
 .../docs/api-shield/security/mtls/byo-ca.mdx  |    1 -
 .../docs/api-shield/security/mtls/index.mdx   |    1 -
 .../security/sequence-analytics.mdx           |    3 +-
 .../security/sequence-mitigation/api.mdx      |   23 +-
 .../sequence-mitigation/custom-rules.mdx      |   21 +-
 .../security/sequence-mitigation/index.mdx    |    8 +-
 .../security/volumetric-abuse-detection.mdx   |   11 +-
 .../docs/argo-smart-routing/analytics.mdx     |    9 +-
 .../argo-smart-routing/argo-for-packets.mdx   |    1 -
 src/content/docs/artifacts/api/errors.mdx     |   28 +-
 .../docs/artifacts/api/git-protocol.mdx       |    6 +-
 .../docs/artifacts/concepts/repositories.mdx  |   10 +-
 .../docs/artifacts/examples/git-client.mdx    |    5 +-
 .../docs/artifacts/guides/authentication.mdx  |   18 +-
 .../artifacts/guides/event-subscriptions.mdx  |    1 +
 .../docs/artifacts/platform/limits.mdx        |    4 +-
 .../docs/artifacts/platform/pricing.mdx       |    8 +-
 .../about/index.mdx                           |    1 -
 .../about/plugin-compatibility.mdx            |   50 +-
 .../about/test-current-speed.mdx              |    1 -
 .../get-started/change-nameservers.mdx        |    2 -
 .../get-started/index.mdx                     |    3 +-
 .../reference/cache-device-type.mdx           |    8 +-
 .../reference/index.mdx                       |    3 +-
 .../reference/page-rule-integration.mdx       |   17 +-
 .../reference/query-parameters.mdx            |   80 +-
 .../reference/subdomain-subdirectories.mdx    |    6 +-
 .../troubleshooting/index.mdx                 |   15 +-
 .../get-started/create-billing-profile.mdx    |    4 +-
 .../get-started/update-billing-info.mdx       |   22 +-
 .../docs/billing/manage/billable-usage.mdx    |   15 +-
 .../docs/billing/manage/budget-alerts.mdx     |   22 +-
 .../billing/manage/cancel-subscription.mdx    |    6 +-
 src/content/docs/billing/manage/invoices.mdx  |   26 +-
 .../docs/billing/manage/optimize-costs.mdx    |   48 +-
 .../manage/pay-invoices-overdue-balances.mdx  |    7 +-
 .../instant-bank-payments-link.mdx            |    6 +-
 .../docs/billing/threshold-billing.mdx        |    8 +-
 .../billing/troubleshoot/error-reference.mdx  |   24 +-
 .../resolve-cannot-remove-payment-method.mdx  |   37 +-
 ...ve-you-cannot-modify-this-subscription.mdx |   12 +-
 .../troubleshoot/troubleshoot-invoices.mdx    |    2 +-
 .../understand/billing-permissions.mdx        |   26 +-
 .../billing/understand/billing-policy.mdx     |   18 +-
 .../billing/understand/how-charges-accrue.mdx |   72 +-
 .../billing/understand/preview-services.mdx   |    2 +-
 .../understand/usage-based-billing.mdx        |   36 +-
 .../docs/bots/account-abuse-protection.mdx    |   75 +-
 .../block-ai-bots.mdx                         |    4 +-
 .../custom-rules.mdx                          |   22 +-
 .../detection-ids/additional-detections.mdx   |    7 +-
 .../bots/additional-configurations/index.mdx  |    5 +-
 .../ja3-ja4-fingerprint/index.mdx             |   81 +-
 .../signals-intelligence.mdx                  |    2 +-
 .../javascript-detections.mdx                 |    2 +-
 src/content/docs/bots/concepts/bot-tags.mdx   |    3 +-
 src/content/docs/bots/concepts/bot/index.mdx  |    2 +-
 .../bots/concepts/bot/signed-agents/index.mdx |    3 +-
 .../concepts/bot/signed-agents/policy.mdx     |    7 +-
 .../concepts/bot/verified-bots/policy.mdx     |    7 +-
 src/content/docs/bots/concepts/index.mdx      |    3 +-
 src/content/docs/bots/get-started/index.mdx   |    3 +-
 src/content/docs/bots/glossary.mdx            |    3 +-
 .../docs/bots/plans/bm-subscription.mdx       |   22 +-
 src/content/docs/bots/reference/alerts.mdx    |    9 +-
 .../reference/bot-management-variables.mdx    |   12 +-
 .../bots/reference/bot-verification/index.mdx |    5 +-
 .../bot-verification/ip-validation.mdx        |    9 +-
 src/content/docs/bots/reference/index.mdx     |    3 +-
 .../reference/machine-learning-models.mdx     |    5 +-
 .../docs/bots/reference/sample-terms.mdx      |    6 +-
 .../troubleshooting/bot-management-skips.mdx  |    3 +-
 .../bots/troubleshooting/false-positives.mdx  |    3 +-
 .../docs/bots/troubleshooting/index.mdx       |    4 +-
 .../docs/bots/workers-templates/index.mdx     |    3 +-
 .../docs/browser-run/features/index.mdx       |    2 +-
 .../docs/browser-run/how-to/deploy-worker.mdx |    2 +-
 src/content/docs/browser-run/mcp-server.mdx   |    2 +-
 .../quick-actions/api-reference.mdx           |    2 +-
 .../reference/browser-close-reasons.mdx       |   54 +-
 src/content/docs/byoip/address-maps/setup.mdx |   26 +-
 src/content/docs/byoip/changelog.mdx          |    2 +-
 src/content/docs/byoip/concepts/index.mdx     |    2 +-
 .../byoip/concepts/prefix-delegations.mdx     |    1 -
 src/content/docs/byoip/glossary.mdx           |    2 +-
 .../docs/byoip/route-leak-detection.mdx       |    3 +-
 .../docs/byoip/service-bindings/index.mdx     |    3 +-
 .../docs/byoip/troubleshooting/index.mdx      |    9 +-
 .../advanced-configuration/cache-reserve.mdx  |    9 +-
 .../advanced-configuration/crawler-hints.mdx  |    9 +-
 .../advanced-configuration/early-hints.mdx    |   21 +-
 .../cache/advanced-configuration/index.mdx    |    3 +-
 .../query-string-sort.mdx                     |   32 +-
 .../serve-tailored-content.mdx                |  158 +--
 .../vary-for-images.mdx                       |   74 +-
 .../cache-security/avoid-web-poisoning.mdx    |   18 +-
 .../cache-security/cache-deception-armor.mdx  |    6 +-
 .../docs/cache/cache-security/cors.mdx        |   11 +-
 .../docs/cache/cache-security/index.mdx       |    3 +-
 .../docs/cache/concepts/cache-behavior.mdx    |   10 +-
 .../docs/cache/concepts/cache-responses.mdx   |    9 +-
 .../docs/cache/concepts/cdn-cache-control.mdx |  178 +--
 .../docs/cache/concepts/customize-cache.mdx   |   13 +-
 .../cache/concepts/default-cache-behavior.mdx |   44 +-
 src/content/docs/cache/concepts/index.mdx     |    3 +-
 .../cache/concepts/retention-vs-freshness.mdx |    5 +-
 .../docs/cache/concepts/revalidation.mdx      |    1 -
 src/content/docs/cache/get-started.mdx        |   58 +-
 src/content/docs/cache/glossary.mdx           |    3 +-
 .../docs/cache/how-to/always-online.mdx       |    5 +-
 src/content/docs/cache/how-to/cache-keys.mdx  |   72 +-
 .../cache-response-rules/create-dashboard.mdx |    4 +-
 .../how-to/cache-rules/examples/index.mdx     |    4 +-
 .../docs/cache/how-to/cache-rules/order.mdx   |    3 +-
 .../cache-rules/page-rules-migration.mdx      |    4 +-
 .../how-to/configure-cache-status-code.mdx    |   14 +-
 .../how-to/edge-browser-cache-ttl/index.mdx   |   14 +-
 .../set-browser-ttl.mdx                       |    7 +-
 src/content/docs/cache/how-to/index.mdx       |    3 +-
 .../how-to/purge-cache/purge-by-hostname.mdx  |    9 +-
 .../purge-cache/purge-by-single-file.mdx      |    2 +-
 .../how-to/purge-cache/purge-by-tags.mdx      |   26 +-
 .../how-to/purge-cache/purge-cache-key.mdx    |   72 +-
 .../how-to/purge-cache/purge-everything.mdx   |    3 +-
 .../purge-cache/purge-varied-images.mdx       |    1 -
 .../purge-cache/purge-zone-versions.mdx       |   81 +-
 .../how-to/purge-cache/purge_by_prefix.mdx    |   39 +-
 .../docs/cache/how-to/set-caching-levels.mdx  |    9 +-
 .../interaction-cloudflare-products/index.mdx |    5 +-
 .../interaction-cloudflare-products/r2.mdx    |    1 -
 .../waf-snippets.mdx                          |    2 +-
 .../workers-cache-rules.mdx                   |    9 +-
 .../workers.mdx                               |    3 +-
 .../performance-review/cache-analytics.mdx    |    5 +-
 .../performance-review/cache-performance.mdx  |    5 +-
 .../docs/cache/performance-review/index.mdx   |    3 +-
 src/content/docs/cache/plans.mdx              |    5 +-
 .../reference/cdn-reference-architecture.mdx  |    1 -
 .../docs/cache/reference/development-mode.mdx |    5 +-
 src/content/docs/cache/reference/index.mdx    |    3 +-
 .../cache/troubleshooting/always-online.mdx   |    3 -
 .../docs/cache/troubleshooting/index.mdx      |    3 +-
 .../concepts/global-acceleration.mdx          |   14 +-
 .../reference/available-products.mdx          |    2 +-
 .../client-ip-geolocation/about/index.mdx     |    4 +-
 .../docs/client-ip-geolocation/faq/index.mdx  |    2 -
 .../client-ip-geolocation/get-started.mdx     |   16 +-
 .../docs/client-ip-geolocation/index.mdx      |   14 +-
 .../additional-configuration.mdx              |    2 +-
 .../challenge-pages/detect-response.mdx       |    2 +-
 .../challenge-types/challenge-pages/index.mdx |    2 +-
 .../challenge-pages/resolve-challenge.mdx     |    2 +-
 .../challenge-types/index.mdx                 |    6 +-
 .../challenge-types/turnstile.mdx             |   12 +-
 .../cloudflare-challenges/concepts/index.mdx  |    4 +-
 .../docs/cloudflare-challenges/index.mdx      |    3 +-
 .../cloudflare-challenges/reference/index.mdx |    6 +-
 .../reference/supported-browsers.mdx          |   38 +-
 .../reference/supported-languages.mdx         |   44 +-
 .../challenge-solve-issues.mdx                |    5 +-
 .../hostname-validation/backoff-schedule.mdx  |    5 +-
 .../hostname-validation/error-codes.mdx       |    1 -
 .../hostname-validation/pre-validation.mdx    |   59 +-
 .../migrating-custom-hostnames.mdx            |    2 +-
 .../hostname-analytics.mdx                    |   16 +-
 .../performance/argo-for-saas.mdx             |    1 -
 .../performance/cache-for-saas.mdx            |    1 -
 .../performance/early-hints-for-saas.mdx      |   66 +-
 .../cloudflare-for-saas/performance/index.mdx |    9 +-
 .../reference/certificate-authorities.mdx     |    1 -
 .../reference/certificate-statuses.mdx        |    1 -
 .../reference/dcv-validation-backoff.mdx      |    1 -
 .../reference/hostname-priority.mdx           |    1 -
 .../reference/status-codes/custom-csrs.mdx    |   59 +-
 .../status-codes/custom-hostnames.mdx         |  123 +-
 .../reference/token-validity-periods.mdx      |    8 +-
 .../reference/versioning.mdx                  |   24 +-
 .../saas-customers/index.mdx                  |    3 +-
 .../saas-customers/product-compatibility.mdx  |    4 +-
 .../provider-guides/webflow.mdx               |    6 +-
 .../certificate-statuses.mdx                  |    1 -
 .../uploading-certificates.mdx                |    5 +-
 .../validate-certificates/delegated-dcv.mdx   |    5 +-
 .../validate-certificates/troubleshooting.mdx |   19 +-
 .../webhook-definitions.mdx                   |  755 +++++------
 .../cloudflare-for-saas/security/index.mdx    |   11 +-
 .../security/waf-for-saas/index.mdx           |   48 +-
 .../regional-services-for-saas.mdx            |    1 -
 .../advanced-settings/worker-as-origin.mdx    |    6 +-
 .../configuration/bindings.mdx                |    5 +
 .../configuration/observability.mdx           |    2 +-
 .../reference/limits.mdx                      |    2 +-
 .../reference/platform-examples.mdx           |    2 +-
 .../reference/worker-isolation.mdx            |   21 +-
 .../best-practices/minimal-ruleset.mdx        |   23 +-
 .../cloudflare-network-firewall/index.mdx     |    4 +-
 .../packet-captures/collect-pcaps.mdx         |    2 +-
 .../packet-captures/pcaps-bucket-setup.mdx    |    4 +-
 .../diagnose-traffic-decisions.mdx            |    8 +-
 .../access-controls/access-settings/index.mdx |    1 -
 .../require-access-protection.mdx             |   10 +-
 .../access-settings/session-management.mdx    |    1 +
 .../access-controls/ai-controls/index.mdx     |    1 -
 .../ai-controls/mcp-portals.mdx               |   16 +-
 .../application-token.mdx                     |   78 +-
 .../http-apps/authorization-cookie/cors.mdx   |    7 +-
 .../applications/http-apps/managed-oauth.mdx  |   14 +-
 .../http-apps/saas-apps/generic-oidc-saas.mdx |   11 +-
 .../saas-apps/grafana-cloud-saas-oidc.mdx     |    2 +-
 .../http-apps/saas-apps/grafana-saas-oidc.mdx |    2 +-
 .../http-apps/saas-apps/index.mdx             |    3 +-
 .../non-http/browser-rendering.mdx            |    9 +-
 .../arbitrary-tcp.mdx                         |    4 +-
 .../automatic-cloudflared-authentication.mdx  |    2 +-
 .../non-http/legacy-private-network-app.mdx   |    5 +-
 .../non-http/self-hosted-private-app.mdx      |   76 +-
 .../access-controls/event-subscriptions.mdx   |    2 +-
 .../access-controls/policies/app-paths.mdx    |   17 +-
 .../access-controls/policies/index.mdx        |   46 +-
 .../policies/policy-management.mdx            |   29 +-
 .../require-purpose-justification.mdx         |    1 -
 .../policies/temporary-auth.mdx               |    8 +-
 .../service-credentials/index.mdx             |    1 -
 .../service-credentials/service-tokens.mdx    |    4 +-
 .../docs/cloudflare-one/account-limits.mdx    |   19 +-
 .../docs/cloudflare-one/changelog/tunnel.mdx  |    5 +-
 .../data-classification/index.mdx             |   12 +-
 .../configure-detection-entries.mdx           |   20 +-
 .../predefined-detection-entries.mdx          |  296 ++---
 .../dlp-profiles/predefined-profiles.mdx      |   15 +-
 .../email-security/investigation/index.mdx    |    4 +-
 .../investigation/search-email.mdx            |    4 +-
 .../email-security/reference/index.mdx        |    4 +-
 .../reference/regional-processing.mdx         |    2 +-
 .../email-security/settings/auto-moves.mdx    |    4 +-
 .../detection-settings/best-practices.mdx     |    6 +-
 .../settings/detection-settings/index.mdx     |    4 +-
 .../settings/domain-management/domain.mdx     |    2 +-
 .../settings/domain-management/index.mdx      |    4 +-
 .../email-security/settings/index.mdx         |    4 +-
 .../phish-submissions/phishnet-365.mdx        |    2 +-
 .../phishnet-google-workspace.mdx             |    2 +-
 .../submission-addresses.mdx                  |    2 +-
 .../email-security/setup/index.mdx            |   18 +-
 .../email-security/setup/manage-domains.mdx   |    2 +-
 .../bcc-setup/gmail-bcc-setup/index.mdx       |    5 +-
 .../bcc-journaling/bcc-setup/index.mdx        |    5 +-
 .../bcc-journaling/index.mdx                  |    2 +-
 .../bcc-journaling/journaling-setup/index.mdx |    5 +-
 .../journaling-setup/m365-journaling.mdx      |    3 +-
 .../journaling-setup/manual-add.mdx           |    1 -
 .../setup/post-delivery-deployment/index.mdx  |    4 +-
 .../pre-delivery-deployment/egress-ips.mdx    |    2 +-
 .../setup/pre-delivery-deployment/index.mdx   |    6 +-
 .../partner-domain-tls.mdx                    |    2 +-
 .../prerequisites/index.mdx                   |    6 +-
 .../use-cases/index.mdx                       |    5 +-
 .../email-security/submissions/index.mdx      |    2 +-
 .../submissions/invalid-submissions.mdx       |    2 +-
 .../docs/cloudflare-one/faq/devices-faq.mdx   |   11 +-
 .../insights/analytics-overview.mdx           |    2 +-
 .../insights/analytics/ai-security.mdx        |   26 +-
 .../insights/analytics/application-access.mdx |   36 +-
 .../insights/dex/mcp-server.mdx               |    3 +-
 .../insights/dex/monitoring.mdx               |   10 +-
 .../cloudflare-one/insights/dex/rules.mdx     |    2 +-
 .../insights/dex/tests/index.mdx              |    6 +-
 .../docs/cloudflare-one/insights/index.mdx    |   18 +-
 .../dashboard-logs/admin-activity-logs.mdx    |   24 +-
 .../dashboard-logs/gateway-logs/index.mdx     |   63 +-
 .../insights/logs/dashboard-logs/index.mdx    |    2 +-
 .../logs/dashboard-logs/posture-logs.mdx      |    2 +-
 .../insights/logs/logpush/index.mdx           |   32 +-
 .../diagnostics/buckets.mdx                   |    4 +-
 .../network-visibility/diagnostics/index.mdx  |    5 +-
 .../integrations/cloud-and-saas/anthropic.mdx |   22 +-
 .../microsoft-365/m365-copilot-fedramp.mdx    |    2 +-
 .../microsoft-365/m365-copilot.mdx            |    2 +-
 .../identity-providers/aws-saml.mdx           |    2 +-
 .../identity-providers/cloudflare.mdx         |    4 +-
 .../identity-providers/facebook-login.mdx     |    8 +-
 .../identity-providers/github.mdx             |    4 +-
 .../integrations/identity-providers/index.mdx |    1 -
 .../integrations/identity-providers/okta.mdx  |    4 +-
 .../identity-providers/pingone-saml.mdx       |    1 -
 .../identity-providers/signed_authn.mdx       |    2 -
 .../integrations/service-providers/index.mdx  |    4 +-
 .../networks/connectivity-options.mdx         |   22 +-
 .../connectors/cloudflare-mesh/routes.mdx     |    1 +
 .../configure-tunnels/cipher-suites.mdx       |   10 +-
 .../configure-tunnels/index.mdx               |    2 +-
 .../configure-tunnels/origin-parameters.mdx   |   16 +-
 .../remote-tunnel-permissions.mdx             |  126 +-
 .../configure-tunnels/run-parameters.mdx      |   28 +-
 .../system-requirements.mdx                   |    5 +-
 .../tunnel-with-firewall.mdx                  |   19 +-
 .../deployment-guides/index.mdx               |    2 +-
 .../deployment-guides/terraform.mdx           |    1 -
 .../tunnel-useful-commands.mdx                |   14 +-
 .../downloads/copyrights.mdx                  |   57 +-
 .../cloudflare-tunnel/downloads/license.mdx   |    1 -
 .../get-started/create-remote-tunnel-api.mdx  |  117 +-
 .../get-started/create-remote-tunnel.mdx      |    6 +-
 .../cloudflare-tunnel/get-started/index.mdx   |    3 +-
 .../connectors/cloudflare-tunnel/index.mdx    |    4 +-
 .../monitor-tunnels/index.mdx                 |    3 +-
 .../monitor-tunnels/notifications.mdx         |    3 +-
 .../private-net/cloudflared/connect-cidr.mdx  |   14 +-
 .../private-net/cloudflared/index.mdx         |    3 +-
 .../private-net/cloudflared/private-dns.mdx   |   23 +-
 .../routing-to-tunnel/dns.mdx                 |   13 +-
 .../routing-to-tunnel/protocols.mdx           |   14 +-
 .../public-load-balancers.mdx                 |   41 +-
 .../troubleshoot-tunnels/common-errors.mdx    |    1 -
 .../troubleshoot-tunnels/diag-logs.mdx        |   59 +-
 .../troubleshoot-tunnels/index.mdx            |    2 +-
 .../cloudflare-tunnel/use-cases/index.mdx     |    9 +-
 .../cloudflare-tunnel/use-cases/rdp/index.mdx |    2 +-
 .../use-cases/rdp/rdp-device-client.mdx       |    2 +-
 .../use-cases/vnc-browser-rendering.mdx       |  214 ++--
 .../cloudflare-wan/analytics/index.mdx        |   23 +-
 .../analytics/netflow-analytics.mdx           |    9 +-
 .../analytics/network-analytics.mdx           |    5 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 .../analytics/site-analytics.mdx              |   16 +-
 .../configure-hardware-appliance/index.mdx    |   84 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/configure-virtual-appliance.mdx |   80 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |   11 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../maintenance/deactivate-appliance.mdx      |    1 -
 .../appliance/maintenance/heartbeat.mdx       |    1 -
 .../appliance/maintenance/index.mdx           |    3 +-
 .../maintenance/interrupt-service-window.mdx  |    1 -
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   18 +-
 .../application-based-policies/index.mdx      |   14 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    5 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   14 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../configuration/appliance/reference.mdx     |   33 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../check-tunnel-health-dashboard.mdx         |   11 +-
 .../configure-tunnel-health-alerts.mdx        |    6 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |   12 +-
 .../update-tunnel-health-checks-frequency.mdx |    3 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   34 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   45 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |   11 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../third-party/alibaba-cloud.mdx             |   19 +-
 .../third-party/aruba-edgeconnect.mdx         |   15 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   22 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   22 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    5 +-
 .../third-party/cisco-meraki-static.mdx       |   30 +-
 .../configuration/third-party/fitelnet.mdx    |   19 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   16 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   19 +-
 .../configuration/third-party/oracle.mdx      |   16 +-
 .../configuration/third-party/palo-alto.mdx   |   19 +-
 .../configuration/third-party/pfsense.mdx     |   19 +-
 .../configuration/third-party/sonicwall.mdx   |   22 +-
 .../third-party/sophos-firewall.mdx           |   22 +-
 .../configuration/third-party/strongswan.mdx  |   13 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   13 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../connectors/cloudflare-wan/get-started.mdx |   21 +-
 .../connectors/cloudflare-wan/index.mdx       |   20 +-
 .../cloudflare-wan/legal/3rdparty.mdx         |    1 -
 .../connectors/cloudflare-wan/legal/index.mdx |    3 +-
 .../cloudflare-wan/network-interconnect.mdx   |   17 +-
 .../connectors/cloudflare-wan/on-ramps.mdx    |   20 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    3 +-
 .../reference/device-compatibility.mdx        |   76 +-
 .../reference/gre-ipsec-tunnels.mdx           |   10 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |   10 +-
 .../cloudflare-wan/reference/index.mdx        |    3 +-
 .../cloudflare-wan/reference/mtu-mss.mdx      |    2 +-
 .../reference/traffic-steering.mdx            |   28 +-
 .../reference/tunnel-health-checks.mdx        |   12 +-
 .../connectors/cloudflare-wan/security.mdx    |    9 +-
 .../troubleshooting/connectivity.mdx          |   15 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   17 +-
 .../troubleshooting/routing-and-bgp.mdx       |   24 +-
 .../troubleshooting/tunnel-health.mdx         |   33 +-
 .../cloudflare-wan/wan-transformation.mdx     |   12 +-
 .../zero-trust/cloudflare-gateway.mdx         |   45 +-
 .../zero-trust/cloudflare-one-client.mdx      |   24 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   15 +-
 .../cloudflare-wan/zero-trust/index.mdx       |    1 -
 .../zero-trust/security-services.mdx          |    9 +-
 .../connectors/granular-permissions.mdx       |    2 +-
 .../networks/connectors/index.mdx             |    3 +-
 .../networks/routes/add-routes.mdx            |   20 +-
 .../networks/routes/reserved-ips.mdx          |    4 +-
 .../networks/virtual-networks.mdx             |   12 +-
 .../accessibility.mdx                         |    2 +-
 .../remote-browser-isolation/index.mdx        |    2 -
 .../known-limitations.mdx                     |    5 +-
 .../network-dependencies.mdx                  |    4 +-
 .../remote-browser-isolation/setup/index.mdx  |   14 +-
 .../custom-pages/gateway-block-page.mdx       |    2 +-
 .../custom-pages/index.mdx                    |    2 +-
 .../client-checks/antivirus.mdx               |   31 +-
 .../client-checks/application-check.mdx       |    4 +-
 .../client-checks/file-check.mdx              |    3 +-
 .../posture-checks/client-checks/firewall.mdx |   11 +-
 .../posture-checks/client-checks/index.mdx    |   41 +-
 .../client-checks/os-version.mdx              |    3 +-
 .../client-checks/require-warp.mdx            |    2 +-
 .../reusable-components/tags.mdx              |    1 -
 .../configure/modes/index.mdx                 |    4 +-
 .../troubleshooting/common-issues.mdx         |   15 +
 .../troubleshooting/connectivity-status.mdx   |   36 +-
 .../troubleshooting/diagnostic-logs.mdx       |  184 +--
 .../devices/device-registration.mdx           |   35 +-
 .../devices/user-side-certificates/index.mdx  |   10 +-
 .../manual-deployment.mdx                     |  218 ++--
 .../team-and-resources/users/risk-score.mdx   |   19 +-
 .../team-and-resources/users/scim.mdx         |    3 +-
 .../team-and-resources/users/users.mdx        |   10 +-
 .../traffic-policies/global-policies.mdx      |   18 +-
 .../network-policies/protocol-detection.mdx   |   18 +-
 .../best-practices/magic-transit-egress.mdx   |    6 +-
 .../tiered-policies/index.mdx                 |   12 +-
 .../tiered-policies/tenant-api.mdx            |    1 -
 .../cloudflare-one/troubleshooting/access.mdx |    2 +-
 .../troubleshooting/browser-isolation.mdx     |    2 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    2 +-
 .../troubleshooting/contact-support.mdx       |    4 +
 .../cloudflare-one/troubleshooting/dex.mdx    |    2 +-
 .../troubleshooting/email-security.mdx        |    2 +-
 .../troubleshooting/gateway.mdx               |    2 +-
 .../cloudflare-one/troubleshooting/tunnel.mdx |   33 +-
 .../troubleshooting/wan/connectivity.mdx      |   17 +-
 .../troubleshooting/wan/index.mdx             |    2 +-
 .../troubleshooting/wan/ipsec.mdx             |   19 +-
 .../troubleshooting/wan/routing-bgp.mdx       |   26 +-
 .../troubleshooting/wan/tunnel-health.mdx     |   35 +-
 .../troubleshooting/warp-client.mdx           |    2 +-
 .../tutorials/entra-id-risky-users.mdx        |   40 +-
 .../docs/cloudflare-wan/analytics/index.mdx   |    7 +-
 .../analytics/netflow-analytics.mdx           |    5 +-
 .../analytics/network-analytics.mdx           |    7 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    6 +-
 .../analytics/query-tunnel-health.mdx         |    9 +-
 .../analytics/site-analytics.mdx              |   19 +-
 src/content/docs/cloudflare-wan/changelog.mdx |    7 +-
 .../configure-hardware-appliance/index.mdx    |   79 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |    9 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../appliance/maintenance/index.mdx           |    5 +-
 .../maintenance/register-appliance.mdx        |    2 +-
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   27 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-options.mdx     |   42 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    7 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   11 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |    8 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   25 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   32 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |    7 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../configuration/multi-cloud-networking.mdx  |    3 +-
 .../third-party/alibaba-cloud.mdx             |   20 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   21 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   21 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    6 +-
 .../third-party/cisco-meraki-static.mdx       |   21 +-
 .../configuration/third-party/fitelnet.mdx    |   20 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   17 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   18 +-
 .../configuration/third-party/oracle.mdx      |   17 +-
 .../configuration/third-party/palo-alto.mdx   |   18 +-
 .../configuration/third-party/pfsense.mdx     |   20 +-
 .../configuration/third-party/sonicwall.mdx   |   23 +-
 .../third-party/sophos-firewall.mdx           |   23 +-
 .../configuration/third-party/strongswan.mdx  |   14 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   14 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../docs/cloudflare-wan/get-started.mdx       |   11 +-
 src/content/docs/cloudflare-wan/glossary.mdx  |    3 +-
 src/content/docs/cloudflare-wan/index.mdx     |    5 +-
 .../docs/cloudflare-wan/legal/3rdparty.mdx    |    3 +-
 .../docs/cloudflare-wan/legal/index.mdx       |    5 +-
 .../cloudflare-wan/network-interconnect.mdx   |   16 +-
 src/content/docs/cloudflare-wan/on-ramps.mdx  |    4 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    4 +-
 .../reference/device-compatibility.mdx        |   58 +-
 .../reference/gre-ipsec-tunnels.mdx           |    4 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/cloudflare-wan/reference/index.mdx   |    5 +-
 .../docs/cloudflare-wan/reference/mtu-mss.mdx |    6 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    9 +-
 .../reference/virtual-networks.mdx            |    9 +-
 src/content/docs/cloudflare-wan/security.mdx  |    8 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   10 +-
 .../troubleshooting/routing-and-bgp.mdx       |   22 +-
 .../troubleshooting/tunnel-health.mdx         |   30 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   12 +-
 .../zero-trust/connectivity-options.mdx       |   19 +-
 .../docs/cloudflare-wan/zero-trust/index.mdx  |    4 +-
 .../docs/constellation/platform/index.mdx     |    2 +-
 src/content/docs/containers/examples/cron.mdx |   41 +-
 .../examples/durable-object-interface.mdx     |    1 -
 .../docs/containers/examples/index.mdx        |    1 -
 .../containers/platform-details/placement.mdx |    8 +-
 src/content/docs/containers/pricing.mdx       |    2 +-
 src/content/docs/containers/ssh.mdx           |    2 +-
 .../d1/best-practices/local-development.mdx   |    2 -
 .../docs/d1/best-practices/query-d1.mdx       |   50 +-
 .../d1/best-practices/remote-development.mdx  |   15 +-
 .../docs/d1/best-practices/retry-queries.mdx  |   26 +-
 .../d1/best-practices/use-d1-from-pages.mdx   |    2 +-
 .../docs/d1/best-practices/use-indexes.mdx    |   26 +-
 .../docs/d1/configuration/environments.mdx    |   60 +-
 src/content/docs/d1/get-started.mdx           |   12 +-
 src/content/docs/d1/observability/billing.mdx |    4 +-
 src/content/docs/d1/platform/limits.mdx       |   34 +-
 .../docs/d1/reference/community-projects.mdx  |   40 +-
 .../docs/d1/reference/data-security.mdx       |    6 +-
 src/content/docs/d1/reference/faq.mdx         |    4 +-
 .../docs/d1/reference/generated-columns.mdx   |   24 +-
 src/content/docs/d1/reference/glossary.mdx    |    2 +-
 src/content/docs/d1/reference/migrations.mdx  |    6 +-
 src/content/docs/d1/sql-api/foreign-keys.mdx  |   28 +-
 src/content/docs/d1/sql-api/query-json.mdx    |   82 +-
 .../tutorials/build-an-api-to-access-d1.mdx   |    8 +-
 .../docs/d1/tutorials/d1-and-prisma-orm.mdx   |    2 +-
 .../docs/data-localization/compatibility.mdx  |   68 +-
 .../data-localization/geo-key-manager.mdx     |    5 +-
 .../docs/ddos-protection/about/components.mdx |    3 +-
 .../about/how-ddos-protection-works.mdx       |   17 +-
 .../docs/ddos-protection/about/index.mdx      |    5 +-
 .../api/dns-protection/index.mdx              |   17 +-
 .../api/dns-protection/json-objects.mdx       |   21 +-
 .../advanced-ddos-systems/api/index.mdx       |    3 +-
 .../programmable-flow-protection/examples.mdx |  209 ++-
 .../programmable-flow-protection/index.mdx    |   37 +-
 .../json-objects.mdx                          |   61 +-
 .../api/tcp-protection/examples.mdx           |  217 ++--
 .../api/tcp-protection/index.mdx              |  103 +-
 .../api/tcp-protection/json-objects.mdx       |   51 +-
 .../how-to/add-prefix.mdx                     |    6 +-
 .../how-to/exclude-prefix.mdx                 |    5 +-
 .../advanced-ddos-systems/how-to/index.mdx    |    5 +-
 .../advanced-ddos-systems/index.mdx           |    4 +-
 .../advanced-ddos-systems/overview/index.mdx  |   16 +-
 .../overview/programmable-flow-protection.mdx |   92 +-
 .../advanced-ddos-systems/troubleshooting.mdx |   13 +-
 .../ddos-protection/best-practices/index.mdx  |    3 +-
 .../best-practices/proactive-defense.mdx      |    4 +-
 .../best-practices/third-party.mdx            |    2 +-
 .../ddos-protection/botnet-threat-feed.mdx    |   58 +-
 .../docs/ddos-protection/get-started.mdx      |    3 +-
 .../managed-rulesets/http/index.mdx           |    2 +-
 .../managed-rulesets/index.mdx                |    1 -
 .../managed-rulesets/network/index.mdx        |    2 +-
 .../network-overrides/override-examples.mdx   |   12 +-
 .../docs/ddos-protection/reference/alerts.mdx |    2 +-
 .../docs/ddos-protection/reference/index.mdx  |    3 +-
 .../docs/ddos-protection/reference/logs.mdx   |    3 +-
 .../reference/simulate-ddos-attack.mdx        |    3 +-
 src/content/docs/dmarc-management/enable.mdx  |    3 +-
 .../dmarc-management/security-records.mdx     |    2 +-
 .../docs/dmarc-management/statistics.mdx      |    1 -
 .../docs/dns/additional-options/index.mdx     |    2 +-
 src/content/docs/dns/changelog.mdx            |    8 +-
 .../docs/dns/cname-flattening/index.mdx       |    2 +-
 .../set-up-cname-flattening.mdx               |    8 +-
 .../random-prefix-attacks/setup.mdx           |   11 +-
 src/content/docs/dns/dnssec/dnssec-states.mdx |   13 +-
 src/content/docs/dns/dnssec/enable-nsec3.mdx  |    4 +-
 src/content/docs/dns/dnssec/index.mdx         |   19 +-
 .../dns/dnssec/multi-signer-dnssec/about.mdx  |    4 +-
 .../dns/dnssec/multi-signer-dnssec/setup.mdx  |    2 +-
 .../dnssec/validation-and-key-management.mdx  |    8 +-
 .../docs/dns/foundation-dns/dnssec-keys.mdx   |    3 +-
 src/content/docs/dns/foundation-dns/index.mdx |   23 +-
 src/content/docs/dns/glossary.mdx             |    2 +-
 .../docs/dns/internal-dns/analytics.mdx       |    2 +-
 .../how-to/create-subdomain.mdx               |    3 +-
 .../how-to/email-records.mdx                  |   15 +-
 .../dns/manage-dns-records/how-to/index.mdx   |    3 +-
 .../how-to/managing-dynamic-ip-addresses.mdx  |    3 +-
 .../how-to/round-robin-dns.mdx                |    1 -
 .../how-to/subdomains-outside-cloudflare.mdx  |   17 +-
 .../manage-dns-records/reference/index.mdx    |    3 +-
 .../reference/record-attributes.mdx           |   17 +-
 .../dns/manage-dns-records/reference/ttl.mdx  |    3 +-
 .../troubleshooting/exposed-ip-address.mdx    |    3 +-
 .../troubleshooting/index.mdx                 |    5 +-
 .../dns/nameservers/advanced-nameservers.mdx  |    1 -
 .../zone-custom-nameservers.mdx               |    1 +
 .../docs/dns/private-origins/index.mdx        |    3 +-
 .../docs/dns/reference/all-features.mdx       |    3 +-
 .../dns/reference/analytics-mcp-server.mdx    |    3 +-
 .../docs/dns/reference/best-practices.mdx     |    3 +-
 .../docs/dns/reference/domain-connect.mdx     |   18 +-
 src/content/docs/dns/reference/index.mdx      |    2 +-
 .../recommended-third-party-tools.mdx         |    9 +-
 .../docs/dns/troubleshooting/email-issues.mdx |   12 +-
 .../docs/dns/troubleshooting/index.mdx        |    9 +-
 .../conversions/convert-full-to-secondary.mdx |   34 +-
 .../conversions/convert-partial-to-full.mdx   |    2 +-
 .../dns/zone-setups/conversions/index.mdx     |    2 +-
 .../docs/dns/zone-setups/full-setup/index.mdx |    2 +-
 .../partial-setup/dns-resolution.mdx          |    7 +-
 .../dns/zone-setups/partial-setup/setup.mdx   |   11 +-
 .../zone-setups/reference/domain-status.mdx   |   10 +-
 .../docs/dns/zone-setups/reference/index.mdx  |    3 +-
 .../subdomain-setup/move-to-new-account.mdx   |    1 -
 .../zone-setups/subdomain-setup/rollback.mdx  |    5 +-
 .../subdomain-setup/setup/parent-on-full.mdx  |    3 -
 .../setup/parent-on-partial.mdx               |    3 +-
 .../dns/zone-setups/troubleshooting/index.mdx |    3 +-
 .../cloudflare-as-primary/index.mdx           |    2 +-
 .../transfer-criteria.mdx                     |    3 +-
 .../cloudflare-as-secondary/alerts.mdx        |    3 +-
 .../cloudflare-as-secondary/index.mdx         |    4 +-
 .../cloudflare-as-secondary/proxy-traffic.mdx |    2 +-
 .../docs/durable-objects/api/alarms.mdx       |   77 +-
 .../api/legacy-kv-storage-api.mdx             |   13 +-
 .../api/sqlite-storage-api.mdx                |   24 +-
 .../access-durable-objects-storage.mdx        |    3 +
 .../concepts/durable-object-lifecycle.mdx     |    2 +-
 .../docs/durable-objects/examples/agents.mdx  |    2 +-
 .../docs/durable-objects/examples/index.mdx   |    5 +-
 .../examples/websocket-server.mdx             |    8 +-
 .../observability/data-studio.mdx             |    2 +-
 .../durable-objects/platform/known-issues.mdx |    2 +-
 .../docs/durable-objects/platform/limits.mdx  |    1 -
 .../reference/data-location.mdx               |   16 +-
 .../reference/data-security.mdx               |    6 +-
 .../reference/environments.mdx                |    7 +-
 .../docs/durable-objects/reference/faq.mdx    |    6 +-
 .../durable-objects/reference/glossary.mdx    |    2 +-
 .../reference/in-memory-state.mdx             |   30 +-
 .../docs/durable-objects/video-tutorials.mdx  |   12 +-
 .../docs/dynamic-workers/usage/bindings.mdx   |  140 +-
 .../email-workers/local-development.mdx       |   95 +-
 .../email-workers/reply-email-workers.mdx     |   60 +-
 .../email-routing/get-started/audit-logs.mdx  |    8 +-
 .../docs/email-routing/get-started/index.mdx  |    2 +-
 .../docs/email-routing/graphql-example.mdx    |    2 +-
 src/content/docs/email-routing/limits.mdx     |    2 +-
 src/content/docs/email-routing/postmaster.mdx |    3 +-
 .../setup/email-routing-dns-records.mdx       |    8 +-
 .../docs/email-routing/setup/index.mdx        |    2 +-
 .../email-routing/troubleshooting/index.mdx   |    2 +-
 .../email-security/account-setup/index.mdx    |    2 +-
 .../gsuite-bcc-setup/create-project-gcp.mdx   |    4 +-
 .../deployment/inline/reference/index.mdx     |    2 +-
 .../deployment/inline/setup/index.mdx         |    2 +-
 .../domains-and-routing/alert-webhooks.mdx    |   10 +-
 .../domains-and-routing/index.mdx             |    2 +-
 .../email-policies/index.mdx                  |    2 +-
 .../enhanced-detections/index.mdx             |    2 +-
 .../email-configuration/lists/index.mdx       |    2 +-
 .../migrate-to-email-security.mdx             |   26 +-
 .../docs/email-security/reference/index.mdx   |    2 +-
 src/content/docs/email-service/api/index.mdx  |    2 +-
 .../api/route-emails/email-handler.mdx        |    2 +-
 .../email-service/api/route-emails/index.mdx  |    2 +-
 .../api/send-emails/rest-api.mdx              |   52 +-
 .../api/send-emails/workers-api.mdx           |   40 +-
 .../docs/email-service/concepts/index.mdx     |    2 +-
 .../email-service/configuration/index.mdx     |    2 +-
 .../email-routing/hard-bounce-handling.mdx    |  241 ++--
 .../examples/email-routing/spam-filtering.mdx |   33 +-
 .../email-service/get-started/send-emails.mdx |   34 +-
 .../email-service/local-development/index.mdx |    2 +-
 .../local-development/routing.mdx             |   44 +-
 .../docs/email-service/platform/index.mdx     |    2 +-
 .../docs/email-service/platform/pricing.mdx   |    8 +-
 .../docs/email-service/reference/index.mdx    |    5 +-
 .../email-service/reference/postmaster.mdx    |    1 -
 .../docs/firewall/api/cf-filters/delete.mdx   |   38 +-
 .../docs/firewall/api/cf-filters/get.mdx      |  100 +-
 .../docs/firewall/api/cf-filters/post.mdx     |   68 +-
 .../docs/firewall/api/cf-filters/put.mdx      |   52 +-
 .../firewall/api/cf-filters/validation.mdx    |   34 +-
 .../api/cf-filters/what-is-a-filter.mdx       |   10 +-
 .../firewall/api/cf-firewall-rules/get.mdx    |  160 +--
 .../firewall/api/cf-firewall-rules/post.mdx   |  116 +-
 .../cf-firewall-rules/order-priority.mdx      |    1 -
 .../account-security/cloudflare-access.mdx    |    4 +-
 .../account/account-security/index.mdx        |    2 +-
 .../leaked-password-notifications.mdx         |    2 -
 .../manage-active-sessions.mdx                |    2 +-
 .../account/account-security/zone-holds.mdx   |    4 +-
 .../fundamentals/account/create-account.mdx   |   11 +-
 .../account/find-account-and-zone-ids.mdx     |   12 +-
 .../docs/fundamentals/account/index.mdx       |    2 +-
 .../api/how-to/control-api-access.mdx         |    6 +-
 .../api/how-to/create-via-api.mdx             |   32 +-
 .../api/how-to/restrict-tokens.mdx            |    7 +-
 src/content/docs/fundamentals/api/index.mdx   |    2 +-
 .../docs/fundamentals/api/reference/index.mdx |    2 +-
 .../fundamentals/api/reference/limits.mdx     |    6 +-
 .../docs/fundamentals/api/troubleshooting.mdx |   18 +-
 .../concepts/how-cloudflare-works.mdx         |    8 +-
 .../docs/fundamentals/concepts/index.mdx      |    2 +-
 .../concepts/traffic-flow-cloudflare.mdx      |   22 +-
 src/content/docs/fundamentals/index.mdx       |    4 +-
 .../fundamentals/manage-domains/add-site.mdx  |   11 +-
 .../manage-domains/domain-version.mdx         |   12 +-
 .../manage-domains/move-domain.mdx            |    2 -
 .../manage-domains/pause-cloudflare.mdx       |    4 +-
 .../fundamentals/manage-members/index.mdx     |    2 +-
 .../fundamentals/manage-members/policies.mdx  |    5 +-
 .../fundamentals/manage-members/roles.mdx     |    2 +-
 .../fundamentals/manage-members/scope.mdx     |   52 +-
 .../manage-members/user-groups.mdx            |   23 +-
 .../docs/fundamentals/new-features/index.mdx  |    4 +-
 .../organizations/limitations.mdx             |    4 +-
 .../docs/fundamentals/organizations/setup.mdx |   16 +-
 .../fundamentals/performance/improve-seo.mdx  |   16 +-
 .../docs/fundamentals/performance/index.mdx   |    2 +-
 .../fundamentals/performance/test-speed.mdx   |   16 +-
 .../fundamentals/reference/best-practices.mdx |    6 +-
 .../reference/cdn-cgi-endpoint.mdx            |   12 +-
 .../reference/cloudflare-ray-id.mdx           |    3 +-
 .../reference/connection-limits.mdx           |   22 +-
 .../reference/cryptographic-personhood.mdx    |   44 +-
 .../docs/fundamentals/reference/glossary.mdx  |    2 +-
 .../reference/google-analytics.mdx            |    4 -
 .../docs/fundamentals/reference/index.mdx     |    2 +-
 .../scim-virtual-groups-migration.mdx         |   17 +-
 .../docs/fundamentals/reference/partners.mdx  |    2 +-
 .../delivering-videos-with-cloudflare.mdx     |   18 +-
 .../reference/policies-compliances/index.mdx  |    2 +-
 .../docs/fundamentals/reference/redirects.mdx |    2 +-
 .../report-abuse/abuse-report-obligations.mdx |    6 +-
 .../report-abuse/complaint-types.mdx          |   26 +-
 .../reference/report-abuse/index.mdx          |    8 +-
 .../reference/report-abuse/submit-report.mdx  |   12 +-
 .../sdk-ecosystem-support-policy.mdx          |   14 +-
 .../reference/tcp-connections.mdx             |    4 +-
 .../reference/troubleshooting.mdx             |   44 +-
 .../docs/fundamentals/security/index.mdx      |    2 +-
 .../docs/fundamentals/security/pci-scans.mdx  |    6 +-
 .../security/under-ddos-attack.mdx            |    8 +-
 .../docs/fundamentals/user-profiles/2fa.mdx   |   34 +-
 .../user-profiles/account-recovery.mdx        |   10 +-
 .../change-password-or-email.mdx              |    2 +-
 .../user-profiles/customize-account.mdx       |    6 +-
 .../user-profiles/delete-account.mdx          |    5 +-
 .../docs/fundamentals/user-profiles/login.mdx |    7 +-
 .../multi-factor-email-authentication.mdx     |    6 +-
 .../user-profiles/verify-email-address.mdx    |    6 +-
 src/content/docs/google-tag-gateway/index.mdx |    6 +-
 .../concepts/health-checks-regions.mdx        |    1 -
 .../docs/health-checks/concepts/index.mdx     |    3 +-
 .../health-checks/health-checks-analytics.mdx |    3 +-
 .../how-to/health-checks-notifications.mdx    |    5 +-
 .../docs/health-checks/how-to/index.mdx       |    3 +-
 .../health-checks/how-to/zone-lockdown.mdx    |    3 +-
 .../drizzle-orm.mdx                           |    4 +-
 .../prisma-postgres.mdx                       |   15 +-
 .../postgres-database-providers/supabase.mdx  |    2 +-
 .../observability/troubleshooting.mdx         |   78 +-
 .../docs/hyperdrive/platform/limits.mdx       |   28 +-
 .../hyperdrive/platform/storage-options.mdx   |    2 +-
 .../reference/wrangler-commands.mdx           |    2 +-
 .../docs/hyperdrive/tutorials/index.mdx       |    2 +-
 ...rverless-timeseries-api-with-timescale.mdx |    2 +-
 .../optimization/make-responsive-images.mdx   |   17 +-
 .../optimization/transformations/flows.mdx    |   19 +-
 .../optimization/transformations/overview.mdx |    3 +-
 .../docs/key-transparency/api/epochs.mdx      |    2 +-
 .../docs/key-transparency/api/index.mdx       |    4 +-
 .../docs/key-transparency/api/namespaces.mdx  |    8 +-
 .../docs/kv/api/delete-key-value-pairs.mdx    |   37 +-
 src/content/docs/kv/concepts/kv-bindings.mdx  |   32 +-
 .../docs/kv/concepts/kv-namespaces.mdx        |   17 +-
 src/content/docs/kv/get-started.mdx           |   15 +-
 src/content/docs/kv/glossary.mdx              |    2 +-
 src/content/docs/kv/observability/index.mdx   |    2 +-
 .../kv/observability/metrics-analytics.mdx    |    1 +
 src/content/docs/kv/platform/pricing.mdx      |    2 +-
 .../docs/kv/reference/data-security.mdx       |    6 +-
 .../docs/kv/reference/environments.mdx        |    2 -
 src/content/docs/kv/reference/kv-commands.mdx |    4 +-
 .../account-security/audit-logs.mdx           |    2 +-
 .../account-security/index.mdx                |    6 +-
 .../review-active-sessions.mdx                |    2 +-
 .../account-security/review-audit-logs.mdx    |    2 +-
 .../account-security/set-up-2fa.mdx           |    4 +-
 .../browser-integrity.mdx                     |    2 +-
 .../default-traffic-security/ddos.mdx         |    4 +-
 .../default-traffic-security/dnssec.mdx       |    2 +-
 .../default-traffic-security/index.mdx        |    2 +-
 .../default-traffic-security/mtls.mdx         |    2 +-
 .../application-security/firewall/index.mdx   |    4 +-
 .../lists/configuration.mdx                   |    2 +-
 .../application-security/lists/features.mdx   |    2 +-
 .../application-security/lists/index.mdx      |    8 +-
 .../application-security/lists/use-cases.mdx  |    2 +-
 .../rate-limiting/configurations.mdx          |   16 +-
 .../rate-limiting/features.mdx                |    2 +-
 .../rate-limiting/index.mdx                   |    4 +-
 .../rate-limiting/use-cases.mdx               |    2 +-
 .../security-center/brand-protection.mdx      |    2 +-
 .../security-center/index.mdx                 |    6 +-
 .../access-application/index.mdx              |    8 +-
 .../advanced-workflows/index.mdx              |    8 +-
 .../alternative-onramps/clientless-rbi.mdx    |    6 +-
 .../alternative-onramps/index.mdx             |    4 +-
 .../clientless-access/concepts/index.mdx      |    2 +-
 .../concepts/what-is-clientless-access.mdx    |    2 +-
 .../best-practices.mdx                        |    6 +-
 .../create-tunnel.mdx                         |   11 +-
 .../connect-private-applications/index.mdx    |    4 +-
 .../customize-ux/app-launcher.mdx             |    2 +-
 .../customize-ux/block-page.mdx               |    2 +-
 .../customize-ux/bookmarks.mdx                |    2 +-
 .../clientless-access/customize-ux/index.mdx  |    8 +-
 .../customize-ux/login-page.mdx               |    2 +-
 .../clientless-access/customize-ux/tags.mdx   |    2 +-
 .../clientless-access/initial-setup/index.mdx |    8 +-
 .../migrate-applications/best-practices.mdx   |   14 +-
 .../migrate-applications/index.mdx            |    6 +-
 .../migrate-applications/integrated-sso.mdx   |   12 +-
 .../clientless-access/terraform/index.mdx     |    2 +-
 .../create-zero-trust-org.mdx                 |    2 +-
 .../cybersafe/account-creation/index.mdx      |    6 +-
 .../cybersafe/concepts/index.mdx              |    8 +-
 .../concepts/what-is-dns-filtering.mdx        |   18 +-
 .../gateway-verify-local-connectivity.mdx     |    8 +-
 .../advertise-prefixes.mdx                    |    2 +-
 .../data-center-protection/concepts/index.mdx |    2 +-
 .../data-center-protection/configure-ddos.mdx |   14 +-
 .../configure-routes.mdx                      |   18 +-
 .../configure-tunnels.mdx                     |   29 +-
 .../configure-tunnels-routes/index.mdx        |    2 +-
 .../enable-notifications.mdx                  |    5 +-
 .../data-center-protection/get-started.mdx    |    8 +-
 .../run-pre-flight-checks.mdx                 |    1 +
 .../dns-best-practices/concepts/index.mdx     |    8 +-
 .../dns-best-practices/concepts/phase-1.mdx   |   52 +-
 .../dns-best-practices/concepts/phase-2.mdx   |   42 +-
 .../dns-best-practices/concepts/phase-3.mdx   |   31 +-
 .../dns-best-practices/concepts/phase-4.mdx   |   38 +-
 .../concepts/summary-considerations.mdx       |   20 +-
 .../holistic-ai-security/appendix/index.mdx   |    1 -
 .../holistic-ai-security/concepts/index.mdx   |    1 -
 .../holistic-ai-security/concepts/mcp.mdx     |    1 -
 .../concepts/shadow-ai.mdx                    |    1 -
 .../get-started/additional-setup.mdx          |    2 +-
 .../get-started/define-ai-risk-tolerance.mdx  |    1 +
 .../get-started/index.mdx                     |    2 +-
 .../monitor-ai-use/index.mdx                  |    1 -
 .../monitor-prompts-responses.mdx             |    3 +-
 .../monitor-ai-use/review-inline-ai-use.mdx   |    3 +-
 .../load-balancing/concepts/health-checks.mdx |    2 +-
 .../load-balancing/concepts/index.mdx         |    8 +-
 .../concepts/load-balancer-components.mdx     |   12 +-
 .../load-balancing/concepts/routing.mdx       |    8 +-
 .../load-balancing/planning/custom-rules.mdx  |    2 +-
 .../load-balancing/planning/index.mdx         |    8 +-
 .../planning/multiple-zones.mdx               |    2 -
 .../planning/origin-steering-policies.mdx     |    6 +-
 .../planning/session-affinity.mdx             |    2 +-
 .../planning/traffic-steering.mdx             |    4 +-
 .../planning/types-load-balancers.mdx         |   16 +-
 .../setup/check-pool-health.mdx               |    2 +-
 .../setup/hostname-preparation.mdx            |    8 +-
 .../load-balancing/setup/index.mdx            |   14 +-
 .../load-balancing/setup/next-steps.mdx       |    2 +-
 .../setup/production-traffic.mdx              |    2 +-
 .../mtls/concepts/mtls-cloudflare.mdx         |   12 +-
 .../mtls/mtls-implementation/index.mdx        |    2 +-
 .../advanced/improve-analytics.mdx            |    2 +-
 .../prevent-ddos-attacks/advanced/index.mdx   |    8 +-
 .../prevent-ddos-attacks/baseline/index.mdx   |    6 +-
 .../baseline/proxy-dns-records.mdx            |    2 +-
 .../baseline/set-up-alerts.mdx                |    2 +-
 .../baseline/tls-versions.mdx                 |    4 +-
 .../prevent-ddos-attacks/concepts/index.mdx   |    4 +-
 .../replace-vpn/build-policies/index.mdx      |    8 +-
 .../build-policies/policy-design.mdx          |   10 +-
 .../build-policies/session-timeouts.mdx       |    2 +-
 .../test-your-first-application.mdx           |    7 +-
 .../replace-vpn/concepts/index.mdx            |    6 +-
 .../concepts/what-is-cloudflare.mdx           |    2 +-
 .../connect-private-network/cloudflared.mdx   |   19 +-
 .../connection-methods.mdx                    |   22 +-
 .../connect-private-network/index.mdx         |    6 +-
 .../overlapping-ips.mdx                       |    2 +-
 .../tunnel-capacity.mdx                       |    2 +-
 .../replace-vpn/get-started/prerequisites.mdx |    8 +-
 .../replace-vpn/troubleshooting/index.mdx     |    4 +-
 .../troubleshoot-private-networks.mdx         |    2 +-
 .../build-dns-policies/index.mdx              |    6 +-
 .../build-egress-policies/index.mdx           |    8 +-
 .../build-http-policies/index.mdx             |    8 +-
 .../concepts/index.mdx                        |    4 +-
 .../choose-on-ramp.mdx                        |   12 +-
 .../initial-setup/prerequisites.mdx           |    4 +-
 .../secure-saas-applications/index.mdx        |    6 +-
 .../sso-front-door.mdx                        |   10 +-
 .../understand-policies/index.mdx             |    6 +-
 .../understand-policies/indicator-feeds.mdx   |    4 +-
 .../order-of-enforcement.mdx                  |    2 +-
 .../secure-your-email/concepts/index.mdx      |    2 +-
 .../protect-from-phishing-attacks.mdx         |    2 +-
 .../concepts/what-is-cloudflare.mdx           |    4 +-
 .../concepts/what-is-email-security.mdx       |    2 +-
 .../concepts/what-is-phishing-attack.mdx      |    2 +-
 .../active-directory-sync.mdx                 |    2 +-
 .../configure-email-security/audit-logs.mdx   |    3 +-
 .../impersonation-registry.mdx                |    2 +-
 .../configure-email-security/index.mdx        |    2 +-
 .../configure-email-security/report-phish.mdx |    2 +-
 .../enable-auto-moves/index.mdx               |    2 +-
 .../get-started/deployment-models.mdx         |    4 +-
 .../get-started/prerequisites.mdx             |    2 +-
 .../recommended-deployment-model.mdx          |    2 +-
 .../get-started/setup-google-workspace.mdx    |    2 +-
 .../get-started/setup-ms-graph-api.mdx        |    4 +-
 .../monitor-your-inbox/phish-submissions.mdx  |    2 +-
 .../surge-readiness/concepts/index.mdx        |   12 +-
 .../surge-readiness/performance/analytics.mdx |    4 +-
 .../surge-readiness/performance/caching.mdx   |   22 +-
 .../surge-readiness/performance/index.mdx     |    2 +-
 .../surge-readiness/performance/logs.mdx      |    7 +-
 .../security/block-agents-lock-zones.mdx      |    1 -
 .../security/confirm-account-security.mdx     |    2 +-
 .../security/control-domain-access.mdx        |   12 +-
 .../surge-readiness/security/enable-iaum.mdx  |    4 +-
 .../surge-readiness/security/index.mdx        |    2 +-
 .../surge-readiness/support/index.mdx         |    2 +-
 .../surge-readiness/support/resources.mdx     |   15 +-
 .../workers/concepts/cloudflare-intro.mdx     |   30 +-
 .../learning-paths/workers/concepts/index.mdx |    6 +-
 .../workers/concepts/serverless-computing.mdx |    6 +-
 .../learning-paths/workers/devplat/index.mdx  |    4 +-
 .../workers/devplat/intro-to-devplat.mdx      |    2 +-
 .../workers/get-started/c3-and-wrangler.mdx   |    8 +-
 .../workers/get-started/first-application.mdx |   23 +-
 .../workers/get-started/index.mdx             |    6 +-
 .../additional-dns-records.mdx                |    5 +-
 .../additional-options/cloudflare-tunnel.mdx  |    1 -
 .../additional-options/index.mdx              |   13 +-
 .../load-balancing-china.mdx                  |    1 -
 .../load-balancing-rules/expressions.mdx      |   13 +-
 .../override-http-host-headers.mdx            |   30 +-
 .../pagerduty-integration.mdx                 |    1 -
 .../planned-maintenance.mdx                   |   12 +-
 .../docs/load-balancing/api-reference.mdx     |    1 -
 .../get-started/enable-load-balancing.mdx     |    3 +-
 .../docs/load-balancing/get-started/index.mdx |    5 +-
 .../load-balancers/common-configurations.mdx  |    7 +-
 .../docs/load-balancing/monitors/index.mdx    |    4 +-
 .../monitors/monitor-groups.mdx               |    1 -
 .../private-network/cloudflare-wan.mdx        |    6 +-
 .../reference-architecture-external-link.mdx  |    1 -
 .../docs/load-balancing/reference/index.mdx   |    3 +-
 .../load-balancing/reference/limitations.mdx  |   15 +-
 .../reference/migration-guides/index.mdx      |    3 +-
 .../troubleshooting/common-error-codes.mdx    |   53 +-
 .../load-balancing/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/load-balancing-faq.mdx    |   37 +-
 .../understand-basics/adaptive-routing.mdx    |    3 +-
 .../understand-basics/index.mdx               |    3 +-
 .../traffic-steering/index.mdx                |    1 -
 .../hash-origin-steering.mdx                  |    4 -
 .../least-outstanding-requests-pools.mdx      |    7 +-
 .../random-origin-steering.mdx                |    1 -
 .../steering-policies/dynamic-steering.mdx    |    1 -
 .../steering-policies/index.mdx               |    1 +
 .../least-outstanding-requests.mdx            |    3 +-
 .../steering-policies/proximity-steering.mdx  |    9 +-
 .../steering-policies/standard-options.mdx    |    1 -
 src/content/docs/log-explorer/api.mdx         |    6 +-
 src/content/docs/log-explorer/changelog.mdx   |    2 +-
 .../docs/log-explorer/example-queries.mdx     |    2 +-
 src/content/docs/log-explorer/index.mdx       |   42 +-
 .../docs/logs/auditlogs-mcp-server.mdx        |    2 +-
 .../docs/logs/changelog/audit-logs.mdx        |    2 +-
 src/content/docs/logs/changelog/index.mdx     |    2 +-
 src/content/docs/logs/changelog/logs.mdx      |    2 -
 .../docs/logs/faq/common-calculations.mdx     |    2 -
 src/content/docs/logs/faq/general-faq.mdx     |    3 -
 src/content/docs/logs/faq/instant-logs.mdx    |    3 -
 src/content/docs/logs/faq/logpull-api.mdx     |    5 -
 .../docs/logs/faq/worker-subrequests.mdx      |   14 +-
 src/content/docs/logs/glossary.mdx            |    2 +-
 src/content/docs/logs/logpull/index.mdx       |    4 +-
 .../docs/logs/logpull/requesting-logs.mdx     |   22 +-
 .../logs/logpull/understanding-the-basics.mdx |   24 +-
 src/content/docs/logs/logpush-mcp-server.mdx  |    2 +-
 .../examples/example-logpush-python.mdx       |    2 -
 .../docs/logs/logpush/examples/index.mdx      |    2 +-
 src/content/docs/logs/logpush/index.mdx       |    4 +-
 .../docs/logs/logpush/logpush-health.mdx      |   72 +-
 .../logpush/logpush-job/api-configuration.mdx |  140 +-
 .../logpush-job/datasets/account/index.mdx    |    2 +-
 .../logs/logpush/logpush-job/datasets/cmb.mdx |    4 +-
 .../logpush/logpush-job/datasets/index.mdx    |   16 +-
 .../logpush-job/datasets/zone/dns_logs.md     |    2 +-
 .../logpush-job/datasets/zone/index.mdx       |    2 +-
 .../logpush/logpush-job/edge-log-delivery.mdx |    3 +-
 .../enable-destinations/aws-s3.mdx            |    6 +-
 .../logpush-job/enable-destinations/azure.mdx |    1 +
 .../enable-destinations/egress-ip.mdx         |   26 +-
 .../enable-destinations/elastic.mdx           |   33 +-
 .../google-cloud-storage.mdx                  |    6 +-
 .../enable-destinations/ibm-qradar.mdx        |  150 ++-
 .../enable-destinations/kinesis.mdx           |    2 +-
 .../third-party/exabeam.mdx                   |    2 +-
 .../third-party/sekoia.mdx                    |    2 +-
 .../third-party/taegis.mdx                    |    2 +-
 .../docs/logs/logpush/logpush-job/filters.mdx |    5 +-
 .../docs/logs/logpush/logpush-job/index.mdx   |    2 +-
 .../logpush-ownership-challenge.mdx           |   22 +-
 .../2023-02-01-security-fields-updates.mdx    |   66 +-
 .../logs/reference/change-notices/index.mdx   |    2 +-
 .../logs/reference/clientrequestsource.mdx    |    3 -
 src/content/docs/logs/reference/index.mdx     |    2 +-
 .../docs/logs/reference/security-fields.mdx   |    8 +-
 .../docs/logs/reference/waf-fields.mdx        |    8 +-
 src/content/docs/magic-transit/about.mdx      |    3 +-
 src/content/docs/magic-transit/alerts.mdx     |    3 +-
 .../docs/magic-transit/analytics/index.mdx    |    9 +-
 .../analytics/network-analytics.mdx           |    6 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 src/content/docs/magic-transit/changelog.mdx  |    5 +-
 .../docs/magic-transit/cloudflare-ips.mdx     |   17 +-
 .../docs/magic-transit/get-started.mdx        |    8 +-
 src/content/docs/magic-transit/glossary.mdx   |    3 +-
 .../how-to/advertise-prefixes.mdx             |   56 +-
 .../magic-transit/how-to/configure-routes.mdx |   18 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   28 +-
 .../how-to/enable-magic-roles.mdx             |    2 +-
 .../docs/magic-transit/how-to/index.mdx       |    5 +-
 .../how-to/safely-withdraw-byoip-prefix.mdx   |    7 +-
 .../docs/magic-transit/network-flow.mdx       |    5 +-
 .../check-tunnel-health-dashboard.mdx         |   12 +-
 .../configure-tunnel-health-alerts.mdx        |    5 +-
 .../magic-transit/network-health/index.mdx    |   16 +-
 .../run-endpoint-health-checks.mdx            |   75 +-
 .../update-tunnel-health-checks-frequency.mdx |    7 +-
 .../magic-transit/network-interconnect.mdx    |    2 +-
 src/content/docs/magic-transit/on-demand.mdx  |    1 -
 .../docs/magic-transit/partners/index.mdx     |    5 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/gre-ipsec-tunnels.mdx           |    3 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/magic-transit/reference/index.mdx    |    5 +-
 .../docs/magic-transit/reference/mtu-mss.mdx  |    4 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    5 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../magic-transit/troubleshooting/index.mdx   |    2 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   12 +-
 .../troubleshooting/routing-and-bgp.mdx       |   21 +-
 .../troubleshooting/tunnel-health.mdx         |   29 +-
 src/content/docs/moq/feature-matrix.mdx       |  121 +-
 src/content/docs/moq/index.mdx                |   15 +-
 .../docs/multi-cloud-networking/changelog.mdx |    5 +-
 .../multi-cloud-networking/cloud-on-ramps.mdx |   11 +-
 .../multi-cloud-networking/get-started.mdx    |   74 +-
 .../manage-resources.mdx                      |    7 +-
 .../docs/multi-cloud-networking/reference.mdx |    1 -
 .../network-error-logging/get-started.mdx     |    3 +-
 .../docs/network-error-logging/how-to.mdx     |   11 +-
 .../docs/network-error-logging/index.mdx      |   45 +-
 src/content/docs/network-flow/api.mdx         |    5 +-
 src/content/docs/network-flow/changelog.mdx   |    5 +-
 .../docs/network-flow/cloud-flow-logs.mdx     |    2 +-
 src/content/docs/network-flow/faq.mdx         |    4 +-
 src/content/docs/network-flow/get-started.mdx |    2 +-
 src/content/docs/network-flow/glossary.mdx    |    3 +-
 .../magic-transit-integration.mdx             |    5 +-
 .../docs/network-flow/network-flow-free.mdx   |    2 +-
 .../docs/network-flow/routers/index.mdx       |    5 +-
 .../routers/netflow-ipfix-config.mdx          |    3 +-
 .../routers/recommended-sampling-rate.mdx     |    3 +-
 .../network-flow/routers/sflow-config.mdx     |    5 +-
 .../routers/supported-routers.mdx             |    5 +-
 src/content/docs/network-flow/rules/index.mdx |    1 -
 .../network-flow/rules/rule-notifications.mdx |    2 +-
 .../network-flow/rules/s-flow-ddos-attack.mdx |    2 +-
 .../network-flow/rules/static-threshold.mdx   |    2 +-
 .../tutorials/ddos-testing-guide.mdx          |    2 +-
 .../tutorials/encrypt-network-flow-data.mdx   |    5 +-
 .../tutorials/graphql-analytics.mdx           |    2 +-
 .../docs/network-flow/tutorials/index.mdx     |    5 +-
 .../docs/network-interconnect/changelog.mdx   |    5 +-
 .../docs/network-interconnect/get-started.mdx |   49 +-
 .../docs/network-interconnect/index.mdx       |   38 +-
 .../monitoring-and-alerts.mdx                 |   10 +-
 .../operational-guidance.mdx                  |    2 +-
 src/content/docs/network/index.mdx            |   36 +-
 src/content/docs/network/websockets.mdx       |    1 -
 .../get-started/configure-pagerduty.mdx       |   14 +-
 .../docs/notifications/get-started/index.mdx  |   27 +-
 src/content/docs/notifications/index.mdx      |    5 +-
 .../notifications/notification-available.mdx  |    2 +-
 .../notifications/notification-history.mdx    |    2 +-
 .../docs/notifications/reference/index.mdx    |    2 +-
 .../reference/traffic-alerts.mdx              |    2 +-
 src/content/docs/pages/configuration/api.mdx  |    1 +
 .../pages/configuration/build-caching.mdx     |   18 +-
 .../docs/pages/configuration/build-image.mdx  |    6 +-
 .../docs/pages/configuration/deploy-hooks.mdx |    1 +
 .../deploy-a-vite3-project.mdx                |    1 +
 .../docs/pages/functions/api-reference.mdx    |    8 -
 src/content/docs/pages/functions/bindings.mdx |   22 +-
 .../pages/functions/examples/ab-testing.mdx   |    1 -
 .../pages/functions/examples/cors-headers.mdx |    1 -
 .../docs/pages/functions/examples/index.mdx   |    1 -
 src/content/docs/pages/functions/metrics.mdx  |    1 +
 .../functions/plugins/community-plugins.mdx   |    1 -
 src/content/docs/pages/get-started/c3.mdx     |   23 -
 .../docs/pages/get-started/direct-upload.mdx  |    2 +-
 .../pages/get-started/git-integration.mdx     |    1 -
 src/content/docs/pages/get-started/index.mdx  |    1 -
 .../pages/how-to/add-custom-http-headers.mdx  |    1 -
 .../pages/how-to/build-commands-branches.mdx  |    2 +-
 .../pages/how-to/custom-branch-aliases.mdx    |    2 +-
 .../docs/pages/how-to/enable-zaraz.mdx        |    1 -
 src/content/docs/pages/how-to/index.mdx       |    2 -
 .../pages/how-to/npm-private-registry.mdx     |    1 -
 .../how-to/preview-with-cloudflare-tunnel.mdx |    1 -
 .../refactor-a-worker-to-pages-functions.mdx  |    1 -
 ...ect-upload-with-continuous-integration.mdx |    4 +-
 .../use-worker-for-ab-testing-in-pages.mdx    |    2 +-
 .../docs/pages/how-to/web-analytics.mdx       |    2 +-
 src/content/docs/pages/migrations/index.mdx   |    2 -
 src/content/docs/pages/platform/index.mdx     |    1 -
 .../docs/pages/platform/known-issues.mdx      |    3 +-
 src/content/docs/pages/platform/limits.mdx    |    7 +-
 .../add-a-react-form-with-formspree.mdx       |    2 +-
 .../build-a-blog-using-nuxt-and-sanity.mdx    |    1 +
 .../pipelines/reference/wrangler-commands.mdx |    3 +-
 .../docs/pipelines/sinks/manage-sinks.mdx     |    2 +-
 .../sql-reference/scalar-functions/string.mdx |    1 -
 .../docs/privacy-gateway/get-started.mdx      |   32 +-
 .../docs/privacy-gateway/reference/index.mdx  |    2 +-
 .../docs/privacy-gateway/reference/legal.mdx  |    4 +-
 .../privacy-gateway/reference/metrics.mdx     |  132 +-
 .../reference/product-compatibility.mdx       |    6 +-
 .../privacy-proxy/concepts/authentication.mdx |   12 +-
 .../concepts/deployment-models.mdx            |   26 +-
 .../privacy-proxy/concepts/geolocation.mdx    |   12 +-
 .../privacy-proxy/concepts/how-it-works.mdx   |   17 +-
 .../docs/privacy-proxy/get-started.mdx        |    2 +-
 .../privacy-proxy/reference/http-headers.mdx  |   32 +-
 .../privacy-proxy/reference/proxy-status.mdx  |   52 +-
 src/content/docs/pulumi/tutorial/index.mdx    |    3 -
 .../queues/configuration/configure-queues.mdx |   82 +-
 .../configuration/consumer-concurrency.mdx    |    2 +-
 .../docs/queues/configuration/index.mdx       |    2 +-
 .../queues/configuration/javascript-apis.mdx  |  243 ++--
 .../configuration/local-development.mdx       |    7 +-
 .../docs/queues/configuration/pause-purge.mdx |    6 +
 .../docs/queues/event-subscriptions/index.mdx |    4 +-
 .../manage-event-subscriptions.mdx            |    8 +-
 .../examples/publish-to-a-queue-via-http.mdx  |    1 -
 .../publish-to-a-queue-via-workers.mdx        |    5 +-
 .../queues/examples/send-errors-to-r2.mdx     |   50 +-
 .../examples/send-messages-from-dash.mdx      |    6 +-
 .../use-queues-with-durable-objects.mdx       |   68 +-
 src/content/docs/queues/glossary.mdx          |    2 +-
 .../docs/queues/observability/index.mdx       |    2 +-
 .../docs/queues/observability/metrics.mdx     |    8 +-
 src/content/docs/queues/platform/index.mdx    |    2 +-
 src/content/docs/queues/platform/limits.mdx   |   57 +-
 src/content/docs/queues/platform/pricing.mdx  |    9 +-
 .../queues/reference/delivery-guarantees.mdx  |    6 +-
 .../docs/queues/reference/error-codes.mdx     |   52 +-
 .../queues/reference/how-queues-works.mdx     |  148 ++-
 src/content/docs/queues/reference/index.mdx   |    2 +-
 .../reference/limitations-best-practices.mdx  |   68 +-
 .../r2-sql/reference/wrangler-commands.mdx    |    2 +-
 .../docs/r2-sql/sql-reference/index.mdx       |   18 +-
 src/content/docs/r2/api/error-codes.mdx       |   88 +-
 src/content/docs/r2/api/index.mdx             |    2 +-
 src/content/docs/r2/api/s3/extensions.mdx     |   18 +-
 src/content/docs/r2/api/s3/presigned-urls.mdx |   11 +-
 .../docs/r2/api/s3/temporary-credentials.mdx  |   54 +-
 .../r2/api/workers/workers-api-reference.mdx  |   78 +-
 .../docs/r2/api/workers/workers-api-usage.mdx |    1 +
 src/content/docs/r2/buckets/bucket-locks.mdx  |    3 +
 src/content/docs/r2/buckets/cors.mdx          |   45 +-
 .../docs/r2/buckets/delete-buckets.mdx        |   26 +-
 .../docs/r2/buckets/event-notifications.mdx   |   33 +-
 src/content/docs/r2/buckets/index.mdx         |    2 +-
 .../docs/r2/buckets/object-lifecycles.mdx     |    2 +
 .../docs/r2/buckets/storage-classes.mdx       |   32 +-
 src/content/docs/r2/data-migration/index.mdx  |    2 +-
 .../data-migration/migration-strategies.mdx   |    2 +-
 src/content/docs/r2/data-migration/sippy.mdx  |   18 +-
 .../docs/r2/data-migration/super-slurper.mdx  |    7 +-
 .../examples/authenticate-r2-auth-tokens.mdx  |    2 +-
 .../authenticate-r2-temp-credentials.mdx      |  174 +--
 .../docs/r2/examples/aws/aws-sdk-js-v3.mdx    |   19 +-
 .../docs/r2/examples/aws/aws-sdk-js.mdx       |   25 +-
 .../docs/r2/examples/aws/aws-sdk-kotlin.mdx   |    1 -
 .../docs/r2/examples/aws/aws4fetch.mdx        |   15 +-
 src/content/docs/r2/examples/aws/boto3.mdx    |   15 +-
 .../docs/r2/examples/aws/custom-header.mdx    |   95 +-
 src/content/docs/r2/examples/cache-api.mdx    |  109 +-
 src/content/docs/r2/examples/terraform.mdx    |    7 +-
 src/content/docs/r2/get-started/cli.mdx       |    9 +-
 src/content/docs/r2/get-started/index.mdx     |    1 +
 src/content/docs/r2/get-started/s3.mdx        |    9 +-
 .../docs/r2/get-started/workers-api.mdx       |    2 +-
 .../docs/r2/objects/delete-objects.mdx        |   19 +-
 .../docs/r2/objects/download-objects.mdx      |    3 +-
 src/content/docs/r2/objects/index.mdx         |    4 +-
 src/content/docs/r2/platform/audit-logs.mdx   |   59 +-
 .../docs/r2/platform/metrics-analytics.mdx    |    7 +-
 .../docs/r2/platform/troubleshooting.mdx      |    5 +-
 src/content/docs/r2/pricing.mdx               |   52 +-
 src/content/docs/r2/r2-sql.mdx                |    2 +-
 .../docs/r2/reference/data-location.mdx       |    2 +
 .../docs/r2/reference/data-security.mdx       |    2 -
 src/content/docs/r2/reference/durability.mdx  |   10 +-
 .../r2/reference/unicode-interoperability.mdx |    6 +-
 .../docs/r2/tutorials/cloudflare-access.mdx   |    2 +-
 src/content/docs/r2/tutorials/mastodon.mdx    |    3 +-
 src/content/docs/r2/tutorials/postman.mdx     |   12 +-
 src/content/docs/r2/video-tutorials.mdx       |   10 +-
 src/content/docs/radar/concepts/index.mdx     |    2 +-
 .../docs/radar/concepts/normalization.mdx     |    2 +-
 .../radar/get-started/configure-alerts.mdx    |    2 +-
 src/content/docs/radar/get-started/embed.mdx  |    4 +-
 src/content/docs/radar/get-started/index.mdx  |    2 +-
 .../radar/get-started/making-comparisons.mdx  |   78 +-
 .../investigate/application-layer-attacks.mdx |   84 +-
 src/content/docs/radar/investigate/dns.mdx    |   26 +-
 .../investigate/domain-ranking-datasets.mdx   |   37 +-
 .../docs/radar/investigate/http-requests.mdx  |   76 +-
 src/content/docs/radar/investigate/index.mdx  |    2 +-
 .../docs/radar/investigate/netflows.mdx       |   18 +-
 .../investigate/network-layer-attacks.mdx     |   86 +-
 .../docs/radar/investigate/outages.mdx        |   14 +-
 .../docs/radar/investigate/url-scanner.mdx    |   88 +-
 src/content/docs/radar/mcp-server.mdx         |    2 +-
 src/content/docs/radar/reference/index.mdx    |    2 +-
 .../reference/quarterly-ddos-reports.mdx      |    6 +-
 .../randomness-beacon/about/background.mdx    |    2 +-
 .../docs/randomness-beacon/about/future.mdx   |    6 +-
 .../cryptographic-background/index.mdx        |    6 +-
 .../randomness-generation.mdx                 |    6 +-
 .../cryptographic-background/setup-phase.mdx  |    4 +-
 src/content/docs/realtime/agents/index.mdx    |    4 +-
 .../docs/realtime/realtimekit/ai/index.mdx    |    2 +-
 .../docs/realtime/realtimekit/ai/summary.mdx  |   69 +-
 .../realtime/realtimekit/ai/transcription.mdx |    2 +-
 .../realtimekit/core/api-reference/RTKAi.md   |   40 +-
 .../realtimekit/core/api-reference/RTKChat.md |  329 ++---
 .../api-reference/RTKConnectedMeetings.md     |   81 +-
 .../core/api-reference/RTKLivestream.md       |   46 +-
 .../realtimekit/core/api-reference/RTKMeta.md |   68 +-
 .../core/api-reference/RTKParticipant.md      |  188 +--
 .../core/api-reference/RTKParticipantMap.md   |   56 +-
 .../core/api-reference/RTKParticipants.md     |  240 ++--
 .../api-reference/RTKPermissionsPreset.md     |  143 ++-
 .../realtimekit/core/api-reference/RTKPip.md  |   72 +-
 .../core/api-reference/RTKPlugin.md           |  122 +-
 .../core/api-reference/RTKPlugins.md          |   21 +-
 .../core/api-reference/RTKPolls.md            |   33 +-
 .../core/api-reference/RTKRecording.md        |   20 +-
 .../realtimekit/core/api-reference/RTKSelf.md |  109 +-
 .../core/api-reference/RTKSelfMedia.md        |   77 +-
 .../core/api-reference/RTKStage.md            |   63 +-
 .../core/api-reference/RTKStore.md            |  167 +--
 .../core/api-reference/RTKThemePreset.md      |   89 +-
 .../core/api-reference/RealtimeKitClient.md   |  129 +-
 .../realtime/realtimekit/legal/3rdparty.mdx   |   99 +-
 .../recording-guide/add-watermark.mdx         |   20 +-
 .../recording-guide/configure-codecs.mdx      |    6 +-
 .../recording-guide/monitor-status.mdx        |   12 +-
 .../recording-guide/track-recording.mdx       |   69 +-
 .../ui-kit/api-reference/angular/index.mdx    |    2 +-
 .../api-reference/angular/rtk-ai-toggle.mdx   |   24 +-
 .../angular/rtk-ai-transcriptions.mdx         |   16 +-
 .../ui-kit/api-reference/angular/rtk-ai.mdx   |   26 +-
 .../api-reference/angular/rtk-audio-grid.mdx  |   27 +-
 .../api-reference/angular/rtk-audio-tile.mdx  |   27 +-
 .../angular/rtk-audio-visualizer.mdx          |   29 +-
 .../api-reference/angular/rtk-avatar.mdx      |   22 +-
 .../angular/rtk-breakout-room-manager.mdx     |   33 +-
 .../rtk-breakout-room-participants.mdx        |   25 +-
 .../angular/rtk-breakout-rooms-manager.mdx    |   18 +-
 .../angular/rtk-breakout-rooms-toggle.mdx     |   27 +-
 .../angular/rtk-broadcast-message-modal.mdx   |   18 +-
 .../api-reference/angular/rtk-button.mdx      |   23 +-
 .../angular/rtk-camera-selector.mdx           |   40 +-
 .../angular/rtk-camera-toggle.mdx             |   21 +-
 .../angular/rtk-caption-toggle.mdx            |   25 +-
 .../angular/rtk-chat-composer-ui.mdx          |   25 +-
 .../angular/rtk-chat-composer-view.mdx        |   35 +-
 .../api-reference/angular/rtk-chat-header.mdx |    4 +-
 .../angular/rtk-chat-message.mdx              |   45 +-
 .../rtk-chat-messages-ui-paginated.mdx        |   23 +-
 .../angular/rtk-chat-messages-ui.mdx          |   27 +-
 .../angular/rtk-chat-search-results.mdx       |   23 +-
 .../angular/rtk-chat-selector-ui.mdx          |   25 +-
 .../angular/rtk-chat-selector.mdx             |   25 +-
 .../api-reference/angular/rtk-chat-toggle.mdx |   37 +-
 .../ui-kit/api-reference/angular/rtk-chat.mdx |   23 +-
 .../api-reference/angular/rtk-clock.mdx       |   17 +-
 .../angular/rtk-confirmation-modal.mdx        |   18 +-
 .../angular/rtk-controlbar-button.mdx         |   29 +-
 .../api-reference/angular/rtk-controlbar.mdx  |   27 +-
 .../api-reference/angular/rtk-counter.mdx     |   22 +-
 .../angular/rtk-debugger-audio.mdx            |   21 +-
 .../angular/rtk-debugger-screenshare.mdx      |   20 +-
 .../angular/rtk-debugger-system.mdx           |   21 +-
 .../angular/rtk-debugger-toggle.mdx           |   23 +-
 .../angular/rtk-debugger-video.mdx            |   21 +-
 .../api-reference/angular/rtk-debugger.mdx    |   21 +-
 .../angular/rtk-dialog-manager.mdx            |   36 +-
 .../api-reference/angular/rtk-dialog.mdx      |   31 +-
 .../angular/rtk-emoji-picker-button.mdx       |   16 +-
 .../angular/rtk-emoji-picker.mdx              |   16 +-
 .../angular/rtk-ended-screen.mdx              |   23 +-
 .../angular/rtk-file-dropzone.mdx             |   16 +-
 .../angular/rtk-file-message-view.mdx         |   19 +-
 .../angular/rtk-file-message.mdx              |   25 +-
 .../angular/rtk-file-picker-button.mdx        |   23 +-
 .../angular/rtk-fullscreen-toggle.mdx         |   25 +-
 .../angular/rtk-grid-pagination.mdx           |   27 +-
 .../ui-kit/api-reference/angular/rtk-grid.mdx |   34 +-
 .../api-reference/angular/rtk-header.mdx      |   28 +-
 .../ui-kit/api-reference/angular/rtk-icon.mdx |   18 +-
 .../api-reference/angular/rtk-idle-screen.mdx |   20 +-
 .../angular/rtk-image-message-view.mdx        |   16 +-
 .../angular/rtk-image-message.mdx             |   25 +-
 .../angular/rtk-image-viewer.mdx              |   19 +-
 .../angular/rtk-information-tooltip.mdx       |   11 +-
 .../api-reference/angular/rtk-join-stage.mdx  |   25 +-
 .../angular/rtk-leave-button.mdx              |   19 +-
 .../angular/rtk-leave-meeting.mdx             |   20 +-
 .../angular/rtk-livestream-indicator.mdx      |   18 +-
 .../angular/rtk-livestream-player.mdx         |   19 +-
 .../angular/rtk-livestream-toggle.mdx         |   21 +-
 .../ui-kit/api-reference/angular/rtk-logo.mdx |   19 +-
 .../angular/rtk-markdown-view.mdx             |   15 +-
 .../angular/rtk-meeting-title.mdx             |   16 +-
 .../api-reference/angular/rtk-meeting.mdx     |   43 +-
 .../api-reference/angular/rtk-menu-item.mdx   |   18 +-
 .../api-reference/angular/rtk-menu-list.mdx   |   16 +-
 .../ui-kit/api-reference/angular/rtk-menu.mdx |   22 +-
 .../angular/rtk-message-list-view.mdx         |   25 +-
 .../angular/rtk-message-view.mdx              |   39 +-
 .../api-reference/angular/rtk-mic-toggle.mdx  |   21 +-
 .../angular/rtk-microphone-selector.mdx       |   40 +-
 .../api-reference/angular/rtk-mixed-grid.mdx  |   40 +-
 .../api-reference/angular/rtk-more-toggle.mdx |   29 +-
 .../angular/rtk-mute-all-button.mdx           |   21 +-
 .../angular/rtk-mute-all-confirmation.mdx     |   18 +-
 .../api-reference/angular/rtk-name-tag.mdx    |   27 +-
 .../angular/rtk-network-indicator.mdx         |   23 +-
 .../angular/rtk-notification.mdx              |   25 +-
 .../angular/rtk-notifications.mdx             |   27 +-
 .../angular/rtk-overlay-modal.mdx             |   18 +-
 .../angular/rtk-paginated-list.mdx            |   33 +-
 .../angular/rtk-participant-count.mdx         |   19 +-
 .../angular/rtk-participant-setup.mdx         |   31 +-
 .../angular/rtk-participant-tile.mdx          |   37 +-
 .../api-reference/angular/rtk-participant.mdx |   31 +-
 .../angular/rtk-participants-audio.mdx        |   19 +-
 .../angular/rtk-participants-stage-list.mdx   |   33 +-
 .../angular/rtk-participants-stage-queue.mdx  |   25 +-
 .../angular/rtk-participants-toggle.mdx       |   35 +-
 .../angular/rtk-participants-viewer-list.mdx  |   29 +-
 .../angular/rtk-participants-waiting-list.mdx |   25 +-
 .../angular/rtk-participants.mdx              |   29 +-
 .../angular/rtk-permissions-message.mdx       |   20 +-
 .../angular/rtk-pinned-message-selector.mdx   |   16 +-
 .../api-reference/angular/rtk-pip-toggle.mdx  |   25 +-
 .../api-reference/angular/rtk-plugin-main.mdx |   19 +-
 .../angular/rtk-plugins-toggle.mdx            |   35 +-
 .../api-reference/angular/rtk-plugins.mdx     |   23 +-
 .../api-reference/angular/rtk-poll-form.mdx   |   15 +-
 .../ui-kit/api-reference/angular/rtk-poll.mdx |   23 +-
 .../angular/rtk-polls-toggle.mdx              |   37 +-
 .../api-reference/angular/rtk-polls.mdx       |   23 +-
 .../angular/rtk-recording-indicator.mdx       |   20 +-
 .../angular/rtk-recording-toggle.mdx          |   29 +-
 .../angular/rtk-screen-share-toggle.mdx       |   23 +-
 .../angular/rtk-screenshare-view.mdx          |   35 +-
 .../angular/rtk-settings-audio.mdx            |   38 +-
 .../angular/rtk-settings-toggle.mdx           |   32 +-
 .../angular/rtk-settings-video.mdx            |   38 +-
 .../api-reference/angular/rtk-settings.mdx    |   23 +-
 .../angular/rtk-setup-screen.mdx              |   25 +-
 .../api-reference/angular/rtk-sidebar-ui.mdx  |   29 +-
 .../api-reference/angular/rtk-sidebar.mdx     |   33 +-
 .../api-reference/angular/rtk-simple-grid.mdx |   29 +-
 .../angular/rtk-speaker-selector.mdx          |   42 +-
 .../api-reference/angular/rtk-spinner.mdx     |   14 +-
 .../angular/rtk-spotlight-grid.mdx            |   42 +-
 .../angular/rtk-spotlight-indicator.mdx       |   18 +-
 .../angular/rtk-stage-toggle.mdx              |   23 +-
 .../api-reference/angular/rtk-stage.mdx       |   17 +-
 .../api-reference/angular/rtk-switch.mdx      |   22 +-
 .../api-reference/angular/rtk-tab-bar.mdx     |   29 +-
 .../angular/rtk-text-composer-view.mdx        |   31 +-
 .../angular/rtk-text-message-view.mdx         |   14 +-
 .../angular/rtk-text-message.mdx              |   25 +-
 .../api-reference/angular/rtk-tooltip.mdx     |   28 +-
 .../api-reference/angular/rtk-transcript.mdx  |   19 +-
 .../api-reference/angular/rtk-transcripts.mdx |   22 +-
 .../api-reference/angular/rtk-ui-provider.mdx |   27 +-
 .../angular/rtk-viewer-count.mdx              |   19 +-
 .../rtk-virtualized-participant-list.mdx      |   23 +-
 .../angular/rtk-waiting-screen.mdx            |   18 +-
 .../ui-kit/api-reference/core/index.mdx       |    2 +-
 .../core/rtk-ai-transcriptions.mdx            |   21 +-
 .../ui-kit/api-reference/core/rtk-ai.mdx      |   28 +-
 .../api-reference/core/rtk-audio-grid.mdx     |   31 +-
 .../api-reference/core/rtk-audio-tile.mdx     |   31 +-
 .../core/rtk-audio-visualizer.mdx             |   33 +-
 .../ui-kit/api-reference/core/rtk-avatar.mdx  |   26 +-
 .../core/rtk-breakout-room-manager.mdx        |   37 +-
 .../core/rtk-breakout-room-participants.mdx   |   31 +-
 .../core/rtk-breakout-rooms-manager.mdx       |   21 +-
 .../core/rtk-breakout-rooms-toggle.mdx        |   30 +-
 .../core/rtk-broadcast-message-modal.mdx      |   21 +-
 .../ui-kit/api-reference/core/rtk-button.mdx  |   27 +-
 .../core/rtk-camera-selector.mdx              |   41 +-
 .../core/rtk-chat-composer-ui.mdx             |   28 +-
 .../core/rtk-chat-composer-view.mdx           |   37 +-
 .../api-reference/core/rtk-chat-header.mdx    |    4 +-
 .../api-reference/core/rtk-chat-message.mdx   |   51 +-
 .../core/rtk-chat-messages-ui-paginated.mdx   |   24 +-
 .../core/rtk-chat-messages-ui.mdx             |   30 +-
 .../core/rtk-chat-search-results.mdx          |   24 +-
 .../core/rtk-chat-selector-ui.mdx             |   26 +-
 .../api-reference/core/rtk-chat-selector.mdx  |   28 +-
 .../ui-kit/api-reference/core/rtk-chat.mdx    |   26 +-
 .../ui-kit/api-reference/core/rtk-clock.mdx   |   20 +-
 .../core/rtk-confirmation-modal.mdx           |   21 +-
 .../core/rtk-controlbar-button.mdx            |   34 +-
 .../api-reference/core/rtk-controlbar.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-counter.mdx |   26 +-
 .../api-reference/core/rtk-debugger-audio.mdx |   24 +-
 .../core/rtk-debugger-screenshare.mdx         |   24 +-
 .../core/rtk-debugger-system.mdx              |   24 +-
 .../api-reference/core/rtk-debugger-video.mdx |   24 +-
 .../api-reference/core/rtk-debugger.mdx       |   24 +-
 .../api-reference/core/rtk-dialog-manager.mdx |   39 +-
 .../ui-kit/api-reference/core/rtk-dialog.mdx  |   35 +-
 .../core/rtk-draft-attachment-view.mdx        |   19 +-
 .../core/rtk-emoji-picker-button.mdx          |   19 +-
 .../api-reference/core/rtk-emoji-picker.mdx   |   19 +-
 .../api-reference/core/rtk-ended-screen.mdx   |   26 +-
 .../api-reference/core/rtk-file-dropzone.mdx  |   18 +-
 .../core/rtk-file-message-view.mdx            |   23 +-
 .../api-reference/core/rtk-file-message.mdx   |   27 +-
 .../core/rtk-file-picker-button.mdx           |   24 +-
 .../core/rtk-grid-pagination.mdx              |   28 +-
 .../ui-kit/api-reference/core/rtk-grid.mdx    |   37 +-
 .../ui-kit/api-reference/core/rtk-header.mdx  |   32 +-
 .../ui-kit/api-reference/core/rtk-icon.mdx    |   21 +-
 .../api-reference/core/rtk-idle-screen.mdx    |   23 +-
 .../core/rtk-image-message-view.mdx           |   19 +-
 .../api-reference/core/rtk-image-message.mdx  |   27 +-
 .../api-reference/core/rtk-image-viewer.mdx   |   21 +-
 .../core/rtk-information-tooltip.mdx          |   15 +-
 .../api-reference/core/rtk-join-stage.mdx     |   28 +-
 .../api-reference/core/rtk-leave-meeting.mdx  |   23 +-
 .../core/rtk-livestream-indicator.mdx         |   22 +-
 .../core/rtk-livestream-player.mdx            |   22 +-
 .../ui-kit/api-reference/core/rtk-logo.mdx    |   22 +-
 .../api-reference/core/rtk-markdown-view.mdx  |   18 +-
 .../api-reference/core/rtk-meeting-title.mdx  |   19 +-
 .../ui-kit/api-reference/core/rtk-meeting.mdx |   45 +-
 .../api-reference/core/rtk-menu-item.mdx      |   21 +-
 .../api-reference/core/rtk-menu-list.mdx      |   18 +-
 .../ui-kit/api-reference/core/rtk-menu.mdx    |   24 +-
 .../core/rtk-message-list-view.mdx            |   27 +-
 .../api-reference/core/rtk-message-view.mdx   |   43 +-
 .../core/rtk-microphone-selector.mdx          |   41 +-
 .../api-reference/core/rtk-mixed-grid.mdx     |   43 +-
 .../api-reference/core/rtk-more-toggle.mdx    |   32 +-
 .../core/rtk-mute-all-confirmation.mdx        |   21 +-
 .../api-reference/core/rtk-name-tag.mdx       |   31 +-
 .../core/rtk-network-indicator.mdx            |   27 +-
 .../api-reference/core/rtk-notification.mdx   |   28 +-
 .../api-reference/core/rtk-notifications.mdx  |   30 +-
 .../api-reference/core/rtk-overlay-modal.mdx  |   21 +-
 .../api-reference/core/rtk-paginated-list.mdx |   36 +-
 .../core/rtk-participant-count.mdx            |   22 +-
 .../core/rtk-participant-setup.mdx            |   33 +-
 .../core/rtk-participant-tile.mdx             |   37 +-
 .../api-reference/core/rtk-participant.mdx    |   33 +-
 .../core/rtk-participants-audio.mdx           |   21 +-
 .../core/rtk-participants-stage-list.mdx      |   36 +-
 .../core/rtk-participants-stage-queue.mdx     |   26 +-
 .../core/rtk-participants-viewer-list.mdx     |   32 +-
 .../core/rtk-participants-waiting-list.mdx    |   26 +-
 .../api-reference/core/rtk-participants.mdx   |   30 +-
 .../core/rtk-permissions-message.mdx          |   23 +-
 .../core/rtk-pinned-message-selector.mdx      |   19 +-
 .../api-reference/core/rtk-plugin-main.mdx    |   21 +-
 .../ui-kit/api-reference/core/rtk-plugins.mdx |   26 +-
 .../api-reference/core/rtk-poll-form.mdx      |   17 +-
 .../ui-kit/api-reference/core/rtk-poll.mdx    |   25 +-
 .../ui-kit/api-reference/core/rtk-polls.mdx   |   26 +-
 .../core/rtk-recording-indicator.mdx          |   24 +-
 .../core/rtk-recording-toggle.mdx             |   34 +-
 .../core/rtk-screenshare-view.mdx             |   35 +-
 .../api-reference/core/rtk-settings-audio.mdx |   41 +-
 .../api-reference/core/rtk-settings-video.mdx |   41 +-
 .../api-reference/core/rtk-settings.mdx       |   26 +-
 .../api-reference/core/rtk-setup-screen.mdx   |   28 +-
 .../api-reference/core/rtk-sidebar-ui.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-sidebar.mdx |   35 +-
 .../api-reference/core/rtk-simple-grid.mdx    |   34 +-
 .../core/rtk-speaker-selector.mdx             |   43 +-
 .../ui-kit/api-reference/core/rtk-spinner.mdx |   17 +-
 .../api-reference/core/rtk-spotlight-grid.mdx |   46 +-
 .../core/rtk-spotlight-indicator.mdx          |   22 +-
 .../ui-kit/api-reference/core/rtk-stage.mdx   |   19 +-
 .../ui-kit/api-reference/core/rtk-switch.mdx  |   27 +-
 .../ui-kit/api-reference/core/rtk-tab-bar.mdx |   31 +-
 .../core/rtk-text-composer-view.mdx           |   33 +-
 .../core/rtk-text-message-view.mdx            |   18 +-
 .../api-reference/core/rtk-text-message.mdx   |   27 +-
 .../ui-kit/api-reference/core/rtk-tooltip.mdx |   31 +-
 .../api-reference/core/rtk-transcript.mdx     |   22 +-
 .../api-reference/core/rtk-transcripts.mdx    |   25 +-
 .../api-reference/core/rtk-ui-provider.mdx    |   31 +-
 .../api-reference/core/rtk-viewer-count.mdx   |   22 +-
 .../core/rtk-virtualized-participant-list.mdx |   25 +-
 .../api-reference/core/rtk-waiting-screen.mdx |   21 +-
 .../react-native/RtkMenuItem.mdx              |   10 +-
 .../ui-kit/api-reference/react/RtkAi.mdx      |   34 +-
 .../api-reference/react/RtkAiToggle.mdx       |   32 +-
 .../react/RtkAiTranscriptions.mdx             |   25 +-
 .../api-reference/react/RtkAudioGrid.mdx      |   36 +-
 .../api-reference/react/RtkAudioTile.mdx      |   40 +-
 .../react/RtkAudioVisualizer.mdx              |   42 +-
 .../ui-kit/api-reference/react/RtkAvatar.mdx  |   30 +-
 .../react/RtkBreakoutRoomManager.mdx          |   46 +-
 .../react/RtkBreakoutRoomParticipants.mdx     |   38 +-
 .../react/RtkBreakoutRoomsManager.mdx         |   26 +-
 .../react/RtkBreakoutRoomsToggle.mdx          |   40 +-
 .../react/RtkBroadcastMessageModal.mdx        |   26 +-
 .../ui-kit/api-reference/react/RtkButton.mdx  |   32 +-
 .../api-reference/react/RtkCameraSelector.mdx |   53 +-
 .../api-reference/react/RtkCameraToggle.mdx   |   30 +-
 .../api-reference/react/RtkCaptionToggle.mdx  |   34 +-
 .../ui-kit/api-reference/react/RtkChat.mdx    |   31 +-
 .../api-reference/react/RtkChatComposerUi.mdx |   38 +-
 .../react/RtkChatComposerView.mdx             |   48 +-
 .../api-reference/react/RtkChatHeader.mdx     |    8 +-
 .../api-reference/react/RtkChatMessage.mdx    |   54 +-
 .../api-reference/react/RtkChatMessagesUi.mdx |   40 +-
 .../react/RtkChatMessagesUiPaginated.mdx      |   36 +-
 .../react/RtkChatSearchResults.mdx            |   36 +-
 .../api-reference/react/RtkChatSelector.mdx   |   33 +-
 .../api-reference/react/RtkChatSelectorUi.mdx |   38 +-
 .../api-reference/react/RtkChatToggle.mdx     |   46 +-
 .../ui-kit/api-reference/react/RtkClock.mdx   |   25 +-
 .../react/RtkConfirmationModal.mdx            |   26 +-
 .../api-reference/react/RtkControlbar.mdx     |   36 +-
 .../react/RtkControlbarButton.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkCounter.mdx |   30 +-
 .../api-reference/react/RtkDebugger.mdx       |   29 +-
 .../api-reference/react/RtkDebuggerAudio.mdx  |   29 +-
 .../react/RtkDebuggerScreenshare.mdx          |   29 +-
 .../api-reference/react/RtkDebuggerSystem.mdx |   29 +-
 .../api-reference/react/RtkDebuggerToggle.mdx |   32 +-
 .../api-reference/react/RtkDebuggerVideo.mdx  |   29 +-
 .../ui-kit/api-reference/react/RtkDialog.mdx  |   44 +-
 .../api-reference/react/RtkDialogManager.mdx  |   44 +-
 .../react/RtkDraftAttachmentView.mdx          |   24 +-
 .../api-reference/react/RtkEmojiPicker.mdx    |   24 +-
 .../react/RtkEmojiPickerButton.mdx            |   24 +-
 .../api-reference/react/RtkEndedScreen.mdx    |   31 +-
 .../api-reference/react/RtkFileDropzone.mdx   |   24 +-
 .../api-reference/react/RtkFileMessage.mdx    |   34 +-
 .../react/RtkFileMessageView.mdx              |   28 +-
 .../react/RtkFilePickerButton.mdx             |   36 +-
 .../react/RtkFullscreenToggle.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkGrid.mdx    |   42 +-
 .../api-reference/react/RtkGridPagination.mdx |   40 +-
 .../ui-kit/api-reference/react/RtkHeader.mdx  |   36 +-
 .../ui-kit/api-reference/react/RtkIcon.mdx    |   26 +-
 .../api-reference/react/RtkIdleScreen.mdx     |   28 +-
 .../api-reference/react/RtkImageMessage.mdx   |   36 +-
 .../react/RtkImageMessageView.mdx             |   24 +-
 .../api-reference/react/RtkImageViewer.mdx    |   27 +-
 .../react/RtkInformationTooltip.mdx           |   20 +-
 .../api-reference/react/RtkJoinStage.mdx      |   36 +-
 .../api-reference/react/RtkLeaveButton.mdx    |   27 +-
 .../api-reference/react/RtkLeaveMeeting.mdx   |   28 +-
 .../react/RtkLivestreamIndicator.mdx          |   27 +-
 .../react/RtkLivestreamPlayer.mdx             |   27 +-
 .../react/RtkLivestreamToggle.mdx             |   30 +-
 .../ui-kit/api-reference/react/RtkLogo.mdx    |   27 +-
 .../api-reference/react/RtkMarkdownView.mdx   |   23 +-
 .../ui-kit/api-reference/react/RtkMeeting.mdx |   56 +-
 .../api-reference/react/RtkMeetingTitle.mdx   |   24 +-
 .../ui-kit/api-reference/react/RtkMenu.mdx    |   30 +-
 .../api-reference/react/RtkMenuItem.mdx       |   27 +-
 .../api-reference/react/RtkMenuList.mdx       |   24 +-
 .../api-reference/react/RtkMessageView.mdx    |   50 +-
 .../api-reference/react/RtkMicToggle.mdx      |   30 +-
 .../react/RtkMicrophoneSelector.mdx           |   53 +-
 .../api-reference/react/RtkMixedGrid.mdx      |   48 +-
 .../api-reference/react/RtkMoreToggle.mdx     |   37 +-
 .../api-reference/react/RtkMuteAllButton.mdx  |   30 +-
 .../react/RtkMuteAllConfirmation.mdx          |   26 +-
 .../ui-kit/api-reference/react/RtkNameTag.mdx |   40 +-
 .../react/RtkNetworkIndicator.mdx             |   36 +-
 .../api-reference/react/RtkNotification.mdx   |   36 +-
 .../api-reference/react/RtkNotifications.mdx  |   35 +-
 .../api-reference/react/RtkOverlayModal.mdx   |   26 +-
 .../api-reference/react/RtkPaginatedList.mdx  |   46 +-
 .../api-reference/react/RtkParticipant.mdx    |   44 +-
 .../react/RtkParticipantCount.mdx             |   27 +-
 .../api-reference/react/RtkParticipants.mdx   |   42 +-
 .../react/RtkParticipantsAudio.mdx            |   32 +-
 .../react/RtkParticipantsStageList.mdx        |   46 +-
 .../react/RtkParticipantsStageQueue.mdx       |   38 +-
 .../react/RtkParticipantsToggle.mdx           |   44 +-
 .../react/RtkParticipantsViewerList.mdx       |   42 +-
 .../react/RtkParticipantsWaitingList.mdx      |   38 +-
 .../react/RtkPermissionsMessage.mdx           |   28 +-
 .../react/RtkPinnedMessageSelector.mdx        |   24 +-
 .../api-reference/react/RtkPipToggle.mdx      |   34 +-
 .../api-reference/react/RtkPluginMain.mdx     |   27 +-
 .../ui-kit/api-reference/react/RtkPlugins.mdx |   31 +-
 .../api-reference/react/RtkPluginsToggle.mdx  |   44 +-
 .../ui-kit/api-reference/react/RtkPoll.mdx    |   34 +-
 .../api-reference/react/RtkPollForm.mdx       |   23 +-
 .../ui-kit/api-reference/react/RtkPolls.mdx   |   31 +-
 .../api-reference/react/RtkPollsToggle.mdx    |   46 +-
 .../react/RtkRecordingIndicator.mdx           |   29 +-
 .../react/RtkRecordingToggle.mdx              |   38 +-
 .../react/RtkScreenShareToggle.mdx            |   32 +-
 .../api-reference/react/RtkSettings.mdx       |   31 +-
 .../api-reference/react/RtkSettingsAudio.mdx  |   46 +-
 .../api-reference/react/RtkSettingsToggle.mdx |   40 +-
 .../api-reference/react/RtkSettingsVideo.mdx  |   46 +-
 .../api-reference/react/RtkSetupScreen.mdx    |   33 +-
 .../ui-kit/api-reference/react/RtkSidebar.mdx |   46 +-
 .../api-reference/react/RtkSidebarUi.mdx      |   42 +-
 .../api-reference/react/RtkSimpleGrid.mdx     |   38 +-
 .../react/RtkSpeakerSelector.mdx              |   55 +-
 .../ui-kit/api-reference/react/RtkSpinner.mdx |   22 +-
 .../api-reference/react/RtkSpotlightGrid.mdx  |   51 +-
 .../react/RtkSpotlightIndicator.mdx           |   27 +-
 .../ui-kit/api-reference/react/RtkStage.mdx   |   25 +-
 .../api-reference/react/RtkStageToggle.mdx    |   32 +-
 .../ui-kit/api-reference/react/RtkSwitch.mdx  |   30 +-
 .../ui-kit/api-reference/react/RtkTabBar.mdx  |   38 +-
 .../api-reference/react/RtkTextMessage.mdx    |   34 +-
 .../react/RtkTextMessageView.mdx              |   23 +-
 .../ui-kit/api-reference/react/RtkTooltip.mdx |   36 +-
 .../api-reference/react/RtkTranscript.mdx     |   27 +-
 .../api-reference/react/RtkTranscripts.mdx    |   30 +-
 .../api-reference/react/RtkUiProvider.mdx     |   40 +-
 .../api-reference/react/RtkViewerCount.mdx    |   27 +-
 .../react/RtkVirtualizedParticipantList.mdx   |   36 +-
 .../api-reference/react/RtkWaitingScreen.mdx  |   26 +-
 .../ui-kit/api-reference/react/index.mdx      |    2 +-
 .../docs/realtime/sfu/calls-vs-sfus.mdx       |    7 +-
 src/content/docs/realtime/sfu/changelog.mdx   |    2 +-
 .../docs/realtime/sfu/datachannels.mdx        |    2 +-
 src/content/docs/realtime/sfu/get-started.mdx |    6 +-
 src/content/docs/realtime/sfu/limits.mdx      |   33 +-
 .../sfu/media-transport-adapters/index.mdx    |    1 +
 .../websocket-adapter.mdx                     |   25 +-
 .../docs/realtime/sfu/sessions-tracks.mdx     |   20 +-
 .../docs/realtime/turn/custom-domains.mdx     |   10 +-
 .../realtime/turn/generate-credentials.mdx    |   35 +-
 .../docs/realtime/turn/replacing-existing.mdx |   20 +-
 src/content/docs/realtime/turn/rfc-matrix.mdx |   30 +-
 .../architectures/sase.mdx                    |   18 +-
 .../architectures/security.mdx                |    2 +-
 .../designing-ztna-access-policies.mdx        |   18 +-
 ...nefits-to-saas-providers-end-customers.mdx |   16 +-
 .../diagrams/ai/index.mdx                     |    2 +-
 .../diagrams/content-delivery/index.mdx       |    2 +-
 ...uring-connected-transportation-systems.mdx |   17 +-
 .../diagrams/network/index.mdx                |    2 +-
 .../diagrams/sase/index.mdx                   |    2 +-
 .../diagrams/security/index.mdx               |    2 +-
 .../serverless/fullstack-application.mdx      |   27 +-
 .../diagrams/serverless/index.mdx             |    2 +-
 .../serverless/programmable-platforms.mdx     |    1 -
 .../diagrams/storage/index.mdx                |    2 +-
 .../implementation-guides/index.mdx           |    2 +-
 .../zero-trust/index.mdx                      |    2 +-
 .../domain-contact-updates.mdx                |   26 +-
 .../account-options/domain-management.mdx     |   18 +-
 .../account-options/icloud-domains.mdx        |   24 +-
 .../docs/registrar/account-options/index.mdx  |    2 +-
 .../inter-account-transfer.mdx                |   31 +-
 .../account-options/renew-domains.mdx         |   22 +-
 .../transfer-out-from-cloudflare.mdx          |   12 +-
 .../account-options/whois-redaction.mdx       |    4 +-
 .../registrar/custom-domain-protection.mdx    |    6 +-
 .../docs/registrar/get-started/index.mdx      |    2 +-
 .../registrar/get-started/register-domain.mdx |   15 +-
 .../top-level-domains/uk-domains.mdx          |   12 +-
 src/content/docs/registrar/whoisrequests.mdx  |    4 +-
 .../docs/resource-tagging/get-started.mdx     |   14 +-
 .../docs/resource-tagging/how-to/index.mdx    |    2 +-
 .../resource-tagging/how-to/manage-tags.mdx   |    6 +-
 .../reference/error-codes.mdx                 |   26 +-
 .../docs/resource-tagging/reference/index.mdx |    2 +-
 .../resource-tagging/reference/limits.mdx     |   37 +-
 .../reference/resource-types.mdx              |   80 +-
 .../docs/rules/normalization/settings.mdx     |    4 +-
 .../docs/rules/snippets/when-to-use.mdx       |    2 +-
 .../managed-transforms/reference.mdx          |    1 -
 .../docs/ruleset-engine/about/index.mdx       |    9 +-
 ...ink-override-ddos-l34-rule-sensitivity.mdx |    1 -
 .../ruleset-engine/rulesets-api/endpoints.mdx |  405 +++---
 src/content/docs/sandbox/bridge/http-api.mdx  |  148 +--
 .../docs/sandbox/concepts/containers.mdx      |   23 +-
 .../docs/sandbox/concepts/preview-urls.mdx    |    6 +-
 .../docs/sandbox/concepts/sandboxes.mdx       |    4 +-
 .../docs/sandbox/concepts/security.mdx        |   65 +-
 .../docs/sandbox/concepts/sessions.mdx        |   77 +-
 .../configuration/environment-variables.mdx   |   32 +-
 .../docs/sandbox/configuration/transport.mdx  |    5 +-
 .../sandbox/guides/production-deployment.mdx  |    9 +-
 src/content/docs/sandbox/platform/pricing.mdx |    2 +
 .../sandbox/tutorials/ai-code-executor.mdx    |   76 +-
 .../tutorials/analyze-data-with-ai.mdx        |   29 +-
 .../tutorials/automated-testing-pipeline.mdx  |  116 +-
 .../tutorials/claude-managed-agents.mdx       |   29 +-
 .../sandbox/tutorials/code-review-bot.mdx     |    4 +-
 src/content/docs/secrets-store/audit-logs.mdx |    2 +-
 src/content/docs/secrets-store/index.mdx      |    3 +-
 .../secrets-store/integrations/ai-gateway.mdx |    2 +-
 .../docs/secrets-store/integrations/index.mdx |    2 +-
 .../secrets-store/manage-secrets/how-to.mdx   |    2 +-
 .../secrets-store/manage-secrets/index.mdx    |    2 +-
 .../docs/security-center/brand-protection.mdx |    2 +-
 .../docs/security-center/changelog.mdx        |   10 +-
 .../cloudforce-one/cloudforce-one.mdx         |    1 -
 .../cloudforce-one/open-port-scanning.mdx     |  170 +--
 .../investigate/change-categorization.mdx     |    1 -
 .../security-center/investigate/index.mdx     |    1 -
 .../investigate/investigate-threats.mdx       |    5 +-
 .../investigate/scan-limits.mdx               |    4 -
 src/content/docs/security/overview.mdx        |   43 +-
 .../docs/smart-shield/concepts/index.mdx      |    2 +-
 .../smart-shield/concepts/network-diagram.mdx |    2 +-
 .../docs/smart-shield/configuration/argo.mdx  |    2 +-
 .../configuration/cache-reserve/analytics.mdx |    6 +-
 .../configuration/cache-reserve/index.mdx     |    2 +-
 .../cache-reserve/operations.mdx              |    5 +-
 .../how-it-works/connection-forwarding.mdx    |    6 +-
 .../how-it-works/index.mdx                    |    2 +-
 .../dedicated-egress-ips/index.mdx            |    8 +-
 .../dedicated-egress-ips/ips-utilization.mdx  |  202 +--
 .../dedicated-egress-ips/other-products.mdx   |    2 +-
 .../configuration/health-checks/analytics.mdx |    5 +-
 .../configuration/health-checks/index.mdx     |    2 +-
 .../configuration/health-checks/setup.mdx     |    4 +-
 .../health-checks/zone-lockdown.mdx           |    2 +-
 .../docs/smart-shield/configuration/index.mdx |    2 +-
 .../configuration/regional-tiered-cache.mdx   |    2 +-
 .../configuration/smart-tiered-cache.mdx      |    2 +-
 src/content/docs/spectrum/about/byoip.mdx     |   75 +-
 .../docs/spectrum/about/ddos-for-spectrum.mdx |    1 -
 src/content/docs/spectrum/about/ftp.mdx       |   16 +-
 src/content/docs/spectrum/about/index.mdx     |    3 +-
 src/content/docs/spectrum/about/static-ip.mdx |   46 +-
 src/content/docs/spectrum/glossary.mdx        |    3 +-
 .../spectrum/how-to/enable-proxy-protocol.mdx |    3 -
 src/content/docs/spectrum/how-to/index.mdx    |    3 +-
 .../docs/spectrum/protocols-per-plan.mdx      |    3 +-
 .../docs/spectrum/reference/analytics.mdx     |   46 +-
 src/content/docs/spectrum/reference/index.mdx |    3 +-
 .../spectrum/reference/layer-7-analytics.mdx  |    4 +-
 src/content/docs/spectrum/reference/logs.mdx  |    3 -
 .../spectrum/reference/settings-by-plan.mdx   |   14 +-
 src/content/docs/speed/aim.mdx                |   33 +-
 src/content/docs/speed/glossary.mdx           |    3 +-
 .../docs/speed/observatory/dashboard.mdx      |   11 +-
 .../docs/speed/observatory/rum-beacon.mdx     |   46 +-
 .../docs/speed/observatory/run-speed-test.mdx |   21 +-
 .../docs/speed/observatory/test-results.mdx   |   23 +-
 .../docs/speed/optimization/content/apo.mdx   |    1 -
 .../optimization/content/compression.mdx      |    6 +-
 .../optimization/content/early-hints.mdx      |    1 -
 .../content/fonts/troubleshooting.mdx         |    5 +-
 .../docs/speed/optimization/content/index.mdx |    3 +-
 .../rocket-loader/ignore-javascripts.mdx      |   10 +-
 .../content/shared-dictionaries.mdx           |    8 +-
 .../optimization/content/smart-hints.mdx      |    1 -
 .../optimization/content/speed-brain.mdx      |    9 +-
 .../content/troubleshooting/index.mdx         |    3 +-
 .../optimization/images/image-resizing.mdx    |    1 -
 .../docs/speed/optimization/images/index.mdx  |    3 +-
 .../docs/speed/optimization/images/polish.mdx |    1 -
 .../images/troubleshooting/index.mdx          |    3 +-
 .../multiple-optimizations.mdx                |    1 -
 .../images/troubleshooting/polish.mdx         |    1 -
 .../troubleshooting-missing-images.mdx        |    6 +-
 src/content/docs/speed/optimization/index.mdx |    3 +-
 .../docs/speed/optimization/measurement.mdx   |    1 -
 .../speed/optimization/protocol/http2.mdx     |    4 +-
 .../speed/optimization/protocol/index.mdx     |    3 +-
 ...hanced-http2-prioritization-ios-safari.mdx |    3 -
 .../protocol/troubleshooting/index.mdx        |    3 +-
 .../speed/optimization/recommendations.mdx    |    1 -
 src/content/docs/speed/smart-shield.mdx       |    3 +-
 src/content/docs/speed/troubleshooting.mdx    |   11 +-
 src/content/docs/ssl/changelog.mdx            |    4 +-
 .../forward-a-client-certificate.mdx          |    2 +-
 .../revoke-client-certificate.mdx             |    3 -
 src/content/docs/ssl/concepts.mdx             |    6 +-
 .../customize-cipher-suites/index.mdx         |    8 +-
 .../cipher-suites/supported-cipher-suites.mdx |   50 +-
 .../additional-options/index.mdx              |    3 +-
 .../additional-options/minimum-tls.mdx        |   22 +-
 .../additional-options/tls-13.mdx             |    9 +-
 .../api-commands.mdx                          |   14 +-
 .../manage-certificates.mdx                   |    8 +-
 .../edge-certificates/backup-certificates.mdx |    3 +-
 .../ssl/edge-certificates/caa-records.mdx     |    1 -
 .../bundling-methodologies.mdx                |    3 +-
 .../custom-certificates/renewing.mdx          |    3 +-
 .../docs/ssl/edge-certificates/ech.mdx        |    4 +-
 .../geokey-manager/supported-options.mdx      |    4 +-
 .../docs/ssl/edge-certificates/index.mdx      |    2 +-
 .../edge-certificates/staging-environment.mdx |   23 +-
 .../universal-ssl/alerts.mdx                  |    8 +-
 .../universal-ssl/disable-universal-ssl.mdx   |    2 -
 .../universal-ssl/troubleshooting.mdx         |    8 +-
 .../ssl/keyless-ssl/configuration/index.mdx   |    3 +-
 src/content/docs/ssl/keyless-ssl/glossary.mdx |    1 -
 .../azure-managed-hsm.mdx                     |    1 -
 .../fortanix-dsm.mdx                          |    2 +-
 .../hardware-security-modules/index.mdx       |    7 +-
 .../reference/high-availability.mdx           |    1 -
 .../docs/ssl/keyless-ssl/reference/index.mdx  |    3 +-
 .../reference/keyless-delegation.mdx          |    1 -
 .../ssl/keyless-ssl/reference/metrics.mdx     |  184 ++-
 .../reference/scaling-and-benchmarking.mdx    |    5 +-
 .../keyless-ssl/upgrading-your-key-server.mdx |    3 -
 .../set-up/global.mdx                         |    5 +-
 .../set-up/index.mdx                          |    5 +-
 .../origin-configuration/cipher-suites.mdx    |   28 +-
 .../docs/ssl/origin-configuration/index.mdx   |    3 +-
 .../origin-ca/troubleshooting.mdx             |    2 +-
 .../origin-configuration/ssl-modes/full.mdx   |    6 +-
 .../origin-configuration/ssl-modes/index.mdx  |    2 +-
 .../ssl-modes/ssl-only-origin-pull.mdx        |    7 +-
 .../docs/ssl/reference/all-features.mdx       |    5 +-
 .../ssl/reference/browser-compatibility.mdx   |    9 +-
 .../certificate-and-hostname-priority.mdx     |   17 +-
 .../ssl/reference/certificate-authorities.mdx |    2 +-
 .../ssl/reference/certificate-pinning.mdx     |    1 -
 .../cloudflare-and-cve-2019-1559.mdx          |    7 +-
 .../compliance-and-vulnerabilities.mdx        |   42 +-
 src/content/docs/ssl/reference/index.mdx      |    3 +-
 .../migration-guides/entrust-distrust.mdx     |   15 +-
 .../ssl/reference/migration-guides/index.mdx  |    3 +-
 src/content/docs/ssl/reference/protocols.mdx  |   18 +-
 src/content/docs/ssl/saas.mdx                 |    1 -
 .../troubleshooting/general-ssl-errors.mdx    |    2 +-
 .../docs/ssl/troubleshooting/index.mdx        |   10 +-
 .../troubleshooting/mixed-content-errors.mdx  |   19 +-
 .../version-cipher-mismatch.mdx               |    6 +-
 .../stream/edit-videos/adding-captions.mdx    |   91 +-
 .../edit-videos/player-enhancements.mdx       |   16 +-
 src/content/docs/stream/examples/dash-js.mdx  |    1 -
 src/content/docs/stream/examples/hls-js.mdx   |    5 +-
 src/content/docs/stream/examples/index.mdx    |    1 -
 .../examples/obs-from-scratch/index.mdx       |    1 -
 .../docs/stream/examples/rtmps_playback.mdx   |    3 +-
 .../docs/stream/examples/srt_playback.mdx     |    3 +-
 .../docs/stream/examples/stream-player.mdx    |   13 +-
 src/content/docs/stream/examples/video-js.mdx |    3 +-
 src/content/docs/stream/examples/vidstack.mdx |   15 +-
 .../fetching-bulk-analytics.mdx               |    1 +
 .../docs/stream/getting-analytics/index.mdx   |   11 +-
 .../getting-analytics/live-viewer-count.mdx   |    1 -
 .../stream/manage-video-library/index.mdx     |    1 -
 .../stream/manage-video-library/searching.mdx |    1 -
 src/content/docs/stream/stream-api.mdx        |    1 -
 .../stream/stream-live/custom-domains.mdx     |    3 +-
 .../download-stream-live-videos.mdx           |    4 +-
 .../docs/stream/stream-live/dvr-for-live.mdx  |   16 +-
 src/content/docs/stream/stream-live/index.mdx |    7 +-
 .../stream-live/live-instant-clipping.mdx     |   91 +-
 .../docs/stream/stream-live/simulcasting.mdx  |   40 +-
 .../stream/stream-live/start-stream-live.mdx  |    1 +
 .../stream/stream-live/troubleshooting.mdx    |   73 +-
 .../docs/stream/stream-live/webhooks.mdx      |   64 +-
 .../docs/stream/transform-videos/bindings.mdx |   36 +-
 .../docs/stream/transform-videos/index.mdx    |    4 +-
 .../docs/stream/uploading-videos/index.mdx    |   14 +-
 .../stream/uploading-videos/player-api.mdx    |  227 ++--
 .../uploading-videos/resumable-uploads.mdx    |    6 -
 .../uploading-videos/upload-via-link.mdx      |   80 +-
 .../viewing-videos/displaying-thumbnails.mdx  |   56 +-
 .../using-the-player-api.mdx                  |  260 ++--
 .../api-content-types/deprecated-apis.mdx     |    4 +-
 .../api-content-types/endpoints.mdx           |   18 +-
 .../api-content-types/index.mdx               |    2 +-
 .../api-content-types/parameters.mdx          |    2 +-
 .../guidelines-for-curl-commands.mdx          |   50 +-
 .../style-guide/components/anchor-heading.mdx |   11 +-
 .../components/available-notifications.mdx    |   15 +-
 .../style-guide/components/description.mdx    |    8 +-
 .../docs/style-guide/components/example.mdx   |   18 +-
 .../style-guide/components/feature-table.mdx  |    4 +-
 .../docs/style-guide/components/feature.mdx   |    8 +-
 .../components/glossary-definition.mdx        |   12 +-
 .../components/glossary-tooltip.mdx           |   12 +-
 .../docs/style-guide/components/glossary.mdx  |   12 +-
 .../style-guide/components/inline-badge.mdx   |   35 +-
 .../style-guide/components/link-cards.mdx     |   24 +-
 .../style-guide/components/list-tutorials.mdx |    2 +-
 .../components/package-managers.mdx           |    4 +-
 .../components/pages-build-preset.mdx         |    4 +-
 .../docs/style-guide/components/plan.mdx      |    5 +-
 .../components/product-availability-text.mdx  |    8 +-
 .../components/product-features.mdx           |    5 +-
 .../components/related-product.mdx            |    7 +-
 .../docs/style-guide/components/rule-id.mdx   |    4 +-
 .../docs/style-guide/components/steps.mdx     |    2 +-
 .../components/subtract-ip-calculator.mdx     |    6 +-
 .../components/type-highlighting.mdx          |    2 +-
 .../docs/style-guide/components/usage.mdx     |    2 +-
 .../components/wrangler-namespace.mdx         |    2 +-
 .../docs/style-guide/components/youtube.mdx   |    6 +-
 .../docs/style-guide/contributions.mdx        |   78 +-
 .../component-attributes/dynamic-lists.mdx    |    8 +-
 .../component-attributes/examples.mdx         |    8 +-
 .../component-attributes/glossary-entry.mdx   |   10 -
 .../component-attributes/index.mdx            |    2 +-
 .../intended-audience.mdx                     |   14 +-
 .../component-attributes/links.mdx            |   18 +-
 .../mathematical-operations.mdx               |    6 +-
 .../component-attributes/next-steps.mdx       |    6 +-
 .../notes-tips-warnings.mdx                   |    8 +-
 .../information-architecture.mdx              |   14 +-
 .../code-conventions-and-format.mdx           |   62 +-
 .../formatting/dates-and-times.mdx            |    6 +-
 .../formatting/external-references.mdx        |    6 +-
 .../formatting/file-types-and-extensions.mdx  |   12 +-
 .../docs/style-guide/formatting/index.mdx     |    2 +-
 .../style-guide/formatting/keyboard-keys.mdx  |   24 +-
 .../notes-and-other-notation-types.mdx        |    1 +
 .../numbers-and-units-of-measurement.mdx      |   18 +-
 .../product-name-and-pluralization.mdx        |    4 +-
 .../formatting/structure/index.mdx            |    2 +-
 .../formatting/structure/lists.mdx            |   79 +-
 .../formatting/structure/tables.mdx           |   79 +-
 .../docs/style-guide/frontmatter/sidebar.mdx  |    4 +-
 .../docs/style-guide/grammar/index.mdx        |    2 +-
 .../grammar/parts-of-speech/abbreviations.mdx |   46 +-
 .../grammar/parts-of-speech/acronyms.mdx      |    8 +-
 .../parts-of-speech/capitalization.mdx        |  160 ++-
 .../parts-of-speech/compound-words.mdx        |   53 +-
 .../grammar/parts-of-speech/contractions.mdx  |    2 +-
 .../grammar/parts-of-speech/index.mdx         |    2 +-
 .../parts-of-speech/nouns-and-pronouns.mdx    |    2 +-
 .../grammar/parts-of-speech/possessives.mdx   |    2 +-
 .../grammar/parts-of-speech/prepositions.mdx  |    2 +-
 .../punctuation-marks-and-symbols/commas.mdx  |    2 +-
 .../punctuation-marks-and-symbols/dashes.mdx  |   16 +-
 .../punctuation-marks-and-symbols/index.mdx   |    2 +-
 .../docs/style-guide/how-we-docs/our-site.mdx |    1 -
 .../docs/style-guide/how-we-docs/reviews.mdx  |   21 +-
 .../support/contacting-cloudflare-support.mdx |   46 +-
 src/content/docs/support/index.mdx            |    2 +-
 ...ress-plugin-automatic-cache-management.mdx |   16 +-
 ...-enable-http2-server-push-in-wordpress.mdx |    6 +-
 ...tent-management-systems-like-wordpress.mdx |   38 +-
 .../content-management-system-cms/index.mdx   |    2 +-
 ...dpress-in-cloudflares-wordpress-plugin.mdx |   26 +-
 .../forum-software/index.mdx                  |    2 +-
 ...-various-forums-vbulletin-xenforo-mybb.mdx |   10 +-
 .../support/third-party-software/index.mdx    |    2 +-
 .../third-party-software/others/index.mdx     |    2 +-
 ...ess-costs-between-azure-and-cloudflare.mdx |    8 +-
 .../cannot-locate-dashboard-account.mdx       |    8 +-
 ...-information-for-troubleshooting-sites.mdx |   26 +-
 .../geographic-traffic-routing.mdx            |    2 +-
 .../general-troubleshooting/index.mdx         |    2 +-
 .../not-receiving-cloudflare-emails.mdx       |   14 +-
 .../service-disruption.mdx                    |    8 +-
 .../third-party-load-balancers.mdx            |   12 +-
 .../troubleshooting-crawl-errors.mdx          |   40 +-
 .../4xx-client-error/error-400.mdx            |    2 +-
 .../4xx-client-error/error-401.mdx            |    2 +-
 .../4xx-client-error/error-406.mdx            |    2 +-
 .../4xx-client-error/error-407.mdx            |    2 +-
 .../4xx-client-error/error-408.mdx            |    2 +-
 .../4xx-client-error/error-409.mdx            |    2 +-
 .../4xx-client-error/error-410.mdx            |    2 +-
 .../4xx-client-error/error-411.mdx            |    2 +-
 .../4xx-client-error/error-412.mdx            |    2 +-
 .../4xx-client-error/error-413.mdx            |    2 +-
 .../4xx-client-error/error-414.mdx            |    2 +-
 .../4xx-client-error/error-416.mdx            |    2 +-
 .../4xx-client-error/error-417.mdx            |    2 +-
 .../4xx-client-error/error-429.mdx            |    1 -
 .../4xx-client-error/error-451.mdx            |    2 +-
 .../4xx-client-error/index.mdx                |    4 +-
 .../cloudflare-10xxx-errors/error-10028.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10043.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10044.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10045.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10046.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10047.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10048.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10049.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10050.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10051.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10052.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10055.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10056.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10058.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10059.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10060.mdx   |    2 +-
 .../cloudflare-10xxx-errors/index.md          |    2 +-
 .../cloudflare-1xxx-errors/error-1000.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1002.mdx     |    4 +-
 .../cloudflare-1xxx-errors/error-1004.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1009.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1014.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1035.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1040.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1102.mdx     |    1 -
 .../cloudflare-1xxx-errors/index.mdx          |    4 -
 .../cloudflare-5xx-errors/error-501.mdx       |    2 +-
 .../cloudflare-5xx-errors/error-503.mdx       |    9 +-
 .../cloudflare-5xx-errors/error-520.mdx       |    1 -
 .../cloudflare-5xx-errors/error-522.mdx       |    4 +-
 .../cloudflare-5xx-errors/error-524.mdx       |    5 +-
 .../cloudflare-5xx-errors/error-525.mdx       |    2 +-
 .../cloudflare-5xx-errors/index.mdx           |    6 +-
 .../cloudflare-error-headers.mdx              |   11 +-
 .../http-status-codes/index.mdx               |    2 +-
 .../docs/support/troubleshooting/index.mdx    |    2 +-
 .../restoring-visitor-ips/index.mdx           |    2 +-
 .../restoring-original-visitor-ips.mdx        |    5 +-
 src/content/docs/tenant/how-to/index.mdx      |    2 +-
 src/content/docs/tenant/index.mdx             |    8 +-
 src/content/docs/tenant/reference/index.mdx   |    2 +-
 .../advanced-topics/best-practices.mdx        |    2 -
 .../terraform/how-to/create-partial-zone.mdx  |    3 +-
 .../how-to/create-secondary-zone.mdx          |    4 +-
 .../authentication-error-dns-records.mdx      |    2 +-
 src/content/docs/terraform/tutorial/index.mdx |   36 +-
 src/content/docs/time-services/index.mdx      |    2 +-
 .../docs/time-services/roughtime/index.mdx    |    2 +-
 .../docs/time-services/roughtime/recipes.mdx  |   32 +-
 src/content/docs/time-services/tos.mdx        |    2 +-
 .../tunnel/advanced/origin-parameters.mdx     |   16 +-
 .../docs/tunnel/advanced/run-parameters.mdx   |   24 +-
 src/content/docs/tunnel/changelog.mdx         |    5 +-
 .../tunnel/deployment-guides/terraform.mdx    |    1 -
 .../tunnel/downloads/system-requirements.mdx  |    7 +-
 src/content/docs/tunnel/troubleshooting.mdx   |    1 +
 .../hostname-management/any-hostname.mdx      |   69 +-
 .../hostname-management/index.mdx             |    5 +-
 .../hostname-management/pre-clearance.mdx     |   17 +-
 .../additional-configuration/index.mdx        |    3 +-
 .../pre-clearance-support.mdx                 |    3 +-
 .../docs/turnstile/concepts/challenges.mdx    |    1 -
 src/content/docs/turnstile/concepts/index.mdx |    5 +-
 .../turnstile/extensions/google-firebase.mdx  |   35 +-
 .../docs/turnstile/extensions/index.mdx       |    3 +-
 .../turnstile/extensions/pages-plugin.mdx     |    1 -
 .../turnstile/extensions/waiting-room.mdx     |    1 -
 .../get-started/widget-management/api.mdx     |   61 +-
 .../get-started/widget-management/index.mdx   |    4 +-
 .../widget-management/terraform.mdx           |   10 +-
 .../docs/turnstile/migration/hcaptcha.mdx     |    2 +-
 .../docs/turnstile/reference/index.mdx        |    3 +-
 .../reference/supported-browsers.mdx          |    1 -
 .../reference/supported-languages.mdx         |    1 -
 .../reference/turnstile-privacy-addendum.mdx  |    1 -
 .../challenge-solve-issues.mdx                |    1 -
 .../client-side-errors/index.mdx              |  137 +-
 .../docs/turnstile/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/rotate-secret-key.mdx     |    3 +-
 .../turnstile/troubleshooting/testing.mdx     |   67 +-
 .../turnstile/turnstile-analytics/index.mdx   |    5 +-
 .../excluding-turnstile-from-e2e-tests.mdx    |   54 +-
 .../fraud-detection-with-ephemeral-ids.mdx    |    4 +-
 ...ating-turnstile-waf-and-bot-management.mdx |    8 +-
 .../docs/use-cases/e-commerce/performance.mdx |    2 +-
 .../encrypt-all-keep-site-secure.mdx          |   27 +-
 .../protect-sensitive-forms-fraud-abuse.mdx   |   77 +-
 .../stop-account-takeover-attacks.mdx         |   42 +-
 .../solutions/stop-malicious-bots.mdx         |    9 +-
 .../docs/use-cases/web-apps/performance.mdx   |    3 +-
 .../docs/vectorize/best-practices/index.mdx   |    2 +-
 .../vectorize/best-practices/list-vectors.mdx |    3 +-
 src/content/docs/vectorize/demos.mdx          |   11 +-
 .../docs/vectorize/examples/agents.mdx        |    2 +-
 src/content/docs/vectorize/examples/index.mdx |    2 +-
 .../docs/vectorize/get-started/index.mdx      |    2 +-
 src/content/docs/vectorize/platform/index.mdx |    2 +-
 .../docs/vectorize/reference/index.mdx        |    2 +-
 src/content/docs/version-management/about.mdx |    6 +-
 .../how-to/compare-versions.mdx               |    2 +-
 .../how-to/environments.mdx                   |   33 +-
 .../docs/version-management/how-to/index.mdx  |    4 +-
 .../version-management/how-to/versions.mdx    |    4 +-
 .../reference/available-configurations.mdx    |   14 +-
 .../version-management/reference/index.mdx    |    4 +-
 .../reference/read-only-environments.mdx      |    7 +-
 .../waf/custom-rules/create-dashboard.mdx     |    1 -
 .../use-cases/sequence-custom-rules.mdx       |    2 +-
 src/content/docs/waf/glossary.mdx             |    3 +-
 src/content/docs/waf/managed-rules/index.mdx  |    1 -
 src/content/docs/waf/tools/index.mdx          |    1 -
 src/content/docs/waf/tools/privacy-pass.mdx   |    9 +-
 src/content/docs/waf/troubleshooting/faq.mdx  |    1 +
 src/content/docs/waiting-room/about.mdx       |    6 +-
 .../additional-options/create-events.mdx      |   33 +-
 .../waiting-room/additional-options/index.mdx |    3 +-
 .../additional-options/ssl-for-saas.mdx       |    1 -
 .../waiting-room-rules/index.mdx              |    3 +-
 .../docs/waiting-room/api-reference.mdx       |    1 -
 src/content/docs/waiting-room/glossary.mdx    |    3 +-
 .../how-to/control-user-session.mdx           |    8 +-
 .../how-to/edit-delete-waiting-room.mdx       |   41 +-
 .../docs/waiting-room/how-to/index.mdx        |    3 +-
 .../waiting-room/how-to/json-response.mdx     |    2 -
 .../how-to/monitor-waiting-room.mdx           |   45 +-
 .../how-to/place-waiting-room.mdx             |    5 +-
 .../how-to/waiting-room-dashboard.mdx         |    3 +-
 src/content/docs/waiting-room/plans.mdx       |    3 +-
 .../reference/configuration-settings.mdx      |   11 +-
 .../docs/waiting-room/reference/index.mdx     |    3 +-
 .../reference/waiting-room-api.mdx            |   21 +-
 .../reference/waiting-room-cookie.mdx         |   12 +-
 .../docs/waiting-room/troubleshooting.mdx     |   50 +-
 .../docs/warp-client/get-started/linux.mdx    |   21 +-
 .../docs/warp-client/known-issues-and-faq.mdx |    8 +-
 .../docs/warp-client/legal/3rdparty.mdx       | 1139 +++++++----------
 src/content/docs/warp-client/legal/index.mdx  |    7 +-
 src/content/docs/warp-client/privacy.mdx      |    1 -
 .../configuration-options/filters.mdx         |    3 +-
 .../configuration-options/index.mdx           |    3 +-
 .../data-metrics/core-web-vitals.mdx          |    5 +-
 .../data-origin-and-collection.mdx            |    2 +-
 .../web-analytics/data-metrics/dimensions.mdx |   21 +-
 .../data-metrics/high-level-metrics.mdx       |    9 +-
 .../docs/web-analytics/data-metrics/index.mdx |    3 +-
 .../data-metrics/page-load-time-summary.mdx   |    1 -
 src/content/docs/web-analytics/faq.mdx        |   14 +-
 .../web-analytics/get-started/rum-beacon.mdx  |    3 +-
 .../get-started/web-analytics-spa.mdx         |   10 +-
 src/content/docs/web-analytics/limits.mdx     |    1 -
 src/content/docs/web3/about.mdx               |    2 +-
 src/content/docs/web3/api-reference.mdx       |    1 -
 .../web3/ethereum-gateway/concepts/index.mdx  |    3 +-
 .../web3/ethereum-gateway/reference/index.mdx |    3 +-
 .../reference/kill-switches.mdx               |    7 +-
 .../reference/rinkeby-deprecation.mdx         |   57 +-
 .../reference/supported-networks.mdx          |    1 -
 src/content/docs/web3/how-to/index.mdx        |    3 +-
 .../docs/web3/how-to/use-ipfs-gateway.mdx     |    1 -
 .../web3/ipfs-gateway/concepts/dnslink.mdx    |    1 -
 .../docs/web3/ipfs-gateway/concepts/index.mdx |    3 +-
 .../reference/automated-deployment.mdx        |    7 +-
 .../web3/ipfs-gateway/reference/index.mdx     |    3 +-
 .../peering-with-content-providers.mdx        |  129 +-
 .../reference/updating-for-ipfs.mdx           |    7 +-
 .../web3/ipfs-gateway/troubleshooting.mdx     |    1 -
 .../web3/reference/gateway-dns-records.mdx    |    5 +-
 .../docs/web3/reference/gateway-status.mdx    |    1 -
 src/content/docs/web3/reference/index.mdx     |    3 +-
 .../docs/web3/reference/migration-guide.mdx   |    3 +-
 src/content/docs/workers-ai/agents.mdx        |   13 +-
 src/content/docs/workers-ai/api-reference.mdx |    1 -
 .../workers-ai/configuration/bindings.mdx     |   26 +-
 .../configuration/hugging-face-chat-ui.mdx    |   34 +-
 .../embedded/examples/fetch.mdx               |   36 +-
 .../function-calling/embedded/examples/kv.mdx |    1 +
 .../embedded/examples/openapi.mdx             |   22 +-
 .../function-calling/embedded/index.mdx       |    4 +-
 .../docs/workers-ai/get-started/dashboard.mdx |    5 +-
 .../docs/workers-ai/get-started/index.mdx     |    4 +-
 .../docs/workers-ai/get-started/rest-api.mdx  |    3 +-
 src/content/docs/workers-ai/guides/agents.mdx |    2 +-
 ...generation-using-deepseek-coder-models.mdx |   18 +-
 ...choose-the-right-text-generation-model.mdx |   72 +-
 .../docs/workers-ai/platform/data-usage.mdx   |    8 +-
 .../docs/workers-ai/platform/pricing.mdx      |   62 +-
 .../docs/workers-vpc/configuration/index.mdx  |    2 +-
 .../configuration/vpc-services/terraform.mdx  |    1 +
 .../docs/workers-vpc/examples/private-api.mdx |    4 +-
 .../examples/private-s3-bucket.mdx            |    4 +-
 .../route-across-private-services.mdx         |   15 +-
 .../workers/ci-cd/builds/automatic-prs.mdx    |    1 +
 .../workers/ci-cd/builds/build-caching.mdx    |   18 +-
 .../docs/workers/ci-cd/builds/build-image.mdx |    5 +-
 .../workers/ci-cd/builds/configuration.mdx    |   12 +-
 .../docs/workers/ci-cd/builds/index.mdx       |   10 +-
 .../ci-cd/builds/limits-and-pricing.mdx       |   24 +-
 .../workers/ci-cd/builds/troubleshoot.mdx     |    1 +
 .../ci-cd/external-cicd/github-actions.mdx    |    2 +
 .../ci-cd/external-cicd/gitlab-cicd.mdx       |    1 +
 .../configuration/integrations/index.mdx      |   22 +-
 .../configuration/routing/custom-domains.mdx  |   36 +-
 .../workers/configuration/routing/routes.mdx  |   14 +-
 .../sites/start-from-existing.mdx             |   36 +-
 .../sites/start-from-scratch.mdx              |   50 +-
 .../configuration/sites/start-from-worker.mdx |   20 +-
 .../versions-and-deployments/index.mdx        |    2 +-
 .../version-overrides.mdx                     |   24 +-
 .../configuration/workers-with-page-rules.mdx |   50 +-
 .../third-party-integrations/supabase.mdx     |    4 +-
 .../third-party-integrations/turso.mdx        |    6 +-
 .../third-party-integrations/upstash.mdx      |    3 +-
 .../third-party-integrations/xata.mdx         |    1 -
 .../development-testing/multi-workers.mdx     |   44 +-
 .../workers/development-testing/testing.mdx   |    2 +-
 .../development-testing/vite-plugin.mdx       |    2 +-
 .../docs/workers/examples/103-early-hints.mdx |    2 +-
 .../docs/workers/examples/ab-testing.mdx      |    1 -
 .../accessing-the-cloudflare-object.mdx       |    1 -
 .../workers/examples/aggregate-requests.mdx   |    1 -
 .../docs/workers/examples/alter-headers.mdx   |    1 -
 .../workers/examples/auth-with-headers.mdx    |    1 -
 .../docs/workers/examples/basic-auth.mdx      |    1 -
 .../docs/workers/examples/block-on-tls.mdx    |    1 -
 .../workers/examples/bulk-origin-proxy.mdx    |    1 -
 .../docs/workers/examples/bulk-redirects.mdx  |    1 -
 .../docs/workers/examples/cache-api.mdx       |    1 -
 .../workers/examples/cache-post-request.mdx   |    1 -
 .../docs/workers/examples/cache-tags.mdx      |    1 -
 .../workers/examples/cache-using-fetch.mdx    |    5 +-
 .../workers/examples/conditional-response.mdx |    1 -
 .../workers/examples/cors-header-proxy.mdx    |    2 -
 .../examples/country-code-redirect.mdx        |    1 -
 .../workers/examples/data-loss-prevention.mdx |    1 -
 .../docs/workers/examples/debugging-logs.mdx  |    1 -
 .../workers/examples/extract-cookie-value.mdx |    1 -
 .../docs/workers/examples/fetch-json.mdx      |    1 -
 .../examples/geolocation-app-weather.mdx      |    1 -
 .../examples/geolocation-custom-styling.mdx   |    1 -
 .../examples/geolocation-hello-world.mdx      |    1 -
 .../workers/examples/hot-link-protection.mdx  |    1 -
 .../examples/modify-request-property.mdx      |    1 -
 .../docs/workers/examples/modify-response.mdx |    1 -
 .../examples/multiple-cron-triggers.mdx       |    1 -
 .../workers/examples/openai-sdk-streaming.mdx |    1 -
 .../docs/workers/examples/post-json.mdx       |    1 -
 .../protect-against-timing-attacks.mdx        |    1 -
 .../docs/workers/examples/read-post.mdx       |    1 -
 .../docs/workers/examples/return-html.mdx     |    1 -
 .../docs/workers/examples/rewrite-links.mdx   |    1 -
 .../workers/examples/signing-requests.mdx     |    1 -
 .../examples/turnstile-html-rewriter.mdx      |    1 -
 .../docs/workers/examples/websockets.mdx      |    4 +-
 .../framework-guides/ai-and-agents/index.mdx  |   13 +-
 .../workers/framework-guides/apis/index.mdx   |    9 +-
 .../docs/workers/framework-guides/index.mdx   |    9 +-
 .../framework-guides/mobile-apps/expo.mdx     |    2 +-
 .../framework-guides/mobile-apps/index.mdx    |    9 +-
 .../framework-guides/web-apps/astro.mdx       |   24 +-
 .../framework-guides/web-apps/index.mdx       |    9 +-
 .../web-apps/more-web-frameworks/analog.mdx   |   18 +-
 .../web-apps/more-web-frameworks/angular.mdx  |    6 +-
 .../more-web-frameworks/docusaurus.mdx        |    2 -
 .../web-apps/more-web-frameworks/hono.mdx     |    2 -
 .../web-apps/more-web-frameworks/index.mdx    |    2 +-
 .../web-apps/more-web-frameworks/nuxt.mdx     |   18 +-
 .../web-apps/more-web-frameworks/solid.mdx    |   18 +-
 .../web-apps/more-web-frameworks/waku.mdx     |   14 +-
 .../framework-guides/web-apps/nextjs.mdx      |   48 +-
 .../framework-guides/web-apps/redwoodsdk.mdx  |    2 +-
 .../framework-guides/web-apps/sveltekit.mdx   |   24 +-
 .../framework-guides/web-apps/vike.mdx        |   32 +-
 .../workers/framework-guides/web-apps/vue.mdx |   24 +-
 .../docs/workers/get-started/dashboard.mdx    |   11 +-
 .../docs/workers/get-started/quickstarts.mdx  |    1 -
 .../workers/languages/javascript/index.mdx    |   13 +-
 .../docs/workers/observability/errors.mdx     |   58 +-
 .../exporting-opentelemetry-data/axiom.mdx    |   22 +-
 .../grafana-cloud.mdx                         |   31 +-
 .../honeycomb.mdx                             |    8 +-
 .../exporting-opentelemetry-data/index.mdx    |   32 +-
 .../exporting-opentelemetry-data/posthog.mdx  |   47 +-
 .../exporting-opentelemetry-data/sentry.mdx   |   29 +-
 .../workers/observability/logs/logpush.mdx    |   91 +-
 .../observability/logs/real-time-logs.mdx     |    1 +
 .../observability/logs/workers-logs.mdx       |    6 +-
 .../observability/metrics-and-analytics.mdx   |    1 +
 .../workers/observability/source-maps.mdx     |   15 +-
 src/content/docs/workers/platform/betas.mdx   |   10 +-
 .../platform/built-with-cloudflare.mdx        |    2 +-
 .../changelog/historical-changelog.mdx        |  448 +++----
 .../docs/workers/platform/changelog/index.mdx |    2 +-
 .../docs/workers/platform/known-issues.mdx    |   10 +-
 src/content/docs/workers/platform/pricing.mdx |    6 +-
 .../workers/reference/how-the-cache-works.mdx |    4 -
 .../workers/reference/how-workers-works.mdx   |   16 +-
 .../docs/workers/reference/protocols.mdx      |   14 +-
 .../docs/workers/reference/security-model.mdx |    6 +-
 .../workers/runtime-apis/bindings/index.mdx   |   55 +-
 .../runtime-apis/bindings/rate-limit.mdx      |   54 +-
 .../bindings/service-bindings/http.mdx        |   22 +-
 .../workers/runtime-apis/bindings/stream.mdx  |    1 -
 .../bindings/version-metadata.mdx             |    2 +-
 .../docs/workers/runtime-apis/cache.mdx       |  105 +-
 .../docs/workers/runtime-apis/console.mdx     |   44 +-
 .../docs/workers/runtime-apis/encoding.mdx    |   44 +-
 .../docs/workers/runtime-apis/eventsource.mdx |   75 +-
 .../workers/runtime-apis/handlers/fetch.mdx   |   27 +-
 .../workers/runtime-apis/handlers/index.mdx   |    4 +-
 .../workers/runtime-apis/handlers/tail.mdx    |  227 ++--
 .../docs/workers/runtime-apis/headers.mdx     |   19 +-
 .../workers/runtime-apis/messagechannel.mdx   |   16 +-
 .../docs/workers/runtime-apis/nodejs/util.mdx |    6 +-
 .../docs/workers/runtime-apis/performance.mdx |    2 +-
 .../runtime-apis/rpc/error-handling.mdx       |    6 +-
 .../runtime-apis/rpc/reserved-methods.mdx     |   14 +-
 .../runtime-apis/streams/readablestream.mdx   |   44 +-
 .../streams/readablestreambyobreader.mdx      |   39 +-
 .../streams/readablestreamdefaultreader.mdx   |   36 +-
 .../runtime-apis/streams/transformstream.mdx  |   77 +-
 .../runtime-apis/streams/writablestream.mdx   |   35 +-
 .../streams/writablestreamdefaultwriter.mdx   |   58 +-
 .../docs/workers/runtime-apis/tcp-sockets.mdx |  183 ++-
 .../docs/workers/runtime-apis/web-crypto.mdx  |  425 ++----
 .../runtime-apis/webassembly/index.mdx        |   16 +-
 .../docs/workers/runtime-apis/websockets.mdx  |  177 +--
 .../routing/full-stack-application.mdx        |    5 +-
 .../testing/miniflare/storage/cache.md        |    4 +-
 .../testing/vitest-integration/recipes.mdx    |    2 +-
 .../docs/workers/vite-plugin/tutorial.mdx     |    1 +
 src/content/docs/workers/wrangler/api.mdx     |   52 +-
 .../docs/workers/wrangler/commands/r2.mdx     |    1 -
 .../docs/workers/wrangler/configuration.mdx   |   46 +-
 .../docs/workers/wrangler/custom-builds.mdx   |   15 +-
 .../docs/workers/wrangler/deprecations.mdx    |  122 +-
 .../wrangler/migration/update-v2-to-v3.mdx    |    2 -
 .../v1-to-v2/wrangler-legacy/commands.mdx     |    8 +-
 src/content/docs/workflows/build/index.mdx    |    2 +-
 .../docs/workflows/build/test-workflows.mdx   |    2 +-
 .../docs/workflows/examples/agents.mdx        |    2 +-
 .../docs/workflows/examples/backup-d1.mdx     |    1 -
 .../docs/workflows/examples/send-invoices.mdx |    1 -
 .../docs/workflows/examples/twilio.mdx        |    1 -
 .../workflows/examples/wait-for-event.mdx     |   13 +-
 .../docs/workflows/observability/index.mdx    |    4 +-
 .../docs/workflows/python/bindings.mdx        |    2 +-
 .../docs/workflows/reference/changelog.mdx    |    4 +-
 .../docs/workflows/reference/glossary.mdx     |    2 +-
 .../docs/workflows/reference/index.mdx        |    2 +-
 .../docs/workflows/reference/pricing.mdx      |   26 +-
 .../workflows/reference/wrangler-commands.mdx |    4 +-
 src/content/docs/workflows/videos.mdx         |   10 +-
 .../advanced/datalayer-compatibility.mdx      |   11 +-
 .../zaraz/advanced/domains-not-proxied.mdx    |    1 -
 .../zaraz/advanced/google-consent-mode.mdx    |   27 +-
 .../docs/zaraz/advanced/import-export.mdx     |    9 +-
 src/content/docs/zaraz/advanced/index.mdx     |    3 +-
 .../load-custom-managed-component.mdx         |    3 +-
 .../docs/zaraz/advanced/load-selectively.mdx  |    3 -
 .../zaraz/advanced/load-zaraz-manually.mdx    |   15 +-
 .../docs/zaraz/advanced/using-jsonata.mdx     |   37 +-
 .../docs/zaraz/consent-management/api.mdx     |  182 +--
 .../zaraz/consent-management/custom-css.mdx   |    4 +-
 .../enable-consent-management.mdx             |    9 +-
 .../consent-management/iab-tcf-compliance.mdx |    4 +-
 .../docs/zaraz/consent-management/index.mdx   |   27 +-
 .../custom-actions/additional-fields.mdx      |    7 +-
 .../zaraz/custom-actions/create-action.mdx    |    3 +-
 .../zaraz/custom-actions/create-trigger.mdx   |    3 +-
 .../custom-actions/edit-tools-and-actions.mdx |   15 +-
 .../zaraz/custom-actions/edit-triggers.mdx    |    7 +-
 src/content/docs/zaraz/embeds.mdx             |    9 +-
 src/content/docs/zaraz/get-started.mdx        |    3 +-
 src/content/docs/zaraz/history/index.mdx      |    3 +-
 src/content/docs/zaraz/history/versions.mdx   |   16 +-
 src/content/docs/zaraz/http-events-api.mdx    |   98 +-
 src/content/docs/zaraz/monitoring/index.mdx   |    5 +-
 src/content/docs/zaraz/pricing-info.mdx       |    7 +-
 src/content/docs/zaraz/reference/context.mdx  |    9 -
 src/content/docs/zaraz/reference/index.mdx    |    3 +-
 .../zaraz/reference/properties-reference.mdx  |   84 +-
 src/content/docs/zaraz/reference/settings.mdx |   18 +-
 .../docs/zaraz/reference/supported-tools.mdx  |    1 -
 .../docs/zaraz/variables/create-variables.mdx |    3 +-
 .../docs/zaraz/variables/edit-variables.mdx   |    7 +-
 src/content/docs/zaraz/variables/index.mdx    |    3 +-
 .../docs/zaraz/variables/worker-variables.mdx |  100 +-
 src/content/docs/zaraz/web-api/debug-mode.mdx |    6 +-
 src/content/docs/zaraz/web-api/ecommerce.mdx  |    3 +-
 src/content/docs/zaraz/web-api/index.mdx      |    3 +-
 src/content/docs/zaraz/web-api/set.mdx        |   21 +-
 .../partials/1.1.1.1/captive-portals.mdx      |    2 +-
 src/content/partials/agents/unique-agents.mdx |    3 +-
 .../ai-crawl-control/plan-comparison.mdx      |   11 +-
 .../ai-gateway/analytics-dashboard.mdx        |    1 -
 src/content/partials/ai-gateway/logging.mdx   |    1 +
 .../ai-gateway/universal-gateway-example.mdx  |    1 -
 .../partials/ai-search/rest-api-auth.mdx      |    2 +-
 .../customer_metadata_boundary_error.mdx      |    5 +-
 .../network-analytics-requirements.mdx        |    7 +-
 .../network-analytics-v1-deprecation.mdx      |    1 -
 .../partials/api-shield/label-methodology.mdx |    9 +-
 .../api-shield/mtls-api-shield-support.mdx    |    1 -
 .../partials/api-shield/mtls-create-rule.mdx  |    5 +-
 .../partials/api-shield/rate-limit-user.mdx   |    1 -
 .../required-session-identifiers.mdx          |    1 -
 .../sequence-mitigation-availability.mdx      |    3 +-
 .../api-shield/session-identifiers.mdx        |    5 +-
 .../partials/billing/two-payment-methods.mdx  |    1 -
 .../bots/about-plan-considerations.mdx        |    5 +-
 .../partials/bots/analytics-features.mdx      |    1 -
 .../partials/bots/bfm-change-notice.mdx       |    1 -
 .../partials/bots/bm-analytics-features.mdx   |    9 +-
 .../bots/bot-settings-vs-custom-rules.mdx     |   18 +-
 src/content/partials/bots/bots-ad.mdx         |    1 -
 src/content/partials/bots/bots-cookie.mdx     |    3 +-
 src/content/partials/bots/bots-heuristics.mdx |    3 +-
 src/content/partials/bots/bots-jsd.mdx        |    1 -
 src/content/partials/bots/bots-ml.mdx         |    5 +-
 .../partials/bots/buttons-plan-pages.mdx      |   16 +-
 .../content-security-policy-limitation.mdx    |    5 +-
 .../partials/bots/disable-cf-bm-cookie.mdx    |    1 -
 .../partials/bots/endpoint-label-warning.mdx  |    7 +-
 src/content/partials/bots/execution-order.mdx |    2 +-
 src/content/partials/bots/flexible-sbfm.mdx   |    3 +-
 src/content/partials/bots/ja3-ja4-null.mdx    |    3 +-
 .../partials/bots/jsd-availability.mdx        |    3 +-
 .../partials/bots/plan-get-started.mdx        |    1 -
 src/content/partials/bots/plan-intro.mdx      |    1 -
 src/content/partials/bots/sequence-rules.mdx  |    7 +-
 .../bots/signals-intelligence-and-ja4.mdx     |    7 +-
 src/content/partials/bots/verified-bots.mdx   |    1 -
 .../improve-blurry-screenshot-resolution.mdx  |   15 +-
 .../partials/byoip/cloudflare-asn-callout.mdx |    2 +-
 src/content/partials/byoip/loa.mdx            |    2 +-
 .../byoip/validate-prefix-endpoint.mdx        |    1 -
 .../cache/cache-reserve-billing-note.mdx      |    3 -
 .../cache/cache-reserve-eligibility.mdx       |    2 +-
 .../partials/cache/cache-reserve-intro.mdx    |    2 +-
 .../partials/cache/cache-reserve-limits.mdx   |    2 +-
 .../cache/cache-reserve-operations.mdx        |    2 +-
 src/content/partials/cache/edge-ttl.mdx       |    2 +-
 .../partials/cache/regional-tiered-cache.mdx  |    2 +-
 .../partials/cache/smart-tiered-cache.mdx     |    2 +-
 .../cf-clearance-cookie.mdx                   |    3 +-
 .../create-challenge-page.mdx                 |    5 +-
 .../apex-proxying-process.mdx                 |    3 -
 .../cname-target-process.mdx                  |    1 -
 .../create-custom-hostname-api.mdx            |    6 +-
 .../create-custom-hostname-limitations.mdx    |    7 +-
 .../create-custom-hostname.mdx                |   13 +-
 .../custom-origin-server-definition.mdx       |    5 +-
 .../delete-custom-hostname-dash.mdx           |    1 -
 .../get-started-initial-setup-preamble.mdx    |    1 -
 .../get-started-per-hostname.mdx              |    5 +-
 .../get-started-prereqs.mdx                   |    7 +-
 .../get-started-service-continuation.mdx      |    1 -
 .../http-dcv-situation.mdx                    |    5 +-
 .../issue-certs-preamble.mdx                  |    1 -
 .../provider-guide-compatibility.mdx          |    7 +-
 .../provider-guide-zone-hold.mdx              |    2 +-
 .../regional-services.mdx                     |    1 -
 .../saas-customer-churn.mdx                   |    1 -
 .../same-name-as-zone.mdx                     |    3 +-
 .../ssl-for-saas-create-hostname.mdx          |    1 -
 .../ssl-for-saas-definition.mdx               |    1 -
 .../ssl-for-saas-plan-limitation.mdx          |    3 -
 .../ssl-for-saas-validate-patch.mdx           |    1 -
 .../txt-dcv-situation.mdx                     |    1 -
 .../txt-validation_api.mdx                    |   83 +-
 .../txt-validation_dashboard.mdx              |    1 -
 .../txt-validation_post.mdx                   |    3 -
 .../txt-validation_preamble.mdx               |    1 -
 .../update-dcv-method.mdx                     |    1 -
 .../wildcard-hostname-reqs.mdx                |    1 -
 .../access/access-block-page.mdx              |    7 +-
 .../cloudflare-one/access/add-mtls-cert.mdx   |   21 +-
 .../cloudflare-one/access/add-target.mdx      |   17 +-
 .../cloudflare-one/access/app-launcher.mdx    |    4 +-
 .../cloudflare-one/access/bookmarks.mdx       |    3 +-
 .../access/create-service-token.mdx           |    3 +-
 .../access/enable-scim-on-dashboard.mdx       |   14 +-
 .../access/entra-id-terraform.mdx             |    1 -
 .../cloudflare-one/access/idp-integration.mdx |    4 +-
 .../access/isolation-prereqs.mdx              |    1 -
 .../access/saas-apps/miro-sso.mdx             |    5 +-
 .../access/saas-apps/saas-sessions.mdx        |    2 +-
 .../access/saas-apps/salesforce-sso.mdx       |    1 -
 .../access/scim-requires-login.mdx            |    2 +-
 .../access/secure-tunnel-with-access.mdx      |    1 -
 .../self-hosted-app/advanced-settings.mdx     |    1 -
 .../browser-rendering-policies.mdx            |    3 +-
 .../self-hosted-app/generic-public-app.mdx    |   25 +-
 .../self-hosted-app/product-compatibility.mdx |    8 +-
 .../access/self-hosted-app/ssh-sessions.mdx   |    2 +-
 .../access/session-duration.mdx               |    1 -
 .../access/short-lived-certs-intro.mdx        |    4 +-
 .../partials/cloudflare-one/access/tags.mdx   |    1 -
 .../access/verify-scim-provisioning.mdx       |    2 +-
 .../partials/cloudflare-one/aws-resolver.mdx  |    3 +-
 .../casb/casb-dlp-integrations.mdx            |    1 -
 .../casb/microsoft/m365-copilot-findings.mdx  |    2 +-
 .../cloudflare-one/choose-team-name.mdx       |    1 -
 .../clientless-browser-isolation.mdx          |    3 +-
 .../dex/notifications-intro.mdx               |    2 +-
 .../partials/cloudflare-one/dex/pcaps-run.mdx |    2 +-
 ...-use-case-1-3-create-quarantine-policy.mdx |    8 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 ...ase-configure-quarantine-notifications.mdx |    1 -
 .../deployment/set-up-mx-inline-step.mdx      |    3 +-
 .../dispositions-and-attributes.mdx           |   10 +-
 .../email-security/domain-information.mdx     |   20 +-
 .../email-security/enable-logs.mdx            |    3 +-
 .../onboarding-prerequisites.mdx              |    3 +-
 .../cloudflare-one/gateway/add-logo-image.mdx |    1 -
 .../gateway/debugging-policies.mdx            |    1 -
 .../gateway/egress-selector-cgnat-ips.mdx     |    3 +-
 .../gateway/egress-selector-onramps.mdx       |   14 +-
 .../gateway/egress-selector-split-tunnels.mdx |    4 +-
 .../gateway/enable-tls-decryption.mdx         |    2 +-
 .../policies/do-not-inspect-applications.mdx  |    3 +-
 .../policies/egress-destination-ip.mdx        |    1 -
 ...trict-access-to-private-networks-allow.mdx |    8 +-
 ...trict-access-to-private-networks-block.mdx |    2 +-
 ...estrict-access-to-private-networks-dns.mdx |    8 +-
 .../gateway/resolver-policies-intro.mdx       |    1 -
 .../gateway/selectors/category-options.mdx    |    1 -
 .../gateway/selectors/destination-country.mdx |    7 +-
 .../gateway/selectors/device-posture.mdx      |    1 -
 .../gateway/selectors/dns-resolver-ip.mdx     |    1 -
 .../gateway/selectors/doh-subdomain.mdx       |    1 -
 .../gateway/selectors/oidc-claims.mdx         |    4 +-
 .../gateway/selectors/protocol.mdx            |    1 -
 .../gateway/selectors/query-record-type.mdx   |    1 -
 .../gateway/selectors/security-categories.mdx |    1 -
 .../gateway/selectors/source-country-dns.mdx  |    7 +-
 .../gateway/selectors/source-country-http.mdx |    7 +-
 .../gateway/selectors/source-country.mdx      |    7 +-
 .../gateway/selectors/source-ip-dns.mdx       |    1 -
 .../gateway/selectors/source-ip-resolver.mdx  |    1 -
 .../gateway/selectors/user-email.mdx          |    4 +-
 .../gateway/selectors/user-group-email.mdx    |    6 +-
 .../gateway/selectors/user-group-ids.mdx      |    6 +-
 .../gateway/selectors/user-group-names.mdx    |    6 +-
 .../gateway/selectors/user-name.mdx           |    6 +-
 .../gateway/selectors/users-dns.mdx           |   16 +-
 .../gateway/selectors/users-http.mdx          |   16 +-
 .../gateway/selectors/users.mdx               |   13 +-
 .../partials/cloudflare-one/gateway/value.mdx |    4 +-
 .../posture/configure-posture-check.mdx       |    3 +-
 .../posture/prereqs-warp-is-deployed.mdx      |    1 -
 .../cloudflare-one/ssh/decrypt-ssh-log.mdx    |    8 +-
 .../cloudflare-one/ssh/public-key.mdx         |    6 +-
 .../cloudflare-one/ssh/restart-server.mdx     |    2 +-
 .../cloudflare-one/ssh/ssh-proxy-ca-note.mdx  |    3 +-
 .../cloudflare-one/ssh/ssh-proxy-ca.mdx       |    2 +-
 .../cloudflare-one/ssh/upload-ssh-key.mdx     |    2 +-
 .../terraform/cloudflare-resources.mdx        |  312 ++---
 .../terraform/gcp-resources.mdx               |  170 +--
 .../cloudflare-one/terraform/providers-v5.mdx |    2 +-
 .../cloudflare-one/terraform/providers.mdx    |   76 +-
 .../troubleshooting/browser-isolation.mdx     |   18 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    4 +
 .../cloudflare-one/troubleshooting/dex.mdx    |    3 +
 .../troubleshooting/email-security.mdx        |   23 +-
 .../troubleshooting/gateway.mdx               |   13 +-
 .../cloudflare-one/tunnel/1033-error.mdx      |    3 +-
 .../tunnel/account-scoped-roles.mdx           |    5 +-
 .../tunnel/add-published-application.mdx      |   13 +-
 .../cloudflared-replicas-diagram.mdx          |    1 -
 .../load-balancer-tcp-monitors.mdx            |    7 +-
 .../availability/tunnel-capacity-baseline.mdx |    7 +-
 .../availability/tunnel-capacity-intro.mdx    |    1 -
 .../tunnel/catch-all-policy.mdx               |    1 -
 .../tunnel/cgnat-split-tunnels.mdx            |    1 -
 .../cloudflare-one/tunnel/create-tunnel.mdx   |    3 +-
 .../deployment-guides/cloud-create-tunnel.mdx |    3 +-
 .../deployment-guides/cloud-private-ip.mdx    |   22 +-
 .../cloud-public-hostname.mdx                 |    1 -
 .../tunnel/diagnostics/docker.mdx             |   33 +-
 .../tunnel/diagnostics/tunnel-diag-file.mdx   |   24 +-
 .../tunnel/dns-cloudflare-settings.mdx        |    1 -
 .../tunnel/dns-records-intro.mdx              |    1 -
 .../cloudflare-one/tunnel/grpc-support.mdx    |    1 -
 .../tunnel/hostname-format-restrictions.mdx   |   21 +-
 .../tunnel/install-and-run-tunnel.mdx         |    3 +-
 .../locally-managed/tunnel-permissions.mdx    |   20 +-
 .../tunnel/logs/filter-logs.mdx               |    8 +-
 .../tunnel/logs/view-logs-dashboard.mdx       |    1 -
 .../tunnel/logs/view-logs-on-server.mdx       |    1 -
 .../tunnel/metrics/cloudflared.mdx            |    2 +-
 .../tunnel/origin-parameters.mdx              |    4 +-
 .../cloudflare-one/tunnel/package-manager.mdx |    3 +-
 .../cloudflare-one/tunnel/protocols-table.mdx |   26 +-
 .../cloudflare-one/tunnel/run-parameters.mdx  |    6 +-
 .../cloudflare-one/tunnel/tunnel-status.mdx   |   12 +-
 .../tunnel/warp-cli-target-list.mdx           |    2 +-
 .../tunnel/warp-to-tunnel-route-ips.mdx       |   66 +-
 .../warp/client-notification-lag.mdx          |    3 +-
 .../warp/client-orchestration-ips.mdx         |    1 -
 .../warp/device-enrollment-mtls.mdx           |    7 +-
 .../warp/enroll-ios-android.mdx               |    3 +-
 .../cloudflare-one/warp/ldf-best-practice.mdx |    2 +-
 .../warp/managed-networks-sha-256.mdx         |    2 +-
 .../cloudflare-one/warp/manually-reauth.mdx   |    2 +-
 .../cloudflare-one/warp/mdm-policy-file.mdx   |    9 +-
 .../cloudflare-one/warp/os-version-semver.mdx |    3 +-
 .../warp/sha-256-fingerprint.mdx              |    2 +-
 .../warp/support-ticket-best-practices.mdx    |    4 +-
 .../warp/system-requirements/linux.mdx        |   19 +-
 .../warp/system-requirements/macOS.mdx        |   19 +-
 .../warp/system-requirements/windows.mdx      |   19 +-
 .../cloudflare-one/warp/vpn-ip-traffic.mdx    |   10 +-
 .../cloudflare-one/warp/warp-modes.mdx        |    4 +-
 .../partials/containers/instance-types.mdx    |    4 +-
 .../d1/d1-do-supported-sqlite-extensions.mdx  |    4 +-
 .../partials/d1/generate-d1-api-token.mdx     |    2 +-
 .../advanced-ddos/dns-protection-intro.mdx    |    2 +-
 .../advanced-ddos/dns-setup.mdx               |    2 +-
 .../mt-advanced-ddos-systems-onboarding.mdx   |    2 +-
 .../advanced-ddos/tcp-protection-intro.mdx    |    2 +-
 .../advanced-ddos/tcp-setup.mdx               |    2 +-
 .../alerts-and-reports-independent.mdx        |    1 -
 .../ddos-protection/allowlist-ip-spoofing.mdx |    5 +-
 .../ddos-protection/atp-filter-definition.mdx |    3 +-
 .../atp-filters-rules-precedence.mdx          |    1 -
 .../ddos-protection/create-notification.mdx   |    1 -
 .../ddos-protection/ddos-attack-coverage.mdx  |   15 +-
 .../log-and-monitor-behavior-link.mdx         |    2 +-
 .../managed-rulesets/create-override.mdx      |    4 +-
 .../managed-rulesets/evaluation-behavior.mdx  |    5 +-
 .../read-only-rules-description.mdx           |    1 -
 .../managed-rulesets/read-only-rules-note.mdx |    1 -
 .../sensitivity-level-reference.mdx           |   17 +-
 .../test-rules-description.mdx                |    1 -
 .../ddos-protection/override-example.mdx      |   25 +-
 .../ddos-protection/override-logic.mdx        |    7 +-
 .../dmarc-management/domain-spoofing.mdx      |    2 -
 .../partials/dns/a-aaaa-definition.mdx        |    1 -
 src/content/partials/dns/acns-tcns-byoip.mdx  |    3 +-
 .../partials/dns/acns-tcns-conditions.mdx     |    7 +-
 src/content/partials/dns/acns-tcns-intro.mdx  |    3 +-
 .../partials/dns/aname-alias-callout.mdx      |    3 +-
 .../partials/dns/api-field-definitions.mdx    |    1 -
 src/content/partials/dns/cname-definition.mdx |    1 -
 .../partials/dns/cname-flattening-callout.mdx |    1 -
 .../conversion-subdomain-setup-callout.mdx    |    3 +-
 .../partials/dns/dns-errors-ts-action.mdx     |    3 +-
 .../partials/dns/dns-errors-ts-intro.mdx      |    5 +-
 .../partials/dns/dns-nxdomain-warning.mdx     |    5 +-
 src/content/partials/dns/dns-record-steps.mdx |   10 +-
 src/content/partials/dns/dns-scan-intro.mdx   |    1 -
 src/content/partials/dns/dns-scan-note.mdx    |    2 +-
 src/content/partials/dns/dnssec-auto-add.mdx  |    3 -
 .../partials/dns/dnssec-cloudflare-steps.mdx  |    1 -
 .../partials/dns/dnssec-definition.mdx        |    1 -
 .../partials/dns/dnssec-enabled-migration.mdx |    3 -
 .../partials/dns/dnssec-registrar-steps.mdx   |    5 +-
 .../partials/dns/export-dns-records.mdx       |    1 -
 .../partials/dns/internal-dns-beta-note.mdx   |    1 -
 .../dns/internal-dns-view-conditions.mdx      |    4 +-
 .../dns/internal-reference-zone-api.mdx       |   15 +-
 .../dns/internal-reference-zone-intro.mdx     |   11 +-
 .../dns/internal-zones-conditions.mdx         |    4 +-
 .../partials/dns/linked-peers-limit.mdx       |    1 -
 .../partials/dns/minimize-downtime-tip.mdx    |    3 +-
 .../dns/mix-proxied-and-unproxied.mdx         |    3 -
 .../partials/dns/nameserver-preamble.mdx      |    1 -
 .../dns/nameservers-registrar-callout.mdx     |    1 -
 .../partials/dns/ns-advanced-vs-custom.mdx    |    1 -
 .../partials/dns/ns-set-omission-callout.mdx  |    1 -
 src/content/partials/dns/ns-static-ips.mdx    |    3 +-
 .../partials/dns/ns-update-providers.mdx      |   71 +-
 src/content/partials/dns/onboard-warning.mdx  |    1 -
 .../partials/dns/partial-setup-definition.mdx |    3 +-
 .../dns/random-prefix-attack-definition.mdx   |    1 -
 .../partials/dns/records-name-field.mdx       |    8 +-
 .../partials/dns/recover-deleted-domain.mdx   |    1 -
 .../dns/secondary-conversion-unlink.mdx       |    3 +-
 .../partials/dns/secondary-dns-override.mdx   |    1 -
 .../partials/dns/ssltls-subdomains.mdx        |    1 -
 .../partials/dns/subdomain-customization.mdx  |    1 -
 .../partials/dns/third-party-caveat.mdx       |    5 +-
 src/content/partials/dns/tsig-create-api.mdx  |    1 -
 src/content/partials/dns/tsig-create-dash.mdx |    7 +-
 src/content/partials/dns/tsig-definition.mdx  |    3 +-
 src/content/partials/dns/tsig-name-match.mdx  |    1 -
 .../partials/dns/why-disable-dnssec.mdx       |    1 -
 .../partials/dns/zone-defaults-exceptions.mdx |    1 -
 .../partials/dns/zone-file-size-limit.mdx     |    1 -
 .../durable-objects/api-async-kv-legacy.mdx   |    4 +-
 .../durable-objects/api-storage-alarms.mdx    |    2 +-
 .../api-storage-other-methods.mdx             |    2 +-
 .../partials/durable-objects/api-sync-kv.mdx  |    2 +-
 .../do-faq-metrics-and-analytics.mdx          |    4 +-
 .../durable-objects/do-plans-note.mdx         |    2 +-
 .../durable-objects/durable-objects-sql.mdx   |  122 +-
 .../durable-objects/recommend-sqlite-do.mdx   |    2 +-
 .../what-are-durable-objects.mdx              |    2 +-
 .../email-routing-definition.mdx              |    1 -
 .../email-routing/enable-create-worker.mdx    |    1 -
 .../send-emails-workers-intro.mdx             |    3 +-
 .../partials/email-routing/types-bindings.mdx |    1 -
 .../partials/email-security/add-user.mdx      |    3 +-
 .../email-security/auto-retraction.mdx        |   18 +-
 .../bec-directory-guide-compromise-list.mdx   |    1 -
 .../bec-directory-guide-secondary-email.mdx   |    1 -
 .../email-security/contact-support.mdx        |    3 +-
 .../bcc-table-geographic-locations.mdx        |   11 +-
 .../deployment/mx-deployment-values.mdx       |    1 -
 .../deployment/mx-geographic-locations.mdx    |   19 +-
 .../email-security/deployment/o365-gcc.mdx    |    1 -
 ...-use-case-1-3-create-quarantine-policy.mdx |    6 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 .../o365-use-case-configure-domain.mdx        |   15 +-
 .../o365-use-case-transport-rules.mdx         |   41 +-
 .../deployment/setup-api-overview.mdx         |   21 +-
 .../deployment/setup-inline-overview.mdx      |   13 +-
 .../deployment/setup-overview.mdx             |    1 -
 .../email-security-description.mdx            |    3 +-
 .../email-security/outbound-email.mdx         |    1 -
 .../email-security/rename-area1-to-ces.mdx    |    1 -
 .../partials/email-security/search.mdx        |    9 +-
 .../email-security/service-addresses.mdx      |    1 -
 .../email-security/sso-enforcement.mdx        |    9 +-
 .../account-audit-logs-definition.mdx         |    3 -
 .../account-manage-active-sessions.mdx        |    3 -
 .../account-member-manage-limitation.mdx      |    1 -
 .../fundamentals/api-change-api-key.mdx       |    3 +-
 .../fundamentals/api-combine-filters.mdx      |    9 +-
 .../fundamentals/api-filter-operators.mdx     |   22 +-
 .../partials/fundamentals/api-rate-limits.mdx |   16 +-
 .../partials/fundamentals/api-using-api.mdx   |    3 -
 .../partials/fundamentals/audit-log-api.mdx   |    1 -
 .../create-account-best-practices.mdx         |    1 -
 .../cybersafe-cipa-subcategories.mdx          |   55 +-
 .../fundamentals/cybersafe-configuration.mdx  |    1 -
 .../fundamentals/cybersafe-description.mdx    |    1 -
 .../fundamentals/cybersafe-requirements.mdx   |    1 -
 .../cybersafe-school-eligibility.mdx          |    5 +-
 .../fundamentals/idp-group-deprecation.mdx    |    5 -
 .../fundamentals/lists-import-notes.mdx       |    7 +-
 .../fundamentals/new-token-warning.mdx        |    3 -
 .../fundamentals/pseudo-ipv4-warning.mdx      |    1 -
 .../fundamentals/revoke-active-sessions.mdx   |    3 +-
 .../fundamentals/ubb-recommendation.mdx       |   12 +-
 .../fundamentals/user-permissions-table.mdx   |   19 +-
 .../partials/fundamentals/user-profiles.mdx   |    3 +-
 .../partials/fundamentals/view-audit-log.mdx  |    3 -
 .../fundamentals/what-is-cloudflare.mdx       |    3 +-
 .../zero-downtime-failover-retry-on-error.mdx |    1 -
 .../hyperdrive/create-hyperdrive-binding.mdx  |    7 +-
 .../hyperdrive/create-hyperdrive-config.mdx   |    9 +-
 .../partials/hyperdrive/pooling-mode.mdx      |    1 -
 .../use-postgres-js-to-make-query.mdx         |    2 +-
 .../learning-paths/cache-basic-diagram.mdx    |    1 -
 .../learning-paths/cache-optimization.mdx     |    7 +-
 ...-network-overview-additional-resources.mdx |    3 +-
 .../china-network-overview-navigation.mdx     |   27 +-
 .../cloudflare-tunnels-origin-description.mdx |    7 +-
 .../ddos-definition-and-diagram.mdx           |    3 +-
 .../learning-paths/email-record-origin-ip.mdx |    1 -
 .../learning-paths/r2-series-navigation.mdx   |   55 +-
 .../learning-paths/sase-series-navigation.mdx |   64 +-
 .../learning-paths/warp-series-navigation.mdx |   25 +-
 .../workflows-series-navigation.mdx           |   35 +-
 .../zero-trust/blocklist-restricted-users.mdx |    3 +-
 .../blocklist-security-categories.mdx         |    1 -
 .../configure-device-agent-description.mdx    |    1 -
 .../configure-device-agent-objectives.mdx     |    9 +-
 .../zero-trust/configure-idp.mdx              |    3 +-
 .../zero-trust/connect-devices-objectives.mdx |    7 +-
 .../learning-paths/zero-trust/create-list.mdx |    3 +-
 .../device-enrollment-permissions.mdx         |    3 +-
 .../zero-trust/email-dispositions.mdx         |   15 +-
 .../zero-trust/enable-proxy-intro.mdx         |    1 -
 .../zero-trust/initial-setup-objectives.mdx   |    7 +-
 .../zero-trust/install-agent.mdx              |   26 +-
 .../learning-paths/zero-trust/mdm.mdx         |    3 +-
 .../zero-trust/split-tunnel-settings.mdx      |    7 +-
 .../validate-traffic-in-gateway.mdx           |    9 +-
 .../components-knowledge-callout.mdx          |    1 -
 .../custom-rules-definition.mdx               |    1 -
 .../dns-load-balancing-benefits.mdx           |    1 -
 .../dns-load-balancing-definition.mdx         |    1 -
 .../dns-load-balancing-limitations.mdx        |   15 +-
 .../endpoints-introduction-callout.mdx        |    1 -
 .../load-balancing/fallback-pools.mdx         |    1 -
 .../load-balancing/health-check-diagram.mdx   |    1 -
 .../load-balancing/health-check-regions.mdx   |    1 -
 .../layer-4-load-balancing-definition.mdx     |    3 -
 .../layer-7-load-balancing-benefits.mdx       |   15 +-
 .../layer-7-load-balancing-definition.mdx     |    1 -
 .../load-balancer-create-api.mdx              |  149 ++-
 .../load-balancing/load-balancer-create.mdx   |   53 +-
 .../load-balancer-definition.mdx              |    1 -
 .../load-balancing/load-balancing-diagram.mdx |    1 -
 .../load-balancing/monitor-create-api.mdx     |  105 +-
 .../load-balancing/monitor-create.mdx         |    3 +-
 .../monitor-health-check-regions-options.mdx  |    5 +-
 .../load-balancing/monitor-prepare-server.mdx |    3 -
 .../load-balancing/monitor-settings-basic.mdx |   11 +-
 .../monitor-settings-consecutive.mdx          |    3 -
 .../origin-steering-definition.mdx            |    7 +-
 .../origin-steering-policies.mdx              |    1 -
 .../origin-steering-weights-definition.mdx    |    1 -
 .../origin-steering-weights-limitations.mdx   |    1 -
 .../partials/load-balancing/pool-create.mdx   |   31 +-
 .../load-balancing/pool-health-threshold.mdx  |    3 +-
 .../load-balancing/region-mapping.mdx         |    1 -
 .../route-production-traffic.mdx              |    7 +-
 .../session-affinity-by-cookie-process.mdx    |    5 +-
 .../session-affinity-definition.mdx           |    1 -
 .../spectrum-lb-limitations.mdx               |    5 +-
 .../load-balancing/test-domain-setup.mdx      |    1 -
 .../traffic-steering-definition.mdx           |    1 -
 .../unexpected-health-statuses.mdx            |    5 +-
 .../unhealthy-pool-traffic-distribution.mdx   |   10 +-
 .../partials/logs/check-log-retention.mdx     |    1 -
 .../partials/logs/disable-log-retention.mdx   |    1 -
 .../partials/logs/enable-log-retention.mdx    |    1 -
 .../partials/logs/enable-logpush-job.mdx      |    5 +-
 .../partials/logs/enable-read-permissions.mdx |    1 -
 .../partials/logs/filtering-limitations.mdx   |    1 -
 .../account-id-api-key.mdx                    |   20 +-
 .../analytics/set-thresholds-site-health.mdx  |    2 +-
 .../analytics/site-analytics.mdx              |   43 +-
 .../cloudflare-one-connectivity-options.mdx   |   35 +-
 .../cloudflare-wan/custom-ike-id-ipsec.mdx    |   13 +-
 .../cloudflare-wan/get-started.mdx            |   12 +-
 .../cloudflare-wan/load-balancing.mdx         |    2 +-
 .../reference/device-compatibility.mdx        |   60 +-
 .../cloudflare-wan/security-filters.mdx       |    2 +-
 .../cloudflare-wan/third-party/aws.mdx        |    4 +-
 .../third-party/azure-virtual-wan.mdx         |   18 +-
 .../cloudflare-wan/third-party/fitelnet.mdx   |    1 -
 .../cloudflare-wan/third-party/fortinet.mdx   |    2 -
 .../cloudflare-wan/third-party/juniper.mdx    |  218 ++--
 .../cloudflare-wan/third-party/oracle.mdx     |   59 +-
 .../cloudflare-wan/third-party/palo-alto.mdx  |  194 +--
 .../third-party/sophos-firewall.mdx           |    1 -
 .../cloudflare-wan/third-party/velocloud.mdx  |    8 +-
 .../cloudflare-wan/third-party/viptela.mdx    |   36 +-
 .../cloudflare-wan/third-party/yamaha.mdx     |   24 +-
 .../cloudflare-wan/wan-transformation.mdx     |   24 +-
 .../cloudflare-wan/zero-trust/gateway.mdx     |   11 +-
 .../cloudflare-wan/zero-trust/overview.mdx    |    6 +-
 .../zero-trust/security-services.mdx          |   35 +-
 .../cloudflare-wan/zero-trust/tunnel.mdx      |   24 +-
 .../cloudflare-wan/zero-trust/warp.mdx        |    9 +-
 .../cni-product-use-cases.mdx                 |   15 +-
 .../query-magic-transit-bandwidth-graphql.mdx |    3 +-
 ...y-magic-transit-endpoint-health-checks.mdx |  126 +-
 .../query-magic-transit-health-checks.mdx     |    2 +-
 .../ipsec-logs-troubleshooting.mdx            |    8 +-
 .../magic-transit/advertise-prefixes.mdx      |    3 +-
 .../magic-transit/cloudflare-ips.mdx          |    8 +-
 .../mtu-mss/mss-clamping-gre.mdx              |    2 -
 .../mtu-mss/mss-clamping-ipsec.mdx            |    2 -
 .../safely-withdraw-byoip-prefix.mdx          |    8 +-
 .../networking-services/magic-user-role.mdx   |    2 +-
 .../mconn/device-metrics.mdx                  |  106 +-
 .../mconn/licence-keys.mdx                    |    4 +-
 .../mconn/maintenance/activate-connectors.mdx |    2 +-
 .../maintenance/deactivate-connector.mdx      |   42 +-
 .../mconn/maintenance/default-password.mdx    |    2 +-
 .../mconn/maintenance/edit-basic-info.mdx     |   39 +-
 .../maintenance/edit-network-settings.mdx     |   46 +-
 .../mconn/maintenance/edit-sites.mdx          |   34 +-
 .../maintenance/edit-traffic-steering.mdx     |   40 +-
 .../mconn/maintenance/heartbeat.mdx           |   45 +-
 .../maintenance/interrupt-service-window.mdx  |   47 +-
 .../register-hardware-appliance.mdx           |   37 +-
 .../mconn/maintenance/remove-connectors.mdx   |   75 +-
 .../mconn/mconn-reference.mdx                 |   17 +-
 .../breakout-prioritized.mdx                  |  262 ++--
 .../app-aware-policies/netflow.mdx            |   19 +-
 .../app-aware-policies/overview.mdx           |    5 +-
 .../mconn/network-options/dhcp/dhcp-relay.mdx |    9 +-
 .../network-options/dhcp/dhcp-server.mdx      |    9 +-
 .../mconn/network-options/nat-subnet.mdx      |    1 -
 .../network-options/network-segmentation.mdx  |    9 +-
 .../mconn/network-options/routed-subnets.mdx  |    2 +-
 .../networking-services/mconn/overview.mdx    |    2 +-
 .../mconn/troubleshooting/troubleshooting.mdx |   33 +-
 .../mconn/vlan-tagging.mdx                    |    2 +-
 .../mconn/wan-two-tunnels.mdx                 |    2 +-
 .../mnm-auto-advertisement-notifications.mdx  |    2 +-
 .../mnm-magic-transit-integration.mdx         |   10 +-
 .../partials/networking-services/mnm/faqs.mdx |    2 +-
 .../mnm/routers/sflow-config.mdx              |    2 +-
 .../mnm/rules/dynamic-threshold.mdx           |   16 +-
 .../mnm/rules/overview.mdx                    |    2 +-
 .../mnm/rules/rule-notifications.mdx          |   21 +-
 .../mnm/rules/s-flow-ddos-attack.mdx          |   16 +-
 .../mnm/rules/static-threshold.mdx            |   32 +-
 .../mnm/tutorials/graphql-analytics.mdx       |    1 -
 ...-vendor-guidelines-mss-settings-origin.mdx |    6 +-
 .../reference/longest-prefix-match.mdx        |    2 +-
 .../traffic-steering-region-codes.mdx         |   22 +-
 .../reference/tunnel-health-checks.mdx        |   23 +-
 .../routing/anycast-warning.mdx               |    2 +-
 .../routing/bgp-config-steps.mdx              |   18 +-
 .../configure-cloudflare-source-ips.mdx       |    2 +
 .../routing/mcn-cloudflare-wan-on-ramps.mdx   |   18 +-
 .../networking-services/sites/sites-brief.mdx |    2 +-
 .../networking-services/sites/sites.mdx       |  156 +--
 .../troubleshoot-connectivity.mdx             |   17 +-
 .../check-tunnel-healthchecks-dash.mdx        |  121 +-
 .../health-checks-compatible-cmb-eu.mdx       |    2 +-
 .../magic-tunnel-health-alerts.mdx            |   33 +-
 .../tunnel-health/mconn-heartbeat-health.mdx  |    2 +-
 .../troubleshoot-tunnel-health.mdx            |  146 +--
 .../virtual-networks-concept.mdx              |   39 +-
 .../partials/notifications/get-started.mdx    |    1 -
 src/content/partials/pages/c3-adapter.mdx     |    3 -
 .../pages/c3-run-command-no-directory.mdx     |    7 +-
 .../pages/cli-precedence-over-file.mdx        |    3 -
 .../partials/pages/custom-domain-steps.mdx    |    1 +
 .../pages/deploy-to-pages-steps-no-preset.mdx |    1 +
 .../deploy-to-pages-steps-with-preset.mdx     |    1 +
 src/content/partials/pages/do-note.mdx        |    1 -
 .../pages/framework-guides/create-gh-repo.mdx |    1 -
 .../create-github-repository-prefix.mdx       |    1 -
 .../framework-guides/git-integration.mdx      |    3 +-
 .../pages/framework-guides/learn-more.mdx     |    3 +-
 .../pages/get-started-git-connect-pages.mdx   |    5 +-
 .../pages/get-started-git-manage-site.mdx     |   11 +-
 .../pages/git-integration-warning.mdx         |    3 -
 .../partials/pages/prod-branch-update.mdx     |    1 -
 .../pages/tutorials-before-you-start.mdx      |    1 -
 .../partials/pages/web-analytics-setup.mdx    |    2 +-
 src/content/partials/queues/enable-queues.mdx |    2 +-
 .../event-subscriptions/access-events.mdx     |   58 +-
 .../event-subscriptions/artifacts-events.mdx  |  366 +++---
 .../queues/event-subscriptions/kv-events.mdx  |   56 +-
 .../queues/event-subscriptions/r2-events.mdx  |   60 +-
 .../super-slurper-events.mdx                  |  202 +--
 .../event-subscriptions/vectorize-events.mdx  |   62 +-
 .../event-subscriptions/workers-ai-events.mdx |   90 +-
 .../workers-builds-events.mdx                 |  264 ++--
 .../event-subscriptions/workflows-events.mdx  |  180 +--
 .../partials/r2/custom-domain-steps.mdx       |    1 +
 .../partials/r2/link-to-workers-r2-api.mdx    |    2 +-
 .../partials/r2/migrator-etag-caveat.mdx      |    3 +-
 .../common/create-your-own-ui-examples.mdx    |    5 +-
 .../common/default-meeting-examples.mdx       |    5 +-
 .../web/breakout-room-close-breakout.mdx      |   13 +-
 .../web/breakout-room-creation-sdk-api.mdx    |   17 +-
 .../breakout-room-fetch-meetings-sdk-api.mdx  |   14 +-
 .../breakout-room-handle-breakout-events.mdx  |   11 +-
 ...breakout-room-move-participant-sdk-api.mdx |   19 +-
 ...t-room-move-preset-participant-sdk-api.mdx |   15 +-
 .../web/breakout-room-permission-check.mdx    |   16 +-
 .../realtimekit/web/language-pack-json.mdx    |  822 ++++++------
 .../description-of-design-guides.mdx          |    1 -
 ...scription-of-ref-architecture-diagrams.mdx |    1 -
 .../description-of-ref-architectures.mdx      |    1 -
 .../what-is-cloudflare-link.mdx               |    3 +-
 .../partials/registrar/email-verification.mdx |    3 -
 .../partials/registrar/enable-dnssec.mdx      |    3 +-
 .../registrar/icann-unverified-email.mdx      |    3 +-
 .../partials/registrar/requirements.mdx       |    1 -
 .../partials/registrar/restrictions.mdx       |   12 +-
 .../partials/registrar/verify-dnssec.mdx      |    1 -
 .../configuration-rule-link-to-examples.mdx   |    1 -
 .../rules/configuration-rule-promotion.mdx    |    3 -
 .../partials/rules/error-pages-list.mdx       |    1 -
 .../partials/rules/page-rules-migration.mdx   |    1 -
 .../rules/rules-creation-workflow.mdx         |    1 -
 .../partials/rules/rules-templates.mdx        |    6 +-
 .../rules/terraform-additional-resources.mdx  |    5 +-
 .../rules/transform/header-valid-names.mdx    |    5 +-
 .../rules/transform/header-valid-values.mdx   |    5 +-
 .../ruleset-engine/max-expression-length.mdx  |    1 -
 .../ruleset-engine/rule-position-values.mdx   |    7 +-
 .../brand-protection-alerts.mdx               |    1 -
 .../brand-protection-definition.mdx           |    3 +-
 .../security-center/scan-frequency.mdx        |    3 +-
 .../security-center/scan-properties.mdx       |    9 +-
 .../security-insights-definition.mdx          |    1 -
 .../partials/smart-shield/argo-analytics.mdx  |    2 +-
 .../partials/smart-shield/argo-intro.mdx      |    2 +-
 .../concurrent-connections-explainer.mdx      |    2 +-
 .../smart-shield/dcei-pool-requirements.mdx   |    2 +-
 .../smart-shield/health-checks-analytics.mdx  |    2 +-
 .../smart-shield/health-checks-intro.mdx      |    2 +-
 .../smart-shield/health-checks-regions.mdx    |    4 +-
 .../smart-shield/smart-shield-callout.mdx     |    2 +-
 .../partials/smart-shield/zone-lockdown.mdx   |    2 +-
 .../spectrum-with-load-balancer-api.mdx       |   63 +-
 .../spectrum-with-load-balancer-dash.mdx      |    3 +-
 .../partials/speed/rocket-loader-csp.mdx      |    3 +-
 src/content/partials/speed/user-agents.mdx    |   10 +-
 .../ssl/acm-ca-hostnames-conditions.mdx       |    1 -
 src/content/partials/ssl/acm-definition.mdx   |    1 -
 .../partials/ssl/acm-validate-cert.mdx        |    5 +-
 .../ssl/aop-per-hostname-upload-cert.mdx      |    3 +-
 .../partials/ssl/caa-records-added-by-cf.mdx  |    3 +-
 .../partials/ssl/caa-records-definition.mdx   |    1 -
 .../ssl/change-encryption-mode-api.mdx        |    1 -
 .../ssl/change-encryption-mode-dash.mdx       |    1 -
 .../ssl/cipher-suites-api-linkout.mdx         |    3 +-
 .../partials/ssl/cipher-suites-definition.mdx |    1 -
 .../ssl/cipher-suites-saas-linkout.mdx        |    3 +-
 .../ssl/ciphers-api-general-notes.mdx         |    2 +-
 .../partials/ssl/cname-cert-verification.mdx  |    1 -
 src/content/partials/ssl/csr-definition.mdx   |    1 -
 .../partials/ssl/custom-cert-ciphers.mdx      |    7 +-
 .../ssl/custom-cert-openssl-commands.mdx      |    1 -
 .../ssl/custom-certificates-definition.mdx    |    1 -
 .../custom-origin-trust-store-definition.mdx  |    1 -
 .../partials/ssl/dcv-certificate-renewal.mdx  |    9 +-
 .../partials/ssl/dcv-conflicting-records.mdx  |    3 +-
 src/content/partials/ssl/dcv-definition.mdx   |    1 -
 .../ssl/dcv-invalid-token-situations.mdx      |    1 -
 .../partials/ssl/dcv-path-security.mdx        |    1 -
 .../partials/ssl/dcv-renewal-fallback.mdx     |    1 -
 .../partials/ssl/dcv-validate-patch.mdx       |    1 -
 .../ssl/encryption-mode-definition.mdx        |    1 -
 .../ssl/enforce-https-recommendation.mdx      |    1 -
 .../partials/ssl/error-rate-limiting.mdx      |    1 -
 .../ssl/generic-validation-process.mdx        |    1 -
 .../partials/ssl/geokey-manager-v1.mdx        |    1 -
 .../ssl/get-started-additional-features.mdx   |    7 +-
 .../ssl/http-cname-validation-process.mdx     |    1 -
 .../partials/ssl/http-to-txt-schedule.mdx     |    3 +-
 .../partials/ssl/keyless-ssl-definition.mdx   |    1 -
 .../partials/ssl/keyless-tunnel-setup.mdx     |    1 -
 .../partials/ssl/keyless-upload-preamble.mdx  |    1 -
 .../partials/ssl/origin-ca-pause-error.mdx    |    3 +-
 .../ssl/partial-zone-acm-dcv-nonwildcard.mdx  |    8 +-
 .../ssl/partial-zone-acm-dcv-wildcard.mdx     |    5 +-
 src/content/partials/ssl/ssl-mode-errors.mdx  |    1 -
 src/content/partials/ssl/ssl-mode-no-aop.mdx  |    1 -
 .../ssl/ssl-recommender-post-setup.mdx        |    3 +-
 .../partials/ssl/ssl-recommender-prereqs.mdx  |    7 +-
 src/content/partials/ssl/test-tls-version.mdx |    3 +-
 .../ssl/tls-1.3-cipher-limitations.mdx        |    1 -
 .../ssl/total-tls-character-limitation.mdx    |    3 +-
 .../partials/ssl/txt-validation-api.mdx       |   53 +-
 .../partials/ssl/txt-validation-dashboard.mdx |    1 -
 .../ssl/txt-validation-definition.mdx         |    1 -
 .../partials/ssl/txt-validation-preamble.mdx  |    1 -
 .../ssl/universal-ssl-enable-full.mdx         |    1 -
 .../partials/ssl/universal-ssl-validity.mdx   |    3 +-
 .../ssl/ussl-limitations-solutions.mdx        |    7 +-
 .../partials/ssl/ussl-limitations-table.mdx   |    1 -
 .../partials/ssl/validation-level-note.mdx    |    1 -
 .../stream/android_playback_code_snippet.mdx  |    1 -
 .../stream/chromecast_limitations.mdx         |    1 -
 .../stream/ios_playback_code_snippet.mdx      |    1 -
 src/content/partials/stream/prereqs.mdx       |    3 -
 .../prereqs_first_start_live_streaming.mdx    |    3 -
 .../partials/stream/srt-supported-modes.mdx   |    3 -
 .../directory-listing-definition.mdx          |    2 +-
 src/content/partials/style-guide/icons.mdx    |    2 +-
 .../style-guide/public-stats-definition.mdx   |    2 +-
 .../partials/style-guide/tab-guidance.mdx     |    4 +-
 .../partials/style-guide/table-guidelines.mdx |    2 +-
 src/content/partials/support/2fa-enable.mdx   |    1 -
 src/content/partials/support/2fa-overview.mdx |    1 -
 .../partials/tenant/account-definition.mdx    |    1 -
 .../tenant/account-details-preamble.mdx       |    1 -
 .../partials/tenant/account-details.mdx       |   23 +-
 .../partials/tenant/account-preamble.mdx      |    1 -
 .../partials/tenant/create-account-api.mdx    |   70 +-
 .../partials/tenant/create-account-dash.mdx   |    1 -
 .../tenant/create-account-subscription.mdx    |   20 +-
 .../tenant/create-zone-subscription.mdx       |   24 +-
 .../partials/tenant/resource-definition.mdx   |    1 -
 .../tenant/tenant-admin-definition.mdx        |    1 -
 .../partials/tenant/tenant-definition.mdx     |    1 -
 .../tenant/tenant-details-preamble.mdx        |    1 -
 .../partials/tenant/tenant-details.mdx        |    5 -
 .../partials/tenant/user-definition.mdx       |    1 -
 .../partials/terraform/create-r2-buckets.mdx  |    1 -
 .../terraform/find-ids-managed-rulesets.mdx   |    5 +-
 src/content/partials/terraform/find-ids.mdx   |    5 +-
 .../import-delete-existing-rulesets.mdx       |    5 +-
 .../partials/terraform/v4-code-snippets.mdx   |    3 +-
 .../partials/terraform/v5-code-snippets.mdx   |    1 -
 .../partials/time-services/ntp-definition.mdx |    1 -
 .../partials/turnstile/challenge-behavior.mdx |    1 -
 .../partials/turnstile/privacy-policy.mdx     |    2 +-
 .../partials/turnstile/proxied-hostnames.mdx  |    1 -
 .../turnstile/security-requirements.mdx       |    2 -
 .../partials/turnstile/siteverify-warning.mdx |    1 -
 src/content/partials/turnstile/siteverify.mdx |    3 +-
 .../partials/turnstile/test-secret-key.mdx    |    3 +-
 .../partials/turnstile/test-sitekey.mdx       |    3 +-
 .../turnstile/troubleshooting-steps.mdx       |   21 +-
 .../partials/turnstile/widget-components.mdx  |   11 +-
 .../partials/vectorize/vectorize-ga.mdx       |    3 -
 .../partials/vectorize/vectorize-pricing.mdx  |    8 +-
 .../create-environment-situation.mdx          |    1 -
 .../version-management/edit-version.mdx       |    7 +-
 .../enable-default-creation.mdx               |    7 +-
 .../version-management/enable-versioning.mdx  |    5 +-
 .../environment-defaults.mdx                  |    7 +-
 .../environment-definition.mdx                |    1 -
 .../production-read-only-default.mdx          |    1 -
 .../version-management/promote-version.mdx    |    4 +-
 .../version-management/test-version.mdx       |    3 +-
 .../version-management/version-definition.mdx |    1 -
 .../waf/api-create-ruleset-with-rule.mdx      |    1 -
 src/content/partials/waf/list-advantages.mdx  |    7 +-
 src/content/partials/waf/managed-lists.mdx    |    4 +-
 .../waf/open-ports-blocked-traffic.mdx        |    1 -
 .../waf/rate-limiting-best-practices.mdx      |   11 +-
 .../waf/rate-limiting-rule-parameters.mdx     |   15 +-
 .../partials/waf/rules-next-steps-table.mdx   |    6 +-
 .../waiting-room/change-queueing-method.mdx   |    7 +-
 .../partials/waiting-room/queue-all.mdx       |    1 -
 .../partials/waiting-room/queue-some.mdx      |    1 -
 .../partials/warp-client/modes-options.mdx    |   13 +-
 .../web-analytics-definition.mdx              |    1 -
 .../web-analytics-notifications.mdx           |    1 -
 .../web-analytics-proxied-setup.mdx           |    1 -
 .../web-analytics-troubleshooting.mdx         |    3 -
 .../partials/web3/cloudflare-settings.mdx     |    1 -
 .../partials/web3/create-gateway-api.mdx      |   31 +-
 .../partials/web3/pricing-page-reference.mdx  |    3 -
 .../workers-ai/custom_requirements.mdx        |    3 -
 .../partials/workers-ai/file_issues.mdx       |    3 -
 .../workers-ai/openai-compatibility.mdx       |    1 -
 .../workers-vpc/create-tunnel-steps.mdx       |    2 +-
 .../partials/workers-vpc/required-roles.mdx   |    1 -
 .../workers/ai-local-usage-charges.mdx        |    3 -
 .../partials/workers/c3-definition.mdx        |    1 -
 .../partials/workers/compute-per-request.mdx  |    3 +-
 .../workers/content_and_contentoptions.mdx    |    3 -
 .../workers/dash-creation-next-steps.mdx      |    1 +
 .../partials/workers/env_and_secrets.mdx      |    1 -
 .../partials/workers/envvar-example.mdx       |    1 -
 .../workers/fetch-html-example-js.mdx         |   15 +-
 .../partials/workers/get-started-dash.mdx     |    3 +-
 .../workers/isolate-cpu-flexibility.mdx       |    1 -
 .../partials/workers/isolate-description.mdx  |    1 -
 .../partials/workers/limits_increase.mdx      |    3 -
 .../partials/workers/nodejs-compat-howto.mdx  |    2 -
 .../partials/workers/playground-callout.mdx   |    3 -
 src/content/partials/workers/prereqs.mdx      |    8 +-
 .../partials/workers/redirect-example-js.mdx  |   11 +-
 .../partials/workers/remote-binding-note.mdx  |    2 +-
 .../workers/request-dot-clone-warning.mdx     |    2 +-
 .../respond-another-site-example-js.mdx       |   27 +-
 .../workers/return-html-example-js.mdx        |   17 +-
 .../workers/return-json-example-js.mdx        |   13 +-
 .../workers/service-binding-rpc-example.mdx   |    1 -
 .../workers/storage-products-table.mdx        |   22 +-
 .../workers/testing-pages-functions.mdx       |    3 -
 .../workers/tutorials-before-you-start.mdx    |    1 -
 .../partials/workers/workers_logs_pricing.mdx |   11 +-
 .../workers/wrangler-commands/containers.mdx  |   16 +-
 .../workers/wrangler-commands/r2-sql.mdx      |   11 +-
 .../partials/workers/wrangler-commands/r2.mdx |   98 +-
 .../workflows/workflows-type-parameters.mdx   |    3 +-
 .../partials/zaraz/zaraz-definition.mdx       |    1 -
 src/pages/agent-setup/index.astro             |   49 +-
 src/pages/plans.astro                         |    4 +-
 3654 files changed, 33884 insertions(+), 34114 deletions(-)
 create mode 100644 src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx

diff --git a/.agents/references/procedures.md b/.agents/references/procedures.md
index b335d124dc55fb0..04454ac541394b5 100644
--- a/.agents/references/procedures.md
+++ b/.agents/references/procedures.md
@@ -11,10 +11,7 @@ Wrap all multi-step procedures in the `Steps` component:
 ```mdx
 import { Steps } from "~/components";
 
-<Steps>
-1. Step one
-2. Step two
-</Steps>
+<Steps>1. Step one 2. Step two</Steps>
 ```
 
 Single-step procedures: fold the step into the introductory sentence rather than making a one-item list.
@@ -26,14 +23,17 @@ Sub-steps use lowercase letters (a, b, c). Sub-sub-steps use lowercase Roman num
 ## Writing rules
 
 **Order**: state location before action, purpose before action.
+
 - "In the **DNS** section, select **Add record**." (location → action)
 - "To delete the rule, select **Delete**." (purpose → action)
 
 **First step**: consolidate login and navigation. Do not make "Log in" its own step if the next step is navigating somewhere.
+
 - "Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **DNS** > **Records**."
 - Write "log in to" (three words), not "log into".
 
 **Optional steps**: prefix with `(Optional)` as the first word.
+
 - "(Optional) Enter a description for the rule."
 
 **Enter key**: if the user must press **Enter** after a step, include it in that step.
@@ -62,10 +62,10 @@ Provide a screenshot when the UI element is genuinely hard to locate without one
 
 ## Terminology in procedures
 
-| Use | Not |
-| --- | --- |
-| select | click |
-| go to | navigate to |
+| Use                | Not              |
+| ------------------ | ---------------- |
+| select             | click            |
+| go to              | navigate to      |
 | turn on / turn off | enable / disable |
-| log in to | log into |
-| (Optional) | Optional: |
+| log in to          | log into         |
+| (Optional)         | Optional:        |
diff --git a/.agents/skills/dependabot-review/SKILL.md b/.agents/skills/dependabot-review/SKILL.md
index 9ad186440519dd9..1b684c642fe06e3 100644
--- a/.agents/skills/dependabot-review/SKILL.md
+++ b/.agents/skills/dependabot-review/SKILL.md
@@ -62,7 +62,7 @@ grep -r "require(['\"]<package>['\"]" src/ worker/ bin/ -l
 grep '"<package>"' package.json
 
 # If transitive, who pulls it in?
-node -e "const lock = require('./pnpm-lock.yaml'); ..." 
+node -e "const lock = require('./pnpm-lock.yaml'); ..."
 # or just:
 grep -A2 '"<package>"' pnpm-lock.yaml | grep -v "^--$" | head -20
 ```
@@ -79,6 +79,7 @@ grep -r "<method_name>\|<export_name>" src/ worker/ bin/ --include="*.ts" --incl
 ```
 
 For Astro/MDX source files under `src/content/docs/`, map them to their route:
+
 - `src/content/docs/workers/get-started/index.mdx` → `/workers/get-started/`
 - `src/content/docs/pages/platform/limits.mdx` → `/pages/platform/limits/`
 
@@ -88,13 +89,13 @@ If more than ~5 files use the changed API, list a representative sample (pick th
 
 Rate the probability that this bump causes a **visible change to the docs site**:
 
-| Rating | Meaning |
-|--------|---------|
-| **None** | Package not used directly; transitive only; or only internal/type changes |
-| **Very Low** | Direct dependency, but changed APIs are not called in this repo |
-| **Low** | Changed APIs are called, but only in build tooling (not runtime or content rendering) |
-| **Medium** | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
-| **High** | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior |
+| Rating       | Meaning                                                                                       |
+| ------------ | --------------------------------------------------------------------------------------------- |
+| **None**     | Package not used directly; transitive only; or only internal/type changes                     |
+| **Very Low** | Direct dependency, but changed APIs are not called in this repo                               |
+| **Low**      | Changed APIs are called, but only in build tooling (not runtime or content rendering)         |
+| **Medium**   | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
+| **High**     | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior       |
 
 For **security fixes**: note what the vulnerability affects and whether our usage is in the vulnerable code path.
 
@@ -142,5 +143,6 @@ For grouped PRs (non-major group), the PR body lists each package separately. Pr
 ### Packages with no public changelog
 
 If a package has no changelog and the upstream repo is private or unavailable:
+
 1. Check npm for version diff: `npm diff <package>@<old> <package>@<new>`
 2. If that also fails, note it explicitly and rate impact conservatively based on usage alone.
diff --git a/.agents/skills/docs-review/SKILL.md b/.agents/skills/docs-review/SKILL.md
index 4f37fbdb5b612a6..7ba37ceae99136b 100644
--- a/.agents/skills/docs-review/SKILL.md
+++ b/.agents/skills/docs-review/SKILL.md
@@ -150,19 +150,19 @@ Read full files for context — code that looks wrong in a diff may be correct i
 
 See `.agents/references/style-guide.md` for the full rules. Quick reference:
 
-| Rule                     | Detail                                                                                               |
-| ------------------------ | ---------------------------------------------------------------------------------------------------- |
-| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                          |
-| Component imports        | Every component used must be imported from `~/components`                                            |
-| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                              |
-| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                     |
-| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                     |
-| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                          |
-| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs    |
-| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                         |
-| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc.    |
-| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                     |
-| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover    |
+| Rule                     | Detail                                                                                            |
+| ------------------------ | ------------------------------------------------------------------------------------------------- |
+| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                       |
+| Component imports        | Every component used must be imported from `~/components`                                         |
+| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                           |
+| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                  |
+| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                  |
+| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                       |
+| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs |
+| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                      |
+| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc. |
+| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                  |
+| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover |
 
 ### 3. Assess What to Flag
 
diff --git a/.agents/skills/eli5/SKILL.md b/.agents/skills/eli5/SKILL.md
index 47c5f5e78f0cc91..3158464814dc939 100644
--- a/.agents/skills/eli5/SKILL.md
+++ b/.agents/skills/eli5/SKILL.md
@@ -67,7 +67,7 @@ Use this skill for content that targets a broad or mixed audience — not every
 
 - **Developer-focused API and SDK references** (e.g. Workers, D1, R2, Durable Objects, KV) — the audience is developers who are expected to know programming concepts, database terminology, and API conventions
 - **Code-heavy tutorials targeting developers** — readers self-select into these and already have the prerequisite knowledge
-- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon *is* the content
+- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon _is_ the content
 
 **Use your judgment for everything else.** Ask: "Would a reasonable reader of this page already know these terms?" If yes, this skill adds little value. On the other hand, if the following are true, this skill could provide significant value.
 
@@ -105,13 +105,13 @@ I read the file, detect sections, analyze organization, and identify the content
 
 After detection, I ask you to confirm the content type. Different types require different strategies:
 
-| Type | Strategy |
-|------|----------|
-| Overview | Problem → Solution → Benefit |
-| Concept | Analogy → Plain explanation → Technical details |
-| How To | Context → Multi-path steps (Dashboard + API) |
+| Type      | Strategy                                         |
+| --------- | ------------------------------------------------ |
+| Overview  | Problem → Solution → Benefit                     |
+| Concept   | Analogy → Plain explanation → Technical details  |
+| How To    | Context → Multi-path steps (Dashboard + API)     |
 | Reference | Use-case organization with two-tier descriptions |
-| Tutorial | Progressive complexity with code explanations |
+| Tutorial  | Progressive complexity with code explanations    |
 
 **3. Apply Enhancement Constraints**
 
@@ -225,7 +225,7 @@ These are the highest-risk categories when documentation has been simplified. Pr
 
 1. **Simplified mechanism descriptions** — Any "how it works" explanation added during simplification that was not in the original. These carry the highest risk: a plausible-sounding explanation that describes the wrong mechanism is worse than the original jargon. Verify the actual mechanism against the source docs in this repository.
 
-2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies *where* crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
+2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies _where_ crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
 
 3. **Net-new claims** — Any explanation, context, or framing added during simplification that was not present in the original document. Every piece of new information requires a citation. If the original said "zones pair with resolver policies" and the simplification adds "based on source IP, user identity, or domain," verify that all three of those selectors are actually supported.
 
@@ -249,12 +249,12 @@ These are the highest-risk categories when documentation has been simplified. Pr
    - **low** — Claim is minor or widely accepted common knowledge.
 5. **Report** — Present findings in this format:
 
-| # | Claim (exact text) | Source | Status |
-|---|---|---|---|
-| 1 | "Workers KV supports keys up to 512 bytes" | `src/content/docs/kv/api/write-key-value-pairs.mdx` | ✅ sourced |
-| 2 | "Latency is under 50 ms globally" | — | ❌ unsourced (high) |
-| 3 | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
-| 4 | "zones pair with resolver policies" | present in original — `path/to/file.mdx:34` | ✅ sourced (original) |
+| #   | Claim (exact text)                                  | Source                                                                                          | Status                   |
+| --- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------ |
+| 1   | "Workers KV supports keys up to 512 bytes"          | `src/content/docs/kv/api/write-key-value-pairs.mdx`                                             | ✅ sourced               |
+| 2   | "Latency is under 50 ms globally"                   | —                                                                                               | ❌ unsourced (high)      |
+| 3   | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
+| 4   | "zones pair with resolver policies"                 | present in original — `path/to/file.mdx:34`                                                     | ✅ sourced (original)    |
 
 ### Rules
 
@@ -397,10 +397,12 @@ Produce output following this template exactly. All sections are required.
 ## Simplification Overview
 
 **What was confusing:**
+
 - [Issue pattern 1]
 - [Issue pattern 2]
 
 **Approach taken:**
+
 - [Strategy 1]
 - [Strategy 2]
 
@@ -409,14 +411,17 @@ Produce output following this template exactly. All sections are required.
 ## Section: [Original Heading]
 
 ### Original Content
+
 [Exact text from source, preserved]
 
 ### Issues Identified
+
 **Jargon:** [terms and why problematic]
 **Assumptions:** [unstated prerequisites]
 **Unclear Logic:** [structural issues]
 
 ### Simplified Version
+
 **In Plain Language:** [One-sentence distillation]
 **What It Is:** [2-3 paragraphs building from basics]
 **Why It Matters:** [Benefits and value]
@@ -434,9 +439,9 @@ Produce output following this template exactly. All sections are required.
 
 ## Terminology Index
 
-| Term | Line | Defined? | Suggested Action |
-| ---- | ---- | -------- | ---------------- |
-| [term] | [line number] | Yes/No | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
+| Term   | Line          | Defined? | Suggested Action                                                        |
+| ------ | ------------- | -------- | ----------------------------------------------------------------------- |
+| [term] | [line number] | Yes/No   | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
 
 ---
 
@@ -449,9 +454,9 @@ Produce output following this template exactly. All sections are required.
 
 Line-numbered recommendations for further improvements:
 
-| Line(s) | Current Approach | Suggested Enhancement | Why | Priority |
-| ------- | ---------------- | --------------------- | --- | -------- |
-| [lines] | [what exists] | [what to change] | [why it improves accessibility] | High/Medium/Low |
+| Line(s) | Current Approach | Suggested Enhancement | Why                             | Priority        |
+| ------- | ---------------- | --------------------- | ------------------------------- | --------------- |
+| [lines] | [what exists]    | [what to change]      | [why it improves accessibility] | High/Medium/Low |
 ```
 
 ## References
diff --git a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
index 6d9e9f57671e88a..a81b5834b7aae6c 100644
--- a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
+++ b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
@@ -193,6 +193,7 @@ For detailed step-by-step setup instructions, see the [Get started guide](/dns/i
 This overview was enhanced with inline context explaining when you'd use Internal DNS, step-by-step query flow showing how views work, and three detailed use case examples with real-world scenarios. Added explanations of key concepts (views, zone referencing, privacy model) and a "Getting started" checklist.
 
 **What was added:**
+
 - Opening context: When to use Internal DNS with concrete example (lines 34-36)
 - Architecture explanations: On-ramp options, why zones are private (lines 42-44, 48-50)
 - Views explanation: Why views matter and how they enable customization (lines 73-75)
diff --git a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
index 742a86dc6ee14df..4d1539a961ee745 100644
--- a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
+++ b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
@@ -26,6 +26,7 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Purpose:** Help users quickly understand what a product/feature is and decide if they need it.
 
 **Required Elements:**
+
 - Opening benefit statement (what problem this solves)
 - Problem/Solution/Benefit structure
 - "Perfect for" self-identification section
@@ -33,6 +34,7 @@ Once content type is detected and validated, I apply type-specific simplificatio
 - Technical architecture separated to bottom
 
 **Analysis Focus:**
+
 - Does opening paragraph answer "what" and "why"?
 - Are features explained with benefits, not just descriptions?
 - Is there a clear call-to-action?
@@ -49,32 +51,36 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Pattern Example:**
 
 ❌ **Before (Technical-first):**
+
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 
-isolates for serverless code execution with sub-millisecond cold 
+Product X is a distributed edge computing platform utilizing V8
+isolates for serverless code execution with sub-millisecond cold
 start performance.
 
 Features:
+
 - Global anycast network deployment
 - Automatic scaling and load distribution
 - Pay-per-request pricing model
 ```
 
 ✅ **After (Benefit-first):**
+
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, 
+Run code worldwide without managing servers. Deploy in seconds,
 scale automatically, pay only for what you use.
 
 **What problem it solves:**
-Maintaining global infrastructure is expensive and complex. Product X 
-runs your code in 300+ cities automatically, handling all the 
+Maintaining global infrastructure is expensive and complex. Product X
+runs your code in 300+ cities automatically, handling all the
 infrastructure for you.
 
 **Perfect for:**
+
 - Applications needing fast global performance
 - Teams wanting to skip server management
 - Projects with variable traffic (scale from zero to millions)
@@ -83,7 +89,7 @@ infrastructure for you.
 
 ---
 
-**For technical users:** Built on V8 isolates with global anycast 
+**For technical users:** Built on V8 isolates with global anycast
 deployment. [Architecture details →]
 ```
 
@@ -94,6 +100,7 @@ deployment. [Architecture details →]
 **Purpose:** Build understanding of WHY something works the way it does.
 
 **Required Elements:**
+
 - Opening analogy or visual (accessible to all)
 - Plain language definition
 - "Why it matters" business value
@@ -102,6 +109,7 @@ deployment. [Architecture details →]
 - Technical details for advanced users (separated)
 
 **Analysis Focus:**
+
 - Is there an analogy early in the content?
 - Does it explain WHY before HOW?
 - Are use cases concrete and realistic?
@@ -118,47 +126,51 @@ deployment. [Architecture details →]
 **Pattern Example:**
 
 ❌ **Before (Technical-only):**
+
 ```markdown
 ## Rate Limiting
 
-Rate limiting implements token bucket algorithms to control request 
-throughput based on configurable parameters including burst size and 
+Rate limiting implements token bucket algorithms to control request
+throughput based on configurable parameters including burst size and
 refill rate. Requests exceeding limits receive 429 status codes.
 ```
 
 ✅ **After (Layered explanation):**
+
 ```markdown
 ## Rate Limiting
 
-**Think of it like:** A nightclub with maximum capacity. Even if 
-1,000 people want to enter at once, you only let a controlled number 
+**Think of it like:** A nightclub with maximum capacity. Even if
+1,000 people want to enter at once, you only let a controlled number
 in at a time to keep things manageable.
 
 **What it is:**
-Rate limiting controls how many requests can hit your website in a 
-given time period. Without it, a sudden spike—whether from real 
+Rate limiting controls how many requests can hit your website in a
+given time period. Without it, a sudden spike—whether from real
 users or attackers—could overwhelm your server.
 
 **Why you need it:**
+
 - Prevents DDoS attacks from taking your site down
 - Stops bots from scraping your content
 - Ensures fair usage across all users
 - Keeps infrastructure costs predictable
 
 **How it works:**
-You set a rule like "100 requests per minute per IP address." When 
-someone exceeds this limit, we block additional requests until the 
+You set a rule like "100 requests per minute per IP address." When
+someone exceeds this limit, we block additional requests until the
 time window resets.
 
 **Real scenarios:**
+
 - E-commerce site during Black Friday preventing bot purchases
 - API preventing scraping of product catalog
 - Forum preventing spam post flooding
 
 ---
 
-**For technical users:** Implements token bucket algorithm with 
-configurable burst size and refill rates. Returns 429 status with 
+**For technical users:** Implements token bucket algorithm with
+configurable burst size and refill rates. Returns 429 status with
 Retry-After header. [Implementation details →]
 ```
 
@@ -169,6 +181,7 @@ Retry-After header. [Implementation details →]
 **Purpose:** Help users successfully accomplish specific tasks.
 
 **Required Elements:**
+
 - Context (what this accomplishes, why you'd do it)
 - Prerequisites listed upfront
 - Expected outcome stated
@@ -179,6 +192,7 @@ Retry-After header. [Implementation details →]
 - Common issues and troubleshooting
 
 **Analysis Focus:**
+
 - Is context provided before steps?
 - Are prerequisites clearly stated?
 - Is there both a Dashboard and API path?
@@ -197,6 +211,7 @@ Retry-After header. [Implementation details →]
 **Pattern Example:**
 
 ❌ **Before (Steps-only):**
+
 ```markdown
 ## Enable Feature
 
@@ -207,16 +222,17 @@ Retry-After header. [Implementation details →]
 ```
 
 ✅ **After (Contextual multi-path):**
-```markdown
+
+````markdown
 ## Enable Feature
 
-**What this does:** Protects your site from [specific threat] by 
+**What this does:** Protects your site from [specific threat] by
 [specific mechanism].
 
 **Time required:** ~2 minutes  
 **Prerequisites:** Admin access to your account
 
-**What happens:** After enabling, all incoming requests will be 
+**What happens:** After enabling, all incoming requests will be
 [specific behavior]. You'll see results in Analytics within 5 minutes.
 
 ### Via Dashboard
@@ -227,7 +243,7 @@ Retry-After header. [Implementation details →]
 4. Find **Feature Name** and toggle it **On**
 5. Click **Save Changes**
 
-💡 **Note:** Changes take effect immediately, but analytics may take 
+💡 **Note:** Changes take effect immediately, but analytics may take
 5 minutes to update.
 
 ### Via API
@@ -240,15 +256,17 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_enabled": true}'
 ```
+````
 
 **Response:**
+
 ```json
 {
-  "success": true,
-  "result": {
-    "feature_enabled": true,
-    "updated_at": "2026-02-09T10:30:00Z"
-  }
+	"success": true,
+	"result": {
+		"feature_enabled": true,
+		"updated_at": "2026-02-09T10:30:00Z"
+	}
 }
 ```
 
@@ -266,9 +284,10 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 ## Troubleshooting
 
 **Problem:** Feature doesn't seem to be active  
-**Solution:** Clear your browser cache and wait 5 minutes for 
+**Solution:** Clear your browser cache and wait 5 minutes for
 propagation. Still not working? Check that [prerequisite].
-```
+
+````
 
 ---
 
@@ -304,19 +323,20 @@ propagation. Still not working? Check that [prerequisite].
 ```markdown
 ## Cache Headers
 
-**Cache-Control:** Controls caching. Values: public, private, 
+**Cache-Control:** Controls caching. Values: public, private,
 no-cache, max-age=seconds
 
 **Expires:** HTTP date for expiration
 
 **Pragma:** Legacy directive. Value: no-cache
-```
+````
 
 ✅ **After (Use-case organized with examples):**
-```markdown
+
+````markdown
 ## Cache Headers Reference
 
-**When to use:** Control how long content stays cached and who can 
+**When to use:** Control how long content stays cached and who can
 cache it.
 
 ### Common Scenarios
@@ -335,17 +355,19 @@ cache it.
 
 **What it does:** Caches content for 1 year before checking for updates
 
-**When to use:** Files that never change, like `logo-v2.png` or 
+**When to use:** Files that never change, like `logo-v2.png` or
 `style.abc123.css` with version hash in filename
 
 **Technical spec:** Integer, seconds. Range: 0-31536000 (1 year max)
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
+````
 
-**Result:** First visitor downloads the file. For the next year, all 
+**Result:** First visitor downloads the file. For the next year, all
 visitors get the cached version with zero origin requests.
 
 ---
@@ -354,17 +376,18 @@ visitors get the cached version with zero origin requests.
 
 **What it does:** Tells browsers this file will literally never change
 
-**When to use:** Combine with `max-age` for versioned assets 
+**When to use:** Combine with `max-age` for versioned assets
 (filename includes hash/version number)
 
 **Technical spec:** No value. Presence activates directive.
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
 
-**Result:** Browsers won't revalidate even on refresh. Perfect for 
+**Result:** Browsers won't revalidate even on refresh. Perfect for
 `style.abc123.css` where hash changes when content changes.
 
 ---
@@ -375,17 +398,18 @@ Cache-Control: public, max-age=31536000, immutable
 
 **What it does:** Caches content for 1 hour
 
-**When to use:** Content that updates occasionally but doesn't need 
+**When to use:** Content that updates occasionally but doesn't need
 to be real-time, like blog posts or product pages
 
 **Technical spec:** Integer, seconds
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=3600
 ```
 
-**Result:** Content stays cached for 1 hour. After expiration, next 
+**Result:** Content stays cached for 1 hour. After expiration, next
 request checks origin for updates.
 
 ---
@@ -394,17 +418,18 @@ request checks origin for updates.
 
 **What it does:** Always check with origin before using cached version
 
-**When to use:** Content that changes frequently but can still be 
+**When to use:** Content that changes frequently but can still be
 cached briefly (shopping cart, personalized pages)
 
 **Technical spec:** No value. Presence activates.
 
 **Example:**
+
 ```http
 Cache-Control: no-cache
 ```
 
-**Result:** Every request checks origin via If-Modified-Since or 
+**Result:** Every request checks origin via If-Modified-Since or
 ETag. If nothing changed, serves cached version (304 response).
 
 ---
@@ -415,19 +440,21 @@ ETag. If nothing changed, serves cached version (304 response).
 
 **What it does:** Prevents any caching
 
-**When to use:** Sensitive data (account info, payment details) or 
+**When to use:** Sensitive data (account info, payment details) or
 highly dynamic content (real-time scores, live chat)
 
 **Technical spec:** Combine both directives
 
 **Example:**
+
 ```http
 Cache-Control: private, no-store
 ```
 
-**Result:** Every request fetches fresh from origin. Nothing cached 
+**Result:** Every request fetches fresh from origin. Nothing cached
 anywhere.
-```
+
+````
 
 ---
 
@@ -473,8 +500,9 @@ const handler = async (req) => {
   return new Response('Hello')
 }
 addEventListener('fetch', e => e.respondWith(handler(e.request)))
-```
-```
+````
+
+````
 
 ✅ **After (Explained progression):**
 ```markdown
@@ -482,14 +510,14 @@ addEventListener('fetch', e => e.respondWith(handler(e.request)))
 
 ### What You'll Build
 
-A working URL shortener that redirects short links to long URLs, 
+A working URL shortener that redirects short links to long URLs,
 stores mappings, and tracks click analytics.
 
 **Live example:** `short.example.com/github` → `github.com/cloudflare`
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience with 
+Developers comfortable with JavaScript. No prior experience with
 Workers needed, but you should understand:
 - HTTP requests and responses
 - JSON data format
@@ -510,7 +538,7 @@ Workers needed, but you should understand:
 
 ## Step 1: Create Your First Worker
 
-Let's start with the absolute minimum—a Worker that responds to 
+Let's start with the absolute minimum—a Worker that responds to
 requests:
 
 ```javascript
@@ -526,7 +554,7 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-```
+````
 
 **What this code does:**
 
@@ -550,15 +578,15 @@ Now let's make it recognize short codes in the URL:
 
 ```javascript
 async function handleRequest(request) {
-  // Extract the pathname from the URL
-  // Example: https://short.example.com/github → "/github"
-  const url = new URL(request.url)
-  const shortCode = url.pathname.slice(1) // Remove leading "/"
-  
-  // For now, just echo back the short code
-  return new Response(`You requested: ${shortCode}`, {
-    headers: { 'content-type': 'text/plain' }
-  })
+	// Extract the pathname from the URL
+	// Example: https://short.example.com/github → "/github"
+	const url = new URL(request.url);
+	const shortCode = url.pathname.slice(1); // Remove leading "/"
+
+	// For now, just echo back the short code
+	return new Response(`You requested: ${shortCode}`, {
+		headers: { "content-type": "text/plain" },
+	});
 }
 ```
 
@@ -590,15 +618,15 @@ Now we can detect what short code someone's requesting...
 
 **Cause:** Your Worker is doing too much computation in a single request
 
-**Solution:** Workers have a 50ms CPU time limit. Move heavy processing 
+**Solution:** Workers have a 50ms CPU time limit. Move heavy processing
 to background tasks or use Durable Objects for longer operations.
 
 **Problem:** "KV data not updating"
 
-**Cause:** KV is eventually consistent and may take 60 seconds to 
+**Cause:** KV is eventually consistent and may take 60 seconds to
 propagate globally
 
-**Solution:** For testing, add a cache-busting parameter (`?v=2`) or 
+**Solution:** For testing, add a cache-busting parameter (`?v=2`) or
 wait 60 seconds between writes and reads.
 
 ---
@@ -608,20 +636,24 @@ wait 60 seconds between writes and reads.
 Want to take this further? Here are some ideas:
 
 **Add Click Analytics** (Medium difficulty)
+
 - Store click count in KV
 - Increment on each redirect
 - Create stats endpoint
 
 **Custom Short Codes** (Easy)
+
 - Let users choose their short code
 - Check if code is already taken
 - Return error if unavailable
 
 **Expiring Links** (Medium)
+
 - Store expiration timestamp
 - Check before redirecting
 - Return 404 if expired
-```
+
+````
 
 ---
 
@@ -642,7 +674,7 @@ Want to take this further? Here are some ideas:
 - Not: "Webhooks, which are HTTP callbacks, send notifications containing event data to your specified endpoint when certain events occur on the platform."
 
 ✅ **Active voice** over passive
-- "The system sends a notification" 
+- "The system sends a notification"
 - Not: "A notification is sent by the system"
 
 ✅ **Concrete nouns** over abstract
@@ -663,11 +695,12 @@ Want to take this further? Here are some ideas:
 
 **Always define on first use:**
 ```markdown
-An API (Application Programming Interface) defines how programs 
+An API (Application Programming Interface) defines how programs
 can request and exchange data...
-```
+````
 
 **Expand acronyms:**
+
 ```markdown
 CDN (Content Delivery Network)
 CI/CD (Continuous Integration/Continuous Deployment)
@@ -675,9 +708,10 @@ HMAC (Hash-based Message Authentication Code)
 ```
 
 **Provide context for technical terms:**
+
 ```markdown
 Not: "Configure the webhook endpoint."
-But: "A webhook endpoint is the URL where we'll send notifications. 
+But: "A webhook endpoint is the URL where we'll send notifications.
 Configure it to point to your server."
 ```
 
@@ -696,16 +730,16 @@ Configure it to point to your server."
 
 ```markdown
 **Think of It Like:**
-An API is like a restaurant menu. The menu shows you what dishes 
-are available (endpoints), what customizations you can request 
-(parameters like "no onions" or "extra spicy"), and what you'll 
-receive (the response - your meal). You don't need to know how the 
-kitchen operates or what cooking techniques they use. You just order 
+An API is like a restaurant menu. The menu shows you what dishes
+are available (endpoints), what customizations you can request
+(parameters like "no onions" or "extra spicy"), and what you'll
+receive (the response - your meal). You don't need to know how the
+kitchen operates or what cooking techniques they use. You just order
 from the menu, and the kitchen handles the rest.
 
 **Where this breaks down:**
-Unlike a restaurant where you wait for your food, API responses are 
-usually near-instantaneous. Also, APIs can fail (kitchen is out of 
+Unlike a restaurant where you wait for your food, API responses are
+usually near-instantaneous. Also, APIs can fail (kitchen is out of
 ingredients), requiring error handling.
 ```
 
@@ -713,15 +747,15 @@ ingredients), requiring error handling.
 
 ```markdown
 **Think of It Like:**
-Caching is like a library's reserve desk. Popular books are kept at 
-the front desk for quick access instead of requiring a trip to the 
-stacks. The first person requesting a book triggers the librarian to 
-fetch it from the stacks, but then it stays at the reserve desk so 
+Caching is like a library's reserve desk. Popular books are kept at
+the front desk for quick access instead of requiring a trip to the
+stacks. The first person requesting a book triggers the librarian to
+fetch it from the stacks, but then it stays at the reserve desk so
 subsequent readers can grab it immediately.
 
 **Where this breaks down:**
-Caches expire (books eventually return to the stacks), and cache 
-invalidation (deciding when to return books) is more complex than 
+Caches expire (books eventually return to the stacks), and cache
+invalidation (deciding when to return books) is more complex than
 the metaphor suggests.
 ```
 
@@ -729,15 +763,15 @@ the metaphor suggests.
 
 ```markdown
 **Think of It Like:**
-Load balancing is like grocery store checkout lanes. Instead of 
-everyone lining up at a single register (which would create a huge 
-wait), customers are distributed across multiple lanes. If one lane 
-gets too long or a register breaks down, the store can redirect 
+Load balancing is like grocery store checkout lanes. Instead of
+everyone lining up at a single register (which would create a huge
+wait), customers are distributed across multiple lanes. If one lane
+gets too long or a register breaks down, the store can redirect
 people to other lanes.
 
 **Where this breaks down:**
-Load balancers are more intelligent than checkout lane selection—they 
-know which servers are healthy, how busy they are, and can route 
+Load balancers are more intelligent than checkout lane selection—they
+know which servers are healthy, how busy they are, and can route
 based on sophisticated algorithms.
 ```
 
@@ -745,14 +779,14 @@ based on sophisticated algorithms.
 
 ```markdown
 **Think of It Like:**
-A webhook is like a doorbell notification. Instead of constantly 
-checking your front door to see if someone arrived (polling), the 
-doorbell alerts you the moment someone presses it (push notification). 
+A webhook is like a doorbell notification. Instead of constantly
+checking your front door to see if someone arrived (polling), the
+doorbell alerts you the moment someone presses it (push notification).
 You only respond when there's actually something to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have some latency due to 
-network transmission. Also, webhooks can fail if your server is down 
+Doorbells are instantaneous, while webhooks have some latency due to
+network transmission. Also, webhooks can fail if your server is down
 (like a broken doorbell).
 ```
 
@@ -760,15 +794,15 @@ network transmission. Also, webhooks can fail if your server is down
 
 ```markdown
 **Think of It Like:**
-Authentication is like a building security badge system. You present 
-your badge (credentials) when entering. The system verifies you are 
-who you claim to be (authentication), then checks what floors you're 
-allowed to access (authorization). Different badges have different 
+Authentication is like a building security badge system. You present
+your badge (credentials) when entering. The system verifies you are
+who you claim to be (authentication), then checks what floors you're
+allowed to access (authorization). Different badges have different
 access levels.
 
 **Where this breaks down:**
-Digital authentication often uses time-limited tokens (like a badge 
-that expires), and can verify identity through multiple methods 
+Digital authentication often uses time-limited tokens (like a badge
+that expires), and can verify identity through multiple methods
 (password + fingerprint), which isn't common with physical badges.
 ```
 
@@ -776,15 +810,15 @@ that expires), and can verify identity through multiple methods
 
 ```markdown
 **Think of It Like:**
-Rate limiting is like freeway on-ramp metering lights. Instead of 
-letting everyone merge at once (causing congestion), the lights 
-control how many cars enter per minute. This keeps traffic flowing 
-smoothly on the main freeway. If you arrive too fast, you wait at 
+Rate limiting is like freeway on-ramp metering lights. Instead of
+letting everyone merge at once (causing congestion), the lights
+control how many cars enter per minute. This keeps traffic flowing
+smoothly on the main freeway. If you arrive too fast, you wait at
 the red light.
 
 **Where this breaks down:**
-Rate limits are often user-specific (you get your own limit), not 
-shared like a metering light. Also, rate limits reset on schedules 
+Rate limits are often user-specific (you get your own limit), not
+shared like a metering light. Also, rate limits reset on schedules
 (every hour, every day), unlike continuous traffic flow.
 ```
 
@@ -792,14 +826,14 @@ shared like a metering light. Also, rate limits reset on schedules
 
 ```markdown
 **Think of It Like:**
-A database index is like the index at the back of a textbook. Instead 
-of reading every page to find mentions of "webhooks," you check the 
-index, which tells you exactly which pages to look at. The index 
+A database index is like the index at the back of a textbook. Instead
+of reading every page to find mentions of "webhooks," you check the
+index, which tells you exactly which pages to look at. The index
 takes up extra space, but makes searching dramatically faster.
 
 **Where this breaks down:**
-Database indexes need updating when data changes (like keeping a 
-book index current as you add pages), and choosing which fields to 
+Database indexes need updating when data changes (like keeping a
+book index current as you add pages), and choosing which fields to
 index involves tradeoffs between search speed and write speed.
 ```
 
@@ -807,16 +841,16 @@ index involves tradeoffs between search speed and write speed.
 
 ```markdown
 **Think of It Like:**
-A CDN (Content Delivery Network) is like having local warehouses 
-instead of shipping everything from one central warehouse. When 
-someone in California orders a product, it ships from the California 
-warehouse (faster delivery). When someone in New York orders, it 
+A CDN (Content Delivery Network) is like having local warehouses
+instead of shipping everything from one central warehouse. When
+someone in California orders a product, it ships from the California
+warehouse (faster delivery). When someone in New York orders, it
 ships from New York. Same product, closer source.
 
 **Where this breaks down:**
-Unlike physical warehouses with unique inventory, CDNs store copies 
-of the same content in many locations. Updates need to propagate to 
-all locations (cache invalidation), which has no physical warehouse 
+Unlike physical warehouses with unique inventory, CDNs store copies
+of the same content in many locations. Updates need to propagate to
+all locations (cache invalidation), which has no physical warehouse
 equivalent.
 ```
 
@@ -824,17 +858,17 @@ equivalent.
 
 ```markdown
 **Think of It Like:**
-Software containers are like shipping containers. Before shipping 
-containers existed, moving goods required different methods for 
-different types of cargo. Shipping containers standardized this—put 
-anything inside a standard container, and it can go on any ship, 
-truck, or train. Software containers work the same way: package your 
+Software containers are like shipping containers. Before shipping
+containers existed, moving goods required different methods for
+different types of cargo. Shipping containers standardized this—put
+anything inside a standard container, and it can go on any ship,
+truck, or train. Software containers work the same way: package your
 application and its dependencies, and it runs anywhere.
 
 **Where this breaks down:**
-Shipping containers physically isolate cargo, while software 
-containers share the same operating system kernel. Also, you can run 
-thousands of software containers on one machine, unlike physical 
+Shipping containers physically isolate cargo, while software
+containers share the same operating system kernel. Also, you can run
+thousands of software containers on one machine, unlike physical
 containers.
 ```
 
@@ -843,15 +877,15 @@ containers.
 ```markdown
 **Think of It Like:**
 Environment variables are like your application's settings panel—
-configuration values that change behavior without modifying code. 
-Just like you might set your phone to dark mode or adjust notification 
-preferences, environment variables let you configure database URLs, 
+configuration values that change behavior without modifying code.
+Just like you might set your phone to dark mode or adjust notification
+preferences, environment variables let you configure database URLs,
 API keys, or feature flags without rewriting your application.
 
 **Where this breaks down:**
-Environment variables are usually set before the application starts 
-(not changed while running), and they're text-based rather than UI 
-toggles. They're also specific to each deployment environment (dev, 
+Environment variables are usually set before the application starts
+(not changed while running), and they're text-based rather than UI
+toggles. They're also specific to each deployment environment (dev,
 staging, production).
 ```
 
@@ -870,22 +904,26 @@ When you encounter a concept not in this library, create a new metaphor by:
 **Always structure content in this order:**
 
 **1. The Problem (Why)**
+
 ```markdown
-When building applications, you often need to know when something 
-happens on another platform—like when a payment completes, a file 
-finishes uploading, or a deployment succeeds. Constantly checking 
+When building applications, you often need to know when something
+happens on another platform—like when a payment completes, a file
+finishes uploading, or a deployment succeeds. Constantly checking
 for updates (polling) wastes resources and creates delays.
 ```
 
 **2. The Solution (What)**
+
 ```markdown
-Webhooks solve this by pushing notifications to you. When an event 
+Webhooks solve this by pushing notifications to you. When an event
 happens, we immediately send a message to your server with the details.
 ```
 
 **3. The Value (Why It Matters)**
+
 ```markdown
 This means:
+
 - Your application responds in real-time instead of polling
 - You save resources (no constant checking)
 - Users get faster updates
@@ -893,8 +931,10 @@ This means:
 ```
 
 **4. The Use Cases (When)**
+
 ```markdown
 Common scenarios:
+
 - Triggering workflows when deployments complete
 - Updating your database when content changes
 - Sending notifications when payments are processed
@@ -902,8 +942,10 @@ Common scenarios:
 ```
 
 **5. The Implementation (How)**
+
 ```markdown
 To set up a webhook:
+
 1. Create an endpoint URL where we'll send notifications
 2. Configure which events you want to receive
 3. Verify requests are from us (using signatures)
@@ -945,7 +987,7 @@ Focus on outcomes, when to involve technical help, business impact
 
 **Example in Practice:**
 
-```markdown
+````markdown
 ## Webhook Signature Verification
 
 ---
@@ -970,11 +1012,13 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## 📋 Simplification Overview
 
 **What was confusing:**
+
 - [Pattern 1 - e.g., Heavy acronym use without expansion]
 - [Pattern 2 - e.g., Assumed understanding of HTTP protocols]
 - [Pattern 3 - e.g., Jumped to implementation without explaining purpose]
 
 **Approach taken:**
+
 - [Strategy 1 - e.g., Added one-sentence summaries for each concept]
 - [Strategy 2 - e.g., Expanded all acronyms on first use]
 - [Strategy 3 - e.g., Added "Why this matters" to each section]
@@ -985,9 +1029,11 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## Section: [Original Heading]
 
 ### 📄 Original Content
-
 ```
+````
+
 [Exact text from source, formatting preserved]
+
 ```
 
 ### ⚠️ Issues Identified
@@ -1006,21 +1052,21 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 
 ### ✨ Simplified Version
 
-**In Plain Language:**  
+**In Plain Language:**
 [One crisp sentence capturing the essence without jargon]
 
-**What It Is:**  
-[2-3 paragraphs building understanding from basics. Define terms. 
+**What It Is:**
+[2-3 paragraphs building understanding from basics. Define terms.
 Explain concepts. Build progressively. No jargon assumed.]
 
-**Why It Matters:**  
+**Why It Matters:**
 [Value proposition and concrete benefits]
 
 - **Benefit 1:** [Specific, concrete impact]
 - **Benefit 2:** [Specific, concrete impact]
 - **Benefit 3:** [Specific, concrete impact]
 
-**When You'd Use This:**  
+**When You'd Use This:**
 
 - **Scenario 1:** [Realistic use case with context]
   - Example: "When building a chat application that needs real-time message delivery..."
@@ -1031,23 +1077,23 @@ Explain concepts. Build progressively. No jargon assumed.]
 - **Scenario 3:** [Realistic use case with context]
   - Example: "When triggering post-deployment tasks like cache clearing..."
 
-**Think of It Like:**  
+**Think of It Like:**
 [Tech-adjacent metaphor with detailed explanation]
 
 [Full metaphor explanation, making connections explicit]
 
-**Where this metaphor breaks down:**  
+**Where this metaphor breaks down:**
 [Acknowledge limitations honestly]
 
-**Common Pitfalls:**  
+**Common Pitfalls:**
 
-- **Pitfall:** [What people commonly misunderstand]  
+- **Pitfall:** [What people commonly misunderstand]
   **Reality:** [Correction with explanation]
 
-- **Pitfall:** [Common mistake]  
+- **Pitfall:** [Common mistake]
   **Reality:** [How it actually works]
 
-**Related Concepts:**  
+**Related Concepts:**
 [Connections to things readers might already know]
 
 - "If you've used [familiar concept], this works similarly..."
@@ -1124,6 +1170,7 @@ After the main simplification and summary, I include a **"Suggestions for Enhanc
 **Format:**
 
 Each suggestion includes:
+
 - **Line reference:** Specific location in the original document
 - **Section name:** What part of the doc this applies to
 - **Current approach:** What's there now
@@ -1133,11 +1180,9 @@ Each suggestion includes:
 
 **Example:**
 
-```markdown
+````markdown
 ---
-
 ## 📝 Suggestions for Enhancement
-
 ---
 
 ## 4. Suggestions for Enhancement
@@ -1154,11 +1199,13 @@ These suggestions show where additional patterns could improve accessibility:
 **Suggested enhancement:** Add API path for technical users who prefer code
 
 **Why this helps:**
+
 - Serves both UI users and developers with their preferred method
 - Technical users can automate the process via API
 - Provides complete coverage for mixed audiences
 
 **Implementation:**
+
 ```markdown
 ### Via API
 
@@ -1167,18 +1214,18 @@ These suggestions show where additional patterns could improve accessibility:
 
 \`\`\`bash
 curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/always_use_https" \\
-  -H "Authorization: Bearer {token}" \\
-  -d '{"value":"on"}'
+-H "Authorization: Bearer {token}" \\
+-d '{"value":"on"}'
 \`\`\`
 
 **Response:**
 \`\`\`json
 {
-  "success": true,
-  "result": {
-    "id": "always_use_https",
-    "value": "on"
-  }
+"success": true,
+"result": {
+"id": "always_use_https",
+"value": "on"
+}
 }
 \`\`\`
 
@@ -1195,6 +1242,7 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 **Suggested enhancement:** Move advanced technical details to collapsible section
 
 **Why this helps:**
+
 - Beginners get the simple explanation without being overwhelmed
 - Experts can expand for full technical depth
 - Maintains clear progressive disclosure
@@ -1202,15 +1250,17 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 
 **Implementation:**
 \`\`\`markdown
+
 ## How TLS Encryption Works
 
-Your connection is encrypted using industry-standard TLS 1.3 protocol, 
+Your connection is encrypted using industry-standard TLS 1.3 protocol,
 ensuring no one can intercept your data in transit.
 
 <details>
 <summary>For technical users: Cipher suite details</summary>
 
 We support TLS 1.3 with modern AEAD cipher suites including:
+
 - TLS_AES_128_GCM_SHA256
 - TLS_AES_256_GCM_SHA384
 - TLS_CHACHA20_POLY1305_SHA256
@@ -1230,6 +1280,7 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 **Suggested enhancement:** Call out recommended default for most users
 
 **Why this helps:**
+
 - Reduces decision paralysis for uncertain users
 - Provides a safe starting point
 - Guides users toward best security practices
@@ -1237,22 +1288,23 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 
 **Implementation:**
 \`\`\`markdown
+
 ### Encryption Modes
 
 **Recommended for most sites:** Full (Strict)
 
-Provides maximum security by validating your origin server's 
-certificate. This is the best option if your server has a valid SSL 
+Provides maximum security by validating your origin server's
+certificate. This is the best option if your server has a valid SSL
 certificate installed.
 
 #### Other Options
 
 - **Off:** No encryption (Not recommended - only use for testing)
-- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your 
+- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your
   server doesn't have SSL)
 - **Full:** Encrypts entire path but doesn't validate certificate
 - **Full (Strict):** Maximum security with certificate validation ✅
-\`\`\`
+  \`\`\`
 
 ---
 
@@ -1264,6 +1316,7 @@ certificate installed.
 **Suggested enhancement:** Add realistic use case showing feature in action
 
 **Why this helps:**
+
 - Makes abstract benefits concrete and relatable
 - Helps users visualize how they'd use this
 - Provides "aha moment" of recognition
@@ -1275,19 +1328,21 @@ certificate installed.
 Prevents attackers from overwhelming your site with fake traffic.
 
 **Real scenario:**
-An e-commerce site during Black Friday gets hit by bots trying to 
-buy limited inventory. DDoS protection automatically filters out 
-the bot traffic, letting real customers complete their purchases 
+An e-commerce site during Black Friday gets hit by bots trying to
+buy limited inventory. DDoS protection automatically filters out
+the bot traffic, letting real customers complete their purchases
 while the attack is absorbed across Cloudflare's network.
 
-Without protection, the site would crash within minutes, losing 
+Without protection, the site would crash within minutes, losing
 thousands in sales.
 \`\`\`
 ```
+````
 
 **When to include suggestions:**
 
 Include this section when:
+
 - Multi-path opportunities exist (Dashboard + API)
 - Technical details could be collapsed
 - Missing recommended defaults
@@ -1298,6 +1353,7 @@ Include this section when:
 **Placement:**
 
 The Suggestions section appears:
+
 - After the "Summary & Recommendations" section
 - Before the "Next Steps" section
 - Clearly separated with heading and explanation
@@ -1335,7 +1391,7 @@ Before finalizing any simplified content, verify:
 ❌ "Clearly, this requires..."  
 ❌ "As everyone knows..."  
 ❌ "It's easy to..."  
-❌ "All you have to do is..."  
+❌ "All you have to do is..."
 
 **Use these respectful alternatives:**
 
@@ -1344,34 +1400,38 @@ Before finalizing any simplified content, verify:
 ✅ "This requires..."  
 ✅ "Here's how this works..."  
 ✅ "This involves..."  
-✅ "The process is..."  
+✅ "The process is..."
 
 ### Accuracy Is Non-Negotiable
 
 **Good simplification:**
+
 ```markdown
-Webhooks send HTTP POST requests to your endpoint URL whenever 
-specified events occur. Think of it as a notification system where 
+Webhooks send HTTP POST requests to your endpoint URL whenever
+specified events occur. Think of it as a notification system where
 we call your server instead of you constantly checking ours.
 ```
-*Accurate, clear, uses metaphor effectively*
+
+_Accurate, clear, uses metaphor effectively_
 
 **Bad simplification:**
+
 ```markdown
 Webhooks let programs talk to each other.
 ```
-*Too vague, loses important details, not actually helpful*
+
+_Too vague, loses important details, not actually helpful_
 
 **When complex accuracy is needed:**
 
 Use progressive disclosure:
 
 ```markdown
-**Simplified:** Rate limiting controls how many requests you can 
+**Simplified:** Rate limiting controls how many requests you can
 make in a time period, like 100 requests per minute.
 
-**More precisely:** Rate limits apply per API key and reset on a 
-sliding window. If you hit the limit, you'll receive a 429 status 
+**More precisely:** Rate limits apply per API key and reset on a
+sliding window. If you hit the limit, you'll receive a 429 status
 code with a Retry-After header indicating when you can try again.
 ```
 
@@ -1380,6 +1440,7 @@ code with a Retry-After header indicating when you can try again.
 #### API Documentation
 
 Focus on:
+
 - What the endpoint does (purpose)
 - When you'd use it (scenarios)
 - What you send (parameters explained)
@@ -1388,6 +1449,7 @@ Focus on:
 - Error handling (what can go wrong)
 
 **Add value through:**
+
 - Explaining parameter purposes, not just types
 - Showing realistic request/response examples
 - Clarifying common misunderstandings
@@ -1396,6 +1458,7 @@ Focus on:
 #### Architecture Documentation
 
 Focus on:
+
 - Problem being solved
 - Why this approach was chosen
 - Tradeoffs made (what was gained/lost)
@@ -1403,6 +1466,7 @@ Focus on:
 - Alternatives considered
 
 **Add value through:**
+
 - Explaining decision rationale
 - Making tradeoffs explicit
 - Providing context for choices
@@ -1411,12 +1475,14 @@ Focus on:
 #### Code Documentation
 
 Focus on:
+
 - What the code accomplishes
 - Why it's structured this way
 - Key concepts or patterns used
 - What to watch out for
 
 **Add value through:**
+
 - Plain-language "reading guides"
 - Explaining non-obvious choices
 - Clarifying complex logic
@@ -1454,22 +1520,25 @@ Focus on:
 ## 📋 Simplification Overview
 
 **What was done well:**
+
 - Clear section headings with logical flow
 - Terms defined on first use
 - Good use of examples
 - "Why" explained before "how"
 
 **Minor improvements suggested:**
+
 - Could add a tech-adjacent metaphor for [concept]
 - Section 3 could benefit from a concrete use case
 - Consider adding "common pitfalls" to section 5
 
 **Overall assessment:**
-This documentation is already quite accessible. The suggestions above 
+This documentation is already quite accessible. The suggestions above
 are minor enhancements rather than necessary corrections.
 ```
 
 **Avoid:**
+
 - Adding unnecessary verbosity
 - Creating problems that don't exist
 - Over-explaining clear content
@@ -1485,6 +1554,7 @@ are minor enhancements rather than necessary corrections.
    - Preserve necessary complexity
 
 2. **Layer explanations**
+
    ```markdown
    **High-level:** [What it accomplishes]
    **How it works:** [Simplified mechanism]
@@ -1511,7 +1581,8 @@ are minor enhancements rather than necessary corrections.
    - Preserve technical correctness
 
 2. **Add explanatory context**
-   ```markdown
+
+   ````markdown
    **What this code does:**
    [Plain-language explanation]
 
@@ -1519,12 +1590,17 @@ are minor enhancements rather than necessary corrections.
    [Architectural rationale]
 
    **Key points to understand:**
+
    - [Important concept 1]
    - [Important concept 2]
 
    ```python
    [Original code, unchanged]
    ```
+   ````
+
+   ```
+
    ```
 
 3. **Create "reading guides"**
@@ -1541,9 +1617,10 @@ are minor enhancements rather than necessary corrections.
    - Leave component code unchanged
 
 2. **Explain component purpose**
+
    ```markdown
    **What this component does:**
-   The <CodeBlock> component displays syntax-highlighted code with 
+   The <CodeBlock> component displays syntax-highlighted code with
    copy functionality, making it easier for readers to use the examples.
    ```
 
@@ -1554,7 +1631,7 @@ are minor enhancements rather than necessary corrections.
 
 ## Future Enhancements
 
-*Documented for future implementation*
+_Documented for future implementation_
 
 ### Planned Features
 
@@ -1567,19 +1644,21 @@ Support for code files with inline documentation:
 def process_webhook(payload, signature):
     """
     Processes incoming webhook notifications.
-    
+
     Verifies signature, parses payload, triggers handlers.
     """
     # Implementation...
 ```
 
 **Planned behavior:**
+
 - Extract docstrings and comments
 - Simplify technical language in comments
 - Add explanatory prose for complex logic
 - Generate "code walkthrough" guides
 
 **Supported formats:**
+
 - `.js`, `.ts`, `.tsx` (JavaScript/TypeScript)
 - `.py` (Python)
 - `.go` (Go)
@@ -1605,6 +1684,7 @@ Quantitative analysis:
 - **Context gap analysis** - Identify missing "why" and "when" statements
 
 **Auto-prioritization:**
+
 - Sort sections by complexity
 - Focus on highest-value simplifications
 - Generate complexity reports
@@ -1646,63 +1726,65 @@ Returns a `webhook` object.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-Set up automatic notifications that we'll send to your server whenever 
+Set up automatic notifications that we'll send to your server whenever
 specific events occur.
 
 **What It Is:**
-A webhook subscription tells our system to notify your application 
-when certain events happen (like a deployment completing or content 
-being published). Instead of your application constantly checking for 
+A webhook subscription tells our system to notify your application
+when certain events happen (like a deployment completing or content
+being published). Instead of your application constantly checking for
 updates (polling), we push notifications to you the moment events occur.
 
 **Why It Matters:**
+
 - **Real-time updates** - Your application responds immediately
 - **Resource efficiency** - No wasted API calls checking for changes
 - **Reliability** - You never miss an event
 - **Automation** - Trigger workflows automatically
 
 **When You'd Use This:**
+
 - **Deployment notifications:** Trigger post-deployment tasks when builds complete
 - **Content synchronization:** Update your CMS when content changes
 - **Monitoring:** Alert your team when errors occur
 - **Integration:** Connect multiple systems to respond to events
 
 **Think of It Like:**
-A webhook is like setting up a doorbell notification on your phone. 
-Instead of constantly checking your front door camera to see if someone 
-arrived (polling), the doorbell alerts you the moment someone presses 
-it (push notification). You only respond when there's actually something 
+A webhook is like setting up a doorbell notification on your phone.
+Instead of constantly checking your front door camera to see if someone
+arrived (polling), the doorbell alerts you the moment someone presses
+it (push notification). You only respond when there's actually something
 to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have small delays due to 
-network transmission. Also, webhooks can fail if your server is down 
+Doorbells are instantaneous, while webhooks have small delays due to
+network transmission. Also, webhooks can fail if your server is down
 (like a broken doorbell), so you need retry logic.
 
 **Parameters Explained:**
 
-- **`endpoint`** - The URL where we'll send notifications (your server's 
+- **`endpoint`** - The URL where we'll send notifications (your server's
   address that listens for webhook events). Must use HTTPS for security.
 
-- **`events`** - Which events you want to receive (like `deployment.succeeded` 
+- **`events`** - Which events you want to receive (like `deployment.succeeded`
   or `content.published`). You choose only the events you care about.
 
-- **`secret`** - Optional security key for verifying notifications actually 
+- **`secret`** - Optional security key for verifying notifications actually
   come from us. We use this to create a signature you can verify.
 
 **Common Pitfalls:**
 
 - **Pitfall:** Thinking webhooks are 100% reliable  
-  **Reality:** Network issues or server downtime can cause missed notifications. 
+  **Reality:** Network issues or server downtime can cause missed notifications.
   Implement retry logic and consider periodic polling as a backup.
 
 - **Pitfall:** Not verifying signatures  
-  **Reality:** Without signature verification, attackers could send fake 
+  **Reality:** Without signature verification, attackers could send fake
   webhooks to trigger unauthorized actions.
 
 **Related Concepts:**
-If you've used RSS feeds, webhooks work similarly—both push updates to 
-you. The difference is webhooks are programmable and work with any type 
+If you've used RSS feeds, webhooks work similarly—both push updates to
+you. The difference is webhooks are programmable and work with any type
 of event, not just content updates.
 ```
 
@@ -1713,8 +1795,8 @@ of event, not just content updates.
 ```markdown
 ## Edge Deployment Architecture
 
-We've implemented a globally distributed edge architecture utilizing 
-V8 isolates for multi-tenant execution with microsecond cold starts 
+We've implemented a globally distributed edge architecture utilizing
+V8 isolates for multi-tenant execution with microsecond cold starts
 and automatic geographic distribution.
 ```
 
@@ -1724,40 +1806,42 @@ and automatic geographic distribution.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-We run your code on servers located around the world, close to your 
+We run your code on servers located around the world, close to your
 users, making responses nearly instant regardless of where users are.
 
 **What It Is:**
-Traditional servers run in specific data centers—if your server is in 
-Virginia and your user is in Singapore, every request travels across 
-the world and back (adding hundreds of milliseconds). Our edge 
-architecture runs your code on servers in hundreds of cities worldwide, 
+Traditional servers run in specific data centers—if your server is in
+Virginia and your user is in Singapore, every request travels across
+the world and back (adding hundreds of milliseconds). Our edge
+architecture runs your code on servers in hundreds of cities worldwide,
 so requests are handled by the nearest server.
 
 **Why It Matters:**
+
 - **Speed:** Users get responses in 10-50ms instead of 200-500ms
 - **Reliability:** If one location fails, others continue serving traffic
 - **Scale:** Handles traffic spikes automatically across all locations
 - **Simplicity:** You deploy once; we handle global distribution
 
 **When You'd Use This:**
+
 - **Global applications:** Users are distributed worldwide
 - **API endpoints:** Need fast response times everywhere
 - **Dynamic content:** Content that can't be cached must still be fast
 - **High availability:** Can't afford regional outages
 
 **Think of It Like:**
-Instead of one central warehouse shipping products nationwide (slow 
-delivery to distant customers), you have local warehouses in every major 
-city. When someone orders, it ships from their nearest warehouse. Same 
+Instead of one central warehouse shipping products nationwide (slow
+delivery to distant customers), you have local warehouses in every major
+city. When someone orders, it ships from their nearest warehouse. Same
 product, faster delivery, handled automatically.
 
 **The Technical Approach:**
 
-We use "V8 isolates"—lightweight execution environments that start in 
-microseconds (thousandths of a millisecond). Traditional "serverless" 
-functions use containers that take 50-500ms to start. Isolates are 
-fast enough that we don't need to keep them warm; they start on-demand 
+We use "V8 isolates"—lightweight execution environments that start in
+microseconds (thousandths of a millisecond). Traditional "serverless"
+functions use containers that take 50-500ms to start. Isolates are
+fast enough that we don't need to keep them warm; they start on-demand
 for each request.
 
 **Why this architecture:**
@@ -1768,11 +1852,12 @@ We evaluated three approaches:
 3. **Isolate-based edge:** Global + fast (our choice)
 
 **Tradeoff made:**
-Isolates have some limitations compared to full containers (no arbitrary 
-system libraries, limited execution time). We accepted these constraints 
+Isolates have some limitations compared to full containers (no arbitrary
+system libraries, limited execution time). We accepted these constraints
 for the massive speed improvement.
 
 **Common Pitfalls:**
+
 - **Pitfall:** Assuming it works like traditional servers  
   **Reality:** Stateless execution—no persistent local storage, no background jobs
 
@@ -1780,20 +1865,22 @@ for the massive speed improvement.
   **Reality:** Implements web standards, not full Node.js APIs
 
 **Related Concepts:**
-If you've used CDNs (Content Delivery Networks), this is similar but 
-for code execution, not just static files. Like a CDN distributes 
+If you've used CDNs (Content Delivery Networks), this is similar but
+for code execution, not just static files. Like a CDN distributes
 content globally, we distribute code execution globally.
 ```
 
 ## Remember
 
 **Your mission:**
+
 - Make technical concepts accessible
 - Maintain technical accuracy
 - Respect reader intelligence
 - Focus on understanding
 
 **Always include:**
+
 - One-sentence plain language summary
 - Clear "why" and "when" explanations
 - Tech-adjacent metaphor with limitations
@@ -1801,25 +1888,28 @@ content globally, we distribute code execution globally.
 - Use cases grounding abstract concepts
 
 **Quality standards:**
+
 - Technical accuracy is non-negotiable
 - Metaphors must clarify, not confuse
 - Tone must be professional and respectful
 - No condescending language ever
 
 **Process:**
+
 1. Ask which sections to focus on
 2. Identify specific issues (jargon, assumptions, logic, context)
 3. Generate complete before/after comparison
 4. Prompt for next steps
 
 **Output:**
+
 - Create `.eli5.md` file in same directory
 - Include all required elements per section
 - Provide actionable recommendations
 - Offer clear next-step options
 
 **Philosophy:**
-Technical expertise should never be a barrier to understanding. Every 
+Technical expertise should never be a barrier to understanding. Every
 person deserves clear, accurate, respectful documentation.
 
 ---
@@ -1831,4 +1921,3 @@ person deserves clear, accurate, respectful documentation.
 **License:** MIT  
 **Version:** 1.0  
 **Last Updated:** February 2026
-
diff --git a/.agents/skills/eli5/references/content-type-guide.md b/.agents/skills/eli5/references/content-type-guide.md
index 85d544a7c071296..1454cfea7242833 100644
--- a/.agents/skills/eli5/references/content-type-guide.md
+++ b/.agents/skills/eli5/references/content-type-guide.md
@@ -7,6 +7,7 @@ Operational guide for detecting and simplifying different documentation types.
 ## Purpose
 
 This guide provides:
+
 - **Detection criteria** for identifying content types
 - **Required elements** checklist for each type
 - **Simplification patterns** specific to each type
@@ -21,6 +22,7 @@ This guide provides:
 For each content type below, the enhancement patterns are designed to ADD MINIMAL CONTEXT AND EXAMPLES, not restructure or massively expand.
 
 **Universal constraints:**
+
 - Maximum 1-2 examples per major concept
 - Each example: 5-15 lines
 - Inline "why" explanations: 1-2 sentences
@@ -31,6 +33,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Minimal testing guidance (3-5 commands for tutorials)
 
 **When patterns below suggest "Add [section]":**
+
 - Interpret as "enhance inline" not "create separate major section"
 - Keep additions brief and integrated
 - Target 1.5-2x expansion, not 5-10x
@@ -39,13 +42,13 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 ## Content Type Overview
 
-| Type | Purpose | Key Pattern | Example |
-|------|---------|-------------|---------|
-| **Overview** | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages |
-| **Concept** | Build understanding of "why" | Analogy → Plain → Technical | "What is rate limiting?" |
-| **How To** | Enable task completion | Context → Multi-path steps | "Enable HTTPS" |
-| **Reference** | Provide comprehensive specs | Use-case organization | API parameters, headers |
-| **Tutorial** | Teach through application | Build → Enhance → Polish | "Build a URL shortener" |
+| Type          | Purpose                             | Key Pattern                  | Example                  |
+| ------------- | ----------------------------------- | ---------------------------- | ------------------------ |
+| **Overview**  | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages    |
+| **Concept**   | Build understanding of "why"        | Analogy → Plain → Technical  | "What is rate limiting?" |
+| **How To**    | Enable task completion              | Context → Multi-path steps   | "Enable HTTPS"           |
+| **Reference** | Provide comprehensive specs         | Use-case organization        | API parameters, headers  |
+| **Tutorial**  | Teach through application           | Build → Enhance → Polish     | "Build a URL shortener"  |
 
 ---
 
@@ -54,6 +57,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 ### Detection Criteria
 
 **Look for:**
+
 - Product/feature name in title or H1
 - Feature lists or capability descriptions
 - "What is [Product]" sections
@@ -62,6 +66,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Lack of step-by-step instructions
 
 **Confidence signals:**
+
 - Multiple features described briefly
 - High-level product description
 - Links to detailed documentation
@@ -69,6 +74,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Pricing or plan information
 
 **Example titles:**
+
 - "Cloudflare Workers"
 - "Introduction to Gateway"
 - "What is Workers KV?"
@@ -77,7 +83,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 - [ ] Opening benefit statement (what problem solved)
 - [ ] Problem/Solution/Benefit structure
-- [ ] "Perfect for" self-identification section  
+- [ ] "Perfect for" self-identification section
 - [ ] Clear call-to-action ("Get started" link)
 - [ ] Feature descriptions with benefits (not just specs)
 - [ ] Technical architecture separated/collapsed
@@ -87,12 +93,14 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Target: 1.5-2x original length**
 
 **Minimal additions:**
+
 1. **Add 2-4 sentence problem statement** (if completely missing) at document start
 2. **Add 1-2 use case examples inline** (5-10 lines each) showing who benefits
 3. **Add inline "why"** (1 sentence) when introducing features
 4. **Define jargon on first use** (brief inline definition)
 
 **Structure to preserve:**
+
 - Keep original opening and headings
 - Don't reorganize sections
 - Don't move architecture (just add brief intro if it leads)
@@ -100,41 +108,46 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Example enhancement:**
 
 Original (8 lines):
+
 ```markdown
 # Internal DNS
 
 Manage DNS records for your private network.
 
-Internal DNS zones pair with Gateway resolver policies to control 
+Internal DNS zones pair with Gateway resolver policies to control
 DNS query responses.
 
 ## Features
+
 - Create internal zones
 - Configure views
 - Link to Gateway
 ```
 
 Enhanced (15 lines - 1.9x):
+
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS 
+Manage DNS records for your private network without running your own DNS
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS query 
+Internal DNS zones pair with Gateway resolver policies to control DNS query
 responses based on context (source IP, user identity, domain).
 
-**Example use case:** A multi-region company creates separate views for London 
-and SF offices. Users query the same hostname (api.company.internal) but get 
+**Example use case:** A multi-region company creates separate views for London
+and SF offices. Users query the same hostname (api.company.internal) but get
 different IP addresses based on location.
 
 ## Features
+
 - Create internal zones - Private namespaces accessible only via Gateway
 - Configure views - Logical groupings that route different users to different resources
 - Link to Gateway - Resolver policies determine which view to use
 ```
 
 What was added:
+
 - 1 sentence "why" (without running own servers)
 - Brief context for zones (source IP, user identity)
 - 1 example (3 lines)
@@ -156,6 +169,7 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
+
 - "What is..." or "Understanding..." titles
 - Explanatory content (not procedural)
 - "How it works" sections
@@ -164,6 +178,7 @@ What was added:
 - Analogies or metaphors (sometimes)
 
 **Confidence signals:**
+
 - Explains mechanisms, not steps
 - Educational tone
 - Links to related concepts
@@ -171,6 +186,7 @@ What was added:
 - Multiple explanation approaches
 
 **Example titles:**
+
 - "Understanding Rate Limiting"
 - "How Caching Works"
 - "What is Edge Computing?"
@@ -188,6 +204,7 @@ What was added:
 ### Simplification Pattern
 
 **Structure:**
+
 ```markdown
 # [Concept Name]
 
@@ -196,6 +213,7 @@ What was added:
 **What it is:** [Plain English definition without jargon]
 
 **Why you need it:**
+
 - [Benefit 1]
 - [Benefit 2]
 - [Benefit 3]
@@ -203,6 +221,7 @@ What was added:
 **How it works:** [Simplified technical explanation]
 
 **Real scenarios:**
+
 - [Use case 1 with context]
 - [Use case 2 with context]
 - [Use case 3 with context]
@@ -228,6 +247,7 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
+
 - Action verbs in titles (Configure, Enable, Create, Set up)
 - Numbered steps or procedures
 - "Prerequisites" sections
@@ -236,6 +256,7 @@ What was added:
 - Command examples or code blocks
 
 **Confidence signals:**
+
 - Clear sequential structure
 - Specific actionable steps
 - Tool/UI references
@@ -243,6 +264,7 @@ What was added:
 - Troubleshooting sections
 
 **Example titles:**
+
 - "Enable Always Use HTTPS"
 - "Configure DNS Settings"
 - "Create a Worker"
@@ -265,6 +287,7 @@ What was added:
 **For how-to guides, preserve existing steps and add minimal context:**
 
 **Minimal additions:**
+
 1. **Add 1-2 sentence "what this accomplishes"** at top (if missing)
 2. **Add inline "why"** (1 sentence) for non-obvious steps
 3. **Add 1 example** showing when you'd use this (3-5 lines)
@@ -272,6 +295,7 @@ What was added:
 5. **Add 1-2 troubleshooting notes** for critical failures only
 
 **Preserve:**
+
 - Original step numbering and flow
 - Existing Dashboard/API paths (don't create new ones)
 - All screenshots and UI elements
@@ -280,6 +304,7 @@ What was added:
 **Example enhancement:**
 
 Original (12 lines):
+
 ```markdown
 # Create a DNS View
 
@@ -297,10 +322,11 @@ Use the create view endpoint with zone IDs.
 ```
 
 Enhanced (20 lines - 1.67x):
+
 ```markdown
 # Create a DNS View
 
-Create a logical grouping of zones that determines which DNS records users see. 
+Create a logical grouping of zones that determines which DNS records users see.
 Useful for multi-region setups or environment separation.
 
 **Example:** Create "London View" and "SF View" to route users to nearest datacenter.
@@ -327,6 +353,7 @@ curl -X POST /api/views -d '{"name": "London View", "zone_ids": ["id1", "id2"]}'
 ```
 
 What was added:
+
 - 2-sentence purpose statement (2 lines)
 - 1 example (1 line)
 - Inline context for 2 steps (2 lines)
@@ -336,11 +363,13 @@ What was added:
 - Total: 8 lines added to 12 original = 20 lines (1.67x) ✅
 
 **What was NOT added:**
+
 - Comprehensive troubleshooting section
 - Multiple examples
 - Separate "Understanding Views" section
 - Extensive testing procedures
-```
+
+````
 
 ### Common Issues to Fix
 
@@ -414,7 +443,7 @@ What was added:
 **Example:**
 ```[language]
 [Realistic usage example]
-```
+````
 
 **Result:** [What happens when this is used]
 
@@ -423,7 +452,8 @@ What was added:
 ### [Next Option]
 
 [Same structure...]
-```
+
+````
 
 ### Common Issues to Fix
 
@@ -513,24 +543,25 @@ Add records to the zone.
 curl -X POST https://api.cloudflare.com/zones/ID/dns_records \\
   -d '{"type": "A", "name": "app", "content": "192.168.1.100"}'
 \`\`\`
-```
+````
 
 Enhanced (35 lines - 1.75x):
+
 ```markdown
 ## Step 1: Create the zone
 
-Create an internal zone that will contain your DNS records. This zone is only 
+Create an internal zone that will contain your DNS records. This zone is only
 accessible via Gateway (not public DNS).
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones \\
-  -d '{
-    "name": "company.internal",  # Your internal domain
-    "type": "internal"             # Marks as internal-only
-  }'
+-d '{
+"name": "company.internal", # Your internal domain
+"type": "internal" # Marks as internal-only
+}'
 \`\`\`
 
-**Example use:** A company creates company.internal for all internal apps 
+**Example use:** A company creates company.internal for all internal apps
 (app.company.internal, api.company.internal, db.company.internal).
 
 ## Step 2: Add DNS records
@@ -539,24 +570,27 @@ Add records mapping hostnames to private IPs.
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones/ZONE_ID/dns_records \\
-  -d '{
-    "type": "A",                           # Address record
-    "name": "app.company.internal",        # Full hostname
-    "content": "192.168.1.100"             # Private IP
-  }'
+-d '{
+"type": "A", # Address record
+"name": "app.company.internal", # Full hostname
+"content": "192.168.1.100" # Private IP
+}'
 \`\`\`
 
-**Test:** 
+**Test:**
 \`\`\`bash
 nslookup app.company.internal
+
 # Expected: Returns 192.168.1.100
+
 \`\`\`
 
-**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP 
+**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP
 connection or DNS settings.
 ```
 
 What was added:
+
 - Brief "why" for each step (1 sentence)
 - Inline code comments (3-4 comments)
 - 1 example showing usage (2 lines)
@@ -565,6 +599,7 @@ What was added:
 - Total: 15 lines added to 20 original = 35 lines (1.75x) ✅
 
 **What was NOT added:**
+
 - Separate "What you'll build" section
 - Multiple examples
 - Comprehensive troubleshooting section
@@ -614,16 +649,19 @@ What was added:
 Sometimes documentation combines types:
 
 ### Overview + How To
+
 **Pattern:** Product intro followed by quick start steps  
 **Approach:** Treat first section as Overview, steps as How To  
 **Example:** "Workers Overview" with "Deploy Your First Worker" steps
 
 ### Concept + Reference
+
 **Pattern:** Conceptual explanation followed by parameter reference  
 **Approach:** Layer explanation first, reference at bottom  
 **Example:** "Understanding Caching" + "Cache Headers Reference"
 
 ### Tutorial + Reference
+
 **Pattern:** Build project + API reference at end  
 **Approach:** Keep tutorial progressive, move reference to appendix  
 **Example:** "Build URL Shortener" + "Workers API Reference"
@@ -635,6 +673,7 @@ Sometimes documentation combines types:
 ## Quick Reference Cards
 
 ### Overview Page Card
+
 ```
 ✓ Opens with benefit statement
 ✓ Problem/Solution structure
@@ -644,6 +683,7 @@ Sometimes documentation combines types:
 ```
 
 ### Concept Page Card
+
 ```
 ✓ Analogy in first paragraph
 ✓ Plain definition
@@ -653,6 +693,7 @@ Sometimes documentation combines types:
 ```
 
 ### How To Page Card
+
 ```
 ✓ Context before steps
 ✓ Prerequisites listed
@@ -662,6 +703,7 @@ Sometimes documentation combines types:
 ```
 
 ### Reference Page Card
+
 ```
 ✓ Opening context
 ✓ Use-case organized
@@ -671,6 +713,7 @@ Sometimes documentation combines types:
 ```
 
 ### Tutorial Page Card
+
 ```
 ✓ "What you'll build"
 ✓ Prerequisites + time
diff --git a/.agents/skills/eli5/references/pattern-library.md b/.agents/skills/eli5/references/pattern-library.md
index 3d7b91b310a8918..f7ebb468915de2c 100644
--- a/.agents/skills/eli5/references/pattern-library.md
+++ b/.agents/skills/eli5/references/pattern-library.md
@@ -7,6 +7,7 @@ A reference collection of reusable before/after patterns for simplifying technic
 ## Purpose
 
 This library provides:
+
 - **Reusable patterns** for common simplification scenarios
 - **Jargon → Plain English** translations
 - **Before/after examples** demonstrating transformations
@@ -19,6 +20,7 @@ This library provides:
 **All patterns below demonstrate minimal, integrated enhancements (1.5-2x growth)**
 
 When applying these patterns:
+
 - ✅ Add inline, not as separate major sections
 - ✅ Integrate with existing content flow
 - ✅ Keep examples brief (5-15 lines each, max 1-2 examples)
@@ -32,6 +34,7 @@ When applying these patterns:
 When a pattern shows "Add [section]" → Interpret as "add brief inline content" not "create major new section"
 
 **Example:**
+
 - Pattern says: "Add use case example"
 - **Correct:** Add 5-10 line example inline with concept
 - **Incorrect:** Create separate "Use Case Examples" section with 4 detailed scenarios
@@ -44,23 +47,23 @@ When a pattern shows "Add [section]" → Interpret as "add brief inline content"
 
 Common technical terms and their accessible alternatives:
 
-| Technical Term | Plain English | Context Example |
-|----------------|---------------|-----------------|
-| **Implement** | Set up, turn on, use | "Set up two-factor authentication" not "Implement 2FA" |
-| **Utilize** | Use | "Use the API" not "Utilize the API" |
-| **Leverage** | Use, take advantage of | "Take advantage of caching" not "Leverage caching capabilities" |
-| **Execute** | Run | "Run the command" not "Execute the command" |
-| **Instantiate** | Create | "Create a new Worker" not "Instantiate a Worker" |
-| **Terminate** | Stop, end | "Stop the process" not "Terminate the process" |
-| **Subsequently** | Then, next | "Then, configure the settings" not "Subsequently, configure" |
-| **Optimal** | Best | "Best performance" not "Optimal performance" |
-| **Facilitate** | Help, enable | "This helps you deploy faster" not "Facilitates rapid deployment" |
-| **Invoke** | Call, trigger | "Call the function" not "Invoke the function" |
-| **Provision** | Set up, create | "Set up your server" not "Provision infrastructure" |
-| **Egress** | Outgoing data | "Data leaving your network" not "Egress traffic" |
-| **Ingress** | Incoming data | "Data entering your network" not "Ingress traffic" |
-| **Anycast** | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
-| **Propagation** | Spreading, updating | "Changes spread globally" not "Configuration propagates" |
+| Technical Term   | Plain English             | Context Example                                                      |
+| ---------------- | ------------------------- | -------------------------------------------------------------------- |
+| **Implement**    | Set up, turn on, use      | "Set up two-factor authentication" not "Implement 2FA"               |
+| **Utilize**      | Use                       | "Use the API" not "Utilize the API"                                  |
+| **Leverage**     | Use, take advantage of    | "Take advantage of caching" not "Leverage caching capabilities"      |
+| **Execute**      | Run                       | "Run the command" not "Execute the command"                          |
+| **Instantiate**  | Create                    | "Create a new Worker" not "Instantiate a Worker"                     |
+| **Terminate**    | Stop, end                 | "Stop the process" not "Terminate the process"                       |
+| **Subsequently** | Then, next                | "Then, configure the settings" not "Subsequently, configure"         |
+| **Optimal**      | Best                      | "Best performance" not "Optimal performance"                         |
+| **Facilitate**   | Help, enable              | "This helps you deploy faster" not "Facilitates rapid deployment"    |
+| **Invoke**       | Call, trigger             | "Call the function" not "Invoke the function"                        |
+| **Provision**    | Set up, create            | "Set up your server" not "Provision infrastructure"                  |
+| **Egress**       | Outgoing data             | "Data leaving your network" not "Egress traffic"                     |
+| **Ingress**      | Incoming data             | "Data entering your network" not "Ingress traffic"                   |
+| **Anycast**      | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
+| **Propagation**  | Spreading, updating       | "Changes spread globally" not "Configuration propagates"             |
 
 ---
 
@@ -71,6 +74,7 @@ Common technical terms and their accessible alternatives:
 ### Example: Internal DNS Documentation
 
 **Before (Original - 15 lines):**
+
 ```markdown
 # Internal DNS
 
@@ -83,6 +87,7 @@ Internal DNS zones pair with Gateway resolver policies.
 Use the dashboard or API to create an internal zone.
 
 ### Dashboard
+
 1. Navigate to Internal DNS
 2. Click Create Zone
 3. Enter zone name
@@ -90,25 +95,27 @@ Use the dashboard or API to create an internal zone.
 ```
 
 **After (Enhanced - 26 lines, 1.73x growth):**
+
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS 
+Manage DNS records for your private network without running your own DNS
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS 
+Internal DNS zones pair with Gateway resolver policies to control DNS
 responses based on source IP, user identity, or domain.
 
-**Example use case:** A multi-region company creates views for London and SF. 
-Users query api.company.internal but get different IPs based on location 
+**Example use case:** A multi-region company creates views for London and SF.
+Users query api.company.internal but get different IPs based on location
 (London users → 10.0.1.100, SF users → 10.0.2.100).
 
 ## Create a Zone
 
-Create an internal zone that will contain your DNS records. Zones are only 
+Create an internal zone that will contain your DNS records. Zones are only
 accessible via Gateway (not public DNS).
 
 ### Dashboard
+
 1. Navigate to Internal DNS → Zones
 2. Click **Create Zone**
 3. Enter zone name (e.g., company.internal)
@@ -118,8 +125,9 @@ accessible via Gateway (not public DNS).
 ```
 
 **What was added:**
+
 - 1 sentence explaining "why" (without running own servers) - 1 line
-- Brief context for resolver policies (source IP, user identity) - 1 line  
+- Brief context for resolver policies (source IP, user identity) - 1 line
 - 1 concrete example (3 lines)
 - Brief zone explanation (2 lines)
 - Inline step context (1 line each for 2 steps) - 2 lines
@@ -127,6 +135,7 @@ accessible via Gateway (not public DNS).
 - **Total added: 11 lines to 15 original = 26 lines (1.73x)** ✅
 
 **What was NOT added:**
+
 - No "What Problem Does Internal DNS Solve?" section
 - No "How It Works (Conceptual)" section before content
 - No diagram annotations
@@ -136,6 +145,7 @@ accessible via Gateway (not public DNS).
 - No separate "Understanding Zones" section
 
 **Why this works:**
+
 - Preserves original structure completely
 - Adds context inline where readers need it
 - Provides 1 concrete example for grounding
@@ -151,33 +161,37 @@ accessible via Gateway (not public DNS).
 ### Overview Pages
 
 **Before (Technical-first):**
+
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 isolates 
-for low-latency serverless code execution with sub-millisecond cold start 
+Product X is a distributed edge computing platform utilizing V8 isolates
+for low-latency serverless code execution with sub-millisecond cold start
 performance and global anycast deployment.
 ```
 
 **After (Benefit-first):**
+
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, scale 
+Run code worldwide without managing servers. Deploy in seconds, scale
 automatically, and pay only for what you use.
 
-**What problem it solves:** Maintaining global infrastructure is expensive 
+**What problem it solves:** Maintaining global infrastructure is expensive
 and complex. Product X runs your code in 300+ cities automatically.
 
 **Perfect for:**
+
 - Applications needing fast global performance
-- Teams wanting to skip server management  
+- Teams wanting to skip server management
 - Projects with variable traffic
 
 [Get started →]
 ```
 
 **Why this works:**
+
 - Opens with clear user value
 - Problem framing creates relevance
 - "Perfect for" helps self-identification
@@ -190,35 +204,39 @@ and complex. Product X runs your code in 300+ cities automatically.
 ### Concept Pages
 
 **Before (Abstract):**
+
 ```markdown
 ## Caching
 
-Caching stores frequently accessed data in high-speed storage layers to 
-reduce origin server load and improve response times through data locality 
+Caching stores frequently accessed data in high-speed storage layers to
+reduce origin server load and improve response times through data locality
 optimization.
 ```
 
 **After (Concrete):**
+
 ```markdown
 ## Caching
 
-**Think of it like:** A library's reserve desk. Popular books stay at the 
+**Think of it like:** A library's reserve desk. Popular books stay at the
 front desk for quick access instead of requiring trips to the distant stacks.
 
-**What it is:** Caching keeps copies of your frequently accessed files 
-(images, CSS, JavaScript) close to users, so they load instantly instead of 
+**What it is:** Caching keeps copies of your frequently accessed files
+(images, CSS, JavaScript) close to users, so they load instantly instead of
 being fetched from your origin server every time.
 
 **Why it matters:**
+
 - Pages load 10x faster (50ms vs 500ms)
 - Reduces server costs (fewer origin requests)
 - Handles traffic spikes (serves from cache, not origin)
 
-**When to use:** Any content that doesn't change constantly—images, stylesheets, 
+**When to use:** Any content that doesn't change constantly—images, stylesheets,
 blog posts, product pages.
 ```
 
 **Why this works:**
+
 - Analogy creates immediate mental model
 - Plain language explanation builds understanding
 - Benefits are concrete and measurable
@@ -231,6 +249,7 @@ blog posts, product pages.
 ### How To Pages
 
 **Before (Steps-only):**
+
 ```markdown
 ## Enable Feature X
 
@@ -241,7 +260,8 @@ blog posts, product pages.
 ```
 
 **After (Contextual multi-path):**
-```markdown
+
+````markdown
 ## Enable Feature X
 
 **What this does:** Protects your site from [specific threat] by [mechanism].
@@ -257,7 +277,7 @@ blog posts, product pages.
 4. Find **Feature X** and toggle it **On**
 5. Click **Save Changes** at the bottom
 
-💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes 
+💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes
 to see it working.
 
 ### Via API
@@ -270,12 +290,14 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_x_enabled": true}'
 ```
+````
 
 **Response:**
+
 ```json
 {
-  "success": true,
-  "result": {"feature_x_enabled": true}
+	"success": true,
+	"result": { "feature_x_enabled": true }
 }
 ```
 
@@ -287,7 +309,8 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 2. Check browser DevTools → Network tab
 3. Look for [specific indicator]
 4. You should see [expected result]
-```
+
+````
 
 **Why this works:**
 - Context explains purpose before steps
@@ -310,15 +333,16 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 **Content-Type:** MIME type. Examples: text/html, application/json
 
 **Expires:** Cache expiration date. Format: HTTP-date
-```
+````
 
 **After (Use-case organized):**
-```markdown
+
+````markdown
 ## Headers by Purpose
 
 ### Controlling Cache Behavior
 
-**When to use:** Make your site faster by controlling what gets cached and 
+**When to use:** Make your site faster by controlling what gets cached and
 for how long.
 
 #### Long-Term Caching (Static Assets)
@@ -327,15 +351,17 @@ for how long.
 
 **What it does:** Caches content for 1 year
 
-**When to use:** Files that never change, like `logo-v2.png` or 
+**When to use:** Files that never change, like `logo-v2.png` or
 `style.abc123.css` with version hash in filename
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
+````
 
-**Result:** First visitor downloads. Next year, everyone gets the cached 
+**Result:** First visitor downloads. Next year, everyone gets the cached
 version instantly.
 
 ---
@@ -349,6 +375,7 @@ version instantly.
 **When to use:** Content that updates occasionally—blog posts, product pages
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=3600
 ```
@@ -362,7 +389,8 @@ Cache-Control: public, max-age=3600
 **When to use:** Tell browsers what type of content they're receiving.
 
 [Continue pattern...]
-```
+
+````
 
 **Why this works:**
 - Organized by task, not alphabet
@@ -389,8 +417,9 @@ async function handleRequest(request) {
   const url = new URL(request.url)
   return new Response('Hello')
 }
-```
-```
+````
+
+````
 
 **After (Explained progression):**
 ```markdown
@@ -404,7 +433,7 @@ A working [specific thing] that [specific capability].
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience needed with 
+Developers comfortable with JavaScript. No prior experience needed with
 [platform], but you should understand HTTP requests and JSON.
 
 ### Time: 30 minutes
@@ -428,14 +457,16 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-```
+````
 
 **What this code does:**
+
 - **Line 2:** Listens for HTTP requests to your Worker
-- **Line 4:** Calls `handleRequest` to process each request  
+- **Line 4:** Calls `handleRequest` to process each request
 - **Line 8-12:** Returns a simple text response
 
 **Test it:**
+
 1. Deploy this code
 2. Visit your Worker's URL
 3. You should see: "Hello! It works!"
@@ -445,7 +476,8 @@ Great! Your Worker is running. Now let's add real functionality...
 ## Step 2: Parse URLs
 
 [Continue building progressively with explanations...]
-```
+
+````
 
 **Why this works:**
 - Sets clear expectations upfront
@@ -465,11 +497,13 @@ Features:
 - Global anycast network
 - Automatic scaling
 - Pay-per-request pricing
-```
+````
 
 **After:**
+
 ```markdown
 **What you get:**
+
 - **Fast everywhere:** Code runs in 300+ cities, close to every user
 - **Auto-scaling:** Handles 10 requests or 10 million without configuration
 - **Cost-efficient:** Pay only when code runs, not for idle servers
@@ -478,27 +512,29 @@ Features:
 ### Transform 2: Jargon Explanation → Layered Understanding
 
 **Before:**
+
 ```markdown
-DDoS mitigation employs anycast architecture to distribute volumetric attacks 
-across our edge network, utilizing L3/L4 packet inspection and L7 behavioral 
+DDoS mitigation employs anycast architecture to distribute volumetric attacks
+across our edge network, utilizing L3/L4 packet inspection and L7 behavioral
 analysis.
 ```
 
 **After:**
+
 ```markdown
 **In plain language:** Stops attackers from overwhelming your site with fake traffic.
 
-**How it protects you:** We have 300+ data centers. When an attack hits, we 
-spread it across all locations—like opening thousands of doors instead of one. 
+**How it protects you:** We have 300+ data centers. When an attack hits, we
+spread it across all locations—like opening thousands of doors instead of one.
 We also identify and block fake visitors before they reach your site.
 
-**What happens:** Your real visitors get through normally while attack traffic 
+**What happens:** Your real visitors get through normally while attack traffic
 is filtered out automatically.
 
 <details>
 <summary>For technical users</summary>
 
-Anycast distributes L3/L4 volumetric attacks across the network. L7 protection 
+Anycast distributes L3/L4 volumetric attacks across the network. L7 protection
 uses JS challenges and behavioral fingerprinting. [Architecture details →]
 
 </details>
@@ -507,21 +543,24 @@ uses JS challenges and behavioral fingerprinting. [Architecture details →]
 ### Transform 3: Assumed Knowledge → Explicit Prerequisites
 
 **Before:**
+
 ```markdown
 Configure your A record to point to the anycast IP.
 ```
 
 **After:**
+
 ```markdown
 Update your DNS A record to point to Cloudflare's IP address.
 
-**What's an A record?** It's the DNS entry that tells the internet where your 
+**What's an A record?** It's the DNS entry that tells the internet where your
 website lives (like an address in a phone book).
 
-**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap, 
+**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap,
 etc.). Look for "DNS Management" or "DNS Settings."
 
-**What to enter:** 
+**What to enter:**
+
 - Type: A
 - Name: @ (means your root domain)
 - Value: 192.0.2.1 (our IP address)
@@ -532,10 +571,12 @@ etc.). Look for "DNS Management" or "DNS Settings."
 ## Metaphor Templates
 
 ### Template: API Explanation
+
 ```markdown
 **Think of it like:** [Familiar interface concept]
 
 An API is like a restaurant menu. It shows you:
+
 - What's available to order (endpoints)
 - What details you need to provide (parameters: "no onions, extra cheese")
 - What you'll get back (response: your meal)
@@ -543,11 +584,12 @@ An API is like a restaurant menu. It shows you:
 
 You don't need to know how the kitchen works. Just order from the menu.
 
-**Where this breaks down:** Unlike restaurants where you wait, API responses 
+**Where this breaks down:** Unlike restaurants where you wait, API responses
 are usually instant. Also, APIs can return errors if your "order" is invalid.
 ```
 
 ### Template: Security Feature Explanation
+
 ```markdown
 **The threat:** [What attackers do]
 
@@ -559,22 +601,26 @@ Think of it like [security analogy]:
 [Concrete comparison that shows the protection model]
 
 **What happens automatically:**
+
 - [Protection 1]
 - [Protection 2]
 
 **What you control:**
+
 - [Setting 1]
 - [Setting 2]
 ```
 
 ### Template: Infrastructure Concept
+
 ```markdown
 **What it is:** [One-sentence plain English definition]
 
-**Real-world comparison:** 
+**Real-world comparison:**
 [Physical/familiar tech analog that maps 1:1 to key concepts]
 
 **Why it matters:**
+
 - [Benefit 1 with measurable impact]
 - [Benefit 2 with measurable impact]
 
@@ -590,24 +636,25 @@ Think of it like [security analogy]:
 
 ### When You See → Do This
 
-| **Original** | **Transform To** |
-|--------------|------------------|
-| Technical architecture first | Problem → Solution → Benefit |
-| Abstract concept | Analogy → Plain explanation → Technical |
-| Steps without context | Context → Prerequisites → Multi-path steps |
-| Alphabetical reference | Use-case groups → Two-tier descriptions |
-| Unexplained code | What you'll build → Progressive steps → Explained blocks |
-| Feature list | Problem/solution pairs with benefits |
-| Jargon without definition | Define inline or use plain alternative |
-| Missing "why" | Add value proposition upfront |
-| No use cases | Add 3-5 realistic scenarios |
-| Assumes knowledge | State prerequisites explicitly |
+| **Original**                 | **Transform To**                                         |
+| ---------------------------- | -------------------------------------------------------- |
+| Technical architecture first | Problem → Solution → Benefit                             |
+| Abstract concept             | Analogy → Plain explanation → Technical                  |
+| Steps without context        | Context → Prerequisites → Multi-path steps               |
+| Alphabetical reference       | Use-case groups → Two-tier descriptions                  |
+| Unexplained code             | What you'll build → Progressive steps → Explained blocks |
+| Feature list                 | Problem/solution pairs with benefits                     |
+| Jargon without definition    | Define inline or use plain alternative                   |
+| Missing "why"                | Add value proposition upfront                            |
+| No use cases                 | Add 3-5 realistic scenarios                              |
+| Assumes knowledge            | State prerequisites explicitly                           |
 
 ---
 
 ## Best Practices Summary
 
 ### Do:
+
 ✅ Lead with benefits and problems solved  
 ✅ Use tech-adjacent metaphors with stated limitations  
 ✅ Provide both Dashboard and API paths  
@@ -615,9 +662,10 @@ Think of it like [security analogy]:
 ✅ Explain every code block  
 ✅ State prerequisites before steps  
 ✅ Include verification/testing sections  
-✅ Add "For technical users" collapsible sections  
+✅ Add "For technical users" collapsible sections
 
 ### Don't:
+
 ❌ Start with technical architecture  
 ❌ Use condescending language ("simply," "just," "obviously")  
 ❌ Assume prior knowledge without stating it  
@@ -625,7 +673,7 @@ Think of it like [security analogy]:
 ❌ Organize specs alphabetically without context  
 ❌ Drop code without explanation  
 ❌ Skip the "why" to get to "how" faster  
-❌ Sacrifice accuracy for brevity  
+❌ Sacrifice accuracy for brevity
 
 ---
 
diff --git a/.github/review-template.md b/.github/review-template.md
index 0e56cc03451cac7..4aee0df6e1cf7ed 100644
--- a/.github/review-template.md
+++ b/.github/review-template.md
@@ -1,8 +1,9 @@
 ## Author self-review
 
 I've reviewed my PR for the following:
+
 - [ ] Metadata in the frontmatter, including `pcx_content_type` and - for tutorials - `updated: YYYY-MM-DD`.
 - [ ] PCX content strategy overall.
 - [ ] PCX style guidelines (product names, capitalization, etc.).
 - [ ] Needed redirects (if deleting any existing pages).
-- [ ] Code blocks && other formatting issues (bolding, italics, lists).
\ No newline at end of file
+- [ ] Code blocks && other formatting issues (bolding, italics, lists).
diff --git a/.opencode/command/styleguide.md b/.opencode/command/styleguide.md
index 085e070750f199c..fbacc3b8e40c886 100644
--- a/.opencode/command/styleguide.md
+++ b/.opencode/command/styleguide.md
@@ -49,6 +49,7 @@ Look at all the unstaged changes to markdown (.md, .mdx) files, pull out the lin
 ## Output Format
 
 For each issue found, report:
+
 - The problematic text (quote it)
 - Which rule it violates
 - A suggested fix
diff --git a/.windsurf/rules/general-rules.md b/.windsurf/rules/general-rules.md
index e563c09c965c3cf..7efe2f90487c8d4 100644
--- a/.windsurf/rules/general-rules.md
+++ b/.windsurf/rules/general-rules.md
@@ -61,4 +61,4 @@ This code would only be rendered if the page has a magicWord variable set to "ha
 - Replace `sh` blocks using `npm commands` with our [`PackageManagers` component](https://developers.cloudflare.com/style-guide/components/package-managers/).
 - Replace in-text mentions of Cloudflare's number of data centers, network capacity, or network peers with our [`PublicStats` component](https://developers.cloudflare.com/style-guide/components/public-stats/).
 - Replace `toml` or `json` code blocks with [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/#sample-wrangler-configuration) information with our [`WranglerConfig` component](https://developers.cloudflare.com/style-guide/components/wrangler-config/).
-- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
\ No newline at end of file
+- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7d3e71c75126c9f..198fa9cdc3bf951 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,9 +1,10 @@
 # Contributing to Cloudflare's developer documentation
 
 Everyone, including those who are not part of the Cloudflare organization, are encouraged to contribute.
+
 - If you are not a Cloudflare employee, learn how to contribute in the [contribution page](https://developers.cloudflare.com/style-guide/contributions/) of the Cloudflare Style Guide.
 - If you are a Cloudflare employee, reach out via our Developer Docs space in Google chat.
 
 Consult the [Cloudflare Style Guide](https://developers.cloudflare.com/style-guide/) on everything from grammar, to formatting, to frontmatter requirements. Browse our [components](/style-guide/components/) to add additional formatting.
 
-Thank you for helping us to maintain quality documentation.
\ No newline at end of file
+Thank you for helping us to maintain quality documentation.
diff --git a/MIGRATION.md b/MIGRATION.md
index 622c020aee16f4d..4ac50851fe0e52b 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -18,7 +18,7 @@
 ## High-risk items and unknowns
 
 | Item                                                  | Risk   | Status                                                        |
-|-------------------------------------------------------|--------|---------------------------------------------------------------|
+| ----------------------------------------------------- | ------ | ------------------------------------------------------------- |
 | **`Page.astro` Vite alias**                           | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`patch-package` hunks against Starlight internals** | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`starlight-links-validator` Zod 4 incompatibility** | HIGH   | Confirmed broken upstream                                     |
@@ -42,7 +42,7 @@ Targets are determined by [withastro/docs#13230].
 That is the north star.
 
 | Package                        | Current  | Target                                                 |
-| ------------------------------ | -------- |--------------------------------------------------------|
+| ------------------------------ | -------- | ------------------------------------------------------ |
 | `astro`                        | `5.13.7` | `6.0.0-beta.8`                                         |
 | `@astrojs/starlight`           | `0.36.0` | `https://pkg.pr.new/@astrojs/starlight@3644`           |
 | `@astrojs/starlight-docsearch` | `0.6.0`  | `https://pkg.pr.new/@astrojs/starlight-docsearch@3644` |
diff --git a/src/components/AutoconfigDiagram.astro b/src/components/AutoconfigDiagram.astro
index dafb15f5e6c8c24..bc843cdd921273a 100644
--- a/src/components/AutoconfigDiagram.astro
+++ b/src/components/AutoconfigDiagram.astro
@@ -21,10 +21,15 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon">
 						<slot name="icon">
-							<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								viewBox="0 0 24 24"
+								fill="none"
+								stroke="currentColor"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</slot>
 					</div>
@@ -43,15 +48,17 @@ const { framework, configs } = Astro.props;
 				<div class="config-box">
 					<span class="config-title">Generated configuration</span>
 					<div class="config-items">
-						{configs.map((config, i) => (
-							<div class="config-item" data-config-index={i}>
-								<div class="config-file">{config.file}</div>
-								<div class="config-detail">
-									<span class="config-label">{config.label}:</span>
-									<span class="config-value">{config.value}</span>
+						{
+							configs.map((config, i) => (
+								<div class="config-item" data-config-index={i}>
+									<div class="config-file">{config.file}</div>
+									<div class="config-detail">
+										<span class="config-label">{config.label}:</span>
+										<span class="config-value">{config.value}</span>
+									</div>
 								</div>
-							</div>
-						))}
+							))
+						}
 					</div>
 				</div>
 			</div>
@@ -64,8 +71,12 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon workers-icon">
 						<svg viewBox="0 0 24 24" fill="none">
-							<path d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z" fill="#F6821F"/>
-							<path d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z" fill="#FBAD41"/>
+							<path
+								d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z"
+								fill="#F6821F"></path>
+							<path
+								d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z"
+								fill="#FBAD41"></path>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -79,7 +90,9 @@ const { framework, configs } = Astro.props;
 		<!-- Status indicator -->
 		<div class="status-indicator">
 			<div class="status-dot"></div>
-			<span class="status-text">Wrangler handles configuration automatically</span>
+			<span class="status-text"
+				>Wrangler handles configuration automatically</span
+			>
 		</div>
 	</div>
 </autoconfig-diagram>
@@ -131,7 +144,9 @@ const { framework, configs } = Astro.props;
 		padding: 0.75rem 1rem;
 		border: 1px solid rgb(229 229 229);
 		min-width: 120px;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -323,7 +338,8 @@ const { framework, configs } = Astro.props;
 
 	.config-file {
 		font-size: 0.625rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		color: rgb(115 115 115);
 		margin-bottom: 0.125rem;
 	}
@@ -334,7 +350,8 @@ const { framework, configs } = Astro.props;
 
 	.config-detail {
 		font-size: 0.6875rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 	}
 
 	.config-label {
@@ -393,8 +410,13 @@ const { framework, configs } = Astro.props;
 	}
 
 	@keyframes pulse {
-		0%, 100% { opacity: 1; }
-		50% { opacity: 0.5; }
+		0%,
+		100% {
+			opacity: 1;
+		}
+		50% {
+			opacity: 0.5;
+		}
 	}
 
 	.status-text {
@@ -415,10 +437,10 @@ const { framework, configs } = Astro.props;
 <script>
 	class AutoconfigDiagram extends HTMLElement {
 		private isRunning = false;
-		private framework = '';
+		private framework = "";
 
 		connectedCallback() {
-			this.framework = this.dataset.framework || '';
+			this.framework = this.dataset.framework || "";
 			// Auto-start after a short delay
 			setTimeout(() => this.run(), 500);
 		}
@@ -427,87 +449,90 @@ const { framework, configs } = Astro.props;
 			if (this.isRunning) return;
 			this.isRunning = true;
 
-			const statusIndicator = this.querySelector('.status-indicator');
-			const statusText = this.querySelector('.status-text');
+			const statusIndicator = this.querySelector(".status-indicator");
+			const statusText = this.querySelector(".status-text");
 
 			// Reset state
 			this.resetState();
 
 			// Update status
-			statusIndicator?.classList.add('running');
-			if (statusText) statusText.textContent = `Detecting ${this.framework} project...`;
+			statusIndicator?.classList.add("running");
+			if (statusText)
+				statusText.textContent = `Detecting ${this.framework} project...`;
 
 			await this.delay(900);
 
 			// Step 1: Framework detected
-			const frameworkNode = this.querySelector('.framework-node');
-			frameworkNode?.classList.add('active');
+			const frameworkNode = this.querySelector(".framework-node");
+			frameworkNode?.classList.add("active");
 			if (statusText) statusText.textContent = `${this.framework} detected`;
 
 			await this.delay(1200);
 
 			// Step 2: First connector
-			const connectors = this.querySelectorAll('.connector');
-			connectors[0]?.classList.add('active');
+			const connectors = this.querySelectorAll(".connector");
+			connectors[0]?.classList.add("active");
 
 			await this.delay(600);
 
 			// Step 3: Config section
-			const configSection = this.querySelector('.config-section');
-			configSection?.classList.add('active');
-			if (statusText) statusText.textContent = 'Generating configuration...';
+			const configSection = this.querySelector(".config-section");
+			configSection?.classList.add("active");
+			if (statusText) statusText.textContent = "Generating configuration...";
 
 			await this.delay(600);
 
 			// Show config items one by one
-			const configItems = this.querySelectorAll('.config-item');
+			const configItems = this.querySelectorAll(".config-item");
 			for (let i = 0; i < configItems.length; i++) {
 				const item = configItems[i];
-				item.classList.add('visible', 'active');
-				
+				item.classList.add("visible", "active");
+
 				// Get the config value for status
-				const valueEl = item.querySelector('.config-value');
-				const labelEl = item.querySelector('.config-label');
+				const valueEl = item.querySelector(".config-value");
+				const labelEl = item.querySelector(".config-label");
 				if (valueEl && labelEl) {
-					const label = labelEl.textContent?.replace(':', '') || '';
-					const value = valueEl.textContent || '';
-					if (statusText) statusText.textContent = `Setting ${label} → ${value}`;
+					const label = labelEl.textContent?.replace(":", "") || "";
+					const value = valueEl.textContent || "";
+					if (statusText)
+						statusText.textContent = `Setting ${label} → ${value}`;
 				}
 
 				await this.delay(1400);
-				item.classList.remove('active');
+				item.classList.remove("active");
 			}
 
 			await this.delay(500);
 
 			// Step 4: Second connector
-			connectors[1]?.classList.add('active');
-			if (statusText) statusText.textContent = 'Deploying to Workers...';
+			connectors[1]?.classList.add("active");
+			if (statusText) statusText.textContent = "Deploying to Workers...";
 
 			await this.delay(900);
 
 			// Step 5: Workers node
-			const workersNode = this.querySelector('.workers-node');
-			workersNode?.classList.add('active');
+			const workersNode = this.querySelector(".workers-node");
+			workersNode?.classList.add("active");
 
 			await this.delay(600);
 
 			// Complete - keep orange theme
-			frameworkNode?.classList.remove('active');
-			frameworkNode?.classList.add('connected');
-			configSection?.classList.remove('active');
-			configSection?.classList.add('connected');
-			connectors.forEach(c => {
-				c.classList.remove('active');
-				c.classList.add('connected');
+			frameworkNode?.classList.remove("active");
+			frameworkNode?.classList.add("connected");
+			configSection?.classList.remove("active");
+			configSection?.classList.add("connected");
+			connectors.forEach((c) => {
+				c.classList.remove("active");
+				c.classList.add("connected");
 			});
-			configItems.forEach(item => item.classList.add('visible'));
-			workersNode?.classList.remove('active');
-			workersNode?.classList.add('connected');
+			configItems.forEach((item) => item.classList.add("visible"));
+			workersNode?.classList.remove("active");
+			workersNode?.classList.add("connected");
 
-			statusIndicator?.classList.remove('running');
-			statusIndicator?.classList.add('complete');
-			if (statusText) statusText.textContent = 'Deployed to Cloudflare Workers!';
+			statusIndicator?.classList.remove("running");
+			statusIndicator?.classList.add("complete");
+			if (statusText)
+				statusText.textContent = "Deployed to Cloudflare Workers!";
 
 			this.isRunning = false;
 
@@ -518,18 +543,18 @@ const { framework, configs } = Astro.props;
 
 		private resetState() {
 			// Remove all state classes
-			this.querySelectorAll('.active, .connected, .visible').forEach(el => {
-				el.classList.remove('active', 'connected', 'visible');
+			this.querySelectorAll(".active, .connected, .visible").forEach((el) => {
+				el.classList.remove("active", "connected", "visible");
 			});
-			
-			const statusIndicator = this.querySelector('.status-indicator');
-			statusIndicator?.classList.remove('running', 'complete');
+
+			const statusIndicator = this.querySelector(".status-indicator");
+			statusIndicator?.classList.remove("running", "complete");
 		}
 
 		private delay(ms: number): Promise<void> {
-			return new Promise(resolve => setTimeout(resolve, ms));
+			return new Promise((resolve) => setTimeout(resolve, ms));
 		}
 	}
 
-	customElements.define('autoconfig-diagram', AutoconfigDiagram);
+	customElements.define("autoconfig-diagram", AutoconfigDiagram);
 </script>
diff --git a/src/components/ComponentUsage.astro b/src/components/ComponentUsage.astro
index 4a3bf2d7677a098..66ee88e6d14b810 100644
--- a/src/components/ComponentUsage.astro
+++ b/src/components/ComponentUsage.astro
@@ -18,7 +18,8 @@ const usage = await getComponentsUsage(component);
 
 <>
 	<p>
-		The <code>{component}</code> component is used <code>{usage.count}</code> times on{" "}
+		The <code>{component}</code> component is used <code>{usage.count}</code> times
+		on{" "}
 		<code>{usage.pages.size}</code> pages.
 	</p>
 	<Details header={`See all examples of pages that use ${component}`}>
diff --git a/src/components/FeatureTable.astro b/src/components/FeatureTable.astro
index 8af0f2ee817b163..e9dd6c485730d49 100644
--- a/src/components/FeatureTable.astro
+++ b/src/components/FeatureTable.astro
@@ -34,12 +34,44 @@ const markdown = (content: any) => {
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"></th>
-			{hasFree && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Free</th>}
-			{hasPro && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Pro</th>}
-			{hasBiz && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Business</th>}
-			{hasEnt && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Enterprise</th>}
-			{hasEntPlus && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">{plan.ent_plus}</th>}
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+			></th>
+			{
+				hasFree && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Free
+					</th>
+				)
+			}
+			{
+				hasPro && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Pro
+					</th>
+				)
+			}
+			{
+				hasBiz && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Business
+					</th>
+				)
+			}
+			{
+				hasEnt && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Enterprise
+					</th>
+				)
+			}
+			{
+				hasEntPlus && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						{plan.ent_plus}
+					</th>
+				)
+			}
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/LayerCard.astro b/src/components/LayerCard.astro
index f809ad95620577b..52528db54e544c5 100644
--- a/src/components/LayerCard.astro
+++ b/src/components/LayerCard.astro
@@ -8,17 +8,17 @@ const { header = "Next Steps", href } = Astro.props;
 ---
 
 <div
-	class="flex w-full flex-col overflow-hidden rounded-lg bg-cl1-gray-9 text-base ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1"
+	class="bg-cl1-gray-9 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1 flex w-full flex-col overflow-hidden rounded-lg text-base ring-1"
 >
 	<div
-		class="-my-2 flex items-center justify-between gap-2 bg-cl1-gray-9 p-4 text-base font-medium text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7"
+		class="bg-cl1-gray-9 text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7 -my-2 flex items-center justify-between gap-2 p-4 text-base font-medium"
 	>
 		<div>{header}</div>
 		{
 			href && (
 				<a
 					href={href}
-					class="flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent text-cl1-gray-0 no-underline hover:bg-cl1-gray-8 focus-visible:outline focus-visible:outline-1 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3"
+					class="text-cl1-gray-0 hover:bg-cl1-gray-8 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3 flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent no-underline focus-visible:outline focus-visible:outline-1"
 					aria-label={`Go to ${header.toLowerCase()}`}
 				>
 					<svg
@@ -35,7 +35,7 @@ const { header = "Next Steps", href } = Astro.props;
 		}
 	</div>
 	<div
-		class="relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg bg-cl1-white p-4 pr-3 ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2"
+		class="bg-cl1-white ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2 relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg p-4 pr-3 ring-1"
 	>
 		<slot />
 	</div>
diff --git a/src/components/LlmsTxtDirective.astro b/src/components/LlmsTxtDirective.astro
index f9ea644e578be8b..87d72771289a198 100644
--- a/src/components/LlmsTxtDirective.astro
+++ b/src/components/LlmsTxtDirective.astro
@@ -11,9 +11,9 @@ const llmsTxt = productPrefix
 ---
 
 <blockquote class="llms-txt-directive" aria-hidden="true">
-Documentation Index<br/>
-Fetch the complete documentation index at: {llmsTxt}<br/>
-Use this file to discover all available pages before exploring further.
+	Documentation Index<br />
+	Fetch the complete documentation index at: {llmsTxt}<br />
+	Use this file to discover all available pages before exploring further.
 </blockquote>
 
 <style>
diff --git a/src/components/PagesBuildPresetsTable.astro b/src/components/PagesBuildPresetsTable.astro
index 93b77d7c42a275a..6383eeb9e7e6adc 100644
--- a/src/components/PagesBuildPresetsTable.astro
+++ b/src/components/PagesBuildPresetsTable.astro
@@ -14,9 +14,18 @@ const entries = Object.values(presets);
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Framework/tool</th>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build command</th>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build directory</th>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Framework/tool</th
+			>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Build command</th
+			>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Build directory</th
+			>
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/ProductReleaseNotes.astro b/src/components/ProductReleaseNotes.astro
index df5a3cc1ee2cd47..5cf7314aeee4f17 100644
--- a/src/components/ProductReleaseNotes.astro
+++ b/src/components/ProductReleaseNotes.astro
@@ -15,9 +15,7 @@ if (!page) {
 	);
 }
 
-if (
-	!page.data.release_notes_file_name
-) {
+if (!page.data.release_notes_file_name) {
 	throw new Error(
 		`[ProductReleaseNotes] ${Astro.params.slug} does not have a 'release_notes_file_name' frontmatter property.`,
 	);
@@ -32,8 +30,7 @@ if (
 	);
 }
 
-const name =
-	page.data.release_notes_file_name?.[0];
+const name = page.data.release_notes_file_name?.[0];
 
 let releaseNotes;
 
diff --git a/src/components/R2LocalUploadsdiagram.astro b/src/components/R2LocalUploadsdiagram.astro
index 6d717c9406d70af..067f6f1892e41e6 100644
--- a/src/components/R2LocalUploadsdiagram.astro
+++ b/src/components/R2LocalUploadsdiagram.astro
@@ -1,32 +1,49 @@
 ---
 interface Props {
-	mode?: 'without' | 'with' | 'comparison';
+	mode?: "without" | "with" | "comparison";
 	autoPlay?: boolean;
 	loop?: boolean;
 }
 
-const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
+const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 ---
 
-<r2-local-uploads-diagram data-mode={mode} data-autoplay={autoPlay} data-loop={loop}>
+<r2-local-uploads-diagram
+	data-mode={mode}
+	data-autoplay={autoPlay}
+	data-loop={loop}
+>
 	<div class="diagram-wrapper">
-		{mode === 'comparison' && (
-			<div class="toggle-container">
-				<span class="toggle-label" id="local-uploads-label">Local uploads</span>
-				<label class="toggle-switch" aria-labelledby="local-uploads-label">
-					<input type="checkbox" class="toggle-input" aria-labelledby="local-uploads-label" />
-					<span class="toggle-slider"></span>
-				</label>
-			</div>
-		)}
+		{
+			mode === "comparison" && (
+				<div class="toggle-container">
+					<span class="toggle-label" id="local-uploads-label">
+						Local uploads
+					</span>
+					<label class="toggle-switch" aria-labelledby="local-uploads-label">
+						<input
+							type="checkbox"
+							class="toggle-input"
+							aria-labelledby="local-uploads-label"
+						/>
+						<span class="toggle-slider" />
+					</label>
+				</div>
+			)
+		}
 		<div class="diagram-container">
 			<!-- Client node -->
 			<div class="flow-node" data-step="1">
 				<div class="node-card">
 					<div class="node-badge">
-						<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-							<rect x="3" y="4" width="18" height="12" rx="2"/>
-							<path d="M7 20h10M12 16v4"/>
+						<svg
+							fill="none"
+							stroke="currentColor"
+							viewBox="0 0 24 24"
+							stroke-width="2"
+						>
+							<rect x="3" y="4" width="18" height="12" rx="2"></rect>
+							<path d="M7 20h10M12 16v4"></path>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -46,10 +63,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				<div class="group-content edge-single">
 					<div class="bucket-component gateway-node-without">
 						<div class="component-icon gateway">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -61,21 +83,74 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			<div class="split-area without-local-uploads" data-connector="2-bucket">
 				<svg class="split-svg" viewBox="0 0 320 100" preserveAspectRatio="none">
 					<!-- Stem from node above -->
-					<line class="split-line stem data-path" x1="160" y1="0" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line stem data-path"
+						x1="160"
+						y1="0"
+						x2="160"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Horizontal bar - left half (metadata) -->
-					<line class="split-line horizontal-left metadata-path" x1="85" y1="20" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line horizontal-left metadata-path"
+						x1="85"
+						y1="20"
+						x2="160"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Horizontal bar - right half (object data) -->
-					<line class="split-line horizontal-right data-path" x1="160" y1="20" x2="235" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line horizontal-right data-path"
+						x1="160"
+						y1="20"
+						x2="235"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Left branch (metadata) -->
-					<line class="split-line left-branch-top metadata-path" x1="85" y1="20" x2="85" y2="50" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line left-branch-top metadata-path"
+						x1="85"
+						y1="20"
+						x2="85"
+						y2="50"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Right branch (object data) -->
-					<line class="split-line right-branch-top data-path" x1="235" y1="20" x2="235" y2="50" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line right-branch-top data-path"
+						x1="235"
+						y1="20"
+						x2="235"
+						y2="50"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Labels positioned on the lines -->
-					<text x="85" y="67" text-anchor="middle" class="svg-label">Object metadata</text>
-					<text x="235" y="67" text-anchor="middle" class="svg-label">Object data</text>
+					<text x="85" y="67" text-anchor="middle" class="svg-label"
+						>Object metadata</text
+					>
+					<text x="235" y="67" text-anchor="middle" class="svg-label"
+						>Object data</text
+					>
 					<!-- Continue lines to bucket -->
-					<line class="split-line left-branch-bottom metadata-path" x1="85" y1="72" x2="85" y2="100" stroke="currentColor" stroke-width="2"/>
-					<line class="split-line right-branch-bottom data-path" x1="235" y1="72" x2="235" y2="100" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line left-branch-bottom metadata-path"
+						x1="85"
+						y1="72"
+						x2="85"
+						y2="100"
+						stroke="currentColor"
+						stroke-width="2"></line>
+					<line
+						class="split-line right-branch-bottom data-path"
+						x1="235"
+						y1="72"
+						x2="235"
+						y2="100"
+						stroke="currentColor"
+						stroke-width="2"></line>
 				</svg>
 			</div>
 
@@ -87,10 +162,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<!-- R2 Gateway Worker -->
 					<div class="bucket-component gateway-node-local">
 						<div class="component-icon gateway">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -100,10 +180,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<!-- Local Object Data Infra -->
 					<div class="bucket-component local-storage-node">
 						<div class="component-icon storage">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<ellipse cx="12" cy="6" rx="8" ry="3"/>
-								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
-								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
+								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
+								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
 							</svg>
 						</div>
 						<span class="component-name">Object Data Infra</span>
@@ -112,7 +197,10 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			</div>
 
 			<!-- WITH local uploads: Two lines down to bucket -->
-			<div class="local-split-columns with-local-uploads hidden" data-connector="local-split">
+			<div
+				class="local-split-columns with-local-uploads hidden"
+				data-connector="local-split"
+			>
 				<div class="split-col left-col">
 					<div class="v-connector meta-line"></div>
 					<div class="split-label-row">
@@ -124,8 +212,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<div class="v-connector replication-line"></div>
 					<div class="split-label-row">
 						<svg class="progress-ring" viewBox="0 0 20 20">
-							<circle class="progress-ring-bg" cx="10" cy="10" r="8" />
-							<circle class="progress-ring-fill" cx="10" cy="10" r="8" />
+							<circle class="progress-ring-bg" cx="10" cy="10" r="8"></circle>
+							<circle class="progress-ring-fill" cx="10" cy="10" r="8"></circle>
 						</svg>
 						<span class="split-col-label replication">Object data</span>
 					</div>
@@ -141,19 +229,31 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<div class="group-content">
 						<div class="bucket-component" data-component="metadata">
 							<div class="component-icon">
-								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-									<circle cx="12" cy="12" r="10"/>
-									<path d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"/>
+								<svg
+									fill="none"
+									stroke="currentColor"
+									viewBox="0 0 24 24"
+									stroke-width="2"
+								>
+									<circle cx="12" cy="12" r="10"></circle>
+									<path
+										d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"
+									></path>
 								</svg>
 							</div>
 							<span class="component-name">Metadata Service</span>
 						</div>
 						<div class="bucket-component" data-component="object-data">
 							<div class="component-icon">
-								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-									<ellipse cx="12" cy="6" rx="8" ry="3"/>
-									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
-									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
+								<svg
+									fill="none"
+									stroke="currentColor"
+									viewBox="0 0 24 24"
+									stroke-width="2"
+								>
+									<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
+									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
+									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
 								</svg>
 							</div>
 							<span class="component-name">Object Data Infra</span>
@@ -164,9 +264,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		</div>
 		<!-- Status indicator -->
 		<div class="status-indicator">
-			<svg class="status-check" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.5">
-				<circle cx="12" cy="12" r="10" class="status-circle" />
-				<path d="M8 12l3 3 5-5" class="status-checkmark" />
+			<svg
+				class="status-check"
+				viewBox="0 0 24 24"
+				fill="none"
+				stroke="currentColor"
+				stroke-width="2.5"
+			>
+				<circle cx="12" cy="12" r="10" class="status-circle"></circle>
+				<path d="M8 12l3 3 5-5" class="status-checkmark"></path>
 			</svg>
 			<span class="status-text">Data is uploaded and accessible</span>
 		</div>
@@ -270,8 +376,6 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		width: 100%;
 	}
 
-
-
 	/* Vertical connector line between nodes */
 	.connector {
 		width: 2px;
@@ -303,7 +407,9 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		border: 1px solid rgb(229 229 229);
 		width: 220px;
 		margin: 0 !important;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -366,7 +472,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 
 	.node-name {
 		font-size: 0.8125rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 	}
@@ -535,7 +642,9 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		padding: 0.5rem;
 		margin: 0 !important;
 		box-sizing: border-box;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .bucket-component {
@@ -571,7 +680,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 
 	.component-name {
 		font-size: 0.625rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 		text-align: center;
@@ -654,8 +764,6 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		color: rgb(249 115 22);
 	}
 
-
-
 	/* Note text under component name */
 	.component-note {
 		font-size: 0.5rem;
@@ -883,42 +991,50 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		private playTimeout: number | null = null;
 
 		connectedCallback() {
-			this.loop = this.dataset.loop === 'true';
-			
-			const toggleInput = this.querySelector('.toggle-input') as HTMLInputElement;
+			this.loop = this.dataset.loop === "true";
+
+			const toggleInput = this.querySelector(
+				".toggle-input",
+			) as HTMLInputElement;
 			if (toggleInput) {
-				toggleInput.addEventListener('change', () => {
+				toggleInput.addEventListener("change", () => {
 					this.localUploadsEnabled = toggleInput.checked;
-					this.setMode(toggleInput.checked ? 'with' : 'without');
+					this.setMode(toggleInput.checked ? "with" : "without");
 					this.resetAnimation();
-					if (this.dataset.autoplay === 'true') {
-						this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
+					if (this.dataset.autoplay === "true") {
+						this.playTimeout = setTimeout(
+							() => this.play(),
+							500,
+						) as unknown as number;
 					}
 				});
 			}
 
-			if (this.dataset.autoplay === 'true') {
-				this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
+			if (this.dataset.autoplay === "true") {
+				this.playTimeout = setTimeout(
+					() => this.play(),
+					500,
+				) as unknown as number;
 			}
 		}
 
-		private setMode(mode: 'without' | 'with') {
-			const withoutElements = this.querySelectorAll('.without-local-uploads');
-			const withElements = this.querySelectorAll('.with-local-uploads');
+		private setMode(mode: "without" | "with") {
+			const withoutElements = this.querySelectorAll(".without-local-uploads");
+			const withElements = this.querySelectorAll(".with-local-uploads");
 
-			if (mode === 'without') {
-				withoutElements.forEach(el => el.classList.remove('hidden'));
-				withElements.forEach(el => el.classList.add('hidden'));
+			if (mode === "without") {
+				withoutElements.forEach((el) => el.classList.remove("hidden"));
+				withElements.forEach((el) => el.classList.add("hidden"));
 			} else {
-				withoutElements.forEach(el => el.classList.add('hidden'));
-				withElements.forEach(el => el.classList.remove('hidden'));
+				withoutElements.forEach((el) => el.classList.add("hidden"));
+				withElements.forEach((el) => el.classList.remove("hidden"));
 			}
 		}
 
 		private resetAnimation() {
 			this.currentStep = 0;
 			this.isPlaying = false;
-			
+
 			// Clear any pending timeouts
 			if (this.stepTimeout !== null) {
 				clearTimeout(this.stepTimeout);
@@ -928,12 +1044,20 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				clearTimeout(this.playTimeout);
 				this.playTimeout = null;
 			}
-			
+
 			// Remove all active and animating states
-			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
-			this.querySelectorAll('.animating').forEach(el => el.classList.remove('animating'));
-			this.querySelectorAll('.data-animating').forEach(el => el.classList.remove('data-animating'));
-			this.querySelectorAll('.metadata-active').forEach(el => el.classList.remove('metadata-active'));
+			this.querySelectorAll(".active").forEach((el) =>
+				el.classList.remove("active"),
+			);
+			this.querySelectorAll(".animating").forEach((el) =>
+				el.classList.remove("animating"),
+			);
+			this.querySelectorAll(".data-animating").forEach((el) =>
+				el.classList.remove("data-animating"),
+			);
+			this.querySelectorAll(".metadata-active").forEach((el) =>
+				el.classList.remove("metadata-active"),
+			);
 		}
 
 		private play() {
@@ -953,7 +1077,10 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				if (this.loop) {
 					// Reset and restart
 					this.resetAnimation();
-					this.playTimeout = setTimeout(() => this.play(), 1000) as unknown as number;
+					this.playTimeout = setTimeout(
+						() => this.play(),
+						1000,
+					) as unknown as number;
 				} else {
 					this.isPlaying = false;
 				}
@@ -961,7 +1088,7 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			}
 
 			this.updateDiagram();
-			
+
 			// Duration for each step
 			let duration = 1200;
 			if (!this.localUploadsEnabled && this.currentStep === 4) {
@@ -973,12 +1100,17 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			} else if (this.localUploadsEnabled && this.currentStep === 9) {
 				duration = 2500; // Linger on final step with status indicator
 			}
-			this.stepTimeout = setTimeout(() => this.advanceStep(), duration) as unknown as number;
+			this.stepTimeout = setTimeout(
+				() => this.advanceStep(),
+				duration,
+			) as unknown as number;
 		}
 
 		private updateDiagram() {
 			// Remove all active states first
-			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
+			this.querySelectorAll(".active").forEach((el) =>
+				el.classList.remove("active"),
+			);
 
 			if (this.localUploadsEnabled) {
 				this.updateWithLocalUploads();
@@ -991,49 +1123,53 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client node lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add('active');
+				clientNode?.classList.add("active");
 			}
 
 			// Step 2: Connector from client to EDGE lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add('active');
+				connector1?.classList.add("active");
 			}
 
 			// Step 3: EDGE box border + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector('.region-box.without-local-uploads');
-				const gatewayNode = this.querySelector('.gateway-node-without');
-				edgeBox?.classList.add('active');
-				gatewayNode?.classList.add('active');
+				const edgeBox = this.querySelector(".region-box.without-local-uploads");
+				const gatewayNode = this.querySelector(".gateway-node-without");
+				edgeBox?.classList.add("active");
+				gatewayNode?.classList.add("active");
 			}
 
 			// Step 4: Object data line starts animating
 			if (this.currentStep >= 4) {
-				const splitArea = this.querySelector('.split-area');
-				splitArea?.classList.add('data-animating');
+				const splitArea = this.querySelector(".split-area");
+				splitArea?.classList.add("data-animating");
 			}
 
 			// Step 5: Object Data Infra lights up
 			if (this.currentStep >= 5) {
-				const objectDataComponent = this.querySelector('[data-component="object-data"]');
-				objectDataComponent?.classList.add('active');
+				const objectDataComponent = this.querySelector(
+					'[data-component="object-data"]',
+				);
+				objectDataComponent?.classList.add("active");
 			}
 
 			// Step 6: Object metadata line lights up
 			if (this.currentStep >= 6) {
-				const splitArea = this.querySelector('.split-area');
-				splitArea?.classList.add('metadata-active');
+				const splitArea = this.querySelector(".split-area");
+				splitArea?.classList.add("metadata-active");
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector('.bucket-group');
-				const metadataComponent = this.querySelector('[data-component="metadata"]');
-				const statusIndicator = this.querySelector('.status-indicator');
-				bucketGroup?.classList.add('active');
-				metadataComponent?.classList.add('active');
-				statusIndicator?.classList.add('active');
+				const bucketGroup = this.querySelector(".bucket-group");
+				const metadataComponent = this.querySelector(
+					'[data-component="metadata"]',
+				);
+				const statusIndicator = this.querySelector(".status-indicator");
+				bucketGroup?.classList.add("active");
+				metadataComponent?.classList.add("active");
+				statusIndicator?.classList.add("active");
 			}
 		}
 
@@ -1041,75 +1177,83 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add('active');
+				clientNode?.classList.add("active");
 			}
 
 			// Step 2: Connector (client -> edge) lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add('active');
+				connector1?.classList.add("active");
 			}
 
 			// Step 3: EDGE box + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector('.region-box.with-local-uploads');
-				const gatewayNode = this.querySelector('.gateway-node-local');
-				edgeBox?.classList.add('active');
-				gatewayNode?.classList.add('active');
+				const edgeBox = this.querySelector(".region-box.with-local-uploads");
+				const gatewayNode = this.querySelector(".gateway-node-local");
+				edgeBox?.classList.add("active");
+				gatewayNode?.classList.add("active");
 			}
 
 			// Step 4: Line from Gateway to Object Data Infra (edge)
 			if (this.currentStep >= 4) {
-				const regionLine = this.querySelector('.region-line');
-				regionLine?.classList.add('active');
+				const regionLine = this.querySelector(".region-line");
+				regionLine?.classList.add("active");
 			}
 
 			// Step 5: Object Data Infra (edge) lights up
 			if (this.currentStep >= 5) {
-				const localStorageNode = this.querySelector('.local-storage-node');
-				localStorageNode?.classList.add('active');
+				const localStorageNode = this.querySelector(".local-storage-node");
+				localStorageNode?.classList.add("active");
 			}
 
 			// Step 6: Line from Gateway to Metadata Service
 			if (this.currentStep >= 6) {
-				const metadataLines = this.querySelectorAll('.left-col .v-connector.meta-line');
-				metadataLines.forEach(el => el.classList.add('active'));
+				const metadataLines = this.querySelectorAll(
+					".left-col .v-connector.meta-line",
+				);
+				metadataLines.forEach((el) => el.classList.add("active"));
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator lights up
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector('.bucket-group');
-				const metadataComponent = this.querySelector('[data-component="metadata"]');
-				const statusIndicator = this.querySelector('.status-indicator');
-				bucketGroup?.classList.add('active');
-				metadataComponent?.classList.add('active');
-				statusIndicator?.classList.add('active');
+				const bucketGroup = this.querySelector(".bucket-group");
+				const metadataComponent = this.querySelector(
+					'[data-component="metadata"]',
+				);
+				const statusIndicator = this.querySelector(".status-indicator");
+				bucketGroup?.classList.add("active");
+				metadataComponent?.classList.add("active");
+				statusIndicator?.classList.add("active");
 			}
 
 			// Step 8: Purple replication line animates downward + progress ring fills
 			if (this.currentStep >= 8) {
-				const replicationLines = this.querySelectorAll('.right-col .v-connector.replication-line');
-				const progressRing = this.querySelector('.progress-ring');
+				const replicationLines = this.querySelectorAll(
+					".right-col .v-connector.replication-line",
+				);
+				const progressRing = this.querySelector(".progress-ring");
 				// Force animation restart by removing class, triggering reflow, then adding class
-				replicationLines.forEach(el => {
-					el.classList.remove('animating');
+				replicationLines.forEach((el) => {
+					el.classList.remove("animating");
 					void (el as HTMLElement).offsetWidth; // Trigger reflow
-					el.classList.add('animating');
+					el.classList.add("animating");
 				});
 				if (progressRing) {
-					progressRing.classList.remove('animating');
+					progressRing.classList.remove("animating");
 					void (progressRing as HTMLElement).offsetWidth; // Trigger reflow
-					progressRing.classList.add('animating');
+					progressRing.classList.add("animating");
 				}
 			}
 
 			// Step 9: Object Data Infra (bucket) lights up
 			if (this.currentStep >= 9) {
-				const objectDataComponent = this.querySelector('[data-component="object-data"]');
-				objectDataComponent?.classList.add('active');
+				const objectDataComponent = this.querySelector(
+					'[data-component="object-data"]',
+				);
+				objectDataComponent?.classList.add("active");
 			}
 		}
 	}
 
-	customElements.define('r2-local-uploads-diagram', R2LocalUploadsDiagram);
+	customElements.define("r2-local-uploads-diagram", R2LocalUploadsDiagram);
 </script>
diff --git a/src/components/WranglerCommand.astro b/src/components/WranglerCommand.astro
index 560f0f0a3b9fc1d..9effdfbbbc05806 100644
--- a/src/components/WranglerCommand.astro
+++ b/src/components/WranglerCommand.astro
@@ -29,7 +29,7 @@ const experimental = definition.metadata.status === "experimental";
 // CED-191 some commands are present but marked as "hidden" and shouldn't be shown
 if (definition.metadata.hidden) {
 	throw new Error(
-		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`
+		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`,
 	);
 }
 
diff --git a/src/components/WranglerConfig.astro b/src/components/WranglerConfig.astro
index cf7cdd0bca5b008..6635f78fddc1700 100644
--- a/src/components/WranglerConfig.astro
+++ b/src/components/WranglerConfig.astro
@@ -19,7 +19,7 @@ const copy = html.querySelector("div.copy > button");
 
 if (!copy) {
 	throw new Error(
-		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`
+		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`,
 	);
 }
 
@@ -27,7 +27,7 @@ let code = copy.attributes["data-code"];
 
 if (!code) {
 	throw new Error(
-		`[WranglerConfig] Unable to find data-code attribute on copy button.`
+		`[WranglerConfig] Unable to find data-code attribute on copy button.`,
 	);
 }
 
diff --git a/src/components/WranglerNamespace.astro b/src/components/WranglerNamespace.astro
index 26f4136c098904f..52fc4b766b79934 100644
--- a/src/components/WranglerNamespace.astro
+++ b/src/components/WranglerNamespace.astro
@@ -41,7 +41,7 @@ flattenSubtree(node.subtree);
 	definitions.map((definition) => {
 		if (definition.type !== "command") {
 			throw new Error(
-				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`
+				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`,
 			);
 		}
 		return (
diff --git a/src/components/agent-setup/AgentComparison.astro b/src/components/agent-setup/AgentComparison.astro
index 5d6382aa20f657f..58cd4d4ce361218 100644
--- a/src/components/agent-setup/AgentComparison.astro
+++ b/src/components/agent-setup/AgentComparison.astro
@@ -122,7 +122,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.pricing_model ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.pricing_model.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.pricing_model] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.pricing_model] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.pricing_model as keyof typeof capabilityLabels
@@ -136,7 +138,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.model_flexibility ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.model_flexibility.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.model_flexibility] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.model_flexibility] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.model_flexibility as keyof typeof capabilityLabels
@@ -150,7 +154,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.context_approach ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.context_approach.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.context_approach] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.context_approach] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.context_approach as keyof typeof capabilityLabels
diff --git a/src/components/agent-setup/AgentHeader.astro b/src/components/agent-setup/AgentHeader.astro
index 65d087ccb59bd27..71bf483f8e9d0e3 100644
--- a/src/components/agent-setup/AgentHeader.astro
+++ b/src/components/agent-setup/AgentHeader.astro
@@ -20,9 +20,7 @@ const { slug } = Astro.props;
 const agent = AGENTS.find((a) => a.slug === slug);
 
 if (!agent) {
-	throw new Error(
-		`[AgentHeader] No agent found for slug="${slug}"`,
-	);
+	throw new Error(`[AgentHeader] No agent found for slug="${slug}"`);
 }
 
 const externalLinks = [
diff --git a/src/components/agent-setup/AgentPrimer.astro b/src/components/agent-setup/AgentPrimer.astro
index 35186f18fb15f25..ebcdc78adfe7adf 100644
--- a/src/components/agent-setup/AgentPrimer.astro
+++ b/src/components/agent-setup/AgentPrimer.astro
@@ -179,8 +179,10 @@
 				</div>
 				<p>
 					Which foundation models you can use. <strong>Locked</strong>
-					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your Own Key) lets you bring
-					your own API key. <strong>Multi-provider</strong>
+					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your
+					Own Key) lets you bring your own API key. <strong
+						>Multi-provider</strong
+					>
 					supports several providers out of the box.
 				</p>
 			</div>
diff --git a/src/components/agent-setup/BuildAgentsCallout.astro b/src/components/agent-setup/BuildAgentsCallout.astro
index 94869f042602215..6b69a6fa5d1d523 100644
--- a/src/components/agent-setup/BuildAgentsCallout.astro
+++ b/src/components/agent-setup/BuildAgentsCallout.astro
@@ -8,8 +8,8 @@
 	<div class="agent-build-callout-header">
 		<span class="agent-build-callout-eyebrow">Also worth knowing</span>
 		<p class="agent-build-callout-lede">
-			Cloudflare is not just a deploy target for agents, it is a full
-			stack for building your own.
+			Cloudflare is not just a deploy target for agents, it is a full stack for
+			building your own.
 		</p>
 	</div>
 
diff --git a/src/components/agent-setup/CloudflareToolsBanner.astro b/src/components/agent-setup/CloudflareToolsBanner.astro
index 5ed10cc064b9b55..0545d11317e00e4 100644
--- a/src/components/agent-setup/CloudflareToolsBanner.astro
+++ b/src/components/agent-setup/CloudflareToolsBanner.astro
@@ -5,27 +5,48 @@
 
 <div class="cf-banner not-content">
 	<div class="cf-banner-items">
-
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">Skills</p>
-			<p class="cf-banner-item-desc">Reusable prompt packages that teach agents about Cloudflare products and APIs.</p>
+			<p class="cf-banner-item-desc">
+				Reusable prompt packages that teach agents about Cloudflare products and
+				APIs.
+			</p>
 			<div class="cf-banner-item-links">
-				<a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">cloudflare/skills &nearr;</a>
+				<a
+					href="https://github.com/cloudflare/skills"
+					target="_blank"
+					rel="noopener noreferrer">cloudflare/skills &nearr;</a
+				>
 			</div>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">MCP</p>
-			<p class="cf-banner-item-desc">Connect agents to your Cloudflare account. Two flavors: <a href="https://github.com/cloudflare/mcp" target="_blank" rel="noopener noreferrer">Code Mode &nearr;</a> for broad API coverage across all products, or <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific servers &nearr;</a> for purpose-built tools within one product area.</p>
+			<p class="cf-banner-item-desc">
+				Connect agents to your Cloudflare account. Two flavors: <a
+					href="https://github.com/cloudflare/mcp"
+					target="_blank"
+					rel="noopener noreferrer">Code Mode &nearr;</a
+				> for broad API coverage across all products, or <a
+					href="https://github.com/cloudflare/mcp-server-cloudflare"
+					target="_blank"
+					rel="noopener noreferrer">domain-specific servers &nearr;</a
+				> for purpose-built tools within one product area.
+			</p>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">CLI</p>
 			<p class="cf-banner-item-desc">
-				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers, KV, D1, R2, and more.
-				<a href="https://blog.cloudflare.com/cf-cli-local-explorer/" target="_blank" rel="noopener noreferrer">cf CLI &nearr;</a> is a next-generation CLI covering every Cloudflare product — in technical preview.
+				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers,
+				KV, D1, R2, and more.
+				<a
+					href="https://blog.cloudflare.com/cf-cli-local-explorer/"
+					target="_blank"
+					rel="noopener noreferrer">cf CLI &nearr;</a
+				> is a next-generation CLI covering every Cloudflare product — in technical
+				preview.
 			</p>
 		</div>
-
 	</div>
 </div>
diff --git a/src/components/agent-setup/PlatformAccessSection.astro b/src/components/agent-setup/PlatformAccessSection.astro
index ca1c8625b1bbfae..a913296e1aae07b 100644
--- a/src/components/agent-setup/PlatformAccessSection.astro
+++ b/src/components/agent-setup/PlatformAccessSection.astro
@@ -32,9 +32,10 @@ import SkillsList from "./SkillsList.astro";
 		</p>
 		<p>
 			MCP servers provide typed tools to call into Cloudflare at runtime. There
-			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/">Code Mode</a> —
-			a single server that covers the entire Cloudflare API (2,500+ endpoints in
-			~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
+			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/"
+				>Code Mode</a
+			> — a single server that covers the entire Cloudflare API (2,500+ endpoints
+			in ~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
 				" "
 			}
 			<a
diff --git a/src/components/ai-gateway/code-examples.astro b/src/components/ai-gateway/code-examples.astro
index 5d48bb635cfa819..91687d405b07449 100644
--- a/src/components/ai-gateway/code-examples.astro
+++ b/src/components/ai-gateway/code-examples.astro
@@ -1,112 +1,245 @@
 ---
-import { CodeExample, CodeSelector, modelOptions, code, aiSDKUnifiedCode, aiSDKNativeCode, curlCode } from "./code-example-selector";
+import {
+	CodeExample,
+	CodeSelector,
+	modelOptions,
+	code,
+	aiSDKUnifiedCode,
+	aiSDKNativeCode,
+	curlCode,
+} from "./code-example-selector";
 import { Code } from "~/components";
 import { z } from "astro/zod";
 
-
 const props = z.object({
 	forceClient: z.string().optional(),
-    forceAPI: z.string().optional(),
+	forceAPI: z.string().optional(),
 });
 
 const { forceClient, forceAPI } = props.parse(Astro.props);
 ---
+
 <style>
-    .aig-code-example-container {
-        background-color: var(--color-gray-200);
-        border-color: var(--color-neutral-300);
-        border-radius: 0.675rem;
-        border-bottom-left-radius: 0.85rem;
-        border-bottom-right-radius: 0.85rem;
-        --selector-bg-color: var(--color-white);
-        --selector-border-color: var(--color-neutral-300);
-        --selector-text-color: var(--color-gray-900);
-        --ec-brdRad: 0.675rem;
-        --ec-brdCol: var(--color-neutral-300);
-        &:where([data-theme=dark], [data-theme=dark] *) {
-            background-color: var(--color-neutral-900);
-            border-color: var(--color-neutral-700);
-            --selector-bg-color: var(--color-neutral-700);
-            --selector-border-color: var(--color-neutral-800);
-            --selector-text-color: var(--color-gray-100);
-            --ec-brdCol: var(--color-neutral-700);
-        }
-    }
+	.aig-code-example-container {
+		background-color: var(--color-gray-200);
+		border-color: var(--color-neutral-300);
+		border-radius: 0.675rem;
+		border-bottom-left-radius: 0.85rem;
+		border-bottom-right-radius: 0.85rem;
+		--selector-bg-color: var(--color-white);
+		--selector-border-color: var(--color-neutral-300);
+		--selector-text-color: var(--color-gray-900);
+		--ec-brdRad: 0.675rem;
+		--ec-brdCol: var(--color-neutral-300);
+		&:where([data-theme="dark"], [data-theme="dark"] *) {
+			background-color: var(--color-neutral-900);
+			border-color: var(--color-neutral-700);
+			--selector-bg-color: var(--color-neutral-700);
+			--selector-border-color: var(--color-neutral-800);
+			--selector-text-color: var(--color-gray-100);
+			--ec-brdCol: var(--color-neutral-700);
+		}
+	}
 </style>
-<div class="border aig-code-example-container">
-<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
-{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript" title="" code={code
-        .replace("{provider}", option.provider)
-        .replace("{model}", option.model)
-        .replace("    {headerauth}\n","")}
-         />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript" title="" code={code
-        .replace("{provider}", option.provider)
-        .replace("{model}", option.model)
-        .replace("{cf_api_token}", "{" + option.provider + "_api_token}")
-        .replace("    {headerauth}\n","  defaultHeaders: {\n      // if gateway is authenticated\n      \"cf-aig-authorization\": `Bearer {cf_api_token}`, \n  },\n")}
-         />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
-            .replaceAll("{provider}", option.provider)
-            .replaceAll("{apikey}", "")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
-            .replaceAll("{provider}", option.provider)
-            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
+<div class="aig-code-example-container border">
+	<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
+	{
+		(!forceClient || forceClient === "openai-js") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="openai-js"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={code
+							.replace("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("    {headerauth}\n", "")}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "openai-js") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="openai-js"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={code
+							.replace("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("{cf_api_token}", "{" + option.provider + "_api_token}")
+							.replace(
+								"    {headerauth}\n",
+								'  defaultHeaders: {\n      // if gateway is authenticated\n      "cf-aig-authorization": `Bearer {cf_api_token}`, \n  },\n',
+							)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKUnifiedCode
+							.replaceAll("{provider}", option.provider)
+							.replaceAll("{apikey}", "")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKUnifiedCode
+							.replaceAll("{provider}", option.provider)
+							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
 
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKNativeCode
-            .replaceAll("{provider}", option.aiSDK.provider)
-            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-            .replaceAll("{apikey}", "")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKNativeCode
-            .replaceAll("{provider}", option.aiSDK.provider)
-            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="stored"
+					apiType="native"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKNativeCode
+							.replaceAll("{provider}", option.aiSDK.provider)
+							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+							.replaceAll("{apikey}", "")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="in-request"
+					apiType="native"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKNativeCode
+							.replaceAll("{provider}", option.aiSDK.provider)
+							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
 
-{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="curl" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code title="" lang="curl" code={curlCode
-            .replaceAll("{provider}", option.provider)
-            .replace("{model}", option.model)
-            .replace("{headerauth}\n","")}
-             />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="curl" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code title="" lang="curl" code={curlCode
-            .replaceAll("{provider}", option.provider)
-            .replace("{model}", option.model)
-            .replace("{headerauth}\n","  --header 'Authorization: Bearer {" + option.provider + "_api_token}' \\\n")} />
-    </CodeExample>
-))}
-</div>
\ No newline at end of file
+	{
+		(!forceClient || forceClient === "curl") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="curl"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						title=""
+						lang="curl"
+						code={curlCode
+							.replaceAll("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("{headerauth}\n", "")}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "curl") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="curl"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						title=""
+						lang="curl"
+						code={curlCode
+							.replaceAll("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace(
+								"{headerauth}\n",
+								"  --header 'Authorization: Bearer {" +
+									option.provider +
+									"_api_token}' \\\n",
+							)}
+					/>
+				</CodeExample>
+			))
+	}
+</div>
diff --git a/src/components/changelog/Pagination.astro b/src/components/changelog/Pagination.astro
index 33e8d73fe0001bd..633f1407b109d74 100644
--- a/src/components/changelog/Pagination.astro
+++ b/src/components/changelog/Pagination.astro
@@ -52,7 +52,10 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 
 {
 	lastPage > 1 && (
-		<nav class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2" aria-label="Pagination">
+		<nav
+			class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2"
+			aria-label="Pagination"
+		>
 			{prevUrl ? (
 				<a href={prevUrl} class="pagination-btn no-underline">
 					← Prev
@@ -64,7 +67,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 			<div class="pagination-pages flex items-center gap-1">
 				{items.map((item) =>
 					item === null ? (
-						<span class="flex h-9 items-center justify-center px-2 text-sm text-sl-color-gray-3">
+						<span class="text-sl-color-gray-3 flex h-9 items-center justify-center px-2 text-sm">
 							…
 						</span>
 					) : item === currentPage ? (
diff --git a/src/components/models/CopyableCode.astro b/src/components/models/CopyableCode.astro
index cf13027f562709e..0b17ed3299291d7 100644
--- a/src/components/models/CopyableCode.astro
+++ b/src/components/models/CopyableCode.astro
@@ -8,12 +8,7 @@ const { text, label = "Copy" } = Astro.props;
 ---
 
 <copyable-code data-text={text}>
-	<button
-		type="button"
-		title={label}
-		aria-label={label}
-		class="copy-button"
-	>
+	<button type="button" title={label} aria-label={label} class="copy-button">
 		<code>{text}</code>
 		<svg
 			xmlns="http://www.w3.org/2000/svg"
@@ -43,7 +38,9 @@ const { text, label = "Copy" } = Astro.props;
 		border: 1px solid var(--sl-color-gray-5);
 		background: transparent;
 		cursor: pointer;
-		transition: border-color 0.15s, background-color 0.15s;
+		transition:
+			border-color 0.15s,
+			background-color 0.15s;
 	}
 
 	.copy-button:hover {
diff --git a/src/components/models/ModelDetailPage.astro b/src/components/models/ModelDetailPage.astro
index f24f3a3540c7658..1019e2aa09c5ec0 100644
--- a/src/components/models/ModelDetailPage.astro
+++ b/src/components/models/ModelDetailPage.astro
@@ -188,7 +188,9 @@ const starlightPageProps = {
 			? { depth: 2, slug: "Examples", text: "Examples" }
 			: false,
 		hasSchema ? { depth: 2, slug: "Parameters", text: "Parameters" } : false,
-		hasSchema ? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" } : false,
+		hasSchema
+			? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" }
+			: false,
 	].filter((v) => Boolean(v)) as MarkdownHeading[],
 	hideTitle: true,
 } as StarlightPageProps;
@@ -424,22 +426,114 @@ const starlightPageProps = {
 					{model.apiModes.flatMap((mode) => [
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">
+									{mode.name}
+								</span>
 								<span class="ml-2 text-gray-500 dark:text-gray-400">Input</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/${mode.id}-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/${mode.id}-input.json`} download={`${mode.id}-input.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-input.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+										<polyline points="15 3 21 3 21 9" />
+										<line x1="10" y1="14" x2="21" y2="3" />
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-input.json`}
+									download={`${mode.id}-input.json`}
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+										<polyline points="7 10 12 15 17 10" />
+										<line x1="12" y1="15" x2="12" y2="3" />
+									</svg>
+								</a>
 							</span>
 						</div>,
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
-								<span class="ml-2 text-gray-500 dark:text-gray-400">Output</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">
+									{mode.name}
+								</span>
+								<span class="ml-2 text-gray-500 dark:text-gray-400">
+									Output
+								</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/${mode.id}-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/${mode.id}-output.json`} download={`${mode.id}-output.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-output.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+										<polyline points="15 3 21 3 21 9" />
+										<line x1="10" y1="14" x2="21" y2="3" />
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-output.json`}
+									download={`${mode.id}-output.json`}
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+										<polyline points="7 10 12 15 17 10" />
+										<line x1="12" y1="15" x2="12" y2="3" />
+									</svg>
+								</a>
 							</span>
 						</div>,
 					])}
@@ -483,17 +577,115 @@ const starlightPageProps = {
 					<h2 id="API-Schemas">API Schemas (Raw)</h2>
 					<div class="not-content grid grid-cols-1 gap-2 sm:grid-cols-2">
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Input</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
+								Input
+							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/schema-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/schema-input.json`} download="schema-input.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/schema-input.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+											<polyline points="15 3 21 3 21 9" />
+											<line x1="10" y1="14" x2="21" y2="3" />
+										</>
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/schema-input.json`}
+									download="schema-input.json"
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+											<polyline points="7 10 12 15 17 10" />
+											<line x1="12" y1="15" x2="12" y2="3" />
+										</>
+									</svg>
+								</a>
 							</span>
 						</div>
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Output</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
+								Output
+							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/schema-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/schema-output.json`} download="schema-output.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/schema-output.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+											<polyline points="15 3 21 3 21 9" />
+											<line x1="10" y1="14" x2="21" y2="3" />
+										</>
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/schema-output.json`}
+									download="schema-output.json"
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+											<polyline points="7 10 12 15 17 10" />
+											<line x1="12" y1="15" x2="12" y2="3" />
+										</>
+									</svg>
+								</a>
 							</span>
 						</div>
 					</div>
diff --git a/src/components/models/SchemaDisplay.astro b/src/components/models/SchemaDisplay.astro
index 6dcb17aa8c69d0f..e87bb767e12aced 100644
--- a/src/components/models/SchemaDisplay.astro
+++ b/src/components/models/SchemaDisplay.astro
@@ -196,11 +196,10 @@ function collectRows(
 			(reg.annotations?.description as string | undefined) ??
 			nullableChildDescription;
 		// Check both validations and fragment for enum (different schema parsers put it in different places)
-		const enumValues =
-			((reg.validations?.enum as unknown[]) ??
-				((reg.fragment as Record<string, unknown>)?.enum as unknown[]))?.map(
-				String,
-			);
+		const enumValues = (
+			(reg.validations?.enum as unknown[]) ??
+			((reg.fragment as Record<string, unknown>)?.enum as unknown[])
+		)?.map(String);
 
 		// Collect all metadata from fragment and validations
 		const metadata: Record<string, string | number | boolean> = {};
@@ -429,7 +428,12 @@ const variantRows =
 				No parameters defined.
 			</p>
 		) : (
-			<SchemaTreeView rows={rows} schemaId={schemaId} hideRequired={hideRequired} client:visible />
+			<SchemaTreeView
+				rows={rows}
+				schemaId={schemaId}
+				hideRequired={hideRequired}
+				client:visible
+			/>
 		)
 	}
 </div>
diff --git a/src/components/models/code/DeepgramFlux.astro b/src/components/models/code/DeepgramFlux.astro
index c5c957d047b01e8..119317163ac8ede 100644
--- a/src/components/models/code/DeepgramFlux.astro
+++ b/src/components/models/code/DeepgramFlux.astro
@@ -73,11 +73,13 @@ function generateRandomAudio() {
   return buffer;
 }
 `;
-
 ---
 
 <>
-	<Details header="Step 1: Create a Worker that establishes a WebSocket connection" open>
+	<Details
+		header="Step 1: Create a Worker that establishes a WebSocket connection"
+		open
+	>
 		<Code code={worker} lang="ts" />
 	</Details>
 
@@ -85,7 +87,10 @@ function generateRandomAudio() {
 		<Code code={deployWorker} lang="sh" />
 	</Details>
 
-  <Details header="Step 3: Write a client script to connect to your Worker and send audio" open>
-    <Code code={clientScript} lang="js" />
-  </Details>
+	<Details
+		header="Step 3: Write a client script to connect to your Worker and send audio"
+		open
+	>
+		<Code code={clientScript} lang="js" />
+	</Details>
 </>
diff --git a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
index e1f4ce5d0ae4e09..ac2d801c62fdeb2 100644
--- a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
+++ b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
@@ -76,8 +76,8 @@ curl https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/v1/
 		</li>
 		<li>
 			<strong>Workers AI Run</strong> (<code>/ai/run</code>) - Dynamic format
-			detection, accepts Chat Completions (<code>messages</code>), legacy Completions
-			(<code>prompt</code>), or Responses API (<code>input</code>)
+			detection, accepts Chat Completions (<code>messages</code>), legacy
+			Completions (<code>prompt</code>), or Responses API (<code>input</code>)
 		</li>
 		<li>
 			<strong>Chat Completions</strong> (<code>/v1/chat/completions</code>) -
diff --git a/src/components/overrides/Page.astro b/src/components/overrides/Page.astro
index 193c0458f2d2a57..e0ba5423f7dfb20 100644
--- a/src/components/overrides/Page.astro
+++ b/src/components/overrides/Page.astro
@@ -12,9 +12,11 @@ const html = await Astro.slots.render("default");
 // Agent-setup pages use `template: splash` (to avoid sidebar group lookup) but
 // still need a right-hand ToC. Splash pages have props.toc === undefined, so we
 // bootstrap the object here before calling generateTableOfContents.
-const isAgentSetup = props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
+const isAgentSetup =
+	props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
 if (isAgentSetup) {
-	if (!props.toc) props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
+	if (!props.toc)
+		props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
 	props.hideBreadcrumbs = true;
 	props.hideTitle = true;
 }
diff --git a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
index c7f5ea93bac1254..d03cecd7bab8754 100644
--- a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
+++ b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
@@ -1,12 +1,12 @@
 ---
 title: Cloudflare Access Logging supports the Customer Metadata Boundary (CMB)
-description: Access logs will now respect the CMB. 
+description: Access logs will now respect the CMB.
 date: 2025-08-14
 products:
   - access
 ---
 
-Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration. 
+Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration.
 
 :::note
 For EU CMB customers, the logs will not be stored by Access and will appear as empty in the dashboard. EU CMB customers should utilize [Logpush](/logs/logpush/) to retain their Access logging, if desired.
diff --git a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
index a82bbcbeee550b8..cd95cf8fdd1edba 100644
--- a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
+++ b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
@@ -15,4 +15,3 @@ An [MCP server portal](/cloudflare-one/access-controls/ai-controls/mcp-portals/)
 - **Observability**: Once the user's AI agent is connected to the portal, Cloudflare Access logs the individual requests made using the tools in the portal.
 
 This is available in an open beta for all customers across all plans! For more information check out our [blog](https://blog.cloudflare.com/zero-trust-mcp-server-portals/) for this release.
-
diff --git a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
index 675b9236a2b9f3d..91a89f79924c5c2 100644
--- a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
+++ b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
@@ -12,6 +12,4 @@ A new **Allow clientless access** setting makes it easier to connect users witho
 
 Previously, to provide clientless access to a private hostname or IP without a [published application](/cloudflare-one/networks/routes/add-routes/#add-a-published-application-route), you had to create a separate [bookmark application](/cloudflare-one/access-controls/applications/bookmarks/) pointing to a prefixed [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) URL (for example, `https://<your-teamname>.cloudflareaccess.com/browser/https://10.0.0.1/`). This bookmark was visible to all users in the App Launcher, regardless of whether they had access to the underlying application.
 
-Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When  **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
-
-
+Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
diff --git a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
index e3dde55074d43c6..8524d2348de427d 100644
--- a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
+++ b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
@@ -33,13 +33,13 @@ const tools = {
 	getWeather: tool({
 		description: "Get weather for a city",
 		inputSchema: z.object({ city: z.string() }),
-		execute: async ({ city }) => fetchWeather(city)
+		execute: async ({ city }) => fetchWeather(city),
 	}),
 
 	// Client-executed tool (no execute = client handles via onToolCall)
 	getLocation: tool({
 		description: "Get user location from browser",
-		inputSchema: z.object({})
+		inputSchema: z.object({}),
 		// No execute function
 	}),
 
@@ -48,8 +48,8 @@ const tools = {
 		description: "Process a payment",
 		inputSchema: z.object({ amount: z.number() }),
 		needsApproval: async ({ amount }) => amount > 100,
-		execute: async ({ amount }) => charge(amount)
-	})
+		execute: async ({ amount }) => charge(amount),
+	}),
 };
 ```
 
@@ -70,11 +70,11 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 				toolCallId: toolCall.toolCallId,
 				output: {
 					lat: position.coords.latitude,
-					lng: position.coords.longitude
-				}
+					lng: position.coords.longitude,
+				},
 			});
 		}
-	}
+	},
 });
 ```
 
@@ -97,9 +97,9 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 		// Handle client-side tool execution
 		await addToolOutput({
 			toolCallId: toolCall.toolCallId,
-			output: { result: "success" }
+			output: { result: "success" },
 		});
-	}
+	},
 });
 ```
 
@@ -112,12 +112,12 @@ const paymentTool = tool({
 	description: "Process a payment",
 	inputSchema: z.object({
 		amount: z.number(),
-		recipient: z.string()
+		recipient: z.string(),
 	}),
 	needsApproval: async ({ amount }) => amount > 1000,
 	execute: async ({ amount, recipient }) => {
 		return await processPayment(amount, recipient);
-	}
+	},
 });
 ```
 
@@ -138,7 +138,7 @@ const pendingToolCallConfirmation = messages.some((m) =>
 if (pendingToolCallConfirmation) {
 	await addToolOutput({
 		toolCallId: part.toolCallId,
-		output: "User approved the action"
+		output: "User approved the action",
 	});
 }
 ```
@@ -158,7 +158,7 @@ import { convertToModelMessages } from "ai";
 
 const result = streamText({
 	messages: await convertToModelMessages(this.messages),
-	model: openai("gpt-4o")
+	model: openai("gpt-4o"),
 });
 ```
 
@@ -182,14 +182,14 @@ const result = await generateObject({
 	mode: "json",
 	model,
 	schema,
-	prompt
+	prompt,
 });
 
 // After (v6)
 const result = await generateObject({
 	model,
 	schema,
-	prompt
+	prompt,
 });
 ```
 
@@ -203,10 +203,10 @@ import { generateText, Output, stepCountIs } from "ai";
 const { output } = await generateText({
 	model: openai("gpt-4"),
 	output: Output.object({
-		schema: z.object({ name: z.string() })
+		schema: z.object({ name: z.string() }),
 	}),
 	stopWhen: stepCountIs(2),
-	prompt: "Generate a name"
+	prompt: "Generate a name",
 });
 ```
 
@@ -282,11 +282,11 @@ import { createAIGateway } from "ai-gateway-provider";
 const model = createAIGateway({
 	gatewayUrl: "https://gateway.ai.cloudflare.com/v1/your-account-id/gateway",
 	headers: {
-		"Authorization": `Bearer ${env.AI_GATEWAY_TOKEN}`
-	}
+		Authorization: `Bearer ${env.AI_GATEWAY_TOKEN}`,
+	},
 })({
 	provider: "openai",
-	model: "gpt-4o"
+	model: "gpt-4o",
 });
 ```
 
diff --git a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
index c47df65f32e38d4..af9c6cd51586110 100644
--- a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
+++ b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
@@ -10,25 +10,25 @@ We are excited to announce two major capability upgrades for **Agent Lee**, the
 
 ### Take action with Write Operations
 
-Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. 
+Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.
 
 To ensure security and accuracy, every write operation requires **explicit user approval**. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select **Confirm**, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.
 
 **Example requests:**
-* *"Add an A record for blog.example.com pointing to 192.0.2.10."*
-* *"Enable Always Use HTTPS on my zone."*
-* *"Set the SSL mode for example.com to Full (strict)."*
 
+- _"Add an A record for blog.example.com pointing to 192.0.2.10."_
+- _"Enable Always Use HTTPS on my zone."_
+- _"Set the SSL mode for example.com to Full (strict)."_
 
 ### Visualize data with Generative UI
 
 Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features **Generative UI**, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry.
 
 **Example requests:**
-* *"Show me a chart of my traffic over the last 7 days."*
-* *"What does my error rate look like for the past 24 hours?"*
-* *"Graph my cache hit rate for example.com this week."*
 
+- _"Show me a chart of my traffic over the last 7 days."_
+- _"What does my error rate look like for the past 24 hours?"_
+- _"Graph my cache hit rate for example.com this week."_
 
 ---
 
diff --git a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
index 70d67fd32103d74..6142d6dbab74b1a 100644
--- a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
+++ b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
@@ -16,4 +16,4 @@ You can find these metrics within each AutoRAG instance:
 - Search breakdown: Compare usage between `ai-search` and `search` endpoints.
 - Top file retrievals: Identify which files are most frequently retrieved in a given period.
 
-Try it today in [AutoRAG](/ai-search/get-started/).
\ No newline at end of file
+Try it today in [AutoRAG](/ai-search/get-started/).
diff --git a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
index 1eff4229721c7bd..37bf0f628f7a6a7 100644
--- a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
+++ b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
@@ -13,9 +13,9 @@ With AI Search you can now use models from different providers like OpenAI and A
 To use AI Search with other [model providers](/ai-search/configuration/models/):
 
 1. **Add provider keys to AI Gateway**
-    1. Go to AI > AI Gateway in the dashboard.
-    2. Select or create an AI gateway.
-    3. In Provider Keys, choose your provider, click Add, and enter the key.
+   1. Go to AI > AI Gateway in the dashboard.
+   2. Select or create an AI gateway.
+   3. In Provider Keys, choose your provider, click Add, and enter the key.
 2. **Connect a gateway to AI Search**: When creating a new AI Search, select the AI Gateway with your provider keys. For an existing AI Search, go to Settings and switch to a gateway that has your keys under Resources.
 3. **Select models**: Embedding models are only available to be changed when creating a new AI Search. Generation model can be selected when creating a new AI Search and can be changed at any time in Settings.
 
@@ -23,19 +23,18 @@ Once configured, your AI Search instance will be able to reference models availa
 
 ```javascript
 export default {
-  async fetch(request, env) {
-    
-    // Query your AI Search instance with a natural language question to an OpenAI model
-    const result = await env.AI.autorag("my-ai-search").aiSearch({
-      query: "What's new for Cloudflare Birthday Week?",
-      model: "openai/gpt-5"
-    });
-
-    // Return only the generated answer as plain text
-    return new Response(result.response, {
-      headers: { "Content-Type": "text/plain" },
-    });
-  },
+	async fetch(request, env) {
+		// Query your AI Search instance with a natural language question to an OpenAI model
+		const result = await env.AI.autorag("my-ai-search").aiSearch({
+			query: "What's new for Cloudflare Birthday Week?",
+			model: "openai/gpt-5",
+		});
+
+		// Return only the generated answer as plain text
+		return new Response(result.response, {
+			headers: { "Content-Type": "text/plain" },
+		});
+	},
 };
 ```
 
diff --git a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
index 5a9abdb9296fae3..561919395ce174d 100644
--- a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
+++ b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
@@ -10,7 +10,8 @@ date: 2025-11-19
 
 Previously, AI Search could only crawl publicly accessible pages, leaving knowledge bases, documentation, and other protected content out of your search results. With custom headers support, you can now include authentication credentials that allow the crawler to access this protected content.
 
-This is particularly useful for indexing content like: 
+This is particularly useful for indexing content like:
+
 - **Internal documentation** behind corporate login systems
 - **Premium content** that requires users to provide access to unlock
 - **Sites protected by Cloudflare Access** using service tokens
@@ -26,6 +27,6 @@ CF-Access-Client-Id: your-token-id.access
 CF-Access-Client-Secret: your-token-secret
 ```
 
-The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked. 
+The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked.
 
-Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
\ No newline at end of file
+Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
diff --git a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
index a54b6cddfff6e9a..105ae21f43fe4fd 100644
--- a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
+++ b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
@@ -7,13 +7,13 @@ date: 2026-04-16T12:00:00Z
 publish_future_dated_entry: true
 ---
 
-New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away. 
+New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away.
 
 Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call.
 
 ## Built-in storage and vector index
 
-All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first. 
+All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first.
 
 ```ts
 const instance = env.AI_SEARCH.get("my-instance");
diff --git a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
index e8c0c6621a0467f..420f30e5265e339 100644
--- a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
+++ b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
@@ -3,12 +3,12 @@ title: New Confidence Intervals in GraphQL Analytics API
 description: Confidence intervals are now supported in the GraphQL Analytics API to show statistical ranges for sampled data results
 date: 2025-10-01
 ---
- 
-The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty. 
+
+The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty.
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`). 
+- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`).
 - **Default**: If no confidence level is specified, no intervals are returned.
 
-For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/). 
+For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/).
diff --git a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
index 6194d159eaef0a2..91c0a2dc9d56063 100644
--- a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
+++ b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
@@ -8,10 +8,10 @@ The Server-Timing header now includes a new `cfWorker` metric that measures time
 
 Previously, Worker execution time was included in the `edge` metric, making it harder to identify true edge performance. The new `cfWorker` metric provides this visibility:
 
-| Metric | Description |
-| --- | --- |
-| `edge` | Total time spent on the Cloudflare edge, including Worker execution |
-| `origin` | Time spent fetching from the origin server |
+| Metric     | Description                                                                           |
+| ---------- | ------------------------------------------------------------------------------------- |
+| `edge`     | Total time spent on the Cloudflare edge, including Worker execution                   |
+| `origin`   | Time spent fetching from the origin server                                            |
 | `cfWorker` | Time spent in Worker execution, including subrequests but excluding origin fetch time |
 
 ### Example response
diff --git a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
index 1b6ce51e1eb4bfd..32a3c52bdfbfc7f 100644
--- a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
+++ b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
@@ -10,8 +10,8 @@ Cloudflare is launching the [Open Beta of the **Web and API Vulnerability Scanne
 
 The initial release focuses on detecting Broken Object Level Authorization (BOLA) vulnerabilities by building API call graphs to simulate attacker and owner contexts, then testing these contexts by sending real HTTP requests to your APIs.
 
-The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release. 
+The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release.
 
 **Access**: This feature is only available to API Shield subscribers via the Cloudflare API. We hope you will use the API for programmatic integration into your CI/CD pipelines and security dashboards.
 
-**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
\ No newline at end of file
+**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
diff --git a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
index 968d7e9e61a7325..8f0e0c75c5a3682 100644
--- a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
+++ b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
@@ -12,13 +12,13 @@ You can now receive [event notifications](/queues/event-subscriptions/) for [Art
 
 This allows you to:
 
-* Run custom workflows when a repository is created or imported
-* Kick off a build and deploy a change when an agent pushes to a repo
-* Trigger a review agent on every push
+- Run custom workflows when a repository is created or imported
+- Kick off a build and deploy a change when an agent pushes to a repo
+- Trigger a review agent on every push
 
 Available events include:
 
-* **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
-* **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
+- **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
+- **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
 
 To learn more, refer to [Artifacts documentation](/artifacts/guides/event-subscriptions/).
diff --git a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
index d613bad87530e49..18f7b35d1cbd348 100644
--- a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
+++ b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
@@ -27,4 +27,3 @@ You can now create optimized cache rules instantly with **one-click templates**,
 ## Get started
 
 To get started, go to [**Rules > Templates**](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) in the dashboard. For more information, refer to the [Cache Rules documentation](/cache/how-to/cache-rules/).
-
diff --git a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
index 13727aa33125d77..803a3785a4f7930 100644
--- a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
+++ b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
@@ -26,14 +26,14 @@ When configuring [custom cache keys](/cache/how-to/cache-keys/), you can now inc
 
 ```json
 {
-  "cache_key": {
-    "custom_key": {
-      "header": {
-        "include": ["accept-language", "user-agent"],
-        "check_presence": ["referer"]
-      }
-    }
-  }
+	"cache_key": {
+		"custom_key": {
+			"header": {
+				"include": ["accept-language", "user-agent"],
+				"check_presence": ["referer"]
+			}
+		}
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
index 3f346c5807413c8..a9d29c3c2cfc2b5 100644
--- a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
+++ b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
@@ -20,19 +20,19 @@ The Trace response includes the cache key in the `cache` object:
 
 ```json
 {
-  "step_name": "request",
-  "type": "cache",
-  "matched": true,
-  "public_name": "Cache Parameters",
-  "cache": {
-    "key": {
-      "zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
-      "scheme": "https",
-      "host": "example.com",
-      "uri": "/images/hero.jpg"
-    },
-    "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
-  }
+	"step_name": "request",
+	"type": "cache",
+	"matched": true,
+	"public_name": "Cache Parameters",
+	"cache": {
+		"key": {
+			"zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
+			"scheme": "https",
+			"host": "example.com",
+			"uri": "/images/hero.jpg"
+		},
+		"key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
index 814ebc40610e652..3f7c005146bb17a 100644
--- a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
+++ b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
@@ -20,28 +20,28 @@ The detailed audit payload is visible within the Cloudflare Dashboard (under **M
 
 ```json
 {
-  "action": {
-    "result": "success",
-    "type": "create"
-  },
-  "actor": {
-    "id": "1234567890abcdef",
-    "email": "user@example.com",
-    "type": "user"
-  },
-  "resource": {
-    "product": "purge_cache",
-    "request": {
-      "files": [
-        "https://example.com/images/logo.png",
-        "https://example.com/css/styles.css"
-      ]
-    }
-  },
-  "zone": {
-    "id": "023e105f4ecef8ad9ca31a8372d0c353",
-    "name": "example.com"
-  }
+	"action": {
+		"result": "success",
+		"type": "create"
+	},
+	"actor": {
+		"id": "1234567890abcdef",
+		"email": "user@example.com",
+		"type": "user"
+	},
+	"resource": {
+		"product": "purge_cache",
+		"request": {
+			"files": [
+				"https://example.com/images/logo.png",
+				"https://example.com/css/styles.css"
+			]
+		}
+	},
+	"zone": {
+		"id": "023e105f4ecef8ad9ca31a8372d0c353",
+		"name": "example.com"
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
index f8b1270d926561c..220ad070c02db00 100644
--- a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
+++ b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-24
 ---
 
-You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses *before* they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
+You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses _before_ they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
 
 ## What changed
 
diff --git a/src/content/changelog/casb/2025-10-28-casb-roles.mdx b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
index 0eba434bfd0c136..45bf12202502ff5 100644
--- a/src/content/changelog/casb/2025-10-28-casb-roles.mdx
+++ b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
@@ -8,8 +8,8 @@ date: 2025-10-28
 
 Cloudflare CASB (Cloud Access Security Broker) now supports two new granular roles to provide more precise access control for your security teams:
 
-* **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
-* **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
+- **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
+- **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
 
 These new roles help you better enforce the principle of least privilege. You can now grant specific members access to CASB security findings without assigning them broader permissions, such as the **Super Administrator** or **Administrator** roles.
 
diff --git a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
index 06fb9e1526fa249..8293deadac922ee 100644
--- a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
+++ b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
@@ -5,4 +5,3 @@ date: 2025-08-29
 ---
 
 We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client.
-
diff --git a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
index ae69ba66324f32d..40a2ecfb6928699 100644
--- a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
+++ b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
@@ -9,9 +9,9 @@ products:
 Zero Trust Dashboard has a brand new, AI-powered search functionality. You can search your account by resources (applications, policies, device profiles, settings, etc.), pages, products, and more.
 
 ![Example search results in the Zero Trust dashboard](~/assets/images/changelog/cloudflare-one/searchexample.png)
-  
+
 **Ask Cloudy** — You can also ask Cloudy, our AI agent, questions about Cloudflare Zero Trust. Cloudy is trained on our developer documentation and implementation guides, so it can tell you how to configure functionality, best practices, and can make recommendations.
 
 Cloudy can then stay open with you as you move between pages to build configuration or answer more questions.
 
-**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
\ No newline at end of file
+**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
diff --git a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
index d4b4b3081b4aa3a..b0f6e01371820c0 100644
--- a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
+++ b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
@@ -8,10 +8,10 @@ products:
 
 You can now duplicate specific Cloudflare One resources with a single click from the dashboard.
 
-
 Initially supported resources:
-* Access Applications
-* Access Policies
-* Gateway Policies
 
-To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
\ No newline at end of file
+- Access Applications
+- Access Policies
+- Gateway Policies
+
+To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
index 3732caa81147c83..1cbf0a71d44db2b 100644
--- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx
+++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
@@ -7,7 +7,7 @@ product: Gateway
 
 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications.
 
-33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. 
+33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security.
 
 To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**.
 
diff --git a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
index 03fb76c0a537bc1..9be106dafc193cc 100644
--- a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
+++ b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
@@ -23,4 +23,4 @@ Key details:
 
 Configuring Cloudflare source IPs requires Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
 
-For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
\ No newline at end of file
+For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
diff --git a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
index 32af30f28627705..a42523b426c282c 100644
--- a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
+++ b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
@@ -9,7 +9,7 @@ date: 2025-10-01
 New instance types provide up to 4 vCPU, 12 GiB of memory, and 20 GB of disk per container instance.
 
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------  | ----  |
+| ------------- | ---- | ------- | ----- |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
diff --git a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
index 3a6f1aa9ae491fc..1d4d4ea196130e1 100644
--- a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
+++ b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
@@ -15,15 +15,15 @@ This means that you now pay less for Containers and Sandboxes.
 Imagine running the `standard-2` instance type for one hour, which can use up to 1 vCPU,
 but on average you use only 20% of your CPU capacity.
 
-CPU-time is priced at *$0.00002 per vCPU-second*.
+CPU-time is priced at _$0.00002 per vCPU-second_.
 
 Previously, you would be charged for the CPU allocated to the instance multiplied by the time it was active, in this case 1 hour.
 
-CPU cost would have been: **$0.072** — 1 vCPU * 3600 seconds * $0.00002
+CPU cost would have been: **$0.072** — 1 vCPU _ 3600 seconds _ $0.00002
 
 Now, since you are only using 20% of your CPU capacity, your CPU cost is cut to 20% of the previous amount.
 
-CPU cost is now: **$0.0144** — 1 vCPU * 3600 seconds * $0.00002 * 20% utilization
+CPU cost is now: **$0.0144** — 1 vCPU _ 3600 seconds _ $0.00002 \* 20% utilization
 
 This can significantly reduce costs for Containers and Sandboxes.
 
diff --git a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
index 242d66f2e0cf6e2..baf0295247c3495 100644
--- a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
+++ b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
@@ -16,4 +16,4 @@ You can now run more [Containers](/containers/) concurrently with significantly
 
 This 15x increase enables larger-scale workloads on Containers. You can now run 15,000 instances of the `lite` instance type, 6,000 instances of `basic`, over 1,500 instances of `standard-1`, or over 1,000 instances of `standard-2` concurrently.
 
-Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
\ No newline at end of file
+Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
diff --git a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
index cb2468f841ffe89..d9a25a5bf08676f 100644
--- a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
+++ b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
@@ -27,4 +27,4 @@ Containers now support [Docker Hub](https://hub.docker.com/) images. You can use
 
 Containers also support private Docker Hub images. To configure credentials, refer to [Use private Docker Hub images](/containers/platform-details/image-management/#use-private-docker-hub-images).
 
-For more information, refer to [Image management](/containers/platform-details/image-management/).
\ No newline at end of file
+For more information, refer to [Image management](/containers/platform-details/image-management/).
diff --git a/src/content/changelog/containers/2026-04-05-regional-placement.mdx b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
index 2871fa894eff6a3..bb35775f82b0c78 100644
--- a/src/content/changelog/containers/2026-04-05-regional-placement.mdx
+++ b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
@@ -8,10 +8,10 @@ date: 2026-04-05
 
 You can now specify placement constraints to control where your [Containers](/containers/) run.
 
-| Constraint     | Values                                  | Use case                          |
-| -------------- | --------------------------------------- | --------------------------------- |
-| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR`          | Geographic placement              |
-| `jurisdiction` | `eu`, `fedramp`                         | Compliance boundaries             |
+| Constraint     | Values                         | Use case              |
+| -------------- | ------------------------------ | --------------------- |
+| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR` | Geographic placement  |
+| `jurisdiction` | `eu`, `fedramp`                | Compliance boundaries |
 
 Use `regions` to limit placement to specific geographic areas. Use `jurisdiction` to restrict containers to compliance boundaries — `eu` maps to European regions (EEUR, WEUR) and `fedramp` maps to North American regions (ENAM, WNAM).
 
diff --git a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
index 4b8f807edcebfbe..169bb898b975965 100644
--- a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
+++ b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
@@ -74,7 +74,7 @@ Define named outbound handlers then apply or remove them at runtime using `setOu
 export class MySandbox extends Sandbox {}
 
 MySandbox.outboundHandlers = {
-	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext ) => {
+	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext) => {
 		const url = new URL(req.url);
 		if (ctx.params.allowedHostnames.includes(url.hostname)) {
 			return fetch(req);
diff --git a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
index 797ef3ce255a866..9b7229b637259e4 100644
--- a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
+++ b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
@@ -51,4 +51,4 @@ To disable SSH, set `ssh.enabled` to `false` in your Container configuration:
 
 </WranglerConfig>
 
-For more information, refer to the [SSH documentation](/containers/ssh/).
\ No newline at end of file
+For more information, refer to the [SSH documentation](/containers/ssh/).
diff --git a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
index 7a8ddd2b404d6c1..076405a6f32954f 100644
--- a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
+++ b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
@@ -6,7 +6,7 @@ date: 2025-11-12
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into WARP device metrics, connectivity, and network performance across your Cloudflare SASE deployment.
 
-We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience. 
+We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience.
 
 1. [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)
 2. [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)
@@ -15,4 +15,4 @@ We've released four new WARP and DEX device data sets that can be exported via [
 
 To create a new DEX or WARP Logpush job, customers can go to the account level of the Cloudflare dashboard > Analytics & Logs > Logpush to get started.
 
-![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
\ No newline at end of file
+![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
diff --git a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
index 25a72ef1269d528..eaa2318c8339332 100644
--- a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
+++ b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
@@ -2,7 +2,6 @@
 title: DEX Supports EU Customer Metadata Boundary
 description: Digital Experience Monitoring now fully supports the EU Customer Metadata Boundary
 date: 2026-02-19
-
 ---
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into [WARP](/warp-client/) device connectivity and performance to any internal or external application.
diff --git a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
index df5d41b9f6f8634..5dabd4aeb835f4e 100644
--- a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
@@ -9,4 +9,4 @@ date: 2026-04-28
 This Internet outage and traffic anomaly data is pulled from [Cloudflare Radar](https://radar.cloudflare.com/). All Internet outage and traffic anomaly observations can be viewed in the [Radar Outage Center](https://radar.cloudflare.com/outage-center).
 
 ![Digital Experience Monitoring dashboard notification for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_ux_notification.png)
-![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
\ No newline at end of file
+![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
diff --git a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
index 37b7e2b2737abdf..a85263a713f6a1e 100644
--- a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
@@ -4,9 +4,10 @@ description: Customers can run speed tests from the Cloudflare One Client to Clo
 date: 2026-04-28
 ---
 
-IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge. 
+IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge.
 
 Each speed test includes the following metrics:
+
 - Internet speed: download and upload throughput
 - Latency: download, upload, unloaded latency, and jitter
 - Network quality score: video streaming, webchat/real-time communication (RTC)
diff --git a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
index abfb872fa28d368..6af9120fe4e08ee 100644
--- a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
+++ b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
@@ -4,9 +4,10 @@ description: Digital experience now supports testing applications with authentic
 date: 2026-04-29
 ---
 
-[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/). 
+[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/).
 
 Digital experience tests also have enhanced configuration options including:
+
 - New HTTP methods (DELETE, PATCH, POST, PUT)
 - Secret Store headers, custom plain text headers, and custom request bodies
 - Advanced settings: follow redirects, response bodies, response headers, and allow untrusted certificates
diff --git a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
index 73705ab18a430b6..608405c5701e920 100644
--- a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
+++ b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
@@ -9,6 +9,7 @@ date: 2026-04-14T12:00:00Z
 **Account-level DLP settings are now available** in Cloudflare One. You can now configure advanced DLP settings at the account level, including OCR, AI context analysis, and payload masking. This provides consistent enforcement across all DLP profiles and simplifies configuration management.
 
 Key changes:
+
 - **Consistent enforcement**: Settings configured at the account level apply to all DLP profiles
 - **Simplified migration**: Settings enabled on any profile are automatically migrated to account level
 - **Deprecation notice**: Profile-level advanced settings will be deprecated in a future release
diff --git a/src/content/changelog/dlp/2025-07-17-document-matching.mdx b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
index 7d3ef70acea78af..16c90b0f67b6ee1 100644
--- a/src/content/changelog/dlp/2025-07-17-document-matching.mdx
+++ b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
@@ -15,10 +15,9 @@ You can now create [document-based](/cloudflare-one/data-loss-prevention/detecti
 - **Granular control with similarity percentage:** Define a minimum similarity percentage (0-100%) that a document must meet to trigger a detection, reducing false positives.
 
 - **Comprehensive coverage:** Apply these document-based detection entries in:
+  - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
 
-    - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
-
-    - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
+  - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
 
 - **Identify sensitive data:** This new detection entry type is ideal for identifying sensitive data within completed forms, templates, or even small snippets of a larger document, helping you prevent data exfiltration and ensure compliance.
 
diff --git a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
index 21f93780d77fd28..17cdc9544eb17e9 100644
--- a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
+++ b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
@@ -24,14 +24,14 @@ To help you apply these topics quickly, we have also released five new predefine
 
 3. **Granular Guardrails**
 
-    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
+   You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
 
-    ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
+   ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
 
- 4. **Full Prompt Logging**
-   
-    To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by ```conversation_id```, allowing you to reconstruct the full context of an interaction that led to a policy violation.
+4. **Full Prompt Logging**
 
-    ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
+   To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by `conversation_id`, allowing you to reconstruct the full context of an interaction that led to a policy violation.
+
+   ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
 
 AI prompt protection is now available in open beta. To learn more about it, read the [blog](https://blog.cloudflare.com/ai-prompt-protection/#closing-the-loop-logging) or refer to [AI prompt topics](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics).
diff --git a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
index 5c12da589a2636c..d8e05425862ab77 100644
--- a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
+++ b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
@@ -11,7 +11,7 @@ Gateway now includes a predefined DLP profile called **Unsanitized HAR** that de
 
 ## How to configure a HAR file policy
 
-In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to  **Zero Trust** >  **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
+In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
 
 | Selector    | Operator | Value             | Action |
 | ----------- | -------- | ----------------- | ------ |
diff --git a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
index 7326522ab2e356e..649f291806b1ee8 100644
--- a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
+++ b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
@@ -7,11 +7,11 @@ products: [dlp]
 
 The **Credentials and Secrets** DLP profile now includes three new predefined entries for detecting Cloudflare API credentials:
 
-| Entry name | Token prefix | Detects |
-| --- | --- | --- |
-| Cloudflare User API Key | `cfk_` | User-scoped API keys |
-| Cloudflare User API Token | `cfut_` | User-scoped API tokens |
-| Cloudflare Account Owned API Token | `cfat_` | Account-scoped API tokens |
+| Entry name                         | Token prefix | Detects                   |
+| ---------------------------------- | ------------ | ------------------------- |
+| Cloudflare User API Key            | `cfk_`       | User-scoped API keys      |
+| Cloudflare User API Token          | `cfut_`      | User-scoped API tokens    |
+| Cloudflare Account Owned API Token | `cfat_`      | Account-scoped API tokens |
 
 These detections target the new [Cloudflare API credential format](/fundamentals/api/get-started/token-formats/), which uses a structured prefix and a CRC32 checksum suffix. The identifiable prefix makes it possible to detect leaked credentials with high confidence and low false positive rates — no surrounding context such as `Authorization: Bearer` headers is required.
 
@@ -26,9 +26,9 @@ Credentials generated before this format change will not be matched by these ent
 
 Example policy:
 
-| Selector | Operator | Value | Action |
-| --- | --- | --- | --- |
-| DLP Profile | in | _Credentials and Secrets_ | Block |
+| Selector    | Operator | Value                     | Action |
+| ----------- | -------- | ------------------------- | ------ |
+| DLP Profile | in       | _Credentials and Secrets_ | Block  |
 
 You can also enable individual entries to scope detection to specific credential types — for example, enabling **Account Owned API Token** detection without enabling **User API Key** detection.
 
diff --git a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
index a4a744c06468c98..64134f5ef20859c 100644
--- a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
+++ b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
@@ -2,7 +2,7 @@
 title: Detect PII records with a new predefined DLP profile
 description: A new predefined DLP profile detects records that contain multiple types of personal data, reducing false positives from isolated matches.
 date: 2026-04-28
-products: 
+products:
   - dlp
 ---
 
diff --git a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
index 483aed6201b6f66..fda8a201e4ce67f 100644
--- a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
+++ b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
@@ -7,6 +7,7 @@ date: 2026-03-31
 Internal DNS is now in open beta.
 
 ## Who can use it?
+
 Internal DNS is bundled as a part of Cloudflare Gateway and is now available to every Enterprise customer with one of the following subscriptions:
 
 - Cloudflare Zero Trust Enterprise
diff --git a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
index ada68f5dc86c767..e9117eeb36fbf71 100644
--- a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
+++ b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
@@ -3,6 +3,7 @@ title: Account-level enforce DNS-only
 description: Bypass Cloudflare's reverse proxy for all zones in your account with a single API call.
 date: 2026-04-28
 ---
+
 import { DashButton } from "~/components";
 
 You can now disable Cloudflare's reverse proxy across all zones in your account simultaneously using the new `enforce_dns_only` setting. When enabled, Cloudflare responds to DNS queries for all proxied records with your origin IP addresses instead of Cloudflare's anycast IPs.
diff --git a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
index e03702fa3be2931..eb2897fd7f98f7b 100644
--- a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
+++ b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
@@ -10,11 +10,11 @@ date: 2025-08-21
 You can now create a client (a [Durable Object stub](/durable-objects/api/stub/)) to a Durable Object with the new `getByName` method, removing the need to convert Durable Object names to IDs and then create a stub.
 
 ```js
-// Before: (1) translate name to ID then (2) get a client 
+// Before: (1) translate name to ID then (2) get a client
 const objectId = env.MY_DURABLE_OBJECT.idFromName("foo"); // or .newUniqueId()
-const stub = env.MY_DURABLE_OBJECT.get(objectId); 
+const stub = env.MY_DURABLE_OBJECT.get(objectId);
 
-// Now: retrieve client to Durable Object directly via its name 
+// Now: retrieve client to Durable Object directly via its name
 const stub = env.MY_DURABLE_OBJECT.getByName("foo");
 
 // Use client to send request to the remote Durable Object
@@ -23,4 +23,4 @@ const rpcResponse = await stub.sayHello();
 
 Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together. You can have billions of Durable Objects, providing isolation between application tenants.
 
-To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
\ No newline at end of file
+To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
diff --git a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
index 10b3c5b7270cdbe..b0b6b6b70c779bb 100644
--- a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
+++ b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
 
 ![Screenshot of Durable Objects Data Studio](~/assets/images/workers/changelog/do-data-studio.png)
 
-You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.  
+You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.
 
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
diff --git a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
index 7d4b1c1963247eb..ab0bc29c8091916 100644
--- a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
+++ b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
@@ -9,9 +9,10 @@ date: 2025-12-12
 
 import { DashButton } from "~/components";
 
-Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). 
+Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier).
 
 To view your SQLite storage usage, go to the **Durable Objects** page
+
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
 If you do not want to incur costs, please take action such as optimizing queries or deleting unnecessary stored data in order to reduce your SQLite storage usage ahead of the January 7th target. Only usage on and after the billing target date will incur charges.
diff --git a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
index c3a7dd97977d0d4..01b6f70aebb1c1f 100644
--- a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
+++ b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
@@ -15,19 +15,19 @@ This is especially useful for [alarms](/durable-objects/api/alarms/), where ther
 import { DurableObject } from "cloudflare:workers";
 
 export class ChatRoom extends DurableObject {
-  async getRoomName() {
-    // ctx.id.name returns the name passed to getByName() or idFromName()
-    return this.ctx.id.name;
-  }
+	async getRoomName() {
+		// ctx.id.name returns the name passed to getByName() or idFromName()
+		return this.ctx.id.name;
+	}
 }
 
 // Worker
 export default {
-  async fetch(request, env) {
-    const stub = env.CHAT_ROOM.getByName("general");
-    const roomName = await stub.getRoomName();
-    return new Response(`Welcome to ${roomName}!`);
-  },
+	async fetch(request, env) {
+		const stub = env.CHAT_ROOM.getByName("general");
+		const roomName = await stub.getRoomName();
+		return new Response(`Welcome to ${roomName}!`);
+	},
 };
 ```
 
diff --git a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
index d4933092b676b0e..7bbf5100d38aea3 100644
--- a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
+++ b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
@@ -12,4 +12,4 @@ Customers can use this feature to dynamically add context to their emails, such
 
 ![Subaddressing](~/assets/images/changelog/email-routing/subaddressing.png)
 
-Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
\ No newline at end of file
+Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
diff --git a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
index 2a643465f298e14..7ac05e0429ad659 100644
--- a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
+++ b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
@@ -16,4 +16,4 @@ This feature is available across these Email security packages:
 
 - **Advantage**
 - **Enterprise**
-- **Enterprise + PhishGuard**
\ No newline at end of file
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
index 7e74cf7136cb225..24afb396ce499bc 100644
--- a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
+++ b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
@@ -13,7 +13,6 @@ These reports offer several key benefits:
 - **Configuration Transparency:** Gain a clear view of your policy, submission, and domain configurations to ensure optimal setup.
 - **Account Takeover Risks:** Get a snapshot of your M365 risky users (requires a Microsoft Entra ID P2 license and [M365 SaaS integration](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/microsoft-365/)).
 
-
 To get started, refer to [Download a security report](/cloudflare-one/email-security/monitoring/download-report/#download-a-security-report).
 ![Report](~/assets/images/changelog/email-security/report.png)
 
diff --git a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
index 47d73e8920e5d3c..cbb47a69c0949ea 100644
--- a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
+++ b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
@@ -6,8 +6,7 @@ date: 2025-11-18
 
 # Adjustment to Final Disposition column
 
-The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
----
+## The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
 
 ### What's Changing
 
diff --git a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
index b8d67579c27c156..92b39dac688afa0 100644
--- a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
+++ b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
@@ -1,6 +1,6 @@
 ---
 title: Reclassifications to Submissions
-description: Submission terminology update to reflect outcomes 
+description: Submission terminology update to reflect outcomes
 date: 2025-12-03T21:11:33Z
 ---
 
@@ -10,7 +10,8 @@ Submissions are leveraged to tune future variants of campaigns. To respect data
 
 ![nav_example](~/assets/images/changelog/email-security/reclassification-submission.png)
 
-This applies to all Email Security packages: 
--   **Advantage** 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
index b38737ac382f6db..e12c5cc1bef0386 100644
--- a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
+++ b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
@@ -4,7 +4,7 @@ description: Additional post delivery action log details for failures
 date: 2026-01-12T11:15:33Z
 ---
 
-The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field. 
+The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field.
 
 :::note
 Error messages will vary depending on whether you are using Google Workspace or Microsoft 365.
@@ -14,6 +14,7 @@ Error messages will vary depending on whether you are using Google Workspace or
 
 This update allows you to see the full lifecycle of a failed action. For instance, if an administrator tries to move an email that has already been deleted or moved manually, the log will now show the multiple retry attempts and the specific destination error.
 
-This applies to all Email Security packages: 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
index 2b9c5533289c542..fdf3bbd3fac9920 100644
--- a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
+++ b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
@@ -6,17 +6,17 @@ date: 2026-02-02T11:05:33Z
 
 We have updated the Monitoring page to provide a more streamlined and insightful experience for administrators, improving both data visualization and dashboard accessibility.
 
-* **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis. 
-![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
-* **Improved Accessibility & Usability**: 
-    * **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation. 
-    * **Actionable UI**: All available actions are now accessible via dedicated buttons. 
-    * **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions. 
-![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
-* **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
-![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
+- **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis.
+  ![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
+- **Improved Accessibility & Usability**:
+  _ **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation.
+  _ **Actionable UI**: All available actions are now accessible via dedicated buttons. \* **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions.
+  ![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
+- **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
+  ![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
 
-This applies to all Email Security packages: 
--   **Advantage** 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
index 6d9695bd7a66d3e..40ee34a930aa4d0 100644
--- a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
+++ b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
@@ -10,12 +10,12 @@ In the dashboard, infinite paging is now supported in the Investigations view. T
 
 For high-volume use cases, we recommend:
 
--   **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
--   **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
--   **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
+- **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
+- **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
+- **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
 
 This applies to all Email Security packages:
 
--   **Advantage**
--   **Enterprise**
--   **Enterprise + PhishGuard**
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
index a69648a508bacbf..cf4ab36e568d60c 100644
--- a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
@@ -3,12 +3,14 @@ title: DANE Support for MX Deployments
 description: DNSSEC-backed TLSA records now available on regional MX hostnames for verified encrypted email delivery
 date: 2026-04-06T09:00:00Z
 ---
+
 Cloudflare Email Security now supports DANE (DNS-based Authentication of Named Entities) for MX deployments. This enhancement strengthens email transport security by enabling DNSSEC-backed certificate verification for our regional MX records.
 
-* Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
-* DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
+- Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
+- DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
 
 This applies to all Email Security packages:
--   **Advantage**
--   **Enterprise**
--   **Enterprise + PhishGuard**
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
index 3019f6e986513d4..eab1731927d760e 100644
--- a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
@@ -5,12 +5,14 @@ date: 2026-04-07 09:00:00 UTC
 ---
 
 Cloudflare Email security now supports **Triage Status Tracking for User Submissions**. This enhancement gives SOC teams a streamlined way to track, manage, and prioritize user-submitted emails directly within the Cloudflare One dashboard.
+
 - The User Submissions table now includes a **Status** column with three states: **Unreviewed** (new submissions awaiting triage), **Reviewed** (submissions assessed by the SOC team), and **Escalated** (submissions escalated to team submissions for further investigation). Analysts can quickly update statuses and filter the table to focus on what needs attention.
 - SOC teams can now organize their triage workflows, avoid duplicate reviews, and make sure critical threats get escalated for deeper investigation—bringing order to the chaos of high-volume submission management.
 
 Triage Status Tracking is **automatically available** for all Email security customers using the user submissions feature. No additional configuration is required; customers just need to make sure user submissions are being sent to their user submission aliases.
 
 This applies to all Email security packages:
+
 - **Advantage**
 - **Enterprise**
 - **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
index 558c35e1449d8c7..8447a0ad8b9c7aa 100644
--- a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
+++ b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
@@ -3,6 +3,7 @@ title: Cloudy Summaries in PhishNet O365
 description: Cloudy email summaries are now available in PhishNet for Office 365 environments.
 date: 2026-05-06T18:15:13Z
 ---
+
 PhishNet users can now access **Cloudy summaries** directly within the email investigation experience. When reviewing a message in PhishNet, users will see an AI-generated summary that provides additional context and key details about the email.
 
 These summaries help users quickly understand the nature of a message without needing to manually parse through headers, body content, and detection signals. Cloudy surfaces the most relevant information so users can make faster, more informed decisions about suspicious emails.
diff --git a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
index a5377b7e567f220..55a9de27459f439 100644
--- a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
+++ b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
@@ -14,11 +14,11 @@ We're announcing the GA of **User Groups for Cloudflare Dashboard** and **System
 
 **SCIM User Groups [GA]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.
 
-**Stability & Scale**: 
+**Stability & Scale**:
 These features have undergone extensive testing during the Public Beta period and are now ready for production use across enterprises of all sizes.
 
 :::note
-SCIM Virtual Groups  (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
+SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
 :::
 
 For more info:
diff --git a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
index 78ffc7cb93ea799..3bf99528e750d6f 100644
--- a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
+++ b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
@@ -1,31 +1,38 @@
 ---
 title: Introducing new headers for rate limiting on Cloudflare's API
-description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code. 
+description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code.
 products:
   - fundamentals
 date: 2025-09-03
 ---
-Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available. 
 
-Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this. 
+Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available.
 
-As always, if you need any help with rate limits, please contact Support. 
+Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this.
+
+As always, if you need any help with rate limits, please contact Support.
 
 ### Changes
+
 #### New Headers
 
 **Headers that are always returned:**
+
 - `Ratelimit`: List of service limit items, composed of the limit name, the remaining quota (`r`) and the time next window resets (`t`). For example: `"default";r=50;t=30`
 - `Ratelimit-Policy`: List of quota policy items, composed of the policy name, the total quota (`q`) and the time window the quota applies to (`w`). For example: `"burst";q=100;w=60`
 
 **Returned only when a rate limit has been reached (error code: 429):**
+
 - Retry-After: Number of Seconds until more capacity is available, rounded up
 
 #### SDK Back offs
-- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached. 
+
+- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached.
 
 ### GraphQL and Edge APIs
-These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL. 
+
+These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL.
 
 ### For more information
-* [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
+
+- [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
diff --git a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
index f3c21ce51683451..2d4cd4c94696926 100644
--- a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
+++ b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
@@ -6,7 +6,8 @@ products:
 date: 2025-09-08
 ---
 
-Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future. 
+Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future.
 
 ## For more information
+
 - [Two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
index 7cdd79523b47438..7132df4e0c21e5a 100644
--- a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
+++ b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
@@ -6,7 +6,8 @@ products:
 date: 2025-09-25
 ---
 
-Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address. 
+Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address.
 
 ## For more information
+
 - [Log in to Cloudflare](/fundamentals/user-profiles/login/)
diff --git a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
index ef6b79ccba485df..a55ff67b07c1c01 100644
--- a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
+++ b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
@@ -12,4 +12,4 @@ Users can now specify that they want to retrieve Cloudflare documentation as mar
 curl https://developers.cloudflare.com/workers/ -H 'Accept: text/markdown'  -v
 ```
 
-If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
\ No newline at end of file
+If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
diff --git a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
index c9763acda83fa9f..4d7ebf5cd529a99 100644
--- a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
+++ b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
@@ -15,4 +15,3 @@ Today, we are launching a new user experience which allows users to manage their
 ## For more information
 
 - [Cloudflare dashboard SSO](/fundamentals/manage-members/dashboard-sso/)
-
diff --git a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
index 206794e93f44faa..07fdea6b5a065fe 100644
--- a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
@@ -4,15 +4,15 @@ description: Cloudflare now offers email two-factor authentication to protect yo
 date: 2025-10-30
 ---
 
-Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support. 
+Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support.
 
-Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already. 
+Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already.
 
 You can now enable email 2FA on the Cloudflare dashboard:
 
 1. Go to **Profile** at the top right corner.
 2. Select **Authentication**.
-3. Under **Two-Factor Authentication**, select **Set up**.  
+3. Under **Two-Factor Authentication**, select **Set up**.
 
 ## Sign-in security best practices
 
diff --git a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
index b8e0027220e35a2..612e193af27fb2f 100644
--- a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
@@ -1,5 +1,5 @@
 ---
-title: Revamped Member Management UI 
+title: Revamped Member Management UI
 description: Simplifying the management of users, groups, and permissions within Cloudflare.
 products:
   - fundamentals
@@ -8,7 +8,6 @@ date: 2025-10-30
 
 As Cloudflare's platform has grown, so has the need for precise, role-based access control. We’ve redesigned the Member Management experience in the Dashboard to help administrators more easily discover, assign, and refine permissions for specific principals.
 
-
 ### What's New
 
 **Refreshed member invite flow**
@@ -17,10 +16,10 @@ We overhauled the Invite Members UI to simplify inviting users and assigning per
 
 ![Updated Invite Flow UX](~/assets/images/changelog/fundamentals/2025-10-30-invite-experience.gif)
 
-
 **Refreshed Members Overview Page**
- 
+
 We've updated the Members Overview Page to clearly display:
+
 - Member 2FA status
 - Which members hold Super Admin privileges
 - API access settings per member
@@ -30,12 +29,11 @@ We've updated the Members Overview Page to clearly display:
 
 **New Member Permission Policies Details View**
 
-We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have. 
+We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have.
 
 ![Updated Permission Policies Details Screen](~/assets/images/changelog/fundamentals/2025-10-30-permission-policies-screen.gif)
 
-
-**Improved Member Permission Workflow** 
+**Improved Member Permission Workflow**
 
 We redesigned the permission management experience to make it faster and easier for administrators to review roles and grant access.
 
@@ -43,4 +41,4 @@ We redesigned the permission management experience to make it faster and easier
 
 **Account-scoped Policies Restrictions Relaxed**
 
-Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions. 
\ No newline at end of file
+Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions.
diff --git a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
index 4809af309b7fae0..c83d90c5c82e0db 100644
--- a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
+++ b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
@@ -6,9 +6,10 @@ date: 2026-01-23
 
 ![Screenshot of new 2FA enrollment experience](~/assets/images/changelog/fundamentals/2026-01-23-2fa-interstitial.png)
 
-In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers. 
+In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers.
 
-We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works. 
+We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works.
 
-## For more information 
-* [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
+## For more information
+
+- [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
diff --git a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
index e00305d994595e1..0bd7606af0188e8 100644
--- a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
+++ b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
@@ -8,7 +8,6 @@ date: 2026-02-12
 
 Cloudflare's network now supports real-time content conversion at the source, for enabled zones using [content negotiation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation) headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for `text/markdown` in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
 
-
 Here is a curl example with the `Accept` negotiation header requesting this page from our developer documentation:
 
 ```bash
@@ -39,4 +38,4 @@ ultimately resulting in better results while minimizing token waste.
 ...
 ```
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
\ No newline at end of file
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
diff --git a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
index 33a3ae22e6230f3..69a7003183ac4a6 100644
--- a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
+++ b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
@@ -16,4 +16,4 @@ This release adds the following improvements:
 
 If you haven’t enabled automatic Markdown conversion yet, visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section of the Cloudflare dashboard and enable **Markdown for Agents**.
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
\ No newline at end of file
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
diff --git a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
index e6ad76ed4ec43a0..5ba8aed4decf5c8 100644
--- a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
@@ -57,5 +57,6 @@ curl -s --compressed -H "Accept: application/problem+json" -A "TestAgent/1.0" -H
 ```
 
 References:
+
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
index aa790c1bc84902b..7635eb13215cd99 100644
--- a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
@@ -12,15 +12,15 @@ Cloudflare-generated 1xxx error responses now include a standard `Retry-After` H
 
 Seven retryable error codes now emit `Retry-After`:
 
-| Error code | Retry-After (seconds) | Error name |
-|---|---|---|
-| 1004 | 120 | DNS resolution error |
-| 1005 | 120 | Banned zone |
-| 1015 | 30 | Rate limited |
-| 1033 | 120 | Argo Tunnel error |
-| 1038 | 60 | HTTP headers limit exceeded |
-| 1200 | 60 | Cache connection limit |
-| 1205 | 5 | Too many redirects |
+| Error code | Retry-After (seconds) | Error name                  |
+| ---------- | --------------------- | --------------------------- |
+| 1004       | 120                   | DNS resolution error        |
+| 1005       | 120                   | Banned zone                 |
+| 1015       | 30                    | Rate limited                |
+| 1033       | 120                   | Argo Tunnel error           |
+| 1038       | 60                    | HTTP headers limit exceeded |
+| 1200       | 60                    | Cache connection limit      |
+| 1205       | 5                     | Too many redirects          |
 
 The header value matches the existing `retry_after` body field in JSON and Markdown responses.
 
@@ -39,5 +39,6 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
+
 - [RFC 9110 section 10.2.3 - Retry-After](https://www.rfc-editor.org/rfc/rfc9110#section-10.2.3)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
index 92f5a45e27a8c57..c0c1a7659fedd48 100644
--- a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
+++ b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-18
 ---
 
-Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers. 
+Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers.
 
 Customers can now sync users and group information from Authentik to Cloudflare, apply Permission Policies to those groups, and manage the lifecycle of users & groups directly from your Authentik Identity Provider.
 
diff --git a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
index 115c15516aecbda..48fa5bd55c357ee 100644
--- a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
+++ b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
@@ -17,9 +17,9 @@ Cloudflare dashboard SCIM provisioning operations are now captured in [Audit Log
 | Create SCIM User  | User provisioned from IdP               |
 | Replace SCIM User | User fully replaced (PUT)               |
 | Update SCIM User  | User attributes modified (PATCH)        |
-| Delete SCIM User  | Member deprovisioned                      |
+| Delete SCIM User  | Member deprovisioned                    |
 | Create SCIM Group | Group provisioned from IdP              |
 | Update SCIM Group | Group membership or attributes modified |
-| Delete SCIM Group | Group deprovisioned                           |
+| Delete SCIM Group | Group deprovisioned                     |
 
 For more details, refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/).
diff --git a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
index 66f075b8044732c..99e5c7faac36b0e 100644
--- a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
+++ b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
@@ -18,7 +18,7 @@ We're announcing the public beta of **Organizations** for enterprise customers,
 
 **Centralized Account Management**: At launch, every Organization member has the Organization Super Admin role. Organization Super Admins can invite other users and manage any child account under the Organization implicitly.
 **Shared policies**: Share [WAF](/waf/custom-rules/) or [Gateway](/cloudflare-one/traffic-policies/tiered-policies/organizations/) policies across multiple accounts within your Organization to simplify centralized policy management.
-**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year. 
+**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year.
 
 **Unified analytics**: View, filter, and download aggregate HTTP analytics across all Organization child accounts from a single dashboard for centralized visibility into traffic patterns and security events.
 
diff --git a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
index 4fb052b1583582b..6df437b0b5fe8f2 100644
--- a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
+++ b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
@@ -1,6 +1,6 @@
 ---
 title: API tokens now detectable by secret scanning tools
-description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code. 
+description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code.
 date: 2026-04-10
 ---
 
diff --git a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
index ea662602678945a..b21e3e867f40139 100644
--- a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
+++ b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
@@ -5,29 +5,45 @@ products:
   - fundamentals
 date: 2026-04-14
 ---
+
 OAuth allows third-party applications to access your Cloudflare account on your behalf — like when Wrangler deploys Workers or when monitoring tools read your analytics. You now have **granular control** over which accounts these applications can access, plus the ability to revoke access anytime.
+
 ## What's new
+
 ### Choose which accounts to authorize
+
 When authorizing an OAuth application, you can now **select specific accounts** instead of granting access to all your accounts:
+
 - **Account-by-account selection** — Choose exactly which accounts the application can access
 - **"All accounts" option** — Still available for trusted tools like Wrangler
-This gives you precise control who can access your data.
+  This gives you precise control who can access your data.
+
 ### Clear consent screens
+
 The OAuth consent screen now shows:
+
 - **What the application can access** — Explicit list of permissions being requested
-- **Who created the application** — Application owner and contact information  
+- **Who created the application** — Application owner and contact information
 - **Which accounts you're authorizing** — Checkboxes for account selection
+
 ### Revoke access anytime
+
 Manage authorized OAuth applications from your profile:
+
 - **See all connected apps** — View every OAuth application with access to your accounts
 - **Review permissions and scope** — Check what each application can do and which accounts it can access
 - **Revoke instantly** — Remove access with one click when you no longer need it
-To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
+  To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
+
 ## Why this matters
+
 These updates give you:
+
 - **Granular control** — Authorize apps per-account instead of all-or-nothing
 - **Transparency** — Know exactly what you're authorizing before you consent
 - **Security** — Limit blast radius by restricting access to only necessary accounts
 - **Easy cleanup** — Revoke access when applications are no longer needed
+
 ## Learn more
+
 Read more about these improvements in our blog post: [Improving the OAuth consent experience](https://blog.cloudflare.com/improved-developer-security/#improving-the-oauth-consent-experience).
diff --git a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
index 0bd7547904452c2..02073d22df3580c 100644
--- a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
@@ -50,5 +50,6 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
+
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 5xx error documentation](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
index 521711f9c22d54b..2babbbfb86081cd 100644
--- a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
+++ b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
@@ -11,34 +11,34 @@ You can now navigate, switch context, and take common actions in the Cloudflare
 
 ## Navigate
 
-| Shortcut | Action |
-| --- | --- |
-| `g h` | Go to Home |
-| `g a` | Go to account overview |
-| `g z` | Go to zone overview |
-| `g p` | Go to your profile |
-| `g w` | Go to Workers & Pages |
-| `g o` | Go to Zero Trust |
-| `g b` | Go to billing |
+| Shortcut      | Action                                                 |
+| ------------- | ------------------------------------------------------ |
+| `g h`         | Go to Home                                             |
+| `g a`         | Go to account overview                                 |
+| `g z`         | Go to zone overview                                    |
+| `g p`         | Go to your profile                                     |
+| `g w`         | Go to Workers & Pages                                  |
+| `g o`         | Go to Zero Trust                                       |
+| `g b`         | Go to billing                                          |
 | `g 1` – `g 5` | Go to a recent or pinned item (by position in sidebar) |
-| `t →` | Move to the next tab |
-| `t ←` | Move to the previous tab |
-| `p →` | Move to the next page of a table |
-| `p ←` | Move to the previous page of a table |
+| `t →`         | Move to the next tab                                   |
+| `t ←`         | Move to the previous tab                               |
+| `p →`         | Move to the next page of a table                       |
+| `p ←`         | Move to the previous page of a table                   |
 
 ## Take action
 
-| Shortcut | Action |
-| --- | --- |
-| `/` | Open quick search |
-| `?` | Show keyboard shortcuts |
-| `s a` | Switch account |
-| `s z` | Switch zone |
-| `s .` | Star or unstar the current zone |
-| `p .` | Pin or unpin the current page |
-| `t s` | Toggle the sidebar open or closed |
-| `t m` | Expand or collapse all sidebar menus |
-| `t a` | Toggle Ask AI sidebar |
-| `d .` | Toggle dark mode |
-| `c u` | Copy the current URL |
-| `c d` | Copy a deep link URL |
+| Shortcut | Action                               |
+| -------- | ------------------------------------ |
+| `/`      | Open quick search                    |
+| `?`      | Show keyboard shortcuts              |
+| `s a`    | Switch account                       |
+| `s z`    | Switch zone                          |
+| `s .`    | Star or unstar the current zone      |
+| `p .`    | Pin or unpin the current page        |
+| `t s`    | Toggle the sidebar open or closed    |
+| `t m`    | Expand or collapse all sidebar menus |
+| `t a`    | Toggle Ask AI sidebar                |
+| `d .`    | Toggle dark mode                     |
+| `c u`    | Copy the current URL                 |
+| `c d`    | Copy a deep link URL                 |
diff --git a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
index 6d777cba0965f65..ae01229a4717c46 100644
--- a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
+++ b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
@@ -7,9 +7,9 @@ hidden: false
 date: 2025-07-24
 ---
 
-[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more. 
+[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more.
 
-You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing  _Inspect on all ports_.
+You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing _Inspect on all ports_.
 
 ![HTTP Inspection on all ports setting](~/assets/images/gateway/Gateway-Inspection-all-ports.png)
 
diff --git a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
index 99deeee7c9cf019..85d54d9085242a7 100644
--- a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
+++ b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
@@ -3,15 +3,13 @@ title: Scam domain category introduced under Security Threats
 description: You can now create policies specifically targeting the Scam content
 date: 2025-07-28
 ---
- 
-We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
- 
-**New category added**
 
+We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
 
-| Parent ID | Parent Name           | Category ID | Category Name                 |
-| --------- | --------------------- | ----------- | ----------------------------- |
-| 21        | Security Threats      | 191          | Scam                |
+**New category added**
 
+| Parent ID | Parent Name      | Category ID | Category Name |
+| --------- | ---------------- | ----------- | ------------- |
+| 21        | Security Threats | 191         | Scam          |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
index 295f092f251e8cc..e4f36b80ddf1cbf 100644
--- a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
+++ b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
@@ -3,8 +3,9 @@ title: Google Bard Application replaced by Gemini
 description: The Google Bard application has been fully replaced with Gemini
 date: 2025-07-22
 ---
+
 The **Google Bard** application (ID: 1198) has been deprecated and fully removed from the system. It has been replaced by the **Gemini** application (ID: 1340).
-Any existing Gateway policies that reference the old Google Bard application will no longer function. 
+Any existing Gateway policies that reference the old Google Bard application will no longer function.
 To ensure your policies continue to work as intended, you should update them to use the new Gemini application.
 We recommend replacing all instances of the deprecated Bard application with the new Gemini application in your Gateway policies.
 For more information about application policies, please see the [Cloudflare Gateway documentation](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
index 0583881ed95d8cb..450c765b4b0e122 100644
--- a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
+++ b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
@@ -8,10 +8,10 @@ We have added three new domain categories under the Technology parent category,
 
 **New categories added**
 
-| Parent ID | Parent Name           | Category ID | Category Name                 |
-| --------- | --------------------- | ----------- | ----------------------------- |
-| 26        | Technology            | 194         | Keep Awake Software           |
-| 26        | Technology            | 192         | Remote Access                 |
-| 26        | Technology            | 193         | Shareware/Freeware            |
+| Parent ID | Parent Name | Category ID | Category Name       |
+| --------- | ----------- | ----------- | ------------------- |
+| 26        | Technology  | 194         | Keep Awake Software |
+| 26        | Technology  | 192         | Remote Access       |
+| 26        | Technology  | 193         | Shareware/Freeware  |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
index 6ae683bd7093044..0d4496f7a95d1af 100644
--- a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
+++ b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
@@ -4,14 +4,15 @@ description: We are preparing to remap some existing applications to better refl
 date: 2025-11-06
 ---
 
-We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28). 
+We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28).
 While the new categories are live now, we want to ensure you have ample time to review and adjust any existing rules you have configured against old categories.
 The remapping of existing applications into these new categories will be completed by January 30, 2026.
 This timeline allows you a dedicated period to:
+
 - Review the new category structure.
 - Identify any policies you have that target the older categories.
 - Adjust your rules to reference the new, more precise categories before the old mappings change.
-Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
+  Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
 
 **Applications being remappedd**
 | Application Name | Existing Category | New Category |
@@ -76,5 +77,4 @@ Once the applications have been fully remapped by January 30, 2026, you might ob
 | DHL Express | Shopping | Business |
 | UPS | Shopping | Business |
 
-
 For more information on creating HTTP policies, refer to [Applications and app types](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
index f20f7a3b16f224a..25d0dbe1436d1fa 100644
--- a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
+++ b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
@@ -10,13 +10,13 @@ Gateway [Protocol Detection](/cloudflare-one/traffic-policies/network-policies/p
 
 | Protocol     | Notes                                              |
 | ------------ | -------------------------------------------------- |
-| IMAP         | Internet Message Access Protocol — email retrieval  |
-| POP3         | Post Office Protocol v3 — email retrieval           |
-| SMTP         | Simple Mail Transfer Protocol — email sending       |
-| MYSQL        | MySQL database wire protocol                        |
-| RSYNC-DAEMON | rsync daemon protocol                               |
-| LDAP         | Lightweight Directory Access Protocol               |
-| NTP          | Network Time Protocol                               |
+| IMAP         | Internet Message Access Protocol — email retrieval |
+| POP3         | Post Office Protocol v3 — email retrieval          |
+| SMTP         | Simple Mail Transfer Protocol — email sending      |
+| MYSQL        | MySQL database wire protocol                       |
+| RSYNC-DAEMON | rsync daemon protocol                              |
+| LDAP         | Lightweight Directory Access Protocol              |
+| NTP          | Network Time Protocol                              |
 
 These protocols join the existing set of detected protocols (HTTP, HTTP2, SSH, TLS, DCERPC, MQTT, and TPKT) and can be used with the _Detected Protocol_ selector in [Network policies](/cloudflare-one/traffic-policies/network-policies/) to identify and filter traffic based on the application-layer protocol, without relying on port-based identification.
 
diff --git a/src/content/changelog/gateway/Gateway-application-categories-added.mdx b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
index ec9c5e87eb92aa4..2f049a7fb324a63 100644
--- a/src/content/changelog/gateway/Gateway-application-categories-added.mdx
+++ b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
@@ -4,7 +4,7 @@ description: Manage outbound traffic with more granular application categories
 date: 2025-10-28
 ---
 
-To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product. 
+To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product.
 
 We have added the following categories to provide more precise organization and allow for finer-grained policy creation, designed around how users interact with different types of applications:
 
@@ -18,7 +18,7 @@ We have added the following categories to provide more precise organization and
 - Photography & Graphic Design
 - Travel
 
-The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories. 
+The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories.
 
 The full remapping will be completed by January 30, 2026.
 
diff --git a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
index 3266a97d34dcdcb..05c67dbc7fb82e7 100644
--- a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
+++ b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
@@ -13,13 +13,13 @@ The `localConnectionString` field and `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_ST
 
 ```jsonc
 {
-  "hyperdrive": [
-    {
-      "binding": "HYPERDRIVE",
-      "id": "your-hyperdrive-id",
-      "localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require"
-    }
-  ]
+	"hyperdrive": [
+		{
+			"binding": "HYPERDRIVE",
+			"id": "your-hyperdrive-id",
+			"localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require",
+		},
+	],
 }
 ```
 
diff --git a/src/content/changelog/images/heic-support.mdx b/src/content/changelog/images/heic-support.mdx
index 8e5f655340c4c12..3baf6ce9372089c 100644
--- a/src/content/changelog/images/heic-support.mdx
+++ b/src/content/changelog/images/heic-support.mdx
@@ -3,6 +3,7 @@ title: HEIC support in Cloudflare Images
 description: You can use Images to ingest HEIC images
 date: 2025-07-08
 ---
+
 You can use Images to ingest HEIC images and serve them in supported output formats like AVIF, WebP, JPEG, and PNG.
 
 When inputting a HEIC image, dimension and sizing limits may still apply. Refer to our documentation to see limits for [uploading to Images](/images/storage/upload-images/methods/) or [transforming a remote image](/images/optimization/transformations/overview/).
diff --git a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
index 8124fd2d6475783..6cf9d6cc44b1683 100644
--- a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
+++ b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
@@ -16,5 +16,3 @@ The new hybrid architecture delivers substantial latency reductions throughout E
 
 - **p95 latency**: Reduced from ~150ms to ~50ms (67% decrease)
 - **p99 latency**: Reduced from ~350ms to ~250ms (29% decrease)
-
-
diff --git a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
index 41b68f6e7a4c23d..d1a8fedd27fa065 100644
--- a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
+++ b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
@@ -5,6 +5,7 @@ date: 2025-06-04
 ---
 
 We've made two large changes to load balancing:
+
 - Redesigned the user interface, now centralized at the **account level**.
 - Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot.
 
@@ -15,13 +16,11 @@ This update streamlines how you manage load balancers across multiple zones and
 **Key Enhancements:**
 
 - **Account-Level UI Consolidation:**
-
   - **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level.
 
   - **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution.
 
 - **Private Network Load Balancing:**
-
   - **Secure Internal Application Access:** Create [**Private Load Balancers**](/load-balancing/private-network/) to distribute traffic to applications hosted within your private network, ensuring they are not exposed to the public Internet.
 
   - **WARP & Magic WAN Integration:** Effortlessly direct internal traffic from users connected via Cloudflare WARP or through your Magic WAN infrastructure to the appropriate internal endpoint pools.
diff --git a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
index 3a0234e53c4e96e..62de99fae3dc892 100644
--- a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
+++ b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
@@ -6,4 +6,4 @@ date: 2025-07-09
 
 [Log Explorer](/log-explorer/) customers can now monitor their data ingestion volume to keep track of their billing. Monthly usage is displayed at the top of the [Log Search](/log-explorer/log-search/) and [Manage Datasets](/log-explorer/manage-datasets/) screens in Log Explorer.
 
-![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
\ No newline at end of file
+![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
diff --git a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
index 02585abcdaa5285..c384730c331df3f 100644
--- a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
+++ b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
@@ -6,4 +6,4 @@ date: 2025-08-15
 
 Customers can now rely on Log Explorer to meet their log retention compliance requirements.
 
-Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
\ No newline at end of file
+Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
diff --git a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
index c1d5c1454d91cdf..bd9895c6bf2de02 100644
--- a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
+++ b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
@@ -11,5 +11,3 @@ Create a custom field to log desired header or cookie values into the `http_requ
 ![Edit Custom fields](src/assets/images/changelog/log-explorer/edit-custom-fields.png)
 
 For more details, refer to [Headers and cookies](/log-explorer/log-search/#headers-and-cookies).
-
-
diff --git a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
index 794a2ac99ef2c6c..a75aa1ccc71be40 100644
--- a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
@@ -4,7 +4,7 @@ description: Log Search now lets you pivot directly to related Cloudflare tools
 date: 2025-09-11
 ---
 
-Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation. 
+Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation.
 
 From the `http_requests` or `fw_events` dataset results, right click on an IP Address or JA3 Fingerprint to pivot to the Investigate portal to lookup the reputation of an IP address or JA3 fingerprint.
 
@@ -14,6 +14,6 @@ Easily learn about error codes by linking directly to our documentation from the
 
 ![View documentation](src/assets/images/changelog/log-explorer/view-documentation.png)
 
-From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy. 
+From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy.
 
 ![View policy](src/assets/images/changelog/log-explorer/policyid.png)
diff --git a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
index 915ab5b7a8c0a8a..9747dcb5ea70714 100644
--- a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
@@ -9,6 +9,6 @@ The results table view of **Log Search** has been updated with additional functi
 - Remove/add columns.
 - Resize columns.
 - Sort columns.
-- Copy values from any field. 
+- Copy values from any field.
 
-![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
\ No newline at end of file
+![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
diff --git a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
index 8a5f4b9954eb85f..7fc5df7c52c3f95 100644
--- a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
+++ b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
@@ -6,4 +6,4 @@ date: 2025-11-04
 
 We're excited to announce that Log Explorer users can now cancel queries that are currently running.
 
-This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
\ No newline at end of file
+This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
diff --git a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
index 6808c2b7ad9372e..4abf8c6cf36fdee 100644
--- a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
+++ b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
@@ -8,4 +8,4 @@ We're excited to announce a quality-of-life improvement for Log Explorer users.
 
 Previously, if you were writing a long custom SQL query, the fixed-size window required excessive scrolling to view the full query. This update allows you to easily drag the bottom edge of the query window to make it taller. This means you can view your entire custom query at once, improving the efficiency and experience of writing and debugging complex queries.
 
-To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
\ No newline at end of file
+To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
diff --git a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
index 012bc9566a75154..20d9cb72a336e55 100644
--- a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
@@ -6,4 +6,4 @@ date: 2025-11-13
 
 We've resolved a bug in Log Explorer that caused inconsistencies between the custom SQL date field filters and the date picker dropdown. Previously, users attempting to filter logs based on a custom date field via a SQL query sometimes encountered unexpected results or mismatching dates when using the interactive date picker.
 
-This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
\ No newline at end of file
+This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
diff --git a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
index eaa4f6d50ecf078..b3d870198ed0514 100644
--- a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
@@ -18,7 +18,6 @@ The newly supported datasets include:
 - `Spectrum_events`
 - `Zaraz_events`
 
-
 ## Account Level
 
 - `Audit Logs`
@@ -31,9 +30,8 @@ The newly supported datasets include:
 - `Sinkhole HTTP`
 - `ipsec_logs`
 
-
 :::note
-`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying. 
+`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying.
 
 The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` role for querying.
 :::
@@ -43,4 +41,3 @@ The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` ro
 You can now use Log Explorer to query and filter with each of these datasets. For example, you can identify an IP address exhibiting suspicious behavior in the `FW_event` logs, and then instantly pivot to the `Network Analytics` logs or `Access` logs to see its network-level traffic profile or if it bypassed a corporate policy.
 
 To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/) and the [Cloudflare Logs documentation](/logs/).
-
diff --git a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
index 305f5dc7bb195af..866a7fd1ae4efd5 100644
--- a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
+++ b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
@@ -21,16 +21,16 @@ When configuring a dataset via the dashboard or API, you can define a specific s
 
 ```json
 {
-  "dataset": "firewall_events",
-  "enabled": true,
-  "fields": [
-    "Timestamp",
-    "ClientRequestHost",
-    "ClientIP",
-    "Action",
-    "EdgeResponseStatus",
-    "OriginResponseStatus"
-  ]
+	"dataset": "firewall_events",
+	"enabled": true,
+	"fields": [
+		"Timestamp",
+		"ClientRequestHost",
+		"ClientIP",
+		"Action",
+		"EdgeResponseStatus",
+		"OriginResponseStatus"
+	]
 }
 ```
 
diff --git a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
index 5c89e845304dd52..67a64c6fcf983b4 100644
--- a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
+++ b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
@@ -8,4 +8,4 @@ Cloudflare has introduced new fields to two Gateway-related datasets in Cloudfla
 
 - **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
 
-- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
\ No newline at end of file
+- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
diff --git a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
index 05e75fb1d124a1b..e21ad4b2e7c9787 100644
--- a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
+++ b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
@@ -24,4 +24,3 @@ Cloudflare has added new fields across multiple [Logpush datasets](/logs/logpush
 - **Zero Trust Network Session Logs**: `SNI`.
 
 For the complete field definitions for each dataset, refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/).
-
diff --git a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
index 0bcd5c49fa1c601..f5a502289149705 100644
--- a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
+++ b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
@@ -31,4 +31,4 @@ Pipelines SQL supports string functions, regex, hashing, JSON extraction, timest
 
 ## Get started
 
-To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
\ No newline at end of file
+To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
diff --git a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
index 451556a3ef70408..322bbb2f1f6d38d 100644
--- a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
+++ b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
@@ -7,13 +7,15 @@ date: 2026-04-21
 When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request. With subrequest merging enabled, subrequest data is embedded as a nested array field on the parent log record instead.
 
 ### What's new
+
 - New subrequest_merging field on Logpush jobs — Set "merge_subrequests": true when creating or updating an http_requests Logpush job to enable the feature.
 - New Subrequests log field — When subrequest merging is enabled, a Subrequests field (`array\<object\>`) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.
 
 ### Limitations
+
 - Applies to the http_requests (zone-scoped) dataset only.
 - A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.
 - Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.
 - Subrequests that do not qualify appear as separate log entries — no data is lost.
 - Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.
-- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
\ No newline at end of file
+- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
diff --git a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
index 7513b6b2b18466c..3e32c36dcd09c10 100644
--- a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
+++ b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
@@ -6,4 +6,4 @@ date: 2026-03-24
 
 The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** > **Interconnects**.
 
-Your existing configurations and functionality remain the same.
\ No newline at end of file
+Your existing configurations and functionality remain the same.
diff --git a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
index e11320f25ae558b..5bbd423dd5f10bf 100644
--- a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
+++ b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
@@ -12,4 +12,4 @@ If you are creating a new Pages project, the new V3 build image that includes No
 
 Note that you can always specify a particular version of Node.js or other built-in dependencies by [setting an environment variable](/pages/configuration/build-image/#override-default-versions).
 
-For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
\ No newline at end of file
+For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
diff --git a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
index 21d1fa8ffb558fc..c3385ca2e92c7dd 100644
--- a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
+++ b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
@@ -8,11 +8,12 @@ date: 2025-03-27 12:00:00 UTC
 
 [Queues](/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:
 
-* Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
-* You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
-* Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
+- Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
+- You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
+- Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
 
 To pause a queue using [Wrangler](/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.
+
 ```bash title="Pause and resume a queue"
 $ wrangler queues pause-delivery my-queue
 Pausing message delivery for queue my-queue.
@@ -24,6 +25,7 @@ Resumed message delivery for queue my-queue.
 ```
 
 Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:
+
 ```bash title="Purge a queue"
 $ wrangler queues purge my-queue
 ✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue
diff --git a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
index f8a980ffedaf040..f3d5e6d4def673d 100644
--- a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
+++ b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
@@ -11,13 +11,16 @@ date: 2025-04-17 12:00:00 UTC
 Pull consumers allow you to consume messages over HTTP from any environment—including outside of [Cloudflare Workers](/workers). They’re also useful when you need fine-grained control over how quickly messages are consumed.
 
 To setup a new queue with a pull based consumer using [Wrangler](/workers/wrangler/), run:
+
 ```sh title="Create a queue with a pull based consumer"
 npx wrangler queues create my-queue
 npx wrangler queues consumer http add my-queue
 ```
+
 You can also configure a pull consumer using the [REST API](/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.
 
 Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:
+
 ```bash title="Pull messages from a queue"
 curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" \
 --header "Authorization: Bearer ${API_TOKEN}" \
diff --git a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
index c7afb7767b23bb4..7cec3511f215302 100644
--- a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
+++ b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
@@ -19,4 +19,4 @@ curl "https://api.cloudflare.com/client/v4/accounts/<account_id>/queues/<queue_i
 
 You can also use our [SDKs](/fundamentals/api/reference/sdks/) for TypeScript, Python, and Go.
 
-To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
\ No newline at end of file
+To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
diff --git a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
index cd3df4c25c12a32..2ad33c340181762 100644
--- a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
+++ b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
@@ -22,21 +22,21 @@ An event is a structured record of something happening in your Cloudflare accoun
 
 ```json title="Example R2 bucket created event"
 {
-  "type": "cf.r2.bucket.created",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "location": "WNAM"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventTimestamp": "2025-07-28T10:30:00Z"
-  }
+	"type": "cf.r2.bucket.created",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"location": "WNAM"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventTimestamp": "2025-07-28T10:30:00Z"
+	}
 }
 ```
 
 Current [event sources](/queues/event-subscriptions/events-schemas/) include [R2](/r2/), [Workers KV](/kv/), [Workers AI](/workers-ai/), [Workers Builds](/workers/ci-cd/builds/), [Vectorize](/vectorize/), [Super Slurper](/r2/data-migration/super-slurper/), and [Workflows](/workflows/). More sources and events are on the way.
 
-For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
\ No newline at end of file
+For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
diff --git a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
index 4e3338c452ffb31..965d8f2e1ebbc40 100644
--- a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
+++ b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
@@ -7,7 +7,7 @@ products:
 hidden: false
 ---
 
-import { LinkCard} from "~/components";
+import { LinkCard } from "~/components";
 
 Today, we're launching the **open beta** for [R2 SQL](/r2-sql/): A serverless, distributed query engine that can efficiently analyze petabytes of data in [Apache Iceberg](https://iceberg.apache.org/) tables managed by [R2 Data Catalog](/r2/data-catalog).
 
diff --git a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
index 6ebf2f9f66bcf2e..55b2b18066b5d26 100644
--- a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
+++ b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
@@ -8,7 +8,6 @@ date: 2026-03-23
 
 [R2 SQL](/r2-sql/) now supports an expanded SQL grammar so you can write richer analytical queries without exporting data. This release adds CASE expressions, column aliases, arithmetic in clauses, 163 scalar functions, 33 aggregate functions, EXPLAIN, Common Table Expressions (CTEs),and full struct/array/map access. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying [Apache Iceberg](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](/r2/data-catalog/). This page documents the supported SQL syntax.
 
-
 ## Highlights
 
 - **Column aliases** — `SELECT col AS alias` now works in all clauses
diff --git a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
index f6fc972ca48a3f5..8be0bd3a266e62c 100644
--- a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
+++ b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
@@ -20,6 +20,7 @@ SELECT
 FROM my_namespace.sales_data
 WHERE json_contains(doc, 'email')
 ```
+
 For a full list of available functions, refer to [JSON functions](/r2-sql/sql-reference/scalar-functions/#json-functions).
 
 `EXPLAIN FORMAT JSON` returns query execution plans as structured JSON for programmatic analysis and observability integrations:
@@ -66,6 +67,7 @@ npx wrangler r2 sql query "${WAREHOUSE}" "EXPLAIN FORMAT JSON SELECT * FROM logp
 │ }                                    │
 └──────────────────────────────────────┘
 ```
+
 For more details, refer to [EXPLAIN](/r2-sql/sql-reference/#explain).
 
 Unpartitioned Iceberg tables can now be queried directly, which is useful for smaller datasets or data without natural time dimensions. For tables with more than 1000 files, partitioning is still recommended for better performance.
diff --git a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
index 3a0934b0df07041..73516e563584422 100644
--- a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
+++ b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
@@ -35,4 +35,4 @@ For the `summary` and `timeseries_groups` endpoints, the following dimensions ar
 - `tld`: Top-level domain for DNS names found in certificates SANs
 - `validation_level`: [Validation level](https://www.cloudflare.com/learning/ssl/types-of-ssl-certificates/)
 
-Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
\ No newline at end of file
+Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
diff --git a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
index 2204d6097ae38bf..702f6495af2db32 100644
--- a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
+++ b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
@@ -18,4 +18,4 @@ All `summary` and `timeseries_groups` endpoints in [`HTTP`](/api/resources/radar
 
 A new filter `geoId` was also added to all endpoints in [`HTTP`](/api/resources/radar/subresources/http/) and [`NetFlows`](/api/resources/radar/subresources/netflows/), allowing filtering by a specific administrative division.
 
-Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
\ No newline at end of file
+Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
diff --git a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
index 3058add7fdc87a1..1da325fa4aeeaef 100644
--- a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
+++ b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
@@ -34,4 +34,4 @@ On AS routing pages, the connectivity table now includes checkmarks for ASPA-ver
 
 ![Screenshot of the ASPA changes timeline on an AS routing page](~/assets/images/radar/aspa-asn-timeline.png)
 
-Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
\ No newline at end of file
+Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
diff --git a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
index b2c0e9bbf120e31..190b32137ec4b34 100644
--- a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
+++ b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
@@ -34,4 +34,4 @@ The [IP address space](https://radar.cloudflare.com/routing) chart now displays
 
 ![Screenshot of the IPv4 and IPv6 combined IP space chart](~/assets/images/radar/combined-ipv4-ipv6-space.png)
 
-Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
\ No newline at end of file
+Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
diff --git a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
new file mode 100644
index 000000000000000..b8b628aa4258d7d
--- /dev/null
+++ b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
@@ -0,0 +1,36 @@
+---
+title: RealtimeKit track recording for specific participant audio tracks
+description: You can now record specific participant audio tracks in RealtimeKit with the new track recording feature.
+products:
+  - realtime
+date: 2026-05-28
+---
+
+You can now record specific participant audio tracks in RealtimeKit with the new [track recording](/realtime/realtimekit/recording-guide/track-recording/) feature. Track recording creates separate WebM files for each participant instead of one composite meeting recording, which is useful for post-processing, transcription, and regulated or content-sensitive workflows where you need speaker-level control over what you store.
+
+To record specific participants, pass `user_ids` when starting a track recording:
+
+```bash
+curl --request POST \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+  "user_ids": ["user-123", "user-456"]
+}'
+```
+
+If you do not provide `user_ids`, RealtimeKit records all participant audio tracks as separate WebM files by default.
+
+To use `user_ids` for selective track recording, upgrade to the following minimum SDK versions:
+
+- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
+- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
+- Android Core or iOS Core: version `2.0.0` or later
+- Android UI Kit or iOS UI Kit: version `1.1.0` or later
+
+RealtimeKit provides SDKs and UI components so that you can build your own meeting experience on [Cloudflare's global WebRTC infrastructure](/realtime/). Teams today build products ranging from telehealth to education companies on RealtimeKit for global audiences. You can get started today with the [RealtimeKit quickstart](/realtime/realtimekit/quickstart/) or take a look at the [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
+
+- [Track recording docs](/realtime/realtimekit/recording-guide/track-recording/)
+- [Recording overview](/realtime/realtimekit/recording-guide/)
diff --git a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
index a57aa1f4b10d63e..4bdd9ba554b4731 100644
--- a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
+++ b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
@@ -10,6 +10,7 @@ Administrators can now automatically escalate the risk score of a user if their
 
 New risk behaviors
 The following risk scoring behaviors are now available:
+
 - CrowdStrike low device score: Automatically increases a user's risk score when the connected device reports a "Low" score from CrowdStrike.
 - CrowdStrike medium device score: Automatically increases a user's risk score when the connected device reports a "Medium" score from CrowdStrike.
 
diff --git a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
index 629804f5f46a6f4..1ade4db9cf454f6 100644
--- a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
+++ b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
@@ -12,10 +12,10 @@ Cloudflare now provides two new request fields in the Ruleset engine that let yo
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
-| `cf.edge.client_tcp` | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC. |
-| `cf.timings.client_tcp_rtt_msec` | Number | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
+| Field                            | Type    | Description                                                                                                                                                          |
+| -------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.edge.client_tcp`             | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC.                                                        |
+| `cf.timings.client_tcp_rtt_msec` | Number  | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
 
 Example filter expression:
 
diff --git a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
index 97bc5ce82abd556..21cdd6b6e931809 100644
--- a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
+++ b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
@@ -10,8 +10,8 @@ You can use this field to build rules that target traffic based on geographic ma
 
 ### Field details
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field               | Type           | Description                                                                                                                   |
+| ------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | `ip.src.metro_code` | String \| null | The metro code (DMA) of the incoming request's IP address. Returns the designated market area code for the client's location. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
index 9fa9ac345fef774..598cf65b45365a7 100644
--- a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
+++ b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
@@ -12,12 +12,12 @@ Cloudflare Rulesets now include new functions that enable advanced expression lo
 
 ### New functions
 
-| Function | Description |
-| --- | --- |
-| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter. |
-| `join(array, delimiter)` | Joins an array of strings into a single string using the specified delimiter. |
-| `has_key(map, key)` | Returns `true` if the specified key exists in the map. |
-| `has_value(map, value)` | Returns `true` if the specified value exists in the map. |
+| Function                   | Description                                                                   |
+| -------------------------- | ----------------------------------------------------------------------------- |
+| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter.       |
+| `join(array, delimiter)`   | Joins an array of strings into a single string using the specified delimiter. |
+| `has_key(map, key)`        | Returns `true` if the specified key exists in the map.                        |
+| `has_value(map, value)`    | Returns `true` if the specified value exists in the map.                      |
 
 ---
 
diff --git a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
index 9e980cd5968d3b0..5dcd031a6e4ba0b 100644
--- a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
+++ b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
@@ -10,20 +10,20 @@ You can now control how Cloudflare buffers HTTP request and response bodies usin
 
 Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:
 
-| Mode | Behavior |
-| --- | --- |
+| Mode                   | Behavior                                                                                                      |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------- |
 | **Standard** (default) | Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management. |
-| **Full** | Buffers the entire request body before sending to origin. |
-| **None** | No buffering — the request body streams directly to origin without inspection. |
+| **Full**               | Buffers the entire request body before sending to origin.                                                     |
+| **None**               | No buffering — the request body streams directly to origin without inspection.                                |
 
 ### Response body buffering
 
 Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:
 
-| Mode | Behavior |
-| --- | --- |
-| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality. |
-| **None** | No buffering — the response body streams directly to the client without inspection. |
+| Mode                   | Behavior                                                                            |
+| ---------------------- | ----------------------------------------------------------------------------------- |
+| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality.     |
+| **None**               | No buffering — the response body streams directly to the client without inspection. |
 
 :::caution
 Setting body buffering to **None** may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.
@@ -33,11 +33,11 @@ Setting body buffering to **None** may break security functionality that require
 
 ```json
 {
-  "action": "set_config",
-  "action_parameters": {
-    "request_body_buffering": "standard",
-    "response_body_buffering": "none"
-  }
+	"action": "set_config",
+	"action_parameters": {
+		"request_body_buffering": "standard",
+		"response_body_buffering": "none"
+	}
 }
 ```
 
diff --git a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
index 52e81f07114dcef..04fd03621cb1999 100644
--- a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
+++ b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
@@ -10,8 +10,8 @@ You can use this field to identify slow Worker executions, detect performance re
 
 ### Field details
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field                    | Type    | Description                                                                                         |
+| ------------------------ | ------- | --------------------------------------------------------------------------------------------------- |
 | `cf.timings.worker_msec` | Integer | The time spent executing a Cloudflare Worker in milliseconds. Returns `0` if no Worker was invoked. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
index f2a0c12b6257543..c2584a81e336dae 100644
--- a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
@@ -43,6 +43,6 @@ You should ensure that `Client-Cert` and `Client-Cert-Chain` headers received by
 
 - **If you use WAF custom rules to block requests with invalid mTLS connections:** The transform rule is sufficient. For all requests that reach your origin server, the rule will overwrite any existing `Client-Cert` and `Client-Cert-Chain` headers.
 - **If you do not enforce mTLS at the WAF:** Add another transform rule that removes any incoming `Client-Cert` and `Client-Cert-Chain` headers from all requests (use expression `true`), ordered before the rule above. This ensures your origin server cannot receive client-supplied values for these HTTP headers.
-:::
+  :::
 
 For more information, refer to [Mutual TLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/), [Request Header Transform Rules](/rules/transform/request-header-modification/), and the [fields reference](/ruleset-engine/rules-language/fields/reference/).
diff --git a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
index 2954caaf3ad34d3..92228ab4dd7a5fd 100644
--- a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,10 +10,10 @@ Previously, QUIC RTT and delivery rate data was only available via the `Server-T
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field                             | Type    | Description                                                                                                                                                               |
+| --------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cf.timings.client_quic_rtt_msec` | Integer | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only populated for QUIC (HTTP/3) connections. Returns `0` for TCP connections. |
-| `cf.edge.l4.delivery_rate` | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request. |
+| `cf.edge.l4.delivery_rate`        | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request.             |
 
 ### Example: Route slow connections to a lightweight origin
 
@@ -27,9 +27,9 @@ cf.timings.client_tcp_rtt_msec > 200 or cf.timings.client_quic_rtt_msec > 200
 
 **Header modifications:**
 
-| Operation | Header name | Value |
-| --- | --- | --- |
-| Set | `X-High-Latency` | `true` |
+| Operation | Header name      | Value  |
+| --------- | ---------------- | ------ |
+| Set       | `X-High-Latency` | `true` |
 
 ### Example: Match low-bandwidth connections
 
diff --git a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
index 9ee69fcc0ccb9c9..89121e503ad9af2 100644
--- a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
@@ -21,6 +21,7 @@ Please ensure you read through the list of changes below before moving to this v
 ### Breaking Changes
 
 #### Addressing - Parameter Requirements Changed
+
 - `BGPPrefixCreateParams.cidr`: optional → **required**
 - `PrefixCreateParams.asn`: `number | null` → `number`
 - `PrefixCreateParams.loa_document_id`: required → **optional**
@@ -28,21 +29,26 @@ Please ensure you read through the list of changes below before moving to this v
 - `ServiceBindingCreateParams.service_id`: optional → **required**
 
 #### API Gateway
+
 - `ConfigurationUpdateResponse` removed
 - `PublicSchema` → `OldPublicSchema`
 - `SchemaUpload` → `UserSchemaCreateResponse`
 - `ConfigurationUpdateParams.properties` removed; use `normalize`
 
 #### CloudforceOne - Response Type Changes
+
 - `ThreatEventBulkCreateResponse`: `number` → complex object with counts and errors
 
 #### D1 Database - Query Parameters
+
 - `DatabaseQueryParams`: simple interface → union type (`D1SingleQuery | MultipleQueries`)
 - `DatabaseRawParams`: same change
 - Supports batch queries via `batch` array
 
 #### DNS Records - Type Renames (21 types)
+
 All record type interfaces renamed from `*Record` to short names:
+
 - `RecordResponse.ARecord` → `RecordResponse.A`
 - `RecordResponse.AAAARecord` → `RecordResponse.AAAA`
 - `RecordResponse.CNAMERecord` → `RecordResponse.CNAME`
@@ -66,52 +72,64 @@ All record type interfaces renamed from `*Record` to short names:
 - `RecordResponse.OpenpgpkeyRecord` → `RecordResponse.Openpgpkey`
 
 #### IAM Resource Groups
+
 - `ResourceGroupCreateResponse.scope`: optional single → **required array**
 - `ResourceGroupCreateResponse.id`: optional → **required**
 
 #### Origin CA Certificates - Parameter Requirements Changed
+
 - `OriginCACertificateCreateParams.csr`: optional → **required**
 - `OriginCACertificateCreateParams.hostnames`: optional → **required**
 - `OriginCACertificateCreateParams.request_type`: optional → **required**
 
 #### Pages
+
 - Renamed: `DeploymentsSinglePage` → `DeploymentListResponsesV4PagePaginationArray`
 - Domain response fields: many optional → **required**
 
 #### Pipelines - v0 to v1 Migration
+
 - Entire v0 API deprecated; use v1 methods (`createV1`, `listV1`, etc.)
 - New sub-resources: `Sinks`, `Streams`
 
 #### R2
+
 - `EventNotificationUpdateParams.rules`: optional → **required**
 - Super Slurper: `bucket`, `secret` now required in source params
 
 #### Radar
+
 - `dataSource`: `string` → typed enum (23 values)
 - `eventType`: `string` → typed enum (6 values)
 - V2 methods require `dimension` parameter (breaking signature change)
 
 #### Resource Sharing
+
 - Removed: `status_message` field from all recipient response types
 
 #### Schema Validation
+
 - Consolidated `SchemaCreateResponse`, `SchemaListResponse`, `SchemaEditResponse`, `SchemaGetResponse` → `PublicSchema`
 - Renamed: `SchemaListResponsesV4PagePaginationArray` → `PublicSchemasV4PagePaginationArray`
 
 #### Spectrum
+
 - Renamed union members: `AppListResponse.UnionMember0` → `SpectrumConfigAppConfig`
 - Renamed union members: `AppListResponse.UnionMember1` → `SpectrumConfigPaygoAppConfig`
 
 #### Workers
+
 - Removed: `WorkersBindingKindTailConsumer` type (all occurrences)
 - Renamed: `ScriptsSinglePage` → `ScriptListResponsesSinglePage`
 - Removed: `DeploymentsSinglePage`
 
 #### Zero-Trust DLP
+
 - `datasets.create()`, `update()`, `get()` return types changed
 - `PredefinedGetResponse` union members renamed to `UnionMember0-5`
 
 #### Zero-Trust Tunnels
+
 - Removed: `CloudflaredCreateResponse`, `CloudflaredListResponse`, `CloudflaredDeleteResponse`, `CloudflaredEditResponse`, `CloudflaredGetResponse`
 - Removed: `CloudflaredListResponsesV4PagePaginationArray`
 
@@ -120,25 +138,30 @@ All record type interfaces renamed from `*Record` to short names:
 ### Features
 
 #### Abuse Reports (`client.abuseReports`)
+
 - **Reports**: `create`, `list`, `get`
 - **Mitigations**: sub-resource for abuse mitigations
 
 #### AI Search (`client.aisearch`)
+
 - **Instances**: `create`, `update`, `list`, `delete`, `read`, `stats`
 - **Items**: `list`, `get`
 - **Jobs**: `create`, `list`, `get`, `logs`
 - **Tokens**: `create`, `update`, `list`, `delete`, `read`
 
 #### Connectivity (`client.connectivity`)
+
 - **Directory Services**: `create`, `update`, `list`, `delete`, `get`
 - Supports IPv4, IPv6, dual-stack, and hostname configurations
 
 #### Organizations (`client.organizations`)
+
 - **Organizations**: `create`, `update`, `list`, `delete`, `get`
 - **OrganizationProfile**: `update`, `get`
 - Hierarchical organization support with parent/child relationships
 
 #### R2 Data Catalog (`client.r2DataCatalog`)
+
 - **Catalog**: `list`, `enable`, `disable`, `get`
 - **Credentials**: `create`
 - **MaintenanceConfigs**: `update`, `get`
@@ -147,6 +170,7 @@ All record type interfaces renamed from `*Record` to short names:
 - Apache Iceberg integration
 
 #### Realtime Kit (`client.realtimeKit`)
+
 - **Apps**: `get`, `post`
 - **Meetings**: `create`, `get`, participant management
 - **Livestreams**: 10+ methods for streaming
@@ -157,52 +181,66 @@ All record type interfaces renamed from `*Record` to short names:
 - **Analytics**: organization analytics
 
 #### Token Validation (`client.tokenValidation`)
+
 - **Configuration**: `create`, `list`, `delete`, `edit`, `get`
 - **Credentials**: `update`
 - **Rules**: `create`, `list`, `delete`, `bulkCreate`, `bulkEdit`, `edit`, `get`
 - JWT validation with RS256/384/512, PS256/384/512, ES256, ES384
 
 #### Alerting Silences (`client.alerting.silences`)
+
 - `create`, `update`, `list`, `delete`, `get`
 
 #### IAM SSO (`client.iam.sso`)
+
 - `create`, `update`, `list`, `delete`, `get`, `beginVerification`
 
 #### Pipelines v1 (`client.pipelines`)
+
 - **Sinks**: `create`, `list`, `delete`, `get`
 - **Streams**: `create`, `update`, `list`, `delete`, `get`
 
 #### Zero-Trust AI Controls / MCP (`client.zeroTrust.access.aiControls.mcp`)
+
 - **Portals**: `create`, `update`, `list`, `delete`, `read`
 - **Servers**: `create`, `update`, `list`, `delete`, `read`, `sync`
 
 #### Accounts
+
 - `managed_by` field with `parent_org_id`, `parent_org_name`
 
 #### Addressing LOA Documents
+
 - `auto_generated` field on `LOADocumentCreateResponse`
 
 #### Addressing Prefixes
+
 - `delegate_loa_creation`, `irr_validation_state`, `ownership_validation_state`, `ownership_validation_token`, `rpki_validation_state`
 
 #### AI
+
 - Added `toMarkdown.supported()` method to get all supported conversion formats
 
 #### AI Gateway
+
 - `zdr` field added to all responses and params
 
 #### Alerting
+
 - New alert type: `abuse_report_alert`
 - `type` field added to PolicyFilter
 
 #### Browser Rendering
+
 - `ContentCreateParams`: refined to discriminated union (`Variant0 | Variant1`)
 - Split into URL-based and HTML-based parameter variants for better type safety
 
 #### Client Certificates
+
 - `reactivate` parameter in edit
 
 #### CloudforceOne
+
 - `ThreatEventCreateParams.indicatorType`: required → optional
 - `hasChildren` field added to all threat event response types
 - `datasetIds` query parameter on `AttackerListParams`, `CategoryListParams`, `TargetIndustryListParams`
@@ -213,56 +251,69 @@ All record type interfaces renamed from `*Record` to short names:
 - `createdAt`, `datasetId` fields on `ThreatEventEditParams`
 
 #### Content Scanning
+
 - Added `create()`, `update()`, `get()` methods
 
 #### Custom Pages
+
 - New page types: `basic_challenge`, `under_attack`, `waf_challenge`
 
 #### D1
+
 - `served_by_colo` - colo that handled query
 - `jurisdiction` - `'eu' | 'fedramp'`
 - **Time Travel** (`client.d1.database.timeTravel`): `getBookmark()`, `restore()` - point-in-time recovery
 
 #### Email Security
+
 - New fields on `InvestigateListResponse`/`InvestigateGetResponse`: `envelope_from`, `envelope_to`, `postfix_id_outbound`, `replyto`
 - New detection classification: `'outbound_ndr'`
 - Enhanced `Finding` interface with `attachment`, `detection`, `field`, `portion`, `reason`, `score`
 - Added `cursor` query parameter to `InvestigateListParams`
 
 #### Gateway Lists
+
 - New list types: `CATEGORY`, `LOCATION`, `DEVICE`
 
 #### Intel
+
 - New issue type: `'configuration_suggestion'`
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Leaked Credential Checks
+
 - Added `detections.get()` method
 
 #### Logpush
+
 - New datasets: `dex_application_tests`, `dex_device_state_events`, `ipsec_logs`, `warp_config_changes`, `warp_toggle_changes`
 
 #### Load Balancers
+
 - `Monitor.port`: `number` → `number | null`
 - `Pool.load_shedding`: `LoadShedding` → `LoadShedding | null`
 - `Pool.origin_steering`: `OriginSteering` → `OriginSteering | null`
 
 #### Magic Transit
+
 - `license_key` field on connectors
 - `provision_license` parameter for auto-provisioning
 - IPSec: `custom_remote_identities` with FQDN support
 - Snapshots: Bond interface, `probed_mtu` field
 
 #### Pages
+
 - New response types: `ProjectCreateResponse`, `ProjectListResponse`, `ProjectEditResponse`, `ProjectGetResponse`
 - Deployment methods return specific response types instead of generic `Deployment`
 
 #### Queues
+
 - Added `subscriptions.get()` method
 - Enhanced `SubscriptionGetResponse` with typed event source interfaces
 - New event source types: Images, KV, R2, Vectorize, Workers AI, Workers Builds, Workflows
 
 #### R2
+
 - Sippy: new provider `s3` (S3-compatible endpoints)
 - Sippy: `bucketUrl` field for S3-compatible sources
 - Super Slurper: `keys` field on source response schemas (specify specific keys to migrate)
@@ -270,32 +321,41 @@ All record type interfaces renamed from `*Record` to short names:
 - Super Slurper: `region` field on S3 source params
 
 #### Radar
+
 - Added `geolocations.list()`, `geolocations.get()` methods
 - Added V2 dimension-based methods (`summaryV2`, `timeseriesGroupsV2`) to radar sub-resources
 
 #### Resource Sharing
+
 - Added `terminal` boolean field to Resource Error interfaces
 
 #### Rules
+
 - Added `id` field to `ItemDeleteParams.Item`
 
 #### Rulesets
+
 - New buffering fields on `SetConfigRule`: `request_body_buffering`, `response_body_buffering`
 
 #### Secrets Store
+
 - New scopes: `'dex'`, `'access'` (in addition to `'workers'`, `'ai_gateway'`)
 
 #### SSL Certificate Packs
+
 - Response types now proper interfaces (was `unknown`)
 - Fields now required: `id`, `certificates`, `hosts`, `status`, `type`
 
 #### Security Center
+
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Shared Types
+
 - Added: `CloudflareTunnelsV4PagePaginationArray` pagination class
 
 #### Workers
+
 - Added `subdomains.delete()` method
 - `Worker.references` - track external dependencies (domains, Durable Objects, queues)
 - `Worker.startup_time_ms` - startup timing
@@ -306,36 +366,44 @@ All record type interfaces renamed from `*Record` to short names:
 - Telemetry: `traces` field, `$containers` event info, `durableObjectId`, `transactionName`, `abr_level` fields
 
 #### Workers for Platforms
+
 - `ScriptUpdateResponse`: new fields `entry_point`, `observability`, `tag`, `tags`
 - `placement` field now union of 4 variants (smart mode, region, hostname, host)
 - `tags`, `tail_consumers` now nullable
 - `TagUpdateParams.body` now accepts `null`
 
 #### Workflows
+
 - `instance_retention`: `unknown` → typed `InstanceRetention` interface with `error_retention`, `success_retention`
 - New status option: `'restart'` added to `StatusEditParams.status`
 
 #### Zero-Trust Devices
+
 - External emergency disconnect settings (4 new fields)
 - `antivirus` device posture check type
 - `os_version_extra` documentation improvements
 
 #### Zones
+
 - New response types: `SubscriptionCreateResponse`, `SubscriptionUpdateResponse`, `SubscriptionGetResponse`
 
 #### Zero-Trust Access Applications
+
 - New `ApplicationType` values: `'mcp'`, `'mcp_portal'`, `'proxy_endpoint'`
 - New destination type: `ViaMcpServerPortalDestination` for MCP server access
 
 #### Zero-Trust Gateway
+
 - Added `rules.listTenant()` method
 
 #### Zero-Trust Gateway - Proxy Endpoints
+
 - `ProxyEndpoint`: interface → discriminated union (`ZeroTrustGatewayProxyEndpointIP | ZeroTrustGatewayProxyEndpointIdentity`)
 - `ProxyEndpointCreateParams`: interface → union type
 - Added `kind` field: `'ip' | 'identity'`
 
 #### Zero-Trust Tunnels
+
 - `WARPConnector*Response`: union type → interface
 
 ---
@@ -371,4 +439,4 @@ All record type interfaces renamed from `*Record` to short names:
 - Added deprecation notices with migration paths
 - **api_gateway:** deprecate API Shield Schema Validation resources ([8a4b20f](https://github.com/cloudflare/cloudflare-typescript/commit/8a4b20f7a572422f74179fbdb4f1c4fb555e3e40))
 - Improved JSDoc examples across all resources
-- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
\ No newline at end of file
+- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
diff --git a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
index 4637fe2ecd6fe2e..7b6922947ee7f2c 100644
--- a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
@@ -98,46 +98,57 @@ will help you understand any down or upstream issues it may cause to your enviro
 ### New Endpoints (Existing Resources)
 
 #### `acm.totaltls`
+
 - `edit()`
 - `update()`
 
 #### `cloudforceone.threatevents`
+
 - `list()`
 
 #### `contentscanning`
+
 - `create()`
 - `get()`
 - `update()`
 
 #### `dns.records`
+
 - `scan_list()`
 - `scan_review()`
 - `scan_trigger()`
 
 #### `intel.indicatorfeeds`
+
 - `create()`
 - `delete()`
 - `list()`
 
 #### `leakedcredentialchecks.detections`
+
 - `get()`
 
 #### `queues.consumers`
+
 - `list()`
 
 #### `radar.ai`
+
 - `summary()`
 - `timeseries()`
 - `timeseries_groups()`
 
 #### `radar.bgp`
+
 - `changes()`
 - `snapshot()`
 
 #### `workers.subdomains`
+
 - `delete()`
 
 #### `zerotrust.networks`
+
 - `create()`
 - `delete()`
 - `edit()`
@@ -164,4 +175,4 @@ will help you understand any down or upstream issues it may cause to your enviro
 - **Discriminated unions**: Correctly handle nested discriminated unions in response parsing
 - **Extra field types**: Parse extra field types correctly
 - **Empty metadata**: Ignore empty metadata fields during parsing
-- **Singularization rules**: Update resource name singularization rules for better consistency
\ No newline at end of file
+- **Singularization rules**: Update resource name singularization rules for better consistency
diff --git a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
index 80b92a2e38719b4..01d745a7853300f 100644
--- a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
+++ b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
@@ -1,16 +1,16 @@
-
 ---
 title: New APIs for Brand Protection setup
 description: You can now use the Brand Protection API endpoints to manage your Brand Protection queries
 date: 2025-07-18
 ---
- 
+
 The Brand Protection API is now available, allowing users to create new queries and delete existing ones, fetch matches and more!
- 
+
 What you can do:
-- **create new string or logo query** 
-- **delete string or logo queries** 
-- **download matches for both logo and string queries** 
-- **read matches for both logo and string queries** 
+
+- **create new string or logo query**
+- **delete string or logo queries**
+- **download matches for both logo and string queries**
+- **read matches for both logo and string queries**
 
 Ready to start? Check out the [Brand Protection API](/api/resources/brand_protection/) in our documentation.
diff --git a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
index a8da24443aa2244..58288565e961039 100644
--- a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
+++ b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
@@ -4,7 +4,7 @@ description: The Requests for Information (RFI) dashboard now shows the number o
 date: 2025-10-27
 ---
 
-The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted. 
+The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted.
 
 ![Cloudforce One RFI tokens](~/assets/images/changelog/security-center/2025-10-24RFITokens.png)
 
diff --git a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
index 5c14e85f93430d3..07257c943d54312 100644
--- a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
+++ b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
@@ -1,9 +1,9 @@
 ---
 title: Report logo misuse to Cloudflare directly from the Brand Protection dashboard
-description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network 
+description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network
 date: 2025-10-31
 ---
 
 The Brand Protection logo query dashboard now allows you to use the **Report to Cloudflare** button to submit an Abuse report directly from the Brand Protection logo queries dashboard. While you could previously report new domains that were impersonating your brand before, now you can do the same for websites found to be using your logo without your permission. The abuse reports will be prefilled and you will only need to validate a few fields before you can click the submit button, after which our team process your request.
 
-Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/). 
+Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/).
diff --git a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
index 9f9d5dd72cde73f..fcd53972aec849f 100644
--- a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
+++ b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
@@ -4,7 +4,7 @@ description: Threat events users can now access threat insights curated by our t
 date: 2025-11-21
 ---
 
-The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity. 
-Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.  
+The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity.
+Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.
 
-For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events). 
+For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events).
diff --git a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
index 1dad1d621eb3f74..f6b64dc1ba68722 100644
--- a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
+++ b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
@@ -9,13 +9,13 @@ This update streamlines how security analysts can share findings with stakeholde
 
 **Key Benefits:**
 
-* Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
-* Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
+- Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
+- Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
 
 **What’s new:**
 
-* **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
-* **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
+- **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
+- **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
 
 To get started with the URL Scanner and explore our reporting capabilities, visit the [URL Scanner API documentation](https://developers.cloudflare.com/api/resources/url_scanner/).
 
diff --git a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
index e0dd22e2c84e189..eff63f778930ece 100644
--- a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
+++ b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
@@ -3,6 +3,7 @@ title: Cloudforce One Threat events graphs are now visible in the dashboard
 description: Trace attack flows with Sankey diagrams and analyze dataset distribution over time
 date: 2026-02-19
 ---
+
 We have introduced dynamic visualizations to the Threat Events dashboard to help you better understand the threat landscape and identify emerging patterns at a glance.
 
 What's new:
diff --git a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
index 5260cc6ad7bf605..4a28f773e0eeeac 100644
--- a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
+++ b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
@@ -9,7 +9,8 @@ date: 2026-02-23
 ## Why this matters
 
 Threat intelligence is most effective when it is personalized. Previously, analysts had to manually re-apply complex filters (like combining specific industry datasets with geographic origins) every time they logged in. This update provides material value by:
-* Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
-* Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
+
+- Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
+- Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
 
 Cloudforce One subscribers can start saving their custom views now in [Application Security > Threat Intelligence > Threat Events](https://dash.cloudflare.com/?to=/:account/security-center/threat-intelligence/threat-events).
diff --git a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
index 14417dfa3c757dd..14c2ac824145ccc 100644
--- a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
+++ b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
@@ -3,25 +3,25 @@ title: Real-time alerts and daily digests for Threat Events
 description: You can now subscribe to automated notifications for your saved views in Threat Events
 date: 2026-04-08
 ---
- 
+
 You can now automate your threat monitoring by setting up custom alerts in your saved views. Instead of manually checking the dashboard for updates, you can subscribe to notifications that trigger whenever new data matches your specific filter sets, like new activity associated to a particular threat actor or spikes in activity within your industry.
- 
+
 ### Stay ahead of emerging threats
- 
+
 By linking your saved views to the Cloudflare Notifications Center, you can ensure the right information reaches your team at the right time.
- 
+
 - **Immediate Alerts**: receive real-time notifications the moment a critical event is detected that matches your saved criteria. This is essential for high-priority monitoring, such as tracking active campaigns from specific APT groups.
- 
+
 - **Daily Digests**: opt for a summarized report delivered once a day. This is ideal for maintaining situational awareness of broader trends, like regional activity shifts or industry-wide threat landscapes, without cluttering your inbox.
- 
+
 ![Threat Events notifications](~/assets/images/changelog/security-center/threat-events-notifications.png)
- 
+
 ### How to get started
- 
+
 To set up an alert, go to **Application Security** > **Threat Intelligence** > **Threat Events**. From there:
- 
+
 1. Choose your datasets and apply your desired filters and select **Save View** (or select an existing one).
 2. Open the **Manage Saved Views** menu.
 3. Select **Add Alert** next to your chosen view to configure your notification preferences in the Cloudflare dashboard.
- 
+
 For more technical details on configuring notifications, refer to the [Threat Events documentation](/security-center/cloudforce-one/).
diff --git a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
index 6ab0a8267691e14..51425d471206a97 100644
--- a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
+++ b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
@@ -7,6 +7,7 @@ date: 2026-05-07
 You can now export your Requests for Information (RFI) history to a **CSV document** and customize your dashboard view by choosing how many RFI records to load per page.
 
 ### Why this matters
+
 These quality-of-life updates focus on data portability and dashboard performance, allowing power users to manage high volumes of requests more efficiently:
 
 - The new **CSV export** allows you to move RFI data into external tools for custom reporting, internal auditing, or cross-referencing with other security projects without manual data entry
diff --git a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
index 7728d2033ec5df9..3045c86a164b8bf 100644
--- a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
+++ b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
@@ -9,18 +9,19 @@ We’ve added a new **Agent Readiness** tab to URL Scanner reports accessible vi
 The Internet is shifting from a human-read web to a machine-read web. AI agents now browse, interact with, and even perform transactions on websites. If a site isn't "agent-ready," these bots may consume excessive bandwidth, fail to find critical information, or be unable to navigate your services efficiently.
 
 This update provides material value by breaking down readiness into six actionable categories:
-- **Basic Web Presence** 
+
+- **Basic Web Presence**
 - **Discoverability**
-- **Content Accessibility** 
-- **Bot Access Control** 
-- **Protocol Discovery** 
-- **Commerce** 
+- **Content Accessibility**
+- **Bot Access Control**
+- **Protocol Discovery**
+- **Commerce**
 
 ## Accessing the report
 
-You can view these scores for any scanned URL directly in the dashboard or via our API. 
+You can view these scores for any scanned URL directly in the dashboard or via our API.
 
-* **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
-* **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
+- **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
+- **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
 
 To learn more about the methodology behind these scores, refer to the [blogpost](https://blog.cloudflare.com/agent-readiness/).
diff --git a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
index f32ba78cbd7337b..632429a872e1c7c 100644
--- a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
+++ b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
@@ -12,7 +12,7 @@ Introducing enhanced archiving capabilities for security action items within the
 
 ### Why this matters
 
-Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored. 
+Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored.
 
 With these new archiving options—**False Positive**, **Accept Risk**, and **Other**—you can now suppress items indefinitely with required rationale text for risk-based decisions. This ensures that your team remains focused on critical, actionable vulnerabilities while preserving institutional knowledge for audits.
 
@@ -36,4 +36,5 @@ To review the history and rationale of a specific archived issue at the account
 ```bash
 curl "[https://api.cloudflare.com/client/v4/accounts/](https://api.cloudflare.com/client/v4/accounts/){account_id}/insights/{insight_id}/audit-log" \
      -H "Authorization: Bearer <API_TOKEN>" \
-     -H "Content-Type: application/json"
\ No newline at end of file
+     -H "Content-Type: application/json"
+```
diff --git a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
index d1f9b23ef4c3974..52e1ce7305a8c77 100644
--- a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
+++ b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
@@ -7,7 +7,7 @@ description: Cloudflare Secrets Store is now integrated with AI Gateway, allowin
 date: 2025-08-25T11:00:00Z
 ---
 
-import { Card, Render, Details } from "~/components"
+import { Card, Render, Details } from "~/components";
 
 Cloudflare Secrets Store is now integrated with AI Gateway, allowing you to store, manage, and deploy your AI provider keys in a secure and seamless configuration through [Bring Your Own Key](https://developers.cloudflare.com/ai-gateway/configuration/bring-your-own-keys/). Instead of passing your AI provider keys directly in every request header, you can centrally manage each key with Secrets Store and deploy in your gateway configuration using only a reference, rather than passing the value in plain text.
 
@@ -25,24 +25,24 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthro
  --header 'anthropic-version: 2023-06-01' \
  --header 'Content-Type: application/json' \
  --data  '{"model": "claude-3-opus-20240229", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}'
- ```
+```
 
- Or, using Javascript:
+Or, using Javascript:
 
- ```
- import Anthropic from '@anthropic-ai/sdk';
+```
+import Anthropic from '@anthropic-ai/sdk';
 
 
 const anthropic = new Anthropic({
-  apiKey: "ANTHROPIC_KEY_1",
-  baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
+ apiKey: "ANTHROPIC_KEY_1",
+ baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
 });
 
 
 const message = await anthropic.messages.create({
-  model: 'claude-3-opus-20240229',
-  messages: [{role: "user", content: "What is Cloudflare?"}],
-  max_tokens: 1024
+ model: 'claude-3-opus-20240229',
+ messages: [{role: "user", content: "What is Cloudflare?"}],
+ max_tokens: 1024
 });
 ```
 
diff --git a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
index c7b16b6e1a681b2..d6f34e72b9e8ed7 100644
--- a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
+++ b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
@@ -10,7 +10,7 @@ an M4A file to use in downstream workflows like [AI inference](/workers-ai/), co
 
 For example,
 
-``` text title="Example URL"
+```text title="Example URL"
 https://example.com/cdn-cgi/media/<OPTIONS>/<SOURCE-VIDEO>
 https://example.com/cdn-cgi/media/mode=audio,time=3s,duration=60s/<input video with diction>
 ```
diff --git a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
index a2a4201f278c795..817c2e0c7c81e19 100644
--- a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
+++ b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
@@ -3,6 +3,7 @@ title: Redesigned Support Portal for faster, personalized help
 description: A streamlined Support Portal featuring AI-driven ticket routing and a simplified interface for all Cloudflare customers.
 date: 2026-04-07
 ---
+
 ## Redesigned "Get Help" Portal for faster, personalized help
 
 Cloudflare has officially launched a redesigned "Get Help" Support Portal to eliminate friction and get you to a resolution faster. Previously, navigating support meant clicking through multiple tiles, categorizing your own technical issues across 50+ conditional fields, and translating your problem into Cloudflare's internal taxonomy.
diff --git a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
index 0fe7d0c34250fb2..906dc74af3ffc2b 100644
--- a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
+++ b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
@@ -12,7 +12,7 @@ This change ensures that when you need help, you spend less time navigating the
 
 ### What changed?
 
-* **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
-* **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
+- **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
+- **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
 
 To learn more about the resources available to you, refer to the [Cloudflare Support documentation](https://developers.cloudflare.com/support/contacting-cloudflare-support/).
diff --git a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
index d128e3253f5acb2..70650f4bcd04ef7 100644
--- a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
+++ b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
@@ -5,6 +5,7 @@ products:
   - fundamentals
 date: 2025-02-03
 ---
+
 ![Screenshot of Terraform defining a Zone](~/assets/images/changelog/2024-02-03-terraform-v5-screenshot.png)
 
 Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure.
@@ -12,5 +13,6 @@ Cloudflare's v5 Terraform Provider is now generally available. With this release
 The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach.
 
 For more info
-* [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-* [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
+
+- [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
+- [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
index d8df928767923fd..692eda375b40aaa 100644
--- a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
@@ -11,12 +11,12 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 ### Changes
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
-	- `cloudflare_zero_trust_gateway_policy`
-	- `cloudflare_zero_trust_access_application`
-	- `cloudflare_zero_trust_tunnel_cloudflared_route`
-	- `cloudflare_zone_setting`
-	- `cloudflare_ruleset`
-	- `cloudflare_page_rule`
+  - `cloudflare_zero_trust_gateway_policy`
+  - `cloudflare_zero_trust_access_application`
+  - `cloudflare_zero_trust_tunnel_cloudflared_route`
+  - `cloudflare_zone_setting`
+  - `cloudflare_ruleset`
+  - `cloudflare_page_rule`
 - Zone settings can be re-applied without client errors
 - Page rules conversion errors are fixed
 - Failure to apply changes to `cloudflare_zero_trust_tunnel_cloudflared_route`
@@ -25,6 +25,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.5.0) in GitHub.
 
 ### Issues Closed
+
 - [#5304: Importing cloudflare_zero_trust_gateway_policy invalid attribute filter value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5304)
 - [#5303: cloudflare_page_rule import does not set values for all of the fields in terraform state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5303)
 - [#5178: cloudflare_page_rule Page rule creation with redirect fails](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5178)
diff --git a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
index 88d70bea95929e7..ce7ec83f1e68809 100644
--- a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
@@ -17,7 +17,7 @@ eye on this changelog for more information about upcoming releases.
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
   - `cloudflare_zero_trust_access_identity_provider`
-	- `cloudflare_zone`
+  - `cloudflare_zone`
 - `cloudflare_page_rules` runtime panic when setting `cache_level` to `cache_ttl_by_status`
 - Failure to serialize requests in `cloudflare_zero_trust_tunnel_cloudflared_config`
 - Undocumented field 'priority' on `zone_lockdown` resource
@@ -33,6 +33,7 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.6.0) in GitHub.
 
 ### Issues Closed
+
 - [#5098: 500 Server Error on updating 'zero_trust_tunnel_cloudflared_virtual_network' Terraform resource](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5098)
 - [#5148: cloudflare_user_agent_blocking_rule doesn’t actually support user agents](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5148)
 - [#5472: cloudflare_zone showing changes in plan after following upgrade steps](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5472)
diff --git a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
index aaabc9c53996ef2..e637557cb1938b2 100644
--- a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
@@ -11,6 +11,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases.
 
 ### Changes
+
 - Addressed permanent diff bug on Cloudflare Tunnel config
 - State is now saved correctly for Zero Trust Access applications
 - Exact match is now working as expected within `data.cloudflare_zero_trust_access_applications`
@@ -24,6 +25,7 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.7.0) in GitHub.
 
 ### Issues Closed
+
 - [#5563: cloudflare_logpull_retention is missing import](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5563)
 - [#5608: cloudflare_zero_trust_access_policy in 5.5.0 provider gives error upon apply unexpected new value: .app_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1)](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5608)
 - [#5612: data.cloudflare_zero_trust_access_applications does not exact match](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5612)
@@ -32,7 +34,6 @@ For a more detailed look at all of the changes, see the
 - [#5565: Running Terraform with the cloudflare_zero_trust_access_policy resource results in updates on every apply, even when no changes are made - breaks idempotency](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5565)
 - [#5529: cloudflare_zero_trust_access_application: self hosted applications with private ips require public domain ](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5529)
 
-
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
index 280ce29c2aebb63..ce5660cdb8f4833 100644
--- a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
@@ -11,6 +11,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_custom_pages`
   - `cloudflare_page_rule`
@@ -18,13 +19,14 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
   - `cloudflare_argo_tiered_caching`
 - Addressed chronic drift issues in `cloudflare_logpush_job`, `cloudflare_zero_trust_dns_location`, `cloudflare_ruleset` & `cloudflare_api_token`
 - `cloudflare_zone_subscription` returns expected values `rate_plan.id` from former versions
-- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate 
-- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy` 
+- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate
+- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy`
 - Other bug fixes
 
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.2) in GitHub.
 
 ### Issues Closed
+
 - [#5666: cloudflare_ruleset example lists id which is a read-only field](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5666)
 - [#5578: cloudflare_logpush_job plan always suggests changes](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5578)
 - [#5552: 5.4.0: Since provider update, existing cloudflare_list_item would be recreated "created" state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5552)
diff --git a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
index 32201f4ca38d484..62ed2ed4b454317 100644
--- a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
@@ -6,13 +6,14 @@ products:
 date: 2025-08-15
 ---
 
-Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. 
+Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability.
 
-One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests. 
+One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests.
 
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_argo_smart_routing`
   - `cloudflare_bot_management`
@@ -40,6 +41,7 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 For a more detailed look at all of the changes, refer to the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.4) in GitHub.
 
 ### Issues Closed
+
 - [#5017: 'Uncaught Error: No such module' using cloudflare_snippets](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5017)
 - [#5701: cloudflare_workers_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5701)
 - [#5640: cloudflare_argo_smart_routing importing doesn't read the actual value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5640)
diff --git a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
index f25c1bc414c9f19..e89ea7fd1f359cd 100644
--- a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
@@ -13,6 +13,7 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 This release includes a new resource, `cloudflare_snippet`, which replaces `cloudflare_snippets`. `cloudflare_snippet` is now considered deprecated but can still be used. Please utilize `cloudflare_snippet` as soon as possible.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_zone_setting`
   - `cloudflare_worker_script`
@@ -28,6 +29,7 @@ For a more detailed look at all of the changes, refer to the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.9.0) in GitHub.
 
 ### Issues Closed
+
 - [#5921: In cloudflare_ruleset removing an existing rule causes recreation of later rules](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5921)
 - [#5904: cloudflare_zero_trust_access_application is not idempotent](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5904)
 - [#5898: (cloudflare_workers_script) Durable Object migrations not applied](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5898)
@@ -47,7 +49,6 @@ For a more detailed look at all of the changes, refer to the
 - [#5727: cloudflare_ruleset http_request_cache_settings bypass mismatch between dashboard and terraform](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5727)
 - [#5700: cloudflare_account_member invalid type 'string' for field 'roles'](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5700)
 
-
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new issue if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
index 3886135203e9e03..ac788bb9e06272c 100644
--- a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
@@ -6,55 +6,56 @@ products:
 date: 2025-11-20
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
-This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more. 
+This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more.
 
 ### Breaking Change
+
 Please be aware that there are breaking changes for the `cloudflare_api_token` and `cloudflare_account_token` resources. These changes eliminate configuration drift caused by policy ordering differences in the Cloudflare API.
 
 For more specific information about the changes or the actions required, please see the [detailed Repository changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.13.0).
 
-
 ### Features
 
-* **New resources and data sources added** 
-	* cloudflare_connectivity_directory
-	* cloudflare_sso_connector
-	* cloudflare_universal_ssl_setting
-* **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
-* **docs:** make docs explicit when a resource does not have import support 
-* **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
-* **worker_version:** add content_base64 support
-* **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
-* **workers_script_subdomains:** add import support  ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
-* **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
-* **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
-
+- **New resources and data sources added**
+  - cloudflare_connectivity_directory
+  - cloudflare_sso_connector
+  - cloudflare_universal_ssl_setting
+- **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
+- **docs:** make docs explicit when a resource does not have import support
+- **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
+- **worker_version:** add content_base64 support
+- **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
+- **workers_script_subdomains:** add import support ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
+- **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
+- **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
 
 ### Bug Fixes
 
-* **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
-* allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
-* **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
-* **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
-* **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
-* **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
-* **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181)) 
-* **workers_kv:** multipart request  ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
-* **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386)) 
-* **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383)) 
-* **workers_script:** allow config.run_worker_first to accept list input 
-* **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
-* **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
-* **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
-* **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
+- **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
+- allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
+- **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
+- **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
+- **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
+- **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
+- **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181))
+- **workers_kv:** multipart request ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
+- **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386))
+- **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383))
+- **workers_script:** allow config.run_worker_first to accept list input
+- **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
+- **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
+- **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
+- **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
 
 ### Upgrading
+
 We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized. We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more info
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
index a33c746b8592808..9cff570347406b9 100644
--- a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
@@ -6,7 +6,7 @@ products:
 date: 2025-12-05
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
@@ -14,7 +14,7 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Deprecation notice
 
-Resource affected: `api_shield_discovery_operation` 
+Resource affected: `api_shield_discovery_operation`
 
 Cloudflare continuously discovers and updates API endpoints and web assets of your web applications. To improve the maintainability of these dynamic resources, we are working on reducing the need to actively engage with discovered operations.
 
@@ -26,21 +26,23 @@ The corresponding public API endpoint of [discovered operations](https://develop
 
 ### Bug fixes
 
-- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488)) 
+- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488))
 - **pages_project**: Ensures non empty refresh plans ([#6515](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6515))
-- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512)) 
-- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521)) 
-- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489)) 
-- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504)) 
-- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503)) 
+- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512))
+- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521))
+- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489))
+- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504))
+- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503))
 - **zero_trust_dlp_custom_profile**: Adds sweepers for `dlp_custom_profile`
 - **zone_subscription|account_subscription**: Adds `partners_ent` as valid enum for `rate_plan.id` ([#6505](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6505))
-- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487)) 
-- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510)) 
+- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487))
+- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510))
 
 ### Upgrade to newer version
+
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
index 017d74955cda99c..6c0f1f7bf13a718 100644
--- a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
@@ -14,29 +14,31 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-* **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
-* **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
-* **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
-* **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
-* **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+- **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
+- **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
+- **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
+- **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+- **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
 
 ### Bug fixes
 
-* **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
-* **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
-* **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
-* **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
-* **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
-* **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
-* **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
+- **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
+- **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
+- **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
+- **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
+- **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
+- **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
+- **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
 
 ### Upgrade to newer version
+
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](/terraform/)
\ No newline at end of file
+- [Documentation on using Terraform with Cloudflare](/terraform/)
diff --git a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
index 00374611ed967d8..fc887b15fcfba63 100644
--- a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
@@ -16,41 +16,42 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-* **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
-* **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
-* **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
-* **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
-* **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
-* **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
-* **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
-* **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
-* **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
-* **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
-* **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
-* **ruleset:** add request body buffering support
-* **ruleset:** enhance ruleset data source with additional configuration options
-* **workers_script:** add observability logs attributes to list data source model
-* **workers_script:** enhance list data source schema with additional configuration options
+- **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
+- **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
+- **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
+- **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
+- **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
+- **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
+- **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
+- **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
+- **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
+- **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
+- **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
+- **ruleset:** add request body buffering support
+- **ruleset:** enhance ruleset data source with additional configuration options
+- **workers_script:** add observability logs attributes to list data source model
+- **workers_script:** enhance list data source schema with additional configuration options
 
 ### Bug Fixes
 
-* **account_member**: fix resource importability issues
-* **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
-* **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
-* **workers_kv:** handle special characters correctly in URL encoding
+- **account_member**: fix resource importability issues
+- **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
+- **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
+- **workers_kv:** handle special characters correctly in URL encoding
 
 ### Documentation
 
-* **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
-* **api_shield:** add resource-level description for API Shield management of auth ID characteristics
-* **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
-* **api_shield:** specify JSONPath expression format for JWT claim locations
-* **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
-* **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
-* **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
-* **hyperdrive_config:** update port description to clarify defaults for different database types
+- **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
+- **api_shield:** add resource-level description for API Shield management of auth ID characteristics
+- **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
+- **api_shield:** specify JSONPath expression format for JWT claim locations
+- **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
+- **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
+- **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
+- **hyperdrive_config:** update port description to clarify defaults for different database types
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
index d8dedb4bea9275a..76242fbae5f2ce1 100644
--- a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
@@ -28,60 +28,61 @@ help us build products that reflect your needs.
 
 ### Features
 
-* **ai_search_instance:** add data source for querying AI Search instances
-* **ai_search_token:** add data source for querying AI Search tokens
-* **account:** add support for tenant unit management with new `unit` field
-* **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
-* **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
-* **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
-* **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
-* **workers_kv:** add `value` field to data source to retrieve KV values directly
-* **workers_script:** add `script` field to data source to retrieve script content
-* **workers_script:** add support for `simple` rate limit binding
-* **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
-* **workers_script:** add `placement_mode` and `placement_status` computed fields
-* **zero_trust_dex_test:** add data source with filter support for finding specific tests
-* **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
+- **ai_search_instance:** add data source for querying AI Search instances
+- **ai_search_token:** add data source for querying AI Search tokens
+- **account:** add support for tenant unit management with new `unit` field
+- **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
+- **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
+- **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
+- **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
+- **workers_kv:** add `value` field to data source to retrieve KV values directly
+- **workers_script:** add `script` field to data source to retrieve script content
+- **workers_script:** add support for `simple` rate limit binding
+- **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
+- **workers_script:** add `placement_mode` and `placement_status` computed fields
+- **zero_trust_dex_test:** add data source with filter support for finding specific tests
+- **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
 
 ### Bug Fixes
 
-* **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
-* **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
-* **authenticated_origin_pulls:** handle array response and implement full lifecycle
-* **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
-* **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
-* **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
-* **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
-* **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
-* **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
-* **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
-* **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
-* **mtls_certificates:** fix resource and test
-* **pages_project:** revert build_config to computed optional
-* **stream_key:** use correct `account_id` field instead of `id` in API calls
-* **total_tls:** use upsert pattern for singleton zone setting
-* **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
-* **workers_script:** add support for placement mode/status
-* **zero_trust_access_application:** update v4 version on migration tests
-* **zero_trust_device_posture_rule:** update tests to match API
-* **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
-* **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
-* **zero_trust_organization:** fix plan issues
+- **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
+- **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
+- **authenticated_origin_pulls:** handle array response and implement full lifecycle
+- **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
+- **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
+- **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
+- **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
+- **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
+- **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
+- **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
+- **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
+- **mtls_certificates:** fix resource and test
+- **pages_project:** revert build_config to computed optional
+- **stream_key:** use correct `account_id` field instead of `id` in API calls
+- **total_tls:** use upsert pattern for singleton zone setting
+- **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
+- **workers_script:** add support for placement mode/status
+- **zero_trust_access_application:** update v4 version on migration tests
+- **zero_trust_device_posture_rule:** update tests to match API
+- **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
+- **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
+- **zero_trust_organization:** fix plan issues
 
 ### Chores
 
-* add state upgraders to 95+ resources to lay the foundation for replacing Grit
+- add state upgraders to 95+ resources to lay the foundation for replacing Grit
   (still under active development)
-* **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
-* **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
-* **dns_record:** add state migration handler for SDKv2 to Framework conversion
-* **leaked_credential_check:** add import functionality and tests
-* **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
-* **pages_project:** add state migration handlers
-* **tiered_cache:** add state migration handlers
-* **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
+- **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
+- **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
+- **dns_record:** add state migration handler for SDKv2 to Framework conversion
+- **leaked_credential_check:** add import functionality and tests
+- **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
+- **pages_project:** add state migration handlers
+- **tiered_cache:** add state migration handlers
+- **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
index 6681382c7d1ae98..c9633450d6adb47 100644
--- a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
@@ -32,6 +32,7 @@ Terraform Provider v5.19.0 introduces 14 new resources spanning AI Gateway, Pipe
 ### V4 to V5 Migration State Upgraders
 
 State upgraders added for seamless migration from v4 to v5 for the following resources:
+
 - account
 - account_member
 - account_token
diff --git a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
index 4aa693f7bd56a44..1acd6e85a6a432f 100644
--- a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
+++ b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
@@ -6,11 +6,11 @@ products:
   - terraform
 ---
 
-We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5. 
+We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5.
 
 ## v5 is stable and ready for production
 
-**Terraform Provider v5 is stable and actively receiving updates.**  We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
+**Terraform Provider v5 is stable and actively receiving updates.** We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
 
 Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool we're providing to the community — ensuring the best possible migration experience.
 
@@ -24,7 +24,7 @@ Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool w
 - **Cross-file reference updates** – Automatically finds and updates all references to renamed resources across your entire configuration
 - **Dry-run mode** – Preview all changes before applying them to ensure safety
 
-Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest. 
+Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest.
 
 ## Supported resources
 
diff --git a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
index d669da557298f32..968781b659c1aca 100644
--- a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
+++ b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
@@ -14,7 +14,8 @@ Your real-time applications running over [Cloudflare Tunnel](/cloudflare-one/net
 This is a foundational improvement to Cloudflare Tunnel, delivered automatically to all customers. There are no settings to configure — your UDP traffic is already flowing faster and more reliably.
 
 **What’s new:**
+
 - **Faster UDP performance**: We've significantly reduced the latency for establishing new UDP sessions, making applications like private DNS much more responsive.
 - **Greater reliability for mixed traffic**: UDP packets are no longer affected by heavy TCP traffic, preventing timeouts and connection drops for your real-time services.
 
-Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
\ No newline at end of file
+Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
diff --git a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
index 4ed43b589b89d2e..e857486e0668872 100644
--- a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
+++ b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
@@ -13,22 +13,22 @@ Starting **December 1, 2025**, list endpoints for the [Cloudflare Tunnel API](/a
 No action is required if you already explicitly set `is_deleted=false` or if you only need to list active resources.
 
 This change affects the following API endpoints:
-* List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
-* List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
-* List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
-* List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
-* List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
-* List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
+
+- List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
+- List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
+- List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
+- List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
+- List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
+- List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
 
 ## What is changing?
 
 The default behavior of the `is_deleted` query parameter will be updated.
 
-| Scenario | Previous behavior (before December 1, 2025) | New behavior (from December 1, 2025) |
-| :--- | :--- | :--- |
+| Scenario                          | Previous behavior (before December 1, 2025)                                | New behavior (from December 1, 2025)                                  |
+| :-------------------------------- | :------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
 | `is_deleted` parameter is omitted | Returns **active & deleted** tunnels, routes, subnets and virtual networks | Returns **only active** tunnels, routes, subnets and virtual networks |
 
-
 ## Action required
 
 If you need to retrieve deleted (or all) resources, please update your API calls to explicitly include the `is_deleted` parameter before **December 1, 2025**.
@@ -48,9 +48,11 @@ curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/virtual_
 Following this change, retrieving a complete list of both active and deleted resources will require two separate API calls: one to get active items (by omitting the parameter or using `is_deleted=false`) and one to get deleted items (`is_deleted=true`).
 
 ## Why we’re making this change
+
 This update is based on user feedback and aims to:
-* **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
-* **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
-* **Improve performance:** For most users, the default query result will now be smaller and more relevant.
 
-To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
\ No newline at end of file
+- **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
+- **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
+- **Improve performance:** For most users, the default query result will now be smaller and more relevant.
+
+To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
diff --git a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
index 947de730982905f..bc751a65e2b32ff 100644
--- a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
+++ b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
@@ -16,6 +16,7 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 ![Hostname-based routing in Cloudflare Tunnel](~/assets/images/changelog/cloudflare-one/tunnel-hostname-routing.webp)
 
 **What’s new:**
+
 - **Hostname & Domain Routing**: Create routes for individual hostnames (e.g., `payroll.acme.local`) or entire domains (e.g., `*.acme.local`) and direct their traffic to a specific Tunnel.
 - **Simplified Zero Trust Policies**: Build resilient policies in Cloudflare Access and Gateway using stable hostnames, making it dramatically easier to apply per-resource authorization for your private applications.
 - **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
@@ -23,4 +24,4 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 
 Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) or [public hostname](/cloudflare-one/traffic-policies/egress-policies/egress-cloudflared/) route.
 
-Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
\ No newline at end of file
+Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
diff --git a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
index b4bdbe1014ee162..35c45b7766d212a 100644
--- a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
+++ b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
@@ -13,4 +13,4 @@ You can now `ping` the WARP Connector host directly on its LAN IP address immedi
 
 Starting with [version 2025.10.186.0](/changelog/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability.
 
-Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
\ No newline at end of file
+Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
diff --git a/src/content/changelog/waf/2025-07-14-waf-release.mdx b/src/content/changelog/waf/2025-07-14-waf-release.mdx
index 27ee5690579c07e..3657b790de4b853 100644
--- a/src/content/changelog/waf/2025-07-14-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-14-waf-release.mdx
@@ -13,7 +13,6 @@ This week’s vulnerability analysis highlights emerging web application threats
 - XSS – Attribute Overloading: A novel cross-site scripting technique where attackers abuse custom or non-standard HTML attributes to smuggle payloads into the DOM. These payloads evade traditional sanitization logic, especially in frameworks that loosely validate attributes or trust unknown tokens.
 - XSS – onToggle Event Abuse: Exploits the lesser-used onToggle event (triggered by elements like `<details>`) to execute arbitrary JavaScript when users interact with UI elements. This vector is often overlooked by static analyzers and can be embedded in seemingly benign components.
 
-
 **Impact**
 
 These vulnerabilities target both user-facing components and back-end databases, introducing potential vectors for credential theft, session hijacking, or full data exfiltration. The XSS variants bypass conventional filters through overlooked HTML behaviors, while the obfuscated SQLi enables attackers to stealthily probe back-end logic, making them especially difficult to detect and block.
diff --git a/src/content/changelog/waf/2025-07-21-emergency.mdx b/src/content/changelog/waf/2025-07-21-emergency.mdx
index ce9154530bc73e3..190744a1169aa10 100644
--- a/src/content/changelog/waf/2025-07-21-emergency.mdx
+++ b/src/content/changelog/waf/2025-07-21-emergency.mdx
@@ -29,30 +29,30 @@ Together, these vulnerabilities significantly weaken the security posture of on-
 			<th>Comments</th>
 		</tr>
 	</thead>
-       <tbody>
- 		<tr>
+	<tbody>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
-					<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
+				<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
 			</td>
 			<td>100817</td>
 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53770</td>
 			<td>N/A</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
- 		</tr>
- 		<tr>
+		</tr>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
- 			<td>
- 					<RuleID id="d21f327516a145bc9d1b05678de656c4" />
- 			</td>
- 			<td>100818</td>
- 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
- 			<td>N/A</td>
- 			<td>Block</td>
- 			<td>This is a New Detection</td>
+			<td>
+				<RuleID id="d21f327516a145bc9d1b05678de656c4" />
+			</td>
+			<td>100818</td>
+			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
 		</tr>
-  </tbody>
+	</tbody>
 </table>
 
-For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
\ No newline at end of file
+For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
diff --git a/src/content/changelog/waf/2025-07-28-waf-release.mdx b/src/content/changelog/waf/2025-07-28-waf-release.mdx
index 3374f46caf0c044..c04a253ad3d3a3e 100644
--- a/src/content/changelog/waf/2025-07-28-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-28-waf-release.mdx
@@ -8,7 +8,6 @@ import { RuleID } from "~/components";
 
 This week’s update spotlights several vulnerabilities across Apache Tomcat, MongoDB, and Fortinet FortiWeb. Several flaws related with a memory leak in Apache Tomcat can lead to a denial-of-service attack. Additionally, a code injection flaw in MongoDB's Mongoose library allows attackers to bypass security controls to access restricted data.
 
-
 **Key Findings**
 
 - Fortinet FortiWeb (CVE-2025-25257): An improper neutralization of special elements used in a SQL command vulnerability in Fortinet FortiWeb versions allows an unauthenticated attacker to execute unauthorized SQL code or commands.
@@ -73,7 +72,9 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="f9e01e28c5d6499cac66364b4b6a5bb1" />
 			</td>
 			<td>100815</td>
-			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
+			<td>
+				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -84,10 +85,12 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="700d4fcc7b1f481a80cbeee5688f8e79" />
 			</td>
 			<td>100816</td>
-			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
+			<td>
+				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-08-04-waf-release.mdx b/src/content/changelog/waf/2025-08-04-waf-release.mdx
index f8f5bc852842740..b0e648fc90a3a62 100644
--- a/src/content/changelog/waf/2025-08-04-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-04-waf-release.mdx
@@ -35,105 +35,110 @@ The Grafana cross-site scripting (XSS) flaw can be used to hijack authenticated
 Meanwhile, the information disclosure flaw in WordPress core provides attackers with valid user emails, fueling targeted phishing campaigns that aim to secure the same account access achievable through the other exploits.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b8ab4644f8044f3485441ee052f30a13" />
-      </td>
-      <td>100535A</td>
-      <td>Sitecore - Dangerous File Upload - CVE:CVE-2025-34510, CVE:CVE-2025-34511</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
-      </td>
-      <td>100535</td>
-      <td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
-      </td>
-      <td>100543</td>
-      <td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
-      </td>
-      <td>100545</td>
-      <td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="28108d25f1cf470c8e7648938f634977" />
-      </td>
-      <td>100820</td>
-      <td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
-      </td>
-      <td>100821</td>
-      <td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
-      </td>
-      <td>100822</td>
-      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="69d43d704b0641898141a4300bf1b661" />
-      </td>
-      <td>100823</td>
-      <td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b8ab4644f8044f3485441ee052f30a13" />
+			</td>
+			<td>100535A</td>
+			<td>
+				Sitecore - Dangerous File Upload - CVE:CVE-2025-34510,
+				CVE:CVE-2025-34511
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
+			</td>
+			<td>100535</td>
+			<td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
+			</td>
+			<td>100543</td>
+			<td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
+			</td>
+			<td>100545</td>
+			<td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="28108d25f1cf470c8e7648938f634977" />
+			</td>
+			<td>100820</td>
+			<td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
+			</td>
+			<td>100821</td>
+			<td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
+			</td>
+			<td>100822</td>
+			<td>
+				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="69d43d704b0641898141a4300bf1b661" />
+			</td>
+			<td>100823</td>
+			<td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
index e7e5dad628ec2f1..e9deb9cfadebeca 100644
--- a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
@@ -23,39 +23,42 @@ Adobe AEM’s remote code execution vulnerability enables attackers to run arbit
 These findings reinforce the urgency of updating to the patched versions — Squid 6.4 and Adobe AEM 6.5.24 or later — and reviewing configurations to prevent exploitation.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
-      </td>
-      <td>100844</td>
-      <td>Adobe Experience Manager Forms - Remote Code Execution - CVE:CVE-2025-54253</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
-      </td>
-      <td>100840</td>
-      <td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
+			</td>
+			<td>100844</td>
+			<td>
+				Adobe Experience Manager Forms - Remote Code Execution -
+				CVE:CVE-2025-54253
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
+			</td>
+			<td>100840</td>
+			<td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-11-waf-release.mdx b/src/content/changelog/waf/2025-08-11-waf-release.mdx
index 62764e4b09840a6..74a303e3d74c2fb 100644
--- a/src/content/changelog/waf/2025-08-11-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-11-waf-release.mdx
@@ -8,26 +8,21 @@ import { RuleID } from "~/components";
 
 This week's update focuses on a wide range of enterprise software, from network infrastructure and security platforms to content management systems and development frameworks. Flaws include unsafe deserialization, OS command injection, SSRF, authentication bypass, and arbitrary file upload — many of which allow unauthenticated remote code execution. Notable risks include Cisco Identity Services Engine and Ivanti EPMM, where successful exploitation could grant attackers full administrative control of core network infrastructure and popular web services such as WordPress, SharePoint, and Ingress-Nginx, where security bypasses and arbitrary file uploads could lead to complete site or server compromise.
 
-
 **Key Findings**
 
 - Cisco Identity Services Engine (CVE-2025-20281): Insufficient input validation in a specific API of Cisco Identity Services Engine (ISE) and ISE-PIC allows an unauthenticated, remote attacker to execute arbitrary code with root privileges on an affected device.
 
 - Wazuh Server (CVE-2025-24016): An unsafe deserialization vulnerability in Wazuh Server (versions 4.4.0 to 4.9.0) allows for remote code execution and privilege escalation. By injecting unsanitized data, an attacker can trigger an exception to execute arbitrary code on the server.
 
-
 - CrushFTP (CVE-2025-54309): A flaw in AS2 validation within CrushFTP allows remote attackers to gain administrative access via HTTPS on systems not using the DMZ proxy feature. This flaw can lead to unauthorized file access and potential system compromise.
 
-
 - Kentico Xperience CMS (CVE-2025-2747, CVE-2025-2748): Vulnerabilities in Kentico Xperience CMS could enable cross-site scripting (XSS), allowing attackers to inject malicious scripts into web pages. Additionally, a flaw could allow unauthenticated attackers to bypass the Staging Sync Server's authentication, potentially leading to administrative control over the CMS.
 
-
 - Node.js (CVE-2025-27210): An incomplete fix for a previous vulnerability (CVE-2025-23084) in Node.js affects the `path.join()` API method on Windows systems. The vulnerability can be triggered using reserved Windows device names such as `CON`, `PRN`, or `AUX`.
 
-- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847): 
-This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
-(Note: CVE-2025-34085 has been rejected as a duplicate.)
-
+- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847):
+  This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
+  (Note: CVE-2025-34085 has been rejected as a duplicate.)
 
 - GeoServer (CVE-2024-29198): A Server-Side Request Forgery (SSRF) vulnerability exists in GeoServer's Demo request endpoint, which can be exploited where the Proxy Base URL has not been configured.
 
@@ -37,240 +32,239 @@ This vulnerability in the Simple File List plugin for WordPress allows an unauth
 
 - Manager-IO (CVE-2025-54122): A critical unauthenticated full read Server-Side Request Forgery (SSRF) vulnerability is present in the proxy handler of both Manager Desktop and Server editions up to version 25.7.18.2519. This allows an unauthenticated attacker to bypass network isolation and access internal services.
 
-- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. 
+- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller.
 
 - PaperCut NG/MF (CVE-2023-2533): A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PaperCut NG/MF. Under specific conditions, an attacker could exploit this to alter security settings or execute arbitrary code if they can deceive an administrator with an active login session into clicking a malicious link.
 
 - SonicWall SMA (CVE-2025-40598): This vulnerability could allow an unauthenticated attacker to bypass security controls. This allows a remote, unauthenticated attacker to potentially execute arbitrary JavaScript code.
 
-- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress  is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
-
+- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
 
 **Impact**
 
 These vulnerabilities span a broad range of enterprise technologies, including network access control systems, monitoring platforms, web servers, CMS platforms, cloud services, and collaboration tools. Exploitation techniques range from remote code execution and command injection to authentication bypass, SQL injection, path traversal, and configuration weaknesses.
 
-A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers. 
+A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ec6480c81253494b947d891e51bc8df1" />
-      </td>
-      <td>100538</td>
-      <td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
-      </td>
-      <td>100548</td>
-      <td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
-      </td>
-      <td>100550</td>
-      <td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e1369c5d629f4f10a14141381dca5738" />
-      </td>
-      <td>100562</td>
-      <td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
-      </td>
-      <td>100565</td>
-      <td>
-        Cisco Identity Services Engine - Remote Code Execution -
-        CVE:CVE-2025-20281
-      </td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed759f7e44184fa398ef71785d8102e1" />
-      </td>
-      <td>100567</td>
-      <td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="71b8e7b646f94d79873213cd99105c43" />
-      </td>
-      <td>100569</td>
-      <td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
-      </td>
-      <td>100571</td>
-      <td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
-      </td>
-      <td>100573</td>
-      <td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
-      </td>   
-      <td>100806</td>      
-      <td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
-      </td>
-      <td>100824</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3638baed75924604987b86d874920ace" />
-      </td>
-      <td>100824A</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
-      </td>
-      <td>100825</td>
-      <td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
-      <td>Log</td>
-      <td>Block</td> 
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
-      </td>
-      <td>100826</td>
-      <td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
-      </td>
-      <td>100827</td>
-      <td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="54dd826f578c483196ce852b6f1c2d12" />
-      </td>
-      <td>100828</td>
-      <td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a2867f7456c14213a94509a40341fccc" />
-      </td>
-      <td>100829</td>
-      <td>
-        WordPress:Plugin:Simple File List - Remote Code Execution -
-        CVE:CVE-2025-34085
-      </td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4cdb0e792d1a428a897526624cefeeda" />
-      </td>
-      <td>100829A</td>
-      <td>
-        WordPress:Plugin:Simple File List - Remote Code Execution -
-        CVE:CVE-2025-34085 - 2
-      </td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ec6480c81253494b947d891e51bc8df1" />
+			</td>
+			<td>100538</td>
+			<td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
+			</td>
+			<td>100548</td>
+			<td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
+			</td>
+			<td>100550</td>
+			<td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e1369c5d629f4f10a14141381dca5738" />
+			</td>
+			<td>100562</td>
+			<td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
+			</td>
+			<td>100565</td>
+			<td>
+				Cisco Identity Services Engine - Remote Code Execution -
+				CVE:CVE-2025-20281
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed759f7e44184fa398ef71785d8102e1" />
+			</td>
+			<td>100567</td>
+			<td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="71b8e7b646f94d79873213cd99105c43" />
+			</td>
+			<td>100569</td>
+			<td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
+			</td>
+			<td>100571</td>
+			<td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
+			</td>
+			<td>100573</td>
+			<td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
+			</td>
+			<td>100806</td>
+			<td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
+			</td>
+			<td>100824</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3638baed75924604987b86d874920ace" />
+			</td>
+			<td>100824A</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
+			</td>
+			<td>100825</td>
+			<td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
+			</td>
+			<td>100826</td>
+			<td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
+			</td>
+			<td>100827</td>
+			<td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="54dd826f578c483196ce852b6f1c2d12" />
+			</td>
+			<td>100828</td>
+			<td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a2867f7456c14213a94509a40341fccc" />
+			</td>
+			<td>100829</td>
+			<td>
+				WordPress:Plugin:Simple File List - Remote Code Execution -
+				CVE:CVE-2025-34085
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4cdb0e792d1a428a897526624cefeeda" />
+			</td>
+			<td>100829A</td>
+			<td>
+				WordPress:Plugin:Simple File List - Remote Code Execution -
+				CVE:CVE-2025-34085 - 2
+			</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-18-waf-release.mdx b/src/content/changelog/waf/2025-08-18-waf-release.mdx
index 78b79350ea882e6..8f05b2eb924b63f 100644
--- a/src/content/changelog/waf/2025-08-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-18-waf-release.mdx
@@ -31,138 +31,143 @@ This week, a series of critical vulnerabilities were discovered impacting core e
 These vulnerabilities affect core infrastructure, from network security appliances like SonicWall to data platforms such as Apache Druid and ML frameworks like BentoML. The code execution and deserialization flaws are particularly severe, offering deep system access that allows attackers to steal data, disrupt services, and establish a foothold for broader intrusions. Simultaneously, SSRF and XXE vulnerabilities undermine network boundaries, exposing sensitive internal data and creating pathways for lateral movement. Beyond data-centric threats, flaws in edge devices like the Tenda router introduce the tangible risk of operational disruption, highlighting a multi-faceted threat to the security and stability of key enterprise systems.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
-      </td>
-      <td>100574</td>
-      <td>SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819, CVE:CVE-2025-32820, CVE:CVE-2025-32821</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
-      </td>
-      <td>100576</td>
-      <td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d62935357ff846d9adefb58108ac45b3" />
-      </td>
-      <td>100585</td>
-      <td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
-      </td>
-      <td>100834</td>
-      <td>Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="1474121b01ba40629f8246f8022ab542" />
-      </td>
-      <td>100835</td>
-      <td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
-      </td>
-      <td>100837</td>
-      <td>SQLi - OOB</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
-      </td>
-      <td>100841</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="40fd793035c947c5ac75add1739180d2" />
-      </td>
-      <td>100841A</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
-      </td>
-      <td>100841B</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
-      </td>
-      <td>100845</td>
-      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
-      </td>
-      <td>100845A</td>
-      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
+			</td>
+			<td>100574</td>
+			<td>
+				SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819,
+				CVE:CVE-2025-32820, CVE:CVE-2025-32821
+			</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
+			</td>
+			<td>100576</td>
+			<td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d62935357ff846d9adefb58108ac45b3" />
+			</td>
+			<td>100585</td>
+			<td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
+			</td>
+			<td>100834</td>
+			<td>
+				Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="1474121b01ba40629f8246f8022ab542" />
+			</td>
+			<td>100835</td>
+			<td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
+			</td>
+			<td>100837</td>
+			<td>SQLi - OOB</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
+			</td>
+			<td>100841</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="40fd793035c947c5ac75add1739180d2" />
+			</td>
+			<td>100841A</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
+			</td>
+			<td>100841B</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
+			</td>
+			<td>100845</td>
+			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
+			</td>
+			<td>100845A</td>
+			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-25-waf-release.mdx b/src/content/changelog/waf/2025-08-25-waf-release.mdx
index f78810c3fd8e64b..42c73f310668c3c 100644
--- a/src/content/changelog/waf/2025-08-25-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-25-waf-release.mdx
@@ -21,50 +21,56 @@ This week, critical vulnerabilities were disclosed that impact widely used open-
 These vulnerabilities pose severe risks to enterprise environments and open-source ecosystems. Remote code execution enables attackers to gain deep system access, steal data, disrupt services, and establish persistent footholds for broader intrusions. Given the widespread deployment of Apache HTTP Server and Laravel in production systems, timely patching and mitigation are critical.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c550282a0f7343ca887bdab528050359" />
-      </td>
-      <td>100822_BETA</td>
-      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This was merged in to the original rule "WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058" (ID: <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
-      </td>
-      <td>100831</td>
-      <td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
-      </td>
-      <td>100846</td>
-      <td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c550282a0f7343ca887bdab528050359" />
+			</td>
+			<td>100822_BETA</td>
+			<td>
+				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>
+				This was merged in to the original rule "WordPress:Plugin:WPBookit -
+				Remote Code Execution - CVE:CVE-2025-6058" (ID:{" "}
+				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
+			</td>
+			<td>100831</td>
+			<td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
+			</td>
+			<td>100846</td>
+			<td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
index e11552cfbac77e9..0d6fc5ee3b10133 100644
--- a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
@@ -21,39 +21,39 @@ This week, new critical vulnerabilities were disclosed in Next.js’s image opti
 Exploitation could expose sensitive files, leak user or backend data, and undermine application trust. Given Next.js’s wide use, immediate patching and cache hardening are strongly advised.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
-      </td>
-      <td>100613</td>
-      <td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
-      </td>
-      <td>100616</td>
-      <td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
+			</td>
+			<td>100613</td>
+			<td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
+			</td>
+			<td>100616</td>
+			<td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-01-waf-release.mdx b/src/content/changelog/waf/2025-09-01-waf-release.mdx
index 5470b675623f1e5..88aa80a7543ddf4 100644
--- a/src/content/changelog/waf/2025-09-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-01-waf-release.mdx
@@ -10,50 +10,48 @@ import { RuleID } from "~/components";
 
 This week, a critical vulnerability was disclosed in Fortinet FortiWeb (versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and versions 7.0.10 and below), linked to improper parameter handling that could allow unauthorized access.
 
-
 **Key Findings**
 
-* Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
+- Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
 
 **Impact**
 
-Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended. 
-
+Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="636b145a49a84946b990d4fac49b7cf8" />
-      </td>
-      <td>100586</td>
-      <td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
-      </td>
-      <td>100136C</td>
-      <td>XSS - JavaScript - Headers and Body</td>
-      <td>N/A</td>
-      <td>N/A</td>
-      <td>Rule metadata description refined. Detection unchanged.</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="636b145a49a84946b990d4fac49b7cf8" />
+			</td>
+			<td>100586</td>
+			<td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
+			</td>
+			<td>100136C</td>
+			<td>XSS - JavaScript - Headers and Body</td>
+			<td>N/A</td>
+			<td>N/A</td>
+			<td>Rule metadata description refined. Detection unchanged.</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
index 385a50fe802115e..5855b853f30db8a 100644
--- a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
@@ -12,6 +12,7 @@ This week, new critical vulnerabilities were disclosed in Sitecore’s Sitecore
 These flaws are caused by unsafe data deserialization and code reflection, leaving affected systems at high risk of exploitation.
 
 **Key Findings**
+
 - CVE-2025-53690: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53691: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53693: HTML Cache Poisoning through Unsafe Reflections
@@ -21,50 +22,50 @@ These flaws are caused by unsafe data deserialization and code reflection, leavi
 Exploitation could allow attackers to execute arbitrary code remotely on the affected system and conduct cache poisoning attacks, potentially leading to further compromise. Applying the latest vendor-released solution without delay is strongly recommended.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
-      </td>
-      <td>100878</td>
-      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-      </td>
-      <td>100631</td>
-      <td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed94c7ce5301411a94a21a096c410240" />
-      </td>
-      <td>100879</td>
-      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
+			</td>
+			<td>100878</td>
+			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+			</td>
+			<td>100631</td>
+			<td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed94c7ce5301411a94a21a096c410240" />
+			</td>
+			<td>100879</td>
+			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-08-waf-release.mdx b/src/content/changelog/waf/2025-09-08-waf-release.mdx
index 1784243e8d5d2af..ccc94cccb99a6c9 100644
--- a/src/content/changelog/waf/2025-09-08-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-08-waf-release.mdx
@@ -6,21 +6,21 @@ date: 2025-09-08
 
 import { RuleID } from "~/components";
 
-**This week's update** 
+**This week's update**
 
 This week’s focus highlights newly disclosed vulnerabilities in web frameworks, enterprise applications, and widely deployed CMS plugins. The vulnerabilities include SSRF, authentication bypass, arbitrary file upload, and remote code execution (RCE), exposing organizations to high-impact risks such as unauthorized access, system compromise, and potential data exposure. In addition, security rule enhancements have been deployed to cover general command injection and server-side injection attacks, further strengthening protections.
 
 **Key Findings**
 
-* Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
+- Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
 
-* ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
+- ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
 
-* Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
+- Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
 
-* Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
+- Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
 
-* WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
+- WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
 
 **Impact**
 
@@ -29,116 +29,128 @@ These vulnerabilities could allow attackers to gain unauthorized access, execute
 Administrators are strongly advised to apply vendor patches immediately, remove unsupported software, and review authentication and access controls to mitigate these risks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
-      </td>
-      <td>100007D</td>
-      <td>Command Injection - Common Attack Commands Args</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "Command Injection - Common Attack Commands" (ID: <RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers only.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cd528243d6824f7ab56182988230a75b" />
-      </td>      
-      <td>100617</td>
-      <td>Next.js - SSRF - CVE:CVE-2025-57822</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
-      </td>
-      <td>100659_BETA</td>
-      <td>Common Payloads for Server-Side Template Injection - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "Common Payloads for Server-Side Template Injection" (ID: <RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)</td>
-    </tr>    
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
-      </td>
-      <td>100824B</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>    
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
-      </td>
-      <td>100848</td>
-      <td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
-      </td>
-      <td>100849</td>
-      <td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e7464139fd3e44938b56716bef971afd" />
-      </td>
-      <td>100872</td>
-      <td>WordPress:Plugin:InfiniteWP Client - Missing Authorization - CVE:CVE-2020-8772</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
-      </td>
-      <td>100873</td>
-      <td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
-      </td>
-      <td>100875</td>
-      <td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>    
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
+			</td>
+			<td>100007D</td>
+			<td>Command Injection - Common Attack Commands Args</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "Command Injection -
+				Common Attack Commands" (ID:{" "}
+				<RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers
+				only.
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cd528243d6824f7ab56182988230a75b" />
+			</td>
+			<td>100617</td>
+			<td>Next.js - SSRF - CVE:CVE-2025-57822</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
+			</td>
+			<td>100659_BETA</td>
+			<td>Common Payloads for Server-Side Template Injection - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "Common Payloads for
+				Server-Side Template Injection" (ID:{" "}
+				<RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
+			</td>
+			<td>100824B</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
+			</td>
+			<td>100848</td>
+			<td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
+			</td>
+			<td>100849</td>
+			<td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e7464139fd3e44938b56716bef971afd" />
+			</td>
+			<td>100872</td>
+			<td>
+				WordPress:Plugin:InfiniteWP Client - Missing Authorization -
+				CVE:CVE-2020-8772
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
+			</td>
+			<td>100873</td>
+			<td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
+			</td>
+			<td>100875</td>
+			<td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-15-waf-release.mdx b/src/content/changelog/waf/2025-09-15-waf-release.mdx
index d6bb571fc9be330..56e8dbc6e1051d7 100644
--- a/src/content/changelog/waf/2025-09-15-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-15-waf-release.mdx
@@ -12,11 +12,11 @@ This week's focus highlights newly disclosed vulnerabilities in DevOps tooling,
 
 **Key Findings**
 
-* Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
+- Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
 
-* DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
+- DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
 
-* Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
+- Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
 
 **Impact**
 
@@ -25,50 +25,50 @@ These vulnerabilities expose organizations to serious risks, including credentia
 Administrators are strongly advised to apply vendor patches immediately, rotate exposed credentials, and review access controls to mitigate these risks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
-      </td>
-      <td>100646</td>
-      <td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
-      </td>
-      <td>100874</td>
-      <td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
-      </td>
-      <td>100880</td>
-      <td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
+			</td>
+			<td>100646</td>
+			<td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
+			</td>
+			<td>100874</td>
+			<td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
+			</td>
+			<td>100880</td>
+			<td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-22-waf-release.mdx b/src/content/changelog/waf/2025-09-22-waf-release.mdx
index fd3fff204e42727..054a8348718a766 100644
--- a/src/content/changelog/waf/2025-09-22-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-22-waf-release.mdx
@@ -10,124 +10,125 @@ This week emphasizes two critical vendor-specific vulnerabilities: a full elevat
 
 **Key Findings**
 
+- Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges.
 
-* Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges. 
+- Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind).
 
-* Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind). 
-
-* Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
+- Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
 
 **Impact**
 
 These vulnerabilities allow attackers to escalate privileges or execute code under conditions where previously they could not:
 
-* Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components. 
-
-* Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components. 
+- Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components.
 
-* The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
+- Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components.
 
+- The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
-      </td>
-      <td>100146</td>
-      <td>SSRF - Host - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
-      </td>
-      <td>100146B</td>
-      <td>SSRF - Local - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
-      </td>
-      <td>100146C</td>
-      <td>SSRF - Cloud - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="78c856218f2d40f4b5988c8c956c1961" />
-      </td>
-      <td>100714</td>
-      <td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
-      </td>
-      <td>100758</td>
-      <td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
-      </td>
-      <td>100773</td>
-      <td>Next.js - SSRF</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
-      </td>
-      <td>100774</td>
-      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
-      </td>
-      <td>100800_BETA</td>
-      <td>SQLi - Obfuscated Boolean - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule (ID: <RuleID id="7663ea44178441a0b3205c145563445f" />)</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
+			</td>
+			<td>100146</td>
+			<td>SSRF - Host - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
+			</td>
+			<td>100146B</td>
+			<td>SSRF - Local - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
+			</td>
+			<td>100146C</td>
+			<td>SSRF - Cloud - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="78c856218f2d40f4b5988c8c956c1961" />
+			</td>
+			<td>100714</td>
+			<td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
+			</td>
+			<td>100758</td>
+			<td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
+			</td>
+			<td>100773</td>
+			<td>Next.js - SSRF</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
+			</td>
+			<td>100774</td>
+			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
+			</td>
+			<td>100800_BETA</td>
+			<td>SQLi - Obfuscated Boolean - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule (ID:{" "}
+				<RuleID id="7663ea44178441a0b3205c145563445f" />)
+			</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
index 2a09bf015de4913..05259d94a3946ba 100644
--- a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
@@ -10,35 +10,35 @@ This week highlights a critical vendor-specific vulnerability: a deserialization
 
 **Key Findings**
 
-* GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
+- GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
 
 **Impact**
 
 GoAnywhere MFT (CVE-2025-10035): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
-      </td>
-      <td>100787</td>
-      <td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
+			</td>
+			<td>100787</td>
+			<td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-26-waf-release.mdx b/src/content/changelog/waf/2025-09-26-waf-release.mdx
index b7e0125e8fa0a1a..aeb564538854fe1 100644
--- a/src/content/changelog/waf/2025-09-26-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-26-waf-release.mdx
@@ -11,138 +11,138 @@ import { RuleID } from "~/components";
 This update introduces 11 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
-      </td>
-      <td>100859A</td>
-      <td>SQLi - UNION - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
-      </td>
-      <td>100889</td>
-      <td>Command Injection - Generic 9</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c15ca8e8290f485287037665f2be3ddf" />
-      </td>
-      <td>100890</td>
-      <td>Information Disclosure - Common Files - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="56669615f2984c2cac8c608980a252a8" />
-      </td>
-      <td>100891</td>
-      <td>Anomaly:URL - Relative Paths</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c41789fb6370431d809567d17e7d3865" />
-      </td>
-      <td>100894</td>
-      <td>XSS - Inline Function</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
-      </td>
-      <td>100895</td>
-      <td>XSS - DOM</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab8277e3f432400bbd9403dd42978e38" />
-      </td>
-      <td>100896</td>
-      <td>SQLi - MSSQL Length Enumeration</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-      </td>
-      <td>100897</td>
-      <td>Generic Rules - Code Injection - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4375dc90c7af4c55908f6b95c1686741" />
-      </td>
-      <td>100898</td>
-      <td>SQLi - Evasion</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="945c5aa9f45141dd872d7ec920999be0" />
-      </td>
-      <td>100899</td>
-      <td>SQLi - Probing 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2c20b5e8684043f48620ff77b4026c88" />
-      </td>
-      <td>100900</td>
-      <td>SQLi - Probing</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
+			</td>
+			<td>100859A</td>
+			<td>SQLi - UNION - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
+			</td>
+			<td>100889</td>
+			<td>Command Injection - Generic 9</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c15ca8e8290f485287037665f2be3ddf" />
+			</td>
+			<td>100890</td>
+			<td>Information Disclosure - Common Files - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="56669615f2984c2cac8c608980a252a8" />
+			</td>
+			<td>100891</td>
+			<td>Anomaly:URL - Relative Paths</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c41789fb6370431d809567d17e7d3865" />
+			</td>
+			<td>100894</td>
+			<td>XSS - Inline Function</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
+			</td>
+			<td>100895</td>
+			<td>XSS - DOM</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab8277e3f432400bbd9403dd42978e38" />
+			</td>
+			<td>100896</td>
+			<td>SQLi - MSSQL Length Enumeration</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+			</td>
+			<td>100897</td>
+			<td>Generic Rules - Code Injection - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4375dc90c7af4c55908f6b95c1686741" />
+			</td>
+			<td>100898</td>
+			<td>SQLi - Evasion</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
+			</td>
+			<td>100899</td>
+			<td>SQLi - Probing 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2c20b5e8684043f48620ff77b4026c88" />
+			</td>
+			<td>100900</td>
+			<td>SQLi - Probing</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
index 93fe72102454c07..73bca3b78f919ec 100644
--- a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
@@ -10,46 +10,52 @@ This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CV
 
 **Key Findings**
 
-* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
 Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
-      </td>
-      <td>100788</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="51de6ce6596a40eb8200452ad30f768e" />
-      </td>
-      <td>100788A</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
+			</td>
+			<td>100788</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="51de6ce6596a40eb8200452ad30f768e" />
+			</td>
+			<td>100788A</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-29-waf-release.mdx b/src/content/changelog/waf/2025-09-29-waf-release.mdx
index b48fadd2caabecb..e4a7094b34030a4 100644
--- a/src/content/changelog/waf/2025-09-29-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-29-waf-release.mdx
@@ -10,82 +10,85 @@ This week highlights four important vendor- and component-specific issues: an au
 
 **Key Findings**
 
-* SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
+- SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
 
-* Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
+- Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
 
-* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
+- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
 
-* Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
+- Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
 
 **Impact**
 
 These vulnerabilities allow attackers to gain access, escalate privileges, or execute actions that were previously unavailable:
 
-* SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
+- SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
 
-* Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
+- Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
 
-* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
+- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
 
-* Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
+- Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6fe90532af50427484a5275c8c2e30fb" />
-      </td>
-      <td>100717</td>
-      <td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged to 100717 in legacy WAF and <RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
-      </td>
-      <td>100775</td>
-      <td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
-      </td>
-      <td>100881</td>
-      <td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
-      </td>
-      <td>100887</td>
-      <td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6fe90532af50427484a5275c8c2e30fb" />
+			</td>
+			<td>100717</td>
+			<td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged to 100717 in legacy WAF and{" "}
+				<RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
+			</td>
+			<td>100775</td>
+			<td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
+			</td>
+			<td>100881</td>
+			<td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
+			</td>
+			<td>100887</td>
+			<td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-10-03-waf-release.mdx b/src/content/changelog/waf/2025-10-03-waf-release.mdx
index c01420c6f44b5c8..f868e1edd121f98 100644
--- a/src/content/changelog/waf/2025-10-03-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-03-waf-release.mdx
@@ -11,248 +11,248 @@ import { RuleID } from "~/components";
 This update introduces 21 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
-      </td>
-      <td>100902</td>
-      <td>Generic Rules - Command Execution - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c3079865ce9a41368657026b514aeeb8" />
-      </td>
-      <td>100908</td>
-      <td>Generic Rules - Command Execution - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
-      </td>
-      <td>100910</td>
-      <td>Generic Rules - Command Execution - 4</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
-      </td>
-      <td>100915</td>
-      <td>Generic Rules - Command Execution - 5</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
-      </td>
-      <td>100899</td>
-      <td>Generic Rules - Content-Type Abuse</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="233364f656ff42b8acc41dcd7996012f" />
-      </td>
-      <td>100914</td>
-      <td>Generic Rules - Content-Type Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="1aa695281c954513be3d003b93209312" />
-      </td>
-      <td>100911</td>
-      <td>Generic Rules - Cookie Header Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
-      </td>
-      <td>100905</td>
-      <td>Generic Rules - NoSQL Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
-      </td>
-      <td>100913</td>
-      <td>Generic Rules - NoSQL Injection - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
-      </td>
-      <td>100907</td>
-      <td>Generic Rules - Parameter Pollution</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
-      </td>
-      <td>100906</td>
-      <td>Generic Rules - PHP Object Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed5190bfbe1b45a6a645126334c88168" />
-      </td>
-      <td>100904</td>
-      <td>Generic Rules - Prototype Pollution</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-      </td>
-      <td>100897</td>
-      <td>Generic Rules - Prototype Pollution 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
-      </td>
-      <td>100903</td>
-      <td>Generic Rules - Reverse Shell</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
-      </td>
-      <td>100909</td>
-      <td>Generic Rules - Reverse Shell - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="475d090baead467c88dfabbb565c78b0" />
-      </td>
-      <td>100898</td>
-      <td>Generic Rules - SSJI NoSQL</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f4c7f98934264c9c937eec1212b837a0" />
-      </td>
-      <td>100896</td>
-      <td>Generic Rules - SSRF</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="efd01b814d144e90b36522b311c4fb00" />
-      </td>
-      <td>100895</td>
-      <td>Generic Rules - Template Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="00a9a0d663da4add95b863abd3ed0123" />
-      </td>
-      <td>100895A</td>
-      <td>Generic Rules - Template Injection - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
-      </td>
-      <td>100912</td>
-      <td>Generic Rules - XXE</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
-      </td>
-      <td>100900</td>
-      <td>Relative Paths - Anomaly Headers</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
+			</td>
+			<td>100902</td>
+			<td>Generic Rules - Command Execution - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c3079865ce9a41368657026b514aeeb8" />
+			</td>
+			<td>100908</td>
+			<td>Generic Rules - Command Execution - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
+			</td>
+			<td>100910</td>
+			<td>Generic Rules - Command Execution - 4</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
+			</td>
+			<td>100915</td>
+			<td>Generic Rules - Command Execution - 5</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
+			</td>
+			<td>100899</td>
+			<td>Generic Rules - Content-Type Abuse</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="233364f656ff42b8acc41dcd7996012f" />
+			</td>
+			<td>100914</td>
+			<td>Generic Rules - Content-Type Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="1aa695281c954513be3d003b93209312" />
+			</td>
+			<td>100911</td>
+			<td>Generic Rules - Cookie Header Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
+			</td>
+			<td>100905</td>
+			<td>Generic Rules - NoSQL Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
+			</td>
+			<td>100913</td>
+			<td>Generic Rules - NoSQL Injection - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
+			</td>
+			<td>100907</td>
+			<td>Generic Rules - Parameter Pollution</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
+			</td>
+			<td>100906</td>
+			<td>Generic Rules - PHP Object Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed5190bfbe1b45a6a645126334c88168" />
+			</td>
+			<td>100904</td>
+			<td>Generic Rules - Prototype Pollution</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+			</td>
+			<td>100897</td>
+			<td>Generic Rules - Prototype Pollution 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
+			</td>
+			<td>100903</td>
+			<td>Generic Rules - Reverse Shell</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
+			</td>
+			<td>100909</td>
+			<td>Generic Rules - Reverse Shell - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="475d090baead467c88dfabbb565c78b0" />
+			</td>
+			<td>100898</td>
+			<td>Generic Rules - SSJI NoSQL</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f4c7f98934264c9c937eec1212b837a0" />
+			</td>
+			<td>100896</td>
+			<td>Generic Rules - SSRF</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="efd01b814d144e90b36522b311c4fb00" />
+			</td>
+			<td>100895</td>
+			<td>Generic Rules - Template Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="00a9a0d663da4add95b863abd3ed0123" />
+			</td>
+			<td>100895A</td>
+			<td>Generic Rules - Template Injection - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
+			</td>
+			<td>100912</td>
+			<td>Generic Rules - XXE</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
+			</td>
+			<td>100900</td>
+			<td>Relative Paths - Anomaly Headers</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-06-waf-release.mdx b/src/content/changelog/waf/2025-10-06-waf-release.mdx
index d4f1efa95c7512e..89c8ea1bc8db134 100644
--- a/src/content/changelog/waf/2025-10-06-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-06-waf-release.mdx
@@ -10,122 +10,124 @@ This week’s highlights prioritise an emergency Oracle E-Business Suite RCE rul
 
 **Key Findings**
 
-* New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
+- New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
 
-* Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
+- Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
 
-* Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
+- Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
 
-* Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
+- Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
 
 **Impact**
 
-* CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced. 
+- CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced.
 
-* CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
+- CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
 
-* CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
+- CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
-      </td>
-      <td>100882</td>
-      <td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
-      </td>
-      <td>100883</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a2591ba5befa4815a6861aefef859a04" />
-      </td>
-      <td>100884</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
-      </td>
-      <td>100886</td>
-      <td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="90514c7810694b188f56979826a4074c" />
-      </td>
-      <td>100888</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
-      </td>
-      <td>100916</td>
-      <td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="badc687a3ba3420a844220b129aa43c3" />
-      </td>
-      <td>100917</td>
-      <td>Generic Rules - SQLi - Inline Comment Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="28fa27511f29428899ceb5a273c10b6f" />
-      </td>
-      <td>100918</td>
-      <td>Generic Rules - SQLi - Information Disclosure</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>                    
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
+			</td>
+			<td>100882</td>
+			<td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
+			</td>
+			<td>100883</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a2591ba5befa4815a6861aefef859a04" />
+			</td>
+			<td>100884</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
+			</td>
+			<td>100886</td>
+			<td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="90514c7810694b188f56979826a4074c" />
+			</td>
+			<td>100888</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
+			</td>
+			<td>100916</td>
+			<td>
+				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="badc687a3ba3420a844220b129aa43c3" />
+			</td>
+			<td>100917</td>
+			<td>Generic Rules - SQLi - Inline Comment Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="28fa27511f29428899ceb5a273c10b6f" />
+			</td>
+			<td>100918</td>
+			<td>Generic Rules - SQLi - Information Disclosure</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
index fa9d65c7613c3e3..724fe2ad9d9bcae 100644
--- a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
@@ -7,9 +7,9 @@ date: 2025-10-07
 import { RuleID } from "~/components";
 
 This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CVE-2025-20333, CVE-2025-20362). This flaw stems from improper input validation in HTTP(S) requests. An authenticated VPN user could send crafted requests to execute code as root, potentially compromising the device.
-The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection. 
+The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection.
 
-* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
@@ -17,28 +17,31 @@ Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables att
 Administrators are strongly advised to apply vendor updates immediately.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
-      </td>
-      <td>100788B</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
+			</td>
+			<td>100788B</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
index 3001df61385c0d0..fc5674015901639 100644
--- a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
@@ -47,7 +47,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="72f0ff933fb0492eb71cda50589f2a1d" /></td>
+			<td>
+				<RuleID id="72f0ff933fb0492eb71cda50589f2a1d" />
+			</td>
 			<td>N/A</td>
 			<td>Anomaly:Header - name - CR, LF</td>
 			<td>N/A</td>
@@ -56,7 +58,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="5d0377e4435f467488614170132fab7e" /></td>
+			<td>
+				<RuleID id="5d0377e4435f467488614170132fab7e" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Body</td>
 			<td>N/A</td>
@@ -65,7 +69,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="54e32f7f802c4a699182e8921a027008" /></td>
+			<td>
+				<RuleID id="54e32f7f802c4a699182e8921a027008" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Header</td>
 			<td>N/A</td>
@@ -74,7 +80,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" /></td>
+			<td>
+				<RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - URI</td>
 			<td>N/A</td>
@@ -83,7 +91,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="b9f3420674cf481da32333dc8e0cf7ad" /></td>
+			<td>
+				<RuleID id="b9f3420674cf481da32333dc8e0cf7ad" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - XXE - Body</td>
 			<td>N/A</td>
@@ -92,7 +102,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="ad55483512f0440b81426acdbf8aab5e" /></td>
+			<td>
+				<RuleID id="ad55483512f0440b81426acdbf8aab5e" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Common Patterns - Header URI</td>
 			<td>N/A</td>
@@ -101,7 +113,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="849c0618d1674f1c92ba6f9b2e466337" /></td>
+			<td>
+				<RuleID id="849c0618d1674f1c92ba6f9b2e466337" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Sleep Function - Header URI</td>
 			<td>N/A</td>
@@ -110,7 +124,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" /></td>
+			<td>
+				<RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - String Function - Header URI</td>
 			<td>N/A</td>
@@ -119,7 +135,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="fa2055b84af94ba4b925f834b0633709" /></td>
+			<td>
+				<RuleID id="fa2055b84af94ba4b925f834b0633709" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - WaitFor Function - Header URI</td>
 			<td>N/A</td>
@@ -128,7 +146,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="158177dec2504acdba1f2da201a076eb" /></td>
+			<td>
+				<RuleID id="158177dec2504acdba1f2da201a076eb" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Local - Beta</td>
 			<td>N/A</td>
@@ -137,7 +157,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" /></td>
+			<td>
+				<RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Local - 2 - Beta</td>
 			<td>N/A</td>
@@ -146,7 +168,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" /></td>
+			<td>
+				<RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - Beta</td>
 			<td>N/A</td>
@@ -155,7 +179,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" /></td>
+			<td>
+				<RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - 2 - Beta</td>
 			<td>N/A</td>
@@ -164,7 +190,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="c16f4e133c4541f293142d02e6e8dc5b" /></td>
+			<td>
+				<RuleID id="c16f4e133c4541f293142d02e6e8dc5b" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - URI</td>
 			<td>N/A</td>
@@ -173,7 +201,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="f4fd9904e7624666b8c49cd62550d794" /></td>
+			<td>
+				<RuleID id="f4fd9904e7624666b8c49cd62550d794" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Header</td>
 			<td>N/A</td>
@@ -182,7 +212,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="5c0875604f774c36a4f9b69c659d12a6" /></td>
+			<td>
+				<RuleID id="5c0875604f774c36a4f9b69c659d12a6" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Body</td>
 			<td>N/A</td>
@@ -191,7 +223,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="fae6fa37ae9249d58628e54b1a3e521e" /></td>
+			<td>
+				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />
+			</td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -200,7 +234,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="9c02e585db34440da620eb668f76bd74" /></td>
+			<td>
+				<RuleID id="9c02e585db34440da620eb668f76bd74" />
+			</td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -209,7 +245,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="cb67fe56a84747b8b64277dc091e296d" /></td>
+			<td>
+				<RuleID id="cb67fe56a84747b8b64277dc091e296d" />
+			</td>
 			<td>N/A</td>
 			<td>HTTP parameter pollution</td>
 			<td>N/A</td>
@@ -218,7 +256,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="443b54d984944cd69043805ee34214ef" /></td>
+			<td>
+				<RuleID id="443b54d984944cd69043805ee34214ef" />
+			</td>
 			<td>N/A</td>
 			<td>Prototype Pollution - Common Payloads - Beta</td>
 			<td>N/A</td>
@@ -226,4 +266,4 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-10-20-waf-release.mdx b/src/content/changelog/waf/2025-10-20-waf-release.mdx
index b566732da2e8dad..3768829710eb921 100644
--- a/src/content/changelog/waf/2025-10-20-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-20-waf-release.mdx
@@ -10,7 +10,7 @@ This week’s update introduces an enhanced rule that expands detection coverage
 
 **Key Findings**
 
-New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
+New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
 
 **Impact**
 
@@ -38,15 +38,21 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  una
 			<td>Remote Code Execution - Common Bash Bypass - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "Remote Code Execution - Common Bash Bypass" (ID: <RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)</td>
-		</tr>         
+			<td>
+				This rule is merged into the original rule "Remote Code Execution -
+				Common Bash Bypass" (ID:{" "}
+				<RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)
+			</td>
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="185b5df42d1e44e0aeb8f8b8a1118614" />
 			</td>
 			<td>100916A</td>
-			<td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2</td>
+			<td>
+				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -63,4 +69,4 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  una
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
index 968037a9f6bf67c..eff22509bb0f005 100644
--- a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ This vulnerability allows unauthenticated attackers to take over customer accoun
 Adobe Commerce (CVE-2025-54236): Exploitation may allow attackers to hijack sessions, execute arbitrary commands, steal data, and disrupt storefronts, resulting in confidentiality and integrity risks for merchants. Administrators are strongly encouraged to apply vendor patches without delay.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
-      </td>
-      <td>N/A</td>
-      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
+			</td>
+			<td>N/A</td>
+			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
index 4deb26e943c3254..ffa6cd0f4a1e7e6 100644
--- a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The vulnerability allows unauthenticated attackers to potentially achieve remote
 Successful exploitation of CVE-2025-59287 could enable attackers to hijack sessions, execute arbitrary commands, exfiltrate sensitive data, and disrupt storefront operations. These actions pose significant confidentiality and integrity risks to affected environments. Administrators should apply vendor patches immediately to mitigate exposure.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
-      </td>
-      <td>N/A</td>
-      <td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
+			</td>
+			<td>N/A</td>
+			<td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
index 48b39ac6c7cfe22..a3359450691e99c 100644
--- a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The flaw is easily exploitable and allows an unauthenticated attacker with netwo
 Successful exploitation of CVE-2025-61884 may result in unauthorized access to critical business data or full exposure of information accessible through Oracle Configurator. Administrators are strongly advised to apply vendor's patches and recommended mitigations to reduce this exposure.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
-      </td>
-      <td>N/A</td>
-      <td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
+			</td>
+			<td>N/A</td>
+			<td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
index c9584fd1902891f..65a2c278f87407e 100644
--- a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
@@ -14,31 +14,31 @@ The Metro Development Server exposes an HTTP endpoint that is vulnerable to OS c
 
 **Impact**
 
-Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk. 
+Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
-      </td>
-      <td>N/A</td>
-      <td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
+			</td>
+			<td>N/A</td>
+			<td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-10-waf-release.mdx b/src/content/changelog/waf/2025-11-10-waf-release.mdx
index c442f86894866c0..6f0e60f36daadeb 100644
--- a/src/content/changelog/waf/2025-11-10-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-10-waf-release.mdx
@@ -39,7 +39,7 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>    
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -61,6 +61,6 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>        
+		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-17-waf-release.mdx b/src/content/changelog/waf/2025-11-17-waf-release.mdx
index 38a33ac01a0985b..f34a07d31022e1b 100644
--- a/src/content/changelog/waf/2025-11-17-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-17-waf-release.mdx
@@ -63,4 +63,4 @@ This vulnerability allows unauthenticated attackers to gain privileged access to
 			<td>Rule metadata description refined. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
index 668d5120066318a..92ca15cf695904c 100644
--- a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
@@ -41,4 +41,4 @@ Oracle Identity Manager (CVE-2025-61757): Exploitation could allow an unauthenti
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-11-24-waf-release.mdx b/src/content/changelog/waf/2025-11-24-waf-release.mdx
index 40fe7147867f34d..b7949e4310a105d 100644
--- a/src/content/changelog/waf/2025-11-24-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-24-waf-release.mdx
@@ -35,7 +35,9 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 				<RuleID id="b957ace6e9844bf29244401c4e2e1a2e" />
 			</td>
 			<td>N/A</td>
-			<td>FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446</td>
+			<td>
+				FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
@@ -49,7 +51,11 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - Body - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>This rule has been merged into the original rule "PHP Wrapper Injection - Body" (ID:<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)</td>
+			<td>
+				This rule has been merged into the original rule "PHP Wrapper Injection
+				- Body" (ID:
+				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -60,7 +66,11 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - URI - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>This rule has been merged into the original rule "PHP Wrapper Injection - URI" (ID:<RuleID id="9c02e585db34440da620eb668f76bd74" />)</td>
+			<td>
+				This rule has been merged into the original rule "PHP Wrapper Injection
+				- URI" (ID:
+				<RuleID id="9c02e585db34440da620eb668f76bd74" />)
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-01-waf-release.mdx b/src/content/changelog/waf/2025-12-01-waf-release.mdx
index 5c9725909eb48b5..bb91b0b857039b3 100644
--- a/src/content/changelog/waf/2025-12-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-01-waf-release.mdx
@@ -39,7 +39,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
-		</tr>    
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -49,7 +49,10 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>XSS - JS Context Escape - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "XSS - JS Context Escape" (ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)</td>
-		</tr>  
+			<td>
+				This rule is merged into the original rule "XSS - JS Context Escape"
+				(ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)
+			</td>
+		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
index 1cdc563f6d10a45..ff06da00aab5c68 100644
--- a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
@@ -52,4 +52,4 @@ New WAF rule deployed for RCE Generic Framework to block malicious POST requests
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
index 317f93bc2050154..e22e9674a2f7a29 100644
--- a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
@@ -15,6 +15,7 @@ Rule description updated to reference React – RCE – CVE-2025-55182 while ret
 **Impact**
 
 Improved classification and traceability with no change to coverage against remote code execution attempts.
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -51,4 +52,4 @@ Improved classification and traceability with no change to coverage against remo
 			<td>Rule metadata description changed. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
index 3c6833f7416480d..25b82374c113154 100644
--- a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
@@ -85,4 +85,4 @@ These updates strengthen protection against React RCE exploitation attempts and
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
index 18c75f46429d216..35ce57a85250982 100644
--- a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
@@ -38,7 +38,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
+			<td>
+				This was labeled as Generic - Server Function Source Code Exposure.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Free Ruleset</td>
@@ -49,7 +51,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
+			<td>
+				This was labeled as Generic - Server Function Source Code Exposure.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -60,7 +64,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - DoS - CVE:CVE-2025-55184</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>This was labeled as Generic – Server Function Resource Exhaustion.</td>
+			<td>
+				This was labeled as Generic – Server Function Resource Exhaustion.
+			</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-18-waf-release.mdx b/src/content/changelog/waf/2025-12-18-waf-release.mdx
index 161f57af1c49b1b..1e89c7251d32210 100644
--- a/src/content/changelog/waf/2025-12-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-18-waf-release.mdx
@@ -12,10 +12,6 @@ This week's release focuses on improvements to existing detections to enhance co
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
-
-
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -28,105 +24,124 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
-      </td>
-      <td>N/A</td>
-      <td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "Atlassian Confluence - Code Injection - CVE:CVE-2021-26084" (ID: <RuleID id="e8c550810618437c953cf3a969e0b97a" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9108ddb347b3497e9f9351640d9206e3" />
-      </td>
-      <td>N/A</td>
-      <td>PostgreSQL - SQLi - Copy - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "PostgreSQL - SQLi - COPY" (ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - Body</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - Header</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6df040f716194070a242967cfd181fb3" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - URI</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Tautology - URI - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Tautology - URI" (ID: <RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - WaitFor Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - WaitFor Function" (ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="80690005fef342e0ad6bc9af596c741e" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Equation 2 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Equation" (ID: <RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)</td>
-    </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
+			</td>
+			<td>N/A</td>
+			<td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "Atlassian Confluence - Code
+				Injection - CVE:CVE-2021-26084" (ID:{" "}
+				<RuleID id="e8c550810618437c953cf3a969e0b97a" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9108ddb347b3497e9f9351640d9206e3" />
+			</td>
+			<td>N/A</td>
+			<td>PostgreSQL - SQLi - Copy - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "PostgreSQL - SQLi - COPY"
+				(ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - Body</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - Header</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6df040f716194070a242967cfd181fb3" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - URI</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Tautology - URI - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Tautology - URI" (ID:{" "}
+				<RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - WaitFor Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - WaitFor Function"
+				(ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="80690005fef342e0ad6bc9af596c741e" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - AND/OR Digit Operator
+				Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Equation 2 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Equation" (ID:{" "}
+				<RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-12-waf-release.mdx b/src/content/changelog/waf/2026-01-12-waf-release.mdx
index f98c0a337960ed6..4c5e3ce6f9668d0 100644
--- a/src/content/changelog/waf/2026-01-12-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-12-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-12
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="72963b917ef74697b5bde02f48a1841a" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT" (ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Benchmark Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Benchmark Function" (ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="72963b917ef74697b5bde02f48a1841a" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT"
+				(ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Benchmark Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Benchmark Function"
+				(ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-15-waf-release.mdx b/src/content/changelog/waf/2026-01-15-waf-release.mdx
index 63c93358717c0b5..884dea72d886e11 100644
--- a/src/content/changelog/waf/2026-01-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-15-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-15
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - String Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - String Function" (ID: <RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Sub Query - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Sub Query" (ID: <RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - String Function" (ID:{" "}
+				<RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Sub Query - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Sub Query" (ID:{" "}
+				<RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-20-waf-release.mdx b/src/content/changelog/waf/2026-01-20-waf-release.mdx
index 0da1e57c513f3ef..1b7ca4114286eb1 100644
--- a/src/content/changelog/waf/2026-01-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-20-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-20
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Comment - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Comment" (ID: <RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Comparison - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Comparison" (ID: <RuleID id="8166da327a614849bfa29317e7907480" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comment - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Comment" (ID:{" "}
+				<RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Comparison" (ID:{" "}
+				<RuleID id="8166da327a614849bfa29317e7907480" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-26-waf-release.mdx b/src/content/changelog/waf/2026-01-26-waf-release.mdx
index cfb420d9e2809ad..030699a9d584923 100644
--- a/src/content/changelog/waf/2026-01-26-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-26-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for denial-of-service attempts t
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="aaede80b4d414dc89c443cea61680354" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="930020d567684f19b05fb35b349edbc6" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-  </tbody>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="aaede80b4d414dc89c443cea61680354" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="930020d567684f19b05fb35b349edbc6" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-02-02-waf-release.mdx b/src/content/changelog/waf/2026-02-02-waf-release.mdx
index 00ed3826f072eeb..cb989e8324478d9 100644
--- a/src/content/changelog/waf/2026-02-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-02-02-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for CVE-2025-64459 and CVE-2025-
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7a47683eacce4abd870ab2c630698ff3" />
-      </td>
-      <td>N/A</td>
-      <td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
-      </td>
-      <td>N/A</td>
-      <td>Django SQLI - CVE:CVE-2025-64459</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8f0d5c98bd24460a9305a1558d667511" />
-      </td>
-      <td>N/A</td>
-      <td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
-      <td>Block</td>
-      <td>Block</td>
-      <td>Rule metadata description refined. Detection unchanged.</td>
-  </tr>
-  </tbody>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7a47683eacce4abd870ab2c630698ff3" />
+			</td>
+			<td>N/A</td>
+			<td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
+			</td>
+			<td>N/A</td>
+			<td>Django SQLI - CVE:CVE-2025-64459</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8f0d5c98bd24460a9305a1558d667511" />
+			</td>
+			<td>N/A</td>
+			<td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
+			<td>Block</td>
+			<td>Block</td>
+			<td>Rule metadata description refined. Detection unchanged.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-02-waf-release.mdx b/src/content/changelog/waf/2026-03-02-waf-release.mdx
index 5e417a5421f9c40..34e9cc77d392db9 100644
--- a/src/content/changelog/waf/2026-03-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-02-waf-release.mdx
@@ -8,7 +8,6 @@ import { RuleID } from "~/components";
 
 This week's release introduces new detections for vulnerabilities in SmarterTools SmarterMail (CVE-2025-52691 and CVE-2026-23760), alongside improvements to an existing Command Injection (nslookup) detection to enhance coverage.
 
-
 **Key Findings**
 
 - CVE-2025-52691: SmarterTools SmarterMail mail server is vulnerable to Arbitrary File Upload, allowing an unauthenticated attacker to upload files to any location on the mail server, potentially enabling remote code execution.
@@ -62,8 +61,10 @@ Successful exploitation of these SmarterMail vulnerabilities could lead to full
 			<td>Command Injection - Nslookup - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "Command Injection - Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)</td>
+			<td>
+				This rule is merged into the original rule "Command Injection -
+				Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)
+			</td>
 		</tr>
-          
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
index 37ee704eb668c95..82b11cdd62ca859 100644
--- a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
@@ -36,11 +36,13 @@ Successful exploitation of Ivanti EPMM vulnerability allows unauthenticated remo
 				<RuleID id="5ae86a9bda0c41dbb905132f796ea2f6" />
 			</td>
 			<td>N/A</td>
-			<td>Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340</td>
+			<td>
+				Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr> 
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
diff --git a/src/content/changelog/waf/2026-03-23-waf-release.mdx b/src/content/changelog/waf/2026-03-23-waf-release.mdx
index 4b55ee8e500a59b..ca8664ddf6e1b0f 100644
--- a/src/content/changelog/waf/2026-03-23-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-23-waf-release.mdx
@@ -12,10 +12,6 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
-
-
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -28,50 +24,58 @@ This week's release focuses on new improvements to enhance coverage.
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - URI Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - Header Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="155bb67d1061479e995a38510677175f" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - Body Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
-      </td>
-      <td>N/A</td>
-      <td>PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132" (ID: <RuleID id="0f2da91cec674eb58006929e824b817c" />)</td>
-    </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - URI Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - Header Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="155bb67d1061479e995a38510677175f" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - Body Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
+			</td>
+			<td>N/A</td>
+			<td>
+				PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File
+				Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "PHP, vBulletin, jQuery
+				File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206,
+				CVE:CVE-2019-17132" (ID:{" "}
+				<RuleID id="0f2da91cec674eb58006929e824b817c" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-30-waf-release.mdx b/src/content/changelog/waf/2026-03-30-waf-release.mdx
index 1bf0c23738bd886..7bb86d5b78461dc 100644
--- a/src/content/changelog/waf/2026-03-30-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-30-waf-release.mdx
@@ -30,61 +30,63 @@ Successful exploitation of the Fortinet and Magento vulnerabilities could allow
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4f7d513cea424c2a853881982f7f95e9" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - Body</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="60d023f3be414d379428add3319731a4" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - Header - Form</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - URI</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab8a96ed13034d56a81a79e570a36147" />
-      </td>
-      <td>N/A</td>
-      <td>Magento 2 - Unrestricted file upload</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
-      </td>
-      <td>N/A</td>
-      <td>Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>    
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4f7d513cea424c2a853881982f7f95e9" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - Body</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="60d023f3be414d379428add3319731a4" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - Header - Form</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - URI</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab8a96ed13034d56a81a79e570a36147" />
+			</td>
+			<td>N/A</td>
+			<td>Magento 2 - Unrestricted file upload</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-15-waf-release.mdx b/src/content/changelog/waf/2026-04-15-waf-release.mdx
index 48b63b279a71a7e..8027bd3284ff60d 100644
--- a/src/content/changelog/waf/2026-04-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-15-waf-release.mdx
@@ -21,7 +21,7 @@ This week's release introduces a new detection for a critical Remote Code Execut
 Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code, gain administrative control over network management infrastructure, or trigger server-side resource exhaustion. Administrators are strongly encouraged to apply official vendor updates.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -31,73 +31,81 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
-      </td>
-      <td>N/A</td>
-      <td>Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
-      </td>
-      <td>N/A</td>
-      <td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>   
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
-      </td>
-      <td>N/A</td>
-      <td>Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "React Server - DOS - CVE:CVE-2026-23864 - 1" (ID: <RuleID id="aaede80b4d414dc89c443cea61680354" />)</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
-      </td>
-      <td>N/A</td>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
+			</td>
+			<td>N/A</td>
+			<td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "React Server - DOS -
+				CVE:CVE-2026-23864 - 1" (ID:{" "}
+				<RuleID id="aaede80b4d414dc89c443cea61680354" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
+			</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI (beta)</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
-      </td>
-      <td>N/A</td>
-      <td>XSS, HTML Injection - Embed Tag  - URI (beta)</td>
 			<td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-</tbody>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
+			</td>
+			<td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag - URI (beta)</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-21-waf-release.mdx b/src/content/changelog/waf/2026-04-21-waf-release.mdx
index d31b75ad221a27b..5a538a69976bfd7 100644
--- a/src/content/changelog/waf/2026-04-21-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-21-waf-release.mdx
@@ -23,7 +23,7 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -33,285 +33,266 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="ff8df24181aa4573a81be531ee159e2e" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Command Injection - Generic 8 - uri</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection. Previous description was "Command Injection - Generic 8 - uri - Beta"</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. Previous description was "Command Injection -
+				Generic 8 - uri - Beta"
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9429b63c137247faadeb8a29a15308cf" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Command Injection - Generic 8 - body - Beta</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Command Injection - Generic 8 - body" (ID:{" "}
-				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />). The rule previously known as "Command Injection - Generic 8" is now renamed to "Command Injection - Generic 8 - body".
+				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />
+				). The rule previously known as "Command Injection - Generic 8" is now
+				renamed to "Command Injection - Generic 8 - body".
 			</td>
-    </tr>		
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="85aaf5db9e0c4237b87e837e958047ed" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
+			<td>Log</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"MySQL - SQLi - Executable Comment - Body" (ID:{" "}
-				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL - SQLi - Executable Comment - Body".
+				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously
+				known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL -
+				SQLi - Executable Comment - Body".
 			</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d19cd574c4644952881a6f3a582cc559" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="407f9ec8a17348dfba3b9450a16639d3" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - URI</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d07e6dbf15664b99b37b0d2544f24211" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Magento 2 - Unrestricted file upload - 2</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>     
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="26ef21cb197b44fc8a98b7cebf170a17" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Apache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7f7bc3d28a8e43bf97bd15d68c2ac1a7" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
+			<td>Log</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Sleep Function" (ID:{" "}
 				<RuleID id="2c333735f7b24566b17cb64ef77e8d54" />)
 			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3872e5638bdf4bf0943a80394dacaeb8" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>   
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="bebce8fadfa94ccab09eb74fed4c9ece" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - URI</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7a40eed5a8654a50a2598a821dfa64df" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - uri</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="15c6b2ce033949b2a1a9f9454c62e2e7" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - header</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="fc9d800b7a724181af8d5650aab28ea1" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - body</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Probing" (ID: <RuleID id="2c20b5e8684043f48620ff77b4026c88" />)
 			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing 2 </td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This rule had duplicate detection logic and has been deprecated.
-			</td>
-    </tr> 
-    <tr>
-	      <td>Cloudflare Managed Ruleset</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This rule had duplicate detection logic and has been deprecated.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="f1771273700342758e73cf16d7aa0008" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - UNION in MSSQL - Body</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
-				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL" (ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains updated rule logic.
+				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL"
+				(ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains
+				updated rule logic.
 			</td>
-    </tr> 
-    <tr> 
-	      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - UNION - 3</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This rule had duplicate detection logic and has been deprecated.
-			</td>
-    </tr> 
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This rule had duplicate detection logic and has been deprecated.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
 			</td>
-      <td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag  - URI</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag - URI</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2635275641bf44d4bad6a2e170282f38" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Embed Tag - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="b3d033ea9f364574b0a2ec4223f4d718" />
 			</td>
-      <td>N/A</td>
-			<td>XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers</td>
-      <td>Log</td>
-      <td>Disabled</td>
+			<td>N/A</td>
 			<td>
-				This is a new detection. 
+				XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers
 			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="76c37816ef5c4997ab2080a36978def1" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - Headers</td>
-      <td>Log</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>           
-</tbody>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-27-waf-release.mdx b/src/content/changelog/waf/2026-04-27-waf-release.mdx
index 0693afdefc19da2..cff93d4886276d7 100644
--- a/src/content/changelog/waf/2026-04-27-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-27-waf-release.mdx
@@ -12,14 +12,12 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
-
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -29,7 +27,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -39,188 +37,198 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
-				This is a new detection.  This rule is merged into the original rule
+				This is a new detection. This rule is merged into the original rule
 				"PostgreSQL - SQLi - COPY - Body (ID:{" "}
-				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />). The rule previously known as "PostgreSQL - SQLi - COPY" is now renamed to "PostgreSQL - SQLi - COPY - Body".
+				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />
+				). The rule previously known as "PostgreSQL - SQLi - COPY" is now
+				renamed to "PostgreSQL - SQLi - COPY - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="71d133c374d94559aa9fdf042903de89" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9f1b1b7fd28a401b9d5c172d1036cfa6" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>  
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="8e40416659334b8ba789365755ff389e" />
 			</td>
-   			<td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR MAKE_SET/ELT - Body" (ID:{" "}
-				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
+				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />
+				). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now
+				renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="1e0d4372ee1e41b9804b2d5c346487f9" />
 			</td>
-   			<td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d2c961a164a64cf6b871c9511ac6ceca" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="4dacc0e6f32d4c5da3c2293edd471337" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Common Patterns - Body" (ID:{" "}
-				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />). The rule previously known as "SQLi - Common Patterns" is now renamed to "SQLi - Common Patterns - Body".
+				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />
+				). The rule previously known as "SQLi - Common Patterns" is now renamed
+				to "SQLi - Common Patterns - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="53a374379f2e41e9934791c1975c07b7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9efedebfc371443f9fe7308605b1b06b" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d53a791496d64700870334f4dd0ba3c7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Equation - Body" (ID:{" "}
-				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />). The rule previously known as "SQLi - Equation" is now renamed to "SQLi - Equation - Body".
+				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />
+				). The rule previously known as "SQLi - Equation" is now renamed to
+				"SQLi - Equation - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46efbd3496e64c3f902ad33d3d1c2384" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46b937649a424b7ead90f6d0e1149ea6" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="04d9182545f54ba8a4fa29fe205adbb0" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR Digit Operator Digit - Body" (ID:{" "}
-				<RuleID id="762dd334ed0b4273816e3ff13893c564" />). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
+				<RuleID id="762dd334ed0b4273816e3ff13893c564" />
+				). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is
+				now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="a24e7c15503948bc8766481aad2abbaa" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - AND/OR Digit Operator Digit - Headers</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-        </tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a24e7c15503948bc8766481aad2abbaa" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR Digit Operator Digit - Headers</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="0c55eb362df64f92a85aa46753acbc0d" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="18c9879b7e184c559d23c1652b45a97d" />
-            </td>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="18c9879b7e184c559d23c1652b45a97d" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Beta</td>
 			<td>Log</td>
@@ -228,22 +236,24 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Benchmark Function - Body" (ID:{" "}
-				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />). The rule previously known as "SQLi - Benchmark Function" is now renamed to "SQLi - Benchmark Function - Body".
+				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />
+				). The rule previously known as "SQLi - Benchmark Function" is now
+				renamed to "SQLi - Benchmark Function - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2adbc36c52324efcb4681b829889aadc" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="69564af3bc54406080deed72491b28e9" />
 			</td>
@@ -254,7 +264,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="94b1646f0b0b46ec9b96f7742aa649de" />
 			</td>
@@ -265,151 +275,166 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Comparison - Body" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />). The rule previously known as "SQLi - Comparison" is now renamed to "SQLi - Comparison - Body".
-			</td>
-		</tr>
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="455ce87681bd4200bf53456c39e3e013" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - Comparison - Headers</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-		</tr>	
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="8152816062ed47f69be0f907f4bdb492" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - Comparison - URI</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-		</tr>
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - String Concatenation - Body - Beta</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection. This rule is merged into the original rule "SQLi - String Concatenation - Headers" (ID:{" "}
-				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />).The rule previously known as "SQLi - String Concatenation - Headers" is now renamed to "SQLi - String Concatenation - Body". </td>
-		</tr>	
-        <tr>
+				<RuleID id="8166da327a614849bfa29317e7907480" />
+				). The rule previously known as "SQLi - Comparison" is now renamed to
+				"SQLi - Comparison - Body".
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="455ce87681bd4200bf53456c39e3e013" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - Headers</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
-            </td>
-            <td>N/A</td>
+			<td>
+				<RuleID id="8152816062ed47f69be0f907f4bdb492" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - URI</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Concatenation - Body - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. This rule is merged into the original rule
+				"SQLi - String Concatenation - Headers" (ID:{" "}
+				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />
+				).The rule previously known as "SQLi - String Concatenation - Headers"
+				is now renamed to "SQLi - String Concatenation - Body".{" "}
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
+			</td>
+			<td>N/A</td>
 			<td>SQLi - String Concatenation - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
-			<td>This is a new detection.(Former Id was{" "}
-				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)</td>
-		</tr>		
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - String Concatenation - URI</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection. (Former Id was{" "}
-				<RuleID id="bd19397228404b85aa3797238fae8c84" />)</td>
-		</tr>	
+			<td>Block</td>
+			<td>
+				This is a new detection.(Former Id was{" "}
+				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)
+			</td>
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
-            </td>
-            <td>N/A</td>
+			<td>
+				<RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Concatenation - URI</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. (Former Id was{" "}
+				<RuleID id="bd19397228404b85aa3797238fae8c84" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
+			</td>
+			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - SELECT Expression - Body" (ID:{" "}
-				<RuleID id="00da180570d34b5bae2121acd0023a36" />). The rule previously known as "SQLi - SELECT Expression" is now renamed to "SQLi - SELECT Expression - Body".
+				<RuleID id="00da180570d34b5bae2121acd0023a36" />
+				). The rule previously known as "SQLi - SELECT Expression" is now
+				renamed to "SQLi - SELECT Expression - Body".
 			</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="4073f7b575ff45dfb7621b43630bb223" />
-            </td>
+			<td>
+				<RuleID id="4073f7b575ff45dfb7621b43630bb223" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
-            </td>
+			<td>
+				<RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
-            </td>
+			<td>
+				<RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - ORD and ASCII- Body" (ID:{" "}
-				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />). The rule previously known as "SQLi - ORD and ASCII" is now renamed to "SQLi - ORD and ASCII- Body".
+				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />
+				). The rule previously known as "SQLi - ORD and ASCII" is now renamed to
+				"SQLi - ORD and ASCII- Body".
 			</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
-            </td>
+			<td>
+				<RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="60704f5c5513425c94cf77031d0906b6" />
-            </td>
+			<td>
+				<RuleID id="60704f5c5513425c94cf77031d0906b6" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="700613b191d3479ea2782b4e9fe4eff5" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Destructive Operations</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>					
+		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
index 8e8330ad016a2e7..a13aa934882650b 100644
--- a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows unauthenticated attackers to bypass middleware or
 We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 				<RuleID id="1de95bf6d6374e1099854278e77e4a53" />
 			</td>
 			<td>N/A</td>
-			<td>Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575</td>
-			<td>N/A</td>
-			<td>Disabled</td>
 			<td>
-				This is a new detection.
+				Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575
 			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-11-waf-release.mdx b/src/content/changelog/waf/2026-05-11-waf-release.mdx
index 043c71508d1a2ef..ab5ae2ac0485b0a 100644
--- a/src/content/changelog/waf/2026-05-11-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-11-waf-release.mdx
@@ -10,14 +10,12 @@ import { RuleID } from "~/components";
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
-
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -41,7 +39,8 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Remote Code Execution - Java Deserialization" (ID:{" "}
-				<RuleID id="36b0532eb3c941449afed2d3744305c4" />).
+				<RuleID id="36b0532eb3c941449afed2d3744305c4" />
+				).
 			</td>
 		</tr>
 	</tbody>
diff --git a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
index 6699189c3e6941d..044ad5768701d6e 100644
--- a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows remote attackers to trigger a heap buffer overflo
 We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, avoid `rewrite` directives with `?` in the replacement string followed by `set` or `if` referencing capture groups.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 				<RuleID id="2013e3e58efe4b79a26e214f7e52be73" />
 			</td>
 			<td>N/A</td>
-			<td>nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945</td>
-			<td>N/A</td>
-			<td>Block</td>
 			<td>
-				This is a new detection.
+				nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945
 			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -51,9 +51,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<td>nginx - Remote Code Execution - Heap Spray - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
+			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-20-waf-release.mdx b/src/content/changelog/waf/2026-05-20-waf-release.mdx
index f6bd07a5a23d740..e26381409165dae 100644
--- a/src/content/changelog/waf/2026-05-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-20-waf-release.mdx
@@ -15,7 +15,7 @@ import { RuleID } from "~/components";
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,9 +37,11 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>Block</td>
 			<td>
-				This rule is merged into the original rule "Sitecore - Cache Poisoning - CVE:CVE-2025-53693" (ID:{" "}
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />).
+				This rule is merged into the original rule "Sitecore - Cache Poisoning -
+				CVE:CVE-2025-53693" (ID:{" "}
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+				).
 			</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
index c086c1b5689e944..e6847cc885baddb 100644
--- a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
+++ b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
@@ -22,8 +22,8 @@ For more information, refer to [Navigation Types](/web-analytics/data-metrics/di
 
 ### Key benefits
 
-* **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
-* **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
+- **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
+- **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
 
 ### Analyze navigation types in the Cloudflare dashboard
 
diff --git a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
index 1dbfdc154f12e70..023c0a2b71c0c0c 100644
--- a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
@@ -13,13 +13,14 @@ Get started with the new models at `@cf/openai/gpt-oss-120b` and `@cf/openai/gpt
 Check out the [blog](https://blog.cloudflare.com/openai-gpt-oss-on-workers-ai) for more details about the new models, and the [`gpt-oss-120b`](/workers-ai/models/gpt-oss-120b) and [`gpt-oss-20b`](/workers-ai/models/gpt-oss-20b) model pages for more information about pricing and context windows.
 
 ## Responses API
+
 If you call the model through:
+
 - Workers Binding, it will accept/return Responses API – `env.AI.run(“@cf/openai/gpt-oss-120b”)`
 - REST API on `/run` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/run/@cf/openai/gpt-oss-120b`
 - REST API on new `/responses` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses`
 - REST API for OpenAI Compatible endpoint, it will return Chat Completions (coming soon) – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/chat/completions`
 
-
 ```
 curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses \
   -H "Content-Type: application/json" \
@@ -39,7 +40,9 @@ curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses
 ```
 
 ## Code Interpreter
+
 The model is natively trained to support stateful code execution, and we've implemented support for this feature using our [Sandbox SDK](https://github.com/cloudflare/sandbox-sdk) and [Containers](https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/). Cloudflare's Developer Platform is uniquely positioned to support this feature, so we're very excited to bring our products together to support this new use case.
 
 ## Web Search (coming soon)
+
 We are working to implement Web Search for the model, where users can bring their own Exa API Key so the model can browse the Internet.
diff --git a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
index 21359bd2975b689..4a63321c26bcb30 100644
--- a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
@@ -11,6 +11,7 @@ New state-of-the-art models have landed on Workers AI! This time, we're introduc
 As well, we're introuding a new turn detection model that enables you to detect when someone is done speaking — useful for building voice agents!
 
 Read the [blog](https://blog.cloudflare.com/workers-ai-partner-models) for more details and check out some of the new models on our platform:
+
 - [`@cf/deepgram/aura-1`](/workers-ai/models/aura-1) is a text-to-speech model that allows you to input text and have it come to life in a customizable voice
 - [`@cf/deepgram/nova-3`](/workers-ai/models/nova-3) is speech-to-text model that transcribes multilingual audio at a blazingly fast speed
 - [`@cf/pipecat-ai/smart-turn-v2`](/workers-ai/models/smart-turn-v2) helps you detect when someone is done speaking
@@ -54,4 +55,4 @@ async def text_to_speech():
 
 if __name__ == "__main__":
     asyncio.run(text_to_speech())
-```
\ No newline at end of file
+```
diff --git a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
index 27cdbf6ba1773e1..f19b116401280e9 100644
--- a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
+++ b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
@@ -12,9 +12,10 @@ We're excited to be a launch partner alongside [Google](https://developers.googl
 Now you can leverage EmbeddingGemma directly through AI Search for your RAG pipelines. EmbeddingGemma's multilingual capabilities make it perfect for global applications that need to understand and retrieve content across different languages with exceptional accuracy.
 
 To use EmbeddingGemma for your AI Search projects:
+
 1. Go to **Create** in the [AI Search dashboard](https://dash.cloudflare.com/?to=/:account/ai/ai-search)
 2. Follow the setup flow for your new RAG instance
 3. In the **Generate Index** step, open up **More embedding models** and select `@cf/google/embeddinggemma-300m` as your embedding model
 4. Complete the setup to create an AI Search
 
-Try it out and let us know what you think!
\ No newline at end of file
+Try it out and let us know what you think!
diff --git a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
index 479a67c4a458f78..0f6f06d216ab8ea 100644
--- a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
+++ b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
@@ -17,7 +17,9 @@ export default {
 		// Perform application logic in Workers here
 
 		// Sample call to an internal API running on ECS in AWS using the binding
-		const response = await env.AWS_VPC_ECS_API.fetch("https://internal-host.example.com");
+		const response = await env.AWS_VPC_ECS_API.fetch(
+			"https://internal-host.example.com",
+		);
 
 		// Additional application logic in Workers
 		return new Response();
diff --git a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
index ad672d1184483df..cd1650bd65edb75 100644
--- a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
+++ b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
@@ -8,13 +8,13 @@ date: 2025-02-07 00:00:00 UTC
 
 ![Import repo or choose template](~/assets/images/workers/choose-template-import-repo.png)
 
-You can now create a Worker by: 
-* **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker. 
-* **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker. 
+You can now create a Worker by:
 
-With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker. 
+- **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker.
+- **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker.
 
-To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
+With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker.
 
-These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9). 
+To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
 
+These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9).
diff --git a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
index f651164ee14bfd0..5b44d0f80ee3d23 100644
--- a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
+++ b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
@@ -47,4 +47,4 @@ CPU time was limited.
 For more information on the updates limits, see the documentation on [Wrangler configuration for `cpu_ms`](/workers/wrangler/configuration/#limits)
 and on [Workers CPU time limits](/workers/platform/limits/#cpu-time).
 
-For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
\ No newline at end of file
+For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
diff --git a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
index d24d77883df382f..2b8b4d848965a55 100644
--- a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
@@ -1,28 +1,28 @@
 ---
 title: Deploy a Workers application in seconds with one-click
-description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project. 
+description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project.
 products:
   - workers
 date: 2025-04-08 00:00:00 UTC
 ---
-You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project! 
+
+You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project!
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/saas-admin-template)
 
+The Deploy to Cloudflare button:
 
-The Deploy to Cloudflare button: 
-1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
-2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
+1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing.
+2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment.
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 
-
-To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL: 
+To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL:
 
 ```md
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=<YOUR_GIT_REPO_URL>)
 ```
 
-Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers. 
+Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers.
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
index b0b15c17427b454..a03418408567548 100644
--- a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
+++ b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -7,7 +7,7 @@ date: 2025-04-09
 hidden: false
 ---
 
-import { WranglerConfig } from "~/components"
+import { WranglerConfig } from "~/components";
 
 The [Workers Observability dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](/workers/observability/logs/workers-logs).
 
@@ -16,6 +16,7 @@ The **Overview** tab shows logs from all your Workers in one place. The **Invoca
 ![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png)
 
 The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:
+
 - Which paths are experiencing the most 5XX errors?
 - What is the wall time distribution by status code for my Worker?
 - What are the slowest requests, and where are they coming from?
@@ -30,6 +31,7 @@ The Query Builder can use any field that you store in your logs as a key to visu
 [Workers Logs](/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.
 
 We've introduced a number of changes during our beta period, including:
+
 - Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
 - Performance improvements to ensure no adverse impact
 - Public [API endpoints](https://developers.cloudflare.com/api/resources/workers/subresources/observability/) for broader consumption
diff --git a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
index 9361cb8dd0b783c..b452371c6b814cf 100644
--- a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
+++ b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
@@ -52,4 +52,4 @@ npx wrangler dev --test-scheduled
 curl "http://localhost:8787/cdn-cgi/handler/scheduled?cron=*+*+*+*+*"
 ```
 
-Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
\ No newline at end of file
+Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
diff --git a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
index 1adf754ef15b998..66b3abe85c67f76 100644
--- a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
+++ b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
@@ -84,4 +84,4 @@ Then test your new Durable Object locally by running `wrangler dev`:
 npx wrangler dev
 ```
 
-Consult the [Durable Objects documentation](/durable-objects/) for more details.
\ No newline at end of file
+Consult the [Durable Objects documentation](/durable-objects/) for more details.
diff --git a/src/content/changelog/workers/2025-06-05-open-next-size.mdx b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
index dc09195d36386df..f812ab669e4ae81 100644
--- a/src/content/changelog/workers/2025-06-05-open-next-size.mdx
+++ b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
@@ -15,4 +15,4 @@ This means that users will now see a decrease from 14 to 8MiB (2.3 to 1.6MiB gzi
 Users only need to update to the latest version of `@opennextjs/cloudflare` to automatically benefit from these improvements.
 
 Note that we published [CVE-2005-6087](https://github.com/opennextjs/opennextjs-cloudflare/security/advisories/GHSA-rvpw-p7vw-wj3m) for a SSRF vulnerability in the `@opennextjs/cloudflare` package.
-The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one. 
+The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one.
diff --git a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
index cdfb5847ef6dfaf..09e28a32e4a37af 100644
--- a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
+++ b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
@@ -17,8 +17,8 @@ These preview URLs are named after your branch and are posted as a comment to ea
 
 Each comment includes **two preview URLs** as shown above:
 
-* **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
-* **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
+- **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
+- **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
 
 ## How it works
 
@@ -39,7 +39,7 @@ wrangler versions upload --preview-alias staging
 
 ## Limitations while in beta
 
-* Only available on the **workers.dev** subdomain (custom domains not yet supported)
-* Requires **Wrangler v4.21.0+**
-* Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
-* Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
+- Only available on the **workers.dev** subdomain (custom domains not yet supported)
+- Requires **Wrangler v4.21.0+**
+- Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
+- Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
diff --git a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
index 69b92f1517e3f97..62563705d8ffbf1 100644
--- a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
+++ b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
@@ -1,15 +1,17 @@
 ---
 title: Increased disk space for Workers Builds
-description: Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
+description:
+  Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
   - workers
 date: 2025-08-04T01:00:00Z
 ---
-As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans. 
+
+As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans.
 
 This provides more space for larger projects, dependencies, and build artifacts while improving overall build reliability.
 
 | Metric     | Free Plan | Paid Plans |
-|------------|-----------|------------|
+| ---------- | --------- | ---------- |
 | Disk Space | 20 GB     | 20 GB      |
 
 All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including CPU, memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
index ec55122dca6b4e3..38902472bf8ef79 100644
--- a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
+++ b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
@@ -40,7 +40,7 @@ export default {
 		// Background task that should complete even after response is sent
 		cleanupTempData(env.KV_NAMESPACE);
 		return new Response("Hello, World!");
-	}
+	},
 };
 
 function cleanupTempData(kvNamespace) {
diff --git a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
index 4b869cc6a72861c..ac79e16b37b4196 100644
--- a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
+++ b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
@@ -19,7 +19,7 @@ Now, Cloudflare automatically truncates long branch names and appends a unique h
 - **Hash generation**: The hash is derived from the full branch name to ensure uniqueness
 - **Stable URLs**: The same branch always generates the same hash across all commits
 
-## Requirements and compatibility 
+## Requirements and compatibility
 
 - **Wrangler 4.30.0 or later**: This feature requires updating to wrangler@4.30.0+
-- **No configuration needed**: Works automatically with existing preview URL setups
\ No newline at end of file
+- **No configuration needed**: Works automatically with existing preview URL setups
diff --git a/src/content/changelog/workers/2025-08-11-messagechannel.mdx b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
index b73740d15413afb..c6fc102f02133c4 100644
--- a/src/content/changelog/workers/2025-08-11-messagechannel.mdx
+++ b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
@@ -17,10 +17,10 @@ using the `no_expose_global_message_channel` compatibility flag.
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log('Received message:', event.data);
+	console.log("Received message:", event.data);
 };
 
-port2.postMessage('Hello from port2!');
+port2.postMessage("Hello from port2!");
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -29,13 +29,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-* Transfer lists are currently not supported. This means that you will not be able to transfer
+- Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-	are errors serializing or deserializing the message data. Instead, the error will be thrown when
-	the `postMessage` method is called on the sending port.
-* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+  are errors serializing or deserializing the message data. Instead, the error will be thrown when
+  the `postMessage` method is called on the sending port.
+- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
index c3da28c859aaa68..63d4feab2b544fb 100644
--- a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
+++ b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
@@ -34,4 +34,4 @@ To keep using the old-style handlers, you can specify the `disable_python_no_glo
 
 </WranglerConfig>
 
-Consult the [Python Workers documentation](/workers/languages/python/) for more details.
\ No newline at end of file
+Consult the [Python Workers documentation](/workers/languages/python/) for more details.
diff --git a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
index 71100f87446e32c..0665a23c274b592 100644
--- a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
+++ b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
@@ -90,20 +90,16 @@ const scriptContent = `
   };
 `;
 
-client.workers.scripts.versions.create('my-worker', {
-  account_id: '123456789',
-  metadata: {
-    main_module: 'my-worker.mjs',
-  },
-  files: [
-    await toFile(
-      Buffer.from(scriptContent),
-      'my-worker.mjs',
-      {
-        type: "application/javascript+module",
-      }
-    )
-  ]
+client.workers.scripts.versions.create("my-worker", {
+	account_id: "123456789",
+	metadata: {
+		main_module: "my-worker.mjs",
+	},
+	files: [
+		await toFile(Buffer.from(scriptContent), "my-worker.mjs", {
+			type: "application/javascript+module",
+		}),
+	],
 });
 ```
 
@@ -115,19 +111,20 @@ Previously when creating a KV value like this:
 
 ```js
 await cf.kv.namespaces.values.update("my-kv-namespace", "key1", {
-  account_id: "123456789",
-  metadata: "my metadata",
-  value: JSON.stringify({
-    hello: "world"
-  })
+	account_id: "123456789",
+	metadata: "my metadata",
+	value: JSON.stringify({
+		hello: "world",
+	}),
 });
 ```
 
 ...and recalling it in your Worker like this:
+
 ```ts
-const value = await c.env.KV.get<{hello: string}>("key1", "json");
+const value = await c.env.KV.get<{ hello: string }>("key1", "json");
 ```
 
-You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}` 
+You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}`
 
 This is fixed in cloudflare-typescript 4.5.0 and will be fixed in cloudflare-python 4.4.0.
diff --git a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
index 26a69c93645b1c1..edafaed88b57a69 100644
--- a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
+++ b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
@@ -1,9 +1,9 @@
 ---
-title: 'Workers Static Assets: Corrected handling of double slashes in redirect rule paths'
+title: "Workers Static Assets: Corrected handling of double slashes in redirect rule paths"
 description: Corrected handling of double slashes in redirect rule paths
 date: 2025-08-15
 ---
- 
-[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed. 
+
+[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed.
 
 If you're serving Static Assets with a `_redirects` file containing a rule like `/ja/* /:splat`, paths with double slashes were previously misinterpreted as external URLs. For example, visiting `/ja//example.com` would incorrectly redirect to `https://example.com` instead of `/example.com` on your domain. This has been fixed and double slashes now correctly resolve as local paths. Note: [Cloudflare Pages](/pages/) was not affected by this issue.
diff --git a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
index 607ca9dbee7a667..bf358c54fd5a98d 100644
--- a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
+++ b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
@@ -10,8 +10,8 @@ Wrangler's error screen has received several improvements to enhance your debugg
 
 The error screen now features a refreshed design thanks to [youch](https://www.npmjs.com/package/youch), with support for both light and dark themes, improved source map resolution logic that handles missing source files more reliably, and better error cause display.
 
-| Before | After (Light) | After (Dark) |
-|--------|---------------|--------------|
+| Before                                                                             | After (Light)                                                                                        | After (Dark)                                                                                       |
+| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
 | ![Old error screen](../../../assets/images/workers/changelog/old-error-screen.png) | ![New light theme error screen](../../../assets/images/workers/changelog/new-error-screen-light.png) | ![New dark theme error screen](../../../assets/images/workers/changelog/new-error-screen-dark.png) |
 
 Try it out now with `npx wrangler@latest dev` in your Workers project.
diff --git a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
index d5f72b78d505a8f..383e128922da73e 100644
--- a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
+++ b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
@@ -3,21 +3,22 @@ title: A new, simpler REST API for Cloudflare Workers (Beta)
 description: Simpler Workers API, SDK methods, and Terraform resources for directly managing Workers, Versions, and Deployments
 date: 2025-09-04
 ---
-You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
+
+You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
 
 This new API is supported in the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) and the [Cloudflare Typescript SDK](https://github.com/cloudflare/cloudflare-typescript), allowing platform teams to manage a Worker's infrastructure in Terraform, while development teams handle code deployments from a separate repository or workflow. We also designed this API with AI agents in mind, as a clear, predictable structure is essential for them to reliably build, test, and deploy applications.
 
 ### Try it out
+
 - [**New beta API endpoints**](/api/resources/workers/subresources/beta/)
 - [**Cloudflare TypeScript SDK v5.0.0**](https://github.com/cloudflare/cloudflare-typescript)
 - [**Cloudflare Go SDK v6.0.0**](https://github.com/cloudflare/cloudflare-go)
 - [**Terraform provider v5.9.0**](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs): [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) , [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version), and [`cloudflare_workers_deployments`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_deployment) resources.
 - See full examples in our [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 
-
 ## Before: Eight+ endpoints with mixed responsibilities
-![**Before**](~/assets/images/workers/platform/api-before.png)
 
+![**Before**](~/assets/images/workers/platform/api-before.png)
 
 The existing API was originally designed for simple, one-shot script uploads:
 
@@ -40,15 +41,17 @@ This API worked for creating a basic Worker, uploading all of its code, and depl
 
 - **Several endpoints implicitly created deployments**: Simple updates like adding a secret or changing a script's content would implicitly create a new version and immediately deploy it.
 
-- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities.  This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
+- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities. This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
 
 - **Scripts used names as primary identifiers**: This meant simple renames could turn into a risky migration, requiring you to create a brand new Worker and update every reference. If you were using Terraform, this could inadvertently destroy your Worker altogether.
 
 ## After: Three resources with clear boundaries
+
 ![**After**](~/assets/images/workers/platform/api-after.png)
-The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
+The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
 
 All endpoints now use simple JSON payloads, with script content embedded as `base64`-encoded strings -- a more consistent and reliable approach than the previous `multipart/form-data` format.
+
 - **Worker**: The parent resource representing your application. It has a stable UUID and holds persistent settings like `name`, `tags`, and `logpush`. You can now create a Worker to establish its identity and settings **before** any code is uploaded.
 
 - **Version**: An immutable snapshot of your code and its specific configuration, like bindings and `compatibility_date`. Creating a new version is a safe action that doesn't affect live traffic.
@@ -66,44 +69,52 @@ All endpoints now use simple JSON payloads, with script content embedded as `bas
 Workers are now standalone resources that can be created and configured without any code. Platform teams can provision Workers with the right settings, then hand them off to development teams for implementation.
 
 #### Example: Typescript SDK
+
 ```ts
 // Step 1: Platform team creates the Worker resource (no code needed)
 const worker = await client.workers.beta.workers.create({
-  name: "payment-service",
-  account_id: "...",
-  observability: {
-    enabled: true,
-  },
+	name: "payment-service",
+	account_id: "...",
+	observability: {
+		enabled: true,
+	},
 });
 
 // Step 2: Development team adds code and creates a version later
 const version = await client.workers.beta.workers.versions.create(worker.id, {
-  account_id: "...",
-  main_module: "worker.js",
-  compatibility_date: "$today",
-  bindings: [ /*...*/ ],
-  modules: [
-    {
-      name: "worker.js",
-      content_type: "application/javascript+module",
-      content_base64: Buffer.from(scriptContent).toString("base64"),
-    },
-  ],
+	account_id: "...",
+	main_module: "worker.js",
+	compatibility_date: "$today",
+	bindings: [
+		/*...*/
+	],
+	modules: [
+		{
+			name: "worker.js",
+			content_type: "application/javascript+module",
+			content_base64: Buffer.from(scriptContent).toString("base64"),
+		},
+	],
 });
 
 // Step 3: Deploy explicitly when ready
-const deployment = await client.workers.scripts.deployments.create(worker.name, {
-  account_id: "...",
-  strategy: "percentage",
-  versions: [
-    {
-      percentage: 100,
-      version_id: version.id,
-    },
-  ],
-});
-````
+const deployment = await client.workers.scripts.deployments.create(
+	worker.name,
+	{
+		account_id: "...",
+		strategy: "percentage",
+		versions: [
+			{
+				percentage: 100,
+				version_id: version.id,
+			},
+		],
+	},
+);
+```
+
 #### Example: Terraform
+
 If you use Terraform, you can now declare the Worker in your Terraform configuration and manage configuration outside of Terraform in your Worker's [`wrangler.jsonc` file](/workers/wrangler/configuration/) and deploy code changes using [Wrangler](/workers/wrangler/).
 
 ```tf
@@ -149,6 +160,7 @@ POST /workers/scripts/{script_name}/deployments
 ```
 
 ### Settings are clearly organized by scope
+
 Configuration is now logically divided: [**Worker settings**](/api/resources/workers/subresources/beta/subresources/workers/) (like `name` and `tags`) persist across all versions, while [**Version settings**](/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) (like `bindings` and `compatibility_date`) are specific to each code snapshot.
 
 ```sh
@@ -180,13 +192,15 @@ The `/workers/workers/` path now supports addressing a Worker by both its immuta
 GET /workers/workers/29494978e03748669e8effb243cf2515  # UUID (stable for automation)
 GET /workers/workers/payment-service                  # Name (convenient for humans)
 ```
+
 This dual approach means:
-  - Developers can use readable names for debugging.
-  - Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
-  - Terraform can rename Workers without destroying and recreating them.
 
+- Developers can use readable names for debugging.
+- Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
+- Terraform can rename Workers without destroying and recreating them.
 
 ## Learn more
+
 - [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 - [API documentation](/api/resources/workers/subresources/beta/)
 - [Versions and Deployments overview](/workers/configuration/versions-and-deployments/)
@@ -195,4 +209,4 @@ This dual approach means:
 
 - The pre-existing Workers REST API remains fully supported. Once the new API exits beta, we'll provide a migration timeline with ample notice and comprehensive migration guides.
 - Existing Terraform resources and SDK methods will continue to be fully supported through the current major version.
-- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
\ No newline at end of file
+- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
diff --git a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
index 8226df15cb8f922..08db5550e9f1847 100644
--- a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
+++ b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
@@ -1,19 +1,22 @@
 ---
 title: Increased vCPU for Workers Builds on paid plans
-description: Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
+description:
+  Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
   - workers
 date: 2025-09-18
 ---
-We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.  
+
+We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.
 
 These changes continue our focus on making [Workers Builds](/workers/ci-cd/builds/) faster and more reliable.
 
-| Metric     | Free Plan | Paid Plans |
-|------------|-----------|------------|
-| CPU |  2 vCPU  |  **4 vCPU**  |
+| Metric | Free Plan | Paid Plans |
+| ------ | --------- | ---------- |
+| CPU    | 2 vCPU    | **4 vCPU** |
 
 ## Performance Improvements
-- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs 
+
+- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs
 - **2x faster multi-threaded builds**: Tools like [esbuild](https://esbuild.github.io/) and [webpack](https://webpack.js.org/) can now utilize additional cores, delivering near-linear performance scaling
 
-All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
\ No newline at end of file
+All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
index ca46348805446ca..52947b26e2a263c 100644
--- a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
+++ b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
@@ -11,11 +11,13 @@ Deploying static site to Workers is now easier. When you run `wrangler deploy [d
 ## Before and after
 
 **Before:** Required remembering multiple flags and parameters
+
 ```bash
 wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project
 ```
 
 **After:** Simple directory deployment with guided setup
+
 ```bash
 wrangler deploy dist
 # Interactive prompts handle the rest as shown in the example flow below
@@ -24,12 +26,14 @@ wrangler deploy dist
 ## What's new
 
 **Interactive prompts for missing configuration:**
+
 - Wrangler detects when you're trying to deploy a directory of static assets
 - Prompts you to confirm the deployment type
 - Asks for a project name (with smart defaults)
 - Automatically sets the compatibility date to today
 
 **Automatic configuration generation:**
+
 - Creates a `wrangler.jsonc` file with your deployment settings
 - Stores your choices for future deployments
 - Eliminates the need to remember complex command-line flags
@@ -60,4 +64,3 @@ wrangler deploy
 ## Requirements
 
 - You must use Wrangler version 4.24.4 or later in order to use this feature
-
diff --git a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
index 50813da8dd6bb74..8dc771049e2038d 100644
--- a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
@@ -10,4 +10,4 @@ We've updated our "Built with Cloudflare" button to make it easier to share that
 
 ![Built with Cloudflare](https://workers.cloudflare.com/built-with-cloudflare.svg)
 
-Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
\ No newline at end of file
+Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
diff --git a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
index ad92d184dcdbf29..b36f8560a42c020 100644
--- a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
+++ b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
@@ -5,14 +5,15 @@ products:
   - workers
 date: 2025-09-11
 ---
+
 The number of recent versions available for a Worker rollback has been increased from 10 to 100.
 
-This allows you to: 
+This allows you to:
 
-* Promote any of the 100 most recent versions to be the active deployment. 
+- Promote any of the 100 most recent versions to be the active deployment.
 
-* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+- Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
 
 You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/general/#rollback)
 
-Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 
+Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/).
diff --git a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
index b43c774dfedb8db..36d8857e5b5101a 100644
--- a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
+++ b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
@@ -1,13 +1,15 @@
 ---
 title: Preview URLs now default to opt-in
-description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in. 
+description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in.
 date: 2025-09-17
 ---
+
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers.
 
 ## One-Time Update for Workers with workers.dev Disabled
+
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
 
 Because preview URLs were historically enabled by default, users who had intentionally disabled their workers.dev route may not have realized their Worker was still accessible at a separate preview URL. This update was performed to ensure that using a preview URL is always an intentional, opt-in choice.
diff --git a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
index f4d8ebd421fb775..2e03e6d00a562e1 100644
--- a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
+++ b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
@@ -5,8 +5,8 @@ products:
   - workers
 date: 2025-09-19
 ---
- 
-[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA). 
+
+[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA).
 
 The `ratelimit` binding is now stable and recommended for all production workloads. Existing deployments using the unsafe binding will continue to function to allow for a smooth transition.
 
diff --git a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
index 0af736a78a816cc..ae4a4020187a762 100644
--- a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
+++ b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
@@ -13,7 +13,6 @@ wrangler dev --config ./web/wrangler.jsonc --config ./api/wrangler.jsonc
 ```
 
 Previously, if you ran the command above and then also ran wrangler dev for a different Worker, the Workers running in separate wrangler dev sessions could not communicate with each other. This prevented you from being able to use [Service Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) and [Tail Workers](https://developers.cloudflare.com/workers/observability/logs/tail-workers/) in local development, when running separate wrangler dev sessions.
-	
 Now, the following works as expected:
 
 ```sh
@@ -28,17 +27,17 @@ These Workers can now communicate with each other across separate dev commands,
 
 ```js title="./api/src/index.ts"
 export default {
-  async fetch(request, env) {
-    // This service binding call now works across dev commands
-    const authorized = await env.AUTH.isAuthorized(request);
+	async fetch(request, env) {
+		// This service binding call now works across dev commands
+		const authorized = await env.AUTH.isAuthorized(request);
 
-    if (!authorized) {
-      return new Response('Unauthorized', { status: 401 });
-    }
+		if (!authorized) {
+			return new Response("Unauthorized", { status: 401 });
+		}
 
-    return new Response('Hello from API Worker!', { status: 200 });
-  },
+		return new Response("Hello from API Worker!", { status: 200 });
+	},
 };
 ```
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
\ No newline at end of file
+Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
diff --git a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
index 811b7c54cb413df..efbdbc961f780a8 100644
--- a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
@@ -1,17 +1,19 @@
 ---
 title: Workers Analytics Engine adds supports for new SQL functions
-description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions! 
+description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions!
 date: 2025-10-02
 products:
   - workers-analytics-engine
 ---
+
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
+
 - `argMin()` - Returns the value associated with the minimum in a group
 - `argMax()` - Returns the value associated with the maximum in a group
 - `topK()` - Returns an array of the most frequent values in a group
@@ -20,6 +22,7 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `last_value()` - Returns the last value in an ordered set of values within a partition
 
 [**New bit functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/bit-functions/)
+
 - `bitAnd()` - Returns the bitwise AND of two expressions
 - `bitCount()` - Returns the number of bits set to one in the binary representation of a number
 - `bitHammingDistance()` - Returns the number of bits that differ between two numbers
@@ -33,24 +36,28 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `bitXor()` - Returns the bitwise exclusive-or of two expressions
 
 [**New mathematical functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/mathematical-functions/)
+
 - `abs()` - Returns the absolute value of a number
 - `log()` - Computes the natural logarithm of a number
-- `round()` - Rounds a number to a specified number of decimal places  
+- `round()` - Rounds a number to a specified number of decimal places
 - `ceil()` - Rounds a number up to the nearest integer
 - `floor()` - Rounds a number down to the nearest integer
 - `pow()` - Returns a number raised to the power of another number
 
 [**New string functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/string-functions/)
+
 - `lowerUTF8()` - Converts a string to lowercase using UTF-8 encoding
 - `upperUTF8()` - Converts a string to uppercase using UTF-8 encoding
 
 [**New encoding functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/encoding-functions/)
+
 - `hex()` - Converts a number to its hexadecimal representation
-- `bin()` - Converts a string to its binary representation 
+- `bin()` - Converts a string to its binary representation
 
 [**New type conversion functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/type-conversion-functions/)
+
 - `toUInt8()` - Converts any numeric expression, or expression resulting in a string representation of a decimal, into an unsigned 8 bit integer
 
+## Ready to get started?
 
-## Ready to get started? 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
diff --git a/src/content/changelog/workers/2025-09-26-ctx-exports.md b/src/content/changelog/workers/2025-09-26-ctx-exports.md
index ca40c83e6442e7d..19bcc4be7d98ad5 100644
--- a/src/content/changelog/workers/2025-09-26-ctx-exports.md
+++ b/src/content/changelog/workers/2025-09-26-ctx-exports.md
@@ -12,17 +12,17 @@ Example:
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class Greeter extends WorkerEntrypoint {
-  greet(name) {
-    return `Hello, ${name}!`;
-  }
+	greet(name) {
+		return `Hello, ${name}!`;
+	}
 }
 
 export default {
-  async fetch(request, env, ctx) {
-    let greeting = await ctx.exports.Greeter.greet("World")
-    return new Response(greeting);
-  }
-}
+	async fetch(request, env, ctx) {
+		let greeting = await ctx.exports.Greeter.greet("World");
+		return new Response(greeting);
+	},
+};
 ```
 
 At present, you must use [the `enable_ctx_exports` compatibility flag](/workers/configuration/compatibility-flags#enable-ctxexports) to enable this API, though it will be on by default in the future.
diff --git a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
index 374f4f9426567ed..7ae62260c3c8ae4 100644
--- a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
@@ -5,7 +5,8 @@ products:
   - workers
 date: 2025-10-09
 ---
-import { Code } from 'astro-expressive-code/components';
+
+import { Code } from "astro-expressive-code/components";
 
 You can now upload Workers with [static assets](/workers/static-assets/) (like HTML, CSS, JavaScript, images) with the [Cloudflare Terraform provider v5.11.0](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), making it even easier to deploy and manage full-stack apps with IaC.
 
@@ -15,14 +16,12 @@ You can now upload Workers with [static assets](/workers/static-assets/) (like H
 
 You can get started today with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), using either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), or the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
-
 ## Examples
 
 #### With `cloudflare_workers_script`
 
 Here's how you can use the existing [`cloudflare_workers_script`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_script) resource to upload your Worker code and assets in one shot.
 
-
 ```hcl
 resource "cloudflare_workers_script" "my_app" {
   account_id  = var.account_id
@@ -82,10 +81,11 @@ resource "cloudflare_workers_deployment" "my_app_deployment" {
 ```
 
 ## What's changed
-Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for *only* those changed files.
 
+Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for _only_ those changed files.
 
 ## Try it out
--  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
+
+- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
 - You can use either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script) to upload your Worker code and assets in one resource.
 - Or you can use the new beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version) (along with the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment)) resources to more granularly control the lifecycle of each Worker resource.
diff --git a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
index a48ee31b4bd8245..8305f662b5ae806 100644
--- a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
@@ -20,8 +20,8 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 # Examples
-Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
 #### With `cloudflare_workflow` and `cloudflare_workers_script`
 
@@ -44,10 +44,9 @@ resource "cloudflare_workflow" "workflow" {
 
 ```
 
-
 #### With `cloudflare_workflow`, and the new beta resources
-You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
+You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
 ```hcl
 
@@ -89,4 +88,5 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 ## Try it out
--  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
\ No newline at end of file
+
+- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
diff --git a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
index 7e4144ec5e29a50..60b2deb83ab1bbe 100644
--- a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
+++ b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
@@ -3,20 +3,23 @@ title: Workers Preview URL default behavior now matches your workers.dev setting
 description: If a Workers Preview URL setting is not explicitly configured, its default behavior will now match the setting of the workers.dev subdomain.
 date: 2025-10-23
 ---
+
 We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/configuration/previews/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
 
 This change is intended to provide a more intuitive and secure experience by aligning your preview URL's default state with your `workers.dev` configuration to prevent cases where a preview URL might remain public even after you disabled your `workers.dev` route.
 
 **What this means for you:**
+
 - **If neither setting is configured:** both the workers.dev route and the preview URL will default to enabled
 - **If your workers.dev route is enabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to enabled
 - **If your workers.dev route is disabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to disabled
 
-You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file). 
+You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file).
 
 **Wrangler Version Behavior**
 
 The default behavior depends on the version of Wrangler you are using. This new logic applies to the latest version. Here is a summary of the behavior across different versions:
+
 - **Before v4.34.0:** Preview URLs defaulted to enabled, regardless of the workers.dev setting.
 - **v4.34.0 up to (but not including) v4.44.0:** Preview URLs defaulted to disabled, regardless of the workers.dev setting.
 - **v4.44.0 or later:** Preview URLs now default to matching your workers.dev setting.
@@ -27,7 +30,7 @@ In July, [we introduced preview URLs to Workers](/changelog/2025-07-23-workers-p
 
 To address this, we made a [one-time update](/changelog/2025-09-17-update-preview-url-setting/) to disable preview URLs on existing Workers that had their workers.dev route disabled and changed the default behavior to be disabled for all new deployments where a preview URL setting was not explicitly configured.
 
-While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience. 
+While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience.
 
 **Securing access to `workers.dev` and preview URL endpoints**
 
diff --git a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
index 8d5b16c36bd1a5c..a4a42cacd6469f1 100644
--- a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
+++ b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
 
 Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
 
-Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag. 
+Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
 
 To use this feature, update to wrangler@4.45.0 and add bindings to your config file _without_ resource IDs e.g.:
 
diff --git a/src/content/changelog/workers/2025-10-30-builds-preview.mdx b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
index 6d384a223acd212..b18b3bf98b7469f 100644
--- a/src/content/changelog/workers/2025-10-30-builds-preview.mdx
+++ b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
@@ -10,8 +10,8 @@ You can now access [preview URLs](/workers/configuration/previews/) directly fro
 
 ![preview button](src/assets/images/changelog/workers/builds-preview-button.png)
 
-
 **What's new**
-* A **Preview** button now appears in the top-right corner of the build details page for successful builds
-* Click it to instantly open the latest preview URL
-* Matches the same experience you're familiar with from Pages
+
+- A **Preview** button now appears in the top-right corner of the build details page for successful builds
+- Click it to instantly open the latest preview URL
+- Matches the same experience you're familiar with from Pages
diff --git a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
index f405d7512be43a7..3d8cbe449a7111e 100644
--- a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
+++ b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
@@ -11,6 +11,7 @@ Wrangler now supports using the `CLOUDFLARE_ENV` [environment variable](/workers
 ## What's new
 
 **Environment selection via environment variable:**
+
 - Set `CLOUDFLARE_ENV` to specify which environment to use for Wrangler commands
 - Works with all Wrangler commands that support the `--env` flag
 - The `--env` command line argument takes precedence over the `CLOUDFLARE_ENV` environment variable
diff --git a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
index aa66f983da252d7..cbf3d01a00ba625 100644
--- a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
@@ -5,18 +5,21 @@ date: 2025-11-12
 products:
   - workers-analytics-engine
 ---
+
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
+
 - `countIf()` - count the number of rows which satisfy a provided condition
 - `sumIf()` - calculate a sum from rows which satisfy a provided condition
 - `avgIf()` - calculate an average from rows which satisfy a provided condition
 
 [**New date and time functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/date-time-functions/)
+
 - `toYear()`
 - `toMonth()`
 - `toDayOfMonth()`
@@ -36,5 +39,6 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `today()`
 - `toYYYYMM()`
 
-## Ready to get started? 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
+## Ready to get started?
+
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
diff --git a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
index 1151c4807768e2e..8a813cefea8b895 100644
--- a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
+++ b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
@@ -12,4 +12,4 @@ We've published build image policies for [Workers Builds](/workers/ci-cd/builds/
 - **Major version updates**: Before preinstalled software reaches end-of-life, we update to the next stable LTS version with 3 months’ notice.
 - **Build image version deprecation (Pages only)**: We provide 6 months’ notice before deprecation. Projects on v1 or v2 will be automatically moved to v3 on their specified deprecation dates.
 
-To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
\ No newline at end of file
+To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
diff --git a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
index 073712734586f32..f8224767a58f981 100644
--- a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
@@ -17,11 +17,11 @@ We set up a benchmark that imports common packages ([httpx](https://www.python-h
 [fastapi](https://fastapi.tiangolo.com/) and [pydantic](https://docs.pydantic.dev/latest/))
 to see how Python Workers stack up against other platforms:
 
-| Platform | Mean Cold Start (ms) |
-|----------|----------------------|
-| Cloudflare Python Workers | 1027 |
-| AWS Lambda | 2502 |
-| Google Cloud Run | 3069 |
+| Platform                  | Mean Cold Start (ms) |
+| ------------------------- | -------------------- |
+| Cloudflare Python Workers | 1027                 |
+| AWS Lambda                | 2502                 |
+| Google Cloud Run          | 3069                 |
 
 These benchmarks run continuously. You can view the results and the methodology on our [benchmark page](https://cold.edgeworker.net).
 
diff --git a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
index 47424c741ce45c1..6889ac1e31e515b 100644
--- a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
@@ -37,5 +37,4 @@ uv run pywrangler deploy
 
 Pywrangler automatically downloads and vendors the necessary packages for your Worker, and these packages are bundled with the Worker when you deploy.
 
-
 Consult the [Python packages documentation](/workers/languages/python/packages/) for full details on Pywrangler and Python package management in Workers.
diff --git a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
index 2890f89b49db4ef..46b90006bdbbd44 100644
--- a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
@@ -8,4 +8,4 @@ date: 2025-12-08
 
 When using the [Cloudflare Vite plugin](/workers/vite-plugin/) to build and deploy Workers, a Wrangler configuration file is now optional for assets-only (static) sites. If no `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` file is found, the plugin generates sensible defaults for an assets-only site. The `name` is based on the `package.json` or the project directory name, and the `compatibility_date` uses the latest date supported by your installed Miniflare version.
 
-This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
\ No newline at end of file
+This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
diff --git a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
index b18355b4e98ed59..7be9426da4e23de 100644
--- a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
@@ -103,4 +103,4 @@ export default defineConfig({
 });
 ```
 
-For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
\ No newline at end of file
+For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
diff --git a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
index 64b1e78e3c965cc..c171a822bbc5fa6 100644
--- a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
+++ b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
@@ -15,9 +15,9 @@ import { createExecutionContext } from "cloudflare:test";
 import { it, expect } from "vitest";
 
 it("can access ctx.exports", async () => {
-  const ctx = createExecutionContext();
-  const result = await ctx.exports.MyEntryPoint.myMethod();
-  expect(result).toBe("expected value");
+	const ctx = createExecutionContext();
+	const result = await ctx.exports.MyEntryPoint.myMethod();
+	expect(result).toBe("expected value");
 });
 ```
 
@@ -28,8 +28,8 @@ import { exports } from "cloudflare:workers";
 import { it, expect } from "vitest";
 
 it("can access imported exports", async () => {
-  const result = await exports.MyEntryPoint.myMethod();
-  expect(result).toBe("expected value");
+	const result = await exports.MyEntryPoint.myMethod();
+	expect(result).toBe("expected value");
 });
 ```
 
diff --git a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
index 2a6b5bff0742249..7f91b0a340dd8fd 100644
--- a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
+++ b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
@@ -6,8 +6,8 @@ products:
 date: 2025-12-19
 ---
 
-[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables 
-and bindings,  and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
+[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables
+and bindings, and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
 
 ```ts title="vite.config.ts"
 import { defineConfig } from "vite";
@@ -15,14 +15,14 @@ import { cloudflare } from "@cloudflare/vite-plugin";
 import { tanstackStart } from "@tanstack/react-start/plugin/vite";
 
 export default defineConfig({
-  plugins: [
-    cloudflare({ viteEnvironment: { name: "ssr" } }),
-    tanstackStart({
-      prerender: {
-        enabled: true,
-      },
-    }),
-  ],
+	plugins: [
+		cloudflare({ viteEnvironment: { name: "ssr" } }),
+		tanstackStart({
+			prerender: {
+				enabled: true,
+			},
+		}),
+	],
 });
 ```
 
diff --git a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
index c28886f2273eb0a..f027c8fd04d6f0d 100644
--- a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
+++ b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
@@ -26,6 +26,7 @@ Key guidance includes:
 ```
 
 </WranglerConfig>
+
 - **Generate binding types with `wrangler types`** — Never hand-write your `Env` interface. Let Wrangler generate it from your actual configuration to catch mismatches at compile time.
 - **Stream request and response bodies** — Avoid buffering large payloads in memory. Use `TransformStream` and `pipeTo` to stay within the 128 MB memory limit and improve time-to-first-byte.
 - **Use bindings, not REST APIs** — Bindings to KV, R2, D1, Queues, and other Cloudflare services are direct, in-process references with no network hop and no authentication overhead.
diff --git a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
index c153f96598e79c4..7e14d709a1a753e 100644
--- a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
@@ -8,31 +8,36 @@ Four new fields are now available on `request.cf.tlsClientAuth` in Workers for r
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
-| `certRFC9440` | String | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented. |
-| `certRFC9440TooLarge` | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`. |
-| `certChainRFC9440` | String | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
-| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`. |
+| Field                      | Type    | Description                                                                                                                                          |
+| -------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `certRFC9440`              | String  | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented.                                       |
+| `certRFC9440TooLarge`      | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`.                                                                    |
+| `certChainRFC9440`         | String  | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
+| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`.                                                             |
 
 ### Example: forwarding client certificate headers to your origin
 
 ```js
 export default {
-  async fetch(request) {
-    const tls = request.cf.tlsClientAuth;
-
-    // Only forward if cert was verified and chain is complete
-    if (!tls || !tls.certVerified || tls.certRevoked || tls.certChainRFC9440TooLarge) {
-      return new Response("Unauthorized", { status: 401 });
-    }
-
-    const headers = new Headers(request.headers);
-    headers.set("Client-Cert", tls.certRFC9440);
-    headers.set("Client-Cert-Chain", tls.certChainRFC9440);
-
-    return fetch(new Request(request, { headers }));
-  },
+	async fetch(request) {
+		const tls = request.cf.tlsClientAuth;
+
+		// Only forward if cert was verified and chain is complete
+		if (
+			!tls ||
+			!tls.certVerified ||
+			tls.certRevoked ||
+			tls.certChainRFC9440TooLarge
+		) {
+			return new Response("Unauthorized", { status: 401 });
+		}
+
+		const headers = new Headers(request.headers);
+		headers.set("Client-Cert", tls.certRFC9440);
+		headers.set("Client-Cert-Chain", tls.certChainRFC9440);
+
+		return fetch(new Request(request, { headers }));
+	},
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
index 1a9e3164168578c..c311cbdd393dadd 100644
--- a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,31 +10,33 @@ Previously, this telemetry was only available via the `Server-Timing: cfL4` resp
 
 ### New properties
 
-| Property | Type | Description |
-| --- | --- | --- |
-| `clientTcpRtt` | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`. |
-| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`. |
-| `edgeL4` | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
+| Property        | Type                | Description                                                                                                                                                                  |
+| --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `clientTcpRtt`  | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`.              |
+| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`.                    |
+| `edgeL4`        | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
 
 ### Example: Log connection quality metrics
 
 ```js
 export default {
-  async fetch(request) {
-    const cf = request.cf;
+	async fetch(request) {
+		const cf = request.cf;
 
-    const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
-    const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
-    const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
+		const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
+		const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
+		const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
 
-    console.log(`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`);
+		console.log(
+			`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`,
+		);
 
-    const headers = new Headers(request.headers);
-    headers.set("X-Client-RTT", String(rtt));
-    headers.set("X-Delivery-Rate", String(deliveryRate));
+		const headers = new Headers(request.headers);
+		headers.set("X-Client-RTT", String(rtt));
+		headers.set("X-Delivery-Rate", String(deliveryRate));
 
-    return fetch(new Request(request, { headers }));
-  },
+		return fetch(new Request(request, { headers }));
+	},
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
index 47a711a702b2fba..ffd136835ae4bc4 100644
--- a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
+++ b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
@@ -9,7 +9,7 @@ date: 2026-05-07 12:00:00 UTC
 
 Multiple security vulnerabilities were disclosed by the React team and Vercel affecting React Server Components and Next.js. These include denial of service, middleware and proxy bypass, server-side request forgery, cross-site scripting, and cache poisoning issues across a range of severity levels.
 
-**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`). 
+**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`).
 
 ## WAF protections
 
diff --git a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
index 48963056126296d..7f215858ca21722 100644
--- a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
+++ b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
@@ -10,8 +10,8 @@ date: 2025-01-15
 
 We've also added:
 
-* `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
-* Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
-* Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
+- `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
+- Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
+- Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
 
 We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks.
diff --git a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
index dbd052de60e2fc7..4f047f473ce8ee4 100644
--- a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
+++ b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
@@ -9,9 +9,9 @@ date: 2025-10-31
 
 We've raised the [Cloudflare Workflows](/workflows/) account-level limits for all accounts on the [Workers paid plan](/workers/platform/pricing/):
 
-* **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
-* **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
+- **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
+- **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
 
-These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/). 
+These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/).
 
 If your application requires a higher limit, fill out the [Limit Increase Request Form](/workers/platform/limits/) or contact your account team. Please refer to [Workflows pricing](/workflows/reference/pricing/) for more information.
diff --git a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
index 90eef81c9251ce0..e29d175b6b83ba6 100644
--- a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
+++ b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
@@ -20,4 +20,4 @@ await instance.pause(); // pauses a running workflow instance
 await instance.resume(); // resumes a paused instance
 await instance.restart(); // restarts the instance from the beginning
 await instance.terminate(); // terminates the instance immediately
-```
\ No newline at end of file
+```
diff --git a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
index 4afac919aa7d970..93eb46096142460 100644
--- a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
+++ b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
@@ -7,15 +7,15 @@ products:
 date: 2026-05-01
 ---
 
-You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime. 
+You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime.
 
 The Worker Loader loads Dynamic Workers on demand, which previously made durability challenging. Even within a Dynamic Worker, a Workflow might sleep for hours or days between steps, and by the time it resumes, the original Dynamic Worker code would no longer be in memory.
 
-The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens. 
+The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens.
 
 Because Dynamic Workers are created on-demand, you do not have to register each Workflow up front or manage them individually. Load the Workflow code in the Dynamic Worker when it is needed, and the Workflows engine handles persistence and retries behind the scenes. Your Workflow code itself is unaffected by the routing and behaves as normal.
 
-This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with: 
+This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with:
 
 - **SaaS platforms** where each tenant defines their own automation, such as onboarding sequences, approval chains, or billing retry logic.
 - **AI agent frameworks** where agents generate and execute multi-step plans at runtime, surviving restarts and waiting for human approval between tool calls.
diff --git a/src/content/compatibility-flags/allow-custom-ports.md b/src/content/compatibility-flags/allow-custom-ports.md
index 4a9cf4a9b5f6932..537127433070005 100644
--- a/src/content/compatibility-flags/allow-custom-ports.md
+++ b/src/content/compatibility-flags/allow-custom-ports.md
@@ -22,6 +22,7 @@ For example:
 ```js
 const response = await fetch("https://example.com:8000");
 ```
+
 With allow_custom_ports the above example would fetch `https://example.com:8000` rather than
 `https://example.com:443`.
 
diff --git a/src/content/compatibility-flags/enable-nodejs-http-modules.md b/src/content/compatibility-flags/enable-nodejs-http-modules.md
index b28f784408c15f9..2bfccf48ee0d939 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-modules.md
@@ -21,10 +21,10 @@ This enables compatibility with Node.js libraries and existing code that
 use the standard node:http and node:https APIs for making HTTP requests.
 The available functionality includes:
 
-* `http.request()` and `https.request()` for making HTTP/HTTPS requests
-* `http.get()` and `https.get()` for making GET requests
-* Request and response objects with standard Node.js APIs
-* Support for standard HTTP methods, headers, and options
+- `http.request()` and `https.request()` for making HTTP/HTTPS requests
+- `http.get()` and `https.get()` for making GET requests
+- Request and response objects with standard Node.js APIs
+- Support for standard HTTP methods, headers, and options
 
 See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html)
 for more details about the Node.js APIs.
diff --git a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
index 1e31b6a8b5508a4..b4b92da33a8f73b 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
@@ -20,9 +20,9 @@ server modules.
 This enables compatibility with Node.js libraries and existing code that
 use the standard Node.js HTTP server APIs. The available functionality includes:
 
-* `http.createServer()` for creating HTTP servers
-* `http.Server` class for server instances
-* `http.ServerResponse` for handling server responses
+- `http.createServer()` for creating HTTP servers
+- `http.Server` class for server instances
+- `http.ServerResponse` for handling server responses
 
 This flag must be used in combination with the `enable_nodejs_http_modules` flag
 to enable full features of `node:http`.
@@ -30,4 +30,4 @@ to enable full features of `node:http`.
 This flag is automatically enabled for Workers using
 a compatibility date of 2025-09-01 or later when `nodejs_compat` is enabled.
 
-See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
\ No newline at end of file
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
diff --git a/src/content/compatibility-flags/fetcher-no-get-put-delete.md b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
index d38f2d504089ae8..dcf2a945b94649b 100644
--- a/src/content/compatibility-flags/fetcher-no-get-put-delete.md
+++ b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
@@ -18,4 +18,3 @@ Historically, API objects that had such a `fetch()` method also had methods `get
 These methods were a very early idea from many years ago, but were never actually documented, and therefore rarely (if ever) used. Enabling the `fetcher_no_get_put_delete`, or setting a compatibility date on or after `2024-03-26` disables these methods for your Worker.
 
 This change paves a future path for you to be able to define your own custom methods using these names. Without this change, you would be unable to define your own `get`, `put`, and `delete` methods, since they would conflict with these built-in helper methods.
-
diff --git a/src/content/compatibility-flags/js-weak-refs.md b/src/content/compatibility-flags/js-weak-refs.md
index 718f8818a545c01..061ea4e608cd187 100644
--- a/src/content/compatibility-flags/js-weak-refs.md
+++ b/src/content/compatibility-flags/js-weak-refs.md
@@ -12,6 +12,7 @@ disable_flag: "disable_weak_ref"
 ---
 
 Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry) and [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef) built-ins.
+
 - `FinalizationRegistry` allows you to register a cleanup callback that runs after an object has been garbage-collected.
 - `WeakRef` creates a weak reference to an object, allowing it to be garbage-collected if no other strong references exist.
 
@@ -21,4 +22,4 @@ Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/
 
 :::caution
 These APIs are fundamentally non-deterministic. The timing and execution of garbage collection are unpredictable, and you **should not rely on them for essential program logic**. Additionally, cleanup callbacks registered with `FinalizationRegistry` may **never be executed**, including but not limited to cases where garbage collection is not triggered, or your Worker gets evicted.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/compatibility-flags/new-url-parser-implementation.md b/src/content/compatibility-flags/new-url-parser-implementation.md
index 55b21a5be67018c..9ec8017e42ea670 100644
--- a/src/content/compatibility-flags/new-url-parser-implementation.md
+++ b/src/content/compatibility-flags/new-url-parser-implementation.md
@@ -13,17 +13,17 @@ disable_flag: "url_original"
 
 The original implementation of the [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) API in Workers was not fully compliant with the [WHATWG URL Standard](https://url.spec.whatwg.org/), differing in several ways, including:
 
-* The original implementation collapsed sequences of multiple slashes into a single slash:
+- The original implementation collapsed sequences of multiple slashes into a single slash:
 
   `new URL("https://example.com/a//b").toString() === "https://example.com/a/b"`
 
-* The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
+- The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
 
-* The original implementation would percent-encode or percent-decode certain content differently:
+- The original implementation would percent-encode or percent-decode certain content differently:
 
   `new URL("https://example.com/a%40b?c d%20e?f").toString() === "https://example.com/a@b?c+d+e%3Ff"`
 
-* The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
+- The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
 
 Set the compatibility date of your Worker to a date after `2022-10-31` or enable the `url_standard` compatibility flag to opt-in the fully spec compliant `URL` API implementation.
 
diff --git a/src/content/compatibility-flags/nodejs-compat.md b/src/content/compatibility-flags/nodejs-compat.md
index 80bfc4fec1b0734..6eb72d18070e7de 100644
--- a/src/content/compatibility-flags/nodejs-compat.md
+++ b/src/content/compatibility-flags/nodejs-compat.md
@@ -14,12 +14,12 @@ Enables [Node.js APIs](/workers/runtime-apis/nodejs/) in the Workers Runtime.
 
 Note that some Node.js APIs are only enabled if your Worker's compatibility date is set to on or after the following dates:
 
-| Node.js API | Enabled after  |
-|---|---|
-| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)  | `2025-09-01`  |
-| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules)  | `2025-08-15`  |
-| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)  | `2025-04-01`  |
-| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)  | `2024-12-02`  |
+| Node.js API                                                                                                                    | Enabled after |
+| ------------------------------------------------------------------------------------------------------------------------------ | ------------- |
+| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)                                 | `2025-09-01`  |
+| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules) | `2025-08-15`  |
+| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)                                 | `2025-04-01`  |
+| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)       | `2024-12-02`  |
 
 When enabling `nodejs_compat`, we recommend using the latest version of [Wrangler CLI](/workers/wrangler/), and the latest compatiblity date, in order to maximize compatibility. Some older versions of Wrangler inject additional polyfills that are no longer neccessary, as they are provided by the Workers runtime, if your Worker is using a more recent compatibility date.
 
diff --git a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
index 82a917d18ac5162..458d6f154b4f789 100644
--- a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
+++ b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
@@ -13,26 +13,29 @@ enable_flag: "queue_consumer_no_wait_for_wait_until"
 By default, [Queues](/queues/) Consumer Workers acknowledge messages only after promises passed to [`ctx.waitUntil()`](/workers/runtime-apis/context) have resolved. This behavior can cause queue consumers which utilize `ctx.waitUntil()` to process messages slowly. The default behavior is documented in the [Queues Consumer Configuration Guide](/queues/configuration/javascript-apis#consumer).
 
 This Consumer Worker is an example of a Worker which utilizes `ctx.waitUntil()`. Under the default behavior, this consumer Worker will only acknowledge a batch of messages after the sleep function has resolved.
+
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    // omitted
-  },
-
-  async queue(batch, env, ctx) {
-    console.log(`received batch of ${batch.messages.length} messages to queue ${batch.queue}`);
-    for (let i = 0; i < batch.messages.length; ++i) {
-      console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
-    }
-    ctx.waitUntil(sleep(30 * 1000));
-  }
+	async fetch(request, env, ctx) {
+		// omitted
+	},
+
+	async queue(batch, env, ctx) {
+		console.log(
+			`received batch of ${batch.messages.length} messages to queue ${batch.queue}`,
+		);
+		for (let i = 0; i < batch.messages.length; ++i) {
+			console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
+		}
+		ctx.waitUntil(sleep(30 * 1000));
+	},
 };
 
 function sleep(ms) {
-  return new Promise(resolve => setTimeout(resolve, ms));
+	return new Promise((resolve) => setTimeout(resolve, ms));
 }
 ```
 
 If the `queue_consumer_no_wait_for_wait_until` flag is enabled, Queues consumers will no longer wait for promises passed to `ctx.waitUntil()` to resolve before acknowledging messages. This can improve the performance of queue consumers which utilize `ctx.waitUntil()`. With the flag enabled, in the above example, the consumer Worker will acknowledge the batch without waiting for the sleep function to resolve.
 
-Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
\ No newline at end of file
+Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
diff --git a/src/content/compatibility-flags/queues-json-messages.md b/src/content/compatibility-flags/queues-json-messages.md
index ed871f0ed83b10b..468e5bc0c452ce5 100644
--- a/src/content/compatibility-flags/queues-json-messages.md
+++ b/src/content/compatibility-flags/queues-json-messages.md
@@ -11,4 +11,4 @@ enable_flag: "queues_json_messages"
 disable_flag: "no_queues_json_messages"
 ---
 
-With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
\ No newline at end of file
+With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
diff --git a/src/content/compatibility-flags/request-signal.md b/src/content/compatibility-flags/request-signal.md
index e60e43e66403e2f..75a494da250906c 100644
--- a/src/content/compatibility-flags/request-signal.md
+++ b/src/content/compatibility-flags/request-signal.md
@@ -5,4 +5,4 @@ enable_flag: "enable_request_signal"
 disable_flag: "disable_request_signal"
 ---
 
-When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
\ No newline at end of file
+When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
diff --git a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
index 994a6a724e2f465..3cdf43761777395 100644
--- a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
+++ b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
@@ -20,12 +20,12 @@ User code should never try to reuse an `ArrayBuffer` that has been passed into a
 let reader = readable.getReader({ mode: "byob" });
 let arrayBufferView = new Uint8Array(4096);
 while (true) {
-  let result = await reader.read(arrayBufferView);
-  if (result.done) break;
-  // Optionally something with `result` here.
-  // Re-use the same memory for the next `read()` by creating
-  // a new Uint8Array backed by the result's ArrayBuffer.
-  arrayBufferView = new Uint8Array(result.value.buffer);
+	let result = await reader.read(arrayBufferView);
+	if (result.done) break;
+	// Optionally something with `result` here.
+	// Re-use the same memory for the next `read()` by creating
+	// a new Uint8Array backed by the result's ArrayBuffer.
+	arrayBufferView = new Uint8Array(result.value.buffer);
 }
 ```
 
diff --git a/src/content/compatibility-flags/strict-crypto.md b/src/content/compatibility-flags/strict-crypto.md
index 91a77815dd82fde..17274d7e485ef60 100644
--- a/src/content/compatibility-flags/strict-crypto.md
+++ b/src/content/compatibility-flags/strict-crypto.md
@@ -14,6 +14,7 @@ disable_flag: "no_strict_crypto_checks"
 ---
 
 Perform additional error checking in the Web Crypto API to conform with the specification and reject possibly unsafe key parameters:
+
 - For RSA key generation, key sizes are required to be multiples of 128 bits as boringssl may otherwise truncate the key.
 - The size of imported RSA keys must be at least 256 bits and at most 16384 bits, as with newly generated keys.
 - The public exponent for imported RSA keys is restricted to the commonly used values `[3, 17, 37, 65537]`.
diff --git a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
index 15ea7891dc4fcad..3b380e857412453 100644
--- a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
+++ b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
@@ -19,4 +19,3 @@ attribute is encountered that is not recognized.
 
 When the `ignore_unrecognized_import_assertion` flag is set, Workers will
 ignore unrecognized import attributes.
-
diff --git a/src/content/compatibility-flags/to-string-tag.md b/src/content/compatibility-flags/to-string-tag.md
index 1de8e533db3f8bb..6fc298a87c182de 100644
--- a/src/content/compatibility-flags/to-string-tag.md
+++ b/src/content/compatibility-flags/to-string-tag.md
@@ -13,5 +13,5 @@ disable_flag: "do_not_set_tostring_tag"
 
 A change was made to set the Symbol.toStringTag on all Workers API objects
 in order to fix several spec compliance bugs. Unfortunately,
-this change was more breaking than anticipated. The `do_not_set_tostring_tag`  compat
+this change was more breaking than anticipated. The `do_not_set_tostring_tag` compat
 flag restores the original behavior with compatibility dates of 2024-09-26 or earlier.
diff --git a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
index ff6e300d56a8451..b94637375b11410 100644
--- a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
+++ b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
@@ -21,7 +21,7 @@ For an example of how this change could break existing code, consider code that
 ```js
 const usp = new URLSearchParams();
 // ...
-['abc', 'xyz'].forEach(usp.delete.bind(usp));
+["abc", "xyz"].forEach(usp.delete.bind(usp));
 ```
 
 The `forEach()` automatically passes multiple parameters to the function that is passed in. Prior to the addition of the new standard parameters, these extra arguments would have been ignored.
@@ -31,5 +31,5 @@ Now, however, the additional arguments have meaning and change the behavior of t
 ```js
 const usp = new URLSearchParams();
 // ...
-['abc', 'xyz'].forEach((key) => usp.delete(key));
-```
\ No newline at end of file
+["abc", "xyz"].forEach((key) => usp.delete(key));
+```
diff --git a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
index be603aaba1a62ba..5a0f4a50358133e 100644
--- a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
+++ b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
@@ -19,12 +19,16 @@ Previously, receiving a server-initiated Close frame left the WebSocket in `CLOS
 const [client, server] = Object.values(new WebSocketPair());
 server.accept();
 
-server.addEventListener("close", (event) => {
-  // readyState is already CLOSED — no need to call server.close().
-  console.log(server.readyState); // WebSocket.CLOSED
-  console.log(event.code); // 1000
-  console.log(event.wasClean); // true
-}, { once: true });
+server.addEventListener(
+	"close",
+	(event) => {
+		// readyState is already CLOSED — no need to call server.close().
+		console.log(server.readyState); // WebSocket.CLOSED
+		console.log(event.code); // 1000
+		console.log(event.wasClean); // true
+	},
+	{ once: true },
+);
 ```
 
 If you do still call `close()` inside the handler, the call is silently ignored. This means existing code that manually replies to Close frames will not break when you update your compatibility date.
@@ -37,14 +41,18 @@ const [client, server] = Object.values(new WebSocketPair());
 // Opt into half-open mode for proxying
 server.accept({ allowHalfOpen: true });
 
-server.addEventListener("close", (event) => {
-  // With allowHalfOpen true, readyState is still CLOSING here,
-  // giving you time to coordinate the close on the other side.
-  console.log(server.readyState); // WebSocket.CLOSING
+server.addEventListener(
+	"close",
+	(event) => {
+		// With allowHalfOpen true, readyState is still CLOSING here,
+		// giving you time to coordinate the close on the other side.
+		console.log(server.readyState); // WebSocket.CLOSING
 
-  // Manually close when ready.
-  server.close(1000, "done");
-}, { once: true });
+		// Manually close when ready.
+		server.close(1000, "done");
+	},
+	{ once: true },
+);
 ```
 
 Note that there is no corresponding option to the `WebSocket` constructor. WebSockets constructed with `new WebSocket` will always auto-reply to closes after this flag takes effect. WebSockets constructed this way are automatically "accepted", so there is no opportunity to pass the option to `accept()`. If you are creating a WebSocket with `new WebSocket`, but you need half-open behavior, you will need to switch to using `fetch()` instead.
@@ -55,10 +63,10 @@ let ws = new WebSocket("wss://example.com");
 
 // But you can do this instead:
 let resp = await fetch("https://example.com", {
-  headers: { "Upgrade": "websocket" }
+	headers: { Upgrade: "websocket" },
 });
 if (!resp.webSocket) {
-  throw new Error("WebSocket handshake not accepted");
+	throw new Error("WebSocket handshake not accepted");
 }
 let ws = resp.webSocket;
 ws.accept({ allowHalfOpen: true });
diff --git a/src/content/compatibility-flags/web-socket-compression.md b/src/content/compatibility-flags/web-socket-compression.md
index c73d329ee01a83e..9949b65656e428f 100644
--- a/src/content/compatibility-flags/web-socket-compression.md
+++ b/src/content/compatibility-flags/web-socket-compression.md
@@ -15,4 +15,4 @@ The Workers runtime did not support WebSocket compression when the initial WebSo
 
 If the flag is present, the Workers runtime is capable of using WebSocket Compression on both inbound and outbound WebSocket connections.
 
-Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
\ No newline at end of file
+Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
diff --git a/src/content/compatibility-flags/websocket-standard-binary-type.md b/src/content/compatibility-flags/websocket-standard-binary-type.md
index 81e8b8883ea49f5..6e389dad36862eb 100644
--- a/src/content/compatibility-flags/websocket-standard-binary-type.md
+++ b/src/content/compatibility-flags/websocket-standard-binary-type.md
@@ -17,7 +17,7 @@ The `binaryType` property itself is available on every `WebSocket` regardless of
 
 ```js
 const resp = await fetch("https://example.com", {
-  headers: { Upgrade: "websocket" },
+	headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -26,7 +26,7 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-  // event.data is an ArrayBuffer for binary frames.
+	// event.data is an ArrayBuffer for binary frames.
 });
 ```
 
diff --git a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
index 9d993472b94bcb7..e0b79d3a85a05ed 100644
--- a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
+++ b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
@@ -19,13 +19,13 @@ Previously, throwing a `NonRetryableError` with a custom message would result in
 import { WorkflowEntrypoint, NonRetryableError } from "cloudflare:workers";
 
 export class MyWorkflow extends WorkflowEntrypoint {
-  async run(event, step) {
-    await step.do("my-step", async () => {
-      throw new NonRetryableError("custom error message");
-      // Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
-      // With this flag: error.message === "custom error message"
-    });
-  }
+	async run(event, step) {
+		await step.do("my-step", async () => {
+			throw new NonRetryableError("custom error message");
+			// Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
+			// With this flag: error.message === "custom error message"
+		});
+	}
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
index 17806e9fea110e3..39b0c719c6a6edd 100644
--- a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
+++ b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
@@ -34,10 +34,10 @@ Define protected routes in `wrangler.jsonc`:
 			{
 				"pattern": "/premium/*",
 				"amount": "0.01",
-				"description": "Access to premium content for 1 hour"
-			}
-		]
-	}
+				"description": "Access to premium content for 1 hour",
+			},
+		],
+	},
 }
 ```
 
@@ -55,7 +55,7 @@ With [Bot Management](/bots/), the proxy can charge crawlers while keeping the s
 	"amount": "0.25",
 	"description": "Content access for 1 hour",
 	"bot_score_threshold": 30,
-	"except_detection_ids": [120623194, 117479730]
+	"except_detection_ids": [120623194, 117479730],
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/x402/index.mdx b/src/content/docs/agents/agentic-payments/x402/index.mdx
index 4ae0cb18581f35d..bc12467db9b9995 100644
--- a/src/content/docs/agents/agentic-payments/x402/index.mdx
+++ b/src/content/docs/agents/agentic-payments/x402/index.mdx
@@ -45,8 +45,8 @@ The facilitator does not hold funds. It verifies and broadcasts the client's pre
 
 x402 uses payment **schemes** to define how a payment is constructed and settled on a given network.
 
-| Scheme                                                                                    | Networks                                 | Description                                                                                                                       |
-| ----------------------------------------------------------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Scheme                                                                                           | Networks                                 | Description                                                                                                                       |
+| ------------------------------------------------------------------------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | [`exact`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact.md) | EVM, Solana, Aptos, Stellar, Hedera, Sui | Transfers a fixed token amount — typically [ERC-20](https://eips.ethereum.org/EIPS/eip-20) USDC on EVM — to the merchant address. |
 | [`upto`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/upto/scheme_upto.md)    | EVM                                      | Authorizes a maximum amount; the actual charge is determined at settlement time based on resource consumption.                    |
 
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
index 25135f65b7f3f89..a766be9a51e7892 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
@@ -38,4 +38,4 @@ You may have both of the following enabled:
 - A selection of AI crawlers to be charged through AI Crawl Control's pay per crawl
 - Bot configuration option to [Block AI Bots](/bots/get-started/bot-fight-mode/#block-ai-bots).
 
-Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
\ No newline at end of file
+Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
index 8e8f5e9661c32ef..57d1c103c3178a0 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
@@ -9,7 +9,14 @@ products:
   - ai-crawl-control
 ---
 
-import { GlossaryTooltip, Example, Steps, Tabs, TabItem, DashButton } from "~/components";
+import {
+	GlossaryTooltip,
+	Example,
+	Steps,
+	Tabs,
+	TabItem,
+	DashButton,
+} from "~/components";
 
 AI Crawl Control works alongside other Cloudflare products, such as Cloudflare [Web Application Firewall (WAF)](/waf/). WAF checks incoming web and API requests, and filters undesired traffic based on rules. [WAF custom rules](/waf/custom-rules/) allow you to perform certain actions such as enforcing <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip>.
 
@@ -132,4 +139,3 @@ Any additions you make are preserved when you subsequently update crawler action
 :::caution
 Changes made directly to the WAF rule are not reflected back in the AI Crawl Control dashboard. Use the **Crawlers** tab as your primary interface, and reserve direct WAF edits for cases where the dashboard does not cover your requirements.
 :::
-
diff --git a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
index 62af2e2d1d983dc..8ed8a785d4df4d8 100644
--- a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
+++ b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
@@ -65,12 +65,12 @@ Visualize crawler activity patterns over the selected time period. Use the view
 
 You can group the data by different dimensions:
 
-| Dimension    | Description                                                                              |
-| ------------ | ---------------------------------------------------------------------------------------- |
-| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).      |
-| **Category** | Analyze crawlers by their purpose or type.                                               |
-| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site.  |
-| **Host**     | Break down activity across multiple subdomains.                                          |
+| Dimension    | Description                                                                             |
+| ------------ | --------------------------------------------------------------------------------------- |
+| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).     |
+| **Category** | Analyze crawlers by their purpose or type.                                              |
+| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site. |
+| **Host**     | Break down activity across multiple subdomains.                                         |
 
 :::note
 The Data transfer view shows `edgeResponseBytes`. Some crawlers may show higher data transfer per request than others, depending on the content they request.
@@ -93,11 +93,11 @@ The **Content Format** chart shows what content types AI systems request versus
 
 The chart includes three views:
 
-| View          | Description                                                                 |
-| ------------- | --------------------------------------------------------------------------- |
-| **Comparison** | A grouped bar chart comparing requested content types versus served content types |
-| **Request Type** | Breakdown of requests by Accept header                                      |
-| **Response Type** | Breakdown of responses by Content-Type header                              |
+| View              | Description                                                                       |
+| ----------------- | --------------------------------------------------------------------------------- |
+| **Comparison**    | A grouped bar chart comparing requested content types versus served content types |
+| **Request Type**  | Breakdown of requests by Accept header                                            |
+| **Response Type** | Breakdown of responses by Content-Type header                                     |
 
 ### Top referrers
 
diff --git a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
index 37400acba85f698..2892e1f8c9c5aa7 100644
--- a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
+++ b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
@@ -8,7 +8,15 @@ products:
   - ai-crawl-control
 ---
 
-import { Steps, GlossaryTooltip, Tabs, TabItem, Example, Plan, DashButton } from "~/components";
+import {
+	Steps,
+	GlossaryTooltip,
+	Tabs,
+	TabItem,
+	Example,
+	Plan,
+	DashButton,
+} from "~/components";
 
 AI Crawl Control enables you to take specific action for each AI crawler.
 
@@ -25,13 +33,13 @@ To manage AI crawlers:
 
 The **Crawlers** tab displays a table of AI crawlers that are requesting access to your content, and how they interact with your pages. The table provides the following information.
 
-| Column                | Details                                                                                                                                                                                    |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                                  |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                          |
-| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control.    |
-| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                               |
-| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).                |
+| Column                | Details                                                                                                                                                                                 |
+| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                               |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                       |
+| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control. |
+| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                            |
+| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).             |
 
 :::note[Quality of AI crawler detection]
 On the free plan, AI Crawl Control identifies AI crawlers based on their [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent). This enables AI Crawl Control to detect well-known, self-identifying AI crawlers.
diff --git a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
index 8fbf42ce0120ba3..175f3072a93187a 100644
--- a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
+++ b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
@@ -29,4 +29,4 @@ Pay per crawl is currently in closed beta.
 To find out how to join the beta program, reach out to us at [Pay per crawl signup](http://www.cloudflare.com/paypercrawl-signup/), or contact your account executive if you are an existing Enterprise customer.
 
 To learn more about pay per crawl, refer to Cloudflare blog: [Introducing pay per crawl: enabling content owners to charge AI crawlers for access](https://blog.cloudflare.com/introducing-pay-per-crawl/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
index f406e702ce30ed6..6673c210889beae 100644
--- a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
+++ b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
@@ -42,12 +42,12 @@ The values in all tables and metrics will update according to your filters.
 
 The **Robots.txt availability** table shows the historical request frequency and health status of `robots.txt` files across your hostnames over the selected time frame.
 
-| Column          | Description                                                                                                                                                                                                                    |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                      |
+| Column          | Description                                                                                                                                                                                                                       |
+| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                 |
 | Requests        | The total number of requests made to this path. Requests are broken down into:<br/>- **Successful:** HTTP status codes below 400 (including **200 OK** and redirects).<br/>- **Unsuccessful:** HTTP status codes of 400 or above. |
-| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                       |
-| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                          |
+| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                          |
+| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                             |
 
 From this table, you can take the following actions:
 
diff --git a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
index 1122f0a6d7d639e..d285d0714cd426d 100644
--- a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
+++ b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
@@ -156,12 +156,12 @@ The feature parses the `<link rel="canonical">` tag from the `<head>` section of
 ```html
 <!DOCTYPE html>
 <html>
-<head>
-  <link rel="canonical" href="https://example.com/current-version">
-</head>
-<body>
-  <!-- Page content -->
-</body>
+	<head>
+		<link rel="canonical" href="https://example.com/current-version" />
+	</head>
+	<body>
+		<!-- Page content -->
+	</body>
 </html>
 ```
 
@@ -169,10 +169,10 @@ Both absolute and relative URLs are supported:
 
 ```html
 <!-- Absolute URL -->
-<link rel="canonical" href="https://example.com/page">
+<link rel="canonical" href="https://example.com/page" />
 
 <!-- Relative URL (resolved against request URL) -->
-<link rel="canonical" href="/current-page">
+<link rel="canonical" href="/current-page" />
 ```
 
 ### Interaction with other redirect features
diff --git a/src/content/docs/ai-gateway/configuration/authentication.mdx b/src/content/docs/ai-gateway/configuration/authentication.mdx
index 780ade1a3e222cc..e848745b780263d 100644
--- a/src/content/docs/ai-gateway/configuration/authentication.mdx
+++ b/src/content/docs/ai-gateway/configuration/authentication.mdx
@@ -66,7 +66,7 @@ const openai = createOpenAI({
 
 :::note
 When an AI Gateway is accessed from a Cloudflare Worker using a **binding**, the `cf-aig-authorization` header does not need to be manually included.  
-Requests made through bindings are **pre-authenticated** within the associated Cloudflare account. 
+Requests made through bindings are **pre-authenticated** within the associated Cloudflare account.
 :::
 
 The following table outlines gateway behavior based on the authentication settings and header status:
diff --git a/src/content/docs/ai-gateway/configuration/custom-providers.mdx b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
index 6da29fa5366081a..0bc6f1543a3b8fe 100644
--- a/src/content/docs/ai-gateway/configuration/custom-providers.mdx
+++ b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
@@ -373,12 +373,12 @@ Everything after `custom-{slug}/` in your request URL is appended directly to th
 
 ### Choosing between Unified API and provider-specific endpoint
 
-| | Unified API (`/compat`) | Provider-specific endpoint |
-|---|---|---|
-| **Best for** | Providers with OpenAI-compatible APIs | Providers with any API structure |
-| **Request format** | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
-| **Path control** | Fixed to `/compat/chat/completions` | Full control over the upstream path |
-| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}` | URL path: `/custom-{slug}/{path}` |
+|                                 | Unified API (`/compat`)                           | Provider-specific endpoint                |
+| ------------------------------- | ------------------------------------------------- | ----------------------------------------- |
+| **Best for**                    | Providers with OpenAI-compatible APIs             | Providers with any API structure          |
+| **Request format**              | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
+| **Path control**                | Fixed to `/compat/chat/completions`               | Full control over the upstream path       |
+| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}`       | URL path: `/custom-{slug}/{path}`         |
 
 Use the **Unified API** when your custom provider accepts the OpenAI-compatible `/chat/completions` request format. This is the simplest option and works well with OpenAI SDKs.
 
@@ -425,10 +425,12 @@ The following examples show how to configure `base_url` and construct request UR
 Many providers follow the OpenAI convention of hosting their API at `{domain}/v1/chat/completions`.
 
 **Configuration:**
+
 - `slug`: `my-openai-compat`
 - `base_url`: `https://api.example-provider.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-openai-compat/v1/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -448,6 +450,7 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-op
 | Upstream URL | `https://api.example-provider.com/v1/chat/completions` |
 
 Since this provider is OpenAI-compatible, you could also use the Unified API:
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -463,10 +466,12 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/
 Some providers use API paths that don't follow the `/v1/` convention. For example, a provider whose chat endpoint is at `https://api.custom-ai.com/api/coding/paas/v4/chat/completions`.
 
 **Configuration:**
+
 - `slug`: `custom-ai`
 - `base_url`: `https://api.custom-ai.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-custom-ai/api/coding/paas/v4/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -494,10 +499,12 @@ For providers with non-standard paths, you must use the provider-specific endpoi
 If you host your own model behind a reverse proxy or on a platform that adds a path prefix, include only the fixed prefix portion in `base_url` if all your endpoints share it. Otherwise, keep `base_url` as just the domain.
 
 **Configuration (domain-only `base_url`):**
+
 - `slug`: `internal-llm`
 - `base_url`: `https://ml.internal.example.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-internal-llm/serving/models/my-model:predict \
   -H "Authorization: Bearer $INTERNAL_API_KEY" \
@@ -520,10 +527,12 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-inter
 When using the OpenAI SDK to connect to a custom provider through AI Gateway, set the SDK's `base_url` to the gateway's provider-specific endpoint path (up to and including the API version prefix that your provider expects).
 
 **Configuration:**
+
 - `slug`: `alt-provider`
 - `base_url`: `https://api.alt-provider.com`
 
 **Python (OpenAI SDK):**
+
 ```python title="Using OpenAI SDK with a custom provider"
 from openai import OpenAI
 
@@ -559,14 +568,14 @@ response = client.chat.completions.create(
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1003,
-      "message": "A custom provider with this slug already exists",
-      "path": ["body", "slug"]
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1003,
+			"message": "A custom provider with this slug already exists",
+			"path": ["body", "slug"]
+		}
+	]
 }
 ```
 
@@ -576,13 +585,13 @@ Each custom provider slug must be unique within your account. Choose a different
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1004,
-      "message": "Custom Provider not found"
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1004,
+			"message": "Custom Provider not found"
+		}
+	]
 }
 ```
 
@@ -592,14 +601,14 @@ The specified provider ID does not exist or you don't have access to it. Verify
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1002,
-      "message": "base_url must be a valid HTTPS URL starting with https://",
-      "path": ["body", "base_url"]
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1002,
+			"message": "base_url must be a valid HTTPS URL starting with https://",
+			"path": ["body", "base_url"]
+		}
+	]
 }
 ```
 
@@ -636,4 +645,4 @@ If you receive a 404 from the upstream provider, the most common cause is an inc
 - [BYOK (Store Keys)](/ai-gateway/configuration/bring-your-own-keys/)
 - [Dynamic routing](/ai-gateway/features/dynamic-routing/)
 - [Caching](/ai-gateway/features/caching/)
-- [Rate limiting](/ai-gateway/features/rate-limiting/)
\ No newline at end of file
+- [Rate limiting](/ai-gateway/features/rate-limiting/)
diff --git a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
index 1583cae3d3cb063..591a2b78db5305d 100644
--- a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
+++ b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
@@ -8,6 +8,7 @@ sidebar:
 products:
   - ai-gateway
 ---
+
 import { DashButton } from "~/components";
 
 Human feedback is a valuable metric to assess the performance of your AI models. By incorporating human feedback, you can gain deeper insights into how the model's responses are perceived and how well it performs from a user-centric perspective. This feedback can then be used in evaluations to calculate performance metrics, driving optimization and ultimately enhancing the reliability, accuracy, and efficiency of your AI application.
diff --git a/src/content/docs/ai-gateway/features/dlp/index.mdx b/src/content/docs/ai-gateway/features/dlp/index.mdx
index fed23035a215241..1a2da0f59706eda 100644
--- a/src/content/docs/ai-gateway/features/dlp/index.mdx
+++ b/src/content/docs/ai-gateway/features/dlp/index.mdx
@@ -59,11 +59,11 @@ Because of this buffering:
 
 DLP scanning runs after a cache miss, when AI Gateway forwards the request to the provider and receives a response. The following table describes how each DLP outcome affects caching:
 
-| DLP outcome | Response cached | Behavior |
-| --- | --- | --- |
-| Pass (no findings) | Yes | The response is cached normally according to your gateway cache settings. |
-| Flag | Yes | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
-| Block | No | The provider response is discarded and replaced with a DLP error response (status `400`). |
+| DLP outcome        | Response cached | Behavior                                                                                                                                                                  |
+| ------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pass (no findings) | Yes             | The response is cached normally according to your gateway cache settings.                                                                                                 |
+| Flag               | Yes             | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
+| Block              | No              | The provider response is discarded and replaced with a DLP error response (status `400`).                                                                                 |
 
 **Cache hits skip DLP scanning.** When a subsequent identical request matches a cached response, AI Gateway serves it directly from cache without re-running DLP. This is safe because only responses that already passed DLP (or were flagged, not blocked) are cached. However, if you update your DLP policies after a response has been cached, the cached response is not re-evaluated. It continues to be served until the cache TTL expires.
 
diff --git a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
index 72c2fa37068d4d0..fc4d9ee983694c4 100644
--- a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
+++ b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
@@ -92,8 +92,7 @@ export default {
 
 ## Response Metadata
 
-The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers 
+The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers
 
 - `cf-aig-model` - The model used
 - `cf-aig-provider` - The slug of provider used
-
diff --git a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
index d03c6eb9622ec7d..04c450d92911bd4 100644
--- a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
+++ b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
@@ -124,7 +124,7 @@ You will be prompted to log in after you run `wrangler dev`. When you run `npx w
 
 ```json
 {
-  "response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
+	"response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
 }
 ```
 
diff --git a/src/content/docs/ai-gateway/mcp-server.mdx b/src/content/docs/ai-gateway/mcp-server.mdx
index 9cb472e8825884a..5d7ff3bfddb2e49 100644
--- a/src/content/docs/ai-gateway/mcp-server.mdx
+++ b/src/content/docs/ai-gateway/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - ai-gateway
----
\ No newline at end of file
+---
diff --git a/src/content/docs/ai-gateway/observability/logging/index.mdx b/src/content/docs/ai-gateway/observability/logging/index.mdx
index cfcd1cab3d1200c..1ee3a267485ed02 100644
--- a/src/content/docs/ai-gateway/observability/logging/index.mdx
+++ b/src/content/docs/ai-gateway/observability/logging/index.mdx
@@ -55,9 +55,9 @@ The `cf-aig-collect-log-payload` header allows you to control whether the raw re
 
 This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completion data.
 
-| Header value | Behavior |
-| ------------ | -------- |
-| `true`       | Request and response payloads are stored. |
+| Header value | Behavior                                                               |
+| ------------ | ---------------------------------------------------------------------- |
+| `true`       | Request and response payloads are stored.                              |
 | `false`      | Payload storage is skipped. Metadata-only log entries are still saved. |
 
 In the example below, we use `cf-aig-collect-log-payload` to skip storing the request and response bodies while keeping the metadata log.
diff --git a/src/content/docs/ai-gateway/reference/audit-logs.mdx b/src/content/docs/ai-gateway/reference/audit-logs.mdx
index 0cfe7251d9d7c8a..250b377c6c517ee 100644
--- a/src/content/docs/ai-gateway/reference/audit-logs.mdx
+++ b/src/content/docs/ai-gateway/reference/audit-logs.mdx
@@ -5,6 +5,7 @@ pcx_content_type: concept
 products:
   - ai-gateway
 ---
+
 import { DashButton } from "~/components";
 
 [Audit logs](/fundamentals/account/account-security/review-audit-logs/) provide a comprehensive summary of changes made within your Cloudflare account, including those made to gateways in AI Gateway. This functionality is available on all plan types, free of charge, and is enabled by default.
@@ -13,7 +14,7 @@ import { DashButton } from "~/components";
 
 To view audit logs for AI Gateway, in the Cloudflare dashboard, go to the **Audit logs** page.
 
-  <DashButton url="/?to=/:account/audit-log" />
+<DashButton url="/?to=/:account/audit-log" />
 
 For more information on how to access and use audit logs, refer to [review audit logs documentation](/fundamentals/account/account-security/review-audit-logs/).
 
@@ -33,39 +34,39 @@ Below is an example of an audit log entry showing the creation of a new gateway:
 
 ```json
 {
- "action": {
-     "info": "gateway created",
-     "result": true,
-     "type": "create"
- },
- "actor": {
-     "email": "<ACTOR_EMAIL>",
-     "id": "3f7b730e625b975bc1231234cfbec091",
-     "ip": "fe32:43ed:12b5:526::1d2:13",
-     "type": "user"
- },
- "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
- "interface": "UI",
- "metadata": {},
- "newValue": "",
- "newValueJson": {
-     "cache_invalidate_on_update": false,
-     "cache_ttl": 0,
-     "collect_logs": true,
-     "id": "test",
-     "rate_limiting_interval": 0,
-     "rate_limiting_limit": 0,
-     "rate_limiting_technique": "fixed"
- },
- "oldValue": "",
- "oldValueJson": {},
- "owner": {
-     "id": "1234d848c0b9e484dfc37ec392b5fa8a"
- },
- "resource": {
-     "id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
-     "type": "ai_gateway.gateway"
- },
- "when": "2024-07-17T14:06:11.425Z"
+	"action": {
+		"info": "gateway created",
+		"result": true,
+		"type": "create"
+	},
+	"actor": {
+		"email": "<ACTOR_EMAIL>",
+		"id": "3f7b730e625b975bc1231234cfbec091",
+		"ip": "fe32:43ed:12b5:526::1d2:13",
+		"type": "user"
+	},
+	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+	"interface": "UI",
+	"metadata": {},
+	"newValue": "",
+	"newValueJson": {
+		"cache_invalidate_on_update": false,
+		"cache_ttl": 0,
+		"collect_logs": true,
+		"id": "test",
+		"rate_limiting_interval": 0,
+		"rate_limiting_limit": 0,
+		"rate_limiting_technique": "fixed"
+	},
+	"oldValue": "",
+	"oldValueJson": {},
+	"owner": {
+		"id": "1234d848c0b9e484dfc37ec392b5fa8a"
+	},
+	"resource": {
+		"id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
+		"type": "ai_gateway.gateway"
+	},
+	"when": "2024-07-17T14:06:11.425Z"
 }
 ```
diff --git a/src/content/docs/ai-gateway/reference/limits.mdx b/src/content/docs/ai-gateway/reference/limits.mdx
index 5c0459bc75ae5e7..8b130857ad0477c 100644
--- a/src/content/docs/ai-gateway/reference/limits.mdx
+++ b/src/content/docs/ai-gateway/reference/limits.mdx
@@ -33,11 +33,14 @@ The following limits apply to gateway configurations, logs, and related features
 <sup>1</sup> When you reach the log storage limit for a gateway, you can
 configure your gateway to either automatically delete the oldest logs to make
 room for new ones, or stop saving new logs. You can also use
-[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to
-external storage. Refer to [Automatic log deletion](/ai-gateway/observability/logging/#automatic-log-deletion)
-for more details.
-
-<sup>2</sup> On the free plan, the log storage limit applies to total logs across all gateways in your account. Same auto-delete or stop-saving behavior as <sup>1</sup>.
+[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to external
+storage. Refer to [Automatic log
+deletion](/ai-gateway/observability/logging/#automatic-log-deletion) for more
+details.
+
+<sup>2</sup> On the free plan, the log storage limit applies to total logs
+across all gateways in your account. Same auto-delete or stop-saving behavior as
+<sup>1</sup>.
 
 <sup>3</sup> Logs larger than 10 MB will not be stored.
 
diff --git a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
index 9f0277bdd3a1ac7..d55b0392378c965 100644
--- a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
+++ b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
@@ -106,12 +106,12 @@ The response includes a prediction `id`:
 
 ```json
 {
-  "id": "xyz789...",
-  "status": "starting",
-  "urls": {
-    "get": "https://api.replicate.com/v1/predictions/xyz789...",
-    "cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
-  }
+	"id": "xyz789...",
+	"status": "starting",
+	"urls": {
+		"get": "https://api.replicate.com/v1/predictions/xyz789...",
+		"cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
+	}
 }
 ```
 
@@ -127,7 +127,7 @@ Keep polling until `status` is `succeeded` (or `failed`). When complete, the `ou
 
 ## Next steps
 
-From here you can: 
+From here you can:
 
 - Use [logging](/ai-gateway/observability/logging/) to monitor requests and debug issues.
 - Set up [rate limiting](/ai-gateway/features/rate-limiting/) to control usage.
diff --git a/src/content/docs/ai-gateway/usage/chat-completion.mdx b/src/content/docs/ai-gateway/usage/chat-completion.mdx
index 1280237dc0187bb..c1dbd0f663fb740 100644
--- a/src/content/docs/ai-gateway/usage/chat-completion.mdx
+++ b/src/content/docs/ai-gateway/usage/chat-completion.mdx
@@ -11,11 +11,7 @@ products:
   - ai-gateway
 ---
 
-import {
-	Details,
-  Tabs,
-  TabItem
-} from "~/components";
+import { Details, Tabs, TabItem } from "~/components";
 import CodeSnippets from "~/components/ai-gateway/code-examples.astro";
 
 :::caution[Deprecated]
diff --git a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
index 7c7d8622dd1be29..aa1ad566a1a3a37 100644
--- a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
@@ -11,6 +11,7 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 [Anthropic](https://www.anthropic.com/) helps build reliable, interpretable, and steerable AI systems.
 
 ## Endpoint
+
 **Base URL**
 
 ```txt
@@ -124,17 +125,18 @@ import Anthropic from "@anthropic-ai/sdk";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic`;
 
 const anthropic = new Anthropic({
-	baseURL,
-	defaultHeaders: {
-		Authorization: `Bearer {cf_api_token}`,
-	},
+baseURL,
+defaultHeaders: {
+Authorization: `Bearer {cf_api_token}`,
+},
 });
 
 const message = await anthropic.messages.create({
-	model: "claude-sonnet-4-5",
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
-	max_tokens: 1024,
+model: "claude-sonnet-4-5",
+messages: [{ role: "user", content: "What is Cloudflare?" }],
+max_tokens: 1024,
 });
+
 ```
 </Details>
 
@@ -151,3 +153,4 @@ const message = await anthropic.messages.create({
     }}
 
 />
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
index bbda8d88dad78df..33bc4a3a7827002 100644
--- a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
@@ -52,14 +52,14 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{
 import { AzureOpenAI } from "openai";
 
 const azure_openai = new AzureOpenAI({
-  apiKey: "{azure_api_key}",
-  baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
-  apiVersion: "2023-05-15",
-  defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
+	apiKey: "{azure_api_key}",
+	baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
+	apiVersion: "2023-05-15",
+	defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
 });
 
 const result = await azure_openai.chat.completions.create({
-  model: '{deployment_name}',
-  messages: [{ role: "user", content: "Hello" }],
+	model: "{deployment_name}",
+	messages: [{ role: "user", content: "Hello" }],
 });
 ```
diff --git a/src/content/docs/ai-gateway/usage/providers/baseten.mdx b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
index 24877ce82f34716..54c26a43777ba18 100644
--- a/src/content/docs/ai-gateway/usage/providers/baseten.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
@@ -57,31 +57,31 @@ const gatewayId = "{gateway_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const openai = new OpenAI({
-  apiKey,
-  baseURL,
+	apiKey,
+	baseURL,
 });
 
 const model = "openai/gpt-oss-120b";
 const messages = [{ role: "user", content: "What is Cloudflare?" }];
 
 const chatCompletion = await openai.chat.completions.create({
-  model,
-  messages,
+	model,
+	messages,
 });
 
 console.log(chatCompletion);
 ```
 
 <Render
-  file="chat-completions-providers"
-  product="ai-gateway"
-  params={{
-    name: "Baseten",
-    jsonexample: `
+	file="chat-completions-providers"
+	product="ai-gateway"
+	params={{
+		name: "Baseten",
+		jsonexample: `
 {
   "model": "baseten/{model}"
-}`
-  }}
+}`,
+	}}
 />
 
 ## Model-specific endpoints
@@ -110,15 +110,15 @@ const modelId = "{model_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const response = await fetch(`${baseURL}/model/${modelId}`, {
-  method: "POST",
-  headers: {
-    "Authorization": `Bearer ${basetenApiToken}`,
-    "Content-Type": "application/json",
-  },
-  body: JSON.stringify({
-    prompt: "What is Cloudflare?",
-    max_tokens: 100,
-  }),
+	method: "POST",
+	headers: {
+		Authorization: `Bearer ${basetenApiToken}`,
+		"Content-Type": "application/json",
+	},
+	body: JSON.stringify({
+		prompt: "What is Cloudflare?",
+		max_tokens: 100,
+	}),
 });
 
 const result = await response.json();
diff --git a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
index 1f2df28b2813847..bb8f30200a44e93 100644
--- a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
@@ -43,10 +43,10 @@ AI Gateway handles this complexity for you. When you store your AWS credentials
 
 ### Authentication methods comparison
 
-| Method | `cf-aig-authorization` header | `Authorization` header | Signing |
-| --- | --- | --- | --- |
-| **BYOK (Recommended)** | `Bearer {CF_AIG_TOKEN}` | Not needed | Gateway signs automatically |
-| **Client-side signing** | `Bearer {CF_AIG_TOKEN}` | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
+| Method                  | `cf-aig-authorization` header | `Authorization` header | Signing                              |
+| ----------------------- | ----------------------------- | ---------------------- | ------------------------------------ |
+| **BYOK (Recommended)**  | `Bearer {CF_AIG_TOKEN}`       | Not needed             | Gateway signs automatically          |
+| **Client-side signing** | `Bearer {CF_AIG_TOKEN}`       | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
 
 :::caution[Do not confuse the headers]
 `cf-aig-authorization` authenticates your request to AI Gateway. When using BYOK, you do not need to include any AWS authorization headers because AI Gateway signs the request for you.
@@ -227,5 +227,3 @@ const response = await client.chat.completions.create({
 
 console.log(response.choices[0].message.content);
 ```
-
-
diff --git a/src/content/docs/ai-gateway/usage/providers/fal.mdx b/src/content/docs/ai-gateway/usage/providers/fal.mdx
index 3e67996cbae3c2d..057d6dda7144ddc 100644
--- a/src/content/docs/ai-gateway/usage/providers/fal.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/fal.mdx
@@ -78,21 +78,23 @@ The `x-fal-target-url` format is compliant with the Fal SDKs, so AI Gateway can
 import { fal } from "@fal-ai/client";
 
 fal.config({
-  credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
-  proxyUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal"
+	credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
+	proxyUrl:
+		"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal",
 });
 
 const result = await fal.subscribe("fal-ai/bytedance/seedream/v4/edit", {
-  "input": {
-    "prompt": "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
-    "image_urls": [
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png"
-    ]
-  }
+	input: {
+		prompt:
+			"Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
+		image_urls: [
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png",
+		],
+	},
 });
 
 console.log(result.data.images[0]);
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
index 7d986484bd9371b..29e542bf31fb4d9 100644
--- a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
@@ -17,6 +17,7 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 ```txt
 https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio
 ```
+
 Then you can append the endpoint you want to hit, for example: `v1/models/{model}:{generative_ai_rest_resource}`
 
 So your final URL will come together as: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio/v1/models/{model}:{generative_ai_rest_resource}`.
@@ -136,18 +137,19 @@ console.log(response.text);
 import { GoogleGenAI } from "@google/genai";
 
 const ai = new GoogleGenAI({
-  apiKey: "{cf_aig_token}",
-  httpOptions: {
-	  baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
-  }
+apiKey: "{cf_aig_token}",
+httpOptions: {
+baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
+}
 });
 
 const response = await ai.models.generateContent({
-  model: "gemini-2.5-flash",
-  contents: "What is Cloudflare?",
+model: "gemini-2.5-flash",
+contents: "What is Cloudflare?",
 });
 
 console.log(response.text);
+
 ```
 </Details>
 
@@ -164,3 +166,4 @@ console.log(response.text);
     }}
 
 />
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
index bc019d9a71628b5..e9213598bdda79c 100644
--- a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
@@ -48,17 +48,17 @@ const ideogramApiKey = "{ideogram_api_key}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/ideogram`;
 
 const response = await fetch(`${baseURL}/v1/ideogram-v3/generate`, {
-  method: "POST",
-  headers: {
-    "Api-Key": ideogramApiKey,
-    "Content-Type": "application/json",
-  },
-  body: JSON.stringify({
-    prompt: "A serene landscape with mountains and a lake at sunset",
-    model: "V_3",
-  }),
+	method: "POST",
+	headers: {
+		"Api-Key": ideogramApiKey,
+		"Content-Type": "application/json",
+	},
+	body: JSON.stringify({
+		prompt: "A serene landscape with mountains and a lake at sunset",
+		model: "V_3",
+	}),
 });
 
 const result = await response.json();
 console.log(result);
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/ai-gateway/usage/rest-api.mdx b/src/content/docs/ai-gateway/usage/rest-api.mdx
index 7dd750f9b04aca9..e2275bfa7e32b91 100644
--- a/src/content/docs/ai-gateway/usage/rest-api.mdx
+++ b/src/content/docs/ai-gateway/usage/rest-api.mdx
@@ -18,12 +18,12 @@ No provider SDKs or API keys are needed. Authentication and billing are handled
 
 Four endpoints are available, each suited to different use cases:
 
-| Endpoint | Format | Use case |
-| -------- | ------ | -------- |
-| `POST /ai/run` | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
-| `POST /ai/v1/chat/completions` | OpenAI chat completions | LLMs — OpenAI SDK compatible |
-| `POST /ai/v1/responses` | OpenAI Responses API | Agentic workflows — OpenAI SDK compatible |
-| `POST /ai/v1/messages` | Anthropic Messages API | LLMs — Anthropic SDK compatible |
+| Endpoint                       | Format                         | Use case                                         |
+| ------------------------------ | ------------------------------ | ------------------------------------------------ |
+| `POST /ai/run`                 | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
+| `POST /ai/v1/chat/completions` | OpenAI chat completions        | LLMs — OpenAI SDK compatible                     |
+| `POST /ai/v1/responses`        | OpenAI Responses API           | Agentic workflows — OpenAI SDK compatible        |
+| `POST /ai/v1/messages`         | Anthropic Messages API         | LLMs — Anthropic SDK compatible                  |
 
 ## Authentication
 
@@ -140,13 +140,13 @@ Point the OpenAI SDK `baseURL` at the Cloudflare API:
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.chat.completions.create({
-  model: "openai/gpt-4.1",
-  messages: [{ role: "user", content: "What is Cloudflare?" }],
+	model: "openai/gpt-4.1",
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -158,13 +158,13 @@ Uses the OpenAI Responses API format for agentic workflows. Compatible with the
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.responses.create({
-  model: "openai/gpt-4.1",
-  input: "What is Cloudflare?",
+	model: "openai/gpt-4.1",
+	input: "What is Cloudflare?",
 });
 ```
 
@@ -194,14 +194,14 @@ Point the Anthropic SDK `baseURL` at the Cloudflare API:
 import Anthropic from "@anthropic-ai/sdk";
 
 const anthropic = new Anthropic({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const message = await anthropic.messages.create({
-  model: "anthropic/claude-sonnet-4-5",
-  max_tokens: 512,
-  messages: [{ role: "user", content: "What is Cloudflare?" }],
+	model: "anthropic/claude-sonnet-4-5",
+	max_tokens: 512,
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -229,11 +229,11 @@ With the OpenAI SDK, set the header via `defaultHeaders`:
 
 ```javascript
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
-  defaultHeaders: {
-    "cf-aig-gateway-id": "my-gateway",
-  },
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	defaultHeaders: {
+		"cf-aig-gateway-id": "my-gateway",
+	},
 });
 ```
 
@@ -243,17 +243,17 @@ All AI Gateway features configured on that gateway — caching, rate limiting, g
 
 Use `cf-aig-*` headers to control AI Gateway behavior on a per-request basis:
 
-| Header | Type | Description |
-| ------ | ---- | ----------- |
-| `cf-aig-skip-cache` | boolean | Skip the cache for this request. |
-| `cf-aig-cache-ttl` | number | Cache TTL in seconds. |
-| `cf-aig-cache-key` | string | Custom cache key. |
-| `cf-aig-collect-log` | boolean | Turn logging on or off for this request. |
-| `cf-aig-request-timeout` | number | Request timeout in milliseconds. |
-| `cf-aig-max-attempts` | number | Retry attempts (max 5). |
-| `cf-aig-retry-delay` | number | Retry delay in milliseconds (max 5000). |
-| `cf-aig-backoff` | string | Backoff method: `constant`, `linear`, or `exponential`. |
-| `cf-aig-metadata` | JSON string | Custom metadata to attach to the log entry. |
+| Header                   | Type        | Description                                             |
+| ------------------------ | ----------- | ------------------------------------------------------- |
+| `cf-aig-skip-cache`      | boolean     | Skip the cache for this request.                        |
+| `cf-aig-cache-ttl`       | number      | Cache TTL in seconds.                                   |
+| `cf-aig-cache-key`       | string      | Custom cache key.                                       |
+| `cf-aig-collect-log`     | boolean     | Turn logging on or off for this request.                |
+| `cf-aig-request-timeout` | number      | Request timeout in milliseconds.                        |
+| `cf-aig-max-attempts`    | number      | Retry attempts (max 5).                                 |
+| `cf-aig-retry-delay`     | number      | Retry delay in milliseconds (max 5000).                 |
+| `cf-aig-backoff`         | string      | Backoff method: `constant`, `linear`, or `exponential`. |
+| `cf-aig-metadata`        | JSON string | Custom metadata to attach to the log entry.             |
 
 For more details on these options, refer to [Request handling](/ai-gateway/configuration/request-handling/) and [Caching](/ai-gateway/features/caching/).
 
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
index bfc911e09f973c8..dd9b384084acdcf 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
@@ -55,7 +55,7 @@ ws.on("open", () => {
 			},
 		}),
 	);
-})
+});
 
 ws.on("message", (message) => {
 	console.log(message.toString());
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
index 57c34339587a994..f444cff4c7a73ef 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
@@ -272,7 +272,7 @@ let isPlayingAudio = false;
 const rl = readline.createInterface({
 	input: process.stdin,
 	output: process.stdout,
-	prompt: "Enter text to speak (or \"quit\" to exit): ",
+	prompt: 'Enter text to speak (or "quit" to exit): ',
 });
 
 ws.onopen = () => {
diff --git a/src/content/docs/ai-search/api/instances/rest-api.mdx b/src/content/docs/ai-search/api/instances/rest-api.mdx
index 178f1c9d6c69011..37757fbb0ff5362 100644
--- a/src/content/docs/ai-search/api/instances/rest-api.mdx
+++ b/src/content/docs/ai-search/api/instances/rest-api.mdx
@@ -20,8 +20,8 @@ Use the AI Search REST API to manage instances and sync jobs over HTTP.
 
 AI Search APIs are available at two base paths:
 
-| Path                                                                 | Description                                                                 |
-| -------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| Path                                                                     | Description                                                                 |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
 | `/accounts/{account_id}/ai-search/instances/{id}`                        | Operates on a specific instance                                             |
 | `/accounts/{account_id}/ai-search/namespaces/{namespace}/instances/{id}` | Operates on instances within a [namespace](/ai-search/concepts/namespaces/) |
 
diff --git a/src/content/docs/ai-search/api/items/rest-api.mdx b/src/content/docs/ai-search/api/items/rest-api.mdx
index f23b4dd83703914..08634485801ed10 100644
--- a/src/content/docs/ai-search/api/items/rest-api.mdx
+++ b/src/content/docs/ai-search/api/items/rest-api.mdx
@@ -35,8 +35,8 @@ The available operations are the same for both paths. For the namespace-scoped A
 
 Upload, list, get, delete, and download items within an instance. For the full specification, refer to the [Items API reference](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/).
 
-| Operation                                                                                                            | Method   | Description                    |
-| -------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------ |
+| Operation                                                                                                                | Method   | Description                    |
+| ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------ |
 | [Upload](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/upload/)     | `POST`   | Upload a document for indexing |
 | [List](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/list/)         | `GET`    | List all items in an instance  |
 | [Get](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/get/)           | `GET`    | Get item info by ID            |
diff --git a/src/content/docs/ai-search/configuration/models/index.mdx b/src/content/docs/ai-search/configuration/models/index.mdx
index c406d789f32edfa..42a76abb29e721b 100644
--- a/src/content/docs/ai-search/configuration/models/index.mdx
+++ b/src/content/docs/ai-search/configuration/models/index.mdx
@@ -28,12 +28,10 @@ To use AI Search with other model providers:
 
 1. Add provider keys to [AI Gateway](/ai-gateway/configuration/bring-your-own-keys/).
 2. Connect the gateway to AI Search.
-
    - When creating a new AI Search, select the AI Gateway with your provider keys.
    - For an existing AI Search, go to **Settings** and switch to a gateway that has your keys under **Resources**.
 
 3. Select models
-
    - Embedding model: Only available to be changed when creating a new AI Search.
    - Generation model: Can be selected when creating a new AI Search and can be changed at any time in **Settings**.
 
diff --git a/src/content/docs/ai-search/how-to/nlweb.mdx b/src/content/docs/ai-search/how-to/nlweb.mdx
index 25d61bcba3c3cb7..eb36852ae5534f6 100644
--- a/src/content/docs/ai-search/how-to/nlweb.mdx
+++ b/src/content/docs/ai-search/how-to/nlweb.mdx
@@ -67,23 +67,23 @@ You can use the embeddable snippet to add a search UI directly into your website
 
 ```html
 <!-- Add css on head -->
-    <link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css">
-    <link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css">
-
-    <!-- Add container on body -->
-    <div id="docs-search-container"></div>
-
-    <!-- Include JavaScript -->
-    <script type="module">
-      import { NLWebDropdownChat } from 'https://ask.example.com/nlweb-dropdown-chat.js';
-
-      const chat = new NLWebDropdownChat({
-        containerId: 'docs-search-container',
-        site: 'https://ask.example.com',
-        placeholder: 'Search for docs...',
-        endpoint: 'https://ask.example.com'
-      });
-    </script>
+<link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css" />
+<link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css" />
+
+<!-- Add container on body -->
+<div id="docs-search-container"></div>
+
+<!-- Include JavaScript -->
+<script type="module">
+	import { NLWebDropdownChat } from "https://ask.example.com/nlweb-dropdown-chat.js";
+
+	const chat = new NLWebDropdownChat({
+		containerId: "docs-search-container",
+		site: "https://ask.example.com",
+		placeholder: "Search for docs...",
+		endpoint: "https://ask.example.com",
+	});
+</script>
 ```
 
 This lets you serve conversational AI search directly from your own domain, with control over how people and agents access your content.
diff --git a/src/content/docs/ai-search/wrangler-commands.mdx b/src/content/docs/ai-search/wrangler-commands.mdx
index f8e1fa53538eca8..916b781370d0e81 100644
--- a/src/content/docs/ai-search/wrangler-commands.mdx
+++ b/src/content/docs/ai-search/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { WranglerNamespace, WranglerCommand } from "~/components";
 
-<WranglerNamespace namespace="ai-search" />
\ No newline at end of file
+<WranglerNamespace namespace="ai-search" />
diff --git a/src/content/docs/ai/related-products/ai-gateway.mdx b/src/content/docs/ai/related-products/ai-gateway.mdx
index c868d2c8ec2fd75..75063087b321b29 100644
--- a/src/content/docs/ai/related-products/ai-gateway.mdx
+++ b/src/content/docs/ai/related-products/ai-gateway.mdx
@@ -6,5 +6,5 @@ sidebar:
 external_link: /ai-gateway/
 products:
   - ai
-  - ai-gateway  
+  - ai-gateway
 ---
diff --git a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
index 0d4aaf4a63bca3e..c5d95a03c76c5d4 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - analytics
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Cloudflare account analytics lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
@@ -18,29 +18,29 @@ Cloudflare account analytics lets you access a wide range of aggregated metrics
 For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
 :::
 
-***
+---
 
 ## View your account analytics
 
 To view metrics for your site, in the Cloudflare dashboard, go to the **Account Analytics** page.
 
-   <DashButton url="/?to=/:account/analytics" />
+<DashButton url="/?to=/:account/analytics" />
 
-Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to *Review your account metrics* below.
+Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to _Review your account metrics_ below.
 
-***
+---
 
 ## Review your account metrics
 
 This section outlines the aggregated metrics under each category. Before reviewing your metrics, let's define a couple of concepts used in some panels:
 
-* *Rate* -  Reflects the ratio between the amount for a specific data category and the total.
-* *Bandwidth* - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
+- _Rate_ -  Reflects the ratio between the amount for a specific data category and the total.
+- _Bandwidth_ - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
 
 Also, note that:
 
-* To filter metrics for a specific time period, use the dropdown in the top right.
-* Most metrics are grouped into panels representing different aspects of the underlying data.
+- To filter metrics for a specific time period, use the dropdown in the top right.
+- Most metrics are grouped into panels representing different aspects of the underlying data.
 
 ### Summary of metrics
 
@@ -52,21 +52,21 @@ These charts aggregate data for HTTP traffic, and include:
 
 ![Chart showing last week's data for HTTP traffic](~/assets/images/support/hc-dash-account-analytics-map.png)
 
-* Spark lines for *Requests*, *Bandwidth*, *Page views*, and *Visitors* (*Unique IPs)*
-* An interactive map that breaks down the number of requests by country
-* A table combining numerical and spark line data, sorted by total number of requests per country
+- Spark lines for _Requests_, _Bandwidth_, _Page views_, and _Visitors_ (_Unique IPs)_
+- An interactive map that breaks down the number of requests by country
+- A table combining numerical and spark line data, sorted by total number of requests per country
 
 #### Security
 
 ![Panel displaying lines highlighting encryption metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_security_panel.png)
 
-This panel features spark lines highlighting various encryption metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous period.
+This panel features spark lines highlighting various encryption metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous period.
 
 #### Cache
 
 ![Panel displaying lines for caching metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_cache_card.png)
 
-This panel features spark lines for various caching metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected *Last week* as your time period, the previous period refers to the *week* before.
+This panel features spark lines for various caching metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected _Last week_ as your time period, the previous period refers to the _week_ before.
 
 #### Errors
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
index 76dccf882a47092..84e856b537c7e3a 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
@@ -13,7 +13,7 @@ Learn how Cloudflare analytics tracks requests made by [Cloudflare Workers](/wor
 
 With a no-op Worker (a Worker that simply proxies traffic by passing on the original client request to the origin and proxying the response) running on a particular route, the request to the origin is counted as a 'subrequest', separate from initial client to edge request. Thus, unless the Worker responds with a static response and never hits an origin, the eyeball → edge request, and edge → origin request will each be counted separately towards the request or bandwidth count in Analytics. Subrequests are not included in the **Requests** or **Bandwidth** graphs of the Cloudflare **Analytics** app.
 
-***
+---
 
 ## Zone analytics
 
@@ -21,20 +21,20 @@ In the dashboard, the numbers in zone analytics reflect visitor traffic. That is
 
 Similarly, the bandwidth is counted based on the bandwidth that is sent to the client, and status codes reflect the status codes that were served back to the client (so if a subrequest received a 500, but you respond with a 200, a 200 will be shown in the status codes breakdown).
 
-***
+---
 
 ## Worker analytics
 
 For a breakdown of subrequest traffic (origin facing traffic), you may go to the Cloudflare **Analytics** app and select the **Workers** tab. Under the **Workers** tab, below the Service Workers panel, are a **Subrequests** breakdown by count, **Bandwidth** and **Status Codes**. This will help you spot and debug errors at your origin (such as spikes in 500s), and identify your cache-hit ratio to help you understand traffic going to your origin.
 
-***
+---
 
 ## FAQ
 
 **Why do I not have any analytics for Workers?**
 
-* If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
-* If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
+- If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
+- If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
 
 **Will this impact billing?** 
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/index.mdx b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
index 54e99ae3cb5ec74..2aeb75e8f6f6dc4 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/index.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Visit the following pages to learn more about account and zone analytics:
 
diff --git a/src/content/docs/analytics/analytics-engine/grafana.mdx b/src/content/docs/analytics/analytics-engine/grafana.mdx
index e6af88fd7a7a901..96310e19e31d8cc 100644
--- a/src/content/docs/analytics/analytics-engine/grafana.mdx
+++ b/src/content/docs/analytics/analytics-engine/grafana.mdx
@@ -20,10 +20,10 @@ We recommend the use of the [Altinity plugin for Clickhouse](https://grafana.com
 
 Configure the plugin as follows:
 
-* URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
-* Leave all auth settings off.
-* Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
-* No other options need to be set.
+- URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
+- Leave all auth settings off.
+- Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
+- No other options need to be set.
 
 ## Querying timeseries data
 
@@ -35,8 +35,8 @@ SELECT
     blob1 AS label,
     SUM(_sample_interval * double1) / SUM(_sample_interval) AS average_metric
 FROM dataset_name
-WHERE 
-    timestamp <= NOW() 
+WHERE
+    timestamp <= NOW()
     AND timestamp > NOW() - INTERVAL '1' DAY
 GROUP BY blob1, t
 ORDER BY t
diff --git a/src/content/docs/analytics/analytics-engine/index.mdx b/src/content/docs/analytics/analytics-engine/index.mdx
index 2eae0d36b0eab7d..ddee07f45c1808c 100644
--- a/src/content/docs/analytics/analytics-engine/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/index.mdx
@@ -8,15 +8,17 @@ products:
   - workers-analytics-engine
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 Workers Analytics Engine provides unlimited-cardinality analytics at scale, via [a built-in API](/analytics/analytics-engine/get-started/) to write data points from Workers, and a [SQL API](/analytics/analytics-engine/sql-api/) to query that data.
 
 You can use Workers Analytics Engine to:
 
-* Expose custom analytics to your own customers
-* Build usage-based billing systems
-* Understand the health of your service on a per-customer or per-user basis
-* Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
+- Expose custom analytics to your own customers
+- Build usage-based billing systems
+- Understand the health of your service on a per-customer or per-user basis
+- Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
 
- <LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">Get started</LinkButton>
+<LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">
+	Get started
+</LinkButton>
diff --git a/src/content/docs/analytics/analytics-engine/limits.mdx b/src/content/docs/analytics/analytics-engine/limits.mdx
index 293093c33e3343b..d4eb97a73b95fcb 100644
--- a/src/content/docs/analytics/analytics-engine/limits.mdx
+++ b/src/content/docs/analytics/analytics-engine/limits.mdx
@@ -13,10 +13,10 @@ products:
 
 The following limits apply to Workers Analytics Engine:
 
-* Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
-* The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
-* Each index must not be more than 96 bytes.
-* You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
+- Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
+- The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
+- Each index must not be more than 96 bytes.
+- You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
 
 ## Data retention
 
diff --git a/src/content/docs/analytics/analytics-engine/pricing.mdx b/src/content/docs/analytics/analytics-engine/pricing.mdx
index 059f55deae8360d..bef373bc86ebf85 100644
--- a/src/content/docs/analytics/analytics-engine/pricing.mdx
+++ b/src/content/docs/analytics/analytics-engine/pricing.mdx
@@ -23,7 +23,7 @@ Workers Analytics Engine is priced based on two metrics — data points written
 
 Currently, you will not be billed for your use of Workers Analytics Engine. Pricing information here is shared in advance, so that you can estimate what your costs will be once Cloudflare starts billing for usage in the coming months.
 
-If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing. 
+If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing.
 :::
 
 ### Data points written
diff --git a/src/content/docs/analytics/analytics-engine/recipes/index.mdx b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
index f0a1bab71954b46..17c5d1b314b065e 100644
--- a/src/content/docs/analytics/analytics-engine/recipes/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Example implementations of common use cases for Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sampling.mdx b/src/content/docs/analytics/analytics-engine/sampling.mdx
index c358eadeb8f377c..bc8b75c9cac7e72 100644
--- a/src/content/docs/analytics/analytics-engine/sampling.mdx
+++ b/src/content/docs/analytics/analytics-engine/sampling.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](https://en.wikipedia.org/wiki/Sampling_\(statistics\)).
+Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>).
 
 When utilizing sampling, you do not need every single data point to answer questions about a dataset. For a sufficiently large dataset, the [necessary sample size](https://select-statistics.co.uk/blog/importance-effect-sample-size/) does not depend on the size of the original population. Necessary sample size depends on the variance of your measure, the size of the subgroups you analyze, and how accurate your estimate must be.
 
@@ -24,11 +24,11 @@ At a high level, the way sampling works is:
 
 In the following sections, you will learn:
 
-* [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
-* [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
-* [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
-* [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
-* [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
+- [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
+- [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
+- [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
+- [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
+- [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
 
 ## How sampling works
 
@@ -44,15 +44,15 @@ The key point is that the map's quality does not solely depend on the resolution
 
 There are similarities between the how a mapping services handles resolution and Cloudflare Analytics delivers analytics using adaptive samples:
 
-* **How data is stored**:
-  * **Mapping service**: Imagery stored at different resolutions.
-  * **Cloudflare Analytics**: Events stored at different sample rates.
-* **How data is displayed to user**:
-  * **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
-  * **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
-* **How a resolution is selected**:
-  * **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
-  * **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
+- **How data is stored**:
+  - **Mapping service**: Imagery stored at different resolutions.
+  - **Cloudflare Analytics**: Events stored at different sample rates.
+- **How data is displayed to user**:
+  - **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
+  - **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
+- **How a resolution is selected**:
+  - **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
+  - **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
 
 ## How to read sampled data
 
@@ -87,11 +87,11 @@ If we took a [simple random sample](https://en.wikipedia.org/wiki/Simple_random_
 
 ![The same graphic as above, but now based on a 1% sample of the data.](~/assets/images/analytics/sample-data.png)
 
-Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](https://en.wikipedia.org/wiki/Quantization_\(signal_processing\)) and may even be rounded to 0 entirely.
+Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](<https://en.wikipedia.org/wiki/Quantization_(signal_processing)>) and may even be rounded to 0 entirely.
 
 This shows that while a one percent (1%) or even smaller sample of a large population may be sufficient, we may need to store a larger proportion of events for a small population to get accurate results.
 
-We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`.  But if you write lots of data points to a single index value, we will start to sample.
+We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`. But if you write lots of data points to a single index value, we will start to sample.
 
 Here is the same distribution, but now with (a simulation of) equitable sampling applied:
 
@@ -117,23 +117,23 @@ In order to get accurate results with sampled data, select an appropriate value
 
 The index has the following properties, which are important to consider when choosing an index:
 
-* Get accurate summary statistics about your entire dataset, across all index values.
-* Get an accurate count of the number of unique values of your index.
-* Get accurate summary statistics (for example, count, sum) within a particular index value.
-* See the `Top N` values of specific fields that are not in your index.
-* Filter on most fields.
-* Run other aggregations like quantiles.
+- Get accurate summary statistics about your entire dataset, across all index values.
+- Get an accurate count of the number of unique values of your index.
+- Get accurate summary statistics (for example, count, sum) within a particular index value.
+- See the `Top N` values of specific fields that are not in your index.
+- Filter on most fields.
+- Run other aggregations like quantiles.
 
 Some limitations and trade-offs to consider are:
 
-* You may not be able to get accurate unique counts of fields that are not in your index.
-  * For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
-* You may not be able to observe very rare values of fields not in the index.
-  * For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
-* You may not be able to run accurate queries across multiple indices at once.
-  * For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
-* There is no guarantee you can retrieve any one individual record.
-* You cannot necessarily reconstruct exact sequences of events.
+- You may not be able to get accurate unique counts of fields that are not in your index.
+  - For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
+- You may not be able to observe very rare values of fields not in the index.
+  - For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
+- You may not be able to run accurate queries across multiple indices at once.
+  - For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
+- There is no guarantee you can retrieve any one individual record.
+- You cannot necessarily reconstruct exact sequences of events.
 
 It is not recommended to write a unique index value on every row (like a UUID) for most use cases. While this will make it possible to retrieve individual data points very quickly, it will slow down most queries for aggregations and time series.
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-api.mdx b/src/content/docs/analytics/analytics-engine/sql-api.mdx
index 55cfccf8e90d48f..1801c7d93dbaf1a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-api.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-api.mdx
@@ -25,10 +25,10 @@ Use the dashboard to create a token with permission to read analytics data on yo
 2. Select **Create Token**.
 3. Select **Create Custom Token**.
 4. Complete the **Create Custom Token** form as follows:
-   * Give your token a descriptive name.
-   * For **Permissions** select *Account* | *Account Analytics* | *Read*
-   * Optionally configure account and IP restrictions and TTL.
-   * Submit and confirm the form to create the token.
+   - Give your token a descriptive name.
+   - For **Permissions** select _Account_ | _Account Analytics_ | _Read_
+   - Optionally configure account and IP restrictions and TTL.
+   - Submit and confirm the form to create the token.
 5. Make a note of the token string.
 
 ## Querying the API
@@ -63,7 +63,7 @@ The table will have the following columns:
 | ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | dataset                      | string   | This column will contain the dataset name in every row.                                                                                                                                                                                              |
 | timestamp                    | DateTime | The timestamp at which the event was logged in your worker.                                                                                                                                                                                          |
-| \_sample\_interval           | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
+| \_sample_interval            | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
 | index1                       | string   | The index value that was logged with the event. The value in this column is used as the key for sampling.                                                                                                                                            |
 | blob1<br/>...<br/>blob20     | string   | The blob values that were logged with the event.                                                                                                                                                                                                     |
 | double1<br/>...<br/>double20 | double   | The double values that were logged with the event.                                                                                                                                                                                                   |
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
index 4d1827c650f3567..62e8e01ba6ec69f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## count
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
index f8d061a0f4b5635..9a64750c492178a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## bitAnd <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
index 9db9dac5fb7d21a..46e2141c8ef25e0 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## formatDateTime
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
index 851779802af43f3..016f68450f83fef 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## bin <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
index ebe0124792308e4..e8a324356d02009 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Reference documentation describing the SQL supported by Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
index ba40ae26a6009c2..97035f5a95abd0e 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## intDiv
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
index 9a4b8089ef3d6c5..40411492466534f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
@@ -12,7 +12,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## length
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
index f87f1a7eb19e146..1ddf69b03623497 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## toUInt8 <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/worker-querying.mdx b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
index 81c7b08511cf5ca..0a8521edc362e68 100644
--- a/src/content/docs/analytics/analytics-engine/worker-querying.mdx
+++ b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
@@ -11,7 +11,6 @@ products:
   - workers-analytics-engine
 ---
 
-
 import { WranglerConfig } from "~/components";
 
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
diff --git a/src/content/docs/analytics/analytics-integrations/datadog.mdx b/src/content/docs/analytics/analytics-integrations/datadog.mdx
index 579cc03b68a207a..07af42f65157723 100644
--- a/src/content/docs/analytics/analytics-integrations/datadog.mdx
+++ b/src/content/docs/analytics/analytics-integrations/datadog.mdx
@@ -36,7 +36,6 @@ To install the Cloudflare App for Datadog:
 4. Click the **Cloudflare** tile to begin the installation.
 
 5. Next, click **Configuration** and then complete the following:
-
    - **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
 
    - **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
diff --git a/src/content/docs/analytics/analytics-integrations/index.mdx b/src/content/docs/analytics/analytics-integrations/index.mdx
index 12212b2b3fbc24f..f97ccae2ade7ad9 100644
--- a/src/content/docs/analytics/analytics-integrations/index.mdx
+++ b/src/content/docs/analytics/analytics-integrations/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare Enterprise customers can use Cloudflare integrations with their preferred analytics provider and configure ready-to-use Cloudflare Dashboards. Most analytics integrations are built on Cloudflare Logs by using Logpush with either Amazon S3 bucket or GCP Storage bucket.
 
diff --git a/src/content/docs/analytics/analytics-integrations/prometheus.mdx b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
index 10a355c84e93b3d..bcee11a6e7f26eb 100644
--- a/src/content/docs/analytics/analytics-integrations/prometheus.mdx
+++ b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
@@ -59,16 +59,16 @@ Create a Cloudflare API token with the following permissions:
 
 [Create token with pre-filled permissions](https://dash.cloudflare.com/profile/api-tokens?permissionGroupKeys=%5B%7B%22key%22%3A%22analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22workers_scripts%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22ssl_and_certificates%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22firewall_services%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22load_balancers%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_logs%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22magic_transit%22%2C%22type%22%3A%22read%22%7D%5D&name=Cloudflare%20Prometheus%20Exporter)
 
-| Permission | Access | Required |
-|---|---|---|
-| Zone > Analytics | Read | Yes |
-| Account > Account Analytics | Read | Yes |
-| Account > Workers Scripts | Read | Yes |
-| Zone > SSL and Certificates | Read | Optional |
-| Zone > Firewall Services | Read | Optional |
-| Zone > Load Balancers | Read | Optional |
-| Account > Logs | Read | Optional |
-| Account > Magic Transit | Read | Optional |
+| Permission                  | Access | Required |
+| --------------------------- | ------ | -------- |
+| Zone > Analytics            | Read   | Yes      |
+| Account > Account Analytics | Read   | Yes      |
+| Account > Workers Scripts   | Read   | Yes      |
+| Zone > SSL and Certificates | Read   | Optional |
+| Zone > Firewall Services    | Read   | Optional |
+| Zone > Load Balancers       | Read   | Optional |
+| Account > Logs              | Read   | Optional |
+| Account > Magic Transit     | Read   | Optional |
 
 ## Task 3 - Configure Prometheus
 
@@ -76,11 +76,11 @@ Add the exporter as a scrape target in your Prometheus configuration:
 
 ```yaml
 scrape_configs:
-  - job_name: 'cloudflare'
+  - job_name: "cloudflare"
     scrape_interval: 60s
     scrape_timeout: 30s
     static_configs:
-      - targets: ['your-worker.your-subdomain.workers.dev']
+      - targets: ["your-worker.your-subdomain.workers.dev"]
 ```
 
 ### With Basic Auth
@@ -89,14 +89,14 @@ If you configured Basic Auth on the exporter, update your Prometheus configurati
 
 ```yaml
 scrape_configs:
-  - job_name: 'cloudflare'
+  - job_name: "cloudflare"
     scrape_interval: 60s
     scrape_timeout: 30s
     basic_auth:
-      username: 'your-username'
-      password: 'your-password'
+      username: "your-username"
+      password: "your-password"
     static_configs:
-      - targets: ['your-worker.your-subdomain.workers.dev']
+      - targets: ["your-worker.your-subdomain.workers.dev"]
 ```
 
 ## Configuration
@@ -105,32 +105,32 @@ Configuration is resolved in order: **KV overrides** > **environment variables**
 
 Set environment variables in `wrangler.jsonc` or via `wrangler secret put`:
 
-| Variable | Default | Description |
-|---|---|---|
-| `CLOUDFLARE_API_TOKEN` | - | Cloudflare API token (secret) |
-| `SCRAPE_DELAY_SECONDS` | `300` | Delay before fetching metrics (data propagation) |
-| `TIME_WINDOW_SECONDS` | `60` | Query time window |
-| `METRIC_REFRESH_INTERVAL_SECONDS` | `60` | Background refresh interval |
-| `CF_ACCOUNTS` | - | Comma-separated account IDs to include (default: all) |
-| `CF_ZONES` | - | Comma-separated zone IDs to include (default: all) |
-| `METRICS_DENYLIST` | - | Comma-separated list of metrics to exclude |
-| `EXCLUDE_HOST` | `false` | Exclude host labels from metrics |
-| `METRICS_PATH` | `/metrics` | Custom path for metrics endpoint |
-| `BASIC_AUTH_USER` | - | Username for Basic Auth (secret) |
-| `BASIC_AUTH_PASSWORD` | - | Password for Basic Auth (secret) |
+| Variable                          | Default    | Description                                           |
+| --------------------------------- | ---------- | ----------------------------------------------------- |
+| `CLOUDFLARE_API_TOKEN`            | -          | Cloudflare API token (secret)                         |
+| `SCRAPE_DELAY_SECONDS`            | `300`      | Delay before fetching metrics (data propagation)      |
+| `TIME_WINDOW_SECONDS`             | `60`       | Query time window                                     |
+| `METRIC_REFRESH_INTERVAL_SECONDS` | `60`       | Background refresh interval                           |
+| `CF_ACCOUNTS`                     | -          | Comma-separated account IDs to include (default: all) |
+| `CF_ZONES`                        | -          | Comma-separated zone IDs to include (default: all)    |
+| `METRICS_DENYLIST`                | -          | Comma-separated list of metrics to exclude            |
+| `EXCLUDE_HOST`                    | `false`    | Exclude host labels from metrics                      |
+| `METRICS_PATH`                    | `/metrics` | Custom path for metrics endpoint                      |
+| `BASIC_AUTH_USER`                 | -          | Username for Basic Auth (secret)                      |
+| `BASIC_AUTH_PASSWORD`             | -          | Password for Basic Auth (secret)                      |
 
 For a full list of configuration options, refer to the [exporter README](https://github.com/cloudflare/cloudflare-prometheus-exporter#configuration).
 
 ## Endpoints
 
-| Path | Method | Description |
-|---|---|---|
-| `/` | GET | Landing page |
-| `/metrics` | GET | Prometheus metrics |
-| `/health` | GET | Health check |
-| `/config` | GET | Get all runtime config |
-| `/config/:key` | PUT | Set a config override (persisted in KV) |
-| `/config/:key` | DELETE | Reset a config key to its default |
+| Path           | Method | Description                             |
+| -------------- | ------ | --------------------------------------- |
+| `/`            | GET    | Landing page                            |
+| `/metrics`     | GET    | Prometheus metrics                      |
+| `/health`      | GET    | Health check                            |
+| `/config`      | GET    | Get all runtime config                  |
+| `/config/:key` | PUT    | Set a config override (persisted in KV) |
+| `/config/:key` | DELETE | Reset a config key to its default       |
 
 ## Available metrics
 
@@ -160,6 +160,7 @@ For a complete list of metrics with types and labels, refer to the [exporter REA
 Zones on Cloudflare's Free plan do not have access to the GraphQL Analytics API. The exporter automatically detects and skips free tier zones for metrics that require this API.
 
 Free tier zones still export:
+
 - `cloudflare_zone_certificate_validation_status` (SSL certificates)
 - `cloudflare_zone_lb_origin_weight` (Load balancer weights, if configured)
 
diff --git a/src/content/docs/analytics/custom-dashboards.mdx b/src/content/docs/analytics/custom-dashboards.mdx
index 49b08e4bdd64804..11fc76cc324f367 100644
--- a/src/content/docs/analytics/custom-dashboards.mdx
+++ b/src/content/docs/analytics/custom-dashboards.mdx
@@ -28,10 +28,10 @@ Investigate incidents so that when something goes wrong, you can create focused
 
 Custom Dashboards are available to all Cloudflare customers.
 
-| Customer type | Dashboard limit |
-|---------------|-----------------|
-| All Cloudflare customers | Up to 25 dashboards |
-| Log Explorer customers | Up to 100 dashboards |
+| Customer type            | Dashboard limit      |
+| ------------------------ | -------------------- |
+| All Cloudflare customers | Up to 25 dashboards  |
+| Log Explorer customers   | Up to 100 dashboards |
 
 ## Get started
 
@@ -39,13 +39,13 @@ Custom Dashboards are available to all Cloudflare customers.
 
 Templates are the fastest way to get value from Custom Dashboards. Each template is designed around a specific use case and includes pre-configured charts that surface the most relevant metrics.
 
-| Template | Use case |
-|----------|----------|
-| **Bot monitoring** | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors |
-| **API Security** | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns |
-| **Account takeover** | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
-| **API Performance** | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain |
-| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time |
+| Template                   | Use case                                                                                                                                 |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| **Bot monitoring**         | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors              |
+| **API Security**           | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns                           |
+| **Account takeover**       | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
+| **API Performance**        | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain   |
+| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time  |
 
 After selecting a template, you can customize it by adding, removing, or modifying charts to fit your specific needs.
 
@@ -81,15 +81,15 @@ For precise control, configure each element of your chart:
 
 Choose the visualization that best fits your data:
 
-| Chart type | Best for |
-|------------|----------|
+| Chart type     | Best for                                                                                 |
+| -------------- | ---------------------------------------------------------------------------------------- |
 | **Timeseries** | Trends and patterns over time — traffic spikes, latency changes, error rate fluctuations |
-| **Bar** | Comparing values across categories — requests by country, errors by status code |
-| **Donut** | Understanding proportions — cache hit ratio, traffic distribution by content type |
-| **Map** | Geographic patterns — where your traffic originates, regional performance differences |
-| **Stat** | Single important numbers — total requests today, current error rate, p99 latency |
-| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion |
-| **Top N** | Rankings — busiest endpoints, most blocked IPs, top user agents |
+| **Bar**        | Comparing values across categories — requests by country, errors by status code          |
+| **Donut**      | Understanding proportions — cache hit ratio, traffic distribution by content type        |
+| **Map**        | Geographic patterns — where your traffic originates, regional performance differences    |
+| **Stat**       | Single important numbers — total requests today, current error rate, p99 latency         |
+| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion                          |
+| **Top N**      | Rankings — busiest endpoints, most blocked IPs, top user agents                          |
 
 #### Example: Build a security overview chart
 
diff --git a/src/content/docs/analytics/faq/about-analytics.mdx b/src/content/docs/analytics/faq/about-analytics.mdx
index 027f8a07eb32e94..53d5f449641933e 100644
--- a/src/content/docs/analytics/faq/about-analytics.mdx
+++ b/src/content/docs/analytics/faq/about-analytics.mdx
@@ -23,10 +23,10 @@ Refer to [Types of analytics](/analytics/types-of-analytics/) for more informati
 
 The underlying datasets that Cloudflare Analytics captures and processes share the following characteristics:
 
-* All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
-* Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
-* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
-* In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
+- All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
+- Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
+- Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
+- In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
 
 ## Apparent data discrepancies
 
@@ -42,10 +42,10 @@ Finally, it is likely that unique visitor data from the Cloudflare Analytics app
 
 You may not be seeing metrics on Cloudflare Analytics for the following reasons:
 
-* You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
-* If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
-* If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
-* Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
+- You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
+- If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
+- If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
+- Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
 
 :::note
 Activations through a hosting partner works via a [CNAME setup](/dns/zone-setups/partial-setup/) on the `www` record. If most of your traffic actually goes to `domain.com`, [forward your traffic](/rules/url-forwarding/bulk-redirects/) from `domain.com` to `www.domain.com`.
diff --git a/src/content/docs/analytics/faq/index.mdx b/src/content/docs/analytics/faq/index.mdx
index c7d87c530a29c24..555fcdc07a3795f 100644
--- a/src/content/docs/analytics/faq/index.mdx
+++ b/src/content/docs/analytics/faq/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Visit the following pages for commonly asked questions:
 
diff --git a/src/content/docs/analytics/faq/other-faqs.mdx b/src/content/docs/analytics/faq/other-faqs.mdx
index 4e9145ab25ee9ae..86adb232c817e4d 100644
--- a/src/content/docs/analytics/faq/other-faqs.mdx
+++ b/src/content/docs/analytics/faq/other-faqs.mdx
@@ -15,10 +15,8 @@ There is a number of different types of traffic which may originate from **CLOUD
 
 Some sources of traffic from ASN13335 include:
 
-* [Workers subrequests](/workers/runtime-apis/fetch/)
-* [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
-* [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
-* [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
-* Other Cloudflare features like [Health Checks](/health-checks/)
-
-
+- [Workers subrequests](/workers/runtime-apis/fetch/)
+- [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
+- [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
+- [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
+- Other Cloudflare features like [Health Checks](/health-checks/)
diff --git a/src/content/docs/analytics/faq/wae-faqs.mdx b/src/content/docs/analytics/faq/wae-faqs.mdx
index 3693060a2bb2ab8..b88ec97467a6ce7 100644
--- a/src/content/docs/analytics/faq/wae-faqs.mdx
+++ b/src/content/docs/analytics/faq/wae-faqs.mdx
@@ -23,29 +23,24 @@ On the other hand, if you pick a good index that aligns with how you read the da
 
 ### What if I need to index on multiple values?
 
-
 It is possible to concatenate multiple values in your index field. So if you want to index on user ID and hostname, you can write, for example `"$userID:$hostname"` into your index field.
 
 Note that, based on your query pattern, it may make sense to write the same dataset with different indices. It is a common misconception that one should avoid "double-writing" data.
 
 Thanks to sampling, the cost of writing data multiple times can be relatively low. However, reading data inefficiently can result in significant expenses or low-quality results due to sampling.
 
-
 ### How do I know if my data is sampled?
 
 You can use the `_sample_interval` field — again, note that this does not tell you if the results are accurate.
 
 You can tell when data is sampled at read time because sample intervals will be multiples of powers of 10, for example `20` or `700`. There is no hard and fast rule for when sampling starts at read time, but in practice reading longer periods (or more index values) will result in a higher sample interval.
 
-
 ### Why is data missing?
 
-
 Sampling is based largely on the choice of index, as well as other factors like the time range queried and number of indices read. If you are reading from a larger index over a longer time period, and have filtered to a relatively small subgroup within that index, it may not be present due to sampling.
 
 If you need to read accurate results for that subgroup, we suggest that you add that field to your index (refer to [What if I need to index on multiple values](/analytics/faq/wae-faqs/#what-if-i-need-to-index-on-multiple-values)).
 
-
 ### Can I trust sampled data? Are my results accurate?
 
 Sampled data is highly reliable, particularly when a carefully selected index is used.
@@ -56,7 +51,7 @@ In the near future, we plan to expose the [margin of error](https://en.wikipedia
 
 ### How are bursts handled?
 
-Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time.  The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
+Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time. The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
 
 ### How much traffic will trigger sampling?
 
@@ -65,5 +60,3 @@ There is no fixed rule determining when sampling will be triggered.
 We have observed that for workloads like our global CDN, which distribute load around our network, each index value needs about 100 data points per second before sampling is noticeable at all.
 
 Depending on your workload and how you use Workers Analytics Engine, sampling may start at a higher or lower threshold than this. For example, if you are writing out many data points from a single worker execution, it is more likely that your data will be sampled.
-
-
diff --git a/src/content/docs/analytics/graphql-api/errors.mdx b/src/content/docs/analytics/graphql-api/errors.mdx
index b40d61df3dca927..aeead71c606fc32 100644
--- a/src/content/docs/analytics/graphql-api/errors.mdx
+++ b/src/content/docs/analytics/graphql-api/errors.mdx
@@ -13,24 +13,24 @@ The GraphQL Analytics API is a RESTful API based on HTTPS requests and JSON resp
 
 All responses contain an `errors` array, which will be `null` if there are no errors, and include at least one error object if there was an error. Non-null error objects will contain the following fields:
 
-* `message`: a string describing the error.
-* `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
-* `timestamp`: UTC datetime when the error occurred.
+- `message`: a string describing the error.
+- `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
+- `timestamp`: UTC datetime when the error occurred.
 
 ## Example
 
 ```json
 {
-  "data": null,
-  "errors": [
-    {
-      "message": "cannot request data older than 2678400s",
-      "path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
-      "extensions": {
-        "timestamp": "2019-12-09T21:27:19.195060142Z"
-      }
-    }
-  ]
+	"data": null,
+	"errors": [
+		{
+			"message": "cannot request data older than 2678400s",
+			"path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
+			"extensions": {
+				"timestamp": "2019-12-09T21:27:19.195060142Z"
+			}
+		}
+	]
 }
 ```
 
@@ -40,8 +40,8 @@ All responses contain an `errors` array, which will be `null` if there are no er
 
 Sample error messages:
 
-* `unable to execute query, please try again later` (HTTP `503`)
-* `too many queries in progress, please try again later` (HTTP `503`)
+- `unable to execute query, please try again later` (HTTP `503`)
+- `too many queries in progress, please try again later` (HTTP `503`)
 
 These messages indicate a temporary server-side issue. The first message typically means the upstream database is unreachable or returned an error. The second message means the server has reached its maximum number of concurrent queries.
 
@@ -51,10 +51,10 @@ Retry the request after a short delay. If the error persists, check the [Cloudfl
 
 Sample error messages:
 
-* `cannot request data older than...` (HTTP `400`)
-* `number of fields can't be more than...` (HTTP `400`)
-* `limit must be positive number and not greater than...` (HTTP `400`)
-* `query time range is too large...` (HTTP `400`)
+- `cannot request data older than...` (HTTP `400`)
+- `number of fields can't be more than...` (HTTP `400`)
+- `limit must be positive number and not greater than...` (HTTP `400`)
+- `query time range is too large...` (HTTP `400`)
 
 These messages indicate that the query exceeds what is allowed for the particular dataset under the current [plan](https://www.cloudflare.com/plans/), and an upgrade should be considered. Refer to [Node limits](/analytics/graphql-api/limits/#node-limits-and-availability) for details.
 
@@ -62,11 +62,11 @@ These messages indicate that the query exceeds what is allowed for the particula
 
 Sample error messages:
 
-* `error parsing args...` (HTTP `400`)
-* `scalar fields must have no selections` (HTTP `400`)
-* `object field must have selections` (HTTP `400`)
-* `unknown field...` (HTTP `400`)
-* `query contains error, please review it and retry` (HTTP `400`)
+- `error parsing args...` (HTTP `400`)
+- `scalar fields must have no selections` (HTTP `400`)
+- `object field must have selections` (HTTP `400`)
+- `unknown field...` (HTTP `400`)
+- `query contains error, please review it and retry` (HTTP `400`)
 
 These messages indicate that the query cannot be processed because it is malformed. Check the query syntax against the [GraphQL schema](/analytics/graphql-api/getting-started/explore-graphql-schema/) and correct the invalid fields or structure.
 
@@ -74,9 +74,9 @@ These messages indicate that the query cannot be processed because it is malform
 
 Sample error messages:
 
-* `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
-* `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
-* `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
+- `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
+- `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
+- `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
 
 These messages indicate the query exceeded rate or resource limits. Reduce the query complexity, the number of zones or accounts per request, or wait before retrying. Refer to the [Limits](/analytics/graphql-api/limits/) section for more details about rate limits.
 
@@ -84,10 +84,10 @@ These messages indicate the query exceeded rate or resource limits. Reduce the q
 
 Sample error messages:
 
-* `Unauthorized` (HTTP `401`)
-* `not authorized for that account` (HTTP `403`)
-* `zones [...] are not authorized` (HTTP `403`)
-* `does not have access to the path...` (HTTP `403`)
+- `Unauthorized` (HTTP `401`)
+- `not authorized for that account` (HTTP `403`)
+- `zones [...] are not authorized` (HTTP `403`)
+- `does not have access to the path...` (HTTP `403`)
 
 An `Unauthorized` response means the API token or bearer token is missing, expired, or invalid. Verify that you are passing a valid token in the `Authorization` header.
 
@@ -97,6 +97,6 @@ A `403` response means the token does not have the required permissions for the
 
 Sample error message:
 
-* `Internal server error` (HTTP `500`)
+- `Internal server error` (HTTP `500`)
 
 This is a generic error indicating an unexpected failure. If it persists, contact [Cloudflare Support](https://support.cloudflare.com/) with the full request and response, including the `Ray-ID` header from the HTTP response.
diff --git a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
index 2def716afc95aff..4900a64e4e2b8ff 100644
--- a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
+++ b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
@@ -9,14 +9,14 @@ products:
   - graphql-api
 ---
 
-Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time. 
+Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time.
 
 ## Availability
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`). 
-- **Default**: If no confidence level is specified, intervals are not returned. 
+- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`).
+- **Default**: If no confidence level is specified, intervals are not returned.
 
 ## Usage example
 
@@ -28,35 +28,35 @@ To request a confidence interval, use the `confidence(level: X)` argument in you
 
 ```graphql graphql-api-explorer title="A GraphQL query"
 query SingleDatasetWithConfidence($zoneTag: string, $start: Time, $end: Time) {
-  viewer {
-    zones(filter: {zoneTag: $zoneTag}) {
-      firewallEventsAdaptiveGroups(
-        filter: {datetime_gt: $start, datetime_lt: $end}
-        limit: 1000
-      ) {
-        count
-        avg {
-          sampleInterval
-        }
-        confidence(level: 0.95) {
-          count {
-            estimate
-            lower
-            upper
-            sampleSize
-          }
-        }
-      }
-    }
-  }
+	viewer {
+		zones(filter: { zoneTag: $zoneTag }) {
+			firewallEventsAdaptiveGroups(
+				filter: { datetime_gt: $start, datetime_lt: $end }
+				limit: 1000
+			) {
+				count
+				avg {
+					sampleInterval
+				}
+				confidence(level: 0.95) {
+					count {
+						estimate
+						lower
+						upper
+						sampleSize
+					}
+				}
+			}
+		}
+	}
 }
 ```
 
 ### Response
 
-The response includes the following values: 
+The response includes the following values:
 
-- `estimate`: The estimated value, based on sampled data. 
+- `estimate`: The estimated value, based on sampled data.
 - `lower`: The lower bound of the confidence interval.
 - `sampleSize`: The number of sampled data points used to calculate the estimate.
 - `upper`: The upper bound of the confidence interval.
@@ -65,30 +65,30 @@ In this example, the interpretation of the response is that, based on a sample o
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "firewallEventsAdaptiveGroups": [
-            {
-              "avg": {
-                "sampleInterval": 1.0720277625205972
-              },
-              "confidence": {
-                "count": {
-                  "estimate": 42939,
-                  "lower": 42673.44115335711,
-                  "sampleSize": 40054,
-                  "upper": 43204.55884664289
-                }
-              },
-              "count": 42939
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"firewallEventsAdaptiveGroups": [
+						{
+							"avg": {
+								"sampleInterval": 1.0720277625205972
+							},
+							"confidence": {
+								"count": {
+									"estimate": 42939,
+									"lower": 42673.44115335711,
+									"sampleSize": 40054,
+									"upper": 43204.55884664289
+								}
+							},
+							"count": 42939
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
diff --git a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
index 74c6b40c78266f7..d7db4d153f586f2 100644
--- a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
@@ -13,5 +13,4 @@ GraphQL API supports [introspection][1] to explore nodes and provides a way to
 retrieve the user's [limits][2] for every node.
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
-
 [2]: /analytics/graphql-api/features/discovery/settings/
diff --git a/src/content/docs/analytics/graphql-api/features/index.mdx b/src/content/docs/analytics/graphql-api/features/index.mdx
index 7b85fab58b64d62..39fea17f29b3b37 100644
--- a/src/content/docs/analytics/graphql-api/features/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The GraphQL Analytics API offers the following features:
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
index 0e458b325ede871..c6a25630a2aedd7 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
@@ -17,13 +17,13 @@ products:
    ![Editing HTTP Headers Window](~/assets/images/analytics/GraphiQL-edit-http-headers-window.png)
 
 3. Select **Add Header** to configure authentication. You can use Cloudflare Analytics API token authentication (recommended) or Cloudflare API key authentication.
-   * **Token authentication**:
+   - **Token authentication**:
 
      Enter **Authorization** in the **Header Name** field, and enter `Bearer {your-analytics-token}` in the **Header value** field, then select **Save**.
 
      ![Editing HTTP Headers](~/assets/images/analytics/GraphiQL-edit-http-headers-token.png)
 
-   * **Key authentication**:
+   - **Key authentication**:
 
      Enter `X-AUTH-EMAIL` in the **Header name** field and your email address registered with Cloudflare in the **Header value** field, and select **Save**.<br/>
 
@@ -36,10 +36,8 @@ products:
 
 :::note[Note]
 
-
 The right-side response pane is empty when you enter your information correctly. An error displays when there are problems with your header credentials.
 
-
 :::
 
 Now that you have configured authentication, you are ready to run queries using GraphiQL.
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
index ed75b1965e7c919..1e96ffce7142c4b 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
@@ -15,30 +15,40 @@ To secure access to your GraphQL Analytics data, use a Cloudflare API key or tok
 
 This table outlines the differences between Cloudflare API keys and tokens:
 
-
-
 <table>
-  <thead>
-      <tr>
-          <th>Authentication Method</th>
-          <th>Description</th>
-      </tr>
-  </thead>
-  <tbody>
-      <tr>
-        <td><a href='/fundamentals/api/get-started/create-token/'>API Tokens</a></td>
-        <td>Cloudflare recommends API Tokens as the preferred way to interact with Cloudflare APIs. You can configure the scope of tokens to limit access to account and zone resources, and you can define the Cloudflare APIs to which the token authorizes access.</td>
-      </tr>
-      <tr>
-        <td><a href='/fundamentals/api/get-started/keys/'>API Keys</a></td>
-        <td><p>Unique to each Cloudflare user and used only for authentication. API keys do not authorize access to accounts or zones.</p>
-        <p>Use the Global API Key for authentication.</p></td>
-      </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Authentication Method</th>
+			<th>Description</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>
+				<a href="/fundamentals/api/get-started/create-token/">API Tokens</a>
+			</td>
+			<td>
+				Cloudflare recommends API Tokens as the preferred way to interact with
+				Cloudflare APIs. You can configure the scope of tokens to limit access
+				to account and zone resources, and you can define the Cloudflare APIs to
+				which the token authorizes access.
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/fundamentals/api/get-started/keys/">API Keys</a>
+			</td>
+			<td>
+				<p>
+					Unique to each Cloudflare user and used only for authentication. API
+					keys do not authorize access to accounts or zones.
+				</p>
+				<p>Use the Global API Key for authentication.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
-
-
 To create and configure GraphQL Analytics API tokens, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
 
 To find and retrieve API keys, as well as edit HTTP headers for authentication in GraphiQL, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
diff --git a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
index 1839c3f0876e56b..4494649d7315149 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
@@ -28,13 +28,11 @@ Click on the editing pane of GraphiQL and add this base query, replacing
 
 :::note[Note]
 
-
 To find the zone's tag, log in to your Cloudflare account and select the site for
 which you want to obtain the tag. In the Cloudflare dashboard **Overview** page,
 scroll to the **API** section in the right sidebar, which displays your zone and
 account tags.
 
-
 :::
 
 To assist query building, the GraphiQL client has word completion. Insert your
@@ -128,29 +126,16 @@ This example query uses the `zoneTag` query variable to represent the zone ID:
 ![Example of GraphiQL query variables][14]
 
 [1]: /analytics/graphql-api/getting-started/querying-basics/
-
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
-
 [3]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
-
 [4]: ~/assets/images/analytics/graphiql-base-query.png
-
 [5]: ~/assets/images/analytics/graphiql-word-completion.png
-
 [6]: ~/assets/images/analytics/graphiql-set-up-base-query.png
-
 [7]: ~/assets/images/analytics/graphiql-parameters.png
-
 [8]: ~/assets/images/analytics/graphiql-filter-fields.png
-
 [9]: ~/assets/images/analytics/graphiql-filter-values.png
-
 [10]: ~/assets/images/analytics/graphiql-set-up-base-query.png
-
 [11]: ~/assets/images/analytics/graphiql-return-fields.png
-
 [12]: ~/assets/images/analytics/graphiql-query-return-field-values.png
-
 [13]: ~/assets/images/analytics/create-query-fw-data-set-play.png
-
 [14]: ~/assets/images/analytics/graphiql-query-variables.png
diff --git a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
index ab3680fa9a78abb..b1eeb322c398cb7 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
@@ -24,8 +24,8 @@ query:
 
 ```json title="A payload structure for GraphQL API"
 {
-  "query": "{viewer { ... }}",
-  "variables": {}
+	"query": "{viewer { ... }}",
+	"variables": {}
 }
 ```
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
index 0d2d0e248a08cf0..e77cba62457a8e1 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
@@ -79,7 +79,7 @@ query.
 
 For example, `zones` can take a filter of `ZoneFilter_InputObject` type as an
 argument. To view the fields available to filter, select
-**ZoneFilter\_InputObject**.
+**ZoneFilter_InputObject**.
 
 ## Find the datasets available for a zone
 
@@ -122,33 +122,18 @@ The list of fields displays:
 For more information on using GraphiQL, please visit this [guide][16].
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
-
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
-
 [3]: https://altairgraphql.dev/#download
-
 [4]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
-
 [5]: ~/assets/images/analytics/graphiql-docs-link.png
-
 [6]: ~/assets/images/analytics/graphiql-doc-explorer.png
-
 [7]: ~/assets/images/analytics/graphiql-doc-explorer-query-mutations.png
-
 [8]: ~/assets/images/analytics/graphiql-doc-explorer-view-cost.png
-
 [9]: ~/assets/images/analytics/graphiql-doc-explorer-viewer-fields.png
-
 [10]: ~/assets/images/analytics/graphiql-doc-explorer-zones.png
-
 [11]: ~/assets/images/analytics/graphiql-doc-explorer-zone-fields.png
-
 [12]: ~/assets/images/analytics/graphiql-doc-explorer-find-firewall.png
-
 [13]: ~/assets/images/analytics/graphiql-doc-explorer-firewallevents-definition.png
-
 [14]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-type-definition.png
-
 [15]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-fields.png
-
 [16]: /analytics/graphql-api/getting-started/compose-graphql-query/
diff --git a/src/content/docs/analytics/graphql-api/getting-started/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
index 2ba6111561b125e..6b82273dfd942ef 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
@@ -9,19 +9,19 @@ products:
   - graphql-api
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Use these articles to get started with the Cloudflare GraphQL API:
 
-* [Authentication][1] - walks you through the options and the steps required to
+- [Authentication][1] - walks you through the options and the steps required to
   set up your access to Cloudflare API successfully,
-* [Querying basics][2] - brings simple query examples for you to start exploring
+- [Querying basics][2] - brings simple query examples for you to start exploring
   the GraphQL API,
-* [Introspect the GraphQL schema][3] - explains how-to surf the schema with
+- [Introspect the GraphQL schema][3] - explains how-to surf the schema with
   GraphQL client,
-* [Create a query in a GraphQL client][4] - describes how to build and run a
+- [Create a query in a GraphQL client][4] - describes how to build and run a
   query against the Cloudflare GraphQL API in the GraphQL clients,
-* [Use curl to query the GraphQL API][5] - walks you through running a query
+- [Use curl to query the GraphQL API][5] - walks you through running a query
   against the Cloudflare GraphQL API from the command line.
 
 For examples of how to build your own GraphQL Analytics dashboard and query
@@ -29,17 +29,13 @@ specific information, such as Firewall and Workers events, please refer to
 [Tutorials][6].
 
 :::note[Data unavailability: Customer Metadata Boundary configuration]
- <Render file="customer_metadata_boundary_error" product="analytics" /> 
+
+<Render file="customer_metadata_boundary_error" product="analytics" />
 :::
 
 [1]: /analytics/graphql-api/getting-started/authentication/
-
 [2]: /analytics/graphql-api/getting-started/querying-basics/
-
 [3]: /analytics/graphql-api/getting-started/explore-graphql-schema/
-
 [4]: /analytics/graphql-api/getting-started/compose-graphql-query/
-
 [5]: /analytics/graphql-api/getting-started/execute-graphql-query/
-
 [6]: /analytics/graphql-api/tutorials/
diff --git a/src/content/docs/analytics/graphql-api/limits.mdx b/src/content/docs/analytics/graphql-api/limits.mdx
index 5adcc44092add47..41bac079ca31cd6 100644
--- a/src/content/docs/analytics/graphql-api/limits.mdx
+++ b/src/content/docs/analytics/graphql-api/limits.mdx
@@ -19,16 +19,16 @@ plans.
 To support this variety of products, Cloudflare GraphQL API has three layers of
 limits:
 
-* global limits
-* user limits
-* node (dataset) limits
+- global limits
+- user limits
+- node (dataset) limits
 
 ## Global limits
 
 These limits are applied to every query for every plan:
 
-* A zone-scoped query can include up to **10 zones**
-* An account-scoped query can include only **1 account**
+- A zone-scoped query can include up to **10 zones**
+- An account-scoped query can include only **1 account**
 
 Additionally, there is a limited number of queries you can make per request. The total number of queries in a request is equal to the number of zone/account scopes, multiplied by the number of nodes to which they are applied.
 
@@ -46,10 +46,10 @@ the Cloudflare API](/fundamentals/api/reference/limits/).
 
 Each data node has its limits, such as:
 
-* how far back in time can data be requested,
-* the maximum time period (in seconds) that can be requested in one query,
-* the maximum number of fields that can be requested in one query,
-* the maximum number of records that can be returned in one query.
+- how far back in time can data be requested,
+- the maximum time period (in seconds) that can be requested in one query,
+- the maximum number of fields that can be requested in one query,
+- the maximum number of records that can be returned in one query.
 
 Node limits are tied to requested `zoneTag` or `accountTag`. Higher plans have
 access to a greater selection of datasets or fields, and can query over broader historical
diff --git a/src/content/docs/analytics/graphql-api/mcp-server.mdx b/src/content/docs/analytics/graphql-api/mcp-server.mdx
index be3bc98608dc365..79aea053b1121fa 100644
--- a/src/content/docs/analytics/graphql-api/mcp-server.mdx
+++ b/src/content/docs/analytics/graphql-api/mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the GraphQL Analytics MCP server.
 products:
   - analytics
   - graphql-api
----
\ No newline at end of file
+---
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
index 4255d116dd9db69..a0cd2058706d926 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
@@ -17,8 +17,8 @@ If you are currently using the deprecated `httpRequests1mByColoGroups` or `httpR
 
 If you are currently using the Zone Analytics API, the following guide will help you migrate your queries to the new GraphQL Analytics API:
 
-* [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
-* [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
+- [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
+- [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
 
 ## Network Analytics migrations
 
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
index f6c3398fe285308..cfec218853327ed 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: reference
 title: NAv1 to NAv2 schema map
 sidebar:
diff --git a/src/content/docs/analytics/graphql-api/sampling.mdx b/src/content/docs/analytics/graphql-api/sampling.mdx
index ce5299faa9407b8..2dcf4bdf7261ff2 100644
--- a/src/content/docs/analytics/graphql-api/sampling.mdx
+++ b/src/content/docs/analytics/graphql-api/sampling.mdx
@@ -38,15 +38,11 @@ Cloudflare almost always uses **adaptive sampling**, which means the sample rate
 
 The following data nodes are based on fixed sampling, where the sample rate does not vary:
 
-
-
 | Data set                                                                                                                                       |   Rate | Notes                                                                                                                                                                                                |
 | :--------------------------------------------------------------------------------------------------------------------------------------------- | -----: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Firewall Rules Preview<br /><p><b>Nodes:</b><br />`firewallRulePreviewGroups`</p>                                                              |     1% | Use with caution. A 1% sample rate does not provide accurate estimates for datasets smaller than a certain threshold, a scenario the Cloudflare dashboard calls out explicitly but the API does not. |
 | Network Analytics<br /><p><b>Nodes:</b><br />`ipFlows1mGroups`<br />`ipFlows1hGroups`<br />`ipFlows1dGroups`<br />`ipFlows1mAttacksGroups`</p> | 0.012% | Sampling rate is in terms of packet count (1 of every 8,192 packets).                                                                                                                                |
 
-
-
 ## Access to raw data
 
 Because sampling is primarily adaptive and automatically adjusts to provide an accurate estimate, the sampling rate cannot be directly controlled. Enterprise customers have access to raw data via Cloudflare Logs.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
index c74285316775d50..b7bf522c3840234 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
@@ -54,107 +54,107 @@ The returned results will be in JSON format (as requested), so piping the output
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "httpRequestsAdaptiveGroups": [
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-21T10:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19849385,
-                "visits": 4383
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-21T06:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20607204,
-                "visits": 4375
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-26T05:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20170839,
-                "visits": 4519
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-23T08:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20141860,
-                "visits": 4448
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-25T15:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 21070367,
-                "visits": 4469
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-28T08:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19200774,
-                "visits": 4345
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-26T02:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20758067,
-                "visits": 4502
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-20T19:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 22127811,
-                "visits": 4443
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-27T15:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20480644,
-                "visits": 4268
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-27T17:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19885704,
-                "visits": 4287
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"httpRequestsAdaptiveGroups": [
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-21T10:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19849385,
+								"visits": 4383
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-21T06:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20607204,
+								"visits": 4375
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-26T05:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20170839,
+								"visits": 4519
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-23T08:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20141860,
+								"visits": 4448
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-25T15:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 21070367,
+								"visits": 4469
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-28T08:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19200774,
+								"visits": 4345
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-26T02:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20758067,
+								"visits": 4502
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-20T19:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 22127811,
+								"visits": 4443
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-27T15:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20480644,
+								"visits": 4268
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-27T17:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19885704,
+								"visits": 4287
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
@@ -162,13 +162,13 @@ The returned results will be in JSON format (as requested), so piping the output
 
 We are going to use the GraphQL Analytics API to query the top 10 consuming URLs from a zone, helping you identify the URLs with the highest resource usage. Here are some configuration instructions:
 
-* To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
-* Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
-* Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
-* To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
-  * `CURRENTDATE=$(gdate -u +'%FT%TZ')`
-  * `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
-* For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
+- To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
+- Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
+- Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
+- To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
+  - `CURRENTDATE=$(gdate -u +'%FT%TZ')`
+  - `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
+- For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
 
 ### API call
 
@@ -196,4 +196,4 @@ https://api.cloudflare.com/client/v4/graphql \
 }' | jq -r 'try .data.viewer.zones[].topPaths[] | "\"\(.dimensions.metric)\": \(.sum.edgeResponseBytes)"' | sort
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/index.mdx b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
index baf7496c1ef4723..ebcfb6d0cf8b7b2 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/index.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The following resources will help you start exploring your data and creating analytics dashboards:
 
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
index 4fbbc812304c501..7f0e232f641a485 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
@@ -15,9 +15,9 @@ The following API call will request logs for a single Access login event and out
 
 You will need to insert your `<CLOUDFLARE_ACCOUNT_TAG>`, your API credentials in `<API_TOKEN>`[^1], and substitute your own values for the following variables:
 
-* `rayID`: A unique identifier assigned to the authentication request.
-* `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
-* `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
+- `rayID`: A unique identifier assigned to the authentication request.
+- `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
+- `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
 
 ## API Call
 
@@ -65,47 +65,47 @@ https://api.cloudflare.com/client/v4/graphql \
 
 :::note
 
-Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`. 
+Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`.
 :::
 
 ## Response
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "accounts": [
-        {
-          "accessLoginRequestsAdaptiveGroups": [
-            {
-              "dimensions": {
-                "approvingPolicyId": "",
-                "cfRayId": "744927037ce06d68",
-                "country": "US",
-                "datetime": "2022-09-02T20:56:27Z",
-                "deviceId": "",
-                "hasExistingJWT": 0,
-                "hasGatewayEnabled": 0,
-                "hasWarpEnabled": 0,
-                "identityProvider": "nonidentity",
-                "ipAddress": "2a09:bac0:15::814:7b37",
-                "isSuccessfulLogin": 0,
-                "mtlsCertSerialId": "",
-                "mtlsCommonName": "",
-                "mtlsStatus": "NONE",
-                "serviceTokenId": "",
-                "userUuid": ""
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"accounts": [
+				{
+					"accessLoginRequestsAdaptiveGroups": [
+						{
+							"dimensions": {
+								"approvingPolicyId": "",
+								"cfRayId": "744927037ce06d68",
+								"country": "US",
+								"datetime": "2022-09-02T20:56:27Z",
+								"deviceId": "",
+								"hasExistingJWT": 0,
+								"hasGatewayEnabled": 0,
+								"hasWarpEnabled": 0,
+								"identityProvider": "nonidentity",
+								"ipAddress": "2a09:bac0:15::814:7b37",
+								"isSuccessfulLogin": 0,
+								"mtlsCertSerialId": "",
+								"mtlsCommonName": "",
+								"mtlsStatus": "NONE",
+								"serviceTokenId": "",
+								"userUuid": ""
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
 You can compare the query results to your Access policies to understand why a user was blocked. For example, if your application requires a valid mTLS certificate, Access blocked the request shown above because `mtlsStatus`, `mtlsCommonName`, and `mtlsCertSerialId` are empty.
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
index ccd12acea299f70..3e8f9dde667b2df 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
@@ -65,74 +65,74 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "emailRoutingAdaptive": [
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:51:25Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "John <john@email.example.com>",
-              "id": "AfWyaZ7V1TAH",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "How are you doing?",
-              "to": "me@example.com"
-            },
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:30:00Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "eBay <ebay@ebay.co.uk>",
-              "id": "aYPegrIfLWia",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "New offers",
-              "to": "me@example.com"
-            },
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:29:59Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "Notification <notifications@example.com>",
-              "id": "nWIl9gs95mY3",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "You're over quota",
-              "to": "me@example.com"
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"emailRoutingAdaptive": [
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:51:25Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "John <john@email.example.com>",
+							"id": "AfWyaZ7V1TAH",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "How are you doing?",
+							"to": "me@example.com"
+						},
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:30:00Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "eBay <ebay@ebay.co.uk>",
+							"id": "aYPegrIfLWia",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "New offers",
+							"to": "me@example.com"
+						},
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:29:59Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "Notification <notifications@example.com>",
+							"id": "nWIl9gs95mY3",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "You're over quota",
+							"to": "me@example.com"
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
@@ -176,114 +176,114 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "emailRoutingAdaptiveGroups": [
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T11:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T12:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T13:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T14:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T15:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T16:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T17:00:00Z"
-              }
-            },
-            {
-              "count": 3,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T18:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T22:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T01:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T02:00:00Z"
-              }
-            },
-            {
-              "count": 4,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T05:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T08:00:00Z"
-              }
-            },
-            {
-              "count": 5,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T09:00:00Z"
-              }
-            },
-            {
-              "count": 6,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T10:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T11:00:00Z"
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"emailRoutingAdaptiveGroups": [
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T11:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T12:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T13:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T14:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T15:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T16:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T17:00:00Z"
+							}
+						},
+						{
+							"count": 3,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T18:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T22:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T01:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T02:00:00Z"
+							}
+						},
+						{
+							"count": 4,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T05:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T08:00:00Z"
+							}
+						},
+						{
+							"count": 5,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T09:00:00Z"
+							}
+						},
+						{
+							"count": 6,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T10:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T11:00:00Z"
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
index deab15ea91ace34..3d4c56d42ef286d 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
@@ -9,8 +9,9 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-endpoint-health-checks"
+<Render
+	file="graphql/query-magic-transit-endpoint-health-checks"
 	product="networking-services"
 />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
index 727a62e37b0ac21..0c1fc135106eaa8 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
@@ -9,8 +9,10 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
-	params={{ productName: "Magic Transit or Cloudflare WAN" }} />
+	params={{ productName: "Magic Transit or Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
index 3ed3c1e2b7fce50..7e2d5a042de9744 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
@@ -9,9 +9,10 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
 	params={{ productName: "Magic Transit or Cloudflare WAN" }}
 />
diff --git a/src/content/docs/analytics/index.mdx b/src/content/docs/analytics/index.mdx
index 8c9eca78825e740..7f6b64667dccaec 100644
--- a/src/content/docs/analytics/index.mdx
+++ b/src/content/docs/analytics/index.mdx
@@ -11,38 +11,52 @@ products:
   - analytics
 ---
 
-import { Feature, RelatedProduct } from "~/components"
+import { Feature, RelatedProduct } from "~/components";
 
 Cloudflare visualizes the metadata collected by our products in the Cloudflare dashboard. Refer to [Types of analytics](/analytics/types-of-analytics/) for more information about the various types of analytics and where they exist in the dashboard.
 
-***
+---
 
 ## Features
 
 <Feature header="Workers Analytics Engine" href="/analytics/analytics-engine/">
-Send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL. 
+	Send unlimited-cardinality data from your Worker to a time-series database.
+	Query it with SQL.
 </Feature>
 
-<Feature header="Account and zone analytics" href="/analytics/account-and-zone-analytics/">
-Provides details about the requests and traffic related to your Cloudflare accounts and zones. 
+<Feature
+	header="Account and zone analytics"
+	href="/analytics/account-and-zone-analytics/"
+>
+	Provides details about the requests and traffic related to your Cloudflare
+	accounts and zones.
 </Feature>
 
-<Feature header="Cloudflare Network Analytics" href="/analytics/network-analytics/">
-Provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. 
+<Feature
+	header="Cloudflare Network Analytics"
+	href="/analytics/network-analytics/"
+>
+	Provides near real-time visibility into network and transport-layer traffic
+	patterns and DDoS attacks.
 </Feature>
 
 <Feature header="GraphQL Analytics API" href="/analytics/graphql-api/">
-Provides all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account. 
+	Provides all of your performance, security, and reliability data from one
+	endpoint. Select exactly what you need, from one metric for a domain to
+	multiple metrics aggregated for your account.
 </Feature>
 
-***
+---
 
 ## Related products
 
 <RelatedProduct header="Workers" href="/workers/" product="workers">
-Cloudflare Workers allows developers to build serverless applications and deploy instantly across the globe for exceptional performance, reliability, and scale. 
+	Cloudflare Workers allows developers to build serverless applications and
+	deploy instantly across the globe for exceptional performance, reliability,
+	and scale.
 </RelatedProduct>
 
 <RelatedProduct header="Logs" href="/logs/" product="logs">
-Detailed logs that contain metadata generated by Cloudflare products helpful for debugging, identifying configuration adjustments, and creating analytics. 
+	Detailed logs that contain metadata generated by Cloudflare products helpful
+	for debugging, identifying configuration adjustments, and creating analytics.
 </RelatedProduct>
diff --git a/src/content/docs/analytics/network-analytics/configure/index.mdx b/src/content/docs/analytics/network-analytics/configure/index.mdx
index 960840cbc5deb03..16e7bfa95e54afc 100644
--- a/src/content/docs/analytics/network-analytics/configure/index.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/network-analytics/configure/share-export.mdx b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
index ebfbca66506210a..4f80063b389f3a8 100644
--- a/src/content/docs/analytics/network-analytics/configure/share-export.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
@@ -11,7 +11,7 @@ products:
   - analytics
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 ## Share Network Analytics filters
 
diff --git a/src/content/docs/analytics/network-analytics/configure/time-range.mdx b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
index f22f93aa5d6e373..4cad33741de7676 100644
--- a/src/content/docs/analytics/network-analytics/configure/time-range.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
@@ -17,7 +17,7 @@ Use the timeframe drop-down list to change the time range over which Network Ana
 
 In the Network Analytics dashboard, the range of historical data you can query is 112 days.
 
-When you select *Previous 30 minutes*, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A *Live* notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
+When you select _Previous 30 minutes_, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A _Live_ notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
 
 ![Timeframe drop-down with Previous 30 minutes selected.](~/assets/images/analytics/network-analytics/timeframe-selector.png)
 
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
index e8908c5bbfc3b1e..72d38cdbd6e45a7 100644
--- a/src/content/docs/analytics/network-analytics/index.mdx
+++ b/src/content/docs/analytics/network-analytics/index.mdx
@@ -12,7 +12,7 @@ products:
   - analytics
 ---
 
-import { InlineBadge, Render } from "~/components"
+import { InlineBadge, Render } from "~/components";
 
 Cloudflare Network Analytics (version 2) provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. Network Analytics visualizes packet and bit-level data, the same data available via the Network Analytics dataset of the GraphQL Analytics API.
 
@@ -22,12 +22,12 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
 
 ## Remarks
 
-* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
+- The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
 
-* The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
+- The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
 
 ## Related resources
 
-* [Cloudflare GraphQL API](/analytics/graphql-api/)
-* [Cloudflare Logpush](/logs/logpush/)
-* [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
\ No newline at end of file
+- [Cloudflare GraphQL API](/analytics/graphql-api/)
+- [Cloudflare Logpush](/logs/logpush/)
+- [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
diff --git a/src/content/docs/analytics/network-analytics/reference/index.mdx b/src/content/docs/analytics/network-analytics/reference/index.mdx
index bfaf9377cbe9497..50a9131063634e7 100644
--- a/src/content/docs/analytics/network-analytics/reference/index.mdx
+++ b/src/content/docs/analytics/network-analytics/reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review reference information about Cloudflare Network Analytics:
 
diff --git a/src/content/docs/analytics/network-analytics/understand/index.mdx b/src/content/docs/analytics/network-analytics/understand/index.mdx
index 364ff4458dc64da..6bbfaed1b7957b3 100644
--- a/src/content/docs/analytics/network-analytics/understand/index.mdx
+++ b/src/content/docs/analytics/network-analytics/understand/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/sampling.mdx b/src/content/docs/analytics/sampling.mdx
index 815514bf77937e5..964b7405a3d5f1a 100644
--- a/src/content/docs/analytics/sampling.mdx
+++ b/src/content/docs/analytics/sampling.mdx
@@ -8,7 +8,7 @@ products:
   - analytics
 ---
 
-[Sampling](https://en.wikipedia.org/wiki/Sampling_(statistics)) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
+[Sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
 
 ## How sampling works
 
@@ -20,17 +20,17 @@ To make this possible, data is stored at multiple resolutions (100%, 10%, 1%), e
 
 Cloudflare's data pipeline handles [over 700 million events per second](https://blog.cloudflare.com/how-we-make-sense-of-too-much-data) (and growing) across its global network. Processing and storing all this data in real-time would be prohibitively expensive and time-consuming. By leveraging carefully designed sampling methods, Cloudflare Analytics delivers accurate and actionable data, balancing precision with performance.
 
-Sampling enables: 
+Sampling enables:
 
 - **Scalability**: Reduces the volume of data processed without compromising insights.
 - **Performance**: Speeds up query execution for analytics.
 - **Cost-Efficiency**: Minimizes resource usage and storage needs.
 
-## Can I trust sampled data? 
+## Can I trust sampled data?
 
 Sampled data is highly reliable, and can provide insights that are as dependable as those derived from full datasets. Cloudflare designs sampling techniques to ensure we capture the essential characteristics of the entire dataset, delivering results you can trust.
 
-Sampling is an approach similarly used in other domains, for instance: 
+Sampling is an approach similarly used in other domains, for instance:
 
 - Google Maps: Just as online maps display lower-resolution images when zoomed out and higher-resolution images when zoomed in — keeping the total number of pixels relatively constant — Cloudflare Analytics dynamically adjusts sampling rates to efficiently provide insights, ensuring queries return consistent and accurate results regardless of dataset size.
 
@@ -44,23 +44,26 @@ In the near future, we plan to expose confidence intervals along with query resu
 
 ## Additional considerations
 
-**When sampling occurs** 
+**When sampling occurs**
+
 - Sampling is typically applied to very high-traffic datasets where full data analysis would be impractical.
 - For smaller datasets, full data analysis is often performed without sampling.
 
-**Sampling rates** 
+**Sampling rates**
+
 - Sampling rates vary depending on the dataset and product.
 - Cloudflare ensures that sampling rates are consistent within a single dataset to maintain accuracy across queries.
 
-**Impact on metrics** 
+**Impact on metrics**
+
 - While sampling reduces the volume of processed data, aggregated metrics like totals, averages, and percentiles are extrapolated based on the sample size. This ensures the reported metrics represent the entire dataset accurately.
 
 **Limitations**
-- Sampling may not capture extremely rare events with very low occurrence rates. 
+
+- Sampling may not capture extremely rare events with very low occurrence rates.
 
 **Sampling in analytics interfaces**
+
 - GraphQL API: Sampling metadata is included in the query response. For more information, refer to the sampling [GraphQL Analytics API](/analytics/graphql-api/sampling/) documentation.
 - Workers Analytics Engine: For more information, refer to the [Workers Analytics Engine](/analytics/analytics-engine/sampling/) documentation.
 - Dashboard Analytics: Displays an icon with the sampled percentage of data, if sampled data was used for the visualization.
-
-
diff --git a/src/content/docs/analytics/types-of-analytics.mdx b/src/content/docs/analytics/types-of-analytics.mdx
index 3754f8a0ce803d1..9b13d4d6e16b1d5 100644
--- a/src/content/docs/analytics/types-of-analytics.mdx
+++ b/src/content/docs/analytics/types-of-analytics.mdx
@@ -40,25 +40,24 @@ Access aggregated traffic, security, and performance metrics for each domain pro
 
 Data available under the **Analytics & Logs** section includes:
 
-* **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
-* **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
-* **Performance** - Origin Performance, Bandwidth Saved.
-* **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
-* **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
-* **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
-* **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
+- **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
+- **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
+- **Performance** - Origin Performance, Bandwidth Saved.
+- **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
+- **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
+- **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
+- **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
 
 ## Product analytics
 
 Beyond the analytics provided for your properties, you can also access analytics related to specific products:
 
-* [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
-* [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
-* [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
-* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
-* [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
-* [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
-
+- [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
+- [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
+- [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
+- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
+- [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
+- [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
 
 ## GraphQL APIs
 
diff --git a/src/content/docs/api-shield/api-gateway.mdx b/src/content/docs/api-shield/api-gateway.mdx
index 7eb6722be62e2c5..159a13ee168f6ba 100644
--- a/src/content/docs/api-shield/api-gateway.mdx
+++ b/src/content/docs/api-shield/api-gateway.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 7
-
 ---
 
 Cloudflare API Shield provides API security, management tools, and integration with the Cloudflare Developer Platform for building new APIs.
diff --git a/src/content/docs/api-shield/glossary.mdx b/src/content/docs/api-shield/glossary.mdx
index f3d2e75924932cd..8cec6bbf2bf209c 100644
--- a/src/content/docs/api-shield/glossary.mdx
+++ b/src/content/docs/api-shield/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 sidebar:
   order: 9
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's API Shield documentation.
 
diff --git a/src/content/docs/api-shield/index.mdx b/src/content/docs/api-shield/index.mdx
index 17d437901096fc5..f95940e11bfbf9e 100644
--- a/src/content/docs/api-shield/index.mdx
+++ b/src/content/docs/api-shield/index.mdx
@@ -11,11 +11,15 @@ head:
     content: Overview
 ---
 
-import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
+import {
+	Description,
+	Feature,
+	Plan,
+	RelatedProduct,
+	Render,
+} from "~/components";
 
-<Description>
-Identify and address your API vulnerabilities.
-</Description>
+<Description>Identify and address your API vulnerabilities.</Description>
 
 <Plan type="ent-add-on" />
 
@@ -37,11 +41,14 @@ Refer to the [Get started](/api-shield/get-started/) guide to set up API Shield.
 ## Features
 
 <Feature header="Security features" href="/api-shield/security/">
-Secure your APIs using API Shield's security features.
+	Secure your APIs using API Shield's security features.
 </Feature>
 
-<Feature header="Management, monitoring, and more" href="/api-shield/management-and-monitoring/">
-Monitor the health of your API endpoints.
+<Feature
+	header="Management, monitoring, and more"
+	href="/api-shield/management-and-monitoring/"
+>
+	Monitor the health of your API endpoints.
 </Feature>
 
 ## Availability
@@ -56,6 +63,11 @@ API Shield currently does not work for JDCloud customers.
 
 ## Related products
 
-<RelatedProduct header="DDoS Protection" href="/ddos-protection/" product="ddos-protection">
-Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised.
+<RelatedProduct
+	header="DDoS Protection"
+	href="/ddos-protection/"
+	product="ddos-protection"
+>
+	Cloudflare DDoS protection secures websites, applications, and entire networks
+	while ensuring the performance of legitimate traffic is not compromised.
 </RelatedProduct>
diff --git a/src/content/docs/api-shield/management-and-monitoring/index.mdx b/src/content/docs/api-shield/management-and-monitoring/index.mdx
index 182cc0cab64e27c..166b939d9e38c8e 100644
--- a/src/content/docs/api-shield/management-and-monitoring/index.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/index.mdx
@@ -6,11 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 5
-  group: 
+  group:
     hideIndex: true
-
 ---
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
index 7139806c6c0866c..34134ffed50f975 100644
--- a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
@@ -6,14 +6,14 @@ products:
 title: Session identifiers
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="session-identifiers" product="api-shield" />
 
 :::note
+
 <Render file="required-session-identifiers" product="api-shield" />
 :::
 
diff --git a/src/content/docs/api-shield/plans.mdx b/src/content/docs/api-shield/plans.mdx
index 7cba5403983b3bc..e54a67a1da3c703 100644
--- a/src/content/docs/api-shield/plans.mdx
+++ b/src/content/docs/api-shield/plans.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 3
-
 ---
 
 Free, Pro, Business, and Enterprise customers without an API Shield subscription can access [Endpoint Management](/api-shield/management-and-monitoring/) and [Schema validation](/api-shield/security/schema-validation/), but no other [API Shield](/api-shield/) features.
@@ -15,10 +14,10 @@ To subscribe to API Shield, upgrade to an Enterprise plan and contact your accou
 
 Limits to endpoints apply to Endpoint Management and Schema validation. Refer to the table below for limits based on your zone plan.
 
-| Plan type | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action |
-| --- | --- | --- | --- | --- |
-| **Free** | 100 | 5 | 200 kB | `Block` only |
-| **Pro** | 250 | 5 | 500 kB | `Block` only |
-| **Business** | 500 | 10 | 2 MB | `Block` only |
-| **Enterprise without API Shield** | 500 | 10 | 5 MB | `Log` or `Block` |
-| **Enterprise with API Shield** | 10,000 | 10+ | 10+ MB | `Log` or `Block` |
\ No newline at end of file
+| Plan type                         | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action      |
+| --------------------------------- | --------------- | ---------------- | -------------------------- | ---------------- |
+| **Free**                          | 100             | 5                | 200 kB                     | `Block` only     |
+| **Pro**                           | 250             | 5                | 500 kB                     | `Block` only     |
+| **Business**                      | 500             | 10               | 2 MB                       | `Block` only     |
+| **Enterprise without API Shield** | 500             | 10               | 5 MB                       | `Log` or `Block` |
+| **Enterprise with API Shield**    | 10,000          | 10+              | 10+ MB                     | `Log` or `Block` |
diff --git a/src/content/docs/api-shield/reference/classic-schema-validation.mdx b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
index 7e5925a84e6068a..4fefbda61645691 100644
--- a/src/content/docs/api-shield/reference/classic-schema-validation.mdx
+++ b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
@@ -12,10 +12,9 @@ sidebar:
     text: Deprecated
   order: 1
   label: Classic Schema validation
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 :::caution[Deprecation notice]
 Classic Schema validation has been deprecated.
@@ -41,14 +40,11 @@ To configure Schema validation in the Cloudflare dashboard:
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Select **Security** > **API Shield**.
 3. Go to **Schema validation** and select **Add schema**.
-4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the *Hostname* field — equal to `api.example.com` — and a check for the *URI Path* field using a regular expression — matching the regex `^/v1`.
-:::caution[Important]
+4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the _Hostname_ field — equal to `api.example.com` — and a check for the _URI Path_ field using a regular expression — matching the regex `^/v1`.
+   :::caution[Important]
 
-To validate the hostname, you must include the *Hostname* field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
-:::
-5. Select **Next**.
-6. Upload your schema file.
-7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
+To validate the hostname, you must include the _Hostname_ field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
+::: 5. Select **Next**. 6. Upload your schema file. 7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
 
 After deploying your API Shield rule, Cloudflare displays a summary of all <GlossaryTooltip term="API endpoint">API endpoints</GlossaryTooltip> organized by their protection level and actions that will occur for non-compliant and unprotected requests.
 
diff --git a/src/content/docs/api-shield/reference/index.mdx b/src/content/docs/api-shield/reference/index.mdx
index d51edc253455ed3..e0fb94f82c8316e 100644
--- a/src/content/docs/api-shield/reference/index.mdx
+++ b/src/content/docs/api-shield/reference/index.mdx
@@ -6,12 +6,11 @@ products:
   - api-shield
 sidebar:
   order: 6
-  group: 
+  group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about API Shield:
 
diff --git a/src/content/docs/api-shield/reference/terraform.mdx b/src/content/docs/api-shield/reference/terraform.mdx
index 823b0b64274405a..8e5c5b8d6c3be74 100644
--- a/src/content/docs/api-shield/reference/terraform.mdx
+++ b/src/content/docs/api-shield/reference/terraform.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 tags:
   - Terraform
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Get started with API Shield using Terraform from the examples below. For more information on how to use Terraform with Cloudflare, refer to the [Terraform documentation](/terraform/).
 
@@ -62,7 +61,7 @@ resource "cloudflare_api_shield_operation" "get_image" {
   host     = "example.com"
   endpoint = "/api/images/{var1}"
 }
- 
+
 resource "cloudflare_api_shield_operation" "post_image" {
   zone_id  = var.zone_id
   method   = "POST"
@@ -75,7 +74,7 @@ resource "cloudflare_api_shield_operation" "post_image" {
 
 :::note
 
-It is required to configure Endpoint Management if you want to set up Schema validation using Terraform. 
+It is required to configure Endpoint Management if you want to set up Schema validation using Terraform.
 :::
 
 Refer to the example configuration below to manage [Schema validation](/api-shield/security/schema-validation/api/) on your zone.
@@ -90,13 +89,13 @@ resource "cloudflare_schema_validation_schemas" "example_schema" {
   source             = file("./schemas/example-schema.yaml")
   validation_enabled = true
 }
- 
+
 # Block all requests that violate schema by default
 resource "cloudflare_schema_validation_settings" "zone_level_settings" {
   zone_id                              = var.zone_id
   validation_default_mitigation_action = "block"
 }
- 
+
 # For endpoint post_image - only log requests that violate schema
 resource "cloudflare_schema_validation_operation_settings" "post_image_log_only" {
   zone_id           = var.zone_id
diff --git a/src/content/docs/api-shield/security/graphql-protection/index.mdx b/src/content/docs/api-shield/security/graphql-protection/index.mdx
index c8c4dfc16b03dd8..6d8f7feb449ca0d 100644
--- a/src/content/docs/api-shield/security/graphql-protection/index.mdx
+++ b/src/content/docs/api-shield/security/graphql-protection/index.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 5
-
 ---
 
 GraphQL is a query language for APIs. In addition to protecting RESTful APIs, Cloudflare can also protect GraphQL APIs.
diff --git a/src/content/docs/api-shield/security/index.mdx b/src/content/docs/api-shield/security/index.mdx
index 36a3a3e4120f463..63dde51928c06d0 100644
--- a/src/content/docs/api-shield/security/index.mdx
+++ b/src/content/docs/api-shield/security/index.mdx
@@ -6,22 +6,19 @@ products:
   - api-shield
 sidebar:
   order: 4
-
 ---
 
-import { DirectoryListing } from "~/components"
-
+import { DirectoryListing } from "~/components";
 
 Cloudflare offers the following features to help secure your APIs:
 
-| Discovery & management | Posture management | Runtime protection |
-| --- | --- | --- |
-| [API Discovery](/api-shield/security/api-discovery/) | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/) | [Schema validation](/api-shield/security/schema-validation/) |
-| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/) | [JWT validation](/api-shield/security/jwt-validation/) |
-| [Sequence Analytics](/api-shield/security/sequence-analytics/) | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/) |
-| | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels) | [Mutual TLS (mTLS)](/api-shield/security/mtls/) |
-| | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) | [GraphQL query protection](/api-shield/security/graphql-protection/) |
-
+| Discovery & management                                                                        | Posture management                                                                 | Runtime protection                                                   |
+| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
+| [API Discovery](/api-shield/security/api-discovery/)                                          | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/)     | [Schema validation](/api-shield/security/schema-validation/)         |
+| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/)             | [JWT validation](/api-shield/security/jwt-validation/)               |
+| [Sequence Analytics](/api-shield/security/sequence-analytics/)                                | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/)     |
+|                                                                                               | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels)  | [Mutual TLS (mTLS)](/api-shield/security/mtls/)                      |
+|                                                                                               | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/)               | [GraphQL query protection](/api-shield/security/graphql-protection/) |
 
 ## Example Cloudflare solutions
 
@@ -29,29 +26,23 @@ Cloudflare API Shield, together with other Cloudflare products, helps protect yo
 
 The following table maps each OWASP vulnerability to the Cloudflare features that address it:
 
-| OWASP issue                                     | Example Cloudflare solution                                                                                                                            |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| OWASP issue                                     | Example Cloudflare solution                                                                                                                                                                                                             |
+| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Broken Object Level Authorization               | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/), [Sequence mitigation], [Schema validation], [JWT validation], [Rate Limiting], [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) |
 | Broken Authentication                           | [Authentication Posture](/api-shield/security/authentication-posture/), [mTLS](/api-shield/security/mtls/), [JWT validation], [Exposed Credential Checks](/waf/managed-rules/check-for-exposed-credentials/), [Bot Management](/bots/)  |
-| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                  |
-| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                   |
-| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                  |
-| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                    |
-| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                       |
-| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                            |
-| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                   |
-| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                  |
+| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
+| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                    |
+| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
+| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                                     |
+| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                                                                                                        |
+| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                                                                                                             |
+| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                                                                                                    |
+| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                                                                                                   |
 
 [Schema validation]: /api-shield/security/schema-validation/
-
 [Sequence mitigation]: /api-shield/security/sequence-mitigation/
-
 [JWT validation]: /api-shield/security/jwt-validation/
-
 [GraphQL Query Protection]: /api-shield/security/graphql-protection/
-
 [Bot management]: /bots/
-
 [Rate limiting]: /waf/rate-limiting-rules/
-
 [WAF managed rules]: /waf/managed-rules/
diff --git a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
index 412e2ee5573001d..e37fc920b98921f 100644
--- a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
@@ -14,7 +14,7 @@ tags:
   - JavaScript
 ---
 
-import { Steps } from "~/components"
+import { Steps } from "~/components";
 
 Use a Worker to automatically keep your identity provider’s latest public key in the JWT validation configuration.
 
diff --git a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
index 102b9af7bb9bb5e..69906adc1b47b63 100644
--- a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
@@ -13,7 +13,7 @@ tags:
   - JSON web token (JWT)
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 You can forward information from a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) to the origin in a header by creating [Transform Rules](/rules/transform/) using claims that Cloudflare has verified via the JSON Web Token.
 
@@ -44,4 +44,4 @@ As an example, to send the `x-send-jwt-claim-user` request header to the origin,
     lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
     ```
     `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT validation and `claim_name` is the JWT claim you want to add to the header.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/api-shield/security/mtls/byo-ca.mdx b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
index 2430485da76550a..90b2c59cd2ff56e 100644
--- a/src/content/docs/api-shield/security/mtls/byo-ca.mdx
+++ b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/client-certificates/byo-ca/
 sidebar:
   order: 3
-
 ---
diff --git a/src/content/docs/api-shield/security/mtls/index.mdx b/src/content/docs/api-shield/security/mtls/index.mdx
index 6652a44adef3c34..c7984dc34ab21f2 100644
--- a/src/content/docs/api-shield/security/mtls/index.mdx
+++ b/src/content/docs/api-shield/security/mtls/index.mdx
@@ -8,7 +8,6 @@ sidebar:
   order: 7
 tags:
   - mTLS
-
 ---
 
 import { GlossaryDefinition, Render } from "~/components";
diff --git a/src/content/docs/api-shield/security/sequence-analytics.mdx b/src/content/docs/api-shield/security/sequence-analytics.mdx
index 34a24e55bdceb85..c70bf1c1ef13f37 100644
--- a/src/content/docs/api-shield/security/sequence-analytics.mdx
+++ b/src/content/docs/api-shield/security/sequence-analytics.mdx
@@ -6,10 +6,9 @@ products:
 title: Sequence Analytics
 sidebar:
   order: 3
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Sequence Analytics tracks the order of API endpoint requests over time, allowing you to discover how users interact with your API. Sequence Analytics groups and highlights important user journeys (sequences) across your API. You can enforce preferred sequences using [Sequence mitigation](/api-shield/security/sequence-mitigation/).
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
index c3bf0a409084cde..33320b54ef171ed 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
@@ -10,24 +10,23 @@ sidebar:
 head:
   - tag: title
     content: Configure sequence mitigation via the API
-
 ---
 
 Configuring sequence mitigation via the API consists of building a rule object by choosing the sequence and setting the type of rule and its action.
 
 ```json title="Example of a rule object"
 {
-    "id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
-    "title": "<RULE_TITLE>",
-    "kind": "allow",
-    "action": "block",
-    "sequence": [
-     "0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
-     "b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
-    ],
-    "priority": 0,
-    "last_updated": "2023-07-24T12:06:51.796286Z",
-    "created_at": "2023-07-24T12:06:51.796286Z"
+	"id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
+	"title": "<RULE_TITLE>",
+	"kind": "allow",
+	"action": "block",
+	"sequence": [
+		"0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
+		"b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
+	],
+	"priority": 0,
+	"last_updated": "2023-07-24T12:06:51.796286Z",
+	"created_at": "2023-07-24T12:06:51.796286Z"
 }
 ```
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
index 08a2a8da0c12da5..5d43aabef5e991b 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
@@ -7,14 +7,14 @@ products:
 sidebar:
   order: 4
   label: Custom rules
-
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
 
 These rules are similar to [cookie sequence rules](/bots/additional-configurations/sequence-rules/) but have a different set of prerequisites:
+
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.
 - Because they require session identifiers, they can only be used on traffic that can be clearly attributed to individual users through session identifiers (authenticated traffic).
 - Because Cloudflare stores the user state in memory and not in a cookie, a session's sequence lifetime is limited to 10 minutes.
@@ -25,6 +25,7 @@ Rules built using these custom rules are similar to the sequence rules that can
 ## Availability
 
 :::note
+
 <Render file="sequence-mitigation-availability" product="api-shield" />
 :::
 
@@ -41,30 +42,30 @@ Each saved endpoint will have an endpoint ID visible in its details page in Endp
 The visitor must wait more than 2 seconds after requesting endpoint `aaaaaaaa` before requesting endpoint `bbbbbbbb`:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and 
+cf.sequence.current_op eq "bbbbbbbb" and
 cf.sequence.msec_since_op["aaaaaaaa"] ge 2000
 ```
 
 The visitor must request endpoints `aaaaaaaa`, then `bbbbbbbb`, then `cccccccc` in that exact order:
 
 ```txt
-cf.sequence.current_op eq "cccccccc" and 
-cf.sequence.previous_ops[0] == "bbbbbbbb" and 
+cf.sequence.current_op eq "cccccccc" and
+cf.sequence.previous_ops[0] == "bbbbbbbb" and
 cf.sequence.previous_ops[1] == "aaaaaaaa"
 ```
 
 The visitor must request endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, but endpoint `aaaaaaaa` can be anywhere in the previous 10 requests:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and 
+cf.sequence.current_op eq "bbbbbbbb" and
 any(cf.sequence.previous_ops[*] == "aaaaaaaa")
 ```
 
 The visitor must request either endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, or endpoint `cccccccc` before endpoint `bbbbbbbb`:
 
 ```txt
-(cf.sequence.current_op eq "bbbbbbbb" and 
-any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or 
-(cf.sequence.current_op eq "bbbbbbbb" and 
+(cf.sequence.current_op eq "bbbbbbbb" and
+any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or
+(cf.sequence.current_op eq "bbbbbbbb" and
 any(cf.sequence.previous_ops[*] == "cccccccc"))
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
index 184e0fe3410c88c..7672a8fafa6039f 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 sidebar:
   order: 4
-
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 Sequence mitigation allows you to enforce request patterns for authenticated clients communicating with your API.
 
@@ -30,7 +29,7 @@ Using sequence mitigation, you can enforce that request pattern with two new seq
 
 :::note
 
-You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/). 
+You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/).
 :::
 
 ## Process
@@ -54,7 +53,6 @@ A negative security model may be useful if you see abusive behavior that is outs
 
 For example, if there was an authorization bug that allowed users to iterate through other users' profiles that contain account numbers via `GET /api/v1/users/{var1}/profile` and then a user tries to make fraudulent funds transfers, you could create a rule to block or log the sequence `GET /api/v1/users/{var1}/profile` to `POST /api/v1/transferFunds`.
 
-
 ## Limitations
 
 ### Endpoint Management
@@ -87,4 +85,4 @@ For example, if you create a rule requiring one endpoint to be requested before
 
 ## Availability
 
-<Render file="sequence-mitigation-availability" product="api-shield" />
\ No newline at end of file
+<Render file="sequence-mitigation-availability" product="api-shield" />
diff --git a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
index ac20b0d38774fb5..4b6e8f08729bae2 100644
--- a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
+++ b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
@@ -6,10 +6,9 @@ products:
 title: Volumetric Abuse Detection
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components"
+import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components";
 
 Cloudflare Volumetric Abuse Detection generates per-endpoint, per-session rate limit recommendations that adjust automatically as your traffic patterns change.
 
@@ -27,7 +26,7 @@ Volumetric Abuse Detection rate limits are a way to prevent blatant volumetric a
 
 Volumetric Abuse Detection analyzes your API's individual session traffic statistics to recommend per-endpoint, per-session rate limits.
 
-To access your endpoints: 
+To access your endpoints:
 
 Old dashboard: **Security** > **API Shield** > **Endpoint Management**
 
@@ -47,7 +46,7 @@ Thresholds are suggested only for endpoints that satisfy all of the following re
 
 After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in the Cloudflare dashboard.
 
-### Rate limiting recommendation calculation 
+### Rate limiting recommendation calculation
 
 Select an endpoint row in **Endpoints** to view its rate limit recommendation. The detail view shows the overall recommended value and percentile-based values (p50, p90, p99).
 
@@ -73,8 +72,8 @@ Refer to the [Rules documentation](/waf/rate-limiting-rules/create-zone-dashboar
 [Rate limit recommendations are available via the API](/api/resources/api_gateway/subresources/operations/methods/get/) if you would like to dynamically update rate limits over time.
 
 <APIRequest
-  path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
-  method="GET"
+	path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
+	method="GET"
 />
 
 ## Special cases
diff --git a/src/content/docs/argo-smart-routing/analytics.mdx b/src/content/docs/argo-smart-routing/analytics.mdx
index 73046eae32ef933..8ba08d6be3c3f77 100644
--- a/src/content/docs/argo-smart-routing/analytics.mdx
+++ b/src/content/docs/argo-smart-routing/analytics.mdx
@@ -22,18 +22,15 @@ You can access Argo analytics for your domain in the [Cloudflare dashboard](http
 
 :::note
 
-
 Detailed performance data within **Origin Performance (Argo)** will only display if Argo has routed at least 500 origin requests within the last 48 hours.
 
-
 :::
 
 ## Types of analytics
 
 The dashboard displays two different views for performance data:
 
-* **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
-
-* **Geography**: A map shows the improvement in response time at each Cloudflare data center.
+- **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
 
-  * A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
+- **Geography**: A map shows the improvement in response time at each Cloudflare data center.
+  - A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
diff --git a/src/content/docs/argo-smart-routing/argo-for-packets.mdx b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
index 8d4a1b15407b0ce..b2e857fe5dca3da 100644
--- a/src/content/docs/argo-smart-routing/argo-for-packets.mdx
+++ b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
@@ -6,7 +6,6 @@ products:
   - argo-smart-routing
 sidebar:
   order: 4
-
 ---
 
 Argo for Packets optimizes IP layer network routing for Cloudflare network services products, including [Magic Transit](/magic-transit/), [Cloudflare WAN](/cloudflare-wan/) (formerly Magic WAN), and [Cloudflare for Offices](https://blog.cloudflare.com/cloudflare-for-offices/).
diff --git a/src/content/docs/artifacts/api/errors.mdx b/src/content/docs/artifacts/api/errors.mdx
index 7545813cd7cbfa2..467365dbf5b37c7 100644
--- a/src/content/docs/artifacts/api/errors.mdx
+++ b/src/content/docs/artifacts/api/errors.mdx
@@ -15,17 +15,17 @@ This is a list of Artifacts errors.
 
 ## Error codes
 
-| Name | Code | Description |
-|------|------|-------------|
-| `ALREADY_EXISTS` | 10201 | The target repository already exists in the namespace. |
-| `NOT_FOUND` | 10200 | The repository or remote resource does not exist. |
-| `IMPORT_IN_PROGRESS` | 10302 | The repository is still being imported and is not yet available. |
-| `FORK_IN_PROGRESS` | 10303 | The repository is still being forked and is not yet available. |
-| `INVALID_INPUT` | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
-| `INVALID_REPO_NAME` | 10101 | The repository name does not meet naming requirements. |
-| `INVALID_TTL` | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds). |
-| `INVALID_URL` | 10104 | The source URL does not point to a valid git repository. |
-| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication. |
-| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached. |
-| `MEMORY_LIMIT` | 10402 | The operation exceeds service memory limits. |
-| `INTERNAL_ERROR` | 10400 | An unexpected internal error occurred. |
+| Name                   | Code  | Description                                                               |
+| ---------------------- | ----- | ------------------------------------------------------------------------- |
+| `ALREADY_EXISTS`       | 10201 | The target repository already exists in the namespace.                    |
+| `NOT_FOUND`            | 10200 | The repository or remote resource does not exist.                         |
+| `IMPORT_IN_PROGRESS`   | 10302 | The repository is still being imported and is not yet available.          |
+| `FORK_IN_PROGRESS`     | 10303 | The repository is still being forked and is not yet available.            |
+| `INVALID_INPUT`        | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
+| `INVALID_REPO_NAME`    | 10101 | The repository name does not meet naming requirements.                    |
+| `INVALID_TTL`          | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds).       |
+| `INVALID_URL`          | 10104 | The source URL does not point to a valid git repository.                  |
+| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication.                            |
+| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached.                               |
+| `MEMORY_LIMIT`         | 10402 | The operation exceeds service memory limits.                              |
+| `INTERNAL_ERROR`       | 10400 | An unexpected internal error occurred.                                    |
diff --git a/src/content/docs/artifacts/api/git-protocol.mdx b/src/content/docs/artifacts/api/git-protocol.mdx
index 0b2fe497d2755c8..df3348a7a33e084 100644
--- a/src/content/docs/artifacts/api/git-protocol.mdx
+++ b/src/content/docs/artifacts/api/git-protocol.mdx
@@ -20,10 +20,10 @@ Use the returned repo `remote` with a regular Git client for `clone`, `fetch`, `
 
 Git routes accept repo access tokens in two forms:
 
-| Format                             | Details                                                                                                                               | Example                                                                                                      |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| Format                             | Details                                                                                                                              | Example                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
 | Bearer token in `http.extraHeader` | Recommended for local workflows. Use the full token string returned by the control plane and keep credentials out of the remote URL. | `git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone` |
-| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`               |
+| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`                  |
 
 ### Token format
 
diff --git a/src/content/docs/artifacts/concepts/repositories.mdx b/src/content/docs/artifacts/concepts/repositories.mdx
index 026597faaae63d4..c00cad8531dd358 100644
--- a/src/content/docs/artifacts/concepts/repositories.mdx
+++ b/src/content/docs/artifacts/concepts/repositories.mdx
@@ -30,11 +30,11 @@ Each repository is isolated from other repositories. Tokens, lifecycle, refs, an
 
 Artifacts exposes the same repository through three interfaces:
 
-| Interface | What you use it for | What it returns |
-| --- | --- | --- |
-| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker | Repository metadata, repository handles, and repo-scoped token results |
-| REST API | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results |
-| Git protocol | Clone, fetch, pull, and push repository contents | Standard Git behavior over HTTPS |
+| Interface       | What you use it for                                                                | What it returns                                                        |
+| --------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
+| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker         | Repository metadata, repository handles, and repo-scoped token results |
+| REST API        | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results    |
+| Git protocol    | Clone, fetch, pull, and push repository contents                                   | Standard Git behavior over HTTPS                                       |
 
 These interfaces point to the same repository.
 
diff --git a/src/content/docs/artifacts/examples/git-client.mdx b/src/content/docs/artifacts/examples/git-client.mdx
index a297d94fb81bf26..10a023272838435 100644
--- a/src/content/docs/artifacts/examples/git-client.mdx
+++ b/src/content/docs/artifacts/examples/git-client.mdx
@@ -11,10 +11,11 @@ products:
 You can use a standard Git client to interact with Artifacts repos. This example walks through clone, but the same approach works for fetch, pull, push, and any other Git operation.
 
 To do this, you need to:
+
 - Fetch the repo's remote URL from the REST API
 - Mint a short-lived token scoped to that repo
 
-Once you have the remote URL and token, you can use them to run Git commands against the repo. 
+Once you have the remote URL and token, you can use them to run Git commands against the repo.
 
 This example assumes the repo already exists and that you have a [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 
@@ -49,11 +50,13 @@ ARTIFACTS_TOKEN=$(printf '%s' "$TOKEN_JSON" | jq -r '.result.plaintext')
 # Clone the repo
 git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone
 ```
+
 You now have a standard Git checkout in `./artifacts-clone`.
 
 This flow is useful when another system owns repo discovery or access control, but your local tooling still expects a normal git remote.
 
 ### Authentication
+
 Treat `ARTIFACTS_TOKEN` as a secret. Keep it out of logs, and prefer `http.extraHeader` over saving credentials in a remote URL.
 
 If you need a self-contained remote URL for a short-lived workflow, extract the token secret and build the authenticated remote only for that command:
diff --git a/src/content/docs/artifacts/guides/authentication.mdx b/src/content/docs/artifacts/guides/authentication.mdx
index ac4559e2184b237..b700afb4e8e3481 100644
--- a/src/content/docs/artifacts/guides/authentication.mdx
+++ b/src/content/docs/artifacts/guides/authentication.mdx
@@ -16,11 +16,11 @@ Review [Namespaces](/artifacts/concepts/namespaces/) first, then use one namespa
 
 ## Compare auth methods
 
-| Interface | Authenticate with | Permissions or scopes | Use for |
-| --- | --- | --- | --- |
-| Workers binding | Configured `artifacts` binding | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`. | Worker code that calls `env.ARTIFACTS` |
-| REST API | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests |
-| Git protocol | Repo-scoped Artifacts token | `read` for clone, fetch, and pull. `write` for push. | Standard Git over HTTPS |
+| Interface       | Authenticate with                                   | Permissions or scopes                                                                   | Use for                                |
+| --------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------- |
+| Workers binding | Configured `artifacts` binding                      | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`.           | Worker code that calls `env.ARTIFACTS` |
+| REST API        | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests            |
+| Git protocol    | Repo-scoped Artifacts token                         | `read` for clone, fetch, and pull. `write` for push.                                    | Standard Git over HTTPS                |
 
 Cloudflare API tokens authenticate control-plane access. Repo-scoped Artifacts tokens authenticate Git access.
 
@@ -79,10 +79,10 @@ curl --request POST "$ARTIFACTS_BASE_URL/repos" \
 
 Git uses repo-scoped Artifacts tokens, not Cloudflare API tokens. Mint these tokens from the Workers binding or the REST API, then use them with the repo `remote` URL.
 
-| Token scope | Allowed commands |
-| --- | --- |
-| `read` | `git clone`, `git fetch`, `git pull` |
-| `write` | `git clone`, `git fetch`, `git pull`, `git push` |
+| Token scope | Allowed commands                                 |
+| ----------- | ------------------------------------------------ |
+| `read`      | `git clone`, `git fetch`, `git pull`             |
+| `write`     | `git clone`, `git fetch`, `git pull`, `git push` |
 
 Use the exact repo `remote` value returned by the Workers binding or REST API:
 
diff --git a/src/content/docs/artifacts/guides/event-subscriptions.mdx b/src/content/docs/artifacts/guides/event-subscriptions.mdx
index 8b1184706241f3d..08ff7f6771fca2b 100644
--- a/src/content/docs/artifacts/guides/event-subscriptions.mdx
+++ b/src/content/docs/artifacts/guides/event-subscriptions.mdx
@@ -13,6 +13,7 @@ import { Render } from "~/components";
 Artifacts emits structured events for repository lifecycle changes — creates, deletes, forks, imports, pushes, clones, fetches, and token changes. By subscribing to these events through [event subscriptions](/queues/event-subscriptions/), you can consume them from a Worker to build commit-driven automation.
 
 For example:
+
 - Run custom workflows when a repository is created or imported
 - Kick off a build and deploy a change when an agent pushes to a repo
 - Trigger a review agent on every push
diff --git a/src/content/docs/artifacts/platform/limits.mdx b/src/content/docs/artifacts/platform/limits.mdx
index 75154c57881d70c..b328482a34c0687 100644
--- a/src/content/docs/artifacts/platform/limits.mdx
+++ b/src/content/docs/artifacts/platform/limits.mdx
@@ -15,9 +15,9 @@ These limits cover naming rules, storage, and request rates for control-plane an
 | Feature                        | Limit                                                                                              |
 | ------------------------------ | -------------------------------------------------------------------------------------------------- |
 | Control-plane request rate     | 2,000 requests per 10 seconds per Artifacts namespace                                              |
-| Git request rate, per artifact     | 2,000 requests per 10 seconds per artifact                                                             |
+| Git request rate, per artifact | 2,000 requests per 10 seconds per artifact                                                         |
 | Maximum storage per repository | 10 GB                                                                                              |
 | Maximum storage per account    | 1 TB (can be raised on request)                                                                    |
-| Maximum number of repositories | Unlimited                                 |
+| Maximum number of repositories | Unlimited                                                                                          |
 | Maximum number of namespaces   | Unlimited                                                                                          |
 | Namespace and repo names       | Start with a letter or digit. Remaining characters may include letters, digits, `.`, `_`, and `-`. |
diff --git a/src/content/docs/artifacts/platform/pricing.mdx b/src/content/docs/artifacts/platform/pricing.mdx
index 8cca99c4745119f..6986d8c6160294c 100644
--- a/src/content/docs/artifacts/platform/pricing.mdx
+++ b/src/content/docs/artifacts/platform/pricing.mdx
@@ -15,10 +15,10 @@ Artifacts pricing is billed on two dimensions:
 
 ## Artifacts pricing
 
-| Unit                          | Workers Free | Workers Paid |
-| ----------------------------- | ------------ | ------------ |
-| Operations (1,000 operations) | Unavailable | First 10,000 per month + $0.15 per additional 1,000 operations |
-| Storage (GB-mo)               | Unavailable | First 1 GB per month + $0.50 per additional GB-mo |
+| Unit                          | Workers Free | Workers Paid                                                   |
+| ----------------------------- | ------------ | -------------------------------------------------------------- |
+| Operations (1,000 operations) | Unavailable  | First 10,000 per month + $0.15 per additional 1,000 operations |
+| Storage (GB-mo)               | Unavailable  | First 1 GB per month + $0.50 per additional GB-mo              |
 
 ## Storage usage
 
diff --git a/src/content/docs/automatic-platform-optimization/about/index.mdx b/src/content/docs/automatic-platform-optimization/about/index.mdx
index 8a627ee1adac90b..8e08942f6c504ec 100644
--- a/src/content/docs/automatic-platform-optimization/about/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/index.mdx
@@ -6,7 +6,6 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 2
-
 ---
 
 With Automatic Platform Optimization (APO), Cloudflare serves your entire site from our edge network, ensuring customers see improved performance when visiting your site. Cloudflare typically only caches static content, but with APO, we can also cache dynamic content — like HTML — to serve the entire site from the cache. This process removes round trips from the origin to drastically improve time to first byte (TTFB) along with other site performance metrics. In addition to caching dynamic content, APO caches third-party scripts to further reduce the number of requests that leave Cloudflare's edge network.
diff --git a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
index 3b36da43020bcd5..c63c3dc4fdccb0f 100644
--- a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
@@ -16,35 +16,33 @@ For questions about a specific plugin not shown in the list, create a thread in
 
 :::note
 
-
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
-
 :::
 
 ## Compatible plugins
 
-* [NitroPack](https://nitropack.io/)
-* [FlyingPress](https://flyingpress.com/)
-* [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
-* [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
-* [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
-* [WooCommerce](https://wordpress.org/plugins/woocommerce/)
-* [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
-* [Object Cache Pro](https://objectcache.pro)
-* [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
-* [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
-* [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
-* [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
-* [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
-* [WPTouch](https://wordpress.org/plugins/wptouch/)
-* [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
-* [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
-* [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
-* [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
-* [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
-* [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
-* [WPML](https://wpml.org/)
-* [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
-* [Imunify360](https://docs.imunify360.com/features/#webshield)
-* [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
+- [NitroPack](https://nitropack.io/)
+- [FlyingPress](https://flyingpress.com/)
+- [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
+- [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
+- [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
+- [WooCommerce](https://wordpress.org/plugins/woocommerce/)
+- [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
+- [Object Cache Pro](https://objectcache.pro)
+- [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
+- [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
+- [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
+- [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
+- [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
+- [WPTouch](https://wordpress.org/plugins/wptouch/)
+- [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
+- [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
+- [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
+- [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
+- [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
+- [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
+- [WPML](https://wpml.org/)
+- [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
+- [Imunify360](https://docs.imunify360.com/features/#webshield)
+- [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
diff --git a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
index 05c85a5ea866629..e4df722b4bb5ebb 100644
--- a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
@@ -6,7 +6,6 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 3
-
 ---
 
 Before you begin using APO, we recommend testing your current site speed. Your site speed results give your website a letter grade and performance rating.
diff --git a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
index e2ba71bfc3a0ea6..422ecb4f5989b1b 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
@@ -33,8 +33,6 @@ We recommend keeping this browser tab or window open and opening a new tab or wi
 
 :::note
 
-
 You may be prompted to confirm the nameserver change with your domain registrar. Confirm or continue after making the update.
 
-
 :::
diff --git a/src/content/docs/automatic-platform-optimization/get-started/index.mdx b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
index 27e95e4ce57100a..1ec49c17ce68232 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with APO
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Before you configure APO for your WordPress site, complete the following tasks.
 
diff --git a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
index a8148c2c7bbb2e6..710c8af46eb1aa8 100644
--- a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
@@ -12,9 +12,9 @@ sidebar:
 
 APO cache by device type provides all of the same benefits of Cloudflare's cache while targeting visitors with content appropriate to their device. Cloudflare evaluates the `User-Agent` header in the HTTP request to identify the device type. Cloudflare then identifies each device type with a case insensitive match to the regex below:
 
-* **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
-* **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
-* **Desktop**: Everything else not matched above.
+- **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
+- **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
+- **Desktop**: Everything else not matched above.
 
 To enable caching by device type, enable the setting from the Cloudflare dashboard's APO card or from the WordPress plugin version 4.4.0 or later.
 
@@ -22,10 +22,8 @@ Once enabled, Cloudflare sends a `CF-Device-Type` HTTP header to your origin wit
 
 :::note
 
-
 Changing Cache By Device Type setting will invalidate Cache.
 
-
 :::
 
 The Cloudflare for WordPress plugin automatically purges all cache variations for updated pages.
diff --git a/src/content/docs/automatic-platform-optimization/reference/index.mdx b/src/content/docs/automatic-platform-optimization/reference/index.mdx
index d3e472301ede3ee..14a92784439d41f 100644
--- a/src/content/docs/automatic-platform-optimization/reference/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/index.mdx
@@ -6,9 +6,8 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
index 80a3a268e1f1395..c1f33213a954200 100644
--- a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
@@ -6,21 +6,20 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 12
-
 ---
 
 The following Page Rules can control APO. Any changes to caching via Page Rules require purging the cache for the changes to take effect.
 
 :::caution
 
-Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability. 
+Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability.
 :::
 
-* **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
+- **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
 
-* **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
+- **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
 
-* **Cache Level: Cache Everything** — APO caches pages with all query strings.
+- **Cache Level: Cache Everything** — APO caches pages with all query strings.
 
   :::caution
 
@@ -28,10 +27,10 @@ Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO
 
   :::
 
-* **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
+- **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
 
-* **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
+- **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
 
-* **Browser Cache TTL** — APO applies custom Browser TTL.
+- **Browser Cache TTL** — APO applies custom Browser TTL.
 
-* `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
+- `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
diff --git a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
index d49a44137e07c34..4c26f989a9835bb 100644
--- a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
@@ -16,46 +16,46 @@ To add a query parameter to our allowlist, [create a post in the community](http
 
 APO serves cached content as long as the query parameters in the URL are one of the following:
 
-* `ref`
-* `utm_source`
-* `utm_medium`
-* `utm_campaign`
-* `utm_term`
-* `utm_content`
-* `utm_expid`
-* `fbclid`
-* `fb_action_ids`
-* `fb_action_types`
-* `fb_source`
-* `mc_cid`
-* `mc_eid`
-* `gclid`
-* `dclid`
-* `_ga`
-* `campaignid`
-* `adgroupid`
-* `_ke`
-* `cn-reloaded`
-* `age-verified`
-* `ao_noptimize`
-* `usqp`
-* `mkt_tok`
-* `epik`
-* `ck_subscriber_id`
+- `ref`
+- `utm_source`
+- `utm_medium`
+- `utm_campaign`
+- `utm_term`
+- `utm_content`
+- `utm_expid`
+- `fbclid`
+- `fb_action_ids`
+- `fb_action_types`
+- `fb_source`
+- `mc_cid`
+- `mc_eid`
+- `gclid`
+- `dclid`
+- `_ga`
+- `campaignid`
+- `adgroupid`
+- `_ke`
+- `cn-reloaded`
+- `age-verified`
+- `ao_noptimize`
+- `usqp`
+- `mkt_tok`
+- `epik`
+- `ck_subscriber_id`
 
 ## Cookies prefixes that always bypass cache
 
-* `wp-`
-* `wordpress`
-* `comment_`
-* `woocommerce_`
-* `xf_`
-* `edd_`
-* `jetpack`
-* `yith_wcwl_session_`
-* `yith_wrvp_`
-* `wpsc_`
-* `ecwid`
-* `ec_`
-* `bookly_`
-* `bookly`
+- `wp-`
+- `wordpress`
+- `comment_`
+- `woocommerce_`
+- `xf_`
+- `edd_`
+- `jetpack`
+- `yith_wcwl_session_`
+- `yith_wrvp_`
+- `wpsc_`
+- `ecwid`
+- `ec_`
+- `bookly_`
+- `bookly`
diff --git a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
index c3ac27a754ccf4a..c14b25e62e38c9f 100644
--- a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
@@ -46,10 +46,10 @@ export default {
 		const originalResponse = await fetch(request);
 
 		// Response properties are immutable. To change them, construct a new Response object.
-    const response = new Response(originalResponse.body, originalResponse);
+		const response = new Response(originalResponse.body, originalResponse);
 
-    // Response headers can be modified through the headers `set` method.
-    response.headers.set("cf-edge-cache", "no-cache");
+		// Response headers can be modified through the headers `set` method.
+		response.headers.set("cf-edge-cache", "no-cache");
 
 		return response;
 	},
diff --git a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
index 4f41ab6c0987264..f680125ba5c4689 100644
--- a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
@@ -6,28 +6,25 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 15
-
 ---
 
 ## WordPress plugin is undetected on Cloudflare dashboard
 
 The WordPress plugin may go undetected on your Cloudflare dashboard for a few reasons.
 
-* Versions older than 3.8.2 of the WordPress plugin are installed.
-  * **Solution:** Install version 4.4.0 of the WordPress plugin.
-* Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
-  * **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
-* WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
-  * **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
+- Versions older than 3.8.2 of the WordPress plugin are installed.
+  - **Solution:** Install version 4.4.0 of the WordPress plugin.
+- Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
+  - **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
+- WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
+  - **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
 
 If your Cloudflare dashboard cannot detect the WordPress plugin after trying the solutions above, ensure you completed all of the steps listed in [Activate the Cloudflare WordPress plugin](/automatic-platform-optimization/get-started/activate-cf-wp-plugin/).
 
 :::note
 
-
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
-
 :::
 
 ## WordPress returns stale content
diff --git a/src/content/docs/billing/get-started/create-billing-profile.mdx b/src/content/docs/billing/get-started/create-billing-profile.mdx
index db1ff0eccc710d9..278be4c84fffc13 100644
--- a/src/content/docs/billing/get-started/create-billing-profile.mdx
+++ b/src/content/docs/billing/get-started/create-billing-profile.mdx
@@ -20,7 +20,7 @@ Customers on an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/co
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**. If no payment method is on file, the dialog opens automatically.
@@ -57,7 +57,7 @@ Optionally, add an additional payment method. Cloudflare automatically retries t
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**.
diff --git a/src/content/docs/billing/get-started/update-billing-info.mdx b/src/content/docs/billing/get-started/update-billing-info.mdx
index 103bc694b8df894..14d3c82fae104fa 100644
--- a/src/content/docs/billing/get-started/update-billing-info.mdx
+++ b/src/content/docs/billing/get-started/update-billing-info.mdx
@@ -20,7 +20,7 @@ If Cloudflare is unable to process your payment, review [Troubleshooting failed
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method** to add a new method, or **Edit** next to an existing one.
@@ -55,7 +55,7 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Delete** next to the payment method you want to remove.
@@ -65,9 +65,9 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 Two address fields exist on your account:
 
-| Field | Where it is used |
-| --- | --- |
-| **Billing profile address** | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening. |
+| Field                              | Where it is used                                                                                                       |
+| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| **Billing profile address**        | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening.                             |
 | **Payment method billing address** | Captured when you add a payment method. Used by the card issuer to authorize each charge. Does not appear on invoices. |
 
 Updating the billing profile address applies to invoices issued after the change. Past invoices keep the address that was on file when they were issued. Updating the billing profile address does not change the address stored on existing payment methods.
@@ -76,7 +76,7 @@ To update the billing profile address:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit** and enter your information.
 3. Review the suggested address in the pop-up window. If the information is correct, select **Confirm**.
@@ -91,7 +91,7 @@ Your billing email address is particularly important if you have [opted into ema
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to **Invoices and documents**.
 3. From **Billing email preference**, select **Change email address**.
@@ -101,13 +101,13 @@ Your billing email address is particularly important if you have [opted into ema
 
 If you added a payment method but did not include a Tax ID, VAT or GST number, you can add or change the Tax ID, VAT or GST number associated with the payment method afterwards.
 
-:::note 
+:::note
 You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, enter your VAT or GST number.
@@ -115,13 +115,13 @@ You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST numbe
 
 ## Remove a Tax ID, VAT, or GST number
 
-:::note 
+:::note
 You cannot remove a VAT or GST number from past invoices. Removing a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, delete the VAT or GST number.
diff --git a/src/content/docs/billing/manage/billable-usage.mdx b/src/content/docs/billing/manage/billable-usage.mdx
index 936144271be0638..3136309de54ce9b 100644
--- a/src/content/docs/billing/manage/billable-usage.mdx
+++ b/src/content/docs/billing/manage/billable-usage.mdx
@@ -40,12 +40,12 @@ Hover over any bar to see the per-product cost breakdown for that day.
 
 Below the chart, a sortable table breaks down usage by product for the full billing period.
 
-| Column | Description |
-| --- | --- |
-| **Product** | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
-| **Total usage** | Total metered usage for the billing period, including any free-tier allowance. |
-| **Billable usage** | Usage that exceeds the free tier and will be charged. |
-| **Usage cost** | Cumulative cost for the product in the selected billing period. |
+| Column             | Description                                                                                                                                              |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Product**        | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
+| **Total usage**    | Total metered usage for the billing period, including any free-tier allowance.                                                                           |
+| **Billable usage** | Usage that exceeds the free tier and will be charged.                                                                                                    |
+| **Usage cost**     | Cumulative cost for the product in the selected billing period.                                                                                          |
 
 Use the **product filter** at the top of the page to narrow the chart and table to specific products.
 
@@ -62,8 +62,6 @@ The dashboard reads from the same data source that generates your monthly invoic
 - Costs reflect the published rate card for your account.
 - The total usage cost shown at the end of a completed billing period matches the usage overage charges on the corresponding invoice.
 
-
-
 ## Set up budget alerts
 
 To get notified when your spend crosses a dollar threshold, you can create budget alerts directly from the dashboard. For detailed instructions, refer to [Budget alerts](/billing/manage/budget-alerts/).
@@ -73,4 +71,3 @@ To get notified when your spend crosses a dollar threshold, you can create budge
 - [Budget alerts](/billing/manage/budget-alerts/) — Get notified when spend crosses a threshold
 - [Usage-based billing](/billing/understand/usage-based-billing/) — Which products use metered billing
 - [How charges accrue](/billing/understand/how-charges-accrue/) — How a request generates charges across products
-
diff --git a/src/content/docs/billing/manage/budget-alerts.mdx b/src/content/docs/billing/manage/budget-alerts.mdx
index 0fb4fdd9330e059..c5cf2ff7f15fc1c 100644
--- a/src/content/docs/billing/manage/budget-alerts.mdx
+++ b/src/content/docs/billing/manage/budget-alerts.mdx
@@ -28,12 +28,12 @@ Budget alerts are available to Pay-as-you-go accounts only. Enterprise contract
 5. Select **Create budget alert**.
 6. Configure the alert:
 
-   | Field | Description |
-   | --- | --- |
-   | **Alert name** | A descriptive name for the alert (for example, "R2 spend warning"). |
-   | **Description** | *(Optional)* A note about when this alert should fire. |
+   | Field                      | Description                                                                                                                                                           |
+   | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | **Alert name**             | A descriptive name for the alert (for example, "R2 spend warning").                                                                                                   |
+   | **Description**            | _(Optional)_ A note about when this alert should fire.                                                                                                                |
    | **Budget threshold (USD)** | The dollar amount that triggers the alert. When your cumulative usage-based spend for the current billing period crosses this value, Cloudflare sends a notification. |
-   | **Email recipients** | One or more email addresses to notify. Select **Add email** to add additional recipients. |
+   | **Email recipients**       | One or more email addresses to notify. Select **Add email** to add additional recipients.                                                                             |
 
 7. Select **Save**.
 
@@ -54,12 +54,12 @@ From there you can edit or delete existing alerts.
 
 Cloudflare offers two types of spend monitoring:
 
-| Feature | Budget alerts | Usage notifications |
-| --- | --- | --- |
-| **Scope** | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
-| **Threshold** | Dollar amount | Product-specific metric (bytes, requests, minutes) |
-| **Setup location** | **Billing** > **Billable Usage** | **Notifications** |
-| **Best for** | Overall cost management | Monitoring a single product |
+| Feature            | Budget alerts                                   | Usage notifications                                       |
+| ------------------ | ----------------------------------------------- | --------------------------------------------------------- |
+| **Scope**          | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
+| **Threshold**      | Dollar amount                                   | Product-specific metric (bytes, requests, minutes)        |
+| **Setup location** | **Billing** > **Billable Usage**                | **Notifications**                                         |
+| **Best for**       | Overall cost management                         | Monitoring a single product                               |
 
 For per-product usage notifications, refer to [Usage-based billing](/billing/understand/usage-based-billing/#usage-based-billing-notifications).
 
diff --git a/src/content/docs/billing/manage/cancel-subscription.mdx b/src/content/docs/billing/manage/cancel-subscription.mdx
index c80dba8a8bcf6e3..5fdf55b5596082d 100644
--- a/src/content/docs/billing/manage/cancel-subscription.mdx
+++ b/src/content/docs/billing/manage/cancel-subscription.mdx
@@ -32,17 +32,17 @@ To disable a subscription:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Select the feature you want to disable under **Active Subscriptions** (Free or Pro customers) or **Plan Extensions** (Enterprise customers).
-4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing *Disable* from a drop-down list.
+4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing _Disable_ from a drop-down list.
 
 ## Step 2: Cancel the subscription in your billing profile
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Find the subscription you want to disable and select **Cancel**.
diff --git a/src/content/docs/billing/manage/invoices.mdx b/src/content/docs/billing/manage/invoices.mdx
index ba940ef55e961bd..43d7879767a806f 100644
--- a/src/content/docs/billing/manage/invoices.mdx
+++ b/src/content/docs/billing/manage/invoices.mdx
@@ -12,10 +12,10 @@ import { DashButton } from "~/components";
 
 You will receive an invoice in the **Billing** section of your Cloudflare account when you:
 
-* Change your Cloudflare plan type.
-* Upgrade or downgrade to or from a paid plan.
-* Add a new domain to a Cloudflare account.
-* Enable or renew a subscription or add-on service.
+- Change your Cloudflare plan type.
+- Upgrade or downgrade to or from a paid plan.
+- Add a new domain to a Cloudflare account.
+- Enable or renew a subscription or add-on service.
 
 For any historical invoices not included in the **Billing** section, [contact Cloudflare support](/support/contacting-cloudflare-support/).
 
@@ -29,25 +29,25 @@ To enable Cloudflare invoice emails which are sent when you add or remove subscr
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
-    
-3. Select **Invoices & Documents**.
-4. From **Billing email preferences**, toggle the notification switch to **On**.
+   <DashButton url="/?to=/:account/billing" />
+
+2. Select **Invoices & Documents**.
+3. From **Billing email preferences**, toggle the notification switch to **On**.
 
 After you enable email invoices, you will receive invoices via email:
 
-* Within one business day of initial set-up.
-* Every month at the end of your billing period.
-* Within one business day for all new purchases.
+- Within one business day of initial set-up.
+- Every month at the end of your billing period.
+- Within one business day for all new purchases.
 
 ## Download invoice
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices & Documents**.
-4. Find the invoice you want to download and select the icon next to the invoice number.
+3. Find the invoice you want to download and select the icon next to the invoice number.
 
 :::note
 Invoices cannot be regenerated after they are issued. Any pending billing updates or changes will appear in the next month's invoice.
diff --git a/src/content/docs/billing/manage/optimize-costs.mdx b/src/content/docs/billing/manage/optimize-costs.mdx
index 1ebb06ae5ce6d13..f4d34d4f201f6a3 100644
--- a/src/content/docs/billing/manage/optimize-costs.mdx
+++ b/src/content/docs/billing/manage/optimize-costs.mdx
@@ -10,10 +10,10 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 ## General strategies
 
-| Strategy | Impact |
-|---|---|
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | Prevents surprise invoices across all products |
-| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives |
+| Strategy                                                                                              | Impact                                                      |
+| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early               | Prevents surprise invoices across all products              |
+| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives            |
 | Understand [how charges accrue](/billing/understand/how-charges-accrue/) across the request lifecycle | Identifies which stage of a request generates the most cost |
 
 ## Per-product optimization
@@ -22,42 +22,42 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 Cached responses are the cheapest path through Cloudflare. Every cache hit avoids origin fetch costs, Argo routing charges, and Workers execution.
 
-| Strategy | What it reduces |
-|---|---|
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
+| Strategy                                                                                                              | What it reduces                                                              |
+| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                                     | Argo data transfer, Workers invocations, origin load                         |
 | Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content that is accessed infrequently | Origin fetches — keeps content cached even when it would normally be evicted |
-| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls | Origin bandwidth and Argo transfer between Cloudflare data centers |
-| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default | Overall cache hit ratio |
+| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls                                              | Origin bandwidth and Argo transfer between Cloudflare data centers           |
+| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default                           | Overall cache hit ratio                                                      |
 
 ### Workers & Durable Objects
 
-| Strategy | What it reduces |
-|---|---|
-| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush | Logpush-enabled Workers requests and Logpush data transfer |
+| Strategy                                                                                                                                                                       | What it reduces                                                                 |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
+| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush                                                                             | Logpush-enabled Workers requests and Logpush data transfer                      |
 | Use the [WebSocket Hibernation API](/durable-objects/best-practices/websockets/#durable-objects-hibernation-websocket-api) for Durable Objects with idle WebSocket connections | Duration (GB-s) charges — billing pauses while the Durable Object is hibernated |
 
 ### R2
 
-| Strategy | What it reduces |
-|---|---|
-| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data |
-| Batch R2 operations where possible instead of per-object reads | Class B operation count |
-| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers | Workers invocations and CPU time |
-| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache | Class B reads — cached objects do not hit R2 |
+| Strategy                                                                                                                | What it reduces                              |
+| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
+| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data              |
+| Batch R2 operations where possible instead of per-object reads                                                          | Class B operation count                      |
+| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers           | Workers invocations and CPU time             |
+| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache            | Class B reads — cached objects do not hit R2 |
 
 ### Stream and Images
 
-| Strategy | What it reduces |
-|---|---|
-| Set appropriate cache headers on Stream embed pages | Repeated Stream delivery minutes |
+| Strategy                                                                                                                           | What it reduces                                  |
+| ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
+| Set appropriate cache headers on Stream embed pages                                                                                | Repeated Stream delivery minutes                 |
 | Use [Image Resizing URL format](/images/optimization/features/) with width/height parameters to serve appropriately sized variants | Transformation count — sized variants are cached |
 
 ### Load Balancing
 
-| Strategy | What it reduces |
-|---|---|
+| Strategy                                                                                      | What it reduces                        |
+| --------------------------------------------------------------------------------------------- | -------------------------------------- |
 | Set health check intervals to the longest acceptable value for your availability requirements | DNS queries to load-balanced hostnames |
-| Use fewer health check regions where regional redundancy is not critical | Health check frequency multiplier |
+| Use fewer health check regions where regional redundancy is not critical                      | Health check frequency multiplier      |
 
 ## Monitor and alert
 
diff --git a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
index 2b082f37ba9f84f..e55450f95a43eb4 100644
--- a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
+++ b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
@@ -12,7 +12,6 @@ import { DashButton } from "~/components";
 
 If automatic payment retries fail and you do not pay manually, your account accrues an overdue balance. While the balance is unpaid, you cannot purchase products, upgrade subscriptions, or update your billing profile. Attempts to do so return an error:
 
-
 **"You cannot add or modify subscriptions or services until the outstanding balance is paid."**
 
 To pay, select **Pay Now** from the **Billing** page in the Cloudflare dashboard. You can pay the entire balance in one transaction or [pay individual invoices](#manually-pay-invoices) separately.
@@ -23,7 +22,7 @@ When an outstanding balance is due, a new invoice will be created in your accoun
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select the most recent invoice - the amount shown should match your outstanding balance
@@ -40,7 +39,7 @@ To pay the total outstanding balance:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Pay overdue balances** section.
 3. Select **Pay now** next to the balance you want to pay.
@@ -53,7 +52,7 @@ If an automatic subscription renewal payment fails, Cloudflare automatically ret
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select **Pay now** next to the invoice you want to pay.
diff --git a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
index f4e3aa40ed248b0..181362bc0ffcd63 100644
--- a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
+++ b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
@@ -33,9 +33,9 @@ Instant Bank Payments via Link is available to US-based self-serve accounts acro
 
 Bank-based Link payments appear in your billing history with these identifiers:
 
-| Field | Value |
-| --- | --- |
-| Payment method | `link` |
+| Field            | Value  |
+| ---------------- | ------ |
+| Payment method   | `link` |
 | Last four digits | `0000` |
 
 Card-based Link payments display your card's last four digits, distinguishing them from bank payments.
diff --git a/src/content/docs/billing/threshold-billing.mdx b/src/content/docs/billing/threshold-billing.mdx
index 0c72335ac0c6b0a..856ef82e55f97e7 100644
--- a/src/content/docs/billing/threshold-billing.mdx
+++ b/src/content/docs/billing/threshold-billing.mdx
@@ -27,11 +27,11 @@ You will never be double-charged. The threshold invoice and end-of-cycle invoice
 
 ### Example
 
-| Event | Charge |
-| --- | --- |
-| Combined usage reaches threshold mid-cycle | Threshold invoice charged (for example, $127.50) |
+| Event                                       | Charge                                             |
+| ------------------------------------------- | -------------------------------------------------- |
+| Combined usage reaches threshold mid-cycle  | Threshold invoice charged (for example, $127.50)   |
 | End of billing cycle (total usage was $180) | End-of-cycle invoice charged (for example, $52.50) |
-| **Total charged** | **$180** |
+| **Total charged**                           | **$180**                                           |
 
 ## Products subject to threshold billing
 
diff --git a/src/content/docs/billing/troubleshoot/error-reference.mdx b/src/content/docs/billing/troubleshoot/error-reference.mdx
index e2fbd524b5852d0..ea345499f66f805 100644
--- a/src/content/docs/billing/troubleshoot/error-reference.mdx
+++ b/src/content/docs/billing/troubleshoot/error-reference.mdx
@@ -12,21 +12,21 @@ Use the table below to find common billing error messages, understand what they
 
 ## Error messages
 
-| Error message | Cause | Solution |
-|---|---|---|
-| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/). |
-| "The payment has failed. Please contact your bank or use a different payment method." | Your payment method was declined by your bank. | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
-| "Payment error: authorization failed" | Your bank declined the transaction, or 3DS authentication was not completed. | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
-| "This zone cannot be upgraded" | The account or a previous owner of the domain has an outstanding balance. | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
-| "There is a problem with your billing profile" | Same as "this zone cannot be upgraded" — an unpaid balance exists. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours. |
-| "You cannot modify this subscription since it is currently scheduled to be cancelled" | You are trying to change a subscription that already has a pending cancellation. | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/). |
-| "You can't remove this payment method while it's linked to active subscriptions." | You are trying to delete a payment method that is still tied to paid services. | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
-| "You can't remove a payment method while there are transactions in progress." | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
+| Error message                                                                               | Cause                                                                                 | Solution                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance.                                                   | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/).                                                                                                               |
+| "The payment has failed. Please contact your bank or use a different payment method."       | Your payment method was declined by your bank.                                        | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                             |
+| "Payment error: authorization failed"                                                       | Your bank declined the transaction, or 3DS authentication was not completed.          | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                                          |
+| "This zone cannot be upgraded"                                                              | The account or a previous owner of the domain has an outstanding balance.             | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
+| "There is a problem with your billing profile"                                              | Same as "this zone cannot be upgraded" — an unpaid balance exists.                    | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours.                                                                                             |
+| "You cannot modify this subscription since it is currently scheduled to be cancelled"       | You are trying to change a subscription that already has a pending cancellation.      | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/).     |
+| "You can't remove this payment method while it's linked to active subscriptions."           | You are trying to delete a payment method that is still tied to paid services.        | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).    |
+| "You can't remove a payment method while there are transactions in progress."               | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).                       |
 
 ## Email notifications
 
-| Email subject | What it means | What to do |
-|---|---|---|
+| Email subject                              | What it means                                                                            | What to do                                                                                                                                                                      |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | "We couldn't process your renewal payment" | A recurring subscription charge failed. Cloudflare will retry up to 5 times over 5 days. | Update your payment method or manually pay the invoice before the grace period ends. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
 
 ## Still stuck?
diff --git a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
index 276892b5ec3390d..8cbc680da963f94 100644
--- a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
@@ -10,13 +10,14 @@ products:
 
 When attempting to remove a payment method, you may see one of the following error messages:
 
-* "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
-* "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
+- "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
+- "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
 
 ## Causes
-* You still have active paid subscriptions
-* You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
-* You have an upcoming Registrar domain registration renewal within the next 24 hours
+
+- You still have active paid subscriptions
+- You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
+- You have an upcoming Registrar domain registration renewal within the next 24 hours
 
 ## Solutions
 
@@ -36,19 +37,19 @@ Repeat this for all active paid subscriptions before attempting to remove the pa
 
 If you have cancelled all paid subscriptions, any usage-based products cancelled within the last 30 days may still generate charges. Your payment method must remain on file until those charges are processed. If you recently cancelled any of the following products, wait 30 days before removing your payment method:
 
-* Images
-* Stream
-* Workers
-* Argo
-* Spectrum
-* R2
-* Cache Reserve
-* Load Balancing
-* Rate Limiting
-* Log Explorer
-* Zero Trust
-* Vectorize
-* Analytics
+- Images
+- Stream
+- Workers
+- Argo
+- Spectrum
+- R2
+- Cache Reserve
+- Load Balancing
+- Rate Limiting
+- Log Explorer
+- Zero Trust
+- Vectorize
+- Analytics
 
 After the next monthly invoice is generated, you can remove the payment method.
 
diff --git a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
index b43d3e71c65fec6..eb388902186d5ac 100644
--- a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
@@ -10,16 +10,19 @@ products:
 
 When attempting to cancel or modify a subscription, you may see the following error message:
 
-* "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
+- "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
 
 ## Causes
-* You are attempting to cancel a subscription which you have already requested cancellation for
-* You are attempting to upgrade a subscription for which a cancellation is already scheduled
+
+- You are attempting to cancel a subscription which you have already requested cancellation for
+- You are attempting to upgrade a subscription for which a cancellation is already scheduled
 
 ## Solutions
+
 If you intended to cancel a subscription, the cancellation is already scheduled. Your subscription ends at the close of the current billing period. Refer to the section below to find the exact date.
 
 ### When will my subscription be cancelled?
+
 After requesting cancellation, the subscriptions page shows the end date under "Ending On".
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
@@ -31,6 +34,7 @@ After requesting cancellation, the subscriptions page shows the end date under "
 If you previously cancelled the subscription and have changed your decision, you need to cancel the downgrade.
 
 ### Can I receive a refund for my cancelled subscription?
+
 No refund will be issued for a cancelled subscription - instead, your subscription will remain active until the end of the current billing period.
 
 If you do not wish to pay for the coming billing period, then you should cancel your subscription no later than on the last day of the billing period. You can discover this date by visiting the **Subscriptions** page and checking the renew date, for example “RENEWS ON Aug 29, 2025”.
@@ -55,4 +59,4 @@ If the cancellation hasn’t taken effect yet, you can click **Cancel Downgrade*
 
 - [Cancel subscriptions](/billing/manage/cancel-subscription/) — How cancellations work
 - [Billing policy](/billing/understand/billing-policy/) — Refund policy and billing terms
-- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
\ No newline at end of file
+- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
diff --git a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
index aba89709e47d926..32e60e707eb83a6 100644
--- a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
+++ b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
@@ -34,4 +34,4 @@ You may have to wait up to one billing period for updates to appear in your Clou
 
 - [Invoices](/billing/manage/invoices/) — Download and manage invoices
 - [How Cloudflare billing works](/billing/understand/how-billing-works/) — How to read your invoice
-- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
\ No newline at end of file
+- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
diff --git a/src/content/docs/billing/understand/billing-permissions.mdx b/src/content/docs/billing/understand/billing-permissions.mdx
index f0a656bc1f33ea6..90f8f01686d0a1a 100644
--- a/src/content/docs/billing/understand/billing-permissions.mdx
+++ b/src/content/docs/billing/understand/billing-permissions.mdx
@@ -10,19 +10,19 @@ Access to billing features in the Cloudflare dashboard depends on the role assig
 
 ## Roles and billing capabilities
 
-| Action | Super Administrator | Administrator | Billing |
-|---|---|---|---|
-| View invoices and billing history | Yes | Yes | Yes |
-| Download invoice PDFs | Yes | Yes | Yes |
-| View billable usage dashboard | Yes | Yes | Yes |
-| Pay an outstanding balance | Yes | No | Yes |
-| Add or update payment methods | Yes | No | Yes |
-| Change billing address | Yes | No | Yes |
-| Change billing email | Yes | No | Yes |
-| Set up budget alerts | Yes | Yes | Yes |
-| Change or cancel subscriptions | Yes | Yes | No |
-| Upgrade or downgrade a domain plan | Yes | Yes | No |
-| Manage account members and roles | Yes | No | No |
+| Action                             | Super Administrator | Administrator | Billing |
+| ---------------------------------- | ------------------- | ------------- | ------- |
+| View invoices and billing history  | Yes                 | Yes           | Yes     |
+| Download invoice PDFs              | Yes                 | Yes           | Yes     |
+| View billable usage dashboard      | Yes                 | Yes           | Yes     |
+| Pay an outstanding balance         | Yes                 | No            | Yes     |
+| Add or update payment methods      | Yes                 | No            | Yes     |
+| Change billing address             | Yes                 | No            | Yes     |
+| Change billing email               | Yes                 | No            | Yes     |
+| Set up budget alerts               | Yes                 | Yes           | Yes     |
+| Change or cancel subscriptions     | Yes                 | Yes           | No      |
+| Upgrade or downgrade a domain plan | Yes                 | Yes           | No      |
+| Manage account members and roles   | Yes                 | No            | No      |
 
 :::note
 The Billing role can view and pay but cannot change subscriptions or plans. To both manage subscriptions and handle payments, a user needs the Super Administrator role.
diff --git a/src/content/docs/billing/understand/billing-policy.mdx b/src/content/docs/billing/understand/billing-policy.mdx
index 14a33c5e72ce247..b980bae02a464c9 100644
--- a/src/content/docs/billing/understand/billing-policy.mdx
+++ b/src/content/docs/billing/understand/billing-policy.mdx
@@ -81,15 +81,15 @@ Enterprise account owners receive invoices directly from the Cloudflare accounti
 
 Cloudflare accepts the following payment methods:
 
-* Visa
-* Mastercard
-* American Express
-* Discover
-* PayPal
-* Apple Pay
-* Google Pay
-* Stripe Link
-* UnionPay
+- Visa
+- Mastercard
+- American Express
+- Discover
+- PayPal
+- Apple Pay
+- Google Pay
+- Stripe Link
+- UnionPay
 
 :::note
 Enterprise customers can use ACH payments for Cloudflare plans and subscriptions.
diff --git a/src/content/docs/billing/understand/how-charges-accrue.mdx b/src/content/docs/billing/understand/how-charges-accrue.mdx
index 44a3bbcf2906350..d13bbe22d007ff3 100644
--- a/src/content/docs/billing/understand/how-charges-accrue.mdx
+++ b/src/content/docs/billing/understand/how-charges-accrue.mdx
@@ -26,17 +26,17 @@ Consider a visitor loading a page on a Pro domain that uses Workers, R2, Argo Sm
 
 The visitor's browser resolves the domain. This DNS query is handled by Cloudflare's authoritative DNS.
 
-| Resource | Billing impact |
-|---|---|
+| Resource    | Billing impact                                                                                                                                 |
+| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
 | DNS queries | Included in all plans at no extra charge. If you use Load Balancing, DNS queries to load-balanced hostnames are metered (first 500K included). |
 
 ### 2. Edge request and TLS
 
 The request arrives at the nearest Cloudflare data center. Cloudflare terminates TLS and processes the request.
 
-| Resource | Billing impact |
-|---|---|
-| TLS/SSL | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
+| Resource | Billing impact                                                                              |
+| -------- | ------------------------------------------------------------------------------------------- |
+| TLS/SSL  | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
 
 ### 3. Cache lookup
 
@@ -44,9 +44,9 @@ Cloudflare checks whether a cached response exists for this request.
 
 **Cache hit** — the response is served directly from the edge. No origin fetch occurs. This is the cheapest path.
 
-| Resource | Billing impact |
-|---|---|
-| Bandwidth | Included in all plans. Cloudflare does not charge for bandwidth. |
+| Resource            | Billing impact                                                                                                                                                                                      |
+| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bandwidth           | Included in all plans. Cloudflare does not charge for bandwidth.                                                                                                                                    |
 | Cache Reserve reads | If Cache Reserve is enabled and the asset is served from tiered cache storage, reads are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 **Cache miss** — the request must be forwarded to the origin. Continue to step 4.
@@ -55,53 +55,53 @@ Cloudflare checks whether a cached response exists for this request.
 
 If Argo is enabled, Cloudflare routes the request through the fastest path across its network to your origin.
 
-| Resource | Billing impact |
-|---|---|
+| Resource           | Billing impact                                                                                                                                             |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Argo data transfer | Metered per GB transferred between Cloudflare and your origin. First 1 GB included. Refer to [Argo Smart Routing](/argo-smart-routing/) for current rates. |
 
 ### 5. Workers execution (if configured)
 
 If a Worker is bound to the route, it executes before or instead of fetching from the origin.
 
-| Resource | Billing impact |
-|---|---|
-| Worker requests | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Worker CPU time | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates. |
+| Resource                | Billing impact                                                                                                                                    |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Worker requests         | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Worker CPU time         | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates.        |
+| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates.   |
 
 ### 6. Origin fetch and response
 
 If the Worker or cache miss triggers an origin fetch, Cloudflare retrieves the response from your origin server.
 
-| Resource | Billing impact |
-|---|---|
+| Resource  | Billing impact                                                                   |
+| --------- | -------------------------------------------------------------------------------- |
 | Bandwidth | No charge for data transfer between Cloudflare and your origin (no egress fees). |
 
 ### 7. R2 storage operations (if used)
 
 If the Worker or origin logic reads from or writes to R2, each operation is metered.
 
-| Resource | Billing impact |
-|---|---|
-| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 Class B operations (reads) | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 storage | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 data egress | Free. Cloudflare does not charge for R2 egress. |
+| Resource                       | Billing impact                                                                     |
+| ------------------------------ | ---------------------------------------------------------------------------------- |
+| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.   |
+| R2 Class B operations (reads)  | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.  |
+| R2 storage                     | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 data egress                 | Free. Cloudflare does not charge for R2 egress.                                    |
 
 ### 8. Cache write (miss path)
 
 After fetching from the origin, Cloudflare caches the response at the edge for future requests.
 
-| Resource | Billing impact |
-|---|---|
+| Resource             | Billing impact                                                                                                                                     |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cache Reserve writes | If Cache Reserve is enabled, writes are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 ### 9. Image Resizing (if configured)
 
 If the request triggers Image Resizing (via URL parameters or a Worker), the transformation is metered.
 
-| Resource | Billing impact |
-|---|---|
+| Resource              | Billing impact                                                                                                                       |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
 | Image transformations | First 50,000 included on the Business plan, then metered per request. Refer to [Images pricing](/images/pricing/) for current rates. |
 
 ### 10. Response delivered
@@ -116,15 +116,15 @@ The key takeaway: **cached responses are the cheapest path**. Every cache hit av
 
 ## Cost optimization strategies
 
-| Strategy | Products affected | Impact |
-|---|---|---|
-| Maximize cache hit ratio with appropriate Cache-Control headers | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs |
-| Use Cache Reserve for long-tail content | Cache, origin | Medium — reduces origin fetches for infrequently accessed content |
-| Set appropriate TTLs to avoid unnecessary revalidation | Cache, Argo | Medium — reduces origin round-trips |
-| Use Workers Smart Placement to run Workers closer to your data | Workers CPU time | Medium — reduces execution time for data-dependent Workers |
-| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage | Medium — reduces storage costs for archival data |
-| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/) | All usage-based products | High — visibility is the first step to optimization |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes | All usage-based products | High — prevents surprise invoices |
+| Strategy                                                                            | Products affected               | Impact                                                            |
+| ----------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------- |
+| Maximize cache hit ratio with appropriate Cache-Control headers                     | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs               |
+| Use Cache Reserve for long-tail content                                             | Cache, origin                   | Medium — reduces origin fetches for infrequently accessed content |
+| Set appropriate TTLs to avoid unnecessary revalidation                              | Cache, Argo                     | Medium — reduces origin round-trips                               |
+| Use Workers Smart Placement to run Workers closer to your data                      | Workers CPU time                | Medium — reduces execution time for data-dependent Workers        |
+| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage                      | Medium — reduces storage costs for archival data                  |
+| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/)  | All usage-based products        | High — visibility is the first step to optimization               |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes   | All usage-based products        | High — prevents surprise invoices                                 |
 
 ## Related resources
 
diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx
index 0be6d9d6118dc30..4b7d658484684f6 100644
--- a/src/content/docs/billing/understand/preview-services.mdx
+++ b/src/content/docs/billing/understand/preview-services.mdx
@@ -29,7 +29,7 @@ To enable a preview service, use the **Dashboard link** in the following table.
 | Load Balancing                     | [Load Balancing dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing)          | [Load Balancing docs](/load-balancing/)                                    | [Load Balancing community](https://community.cloudflare.com/tag/loadbalancing) |
 | Advanced Rate Limiting             | [Rate Limiting dashboard](https://dash.cloudflare.com/?to=/:account/:zone/security/waf/rate-limiting-rules) | [Rate Limiting docs](/waf/rate-limiting-rules/)                            | [Rate Limiting community](https://community.cloudflare.com/c/security/6)       |
 | Stream                             | [Stream dashboard](https://dash.cloudflare.com/?to=/:account/stream)                                        | [Stream docs](/stream/)                                                    | [Stream community](https://community.cloudflare.com/tag/cloudflarestream)      |
-| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)        | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
+| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)             | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
 | Web3                               | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3)                                      | [Web3 docs](/web3/)                                                        | [Web3 discord](https://discord.cloudflare.com)                                 |
 | Workers                            | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers)                                      | [Workers docs](/workers/)                                                  | [Workers discord](https://discord.com/invite/cloudflaredev)                    |
 | Zero Trust                         | [Zero Trust dashboard](https://one.dash.cloudflare.com/)                                                    | [Zero Trust docs](/cloudflare-one/)                                        | [Zero Trust community](https://community.cloudflare.com/c/security/access/51)  |
diff --git a/src/content/docs/billing/understand/usage-based-billing.mdx b/src/content/docs/billing/understand/usage-based-billing.mdx
index 2e7cc4c49963e48..c3270b67c1b766d 100644
--- a/src/content/docs/billing/understand/usage-based-billing.mdx
+++ b/src/content/docs/billing/understand/usage-based-billing.mdx
@@ -24,29 +24,29 @@ The following products bill based on consumption. Each product includes a free t
 
 For current overage rates, refer to the [Cloudflare plans page](https://www.cloudflare.com/plans/) or each product's pricing page linked below. Rates may change — the links below are always up to date.
 
-| Product | Billable metric | Free tier (included) | Pricing details |
-|---|---|---|---|
-| [Workers](/workers/platform/pricing/) | Requests, CPU time | 10M requests, 30M CPU-ms | [Workers pricing](/workers/platform/pricing/) |
-| [R2](/r2/pricing/) | Storage, operations | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/) |
-| [Argo Smart Routing](/argo-smart-routing/) | Data transfer (GB) | First 1 GB | [Argo pricing](/argo-smart-routing/) |
-| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage | None | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
-| [Load Balancing](/load-balancing/) | DNS queries | First 500K | [Load Balancing](/load-balancing/) |
-| [Stream](/stream/pricing/) | Minutes stored, minutes viewed | Varies by plan | [Stream pricing](/stream/pricing/) |
-| [Images](/images/pricing/) | Transformations, storage | Varies by plan | [Images pricing](/images/pricing/) |
-| [Spectrum](/spectrum/) | Data transfer (GB) | None | [Spectrum](/spectrum/) |
+| Product                                                       | Billable metric                | Free tier (included)                   | Pricing details                                                       |
+| ------------------------------------------------------------- | ------------------------------ | -------------------------------------- | --------------------------------------------------------------------- |
+| [Workers](/workers/platform/pricing/)                         | Requests, CPU time             | 10M requests, 30M CPU-ms               | [Workers pricing](/workers/platform/pricing/)                         |
+| [R2](/r2/pricing/)                                            | Storage, operations            | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/)                                            |
+| [Argo Smart Routing](/argo-smart-routing/)                    | Data transfer (GB)             | First 1 GB                             | [Argo pricing](/argo-smart-routing/)                                  |
+| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage         | None                                   | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
+| [Load Balancing](/load-balancing/)                            | DNS queries                    | First 500K                             | [Load Balancing](/load-balancing/)                                    |
+| [Stream](/stream/pricing/)                                    | Minutes stored, minutes viewed | Varies by plan                         | [Stream pricing](/stream/pricing/)                                    |
+| [Images](/images/pricing/)                                    | Transformations, storage       | Varies by plan                         | [Images pricing](/images/pricing/)                                    |
+| [Spectrum](/spectrum/)                                        | Data transfer (GB)             | None                                   | [Spectrum](/spectrum/)                                                |
 
 ## Optimize usage-based costs
 
 Reducing usage-based charges starts with understanding where your consumption comes from. Use the [billable usage dashboard](/billing/manage/billable-usage/) to identify which products are driving costs, then apply the strategies below.
 
-| Strategy | What it reduces |
-|---|---|
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
-| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content | Origin fetches for infrequently accessed assets |
-| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs |
-| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers | Workers CPU time |
-| Batch R2 operations where possible instead of per-object reads | R2 Class B operation count |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | All products — prevents surprise invoices |
+| Strategy                                                                                                 | What it reduces                                      |
+| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                        | Argo data transfer, Workers invocations, origin load |
+| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content                  | Origin fetches for infrequently accessed assets      |
+| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs                                     |
+| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers                  | Workers CPU time                                     |
+| Batch R2 operations where possible instead of per-object reads                                           | R2 Class B operation count                           |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early                  | All products — prevents surprise invoices            |
 
 For a detailed walkthrough of how a single request generates charges across multiple products, refer to [How charges accrue](/billing/understand/how-charges-accrue/).
 
diff --git a/src/content/docs/bots/account-abuse-protection.mdx b/src/content/docs/bots/account-abuse-protection.mdx
index ddd1362d953258a..e54a667206310fc 100644
--- a/src/content/docs/bots/account-abuse-protection.mdx
+++ b/src/content/docs/bots/account-abuse-protection.mdx
@@ -12,16 +12,15 @@ sidebar:
   badge:
     text: Early Access
     variant: note
-
 ---
 
-import { Render, Description, DashButton, Steps } from "~/components"
+import { Render, Description, DashButton, Steps } from "~/components";
 
 <Description>
-Identify and mitigate attacks on your customer and user accounts.
+	Identify and mitigate attacks on your customer and user accounts.
 </Description>
 
-Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems. 
+Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems.
 
 ## Availability
 
@@ -38,15 +37,15 @@ Contact your Cloudflare account team to request access.
 User ID is a cryptographically hashed, per-zone identifier that customers can use in [Security Analytics](/waf/analytics/security-analytics/), [Security Rules](/waf/custom-rules/), and [Managed Transforms](/rules/transform/managed-transforms/reference/). Hashed User IDs are created by encrypting the primary credentials your users provide, converting them into opaque identifiers unique to your zone. This allows traffic analysis while protecting user privacy. With access to hashed User ID, website owners can:
 
 - Review which users have the most activity on your website.
-- Find the details on a specific user's characteristics and activity patterns.  
-- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.  
-- Combine fields to see when accounts are being targeted with leaked credentials.  
+- Find the details on a specific user's characteristics and activity patterns.
+- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.
+- Combine fields to see when accounts are being targeted with leaked credentials.
 - Manage network patterns or signals associated with specific users.
 
 :::note[Data privacy]
-User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications. 
+User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications.
 
-Other Cloudflare customers cannot access your user profiles. They are unique to your zone. 
+Other Cloudflare customers cannot access your user profiles. They are unique to your zone.
 :::
 
 User ID is an opt-in feature that can be enabled in Security Settings.
@@ -65,13 +64,13 @@ To enable, edit, or disable the setting:
 
 ### Ephemeral IDs
 
-Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection. 
+Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection.
 
 Refer to [Fraud detection with ephemeral IDs](/turnstile/tutorials/fraud-detection-with-ephemeral-ids/) for more information.
 
 ### Account takeover detections
 
-Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks. 
+Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks.
 
 Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/) for more information.
 
@@ -85,25 +84,25 @@ Account takeover (ATO) detections are not available for accounts using the [Data
 
 ### Prerequisites
 
-Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior. 
+Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior.
 
 #### Security Settings
 
-- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections. 
+- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections.
 
-#### Eligible traffic 
+#### Eligible traffic
 
-Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations. 
+Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations.
 
 - Sign-ups: Cloudflare automatically monitors traffic on endpoints that match common sign up endpoints.
 - Login: Cloudflare automatically monitors traffic on endpoints that match common login endpoints.
 
 Verify that your endpoints are properly labeled to ensure Cloudflare can detect and monitor them correctly.
 
-<Render 
-  file="endpoint-label-warning" 
-  product="bots"
-  params={{ one: "or sign up" }} 
+<Render
+	file="endpoint-label-warning"
+	product="bots"
+	params={{ one: "or sign up" }}
 />
 
 :::tip[Enhanced with leaked credential detections]
@@ -114,43 +113,43 @@ Cloudflare also recommends enabling [Leaked credentials detection](/waf/detectio
 
 ### Detections
 
-Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints. 
+Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints.
 
 #### Account creation
 
-Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure. 
+Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure.
 
-You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email. 
+You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email.
 
 #### Suspicious emails
 
-Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections. 
+Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections.
 
-Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching. 
+Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching.
 
-| Detection tag | Description |
-| --- | --- |
-| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services. |
-| `cf.fraud.email_risk` | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
+| Detection tag                         | Description                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services.                                                                                                                                                                                                                                                                            |
+| `cf.fraud.email_risk`                 | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
 
---- 
+---
 
 ### Mitigations
 
-The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic. 
+The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic.
 
 #### Security Rules
 
 The following fields can be used in new and existing Security Rules.
 
-| Field | Description | Values |
-| --- | --- | --- |
-| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False` |
-| `cf.fraud.email_risk` | Measures risk of email based on randomness of characters in the username and domain. | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
+| Field                                  | Description                                                                                        | Values                                                                                                                                                                                                                                                              |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False`                                                                                                                                                                                                                                                   |
+| `cf.fraud.email_risk`                  | Measures risk of email based on randomness of characters in the username and domain.               | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
 
 #### Other rules
 
-You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin. 
+You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin.
 
 #### LogPush
 
@@ -160,12 +159,12 @@ You can add Fraud detection fields to existing or new [LogPush](/logs/logpush/)
 
 ## Analytics
 
-You can find Fraud data and detections in Security Analytics, where you can see top User IDs. 
+You can find Fraud data and detections in Security Analytics, where you can see top User IDs.
 
 <DashButton url="/?to=/:account/:zone/security/analytics" />
 
-Fraud fields can be used as filters to identify suspicious patterns in your traffic. 
+Fraud fields can be used as filters to identify suspicious patterns in your traffic.
 
-The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers. 
+The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers.
 
 A user level profile also provides a quick way to review the latest events associated with a user so that you can identify any anomalies and create a custom rule to log, block, or challenge that user.
diff --git a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
index 61260abf06b336f..b666e3479ba08d7 100644
--- a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
+++ b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
@@ -12,7 +12,7 @@ sidebar:
   label: Block AI Bots
 ---
 
-import { Render, Steps, DashButton } from "~/components"
+import { Render, Steps, DashButton } from "~/components";
 
 :::note[Block AI bots availability]
 The **Block AI bots** feature is only available in the new [application security dashboard](/security/).
@@ -35,4 +35,4 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
   5. Select **Save** to save your configuration.
 </Steps>
 
-To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
\ No newline at end of file
+To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
diff --git a/src/content/docs/bots/additional-configurations/custom-rules.mdx b/src/content/docs/bots/additional-configurations/custom-rules.mdx
index 287bace657d036c..fca74fa82b41d73 100644
--- a/src/content/docs/bots/additional-configurations/custom-rules.mdx
+++ b/src/content/docs/bots/additional-configurations/custom-rules.mdx
@@ -16,17 +16,17 @@ Bot protection on Cloudflare works through two complementary mechanisms: built-i
 
 The following features are configured through toggles and dropdowns in [Security Settings](/security/settings/). They do not require you to write any rule expressions.
 
-| Feature | What it does | Availability |
-| --- | --- | --- |
-| [Block AI bots](/bots/additional-configurations/block-ai-bots/) | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans |
-| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/) | Feeds non-compliant AI crawlers into a maze of generated content | All plans |
-| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/) | Prepends AI crawler disallow directives to your `robots.txt` | All plans |
-| Super Bot Fight Mode > **Definitely automated** | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1 | Pro, Business, Enterprise |
-| Super Bot Fight Mode > **Likely automated** | Blocks or challenges traffic with a bot score of 2-29 | Business, Enterprise |
-| [Verified bots](/bots/concepts/bot/verified-bots/) | Managed category of high-trust bots (Googlebot, Bingbot, and others) | Pro, Business, Enterprise |
-| [Static resource protection](/bots/additional-configurations/static-resources/) | Extends bot actions to cover static file types | Pro, Business, Enterprise |
-| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/) | Allows WordPress loopback requests through bot protection | Pro, Business, Enterprise |
-| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript | All plans (automatic on Free) |
+| Feature                                                                                | What it does                                                                                       | Availability                  |
+| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- |
+| [Block AI bots](/bots/additional-configurations/block-ai-bots/)                        | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans                     |
+| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/)                          | Feeds non-compliant AI crawlers into a maze of generated content                                   | All plans                     |
+| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/)              | Prepends AI crawler disallow directives to your `robots.txt`                                       | All plans                     |
+| Super Bot Fight Mode > **Definitely automated**                                        | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1                    | Pro, Business, Enterprise     |
+| Super Bot Fight Mode > **Likely automated**                                            | Blocks or challenges traffic with a bot score of 2-29                                              | Business, Enterprise          |
+| [Verified bots](/bots/concepts/bot/verified-bots/)                                     | Managed category of high-trust bots (Googlebot, Bingbot, and others)                               | Pro, Business, Enterprise     |
+| [Static resource protection](/bots/additional-configurations/static-resources/)        | Extends bot actions to cover static file types                                                     | Pro, Business, Enterprise     |
+| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/)              | Allows WordPress loopback requests through bot protection                                          | Pro, Business, Enterprise     |
+| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript                    | All plans (automatic on Free) |
 
 Bot settings update automatically as Cloudflare identifies new bot signatures and AI crawlers, while custom rules require manual updates. They do not count toward your [custom rule limits](/waf/custom-rules/#availability), and apply uniformly across your domain without the risk of expression errors.
 
diff --git a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
index ce92bacfafafb92..d36b1802e907d09 100644
--- a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
@@ -12,7 +12,6 @@ Cloudflare bot detection includes additional signals to catch different kinds of
 
 Bot management customers automatically benefit from the residential proxy detection improvement below, which lowers the [bot score](/bots/concepts/bot-score/) for matched requests. Using the detection ID in [custom rules](/waf/custom-rules/) provides even more visibility and control over mitigating residential proxy traffic.
 
-
-| <div style="width:100px">Detection ID</div> | Description                              |
-| ------------------------------------------ | ---------------------------------------- |
-| `50331651`                                 | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
+| <div style="width:100px">Detection ID</div> | Description                                                                                                                                                                                                                                                                               |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `50331651`                                  | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
diff --git a/src/content/docs/bots/additional-configurations/index.mdx b/src/content/docs/bots/additional-configurations/index.mdx
index 0768d508f998fd1..bc876caf734e5e0 100644
--- a/src/content/docs/bots/additional-configurations/index.mdx
+++ b/src/content/docs/bots/additional-configurations/index.mdx
@@ -11,11 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Additional Bots configurations
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on additional bot management configurations:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
index b575e485e4d47b1..f8af19b5b7de7b0 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 1
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 [**JA3**](https://github.com/salesforce/ja3) and [**JA4**](https://github.com/FoxIO-LLC/ja4) **fingerprints** identify TLS clients based on how they initiate connections. Each client type (browser, bot, or application) has distinct connection characteristics, so the resulting fingerprint acts as a stable identifier across different destination IPs, ports, and certificates.
 
@@ -17,64 +16,62 @@ JA4 improves on JA3 by sorting ClientHello extensions, which reduces the number
 
 :::note
 
-JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management. 
+JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management.
 :::
 
 <Render file="signals-intelligence-and-ja4" product="bots" />
 
 ```json
-
 {
-  "ja4Signals": {
-    "h2h3_ratio_1h": 0.98826485872269,
-    "heuristic_ratio_1h": 7.288895722013e-05,
-    "reqs_quantile_1h": 0.99905741214752,
-    "uas_rank_1h": 901,
-    "browser_ratio_1h": 0.93640440702438,
-    "paths_rank_1h": 655,
-    "reqs_rank_1h": 850,
-    "cache_ratio_1h": 0.18918327987194,
-    "ips_rank_1h": 662,
-    "ips_quantile_1h": 0.99926590919495
-  },
-  "jaSignalsParsed": {
-    "ratios": {
-      "h2h3_ratio_1h": 0.98826485872269,
-      "heuristic_ratio_1h": 7.288895722013e-05,
-      "browser_ratio_1h": 0.93640440702438,
-      "cache_ratio_1h": 0.18918327987194
-    },
-    "ranks": {
-      "uas_rank_1h": 901,
-      "paths_rank_1h": 655,
-      "reqs_rank_1h": 850,
-      "ips_rank_1h": 662
-    },
-    "quantiles": {
-      "reqs_quantile_1h": 0.99905741214752,
-      "ips_quantile_1h": 0.99926590919495
-    }
-  }
+	"ja4Signals": {
+		"h2h3_ratio_1h": 0.98826485872269,
+		"heuristic_ratio_1h": 7.288895722013e-5,
+		"reqs_quantile_1h": 0.99905741214752,
+		"uas_rank_1h": 901,
+		"browser_ratio_1h": 0.93640440702438,
+		"paths_rank_1h": 655,
+		"reqs_rank_1h": 850,
+		"cache_ratio_1h": 0.18918327987194,
+		"ips_rank_1h": 662,
+		"ips_quantile_1h": 0.99926590919495
+	},
+	"jaSignalsParsed": {
+		"ratios": {
+			"h2h3_ratio_1h": 0.98826485872269,
+			"heuristic_ratio_1h": 7.288895722013e-5,
+			"browser_ratio_1h": 0.93640440702438,
+			"cache_ratio_1h": 0.18918327987194
+		},
+		"ranks": {
+			"uas_rank_1h": 901,
+			"paths_rank_1h": 655,
+			"reqs_rank_1h": 850,
+			"ips_rank_1h": 662
+		},
+		"quantiles": {
+			"reqs_quantile_1h": 0.99905741214752,
+			"ips_quantile_1h": 0.99926590919495
+		}
+	}
 }
-
 ```
 
 When JA4 Signals are missing, the output appears as follows:
 
 ```json output title="Missing JA4 signals output"
 {
-  "ja4Signals": {},
-  "jaSignalsParsed": {
-    "ratios": {},
-    "ranks": {},
-    "quantiles": {}
-  }
+	"ja4Signals": {},
+	"jaSignalsParsed": {
+		"ratios": {},
+		"ranks": {},
+		"quantiles": {}
+	}
 }
 ```
 
 :::note
 
-This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/). 
+This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/).
 :::
 
 <Render file="ja3-ja4-null" product="bots" />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
index 2a86d9d70cbc989..23baf713cc11a7c 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Bot Management customers can view aggregate intelligence data for each [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/) based on traffic across the Cloudflare network. Use this data to understand why a request received a specific bot score or to feed into your own machine learning models running in [Cloudflare Workers](/workers/) or at your origin.
 
diff --git a/src/content/docs/bots/additional-configurations/javascript-detections.mdx b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
index 69e80bc8893eef4..e3c29b9383911ff 100644
--- a/src/content/docs/bots/additional-configurations/javascript-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
@@ -7,4 +7,4 @@ products:
 external_link: /cloudflare-challenges/challenge-types/javascript-detections/
 sidebar:
   order: 3
----
\ No newline at end of file
+---
diff --git a/src/content/docs/bots/concepts/bot-tags.mdx b/src/content/docs/bots/concepts/bot-tags.mdx
index ce7772981cc0afe..f498c1ebd7862df 100644
--- a/src/content/docs/bots/concepts/bot-tags.mdx
+++ b/src/content/docs/bots/concepts/bot-tags.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 3
-
 ---
 
-import { Render, GlossaryTooltip } from "~/components"
+import { Render, GlossaryTooltip } from "~/components";
 
 <GlossaryTooltip term="bot tags">Bot tags</GlossaryTooltip> provide more detail about *why* Cloudflare assigned a <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/">bot score</GlossaryTooltip> to a request.
 
diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx
index 79b102ed14105a3..8135d2506798f9c 100644
--- a/src/content/docs/bots/concepts/bot/index.mdx
+++ b/src/content/docs/bots/concepts/bot/index.mdx
@@ -29,7 +29,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni
 <Render file="verified-bots" product="bots" />
 
 :::note
-The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability). 
+The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability).
 :::
 
 ## AI bots
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
index 79b4ca637337d88..51b8af2d0e34705 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
@@ -9,7 +9,6 @@ sidebar:
 learning_center:
   title: What is a bot?
   link: https://www.cloudflare.com/learning/bots/what-is-a-bot/
-
 ---
 
 A signed agent is a bot controlled by an end user and verified through [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) cryptographic signatures.
@@ -33,4 +32,4 @@ Once Cloudflare approves a signed agent, it should appear on [Cloudflare Radar's
 
 ## Verification method
 
-The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
\ No newline at end of file
+The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
index 4b3a2e13bca22e5..7012c9a37f3a779 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
@@ -5,9 +5,8 @@ description: Requirements an agent must meet to be listed as a Cloudflare signed
 products:
   - bots
 sidebar:
-    order: 3
-    label: Policy
-
+  order: 3
+  label: Policy
 ---
 
 In order to be listed by Cloudflare as a signed agent, your agent must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
@@ -64,4 +63,4 @@ If any of the requirements to validate are breached, a service will be removed f
 The following are examples of breaches of policy:
 
 - The service has vulnerabilities that have not been patched.
-- The disclosed purpose of the service does not reflect on the traffic.
\ No newline at end of file
+- The disclosed purpose of the service does not reflect on the traffic.
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
index 0a353f6982931b7..35f535378a55bd9 100644
--- a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
@@ -5,12 +5,11 @@ description: Requirements a bot must meet to be listed as a Cloudflare verified
 products:
   - bots
 sidebar:
-    order: 5
-    label: Policy
-
+  order: 5
+  label: Policy
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
 
diff --git a/src/content/docs/bots/concepts/index.mdx b/src/content/docs/bots/concepts/index.mdx
index 24071d2b6d12abd..6c7d7f72e402af2 100644
--- a/src/content/docs/bots/concepts/index.mdx
+++ b/src/content/docs/bots/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on bot concepts:
 
diff --git a/src/content/docs/bots/get-started/index.mdx b/src/content/docs/bots/get-started/index.mdx
index 4082e3406e6058c..e3dd198f6f0fb99 100644
--- a/src/content/docs/bots/get-started/index.mdx
+++ b/src/content/docs/bots/get-started/index.mdx
@@ -12,10 +12,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with Cloudflare bot solutions
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to get started with Cloudflare's bot solutions based on your plan type:
 
diff --git a/src/content/docs/bots/glossary.mdx b/src/content/docs/bots/glossary.mdx
index 0fbbfcdccbc2f94..51cd6fdaf56a98f 100644
--- a/src/content/docs/bots/glossary.mdx
+++ b/src/content/docs/bots/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 10
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Bots documentation.
 
diff --git a/src/content/docs/bots/plans/bm-subscription.mdx b/src/content/docs/bots/plans/bm-subscription.mdx
index 3d5517526b98383..c0946617758e924 100644
--- a/src/content/docs/bots/plans/bm-subscription.mdx
+++ b/src/content/docs/bots/plans/bm-subscription.mdx
@@ -105,17 +105,17 @@ Zones that have [Enterprise Bot Management](/bots/get-started/bot-management/) e
 
 Bot Management customers have both bot settings (configured in **Security Settings**) and the ability to create custom rules using bot score fields. Start with the bot settings for baseline protection, then add custom rules only when you need additional control.
 
-| Feature | Handled by bot settings | When to use custom rules instead |
-| --- | --- | --- |
-| Block or challenge definitely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
-| Block or challenge likely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
-| Allow or block verified bots | No | Granular control by verified bot category |
-| Block AI crawlers | Yes | Target individual AI crawlers using detection IDs |
-| Protect static resources | No | Exclude static resources from specific rules |
-| Optimize for WordPress | No | No |
-| Forward bot data to origin | No | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/) |
-| Detection ID targeting | No | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/) |
-| JA3/JA4 fingerprint rules | No | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
+| Feature                                         | Handled by bot settings | When to use custom rules instead                                                                  |
+| ----------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
+| Block or challenge definitely automated traffic | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
+| Block or challenge likely automated traffic     | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
+| Allow or block verified bots                    | No                      | Granular control by verified bot category                                                         |
+| Block AI crawlers                               | Yes                     | Target individual AI crawlers using detection IDs                                                 |
+| Protect static resources                        | No                      | Exclude static resources from specific rules                                                      |
+| Optimize for WordPress                          | No                      | No                                                                                                |
+| Forward bot data to origin                      | No                      | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/)                          |
+| Detection ID targeting                          | No                      | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/)                       |
+| JA3/JA4 fingerprint rules                       | No                      | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
 
 For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
 
diff --git a/src/content/docs/bots/reference/alerts.mdx b/src/content/docs/bots/reference/alerts.mdx
index 76c74e5d486644c..039399e05dda310 100644
--- a/src/content/docs/bots/reference/alerts.mdx
+++ b/src/content/docs/bots/reference/alerts.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 4
-
 ---
 
-import { AvailableNotifications, Steps, DashButton } from "~/components"
+import { AvailableNotifications, Steps, DashButton } from "~/components";
 
 Bot alerts inform you when Cloudflare detects spikes in your traffic with any of the following characteristics:
 
@@ -17,7 +16,7 @@ Bot alerts inform you when Cloudflare detects spikes in your traffic with any of
 - An increase in traffic on available dimensions in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 - Filters of your choosing in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 
---- 
+---
 
 ## Alert types
 
@@ -73,5 +72,5 @@ You can also choose to group by the following dimensions so that they can be ale
 - Bot Detection IDs
 
 :::note
-Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/). 
-:::
\ No newline at end of file
+Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/).
+:::
diff --git a/src/content/docs/bots/reference/bot-management-variables.mdx b/src/content/docs/bots/reference/bot-management-variables.mdx
index 8b78f19b39ba24e..388e76e2a3c7d80 100644
--- a/src/content/docs/bots/reference/bot-management-variables.mdx
+++ b/src/content/docs/bots/reference/bot-management-variables.mdx
@@ -6,21 +6,21 @@ products:
   - bots
 sidebar:
   order: 2
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Ruleset Engine fields
 
 Bot Management provides access to several [new variables](/ruleset-engine/rules-language/fields/reference/?field-category=Bots) within the expression builder of Ruleset Engine-based products such as [WAF custom rules](/waf/custom-rules/).
 
 - **Bot Score** (`cf.bot_management.score`): An integer between 1-99 that indicates [Cloudflare's level of certainty](/bots/concepts/bot-score/) that a request comes from a bot.
-- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot. 
-  
-  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service. 
-  
+- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot.
+
+  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service.
+
   We also use additional validation methods, including checking ASN blocks and public lists. If these methods are unavailable, Cloudflare utilizes internal data and machine learning to identify and verify legitimate IP addresses from good bots. Most customers choose to [allow this traffic](/ruleset-engine/rules-language/fields/reference/cf.bot_management.verified_bot/).
+
 - **Serves Static Resource** (`cf.bot_management.static_resource`): An identifier that matches [file extensions](/bots/additional-configurations/static-resources/) for many types of static resources. Use this variable if you send emails that retrieve static images.
 - **ja3Hash** (`cf.bot_management.ja3_hash`) and **ja4** (`cf.bot_management.ja4`): A [**JA3/JA4 fingerprint**](/bots/additional-configurations/ja3-ja4-fingerprint/) helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
 - **Bot Detection IDs** (`cf.bot_management.detection_ids`): List of IDs that correlate to the Bot Management heuristic detections made on a request (you can have multiple heuristic detections on the same request).
diff --git a/src/content/docs/bots/reference/bot-verification/index.mdx b/src/content/docs/bots/reference/bot-verification/index.mdx
index c074fd2973d2c84..ea311232d0c71de 100644
--- a/src/content/docs/bots/reference/bot-verification/index.mdx
+++ b/src/content/docs/bots/reference/bot-verification/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 1
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's validation methods for [Verified](/bots/concepts/bot/verified-bots/) and [Signed](/bots/concepts/bot/signed-agents/) bots.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
index 9d65f3cb32d07cf..e21b0eabee315f3 100644
--- a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
+++ b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
@@ -5,12 +5,11 @@ description: Verify bot identity by matching request IP addresses against publis
 products:
   - bots
 sidebar:
-    order: 3
-    label: IP validation
-
+  order: 3
+  label: IP validation
 ---
 
-import { GlossaryTooltip, Steps } from "~/components"
+import { GlossaryTooltip, Steps } from "~/components";
 
 The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. IP validation is only used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/).
 
@@ -57,4 +56,4 @@ Generic user-agents include:
 - `node-fetch`
 - `okhttp`
 - `python-requests`
-- `uTorrent`
\ No newline at end of file
+- `uTorrent`
diff --git a/src/content/docs/bots/reference/index.mdx b/src/content/docs/bots/reference/index.mdx
index d98d7d7b81bce95..f157689e81141cc 100644
--- a/src/content/docs/bots/reference/index.mdx
+++ b/src/content/docs/bots/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's bot solutions:
 
diff --git a/src/content/docs/bots/reference/machine-learning-models.mdx b/src/content/docs/bots/reference/machine-learning-models.mdx
index 49af33d0da4309d..bdaac08a260b29c 100644
--- a/src/content/docs/bots/reference/machine-learning-models.mdx
+++ b/src/content/docs/bots/reference/machine-learning-models.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
 tags:
   - AI
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Enable auto-updates to the Machine Learning models
 
@@ -39,4 +38,4 @@ By not updating to the latest version, you will be using a Machine Learning mode
 | v6      | Significantly improved scoring for native Android application traffic. <br/><br/>Improved scoring on the newest versions of Chromium browsers.                                                                                              | Q1 2022     |
 | v7      | Increased recognition of distributed botnets. <br/><br/>Improved HTTP/3 scoring.                                                                                                                                                            | Q1 2024     |
 | v8      | Improved detection of residential proxies. <br/><br/>Increased weight on network level traffic characteristics.                                                                                                                             | Q2 2024     |
-| v9      | Improved model consistency and model efficacy against randomization attack techniques | Q2 2025     |
+| v9      | Improved model consistency and model efficacy against randomization attack techniques                                                                                                                                                       | Q2 2025     |
diff --git a/src/content/docs/bots/reference/sample-terms.mdx b/src/content/docs/bots/reference/sample-terms.mdx
index 3c05cc2e80dd3e8..2ba93ce64ee1935 100644
--- a/src/content/docs/bots/reference/sample-terms.mdx
+++ b/src/content/docs/bots/reference/sample-terms.mdx
@@ -8,7 +8,6 @@ sidebar:
   order: 5
 tags:
   - AI
-
 ---
 
 Cloudflare recommends that customers consider updating their Terms of Service to address bots specifically related to Artificial Intelligence (AI) training and data scraping. The text below provides an informational example of the kind of language that could be added to a website's terms of use.
@@ -19,8 +18,7 @@ Cloudflare recommends that customers consider updating their Terms of Service to
 
 :::caution[Disclaimer]
 
-This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome. 
+This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome.
 
-This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file. 
+This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file.
 :::
-
diff --git a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
index 363aa1c84d09636..b8453361111ca0c 100644
--- a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
+++ b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 1
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/additional-configurations/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
 
diff --git a/src/content/docs/bots/troubleshooting/false-positives.mdx b/src/content/docs/bots/troubleshooting/false-positives.mdx
index 377e7ac13199bff..7d7dadcae903c10 100644
--- a/src/content/docs/bots/troubleshooting/false-positives.mdx
+++ b/src/content/docs/bots/troubleshooting/false-positives.mdx
@@ -7,7 +7,6 @@ products:
 sidebar:
   order: 3
   label: False positives
-
 ---
 
 import { Render } from "~/components";
@@ -25,4 +24,4 @@ You cannot bypass or skip Bot Fight Mode using the _Skip_ action in WAF custom r
 
 Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.
 
-If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
\ No newline at end of file
+If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
diff --git a/src/content/docs/bots/troubleshooting/index.mdx b/src/content/docs/bots/troubleshooting/index.mdx
index b1e6d5b78a345c4..821d9ed42c52b76 100644
--- a/src/content/docs/bots/troubleshooting/index.mdx
+++ b/src/content/docs/bots/troubleshooting/index.mdx
@@ -12,12 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot issues with Bots
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to troubleshoot issues with Cloudflare's bot solutions:
 
 <DirectoryListing />
-
diff --git a/src/content/docs/bots/workers-templates/index.mdx b/src/content/docs/bots/workers-templates/index.mdx
index aae030a3a8b29b2..6bf57e8cbfb768f 100644
--- a/src/content/docs/bots/workers-templates/index.mdx
+++ b/src/content/docs/bots/workers-templates/index.mdx
@@ -12,10 +12,9 @@ sidebar:
 head:
   - tag: title
     content: Workers templates
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the templates below to integrate Bot Management with [Cloudflare Workers](/workers/):
 
diff --git a/src/content/docs/browser-run/features/index.mdx b/src/content/docs/browser-run/features/index.mdx
index 6ef34df2029deea..8f79040189134a4 100644
--- a/src/content/docs/browser-run/features/index.mdx
+++ b/src/content/docs/browser-run/features/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/browser-run/how-to/deploy-worker.mdx b/src/content/docs/browser-run/how-to/deploy-worker.mdx
index 808b712441c47df..d15deee8a1e1894 100644
--- a/src/content/docs/browser-run/how-to/deploy-worker.mdx
+++ b/src/content/docs/browser-run/how-to/deploy-worker.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 1
 products:
   - browser-run
-  - workers 
+  - workers
 ---
 
 import {
diff --git a/src/content/docs/browser-run/mcp-server.mdx b/src/content/docs/browser-run/mcp-server.mdx
index 3d7ba05eaeadd22..a79dc14dcabbbb1 100644
--- a/src/content/docs/browser-run/mcp-server.mdx
+++ b/src/content/docs/browser-run/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - browser-run
----
\ No newline at end of file
+---
diff --git a/src/content/docs/browser-run/quick-actions/api-reference.mdx b/src/content/docs/browser-run/quick-actions/api-reference.mdx
index 15e3e787ca1f282..dc44d9a5ba8d2e4 100644
--- a/src/content/docs/browser-run/quick-actions/api-reference.mdx
+++ b/src/content/docs/browser-run/quick-actions/api-reference.mdx
@@ -4,7 +4,7 @@ title: Reference
 description: View the complete Browser Run Quick Actions API reference for all available endpoints and parameters.
 external_link: /api/resources/browser_rendering/
 sidebar:
- order: 15
+  order: 15
 products:
   - browser-run
 ---
diff --git a/src/content/docs/browser-run/reference/browser-close-reasons.mdx b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
index 3fe11accbc5a78a..cfb411b73a356c1 100644
--- a/src/content/docs/browser-run/reference/browser-close-reasons.mdx
+++ b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
@@ -24,13 +24,13 @@ Browser Run sessions are billed based on [usage](/browser-run/pricing/). We do n
 
 ## Close reasons
 
-| Reason | Description |
-| --- | --- |
-| **Normal closure** | Your code called `browser.close()` and the session ended normally. No action needed. |
-| **Browser idle** | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
-| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks. |
-| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block. |
-| **Session evicted** | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic. |
+| Reason               | Description                                                                                                                                                                                                                                                                        |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Normal closure**   | Your code called `browser.close()` and the session ended normally. No action needed.                                                                                                                                                                                               |
+| **Browser idle**     | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
+| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks.                               |
+| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block.                                                    |
+| **Session evicted**  | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic.                                                                            |
 
 ## Handling unexpected closures
 
@@ -38,18 +38,18 @@ Sessions can close at any time due to infrastructure events, network issues, or
 
 ```js
 async function runBrowser(env) {
-  let browser;
-  try {
-    browser = await puppeteer.launch(env.MYBROWSER);
-    const page = await browser.newPage();
-    await page.goto("https://example.com");
-    // Your browser automation logic
-  } catch (error) {
-    console.error("Browser session ended unexpectedly:", error.message);
-    // Retry or return an error response
-  } finally {
-    await browser?.close();
-  }
+	let browser;
+	try {
+		browser = await puppeteer.launch(env.MYBROWSER);
+		const page = await browser.newPage();
+		await page.goto("https://example.com");
+		// Your browser automation logic
+	} catch (error) {
+		console.error("Browser session ended unexpectedly:", error.message);
+		// Retry or return an error response
+	} finally {
+		await browser?.close();
+	}
 }
 ```
 
@@ -57,13 +57,13 @@ For long-running or critical workflows, consider adding retry logic:
 
 ```js
 async function runWithRetry(env, maxRetries = 3) {
-  for (let attempt = 1; attempt <= maxRetries; attempt++) {
-    try {
-      return await runBrowser(env);
-    } catch (error) {
-      if (attempt === maxRetries) throw error;
-      console.log(`Attempt ${attempt} failed, retrying...`);
-    }
-  }
+	for (let attempt = 1; attempt <= maxRetries; attempt++) {
+		try {
+			return await runBrowser(env);
+		} catch (error) {
+			if (attempt === maxRetries) throw error;
+			console.log(`Attempt ${attempt} failed, retrying...`);
+		}
+	}
 }
 ```
diff --git a/src/content/docs/byoip/address-maps/setup.mdx b/src/content/docs/byoip/address-maps/setup.mdx
index 9e80f9aa794cc37..4ded8d833123a77 100644
--- a/src/content/docs/byoip/address-maps/setup.mdx
+++ b/src/content/docs/byoip/address-maps/setup.mdx
@@ -11,7 +11,13 @@ sidebar:
   label: Setup
 ---
 
-import { GlossaryTooltip, APIRequest, DashButton, Tabs, TabItem } from "~/components";
+import {
+	GlossaryTooltip,
+	APIRequest,
+	DashButton,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 Consider the sections below to learn how to set up address maps.
 
@@ -120,13 +126,13 @@ Default SNI for Spectrum can only be created via API using the [Create Address M
 Do not include any membership in your command. Your API command should resemble the following:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/address_maps"
-  method="POST"
-  json={{
-		"description": "default_sni",
-		"default_sni": "sni.example.com",
-		"enabled": false,
-		"ips": ["192.0.0.1"],
-		"memberships": [],
+	path="/accounts/{account_id}/addressing/address_maps"
+	method="POST"
+	json={{
+		description: "default_sni",
+		default_sni: "sni.example.com",
+		enabled: false,
+		ips: ["192.0.0.1"],
+		memberships: [],
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/byoip/changelog.mdx b/src/content/docs/byoip/changelog.mdx
index 389731c7bfc427f..bee100a7b07c3bc 100644
--- a/src/content/docs/byoip/changelog.mdx
+++ b/src/content/docs/byoip/changelog.mdx
@@ -14,4 +14,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/byoip.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductReleaseNotes />
\ No newline at end of file
+<ProductReleaseNotes />
diff --git a/src/content/docs/byoip/concepts/index.mdx b/src/content/docs/byoip/concepts/index.mdx
index 646653a0d44f0e6..7a7f4b5b8de1b6d 100644
--- a/src/content/docs/byoip/concepts/index.mdx
+++ b/src/content/docs/byoip/concepts/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the topics below for more information about concepts related to BYOIP.
 
diff --git a/src/content/docs/byoip/concepts/prefix-delegations.mdx b/src/content/docs/byoip/concepts/prefix-delegations.mdx
index 65ddd820ea83124..2c7fa214ed734aa 100644
--- a/src/content/docs/byoip/concepts/prefix-delegations.mdx
+++ b/src/content/docs/byoip/concepts/prefix-delegations.mdx
@@ -10,7 +10,6 @@ sidebar:
 
 Prefix delegations allow a prefix owner (Account A) to grant another Cloudflare account (Account B) permission to use all or part of their BYOIP prefix. The original prefix remains managed by Account A, but Account B can use the delegated IPs with CDN services (including Cloudflare for SaaS) or Spectrum. Refer to [service bindings](/byoip/service-bindings/) for more information on the services an IP can be bound to.
 
-
 ## CDN
 
 CDN delegations allow you to use the IP(s) with [Address Maps](/byoip/address-maps/) or [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) customers.
diff --git a/src/content/docs/byoip/glossary.mdx b/src/content/docs/byoip/glossary.mdx
index 8b3f72c3e98e200..21eb58070060e3a 100644
--- a/src/content/docs/byoip/glossary.mdx
+++ b/src/content/docs/byoip/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 12
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's BYOIP documentation.
 
diff --git a/src/content/docs/byoip/route-leak-detection.mdx b/src/content/docs/byoip/route-leak-detection.mdx
index 7b25fea18deee8c..b42d00458f0abed 100644
--- a/src/content/docs/byoip/route-leak-detection.mdx
+++ b/src/content/docs/byoip/route-leak-detection.mdx
@@ -6,10 +6,9 @@ products:
   - byoip
 sidebar:
   order: 8
-
 ---
 
-import { AvailableNotifications, DashButton } from "~/components"
+import { AvailableNotifications, DashButton } from "~/components";
 
 Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
 
diff --git a/src/content/docs/byoip/service-bindings/index.mdx b/src/content/docs/byoip/service-bindings/index.mdx
index 0078224d0428db2..51ae83d822bc673 100644
--- a/src/content/docs/byoip/service-bindings/index.mdx
+++ b/src/content/docs/byoip/service-bindings/index.mdx
@@ -79,4 +79,5 @@ When adding a service binding for a given IP address, it must be either a CDN se
 <DirectoryListing />
 
 [^1]: Layer 7 HTTP-based
-[^2]: Layer 4 or Layer 7 HTTP with custom ports
\ No newline at end of file
+
+[^2]: Layer 4 or Layer 7 HTTP with custom ports
diff --git a/src/content/docs/byoip/troubleshooting/index.mdx b/src/content/docs/byoip/troubleshooting/index.mdx
index c3c66603d15744f..b83821670151137 100644
--- a/src/content/docs/byoip/troubleshooting/index.mdx
+++ b/src/content/docs/byoip/troubleshooting/index.mdx
@@ -36,13 +36,12 @@ Instead, you can use Address Maps to set a default SNI for IPs on your account o
 
 When onboarding BYOIP prefixes via the API, you may encounter the following errors:
 
-| Error code | Meaning | Resolution |
-|---|---|---|
+| Error code                      | Meaning                                                                                                     | Resolution                                                                                                                                                                                                                                                                             |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `prefix_not_valid_and_approved` | The prefix has not passed IRR validation, RPKI validation, and ownership verification (or manual approval). | Verify all three validation steps have completed. If one or more are failing, check prefix registration with your Regional Internet Registry (RIR) and your RPKI ROA configuration. If validation is passing but you are still seeing this error, contact support for manual approval. |
-| `incomplete_bgp_deployment` | Cannot create a BGP prefix without a default edge service binding configured. | Configure a default edge service binding before creating BGP prefixes. |
-| `advertise_state_locked` | Cannot create a BGP prefix — the default edge service binding is still deploying. | Wait for the edge service binding deployment to complete, then retry. |
+| `incomplete_bgp_deployment`     | Cannot create a BGP prefix without a default edge service binding configured.                               | Configure a default edge service binding before creating BGP prefixes.                                                                                                                                                                                                                 |
+| `advertise_state_locked`        | Cannot create a BGP prefix — the default edge service binding is still deploying.                           | Wait for the edge service binding deployment to complete, then retry.                                                                                                                                                                                                                  |
 
 :::note
 Self-serve BYOIP onboarding is not supported when BYOIP is used as a Magic Transit on-ramp configuration. For more information, refer to [Magic Transit with CDN](/byoip/service-bindings/magic-transit-with-cdn/).
 :::
-
diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
index 5bd9e4060218ead..4e48745c1d36d41 100644
--- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
+++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
@@ -105,10 +105,7 @@ For example:
 
 ### Operations
 
-<Render
-  file="cache-reserve-operations"
-  product="cache"
-/>
+<Render file="cache-reserve-operations" product="cache" />
 
 ## Cache Reserve billing examples
 
@@ -152,10 +149,10 @@ Cache Reserve is designed for use with [Tiered Cache](/cache/how-to/tiered-cache
 ## Cache Reserve Analytics
 
 <Render
-  file="cache-reserve-analytics"
+	file="cache-reserve-analytics"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
diff --git a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
index 22a7ef8c9ba65a7..e94802d8e09921e 100644
--- a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
@@ -4,10 +4,9 @@ description: Signal search engine crawlers when content changes with IndexNow.
 products:
   - cache
 title: Crawler Hints
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Crawler Hints uses Cloudflare cache signals to tell search engines when your content has likely changed, so they crawl your site at the right time instead of guessing.
 
@@ -41,6 +40,6 @@ After enabling Crawler Hints, Cloudflare will begin sending hints to search engi
 
 When enabled, Crawler Hints is a global setting for your entire website. You can stop a specific page from being indexed by either:
 
-* Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
-* Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
-* Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
+- Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
+- Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
+- Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
diff --git a/src/content/docs/cache/advanced-configuration/early-hints.mdx b/src/content/docs/cache/advanced-configuration/early-hints.mdx
index 0dbc92752839ea9..cc491452932a8a8 100644
--- a/src/content/docs/cache/advanced-configuration/early-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/early-hints.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Preload assets with 103 Early Hints to speed up page loads.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 When a browser requests a page, the origin server takes time to prepare the full response. Early Hints uses this wait time to send the browser a preliminary `103` response containing `Link` headers that tell the browser which assets it will need. The browser can start loading those assets before the full response arrives, which speeds up page loads.
 
@@ -15,10 +14,8 @@ Early Hints is defined in [RFC 8297](https://httpwg.org/specs/rfc8297.html) as a
 
 :::note[Note]
 
-
 Early Hints is currently only supported over HTTP/2 and HTTP/3.
 
-
 :::
 
 For more information about Early Hints, refer to the [Cloudflare](https://blog.cloudflare.com/early-hints) and [Google Chrome](https://developer.chrome.com/en/blog/early-hints/) blogs.
@@ -40,16 +37,14 @@ For more information about Early Hints, refer to the [Cloudflare](https://blog.c
 
 Early Hints are only generated and cached:
 
-* For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
-* On 200, 301, or 302 response return codes
-* When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
+- For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
+- On 200, 301, or 302 response return codes
+- When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
 
 :::note
 
-
 Early Hints cache entries are keyed by request URI and ignore query strings.
 
-
 :::
 
 ## Emit Early Hints
@@ -60,7 +55,7 @@ Currently, only certain browser versions will take action to preload or preconne
 
 Additionally, keep the following in mind:
 
-* Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
-* Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
-* Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
-* You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
+- Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
+- Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
+- Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
+- You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
diff --git a/src/content/docs/cache/advanced-configuration/index.mdx b/src/content/docs/cache/advanced-configuration/index.mdx
index 9efd5cc15381ed7..12fa7c03f59e222 100644
--- a/src/content/docs/cache/advanced-configuration/index.mdx
+++ b/src/content/docs/cache/advanced-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
index 0b41b69eb776303..05e6363b11a6dad 100644
--- a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
+++ b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
@@ -9,14 +9,14 @@ tags:
   - WordPress
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 **Query String Sort** increases cache-hit rates by first sorting query strings into a consistent order before checking the Cloudflare cache.
 
 By default, Cloudflare’s cache treats resources as distinct if their URL query strings are in a different order. For instance, these resources are cached separately:
 
-* `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
-* `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
+- `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
+- `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
 
 Query String Sort changes this behavior. If two query strings exist with the same name, the URL is sorted by the parameter value. For example:
 
@@ -30,7 +30,7 @@ would be sorted to:
 
 <FeatureTable id="cache.query_string_sort" />
 
-***
+---
 
 ## Enable Query String Sort
 
@@ -41,7 +41,7 @@ To enable Query String Sort:
 3. Go to **Caching** > **Configuration**.
 4. For **Enable Query String Sort**, switch the toggle to **On**.
 
-***
+---
 
 ## Unexpected behavior with WordPress admin pages
 
@@ -49,19 +49,17 @@ When a site or an application requires exact query string ordering, enabling Que
 
 For example in the WordPress admin UI, you might notice any of the following behaviors:
 
-* No media appear in the Media Library
-* Inability to customize the site via **Appearance** > **Customize**
-* Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
-* Inability to edit menus in **Appearance** > **Menus**
+- No media appear in the Media Library
+- Inability to customize the site via **Appearance** > **Customize**
+- Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
+- Inability to edit menus in **Appearance** > **Menus**
 
 To understand why this happens, note that WordPress [concatenates JavaScript files](https://developer.wordpress.org/advanced-administration/wordpress/wp-config/#disable-javascript-concatenation) to speed up the administration interface. The way WordPress implements this involves multiple occurrences of `load[]` parameters in the query string, where the order of those parameters is crucial.
 
 :::note
 
-
 Note that more recent versions of WordPress may not experience this issue, as a patch has been implemented in WordPress since 2019. The patch can be found at [WordPress Core Trac Changeset 45456](https://core.trac.wordpress.org/changeset/45456).
 
-
 :::
 
 ### Identify the problem
@@ -100,15 +98,15 @@ For example, you might have an image resizing endpoint or a search form, where t
 
 To minimize problems, consider:
 
-* Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
-* Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
-* Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
+- Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
+- Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
+- Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
 
 To learn more about Cache Rules, visit [Cache Rules](/cache/how-to/cache-rules/).
 
-***
+---
 
 ## Related resources
 
-* [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
-* [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
+- [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
+- [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
diff --git a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
index 8d6b138d7f117d2..4f0f14a99828213 100644
--- a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
+++ b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
@@ -42,8 +42,8 @@ In this example, you run an e-commerce site and want to display prices in the lo
    - **Operator:** `equals`
    - **Value:** `Canada`
 6. Under **Then...**
-    - for **Path**, select **Preserve**.
-    - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
+   - for **Path**, select **Preserve**.
+   - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
 7. Select **Save**.
 
 Now, requests from Canada to `/products/item` will be transformed to `/products/item?loc=ca` before reaching your origin or the cache, creating a distinct cache entry.
@@ -65,14 +65,14 @@ To enable this feature, create a _variants rule_ using the API. This rule maps f
 For example, the following API call tells Cloudflare that for `.jpeg` and `.jpg` files, your origin can serve `image/webp` and `image/avif` variants:
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp", "image/avif"],
-      jpg: ["image/webp", "image/avif"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp", "image/avif"],
+			jpg: ["image/webp", "image/avif"],
+		},
+	}}
 />
 
 After creating the rule, Cloudflare will create distinct cache entries for each image variant, improving performance for users with modern browsers.
@@ -100,26 +100,27 @@ In this example, you run an A/B test controlled by a cookie named `ab-test` (wit
 const CACHE_DURATION = 30 * 24 * 60 * 60; // 30 days
 
 export default {
-  async fetch(request) {
-    // Construct a new URL for the cache key based on the A/B cookie
-    const abCookie = request.headers.get('Cookie')?.match(/ab-test=([^;]+)/)?.[1] || 'control';
-    const url = new URL(request.url);
-    url.pathname = `/ab-test/${abCookie}${url.pathname}`;
-
-    const cacheKey = new Request(url, request);
-    const cache = caches.default;
-
-    let response = await cache.match(cacheKey);
-    if (!response) {
-      // If not in cache, fetch from origin
-      response = await fetch(request);
-      response = new Response(response.body, response);
-      response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
-      // Put the response into cache with the custom key
-      await cache.put(cacheKey, response.clone());
-    }
-    return response;
-  },
+	async fetch(request) {
+		// Construct a new URL for the cache key based on the A/B cookie
+		const abCookie =
+			request.headers.get("Cookie")?.match(/ab-test=([^;]+)/)?.[1] || "control";
+		const url = new URL(request.url);
+		url.pathname = `/ab-test/${abCookie}${url.pathname}`;
+
+		const cacheKey = new Request(url, request);
+		const cache = caches.default;
+
+		let response = await cache.match(cacheKey);
+		if (!response) {
+			// If not in cache, fetch from origin
+			response = await fetch(request);
+			response = new Response(response.body, response);
+			response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
+			// Put the response into cache with the custom key
+			await cache.put(cacheKey, response.clone());
+		}
+		return response;
+	},
 };
 ```
 
@@ -151,13 +152,13 @@ If your origin serves different content types (for example, `application/json` v
    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
-3. Enter  rule name, such as `Vary by Accept Header`.
+3. Enter rule name, such as `Vary by Accept Header`.
 4. Set the condition for the rule to apply (for example, a specific hostname or path).
 5. Under **Cache key**, select **Use custom key**.
 6. Select **Add new**.
-    - **Type**: `Header`
-    - **Name**: `Accept`
-    - **Value**: Add each `value`, or leave empty for all.
+   - **Type**: `Header`
+   - **Name**: `Accept`
+   - **Value**: Add each `value`, or leave empty for all.
 7. Select **Deploy**.
 
 This configuration creates separate cache entries based on the `Accept` header value, respecting your API's content negotiation.
@@ -176,28 +177,28 @@ This Worker detects whether a visitor is on a mobile or desktop device and creat
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    const userAgent = request.headers.get('User-Agent') || '';
-    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
+	async fetch(request, env, ctx) {
+		const userAgent = request.headers.get("User-Agent") || "";
+		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
 
-    // Create a new URL for the cache key that includes the device type
-    const url = new URL(request.url);
-    url.pathname = `/${deviceType}${url.pathname}`;
+		// Create a new URL for the cache key that includes the device type
+		const url = new URL(request.url);
+		url.pathname = `/${deviceType}${url.pathname}`;
 
-    const cacheKey = new Request(url, request);
-    const cache = caches.default;
+		const cacheKey = new Request(url, request);
+		const cache = caches.default;
 
-    let response = await cache.match(cacheKey);
+		let response = await cache.match(cacheKey);
 
-    if (!response) {
-      console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
-      response = await fetch(request);
-      let responseToCache = response.clone();
-      ctx.waitUntil(cache.put(cacheKey, responseToCache));
-    }
+		if (!response) {
+			console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
+			response = await fetch(request);
+			let responseToCache = response.clone();
+			ctx.waitUntil(cache.put(cacheKey, responseToCache));
+		}
 
-    return response;
-  },
+		return response;
+	},
 };
 ```
 
@@ -211,28 +212,28 @@ This Worker detects if a visitor is on a mobile device or a desktop and creates
 
 ```js
 export default {
-  async fetch(request) {
-    // 1. Determine the device type from the User-Agent header
-    const userAgent = request.headers.get('User-Agent') || '';
-    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
-
-    // 2. Create a custom cache key by appending the device type to the URL
-    const customCacheKey = `${request.url}-${deviceType}`;
-
-    // 3. Fetch the response. Cloudflare's cache automatically uses the
-    //    customCacheKey for cache operations (match, put).
-    const response = await fetch(request, {
-      cf: {
-        cacheKey: customCacheKey,
-      },
-    });
-
-    // Optionally, you can modify the response before returning it
-    // For example, add a header to indicate which cache key was used
-    const newResponse = new Response(response.body, response);
-    newResponse.headers.set("X-Cache-Key", customCacheKey);
-    return newResponse;
-  },
+	async fetch(request) {
+		// 1. Determine the device type from the User-Agent header
+		const userAgent = request.headers.get("User-Agent") || "";
+		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
+
+		// 2. Create a custom cache key by appending the device type to the URL
+		const customCacheKey = `${request.url}-${deviceType}`;
+
+		// 3. Fetch the response. Cloudflare's cache automatically uses the
+		//    customCacheKey for cache operations (match, put).
+		const response = await fetch(request, {
+			cf: {
+				cacheKey: customCacheKey,
+			},
+		});
+
+		// Optionally, you can modify the response before returning it
+		// For example, add a header to indicate which cache key was used
+		const newResponse = new Response(response.body, response);
+		newResponse.headers.set("X-Cache-Key", customCacheKey);
+		return newResponse;
+	},
 };
 ```
 
@@ -256,11 +257,11 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 3. Enter a name, such as `Vary by RSC Header`.
 4. In **If incoming requests match**, select **Custom filter expression**.
 5. Under **When incoming requests match**, manually edit the expression so that it checks for the presence of the `RSC` header:
-    - `has_key(http.request.headers, "rsc")`
+   - `has_key(http.request.headers, "rsc")`
 
 6. Under **Then**:
-    - For **Path**, select **Preserve**.
-    - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
+   - For **Path**, select **Preserve**.
+   - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
 
 7. Select **Save**.
 
@@ -269,8 +270,7 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 Alternatively, use [Snippets](/rules/snippets/) or [Custom Cache Keys](/cache/how-to/cache-keys) to add the `RSC` header directly to the cache key without modifying the visible URL. This provides a cleaner URL but requires more advanced configuration.
 
 :::note[Availability]
+
 - Snippets: Pro, Business, Enterprise
 - Custom Cache Keys: Enterprise only
-:::
-
-
+  :::
diff --git a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
index ab7ed953aa09229..1209ddf6440e3ee 100644
--- a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
+++ b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Serve images in the best format for each visitor browser.
 products:
   - cache
-
 ---
 
-import { Details, FeatureTable, APIRequest } from "~/components"
+import { Details, FeatureTable, APIRequest } from "~/components";
 
 The `Vary` HTTP response header tells Cloudflare that an origin can serve different versions of the same resource depending on the request headers. For images, this allows your origin to serve modern formats like WebP or AVIF to browsers that support them, while continuing to serve JPEG or PNG to others.
 
@@ -25,20 +24,19 @@ Vary for images is available for Pro, Business, and Enterprise customers.
 
 You can use vary for images on the file extensions below if the origin server sends the `Vary: Accept` response header. If the origin server sends `Vary: Accept` but does not serve the set variant, the response is not cached and displays `BYPASS` in the cache status in the response header. Additionally, the list of variant types the origin serves for each extension must be configured so that Cloudflare decides which variant to serve without contacting the origin server.
 
-
 <Details header="File extensions enabled for varying">
-  <ul>
-    <li>.avif</li>
-    <li>.bmp</li>
-    <li>.gif</li>
-    <li>.jpg</li>
-    <li>.jpeg</li>
-    <li>.jp2</li>
-    <li>.png</li>
-    <li>.tif</li>
-    <li>.tiff</li>
-    <li>.webp</li>
-  </ul>
+	<ul>
+		<li>.avif</li>
+		<li>.bmp</li>
+		<li>.gif</li>
+		<li>.jpg</li>
+		<li>.jpeg</li>
+		<li>.jp2</li>
+		<li>.png</li>
+		<li>.tif</li>
+		<li>.tiff</li>
+		<li>.webp</li>
+	</ul>
 </Details>
 
 ## Enable vary for images
@@ -48,46 +46,40 @@ Vary for Images is enabled through Cloudflare's API by creating a variants rule.
 ### Create a variants rule
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp", "image/avif"],
-      jpg: ["image/webp", "image/avif"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp", "image/avif"],
+			jpg: ["image/webp", "image/avif"],
+		},
+	}}
 />
 
 ### Modify to only allow WebP variants
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp"],
-      jpg: ["image/webp"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp"],
+			jpg: ["image/webp"],
+		},
+	}}
 />
 
 ### Delete the rule
 
-<APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="DELETE"
-/>
+<APIRequest path="/zones/{zone_id}/cache/variants" method="DELETE" />
 
 ### Get the rule
 
-<APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="GET"
-/>
+<APIRequest path="/zones/{zone_id}/cache/variants" method="GET" />
 
 To learn more about purging varied images, refer to [Purge varied images](/cache/how-to/purge-cache/purge-varied-images/).
 
 ## Limitations
 
-* For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
-* Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
+- For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
+- Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
diff --git a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
index 3978e79c7e9bb20..f115a63a6b91c56 100644
--- a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
+++ b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
@@ -19,22 +19,22 @@ A Content Delivery Network (CDN) like Cloudflare relies on cache keys to compare
 
 To deepen your understanding of the risks and vulnerabilities associated with cache poisoning, consult the following resources:
 
-* [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
-* [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
+- [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
+- [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
 
 ## Only cache files that are truly static
 
 Review the caching configuration for your origin web server and ensure you are caching files that are static and do not depend on user input in any way. To learn more about Cloudflare caching, review:
 
-* [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
-* [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
+- [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
+- [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
 
 ## Do not trust data in HTTP headers
 
 Attackers can exploit HTTP headers to inject malicious content into cached responses. For example, if your application reflects an untrusted header value in the response body, an attacker could use this to perform cross-site scripting (XSS) through the cache. To reduce this risk:
 
-* Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
-* Do not include untrusted header values in your response body.
+- Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
+- Do not include untrusted header values in your response body.
 
 ## Do not trust GET request bodies
 
@@ -44,6 +44,6 @@ Cloudflare caches contents of GET request bodies, but they are not included in t
 
 To keep informed about Internet security threats, Cloudflare recommends that you monitor web security advisories on a regular basis. Some of the more popular advisories include:
 
-* [Drupal Security Advisories](https://www.drupal.org/security)
-* [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
-* [Laminas Security Advisories](https://getlaminas.org/security/advisories)
+- [Drupal Security Advisories](https://www.drupal.org/security)
+- [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
+- [Laminas Security Advisories](https://getlaminas.org/security/advisories)
diff --git a/src/content/docs/cache/cache-security/cache-deception-armor.mdx b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
index a008458a9255072..2b41dc71ac0ea52 100644
--- a/src/content/docs/cache/cache-security/cache-deception-armor.mdx
+++ b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
@@ -24,9 +24,9 @@ In the newsfeed example above, if `http://www.example.com/newsfeed` is a script
 
 ### Exceptions
 
-* If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
-* Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
-* Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
+- If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
+- Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
+- Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
 
 ## Enable Cache Deception Armor
 
diff --git a/src/content/docs/cache/cache-security/cors.mdx b/src/content/docs/cache/cache-security/cors.mdx
index 5f1e357e312c2fe..3f70fe69412f798 100644
--- a/src/content/docs/cache/cache-security/cors.mdx
+++ b/src/content/docs/cache/cache-security/cors.mdx
@@ -12,8 +12,8 @@ A cross-origin request occurs when a webpage on one origin (for example, `a.exam
 
 Cloudflare supports CORS by:
 
-* Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
-* Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
+- Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
+- Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
 
 The `Access-Control-Allow-Origin` header lets a server specify rules for sharing its resources with external origins. A server may respond with different `Access-Control-Allow-Origin` values depending on the `Origin` header in the request. These headers are often present on [cacheable content](/cache/concepts/default-cache-behavior/).
 
@@ -21,9 +21,9 @@ The `Access-Control-Allow-Origin` header lets a server specify rules for sharing
 
 If you add or change CORS configuration at your origin web server, purging the Cloudflare cache by URL does not update the CORS headers. Force Cloudflare to retrieve the new CORS headers via one of the following options:
 
-* Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
-* Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
-* Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
+- Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
+- Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
+- Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
 
 ## Add or change CORS headers on Cloudflare
 
@@ -32,4 +32,3 @@ You can use one of following methods to set CORS headers using Cloudflare produc
 - Use a [Worker](/workers/): Refer to [CORS header proxy](/workers/examples/cors-header-proxy/) for an example.
 - Configure a [Snippet](/rules/snippets/): Refer to [Define CORS headers](/rules/snippets/examples/define-cors-headers/) for an example.
 - Use [Transform Rules](/rules/transform/): Refer to [Add a wildcard CORS response header](/rules/transform/examples/add-cors-header/) for an example.
-
diff --git a/src/content/docs/cache/cache-security/index.mdx b/src/content/docs/cache/cache-security/index.mdx
index 6f753ca961b67d0..3287619c54fa92c 100644
--- a/src/content/docs/cache/cache-security/index.mdx
+++ b/src/content/docs/cache/cache-security/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following content to learn more about cache security.
 
diff --git a/src/content/docs/cache/concepts/cache-behavior.mdx b/src/content/docs/cache/concepts/cache-behavior.mdx
index 212cd5cec8fe30f..ca4b43ee981b90a 100644
--- a/src/content/docs/cache/concepts/cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/cache-behavior.mdx
@@ -11,8 +11,8 @@ tags:
 
 This page describes how Cloudflare's cache system behaves in interaction with:
 
-* `HEAD` requests
-* `Set-Cookie` response headers
+- `HEAD` requests
+- `Set-Cookie` response headers
 
 ## Interaction of `HEAD` requests with Cache
 
@@ -24,8 +24,8 @@ When you make a `HEAD` request for a cacheable resource and Cloudflare does not
 
 For non-cacheable requests, `Set-Cookie` is always preserved. For cacheable requests, there are three possible behaviors:
 
-* `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
+- `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
 
-* `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
+- `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
 
-* `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
+- `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
diff --git a/src/content/docs/cache/concepts/cache-responses.mdx b/src/content/docs/cache/concepts/cache-responses.mdx
index a1f3935e1f26ba9..20f1007625c6956 100644
--- a/src/content/docs/cache/concepts/cache-responses.mdx
+++ b/src/content/docs/cache/concepts/cache-responses.mdx
@@ -7,7 +7,6 @@ products:
 head:
   - tag: title
     content: Cloudflare cache responses
-
 ---
 
 The `CF-Cache-Status` header output indicates whether a resource is cached or not. To investigate cache responses returned by this header, use services like [Redbot](https://redbot.org/), [webpagetest.org](http://www.webpagetest.org/), or a visual tool like [Cloudflare Optics plugin](https://chromewebstore.google.com/detail/cloudflare-optics/mdjgbjnbdnhneejmmaabmccfehigbjbe).
@@ -32,13 +31,13 @@ The resource was not found in Cloudflare's cache and was served from the origin
 
 Cloudflare generated a response that denotes the asset is not eligible for caching. This may have happened because:
 
-* A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
+- A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
 
-* A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
+- A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
 
-* A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
+- A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
 
-* A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
+- A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
 
 ## EXPIRED
 
diff --git a/src/content/docs/cache/concepts/cdn-cache-control.mdx b/src/content/docs/cache/concepts/cdn-cache-control.mdx
index 81e86ba54273c84..ae3401ebbb3fa3b 100644
--- a/src/content/docs/cache/concepts/cdn-cache-control.mdx
+++ b/src/content/docs/cache/concepts/cdn-cache-control.mdx
@@ -18,11 +18,11 @@ If a [Cache Response Rule](/cache/how-to/cache-response-rules/) sets `Cache-Cont
 
 When no Cache Response Rule applies, an origin can:
 
-* Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
+- Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
 
-* Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
+- Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
 
-* Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
+- Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
 
 Additionally, surrogates will not honor `Cache-Control` headers in the response from an origin. For example, if the `Surrogate-Control` header is present within the response, Cloudflare ignores any `Cache-Control` directives, even if the `Surrogate-Control` header does not contain directives.
 
@@ -52,61 +52,61 @@ Use `CDN-Cache-Control` when you want to manage cached asset’s TTLs separately
 
 Headers:
 
-* `Cache-Control: max-age=14400, s-maxage=84000`
-* `Cloudflare-CDN-Cache-Control: max-age=24400`
-* `CDN-Cache-Control: max-age=18000`
+- `Cache-Control: max-age=14400, s-maxage=84000`
+- `Cloudflare-CDN-Cache-Control: max-age=24400`
+- `CDN-Cache-Control: max-age=18000`
 
 Cache behavior:
 
 <table>
-  <tbody>
-    <th colspan="5" rowspan="1">
-      Caches
-    </th>
-    <th colspan="5" rowspan="1">
-      Cache TTL (seconds)
-    </th>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Origin Server Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        14400
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Network Shared Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        84000
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Cloudflare Edge
-      </td>
-      <td colspan="5" rowspan="1">
-        24400
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Other CDNs
-      </td>
-      <td colspan="5" rowspan="1">
-        18000
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Browser Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        14400
-      </td>
-    </tr>
-  </tbody>
+	<tbody>
+		<th colspan="5" rowspan="1">
+			Caches
+		</th>
+		<th colspan="5" rowspan="1">
+			Cache TTL (seconds)
+		</th>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Origin Server Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				14400
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Network Shared Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				84000
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Cloudflare Edge
+			</td>
+			<td colspan="5" rowspan="1">
+				24400
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Other CDNs
+			</td>
+			<td colspan="5" rowspan="1">
+				18000
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Browser Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				14400
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ### Specify when to serve stale content
@@ -115,43 +115,43 @@ Use `CDN-Cache-Control` headers in conjunction with `Cache-Control` headers to s
 
 Headers:
 
-* `Cache-Control: stale-if-error=400`
-* `Cloudflare-CDN-Cache-Control: stale-if-error=60`
-* `CDN-Cache-Control: stale-if-error=200`
+- `Cache-Control: stale-if-error=400`
+- `Cloudflare-CDN-Cache-Control: stale-if-error=60`
+- `CDN-Cache-Control: stale-if-error=200`
 
 Behavior in response to [5XX error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/):
 
 <table>
-  <tbody>
-    <th colspan="5" rowspan="1">
-      Caches
-    </th>
-    <th colspan="5" rowspan="1">
-      Stale served (seconds) in response to error
-    </th>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Origin Cache Layer/Network Cache/Browser Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        400 (if it assumes the directive applies)
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Cloudflare Edge
-      </td>
-      <td colspan="5" rowspan="1">
-        60
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Other CDN
-      </td>
-      <td colspan="5" rowspan="1">
-        200
-      </td>
-    </tr>
-  </tbody>
+	<tbody>
+		<th colspan="5" rowspan="1">
+			Caches
+		</th>
+		<th colspan="5" rowspan="1">
+			Stale served (seconds) in response to error
+		</th>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Origin Cache Layer/Network Cache/Browser Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				400 (if it assumes the directive applies)
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Cloudflare Edge
+			</td>
+			<td colspan="5" rowspan="1">
+				60
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Other CDN
+			</td>
+			<td colspan="5" rowspan="1">
+				200
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/docs/cache/concepts/customize-cache.mdx b/src/content/docs/cache/concepts/customize-cache.mdx
index c4f49110ea13c65..1a9047525da3655 100644
--- a/src/content/docs/cache/concepts/customize-cache.mdx
+++ b/src/content/docs/cache/concepts/customize-cache.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: Methods for customizing cache behavior with rules, Workers, and headers.
 products:
   - cache
-
 ---
 
 Some possible combinations of origin web server settings and Cloudflare [Cache Rules](/cache/how-to/cache-rules/) include:
@@ -13,21 +12,21 @@ Some possible combinations of origin web server settings and Cloudflare [Cache R
 
 For example, create a `/static/` subdirectory at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
-* Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
+- Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
 
 ## Append a unique file extension to static pages
 
 For example, create a `.shtml` file extension for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
-* Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
+- Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
 
 ## Add a query string to a resource’s URL to mark the content as static
 
 For example, add a `static=true` query string for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
-* Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
+- Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
 
 Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a Cache-Control header of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.
diff --git a/src/content/docs/cache/concepts/default-cache-behavior.mdx b/src/content/docs/cache/concepts/default-cache-behavior.mdx
index 0f9a375df7316c6..6749f5b82907cf1 100644
--- a/src/content/docs/cache/concepts/default-cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/default-cache-behavior.mdx
@@ -7,20 +7,24 @@ products:
 head:
   - tag: title
     content: Default Cache Behavior
-
 ---
 
-import { FeatureTable, GlossaryTooltip, Render, DashButton } from "~/components"
+import {
+	FeatureTable,
+	GlossaryTooltip,
+	Render,
+	DashButton,
+} from "~/components";
 
 Cloudflare respects the origin web server’s cache headers in the following order unless an [Edge Cache TTL cache rule](/cache/how-to/cache-rules/settings/#edge-ttl) overrides the headers. Refer to the [Edge TTL](/cache/how-to/configure-cache-status-code/#edge-ttl) section for details on default TTL behavior.
 
-* Cloudflare **does not** cache the resource when:
-  * The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
-  * The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
-  * The HTTP request method is anything other than a `GET`.
-* Cloudflare **does** cache the resource when:
-  * The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
-  * The `Expires` header is set to a future date.
+- Cloudflare **does not** cache the resource when:
+  - The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
+  - The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
+  - The HTTP request method is anything other than a `GET`.
+- Cloudflare **does** cache the resource when:
+  - The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
+  - The `Expires` header is set to a future date.
 
 :::note
 Cloudflare does cache the resource even if there is no `Cache-Control` header based on [status codes](/cache/how-to/configure-cache-status-code/#edge-ttl).
@@ -36,8 +40,8 @@ When [Origin Cache Control](/cache/concepts/cache-control/) is enabled on an Ent
 
 Clients can send range requests to be served from the cache using the `Range` header. Note that:
 
- - If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
- - If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
+- If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
+- If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
 
 ## Request collapsing
 
@@ -64,10 +68,10 @@ Cloudflare only caches based on file extension and not by MIME type. The Cloudfl
 To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/) to create a rule to cache everything.
 
 <Render
-  file="edge-ttl"
+	file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
@@ -75,14 +79,14 @@ To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/)
 
 Cloudflare’s CDN provides several cache customization options:
 
-* Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
+- Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
 
- <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+<DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
-* Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
-* Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
+- Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
+- Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
 
- <DashButton url="/?to=/:account/:zone/caching/configuration" />
+<DashButton url="/?to=/:account/:zone/caching/configuration" />
 
 ### Upload limits
 
@@ -96,8 +100,8 @@ If you require a larger upload, you can group requests into smaller chunks, uplo
 
 Cloudflare cacheable file limits:
 
-* Free, Pro and Business customers have a limit of 512 MB.
-* For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
+- Free, Pro and Business customers have a limit of 512 MB.
+- For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
 
 ## When does Cloudflare cache successfully?
 
diff --git a/src/content/docs/cache/concepts/index.mdx b/src/content/docs/cache/concepts/index.mdx
index 9d7aa540158df71..c39bdbe713dbf77 100644
--- a/src/content/docs/cache/concepts/index.mdx
+++ b/src/content/docs/cache/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-    
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts and components of Cloudflare Cache.
 
diff --git a/src/content/docs/cache/concepts/retention-vs-freshness.mdx b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
index 1148870b16f91ca..86ee2ef5d7736c5 100644
--- a/src/content/docs/cache/concepts/retention-vs-freshness.mdx
+++ b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: How cache retention and TTL freshness differ in Cloudflare.
 products:
   - cache
-
 ---
 
 In the context of Cloudflare CDN (Content Delivery Network), retention and freshness refer to two separate but related concepts. For an object in cache, freshness is how long it should be considered valid without consulting its source, while retention refers to how long it stays in cache before being removed.
@@ -19,8 +18,8 @@ Cloudflare uses a Least Recently Used (LRU) algorithm to decide which objects to
 
 Freshness, also known as Time to Live (TTL), determines how long a cache can use an object without checking with the origin again. For example, if an object has a TTL of five minutes, the cache serves it directly for five minutes after first receiving it. After five minutes, Cloudflare must check with the origin to confirm the object is still valid before serving it again. There are a few ways to configure TTLs for resources served through Cloudflare's CDN:
 
-* Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
+- Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
 
-* Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
+- Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
 
 If an object in cache is no longer fresh, Cloudflare revalidates it with the origin. When [`stale-while-revalidate`](/cache/concepts/cache-control/#revalidation) is set, revalidation happens asynchronously at expiry — visitors continue to be served from cache while Cloudflare fetches a fresh copy in the background. Without this directive, incoming requests wait for the origin to respond before receiving content. The origin can either confirm the cached object is still valid (refreshing its TTL) or return a new version to replace it. Refer to [Revalidation](/cache/concepts/revalidation/) for details.
diff --git a/src/content/docs/cache/concepts/revalidation.mdx b/src/content/docs/cache/concepts/revalidation.mdx
index be6792de1f48057..f289dc2c55c0ce6 100644
--- a/src/content/docs/cache/concepts/revalidation.mdx
+++ b/src/content/docs/cache/concepts/revalidation.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: How Cloudflare revalidates stale cached content with your origin.
 products:
   - cache
-
 ---
 
 ## Stale-while-revalidate
diff --git a/src/content/docs/cache/get-started.mdx b/src/content/docs/cache/get-started.mdx
index ab1be9257230ee3..485414c218db17e 100644
--- a/src/content/docs/cache/get-started.mdx
+++ b/src/content/docs/cache/get-started.mdx
@@ -13,7 +13,7 @@ head:
     content: Get started with Cache
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare speeds up your website by caching content across globally distributed data centers.
 
@@ -21,12 +21,12 @@ Content can be static or dynamic. Static content — such as images, CSS, and Ja
 
 Cloudflare caches static content based on the following factors:
 
-* [Caching levels](/cache/how-to/set-caching-levels/)
-* [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
-* Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
-* [Origin cache-control headers](/cache/concepts/cache-control/)
-* Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
-* Cache rules that bypass cache on cookie
+- [Caching levels](/cache/how-to/set-caching-levels/)
+- [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+- Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
+- [Origin cache-control headers](/cache/concepts/cache-control/)
+- Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
+- Cache rules that bypass cache on cookie
 
 Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, or content hosted on [DNS-only (unproxied)](/dns/proxy-status/) DNS records.
 
@@ -34,35 +34,35 @@ Cloudflare only caches resources within the Cloudflare data center that serve th
 
 Discover the benefits of caching with Cloudflare's CDN and understand the default cache behavior.
 
-* [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
-* [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
-* [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+- [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
+- [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
+- [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
 
 ## Make more resources cacheable
 
 Configure your settings to cache static HTML or cache anonymous page views of dynamic content.
 
-* [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
-* [Specify which resources to cache](/cache/concepts/customize-cache/)
-* [Understand Origin Cache Control](/cache/concepts/cache-control/)
-* [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
+- [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
+- [Specify which resources to cache](/cache/concepts/customize-cache/)
+- [Understand Origin Cache Control](/cache/concepts/cache-control/)
+- [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
 
 ## Improve cache HIT rates
 
 Include or exclude query strings, optimize cache keys, or enable [Tiered Cache](/cache/how-to/tiered-cache/) to improve HIT rates and reduce traffic to your origin.
 
-* [Choose a cache level](/cache/how-to/set-caching-levels/)
-* [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
-* [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
-* [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
+- [Choose a cache level](/cache/how-to/set-caching-levels/)
+- [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
+- [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
+- [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
 
 ## Secure your cache configuration
 
 Control resources a client is allowed to load and set access permissions to allow different origins to access your origin's resources. Protect your site from web cache deception attacks while still caching static assets.
 
-* [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
-* [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
-* [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
+- [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
+- [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
+- [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
 
 ## Features that alter cached content
 
@@ -70,16 +70,16 @@ Some Cloudflare features modify your HTML or cached objects at the edge to enabl
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. Cloudflare removes the changes when you disable the feature and purge the cache.
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. The changes are removed if the feature is disabled and the cache is purged.
 
-* [Rocket Loader](/speed/optimization/content/rocket-loader/)
-* [Polish](/images/polish/)
-* [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
-* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
-* [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
+- [Rocket Loader](/speed/optimization/content/rocket-loader/)
+- [Polish](/images/polish/)
+- [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
+- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
+- [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
 
 ## Troubleshoot
 
 Resolve common caching concerns.
 
-* [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
-* [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
-* [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
+- [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
+- [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
+- [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
diff --git a/src/content/docs/cache/glossary.mdx b/src/content/docs/cache/glossary.mdx
index 93414f59d8d1137..ae52887a0324745 100644
--- a/src/content/docs/cache/glossary.mdx
+++ b/src/content/docs/cache/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Cache documentation.
 products:
   - cache
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Cache documentation.
 
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
index 5e0cffeecb60098..26540e1b1bc9dfc 100644
--- a/src/content/docs/cache/how-to/always-online.mdx
+++ b/src/content/docs/cache/how-to/always-online.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Serve cached pages when your origin server is unavailable.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Cloudflare’s Always Online feature is now integrated with the [Internet Archive](https://archive.org/) so that visitors can access a portion of your website even when your origin server is unreachable and a Cloudflare-cached version is unavailable. When your origin is unreachable, Always Online checks Cloudflare’s cache for a stale or expired version of your website. If a version does not exist, Cloudflare goes to the Internet Archive to fetch and serve static portions of your website.
 
@@ -46,10 +45,8 @@ Here is how to enable Always Online in the dashboard:
 
 :::note[Note]
 
-
 When turning on Always Online, you are also enabling the Internet Archive integration.
 
-
 :::
 
 Refer to [Always Online](/cache/troubleshooting/always-online/) for best practices, limitations, and FAQs.
diff --git a/src/content/docs/cache/how-to/cache-keys.mdx b/src/content/docs/cache/how-to/cache-keys.mdx
index 59b3e1e4cd98538..8afbd280f376234 100644
--- a/src/content/docs/cache/how-to/cache-keys.mdx
+++ b/src/content/docs/cache/how-to/cache-keys.mdx
@@ -14,16 +14,16 @@ head:
     content: Cache Keys
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.
 
 A default cache key includes:
 
 1. Full URL:
-   * scheme - could be HTTP or HTTPS.
-   * host - for example, `www.cloudflare.com`
-   * URI with query string - for example, `/logo.jpg?utm_source=newsletter`
+   - scheme - could be HTTP or HTTPS.
+   - host - for example, `www.cloudflare.com`
+   - URI with query string - for example, `/logo.jpg?utm_source=newsletter`
 2. Origin header sent by client (for CORS support).
 3. `x-http-method-override`, `x-http-method`, and `x-method-override` headers.
 4. `x-forwarded-host`, `x-host`, `x-forwarded-scheme` (unless http or https), `x-original-url`, `x-rewrite-url`, and `forwarded` headers.
@@ -51,8 +51,8 @@ When [URL normalization](/rules/normalization/) is enabled, we recommend also en
 
 There are a couple of common reasons to change the Cache Key Template. You might change the Cache Key Template to:
 
-* Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
-* Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
+- Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
+- Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
 
 ### Impact of SSL settings on Cache behavior
 
@@ -90,9 +90,9 @@ If you include the query string foo in a URL like `https://www.example.com/?foo=
 
 #### Usage notes
 
-* To include all query string parameters (the default behavior), use include: `"\*"`
-* To ignore query strings, use exclude: `"\*"`
-* To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
+- To include all query string parameters (the default behavior), use include: `"\*"`
+- To ignore query strings, use exclude: `"\*"`
+- To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
 
 ### Headers
 
@@ -102,13 +102,13 @@ When you include a header, the header value is included in the Cache Key. For ex
 
 In the **Include headers and selected values** section, you can add header names and their values to the cache key. For custom headers, values are optional, but for the following restricted headers, you must include one to 10 specific values:
 
-  * `accept`
-  * `accept-charset`
-  * `accept-encoding`
-  * `accept-datetime`
-  * `accept-language`
-  * `referer`
-  * `user-agent`
+- `accept`
+- `accept-charset`
+- `accept-encoding`
+- `accept-datetime`
+- `accept-language`
+- `referer`
+- `user-agent`
 
 To check for the presence of a header without including its actual value, use the **Check presence of** option.
 
@@ -116,28 +116,28 @@ Currently, you can only exclude the `Origin` header. The `Origin` header is alwa
 
 Additionally, you cannot include the following headers:
 
-* Headers that re-implement cache or proxy features
-  * `connection`
-  * `content-length`
-  * `cache-control`
-  * `if-match`
-  * `if-modified-since`
-  * `if-none-match`
-  * `if-unmodified-since`
-  * `range`
-  * `upgrade`
-* Headers that are covered by other Cache Key features
-  * `cookie`
-  * `host`
-* Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
-* Headers that are already included in the custom Cache Key template, for example, `origin`
+- Headers that re-implement cache or proxy features
+  - `connection`
+  - `content-length`
+  - `cache-control`
+  - `if-match`
+  - `if-modified-since`
+  - `if-none-match`
+  - `if-unmodified-since`
+  - `range`
+  - `upgrade`
+- Headers that are covered by other Cache Key features
+  - `cookie`
+  - `host`
+- Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
+- Headers that are already included in the custom Cache Key template, for example, `origin`
 
 ### Host
 
 Host determines which host header to include in the Cache Key.
 
-* If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
-* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
+- If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
+- If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
 
 ### Cookie
 
@@ -151,9 +151,9 @@ You cannot include cookies specific to Cloudflare. Cloudflare cookies are prefix
 
 User feature fields add features about the end-user (client) into the Cache Key.
 
-* `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
-* `geo` includes the client’s country, derived from the IP address
-* `lang` includes the first language code contained in the `Accept-Language` header sent by the client
+- `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
+- `geo` includes the client’s country, derived from the IP address
+- `lang` includes the first language code contained in the `Accept-Language` header sent by the client
 
 ## Availability
 
diff --git a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
index f8032d4bd1be12e..7c75c81a407e301 100644
--- a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
+++ b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
@@ -30,7 +30,6 @@ 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 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:
@@ -43,7 +42,8 @@ import { Render, DashButton } from "~/components";
    - **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**.
 
-   <Render file="rules-creation-dash-dns-popup" product="rules" />
+<Render file="rules-creation-dash-dns-popup" product="rules" />
diff --git a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
index ba3e5a14e0342aa..24434a23533ec9f 100644
--- a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: false
 pcx_content_type: navigation
 description: Example cache rule configurations for common use cases.
@@ -8,10 +7,9 @@ products:
 title: Examples
 sidebar:
   order: 8
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In the following sections, you can find common cache rules examples.
 
diff --git a/src/content/docs/cache/how-to/cache-rules/order.mdx b/src/content/docs/cache/how-to/cache-rules/order.mdx
index 40377bc15fa1145..5810d731d8608f8 100644
--- a/src/content/docs/cache/how-to/cache-rules/order.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/order.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Order and priority
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cache rules affect requests differently from Page Rules. This is how they are applied:
 
diff --git a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
index 6541177a91b6aa8..b1875b3767c20c3 100644
--- a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
@@ -13,7 +13,7 @@ head:
     content: Migration from Page Rules
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 If you are migrating from Page Rules, there is a behavior change between Page Rules and Cache Rules.
 
@@ -64,10 +64,8 @@ If you prefer, you can select **Edit expression** and paste the following expres
 
 :::note[Note]
 
-
 Remember to create the rules in the specified order: first, the `bypass everything` rule, and then the `cache all default cacheable file extensions` rule.
 
 ![Rules order](~/assets/images/cache/rule-order.png)
 
-
 :::
diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
index 2c71df51f6c0e94..c30d541d4d833c7 100644
--- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx
+++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
@@ -8,7 +8,7 @@ tags:
   - REST API
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin.
 
@@ -19,10 +19,10 @@ Setting cache TTL based on response status overrides the [default cache behavior
 The maximum caching limit for Free, Pro, and Business customers is 512 MB per file, and the maximum caching limit for Enterprise customers is 5 GB per file. If you need to raise the limits, contact your Customer Success Manager.
 
 <Render
-  file="edge-ttl"
+	file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
@@ -79,9 +79,9 @@ curl --request PUT \
 
 Provide a JSON object containing status codes and their corresponding TTLs. Each key-value pair in the cache TTL by status cache rule has the following syntax:
 
-* `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
-* `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
-* `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
+- `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
+- `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
+- `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
 
 ## Set cache TTL by response status via a Cloudflare Worker
 
@@ -98,4 +98,4 @@ The **cacheTtlByStatus** option is a version of the **cacheTtl** feature that de
 
 For example, if a user specifies a TTL of one hour for status `200` and 0 seconds (cache and always revalidate) for status `304`, the asset will be cached for 1 hour. After it expires, we revalidate with the origin. If the origin returns a `304`, each subsequent request will trigger revalidation. If the origin continues to return `304`, this cycle will persist.
 
-This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
\ No newline at end of file
+This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
index 9bd8eb61f1eeb6f..c26df5fd963f037 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Configure edge and browser cache TTL for your resources.
 products:
   - cache
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 ## Edge Cache TTL
 
@@ -21,17 +20,16 @@ For more information on how to set up Edge Cache TTL, refer to [Cache rules](/ca
 
 The Browser Cache TTL sets the expiration for resources cached in a visitor’s browser. By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers but overrides those headers if:
 
-* The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
-* The origin web server does not send a `Cache-Control` or an `Expires` header.
+- The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
+- The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a cache rule, Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
 :::note[Note]
 
-
-* Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
-* If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
-* Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser. 
+- Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
+- If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
+- Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.
   :::
 
 <FeatureTable id="cache.browser_cache_ttl" />
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
index fcaf35844aa8d00..bed629ee6ba70c8 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 3
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +14,8 @@ Specify a time for a visitor’s Browser Cache TTL to accelerate the page load f
 
 By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers. Cloudflare overrides any `Cache-Control` or `Expires` headers with values set via the **Browser Cache TTL** option under **Caching** on your dashboard if:
 
-* The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
-* The origin web server does not send a `Cache-Control` or an `Expires` header.
+- The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
+- The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a [Cache Rule](/cache/how-to/cache-rules/), Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
@@ -26,10 +25,8 @@ Nevertheless, the value you set via Cache Rule will be ignored if `Cache-Control
 
 :::note[Note]
 
-
 If you modify cached assets, the new asset is not displayed to repeat visitors before the Browser Cache TTL duration. [Purging Cloudflare’s cache](/cache/how-to/purge-cache/) does not affect assets cached in a visitor’s browser.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Caching** page.
diff --git a/src/content/docs/cache/how-to/index.mdx b/src/content/docs/cache/how-to/index.mdx
index 80c1f5c0266452d..9bb4c1c487aacad 100644
--- a/src/content/docs/cache/how-to/index.mdx
+++ b/src/content/docs/cache/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
index eccbbdee17432d8..f33d3c2f25167fd 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 4
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Purging by hostname means that all assets at URLs with a host that matches one of the provided values will be instantly purged from the cache.
 
@@ -20,9 +19,9 @@ Purging by hostname means that all assets at URLs with a host that matches one o
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Hostname**.
 4. Follow the syntax instructions:
-   * One hostname per line.
-   * Separated by commas.
-   * You can purge up to 30 hostnames at a time.
+   - One hostname per line.
+   - Separated by commas.
+   - You can purge up to 30 hostnames at a time.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
index 1eba5da16e5ee10..20267fbc6318106 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 With purge by single-file, cached resources are instantly removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific Cloudflare data center that served the request.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
index 0531322accc993e..0b305a3f14ae32d 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 3
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more.
 
@@ -23,10 +22,8 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 
 :::caution[Warning]
 
-
 Be careful when purging. A cache MISS can cause execution delays by requiring a fetch from your origin server.
 
-
 :::
 
 ## Add Cache-Tag HTTP response headers
@@ -35,19 +32,19 @@ You add cache-tags to your web content in `Cache-Tag` HTTP response headers to a
 
 When your content reaches our edge network, Cloudflare:
 
-* Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
-* Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
-* Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
+- Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
+- Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
+- Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
 
 ## A few things to remember
 
-* A single HTTP response can have more than one `Cache-Tag` HTTP header field.
-* The minimum length of a cache-tag is one byte.
-* Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
-* For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
-* The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
-* Spaces are not allowed in cache-tags.
-* Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
+- A single HTTP response can have more than one `Cache-Tag` HTTP header field.
+- The minimum length of a cache-tag is one byte.
+- Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
+- For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
+- The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
+- Spaces are not allowed in cache-tags.
+- Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
 
 ## Purge using cache-tags
 
@@ -62,7 +59,6 @@ When your content reaches our edge network, Cloudflare:
 
 For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
 
-
 ## Resulting cache status
 
 Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests.
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
index 831850a380c6d9f..d251d69477368b4 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
@@ -25,18 +25,18 @@ For a Cache Key based on device type, purge the asset by passing the `CF-Device-
 Refer to the example API request below to instantly purge all mobile assets on the root webpage.
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "CF-Device-Type": "mobile"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"CF-Device-Type": "mobile",
+				},
+			},
+		],
+	}}
 />
 
 ## Purge by geo
@@ -44,18 +44,18 @@ Refer to the example API request below to instantly purge all mobile assets on t
 Instantly purge resources for a location-based Cache Key by specifying the two-letter country code. Spain is used in the example below.
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "CF-IPCountry": "ES"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"CF-IPCountry": "ES",
+				},
+			},
+		],
+	}}
 />
 
 ## Purge by language
@@ -63,16 +63,16 @@ Instantly purge resources for a location-based Cache Key by specifying the two-l
 For a Cache Key based on language, purge the asset by passing the `accept-language` header. Refer to the example API request below to instantly purge all assets in Chinese (PRC).
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "accept-language": "zh-CN"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"accept-language": "zh-CN",
+				},
+			},
+		],
+	}}
 />
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
index 1253a3d847f6bfb..42378f5e362023e 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 2
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 To maintain optimal site performance, Cloudflare strongly recommends using single-file (by URL) purging instead of a complete cache purge.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
index 2da37b5840f703d..f2953ab487936d9 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 7
-
 ---
 
 Purging varied images instantly purges all content variants for that URL. This behavior occurs so that if an image changes, you can easily update the cache with a single purge request instead of trying to determine the potential number of out-of-date variants. The behavior is true regardless of [purge type](/cache/how-to/purge-cache/) used, such as [single file](/cache/how-to/purge-cache/purge-by-single-file/), [tag](/cache/how-to/purge-cache/purge-by-tags/), or [hostname](/cache/how-to/purge-cache/purge-by-hostname/).
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
index 06f0af7f6b98cd4..837b8a1faf20235 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 8
-
 ---
 
 To purge zone versions via the Cloudflare API, follow these steps:
@@ -23,44 +22,44 @@ This API call will return a JSON response similar to the example below:
 
 ```json
 {
-  "result": {
-    "environments": [
-      {
-        "name": "Production",
-        "ref": "12abcd3e45f678940a573f51834a54",
-        "version": 0,
-        "expression": "(cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "before": "5d41402abc4b2a76b9719d911017c"
-        }
-      },
-      {
-        "name": "Staging",
-        "ref": "5d41402abc4b2a76b9719d911017c",
-        "version": 0,
-        "expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "before": "49f0bad299687c62334182178bfd",
-          "after": "12abcd3e45f678940a573f51834a54"
-        }
-      },
-      {
-        "name": "Development",
-        "ref": "49f0bad299687c62334182178bfd",
-        "version": 0,
-        "expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "after": "5d41402abc4b2a76b9719d911017c"
-        }
-      }
-    ]
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"environments": [
+			{
+				"name": "Production",
+				"ref": "12abcd3e45f678940a573f51834a54",
+				"version": 0,
+				"expression": "(cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"before": "5d41402abc4b2a76b9719d911017c"
+				}
+			},
+			{
+				"name": "Staging",
+				"ref": "5d41402abc4b2a76b9719d911017c",
+				"version": 0,
+				"expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"before": "49f0bad299687c62334182178bfd",
+					"after": "12abcd3e45f678940a573f51834a54"
+				}
+			},
+			{
+				"name": "Development",
+				"ref": "49f0bad299687c62334182178bfd",
+				"version": 0,
+				"expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"after": "5d41402abc4b2a76b9719d911017c"
+				}
+			}
+		]
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -76,7 +75,7 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/purge_cache/
 
 To purge non-production environments, you must use a new `purge_cache` endpoint and specify the environment you would like to purge.
 
-To purge the Staging environment from the example above, send a request to the following endpoint: 
+To purge the Staging environment from the example above, send a request to the following endpoint:
 
 ```bash
 https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/5d41402abc4b2a76b9719d911017c/purge_cache/
@@ -90,4 +89,4 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/49f0bad299687c
 
 :::note
 When purging everything for a non-production cache environment, all files for that specific cache environment will be purged. However, when purging everything for the production environment, all files will be purged across all environments.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
index 315411bd1db2ac1..38922ec63e70388 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
@@ -6,24 +6,23 @@ products:
   - cache
 sidebar:
   order: 5
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 You can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
 
-* `www.example.com`
-* `www.example.com/foo`
-* `www.example.com/foo/bar`
-* `www.example.com/foo/bar/baz`
-* `www.example.com/foo/bar/baz/qux.jpg`
+- `www.example.com`
+- `www.example.com/foo`
+- `www.example.com/foo/bar`
+- `www.example.com/foo/bar/baz`
+- `www.example.com/foo/bar/baz/qux.jpg`
 
 Purging by prefix is useful in different scenarios, such as:
 
-* Purging everything within a directory.
-* Increasing control over cached objects in a path.
-* Simplifying the number of purge calls sent.
+- Purging everything within a directory.
+- Increasing control over cached objects in a path.
+- Simplifying the number of purge calls sent.
 
 1. In the Cloudflare dashboard, go to the **Configuration** page.
 
@@ -32,8 +31,8 @@ Purging by prefix is useful in different scenarios, such as:
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Prefix**.
 4. Follow the syntax instructions.
-   * One prefix per line.
-   * Maximum 30 prefixes per API call.
+   - One prefix per line.
+   - Maximum 30 prefixes per API call.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
@@ -41,10 +40,8 @@ For information on rate limits, refer to the [Availability and limits](/cache/ho
 
 :::caution[Warning]
 
-
 If you have a [Transform Rule](/rules/transform/) in place that is modifying part of a URL path, you must use the post-transformed (origin) URL when performing a prefix purge so that purge can take effect.
 
-
 :::
 
 ## Resulting cache status
@@ -58,21 +55,19 @@ Depending on whether the upper tier has the resource or not, and whether the end
 
 There are several limitations regarding purge by prefix:
 
-* Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
-* Purge requests are limited to 30 prefixes per request.
-* [Purge rate-limits apply](/api/resources/cache/methods/purge/).
-* URI query strings & fragments cannot purge by prefix:
-  * `www.example.com/foo?a=b` (query string)
-  * `www.example.com/foo#bar` (fragment)
+- Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
+- Purge requests are limited to 30 prefixes per request.
+- [Purge rate-limits apply](/api/resources/cache/methods/purge/).
+- URI query strings & fragments cannot purge by prefix:
+  - `www.example.com/foo?a=b` (query string)
+  - `www.example.com/foo#bar` (fragment)
 
 :::caution[Warning]
 
-
 Because purge by prefix purges a directory, any URI for a resource within the purged directory is purged regardless of query string or fragment (though fragments are not generally sent by browsers). Purge by prefix rules do not accept fragments and query strings.
 
 Example: If you purge `foo.com/bar`, any asset that starts with `foo.com/bar` will be purged, for example, `foo.com/bar/baz`, `foo.com/bar?good=bad`, etc. and purging `foo.com/bar?good=bad` itself will not work.
 
-
 :::
 
 ## Purge by prefix normalization
diff --git a/src/content/docs/cache/how-to/set-caching-levels.mdx b/src/content/docs/cache/how-to/set-caching-levels.mdx
index 4d6a0dee4f74ba7..84cb1614461925d 100644
--- a/src/content/docs/cache/how-to/set-caching-levels.mdx
+++ b/src/content/docs/cache/how-to/set-caching-levels.mdx
@@ -7,23 +7,20 @@ products:
 head:
   - tag: title
     content: Caching levels
-
 ---
 
 Caching levels determine how much of your website’s static content Cloudflare should cache. Cloudflare’s CDN caches static content according to the levels below.
 
-* **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
-* **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
-* **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
+- **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
+- **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
+- **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
 
 You can adjust the caching level from the dashboard under **Caching** > **Configuration** > **Caching level**.
 
 :::note[Note]
 
-
 Ignore Query String only disregards the query string for static file extensions. For example, Cloudflare serves the `style.css` resource to requests for either `style.css?this` or `style.css?that`.
 
-
 :::
 
 ## API Caching level values
diff --git a/src/content/docs/cache/interaction-cloudflare-products/index.mdx b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
index 449a56ed4e7345c..842985c69a31adc 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/index.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-    
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare caches content at data centers close to your visitors so your origin server handles fewer requests. The pages below explain how caching works when you also use Workers, R2 storage, or WAF security rules, and what to watch out for when combining them.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
index ed54947bc4e5f34..11c3946c910d777 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Enable cache in an R2 bucket
-
 ---
 
 By default, R2 buckets are private. To serve R2 objects through Cloudflare's cache, you need to attach a domain name you control — called a [Custom Domain](/r2/buckets/public-buckets/#custom-domains) — to the bucket. This creates a public URL backed by Cloudflare's network, so requests for your stored files go through Cloudflare's cache instead of hitting R2 directly every time.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
index fb6bf25720d358f..5f5d22b02dd934b 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
@@ -23,7 +23,7 @@ accTitle: Connections with Cloudflare
 A[User's request] --> B[WAF] --> C[Cache] --> D[R2]
 ```
 
-<br/>
+<br />
 
 ## Presigned URLs
 
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
index 390f1369a9cee75..a7765d2c345f3a1 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: How Workers interact with Cache Rules
-
 ---
 
 When you use both [Cache Rules](/cache/how-to/cache-rules/) and [Workers](/workers/) on the same request, the Worker's cache settings take priority — but only when the required [compatibility flags](#compatibility-flags) are enabled.
@@ -39,10 +38,10 @@ These flags must be enabled to allow Workers scripts to override Cache Rules. If
 
 A Worker's [compatibility date](/workers/configuration/compatibility-dates/) determines which flags are active by default. When you set a compatibility date, all flags with an enable date on or before that date are automatically turned on.
 
-| Flag | Enabled by default | Prerequisite |
-| --- | --- | --- |
-| `request_cf_overrides_cache_rules` (Fetch API) | Compatibility dates on or after `2025-04-02` | None |
-| `cache_api_compat_flags` | Compatibility dates on or after `2025-04-19` | None |
+| Flag                                                     | Enabled by default                           | Prerequisite                      |
+| -------------------------------------------------------- | -------------------------------------------- | --------------------------------- |
+| `request_cf_overrides_cache_rules` (Fetch API)           | Compatibility dates on or after `2025-04-02` | None                              |
+| `cache_api_compat_flags`                                 | Compatibility dates on or after `2025-04-19` | None                              |
 | `cache_api_request_cf_overrides_cache_rules` (Cache API) | Compatibility dates on or after `2025-05-19` | Requires `cache_api_compat_flags` |
 
 The Cache API has an extra requirement: `cache_api_compat_flags` must be enabled for any compatibility flags to take effect on the Cache API. Without it, the Cache API ignores all compatibility flags, even ones you explicitly list in your configuration.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
index 0b90c7883ab5180..91df57a65ed0396 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Customize cache behavior with Workers
-
 ---
 
 You can use [Workers](/workers/) to customize cache behavior on Cloudflare's network. Workers run as middleware in the request lifecycle — a single Worker handles both the request and response phases. When a request arrives, it hits the Worker before the cache is checked. The Worker can modify the incoming request (for example, rewrite the URL or add headers), then call `fetch()` to continue the request through the cache. When the response comes back — whether from cache or from the origin server — the Worker can also modify the response before it is sent to the visitor.
@@ -46,4 +45,4 @@ Workers offer two ways to interact with the cache. Use `fetch()` when your Worke
 
 - **Cache API**: Allows you to programmatically store, retrieve, and delete responses in Cloudflare's cache using `caches.default` or `caches.open()`. Unlike `fetch()`, the Cache API only operates on the cache in the data center handling the current request — it does not interact with Tiered Cache. Use the Cache API when you need to cache responses that did not come from an origin. For more details, refer to [Using the Cache API](/workers/examples/cache-api/).
 
-To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
\ No newline at end of file
+To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
diff --git a/src/content/docs/cache/performance-review/cache-analytics.mdx b/src/content/docs/cache/performance-review/cache-analytics.mdx
index 5e225c6a89340c7..6db30fa95015ec1 100644
--- a/src/content/docs/cache/performance-review/cache-analytics.mdx
+++ b/src/content/docs/cache/performance-review/cache-analytics.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: View cache hit rates and bandwidth savings in Cache Analytics.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Cache Analytics shows how much of your site's traffic is served from Cloudflare's cache versus your origin server. When content is served from cache, visitors get faster page loads and your origin web server handles less traffic. Use Cache Analytics to identify resources that are [missing from cache](/cache/concepts/cache-responses/#miss), [expired](/cache/concepts/cache-responses/#expired) (cached copy is outdated), or [ineligible for caching](/cache/concepts/cache-responses/#noneunknown) (not eligible for caching). You can filter by hostname, review the top URLs that miss cache, and query up to three days of data.
 
@@ -19,7 +18,7 @@ Cache Analytics shows how much of your site's traffic is served from Cloudflare'
 
 In the Cloudflare dashboard, go to the **Caching** page.
 
-   <DashButton url="/?to=/:account/:zone/caching" />
+<DashButton url="/?to=/:account/:zone/caching" />
 
 ## Requests vs Data Transfer
 
diff --git a/src/content/docs/cache/performance-review/cache-performance.mdx b/src/content/docs/cache/performance-review/cache-performance.mdx
index 528344752e6ef3d..9e4e9ebc7569a11 100644
--- a/src/content/docs/cache/performance-review/cache-performance.mdx
+++ b/src/content/docs/cache/performance-review/cache-performance.mdx
@@ -24,7 +24,6 @@ Depending on the [cache status](/cache/concepts/cache-responses/) you receive, y
 Use [Cache Analytics](/cache/performance-review/cache-analytics/) to identify cache performance issues. The following examples show how to filter for common problems and resolve them.
 
 - Not caching HTML.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Dynamic**.
   - Resolution: Set a Cloudflare Cache Rule to [cache dynamic content](/cache/how-to/cache-rules/examples/cache-everything/).
 
@@ -35,14 +34,12 @@ This option caches all HTML regardless of the presence of dynamic content (conte
 - Checking for the presence of a cookie.
 - Excluding requests that match known dynamic content file paths.
 - Excluding requests with dynamic content extensions (or no extension).
-:::
+  :::
 
 - Short cache expiration TTL.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Revalidated**.
   - Resolution: [Increase Cloudflare's Edge Cache TTL via a Cache Rule](/cache/how-to/cache-rules/examples/edge-ttl/).
 
 - Need to enable Tiered Cache or custom cache key.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Miss**.
   - Resolution: [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) or [create a custom cache key](/cache/how-to/cache-rules/examples/custom-cache-key/).
diff --git a/src/content/docs/cache/performance-review/index.mdx b/src/content/docs/cache/performance-review/index.mdx
index 62a5b788d098027..b2b00f57fe7dfb6 100644
--- a/src/content/docs/cache/performance-review/index.mdx
+++ b/src/content/docs/cache/performance-review/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 8
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use Cache Analytics to understand how effectively Cloudflare caches your content, and apply optimization techniques to improve your cache hit ratio and reduce origin server load.
 
diff --git a/src/content/docs/cache/plans.mdx b/src/content/docs/cache/plans.mdx
index e8f54313de37f9f..a4543e9bf53afe7 100644
--- a/src/content/docs/cache/plans.mdx
+++ b/src/content/docs/cache/plans.mdx
@@ -10,13 +10,12 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="cache" />
\ No newline at end of file
+<ProductFeatures id="cache" />
diff --git a/src/content/docs/cache/reference/cdn-reference-architecture.mdx b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
index 4681ed5552d3aa6..145f83c1cb84f3c 100644
--- a/src/content/docs/cache/reference/cdn-reference-architecture.mdx
+++ b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
@@ -5,5 +5,4 @@ products:
   - cache
 title: CDN Reference Architecture
 external_link: /reference-architecture/architectures/cdn/
-
 ---
diff --git a/src/content/docs/cache/reference/development-mode.mdx b/src/content/docs/cache/reference/development-mode.mdx
index c6f9d879d1f7baf..417c841881601c5 100644
--- a/src/content/docs/cache/reference/development-mode.mdx
+++ b/src/content/docs/cache/reference/development-mode.mdx
@@ -4,16 +4,15 @@ pcx_content_type: how-to
 description: Bypass the cache temporarily with Development Mode.
 products:
   - cache
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript.
 
 :::note
 
-To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache). 
+To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache).
 :::
 
 ## Enable Development Mode
diff --git a/src/content/docs/cache/reference/index.mdx b/src/content/docs/cache/reference/index.mdx
index 57aa94f03cf5680..fa4c9cb8953cc15 100644
--- a/src/content/docs/cache/reference/index.mdx
+++ b/src/content/docs/cache/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the reference content to learn more about specific caching functionality.
 
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx
index c5011e04ae13af4..bd25e5e49df3439 100644
--- a/src/content/docs/cache/troubleshooting/always-online.mdx
+++ b/src/content/docs/cache/troubleshooting/always-online.mdx
@@ -36,16 +36,13 @@ Always Online does not trigger for HTTP response codes such as [404](/support/tr
 ## Frequently asked questions
 
 1. How can I know if a page has been crawled?
-
    - You can go to the [Internet Archive](https://web.archive.org/) and search for the page URL to see if it has been crawled or not.
    - You can also check this via the [Internet Archive Availability API](https://archive.org/help/wayback_api.php).
 
 2. Why were not pages x, y, and z crawled?
-
    - Since Cloudflare only requests to crawl the most popular pages on the site, it is possible that there will be missing pages. If you really want to archive a page, then you can visit the [Internet Archive](https://web.archive.org/save) save page and ask them to crawl a particular page.
 
 3. What IP addresses do we need to allowlist to make sure crawling works?
-
    - IP Range: `207.241.224.0/20` and `208.70.24.0/21`. Note that this ip range belongs to Internet Archive and NOT Cloudflare, since it is the Internet Archive that does the crawling.
 
 4. What user agent should the origin expect to see?
diff --git a/src/content/docs/cache/troubleshooting/index.mdx b/src/content/docs/cache/troubleshooting/index.mdx
index 6d019d87491a048..43a1ccb36799ea9 100644
--- a/src/content/docs/cache/troubleshooting/index.mdx
+++ b/src/content/docs/cache/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The following topics are useful for troubleshooting Cache issues.
 
diff --git a/src/content/docs/china-network/concepts/global-acceleration.mdx b/src/content/docs/china-network/concepts/global-acceleration.mdx
index d5cf13877556bdc..65a11d18c9950e0 100644
--- a/src/content/docs/china-network/concepts/global-acceleration.mdx
+++ b/src/content/docs/china-network/concepts/global-acceleration.mdx
@@ -30,14 +30,14 @@ Organizations that serve content or connect employees in Mainland China face con
 
 Global Acceleration can support the following scenarios:
 
-| Service                                                                                 | Scenario                                                            |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
+| Service                                                                                 | Scenario                                                                                           |
+| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
 | [CDN Global Acceleration](#cdn-global-acceleration)                                     | Improved performance for dynamic content (API responses, personalized pages) on China Network CDN. |
-| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                       |
-| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                              |
-| [ICP](#icp-services)                                                                    | China Network prerequisite.                                         |
-| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                       |
-| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China. |
+| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                                                      |
+| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                                                             |
+| [ICP](#icp-services)                                                                    | China Network prerequisite.                                                                        |
+| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                                                      |
+| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China.                  |
 
 ## CDN Global Acceleration
 
diff --git a/src/content/docs/china-network/reference/available-products.mdx b/src/content/docs/china-network/reference/available-products.mdx
index f5ba030c4d27bda..0ae2911eaa5b486 100644
--- a/src/content/docs/china-network/reference/available-products.mdx
+++ b/src/content/docs/china-network/reference/available-products.mdx
@@ -37,7 +37,7 @@ The following products and features are available on the Cloudflare China Networ
 | [R2](/r2/)[^3]                                                            | Object storage for all your data.                                                                                                                  |
 | [Assets](/workers/static-assets/)                                         | Upload static assets (HTML, CSS, images and other files) as part of your Worker — Cloudflare will handle caching and serving them to web browsers. |
 | [Environment variables](/workers/configuration/environment-variables/)    | Attach text strings or JSON values to your Worker.                                                                                                 |
-| [Images](/images/optimization/transformations/bindings/)[^4]                          | Store, transform, optimize, and deliver images at scale.                                                                                           |
+| [Images](/images/optimization/transformations/bindings/)[^4]              | Store, transform, optimize, and deliver images at scale.                                                                                           |
 | [mTLS](/workers/runtime-apis/bindings/mtls/)                              | Securely connect to backend servers over [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).                        |
 | [Rate Limiting](/workers/runtime-apis/bindings/rate-limit/)               | Define rate limits and write code around them in your Worker.                                                                                      |
 | [Secrets](/workers/configuration/secrets/)                                | Attach encrypted text values to your Worker.                                                                                                       |
diff --git a/src/content/docs/client-ip-geolocation/about/index.mdx b/src/content/docs/client-ip-geolocation/about/index.mdx
index 28a8f360c648938..eeb0a5dfa94995f 100644
--- a/src/content/docs/client-ip-geolocation/about/index.mdx
+++ b/src/content/docs/client-ip-geolocation/about/index.mdx
@@ -10,10 +10,8 @@ description: Learn how Cloudflare Firewall Rules work.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 Cloudflare Client IP Geolocation helps you understand where in the world a given client is located, even if their true client IP address is obscured by Cloudflare's proxy systems. We offer this service to ensure customers have high-quality experiences interacting with origins that rely on geolocation — such as mapping providers — and origin operators can deliver the right content to the right users. Ensuring origins know where clients are located avoids problems associated with traditional VPNs that obscure a consumer’s geolocation and allow circumvention of geographic restrictions on content.
@@ -30,7 +28,7 @@ If a VPN user tries to use an interposed VPN or proxy system that attempts to hi
 
 ## Technical explanation
 
-We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like *MaxMind*, *IP 2 Location*, and *Neustar*.
+We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like _MaxMind_, _IP 2 Location_, and _Neustar_.
 
 When Cloudflare receives an inbound request from a WARP or 1.1.1.1 user, we first geolocate the IP address that made the connection to Cloudflare. Then, we select an egress IP that maps to the client geolocation. We then discard Client IP information to preserve user privacy but return their true geographic location.
 
diff --git a/src/content/docs/client-ip-geolocation/faq/index.mdx b/src/content/docs/client-ip-geolocation/faq/index.mdx
index c7687b23fc2d865..85a00673fec5ea2 100644
--- a/src/content/docs/client-ip-geolocation/faq/index.mdx
+++ b/src/content/docs/client-ip-geolocation/faq/index.mdx
@@ -10,10 +10,8 @@ description: Answers to common questions.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 ## Website operators
diff --git a/src/content/docs/client-ip-geolocation/get-started.mdx b/src/content/docs/client-ip-geolocation/get-started.mdx
index 7bfddd2706bc177..f6115e8f83f2b6f 100644
--- a/src/content/docs/client-ip-geolocation/get-started.mdx
+++ b/src/content/docs/client-ip-geolocation/get-started.mdx
@@ -10,18 +10,16 @@ description: Set up Client IP Geolocation for your network.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 There are several things you can do to best handle traffic from Cloudflare VPN and forward-proxy users:
 
-* **Origin operators**:
-  * Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
-  * To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
-* **Geolocation data providers**:
-  * Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
-* **Users of WARP and 1.1.1.1**:
-  * Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
+- **Origin operators**:
+  - Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
+  - To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
+- **Geolocation data providers**:
+  - Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
+- **Users of WARP and 1.1.1.1**:
+  - Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
diff --git a/src/content/docs/client-ip-geolocation/index.mdx b/src/content/docs/client-ip-geolocation/index.mdx
index 5464f9a0cb448ee..bd7c326b3032781 100644
--- a/src/content/docs/client-ip-geolocation/index.mdx
+++ b/src/content/docs/client-ip-geolocation/index.mdx
@@ -11,27 +11,27 @@ products:
 description: Add geolocation data for clients behind Cloudflare proxies.
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 Cloudflare designed [Cloudflare WARP](/warp-client/) and [1.1.1.1](/1.1.1.1/) to make Internet browsing more private and secure. These applications encrypt last-mile connections and make it more difficult for others to use client IP addresses in user fingerprinting.
 
 However, unlike legacy VPN applications, we never designed WARP or 1.1.1.1 to hide user locations or allow users to misrepresent their true geographic location. As a web property operator, you can use **Client IP Geolocation** to map Cloudflare egress IP addresses to specific geolocations.
 
- <LinkButton variant="primary" href="/client-ip-geolocation/get-started/">Get started</LinkButton> <LinkButton variant="secondary" href="/client-ip-geolocation/about/">Learn more</LinkButton>
-
+<LinkButton variant="primary" href="/client-ip-geolocation/get-started/">
+	Get started
+</LinkButton>
+<LinkButton variant="secondary" href="/client-ip-geolocation/about/">
+	Learn more
+</LinkButton>
 
 :::note
 
-
 Client IP Geolocation is different from the [Cloudflare IP Geolocation setting](/network/ip-geolocation/), which helps you capture country codes for visitors.
 
-
 :::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
index c3af18280364b77..e8e7c1e8e6a9464 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
@@ -214,4 +214,4 @@ The custom error token provides diagnostic information or specific functionality
     </html>
   ```
   </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
index 82759d6a2395e0b..a5b7daf4949db75 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
@@ -29,4 +29,4 @@ fetch("/my-api-endpoint").then((response) => {
 		// Process response as usual
 	}
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
index bc5eb92be6854f4..6c07e3d158b50d9 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
@@ -56,4 +56,4 @@ To ensure your API calls are protected without breaking single-page applications
 
 By enabling Pre-clearance, the Turnstile widget issues a persistent clearance cookie (`cf_clearance`) upon successful human verification on an initial HTML page. This cookie pre-clears the visitor to interact with sensitive API endpoints secured by WAF rules, allowing you to deploy granular security without forcing a disruptive Challenge Page response.
 
-For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
\ No newline at end of file
+For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
index ca4edef555c115d..9f1f938bab49aa4 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
@@ -19,4 +19,4 @@ When observing a Cloudflare Challenge page, a visitor could:
 
 :::note
 Visitors must enable JavaScript and cookies on their browser to be able to pass any type of Challenge.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
index 5ccae5620b19ca2..e0f3d123a4bb4d7 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on available challenge types:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
index 3a4bd64156f9af5..5c15a8df1753eff 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
@@ -16,7 +16,7 @@ Turnstile differs from Challenges Pages in that the challenge does not pause the
 
 In most cases, nothing further is required from the visitor. However, if necessary, Turnstile may display a simple checkbox that the visitor must click to proceed.
 
-After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions. 
+After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions.
 
 <Render file="siteverify-warning" product="turnstile" />
 
@@ -26,20 +26,18 @@ While there are three types of widgets that you can choose to implement on your
 
 - **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a challenge based on the signals gathered from the visitor's browser and presents an interaction only if it detects potentially automated traffic.
 
-- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity. 
+- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity.
 
 - **Invisible**: The widget is completely invisible to the visitor, but the challenge still runs in the background.
 
   :::note[Link to Cloudflare's Turnstile Privacy Policy]
-  <Render
-    file="privacy-policy"
-    product="turnstile"
-  />
+
+  <Render file="privacy-policy" product="turnstile" />
   :::
 
 ## Implementation
 
-When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey. 
+When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey.
 
 The sitekey is used with [client-side rendering](/turnstile/get-started/client-side-rendering/#implicitly-render-the-turnstile-widget) by adding it to the `<div>` container placeholder. You will then place that `<div>` code snippet where you want to add the widget to your site page or form.
 
diff --git a/src/content/docs/cloudflare-challenges/concepts/index.mdx b/src/content/docs/cloudflare-challenges/concepts/index.mdx
index 8587e3ba1d8f3f0..181b5dfde7eb724 100644
--- a/src/content/docs/cloudflare-challenges/concepts/index.mdx
+++ b/src/content/docs/cloudflare-challenges/concepts/index.mdx
@@ -7,11 +7,11 @@ products:
 sidebar:
   order: 2
   label: About
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on how challenges work:
 
diff --git a/src/content/docs/cloudflare-challenges/index.mdx b/src/content/docs/cloudflare-challenges/index.mdx
index b1612b44767b991..08083dc2ca79e13 100644
--- a/src/content/docs/cloudflare-challenges/index.mdx
+++ b/src/content/docs/cloudflare-challenges/index.mdx
@@ -11,7 +11,8 @@ sidebar:
 import { Render, Description, Plan, RelatedProduct } from "~/components";
 
 <Description>
-	Challenges are security mechanisms used by Cloudflare to verify whether a visitor to your site is a real human and not a bot or automated script.
+	Challenges are security mechanisms used by Cloudflare to verify whether a
+	visitor to your site is a real human and not a bot or automated script.
 </Description>
 
 When a Challenge is issued, Cloudflare asks the browser to perform a series of checks that help confirm the visitor's legitimacy. This process involves evaluating client-side signals (data gathered from the visitor's browser environment) or asking a visitor to take minimal action such as checking a box or selecting a button.
diff --git a/src/content/docs/cloudflare-challenges/reference/index.mdx b/src/content/docs/cloudflare-challenges/reference/index.mdx
index 3c0a6f05993d737..fe3f9e06287d1c6 100644
--- a/src/content/docs/cloudflare-challenges/reference/index.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Cloudflare Challenges:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
index a8b394b4c4b0410..d5d5ad31165401a 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
@@ -8,45 +8,43 @@ sidebar:
   order: 4
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
-Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge. 
+Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge.
 
-Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of. 
+Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of.
 
 ## Overview
 
-Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis. 
+Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis.
 
 ### Supported browsers
 
 The following browsers are officially supported and tested.
 
 <Details header="Google Chrome (desktop and mobile)">
-  - Current version and two previous major versions
-  - Chromium-based browsers and Chromium-based browsers that track the current Chrome stable version
-  
-  :::caution
-  Beta, Dev, Canary, Nightly, or other unreleased builds are not officially supported.
-  :::
+	- Current version and two previous major versions - Chromium-based browsers
+	and Chromium-based browsers that track the current Chrome stable version
+	:::caution Beta, Dev, Canary, Nightly, or other unreleased builds are not
+	officially supported. :::
 </Details>
 
 <Details header="Mozilla Firefox">
-  - Current version and two previous major versions
-  - Extended Support Release (ESR) versions are supported
+	- Current version and two previous major versions - Extended Support Release
+	(ESR) versions are supported
 </Details>
 
 <Details header="Safari">
-  - Current version and two previous major versions
-  - iOS Safari on current iOS version and two previous major versions
+	- Current version and two previous major versions - iOS Safari on current iOS
+	version and two previous major versions
 </Details>
 
 <Details header="Microsoft Edge">
-  - Current version and two previous major versions
-  </Details>
+	- Current version and two previous major versions
+</Details>
 
 <Details header="Samsung Internet Browser">
-  - Current version and two previous major versions
+	- Current version and two previous major versions
 </Details>
 
 ### Limited browser support
@@ -81,19 +79,19 @@ Browser extensions can interfere with challenges in several ways.
 - Browser automation tools are often detected as potential bots and may cause challenge failures.
 
 :::note
-If challenges consistently fail, try temporarily disabling extensions and reload the page. 
+If challenges consistently fail, try temporarily disabling extensions and reload the page.
 :::
 
 ### Device emulation and developer tools
 
 Challenges are designed to distinguish between real human users and automated traffic. When device emulation is enabled (such as through browser developer tools), it can trigger bot detection mechanisms.
 
-- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices. 
+- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices.
 - Developer tools may modify browser behavior or expose debugging information that changes how challenges operate.
 - Automation frameworks like Selenium, Puppeteer, or Playwright are specifically detected as non-human traffic.
 
 :::note
-For developers testing applications, we recommend using real devices rather than emulated environments when possible. 
+For developers testing applications, we recommend using real devices rather than emulated environments when possible.
 
 If you must use emulation, be aware that challenges may be more difficult to pass, and do not reflect the real experience on mobile devices.
 :::
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
index 3b3282d4adca332..c9c87ed0b0cddc3 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
@@ -12,30 +12,30 @@ sidebar:
 
 ## Multi-language support
 
-Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface. 
+Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface.
 
-For language support specific to Challenge Pages, refer to the table below. 
+For language support specific to Challenge Pages, refer to the table below.
 
-| Language                         | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
-| -------------------------------- | ----------------------------- | ----------------------------- |
-| Arabic (Egypt)                   | `ar-eg`                       | `ar`                          |
-| Chinese (Simplified, China)      | `zh-cn`                       | `zh`                          |
-| Chinese (Traditional, Taiwan)    | `zh-tw`                       | --                            |
-| Dutch (Netherlands)              | `nl-nl`                       | `nl`                          |
-| English (United States)          | `en-us`                       | `en`                          |
-| French (France)                  | `fr-fr`                       | `fr`                          |
-| German (Germany)                 | `de-de`                       | `de`                          |
-| Indonesian (Indonesia)           | `id-id`                       | `id`                          |
-| Italian (Italy)                  | `it-it`                       | `it`                          |
-| Japanese (Japan)                 | `ja-jp`                       | `ja`                          |
-| Korean (Korea)                   | `ko-kr`                       | `ko`                          |
-| Persian                          |  --                           | `fa`
-| Polish (Poland)                  | `pl-pl`                       | `pl`                          |
-| Portuguese (Brazil)              | `pt-br`                       | `pt`                          |
-| Russian (Russia)                 | `ru-ru`                       | `ru`                          |
-| Spanish (Spain)                  | `es-es`                       | `es`                          |
-| Turkish (Turkey)                 | `tr-tr`                       | `tr`                          |
+| Language                      | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
+| ----------------------------- | ----------------------------- | ----------------------------- |
+| Arabic (Egypt)                | `ar-eg`                       | `ar`                          |
+| Chinese (Simplified, China)   | `zh-cn`                       | `zh`                          |
+| Chinese (Traditional, Taiwan) | `zh-tw`                       | --                            |
+| Dutch (Netherlands)           | `nl-nl`                       | `nl`                          |
+| English (United States)       | `en-us`                       | `en`                          |
+| French (France)               | `fr-fr`                       | `fr`                          |
+| German (Germany)              | `de-de`                       | `de`                          |
+| Indonesian (Indonesia)        | `id-id`                       | `id`                          |
+| Italian (Italy)               | `it-it`                       | `it`                          |
+| Japanese (Japan)              | `ja-jp`                       | `ja`                          |
+| Korean (Korea)                | `ko-kr`                       | `ko`                          |
+| Persian                       | --                            | `fa`                          |
+| Polish (Poland)               | `pl-pl`                       | `pl`                          |
+| Portuguese (Brazil)           | `pt-br`                       | `pt`                          |
+| Russian (Russia)              | `ru-ru`                       | `ru`                          |
+| Spanish (Spain)               | `es-es`                       | `es`                          |
+| Turkish (Turkey)              | `tr-tr`                       | `tr`                          |
 
 ### Turnstile language support
 
-For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
\ No newline at end of file
+For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
diff --git a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
index d9da862f3207f6c..0403f66ba3ed126 100644
--- a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
@@ -8,10 +8,9 @@ tags:
   - Debugging
 sidebar:
   order: 2
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Challenge loops
 
@@ -35,6 +34,6 @@ Ensure your browser is updated to the latest version to maintain compatibility.
 
 Follow the steps below to ensure that your environment is properly configured.
 
-<Render file="troubleshooting-steps" product="turnstile"/>
+<Render file="troubleshooting-steps" product="turnstile" />
 
 If none of the above resolves your issue, contact the website administrator with the [error code](/turnstile/troubleshooting/client-side-errors/error-codes/) and Ray ID or submit a [feedback report](/turnstile/troubleshooting/feedback-reports/) through the Turnstile widget by selecting **Submit Feedback**.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
index 360ff1b151ff9d5..7ff0b1bb50a2ea4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
@@ -9,20 +9,19 @@ sidebar:
 head:
   - tag: title
     content: Backoff schedule | Hostname validation
-
 ---
 
 After you create a custom hostname, Cloudflare has to [validate that hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/).
 
 Attempts to validate a Custom Hostname are distributed over seven days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
 
-* For the first 10 attempts:
+- For the first 10 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.05, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
 ```
 
-* For the remaining 65 attempts:
+- For the remaining 65 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.15, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
index 3583929fa75cde3..e53e217ee14dd51 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Error codes - Custom Hostname Validation
-
 ---
 
 When you [validate a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/), you might encounter the following error codes.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
index 4e23151ad107b4f..12b2229cd3ba429 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Pre-validation methods - Custom Hostname Validation
-
 ---
 
 Pre-validation methods help verify domain ownership before your customer's traffic is proxying through Cloudflare.
@@ -30,10 +29,8 @@ TXT validation is when your customer adds a `TXT` record to their authoritative
 
 :::note
 
-
 If your customer cannot update their authoritative DNS, you could also use [HTTP validation](#http-tokens).
 
-
 :::
 
 To set up `TXT` validation:
@@ -42,21 +39,23 @@ To set up `TXT` validation:
 
    ```json null {11-12}
    {
-   "result": [
-       {
-       "id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
-       "hostname": "app.example.com",
-       // ...
-       "status": "pending",
-       "verification_errors": ["custom hostname does not CNAME to this zone."],
-       "ownership_verification": {
-           "type": "txt",
-           "name": "_cf-custom-hostname.app.example.com",
-           "value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
-       },
-       "created_at": "2020-03-04T19:04:02.705068Z"
-       }
-   ]
+   	"result": [
+   		{
+   			"id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
+   			"hostname": "app.example.com",
+   			// ...
+   			"status": "pending",
+   			"verification_errors": [
+   				"custom hostname does not CNAME to this zone."
+   			],
+   			"ownership_verification": {
+   				"type": "txt",
+   				"name": "_cf-custom-hostname.app.example.com",
+   				"value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
+   			},
+   			"created_at": "2020-03-04T19:04:02.705068Z"
+   		}
+   	]
    }
    ```
 
@@ -82,18 +81,18 @@ To get and use the `ownership_verification` record:
 
    ```json title="Example response (truncated)" {8-9}
    {
-     "result": [
-       {
-         "id": "24c8c68e-bec2-49b6-868e-f06373780630",
-         "hostname": "app.example.com",
-         // ...
-         "ownership_verification_http": {
-             "http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
-             "http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
-         },
-         "created_at": "2020-03-04T20:06:04.117122Z"
-       }
-     ]
+   	"result": [
+   		{
+   			"id": "24c8c68e-bec2-49b6-868e-f06373780630",
+   			"hostname": "app.example.com",
+   			// ...
+   			"ownership_verification_http": {
+   				"http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
+   				"http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
+   			},
+   			"created_at": "2020-03-04T20:06:04.117122Z"
+   		}
+   	]
    }
    ```
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
index 37075f00034342b..4cc01d36fb14628 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
@@ -15,7 +15,7 @@ description: Learn how to move hostnames between different zones.
 
 As a SaaS provider, you may want, or have, multiple zones to manage hostnames. Each zone can have different configurations or origins, as well as correlate to varying products. You might shift custom hostnames between zones to enable or disable certain features. Cloudflare allows migration within the same account through the steps below:
 
-***
+---
 
 ## CNAME
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
index 9623b2a72514ec3..3c056f32553e457 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
@@ -11,7 +11,7 @@ sidebar:
   order: 7
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can use custom hostname analytics for two general purposes: exploring how your customers use your product and sharing the benefits provided by Cloudflare with your customers.
 
@@ -19,19 +19,17 @@ These analytics include **Site Analytics**, **Bot Analytics**, **Cache Analytics
 
 :::note
 
-
 The plan of your Cloudflare for SaaS application determines the analytics available for your custom hostnames.
 
-
 :::
 
 ## Explore customer usage
 
 Use custom hostname analytics to help your organization with billing and infrastructure decisions, answering questions like:
 
-* "How many total requests is your service getting?"
-* "Is one customer transferring significantly more data than the others?"
-* "How many global customers do you have and where are they distributed?"
+- "How many total requests is your service getting?"
+- "Is one customer transferring significantly more data than the others?"
+- "How many global customers do you have and where are they distributed?"
 
 If you see one customer is using more data than another, you might increase their bill. If requests are increasing in a certain geographic region, you might want to increase the origin servers in that region.
 
@@ -41,9 +39,9 @@ To access custom hostname analytics, either [use the dashboard](/analytics/faq/a
 
 With custom hostname analytics, you can also share site information with your customers, including data about:
 
-* How many pageviews their site is receiving.
-* Whether their site has a large percentage of bot traffic.
-* How fast their site is.
+- How many pageviews their site is receiving.
+- Whether their site has a large percentage of bot traffic.
+- How fast their site is.
 
 Build custom dashboards to share this information by specifying an individual custom hostname in `clientRequestHTTPHost` field of [any dataset](/analytics/graphql-api/features/data-sets/) that includes this field.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
index 55fbfb5650d6322..5e86134809b77f7 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
@@ -6,7 +6,6 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Argo Smart Routing uses real-time global network information to route traffic on the fastest possible path across the Internet. Regardless of geographic location, this allows Cloudflare to optimize routing to make it faster, more reliable, and more secure. As a SaaS provider, you may want to emphasize the quickest traffic delivery for your end customers. To do so, [enable Argo Smart Routing](/argo-smart-routing/get-started/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
index 16b0b87aaa5f035..9b9a27e309eb3ba 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
@@ -6,7 +6,6 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Cloudflare makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers. Content can be either static or dynamic: static content is “cacheable” or eligible for caching, and dynamic content is “uncacheable” or ineligible for caching. The cached copies of content are stored physically closer to users, optimized to be fast, and do not require recomputing.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
index 439f92b92dc27a1..74ec34298a49532 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
@@ -12,13 +12,13 @@ import { APIRequest } from "~/components";
 
 [Early Hints](/cache/advanced-configuration/early-hints/) allows the browser to begin loading resources while the origin server is compiling the full response. This improves webpage’s loading speed for the end user. As a SaaS provider, you may prioritize speed for some of your custom hostnames. Using custom metadata, you can [enable Early Hints](/cache/advanced-configuration/early-hints/#enable-early-hints) per custom hostname.
 
-***
+---
 
 ## Prerequisites
 
 Before you can employ Early Hints for SaaS, you need to create a custom hostname. Review [Get Started with Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) if you have not already done so.
 
-***
+---
 
 ## Enable Early Hints per custom hostname via the API
 
@@ -29,51 +29,51 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
 3. If you are [creating a new custom hostname](/api/resources/custom_hostnames/methods/create/), make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames"
-  method="POST"
-  json={{
-		"hostname": "<CUSTOM_HOSTNAME>",
-		"ssl": {
-			"method": "http",
-			"type": "dv",
-			"settings": {
-				"http2": "on",
-				"min_tls_version": "1.2",
-				"tls_1_3": "on",
-				"early_hints": "on"
-				},
-				"bundle_method": "ubiquitous",
-				"wildcard": false
+	path="/zones/{zone_id}/custom_hostnames"
+	method="POST"
+	json={{
+		hostname: "<CUSTOM_HOSTNAME>",
+		ssl: {
+			method: "http",
+			type: "dv",
+			settings: {
+				http2: "on",
+				min_tls_version: "1.2",
+				tls_1_3: "on",
+				early_hints: "on",
 			},
+			bundle_method: "ubiquitous",
+			wildcard: false,
+		},
 	}}
 />
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames"
-  method="GET"
-  parameters={{
-		hostname:"{hostname}"
+	path="/zones/{zone_id}/custom_hostnames"
+	method="GET"
+	parameters={{
+		hostname: "{hostname}",
 	}}
 />
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
-  method="PATCH"
-  json={{
-		"ssl": {
-			"method": "http",
-			"type": "dv",
-			"settings": {
-				"http2": "on", // Note: These settings will be set to default if not included when updating early hints
-				"min_tls_version": "1.2",
-				"tls_1_3": "on",
-				"early_hints": "on"
-				}
+	path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+	method="PATCH"
+	json={{
+		ssl: {
+			method: "http",
+			type: "dv",
+			settings: {
+				http2: "on", // Note: These settings will be set to default if not included when updating early hints
+				min_tls_version: "1.2",
+				tls_1_3: "on",
+				early_hints: "on",
 			},
+		},
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
index 599383a86465771..1f00c930036f700 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
@@ -6,12 +6,11 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
-
 ---
 
 Cloudflare for SaaS allows you to deliver the best performance to your end customers by helping enable you to reduce latency through:
 
-* [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
-* [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
-* [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
-* By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
+- [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
+- [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
+- [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
+- By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
index beee8c46e86d55c..8e173849b2eee87 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-authorities/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
index 66293af0636f89f..0914ddfc956673d 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
index 2e40b6f99d15771..aaeb2fc1941b5f1 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
index c6b4665a4571939..b13a64d43827f6c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-and-hostname-priority/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
index 6b92b6171e4f460..8f572172a0a7569 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Custom Certificate Signing Requests
-
 ---
 
 ## Success codes
@@ -23,33 +22,33 @@ head:
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                        |
-| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                              |
-| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                             |
-| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                           |
-| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                             |
-| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                          |
-| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                      |
-| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                       |
-| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                      |
-| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                             |
-| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&*()=+{}[]                                                                                                                                       |
-| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                        |
-| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                          |
-| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                        |
-| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                  |
-| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                            |
-| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                        |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                       |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                            |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                       |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                           |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                  |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                              |
-| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                   |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                 |
+| ---------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                       |
+| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                          |
+| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                      |
+| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                                      |
+| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                                   |
+| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                               |
+| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                                |
+| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                               |
+| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                                      |
+| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&\*()=+{}[]                                                                                                                                                   |
+| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                 |
+| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                   |
+| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                                 |
+| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                           |
+| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                                     |
+| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                    |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                           |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                       |
+| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                    |
 | 403              | 1404           | Access to generating CSRs has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you. |
-| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                        |
-| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                  |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                |
+| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                 |
+| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                           |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
index e55d19e7fac4ad4..fc889f9bb826a89 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Status codes - Custom hostnames
-
 ---
 
-***
+---
 
 ## Success codes
 
@@ -24,66 +23,66 @@ head:
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | DELETE | 200 OK       |
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | PATCH  | 202 Accepted |
 
-***
+---
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                        |
-| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                 |
-| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                   |
-| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                         |
-| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                            |
-| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                 |
-| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                           |
-| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                            |
-| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                      |
-| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                     |
-| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                            |
-| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                        |
-| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                               |
-| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                     |
-| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                |
-| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                    |
-| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                  |
-| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                            |
-| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                             |
-| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                             |
-| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                             |
-| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                        |
-| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
-| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                   |
-| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                      |
-| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                        |
-| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                            |
-| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                     |
-| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                  |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                      |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                            |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                        |
-| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                |
-| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                           |
-| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid  customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
-| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                              |
-| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                               |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                          |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                          |
+| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                      |
+| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                |
+| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                  |
+| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                        |
+| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                           |
+| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                 |
+| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                |
+| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                          |
+| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                           |
+| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                     |
+| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                           |
+| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                    |
+| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                               |
+| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
+| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                 |
+| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                           |
+| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                            |
+| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                            |
+| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                       |
+| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                               |
+| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                      |
+| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                     |
+| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                       |
+| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                             |
+| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                           |
+| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                    |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                           |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                       |
+| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                               |
+| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                          |
+| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
+| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                             |
+| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                              |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
index 51109dbc3c37bd3..7ecb44f98f46429 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When you perform [TXT](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/) domain control validation, you will need to share these tokens with your customers.
 
@@ -19,8 +18,9 @@ However, these tokens expire after a certain amount of time, depending on your c
 | --------------------- | -------------- |
 | Let's Encrypt         | 7 days         |
 | Google Trust Services | 14 days        |
-| SSL.com | 14 days        |
+| SSL.com               | 14 days        |
 
 :::caution
- <Render file="dcv-invalid-token-situations" product="ssl" />
+
+<Render file="dcv-invalid-token-situations" product="ssl" />
 :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
index 916488e61763006..b13acdc07c26874 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
@@ -32,13 +32,13 @@ Using a [TXT](#dns-txt-record) or [HTTP](#http-token) validation method helps yo
 
 #### DNS TXT Record
 
-When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership\_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
+When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
 
 #### HTTP Token
 
-When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership\_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
+When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
 
-Cloudflare sends GET requests to the http\_url using `User-Agent: Cloudflare Custom Hostname Verification`.
+Cloudflare sends GET requests to the http_url using `User-Agent: Cloudflare Custom Hostname Verification`.
 
 If you validated a hostname that is not proxying traffic through Cloudflare, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app when the HTTP token is verified (under the **Custom Hostnames** tab).
 
@@ -73,10 +73,8 @@ Once the migration has been started for your zone(s), Cloudflare will require ev
 
 :::note
 
-
 You can revert the migration at any time.
 
-
 :::
 
 ### Before the migration
@@ -85,15 +83,15 @@ Before your migration, you should:
 
 1. To test validation methods, set up a test zone and ask your account team to enable SSL for SaaS v2.
 2. Wait for your account team to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
-   * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
-   * `test_active`: Passed CNAME verification
-   * `test_active_apex`: Passed Apex Proxy verification
-   * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
-   * `test_failed`: Failed hostname verification 25 times
+   - `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
+   - `test_active`: Passed CNAME verification
+   - `test_active_apex`: Passed Apex Proxy verification
+   - `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
+   - `test_failed`: Failed hostname verification 25 times
 3. Review the results of our pre-migration tool (run by your account team) using one of the following methods:
-   * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
-   * Via a CSV file (provided by your account team)
-   * Via the Cloudflare dashboard:
+   - Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
+   - Via a CSV file (provided by your account team)
+   - Via the Cloudflare dashboard:
      ![Review SSL migration status in the dashboard](~/assets/images/cloudflare-for-platforms/ssl-migration-status.png)
 4. Approve the migration. Your account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
index edf8ce49e980942..2264ad62fa3dbc5 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Resources for SaaS customers
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare partners with many [SaaS providers](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/) to extend our performance and security benefits to your website.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
index 0681efe793946a6..63c9a0ce28c29a6 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
@@ -30,12 +30,12 @@ This is not an exhaustive list of Cloudflare products and features.
 | [China Network](/china-network/)                                                                    | No            | No                 |                                                                                                                                                                                                                                                                                                                                                                   |
 | [DNS](/dns/)                                                                                        | Yes\*         | Yes                | As a SaaS customer, do not remove the records related to your Cloudflare for SaaS setup.<br/><br/>Otherwise, your traffic will begin routing away from your SaaS provider.                                                                                                                                                                                        |
 | [HTTP/2 prioritization](https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/) | Yes           | Yes\*              | This feature must be enabled on the customer zone to function.                                                                                                                                                                                                                                                                                                    |
-| [Image resizing](/images/optimization/transformations/overview/)                                                         | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Image resizing](/images/optimization/transformations/overview/)                                    | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | IPv6                                                                                                | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [IPv6 Compatibility](/network/ipv6-compatibility/)                                                  | Yes           | Yes\*              | If the customer zone has **IPv6 Compatibility** enabled, generally the SaaS zone should as well.<br/><br/>If not, make sure the SaaS zone enables [Pseudo IPv4](/network/pseudo-ipv4/).                                                                                                                                                                           |
 | [Load Balancing](/load-balancing/)                                                                  | No            | Yes                | Customer zones can still use Load Balancing for non-O2O traffic.                                                                                                                                                                                                                                                                                                  |
 | [Page Rules](/rules/page-rules/)                                                                    | Yes\*         | Yes                | Page Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                                |
-| [Origin Rules](/rules/origin-rules/)                                                                | No           | Yes                |                                                                                                                                                                                                                                       |
+| [Origin Rules](/rules/origin-rules/)                                                                | No            | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Client-side security](/client-side-security/) (formerly Page Shield)                               | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Polish](/images/polish/)                                                                           | Yes\*         | Yes                | Polish only runs on cached assets. If the customer zone is bypassing cache for SaaS zone destined traffic, then images optimized by Polish will not be loaded from origin.                                                                                                                                                                                        |
 | [Rate Limiting](/waf/rate-limiting-rules/)                                                          | Yes\*         | Yes                | Rate Limiting rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
index 8f5c695a4ed8b46..cff52354c33fa79 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
@@ -31,9 +31,9 @@ Webflow customers can enable O2O on any Cloudflare zone plan.
 
 To enable O2O for a specific hostname within a Cloudflare Zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with your Webflow site name as the target. Webflow's domain addition setup will walk you through other validation steps.
 
-| Type    | Name                 | Target                | Proxy status |
-| ------- | -------------------- | --------------------- | ------------ |
-| `CNAME` | `<YOUR_DOMAIN>`      | `cdn.webflow.com`     | Proxied      |
+| Type    | Name            | Target            | Proxy status |
+| ------- | --------------- | ----------------- | ------------ |
+| `CNAME` | `<YOUR_DOMAIN>` | `cdn.webflow.com` | Proxied      |
 
 ## Zone hold
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
index 5f503f70abb253c..38885b976200c1e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
index 541ee92bd1ce3a3..335795eba693675 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Manage custom certificates
-
 ---
 
-import { Render, TabItem, Tabs } from "~/components"
+import { Render, TabItem, Tabs } from "~/components";
 
 Learn how to manage custom certificates for your Cloudflare for SaaS custom hostnames. For use cases and limitations, refer to [custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/).
 
@@ -86,7 +85,7 @@ To replace a single custom certificate within a certificate pack that contains t
 
 You can only replace an RSA certificate with another RSA certificate, or an ECDSA certificate with another ECDSA certificate.
 
-***
+---
 
 ## Move to a Cloudflare certificate
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
index 4a1ffdb4234511d..3b173935c952ce9 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
@@ -11,16 +11,15 @@ sidebar:
 head:
   - tag: title
     content: Delegated domain control validation (DCV)
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Delegated DCV allows SaaS providers to delegate the DCV process to Cloudflare.
 
 DCV Delegation requires your customers to place a one-time record at their authoritative DNS that allows Cloudflare to auto-renew all future certificate orders, so that there is no manual intervention from you or your customers at the time of the renewal.
 
-***
+---
 
 ## Setup
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
index 60f518c1628966e..e4cb716dca2b5d4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting | Certificate validation
-
 ---
 
 ## High-risk domains
@@ -20,7 +19,7 @@ Occasionally, a domain will be flagged as “high risk” by Cloudflare’s CA p
 
 If a domain is flagged by the CA, you need to contact Support before validation can finish. The API call will return indicating the failure, along with a link to where the ticket can be filed.
 
-***
+---
 
 ## Certificate Authority Authorization (CAA) records
 
@@ -44,26 +43,26 @@ In some cases, the validation may be prevented because your hostname points to a
 
 In this case you would need to either select a Certificate Authority whose CAA records are present at the target, or review the configuration with the service provider that owns the target.
 
-***
+---
 
 ## Time outs
 
 If a certificate issuance times out, the error message will indicate where the timeout occurred:
 
-* Timed Out (Initializing)
-* Timed Out (Validation)
-* Timed Out (Issuance)
-* Timed Out (Deployment)
-* Timed Out (Deletion)
+- Timed Out (Initializing)
+- Timed Out (Validation)
+- Timed Out (Issuance)
+- Timed Out (Deployment)
+- Timed Out (Deletion)
 
 To fix this error, send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) through the API or select **Refresh** for the specific custom hostname in the dashboard. If using the API, make sure that the `--data` field contains an `ssl` object with the same `method` and `type` as the original request.
 
 If these return an error, delete and recreate the custom hostname.
 
-***
+---
 
 ## Immediate validation checks
 
 You can send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) to request an immediate validation check on any certificate. The PATCH data should include the same `ssl` object as the original request.
 
-***
+---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
index 3545c355b84844b..7ac9fd652e89438 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 5
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 When you [create a webhook notification](/notifications/get-started/configure-webhooks/) for **SSL for SaaS Custom Hostnames**, you may want to automate responses to specific events (certificate issuance, failed validation, etc.).
 
@@ -26,38 +26,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.validation.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.validation.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -67,49 +67,49 @@ Cloudflare sends this alert each time a certificate remains in a `pending_valida
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.validation.failed",
-      "created_at": "2018-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_validation",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "blog.example.com reported as potential risk: google_safe_browsing"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.validation.failed",
+			"created_at": "2018-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_validation",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "blog.example.com reported as potential risk: google_safe_browsing"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate issuance
 
@@ -121,38 +121,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.issuance.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.issuance.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -162,49 +162,49 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.issuance.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "caa_error: blog.example.com"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.issuance.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "caa_error: blog.example.com"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate deployment
 
@@ -216,38 +216,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_dep
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deployment.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "active",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deployment.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "active",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -257,42 +257,42 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deployment.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deployment.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate deletion
 
@@ -302,34 +302,34 @@ Cloudflare sends this alert when certificates move from a status of `pending_del
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deletion.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "deleted"
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deletion.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "deleted"
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -339,38 +339,38 @@ Cloudflare sends this alert each time a certificate remains in status of `pendin
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deletion.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deletion"
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deletion.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deletion"
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate renewal
 
@@ -382,43 +382,43 @@ The actions that you need to perform to renew certificates depend on your [valid
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "status": "active",
-      "hosts": ["blog.example.com"],
-      "issuer": "DigiCertInc",
-      "serial_number": "1001172778337169491",
-      "signature": "ECDSAWithSHA256",
-      "uploaded_on": "2021-11-17T04:33:54.561747Z",
-      "expires_on": "2022-11-21T12:00:00Z",
-      "custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"status": "active",
+			"hosts": ["blog.example.com"],
+			"issuer": "DigiCertInc",
+			"serial_number": "1001172778337169491",
+			"signature": "ECDSAWithSHA256",
+			"uploaded_on": "2021-11-17T04:33:54.561747Z",
+			"expires_on": "2022-11-21T12:00:00Z",
+			"custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -428,38 +428,38 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -469,45 +469,45 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "caa_error: blog.example.com"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "caa_error: blog.example.com"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -521,6 +521,9 @@ This behavior is because each custom hostname can only have one certificate atta
 
 You can configure alerts to receive notifications for changes in your custom hostname certificates.
 
-<AvailableNotifications product="SSL/TLS" notificationFilter="SSL for SaaS Custom Hostnames Alert" />
+<AvailableNotifications
+	product="SSL/TLS"
+	notificationFilter="SSL for SaaS Custom Hostnames Alert"
+/>
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
index 79e692861ae83d3..dad31a4c49f6b78 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
@@ -6,13 +6,12 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Cloudflare for SaaS provides increased security per custom hostname through:
 
-* [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
-  * [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
-  * [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
-* Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
-* Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
+- [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
+  - [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
+  - [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
+- Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
+- Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
index a9b88bc6d3f027e..8c044e098c1a507 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
@@ -9,7 +9,7 @@ sidebar:
   label: Setup
 ---
 
-import { DashButton, APIRequest, } from "~/components";
+import { DashButton, APIRequest } from "~/components";
 
 [Web Application Firewall (WAF)](/waf/) allows you to create additional security measures through Cloudflare. As a SaaS provider, you can link custom rules, rate limiting rules, and managed rules to your custom hostnames. This provides more control to keep your domains safe from malicious traffic.
 
@@ -74,40 +74,38 @@ This assigns custom metadata to your custom hostname so that it has a security t
 2. Build your rules either [through the dashboard](/waf/custom-rules/create-dashboard/) or via the API. An example rate limiting rule, corresponding to `"security_level"` low, is shown below as an API call.
 
 <APIRequest
-  path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
-  method="PUT"
-  json={{
-		"rules": [
+	path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
+	method="PUT"
+	json={{
+		rules: [
 			{
-				"action": "block",
-				"ratelimit": {
-					"characteristics": [
-						"cf.colo.id",
-						"ip.src"
-					],
-					"period": 10,
-					"requests_per_period": 2,
-					"mitigation_timeout": 60
+				action: "block",
+				ratelimit: {
+					characteristics: ["cf.colo.id", "ip.src"],
+					period: 10,
+					requests_per_period: 2,
+					mitigation_timeout: 60,
 				},
-				"expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
-			}
-		]
+				expression:
+					'lookup_json_string(cf.hostname.metadata, "security_level") eq "low" and http.request.uri contains "login"',
+			},
+		],
 	}}
 	parameters={{
-		ruleset_phase: "http_ratelimit"
+		ruleset_phase: "http_ratelimit",
 	}}
 />
 
 To build rules through the dashboard:
 
-1. In the Cloudflare dashboard, go to the **WAF** page.
+1.  In the Cloudflare dashboard, go to the **WAF** page.
 
-		<DashButton url="/?to=/:account/application-security/waf" />
+        <DashButton url="/?to=/:account/application-security/waf" />
 
-2. Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
+2.  Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
 
-3. Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
+3.  Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
 
-   :::caution
-   This API call will replace any existing rate limiting rules in the zone.
-   :::
+    :::caution
+    This API call will replace any existing rate limiting rules in the zone.
+    :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
index 5f74db1bcc4eac2..44166be7219fb59 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /data-localization/how-to/cloudflare-for-saas/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
index b3bba3fd7a2c5ea..e385caf0bc3f783 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
@@ -55,9 +55,9 @@ You do not need to add individual Worker routes for each custom hostname. The wi
 
      For example, if your zone is `saasprovider.com` and you want `api.saasprovider.com` to bypass the Worker, create an additional route `api.saasprovider.com/*` with no Worker assigned. More specific routes take precedence over wildcard routes.
 
-    - **Route only custom hostname traffic to the Worker**:
-     - **Route**: `vanity.customer.com`
-     - **Worker**: Select the Worker used for your SaaS application.
+   - **Route only custom hostname traffic to the Worker**:
+   - **Route**: `vanity.customer.com`
+   - **Worker**: Select the Worker used for your SaaS application.
 
 5. Click **Save**.
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
index b5e1b4537b932f3..7c32801c1a98fdd 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
@@ -9,11 +9,13 @@ sidebar:
 products:
   - cloudflare-for-platforms
 ---
+
 import { Aside } from "@astrojs/starlight/components";
 
 When you deploy User Workers through Workers for Platforms, you can attach [bindings](/workers/runtime-apis/bindings/) to give them access to resources like [KV namespaces](/kv/), [D1 databases](/d1/), [R2 buckets](/r2/), and more. This enables your end customers to build more powerful applications without you having to build the infrastructure components yourself.
 
 With bindings, each of your users can have their own:
+
 - [KV namespace](/kv/) that they can use to store and retrieve data
 - [R2 bucket](/r2/) that they can use to store files and assets
 - [Analytics Engine](/analytics/analytics-engine/) dataset that they can use to collect observability data
@@ -26,9 +28,11 @@ Each User Worker can only access the bindings that are explicitly attached to it
 ![Resource Isolation Model](~/assets/images/reference-architecture/programmable-platforms/programmable-platforms-5.svg "Resource Isolation Model")
 
 ## Adding a KV Namespace to a User Worker
+
 This example walks through how to create a [KV namespace](/kv/) and attach it to a User Worker. The same process can be used to attach to other [bindings](/workers/runtime-apis/bindings/).
 
 ### 1. Create a KV namespace
+
 Create a KV namespace using the [Cloudflare API](/api/resources/kv/subresources/namespaces/methods/bulk_update/).
 
 ### 2. Attach the KV namespace to the User Worker
@@ -58,6 +62,7 @@ curl -X PUT \
   }' \
   -F 'worker.js=@/path/to/worker.js'
 ```
+
 Now, the User Worker has can access the `USER_KV` binding through the `env` argument using `env.USER_DATA.get()`, `env.USER_DATA.put()`, and other KV methods.
 
 Note: If you plan to add new bindings to the Worker, use the `keep_bindings` parameter to ensure existing bindings are preserved while adding new ones.
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
index 6a9982c4fc08bc4..9cdf87f9fd91826 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
@@ -31,7 +31,7 @@ A [Tail Worker](/workers/observability/logs/tail-workers/) receives information
 
 Use [Tail Workers](/workers/observability/logs/tail-workers/) instead of Logpush if you want granular control over formatting before logs are sent to their destination to receive [diagnostics channel events](/workers/runtime-apis/nodejs/diagnostics-channel), or if you want logs delivered in real-time.
 
-Adding a Tail Worker to  your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
+Adding a Tail Worker to your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
 
 ## Analytics
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
index b5f72ee55754ce1..a5d3d76bafe414b 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-for-platforms
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Script limits
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
index 4ed59262b2ebb15..c7998ff2541bb30 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
@@ -18,7 +18,7 @@ import {
 	ResourcesBySelector,
 } from "~/components";
 
-The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically. 
+The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically.
 
 ### Prerequisites
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
index 378810ebff4dd3e..4842b92536a2d6c 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
@@ -18,11 +18,11 @@ In untrusted mode:
 - Each Worker has an isolated cache, when using the [Cache API](/workers/runtime-apis/cache/) or when making subrequests using `fetch()`, which egress via [Cloudflare's cache](/cache/)
 - [`caches.default`](/workers/reference/how-the-cache-works/#cache-api) is disabled for all Workers in the namespace
 
-This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access. 
+This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access.
 
 ### Trusted Mode
 
-If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code. 
+If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code.
 
 In trusted mode:
 
@@ -31,9 +31,10 @@ In trusted mode:
 
 :::note
 In trusted mode, Workers can potentially access cached responses from other Workers in the namespace. Only enable this if you control all Worker code or have appropriate cache key isolation strategies.
-::: 
+:::
 
 To convert a namespace from untrusted to trusted:
+
 ```bash
 curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace_name}" \
   -H "Authorization: Bearer {api_token}" \
@@ -42,14 +43,16 @@ curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/
     "name": "{namespace_name}",
     "trusted_workers": true
   }'
-  ```
+```
 
-If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it. 
+If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it.
 
 ### Maintaining cache isolation in trusted mode
-If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
+
+If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys.
 
 ## Related Resources
-* [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
-* [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
-* [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
\ No newline at end of file
+
+- [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
+- [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
+- [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
diff --git a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
index 1d4db0fb3f37d82..c2bc163fbb4b639 100644
--- a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
+++ b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
@@ -12,7 +12,6 @@ sidebar:
 head:
   - tag: title
     content: Minimal suggested ruleset
-
 ---
 
 The suggested minimal ruleset blocks some known common vectors for DDoS attacks and permits all other ESP, TCP, UDP, GRE and ICMP traffic.
@@ -66,17 +65,17 @@ The information below covers traffic type, how the port is used, and reasons for
 
 The list below is a common list of traffic types you should also consider blocking or restricting inbound.
 
-* SFTP, TFTP
-* SSH, Telnet
-* RDP
-* RCP
-* SMCP
-* NTP
-  * Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
-* MS-SQL
-  * Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
-* HTTP and HTTPS
-  * If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
+- SFTP, TFTP
+- SSH, Telnet
+- RDP
+- RCP
+- SMCP
+- NTP
+  - Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
+- MS-SQL
+  - Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
+- HTTP and HTTPS
+  - If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
 
 If relevant to your environment, consider blocking based on geolocation data, which blocks traffic based on the country or user when an end user's IP address is registered in the geolocation database.
 
diff --git a/src/content/docs/cloudflare-network-firewall/index.mdx b/src/content/docs/cloudflare-network-firewall/index.mdx
index f5c445fd27e1de4..f546e7f0e9b2faa 100644
--- a/src/content/docs/cloudflare-network-firewall/index.mdx
+++ b/src/content/docs/cloudflare-network-firewall/index.mdx
@@ -20,8 +20,8 @@ import {
 } from "~/components";
 
 <Description>
-	Filter and block unwanted traffic at Cloudflare's global network,
-	before it reaches your infrastructure.
+	Filter and block unwanted traffic at Cloudflare's global network, before it
+	reaches your infrastructure.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
index 70c21d97f76d65a..53c0015446461f2 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
@@ -304,4 +304,4 @@ Due to the nature of Cloudflare network, your traffic may traverse various physi
 
 - Multiple PCAP Files: A single full PCAP capture may produce many small PCAP files, as a capture is taken for each physical server your traffic traverses in a Cloudflare location.
   - You can get more granular by applying packet-specific filters like protocol, port (and more) to target the traffic you need.
-- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
\ No newline at end of file
+- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
index 6f7330a2abce626..2ee588985ab4a4f 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
@@ -174,7 +174,7 @@ To start collecting packet captures with R2, you first need to configure it prop
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-	<DashButton url="/?to=/:account/r2/overview" />
+   <DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -218,4 +218,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
diff --git a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
index 190cc5e6da18dfa..1833bff8925d2c5 100644
--- a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
+++ b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
@@ -21,9 +21,9 @@ Traffic passing through Cloudflare's network is evaluated by several independent
 Each system operates independently. Traffic blocked by an earlier system never reaches later systems for evaluation.
 
 :::caution
-	Creating an allow rule in Network Firewall does **not** bypass DDoS
-	protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
-	rules, you must configure bypasses in those systems separately.
+Creating an allow rule in Network Firewall does **not** bypass DDoS
+protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
+rules, you must configure bypasses in those systems separately.
 :::
 
 To diagnose blocked traffic, use [Network Analytics](/analytics/network-analytics/) to identify which system is blocking the traffic and why. If Network Analytics does not provide enough information, you can use packet captures for deeper analysis.
@@ -99,4 +99,4 @@ If you cannot identify the issue from Network Analytics, use [packet captures](/
 - [Network Analytics](/analytics/network-analytics/)
 - [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/)
 - [Network Firewall rule configuration](/cloudflare-network-firewall/how-to/add-policies/)
-- [Packet captures](/cloudflare-network-firewall/packet-captures/)
\ No newline at end of file
+- [Packet captures](/cloudflare-network-firewall/packet-captures/)
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
index 24eaf60c6cf1b66..3b09b3e2ad4da6e 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
index db274e1c338cdc3..69fc5cb5e2e1111 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
@@ -7,7 +7,7 @@ title: Require Access protection
 sidebar:
   order: 3
 tags:
-- Security
+  - Security
 ---
 
 Cloudflare Access allows you to require Access protection for all hostnames in your account. When this setting is turned on, traffic to any hostname without a matching [Access application](/cloudflare-one/access-controls/applications/) is automatically blocked.
@@ -23,13 +23,13 @@ Turning on Access protection blocks traffic to any hostname that does not have a
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **Zero Trust** > **Access controls** > **Access settings**.
 2. Turn on **Block traffic to all domains in this account**. You will see a dialog confirming you understand the scope of this change. Select **Confirm**.
 
-	Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
+   Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
 
 3. (Optional) Under **Hostnames to Exempt**, select specific domains to exempt from the **Block traffic to all domains in this account** setting. Traffic to exempted hostnames is allowed even if no Access application exists.
 
-	:::note
-	Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
-	:::
+   :::note
+   Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
+   :::
 
 ## Allow traffic to a hostname
 
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
index d5cc04f026c092a..d74a4f8adf061e0 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
@@ -100,6 +100,7 @@ Users who match a policy configured with a _Same as application session timeout_
 When [Authenticate with Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/#configure-client-sessions-in-access) is enabled for an Access application, the Cloudflare One Client session duration takes precedence over all other session durations (application, policy, and global). As long as the Cloudflare One Client session is valid and the user is running the Cloudflare One Client, the user will not be prompted to re-authenticate with the IdP — even if the global session has expired.
 
 ### MFA session duration
+
 If you use [independent multi-factor authentication (MFA)](/cloudflare-one/access-controls/access-settings/independent-mfa/), the MFA session duration determines how long a user can log in to Cloudflare Access without being prompted for MFA. The MFA session is independent of the global, policy, and application session durations. When logging in to an Access app with [MFA enabled](/cloudflare-one/access-controls/policies/mfa-requirements/#configure-independent-mfa-for-an-application), users must complete an MFA challenge if their last MFA authentication falls outside the configured session duration. After authenticating with their identity provider, users are prompted for MFA. The [`CF_Device` cookie](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#cf_device) ensures both authentication steps occur on the same device. MFA session durations do not affect how long a user has access to the application (that is controlled by the [application token](#session-durations)).
 
 ### Order of enforcement
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
index 603b94d330906d6..f387963685b0849 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
index cfff5ab05a7f8ee..f4dd978b1db79a4 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
@@ -179,9 +179,9 @@ You can assign aliases to tools to give them clearer names in the portal. Aliase
 
 Aliases can be set at two levels:
 
-| Level | Field | Scope |
-| ----- | ----- | ----- |
-| **Server-level** | `alias` | Applies to the tool across all portals that include this server |
+| Level            | Field          | Scope                                                                                   |
+| ---------------- | -------------- | --------------------------------------------------------------------------------------- |
+| **Server-level** | `alias`        | Applies to the tool across all portals that include this server                         |
 | **Portal-level** | `portal_alias` | Applies only within this specific portal and takes priority over the server-level alias |
 
 When a tool has multiple names configured, the portal uses the following priority order: `portal_alias` > `server_alias` > `alias` > original tool name.
@@ -245,11 +245,11 @@ Unlike the dashboard, the API does not automatically create a DNS record for you
 
 The `auth_type` field accepts the following values:
 
-| Value | Description |
-| ----- | ----------- |
-| `oauth` | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
-| `bearer` | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`. |
-| `unauthenticated` | The server does not require authentication. |
+| Value             | Description                                                                                                                                          |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `oauth`           | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
+| `bearer`          | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`.                                                   |
+| `unauthenticated` | The server does not require authentication.                                                                                                          |
 
 ### Force sync an MCP server
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
index b342006708c137a..8b12f3259058db0 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
@@ -57,18 +57,18 @@ The payload contains the actual claim and user information to pass to the applic
 }
 ```
 
-| Field          | Description                                                                                                                                                                                                                                                                                     |
-| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                                    |
-| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                 |
-| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                             |
-| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                               |
-| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                           |
-| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                           |
-| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                       |
-| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                  |
+| Field          | Description                                                                                                                                                                                                                                                                                               |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                |
+| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                           |
+| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                                       |
+| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                                         |
+| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                                     |
+| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                                     |
+| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                                 |
+| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                            |
 | sub            | The ID of the user. This value is unique to an email address per account. The user would get a different `sub` if they are [removed](/cloudflare-one/team-and-resources/users/seat-management/#remove-a-user) and re-added to your Zero Trust organization, or if they log into a different organization. |
-| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                  |
+| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                            |
 
 #### Custom SAML attributes and OIDC claims
 
@@ -86,26 +86,26 @@ curl -H 'cookie: CF_Authorization=<user-token>' https://<your-team-name>.cloudfl
 
 Access will return a JSON structure containing the following data:
 
-| Field                | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| email                | The email address of the user.                                              |
-| idp                  | Data from your identity provider.                                           |
-| geo                  | The country where the user authenticated from.                              |
-| user_uuid            | The ID of the user.                                                         |
-| devicePosture        | The device posture attributes.                                              |
-| account_id           | The account ID for your organization.                                       |
-| iat                  | The timestamp indicating when the user logged in.                           |
-| ip                   | The IP address of the user.                                                 |
-| auth_status          | The status if authenticating with mTLS.                                     |
-| common_name          | The common name on the mTLS client certificate.                             |
-| service_token_id     | The Client ID of the service token used for authentication.                 |
-| service_token_status | True if authentication was through a service token instead of an IdP.       |
-| is_warp              | True if the user enabled WARP.                                              |
-| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team.       |
-| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team. |
-| device_id            | The ID of the device used for authentication.                               |
-| version              | The version of the `get-identity` object.                                   |
-| device_sessions      | A list of all sessions initiated by the user.                               |
+| Field                | Description                                                                                |
+| -------------------- | ------------------------------------------------------------------------------------------ |
+| email                | The email address of the user.                                                             |
+| idp                  | Data from your identity provider.                                                          |
+| geo                  | The country where the user authenticated from.                                             |
+| user_uuid            | The ID of the user.                                                                        |
+| devicePosture        | The device posture attributes.                                                             |
+| account_id           | The account ID for your organization.                                                      |
+| iat                  | The timestamp indicating when the user logged in.                                          |
+| ip                   | The IP address of the user.                                                                |
+| auth_status          | The status if authenticating with mTLS.                                                    |
+| common_name          | The common name on the mTLS client certificate.                                            |
+| service_token_id     | The Client ID of the service token used for authentication.                                |
+| service_token_status | True if authentication was through a service token instead of an IdP.                      |
+| is_warp              | True if the user enabled WARP.                                                             |
+| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team. |
+| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team.      |
+| device_id            | The ID of the device used for authentication.                                              |
+| version              | The version of the `get-identity` object.                                                  |
+| device_sessions      | A list of all sessions initiated by the user.                                              |
 
 ### Service token authentication
 
@@ -121,15 +121,15 @@ Access will return a JSON structure containing the following data:
 }
 ```
 
-| Field       | Description                                                                                                                                      |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| type        | The type of Access token (`app` for application token or `org` for global session token).                                                        |
+| Field       | Description                                                                                                                                                                    |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| type        | The type of Access token (`app` for application token or `org` for global session token).                                                                                      |
 | aud         | The [application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application. |
-| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                 |
-| iss         | The Cloudflare Access domain URL for the application.                                                                                            |
-| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                      |
-| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                   |
-| sub         | Contains an empty string when authentication was through a service token.                                                                        |
+| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                                               |
+| iss         | The Cloudflare Access domain URL for the application.                                                                                                                          |
+| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                                                    |
+| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                                                 |
+| sub         | Contains an empty string when authentication was through a service token.                                                                                                      |
 
 ## Signature
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
index 6ac256251bea1e9..3917b42fff99c6f 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
@@ -197,7 +197,10 @@ export default {
 		const newRequest = new Request(url.toString(), request);
 
 		newRequest.headers.set("cf-access-client-id", env.CF_ACCESS_CLIENT_ID);
-		newRequest.headers.set("cf-access-client-secret", env.CF_ACCESS_CLIENT_SECRET);
+		newRequest.headers.set(
+			"cf-access-client-secret",
+			env.CF_ACCESS_CLIENT_SECRET,
+		);
 		try {
 			const response = await fetch(newRequest);
 
@@ -227,7 +230,7 @@ npx wrangler deploy
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.
 
-	<DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select your newly created Worker.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
index 5b1182c9666a6e2..03576d37f7ff815 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
@@ -188,13 +188,13 @@ The authorization flow proceeds as follows:
 
 Both managed OAuth and [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) allow non-browser clients to authenticate with Access-protected applications, but they serve different use cases:
 
-| | Managed OAuth | Service tokens |
-| --- | --- | --- |
-| **Authentication model** | User-based — the end user logs in through their identity provider | Machine-based — a shared secret authenticates the service itself |
-| **Best for** | Interactive CLI tools, AI agents, SDKs where a human initiates the request | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication |
-| **User identity** | Access knows which user made the request | No user identity — requests are attributed to the service token |
-| **Policy enforcement** | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
-| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials | Requires distributing and rotating Client ID and Client Secret |
+|                           | Managed OAuth                                                                    | Service tokens                                                                                  |
+| ------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **Authentication model**  | User-based — the end user logs in through their identity provider                | Machine-based — a shared secret authenticates the service itself                                |
+| **Best for**              | Interactive CLI tools, AI agents, SDKs where a human initiates the request       | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication             |
+| **User identity**         | Access knows which user made the request                                         | No user identity — requests are attributed to the service token                                 |
+| **Policy enforcement**    | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
+| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials  | Requires distributing and rotating Client ID and Client Secret                                  |
 
 Use managed OAuth when you want non-browser clients to authenticate users the same way a browser would — the user logs in once, and the client receives an OAuth token to make requests on their behalf.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
index 52fef67da2246a1..cadc87d1fda6ab5 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
@@ -59,12 +59,15 @@ Some SaaS applications provide the Redirect URL after you [configure the SSO pro
 
 11. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-12. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "saas" }}/>
+12. <Render
+    	file="access/access-choose-idps"
+    	product="cloudflare-one"
+    	params={{ appType: "saas" }}
+    />
 
 13. (Optional) Go to **Additional settings** to customize the application experience:
-
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
-	- <Render file="access/access-block-page" product="cloudflare-one" />
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
+    - <Render file="access/access-block-page" product="cloudflare-one" />
 
 14. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
index c554be332b64448..cee76077b2de270 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-- SSO
+  - SSO
 ---
 
 This guide covers how to configure [Grafana Cloud](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/authorization/#configure-oauth-20-with-generic-oauth) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
index b7a904dc94c5681..c343d9ad68ce913 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-- SSO
+  - SSO
 ---
 
 This guide covers how to configure [Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
index 3118fcac0cec9c2..01dc8bf2c1ccd20 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
@@ -6,10 +6,9 @@ products:
 title: SaaS applications
 sidebar:
   order: 1
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare Access allows you to add an additional authentication layer to your SaaS applications. When you integrate a SaaS application with Access, users log in to the application with Cloudflare as the Single Sign-On provider. The user is then redirected to the configured identity providers for that application and are only granted access if they pass your Access policies.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
index ae83f5143d310dc..2cfa346e15fc6c3 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
@@ -7,8 +7,8 @@ title: Browser-rendered terminal
 sidebar:
   order: 3
 tags:
-- SSH
-- RDP
+  - SSH
+  - RDP
 ---
 
 import { Render } from "~/components";
@@ -31,7 +31,10 @@ To turn on browser rendering for an SSH or VNC application:
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/). Select **Configure**.
 3. Turn on **Allow access through browser-based RDP, SSH, or VNC sessions**, then select _SSH_ or _VNC_.
-	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
+   <Render
+   	file="access/self-hosted-app/browser-rendering-policies"
+   	product="cloudflare-one"
+   />
 4. Select **Save**.
 
 When users authenticate and visit the URL of the application, Cloudflare will render a terminal in their browser.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
index e0badb2c31fe6c0..203505a89c9fa0e 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
@@ -7,8 +7,8 @@ title: Arbitrary TCP
 sidebar:
   order: 11
 tags:
-- TCP
-- SSH
+  - TCP
+  - SSH
 ---
 
 Cloudflare Access provides a mechanism for end users to authenticate with their single sign-on (SSO) provider and connect to resources over arbitrary TCP without being on a virtual private network (VPN).
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
index 0e09be8ca535069..242e714857c5c7a 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
@@ -7,7 +7,7 @@ title: Enable automatic cloudflared authentication
 sidebar:
   order: 2
 tags:
-- Authentication
+  - Authentication
 ---
 
 When users connect to an Access application through `cloudflared`, the browser prompts them to allow access by displaying this page:
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
index 2f0c700b0197311..7b753f951aa5916 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
   label: Private network applications (legacy)
 tags:
-- Private networks
+  - Private networks
 ---
 
 :::caution
@@ -35,7 +35,6 @@ Existing **Private Network** applications continue to function and can still be
 7. Select **Next**. You will see two auto-generated Gateway Network policies: one that allows access to the destination IP and another that blocks access.
 
 8. Modify the policies to include additional identity-based conditions. For example:
-
    - **Policy 1**
 
      | Selector       | Operator      | Value            | Logic | Action |
@@ -53,4 +52,4 @@ Existing **Private Network** applications continue to function and can still be
 
 9. Select **Add application**.
 
-Your application will appear on the **Applications** page.
\ No newline at end of file
+Your application will appear on the **Applications** page.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
index 00a20e37e19d6cb..4b7341a9ec0afcb 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
@@ -11,7 +11,7 @@ sidebar:
   label: Add a self-hosted private application
 ---
 
-import { Render, GlossaryTooltip, } from "~/components";
+import { Render, GlossaryTooltip } from "~/components";
 
 You can configure a self-hosted Access application to manage access to specific IPs or hostnames on your private network.
 
@@ -28,54 +28,59 @@ This feature replaces the legacy [private network app type](/cloudflare-one/acce
 
 ## Add your application to Access
 
-1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+1.  In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
-2. Select **Create new application**.
+2.  Select **Create new application**.
 
-3. Select **Self-hosted and private**.
+3.  Select **Self-hosted and private**.
 
-4.  To add an application using its private IP:
-		1. Select **Add private IP**.
-		2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`).
-		3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+4.  To add an application using its private IP: 1. Select **Add private IP**. 2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`). 3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-			Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
+        	Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
 
-5. To add an application using its private hostname:
-	1. Select **Add private hostname**.
-	2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
-	3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+5.  To add an application using its private hostname:
+    1. Select **Add private hostname**.
+    2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
+    3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-	:::note
-	- **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
-	- **Non-HTTPS applications**:  Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
+    :::note
+    - **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
+    - **Non-HTTPS applications**: Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
 
-		<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one"/>
+      <Render
+      	file="gateway/egress-selector-cgnat-ips"
+      	product="cloudflare-one"
+      />
 
-		For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
+      For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
 
 6.  <Render file="access/add-access-policies" product="cloudflare-one" />
-7.  <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "private" }}/>
+7.  <Render
+    	file="access/access-choose-idps"
+    	product="cloudflare-one"
+    	params={{ appType: "private" }}
+    />
 
-8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
+8.  <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
-9. <Render file="access/session-duration" product="cloudflare-one" />
+9.  <Render file="access/session-duration" product="cloudflare-one" />
 
-   If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
+    If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+    - **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
 
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	- **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
-
-		:::note
-		Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
-		:::
-
-	- <Render file="access/access-block-page" product="cloudflare-one" />
-	- The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
-		<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
+      :::note
+      Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
+      :::
 
+    - <Render file="access/access-block-page" product="cloudflare-one" />
+    - The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
+      <Render
+      	file="access/self-hosted-app/advanced-settings"
+      	product="cloudflare-one"
+      />
 
 11. Select **Create**.
 
@@ -113,8 +118,11 @@ An Access application defined by a private hostname takes precedence over an Acc
 
 ### Browser Isolation is not compatible with apps on non-`443` ports
 
-<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
+<Render
+	file="access/self-hosted-app/browser-isolation-non-443"
+	product="cloudflare-one"
+/>
 
 ### Google Chrome restricts access to private hostnames
 
-<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one"/>
+<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
index 3dfe9164a038ef3..2de16fa32411bf7 100644
--- a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Available Access events
 
-<Render file="event-subscriptions/access-events" product="queues" />
\ No newline at end of file
+<Render file="event-subscriptions/access-events" product="queues" />
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
index 1c0b4d46c3a4704..899ed27993f86f3 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
@@ -6,7 +6,6 @@ products:
 title: Application paths
 sidebar:
   order: 5
-
 ---
 
 Application paths define the URLs protected by an Access policy. When adding a self-hosted application to Access, you can choose to protect the entire website by entering its apex domain, or alternatively, protect specific subdomains and paths.
@@ -27,9 +26,9 @@ When you create an application for a specific subdomain or path, you can use ast
 
 A wildcard in the **Subdomain** field only matches that specific subdomain level. It does not cover the apex domain or multiple levels of the subdomain. If you want to cover multiple subdomain levels, you can use multiple wildcards.
 
-| Application     | Covers                                       | Does not cover |
-| --------------- | -------------------------------------------- | -------------- |
-| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com`  |
+| Application     | Covers                                       | Does not cover                            |
+| --------------- | -------------------------------------------- | ----------------------------------------- |
+| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com` |
 
 #### Match all paths of an apex domain
 
@@ -43,9 +42,9 @@ To protect an apex domain and all of the paths under it, leave the **Path** fiel
 
 Using a wildcard in the **Subdomain** field does not cover the parent subdomain nor the apex domain.
 
-| Application          | Covers                                                 | Does not cover                          |
-| -------------------- | ------------------------------------------------------ | --------------------------------------- |
-| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com`  <br/> `example.com` |
+| Application          | Covers                                                 | Does not cover                         |
+| -------------------- | ------------------------------------------------------ | -------------------------------------- |
+| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com` <br/> `example.com` |
 
 #### Partially match subdomains
 
@@ -73,8 +72,8 @@ Using a wildcard in the middle of the **Path** field covers multiple segments of
 
 ### Limitations
 
-* At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
-* At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
+- At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
+- At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
 
 ## Subdomain setups
 
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
index c8ec944860e8d4b..e08ee885d64e235 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
@@ -145,29 +145,29 @@ When you add a rule to your Cloudflare Access policy, you will be asked to speci
 
 Non-identity attributes are polled continuously, meaning they are evaluated with each new HTTP request for changes during the [user session](/cloudflare-one/access-controls/access-settings/session-management/). If you have configured [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/), you can force a user to re-attest all attributes with Access whenever you revoke the user in the IdP or update their IdP group membership.
 
-| Selector                 | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
-| Emails                   | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Emails ending in         | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
-| External Evaluation      | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
-| IP ranges                | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
-| Country                  | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
-| Everyone                 | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
-| Common Name              | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
-| Valid Certificate        | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Service Token            | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Any Access Service Token | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
-| User Risk Score          | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
-| Linked App Token         | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                   | ✅               | ✅                               | ❌                       |
-| Login Methods            | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
-| Authentication Method    | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
-| Identity provider group  | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
-| SAML Group               | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
-| OIDC Claim               | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Device posture           | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
-| Warp                     | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
-| Gateway                  | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
-| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                                | ✅               | ❌                               | ✅                       |
+| Selector                  | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
+| Emails                    | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Emails ending in          | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
+| External Evaluation       | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
+| IP ranges                 | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
+| Country                   | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
+| Everyone                  | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
+| Common Name               | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
+| Valid Certificate         | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Service Token             | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Any Access Service Token  | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
+| User Risk Score           | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
+| Linked App Token          | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                      | ✅               | ✅                               | ❌                       |
+| Login Methods             | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
+| Authentication Method     | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
+| Identity provider group   | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
+| SAML Group                | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
+| OIDC Claim                | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Device posture            | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
+| Warp                      | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
+| Gateway                   | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
+| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                               | ✅               | ❌                               | ✅                       |
 
 <sup>1</sup> For SaaS applications, Access can only enforce policies at the time
 of initial sign on and when reissuing the SaaS session. Once the user has
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
index 7213c910db20077..11eeaa22045b223 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
@@ -54,7 +54,7 @@ To delete a reusable Access policy:
 
 ## Test your policies
 
-You can test your Access policies against all existing user identities in your Zero Trust organization.  For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
+You can test your Access policies against all existing user identities in your Zero Trust organization. For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
 
 Cloudflare will use the most recent device that was authenticated with Access to test your policies.
 
@@ -76,25 +76,22 @@ You can test your Access application policies against your user population befor
 
 To test if users have access to an application:
 
-1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
-2. Locate the application you want to test and select **Configure**.
-3. Go to **Policies** > **Policy tester**.
-4. To test all active users in your organization, select **Test policies**.
+1.  In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+2.  Locate the application you want to test and select **Configure**.
+3.  Go to **Policies** > **Policy tester**.
+4.  To test all active users in your organization, select **Test policies**.
 
-		The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
+        The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
 
-5. To perform a detailed test on a single user:
+5.  To perform a detailed test on a single user:
 
-	a. If you made any changes to your policies, first save the application.
+    a. If you made any changes to your policies, first save the application.
 
-	b. Select **testing a single user**.
+    b. Select **testing a single user**.
 
-	c. Enter their email address and select **Test policies**.
+    c. Enter their email address and select **Test policies**.
 
-	The single user test results will show:
-		- Whether the user is allowed or denied access to this application based on all configured policies.
-		- The user's identity from their most recent Access login attempt.
-		- Whether the user matches individual Allow, Block, or Bypass policies.
+    The single user test results will show: - Whether the user is allowed or denied access to this application based on all configured policies. - The user's identity from their most recent Access login attempt. - Whether the user matches individual Allow, Block, or Bypass policies.
 
 ## Legacy policies
 
@@ -114,8 +111,8 @@ To migrate legacy policies to reusable policies:
 You can use the API to convert a legacy policy into a reusable policy. To convert a legacy policy, make a `PUT` request with an empty request body:
 
 <APIRequest
-  path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
-  method="PUT"
+	path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
+	method="PUT"
 />
 
 The policy is now removed from the applications endpoint (`/access/apps/$APP_ID/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/$POLICY_ID`).
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
index ef3c106a4c83c56..3759f0ffb3db29b 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Require purpose justification after login
-
 ---
 
 Cloudflare Access allows security and IT teams to present users with a purpose justification screen directly after they log in to an Access application. This allows organizations to audit not only for who is accessing their resources, but also for why they are requesting access.
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
index 3c320499e0997ac..a3fccad67a5f5e6 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
@@ -7,7 +7,7 @@ title: Temporary authentication
 sidebar:
   order: 11
 tags:
-- Authentication
+  - Authentication
 ---
 
 With Cloudflare Access, you can require that users obtain approval before they can access a specific self-hosted application or SaaS application. The administrator will receive an email notification to approve or deny the request. Unlike a typical Allow policy, the user will have to request access at the end of each session. This allows you to define the users who should have persistent access and those who must request temporary access.
@@ -20,9 +20,9 @@ With Cloudflare Access, you can require that users obtain approval before they c
 4. Under **Additional settings**, turn on [**Purpose justification**](/cloudflare-one/access-controls/policies/require-purpose-justification/).
 5. Turn on **Temporary authentication**.
 6. Enter the **Email addresses of the approvers**.
-	:::note
-	Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	:::
+   :::note
+   Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
+   :::
 7. Save the policy.
 
 Temporary authentication is now enabled for users who match this policy. You can optionally add a second **Allow** policy for users who should have persistent access. Be sure the policy order is set to allow persistent users through.
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
index 7ff124cd8eb6d90..a9f7713dccc5a33 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
index 64603599f027224..28d4336eca249b9 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
@@ -7,8 +7,8 @@ title: Service tokens
 sidebar:
   order: 6
 tags:
-- JSON web token (JWT)
-- Authentication
+  - JSON web token (JWT)
+  - Authentication
 ---
 
 import {
diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index e29b38b2b415178..2b66eb6b6433481 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -62,19 +62,19 @@ This page lists the default account limits for rules, applications, fields, and
 
 ## Cloudflare Tunnel
 
-| Feature                                            | Limit |
-| -------------------------------------------------- | ----- |
-| `cloudflared` tunnels per account                  | 1,000 |
+| Feature                                            | Limit                               |
+| -------------------------------------------------- | ----------------------------------- |
+| `cloudflared` tunnels per account                  | 1,000                               |
 | Routes (CIDR routes + Hostname routes) per account | 1,000 (shared with Cloudflare Mesh) |
-| Active `cloudflared` replicas per tunnel           | 25    |
-| Virtual networks per account                       | 1,000 |
+| Active `cloudflared` replicas per tunnel           | 25                                  |
+| Virtual networks per account                       | 1,000                               |
 
 ## Cloudflare Mesh
 
-| Feature                                            | Limit |
-| -------------------------------------------------- | ----- |
-| Mesh nodes per account                             | 50    |
-| Routes (CIDR routes) per account                   | 1,000 (shared with Cloudflare Tunnel) |
+| Feature                          | Limit                                 |
+| -------------------------------- | ------------------------------------- |
+| Mesh nodes per account           | 50                                    |
+| Routes (CIDR routes) per account | 1,000 (shared with Cloudflare Tunnel) |
 
 ## Digital Experience Monitoring (DEX)
 
@@ -106,6 +106,7 @@ This page lists the default account limits for rules, applications, fields, and
 | Gateway API policy expression | 140,000         |
 
 ## Cloudflare One Client
+
 | Feature                                                                    | Limit  |
 | -------------------------------------------------------------------------- | ------ |
 | Characters per device profile expression                                   | 10,000 |
diff --git a/src/content/docs/cloudflare-one/changelog/tunnel.mdx b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
index 7d4677d85c9b423..5c1f6285b4348a4 100644
--- a/src/content/docs/cloudflare-one/changelog/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog, Render } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog
-	product="tunnel"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
 
 ## 2024-10-17
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
index 64994724c683773..508f0cb7179a5a0 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
@@ -29,13 +29,13 @@ Templates provide Cloudflare-managed starting points for sensitivity schemas and
 
 Data Classification works alongside detection entries and DLP profiles.
 
-| Component | What it does |
-| --- | --- |
+| Component         | What it does                                                                                                            |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
 | Detection entries | Detect specific content such as patterns, datasets, document fingerprints, AI prompt topics, and predefined detections. |
-| Labels | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content. |
-| Templates | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups. |
-| Data classes | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags. |
-| DLP profiles | Apply detection and classification logic to DLP scanning and enforcement workflows. |
+| Labels            | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content.        |
+| Templates         | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups.                                 |
+| Data classes      | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags.      |
+| DLP profiles      | Apply detection and classification logic to DLP scanning and enforcement workflows.                                     |
 
 In general, detection entries help identify sensitive content. Data Classification helps organize and label that content so administrators can identify its severity, understand where it exists, and apply it consistently. DLP profiles then apply that logic to scanning and enforcement workflows.
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
index 76a268ab8c5fbda..2e931248090f21d 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
@@ -182,16 +182,16 @@ Your new document entry will replace the original document entry. If your file u
 
 DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
 
-| Detection entry | Description |
-| --- | --- |
-| Content: PII | Prompt contains personal information such as names, SSNs, or email addresses. |
-| Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials. |
-| Content: Source Code | Prompt contains actual source code, code snippets, or proprietary algorithms. |
-| Content: Customer Data | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
-| Content: Financial Information | Prompt contains financial numbers or confidential business data. |
-| Intent: PII | Prompt requests specific personal information about individuals. |
-| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities. |
-| Intent: Jailbreak | Prompt attempts to circumvent AI security policies. |
+| Detection entry                       | Description                                                                                       |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| Content: PII                          | Prompt contains personal information such as names, SSNs, or email addresses.                     |
+| Content: Credentials and Secrets      | Prompt contains API keys, passwords, or other sensitive credentials.                              |
+| Content: Source Code                  | Prompt contains actual source code, code snippets, or proprietary algorithms.                     |
+| Content: Customer Data                | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
+| Content: Financial Information        | Prompt contains financial numbers or confidential business data.                                  |
+| Intent: PII                           | Prompt requests specific personal information about individuals.                                  |
+| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities.                      |
+| Intent: Jailbreak                     | Prompt attempts to circumvent AI security policies.                                               |
 
 Each detection entry is categorized as either **Content** or **Intent**:
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
index ccd073189323e6d..e948a705b784d4a 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
@@ -14,151 +14,151 @@ Predefined detection entries are Cloudflare-managed detections for specific type
 
 You can add any predefined detection entry directly to a custom [DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/#build-a-custom-profile) or [data class](/cloudflare-one/data-loss-prevention/data-classification/build-a-data-class/). Use the following reference to review all predefined detection entries currently supported by Cloudflare DLP.
 
-| Detection entry | Description |
-| --- | --- |
-| AI Prompt Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials |
-| AI Prompt Content: Customer data | Prompt contains customer names, projects, business activities, or confidential customer contexts |
-| AI Prompt Content: Financial Information | Prompt contains actual financial numbers or confidential business data |
-| AI Prompt Content: PII | Prompt contains personal information (names, SSNs, emails, etc.) |
-| AI Prompt Content: Source code | Prompt contains source code, code snippets, or proprietary algorithms |
-| AI Prompt Intent: Code Abuse and Malicious Code | Malicious code or attempts to exploit vulnerabilities |
-| AI Prompt Intent: Jailbreak | Prompt attempts to circumvent security policies |
-| AI Prompt Intent: PII | Prompt requests specific personal information about individuals |
-| Amazon AWS Access Key ID | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`. |
-| Amazon AWS Secret Access Key | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`. |
-| American Express Card Number | Detects American Express credit card numbers such as "378282246310005". |
-| American Express Text | Detects mentions of the American Express brand name such as "American Express". |
-| AU Passport Number | Detects Australian passport numbers such as "L1234567". |
-| Australia Address | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000". |
-| Australia Business (ABN) | Detects Australian Business Numbers (ABN) such as "51 824 753 556". |
-| Australia Company (ACN) | Detects Australian Company Numbers (ACN) such as "001 000 004". |
-| Australia Medicare | Detects Australian Medicare card numbers such as "2000000006". |
-| Australia Passport | Detects Australian passport numbers such as "L1234567". |
-| Australia Tax File Number | Detects Australian Tax File Numbers (TFN) such as "85 655 734". |
-| Austria SSN (SV-Nummer) | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180". |
-| Austria Tax ID | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789". |
-| Austria VAT (UID) | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678". |
-| Belgium Tax ID (NN) | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61". |
-| Belgium VAT | Detects Belgian VAT numbers such as "BE0000000097". |
-| Bitcoin Wallet | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2". |
-| Brazil CNPJ | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81". |
-| Brazil CPF (Tax ID) | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25". |
-| Bulgaria Uniform Civil (EGN) | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007". |
-| C | Detects C source code. |
-| C# | Detects C# source code. |
-| C++ | Detects C++ source code. |
-| Canada Bank Account Number | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567". |
-| Canada Health Number | Detects Canadian provincial health card numbers such as "1234-567-897". |
-| Canada Passport | Detects Canadian passport numbers such as "AB123456". |
-| Canada PHIN (Manitoba) | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009". |
-| Canada Physical Address | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1". |
-| Canada Social Insurance Number | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474". |
-| Chile National ID (RUT) | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5". |
-| China ID Card | Detects Chinese resident identity card numbers such as "11010519491231002X". |
-| Cloudflare Account Owned API Token | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`. |
-| Cloudflare User API Key | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`. |
-| Cloudflare User API Token | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`. |
-| Croatia Personal ID (OIB) | Detects Croatian personal identification numbers (OIB) such as "10000000005". |
-| Denmark Tax (CPR) | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008". |
-| Diners Club Card Number | Detects Diners Club credit card numbers such as "30121690374838". |
-| Discord Webhook | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`. |
-| Email Address | Detects email addresses such as "test@example.com". |
-| Ethereum Wallet | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F". |
-| EU Passport | Detects EU member state passport numbers such as "AB1234567". |
-| FDA Active Ingredients | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB". |
-| FDA Drug Names | Detects FDA-registered drug names such as "ABACAVIR". |
-| Finland Tax ID | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y". |
-| France CNI (National ID) | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901". |
-| France Passport | Detects French passport numbers such as "12AB34567". |
-| France Social Security Number | Detects French social security (INSEE) numbers such as "145081849670637". |
-| France Tax ID (SPI) | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123". |
-| France VAT | Detects French VAT numbers such as "FR12000000000". |
-| Full Name | Detects personal full names. |
-| Generic CVV Card Number | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033". |
-| Germany Tax ID | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005". |
-| Germany VAT | Detects German VAT numbers (USt-IdNr) such as "DE100000003". |
-| GitHub PAT | Detects GitHub personal access tokens such as a token beginning with `ghp_`. |
-| Go | Detects Go source code. |
-| Google GCP API Key | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`. |
-| Greece Tax (AFM) | Detects Greek tax identification numbers (AFM) such as "100000003". |
-| Haskell | Detects Haskell source code. |
-| Hong Kong Identity Card Number | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)". |
-| Hungary Tax | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008". |
-| IBAN | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59". |
-| ICD-10 FY2023 Short Description | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified". |
-| ICD-11 Short Description | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS". |
-| India Aadhaar | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124". |
-| India GST (GSTIN) | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5". |
-| India PAN Card | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F". |
-| India Voter ID | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567". |
-| Indonesia Identity Card Number | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011". |
-| Indonesia Tax (NPWP) | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345". |
-| Ireland Tax (PPS) | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA". |
-| Ireland VAT | Detects Ireland VAT numbers such as "IE1234567T". |
-| Italy Fiscal Code | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z". |
-| Japan Address | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001". |
-| Japan My Number (Corp) | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002". |
-| Japan My Number (Person) | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005". |
-| Japan Names (Kanji) | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎". |
-| Japan Passport | Detects Japanese passport numbers such as "TZ1234567". |
-| Java | Detects Java source code. |
-| JavaScript | Detects JavaScript source code. |
-| Korea Resident Number (RRN) | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567". |
-| Lua | Detects Lua source code. |
-| Luxembourg Tax | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345". |
-| Luxembourg VAT | Detects Luxembourg VAT numbers such as "LU10000053". |
-| Malaysian National Identity Card Number | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354". |
-| Mastercard Card Number | Detects Mastercard credit card numbers such as "5252 5971 4219 4116". |
-| Mastercard Text | Detects mentions of the Mastercard brand name such as "Mastercard". |
-| Microsoft Azure Client Secret | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`. |
-| MX CLABE (Bank) | Detects Mexican CLABE bank account numbers such as "032180000118359719". |
-| MX CURP | Detects Mexican CURP codes such as "GOMC850515HJCRRR05". |
-| Netherlands BSN | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782". |
-| Netherlands VAT | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01". |
-| NPM Token | Detects npm registry access tokens such as a token beginning with `npm_`. |
-| NZ NHI Number | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016". |
-| NZ Tax (IRD) | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850". |
-| OpenAI API Key | Detects OpenAI API keys such as a key beginning with `sk-proj-`. |
-| Peru Tax (RUC) | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001". |
-| Peru Unique ID (DNI) | Detects Peruvian national identity numbers (DNI) such as "12345678". |
-| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1". |
-| Poland National ID (PESEL) | Detects Polish national identification numbers (PESEL) such as "85051500006". |
-| Poland REGON | Detects Polish National Business Registry numbers (REGON) such as "100000008". |
-| Poland Tax (NIP) | Detects Polish tax identification numbers (NIP) such as "123-456-32-18". |
-| Portugal Tax (NIF) | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002". |
-| PyPI Token | Detects PyPI package upload tokens such as a token beginning with `pypi-`. |
-| Python | Detects Python source code. |
-| R | Detects R source code. |
-| Rust | Detects Rust source code. |
-| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H". |
-| Slack API Token | Detects Slack API tokens such as a token beginning with `xoxb-`. |
-| Slack Webhook | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`. |
-| Spain DNI/NIF | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z". |
-| Spain SSN | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890". |
-| Spain Tax (CIF) | Detects Spanish corporate tax identification codes (CIF) such as "A58818501". |
-| SSH Private Key | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----". |
-| Stripe Granular Restricted Key | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`. |
-| Stripe Standard Secret Key | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`. |
-| Sweden Tax | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874". |
-| SWIFT | Detects SWIFT/BIC business identifier codes such as "PMFAUS66". |
-| Swift | Detects Swift source code. |
-| Taiwan National Identification Number | Detects Taiwan national identification numbers such as "W171845961". |
-| Thai Identity Card Number | Detects Thai national identity card numbers such as "4-8547-01245-28-9". |
-| UAE Passport | Detects United Arab Emirates passport numbers such as "A1234567". |
-| Union Pay Card Number | Detects UnionPay credit card numbers such as "6250941006528599". |
-| Union Pay Text | Detects mentions of the UnionPay brand name such as "Union Pay". |
-| United Kingdom National Insurance Number | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C". |
-| United Kingdom NHS Number | Detects UK NHS patient identification numbers such as "485-585-0454". |
-| United States ABA Routing Number | Detects US ABA bank routing numbers such as "021000021". |
-| United States SSN Numeric Detection | Detects US Social Security Numbers such as "123-45-6789". |
-| United States SSN Text | Detects mentions of "SSN" or "social security" as a keyword, such as "social security". |
-| Unsanitized HAR File | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
-| Uruguay ID (CI) | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8". |
-| US Driver's License Number | Detects US driver's license numbers such as "CA License: A1234567". |
-| US Individual Tax Identification Number (ITIN) | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678". |
-| US Mailing Address | Detects US mailing addresses such as "100 First St, Chicago, IL 60601". |
-| US Passport Number | Detects US passport numbers such as "A12345678". |
-| US Phone Number | Detects US phone numbers such as "555-555-5555". |
-| US Physical Address | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601". |
-| Visa Card Number | Detects Visa credit card numbers such as "4111 1111 1111 1111". |
-| Visa Text | Detects mentions of the Visa brand name such as "Visa". |
+| Detection entry                                      | Description                                                                                                                                                                  |
+| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| AI Prompt Content: Credentials and Secrets           | Prompt contains API keys, passwords, or other sensitive credentials                                                                                                          |
+| AI Prompt Content: Customer data                     | Prompt contains customer names, projects, business activities, or confidential customer contexts                                                                             |
+| AI Prompt Content: Financial Information             | Prompt contains actual financial numbers or confidential business data                                                                                                       |
+| AI Prompt Content: PII                               | Prompt contains personal information (names, SSNs, emails, etc.)                                                                                                             |
+| AI Prompt Content: Source code                       | Prompt contains source code, code snippets, or proprietary algorithms                                                                                                        |
+| AI Prompt Intent: Code Abuse and Malicious Code      | Malicious code or attempts to exploit vulnerabilities                                                                                                                        |
+| AI Prompt Intent: Jailbreak                          | Prompt attempts to circumvent security policies                                                                                                                              |
+| AI Prompt Intent: PII                                | Prompt requests specific personal information about individuals                                                                                                              |
+| Amazon AWS Access Key ID                             | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`.                                                                                                             |
+| Amazon AWS Secret Access Key                         | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`.                                                                                           |
+| American Express Card Number                         | Detects American Express credit card numbers such as "378282246310005".                                                                                                      |
+| American Express Text                                | Detects mentions of the American Express brand name such as "American Express".                                                                                              |
+| AU Passport Number                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
+| Australia Address                                    | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000".                                                                        |
+| Australia Business (ABN)                             | Detects Australian Business Numbers (ABN) such as "51 824 753 556".                                                                                                          |
+| Australia Company (ACN)                              | Detects Australian Company Numbers (ACN) such as "001 000 004".                                                                                                              |
+| Australia Medicare                                   | Detects Australian Medicare card numbers such as "2000000006".                                                                                                               |
+| Australia Passport                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
+| Australia Tax File Number                            | Detects Australian Tax File Numbers (TFN) such as "85 655 734".                                                                                                              |
+| Austria SSN (SV-Nummer)                              | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180".                                                                                                  |
+| Austria Tax ID                                       | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789".                                                                                            |
+| Austria VAT (UID)                                    | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678".                                                                                                             |
+| Belgium Tax ID (NN)                                  | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61".                                                                          |
+| Belgium VAT                                          | Detects Belgian VAT numbers such as "BE0000000097".                                                                                                                          |
+| Bitcoin Wallet                                       | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2".                                                                                               |
+| Brazil CNPJ                                          | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81".                                                                                   |
+| Brazil CPF (Tax ID)                                  | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25".                                                                                       |
+| Bulgaria Uniform Civil (EGN)                         | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007".                                                                                                          |
+| C                                                    | Detects C source code.                                                                                                                                                       |
+| C#                                                   | Detects C# source code.                                                                                                                                                      |
+| C++                                                  | Detects C++ source code.                                                                                                                                                     |
+| Canada Bank Account Number                           | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567".                                                                         |
+| Canada Health Number                                 | Detects Canadian provincial health card numbers such as "1234-567-897".                                                                                                      |
+| Canada Passport                                      | Detects Canadian passport numbers such as "AB123456".                                                                                                                        |
+| Canada PHIN (Manitoba)                               | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009".                                                                                          |
+| Canada Physical Address                              | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1".                                                                                |
+| Canada Social Insurance Number                       | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474".                                                                                                       |
+| Chile National ID (RUT)                              | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5".                                                                         |
+| China ID Card                                        | Detects Chinese resident identity card numbers such as "11010519491231002X".                                                                                                 |
+| Cloudflare Account Owned API Token                   | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`.                                                                                        |
+| Cloudflare User API Key                              | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`.                                                                                                               |
+| Cloudflare User API Token                            | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`.                                                                                                          |
+| Croatia Personal ID (OIB)                            | Detects Croatian personal identification numbers (OIB) such as "10000000005".                                                                                                |
+| Denmark Tax (CPR)                                    | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008".                                                                                           |
+| Diners Club Card Number                              | Detects Diners Club credit card numbers such as "30121690374838".                                                                                                            |
+| Discord Webhook                                      | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`.                                                                                        |
+| Email Address                                        | Detects email addresses such as "test@example.com".                                                                                                                          |
+| Ethereum Wallet                                      | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F".                                                                                      |
+| EU Passport                                          | Detects EU member state passport numbers such as "AB1234567".                                                                                                                |
+| FDA Active Ingredients                               | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB".                                                                                                   |
+| FDA Drug Names                                       | Detects FDA-registered drug names such as "ABACAVIR".                                                                                                                        |
+| Finland Tax ID                                       | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y".                                                                                        |
+| France CNI (National ID)                             | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901".                                                                            |
+| France Passport                                      | Detects French passport numbers such as "12AB34567".                                                                                                                         |
+| France Social Security Number                        | Detects French social security (INSEE) numbers such as "145081849670637".                                                                                                    |
+| France Tax ID (SPI)                                  | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123".                                                                                       |
+| France VAT                                           | Detects French VAT numbers such as "FR12000000000".                                                                                                                          |
+| Full Name                                            | Detects personal full names.                                                                                                                                                 |
+| Generic CVV Card Number                              | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033".                                                                          |
+| Germany Tax ID                                       | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005".                                                                               |
+| Germany VAT                                          | Detects German VAT numbers (USt-IdNr) such as "DE100000003".                                                                                                                 |
+| GitHub PAT                                           | Detects GitHub personal access tokens such as a token beginning with `ghp_`.                                                                                                 |
+| Go                                                   | Detects Go source code.                                                                                                                                                      |
+| Google GCP API Key                                   | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`.                                                                                                              |
+| Greece Tax (AFM)                                     | Detects Greek tax identification numbers (AFM) such as "100000003".                                                                                                          |
+| Haskell                                              | Detects Haskell source code.                                                                                                                                                 |
+| Hong Kong Identity Card Number                       | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)".                                                                                                         |
+| Hungary Tax                                          | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008".                                                                                        |
+| IBAN                                                 | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59".                                                                                     |
+| ICD-10 FY2023 Short Description                      | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified".                                                                                          |
+| ICD-11 Short Description                             | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS".                                                                                                    |
+| India Aadhaar                                        | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124".                                                                                             |
+| India GST (GSTIN)                                    | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5".                                                                              |
+| India PAN Card                                       | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F".                                                                                         |
+| India Voter ID                                       | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567".                                                                                                                 |
+| Indonesia Identity Card Number                       | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011".                                                                                               |
+| Indonesia Tax (NPWP)                                 | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345".                                                                                    |
+| Ireland Tax (PPS)                                    | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA".                                                                                                     |
+| Ireland VAT                                          | Detects Ireland VAT numbers such as "IE1234567T".                                                                                                                            |
+| Italy Fiscal Code                                    | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z".                                                                                                    |
+| Japan Address                                        | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001".                                                                                   |
+| Japan My Number (Corp)                               | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002".                                                                                      |
+| Japan My Number (Person)                             | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005".                                                                                      |
+| Japan Names (Kanji)                                  | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎".                                                                            |
+| Japan Passport                                       | Detects Japanese passport numbers such as "TZ1234567".                                                                                                                       |
+| Java                                                 | Detects Java source code.                                                                                                                                                    |
+| JavaScript                                           | Detects JavaScript source code.                                                                                                                                              |
+| Korea Resident Number (RRN)                          | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567".                                                                                           |
+| Lua                                                  | Detects Lua source code.                                                                                                                                                     |
+| Luxembourg Tax                                       | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345".                                                                                      |
+| Luxembourg VAT                                       | Detects Luxembourg VAT numbers such as "LU10000053".                                                                                                                         |
+| Malaysian National Identity Card Number              | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354".                                                                                           |
+| Mastercard Card Number                               | Detects Mastercard credit card numbers such as "5252 5971 4219 4116".                                                                                                        |
+| Mastercard Text                                      | Detects mentions of the Mastercard brand name such as "Mastercard".                                                                                                          |
+| Microsoft Azure Client Secret                        | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`.                                                                                                      |
+| MX CLABE (Bank)                                      | Detects Mexican CLABE bank account numbers such as "032180000118359719".                                                                                                     |
+| MX CURP                                              | Detects Mexican CURP codes such as "GOMC850515HJCRRR05".                                                                                                                     |
+| Netherlands BSN                                      | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782".                                                                                       |
+| Netherlands VAT                                      | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01".                                                                                                             |
+| NPM Token                                            | Detects npm registry access tokens such as a token beginning with `npm_`.                                                                                                    |
+| NZ NHI Number                                        | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016".                                                                                                   |
+| NZ Tax (IRD)                                         | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850".                                                                                        |
+| OpenAI API Key                                       | Detects OpenAI API keys such as a key beginning with `sk-proj-`.                                                                                                             |
+| Peru Tax (RUC)                                       | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001".                                                                                                |
+| Peru Unique ID (DNI)                                 | Detects Peruvian national identity numbers (DNI) such as "12345678".                                                                                                         |
+| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1".                                                                                        |
+| Poland National ID (PESEL)                           | Detects Polish national identification numbers (PESEL) such as "85051500006".                                                                                                |
+| Poland REGON                                         | Detects Polish National Business Registry numbers (REGON) such as "100000008".                                                                                               |
+| Poland Tax (NIP)                                     | Detects Polish tax identification numbers (NIP) such as "123-456-32-18".                                                                                                     |
+| Portugal Tax (NIF)                                   | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002".                                                                            |
+| PyPI Token                                           | Detects PyPI package upload tokens such as a token beginning with `pypi-`.                                                                                                   |
+| Python                                               | Detects Python source code.                                                                                                                                                  |
+| R                                                    | Detects R source code.                                                                                                                                                       |
+| Rust                                                 | Detects Rust source code.                                                                                                                                                    |
+| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H".                                                                                                        |
+| Slack API Token                                      | Detects Slack API tokens such as a token beginning with `xoxb-`.                                                                                                             |
+| Slack Webhook                                        | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`.                                                                                 |
+| Spain DNI/NIF                                        | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z".                                                                                                     |
+| Spain SSN                                            | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890".                                                                                           |
+| Spain Tax (CIF)                                      | Detects Spanish corporate tax identification codes (CIF) such as "A58818501".                                                                                                |
+| SSH Private Key                                      | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----".                                                                                              |
+| Stripe Granular Restricted Key                       | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`.                                                                                        |
+| Stripe Standard Secret Key                           | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`.                                                                                            |
+| Sweden Tax                                           | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874".                                                                                              |
+| SWIFT                                                | Detects SWIFT/BIC business identifier codes such as "PMFAUS66".                                                                                                              |
+| Swift                                                | Detects Swift source code.                                                                                                                                                   |
+| Taiwan National Identification Number                | Detects Taiwan national identification numbers such as "W171845961".                                                                                                         |
+| Thai Identity Card Number                            | Detects Thai national identity card numbers such as "4-8547-01245-28-9".                                                                                                     |
+| UAE Passport                                         | Detects United Arab Emirates passport numbers such as "A1234567".                                                                                                            |
+| Union Pay Card Number                                | Detects UnionPay credit card numbers such as "6250941006528599".                                                                                                             |
+| Union Pay Text                                       | Detects mentions of the UnionPay brand name such as "Union Pay".                                                                                                             |
+| United Kingdom National Insurance Number             | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C".                                                                                                        |
+| United Kingdom NHS Number                            | Detects UK NHS patient identification numbers such as "485-585-0454".                                                                                                        |
+| United States ABA Routing Number                     | Detects US ABA bank routing numbers such as "021000021".                                                                                                                     |
+| United States SSN Numeric Detection                  | Detects US Social Security Numbers such as "123-45-6789".                                                                                                                    |
+| United States SSN Text                               | Detects mentions of "SSN" or "social security" as a keyword, such as "social security".                                                                                      |
+| Unsanitized HAR File                                 | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
+| Uruguay ID (CI)                                      | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8".                                                                                     |
+| US Driver's License Number                           | Detects US driver's license numbers such as "CA License: A1234567".                                                                                                          |
+| US Individual Tax Identification Number (ITIN)       | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678".                                                                                          |
+| US Mailing Address                                   | Detects US mailing addresses such as "100 First St, Chicago, IL 60601".                                                                                                      |
+| US Passport Number                                   | Detects US passport numbers such as "A12345678".                                                                                                                             |
+| US Phone Number                                      | Detects US phone numbers such as "555-555-5555".                                                                                                                             |
+| US Physical Address                                  | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601".                                                                               |
+| Visa Card Number                                     | Detects Visa credit card numbers such as "4111 1111 1111 1111".                                                                                                              |
+| Visa Text                                            | Detects mentions of the Visa brand name such as "Visa".                                                                                                                      |
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
index 96398de8d42e757..abd3ab310d2558c 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
@@ -37,10 +37,10 @@ The following secrets are validated with regex.
 
 The following Cloudflare API credentials are validated algorithmically using a checksum. Only credentials generated after [Cloudflare's token format update](/fundamentals/api/get-started/token-formats/) will be matched by these entries.
 
-| Detection entry | Format |
-| --- | --- |
-| Cloudflare User API Key | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum |
-| Cloudflare User API Token | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Detection entry                    | Format                                                                         |
+| ---------------------------------- | ------------------------------------------------------------------------------ |
+| Cloudflare User API Key            | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum  |
+| Cloudflare User API Token          | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 | Cloudflare Account Owned API Token | `cfat_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 
 ## Financial Information
@@ -52,7 +52,6 @@ The following Cloudflare API credentials are validated algorithmically using a c
 
 Credit card numbers begin with a six or eight-digit Issuer Identification Number (IIN) and are followed by up to 23 additional digits. Card verification values (CVVs) are not validated.
 
-
 In the table below, entries use one of three validation methods. [Luhn's algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is a checksum formula used to verify credit card numbers. Entries validated "with checksum" use an arithmetic check specific to that number format. Entries validated "with regex" match a known text pattern without performing a mathematical check.
 
 | Detection entry                  | Notes                                                                             |
@@ -74,9 +73,9 @@ In the table below, entries use one of three validation methods. [Luhn's algorit
 
 The **Unsanitized HAR** predefined profile detects HTTP Archive (HAR) files in traffic that have not been processed by Cloudflare's HAR sanitizer. HAR files frequently contain sensitive data such as session cookies, authorization headers, and other credentials.
 
-| Detection entry       | Notes                                                                                                                           |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| Unsanitized HAR file  | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
+| Detection entry      | Notes                                                                                                                                                              |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Unsanitized HAR file | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
 
 You can use this profile in a Gateway HTTP policy to block HAR file uploads or redirect users to `https://har-sanitizer.pages.dev/` to sanitize the file before uploading. For more information, refer to [common DLP policies](/cloudflare-one/data-loss-prevention/dlp-policies/common-policies/).
 
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
index 2ec67b8a7f2d86d..1df5ea81ecd5b67 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
index 014c621a7fcbb9e..4b180d527caeea5 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
@@ -166,9 +166,9 @@ Email security displays the following details:
 
 #### Cloudy summaries
 
-The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. 
+The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted.
 
-Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). 
+Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values).
 
 **View all signatures** allows you to view all the detections that triggered on the email, including detections that did not determine the final disposition.
 
diff --git a/src/content/docs/cloudflare-one/email-security/reference/index.mdx b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
index ed22d9cc45c63d0..554e42af73200ca 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
index e72de496842e22a..f29fd4a0c946be4 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
@@ -19,4 +19,4 @@ Currently, you can process emails in the following regions:
 - US
 - Germany
 - India
-- Australia
\ No newline at end of file
+- Australia
diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
index 04516541176d46d..67304fed00d84ff 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
@@ -21,8 +21,8 @@ To configure auto-move events:
 5. Under **Auto-moves**, select **Configure**.
 6. For each disposition (malicious, spam, bulk, suspicious, spoof), choose what happens to matching emails:
    - **Soft delete - user recoverable**: Moves the message to the user's **Recoverable Items - Deleted** folder. The user can still find and restore the message. This option is only available for Microsoft 365 customers. Refer to [Microsoft 365 Exchange data deletion](https://learn.microsoft.com/en-us/compliance/assurance/assurance-exchange-online-data-deletion) for more information.
-   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it. 
+   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it.
    - **Move to trash**: Moves the message to the user's trash or deleted items folder. This option is only available for Google Workspace users.
    - **Move to junk**: Moves the message to the user's junk or spam folder.
    - **No action**: Leaves the message where it is. Email security still records the disposition, but does not move the message.
-7. Select **Save**.
\ No newline at end of file
+7. Select **Save**.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
index d4eaee4d21f7a1b..447a71c6bb9e4af 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
@@ -10,11 +10,11 @@ sidebar:
 
 This guide describes how to configure detection settings to mitigate impersonation risks while ensuring legitimate delivery.
 
-Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address. 
+Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address.
 
 For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to mitigate delivery disruptions.
 
-To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific.  In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
+To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific. In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
 
 ## Policy selection criteria
 
@@ -36,4 +36,4 @@ Example use cases:
 
 - Prioritize static IPs: Use known and owned, static IP addresses for relay servers. Avoid [ephemeral IP addresses](https://docs.cloud.google.com/vpc/docs/ip-addresses#ephemeral_and_static_ip_addresses) as their transient nature can lead to policy degradation.
 - Enforce Sender Verification: Always have **Sender Verification (Recommended)** enabled in the Cloudflare dashboard. It validates the originating system's email authentication records (namely [SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), and [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) against the domain to ensure authenticity.
-- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
\ No newline at end of file
+- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
index 8481b73230a9b54..efaa4f6b773fcca 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
index fffa7bf2fdd3e28..7c3b68ba2333939 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="email-security/domain-information" product="cloudflare-one" />
\ No newline at end of file
+<Render file="email-security/domain-information" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
index 4a962408af45bb5..9a9a590d97573b0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
index 0365a23705fb682..b5fed567bea01e0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
index 03b7792d24ac057..d3771d0098d4bb0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
@@ -21,4 +21,4 @@ To set up PhishNet Microsoft 365:
 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**.
 4. Select **Upload custom apps**.
 5. Choose **Provide link to manifest file** and paste the URL you copied from the Cloudflare One dashboard.
-6. Verify and complete the wizard.
\ No newline at end of file
+6. Verify and complete the wizard.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
index 414eff1eb5c872e..0d1522a54efcba7 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
@@ -27,4 +27,4 @@ You have now successfully installed Cloudflare PhishNet.
 1. In your Gmail web client, open the message you would like to flag as either spam or phish.
 2. Select the PhishNet logo on the side panel.
 3. Under **Select Submission Type**, select **Spam** or **Phish**.
-4. Select **Submit Report**.
\ No newline at end of file
+4. Select **Submit Report**.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
index 9e049608ac65e75..4190cae0904f56e 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
@@ -15,4 +15,4 @@ To view the destination addresses of user and team submissions:
 3. Select **Settings**.
 4. Go to **Phish submission** > **Submission addresses** > **View**.
 
-The dashboard will display **User submission addresses** and **Team submission addresses**.
\ No newline at end of file
+The dashboard will display **User submission addresses** and **Team submission addresses**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
index c65b4336fa5ad20..43e57d4a1c293fa 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
@@ -15,24 +15,24 @@ import { Markdown } from "~/components";
 
 Before you start the onboarding process, you will have to:
 
-1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline. 
+1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline.
 2. Learn about dispositions, impersonation registry, and submissions.
 3. Know the steps to configure your email environment correctly.
 
 The following table compares features available across API, BCC/Journaling and MX/Inline:
 
-| Feature             	| Microsoft 365                                       	| Google Workspace                  	| Others (On-prem/Cloud)                                   	|
-|---------------------	|-----------------------------------------------------	|-----------------------------------	|----------------------------------------------------------	|
-| Deployment type     	| API and MX                                          	| BCC and MX                        	| MX only                                                  	|
-| API integration     	| Microsoft Graph API                                 	| BCC only                          	| None                                                     	|
-| BCC/Journaling      	| Uses a Journal Rule in the Microsoft Purview portal 	| Uses BCC rules                    	| Uses journaling                                          	|
-| Inline/MX Mode      	| MX records point to Cloudflare                      	| MX records point to Cloudflare    	| MX records point to Cloudflare                           	|
-| Message remediation 	| Auto-moves through Read/Write API                   	| Auto-moves through Read/Write API 	| Messages can be blocked, quarantined, or modified inline 	|
+| Feature             | Microsoft 365                                       | Google Workspace                  | Others (On-prem/Cloud)                                   |
+| ------------------- | --------------------------------------------------- | --------------------------------- | -------------------------------------------------------- |
+| Deployment type     | API and MX                                          | BCC and MX                        | MX only                                                  |
+| API integration     | Microsoft Graph API                                 | BCC only                          | None                                                     |
+| BCC/Journaling      | Uses a Journal Rule in the Microsoft Purview portal | Uses BCC rules                    | Uses journaling                                          |
+| Inline/MX Mode      | MX records point to Cloudflare                      | MX records point to Cloudflare    | MX records point to Cloudflare                           |
+| Message remediation | Auto-moves through Read/Write API                   | Auto-moves through Read/Write API | Messages can be blocked, quarantined, or modified inline |
 
 Note that:
 
 - All email providers support MX/Inline deployment.
-- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or  post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
+- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
 - Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/).
 
 ## 1. Choose a deployment
diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
index 5c704f3a770261e..61054ee69b7887b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
@@ -43,4 +43,4 @@ To stop scanning domains:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**.
-4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
\ No newline at end of file
+4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
index 43b90fbe16e9a31..f61e4bcb70cd12f 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
index 57f5aa4227abd1d..8bb78df403639c3 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
index 327257b4eb0b5e5..ad3849aad352d63 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
@@ -11,4 +11,4 @@ sidebar:
 BCC/Journaling deployment is a post-delivery type of deployment. Cloudflare analyzes emails after they reach the user's inbox. Every time you receive an email, your email provider will send a blind copy to Cloudflare for an analysis.
 
 - Choose [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/) if your email provider is Gmail.
-- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
\ No newline at end of file
+- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
index 943a2e42ca67928..776f45cf8537714 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
index 8ff736556bdbdba..ac23a96bd6a598d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
@@ -95,7 +95,6 @@ To verift that your domain has been added successfully and that your emails are
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**.
 
-
 ## Next steps
 
-<Render file="email-security/enable-logs" product="cloudflare-one" />
\ No newline at end of file
+<Render file="email-security/enable-logs" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
index 4c636aa1972e3b4..6e14bc7bb3cbd1b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
@@ -22,7 +22,6 @@ To use Email security, you will need to have:
 	product="cloudflare-one"
 />
 
-
 ## Manually add domains
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
index f15a938e8733a92..e5945fa7ffe219b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
@@ -11,6 +11,6 @@ sidebar:
 next: false
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
index 34f65be10df2f54..be6fcfaa82de80d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
@@ -16,7 +16,7 @@ Add all of the following addresses to your mail provider's IP allowlist.
 
 Microsoft 365 does not support IPv6 addresses or the following IPv4 ranges:
 
-- `104.30.32.0/19` 
+- `104.30.32.0/19`
 - `134.195.26.0/23`
 
 If you use Microsoft 365, use the individual `/24` blocks (256 addresses each) listed in [Microsoft 365 `/24` addresses](#microsoft-365-24-addresses) instead.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
index 53963c84381f2fe..fce333e04ebd1b6 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
@@ -10,8 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
index d33970c173669e0..2bcd30388647a00 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
@@ -27,4 +27,4 @@ To set up a partner domain:
 
 To edit a partner domain, select the three dots > **Edit**.
 
-To delete a partner domain, select the three dots > **Delete**.
\ No newline at end of file
+To delete a partner domain, select the three dots > **Delete**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
index 35bc8f11bdcdad3..a1e35434d0580f7 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
@@ -10,8 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
index 7f5428d95fbf8ef..4c76d96d35736ed 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
index 14e7f12e83a674d..e04482e75dcf67e 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
@@ -52,4 +52,4 @@ To view submissions:
 3. Choose from the following submission types:
    - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions.
    - [**User submissions**](/cloudflare-one/email-security/submissions/user-submissions/): View emails your users submitted for submissions.
-   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
\ No newline at end of file
+   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
index aff37d96e27156f..87a9a602b6c10cb 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
@@ -36,4 +36,4 @@ To enable Invalid submission email notifications:
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
-3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
\ No newline at end of file
+3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
diff --git a/src/content/docs/cloudflare-one/faq/devices-faq.mdx b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
index d37af87433794e5..86a6908deaaf164 100644
--- a/src/content/docs/cloudflare-one/faq/devices-faq.mdx
+++ b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
@@ -7,7 +7,6 @@ sidebar:
   order: 6
 head: []
 description: Review frequently asked questions about devices in Cloudflare Zero Trust.
-
 ---
 
 [❮ Back to FAQ](/cloudflare-one/faq/)
@@ -20,8 +19,8 @@ As the Cloudflare One Client has replaced WinDivert with WinTun architecture, al
 
 As our [Network Map](https://www.cloudflare.com/en-gb/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the data center (colo) you are connecting to isn't necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-* Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
-* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+- Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
+- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
 
 ## Why is my public IP address sometimes visible?
 
@@ -50,8 +49,8 @@ An [OS firewall rule](/cloudflare-one/team-and-resources/devices/cloudflare-one-
 
 If your private network is [exposed via Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/):
 
-* Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
-* Verify that the user is allowed through by your Access and Gateway policies.
-* Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
+- Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
+- Verify that the user is allowed through by your Access and Gateway policies.
+- Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
 
 When contacting Cloudflare support, ensure that you include [Cloudflare One Client debug logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/) for your device. These logs will help Cloudflare support understand the overall architecture of your machine and networks.
diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
index 94280945992ed4c..f1c5be808fd91bf 100644
--- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
@@ -133,4 +133,4 @@ In **Gateway insights**, you can view a report on your Gateway firewall policies
 In **CASB**, you can review instances of security issues — such as misconfigurations, unauthorized user activity, and shadow IT — found in your SaaS integrations by [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).
 
 - Integrations by number of findings
-- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
\ No newline at end of file
+- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
diff --git a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
index 2295744544866ab..3ab91476f6fa6d1 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
@@ -24,19 +24,19 @@ To view the AI security report dashboard:
 
 To populate the AI security report dashboard, you must have:
 
-* [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
-* User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
-* [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
+- [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
+- User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
+- [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
 
 ## Available insights
 
 The AI security report dashboard includes the following panels and metrics:
 
-* [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
-* [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
-* [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
-* [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
-* [Access login events to MCP servers](#access-login-events-to-mcp-servers)
+- [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
+- [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
+- [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
+- [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
+- [Access login events to MCP servers](#access-login-events-to-mcp-servers)
 
 ### Top 5 visited AI applications by user count
 
@@ -50,10 +50,10 @@ Use this chart to monitor adoption trends and detect new or unauthorized AI tool
 Reports the total number of AI applications identified and their review statuses.  
 Statuses include:
 
-* Unreviewed — Applications not yet evaluated by administrators.  
-* In Review — Applications currently under review for approval.  
-* Unapproved — Applications that are restricted or blocked.  
-* Approved — Applications explicitly permitted for organizational use.
+- Unreviewed — Applications not yet evaluated by administrators.
+- In Review — Applications currently under review for approval.
+- Unapproved — Applications that are restricted or blocked.
+- Approved — Applications explicitly permitted for organizational use.
 
 ### Data uploaded to Artificial Intelligence applications by status
 
@@ -66,4 +66,4 @@ Displays the number of Model Context Protocol (MCP) servers protected by [Cloudf
 
 ### Access login events to MCP servers
 
-Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
\ No newline at end of file
+Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
diff --git a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
index 475a4c3d35c46ac..7a066e04802a46a 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
@@ -29,20 +29,20 @@ To view the Application Access Report dashboard:
 
 To populate the Application Access Report dashboard, you must have:
 
-* At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
-* Users authenticating to these applications through Cloudflare Access.
+- At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
+- Users authenticating to these applications through Cloudflare Access.
 
 ## Available insights
 
 The Application Access Report dashboard includes the following panels and metrics:
 
-* [Summary of Access activity](#summary-of-access-activity)
-* [Access events](#access-events)
-* [Access decisions by event count](#access-decisions-by-event-count)
-* [Access applications by event count](#access-applications-by-event-count)
-* [Access events by type](#access-events-by-type)
-* [Top counts of event details](#top-counts-of-event-details)
-* [Access admin metrics](#access-admin-metrics)
+- [Summary of Access activity](#summary-of-access-activity)
+- [Access events](#access-events)
+- [Access decisions by event count](#access-decisions-by-event-count)
+- [Access applications by event count](#access-applications-by-event-count)
+- [Access events by type](#access-events-by-type)
+- [Top counts of event details](#top-counts-of-event-details)
+- [Access admin metrics](#access-admin-metrics)
 
 ### Summary of Access activity
 
@@ -55,7 +55,7 @@ You can use this graph to review user authentication activity and detect unusual
 
 ### Access decisions by event count
 
-Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).  
+Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).
 
 ### Access applications by event count
 
@@ -71,11 +71,11 @@ This panel helps administrators understand how users are authenticating across a
 
 Lists the most common Access event attributes, including:
 
-* Application name — Displays the top accessed applications.
-* Identity provider — Shows which identity providers (IdPs) were most used.
-* Users — Lists top users by number of login events.
-* Countries — Displays top countries where users logged in.
-* IP addresses — Lists the top source IPs associated with login events.
+- Application name — Displays the top accessed applications.
+- Identity provider — Shows which identity providers (IdPs) were most used.
+- Users — Lists top users by number of login events.
+- Countries — Displays top countries where users logged in.
+- IP addresses — Lists the top source IPs associated with login events.
 
 These insights help administrators identify usage patterns and trends.
 
@@ -83,7 +83,7 @@ These insights help administrators identify usage patterns and trends.
 
 Provides a summary of Access configurations made by admin in your organization, including:
 
-* Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
-* Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
+- Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
+- Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
 
-This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
\ No newline at end of file
+This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
diff --git a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
index 7768588f1179831..cc397c6684cbb8e 100644
--- a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
@@ -7,5 +7,4 @@ title: MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dex-analysis
 sidebar:
   order: 90
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
index 056e13ea2ec0cca..1309beff1282a3f 100644
--- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
@@ -35,12 +35,12 @@ To view analytics on a per-device level, go to [Device monitoring](/cloudflare-o
 
 - **Connectivity status**: Percentage of devices in a given Cloudflare One Client state.
 
-  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                               |
-  | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                          |
-  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                           |
+  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                                                         |
+  | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                               |
+  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                                |
   | Paused       | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [admin override code](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes). Paused clients will [auto-connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) after a timeout period. |
-  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                            |
+  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                 |
 
 - **Mode**: [Client mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) deployed on the device.
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
index 0823f895e22fb5c..7336bc04cde6cad 100644
--- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
@@ -42,7 +42,7 @@ Review the available selectors and their scope in the following list.
 | **Operating system version** | For specifying an operating system version (use Operator `in`) or versions (use Operator `is`).                                   |
 | **Managed network**          | For specifying users accessing the network from the office (managed network) compared to those accessing remotely.                |
 | **SAML attributes**          | For specifying a value from the [SAML Attribute Assertion](/cloudflare-one/traffic-policies/identity-selectors/#saml-attributes). |
-| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                          |
+| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                 |
 
 ## Add a rule to a test
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
index 15a13b2b8c484f9..d09f0e887f56c41 100644
--- a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
@@ -20,4 +20,8 @@ To control which users or groups run a test, use [DEX rules](/cloudflare-one/ins
 
 ## Export DEX application test logs
 
-<Render file="dex/logpush-export" product="cloudflare-one" params={{ applicationTests: true }} />
+<Render
+	file="dex/logpush-export"
+	product="cloudflare-one"
+	params={{ applicationTests: true }}
+/>
diff --git a/src/content/docs/cloudflare-one/insights/index.mdx b/src/content/docs/cloudflare-one/insights/index.mdx
index 84559d3b901bfca..53baf5cb249a412 100644
--- a/src/content/docs/cloudflare-one/insights/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/index.mdx
@@ -40,18 +40,16 @@ If your device is experiencing connectivity issues, Cloudflare recommends starti
 
 1. Use [Analytics Dashboards](/cloudflare-one/insights/analytics/) to understand trends and for visualizations of your log data.
 
-    Administrators typically start with Analytics Dashboards because they offer:
-
-    - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
-    - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
+   Administrators typically start with Analytics Dashboards because they offer:
+   - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
+   - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
 
 2. Use [Logs](/cloudflare-one/insights/logs/) as needed for event-level verification.
 
-    Use Logs when you need to:
-
-    - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
-    - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
-    - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
+   Use Logs when you need to:
+   - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
+   - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
+   - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
 
 ### User-reported issues
 
@@ -59,4 +57,4 @@ Users may report problems like slow or failing connections to internal apps.
 
 1. Start with [Analytics Dashboards](/cloudflare-one/insights/analytics/) to review whether the issue impacts others.
 2. Check [Logs](/cloudflare-one/insights/logs/) for failed authentication attempts, blocked requests, or unexpected policy matches.
-3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
\ No newline at end of file
+3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
index 304fa8f96f03164..0761b8662b76208 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
@@ -16,18 +16,18 @@ To view admin activity logs, log in to the [Cloudflare dashboard](https://dash.c
 
 ## Explanation of the fields
 
-| Field           | Description                                           | Example Value                                                                      |
-| ----------------| ------------------------------------------------------| -----------------------------------------------------------------------------------|
-| Email           | User who performed the action                         | josephli@cloudflare.com                                                            |
-| Product         | Cloudflare product being modified                     | Tunnel                                                                             |
-| Resource        | Specific resource type within the product             | Route                                                                              |
-| Event           | Action performed (Create, Update, Delete)             | Create                                                                             |
-| Date            | Timestamp of when the action occurred                 | April 30, 2026 • 12:19 AM                                                          |
-| User IP Address | IP address of the user who made the change            | 2a09:bac6:6447:523::83:30                                                          |
-| Interface       | How the change was initiated                          | API                                                                                |
-| Audit record    | Unique identifier for the audit log entry             | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                               |
-| Old value       | Previous configuration state (empty for creates)      | {}                                                                                 |
-| New value       | New configuration state after the change              | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
+| Field           | Description                                      | Example Value                                                                          |
+| --------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------- |
+| Email           | User who performed the action                    | josephli@cloudflare.com                                                                |
+| Product         | Cloudflare product being modified                | Tunnel                                                                                 |
+| Resource        | Specific resource type within the product        | Route                                                                                  |
+| Event           | Action performed (Create, Update, Delete)        | Create                                                                                 |
+| Date            | Timestamp of when the action occurred            | April 30, 2026 • 12:19 AM                                                              |
+| User IP Address | IP address of the user who made the change       | 2a09:bac6:6447:523::83:30                                                              |
+| Interface       | How the change was initiated                     | API                                                                                    |
+| Audit record    | Unique identifier for the audit log entry        | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                                   |
+| Old value       | Previous configuration state (empty for creates) | {}                                                                                     |
+| New value       | New configuration state after the change         | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
 
 ## Export admin activity logs
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
index b2a31ec6e175c94..32b6c971303f04d 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
@@ -30,17 +30,18 @@ To view Gateway activity logs:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Choose a type of Gateway log:
-	- **DNS query logs**
-	- **Network logs**
-	- **HTTP request logs**
-	:::note[Log viewer (beta)]
-	Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
-	:::
+   - **DNS query logs**
+   - **Network logs**
+   - **HTTP request logs**
+     :::note[Log viewer (beta)]
+     Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
+     :::
 3. (Optional) Filter the logs that display in the log viewer. You can filter logs by their timestamp and event details (such as host, URL, user email, policy action, and more).
 
-	:::tip
-	Querying for fewer fields improves log loading performance.
-	:::
+   :::tip
+   Querying for fewer fields improves log loading performance.
+   :::
+
 4. Select an individual timestamp to investigate the event in more detail.
 
 ## Selective logging
@@ -61,16 +62,16 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Basic information
 
-| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                             |
-| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                        |
+| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                                       |
+| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                                  |
 | **Email**             | Email address of the user who registered the Cloudflare One Client where traffic originated from. If a non-identity on-ramp (such as a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)) or machine-level authentication (such as a [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/)) was used, this value will be `non_identity@<team-domain>.cloudflareaccess.com`. |
-| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                      |
-| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                           |
-| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                           |
-| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                    |
+| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                                |
+| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                            |
+| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                                     |
+| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                              |
 
 #### Configuration information
 
@@ -85,14 +86,14 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Identities
 
-| Field                  | Description                                                                                                                                                                                                        |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Field                  | Description                                                                                                                                                                                                                  |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who registered the Cloudflare One Client where traffic originated from.                                                                                                                            |
-| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                              |
+| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                                        |
 | **Registration ID**    | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered for a particular email. The same physical device may have multiple registration IDs.           |
 | **Device name**        | Display name of the device returned by the operating system to the Cloudflare One Client. Typically this is the hostname of a device. Not all devices will have a device name. Device names are not guaranteed to be unique. |
 | **Device ID**          | UUID of the device connected with the Cloudflare One Client. Each physical device in your organization will have a UUID.                                                                                                     |
-| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                |
+| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                          |
 
 #### DNS query details
 
@@ -182,14 +183,14 @@ To log failed connections, use [network session logs](/logs/logpush/logpush-job/
 
 #### Identities
 
-| Field                  | Description                                                                           |
-| ---------------------- | ------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                     |
+| ---------------------- | ----------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user sending the packet. This is generated by the Cloudflare One Client.   |
 | **User ID**            | ID of the user sending the packet. This is generated by the Cloudflare One Client.              |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.           |
-| **Device name**        | Name of the device that sent the packet.                                              |
+| **Device name**        | Name of the device that sent the packet.                                                        |
 | **Device ID**          | ID of the physical device that sent the packet. This is generated by the Cloudflare One Client. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                            |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                      |
 
 #### Network query details
 
@@ -228,7 +229,7 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 | Field                        | Description                                                                                                                                                                                                                                                                                                                              |
 | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Host**                     | Hostname in the HTTP header for the HTTP request. Gateway will log the SNI in this field if it responded to the request with a Do Not Inspect action. If Gateway does not receive the SNI, this field will be empty.                                                                                                                     |
-| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                               |
+| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                     |
 | **Action**                   | The Gateway [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) taken based on the first rule that matched (such as Allow or Block).                                                                                                                                                                                        |
 | **Request ID**               | Unique ID of the request.                                                                                                                                                                                                                                                                                                                |
 | **Time**                     | Date and time of the HTTP request.                                                                                                                                                                                                                                                                                                       |
@@ -252,14 +253,14 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 
 #### Identities
 
-| Field                  | Description                                                                                                                   |
-| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                             |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                    |
 | **User ID**            | ID of the user who made the request. This is generated by the Cloudflare One Client.                                                    |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.                                                   |
-| **Device name**        | Name of the device that made the request.                                                                                     |
+| **Device name**        | Name of the device that made the request.                                                                                               |
 | **Device ID**          | ID of the physical device that made the request. This is generated by the Cloudflare One Client on the device that created the request. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                    |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                              |
 
 #### HTTP query details
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
index bc1f6d84f202733..5a3e6717195a05e 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
@@ -15,6 +15,6 @@ import { DirectoryListing } from "~/components";
 
 The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment.
 
-<DirectoryListing button={true}/>
+<DirectoryListing button={true} />
 
 For additional datasets and long-term log storage, refer to [Logpush](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
index 9a69bac2bfb4fe7..ec364aac8147715 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
@@ -33,7 +33,7 @@ Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/
 | Field               | Description                                                                                                                                                                                                                    |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**           | Email used to register the device with Zero Trust.                                                                                                                                                                             |
-| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                    |
+| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                                |
 | **Registration ID** | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered. The same physical device may have multiple registration IDs if multiple users share the device. |
 
 ### Posture details
diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
index 375008abd658fd5..0d6bfb37f1273e2 100644
--- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
@@ -38,23 +38,23 @@ For more information on supported destinations, refer to [Enable destinations](/
 
 Logpush supports all [dashboard logs](/cloudflare-one/insights/logs/dashboard-logs/) as well as additional datasets not available in the Cloudflare One dashboard. Refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/) for a list of all available fields.
 
-| Dataset                                                                                                    | Description                                                                                                                                              |
-| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                    |
-| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                          |
-| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                |
-| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                             |
-| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                     |
-| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                   |
-| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                          |
-| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                              |
-| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                            |
-| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                          |
-| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                     |
-| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) |
+| Dataset                                                                                                    | Description                                                                                                                                                            |
+| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                                  |
+| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                                        |
+| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                              |
+| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                                           |
+| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                                   |
+| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                                |
+| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                                        |
+| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                                            |
+| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                                          |
+| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                                        |
+| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                                   |
+| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/)               |
 | [WARP Config Changes](/logs/logpush/logpush-job/datasets/account/warp_config_changes/)                     | Event logs that Cloudflare generates whenever a device changes [profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) |
-| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                       |
-| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                    |
+| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                                     |
+| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                                  |
 
 ## Verify regional map application
 
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
index b326012ef5deb96..cc0006a02875a8c 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
@@ -176,7 +176,7 @@ When you validate an R2 bucket, exclude the `access-key-id` and `secret-access-k
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-	<DashButton url="/?to=/:account/r2/overview" />
+   <DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -220,4 +220,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
index f8b03fb96ce715a..26abc473b6c624b 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-one
 sidebar:
   order: 1
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Packet captures allow you to record raw network traffic data passing through Cloudflare's network so you can inspect it offline in tools like Wireshark. This is useful for diagnosing connectivity issues, verifying firewall rules, or investigating unexpected traffic patterns.
 
@@ -35,4 +34,4 @@ Full packet captures will collect new traffic sent to Cloudflare's network after
 
 Refer to the articles in this section to learn how to use packet captures.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
index abe3862c5a9b050..62b2709c8e9fc6c 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
@@ -78,14 +78,14 @@ Flag organization access issues to help enforce best practices.
 
 <Render file="casb/data-loss-prevention" product="cloudflare-one" />
 
-| Finding type                                                  | Severity |
-| ------------------------------------------------------------- | -------- |
-| Anthropic: Downloadable File with DLP Profile match           | High     |
-| Anthropic: Claude Chat User Prompt with DLP Profile match     | High     |
-| Anthropic: Claude Chat Assistant Response with DLP Profile match | High  |
-| Anthropic: Claude Chat Uploaded File with DLP Profile match   | High     |
-| Anthropic: Claude Chat Generated File with DLP Profile match  | High     |
-| Anthropic: Claude Project File with DLP Profile match         | High     |
-| Anthropic: Claude Project Document with DLP Profile match     | High     |
-| Anthropic: Claude Chat Artifact with DLP Profile match        | High     |
-| Anthropic: Claude Project Instructions with DLP Profile match | High     |
+| Finding type                                                     | Severity |
+| ---------------------------------------------------------------- | -------- |
+| Anthropic: Downloadable File with DLP Profile match              | High     |
+| Anthropic: Claude Chat User Prompt with DLP Profile match        | High     |
+| Anthropic: Claude Chat Assistant Response with DLP Profile match | High     |
+| Anthropic: Claude Chat Uploaded File with DLP Profile match      | High     |
+| Anthropic: Claude Chat Generated File with DLP Profile match     | High     |
+| Anthropic: Claude Project File with DLP Profile match            | High     |
+| Anthropic: Claude Project Document with DLP Profile match        | High     |
+| Anthropic: Claude Chat Artifact with DLP Profile match           | High     |
+| Anthropic: Claude Project Instructions with DLP Profile match    | High     |
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
index a4f8fc32d81828a..9b59aa70fcbddaa 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
@@ -30,4 +30,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot-fedramp",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
index 6c36357bcb412de..b3db2aa1d185051 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
@@ -22,4 +22,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
index 9e0e96c4c48ecff..e82f7aac39559b8 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
@@ -60,7 +60,7 @@ https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
 | `name`         | `${user:name}`       |
 | `surName`      | `${user:familyName}` |
 
-| `givenName`    | `${user:givenName}`  |
+| `givenName` | `${user:givenName}` |
 
 ![Configuring attribute statements in IAM Identity Center](~/assets/images/cloudflare-one/identity/aws/aws-saml-attributes.png)
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
index b11fbe6575bd942..d01bcec09cbb731 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
@@ -46,8 +46,8 @@ Make a `POST` request to the [Identity Providers](/api/resources/zero_trust/subr
 
 ## Configuration options
 
-| Option | Description | Default |
-| --- | --- | --- |
+| Option                          | Description                                                                                                                                                                  | Default  |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
 | **Restrict to account members** | When enabled, only users who are members of your Cloudflare account can authenticate. When disabled, any Cloudflare user can authenticate (subject to your Access policies). | Disabled |
 
 ## Use Cloudflare account membership in policies
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
index f15160944863211..c9d7965c3fd2706 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
@@ -12,7 +12,7 @@ import { Render } from "~/components";
 
 Use these steps to set up Facebook as your identity provider.
 
-1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one. 
+1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one.
 
 2. Select **Create App** at the top-right. The **Create an app** card displays.
 
@@ -42,7 +42,7 @@ Use these steps to set up Facebook as your identity provider.
 
 15. Select **Settings**, and ensure that **Use Strict Mode for redirect URIs** slider is set to **Yes**.
 
-15. In the **Valid OAuth Redirect URIs** field, enter the following URL:
+16. In the **Valid OAuth Redirect URIs** field, enter the following URL:
 
     ```txt
     https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
@@ -50,7 +50,7 @@ Use these steps to set up Facebook as your identity provider.
 
     <Render file="find-team-name" product="cloudflare-one" />
 
-16. Select **Save Changes**.
+17. Select **Save Changes**.
 
 To test that your connection is working, follow the steps on [SSO Integration](/cloudflare-one/integrations/identity-providers/#test-idps-in-cloudflare-one).
 
@@ -65,4 +65,4 @@ To test that your connection is working, follow the steps on [SSO Integration](/
 	"type": "facebook",
 	"name": "my example idp"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
index 8ffadf28cdfd7c6..583bae2a4359175 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
@@ -55,8 +55,8 @@ To configure GitHub access in both GitHub and Cloudflare One:
 14. Select **Save**.
 
 15. Select **Finish setup** to launch a GitHub authorization page. You will be asked to grant the following permissions to Cloudflare Access:
-	- Organizations and teams (read-only)
-	- Email addresses (read-only)
+    - Organizations and teams (read-only)
+    - Email addresses (read-only)
 
 16. Select **Authorize**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
index 643ef76b062e609..e8868c73cbac521 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
@@ -10,7 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-
 Cloudflare One integrates with your organization's identity provider to apply Cloudflare One and Secure Web Gateway policies. If you work with partners, contractors, or other organizations, you can integrate multiple identity providers simultaneously.
 
 As an alternative to configuring an identity provider, Cloudflare One can send a [one-time PIN (OTP)](/cloudflare-one/integrations/identity-providers/one-time-pin/) to approved email addresses. No configuration needed — simply add a user's email address to an [Access policy](/cloudflare-one/access-controls/policies/) and to the group that allows your team to reach the application. You can simultaneously configure an OTP and an identity provider to allow users to use their own authentication method.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
index 2ef2f3ad811f160..88472d050f21f91 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
@@ -78,13 +78,13 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
 
    ![Configuring the Groups claim filter in Okta](~/assets/images/cloudflare-one/identity/okta/okta-2.png)
 
-
 9. Set **Groups claim filter** to _Matches regex_ and its value to `.*`.
 
 :::note[Token claim expressions]
+
 - Groups managed outside of Okta (for example, Microsoft Entra ID or Google groups) may require different regex values. For more information, refer to the Okta documentation on [Groups Claims](https://support.okta.com/help/s/article/Why-isnt-my-Groups-claim-returning-Active-Directory-groups) and [OpenID Connect Claims](https://support.okta.com/help/s/article/Can-we-retrieve-both-Active-Directory-and-Okta-groups-in-OpenID-Connect-claims).
 - To configure more complex expressions, refer to Okta's [token claims documentation](https://help.okta.com/okta_help.htm?type=oie&locale=en&id=federated-claims-overview).
-:::
+  :::
 
 10. In the **General** tab, copy the **Client ID** and **Client secret**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
index 6e57a4c17621c6c..9d30c743f2b37e0 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
@@ -46,7 +46,6 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C
    | `givenName`           | Given Name     |
    | `surName`             | Family Name    |
 
-
    These [SAML attributes](/cloudflare-one/integrations/identity-providers/generic-saml/#saml-attributes) tell Cloudflare Access who the user is.
 
 9. Set the application to **Active**.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
index 1dfbd4cc2c93d21..698b9665695a37d 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
@@ -37,12 +37,10 @@ To set up Signed AuthN requests:
    Ensure that your IdP validation uses the most recent certificate. Cloudflare Access routinely rotates the public key as a security measure.
 
    Cloudflare Access uses a certificate that includes the following 2 distinguished name fields:
-
    - **Issuer Distinguished Name** - `CN=cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
    - **Subject Distinguished Name** - `CN=*.cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
 
    Most IdP configurations require 3 components to enforce AuthN signature verification:
-
    - **Certificate issuer [distinguished name (DN)](https://knowledge.digicert.com/generalinformation/INFO1745.html)**
    - **Certificate subject distinguished name**
    - **Public certificate**
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
index 164e679ec887af6..470285aa6aaa407 100644
--- a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
@@ -18,8 +18,8 @@ Service-to-service integrations allow the Cloudflare One Client to get device po
 
 ## Supported operating systems
 
-| Device posture check                                                                        | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| ------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| Device posture check                                                                    | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| --------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
 | [Custom integration](/cloudflare-one/integrations/service-providers/custom/)            | ✅    | ✅      | ✅    | ✅  | ✅               |
 | [Crowdstrike](/cloudflare-one/integrations/service-providers/crowdstrike/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
 | [Kolide](/cloudflare-one/integrations/service-providers/kolide/)                        | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
index e973af0760d4ab3..ff02d7946387387 100644
--- a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
@@ -11,13 +11,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-one-connectivity-options"
-  product="networking-services"
-  params={{
-    unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-    connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
-    cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-    onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/"
-  }}
+	file="cloudflare-one-connectivity-options"
+	product="networking-services"
+	params={{
+		unifiedRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
index 7e26c4da5a75875..c69c567e9be0058 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
@@ -37,6 +37,7 @@ flowchart LR
   node --> db
   node --> printer
 ```
+
 ## Manage routes
 
 Use CIDR routes to forward traffic from your mesh node to devices on your local network.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
index 4d20096eb33e2fd..98f1c0ce87d79e1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
@@ -15,8 +15,8 @@ Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`,
 
 The following table lists the cipher suites supported by `cloudflared`:
 
-| Protocol support | Cipher suites |
-|------------------|----------------|
-| TLS 1.3 only | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256` |
-| TLS 1.2 only | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
-| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA` |
+| Protocol support            | Cipher suites                                                                                                                                                                                                                                                                              |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| TLS 1.3 only                | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256`                                                                                                                                                                                                 |
+| TLS 1.2 only                | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
+| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`                                                                                                                     |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
index f60f0eecf786013..e0edd83ad74e895 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 3
 ---
 
-import { DirectoryListing  } from "~/components";
+import { DirectoryListing } from "~/components";
 
 After [creating your Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/), you can configure various aspects of how `cloudflared` runs and connects your infrastructure to Cloudflare's network. This section covers advanced configuration options to optimize tunnel performance, security, and availability.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
index b6e4ec71f36882d..19d5f191ab29920 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
@@ -13,11 +13,13 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/origin-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
-  }}
+	file="tunnel/origin-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+		validatingJwtURL:
+			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
index 3b9c067dddd114d..f6088ef1050edb8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
@@ -65,70 +65,70 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-	<Tabs syncKey="dashPlusAPI">
-	<TabItem label="Dashboard">
-	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
-	2. Select a `cloudflared` tunnel and select **Edit**.
-	3. Select **Refresh token**.
-	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
-
-	</TabItem>
-	<TabItem label="API">
-		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
-
-				```sh
-				openssl rand -base64 32
-				```
-
-				```sh output
-				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
-				```
-
-	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
-
-			<APIRequest
-				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-				method="PATCH"
-				json={{
-					name: "Example tunnel",
-					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
-				}}
-			/>
-
-			```sh output {18}
-			{
-				"success": true,
-				"errors": [],
-				"messages": [],
-				"result": {
-					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
-					"account_tag": "699d98642c564d2e855e9661899b7252",
-					"created_at": "2024-12-04T22:03:26.291225Z",
-					"deleted_at": null,
-					"name": "Example tunnel",
-					"connections": [],
-					"conns_active_at": null,
-					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
-					"tun_type": "cfd_tunnel",
-					"metadata": {},
-					"status": "inactive",
-					"remote_config": true,
-					"token": "eyJhIjoiNWFiNGU5Z..."
-				}
-			}
-			```
-
-	3.  Copy the `token` value shown in the output.
-
-	</TabItem>
-	</Tabs>
-
-	After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
+   <Tabs syncKey="dashPlusAPI">
+   	<TabItem label="Dashboard">
+   	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
+   	2. Select a `cloudflared` tunnel and select **Edit**.
+   	3. Select **Refresh token**.
+   	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+   
+   	</TabItem>
+   	<TabItem label="API">
+   		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
+   
+   				```sh
+   				openssl rand -base64 32
+   				```
+   
+   				```sh output
+   				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
+   				```
+   
+   	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
+   
+   			<APIRequest
+   				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+   				method="PATCH"
+   				json={{
+   					name: "Example tunnel",
+   					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
+   				}}
+   			/>
+   
+   			```sh output {18}
+   			{
+   				"success": true,
+   				"errors": [],
+   				"messages": [],
+   				"result": {
+   					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
+   					"account_tag": "699d98642c564d2e855e9661899b7252",
+   					"created_at": "2024-12-04T22:03:26.291225Z",
+   					"deleted_at": null,
+   					"name": "Example tunnel",
+   					"connections": [],
+   					"conns_active_at": null,
+   					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
+   					"tun_type": "cfd_tunnel",
+   					"metadata": {},
+   					"status": "inactive",
+   					"remote_config": true,
+   					"token": "eyJhIjoiNWFiNGU5Z..."
+   				}
+   			}
+   			```
+   
+   	3.  Copy the `token` value shown in the output.
+   
+   	</TabItem>
+   	</Tabs>
+
+   After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
 2. On half of your `cloudflared` replicas, reinstall the `cloudflared` service with the new token. For example, on a Linux host:
 
    ```sh
-	 sudo cloudflared service uninstall
+    sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
@@ -140,9 +140,9 @@ To rotate a tunnel token:
 
    While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
-5. Wait 10 minutes for traffic to route through the new connectors.
+4. Wait 10 minutes for traffic to route through the new connectors.
 
-6. Repeat steps 2, 3, and 4 for the second half of the replicas.
+5. Repeat steps 2, 3, and 4 for the second half of the replicas.
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
@@ -163,7 +163,7 @@ If your tunnel token is compromised, we recommend taking the following steps:
 3. On each `cloudflared` replica, update `cloudflared` to use the new token. For example, on a Linux host:
 
    ```sh
-	 sudo cloudflared service uninstall
+    sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
index 6840e8a166897b2..c545b148afb32c3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
@@ -14,15 +14,21 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/run-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    usageMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    tunnelWithFirewallURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
-    tunnelPermissionsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
-    createRemoteTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
-    faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/"
-  }}
+	file="tunnel/run-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		usageMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		tunnelWithFirewallURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
+		tunnelPermissionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
+		createRemoteTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
+		faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
index 0a7cbccf1dcbcbc..81564acce0df5df 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
@@ -32,7 +32,10 @@ When `cloudflared` receives a request from a device, it uses the ports on the ho
 - `cloudflared` should be deployed on a dedicated host machine. This model is typically appropriate, but there may be serverless or clustered workflows where a dedicated host is not possible.
 - The host machine should allocate 50,000 ports to be available for use by the `cloudflared` service. The remaining ports are reserved for system administrative processes.
 
-<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
+<Render
+	file="tunnel/availability/port-configuration"
+	product="cloudflare-one"
+/>
 
 ### Private DNS
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
index 5954dd3c2bbff27..73321967dcd5876 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
@@ -35,22 +35,29 @@ Ensure port `7844` is allowed for both TCP and UDP protocols (for `http2` and `q
 <Render file="tunnel/firewall/required-ports" product="cloudflare-one" />
 
 #### SNI-enforcing firewalls
+
 <Render file="tunnel/firewall/sni-hostnames" product="cloudflare-one" />
 
 ### Region US
 
 <Render
-  file="tunnel/firewall/us-region-ports"
-  product="cloudflare-one"
-  params={{ regionURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region" }}
+	file="tunnel/firewall/us-region-ports"
+	product="cloudflare-one"
+	params={{
+		regionURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region",
+	}}
 />
 
 ### Region FedRAMP High
 
 <Render
-  file="tunnel/firewall/fedramp-high-ports"
-  product="cloudflare-one"
-  params={{ tunnelTokenURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/" }}
+	file="tunnel/firewall/fedramp-high-ports"
+	product="cloudflare-one"
+	params={{
+		tunnelTokenURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/",
+	}}
 />
 
 ### Optional
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
index 57b31886ddd0a26..a02784740a89917 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Deploy Cloudflare Tunnel in your environment — from cloud VMs to Kubernetes clusters, with Infrastructure as Code support.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
index 1c27eaad46459cc..2e42733bf93cb6e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
@@ -86,7 +86,6 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
-
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
index 60b688f0c55e95a..6dad6b29b8df2dc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
@@ -31,12 +31,12 @@ import { Render } from "~/components";
 
 ## Manage private networks
 
-| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cloudflared tunnel route ip add <IP/CIDR> <NAME or UUID>` | Adds any network route space (represented as a CIDR) to your routing table. That network space becomes reachable for requests egressing from a user's machine as long as it is using the Cloudflare One Client and is enrolled in the same account that is running the tunnel chosen here. Further, those requests will be proxied to the specified tunnel, and reach an IP in the given CIDR, as long as that IP is reachable from the tunnel. To assign the IP route to a specific [Virtual Network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/), use the `--vnet` option. |
-| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | `cloudflared tunnel route ip delete`                       | Deletes the row for a given CIDR from your routing table. That portion of your network will no longer be reachable by the Cloudflare One Client.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
index e79d92232542499..75fdb3581cab640 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 102
 head: []
 description: View associated copyrights.
-
 ---
 
-***
+---
 
 [https://github.com/BurntSushi/toml](https://github.com/BurntSushi/toml)
 
@@ -36,7 +35,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/Sirupsen/logrus](https://github.com/Sirupsen/logrus)
 
@@ -62,7 +61,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/beorn7/perks/](https://github.com/beorn7/perks/)
 
@@ -87,7 +86,7 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-***
+---
 
 [https://github.com/certifi/gocertifi](https://github.com/certifi/gocertifi)
 
@@ -95,7 +94,7 @@ This Source Code Form is subject to the terms of the Mozilla Public License,
 v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain
 one at [http://mozilla.org/MPL/2.0/](http://mozilla.org/MPL/2.0/).
 
-***
+---
 
 [https://github.com/coreos/go-oidc/](https://github.com/coreos/go-oidc/)
 [https://github.com/coreos/go-systemd/](https://github.com/coreos/go-systemd/)
@@ -306,7 +305,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/facebookgo/grace](https://github.com/facebookgo/grace)
 
@@ -319,14 +318,14 @@ Copyright (c) 2015, Facebook, Inc. All rights reserved.
 Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-* Redistributions of source code must retain the above copyright notice, this
+- Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-* Redistributions in binary form must reproduce the above copyright notice,
+- Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-* Neither the name Facebook nor the names of its contributors may be used to
+- Neither the name Facebook nor the names of its contributors may be used to
   endorse or promote products derived from this software without specific
   prior written permission.
 
@@ -341,7 +340,7 @@ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/getsentry/raven-go](https://github.com/getsentry/raven-go)
 
@@ -352,13 +351,13 @@ Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
 met:
 
-* Redistributions of source code must retain the above copyright
+- Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the above
+- Redistributions in binary form must reproduce the above
   copyright notice, this list of conditions and the following disclaimer
   in the documentation and/or other materials provided with the
   distribution.
-* Neither the name of Apollic Software, LLC nor the names of its
+- Neither the name of Apollic Software, LLC nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 
@@ -374,7 +373,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/glycerine/rbtree](https://github.com/glycerine/rbtree)
 
@@ -398,7 +397,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/golang/protobuf](https://github.com/golang/protobuf)
 
@@ -434,7 +433,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/lib/pq](https://github.com/lib/pq)
 
@@ -447,9 +446,9 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-***
+---
 
-[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\\_protobuf\\_extensions/pbutil)
+[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\_protobuf\_extensions/pbutil)
 
 ```
                              Apache License
@@ -659,7 +658,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/mitchellh/go-homedir](https://github.com/mitchellh/go-homedir)
 
@@ -685,7 +684,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/pkg/errors](https://github.com/pkg/errors)
 
@@ -695,10 +694,10 @@ All rights reserved.
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
 
-* Redistributions of source code must retain the above copyright notice, this
+- Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-* Redistributions in binary form must reproduce the above copyright notice,
+- Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
@@ -713,10 +712,10 @@ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
-[https://github.com/prometheus/client\_golang](https://github.com/prometheus/client_golang)
-[https://github.com/prometheus/client\_model](https://github.com/prometheus/client_model)
+[https://github.com/prometheus/client_golang](https://github.com/prometheus/client_golang)
+[https://github.com/prometheus/client_model](https://github.com/prometheus/client_model)
 [https://github.com/prometheus/common](https://github.com/prometheus/common)
 [https://github.com/prometheus/procfs](https://github.com/prometheus/procfs)
 
@@ -928,7 +927,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/urfave/cli](https://github.com/urfave/cli)
 
@@ -954,7 +953,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-***
+---
 
 [https://github.com/go-yaml/yaml](https://github.com/go-yaml/yaml)
 
@@ -1166,7 +1165,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://zombiezen.com/go/capnproto2](https://zombiezen.com/go/capnproto2)
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
index c3079b110404278..6299a916a068aac 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
@@ -6,7 +6,6 @@ products:
 title: License
 sidebar:
   order: 51
-
 ---
 
 Apache License
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
index e880dc05a8955b9..1004578cbdb1b59 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
@@ -30,12 +30,12 @@ Follow this guide to set up a Cloudflare Tunnel using the API.
 Make a `POST` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/create/) endpoint:
 
 <APIRequest
-  path="/accounts/{account_id}/cfd_tunnel"
-  method="POST"
-  json={{
-    name: "api-tunnel",
-    config_src: "cloudflare",
-  }}
+	path="/accounts/{account_id}/cfd_tunnel"
+	method="POST"
+	json={{
+		name: "api-tunnel",
+		config_src: "cloudflare",
+	}}
 />
 
 ```sh output
@@ -80,46 +80,47 @@ Before you publish an application through your tunnel, you must:
 
 Follow these steps to publish an application to the Internet. If you are looking to connect a private resource, skip to the [Connect a network](#3b-connect-a-network) section.
 
-1. Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
-
-		<APIRequest
-			path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
-			method="PUT"
-			json={{
-				config: {
-					ingress: [
-						{
-							hostname: "app.example.com",
-							service: "http://localhost:8001",
-							originRequest: {},
-						},
-						{
-							service: "http_status:404",
-						},
-					],
-				},
-			}}
-		/>
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
-
-   Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
-
-2. [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
-
-		<APIRequest
-			path="/zones/{zone_id}/dns_records"
-			method="POST"
-			json={{
-				type: "CNAME",
-				proxied: true,
-				name: "app.example.com",
-				content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
-			}}
-		/>
-
-   This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
+1.  Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
+
+        <APIRequest
+        	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
+        	method="PUT"
+        	json={{
+        		config: {
+        			ingress: [
+        				{
+        					hostname: "app.example.com",
+        					service: "http://localhost:8001",
+        					originRequest: {},
+        				},
+        				{
+        					service: "http_status:404",
+        				},
+        			],
+        		},
+        	}}
+        />
+
+    :::note
+    If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+    :::
+
+    Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
+
+2.  [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
+
+        <APIRequest
+        	path="/zones/{zone_id}/dns_records"
+        	method="POST"
+        	json={{
+        		type: "CNAME",
+        		proxied: true,
+        		name: "app.example.com",
+        		content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
+        	}}
+        />
+
+    This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
 
 This application will be publicly available on the Internet once you [run the tunnel](#4-install-and-run-the-tunnel). To allow or block specific users, [create an Access application](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/).
 
@@ -128,13 +129,13 @@ This application will be publicly available on the Internet once you [run the tu
 To connect a private network through your tunnel, [add a tunnel route](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/create/):
 
 <APIRequest
-  path="/accounts/{account_id}/teamnet/routes"
-  method="POST"
-  json={{
-    network: "172.16.0.0/16",
-    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-    comment: "Example private network route",
-  }}
+	path="/accounts/{account_id}/teamnet/routes"
+	method="POST"
+	json={{
+		network: "172.16.0.0/16",
+		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+		comment: "Example private network route",
+	}}
 />
 
 `cloudflared` can now route traffic to these destination IPs. To configure Zero Trust policies and connect as a user, refer to [Connect private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/).
@@ -150,11 +151,11 @@ Install `cloudflared` on your server and run the tunnel using the `token` value
 To check if the tunnel is serving traffic:
 
 <APIRequest
-  path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-  method="GET"
-  parameters={{
-    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-  }}
+	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+	method="GET"
+	parameters={{
+		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+	}}
 />
 
 ```sh output
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
index 87b44a017b40937..18e2da263fc28c1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
@@ -18,7 +18,11 @@ Follow this step-by-step guide to create your first [remotely-managed tunnel](/c
 
 ## 1. Create a tunnel
 
-<Stream id="4b75ad2aa58700602e94b148827687a2" title="How to set up Cloudflare Tunnel" thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png" />
+<Stream
+	id="4b75ad2aa58700602e94b148827687a2"
+	title="How to set up Cloudflare Tunnel"
+	thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png"
+/>
 
 <Render file="tunnel/create-tunnel" product="cloudflare-one" />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
index ca65ff18a9887ff..2482ef654c8cfb8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Set up your first tunnel
-
 ---
 
-import { DirectoryListing, GlossaryTooltip } from "~/components"
+import { DirectoryListing, GlossaryTooltip } from "~/components";
 
 To create and manage tunnels, you will need to install and authenticate <GlossaryTooltip term="cloudflared"><code>cloudflared</code></GlossaryTooltip> on your origin server. `cloudflared` is what connects your server to Cloudflare's global network.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
index 017e02c4b363879..6dda076ed46e587 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
@@ -13,8 +13,8 @@ tags:
 
 import { Render, Stream } from "~/components";
 
-:::note[Looking to expose public applications?] 
-This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel). 
+:::note[Looking to expose public applications?]
+This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel).
 :::
 
 Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (`cloudflared`) creates [outbound-only connections](#outbound-only-connections) to Cloudflare's global network. Cloudflare Tunnel can connect HTTP web servers, [SSH servers](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/), [remote desktops](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/), and other protocols safely to Cloudflare. This way, your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
index 25b86d04e55286d..d346bec2114ef0d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Monitor tunnels
 sidebar:
   order: 9
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
index a23a3c04da466a9..90b446cff03deba 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
@@ -6,10 +6,9 @@ products:
 title: Notifications
 sidebar:
   order: 1
-
 ---
 
-import { AvailableNotifications } from "~/components"
+import { AvailableNotifications } from "~/components";
 
 Administrators can receive an alert when Cloudflare Tunnels in an account change their health or deployment status. Notifications can be delivered via email, webhook, and third-party services.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
index b2dd6df9595c190..e80b571a1bbc009 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
@@ -24,9 +24,9 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 4. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/) for this tunnel route. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
 
-	:::note
-	To create a new virtual network, select **Manage virtual networks**.
-	:::
+   :::note
+   To create a new virtual network, select **Manage virtual networks**.
+   :::
 
 ## 2. Set up the client
 
@@ -34,7 +34,11 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ## 3. Route private network IPs through the Cloudflare One Client
 
-<Render file="tunnel/warp-to-tunnel-route-ips" product="cloudflare-one" params={{ one: "private network"}}/>
+<Render
+	file="tunnel/warp-to-tunnel-route-ips"
+	product="cloudflare-one"
+	params={{ one: "private network" }}
+/>
 
 ## 4. (Recommended) Filter network traffic with Gateway
 
@@ -46,7 +50,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ### Zero Trust policies
 
-<Render file="tunnel/catch-all-policy" product="cloudflare-one"/>
+<Render file="tunnel/catch-all-policy" product="cloudflare-one" />
 
 If you have applications clearly defined by IPs or hostnames, we recommend [creating an Access application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) and managing user access alongside your SaaS and other web apps. Alternatively, if you prefer to secure a private network using a traditional firewall model, you can build Gateway network and DNS policies for IP ranges and domains.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
index 9322c427b9241f5..03dd3b5c2c280f9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
@@ -18,5 +18,6 @@ On the client side, end users connect to Cloudflare's global network using the C
 ![Diagram displaying connections between a device, Cloudflare, and a private network.](~/assets/images/cloudflare-one/connections/private-ips-diagram.png)
 
 To enable remote access to your private network, refer to the following guides:
+
 - [**Connect a private hostname**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/): Route network traffic to an internal application using its hostname.
-- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
\ No newline at end of file
+- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
index 180ab16892b1bcf..f4e9849be0a0224 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 By default, all DNS requests on the user device are resolved by Cloudflare's [public DNS resolver](/1.1.1.1/) except for common top level domains used for local resolution (such as `localhost`). You can connect an internal DNS resolver to Cloudflare and use it to resolve non-publicly routed domains.
 
@@ -18,24 +18,23 @@ By default, all DNS requests on the user device are resolved by Cloudflare's [pu
 
 To resolve private DNS queries:
 
-1. [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
+1.  [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
 
-2. Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
+2.  Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
 
-		:::note
+        :::note
 
-		Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
+        Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
 
-		:::
+        :::
 
-3. Route specific DNS queries to your internal DNS resolver using one of the following options:
+3.  Route specific DNS queries to your internal DNS resolver using one of the following options:
+    - [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
+    - Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
 
-	- [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
-	- Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
+4.  [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
 
-4. [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
-
-5. Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
+5.  Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
 
 The Cloudflare One Client will now send DNS queries to your internal DNS resolver for resolution. To learn more, refer to [How the Cloudflare One Client handles DNS requests](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/#how-the-warp-client-handles-dns-requests).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
index 98430c7fdc1b90a..99d934881a0f10d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
@@ -17,13 +17,14 @@ import { Render } from "~/components";
 ## Create a DNS record
 
 <Render
-  file="tunnel/dns-records-create"
-  product="cloudflare-one"
-  params={{
-    certPemURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem"
-  }}
+	file="tunnel/dns-records-create"
+	product="cloudflare-one"
+	params={{
+		certPemURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem",
+	}}
 />
 
 ## Cloudflare settings
 
-<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
\ No newline at end of file
+<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
index 17cb132130adfc8..f658fb166750775 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
@@ -15,10 +15,12 @@ import { Render } from "~/components";
 When you [add a published application route](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application) to a Cloudflare Tunnel, you are instructing Cloudflare to proxy requests for your public hostname to a service running privately behind `cloudflared`.
 
 <Render
-  file="tunnel/protocols-table"
-  product="cloudflare-one"
-  params={{
-    disableTlsVerificationURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
-    locallyManagedTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications"
-  }}
+	file="tunnel/protocols-table"
+	product="cloudflare-one"
+	params={{
+		disableTlsVerificationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
+		locallyManagedTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
index 05468c98e98ec02..cbb16832f033141 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
@@ -25,12 +25,14 @@ When you add a [published application route](/cloudflare-one/networks/connectors
 ### Create a load balancer
 
 <Render
-  file="tunnel/availability/load-balancer-create"
-  product="cloudflare-one"
-  params={{
-    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-    tunnelIdLocation: "the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**"
-  }}
+	file="tunnel/availability/load-balancer-create"
+	product="cloudflare-one"
+	params={{
+		publishedAppRouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+		tunnelIdLocation:
+			"the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**",
+	}}
 />
 
 Refer to the [Load Balancing documentation](/load-balancing/) for more details on load balancer settings and configurations.
@@ -79,6 +81,7 @@ graph LR
 ```
 
 As shown in the diagram, a typical setup includes:
+
 - A dedicated Cloudflare Tunnel per data center.
 - One load balancer pool per tunnel. The load balancer hostname is set to the user-facing application hostname (`app.example.com`).
 - One load balancer endpoint per pool. The endpoint host header is set to the `cloudflared` published application hostname (`server1.example.com`)
@@ -146,12 +149,12 @@ Here is an example of what your DNS records will look like before and after sett
 | CNAME | app1 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app2 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app1 | `<UUID_2>.cfargotunnel.com` |
-| CNAME | app2 | `<UUID_2>.cfargotunnel.com`  |
+| CNAME | app2 | `<UUID_2>.cfargotunnel.com` |
 
 **After**:
 | Type | Name | Content |
 | ---- | ---- | ------- |
-| LB   | `lb.example.com` | n/a |
+| LB | `lb.example.com` | n/a |
 | CNAME | app1 | `lb.example.com` |
 | CNAME | app2 | `lb.example.com` |
 
@@ -160,11 +163,12 @@ Here is an example of what your DNS records will look like before and after sett
 ### Monitors and TCP tunnel origins
 
 <Render
-  file="tunnel/availability/load-balancer-tcp-monitors"
-  product="cloudflare-one"
-  params={{
-    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application"
-  }}
+	file="tunnel/availability/load-balancer-tcp-monitors"
+	product="cloudflare-one"
+	params={{
+		publishedAppRouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+	}}
 />
 
 ### Session affinity and replicas
@@ -174,9 +178,10 @@ The load balancer does not distinguish between [replicas](/cloudflare-one/networ
 ### Local connection preference
 
 <Render
-  file="tunnel/availability/load-balancer-local-connection"
-  product="cloudflare-one"
-  params={{
-    replicasURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/"
-  }}
+	file="tunnel/availability/load-balancer-local-connection"
+	product="cloudflare-one"
+	params={{
+		replicasURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
index d9c0787deeffdfa..ee3c9509de79961 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
@@ -74,5 +74,4 @@ If you see an error with the title `This site can't provide a secure connection`
 
 If you added a [multi-level subdomain](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) as Cloudflare's Universal certificate will not cover the public hostname by default.
 
-
 For more information on Tunnel errors, view your [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) or [contact Cloudflare Support](/support/contacting-cloudflare-support/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
index 04c3693aabbaeb1..0c3a0e8a6720af6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
@@ -28,44 +28,53 @@ The steps for getting diagnostic logs depend on your `cloudflared` deployment en
 These instructions apply to remotely-managed and locally-managed tunnels running directly on the host machine.
 
 <Render
-  file="tunnel/diagnostics/host-environment"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/host-environment"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address",
+	}}
 />
 
 ### Docker
 
 <Render
-  file="tunnel/diagnostics/docker"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/docker"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		defaultMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
+	}}
 />
 
 ### Kubernetes
 
 <Render
-  file="tunnel/diagnostics/kubernetes"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/kubernetes"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		defaultMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
+	}}
 />
 
 ## cloudflared-diag files
 
 <Render
-  file="tunnel/diagnostics/tunnel-diag-file"
-  product="cloudflare-one"
-  params={{
-    runParametersURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
-    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
-    loglevelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server"
-  }}
+	file="tunnel/diagnostics/tunnel-diag-file"
+	product="cloudflare-one"
+	params={{
+		runParametersURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
+		logsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
+		loglevelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
index 281adab55837939..61105e303be197e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 10
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore resources to help you resolve issues with Cloudflare Tunnel connectivity and configuration.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
index 465c95783571898..19b86f3981d6630 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
@@ -7,12 +7,11 @@ title: Use cases
 hidden: false
 sidebar:
   order: 4
-
 ---
 
 Cloudflare Tunnel creates a secure, outbound-only connection between your services and Cloudflare by deploying a lightweight connector in your environment. Here is how to use tunnels with some specific services:
 
-* [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
-* [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
-* [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
-* [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
+- [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
+- [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
+- [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
+- [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
index c39aca829aac5a9..8ae62963190d27f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
@@ -17,4 +17,4 @@ Cloudflare offers three ways to secure RDP:
 
 - [Browser-based RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser/)
 - [RDP with Cloudflare One Client](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client/)
-- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
\ No newline at end of file
+- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
index 7830923733b5e59..e9787ea4da56ea5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
@@ -57,7 +57,7 @@ By default, Internet Explorer will be installed and configured in [Enhanced Secu
 
 <Render file="tunnel/connect-private-network" product="cloudflare-one" />
 
-3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the  **Internal IP** of the VM instance.
+3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the **Internal IP** of the VM instance.
 
 4. (Optional) [Set up Zero Trust policies](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#4-recommended-filter-network-traffic-with-gateway) to fine-tune access to your server.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
index dfb0e2feed3b4db..de8d6a6065a81b3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
@@ -31,160 +31,159 @@ There are a number of different VNC server versions, deployments, and instances.
 
 For demonstration purposes, we will create a TightVNC server on an Ubuntu virtual machine (VM) hosted in Google Cloud Project (GCP). We will configure the VNC server to run XFCE, a lightweight desktop environment suitable for remote access. If you already have a VNC server installed, you can skip this step and [go to Step 2](#2-connect-the-server-to-cloudflare).
 
-1. Open a terminal window for your Ubuntu VM.
+1.  Open a terminal window for your Ubuntu VM.
 
-2. Install XFCE and TightVNC by running the following command:
+2.  Install XFCE and TightVNC by running the following command:
 
-		```sh
-		sudo apt update
-		sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
+        ```sh
+        sudo apt update
+        sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
 
-		```
+        ```
 
-		This command installs the desktop, some helpful utilities, and the VNC server software.
+        This command installs the desktop, some helpful utilities, and the VNC server software.
 
-3. To initialize the VNC server:
+3.  To initialize the VNC server:
+    1. Create a VNC server instance:
 
-	1. Create a VNC server instance:
+       ```sh
+       vncserver
+       ```
 
-		```sh
-		vncserver
-		```
+    2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
 
-	2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
+       TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
 
-		TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
+    3. You will be asked if you want to create a view-only password. You can press `n` for no.
 
-	3. You will be asked if you want to create a view-only password. You can press `n` for no.
+    4. Kill this initial session so that you can edit its configuration:
 
-	4. Kill this initial session so that you can edit its configuration:
+       ```sh
+       vncserver -kill :1
+       ```
 
-		```sh
-		vncserver -kill :1
-		```
-4. Configure VNC to launch the XFCE desktop:
+4.  Configure VNC to launch the XFCE desktop:
+    1. Create a VNC configuration directory if it is missing:
 
-	1. Create a VNC configuration directory if it is missing:
+    ```sh
+    mkdir -p ~/.vnc
+    ```
 
-	```sh
-	mkdir -p ~/.vnc
-	```
+    2. Open the `xstartup` file using a text editor. For example,
 
-	2. Open the `xstartup` file using a text editor. For example,
+    ```sh
+    vim ~/.vnc/xstartup
+    ```
 
-	```sh
-	vim ~/.vnc/xstartup
-	```
+    3. Update the file to the following configuration:
 
-	3. Update the file to the following configuration:
+    ```bash
+    #!/bin/sh
+    unset SESSION_MANAGER
+    unset DBUS_SESSION_BUS_ADDRESS
+    startxfce4
+    ```
 
-	```bash
-	#!/bin/sh
-	unset SESSION_MANAGER
-	unset DBUS_SESSION_BUS_ADDRESS
-	startxfce4
-	```
+    4. Make the file executable:
 
-	4. Make the file executable:
+    ```sh
+    chmod +x ~/.vnc/xstartup
+    ```
 
-	```sh
-	chmod +x ~/.vnc/xstartup
-	```
+5.  Start the VNC server again:
 
-5. Start the VNC server again:
-	```sh
-	vncserver -localhost :1
-	```
+    ```sh
+    vncserver -localhost :1
+    ```
 
-	The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
+    The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
 
-6. (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
+6.  (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
+    1. Open a terminal on the client machine.
 
-	1. Open a terminal on the client machine.
+    2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
 
-	2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
+       ```sh
+       gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
+       ```
 
-		```sh
-		gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
-		```
+    3. Open your preferred VNC viewer application.
 
-	3. Open your preferred VNC viewer application.
+    4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
 
-	4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
+    You should see the Ubuntu VM desktop.
 
-	You should see the Ubuntu VM desktop.
+7.  (Optional) Configure the VNC server to start on boot:
+    1. Find the full path to the `vncserver` command:
 
-7. (Optional) Configure the VNC server to start on boot:
+       ```sh
+       which vncserver
+       ```
 
-	1. Find the full path to the `vncserver` command:
+       ```sh output
+       /usr/bin/vncserver
+       ```
 
-		```sh
-		which vncserver
-		```
-		```sh output
-		/usr/bin/vncserver
-		```
-	2. Create a new service configuration file:
+    2. Create a new service configuration file:
 
-	```sh
-	sudo vim /etc/systemd/system/vncserver@.service
-	```
+    ```sh
+    sudo vim /etc/systemd/system/vncserver@.service
+    ```
 
-	3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
+    3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
 
-		```toml
-		[Unit]
-		Description=Start TightVNC server at startup
-		After=syslog.target network.target
+       ```toml
+       [Unit]
+       Description=Start TightVNC server at startup
+       After=syslog.target network.target
 
-		[Service]
-		Type=forking
-		User=[YOUR_USERNAME]
-		WorkingDirectory=/home/[YOUR_USERNAME]
+       [Service]
+       Type=forking
+       User=[YOUR_USERNAME]
+       WorkingDirectory=/home/[YOUR_USERNAME]
 
-		PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
+       PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
 
-		ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
-		ExecStart=/usr/bin/vncserver -localhost :%i
-		ExecStop=/usr/bin/vncserver -kill :%i
+       ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
+       ExecStart=/usr/bin/vncserver -localhost :%i
+       ExecStop=/usr/bin/vncserver -kill :%i
 
-		[Install]
-		WantedBy=multi-user.target
-		```
+       [Install]
+       WantedBy=multi-user.target
+       ```
 
-		4. Reload `systemd` to read in the new service file:
+       4. Reload `systemd` to read in the new service file:
 
-		```sh
-		sudo systemctl daemon-reload
-		```
+       ```sh
+       sudo systemctl daemon-reload
+       ```
 
-		5. Enable the service to start at boot:
+       5. Enable the service to start at boot:
 
-		```sh
-		sudo systemctl enable vncserver@1.service
-		```
+       ```sh
+       sudo systemctl enable vncserver@1.service
+       ```
 
-		The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
+       The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
+       6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
 
-		6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
+       ```sh
+       sudo loginctl enable-linger [YOUR_USERNAME]
+       ```
 
-		```sh
-		sudo loginctl enable-linger [YOUR_USERNAME]
-		```
+       7. Start the service:
 
-		7. Start the service:
+       ```sh
+       sudo systemctl start vncserver@1.service
+       ```
 
-		```sh
-		sudo systemctl start vncserver@1.service
-		```
+       8. Check its status:
 
-		8. Check its status:
+       ```sh
+       sudo systemctl status vncserver@1.service
+       ```
 
-		```sh
-		sudo systemctl status vncserver@1.service
-		```
-
-		The VNC server will now start automatically every time the VM boots.
+       The VNC server will now start automatically every time the VM boots.
 
 ## 2. Connect the server to Cloudflare
 
@@ -198,7 +197,7 @@ For demonstration purposes, we will create a TightVNC server on an Ubuntu virtua
 
 5. For **Service**, select _TCP_ and enter `localhost:<5901>`. If the VNC server is on a different machine from where you installed the tunnel, enter `<SERVER_IP>:5901`.
 
-	Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
+   Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
 
 6. Save the route.
 
@@ -220,7 +219,10 @@ Create a Cloudflare Access application that users can access through their brows
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
+   <Render
+   	file="access/self-hosted-app/browser-rendering-policies"
+   	product="cloudflare-one"
+   />
 
 7. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
index 621709d181b4715..7f5b8371def9c4d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
@@ -6,7 +6,8 @@ products:
 sidebar:
   order: 10
 head: []
-description: Use Cloudflare WAN's different analytic options for an overview of the
+description:
+  Use Cloudflare WAN's different analytic options for an overview of the
   performance of your sites, or to troubleshoot potential issues.
 tags:
   - Analytics
@@ -16,15 +17,21 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		networkAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		traceRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
-		graphQlTunnelBandwidthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/"
-		 }}
+		networkAnalyticsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		traceRoutes:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
+		graphQlTunnelBandwidthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		siteAnalyticsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
index d3c2fff924b3af7..f685696ff741fda 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -15,4 +15,11 @@ head:
 
 import { Render } from "~/components";
 
-<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" params={{ breakoutTrafficURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/" }} />
\ No newline at end of file
+<Render
+	file="mconn/network-options/app-aware-policies/netflow"
+	product="networking-services"
+	params={{
+		breakoutTrafficURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
index 4694b2188d10e76..81bc27fef3b688e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
@@ -15,9 +15,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN"
+		magicWord: "CF1 Cloudflare WAN",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
index c7a0918e9e4281f..0a93283b55966af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
index 761d5ad3c83ef95..12fc47ede0c7643 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -12,9 +12,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
index 6c2c604b49fd3c4..a7cdd1152a38d1e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -12,8 +12,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }} />
+	params={{ productName: "Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
index 9a1e57ebda7c9dd..294f9511dcdaaa2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
@@ -13,18 +13,21 @@ tags:
   - Analytics
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions: "Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions:
+			"Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "CF1 Cloudflare WAN",
 		networkOverviewPageName: "Network visibility",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
-		}}
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
+	}}
 />
 
 ### Set thresholds for site health
@@ -34,6 +37,7 @@ import { Render } from "~/components"
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index e934890d0601507..e5c5a9d02461bc1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,35 +11,59 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "hardware",
-	productName: "Cloudflare One Appliance",
-	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "CF1 Cloudflare WAN",
-	sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-	wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-	lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-	noConnectorShows: "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
-	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "The Connector is shipped to you deactivated",
-	hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-  maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "hardware",
+		productName: "Cloudflare One Appliance",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "CF1 Cloudflare WAN",
+		sfpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+		lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+		noConnectorShows:
+			"You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage: "The Connector is shipped to you deactivated",
+		hardSoftConn:
+			"You need to deploy two Connectors in your premises before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		referenceInformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index e8ca4f7240d425e..7d8436c9226ce40 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,10 +4,8 @@ description: Reference information for SFP+ port information in Zero Trust netwo
 products:
   - cloudflare-one
 title: SFP+ port information
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info"
-	product="networking-services" />
+<Render file="mconn/sfp-port-info" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
index 6a1b94bdb249832..5299a10b9e18f37 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
@@ -10,34 +10,56 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "virtual",
-	productName: "Cloudflare One Appliance",
-	productNameVirtual: "Virtual Appliance",
-	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "CF1 Cloudflare WAN",
-	wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
-	lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
-	noConnectorShows: "For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
-	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "Virtual Appliance is deactivated after you install it",
-	hardSoftConn: "You need to install two Virtual Appliances before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "virtual",
+		productName: "Cloudflare One Appliance",
+		productNameVirtual: "Virtual Appliance",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "CF1 Cloudflare WAN",
+		wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
+		lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
+		noConnectorShows:
+			"For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage: "Virtual Appliance is deactivated after you install it",
+		hardSoftConn:
+			"You need to install two Virtual Appliances before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+		referenceInformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
index ffd0a4c4b645784..c0051513debf6e3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
index fb436734ed7d217..cb114ce2b99fa6c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,9 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Virtual Appliance",
-		virtualUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		}}
+		virtualUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index ac563378234270b..c7cbae7c3ceabbf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -14,6 +14,9 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-		}} />
+		hardwareConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
index 35e5bf0f59c7313..6bcfc54764da629 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
@@ -6,7 +6,6 @@ products:
 title: Deactivate Connector
 sidebar:
   order: 8
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
index f2b21ce17eccf65..490ed326c212d3f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
@@ -6,7 +6,6 @@ products:
 title: Heartbeat
 sidebar:
   order: 9
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 922634423e75753..630305e6d60c767 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
index c7b5151598427ee..056b0ca5a650163 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
@@ -6,7 +6,6 @@ title: Interrupt window
 description: Learn how to set up when Connector can update its systems.
 sidebar:
   order: 10
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 3949eb19c151c2e..98554bc18b3cf72 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -15,5 +15,5 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		}}
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index b7f774b674a7b81..3a9310c33020487 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,12 +9,16 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "breakout",
-	featureName: "Breakout traffic",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
-	dashName: "CF1 Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "breakout",
+		featureName: "Breakout traffic",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		whatHappensApp:
+			"will now go directly to the Internet and bypass Cloudflare's filtering",
+		dashName: "CF1 Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
index b12153e883b952b..0468257e119128d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
@@ -4,14 +4,16 @@ description: How Application-aware policies works in Zero Trust networking.
 products:
   - cloudflare-one
 title: Application-aware policies
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/overview"
+<Render
+	file="mconn/network-options/app-aware-policies/overview"
 	product="networking-services"
 	params={{
-	gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
-	appTypesGatewayURL: "/cloudflare-one/policies/gateway/application-app-types/"
-	}} />
+		gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
+		appTypesGatewayURL:
+			"/cloudflare-one/policies/gateway/application-app-types/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 4067d211b871836..5aac85459c295d4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,11 +9,13 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "prioritized",
-	featureName: "Prioritized traffic",
-	whatHappensApp: "is now processed first by Connector",
-	dashName: "CF1 Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "prioritized",
+		featureName: "Prioritized traffic",
+		whatHappensApp: "is now processed first by Connector",
+		dashName: "CF1 Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 2c0fe51a6772f0b..fb14bed9a02c912 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,11 +8,13 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-relay"
+<Render
+	file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
+		cfVsCoreDashNamingMwanCni:
+			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
 	}}
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index c8a992aa8ac61b7..54ddbc7c233c16a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,9 +8,10 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-server"
+<Render
+	file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index a3ba4bd0341904e..525082ff11a2ee0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,9 +8,11 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render
+	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
index bda0220b0ebbf27..d3bb4e7b3f2a648 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index b6dc835b4894396..bfd8e592fdc15f9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,11 +8,15 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/link-aggregation"
+<Render
+	file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 1ccd87afb778419..5405768ac68156c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,14 +4,17 @@ products:
   - cloudflare-one
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Connector to  re-use address spaces locally.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/nat-subnet"
+<Render
+	file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-	hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-  virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
\ No newline at end of file
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 43b9ee7508fbdd0..b5133cb7577975e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,12 +6,16 @@ title: Network segmentation
 description: Define policies to define if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/network-segmentation"
+<Render
+	file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index 741b251ec5b73f3..00ebfc4681edb6c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,15 +4,19 @@ products:
   - cloudflare-one
 title: Routed subnets
 description: Learn how to configure routed subnets on a Connector, including setting static routes and next-hop addresses for complex LAN setups.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/routed-subnets"
+<Render
+	file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		netSubnetURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
index 63e642f8fee211d..be5fdb923289884 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
@@ -16,17 +16,28 @@ import { Render } from "~/components";
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		haSetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
-		ecmpRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		multipleWansURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
-		sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		haSetupURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
+		ecmpRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		multipleWansURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
+		sfpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
 		vlanIdURL: "#vlan-id",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		hcFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		dhcpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
-		routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/"
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		hcFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		dhcpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 3806aad41029a92..bec67a3bb4ce2d5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -17,8 +17,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		activateURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		activateURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
index 5c087c6432ea87f..854c24e84e725b5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
@@ -16,12 +16,14 @@ import { Render } from "~/components";
 	params={{
 		dashInfo:
 			"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
-		graphQL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		graphQL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
 		notificationsPath:
 			"[notifications wizard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		magicWord: "CF1 Cloudflare WAN"
+		networkAnalytics:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		magicWord: "CF1 Cloudflare WAN",
 	}}
 />
 
@@ -39,7 +41,8 @@ import { Render } from "~/components";
 	file="tunnel-health/mconn-heartbeat-health"
 	product="networking-services"
 	params={{
-		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		heartbeatURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
index 3b09a3fa29ff311..5c56ccb5ff6fcbf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
@@ -18,7 +18,9 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		magicTunnelHealthCheckCalculation:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/",
-		networkAnalyticsPath: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		healthChecks: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsPath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		healthChecks:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index 4a5d426468f3433..33927b2f361233a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -12,4 +12,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
+<Render
+	file="cloudflare-wan/custom-ike-id-ipsec"
+	product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
index 066c118ccf4222d..e3d0145968a7905 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,10 +15,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		greIpsecTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		greIpsecTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
index f9858038dbd480e..d1d59be9414d68b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
@@ -16,7 +16,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		healthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		healthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		addTunnelsPath:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 26d6f25b6a74b55..ca3e788d025bd8b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,10 +13,11 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-  file="routing/configure-cloudflare-source-ips"
-  product="networking-services"
-  params={{
-    unifiedRoutingLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/"
-  }}
+	file="routing/configure-cloudflare-source-ips"
+	product="networking-services"
+	params={{
+		unifiedRoutingLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 2fd957397c1f902..334a23c9167b3af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -6,29 +6,37 @@ products:
 sidebar:
   order: 2
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		trafficSteeringPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		trafficSteeringPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		addTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table"
+		routingTableName: "Cloudflare Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 1f5ce39957c3508..d615ab646878dd7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -12,26 +12,41 @@ tags:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		cniLink: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		tunnelHealthChecksPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		tunnelsAndEncapsulationPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		cniLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		updateHCFrequencyPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		tunnelHealthChecksPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
+		tunnelHealthDash:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		configureARRURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
index 478096429eb0edf..8d38559e9f784a5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
index 91c321110a4e9fa..006aa7559219809 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -15,8 +15,11 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
index ee5e8e31b67dd5d..7cfe5c8a32d1f27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index 2e3362c2297a304..c44c422d412e3e9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/alibaba-cloud"
-  product="networking-services"
-  params={{
-    ipSecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/alibaba-cloud"
+	product="networking-services"
+	params={{
+		ipSecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
index 47bdff355de0e2a..53f7609c41d4c0e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
@@ -10,10 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aruba-edgeconnect"
-  product="networking-services"
-  params={{
-		tunnelHealthCheckUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+<Render
+	file="cloudflare-wan/third-party/aruba-edgeconnect"
+	product="networking-services"
+	params={{
+		tunnelHealthCheckUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		magicFirewallUrl: "/cloudflare-network-firewall/",
-		gatewayUrl: "/cloudflare-one/traffic-policies/"
-  }} />
+		gatewayUrl: "/cloudflare-one/traffic-policies/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
index dd27825eb60ed8a..4dde9787ebca0b6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
@@ -6,14 +6,17 @@ products:
 title: Amazon AWS Transit Gateway
 tags:
   - AWS
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aws"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/aws"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index 6e4f1a3573cbf12..b02d849640387d0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-virtual-wan"
-  product="networking-services"
-  params={{
-  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  cloudflareDocumentationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-virtual-wan"
+	product="networking-services"
+	params={{
+		tunnelHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		ipsecTunnelUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		cloudflareDocumentationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index 6308449fc485359..e3af7916ddaaf15 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
-  product="networking-services"
-  params={{
-  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  staticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-vpn-gateway"
+	product="networking-services"
+	params={{
+		ipsecTunnelUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		tunnelHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
index 3692dd21b4e45ca..61a653693d0b777 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index 26cd14b751b3d81..df5158c103fe80f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -10,6 +10,7 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-ios-xe"
-  product="networking-services"
+<Render
+	file="cloudflare-wan/third-party/cisco-ios-xe"
+	product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 2bf5636cbdce15a..b752d4f85dab6f7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -10,15 +10,25 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render
+	file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
-		trafficSteeringUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		paloAltoGuideUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-	}} />
+		antiReplayProtectionUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		unifiedRoutingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		supportedConfigParametersUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		paloAltoGuideUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 4af42ab35a2bc43..0da4cb37c63d84d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fitelnet"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    typeId_ipv4_addrUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fitelnet"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		typeId_ipv4_addrUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
index 3869ebd7e5a01ea..e71cf29b9f07669 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -10,12 +10,19 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fortinet"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    equalCostMultipathRoutingEcmpUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fortinet"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		equalCostMultipathRoutingEcmpUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
index e35533f9aa61fae..e8e6fe1d8fc944a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
@@ -12,9 +12,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/google"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/google"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
index 28c8eb38103e3a7..88548b31947b629 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
index 9041812a55d647d..f3b4d51ebae092c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/juniper"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/juniper"
+	product="networking-services"
+	params={{
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
index 544a2fd71e1b10b..4fe095992306cb0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -10,9 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/oracle"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/oracle"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
index 74648ea559442b1..d3a02cd42315066 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,10 +13,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/palo-alto"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/palo-alto"
+	product="networking-services"
+	params={{
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
index 5c7329f8bb2a15d..8beb36669a01a5a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -11,10 +11,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/pfsense"
-  product="networking-services"
-  params={{
-    configureTwoIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    staticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/pfsense"
+	product="networking-services"
+	params={{
+		configureTwoIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		staticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 681705328bc2479..e2236e3c62ec88c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sonicwall"
-  product="networking-services"
-  params={{
-    ipsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    creatingYourIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createYourStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sonicwall"
+	product="networking-services"
+	params={{
+		ipsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		creatingYourIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createYourStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index b2a4c4249e87375..afc7910dc9d12af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sophos-firewall"
-  product="networking-services"
-  params={{
-    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    ikeIdUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sophos-firewall"
+	product="networking-services"
+	params={{
+		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		ikeIdUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
index ceba0f994025298..bb005e68632169a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -11,8 +11,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/strongswan"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/strongswan"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index a97b5659741e9d7..9a96fafe0bfa4ab 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -11,9 +11,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-wan/third-party/ubiquiti"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN"
-  }}
+	file="cloudflare-wan/third-party/ubiquiti"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
index f944858befeffef..736fbd873bbdd38 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -10,8 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/velocloud"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/velocloud"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
index 1d4fe3f1866abf4..c7dc2d9c75ba0a6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -11,10 +11,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/viptela"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/viptela"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		ciscoIosXeUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
index 75be63a9bfe72a6..e79d26181aeb494 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -10,6 +10,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos"
-  product="networking-services"
-/>
+<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
index 77d9af6a973237c..b2355afb2d6994d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -10,9 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/yamaha"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/yamaha"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
index f8e8f7694c90053..8cf6de52ad11759 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
@@ -16,12 +16,19 @@ import { Render } from "~/components";
 	params={{
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		configureConnectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		configureMwanManually: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		greReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		mtuReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/"
+		configureConnectorUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		configureMwanManually:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ipsecReferenceUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		mtuReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		wanTransformationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
index 8aac7ee6d2a4275..c804130785b3a29 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
@@ -20,13 +20,19 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		connectorName: "Cloudflare One Appliance",
 		connectorCta: "Use Cloudflare One Appliance",
-		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		connectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
-		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/"
+		connectorUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		zeroTrustUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		bgpRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		wanTransformationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
index a8d18b418df7a40..c54c3b324cf1b28 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
@@ -5,7 +5,6 @@ pcx_content_type: reference
 description: Reference information for Third party licenses in Zero Trust networking.
 products:
   - cloudflare-one
-
 ---
 
 import text from "./3rdparty.txt?raw";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
index 70f7ed48d19fc64..653b31922480265 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 12
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
index b6c275104b79281..475873e33440e3a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
@@ -13,14 +13,21 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
+<Render
+	file="magic-cni"
+	product="networking-services"
+	params={{ magicWord: "Cloudflare WAN" }}
+/>
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
index 0e0944033ed0838..506e7260402fd54 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
@@ -17,11 +17,17 @@ import { Render } from "~/components";
 		magicWord: "CF1 Cloudflare WAN",
 		productNameWAN: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/"
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		thirdPartyIntegrationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
index f827135b0192839..bdb55cdaa44ca58 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -5,7 +5,8 @@ products:
 title: Anti-replay protection
 tags:
   - IPsec
-description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description:
+  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
index 6a168b9730c3943..32b8afa7e6f4527 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cloudflareTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
index 4fa1452c2f1d01c..a51b28317cfdf42 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
@@ -12,29 +12,53 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/reference/device-compatibility"
-  product="networking-services"
-  params={{
-    supportedConfigurationParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    arubaEdgeconnectUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-    ciscoMerakiStaticUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-    ciscoSdWanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
-    fortinetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
-    fitelnetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
-    juniperUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
-    paloAltoUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-    pfsenseUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
-    sonicwallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
-    sophosFirewallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
-    strongswanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
-    ubiquitiUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
-    velocloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
-    vyosUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
-    yamahaUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
-    alibabaCloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-    awsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
-    azureUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
-    googleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
-    oracleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/"
-  }} />
+<Render
+	file="cloudflare-wan/reference/device-compatibility"
+	product="networking-services"
+	params={{
+		supportedConfigurationParametersUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		arubaEdgeconnectUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+		ciscoIosXeUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+		ciscoMerakiStaticUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+		ciscoSdWanUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
+		fortinetUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
+		fitelnetUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
+		juniperUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
+		paloAltoUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		pfsenseUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
+		sonicwallUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
+		sophosFirewallUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
+		strongswanUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
+		ubiquitiUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
+		velocloudUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
+		vyosUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
+		yamahaUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
+		alibabaCloudUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+		awsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
+		azureUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
+		googleUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
+		oracleUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index e48aacf091b3898..32c6047307e94c8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -19,14 +19,18 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		mssURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		productURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		mssURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		productURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index f4b1ec66d7f87c2..c08c54539b5b3b6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,13 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination"	}}
+	params={{
+		tunnelStatePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
index c9bbdad031b4e3d..936eef5bb11c21b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
index dad3b9a5d8d8777..a6693ef9af219d6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN"
+		productName: "Cloudflare WAN",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
index 354bdbd705088a9..c5d20719e86eb64 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
@@ -17,22 +17,30 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-  	magicWord: "CF1 Cloudflare WAN",
-  	productName: "Cloudflare WAN",
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-  	greIpsecReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-  	createStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  	editStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
-  	setupBgpPeering: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
-		legacyHCs: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
-		tunnelHCsPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		greIpsecReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		createStaticRoute:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		editStaticRoute:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
+		setupBgpPeering:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		sourceIPsURL:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/",
 		virtualNetworkName: "Cloudflare Virtual Network",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
index 276bc867f82dcd8..f8b615e6070db55 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -18,12 +18,16 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		addTunnels: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
-		staticRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		staticRoutes:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
index d122736e9eeaedc..eace55f088f5192 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
@@ -9,14 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="cloudflare-wan/security-filters"
+<Render
+	file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/"
+		gatewayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
index 2eb4a9483c2622f..e5bc049482c1740 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,10 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
index 1e718eb8e9c31ce..fb5782e5fef4adf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 3f0cd1c1f120d63..23dbe5aa1465d70 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -10,14 +10,19 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index 41ea7fb74a080e1..dd1b594c265542e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -13,14 +13,18 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 49a3d8aef991d65..fca3b17df568c35 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -14,17 +14,24 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
index a1fce7bc5634d3c..0dcfa150778deae 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
@@ -17,11 +17,15 @@ import { Render } from "~/components";
 	file="cloudflare-wan/wan-transformation"
 	product="networking-services"
 	params={{
-		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		connectivityOptionsUrl: "/cloudflare-one/networks/connectivity-options/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		applianceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		secureWanTrafficUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
+		zeroTrustUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		applianceUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		secureWanTrafficUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
index 37ab275a843c03d..c39636c40320181 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
@@ -18,21 +18,36 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfAutoCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
-		cfManualCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
-		decryptTlsURL: "/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
-		doNotInspectURL: "/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
-		warpChecksURL: "/cloudflare-one/reusable-components/posture-checks/client-checks/",
-		osVersionChecks: "/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
-		mwanOnrampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		gatewayResolverPoliciesURL: "/cloudflare-one/traffic-policies/resolver-policies/",
-		gatewayInternalDnsURL: "/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfAutoCertificatesURL:
+			"/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
+		cfManualCertificatesURL:
+			"/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
+		decryptTlsURL:
+			"/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
+		doNotInspectURL:
+			"/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
+		warpChecksURL:
+			"/cloudflare-one/reusable-components/posture-checks/client-checks/",
+		osVersionChecks:
+			"/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
+		mwanOnrampsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+		gatewayResolverPoliciesURL:
+			"/cloudflare-one/traffic-policies/resolver-policies/",
+		gatewayInternalDnsURL:
+			"/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
 		egressPoliciesURL: "/cloudflare-one/traffic-policies/egress-policies/",
-		gatewayLogsURL: "/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
-		tcpMssClampingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		ikeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		gatewayLogsURL:
+			"/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
+		tcpMssClampingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		ikeURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
index 021d27ca4f6f08d..a6aa06e27222024 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
@@ -18,15 +18,23 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/warp"
 	product="networking-services"
 	params={{
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		setupZeroTrustAccountURL: "/cloudflare-one/setup/#2-create-a-zero-trust-organization",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		setupZeroTrustAccountURL:
+			"/cloudflare-one/setup/#2-create-a-zero-trust-organization",
 		ztDashPath: "My Team > Devices",
-		splitTunnelsURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
-		warpDeploymentURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
-		warpIngressIpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
+		splitTunnelsURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
+		warpDeploymentURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
+		warpIngressIpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
 		mwanConnectorName: "Cloudflare One Appliance",
-		domainFallbackURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		domainFallbackURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index d1ca77abe7c8a72..0d372fbdcc0d99f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -15,10 +15,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
index 86daf36cc1a9660..510e6bd01921e87 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
@@ -9,7 +9,6 @@ head:
   - tag: title
     content: Cloudflare One integration tutorials
 description: Learn how to integrate Cloudflare WAN with other Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
index 1bcbcba64603e90..a634aba89cca3ac 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
@@ -16,8 +16,11 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/security-services"
 	product="networking-services"
 	params={{
-		networkFirewallURL: "/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
-		gatewaySetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
-		wanTransformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		networkFirewallURL:
+			"/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
+		gatewaySetupURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		wanTransformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
index 1db111952cb9cd0..21c15ec9d2d739b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-one
 ---
 
-import { Steps } from '~/components';
+import { Steps } from "~/components";
 
 You can scope Cloudflare member permissions to individual [Cloudflare Tunnel](/tunnel/) instances and [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) nodes, instead of granting account-wide access to every Tunnel and Mesh node. This enables least-privilege delegation for private networking operations — for example, letting a support operator stream logs from a single Tunnel without exposing the rest of your account.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
index 24eaa0394bc62b2..7c6fe57320f8f26 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
-
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
index 8bfca8fb0871aec..189b65dec009c19 100644
--- a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
@@ -29,9 +29,9 @@ To add a CIDR route:
 3. In **CIDR**, enter the IP address or CIDR range that you wish to route through the tunnel (for example, `10.0.0.1` or `10.0.0.0/24`). This can be a private or public IP.
 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare.
 5. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/virtual-networks/) for this tunnel route. A virtual network is a private routing domain that provides routing isolation within your account. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
-		:::note
-		Virtual networks are only supported for `cloudflared` tunnels.
-		:::
+   :::note
+   Virtual networks are only supported for `cloudflared` tunnels.
+   :::
 6. Select **Create**.
 
 Cloudflare will now route requests to your private network. However, the route does not automatically capture traffic from end users. To enable client-side connectivity, refer to the [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/) or
@@ -61,9 +61,10 @@ Published application routes expose applications to the Internet via a domain th
 
 :::note[Prerequisites]
 Before you publish an application, ensure you have:
+
 - [Created a Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) using `cloudflared`.
 - [Added a website to Cloudflare](/fundamentals/manage-domains/add-site/).
-:::
+  :::
 
 To add a published application route to an existing tunnel:
 
@@ -74,13 +75,13 @@ To add a published application route to an existing tunnel:
 3. Go to the **Published application routes** tab and select **Add a published application route**.
 
 4. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-	:::note
-	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-	:::
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
 
 5. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example:
-	- **Type**: _HTTP_
-	- **URL**: `localhost:8000`
+   - **Type**: _HTTP_
+   - **URL**: `localhost:8000`
 
 6. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
@@ -91,4 +92,3 @@ Anyone on the Internet can now access the application at the specified hostname.
 ## Add a WAN route
 
 WAN routes define the IP network segments (such as `10.0.0.0/24`) that are reachable via a GRE or IPsec tunnel. To add a WAN route, refer to the [WAN Connectors documentation](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/).
-
diff --git a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
index 90e480866276de9..308de57b07e7f48 100644
--- a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
@@ -23,14 +23,14 @@ When planning your private network addressing and configuring [Split Tunnel](/cl
 | ------------------------------------------------------------- | ---------------- | ------------ |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `100.64.0.0/12`  | Yes          |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `100.80.0.0/16`  | No           |
-| [Device IPs](#device-ips)                           | `100.96.0.0/12`  | Yes          |
+| [Device IPs](#device-ips)                                     | `100.96.0.0/12`  | Yes          |
 | [Private Load Balancer IPs](#private-load-balancer-ips)       | `100.112.0.0/16` | Yes          |
 
 ## IPv6 ranges
 
 | Name                                                          | Default CIDR               | Configurable |
 | ------------------------------------------------------------- | -------------------------- | ------------ |
-| [Device IPs](#device-ips)                           | `2606:4700:0cf1:1000::/64` | No           |
+| [Device IPs](#device-ips)                                     | `2606:4700:0cf1:1000::/64` | No           |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `2606:4700:0cf1:4000::/64` | No           |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `2606:4700:0cf1:5000::/64` | No           |
 
diff --git a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
index 6a8f6c283d0c8b1..be5f7bea46c3b41 100644
--- a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
@@ -17,11 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare One",
-		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		configureRoutesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		privateNetworksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
index 0749407053febed..c3ff67b1fdb0308 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
@@ -24,4 +24,4 @@ Alternatively, to use a keyboard shortcut, press `CTRL + ALT + Z`.
 
 ## Languages
 
-The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
\ No newline at end of file
+The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
index c608dbdef4888a2..3ad4acc8218df86 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
@@ -12,7 +12,6 @@ tags:
 
 import { Render } from "~/components";
 
-
 :::note
 Remote browser isolation is available as an add-on to Zero Trust Pay-as-you-go and Enterprise plans.
 :::
@@ -30,4 +29,3 @@ Cloudflare Browser Isolation is a security product. In order to serve transparen
 ## Troubleshooting
 
 For help resolving common issues with Browser Isolation, refer to [Troubleshoot Browser Isolation](/cloudflare-one/remote-browser-isolation/troubleshooting/).
-
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
index b4040d192dbbf47..e7f230098916d61 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
@@ -83,4 +83,7 @@ You no longer need to isolate both the Identity Provider (IdP) and Service Provi
 
 ## Browser Isolation is not compatible with private apps on non-`443` ports
 
-<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
+<Render
+	file="access/self-hosted-app/browser-isolation-non-443"
+	product="cloudflare-one"
+/>
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
index a74778b93fcbd01..21df1128ff02665 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
@@ -34,8 +34,8 @@ Browser Isolation uses WebRTC (a real-time communication protocol) for low-laten
 
 In order to pass WebRTC traffic, the remoting client must be able to connect to the following IP addresses:
 
-| IP range                                                                 | Port range    | Protocol |
-| ------------------------------------------------------------------------ | ------------- | -------- |
+| IP range                                                                                                           | Port range    | Protocol |
+| ------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
 | IPv4: `162.159.201.10 - 162.159.201.255` <br/> IPv4: `172.64.73.0 - 172.64.73.255` <br/> IPv6: `2606:4700:f2::/48` | 10000 - 59999 | UDP      |
 
 Each remote browser instance is randomly assigned a port, and the port that a user is allocated to will change often and without notice.
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
index c45a25eaf8d13b8..9e910279a1fe9a8 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
@@ -15,13 +15,13 @@ Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudfl
 
 Setup instructions vary depending on how you want to connect your devices to Cloudflare. Refer to the links below to view the setup guide for each deployment option.
 
-| Connection                                                                                                | Mode         | Description                                                                                                          |
-| --------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
-| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                       |
-| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                     |
-| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                           |
-| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network).                                 |
-| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`. |
+| Connection                                                                                                | Mode         | Description                                                                                                                                       |
+| --------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                                          |
+| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                                                  |
+| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).     |
+| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network). |
+| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`.                              |
 
 **In-line** mode means traffic is inspected as it flows through Gateway — users browse to websites using normal URLs, not a special Cloudflare prefix. Some in-line methods require device or network configuration, such as installing the Cloudflare One Client or configuring a PAC file. **Prefixed URL** mode requires users to visit a Cloudflare-hosted URL that wraps the target website.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
index f0ab810ee252406..318f06a6fc92ed4 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
@@ -79,7 +79,7 @@ You can add a Mailto link to your custom block page, which allows users to direc
 | Source IP    | The public source IP of the user device.                                                                                                                                                                                    |
 | Account ID   | The Cloudflare account associated with the block policy.                                                                                                                                                                    |
 | User ID      | The ID of the user who visited the page. Currently, User IDs are not surfaced in the dashboard and can only be viewed by calling the [API](/api/resources/zero_trust/subresources/access/subresources/users/methods/list/). |
-| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                           |
+| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                 |
 | Block Reason | Your policy-specific block message.                                                                                                                                                                                         |
 
 ## Configure policy block behavior
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
index c7cde6525fc3b70..96799f2d3e915f6 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
index 1b02eaa266e0cf7..ccfd4fb9efc2beb 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
@@ -49,24 +49,23 @@ You can use the following commands to validate if the posture check is working a
 1. Open a PowerShell window.
 2. List all installed antivirus products registered with Windows Security Center:
 
-	```powershell
-	Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
-	```
-
-	```powershell output
-	<redacted>
-	displayName              : Windows Defender
-	instanceGuid             : {00000000-0000-0000-0000-000000000000}
-	pathToSignedProductExe   : windowsdefender://
-	pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
-	productState             : 397568
-	timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
-	PSComputerName           : ENDPOINT-01
-	```
+   ```powershell
+   Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
+   ```
+
+   ```powershell output
+   <redacted>
+   displayName              : Windows Defender
+   instanceGuid             : {00000000-0000-0000-0000-000000000000}
+   pathToSignedProductExe   : windowsdefender://
+   pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
+   productState             : 397568
+   timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
+   PSComputerName           : ENDPOINT-01
+   ```
 
 3. Microsoft does not support decoding the `productState` from the `SecurityCenter2` namespace. To verify that an antivirus product is active, open the [Windows Security app](https://support.microsoft.com/en-us/windows/stay-protected-with-the-windows-security-app-2ae0363d-0ada-c064-8b56-6a39afb6a963). The **Virus & threat protection** panel should say `No action needed` with a green checkmark.
 
-	To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
+   To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
 
 4. If you configured a maximum antivirus signature age in your posture check, compare the `timestamp` in the PowerShell output against the current system time. If the difference exceeds the configured number of days, the posture check will fail.
-
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
index daec64a910742b5..6e24b6094c78b8c 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
@@ -38,12 +38,12 @@ The Application Check device posture attribute checks that a specific applicatio
    2. **Operating system**: Select your operating system.
    3. **Application path**: Enter the file path for the executable that will be running (for example, `C:\Program Files\myfolder\myfile.exe`).
 
-		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
 
    :::note
    - Be sure to enter the binary file path, not the application launch path. When checking for an application on macOS, a common mistake is to enter `/Applications/ApplicationName.app`. This will not work as `ApplicationName.app` is a folder. The executable file that will be running is located within the folder, for example `ApplicationName.app/Contents/MacOS/ApplicationName`.
    - Some applications change their file path after an update. Ensure that the application is always in a stable location or use environment variables.
-	 :::
+     :::
 
 5. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint of the publishing certificate](#determine-the-signing-thumbprint) used to sign the binary. Adding this information will enable the check to ensure that the application was signed by the expected software developer.
 6. **SHA-256 (optional)**: Enter the [SHA-256 value](#determine-the-sha-256-value) of the binary. This is used to ensure the integrity of the binary file on the device.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
index bcf50cd88967c96..d0a1f568446a035 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
@@ -38,7 +38,8 @@ The File Check device posture attribute checks for the presence of a file on a d
    2. **Operating system**: Select your operating system.
    3. **File Path**: Enter a file path (for example, `c:\my folder\myfile.exe`).
 
-		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+
    4. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-signing-thumbprint) of the publishing certificate used to sign the file. Adding this information will enable the check to ensure that the file was signed by the expected software developer.
    5. **SHA-256 (optional)**: Enter the [SHA-256 value](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-sha-256-value) of the file. This is used to ensure the integrity of the file on the device.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
index 1d1d08a80225a0d..b580c8ae61cbeb2 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
@@ -36,12 +36,13 @@ The Firewall device posture attribute ensures that a firewall is running on a de
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Configure **Enable firewall check** based on your desired security policy:
-	- **Enabled**: (Recommended) The posture check passes only if the firewall is running.
-	- **Disabled**: The posture check passes only if the firewall is turned off.
+   - **Enabled**: (Recommended) The posture check passes only if the firewall is running.
+   - **Disabled**: The posture check passes only if the firewall is turned off.
+
+   :::note
+   The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
+   :::
 
-	:::note
-	The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
-	:::
 7. Select **Save**.
 
 Next, go to **Insights** > **Logs** > **Posture logs** and verify that the firewall check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
index 1ceee1540f5307e..00d1b33264aa55e 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
@@ -6,33 +6,32 @@ products:
 title: Cloudflare One Client checks
 sidebar:
   order: 1
-
 ---
 
 These device posture checks are performed by the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/). To use this feature, you must [deploy the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) to your devices and enable the desired posture checks.
 
 ## Supported Client modes
 
-* Traffic and DNS mode
-* Traffic only mode
-* Posture only mode
+- Traffic and DNS mode
+- Traffic only mode
+- Posture only mode
 
 ## Supported operating systems
 
-| Device posture check                                                                          | macOS | Windows | Linux       | iOS | Android/ChromeOS |
-| --------------------------------------------------------------------------------------------- | ----- | ------- | ----------- | --- | ---------------- |
-| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
-| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌     | ❌       | ❌           | ✅   | ✅                |
-| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
-| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅     | ✅       | ❌           | ❌   | ❌                |
-| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                          | ✅    | ✅      | ✅    | ❌  | ❌  |
+| Device posture check                                                                                       | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| ---------------------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)                   | ❌    | ✅      | ❌    | ❌  | ❌               |
+| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌    | ❌      | ❌    | ✅  | ✅               |
+| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌    | ✅      | ❌    | ❌  | ❌               |
+| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅    | ✅      | ❌    | ❌  | ❌               |
+| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
index e30d916ac2409c1..92e23f910d1ba59 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
@@ -36,7 +36,7 @@ The OS Version device posture attribute checks whether the version of a device's
 
 5.  (Optional) Configure additional OS-specific fields:
 
-		<Tabs>
+<Tabs>
 		<TabItem label="Windows">
 		To check that Windows devices have required security patches and features installed, include an Update Build Revision (UBR) number in the OS version check.
 		- **Update Build Revision**: Enter the Windows UBR you want devices to match (for example, `3803`). The UBR is the fourth part of the full Windows version number (for example, in `10.0.19045.3803`, the UBR is `3803`).
@@ -77,6 +77,7 @@ Operating systems display version numbers in different ways. This section covers
 ### Windows
 
 Windows version numbers consist of four parts: `Major.Minor.Build.UBR`. For example, `10.0.19045.3803` where:
+
 - `10.0` is the **Version** (Major.Minor)
 - `19045` is the **Build** number
 - `3803` is the **UBR** (Update Build Revision)
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
index fe3b97910a59def..14c460754260543 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
@@ -37,7 +37,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru
 ## 1. Enable the WARP check
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Traffic settings**.
-2. Ensure that *Allow Secure Web Gateway to proxy traffic** is enabled.
+2. Ensure that \*Allow Secure Web Gateway to proxy traffic\*\* is enabled.
 3. Go to **Reusable components** > **Posture checks**.
 4. In **Cloudflare One Client checks**, select **Add a check**.
 5. Select **WARP**, then select **Save**.
diff --git a/src/content/docs/cloudflare-one/reusable-components/tags.mdx b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
index affffb57c1a52f9..9cf337c0f0573e9 100644
--- a/src/content/docs/cloudflare-one/reusable-components/tags.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
@@ -11,4 +11,3 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
-
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
index 06e26a64c28ed43..be1e46ccc11fec2 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
@@ -109,8 +109,8 @@ Use when you only want to enforce [Cloudflare One Client device posture checks](
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                   | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                          | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | Full security with all filtering capabilities    | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | DNS filtering without routing device traffic     | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | Traffic routing with existing DNS infrastructure | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
index 3ddfb9848c66291..7042d96a25bd81b 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
@@ -19,6 +19,7 @@ This section covers the most common issues you might encounter as you deploy the
 ## Connectivity and registration
 
 ### Stuck on "Disconnected" or frequent flapping
+
 If the Cloudflare One Client is stuck in the `Disconnected` state or frequently changes between `Connected` and `Disconnected`, this indicates that the client cannot establish a connection to Cloudflare's global network.
 
 In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/), `daemon.log` will typically show one or more of the following errors:
@@ -27,61 +28,75 @@ In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/clou
 - Connectivity checks timing out for `connectivity.cloudflareclient.com`.
 
 **Common causes**:
+
 - **Firewall blocks**: A local or network firewall is blocking the [required IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 - **VPN interference**: A third-party VPN is fighting for control over the routing table or DNS. Refer to the [VPN compatibility guide](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/vpn/).
 - **ISP blocks**: Your country or ISP may be explicitly blocking client traffic.
 
 ### Registration error (Authentication Expired)
+
 When registering the client, you may see `Authentication Expired` or `Registration error. Please try again later`.
 
 **Common causes**:
+
 - **System clock out of sync**: Your computer system clock must be properly synced via NTP. If your clock is off by more than 20 seconds, the authentication token (JWT) will be invalid.
 - **Prompt timeout**: You must complete the registration in your browser and return to the client within one minute of the prompt.
 
 ### (Linux) DNS connectivity check failed
+
 This error often means that `systemd-resolved` is not allowing the client to resolve DNS requests. In `daemon.log`, you will see `DNS connectivity check failed to resolve host="warp-svc."`.
 
 **Solution**:
+
 1. Add `ResolveUnicastSingleLabel=yes` to `/etc/systemd/resolved.conf`.
 2. Ensure no other DNS servers are explicitly configured in that file.
 3. Restart the service: `sudo systemctl restart systemd-resolved.service`.
 
 ### (Mac/Linux) Invalid character in resolv.conf
+
 The client cannot parse `resolv.conf` files containing invalid characters like `!@#$%^&*()<>?` in `search` directives. Remove these characters to restore service.
 
 ## Browser and certificate issues
 
 ### "Your connection is not private" or untrusted warnings
+
 Advanced security features require the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) to be trusted on the device.
 
 - **Chrome/Edge**: These browsers cache certificates. If you installed the certificate while the browser was running, you must restart the browser.
 - **Root certificate expiry**: The default Cloudflare root certificate expired on February 2, 2025. If you are seeing errors, [generate and activate a new certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) in the dashboard.
 
 ### 2025 Certificate migration
+
 Starting with version 2024.12.554.0, the client can automatically install new certificates as soon as they are **Available** in the dashboard. For older versions, certificates had to be marked **In-Use** first. Ensure **Install CA to system certificate store** is enabled in your [Device settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).
 
 ## Windows-specific issues
 
 ### Windows shows "No Internet access"
+
 This is often a cosmetic error with Windows Network Connectivity Status Indicator (NCSI). Apps like Outlook or JumpCloud may refuse to connect because of this status.
 
 **Solution**:
 Configure NCSI to detect the client's local DNS proxy and use active probing by setting these registry keys to `1`:
+
 - `HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS`
 - `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\EnableActiveProbing`
 
 ### Setup Wizard ends prematurely
+
 This usually indicates a missing dependency, such as .NET Framework `4.7.2` or later. Legacy systems (like Windows 10 Enterprise 1607) may require a manual update of the [.NET Framework Runtime](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net472).
 
 ## Other environment issues
 
 ### WSL2 connectivity
+
 If WSL2 loses connectivity, check your [split tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). The IP range used by WSL to communicate with the host may be accidentally included in the tunnel. Exclude the WSL network range to restore connectivity.
 
 ### SMTP port 25 blocked
+
 By default, the client blocks outgoing traffic on port `25` to prevent spam. Use port `587` or `465` for encrypted email, or contact your account team to request an unblock.
 
 ### Admin override codes expired
+
 [Admin override codes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes) are time-sensitive and adhere to fixed-hour blocks. A code generated at 9:30 AM with a 1-hour timeout will expire at 10:00 AM because its validity is counted within the 9:00 AM-10:00 AM window.
 
 ---
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
index 41e24ebbe3edf84..57570302af9994e 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
@@ -16,22 +16,22 @@ The Cloudflare One Client (formerly WARP) GUI displays the following status mess
 
 To print status messages to the console, run the `warp-cli -l status` command before connecting the client.
 
-| Status message                       | Description                                                                                                                                                                                                                                                                        |
-| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                           |
-| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                              |
-| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                           |
-| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                             |
-| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                              |
-| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                       |
+| Status message                       | Description                                                                                                                                                                                                                                                                                                  |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                                              |
+| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                                                        |
+| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                                                     |
+| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                                                       |
+| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                                          |
+| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                                                 |
 | Setting up your routing table        | Updates the [system routing table](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#routing-table) based on your [Split Tunnel rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). |
-| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                |
-| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                   |
-| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                |
-| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                       |
-| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                  |
-| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                              |
-| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                             |
-| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                 |
-| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                  |
-| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                           |
+| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                            |
+| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                                             |
+| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                                          |
+| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                                   |
+| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                                            |
+| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                                                 |
+| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                                      |
+| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                                           |
+| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                                     |
+| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                                              |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
index 1a48f5bece5c008..2bff092a3e7064e 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
@@ -59,82 +59,82 @@ You can collect client diagnostic logs remotely from the Zero Trust dashboard by
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                            |
-| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                     |
-| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                         |
-| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                                                 |
-| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                     |
-| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                      |
-| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                            |
-| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                         |
-| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                   |
-| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                                   |
-| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                                                 |
-| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                             |
-| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                       |
-| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                              |
-| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                             |
-| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                     |
-| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                     |
-| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                          |
-| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                         |
+| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                                   |
+| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                            |
+| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                              |
+| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                           |
+| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                        |
+| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                 |
+| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                                   |
+| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                                |
+| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                          |
+| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                         |
+| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                            |
+| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                                    |
+| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                              |
+| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                                     |
+| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                                    |
+| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                            |
+| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                            |
+| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                                 |
+| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                                |
 | `dns-check.txt`                                                                                     | Verifies that the Cloudflare One Client DNS servers are set as system default. For [operating modes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) where DNS filtering is enabled, this file contains the IPs of the local DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                |
-| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                           |
-| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                |
-| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                                  |
-| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                          |
-| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                     |
-| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                    |
-| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                            |
-| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                        |
-| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                        |
-| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                           |
-| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                      |
-| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                            |
-| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                  |
-| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                 |
-| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                                  |
-| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                    |
-| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                      |
-| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                       |
-| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
-| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                   |
-| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                     |
-| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                          |
-| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                            |
-| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                             |
-| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                              |
-| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                           |
-| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                            |
-| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                            |
-| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                          |
-| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
-| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                            |
-| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                            |
-| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                              |
-| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                              |
-| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                       |
-| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                |
-| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                            |
-| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                             |
-| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                |
-| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                        |
-| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                               |
-| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                   |
-| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                      |
-| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                               |
-| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                  |
-| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                              |
-| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                               |
-| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                       |
-| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                  |
+| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                       |
+| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                                  |
+| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                       |
+| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                           |
+| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                                 |
+| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                            |
+| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                           |
+| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                                   |
+| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                               |
+| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                               |
+| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                                  |
+| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                             |
+| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                                   |
+| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                         |
+| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                        |
+| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                        |
+| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                           |
+| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                             |
+| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                              |
+| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
+| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                          |
+| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                            |
+| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                                 |
+| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                                              |
+| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                    |
+| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                                     |
+| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                  |
+| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                                   |
+| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                                   |
+| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                                 |
+| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
+| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                                   |
+| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                                   |
+| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                                     |
+| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                                     |
+| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                              |
+| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                       |
+| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                  |
+| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                        |
+| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                       |
+| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                               |
+| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                          |
+| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                          |
+| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                             |
+| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                                           |
+| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                         |
+| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                                     |
+| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                                      |
+| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                              |
+| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                         |
 | `warp-settings.txt`                                                                                 | [Cloudflare One Client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/) applied to the device.                                                                                                                                                                                                                 |
-| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                              |
-| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                        |
-| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                        |
-| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                               |
+| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                                     |
+| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                               |
+| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                               |
+| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                                      |
 
 #### Multiple versions of the same log
 
@@ -161,14 +161,14 @@ This enables a few more logging features:
 - DNS logs for [service modes with DNS filtering](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/)
 - One-shot connectivity checks (same information as `connectivity.txt`, collected when extra debug logging starts rather than when `warp-diag` runs)
 - One-shot traceroutes to:
-	- DNS resolver IPs
-	- DNS resolver hostname
-	- Device API endpoint IPs
-	- Device API endpoint hostname
-	- Tunnel edge connection IPs
+  - DNS resolver IPs
+  - DNS resolver hostname
+  - Device API endpoint IPs
+  - Device API endpoint hostname
+  - Tunnel edge connection IPs
 - On Windows, if you are an administrator:
-	- [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
-	- [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
+  - [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
+  - [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
 
 If extra debug logging is enabled, the command `warp-cli debug extra reconnect` forces the tunnel connection to restart.
 This can be useful for collecting log information if the tunnel connection fails.
@@ -246,19 +246,19 @@ The following log files are available for iOS, Android, and ChromeOS devices.
 
 #### iOS
 
-| Name                                    | Description           |
-| --------------------------------------- | ------------------------------------ |
-| **Extension logs**                          | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                   |
-| **Application logs**                        | Logs from the iOS app process, including GUI events, setting changes, and API calls.                         |
-| **Qlogs**                                  | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID. |
+| Name                 | Description                                                                                                                                                                                 |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Extension logs**   | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
+| **Application logs** | Logs from the iOS app process, including GUI events, setting changes, and API calls.                                                                                                        |
+| **Qlogs**            | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID.                                                    |
 
 #### Android/ChromeOS
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| Name             | Description                           |
-| ---------------- | ---------------------------------------------------- |
-| `unhandled_exception.log`   | Captures errors in the Android application layer that were not caught and could have crashed the app.                                |
-| `console.log` | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes. |
-| `native_tunnel.log`  | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                        |
-| `<connection_id>.sqlog`    | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. |
+| Name                      | Description                                                                                                                                                                                 |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `unhandled_exception.log` | Captures errors in the Android application layer that were not caught and could have crashed the app.                                                                                       |
+| `console.log`             | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes.                                                |
+| `native_tunnel.log`       | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
+| `<connection_id>.sqlog`   | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections.                                                                                                                     |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
index e4307d464bc1c09..80e66ab48ee8d61 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
@@ -20,13 +20,13 @@ A single physical device can have [multiple device registrations](/cloudflare-on
 
 ## Key concepts
 
-| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                                      |
-| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                                            |
-| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                                                |
-| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                             |
-| Device registration                                                                  |  An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
-| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                                                                |
+| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                         |
+| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                             |
+| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                  |
+| Device registration                                                                  | An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
+| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                       |
 
 ## Review device registration status
 
@@ -102,20 +102,20 @@ If the user or service token can successfully re-authenticate, a new device regi
 
 Registrations can have the following statuses:
 
-| Status | Description |
-| --- | --- |
-| **Active** | Registered and able to connect via the Cloudflare One Client. This is the expected operational state. |
+| Status      | Description                                                                                                  |
+| ----------- | ------------------------------------------------------------------------------------------------------------ |
+| **Active**  | Registered and able to connect via the Cloudflare One Client. This is the expected operational state.        |
 | **Revoked** | The registration's public key is invalidated. Revocation does not release the assigned virtual IP addresses. |
 
 ## Manage device registrations
 
 The following table summarizes the actions available for managing device registrations and devices. For all actions, if the user or service token can still re-authenticate, a new registration will be created automatically. To permanently remove access, refer to [Device management](#device-management).
 
-| Action                                                 | What it does                                                                                             | Virtual IPs released?                                  | When to use                                                                                                                                                                                  |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                                                    | You want to fully remove a user's enrollment from a device and free up the virtual IP.                                                                                                       |
-| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                                                     | You want to temporarily block a device from connecting but preserve the registration record. |
-| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes | You want to fully remove a device and all associated registrations.                                                                                                                 |
+| Action                                                 | What it does                                                                                             | Virtual IPs released? | When to use                                                                                  |
+| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------- |
+| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                   | You want to fully remove a user's enrollment from a device and free up the virtual IP.       |
+| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                    | You want to temporarily block a device from connecting but preserve the registration record. |
+| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes                   | You want to fully remove a device and all associated registrations.                          |
 
 ### Delete a device registration
 
@@ -213,8 +213,9 @@ To block a service token from re-authenticating, you must either:
 
 1. Delete the enrollment policy associated with the token, or modify the enrollment policy to no longer include the token (by removing its specific Include rule).
 2. (Optional) [Delete the service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).
-      <br/> You cannot use this service token to create new registrations.
-      <br/> You cannot delete a service token while it is attached to a device enrollment policy.
+   <br /> You cannot use this service token to create new registrations.
+   <br /> You cannot delete a service token while it is attached to a device
+   enrollment policy.
 3. Delete the service token [device registration](/cloudflare-one/team-and-resources/devices/device-registration/#delete-a-device-registration).
 4. (Optional) To fully decommission a device, [remove user access](/cloudflare-one/team-and-resources/devices/device-registration/#remove-user-access), if any exists. Devices with existing registrations will remain connected to Cloudflare until those specific device registrations are manually deleted.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
index 55005c37db7e2b8..8e70dfe2c679456 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
@@ -26,12 +26,12 @@ Review how this change impacts certificate propagation to your end-user devices
 
 Zero Trust will indicate if a certificate is ready for use in inspection based on its deployment status:
 
-| Deployment status    | Description                                                                                                                                                      |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                   |
-| Pending              | The certificate is being activated or deactivated for use.                                                                                                       |
+| Deployment status    | Description                                                                                                                                                                |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                             |
+| Pending              | The certificate is being activated or deactivated for use.                                                                                                                 |
 | Available            | The certificate is deployed across the Cloudflare global network and ready to be turned on. The Cloudflare One Client will install the certificate on your users' devices. |
-| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                   |
+| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                             |
 
 ## Generate a Cloudflare root certificate
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
index 08917bf7ed0f8f9..8d64d7b39cd4c59 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
@@ -754,115 +754,115 @@ To install a certificate for use in a Docker container:
 4. Add the certificate to your Docker image:
 
    <Tabs> <TabItem label="During build process">
-
-   To add the certificate to your Dockerfile to install it during the build process:
-   1. Add the certificate install directions to your Dockerfile. For example:
-
-      ```docker title="Red Hat-based images"
-      FROM registry.access.redhat.com/ubi9/ubi:latest
-      # Or FROM centos:7 or FROM fedora:38
-
-      # Install necessary certificates package
-      RUN dnf install -y ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
-      RUN update-ca-trust extract
-      ```
-
-      ```docker title="Debian-based images"
-      FROM debian:12
-      # Or FROM ubuntu:22.04
-
-      # Install necessary certificates package
-      RUN apt-get update && apt-get install -y ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-      RUN update-ca-certificates
-      ```
-
-      ```docker title="Alpine-based images"
-      FROM alpine:3.18
-
-      # Install necessary certificates package
-      RUN apk add --no-cache ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-      RUN update-ca-certificates
-      ```
-
-   2. Build the Docker image:
-
-      ```sh
-      docker build -t <your-container-name> .
-      ```
-
-   3. Verify the certificate was installed:
-
-      ```sh title="Red Hat-based images"
-      docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-      ```
-
-      ```sh title="Debian and Alpine-based images"
-      docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
-      ```
-
-   </TabItem>
-
-   <TabItem label="During runtime">
-
-   To add the certificate to your Docker Compose file to install it during runtime:
-   1. Add the certificate install directions to your `docker-compose.yml` file. For example:
-
-      ```yaml title="Red Hat-based containers"
-      version: '3'
-      services:
-      	redhat-app:
-      		image: registry.access.redhat.com/ubi9/ubi:latest
-       		volumes:
-       			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
-       		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
-      ```
-
-      ```yaml title="Debian-based containers"
-      version: '3'
-      services:
-      	debian-app:
-      		image: debian:12
-       		volumes:
-       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
-       		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
-      ```
-
-      ```yaml title="Alpine-based containers"
-      version: '3'
-      services:
-      	alpine-app:
-      		image: alpine:3.18
-       		volumes:
-       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
-       		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
-      ```
-
-   2. Run the container:
-
-      ```sh
-      docker-compose up
-      ```
-
-   3. Verify the certificate was installed:
-
-      ```sh title="Red Hat-based containers"
-      docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-      ```
-
-      ```sh title="Debian and Alpine-based containers"
-      docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
-      ```
-
-   </TabItem> </Tabs>
+   
+      To add the certificate to your Dockerfile to install it during the build process:
+      1. Add the certificate install directions to your Dockerfile. For example:
+   
+         ```docker title="Red Hat-based images"
+         FROM registry.access.redhat.com/ubi9/ubi:latest
+         # Or FROM centos:7 or FROM fedora:38
+   
+         # Install necessary certificates package
+         RUN dnf install -y ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
+         RUN update-ca-trust extract
+         ```
+   
+         ```docker title="Debian-based images"
+         FROM debian:12
+         # Or FROM ubuntu:22.04
+   
+         # Install necessary certificates package
+         RUN apt-get update && apt-get install -y ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+         RUN update-ca-certificates
+         ```
+   
+         ```docker title="Alpine-based images"
+         FROM alpine:3.18
+   
+         # Install necessary certificates package
+         RUN apk add --no-cache ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+         RUN update-ca-certificates
+         ```
+   
+      2. Build the Docker image:
+   
+         ```sh
+         docker build -t <your-container-name> .
+         ```
+   
+      3. Verify the certificate was installed:
+   
+         ```sh title="Red Hat-based images"
+         docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+         ```
+   
+         ```sh title="Debian and Alpine-based images"
+         docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
+         ```
+   
+      </TabItem>
+   
+      <TabItem label="During runtime">
+   
+      To add the certificate to your Docker Compose file to install it during runtime:
+      1. Add the certificate install directions to your `docker-compose.yml` file. For example:
+   
+         ```yaml title="Red Hat-based containers"
+         version: '3'
+         services:
+         	redhat-app:
+         		image: registry.access.redhat.com/ubi9/ubi:latest
+          		volumes:
+          			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
+          		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
+         ```
+   
+         ```yaml title="Debian-based containers"
+         version: '3'
+         services:
+         	debian-app:
+         		image: debian:12
+          		volumes:
+          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
+          		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
+         ```
+   
+         ```yaml title="Alpine-based containers"
+         version: '3'
+         services:
+         	alpine-app:
+         		image: alpine:3.18
+          		volumes:
+          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
+          		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
+         ```
+   
+      2. Run the container:
+   
+         ```sh
+         docker-compose up
+         ```
+   
+      3. Verify the certificate was installed:
+   
+         ```sh title="Red Hat-based containers"
+         docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+         ```
+   
+         ```sh title="Debian and Alpine-based containers"
+         docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
+         ```
+   
+      </TabItem> </Tabs>
 
 ### Command-line tools
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
index 5ec0ab6973dad12..442499bd33c48ff 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
@@ -61,16 +61,17 @@ While the Okta integration is turned on, Cloudflare One will send any user risk
 ## Predefined risk behaviors
 
 By default, all predefined behaviors are disabled. When a behavior is enabled, Cloudflare One will continuously evaluate all users within the organization for the behavior. You can [change the risk level](#change-risk-behavior-risk-levels) for predefined behaviors if the default assignment does not suit your environment.
-| Risk behavior                         | Requirements                                                                                                | Description                                                                                                                                                                                                            | Evaluation timing |
+| Risk behavior | Requirements | Description | Evaluation timing |
 | -------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
-| Impossible travel                      | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/)                                            | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
-| High number of DLP policies triggered  | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/)                     | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/).                                  | Evaluated per-request in milliseconds. |
-| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user.                                          | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
+| Impossible travel | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/) | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
+| High number of DLP policies triggered | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/) | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/). | Evaluated per-request in milliseconds. |
+| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
 | CrowdStrike Low ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 0-50 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information.| Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | CrowdStrike Medium ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 50-79 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | Interaction with Malicious File | [Gateway AV scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/) or [File sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/) | User uploads or downloads a file flagged as malicious by Gateway's AV scanner or file sandboxing. Risk is elevated even if the file is blocked. | Evaluated per-request in milliseconds. |
-| Suspicious Security Domain Visited  | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| Suspicious Security Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+
 ## Manage risk behaviors
 
 To toggle risk behaviors, go to **Risk score** > **Risk behaviors**.
@@ -92,9 +93,9 @@ You can change the risk level for a behavior at any time.
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Teams & Resources**.
 2. Go to **Users**.
 3. Select **Risk score** > **Risk behaviors**.
-2. Select the risk behavior you want to modify.
-3. In the drop-down menu, choose your desired risk level.
-4. Select **Save**.
+4. Select the risk behavior you want to modify.
+5. In the drop-down menu, choose your desired risk level.
+6. Select **Save**.
 
 ## Use risk scores in Access policies
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
index c8ace201fdac273..2ce86cab7d6270b 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
@@ -8,10 +8,9 @@ tags:
   - SCIM
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers to synchronize user identity information with cloud applications and services. After configuring SCIM, user identities that you create, edit, or delete in the identity provider are automatically updated across all supported applications. This makes it easier for IT admins to onboard new users, update their groups and permissions, and revoke access in the event of an employee termination or security breach.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
index 1cf937a40bfe8b7..2f4b39bfbcd969d 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 User logs show a list of all users who have authenticated to Cloudflare One. For each user who has logged in, you can view their enrolled devices, login history, seat usage, and identity used for policy enforcement.
 
@@ -20,7 +20,7 @@ This page lists all users who have registered the Cloudflare One Client or authe
 
 ### Available logs
 
-* **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
-* **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
-* **Devices**: Devices registered to the user via the Cloudflare One Client.
-* **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
+- **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
+- **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
+- **Devices**: Devices registered to the user via the Cloudflare One Client.
+- **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
diff --git a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
index 64308a2ccb340c0..f788aa791bdb0b6 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
@@ -38,8 +38,8 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 | Resolve nel.cloudflare.com through 1.1.1.1                                                | `00000001-0034-45a0-8333-f339451fba46` | `nel.cloudflare.com`                                                                                                                                      | resolve |
 | Allow DNS queries for api.cloudflare.com domain                                           | `00000001-5eea-4932-8dd5-8e1ec9770396` | `api.cloudflare.com`                                                                                                                                      | allow   |
 | Resolve api.cloudflare.com through 1.1.1.1                                                | `00000001-4f0c-4f86-9b96-5d26123a194b` | `api.cloudflare.com`                                                                                                                                      | resolve |
-| Allow DNS queries for one.dash.cloudflare.com domain                                    | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                               | allow   |
-| Resolve one.dash.cloudflare.com through 1.1.1.1                                         | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                               | resolve |
+| Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                                 | allow   |
+| Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                                 | resolve |
 | Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-a9fd-40de-a662-51d3a3ae0ad8` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | allow   |
 | Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-70f2-4eea-b711-201bca434ed4` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | resolve |
 | Allow DNS queries for dash.cloudflare.com domain                                          | `00000001-0c2a-4b31-8606-3e5a1d87c1bf` | `dash.cloudflare.com` and `dash.fed.cloudflare.com`                                                                                                       | allow   |
@@ -59,14 +59,14 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 
 ## Network proxy policies
 
-| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                    | Action | Description                                                                                                                                                   |
-| --------------------------------------------------- | -------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                   | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
-| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows Zero Trust client.                                                                                                                                     |
-| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                            | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
+| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                  | Action | Description                                                                                                                                                   |
+| --------------------------------------------------- | -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                 | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
+| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows Zero Trust client.                                                                                                                                     |
+| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                          | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
 | Allow Zero Trust Services                           | `00000001-e1e8-421b-a0fe-895397489f28` | Hostname | `one.dash.cloudflare.com`, `help.teams.cloudflare.com`, `blocked.teams.cloudflare.com`, `blocked.teams.fed.cloudflare.com`, `api.cloudflare.com`, `api.fed.cloudflare.com`, `cloudflarestatus.com`, `www.cloudflarestatus.com`, `one.dash.cloudflare.com`, `one.dash.fed.cloudflare.com`, `help.one.cloudflare.com`, `dash.cloudflare.com`, `dash.fed.cloudflare.com`, and `developers.cloudflare.com` | allow  | Allows Cloudflare Zero Trust services.                                                                                                                        |
-| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
-| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                                | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
+| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
+| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                              | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
 
 ## HTTP inspection policies
 
diff --git a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
index 84848c8086de50c..2df964a6c3a878e 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
@@ -50,15 +50,15 @@ To use HTTP policies to filter all HTTPS traffic on all ports when using a defau
 
 Gateway supports detection and filtering of the following protocols:
 
-| Protocol                                                          | Notes                                                                                        |
-| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| HTTP                                                              | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
-| HTTP2                                                             | Hypertext Transfer Protocol Version 2.                                                       |
-| SSH                                                               | Secure Shell Protocol — remote login and command execution.                                  |
-| TLS                                                               | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
-| DCERPC                                                            | Distributed Computing Environment / Remote Procedure Call.                                   |
-| MQTT                                                              | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
-| TPKT                                                              | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
+| Protocol     | Notes                                                                                        |
+| ------------ | -------------------------------------------------------------------------------------------- |
+| HTTP         | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
+| HTTP2        | Hypertext Transfer Protocol Version 2.                                                       |
+| SSH          | Secure Shell Protocol — remote login and command execution.                                  |
+| TLS          | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
+| DCERPC       | Distributed Computing Environment / Remote Procedure Call.                                   |
+| MQTT         | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
+| TPKT         | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
 | IMAP         | Internet Message Access Protocol — email retrieval.                                          |
 | POP3         | Post Office Protocol v3 — email retrieval.                                                   |
 | SMTP         | Simple Mail Transfer Protocol — email sending.                                               |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
index 61657d39a175ca7..da83a0d0f8b94ed 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
@@ -17,7 +17,7 @@ For Magic Transit egress traffic, consider the following:
 - Network Firewall rules apply to both Magic Transit ingress and egress traffic passing through Cloudflare.
 - If you have a "default drop" catchall rule (a final rule that blocks all traffic not matched by earlier rules) for ingress traffic, you must add an earlier rule to permit traffic sourced from your Magic Transit prefix with the destination as **any** to allow outbound egress traffic.
 
-   For example, place the following allow rule before any default-drop catchall rule:
+  For example, place the following allow rule before any default-drop catchall rule:
 
-   **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
-   **Action**: Allow
+  **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
+  **Action**: Allow
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
index 353d64288db846e..7ad5f83b0ccb97c 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
@@ -22,9 +22,9 @@ There are two approaches for setting up tiered policies, depending on your deplo
 ## Organizations vs. Tenant API
 
 | Feature                    | [Cloudflare Organizations](/cloudflare-one/traffic-policies/tiered-policies/organizations/) | [Tenant API](/cloudflare-one/traffic-policies/tiered-policies/tenant-api/) |
-| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                         |
-| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                          |
-| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                      |
-| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                         |
-| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                                  |
+| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                   |
+| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                    |
+| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                |
+| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                   |
+| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                            |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
index 61dee092052c3ac..558bcf16daff10b 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
@@ -21,7 +21,6 @@ The Tenant API platform only supports [DNS policies](/cloudflare-one/traffic-pol
 
 For more information, refer to the [Cloudflare Zero Trust for managed service providers](https://blog.cloudflare.com/gateway-managed-service-provider/) blog post.
 
-
 ## Get started
 
 To set up the Tenant API, refer to [Get started](/tenant/get-started/). Once you have provisioned and configured your customer's Cloudflare accounts, you can create [DNS policies](/cloudflare-one/traffic-policies/dns-policies/).
diff --git a/src/content/docs/cloudflare-one/troubleshooting/access.mdx b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
index b6396e705f97636..b8ece1182ed0454 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/access.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Access troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/access-controls/troubleshooting/">
-  Full Access troubleshooting guide ❯
+	Full Access troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
index c31dd68373abe7a..e4cf3238d0cd8bd 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Browser Isolation documentation.
 
 <LinkButton href="/cloudflare-one/remote-browser-isolation/troubleshooting/">
-  Browser Isolation troubleshooting ❯
+	Browser Isolation troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
index 064db32c9b01121..72cda8b9e748c03 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full CASB documentation.
 
 <LinkButton href="/cloudflare-one/integrations/cloud-and-saas/troubleshooting/">
-  CASB troubleshooting ❯
+	CASB troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
index 304a4016752f5ba..a15cd8ee067f5b5 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
@@ -32,12 +32,15 @@ For all issues, please include:
 Depending on the product, providing diagnostic files is critical for a technical investigation.
 
 ### Cloudflare One Client (WARP)
+
 If the issue involves the Cloudflare One Client, run the `warp-diag` command on the affected device and attach the resulting `.zip` file to your case. For more information, refer to [Diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/).
 
 ### Cloudflare Tunnel
+
 If the issue involves Cloudflare Tunnel, run the `cloudflared tunnel diag` command and provide the generated report. For more information, refer to [Tunnel diagnostic logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs/).
 
 ### Access and Gateway
+
 For issues related to authentication loops, blocked websites, or policy enforcement:
 
 - **HAR file**: Provide a [HAR file](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file) captured while reproducing the issue.
@@ -46,6 +49,7 @@ For issues related to authentication loops, blocked websites, or policy enforcem
 - **Request ID**: For Gateway issues, you can find the `request_id` (HTTP logs) or `query_id` (DNS logs) in your [Gateway logs](/cloudflare-one/traffic-policies/troubleshooting/).
 
 ### Digital Experience Monitoring (DEX)
+
 For issues with DEX tests or device monitoring, provide a [remote capture](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/) from the Zero Trust dashboard.
 
 ---
diff --git a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
index 731999d5fb8036d..8c96f5ab4305ba3 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full DEX documentation.
 
 <LinkButton href="/cloudflare-one/insights/dex/troubleshooting/">
-  DEX troubleshooting ❯
+	DEX troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
index c84e1260e343735..690763e57e48c08 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Email Security documentation.
 
 <LinkButton href="/cloudflare-one/email-security/troubleshooting/">
-  Email Security troubleshooting ❯
+	Email Security troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
index e38ab6f5acae44e..0d5841ea8bb17d1 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Gateway troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/traffic-policies/troubleshooting/">
-  Full Gateway troubleshooting guide ❯
+	Full Gateway troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
index 1d692f0aa4341e2..eb881c4c7e9300a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
@@ -12,18 +12,25 @@ import { Render, LinkButton } from "~/components";
 
 Explore common issues and solutions for Cloudflare Tunnel.
 
-<Render 
-  file="tunnel/common-errors" 
-  product="cloudflare-one" 
-  params={{
-    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-    protocolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
-    configFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    originServerNameURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    caPoolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    noTLSVerifyURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    ulimitsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/"
-  }} 
+<Render
+	file="tunnel/common-errors"
+	product="cloudflare-one"
+	params={{
+		logsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+		protocolURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
+		configFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		originServerNameURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		caPoolURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		noTLSVerifyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		ulimitsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/",
+	}}
 />
 
 ---
@@ -33,5 +40,5 @@ Explore common issues and solutions for Cloudflare Tunnel.
 For more information, refer to the full Tunnel troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/">
-  Full Tunnel troubleshooting guide ❯
+	Full Tunnel troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
index 82128a0306e3847..4012b24a1e816aa 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
@@ -15,11 +15,16 @@ import { Render, LinkButton } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
 
@@ -30,5 +35,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity/">
-  Full connectivity troubleshooting guide ❯
+	Full connectivity troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
index 0c2b64583258ccf..7cbca452e33919a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 32
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore resources to help you resolve issues with Cloudflare WAN (formerly Magic WAN) connectivity, routing, and tunnel health.
 
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
index 2499d5ff7d77041..2787fccd3b01cf7 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
@@ -8,15 +8,20 @@ sidebar:
   order: 33
 ---
 
-import { Render, LinkButton } from "~/components"
+import { Render, LinkButton } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
 
@@ -27,5 +32,5 @@ import { Render, LinkButton } from "~/components"
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/">
-  Full IPsec troubleshooting guide ❯
+	Full IPsec troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
index 6766ee8164db987..732752846b608d7 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
@@ -11,16 +11,20 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
 
 ---
@@ -30,5 +34,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/">
-  Full routing and BGP guide ❯
+	Full routing and BGP guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
index 4ed284bd72ee49e..b2a3db82e0e9e8d 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
@@ -11,19 +11,26 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
 
 ---
@@ -33,5 +40,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/">
-  Full tunnel health guide ❯
+	Full tunnel health guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
index 4511789b45bde5c..a5fe18d5dcf8599 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare One Client documentation.
 
 <LinkButton href="/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/">
-  Cloudflare One Client troubleshooting ❯
+	Cloudflare One Client troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
index fbfa9dc10b86312..8758982fe37aa85 100644
--- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
+++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
@@ -91,26 +91,26 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
    - `<CLIENT_ID>`: your Entra ID **Application (client) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-   	"$schema": "./node_modules/wrangler/config-schema.json",
-   	"name": "risky-users",
-   	"compatibility_date": "$today",
-   	"main": "src/index.js",
-   	"workers_dev": false,
-   	"account_id": "<ACCOUNT-ID>",
-   	"vars": {
-   		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
-   		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
-   	},
-   	"triggers": {
-   		"crons": ["* * * * *"],
-   	},
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+      	"$schema": "./node_modules/wrangler/config-schema.json",
+      	"name": "risky-users",
+      	"compatibility_date": "$today",
+      	"main": "src/index.js",
+      	"workers_dev": false,
+      	"account_id": "<ACCOUNT-ID>",
+      	"vars": {
+      		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
+      		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
+      	},
+      	"triggers": {
+      		"crons": ["* * * * *"],
+      	},
+      }
+      ```
+   
+      </WranglerConfig>
 
 :::note
 
diff --git a/src/content/docs/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-wan/analytics/index.mdx
index 7591d777198e731..8730a735f15a9f2 100644
--- a/src/content/docs/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/index.mdx
@@ -12,7 +12,8 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
@@ -21,6 +22,6 @@ Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance an
 		traceRoutes: "/cloudflare-wan/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/cloudflare-wan/analytics/query-bandwidth/",
 		graphQlTunnelHealthURL: "/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/"
+		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
index c961a9e26011107..d02a87f11d097c0 100644
--- a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -17,6 +17,7 @@ import { Render } from "~/components";
 	file="mconn/network-options/app-aware-policies/netflow"
 	product="networking-services"
 	params={{
-		breakoutTrafficURL: "/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/"
+		breakoutTrafficURL:
+			"/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
index adb2d9fc1ad3f0a..3694ed5590489c3 100644
--- a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
@@ -13,9 +13,10 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Cloudflare WAN"
+		magicWord: "Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
index 84a4a80f0ea9f2d..34889d808b65f54 100644
--- a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
index f62f8a3cac1ad1a..7ec650366209348 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -6,12 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel bandwidth analytics with GraphQL
 sidebar:
   order: 6
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
index 8c71bfa0ecc6910..2c6eea69fb48cbe 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -6,11 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel health check results with GraphQL
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }} />
+	params={{ productName: "Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
index 8a916f198158f40..a3c3c203418a701 100644
--- a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
@@ -9,21 +9,23 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare WAN network overview
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions: "Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions:
+			"Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "Cloudflare WAN",
 		networkOverviewPageName: "Network overview",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL: "/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
-		}}
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL:
+			"/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
+	}}
 />
 
 ### Set thresholds for site health
@@ -33,6 +35,7 @@ import { Render } from "~/components"
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/changelog.mdx b/src/content/docs/cloudflare-wan/changelog.mdx
index 5e8580b361df863..dab8b24716303bb 100644
--- a/src/content/docs/cloudflare-wan/changelog.mdx
+++ b/src/content/docs/cloudflare-wan/changelog.mdx
@@ -12,7 +12,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/cloudflare-wan/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="cloudflare-wan" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="cloudflare-wan"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2025-02-14
 
@@ -78,4 +81,4 @@ Customers using Gateway to filter traffic to Magic WAN destinations will now see
 
 **Network segmentation**
 
-You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
\ No newline at end of file
+You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index 1ae5d831a62d218..6e7bcd9b792dfd6 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,35 +11,54 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "hardware",
-	productName: "Cloudflare One Appliance",
-	maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "Cloudflare WAN",
-	sfpURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-	wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-	lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-	noConnectorShows: "You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
-	networkSegmentationURL: "/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "The Cloudflare One Appliance is shipped to you deactivated",
-	hardSoftConn: "You need to deploy two Appliances in your premises before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-wan/configuration/appliance/network-options/",
-  maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-  referenceInformationURL: "/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "hardware",
+		productName: "Cloudflare One Appliance",
+		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "Cloudflare WAN",
+		sfpURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+		lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+		noConnectorShows:
+			"You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
+		networkSegmentationURL:
+			"/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage:
+			"The Cloudflare One Appliance is shipped to you deactivated",
+		hardSoftConn:
+			"You need to deploy two Appliances in your premises before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-wan/configuration/appliance/network-options/",
+		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+		referenceInformationURL:
+			"/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index 71ca26721aa0603..b3fa278d08bae29 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,10 +4,8 @@ description: SFP+ port specifications for the hardware Appliance.
 products:
   - cloudflare-wan
 title: SFP+ port information
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info"
-	product="networking-services" />
\ No newline at end of file
+<Render file="mconn/sfp-port-info" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
index c37e1581eefa1cb..8f201a38e5455a4 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
+		troubleshootingURL:
+			"/cloudflare-wan/configuration/appliance/troubleshooting/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
index 2de202a6c0d9a45..ffbd3902d481e2e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,9 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl: "/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl:
+			"/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Cloudflare One Virtual Appliance",
-		virtualUrl: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
+		virtualUrl:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index f2cfc7422c36ccd..75d2c374e500dc1 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -12,6 +12,9 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-		}} />
+		hardwareConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index d4cbc5987d03273..2b74af67e463be6 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
index 071ef98749d5405..967aa8ccb663c13 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/register-hardware-appliance"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)"
+		dashName: "Cloudflare WAN (formerly Magic WAN)",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index b53cd5b9f9965c3..5b789f4f9046d5d 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -12,6 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/remove-connectors"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)"
+		dashName: "Cloudflare WAN (formerly Magic WAN)",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 9bdf18008a25f54..46c95fb5d790192 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,15 +9,18 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "breakout",
-	featureName: "Breakout traffic",
-	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
-	dashName: "Cloudflare WAN",
-	}} />
+		magicWord: "breakout",
+		featureName: "Breakout traffic",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+		whatHappensApp:
+			"will now go directly to the Internet and bypass Cloudflare's filtering",
+		dashName: "Cloudflare WAN",
+	}}
+/>
 
 ## Breakout by source
 
@@ -27,11 +30,11 @@ Source-based breakout is configured via the API and Terraform.
 
 ### Match criteria
 
-| Criterion             | Behavior                                                                                          |
-| --------------------- | ------------------------------------------------------------------------------------------------- |
-| Source LAN interface  | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
-| Source CIDR / IP range| All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
+| Criterion              | Behavior                                                                                                            |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| Source LAN interface   | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
+| Source CIDR / IP range | All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
 
 The same criteria can be used to mark traffic as **prioritized** instead of broken out. Refer to [Prioritized traffic](/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic/) for details.
 
-Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
\ No newline at end of file
+Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 709867b882cbf6b..dce54b18e5ae528 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,11 +9,13 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "prioritized",
-	featureName: "Prioritized traffic",
-	whatHappensApp: "is now processed first by Connector",
-	dashName: "Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "prioritized",
+		featureName: "Prioritized traffic",
+		whatHappensApp: "is now processed first by Connector",
+		dashName: "Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
index 1625f2d8f072527..cdde5b9bfd22fea 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
@@ -20,35 +20,35 @@ DHCP options are configured via the API and Terraform.
 
 Each option is defined by three fields:
 
-| Field           | Description                                         | Example                |
-| --------------- | --------------------------------------------------- | ---------------------- |
-| `option_number` | The DHCP option code (1–254).                       | `67`                   |
-| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                 |
-| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0`  |
+| Field           | Description                                         | Example               |
+| --------------- | --------------------------------------------------- | --------------------- |
+| `option_number` | The DHCP option code (1–254).                       | `67`                  |
+| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                |
+| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0` |
 
 ### Value type encoding
 
-| Type      | Format                                                      | Example value                 |
-| --------- | ----------------------------------------------------------- | ----------------------------- |
-| `ip`      | A dotted-quad IPv4 address.                                 | `10.20.30.40`                 |
-| `integer` | A decimal integer.                                          | `0`                           |
-| `text`    | A UTF-8 string.                                             | `boot/x64/pxelinux.0`         |
-| `hex`     | A colon-separated sequence of bytes, used for sub-options.  | `01:04:aa:bb:cc`              |
+| Type      | Format                                                     | Example value         |
+| --------- | ---------------------------------------------------------- | --------------------- |
+| `ip`      | A dotted-quad IPv4 address.                                | `10.20.30.40`         |
+| `integer` | A decimal integer.                                         | `0`                   |
+| `text`    | A UTF-8 string.                                            | `boot/x64/pxelinux.0` |
+| `hex`     | A colon-separated sequence of bytes, used for sub-options. | `01:04:aa:bb:cc`      |
 
 ## Common PXE / iPXE options
 
 The most frequently used options for PXE / iPXE boot are:
 
-| Option | Type    | Purpose                                                                              |
-| ------ | ------- | ------------------------------------------------------------------------------------ |
-| 60     | `text`  | Vendor class identifier (typically `PXEClient`).                                     |
-| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                                |
-| 67     | `text`  | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).                   |
-| 43     | `hex`   | Vendor-specific information; sub-option layout is vendor-defined.                    |
-| 175    | `hex`   | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more).          |
-| 209    | `text`  | iPXE configuration file URI.                                                         |
-| 210    | `text`  | iPXE configuration file path prefix.                                                 |
-| 211    | `text`  | iPXE configuration file path.                                                        |
+| Option | Type           | Purpose                                                                     |
+| ------ | -------------- | --------------------------------------------------------------------------- |
+| 60     | `text`         | Vendor class identifier (typically `PXEClient`).                            |
+| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                               |
+| 67     | `text`         | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).          |
+| 43     | `hex`          | Vendor-specific information; sub-option layout is vendor-defined.           |
+| 175    | `hex`          | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more). |
+| 209    | `text`         | iPXE configuration file URI.                                                |
+| 210    | `text`         | iPXE configuration file path prefix.                                        |
+| 211    | `text`         | iPXE configuration file path.                                               |
 
 For a complete list of standard DHCP option codes, refer to the [IANA BOOTP/DHCP parameters registry](https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml).
 
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 7a2bc1beac7de02..46f826cc1ad4c6b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,11 +8,13 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-relay"
+<Render
+	file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
+		cfVsCoreDashNamingMwanCni:
+			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
 	}}
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 2d895e9f31c584b..6577eeb5272f5ce 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,9 +8,10 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-server"
+<Render
+	file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN"
+		dashName: "Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index 5c0bcbed619c268..f5fed31c4c5855e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,9 +8,11 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render
+	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
index b651bbe1b01b881..a9f4fad888935fe 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index 3eab8ea9a7bb2bf..2cbcd17985e02d7 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,11 +8,15 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/link-aggregation"
+<Render
+	file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 007bef4f404e26e..8f1cbe1ed9a4b20 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,14 +4,17 @@ products:
   - cloudflare-wan
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Cloudflare One Appliance to re-use address spaces locally.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/nat-subnet"
+<Render
+	file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-	hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-  virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 32603d94e6a92ca..822619f84e0b5cf 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,13 +6,16 @@ title: Network segmentation
 description: Define policies to determine if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/network-segmentation"
+<Render
+	file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index a7d739e9540ba6a..caa93793bc8278e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,15 +4,19 @@ products:
   - cloudflare-wan
 title: Routed subnets
 description: Learn how to configure routed subnets on a Cloudflare One Appliance, including setting static routes and next-hop addresses for complex LAN setups.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/routed-subnets"
+<Render
+	file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL: "/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		netSubnetURL:
+			"/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 0190821520209fd..17809b37e6377e7 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -15,8 +15,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		activateURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL: "/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		activateURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL:
+			"/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index eca36e5f7e8eb4b..bdbd8aaf1e5dec4 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -10,4 +10,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
+<Render
+	file="cloudflare-wan/custom-ike-id-ipsec"
+	product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
index 5e0399f52cb9889..b4d9501da0d4693 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,10 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		greIpsecTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecTunnelsURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		connectorURL: "/cloudflare-wan/configuration/appliance/",
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 9a7d3b257246a34..0432393f1f1c0ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,10 +13,11 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-  file="routing/configure-cloudflare-source-ips"
-  product="networking-services"
-  params={{
-    unifiedRoutingLink: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/"
-  }}
+	file="routing/configure-cloudflare-source-ips"
+	product="networking-services"
+	params={{
+		unifiedRoutingLink:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 8335fb6e9cf3559..e5b02b3a5366e73 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 2
 head: []
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -19,17 +18,23 @@ import { Render } from "~/components"
 		magicWord: "Cloudflare WAN",
 		trafficSteeringPage: "/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization:
+			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		addTunnelsURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table"
+		routingTableName: "Cloudflare Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 41b3800804ce8c9..9fb7c93867e3747 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -11,26 +11,36 @@ description: Learn how to configure IPsec or GRE tunnels for Cloudflare WAN.
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/cloudflare-wan/reference/anti-replay-protection/",
 		cniLink: "/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthDash:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
+		configureARRURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
index 4a554e27b3969b6..9e7d62f8d1aeab1 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
index ac5910dadeb36ca..38b42c7e4dd0350 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -16,8 +16,9 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-wan/configuration/index.mdx
index 13702b827029038..5ddfb172a16c533 100644
--- a/src/content/docs/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
index 76af852c660c808..4a444cbdbff83f9 100644
--- a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
@@ -17,6 +17,7 @@ import { Render } from "~/components";
 	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
 	params={{
-		mwanAccount: "Have a Multi-Cloud Networking account. Contact your account team to learn more.",
+		mwanAccount:
+			"Have a Multi-Cloud Networking account. Contact your account team to learn more.",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index bb10e2869c1ee67..ff1a38a9ff1a28e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -4,15 +4,19 @@ pcx_content_type: integration-guide
 description: Connect Alibaba Cloud VPN Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/alibaba-cloud"
-  product="networking-services"
-  params={{
-    ipSecTunnelsUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/alibaba-cloud"
+	product="networking-services"
+	params={{
+		ipSecTunnelsUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
index f9028eefecd609a..58ce92bd34520fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
@@ -4,14 +4,17 @@ description: Connect Amazon AWS Transit Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Amazon AWS Transit Gateway
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aws"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/aws"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index f041179a7d471bc..a76d15bdf214c1a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -8,11 +8,16 @@ title: Microsoft Azure Virtual WAN
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-virtual-wan"
-  product="networking-services"
-  params={{
-  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  cloudflareDocumentationUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-virtual-wan"
+	product="networking-services"
+	params={{
+		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+		ipsecTunnelUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		cloudflareDocumentationUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index 79e3ab4a2c3e78e..f424bafbae91997 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -8,11 +8,16 @@ title: Microsoft Azure VPN Gateway
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
-  product="networking-services"
-  params={{
-  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  staticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-vpn-gateway"
+	product="networking-services"
+	params={{
+		ipsecTunnelUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
index be31f60acc7149a..2cc5b0788919598 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -9,8 +9,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index cba0f106bf12657..8831ea12bbf6ea5 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -4,11 +4,11 @@ description: Connect Cisco IOS XE to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Cisco IOS XE
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-ios-xe"
-  product="networking-services"
+<Render
+	file="cloudflare-wan/third-party/cisco-ios-xe"
+	product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 896e02c855659fd..4191b38bc630e29 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -8,15 +8,22 @@ title: Cisco Meraki MX (static routing)
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render
+	file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl: "/cloudflare-wan/reference/anti-replay-protection/",
+		antiReplayProtectionUrl:
+			"/cloudflare-wan/reference/anti-replay-protection/",
 		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		unifiedRoutingUrl:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		trafficSteeringUrl: "/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedConfigParametersUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		paloAltoGuideUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-	}} />
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
index e28d8ba4847ab6f..4ab6dfd8b7b76e9 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -4,15 +4,19 @@ description: Connect Furukawa Electric FITELnet to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Furukawa Electric FITELnet
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fitelnet"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    typeId_ipv4_addrUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fitelnet"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		typeId_ipv4_addrUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
index 5a12895743cb66e..cf11763d0a341ab 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -8,12 +8,19 @@ title: Fortinet
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fortinet"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    equalCostMultipathRoutingEcmpUrl: "/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fortinet"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		equalCostMultipathRoutingEcmpUrl:
+			"/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
index 6f89300b8494e05..2ae56b6dbe49b81 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
@@ -4,14 +4,17 @@ description: Connect Google Cloud VPN to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Google Cloud VPN
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/google"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/google"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
index f6e508d000a5d0d..c73eca34c84c602 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
index 3818804b0252018..85e683e79c81b16 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,10 +10,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/juniper"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/juniper"
+	product="networking-services"
+	params={{
+		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
index 78849f6cad28825..1f2ddeaeeefca8f 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -4,14 +4,17 @@ description: Connect Oracle Cloud to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Oracle Cloud
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/oracle"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/oracle"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
index 110c15959491f36..a95d9f3fabecc02 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,10 +13,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/palo-alto"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/palo-alto"
+	product="networking-services"
+	params={{
+		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
index d86dc81c4715843..862ad0f4b4e8284 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -5,15 +5,19 @@ products:
   - cloudflare-wan
 title: pfSense
 reviewed: 2024-06-20
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/pfsense"
-  product="networking-services"
-  params={{
-    configureTwoIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    staticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/pfsense"
+	product="networking-services"
+	params={{
+		configureTwoIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		staticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 26a76c80f25db4e..536b6c9ff0ab552 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -4,16 +4,21 @@ pcx_content_type: integration-guide
 description: Connect SonicWall to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sonicwall"
-  product="networking-services"
-  params={{
-    ipsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    creatingYourIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createYourStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sonicwall"
+	product="networking-services"
+	params={{
+		ipsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		creatingYourIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createYourStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index b6d0e9a1f52a074..1d3ab31ab967c03 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -4,16 +4,21 @@ pcx_content_type: integration-guide
 description: Connect Sophos Firewall to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sophos-firewall"
-  product="networking-services"
-  params={{
-    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    ikeIdUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sophos-firewall"
+	product="networking-services"
+	params={{
+		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		ikeIdUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
index fc4d45f5469a352..bac9233cb7a5f21 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -4,13 +4,15 @@ description: Connect strongSwan to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: strongSwan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/strongswan"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/strongswan"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 868c273f24c50f6..5f49238ade5259c 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -9,9 +9,9 @@ title: Ubiquiti
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-wan/third-party/ubiquiti"
-  product="networking-services"
-  params={{
-    magicWord: "Cloudflare WAN",
-  }}
+	file="cloudflare-wan/third-party/ubiquiti"
+	product="networking-services"
+	params={{
+		magicWord: "Cloudflare WAN",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
index fc2441a6857269e..03266a7985edc32 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -4,13 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Velocloud to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/velocloud"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/velocloud"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
index b6b97c01cebaf9d..cbcaa056c559724 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -4,15 +4,18 @@ pcx_content_type: integration-guide
 description: Connect Cisco SD-WAN to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/viptela"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/viptela"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
index 0ccbceefbb7c339..da8b1fef607c6af 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -8,6 +8,4 @@ title: VyOS
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos"
-  product="networking-services"
-/>
+<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
index c117c2a4435efd5..3e0e9e8caca4dee 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -8,9 +8,13 @@ title: Yamaha RTX Router
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/yamaha"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/yamaha"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-wan/get-started.mdx
index b2f98f780c0e192..50110e083ff7170 100644
--- a/src/content/docs/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-wan/get-started.mdx
@@ -17,11 +17,14 @@ import { Render } from "~/components";
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
 		configureConnectorUrl: "/cloudflare-wan/configuration/appliance/",
-		configureMwanManually: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureMwanManually:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		greReferenceURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		ipsecReferenceUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		mtuReferenceURL: "/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-wan/wan-transformation/"
+		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/glossary.mdx b/src/content/docs/cloudflare-wan/glossary.mdx
index 9707d04db10e16a..5b50582a0620f31 100644
--- a/src/content/docs/cloudflare-wan/glossary.mdx
+++ b/src/content/docs/cloudflare-wan/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-wan
 sidebar:
   order: 14
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare WAN (formerly Magic WAN) documentation.
 
diff --git a/src/content/docs/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-wan/index.mdx
index 5eac1897c216694..9a0cea6bca082c4 100644
--- a/src/content/docs/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-wan/index.mdx
@@ -27,8 +27,9 @@ import { Render } from "~/components";
 		connectorUrl: "/cloudflare-wan/configuration/appliance/",
 		thirdPartyUrl: "/cloudflare-wan/configuration/third-party/",
 		zeroTrustUrl: "/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		bgpRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
 		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/"
+		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
index de5decbd83487cb..9d694953eaa9562 100644
--- a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
@@ -5,10 +5,9 @@ pcx_content_type: reference
 description: Third-party licenses used in Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import text from "./3rdparty.txt?raw";
 import { Markdown } from "~/components";
 
-<Markdown text={text} inline={false} />
\ No newline at end of file
+<Markdown text={text} inline={false} />
diff --git a/src/content/docs/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-wan/legal/index.mdx
index e2e9dc5f914a078..907e5abf6f28688 100644
--- a/src/content/docs/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-wan/legal/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 12
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-wan/network-interconnect.mdx
index 2f3024d241fa36f..86be9e7f16b6297 100644
--- a/src/content/docs/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-wan/network-interconnect.mdx
@@ -13,14 +13,20 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
+<Render
+	file="magic-cni"
+	product="networking-services"
+	params={{ magicWord: "Cloudflare WAN" }}
+/>
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/"
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-wan/on-ramps.mdx
index 86da6b248ebe042..32fdec0f6eabfab 100644
--- a/src/content/docs/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-wan/on-ramps.mdx
@@ -22,6 +22,6 @@ import { Render } from "~/components";
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/"
+		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
index a081ee8130d1870..9ed3368c2c98be2 100644
--- a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -4,7 +4,8 @@ products:
   - cloudflare-wan
 title: Anti-replay protection
 head: []
-description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description:
+  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
index fbec0cd8573df1d..cc92b6c823ab972 100644
--- a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
index a504caad9990939..dbcdf9a17252a75 100644
--- a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
@@ -10,29 +10,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/reference/device-compatibility"
-  product="networking-services"
-  params={{
-    supportedConfigurationParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    arubaEdgeconnectUrl: "/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-    ciscoMerakiStaticUrl: "/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-    ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
-    fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
-    fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
-    juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
-    paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-    pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
-    sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
-    sophosFirewallUrl: "/cloudflare-wan/configuration/third-party/sophos-firewall/",
-    strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
-    ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
-    velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
-    vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
-    yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
-    alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-    awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
-    azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
-    googleUrl: "/cloudflare-wan/configuration/third-party/google/",
-    oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/"
-  }} />
+<Render
+	file="cloudflare-wan/reference/device-compatibility"
+	product="networking-services"
+	params={{
+		supportedConfigurationParametersUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		arubaEdgeconnectUrl:
+			"/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+		ciscoMerakiStaticUrl:
+			"/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+		ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
+		fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
+		fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
+		juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
+		paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
+		pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
+		sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
+		sophosFirewallUrl:
+			"/cloudflare-wan/configuration/third-party/sophos-firewall/",
+		strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
+		ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
+		velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
+		vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
+		yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
+		alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+		awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
+		azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
+		googleUrl: "/cloudflare-wan/configuration/third-party/google/",
+		oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 68d4b4a66826115..6cf088b347f6d36 100644
--- a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -20,12 +20,14 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		mssURL: "/cloudflare-wan/get-started/#set-maximum-segment-size",
 		productURL: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 6a4cb0f5b700132..0251f5066fd362c 100644
--- a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,12 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down" }}
+	params={{
+		tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-wan/reference/index.mdx
index ae239f4ddfc37af..1de78f741d45c97 100644
--- a/src/content/docs/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-wan/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
index c0e144ba5def202..433a4d677c2c8b1 100644
--- a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN"
-		}}
-/>
\ No newline at end of file
+		productName: "Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
index 5f34c73baea554a..9d1d78aca887206 100644
--- a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
@@ -23,7 +23,8 @@ import { Render } from "~/components";
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
index 98d45cc88d50519..af8dd8496a2775f 100644
--- a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -17,12 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		addTunnels: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
 		staticRoutes: "/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
index cb97c92d8e4803d..7a88bf96e8c4a54 100644
--- a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
@@ -15,11 +15,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
+		configureRoutesURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
 		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		privateNetworksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-wan/security.mdx
index 20d951ee8b334c0..8a6e3df9eaad074 100644
--- a/src/content/docs/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-wan/security.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="cloudflare-wan/security-filters"
+<Render
+	file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/"
+		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
index a190ec5d61db5ed..220b98e58c0e0a5 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
 		routingBgpLink: "/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		checkHealthDashLink:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
index 905787c40bc06f3..5d7bf235ac3cb37 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 13
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 274a58ce5258d51..dc1236e65423f20 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -8,14 +8,16 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/"
+		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index ed25cd90faf8949..a43339acccd25e2 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -11,14 +11,16 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 807fee1aad43dc6..485d6bb04a1e428 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -11,17 +11,21 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index ad22094662587ee..095f4976ce553d9 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -13,10 +13,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
+		trafficSteeringURL:
+			"/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
index 7a6e010f13f8f63..566bc65d5095477 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
@@ -11,13 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-one-connectivity-options"
-  product="networking-services"
-  params={{
-    unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-    connectorURL: "/cloudflare-wan/configuration/appliance/",
-    cniURL: "/cloudflare-wan/network-interconnect/",
-    onRampsURL: "/cloudflare-wan/on-ramps/"
-  }}
+	file="cloudflare-one-connectivity-options"
+	product="networking-services"
+	params={{
+		unifiedRoutingURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		connectorURL: "/cloudflare-wan/configuration/appliance/",
+		cniURL: "/cloudflare-wan/network-interconnect/",
+		onRampsURL: "/cloudflare-wan/on-ramps/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
index 039a590ad02f2f0..52b072c14394b76 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
@@ -8,9 +8,9 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare One integration tutorials
-description: Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
+description:
+  Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
   Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/constellation/platform/index.mdx b/src/content/docs/constellation/platform/index.mdx
index 8d627d53915bd45..1b6cdafb1ff1640 100644
--- a/src/content/docs/constellation/platform/index.mdx
+++ b/src/content/docs/constellation/platform/index.mdx
@@ -7,6 +7,6 @@ products:
   - constellation
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/containers/examples/cron.mdx b/src/content/docs/containers/examples/cron.mdx
index beb5c71d036990a..fa89b747782586a 100644
--- a/src/content/docs/containers/examples/cron.mdx
+++ b/src/content/docs/containers/examples/cron.mdx
@@ -57,32 +57,37 @@ Use a cron expression in your Wrangler config to specify the schedule:
 Then in your Worker, call your Container from the "scheduled" handler:
 
 ```ts
-import { Container, getContainer } from '@cloudflare/containers';
+import { Container, getContainer } from "@cloudflare/containers";
 
 export class CronContainer extends Container {
-  sleepAfter = '10s';
+	sleepAfter = "10s";
 
-  override onStart() {
-    console.log('Starting container');
-  }
+	override onStart() {
+		console.log("Starting container");
+	}
 
-  override onStop() {
-    console.log('Container stopped');
-  }
+	override onStop() {
+		console.log("Container stopped");
+	}
 }
 
 export default {
-  async fetch(): Promise<Response> {
-    return new Response("This Worker runs a cron job to execute a container on a schedule.");
-  },
+	async fetch(): Promise<Response> {
+		return new Response(
+			"This Worker runs a cron job to execute a container on a schedule.",
+		);
+	},
 
-  async scheduled(_controller: any, env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> }) {
-    let container = getContainer(env.CRON_CONTAINER);
-    await container.start({
-      envVars: {
+	async scheduled(
+		_controller: any,
+		env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> },
+	) {
+		let container = getContainer(env.CRON_CONTAINER);
+		await container.start({
+			envVars: {
 				MESSAGE: "Start Time: " + new Date().toISOString(),
-      }
-    })
-  },
+			},
+		});
+	},
 };
 ```
diff --git a/src/content/docs/containers/examples/durable-object-interface.mdx b/src/content/docs/containers/examples/durable-object-interface.mdx
index f957451fa12358b..d54c84506542fc7 100644
--- a/src/content/docs/containers/examples/durable-object-interface.mdx
+++ b/src/content/docs/containers/examples/durable-object-interface.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Various examples calling Containers directly from Durable Objects
 pcx_content_type: example
 title: Using Durable Objects Directly
diff --git a/src/content/docs/containers/examples/index.mdx b/src/content/docs/containers/examples/index.mdx
index eb6ca3b44e7d6f7..5cf608f97ac0ecc 100644
--- a/src/content/docs/containers/examples/index.mdx
+++ b/src/content/docs/containers/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: false
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/containers/platform-details/placement.mdx b/src/content/docs/containers/platform-details/placement.mdx
index bcb40145e1c38a1..67d5a76095272fe 100644
--- a/src/content/docs/containers/platform-details/placement.mdx
+++ b/src/content/docs/containers/platform-details/placement.mdx
@@ -34,10 +34,10 @@ Limited capacity regions (ME, OC, AFR) cannot be used exclusively. Include at le
 
 Use the `jurisdiction` constraint to restrict containers to compliance boundaries:
 
-| Jurisdiction | Regions    | Use case           |
-| ------------ | ---------- | ------------------ |
-| `eu`         | EEUR, WEUR | EU data residency  |
-| `fedramp`    | ENAM, WNAM | FedRAMP regions    |
+| Jurisdiction | Regions    | Use case          |
+| ------------ | ---------- | ----------------- |
+| `eu`         | EEUR, WEUR | EU data residency |
+| `fedramp`    | ENAM, WNAM | FedRAMP regions   |
 
 When you specify both `jurisdiction` and `regions`, the regions must be valid for that jurisdiction. For example, specifying `jurisdiction: "eu"` with `regions: ["ENAM"]` is invalid.
 
diff --git a/src/content/docs/containers/pricing.mdx b/src/content/docs/containers/pricing.mdx
index a26fc07ae355276..504db4e7c197e95 100644
--- a/src/content/docs/containers/pricing.mdx
+++ b/src/content/docs/containers/pricing.mdx
@@ -22,7 +22,7 @@ Containers are billed for every 10ms that they are actively running at the follo
 
 You only pay for what you use — charges start when a request is sent to the container or when it is manually started. Charges stop after the container instance goes to sleep, which can happen automatically after a timeout. This makes it easy to scale to zero, and allows you to get high utilization even with bursty traffic.
 
-Memory and disk usage are based on the *provisioned resources* for the instance type you select, while CPU usage is based on *active usage* only.
+Memory and disk usage are based on the _provisioned resources_ for the instance type you select, while CPU usage is based on _active usage_ only.
 
 #### Instance Types
 
diff --git a/src/content/docs/containers/ssh.mdx b/src/content/docs/containers/ssh.mdx
index fab40ae97a43594..bc91bd0cdc3968d 100644
--- a/src/content/docs/containers/ssh.mdx
+++ b/src/content/docs/containers/ssh.mdx
@@ -58,4 +58,4 @@ wrangler containers ssh <INSTANCE_ID>
 
 ## Process visibility
 
-Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
\ No newline at end of file
+Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
diff --git a/src/content/docs/d1/best-practices/local-development.mdx b/src/content/docs/d1/best-practices/local-development.mdx
index f6f28cdf1259255..a225fec2f2d3b74 100644
--- a/src/content/docs/d1/best-practices/local-development.mdx
+++ b/src/content/docs/d1/best-practices/local-development.mdx
@@ -137,8 +137,6 @@ Users of wrangler `2.x` must use the `--persist` flag: previous versions of wran
 
 You can use Miniflare's [support for D1](https://miniflare.dev/storage/d1) to create D1 databases you can use for testing:
 
-
-
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/d1/best-practices/query-d1.mdx b/src/content/docs/d1/best-practices/query-d1.mdx
index 74e5a405162b2c2..6f4eddbd73c830b 100644
--- a/src/content/docs/d1/best-practices/query-d1.mdx
+++ b/src/content/docs/d1/best-practices/query-d1.mdx
@@ -52,15 +52,16 @@ Given the following JSON object (`type:blob`) in a column named `sensor_reading`
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
+
 ```sql
 -- Extract the temperature value
 SELECT json_extract(sensor_reading, '$.measurement.temp_f')-- returns "77.4" as TEXT
@@ -80,22 +81,24 @@ This requires you to:
 
 ```js title="index.js"
 export default {
-    async fetch(request, env) {
-        const {pathname} = new URL(request.url);
-        const companyName1 = `Bs Beverages`;
-        const companyName2 = `Around the Horn`;
-        const stmt = env.DB.prepare(`SELECT * FROM Customers WHERE CompanyName = ?`);
-
-        if (pathname === `/RUN`) {
-            const returnValue = await stmt.bind(companyName1).run();
-            return Response.json(returnValue);
-        }
-
-        return new Response(
-            `Welcome to the D1 API Playground!
+	async fetch(request, env) {
+		const { pathname } = new URL(request.url);
+		const companyName1 = `Bs Beverages`;
+		const companyName2 = `Around the Horn`;
+		const stmt = env.DB.prepare(
+			`SELECT * FROM Customers WHERE CompanyName = ?`,
+		);
+
+		if (pathname === `/RUN`) {
+			const returnValue = await stmt.bind(companyName1).run();
+			return Response.json(returnValue);
+		}
+
+		return new Response(
+			`Welcome to the D1 API Playground!
 						\nChange the URL to test the various methods inside your index.js file.`,
-        );
-    },
+		);
+	},
 };
 ```
 
@@ -114,6 +117,7 @@ You can use Wrangler commands to query a D1 database. Note that Wrangler command
 ```sh
 npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ```
+
 ```sh output
 🌀 Mapping SQL input into an array of statements
 🌀 Executing on local database production-db-backend (<DATABASE_ID>) from .wrangler/state/v3/d1:
@@ -128,4 +132,4 @@ npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ├────────────┼─────────────────────┼───────────────────┤
 │ 13         │ Bs Beverages        │ Random Name       │
 └────────────┴─────────────────────┴───────────────────┘
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/d1/best-practices/remote-development.mdx b/src/content/docs/d1/best-practices/remote-development.mdx
index 40be666bf1fb1f5..4efe9586181686f 100644
--- a/src/content/docs/d1/best-practices/remote-development.mdx
+++ b/src/content/docs/d1/best-practices/remote-development.mdx
@@ -17,17 +17,16 @@ D1 supports remote development using the [dashboard playground](/workers/playgro
 
 :::note
 
-
 This guide assumes you have previously created a Worker, and a D1 database.
 
 Users new to D1 and/or Cloudflare Workers should read the [D1 tutorial](/d1/get-started/) to install `wrangler` and deploy their first database.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select an existing Worker.
 3. Go to the **Bindings** tab.
 4. Select **Add binding**.
@@ -44,14 +43,14 @@ Use the following Worker script to verify that the Worker has access to the boun
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    const res = await env.DB.prepare("SELECT 1;").run();
-    return new Response(JSON.stringify(res, null, 2));
-  },
+	async fetch(request, env, ctx) {
+		const res = await env.DB.prepare("SELECT 1;").run();
+		return new Response(JSON.stringify(res, null, 2));
+	},
 };
 ```
 
 ## Related resources
 
-* Learn [how to debug D1](/d1/observability/debug-d1/).
-* Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
+- Learn [how to debug D1](/d1/observability/debug-d1/).
+- Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
diff --git a/src/content/docs/d1/best-practices/retry-queries.mdx b/src/content/docs/d1/best-practices/retry-queries.mdx
index 02bc218ed30d67e..0dafe17addbbd3c 100644
--- a/src/content/docs/d1/best-practices/retry-queries.mdx
+++ b/src/content/docs/d1/best-practices/retry-queries.mdx
@@ -27,20 +27,20 @@ You can use libraries abstracting that already like [`@cloudflare/actors`](https
 import { tryWhile } from "@cloudflare/actors";
 
 function queryD1Example(d1: D1Database, sql: string) {
-  return await tryWhile(async () => {
-    return await d1.prepare(sql).run();
-  }, shouldRetry);
+	return await tryWhile(async () => {
+		return await d1.prepare(sql).run();
+	}, shouldRetry);
 }
 
 function shouldRetry(err: unknown, nextAttempt: number) {
-  const errMsg = String(err);
-  const isRetryableError =
-    errMsg.includes("Network connection lost") ||
-    errMsg.includes("storage caused object to be reset") ||
-    errMsg.includes("reset because its code was updated");
-  if (nextAttempt <= 5 && isRetryableError) {
-    return true;
-  }
-  return false;
+	const errMsg = String(err);
+	const isRetryableError =
+		errMsg.includes("Network connection lost") ||
+		errMsg.includes("storage caused object to be reset") ||
+		errMsg.includes("reset because its code was updated");
+	if (nextAttempt <= 5 && isRetryableError) {
+		return true;
+	}
+	return false;
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
index cf575cec298ffee..5ba46a35c327eba 100644
--- a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
+++ b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
@@ -7,5 +7,5 @@ sidebar:
   order: 11
 products:
   - d1
-  - pages  
+  - pages
 ---
diff --git a/src/content/docs/d1/best-practices/use-indexes.mdx b/src/content/docs/d1/best-practices/use-indexes.mdx
index dc25d04079a3170..b363212f5718cc1 100644
--- a/src/content/docs/d1/best-practices/use-indexes.mdx
+++ b/src/content/docs/d1/best-practices/use-indexes.mdx
@@ -16,9 +16,9 @@ Indexes enable D1 to improve query performance over the indexed columns for comm
 
 Indexes are useful:
 
-* When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
-* For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
-* In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
+- When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
+- For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
+- In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
 
 Indexes are automatically updated when the table and column(s) they reference are inserted, updated or deleted. You do not need to manually update an index after you write to the table it references.
 
@@ -114,7 +114,7 @@ Using an index can reduce the number of rows read by a query. Use the `meta` obj
 
 ## Multi-column indexes
 
-For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either *all* of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
+For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either _all_ of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
 
 Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions(customer_id, transaction_date)`, the following table shows when the index is used (or not):
 
@@ -126,16 +126,16 @@ Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions
 
 Notes:
 
-* If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
-* With the same index, a query that uses only `transaction_date` and `shipping_status` would *not* use the index, as you have not used `customer_id` (the leftmost column) in the query.
+- If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
+- With the same index, a query that uses only `transaction_date` and `shipping_status` would _not_ use the index, as you have not used `customer_id` (the leftmost column) in the query.
 
 ## Partial indexes
 
 Partial indexes are indexes over a subset of rows in a table. Partial indexes are defined by the use of a `WHERE` clause when creating the index. A partial index can be useful to omit certain rows, such as those where values are `NULL` or where rows with a specific value are present across queries.
 
-* A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
-* This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
-* Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
+- A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
+- This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
+- Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
 
 A partial index that filters out completed orders from the index would resemble the following:
 
@@ -153,7 +153,7 @@ Use `DROP INDEX` to remove an index. Dropped indexes cannot be restored.
 
 Take note of the following considerations when creating indexes:
 
-* Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
-* You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
-* Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
-* Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
+- Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
+- You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
+- Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
+- Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
diff --git a/src/content/docs/d1/configuration/environments.mdx b/src/content/docs/d1/configuration/environments.mdx
index d006e54c8c8878d..9211ae269c77fa0 100644
--- a/src/content/docs/d1/configuration/environments.mdx
+++ b/src/content/docs/d1/configuration/environments.mdx
@@ -78,22 +78,20 @@ Therefore, the above binding is equivalent to:
 
 ```json
 {
-  "production": {
-    "d1_databases": [
-      {
-        "binding": "DB",
-        "database_name": "DATABASE_NAME",
-        "database_id": "DATABASE_ID"
-      }
-    ]
-  }
+	"production": {
+		"d1_databases": [
+			{
+				"binding": "DB",
+				"database_name": "DATABASE_NAME",
+				"database_id": "DATABASE_ID"
+			}
+		]
+	}
 }
 ```
 
 ### Example
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -127,25 +125,25 @@ The above is equivalent to the following structure in JSON:
 
 ```json
 {
-  "env": {
-    "production": {
-      "d1_databases": [
-        {
-          "binding": "BINDING_NAME_2",
-          "database_id": "UUID_2",
-          "database_name": "DATABASE_NAME_2"
-        }
-      ]
-    },
-    "staging": {
-      "d1_databases": [
-        {
-          "binding": "BINDING_NAME_1",
-          "database_id": "UUID_1",
-          "database_name": "DATABASE_NAME_1"
-        }
-      ]
-    }
-  }
+	"env": {
+		"production": {
+			"d1_databases": [
+				{
+					"binding": "BINDING_NAME_2",
+					"database_id": "UUID_2",
+					"database_name": "DATABASE_NAME_2"
+				}
+			]
+		},
+		"staging": {
+			"d1_databases": [
+				{
+					"binding": "BINDING_NAME_1",
+					"database_id": "UUID_1",
+					"database_name": "DATABASE_NAME_1"
+				}
+			]
+		}
+	}
 }
 ```
diff --git a/src/content/docs/d1/get-started.mdx b/src/content/docs/d1/get-started.mdx
index c5ee956264ad848..5d22a0fe3363f7c 100644
--- a/src/content/docs/d1/get-started.mdx
+++ b/src/content/docs/d1/get-started.mdx
@@ -9,7 +9,17 @@ products:
   - d1
 ---
 
-import { Render, PackageManagers, Steps, FileTree, Tabs, TabItem, TypeScriptExample, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	FileTree,
+	Tabs,
+	TabItem,
+	TypeScriptExample,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 This guide instructs you through:
 
diff --git a/src/content/docs/d1/observability/billing.mdx b/src/content/docs/d1/observability/billing.mdx
index 31ef2103ba9196a..1a4a8d3fffc9712 100644
--- a/src/content/docs/d1/observability/billing.mdx
+++ b/src/content/docs/d1/observability/billing.mdx
@@ -21,6 +21,7 @@ Total account billable usage analytics for D1 are available in the Cloudflare da
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
    <DashButton url="/?to=/:account/billing" />
+
 2. Go to **Billable Usage**.
 
 From here you can view charts of your account's D1 usage on a daily or month-to-date timeframe.
@@ -32,5 +33,6 @@ Note that billable usage history is stored for a maximum of 30 days.
 Usage-based billing notifications are available within the [Cloudflare dashboard](https://dash.cloudflare.com) for users looking to monitor their total account usage.
 
 Notifications on the following metrics are available:
+
 - Rows Read
-- Rows Written
\ No newline at end of file
+- Rows Written
diff --git a/src/content/docs/d1/platform/limits.mdx b/src/content/docs/d1/platform/limits.mdx
index 4c61da8679fd68e..21cb95db52dfab3 100644
--- a/src/content/docs/d1/platform/limits.mdx
+++ b/src/content/docs/d1/platform/limits.mdx
@@ -10,24 +10,24 @@ products:
 
 import { Render } from "~/components";
 
-| Feature                                                                                                             | Limit                                             |
-| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| Databases per account                                                                                               | 50,000 (Workers Paid) [^1] / 10 (Free)            |
-| Maximum database size                                                                                               | 10 GB (Workers Paid) / 500 MB (Free)              |
-| Maximum storage per account                                                                                         | 1 TB (Workers Paid) [^2] / 5 GB (Free)             |
-| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                                         | 30 days (Workers Paid) / 7 days (Free)            |
-| Maximum Time Travel restore operations                                                                              | 10 restores per 10 minutes (per database)          |
+| Feature                                                                                         | Limit                                             |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| Databases per account                                                                           | 50,000 (Workers Paid) [^1] / 10 (Free)            |
+| Maximum database size                                                                           | 10 GB (Workers Paid) / 500 MB (Free)              |
+| Maximum storage per account                                                                     | 1 TB (Workers Paid) [^2] / 5 GB (Free)            |
+| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                     | 30 days (Workers Paid) / 7 days (Free)            |
+| Maximum Time Travel restore operations                                                          | 10 restores per 10 minutes (per database)         |
 | Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#subrequests)) | 1000 (Workers Paid) / 50 (Free)                   |
-| Maximum number of columns per table                                                                                 | 100                                               |
-| Maximum number of rows per table                                                                                    | Unlimited (excluding per-database storage limits) |
-| Maximum string, `BLOB` or table row size                                                                            | 2,000,000 bytes (2 MB)                            |
-| Maximum SQL statement length                                                                                        | 100,000 bytes (100 KB)                            |
-| Maximum bound parameters per query                                                                                  | 100                                               |
-| Maximum arguments per SQL function                                                                                  | 32                                                |
-| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                                            | 50 bytes                                          |
-| Maximum bindings per Workers script                                                                                 | Approximately 5,000 [^3]                          |
-| Maximum SQL query duration                                                                                          | 30 seconds [^4]                                   |
-| Maximum file import (`d1 execute`) size                                                                             | 5 GB [^5]                                         |
+| Maximum number of columns per table                                                             | 100                                               |
+| Maximum number of rows per table                                                                | Unlimited (excluding per-database storage limits) |
+| Maximum string, `BLOB` or table row size                                                        | 2,000,000 bytes (2 MB)                            |
+| Maximum SQL statement length                                                                    | 100,000 bytes (100 KB)                            |
+| Maximum bound parameters per query                                                              | 100                                               |
+| Maximum arguments per SQL function                                                              | 32                                                |
+| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                        | 50 bytes                                          |
+| Maximum bindings per Workers script                                                             | Approximately 5,000 [^3]                          |
+| Maximum SQL query duration                                                                      | 30 seconds [^4]                                   |
+| Maximum file import (`d1 execute`) size                                                         | 5 GB [^5]                                         |
 
 :::note[Batch limits]
 Limits for individual queries (listed above) apply to each individual statement contained within a batch statement. For example, the maximum SQL statement length of 100 KB applies to each statement inside a `db.batch()`.
diff --git a/src/content/docs/d1/reference/community-projects.mdx b/src/content/docs/d1/reference/community-projects.mdx
index a095bb554ffe1f5..2974e7452d65edb 100644
--- a/src/content/docs/d1/reference/community-projects.mdx
+++ b/src/content/docs/d1/reference/community-projects.mdx
@@ -12,10 +12,8 @@ Members of the Cloudflare developer community and broader developer ecosystem ha
 
 :::note
 
-
 Community projects are not maintained by the Cloudflare D1 team. They are managed and updated by the project authors.
 
-
 :::
 
 ## Projects
@@ -37,57 +35,57 @@ knex-cloudflare-d1 is the Cloudflare D1 dialect for Knex.js. Note that this is n
 
 [Prisma ORM](https://www.prisma.io/orm) is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to its intuitive data model, automated migrations, type-safety and auto-completion.
 
-* [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
-* [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
+- [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
+- [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
 
 ### D1 adapter for Kysely ORM
 
 Kysely is a type-safe and autocompletion-friendly typescript SQL query builder. With this adapter you can interact with D1 with the familiar Kysely interface.
 
-* [Kysely GitHub](https://github.com/koskimas/kysely)
-* [D1 adapter](https://github.com/aidenwallis/kysely-d1)
+- [Kysely GitHub](https://github.com/koskimas/kysely)
+- [D1 adapter](https://github.com/aidenwallis/kysely-d1)
 
 ### feathers-kysely
 
 The `feathers-kysely` database adapter follows the FeathersJS Query Syntax standard and works with any framework. It is built on the D1 adapter for Kysely and supports passing queries directly from client applications. Since the FeathersJS query syntax is a subset of MongoDB's syntax, this is a great tool for MongoDB users to use Cloudflare D1 without previous SQL experience.
 
-* [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
-* [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
+- [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
+- [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
 
 ### Drizzle ORM
 
 Drizzle is a headless TypeScript ORM with a head which runs on Node, Bun and Deno. Drizzle ORM lives on the Edge and it is a JavaScript ORM too. It comes with a drizzle-kit CLI companion for automatic SQL migrations generation. Drizzle automatically generates your D1 schema based on types you define in TypeScript, and exposes an API that allows you to query your database directly.
 
-* [Docs](https://orm.drizzle.team/docs)
-* [GitHub](https://github.com/drizzle-team/drizzle-orm)
-* [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
+- [Docs](https://orm.drizzle.team/docs)
+- [GitHub](https://github.com/drizzle-team/drizzle-orm)
+- [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
 
 ### workers-qb
 
 `workers-qb` is a zero-dependency query builder that provides a simple standardized interface while keeping the benefits and speed of using raw queries over a traditional ORM. While not intended to provide ORM-like functionality, `workers-qb` makes it easier to interact with your database from code for direct SQL access.
 
-* [GitHub](https://github.com/G4brym/workers-qb)
-* [Documentation](https://workers-qb.massadas.com/)
+- [GitHub](https://github.com/G4brym/workers-qb)
+- [Documentation](https://workers-qb.massadas.com/)
 
 ### d1-console
 
 Instead of running the `wrangler d1 execute` command in your terminal every time you want to interact with your database, you can interact with D1 from within the `d1-console`. Created by a Discord Community Champion, this gives the benefit of executing multi-line queries, obtaining command history, and viewing a cleanly formatted table output.
 
-* [GitHub](https://github.com/isaac-mcfadyen/d1-console)
+- [GitHub](https://github.com/isaac-mcfadyen/d1-console)
 
 ### L1
 
 `L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
 
-* [GitHub](https://github.com/renoki-co/l1)
-* [Packagist](https://packagist.org/packages/renoki-co/l1)
+- [GitHub](https://github.com/renoki-co/l1)
+- [Packagist](https://packagist.org/packages/renoki-co/l1)
 
 ### Staff Directory - a D1-based demo
 
 Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/honox), and [Cloudflare Pages](/pages/). It uses D1 to store employee data, and is an example of a full-stack application built on top of D1.
 
-* [GitHub](https://github.com/lauragift21/staff-directory)
-* [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
+- [GitHub](https://github.com/lauragift21/staff-directory)
+- [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
 
 ### NuxtHub
 
@@ -95,9 +93,9 @@ Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/ho
 
 `NuxtHub` also provides a way to use your remote D1 database in development using the `npx nuxt dev --remote` command.
 
-* [GitHub](https://github.com/nuxt-hub/core)
-* [Documentation](https://hub.nuxt.com)
-* [Example](https://github.com/Atinux/nuxt-todos-edge)
+- [GitHub](https://github.com/nuxt-hub/core)
+- [Documentation](https://hub.nuxt.com)
+- [Example](https://github.com/Atinux/nuxt-todos-edge)
 
 ## Feedback
 
diff --git a/src/content/docs/d1/reference/data-security.mdx b/src/content/docs/d1/reference/data-security.mdx
index 810de22ec7f45ea..ab79357a7114750 100644
--- a/src/content/docs/d1/reference/data-security.mdx
+++ b/src/content/docs/d1/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of D1, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/d1/reference/faq.mdx b/src/content/docs/d1/reference/faq.mdx
index 112c665dd4004ad..e86017db8b829fa 100644
--- a/src/content/docs/d1/reference/faq.mdx
+++ b/src/content/docs/d1/reference/faq.mdx
@@ -12,8 +12,8 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="faq-pricing" product="d1"/>
+<Render file="faq-pricing" product="d1" />
 
 ## Limits
 
-<Render file="faq-limits" product="d1"/>
\ No newline at end of file
+<Render file="faq-limits" product="d1" />
diff --git a/src/content/docs/d1/reference/generated-columns.mdx b/src/content/docs/d1/reference/generated-columns.mdx
index 5d116b3321076a7..ccadcdb1b12d227 100644
--- a/src/content/docs/d1/reference/generated-columns.mdx
+++ b/src/content/docs/d1/reference/generated-columns.mdx
@@ -18,8 +18,8 @@ Generated columns can also have [indexes defined](/d1/best-practices/use-indexes
 
 There are two types of generated columns:
 
-* `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
-* `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
+- `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
+- `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
 
 When omitted from a generated column expression, generated columns default to the `VIRTUAL` type. The `STORED` type is recommended when the generated column is compute intensive. For example, when parsing large JSON structures.
 
@@ -40,13 +40,13 @@ As a concrete example, to automatically extract the `location` value from the fo
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
 
@@ -100,6 +100,6 @@ ADD COLUMN expires_at AS (date(timestamp, '+30 days'));
 
 ## Additional considerations
 
-* Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
-* Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
-* Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
+- Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
+- Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
+- Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
diff --git a/src/content/docs/d1/reference/glossary.mdx b/src/content/docs/d1/reference/glossary.mdx
index 5fe0afff9a376e2..87e1a98504fae41 100644
--- a/src/content/docs/d1/reference/glossary.mdx
+++ b/src/content/docs/d1/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - d1
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's D1 documentation.
 
diff --git a/src/content/docs/d1/reference/migrations.mdx b/src/content/docs/d1/reference/migrations.mdx
index 50d3292c20ea584..20dc9869915cbc2 100644
--- a/src/content/docs/d1/reference/migrations.mdx
+++ b/src/content/docs/d1/reference/migrations.mdx
@@ -16,9 +16,9 @@ Database migrations are a way of versioning your database. Each migration is sto
 
 Currently, the migrations system aims to be simple yet effective. With the current implementation, you can:
 
-* [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
-* [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
-* [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
+- [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
+- [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
+- [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
 
 Every migration file in the `migrations` folder has a specified version number in the filename. Files are listed in sequential order. Every migration file is an SQL file where you can specify queries to be run.
 
diff --git a/src/content/docs/d1/sql-api/foreign-keys.mdx b/src/content/docs/d1/sql-api/foreign-keys.mdx
index 1c38b8d8d995ec3..fdc9e715186ae46 100644
--- a/src/content/docs/d1/sql-api/foreign-keys.mdx
+++ b/src/content/docs/d1/sql-api/foreign-keys.mdx
@@ -47,13 +47,13 @@ A foreign key relationship can be defined when creating a table via `CREATE TABL
 
 To illustrate this with an example based on an e-commerce website with two tables:
 
-* A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
-* An `orders` table that maps an order back to a `user_id` in the user table.
+- A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
+- An `orders` table that maps an order back to a `user_id` in the user table.
 
 This mapping is defined as `FOREIGN KEY`, which ensures that:
 
-* You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
-* `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
+- You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
+- `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
 
 ```sql
 CREATE TABLE users (
@@ -77,22 +77,22 @@ You can define multiple foreign key relationships per-table, and foreign key def
 
 ## Foreign key actions
 
-You can define *actions* as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining *actions* makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
+You can define _actions_ as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining _actions_ makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
 
 There are five actions you can set when defining the `ON UPDATE` and/or `ON DELETE` clauses as part of a foreign key relationship. You can also define different actions for `ON UPDATE` and `ON DELETE` depending on your requirements.
 
-* `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
-* `RESTRICT` - A parent key cannot be updated or deleted when *any* child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
-* `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
-* `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
-* `NO ACTION` - Take no action.
+- `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
+- `RESTRICT` - A parent key cannot be updated or deleted when _any_ child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
+- `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
+- `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
+- `NO ACTION` - Take no action.
 
 :::caution[CASCADE usage]
 
 Although `CASCADE` can be the desired behavior in some cases, deleting child rows across tables can have undesirable effects and/or result in unintended side effects for your users.
 :::
 
-In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that *other* users can no longer look up or refer to scores that were still valid.
+In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that _other_ users can no longer look up or refer to scores that were still valid.
 
 ```sql
 CREATE TABLE users (
@@ -111,6 +111,6 @@ CREATE TABLE scores (
 
 ## Next Steps
 
-* Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
-* Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
-* Understand how [database migrations work](/d1/reference/migrations/) with D1.
+- Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
+- Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
+- Understand how [database migrations work](/d1/reference/migrations/) with D1.
diff --git a/src/content/docs/d1/sql-api/query-json.mdx b/src/content/docs/d1/sql-api/query-json.mdx
index 9b44068ab62c958..82c65b749bd3e7f 100644
--- a/src/content/docs/d1/sql-api/query-json.mdx
+++ b/src/content/docs/d1/sql-api/query-json.mdx
@@ -12,10 +12,10 @@ products:
 
 D1 has built-in support for querying and parsing JSON data stored within a database. This enables you to:
 
-* [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
-* Insert and/or replace values within an object or array.
-* [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
-* Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
+- [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
+- Insert and/or replace values within an object or array.
+- [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
+- Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
 
 One of the biggest benefits to parsing JSON within D1 directly is that it can directly reduce the number of round-trips (queries) to your database. It reduces the cases where you have to read a JSON object into your application (1), parse it, and then write it back (2).
 
@@ -25,18 +25,18 @@ This allows you to more precisely query over data and reduce the result set your
 
 JSON data is stored as a `TEXT` column in D1. JSON types follow the same [type conversion rules](/d1/worker-api/#type-conversion) as D1 in general, including:
 
-* A JSON null is treated as a D1 `NULL`.
-* A JSON number is treated as an `INTEGER` or `REAL`.
-* Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
-* Object and array values as `TEXT`.
+- A JSON null is treated as a D1 `NULL`.
+- A JSON number is treated as an `INTEGER` or `REAL`.
+- Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
+- Object and array values as `TEXT`.
 
 ## Supported functions
 
 The following table outlines the JSON functions built into D1 and example usage.
 
-* The `json` argument placeholder can be a JSON object, array, string, number or a null value.
-* The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
-* The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
+- The `json` argument placeholder can be a JSON object, array, string, number or a null value.
+- The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
+- The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
 
 | Function                                                    | Description                                                                                                                                                    | Example                                                                                   |
 | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
@@ -53,7 +53,7 @@ The following table outlines the JSON functions built into D1 and example usage.
 | `json_replace(json, path, value)`                           | Insert a value at the given path. Overwrites an existing value, but does not create a new key if it doesn't exist.                                             |                                                                                           |
 | `json_set(json, path, value)`                               | Insert a value at the given path. Overwrites an existing value.                                                                                                |                                                                                           |
 | `json_type(json)` - `json_type(json, path)`                 | Return the type of the provided value or value at the specified path. Returns one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`. | `json_type('{"temperatures":[73.6, 77.8, 80.2]}', '$.temperatures')` returns `array`      |
-| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                  |
+| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                   |
 | `json_quote(value)`                                         | Converts the provided SQL value into its JSON representation.                                                                                                  | `json_quote('[1, 2, 3]')` returns `[1,2,3]`                                               |
 | `json_group_array(value)`                                   | Returns the provided value(s) as a JSON array.                                                                                                                 |                                                                                           |
 | `json_each(value)` - `json_each(value, path)`               | Returns each element within the object as an individual row. It will only traverse the top-level object.                                                       |                                                                                           |
@@ -102,9 +102,9 @@ Refer to [Generated columns](/d1/reference/generated-columns/) to learn more abo
 
 There are three ways to extract a value from a JSON object in D1:
 
-* The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
-* The `->` operator, which returns a JSON representation of the value.
-* The `->>` operator, which returns an SQL representation of the value.
+- The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
+- The `->` operator, which returns a JSON representation of the value.
+- The `->>` operator, which returns an SQL representation of the value.
 
 The `->` and `->>` operators functions both operate similarly to the same operators in PostgreSQL and MySQL/MariaDB.
 
@@ -112,13 +112,13 @@ Given the following JSON object in a column named `sensor_reading`, you can extr
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
 
@@ -148,8 +148,12 @@ For example, given the following JSON object stored in a column called `login_hi
 
 ```json
 {
-    "user_id": "abc12345",
-    "previous_logins": ["2023-03-31T21:07:14-05:00", "2023-03-28T08:21:02-05:00", "2023-03-28T05:52:11-05:00"]
+	"user_id": "abc12345",
+	"previous_logins": [
+		"2023-03-31T21:07:14-05:00",
+		"2023-03-28T08:21:02-05:00",
+		"2023-03-28T05:52:11-05:00"
+	]
 }
 ```
 
@@ -164,7 +168,13 @@ You can also use `json_array_length` as a predicate in a more complex query - fo
 You can insert a value into an existing JSON object or array using `json_insert()`. For example, if you have a `TEXT` column called `login_history` in a `users` table containing the following object:
 
 ```json
-{"history": ["2023-05-13T15:13:02+00:00", "2023-05-14T07:11:22+00:00", "2023-05-15T15:03:51+00:00"]}
+{
+	"history": [
+		"2023-05-13T15:13:02+00:00",
+		"2023-05-14T07:11:22+00:00",
+		"2023-05-15T15:03:51+00:00"
+	]
+}
 ```
 
 To add a new timestamp to the `history` array within our `login_history` column, write a query resembling the following:
@@ -197,11 +207,11 @@ This would extract only the `value` column from the table returned by `json_each
 
 `json_each` effectively returns a table with multiple columns, with the most relevant being:
 
-* `key` - the key (or index).
-* `value` - the literal value of each element parsed by `json_each`.
-* `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
-* `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
-* `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
+- `key` - the key (or index).
+- `value` - the literal value of each element parsed by `json_each`.
+- `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
+- `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
+- `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
 
 In this example, `SELECT * FROM json_each('[183183, 13913, 94944]')` would return a table resembling the below:
 
@@ -215,12 +225,12 @@ key|value|type|id|fullkey|path
 You can use `json_each` with [D1 Workers Binding API](/d1/worker-api/) in a Worker by creating a statement and using `JSON.stringify` to pass an array as a [bound parameter](/d1/worker-api/d1-database/#guidance):
 
 ```ts
-const stmt = context.env.DB
-    .prepare("UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))")
-const resp = await stmt.bind(
-    "2023-05-16T11:24:08+00:00",
-    JSON.stringify([183183, 13913, 94944])
-    ).run()
+const stmt = context.env.DB.prepare(
+	"UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))",
+);
+const resp = await stmt
+	.bind("2023-05-16T11:24:08+00:00", JSON.stringify([183183, 13913, 94944]))
+	.run();
 ```
 
 This would only update rows in your `users` table where the `id` matches one of the three provided.
diff --git a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
index 986d25d5413005e..2a203c8cb9975a9 100644
--- a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
+++ b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
@@ -12,7 +12,13 @@ description: >-
   This tutorial shows how to create an API that allows you to securely run queries against a D1 database. The API can be used to customize access controls and/or limit what tables can be queried.
 ---
 
-import { Render, PackageManagers, Steps, Details, WranglerConfig } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	Details,
+	WranglerConfig,
+} from "~/components";
 
 In this tutorial, you will learn how to create an API that allows you to securely run queries against a D1 database.
 
diff --git a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
index 3ae7982d8bf2cca..64bb7a1593def46 100644
--- a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
+++ b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
@@ -230,7 +230,7 @@ npx prisma migrate diff --from-empty --to-schema-datamodel ./prisma/schema.prism
 
 </TabItem>
 </Tabs>
- 
+
 This stores a SQL statement to create a new `User` table in your migration file from before, here is what it looks like:
 
 <GitHubCode
diff --git a/src/content/docs/data-localization/compatibility.mdx b/src/content/docs/data-localization/compatibility.mdx
index 472524c6f61c822..724dbfd2c9587c6 100644
--- a/src/content/docs/data-localization/compatibility.mdx
+++ b/src/content/docs/data-localization/compatibility.mdx
@@ -29,19 +29,19 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                                    | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------ | --------------- | ----------------- | -------------------------- |
 | Caching/CDN                                | ✅              | ✅                | ✅                         |
-| Cache Reserve                              | ⚫️             | 🚧                | ✅ [^29]                   |
-| DNS                                        | ⚫️             | 🚧 [^33]          | ✅                         |
-| HTTP/3 (with QUIC)                         | ⚫️             | ✘                 | ⚫️                        |
+| Cache Reserve                              | ⚫️              | 🚧                | ✅ [^29]                   |
+| DNS                                        | ⚫️              | 🚧 [^33]          | ✅                         |
+| HTTP/3 (with QUIC)                         | ⚫️              | ✘                 | ⚫️                         |
 | Image Resizing                             | ✅              | ✅ [^6]           | 🚧 [^1]                    |
 | Load Balancing                             | ✅              | ✅                | 🚧 [^1]                    |
-| Network Error Logging (NEL)                | ⚫️             | ⚫️               | ✘                          |
+| Network Error Logging (NEL)                | ⚫️              | ⚫️                | ✘                          |
 | Onion Routing                              | ✘               | ✘                 | ✘                          |
 | O2O                                        | ✘               | ✘                 | ✘                          |
 | Stream Delivery                            | ✅              | ✅                | ✅                         |
 | Tiered Caching                             | ✅              | 🚧 [^2]           | 🚧 [^30]                   |
 | Trace                                      | ✘               | ✘                 | ✘                          |
-| Waiting Room                               | ⚫️             | ✅                | ✅                         |
-| Web Analytics / Real User Monitoring (RUM) | ⚫️             | ⚫️               | ✘ [^43]                    |
+| Waiting Room                               | ⚫️              | ✅                | ✅                         |
+| Web Analytics / Real User Monitoring (RUM) | ⚫️              | ⚫️                | ✘ [^43]                    |
 | Zaraz                                      | ✅              | ✅                | ✅                         |
 
 ---
@@ -50,18 +50,18 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------- | --------------- | ----------------- | -------------------------- |
-| Advanced Certificate Manager                | ⚫️             | ⚫️               | ⚫️                        |
+| Advanced Certificate Manager                | ⚫️              | ⚫️                | ⚫️                         |
 | Advanced DDoS Protection                    | ✅              | ✅                | 🚧 [^3]                    |
 | API Shield                                  | ✅              | ✅                | 🚧 [^4]                    |
 | Bot Management                              | ✅              | ✅                | ✅                         |
 | Client-side security (formerly Page Shield) | ✅              | ✅                | ✅                         |
-| DNS Firewall                                | ⚫️             | ⚫️               | ✅                         |
+| DNS Firewall                                | ⚫️              | ⚫️                | ✅                         |
 | Rate Limiting                               | ✅              | ✅                | ✅ [^37]                   |
 | SSL                                         | ✅              | ✅                | ✅                         |
 | Cloudflare for SaaS                         | ✘               | ✅                | ✅                         |
-| Turnstile                                   | ⚫️             | ✘                 | ✅ [^38]                   |
+| Turnstile                                   | ⚫️              | ✘                 | ✅ [^38]                   |
 | WAF/L7 Firewall                             | ✅              | ✅                | ✅                         |
-| DMARC Management                            | ⚫️             | ⚫️               | ✅                         |
+| DMARC Management                            | ⚫️              | ⚫️                | ✅                         |
 
 ---
 
@@ -69,24 +69,24 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                        | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------ | --------------- | ----------------- | -------------------------- |
-| Cloudflare Images              | ⚫️             | ✅ [^36]          | 🚧 [^35]                   |
+| Cloudflare Images              | ⚫️              | ✅ [^36]          | 🚧 [^35]                   |
 | AI Gateway                     | ✘               | ✘                 | 🚧 [^39]                   |
 | AI Search                      | ✘ [^46]         | ✘ [^47]           | 🚧 [^48]                   |
 | AI Security for Apps           | ✘               | ✘                 | ✘                          |
 | Cloudflare Pages               | ✅ [^11]        | ✅ [^11]          | 🚧 [^1]                    |
-| Cloudflare D1                  | ⚫️             | ⚫️               | 🚧 [^40]                   |
-| Durable Objects                | ⚫️             | ✅ [^7]           | 🚧 [^1]                    |
-| Email Routing                  | ⚫️             | ⚫️               | ✅                         |
+| Cloudflare D1                  | ⚫️              | ⚫️                | 🚧 [^40]                   |
+| Durable Objects                | ⚫️              | ✅ [^7]           | 🚧 [^1]                    |
+| Email Routing                  | ⚫️              | ⚫️                | ✅                         |
 | Remote MCP Server              | ✅ [^44]        | ✅ [^45]          | 🚧 [^1]                    |
 | R2                             | ✅ [^27]        | ✅ [^8]           | ✅ [^28]                   |
-| Smart Placement                | ⚫️             | ✘                 | ✘                          |
-| Stream                         | ⚫️             | ✘                 | 🚧 [^1]                    |
-| Vectorize                      | ⚫️             | ✘                 | ✘                          |
+| Smart Placement                | ⚫️              | ✘                 | ✘                          |
+| Stream                         | ⚫️              | ✘                 | 🚧 [^1]                    |
+| Vectorize                      | ⚫️              | ✘                 | ✘                          |
 | Workers (deployed on a Zone)   | ✅              | ✅                | 🚧 [^41]                   |
-| Workers AI                     | ⚫️             | ✘                 | ✅                         |
-| Workers KV                     | ⚫️             | ✘                 | ✅ [^34]                   |
+| Workers AI                     | ⚫️              | ✘                 | ✅                         |
+| Workers KV                     | ⚫️              | ✘                 | ✅ [^34]                   |
 | Workers.dev                    | ✘               | ✘                 | ✘                          |
-| Workers Analytics Engine (WAE) | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Workers Analytics Engine (WAE) | ⚫️              | ⚫️                | 🚧 [^1]                    |
 
 ---
 
@@ -95,11 +95,11 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------------- | --------------- | ----------------- | -------------------------- |
 | Argo Smart Routing          | ✅              | ✘ [^9]            | ✘ [^10]                    |
-| Static IP/BYOIP             | ⚫️             | ✅ [^26]          | ⚫️                        |
-| Cloudflare Network Firewall | ⚫️             | ⚫️               | ✅                         |
-| Network Flow                | ⚫️             | ⚫️               | 🚧 [^1]                    |
-| Magic Transit               | ⚫️             | ⚫️               | ✅ [^3]                    |
-| Cloudflare WAN              | ⚫️             | ⚫️               | ✅                         |
+| Static IP/BYOIP             | ⚫️              | ✅ [^26]          | ⚫️                         |
+| Cloudflare Network Firewall | ⚫️              | ⚫️                | ✅                         |
+| Network Flow                | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Magic Transit               | ⚫️              | ⚫️                | ✅ [^3]                    |
+| Cloudflare WAN              | ⚫️              | ⚫️                | ✅                         |
 | Spectrum                    | ✅              | ✅ [^42]          | ✅                         |
 
 ---
@@ -108,9 +108,9 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product      | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------ | --------------- | ----------------- | -------------------------- |
-| Logpull      | ⚫️             | ⚫️               | 🚧 [^12]                   |
-| Logpush      | ⚫️             | ✅                | 🚧 [^13]                   |
-| Log Explorer | ⚫️             | ⚫️               | ✘ [^23]                    |
+| Logpull      | ⚫️              | ⚫️                | 🚧 [^12]                   |
+| Logpush      | ⚫️              | ✅                | 🚧 [^13]                   |
+| Log Explorer | ⚫️              | ⚫️                | ✘ [^23]                    |
 
 ---
 
@@ -119,13 +119,13 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product               | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------- | --------------- | ----------------- | -------------------------- |
 | Access                | 🚧 [^14]        | 🚧 [^15]          | ✅ [^16]                   |
-| Browser Isolation     | ⚫️             | 🚧 [^17]          | ✅                         |
-| CASB                  | ⚫️             | ⚫️               | ✘                          |
-| Cloudflare Tunnel     | ⚫️             | 🚧 [^18]          | ⚫️                        |
-| Digital Experience    | ⚫️             | ⚫️               | 🚧 [^49]                   |
-| DLP                   | ⚫️ [^19]       | ⚫️ [^19]         | 🚧 [^31]                   |
+| Browser Isolation     | ⚫️              | 🚧 [^17]          | ✅                         |
+| CASB                  | ⚫️              | ⚫️                | ✘                          |
+| Cloudflare Tunnel     | ⚫️              | 🚧 [^18]          | ⚫️                         |
+| Digital Experience    | ⚫️              | ⚫️                | 🚧 [^49]                   |
+| DLP                   | ⚫️ [^19]        | ⚫️ [^19]          | 🚧 [^31]                   |
 | Gateway               | 🚧 [^20]        | 🚧 [^21]          | 🚧 [^22]                   |
-| Cloudflare One Client | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Cloudflare One Client | ⚫️              | ⚫️                | 🚧 [^1]                    |
 
 [^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
 
diff --git a/src/content/docs/data-localization/geo-key-manager.mdx b/src/content/docs/data-localization/geo-key-manager.mdx
index 6bafbbf4ad50e68..510eb40b49191a5 100644
--- a/src/content/docs/data-localization/geo-key-manager.mdx
+++ b/src/content/docs/data-localization/geo-key-manager.mdx
@@ -9,7 +9,6 @@ tags:
   - Compliance
 sidebar:
   order: 4
-
 ---
 
 Geo Key Manager offers enhanced control over the storage location of your private SSL/TLS keys — the cryptographic keys that Cloudflare uses to decrypt your HTTPS traffic. By restricting where these keys are stored, you can ensure compliance with regional data regulations and security requirements.
@@ -24,7 +23,7 @@ Geo Key Manager was restricted to the US, EU, and high-security data centers, bu
 
 The following diagram shows what happens when an end user connects to a Cloudflare data center that does not hold your private key. Because TLS termination requires the private key, the local data center must request a temporary session key (a short-lived symmetric encryption key) from a data center in an authorized region. Once the session key is established, the local data center can decrypt traffic for the remainder of the connection without contacting the key-holding data center again. This extra step adds latency on the first request, which can be as much as a second if the key-holding data center is geographically distant.
 
-<br/>
+<br />
 
 ```mermaid
 sequenceDiagram
@@ -41,6 +40,6 @@ sequenceDiagram
     User-->>CloudflarePoP: Subsequent requests use the Session Key
 ```
 
-<br/>
+<br />
 
 For detailed information on setup and supported options, refer to [Geo Key Manager documentation](/ssl/edge-certificates/geokey-manager/).
diff --git a/src/content/docs/ddos-protection/about/components.mdx b/src/content/docs/ddos-protection/about/components.mdx
index fdad5713c8a928e..9161b6dd7d87b5a 100644
--- a/src/content/docs/ddos-protection/about/components.mdx
+++ b/src/content/docs/ddos-protection/about/components.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 ![Diagram with the main components providing protection against DDoS attacks at Cloudflare](~/assets/images/ddos-protection/ddos-diagram.png)
 
diff --git a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
index 2be132500131a7d..921203e498c7fda 100644
--- a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
+++ b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
@@ -9,10 +9,9 @@ sidebar:
 learning_center:
   title: What is a DDoS attack?
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To detect and mitigate <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attacks</GlossaryTooltip>, Cloudflare's autonomous edge and centralized DDoS systems analyze traffic samples out of path, which allows Cloudflare to asynchronously detect DDoS attacks without causing latency or impacting performance.
 
@@ -31,13 +30,13 @@ You can set an override expression for the [HTTP DDoS Attack Protection](/ddos-p
 
 Once attack traffic matches a rule, Cloudflare's systems will track that traffic and generate a real-time signature to surgically match against the attack pattern and mitigate the attack without impacting legitimate traffic. The rules are able to generate different signatures based on various properties of the attacks and the signal strength of each attribute. For example, if the attack is distributed — that is, originating from many source IPs — then the source IP field will not serve as a strong indicator, and the rule will not choose the source IP field as part of the attack signature. Once generated, the fingerprint is propagated as a mitigation rule to the most optimal location on the Cloudflare global network for cost-efficient mitigation. These mitigation rules are ephemeral and will expire shortly after the attack has ended, which happens when no additional traffic has been matched to the rule.
 
-| Actions | Description |
-| --- | --- |
-| Block | Matching requests are denied access to the site. |
-| Managed Challenge | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
-| Interactive Challenge | The client that made the request must pass an interactive Challenge. |
-| Log | Records matching requests in the Cloudflare Logs. |
-| Use rule defaults | Uses the default action that is pre-defined for each rule. |
+| Actions               | Description                                                                                             |
+| --------------------- | ------------------------------------------------------------------------------------------------------- |
+| Block                 | Matching requests are denied access to the site.                                                        |
+| Managed Challenge     | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
+| Interactive Challenge | The client that made the request must pass an interactive Challenge.                                    |
+| Log                   | Records matching requests in the Cloudflare Logs.                                                       |
+| Use rule defaults     | Uses the default action that is pre-defined for each rule.                                              |
 
 ## Thresholds
 
diff --git a/src/content/docs/ddos-protection/about/index.mdx b/src/content/docs/ddos-protection/about/index.mdx
index 65805b05908aecd..c294dbc5482978b 100644
--- a/src/content/docs/ddos-protection/about/index.mdx
+++ b/src/content/docs/ddos-protection/about/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: About Cloudflare DDoS protection
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare provides unmetered and unlimited <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">distributed denial-of-service (DDoS)</GlossaryTooltip> protection at layers 3, 4, and 7 to all customers on all plans and services.
 
@@ -20,4 +19,4 @@ The protection is enabled by Cloudflare's [Autonomous DDoS Protection Edge](/ddo
 
 The Autonomous Edge includes multiple dynamic mitigation rules exposed as [managed rulesets](/ddos-protection/managed-rulesets/), which provide comprehensive protection against a variety of DDoS attacks across layers 3/4 and layer 7 of the OSI model.
 
-[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
\ No newline at end of file
+[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
index 80a1257af1beb09..011867f5ba98440 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
@@ -10,7 +10,6 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced DNS Protection via API
-
 ---
 
 Use the [Cloudflare API](/api/) to configure Advanced DNS Protection via API.
@@ -29,11 +28,11 @@ The `{account_id}` argument is the [account ID](/fundamentals/account/find-accou
 
 The following table summarizes the available operations.
 
-| Operation | Verb + Endpoint |
-| --- | --- |
-| List DNS protection rules | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account. |
-| Add a DNS protection rule | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account. |
-| Get a DNS protection rule | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
-| Update a DNS protection rule | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account. |
-| Delete a DNS protection rule | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account. |
-| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account. |
\ No newline at end of file
+| Operation                       | Verb + Endpoint                                                                                                                                                               |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List DNS protection rules       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account.                                 |
+| Add a DNS protection rule       | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account.                                      |
+| Get a DNS protection rule       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
+| Update a DNS protection rule    | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account.              |
+| Delete a DNS protection rule    | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account.           |
+| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account.                   |
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
index 1c556c9c56533bc..803a3e818448f83 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
-
 ---
 
 # JSON object
@@ -20,15 +19,15 @@ This page contains an example of the DNS protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "mode": "monitoring",
-  "profile_sensitivity": "medium",
-  "rate_sensitivity": "medium",
-  "burst_sensitivity": "medium",
-  "created_on": "2023-10-01T13:10:38.762503+01:00",
-  "modified_on": "2023-10-01T13:10:38.762503+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"mode": "monitoring",
+	"profile_sensitivity": "medium",
+	"rate_sensitivity": "medium",
+	"burst_sensitivity": "medium",
+	"created_on": "2023-10-01T13:10:38.762503+01:00",
+	"modified_on": "2023-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -40,4 +39,4 @@ The `profile_sensitivity` field value must be one of `low` (default), `medium`,
 
 The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`, `medium`, or `high`.
 
-For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
\ No newline at end of file
+For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
index 703796d727a36f1..52ffefc830a024b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced TCP Protection and Advanced DNS Protection via the API
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to configure Advanced TCP Protection and Advanced DNS Protection via the API.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
index 75c5ed4d2392138..2783ca32b25243f 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
@@ -8,7 +8,6 @@ tags:
   - REST API
 sidebar:
   order: 2
-
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/#endpoints).
@@ -24,18 +23,18 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<PROGRAM_ID>",
-      "name": "rate-limiter",
-      "status": "success",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<PROGRAM_ID>",
+			"name": "rate-limiter",
+			"status": "success",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -52,16 +51,16 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<PROGRAM_ID>",
-    "name": "program",
-    "status": "success",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<PROGRAM_ID>",
+		"name": "program",
+		"status": "success",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -69,15 +68,15 @@ If the program fails compilation or verification, the API returns a detailed err
 
 ```json title="Example error response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "code": 1001,
-      "message": "Program verification failed: invalid memory access at line 42"
-    }
-  ],
-  "messages": []
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"code": 1001,
+			"message": "Program verification failed: invalid memory access at line 42"
+		}
+	],
+	"messages": []
 }
 ```
 
@@ -95,16 +94,16 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<PROGRAM_ID>",
-    "name": "program",
-    "status": "success",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<PROGRAM_ID>",
+		"name": "program",
+		"status": "success",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -120,10 +119,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": null,
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -138,21 +137,21 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID>",
-      "program_id": "<PROGRAM_ID>",
-      "scope": "global",
-      "name": "global",
-      "mode": "enabled",
-      "expression": "",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<RULE_ID>",
+			"program_id": "<PROGRAM_ID>",
+			"scope": "global",
+			"name": "global",
+			"mode": "enabled",
+			"expression": "",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -174,19 +173,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "global",
-    "name": "global",
-    "mode": "monitoring",
-    "expression": "",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "global",
+		"name": "global",
+		"mode": "monitoring",
+		"expression": "",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -211,19 +210,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "enabled",
-    "expression": "ip.dst in { 192.0.2.0/24 }",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "enabled",
+		"expression": "ip.dst in { 192.0.2.0/24 }",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -245,19 +244,19 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "global",
-    "name": "global",
-    "mode": "enabled",
-    "expression": "",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "global",
+		"name": "global",
+		"mode": "enabled",
+		"expression": "",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -275,10 +274,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": null,
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -299,7 +298,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 The output PCAP file contains the same packets as the input file, but with annotations on each packet.
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
index e9ea67979faf416..5a3cb4ee6ba3756 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
@@ -12,7 +12,6 @@ sidebar:
 head:
   - tag: title
     content: Configure Programmable Flow Protection via API
-
 ---
 
 Use the [Cloudflare API](/api/) to configure Programmable Flow Protection.
@@ -33,30 +32,30 @@ The tables in the following sections summarize the available operations.
 
 ### Program operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List programs | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
-| Upload a program | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account. |
-| Get a program | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program. |
-| Update a program | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program. |
-| Delete a program | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account. |
-| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account. |
+| Operation           | Method and endpoint / Description                                                                                                                       |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List programs       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
+| Upload a program    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account.                            |
+| Get a program       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program.          |
+| Update a program    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program.                       |
+| Delete a program    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account.     |
+| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account.                |
 
 ### Rule operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List rules | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
-| Create a rule | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account. |
-| Get a rule | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule. |
-| Update a rule | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account. |
-| Delete a rule | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account. |
-| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account. |
+| Operation        | Method and endpoint / Description                                                                                                                 |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List rules       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
+| Create a rule    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account.                            |
+| Get a rule       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule.             |
+| Update a rule    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account.           |
+| Delete a rule    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account.        |
+| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account.                |
 
 ### Debug operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
+| Operation       | Method and endpoint / Description                                                                                                                                                                |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Debug with PCAP | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}/pcap`</p>Runs a program against a PCAP file and returns an annotated PCAP with program verdicts. |
 
 ## Pagination
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
index f0fffca40457798..7857e0cab2af7ad 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Programmable Flow Protection API - JSON objects
-
 ---
 
 This page contains examples of the JSON objects used in the Programmable Flow Protection API.
@@ -20,47 +19,47 @@ This page contains examples of the JSON objects used in the Programmable Flow Pr
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "name": "rate-limiter",
-  "status": "success",
-  "created_on": "2024-01-01T13:06:04.721954+01:00",
-  "modified_on": "2024-01-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"name": "rate-limiter",
+	"status": "success",
+	"created_on": "2024-01-01T13:06:04.721954+01:00",
+	"modified_on": "2024-01-01T13:06:04.721954+01:00"
 }
 ```
 
-| Field | Description |
-| --- | --- |
-| `id` | Unique identifier for the program. |
-| `name` | Name of the program, derived from the uploaded filename. |
-| `status` | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
-| `created_on` | Timestamp when the program was created. |
-| `modified_on` | Timestamp when the program was last modified. |
+| Field         | Description                                                                                                                                             |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | Unique identifier for the program.                                                                                                                      |
+| `name`        | Name of the program, derived from the uploaded filename.                                                                                                |
+| `status`      | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
+| `created_on`  | Timestamp when the program was created.                                                                                                                 |
+| `modified_on` | Timestamp when the program was last modified.                                                                                                           |
 
 ## Rule
 
 ```json
 {
-  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-  "program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "mode": "enabled",
-  "expression": "ip.dst in { 192.0.2.0/24 }",
-  "created_on": "2024-01-01T13:10:38.762503+01:00",
-  "modified_on": "2024-01-01T13:10:38.762503+01:00"
+	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+	"program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"mode": "enabled",
+	"expression": "ip.dst in { 192.0.2.0/24 }",
+	"created_on": "2024-01-01T13:10:38.762503+01:00",
+	"modified_on": "2024-01-01T13:10:38.762503+01:00"
 }
 ```
 
-| Field | Description |
-| --- | --- |
-| `id` | Unique identifier for the rule. |
-| `program_id` | The ID of the program this rule executes. |
-| `scope` | The scope of the rule. Must be one of `global`, `region`, or `datacenter`. |
-| `name` | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code. |
-| `mode` | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`. |
-| `expression` | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
-| `created_on` | Timestamp when the rule was created. |
-| `modified_on` | Timestamp when the rule was last modified. |
+| Field         | Description                                                                                                                       |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | Unique identifier for the rule.                                                                                                   |
+| `program_id`  | The ID of the program this rule executes.                                                                                         |
+| `scope`       | The scope of the rule. Must be one of `global`, `region`, or `datacenter`.                                                        |
+| `name`        | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code.                 |
+| `mode`        | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`.                                                             |
+| `expression`  | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
+| `created_on`  | Timestamp when the rule was created.                                                                                              |
+| `modified_on` | Timestamp when the rule was last modified.                                                                                        |
 
 ### Scope
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
index 8e87b35dd014b57..c8ce427c16455cb 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
@@ -8,7 +8,6 @@ tags:
   - REST API
 sidebar:
   order: 2
-
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/tcp-protection/#endpoints).
@@ -24,12 +23,12 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json title="Example response"
 {
-  "result": {
-    "enabled": false
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"enabled": false
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -58,16 +57,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "prefix": "203.0.113/24",
-      "comment": "My prefix",
-      "excluded": false
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"prefix": "203.0.113/24",
+			"comment": "My prefix",
+			"excluded": false
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -95,27 +94,27 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "id": "<PREFIX_1_ID>",
-      "prefix": "192.0.2.0/24",
-      "excluded": false,
-      "comment": "Game ranges",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    },
-    {
-      "id": "<PREFIX_2_ID>",
-      "prefix": "192.0.2.2/26",
-      "excluded": true,
-      "comment": "Range for a specific game",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<PREFIX_1_ID>",
+			"prefix": "192.0.2.0/24",
+			"excluded": false,
+			"comment": "Game ranges",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		},
+		{
+			"id": "<PREFIX_2_ID>",
+			"prefix": "192.0.2.2/26",
+			"excluded": true,
+			"comment": "Range for a specific game",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -130,19 +129,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "id": "<ALLOWLIST_PREFIX_ID>",
-      "prefix": "192.0.2.127",
-      "comment": "Single IP address in allowlist",
-      "enabled": true,
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<ALLOWLIST_PREFIX_ID>",
+			"prefix": "192.0.2.127",
+			"comment": "Single IP address in allowlist",
+			"enabled": true,
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -163,17 +162,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<ALLOWLIST_PREFIX_1_ID>",
-    "prefix": "203.0.113.0/26",
-    "comment": "Partner range",
-    "enabled": true,
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<ALLOWLIST_PREFIX_1_ID>",
+		"prefix": "203.0.113.0/26",
+		"comment": "Partner range",
+		"enabled": true,
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -196,19 +195,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<SYN_FLOOD_RULE_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "monitoring",
-    "rate_sensitivity": "medium",
-    "burst_sensitivity": "medium",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<SYN_FLOOD_RULE_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "monitoring",
+		"rate_sensitivity": "medium",
+		"burst_sensitivity": "medium",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -233,19 +232,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<OOS_TCP_RULE_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "monitoring",
-    "rate_sensitivity": "low",
-    "burst_sensitivity": "low",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<OOS_TCP_RULE_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "monitoring",
+		"rate_sensitivity": "low",
+		"burst_sensitivity": "low",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -267,16 +266,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<SYN_FLOOD_FILTER_ID>",
-    "expression": "ip.dst in { 192.0.2.0/24 }",
-    "mode": "monitoring",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<SYN_FLOOD_FILTER_ID>",
+		"expression": "ip.dst in { 192.0.2.0/24 }",
+		"mode": "monitoring",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -298,17 +297,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<OOS_TCP_FILTER_ID>",
-    "expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
-    "mode": "disabled",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<OOS_TCP_FILTER_ID>",
+		"expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
+		"mode": "disabled",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
-Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
\ No newline at end of file
+Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
index 54d00d15660f858..5af3cfacb95b70f 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
@@ -12,7 +12,6 @@ head:
     content: Configure Advanced TCP Protection via API
 tags:
   - TCP
-
 ---
 
 You can configure Advanced TCP Protection using the Advanced TCP Protection API.
@@ -37,81 +36,81 @@ The tables in the following sections summarize the available operations.
 
 ### General operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| Get Advanced TCP Protection status | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
+| Operation                             | Method and endpoint / Description                                                                                                                                   |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Get Advanced TCP Protection status    | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
 | Update Advanced TCP Protection status | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Enables or disables Advanced TCP Protection.                        |
 
 ### Prefix operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account. |
+| Operation            | Method and endpoint / Description                                                                                                                             |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List prefixes        | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account.                 |
 | Add prefixes in bulk | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/bulk`</p>Adds prefixes in bulk to the account (up to 300 prefixes per request). |
-| Get a prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix. |
-| Update a prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix. |
-| Delete a prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix. |
-| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account. |
+| Get a prefix         | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix.                       |
+| Update a prefix      | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix.                                    |
+| Delete a prefix      | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix.                                   |
+| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account.                           |
 
 ### Allowlist operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List allowlisted prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
-| Add an allowlisted prefix | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
-| Get an allowlisted prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
-| Update an allowlisted prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist. |
-| Delete an allowlisted prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist. |
-| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist. |
+| Operation                       | Method and endpoint / Description                                                                                                                            |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List allowlisted prefixes       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
+| Add an allowlisted prefix       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
+| Get an allowlisted prefix       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
+| Update an allowlisted prefix    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist.              |
+| Delete an allowlisted prefix    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist.           |
+| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist.                       |
 
 ### SYN Flood Protection operations
 
 #### Rules
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List SYN flood rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account. |
-| Add a SYN flood rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account. |
-| Get a SYN flood rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
-| Update a SYN flood rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account. |
-| Delete a SYN flood rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account. |
-| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account. |
+| Operation                  | Method and endpoint / Description                                                                                                                                        |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List SYN flood rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account.                                 |
+| Add a SYN flood rule       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account.                                      |
+| Get a SYN flood rule       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
+| Update a SYN flood rule    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account.              |
+| Delete a SYN flood rule    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account.           |
+| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account.                   |
 
 #### Filters
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List SYN flood filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account. |
-| Add a SYN flood filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account. |
-| Get a SYN flood filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
-| Update a SYN flood filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account. |
-| Delete a SYN flood filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account. |
-| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account. |
+| Operation                    | Method and endpoint / Description                                                                                                                                              |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List SYN flood filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account.                                   |
+| Add a SYN flood filter       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account.                                        |
+| Get a SYN flood filter       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
+| Update a SYN flood filter    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account.              |
+| Delete a SYN flood filter    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account.           |
+| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account.                     |
 
 ### Out-of-state TCP Protection operations
 
 #### Rules
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List out-of-state TCP rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account. |
-| Add an out-of-state TCP rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account. |
-| Get an out-of-state TCP rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
-| Update an out-of-state TCP rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account. |
-| Delete an out-of-state TCP rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account. |
-| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account. |
+| Operation                         | Method and endpoint / Description                                                                                                                                                    |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List out-of-state TCP rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account.                                 |
+| Add an out-of-state TCP rule      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account.                                     |
+| Get an out-of-state TCP rule      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
+| Update an out-of-state TCP rule   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account.              |
+| Delete an out-of-state TCP rule   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account.           |
+| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account.                   |
 
 #### Filters
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List out-of-state TCP filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account. |
-| Add an out-of-state TCP filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account. |
-| Get an out-of-state TCP filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
-| Update an out-of-state TCP filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account. |
-| Delete an out-of-state TCP filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account. |
-| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account. |
+| Operation                           | Method and endpoint / Description                                                                                                                                                          |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List out-of-state TCP filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account.                                   |
+| Add an out-of-state TCP filter      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account.                                       |
+| Get an out-of-state TCP filter      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
+| Update an out-of-state TCP filter   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account.              |
+| Delete an out-of-state TCP filter   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account.           |
+| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account.                     |
 
 ## Pagination
 
-The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
\ No newline at end of file
+The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
index b2186e3c55edc9b..1368cbecbe0cfe8 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
-
 ---
 
 This page contains an example of the TCP protection rule JSON object used in the API.
@@ -20,12 +19,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "prefix": "192.0.2.0/24",
-  "comment": "Game ranges",
-  "excluded": false,
-  "created_on": "2022-01-01T13:06:04.721954+01:00",
-  "modified_on": "2022-01-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"prefix": "192.0.2.0/24",
+	"comment": "Game ranges",
+	"excluded": false,
+	"created_on": "2022-01-01T13:06:04.721954+01:00",
+	"modified_on": "2022-01-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -33,12 +32,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "prefix": "192.0.2.0/24",
-  "comment": "Game ranges",
-  "enabled": true,
-  "created_on": "2021-10-01T13:06:04.721954+01:00",
-  "modified_on": "2021-10-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"prefix": "192.0.2.0/24",
+	"comment": "Game ranges",
+	"enabled": true,
+	"created_on": "2021-10-01T13:06:04.721954+01:00",
+	"modified_on": "2021-10-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -48,13 +47,13 @@ The `prefix` field can contain an IP address or a CIDR range.
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "rate_sensitivity": "medium",
-  "burst_sensitivity": "medium",
-  "created_on": "2021-10-01T13:10:38.762503+01:00",
-  "modified_on": "2021-10-01T13:10:38.762503+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"rate_sensitivity": "medium",
+	"burst_sensitivity": "medium",
+	"created_on": "2021-10-01T13:10:38.762503+01:00",
+	"modified_on": "2021-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -66,11 +65,11 @@ The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`
 
 ```json
 {
-  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-  "expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
-  "mode": "enabled",
-  "created_on": "2022-11-01T13:10:38.762503+01:00",
-  "modified_on": "2022-11-01T13:10:38.762503+01:00"
+	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+	"expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
+	"mode": "enabled",
+	"created_on": "2022-11-01T13:10:38.762503+01:00",
+	"modified_on": "2022-11-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -86,4 +85,4 @@ The `expression` field is a [Rules language expression](/ruleset-engine/rules-la
 Expressions of SYN flood protection and out-of-state TCP protection filters do not currently support functions.
 :::
 
-The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
\ No newline at end of file
+The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
index 7906194f1a69e0b..e542bce53c6b4fa 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
@@ -9,9 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Add a prefix to Advanced DDoS Protection
-
 ---
-import { Steps, DashButton } from "~/components"
+
+import { Steps, DashButton } from "~/components";
 
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
@@ -28,4 +28,4 @@ To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to
 :::note[Note]
 
 The **Add existing prefix** list will not display leased prefixes, but you can add them manually in the Cloudflare dashboard or [using the API](/ddos-protection/advanced-ddos-systems/api/). You cannot add [delegated prefixes](/byoip/concepts/prefix-delegations/) to Advanced TCP Protection.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
index df2d627092922fe..405eeb35a0dab05 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 5
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
@@ -26,4 +25,4 @@ To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 :::note
 
 Prefixes or subsets added as _Excluded_ will not be protected by Advanced TCP Protection.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
index 19ab785b897da72..87c03f48746ed33 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: How-to guides
 description: How-to guides for configuring Advanced TCP Protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
index 7ee74065ee74642..fe36b285e12bed7 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
@@ -8,11 +8,9 @@ sidebar:
   group:
     hideIndex: true
   order: 6
-
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's Advanced DDoS systems:
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
index 495f1aa4c759f15..bedd9eaac204c3e 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
@@ -39,20 +39,20 @@ Once thresholds are configured, the Advanced DDoS Protection systems have been i
 
 Automatic thresholds for Cloudflare's Advanced DDoS Protection system optimizes the detection and mitigation of DDoS attacks by automatically calculating appropriate traffic thresholds for each system for each customer account. This system applies to Advanced TCP Protection (specifically SYN Flood Protection and Out-of-State TCP Flood Protection) and Advanced DNS Protection.
 
-Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds. 
+Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds.
 
 #### Process
 
-The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below. 
+The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below.
 
 - The `flowtrackd` account was created within the past 7 to 10 days.
 - The account has at least one configured global threshold (rate and burst). This can be a threshold that was automatically provisioned by the system or manually provisioned by Cloudflare.
 
 These checks are performed independently for SYN Flood Protection, Out-of-State TCP Flood Protection, and Advanced DNS Protection. The criteria does not require the presence of any rules to be configured. Accounts initially provisioned by the automatic system will have default thresholds. Otherwise, thresholds may be unconfigured if they are not set by Cloudflare.
 
-After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic. 
+After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic.
 
-Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst. 
+Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst.
 
 Thresholds are derived using the 95th percentile (P95) of observed traffic over the preceding seven days:
 
@@ -60,9 +60,9 @@ Thresholds are derived using the 95th percentile (P95) of observed traffic over
 - Out-of-State TCP Flood Protection: Based on all other TCP flag traffic.
 - Advanced DNS Protection: Based on DNS over UDP traffic.
 
-While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance. 
+While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance.
 
-The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team. 
+The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team.
 
 #### Implementation
 
@@ -70,7 +70,7 @@ You should enable the automatically provisioned rules. Initially, these rules wi
 
 #### Recalculation
 
-Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration. 
+Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration.
 
 #### Overrides
 
@@ -82,7 +82,7 @@ If you are actively under attack and diverting traffic to Cloudflare, the automa
 
 #### Limitations
 
-Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated. 
+Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated.
 
 The auto-threshold calculation component currently runs only in PDX. Therefore, this feature is not compatible if you have enabled Data Localization Services (DLS) and are located outside of the US, such as EU CMB. Future improvements will address this limitation.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
index 5c86d3ba72f115a..8e7eeb417b2d7c0 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
@@ -60,7 +60,7 @@ The Programmable Flow Protection system supports the [Data Localization suite](/
 :::caution[Beta functionality limitations]
 
 For more information on beta services, refer to section 2.6 in the [Enterprise Terms of Service](https://www.cloudflare.com/enterpriseterms/).
-  :::
+:::
 
 ### Write a basic program
 
@@ -210,6 +210,7 @@ The steps below write a sample program that drops all User Datagram Protocol (UD
 </Steps>
 
 For reference, the example below is the basic program in its entirety:
+
 ```c
 #define CF_EBPF_HELPER_V0
 
@@ -269,7 +270,6 @@ cf_ebpf_main(void *state)
 }
 ```
 
-
 ### Write a complex program: challenge-based response
 
 The example program below implements a UDP-based challenge-response mechanism using helper functions to maintain state between packets from the same source IP. This is useful for mitigating DDoS attacks by requiring clients to prove they can receive and respond to challenges before allowing their traffic through.
@@ -644,12 +644,12 @@ For reference, the example below is the rate limiting program in its entirety:
 #define RATE_LIMIT 100         // Maximum packets allowed per window
 #define WINDOW_SECONDS 60      // Time window in seconds
 
-// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the 
+// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the
 // table hold a timestamp and a counter to accomplish a ratelimit.
-// 
-// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted. 
+//
+// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted.
 // Values are also garbage collected from the table every 1hr.
-// 
+//
 // The macros below pack the timestamp (upper 32 bits) and counter (lower 32 bits) into 64-bit data
 // into a value that we can store into the source IP table.
 #define PACK_STATE(ts, count) (((uint64_t)(ts) << 32) | ((uint64_t)(count) & 0xFFFFFFFF))
@@ -727,14 +727,15 @@ If an incoming packet's source IP is blocklisted in the source IP state table, t
 
 The source IP state table stores state keyed by source IP address. Each entry contains:
 
-| Field | Type | Description |
-| --- | --- | --- |
-| Status | Enum | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
-| User data | `u64` | A user-defined value you can set for any purpose. |
+| Field     | Type  | Description                                                                                      |
+| --------- | ----- | ------------------------------------------------------------------------------------------------ |
+| Status    | Enum  | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
+| User data | `u64` | A user-defined value you can set for any purpose.                                                |
 
 The default maximum capacity is 1,000 entries.
 
 Use the following helper functions to interact with this table:
+
 - `get_src_ip_status` — Retrieve the status of the current packet's source IP.
 - `set_src_ip_status` — Set the status of the current packet's source IP.
 - `get_src_ip_data` — Retrieve the user data for the current packet's source IP.
@@ -747,6 +748,7 @@ The flow state table stores state keyed by the 4-tuple: source IP, source port,
 The default maximum capacity is 10,000 entries.
 
 Use the following helper functions to interact with this table:
+
 - `get_flow_data` — Retrieve the user data for the current flow.
 - `set_flow_data` — Store user data for the current flow.
 
@@ -768,32 +770,32 @@ Helper functions may be removed or changed. New helper functions may be introduc
 
 The table below provides a list of currently supported helper functions:
 
-| Function name       | Function signature                                                               | Description                                                                                                                                                                                                                             |
-| ------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `rand`      | `uint64_t rand(void)`                                                                           | Generates a random unsigned integer.                                                                                                                                                                                                    |
-| `timestamp` | `uint64_t timestamp(void)` | Returns the current timestamp. |
-| `hash_md5` | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes MD5 hash of the source buffer and stores result in destination buffer. |
-| `hash_sha256` | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-256 hash of the source buffer and stores result in destination buffer. |
-| `hash_sha512` | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-512 hash of the source buffer and stores result in destination buffer. |
-| `hash_crc32` | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes CRC32 hash of the source buffer and stores result in destination buffer. |
-| `hmac_sha256` | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer. |
-| `hmac_sha512` | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer. |
-| `set_challenge` | `int set_challenge(uint8_t *src, size_t src_len)` | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset. |
-| `get_src_ip_status` | `uint64_t get_src_ip_status(void)` | Retrieves the status value associated with the source IP address from the state table. |
-| `set_src_ip_status` | `int set_src_ip_status(uint64_t status)` | Sets the status value associated with the source IP address in the state table. |
-| `get_src_ip_data` | `int get_src_ip_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the source IP address from the state table. |
-| `set_src_ip_data` | `int set_src_ip_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the source IP address in the state table. |
-| `get_flow_data` | `int get_flow_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the current flow from the state table. |
-| `set_flow_data` | `int set_flow_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the current flow in the state table. |
-| `entropy` | `double entropy(uint8_t *src, size_t src_len)` | Calculates the entropy of the source buffer. |
-| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)` | Sets a custom tag for network analytics reporting. Defaults to `0` if not set. |
-| `ntohs` | `uint16_t ntohs(uint16_t netshort)` | Converts a 16-bit integer from network byte order to host byte order. |
-| `htons` | `uint16_t htons(uint16_t hostshort)` | Converts a 16-bit integer from host byte order to network byte order. |
-| `ntohl` | `uint32_t ntohl(uint32_t netlong)` | Converts a 32-bit integer from network byte order to host byte order. |
-| `htonl` | `uint32_t htonl(uint32_t hostlong)` | Converts a 32-bit integer from host byte order to network byte order. |
-| `ntohll` | `uint64_t ntohll(uint64_t netlonglong)` | Converts a 64-bit integer from network byte order to host byte order. |
-| `htonll` | `uint64_t htonll(uint64_t hostlonglong)` | Converts a 64-bit integer from host byte order to network byte order. |
-| `parse_packet_data` | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)` | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
+| Function name               | Function signature                                                                          | Description                                                                                                                                                                                                                             |
+| --------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rand`                      | `uint64_t rand(void)`                                                                       | Generates a random unsigned integer.                                                                                                                                                                                                    |
+| `timestamp`                 | `uint64_t timestamp(void)`                                                                  | Returns the current timestamp.                                                                                                                                                                                                          |
+| `hash_md5`                  | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)`                                  | Computes MD5 hash of the source buffer and stores result in destination buffer.                                                                                                                                                         |
+| `hash_sha256`               | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-256 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
+| `hash_sha512`               | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-512 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
+| `hash_crc32`                | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)`                                | Computes CRC32 hash of the source buffer and stores result in destination buffer.                                                                                                                                                       |
+| `hmac_sha256`               | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
+| `hmac_sha512`               | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
+| `set_challenge`             | `int set_challenge(uint8_t *src, size_t src_len)`                                           | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset.                                                                                                                                                 |
+| `get_src_ip_status`         | `uint64_t get_src_ip_status(void)`                                                          | Retrieves the status value associated with the source IP address from the state table.                                                                                                                                                  |
+| `set_src_ip_status`         | `int set_src_ip_status(uint64_t status)`                                                    | Sets the status value associated with the source IP address in the state table.                                                                                                                                                         |
+| `get_src_ip_data`           | `int get_src_ip_data(uint8_t *dst, size_t dst_len)`                                         | Retrieves custom data associated with the source IP address from the state table.                                                                                                                                                       |
+| `set_src_ip_data`           | `int set_src_ip_data(uint8_t *src, size_t src_len)`                                         | Stores custom data associated with the source IP address in the state table.                                                                                                                                                            |
+| `get_flow_data`             | `int get_flow_data(uint8_t *dst, size_t dst_len)`                                           | Retrieves custom data associated with the current flow from the state table.                                                                                                                                                            |
+| `set_flow_data`             | `int set_flow_data(uint8_t *src, size_t src_len)`                                           | Stores custom data associated with the current flow in the state table.                                                                                                                                                                 |
+| `entropy`                   | `double entropy(uint8_t *src, size_t src_len)`                                              | Calculates the entropy of the source buffer.                                                                                                                                                                                            |
+| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)`                                                  | Sets a custom tag for network analytics reporting. Defaults to `0` if not set.                                                                                                                                                          |
+| `ntohs`                     | `uint16_t ntohs(uint16_t netshort)`                                                         | Converts a 16-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htons`                     | `uint16_t htons(uint16_t hostshort)`                                                        | Converts a 16-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `ntohl`                     | `uint32_t ntohl(uint32_t netlong)`                                                          | Converts a 32-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htonl`                     | `uint32_t htonl(uint32_t hostlong)`                                                         | Converts a 32-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `ntohll`                    | `uint64_t ntohll(uint64_t netlonglong)`                                                     | Converts a 64-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htonll`                    | `uint64_t htonll(uint64_t hostlonglong)`                                                    | Converts a 64-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `parse_packet_data`         | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)`   | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
 
 ---
 
@@ -805,7 +807,7 @@ With the exception of `rand`, `timestamp`, `ntohs`, `htons`, `ntohl`, `htonl`, `
 
 To upload a program, navigate to Networking > L3/4 DDoS protection > Advanced Protection in the Cloudflare dashboard. Then select the tab titled Programmable Flow Protection.
 
-Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code. 
+Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code.
 
 The Cloudflare API will receive the source code in the `C` file, compile it into BPF bytecode, and run the verifier against it.
 
@@ -813,12 +815,11 @@ If compilation or verification fails, the API will return a detailed error messa
 
 If compilation and verification succeeds, Cloudflare will store the source code and object file to the account and return the program ID.
 
-
 ### Update a program
 
 During the development process, you may find it useful to update the same program (identified by the same program ID) instead of repeatedly creating new programs as new resources.
 
-To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code. 
+To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code.
 
 :::note
 It is possible to update and overwrite a program that is currently in use by one or more rules. When doing so, you will be warned that the program is currently active and will be overwritten. However, if an active program is being updated with a program that either does not compile or can not be verified, the update will fail and the old program will continue to be in use.
@@ -832,7 +833,7 @@ A link icon next to the program name indicates that the program is currently in
 
 ### Delete a program
 
-To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**. 
+To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**.
 
 Note that you will not be able to delete a program that is referenced in an active Rule.
 
@@ -887,10 +888,11 @@ curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/programmab
 
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
+
 ---
 
 ## Safe program and rule deployment best practices
@@ -1011,7 +1013,7 @@ struct cf_ebpf_parsed_headers {
    uint8_t        *data_end;
 };
 
-/* 
+/*
 * IPv4 header, used as field of cf_ebpf_parsed_headers */
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ip.h#L87
 */
@@ -1034,10 +1036,10 @@ struct iphdr {
     uint32_t daddr;
 };
 
-/* 
+/*
 * IPv6 header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ipv6.h#L118
-*/ 
+*/
 struct ipv6hdr {
 #if defined(__BYTE_ORDER__) && __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
     uint8_t  version:4,
@@ -1054,7 +1056,7 @@ struct ipv6hdr {
     uint8_t  daddr[16];
 };
 
-/* 
+/*
 * UDP header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/udp.h#L23
 */
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
index 36422e1fcf667c9..05220d120fb6f68 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
@@ -19,6 +19,7 @@ Always transition from Monitoring mode to Mitigation (Enabled) mode. Do not swit
 When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Protection begins a learning period to observe existing connection state. Long-lived connections that pre-date this learning period may be dropped because they have no state in the tracker.
 
 **Recommended procedure:**
+
 1. Set to **Monitoring** mode for at least 4 hours (longer if your network has long-lived connections).
 2. Review the Monitoring mode logs in [Network Analytics](/analytics/network-analytics/) to confirm legitimate traffic patterns.
 3. Switch to **Mitigation (Enabled)** mode.
@@ -27,12 +28,12 @@ When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Pro
 
 Check the **Mitigation reason** field in the **Advanced TCP Protection** tab of [Network Analytics](/analytics/network-analytics/) and use the reason to identify the cause:
 
-| Mitigation reason | Likely cause | Action |
-|---|---|---|
-| **Not found** | Learning period was incomplete, or long-lived connections pre-date ATP activation | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled) |
-| **Unexpected** | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
-| **Out of sequence** | Packet reordering or packet loss in the network path | Increase burst sensitivity threshold for the affected colo |
-| Drops during traffic spikes only | Burst sensitivity threshold too low | Increase burst sensitivity (keep rate sensitivity the same) |
+| Mitigation reason                | Likely cause                                                                              | Action                                                                                                  |
+| -------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| **Not found**                    | Learning period was incomplete, or long-lived connections pre-date ATP activation         | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled)                                |
+| **Unexpected**                   | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
+| **Out of sequence**              | Packet reordering or packet loss in the network path                                      | Increase burst sensitivity threshold for the affected colo                                              |
+| Drops during traffic spikes only | Burst sensitivity threshold too low                                                       | Increase burst sensitivity (keep rate sensitivity the same)                                             |
 
 **Threshold tuning:** Adjust burst sensitivity before rate sensitivity. Burst sensitivity handles momentary spikes; rate sensitivity controls sustained packet rates.
 
diff --git a/src/content/docs/ddos-protection/best-practices/index.mdx b/src/content/docs/ddos-protection/best-practices/index.mdx
index c90d2aafc0fd31d..d5e1f5b2afacde1 100644
--- a/src/content/docs/ddos-protection/best-practices/index.mdx
+++ b/src/content/docs/ddos-protection/best-practices/index.mdx
@@ -9,10 +9,9 @@ sidebar:
     hideIndex: true
 head: []
 description: Learn about best practices for configuring Cloudflare's DDoS protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on DDoS protection best practices:
 
diff --git a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
index 4be4546f04f6fa5..07721304f2cfb3c 100644
--- a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
+++ b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
@@ -11,7 +11,7 @@ tags:
   - Caching
 ---
 
-import { GlossaryTooltip, Steps } from "~/components"
+import { GlossaryTooltip, Steps } from "~/components";
 
 Cloudflare's network automatically mitigates large <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">DDoS attacks</GlossaryTooltip>, but these attacks can still affect your application.
 
@@ -35,4 +35,4 @@ In addition to the steps for all customers, Cloudflare Enterprise customers subs
 
 ## Magic Transit customers
 
-In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
\ No newline at end of file
+In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
diff --git a/src/content/docs/ddos-protection/best-practices/third-party.mdx b/src/content/docs/ddos-protection/best-practices/third-party.mdx
index 5e4e9065879bfc6..f7d646f767015f2 100644
--- a/src/content/docs/ddos-protection/best-practices/third-party.mdx
+++ b/src/content/docs/ddos-protection/best-practices/third-party.mdx
@@ -25,7 +25,7 @@ Therefore, it is recommended that you **use the [Cloudflare CDN](/cache/)**, whi
 - You perform DDoS filtering in the first point of contact from the Internet, which is a recommended best practice.
 
 :::caution[L3/4 DDoS mitigation accuracy]
-Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation. 
+Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation.
 
 When traffic is proxied through another vendor, the vendor's IP addresses are available to Cloudflare's network-layer protection systems rather than the true client IP addresses. This lack of visibility into the original source can lead to less effective automated mitigation and potential false positives.
 :::
diff --git a/src/content/docs/ddos-protection/botnet-threat-feed.mdx b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
index ba3a7ca8409be2e..8058f8d886012b1 100644
--- a/src/content/docs/ddos-protection/botnet-threat-feed.mdx
+++ b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
@@ -14,9 +14,9 @@ learning_center:
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-botnet/
 tags:
   - REST API
-
 ---
-import { Steps, APIRequest, DashButton } from "~/components"
+
+import { Steps, APIRequest, DashButton } from "~/components";
 
 The Cloudflare DDoS Botnet Threat Feed is a threat intelligence feed for service providers (SPs) such as hosting providers and Internet service providers (ISPs) that provides information about their own IP addresses that have participated in HTTP DDoS attacks as observed from Cloudflare's global network. The feed aims to help service providers stop the abuse and reduce DDoS attacks originating from within their networks.
 
@@ -85,7 +85,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
 - The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
 - Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
 - When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
-:::
+  :::
 
 To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:
 
@@ -103,23 +103,23 @@ Retrieves all the data in the botnet tracking database for a given ASN (currentl
 The provided `{asn}` must be affiliated with your account.
 
 <APIRequest
-  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
-  method="GET"
+	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
+	method="GET"
 />
 
 ```json output
 {
-  "result": [
-    {
-      "cidr": "127.0.0.1/32",
-      "date": "1970-01-01T00:00:00Z",
-      "offense_count": 10000
-    },
-    // ... other entries ...
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"cidr": "127.0.0.1/32",
+			"date": "1970-01-01T00:00:00Z",
+			"offense_count": 10000
+		}
+		// ... other entries ...
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -135,22 +135,22 @@ The provided `{asn}` must be affiliated with your account.
 `{date}` must be an ISO 8601-formatted date: `YYYY-MM-DD`. If no date is specified, the API responds with the data from the day before.
 
 <APIRequest
-  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
-  method="GET"
+	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
+	method="GET"
 />
 
 ```json output
 {
-  "result": [
-    {
-      "cidr": "127.0.0.1/32",
-      "date": "2024-05-05T00:00:00Z",
-      "offense_count": 10000
-    },
-    // ... other entries ...
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"cidr": "127.0.0.1/32",
+			"date": "2024-05-05T00:00:00Z",
+			"offense_count": 10000
+		}
+		// ... other entries ...
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
index 23e89367c6df2b1..294386d75a7913f 100644
--- a/src/content/docs/ddos-protection/get-started.mdx
+++ b/src/content/docs/ddos-protection/get-started.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 3
-
 ---
 
-import { Steps } from "~/components"
+import { Steps } from "~/components";
 
 ## Free, Pro, and Business plans
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
index d811b5a27be035b..da3c36e2cef5dc2 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
@@ -55,7 +55,7 @@ Cloudflare HTTP DDoS Protection can also initiate mitigation based on the origin
 This rule is available for zones on any plan.
 :::
 
-While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules: 
+While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules:
 
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by configuring the HTTP DDoS Attack Protection managed ruleset.
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
index aa5cf2850cf749b..d30b1f397074ef2 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
@@ -6,7 +6,6 @@ products:
   - ddos-protection
 sidebar:
   order: 5
-
 ---
 
 The DDoS Attack Protection managed rulesets provide comprehensive protection against a [variety of DDoS attacks](/ddos-protection/about/attack-coverage/) across L3/4 (network layer) and L7 (application layer) of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/).
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
index 08ab036ae1868dc..ec4a3407ca3c976 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
@@ -54,7 +54,7 @@ While you can manually override a rule from `Log` to `Block`, consider the follo
 
 - The default action of a rule is decided during the testing period. Cloudflare may set its default action to **DDoS Dynamic**, which may use rate-limiting or a multi-step mitigation combination based on traffic factors. By applying a manual `Block` override, you prevent your configuration from automatically inheriting the more nuanced DDoS Dynamic action once it is released.
 
-If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action. 
+If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action.
 
 ## Availability
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
index 679aaba3f002a27..526d496f44f19d3 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Override examples for Network-layer DDoS Attack Protection
-
 ---
 
-import { Details, GlossaryTooltip, DashButton } from "~/components"
+import { Details, GlossaryTooltip, DashButton } from "~/components";
 
 ## Use cases
 
@@ -36,11 +35,12 @@ To avoid disruptions during initial deployment, you can create a _Log_ only –
 
 1. In the Cloudflare dashboard, go to the **Security rules** page.
 
-    <DashButton url="/?to=/:account/:zone/security/security-rules" />
+   <DashButton url="/?to=/:account/:zone/security/security-rules" />
+
 2. Go to the **DDoS protection** tab.
 3. On **HTTP DDoS attack protection**, select **Create override**.
 4. Set the **Scope** to _Apply to all incoming requests_.
 5. Under **Ruleset configuration**:
-    - Set the **Ruleset action** to _Log_.
-    - Set the **Ruleset sensitivity** to _Essentially Off_. 
-6. Select **Save**. 
\ No newline at end of file
+   - Set the **Ruleset action** to _Log_.
+   - Set the **Ruleset sensitivity** to _Essentially Off_.
+6. Select **Save**.
diff --git a/src/content/docs/ddos-protection/reference/alerts.mdx b/src/content/docs/ddos-protection/reference/alerts.mdx
index 02ded106c58f5b9..2d58a70a27086ca 100644
--- a/src/content/docs/ddos-protection/reference/alerts.mdx
+++ b/src/content/docs/ddos-protection/reference/alerts.mdx
@@ -108,4 +108,4 @@ To investigate a possibly ongoing attack, select **View Dashboard**. To go to th
 - In some cases, HTTP DDoS attack alerts will reference the attacked zone name instead of the attacked hostname. This occurs when the attack signature does not include information on the attacked hostname because it is not a strong indicator for identifying attack requests. For more information on attack signatures, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
 - DDoS alerts are currently only available for DDoS attacks detected and mitigated by the [DDoS managed rulesets](/ddos-protection/managed-rulesets/). Alerts are not yet available for DDoS attacks detected and mitigated by the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), the [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), or the [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) system.
 - You will not receive duplicate DDoS alerts within the same one-hour time frame.
-- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
\ No newline at end of file
+- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
diff --git a/src/content/docs/ddos-protection/reference/index.mdx b/src/content/docs/ddos-protection/reference/index.mdx
index 1ffe418f0eceaf3..3ae60ce4bd017c0 100644
--- a/src/content/docs/ddos-protection/reference/index.mdx
+++ b/src/content/docs/ddos-protection/reference/index.mdx
@@ -9,10 +9,9 @@ sidebar:
     hideIndex: true
 head: []
 description: Reference information for Cloudflare's DDoS protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Cloudflare DDoS protection:
 
diff --git a/src/content/docs/ddos-protection/reference/logs.mdx b/src/content/docs/ddos-protection/reference/logs.mdx
index f0d23899c38c060..1bbc798b5e49584 100644
--- a/src/content/docs/ddos-protection/reference/logs.mdx
+++ b/src/content/docs/ddos-protection/reference/logs.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: DDoS logs
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Retrieve HTTP events using [Cloudflare Logs](/logs/) to integrate them into your <GlossaryTooltip term="SIEM">SIEM systems</GlossaryTooltip>.
 
diff --git a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
index 187dff380ea2545..20dba8ba991db4e 100644
--- a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
+++ b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 After onboarding to Cloudflare, you may want to simulate DDoS attacks against your Internet properties to test the protection, [reporting](/ddos-protection/reference/reports/), and [alerting](/ddos-protection/reference/alerts/) mechanisms. Follow the guidelines in this section to simulate a DDoS attack.
 
diff --git a/src/content/docs/dmarc-management/enable.mdx b/src/content/docs/dmarc-management/enable.mdx
index 1eeb169d8368e0c..c38ef8ef703db1d 100644
--- a/src/content/docs/dmarc-management/enable.mdx
+++ b/src/content/docs/dmarc-management/enable.mdx
@@ -10,7 +10,6 @@ sidebar:
     text: Beta
 tags:
   - DNS
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -30,4 +29,4 @@ To enable DMARC Management:
    - If no DMARC record is found, Cloudflare will automatically invite you to add one that you can edit later. Select **Add** to continue.
    - If a DMARC record is found in your zone, Cloudflare will add another `rua` (Reporting URI for Aggregate data) entry to it. The `rua` tag specifies the URI (typically a `mailto:` address) where aggregate DMARC reports are sent. This additional entry uses a Cloudflare email address so that Cloudflare can receive and process DMARC reports on your behalf. Select **Next** to continue.
 
-DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
\ No newline at end of file
+DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
diff --git a/src/content/docs/dmarc-management/security-records.mdx b/src/content/docs/dmarc-management/security-records.mdx
index 2ec513fecf908f2..df2912e19e4d6cc 100644
--- a/src/content/docs/dmarc-management/security-records.mdx
+++ b/src/content/docs/dmarc-management/security-records.mdx
@@ -29,4 +29,4 @@ To set up email security records:
 
 ## Edit or delete records
 
-Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
\ No newline at end of file
+Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
diff --git a/src/content/docs/dmarc-management/statistics.mdx b/src/content/docs/dmarc-management/statistics.mdx
index 58a5e6ea804a49b..b9186d28b90635d 100644
--- a/src/content/docs/dmarc-management/statistics.mdx
+++ b/src/content/docs/dmarc-management/statistics.mdx
@@ -11,7 +11,6 @@ head:
     content: Review DMARC statistics
 tags:
   - DNS
-
 ---
 
 DMARC Management (beta) allows you to review whether emails sent on your behalf passed or failed DMARC, SPF, and DKIM authentication checks.
diff --git a/src/content/docs/dns/additional-options/index.mdx b/src/content/docs/dns/additional-options/index.mdx
index 66b93896ae59062..2c2a6572e2ac236 100644
--- a/src/content/docs/dns/additional-options/index.mdx
+++ b/src/content/docs/dns/additional-options/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Beyond [setting up your zone](/dns/zone-setups/) and [updating your DNS records](/dns/manage-dns-records/), you may want to customize the following settings in Cloudflare DNS:
 
diff --git a/src/content/docs/dns/changelog.mdx b/src/content/docs/dns/changelog.mdx
index b1163dea5558b84..3c688d1cb2da69d 100644
--- a/src/content/docs/dns/changelog.mdx
+++ b/src/content/docs/dns/changelog.mdx
@@ -12,7 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelogs/dns/. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="dns"/>
+<ProductChangelog product="dns" />
 
 ## 2025-01-27
 
@@ -26,11 +26,11 @@ Records returned by the API will no longer contain the `zone_id` and `zone_name`
 
 When creating [TXT records](/dns/manage-dns-records/reference/dns-record-types/#txt) via the dashboard you will now find:
 
-* Field validation errors if double quotes `"` are added inconsistently.
-* Automatically quoted TXT content upon save if no quotes exist in the record content field.
+- Field validation errors if double quotes `"` are added inconsistently.
+- Automatically quoted TXT content upon save if no quotes exist in the record content field.
 
 ## 2024-10-07
 
 **API support for per-record CNAME flattening**
 
-Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
\ No newline at end of file
+Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx
index 918f0fcc6932086..521021c63c3011d 100644
--- a/src/content/docs/dns/cname-flattening/index.mdx
+++ b/src/content/docs/dns/cname-flattening/index.mdx
@@ -31,4 +31,4 @@ For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), re
 
 - CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
 - CNAME to a different Cloudflare account is prohibited and will result in [Error 1014: CNAME Cross-User Banned](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/)
-- <Render file="cname-flattening-callout" product="dns" />
\ No newline at end of file
+- <Render file="cname-flattening-callout" product="dns" />
diff --git a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
index 675a692b4527d82..22b36e298b9f3bf 100644
--- a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
+++ b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
@@ -11,7 +11,13 @@ head:
     content: Set up CNAME flattening
 ---
 
-import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 :::note
 
diff --git a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
index 3b579df96996538..c961134f600f565 100644
--- a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
+++ b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Protect against random prefix attacks
-
 ---
 
 import { APIRequest } from "~/components";
@@ -23,10 +22,10 @@ In order to enable automatic mitigation of [random prefix attacks](/dns/dns-fire
    	path="/accounts/{account_id}/dns_firewall/{dns_firewall_id}"
    	method="PATCH"
    	json={{
-      "attack_mitigation": {
-        "enabled": true,
-        "only_when_upstream_unhealthy": true,
-      }
+   		attack_mitigation: {
+   			enabled: true,
+   			only_when_upstream_unhealthy: true,
+   		},
    	}}
    />
 
@@ -34,8 +33,6 @@ Once you receive a `200` success response from the API, queries identified as be
 
 :::note
 
-
 If you do not specify otherwise in your API call, Cloudflare automatically sets the `"only_when_upstream_unhealthy"` parameter to true, which means that Cloudflare will only mitigate attacks when we detect that the upstream is unresponsive (possibly as a result of an attack). This setting can also be changed via the API, using a request similar to the ones shown above.
 
-
 :::
diff --git a/src/content/docs/dns/dnssec/dnssec-states.mdx b/src/content/docs/dns/dnssec/dnssec-states.mdx
index 5b40526a38a6545..381c0a152b40f23 100644
--- a/src/content/docs/dns/dnssec/dnssec-states.mdx
+++ b/src/content/docs/dns/dnssec/dnssec-states.mdx
@@ -6,17 +6,16 @@ products:
 title: DNSSEC states
 sidebar:
   order: 4
-
 ---
 
 This page describes different DNSSEC states and how they relate to the responses you get from the [DNSSEC details API endpoint](/api/resources/dns/subresources/dnssec/methods/get/).
 
-| State            | API response                                                     | Description                                                                                                                                                                       |
-| ---------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                         |
-| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                 |
-| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                            |
-| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                        |
+| State            | API response                                                     | Description                                                                                                                                                                                 |
+| ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                                   |
+| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                           |
+| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                                      |
+| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                                  |
 | Deleted          | `"status":"disabled"`<br /> `"modified_on": null`                | DNSSEC has never been enabled for the zone or DNSSEC has been disabled and then deleted using the [Delete DNSSEC records endpoint](/api/resources/dns/subresources/dnssec/methods/delete/). |
 
 :::caution
diff --git a/src/content/docs/dns/dnssec/enable-nsec3.mdx b/src/content/docs/dns/dnssec/enable-nsec3.mdx
index 710497fda89108a..adc9d72f7a3971a 100644
--- a/src/content/docs/dns/dnssec/enable-nsec3.mdx
+++ b/src/content/docs/dns/dnssec/enable-nsec3.mdx
@@ -22,8 +22,8 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met
 	path="/zones/{zone_id}/dnssec"
 	method="PATCH"
 	json={{
-		"dnssec_use_nsec3": true,
-		"status": "active"
+		dnssec_use_nsec3: true,
+		status: "active",
 	}}
 />
 
diff --git a/src/content/docs/dns/dnssec/index.mdx b/src/content/docs/dns/dnssec/index.mdx
index a4f8af210e23313..d58d3d633a1fcfb 100644
--- a/src/content/docs/dns/dnssec/index.mdx
+++ b/src/content/docs/dns/dnssec/index.mdx
@@ -6,14 +6,13 @@ products:
 title: DNSSEC
 sidebar:
   order: 8
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="dnssec-definition" product="dns" />
 
-***
+---
 
 ## Disable DNSSEC
 
@@ -21,7 +20,7 @@ import { Render } from "~/components"
 
 <Render file="dnssec-enabled-migration" product="dns" />
 
-***
+---
 
 ## Enable DNSSEC
 
@@ -37,7 +36,7 @@ When you enable DNSSEC, Cloudflare signs your zone, publishes your public signin
 
 <Render file="dnssec-auto-add" product="dns" />
 
-***
+---
 
 ## Other DNSSEC setup options
 
@@ -45,14 +44,14 @@ If you are using Cloudflare as your Secondary DNS provider and want to configure
 
 If you want to set up DNSSEC on a subdomain zone, refer to [Subdomain DNSSEC](/dns/zone-setups/subdomain-setup/dnssec/).
 
-***
+---
 
 ## Limitations
 
 If your registrar does not support DNSSEC with Cloudflare's preferred cipher choice (Algorithm 13), you have several options:
 
-* Contact your registrar to ask for DNSSEC with modern encryption.
-* Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
-* File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
+- Contact your registrar to ask for DNSSEC with modern encryption.
+- Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
+- File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
 
-If your top-level domain does not support DNSSEC with Algorithm 13 (also known as *ECDSA Curve P-256 with SHA-256*), [contact that top-level domain](https://www.iana.org/domains/root/db).
\ No newline at end of file
+If your top-level domain does not support DNSSEC with Algorithm 13 (also known as _ECDSA Curve P-256 with SHA-256_), [contact that top-level domain](https://www.iana.org/domains/root/db).
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
index dea0d2d6371ecdd..1fd48842270e6c8 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: About multi-signer DNSSEC
-
 ---
 
 Multi-signer DNSSEC consists of two models that allow different authoritative DNS providers to serve the same zone and have DNSSEC enabled at the same time.
@@ -20,7 +19,6 @@ You can [set up multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/) usi
 
 ## How it works
 
-
 :::note
 This is a simplified explanation to give you context and clarify what is involved in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/setup/). For technical details refer to [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html). To read more about DNSSEC, refer to [How DNSSEC works](https://www.cloudflare.com/dns/dnssec/how-dnssec-works/).
 :::
@@ -95,4 +93,4 @@ Multi-signer DNSSEC involves coordinating cryptographic keys across multiple pro
 1. Verify that both providers have each other's ZSKs in their DNSKEY RRsets.
 2. Confirm that both DS records are present at the registrar.
 3. Use DNSSEC validation tools to test resolution from both providers.
-4. Monitor for validation errors during the transition period.
\ No newline at end of file
+4. Monitor for validation errors during the transition period.
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
index 99825944a7ae3ae..b2c476f53cf14a9 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
@@ -173,4 +173,4 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
 
 1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
 
-2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
\ No newline at end of file
+2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
diff --git a/src/content/docs/dns/dnssec/validation-and-key-management.mdx b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
index 83711e5a34916e7..307aec3cbfdc7e4 100644
--- a/src/content/docs/dns/dnssec/validation-and-key-management.mdx
+++ b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
@@ -30,9 +30,9 @@ This is why you cannot simply keep your existing DS record when migrating to Clo
 
 When you enable DNSSEC, Cloudflare automatically publishes **CDS** (Child Delegation Signer) and **CDNSKEY** (Child DNSKEY) records in your zone. These records automate the chain of trust management between your domain and the Top-Level Domain registry.
 
-| Record | Purpose | Contents |
-| --- | --- | --- |
-| **CDS** | High-level instruction | A hashed version of the public key (same data as a DS record) |
+| Record      | Purpose                | Contents                                                                           |
+| ----------- | ---------------------- | ---------------------------------------------------------------------------------- |
+| **CDS**     | High-level instruction | A hashed version of the public key (same data as a DS record)                      |
 | **CDNSKEY** | Public key instruction | The full public Key Signing Key (KSK) for the parent to generate its own DS record |
 
 Registrars that support [RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html) periodically scan your domain for these records and automatically update the DS record at the registry level. This eliminates manual DS record management and ensures seamless key rollovers.
@@ -46,4 +46,4 @@ Not all registrars support automatic CDS/CDNSKEY scanning. If your registrar doe
 ## DNSKEY flags
 
 - **ZSKs (Zone Signing Keys)**: flag `256`
-- **KSKs (Key Signing Keys)**: flag `257`
\ No newline at end of file
+- **KSKs (Key Signing Keys)**: flag `257`
diff --git a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
index 266d6dcc5a7d28d..37222616afae066 100644
--- a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
+++ b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
@@ -6,7 +6,6 @@ products:
 title: DNSSEC keys
 sidebar:
   order: 5
-
 ---
 
 With [Foundation DNS](/dns/foundation-dns/), you can request that the ZSK/KSK pair that is used for [DNSSEC](/dns/dnssec/) is unique to your Cloudflare account. To opt in to this feature, contact your account team.
@@ -17,4 +16,4 @@ All zones within your Cloudflare account - regardless of using [standard](/dns/n
 
 For more background information, refer to [How DNSSEC works](https://www.cloudflare.com/learning/dns/dnssec/how-dnssec-works/).
 
-For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
\ No newline at end of file
+For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
diff --git a/src/content/docs/dns/foundation-dns/index.mdx b/src/content/docs/dns/foundation-dns/index.mdx
index 0c60c2a7c820aca..bb4381b3a49156f 100644
--- a/src/content/docs/dns/foundation-dns/index.mdx
+++ b/src/content/docs/dns/foundation-dns/index.mdx
@@ -6,22 +6,21 @@ products:
 title: Foundation DNS
 sidebar:
   order: 4
-
 ---
 
 Foundation DNS is the Cloudflare DNS offering for enterprise customers.
 
 With Foundation DNS, you get access to increased reliability, security, and insights. Features include the following:
 
-* [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
-  * Strategically distributed IPs to enhance resiliency
-  * Reduced exposure to incidents or software regression
-  * More consistent nameserver assignment
-* [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
-* Additional DNS settings, including:
-  * [Zone defaults](/dns/additional-options/dns-zone-defaults/)
-  * [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
-  * Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
+- [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
+  - Strategically distributed IPs to enhance resiliency
+  - Reduced exposure to incidents or software regression
+  - More consistent nameserver assignment
+- [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
+- Additional DNS settings, including:
+  - [Zone defaults](/dns/additional-options/dns-zone-defaults/)
+  - [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
+  - Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
 
 ## Availability
 
@@ -33,5 +32,5 @@ Both advanced nameservers and unique ZSK/KSK are opt-in configurations. Refer to
 
 ## Related resources
 
-* [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
-* [Product page](https://www.cloudflare.com/dns/foundation-dns/)
+- [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
+- [Product page](https://www.cloudflare.com/dns/foundation-dns/)
diff --git a/src/content/docs/dns/glossary.mdx b/src/content/docs/dns/glossary.mdx
index c7e9390c51ff273..6b99f261ae66987 100644
--- a/src/content/docs/dns/glossary.mdx
+++ b/src/content/docs/dns/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 30
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's DNS documentation.
 
diff --git a/src/content/docs/dns/internal-dns/analytics.mdx b/src/content/docs/dns/internal-dns/analytics.mdx
index af54b9d66ef1e04..b1608c69e81f1a0 100644
--- a/src/content/docs/dns/internal-dns/analytics.mdx
+++ b/src/content/docs/dns/internal-dns/analytics.mdx
@@ -28,4 +28,4 @@ The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to c
 
 Leverage Logpush jobs for [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation.
 
-You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
\ No newline at end of file
+You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
index 115c06fb29de7c0..304c2d379c31eef 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
@@ -6,10 +6,9 @@ products:
 title: Create subdomain records
 sidebar:
   order: 4
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="create-subdomain-record" product="dns" />
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
index bcaca8ad13ed17d..6cfa20495a46cc1 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
@@ -6,24 +6,23 @@ products:
 title: Set up email records
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 There are three reasons to set up email records for your domain:
 
-* To make sure your domain can [receive email](#receive-email).
-* To make sure your domain can [send and receive email](#send-and-receive-email).
-* To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
+- To make sure your domain can [receive email](#receive-email).
+- To make sure your domain can [send and receive email](#send-and-receive-email).
+- To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
 
 The exact values for your DNS mail records depend on your email provider. If you have issues, review the [Troubleshooting](/dns/troubleshooting/email-issues/) and contact your email service provider to confirm your DNS records are correct.
 
-***
+---
 
 <Render file="add-mx-records" product="dns" />
 
-***
+---
 
 ## Prevent domain spoofing
 
@@ -35,4 +34,4 @@ Refer to [Security records](/dmarc-management/security-records/) to learn how to
 
 ## Proxy SMTP traffic
 
-By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
\ No newline at end of file
+By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
diff --git a/src/content/docs/dns/manage-dns-records/how-to/index.mdx b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
index f0d1c4dd9c45127..8ec9e0fc39b8c4d 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
@@ -11,10 +11,9 @@ head:
   - tag: title
     content: DNS records - How to
 description: Learn how to use Cloudflare DNS to manage your DNS records.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following resources for more information about creating and maintaining DNS records:
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
index e8f26982405820e..44177c0cbae3d1a 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
@@ -6,7 +6,6 @@ products:
 title: Dynamically update DNS records
 sidebar:
   order: 13
-
 ---
 
 Most Internet service providers and some hosting providers dynamically update their customer's IP addresses. If this situation applies to you, you need an automated solution to dynamically update your DNS records in Cloudflare.
@@ -17,4 +16,4 @@ Create a script to monitor IP address changes and then have that script push cha
 
 ## ddclient
 
-[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
\ No newline at end of file
+[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
index 9768ac45ceeda63..980e98757c3145e 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
@@ -6,7 +6,6 @@ products:
 title: Round-robin DNS
 sidebar:
   order: 18
-
 ---
 
 To randomly distribute traffic across multiple servers, set up multiple DNS `A` or `AAAA` records for the same hostname.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
index d21e31b5faedd36..886b037b118a29a 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
@@ -7,10 +7,9 @@ source: https://support.cloudflare.com/hc/en-us/articles/360021357131-Delegating
 title: Delegate subdomains
 sidebar:
   order: 20
-
 ---
 
-import { FeatureTable, DashButton, Render } from "~/components"
+import { FeatureTable, DashButton, Render } from "~/components";
 
 Subdomain delegation allows different individuals, teams, or organizations to manage different subdomains of a site.
 
@@ -30,7 +29,7 @@ Cloudflare's CDN and security services are not applied to delegated subdomains.
 
 <FeatureTable id="dns.subdomain_delegation" />
 
-***
+---
 
 ## Delegate a subdomain (outgoing)
 
@@ -43,12 +42,12 @@ To delegate a subdomain such as `blog.example.com`, tell DNS resolvers where to
    <DashButton url="/?to=/:account/:zone/dns/records" />
 
 4. Create `NS` records for the subdomain. For example:
-   * `blog.example.com NS ns1.externalhost.com`
-   * `blog.example.com NS ns2.externalhost.com`
-   * `blog.example.com NS ns3.externalhost.com`
-   :::note
-   The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
-   :::
+   - `blog.example.com NS ns1.externalhost.com`
+   - `blog.example.com NS ns2.externalhost.com`
+   - `blog.example.com NS ns3.externalhost.com`
+     :::note
+     The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
+     :::
 5. (Optional) If the delegated nameserver has DNSSEC enabled, [add the `DS` record](/dns/dnssec/#1-activate-dnssec-in-cloudflare) in Cloudflare.
 
 ### Limits
diff --git a/src/content/docs/dns/manage-dns-records/reference/index.mdx b/src/content/docs/dns/manage-dns-records/reference/index.mdx
index 435c9bbea21f1f9..1bbba02e42aadf2 100644
--- a/src/content/docs/dns/manage-dns-records/reference/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Reference — DNS records
 description: Check information about record types, status and additional options.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
index 99740688e33b318..67e4399d03b9c75 100644
--- a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: DNS record comments and tags
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 Use DNS record comments and tags to categorize and clarify the purpose of DNS records within Cloudflare.
 
@@ -20,19 +19,17 @@ Comments provide a unique descriptions for specific records, whereas tags group
 
 These attributes are particularly useful when:
 
-* Multiple teams are managing DNS records within the same zone.
-* Your zone contains a large number of DNS records.
-* You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
+- Multiple teams are managing DNS records within the same zone.
+- Your zone contains a large number of DNS records.
+- You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
 
 :::note
 
-
 The information in record attributes will not impact DNS record resolution or propagation timing and is only meant for your private reference. This information is only visible to [members](/fundamentals/manage-members/manage/) of your Cloudflare account and is not visible publicly.
 
-
 :::
 
-***
+---
 
 ## Availability
 
@@ -46,7 +43,7 @@ Comments and tags are only supported for [primary zones (full setup)](/dns/zone-
 
 <FeatureTable id="dns.record_tags" />
 
-***
+---
 
 ## Add or edit record attributes
 
@@ -56,7 +53,7 @@ You can also add or edit attributes by [exporting and re-importing](/dns/manage-
 
 When exporting and importing, special tags starting by `cf-` allow you to control specific Cloudflare configurations. On export, these tags are automatically added to reflect the current configuration for each record on your zone. Refer to [reserved cf- tags](/dns/manage-dns-records/how-to/import-and-export/#reserved-cf--tags) for details.
 
-***
+---
 
 ## Reference
 
diff --git a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
index 41114679b9e211e..3f25313a41b3cd5 100644
--- a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
@@ -6,7 +6,6 @@ products:
 title: Time to Live (TTL)
 sidebar:
   order: 3
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -33,4 +32,4 @@ A TTL of **Auto** is set to 300 seconds (five minutes).
 
 ## Nameserver TTL
 
-[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
\ No newline at end of file
+[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
index 2abc708b8e738ad..4df29d02c4d8f19 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
@@ -29,7 +29,6 @@ When your zone has DNS records that are not proxied, the **DNS Records** page di
 
 `Proxying is required for most security and performance features. Set your DNS records to proxied by clicking "Edit" in the table below, to benefit from DDoS protection, security rules, caching, and more.`
 
-
 Individual DNS records may also display warnings. The specific message depends on whether the record can be proxied.
 
 ---
@@ -51,4 +50,4 @@ When a DNS-only record points to the same origin server as a proxied record, a `
 To mitigate this risk:
 
 - Analyze the impact of hosting multiple services on the same origin server in cases when you cannot avoid having DNS-only records.
-- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
\ No newline at end of file
+- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
index 104ad57575d8b7f..6dc331f5f84f29c 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
@@ -11,11 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS records
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
 
-* [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
+- [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
diff --git a/src/content/docs/dns/nameservers/advanced-nameservers.mdx b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
index 6138cff878b675f..e545226613700b5 100644
--- a/src/content/docs/dns/nameservers/advanced-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
@@ -7,5 +7,4 @@ title: Advanced nameservers
 external_link: /dns/foundation-dns/advanced-nameservers/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
index c9268ed929c445c..d6fd863c76c52cf 100644
--- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
@@ -56,6 +56,7 @@ The next step depends on whether you are using [Cloudflare Registrar](/registrar
 
 - If you are using Cloudflare Registrar for your domain, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to add the custom nameservers and IP addresses as glue records to the domain.
 - If you are not using Cloudflare Registrar for your domain, add the zone custom nameservers at your registrar as your authoritative nameservers and as glue (A and AAAA) records ([RFC 1912](https://www.rfc-editor.org/rfc/rfc1912.html)). If you do not add these records, DNS lookups for your domain will fail.
+
 ### Secondary zones
 
 If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), you can still set up zone custom nameservers. After following the [steps above](/dns/nameservers/custom-nameservers/zone-custom-nameservers/#primary-zones-full-setup) to create zone custom nameservers, do the following:
diff --git a/src/content/docs/dns/private-origins/index.mdx b/src/content/docs/dns/private-origins/index.mdx
index 8398f269855ab93..49be787e2f6008e 100644
--- a/src/content/docs/dns/private-origins/index.mdx
+++ b/src/content/docs/dns/private-origins/index.mdx
@@ -23,7 +23,8 @@ import {
 } from "~/components";
 
 <Description>
-Proxy HTTP/HTTPS traffic from public hostnames to origins in your private network.
+	Proxy HTTP/HTTPS traffic from public hostnames to origins in your private
+	network.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/dns/reference/all-features.mdx b/src/content/docs/dns/reference/all-features.mdx
index 9186a4860de7efa..8ef860d82833097 100644
--- a/src/content/docs/dns/reference/all-features.mdx
+++ b/src/content/docs/dns/reference/all-features.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 4
 head: []
 description: Review information on all Cloudflare DNS features and their availability.
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
diff --git a/src/content/docs/dns/reference/analytics-mcp-server.mdx b/src/content/docs/dns/reference/analytics-mcp-server.mdx
index de1faf7d51e1b2b..6d120789cebde25 100644
--- a/src/content/docs/dns/reference/analytics-mcp-server.mdx
+++ b/src/content/docs/dns/reference/analytics-mcp-server.mdx
@@ -7,5 +7,4 @@ title: Analytics MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dns-analytics
 sidebar:
   order: 90
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/dns/reference/best-practices.mdx b/src/content/docs/dns/reference/best-practices.mdx
index c4fe1210a6d1a7e..9ef1525a0d2fb08 100644
--- a/src/content/docs/dns/reference/best-practices.mdx
+++ b/src/content/docs/dns/reference/best-practices.mdx
@@ -7,5 +7,4 @@ title: Migrate DNS from BIND
 external_link: /learning-paths/dns-best-practices/concepts/
 sidebar:
   order: 4
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/dns/reference/domain-connect.mdx b/src/content/docs/dns/reference/domain-connect.mdx
index 06e2489b08294a7..fa4d6d8026995b0 100644
--- a/src/content/docs/dns/reference/domain-connect.mdx
+++ b/src/content/docs/dns/reference/domain-connect.mdx
@@ -23,8 +23,8 @@ In practice, this means that when a user that owns `example.com` and has Cloudfl
 
 ### Before you begin
 
-* Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
-* Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
+- Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
+- Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
 
 ### 1. Add templates to the repository
 
@@ -32,12 +32,12 @@ Domain Connect templates are published and maintained on a GitHub repository.
 
 1. Create a fork of the [templates repository](https://github.com/Domain-Connect/Templates).
 2. Add your template. You can create a copy of one of the existing templates and edit it according to your needs.
-   * Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
-	 :::note
-	 Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
-	 :::
-   * If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
-   * You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
+   - Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
+     :::note
+     Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
+     :::
+   - If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
+   - You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
 3. Make sure you follow the naming format defined by Domain Connect: `<providerId>.<serviceId>.json`.
 
 :::note[Tip]
@@ -155,4 +155,4 @@ The most common issues after template onboarding are validation errors, typicall
 
 You can fix these by republishing the signature, using tools such as the one provided by [Domain Connect](https://exampleservice.domainconnect.org/sig). Additionally, you can test signature validation with this [public key debug tool](https://github.com/kerolasa/dc-debug-pubkey).
 
-[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
\ No newline at end of file
+[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
diff --git a/src/content/docs/dns/reference/index.mdx b/src/content/docs/dns/reference/index.mdx
index e12d2e5c169f815..51f81d1b1b3aeac 100644
--- a/src/content/docs/dns/reference/index.mdx
+++ b/src/content/docs/dns/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/reference/recommended-third-party-tools.mdx b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
index 3382d1ddc811487..61e3bd775e91b13 100644
--- a/src/content/docs/dns/reference/recommended-third-party-tools.mdx
+++ b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
@@ -7,15 +7,14 @@ sidebar:
   order: 3
 head: []
 description: List of recommended third-party tools for DNS testing and troubleshooting.
-
 ---
 
 You can use the third-party tools listed below to test and troubleshoot DNS settings.
 
-* [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
+- [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
 
-* [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
+- [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
 
-* [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
+- [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
 
-* [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
+- [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
diff --git a/src/content/docs/dns/troubleshooting/email-issues.mdx b/src/content/docs/dns/troubleshooting/email-issues.mdx
index 417ecfa92fdf7e1..291bb8f2240fef4 100644
--- a/src/content/docs/dns/troubleshooting/email-issues.mdx
+++ b/src/content/docs/dns/troubleshooting/email-issues.mdx
@@ -85,12 +85,12 @@ If you are not sure whether the DNS content itself is correct, compare it with t
 
 Common examples include:
 
-| Provider | MX records | SPF record |
-| --- | --- | --- |
-| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all` |
-| Microsoft 365 | `<your-domain>.mail.protection.outlook.com` (priority `0`) | `v=spf1 include:spf.protection.outlook.com -all` |
-| iCloud Mail | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`) | `v=spf1 include:icloud.com ~all` |
-| Mailgun | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`) | `v=spf1 include:mailgun.org ~all` |
+| Provider         | MX records                                                                                                                                                                           | SPF record                                       |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
+| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all`            |
+| Microsoft 365    | `<your-domain>.mail.protection.outlook.com` (priority `0`)                                                                                                                           | `v=spf1 include:spf.protection.outlook.com -all` |
+| iCloud Mail      | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`)                                                                                                                    | `v=spf1 include:icloud.com ~all`                 |
+| Mailgun          | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`)                                                                                                                              | `v=spf1 include:mailgun.org ~all`                |
 
 Always confirm the exact values with your provider before making changes.
 
diff --git a/src/content/docs/dns/troubleshooting/index.mdx b/src/content/docs/dns/troubleshooting/index.mdx
index 2ad611b0f95694a..b616c9d14356e9f 100644
--- a/src/content/docs/dns/troubleshooting/index.mdx
+++ b/src/content/docs/dns/troubleshooting/index.mdx
@@ -9,8 +9,13 @@ sidebar:
   label: Full resources list
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 The following topics are useful for troubleshooting DNS issues.
 
-<ResourcesBySelector directory="dns" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+<ResourcesBySelector
+	directory="dns"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
index 96a01af7dd298db..1b87486546a0e69 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
@@ -11,7 +11,13 @@ description: >-
   If you initially configured a full setup you can later convert your zone to use incoming zone transfers (Cloudflare as secondary).
 ---
 
-import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 If you initially configured a [primary setup (full)](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/).
 
@@ -37,14 +43,14 @@ Follow the steps below to achieve this conversion.
    <Render file="tsig-definition" product="dns" />
 
    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
-
-   <Render file="tsig-create-dash" product="dns" />
-
-   </TabItem> <TabItem label="API">
-
-   <Render file="tsig-create-api" product="dns" />
-
-   </TabItem> </Tabs>
+   
+      <Render file="tsig-create-dash" product="dns" />
+   
+      </TabItem> <TabItem label="API">
+   
+      <Render file="tsig-create-api" product="dns" />
+   
+      </TabItem> </Tabs>
 
 3. Create a peer server.
 
@@ -58,8 +64,8 @@ Follow the steps below to achieve this conversion.
    <DashButton url="/?to=/:account/:zone/dns/settings" />
 
 3. Select **Manage linked peers** under **DNS Zone Transfers**.
-3. Link the peer server you created in the previous steps and select **Save**.
-4. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
-5. Confirm the DNS records are transferring as expected.
-6. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
-7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
+4. Link the peer server you created in the previous steps and select **Save**.
+5. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
+6. Confirm the DNS records are transferring as expected.
+7. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
+8. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
index f25552f8df2c42b..6c458149ea4d45b 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
@@ -66,7 +66,7 @@ If you are counting on Universal SSL certificates to cover your website or appli
 :::
 
 Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page
- and add the DS record to your registrar.
+and add the DS record to your registrar.
 
 Once all the DNS TTLs expire, all your DNS queries will be answered by the Cloudflare global network.
 
diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx
index 04bc2c37ce4a3a5..42226cfb7ad094d 100644
--- a/src/content/docs/dns/zone-setups/conversions/index.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/index.mdx
@@ -15,4 +15,4 @@ import { DirectoryListing } from "~/components";
 
 You can perform the following DNS setup conversions:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/full-setup/index.mdx b/src/content/docs/dns/zone-setups/full-setup/index.mdx
index 6a5717e76167fdf..f92648b37069542 100644
--- a/src/content/docs/dns/zone-setups/full-setup/index.mdx
+++ b/src/content/docs/dns/zone-setups/full-setup/index.mdx
@@ -19,4 +19,4 @@ For this to work, you must go through a few steps that involve not only Cloudfla
 
 ## Availability
 
-<FeatureTable id="dns.full_setup" />
\ No newline at end of file
+<FeatureTable id="dns.full_setup" />
diff --git a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
index 45952ff6ebee99e..1697f7240a301ac 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: DNS resolution in partial zones
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 When you have a partial zone (<GlossaryTooltip term="CNAME setup" link="/dns/zone-setups/partial-setup/">CNAME setup</GlossaryTooltip>), Cloudflare handles DNS records a bit differently from primary zones (full setup) in order to internally resolve the origin server where proxied HTTP requests are sent to.
 
@@ -62,7 +61,7 @@ When you avoid this situation - meaning you do not have the **target** of the CN
       end
 ```
 
-***
+---
 
 ## Records pointing to a partial zone within the same account
 
@@ -115,4 +114,4 @@ If such setup is in place, the subdomain (`www.partialzone.com` in this example)
       subgraph Authoritative DNS
       C
       end
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
index 0afa82eb5bc7ecb..627350007665712 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
@@ -13,7 +13,15 @@ description: >-
   A CNAME setup (also known as partial) allows you to use Cloudflare's reverse proxy while maintaining your primary and authoritative DNS provider.
 ---
 
-import { Details, Render, GlossaryTooltip, Steps, Tabs, TabItem, APIRequest } from "~/components";
+import {
+	Details,
+	Render,
+	GlossaryTooltip,
+	Steps,
+	Tabs,
+	TabItem,
+	APIRequest,
+} from "~/components";
 
 <Render file="partial-setup-definition" product="dns" />
 
@@ -40,7 +48,6 @@ A CNAME setup (partial) is only available to customers on a Business or Enterpri
 
 ## 1. Convert your zone and review DNS records
 
-
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 :::caution[Make sure you have the correct plan]
diff --git a/src/content/docs/dns/zone-setups/reference/domain-status.mdx b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
index 2d26b5684dba1b2..9541eaa1de5c4f2 100644
--- a/src/content/docs/dns/zone-setups/reference/domain-status.mdx
+++ b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
@@ -69,11 +69,11 @@ After you add your domain, Cloudflare performs checks on a schedule to confirm y
 
 The activation check behavior depends on your zone setup:
 
-| Zone setup                                                                                                                                                                                                                          | Activation requirement                                                                                                                            |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                           | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)      | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.         |
-| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                             | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                     |
+| Zone setup                                                                                                                                                                                                                      | Activation requirement                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                      | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/) | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.           |
+| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                        | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                       |
 
 ### Expected behavior for different plans
 
diff --git a/src/content/docs/dns/zone-setups/reference/index.mdx b/src/content/docs/dns/zone-setups/reference/index.mdx
index a6c71ff65f2b7a8..6185d7acd7149ea 100644
--- a/src/content/docs/dns/zone-setups/reference/index.mdx
+++ b/src/content/docs/dns/zone-setups/reference/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Reference — DNS zone setups
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
index 58cb7e6b8986b33..363f7e2bbee2c84 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Migrate subdomain to a new account
-
 ---
 
 When using a [subdomain setup](/dns/zone-setups/subdomain-setup/), you can have your subdomain as a separate zone within the same account as the parent domain or within a different account.
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
index 7523187ca70b247..1a8c8cfae71d112 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
@@ -9,15 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Rollback subdomain setup
-
 ---
 
 Refer to the following process to understand how you can rollback a [subdomain setup](/dns/zone-setups/subdomain-setup/) and recreate the corresponding subdomain DNS records in an existing parent zone within Cloudflare.
 
 ## Before you begin
 
-* This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
-* In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
+- This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
+- In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
 
 :::caution[Important]
 
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
index ed7910947587eae..8cbfcf5e76c38b0 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
@@ -9,17 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on full setup
-
 ---
 
 When the parent zone is using a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
 :::note
 
-
 The following steps are similar if your Cloudflare parent zone is in a secondary setup, with the only difference that you will use your external primary DNS provider to make any necessary adjustments to DNS records.
 
-
 :::
 
 ## Subdomain does not exist
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
index 46a0cf3ae1e1d99..0ae18341ccfb5ac 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on partial setup
-
 ---
 
-import { Details, TabItem, Tabs } from "~/components"
+import { Details, TabItem, Tabs } from "~/components";
 
 When the parent zone is using a [CNAME setup (partial)](/dns/zone-setups/partial-setup/)[^2], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
diff --git a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
index d7b45d34cc6ea33..485e9d9090a0bfb 100644
--- a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
+++ b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS setups
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
index ee6a63ef200265e..6c1cdba3b2785b7 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
@@ -17,7 +17,7 @@ When you [make edits](/dns/manage-dns-records/how-to/create-dns-records/) to Clo
 
 ## How to
 
-* [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
+- [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
index 854dcfad6b2831a..284707a6b0416f1 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
@@ -10,7 +10,6 @@ sidebar:
 
 Consider the sections below to understand the expected behaviors, depending on DNS record type and proxied status.
 
-
 ## Proxied records
 
 For each [proxied DNS record](/dns/proxy-status/) in your zone, Cloudflare will transfer out two `A` and two `AAAA` records.
@@ -42,4 +41,4 @@ The following records are not transferred out when you use Cloudflare as primary
 
 :::note
 Proxied Load Balancing records are transferred as explained in [Proxied records](#proxied-records).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
index bfd1df6c824f6a5..f5191d5c420f6ce 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Secondary DNS
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your secondary DNS.
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
index 463cb6408c5cbb2..2bb69c6bc3e6288 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
@@ -23,8 +23,8 @@ B & C <--DNS lookups--> D[Resolver] <--DNS lookups--> E((User))
 
 ## How to
 
-* [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
-* Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
+- [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
+- Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
index a21202b1749130a..b8a0e6712109252 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
@@ -81,4 +81,4 @@ Once you create a CNAME record at the apex, existing A or AAAA records on the zo
 
 ## Verify that your records are proxied
 
-Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
\ No newline at end of file
+Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
diff --git a/src/content/docs/durable-objects/api/alarms.mdx b/src/content/docs/durable-objects/api/alarms.mdx
index 4d576fbe8cd6cb3..fa9a03af7538bea 100644
--- a/src/content/docs/durable-objects/api/alarms.mdx
+++ b/src/content/docs/durable-objects/api/alarms.mdx
@@ -38,42 +38,42 @@ Although each Durable Object can only have one alarm set at a time, you can mana
 import { DurableObject } from "cloudflare:workers";
 
 export class AgentServer extends DurableObject {
-  // Schedule a one-time or recurring event
-  async scheduleEvent(id, runAt, repeatMs = null) {
-    await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
-    const currentAlarm = await this.ctx.storage.getAlarm();
-    if (!currentAlarm || runAt < currentAlarm) {
-      await this.ctx.storage.setAlarm(runAt);
-    }
-  }
-
-  async alarm() {
-    const now = Date.now();
-    const events = await this.ctx.storage.list({ prefix: "event:" });
-    let nextAlarm = null;
-
-    for (const [key, event] of events) {
-      if (event.runAt <= now) {
-        await this.processEvent(event);
-        if (event.repeatMs) {
-          event.runAt = now + event.repeatMs;
-          await this.ctx.storage.put(key, event);
-        } else {
-          await this.ctx.storage.delete(key);
-        }
-      }
-      // Track the next event time
-      if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
-        nextAlarm = event.runAt;
-      }
-    }
-
-    if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
-  }
-
-  async processEvent(event) {
-    // Your event handling logic here
-  }
+	// Schedule a one-time or recurring event
+	async scheduleEvent(id, runAt, repeatMs = null) {
+		await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
+		const currentAlarm = await this.ctx.storage.getAlarm();
+		if (!currentAlarm || runAt < currentAlarm) {
+			await this.ctx.storage.setAlarm(runAt);
+		}
+	}
+
+	async alarm() {
+		const now = Date.now();
+		const events = await this.ctx.storage.list({ prefix: "event:" });
+		let nextAlarm = null;
+
+		for (const [key, event] of events) {
+			if (event.runAt <= now) {
+				await this.processEvent(event);
+				if (event.repeatMs) {
+					event.runAt = now + event.repeatMs;
+					await this.ctx.storage.put(key, event);
+				} else {
+					await this.ctx.storage.delete(key);
+				}
+			}
+			// Track the next event time
+			if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
+				nextAlarm = event.runAt;
+			}
+		}
+
+		if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
+	}
+
+	async processEvent(event) {
+		// Your event handling logic here
+	}
 }
 ```
 
@@ -82,7 +82,6 @@ export class AgentServer extends DurableObject {
 ### `getAlarm`
 
 - <code>getAlarm()</code>: <Type text="number | null" />
-
   - If there is an alarm set, then return the currently set alarm time as the number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
   - If `getAlarm` is called while an [`alarm`](/durable-objects/api/alarms/#alarm) is already running, it returns `null` unless `setAlarm` has also been called since the alarm handler started running.
@@ -90,7 +89,6 @@ export class AgentServer extends DurableObject {
 ### `setAlarm`
 
 - <code> setAlarm(scheduledTimeMs <Type text="number" />) </code>: <Type text="void" />
-
   - Set the time for the alarm to run. Specify the time as the number of milliseconds elapsed since the UNIX epoch.
   - If you call `setAlarm` when there is already one scheduled, it will override the existing alarm.
 
@@ -103,7 +101,6 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `deleteAlarm`
 
 - `deleteAlarm()`: <Type text='void' />
-
   - Unset the alarm if there is a currently set alarm.
 
   - Calling `deleteAlarm()` inside the `alarm()` handler may prevent retries on a best-effort basis, but is not guaranteed.
@@ -113,11 +110,9 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `alarm`
 
 - <code>alarm(alarmInfo <Type text="Object" />)</code>: <Type text="void" />
-
   - Called by the system when a scheduled alarm time is reached.
 
   - The optional parameter `alarmInfo` object has two properties:
-
     - `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
     - `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
 
diff --git a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
index 541d4b55aeebebd..c41b19cc99bc69c 100644
--- a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
@@ -8,7 +8,16 @@ products:
   - durable-objects
 ---
 
-import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	GlossaryTooltip,
+	TypeScriptExample,
+	Details,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 :::note
 This page documents the storage API for legacy KV-backed Durable Objects.
@@ -83,6 +92,6 @@ KV-backed Durable Objects provide KV API methods which are asynchronous.
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
index 2e6c605ca634618..70afb0cebace527 100644
--- a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
@@ -8,7 +8,16 @@ products:
   - durable-objects
 ---
 
-import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	GlossaryTooltip,
+	TypeScriptExample,
+	Details,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 :::note
 This page documents the storage API for the newer SQLite-backed Durable Objects.
@@ -136,7 +145,11 @@ class MyDurableObject(DurableObject):
 - When writing data, every row update of an index counts as an additional row. However, indexes may be beneficial for read-heavy use cases. Refer to [Index for SQLite Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#indexes-in-sqlite).
 - Writing data to [SQLite virtual tables](https://www.sqlite.org/vtab.html) also counts towards rows written.
 
-<Render file="d1-do-supported-sqlite-extensions" product="d1" params={{ product: "Durable Objects support" }}/>
+<Render
+	file="d1-do-supported-sqlite-extensions"
+	product="d1"
+	params={{ product: "Durable Objects support" }}
+/>
 
 ### `exec`
 
@@ -161,7 +174,10 @@ Always consume the cursor fully before yielding the event loop. Call `.toArray()
 ```ts
 // ✅ Safe: cursor is fully consumed before any await
 const rows = this.ctx.storage.sql.exec("SELECT * FROM users").toArray();
-const result = await fetch("https://example.com", { method: "POST", body: JSON.stringify(rows) });
+const result = await fetch("https://example.com", {
+	method: "POST",
+	body: JSON.stringify(rows),
+});
 ```
 
 ```ts
@@ -351,6 +367,6 @@ ctx.storage.onNextSessionRestoreBookmark(bookmark)
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
index cbcc52ad9c8be68..28b40fdda357f9f 100644
--- a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
+++ b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
@@ -11,10 +11,13 @@ products:
 import { Render, GlossaryTooltip, WranglerConfig } from "~/components";
 
 <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> are a
+
 powerful compute API that provides a compute with storage building block. Each
 Durable Object has its own private, transactional, and strongly consistent
 storage. Durable Objects
+
 <GlossaryTooltip term="Storage API">Storage API</GlossaryTooltip> provides
+
 access to a Durable Object's attached storage.
 
 A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
diff --git a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
index 1f90f81aa40a253..163f0a7cc9d2cb5 100644
--- a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
+++ b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
@@ -82,7 +82,7 @@ Durable Objects will occasionally shut down and objects are restarted, which wil
 
 When a Durable Object is shut down, the object instance is automatically restarted and new requests are routed to the new instance. In-flight requests are handled as follows:
 
-- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage.  If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
+- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage. If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
 - **WebSocket connections**: WebSocket requests are terminated automatically during shutdown. This is so that the new instance can take over the connection as soon as possible.
 - **Other invocations (email, cron)**: Other invocations are treated similarly to HTTP requests.
 
diff --git a/src/content/docs/durable-objects/examples/agents.mdx b/src/content/docs/durable-objects/examples/agents.mdx
index 0a633feca9fcda1..822795f49b71103 100644
--- a/src/content/docs/durable-objects/examples/agents.mdx
+++ b/src/content/docs/durable-objects/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - durable-objects
----
\ No newline at end of file
+---
diff --git a/src/content/docs/durable-objects/examples/index.mdx b/src/content/docs/durable-objects/examples/index.mdx
index a885b12632c278f..3c4df69e31c31d3 100644
--- a/src/content/docs/durable-objects/examples/index.mdx
+++ b/src/content/docs/durable-objects/examples/index.mdx
@@ -14,4 +14,7 @@ import { ResourcesBySelector, GlossaryTooltip } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Durable Objects.
 
-<ResourcesBySelector types={["example"]} directory="durable-objects/examples/" />
+<ResourcesBySelector
+	types={["example"]}
+	directory="durable-objects/examples/"
+/>
diff --git a/src/content/docs/durable-objects/examples/websocket-server.mdx b/src/content/docs/durable-objects/examples/websocket-server.mdx
index 6c9fed4be7d126e..24b3a890045da9a 100644
--- a/src/content/docs/durable-objects/examples/websocket-server.mdx
+++ b/src/content/docs/durable-objects/examples/websocket-server.mdx
@@ -12,7 +12,13 @@ products:
   - durable-objects
 ---
 
-import { TabItem, Tabs, GlossaryTooltip, WranglerConfig, TypeScriptExample } from "~/components";
+import {
+	TabItem,
+	Tabs,
+	GlossaryTooltip,
+	WranglerConfig,
+	TypeScriptExample,
+} from "~/components";
 
 This example shows how to build a WebSocket server using <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> and Workers. The example exposes an endpoint to create a new WebSocket connection. This WebSocket connection echos any message while including the total number of WebSocket connections currently established. For more information, refer to [Use Durable Objects with WebSockets](/durable-objects/best-practices/websockets/).
 
diff --git a/src/content/docs/durable-objects/observability/data-studio.mdx b/src/content/docs/durable-objects/observability/data-studio.mdx
index 847423a93b479a1..39fe7cf43e104b3 100644
--- a/src/content/docs/durable-objects/observability/data-studio.mdx
+++ b/src/content/docs/durable-objects/observability/data-studio.mdx
@@ -40,4 +40,4 @@ You need to have at least the `Workers Platform Admin` [role](/fundamentals/mana
 
 All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/) for your security and compliance needs.
 
-- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
\ No newline at end of file
+- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
diff --git a/src/content/docs/durable-objects/platform/known-issues.mdx b/src/content/docs/durable-objects/platform/known-issues.mdx
index a590711f8bcb13e..8d63e009732811e 100644
--- a/src/content/docs/durable-objects/platform/known-issues.mdx
+++ b/src/content/docs/durable-objects/platform/known-issues.mdx
@@ -38,4 +38,4 @@ The Workers editor in the [Cloudflare dashboard](https://dash.cloudflare.com/) a
 
 Currently, when developing locally (using `npx wrangler dev`), Durable Object [alarm methods](/durable-objects/api/alarms) may fail after a hot reload (if you edit the code while the code is running locally).
 
-To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
\ No newline at end of file
+To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx
index ef53c2fd80d3d9c..26f4a596ac0219e 100644
--- a/src/content/docs/durable-objects/platform/limits.mdx
+++ b/src/content/docs/durable-objects/platform/limits.mdx
@@ -77,4 +77,3 @@ For Durable Object classes with [SQLite storage](/durable-objects/api/sqlite-sto
 <Render file="do-faq-limits" product="durable-objects" />
 
 <Render file="wall-time-limits" product="workers" />
-
diff --git a/src/content/docs/durable-objects/reference/data-location.mdx b/src/content/docs/durable-objects/reference/data-location.mdx
index 4f4ced530d3685f..9465de9ade8d4de 100644
--- a/src/content/docs/durable-objects/reference/data-location.mdx
+++ b/src/content/docs/durable-objects/reference/data-location.mdx
@@ -58,9 +58,9 @@ Note that it is also possible to specify a jurisdiction by creating an individua
 
 ### Supported locations
 
-| Parameter | Location                     |
-| --------- | ---------------------------- |
-| eu        | The European Union           |
+| Parameter | Location                       |
+| --------- | ------------------------------ |
+| eu        | The European Union             |
 | fedramp   | FedRAMP-compliant data centers |
 
 ## Provide a location hint
@@ -102,10 +102,14 @@ Hints are a best effort and not a guarantee. Unlike with jurisdictions, Durable
 | afr       | Africa <sup>2</sup>        |
 | me        | Middle East <sup>2</sup>   |
 
-<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the future.
+<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the
+future.
 
-<sup>2</sup> Durable Objects currently do not spawn in this location. Instead, the Durable Object will spawn in a nearby location which does support Durable Objects. For example, Durable Objects hinted to South America spawn in Eastern North America instead.
+<sup>2</sup> Durable Objects currently do not spawn in this location. Instead,
+the Durable Object will spawn in a nearby location which does support Durable
+Objects. For example, Durable Objects hinted to South America spawn in Eastern
+North America instead.
 
 ## Additional resources
 
-- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
\ No newline at end of file
+- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
diff --git a/src/content/docs/durable-objects/reference/data-security.mdx b/src/content/docs/durable-objects/reference/data-security.mdx
index e91b874429d9483..d410809c1239ec7 100644
--- a/src/content/docs/durable-objects/reference/data-security.mdx
+++ b/src/content/docs/durable-objects/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of Durable Objects, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/durable-objects/reference/environments.mdx b/src/content/docs/durable-objects/reference/environments.mdx
index 21a1b30c3e2981f..ac38518bf59f293 100644
--- a/src/content/docs/durable-objects/reference/environments.mdx
+++ b/src/content/docs/durable-objects/reference/environments.mdx
@@ -43,8 +43,6 @@ Durable Object bindings are not inherited. For example, you can define an enviro
 
 Because Wrangler appends the [environment name](/workers/wrangler/environments/) to the top-level name when publishing, for a Worker named `worker-name` the above example is equivalent to:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -71,8 +69,6 @@ Because Wrangler appends the [environment name](/workers/wrangler/environments/)
 
 If you want an environment-specific binding that accesses the same Objects as the top-level binding, specify the top-level Worker code name explicitly using `script_name`:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -118,9 +114,10 @@ To start remote development:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select an existing Worker.
 3. Select the **Edit code** icon located on the upper-right of the screen.
 
 :::caution
 Remote development is only available for KV-backed Durable Objects. SQLite-backed Durable Objects do not support remote development.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/durable-objects/reference/faq.mdx b/src/content/docs/durable-objects/reference/faq.mdx
index 2cff6f2d62e279c..84262a5b52de7b9 100644
--- a/src/content/docs/durable-objects/reference/faq.mdx
+++ b/src/content/docs/durable-objects/reference/faq.mdx
@@ -12,12 +12,12 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="do-faq-pricing" product="durable-objects"/>
+<Render file="do-faq-pricing" product="durable-objects" />
 
 ## Limits
 
-<Render file="do-faq-limits" product="durable-objects"/>
+<Render file="do-faq-limits" product="durable-objects" />
 
 ## Metrics and analytics
 
-<Render file="do-faq-metrics-and-analytics" product="durable-objects"/>
\ No newline at end of file
+<Render file="do-faq-metrics-and-analytics" product="durable-objects" />
diff --git a/src/content/docs/durable-objects/reference/glossary.mdx b/src/content/docs/durable-objects/reference/glossary.mdx
index b95a0d5b0e6b08d..1e9b3d062d8832e 100644
--- a/src/content/docs/durable-objects/reference/glossary.mdx
+++ b/src/content/docs/durable-objects/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - durable-objects
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Durable Objects documentation.
 
diff --git a/src/content/docs/durable-objects/reference/in-memory-state.mdx b/src/content/docs/durable-objects/reference/in-memory-state.mdx
index 772169b848b90bd..7ef26232dd22b2b 100644
--- a/src/content/docs/durable-objects/reference/in-memory-state.mdx
+++ b/src/content/docs/durable-objects/reference/in-memory-state.mdx
@@ -20,21 +20,21 @@ A common pattern is to initialize a Durable Object from [persistent storage](/du
 import { DurableObject } from "cloudflare:workers";
 
 export class Counter extends DurableObject {
-  constructor(ctx, env) {
-    super(ctx, env);
-    // `blockConcurrencyWhile()` ensures no requests are delivered until
-    // initialization completes.
-    this.ctx.blockConcurrencyWhile(async () => {
-      let stored = await this.ctx.storage.get("value");
-      // After initialization, future reads do not need to access storage.
-      this.value = stored || 0;
-    });
-  }
-
-  // Handle HTTP requests from clients.
-  async fetch(request) {
-    // use this.value rather than storage
-  }
+	constructor(ctx, env) {
+		super(ctx, env);
+		// `blockConcurrencyWhile()` ensures no requests are delivered until
+		// initialization completes.
+		this.ctx.blockConcurrencyWhile(async () => {
+			let stored = await this.ctx.storage.get("value");
+			// After initialization, future reads do not need to access storage.
+			this.value = stored || 0;
+		});
+	}
+
+	// Handle HTTP requests from clients.
+	async fetch(request) {
+		// use this.value rather than storage
+	}
 }
 ```
 
diff --git a/src/content/docs/durable-objects/video-tutorials.mdx b/src/content/docs/durable-objects/video-tutorials.mdx
index 4af3068247492a4..4390949faf52bc7 100644
--- a/src/content/docs/durable-objects/video-tutorials.mdx
+++ b/src/content/docs/durable-objects/video-tutorials.mdx
@@ -11,11 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Introduction to Durable Objects"
-        description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
-        href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
-    />
+	<LinkCard
+		title="Introduction to Durable Objects"
+		description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
+		href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
+	/>
 </CardGrid>
-
-
diff --git a/src/content/docs/dynamic-workers/usage/bindings.mdx b/src/content/docs/dynamic-workers/usage/bindings.mdx
index 5fed51bc8b0efe7..2970ac1c09b9962 100644
--- a/src/content/docs/dynamic-workers/usage/bindings.mdx
+++ b/src/content/docs/dynamic-workers/usage/bindings.mdx
@@ -10,7 +10,7 @@ products:
 
 import { WranglerConfig } from "~/components";
 
-Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use. 
+Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use.
 
 This allows you to:
 
@@ -21,7 +21,8 @@ This allows you to:
 ## Custom Bindings with Dynamic Workers
 
 With custom bindings, you:
-- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer. 
+
+- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer.
 - **Pass it to the Dynamic Worker as a binding**: It just calls methods like `this.env.CHAT_ROOM.post("Hello!")` without knowing anything about the implementation behind it.
 
 ### How it works
@@ -29,54 +30,65 @@ With custom bindings, you:
 #### Step 1: Define the binding
 
 To create a custom binding, your loader Worker needs to implement a [`WorkerEntrypoint` class](/workers/runtime-apis/bindings/service-bindings/rpc#the-workerentrypoint-class) and export it. The methods you define on this class are the methods the Dynamic Worker will be able to call.
+
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint {
-  async post(text: string): Promise<void> {
-    // Your implementation here
-  }
+	async post(text: string): Promise<void> {
+		// Your implementation here
+	}
 }
 ```
+
 #### Step 2: Pass it to the Dynamic Worker
-Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`. 
+
+Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`.
 
 ```ts
 let chatRoom = ctx.exports.ChatRoom({ props: { roomName: "#bot-chat" } });
 
 let worker = env.LOADER.load({
-  env: { CHAT_ROOM: chatRoom },
-  // ...
+	env: { CHAT_ROOM: chatRoom },
+	// ...
 });
 ```
 
-From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call: 
+From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call:
+
 ```ts
 // Inside the Dynamic Worker
 await this.env.CHAT_ROOM.post("Hello!");
 ```
+
 #### Step 3: Customize per user with props
-One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user. 
+
+One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user.
 
 ```ts
 // Same class, different props per user
-let aliceRoom = ctx.exports.ChatRoom({ props: { roomName: "#alice", apiKey: ALICE_KEY } });
-let bobRoom   = ctx.exports.ChatRoom({ props: { roomName: "#bob", apiKey: BOB_KEY } });
+let aliceRoom = ctx.exports.ChatRoom({
+	props: { roomName: "#alice", apiKey: ALICE_KEY },
+});
+let bobRoom = ctx.exports.ChatRoom({
+	props: { roomName: "#bob", apiKey: BOB_KEY },
+});
 ```
 
 When the Dynamic Worker calls a method on the binding, it's actually making a call back to your loader Worker, that's where the method runs. Inside that method, you can read the `props` via [`this.ctx.props`](/workers/runtime-apis/context#props). Only the loader Worker has access to the props, the Dynamic Worker never sees them.
 
 ```ts
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-  async post(text: string): Promise<void> {
-    // Props are set when the stub is created — the Dynamic Worker never sees them
-    let roomName = this.ctx.props.roomName;
-    await postToChat(roomName, text);
-  }
+	async post(text: string): Promise<void> {
+		// Props are set when the stub is created — the Dynamic Worker never sees them
+		let roomName = this.ctx.props.roomName;
+		await postToChat(roomName, text);
+	}
 }
 ```
 
 ### Example: Chat room agent
+
 Here's a complete example putting it all together. Say you're building a platform where AI agents can post to chat rooms. Each agent should only be able to post to its assigned room and it should never see the API key used to authenticate.
 
 You define a `ChatRoom` class in your parent Worker. This class has a `post` method, the only method the Dynamic Worker can call on this binding. Inside this class, you control which room the message goes to, which API key is used, and what name is attached to the message.
@@ -85,44 +97,46 @@ You define a `ChatRoom` class in your parent Worker. This class has a `post` met
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-  async post(text: string): Promise<void> {
-    let { apiKey, botName, roomName } = this.ctx.props;
+	async post(text: string): Promise<void> {
+		let { apiKey, botName, roomName } = this.ctx.props;
 
-    // Prefix the message with the bot's name.
-    text = `[${botName}]: ${text}`;
+		// Prefix the message with the bot's name.
+		text = `[${botName}]: ${text}`;
 
-    // Send it to the chat service.
-    await postToChat(apiKey, roomName, text);
-  }
+		// Send it to the chat service.
+		await postToChat(apiKey, roomName, text);
+	}
 }
 
 type ChatRoomProps = {
-  apiKey: string;
-  roomName: string;
-  botName: string;
+	apiKey: string;
+	roomName: string;
+	botName: string;
 };
 ```
+
 You export one `ChatRoom` class, but each stub you create can have different `props` — a different room name, a different API key, a different bot name. The `props` are set when you create the stub, and the Dynamic Worker never sees them.
 
 Now pass it to a Dynamic Worker:
+
 ```ts
 // Create a stub scoped to a specific room.
 let chatRoom = ctx.exports.ChatRoom({
-  props: {
-    apiKey,
-    roomName: "#bot-chat",
-    botName: "Robo",
-  },
+	props: {
+		apiKey,
+		roomName: "#bot-chat",
+		botName: "Robo",
+	},
 });
 
 let worker = env.LOADER.load({
-  env: {
-    CHAT_ROOM: chatRoom,
-  },
-  compatibilityDate: "$today",
-  mainModule: "index.js",
-  modules: {
-    "index.js": `
+	env: {
+		CHAT_ROOM: chatRoom,
+	},
+	compatibilityDate: "$today",
+	mainModule: "index.js",
+	modules: {
+		"index.js": `
       export class Agent extends WorkerEntrypoint {
         async run() {
           // This is all the Dynamic Worker sees.
@@ -130,13 +144,14 @@ let worker = env.LOADER.load({
         }
       }
     `,
-  },
-  globalOutbound: null,
+	},
+	globalOutbound: null,
 });
 
 return worker.getEntrypoint("Agent").run();
 ```
-The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages. 
+
+The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages.
 
 ### Tip: Tell your agent about the types
 
@@ -146,45 +161,52 @@ Make sure your `WorkerEntrypoint` class extends the TypeScript type so the decla
 
 ## Passing normal Workers bindings
 
-To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose. 
+To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose.
 
 ### Example: Scoping a KV namespace per customer
 
 First, bind the KV namespace to your loader Worker. Then in your loader Worker, export a class that uses the KV binding and defines the methods Dynamic Workers can call:
+
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
-export class MyStorage extends WorkerEntrypoint<Cloudflare.Env, MyStorageProps> {
-  // Export this class from your loader Worker
-  // The Dynamic Worker will be able to call get() and put()
-  async get(key: string): Promise<string | null> {
-    // Prefix the key so this customer can only access their own data
-    return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
-  }
-
-  async put(key: string, value: string): Promise<void> {
-    await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
-  }
+export class MyStorage extends WorkerEntrypoint<
+	Cloudflare.Env,
+	MyStorageProps
+> {
+	// Export this class from your loader Worker
+	// The Dynamic Worker will be able to call get() and put()
+	async get(key: string): Promise<string | null> {
+		// Prefix the key so this customer can only access their own data
+		return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
+	}
+
+	async put(key: string, value: string): Promise<void> {
+		await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
+	}
 }
 
 type MyStorageProps = {
-  prefix: string;
+	prefix: string;
 };
 ```
+
 Then pass it to the Dynamic Worker with a customer-specific prefix:
+
 ```ts
 // Create a stub scoped to this customer's prefix
 let storage = ctx.exports.MyStorage({
-  props: { prefix: `customer-${customerId}` },
+	props: { prefix: `customer-${customerId}` },
 });
 
 let worker = env.LOADER.load({
-  env: { STORAGE: storage },
-  // ...
+	env: { STORAGE: storage },
+	// ...
 });
 ```
 
 The Dynamic Worker just uses it like any other binding:
+
 ```ts
 // Inside the Dynamic Worker, it just sees STORAGE with get and put
 let value = await this.env.STORAGE.get("settings");
@@ -197,7 +219,7 @@ For persistent storage that lives with each Dynamic Worker, see [Durable Object
 
 ## Capability-based Sandboxing
 
-Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it.  If it hasn't received a stub for something, it can't access it. 
+Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it. If it hasn't received a stub for something, it can't access it.
 
 This is powered by Workers RPC, also known as [Cap'n Web](https://github.com/cloudflare/capnweb), an RPC system designed to pass object references across security boundaries. When a Dynamic Worker receives a stub, it can call that object's methods and each call is an RPC back to the original object in your loader Worker. Stubs have no global identifier and cannot be forged, the only way to obtain one is to receive it.
 
diff --git a/src/content/docs/email-routing/email-workers/local-development.mdx b/src/content/docs/email-routing/email-workers/local-development.mdx
index 7764c919d997f0d..ab7767665ecebf0 100644
--- a/src/content/docs/email-routing/email-workers/local-development.mdx
+++ b/src/content/docs/email-routing/email-workers/local-development.mdx
@@ -41,7 +41,7 @@ You can now test receiving, replying, and sending emails in your local environme
 Consider this example Email Worker script that uses the open source [`postal-mime`](https://www.npmjs.com/package/postal-mime) email parser:
 
 ```ts
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
 	async email(message, env, ctx) {
@@ -79,31 +79,31 @@ This is what you get in the console:
 
 ```json
 {
-  headers: [
-    {
-      key: 'received',
-      value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
-    },
-    { key: 'from', value: '"John" <sender@example.com>' },
-    { key: 'reply-to', value: 'sender@example.com' },
-    { key: 'to', value: 'recipient@example.com' },
-    { key: 'subject', value: 'Testing Email Workers Local Dev' },
-    { key: 'content-type', value: 'text/html; charset="windows-1252"' },
-    { key: 'x-mailer', value: 'Curl' },
-    { key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
-    {
-      key: 'message-id',
-      value: '<6114391943504294873000@ZSH-GHOSTTY>'
-    }
-  ],
-  from: { address: 'sender@example.com', name: 'John' },
-  to: [ { address: 'recipient@example.com', name: '' } ],
-  replyTo: [ { address: 'sender@example.com', name: '' } ],
-  subject: 'Testing Email Workers Local Dev',
-  messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
-  date: '2024-08-27T15:49:44.000Z',
-  html: 'Hi there\n',
-  attachments: []
+	"headers": [
+		{
+			"key": "received",
+			"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
+		},
+		{ "key": "from", "value": "\"John\" <sender@example.com>" },
+		{ "key": "reply-to", "value": "sender@example.com" },
+		{ "key": "to", "value": "recipient@example.com" },
+		{ "key": "subject", "value": "Testing Email Workers Local Dev" },
+		{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
+		{ "key": "x-mailer", "value": "Curl" },
+		{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
+		{
+			"key": "message-id",
+			"value": "<6114391943504294873000@ZSH-GHOSTTY>"
+		}
+	],
+	"from": { "address": "sender@example.com", "name": "John" },
+	"to": [{ "address": "recipient@example.com", "name": "" }],
+	"replyTo": [{ "address": "sender@example.com", "name": "" }],
+	"subject": "Testing Email Workers Local Dev",
+	"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
+	"date": "2024-08-27T15:49:44.000Z",
+	"html": "Hi there\n",
+	"attachments": []
 }
 ```
 
@@ -113,23 +113,27 @@ Wrangler can also simulate sending emails locally. Consider this example Email W
 
 ```ts
 import { EmailMessage } from "cloudflare:email";
-import { createMimeMessage } from 'mimetext';
+import { createMimeMessage } from "mimetext";
 
 export default {
 	async fetch(request, env, ctx) {
 		const msg = createMimeMessage();
-		msg.setSender({ name: 'Sending email test', addr: 'sender@example.com' });
-		msg.setRecipient('recipient@example.com');
-		msg.setSubject('An email generated in a worker');
+		msg.setSender({ name: "Sending email test", addr: "sender@example.com" });
+		msg.setRecipient("recipient@example.com");
+		msg.setSubject("An email generated in a worker");
 		msg.addMessage({
-			contentType: 'text/plain',
+			contentType: "text/plain",
 			data: `Congratulations, you just sent an email from a worker.`,
 		});
 
-		var message = new EmailMessage('sender@example.com', 'recipient@example.com', msg.asRaw());
+		var message = new EmailMessage(
+			"sender@example.com",
+			"recipient@example.com",
+			msg.asRaw(),
+		);
 		await env.EMAIL.send(message);
 		return Response.json({ ok: true });
-	}
+	},
 };
 ```
 
@@ -163,9 +167,9 @@ Congratulations, you just sent an email from a worker.
 Likewise, [`EmailMessage`](/email-routing/email-workers/runtime-api/#emailmessage-definition)'s `forward()` and `reply()` methods are also simulated locally. Consider this Worker that receives an email, parses it, replies to the sender, and forwards the original message to one your verified recipient addresses:
 
 ```ts
-import * as PostalMime from 'postal-mime';
-import { createMimeMessage } from 'mimetext';
-import { EmailMessage } from 'cloudflare:email';
+import * as PostalMime from "postal-mime";
+import { createMimeMessage } from "mimetext";
+import { EmailMessage } from "cloudflare:email";
 
 export default {
 	async email(message, env: any, ctx: any) {
@@ -179,16 +183,23 @@ export default {
 
 		// creates reply message
 		const msg = createMimeMessage();
-		msg.setSender({ name: 'Thank you for your contact', addr: 'sender@example.com' });
+		msg.setSender({
+			name: "Thank you for your contact",
+			addr: "sender@example.com",
+		});
 		msg.setRecipient(message.from);
-		msg.setHeader('In-Reply-To', message.headers.get('Message-ID'));
-		msg.setSubject('An email generated in a worker');
+		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+		msg.setSubject("An email generated in a worker");
 		msg.addMessage({
-			contentType: 'text/plain',
+			contentType: "text/plain",
 			data: `This is an automated reply. We received you email with the subject "${email.subject}", and will handle it as soon as possible.`,
 		});
 
-		const replyMessage = new EmailMessage('sender@example.com', message.from, msg.asRaw());
+		const replyMessage = new EmailMessage(
+			"sender@example.com",
+			message.from,
+			msg.asRaw(),
+		);
 
 		await message.reply(replyMessage);
 		await message.forward("recipient@example.com");
@@ -205,4 +216,4 @@ Run `npx wrangler dev` and use curl to `POST` the same message from the [Receive
   /var/folders/33/pn86qymd0w50htvsjp93rys40000gn/T/miniflare-381a79d7efa4e991607b30a079f6b17d/files/email/a1db7ebb-ccb4-45ef-b315-df49c6d820c0.eml
 [wrangler:inf] Email handler forwarded message with
   rcptTo: recipient@example.com
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
index abe2ab9e1917b97..9b1bca4d651c33d 100644
--- a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
+++ b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
@@ -17,37 +17,39 @@ import { EmailMessage } from "cloudflare:email";
 import { createMimeMessage } from "mimetext";
 
 export default {
-  async email(message, env, ctx) {
-
-    const ticket = createTicket(message);
-
-    const msg = createMimeMessage();
-    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
-    msg.setRecipient(message.from);
-    msg.setSubject("Email Routing Auto-reply");
-    msg.addMessage({
-      contentType: 'text/plain',
-      data: `We got your message, your ticket number is ${ ticket.id }`
-    });
-
-    const replyMessage = new EmailMessage(
-      "<SENDER>@example.com",
-      message.from,
-      msg.asRaw()
-    );
-
-    await message.reply(replyMessage);
-  }
-}
+	async email(message, env, ctx) {
+		const ticket = createTicket(message);
+
+		const msg = createMimeMessage();
+		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+		msg.setSender({
+			name: "Thank you for your contact",
+			addr: "<SENDER>@example.com",
+		});
+		msg.setRecipient(message.from);
+		msg.setSubject("Email Routing Auto-reply");
+		msg.addMessage({
+			contentType: "text/plain",
+			data: `We got your message, your ticket number is ${ticket.id}`,
+		});
+
+		const replyMessage = new EmailMessage(
+			"<SENDER>@example.com",
+			message.from,
+			msg.asRaw(),
+		);
+
+		await message.reply(replyMessage);
+	},
+};
 ```
 
 To mitigate security risks and abuse, replying to incoming emails has a few requirements and limits:
 
-* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
-* The email can only be replied to once in the same `EmailMessage` event.
-* The recipient in the reply must match the incoming sender.
-* The outgoing sender domain must match the same domain that received the email.
-* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
+- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
+- The email can only be replied to once in the same `EmailMessage` event.
+- The recipient in the reply must match the incoming sender.
+- The outgoing sender domain must match the same domain that received the email.
+- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
 
-If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
\ No newline at end of file
+If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
diff --git a/src/content/docs/email-routing/get-started/audit-logs.mdx b/src/content/docs/email-routing/get-started/audit-logs.mdx
index ea56a04e458c21b..ecd9b2792350842 100644
--- a/src/content/docs/email-routing/get-started/audit-logs.mdx
+++ b/src/content/docs/email-routing/get-started/audit-logs.mdx
@@ -13,9 +13,9 @@ products:
 
 Audit logs for Email Routing are available in the [Cloudflare dashboard](https://dash.cloudflare.com/?account=audit-log). The following changes to Email Routing will be displayed:
 
-* Add/edit Rule
-* Add address
-* Address change status
-* Enable/disable/unlock zone
+- Add/edit Rule
+- Add address
+- Address change status
+- Enable/disable/unlock zone
 
 Refer to [Review audit logs](/fundamentals/account/account-security/review-audit-logs/) for more information.
diff --git a/src/content/docs/email-routing/get-started/index.mdx b/src/content/docs/email-routing/get-started/index.mdx
index 79651ecf8525c75..4f3a50117f3555f 100644
--- a/src/content/docs/email-routing/get-started/index.mdx
+++ b/src/content/docs/email-routing/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 To enable Email Routing, start by creating a custom email address linked to a destination address or Email Worker. This forms an **email rule**. You can enable or disable rules from the Cloudflare dashboard. Refer to [Enable Email Routing](/email-routing/get-started/enable-email-routing) for more details.
 
diff --git a/src/content/docs/email-routing/graphql-example.mdx b/src/content/docs/email-routing/graphql-example.mdx
index 1026c732af09d68..01e88cb7c926f54 100644
--- a/src/content/docs/email-routing/graphql-example.mdx
+++ b/src/content/docs/email-routing/graphql-example.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 10
 products:
   - email-routing
----
\ No newline at end of file
+---
diff --git a/src/content/docs/email-routing/limits.mdx b/src/content/docs/email-routing/limits.mdx
index aa0c9137f7e93b4..7ba2a9378e24cab 100644
--- a/src/content/docs/email-routing/limits.mdx
+++ b/src/content/docs/email-routing/limits.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Email Workers size limits
 
diff --git a/src/content/docs/email-routing/postmaster.mdx b/src/content/docs/email-routing/postmaster.mdx
index f2e0afee4304d44..5024a5fca40679d 100644
--- a/src/content/docs/email-routing/postmaster.mdx
+++ b/src/content/docs/email-routing/postmaster.mdx
@@ -223,7 +223,6 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
-
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
@@ -236,4 +235,4 @@ Email Routing does not support sending or replying from your Cloudflare domain.
 
 ### "`.`" is treated as a normal character for custom addresses
 
-The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
\ No newline at end of file
+The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
diff --git a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
index 5b19f941bc3973c..d5a45e53b881844 100644
--- a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
+++ b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
@@ -17,8 +17,8 @@ You can check the status of your DNS records in the **Settings** section of Emai
 
 Check the status of your account's DNS records in the **Email DNS records** card:
 
-* **Email DNS records configured** - DNS records are properly configured.
-* **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
+- **Email DNS records configured** - DNS records are properly configured.
+- **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
 
 ### Start disabling
 
@@ -36,8 +36,8 @@ Select **View DNS records** for a list of the required `MX` and sender policy fr
 
 If you are having trouble with your account's DNS records, refer to the [Troubleshooting](/email-routing/troubleshooting/) section.
 
-## _dc-mx DNS responses
+## \_dc-mx DNS responses
 
 If you see a DNS response with a `_dc-mx` prefix (for example, `_dc-mx.a1b2c3d4e5f6.example.com`), Cloudflare inserted it automatically. This response appears when your `MX` record points to a hostname that is [proxied](/dns/proxy-status/) through Cloudflare. The `_dc-mx` target itself resolves directly to your origin IP address so that mail traffic bypasses the proxy and reaches your mail server.
 
-For more information, refer to [_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
+For more information, refer to [\_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
diff --git a/src/content/docs/email-routing/setup/index.mdx b/src/content/docs/email-routing/setup/index.mdx
index 9e8e6168e7d9d3d..a985b31913d2240 100644
--- a/src/content/docs/email-routing/setup/index.mdx
+++ b/src/content/docs/email-routing/setup/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-routing/troubleshooting/index.mdx b/src/content/docs/email-routing/troubleshooting/index.mdx
index 6049ae5a1dbf1b6..320a435287a9f78 100644
--- a/src/content/docs/email-routing/troubleshooting/index.mdx
+++ b/src/content/docs/email-routing/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Email Routing warns you when your DNS records are not properly configured. In Email Routing's **Overview** page, you will see a message explaining what type of problem your account's DNS records have.
 
diff --git a/src/content/docs/email-security/account-setup/index.mdx b/src/content/docs/email-security/account-setup/index.mdx
index 58b9191302f4924..115b19e40df6b41 100644
--- a/src/content/docs/email-security/account-setup/index.mdx
+++ b/src/content/docs/email-security/account-setup/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
index 1a386467767d7a5..74464f58cb9a20e 100644
--- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
+++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 1. Log in to the [Google Cloud Console](https://console.cloud.google.com/welcome/new). From the dashboard, select **CREATE OR SELECT PROJECT**.
 2. Provide the details for the new project, and select **CREATE** to start your new project.
@@ -19,4 +19,4 @@ import { Render } from "~/components"
 
 ## Next steps
 
-Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
\ No newline at end of file
+Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
diff --git a/src/content/docs/email-security/deployment/inline/reference/index.mdx b/src/content/docs/email-security/deployment/inline/reference/index.mdx
index 3acddcd2503e68e..d967052afafa9a8 100644
--- a/src/content/docs/email-security/deployment/inline/reference/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/inline/setup/index.mdx b/src/content/docs/email-security/deployment/inline/setup/index.mdx
index 9d77a311b1def17..7944841692ccc8f 100644
--- a/src/content/docs/email-security/deployment/inline/setup/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/setup/index.mdx
@@ -11,7 +11,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For help getting started with an [inline setup](/email-security/deployment/inline/), refer to the following guides:
 
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
index b36be50d7f74394..1d64d9275d3103e 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
@@ -15,11 +15,11 @@ Alert Webhooks allow you to connect external services to Email security, includi
 - Slack
 - Email addresses
 - <GlossaryTooltip
-  	term="SIEM"
-  	link="/email-security/reporting/siem-integration/"
-  >
-  	SIEM
-  </GlossaryTooltip>
+    	term="SIEM"
+    	link="/email-security/reporting/siem-integration/"
+    >
+    	SIEM
+    </GlossaryTooltip>
 - Microsoft Teams
 
 ## Create an alert webhook
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
index 064f16bbe246605..bcf17ca94340495 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/email-policies/index.mdx b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
index 970060f35bca548..f02050d417bebf4 100644
--- a/src/content/docs/email-security/email-configuration/email-policies/index.mdx
+++ b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 <Render file="contact-support" product="email-security" />
 
diff --git a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
index cf276be7c979d2c..57eafdbc713f614 100644
--- a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
+++ b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/lists/index.mdx b/src/content/docs/email-security/email-configuration/lists/index.mdx
index fb788ae5a7833ef..309b6ba3c5e4a88 100644
--- a/src/content/docs/email-security/email-configuration/lists/index.mdx
+++ b/src/content/docs/email-security/email-configuration/lists/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx
index 0f8848970f558ed..1f577dece7e60c7 100644
--- a/src/content/docs/email-security/migrate-to-email-security.mdx
+++ b/src/content/docs/email-security/migrate-to-email-security.mdx
@@ -45,15 +45,15 @@ To invite users in Zero Trust Email security:
 
 Once you have added new account members, you will have to assign each member an [Email security role](/cloudflare-one/roles-permissions/#email-security-roles).
 
-| Area 1              | Email security                                                            | Description                                                                                                                                                                                             |
-| ------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Area 1              | Email security                                                            | Description                                                                                                                                                                                                                  |
+| ------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | N/A                 | Cloudflare Zero Trust                                                     | Can edit Cloudflare [Zero Trust](/cloudflare-one/). Has administrator access to all Zero Trust products including Access, Gateway, the Cloudflare One Client, Tunnel, Browser Isolation, CASB, DLP, DEX, and Email security. |
-| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                 |
-| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                 |
-| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                          |
-| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                        |
-| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                               |
-| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                              |
+| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                                      |
+| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                                      |
+| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                                               |
+| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                                             |
+| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                                                    |
+| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                                                   |
 
 ## Create webhooks
 
@@ -142,12 +142,12 @@ This table displays the difference in terminology used when creating policies:
 
 This table displays the difference in terminology used when finding emails whose disposition is incorrect:
 
-| Area 1                                                                                                                                                                                   | Email security                                                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| Area 1                                                                                                                                                                                   | Email security                                                                                       |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | Report [false negative](/email-security/email-configuration/phish-submissions/#false-negatives)/[false positive](/email-security/email-configuration/phish-submissions/#false-positives) | [Submit messages for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) |
-| N/A                                                                                                                                                                                      | Escalate user submissions                                                                |
-| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)         |
-| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)         |
+| N/A                                                                                                                                                                                      | Escalate user submissions                                                                            |
+| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)                     |
+| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)                     |
 
 ## Business Email Compromise
 
diff --git a/src/content/docs/email-security/reference/index.mdx b/src/content/docs/email-security/reference/index.mdx
index 9f7509bd9cf9280..c38a16a0de9f080 100644
--- a/src/content/docs/email-security/reference/index.mdx
+++ b/src/content/docs/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-service/api/index.mdx b/src/content/docs/email-service/api/index.mdx
index 44e78505396a107..d03187150053624 100644
--- a/src/content/docs/email-service/api/index.mdx
+++ b/src/content/docs/email-service/api/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/api/route-emails/email-handler.mdx b/src/content/docs/email-service/api/route-emails/email-handler.mdx
index a5e96e60aafc443..4de6233a27266e7 100644
--- a/src/content/docs/email-service/api/route-emails/email-handler.mdx
+++ b/src/content/docs/email-service/api/route-emails/email-handler.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 products:
   - email-service
-  - workers 
+  - workers
 ---
 
 import { Tabs, TabItem } from "~/components";
diff --git a/src/content/docs/email-service/api/route-emails/index.mdx b/src/content/docs/email-service/api/route-emails/index.mdx
index 5d7f8f3f10cb0db..1d26611cdc87d0d 100644
--- a/src/content/docs/email-service/api/route-emails/index.mdx
+++ b/src/content/docs/email-service/api/route-emails/index.mdx
@@ -14,4 +14,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/api/send-emails/rest-api.mdx b/src/content/docs/email-service/api/send-emails/rest-api.mdx
index 7435885f3824271..91cbd43aa37da94 100644
--- a/src/content/docs/email-service/api/send-emails/rest-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/rest-api.mdx
@@ -135,14 +135,14 @@ A successful response returns the delivery status for each recipient:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "delivered": ["recipient@example.com"],
-    "permanent_bounces": [],
-    "queued": []
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"delivered": ["recipient@example.com"],
+		"permanent_bounces": [],
+		"queued": []
+	}
 }
 ```
 
@@ -156,29 +156,29 @@ The REST API returns standard Cloudflare API error responses. A failed request r
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 10001,
-      "message": "email.sending.error.invalid_request_schema"
-    }
-  ],
-  "messages": [],
-  "result": null
+	"success": false,
+	"errors": [
+		{
+			"code": 10001,
+			"message": "email.sending.error.invalid_request_schema"
+		}
+	],
+	"messages": [],
+	"result": null
 }
 ```
 
 Common REST API error codes:
 
-| HTTP Status | Code | Message | Description |
-| ----------- | ---- | ------- | ----------- |
-| 400 | 10001 | `email.sending.error.invalid_request_schema` | Invalid request format |
-| 400 | 10200 | `email.sending.error.email.invalid` | Invalid email content |
-| 400 | 10201 | `email.sending.error.email.no_content_length` | Missing content length |
-| 400 | 10202 | `email.sending.error.email.too_big` | Email exceeds size limit |
-| 403 | 10203 | `email.sending.error.email.sending_disabled` | Sending disabled for this zone/account |
-| 429 | 10004 | `email.sending.error.throttled` | Rate limit exceeded |
-| 500 | 10002 | `email.sending.error.internal_server` | Internal server error |
+| HTTP Status | Code  | Message                                       | Description                            |
+| ----------- | ----- | --------------------------------------------- | -------------------------------------- |
+| 400         | 10001 | `email.sending.error.invalid_request_schema`  | Invalid request format                 |
+| 400         | 10200 | `email.sending.error.email.invalid`           | Invalid email content                  |
+| 400         | 10201 | `email.sending.error.email.no_content_length` | Missing content length                 |
+| 400         | 10202 | `email.sending.error.email.too_big`           | Email exceeds size limit               |
+| 403         | 10203 | `email.sending.error.email.sending_disabled`  | Sending disabled for this zone/account |
+| 429         | 10004 | `email.sending.error.throttled`               | Rate limit exceeded                    |
+| 500         | 10002 | `email.sending.error.internal_server`         | Internal server error                  |
 
 :::note[Workers binding vs REST API errors]
 The REST API returns standard Cloudflare API numeric error codes, while the [Workers binding](/email-service/api/send-emails/workers-api/) throws errors with string codes (for example, `E_SENDER_NOT_VERIFIED`). Refer to the [Workers API error codes table](/email-service/api/send-emails/workers-api/#error-codes) for the string error codes.
diff --git a/src/content/docs/email-service/api/send-emails/workers-api.mdx b/src/content/docs/email-service/api/send-emails/workers-api.mdx
index 83244ea4c0e7dbb..ad7de8aa161ea02 100644
--- a/src/content/docs/email-service/api/send-emails/workers-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/workers-api.mdx
@@ -235,27 +235,27 @@ export default {
 
 The following error codes may be returned when sending emails:
 
-| Error Code                      | Description                             | Common Causes                                                 |
-| ------------------------------- | --------------------------------------- | ------------------------------------------------------------- |
-| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data |
-| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                     |
-| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                           |
-| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                     |
-| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`      |
-| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam     |
-| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                         |
-| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                        |
-| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection             |
-| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                    |
-| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                   |
-| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                         |
+| Error Code                      | Description                             | Common Causes                                                                              |
+| ------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------ |
+| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data                              |
+| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                                                  |
+| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                                                        |
+| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                                                  |
+| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`                                   |
+| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam                                  |
+| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                                                      |
+| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                                                     |
+| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection                                          |
+| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                                                 |
+| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                                                |
+| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                                                      |
 | `E_HEADER_NOT_ALLOWED`          | Header not allowed                      | Header is platform-controlled or not on the [whitelist](/email-service/reference/headers/) |
-| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field    |
-| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                   |
-| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                |
-| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                  |
-| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                       |
-| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers               |
+| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field                                 |
+| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                                                |
+| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                                             |
+| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                                               |
+| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                                                    |
+| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers                                            |
 
 ## Legacy `EmailMessage` API
 
diff --git a/src/content/docs/email-service/concepts/index.mdx b/src/content/docs/email-service/concepts/index.mdx
index 6dacc309b767a1c..20dd8baf3869d18 100644
--- a/src/content/docs/email-service/concepts/index.mdx
+++ b/src/content/docs/email-service/concepts/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/configuration/index.mdx b/src/content/docs/email-service/configuration/index.mdx
index d7381d7a1565017..d8ae4416f025c07 100644
--- a/src/content/docs/email-service/configuration/index.mdx
+++ b/src/content/docs/email-service/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
index be8214fb629d3e3..7b743963157b998 100644
--- a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
+++ b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
@@ -44,138 +44,145 @@ id = "your-kv-namespace-id"
 ## Hard bounce detection
 
 ```javascript
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
-  async email(message, env, ctx) {
-    // Parse the raw email message
-    const parser = new PostalMime.default();
-    const rawEmail = new Response(message.raw);
-    const email = await parser.parse(await rawEmail.arrayBuffer());
-
-    // Check if this is a bounce notification
-    if (isBounceNotification(email)) {
-      const bounceInfo = await parseBounceInfo(email);
-
-      if (bounceInfo.type === 'hard') {
-        await handleHardBounce(bounceInfo, env);
-        console.log(`Hard bounce processed for: ${bounceInfo.originalRecipient}`);
-        return;
-      }
-    }
-
-    // Forward non-bounce emails normally
-    await message.forward('admin@yourdomain.com');
-  },
+	async email(message, env, ctx) {
+		// Parse the raw email message
+		const parser = new PostalMime.default();
+		const rawEmail = new Response(message.raw);
+		const email = await parser.parse(await rawEmail.arrayBuffer());
+
+		// Check if this is a bounce notification
+		if (isBounceNotification(email)) {
+			const bounceInfo = await parseBounceInfo(email);
+
+			if (bounceInfo.type === "hard") {
+				await handleHardBounce(bounceInfo, env);
+				console.log(
+					`Hard bounce processed for: ${bounceInfo.originalRecipient}`,
+				);
+				return;
+			}
+		}
+
+		// Forward non-bounce emails normally
+		await message.forward("admin@yourdomain.com");
+	},
 };
 
 function isBounceNotification(email) {
-  // Check common bounce indicators
-  const subject = email.subject?.toLowerCase() || '';
-  const fromAddress = email.from?.address?.toLowerCase() || '';
-
-  // Common bounce indicators
-  const bounceSubjects = [
-    'mail delivery failed',
-    'undelivered mail returned to sender',
-    'delivery status notification',
-    'returned mail',
-    'mail system error'
-  ];
-
-  const bounceFromPatterns = [
-    'mailer-daemon',
-    'mail-daemon',
-    'postmaster',
-    'noreply',
-    'bounce'
-  ];
-
-  return bounceSubjects.some(phrase => subject.includes(phrase)) ||
-         bounceFromPatterns.some(pattern => fromAddress.includes(pattern));
+	// Check common bounce indicators
+	const subject = email.subject?.toLowerCase() || "";
+	const fromAddress = email.from?.address?.toLowerCase() || "";
+
+	// Common bounce indicators
+	const bounceSubjects = [
+		"mail delivery failed",
+		"undelivered mail returned to sender",
+		"delivery status notification",
+		"returned mail",
+		"mail system error",
+	];
+
+	const bounceFromPatterns = [
+		"mailer-daemon",
+		"mail-daemon",
+		"postmaster",
+		"noreply",
+		"bounce",
+	];
+
+	return (
+		bounceSubjects.some((phrase) => subject.includes(phrase)) ||
+		bounceFromPatterns.some((pattern) => fromAddress.includes(pattern))
+	);
 }
 
 async function parseBounceInfo(email) {
-  const text = email.text || '';
-  const html = email.html || '';
-  const content = text + ' ' + html;
-
-  // Extract original recipient email
-  const recipientMatch = content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
-                        content.match(/([^\s<]+@[^\s>]+)/);
-
-  const originalRecipient = recipientMatch ? recipientMatch[1] : null;
-
-  // Determine bounce type based on content
-  const hardBounceIndicators = [
-    'user unknown',
-    'no such user',
-    'invalid recipient',
-    'recipient address rejected',
-    'mailbox unavailable',
-    'domain not found',
-    '5.1.1', // SMTP error code for bad destination mailbox
-    '5.1.2', // SMTP error code for bad destination system
-    '5.4.1', // SMTP error code for no answer from host
-  ];
-
-  const isHardBounce = hardBounceIndicators.some(indicator =>
-    content.toLowerCase().includes(indicator.toLowerCase())
-  );
-
-  return {
-    type: isHardBounce ? 'hard' : 'soft',
-    originalRecipient,
-    reason: extractBounceReason(content),
-    timestamp: new Date().toISOString()
-  };
+	const text = email.text || "";
+	const html = email.html || "";
+	const content = text + " " + html;
+
+	// Extract original recipient email
+	const recipientMatch =
+		content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
+		content.match(/([^\s<]+@[^\s>]+)/);
+
+	const originalRecipient = recipientMatch ? recipientMatch[1] : null;
+
+	// Determine bounce type based on content
+	const hardBounceIndicators = [
+		"user unknown",
+		"no such user",
+		"invalid recipient",
+		"recipient address rejected",
+		"mailbox unavailable",
+		"domain not found",
+		"5.1.1", // SMTP error code for bad destination mailbox
+		"5.1.2", // SMTP error code for bad destination system
+		"5.4.1", // SMTP error code for no answer from host
+	];
+
+	const isHardBounce = hardBounceIndicators.some((indicator) =>
+		content.toLowerCase().includes(indicator.toLowerCase()),
+	);
+
+	return {
+		type: isHardBounce ? "hard" : "soft",
+		originalRecipient,
+		reason: extractBounceReason(content),
+		timestamp: new Date().toISOString(),
+	};
 }
 
 function extractBounceReason(content) {
-  // Extract the specific error message
-  const reasonPatterns = [
-    /diagnostic[- ]code:\s*(.+)/i,
-    /reason:\s*(.+)/i,
-    /error:\s*(.+)/i,
-    /(5\.\d+\.\d+[^.\n]*)/i
-  ];
-
-  for (const pattern of reasonPatterns) {
-    const match = content.match(pattern);
-    if (match) {
-      return match[1].trim().split('\n')[0]; // Take first line only
-    }
-  }
-
-  return 'Unknown bounce reason';
+	// Extract the specific error message
+	const reasonPatterns = [
+		/diagnostic[- ]code:\s*(.+)/i,
+		/reason:\s*(.+)/i,
+		/error:\s*(.+)/i,
+		/(5\.\d+\.\d+[^.\n]*)/i,
+	];
+
+	for (const pattern of reasonPatterns) {
+		const match = content.match(pattern);
+		if (match) {
+			return match[1].trim().split("\n")[0]; // Take first line only
+		}
+	}
+
+	return "Unknown bounce reason";
 }
 
 async function handleHardBounce(bounceInfo, env) {
-  if (!bounceInfo.originalRecipient) {
-    console.log('Could not extract original recipient from bounce');
-    return;
-  }
-
-  // Add to suppression list in KV
-  await env.SUPPRESSION_LIST.put(
-    bounceInfo.originalRecipient,
-    JSON.stringify({
-      type: 'hard_bounce',
-      reason: bounceInfo.reason,
-      timestamp: bounceInfo.timestamp,
-      status: 'suppressed'
-    }),
-    {
-      metadata: {
-        bounceType: 'hard',
-        addedDate: bounceInfo.timestamp
-      }
-    }
-  );
-
-  console.log(`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`);
+	if (!bounceInfo.originalRecipient) {
+		console.log("Could not extract original recipient from bounce");
+		return;
+	}
+
+	// Add to suppression list in KV
+	await env.SUPPRESSION_LIST.put(
+		bounceInfo.originalRecipient,
+		JSON.stringify({
+			type: "hard_bounce",
+			reason: bounceInfo.reason,
+			timestamp: bounceInfo.timestamp,
+			status: "suppressed",
+		}),
+		{
+			metadata: {
+				bounceType: "hard",
+				addedDate: bounceInfo.timestamp,
+			},
+		},
+	);
+
+	console.log(
+		`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`,
+	);
 }
-````
+```
 
 ## Testing hard bounce handling
 
diff --git a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
index a7a6a6f31405fa0..4f7199cce0ef4f7 100644
--- a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
+++ b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
@@ -40,7 +40,7 @@ class SimpleSpamFilter implements SpamFilter {
 		"winner",
 		"congratulations",
 		"inheritance",
-		"lottery"
+		"lottery",
 	];
 
 	private trustedDomains = ["company.com", "trusted-partner.com", "vendor.net"];
@@ -83,7 +83,10 @@ class SimpleSpamFilter implements SpamFilter {
 		}
 
 		// Check for suspicious sender patterns
-		if (sender.includes("noreply") && subject.toLowerCase().includes("urgent")) {
+		if (
+			sender.includes("noreply") &&
+			subject.toLowerCase().includes("urgent")
+		) {
 			score += 2;
 			reasons.push("Suspicious noreply + urgent combination");
 		}
@@ -101,31 +104,33 @@ const spamFilter = new SimpleSpamFilter();
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const startTime = Date.now();
-		
+
 		// Check for spam
 		const spamCheck = await spamFilter.checkSpam(message);
 
 		// Track spam check metrics
 		env.EMAIL_ANALYTICS?.writeDataPoint({
 			blobs: [
-				'spam_check_completed',
+				"spam_check_completed",
 				message.from,
 				message.to,
-				spamCheck.isSpam ? 'spam' : 'legitimate'
+				spamCheck.isSpam ? "spam" : "legitimate",
 			],
 			doubles: [
 				1, // Count
 				spamCheck.score,
-				Date.now() - startTime
+				Date.now() - startTime,
 			],
 			indexes: [
 				`spam_detected:${spamCheck.isSpam}`,
-				`score_range:${getScoreRange(spamCheck.score)}`
-			]
+				`score_range:${getScoreRange(spamCheck.score)}`,
+			],
 		});
 
 		if (spamCheck.isSpam) {
-			console.log(`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`);
+			console.log(
+				`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`,
+			);
 			message.setReject(`Message rejected: ${spamCheck.reasons[0]}`);
 			return;
 		}
@@ -141,13 +146,13 @@ export default {
 };
 
 function getScoreRange(score: number): string {
-	if (score < 0) return 'trusted';
-	if (score === 0) return 'neutral';
-	if (score === 1) return 'suspicious';
-	return 'spam';
+	if (score < 0) return "trusted";
+	if (score === 0) return "neutral";
+	if (score === 1) return "suspicious";
+	return "spam";
 }
 ```
 
 ## Advanced spam detection with AI
 
-For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
\ No newline at end of file
+For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
diff --git a/src/content/docs/email-service/get-started/send-emails.mdx b/src/content/docs/email-service/get-started/send-emails.mdx
index 14f5fccbd0ab3f5..cb5765ac4807d02 100644
--- a/src/content/docs/email-service/get-started/send-emails.mdx
+++ b/src/content/docs/email-service/get-started/send-emails.mdx
@@ -54,14 +54,14 @@ A successful response includes the delivery status for each recipient:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "delivered": ["recipient@example.com"],
-    "permanent_bounces": [],
-    "queued": []
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"delivered": ["recipient@example.com"],
+		"permanent_bounces": [],
+		"queued": []
+	}
 }
 ```
 
@@ -84,14 +84,14 @@ If you are building on Cloudflare Workers, you can use the Workers binding for n
 2.  Add the email binding to your Wrangler configuration file:
 
     <WranglerConfig>
-
-    ```toml
-    [[send_email]]
-    name = "EMAIL"
-    remote = true
-    ```
-
-    </WranglerConfig>
+    
+        ```toml
+        [[send_email]]
+        name = "EMAIL"
+        remote = true
+        ```
+    
+        </WranglerConfig>
 
 3.  Create your Worker code in `src/index.ts`:
 
@@ -147,4 +147,4 @@ Now that you can send emails, explore advanced features:
 
 - **[Route incoming emails](/email-service/get-started/route-emails/)** - Process emails sent to your domain
 - **[API reference](/email-service/api/send-emails/)** - Complete API documentation
-- **[Examples](/email-service/examples/)** - Real-world implementation patterns
\ No newline at end of file
+- **[Examples](/email-service/examples/)** - Real-world implementation patterns
diff --git a/src/content/docs/email-service/local-development/index.mdx b/src/content/docs/email-service/local-development/index.mdx
index 9b9df2443a3e182..90f0be957d8c338 100644
--- a/src/content/docs/email-service/local-development/index.mdx
+++ b/src/content/docs/email-service/local-development/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Test and develop your email applications locally using Wrangler before deploying to production.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/local-development/routing.mdx b/src/content/docs/email-service/local-development/routing.mdx
index caf0d02137925c7..50adb9e89ffd9e6 100644
--- a/src/content/docs/email-service/local-development/routing.mdx
+++ b/src/content/docs/email-service/local-development/routing.mdx
@@ -35,30 +35,30 @@ name = "EMAIL"
 ## Basic routing worker
 
 ```javascript
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
-  async email(message, env, ctx) {
-    // Parse the raw email message
-    const parser = new PostalMime.default();
-    const rawEmail = new Response(message.raw);
-    const email = await parser.parse(await rawEmail.arrayBuffer());
-
-    console.log('Received email:', {
-      from: message.from,
-      to: message.to,
-      subject: email.subject,
-      text: email.text,
-      html: email.html
-    });
-
-    // Route based on recipient
-    if (message.to.includes('support@')) {
-      await message.forward('support-team@company.com');
-    } else {
-      await message.forward('general@company.com');
-    }
-  },
+	async email(message, env, ctx) {
+		// Parse the raw email message
+		const parser = new PostalMime.default();
+		const rawEmail = new Response(message.raw);
+		const email = await parser.parse(await rawEmail.arrayBuffer());
+
+		console.log("Received email:", {
+			from: message.from,
+			to: message.to,
+			subject: email.subject,
+			text: email.text,
+			html: email.html,
+		});
+
+		// Route based on recipient
+		if (message.to.includes("support@")) {
+			await message.forward("support-team@company.com");
+		} else {
+			await message.forward("general@company.com");
+		}
+	},
 };
 ```
 
diff --git a/src/content/docs/email-service/platform/index.mdx b/src/content/docs/email-service/platform/index.mdx
index 56789154dfe88e9..c4e599e6b17ffc9 100644
--- a/src/content/docs/email-service/platform/index.mdx
+++ b/src/content/docs/email-service/platform/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/platform/pricing.mdx b/src/content/docs/email-service/platform/pricing.mdx
index 914f0b2cf37e5a8..4dfa8f6a7c2c0c2 100644
--- a/src/content/docs/email-service/platform/pricing.mdx
+++ b/src/content/docs/email-service/platform/pricing.mdx
@@ -14,9 +14,9 @@ Cloudflare Email Service pricing is based on your Cloudflare plan and email usag
 
 Email Routing is available on both the Workers Free and Workers Paid plans. Email Sending is only available on the Workers Paid plan.
 
-|                                                         | Workers Free     | Workers Paid     |
-| ------------------------------------------------------- | ---------------- | ---------------- |
-| **Outbound emails (Email Sending)**                     | Not available    | 3,000 included per month, then $0.35 per 1,000 emails |
-| **Inbound emails (Email Routing)**                      | Unlimited        | Unlimited        |
+|                                     | Workers Free  | Workers Paid                                          |
+| ----------------------------------- | ------------- | ----------------------------------------------------- |
+| **Outbound emails (Email Sending)** | Not available | 3,000 included per month, then $0.35 per 1,000 emails |
+| **Inbound emails (Email Routing)**  | Unlimited     | Unlimited                                             |
 
 Email Routing Workers is billed according to [Workers pricing](/workers/platform/pricing/).
diff --git a/src/content/docs/email-service/reference/index.mdx b/src/content/docs/email-service/reference/index.mdx
index fb104b8db015bee..667dce89f146995 100644
--- a/src/content/docs/email-service/reference/index.mdx
+++ b/src/content/docs/email-service/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
     hideIndex: true
 products:
   - email-service
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/reference/postmaster.mdx b/src/content/docs/email-service/reference/postmaster.mdx
index e5f357aa33574bd..329745da9935650 100644
--- a/src/content/docs/email-service/reference/postmaster.mdx
+++ b/src/content/docs/email-service/reference/postmaster.mdx
@@ -164,7 +164,6 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
-
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
diff --git a/src/content/docs/firewall/api/cf-filters/delete.mdx b/src/content/docs/firewall/api/cf-filters/delete.mdx
index b6c9144e5c5757d..3d3ea8b45311d7f 100644
--- a/src/content/docs/firewall/api/cf-filters/delete.mdx
+++ b/src/content/docs/firewall/api/cf-filters/delete.mdx
@@ -24,17 +24,17 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>"
-    },
-    {
-      "id": "<FILTER_ID_2>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID_1>"
+		},
+		{
+			"id": "<FILTER_ID_2>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -51,13 +51,13 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/get.mdx b/src/content/docs/firewall/api/cf-filters/get.mdx
index c4c4d34c089e8f4..f60ae9c7c41a342 100644
--- a/src/content/docs/firewall/api/cf-filters/get.mdx
+++ b/src/content/docs/firewall/api/cf-filters/get.mdx
@@ -23,47 +23,47 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>",
-      "paused": false,
-      "description": "Login from office",
-      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "Login",
-      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_3>",
-      "paused": false,
-      "description": "not /api",
-      "expression": "not http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_4>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_5>",
-      "paused": false,
-      "expression": "ip.src eq 93.184.216.0"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result_info": {
-    "page": 1,
-    "per_page": 25,
-    "count": 5,
-    "total_count": 5,
-    "total_pages": 1
-  }
+	"result": [
+		{
+			"id": "<FILTER_ID_1>",
+			"paused": false,
+			"description": "Login from office",
+			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "Login",
+			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_3>",
+			"paused": false,
+			"description": "not /api",
+			"expression": "not http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_4>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_5>",
+			"paused": false,
+			"expression": "ip.src eq 93.184.216.0"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result_info": {
+		"page": 1,
+		"per_page": 25,
+		"count": 5,
+		"total_count": 5,
+		"total_pages": 1
+	}
 }
 ```
 
@@ -79,14 +79,14 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters/{filter_id}"
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<FILTER_ID>",
-    "paused": false,
-    "description": "Login from office",
-    "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<FILTER_ID>",
+		"paused": false,
+		"description": "Login from office",
+		"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/post.mdx b/src/content/docs/firewall/api/cf-filters/post.mdx
index ec20a4e1f410ada..966cc67d408dcfc 100644
--- a/src/content/docs/firewall/api/cf-filters/post.mdx
+++ b/src/content/docs/firewall/api/cf-filters/post.mdx
@@ -43,39 +43,39 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>",
-      "paused": false,
-      "expression": "ip.src eq 93.184.216.0"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_3>",
-      "paused": false,
-      "description": "not /api",
-      "expression": "not http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_4>",
-      "paused": false,
-      "description": "Login",
-      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_5>",
-      "paused": false,
-      "description": "Login from office",
-      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID_1>",
+			"paused": false,
+			"expression": "ip.src eq 93.184.216.0"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_3>",
+			"paused": false,
+			"description": "not /api",
+			"expression": "not http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_4>",
+			"paused": false,
+			"description": "Login",
+			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_5>",
+			"paused": false,
+			"description": "Login from office",
+			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/put.mdx b/src/content/docs/firewall/api/cf-filters/put.mdx
index 4a08764ea671787..a0412eac414fc43 100644
--- a/src/content/docs/firewall/api/cf-filters/put.mdx
+++ b/src/content/docs/firewall/api/cf-filters/put.mdx
@@ -38,23 +38,23 @@ curl --request PUT \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID>",
-      "paused": false,
-      "description": "IP of example.org",
-      "expression": "ip.src eq 93.184.216.0"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID>",
+			"paused": false,
+			"description": "IP of example.org",
+			"expression": "ip.src eq 93.184.216.0"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -78,14 +78,14 @@ curl --request PUT \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<FILTER_ID>",
-    "paused": false,
-    "description": "Login from office",
-    "expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<FILTER_ID>",
+		"paused": false,
+		"description": "Login from office",
+		"expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/validation.mdx b/src/content/docs/firewall/api/cf-filters/validation.mdx
index 42402810e50cc29..191219397a1902a 100644
--- a/src/content/docs/firewall/api/cf-filters/validation.mdx
+++ b/src/content/docs/firewall/api/cf-filters/validation.mdx
@@ -10,8 +10,6 @@ description: Validate firewall rule expressions via the API.
 
 The Cloudflare Filters API supports an endpoint for validating expressions.
 
-
-
 ## Examples
 
 ### Validate expression via query string
@@ -24,14 +22,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr?expression=ip.s
 
 ```json title="Response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
-    }
-  ],
-  "messages": null
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
+		}
+	],
+	"messages": null
 }
 ```
 
@@ -57,14 +55,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr" \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
-    }
-  ],
-  "messages": null
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
+		}
+	],
+	"messages": null
 }
 ```
 
diff --git a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
index 493daca2fecd16a..c396807b1630fa8 100644
--- a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
+++ b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
@@ -24,9 +24,9 @@ A filter object typically looks like the following:
 
 ```json
 {
-  "id": "<FILTER_ID>",
-  "expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
-  "description": "WordPress login paths via the login page or mobile RPC endpoint"
+	"id": "<FILTER_ID>",
+	"expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
+	"description": "WordPress login paths via the login page or mobile RPC endpoint"
 }
 ```
 
@@ -38,8 +38,8 @@ The expression specified in this example filter is:
 
 This filter expression has a `(this or that) and not this` structure designed to:
 
-* Capture two WordPress paths that may be subject to brute force password attacks, and
-* Exclude traffic that comes from the IP address `93.184.216.34`.
+- Capture two WordPress paths that may be subject to brute force password attacks, and
+- Exclude traffic that comes from the IP address `93.184.216.34`.
 
 Imagine that this is an IP for your office. This expression demonstrates a filter that might be used (in a firewall rule) to block access to the WordPress login when accessed outside the office network.
 
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
index fa662e947375338..75c661f0deb8cc4 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
@@ -23,70 +23,70 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID_1>",
-      "paused": false,
-      "description": "allow API traffic without challenge",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_1>",
-        "expression": "http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "/api"
-      }
-    },
-    {
-      "id": "<RULE_ID_2>",
-      "paused": false,
-      "description": "do not challenge login from office",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_2>",
-        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login from office"
-      }
-    },
-    {
-      "id": "<RULE_ID_3>",
-      "paused": false,
-      "description": "challenge login",
-      "action": "challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_3>",
-        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login"
-      }
-    },
-    {
-      "id": "<RULE_ID_4>",
-      "paused": false,
-      "description": "Non-interactive challenge site",
-      "action": "js_challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_4>",
-        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "not /api"
-      }
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result_info": {
-    "page": 1,
-    "per_page": 25,
-    "count": 4,
-    "total_count": 4,
-    "total_pages": 1
-  }
+	"result": [
+		{
+			"id": "<RULE_ID_1>",
+			"paused": false,
+			"description": "allow API traffic without challenge",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_1>",
+				"expression": "http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "/api"
+			}
+		},
+		{
+			"id": "<RULE_ID_2>",
+			"paused": false,
+			"description": "do not challenge login from office",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_2>",
+				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login from office"
+			}
+		},
+		{
+			"id": "<RULE_ID_3>",
+			"paused": false,
+			"description": "challenge login",
+			"action": "challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_3>",
+				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login"
+			}
+		},
+		{
+			"id": "<RULE_ID_4>",
+			"paused": false,
+			"description": "Non-interactive challenge site",
+			"action": "js_challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_4>",
+				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "not /api"
+			}
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result_info": {
+		"page": 1,
+		"per_page": 25,
+		"count": 4,
+		"total_count": 4,
+		"total_pages": 1
+	}
 }
 ```
 
@@ -102,21 +102,21 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules/{rule_
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "paused": false,
-    "description": "do not challenge login from office",
-    "action": "allow",
-    "priority": null,
-    "filter": {
-      "id": "<FILTER_ID>",
-      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-      "paused": false,
-      "description": "Login from office"
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"paused": false,
+		"description": "do not challenge login from office",
+		"action": "allow",
+		"priority": null,
+		"filter": {
+			"id": "<FILTER_ID>",
+			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+			"paused": false,
+			"description": "Login from office"
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
index b3ec7601d83b43b..3c5f3df30b5c373 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
@@ -15,10 +15,8 @@ This example creates several firewall rules using a single API call.
 
 :::note
 
-
 To create a firewall rule you need a [filter](/firewall/api/cf-filters/what-is-a-filter/) identifier (`id`). If you have not created a filter yet, refer to the [Cloudflare Filters API documentation](/firewall/api/cf-filters/).
 
-
 :::
 
 ```bash title="Request"
@@ -60,62 +58,62 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID_1>",
-      "paused": false,
-      "description": "Do not challenge login from office",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_1>",
-        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login from office"
-      }
-    },
-    {
-      "id": "<RULE_ID_2>",
-      "paused": false,
-      "description": "Challenge login",
-      "action": "challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_2>",
-        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login"
-      }
-    },
-    {
-      "id": "<RULE_ID_3>",
-      "paused": false,
-      "description": "Non-interactive challenge site",
-      "action": "js_challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_3>",
-        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "not /api"
-      }
-    },
-    {
-      "id": "<RULE_ID_4>",
-      "paused": false,
-      "description": "Allow API traffic without challenge",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_4>",
-        "expression": "http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "/api"
-      }
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<RULE_ID_1>",
+			"paused": false,
+			"description": "Do not challenge login from office",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_1>",
+				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login from office"
+			}
+		},
+		{
+			"id": "<RULE_ID_2>",
+			"paused": false,
+			"description": "Challenge login",
+			"action": "challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_2>",
+				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login"
+			}
+		},
+		{
+			"id": "<RULE_ID_3>",
+			"paused": false,
+			"description": "Non-interactive challenge site",
+			"action": "js_challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_3>",
+				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "not /api"
+			}
+		},
+		{
+			"id": "<RULE_ID_4>",
+			"paused": false,
+			"description": "Allow API traffic without challenge",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_4>",
+				"expression": "http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "/api"
+			}
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
index 0d5982f433847fe..3136c338ab132ce 100644
--- a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
+++ b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
@@ -73,7 +73,6 @@ While your priority numbering scheme can be arbitrary, keep the following in min
 - **Rules without a priority number are evaluated last**, in order of their action precedence. For example, a rule with the _Log_ action is evaluated before a rule that has the _Block_ action. For more on action precedence, refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/).
 - **Avoid using the number `1` as a priority** to make rule order modification easier in the future.
 - **Consider grouping ranges of priority numbers into categories** that have some meaning for your deployment. Here are some examples:
-
   - 5000-9999: Trusted IP addresses
   - 10000-19999: Blocking rules for bad crawlers
   - 20000-29999: Blocking rules for abusive users/spam
diff --git a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
index 94c7ab99e5aa858..1fb0715951d644a 100644
--- a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
+++ b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
@@ -21,7 +21,7 @@ To enable editing access by your Account Team:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page. (You must be logged in as a **Super Administrator**).
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Editing Permission**, switch the toggle to **On**.
 3. Select a duration.
@@ -29,8 +29,6 @@ To enable editing access by your Account Team:
 
 :::note
 
-
 In an emergency, Cloudflare Support can override your **Editing Permissions** and make updates to your account, but your Super Administrator will receive an email and the action will be recorded in your [Audit Logs](/fundamentals/account/account-security/review-audit-logs/) with an **Action** of **Break glass**.
 
-
 :::
diff --git a/src/content/docs/fundamentals/account/account-security/index.mdx b/src/content/docs/fundamentals/account/account-security/index.mdx
index 62434c63a9879ee..774bf0f5dba2826 100644
--- a/src/content/docs/fundamentals/account/account-security/index.mdx
+++ b/src/content/docs/fundamentals/account/account-security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
index 44b877f610b9365..3f045d04d65881c 100644
--- a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
+++ b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
@@ -14,12 +14,10 @@ Refer to the [blog post](https://blog.cloudflare.com/helping-keep-customers-safe
 
 :::note[Note]
 
-
 Cloudflare does not have additional information about the specific breach or Internet service that potentially lost your password.
 
 Popular online tools such as [Have I Been Pwned](https://haveibeenpwned.com/) can help you better understand where your external accounts were attacked. If you reused this password in other systems, it is recommended that you reset it in those as well.
 
-
 :::
 
 If your password is found in a data breach, we will email you information on how to reset your password and prompt you to do so in the Cloudflare dashboard.
diff --git a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
index bacbe900335ef0a..be25f61733a7a37 100644
--- a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
+++ b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
@@ -18,7 +18,7 @@ To view the active sessions associated with your email address:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 
diff --git a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
index 9e379c53fec4c81..f93945373a085e6 100644
--- a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
+++ b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 Zone holds prevent other teams in your organization from adding zones that are already active in another account.
 
@@ -24,7 +24,7 @@ Zone holds are enabled by default for all Enterprise zones.
 
 When you enable a zone hold, no one else can [add your zone](/fundamentals/manage-domains/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
 
-*The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed.*
+_The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed._
 
 To enable a zone hold:
 
diff --git a/src/content/docs/fundamentals/account/create-account.mdx b/src/content/docs/fundamentals/account/create-account.mdx
index cc509b79ec43b6f..e93d05d94fd8d52 100644
--- a/src/content/docs/fundamentals/account/create-account.mdx
+++ b/src/content/docs/fundamentals/account/create-account.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components"
+import { DashButton, Render } from "~/components";
 
 To create a Cloudflare account:
 
@@ -29,7 +29,7 @@ To change your account name:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page.
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Account Name**, select **Change Name**.
 3. Enter a new account name.
@@ -37,13 +37,13 @@ To change your account name:
 
 ## Best practices
 
-<Render file="create-account-best-practices" product="fundamentals" /> 
+<Render file="create-account-best-practices" product="fundamentals" />
 
-Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain. 
+Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain.
 
 Once you [set up an account](/fundamentals/account/), you have several ways to interact with Cloudflare.
 
-## Interact with Cloudflare 
+## Interact with Cloudflare
 
 If you prefer working without code, you can manage your account and domain settings through the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
@@ -62,4 +62,3 @@ For those who prefer to interact with Cloudflare programmatically, you can use s
 | [cloudflare-go](https://github.com/cloudflare/cloudflare-go)                           | [README](https://github.com/cloudflare/cloudflare-go#readme)         | The official Go library for the Cloudflare API.                                |
 | [cloudflare-typescript](https://github.com/cloudflare/cloudflare-typescript)           | [README](https://github.com/cloudflare/cloudflare-typescript#readme) | The official TypeScript library for the Cloudflare API.                        |
 | [cloudflare-python](https://github.com/cloudflare/cloudflare-python)                   | [README](https://github.com/cloudflare/cloudflare-python#readme)     | The official Python library for the Cloudflare API.                            |
-
diff --git a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
index d942475ab7e6765..535d145aa95d13f 100644
--- a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
+++ b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
@@ -16,10 +16,10 @@ Once you [set up a new account](/fundamentals/account/) and [add your domain](/f
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button at the end of the account row.
-![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
+   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
 
 3. Select **Copy account ID**.
 
@@ -29,17 +29,17 @@ To copy the account ID when you only have one account:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and locate your account.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button next to your account name.
 3. From the list that appears, select **Copy account ID**.
-![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
+   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
 
 ## Copy your Zone ID
 
 1. In the Cloudflare dashboard, go to the **Account** home and locate your account.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. From the **Overview** page for your account, locate the **API** section towards the bottom of the page.
 
@@ -53,7 +53,7 @@ You can also find your account ID from the **Workers & Pages** section of your a
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-    <DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. The **Account details** section contains your **Account ID**.
 3. To copy the Account ID, select **Click to copy**.
diff --git a/src/content/docs/fundamentals/account/index.mdx b/src/content/docs/fundamentals/account/index.mdx
index 78335a849e9c2ba..ed12e22c5045241 100644
--- a/src/content/docs/fundamentals/account/index.mdx
+++ b/src/content/docs/fundamentals/account/index.mdx
@@ -10,7 +10,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 If you need help setting up a new Cloudflare account, refer to the following resources:
 
diff --git a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
index 90ef1f2f6f50643..692fcea9aa69c90 100644
--- a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
+++ b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
@@ -21,7 +21,7 @@ To restrict the API access for the entire account:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Locate the **Enable API Access** section and then update the setting.
 
@@ -29,16 +29,14 @@ To restrict the API access for the entire account:
 
 :::note
 
-
 Member-level settings will override the account-level setting. If a specific member has API access enabled whereas the account has the access disabled, that member can still call APIs related to the Enterprise account.
 
-
 :::
 
 To restrict the API access for a specific member:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Click on the member to expand and choose the intended **API Access**. If `Account Default`, then it follows the account level setting.
diff --git a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
index f58ab298b5d15c4..8f1f58e538d2e66 100644
--- a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
+++ b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
@@ -114,24 +114,20 @@ To fetch all available permission groups and their IDs, use the [List permission
 
 ```json output
 {
-  "result": [
-    {
-      "id": "19637fbb73d242c0a92845d8db0b95b1",
-      "name": "AI Crawl Control Read",
-      "description": "Grants access to reading AI Crawl Control",
-      "scopes": [
-        "com.cloudflare.api.account.zone"
-      ]
-    },
-    {
-      "id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
-      "name": "AI Crawl Control Write",
-      "description": "Grants access to reading and editing AI Crawl Control",
-      "scopes": [
-        "com.cloudflare.api.account.zone"
-      ]
-    },
-    // (...)
+	"result": [
+		{
+			"id": "19637fbb73d242c0a92845d8db0b95b1",
+			"name": "AI Crawl Control Read",
+			"description": "Grants access to reading AI Crawl Control",
+			"scopes": ["com.cloudflare.api.account.zone"]
+		},
+		{
+			"id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
+			"name": "AI Crawl Control Write",
+			"description": "Grants access to reading and editing AI Crawl Control",
+			"scopes": ["com.cloudflare.api.account.zone"]
+		}
+		// (...)
 	]
 }
 ```
diff --git a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
index d084a748cb05a70..487d294ea4ff9cf 100644
--- a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
+++ b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
@@ -11,8 +11,8 @@ products:
 
 API tokens can be restricted at runtime in two ways:
 
-* [Client IP address range filtering](#client-ip-address-range-filtering)
-* [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
+- [Client IP address range filtering](#client-ip-address-range-filtering)
+- [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
 
 ## Client IP address range filtering
 
@@ -26,17 +26,14 @@ Client IP address range filtering is not applied to the [Verify Token](https://d
 
 :::
 
-
 ## Time to live (TTL) constraints
 
 By default, tokens do not expire and are long lived. Defining a TTL sets when a token starts being valid and when a token is no longer valid. This is often referred to as `notBefore` and `notAfter`. Setting these timestamps limits the lifetime of the token to the defined period. Not setting the start date or `notBefore` means the token is active as soon as it is created. Not setting the end date or `notAfter` means the token does not expire.
 
 :::note
 
-
 Dates selected are defined as 00:00 UTC of that day. For finer grained time selection, use the [API](/fundamentals/api/).
 
-
 :::
 
 ![Time to Live selection calendar](~/assets/images/fundamentals/api/ttl.png)
diff --git a/src/content/docs/fundamentals/api/index.mdx b/src/content/docs/fundamentals/api/index.mdx
index fc2b5ca4dd7c1ca..5c920d17b99595e 100644
--- a/src/content/docs/fundamentals/api/index.mdx
+++ b/src/content/docs/fundamentals/api/index.mdx
@@ -11,7 +11,7 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use the following resources to learn more about Cloudflare's REST API:
 
diff --git a/src/content/docs/fundamentals/api/reference/index.mdx b/src/content/docs/fundamentals/api/reference/index.mdx
index 2b69ab6e04041ec..51171664a4e68eb 100644
--- a/src/content/docs/fundamentals/api/reference/index.mdx
+++ b/src/content/docs/fundamentals/api/reference/index.mdx
@@ -11,6 +11,6 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/api/reference/limits.mdx b/src/content/docs/fundamentals/api/reference/limits.mdx
index 056310a63a2cf5e..af4f24a26742004 100644
--- a/src/content/docs/fundamentals/api/reference/limits.mdx
+++ b/src/content/docs/fundamentals/api/reference/limits.mdx
@@ -11,7 +11,11 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="api-rate-limits" product="fundamentals"  params={{showHeading: true}} />
+<Render
+	file="api-rate-limits"
+	product="fundamentals"
+	params={{ showHeading: true }}
+/>
 
 ## Rate limiting headers
 
diff --git a/src/content/docs/fundamentals/api/troubleshooting.mdx b/src/content/docs/fundamentals/api/troubleshooting.mdx
index f1b15f7ee9bdbf6..442eb608d3525d0 100644
--- a/src/content/docs/fundamentals/api/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/api/troubleshooting.mdx
@@ -23,15 +23,15 @@ curl "https://api.cloudflare.com/client/v4/user/tokens/verify" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "f267e341f3dd4697bd3b9f71dd96247f",
-    "status": "active",
-    "not_before": "2018-07-01T05:20:00Z",
-    "expires_on": "2020-01-01T00:00:00Z"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "f267e341f3dd4697bd3b9f71dd96247f",
+		"status": "active",
+		"not_before": "2018-07-01T05:20:00Z",
+		"expires_on": "2020-01-01T00:00:00Z"
+	}
 }
 ```
 
diff --git a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
index fc8a96817900340..7bb8ee6aba29a4d 100644
--- a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
+++ b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
@@ -8,11 +8,15 @@ products:
   - fundamentals
 ---
 
-import { Stream, GlossaryTooltip } from "~/components"
+import { Stream, GlossaryTooltip } from "~/components";
 
 To optimize your website or web application, Cloudflare provides [DNS](https://www.cloudflare.com/learning/dns/what-is-dns/) and [CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) services, so we can [reverse proxy](https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/) the web traffic to and from your domain.
 
-<Stream id="980c8494f2403b95473d2ed687b4f402" title="How Cloudflare DNS works for your domain" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public" />
+<Stream
+	id="980c8494f2403b95473d2ed687b4f402"
+	title="How Cloudflare DNS works for your domain"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public"
+/>
 
 ## DNS explained
 
diff --git a/src/content/docs/fundamentals/concepts/index.mdx b/src/content/docs/fundamentals/concepts/index.mdx
index 6a64b49f7e2d8a3..52496a8fd9b8022 100644
--- a/src/content/docs/fundamentals/concepts/index.mdx
+++ b/src/content/docs/fundamentals/concepts/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
index 31af11a5ba634c1..ffb08d179a6080f 100644
--- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
+++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
@@ -10,7 +10,7 @@ products:
 
 Internet traffic is made up of people, services, and agents requesting online resources from wherever they are hosted. Your resources may be publicly available, like a website or application that anyone on the Internet can access. Or your resources may be privately available, like an internal app or network that only your employees and partners should be able to access.
 
-Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.  
+Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.
 
 For example, you may not always want the direct traffic because it can come from malicious sources, like hackers, or in the form of [DDoS attacks](https://www.cloudflare.com/learning/ddos/ddos-attack-tools/how-to-ddos/). Additionally, depending on the location where the request originated, you want to ensure the traffic is [routed through the most efficient and fastest path](/argo-smart-routing/).
 
@@ -36,18 +36,18 @@ One example of on-ramping traffic to Cloudflare is updating your public website
 
 However, maybe you need to protect a private application that is not directly available on the Internet. In this scenario, you can:
 
-* Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
-* For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
+- Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
+- For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
 
 With these options, any request from a user device can access internal private applications via the secure private tunnels.
 
 Refer to the list below for products you can use to on-ramp traffic to Cloudflare.
 
-* [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
-* [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
-* [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
-* [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
-* The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
+- [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
+- [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
+- [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
+- [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
+- The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
 
 ### Off-ramp traffic from Cloudflare
 
@@ -61,6 +61,6 @@ You can also utilize [caching](/cache/) to help with performance. Instead of off
 
 Refer to the list below for products you can use to off-ramp traffic from Cloudflare.
 
-* [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
-* [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
-* [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
\ No newline at end of file
+- [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
+- [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
+- [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
diff --git a/src/content/docs/fundamentals/index.mdx b/src/content/docs/fundamentals/index.mdx
index 4fbceb5e645cec0..6da0f6862aab3d2 100644
--- a/src/content/docs/fundamentals/index.mdx
+++ b/src/content/docs/fundamentals/index.mdx
@@ -24,6 +24,6 @@ Refer to the list below for additional Cloudflare resources.
 - [Cloudflare blog](https://blog.cloudflare.com)
 - [Cloudflare's Go library](https://github.com/cloudflare/cloudflare-go)
 - [Cloudflare system status](https://www.cloudflarestatus.com/)
-- [Cloudflare Radar](https://radar.cloudflare.com) 
-- [Cloudflare TV](https://cloudflare.tv/schedule) 
+- [Cloudflare Radar](https://radar.cloudflare.com)
+- [Cloudflare TV](https://cloudflare.tv/schedule)
 - [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
diff --git a/src/content/docs/fundamentals/manage-domains/add-site.mdx b/src/content/docs/fundamentals/manage-domains/add-site.mdx
index 081c4aeb68c902e..e089a041cbe43bc 100644
--- a/src/content/docs/fundamentals/manage-domains/add-site.mdx
+++ b/src/content/docs/fundamentals/manage-domains/add-site.mdx
@@ -7,7 +7,13 @@ products:
   - fundamentals
 ---
 
-import { DashButton, GlossaryTooltip, Render, Stream, Details } from "~/components";
+import {
+	DashButton,
+	GlossaryTooltip,
+	Render,
+	Stream,
+	Details,
+} from "~/components";
 
 After you onboard your domain, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
 
@@ -77,6 +83,7 @@ If you encounter unexpected results when changing your nameservers, refer to the
 ## Further options
 
 ### Other DNS setups
+
 - To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/).
 - To use one or more DNS providers, refer to [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
 - Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
@@ -89,4 +96,4 @@ If you encounter unexpected results when changing your nameservers, refer to the
 
 [^2]: Enterprise customers can onboard these using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
 
-[^3]: A security feature that protects DNS records from spoofing
\ No newline at end of file
+[^3]: A security feature that protects DNS records from spoofing
diff --git a/src/content/docs/fundamentals/manage-domains/domain-version.mdx b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
index 124534a2bf1c4e0..80c3dfce25a53ae 100644
--- a/src/content/docs/fundamentals/manage-domains/domain-version.mdx
+++ b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
@@ -8,28 +8,25 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 [Version Management](/version-management/) is available for Enterprise customers and allows you to safely test, deploy, and roll back changes to your zone configurations.
 
-
 ## Enable versioning
 
-
 <Render file="enable-versioning" product="version-management" />
 
-
 ## (Optional) Create additional environments
 
 <Render file="enable-default-creation" product="version-management" />
 
 These environments each serve a specific purpose and are accessed differently: <Render file="environment-defaults" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" /> <br/>
+<Render file="create-environment-situation" product="version-management" />
+<br />
 
 For more details, refer to [Create environment](/version-management/how-to/environments/#create-environment).
 
-
 ## Update configurations
 
 <Render file="edit-version" product="version-management" />
@@ -40,7 +37,6 @@ For more details, refer to [Create environment](/version-management/how-to/envir
 
 ## Promote version
 
-
 Next, [promote](/version-management/how-to/environments/#change-environment-version) your version through your different environments.
 
 <Render file="promote-version" product="version-management" />
@@ -50,5 +46,3 @@ After promoting to each environment, test the new version in your new environmen
 ## Repeat
 
 For new changes to your zone, [create a new version](/version-management/how-to/versions/#create-version) and repeat this process.
-
-
diff --git a/src/content/docs/fundamentals/manage-domains/move-domain.mdx b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
index adb048fe514eab7..554db841218b10c 100644
--- a/src/content/docs/fundamentals/manage-domains/move-domain.mdx
+++ b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
@@ -30,13 +30,11 @@ To transfer a domain from one Cloudflare account to another, you will need:
 
 :::caution
 
-
 Before transferring an active Cloudflare domain to another Cloudflare account, you must remove any [DNSSEC configurations](/dns/dnssec/) and [add-ons or subscriptions](/billing/manage/cancel-subscription/).
 
 We also recommend [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records of your zone while it is in the previous account. Then, you can [import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the correct DNS records into the new account.
 If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
-
 :::
 
 If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](#issue-new-certificates) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
diff --git a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
index 1ac459d5abe6896..8887da35f668294 100644
--- a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
+++ b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
@@ -12,7 +12,7 @@ To troubleshoot your site, you can pause Cloudflare globally. This will send tra
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and domain.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Within **Overview**, choose **Advanced Actions** > **Pause Cloudflare on Site**.
 
@@ -22,7 +22,7 @@ The process of pausing Cloudflare takes five minutes or less. This approach is p
 Disabling a zone does not impact Spectrum applications.
 :::
 
-***
+---
 
 ## Alternatives to global pause
 
diff --git a/src/content/docs/fundamentals/manage-members/index.mdx b/src/content/docs/fundamentals/manage-members/index.mdx
index 854f89c1e4e7eca..349b6e8ec38dafd 100644
--- a/src/content/docs/fundamentals/manage-members/index.mdx
+++ b/src/content/docs/fundamentals/manage-members/index.mdx
@@ -12,7 +12,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 On any Cloudflare account, you can collaborate by adding members to your account and assigning them access via one or several policies.
 
diff --git a/src/content/docs/fundamentals/manage-members/policies.mdx b/src/content/docs/fundamentals/manage-members/policies.mdx
index 6ca9aafa9521ce1..36f550450d46ae3 100644
--- a/src/content/docs/fundamentals/manage-members/policies.mdx
+++ b/src/content/docs/fundamentals/manage-members/policies.mdx
@@ -27,8 +27,8 @@ For example, you may want to assign multiple policies and use scopes to control
 
 A set of standard API endpoints is present on every account that allow access to your members, which has recently been enhanced by a list of `resourceGroups` and `PermissionGroups`.
 
-* A `resourceGroup` is a unique identifier for the scope for which a policy applies.
-* A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
+- A `resourceGroup` is a unique identifier for the scope for which a policy applies.
+- A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
 
 Refer to the [API documentation](/api/) for more information.
 
@@ -44,4 +44,3 @@ To understand a member’s full access, check both the **Members** and **User Gr
 
 Cloudflare is actively working on improvements to consolidate this view in a future update.
 :::
-
diff --git a/src/content/docs/fundamentals/manage-members/roles.mdx b/src/content/docs/fundamentals/manage-members/roles.mdx
index c7a01704fb29721..e6e4019dccc01f9 100644
--- a/src/content/docs/fundamentals/manage-members/roles.mdx
+++ b/src/content/docs/fundamentals/manage-members/roles.mdx
@@ -28,7 +28,7 @@ Account-scoped roles apply across an entire Cloudflare account, and through all
 | Application Security Reports Read                            | Can read Application Security Reports.                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audit Logs Viewer                                            | Can view [Audit Logs](/fundamentals/account/account-security/review-audit-logs/).                                                                                                                                                                                                                                                                                                                                                 |
 | Bot Management (Account-Wide)                                | Can edit [Bot Management](/bots/plans/bm-subscription/) (including [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/)) configurations for all domains in account.                                                                                                                                                                                                                                                    |
-| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                                      |
+| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                          |
 | Cache Purge                                                  | Can purge the edge cache and allows the reading of zone settings.                                                                                                                                                                                                                                                                                                                                                                 |
 | Cloudflare Access                                            | Can edit [Cloudflare Access](/cloudflare-one/access-controls/policies/) and [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).                                                                                                                                                                                                                                                                          |
 | Cloudflare CASB                                              | Can edit [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/fundamentals/manage-members/scope.mdx b/src/content/docs/fundamentals/manage-members/scope.mdx
index ecfacf62744dfa0..e75d47dafac71c1 100644
--- a/src/content/docs/fundamentals/manage-members/scope.mdx
+++ b/src/content/docs/fundamentals/manage-members/scope.mdx
@@ -19,7 +19,7 @@ To allow for flexible combinations of access to users, Cloudflare currently has
 - **Domain groups:** Use when you have related domains that share the same access needs, for example, all production domains.
 - **Specific resources:** Use when access should be limited to individual resources.
 
-***
+---
 
 ## Choose the scope of roles
 
@@ -33,15 +33,13 @@ If you want the member to have a policy that applies across your account, use th
 
 | Field    | Value         |
 | -------- | ------------- |
-| Operator | *Include*     |
-| Type     | *All domains* |
+| Operator | _Include_     |
+| Type     | _All domains_ |
 
 :::note
 
-
 You can only assign [account-scoped roles](/fundamentals/manage-members/roles/#account-scoped-roles) as part of these types of policies
 
-
 :::
 
 ### Specific domains
@@ -50,9 +48,9 @@ If you want the member to have a policy that applies to a specific domain, use t
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | *Include*           |
-| Type     | *A specific domain* |
-| Name     | *A specific domain* |
+| Operator | _Include_           |
+| Type     | _A specific domain_ |
+| Name     | _A specific domain_ |
 
 ### Domain groups
 
@@ -64,11 +62,10 @@ To create a domain group:
 
 1. In the Cloudflare dashboard, go to the **Settings** > **Lists** page. (You must be logged in as a **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/)).
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Domain Group Manager**, select **Create**.
 3. Create your domain group:
-
    1. Select the domains to include.
    2. Add a **Name**.
    3. Select **Create**.
@@ -81,43 +78,40 @@ To assign a member permissions to a domain group, use the following combination
 
 | Field    | Value           |
 | -------- | --------------- |
-| Operator | *Include*       |
-| Type     | *Domain Group*  |
-| Name     | *Example Group* |
+| Operator | _Include_       |
+| Type     | _Domain Group_  |
+| Name     | _Example Group_ |
 
 :::note
 
-
 With Domain Groups, you can only assign [domain-scoped roles](/fundamentals/manage-members/roles/#domain-scoped-roles) to these members.
 
-
 :::
 
-
 ### Specific resources
 
 If you want the member to have a policy that applies to a specific resource, use the following combination of fields.
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | *Include*           |
-| Type     | *Granular* |
-| Product  | *Product Name* |
-| Resource  | *Specific Resource* |
+| Operator | _Include_           |
+| Type     | _Granular_          |
+| Product  | _Product Name_      |
+| Resource | _Specific Resource_ |
 
 #### Available scopes
 
 You can assign the following resource-specific scopes to members:
 
-| Scope                                     | Description                                                                                                                                              |
-| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Individual Access applications               | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                                   |
-| Individual Access identity providers (IdPs)  | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                                    |
-| Individual Access policies                   | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                            |
-| Individual Access service tokens             | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                           |
-| Individual Access infrastructure targets     | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/).        |
-| Individual Cloudflare Tunnel instances       | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                                |
-| Individual Cloudflare Mesh nodes             | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                          |
+| Scope                                       | Description                                                                                                                                       |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Individual Access applications              | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                            |
+| Individual Access identity providers (IdPs) | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                     |
+| Individual Access policies                  | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                     |
+| Individual Access service tokens            | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                    |
+| Individual Access infrastructure targets    | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/). |
+| Individual Cloudflare Tunnel instances      | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                         |
+| Individual Cloudflare Mesh nodes            | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                   |
 
 :::note
 When using scopes for specific resources, you can only assign [resource-scoped roles](/fundamentals/manage-members/roles/#resource-scoped-roles) to these members.
diff --git a/src/content/docs/fundamentals/manage-members/user-groups.mdx b/src/content/docs/fundamentals/manage-members/user-groups.mdx
index 6ac8ab7b5b960bc..ac0ff7d261fe721 100644
--- a/src/content/docs/fundamentals/manage-members/user-groups.mdx
+++ b/src/content/docs/fundamentals/manage-members/user-groups.mdx
@@ -10,9 +10,9 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Tabs, TabItem } from '~/components';
+import { DashButton, Tabs, TabItem } from "~/components";
 
-User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of. 
+User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of.
 
 :::note
 User Group permissions are inherited by each member of the group but are not currently reflected in the role field on the **Members** page. To view a member’s full set of permissions, check both:
@@ -23,21 +23,21 @@ User Group permissions are inherited by each member of the group but are not cur
 Cloudflare is actively working on improving this experience to make inherited and direct permissions easier to view.
 :::
 
-## Create a User Group manually 
+## Create a User Group manually
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Select the **Groups** tab.
 3. Select **Create a Group** and enter a name and description for your new group.
 4. Select **Create group** to confirm your changes. The **Group members** tab displays.
-5. Select **Add members**. 
+5. Select **Add members**.
 6. Select the relevant members you want to include in the group and select **Add to Group**.
 
 ### Assign a Permission Policy
 
-With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group. 
+With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -86,24 +86,23 @@ PAYLOAD
 
 ## Create a User Group with SCIM
 
-Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account. 
-
+Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account.
 
 :::note
 If you use the [Cloudflare dashboard SCIM integration](/fundamentals/account/account-security/scim-setup/), you can sync Groups from an upstream Identity Provider. This allows you to centralize user and group management at your identity provider.
 
 Note that when managing User Groups via SCIM:
-- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API. 
+
+- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API.
 - The integration requires one external SCIM application per Cloudflare account.
 - Cloudflare does not currently support updating user profile fields (`firstName`, `lastName`, or `email`) via SCIM. If those attributes change in your IdP, they will not be updated in Cloudflare. These values are only set during initial provisioning.
-:::
-
+  :::
 
 To set up a user group with SCIM, refer to the [Provisioning with SCIM guide](/fundamentals/account/account-security/scim-setup/).
 
 ### Set up permissions for User Groups
 
-After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it. 
+After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/docs/fundamentals/new-features/index.mdx b/src/content/docs/fundamentals/new-features/index.mdx
index 8f052702ba7fe7e..00ba70c15225ddb 100644
--- a/src/content/docs/fundamentals/new-features/index.mdx
+++ b/src/content/docs/fundamentals/new-features/index.mdx
@@ -10,8 +10,8 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare offers several RSS feeds to help you consume content programmatically.
 
-<DirectoryListing/>
+<DirectoryListing />
diff --git a/src/content/docs/fundamentals/organizations/limitations.mdx b/src/content/docs/fundamentals/organizations/limitations.mdx
index 732b548986c8775..037c78efb4df0b2 100644
--- a/src/content/docs/fundamentals/organizations/limitations.mdx
+++ b/src/content/docs/fundamentals/organizations/limitations.mdx
@@ -14,7 +14,7 @@ The following limitations apply during the public beta.
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Organization creation   | You must be a Super Administrator of an Enterprise account to create an Organization.                                                                                                       |
 | Adding accounts         | Once you've created an Organization, accounts of any plan type can be added. You must have Super Administrator access to the account, and it cannot already belong to another Organization. |
-| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                                |
+| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                              |
 | Roles                   | Organization Super Administrator is the only role available during the beta. Additional roles will be available in a future release.                                                        |
-| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                       |
+| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                                              |
 | Account removal         | Self-service account removal is not yet available. To remove an account from your Organization, contact [Cloudflare Support](/support/contacting-cloudflare-support/).                      |
diff --git a/src/content/docs/fundamentals/organizations/setup.mdx b/src/content/docs/fundamentals/organizations/setup.mdx
index 3cb26686125e379..cb9c27ffabafa59 100644
--- a/src/content/docs/fundamentals/organizations/setup.mdx
+++ b/src/content/docs/fundamentals/organizations/setup.mdx
@@ -101,11 +101,11 @@ You can manage Organizations using the [Cloudflare Terraform provider](https://r
 
 You may encounter the following errors during the setup flow. Please see below for more information on how to resolve these.
 
-| Error | Description |
-| --- | --- |
-| Organization management is only available on the Enterprise plan at this time. | You are not a member of any Enterprise accounts. |
-| You need a super admin role on an enterprise account to create an Organization. | You are not a Super Administrator of an Enterprise account. |
-| One or more of your enterprise accounts is already part of an Organization. | You may not create another organization because your accounts are already in an organization. |
-| You have reached the maximum number of organizations. | You may not create another organization because you already have one. |
-| An Organization has already been created for accounts associated with your company. Please contact your company administrator. | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
-| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it.| This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data. |
+| Error                                                                                                                                                | Description                                                                                                                                                                                                              |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Organization management is only available on the Enterprise plan at this time.                                                                       | You are not a member of any Enterprise accounts.                                                                                                                                                                         |
+| You need a super admin role on an enterprise account to create an Organization.                                                                      | You are not a Super Administrator of an Enterprise account.                                                                                                                                                              |
+| One or more of your enterprise accounts is already part of an Organization.                                                                          | You may not create another organization because your accounts are already in an organization.                                                                                                                            |
+| You have reached the maximum number of organizations.                                                                                                | You may not create another organization because you already have one.                                                                                                                                                    |
+| An Organization has already been created for accounts associated with your company. Please contact your company administrator.                       | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
+| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it. | This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data.                  |
diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx
index 297c524991656ee..aa834449efa4ed4 100644
--- a/src/content/docs/fundamentals/performance/improve-seo.mdx
+++ b/src/content/docs/fundamentals/performance/improve-seo.mdx
@@ -12,10 +12,8 @@ In practice, SEO is primarily about quality content, user experience, and not ma
 
 :::note[Tip:]
 
-
 For general guidelines around SEO, refer to [Google's recommendations](https://developers.google.com/search/docs/advanced/guidelines/overview).
 
-
 :::
 
 ## SEO improvements with Cloudflare
@@ -47,9 +45,9 @@ Depending on your domain's security settings, you might accidentally block searc
 
 If you notice SEO issues, make sure your:
 
-* [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
-* [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
-* [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
+- [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
+- [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
+- [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
 
 If you still notice issues with search engine crawlers, refer to our [Troubleshooting guide](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/).
 
@@ -57,7 +55,7 @@ If you still notice issues with search engine crawlers, refer to our [Troublesho
 
 The following characteristics do not affect your domain's SEO:
 
-* **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
-* **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
-* **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
-* **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
+- **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
+- **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
+- **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
+- **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
diff --git a/src/content/docs/fundamentals/performance/index.mdx b/src/content/docs/fundamentals/performance/index.mdx
index 4fa36b844e2eec8..8c00c87f68d593b 100644
--- a/src/content/docs/fundamentals/performance/index.mdx
+++ b/src/content/docs/fundamentals/performance/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/performance/test-speed.mdx b/src/content/docs/fundamentals/performance/test-speed.mdx
index 12ea8823571be55..246a968ab7ae1c4 100644
--- a/src/content/docs/fundamentals/performance/test-speed.mdx
+++ b/src/content/docs/fundamentals/performance/test-speed.mdx
@@ -8,7 +8,7 @@ products:
 
 Cloudflare offers several tools to test the speed of your website, as well as the speed of your Internet connection.
 
-***
+---
 
 ## Test website speed
 
@@ -24,11 +24,11 @@ If you experience any issues, make sure you are not blocking specific [user agen
 
 If your domain is not yet active on Cloudflare or you want to measure the before and after improvements of using Cloudflare, Cloudflare recommends using the following third-party tools:
 
-* [PageGym](https://pagegym.com/)
-* [GTmetrix](https://gtmetrix.com/)
-* [DebugBear](https://www.debugbear.com/test/website-speed)
-* [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
-* [WebPageTest](https://www.webpagetest.org/)
+- [PageGym](https://pagegym.com/)
+- [GTmetrix](https://gtmetrix.com/)
+- [DebugBear](https://www.debugbear.com/test/website-speed)
+- [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
+- [WebPageTest](https://www.webpagetest.org/)
 
 If you use these third-party tools, you should do the following to test website speed:
 
@@ -46,13 +46,11 @@ Based on the results of these speed tests, you may want to explore other ways to
 
 :::note
 
-
 Cloudflare does not consider Time to First Byte (TTFB) the most important measure of page load speed. If you are concerned about a slower TTFB while using Cloudflare, refer to our blog post about [Cloudflare and TTFB](http://blog.cloudflare.com/ttfb-time-to-first-byte-considered-meaningles/).
 
-
 :::
 
-***
+---
 
 ## Test Internet speed
 
diff --git a/src/content/docs/fundamentals/reference/best-practices.mdx b/src/content/docs/fundamentals/reference/best-practices.mdx
index a237a1d635c541d..6d8aa19d844e6f7 100644
--- a/src/content/docs/fundamentals/reference/best-practices.mdx
+++ b/src/content/docs/fundamentals/reference/best-practices.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account. 
+More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account.
 
 You can lose access to your account and or domain for several reasons: Death, divorce, disgruntled employee, or simply missing an email notification.
 
@@ -19,7 +19,7 @@ To help prevent loss of access:
 
 ## Relationships, partnerships, and business ventures
 
-Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active. 
+Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active.
 
 If you have a domain name or a portfolio of domain names for your business, ensuring you have a strict organization policy when it comes to vendor account creation or domain name registration is critical. The steps below will ensure your organization is the owner of the account and or domain names:
 
@@ -37,4 +37,4 @@ Most if not all online services have automated billing processes that will attem
 
 ## Deceased account holder or registrant
 
-While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you. 
+While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you.
diff --git a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
index f040e11a6251600..070a9aa8b37e5a3 100644
--- a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
+++ b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
@@ -12,12 +12,12 @@ This endpoint is managed and served by Cloudflare. It cannot be modified or cust
 
 A few examples include (but are not limited to):
 
-* [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
-* [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
-* [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
-* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
-* [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
-* [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
+- [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
+- [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
+- [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
+- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
+- [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
+- [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
 
 ## Recommended exclusions
 
diff --git a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
index dd7a00e47dce594..e99011bb53a7c81 100644
--- a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
+++ b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
@@ -13,7 +13,6 @@ Ray IDs are particularly useful when evaluating Security Events for patterns or
 Ray IDs are added as a [request header, cf-ray](/fundamentals/reference/http-headers/#cf-ray), to the connection from Cloudflare to the origin web server.
 As such the Ray IDs can be found using the Developer Tools in your browser or using curl with the `-v` option to show the headers.
 
-
 :::caution
 Ray IDs are not guaranteed to be unique for every request. In some situations, different requests may have the same Ray ID.
 :::
@@ -34,7 +33,7 @@ Please note that Security Events may use sampled data to improve performance. If
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer allows you to [build queries](/log-explorer/log-search/) for filtering specific Ray IDs.
 
diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
index 5a3fae1ade1c6bd..4d7916b94c2550d 100644
--- a/src/content/docs/fundamentals/reference/connection-limits.mdx
+++ b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), there are often two established [TCP connections](/fundamentals/reference/tcp-connections/): the first is between the requesting client to Cloudflare and the second is between Cloudflare and the origin server. Each connection has their own set of TCP and HTTP limits, which are documented below.
 
@@ -24,16 +24,16 @@ When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/h
 If you are using [Cloudflare tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), refer to [Origin configuration](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) to view or modify your connection settings.
 :::
 
-| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
-| ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/)                       |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | No                                                                             |
-| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
-| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
+| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                          | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits)        |
+| ----------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/) |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | No                                                                                    |
+| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                  | Yes                                                                                   |
+| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                 | No                                                                                    |
 
 ## Configurable limits
 
diff --git a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
index d1039a6ef7988a6..d4c1619380433f2 100644
--- a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
+++ b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
@@ -32,11 +32,11 @@ Yes, Cloudflare does collect a limited amount of data about your key. We store t
 
 Some self-signed keys and keys from certain manufacturers have been found to [not meet this requirement](https://www.chromium.org/security-keys) and should be avoided if you are minimizing your online privacy risk.
 
-***
+---
 
 For more details on how we set up Cryptographic Attestation of Personhood, refer to the [introductory blog post](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/).
 
-***
+---
 
 ## What devices are and are not allowed?
 
@@ -44,21 +44,21 @@ For more details on how we set up Cryptographic Attestation of Personhood, refer
 
 CAP supports a wide variety of hardware authenticators:
 
-* **Roaming (cross-platform) authenticators**:
-  * *Supported*: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
-  * *Examples*: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
-* **Platform authenticators:**
-  * *Examples*: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
+- **Roaming (cross-platform) authenticators**:
+  - _Supported_: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
+  - _Examples_: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
+- **Platform authenticators:**
+  - _Examples_: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
 
 ### Known limitations
 
 Most combinations of of web browsers and WebAuthn-capable authenticators will work, but there are some known compatibility issues with WebAuthn attestation that may prevent CAP from working successfully:
 
-* **Basic CAP**:
-  * *macOS desktop*: For TouchID, browser must be Safari
-  * *Android*: Browser must be Chrome
-* **CAP with Zero-Knowledge Proof**:
-  * *Apple platform authenticators* (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
+- **Basic CAP**:
+  - _macOS desktop_: For TouchID, browser must be Safari
+  - _Android_: Browser must be Chrome
+- **CAP with Zero-Knowledge Proof**:
+  - _Apple platform authenticators_ (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
 
 We are updating this list as the ecosystem evolves and as we continue to test different combinations.
 
@@ -74,16 +74,16 @@ If you do not have the necessary hardware (such as a Yubikey), you can still sol
 
 ## What are the common error codes and what do they mean?
 
-* **Unsupported\_att\_fmt**:
-  * *Cause*: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use *Firefox* and select the option to "anonymise your key".
-  * *Solution:* If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
-* **Unsupported\_issuer**:
-  * *Cause*: Your key is currently not supported.
-  * *Solution*: Use a [supported key](#allowed-devices).
+- **Unsupported_att_fmt**:
+  - _Cause_: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use _Firefox_ and select the option to "anonymise your key".
+  - _Solution:_ If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
+- **Unsupported_issuer**:
+  - _Cause_: Your key is currently not supported.
+  - _Solution_: Use a [supported key](#allowed-devices).
 
 ## Related resources
 
-* [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
-* [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
-* [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
-* [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
+- [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
+- [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
+- [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
+- [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
diff --git a/src/content/docs/fundamentals/reference/glossary.mdx b/src/content/docs/fundamentals/reference/glossary.mdx
index 32fb01bd11d1fa6..0656993c5d88b81 100644
--- a/src/content/docs/fundamentals/reference/glossary.mdx
+++ b/src/content/docs/fundamentals/reference/glossary.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's documentation.
 
diff --git a/src/content/docs/fundamentals/reference/google-analytics.mdx b/src/content/docs/fundamentals/reference/google-analytics.mdx
index 2f936dae6e12865..1e67ecfa7422f9b 100644
--- a/src/content/docs/fundamentals/reference/google-analytics.mdx
+++ b/src/content/docs/fundamentals/reference/google-analytics.mdx
@@ -19,10 +19,8 @@ Cloudflare only affects analytics tools that read logs directly from your web se
 
 :::note
 
-
 To troubleshoot potential issues with Google Analytics, refer to [Common GA setup mistakes](https://support.google.com/analytics/answer/1009683).
 
-
 :::
 
 ## Zaraz
@@ -31,8 +29,6 @@ As an alternative to the standard setup of Google Analytics with tag/snippet, Cl
 
 :::note
 
-
 Details about features of Google Analytics that are unavailable with Zaraz can be found in [Zaraz FAQ](/zaraz/faq/#tools)
 
-
 :::
diff --git a/src/content/docs/fundamentals/reference/index.mdx b/src/content/docs/fundamentals/reference/index.mdx
index edf24d7ad793faf..e239c0c053a0085 100644
--- a/src/content/docs/fundamentals/reference/index.mdx
+++ b/src/content/docs/fundamentals/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
index 15fcb26bc9607e2..1587fb70d0d1b81 100644
--- a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
+++ b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
@@ -10,14 +10,15 @@ products:
   - fundamentals
 ---
 
-Cloudflare's first iteration of SCIM integration introduced a concept called *Virtual Groups*, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.  
+Cloudflare's first iteration of SCIM integration introduced a concept called _Virtual Groups_, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.
+
+While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:
 
-While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:  
 - They could not be renamed or deleted in the IdP.
 - They could not be managed within Cloudflare.
 - Functionally, managing a Virtual Group was equivalent to syncing users and editing each member’s policies individually.
 
-With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.  
+With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.
 
 If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtual Group from your IdP to Cloudflare, no action is needed.
 
@@ -32,9 +33,7 @@ If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtua
 
 ## More resources
 
-* [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)  
-* [User Groups documentation](/fundamentals/manage-members/user-groups/)  
-* [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)  
-* [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)  
-
-
+- [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)
+- [User Groups documentation](/fundamentals/manage-members/user-groups/)
+- [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)
+- [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)
diff --git a/src/content/docs/fundamentals/reference/partners.mdx b/src/content/docs/fundamentals/reference/partners.mdx
index 5e6be4d2e93fd82..a066448644a58cd 100644
--- a/src/content/docs/fundamentals/reference/partners.mdx
+++ b/src/content/docs/fundamentals/reference/partners.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 [Cloudflare Technology Partners](https://www.cloudflare.com/partners/technology-partners/) offer purpose-built integrations with our products, providing expanded functionality for our users. Learn how to configure these integrations with our tutorials and how-to guides.
 
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
index 7e65a2e16b6a01a..106282e9575100c 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
@@ -17,7 +17,7 @@ Unfortunately, while most people respect these limitations and understand they e
 
 The following are some recommendations for using Cloudflare's services based on what may have brought you to this page.
 
-***
+---
 
 ## I'm a website operator and my content was redirected for Terms of Service violations
 
@@ -25,9 +25,9 @@ If you are on a Free, Pro, or Business Plan and your application appears to be s
 
 ## Options for web admins to remove redirects
 
-* **Serve redirected content from a grey-clouded sub-domain**
+- **Serve redirected content from a grey-clouded sub-domain**
 
-* **Serve redirected content from a paid service as outlined below**
+- **Serve redirected content from a paid service as outlined below**
 
 ## Delivering videos with Cloudflare using paid products
 
@@ -43,14 +43,14 @@ To get started with Stream, visit **Stream** from your Dashboard or [sign up](ht
 
 [Stream Delivery](https://www.cloudflare.com/products/stream-delivery/) offers caching and delivery of video content through Cloudflare data centers around the globe. This CDN feature is only available on the Cloudflare Enterprise Plan. Please [contact sales](https://www.cloudflare.com/products/stream-delivery/#) if you'd like to explore this option.
 
-***
+---
 
 ## Getting information on the content you are delivering
 
 If you need more information about the content your zone is serving (for example, content type), you can use the following tools:
 
-* Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
-* Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
+- Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
+- Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
 
 ![Cache Analytics - Identify type of traffic being transferred](~/assets/images/support/traffic-types.png)
 
@@ -58,6 +58,6 @@ If you need more information about the content your zone is serving (for example
 
 If you have additional questions about redirection (e.g. if you believe your content was redirected in error and have supporting evidence), file a [support ticket](https://dash.cloudflare.com/redirect?account=support) and include the following information:
 
-* Name of your domain
-* Description of the problem
-* Description of the content you're serving through Cloudflare's network
+- Name of your domain
+- Description of the problem
+- Description of the content you're serving through Cloudflare's network
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
index 1187f88b49dbde0..a0e6c30419d4e4c 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/redirects.mdx b/src/content/docs/fundamentals/reference/redirects.mdx
index cd7ef6cc592e166..faf74ce66f949a6 100644
--- a/src/content/docs/fundamentals/reference/redirects.mdx
+++ b/src/content/docs/fundamentals/reference/redirects.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare offers a variety of ways to perform <GlossaryTooltip term="redirect">URL redirects</GlossaryTooltip>, which tell a visitor's browser that the location of a page has been changed.
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
index c5e1d5484357c60..3a4e6c9b913f065 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
@@ -18,6 +18,6 @@ Our Trust & Safety team sends abuse reports to the domain owner or the abuse poi
 
 To assist with timely resolution and avoid potential service interruptions:
 
-* Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
-* Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
-* Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
+- Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
+- Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
+- Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
diff --git a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
index b216ceff2722d04..5c3cff418dfa842 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
@@ -13,31 +13,31 @@ products:
 
 Use Cloudflare's [online abuse form](https://abuse.cloudflare.com/) to report different types of abuse.
 
-***
+---
 
 ## DMCA complaints
 
 Valid [Digital Millennium Copyright Act (DMCA)](https://www.copyright.gov/dmca/) complaints must provide all of the following details:
 
-* A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
-* Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
-* Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
-* Your contact information, including your address, telephone number, and email address.
-* A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
-* A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
+- A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
+- Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
+- Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
+- Your contact information, including your address, telephone number, and email address.
+- A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
+- A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
 
-***
+---
 
 ## Phishing
 
 Valid phishing reports must provide all of the following details:
 
-* The domain in question.
-* The specific link to the phishing page.
+- The domain in question.
+- The specific link to the phishing page.
 
 After Cloudflare confirms existence of the phishing page, Cloudflare provides a warning page to visitors accessing the phishing link. Cloudflare also notifies the site owner to clean the malicious files from their origin web server.
 
-***
+---
 
 ## Trademark infringement
 
@@ -45,7 +45,7 @@ Cloudflare only acknowledges abuse reports from trademark holders or their legal
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
-***
+---
 
 ## Malware sites
 
@@ -53,7 +53,7 @@ Legitimate reports of malware URLs are blocked from loading via Cloudflare.
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
-***
+---
 
 ## Child exploitation material
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/index.mdx b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
index 1607f978b92b9c9..211b1f859b80956 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/index.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
@@ -19,7 +19,7 @@ When it comes to reports of abuse on websites that use our services, our ability
 
 ## Resources
 
-* [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
-* [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
-* [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
-* [Submit abuse report](https://www.cloudflare.com/abuse/form)
+- [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
+- [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
+- [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
+- [Submit abuse report](https://www.cloudflare.com/abuse/form)
diff --git a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
index bd36756a9df63e7..3da4ad19a0ab288 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
@@ -19,8 +19,10 @@ Cloudflare offers three ways for you to submit an abuse report:
 - Public form: Refer to [Submit an Abuse Report](https://abuse.cloudflare.com/) to learn more.
 - The Cloudflare dashboard, on the **Abuse reports** page.
 
-    <DashButton url="/?to=/:account/abuse-reports" />
-  Optionally, filter the reports based on date, report status, report type, and domain.
+  <DashButton url="/?to=/:account/abuse-reports" />
+  Optionally, filter the reports based on date, report status, report type, and
+  domain.
+
 - The Cloudflare API: Use the [Abuse Reports API](/api/resources/abuse_reports/) to submit an abuse report.
 
 ## View submitted reports
@@ -29,7 +31,7 @@ Users with Admin, Super Admin, or Trust & Safety roles can view any abuse report
 
 1. In the Cloudflare dashboard, go to the **Abuse reports** page.
 
-    <DashButton url="/?to=/:account/abuse-reports" />
+   <DashButton url="/?to=/:account/abuse-reports" />
 
 2. Optionally, filter the reports based on date, report status, report type, and domain.
 
@@ -37,6 +39,6 @@ If there was a mitigation against your website due to the abuse allegation, you
 
 ## Receive notifications
 
-You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites. 
+You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites.
 
-For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
\ No newline at end of file
+For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
diff --git a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
index 1b46a73b2f45f59..31a4b85d98924b4 100644
--- a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
+++ b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
@@ -21,7 +21,7 @@ These lifecycle stages may be referred to in different terms across Cloudflare p
 
 ### Early access
 
-During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will  often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
+During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
 
 ### Active support
 
@@ -41,13 +41,13 @@ While Cloudflare cannot provide support for all older versions of our libraries
 
 The SDK ecosystem follows semantic versioning, which defines versions as follows:
 
-* MAJOR version when there are backward-incompatible changes made.
-* MINOR version when functionality is added in a backward compatible-manner.
-* PATCH version for backward-compatible bug fixes (without any improvements).
+- MAJOR version when there are backward-incompatible changes made.
+- MINOR version when functionality is added in a backward compatible-manner.
+- PATCH version for backward-compatible bug fixes (without any improvements).
 
 :::caution
 
-As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases *may* contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
+As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases _may_ contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
 
 If this is not suitable for your use case, pin to a known good version or use the previous major version of the library.
 :::
@@ -62,5 +62,5 @@ Alongside the automatic migration approach, we provide documentation on the chan
 
 ## Related resources
 
-* [Semantic versioning definitions](https://semver.org/)
-* [Cloudflare's Terraform documentation](/terraform/)
+- [Semantic versioning definitions](https://semver.org/)
+- [Cloudflare's Terraform documentation](/terraform/)
diff --git a/src/content/docs/fundamentals/reference/tcp-connections.mdx b/src/content/docs/fundamentals/reference/tcp-connections.mdx
index 2a10e61edd13149..7662f578f5197a6 100644
--- a/src/content/docs/fundamentals/reference/tcp-connections.mdx
+++ b/src/content/docs/fundamentals/reference/tcp-connections.mdx
@@ -18,7 +18,7 @@ accTitle: Connections with Cloudflare
 A[Visitor] <-- Connection --> B[Cloudflare global network] <-- Connection --> C[Origin server]
 ```
 
-<br/>
+<br />
 
 User traffic is routed to the nearest Cloudflare data center based on the shortest [Border Gateway Protocol](https://www.cloudflare.com/learning/security/glossary/what-is-bgp/) (BGP) path, thanks to [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) routing. Cloudflare then processes the request. In case a request is not served from Cloudflare’s data centers, Cloudflare will open a connection to the origin server to forward the request.
 
@@ -36,10 +36,8 @@ For connections to users, Cloudflare has a default idle timeout of 400 seconds.
 
 :::note
 
-
 Be aware that even if there are keep-alives, Cloudflare cannot guarantee to keep a connection, since besides idleness, there are other reasons, like capacity balancing, data center maintenance or node restarts that can cause disconnections. Having this in mind, applications should be structured to handle disconnections gracefully.
 
-
 :::
 
 TCP connection settings between the user and Cloudflare, and between Cloudflare and Origin can be customized for Enterprise customers. Reach out to your account team for more details.
diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx
index b9e4589f7feeebc..7f18e62f0b0f805 100644
--- a/src/content/docs/fundamentals/reference/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/reference/troubleshooting.mdx
@@ -15,42 +15,42 @@ When you [set up Cloudflare](/fundamentals/account/), you may experience the fol
 
 ## Error messages
 
-* [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
-* [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
-* [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
-* [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
-* [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
-* [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
-* [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
-* [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
+- [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
+- [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
+- [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
+- [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
+- [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
+- [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
+- [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
+- [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
 
 ## Behavior
 
-* [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
-* [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
-* [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
-* [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
-* [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
-* [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
-* [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
+- [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
+- [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
+- [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
+- [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
+- [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
+- [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
+- [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
 
 ## Cloudflare
 
-* [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
-* [Contact Cloudflare support](/support/contacting-cloudflare-support/)
-* [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
+- [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
+- [Contact Cloudflare support](/support/contacting-cloudflare-support/)
+- [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
 
 ## General resources
 
-* [DNS FAQ](/dns/faq/)
-* [SSL/TLS FAQ](/ssl/faq/)
+- [DNS FAQ](/dns/faq/)
+- [SSL/TLS FAQ](/ssl/faq/)
 
 ## Is Cloudflare attacking me
 
 Two common scenarios falsely lead to the perception that Cloudflare is attacking your site:
 
-* Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
-* The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
+- Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
+- The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
 
 Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare's network.
 
diff --git a/src/content/docs/fundamentals/security/index.mdx b/src/content/docs/fundamentals/security/index.mdx
index 530676a405630c9..6998badd02eba4c 100644
--- a/src/content/docs/fundamentals/security/index.mdx
+++ b/src/content/docs/fundamentals/security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/security/pci-scans.mdx b/src/content/docs/fundamentals/security/pci-scans.mdx
index 6d67add60af9062..267a0d3f3e9bc55 100644
--- a/src/content/docs/fundamentals/security/pci-scans.mdx
+++ b/src/content/docs/fundamentals/security/pci-scans.mdx
@@ -11,10 +11,8 @@ products:
 
 :::note
 
-
 Cloudflare is PCI certified as a Data Processor. Refer to [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities) and Cloudflare's PCI DSS Responsibility Matrix for more information.
 
-
 :::
 
 PCI scanners are tools used to identify security weaknesses. When a business undergoes a compliance audit, PCI scan results are used for compliance verification.
@@ -39,7 +37,7 @@ However, customers can easily block all unwanted traffic to these ports by using
 
 You can find all our public compliance resources in the following pages:
 
-* [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
-* [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
+- [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
+- [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
 
 You can access Compliance documents in the Cloudflare dashboard by selecting your account where you are a Super Administrator and then navigating to **Support** > **Compliance Documents**.
diff --git a/src/content/docs/fundamentals/security/under-ddos-attack.mdx b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
index fec2c129035f0eb..2b0568e28ce011d 100644
--- a/src/content/docs/fundamentals/security/under-ddos-attack.mdx
+++ b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
@@ -7,7 +7,7 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="ddos-definition-and-diagram" product="learning-paths" />
 
@@ -15,9 +15,9 @@ import { Render } from "~/components"
 
 Common signs that you are under DDoS attack include:
 
-* Your site is offline or slow to respond to requests.
-* Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
-* Strange requests appear in your origin web server logs that do not match normal visitor behavior.
+- Your site is offline or slow to respond to requests.
+- Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
+- Strange requests appear in your origin web server logs that do not match normal visitor behavior.
 
 :::note
 
diff --git a/src/content/docs/fundamentals/user-profiles/2fa.mdx b/src/content/docs/fundamentals/user-profiles/2fa.mdx
index 57dc48b28cb5962..62092f62c5e8c8f 100644
--- a/src/content/docs/fundamentals/user-profiles/2fa.mdx
+++ b/src/content/docs/fundamentals/user-profiles/2fa.mdx
@@ -6,12 +6,10 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components"
-
+import { DashButton, Render } from "~/components";
 
 <Render file="2fa-enable" product="support" />
 
-
 ## Configure security key authentication for two-factor Cloudflare login
 
 :::caution
@@ -111,7 +109,7 @@ Regenerating your backup codes will invalidate your previous codes.
 
 1. Log in to the Cloudflare dashboard.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Authentication**.
@@ -129,17 +127,17 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 1. Log in to the Cloudflare dashboard.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Profile**.
 3. Select the **Authentication**.
    - To remove your security key:
-      1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
-      2. Select **Delete**.
-      3. Enter your Cloudflare password, then select **Remove**.
+     1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
+     2. Select **Delete**.
+     3. Enter your Cloudflare password, then select **Remove**.
    - To remove your TOTP mobile application authentication:
-      1. Select **Delete method** in the **Mobile App Authentication** card.
-      2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
+     1. Select **Delete method** in the **Mobile App Authentication** card.
+     2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
 
 ![how to disable your TOTP mobile application authentication.](https://developerdocsgifs.cloudflaretraining.com/resampled_5fps_disable_mobile_auth_v2_final.gif)
 
@@ -147,18 +145,18 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 If you lose access to a mobile device, security key, or authentication code, you can solve these issues by using a backup code or retrieving a backup code from your preferred authentication app.
 
-Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid\&hl=en\&oco=0).
+Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid&hl=en&oco=0).
 
 When setting up 2FA, you should have saved your backup codes in a secure location. To restore lost access using a Cloudflare backup code:
 
 1. Retrieve the backup code from where you stored it.
 2. Go to the [Cloudflare login page](https://dash.cloudflare.com/login), enter your username and password and select **Log in**.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 3. You should see a page titled **Two-Factor Authentication**
-   * If it has a text box, enter one of your backup codes and select **Log in**.
-   * If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
+   - If it has a text box, enter one of your backup codes and select **Log in**.
+   - If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
 
 :::note
 
@@ -167,7 +165,7 @@ Once you use a backup code, it becomes invalid.
 
 ## Related resources
 
-* [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en\&ref_topic=2954345\&co=GENIE.Platform%3DiOS\&oco=0)
-* [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
-* [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
-* [Account recovery](/fundamentals/user-profiles/account-recovery/)
+- [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en&ref_topic=2954345&co=GENIE.Platform%3DiOS&oco=0)
+- [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
+- [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
+- [Account recovery](/fundamentals/user-profiles/account-recovery/)
diff --git a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
index 31d166bcf9914c5..05298913d04f3cd 100644
--- a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
+++ b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
@@ -12,7 +12,7 @@ If you do not have access to your 2FA account or backup codes and cannot current
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. On the **Two-Factor Authentication** page, select **Try recovery** on **Lost all 2FA devices and backup codes?**.
 3. Select **Begin recovery**.
@@ -24,8 +24,8 @@ If you see **Device verified**, you will receive an email within 3-5 days with i
 
 If you see **Device verification failed**, you may be able to try again considering the following:
 
-   * If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
-   * Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
-   * You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
+- If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
+- Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
+- You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
 
-If you are still unable to verify your device, follow the instructions to *Request manual verification* on the **Device verification failed** page.
+If you are still unable to verify your device, follow the instructions to _Request manual verification_ on the **Device verification failed** page.
diff --git a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
index f848ead54c25ce4..7e8b24b3c6504bf 100644
--- a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
+++ b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
@@ -62,7 +62,7 @@ If you forget the email address associated with your application:
 
 ## Forgot your password
 
-You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option. 
+You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option.
 
 If you forget the password associated with your email address:
 
diff --git a/src/content/docs/fundamentals/user-profiles/customize-account.mdx b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
index e2069315ad718cd..c7b80fefce89a7c 100644
--- a/src/content/docs/fundamentals/user-profiles/customize-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
@@ -35,9 +35,9 @@ Adjust how the Cloudflare dashboard appears on your device.
 
 2. Go to **Profile**.
 3. From **Settings** > **Dashboard appearance**, choose a value:
-   * **Dark**: Defaults to darker colors.
-   * **Light**: Defaults to lighter colors.
-   * **Use system setting**: Defaults to the option used on your device.
+   - **Dark**: Defaults to darker colors.
+   - **Light**: Defaults to lighter colors.
+   - **Use system setting**: Defaults to the option used on your device.
 
 Your dashboard display will update to the new appearance setting automatically.
 
diff --git a/src/content/docs/fundamentals/user-profiles/delete-account.mdx b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
index 94289a564a45da4..09b79d815f25fa7 100644
--- a/src/content/docs/fundamentals/user-profiles/delete-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
@@ -28,7 +28,7 @@ Before Cloudflare can cancel your account and delete your personal information,
 - [Disable auto-renew for your Registrar domain(s)](/registrar/account-options/renew-domains#set-up-automatic-renewals)
 - If you are using a Cloudflare [CNAME setup](/dns/zone-setups/partial-setup/), [update your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) at your DNS provider to point to your website IPs or hostnames instead of Cloudflare.
 - [Delete payment information](/billing/get-started/update-billing-info/#delete-a-payment-method)
-- (*Optional*) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
+- (_Optional_) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
 
 ## Delete your Cloudflare account
 
@@ -49,7 +49,7 @@ All domains, subscriptions, and billing information on your account will be remo
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Delete this user**.
@@ -61,4 +61,3 @@ All domains, subscriptions, and billing information on your account will be remo
 Cloudflare will purge your personal information within a year of a deletion request unless required to retain it for legal obligations (such as ongoing abuse investigations or pending litigation). Refer to the [Cloudflare Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/) for further information about the deletion of personal information following the cancellation of your account.
 
 :::
-
diff --git a/src/content/docs/fundamentals/user-profiles/login.mdx b/src/content/docs/fundamentals/user-profiles/login.mdx
index e81d66c7afbac91..9152dcc59e82381 100644
--- a/src/content/docs/fundamentals/user-profiles/login.mdx
+++ b/src/content/docs/fundamentals/user-profiles/login.mdx
@@ -27,6 +27,7 @@ Enter your email address and password.
 If your admin has enabled [enabled SSO](/fundamentals/manage-members/dashboard-sso/), enter your email address.
 
 ### Social login
+
 Social login allows you to sign in with a trusted 3rd party sign in service such as Apple, Google, or GitHub. Social login is only available for accounts with a verified email address, or accounts that signed up via social login initially. If you have additionally configured two-factor authentication on your account, that will be presented in addition to any login and two-factor authentication provided by the social login provider.
 
 :::note
@@ -43,12 +44,11 @@ To set a password, go to [Forgot Password](https://dash.cloudflare.com/forgot-pa
 You will receive an email with instructions to set your password. Once created, use your email and the new password to log in.
 :::
 
-
 #### Sign in with Apple
 
-* **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
+- **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
 
-* **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
+- **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
 
 If you chose to share your email when creating a Cloudflare account with Apple ID and want to set a password and obtain an API key, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) login page and select **Forgot your password?** to trigger a password reset email.
 
@@ -73,4 +73,3 @@ If you created your Cloudflare account using Apple Relay and decide to change yo
 - Sign in with GitHub uses the [Primary email address](https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address) which is set on your GitHub account. If you change your primary email address in GitHub, you will not be able to log into your Cloudflare account using GitHub social login.
 
 - If you select **Sign in with GitHub** with an email that does not already have a Cloudflare account associated with it, Cloudflare will create a new account and allow you to sign in using **Sign in with GitHub** option moving forward.
-
diff --git a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
index ce1ca48798a83bb..8dfe5802aeb8a3b 100644
--- a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
+++ b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
@@ -25,14 +25,14 @@ Email MFA can only be disabled by enabling [two-factor authentication](/fundamen
 
 ## Troubleshoot MFA
 
-Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from *[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)*\_**.**\_
+Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from _[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)_\_**.**\_
 
 Other times, emails are rejected by the recipient email service. Cloudflare will try again it will flag your email address after several attempts and no further emails will be sent.
 
 If you still do not receive an email after ensuring your email service is not flagging Cloudflare, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
 
-***
+---
 
 ## Related resources
 
-* [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
+- [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
index b3fc9378ed0e2b3..430a7d78421a34a 100644
--- a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
+++ b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
@@ -34,7 +34,7 @@ If you cannot find your verification email or your email has expired, request an
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified).
@@ -47,11 +47,11 @@ To check your verification:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, your email address will have `(verified)` added after it.
 
 If your email is still not verified, try clicking the verification link in a different browser or a private window.
 
-If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
\ No newline at end of file
+If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
diff --git a/src/content/docs/google-tag-gateway/index.mdx b/src/content/docs/google-tag-gateway/index.mdx
index df04561d2b6e7ba..313bd3117c71010 100644
--- a/src/content/docs/google-tag-gateway/index.mdx
+++ b/src/content/docs/google-tag-gateway/index.mdx
@@ -8,8 +8,8 @@ sidebar:
   order: 1
 tags:
   - Google
-
 ---
+
 import { DashButton } from "~/components";
 
 Google tag gateway for advertisers allows website owners using Cloudflare as a CDN to get the most out of ad measurement tools with just a few clicks. It allows you to deploy Google scripts using your own domain, enhancing data privacy and improving signal measurement recovery. Unlike standard setups where tags are requested from a Google domain, Google tag gateway for advertisers loads the tag from your domain and sends measurement events to your domain, where they are forwarded to Google.
@@ -25,6 +25,7 @@ Google tag gateway for advertisers is free to use. Requests routed through the g
 Site owners can enable this feature in one of two ways: through the Google tag console, or through the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/tag-management/google-tag-gateway).
 
 ### Configure in Google Tag Manager
+
 The fastest way to set up Google tag gateway for advertisers is in Google Tag Manager. [Follow the steps in Google's Help Center](https://support.google.com/analytics/answer/16061641).
 
 ### Configure in the Cloudflare dashboard
@@ -43,7 +44,7 @@ Your Cloudflare dashboard user must have one of the following [Account Roles](/f
 ![Google tag gateway for advertisers configuration](~/assets/images/google-tag-gateway/google-tag-configuration.png)
 
 4. Add your Google tag ID and the path on your website reserved for the Google tag.
-The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
+   The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
 
 ![Add to ID and path](~/assets/images/google-tag-gateway/google-tag-id-path.png)
 
@@ -62,6 +63,7 @@ If you need different tag behavior for specific subdomains (for example, only fi
 This approach lets you maintain a single zone-wide Google tag gateway configuration while still customizing tag behavior per subdomain.
 
 ## Related resources
+
 - [Google Developer Docs: Set up Google tag gateway for advertisers](https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide?setup=auto)
 - [Google Help Center: Set up Google tag gateway for advertisers in the Google tag with Cloudflare](https://support.google.com/tagmanager/answer/16061406)
 - [Google Help Center: Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare](https://support.google.com/analytics/answer/16061641)
diff --git a/src/content/docs/health-checks/concepts/health-checks-regions.mdx b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
index 2cafe5f8e78ba1a..65a3eecbc16b25f 100644
--- a/src/content/docs/health-checks/concepts/health-checks-regions.mdx
+++ b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
@@ -6,7 +6,6 @@ products:
   - health-checks
 sidebar:
   order: 4
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/health-checks/concepts/index.mdx b/src/content/docs/health-checks/concepts/index.mdx
index 63214119f1c7c7c..4bf31c3559d964a 100644
--- a/src/content/docs/health-checks/concepts/index.mdx
+++ b/src/content/docs/health-checks/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts involved in Cloudflare Health Checks.
 
diff --git a/src/content/docs/health-checks/health-checks-analytics.mdx b/src/content/docs/health-checks/health-checks-analytics.mdx
index 0270a58b2a3f59a..532c92b0c481ca8 100644
--- a/src/content/docs/health-checks/health-checks-analytics.mdx
+++ b/src/content/docs/health-checks/health-checks-analytics.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
 tags:
   - Analytics
-
 ---
 
-import { AvailableNotifications, Render, DashButton } from "~/components"
+import { AvailableNotifications, Render, DashButton } from "~/components";
 
 <Render file="smart-shield-callout" product="smart-shield" />
 
diff --git a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
index 6ac6065ecb7a80e..7f000b24d42b7cc 100644
--- a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
+++ b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
@@ -6,10 +6,9 @@ products:
   - health-checks
 sidebar:
   order: 9
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 You can [configure notification emails](/health-checks/how-to/health-checks-notifications/#configure-notifications) to be alerted when the Health Check detects that there is a change in the status of your origin server. Cloudflare will send you an email within seconds so you can take the necessary action before customers are impacted.
 
@@ -31,12 +30,10 @@ The email provides information to determine what caused the health status change
 
 :::note
 
-
 A notification is only sent after a change of status in the majority of all selected region(s).
 
 For a single region, this will be 2 of 3 data centers. With 13 regions selected, this will be 7 of 13 regions.
 
-
 :::
 
 See [common error codes](/health-checks/health-checks-analytics/#common-error-codes) for more information regarding the cause of any changes to your Health Check.
diff --git a/src/content/docs/health-checks/how-to/index.mdx b/src/content/docs/health-checks/how-to/index.mdx
index 0ee79dad8ccb82c..db9952b5952d517 100644
--- a/src/content/docs/health-checks/how-to/index.mdx
+++ b/src/content/docs/health-checks/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 See the following pages for more information about standalone Health Checks:
 
diff --git a/src/content/docs/health-checks/how-to/zone-lockdown.mdx b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
index 591c602337a1232..a4478cdeee2a61a 100644
--- a/src/content/docs/health-checks/how-to/zone-lockdown.mdx
+++ b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Zone lockdown migration guide
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
+<Render file="zone-lockdown" product="smart-shield" />
diff --git a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
index c65b5e2f272d5e2..2062eeebed2f06a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
@@ -34,7 +34,7 @@ npm i -D drizzle-kit tsx @types/node
 
 Add the required Node.js compatibility flags and Hyperdrive binding to your `wrangler.jsonc` file:
 
-<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive"/>
+<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive" />
 
 ## 2. Configure Drizzle
 
@@ -75,7 +75,7 @@ import { users } from "./db/schema";
 
 export interface Env {
 	HYPERDRIVE: Hyperdrive;
-  }
+}
 
 export default {
 	async fetch(request, env, ctx): Promise<Response> {
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
index e193a5b10a6b006..2d0266f83dce9cd 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
@@ -25,12 +25,13 @@ You can connect Hyperdrive to any existing Prisma Postgres database by using you
 2. Select **Connect to your database** > **Any client**.
 3. Select **Generate database credentials**. Copy the connection string for your Prisma Postgres database.
 4. Edit the connection string to make it compatible with Hyperdrive.
-  - Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
-  - The final string will look like:
-  
-   ```txt ins="database_name"
-   postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
-    ```   
+
+- Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
+- The final string will look like:
+
+````txt ins="database_name"
+postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
+ ```
 
 :::note
 
@@ -38,7 +39,7 @@ An alternative to the Prisma Data Platform is to use the [`create-db`](https://w
 
 ```bash
 npx create-db@latest
-```
+````
 
 :::
 
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
index 9c1996a98116a4a..72797b0b520501a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
@@ -32,7 +32,7 @@ With a database user, password, database endpoint (hostname and port) and databa
 
 :::note
 
-When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers. 
+When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers.
 
 :::
 
diff --git a/src/content/docs/hyperdrive/observability/troubleshooting.mdx b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
index 4ef6f14661763a2..1c6ad7bce772665 100644
--- a/src/content/docs/hyperdrive/observability/troubleshooting.mdx
+++ b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
@@ -32,10 +32,10 @@ Hyperdrive will also issue an empty test query, a `;` in PostgreSQL, to validate
 
 Hyperdrive may also emit `Failed to connect to the provided database` when it fails to connect to the database when attempting to create a Hyperdrive configuration. This is possible when the TLS (SSL) certificates are misconfigured. Here is a non-exhaustive table of potential failure to connect errors:
 
-| Error message | Details               | Recommended fixes |
-| ---------- | -------------------- | --------------------- |
-| Server return error and closed connection. | This message occurs when you attempt to connect to a database that has client certificate verification enabled. | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
-| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database. |
+| Error message                                 | Details                                                                                                                                                                                               | Recommended fixes                                                                                                                                                     |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Server return error and closed connection.    | This message occurs when you attempt to connect to a database that has client certificate verification enabled.                                                                                       | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
+| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database.                                      |
 
 ## Connection errors
 
@@ -46,16 +46,14 @@ Hyperdrive errors that do not map 1:1 with an error message code [documented by
 
 Hyperdrive may also encounter `ErrorResponse` wire protocol messages sent by your database. Hyperdrive will pass these errors through unchanged when possible.
 
-
-
 ### Hyperdrive specific errors
 
-| Error Message                                          | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
-| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Internal error.`                                      | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                                                               |
-| `Failed to acquire a connection from the pool.`        | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
-| `Server connection attempt failed: connection_refused` | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
-| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases. | Remove prepared statements from your MySQL queries. |
+| Error Message                                                           | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
+| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Internal error.`                                                       | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                    |
+| `Failed to acquire a connection from the pool.`                         | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
+| `Server connection attempt failed: connection_refused`                  | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
+| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases.                            | Remove prepared statements from your MySQL queries.                                                                                                                                                                                                                                            |
 
 ### Node errors
 
@@ -75,8 +73,8 @@ If your queries are not being cached despite Hyperdrive having caching enabled,
 
 ### Driver errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| Error Message                                              | Details                                                                                                                                              | Recommended fixes                                                                                                                                                                               |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `Code generation from strings disallowed for this context` | The database driver you are using is attempting to use the `eval()` command, which is unsupported on Cloudflare Workers (common in `mysql2` driver). | Configure the database driver to not use `eval()`. See how to [configure `mysql2` to disable the usage of `eval()`](/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/mysql2/). |
 
 ### Stale connection and I/O context errors
@@ -85,46 +83,46 @@ These errors occur when a database client or connection is created in the global
 
 #### Workers runtime errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.` | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function. |
-| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request. | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
+| Error Message                                                                                                                                                                                                                  | Details                                                                                                                     | Recommended fixes                                                                                                                                                             |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.`                                           | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function.                                                                                      |
+| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request.                         | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
 
 #### node-postgres (`pg`) errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Connection terminated` | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request. | Create a new `Client` inside your handler instead of reusing one from a prior request. |
-| `Connection terminated unexpectedly` | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request. |
-| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests). | Create a new `Client` inside your handler. Do not store clients in global variables. |
-| `Client was closed and is not queryable` | A query was attempted on a client whose `.end()` method was already called. | Create a new `Client` inside your handler instead of reusing one. |
-| `Cannot use a pool after calling end on the pool` | `pool.connect()` was called on a `Pool` instance that has already been ended. | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
-| `Client has already been connected. You cannot reuse a client.` | `client.connect()` was called on a client that was already connected in a previous invocation. | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected. |
+| Error Message                                                    | Details                                                                                                                                         | Recommended fixes                                                                                                                         |
+| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `Connection terminated`                                          | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request.                                     | Create a new `Client` inside your handler instead of reusing one from a prior request.                                                    |
+| `Connection terminated unexpectedly`                             | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request.                                                                              |
+| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests).                                                 | Create a new `Client` inside your handler. Do not store clients in global variables.                                                      |
+| `Client was closed and is not queryable`                         | A query was attempted on a client whose `.end()` method was already called.                                                                     | Create a new `Client` inside your handler instead of reusing one.                                                                         |
+| `Cannot use a pool after calling end on the pool`                | `pool.connect()` was called on a `Pool` instance that has already been ended.                                                                   | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
+| `Client has already been connected. You cannot reuse a client.`  | `client.connect()` was called on a client that was already connected in a previous invocation.                                                  | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected.                                            |
 
 #### Postgres.js (`postgres`) errors
 
 Postgres.js error messages include the error code and the target host. The `code` property on the error object contains the error code.
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `write CONNECTION_ENDED <host>:<port>` | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`. | Create a new `postgres()` instance inside your handler. |
-| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request. |
-| `write CONNECTION_CLOSED <host>:<port>` | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`. | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
+| Error Message                              | Details                                                                                                                                                                                 | Recommended fixes                                                                                                                           |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `write CONNECTION_ENDED <host>:<port>`     | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`.                                              | Create a new `postgres()` instance inside your handler.                                                                                     |
+| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request.                                                                   |
+| `write CONNECTION_CLOSED <host>:<port>`    | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`.                                                                        | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
 
 #### mysql2 errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error. | Create a new connection inside your handler instead of reusing one from global scope. |
-| `Connection lost: The server closed the connection.` | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request. |
-| `Pool is closed.` | `pool.getConnection()` was called on a pool that has already been closed. | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
+| Error Message                                              | Details                                                                                                                           | Recommended fixes                                                                                                                          |
+| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error.                                  | Create a new connection inside your handler instead of reusing one from global scope.                                                      |
+| `Connection lost: The server closed the connection.`       | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request.                                                                             |
+| `Pool is closed.`                                          | `pool.getConnection()` was called on a pool that has already been closed.                                                         | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
 
 #### mysql errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Cannot enqueue Query after fatal error.` | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`. | Create a new connection inside your handler instead of reusing one from global scope. |
-| `Cannot enqueue Query after invoking quit.` | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`. | Create a new connection inside your handler for every request. |
+| Error Message                                                   | Details                                                                                                                                   | Recommended fixes                                                                            |
+| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| `Cannot enqueue Query after fatal error.`                       | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`.        | Create a new connection inside your handler instead of reusing one from global scope.        |
+| `Cannot enqueue Query after invoking quit.`                     | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`.                               | Create a new connection inside your handler for every request.                               |
 | `Cannot enqueue Handshake after already enqueuing a Handshake.` | `.connect()` was called on a connection that was already connected in a previous request. Error code: `PROTOCOL_ENQUEUE_HANDSHAKE_TWICE`. | Create a new connection per request. mysql connections cannot be reconnected once connected. |
 
 ### Improve performance
diff --git a/src/content/docs/hyperdrive/platform/limits.mdx b/src/content/docs/hyperdrive/platform/limits.mdx
index 76f3f59ff4ae007..312468a7fe964d7 100644
--- a/src/content/docs/hyperdrive/platform/limits.mdx
+++ b/src/content/docs/hyperdrive/platform/limits.mdx
@@ -14,10 +14,10 @@ The following limits apply to Hyperdrive configurations, connections, and querie
 
 These limits apply when creating or updating Hyperdrive configurations.
 
-| Limit                          | Free                  | Paid                  |
-| ------------------------------ | --------------------- | --------------------- |
-| Maximum configured databases   | 10 per account        | 25 per account        |
-| Maximum username length [^1]   | 63 characters (bytes) | 63 characters (bytes) |
+| Limit                             | Free                  | Paid                  |
+| --------------------------------- | --------------------- | --------------------- |
+| Maximum configured databases      | 10 per account        | 25 per account        |
+| Maximum username length [^1]      | 63 characters (bytes) | 63 characters (bytes) |
 | Maximum database name length [^1] | 63 characters (bytes) | 63 characters (bytes) |
 
 [^1]: This is a limit enforced by PostgreSQL. Some database providers may enforce smaller limits.
@@ -26,10 +26,10 @@ These limits apply when creating or updating Hyperdrive configurations.
 
 These limits apply to connections between Hyperdrive and your origin database.
 
-| Limit                              | Free                     | Paid                      |
-| ---------------------------------- | ------------------------ | ------------------------- |
-| Initial connection timeout         | 15 seconds               | 15 seconds                |
-| Idle connection timeout            | 10 minutes               | 10 minutes                |
+| Limit                                                        | Free            | Paid             |
+| ------------------------------------------------------------ | --------------- | ---------------- |
+| Initial connection timeout                                   | 15 seconds      | 15 seconds       |
+| Idle connection timeout                                      | 10 minutes      | 10 minutes       |
 | Maximum origin database connections (per configuration) [^2] | ~20 connections | ~100 connections |
 
 Hyperdrive does not limit the number of concurrent client connections from your Workers. However, Hyperdrive limits connections to your origin database because most hosted databases have connection limits.
@@ -40,9 +40,9 @@ Hyperdrive does not limit the number of concurrent client connections from your
 
 When Hyperdrive cannot acquire a connection to your origin database, you may see one of the following errors:
 
-| Error message | Cause |
-| ------------- | ----- |
-| `Failed to acquire a connection from the pool.` | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause. |
+| Error message                                          | Cause                                                                                                                                                           |
+| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Failed to acquire a connection from the pool.`        | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause.                           |
 | `Server connection attempt failed: connection_refused` | Your origin database is rejecting connections. This can occur when a firewall blocks Hyperdrive, or when your database provider's connection limit is exceeded. |
 
 For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdrive/observability/troubleshooting/).
@@ -51,10 +51,10 @@ For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdriv
 
 These limits apply to queries sent through Hyperdrive.
 
-| Limit                              | Free      | Paid      |
-| ---------------------------------- | --------- | --------- |
+| Limit                              | Free       | Paid       |
+| ---------------------------------- | ---------- | ---------- |
 | Maximum query (statement) duration | 60 seconds | 60 seconds |
-| Maximum cached query response size | 50 MB     | 50 MB     |
+| Maximum cached query response size | 50 MB      | 50 MB      |
 
 Queries exceeding the maximum duration are terminated. Query responses larger than 50 MB are not cached but are still returned to your Worker.
 
diff --git a/src/content/docs/hyperdrive/platform/storage-options.mdx b/src/content/docs/hyperdrive/platform/storage-options.mdx
index 15e4357c49ab353..e47f0bee278b20d 100644
--- a/src/content/docs/hyperdrive/platform/storage-options.mdx
+++ b/src/content/docs/hyperdrive/platform/storage-options.mdx
@@ -9,5 +9,5 @@ products:
   - hyperdrive
   - kv
   - r2
-  - d1 
+  - d1
 ---
diff --git a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
index 79d2a4c9a8334f6..634a4a834452673 100644
--- a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
+++ b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
@@ -12,4 +12,4 @@ import { WranglerNamespace } from "~/components";
 
 The following [Wrangler commands](/workers/wrangler/) apply to Hyperdrive.
 
-<WranglerNamespace namespace="hyperdrive" />
\ No newline at end of file
+<WranglerNamespace namespace="hyperdrive" />
diff --git a/src/content/docs/hyperdrive/tutorials/index.mdx b/src/content/docs/hyperdrive/tutorials/index.mdx
index 303882afc56a048..20365d245d2b967 100644
--- a/src/content/docs/hyperdrive/tutorials/index.mdx
+++ b/src/content/docs/hyperdrive/tutorials/index.mdx
@@ -10,7 +10,7 @@ products:
   - workers
 ---
 
-import { GlossaryTooltip, ListTutorials } from "~/components"
+import { GlossaryTooltip, ListTutorials } from "~/components";
 
 View <GlossaryTooltip term="tutorial">tutorials</GlossaryTooltip> to help you get started with Hyperdrive.
 
diff --git a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
index b9f564b90204b67..83a5d692b9d5e21 100644
--- a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
+++ b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
@@ -3,7 +3,7 @@ reviewed: 2023-10-30
 difficulty: Beginner
 pcx_content_type: tutorial
 title: Create a serverless, globally distributed time-series API with Timescale
-products:	[workers]
+products: [workers]
 tags:
   - PostgreSQL
   - TypeScript
diff --git a/src/content/docs/images/optimization/make-responsive-images.mdx b/src/content/docs/images/optimization/make-responsive-images.mdx
index a0dcd9f7f0c9726..951c3590cc0ae6e 100644
--- a/src/content/docs/images/optimization/make-responsive-images.mdx
+++ b/src/content/docs/images/optimization/make-responsive-images.mdx
@@ -68,12 +68,7 @@ The browser evaluates screen size, pixel density, and network conditions, then s
 The snippet below shows how `srcset` can be used within an `<img>` tag to serve one of two possible sizes, depending on the user's device pixel ratio:
 
 ```html
-<img
-	src="portrait-800w.jpg"
-	srcset="
-		portrait-1600.jpg 2x,
-	"
-/>
+<img src="portrait-800w.jpg" srcset="portrait-1600.jpg 2x" />
 ```
 
 Instead of pre-generating each size, use Images to point every `srcset` entry at the same source image with a different `width` parameter and pixel density descriptor (for example, `2x`). Once the browser selects the right width for the user's device pixel ratio, Cloudflare dynamically generates the resized version on request:
@@ -164,11 +159,11 @@ The default breakpoints for client hints are: `320`, `768`, `960`, and `1200` pi
 The following table shows the widths that Cloudflare will pick based on the default breakpoints. If the detected viewport width exceeds the largest breakpoint, the image is served at that largest breakpoint.
 
 | Detected viewport width | Served image width |
-| ---------- | ------------- |
-| 280px          | 320px         |
-| 500px          | 768px         |
-| 960px          | 960px         |
-| 1500px          | 1200px        |
+| ----------------------- | ------------------ |
+| 280px                   | 320px              |
+| 500px                   | 768px              |
+| 960px                   | 960px              |
+| 1500px                  | 1200px             |
 
 You can override the default breakpoints using the [`wbreakpoints`](/images/optimization/features/#width) sub-parameter, which accepts positive integers separated by semicolons.
 
diff --git a/src/content/docs/images/optimization/transformations/flows.mdx b/src/content/docs/images/optimization/transformations/flows.mdx
index 90b4c423f905e10..c9d36c389aba1ca 100644
--- a/src/content/docs/images/optimization/transformations/flows.mdx
+++ b/src/content/docs/images/optimization/transformations/flows.mdx
@@ -6,10 +6,12 @@ sidebar:
   products:
     - images
 ---
+
 import { Description, Render } from "~/components";
 
 <Description>
-	Define automated rules to optimize remote images without writing any code or changing your existing URLs.
+	Define automated rules to optimize remote images without writing any code or
+	changing your existing URLs.
 </Description>
 
 Flows let you automatically apply image optimization to requests on your zone.
@@ -32,6 +34,7 @@ Currently, Cloudflare supports flows for Fastly Image Optimizer. When enabled, C
 A **custom flow** lets you define your own conditions and actions for image optimization.
 
 This is well-suited for situations where you want to optimize your images broadly and consistently, such as:
+
 - **Automatic format conversion** — Transcode all images to modern formats like AVIF or WebP across your entire site.
 - **Responsive sizing** — Automatically resize images based on each user's device.
 - **Directory-based optimization** — Enforce a consistent size for all images in a particular path, such as 100x100 for images where the path contains `/thumbnail`.
@@ -41,16 +44,19 @@ This is well-suited for situations where you want to optimize your images broadl
 Before setting up a flow, make sure that transformations are turned on for your zone under **Images** > **Transformations** in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/images/transformations).
 
 When an image is requested on your zone, Cloudflare checks to see whether the request matches the conditions for any of your configured flows:
+
 - Flows are evaluated from top to bottom in the order that they appear in the dashboard.
 - If a request matches more than one flow, only the first matching flow will run.
 - If no flow matches, then the request passes through to your origin unmodified.
 - To control priority, you can reorder flows in the dashboard.
 
 If the request matches a flow's conditions, then Cloudflare rewrites the URL to pass through the Images service with the specified parameters:
+
 - A custom flow triggers only on requests for [supported image extensions](/images/get-started/limits/). HTML pages, CSS files, and other non-images are never affected.
 - A provider flow evaluates requests based on provider-specific optimization parameters. For example, a Fastly provider flow triggers only when the request contains parameters like `?width`, `?height`, or `?fit`. Cloudflare will ignore any unrecognized parameters.
 
 In your request lifecycle, flows are evaluated after standard HTTP [redirect rules](/rules/url-forwarding/):
+
 - Any existing URL rewrites or redirect rules will be applied before Images evaluates the request, which may affect matching behavior.
 - Flows include built-in loop prevention. If the request is already coming from the Images service, then the flow will not re-trigger on that subrequest.
 
@@ -59,6 +65,7 @@ In your request lifecycle, flows are evaluated after standard HTTP [redirect rul
 Currently, Cloudflare supports flows to handle migrations from Fastly Image Optimizer.
 
 To add a provider flow:
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Images** > **Transformations** and select your zone.
 3. Select the **Automation** tab, then select **Add provider flow**.
@@ -122,11 +129,11 @@ Cloudflare determines the optimal width using either [client hints](/images/opti
 
 You can fine-tune the `width=auto` behavior with the following sub-parameters:
 
-| Sub-parameter | Description | Default |
-| --- | --- | --- |
-| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints) | `320;768;960;1200` |
-| `wmobile` | Override default width, in pixels, for mobile devices (user-agent detection) | `768` |
-| `wdesktop` | Override default width, in pixels, for desktop devices (user-agent detection) | `1200` |
+| Sub-parameter  | Description                                                                   | Default            |
+| -------------- | ----------------------------------------------------------------------------- | ------------------ |
+| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints)                  | `320;768;960;1200` |
+| `wmobile`      | Override default width, in pixels, for mobile devices (user-agent detection)  | `768`              |
+| `wdesktop`     | Override default width, in pixels, for desktop devices (user-agent detection) | `1200`             |
 
 To learn how `width=auto` works, refer to our guide on [serving responsive images](/images/optimization/make-responsive-images/).
 
diff --git a/src/content/docs/images/optimization/transformations/overview.mdx b/src/content/docs/images/optimization/transformations/overview.mdx
index d623c6694db1f47..7de24256a768de1 100644
--- a/src/content/docs/images/optimization/transformations/overview.mdx
+++ b/src/content/docs/images/optimization/transformations/overview.mdx
@@ -11,7 +11,8 @@ products:
 import { Description, Render } from "~/components";
 
 <Description>
-	Transformations are requests to optimize and manipulate remote images that are stored outside of Images.
+	Transformations are requests to optimize and manipulate remote images that are
+	stored outside of Images.
 </Description>
 
 When you ship applications on Cloudflare, you can use Images to automatically optimize and cache your images from any origin.
diff --git a/src/content/docs/key-transparency/api/epochs.mdx b/src/content/docs/key-transparency/api/epochs.mdx
index d9a24544386e49e..6aa0c01a45d12dd 100644
--- a/src/content/docs/key-transparency/api/epochs.mdx
+++ b/src/content/docs/key-transparency/api/epochs.mdx
@@ -49,7 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}/audit
 - If `root` is defined for the namespace, the first epoch must match it (number and digest).
 - Epochs must be increasing. Second epoch is 2, third is 3, etc.
 - Epochs must have a unique digest or it will be rejected.
-- Epochs cannot be republished. 
+- Epochs cannot be republished.
 - Digest must be a 32 byte string hex encoded (length 64).
 
 If a namespace is disabled, you receive the following error:
diff --git a/src/content/docs/key-transparency/api/index.mdx b/src/content/docs/key-transparency/api/index.mdx
index c390a1774ee252d..64b24fdf3146f9d 100644
--- a/src/content/docs/key-transparency/api/index.mdx
+++ b/src/content/docs/key-transparency/api/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/key-transparency/api/namespaces.mdx b/src/content/docs/key-transparency/api/namespaces.mdx
index 3e42e5b0a09d29b..055e97b897823f2 100644
--- a/src/content/docs/key-transparency/api/namespaces.mdx
+++ b/src/content/docs/key-transparency/api/namespaces.mdx
@@ -20,8 +20,8 @@ The following fields are required when making a `POST` request:
 - `name`
 - `public`
 - `root`
-- `signature_version`: 
-  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor 
+- `signature_version`:
+  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor
   - 0x0002 for [bincode serialisation](https://github.com/bincode-org/bincode/blob/trunk/docs/spec.md) E25519 serialisation by the Auditor
 
 The `log_directory` field is optional. If set, Cloudflare will use it to fetch audit proofs and validate them.
@@ -49,6 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces' \
 ```
 
 After publishing the first epoch, `status` will show `Online`. Possible statuses include:
+
 - `Online`
 - `Initialization`
 - `Disabled`
@@ -73,7 +74,6 @@ If a log state has been corrupted, lost, or needs to be sharded to be maintainab
 
 This API is authenticated via [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).
 
-
 ```sh
 curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}' \
         	-H 'Content-Type: application/json' \
@@ -89,4 +89,4 @@ curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespa
   "audits_uri": "/namespaces/your.new.log.com/audits",
   "signature_version": 1
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/kv/api/delete-key-value-pairs.mdx b/src/content/docs/kv/api/delete-key-value-pairs.mdx
index f4275b10c635eef..e8173282815e34f 100644
--- a/src/content/docs/kv/api/delete-key-value-pairs.mdx
+++ b/src/content/docs/kv/api/delete-key-value-pairs.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
@@ -22,25 +22,24 @@ An example of deleting a key-value pair from within a Worker:
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    try {
-      await env.NAMESPACE.delete("first-key");
-
-      return new Response("Successful delete", {
-        status: 200
-      });
-    }
-    catch (e)
-    {
-      return new Response(e.message, {status: 500});
-    }
-  },
+	async fetch(request, env, ctx) {
+		try {
+			await env.NAMESPACE.delete("first-key");
+
+			return new Response("Successful delete", {
+				status: 200,
+			});
+		} catch (e) {
+			return new Response(e.message, { status: 500 });
+		}
+	},
 };
 ```
 
 ## Reference
 
 The following method is provided to delete from KV:
+
 - [delete()](#delete-method)
 
 ### `delete()` method
@@ -53,14 +52,13 @@ env.NAMESPACE.delete(key);
 
 #### Parameters
 
-* `key`: `string`
-  * The key to associate with the value.
+- `key`: `string`
+  - The key to associate with the value.
 
 #### Response
 
-* `response`: `Promise<void>`
-  * A `Promise` that resolves if the delete is successful.
-
+- `response`: `Promise<void>`
+  - A `Promise` that resolves if the delete is successful.
 
 This method returns a promise that you should `await` on to verify successful deletion. Calling `delete()` on a non-existing key is returned as a successful delete.
 
@@ -75,4 +73,5 @@ Delete more than one key-value pair at a time with Wrangler or [via the REST API
 The bulk REST API can accept up to 10,000 KV pairs at once. Bulk writes are not supported using the [KV binding](/kv/concepts/kv-bindings/).
 
 ## Other methods to access KV
+
 You can also [delete key-value pairs from the command line with Wrangler](/kv/reference/kv-commands/#kv-namespace-delete) or [with the REST API](/api/resources/kv/subresources/namespaces/subresources/values/methods/delete/).
diff --git a/src/content/docs/kv/concepts/kv-bindings.mdx b/src/content/docs/kv/concepts/kv-bindings.mdx
index 025824dc80e64ab..1710c1db27c0aad 100644
--- a/src/content/docs/kv/concepts/kv-bindings.mdx
+++ b/src/content/docs/kv/concepts/kv-bindings.mdx
@@ -52,14 +52,14 @@ With this, the deployed Worker will have a `TODO` field in their environment obj
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    // Get the value for the "to-do:123" key
-    // NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
-    let value = await env.TODO.get("to-do:123");
-
-    // Return the value, as is, for the Response
-    return new Response(value);
-  },
+	async fetch(request, env, ctx) {
+		// Get the value for the "to-do:123" key
+		// NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
+		let value = await env.TODO.get("to-do:123");
+
+		// Return the value, as is, for the Response
+		return new Response(value);
+	},
 };
 ```
 
@@ -97,13 +97,13 @@ An example might look like:
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-  constructor(ctx, env) {
-    super(ctx, env);
-  }
-
-  async fetch(request) {
-    const valueFromKV = await this.env.NAMESPACE.get("someKey");
-    return new Response(valueFromKV);
-  }
+	constructor(ctx, env) {
+		super(ctx, env);
+	}
+
+	async fetch(request) {
+		const valueFromKV = await this.env.NAMESPACE.get("someKey");
+		return new Response(valueFromKV);
+	}
 }
 ```
diff --git a/src/content/docs/kv/concepts/kv-namespaces.mdx b/src/content/docs/kv/concepts/kv-namespaces.mdx
index 7867efd8d6aaab6..0919c833f8ab666 100644
--- a/src/content/docs/kv/concepts/kv-namespaces.mdx
+++ b/src/content/docs/kv/concepts/kv-namespaces.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - kv
 ---
+
 import { Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 A KV namespace is a key-value database replicated to Cloudflare’s global network.
@@ -23,17 +24,14 @@ KV namespace IDs are public and bound to your account.
 
 To bind KV namespaces to your Worker, assign an array of the below object to the `kv_namespaces` key.
 
-* `binding` <Type text="string" /> <MetaInfo text="required" />
-
-  * The binding name used to refer to the KV namespace.
-
-* `id` <Type text="string" /> <MetaInfo text="required" />
+- `binding` <Type text="string" /> <MetaInfo text="required" />
+  - The binding name used to refer to the KV namespace.
 
-  * The ID of the KV namespace.
+- `id` <Type text="string" /> <MetaInfo text="required" />
+  - The ID of the KV namespace.
 
-* `preview_id` <Type text="string" /> <MetaInfo text="optional" />
-
-  * The ID of the KV namespace used during `wrangler dev`.
+- `preview_id` <Type text="string" /> <MetaInfo text="optional" />
+  - The ID of the KV namespace used during `wrangler dev`.
 
 Example:
 
@@ -59,6 +57,7 @@ To bind the namespace to your Worker in the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your **Worker**.
 3. Select **Settings** > **Bindings**.
 4. Select **Add**.
diff --git a/src/content/docs/kv/get-started.mdx b/src/content/docs/kv/get-started.mdx
index 1087ab11b86e2ce..2940849e4bb17a3 100644
--- a/src/content/docs/kv/get-started.mdx
+++ b/src/content/docs/kv/get-started.mdx
@@ -3,7 +3,7 @@ title: Getting started
 description: Create a KV namespace, write key-value pairs, and read data from Workers KV using Wrangler or the dashboard.
 pcx_content_type: get-started
 summary: |
-    Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
+  Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
 reviewed: 2025-05-19
 sidebar:
   order: 2
@@ -11,7 +11,18 @@ products:
   - kv
 ---
 
-import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem, WranglerConfig, GitHubCode, DashButton } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	FileTree,
+	Details,
+	Tabs,
+	TabItem,
+	WranglerConfig,
+	GitHubCode,
+	DashButton,
+} from "~/components";
 
 Workers KV provides low-latency, high-throughput global storage to your [Cloudflare Workers](/workers/) applications. Workers KV is ideal for storing user configuration data, routing data, A/B testing configurations and authentication tokens, and is well suited for read-heavy workloads.
 
diff --git a/src/content/docs/kv/glossary.mdx b/src/content/docs/kv/glossary.mdx
index 6b9c8f69e63c1a2..fca60dffa616ae9 100644
--- a/src/content/docs/kv/glossary.mdx
+++ b/src/content/docs/kv/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's KV documentation.
 
diff --git a/src/content/docs/kv/observability/index.mdx b/src/content/docs/kv/observability/index.mdx
index 9f1c8fd90be7853..8f1670df25b7b57 100644
--- a/src/content/docs/kv/observability/index.mdx
+++ b/src/content/docs/kv/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - kv
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/kv/observability/metrics-analytics.mdx b/src/content/docs/kv/observability/metrics-analytics.mdx
index c341d12aa8f4c3c..01ac3d93bddf26b 100644
--- a/src/content/docs/kv/observability/metrics-analytics.mdx
+++ b/src/content/docs/kv/observability/metrics-analytics.mdx
@@ -32,6 +32,7 @@ Per-namespace analytics for KV are available in the Cloudflare dashboard. To vie
 1. In the Cloudflare dashboard, go to the **Workers KV** page.
 
    <DashButton url="/?to=/:account/workers/kv/namespaces" />
+
 2. Select an existing namespace.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/kv/platform/pricing.mdx b/src/content/docs/kv/platform/pricing.mdx
index 2fbcd27b1c0dc52..e52462c5d821622 100644
--- a/src/content/docs/kv/platform/pricing.mdx
+++ b/src/content/docs/kv/platform/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="kv_pricing" product="workers" />
 
diff --git a/src/content/docs/kv/reference/data-security.mdx b/src/content/docs/kv/reference/data-security.mdx
index 56ffef1944f609a..5c00ce589165eee 100644
--- a/src/content/docs/kv/reference/data-security.mdx
+++ b/src/content/docs/kv/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of KV, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/kv/reference/environments.mdx b/src/content/docs/kv/reference/environments.mdx
index ef1e9305aea8aa3..dc41508ef498dcf 100644
--- a/src/content/docs/kv/reference/environments.mdx
+++ b/src/content/docs/kv/reference/environments.mdx
@@ -68,8 +68,6 @@ Specifying an environment with the optional `--env` flag allows you to publish W
 
 For example, you could use separate staging and production KV namespaces for KV data in your Wrangler file:
 
-
-
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/kv/reference/kv-commands.mdx b/src/content/docs/kv/reference/kv-commands.mdx
index 431cd3c20f17a6f..fe72655a36d9f3d 100644
--- a/src/content/docs/kv/reference/kv-commands.mdx
+++ b/src/content/docs/kv/reference/kv-commands.mdx
@@ -8,9 +8,9 @@ products:
   - kv
 ---
 
-import {Render} from "~/components"
+import { Render } from "~/components";
 
-<Render file="wrangler-commands/kv" product="workers"/>
+<Render file="wrangler-commands/kv" product="workers" />
 
 ## Deprecations
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
index e12e1fb27bbc69d..390d7d7727dc08f 100644
--- a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
@@ -5,7 +5,7 @@ pcx_content_type: overview
 sidebar:
   order: 5
   label: Audit Logs - v2
-  badge: 
+  badge:
     text: Beta
 description: Use the updated Audit Logs v2 interface.
 products:
diff --git a/src/content/docs/learning-paths/application-security/account-security/index.mdx b/src/content/docs/learning-paths/application-security/account-security/index.mdx
index cb51b549f91cf51..8bd856a5fcab2d3 100644
--- a/src/content/docs/learning-paths/application-security/account-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/index.mdx
@@ -18,6 +18,6 @@ Make sure your account's security basics are configured properly.
 
 By the end of this module, you will be able to:
 
-* Secure your account
-* Understand and configure the most common settings for Cloudflare's Application Security Products
-* Explore advanced security products such as Bot Management and API Protection
+- Secure your account
+- Understand and configure the most common settings for Cloudflare's Application Security Products
+- Explore advanced security products such as Bot Management and API Protection
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
index 7b0bddc7ba7917f..040aa06f0220922 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="account-manage-active-sessions" product="fundamentals" />
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
index 808ba2c05ca7dad..f58aa925b394692 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 :::note
 Audit Logs version 2 is available in beta. Refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/) for more details.
diff --git a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
index 29a6b9e44022824..f7846d7a368fa45 100644
--- a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
@@ -12,11 +12,11 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="2fa-overview" product="support" />
 
-***
+---
 
 ## Enable 2FA
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
index 2f7bec4ece18e95..d9d1cae9beaab73 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="bic-description" product="waf" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
index 6358ef403930629..33a0732d1aa3a3e 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
@@ -12,10 +12,10 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare automatically detects and mitigates DDoS attacks using its [Autonomous Edge](/ddos-protection/about/components/#autonomous-edge), which is always-on. `Advanced` protections are reserved for Magic Transit customers.
 
 <Render file="ddos-attack-coverage" product="ddos-protection" />
 
-Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/)  to dive deeper into this subject.
+Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/) to dive deeper into this subject.
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
index d3c76bce71f7ce2..636464957d64e91 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="dnssec-definition" product="dns" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
index f9c577f4d3368d9..5432c5e8c039ee4 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
@@ -18,4 +18,4 @@ As soon as you onboard your domain to Cloudflare, you are automatically protecte
 
 By the end of this module, you will be able to:
 
-* Understand the most common security controls your applications will have access to
+- Understand the most common security controls your applications will have access to
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
index a68ec976eb10fae..3d460f58056b631 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Mutual TLS (mTLS) authentication uses client certificates to ensure traffic between client and server is bidirectionally secure and trusted. mTLS also allows requests that do not authenticate via an identity provider — such as Internet-of-things (IoT) devices — to demonstrate they can reach a given resource.
 
diff --git a/src/content/docs/learning-paths/application-security/firewall/index.mdx b/src/content/docs/learning-paths/application-security/firewall/index.mdx
index 6ee96f14dba91e6..78fffa803dc49c0 100644
--- a/src/content/docs/learning-paths/application-security/firewall/index.mdx
+++ b/src/content/docs/learning-paths/application-security/firewall/index.mdx
@@ -18,5 +18,5 @@ Cloudflare's Web Application Firewall (WAF) is used to protect websites from a w
 
 By the end of this module, you will be able to:
 
-* Understand the different WAF components that Cloudflare offers
-* Understand the main features within each WAF offering
+- Understand the different WAF components that Cloudflare offers
+- Understand the main features within each WAF offering
diff --git a/src/content/docs/learning-paths/application-security/lists/configuration.mdx b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
index 0a7cc2639adf13f..de13360e165d887 100644
--- a/src/content/docs/learning-paths/application-security/lists/configuration.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Both Custom and Managed Lists are located in the account settings. Refer to [Features by plan type](/learning-paths/application-security/lists/features/) for more information on plan eligibility.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/features.mdx b/src/content/docs/learning-paths/application-security/lists/features.mdx
index 96704045ef785d4..4ea1c31ecbdd63e 100644
--- a/src/content/docs/learning-paths/application-security/lists/features.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { FeatureTable, Render } from "~/components"
+import { FeatureTable, Render } from "~/components";
 
 List availability varies according to the list type and your Cloudflare plan and subscriptions.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/index.mdx b/src/content/docs/learning-paths/application-security/lists/index.mdx
index 5278a33aaa568ba..852a5c8744856ab 100644
--- a/src/content/docs/learning-paths/application-security/lists/index.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/index.mdx
@@ -14,12 +14,12 @@ products:
 
 Cloudflare Lists is a WAF feature that enables administrators to groups identifiers together, such as IPs, hostnames or ASNs, and reference the list by other Cloudflare products such as [Custom rules](/waf/custom-rules/). Cloudflare currently supports the following types of lists:
 
-* [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
-* [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
+- [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
+- [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Understand all the options Cloudflare's Lists products offer
-* Understand the advanced configurations provided to you with a paid offering
+- Understand all the options Cloudflare's Lists products offer
+- Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
index b14eddd109c6d34..9823a3c2fca778d 100644
--- a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
index ceee8008c0ec64e..21914e63f80aefc 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
@@ -14,14 +14,14 @@ products:
 
 Let's step through an example. If your `/create-account` page is being attacked, you will create a rule to limit the amount of requests, per `counting characteristic`, that you feel comfortable permitting through to your origin.
 
-The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, *after* 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
+The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, _after_ 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
 
-***
+---
 
 ![rate-limiting-create-account-endpoint](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint.png)
 ![rate-limiting-create-account-endpoint-block](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint-block.png)
 
-***
+---
 
 ## Advanced configuration
 
@@ -29,14 +29,14 @@ In the previous module, we reviewed the various configurations available per pla
 
 The rule below is being created on the `enterprise` plan, so we are no longer limited to default configurations.
 
-* The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
-* Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
-* Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
-* Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
+- The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
+- Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
+- Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
+- Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
 
 ![rate-limiting-advanced-config-1](~/assets/images/waf/rate-limiting-rules/rl-advanced-config.png)
 
-***
+---
 
 ## Best practices
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
index 21aa7c300cdb961..606b48b86302118 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Rate limiting is composed of the following parameters:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
index 75a9a0e25347d72..45270f5ec40f21e 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
@@ -18,5 +18,5 @@ Rate Limiting mitigates excessive request rates for specific URLs or for an enti
 
 By the end of this module, you will be able to:
 
-* Understand all the options Cloudflare's Rate Limiting product offers
-* Understand the advanced configurations provided to you with a paid offering
+- Understand all the options Cloudflare's Rate Limiting product offers
+- Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
index 7eb7c2accedce4b..81787364edb5b8b 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
index 06d7cf0e3aa85f1..2533b2fabe4489e 100644
--- a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="brand-protection-definition" product="security-center" />
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/index.mdx b/src/content/docs/learning-paths/application-security/security-center/index.mdx
index 3c114e0c0f9d8d6..443cd3864fd9da6 100644
--- a/src/content/docs/learning-paths/application-security/security-center/index.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/index.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="security-center-definition" product="security-center" />
 
@@ -20,5 +20,5 @@ import { Render } from "~/components"
 
 By the end of this module, you will be able to:
 
-* Understand the primary Security Center features such as Security Insights and Brand Protection
-* Review and manage security risks at the account level, encompassing all of your domains in one unified view
+- Understand the primary Security Center features such as Security Insights and Brand Protection
+- Review and manage security risks at the account level, encompassing all of your domains in one unified view
diff --git a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
index 54e046c2db79eed..9ce422510bb4427 100644
--- a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
@@ -16,7 +16,7 @@ Now that you have [connected your private applications](/learning-paths/clientle
 
 By the end of this module, you will be able to:
 
-* Add your application to Cloudflare Access.
-* Create an Access policy.
-* Design reusable policies.
-* Design a domain structure for your applications.
+- Add your application to Cloudflare Access.
+- Create an Access policy.
+- Design reusable policies.
+- Design a domain structure for your applications.
diff --git a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
index 38a2051d7e24d98..5450985227dcb8e 100644
--- a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
@@ -16,7 +16,7 @@ Configure advanced Access policies to meet the specific requirements of your app
 
 By the end of this module, you will be able to:
 
-* Check identity-based attributes that are not directly supported by the Access policy builder.
-* Deliver sensitive web applications in an isolated browser.
-* Apply Gateway HTTP policies without a device client.
-* Connect to applications using their private hostnames without a device client.
+- Check identity-based attributes that are not directly supported by the Access policy builder.
+- Deliver sensitive web applications in an isolated browser.
+- Apply Gateway HTTP policies without a device client.
+- Connect to applications using their private hostnames without a device client.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
index 700dfb2c429be48..ba3876cbb069c62 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
@@ -27,6 +27,6 @@ To configure Clientless Web Isolation to augment clientless access, refer to [th
 
 ## Best practices
 
-* For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
-* If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
-* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
+- For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
+- If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
+- You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
index 236369d2c8ea5d8..3d6978794492877 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
@@ -10,10 +10,10 @@ products:
   - cloudflare-one
 ---
 
-As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access.  However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
+As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access. However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Connect to private web applications using their private hostnames.
+- Connect to private web applications using their private hostnames.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
index 1c76266d3e00159..96467fa3ad74ab3 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
@@ -16,4 +16,4 @@ Review the concepts behind clientless access.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose and benefits of clientless access.
\ No newline at end of file
+- Understand the purpose and benefits of clientless access.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
index 446f1e1c72913e7..9b3e4a2a40a5b80 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
@@ -12,7 +12,7 @@ products:
 
 Clientless access is a deployment option of a [Zero Trust Network Access (ZTNA)](https://www.cloudflare.com/learning/access-management/what-is-ztna/) service that provides secure access to internal applications without requiring end users to install any software. Users access corporate resources like intranet web apps, SSH terminals, and Windows servers through RDP from their web browser. Clientless access is commonly used to provide internal, [least-privilege access](https://www.cloudflare.com/learning/access-management/principle-of-least-privilege/) to users on unmanaged devices. Users may include third-party contractors, suppliers, and partners, or employees using personal mobile phones as part of an organization's bring-your-own-device (BYOD) policy.
 
-IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as  preventing uploads/downloads or copy/paste, or incorporating DLP policies.
+IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as preventing uploads/downloads or copy/paste, or incorporating DLP policies.
 
 ## Alternatives to clientless access
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
index 7015fc5b6c802b5..7eb4c09d0ecbf01 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
@@ -20,9 +20,9 @@ For an additional point of availability, add a [`cloudflared` replica](/cloudfla
 
 To make your applications easier to manage, standardize the public hostnames that you publish your applications on. Here are a few examples of how customers manage their public hostnames:
 
-* Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
-* If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
-* Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
+- Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
+- If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
+- Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
 
 ## Disable TLS verification
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
index 3120d43f30efdce..9c6cbcd138686f2 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To enable clientless access to your applications, you will need to create a Cloudflare Tunnel that publishes applications to a domain on Cloudflare. A published application creates a public DNS record that routes traffic to a specific address, protocol, and port associated with a private application. For example, you can define a public hostname (`mywebapp.example.com`) to provide access to a web server running on `https://localhost:8080`. When a user goes to `mywebapp.example.com` in their browser, their request will first route to a Cloudflare data center where it is inspected against your configured security policies. Cloudflare will then forward validated requests down your tunnel to the web server.
 
@@ -32,9 +32,8 @@ All users on the Internet can now connect to this application via its public hos
 
 If the tunnel is disconnected:
 
-* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
-
+- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
 
 :::
 
@@ -42,5 +41,5 @@ If the tunnel is disconnected:
 
 For more control over how traffic routes through your tunnel, refer to the following links:
 
-* [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
-* [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
+- [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
+- [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
index fe443c8a8e5c306..4f9337b3961247c 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
@@ -16,5 +16,5 @@ Cloudflare Tunnel allows you to securely connect your applications to Cloudflare
 
 By the end of this module, you will be able to:
 
-* Create a Cloudflare Tunnel.
-* Publish your application via a public hostname.
+- Create a Cloudflare Tunnel.
+- Publish your application via a public hostname.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
index 49e6a3bcf50f75b..a14fda563a6432d 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/app-launcher" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
index 3f202ae036ff2e9..3de4f9ba2ef5141 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/block-page" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
index 23e9d4431ca5719..6a740a977e9de4c 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/bookmarks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
index 681cb50fbfb8882..01df3d80b023dd8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
@@ -16,7 +16,7 @@ Cloudflare Access offers several ways to customize the look and feel of the user
 
 By the end of this module, you will be able to:
 
-* Configure the App Launcher so that users can open all applications from single dashboard.
-* Add bookmarks to the App Launcher for applications that are not behind Access.
-* Customize the Access login page with your organization's branding.
-* Display custom block pages when a user is blocked by your Access policies.
+- Configure the App Launcher so that users can open all applications from single dashboard.
+- Add bookmarks to the App Launcher for applications that are not behind Access.
+- Customize the Access login page with your organization's branding.
+- Display custom block pages when a user is blocked by your Access policies.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
index 0784ac3db460bb8..b04f07439a4c9c8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The Access login page is where users select their identity provider (IdP) or One-Time PIN prior to accessing the application. Customers who only use one IdP usually enable **Apply instant authentication** for their applications, which redirects end users directly to the SSO login page. If you are using multiple IdPs, we recommend customizing the Access login page to match your branding and minimize user confusion.
 
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
index 6b8b7f8ee3ace2f..65bd38ce4da91e9 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
index bf6be752e98fce7..0348346f1053ba1 100644
--- a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
@@ -18,7 +18,7 @@ If you need to deliver access to non-browser based applications, refer to our co
 
 By the end of this module, you will be able to:
 
-* Set up a Cloudflare account.
-* Add your domain to Cloudflare.
-* Create a Zero Trust organization to manage applications and policies.
-* Configure an identity provider (IdP) for user authentication.
+- Set up a Cloudflare account.
+- Add your domain to Cloudflare.
+- Create a Zero Trust organization to manage applications and policies.
+- Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
index 238af10cab095cb..f519cc3082b5669 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
@@ -12,10 +12,10 @@ products:
 
 Most customers have a heterogeneous private application portfolio; some are home-built, some are internal managed services, some have SSO integrations available, and some rely on HTML or other forms of authentication. With that in mind, we recommend that you mix-and-match [onboarding solutions](/learning-paths/clientless-access/migrate-applications/integrated-sso/#potential-solutions) to fit the needs of each individual application. As shown in the table below, you can bucket applications into a series of stack-ranked categories that prioritize ease of implementation and total organizational impact.
 
-| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                             | Outcome                                                                                                                                                                                                                                                      |
-| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                     |
-| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                             |
-| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                     |
-| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.      | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
-| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                                                            | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                                                |
+| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                         | Outcome                                                                                                                                                                                                                                                  |
+| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                 |
+| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                         |
+| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                 |
+| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.          | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
+| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                             | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                 |
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
index 87fd2e5aafa3f63..9221ff52404a5f0 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
@@ -21,6 +21,6 @@ The remaining modules (Modules 6-9) discuss special considerations and setup opt
 
 By the end of this module, you will be able to:
 
-* Manage applications that are directly integrated with an identity provider.
-* Pass user information from Cloudflare Access to your application.
-* Review best practices for onboarding different types of internal applications.
+- Manage applications that are directly integrated with an identity provider.
+- Pass user information from Cloudflare Access to your application.
+- Review best practices for onboarding different types of internal applications.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
index 05491e91bbf7537..237820c4e1c9ca7 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
@@ -31,12 +31,12 @@ app.internal.com")
 
 If your applications use integrated SSO, there are a number of different paths you can take to onboard your applications to Cloudflare Access.
 
-| Solution                                                                                                                       | Steps required                                                                                                     | Pros                                                                                                                                                                        | Cons                                                                                                                     |
-| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                                | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                        | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
-| Present applications on existing internal domains with identical external domains delegated to Cloudflare                      | Add domains to Cloudflare that match internal domains                                                              | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
-| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li> | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
-| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                       | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/)           | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
+| Solution                                                                                                                   | Steps required                                                                                                      | Pros                                                                                                                                                                        | Cons                                                                                                                     |
+| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                            | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                         | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
+| Present applications on existing internal domains with identical external domains delegated to Cloudflare                  | Add domains to Cloudflare that match internal domains                                                               | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
+| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li>  | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
+| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                   | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/) | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
 
 ## Recommended solution
 
diff --git a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
index 7412e5a55b1652c..596225f3171052b 100644
--- a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
@@ -16,4 +16,4 @@ Integrate Cloudflare Access into your private application development pipeline.
 
 By the end of this module, you will be able to:
 
-* Publish internal applications to Cloudflare using Terraform.
+- Publish internal applications to Cloudflare using Terraform.
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
index 69453ef2d875700..1e092ce574856b2 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
@@ -11,7 +11,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To set up a Zero Trust organization:
 
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
index 721649155e70883..c0853f8ed750a7f 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
@@ -16,6 +16,6 @@ Get started by creating a Cloudflare account and initializing the Zero Trust and
 
 By the end of this module, you will have:
 
-* Created a Cloudflare account.
-* Initialized the Zero Trust dashboard.
-* Initialized the Area 1 dashboard.
+- Created a Cloudflare account.
+- Initialized the Zero Trust dashboard.
+- Initialized the Area 1 dashboard.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
index 098f42bdf6a93f6..c6dc2bacee257d2 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
@@ -16,7 +16,7 @@ Learn the technical concepts behind Project Cybersafe Schools.
 
 By the end of this module, you will be able to:
 
-* Understand the purpose of the Children’s Internet Protection Act (CIPA).
-* Describe the life of a DNS request.
-* Explain how DNS filtering works to control which websites users can access.
-* Understand the benefits of protecting your email inbox.
+- Understand the purpose of the Children’s Internet Protection Act (CIPA).
+- Describe the life of a DNS request.
+- Explain how DNS filtering works to control which websites users can access.
+- Understand the benefits of protecting your email inbox.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
index af663840fbd1be0..c7e8ff61a49fecf 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
@@ -16,9 +16,9 @@ DNS filtering is a technique to block access to websites or online content. DNS
 
 DNS filtering is commonly used to:
 
-* Protect school data from phishing, ransomware, and malware.
-* Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
-* Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
+- Protect school data from phishing, ransomware, and malware.
+- Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
+- Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
 
 ## How DNS filtering works
 
@@ -52,17 +52,17 @@ DNS filtering only applies to the hostname — `subdomain.domain.tld`. You canno
 
 Secure Web Gateways (SWGs) offer a greater set of capabilities, including:
 
-* [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
-* L4 firewalls to block ports and protocols
-* Antivirus scanning
-* [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
-* [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
+- [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
+- L4 firewalls to block ports and protocols
+- Antivirus scanning
+- [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
+- [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
 
 However, this can make SWGs more complex to deploy. Therefore, many organizations will start with DNS filtering as an initial layer of defense against Internet threats.
 
 ## Related resources
 
-* For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
+- For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
 
 ## Next steps
 
diff --git a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
index 75e5801177a4b47..c3c1b8bad4a14a0 100644
--- a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
+++ b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
@@ -10,8 +10,12 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To verify that your DNS traffic is sent to Gateway:
 
-<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
+<Render
+	file="gateway/verify-connectivity"
+	product="cloudflare-one"
+	params={{ one: "DNS", two: "queries" }}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
index b47b3a80514a788..eb3666dd5133b61 100644
--- a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
@@ -11,4 +11,4 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="magic-transit/advertise-prefixes"	product="networking-services" />
\ No newline at end of file
+<Render file="magic-transit/advertise-prefixes" product="networking-services" />
diff --git a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
index 6d99098e5ffbd39..49959caa851cad4 100644
--- a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
@@ -14,6 +14,6 @@ Learn core concepts about Magic Transit and its functionality, in order to prote
 ## Objectives
 
 By the end of this module you will be able to:
+
 - Understand what Magic Transit is
 - Why you should use it to protect your IP network
-
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
index 96178b835574113..a62c27d80ec53ce 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare DDoS protection automatically detects and mitigates Distributed Denial of Service (DDoS) attacks using its Autonomous Edge. Magic Transit customers have access to additional features, such as:
 
@@ -26,7 +26,10 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/tcp-protection-intro" product="ddos-protection" />
 
-<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
+<Render
+	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
+	product="ddos-protection"
+/>
 
 #### Setup
 
@@ -36,8 +39,11 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/dns-protection-intro" product="ddos-protection" />
 
-<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
+<Render
+	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
+	product="ddos-protection"
+/>
 
 #### Setup
 
-<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
\ No newline at end of file
+<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
index 482c2b215ae173f..51c5f4f2f692123 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -19,12 +19,16 @@ import { Render } from "~/components"
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT:
+			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table"
+		routingTableName: "Magic Transit Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
index 4c93f4789229aab..bd53e3d65b54e92 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
@@ -11,22 +11,31 @@ products:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
-	}} />
\ No newline at end of file
+		unifiedRoutingURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
+	}}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
index 6f1888d2fbbff7e..b98f8551ad40475 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
@@ -14,6 +14,6 @@ In this unit you will learn how to set up tunnels and routes to steer traffic.
 ## Objectives
 
 By the end of this module you will be able to:
+
 - Create tunnels on both the Cloudflare side and your router side to connect to your infrastructure.
 - Configure static routes or dynamic routes with BGP peering to steer your traffic via next-hop from Cloudflare's global network to your connected networks.
-
diff --git a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
index 1efb22a01b5feef..40adf54d7baae5f 100644
--- a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
@@ -17,7 +17,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation:
+			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
@@ -32,4 +33,4 @@ Cloudflare also recommends that you enable the following account notifications f
 - (Optional) Advanced Layer 3/4 DDoS Attack Alert
 - (Optional) Cloudflare status - Maintenance Notification (in case you want to be alerted regarding maintenance in specific Cloudflare data centers).
 
-Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
\ No newline at end of file
+Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
diff --git a/src/content/docs/learning-paths/data-center-protection/get-started.mdx b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
index 58e23aba7e9451b..16b63ff273ced89 100644
--- a/src/content/docs/learning-paths/data-center-protection/get-started.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
@@ -9,6 +9,10 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Learning Path" }} />
\ No newline at end of file
+<Render
+	file="magic-transit/get-started"
+	product="networking-services"
+	params={{ magicWord: "Learning Path" }}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
index 7d6e4bdd8b5ba93..88f72d32072ad16 100644
--- a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
@@ -10,6 +10,7 @@ products:
 ---
 
 After setting up your Magic Transit product, Cloudflare validates:
+
 - Tunnel connectivity
 - Tunnel and endpoint [health checks](/magic-transit/reference/tunnel-health-checks/#types-of-health-checks)
 - Letter of Agency (LOA)
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
index 4b7ab7651839800..efe4d0f80aa7a93 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
@@ -14,7 +14,7 @@ Migrating your DNS from an on-premises BIND solution to a cloud-based provider l
 
 By the end of this module, you will be able to:
 
-* Plan and take inventory of your DNS migration.
-* Prepare for the migration with minimal downtime.
-* Learn how to make the actual switch to Cloudflare.
-* Verify and stabilize after your migration.
+- Plan and take inventory of your DNS migration.
+- Prepare for the migration with minimal downtime.
+- Learn how to make the actual switch to Cloudflare.
+- Verify and stabilize after your migration.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
index 05eae75787849b0..ac9f126e6cfb046 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
@@ -12,55 +12,55 @@ Detailed planning is the cornerstone of a successful DNS migration.
 
 ## 1. Understand your current BIND setup
 
-1. Identify all DNS zones currently hosted on your BIND servers.  
-2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.  
-3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.  
-   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.  
+1. Identify all DNS zones currently hosted on your BIND servers.
+2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.
+3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.
+   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.
    - For policy-based internal DNS, consider Cloudflare Zero Trust features such as DNS policies and Internal DNS (Beta). For more details, refer to [Cloudflare DNS](/dns/) and [Internal DNS](/dns/internal-dns/).
-4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:  
-   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.  
-   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.  
-   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:  
-      - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)  
-      - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)  
+4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:
+   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.
+   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.
+   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:
+     - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)
+     - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)
 
-      These setups document how to restrict which IP addresses can perform zone transfers.
+     These setups document how to restrict which IP addresses can perform zone transfers.
 
-5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.  
+5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.
 
 ## 2. Define scope and objectives
 
-Clearly list all domain names to be migrated and define success criteria for the migration.  
+Clearly list all domain names to be migrated and define success criteria for the migration.
 
 ## 3. Cloudflare account and familiarization
 
-1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.  
-2. Familiarize yourself with the Cloudflare DNS dashboard and its features.  
+1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.
+2. Familiarize yourself with the Cloudflare DNS dashboard and its features.
 3. Consider the different [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) you can manage on Cloudflare and how they map from BIND.
 
 ## 4. DNSSEC strategy (critical)
 
-Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.  
+Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.
 
-Cloudflare supports two main migration approaches when DNSSEC is enabled: 
+Cloudflare supports two main migration approaches when DNSSEC is enabled:
 
-   - Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.  
-   - Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).  
+- Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.
+- Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
-**Disable-and-re-enable approach (safer for most teams):**  
+**Disable-and-re-enable approach (safer for most teams):**
 
-1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.  
-2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.  
+1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.
+2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.
 
-*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.  
+\*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.
 
 For more information about DNSSEC on Cloudflare, refer to [DNSSEC](/dns/dnssec/).
 
 ## 5. Choose migration window
 
-Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.  
+Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.
 
 ## 6. Develop communication and rollback plan
 
-- Communication: Plan how to communicate with stakeholders before, during, and after the migration.  
-- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
\ No newline at end of file
+- Communication: Plan how to communicate with stakeholders before, during, and after the migration.
+- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
index f53af665ca87cfd..b3b2d045d7021ec 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
@@ -14,49 +14,49 @@ Careful preparation will minimize downtime and issues during the cutover.
 
 ## 1. Reduce DNS record TTLs (Time To Live)
 
-At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).  
+At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).
 
-This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.  
+This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.
 
-- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).  
+- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).
 
 ## 2. Export zone files from BIND
 
-Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.  
+Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.
 
 ## 3. Add domains to Cloudflare
 
-1. Log in to your Cloudflare dashboard.  
+1. Log in to your Cloudflare dashboard.
 
    <DashButton url="/?to=/:account/home" />
 
-2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.  
+2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.
 
 ## 4. Import DNS Records into Cloudflare
 
-Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.  
-   
-   <DashButton url="/?to=/:account/home" />
+Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.
+
+<DashButton url="/?to=/:account/home" />
 
-- Verification (Crucial): 
-   - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.  
-   - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.  
-   - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).  
-- Proxy status (orange vs grey cloud):  
-   - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.  
-   - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).  
-   - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
+- Verification (Crucial):
+  - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.
+  - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.
+  - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).
+- Proxy status (orange vs grey cloud):
+  - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.
+  - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).
+  - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
 
 ## 5. DNSSEC preparation (if currently enabled)
 
-Complete this step before you change your nameservers at the registrar.  
+Complete this step before you change your nameservers at the registrar.
 
 :::note
 
-For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy,  refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
 :::
 
-- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.  
+- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.
 - **Wait for DS TTL:** Wait at least the full DS record TTL published at the parent zone, and preferably up to 1.5 times that TTL, before you change nameservers. This ensures that validating resolvers stop expecting the old DNSSEC chain. The typical TTL duration for DS records is set to +24 hours (86,400 seconds).
-- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.  
+- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
index 7307e676b28660a..1decb20de5cda62 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
@@ -12,30 +12,29 @@ Phase 3 is when you make the actual switch to Cloudflare.
 
 ## 1. Final verification
 
-Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.  
+Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.
 
 ## 2. Update nameservers at your registrar
 
-   1. Log in to your domain registrar's control panel for each domain.  
-   2. Navigate to the section for managing nameservers.  
-   3. Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.  
-   4. Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).  
-   5. Save the changes.  
+1.  Log in to your domain registrar's control panel for each domain.
+2.  Navigate to the section for managing nameservers.
+3.  Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.
+4.  Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).
+5.  Save the changes.
 
 ## 3. Monitor propagation
 
-- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).  
-- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.  
-   - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)  
-   - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
-   - `whois yourdomain.com`
-   - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
-   
-   You are looking for the Cloudflare nameservers to be reported consistently. 
+- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).
+- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.
+  - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)
+  - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
+  - `whois yourdomain.com`
+  - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
+  You are looking for the Cloudflare nameservers to be reported consistently.
 
 ## 4. Initial testing
 
 Once propagation appears to be widespread, perform basic resolution tests for critical records (for example, your website's `A` record and any `MX` records, if you had them set up).
 
-- `dig yourdomain.com A +short`  
-- `dig yourdomain.com MX +short`
\ No newline at end of file
+- `dig yourdomain.com A +short`
+- `dig yourdomain.com MX +short`
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
index e1f0d1f96eb1bac..e08e73b597e57b0 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
@@ -14,47 +14,49 @@ After the cutover, verify and stabilize.
 
 ## 1. Thorough testing and validation
 
-1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.  
-2. Test from different networks and geographical locations if possible.  
-3. Monitor application logs for any DNS-related errors.  
+1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.
+2. Test from different networks and geographical locations if possible.
+3. Monitor application logs for any DNS-related errors.
 
 ## 2. Enable DNSSEC in Cloudflare (if disabled earlier)
 
 Enable DNSSEC only after you are confident that DNS is resolving correctly through Cloudflare and that nameserver changes have fully propagated. In practice, plan for at least one full DS TTL after you add new DS records at the registrar.
 
-**Action in Cloudflare:**  
-   1. In the Cloudflare dashboard, go to your zone's **DNS Settings**.  
+**Action in Cloudflare:**
 
-      <DashButton url="/?to=/:account/:zone/dns/settings" />
+1.  In the Cloudflare dashboard, go to your zone's **DNS Settings**.
 
-   2. Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details. 
- 
-**Action at registrar:**  
-   1. Log in to your domain registrar.  
-   2. Navigate to the DNSSEC management section for your domain.  
-   3. Add the `DS` record details provided by Cloudflare.  
+    <DashButton url="/?to=/:account/:zone/dns/settings" />
+
+2.  Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details.
+
+**Action at registrar:**
+
+1.  Log in to your domain registrar.
+2.  Navigate to the DNSSEC management section for your domain.
+3.  Add the `DS` record details provided by Cloudflare.
 
 After adding the `DS` record, allow time for propagation and then validate your configuration with tools such as [DNSViz](https://dnsviz.net) or [Verisign's DNSSEC debugger](https://dnssec-debugger.verisignlabs.com/). For more information, refer to [DNSSEC](/dns/dnssec/).
 
-   :::note
-    If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
-   :::
+:::note
+If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
+:::
 
 ## 3. Adjust TTLs in Cloudflare
 
-After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).  
+After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).
 
 Higher TTLs improve resolver cache efficiency and can reduce latency by allowing recursive resolvers to reuse cached answers for longer, at the cost of slower propagation when you make changes.
 
 ## 4. Review and enable Cloudflare proxy features
 
-If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.  
+If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.
 
 ## 5. Decommission On-Prem BIND servers
 
 Only after a significant stabilization period (for example, several days to a week after full propagation and successful testing) and when you are fully confident in the Cloudflare setup, decommission the on-premise BIND servers.
 
-Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.   
+Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.
 
 ## 6. Update internal documentation and monitoring
 
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
index 8e23617d11caed2..5d966db6e4f2e51 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
@@ -8,15 +8,15 @@ products:
   - dns
 ---
 
-- Plan meticulously: Do not rush the planning and preparation phases.  
-- Communicate clearly: Keep stakeholders informed.  
-- Lower TTLs in advance: This is crucial for a faster cutover.  
-- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.  
-- Verify, verify, verify: Double-check record imports and functionality at each stage.  
-- Test thoroughly: From multiple locations and for all critical services.  
-- Have a rollback plan: Know how to revert if necessary.  
-- Migrate during low traffic: Minimize potential user impact.  
-- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.  
+- Plan meticulously: Do not rush the planning and preparation phases.
+- Communicate clearly: Keep stakeholders informed.
+- Lower TTLs in advance: This is crucial for a faster cutover.
+- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.
+- Verify, verify, verify: Double-check record imports and functionality at each stage.
+- Test thoroughly: From multiple locations and for all critical services.
+- Have a rollback plan: Know how to revert if necessary.
+- Migrate during low traffic: Minimize potential user impact.
+- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.
 - Take advantage of Cloudflare features: Once stable, explore and implement Cloudflare's security and performance enhancements.
 
-By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
\ No newline at end of file
+By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
index 13c9e675861f17d..a1bed2340a8f735 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
@@ -12,4 +12,3 @@ products:
   - dlp
   - casb
 ---
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
index 4f342e9997e31ea..776126418ebd729 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
@@ -20,4 +20,3 @@ The goal of this learning path is to provide Cloudflare One users with the strat
 - Monitor AI usage: Utilize Cloudflare One's tools, such as the Shadow IT dashboard and API CASB integrations, to gain visibility into both sanctioned and unsanctioned AI application usage.
 - Build security policies: Create granular security policies using Cloudflare Gateway to control AI usage, prevent data loss with DLP, and manage user behavior through actions like blocking or redirecting.
 - Secure sanctioned models: Apply Zero Trust principles to sanctioned AI models and internal services like Model Context Protocol (MCP) servers to ensure secure access and protect sensitive data from being exposed.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
index c8811b8737b69c2..29330ef6e90787c 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
@@ -22,4 +22,3 @@ MCP uses a client-server architecture where an AI agent acts as the client and s
 ## What are the security concerns with MCP?
 
 MCP doesn't have native authentication, authorization, or encryption. Because it functions similarly to an API, many of the same security considerations apply. If developers do not proactively implement security measures like Transport Layer Security (TLS) and rate limiting, MCP servers can be vulnerable to attacks, data leaks, and unauthorized access. Organizations must ensure that they validate inputs and protect confidential data to secure their MCP implementations.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
index 1d18a0ebba41b16..97b3651ba7daa5d 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
@@ -18,4 +18,3 @@ Shadow AI is the use of any AI tool or application by employees without the form
 Since it may not be feasible to eliminate all instances of shadow AI, organizations can manage the risks by taking a balanced approach. First, it is essential to foster collaboration and open communication between IT and other departments to understand why employees are using these tools. Next, implement guardrails by developing a flexible governance framework with clear guidelines on which types of AI systems can be used and how sensitive information should be handled. Finally, monitor AI usage with network tools to track what is being used and educate employees on the risks of unauthorized AI.
 
 To combat the risks associated with shadow AI, Cloudflare's API-driven CASB integrates with SaaS applications and cloud environments to scan for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
index f98c47c842d9d81..2f4c30d5cb527a1 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
@@ -16,4 +16,4 @@ To use the recommended AI security solutions in this learning path, you will nee
 
 :::note
 If you are new to securing your Internet traffic, refer to [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/) to get started and then return to this learning path to continue securing your organizations.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
index 67b07408d9070cd..7b68b9d51991f49 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
@@ -17,6 +17,7 @@ Before you can secure AI, you need to understand your organization's goals and c
 The level of risk you are willing to accept will determine how quickly you need to act and how deeply you need to implement security measures. Your specific concerns will then guide the exact security approaches you take to monitor and control AI usage.
 
 To begin, consider these questions to help shape your strategy:
+
 - Sanctioned versus shadow AI: Are your employees already using approved AI services, or are you primarily concerned with shadow AI — unapproved applications that may pose a risk? Note: Some approved vendors may offer embedded AI functionality. Consider whether those AI services are a risk, too.
 - Data sensitivity: What types of sensitive data do you currently monitor, classify, and protect? This will help you identify what you need to safeguard when employees interact with AI. If you have not determined this yet, refer to [Define your sensitive data](/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention/#define-your-sensitive-data) to learn more.
 - Encouraging user behavior: Do you want to encourage or limit user engagement with AI? How much do you expect your employees to use AI in a controlled, sanctioned way?
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
index b5caf20d92a283f..d466618622bbdb9 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
@@ -16,4 +16,4 @@ Businesses are eager to realize the potential boosts to productivity and efficie
 
 IT and security leaders are often asked to address risks and deal with increasing challenges like the use of shadow AI before they have an AI security strategy.
 
-Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively. 
+Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
index 48c3654da15b283..5edae280f6bbf30 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
@@ -17,4 +17,3 @@ Monitoring AI usage is one of the first steps in assessing holistic risk. Cloudf
 After you begin to understand your organization's AI usage, you should develop a balanced perspective on what constitutes sanctioned use of a tool. A good practice is to review applications in phases and then apply security policies based on those phases. For example, you can apply different security policies to applications that are considered approved, unapproved, unreviewed, or in review until they pass your corporate security standards and data privacy reviews.
 
 This section will detail options for assessing and understanding that risk by using inline (client) and out-of-band (API CASB) based methods.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
index 38cfd98df28c2ac..18a65bd00076557 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
@@ -13,10 +13,11 @@ products:
 ---
 
 When you enable [TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/#turn-on-tls-decryption), you can review the prompts and responses for supported AI applications. This allows you to understand three key things about AI application usage:
+
 - The sanctioned and unsanctioned AI tools your users are engaging with.
 - How they are interacting with them.
 - What information they are sharing.
 
 ![Log entry for a prompt detected using AI prompt protection.](~/assets/images/learning-paths/holistic-ai-security/gateway-prompt-log.png)
 
-You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
\ No newline at end of file
+You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
index c60e183df9211b9..aacf8456e79fe1c 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
@@ -20,7 +20,6 @@ To review how your organization uses AI apps, start with the Cloudflare [Shadow
 
 ![Shadow IT dashboard showing utilization of application statuses (Approved, Unapproved, In Review, Unreviewed).](~/assets/images/learning-paths/holistic-ai-security/shadowit-dashboard-ai-apps.png)
 
-This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as *Approved*. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
+This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as _Approved_. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
 
 ![The App Library filtered to show some of the supported Artificial Intelligence applications.](~/assets/images/learning-paths/holistic-ai-security/ai-app-type-app-library.png)
-
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
index 9d1796cbc8e77a5..da4bbe2960c586f 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { GlossaryDefinition, Render } from "~/components"
+import { GlossaryDefinition, Render } from "~/components";
 
 There's more to a load balancer than just distributing traffic, however.
 
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
index 2a58f062dc5eeeb..7369a7445edbd8d 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
@@ -14,7 +14,7 @@ Learn the concepts behind load balancing, whether you are using Cloudflare or an
 
 By the end of this module, you will be able to:
 
-* Explain what load balancing is.
-* Describe the differences between load balancers, pools, and servers.
-* Explain what pool health is and how it affects load balancer traffic.
-* List the different ways your traffic can be routed.
+- Explain what load balancing is.
+- Describe the differences between load balancers, pools, and servers.
+- Explain what pool health is and how it affects load balancer traffic.
+- List the different ways your traffic can be routed.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
index 7dd7ff6d269783a..e132195e0f7fb3a 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
@@ -8,13 +8,13 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 At it's most basic, load balancing is made up of three components:
 
-* **Pools**: Which contain one or more endpoints.
-* **Endpoints**: Which respond to individual requests.
-* **A load balancer**: Which decides which traffic goes to each pool.
+- **Pools**: Which contain one or more endpoints.
+- **Endpoints**: Which respond to individual requests.
+- **A load balancer**: Which decides which traffic goes to each pool.
 
 ## How it works
 
@@ -22,7 +22,7 @@ Normally, requests to your application would go to individual servers directly.
 
 With a load balancer, requests first go through the load balancer. Your load balancer then routes requests to specific pools.
 
-<Render file="load-balancing-diagram" product="load-balancing" /> <br/>
+<Render file="load-balancing-diagram" product="load-balancing" /> <br />
 
 Within each pool, requests then go to individual endpoints. And that endpoint is what responds to the request.
 
@@ -37,6 +37,6 @@ Within each pool, requests then go to individual endpoints. And that endpoint is
       end
 ```
 
-<br/>
+<br />
 
 This progression of load balancer --> pool --> endpoint is the core part of how a load balancer works.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
index b5cf54d4113227f..d8019a91c1cf983 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
@@ -8,11 +8,11 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Before, we covered how requests move from load balancers to pools and then from pools to individual servers.
 
-What we did not mention, however, was *how* the load balancer and pools make those decisions.
+What we did not mention, however, was _how_ the load balancer and pools make those decisions.
 
 This is a concept known as routing.
 
@@ -60,5 +60,5 @@ Often, load balancers have a special pool known as the **Fallback Pool**, which
 
 Finally, specific settings can also affect the ways a load balancer distributes traffic, such as:
 
-* Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
-* Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
+- Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
+- Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
index 6337e5cf7172cd6..cc8e287532908ff 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="custom-rules-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/index.mdx b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
index eeee73027d3ca18..370f197fbab2a2d 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
@@ -14,7 +14,7 @@ Explore the configuration choices available for your Cloudflare load balancer.
 
 By the end of this module, you will be able to:
 
-* Describe the difference between load balancing at different layers of the network stack.
-* Identify when a load balancer should utilize session affinity.
-* Describe the different policies for endpoint steering and traffic steering.
-* List the different options available to monitor server health.
+- Describe the difference between load balancing at different layers of the network stack.
+- Identify when a load balancer should utilize session affinity.
+- Describe the different policies for endpoint steering and traffic steering.
+- List the different options available to monitor server health.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
index 34aa1d6847c2ece..820f34fada45575 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
@@ -20,10 +20,8 @@ If you want to share a load balancing configuration across multiple hostnames, y
 
 :::note
 
-
 You could also achieve the same goal or create more advanced routing decisions by setting up DNS Overrides within [Origin Rules](/rules/origin-rules/) on each hostname that override the hostname to `lb.example.com`.
 
-
 :::
 
 ## Unique configurations
diff --git a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
index d03dbb9b4796bd1..b430e5865cbd6a6 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
@@ -8,17 +8,17 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="origin-steering-definition" product="load-balancing" />
 
-***
+---
 
 ## Policies
 
 <Render file="origin-steering-policies" product="load-balancing" />
 
-***
+---
 
 ## Weights
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
index dd99e87ee3c3d01..70a7b3e021585fc 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="session-affinity-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
index 9ced34523117fe9..3b370b1ed392b31 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
@@ -8,8 +8,8 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
-<Render file="traffic-steering-definition" product="load-balancing" /> <br/>
+<Render file="traffic-steering-definition" product="load-balancing" /> <br />
 
 <DirectoryListing folder="load-balancing/understand-basics/traffic-steering/steering-policies" />
diff --git a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
index a1fbbb640bf00cb..1b2a9ce5c84006d 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
@@ -8,15 +8,15 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 With Cloudflare, you can choose between three types of load balancers:
 
-* [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
-* [DNS-only](#dns-only-load-balancing)
-* [Layer 4 (TCP)](#layer-4-load-balancing)
+- [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
+- [DNS-only](#dns-only-load-balancing)
+- [Layer 4 (TCP)](#layer-4-load-balancing)
 
-***
+---
 
 ## Layer 7 load balancing
 
@@ -26,7 +26,7 @@ With Cloudflare, you can choose between three types of load balancers:
 
 <Render file="layer-7-load-balancing-benefits" product="load-balancing" />
 
-***
+---
 
 ## DNS-only load balancing
 
@@ -34,13 +34,13 @@ With Cloudflare, you can choose between three types of load balancers:
 
 ### Benefits
 
-<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br/>
+<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br />
 
 ### Limitations
 
 <Render file="dns-load-balancing-limitations" product="load-balancing" />
 
-***
+---
 
 ## Layer 4 load balancing
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
index e44453449357179..a34dcbf56c1a141 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="confirm-pool-health" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
index f963bd4a1cc3aee..54cf2a41d9f5d89 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
@@ -10,8 +10,8 @@ products:
 
 Before setting up anything related to your load balancer, make sure you test that production hostnames meet the following criteria:
 
-* Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
-* Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
+- Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
+- Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 
 After confirming each of these conditions are met, you can proceed with setting up your load balancer.
 
@@ -19,5 +19,5 @@ After confirming each of these conditions are met, you can proceed with setting
 
 Depending on your preferences and infrastructure, you might route traffic to your load balancer in different ways:
 
-* For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
-* However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
+- For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
+- However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/index.mdx b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
index 20b76253146a2fe..2f7ceb3e5cd7744 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
@@ -14,13 +14,13 @@ Create a load balancer that monitors endpoint health and intelligently routes tr
 
 By the end of this module, you will be able to:
 
-* Configure a monitor and health checks.
-* Create a pool.
-* Create a load balancer.
-* Analyze traffic patterns.
+- Configure a monitor and health checks.
+- Create a pool.
+- Create a load balancer.
+- Analyze traffic patterns.
 
 ## Prerequisites
 
-* Multiple endpoints, either physical or cloud-based.
-* Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
-* Two hostnames, one for test traffic and the other for production traffic.
+- Multiple endpoints, either physical or cloud-based.
+- Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
+- Two hostnames, one for test traffic and the other for production traffic.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
index 7dea7a8b054a166..5cb5b8556548c35 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Your load balancer should be receiving production traffic (and you can confirm this by reviewing the [analytics](/load-balancing/reference/load-balancing-analytics/)).
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
index f2dda24cae894f0..5f6e8812e2b018b 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
@@ -8,6 +8,6 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="route-production-traffic" product="load-balancing" />
diff --git a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
index 158ed1dbb6f5b89..a9014dbe620e151 100644
--- a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
+++ b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
@@ -20,10 +20,10 @@ Some common mTLS use cases are:
 
 There are two main ways to use mTLS at Cloudflare, either by using the Application Security offering (optionally including [API Shield](/api-shield/)) or [Cloudflare Access](/cloudflare-one/access-controls/policies/). Below is a non-exhaustive overview table of their differences:
 
-| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | Client Certificate Details                                            | Forwarded to the origin server via [Cloudflare API](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-api), [Cloudflare Workers](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-workers), and [Managed Transforms](/ssl/client-certificates/forward-a-client-certificate/#managed-transforms). | Forwarded to the origin server via [Cloudflare API](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-api), [Cloudflare Workers](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-workers), and [Managed Transforms](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#managed-transforms). Client Certificate headers and [Cf-Access-Jwt-Assertion](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/) JWT header can be forwarded to the origin server. |
-| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                         |
+| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                                                     |
diff --git a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
index 93042dd1fa01f4d..4bc6231c21b5a96 100644
--- a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
+++ b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
@@ -26,4 +26,4 @@ mTLS user authentication is included with Cloudflare Access and depends on the n
 
 ## Option 3: mTLS Service Authentication
 
-The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
\ No newline at end of file
+The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
index 16c8ccf32ad86d5..c481f87de2d65a0 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 Cloudflare provides analytics for [security events](/waf/analytics/security-events/), [traffic patterns](/analytics/account-and-zone-analytics/zone-analytics/), and more according to the level of your zone's plan.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
index a4da185bc6f5065..05f03d0f144275e 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
@@ -15,7 +15,7 @@ Learn how to customize and augment Cloudflare’s DDoS protection.
 
 By the end of this module, you will be able to:
 
-* Audit DNS records to prevent accidental IP address exposures.
-* Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
-* Augment Cloudflare's default analytics to examine attacks in more detail.
-* Evaluate different ways to restrict external connections to your origin server.
+- Audit DNS records to prevent accidental IP address exposures.
+- Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
+- Augment Cloudflare's default analytics to examine attacks in more detail.
+- Evaluate different ways to restrict external connections to your origin server.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
index c37bbf8ec26a7db..c2f9d500ff25ee7 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
@@ -15,6 +15,6 @@ Get world-class DDoS protection with a few simple steps.
 
 By the end of this module, you will be able to:
 
-* List the built-in DDoS protection measures provided by Cloudflare.
-* Implement a few, simple customizations to improve DDoS protection.
-* Set up DDoS-related notifications.
+- List the built-in DDoS protection measures provided by Cloudflare.
+- Implement a few, simple customizations to improve DDoS protection.
+- Set up DDoS-related notifications.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
index d464cb2979e60be..882b2ac86f7af63 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The first - and often easiest - step of DDoS protection is making sure your DNS records are [proxied](/dns/proxy-status/) through Cloudflare.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
index 52946023a5865ab..504b661aeade97c 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Another part of preparing for DDoS attacks is knowing when your application is being attacked.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
index 315ae18c24d496c..2dde4bb728e4cad 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
@@ -13,8 +13,8 @@ In some circumstances - specifically when an application allows client-initiated
 
 When you use an SSL/TLS certificate issued by Cloudflare[^1], you can reduce the impact of this vulnerability by:
 
-* Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
-* Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
+- Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
+- Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
 
 [^1]: Meaning either [Universal](/ssl/edge-certificates/universal-ssl/) or [Advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
index cfb31f718c1afba..5d276a7499bc51b 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
@@ -15,5 +15,5 @@ Learn the concepts behind DDoS attacks and protection, whether you are using Clo
 
 By the end of this module, you will be able to:
 
-* Explain what a DDoS attack is and how it could affect your application.
-* List the common ways to prevent DDoS attacks.
+- Explain what a DDoS attack is and how it could affect your application.
+- List the common ways to prevent DDoS attacks.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
index bc327a66a03d394..55992a486b4f980 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
@@ -18,7 +18,7 @@ With Cloudflare Zero Trust, you can apply granular security policies to all traf
 
 By the end of this module, you will be able to:
 
-* Create Zero Trust policies to secure access to your private network.
-* Enforce Cloudflare One Client session timeouts.
-* Display custom block messages.
-* Discover Shadow IT within your private network.
+- Create Zero Trust policies to secure access to your private network.
+- Enforce Cloudflare One Client session timeouts.
+- Display custom block messages.
+- Discover Shadow IT within your private network.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
index 29387c50590e5a7..78c93a432dea818 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
@@ -17,11 +17,11 @@ Most policy building for private network access happens within the Gateway DNS a
 
 Before building your policies, it is helpful to ask yourself a few questions:
 
-* Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
-* Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
-* Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
-* Do you have sources of truth for identity and device posture that will be used in policies?
-* Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
+- Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
+- Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
+- Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
+- Do you have sources of truth for identity and device posture that will be used in policies?
+- Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
 
 ## Prepare to build policies
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
index 943c9627d37f792..a78d1ef69ea07de 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Most legacy VPNs have a global timeout setting that requires end users to log in every X hours or resets VPN profiles at a certain frequency. By doing continuous identity evaluation, a Zero Trust security model eliminates the need for most of the user-interrupting workflows triggered by session timeouts. However, there can still be valid reasons to want users to reauthenticate, either on a recurring basis or to access specific, highly-sensitive or regulated internal services.
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
index 10077edc657d785..43ea4220994ee40 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
@@ -43,11 +43,13 @@ Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build
 [Logs](/cloudflare-one/insights/logs/) provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment.
 
 To review traffic activity for applications protected by Access:
+
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **Access authentication logs**.
 3. Review the [per-request logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#per-request-logs) for your application.
 
 To review traffic activity in the [Gateway logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/):
+
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **HTTP request logs**, **Network logs**, or **DNS query logs** depending on your investigation scope.
 
@@ -98,7 +100,8 @@ To create a device connectivity anomaly notification:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-    <DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select **Add**.
 3. Find **Product** DEX and **Alert type** Device connectivity anomaly, and choose **Select**.
 4. Name the notification.
@@ -116,4 +119,4 @@ Once your policies are live, you can use [DEX tests](/learning-paths/replace-vpn
 
 To learn how to use Logs, Analytics, and DEX together during real-world situations, like onboarding, daily monitoring, and troubleshooting, refer to [Insights](/cloudflare-one/insights/) for more example use cases.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
index f21582fa384073e..e227e835a77f69b 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
@@ -17,6 +17,6 @@ Concepts explain the basic ideas behind how Cloudflare Zero Trust works.
 
 By the end of this module, you will be able to:
 
-* Explain how Cloudflare works.
-* Describe the purpose of a VPN.
-* Understand the benefits of switching to a Zero Trust architecture.
+- Explain how Cloudflare works.
+- Describe the purpose of a VPN.
+- Understand the benefits of switching to a Zero Trust architecture.
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
index 9d605a12bcca0b2..92bfa07cbd99ff5 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
index 62f98d74710996a..7a46245dacacf0c 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
@@ -12,7 +12,7 @@ products:
   - gateway
 ---
 
-import { Render, Tabs, TabItem } from "~/components"
+import { Render, Tabs, TabItem } from "~/components";
 
 Cloudflare Tunnel is an outbound-only daemon service that can run on nearly any host machine and proxies local traffic once validated from the Cloudflare network. User traffic initiated from the Cloudflare One Client onramps to Cloudflare, passes down your Cloudflare Tunnel connections, and terminates automatically in your local network. Traffic reaching your internal applications or services will carry the local source IP address of the host machine running the `cloudflared` daemon.
 
@@ -73,17 +73,16 @@ All internal applications and services in this IP range are now connected to Clo
 
 If the tunnel is disconnected:
 
-* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
-
+- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
 
 :::
 
 ## Best practices
 
-* Segregate production and staging traffic among different Cloudflare tunnels.
-* Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
-* Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
-* [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
-* [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
-* [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
+- Segregate production and staging traffic among different Cloudflare tunnels.
+- Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
+- Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
+- [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
+- [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
+- [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
index d36ecb80dd109d4..9ff188f45e603dd 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
@@ -33,17 +33,17 @@ There are [multiple ways](/reference-architecture/architectures/sase/#connecting
 
 ## Comparison table
 
-|                       | Cloudflare Mesh                 | Cloudflare Tunnel           |
-| --------------------- | ------------------------------- | --------------------------- |
-| Bidirectional traffic | ✅                              | ❌                          |
-| High availability     | ✅ (active-passive)             | ✅ (active-active replicas) |
-| Source IP of request  | Virtual IP of requesting device | `cloudflared` host machine  |
-| Host machine          | Linux (amd64, arm64)            | Linux, macOS, Windows       |
-| IPv4                  | ✅                              | ✅                          |
-| IPv6                  | ✅                              | ✅                          |
-| OSI layer             | L3                              | L7                          |
-| Protocol              | MASQUE                          | QUIC or HTTP/2              |
-| Protocols proxied     | TCP, UDP, ICMP                  | HTTP/S, TCP, SSH, RDP, SMB  |
+|                       | Cloudflare Mesh                                                        | Cloudflare Tunnel                                                                                                                                                                                                                                   |
+| --------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bidirectional traffic | ✅                                                                     | ❌                                                                                                                                                                                                                                                  |
+| High availability     | ✅ (active-passive)                                                    | ✅ (active-active replicas)                                                                                                                                                                                                                         |
+| Source IP of request  | Virtual IP of requesting device                                        | `cloudflared` host machine                                                                                                                                                                                                                          |
+| Host machine          | Linux (amd64, arm64)                                                   | Linux, macOS, Windows                                                                                                                                                                                                                               |
+| IPv4                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
+| IPv6                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
+| OSI layer             | L3                                                                     | L7                                                                                                                                                                                                                                                  |
+| Protocol              | MASQUE                                                                 | QUIC or HTTP/2                                                                                                                                                                                                                                      |
+| Protocols proxied     | TCP, UDP, ICMP                                                         | HTTP/S, TCP, SSH, RDP, SMB                                                                                                                                                                                                                          |
 | Connection handling   | End-to-end — preserves long-lived TCP connections across the full path | Proxied — TCP connections are terminated and re-established at Cloudflare, which can interrupt long-lived sessions (for example, SAP transactions, database replication streams, or persistent RDP sessions may drop when `cloudflared` reconnects) |
 
 ## Recommendation
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
index 8dfc2d8f3e258e1..73d7ed1fcc063fd 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
@@ -17,6 +17,6 @@ This module covers how to connect your private network services and applications
 
 By the end of this module, you will be able to:
 
-* Create a Cloudflare Tunnel.
-* Configure private network routes for your tunnel.
-* Understand how to size and scale your tunnel.
+- Create a Cloudflare Tunnel.
+- Configure private network routes for your tunnel.
+- Understand how to size and scale your tunnel.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
index c6b1493e5165c97..536d489c6b31be9 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
@@ -10,7 +10,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="tunnel/virtual-networks-intro" product="cloudflare-one" />
 
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
index 91c1e173b09527c..061277556b36313 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Now that you have a Cloudflare Tunnel up and running, evaluate whether `cloudflared` has enough system resources to handle the expected volume of requests from end users. <Render file="tunnel/availability/tunnel-capacity-intro" product="cloudflare-one" />
 If you have exhausted the ports on a single machine, you will need to add additional servers running `cloudflared`.
diff --git a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
index 9add3ff07321ee9..b7e1bbfc5ccef53 100644
--- a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
@@ -13,7 +13,7 @@ products:
 
 To make the most of this learning path, make sure that you have the following:
 
-* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-* A private network with applications or services that are available locally or via a VPN.
-* A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
-* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
+- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+- A private network with applications or services that are available locally or via a VPN.
+- A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
+- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
index a516b09d3f257d6..1b88fb9f8b8b920 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
@@ -19,7 +19,7 @@ Learn how to troubleshoot your ZTNA deployment.
 
 By the end of this module, you will be able to:
 
-* Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
-* Fix the most common causes of connectivity issues.
+- Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
+- Fix the most common causes of connectivity issues.
 
 <Render file="warp/troubleshooting-guide-reference" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
index e4c61751d31b4a3..4a8c12e1c07aa82 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="tunnel/troubleshoot-private-networks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
index fa82b98809cbb10..d83c0f50abab201 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
@@ -18,6 +18,6 @@ DNS security is an important, wide-reaching, and early action in the lifecycle o
 
 By the end of this module, you will be able to:
 
-* Create your first Gateway DNS policy.
-* Build an allow or block list for use in firewall policies.
-* Onboard networks to Gateway to filter DNS queries.
+- Create your first Gateway DNS policy.
+- Build an allow or block list for use in firewall policies.
+- Onboard networks to Gateway to filter DNS queries.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
index 3a42196c4090ecc..3264f26eb9ea844 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
@@ -16,18 +16,16 @@ Now that you have created firewall policies to secure your organization, you can
 
 :::note
 
-
 The following module requires [egress policies](/cloudflare-one/traffic-policies/egress-policies/), a feature only available on Enterprise plans. If you are not an Enterprise user, you can skip ahead to [Secure SaaS applications](/learning-paths/secure-internet-traffic/secure-saas-applications/).
 
 For more information on egress policies, contact your account team.
 
-
 :::
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Understand when your organization may need source IP anchoring.
-* Create egress policies to make use of dedicated egress IPs.
-* Follow best practices for deploying egress IPs.
+- Understand when your organization may need source IP anchoring.
+- Create egress policies to make use of dedicated egress IPs.
+- Follow best practices for deploying egress IPs.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
index b67afebdb19655c..486ba1b10c7e8c0 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
@@ -18,7 +18,7 @@ After securing your organization's DNS queries and network level traffic, you ca
 
 By the end of this module, you will be able to:
 
-* Understand how and when to use TLS inspection to decrypt HTTPS traffic.
-* Configure and enable Data Loss Prevention to protect your organization's sensitive data.
-* Protect user endpoints with Browser Isolation.
-* Add recommended HTTP security policies.
+- Understand how and when to use TLS inspection to decrypt HTTPS traffic.
+- Configure and enable Data Loss Prevention to protect your organization's sensitive data.
+- Protect user endpoints with Browser Isolation.
+- Add recommended HTTP security policies.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
index 71711da35cc0387..8d4115bd0b7fde1 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
@@ -18,5 +18,5 @@ Learn the core concepts of using Cloudflare Zero Trust functionality to provide
 
 By the end of this module, you will be able to:
 
-* Understand what products and features Cloudflare offers.
-* Describe how Cloudflare implements Internet traffic and SaaS app security.
+- Understand what products and features Cloudflare offers.
+- Describe how Cloudflare implements Internet traffic and SaaS app security.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
index 319216b4c04291b..a22224d4e229731 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
@@ -36,12 +36,12 @@ Cloudflare supports filtering HTTP/S traffic sent via a PAC file on a user devic
 
 Cloudflare Browser Isolation runs a headless, Chromium-based browser for your users to accomplish their secure browsing needs. It can be activated via an Access application, a Gateway policy, or by using link-based isolation (reverse proxy). In this model, your users can connect from any device to a proxy website to browse the Internet while applying all your Gateway HTTP policies and inspection requirements.
 
-|                                   | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
-| --------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
-| Supported OS                      | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
-| Configurable via MDM              | Yes                                  | Yes            | N/A                                   |
-| Gateway policy types supported    | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
-| Identity-based policies supported | Yes                                  | No             | Yes                                   |
+|                                                                                                 | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
+| Supported OS                                                                                    | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
+| Configurable via MDM                                                                            | Yes                                  | Yes            | N/A                                   |
+| Gateway policy types supported                                                                  | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
+| Identity-based policies supported                                                               | Yes                                  | No             | Yes                                   |
 | [Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Yes                                  | Yes            | Yes                                   |
 
 ## Network on-ramps
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
index 14f947c033c85f7..0317f717c9237be 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
@@ -14,5 +14,5 @@ products:
 
 To make the most of securing your Internet traffic and SaaS apps, make sure that you have the following:
 
-* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
+- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
index 1dcb52b2c614a63..e67e85f67da54d6 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
@@ -18,6 +18,6 @@ Now that you have deployed dedicated egress IPs and created egress policies to a
 
 By the end of this module, you will be able to:
 
-* Secure your SaaS applications by integrating them with Cloudflare CASB.
-* Control access to your SSO front door.
-* Layer multiple security methods for protecting SaaS apps.
+- Secure your SaaS applications by integrating them with Cloudflare CASB.
+- Control access to your SSO front door.
+- Layer multiple security methods for protecting SaaS apps.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
index 52d73e8318fb87d..92db03a4e2e98a1 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
@@ -18,10 +18,10 @@ products:
 
 Access for SaaS integrates directly with your SaaS app using standard protocols (such as SAML) to become the primary enforcement point for user access. Access calls your identity provider (IdP) of choice and uses additional security signals about your users and devices to make policy decisions. Benefits of Access for SaaS include:
 
-* A streamlined experience for users on both managed and unmanaged devices.
-* Application of baseline policies requiring specific concepts such as device posture and endpoint control.
-* Distinct access methodology for contractors.
-* Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
+- A streamlined experience for users on both managed and unmanaged devices.
+- Application of baseline policies requiring specific concepts such as device posture and endpoint control.
+- Distinct access methodology for contractors.
+- Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
 
 ### SSO integrations
 
@@ -29,10 +29,8 @@ You can pair Access for SaaS with the [App Launcher](/cloudflare-one/access-cont
 
 :::note[SCIM provisioning limitation]
 
-
 Access for SaaS supports SCIM passthrough in an API-only closed beta. If you require SCIM passthrough, contact your account team.
 
-
 :::
 
 ## Configure your SSO provider
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
index 4028b6ad5e95765..3e738d411947195 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
@@ -22,6 +22,6 @@ This guide will provide you with a baseline of recommended policies to build and
 
 By the end of this module, you will be able to:
 
-* Understand the order Gateway enforces policies for filtering traffic.
-* Create reusable lists for Gateway policies.
-* Subscribe to indicator feeds for advanced threat intelligence.
+- Understand the order Gateway enforces policies for filtering traffic.
+- Create reusable lists for Gateway policies.
+- Subscribe to indicator feeds for advanced threat intelligence.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
index d37b3443e21db00..288ad4bd4f9c714 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When building DNS, network, or HTTP policies to block malicious activity for your organization, you can use external indicator feeds supplied by Cloudflare and other third-party providers.
 
@@ -20,4 +20,4 @@ When building DNS, network, or HTTP policies to block malicious activity for you
 
 <Render file="indicator-feeds-overview" product="security-center" />
 
-To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
\ No newline at end of file
+To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
index 4613217ef45c558..075efbb8570f006 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Gateway follows a specific order of enforcement as traffic travels through the Cloudflare global network to the Internet:
 
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
index 094d430d9789447..779c314e0307099 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
@@ -16,4 +16,4 @@ By the end of this module, you will be able to:
 
 - Explain how Cloudflare works.
 - Describe what Email security is.
-- Understand how Cloudflare prevents email-based phishing attacks.
\ No newline at end of file
+- Understand how Cloudflare prevents email-based phishing attacks.
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
index 325d8d4fbe5e300..a81f77056268cbd 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
@@ -16,4 +16,4 @@ As organizations continue to adopt Microsoft 365 and Google Workspace to enhance
 
 Analysts agree that consolidating capabilities to minimize overlapping functionality is helping organizations reduce cost and complexity. However, they also advise organizations to carefully assess native features to ensure they satisfy all use cases. As Microsoft and Google continue to build out its essential email security features, the growing overlap with SEGs has given organizations an opportunity to streamline security operations by leveraging capabilities already included in their E3 or E5 license.
 
-This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
\ No newline at end of file
+This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
index 606e29d7f67ce79..6810419da647886 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="what-is-cloudflare" product="fundamentals" />
\ No newline at end of file
+<Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
index 972a75f3e69fb82..e751db0ccb39b91 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
@@ -10,4 +10,4 @@ products:
 
 Despite email's importance as a communication method, security and privacy were not built into the [The Simple Mail Transfer Protocol (SMTP) protocol](https://www.cloudflare.com/learning/email-security/what-is-smtp/). As a result, email is a major attack vector.
 
-Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
\ No newline at end of file
+Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
index 1134bd825289830..2476b73b8cb70b2 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
@@ -12,4 +12,4 @@ products:
 
 Phishing attackers disguise themselves as a reputable source. With an enticing or seemingly urgent request, an attacker lures the victim into providing information, just as a person uses bait while fishing.
 
-Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
\ No newline at end of file
+Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
index a017783809f59cb..09e0b06afb41ca9 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
@@ -49,4 +49,4 @@ In addition, Email security allows you to:
 
 - [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry).
 - [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry).
-- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
\ No newline at end of file
+- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
index 665a142ede96132..8df6912430c831b 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
@@ -21,7 +21,6 @@ To enable audit logs:
 2. Select your storage destination.
 3. Select the three dots > **Edit**.
 4. Under **Configure logpush job**:
-
    - **Job name**: Enter the job name, if it is not already prepopulated.
    - **If logs match** > Select **Filtered logs**:
      - **Field**: Choose `ResourceType`.
@@ -30,4 +29,4 @@ To enable audit logs:
 
 5. Select **Submit**.
 
-You can now view logs via the Cloudflare dashboard.
\ No newline at end of file
+You can now view logs via the Cloudflare dashboard.
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
index 0378058f8d87ec6..fbbb6474283ca81 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
@@ -30,4 +30,4 @@ To add a user to the impersonation registry:
      - **Add users or groups**: Choose the users or groups you want to register.
 6. Select **Save**.
 
-For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
\ No newline at end of file
+For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
index 461cbd6dbd19774..2e7a4d8bfb7cbe7 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
@@ -10,4 +10,4 @@ products:
 
 With Email security, there is limited manual configuration and tuning. The Active Directory sync, allow policies, and additional detections are important to consider when you set up Email security.
 
-In this module, you will configure your email environment.
\ No newline at end of file
+In this module, you will configure your email environment.
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
index 3cc5f8cd3fe2d8c..ba4ad5c0c65ba4a 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
@@ -33,4 +33,4 @@ To set up PhishNet for Google Workspace:
 1. Log in to the Google Workspace Marketplace using an administrator account.
 2. Select **Admin install** to install Cloudflare PhishNet.
 
-Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
\ No newline at end of file
+Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
index 34c5572c1d9bd7f..6efc9e48a5b5f2c 100644
--- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
@@ -16,4 +16,4 @@ Ensure you have completed the previous modules before enabling auto-moves.
 
 Auto-move events are events where emails are automatically moved to different inboxes based on the disposition assigned to them by Email security.
 
-When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
\ No newline at end of file
+When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
index a5209b5455fedb9..20822f04cf3be59 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
@@ -20,8 +20,8 @@ If you are a Google Workspace user, you can enable Email security via [BCC setup
 
 ![Google Workspace BCC deployment diagram](~/assets/email-security/Gmail_Deployment_BCC.png)
 
-With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection. 
+With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection.
 
 ![Microsoft 365 and Google Workspace MX/Inline](~/assets/email-security/Email_security_Deployment_Inline.png)
 
-Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
\ No newline at end of file
+Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
index 16e8a6a9cc6b7f5..ddf2e2a40c90def 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
@@ -8,4 +8,4 @@ products:
   - email-security
 ---
 
-To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account. 
\ No newline at end of file
+To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
index a83c5051a08616c..891d3080a754f62 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
@@ -16,4 +16,4 @@ The API deployment with Email security offers:
 - Agentless deployment for Microsoft 365.
 - Office 365 directory integration to retrieve user and group information and prevent user impersonation.
 
-![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
\ No newline at end of file
+![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
index 28bf9247f9c6975..3743a5c02f2a30e 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
@@ -11,4 +11,4 @@ products:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**.
-4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
\ No newline at end of file
+4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
index 447dea2119c80ba..1c65ac9d9434a5c 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
@@ -12,7 +12,7 @@ products:
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**.
 4. Enable **Microsoft Integration**:
-   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. 
+   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration.
    2. **Name integration**: Add your integration name, then select **Continue**.
    3. **Authorize integration**:
       - Select **Authorize**. Selecting **Authorize** will take you to the Microsoft Sign in page where you will have to enter your email address.
@@ -20,4 +20,4 @@ products:
       - After selecting **Next**, the system will show a dialog box with a list of requested permissions. Select **Accept** to authorize Email security. Upon authorization, you will be redirected to a page where you can review details and enroll integration.
    4. **Review details**: Review your integration details, then:
       - Select **Complete Email security set up** where you will be able to connect your domains and configure auto-moves.
-      - Select **Continue to Email security**.
\ No newline at end of file
+      - Select **Continue to Email security**.
diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
index e5a57972d2a82f0..40565ed07e17558 100644
--- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
@@ -17,4 +17,4 @@ There are two different ways to [submit a phish](/cloudflare-one/email-security/
   - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you.
 - Admin submission:
   - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address.
-  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
\ No newline at end of file
+  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
diff --git a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
index 3432b43cd002658..47bf090845f40be 100644
--- a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
@@ -20,15 +20,15 @@ To learn more about our service offerings, refer to [Customer Success offerings]
 
 For the security and protection of your account, be sure to register all account users.
 
-1. In the Cloudflare dashboard, go to the  **Manage Account** > **Members** page.
+1. In the Cloudflare dashboard, go to the **Manage Account** > **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Select more than one Super Administrator to ensure appropriate access when needed.
 
 :::note
 
-Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users. 
+Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users.
 
 :::
 
@@ -50,7 +50,7 @@ We strongly advise against credential-sharing which can jeopardize the trust and
   Certificates managed by Cloudflare are auto-renewed.
   :::
 - Review your Operational and Disaster recovery preparedness
-    - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
-    - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
+  - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
+  - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
 - Review and update your current users' access
-- Check your domain registry validity
\ No newline at end of file
+- Check your domain registry validity
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
index 11fe9044b199b1c..d58062e1f6e2e72 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
@@ -14,16 +14,14 @@ products:
 
 Use the [Workers Analytics Engine](/analytics/analytics-engine/) to send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL.
 
-
 ## Account and zone analytics
 
 Use [Account and zone analytics](/analytics/account-and-zone-analytics/) to provide details about the requests and traffic related to your Cloudflare accounts and zones.
 
-
 ## Cloudflare Network Analytics
 
 Use [Cloudflare Network Analytics](/analytics/network-analytics/) to provide near real-time visibility into network and transport-layer traffic patterns and DDoS attacks.
 
 ## GraphQL Analytics API
 
-Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
\ No newline at end of file
+Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
index d594e17850fe651..7be8e912c96ed9a 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
@@ -16,26 +16,21 @@ import { DashButton } from "~/components";
 
 By default, Cloudflare [caches static content](/cache/concepts/default-cache-behavior/) such as images, CSS, and JavaScript. However, you can extend Cloudflare caching to work with HTML by creating custom [Cache Rules](/cache/how-to/cache-rules/).
 
-
 ### Cache more requests
 
-1. In  the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page. 
+1. In the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page.
 
-    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+   <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
 3. For When incoming requests match, enter either your entire website or a specific path on your application, based on the Hostname or URI Path. Refer to the [available fields](/cache/how-to/cache-rules/settings/#fields).
 4. For Cache eligibility, define how these requests should be cached and for how long. Refer to the available [cache eligibility settings](/cache/how-to/cache-rules/settings/#eligible-for-cache-settings).
 5. You can then monitor the effectiveness of your cache settings using [Cache Analytics](/cache/performance-review/cache-analytics/) and update your configuration according to our [Cache performance guide](/cache/performance-review/cache-performance/).
 
-
 ### Advanced cache optimizations
 
-
-
-* [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
-* [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
-
+- [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
+- [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
 
 ## Tiered Cache
 
@@ -45,7 +40,6 @@ It works by dividing Cloudflare's data centers into a hierarchy of lower-tiers a
 
 Refer to [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) to get started.
 
-
 ### Cache Reserve
 
 [Cache Reserve](/cache/advanced-configuration/cache-reserve/) is a large, persistent data store implemented on top of [R2](/r2/).
@@ -54,38 +48,32 @@ With a single click in the dashboard, your cacheable content will be written to
 
 This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
 
-
 ## Cloudflare Waiting Room
 
 [Cloudflare Waiting Room](/waiting-room/) allows you to route excess users of your website to a customized waiting room, helping preserve customer experience and protect origin servers from being overwhelmed with requests.
 
-
 ## Use Cloudflare IP addresses
 
 Take action to prevent attacks to your application during peak season by configuring your firewall to only accept traffic from Cloudflare IP addresses. By only allowing [Cloudflare IPs](https://www.cloudflare.com/ips), you can prevent attackers from bypassing Cloudflare and sending requests directly to your origin.
 
 Refer to [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) for more information.
 
-
 ## Monitor traffic
 
 You can use the Cloudflare dashboard to closely monitor the traffic on your domain and fine-tune your cache and security settings accordingly.
 
-
 ### Zone and Account analytics
 
 [Cloudflare zone analytics](/analytics/account-and-zone-analytics/zone-analytics/) gives you access to a wide range of metrics, collected at the website or domain level.
 
 [Cloudflare account analytics](/analytics/account-and-zone-analytics/account-analytics/) lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
-
 ### Security Analytics and Security Events
 
 [Security Analytics](/waf/analytics/security-analytics/) displays information about all incoming HTTP requests for your domain, including requests not handled by Cloudflare security products.
 
 You can also use the [Security Events](/waf/analytics/security-events/) to review mitigated requests and tailor your security configurations.
 
-
 ### Cache Analytics
 
-You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
\ No newline at end of file
+You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
index 63efb8a1e0f3aef..2655eccdda8256f 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
index 46f719837ac8da1..6434accda802398 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
@@ -14,17 +14,14 @@ products:
 
 Use [Logpush](/logs/logpush/) to push your request or event logs to your cloud service provider using Logpush, which can be configured via the Cloudflare dashboard or API.
 
-
 ## Instant Logs
 
 Use [Instant Logs](/logs/instant-logs/) to view HTTP request logs instantly in the Cloudflare dashboard or the CLI.
 
-
 ## Logs Engine
 
-Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.  
-
+Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.
 
 ## Log Explorer
 
-Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API. 
\ No newline at end of file
+Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
index 07a1c32748a4a4b..075b1e688bd6801 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
@@ -10,7 +10,6 @@ products:
   - ddos-protection
 ---
 
-
 [User Agent (UA) Blocking](/waf/tools/user-agent-blocking/) rules match against specific User-Agent request headers sent by the browser or application accessing your site. UA rules are applied against the entire domain, and after a rule is triggered, you can decide which action to take against the visitor.
 
 Actions:
diff --git a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
index 8a5b929f561880a..c0d4fe2c9a50ebe 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Review the list below for guidance on securing your account.
 
-<DirectoryListing folder="fundamentals/account/account-security" />
\ No newline at end of file
+<DirectoryListing folder="fundamentals/account/account-security" />
diff --git a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
index 9fb487a7190ccfd..8508360fa7d7ac7 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
@@ -14,13 +14,10 @@ products:
 
 IP Access Rules can be applied based on:
 
-
-
-* IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
-* IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
-* ASN
-* Country or the Tor network
-
+- IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
+- IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
+- ASN
+- Country or the Tor network
 
 :::note
 
@@ -34,4 +31,3 @@ Actions:
 - Non-Interactive Challenge: Visitors will be shown a non-interactive challenge before allowed access.
 - Interactive Challenge: Visitors will be shown an interactive challenge before allowed access.
 - Allowlist: Ensures that an IP address will never be blocked from accessing your site. This supersedes any Cloudflare security profile.
-
diff --git a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
index 1c28bd66975b7dd..2436739e7c61285 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
@@ -1,7 +1,7 @@
 ---
 title: What to do when under attack
 pcx_content_type: overview
-sidebar: 
+sidebar:
   order: 9
 description: Respond to active DDoS attacks.
 products:
@@ -16,14 +16,12 @@ If you are under attack and have this feature enabled during the attack, visitor
 
 Refer to [I'm Under Attack Mode](https://developers.cloudflare.com/fundamentals/reference/under-attack-mode/) for more information.
 
-
 ## Change Access Control List (ACL)
 
 An ACL refers to rules that are applied to port numbers or IP addresses that are available on a host permitting use of the service. When you only allow Cloudflare IPs, you eliminate threats attempting to attack your origin IP range.
 
 Refer to [Cloudflare IP Ranges](https://www.cloudflare.com/ips) for more information.
 
-
 ## Change Origin IPs and update Cloudflare DNS records
 
 If your origin is still being attacked, consider moving your Origin IPs and updating your Cloudflare DNS records.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/index.mdx b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
index cd4191d21fbf2c9..4e47eb5f69bf264 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/support/index.mdx b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
index 38e3bfb1f22fb97..289654ff24ecd81 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
index 1ae293e1c4a56e6..0ce3a91e3055cfd 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
@@ -10,15 +10,14 @@ products:
   - ddos-protection
 ---
 
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
-
-| Support type | Resource |
-| ------------ | -------- |
-| Self-serve questions | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals |
-| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team |
-| Non-critical production issues (reactive) | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
-| Critical issues such as attacks (reactive) | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)| 
+| Support type                                      | Resource                                                                                     |
+| ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| Self-serve questions                              | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals          |
+| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team                                                     |
+| Non-critical production issues (reactive)         | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
+| Critical issues such as attacks (reactive)        | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)       |
 
 :::note
 For security reasons, Cloudflare Support only assists individuals whose email addresses are validated against the list of registered account contacts. Review and update all contacts accordingly in your Cloudflare Dashboard. For more information, refer to [Manage members](/fundamentals/manage-members/).
diff --git a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
index 2865a6b3e04b8af..898e3bb0f7ac8ed 100644
--- a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
@@ -24,13 +24,13 @@ If your application is built on Cloudflare, then Cloudflare would act as the ori
 
 An example tech stack for an application built on Cloudflare would look like:
 
-* [Domain Registrar](/registrar/) to buy a new your domain.
-* [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
-* [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
-* [Storage resources](/workers/platform/storage-options/) to persist different types of data.
-* [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
-* [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
-* [AI](/use-cases/ai/) to run machine learning models.
+- [Domain Registrar](/registrar/) to buy a new your domain.
+- [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
+- [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
+- [Storage resources](/workers/platform/storage-options/) to persist different types of data.
+- [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
+- [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
+- [AI](/use-cases/ai/) to run machine learning models.
 
 And more depending on your use case.
 
@@ -42,11 +42,11 @@ When you add your application to Cloudflare, Cloudflare's global network of serv
 
 After you add your application to [Cloudflare](/fundamentals/concepts/how-cloudflare-works/), you can:
 
-* Use Workers to augment the application by deploying code.
-* Add storage resources available on the Developer Platform.
-* Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
-* Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
-* Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
+- Use Workers to augment the application by deploying code.
+- Add storage resources available on the Developer Platform.
+- Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
+- Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
+- Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
 
 And more depending on your use case.
 
@@ -54,8 +54,8 @@ And more depending on your use case.
 
 By reading this page, you have:
 
-* Learned the scale of Cloudflare's global network.
-* Explored the product offering to know what Cloudflare can offer for users like you.
-* Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
+- Learned the scale of Cloudflare's global network.
+- Explored the product offering to know what Cloudflare can offer for users like you.
+- Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
 
 In the next section, you will be introduced to the fundamentals of serverless computing, the concept behind Cloudflare Workers.
diff --git a/src/content/docs/learning-paths/workers/concepts/index.mdx b/src/content/docs/learning-paths/workers/concepts/index.mdx
index e293a2f1d9d87d7..9837915441175e0 100644
--- a/src/content/docs/learning-paths/workers/concepts/index.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/index.mdx
@@ -16,6 +16,6 @@ Learn the concepts behind what makes Cloudflare Workers reliable, scalable and f
 
 By the end of this module, you will learn:
 
-* What Cloudflare is.
-* The difference between serverless computing and cloud computing paradigms.
-* How Workers works.
+- What Cloudflare is.
+- The difference between serverless computing and cloud computing paradigms.
+- How Workers works.
diff --git a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
index 1fd5f921d05c1ed..c9f1788b07d3213 100644
--- a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
@@ -40,8 +40,8 @@ Developers and organizations using serverless computing are billed on a usage mo
 
 By reading this page, you have:
 
-* Been introduced to the serverless computing concept that is behind Cloudflare Workers.
-* Reviewed the differences between legacy on-premise and cloud computing infrastructure.
-* Analyzed the key differences between the cloud computing and serverless computing paradigms.
+- Been introduced to the serverless computing concept that is behind Cloudflare Workers.
+- Reviewed the differences between legacy on-premise and cloud computing infrastructure.
+- Analyzed the key differences between the cloud computing and serverless computing paradigms.
 
 In the next section, you will learn about what makes Workers, a serverless computing platform that is part of the larger Cloudflare Developer Platform, unique in its architecture from other serverless computing providers.
diff --git a/src/content/docs/learning-paths/workers/devplat/index.mdx b/src/content/docs/learning-paths/workers/devplat/index.mdx
index f792c7ba4cbfda3..365fd4fa0f8d551 100644
--- a/src/content/docs/learning-paths/workers/devplat/index.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/index.mdx
@@ -16,5 +16,5 @@ The Cloudflare Developer Platform allows you to build full-stack applications wi
 
 By the end of this module, you will learn:
 
-* Cloudflare Developer Platform's product offering.
-* What storage options are available to your Worker.
+- Cloudflare Developer Platform's product offering.
+- What storage options are available to your Worker.
diff --git a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
index 20e6536f1ef0349..5a516cca6e30fc3 100644
--- a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { Render, YouTube } from "~/components"
+import { Render, YouTube } from "~/components";
 
 The [Cloudflare Developer Platform](https://www.cloudflare.com/developer-platform/products/) offers various services to empower developers to build full-stack applications, including: [compute](https://www.cloudflare.com/developer-platform/products/#compute), [storage](https://www.cloudflare.com/developer-platform/products/#storage), [web development, image optimization, video streaming](https://www.cloudflare.com/developer-platform/products/#webdev) and [AI](https://ai.cloudflare.com/).
 
diff --git a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
index 4783f290410f89f..491c0bb0dc6773c 100644
--- a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
@@ -18,8 +18,8 @@ You can build and develop your Worker on the Cloudflare dashboard, without needi
 
 The Cloudflare Developer Platform ecosystem has two command-line interfaces (CLI):
 
-* C3: To create new projects.
-* Wrangler: To build and deploy your projects.
+- C3: To create new projects.
+- Wrangler: To build and deploy your projects.
 
 ## C3
 
@@ -45,7 +45,7 @@ Cloudflare recommends choosing and using one [source of truth](/workers/wrangler
 
 By reading this page, you have learned:
 
-* How to use C3 to create new Workers and Pages projects.
-* How to use Wrangler to develop, configure, and delete your projects.
+- How to use C3 to create new Workers and Pages projects.
+- How to use Wrangler to develop, configure, and delete your projects.
 
 In the next section, you will learn more about the Cloudflare dashboard before moving on to deploy your first Worker.
diff --git a/src/content/docs/learning-paths/workers/get-started/first-application.mdx b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
index 422ae8875a66d14..5797be4e53286d6 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-application.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
@@ -9,6 +9,7 @@ description: Build an AI application with Hono.
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 ## Build an AI application with Hono and Workers
@@ -17,21 +18,21 @@ If you have already created your first Worker and want to learn what more you ca
 
 In this course, you will:
 
-* Deploy your first Worker.
-* Develop your application locally.
-* Add the Hono framework to your project.
-* Integrate Workers AI into your project.
+- Deploy your first Worker.
+- Develop your application locally.
+- Add the Hono framework to your project.
+- Integrate Workers AI into your project.
 
 <div style="position: relative; padding-top: 56.25%;">
-    <iframe
-        src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
-        style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-        allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-        allowfullscreen="true">
-    </iframe>
+	<iframe
+		src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
 </div>
 
-<br/>
+<br />
 
 Find [the video on YouTube](https://youtu.be/H7Qe96fqg1M?si=GVkdGLrmb1faiHma) and explore other Cloudflare Workers tutorials.
 
diff --git a/src/content/docs/learning-paths/workers/get-started/index.mdx b/src/content/docs/learning-paths/workers/get-started/index.mdx
index 39b04e54f6794eb..a25e920d7e95452 100644
--- a/src/content/docs/learning-paths/workers/get-started/index.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/index.mdx
@@ -14,6 +14,6 @@ Deploy your first Worker to the Cloudflare global network by
 
 By the end of this module, you will learn:
 
-* The difference between C3 (`create-cloudflare` CLI) and Wrangler.
-* How to use the Cloudflare dashboard to manage your Workers.
-* How to create and deploy your first Worker.
+- The difference between C3 (`create-cloudflare` CLI) and Wrangler.
+- How to use the Cloudflare dashboard to manage your Workers.
+- How to create and deploy your first Worker.
diff --git a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
index cc182b7d7c81178..a01215316a0f040 100644
--- a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
+++ b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
@@ -7,7 +7,6 @@ products:
 head:
   - tag: title
     content: Load balance additional DNS records
-
 ---
 
 In addition to load balancing between DNS records used for IP resolution — `A`, `AAAA`, and `CNAME` records — Enterprise customers can also load balance between **MX** and **SRV** records.
@@ -17,7 +16,7 @@ In addition to load balancing between DNS records used for IP resolution — `A`
 To load balance between multiple mail servers:
 
 1. Make sure you have the [required DNS records](/dns/manage-dns-records/how-to/email-records/#send-and-receive-email) for your mail servers.
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *SMTP*.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _SMTP_.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your mail servers and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. Since it will forward SMTP traffic, the load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
 
@@ -26,6 +25,6 @@ To load balance between multiple mail servers:
 To load balance between different **SRV** records, which contain significantly more information than many other DNS records:
 
 1. [Create your SRV records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records).
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *UDP-ICMP* or *TCP*.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _UDP-ICMP_ or _TCP_.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your various SRV records and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. This load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
diff --git a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
index 26703586383732d..826228781b9546b 100644
--- a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
+++ b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Route traffic through a Cloudflare Tunnel
-
 ---
 
 Cloudflare Tunnel (formerly Argo Tunnel) establishes a secure outbound connection which runs in your infrastructure to connect the applications and machines to Cloudflare.
diff --git a/src/content/docs/load-balancing/additional-options/index.mdx b/src/content/docs/load-balancing/additional-options/index.mdx
index fa8021c02caae66..67bfe4b67c3ffd3 100644
--- a/src/content/docs/load-balancing/additional-options/index.mdx
+++ b/src/content/docs/load-balancing/additional-options/index.mdx
@@ -6,22 +6,21 @@ products:
 title: Additional configuration
 sidebar:
   order: 49
-
 ---
 
 Beyond [creating a simple load balancer](/load-balancing/load-balancers/create-load-balancer/), you may want to further customize how your load balancer routes traffic or integrate your load balancer with other Cloudflare products.
 
 ## Customize load balancer behavior
 
-* Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
-* Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
-* Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
+- Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
+- Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
+- Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
 
 ## Integrate with other Cloudflare products
 
-* Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
-* Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
+- Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
+- Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
 
 ## Integrate with 3rd parties
 
-* Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
+- Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
index ce90921b4f41919..e0591ff2cfa42ea 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Balancing with the China Network
 sidebar:
   order: 15
-
 ---
 
 ## Prerequisites
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
index 3fa85bff4993517..ef52ac1aafb7236 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
@@ -9,16 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Load Balancing expressions
-
 ---
 
 [Load Balancing rules](/load-balancing/additional-options/load-balancing-rules/) use two kinds of expressions:
 
-* [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (*equals* or *less than*, for example).
+- [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (_equals_ or _less than_, for example).
 
-* [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (*and*, *or*, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
+- [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (_and_, _or_, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
 
-***
+---
 
 ## Simple expressions
 
@@ -44,11 +43,11 @@ In general, simple expressions use this pattern:
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
-***
+---
 
 ## Compound expressions
 
-A compound expression uses a **logical operator** (*and*, *or*, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
+A compound expression uses a **logical operator** (_and_, _or_, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
 
 The example expression below returns true when both the HTTP request URI path contains `/content` and the query string contains `webserver`:
 
@@ -67,7 +66,7 @@ A compound expression can be an operand of a logical operator. This allows multi
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
-***
+---
 
 ## Working with expressions
 
diff --git a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
index 135607380a8e453..ec4cd87db9d1d86 100644
--- a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
+++ b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
@@ -6,19 +6,16 @@ products:
 title: Override HTTP Host headers
 sidebar:
   order: 16
-
 ---
 
 When your application needs specialized routing (`CNAME` setup or custom hosts like Heroku), you can customize the `Host` header used in health monitors on a per-endpoint or per-monitor level.
 
 :::caution[Important]
 
-
 If you set a header override on an individual endpoint, it will take precedence over a header override set on a monitor.
 
 Also, if you configure an [Origin Rule](/rules/origin-rules/) that overrides the hostname and set up a header override in your Load Balancer configuration, the Load Balancer configuration will take precedence over the Origin Rule hostname override.
 
-
 :::
 
 ## Per endpoint Host header override
@@ -27,13 +24,13 @@ To balance traffic across multiple hosts, add `Host` headers to individual endpo
 
 For example, you might have a pool with endpoints hosted in multiple AppEngine projects or Amazon S3 buckets. You also might want to set up specific failover endpoints within a pool.
 
-Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic *without* a `Host` header override.
+Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic _without_ a `Host` header override.
 
 If you need an endpoint `Host` header override, add it when [creating](/load-balancing/pools/create-pool/) or editing a pool. For security reasons, this header must meet one of the following criteria:
 
-* Is a subdomain of a zone associated with this account
-* Matches the endpoint address
-* Publicly resolves to the endpoint address
+- Is a subdomain of a zone associated with this account
+- Matches the endpoint address
+- Publicly resolves to the endpoint address
 
 ## Host header prioritization
 
@@ -41,19 +38,16 @@ If you set a header override on an individual endpoint, it will take precedence
 
 For example, you might have a load balancer for `www.example.com` with the following setup:
 
-* Pools:
-
-  * Pool 1:
-
-    * Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
-    * Endpoint 2
-
-  * Pool 2:
+- Pools:
+  - Pool 1:
+    - Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
+    - Endpoint 2
 
-    * Endpoint 3
-    * Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
+  - Pool 2:
+    - Endpoint 3
+    - Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
 
-* Monitor (`Host` header set to `www.example.com`)
+- Monitor (`Host` header set to `www.example.com`)
 
 In this scenario, health monitor requests for **Endpoint 1** would use `lb-app-a.example.com`, health monitor requests for **Endpoint 4** would use `lb-app-b.example.com`, and all other health monitor requests would default to `www.example.com`. For more information on updating your custom host configuration to be compatible with Cloudflare, see [Configure Cloudflare and Heroku over HTTPS](/support/third-party-software/others/configure-cloudflare-and-heroku-over-https/).
 
diff --git a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
index 800fefee9fab77d..f9d25700c2ef3e6 100644
--- a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
+++ b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
@@ -6,7 +6,6 @@ products:
 title: Integrate with PagerDuty
 sidebar:
   order: 41
-
 ---
 
 To integrate Cloudflare health monitor notifications with PagerDuty, follow the steps outlined in PagerDuty’s [Email Integration Guide](https://www.pagerduty.com/docs/guides/email-integration-guide/). If you do not have a PagerDuty account, you will first need to set that up.
diff --git a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
index 44d8e5917088c19..934c8b9eaad2618 100644
--- a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
+++ b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
@@ -18,10 +18,8 @@ To direct traffic away from your endpoint immediately, [adjust settings on the p
 
 :::note
 
-
 If you want to divert traffic from an endpoint to prevent it from becoming unhealthy, use [Load Shedding](/load-balancing/additional-options/load-shedding/) instead.
 
-
 :::
 
 ## Before you begin
@@ -34,10 +32,8 @@ If a pool falls below its **Health Threshold**, it will be considered **Unhealth
 
 :::note
 
-
 Endpoint drain is only available for [proxied load balancers (orange-clouded)](/load-balancing/understand-basics/proxy-modes/).
 
-
 :::
 
 With [session-based load balancing](/load-balancing/understand-basics/session-affinity/), it is important to direct all requests from a particular end user to a specific endpoint. Otherwise, information about the user session — such as items in their shopping cart — may be lost and lead to negative business outcomes.
@@ -63,10 +59,10 @@ To remove an endpoint from rotation while still preserving session continuity, s
 To direct traffic away from an endpoint immediately:
 
 1. Do one of the following actions:
-   * On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
-   * On the pool, disable the endpoint.
-   * On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
+   - On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
+   - On the pool, disable the endpoint.
+   - On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
 2. Monitor [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) to make sure no requests are reaching the pool.
-   * If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
+   - If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
 3. Perform your required maintenance or upgrades.
 4. Undo the changes you made in **Step 1**.
diff --git a/src/content/docs/load-balancing/api-reference.mdx b/src/content/docs/load-balancing/api-reference.mdx
index beaae8039b92f86..5fcef7600b948c2 100644
--- a/src/content/docs/load-balancing/api-reference.mdx
+++ b/src/content/docs/load-balancing/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/load_balancers/methods/get/
 sidebar:
   order: 152
-
 ---
diff --git a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
index 2d257351a66f0cf..290ae83ee3bfbe9 100644
--- a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
+++ b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
@@ -9,10 +9,9 @@ head:
   - tag: title
     content: Enable Load Balancing
 description: Learn how to enable load balancing.
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Load balancing is an add-on for your account, meaning your account needs a [billing profile](/billing/get-started/create-billing-profile/).
 
diff --git a/src/content/docs/load-balancing/get-started/index.mdx b/src/content/docs/load-balancing/get-started/index.mdx
index 718f24899007689..42931ed740f8d8a 100644
--- a/src/content/docs/load-balancing/get-started/index.mdx
+++ b/src/content/docs/load-balancing/get-started/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Get started
 sidebar:
   order: 1
-
 ---
 
 Get started with load balancing in one of two ways:
 
-* [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
-* [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
+- [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
+- [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
diff --git a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
index 47be390136f8260..9e97aeac3cc0923 100644
--- a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
+++ b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
@@ -6,7 +6,6 @@ products:
 title: Common configurations
 sidebar:
   order: 6
-
 ---
 
 Consider the following sections to understand how to achieve some commonly used load balancer configurations.
@@ -39,13 +38,11 @@ This setup speeds up overall requests, but is more vulnerable to planned or unpl
 
 To set up a load balancer with **active-active failover**, either:
 
-* Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
-* Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
+- Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
+- Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
 
 :::note
 
-
 For more background reading on server failover and common configurations, refer to [our Learning Center](https://www.cloudflare.com/learning/performance/what-is-server-failover/).
 
-
 :::
diff --git a/src/content/docs/load-balancing/monitors/index.mdx b/src/content/docs/load-balancing/monitors/index.mdx
index 4f3257567e10daf..1e9332fef2a2c18 100644
--- a/src/content/docs/load-balancing/monitors/index.mdx
+++ b/src/content/docs/load-balancing/monitors/index.mdx
@@ -86,6 +86,6 @@ The following table summarizes the different types of monitors available in Clou
 | ------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | HTTP/HTTPS   | Public and private | Used for HTTP and HTTPS endpoints with specific protocol attributes.                                                                                                                       | The probe is configured with settings and success criteria such as Method, Simulate Zone, Follow Redirects, Request Headers, and Response Body. The probe then evaluates the configured success criteria using the HTTP protocol. Throughout the configured timeout period, the TCP connection is kept active using [keep-alives](/fundamentals/reference/tcp-connections/#tcp-connections-and-keep-alives), even if no response is received. | Success is based on meeting the configured HTTP success criteria. No response within the configured timeout and retries is considered unhealthy.   |
 | TCP          | Public and private | Checks TCP connectivity by attempting to open a connection to the endpoint.                                                                                                                | The monitor sends a TCP SYN message to the specified port. A successful health check requires receiving a SYN/ACK message to establish the connection. The connection is closed by sending a FIN or RST packet, or by receiving a FIN packet from the endpoint.                                                                                                                                                                               | Failure to establish a TCP connection within the configured timeout and retries is considered unhealthy.                                           |
-| ICMP Ping    | Public and Tunnel | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
-| UDP-ICMP     | Public and Tunnel | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
+| ICMP Ping    | Public and Tunnel  | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
+| UDP-ICMP     | Public and Tunnel  | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
 | SMTP         | Public             | Verifies SMTP availability at the application layer.                                                                                                                                       | The monitor establishes a TCP connection and sends an SMTP HELO command. It expects a reply with code 250. The monitor then sends an SMTP QUIT command, expecting a reply with code 221. At the end of each interval, the TCP connection is closed by sending a TCP FIN packet.                                                                                                                                                               | The endpoint must respond with correct SMTP codes (250 for HELO, 221 for QUIT) within the configured timeout and retries to be considered healthy. |
diff --git a/src/content/docs/load-balancing/monitors/monitor-groups.mdx b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
index 50904c9a7de3215..c9523c593355ecb 100644
--- a/src/content/docs/load-balancing/monitors/monitor-groups.mdx
+++ b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
@@ -6,7 +6,6 @@ products:
 title: Monitor Groups
 sidebar:
   order: 48
-
 ---
 
 Group multiple health monitors together to create sophisticated health checks for your applications, ensuring more intelligent and resilient traffic steering.
diff --git a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
index db0595b89b0b6ef..3d3b8c26fad9827 100644
--- a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
+++ b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
@@ -33,8 +33,10 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to
 1. Go to **Load Balancing** at the account level and select **Create a Load Balancer**.
 2. Select **Private Load Balancer**.
 3. On the next step you can choose to associate this load balancer with either:
- - A CGNAT IP from the Cloudflare range or
- - A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
+
+- A CGNAT IP from the Cloudflare range or
+- A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
+
 4. Add a descriptive name to identify your Load Balancer.
 5. Proceed through the setup.
 
diff --git a/src/content/docs/load-balancing/reference-architecture-external-link.mdx b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
index 09dbce736aec377..0183c3d39e2e8f3 100644
--- a/src/content/docs/load-balancing/reference-architecture-external-link.mdx
+++ b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
@@ -7,5 +7,4 @@ title: Reference architecture
 external_link: /reference-architecture/architectures/load-balancing/
 sidebar:
   order: 150
-
 ---
diff --git a/src/content/docs/load-balancing/reference/index.mdx b/src/content/docs/load-balancing/reference/index.mdx
index ec8770d1780404a..e6f4d8d2d6c3b20 100644
--- a/src/content/docs/load-balancing/reference/index.mdx
+++ b/src/content/docs/load-balancing/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 50
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 See the following pages for more information about Cloudflare Load Balancing:
 
diff --git a/src/content/docs/load-balancing/reference/limitations.mdx b/src/content/docs/load-balancing/reference/limitations.mdx
index 5bde030458bc22e..c46c0f6c8a12462 100644
--- a/src/content/docs/load-balancing/reference/limitations.mdx
+++ b/src/content/docs/load-balancing/reference/limitations.mdx
@@ -6,13 +6,12 @@ products:
 title: Limitations
 sidebar:
   order: 48
-
 ---
 
- Name | Non-Enterprise | Enterprise |
- --- | --- | --- |
- Load balancers | 20 | custom |
- Monitor intervals | 15s (min), 3600s (max) | 10s (min), 3600s (max) |
- Monitors | 1.5x the number of pools | 1.5x the number of pools |
- Endpoints | 20 | custom |
- Pools | 20 | custom |
+| Name              | Non-Enterprise           | Enterprise               |
+| ----------------- | ------------------------ | ------------------------ |
+| Load balancers    | 20                       | custom                   |
+| Monitor intervals | 15s (min), 3600s (max)   | 10s (min), 3600s (max)   |
+| Monitors          | 1.5x the number of pools | 1.5x the number of pools |
+| Endpoints         | 20                       | custom                   |
+| Pools             | 20                       | custom                   |
diff --git a/src/content/docs/load-balancing/reference/migration-guides/index.mdx b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
index aecc03630e37bc8..f1e1ae6e2a682da 100644
--- a/src/content/docs/load-balancing/reference/migration-guides/index.mdx
+++ b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
index ede4a1cdcb502e9..9f0e7e87097a25c 100644
--- a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
@@ -6,7 +6,6 @@ products:
 title: Common error codes
 sidebar:
   order: 51
-
 ---
 
 The Cloudflare Load Balancing API adds global health to each pool and endpoint. It also gives you a view into what our network sees at a wider level. Cloudflare uses a quorum system to determine pool and endpoint health status. The quorum is taken from PoPs responsible for running health monitor requests in a region, and the majority result is used.
@@ -23,7 +22,7 @@ If a health monitor request fails, the breakdown will include the reason.
 
 Common troubleshooting causes and solutions are listed below.
 
-***
+---
 
 ## TCP connection failed
 
@@ -35,7 +34,7 @@ Our health monitor requests failed to establish a TCP connection to your endpoin
 
 This typically occurs when there is a network failure between Cloudflare and your endpoint, and/or a firewall refused to allow our connection. Ensure your network and firewall configurations are not interfering with load balancing traffic.
 
-***
+---
 
 ## HTTP timeout occurred
 
@@ -47,7 +46,7 @@ The endpoint failed to return an HTTP response within the timeout configured. Th
 
 We recommend increasing the HTTP response timeout to allow the endpoint to respond.
 
-***
+---
 
 ## Response code mismatch error
 
@@ -67,7 +66,7 @@ You may also see this issue if you have a monitor configured to use HTTP connect
 
 Either change your Cloudflare monitor configuration to use HTTPS, or set the value of `follow_redirect` to `true` so that we can resolve the correct status code.
 
-***
+---
 
 ## Response body mismatch error
 
@@ -75,13 +74,13 @@ Either change your Cloudflare monitor configuration to use HTTPS, or set the val
 
 The response body returns from your endpoint and does not include the (case-insensitive) value of `expected_body` configured in your monitor.
 
-Note that we only read the first 10 KB of the response. If you return a larger response, and the expected\_body is not in the first 10 KB, the health monitor request will fail.
+Note that we only read the first 10 KB of the response. If you return a larger response, and the expected_body is not in the first 10 KB, the health monitor request will fail.
 
 ### Solution
 
-Ensure the expected\_body is in the first 10 KB of the response body.
+Ensure the expected_body is in the first 10 KB of the response body.
 
-***
+---
 
 ## TLS untrusted certificate error
 
@@ -93,7 +92,7 @@ The certificate is not trusted by a public Certificate Authority (CA).
 
 If you're using a self-signed certificate, we recommend either using a publicly trusted certificate or setting the `allow_insecure` property on your monitor to `true`.
 
-***
+---
 
 ## TLS name mismatch error
 
@@ -105,7 +104,7 @@ Our health monitor (client) was not able to match a name on the server certifica
 
 Use the List Monitors command to confirm that the `header` value set in the Cloudflare monitor is correct and the Update Monitors command to make any necessary changes.
 
-***
+---
 
 ## TLS protocol error
 
@@ -117,7 +116,7 @@ This error can occur if you’re using an older version of TLS or your endpoint
 
 Ensure that your endpoint supports TLS 1.0 or greater and is configured for HTTPS.
 
-***
+---
 
 ## TLS unrecognized name error
 
@@ -129,7 +128,7 @@ The server did not recognize the name provided by the client. When a host header
 
 Set the host header in your monitor object.
 
-***
+---
 
 ## No route to host error
 
@@ -141,7 +140,7 @@ The IP address cannot be reached from our network. Common causes are ISP or host
 
 Make sure IP is accurate, and if it is check if there is an ISP or hosting provider network issue.
 
-***
+---
 
 ## Exceeded quota error
 
@@ -155,10 +154,10 @@ If you're using the **Cloudflare API**, you will receive an error message.
 
 ### Solution
 
-* Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
-* Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
+- Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
+- Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
 
-***
+---
 
 ## TCP Timeout
 
@@ -170,7 +169,7 @@ Data transmission was not acknowledged and retransmit of data did not succeed.
 
 Confirm whether the SYN-ACK for the handshake takes place at your endpoint and [contact Cloudflare Support](/support/contacting-cloudflare-support/).
 
-***
+---
 
 ## TLS Handshake Failure
 
@@ -182,7 +181,7 @@ Indicates that the browser's connection to the web server is not secure.
 
 Change wifi networks, connect to a wired network, or verify the network connection is stable.
 
-***
+---
 
 ## Network Unreachable
 
@@ -194,7 +193,7 @@ Cloudflare cannot connect to the endpoint due to network unavailability. This is
 
 Check either the IP entered for the endpoint in Cloudflare's Load Balancer configuration or the IP returned via DNS for the endpoint hostname.
 
-***
+---
 
 ## HTTP Invalid Response
 
@@ -206,7 +205,7 @@ Usually caused by an HTTP 502 error or bad gateway.
 
 Ensure the endpoint responds to requests and that no applications have crashed or are under high load.
 
-***
+---
 
 ## DNS Unknown Host
 
@@ -218,7 +217,7 @@ The endpoint hostname does not exist.
 
 Confirm the endpoint resolves to an IP address.
 
-***
+---
 
 ## Connection Reset by Peer
 
@@ -230,7 +229,7 @@ A network error occurred while the client received data from the endpoint.
 
 Confirm whether the endpoint is experiencing a high amount of traffic or an error.
 
-***
+---
 
 ## Monitor Config Error
 
@@ -242,7 +241,7 @@ There was a configuration error in the monitor and no checks are run against the
 
 Review your monitor configuration to ensure it matches an expected request to your endpoint.
 
-***
+---
 
 ## DNS Internal
 
@@ -254,7 +253,7 @@ The endpoint's hostname resolves to an internal or orange-clouded IP address. No
 
 Cloudflare does not allow use of an endpoint hostname that is proxied by Cloudflare.
 
-***
+---
 
 ## Load Balancing Not Enabled
 
@@ -266,7 +265,7 @@ Load Balancing is not enabled for your account or zone.
 
 For Enterprise customers, reach out to your Cloudflare Account Team. Free, Pro, and Business customers should [Enable Load Balancing](/load-balancing/get-started/enable-load-balancing/).
 
-***
+---
 
 ## Validation failed error
 
@@ -278,7 +277,7 @@ You will receive an error if you try to set the host header value while configur
 
 Cloudflare now restricts configured [endpoint host headers](/load-balancing/additional-options/override-http-host-headers/) to fully qualified domain names (FQDNs) that are immediate subdomains of a zone associated with the account. For example, this host header would be the same zone as the load balancer itself, but pools may be used across multiple Load balancers.
 
-***
+---
 
 ## Object referenced by other objects
 
@@ -290,7 +289,7 @@ You will receive this error when you attempt to delete a pool that is referenced
 
 Remove the pool from the load balancer's geo steering configuration. If your load balancer no longer uses geo steering, you will need to [re-enable geo steering](/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering/) and then remove the pool.
 
-***
+---
 
 ## Other Failure
 
diff --git a/src/content/docs/load-balancing/troubleshooting/index.mdx b/src/content/docs/load-balancing/troubleshooting/index.mdx
index ab1582dd07df552..2a9154394f0dda7 100644
--- a/src/content/docs/load-balancing/troubleshooting/index.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 151
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more guidance related to common issues with load balancers, refer to the following resources:
 
diff --git a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
index f9b35fca372872e..49722335e1400f4 100644
--- a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
@@ -4,7 +4,6 @@ description: Answers to common Load Balancing questions.
 products:
   - load-balancing
 title: FAQs
-
 ---
 
 ## Overview
@@ -17,7 +16,7 @@ Are you trying to turn on Load Balancing? [Enable Load
 Balancing](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing).
 :::
 
-***
+---
 
 ## Why is my origin receiving so many health monitor requests?
 
@@ -35,7 +34,7 @@ To reduce traffic, reduce the number of selected regions or choose an option bes
 
 If you have a low interval for your health monitor requests, you may increase the traffic sent to your endpoints.
 
-***
+---
 
 ## Why is my endpoint or pool considered unhealthy?
 
@@ -43,15 +42,15 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 If you know that your endpoint is healthy but load balancing is reporting it as unhealthy, check the following settings on the [monitor](/load-balancing/monitors):
 
-* Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
-* Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
-* If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
-* If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
-* Try increasing the **Timeout** value.
-* Review the **Host Header** for the health monitor.
-* If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
+- Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
+- Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
+- If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
+- If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
+- Try increasing the **Timeout** value.
+- Review the **Host Header** for the health monitor.
+- If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
 
-***
+---
 
 ## Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?
 
@@ -59,7 +58,7 @@ You occasionally might see traffic routed away from a pool if a health monitor r
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
-***
+---
 
 ## What happens when a pool or endpoint becomes unhealthy?
 
@@ -77,7 +76,7 @@ To avoid these scenarios:
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
-***
+---
 
 ## What is the difference between Load Balancing and Health Checks?
 
@@ -85,7 +84,7 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 [Cloudflare Health Checks](/health-checks/) are identical to monitors within a load balancer, but only meant for probing server health (and not distributing traffic).
 
-***
+---
 
 ## Why do I see different numbers of requests in Load Balancing Analytics?
 
@@ -93,16 +92,16 @@ You may see different numbers of requests when reviewing [Load Balancing Analyti
 
 Load balancing **requests** are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds. This built-in caching is often the cause of an discrepancies.
 
-***
+---
 
 ## I'm seeing a specific error code for my load balancer or monitor.
 
 For a list of specific error codes and next steps, refer to [Load Balancing Troubleshooting](/load-balancing/troubleshooting).
 
-***
+---
 
 ## Related resources
 
-* [Endpoint and pool health](/load-balancing/understand-basics/health-details)
-* [Monitors](/load-balancing/monitors)
-* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
+- [Endpoint and pool health](/load-balancing/understand-basics/health-details)
+- [Monitors](/load-balancing/monitors)
+- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
diff --git a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
index 5932d2fa80bf195..0d58152b129b64d 100644
--- a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
+++ b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
@@ -6,10 +6,9 @@ products:
 title: Adaptive routing
 sidebar:
   order: 18
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Adaptive routing controls features that modify the routing of requests to pools and endpoints in response to dynamic conditions, such as during the interval between active health monitoring requests. <Render file="zero-downtime-failover-retry-on-error" product="fundamentals" />
 
diff --git a/src/content/docs/load-balancing/understand-basics/index.mdx b/src/content/docs/load-balancing/understand-basics/index.mdx
index c85c1403d1845cf..792addac1391985 100644
--- a/src/content/docs/load-balancing/understand-basics/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts and components involved in Cloudflare Load Balancing.
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
index fdba031ab13f323..923d4f04f8cf0f3 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
@@ -6,7 +6,6 @@ products:
 title: Traffic steering
 sidebar:
   order: 4
-
 ---
 
 When requests come to your load balancer, it distributes them across your pools and endpoints according to three factors:
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
index 0c4c24f3ea88b14..4cdb38526cfe80e 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Hash steering
-
 ---
 
 **Hash steering** guides Cloudflare to send requests to endpoints based on a combination of [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) and previous requests from that IP address. Ensures requests from the same IP address will hit the same endpoint, but actual traffic distribution may differ from endpoint weights.
@@ -23,6 +22,3 @@ When a request originates from a browser, it lacks an `x-forwarded-for` header,
 ### Workaround
 
 To ensure Hash Steering works correctly when using a Worker in front of a Load Balancer, manually set the `x-forwarded-for` header in the Worker to the client's original IP address. By manually setting `x-forwarded-for` to `CF-Connecting-IP`, Hash Steering will function as expected, ensuring traffic consistency for end users.
-
-
-
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
index c51194139beb164..02a10b15022975c 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Endpoint-level steering
-
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to endpoints that currently have the lowest number of outstanding requests.
@@ -22,9 +21,9 @@ Least Outstanding Requests steering is best to use if your endpoints are easily
 
 ```json title="Pools"
 {
-  "origin_steering": {
-    "policy": "least_outstanding_requests"
-  }
+	"origin_steering": {
+		"policy": "least_outstanding_requests"
+	}
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
index 80045c618e6408a..537f0a763c9de2a 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Random steering
-
 ---
 
 **Random steering** sends requests to endpoints purely based on [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights). Distributes traffic more accurately, but may cause requests from the same IP to hit different endpoints.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
index 666b471d0af1334..f64ceb698d2ba17 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Dynamic steering
-
 ---
 
 **Dynamic steering** uses health monitor data to identify the fastest pool for a given Cloudflare Region or data center.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
index 4ad16dc07656f19..944941d3224b8ce 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
@@ -20,6 +20,7 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components";
 ## EDNS Client Subnet (ECS) support
 
 <GlossaryTooltip term="EDNS Client Subnet (ECS)"> EDNS Client Subnet (ECS) </GlossaryTooltip> support provides customers with more control over location-based steering during
+
 gray-clouded DNS resolutions and can be used for proximity or geo (country) steering.
 
 Customers can configure their load balancer using the `location_strategy` parameter, which includes the properties `prefer_ecs` and `mode`.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
index a52ce97da3eb882..b6cd01080f74721 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Steering policies
-
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to pools that currently have the lowest number of outstanding requests.
@@ -22,7 +21,7 @@ Least Outstanding Requests steering is best to use if your pools are easily over
 
 ```json title="Load Balancers"
 {
-  "steering_policy": "least_outstanding_requests"
+	"steering_policy": "least_outstanding_requests"
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
index 2b5fbd7114d502e..b5922711d2d91b3 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Proximity steering
-
 ---
 
 **Proximity steering** routes visitors or internal services to the closest physical data center.
@@ -18,21 +17,19 @@ To use proximity steering on a load balancer, you first need to add GPS coordina
 
 ## When to add proximity steering
 
-* For new pools, add GPS coordinates when you create a pool.
-* For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
+- For new pools, add GPS coordinates when you create a pool.
+- For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
 
 ## How to add proximity steering
 
 To add coordinates when creating or editing a pool:
 
-1. Click the *Configure coordinates for Proximity Steering* dropdown.
+1. Click the _Configure coordinates for Proximity Steering_ dropdown.
 2. Enter the latitude and longitude or drag a marker on the map.
 3. Select **Save**.
 
 :::caution[Warning:]
 
-
 For accurate proximity steering, add GPS coordinates to all pools within the same load balancer.
 
-
 :::
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
index 22d271801178c9b..4cb1a555bf452a2 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Standard traffic steering policies
-
 ---
 
 **Standard steering** policies include **Off - Failover** and **Random**.
diff --git a/src/content/docs/log-explorer/api.mdx b/src/content/docs/log-explorer/api.mdx
index 305c470002dd3d8..6bdcc752a5d4156 100644
--- a/src/content/docs/log-explorer/api.mdx
+++ b/src/content/docs/log-explorer/api.mdx
@@ -8,7 +8,7 @@ products:
   - log-explorer
 ---
 
-Configuration and Log searches are also available via a public API. 
+Configuration and Log searches are also available via a public API.
 
 ## Authentication
 
@@ -18,7 +18,7 @@ For detailed information on permissions required for each Log Explorer feature,
 
 ## Query data
 
-Log Explorer includes a SQL API for submitting queries. 
+Log Explorer includes a SQL API for submitting queries.
 
 For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
 
@@ -77,4 +77,4 @@ This command returns the following request details:
 	"errors": [],
 	"messages": []
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/log-explorer/changelog.mdx b/src/content/docs/log-explorer/changelog.mdx
index 2f97c532c5ac0e6..707f755e2c52edd 100644
--- a/src/content/docs/log-explorer/changelog.mdx
+++ b/src/content/docs/log-explorer/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="log-explorer" />
\ No newline at end of file
+<ProductChangelog product="log-explorer" />
diff --git a/src/content/docs/log-explorer/example-queries.mdx b/src/content/docs/log-explorer/example-queries.mdx
index 3d9b6d9cb490e20..265a16759a71279 100644
--- a/src/content/docs/log-explorer/example-queries.mdx
+++ b/src/content/docs/log-explorer/example-queries.mdx
@@ -131,5 +131,5 @@ FROM http_requests
 WHERE {{ timeFilter }}
 GROUP BY ClientRequestPath
 ORDER BY avg_ttfb DESC
-LIMIT 10 
+LIMIT 10
 ```
diff --git a/src/content/docs/log-explorer/index.mdx b/src/content/docs/log-explorer/index.mdx
index 89e85b9513fb688..8d7a69052b79578 100644
--- a/src/content/docs/log-explorer/index.mdx
+++ b/src/content/docs/log-explorer/index.mdx
@@ -8,15 +8,16 @@ products:
   - log-explorer
 ---
 
-import { Description, Feature, RelatedProduct } from "~/components"
+import { Description, Feature, RelatedProduct } from "~/components";
 
 <Description>
-Store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
+	Store and explore your Cloudflare logs directly within the Cloudflare
+	dashboard or API.
 </Description>
 
 Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third-party tools.
 
-Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include: 
+Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include:
 
 - **Reduced cost and complexity**: Drastically reduce the expense and operational overhead associated with forwarding, storing, and analyzing terabytes of log data in external tools.
 - **Faster detection and triage**: Access Cloudflare-native logs directly, eliminating cumbersome data pipelines and the ingest lags that delay critical security insights.
@@ -27,14 +28,14 @@ Contract customers can choose to store their logs in Log Explorer for up to two
 
 ## Permissions
 
-Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards. 
- 
-| Feature | Required Permission | Description |
-|----------|--------------------|--------------|
-| **Manage datasets** | `Logs Edit` | Add, enable, or disable datasets. |
-| **Log Search** | `Logs Read` | Query logs in the dashboard or via API. |
-| **Log Search (save query)** | `Logs Write` | Save log search queries. |
-| **Custom dashboards** | `Analytics Read` | Create and view custom dashboards. |
+Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards.
+
+| Feature                     | Required Permission | Description                             |
+| --------------------------- | ------------------- | --------------------------------------- |
+| **Manage datasets**         | `Logs Edit`         | Add, enable, or disable datasets.       |
+| **Log Search**              | `Logs Read`         | Query logs in the dashboard or via API. |
+| **Log Search (save query)** | `Logs Write`        | Save log search queries.                |
+| **Custom dashboards**       | `Analytics Read`    | Create and view custom dashboards.      |
 
 These permissions apply across both the dashboard and the API, and must be granted at either the account or zone level depending on which datasets you need to access.
 
@@ -43,27 +44,30 @@ Authentication with the API can be done via an API token or API key with an emai
 ## Features
 
 <Feature header="Log Search" href="/log-explorer/log-search/">
-Explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
+	Explore your Cloudflare logs directly within the Cloudflare dashboard or
+	[API](/log-explorer/api/).
 </Feature>
 
 <Feature header="Custom dashboards" href="/log-explorer/custom-dashboards/">
-Design customized views for tracking application security, performance, and usage metrics.
+	Design customized views for tracking application security, performance, and
+	usage metrics.
 </Feature>
 
 <Feature header="Manage datasets" href="/log-explorer/manage-datasets/">
-Manage the data you want to store within Log Explorer. 
+	Manage the data you want to store within Log Explorer.
 </Feature>
 
-<Feature header="API" href= "/log-explorer/api/">
-Manage configuration and perform queries via the API.
+<Feature header="API" href="/log-explorer/api/">
+	Manage configuration and perform queries via the API.
 </Feature>
 
 ## Related products
 
 <RelatedProduct header="Logpush" href="/logs/" product="logs">
-Forward Cloudflare logs to third-party tools for debugging, identifying configuration adjustments, and creating analytics dashboards.
+	Forward Cloudflare logs to third-party tools for debugging, identifying
+	configuration adjustments, and creating analytics dashboards.
 </RelatedProduct>
 
 <RelatedProduct header="Analytics" href="/analytics/" product="analytics">
-Visualize the metadata collected by our products in the Cloudflare dashboard.
-</RelatedProduct>
\ No newline at end of file
+	Visualize the metadata collected by our products in the Cloudflare dashboard.
+</RelatedProduct>
diff --git a/src/content/docs/logs/auditlogs-mcp-server.mdx b/src/content/docs/logs/auditlogs-mcp-server.mdx
index c0a8f2dd81e60e2..36c461b0633126a 100644
--- a/src/content/docs/logs/auditlogs-mcp-server.mdx
+++ b/src/content/docs/logs/auditlogs-mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the Audit Logs MCP server on GitHub.
 products:
   - logs
   - audit-logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/changelog/audit-logs.mdx b/src/content/docs/logs/changelog/audit-logs.mdx
index 146a75efedab424..2e97637e3f86291 100644
--- a/src/content/docs/logs/changelog/audit-logs.mdx
+++ b/src/content/docs/logs/changelog/audit-logs.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="audit-logs" />
\ No newline at end of file
+<ProductChangelog product="audit-logs" />
diff --git a/src/content/docs/logs/changelog/index.mdx b/src/content/docs/logs/changelog/index.mdx
index 337ffa7afa5c1cb..771bbd8160cd93c 100644
--- a/src/content/docs/logs/changelog/index.mdx
+++ b/src/content/docs/logs/changelog/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: View recent changes to Cloudflare Logs.
 products:
   - logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/changelog/logs.mdx b/src/content/docs/logs/changelog/logs.mdx
index 69133c374ad154f..7f30b4e52b1ad87 100644
--- a/src/content/docs/logs/changelog/logs.mdx
+++ b/src/content/docs/logs/changelog/logs.mdx
@@ -13,5 +13,3 @@ import { ProductChangelog } from "~/components";
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
 <ProductChangelog product="logs" />
-
-
diff --git a/src/content/docs/logs/faq/common-calculations.mdx b/src/content/docs/logs/faq/common-calculations.mdx
index 97fe1a4a59bed1f..0252af63297f09c 100644
--- a/src/content/docs/logs/faq/common-calculations.mdx
+++ b/src/content/docs/logs/faq/common-calculations.mdx
@@ -20,5 +20,3 @@ The best way to calculate bytes served by the origin is to use the `CacheRespons
 ### How do I calculate bandwidth usage for my zone?
 
 Bandwidth (or data transfer) can be calculated by adding the `EdgeResponseBytes` field in HTTP request logs. There are some types of requests that are not factored into bandwidth calculations. In order to only include relevant requests in calculations, add the filter `ClientRequestSource = 'eyeball'`.
-
-
diff --git a/src/content/docs/logs/faq/general-faq.mdx b/src/content/docs/logs/faq/general-faq.mdx
index dc0077117908e87..0be1d8058566c6f 100644
--- a/src/content/docs/logs/faq/general-faq.mdx
+++ b/src/content/docs/logs/faq/general-faq.mdx
@@ -32,7 +32,6 @@ Yes. The time period for which you pull or receive logs is based on our processi
 
 Not at this time. Talk to your Cloudflare account team or [Cloudflare Support](/support/contacting-cloudflare-support/) if you are interested in other formats and we will consider them for the future.
 
-
 ### Is it possible to track cache purge requests in the logs?
 
 Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/audit-logs/).
@@ -41,5 +40,3 @@ Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/au
 
 Requests are logged only after they successfully reach our proxy.
 It means that requests failing during the TCP or TLS handshake between the client and the Cloudflare proxy will not be available in the logs.
-
-
diff --git a/src/content/docs/logs/faq/instant-logs.mdx b/src/content/docs/logs/faq/instant-logs.mdx
index b2c23c3ee7e6a1c..1ec7a24289b2ae0 100644
--- a/src/content/docs/logs/faq/instant-logs.mdx
+++ b/src/content/docs/logs/faq/instant-logs.mdx
@@ -14,7 +14,6 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
-
 ### I am getting an HTTP 301 when attempting to connect to my WebSocket. What can I do?
 
 Make sure you are using the `wss://` protocol when connecting to your WebSocket.
@@ -34,5 +33,3 @@ Finally, make sure the destination is proxied through Cloudflare (also known as
 ### I am getting an error fetching my data. How can I solve this?
 
 Make sure you have the correct permissions. To use Instant Logs you need Super Administrator, Administrator, Log Share, or Log Share Reader permissions.
-
-
diff --git a/src/content/docs/logs/faq/logpull-api.mdx b/src/content/docs/logs/faq/logpull-api.mdx
index 28623ba05c80d58..04a52d4ae5aeb26 100644
--- a/src/content/docs/logs/faq/logpull-api.mdx
+++ b/src/content/docs/logs/faq/logpull-api.mdx
@@ -12,17 +12,12 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
-
 ### How long are logs retained?
 
 Cloudflare makes logs available for at least three days and up to seven days. If you need your logs for a longer time period, download and store them locally.
 
-
 ### I am asking for logs for the time window of 16:10-16:13. However, the timestamps in the logs show requests that are before this time period. Why does that happen?
 
-
 When you make a call for the time period of 16:10-16:13, you are actually asking for the logs that were received and processed by our system during that time (hence the endpoint name, `logs/received`). The received time is the time the logs are written to disk. There is some delay between the time the request hits the Cloudflare edge and the time it is received and processed. The **request time** is what you see in the log itself: **EdgeStartTimestamp** and **EdgeEndTimestamp** tell you when the edge started and stopped processing the request.
 
 The advantage of basing the responses on the **time received** rather than the request or edge time is not needing to worry about late-arriving logs. As long as you are calling our API for continuous time segments, you will always get all of your logs without making duplicate calls. If we based the response on request time, you could never be sure that all the logs for that request time had been processed.
-
-
diff --git a/src/content/docs/logs/faq/worker-subrequests.mdx b/src/content/docs/logs/faq/worker-subrequests.mdx
index 3d51ed73a21100d..d1652e3ff63fadd 100644
--- a/src/content/docs/logs/faq/worker-subrequests.mdx
+++ b/src/content/docs/logs/faq/worker-subrequests.mdx
@@ -19,10 +19,10 @@ Because the initial log entry only covers the request from the client to the Wor
 
 ### What the two log entries represent
 
-| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                    |
-| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------- |
+| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                                      |
+| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------------------------- |
 | Initial request   | `eyeball`                           | End-user request to the Worker         | `OriginResponseStatus` is `0`, `OriginIP` is empty |
-| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                    |
+| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                   |
 
 Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for the full list of possible `ClientRequestSource` values.
 
@@ -30,10 +30,10 @@ Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for t
 
 Each log entry has its own `RayID`. The Worker subrequest also includes `ParentRayID`, which is the `RayID` of the request that triggered it — its immediate parent.
 
-| Field         | Initial request                            | Worker subrequest                          |
-| ------------- | ------------------------------------------ | ------------------------------------------ |
-| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest       |
-| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it   |
+| Field         | Initial request                            | Worker subrequest                        |
+| ------------- | ------------------------------------------ | ---------------------------------------- |
+| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest     |
+| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it |
 
 To correlate the two records:
 
diff --git a/src/content/docs/logs/glossary.mdx b/src/content/docs/logs/glossary.mdx
index 5996605fa39a008..986f0dca8ab17e7 100644
--- a/src/content/docs/logs/glossary.mdx
+++ b/src/content/docs/logs/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - logs
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Logs documentation.
 
diff --git a/src/content/docs/logs/logpull/index.mdx b/src/content/docs/logs/logpull/index.mdx
index b22aea276e0eb94..3629ad283b4166f 100644
--- a/src/content/docs/logs/logpull/index.mdx
+++ b/src/content/docs/logs/logpull/index.mdx
@@ -8,16 +8,14 @@ products:
   - logs
 ---
 
-import { DirectoryListing, FeatureTable } from "~/components"
+import { DirectoryListing, FeatureTable } from "~/components";
 
 Cloudflare Logpull is a REST API for consuming request logs over HTTP. These logs contain data related to the connecting client, the request path through the Cloudflare network, and the response from the origin web server. This data is useful for enriching existing logs on an origin server. Logpull is available to customers on the Enterprise plan.
 
 :::caution
 
-
 Logpull is considered a legacy feature and we recommend using [Logpush](/logs/logpush/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
 
-
 :::
 
 Review the following content to learn more about Logpull.
diff --git a/src/content/docs/logs/logpull/requesting-logs.mdx b/src/content/docs/logs/logpull/requesting-logs.mdx
index c7443bca08d6d5c..685501c9631c889 100644
--- a/src/content/docs/logs/logpull/requesting-logs.mdx
+++ b/src/content/docs/logs/logpull/requesting-logs.mdx
@@ -12,20 +12,20 @@ products:
 
 The three endpoints supported by the Logpull API are:
 
-* `GET /logs/received` - returns HTTP request log data based on the parameters specified
-* `GET /logs/received/fields` - returns the list of all available log fields
-* `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
+- `GET /logs/received` - returns HTTP request log data based on the parameters specified
+- `GET /logs/received/fields` - returns the list of all available log fields
+- `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
 
 ## Required authentication headers
 
 The following headers are required for all endpoint calls:
 
-* `X-Auth-Email` - the Cloudflare account email address associated with the domain
-* `X-Auth-Key` - the Cloudflare API key
+- `X-Auth-Email` - the Cloudflare account email address associated with the domain
+- `X-Auth-Key` - the Cloudflare API key
 
 Alternatively, API tokens with Logs Read permissions can also be used for authentication:
 
-* `Authorization: Bearer <API_TOKEN>`
+- `Authorization: Bearer <API_TOKEN>`
 
 ## Parameters
 
@@ -45,11 +45,9 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}?[&fiel
 
 The following table describes the parameters available:
 
-
-
 | Parameter      | Description                                                                                                                                                                                                                                                                                                                          | Applies to                                | Required |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | -------- |
-| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p>                                                                                                                                                 | /logs/received                            | Yes      |
+| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p> | /logs/received                            | Yes      |
 | end            | <p>- Exclusive</p> <p>- Same format as <em>start</em></p> <p>- Must be at least 1 minute earlier than now and later than <em>start</em></p>                                                                                                                                                                                          | /logs/received                            | Yes      |
 | count          | <p>- Return up to that many records</p> <p>- Do not include if returning all records</p> <p>- Results are not sorted; therefore, different data for repeated requests is likely</p> <p></p> <p>- Applies to number of total records returned, not number of sampled records</p>                                                      | /logs/received                            | No       |
 | sample         | <p>- Return only a sample of records</p> <p>- Do not include if returning all records</p> <p>- Value can range from `0.0` (exclusive) to `1.0` (inclusive)</p> <p>- `sample=0.1` means return 10% (1 in 10) of all records</p> <p>- Results are random; therefore, different numbers of results for repeated requests are likely</p> | /logs/received                            | No       |
@@ -57,18 +55,14 @@ The following table describes the parameters available:
 | timestamps     | <p>- Format in which timestamp fields will be returned</p> <p>- Value options are: `unixnano` (default), `unix`, `rfc3339`</p> <p>- Timestamps returned as integers for `unix` and `unixnano` and as strings for `rfc3339`</p>                                                                                                       | <p>/logs/received</p> <p>/logs/rayids</p> | No       |
 | CVE-2021-44228 | <p>- Optional redaction for [CVE-2021-44228](https://www.cve.org/CVERecord?id=CVE-2021-44228). This option will replace every occurrence of the string `${` with `x{`.</p> <p> For example: `CVE-2021-44228=true` </p>                                                                                                               | <p>/logs/received</p>                     | No       |
 
-
-
 :::note[Note]
 
-
 The maximum time range from **start** to **end** cannot exceed 1 hour. Because **start** is inclusive and **end** is exclusive, to get all the data for every minute, starting at 10AM, the proper values are:
 
 `start=2018-05-15T10:00:00Z&end=2018-05-15T10:01:00Z`, then `start=2018-05-15T10:01:00Z&end=2018-05-15T10:02:00Z` and so on.
 
 The overlap will be handled correctly.
 
-
 :::
 
 ## Example API requests using cURL
@@ -91,10 +85,8 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}}
 
 :::note[Note]
 
-
 The IATA code returned as part of the **RayID** does not need to included in the request. For example, if you have a **RayID** such as `49ddb3e70e665831-DFW`, only include `49ddb3e70e665831` in your request.
 
-
 :::
 
 ## Fields
diff --git a/src/content/docs/logs/logpull/understanding-the-basics.mdx b/src/content/docs/logs/logpull/understanding-the-basics.mdx
index 0464c6ff3cdf093..bdd4d1622f13746 100644
--- a/src/content/docs/logs/logpull/understanding-the-basics.mdx
+++ b/src/content/docs/logs/logpull/understanding-the-basics.mdx
@@ -10,7 +10,7 @@ products:
 
 ## Access pattern
 
-The basic access pattern is *give me all the logs for zone Z for minute M* where the minute *M* refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
+The basic access pattern is _give me all the logs for zone Z for minute M_ where the minute _M_ refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
 
 To start, try running your query every minute. If responses are too small, go up to 5 minutes as this will be appropriate for most zones. If the responses are too large, try going down to 15 seconds.
 
@@ -24,7 +24,7 @@ Because our log processing system ingests data in batches, most zones with less
 
 The `logs/received` API endpoint exposes data by time received, which is the time the event was written to disk in the Cloudflare Logs aggregation system.
 
-Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from *rsyslog* (albeit in chunks).
+Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from _rsyslog_ (albeit in chunks).
 
 This means that to obtain logs for a given time range, you can issue one call for each consecutive minute (or other time range). Because log lines are batched by time received and made available, there is no late arriving data. A response for a given minute will never change. You do not have to repeatedly poll a given time range to receive logs as they converge on our aggregation system.
 
@@ -32,7 +32,7 @@ This means that to obtain logs for a given time range, you can issue one call fo
 
 The Logpull API returns data in NDJSON format, whereby each log line is a valid JSON object. Major analysis tools like Google BigQuery and AWS Kinesis require this format.
 
-To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into *jq* using the *slurp* (or simply *s*) flag:
+To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into _jq_ using the _slurp_ (or simply _s_) flag:
 
 `<API request data> | jq -s`
 
@@ -42,15 +42,15 @@ The following is a sample log with default fields:
 
 ```json
 {
-  "ClientIP": "89.163.242.206",
-  "ClientRequestHost": "www.theburritobot.com",
-  "ClientRequestMethod": "GET",
-  "ClientRequestURI": "/static/img/testimonial-hipster.png",
-  "EdgeEndTimestamp": 1506702504461999900,
-  "EdgeResponseBytes": 69045,
-  "EdgeResponseStatus": 200,
-  "EdgeStartTimestamp": 1506702504433000200,
-  "RayID": "3a6050bcbe121a87"
+	"ClientIP": "89.163.242.206",
+	"ClientRequestHost": "www.theburritobot.com",
+	"ClientRequestMethod": "GET",
+	"ClientRequestURI": "/static/img/testimonial-hipster.png",
+	"EdgeEndTimestamp": 1506702504461999900,
+	"EdgeResponseBytes": 69045,
+	"EdgeResponseStatus": 200,
+	"EdgeStartTimestamp": 1506702504433000200,
+	"RayID": "3a6050bcbe121a87"
 }
 ```
 
diff --git a/src/content/docs/logs/logpush-mcp-server.mdx b/src/content/docs/logs/logpush-mcp-server.mdx
index 606c4e683714467..66fb1c45f2e2f73 100644
--- a/src/content/docs/logs/logpush-mcp-server.mdx
+++ b/src/content/docs/logs/logpush-mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Access the Logpush MCP server on GitHub.
 products:
   - logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
index 4ab48625e439d06..fd2d2d005e6d33d 100644
--- a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
+++ b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
@@ -12,10 +12,8 @@ You can manage your Cloudflare Logpush service using Python. In the script below
 
 :::note
 
-
 The examples below are for zone-scoped datasets. Account-scoped datasets should use `<ACCOUNT_ID>` instead of `<ZONE_ID>`.
 
-
 :::
 
 ```python
diff --git a/src/content/docs/logs/logpush/examples/index.mdx b/src/content/docs/logs/logpush/examples/index.mdx
index d593b40a49fe8db..17da91fca9f2307 100644
--- a/src/content/docs/logs/logpush/examples/index.mdx
+++ b/src/content/docs/logs/logpush/examples/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/index.mdx b/src/content/docs/logs/logpush/index.mdx
index c97ab2846f221ff..e93944723bd2eb9 100644
--- a/src/content/docs/logs/logpush/index.mdx
+++ b/src/content/docs/logs/logpush/index.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { FeatureTable, LinkButton } from "~/components"
+import { FeatureTable, LinkButton } from "~/components";
 
 Logpush delivers logs in batches as quickly as possible, with no minimum batch size, potentially delivering files more than once per minute. This capability enables Cloudflare to provide information almost in real time, in smaller file sizes.
 
@@ -57,8 +57,6 @@ There is currently a max limit of **4 Logpush jobs per zone**. Trying to create
 
 :::note
 
-
 Users without an Enterprise plan can still access [Workers Trace Events Logpush](/workers/observability/logs/logpush/) by subscribing to the [Workers Paid](/workers/platform/pricing/) plan.
 
-
 :::
diff --git a/src/content/docs/logs/logpush/logpush-health.mdx b/src/content/docs/logs/logpush/logpush-health.mdx
index 10604407f89dd20..9f31536d4532a8a 100644
--- a/src/content/docs/logs/logpush/logpush-health.mdx
+++ b/src/content/docs/logs/logpush/logpush-health.mdx
@@ -20,17 +20,17 @@ Health notifications work alongside the Health Dashboard to provide both real-ti
 
 ## Access Health Dashboards
 
-1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.  
-2. Go to the **Health** tab.  
-3. Select the job you want to analyze.  
-4. Specify the time range you want to review.  
-5. *(Optional)* From the **Jobs** tab, locate the job you want to analyze.  
-6. Hover over the **Job Health (24h)** column for that job and select **View Health**.  
+1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.
+2. Go to the **Health** tab.
+3. Select the job you want to analyze.
+4. Specify the time range you want to review.
+5. _(Optional)_ From the **Jobs** tab, locate the job you want to analyze.
+6. Hover over the **Job Health (24h)** column for that job and select **View Health**.
 7. You will be redirected to the **Health** tab, where you can select the desired time range for analysis.
 
 ### Data availability and API access
 
-- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.  
+- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.
 - The raw health metrics can be queried via the `logpushHealthAdaptiveGroups` dataset in the GraphQL API.
 - You can explore or test queries using the [Cloudflare GraphQL Explorer](https://graphql.cloudflare.com/explorer).
 
@@ -62,7 +62,7 @@ Indicates that all upload attempts for a batch were exhausted without success. W
 
 ## Health dashboard flow
 
-The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.  
+The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.
 
 Each view highlights a different aspect of job performance — what was delivered and how reliably it was delivered.
 
@@ -72,23 +72,23 @@ Each view highlights a different aspect of job performance — what was delivere
 
 #### Charts and metrics
 
-- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.  
-    - **Successful Uploads** - Total number of batches successfully uploaded.  
-    - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
+- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.
+  - **Successful Uploads** - Total number of batches successfully uploaded.
+  - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
 
-- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.  
-    - **Uploaded Log Lines** - Total number of log lines successfully delivered.  
-    - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
+- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.
+  - **Uploaded Log Lines** - Total number of log lines successfully delivered.
+  - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
 
-- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.  
-    - **Uncompressed Data (raw)** - Total size of log data before compression.  
-    - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
+- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.
+  - **Uncompressed Data (raw)** - Total size of log data before compression.
+  - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
 
 #### When to use
 
 Start here to assess overall data delivery health:
 
-- High upload success and stable data volume indicate a healthy Logpush job.  
+- High upload success and stable data volume indicate a healthy Logpush job.
 - Drops, spikes, or failed uploads suggest delivery issues — proceed to **Upload Reliability** to investigate root causes.
 
 ### Upload Reliability
@@ -97,37 +97,37 @@ Upload Reliability helps you identify factors affecting reliability, stability,
 
 #### Charts and metrics
 
-- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.  
-    - **Success Rate** - Percentage of batches successfully uploaded.  
-    - **Successful Uploads** - Total number of batches successfully completed.
+- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.
+  - **Success Rate** - Percentage of batches successfully uploaded.
+  - **Successful Uploads** - Total number of batches successfully completed.
 
-- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.  
-    - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.  
-    - **Average Upload Duration** - Average time taken to upload logs after they are generated.
+- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.
+  - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.
+  - **Average Upload Duration** - Average time taken to upload logs after they are generated.
 
-- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.  
-    - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
+- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.
+  - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
 
 #### When to use
 
 Use this view to troubleshoot reliability issues:
 
-- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.  
+- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.
 - Combine with **Upload Health** metrics to correlate delivery success with underlying reliability patterns.
 
 ## Troubleshooting guide
 
 The Logpush Health Dashboards help you monitor the status, reliability, and performance of your Logpush jobs. Use this guide to interpret each chart, identify the root cause of anomalies, and take corrective action.
 
-| Chart name | Symptom | What it means | Possible causes | Recommended actions |
-|-----------------|-------------|-------------------|----------------------|--------------------------|
-| **Batch Upload Success vs Failure** | Failed uploads | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/>  - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
-| **Log Lines Uploaded** | Dropped log lines or reduced delivery volume | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches. | - Spike in failed uploads. <br/>  - Destination ingestion limits or partial uploads. | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/>  - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes. |
-| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches. | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits. | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries. |
-| **Uploaded Logs by Status Code** | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries. | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination. | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size. |
-| **Retry Attempts** | Frequent retry activity | Uploads are repeatedly failing and retried multiple times. | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination. | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review. |
-| **Avg. Upload Duration** | Long upload times | Uploads are taking longer than expected, indicating latency or oversized batches. | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays. | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings. |
-| **Destination Availability** | Low or unstable availability | Cloudflare cannot consistently connect to your destination. | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare. | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings. |
+| Chart name                                  | Symptom                                       | What it means                                                                                                                                 | Possible causes                                                                                                                                                                                                       | Recommended actions                                                                                                                                                                                                                           |
+| ------------------------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Batch Upload Success vs Failure**         | Failed uploads                                | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/> - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
+| **Log Lines Uploaded**                      | Dropped log lines or reduced delivery volume  | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches.                                                 | - Spike in failed uploads. <br/> - Destination ingestion limits or partial uploads.                                                                                                                                   | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/> - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes.                                               |
+| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume                | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches.                                       | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits.                                                                                                         | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries.                                                                                             |
+| **Uploaded Logs by Status Code**            | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries.                                                                                     | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination.                                                                                                   | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size.                                                                                         |
+| **Retry Attempts**                          | Frequent retry activity                       | Uploads are repeatedly failing and retried multiple times.                                                                                    | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination.                                                                                                    | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review.                                                             |
+| **Avg. Upload Duration**                    | Long upload times                             | Uploads are taking longer than expected, indicating latency or oversized batches.                                                             | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays.                                                                                                 | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings.                                                                                        |
+| **Destination Availability**                | Low or unstable availability                  | Cloudflare cannot consistently connect to your destination.                                                                                   | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare.                                                                                           | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings.                                                                             |
 
 ## Understanding retry behavior
 
diff --git a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
index 6a98f17905433ca..d7b7dd78507d62e 100644
--- a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
@@ -18,19 +18,19 @@ You can locate `{zone_id}` and `{account_id}` arguments based on the [Find zone
 The `{job_id}` argument is numeric, like 123456.
 The `{dataset_id}` argument indicates the log category (such as `http_requests` or `audit_logs`).
 
-| Operation | Description                                 | API                                                                                                                                                                                              |
+| Operation | Description                                 | API                                                                                            |
 | --------- | ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                                             |
-| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)                                     |
-| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                                                 |
-| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)        |
+| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                      |
+| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
+| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                        |
+| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
 | `GET`     | Retrieve all available fields for a dataset | [Documentation](/api/resources/logpush/subresources/datasets/subresources/fields/methods/get/) |
-| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                                      |
-| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                           |
-| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/) |
-| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                                      |
-| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                      |
-| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                           |
+| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                      |
+| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                      |
+| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/)             |
+| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
+| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
+| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                  |
 
 For concrete examples, refer to the tutorials in [Logpush examples](/logs/logpush/examples/).
 
@@ -47,25 +47,25 @@ Before creating a new job, ownership of the destination must be proven.
 To issue an ownership challenge token to your destination:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/ownership"
-  method="POST"
-  json={{
-    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-  }}
+	path="/zones/{zone_id}/logpush/ownership"
+	method="POST"
+	json={{
+		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+	}}
 />
 
 A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path, if appropriate for your destination):
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "valid": true,
-    "message": "",
-    "filename": "<PATH_TO_CHALLENGE_FILE>.txt"
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"valid": true,
+		"message": "",
+		"filename": "<PATH_TO_CHALLENGE_FILE>.txt"
+	},
+	"success": true
 }
 ```
 
@@ -138,23 +138,23 @@ For more information on the value for your cloud storage provider, consult the f
 To check if a destination is already in use:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/validate/destination/exists"
-  method="POST"
-  json={{
-    destination_conf: "s3://foo",
-  }}
+	path="/zones/{zone_id}/logpush/validate/destination/exists"
+	method="POST"
+	json={{
+		destination_conf: "s3://foo",
+	}}
 />
 
 Response
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "exists": false
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"exists": false
+	},
+	"success": true
 }
 ```
 
@@ -173,28 +173,28 @@ The kind parameter cannot be used to update existing Logpush jobs. You can only
 :::
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/jobs"
-  method="POST"
-  json={{
-    name: "<DOMAIN_NAME>",
-    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-    dataset: "http_requests",
-    output_options: {
-      field_names: [
-        "ClientIP",
-        "ClientRequestHost",
-        "ClientRequestMethod",
-        " ClientRequestURI",
-        "EdgeEndTimestamp",
-        "EdgeResponseBytes",
-        "EdgeResponseStatus",
-        "EdgeStartTimestamp",
+	path="/zones/{zone_id}/logpush/jobs"
+	method="POST"
+	json={{
+		name: "<DOMAIN_NAME>",
+		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+		dataset: "http_requests",
+		output_options: {
+			field_names: [
+				"ClientIP",
+				"ClientRequestHost",
+				"ClientRequestMethod",
+				" ClientRequestURI",
+				"EdgeEndTimestamp",
+				"EdgeResponseBytes",
+				"EdgeResponseStatus",
+				"EdgeStartTimestamp",
 				"RayID",
-      ],
+			],
 			timestamp_format: "rfc3339",
-    },
+		},
 		kind: "edge",
-  }}
+	}}
 />
 
 ## Options
@@ -205,7 +205,7 @@ If you are still using logpull_options, here are the options that you can custom
 
 1. **Fields** (optional): Refer to [Datasets](/logs/logpush/logpush-job/datasets/) for the currently available fields. The list of fields is also accessible directly from the API: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields`. Default fields: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields/default`.
 2. **Timestamp format** (optional): The format in which timestamp fields will be returned. Value options: `unixnano` (nanoseconds unit - default), `unix` (seconds unit), `rfc3339` (seconds unit).
-3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`.  To enable it, set `"CVE-2021-44228": true`.
+3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`. To enable it, set `"CVE-2021-44228": true`.
 
 :::note[Note]
 
@@ -215,26 +215,26 @@ The **CVE-2021-44228** parameter can only be set through the API at this time. U
 To check if the selected **logpull_options** are valid:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/validate/origin"
-  method="POST"
-  json={{
+	path="/zones/{zone_id}/logpush/validate/origin"
+	method="POST"
+	json={{
 		logpull_options:
 			"fields=RayID,ClientIP,EdgeStartTimestamp&timestamps=rfc3339&CVE-2021-44228=true",
 		dataset: "http_requests",
-  }}
+	}}
 />
 
 Response
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "valid": true,
-    "message": ""
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"valid": true,
+		"message": ""
+	},
+	"success": true
 }
 ```
 
@@ -280,10 +280,10 @@ When customer-configured sampling is applied, the `SampleInterval` field value i
 
 These parameters control the size of each upload batch — not how quickly data is delivered. Use them to prevent overloading your destination with uploads that are too large or too small.
 
-| Parameter | Description | Default |
-| --- | --- | --- |
-| `max_upload_bytes` | Maximum uncompressed file size of a batch of logs. | Varies by destination |
-| `max_upload_records` | Maximum number of log lines per batch. | 100,000 |
+| Parameter                     | Description                                                               | Default               |
+| ----------------------------- | ------------------------------------------------------------------------- | --------------------- |
+| `max_upload_bytes`            | Maximum uncompressed file size of a batch of logs.                        | Varies by destination |
+| `max_upload_records`          | Maximum number of log lines per batch.                                    | 100,000               |
 | `max_upload_interval_seconds` | Maximum time-span of log data per batch (used during catch-up scenarios). | Varies by destination |
 
 :::note
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
index 618a7f86d3a5d55..a9bd442099c837b 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
index 2068e23086295d9..452263a6cac1017 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
@@ -1,8 +1,8 @@
 ---
 pcx_content_type: reference
-title: CMB support by dataset 
+title: CMB support by dataset
 external_link: /data-localization/metadata-boundary/logpush-datasets/
 description: Learn about cmb support by dataset  in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
index 64c4408ce21b874..d57a162728ea19b 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
@@ -12,25 +12,25 @@ products:
 
 The datasets below describe the fields available by log category:
 
-* [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
-* [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
+- [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
+- [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
 
 ## API
 
 The list of fields can also be accessed directly from the API using the following endpoints:
 
-* For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
+- For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
 
-* For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
+- For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
 
 The `<DATASET>` argument indicates the log category. For example, `http_requests`, `spectrum_events`, `firewall_events`, `nel_reports`, or `dns_logs`.
 
 ## Availability
 
-* The availability of Logpush dataset fields depends on your subscription plan.
-* Zone-scoped HTTP requests are available in both Logpush and Logpull.
-* [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
-* All other datasets are only available through Logpush.
+- The availability of Logpush dataset fields depends on your subscription plan.
+- Zone-scoped HTTP requests are available in both Logpush and Logpull.
+- [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
+- All other datasets are only available through Logpush.
 
 ## Deprecation
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
index f21b39be05e2657..3916cd8f337d26e 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
@@ -49,7 +49,7 @@ Whether the response was cached or not.
 
 Type: `int`
 
-Integer value of response code. For more information refer to  [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
+Integer value of response code. For more information refer to [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
 
 ## SourceIP
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
index b44ea90a6fa6a98..d9de685d205d4d0 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
index 6b8090800495242..12b4d2e27bc5489 100644
--- a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
@@ -8,9 +8,8 @@ products:
   - logpush
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 Edge Log Delivery allows customers to send logs directly from Cloudflare’s edge to their destination of choice. You can configure the maximum interval for your log batches between 30 seconds and five minutes. However, you cannot specify a minimum interval for log batches, meaning that log files may be sent in shorter intervals than the maximum specified. Compared to Logpush, Edge Log Delivery sends logs with lower latency, more frequently, and in smaller batches.
 
 Edge Log Delivery is only available for HTTP request logs. Refer to the [API configuration](/logs/logpush/logpush-job/api-configuration/#kind) page for steps on how to configure a job to use Edge Log Delivery.
-
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
index 65b671327acdea2..e9823d82ca24e5c 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
@@ -42,9 +42,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
index 301c4bcbaf9e976..437fe5b4f67cf0f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
@@ -79,6 +79,7 @@ signedResourceTypes must be Object only (srt=o)
 ```
 
 To resolve this error, regenerate your SAS token using [Storage Explorer](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer) with the correct permissions:
+
 - Service: Blob-only (`ss=b`)
 - Resource type: Object-only (`srt=o`)
 - Permissions: Write-only
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
index bde5e5a6cadf67d..bfc9e8b76c9f8f2 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
@@ -40,22 +40,23 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 1. Register or use an existing zone for the dedicated egress IPs pool.
 2. Contact your account team to get the ID for your dedicated egress IPs pool.
 3. Make a `PATCH` request to the [Edit Zone Setting](/api/resources/zones/subresources/settings/methods/edit/) endpoint:
-  - Specify `aegis` as the setting ID in the URL.
-  - In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
+
+- Specify `aegis` as the setting ID in the URL.
+- In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
 
 <APIRequest
-  path="/zones/{zone_id}/settings/{setting_id}"
-  method="PATCH"
-  json={{
-		  "id": "aegis",
-			"value": {
-				"enabled": true,
-				"pool_id": "<YOUR_EGRESS_POOL_ID>",
-				},
+	path="/zones/{zone_id}/settings/{setting_id}"
+	method="PATCH"
+	json={{
+		id: "aegis",
+		value: {
+			enabled: true,
+			pool_id: "<YOUR_EGRESS_POOL_ID>",
+		},
 	}}
 	parameters={{
-    setting_id: "aegis",
-  }}
+		setting_id: "aegis",
+	}}
 />
 
 ## 3. Proxy zone setup
@@ -66,7 +67,6 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 
 2. If needed, configure [origin rules](/rules/origin-rules/) to specify a custom port. This is useful if your destination only accepts traffic on a non standard port, for example `12345`. You can configure `logpush.yourdestinationendpoint.com` (without specifying a port, as Cloudflare by default only proxies traffic on HTTP/HTTPS ports) to proxy to `yourdestinationendpoint.com:12345`.
 
-
 ## 4. Configure Logpush
 
 1. Create a Logpush job with the following details:
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
index 037278d7af513e7..271f74a01e3f258 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
@@ -11,22 +11,20 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Push your Cloudflare logs to Elastic for instant visibility and insights. Enabling this integration with Elastic comes with a predefined dashboard to view all of your Cloudflare observability and security data with ease.
 
 The Cloudflare Logpush integration can be used in three different modes to collect data:
 
-* **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
-* **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
-* **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
+- **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
+- **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
+- **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
 
 :::note[Note]
 
-
 Elastic recommends the AWS S3 SQS mode.
 
-
 :::
 
 ## Enable Logpush Job in Cloudflare
@@ -44,17 +42,18 @@ Add the same custom header along with its value on both sides for additional sec
 For example, while creating a job along with a header and value for a particular dataset:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/jobs"
-  method="POST"
-  json={{
-    name: "<PUBLIC_DOMAIN>",
-    destination_conf: "https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
-    dataset: "http_requests",
-    output_options: {
-      field_names: ["RayID", "EdgeStartTimestamp"],
-      timestamp_format: "rfc3339"
-    }
-  }}
+	path="/zones/{zone_id}/logpush/jobs"
+	method="POST"
+	json={{
+		name: "<PUBLIC_DOMAIN>",
+		destination_conf:
+			"https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
+		dataset: "http_requests",
+		output_options: {
+			field_names: ["RayID", "EdgeStartTimestamp"],
+			timestamp_format: "rfc3339",
+		},
+	}}
 />
 
 ## Enable the Integration in Elastic
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
index 559b432c8b43b4e..79d92a490df72b5 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
@@ -39,9 +39,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
index 54b030d14362706..bc517b5783e0a01 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 To configure a QRadar/Cloudflare integration you have the option to use one of the following methods:
 
@@ -22,57 +22,113 @@ To send Cloudflare logs to QRadar you need to create a [Logpush job to HTTP endp
 ### Cloudflare Firewall events
 
 <APIRequest
-  method="POST"
-  path="/zones/{zone_id}/logpush/jobs"
-  json={{
-    name: "<NAME>",
-    output_options: {
-      field_names: [
-        "Action", "ClientIP", "ClientASN", "ClientASNDescription", "ClientCountry", "ClientIPClass",
-        "ClientRefererHost", "ClientRefererPath", "ClientRefererQuery", "ClientRefererScheme",
-        "ClientRequestHost", "ClientRequestMethod", "ClientRequestPath", "ClientRequestProtocol",
-        "ClientRequestQuery", "ClientRequestScheme", "ClientRequestUserAgent", "EdgeColoCode",
-        "EdgeResponseStatus", "Kind", "MatchIndex", "Metadata", "OriginResponseStatus",
-        "OriginatorRayID", "RayID", "RuleID", "Source", "Datetime"
-      ],
-      timestamp_format: "rfc3339"
-    },
-    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-    max_upload_bytes: 5000000,
-    max_upload_records: 1000,
-    dataset: "firewall_events",
-    enabled: true
-  }}
+	method="POST"
+	path="/zones/{zone_id}/logpush/jobs"
+	json={{
+		name: "<NAME>",
+		output_options: {
+			field_names: [
+				"Action",
+				"ClientIP",
+				"ClientASN",
+				"ClientASNDescription",
+				"ClientCountry",
+				"ClientIPClass",
+				"ClientRefererHost",
+				"ClientRefererPath",
+				"ClientRefererQuery",
+				"ClientRefererScheme",
+				"ClientRequestHost",
+				"ClientRequestMethod",
+				"ClientRequestPath",
+				"ClientRequestProtocol",
+				"ClientRequestQuery",
+				"ClientRequestScheme",
+				"ClientRequestUserAgent",
+				"EdgeColoCode",
+				"EdgeResponseStatus",
+				"Kind",
+				"MatchIndex",
+				"Metadata",
+				"OriginResponseStatus",
+				"OriginatorRayID",
+				"RayID",
+				"RuleID",
+				"Source",
+				"Datetime",
+			],
+			timestamp_format: "rfc3339",
+		},
+		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+		max_upload_bytes: 5000000,
+		max_upload_records: 1000,
+		dataset: "firewall_events",
+		enabled: true,
+	}}
 />
 
-
 ### Cloudflare HTTP events
 
 <APIRequest
-  method="POST"
-  path="/zones/{zone_id}/logpush/jobs"
-  json={{
-    name: "<NAME>",
-    output_options: {
-      field_names: [
-        "ClientRequestMethod", "EdgeResponseStatus", "ClientIP", "ClientSrcPort", "CacheCacheStatus",
-        "ClientCountry", "ClientDeviceType", "ClientIPClass", "ClientMTLSAuthCertFingerprint", "ClientMTLSAuthStatus",
-        "ClientRegionCode", "ClientRequestBytes", "ClientRequestHost", "ClientRequestPath", "ClientRequestProtocol",
-        "ClientRequestReferer", "ClientRequestScheme", "ClientRequestSource", "ClientRequestURI", "ClientRequestUserAgent",
-        "ClientSSLCipher", "ClientSSLProtocol", "ClientXRequestedWith", "EdgeEndTimestamp", "EdgeRequestHost",
-        "EdgeResponseBodyBytes", "EdgeResponseBytes", "EdgeServerIP", "EdgeStartTimestamp", "SecurityActions",
-        "SecurityRuleIDs", "SecuritySources", "OriginIP", "OriginResponseStatus", "OriginSSLProtocol", "ParentRayID",
-        "RayID", "SecurityAction", "WAFAttackScore", "SecurityRuleID", "SecurityRuleDescription", "WAFSQLiAttackScore",
-        "WAFXSSAttackScore", "EdgeStartTimestamp"
-      ],
-      timestamp_format: "rfc3339"
-    },
-    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-    max_upload_bytes: 5000000,
-    max_upload_records: 1000,
-    dataset: "http_requests",
-    enabled: true
-  }}
+	method="POST"
+	path="/zones/{zone_id}/logpush/jobs"
+	json={{
+		name: "<NAME>",
+		output_options: {
+			field_names: [
+				"ClientRequestMethod",
+				"EdgeResponseStatus",
+				"ClientIP",
+				"ClientSrcPort",
+				"CacheCacheStatus",
+				"ClientCountry",
+				"ClientDeviceType",
+				"ClientIPClass",
+				"ClientMTLSAuthCertFingerprint",
+				"ClientMTLSAuthStatus",
+				"ClientRegionCode",
+				"ClientRequestBytes",
+				"ClientRequestHost",
+				"ClientRequestPath",
+				"ClientRequestProtocol",
+				"ClientRequestReferer",
+				"ClientRequestScheme",
+				"ClientRequestSource",
+				"ClientRequestURI",
+				"ClientRequestUserAgent",
+				"ClientSSLCipher",
+				"ClientSSLProtocol",
+				"ClientXRequestedWith",
+				"EdgeEndTimestamp",
+				"EdgeRequestHost",
+				"EdgeResponseBodyBytes",
+				"EdgeResponseBytes",
+				"EdgeServerIP",
+				"EdgeStartTimestamp",
+				"SecurityActions",
+				"SecurityRuleIDs",
+				"SecuritySources",
+				"OriginIP",
+				"OriginResponseStatus",
+				"OriginSSLProtocol",
+				"ParentRayID",
+				"RayID",
+				"SecurityAction",
+				"WAFAttackScore",
+				"SecurityRuleID",
+				"SecurityRuleDescription",
+				"WAFSQLiAttackScore",
+				"WAFXSSAttackScore",
+				"EdgeStartTimestamp",
+			],
+			timestamp_format: "rfc3339",
+		},
+		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+		max_upload_bytes: 5000000,
+		max_upload_records: 1000,
+		dataset: "http_requests",
+		enabled: true,
+	}}
 />
 
 Cloudflare checks the accessibility of the IP address, port, and validates the certificate of the HTTP Receive log source. If all parameters are valid, a Logpush is created, and starts to send events to HTTP Receiver log source.
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
index c9e507400e4736f..e30073dde0691a1 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
@@ -79,7 +79,7 @@ When configuring your Logpush job using IAM Access Keys, ensure that the IAM use
 kinesis://<STREAM_NAME>?region=<AWS_REGION>&access-key-id=<AWS_ACCESS_KEY_ID>&secret-access-key=<AWS_SECRET_ACCESS_KEY>
 ```
 
-### IAM Access Key example 
+### IAM Access Key example
 
 ```bash
 $ curl https://api.cloudflare.com/client/v4/zones/$ZONE_TAG/logpush/jobs \
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
index b5a8ad2efe5d08a..c8e74bd58ce5b1c 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about exabeam in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
index ebd93fd74f3fe4e..e035c9cab36b111 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about sekoia in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
index 33a79b6922e260b..9b27ff95df6e41f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about taegis in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/filters.mdx b/src/content/docs/logs/logpush/logpush-job/filters.mdx
index e3d0dec59462d05..70fd97b0bc41bcc 100644
--- a/src/content/docs/logs/logpush/logpush-job/filters.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/filters.mdx
@@ -100,11 +100,10 @@ Here is an example request using cURL via API:
 To set filters through the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
- 
+
    For account: <DashButton url="/?to=/:account/logs" />
- 
-   For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
+   For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select the dataset you want to push to a storage service. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
 3. Below **Select data fields**, in the **Filter** section, you can set up your filters.
diff --git a/src/content/docs/logs/logpush/logpush-job/index.mdx b/src/content/docs/logs/logpush/logpush-job/index.mdx
index 552977e3e38e2b6..9f631a5d38edfd0 100644
--- a/src/content/docs/logs/logpush/logpush-job/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: Configure and manage Logpush job settings.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
index 69caff8184b218b..0c4922d8910409d 100644
--- a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
@@ -70,17 +70,17 @@ Your bucket's IAM/access controls and Cloudflare account security are the primar
 
 ## Which destinations require an ownership challenge?
 
-| Destination | Ownership challenge required |
-| --- | --- |
-| AWS S3 | Yes (or use access key/secret key) |
-| Google Cloud Storage | Yes |
-| Azure Blob Storage | Yes |
-| Sumo Logic | Yes |
-| S3-compatible storage | No |
-| HTTP endpoints | No |
-| Datadog | No |
-| Splunk | No |
-| New Relic | No |
+| Destination           | Ownership challenge required       |
+| --------------------- | ---------------------------------- |
+| AWS S3                | Yes (or use access key/secret key) |
+| Google Cloud Storage  | Yes                                |
+| Azure Blob Storage    | Yes                                |
+| Sumo Logic            | Yes                                |
+| S3-compatible storage | No                                 |
+| HTTP endpoints        | No                                 |
+| Datadog               | No                                 |
+| Splunk                | No                                 |
+| New Relic             | No                                 |
 
 For destinations that do not require an ownership challenge, Cloudflare uses alternative authentication methods such as API keys or tokens.
 
diff --git a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
index 090c84dab4fef92..b69e56fe07a33a4 100644
--- a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
+++ b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
@@ -9,12 +9,12 @@ products:
   - logs
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components";
 
 Cloudflare will deploy some updates to security-related fields in Cloudflare Logs. These updates will affect the following datasets:
 
-* [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
-* [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
+- [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
+- [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
 
 ## Timeline
 
@@ -26,18 +26,18 @@ For the log fields being added, Cloudflare will gradually start adding them to l
 
 For the log fields being renamed, Cloudflare will:
 
-* **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
-* **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
+- **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
+- **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
 
 For the log fields being removed, Cloudflare is announcing them as deprecated. Their removal from logs datasets will occur on August 1, 2023.
 
 In addition to these Cloudflare Logs changes, Cloudflare will also add new security-related fields to the following [GraphQL datasets](/analytics/graphql-api/features/data-sets/):
 
-* `httpRequestsAdaptive `
-* `httpRequestsAdaptiveGroups`
-* `firewallEventsAdaptive`
-* `firewallEventsAdaptiveGroups`
-* `firewallEventsAdaptiveByTimeGroups`
+- `httpRequestsAdaptive `
+- `httpRequestsAdaptiveGroups`
+- `firewallEventsAdaptive`
+- `firewallEventsAdaptiveGroups`
+- `firewallEventsAdaptiveByTimeGroups`
 
 ### Phase 2 (August 1, 2023)
 
@@ -49,27 +49,23 @@ For the log fields being removed, Cloudflare will also remove them from the Clou
 
 The following concepts are used below in the reviewed field descriptions:
 
-* **Terminating action:** One of the following actions:
-
-  * `block`
-  * `js_challenge`
-  * `managed_challenge`
-  * `challenge` (*Interactive Challenge*)
+- **Terminating action:** One of the following actions:
+  - `block`
+  - `js_challenge`
+  - `managed_challenge`
+  - `challenge` (_Interactive Challenge_)
 
 For more information on these actions, refer to the [Actions](/ruleset-engine/rules-language/actions/) reference in the Rules language documentation.
 
-* **Security rule:** One of the following rule types:
-
-  * [WAF managed rule](/waf/managed-rules/)
-  * [WAF custom rule](/waf/custom-rules/)
-  * [WAF rate limiting rule](/waf/rate-limiting-rules/)
+- **Security rule:** One of the following rule types:
+  - [WAF managed rule](/waf/managed-rules/)
+  - [WAF custom rule](/waf/custom-rules/)
+  - [WAF rate limiting rule](/waf/rate-limiting-rules/)
 
 ## HTTP Requests dataset changes
 
 The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) dataset according to the two-phase strategy outlined in the [timeline](#timeline):
 
-
-
 | New field name            | Type         | Description                                                                        | Old field name<br/>(deprecated on Aug 1, 2023) |
 | ------------------------- | ------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------- |
 | `SecurityRuleID`          | String       | Rule ID of the security rule that triggered a terminating action, if any.          | `WAFRuleID`                                    |
@@ -79,12 +75,8 @@ The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpus
 | `SecurityActions`         | String Array | Array of actions that Cloudflare security products performed on the request.       | `FirewallMatchesActions`                       |
 | `SecuritySources`         | String Array | Array of Cloudflare security products that matched the request.                    | `FirewallMatchesSources`                       |
 
-
-
 The following fields are now deprecated and they will be removed from the HTTP Requests dataset on August 1, 2023:
 
-
-
 | Deprecated field name | Notes                                                                 |
 | --------------------- | --------------------------------------------------------------------- |
 | `WAFProfile`          | Used in the previous version of WAF managed rules (now deprecated).   |
@@ -92,44 +84,30 @@ The following fields are now deprecated and they will be removed from the HTTP R
 | `EdgeRateLimitID`     | Used in the previous version of rate limiting rules (now deprecated). |
 | `SecurityLevel`       | N/A                                                                   |
 
-
-
 ## Firewall Events dataset changes
 
 The following fields will be added to the [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/) dataset:
 
-
-
 | Field name    | Type   | Description                                                        |
 | ------------- | ------ | ------------------------------------------------------------------ |
 | `Description` | String | The description of the rule triggered by the request.              |
 | `Ref`         | String | The user-defined identifier for the rule triggered by the request. |
 
-
-
 ## Changes to GraphQL datasets
 
 Cloudflare will add the following fields to the `httpRequestsAdaptive `and `httpRequestsAdaptiveGroups `datasets:
 
-
-
 | Field name       | Type   | Description                                                              |
 | ---------------- | ------ | ------------------------------------------------------------------------ |
 | `securityAction` | String | Action of the security rule that triggered a terminating action, if any. |
 | `securitySource` | String | Source of the security rule that triggered a terminating action, if any. |
 
-
-
 Cloudflare will also add the following field to the `firewallEventsAdaptive`, `firewallEventsAdaptiveGroups`, and `firewallEventsAdaptiveByTimeGroups` datasets:
 
-
-
 | Field name    | Type   | Description                                           |
 | ------------- | ------ | ----------------------------------------------------- |
 | `description` | String | The description of the rule triggered by the request. |
 
-
-
 These new fields will become gradually available.
 
 For more information on the available datasets, refer to [GraphQL datasets](/analytics/graphql-api/features/data-sets/).
@@ -143,8 +121,8 @@ After updating Logpush jobs, you may need to update external filters or reports
 ### Update Logpush job in the dashboard
 
 1. In the Cloudflare dashboard, go to the **Logpush** page.
- 
-    <DashButton url="/?to=/:account/:zone/analytics/logs" />
+
+   <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select **Edit** next to the Logpush job you wish to edit.
 3. Under **Select data fields**, update the fields in your job. The new security log fields are available under **General**.
@@ -152,7 +130,7 @@ After updating Logpush jobs, you may need to update external filters or reports
 
 ### Update Logpush job via API
 
-Follow the instructions in [Update output\_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
+Follow the instructions in [Update output_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
 
 ### Update Logpush job via Terraform
 
diff --git a/src/content/docs/logs/reference/change-notices/index.mdx b/src/content/docs/logs/reference/change-notices/index.mdx
index 73f10f158563f08..9457944fa3b5f78 100644
--- a/src/content/docs/logs/reference/change-notices/index.mdx
+++ b/src/content/docs/logs/reference/change-notices/index.mdx
@@ -11,6 +11,6 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/reference/clientrequestsource.mdx b/src/content/docs/logs/reference/clientrequestsource.mdx
index 142639187d95beb..13558a727481adb 100644
--- a/src/content/docs/logs/reference/clientrequestsource.mdx
+++ b/src/content/docs/logs/reference/clientrequestsource.mdx
@@ -11,8 +11,6 @@ products:
 
 The possible values for the `ClientRequestSource` field are the following:
 
-
-
 | Value | Request source     | Description                                                                                                                             |
 | ----- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
 | `0`   | unknown            | Should never happen.                                                                                                                    |
@@ -28,4 +26,3 @@ The possible values for the `ClientRequestSource` field are the following:
 | `10`  | sslDetector        | A request made by Cloudflare's [SSL Detector system](https://blog.cloudflare.com/ssl-tls-recommender/).                                 |
 | `11`  | earlyHintsCache    | An [Early Hint request](https://blog.cloudflare.com/early-hints/).                                                                      |
 | `12`  | inBrowserChallenge | An end user request caused by a Cloudflare security product (Challenges, JavaScript Detections). These requests never reach the origin. |
-
diff --git a/src/content/docs/logs/reference/index.mdx b/src/content/docs/logs/reference/index.mdx
index 2dee7feaa4467ed..31fafb51510ff9a 100644
--- a/src/content/docs/logs/reference/index.mdx
+++ b/src/content/docs/logs/reference/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 These reference resources are useful for gaining a more in-depth understanding of the terminology and status codes that are part of the Cloudflare Logs data. This information is especially important when integrating your data with third-party tools:
 
diff --git a/src/content/docs/logs/reference/security-fields.mdx b/src/content/docs/logs/reference/security-fields.mdx
index c1dfac2c6154b28..af844e299e4e427 100644
--- a/src/content/docs/logs/reference/security-fields.mdx
+++ b/src/content/docs/logs/reference/security-fields.mdx
@@ -13,8 +13,6 @@ The Security fields contain rules to block requests that contain specific types
 
 ## SecurityActions
 
-
-
 | Value                                  | Action         | Description                                                                                                                                                |
 | -------------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `unknown`                              | Unknown        | Take no other action.                                                                                                                                      |
@@ -27,19 +25,15 @@ The Security fields contain rules to block requests that contain specific types
 | `challengeSolved`                      | Allow          | Allow once interactive challenge solved.                                                                                                                   |
 | `challengeBypassed`                    | Allow          | Interactive challenge is not issued again because the visitor had previously passed an interactive challenge and a valid `cf_clearance` cookie is present. |
 | `jschallengeSolved`                    | Allow          | Allow once non-interactive challenge solved.                                                                                                               |
-| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                  |
+| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                 |
 | `bypass`                               | Allow          | Bypass all subsequent firewall rules.                                                                                                                      |
 | `managedChallenge`                     | Challenge Drop | Issue managed challenge.                                                                                                                                   |
 | `managedChallengeNonInteractiveSolved` | Allow          | Allow once the managed challenge is solved via non-interactive interstitial page.                                                                          |
 | `managedChallengeInteractiveSolved`    | Allow          | Allow once the managed challenged is solved via interactive interstitial page.                                                                             |
 | `managedChallengeBypassed`             | Allow          | Challenge was not presented because visitor had clearance from previous challenge.                                                                         |
 
-
-
 ## SecuritySources
 
-
-
 | Value             | Description                                                                                                      |
 | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
 | `unknown`         | Used if an event is received from a new source but the logging system has not been updated.                      |
diff --git a/src/content/docs/logs/reference/waf-fields.mdx b/src/content/docs/logs/reference/waf-fields.mdx
index 421f434955eb3f0..e53ba194338c1b2 100644
--- a/src/content/docs/logs/reference/waf-fields.mdx
+++ b/src/content/docs/logs/reference/waf-fields.mdx
@@ -13,8 +13,6 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 
 ## WAF Action
 
-
-
 | Value                                      | Action          | Description                                  |
 | ------------------------------------------ | --------------- | -------------------------------------------- |
 | <span style="font-weight: 400;">`0`</span> | Unknown         | Take no other action.                        |
@@ -24,11 +22,9 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 | <span style="font-weight: 400;">`4`</span> | Challenge Drop  | Unused.                                      |
 | <span style="font-weight: 400;">`5`</span> | Log             | Take no action other than logging the event. |
 
-
-
 ## Deprecated fields for internal Cloudflare use
 
 The values of these fields are subject to change by Cloudflare at any time and are irrelevant for customer data analysis:
 
-* WAFFlags
-* WAFMatchedVar
+- WAFFlags
+- WAFMatchedVar
diff --git a/src/content/docs/magic-transit/about.mdx b/src/content/docs/magic-transit/about.mdx
index d24ff959ee90edf..dc0086ba6a2fe2a 100644
--- a/src/content/docs/magic-transit/about.mdx
+++ b/src/content/docs/magic-transit/about.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: About Magic Transit
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Magic Transit is a network security and performance solution that offers Distributed Denial of Service ([DDoS](/ddos-protection/)) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 
diff --git a/src/content/docs/magic-transit/alerts.mdx b/src/content/docs/magic-transit/alerts.mdx
index c0c7de7a4836d78..f8cadf60286d59c 100644
--- a/src/content/docs/magic-transit/alerts.mdx
+++ b/src/content/docs/magic-transit/alerts.mdx
@@ -6,10 +6,9 @@ products:
   - magic-transit
 sidebar:
   order: 14
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your network.
 
diff --git a/src/content/docs/magic-transit/analytics/index.mdx b/src/content/docs/magic-transit/analytics/index.mdx
index 04ca8e61b7d11ce..dfe4e5e0295bb7b 100644
--- a/src/content/docs/magic-transit/analytics/index.mdx
+++ b/src/content/docs/magic-transit/analytics/index.mdx
@@ -13,13 +13,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
 		traceRoutes: "/magic-transit/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
-		 }}
-/>
\ No newline at end of file
+		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/",
+	}}
+/>
diff --git a/src/content/docs/magic-transit/analytics/network-analytics.mdx b/src/content/docs/magic-transit/analytics/network-analytics.mdx
index 14e7c6f5b8cbfd3..c872539c3620160 100644
--- a/src/content/docs/magic-transit/analytics/network-analytics.mdx
+++ b/src/content/docs/magic-transit/analytics/network-analytics.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit Network Analytics
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Magic Transit"
+		magicWord: "Magic Transit",
 	}}
 />
diff --git a/src/content/docs/magic-transit/analytics/packet-captures.mdx b/src/content/docs/magic-transit/analytics/packet-captures.mdx
index 0dd8a83c52fb2da..8ef49043b64053d 100644
--- a/src/content/docs/magic-transit/analytics/packet-captures.mdx
+++ b/src/content/docs/magic-transit/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
index e20b8573ade07d3..6f46709874eb1bc 100644
--- a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
+++ b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
@@ -11,9 +11,10 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Magic Transit" }}
 />
diff --git a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
index ec044cf25d36e9c..347e8ce8854d5cd 100644
--- a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
@@ -11,8 +11,10 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Magic Transit" }} />
+	params={{ productName: "Magic Transit" }}
+/>
diff --git a/src/content/docs/magic-transit/changelog.mdx b/src/content/docs/magic-transit/changelog.mdx
index df426867ae71afe..f3d81cf0accb7be 100644
--- a/src/content/docs/magic-transit/changelog.mdx
+++ b/src/content/docs/magic-transit/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/magic-transit/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="magic-transit" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="magic-transit"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/magic-transit/cloudflare-ips.mdx b/src/content/docs/magic-transit/cloudflare-ips.mdx
index 4ee1316b242c1ab..9812bcc56adb708 100644
--- a/src/content/docs/magic-transit/cloudflare-ips.mdx
+++ b/src/content/docs/magic-transit/cloudflare-ips.mdx
@@ -8,23 +8,26 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="magic-transit/cloudflare-ips"
 	product="networking-services"
 	params={{
 		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
-		mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
-		}} />
+		mtLpStaticRoute:
+			"/magic-transit/how-to/configure-routes/#configure-static-routes",
+		mtLpBgpPeering:
+			"/magic-transit/how-to/configure-routes/#configure-bgp-routes",
+	}}
+/>
 
 ## Check your Cloudflare IPs
 
 <Render
-  file="check-leased-ips"
+	file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "Anycast IPs for Magic Transit"
+		product: "Anycast IPs for Magic Transit",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/get-started.mdx b/src/content/docs/magic-transit/get-started.mdx
index eec224e8dbadd55..8efc46ed319d06b 100644
--- a/src/content/docs/magic-transit/get-started.mdx
+++ b/src/content/docs/magic-transit/get-started.mdx
@@ -10,6 +10,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Magic Transit" }} />
\ No newline at end of file
+<Render
+	file="magic-transit/get-started"
+	product="networking-services"
+	params={{ magicWord: "Magic Transit" }}
+/>
diff --git a/src/content/docs/magic-transit/glossary.mdx b/src/content/docs/magic-transit/glossary.mdx
index b14631d9375bd84..089812e9c6ecd3e 100644
--- a/src/content/docs/magic-transit/glossary.mdx
+++ b/src/content/docs/magic-transit/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Magic Transit documentation.
 products:
   - magic-transit
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Magic Transit documentation.
 
diff --git a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
index ec7bc738458e71d..e8f018925c30330 100644
--- a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
+++ b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
@@ -8,7 +8,15 @@ sidebar:
   order: 5
 ---
 
-import { APIRequest, DashButton, Details, GlossaryTooltip, Render, Tabs, TabItem } from "~/components"
+import {
+	APIRequest,
+	DashButton,
+	Details,
+	GlossaryTooltip,
+	Render,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 ## Onboard prefixes
 
@@ -67,11 +75,11 @@ You should only use one control method per prefix at any given time. Mixing mult
 Create a [POST request](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/create/) to add a BGP prefix. For example:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
-  method="POST"
-  json={{
-    "cidr": "192.0.2.0/24"
-  }}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
+	method="POST"
+	json={{
+		cidr: "192.0.2.0/24",
+	}}
 />
 
 ### Advertise or withdraw a BGP prefix
@@ -117,7 +125,7 @@ Refer to [Safely withdraw a BYOIP prefix](#safely-withdraw-a-byoip-prefix) for m
 
 ### Delete an IP prefix
 
-You can only delete a prefix with an *Unapproved* status. To delete prefixes with a different status, contact your administrator or account manager.
+You can only delete a prefix with an _Unapproved_ status. To delete prefixes with a different status, contact your administrator or account manager.
 
 1. Go to the **Routes** page.
 
@@ -137,11 +145,11 @@ BGP has different mechanisms to control route priorities which are set by the pe
 Refer to the following example for how to prepend AS13335 three times to a BGP prefix:
 
 <APIRequest
-path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-method="PATCH"
-json={{
-	"asn_prepend_count": 3
-}}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+	method="PATCH"
+	json={{
+		asn_prepend_count: 3,
+	}}
 />
 
 AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once provides a smoother traffic migration and minimizes packet loss during a change of provider.
@@ -155,8 +163,6 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
 - **Introduce new provider**: You begin advertising the same prefix from your alternate provider with a standard (shorter) `AS_PATH`.
 - **Final state**: External networks now receive two advertisements: the prepended route through Cloudflare and the non-prepended route through your new provider. The external network will select a path based on its BGP policy rules.
 
-
-
 :::caution
 Cloudflare's internal network enforces local preference for traffic delivery to Magic Transit, even if a more specific or shorter path route is available on the public Internet. Withdraw the prefix from Cloudflare to avoid delivery of Cloudflare-sourced traffic over Magic Transit. This preference is local to our internal network and does not impact the route decision process of other networks.
 
@@ -165,27 +171,32 @@ For example, if you have a CDN zone with a Magic Transit-protected origin that i
 
 ## Safely withdraw a BYOIP prefix
 
-<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
+<Render
+	file="magic-transit/safely-withdraw-byoip-prefix"
+	product="networking-services"
+/>
 
 ## BGP control to Magic Transit Virtual Network routing table
 
 ### Automatically announce and withdraw anycast-based Magic BGP routes
 
 If you use CNI with Dataplane v2, GRE or IPsec tunnels, you can:
+
 - Automatically withdraw your prefixes from Cloudflare's global edge infrastructure when you withdraw all matching BGP learned prefixes from the Magic Transit Virtual Network routing table.
 - Automatically advertise your prefixes through Cloudflare's global edge infrastructure when you have at least one matching BGP learned prefix in the Magic Transit Virtual Network routing table.
 
 To enable automatic global announcement and withdrawal, enable this feature on the BGP prefix using the [Addressing API](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/edit/). For example:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-  method="PATCH"
-  json={{
-    "auto_advertise_withdraw": true
-  }}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+	method="PATCH"
+	json={{
+		auto_advertise_withdraw: true,
+	}}
 />
 
 Once you configure this for a BGP prefix, Cloudflare applies the following logic:
+
 - If there are no BGP routes in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare withdraws the BGP prefix.
 - If there is at least one BGP route in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare announces the BGP prefix.
 
@@ -316,7 +327,10 @@ If you use CNI with Dataplane v2, GRE or IPsec tunnels to on-ramp your network t
 
 Magic Transit supports both static routing and BGP to steer traffic from Cloudflare's network to your configured off-ramps (GRE tunnels, IPsec tunnels, or CNI). Cloudflare does not currently support advertisement of routes for traffic engineering purposes. As a best practice to reduce last-hop latency, consider scoping your routes regionally.
 
-<Render file="reference/traffic-steering-region-codes" product="networking-services" />
+<Render
+	file="reference/traffic-steering-region-codes"
+	product="networking-services"
+/>
 
 The default setting for static route regions is **All Regions**. Configure scoping for your traffic in the **Region code** section when [adding](/magic-transit/how-to/configure-routes/#create-a-static-route) or [editing](/magic-transit/how-to/configure-routes/#edit-a-static-route) a static route.
 
diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx
index c3053044b8b28e3..0dfce207230821b 100644
--- a/src/content/docs/magic-transit/how-to/configure-routes.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx
@@ -11,7 +11,7 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -21,12 +21,16 @@ import { Render } from "~/components"
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT:
+			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table"
+		routingTableName: "Magic Transit Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
index af1eee331945798..ab317378e353ddc 100644
--- a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
@@ -14,23 +14,31 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
+		unifiedRoutingURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
index ccf843678ccbee2..7910debecdaac0e 100644
--- a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
+++ b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
@@ -7,6 +7,6 @@ head: []
 description: You can determine which users have, or do not have, configuration edit access for Magic products.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="magic-user-role" product="networking-services" />
diff --git a/src/content/docs/magic-transit/how-to/index.mdx b/src/content/docs/magic-transit/how-to/index.mdx
index 962bded34f466cd..a80f260452a9bd5 100644
--- a/src/content/docs/magic-transit/how-to/index.mdx
+++ b/src/content/docs/magic-transit/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
index b08bce6faedffc0..95d51e29e27e30d 100644
--- a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
@@ -8,6 +8,9 @@ sidebar:
   order: 6
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
\ No newline at end of file
+<Render
+	file="magic-transit/safely-withdraw-byoip-prefix"
+	product="networking-services"
+/>
diff --git a/src/content/docs/magic-transit/network-flow.mdx b/src/content/docs/magic-transit/network-flow.mdx
index 9af74ab7d1573b5..d77808bebde34fe 100644
--- a/src/content/docs/magic-transit/network-flow.mdx
+++ b/src/content/docs/magic-transit/network-flow.mdx
@@ -6,16 +6,15 @@ products:
   - magic-transit
 sidebar:
   order: 10
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
 	}}
 />
diff --git a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
index 99ee9ad379632a8..7218ba148af08d2 100644
--- a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
@@ -14,11 +14,13 @@ import { Render } from "~/components";
 	file="tunnel-health/check-tunnel-healthchecks-dash"
 	product="networking-services"
 	params={{
-		dashInfo: "The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
+		dashInfo:
+			"The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
 		graphQL: "/magic-transit/analytics/query-tunnel-health/",
-		notificationsPath: "[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
+		notificationsPath:
+			"[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/magic-transit/analytics/network-analytics/"
+		networkAnalytics: "/magic-transit/analytics/network-analytics/",
 	}}
 />
 
@@ -26,7 +28,7 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
 />
 
@@ -34,4 +36,4 @@ import { Render } from "~/components";
 
 If you received a tunnel health alert but are unsure whether it affects your traffic, refer to [Troubleshoot connectivity](/magic-transit/troubleshooting/connectivity/) to determine whether the alert is relevant.
 
-If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
\ No newline at end of file
+If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
diff --git a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
index d606ec4dcd288b1..32dcf34acba8937 100644
--- a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation:
+			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/network-health/index.mdx b/src/content/docs/magic-transit/network-health/index.mdx
index 909456bebc21630..ac18e64e89dac4c 100644
--- a/src/content/docs/magic-transit/network-health/index.mdx
+++ b/src/content/docs/magic-transit/network-health/index.mdx
@@ -8,23 +8,23 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Magic Transit uses health check probes to determine the status of tunnels. Cloudflare uses this information to steer traffic through the best available route and warn you about potential issues with a tunnel. Service-level indicators (SLIs) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [How Cloudflare calculates tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/) for more information about SLIs and SLOs.
 
 There are two types of health checks available: endpoint and tunnel health checks.
 
- - Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
+- Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
 
-	Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
+  Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
 
-	During onboarding, you specify IP addresses to configure endpoint health checks.
+  During onboarding, you specify IP addresses to configure endpoint health checks.
 
 - Tunnel health checks monitor the status of the tunnels that route traffic from Cloudflare to your origin network. Magic Transit relies on health checks to steer traffic to the best available routes.
 
-	During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
+  During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
 
-	You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
+  You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
 
 Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/) for a deep dive into the different types of health checks, what they do, and how they work.
 
@@ -32,10 +32,10 @@ Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/)
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
 />
 
 Refer to the following pages for details on how to use the various network health checks available.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
index b734e7357208bff..3fedb7f8c2cb1a3 100644
--- a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
+++ b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
@@ -14,7 +14,7 @@ tags:
   - ICMP
 ---
 
-import { CURL, Render, DashButton } from '~/components';
+import { CURL, Render, DashButton } from "~/components";
 
 Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
 
@@ -43,32 +43,35 @@ Refer to the [API documentation](/api/resources/diagnostics/subresources/endpoin
 <Render file="account-id-api-key" product="networking-services" />
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-  method="POST"
-  json={{
-    "check_type": "icmp",
-    "endpoint": "8.31.160.1",
-    "name": "Datacenter 1 - primary"
-  }}
+	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+	method="POST"
+	json={{
+		check_type: "icmp",
+		endpoint: "8.31.160.1",
+		name: "Datacenter 1 - primary",
+	}}
 />
 
 ```json output
 {
-    "result": {
-        "id": "<HEALTH_CHECK_ID>",
-        "check_type": "icmp",
-        "endpoint": "8.31.160.1",
-        "name": "Datacenter 1 - primary"
-    },
-    "success": true,
-    "errors": [],
-    "messages": []
+	"result": {
+		"id": "<HEALTH_CHECK_ID>",
+		"check_type": "icmp",
+		"endpoint": "8.31.160.1",
+		"name": "Datacenter 1 - primary"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Query endpoint health checks with GraphQL
 
-<Render file="graphql/query-magic-transit-endpoint-health-checks" product="networking-services" />
+<Render
+	file="graphql/query-magic-transit-endpoint-health-checks"
+	product="networking-services"
+/>
 
 ## Configure alerts for endpoint health checks
 
@@ -77,23 +80,23 @@ You can set up alerts to be notified when the state of your endpoint's health is
 1. Make a `GET` request to get a list of IDs for all of the endpoint health checks configured:
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-  method="GET"
+	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+	method="GET"
 />
 
 ```json output
 {
-    "result": [
-        {
-            "id": "<HEALTH_CHECK_ID>",
-            "check_type": "icmp",
-            "endpoint": "8.31.160.1",
-            "name": "Datacenter 1 - primary"
-        }
-    ],
-    "success": true,
-    "errors": [],
-    "messages": []
+	"result": [
+		{
+			"id": "<HEALTH_CHECK_ID>",
+			"check_type": "icmp",
+			"endpoint": "8.31.160.1",
+			"name": "Datacenter 1 - primary"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -103,13 +106,13 @@ You can set up alerts to be notified when the state of your endpoint's health is
 <DashButton url="/?to=/:account/notifications" />
 
 4. Select **Add**.
-5. From the drop-down menu, select *Magic Transit*.
+5. From the drop-down menu, select _Magic Transit_.
 6. Select **Magic Endpoint Health Check Alert**.
 7. Provide a name for your new notification and optionally provide a description.
-8. In the *Service Level Objective (SLO)* drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
-	- **High** - 99%
-	- **Medium** - 98%
-	- **Low** - 97%
+8. In the _Service Level Objective (SLO)_ drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
+   - **High** - 99%
+   - **Medium** - 98%
+   - **Low** - 97%
 9. In the drop-down menu below SLOs, select the `id` value that matches the `id` you got through the API in step 1. This `id` should match the endpoint health check you want to get notifications for.
 10. Select your preferred notification method (such as email or webhooks).
 11. Select **Save**.
diff --git a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
index 5abf823c7864447..cc01a8092fae660 100644
--- a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
@@ -17,7 +17,8 @@ import { Render } from "~/components";
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",
-		addTunnelsPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels"
+		addTunnelsPath:
+			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
@@ -25,6 +26,6 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/network-interconnect.mdx b/src/content/docs/magic-transit/network-interconnect.mdx
index 44619ba947f13ef..d9cb97232b3510b 100644
--- a/src/content/docs/magic-transit/network-interconnect.mdx
+++ b/src/content/docs/magic-transit/network-interconnect.mdx
@@ -13,4 +13,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" />
\ No newline at end of file
+<Render file="magic-cni" product="networking-services" />
diff --git a/src/content/docs/magic-transit/on-demand.mdx b/src/content/docs/magic-transit/on-demand.mdx
index 019f50728fcda3c..75c387b34768ef6 100644
--- a/src/content/docs/magic-transit/on-demand.mdx
+++ b/src/content/docs/magic-transit/on-demand.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit on-demand
-
 ---
 
 If you have access to the Magic Transit on-demand option, you can [configure prefix advertisement](/byoip/concepts/dynamic-advertisement/best-practices/#configure-dynamic-advertisement) from the **IP Prefixes** page in your Cloudflare account home or through the [Cloudflare API](/api/resources/addressing/subresources/prefixes/subresources/advertisement_status/methods/edit/).
diff --git a/src/content/docs/magic-transit/partners/index.mdx b/src/content/docs/magic-transit/partners/index.mdx
index bfd05db0b774788..6ee348692df331a 100644
--- a/src/content/docs/magic-transit/partners/index.mdx
+++ b/src/content/docs/magic-transit/partners/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 15
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
index 7bc128098d8f68c..535769eb632525c 100644
--- a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
+++ b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
@@ -18,7 +18,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
-		productPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		productPath:
+			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
index 6b1bfa5d9f79f7f..dc972d88c678590 100644
--- a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
@@ -22,12 +22,13 @@ import { Render } from "~/components";
 		mssURL: "/magic-transit/get-started/#set-maximum-segment-size",
 		productURL: "/magic-transit/reference/anti-replay-protection/",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		magicWord: "Magic Transit"
+		magicWord: "Magic Transit",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/magic-transit/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 1fba89abfb6a2f8..f9fbf42cffa7459 100644
--- a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,12 @@ sidebar:
   order: 9
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down" }}
+	params={{
+		tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down",
+	}}
 />
diff --git a/src/content/docs/magic-transit/reference/index.mdx b/src/content/docs/magic-transit/reference/index.mdx
index 19ff0a30a962cbc..fe0a8581aa501bb 100644
--- a/src/content/docs/magic-transit/reference/index.mdx
+++ b/src/content/docs/magic-transit/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 16
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/reference/mtu-mss.mdx b/src/content/docs/magic-transit/reference/mtu-mss.mdx
index aea2b11b3a8ca3a..c35b312d04d675d 100644
--- a/src/content/docs/magic-transit/reference/mtu-mss.mdx
+++ b/src/content/docs/magic-transit/reference/mtu-mss.mdx
@@ -20,6 +20,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
-		productName: "Magic Transit"
-		}}
+		productName: "Magic Transit",
+	}}
 />
diff --git a/src/content/docs/magic-transit/reference/traffic-steering.mdx b/src/content/docs/magic-transit/reference/traffic-steering.mdx
index 6343ed66f6690f6..3864fa3d06c3f68 100644
--- a/src/content/docs/magic-transit/reference/traffic-steering.mdx
+++ b/src/content/docs/magic-transit/reference/traffic-steering.mdx
@@ -22,7 +22,8 @@ import { Render } from "~/components";
 		routingTableName: "Magic Transit Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
index cc8c425a16b925c..9f4b6435299ad5a 100644
--- a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
@@ -20,11 +20,12 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		addTunnels: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		changeHealthCheckRate:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
 		staticRoutes: "/magic-transit/how-to/configure-routes/",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
index ff5293328e0537b..bc19d9e2ed3a087 100644
--- a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 		productName: "Magic Transit",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
 		routingBgpLink: "/magic-transit/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		checkHealthDashLink:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/index.mdx b/src/content/docs/magic-transit/troubleshooting/index.mdx
index 6487eea738df77b..24dc284181dfdf0 100644
--- a/src/content/docs/magic-transit/troubleshooting/index.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/index.mdx
@@ -12,6 +12,6 @@ tags:
   - Debugging
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
index bacfef32c5f77a3..3ad6b0cbb6091ce 100644
--- a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
@@ -12,15 +12,17 @@ tags:
   - Logging
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		mtuMssLink: "/magic-transit/reference/mtu-mss/"
+		mtuMssLink: "/magic-transit/reference/mtu-mss/",
 	}}
 />
 
@@ -29,6 +31,7 @@ import { Render } from "~/components"
 Some customer routers cannot fully disable IPsec anti-replay protection, which is required for optimal Magic Transit operation (packet reordering at the Cloudflare edge can otherwise trigger false drops).
 
 **If your router does not support disabling anti-replay:**
+
 1. Check whether your router supports configuring a **replay window size**. Setting this to `0` is equivalent to disabling anti-replay protection.
 2. If neither disabling anti-replay nor setting the window size to `0` is supported, **the router cannot be used as a Magic Transit IPsec on-ramp**. Consider using a GRE tunnel or Cloudflare Network Interconnect (CNI) instead.
 
@@ -41,4 +44,3 @@ If your ISP is blocking these response packets, health checks will fail even whe
 **Symptom:** Health checks fail but application traffic flows normally through the tunnel.
 
 **Resolution:** Switch to bidirectional health checks, which send both the probe and the response through the tunnel. Bidirectional health checks require egress traffic to be turned on for your Magic Transit configuration. For more information, refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/).
-
diff --git a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
index d207cbb1af0bab8..43b9bb867569e75 100644
--- a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
@@ -11,14 +11,15 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "Magic Transit",
-    productName: "Magic Transit",
-    trafficSteeringLink: "/magic-transit/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/magic-transit/how-to/configure-routes/",
-    tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "Magic Transit",
+		productName: "Magic Transit",
+		trafficSteeringLink:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink: "/magic-transit/how-to/configure-routes/",
+		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
index 1f0887e6040a0f8..747fc6d131cd7b6 100644
--- a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
@@ -14,17 +14,20 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Magic Transit",
-    healthCheckDefault: "_Unidirectional_ (direct server return)",
-    tunnelsConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-    antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Magic Transit",
+		healthCheckDefault: "_Unidirectional_ (direct server return)",
+		tunnelsConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
+		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
+		configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/moq/feature-matrix.mdx b/src/content/docs/moq/feature-matrix.mdx
index 200715e6e3a4ba2..92148c292bc4988 100644
--- a/src/content/docs/moq/feature-matrix.mdx
+++ b/src/content/docs/moq/feature-matrix.mdx
@@ -3,81 +3,80 @@ pcx_content_type: get-started
 title: MoQ Feature Matrix
 sidebar:
   order: 18
-
 ---
 
 ## Draft-14 Messages
 
 ### Supported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_CANCEL | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message                            | Support | Relevant specification                                                                           |
+| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_CANCEL           | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_OK               | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_ERROR            | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_OK                         | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE                  | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_DONE             | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_DONE                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_OK                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ### Unsupported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| GOAWAY | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| MAX_REQUEST_ID | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| REQUESTS_BLOCKED | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_CANCEL | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message                   | Support | Relevant specification                                                                           |
+| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| GOAWAY                    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| MAX_REQUEST_ID            | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| REQUESTS_BLOCKED          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_ERROR             | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH                     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_OK                  | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_ERROR               | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_ERROR        | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE       | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_OK    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_ERROR | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE_NAMESPACE     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ## Draft-07 Messages
 
 ### Supported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| ANNOUNCE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_CANCEL | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS_REQUEST | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_DONE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| MAX_SUBSCRIBE_ID | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message                            | Support | Relevant specification                                                                           |
+| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| ANNOUNCE_OK                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_ERROR                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_CANCEL                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS_REQUEST               | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE                           | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNANNOUNCE                         | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_DONE                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| MAX_SUBSCRIBE_ID                   | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
 
 ### Unsupported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| GOAWAY | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_CANCEL | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message                   | Support | Relevant specification                                                                           |
+| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| GOAWAY                    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES       | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_OK    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_ERROR | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE_ANNOUNCES     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH                     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_OK                  | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_ERROR               | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
diff --git a/src/content/docs/moq/index.mdx b/src/content/docs/moq/index.mdx
index 838ca1c7516741e..d02f8400089cf48 100644
--- a/src/content/docs/moq/index.mdx
+++ b/src/content/docs/moq/index.mdx
@@ -22,7 +22,7 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Frequently Asked Questions
 
-* What about Safari?
+- What about Safari?
 
   Safari does not yet have fully functional WebTransport support. Apple never publicly commits to timelines for new features like this. However, Apple has indicated their [intent to support WebTransport](https://github.com/WebKit/standards-positions/issues/18#issuecomment-1495890122). An Apple employee is even a co-author of the [WebTransport over HTTP/3](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/) draft. Since Safari 18.4 (2025-03-31), an early (not yet fully functional) implementation of the WebTransport API has been available for testing behind a developer-mode / advanced settings feature flag (including on iOS).
 
@@ -30,12 +30,12 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Known Issues
 
-* Extra Subgroup header field
+- Extra Subgroup header field
+
+  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits.
 
-  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits. 
-  
   In section 7.3.1, `draft-ietf-moq-transport-07` [specifies](https://www.ietf.org/archive/id/draft-ietf-moq-transport-07.html#section-7.3.1):
-  
+
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Track Alias (i),
@@ -44,8 +44,9 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-  
+
   Whereas our implementation expects and produces:
+
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Subscribe ID (i),
@@ -55,5 +56,5 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-  
+
   This was erroroneously left over from a previous draft version and will be fixed in a future release. Thank you to [@yuki-uchida](https://github.com/yuki-uchida) for reporting.
diff --git a/src/content/docs/multi-cloud-networking/changelog.mdx b/src/content/docs/multi-cloud-networking/changelog.mdx
index 4374533a030deb1..4bbf7ded14ca757 100644
--- a/src/content/docs/multi-cloud-networking/changelog.mdx
+++ b/src/content/docs/multi-cloud-networking/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/multi-cloud-networking/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="multi-cloud-networking" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="multi-cloud-networking"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-11-21
 
diff --git a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
index d388a38c069f08b..d20a8425820479e 100644
--- a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
+++ b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
@@ -6,12 +6,15 @@ products:
 title: Cloud on-ramps
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="routing/mcn-cloudflare-wan-on-ramps"
+<Render
+	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
-	params={{ mwanAccount: "Have a Cloudflare WAN account. Contact your account team to learn more." }}
+	params={{
+		mwanAccount:
+			"Have a Cloudflare WAN account. Contact your account team to learn more.",
+	}}
 />
diff --git a/src/content/docs/multi-cloud-networking/get-started.mdx b/src/content/docs/multi-cloud-networking/get-started.mdx
index 04c91b1108e2aa5..ef3448467003242 100644
--- a/src/content/docs/multi-cloud-networking/get-started.mdx
+++ b/src/content/docs/multi-cloud-networking/get-started.mdx
@@ -25,7 +25,7 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 1. Go to the **Cloud integrations (beta)** page.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **AWS integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -38,29 +38,29 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 ```json
 {
-    "Version": "2012-10-17",
-    "Statement": [
-        {
-            "Effect": "Allow",
-            "Action": [
-                "ec2:AcceptTransitGatewayPeeringAttachment",
-                "ec2:CreateTransitGatewayPeeringAttachment",
-                "ec2:DeleteTransitGatewayPeeringAttachment",
-                "ec2:DescribeRegions",
-                "ec2:DescribeTransitGatewayPeeringAttachments",
-                "ec2:RejectTransitGatewayPeeringAttachment",
-                "ec2:GetManagedPrefixListEntries",
-                "ec2:CreateManagedPrefixList",
-                "ec2:ModifyManagedPrefixList",
-                "ec2:DeleteManagedPrefixList",
-                "ec2:CreateTransitGatewayPrefixListReference",
-                "ec2:DeleteTransitGatewayPrefixListReference",
-                "ec2:GetTransitGatewayPrefixListReferences",
-                "ec2:ModifyTransitGatewayPrefixListReference"
-            ],
-            "Resource": "*"
-        }
-    ]
+	"Version": "2012-10-17",
+	"Statement": [
+		{
+			"Effect": "Allow",
+			"Action": [
+				"ec2:AcceptTransitGatewayPeeringAttachment",
+				"ec2:CreateTransitGatewayPeeringAttachment",
+				"ec2:DeleteTransitGatewayPeeringAttachment",
+				"ec2:DescribeRegions",
+				"ec2:DescribeTransitGatewayPeeringAttachments",
+				"ec2:RejectTransitGatewayPeeringAttachment",
+				"ec2:GetManagedPrefixListEntries",
+				"ec2:CreateManagedPrefixList",
+				"ec2:ModifyManagedPrefixList",
+				"ec2:DeleteManagedPrefixList",
+				"ec2:CreateTransitGatewayPrefixListReference",
+				"ec2:DeleteTransitGatewayPrefixListReference",
+				"ec2:GetTransitGatewayPrefixListReferences",
+				"ec2:ModifyTransitGatewayPrefixListReference"
+			],
+			"Resource": "*"
+		}
+	]
 }
 ```
 
@@ -69,15 +69,15 @@ Once Cloudflare has the credentials required to access your cloud environments,
 1. Create an [AWS role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html) with the following settings:
    - **Trusted entity type**: Select **Custom trust policy**, and paste the custom trust policy returned by the Cloudflare dashboard.
    - **Permissions**: Add the IAM policy you created in the previous step, along with these AWS-managed policies:
-      - `NetworkAdministrator`
-      - `AmazonEC2ReadOnlyAccess`
-      - `AmazonVPCReadOnlyAccess`
-      - `IAMReadOnlyAccess`
+     - `NetworkAdministrator`
+     - `AmazonEC2ReadOnlyAccess`
+     - `AmazonVPCReadOnlyAccess`
+     - `IAMReadOnlyAccess`
    - **ARN**: Copy the ARN for your newly created user.
 
    :::note
-	 The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-	 :::
+   The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+   :::
 
 2. Select **I authorize Cloudflare to access my AWS account.**
 3. Select **Authorize**.
@@ -92,7 +92,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Azure integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -115,8 +115,8 @@ Multi-Cloud Networking does not support personal Microsoft accounts. Sign in usi
 6. In **Verify account ownership**, [add the tags displayed in the Cloudflare dashboard](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources-portal).
 
    :::note
-	 The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-	 :::
+   The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+   :::
 
 7. Select **I authorize Cloudflare to access my Azure account.** If your account does not have administrator privileges, you may need to pass this link to an account that has administrator privileges.
 8. Select **Authorize**.
@@ -131,7 +131,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Google integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -142,8 +142,8 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. Create a new [GCP service account](https://cloud.google.com/iam/docs/service-accounts-create) in your **Google account** > **GCP Console** > **IAM & Admin** > **Service Accounts**.
 2. Grant the new service account these roles:
-	- `Compute Network Admin`
-	- `Compute Viewer`
+   - `Compute Network Admin`
+   - `Compute Viewer`
 3. Under **IAM & Admin** > **Service Accounts**, select the service account you just created, and navigate to the **Permissions** tab.
 4. Grant the **Service Account Token Creator** role to our bot account to allow it to impersonate this service account. Learn how to grant a specific role [in Google's documentation](https://cloud.google.com/iam/docs/manage-access-service-accounts#grant-single-role):
    - `mcn-integrations-bot-prod@mcn-gcp-01.iam.gserviceaccount.com`
@@ -163,4 +163,4 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 - [Set up Cloudflare WAN](/multi-cloud-networking/cloud-on-ramps/) as an on-ramp to your cloud.
 - [Manage resources](/multi-cloud-networking/manage-resources/) found by Multi-Cloud Networking.
-- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
\ No newline at end of file
+- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
diff --git a/src/content/docs/multi-cloud-networking/manage-resources.mdx b/src/content/docs/multi-cloud-networking/manage-resources.mdx
index 4307d7b9da2de5c..b9eb3e0bc385769 100644
--- a/src/content/docs/multi-cloud-networking/manage-resources.mdx
+++ b/src/content/docs/multi-cloud-networking/manage-resources.mdx
@@ -6,7 +6,6 @@ products:
 title: Manage resources
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,7 @@ To browse the resources in your catalog:
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select a resource to inspect its details.
@@ -30,7 +29,7 @@ You can change which cloud account the integration is linked to or delete the in
 
 1. Go to **Cloud integrations**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select your integration > **Edit**.
 3. In **Linked account details**, select **Link integration to a different cloud account**.
@@ -43,7 +42,7 @@ You can download a JSON file containing metadata and configuration for all your
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select **Download catalog**.
diff --git a/src/content/docs/multi-cloud-networking/reference.mdx b/src/content/docs/multi-cloud-networking/reference.mdx
index 8c37c24b0eabb74..16d0b78776c4c47 100644
--- a/src/content/docs/multi-cloud-networking/reference.mdx
+++ b/src/content/docs/multi-cloud-networking/reference.mdx
@@ -6,7 +6,6 @@ products:
 title: Reference
 sidebar:
   order: 5
-
 ---
 
 Refer to this page for details about how Cloudflare orchestrates VPN connectivity to your cloud networks.
diff --git a/src/content/docs/network-error-logging/get-started.mdx b/src/content/docs/network-error-logging/get-started.mdx
index e211ba22e5e901a..2b07fd6d29a8e84 100644
--- a/src/content/docs/network-error-logging/get-started.mdx
+++ b/src/content/docs/network-error-logging/get-started.mdx
@@ -6,7 +6,6 @@ products:
   - network-error-logging
 tags:
   - Logging
-
 ---
 
 import { DashButton } from "~/components";
@@ -17,7 +16,7 @@ To enable Network Error Logging for Free and Pro zones:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Network** and locate **Network Error Logging Monitoring**.
 3. Select the toggle to enable Network Error Logging.
diff --git a/src/content/docs/network-error-logging/how-to.mdx b/src/content/docs/network-error-logging/how-to.mdx
index 6aac695c1d00025..74f33f4e7eeadff 100644
--- a/src/content/docs/network-error-logging/how-to.mdx
+++ b/src/content/docs/network-error-logging/how-to.mdx
@@ -11,21 +11,20 @@ head:
 description: NEL reports show you why a request failed, the country a request
   failed from, and last mile network a request failed from, and the likely
   intended Cloudflare data center.
-
 ---
 
 import { DashButton } from "~/components";
 
 Use NEL reports to view information such as:
 
-* Why a request failed
-* The country a request failed from
-* The last mile network a request failed from
-* The Cloudflare data center the request was most likely meant for
+- Why a request failed
+- The country a request failed from
+- The last mile network a request failed from
+- The Cloudflare data center the request was most likely meant for
 
 1. Log in to your Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Analytics & Logs** > **Edge Reachability**.
 
diff --git a/src/content/docs/network-error-logging/index.mdx b/src/content/docs/network-error-logging/index.mdx
index b712cac7782fb54..9f1acd04e344ba5 100644
--- a/src/content/docs/network-error-logging/index.mdx
+++ b/src/content/docs/network-error-logging/index.mdx
@@ -34,21 +34,21 @@ A sample Network Error Report payload appears as follows:
 
 ```json
 {
-  "age": 20,
-  "type": "network-error",
-  "url": "https://example.com/previous-page",
-  "body": {
-    "elapsed_time": 18,
-    "method": "POST",
-    "phase": "dns",
-    "protocol": "http/1.1",
-    "referrer": "https://example.com/previous-page",
-    "sampling_fraction": 1,
-    "server_ip": "",
-    "status_code": 0,
-    "type": "dns.name_not_resolved",
-    "url": "https://example-host.com/"
-  }
+	"age": 20,
+	"type": "network-error",
+	"url": "https://example.com/previous-page",
+	"body": {
+		"elapsed_time": 18,
+		"method": "POST",
+		"phase": "dns",
+		"protocol": "http/1.1",
+		"referrer": "https://example.com/previous-page",
+		"sampling_fraction": 1,
+		"server_ip": "",
+		"status_code": 0,
+		"type": "dns.name_not_resolved",
+		"url": "https://example-host.com/"
+	}
 }
 ```
 
@@ -56,9 +56,9 @@ A sample Network Error Report payload appears as follows:
 
 Cloudflare uses geolocation lookups to extract the following information from every client IP in a NEL report:
 
-* Client ASN
-* Client country
-* Client metro area
+- Client ASN
+- Client country
+- Client metro area
 
 Cloudflare uses internal lookups to associate the above data with a customer domain and customer account.
 
@@ -67,9 +67,10 @@ Cloudflare does not store any PII or user-specific data, and any IP data is only
 The client IP address is only stored in volatile memory for the lifetime of the request to Cloudflare’s NEL endpoint (order of milliseconds) and is dropped immediately after the request completes. Cloudflare does not log the client IP address anywhere in the Network Error Logging pipeline.
 
 NEL reports contain information about the end user's network conditions, which could be considered sensitive. Cloudflare takes privacy seriously and has implemented the following safeguards:
-* Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
-* Reports do not contain personally identifiable information (PII).
-* Customers can opt out of having their end users consume the NEL headers using one of the following methods:
+
+- Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
+- Reports do not contain personally identifiable information (PII).
+- Customers can opt out of having their end users consume the NEL headers using one of the following methods:
   1. **Self-service (Zone setting)** — Use the dashboard toggle or API (`PATCH /zones/{zone_id}/settings/nel`) to disable NEL for your zone. This can be re-enabled by any zone administrator at any time.
   2. **Permanent opt-out via Support** — Contact Cloudflare support to have the `nel___enable` feature flag disabled at the product level. This prevents NEL from being enabled on your zone entirely and cannot be reversed by zone administrators.
-For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
+     For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
diff --git a/src/content/docs/network-flow/api.mdx b/src/content/docs/network-flow/api.mdx
index abedf0335eb08a4..86093e48a9529bf 100644
--- a/src/content/docs/network-flow/api.mdx
+++ b/src/content/docs/network-flow/api.mdx
@@ -6,9 +6,8 @@ products:
   - network-flow
 sidebar:
   order: 9
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mnm/api" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/api" product="networking-services" />
diff --git a/src/content/docs/network-flow/changelog.mdx b/src/content/docs/network-flow/changelog.mdx
index b94beaa04726a51..c0a384cb7ba3378 100644
--- a/src/content/docs/network-flow/changelog.mdx
+++ b/src/content/docs/network-flow/changelog.mdx
@@ -13,4 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-flow/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="network-flow" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="network-flow"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
diff --git a/src/content/docs/network-flow/cloud-flow-logs.mdx b/src/content/docs/network-flow/cloud-flow-logs.mdx
index b3b71aa0230d535..1f7b9357b839a4c 100644
--- a/src/content/docs/network-flow/cloud-flow-logs.mdx
+++ b/src/content/docs/network-flow/cloud-flow-logs.mdx
@@ -16,4 +16,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/cloud-flow-logs" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/cloud-flow-logs" product="networking-services" />
diff --git a/src/content/docs/network-flow/faq.mdx b/src/content/docs/network-flow/faq.mdx
index 83e76018f873f71..7f18175619785c3 100644
--- a/src/content/docs/network-flow/faq.mdx
+++ b/src/content/docs/network-flow/faq.mdx
@@ -11,6 +11,6 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mnm/faqs" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/faqs" product="networking-services" />
diff --git a/src/content/docs/network-flow/get-started.mdx b/src/content/docs/network-flow/get-started.mdx
index 8129f8e3bb7ce5a..4c52c7365d5e149 100644
--- a/src/content/docs/network-flow/get-started.mdx
+++ b/src/content/docs/network-flow/get-started.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/get-started" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/get-started" product="networking-services" />
diff --git a/src/content/docs/network-flow/glossary.mdx b/src/content/docs/network-flow/glossary.mdx
index 560fd3884273263..3000aa1c392cf88 100644
--- a/src/content/docs/network-flow/glossary.mdx
+++ b/src/content/docs/network-flow/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - network-flow
 sidebar:
   order: 10
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Network Flow (formerly Magic Network Monitoring) documentation.
 
diff --git a/src/content/docs/network-flow/magic-transit-integration.mdx b/src/content/docs/network-flow/magic-transit-integration.mdx
index 8defa83ac2a41fc..0b4ac3859f62b97 100644
--- a/src/content/docs/network-flow/magic-transit-integration.mdx
+++ b/src/content/docs/network-flow/magic-transit-integration.mdx
@@ -8,16 +8,15 @@ tags:
   - Integration
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
 	}}
 />
diff --git a/src/content/docs/network-flow/network-flow-free.mdx b/src/content/docs/network-flow/network-flow-free.mdx
index ca7198f7f03d8fe..645bf56f6cb3a17 100644
--- a/src/content/docs/network-flow/network-flow-free.mdx
+++ b/src/content/docs/network-flow/network-flow-free.mdx
@@ -11,6 +11,6 @@ head:
     content: Network Flow free version
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="mnm/network-flow-free" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/index.mdx b/src/content/docs/network-flow/routers/index.mdx
index dc7bb414eb48ca9..476c0017b240362 100644
--- a/src/content/docs/network-flow/routers/index.mdx
+++ b/src/content/docs/network-flow/routers/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
index 3d1f2222d0b7878..58e65c53add4e60 100644
--- a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
+++ b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
@@ -11,9 +11,8 @@ sidebar:
 head: []
 description: A step-by-step configuration guide for exporting NetFlow or IPFIX
   data to Cloudflare's network.
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
index 82158fe7ad97cf0..b8cd99b68ae977e 100644
--- a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
+++ b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
@@ -9,7 +9,6 @@ sidebar:
   order: 2
 head: []
 description: The best sampling rate recommendations for your network's traffic volume.
-
 ---
 
 import { Render } from "~/components";
@@ -17,4 +16,4 @@ import { Render } from "~/components";
 <Render
 	file="mnm/routers/recommended-sampling-rate"
 	product="networking-services"
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/network-flow/routers/sflow-config.mdx b/src/content/docs/network-flow/routers/sflow-config.mdx
index ee37c4c868a8ac4..5b7ba843d316df0 100644
--- a/src/content/docs/network-flow/routers/sflow-config.mdx
+++ b/src/content/docs/network-flow/routers/sflow-config.mdx
@@ -14,7 +14,4 @@ description: A step-by-step configuration guide for exporting sFlow data to
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/routers/sflow-config"
-	product="networking-services"
-	/>
\ No newline at end of file
+<Render file="mnm/routers/sflow-config" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/supported-routers.mdx b/src/content/docs/network-flow/routers/supported-routers.mdx
index 45a57d81dc9d9a9..410865594728185 100644
--- a/src/content/docs/network-flow/routers/supported-routers.mdx
+++ b/src/content/docs/network-flow/routers/supported-routers.mdx
@@ -13,7 +13,4 @@ description: A list of open source, NetFlow, and sFlow routers.
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/routers/supported-routers"
-	product="networking-services"
-	/>
\ No newline at end of file
+<Render file="mnm/routers/supported-routers" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/index.mdx b/src/content/docs/network-flow/rules/index.mdx
index ef9d83a02553c40..ff541e592e5802a 100644
--- a/src/content/docs/network-flow/rules/index.mdx
+++ b/src/content/docs/network-flow/rules/index.mdx
@@ -14,4 +14,3 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="mnm/rules/overview" product="networking-services" />
-
diff --git a/src/content/docs/network-flow/rules/rule-notifications.mdx b/src/content/docs/network-flow/rules/rule-notifications.mdx
index 0f85c34f0e1fd3d..cfc447c89cb41dd 100644
--- a/src/content/docs/network-flow/rules/rule-notifications.mdx
+++ b/src/content/docs/network-flow/rules/rule-notifications.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/rule-notifications" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/rule-notifications" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
index 9dfff3f061f5c5d..34d38296b6570d4 100644
--- a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
+++ b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/static-threshold.mdx b/src/content/docs/network-flow/rules/static-threshold.mdx
index 172ca611aa68db2..fa5fca21e7cef6f 100644
--- a/src/content/docs/network-flow/rules/static-threshold.mdx
+++ b/src/content/docs/network-flow/rules/static-threshold.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/static-threshold" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/static-threshold" product="networking-services" />
diff --git a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
index 0b0bb68e1ebbc8d..d43167ed7936fd7 100644
--- a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
+++ b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
@@ -15,4 +15,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
diff --git a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
index f7562708d10bd0d..8b86d643dd5ade2 100644
--- a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
+++ b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
@@ -19,4 +19,7 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/encrypt-network-flow-data" product="networking-services" />
\ No newline at end of file
+<Render
+	file="mnm/tutorials/encrypt-network-flow-data"
+	product="networking-services"
+/>
diff --git a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
index 00c00c094490f32..26f062040cac4f3 100644
--- a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
+++ b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
@@ -20,4 +20,4 @@ import { Render } from "~/components";
 
 <Render file="mnm/tutorials/graphql-analytics" product="networking-services" />
 
-<Render file="case-sensitivity-note" product="analytics" />
\ No newline at end of file
+<Render file="case-sensitivity-note" product="analytics" />
diff --git a/src/content/docs/network-flow/tutorials/index.mdx b/src/content/docs/network-flow/tutorials/index.mdx
index 8fae75e32ca4f24..a13ee6bc966bfd7 100644
--- a/src/content/docs/network-flow/tutorials/index.mdx
+++ b/src/content/docs/network-flow/tutorials/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/network-interconnect/changelog.mdx b/src/content/docs/network-interconnect/changelog.mdx
index 5b15e2c668e23f3..64c3877fd409947 100644
--- a/src/content/docs/network-interconnect/changelog.mdx
+++ b/src/content/docs/network-interconnect/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-interconnect/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="network-interconnect" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="network-interconnect"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx
index 16c0b376aa76fb9..daba42777661fd5 100644
--- a/src/content/docs/network-interconnect/get-started.mdx
+++ b/src/content/docs/network-interconnect/get-started.mdx
@@ -11,7 +11,7 @@ tags:
   - GCP
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 :::note[BGP architecture and resiliency]
 CNI supports BGP peering with the Cloudflare Virtual Network routing table. BGP over CNI is in closed beta and is not currently available to new customers. If you are interested in BGP peering over CNI, contact your account team.
@@ -26,7 +26,7 @@ For detailed information about BGP architecture, Edge Resiliency Mode, and route
 Your Cloudflare account team determines CNI eligibility and port availability. Notably:
 
 - CNI ports are currently offered at no charge to Enterprise customers.
-	- Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
+  - Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
 - CNI is available at select Cloudflare data centers:
   - The type of Dataplane offered in that location will determine specifications of the supported connection, such as the MTU.
   - The diversity offered in the location will vary.
@@ -43,36 +43,37 @@ To peer with Cloudflare, advertise prefixes with a prefix length of `/24` or sho
 ## Technical specifications
 
 - **Supported port types**:
-	- **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
-	- **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
+  - **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
+  - **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
 - **Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection.
 - **IP addressing:** All CNI connections and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare.
 - **VLAN support:**
-	- **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
-	- **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
+  - **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
+  - **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
 - **MTU considerations:**
-	- **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
-	- **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
+  - **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
+  - **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
 - **Bidirectional Forwarding Detection (BFD):**
-	- **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
-	- **Dataplane v2**: Not yet supported.
+  - **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
+  - **Dataplane v2**: Not yet supported.
 - **Link Aggregation Control Protocol (LACP)**:
-	- **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
-	- **Dataplane v2**: Not yet supported. Use ECMP instead.
+  - **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
+  - **Dataplane v2**: Not yet supported. Use ECMP instead.
 
 ## Performance characteristics
 
 The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration.
 
-| Direction (use case) | 10G Circuit | 100G Circuit |
-|----------------------|-------------|--------------|
-| From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps |
-| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
-| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection  |
+| Direction (use case)                            | 10G Circuit                                                                                     | 100G Circuit                                                                                    |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| From Cloudflare to Customer (all use cases)     | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
+| From Customer to Cloudflare (peering use case)  | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
+| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection |
 
 ## Service expectations
 
 Consider the following service levels when planning your deployment:
+
 - **No Formal SLA**:
   - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms).
   - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel.
@@ -98,8 +99,8 @@ The process of provisioning a CNI typically takes two to four weeks, depending o
 1. **Submit request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process.
 2. **Review configuration**: For the v1 Dataplane, the Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document. For the v2 Dataplane, this step is not necessary.
 3. **Order connection**:
-	- For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
-	- For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
+   - For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
+   - For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
 4. **Configure network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document.
 5. **Test and verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and, if applicable, verify that the BGP session can be established.
 6. Enable tunnel health checks for [Magic Transit](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) and/or [Cloudflare WAN](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels).
@@ -142,7 +143,7 @@ To connect to AWS Direct Connect:
 
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select **Create an interconnect**.
 3. Under **Cloud Interconnect**, select **Create new**.
@@ -162,9 +163,5 @@ You can now select **View interconnects** for a list of all interconnects on you
 
 After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect:
 
-- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP:
-		- Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths.
-		- Note that routes advertised by BGP from GCP Cloud Router will be ignored.
-- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router:
-		- Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes).
-		- Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
+- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP: - Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths. - Note that routes advertised by BGP from GCP Cloud Router will be ignored.
+- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router: - Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes). - Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
diff --git a/src/content/docs/network-interconnect/index.mdx b/src/content/docs/network-interconnect/index.mdx
index 80bde6dd95d9bb1..9b63e926dc454eb 100644
--- a/src/content/docs/network-interconnect/index.mdx
+++ b/src/content/docs/network-interconnect/index.mdx
@@ -11,10 +11,10 @@ head:
     content: Overview
 ---
 
-import { Description, Plan, RelatedProduct, Render } from "~/components"
+import { Description, Plan, RelatedProduct, Render } from "~/components";
 
 <Description>
-Connect your network infrastructure directly to Cloudflare
+	Connect your network infrastructure directly to Cloudflare
 </Description>
 
 <Plan type="enterprise" />
@@ -24,6 +24,7 @@ Cloudflare Network Interconnect (CNI) allows you to connect your network infrast
 ## Benefits
 
 Enterprises use CNI to achieve:
+
 - **Enhanced Performance**: Gain lower latency and more consistent network throughput.
 - **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet.
 
@@ -31,15 +32,16 @@ Enterprises use CNI to achieve:
 
 Choose the connection type for your infrastructure and operational needs.
 
-| | Direct Interconnect | Partner Interconnect | Cloud Interconnect |
-| --- | --- | --- | --- |
-| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare. |
-| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
-| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. |
+|                    | Direct Interconnect                                                                                                     | Partner Interconnect                                                                                       | Cloud Interconnect                                                                                                                              |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Port type**      | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners.            | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare.             |
+| **Operations**     | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment.                    | Your partner manages the connection logistics, often through a software-defined networking portal.         | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
+| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability.                     | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services.                                    |
 
 ## Dataplane
 
 Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection:
+
 - **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports Generic Routing Encapsulation (GRE) tunnels for connecting with the Cloudflare Virtual Network, with optional GRE-less delivery for Magic Transit Direct Server Return.
 - **Dataplane v2**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte Maximum Transmission Unit (MTU) bidirectionally.
 
@@ -55,15 +57,25 @@ To protect against a single point of failure, it is critical to design your CNI
 
 Refer to [Service Expectations](/network-interconnect/get-started/#service-expectations) for more information.
 
-***
+---
 
 ## Related products
 
-<RelatedProduct header="Magic Transit" href="/magic-transit/" product="magic-transit">
-Magic Transit is a network security and performance solution that offers Distributed Denial of Service (DDoS) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
+<RelatedProduct
+	header="Magic Transit"
+	href="/magic-transit/"
+	product="magic-transit"
+>
+	Magic Transit is a network security and performance solution that offers
+	Distributed Denial of Service (DDoS) protection, traffic acceleration, and
+	more for on-premise, cloud-hosted, and hybrid networks.
 </RelatedProduct>
 
-<RelatedProduct header="Cloudflare WAN" href="/cloudflare-wan/" product="cloudflare-wan">
-Improve security and performance for your entire corporate network, reducing cost and operation complexity.
+<RelatedProduct
+	header="Cloudflare WAN"
+	href="/cloudflare-wan/"
+	product="cloudflare-wan"
+>
+	Improve security and performance for your entire corporate network, reducing
+	cost and operation complexity.
 </RelatedProduct>
-
diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
index 861b447fcad7132..1b73b9485ee8d93 100644
--- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
+++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 5
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 ## Monitoring
 
@@ -22,17 +22,18 @@ The Status column displays three statuses:
 - **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
 - **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The **Pending** status will disappear after the customer completes the cross-connect and status moves to **Active**.
 
-
 ## Alerts (v1 dataplane only)
 
 You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
 
 **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only.
+
 - You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections.
 - You will be notified if the details of a scheduled maintenance change or if it is canceled.
 - For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments.
 
 **Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network.
+
 - You will be warned about potentially disruptive maintenance at the PoP level.
 - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these.
 - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits.
@@ -43,7 +44,7 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-	<DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
 
 2. Select **Add**.
 3. From the product drop-down menu, select _Cloudflare Network Interconnect_.
@@ -55,9 +56,10 @@ You can configure notifications for upcoming CNI maintenance events using the No
 ### Enable Cloudflare Status Maintenance Notification
 
 First, identify the PoP code for your CNI circuit:
+
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select the CNI you want to enable notifications for.
 3. In the menu that appears, note the Data Center code (for example, `gru-b`).
diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx
index a94aa4bae85717a..2cf09f24173e915 100644
--- a/src/content/docs/network-interconnect/operational-guidance.mdx
+++ b/src/content/docs/network-interconnect/operational-guidance.mdx
@@ -52,4 +52,4 @@ If no system-wide problems are reported, gather the following information before
 - **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
 - **Physical Layer**: Light levels of the CNI link (if applicable).
 - **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
-- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
\ No newline at end of file
+- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
diff --git a/src/content/docs/network/index.mdx b/src/content/docs/network/index.mdx
index e6d3e05e3d5a401..e9f9e837d33f580 100644
--- a/src/content/docs/network/index.mdx
+++ b/src/content/docs/network/index.mdx
@@ -11,38 +11,48 @@ products:
   - network
 ---
 
-import { Description, Feature, Plan, RelatedProduct } from "~/components"
+import { Description, Feature, Plan, RelatedProduct } from "~/components";
 
-<Description>
-Manage network settings for your website.
-</Description>
+<Description>Manage network settings for your website.</Description>
 
 <Plan type="all" />
 
-***
+---
 
 ## Features
 
 <Feature header="IP Geolocation" href="/network/ip-geolocation/">
-Include the country code of the visitor location with all requests to your website.
+	Include the country code of the visitor location with all requests to your
+	website.
 </Feature>
 
 <Feature header="IPv6 Compatibility" href="/network/ipv6-compatibility/">
-Enable IPv6 support and gateway.
+	Enable IPv6 support and gateway.
 </Feature>
 
 <Feature header="WebSockets" href="/network/websockets/">
-Allow WebSockets connections to your origin server.
+	Allow WebSockets connections to your origin server.
 </Feature>
 
-***
+---
 
 ## Related products
 
-<RelatedProduct header="China Network" href="/china-network/" product="china-network">
-The Cloudflare China Network is a package of selected Cloudflare’s performance and security products running on data centers located in mainland China and operated by Cloudflare’s partner JD Cloud.
+<RelatedProduct
+	header="China Network"
+	href="/china-network/"
+	product="china-network"
+>
+	The Cloudflare China Network is a package of selected Cloudflare’s performance
+	and security products running on data centers located in mainland China and
+	operated by Cloudflare’s partner JD Cloud.
 </RelatedProduct>
 
-<RelatedProduct header="Managed Transforms" href="/rules/transform/managed-transforms/" product="rules">
-Managed Transforms allow you to perform common adjustments to HTTP request and response headers with the click of a button.
+<RelatedProduct
+	header="Managed Transforms"
+	href="/rules/transform/managed-transforms/"
+	product="rules"
+>
+	Managed Transforms allow you to perform common adjustments to HTTP request and
+	response headers with the click of a button.
 </RelatedProduct>
diff --git a/src/content/docs/network/websockets.mdx b/src/content/docs/network/websockets.mdx
index 77ff14da6b28963..dbb08884e375a08 100644
--- a/src/content/docs/network/websockets.mdx
+++ b/src/content/docs/network/websockets.mdx
@@ -89,4 +89,3 @@ Cloudflare will close a WebSocket connection when no data is transmitted in eith
 ### Session affinity for load-balanced WebSocket origins
 
 If your WebSocket origin is behind a Cloudflare Load Balancer, turn on **Session affinity** to ensure all requests from the same client are routed to the same origin server. Without session affinity, a WebSocket reconnect may land on a different origin that does not have the session state.
-
diff --git a/src/content/docs/notifications/get-started/configure-pagerduty.mdx b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
index fef6662b17543be..a4e84b32aedd7cb 100644
--- a/src/content/docs/notifications/get-started/configure-pagerduty.mdx
+++ b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
@@ -12,7 +12,7 @@ import { DashButton } from "~/components";
 
 :::note
 
-This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/). 
+This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/).
 :::
 
 Cloudflare’s Notification service supports routing notifications to PagerDuty. By sending notifications to PagerDuty you can leverage the same service definitions and escalation paths that you would for other third-party services that you connect to PagerDuty.
@@ -23,14 +23,15 @@ To use PagerDuty as a connected service, you must [sign up for a PagerDuty accou
 
 :::note
 
-According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner. 
+According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner.
 :::
 
 ## Connect PagerDuty to a Cloudflare account
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **Connect**.
 4. Log in to your [PagerDuty account](https://www.pagerduty.com/) to connect it to your Cloudflare account.
@@ -48,8 +49,9 @@ Disconnecting PagerDuty will disable any notifications being sent to PagerDuty w
 If other delivery destinations were selected, then those notifications will still be routed as configured.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **View** on the PagerDuty service you want to disconnect.
 4. Select **Disconnect** > **Confirm**.
diff --git a/src/content/docs/notifications/get-started/index.mdx b/src/content/docs/notifications/get-started/index.mdx
index 4e0d0a3fba2ffc8..04bb4821e3116e6 100644
--- a/src/content/docs/notifications/get-started/index.mdx
+++ b/src/content/docs/notifications/get-started/index.mdx
@@ -36,8 +36,9 @@ This guide will help you create, edit, test, or delete notifications using the C
 You can create a notification via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select **Add**.
 3. On the notification you want to create, choose **Select**.
 4. Name the notification.
@@ -45,7 +46,7 @@ You can create a notification via the Cloudflare dashboard.
 
 :::note
 
-Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks. 
+Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks.
 :::
 
 6. (Optional) Specify any additional options for the notification, if required. For example, some notifications require that you select one or more domains or services.
@@ -58,8 +59,9 @@ The browser will navigate back to the list of notifications, where the new notif
 You can edit existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to modify, select **Edit**.
 3. Make your changes as needed and select **Save**.
 
@@ -70,8 +72,9 @@ The browser will navigate back to the list of notifications.
 You can delete or disable existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to disable, select the **Enabled** toggle. To delete it, select **Delete**.
 
 ### Mute a notification
@@ -79,8 +82,9 @@ You can delete or disable existing Notifications via the Cloudflare dashboard.
 You can temporarily mute a notification to stop receiving alerts for a set period of time. Muted notifications create a silence that automatically expires after the specified duration.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to mute, select **Mute**.
 3. Select a duration preset (**1h**, **12h**, or **24h**), or set a custom time range using the **Start Time** and **End Time** fields.
 4. Select **Save**.
@@ -95,8 +99,9 @@ While a notification is muted, alerts that would have triggered it are suppresse
 You can view, edit, or delete existing silences from the **Silences** tab.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select the **Silences** tab.
 3. To create a new silence, select **Add**. To modify an existing silence, select **Edit**. To remove a silence before it expires, select **Delete**.
 
diff --git a/src/content/docs/notifications/index.mdx b/src/content/docs/notifications/index.mdx
index a1d547bdecee617..829b5519eba15c2 100644
--- a/src/content/docs/notifications/index.mdx
+++ b/src/content/docs/notifications/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: overview
 title: Notifications
 sidebar:
@@ -9,7 +8,7 @@ products:
 description: Configure alerts for your Cloudflare account.
 ---
 
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
 <Plan type="all" />
 
@@ -29,4 +28,4 @@ The availability of delivery methods like PagerDuty and webhooks in Free or Prof
 
 - PagerDuty is available in zones on a Free/Professional plan if your Cloudflare account has at least one zone in a Business plan (or higher).
 - Webhooks are available in zones on a Free plan if your Cloudflare account has at least one zone in a Professional plan (or higher).
-:::
+  :::
diff --git a/src/content/docs/notifications/notification-available.mdx b/src/content/docs/notifications/notification-available.mdx
index 6712c3aee831957..b41697b971f7c3d 100644
--- a/src/content/docs/notifications/notification-available.mdx
+++ b/src/content/docs/notifications/notification-available.mdx
@@ -8,7 +8,7 @@ products:
 description: Browse available notification types by product.
 ---
 
-import { AvailableNotifications } from "~/components"
+import { AvailableNotifications } from "~/components";
 
 Available Notifications depend on your Cloudflare plan. Cloudflare offers a variety of Notifications for our products and services, such as [Billing](/billing/), [Denial of Service protection](/ddos-protection/), [Magic Transit](/magic-transit/), and [SSL/TLS](/ssl/).
 
diff --git a/src/content/docs/notifications/notification-history.mdx b/src/content/docs/notifications/notification-history.mdx
index 57b80f9b1bd7402..4bbc04b274ecd9b 100644
--- a/src/content/docs/notifications/notification-history.mdx
+++ b/src/content/docs/notifications/notification-history.mdx
@@ -32,5 +32,5 @@ Notification History is available on all plans. The amount of history clients ha
 
 :::note
 
-Customers will not be able to access Notification History from before 2021-10-11. 
+Customers will not be able to access Notification History from before 2021-10-11.
 :::
diff --git a/src/content/docs/notifications/reference/index.mdx b/src/content/docs/notifications/reference/index.mdx
index 38d8d2becb9beec..6d7a07ae02df9e1 100644
--- a/src/content/docs/notifications/reference/index.mdx
+++ b/src/content/docs/notifications/reference/index.mdx
@@ -10,7 +10,7 @@ products:
 description: Reference information for Cloudflare Notifications.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Notifications:
 
diff --git a/src/content/docs/notifications/reference/traffic-alerts.mdx b/src/content/docs/notifications/reference/traffic-alerts.mdx
index 9741d0e2d2dcc30..42527aee765f7ca 100644
--- a/src/content/docs/notifications/reference/traffic-alerts.mdx
+++ b/src/content/docs/notifications/reference/traffic-alerts.mdx
@@ -28,7 +28,7 @@ This approach does not work as well for low traffic zones. If there are not many
 
 ### Service-level objective recommendations
 
-SLOs determine the sensitivity of an alert.  For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
+SLOs determine the sensitivity of an alert. For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
 
 Your traffic levels impact the accuracy of high sensitivity alerts. High sensitivity alerts are not recommended for zones with low traffic since the Error Rate alert will likely alert on every 5xx error. However, If you have a zone that has very high traffic (hundreds of millions of requests per day), High Sensitivity SLOs are recommended.
 
diff --git a/src/content/docs/pages/configuration/api.mdx b/src/content/docs/pages/configuration/api.mdx
index 5f49f4fd6a70543..d813c97fe6c9adf 100644
--- a/src/content/docs/pages/configuration/api.mdx
+++ b/src/content/docs/pages/configuration/api.mdx
@@ -19,6 +19,7 @@ To create an API token:
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
+
 2. Select **Create Token**.
 3. You can go to **Edit Cloudflare Workers** template > **Use template** or go to **Create Custom Token** > **Get started**. If you create a custom token, you will need to make sure to add the **Cloudflare Pages** permission with **Edit** access.
 
diff --git a/src/content/docs/pages/configuration/build-caching.mdx b/src/content/docs/pages/configuration/build-caching.mdx
index 3cd918887d0b276..436cc3e60e5c6d3 100644
--- a/src/content/docs/pages/configuration/build-caching.mdx
+++ b/src/content/docs/pages/configuration/build-caching.mdx
@@ -37,15 +37,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                                          |
-| ---------- | ----------------------------------------------------------- |
-| Astro      | `node_modules/.astro`                                       |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
-| Eleventy   | `.cache`                                                    |
-| Gatsby     | `.cache`, `public`                                          |
-| Next.js    | `.next/cache`                                               |
-| Nuxt       | `node_modules/.cache/nuxt`                                  |
-| SvelteKit  | `node_modules/.cache/imagetools`                            |
+| Framework  | Directories cached                            |
+| ---------- | --------------------------------------------- |
+| Astro      | `node_modules/.astro`                         |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
+| Eleventy   | `.cache`                                      |
+| Gatsby     | `.cache`, `public`                            |
+| Next.js    | `.next/cache`                                 |
+| Nuxt       | `node_modules/.cache/nuxt`                    |
+| SvelteKit  | `node_modules/.cache/imagetools`              |
 
 ### Limits
 
diff --git a/src/content/docs/pages/configuration/build-image.mdx b/src/content/docs/pages/configuration/build-image.mdx
index d2c7006afebcc61..e4596187251d055 100644
--- a/src/content/docs/pages/configuration/build-image.mdx
+++ b/src/content/docs/pages/configuration/build-image.mdx
@@ -88,6 +88,7 @@ To migrate to this new version, configure your Pages project settings in the das
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Deployments** > **All deployments** > and select the latest version.
 
@@ -109,7 +110,6 @@ Cloudflare Pages builds are run in a [gVisor](https://gvisor.dev/docs/) containe
 
 <PagesBuildEnvironment />
 
-
 ## Build Image Policy
 
 ### Build Image Version Deprecation
@@ -131,6 +131,7 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
+
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -140,6 +141,7 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
+
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
 - **Plan for migration** when you receive update notices
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
\ No newline at end of file
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
diff --git a/src/content/docs/pages/configuration/deploy-hooks.mdx b/src/content/docs/pages/configuration/deploy-hooks.mdx
index 66418eb9f810990..b40eb6d48f435bb 100644
--- a/src/content/docs/pages/configuration/deploy-hooks.mdx
+++ b/src/content/docs/pages/configuration/deploy-hooks.mdx
@@ -19,6 +19,7 @@ To create a Deploy Hook:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Builds** and select **Add deploy hook** to start configuration.
 
diff --git a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
index 377ecb62654d209..46e064b4a0d8063 100644
--- a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
+++ b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
@@ -68,6 +68,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Import from an existing Git repository**.
 3. Select your new GitHub repository.
 4. In the **Set up builds and deployments**, set `npm run build` as the **Build command**, and `dist` as the **Build output directory**.
diff --git a/src/content/docs/pages/functions/api-reference.mdx b/src/content/docs/pages/functions/api-reference.mdx
index e15d8a9a4aa0a15..9a521a8c592d30b 100644
--- a/src/content/docs/pages/functions/api-reference.mdx
+++ b/src/content/docs/pages/functions/api-reference.mdx
@@ -18,35 +18,27 @@ The following methods can be used to configure your Pages Function.
 The `onRequest` method will be called unless a more specific `onRequestVerb` method is exported. For example, if both `onRequest` and `onRequestGet` are exported, only `onRequestGet` will be called for `GET` requests.
 
 - <code>onRequest(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all requests no matter what the request method is, as long as no specific request verb (like one of the methods below) is exported.
 
 - <code>onRequestGet(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `GET` requests.
 
 - <code>onRequestPost(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `POST` requests.
 
 - <code>onRequestPatch(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `PATCH` requests.
 
 - <code>onRequestPut(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `PUT` requests.
 
 - <code>onRequestDelete(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `DELETE` requests.
 
 - <code>onRequestHead(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `HEAD` requests.
 
 - <code>onRequestOptions(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `OPTIONS` requests.
 
 ### `env.ASSETS.fetch()`
diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx
index b6f53b59192f9eb..4b1016b85d127f3 100644
--- a/src/content/docs/pages/functions/bindings.mdx
+++ b/src/content/docs/pages/functions/bindings.mdx
@@ -14,7 +14,13 @@ products:
   - durable-objects
 ---
 
-import { Render, TabItem, Tabs, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 A [binding](/workers/runtime-apis/bindings/) enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like [KV](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2](/r2/), and [D1](/d1/). You can set bindings for both production and preview environments.
 
@@ -37,6 +43,7 @@ To configure a KV namespace binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **KV namespace**.
 4. Give your binding a name under **Variable name**.
@@ -97,6 +104,7 @@ To configure a Durable Object binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Durable Object**.
 4. Give your binding a name under **Variable name**.
@@ -161,6 +169,7 @@ To configure a R2 bucket binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **R2 bucket**.
 4. Give your binding a name under **Variable name**.
@@ -233,6 +242,7 @@ To configure a D1 database binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add**> **D1 database bindings**.
 4. Give your binding a name under **Variable name**.
@@ -309,12 +319,13 @@ To configure a Vectorize index binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 3. Select your Pages project > **Settings**.
 4. Go to **Bindings** > **Add** > **Vectorize index**.
 5. Give your binding a name under **Variable name**.
 6. Under **Vectorize index**, select your desired Vectorize index.
-8. Redeploy your project for the binding to take effect.
+7. Redeploy your project for the binding to take effect.
 
 ### Use Vectorize index bindings
 
@@ -449,6 +460,7 @@ To configure a Workers AI binding via the Cloudflare dashboard:
 1. Go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings**.
 3. Select your Pages environment > **Bindings** > **Add** > **Workers AI**.
 4. Give your binding a name under **Variable name**.
@@ -522,6 +534,7 @@ To configure a Service binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Service binding**.
 4. Give your binding a name under **Variable name**.
@@ -586,6 +599,7 @@ To configure a queue producer binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Queue**.
 4. Give your binding a name under **Variable name**.
@@ -662,6 +676,7 @@ To configure a Hyperdrive binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Hyperdrive**.
 4. Give your binding a name under **Variable name**.
@@ -735,6 +750,7 @@ To configure an Analytics Engine binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Analytics engine**.
 4. Give your binding a name under **Variable name**.
@@ -796,6 +812,7 @@ To configure an environment variable via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add** .
 4. After setting a variable name and value, select **Save**.
@@ -854,6 +871,7 @@ To add secrets to your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add**.
 4. Set a variable name and value.
diff --git a/src/content/docs/pages/functions/examples/ab-testing.mdx b/src/content/docs/pages/functions/examples/ab-testing.mdx
index 96d45b37cd3e0f8..125a99e100cd193 100644
--- a/src/content/docs/pages/functions/examples/ab-testing.mdx
+++ b/src/content/docs/pages/functions/examples/ab-testing.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up an A/B test by controlling what page is served based on cookies.
   This version supports passing the request through to test and control on the
   origin.
diff --git a/src/content/docs/pages/functions/examples/cors-headers.mdx b/src/content/docs/pages/functions/examples/cors-headers.mdx
index 0011928013bbd10..48c58ea881e153c 100644
--- a/src/content/docs/pages/functions/examples/cors-headers.mdx
+++ b/src/content/docs/pages/functions/examples/cors-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: A Pages Functions for appending CORS headers.
 tags:
   - Headers
diff --git a/src/content/docs/pages/functions/examples/index.mdx b/src/content/docs/pages/functions/examples/index.mdx
index 26f22f52cf8ceca..a7ae43643a007ce 100644
--- a/src/content/docs/pages/functions/examples/index.mdx
+++ b/src/content/docs/pages/functions/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: Examples
 description: Code examples for common Pages Functions use cases.
diff --git a/src/content/docs/pages/functions/metrics.mdx b/src/content/docs/pages/functions/metrics.mdx
index 12b285087c355a7..802ad2e19dd4a42 100644
--- a/src/content/docs/pages/functions/metrics.mdx
+++ b/src/content/docs/pages/functions/metrics.mdx
@@ -19,6 +19,7 @@ Functions metrics aggregate request data for an individual Pages project. To vie
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. In your Pages project, select **Functions Metrics**.
 
diff --git a/src/content/docs/pages/functions/plugins/community-plugins.mdx b/src/content/docs/pages/functions/plugins/community-plugins.mdx
index 164f24737e7be5c..69d5080b51c5b6f 100644
--- a/src/content/docs/pages/functions/plugins/community-plugins.mdx
+++ b/src/content/docs/pages/functions/plugins/community-plugins.mdx
@@ -17,7 +17,6 @@ The following are some of the community-maintained Pages Plugins. If you have cr
 - [proxyflare-for-pages](https://github.com/flaregun-net/proxyflare-for-pages)
 
   Move traffic around your Cloudflare Pages domain with ease. Proxyflare is a reverse-proxy that enables you to:
-
   - Port forward, redirect, and reroute HTTP and websocket traffic anywhere on the Internet.
   - Mount an entire website on a subpath (for example, `mysite.com/docs`) on your apex domain.
   - Serve static text (like `robots.txt` and other structured metadata) from any endpoint.
diff --git a/src/content/docs/pages/get-started/c3.mdx b/src/content/docs/pages/get-started/c3.mdx
index 68c5c783012edad..c88153d094feefa 100644
--- a/src/content/docs/pages/get-started/c3.mdx
+++ b/src/content/docs/pages/get-started/c3.mdx
@@ -10,7 +10,6 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 products:
   - pages
-
 ---
 
 import {
@@ -85,30 +84,24 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
 />
 
 - `DIRECTORY` <Type text="string" /> <MetaInfo text="optional" />
-
   - The directory where the application should be created. The name of the application is taken from the directory name.
 
 - `NESTED ARGS..` <Type text="string[]" /> <MetaInfo text="optional" />
-
   - CLI arguments to pass to eventual third party CLIs C3 might invoke (in the case of full-stack applications).
 
 - `--category` <Type text="string" /> <MetaInfo text="optional" />
-
   - The kind of templates that should be created.
 
   - The possible values for this option are:
-
     - `hello-world`: Hello World example
     - `web-framework`: Framework Starter
     - `demo`: Application Starter
     - `remote-template`: Template from a GitHub repo
 
 - `--type` <Type text="string" /> <MetaInfo text="optional" />
-
   - The type of application that should be created.
 
   - The possible values for this option are:
-
     - `hello-world`: A basic "Hello World" Cloudflare Worker.
     - `hello-world-durable-object`: A [Durable Object](/durable-objects/) and a Worker to communicate with it.
     - `common`: A Cloudflare Worker which implements a common example of routing/proxying functionalities.
@@ -118,11 +111,9 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `pre-existing`: Fetch a Worker initialized from the Cloudflare dashboard.
 
 - `--framework` <Type text="string" /> <MetaInfo text="optional" />
-
   - The type of framework to use to create a web application (when using this option, `--type` is ignored).
 
   - The possible values for this option are:
-
     - `angular`
     - `astro`
     - `docusaurus`
@@ -139,11 +130,9 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `vue`
 
 - `--template` <Type text="string" /> <MetaInfo text="optional" />
-
   - Create a new project via an external template hosted in a git repository
 
   - The value for this option may be specified as any of the following:
-
     - `user/repo`
     - `git@github.com:user/repo`
     - `https://github.com/user/repo`
@@ -156,7 +145,6 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the `degit` [docs](https://github.com/Rich-Harris/degit) for more details.
 
     At a minimum, templates must contain the following:
-
     - `package.json`
     - [Wrangler configuration file](/pages/functions/wrangler-configuration/)
     - `src/` containing a worker script referenced from the Wrangler configuration file
@@ -164,51 +152,40 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the [templates folder](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare/templates) of this repo for more examples.
 
 - `--deploy` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Deploy your application after it has been created.
 
 - `--lang` <Type text="string" /> <MetaInfo text="(default: ts) optional" />
-
   - The programming language of the template.
 
   - The possible values for this option are:
-
     - `ts`
     - `js`
     - `python`
 
 - `--ts` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Use TypeScript in your application. Deprecated. Use `--lang=ts` instead.
 
 - `--git` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Initialize a local git repository for your application.
 
 - `--open` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Open with your browser the deployed application (this option is ignored if the application is not deployed).
 
 - `--existing-script` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of an existing Cloudflare Workers script to clone locally. When using this option, `--type` is coerced to `pre-existing`.
 
   - When `--existing-script` is specified, `deploy` will be ignored.
 
 - `-y`, `--accept-defaults` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Use all the default C3 options each can also be overridden by specifying it.
 
 - `--auto-update` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Automatically uses the latest version of C3.
 
 - `-v`, `--version` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Show version number.
 
 - `-h`, `--help` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Show a help message.
 
 :::note
diff --git a/src/content/docs/pages/get-started/direct-upload.mdx b/src/content/docs/pages/get-started/direct-upload.mdx
index 9f7252898b5ddba..f1f5228ef2053d0 100644
--- a/src/content/docs/pages/get-started/direct-upload.mdx
+++ b/src/content/docs/pages/get-started/direct-upload.mdx
@@ -8,7 +8,6 @@ description: Upload your prebuilt assets to Pages and deploy them via the
   Wrangler CLI or the Cloudflare dashboard.
 products:
   - pages
-
 ---
 
 import { Render, DashButton } from "~/components";
@@ -128,6 +127,7 @@ To deploy with drag and drop:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Get started** > **Drag and drop your files**.
 3. Enter your project name in the provided field and drag and drop your assets.
 4. Select **Deploy site**.
diff --git a/src/content/docs/pages/get-started/git-integration.mdx b/src/content/docs/pages/get-started/git-integration.mdx
index 3b6cb58789596cb..5ac8218965fb505 100644
--- a/src/content/docs/pages/get-started/git-integration.mdx
+++ b/src/content/docs/pages/get-started/git-integration.mdx
@@ -7,7 +7,6 @@ head:
 description: Connect your Git provider to Pages.
 products:
   - pages
-
 ---
 
 import { Details, Render } from "~/components";
diff --git a/src/content/docs/pages/get-started/index.mdx b/src/content/docs/pages/get-started/index.mdx
index 328bd28a8396d9c..e76af4b0b86da8a 100644
--- a/src/content/docs/pages/get-started/index.mdx
+++ b/src/content/docs/pages/get-started/index.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 2
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/add-custom-http-headers.mdx b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
index 3402e5e5a66d4e5..7dedb62c0645ef1 100644
--- a/src/content/docs/pages/how-to/add-custom-http-headers.mdx
+++ b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
@@ -5,7 +5,6 @@ description: Customize HTTP headers on Cloudflare Pages using a Workers function
 products:
   - pages
   - workers
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/docs/pages/how-to/build-commands-branches.mdx b/src/content/docs/pages/how-to/build-commands-branches.mdx
index 46ab3dfafb2d1a1..d91423afb902d99 100644
--- a/src/content/docs/pages/how-to/build-commands-branches.mdx
+++ b/src/content/docs/pages/how-to/build-commands-branches.mdx
@@ -5,7 +5,6 @@ title: Set build commands per branch
 description: Run different build commands on specific branches in your Cloudflare Pages project.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -46,6 +45,7 @@ To put your changes into effect:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
 4. Update the **Build command** field value to `bash build.sh` and select **Save**.
diff --git a/src/content/docs/pages/how-to/custom-branch-aliases.mdx b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
index a50f4c6b38fe0a3..818ca533a5bf852 100644
--- a/src/content/docs/pages/how-to/custom-branch-aliases.mdx
+++ b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
@@ -4,7 +4,6 @@ title: Add a custom domain to a branch
 description: Point a custom domain to a specific branch deployment of your Cloudflare Pages project.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -32,6 +31,7 @@ To do this:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Select **Custom domains** > **Setup a custom domain**.
 4. Input the domain you would like to use, such as `staging.example.com`
diff --git a/src/content/docs/pages/how-to/enable-zaraz.mdx b/src/content/docs/pages/how-to/enable-zaraz.mdx
index a421e08bb06a094..20a3092b435873c 100644
--- a/src/content/docs/pages/how-to/enable-zaraz.mdx
+++ b/src/content/docs/pages/how-to/enable-zaraz.mdx
@@ -4,7 +4,6 @@ title: Enable Zaraz
 description: Set up Zaraz on your Cloudflare Pages project using a custom domain.
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/index.mdx b/src/content/docs/pages/how-to/index.mdx
index d2707643d72ee16..3da369ff33b9913 100644
--- a/src/content/docs/pages/how-to/index.mdx
+++ b/src/content/docs/pages/how-to/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: How to
 description: Step-by-step guides for common Cloudflare Pages tasks and configurations.
@@ -9,7 +8,6 @@ sidebar:
     hideIndex: true
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/npm-private-registry.mdx b/src/content/docs/pages/how-to/npm-private-registry.mdx
index 95889b262b4dd84..a03e59ef22f9dc3 100644
--- a/src/content/docs/pages/how-to/npm-private-registry.mdx
+++ b/src/content/docs/pages/how-to/npm-private-registry.mdx
@@ -4,7 +4,6 @@ title: Install private packages
 description: Use custom npm registries and private dependencies in your Cloudflare Pages builds.
 products:
   - pages
-
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
index 8780a611c5c465c..76183d80849d09f 100644
--- a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
+++ b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
@@ -5,7 +5,6 @@ description: Use Cloudflare Tunnel to share locally running Pages projects over
 products:
   - pages
   - tunnel
-
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) runs a lightweight daemon (`cloudflared`) in your infrastructure that establishes outbound connections (Tunnels) between your origin web server and the Cloudflare global network. In practical terms, you can use Cloudflare Tunnel to allow remote access to services running on your local machine. It is an alternative to popular tools like [Ngrok](https://ngrok.com), and provides free, long-running tunnels via the [TryCloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/trycloudflare/) service.
diff --git a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
index e70f762274f2772..4349352400a31e5 100644
--- a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
+++ b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
@@ -6,7 +6,6 @@ sidebar:
   hidden: true
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
index 1770a4c1621da73..5526154ba6650bd 100644
--- a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
+++ b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
@@ -4,7 +4,6 @@ title: Use Direct Upload with continuous integration
 description: Deploy prebuilt assets to Cloudflare Pages using Wrangler in your CI/CD pipeline.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -29,6 +28,7 @@ To generate an API token:
 1. In the Cloudflare dashboard, go to the **API Tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
+
 2. Select **Create Token**.
 3. Under **Custom Token**, select **Get started**.
 4. Name your API Token in the **Token name** field.
@@ -43,7 +43,7 @@ Now that you have created your API token, you can use it to push your project fr
 
 To find your account ID, go to the **Zone Overview** page in the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/:zone/" />
+<DashButton url="/?to=/:account/:zone/" />
 
 Find your account ID in the **API** section on the right-hand side menu.
 
diff --git a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
index 2d7fb92626a856d..8e750ac70df0a77 100644
--- a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
+++ b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
@@ -4,7 +4,6 @@ title: Use Pages Functions for A/B testing
 description: Implement A/B testing in Cloudflare Pages using Pages Functions and cookies.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -162,4 +161,5 @@ After you have deployed your application, review your middleware Function:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings** > **Functions** > **Configuration**.
diff --git a/src/content/docs/pages/how-to/web-analytics.mdx b/src/content/docs/pages/how-to/web-analytics.mdx
index 723b5241d55c0e2..80cab7cc7a0ebda 100644
--- a/src/content/docs/pages/how-to/web-analytics.mdx
+++ b/src/content/docs/pages/how-to/web-analytics.mdx
@@ -4,7 +4,6 @@ title: Enable Web Analytics
 description: Set up Cloudflare Web Analytics on your Pages project with one-click configuration.
 products:
   - pages
-
 ---
 
 import { Render, DashButton } from "~/components";
@@ -24,6 +23,7 @@ To view the metrics associated with your Pages project:
 1. In the Cloudflare dashboard, go to the **Web Analytics** page.
 
    <DashButton url="/?to=/:account/web-analytics" />
+
 2. Select the analytics associated with your Pages project.
 
 For more details about how to use Web Analytics, refer to the [Web Analytics documentation](/web-analytics/data-metrics/).
diff --git a/src/content/docs/pages/migrations/index.mdx b/src/content/docs/pages/migrations/index.mdx
index dfac1294f41d646..462426a9667eb83 100644
--- a/src/content/docs/pages/migrations/index.mdx
+++ b/src/content/docs/pages/migrations/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: Migration guides
 description: Migrate your existing site from another platform to Cloudflare Pages.
@@ -8,7 +7,6 @@ sidebar:
   order: 4
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/index.mdx b/src/content/docs/pages/platform/index.mdx
index 1a133b13acfc655..925be7f4266e12b 100644
--- a/src/content/docs/pages/platform/index.mdx
+++ b/src/content/docs/pages/platform/index.mdx
@@ -8,7 +8,6 @@ sidebar:
     hideIndex: true
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/known-issues.mdx b/src/content/docs/pages/platform/known-issues.mdx
index cd105ebacb7fa5e..3a0b439ae2c0327 100644
--- a/src/content/docs/pages/platform/known-issues.mdx
+++ b/src/content/docs/pages/platform/known-issues.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 4
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -40,7 +39,6 @@ Here are some known bugs and issues with Cloudflare Pages:
 ## Custom Domains
 
 - It is currently not possible to add a custom domain with
-
   - a wildcard, for example, `*.domain.com`.
   - a Worker already routed on that domain.
 
@@ -67,6 +65,7 @@ If you would like to enable [Cloudflare Access](https://www.cloudflare.com/teams
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Enable access policy**.
 4. Select **Manage** on the Access policy created for your preview deployments.
diff --git a/src/content/docs/pages/platform/limits.mdx b/src/content/docs/pages/platform/limits.mdx
index dd994f7de3cd191..372373843e2b19a 100644
--- a/src/content/docs/pages/platform/limits.mdx
+++ b/src/content/docs/pages/platform/limits.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 1
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
@@ -18,10 +17,10 @@ Below are limits observed by the Cloudflare Free plan. For more details on remov
 ## Builds
 
 Each time you push new code to your Git repository, Pages will build and deploy your site. Build limits depend on your plan:
-|                  | Free              | Pro                 | Business             |
+| | Free | Pro | Business |
 | ---------------- | ----------------- | ------------------- | -------------------- |
-| Builds           | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
-| Builds per month | 500               | 5,000               | 20,000               |
+| Builds | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
+| Builds per month | 500 | 5,000 | 20,000 |
 
 Builds will timeout after 20 minutes. Concurrent builds are counted per account.
 
diff --git a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
index 880fe3088aafd05..499da32c9d96168 100644
--- a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
+++ b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
@@ -114,7 +114,7 @@ import ContactForm from "./ContactForm";
 Then insert the form into the page as a react component:
 
 ```jsx
-<ContactForm />
+<ContactForm />;
 ```
 
 For example, you can update your `src/App.js` file to add the form:
diff --git a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
index d8a492d5d29124e..413e037121afc72 100644
--- a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
+++ b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
@@ -365,6 +365,7 @@ After you have pushed your project to GitHub, deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Import an existing Git repository**.
 3. Select the new GitHub repository that you created and select **Begin setup**.
 4. In the **Set up builds and deployments** section, under **Build settings** > **Framework preset**, choose _Nuxt_. Pages will set the correct fields for you automatically.
diff --git a/src/content/docs/pipelines/reference/wrangler-commands.mdx b/src/content/docs/pipelines/reference/wrangler-commands.mdx
index 655d91f87e8a583..154b40b6ccb4976 100644
--- a/src/content/docs/pipelines/reference/wrangler-commands.mdx
+++ b/src/content/docs/pipelines/reference/wrangler-commands.mdx
@@ -10,5 +10,4 @@ products:
 
 import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="pipelines"/>
-
+<WranglerNamespace namespace="pipelines" />
diff --git a/src/content/docs/pipelines/sinks/manage-sinks.mdx b/src/content/docs/pipelines/sinks/manage-sinks.mdx
index 7623ca305f5c3e1..5f4d14b28b01f0a 100644
--- a/src/content/docs/pipelines/sinks/manage-sinks.mdx
+++ b/src/content/docs/pipelines/sinks/manage-sinks.mdx
@@ -101,4 +101,4 @@ Deleting a sink stops all data writes to that destination.
 ## Limitations
 
 - Sinks cannot be modified after creation. To change sink configuration, you must delete and recreate the sink.
-- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
\ No newline at end of file
+- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
diff --git a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
index b47c9b02de9b990..da91b792332d4d5 100644
--- a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
+++ b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
@@ -521,7 +521,6 @@ uuid()
 Returns the string which is replaced by another string from the specified position and specified count length.
 For example, `overlay('Txxxxas' placing 'hom' from 2 for 4) → Thomas`
 
-
 ```
 overlay(str PLACING substr FROM pos [FOR count])
 ```
diff --git a/src/content/docs/privacy-gateway/get-started.mdx b/src/content/docs/privacy-gateway/get-started.mdx
index 41f956ba77f1276..05973978d5a98cd 100644
--- a/src/content/docs/privacy-gateway/get-started.mdx
+++ b/src/content/docs/privacy-gateway/get-started.mdx
@@ -14,13 +14,13 @@ Privacy Gateway implementation consists of three main parts:
 2. Client configuration (operated by you).
 3. Connection to a Privacy Gateway Relay Server (operated by Cloudflare).
 
-***
+---
 
 ## Before you begin
 
 Privacy Gateway is currently in closed beta. If you are interested, [contact us](https://www.cloudflare.com/lp/privacy-edge/).
 
-***
+---
 
 ## Step 1 - Configure your server
 
@@ -34,13 +34,13 @@ Applications can also implement this functionality themselves. Details about [pu
 
 Use the following resources for help with server configuration:
 
-* **Go**:
-  * [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
-  * [Gateway library](https://github.com/chris-wood/ohttp-go)
-* **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
-* **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
+- **Go**:
+  - [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
+  - [Gateway library](https://github.com/chris-wood/ohttp-go)
+- **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
+- **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
 
-***
+---
 
 ## Step 2 - Configure your client
 
@@ -52,21 +52,21 @@ Additionally, app developers need to [configure the client](#resources-1) to fet
 
 Use the following resources for help with client configuration:
 
-* **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
-* **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
-* **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
+- **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
+- **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
+- **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
 
-***
+---
 
 ## Step 3 - Review your application
 
 After you have configured your client and server, review your application to make sure you are only sending intended data to Cloudflare and the application backend. In particular, application data should not contain anything unique to an end-user, as this would invalidate the benefits that OHTTP provides.
 
-* Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
-* Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
-* Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
+- Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
+- Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
+- Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
 
-***
+---
 
 ## Step 4 - Relay requests through Cloudflare
 
diff --git a/src/content/docs/privacy-gateway/reference/index.mdx b/src/content/docs/privacy-gateway/reference/index.mdx
index 50d23832e8505f7..bdcb0f1f7729beb 100644
--- a/src/content/docs/privacy-gateway/reference/index.mdx
+++ b/src/content/docs/privacy-gateway/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - privacy-gateway
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/privacy-gateway/reference/legal.mdx b/src/content/docs/privacy-gateway/reference/legal.mdx
index 22928aac224e0f6..8f68db4684d0d76 100644
--- a/src/content/docs/privacy-gateway/reference/legal.mdx
+++ b/src/content/docs/privacy-gateway/reference/legal.mdx
@@ -24,5 +24,5 @@ Cloudflare retains the Privacy Gateway Logs information for the most recent quar
 
 ## What Privacy Gateway customers see
 
-* The application content of requests.
-* The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
+- The application content of requests.
+- The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
diff --git a/src/content/docs/privacy-gateway/reference/metrics.mdx b/src/content/docs/privacy-gateway/reference/metrics.mdx
index f40cb4d6ffbc6ee..6a0751366ca483b 100644
--- a/src/content/docs/privacy-gateway/reference/metrics.mdx
+++ b/src/content/docs/privacy-gateway/reference/metrics.mdx
@@ -10,8 +10,8 @@ products:
 
 Privacy Gateway now supports enhanced monitoring through our GraphQL API, providing detailed insights into your gateway traffic and performance. To access these metrics, ensure you have:
 
-* A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
-* An API token with Analytics Read permissions.
+- A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
+- An API token with Analytics Read permissions.
   We offer two GraphQL nodes to retrieve metrics: `ohttpMetricsAdaptive` and `ohttpMetricsAdaptiveGroups`. The first node provides comprehensive request data, while the second facilitates grouped analytics.
 
 ## ohttpMetricsAdaptive
@@ -20,33 +20,27 @@ The `ohttpMetricsAdaptive` node is designed for detailed insights into individua
 
 ### Key Arguments
 
-
-
-* `filter` required
-  * Apply filters to narrow down your data set. `accountTag` is a required filter.
-* `limit`  optional
-  * Specify the maximum number of records to return.
-* `orderBy` optional
-  * Choose how to sort your data, with options for various dimensions and metrics.
-
+- `filter` required
+  - Apply filters to narrow down your data set. `accountTag` is a required filter.
+- `limit` optional
+  - Specify the maximum number of records to return.
+- `orderBy` optional
+  - Choose how to sort your data, with options for various dimensions and metrics.
 
 ### Available Fields
 
-
-
-* `bytesToClient` int optional
-  * The number of bytes returned to the client.
-* `bytesToGateway` int optional
-  * Total bytes received from the client.
-* `colo` string optional
-  * Airport code of the Cloudflare data center that served the request.
-* `datetime` Time optional
-  * The date and time when the event was recorded.
-* `gatewayStatusCode` int optional
-  * Status code returned by the gateway.
-* `relayStatusCode` int optional
-  * Status code returned by the relay.
-
+- `bytesToClient` int optional
+  - The number of bytes returned to the client.
+- `bytesToGateway` int optional
+  - Total bytes received from the client.
+- `colo` string optional
+  - Airport code of the Cloudflare data center that served the request.
+- `datetime` Time optional
+  - The date and time when the event was recorded.
+- `gatewayStatusCode` int optional
+  - Status code returned by the gateway.
+- `relayStatusCode` int optional
+  - Status code returned by the relay.
 
 This node is useful for a granular view of traffic, helping you identify patterns, performance issues, or anomalies in your data flow.
 
@@ -56,66 +50,56 @@ The `ohttpMetricsAdaptiveGroups` node allows for aggregated analysis of OHTTP re
 
 ### Key Arguments
 
-
-
-* `filter` required
-  * Apply filters to narrow down your data set. `accountTag` is a required filter.
-* `limit`  optional
-  * Specify the maximum number of records to return.
-* `orderBy` optional
-  * Choose how to sort your data, with options for various dimensions and metrics.
-
+- `filter` required
+  - Apply filters to narrow down your data set. `accountTag` is a required filter.
+- `limit` optional
+  - Specify the maximum number of records to return.
+- `orderBy` optional
+  - Choose how to sort your data, with options for various dimensions and metrics.
 
 ### Available Fields
 
-
-
-* `count` int optional
-  * The number of records that meet the criteria.
-* `dimensions` optional
-  * Specifies the grouping dimensions for your data.
-* `sum` optional
-  * Aggregated totals for various metrics, per dimension.
-
+- `count` int optional
+  - The number of records that meet the criteria.
+- `dimensions` optional
+  - Specifies the grouping dimensions for your data.
+- `sum` optional
+  - Aggregated totals for various metrics, per dimension.
 
 **Dimensions**
 
 You can group your metrics by various dimensions to get a more segmented view of your data:
 
-
-* `colo` string optional
-  * The airport code of the Cloudflare data center.
-* `date` Date optional
-  * The date of OHTTP request metrics.
-* `datetimeFifteenMinutes` Time optional
-  * Timestamp truncated to fifteen minutes.
-* `datetimeFiveMinutes` Time optional
-  * Timestamp truncated to five minutes.
-* `datetimeHour` Time optional
-  * Timestamp truncated to the hour.
-* `datetimeMinute` Time optional
-  * Timestamp truncated to the minute.
-* `endpoint` string optional
-  * The appId that generated traffic.
-* `gatewayStatusCode` int optional
-  * Status code returned by the gateway.
-* `relayStatusCode` int optional
-  * Status code returned by the relay.
-
+- `colo` string optional
+  - The airport code of the Cloudflare data center.
+- `date` Date optional
+  - The date of OHTTP request metrics.
+- `datetimeFifteenMinutes` Time optional
+  - Timestamp truncated to fifteen minutes.
+- `datetimeFiveMinutes` Time optional
+  - Timestamp truncated to five minutes.
+- `datetimeHour` Time optional
+  - Timestamp truncated to the hour.
+- `datetimeMinute` Time optional
+  - Timestamp truncated to the minute.
+- `endpoint` string optional
+  - The appId that generated traffic.
+- `gatewayStatusCode` int optional
+  - Status code returned by the gateway.
+- `relayStatusCode` int optional
+  - Status code returned by the relay.
 
 **Sum Fields**
 
 Sum fields offer a cumulative view of various metrics over your selected time period:
 
-
-* `bytesToClient` int optional
-  * Total bytes sent from the gateway to the client.
-* `bytesToGateway` int optional
-  * Total bytes from the client to the gateway.
-* `clientRequestErrors` int optional
-  * Total number of client request errors.
-* `gatewayResponseErrors` int optional
-  * Total number of gateway response errors.
-
+- `bytesToClient` int optional
+  - Total bytes sent from the gateway to the client.
+- `bytesToGateway` int optional
+  - Total bytes from the client to the gateway.
+- `clientRequestErrors` int optional
+  - Total number of client request errors.
+- `gatewayResponseErrors` int optional
+  - Total number of gateway response errors.
 
 Utilize the ohttpMetricsAdaptiveGroups node to gain comprehensive, aggregated insights into your traffic patterns, helping you optimize performance and user experience.
diff --git a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
index f6f435416d2e986..e319b9824e7ef2c 100644
--- a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
+++ b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
@@ -12,6 +12,6 @@ When [using Privacy Gateway](/privacy-gateway/get-started/), the majority of Clo
 
 However, the following products are not compatible:
 
-* [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
-* [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
-* [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
+- [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
+- [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
+- [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
diff --git a/src/content/docs/privacy-proxy/concepts/authentication.mdx b/src/content/docs/privacy-proxy/concepts/authentication.mdx
index 5adead0bc45a818..344ac01c3d65a39 100644
--- a/src/content/docs/privacy-proxy/concepts/authentication.mdx
+++ b/src/content/docs/privacy-proxy/concepts/authentication.mdx
@@ -14,11 +14,11 @@ Privacy Proxy requires clients to authenticate before proxying traffic. This pag
 
 Privacy Proxy supports three authentication methods:
 
-| Method | Use case | Privacy level |
-| -------- | ---------- | --------------- |
-| Pre-shared key (PSK) | Proof of concept, testing | Lower |
-| Privacy Pass tokens | Client to server | High |
-| mTLS | Server to server | Higher |
+| Method               | Use case                  | Privacy level |
+| -------------------- | ------------------------- | ------------- |
+| Pre-shared key (PSK) | Proof of concept, testing | Lower         |
+| Privacy Pass tokens  | Client to server          | High          |
+| mTLS                 | Server to server          | Higher        |
 
 ---
 
@@ -166,7 +166,7 @@ Proxy A (which you operate) authenticates users. Common methods include:
 - Privacy Pass tokens issued by your infrastructure
 - Client certificates (mTLS)
 
-### Proxy A to Proxy B 
+### Proxy A to Proxy B
 
 Proxy B authenticates itself to Proxy A using TLS. Depending on your configuration, this can use:
 
diff --git a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
index 72190396733d8b8..dfe5168ada7b9a2 100644
--- a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
+++ b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
@@ -65,12 +65,12 @@ In a double-hop deployment, you operate the first proxy (Proxy A), and Cloudflar
 
 The double-hop architecture ensures:
 
-| Information | Proxy A (you) | Proxy B (Cloudflare) |
-| ------------- | --------------- | ---------------------- |
-| Client IP address | Yes | No |
-| User account | Yes | No |
-| Destination server | Encrypted | Yes |
-| Request content | Encrypted | Encrypted |
+| Information        | Proxy A (you) | Proxy B (Cloudflare) |
+| ------------------ | ------------- | -------------------- |
+| Client IP address  | Yes           | No                   |
+| User account       | Yes           | No                   |
+| Destination server | Encrypted     | Yes                  |
+| Request content    | Encrypted     | Encrypted            |
 
 Proxy A knows who the user is but cannot see where they are going (the destination is encrypted). Proxy B knows the destination but not who is making the request. Neither party has the complete picture.
 
@@ -90,13 +90,13 @@ Double-hop deployment works well when:
 
 ## Comparison
 
-| Aspect | Single-hop | Double-hop |
-| -------- | ------------ | ------------ |
-| Infrastructure | Cloudflare only | You + Cloudflare |
-| Privacy separation | Proxy sees identity + destination | Split across two parties |
-| Operational complexity | Lower | Higher |
-| Authentication | Cloudflare-managed | You manage first-hop auth |
-| Use case | Browser VPNs, simple privacy | Maximum privacy separation |
+| Aspect                 | Single-hop                        | Double-hop                 |
+| ---------------------- | --------------------------------- | -------------------------- |
+| Infrastructure         | Cloudflare only                   | You + Cloudflare           |
+| Privacy separation     | Proxy sees identity + destination | Split across two parties   |
+| Operational complexity | Lower                             | Higher                     |
+| Authentication         | Cloudflare-managed                | You manage first-hop auth  |
+| Use case               | Browser VPNs, simple privacy      | Maximum privacy separation |
 
 ---
 
diff --git a/src/content/docs/privacy-proxy/concepts/geolocation.mdx b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
index 987c5e96e5514ab..2c60dc4cbde92c0 100644
--- a/src/content/docs/privacy-proxy/concepts/geolocation.mdx
+++ b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
@@ -30,12 +30,12 @@ Privacy Proxy uses geohashes to preserve location without revealing precise coor
 A [geohash](https://en.wikipedia.org/wiki/Geohash) is a compact representation of latitude and longitude. Geohashes use a hierarchical encoding where longer strings represent more precise locations:
 
 | Geohash length | Approximate area |
-| ---------------- | ------------------ |
-| 1 character | ~5,000 km |
-| 2 characters | ~1,250 km |
-| 3 characters | ~150 km |
-| 4 characters | ~40 km |
-| 5 characters | ~5 km |
+| -------------- | ---------------- |
+| 1 character    | ~5,000 km        |
+| 2 characters   | ~1,250 km        |
+| 3 characters   | ~150 km          |
+| 4 characters   | ~40 km           |
+| 5 characters   | ~5 km            |
 
 Privacy Proxy uses reduced-precision geohashes (typically four to five characters) to locate users to a city or region without pinpointing their exact location.
 
diff --git a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
index 3c4634922f9757c..6d1b3146f38fc82 100644
--- a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
+++ b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
@@ -35,15 +35,14 @@ Privacy Proxy uses the MASQUE protocol suite to create encrypted tunnels between
 
 Throughout this process, the proxy learns the destination but not the content. The destination learns the egress IP address but not the client's real IP.
 
-
 ## MASQUE protocols
 
 [MASQUE](https://datatracker.ietf.org/wg/masque/about/) (Multiplexed Application Substrate over QUIC Encryption) defines methods for proxying traffic over HTTP. Privacy Proxy supports two MASQUE methods:
 
-| Method | Transport | Use case |
-| -------- | ----------- | ---------- |
-| HTTP CONNECT | TCP | Traditional HTTPS traffic |
-| CONNECT-UDP | UDP | QUIC-based traffic, real-time applications |
+| Method       | Transport | Use case                                   |
+| ------------ | --------- | ------------------------------------------ |
+| HTTP CONNECT | TCP       | Traditional HTTPS traffic                  |
+| CONNECT-UDP  | UDP       | QUIC-based traffic, real-time applications |
 
 Both methods create encrypted tunnels where the proxy forwards traffic without inspecting the content. The proxy sees only the destination hostname and port, not the actual requests, paths, or data exchanged.
 
@@ -55,11 +54,11 @@ For a technical deep dive into how these protocols work, refer to our [blog post
 
 Privacy Proxy creates a privacy boundary between user identity and user activity:
 
-| Information | Who knows it |
-| ------------- | -------------- |
+| Information                         | Who knows it                                                  |
+| ----------------------------------- | ------------------------------------------------------------- |
 | User identity (IP address, account) | Authentication service, first-hop proxy (if using double-hop) |
-| Destination server | Privacy Proxy, destination server |
-| Request content | Client, destination server only |
+| Destination server                  | Privacy Proxy, destination server                             |
+| Request content                     | Client, destination server only                               |
 
 The proxy authenticates users to verify they have permission to use the service, but authentication happens separately from proxying. Once authenticated, the proxy forwards traffic without linking individual requests to specific users.
 
diff --git a/src/content/docs/privacy-proxy/get-started.mdx b/src/content/docs/privacy-proxy/get-started.mdx
index f07aa967b04f5d0..951b12a8ad7876e 100644
--- a/src/content/docs/privacy-proxy/get-started.mdx
+++ b/src/content/docs/privacy-proxy/get-started.mdx
@@ -37,7 +37,7 @@ curl -v \
   https://example.com
 ```
 
-### Use Chaussette 
+### Use Chaussette
 
 [Chaussette](/privacy-proxy/reference/client-libraries/#chaussette) is a local SOCKS5 proxy that handles authentication and forwards requests to Privacy Proxy.
 
diff --git a/src/content/docs/privacy-proxy/reference/http-headers.mdx b/src/content/docs/privacy-proxy/reference/http-headers.mdx
index 39788fd3a51a37b..da3750df07b72b9 100644
--- a/src/content/docs/privacy-proxy/reference/http-headers.mdx
+++ b/src/content/docs/privacy-proxy/reference/http-headers.mdx
@@ -30,10 +30,10 @@ Privacy Pass token format:
 Proxy-Authorization: PrivateToken token=<base64-encoded-token>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
-| `<key>` | The pre-shared key provided by Cloudflare |
-| `<base64-encoded-token>` | A base64-encoded Privacy Pass token |
+| Parameter                | Description                               |
+| ------------------------ | ----------------------------------------- |
+| `<key>`                  | The pre-shared key provided by Cloudflare |
+| `<base64-encoded-token>` | A base64-encoded Privacy Pass token       |
 
 ### GraphQL Analytics API request headers
 
@@ -47,10 +47,10 @@ Specifies the client's geographic location for egress IP selection. Optional but
 sec-ch-geohash: <geohash>-<country_code>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
-| `<geohash>` | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
-| `<country_code>` | ISO 3166-1 alpha-2 country code |
+| Parameter        | Description                                                                          |
+| ---------------- | ------------------------------------------------------------------------------------ |
+| `<geohash>`      | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
+| `<country_code>` | ISO 3166-1 alpha-2 country code                                                      |
 
 ```http title="Example"
 sec-ch-geohash: u4pruydqqvj-GB
@@ -72,8 +72,8 @@ Provides timing information about proxy processing. This is part of the [OpenTel
 Server-Timing: proxy;dur=<milliseconds>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
+| Parameter        | Description                                             |
+| ---------------- | ------------------------------------------------------- |
 | `<milliseconds>` | Processing time in milliseconds introduced by the proxy |
 
 ```http title="Example"
@@ -99,9 +99,9 @@ sec-ch-geohash: 9q8yy-US
 
 The proxy responds with a status code indicating success or failure:
 
-| Status | Meaning |
-| -------- | --------- |
-| `200 OK` | Tunnel established successfully |
-| `403 Forbidden` | Authentication failed |
-| `502 Bad Gateway` | Could not connect to destination |
-| `503 Service Unavailable` | Proxy temporarily unavailable |
+| Status                    | Meaning                          |
+| ------------------------- | -------------------------------- |
+| `200 OK`                  | Tunnel established successfully  |
+| `403 Forbidden`           | Authentication failed            |
+| `502 Bad Gateway`         | Could not connect to destination |
+| `503 Service Unavailable` | Proxy temporarily unavailable    |
diff --git a/src/content/docs/privacy-proxy/reference/proxy-status.mdx b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
index 8a0a873a9b6ca6f..3cd177c2306ccca 100644
--- a/src/content/docs/privacy-proxy/reference/proxy-status.mdx
+++ b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
@@ -16,29 +16,29 @@ The `proxyStatus` dimension provides proxy-level error classification. This fiel
 
 ## `proxyStatus` values
 
-| Value | Description |
-| --- | --- |
-| `dns_error` | The proxy encountered a DNS error when resolving the next hop hostname. |
-| `dns_timeout` | The proxy timed out while resolving the next hop hostname. |
-| `destination_not_found` | The proxy cannot determine the appropriate next hop for this request. |
-| `destination_unavailable` | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
-| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address. |
-| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address. |
-| `connection_refused` | The proxy's connection to the next hop was refused. |
-| `connection_terminated` | The proxy's connection to the next hop was closed before any response was received. |
-| `connection_timeout` | The proxy's attempt to open a connection to the next hop timed out. |
-| `connection_read_timeout` | The proxy was expecting data on a connection but received none within the configured time limit. |
-| `connection_write_timeout` | The proxy was attempting to write data to a connection but was unable to. |
-| `connection_limit_reached` | The proxy's configured connection limit to the next hop has been exceeded. |
-| `source_addr_in_use` | The proxy cannot assign a source address when connecting to the next hop. |
-| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure). |
-| `tls_protocol_error` | The proxy encountered a TLS error when communicating with the next hop. |
-| `tls_certificate_error` | The proxy encountered an error verifying the certificate presented by the next hop. |
-| `http_request_error` | The proxy is generating a client (4xx) response on the origin's behalf. |
-| `http_upgrade_failed` | The HTTP Upgrade between the proxy and the next hop failed. |
-| `http_request_denied` | The proxy rejected the HTTP request based on its configuration or policy. |
-| `proxy_internal_error` | The proxy encountered an internal error unrelated to the origin. |
-| `proxy_loop_detected` | The proxy tried to forward the request to itself. |
-| `http_protocol_error` | The proxy encountered an HTTP protocol error when communicating with the next hop. |
-| `http_response_incomplete` | The proxy received an incomplete response from the next hop. |
-| `rate_limited` | The client has reached the maximum number of connections per second to a single origin. |
+| Value                       | Description                                                                                          |
+| --------------------------- | ---------------------------------------------------------------------------------------------------- |
+| `dns_error`                 | The proxy encountered a DNS error when resolving the next hop hostname.                              |
+| `dns_timeout`               | The proxy timed out while resolving the next hop hostname.                                           |
+| `destination_not_found`     | The proxy cannot determine the appropriate next hop for this request.                                |
+| `destination_unavailable`   | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
+| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address.                          |
+| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address.                                            |
+| `connection_refused`        | The proxy's connection to the next hop was refused.                                                  |
+| `connection_terminated`     | The proxy's connection to the next hop was closed before any response was received.                  |
+| `connection_timeout`        | The proxy's attempt to open a connection to the next hop timed out.                                  |
+| `connection_read_timeout`   | The proxy was expecting data on a connection but received none within the configured time limit.     |
+| `connection_write_timeout`  | The proxy was attempting to write data to a connection but was unable to.                            |
+| `connection_limit_reached`  | The proxy's configured connection limit to the next hop has been exceeded.                           |
+| `source_addr_in_use`        | The proxy cannot assign a source address when connecting to the next hop.                            |
+| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure).           |
+| `tls_protocol_error`        | The proxy encountered a TLS error when communicating with the next hop.                              |
+| `tls_certificate_error`     | The proxy encountered an error verifying the certificate presented by the next hop.                  |
+| `http_request_error`        | The proxy is generating a client (4xx) response on the origin's behalf.                              |
+| `http_upgrade_failed`       | The HTTP Upgrade between the proxy and the next hop failed.                                          |
+| `http_request_denied`       | The proxy rejected the HTTP request based on its configuration or policy.                            |
+| `proxy_internal_error`      | The proxy encountered an internal error unrelated to the origin.                                     |
+| `proxy_loop_detected`       | The proxy tried to forward the request to itself.                                                    |
+| `http_protocol_error`       | The proxy encountered an HTTP protocol error when communicating with the next hop.                   |
+| `http_response_incomplete`  | The proxy received an incomplete response from the next hop.                                         |
+| `rate_limited`              | The client has reached the maximum number of connections per second to a single origin.              |
diff --git a/src/content/docs/pulumi/tutorial/index.mdx b/src/content/docs/pulumi/tutorial/index.mdx
index a221bc981254072..2d5a00e48f838d0 100644
--- a/src/content/docs/pulumi/tutorial/index.mdx
+++ b/src/content/docs/pulumi/tutorial/index.mdx
@@ -12,19 +12,16 @@ products:
 Before you begin, make sure you [install Pulumi](/pulumi/installing/).
 
 1. [Add a Site](/pulumi/tutorial/add-site/)
-
    - Bring your existing site under Cloudflare with Pulumi IaC.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Zone and DNS records.
 
 2. [Manage secrets](/pulumi/tutorial/manage-secrets/)
-
    - Develop Workers securely with Pulumi ESC and Wrangler.
    - Introduction to the ESC CLI and the Wrangler CLI.
    - Manage Cloudflare credentials, Worker secrets, and `.dev.vars`.
 
 3. [Deploy a Worker](/pulumi/tutorial/hello-world/)
-
    - Brief introduction to deploying a Cloudflare Workers application with Pulumi.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Worker script, Worker route, and DNS record.
diff --git a/src/content/docs/queues/configuration/configure-queues.mdx b/src/content/docs/queues/configuration/configure-queues.mdx
index 67aaf22fcf32e57..cec7b05be692f5a 100644
--- a/src/content/docs/queues/configuration/configure-queues.mdx
+++ b/src/content/docs/queues/configuration/configure-queues.mdx
@@ -15,35 +15,33 @@ import { WranglerConfig, Type } from "~/components";
 
 Cloudflare Queues can be configured using [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Cloudflare's Developer Platform, which includes [Workers](/workers/), [R2](/r2/), and other developer products.
 
-
 Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
 
 Use the options below to configure your queue.
 
 :::note
 
-
 Below are options for queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
 
-
 :::
 
 ## Queue configuration
+
 The following queue level settings can be configured using Wrangler:
 
 ```sh
 npx wrangler queues update <QUEUE-NAME> --delivery-delay-secs 60 --message-retention-period-secs 3000
 ```
 
-* `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
-	* How long a published message is delayed for, before it is delivered to consumers.
-	* Must be between 0 and 86400 (24 hours).
-	* Defaults to 0.
+- `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
+  - How long a published message is delayed for, before it is delivered to consumers.
+  - Must be between 0 and 86400 (24 hours).
+  - Defaults to 0.
 
-* `--message-retention-period-secs`  <Type text="number" /> <Type text="optional" />
-	* How long messages are retained on the Queue.
-	* Defaults to 345600 (4 days).
-	* Must be between 60 and 1209600 (14 days)
+- `--message-retention-period-secs` <Type text="number" /> <Type text="optional" />
+  - How long messages are retained on the Queue.
+  - Defaults to 345600 (4 days).
+  - Must be between 60 and 1209600 (14 days)
 
 ## Producer Worker configuration
 
@@ -68,24 +66,16 @@ To produce to a queue, set up a binding in your Wrangler file. These options sho
 
 </WranglerConfig>
 
+- <code>queue</code> <Type text="string" />
+  - The name of the queue.
 
-
-* <code>queue</code> <Type text="string" />
-
-  * The name of the queue.
-
-* <code>binding</code> <Type text="string" />
-
-  * The name of the binding, which is a JavaScript variable.
-
-
+- <code>binding</code> <Type text="string" />
+  - The name of the binding, which is a JavaScript variable.
 
 ## Consumer Worker Configuration
 
 To consume messages from one or more queues, set up a binding in your Wrangler file. These options should be used when a Worker wants to receive messages from a queue.
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -108,39 +98,29 @@ To consume messages from one or more queues, set up a binding in your Wrangler f
 
 Refer to [Limits](/queues/platform/limits) to review the maximum values for each of these options.
 
+- <code>queue</code> <Type text="string" />
+  - The name of the queue.
 
+- <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of messages allowed in each batch.
+  - Defaults to `10` messages.
 
-* <code>queue</code> <Type text="string" />
-
-  * The name of the queue.
-
-* <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of messages allowed in each batch.
-  * Defaults to `10` messages.
-
-* <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of seconds to wait until a batch is full.
-  * Defaults to `5` seconds.
-
-* <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
-  * Defaults to `3` retries.
-
-* <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
-
-  * The name of another queue to send a message if it fails processing at least `max_retries` times.
-  * If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
-  * If there is no queue with the specified name, it will be created automatically.
-
-* <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
+- <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of seconds to wait until a batch is full.
+  - Defaults to `5` seconds.
 
-  * The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
-  * Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
+- <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
+  - Defaults to `3` retries.
 
+- <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
+  - The name of another queue to send a message if it fails processing at least `max_retries` times.
+  - If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
+  - If there is no queue with the specified name, it will be created automatically.
 
+- <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
+  - Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
 ## Pull-based
 
diff --git a/src/content/docs/queues/configuration/consumer-concurrency.mdx b/src/content/docs/queues/configuration/consumer-concurrency.mdx
index 072aa3381bd5001..503b8d2fdba5fa2 100644
--- a/src/content/docs/queues/configuration/consumer-concurrency.mdx
+++ b/src/content/docs/queues/configuration/consumer-concurrency.mdx
@@ -71,7 +71,7 @@ To configure the concurrency settings for your consumer Worker from the dashboar
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select your queue > **Settings**.
 3. Select **Edit Consumer** under Consumer details.
diff --git a/src/content/docs/queues/configuration/index.mdx b/src/content/docs/queues/configuration/index.mdx
index fb230019e4a5916..bc7e0d0237bb4c5 100644
--- a/src/content/docs/queues/configuration/index.mdx
+++ b/src/content/docs/queues/configuration/index.mdx
@@ -8,6 +8,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/configuration/javascript-apis.mdx b/src/content/docs/queues/configuration/javascript-apis.mdx
index 9a34dca675084e9..a948c75c6c39862 100644
--- a/src/content/docs/queues/configuration/javascript-apis.mdx
+++ b/src/content/docs/queues/configuration/javascript-apis.mdx
@@ -94,30 +94,27 @@ A binding that allows a producer to send messages to a Queue.
 
 ```ts
 interface Queue<Body = unknown> {
-  send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
-  sendBatch(messages: Iterable<MessageSendRequest<Body>>, options?: QueueSendBatchOptions): Promise<QueueSendResult>;
-  metrics(): Promise<QueueMetrics>;
+	send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
+	sendBatch(
+		messages: Iterable<MessageSendRequest<Body>>,
+		options?: QueueSendBatchOptions,
+	): Promise<QueueSendResult>;
+	metrics(): Promise<QueueMetrics>;
 }
 ```
 
+- `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
+  - Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+  - When the promise resolves, the message is confirmed to be written to disk.
+  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
 
+- `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
+  - Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
+  - The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
+  - When the promise resolves, the messages are confirmed to be written to disk.
 
-* `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
-
-  * Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-  * When the promise resolves, the message is confirmed to be written to disk.
-  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
-
-* `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
-
-  * Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
-  * The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
-  * When the promise resolves, the messages are confirmed to be written to disk.
-
-* `metrics()` <Type text="Promise<QueueMetrics>" />
-
-  * Returns realtime [QueueMetrics](#queuemetrics) for the queue.
-
+- `metrics()` <Type text="Promise<QueueMetrics>" />
+  - Returns realtime [QueueMetrics](#queuemetrics) for the queue.
 
 ### `MessageSendRequest`
 
@@ -125,54 +122,44 @@ A wrapper type used for sending message batches.
 
 ```ts
 interface MessageSendRequest<Body = unknown> {
-  body: Body;
-  contentType?: QueueContentType;
-  delaySeconds?: number;
+	body: Body;
+	contentType?: QueueContentType;
+	delaySeconds?: number;
 }
 ```
 
+- <code>body</code> <Type text="unknown" />
+  - The body of the message.
+  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
+- <code>contentType</code> <Type text="QueueContentType" />
+  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-* <code>body</code> <Type text="unknown" />
-
-  * The body of the message.
-  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-
-* <code>contentType</code> <Type text="QueueContentType" />
-
-  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  * See [QueuesContentType](#queuescontenttype) for possible values.
-
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be an integer between 0 and 86400 (24 hours).
-
-
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be an integer between 0 and 86400 (24 hours).
 
 ### `QueueSendOptions`
 
 Optional configuration that applies when sending a message to a queue.
 
-* <code>contentType</code> <Type text="QueuesContentType" />
-
-  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  * As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
-  * See [QueuesContentType](#queuescontenttype) for possible values.
+- <code>contentType</code> <Type text="QueuesContentType" />
+  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  - As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
+  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
 
 ### `QueueSendBatchOptions`
 
 Optional configuration that applies when sending a batch of messages to a queue.
 
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be a positive integer.
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be a positive integer.
 
 ### `QueuesContentType`
 
@@ -183,17 +170,15 @@ A union type containing valid message content types.
 type QueuesContentType = "text" | "bytes" | "json" | "v8";
 ```
 
-* Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
-* Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
-* Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
-* Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+- Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
+- Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
+- Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+- Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
 
 :::note
 
-
 The default content type for Queues changed to `json` (from `v8`) to improve compatibility with pull-based consumers for any Workers with a [compatibility date](/workers/configuration/compatibility-flags/#queues-send-messages-in-json-format) after `2024-03-18`.
 
-
 :::
 
 If you specify an invalid content type, or if your specified content type does not match the message content's type, the send operation will fail with an error.
@@ -210,15 +195,11 @@ interface QueueSendResult {
 }
 ```
 
+- <code>metadata</code> <Type text="object" />
+  - Contains metadata about the queue after the send operation.
 
-
-* <code>metadata</code> <Type text="object" />
-
-  * Contains metadata about the queue after the send operation.
-
-* <code>metadata.metrics</code> <Type text="QueueMetrics" />
-
-  * Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
+- <code>metadata.metrics</code> <Type text="QueueMetrics" />
+  - Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
 
 ### `QueueMetrics`
 
@@ -232,19 +213,14 @@ interface QueueMetrics {
 }
 ```
 
+- <code>backlogCount</code> <Type text="number" />
+  - The number of messages currently in the queue.
 
+- <code>backlogBytes</code> <Type text="number" />
+  - The total size of messages in the queue, in bytes.
 
-* <code>backlogCount</code> <Type text="number" />
-
-  * The number of messages currently in the queue.
-
-* <code>backlogBytes</code> <Type text="number" />
-
-  * The total size of messages in the queue, in bytes.
-
-* <code>oldestMessageTimestamp</code> <Type text="number" />
-
-  * The timestamp (in milliseconds since epoch) of the oldest message in the queue.
+- <code>oldestMessageTimestamp</code> <Type text="number" />
+  - The timestamp (in milliseconds since epoch) of the oldest message in the queue.
 
 ## Consumer
 
@@ -262,10 +238,8 @@ If the `queue()` function throws, or the promise returned by it or any of the pr
 
 :::note
 
-
 `waitUntil()` is the only supported method to run tasks (such as logging or metrics calls) that resolve after a queue handler has completed. Promises that have not resolved by the time the queue handler returns may not complete and will not block completion of execution.
 
-
 :::
 
 <Tabs syncKey="workersExamples">
@@ -304,19 +278,19 @@ You can type queue messages with `Queue<T>` on the producer and `ExportedHandler
 
 ```ts
 type MyMessage = {
-  id: string;
+	id: string;
 };
 
 interface Env {
-  MY_QUEUE: Queue<MyMessage>;
+	MY_QUEUE: Queue<MyMessage>;
 }
 
 export default {
-  async queue(batch) {
-    for (const message of batch.messages) {
-      console.log(message.body.id);
-    }
-  },
+	async queue(batch) {
+		for (const message of batch.messages) {
+			console.log(message.body.id);
+		}
+	},
 } satisfies ExportedHandler<Env, MyMessage>;
 ```
 
@@ -325,7 +299,7 @@ For primitive messages, use `Queue<number>` or `satisfies ExportedHandler<Env, n
 Or alternatively, a queue consumer can be written using the (deprecated) service worker syntax:
 
 ```js
-addEventListener('queue', (event) => {
+addEventListener("queue", (event) => {
 	event.waitUntil(handleMessages(event));
 });
 ```
@@ -334,10 +308,8 @@ In service worker syntax, `event` provides the same fields and methods as `Messa
 
 :::note
 
-
 When performing asynchronous tasks in your queue handler that iterates through messages, use an asynchronous version of iterating through your messages. For example, `for (const m of batch.messages)`or `await Promise.all(batch.messages.map(work))` allow for waiting for the results of asynchronous calls. `batch.messages.forEach()` does not.
 
-
 :::
 
 ### `MessageBatch`
@@ -346,34 +318,25 @@ A batch of messages that are sent to a consumer Worker.
 
 ```ts
 interface MessageBatch<Body = unknown> {
-  readonly queue: string;
-  readonly messages: readonly Message<Body>[];
-  ackAll(): void;
-  retryAll(options?: QueueRetryOptions): void;
+	readonly queue: string;
+	readonly messages: readonly Message<Body>[];
+	ackAll(): void;
+	retryAll(options?: QueueRetryOptions): void;
 }
 ```
 
+- <code>queue</code> <Type text="string" />
+  - The name of the Queue that belongs to this batch.
 
+- <code>messages</code> <Type text="Message[]" />
+  - An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
 
-* <code>queue</code> <Type text="string" />
-
-  * The name of the Queue that belongs to this batch.
-
-* <code>messages</code> <Type text="Message[]" />
-
-  * An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
-
-* <code>ackAll()</code> <Type text="void" />
-
-
-  * Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
-
-* <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
-
-  * Marks every message to be retried in the next batch.
-  * Supports an optional `options` object.
-
+- <code>ackAll()</code> <Type text="void" />
+  - Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
+- <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
+  - Marks every message to be retried in the next batch.
+  - Supports an optional `options` object.
 
 ### `Message`
 
@@ -381,44 +344,34 @@ A message that is sent to a consumer Worker.
 
 ```ts
 interface Message<Body = unknown> {
-  readonly id: string;
-  readonly timestamp: Date;
-  readonly body: Body;
+	readonly id: string;
+	readonly timestamp: Date;
+	readonly body: Body;
 	readonly attempts: number;
-  ack(): void;
-  retry(options?: QueueRetryOptions): void;
+	ack(): void;
+	retry(options?: QueueRetryOptions): void;
 }
 ```
 
+- <code>id</code> <Type text="string" />
+  - A unique, system-generated ID for the message.
 
+- <code>timestamp</code> <Type text="Date" />
+  - A timestamp when the message was sent.
 
-* <code>id</code> <Type text="string" />
-
-  * A unique, system-generated ID for the message.
-
-* <code>timestamp</code> <Type text="Date" />
-
-  * A timestamp when the message was sent.
-
-* <code>body</code> <Type text="unknown" />
-
-  * The body of the message.
-  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-
-* <code>attempts</code> <Type text="number" />
-
-	* The number of times the consumer has attempted to process this message. Starts at 1.
-
-* <code>ack()</code> <Type text="void" />
-
-  * Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
-
-* <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
+- <code>body</code> <Type text="unknown" />
+  - The body of the message.
+  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
-  * Marks a message to be retried in the next batch.
-  * Supports an optional `options` object.
+- <code>attempts</code> <Type text="number" />
+  - The number of times the consumer has attempted to process this message. Starts at 1.
 
+- <code>ack()</code> <Type text="void" />
+  - Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
+- <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
+  - Marks a message to be retried in the next batch.
+  - Supports an optional `options` object.
 
 ### `QueueRetryOptions`
 
@@ -426,13 +379,13 @@ Optional configuration when marking a message or a batch of messages for retry.
 
 ```ts
 interface QueueRetryOptions {
-  delaySeconds?: number;
+	delaySeconds?: number;
 }
 ```
 
-* <code>delaySeconds</code> <Type text="number" />
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be a positive integer.
 
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be a positive integer.
-* When the promise resolves, the messages are written to disk.
-  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+- When the promise resolves, the messages are written to disk.
+  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
diff --git a/src/content/docs/queues/configuration/local-development.mdx b/src/content/docs/queues/configuration/local-development.mdx
index 69ba57856a90286..557fb80e5c067c5 100644
--- a/src/content/docs/queues/configuration/local-development.mdx
+++ b/src/content/docs/queues/configuration/local-development.mdx
@@ -23,6 +23,7 @@ To develop locally with Queues, you will need:
 ## Start a local development session
 
 Open your terminal and run the following commands to start a local development session:
+
 ```sh
 npx wrangler@latest dev
 ```
@@ -40,13 +41,15 @@ Local development sessions create a standalone, local-only environment that mirr
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/general/#dev) to learn more about how to configure a local development session.
 
 ## Separating producer & consumer Workers
+
 Wrangler supports running multiple Workers simultaneously with a single command. If your architecture separates the producer and consumer into distinct Workers, you can use this functionality to test the entire message flow locally.
 
 :::caution
 Support for running multiple Workers at once with one Wrangler command is experimental, and subject to change as we work on the experience. If you run into bugs or have any feedback, [open an issue on the workers-sdk repository](https://github.com/cloudflare/workers-sdk/issues/new)
 :::
 
-For example, if your project has the following directory structure: 
+For example, if your project has the following directory structure:
+
 ```
 producer-worker/
 ├── wrangler.jsonc
@@ -57,6 +60,7 @@ producer-worker/
 ```
 
 You can start development servers for both workers with the following command:
+
 ```sh
 npx wrangler@latest dev -c wrangler.jsonc -c consumer-worker/wrangler.jsonc --persist-to .wrangler/state
 ```
@@ -67,4 +71,5 @@ When the producer Worker sends messages to the queue, the consumer Worker will a
 :::
 
 ## Known Issues
+
 - Queues does not support Wrangler remote mode (`wrangler dev --remote`).
diff --git a/src/content/docs/queues/configuration/pause-purge.mdx b/src/content/docs/queues/configuration/pause-purge.mdx
index 0ca72cdbb02b121..aa3e793a9a0dc2e 100644
--- a/src/content/docs/queues/configuration/pause-purge.mdx
+++ b/src/content/docs/queues/configuration/pause-purge.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - queues
 ---
+
 import { WranglerConfig, Type, MetaInfo } from "~/components";
 
 ## Pause Delivery
@@ -38,9 +39,11 @@ $ npx wrangler queues resume-delivery <QUEUE-NAME>
   - The name of the queue for which delivery should be resumed.
 
 ### What happens to HTTP Pull consumers with a paused queue?
+
 When a queue is paused, messages cannot be pulled by an [HTTP pull based consumer](/queues/configuration/pull-consumers). Requests to pull messages will receive a `409` response, along with an error message stating `queue_delivery_paused`.
 
 ## Purge queue
+
 Purging a queue permanently deletes any messages currently stored in the Queue. Purging is useful while developing a new application, especially to clear out any test data. It can also be useful in production to handle scenarios when a batch of bad messages have been sent to a Queue.
 
 Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the queue.
@@ -50,7 +53,9 @@ Purging a queue is an irreversible operation. Make sure to use this operation ca
 :::
 
 ### Purge queue using Wrangler
+
 The following command will purge messages from your queue. You will be prompted to enter the queue name to confirm the operation.
+
 ```sh
 $ npx wrangler queues purge <QUEUE-NAME>
 
@@ -58,4 +63,5 @@ This operation will permanently delete all the messages in Queue <QUEUE-NAME>. T
 ```
 
 ### Does purging a Queue affect my bill?
+
 Purging a queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.
diff --git a/src/content/docs/queues/event-subscriptions/index.mdx b/src/content/docs/queues/event-subscriptions/index.mdx
index 7fea1b1b89a7a1d..8d7a0aa847de518 100644
--- a/src/content/docs/queues/event-subscriptions/index.mdx
+++ b/src/content/docs/queues/event-subscriptions/index.mdx
@@ -12,7 +12,7 @@ products:
   - workers
 ---
 
-import { LinkCard } from "~/components"
+import { LinkCard } from "~/components";
 
 Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products (e.g., [KV](/kv/), [Workers AI](/workers-ai), [Workers](/workers)) can publish structured events to a queue, which you can then consume with Workers or [HTTP pull consumers](/queues/configuration/pull-consumers/) to build custom workflows, integrations, or logic.
 
@@ -34,4 +34,4 @@ An event is a structured record of something happening in your Cloudflare accoun
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event types and their corresponding data schemas."
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
index aa2f5a7998b8f6d..d7dc089f45b0751 100644
--- a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
+++ b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
@@ -8,11 +8,7 @@ sidebar:
   order: 1
 ---
 
-import {
-	Steps,
-	LinkCard,
-	DashButton,
-} from "~/components";
+import { Steps, LinkCard, DashButton } from "~/components";
 
 Learn how to:
 
@@ -102,4 +98,4 @@ npx wrangler queues subscription delete <queue-name> --id <subscription-id>
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event sources and types that you can subscribe to."
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
index 58bc8f327afbbc5..4875bc7d1174f24 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
@@ -22,7 +22,6 @@ This allows you to write to a Queue from any service or programming language tha
 - A [queue created](/queues/get-started/#3-create-a-queue) via the [Cloudflare dashboard](https://dash.cloudflare.com) or the [wrangler CLI](/workers/wrangler/install-and-update/).
 - A Cloudflare API token with the `Queues Edit` permission.
 
-
 ### 1. Send a test message
 
 To make sure you successfully authenticate and write a message to your queue, use `curl` on the command line:
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
index 45926ceeb6e587d..fb595d622adf56c 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
@@ -66,7 +66,10 @@ export default {
 			messages = await req.json();
 		} catch {
 			// Return a HTTP 400 (Bad Request) if the payload isn't JSON
-			return Response.json({ error: "payload not valid JSON" }, { status: 400 });
+			return Response.json(
+				{ error: "payload not valid JSON" },
+				{ status: 400 },
+			);
 		}
 
 		// Publish to the Queue
diff --git a/src/content/docs/queues/examples/send-errors-to-r2.mdx b/src/content/docs/queues/examples/send-errors-to-r2.mdx
index ba6649a7b277a6a..0ff30d559be40f2 100644
--- a/src/content/docs/queues/examples/send-errors-to-r2.mdx
+++ b/src/content/docs/queues/examples/send-errors-to-r2.mdx
@@ -63,33 +63,33 @@ interface Env {
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      return doRequest(req);
-    } catch (e) {
-      const error: ErrorMessage = {
-        message: e instanceof Error ? e.message : String(e),
-        stack: e instanceof Error ? e.stack : undefined,
-      };
-      await env.ERROR_QUEUE.send(error);
-      return new Response(error.message, { status: 500 });
-    }
-  },
-  async queue(batch, env, ctx): Promise<void> {
-    let file = "";
-    for (const message of batch.messages) {
-      const error = message.body;
-      file += error.stack ?? error.message;
-      file += "\r\n";
-    }
-    await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			return doRequest(req);
+		} catch (e) {
+			const error: ErrorMessage = {
+				message: e instanceof Error ? e.message : String(e),
+				stack: e instanceof Error ? e.stack : undefined,
+			};
+			await env.ERROR_QUEUE.send(error);
+			return new Response(error.message, { status: 500 });
+		}
+	},
+	async queue(batch, env, ctx): Promise<void> {
+		let file = "";
+		for (const message of batch.messages) {
+			const error = message.body;
+			file += error.stack ?? error.message;
+			file += "\r\n";
+		}
+		await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
+	},
 } satisfies ExportedHandler<Env, ErrorMessage>;
 
 function doRequest(request: Request): Response {
-  if (Math.random() > 0.5) {
-    return new Response("Success!");
-  }
-  throw new Error("Failed!");
+	if (Math.random() > 0.5) {
+		return new Response("Success!");
+	}
+	throw new Error("Failed!");
 }
 ```
diff --git a/src/content/docs/queues/examples/send-messages-from-dash.mdx b/src/content/docs/queues/examples/send-messages-from-dash.mdx
index 6d384b6b6bd668a..1a2b6cc2f1b7455 100644
--- a/src/content/docs/queues/examples/send-messages-from-dash.mdx
+++ b/src/content/docs/queues/examples/send-messages-from-dash.mdx
@@ -22,14 +22,14 @@ To send messages from the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select the queue to send a message to.
 3. Select the **Messages** tab.
 4. Select **Send**.
 5. Choose your message **Content Type**: _Text_ or _JSON_.
-5. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
-6. Select **Send**.
+6. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
+7. Select **Send**.
 
 Your message will be sent to the queue.
 
diff --git a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
index 481b9a11fe9e225..4803ac4d16c217c 100644
--- a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
+++ b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
@@ -73,45 +73,45 @@ Extending the `DurableObject` base class makes your `Env` available on `this.env
 import { DurableObject } from "cloudflare:workers";
 
 interface Env {
-  YOUR_QUEUE: Queue;
-  YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
+	YOUR_QUEUE: Queue;
+	YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    // Assume each Durable Object is mapped to a userId in a query parameter
-    // In a production application, this will be a userId defined by your application
-    // that you validate (and/or authenticate) first.
-    const url = new URL(req.url);
-    const userIdParam = url.searchParams.get("userId");
-
-    if (userIdParam) {
-      // Get a stub that allows you to call that Durable Object
-      const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
-
-      // Pass the request to that Durable Object and await the response
-      // This invokes the constructor once on your Durable Object class (defined further down)
-      // on the first initialization, and the fetch method on each request.
-      // We pass the original Request to the Durable Object's fetch method
-      const response = await durableObjectStub.fetch(req);
-
-      // This would return "wrote to queue", but you could return any response.
-      return response;
-    }
-    return new Response("userId must be provided", { status: 400 });
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		// Assume each Durable Object is mapped to a userId in a query parameter
+		// In a production application, this will be a userId defined by your application
+		// that you validate (and/or authenticate) first.
+		const url = new URL(req.url);
+		const userIdParam = url.searchParams.get("userId");
+
+		if (userIdParam) {
+			// Get a stub that allows you to call that Durable Object
+			const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
+
+			// Pass the request to that Durable Object and await the response
+			// This invokes the constructor once on your Durable Object class (defined further down)
+			// on the first initialization, and the fetch method on each request.
+			// We pass the original Request to the Durable Object's fetch method
+			const response = await durableObjectStub.fetch(req);
+
+			// This would return "wrote to queue", but you could return any response.
+			return response;
+		}
+		return new Response("userId must be provided", { status: 400 });
+	},
 } satisfies ExportedHandler<Env>;
 
 export class YourDurableObject extends DurableObject<Env> {
-  async fetch(req: Request): Promise<Response> {
-    // Error handling elided for brevity.
-    // Publish to your queue
-    await this.env.YOUR_QUEUE.send({
-      id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
-      // Write any other properties to your queue
-    });
-
-    return new Response("wrote to queue");
-  }
+	async fetch(req: Request): Promise<Response> {
+		// Error handling elided for brevity.
+		// Publish to your queue
+		await this.env.YOUR_QUEUE.send({
+			id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
+			// Write any other properties to your queue
+		});
+
+		return new Response("wrote to queue");
+	}
 }
 ```
diff --git a/src/content/docs/queues/glossary.mdx b/src/content/docs/queues/glossary.mdx
index 845aecc4bdd10b3..4bb72d0ab69bbf6 100644
--- a/src/content/docs/queues/glossary.mdx
+++ b/src/content/docs/queues/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - queues
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Queues documentation.
 
diff --git a/src/content/docs/queues/observability/index.mdx b/src/content/docs/queues/observability/index.mdx
index c9ebe21e8103fb1..7becde1ad32ae99 100644
--- a/src/content/docs/queues/observability/index.mdx
+++ b/src/content/docs/queues/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/observability/metrics.mdx b/src/content/docs/queues/observability/metrics.mdx
index e003fb8ca5507e5..39c918a48ff366b 100644
--- a/src/content/docs/queues/observability/metrics.mdx
+++ b/src/content/docs/queues/observability/metrics.mdx
@@ -74,10 +74,10 @@ The `queueMessageOperationsAdaptiveGroups` dataset provides the following dimens
 
 You can access realtime backlog metrics via the [Queues REST API](/api/resources/queues/) and [JavaScript API](/queues/configuration/javascript-apis/). These metrics provide point-in-time values rather than aggregated data.
 
-| Metric                   | Field Name                 | Description                                                    |
-| ------------------------ | -------------------------- | -------------------------------------------------------------- |
-| Backlog count            | `backlog_count`            | Number of messages currently in the queue                      |
-| Backlog bytes            | `backlog_bytes`            | Total size of messages in the queue, in bytes                  |
+| Metric                   | Field Name                    | Description                                                    |
+| ------------------------ | ----------------------------- | -------------------------------------------------------------- |
+| Backlog count            | `backlog_count`               | Number of messages currently in the queue                      |
+| Backlog bytes            | `backlog_bytes`               | Total size of messages in the queue, in bytes                  |
 | Oldest message timestamp | `oldest_message_timestamp_ms` | Timestamp (in milliseconds) of the oldest message in the queue |
 
 To retrieve these metrics via the REST API, use the metrics endpoint (`/accounts/{account_id}/queues/{queue_id}/metrics`).
diff --git a/src/content/docs/queues/platform/index.mdx b/src/content/docs/queues/platform/index.mdx
index a227085598b92e9..db2ed89685726c9 100644
--- a/src/content/docs/queues/platform/index.mdx
+++ b/src/content/docs/queues/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/platform/limits.mdx b/src/content/docs/queues/platform/limits.mdx
index 4ca7f09527545a6..7da1292c246a72b 100644
--- a/src/content/docs/queues/platform/limits.mdx
+++ b/src/content/docs/queues/platform/limits.mdx
@@ -8,42 +8,49 @@ products:
   - queues
 ---
 
-import { Render, WranglerConfig } from "~/components"
+import { Render, WranglerConfig } from "~/components";
 
 :::caution
 The following limits apply to both Workers Paid and Workers Free plans with the exception of **Message Retention**, which is non-configurable at 24 hours for the Workers Free plan.
 :::
 
-| Feature                                       									| Limit                                                         |
-| ----------------------------------------------------------------| ------------------------------------------------------------- |
-| Queues                                        									| 10,000 per account								                            |
-| Message size                                  									| 128 KB <sup>1</sup>                                           |
-| Message retries                               									| 100                                                           |
-| Maximum consumer batch size                   									| 100 messages 								                                  |
-| Maximum messages per `sendBatch` call         									| 100 (or 256KB in total)                                       |
-| Maximum Batch wait time                       									| 60 seconds                                                    |
-| Per-queue message throughput    																| 5,000 messages per second <sup>2</sup>                        |
-| Message retention period <sup>3</sup>         									| [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration). |
-| Per-queue backlog size <sup>4</sup>           									| 25GB                                                          |
-| Concurrent consumer invocations               									| 250 <sup>push-based only</sup>                                |
-| Consumer duration (wall clock time) 														| 15 minutes <sup>5</sup>                                       |
-| [Consumer CPU time](/workers/platform/limits/#cpu-time)| [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) 							|
-| `visibilityTimeout` (pull-based queues)       									| 12 hours                                                      |
-| `delaySeconds` (when sending or retrying)     									| 24 hours                                                      |
-
-<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100 bytes of internal metadata that counts towards total message limits.
-
-<sup>2</sup> Exceeding the maximum message throughput will cause the `send()` and `sendBatch()` methods to throw an exception with a `Too Many Requests` error until your producer falls below the limit.
-
-<sup>3</sup> Messages in a queue that reach the maximum message retention are deleted from the queue. Queues does not delete messages in the same queue that have not reached this limit.
-
-<sup>4</sup> Individual queues that reach this limit will receive a `Storage Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
+| Feature                                                 | Limit                                                                                             |
+| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| Queues                                                  | 10,000 per account                                                                                |
+| Message size                                            | 128 KB <sup>1</sup>                                                                               |
+| Message retries                                         | 100                                                                                               |
+| Maximum consumer batch size                             | 100 messages                                                                                      |
+| Maximum messages per `sendBatch` call                   | 100 (or 256KB in total)                                                                           |
+| Maximum Batch wait time                                 | 60 seconds                                                                                        |
+| Per-queue message throughput                            | 5,000 messages per second <sup>2</sup>                                                            |
+| Message retention period <sup>3</sup>                   | [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration).        |
+| Per-queue backlog size <sup>4</sup>                     | 25GB                                                                                              |
+| Concurrent consumer invocations                         | 250 <sup>push-based only</sup>                                                                    |
+| Consumer duration (wall clock time)                     | 15 minutes <sup>5</sup>                                                                           |
+| [Consumer CPU time](/workers/platform/limits/#cpu-time) | [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) |
+| `visibilityTimeout` (pull-based queues)                 | 12 hours                                                                                          |
+| `delaySeconds` (when sending or retrying)               | 24 hours                                                                                          |
+
+<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100
+bytes of internal metadata that counts towards total message limits.
+
+<sup>2</sup> Exceeding the maximum message throughput will cause the `send()`
+and `sendBatch()` methods to throw an exception with a `Too Many Requests` error
+until your producer falls below the limit.
+
+<sup>3</sup> Messages in a queue that reach the maximum message retention are
+deleted from the queue. Queues does not delete messages in the same queue that
+have not reached this limit.
+
+<sup>4</sup> Individual queues that reach this limit will receive a `Storage
+Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
 
 <sup>5</sup> Refer to [Workers limits](/workers/platform/limits/#cpu-time).
 
 <Render file="limits_increase" product="workers" />
 
 ### Increasing Queue Consumer Worker CPU Limits
+
 [Queue consumer Workers](/queues/reference/how-queues-works/#consumers) are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#account-plan-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O.
 
 By default, the maximum CPU time per consumer Worker invocation is set to 30 seconds, but can be increased by setting `limits.cpu_ms` in your Wrangler configuration:
diff --git a/src/content/docs/queues/platform/pricing.mdx b/src/content/docs/queues/platform/pricing.mdx
index f8336c97f5b08a3..0a2d005b5559044 100644
--- a/src/content/docs/queues/platform/pricing.mdx
+++ b/src/content/docs/queues/platform/pricing.mdx
@@ -11,7 +11,7 @@ products:
   - queues
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="queues_pricing" product="workers" />
 
@@ -19,23 +19,16 @@ import { Render } from "~/components"
 
 If an application writes, reads and deletes (consumes) one million messages a day (in a 30 day month), and each message is less than 64 KB in size, the estimated bill for the month would be:
 
-
-
 |                     | Total Usage           | Free Usage | Billed Usage | Price      |
 | ------------------- | --------------------- | ---------- | ------------ | ---------- |
 | Standard operations | 3 \* 30 \* 1,000,000  | 1,000,000  | 89,000,000   | $35.60     |
 |                     | (write, read, delete) |            |              |            |
 | **TOTAL**           |                       |            |              | **$35.60** |
 
-
-
 An application that writes, reads and deletes (consumes) 100 million \~127 KB messages (each message counts as two 64 KB chunks) per month would have an estimated bill resembling the following:
 
-
-
 |                     | Total Usage                  | Free Usage | Billed Usage | Price       |
 | ------------------- | ---------------------------- | ---------- | ------------ | ----------- |
 | Standard operations | 2 \* 3 \* 100 \* 1,000,000   | 1,000,000  | 599,000,000  | $239.60     |
 |                     | (2x ops for > 64KB messages) |            |              |             |
 | **TOTAL**           |                              |            |              | **$239.60** |
-
diff --git a/src/content/docs/queues/reference/delivery-guarantees.mdx b/src/content/docs/queues/reference/delivery-guarantees.mdx
index 1f78e3276a09305..bd589fd8317c267 100644
--- a/src/content/docs/queues/reference/delivery-guarantees.mdx
+++ b/src/content/docs/queues/reference/delivery-guarantees.mdx
@@ -12,8 +12,8 @@ Delivery guarantees define how strongly a messaging system enforces the delivery
 
 As you make stronger guarantees about message delivery, the system needs to perform more checks and acknowledgments to ensure that messages are delivered, or maintain state to ensure a message is only delivered the specified number of times. This increases the latency of the system and reduces the overall throughput of the system. Each message may require an additional internal acknowledgements, and an equivalent number of additional roundtrips, before it can be considered delivered.
 
-* **Queues provides *at least once* delivery by default** in order to optimize for reliability.
-* This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
-* For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
+- **Queues provides _at least once_ delivery by default** in order to optimize for reliability.
+- This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
+- For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
 
 In cases where processing the same message more than once would introduce unintended behaviour, generating a unique ID when writing the message to the queue and using that as the primary key on database inserts and/or as an idempotency key to de-duplicate the message after processing. For example, using this idempotency key as the ID in an upstream email API or payment API will allow those services to reject the duplicate on your behalf, without you having to carry additional state in your application.
diff --git a/src/content/docs/queues/reference/error-codes.mdx b/src/content/docs/queues/reference/error-codes.mdx
index 1a227b114e29bfe..94d502fd00435b6 100644
--- a/src/content/docs/queues/reference/error-codes.mdx
+++ b/src/content/docs/queues/reference/error-codes.mdx
@@ -17,7 +17,7 @@ For the [JavaScript APIs](/queues/configuration/javascript-apis/), Queues operat
 ```js
 try {
 	await env.MY_QUEUE.send("message", { delaySeconds: 999999 });
-    return new Response("Sent message to the queue");
+	return new Response("Sent message to the queue");
 } catch (error) {
 	console.error(error);
 	return new Response("Failed to send message to the queue", { status: 500 });
@@ -28,20 +28,18 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ```json
 {
-  "errors": [
-    {
-      "code": 7003,
-      "message": "No route for the URI",
-      "documentation_url": "documentation_url",
-      "source": {
-        "pointer": "pointer"
-      }
-    }
-  ],
-  "messages": [
-    "string"
-  ],
-  "success": true
+	"errors": [
+		{
+			"code": 7003,
+			"message": "No route for the URI",
+			"documentation_url": "documentation_url",
+			"source": {
+				"pointer": "pointer"
+			}
+		}
+	],
+	"messages": ["string"],
+	"success": true
 }
 ```
 
@@ -49,19 +47,19 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ### Client side errors
 
-| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                                                                                       |
-| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                                                                                       |
-| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                                                                            |
-| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                                                                             |
-| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                                                                                       |
-| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                                                                                   |
+| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                           |
+| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                           |
+| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                |
+| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                 |
+| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                           |
+| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                       |
 | 10203      | MessageMetadataInvalid   | Invalid message metadata (includes invalid content type and invalid delay) | Ensure `contentType` is one of `text`, `bytes`, `json`, or `v8`. Ensure the message delay does not exceed the [maximum of 24 hours](/queues/platform/limits/) |
-| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                                                                                           |
-| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                                                                             |
-| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                                                                                      |
-| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                                                                                         |
-| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                                                                                                                         |
+| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                               |
+| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                 |
+| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                          |
+| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                             |
+| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                    |
 
 ### 429 type errors
 
diff --git a/src/content/docs/queues/reference/how-queues-works.mdx b/src/content/docs/queues/reference/how-queues-works.mdx
index efc649900122fdd..807d34b52e91d6c 100644
--- a/src/content/docs/queues/reference/how-queues-works.mdx
+++ b/src/content/docs/queues/reference/how-queues-works.mdx
@@ -29,9 +29,9 @@ Queues does not guarantee that messages will be delivered to a consumer in the s
 
 Developers can create multiple queues. Creating multiple queues can be useful to:
 
-* Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
-* Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
-* Configure different batching strategies for each consumer connected to a queue.
+- Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
+- Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
+- Configure different batching strategies for each consumer connected to a queue.
 
 For most applications, a single producer Worker per queue, with a single consumer Worker consuming messages from that queue allows you to logically separate the processing for each of your queues.
 
@@ -43,31 +43,29 @@ For example, if we bound a queue named `my-first-queue` to a binding of `MY_FIRS
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    const message = {
-      url: req.url,
-      method: req.method,
-      headers: Object.fromEntries(req.headers),
-    };
-
-    await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
-    return new Response("Sent!");
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		const message = {
+			url: req.url,
+			method: req.method,
+			headers: Object.fromEntries(req.headers),
+		};
+
+		await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
+		return new Response("Sent!");
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
 :::note
 
-
 You can also use [`context.waitUntil()`](/workers/runtime-apis/context/#waituntil) to send the message without blocking the response.
 
 Note that because `waitUntil()` is non-blocking, any errors raised from the `send()` or `sendBatch()` methods on a queue will be implicitly ignored.
 
-
 :::
 
 A queue can have multiple producer Workers. For example, you may have multiple producer Workers writing events or logs to a shared queue based on incoming HTTP requests from users. There is no limit to the total number of producer Workers that can write to a single queue.
@@ -82,25 +80,25 @@ To explicitly set the content type or specify an alternative content type, pass
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    const message = {
-      url: req.url,
-      method: req.method,
-      headers: Object.fromEntries(req.headers),
-    };
-    try {
-      await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
-      return new Response("Sent!");
-    } catch (e) {
-      // Catch cases where send fails, including due to a mismatched content type
-      const msg = e instanceof Error ? e.message : "Unknown error";
-      return Response.json({ error: msg }, { status: 500 });
-    }
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		const message = {
+			url: req.url,
+			method: req.method,
+			headers: Object.fromEntries(req.headers),
+		};
+		try {
+			await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
+			return new Response("Sent!");
+		} catch (e) {
+			// Catch cases where send fails, including due to a mismatched content type
+			const msg = e instanceof Error ? e.message : "Unknown error";
+			return Response.json({ error: msg }, { status: 500 });
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -108,21 +106,21 @@ To only accept simple strings when writing to a queue, set `{ contentType: "text
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      // This will throw an exception (error) if you pass a non-string to the queue,
-      // such as a native JavaScript object or ArrayBuffer.
-      await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
-      return new Response("Sent!");
-    } catch (e) {
-      const msg = e instanceof Error ? e.message : "Unknown error";
-      return Response.json({ error: msg }, { status: 500 });
-    }
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			// This will throw an exception (error) if you pass a non-string to the queue,
+			// such as a native JavaScript object or ArrayBuffer.
+			await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
+			return new Response("Sent!");
+		} catch (e) {
+			const msg = e instanceof Error ? e.message : "Unknown error";
+			return Response.json({ error: msg }, { status: 500 });
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -139,22 +137,22 @@ A queue can only have one type of consumer configured.
 
 ### Create a consumer Worker
 
-A consumer is the term for a client that is subscribing to or *consuming* messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
+A consumer is the term for a client that is subscribing to or _consuming_ messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
 
 ```ts
 interface Env {
-  // Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
+	// Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
 }
 
 export default {
-  async queue(batch, env, ctx): Promise<void> {
-    // Do something with messages in the batch
-    // i.e. write to R2 storage, D1 database, or POST to an external API
-    for (const msg of batch.messages) {
-      // Process each message
-      console.log(msg.body);
-    }
-  },
+	async queue(batch, env, ctx): Promise<void> {
+		// Do something with messages in the batch
+		// i.e. write to R2 storage, D1 database, or POST to an external API
+		for (const msg of batch.messages) {
+			// Process each message
+			console.log(msg.body);
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -182,42 +180,40 @@ Importantly, each queue can only have one active consumer. This allows Cloudflar
 
 :::note[Best practice]
 
-
 Configure a single consumer per queue. This both logically separates your queues, and ensures that errors (failures) in processing messages from one queue do not impact your other queues.
 
-
 :::
 
 Notably, you can use the same consumer with multiple queues. The queue handler that defines your consumer Worker will be invoked by the queues it is connected to.
 
-* The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
-* This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
+- The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
+- This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
 
 For example, a consumer configured to consume messages from multiple queues would resemble the following:
 
 ```ts
 interface Env {
-  // Add your bindings here
+	// Add your bindings here
 }
 
 export default {
-  async queue(batch, env, ctx): Promise<void> {
-    // MessageBatch has a `queue` property we can switch on
-    switch (batch.queue) {
-      case "log-queue":
-        // Write the batch to R2
-        break;
-      case "debug-queue":
-        // Write the message to the console or to another queue
-        break;
-      case "email-reset":
-        // Trigger a password reset email via an external API
-        break;
-      default:
-        // Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
-        break;
-    }
-  },
+	async queue(batch, env, ctx): Promise<void> {
+		// MessageBatch has a `queue` property we can switch on
+		switch (batch.queue) {
+			case "log-queue":
+				// Write the batch to R2
+				break;
+			case "debug-queue":
+				// Write the message to the console or to another queue
+				break;
+			case "email-reset":
+				// Trigger a password reset email via an external API
+				break;
+			default:
+				// Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
+				break;
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
diff --git a/src/content/docs/queues/reference/index.mdx b/src/content/docs/queues/reference/index.mdx
index 5470c10d9bcf385..a4b4b60c39f76b3 100644
--- a/src/content/docs/queues/reference/index.mdx
+++ b/src/content/docs/queues/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
index ca3746a34a661dd..1f5af0257e338e5 100644
--- a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
+++ b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
@@ -27,15 +27,15 @@ This page summarizes supported features, limitations, and best practices.
 | 173 scalar functions                                    | Yes       | Math, string, datetime, regex, crypto, array, map, struct, JSON              |
 | 33 aggregate functions                                  | Yes       | Basic, approximate, statistical, bitwise, boolean, positional                |
 | Approximate aggregates                                  | Yes       | `approx_distinct`, `approx_median`, `approx_percentile_cont`, `approx_top_k` |
-| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions           |
+| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions              |
 | CTEs (`WITH ... AS`)                                    | Yes       | Can reference different tables and include JOINs                             |
 | JOINs (INNER, LEFT, RIGHT, FULL OUTER, CROSS)           | Yes       | All standard join types                                                      |
-| Implicit joins (comma FROM)                              | Yes       |                                                                              |
-| Subqueries (`IN`, `NOT IN`)                              | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
-| Subqueries (`EXISTS`, `NOT EXISTS`)                      | Yes       | semi-join and anti-join patterns                                             |
-| Scalar subqueries                                        | Yes       | In SELECT, WHERE, HAVING                                                     |
-| Derived tables (FROM subqueries)                         | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
-| Self-joins                                               | Yes       | Same table with different aliases                                            |
+| Implicit joins (comma FROM)                             | Yes       |                                                                              |
+| Subqueries (`IN`, `NOT IN`)                             | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
+| Subqueries (`EXISTS`, `NOT EXISTS`)                     | Yes       | semi-join and anti-join patterns                                             |
+| Scalar subqueries                                       | Yes       | In SELECT, WHERE, HAVING                                                     |
+| Derived tables (FROM subqueries)                        | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
+| Self-joins                                              | Yes       | Same table with different aliases                                            |
 | Window functions (`OVER`)                               | No        |                                                                              |
 | `SELECT DISTINCT`                                       | No        | Use `approx_distinct`                                                        |
 | `OFFSET`                                                | No        |                                                                              |
@@ -49,44 +49,44 @@ For the full SQL syntax, refer to the [SQL reference](/r2-sql/sql-reference/).
 
 ## Unsupported SQL features
 
-| Feature                                                                       | Error                                                    |
-| :---------------------------------------------------------------------------- | :------------------------------------------------------- |
-| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported`  |
-| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`    |
-| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                             |
-| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`    |
-| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                     |
-| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                     |
-| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                            |
-| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                            |
-| Nested (parenthesized) joins                                                  | Not supported                                            |
-| `LATERAL` derived tables                                                      | Not supported                                            |
-| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                            |
+| Feature                                                                       | Error                                                   |
+| :---------------------------------------------------------------------------- | :------------------------------------------------------ |
+| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported` |
+| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`   |
+| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                            |
+| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`   |
+| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                    |
+| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                    |
+| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                           |
+| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                           |
+| Nested (parenthesized) joins                                                  | Not supported                                           |
+| `LATERAL` derived tables                                                      | Not supported                                           |
+| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                           |
 
 ---
 
 ## Unsupported expression patterns
 
-| Pattern                                                 | Alternative                                                                                       |
-| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------ |
-| `func(DISTINCT ...)` on any aggregate                   | Use `approx_distinct` for counting                                                                |
-| `PERCENTILE_CONT` / `PERCENTILE_DISC`                   | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
-| `MEDIAN`                                                | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
-| `ARRAY_AGG`                                             | No alternative (unsupported for memory safety)                                                    |
-| `STRING_AGG`                                            | No alternative (unsupported for memory safety)                                                    |
-| `NOT IN` subquery on nullable columns                   | Use `NOT EXISTS` with a correlated subquery instead                                               |
+| Pattern                               | Alternative                                                                                       |
+| :------------------------------------ | :------------------------------------------------------------------------------------------------ |
+| `func(DISTINCT ...)` on any aggregate | Use `approx_distinct` for counting                                                                |
+| `PERCENTILE_CONT` / `PERCENTILE_DISC` | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
+| `MEDIAN`                              | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
+| `ARRAY_AGG`                           | No alternative (unsupported for memory safety)                                                    |
+| `STRING_AGG`                          | No alternative (unsupported for memory safety)                                                    |
+| `NOT IN` subquery on nullable columns | Use `NOT EXISTS` with a correlated subquery instead                                               |
 
 ---
 
 ## Runtime constraints
 
-| Constraint                           | Details                                                                                               |
-| :----------------------------------- | :---------------------------------------------------------------------------------------------------- |
+| Constraint                           | Details                                                                                                                                                                                    |
+| :----------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Multi-table queries                  | JOINs, subqueries (IN, EXISTS, scalar, derived tables), and multi-table CTEs are supported. Performance depends on intermediate result size; use WHERE filters to manage join selectivity. |
-| Partitioned and unpartitioned tables  | Both partitioned and unpartitioned Iceberg tables are supported.                                       |
-| Parquet format only                  | No CSV, JSON, or other formats.                                                                       |
-| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                  |
-| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                       |
+| Partitioned and unpartitioned tables | Both partitioned and unpartitioned Iceberg tables are supported.                                                                                                                           |
+| Parquet format only                  | No CSV, JSON, or other formats.                                                                                                                                                            |
+| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                                                                                                       |
+| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                                                                                                            |
 
 ---
 
diff --git a/src/content/docs/r2-sql/reference/wrangler-commands.mdx b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
index 26a591c683434f5..f9765698d06f77d 100644
--- a/src/content/docs/r2-sql/reference/wrangler-commands.mdx
+++ b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { Render, Type, MetaInfo } from "~/components";
 
-<Render file="wrangler-commands/r2-sql" product="workers" />
\ No newline at end of file
+<Render file="wrangler-commands/r2-sql" product="workers" />
diff --git a/src/content/docs/r2-sql/sql-reference/index.mdx b/src/content/docs/r2-sql/sql-reference/index.mdx
index 70227b97d4db20a..58ed3641062a224 100644
--- a/src/content/docs/r2-sql/sql-reference/index.mdx
+++ b/src/content/docs/r2-sql/sql-reference/index.mdx
@@ -194,14 +194,14 @@ R2 SQL supports joining multiple Iceberg tables in a single query. All join type
 
 ### Supported join types
 
-| Join type        | Syntax                              | Description                                                        |
-| :--------------- | :---------------------------------- | :----------------------------------------------------------------- |
-| Inner join       | `INNER JOIN ... ON`                 | Returns rows that match in both tables                             |
-| Left outer join  | `LEFT JOIN ... ON`                  | Returns all rows from the left table, NULLs for non-matching right |
-| Right outer join | `RIGHT JOIN ... ON`                 | Returns all rows from the right table, NULLs for non-matching left |
-| Full outer join  | `FULL OUTER JOIN ... ON`            | Returns all rows from both tables, NULLs where no match            |
-| Cross join       | `CROSS JOIN`                        | Cartesian product of both tables                                   |
-| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id`  | Comma-separated tables with join condition in `WHERE`              |
+| Join type        | Syntax                            | Description                                                        |
+| :--------------- | :-------------------------------- | :----------------------------------------------------------------- |
+| Inner join       | `INNER JOIN ... ON`               | Returns rows that match in both tables                             |
+| Left outer join  | `LEFT JOIN ... ON`                | Returns all rows from the left table, NULLs for non-matching right |
+| Right outer join | `RIGHT JOIN ... ON`               | Returns all rows from the right table, NULLs for non-matching left |
+| Full outer join  | `FULL OUTER JOIN ... ON`          | Returns all rows from both tables, NULLs where no match            |
+| Cross join       | `CROSS JOIN`                      | Cartesian product of both tables                                   |
+| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id` | Comma-separated tables with join condition in `WHERE`              |
 
 ### Syntax
 
@@ -264,6 +264,7 @@ SELECT * FROM (t1 JOIN t2 ON t1.id = t2.id) JOIN t3 ON t2.id = t3.id
 -- Supported
 SELECT * FROM t1 JOIN t2 ON t1.id = t2.id JOIN t3 ON t2.id = t3.id
 ```
+
 :::
 
 ### Best practices for joins
@@ -358,6 +359,7 @@ WHERE NOT EXISTS (
 )
 LIMIT 20
 ```
+
 :::
 
 ### `EXISTS` / `NOT EXISTS` subqueries
diff --git a/src/content/docs/r2/api/error-codes.mdx b/src/content/docs/r2/api/error-codes.mdx
index 49ec6f7e7bff0ec..27e9cbdf09979fb 100644
--- a/src/content/docs/r2/api/error-codes.mdx
+++ b/src/content/docs/r2/api/error-codes.mdx
@@ -16,10 +16,10 @@ For the **Workers API**, R2 operations throw exceptions that you can catch. The
 
 ```js
 try {
-  await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
+	await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
 } catch (error) {
-  console.error(error.message);
-  // "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
+	console.error(error.message);
+	// "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
 }
 ```
 
@@ -37,59 +37,59 @@ For the **S3-compatible API**, errors are returned as XML in the response body:
 
 ### Authentication and authorization errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10002 | Unauthorized | 401 | Missing or invalid authentication credentials. | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired. |
-| 10003 | AccessDenied | 403 | Insufficient permissions for the requested operation. | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
-| 10018 | ExpiredRequest | 400 | Presigned URL or request signature has expired. | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature. |
-| 10035 | SignatureDoesNotMatch | 403 | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues. |
-| 10042 | NotEntitled | 403 | Account not entitled to this feature. | Ensure your account has an [R2 subscription](/r2/pricing/). |
+| Error Code | S3 Code               | HTTP Status | Details                                                | Recommended Fix                                                                                         |
+| ---------- | --------------------- | ----------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
+| 10002      | Unauthorized          | 401         | Missing or invalid authentication credentials.         | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired.    |
+| 10003      | AccessDenied          | 403         | Insufficient permissions for the requested operation.  | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
+| 10018      | ExpiredRequest        | 400         | Presigned URL or request signature has expired.        | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature.                                |
+| 10035      | SignatureDoesNotMatch | 403         | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues.                            |
+| 10042      | NotEntitled           | 403         | Account not entitled to this feature.                  | Ensure your account has an [R2 subscription](/r2/pricing/).                                             |
 
 ### Bucket errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10005 | InvalidBucketName | 400 | Bucket name does not meet naming requirements. | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric. |
-| 10006 | NoSuchBucket | 404 | The specified bucket does not exist. | Verify the bucket name is correct and the bucket exists in your account. |
-| 10008 | BucketNotEmpty | 409 | Cannot delete bucket that contains objects. | Delete all objects in the bucket before deleting the bucket. |
-| 10009 | TooManyBuckets | 400 | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
-| 10073 | BucketConflict | 409 | Bucket name already exists. | Choose a different bucket name. Bucket names must be unique within your account. |
+| Error Code | S3 Code           | HTTP Status | Details                                                     | Recommended Fix                                                                                       |
+| ---------- | ----------------- | ----------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| 10005      | InvalidBucketName | 400         | Bucket name does not meet naming requirements.              | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric.     |
+| 10006      | NoSuchBucket      | 404         | The specified bucket does not exist.                        | Verify the bucket name is correct and the bucket exists in your account.                              |
+| 10008      | BucketNotEmpty    | 409         | Cannot delete bucket that contains objects.                 | Delete all objects in the bucket before deleting the bucket.                                          |
+| 10009      | TooManyBuckets    | 400         | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
+| 10073      | BucketConflict    | 409         | Bucket name already exists.                                 | Choose a different bucket name. Bucket names must be unique within your account.                      |
 
 ### Object errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10007 | NoSuchKey | 404 | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted. |
-| 10020 | InvalidObjectName | 400 | Object key contains invalid characters or is too long. | Use valid UTF-8 characters. Maximum key length is 1024 bytes. |
-| 100100 | EntityTooLarge | 400 | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart). | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
-| 10012 | MetadataTooLarge | 400 | Custom metadata exceeds the 8,192 byte limit. | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata. |
-| 10069 | ObjectLockedByBucketPolicy | 403 | Object is protected by a bucket lock rule and cannot be modified or deleted. | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/). |
+| Error Code | S3 Code                    | HTTP Status | Details                                                                                                                                                         | Recommended Fix                                                                                                                   |
+| ---------- | -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| 10007      | NoSuchKey                  | 404         | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted.                                                             |
+| 10020      | InvalidObjectName          | 400         | Object key contains invalid characters or is too long.                                                                                                          | Use valid UTF-8 characters. Maximum key length is 1024 bytes.                                                                     |
+| 100100     | EntityTooLarge             | 400         | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart).                                                                                     | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
+| 10012      | MetadataTooLarge           | 400         | Custom metadata exceeds the 8,192 byte limit.                                                                                                                   | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata.                                                |
+| 10069      | ObjectLockedByBucketPolicy | 403         | Object is protected by a bucket lock rule and cannot be modified or deleted.                                                                                    | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/).                                      |
 
 ### Upload and request errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10033 | MissingContentLength | 411 | `Content-Length` header required but missing. | Include the `Content-Length` header in PUT/POST requests. |
-| 10013 | IncompleteBody | 400 | Request body terminated before expected `Content-Length`. | Ensure the full request body is sent. Check for network interruptions or client timeouts. |
-| 10014 | InvalidDigest | 400 | Checksum header format is malformed. | Ensure checksums are properly encoded (base64 for SHA/CRC checksums). |
-| 10037 | BadDigest | 400 | Provided checksum does not match the uploaded content. | Verify data integrity and retry the upload. |
-| 10039 | InvalidRange | 416 | Requested byte range is not satisfiable. | Ensure the range start is less than object size. Check `Range` header format. |
-| 10031 | PreconditionFailed | 412 | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
+| Error Code | S3 Code              | HTTP Status | Details                                                                           | Recommended Fix                                                                                                                                                                     |
+| ---------- | -------------------- | ----------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10033      | MissingContentLength | 411         | `Content-Length` header required but missing.                                     | Include the `Content-Length` header in PUT/POST requests.                                                                                                                           |
+| 10013      | IncompleteBody       | 400         | Request body terminated before expected `Content-Length`.                         | Ensure the full request body is sent. Check for network interruptions or client timeouts.                                                                                           |
+| 10014      | InvalidDigest        | 400         | Checksum header format is malformed.                                              | Ensure checksums are properly encoded (base64 for SHA/CRC checksums).                                                                                                               |
+| 10037      | BadDigest            | 400         | Provided checksum does not match the uploaded content.                            | Verify data integrity and retry the upload.                                                                                                                                         |
+| 10039      | InvalidRange         | 416         | Requested byte range is not satisfiable.                                          | Ensure the range start is less than object size. Check `Range` header format.                                                                                                       |
+| 10031      | PreconditionFailed   | 412         | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
 
 ### Multipart upload errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10011 | EntityTooSmall | 400 | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB. |
-| 10024 | NoSuchUpload | 404 | Multipart upload does not exist or was aborted. | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
-| 10025 | InvalidPart | 400 | One or more parts could not be found when completing the upload. | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`. |
-| 10048 | InvalidPart | 400 | All non-trailing parts must have the same size. | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads. |
+| Error Code | S3 Code        | HTTP Status | Details                                                                 | Recommended Fix                                                                                                                                               |
+| ---------- | -------------- | ----------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10011      | EntityTooSmall | 400         | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB.                                                                                                         |
+| 10024      | NoSuchUpload   | 404         | Multipart upload does not exist or was aborted.                         | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
+| 10025      | InvalidPart    | 400         | One or more parts could not be found when completing the upload.        | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`.                                                                 |
+| 10048      | InvalidPart    | 400         | All non-trailing parts must have the same size.                         | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads.                                                  |
 
 ### Service errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10001 | InternalError | 500 | An internal error occurred. | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
-| 10043 | ServiceUnavailable | 503 | Service is temporarily unavailable. | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com). |
-| 10054 | ClientDisconnect | 400 | Client disconnected before request completed. | Check network connectivity and retry. |
-| 10058 | TooManyRequests | 429 | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/). |
+| Error Code | S3 Code            | HTTP Status | Details                                                                                                                   | Recommended Fix                                                                                                   |
+| ---------- | ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| 10001      | InternalError      | 500         | An internal error occurred.                                                                                               | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
+| 10043      | ServiceUnavailable | 503         | Service is temporarily unavailable.                                                                                       | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com).                      |
+| 10054      | ClientDisconnect   | 400         | Client disconnected before request completed.                                                                             | Check network connectivity and retry.                                                                             |
+| 10058      | TooManyRequests    | 429         | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/).               |
diff --git a/src/content/docs/r2/api/index.mdx b/src/content/docs/r2/api/index.mdx
index ea9d2d32f1163c9..c7113b1969a8c64 100644
--- a/src/content/docs/r2/api/index.mdx
+++ b/src/content/docs/r2/api/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 R2 provides three API surfaces for interacting with your data:
 
diff --git a/src/content/docs/r2/api/s3/extensions.mdx b/src/content/docs/r2/api/s3/extensions.mdx
index 79016396a6a9091..3d837887f7d5b66 100644
--- a/src/content/docs/r2/api/s3/extensions.mdx
+++ b/src/content/docs/r2/api/s3/extensions.mdx
@@ -16,13 +16,11 @@ HTTP header names and values may only contain ASCII characters, which is a small
 
 :::caution[Metadata variance]
 
-Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted. 
+Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted.
 :::
 
 These headers map to the `httpMetadata` field in the [R2 bindings](/workers/runtime-apis/bindings/):
 
-
-
 | HTTP Header           | Property Name                     |
 | --------------------- | --------------------------------- |
 | `Content-Encoding`    | `httpMetadata.contentEncoding`    |
@@ -73,8 +71,6 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 `ListBuckets` supports all the same search parameters as `ListObjectsV2` in R2 because some customers may have more than 1,000 buckets. Because tooling, like existing S3 libraries, may not expose a way to set these search parameters, these values may also be sent in via headers. Values in headers take precedence over the search parameters.
 
-
-
 | Search parameter     | HTTP Header             | Meaning                                                           |
 | -------------------- | ----------------------- | ----------------------------------------------------------------- |
 | `prefix`             | `cf-prefix`             | Show buckets with this prefix only.                               |
@@ -85,8 +81,6 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 The XML response contains a `NextContinuationToken` and `IsTruncated` elements as appropriate. Since these may not be accessible from existing S3 APIs, these are also available in response headers:
 
-
-
 | XML Response Element    | HTTP Response Header         | Meaning                                                                                        |
 | ----------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------- |
 | `IsTruncated`           | `cf-is-truncated`            | This is set to `true` if the list of buckets returned is not all the buckets on the account.   |
@@ -101,15 +95,15 @@ The XML response contains a `NextContinuationToken` and `IsTruncated` elements a
 
 :::note
 
-This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81). 
+This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81).
 :::
 
 `CopyObject` already supports conditions that relate to the source object through the `x-amz-copy-source-if-...` headers as part of our compliance with the S3 API. In addition to this, R2 supports an R2 specific set of headers that allow the `CopyObject` operation to be conditional on the target object:
 
-* `cf-copy-destination-if-match`
-* `cf-copy-destination-if-none-match`
-* `cf-copy-destination-if-modified-since`
-* `cf-copy-destination-if-unmodified-since`
+- `cf-copy-destination-if-match`
+- `cf-copy-destination-if-none-match`
+- `cf-copy-destination-if-modified-since`
+- `cf-copy-destination-if-unmodified-since`
 
 These headers work akin to the similarly named conditional headers supported on `PutObject`. When the preceding state of the destination object to does not match the specified conditions the `CopyObject` operation will be rejected with a `412 PreconditionFailed` error code.
 
diff --git a/src/content/docs/r2/api/s3/presigned-urls.mdx b/src/content/docs/r2/api/s3/presigned-urls.mdx
index 4b4c1fc51449c91..bda593cdc55a82e 100644
--- a/src/content/docs/r2/api/s3/presigned-urls.mdx
+++ b/src/content/docs/r2/api/s3/presigned-urls.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import {Tabs, TabItem, LinkCard } from "~/components";
+import { Tabs, TabItem, LinkCard } from "~/components";
 
 Presigned URLs are an [S3 concept](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) for granting temporary access to objects without exposing your API credentials. A presigned URL includes signature parameters in the URL itself, authorizing anyone with the URL to perform a specific operation (like `GetObject` or `PutObject`) on a specific object until the URL expires.
 
@@ -24,10 +24,10 @@ Presigned URLs are generated client-side with no communication with R2, requirin
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern | Grants | Good for |
-| --- | --- | --- |
-| Presigned URLs (this page) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
-| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
+| Pattern                                                    | Grants                                                                                                         | Good for                                                                                                                   |
+| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Presigned URLs (this page)                                 | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
 
 ## Generate a presigned URL
 
@@ -136,6 +136,7 @@ aws s3 presign --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com \
 </Tabs>
 
 For complete examples and additional operations, refer to the SDK-specific documentation:
+
 - [AWS SDK for JavaScript](/r2/examples/aws/aws-sdk-js-v3/#generate-presigned-urls)
 - [AWS SDK for Python (Boto3)](/r2/examples/aws/boto3/#generate-presigned-urls)
 - [AWS CLI](/r2/examples/aws/aws-cli/#generate-presigned-urls)
diff --git a/src/content/docs/r2/api/s3/temporary-credentials.mdx b/src/content/docs/r2/api/s3/temporary-credentials.mdx
index eabe88c5d475d9f..42a48a5428e8ec4 100644
--- a/src/content/docs/r2/api/s3/temporary-credentials.mdx
+++ b/src/content/docs/r2/api/s3/temporary-credentials.mdx
@@ -16,10 +16,10 @@ Use temporary credentials to delegate access without issuing a long-lived token.
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern | Grants | Good for |
-| --- | --- | --- |
-| Temporary credentials (this page) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
-| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| Pattern                                      | Grants                                                                                                         | Good for                                                                                                                   |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Temporary credentials (this page)            | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
+| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
 
 ## Generate temporary credentials
 
@@ -108,11 +108,11 @@ For example, `actions: ["GetObject", "HeadObject"]` grants read of individual ob
 
 Valid actions:
 
-| Category | Actions |
-| --- | --- |
-| Read | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
-| Write | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject` |
-| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload` |
+| Category  | Actions                                                                                                               |
+| --------- | --------------------------------------------------------------------------------------------------------------------- |
+| Read      | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
+| Write     | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject`                                                            |
+| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload`            |
 
 ### Paths
 
@@ -122,8 +122,8 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-  "prefixes": ["uploads/user-123/"],
-  "objects": ["shared/manifest.json"]
+	"prefixes": ["uploads/user-123/"],
+	"objects": ["shared/manifest.json"],
 }
 ```
 
@@ -131,10 +131,10 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-  "paths": {
-    "prefixPaths": ["uploads/user-123/"],
-    "objectPaths": ["shared/manifest.json"]
-  }
+	"paths": {
+		"prefixPaths": ["uploads/user-123/"],
+		"objectPaths": ["shared/manifest.json"],
+	},
 }
 ```
 
@@ -205,25 +205,25 @@ Treat temporary credentials as bearer tokens. Anyone in possession of all three
 ## Related resources
 
 <LinkCard
-  title="Authenticate against R2 with temporary credentials"
-  href="/r2/examples/authenticate-r2-temp-credentials/"
-  description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
+	title="Authenticate against R2 with temporary credentials"
+	href="/r2/examples/authenticate-r2-temp-credentials/"
+	description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
 />
 
 <LinkCard
-  title="Presigned URLs"
-  href="/r2/api/s3/presigned-urls/"
-  description="Grant single-operation access to a specific object without issuing credentials."
+	title="Presigned URLs"
+	href="/r2/api/s3/presigned-urls/"
+	description="Grant single-operation access to a specific object without issuing credentials."
 />
 
 <LinkCard
-  title="R2 API tokens"
-  href="/r2/api/tokens/"
-  description="Create the parent token that temporary credentials derive from."
+	title="R2 API tokens"
+	href="/r2/api/tokens/"
+	description="Create the parent token that temporary credentials derive from."
 />
 
 <LinkCard
-  title="Error codes"
-  href="/r2/api/error-codes/"
-  description="Authentication and authorization error codes returned by R2."
+	title="Error codes"
+	href="/r2/api/error-codes/"
+	description="Authentication and authorization error codes returned by R2."
 />
diff --git a/src/content/docs/r2/api/workers/workers-api-reference.mdx b/src/content/docs/r2/api/workers/workers-api-reference.mdx
index b7489165a08ccee..d60ffa3b2d79709 100644
--- a/src/content/docs/r2/api/workers/workers-api-reference.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-reference.mdx
@@ -103,40 +103,33 @@ class Default(WorkerEntrypoint):
 </Tabs>
 
 - `head` <Type text="(key: string): Promise<R2Object | null>" />
-
   - Retrieves the `R2Object` for the given key containing only object metadata, if the key exists, and `null` if the key does not exist.
 
 - `get` <Type text="(key: string, options?: R2GetOptions): Promise<R2ObjectBody | R2Object | null>" />
-
   - Retrieves the `R2ObjectBody` for the given key containing object metadata and the object body as a <code>ReadableStream</code>, if the key exists, and `null` if the key does not exist.
   - In the event that a precondition specified in <code>options</code> fails, <code>get()</code> returns an <code>R2Object</code> with <code>body</code> undefined.
 
 - `put` <Type text="(key: string, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | null | Blob, options?: R2PutOptions): Promise<R2Object | null>" />
-
   - Stores the given <code>value</code> and metadata under the associated <code>key</code>. Once the write succeeds, returns an `R2Object` containing metadata about the stored Object.
   - In the event that a precondition specified in <code>options</code> fails, <code>put()</code> returns `null`, and the object will not be stored.
   - R2 writes are strongly consistent. Once the Promise resolves, all subsequent read operations will see this key value pair globally.
 
 - `delete` <Type text="(key: string | string[]): Promise<void>" />
-
   - Deletes the given <code>values</code> and metadata under the associated <code>keys</code>. Once the delete succeeds, returns <code>void</code>.
   - R2 deletes are strongly consistent. Once the Promise resolves, all subsequent read operations will no longer see the provided key value pairs globally.
   - Up to 1000 keys may be deleted per call.
 
 - `list` <Type text="(options?: R2ListOptions): Promise<R2Objects>" />
-
-  * Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
-  * The returned list of objects is ordered lexicographically.
-  * Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
-  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
+  - Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
+  - The returned list of objects is ordered lexicographically.
+  - Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
+  - To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
 
 * `createMultipartUpload` <Type text="(key: string, options?: R2MultipartOptions): Promise<R2MultipartUpload>" />
-
   - Creates a multipart upload.
   - Returns Promise which resolves to an `R2MultipartUpload` object representing the newly created multipart upload. Once the multipart upload has been created, the multipart upload can be immediately interacted with globally, either through the Workers API, or through the S3 API.
 
 - `resumeMultipartUpload` <Type text="(key: string, uploadId: string): R2MultipartUpload" />
-
   - Returns an object representing a multipart upload with the given key and uploadId.
   - The resumeMultipartUpload operation does not perform any checks to ensure the validity of the uploadId, nor does it verify the existence of a corresponding active multipart upload. This is done to minimize latency before being able to call subsequent operations on the `R2MultipartUpload` object.
 
@@ -145,15 +138,12 @@ class Default(WorkerEntrypoint):
 `R2Object` is created when you `PUT` an object into an R2 bucket. `R2Object` represents the metadata of an object based on the information provided by the uploader. Every object that you `PUT` into an R2 bucket will have an `R2Object` created.
 
 - `key` <Type text="string" />
-
   - The object's key.
 
 - `version` <Type text="string" />
-
   - Random unique string associated with a specific upload of a key.
 
 - `size` <Type text="number" />
-
   - Size of the object in bytes.
 
 - `etag` <Type text="string" />
@@ -166,39 +156,30 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 - The etag associated with the object upload.
 
 - `httpEtag` <Type text="string" />
-
   - The object's etag, in quotes so as to be returned as a header.
 
 - `uploaded` <Type text="Date" />
-
   - A Date object representing the time the object was uploaded.
 
 - `httpMetadata` <Type text="R2HTTPMetadata" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" />
-
   - A map of custom, user-defined metadata associated with the object.
 
 - `range` <Type text="R2Range" />
-
   - A `R2Range` object containing the returned range of the object.
 
 - `checksums` <Type text="R2Checksums" />
-
   - A `R2Checksums` object containing the stored checksums of the object. Refer to [checksums](#checksums).
 
 - `writeHttpMetadata` <Type text="(headers: Headers): void" />
-
   - Retrieves the `httpMetadata` from the `R2Object` and applies their corresponding HTTP headers to the `Headers` input object. Refer to [HTTP Metadata](#http-metadata).
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
-
   - The storage class associated with the object. Refer to [Storage Classes](#storage-class).
 
 - `ssecKeyMd5` <Type text="string" />
-
   - Hex-encoded MD5 hash of the [SSE-C](/r2/examples/ssec) key used for encryption (if one was provided). Hash can be used to identify which key is needed to decrypt object.
 
 ## `R2ObjectBody` definition
@@ -206,27 +187,21 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 `R2ObjectBody` represents an object's metadata combined with its body. It is returned when you `GET` an object from an R2 bucket. The full list of keys for `R2ObjectBody` includes the list below and all keys inherited from [`R2Object`](#r2object-definition).
 
 - `body` <Type text="ReadableStream" />
-
   - The object's value.
 
 - `bodyUsed` <Type text="boolean" />
-
   - Whether the object's value has been consumed or not.
 
 - `arrayBuffer` <Type text="(): Promise<ArrayBuffer>" />
-
   - Returns a Promise that resolves to an `ArrayBuffer` containing the object's value.
 
 - `text` <Type text="(): Promise<string>" />
-
   - Returns a Promise that resolves to an string containing the object's value.
 
 - `json` <Type text="<T>() : Promise<T>" />
-
   - Returns a Promise that resolves to the given object containing the object's value.
 
 - `blob` <Type text="(): Promise<Blob>" />
-
   - Returns a Promise that resolves to a binary Blob containing the object's value.
 
 ## `R2MultipartUpload` definition
@@ -244,24 +219,19 @@ A multipart upload can be completed or aborted at any time, either through the S
 :::
 
 - `key` <Type text="string" />
-
   - The `key` for the multipart upload.
 
 - `uploadId` <Type text="string" />
-
   - The `uploadId` for the multipart upload.
 
 - `uploadPart` <Type text="(partNumber: number, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | Blob, options?: R2MultipartOptions): Promise<R2UploadedPart>" />
-
   - Uploads a single part with the specified part number to this multipart upload. Each part must be uniform in size with an exception for the final part which can be smaller.
   - Returns an `R2UploadedPart` object containing the `etag` and `partNumber`. These `R2UploadedPart` objects are required when completing the multipart upload.
 
 - `abort` <Type text="(): Promise<void>" />
-
   - Aborts the multipart upload. Returns a Promise that resolves when the upload has been successfully aborted.
 
 - `complete` <Type text="(uploadedParts: R2UploadedPart[]): Promise<R2Object>" />
-
   - Completes the multipart upload with the given parts.
   - Returns a Promise that resolves when the complete operation has finished. Once this happens, the object is immediately accessible globally by any subsequent read operation.
 
@@ -270,15 +240,12 @@ A multipart upload can be completed or aborted at any time, either through the S
 ### R2GetOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
-
   - Specifies that the object should only be returned given satisfaction of certain conditions in the `R2Conditional` or in the conditional Headers. Refer to [Conditional operations](#conditional-operations).
 
 - `range` <Type text="R2Range" />
-
   - Specifies that only a specific length (from an optional offset) or suffix of bytes from the object should be returned. Refer to [Ranged reads](#ranged-reads).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 #### Ranged reads
@@ -292,29 +259,23 @@ There are 3 variations of arguments that can be used in a range:
 - A suffix.
 
 - `offset` <Type text="number" />
-
   - The byte to begin returning data from, inclusive.
 
 - `length` <Type text="number" />
-
   - The number of bytes to return. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 - `suffix` <Type text="number" />
-
   - The number of bytes to return from the end of the file, starting from the last byte. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 ### R2PutOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
-
   - Specifies that the object should only be stored given satisfaction of certain conditions in the `R2Conditional`. Refer to [Conditional operations](#conditional-operations).
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
-
   - A map of custom, user-defined metadata that will be stored with the object.
 
 :::note
@@ -324,73 +285,57 @@ Only a single hashing algorithm can be specified at once.
 :::
 
 - `md5` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A md5 hash to use to check the received object's integrity.
 
 - `sha1` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-1 hash to use to check the received object's integrity.
 
 - `sha256` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-256 hash to use to check the received object's integrity.
 
 - `sha384` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-384 hash to use to check the received object's integrity.
 
 - `sha512` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-512 hash to use to check the received object's integrity.
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
-
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2MultipartOptions
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
-
   - A map of custom, user-defined metadata that will be stored with the object.
 
 - `storageClass` <Type text="string" />
-
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2ListOptions
 
 - `limit` <Type text="number" /> <MetaInfo text="optional" />
-
   - The number of results to return. Defaults to `1000`, with a maximum of `1000`.
 
   - If `include` is set, you may receive fewer than `limit` results in your response to accommodate metadata.
 
 - `prefix` <Type text="string" /> <MetaInfo text="optional" />
-
   - The prefix to match keys against. Keys will only be returned if they start with given prefix.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
-
   - An opaque token that indicates where to continue listing objects from. A cursor can be retrieved from a previous list operation.
 
 - `delimiter` <Type text="string" /> <MetaInfo text="optional" />
-
   - The character to use when grouping keys.
 
 - `include` <Type text="Array<string>" /> <MetaInfo text="optional" />
-
   - Can include `httpMetadata` and/or `customMetadata`. If included, items returned by the list will include the specified metadata.
 
   - Note that there is a limit on the total amount of data that a single `list` operation can return. If you request data, you may receive fewer than `limit` results in your response to accommodate metadata.
@@ -435,19 +380,15 @@ while (truncated) {
 An object containing an `R2Object` array, returned by `BUCKET_BINDING.list()`.
 
 - `objects` <Type text="Array<R2Object>" />
-
   - An array of objects matching the `list` request.
 
 - `truncated` boolean
-
   - If true, indicates there are more results to be retrieved for the current `list` request.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
-
   - A token that can be passed to future `list` calls to resume listing from that point. Only present if truncated is true.
 
 - `delimitedPrefixes` <Type text="Array<string>" />
-
   - If a delimiter has been specified, contains all prefixes between the specified prefix and the next occurrence of the delimiter.
 
   - For example, if no prefix is provided and the delimiter is '/', `foo/bar/baz` would return `foo` as a delimited prefix. If `foo/` was passed as a prefix with the same structure and delimiter, `foo/bar` would be returned as a delimited prefix.
@@ -459,19 +400,15 @@ You can pass an `R2Conditional` object to `R2GetOptions` and `R2PutOptions`. If
 If the condition check for `put()` fails, `null` will be returned instead of the `R2Object`.
 
 - `etagMatches` <Type text="string" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object's etag matches the given string.
 
 - `etagDoesNotMatch` <Type text="string" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object's etag does not match the given string.
 
 - `uploadedBefore` <Type text="Date" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object was uploaded before the given date.
 
 - `uploadedAfter` <Type text="Date" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object was uploaded after the given date.
 
 Alternatively, you can pass a `Headers` object containing conditional headers to `R2GetOptions` and `R2PutOptions`. For information on these conditional headers, refer to [the MDN docs on conditional requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditional_requests#conditional_headers). All conditional headers aside from `If-Range` are supported.
@@ -499,23 +436,18 @@ Generally, these fields match the HTTP metadata passed when the object was creat
 If a checksum was provided when using the `put()` binding, it will be available on the returned object under the `checksums` property. The MD5 checksum will be included by default for non-multipart objects.
 
 - `md5` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The MD5 checksum of the object.
 
 - `sha1` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-1 checksum of the object.
 
 - `sha256` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-256 checksum of the object.
 
 - `sha384` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-384 checksum of the object.
 
 - `sha512` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-512 checksum of the object.
 
 ### `R2UploadedPart`
@@ -523,11 +455,9 @@ If a checksum was provided when using the `put()` binding, it will be available
 An `R2UploadedPart` object represents a part that has been uploaded. `R2UploadedPart` objects are returned from `uploadPart` operations and must be passed to `completeMultipartUpload` operations.
 
 - `partNumber` <Type text="number" />
-
   - The number of the part.
 
 - `etag` <Type text="string" />
-
   - The `etag` of the part.
 
 ### Storage Class
diff --git a/src/content/docs/r2/api/workers/workers-api-usage.mdx b/src/content/docs/r2/api/workers/workers-api-usage.mdx
index 6cfb3742ecf0dbe..3201040184b441e 100644
--- a/src/content/docs/r2/api/workers/workers-api-usage.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-usage.mdx
@@ -251,6 +251,7 @@ class Default(WorkerEntrypoint):
 ```
 </TabItem>
 </Tabs>
+
 <Render file="request-dot-clone-warning" product="workers" />
 
 ## 5. Bucket access and privacy
diff --git a/src/content/docs/r2/buckets/bucket-locks.mdx b/src/content/docs/r2/buckets/bucket-locks.mdx
index 464a1623fef1b18..d7bcec562a81685 100644
--- a/src/content/docs/r2/buckets/bucket-locks.mdx
+++ b/src/content/docs/r2/buckets/bucket-locks.mdx
@@ -22,6 +22,7 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Select **Add rule** and enter the rule name, prefix, and retention period.
@@ -97,6 +98,7 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 
@@ -119,6 +121,7 @@ For more information on required parameters and examples of how to get bucket lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Locate the rule you want to remove, select the `...` icon next to it, and then select **Delete**.
diff --git a/src/content/docs/r2/buckets/cors.mdx b/src/content/docs/r2/buckets/cors.mdx
index 509574538198e4b..e377d4c3587d41b 100644
--- a/src/content/docs/r2/buckets/cors.mdx
+++ b/src/content/docs/r2/buckets/cors.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) is a standardized method that prevents domain X from accessing the resources of domain Y. It does so by using special headers in HTTP responses from domain Y, that allow your browser to verify that domain Y permits domain X to access these resources.
 
@@ -56,13 +56,13 @@ The following example allows browser-based uploads from `https://example.com` wi
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -83,6 +83,7 @@ If you set a CORS policy on a bucket that is already serving traffic using a cus
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. Select **Settings**.
 4. Under **CORS Policy**, select **Add CORS policy**.
@@ -99,14 +100,14 @@ You can configure CORS rules using the [Wrangler CLI](/r2/reference/wrangler-com
 
 ```json title="cors.json"
 {
-  "rules": [
-    {
-      "allowed": {
-        "origins": ["https://example.com"],
-        "methods": ["GET"]
-      }
-    }
-  ]
+	"rules": [
+		{
+			"allowed": {
+				"origins": ["https://example.com"],
+				"methods": ["GET"]
+			}
+		}
+	]
 }
 ```
 
@@ -126,13 +127,13 @@ npx wrangler r2 bucket cors list <BUCKET_NAME>
 
 The following fields in an R2 CORS policy map to HTTP response headers. These response headers are only returned when the incoming HTTP request is a valid CORS request.
 
-| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                           | Example                                                                                                                                                                                                                              |
-| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                          | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
-| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                         | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
-| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
+| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                                     | Example                                                                                                                                                                                                                              |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                    | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
+| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                   | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
+| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                          | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
 | `ExposeHeaders`  | Specifies the headers that can be exposed back, and accessed by, the JavaScript making the cross-origin request. If you need to access headers beyond the [safelisted response headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers#examples), such as `Content-Encoding` or `cf-cache-status`, you must specify it here. | `Content-Encoding`, `cf-cache-status`, `Date`                                                                                                                                                                                        |
-| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                         | `3600`                                                                                                                                                                                                                               |
+| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                                   | `3600`                                                                                                                                                                                                                               |
 
 ## Example
 
diff --git a/src/content/docs/r2/buckets/delete-buckets.mdx b/src/content/docs/r2/buckets/delete-buckets.mdx
index cae21c981e67944..71cdbc593f9c6e8 100644
--- a/src/content/docs/r2/buckets/delete-buckets.mdx
+++ b/src/content/docs/r2/buckets/delete-buckets.mdx
@@ -27,6 +27,7 @@ The dashboard provides an **Empty Bucket** action that handles this for you, reg
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you want to empty.
 3. Go to the **Settings** tab.
 4. Scroll to the **Empty Bucket** section.
@@ -86,6 +87,7 @@ You can delete a bucket in various ways.
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you want to delete.
 3. Go to the **Settings** tab.
 4. Scroll to the **Delete Bucket** section. If the bucket is not empty, select **Empty Bucket** first to clear all objects.
@@ -129,25 +131,25 @@ curl -X DELETE "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/r2/bu
 ## Related resources
 
 <LinkCard
-  title="Delete objects"
-  href="/r2/objects/delete-objects/"
-  description="Delete individual objects or folders from an R2 bucket."
+	title="Delete objects"
+	href="/r2/objects/delete-objects/"
+	description="Delete individual objects or folders from an R2 bucket."
 />
 
 <LinkCard
-  title="Bucket locks"
-  href="/r2/buckets/bucket-locks/"
-  description="Prevent accidental deletion by setting retention policies on objects."
+	title="Bucket locks"
+	href="/r2/buckets/bucket-locks/"
+	description="Prevent accidental deletion by setting retention policies on objects."
 />
 
 <LinkCard
-  title="Object lifecycles"
-  href="/r2/buckets/object-lifecycles/"
-  description="Automatically expire objects after a specified period instead of emptying manually."
+	title="Object lifecycles"
+	href="/r2/buckets/object-lifecycles/"
+	description="Automatically expire objects after a specified period instead of emptying manually."
 />
 
 <LinkCard
-  title="Create buckets"
-  href="/r2/buckets/create-buckets/"
-  description="Create a new R2 bucket after deleting an existing one."
+	title="Create buckets"
+	href="/r2/buckets/create-buckets/"
+	description="Create a new R2 bucket after deleting an existing one."
 />
diff --git a/src/content/docs/r2/buckets/event-notifications.mdx b/src/content/docs/r2/buckets/event-notifications.mdx
index b0fe30eb775ad6f..e910f9b896e6223 100644
--- a/src/content/docs/r2/buckets/event-notifications.mdx
+++ b/src/content/docs/r2/buckets/event-notifications.mdx
@@ -26,6 +26,7 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you'd like to add an event notification rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Event notifications** card.
 4. Select **Add notification** and choose the queue you'd like to receive notifications and the [type of events](/r2/buckets/event-notifications/#event-types) that will trigger them.
@@ -66,10 +67,10 @@ Event notification rules determine the [event types](/r2/buckets/event-notificat
 
 ## Event types
 
-| Event type | Description | Trigger actions |
-|------------|-------------|----------------|
+| Event type      | Description                                                                 | Trigger actions                                                                      |
+| --------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
 | `object-create` | Triggered when new objects are created or existing objects are overwritten. | <ul><li>`PutObject`</li><li>`CopyObject`</li><li>`CompleteMultipartUpload`</li></ul> |
-| `object-delete` | Triggered when an object is explicitly removed from the bucket. | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul> |
+| `object-delete` | Triggered when an object is explicitly removed from the bucket.             | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul>                         |
 
 ## Message format
 
@@ -95,19 +96,19 @@ Queue consumers receive notifications as [Messages](/queues/configuration/javasc
 
 ### Properties
 
-| Property | Type | Description |
-|----------|------|-------------|
-| `account` | String | The Cloudflare account ID that the event is associated with. |
-| `action` | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
-| `bucket` | String | The name of the bucket where the event occurred. |
-| `object` | Object | A nested object containing details about the object involved in the event. |
-| `object.key` | String | The key (or name) of the object within the bucket. |
-| `object.size` | Number | The size of the object in bytes. Note: not present for object-delete events. |
-| `object.eTag` | String | The entity tag (eTag) of the object. Note: not present for object-delete events. |
-| `eventTime` | String | The time when the action that triggered the event occurred. |
-| `copySource` | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`. |
-| `copySource.bucket` | String | The bucket that contained the source object. |
-| `copySource.object` | String | The name of the source object. |
+| Property            | Type   | Description                                                                                                                                              |
+| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `account`           | String | The Cloudflare account ID that the event is associated with.                                                                                             |
+| `action`            | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
+| `bucket`            | String | The name of the bucket where the event occurred.                                                                                                         |
+| `object`            | Object | A nested object containing details about the object involved in the event.                                                                               |
+| `object.key`        | String | The key (or name) of the object within the bucket.                                                                                                       |
+| `object.size`       | Number | The size of the object in bytes. Note: not present for object-delete events.                                                                             |
+| `object.eTag`       | String | The entity tag (eTag) of the object. Note: not present for object-delete events.                                                                         |
+| `eventTime`         | String | The time when the action that triggered the event occurred.                                                                                              |
+| `copySource`        | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`.                         |
+| `copySource.bucket` | String | The bucket that contained the source object.                                                                                                             |
+| `copySource.object` | String | The name of the source object.                                                                                                                           |
 
 ## Notes
 
diff --git a/src/content/docs/r2/buckets/index.mdx b/src/content/docs/r2/buckets/index.mdx
index 6b32cf898b1518c..56bda3ed5e0d4ce 100644
--- a/src/content/docs/r2/buckets/index.mdx
+++ b/src/content/docs/r2/buckets/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 With object storage, all of your objects are stored in buckets. Buckets do not contain folders that group the individual files, but instead, buckets have a flat structure which simplifies the way you access and retrieve the objects in your bucket.
 
diff --git a/src/content/docs/r2/buckets/object-lifecycles.mdx b/src/content/docs/r2/buckets/object-lifecycles.mdx
index 8aa7719e17e7b1a..0eaef01b4fefed0 100644
--- a/src/content/docs/r2/buckets/object-lifecycles.mdx
+++ b/src/content/docs/r2/buckets/object-lifecycles.mdx
@@ -35,6 +35,7 @@ When you create an object lifecycle rule, you can specify which prefix you would
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object Lifecycle Rules**, select **Add rule**.
@@ -186,6 +187,7 @@ console.log(
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object lifecycle rules**, select the rules you would like to delete.
diff --git a/src/content/docs/r2/buckets/storage-classes.mdx b/src/content/docs/r2/buckets/storage-classes.mdx
index d26bd2b34d5a359..329e212d619b99e 100644
--- a/src/content/docs/r2/buckets/storage-classes.mdx
+++ b/src/content/docs/r2/buckets/storage-classes.mdx
@@ -6,22 +6,22 @@ products:
   - r2
 ---
 
-import { Badge, Tabs, TabItem } from "~/components"
+import { Badge, Tabs, TabItem } from "~/components";
 
 Storage classes allow you to trade off between the cost of storage and the cost of accessing data. Every object stored in R2 has an associated storage class.
 
 All storage classes share the following characteristics:
 
-* Compatible with Workers API, S3 API, and public buckets.
-* 99.999999999% (eleven 9s) of annual durability.
-* No minimum object size.
+- Compatible with Workers API, S3 API, and public buckets.
+- 99.999999999% (eleven 9s) of annual durability.
+- No minimum object size.
 
 ## Available storage classes
 
-| Storage class                  | Minimum storage duration  | Data retrieval fees (processing) | Egress fees (data transfer to Internet)  |
-|--------------------------------|---------------------------|----------------------------------|------------------------------------------|
-| Standard                       | None                      | None                             | None                                     |
-| Infrequent Access              | 30 days                   | Yes                              | None                                     |
+| Storage class     | Minimum storage duration | Data retrieval fees (processing) | Egress fees (data transfer to Internet) |
+| ----------------- | ------------------------ | -------------------------------- | --------------------------------------- |
+| Standard          | None                     | None                             | None                                    |
+| Infrequent Access | 30 days                  | Yes                              | None                                    |
 
 For more information on how storage classes impact pricing, refer to [Pricing](/r2/pricing/).
 
@@ -31,11 +31,11 @@ Standard storage is designed for data that is accessed frequently. This is the d
 
 #### Example use cases
 
-* Website and application data
-* Media content (e.g., images, video)
-* Storing large datasets for analysis and processing
-* AI training data
-* Other workloads involving frequently accessed data
+- Website and application data
+- Media content (e.g., images, video)
+- Storing large datasets for analysis and processing
+- AI training data
+- Other workloads involving frequently accessed data
 
 ### Infrequent Access storage
 
@@ -47,9 +47,9 @@ For objects stored in Infrequent Access storage, you will be charged for the obj
 
 #### Example use cases
 
-* Long-term data archiving (for example, logs and historical records needed for compliance)
-* Data backup and disaster recovery
-* Long tail user-generated content
+- Long-term data archiving (for example, logs and historical records needed for compliance)
+- Data backup and disaster recovery
+- Long tail user-generated content
 
 ## Set default storage class for buckets
 
diff --git a/src/content/docs/r2/data-migration/index.mdx b/src/content/docs/r2/data-migration/index.mdx
index 05a1dabde3c991d..1fc637f6979b11a 100644
--- a/src/content/docs/r2/data-migration/index.mdx
+++ b/src/content/docs/r2/data-migration/index.mdx
@@ -58,4 +58,4 @@ Quickly and easily migrate data from other cloud providers to R2. Explore each o
 	</tbody>
 </table>
 
-For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
\ No newline at end of file
+For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
diff --git a/src/content/docs/r2/data-migration/migration-strategies.mdx b/src/content/docs/r2/data-migration/migration-strategies.mdx
index 9771c0a5eb95eb3..484528cc3c1eabc 100644
--- a/src/content/docs/r2/data-migration/migration-strategies.mdx
+++ b/src/content/docs/r2/data-migration/migration-strategies.mdx
@@ -60,4 +60,4 @@ You can create separate jobs with prefixes such as:
 - `/photos/2024` to migrate all 2024 files
 - `/photos/202` to migrate all files from 2023 and 2024
 
-Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
\ No newline at end of file
+Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
diff --git a/src/content/docs/r2/data-migration/sippy.mdx b/src/content/docs/r2/data-migration/sippy.mdx
index 66ef2a76b92a898..5715798fe2b8a77 100644
--- a/src/content/docs/r2/data-migration/sippy.mdx
+++ b/src/content/docs/r2/data-migration/sippy.mdx
@@ -85,10 +85,10 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 
 When enabled, Sippy exposes metrics that help you understand the progress of your ongoing migrations.
 
-| Metric | Description |
-|--------|-------------|
+| Metric                   | Description                                                                                                                                                    |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Requests served by Sippy | The percentage of overall requests served by R2 over a period of time. A higher percentage indicates that fewer requests need to be made to the source bucket. |
-| Data migrated by Sippy | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes. |
+| Data migrated by Sippy   | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes.                                                 |
 
 To view current and historical metrics:
 
@@ -138,12 +138,12 @@ Cloudflare currently supports copying data from the following cloud object stora
 
 When Sippy is enabled, it changes the behavior of certain actions on your R2 bucket across [Workers](/r2/api/workers/), [S3 API](/r2/api/s3/), and [public buckets](/r2/buckets/public-buckets/).
 
-| Action | New behavior |
-|--------|-------------|
-| GetObject | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
-| HeadObject | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket. |
-| PutObject | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket. |
-| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul> |
+| Action       | New behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| GetObject    | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
+| HeadObject   | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| PutObject    | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 
 Actions not listed above have no change in behavior. For more information, refer to [Workers API reference](/r2/api/workers/workers-api-reference/) or [S3 API compatibility](/r2/api/s3/api/).
 
diff --git a/src/content/docs/r2/data-migration/super-slurper.mdx b/src/content/docs/r2/data-migration/super-slurper.mdx
index 584c6edca51ca0f..9788052b63d58ac 100644
--- a/src/content/docs/r2/data-migration/super-slurper.mdx
+++ b/src/content/docs/r2/data-migration/super-slurper.mdx
@@ -32,6 +32,7 @@ For migration use cases that do not meet the above criteria, we recommend using
 1. In the Cloudflare dashboard, go to the **R2 data migration** page.
 
    <DashButton url="/?to=/:account/r2/slurper" />
+
 2. Select **Migrate files**.
 3. Select the source cloud storage provider that you will be migrating data from.
 4. Enter your source bucket name and associated credentials and select **Next**.
@@ -136,7 +137,11 @@ You can now use this JSON key file when enabling Super Slurper.
 
 ### ETags
 
-<Render file="migrator-etag-caveat" params={{ one: "Super Slurper" }} product="r2" />
+<Render
+	file="migrator-etag-caveat"
+	params={{ one: "Super Slurper" }}
+	product="r2"
+/>
 
 ### Archive storage classes
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
index a4c2c23cbae798d..d603be9a7e32e27 100644
--- a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
@@ -7,7 +7,7 @@ products:
   - r2
 ---
 
-import { PackageManagers, Tabs, TabItem } from '~/components';
+import { PackageManagers, Tabs, TabItem } from "~/components";
 
 The following example shows how to authenticate against R2 using the S3 API and an API token.
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
index 76b0c32d6744f0f..0d2a8e4861600f8 100644
--- a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
@@ -40,14 +40,14 @@ The response wraps the credentials in a `result` object:
 
 ```json
 {
-  "result": {
-    "accessKeyId": "<accessKeyId>",
-    "secretAccessKey": "<secretAccessKey>",
-    "sessionToken": "<sessionToken>"
-  },
-  "errors": [],
-  "messages": [],
-  "success": true
+	"result": {
+		"accessKeyId": "<accessKeyId>",
+		"secretAccessKey": "<secretAccessKey>",
+		"sessionToken": "<sessionToken>"
+	},
+	"errors": [],
+	"messages": [],
+	"success": true
 }
 ```
 
@@ -63,77 +63,77 @@ The following helper signs a JWT with your parent secret access key and derives
 import { SignJWT } from "jose";
 
 type R2Scope =
-  | "object-read-only"
-  | "object-read-write"
-  | "admin-read-only"
-  | "admin-read-write";
+	| "object-read-only"
+	| "object-read-write"
+	| "admin-read-only"
+	| "admin-read-write";
 
 export interface TempCredentialOptions {
-  scope: R2Scope;
-  // Optional: narrow the credential to specific S3 operations.
-  actions?: string[];
-  // Time-to-live in seconds. Defaults to 1 hour.
-  ttlSeconds?: number;
-  // Optional: restrict access to specific prefixes or objects.
-  paths?: { prefixPaths?: string[]; objectPaths?: string[] };
+	scope: R2Scope;
+	// Optional: narrow the credential to specific S3 operations.
+	actions?: string[];
+	// Time-to-live in seconds. Defaults to 1 hour.
+	ttlSeconds?: number;
+	// Optional: restrict access to specific prefixes or objects.
+	paths?: { prefixPaths?: string[]; objectPaths?: string[] };
 }
 
 export async function createTempCredentials(
-  endpoint: string,
-  accountId: string,
-  parentAccessKeyId: string,
-  parentSecretAccessKey: string,
-  bucket: string,
-  opts: TempCredentialOptions,
+	endpoint: string,
+	accountId: string,
+	parentAccessKeyId: string,
+	parentSecretAccessKey: string,
+	bucket: string,
+	opts: TempCredentialOptions,
 ): Promise<{
-  accessKeyId: string;
-  secretAccessKey: string;
-  sessionToken: string;
+	accessKeyId: string;
+	secretAccessKey: string;
+	sessionToken: string;
 }> {
-  const ttl = opts.ttlSeconds ?? 3600;
-
-  const claims: Record<string, unknown> = {
-    bucket,
-    scope: opts.scope,
-  };
-
-  if (opts.actions !== undefined && opts.actions.length > 0) {
-    claims.actions = opts.actions;
-  }
-
-  if (opts.paths !== undefined) {
-    claims.paths = {
-      prefixPaths: opts.paths.prefixPaths ?? [],
-      objectPaths: opts.paths.objectPaths ?? [],
-    };
-  }
-
-  // Sign the JWT with the parent secret access key. R2 validates this signature.
-  const jwt = await new SignJWT(claims)
-    .setProtectedHeader({ alg: "HS256", typ: "JWT" })
-    .setSubject(accountId)
-    .setIssuer(parentAccessKeyId)
-    .setAudience(new URL(endpoint).host)
-    .setIssuedAt()
-    .setExpirationTime(`${ttl}s`)
-    .sign(new TextEncoder().encode(parentSecretAccessKey));
-
-  // The temporary secret access key is the SHA-256 hex digest of the signed JWT.
-  const digest = await crypto.subtle.digest(
-    "SHA-256",
-    new TextEncoder().encode(jwt),
-  );
-  const secretAccessKey = Array.from(new Uint8Array(digest))
-    .map((b) => b.toString(16).padStart(2, "0"))
-    .join("");
-
-  return {
-    // Reuse the parent access key ID as the temporary access key ID.
-    accessKeyId: parentAccessKeyId,
-    secretAccessKey,
-    // The session token is base64("jwt/" + signed JWT).
-    sessionToken: btoa(`jwt/${jwt}`),
-  };
+	const ttl = opts.ttlSeconds ?? 3600;
+
+	const claims: Record<string, unknown> = {
+		bucket,
+		scope: opts.scope,
+	};
+
+	if (opts.actions !== undefined && opts.actions.length > 0) {
+		claims.actions = opts.actions;
+	}
+
+	if (opts.paths !== undefined) {
+		claims.paths = {
+			prefixPaths: opts.paths.prefixPaths ?? [],
+			objectPaths: opts.paths.objectPaths ?? [],
+		};
+	}
+
+	// Sign the JWT with the parent secret access key. R2 validates this signature.
+	const jwt = await new SignJWT(claims)
+		.setProtectedHeader({ alg: "HS256", typ: "JWT" })
+		.setSubject(accountId)
+		.setIssuer(parentAccessKeyId)
+		.setAudience(new URL(endpoint).host)
+		.setIssuedAt()
+		.setExpirationTime(`${ttl}s`)
+		.sign(new TextEncoder().encode(parentSecretAccessKey));
+
+	// The temporary secret access key is the SHA-256 hex digest of the signed JWT.
+	const digest = await crypto.subtle.digest(
+		"SHA-256",
+		new TextEncoder().encode(jwt),
+	);
+	const secretAccessKey = Array.from(new Uint8Array(digest))
+		.map((b) => b.toString(16).padStart(2, "0"))
+		.join("");
+
+	return {
+		// Reuse the parent access key ID as the temporary access key ID.
+		accessKeyId: parentAccessKeyId,
+		secretAccessKey,
+		// The session token is base64("jwt/" + signed JWT).
+		sessionToken: btoa(`jwt/${jwt}`),
+	};
 }
 ```
 
@@ -145,17 +145,17 @@ import { createTempCredentials } from "./temp-credentials";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const creds = await createTempCredentials(
-  R2_URL,
-  ACCOUNT_ID,
-  PARENT_ACCESS_KEY_ID,
-  PARENT_SECRET_ACCESS_KEY,
-  "my-bucket",
-  {
-    scope: "object-read-only",
-    actions: ["GetObject", "HeadObject"],
-    ttlSeconds: 900,
-    paths: { prefixPaths: ["data/"] },
-  },
+	R2_URL,
+	ACCOUNT_ID,
+	PARENT_ACCESS_KEY_ID,
+	PARENT_SECRET_ACCESS_KEY,
+	"my-bucket",
+	{
+		scope: "object-read-only",
+		actions: ["GetObject", "HeadObject"],
+		ttlSeconds: 900,
+		paths: { prefixPaths: ["data/"] },
+	},
 );
 ```
 
@@ -169,10 +169,10 @@ import { AwsClient } from "aws4fetch";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const client = new AwsClient({
-  accessKeyId: ACCESS_KEY_ID,
-  secretAccessKey: SECRET_ACCESS_KEY,
-  sessionToken: SESSION_TOKEN,
-  service: "s3",
+	accessKeyId: ACCESS_KEY_ID,
+	secretAccessKey: SECRET_ACCESS_KEY,
+	sessionToken: SESSION_TOKEN,
+	service: "s3",
 });
 
 // Allowed: object under the data/ prefix.
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
index 8c7b8736c9498a9..1fb6ee02263c766 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
@@ -58,9 +58,7 @@ console.log(await S3.send(new ListBucketsCommand({})));
 //     }
 // }
 
-console.log(
-	await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })),
-);
+console.log(await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })));
 // {
 //     '$metadata': {
 //       httpStatusCode: 200,
@@ -157,13 +155,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -182,5 +180,6 @@ const putUrl = await getSignedUrl(
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
index 3143d3c15d33437..a7845d865d25f16 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
@@ -74,11 +74,11 @@ You can also generate presigned links that can be used to share public read or w
 ```ts
 // Use the expires property to determine how long the presigned link is valid.
 console.log(
-await s3.getSignedUrlPromise("getObject", {
-	Bucket: "my-bucket",
-	Key: "dog.png",
-	Expires: 3600,
-}),
+	await s3.getSignedUrlPromise("getObject", {
+		Bucket: "my-bucket",
+		Key: "dog.png",
+		Expires: 3600,
+	}),
 );
 // You can also create links for operations such as putObject to allow temporary write access to a specific key.
 // Specify ContentType to restrict uploads to a specific file type.
@@ -115,13 +115,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -137,5 +137,6 @@ const putUrl = await s3.getSignedUrlPromise("putObject", {
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
index e19b20b7d19fdd1..ef0c34ebe76c4fc 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
@@ -104,4 +104,3 @@ To download a file using the GET URL:
 ```bash
 curl -X GET "https://<your-presigned-get-url>" -o downloaded-file.txt
 ```
-
diff --git a/src/content/docs/r2/examples/aws/aws4fetch.mdx b/src/content/docs/r2/examples/aws/aws4fetch.mdx
index 6330b4a288944d3..51411a247aef736 100644
--- a/src/content/docs/r2/examples/aws/aws4fetch.mdx
+++ b/src/content/docs/r2/examples/aws/aws4fetch.mdx
@@ -144,13 +144,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -172,5 +172,6 @@ const putUrl = signedRequest.url.toString();
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/boto3.mdx b/src/content/docs/r2/examples/aws/boto3.mdx
index fe1fe466ad3d55c..9dce860b7a623d6 100644
--- a/src/content/docs/r2/examples/aws/boto3.mdx
+++ b/src/content/docs/r2/examples/aws/boto3.mdx
@@ -118,13 +118,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -145,5 +145,6 @@ put_url = s3.generate_presigned_url(
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/custom-header.mdx b/src/content/docs/r2/examples/aws/custom-header.mdx
index 59695cb8019c958..31c3e784bed5934 100644
--- a/src/content/docs/r2/examples/aws/custom-header.mdx
+++ b/src/content/docs/r2/examples/aws/custom-header.mdx
@@ -45,35 +45,32 @@ print(response)
 `aws-sdk-js-v3` allows the customization of request behavior through the use of its [middleware stack](https://aws.amazon.com/blogs/developer/middleware-stack-modular-aws-sdk-js/). This example adds a middleware to the client which adds a header to every `PutObject` request being made.
 
 ```ts
-import {
-  PutObjectCommand,
-  S3Client,
-} from "@aws-sdk/client-s3";
+import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-  region: "auto", // Required by SDK but not used by R2
-  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-  credentials: {
-    accessKeyId: ACCESS_KEY_ID,
-    secretAccessKey: SECRET_ACCESS_KEY,
-  },
+	region: "auto", // Required by SDK but not used by R2
+	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+	credentials: {
+		accessKeyId: ACCESS_KEY_ID,
+		secretAccessKey: SECRET_ACCESS_KEY,
+	},
 });
 
 client.middlewareStack.add(
-  (next, context) => async (args) => {
-      const r = args.request as RequestInit
-      r.headers["cf-create-bucket-if-missing"] = "true";
+	(next, context) => async (args) => {
+		const r = args.request as RequestInit;
+		r.headers["cf-create-bucket-if-missing"] = "true";
 
-      return await next(args)
-    },
-  { step: 'build', name: 'customHeaders' },
-)
+		return await next(args);
+	},
+	{ step: "build", name: "customHeaders" },
+);
 
 const command = new PutObjectCommand({
-  Bucket: "my_bucket",
-  Key: "my_key",
-  Body: "my_data"
+	Bucket: "my_bucket",
+	Key: "my_key",
+	Body: "my_data",
 });
 
 const response = await client.send(command);
@@ -127,44 +124,40 @@ print(response)
 Here we again configure the header we would like to set by creating a middleware, but this time we add the middleware to the request itself instead of to the whole client.
 
 ```ts
-import {
-  PutObjectCommand,
-  S3Client,
-} from "@aws-sdk/client-s3";
+import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-  region: "auto", // Required by SDK but not used by R2
-  // Provide your Cloudflare account ID
-  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-  credentials: {
-    accessKeyId: ACCESS_KEY_ID,
-    secretAccessKey: SECRET_ACCESS_KEY,
-  },
+	region: "auto", // Required by SDK but not used by R2
+	// Provide your Cloudflare account ID
+	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+	credentials: {
+		accessKeyId: ACCESS_KEY_ID,
+		secretAccessKey: SECRET_ACCESS_KEY,
+	},
 });
 
 const command = new PutObjectCommand({
-  Bucket: "my_bucket",
-  Key: "my_key",
-  Body: "my_data"
+	Bucket: "my_bucket",
+	Key: "my_key",
+	Body: "my_data",
 });
 
-const headers = { 'If-Match': '"29d911f495d1ba7cb3a4d7d15e63236a"' }
+const headers = { "If-Match": '"29d911f495d1ba7cb3a4d7d15e63236a"' };
 command.middlewareStack.add(
-  (next) =>
-    (args) => {
-      const r = args.request as RequestInit
-
-      Object.entries(headers).forEach(
-        ([k, v]: [key: string, value: string]): void => {
-          r.headers[k] = v
-        },
-      )
-
-      return next(args)
-    },
-  { step: 'build', name: 'customHeaders' },
-)
+	(next) => (args) => {
+		const r = args.request as RequestInit;
+
+		Object.entries(headers).forEach(
+			([k, v]: [key: string, value: string]): void => {
+				r.headers[k] = v;
+			},
+		);
+
+		return next(args);
+	},
+	{ step: "build", name: "customHeaders" },
+);
 const response = await client.send(command);
 
 console.log(response);
diff --git a/src/content/docs/r2/examples/cache-api.mdx b/src/content/docs/r2/examples/cache-api.mdx
index 8b5d8ebd9354ccc..c5b5a3f0b9d2437 100644
--- a/src/content/docs/r2/examples/cache-api.mdx
+++ b/src/content/docs/r2/examples/cache-api.mdx
@@ -11,67 +11,64 @@ Use the [Cache API](/workers/runtime-apis/cache/) to store R2 objects in Cloudfl
 
 :::note
 
-
 You will need to [connect a custom domain](/workers/configuration/routing/custom-domains/) or [route](/workers/configuration/routing/routes/) to your Worker in order to use the Cache API. Cache API operations in the Cloudflare Workers dashboard editor, Playground previews, and any `*.workers.dev` deployments will have no impact.
 
-
 :::
 
 ```js
-
 export default {
-  async fetch(request, env, context) {
-    try {
-      const url = new URL(request.url);
-
-      // Construct the cache key from the cache URL
-      const cacheKey = new Request(url.toString(), request);
-      const cache = caches.default;
-
-      // Check whether the value is already available in the cache
-      // if not, you will need to fetch it from R2, and store it in the cache
-      // for future access
-      let response = await cache.match(cacheKey);
-
-      if (response) {
-        console.log(`Cache hit for: ${request.url}.`);
-        return response;
-      }
-
-      console.log(
-        `Response for request url: ${request.url} not present in cache. Fetching and caching request.`
-      );
-
-      // If not in cache, get it from R2
-      const objectKey = url.pathname.slice(1);
-      const object = await env.MY_BUCKET.get(objectKey);
-      if (object === null) {
-        return new Response('Object Not Found', { status: 404 });
-      }
-
-      // Set the appropriate object headers
-      const headers = new Headers();
-      object.writeHttpMetadata(headers);
-      headers.set('etag', object.httpEtag);
-
-      // Cache API respects Cache-Control headers. Setting s-max-age to 10
-      // will limit the response to be in cache for 10 seconds max
-      // Any changes made to the response here will be reflected in the cached value
-      headers.append('Cache-Control', 's-maxage=10');
-
-      response = new Response(object.body, {
-        headers,
-      });
-
-      // Store the fetched response as cacheKey
-      // Use waitUntil so you can return the response without blocking on
-      // writing to cache
-      context.waitUntil(cache.put(cacheKey, response.clone()));
-
-      return response;
-    } catch (e) {
-      return new Response('Error thrown ' + e.message);
-    }
-  },
+	async fetch(request, env, context) {
+		try {
+			const url = new URL(request.url);
+
+			// Construct the cache key from the cache URL
+			const cacheKey = new Request(url.toString(), request);
+			const cache = caches.default;
+
+			// Check whether the value is already available in the cache
+			// if not, you will need to fetch it from R2, and store it in the cache
+			// for future access
+			let response = await cache.match(cacheKey);
+
+			if (response) {
+				console.log(`Cache hit for: ${request.url}.`);
+				return response;
+			}
+
+			console.log(
+				`Response for request url: ${request.url} not present in cache. Fetching and caching request.`,
+			);
+
+			// If not in cache, get it from R2
+			const objectKey = url.pathname.slice(1);
+			const object = await env.MY_BUCKET.get(objectKey);
+			if (object === null) {
+				return new Response("Object Not Found", { status: 404 });
+			}
+
+			// Set the appropriate object headers
+			const headers = new Headers();
+			object.writeHttpMetadata(headers);
+			headers.set("etag", object.httpEtag);
+
+			// Cache API respects Cache-Control headers. Setting s-max-age to 10
+			// will limit the response to be in cache for 10 seconds max
+			// Any changes made to the response here will be reflected in the cached value
+			headers.append("Cache-Control", "s-maxage=10");
+
+			response = new Response(object.body, {
+				headers,
+			});
+
+			// Store the fetched response as cacheKey
+			// Use waitUntil so you can return the response without blocking on
+			// writing to cache
+			context.waitUntil(cache.put(cacheKey, response.clone()));
+
+			return response;
+		} catch (e) {
+			return new Response("Error thrown " + e.message);
+		}
+	},
 };
 ```
diff --git a/src/content/docs/r2/examples/terraform.mdx b/src/content/docs/r2/examples/terraform.mdx
index 70ba59913732088..6298b67ad2b5e29 100644
--- a/src/content/docs/r2/examples/terraform.mdx
+++ b/src/content/docs/r2/examples/terraform.mdx
@@ -7,18 +7,17 @@ products:
   - r2
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="keys" product="r2" /><br/>
+<Render file="keys" product="r2" />
+<br />
 
 This example shows how to configure R2 with Terraform using the [Cloudflare provider](https://github.com/cloudflare/terraform-provider-cloudflare).
 
 :::note[Note for using AWS provider]
 
-
 When using the Cloudflare Terraform provider, you can only manage buckets. To configure items such as CORS and object lifecycles, you will need to use the [AWS Provider](/r2/examples/terraform-aws/).
 
-
 :::
 
 With [`terraform`](https://developer.hashicorp.com/terraform/downloads) installed, create `main.tf` and copy the content below replacing with your API Token.
diff --git a/src/content/docs/r2/get-started/cli.mdx b/src/content/docs/r2/get-started/cli.mdx
index 96eb679c9c1e3f1..9d545d0ef4b0755 100644
--- a/src/content/docs/r2/get-started/cli.mdx
+++ b/src/content/docs/r2/get-started/cli.mdx
@@ -8,7 +8,14 @@ products:
   - r2
 ---
 
-import { PackageManagers, LinkCard, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	PackageManagers,
+	LinkCard,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 Manage R2 buckets and objects directly from your terminal. Use CLI tools to automate tasks and manage objects.
 
diff --git a/src/content/docs/r2/get-started/index.mdx b/src/content/docs/r2/get-started/index.mdx
index f23578ee0cbb2f0..dd498e4f6f5b795 100644
--- a/src/content/docs/r2/get-started/index.mdx
+++ b/src/content/docs/r2/get-started/index.mdx
@@ -16,6 +16,7 @@ Cloudflare R2 Storage allows developers to store large amounts of unstructured d
 ## Before you begin
 
 You need a Cloudflare account with an R2 subscription. If you do not have one:
+
 1. Go to the [Cloudflare Dashboard](https://dash.cloudflare.com/).
 2. Select **Storage & databases > R2 > Overview**
 3. Complete the checkout flow to add an R2 subscription to your account.
diff --git a/src/content/docs/r2/get-started/s3.mdx b/src/content/docs/r2/get-started/s3.mdx
index d8f07cb88333887..30f8f11008b2c09 100644
--- a/src/content/docs/r2/get-started/s3.mdx
+++ b/src/content/docs/r2/get-started/s3.mdx
@@ -8,7 +8,14 @@ products:
   - r2
 ---
 
-import { LinkCard, PackageManagers, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	LinkCard,
+	PackageManagers,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 R2 provides support for a [S3-compatible API](/r2/api/s3/api/), which means you can use any S3 SDK, library, or tool to interact with your buckets. If you have existing code that works with S3, you can use it with R2 by changing the endpoint URL.
 
diff --git a/src/content/docs/r2/get-started/workers-api.mdx b/src/content/docs/r2/get-started/workers-api.mdx
index 2fca2b0febc4696..408785ea7255ff2 100644
--- a/src/content/docs/r2/get-started/workers-api.mdx
+++ b/src/content/docs/r2/get-started/workers-api.mdx
@@ -15,7 +15,7 @@ import {
 	Render,
 	Tabs,
 	TabItem,
-	Steps
+	Steps,
 } from "~/components";
 
 [Workers](/workers/) let you run code at the edge. When you bind an R2 bucket to a Worker, you can read and write objects directly using the [Workers API](/r2/api/workers/workers-api-usage/).
diff --git a/src/content/docs/r2/objects/delete-objects.mdx b/src/content/docs/r2/objects/delete-objects.mdx
index a890b14c861b46d..30dedcd5ba096ac 100644
--- a/src/content/docs/r2/objects/delete-objects.mdx
+++ b/src/content/docs/r2/objects/delete-objects.mdx
@@ -17,6 +17,7 @@ You can delete objects from R2 using the dashboard, Workers API, S3 API, or comm
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. (Optional) Select the **View prefixes as directories** checkbox to view prefixes grouped as [folders](/r2/objects/#prefixes-and-folders).
 4. Select the objects or folders you want to delete. You can select a mix of both in the same operation.
@@ -110,19 +111,19 @@ wrangler r2 object delete test-bucket/image.png
 ## Related resources
 
 <LinkCard
-  title="Delete buckets"
-  href="/r2/buckets/delete-buckets/"
-  description="Empty all objects from a bucket and permanently delete it."
+	title="Delete buckets"
+	href="/r2/buckets/delete-buckets/"
+	description="Empty all objects from a bucket and permanently delete it."
 />
 
 <LinkCard
-  title="Bucket locks"
-  href="/r2/buckets/bucket-locks/"
-  description="Protect objects from accidental deletion with retention policies."
+	title="Bucket locks"
+	href="/r2/buckets/bucket-locks/"
+	description="Protect objects from accidental deletion with retention policies."
 />
 
 <LinkCard
-  title="Object lifecycles"
-  href="/r2/buckets/object-lifecycles/"
-  description="Automatically expire objects after a specified period."
+	title="Object lifecycles"
+	href="/r2/buckets/object-lifecycles/"
+	description="Automatically expire objects after a specified period."
 />
diff --git a/src/content/docs/r2/objects/download-objects.mdx b/src/content/docs/r2/objects/download-objects.mdx
index d060979a0b675d4..78ebe64fe9940ee 100644
--- a/src/content/docs/r2/objects/download-objects.mdx
+++ b/src/content/docs/r2/objects/download-objects.mdx
@@ -17,6 +17,7 @@ You can download objects from R2 using the dashboard, Workers API, S3 API, or co
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Locate the object you want to download.
 4. Select **...** for the object and click **Download**.
@@ -108,4 +109,4 @@ Use [Wrangler](/workers/wrangler/install-and-update/) to download objects. Run t
 wrangler r2 object get test-bucket/image.png
 ```
 
-The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
\ No newline at end of file
+The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
diff --git a/src/content/docs/r2/objects/index.mdx b/src/content/docs/r2/objects/index.mdx
index 7cee8cf9e982a0c..147e55a78a576d7 100644
--- a/src/content/docs/r2/objects/index.mdx
+++ b/src/content/docs/r2/objects/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Objects are individual files or data that you store in an R2 bucket. Each object is identified by its key, a string like `images/photo.png`.
 
@@ -22,4 +22,4 @@ The R2 dashboard groups objects that share a common prefix into folders when the
 
 <DirectoryListing />
 
-<Render file="link-to-workers-r2-api" product="r2"/>
\ No newline at end of file
+<Render file="link-to-workers-r2-api" product="r2" />
diff --git a/src/content/docs/r2/platform/audit-logs.mdx b/src/content/docs/r2/platform/audit-logs.mdx
index 56b604e8c1363a0..ca1e6d74b1b1059 100644
--- a/src/content/docs/r2/platform/audit-logs.mdx
+++ b/src/content/docs/r2/platform/audit-logs.mdx
@@ -22,18 +22,18 @@ For more information on how to access and use audit logs, refer to [Review audit
 
 The following configuration actions are logged:
 
-| Operation | Description |
-|-----------|-------------|
-| CreateBucket | Creation of a new bucket. |
-| DeleteBucket | Deletion of an existing bucket. |
-| AddCustomDomain | Addition of a custom domain to a bucket. |
-| RemoveCustomDomain | Removal of a custom domain from a bucket. |
-| ChangeBucketVisibility | Change to the managed public access (`r2.dev`) settings of a bucket. |
-| PutBucketStorageClass | Change to the default storage class of a bucket. |
-| PutBucketLifecycleConfiguration | Change to the object lifecycle configuration of a bucket. |
-| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket. |
-| PutBucketCors | Change to the CORS configuration for a bucket. |
-| DeleteBucketCors | Deletion of the CORS configuration for a bucket. |
+| Operation                          | Description                                                          |
+| ---------------------------------- | -------------------------------------------------------------------- |
+| CreateBucket                       | Creation of a new bucket.                                            |
+| DeleteBucket                       | Deletion of an existing bucket.                                      |
+| AddCustomDomain                    | Addition of a custom domain to a bucket.                             |
+| RemoveCustomDomain                 | Removal of a custom domain from a bucket.                            |
+| ChangeBucketVisibility             | Change to the managed public access (`r2.dev`) settings of a bucket. |
+| PutBucketStorageClass              | Change to the default storage class of a bucket.                     |
+| PutBucketLifecycleConfiguration    | Change to the object lifecycle configuration of a bucket.            |
+| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket.         |
+| PutBucketCors                      | Change to the CORS configuration for a bucket.                       |
+| DeleteBucketCors                   | Deletion of the CORS configuration for a bucket.                     |
 
 :::note
 Logs for data access operations, such as `GetObject` and `PutObject`, are not included in audit logs. To log HTTP requests made to public R2 buckets, use the [HTTP requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) Logpush dataset.
@@ -45,23 +45,22 @@ Below is an example of an audit log entry showing the creation of a new bucket:
 
 ```json
 {
-  "action": { "info": "CreateBucket", "result": true, "type": "create" },
-  "actor": {
-    "email": "<ACTOR_EMAIL>",
-    "id": "3f7b730e625b975bc1231234cfbec091",
-    "ip": "fe32:43ed:12b5:526::1d2:13",
-    "type": "user"
-  },
-  "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-  "interface": "API",
-  "metadata": { "zone_name": "r2.cloudflarestorage.com" },
-  "newValue": "",
-  "newValueJson": {},
-  "oldValue": "",
-  "oldValueJson": {},
-  "owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
-  "resource": { "id": "my-bucket", "type": "r2.bucket" },
-  "when": "2024-07-15T16:32:52.412Z"
+	"action": { "info": "CreateBucket", "result": true, "type": "create" },
+	"actor": {
+		"email": "<ACTOR_EMAIL>",
+		"id": "3f7b730e625b975bc1231234cfbec091",
+		"ip": "fe32:43ed:12b5:526::1d2:13",
+		"type": "user"
+	},
+	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+	"interface": "API",
+	"metadata": { "zone_name": "r2.cloudflarestorage.com" },
+	"newValue": "",
+	"newValueJson": {},
+	"oldValue": "",
+	"oldValueJson": {},
+	"owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
+	"resource": { "id": "my-bucket", "type": "r2.bucket" },
+	"when": "2024-07-15T16:32:52.412Z"
 }
-
 ```
diff --git a/src/content/docs/r2/platform/metrics-analytics.mdx b/src/content/docs/r2/platform/metrics-analytics.mdx
index 91288c6dcf21e47..e28dc53a56af003 100644
--- a/src/content/docs/r2/platform/metrics-analytics.mdx
+++ b/src/content/docs/r2/platform/metrics-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 R2 exposes analytics that allow you to inspect the requests and storage of the buckets in your account.
 
@@ -16,8 +16,8 @@ The metrics displayed for a bucket in the [Cloudflare dashboard](https://dash.cl
 
 R2 currently has two datasets:
 
-| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                          |
-| --------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- |
+| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                                  |
+| --------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------- |
 | Operations                              | `r2OperationsAdaptiveGroups`                         | This dataset consists of the operations taken on a bucket within an account. |
 | Storage                                 | `r2StorageAdaptiveGroups`                            | This dataset consists of the storage of a bucket within an account.          |
 
@@ -58,6 +58,7 @@ Per-bucket analytics for R2 are available in the Cloudflare dashboard. To view c
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/r2/platform/troubleshooting.mdx b/src/content/docs/r2/platform/troubleshooting.mdx
index e42a38c8bff9748..726ef97a385e92b 100644
--- a/src/content/docs/r2/platform/troubleshooting.mdx
+++ b/src/content/docs/r2/platform/troubleshooting.mdx
@@ -21,6 +21,7 @@ If you do have a CORS issue, refer to [Resolving CORS issues](#if-it-is-actually
 1. Open developer tools on your browser.
 2. Go to the **Network** tab and find the failing request. You may need to reload the page, as requests are only logged after developer tools have been opened.
 3. Check the response headers for the following two headers:
+
 - `cf-cache-status`
 - `cf-mitigated`
 
@@ -64,7 +65,7 @@ If your users are directly uploading to the bucket (for example, using the S3 or
 
 ### Bucket sharding
 
-For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket.  While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
+For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket. While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
 
 ## Objects named `This object is unnamed`
 
@@ -84,4 +85,4 @@ For example, uploading an object named `example/` into an R2 bucket will be disp
 <FileTree>
 - example
   - `This object is unnamed`
-</FileTree>
\ No newline at end of file
+</FileTree>
diff --git a/src/content/docs/r2/pricing.mdx b/src/content/docs/r2/pricing.mdx
index 7c3d3a55663af73..6d420e4740d8b39 100644
--- a/src/content/docs/r2/pricing.mdx
+++ b/src/content/docs/r2/pricing.mdx
@@ -27,13 +27,13 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 ## R2 pricing
 
-|                                    | Standard storage         | Infrequent Access storage                               |
-| ---------------------------------- | ------------------------ | ------------------------------------------------------- |
-| Storage                            | $0.015 / GB-month        | $0.01 / GB-month                                        |
-| Class A Operations                 | $4.50 / million requests | $9.00 / million requests                                |
-| Class B Operations                 | $0.36 / million requests | $0.90 / million requests                                |
-| Data Retrieval (processing)        | None                     | $0.01 / GB                                              |
-| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                                               |
+|                                    | Standard storage         | Infrequent Access storage |
+| ---------------------------------- | ------------------------ | ------------------------- |
+| Storage                            | $0.015 / GB-month        | $0.01 / GB-month          |
+| Class A Operations                 | $4.50 / million requests | $9.00 / million requests  |
+| Class B Operations                 | $0.36 / million requests | $0.90 / million requests  |
+| Data Retrieval (processing)        | None                     | $0.01 / GB                |
+| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                 |
 
 :::caution[Billable unit rounding]
 Cloudflare rounds up your usage to the next billing unit.
@@ -43,7 +43,7 @@ For example:
 - If you have performed one million and one operations, you will be billed for two million operations.
 - If you have used 1.1 GB-month, you will be billed for 2 GB-month.
 - If you have retrieved data (for infrequent access storage) for 1.1 GB, you will be billed for 2 GB.
-:::
+  :::
 
 ### Free tier
 
@@ -92,10 +92,10 @@ Data retrieval fees apply when you access or retrieve data from the Infrequent A
 
 For objects stored in Infrequent Access storage, you will be charged for the object for the minimum storage duration even if the object was deleted, moved, or replaced before the specified duration.
 
-| Storage class                                          | Minimum storage duration |
-| ------------------------------------------------------ | ------------------------ |
-| Standard storage                                       | None                     |
-| Infrequent Access storage                              | 30 days                  |
+| Storage class             | Minimum storage duration |
+| ------------------------- | ------------------------ |
+| Standard storage          | None                     |
+| Infrequent Access storage | 30 days                  |
 
 ## R2 Data Catalog pricing
 
@@ -127,25 +127,25 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 If a user writes 1,000 objects in R2 **Standard storage** for 1 month with an average size of 1 GB and reads each object 1,000 times during the month, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85      |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00       |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00       |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA         | None              | $0.00       |
-| **TOTAL**                   |                                                               |              |                   | **$14.85**  |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price      |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ---------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85     |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00      |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00      |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | None              | $0.00      |
+| **TOTAL**                   |                                                               |              |                   | **$14.85** |
 
 ### Infrequent access example
 
 If a user writes 1,000 objects in R2 Infrequent Access storage with an average size of 1 GB, stores them for 5 days, and then deletes them (delete operations are free), and during those 5 days each object is read 1,000 times, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA           | 1,000 GB-months   | $10.00      |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA           | 1,000             | $9.00       |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA           | 1 million         | $0.90       |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | 1,000 GB          | $10.00      |
-| **TOTAL**                   |                                                               |              |                   | **$29.90**  |
+|                             | Usage                                                         | Free Tier | Billable Quantity | Price      |
+| --------------------------- | ------------------------------------------------------------- | --------- | ----------------- | ---------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA        | 1,000 GB-months   | $10.00     |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA        | 1,000             | $9.00      |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA        | 1 million         | $0.90      |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA        | 1,000 GB          | $10.00     |
+| **TOTAL**                   |                                                               |           |                   | **$29.90** |
 
 Note that the minimal storage duration for infrequent access storage is 30 days, which means the billable quantity is 1,000 GB-months, rather than 167 GB-months.
 
diff --git a/src/content/docs/r2/r2-sql.mdx b/src/content/docs/r2/r2-sql.mdx
index 690e0b283548807..727a004053c732a 100644
--- a/src/content/docs/r2/r2-sql.mdx
+++ b/src/content/docs/r2/r2-sql.mdx
@@ -10,4 +10,4 @@ description: >-
   R2 SQL is a serverless SQL interface for Cloudflare R2, enabling querying and analyzing data.
 products:
   - r2
----
\ No newline at end of file
+---
diff --git a/src/content/docs/r2/reference/data-location.mdx b/src/content/docs/r2/reference/data-location.mdx
index 64607b3dbd621ac..a55ac28a3ebbc87 100644
--- a/src/content/docs/r2/reference/data-location.mdx
+++ b/src/content/docs/r2/reference/data-location.mdx
@@ -29,6 +29,7 @@ You can choose to automatically create your bucket in the closest available regi
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, leave _None_ selected for automatic selection or choose a region from the list.
@@ -79,6 +80,7 @@ Use Jurisdictional Restrictions when you need to ensure data is stored and proce
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
diff --git a/src/content/docs/r2/reference/data-security.mdx b/src/content/docs/r2/reference/data-security.mdx
index 15c1260d9648ae3..96c66a58a3eb8df 100644
--- a/src/content/docs/r2/reference/data-security.mdx
+++ b/src/content/docs/r2/reference/data-security.mdx
@@ -26,10 +26,8 @@ Access over plaintext HTTP (without TLS/SSL) can be disabled by connecting a [cu
 
 :::note
 
-
 R2 custom domains use Cloudflare for SaaS certificates and cannot be customized. Even if you have [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/), the advanced certificate will not be used due to [certificate prioritization](/ssl/reference/certificate-and-hostname-priority/).
 
-
 :::
 
 ## Compliance
diff --git a/src/content/docs/r2/reference/durability.mdx b/src/content/docs/r2/reference/durability.mdx
index 177e6ed4bd08d13..5d15f76865bd036 100644
--- a/src/content/docs/r2/reference/durability.mdx
+++ b/src/content/docs/r2/reference/durability.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-R2 is designed to provide 99.999999999% (eleven 9s) of annual durability.  This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
+R2 is designed to provide 99.999999999% (eleven 9s) of annual durability. This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
 
 ## How R2 achieves eleven-nines durability
 
@@ -22,7 +22,7 @@ R2's durability is built on multiple layers of redundancy and data protection:
 
 ### Considerations
 
-* Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
-* R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
-* Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
-* Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
+- Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
+- R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
+- Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
+- Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
diff --git a/src/content/docs/r2/reference/unicode-interoperability.mdx b/src/content/docs/r2/reference/unicode-interoperability.mdx
index 1543c6629fa5744..77796a1f1294a90 100644
--- a/src/content/docs/r2/reference/unicode-interoperability.mdx
+++ b/src/content/docs/r2/reference/unicode-interoperability.mdx
@@ -16,8 +16,8 @@ R2 preserves the encoding for display though. When you list the objects, you wil
 
 There are still some platform-specific differences to consider:
 
-* Windows and macOS filenames are case-insensitive while R2 and Linux are not.
-* Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
-* Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
+- Windows and macOS filenames are case-insensitive while R2 and Linux are not.
+- Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
+- Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
 
 If it is important for you to be able to bypass the unicode equivalence and use byte-oriented key names, contact your Cloudflare account team.
diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx
index 0c041c84fc44833..1025cfea8f7c9bb 100644
--- a/src/content/docs/r2/tutorials/cloudflare-access.mdx
+++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx
@@ -49,7 +49,7 @@ To create an Access application for your R2 bucket:
    Ensure that your policies only allow the users within your organization that need access to this R2 bucket.
    :::
 
-6. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
+5. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
 
 ## 3. Connect a custom domain
 
diff --git a/src/content/docs/r2/tutorials/mastodon.mdx b/src/content/docs/r2/tutorials/mastodon.mdx
index 3a1bb7b0eae2ed8..dd7a6b339aace64 100644
--- a/src/content/docs/r2/tutorials/mastodon.mdx
+++ b/src/content/docs/r2/tutorials/mastodon.mdx
@@ -23,10 +23,8 @@ Different from the default hostname of your Mastodon instance, object storage fo
 
 :::note
 
-
 If you move from R2 to another S3 compatible service later on, you can continue using the same hostname determined in this step. We do not recommend changing the hostname after the instance has been running to avoid breaking historical file references. In such a scenario, [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) can be used to instruct requests reaching the previous hostname to refer to the new hostname.
 
-
 :::
 
 ### 2. Create and set up an R2 bucket
@@ -34,6 +32,7 @@ If you move from R2 to another S3 compatible service later on, you can continue
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter your bucket name and then select **Create bucket**. This name is internal when setting up your Mastodon instance and is not publicly accessible.
 4. Once the bucket is created, navigate to the **Settings** tab of this bucket and copy the value of **S3 API**.
diff --git a/src/content/docs/r2/tutorials/postman.mdx b/src/content/docs/r2/tutorials/postman.mdx
index 2c8fbc313867b2b..4bec7f80443cc16 100644
--- a/src/content/docs/r2/tutorials/postman.mdx
+++ b/src/content/docs/r2/tutorials/postman.mdx
@@ -11,7 +11,7 @@ products:
 
 import { DashButton } from "~/components";
 
-Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290) includes a complete list of operations supported by the platform.
+Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290) includes a complete list of operations supported by the platform.
 
 ## 1. Purchase R2
 
@@ -19,11 +19,11 @@ This guide assumes that you have made a Cloudflare account and purchased R2.
 
 ## 2. Explore R2 in Postman
 
-Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
+Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
 
 ## 3. Configure your R2 credentials
 
-In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
+In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
 
 To execute basic operations, you must set the `account-id`, `r2-access-key-id`, and `r2-secret-access-key` variables in the Postman dashboard > **Variables**.
 
@@ -32,8 +32,9 @@ To do this:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. In **R2**, under **Manage R2 API Tokens** on the right side of the dashboard, copy your Cloudflare account ID.
-3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation).
+3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation).
 4. Set the **CURRENT VALUE** of `account-id` to your Cloudflare account ID and select **Save**.
 
 Next, generate an R2 API token:
@@ -41,6 +42,7 @@ Next, generate an R2 API token:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. On the right hand sidebar, select **Manage R2 API Tokens**.
 3. Select **Create API token**.
 4. Name your token **Postman** by selecting the pencil icon next to the API name and grant it the **Edit** permission.
@@ -49,7 +51,7 @@ Guard this token and the **Access Key ID** and **Secret Access Key** closely. Yo
 
 After you have created your API token in the Cloudflare dashboard:
 
-1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation) > **Variables**.
+1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation) > **Variables**.
 2. Copy `Access Key ID` value from the Cloudflare dashboard and paste it into Postman’s `r2-access-key-id` variable value and select **Save**.
 3. Copy the `Secret Access Key` value from the Cloudflare dashboard and paste it into Postman’s `r2-secret-access-key` variable value and select **Save**.
 
diff --git a/src/content/docs/r2/video-tutorials.mdx b/src/content/docs/r2/video-tutorials.mdx
index 67585e1469ac91a..f92a3914495462c 100644
--- a/src/content/docs/r2/video-tutorials.mdx
+++ b/src/content/docs/r2/video-tutorials.mdx
@@ -12,9 +12,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Introduction to R2"
-        description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
-        href="/learning-paths/r2-intro/series/r2-1/"
-    />
+	<LinkCard
+		title="Introduction to R2"
+		description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
+		href="/learning-paths/r2-intro/series/r2-1/"
+	/>
 </CardGrid>
diff --git a/src/content/docs/radar/concepts/index.mdx b/src/content/docs/radar/concepts/index.mdx
index e8c3c876f284ebb..e439f4733f5f884 100644
--- a/src/content/docs/radar/concepts/index.mdx
+++ b/src/content/docs/radar/concepts/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/concepts/normalization.mdx b/src/content/docs/radar/concepts/normalization.mdx
index dbf55dfbe42a9f7..3a2a09e5b4ebd78 100644
--- a/src/content/docs/radar/concepts/normalization.mdx
+++ b/src/content/docs/radar/concepts/normalization.mdx
@@ -19,7 +19,7 @@ Refer to the `result.meta.normalization` property in the response to check which
 | `PERCENTAGE`            | Values represent percentages.                                                                                                                                                    |
 | `PERCENTAGE_CHANGE`     | Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period.                                   |
 | `OVERLAPPED_PERCENTAGE` | Values represent percentages that exceed 100% due to overlap.                                                                                                                    |
-| `MIN_MAX`               | Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)).                                                  |
+| `MIN_MAX`               | Values have been normalized using [min-max](<https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_(min-max_normalization)>).                                                  |
 | `MIN0_MAX`              | Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
 | `RAW_VALUES`            | Values are raw and have not been changed.                                                                                                                                        |
 
diff --git a/src/content/docs/radar/get-started/configure-alerts.mdx b/src/content/docs/radar/get-started/configure-alerts.mdx
index 6e7641992176d98..64ad4396db7c424 100644
--- a/src/content/docs/radar/get-started/configure-alerts.mdx
+++ b/src/content/docs/radar/get-started/configure-alerts.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications when Radar detects changes impacting countries, regions, or autonomous systems.
 
diff --git a/src/content/docs/radar/get-started/embed.mdx b/src/content/docs/radar/get-started/embed.mdx
index 249eccb402d8918..bf036cde8f960ad 100644
--- a/src/content/docs/radar/get-started/embed.mdx
+++ b/src/content/docs/radar/get-started/embed.mdx
@@ -25,8 +25,8 @@ Charts supporting this feature will have a share icon next to its description.
 
 1. Select the Share icon next to the description of the chart you wish to share.
 2. Select between Fixed Time and Real Time.
-   * Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
-   * Fixed Time will always display a chart with only the currently visible data points.
+   - Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
+   - Fixed Time will always display a chart with only the currently visible data points.
 3. Select Copy Code and paste the code into your web page.
 
 **Note**: Your current selections, such as date range, location, autonomous system (ASN), and visible series, will be reflected in the shared chart.
diff --git a/src/content/docs/radar/get-started/index.mdx b/src/content/docs/radar/get-started/index.mdx
index 1ce36868a710f4f..809a736dd35ebc9 100644
--- a/src/content/docs/radar/get-started/index.mdx
+++ b/src/content/docs/radar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/get-started/making-comparisons.mdx b/src/content/docs/radar/get-started/making-comparisons.mdx
index 9bffd560f9e690b..984fcafb3a77490 100644
--- a/src/content/docs/radar/get-started/making-comparisons.mdx
+++ b/src/content/docs/radar/get-started/making-comparisons.mdx
@@ -35,26 +35,26 @@ The response (shortened below for brevity) uses the provided `name` property to
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "us_data": {
-      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
-      "values": [ "0.871752", "1" ]
-    },
-    "pt_data": {
-      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
-      "values": [ "0.020457", "0.012313" ]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-10-26T17:00:00Z",
-        "endTime": "2022-11-02T17:00:00Z"
-      },
-      "aggInterval": "ONE_HOUR",
+	"success": true,
+	"errors": [],
+	"result": {
+		"us_data": {
+			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
+			"values": ["0.871752", "1"]
+		},
+		"pt_data": {
+			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
+			"values": ["0.020457", "0.012313"]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-10-26T17:00:00Z",
+				"endTime": "2022-11-02T17:00:00Z"
+			},
+			"aggInterval": "ONE_HOUR"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -81,14 +81,24 @@ Now, in the `result` property, you should get something like this:
 
 ```json
 {
-  "this_week": {
-    "timestamps": [ "2022-10-27T13:00:00Z", "2022-10-27T14:00:00Z", "...", "2022-11-03T12:00:00Z" ],
-    "values": [ "0.794321", "1", "...", "0.718433"]
-  },
-  "previous_week": {
-    "timestamps": [ "2022-10-20T13:00:00Z", "2022-10-20T14:00:00Z", "...", "2022-10-27T12:00:00Z" ],
-    "values": [ "0.774392", "0.835071", "...", "0.720181"]
-  }
+	"this_week": {
+		"timestamps": [
+			"2022-10-27T13:00:00Z",
+			"2022-10-27T14:00:00Z",
+			"...",
+			"2022-11-03T12:00:00Z"
+		],
+		"values": ["0.794321", "1", "...", "0.718433"]
+	},
+	"previous_week": {
+		"timestamps": [
+			"2022-10-20T13:00:00Z",
+			"2022-10-20T14:00:00Z",
+			"...",
+			"2022-10-27T12:00:00Z"
+		],
+		"values": ["0.774392", "0.835071", "...", "0.720181"]
+	}
 }
 ```
 
@@ -118,11 +128,21 @@ The `result` property should return a response like this:
 ```json
 {
 	"tonga": {
-		"timestamps": ["2022-10-15T02:00:00Z", "2022-10-15T03:00:00Z", "2022-10-15T04:00:00Z", "2022-10-15T05:00:00Z"],
+		"timestamps": [
+			"2022-10-15T02:00:00Z",
+			"2022-10-15T03:00:00Z",
+			"2022-10-15T04:00:00Z",
+			"2022-10-15T05:00:00Z"
+		],
 		"values": ["1.0", "0.832473", "0.820083", "0.79408"]
 	},
 	"tonga_outage": {
-		"timestamps": ["2022-01-15T02:00:00Z", "2022-01-15T03:00:00Z", "2022-01-15T04:00:00Z", "2022-01-15T05:00:00Z"],
+		"timestamps": [
+			"2022-01-15T02:00:00Z",
+			"2022-01-15T03:00:00Z",
+			"2022-01-15T04:00:00Z",
+			"2022-01-15T05:00:00Z"
+		],
 		"values": ["0.354105", "0.357287", "0.181811", "0.044198"]
 	}
 }
diff --git a/src/content/docs/radar/investigate/application-layer-attacks.mdx b/src/content/docs/radar/investigate/application-layer-attacks.mdx
index bef19dc325ce63d..62b6591ff068b45 100644
--- a/src/content/docs/radar/investigate/application-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/application-layer-attacks.mdx
@@ -40,27 +40,27 @@ From the abbreviated response below, we can conclude that distributed denial-of-
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks": {
-      "timestamps": ["2022-11-05T11:00:00Z", ".."],
-      "ddos": ["53.824302", "54.305823",  ".."],
-      "waf": ["39.760956", "39.31228",  ".."],
-      "ip_reputation": ["5.623487", "5.485468",  ".."],
-      "access_rules": ["0.648368", "0.676456",  ".."],
-      "bot_management": ["0.139733", "0.217155",  ".."],
-      "api_shield": ["0.003154", "0.002819",  ".."],
-      "data_loss_prevention": ["0.0", "0.0",  ".."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-05T11:00:00Z",
-        "endTime": "2022-11-06T11:00:00Z"
-      },
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks": {
+			"timestamps": ["2022-11-05T11:00:00Z", ".."],
+			"ddos": ["53.824302", "54.305823", ".."],
+			"waf": ["39.760956", "39.31228", ".."],
+			"ip_reputation": ["5.623487", "5.485468", ".."],
+			"access_rules": ["0.648368", "0.676456", ".."],
+			"bot_management": ["0.139733", "0.217155", ".."],
+			"api_shield": ["0.003154", "0.002819", ".."],
+			"data_loss_prevention": ["0.0", "0.0", ".."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-05T11:00:00Z",
+				"endTime": "2022-11-06T11:00:00Z"
+			}
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -79,9 +79,9 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"attacks_gb": {
 			"waf": "75.012138",
 			"ddos": "18.539149",
@@ -90,10 +90,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 			"bot_management": "0.131998",
 			"api_shield": "0.003178",
 			"data_loss_prevention": "0.0"
-  	},
+		},
 		"meta": {
 			// ...
-    }
+		}
 	}
 }
 ```
@@ -115,10 +115,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks_target": [
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks_target": [
 			{
 				"targetCountryName": "Belgium",
 				"targetCountryAlpha2": "BE",
@@ -150,14 +150,14 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 				"rank": 5
 			}
 		],
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-05T12:00:00Z",
-        "endTime": "2022-11-06T12:00:00Z"
-      },
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-05T12:00:00Z",
+				"endTime": "2022-11-06T12:00:00Z"
+			}
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -178,9 +178,9 @@ A typical response will be similar to the following:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"originCountryName": "United States",
@@ -223,10 +223,10 @@ A typical response will be similar to the following:
 				"rank": 5
 			}
 		],
-    "meta": {
+		"meta": {
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/dns.mdx b/src/content/docs/radar/investigate/dns.mdx
index 59db1f37eb09dbc..837edba24ef5632 100644
--- a/src/content/docs/radar/investigate/dns.mdx
+++ b/src/content/docs/radar/investigate/dns.mdx
@@ -27,9 +27,9 @@ The response shows that most queries come from the United States and Brazil:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "US",
@@ -43,9 +43,9 @@ The response shows that most queries come from the United States and Brazil:
 			}
 		],
 		"meta": {
-      // ...
-    }
-  }
+			// ...
+		}
+	}
 }
 ```
 
@@ -60,9 +60,9 @@ Returns the following response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "RU",
@@ -76,9 +76,9 @@ Returns the following response:
 			}
 		],
 		"meta": {
-      // ...
-    }
-  }
+			// ...
+		}
+	}
 }
 ```
 
@@ -86,7 +86,7 @@ As expected, most queries come from Russia.
 
 :::note
 
-Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
+Note that these examples return the total number of DNS queries from a location to a hostname, _out_ of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
 :::
 
 You can also provide multiple hostnames. Refer to [Get DNS top locations](/api/resources/radar/subresources/dns/subresources/top/methods/locations/) for more information. This is useful when the application you want to explore uses several hostnames to serve its content (like a hostname for the main website, another hostname dedicated to its API, etc.).
diff --git a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
index 9c025150aa46f67..26d9f65fea55f7d 100644
--- a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
+++ b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
@@ -8,10 +8,10 @@ products:
   - radar
 ---
 
-Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/),  Cloudflare's public DNS resolver.  Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
+Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/), Cloudflare's public DNS resolver. Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
 
-* An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
-* An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
+- An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
+- An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
 
 ## List of endpoints
 
@@ -26,10 +26,10 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "top_0": [
+	"success": true,
+	"errors": [],
+	"result": {
+		"top_0": [
 			{
 				"rank": 1,
 				"domain": "google.com"
@@ -50,8 +50,8 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 				"rank": 5,
 				"domain": "apple.com"
 			}
-    ]
-  },
+		]
+	},
 	"meta": {
 		// ...
 	}
@@ -75,24 +75,21 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets?limit=10&datasetType=R
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"datasets": [
 			{
 				"id": 213,
 				"title": "Top 1000000 ranking domains",
 				"description": "Unordered top 1000000 from 2023-01-02 to 2023-01-09",
 				"type": "RANKING_BUCKET",
-				"tags": [
-					"GLOBAL",
-					"top_1000000"
-				],
+				"tags": ["GLOBAL", "top_1000000"],
 				"meta": {
 					"top": 1000000
 				},
 				"alias": "ranking_top_1000000"
-			},
+			}
 			// ...
 		]
 	}
@@ -114,9 +111,9 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets/download" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"dataset": {
 			"url": "https://example.com/download"
 		}
diff --git a/src/content/docs/radar/investigate/http-requests.mdx b/src/content/docs/radar/investigate/http-requests.mdx
index 8fcdba8ef35ed24..f850973ae9af912 100644
--- a/src/content/docs/radar/investigate/http-requests.mdx
+++ b/src/content/docs/radar/investigate/http-requests.mdx
@@ -19,9 +19,9 @@ Most of the charts in the [Adoption and Usage](https://radar.cloudflare.com/adop
 
 These endpoints can be broadly split into:
 
-* `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
-* `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
-* `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
+- `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
+- `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
+- `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
 
 ## List of endpoints
 
@@ -40,29 +40,29 @@ Here is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "human": {
-      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-      "mobile": ["52.5532", "52.146628", ".."],
-      "desktop": ["47.394791", "47.800731", ".."],
-      "other": ["0.052009", "0.052642", ".."]
-    },
-    "bot": {
-      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-      "desktop": ["83.833892", "84.017711", ".."],
-      "mobile": ["16.156748", "15.969936", ".."],
-      "other": ["0.00936", "0.012353", ".."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-03T13:00:00Z",
-        "endTime": "2022-11-04T13:00:00Z"
-      },
-      "normalization": "PERCENTAGE"
-    }
-  }
+	"success": true,
+	"errors": [],
+	"result": {
+		"human": {
+			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+			"mobile": ["52.5532", "52.146628", ".."],
+			"desktop": ["47.394791", "47.800731", ".."],
+			"other": ["0.052009", "0.052642", ".."]
+		},
+		"bot": {
+			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+			"desktop": ["83.833892", "84.017711", ".."],
+			"mobile": ["16.156748", "15.969936", ".."],
+			"other": ["0.00936", "0.012353", ".."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-03T13:00:00Z",
+				"endTime": "2022-11-04T13:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
+		}
+	}
 }
 ```
 
@@ -90,9 +90,9 @@ Here is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"human": {
 			"mobile": "54.967243",
 			"desktop": "44.974006",
@@ -103,7 +103,7 @@ Here is the abbreviated response:
 			"mobile": "16.707455",
 			"other": "0.017093"
 		}
-  }
+	}
 }
 ```
 
@@ -122,9 +122,9 @@ This returns the following:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"human": {
 			"IPv4": "76.213647",
 			"IPv6": "23.786353"
@@ -133,7 +133,7 @@ This returns the following:
 			"IPv4": "91.492032",
 			"IPv6": "8.507968"
 		}
-  }
+	}
 }
 ```
 
@@ -156,9 +156,9 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"ipv6": [
 			{
 				"clientCountryAlpha2": "IN",
@@ -186,7 +186,7 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 				"value": "39.1514"
 			}
 		]
-  }
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/index.mdx b/src/content/docs/radar/investigate/index.mdx
index c377e8628eba30c..5c1a9cd5a898a6c 100644
--- a/src/content/docs/radar/investigate/index.mdx
+++ b/src/content/docs/radar/investigate/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore the different types of data available in Cloudflare Radar, from NetFlows (what feeds the [Internet Traffic Change](https://radar.cloudflare.com/) chart in Radar) to HTTP requests and DNS queries.
 
diff --git a/src/content/docs/radar/investigate/netflows.mdx b/src/content/docs/radar/investigate/netflows.mdx
index 1d7c85ee2290995..3971efa9cabc498 100644
--- a/src/content/docs/radar/investigate/netflows.mdx
+++ b/src/content/docs/radar/investigate/netflows.mdx
@@ -36,9 +36,9 @@ This is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS3243_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.565885", "0.586434", "..."]
@@ -64,9 +64,9 @@ The abbreviated response is:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
@@ -92,9 +92,9 @@ which would lead to a response like this:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
diff --git a/src/content/docs/radar/investigate/network-layer-attacks.mdx b/src/content/docs/radar/investigate/network-layer-attacks.mdx
index edd685c50ae34f8..56394fa33270271 100644
--- a/src/content/docs/radar/investigate/network-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/network-layer-attacks.mdx
@@ -35,36 +35,36 @@ If we inspect the abbreviated response below, we can conclude that globally, at
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "global": {
-      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-      "udp": ["50.784034", "51.055221", "..."],
-      "tcp": ["49.213944", "48.943769", "..."],
-      "icmp": ["0.002023", "0.001009", "..."],
-      "gre": ["0.0", "0.0", "0.0", "..."]
-    },
-    "singapore": {
-      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-      "tcp": ["79.605287", "83.943885", "..."],
-      "udp": ["20.394594", "16.056115", "..."],
-      "icmp": ["0.000119", "0.0", "..."],
-      "gre": ["0.0", "0.0", "..."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-06T13:00:00Z",
-        "endTime": "2022-11-07T13:00:00Z"
-      },
-      "normalization": "PERCENTAGE",
+	"success": true,
+	"errors": [],
+	"result": {
+		"global": {
+			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+			"udp": ["50.784034", "51.055221", "..."],
+			"tcp": ["49.213944", "48.943769", "..."],
+			"icmp": ["0.002023", "0.001009", "..."],
+			"gre": ["0.0", "0.0", "0.0", "..."]
+		},
+		"singapore": {
+			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+			"tcp": ["79.605287", "83.943885", "..."],
+			"udp": ["20.394594", "16.056115", "..."],
+			"icmp": ["0.000119", "0.0", "..."],
+			"gre": ["0.0", "0.0", "..."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-06T13:00:00Z",
+				"endTime": "2022-11-07T13:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
-We can also conclude that the distribution of network layer attacks coming from Singapore  — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
+We can also conclude that the distribution of network layer attacks coming from Singapore — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
 
 For more information refer to the [API reference](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) for this endpoint.
 
@@ -81,24 +81,24 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer3/summary?location
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks_ru": {
-      "udp": "86.682356",
-      "tcp": "11.928664",
-      "gre": "1.381015",
-      "icmp": "0.007965"
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-06T15:00:00Z",
-        "endTime": "2022-11-07T15:00:00Z"
-      },
-      "normalization": "PERCENTAGE",
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks_ru": {
+			"udp": "86.682356",
+			"tcp": "11.928664",
+			"gre": "1.381015",
+			"icmp": "0.007965"
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-06T15:00:00Z",
+				"endTime": "2022-11-07T15:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/outages.mdx b/src/content/docs/radar/investigate/outages.mdx
index 6d6f0d662f2a97e..4627c42298d06d6 100644
--- a/src/content/docs/radar/investigate/outages.mdx
+++ b/src/content/docs/radar/investigate/outages.mdx
@@ -12,13 +12,13 @@ products:
 
 Refer the [blog post](https://blog.cloudflare.com/announcing-cloudflare-radar-outage-center/) for more information but, in short, Radar provides the following information:
 
-* **Location**: Where was the outage?
-* **ASN**: What autonomous system experienced a disruption in connectivity?
-* **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
-* **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
-* **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
-* **Start time**: When did the outage start?
-* **End time**: When did the outage end?
+- **Location**: Where was the outage?
+- **ASN**: What autonomous system experienced a disruption in connectivity?
+- **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
+- **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
+- **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
+- **Start time**: When did the outage start?
+- **End time**: When did the outage end?
 
 ## List of endpoints
 
diff --git a/src/content/docs/radar/investigate/url-scanner.mdx b/src/content/docs/radar/investigate/url-scanner.mdx
index ec99e52a8ef0c7b..ab5ce64f3fd1662 100644
--- a/src/content/docs/radar/investigate/url-scanner.mdx
+++ b/src/content/docs/radar/investigate/url-scanner.mdx
@@ -14,7 +14,7 @@ To better understand Internet usage around the world, use Cloudflare's URL Scann
 
 ## Use the API
 
-To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with *Account* > *URL Scanner* in the **Permissions** group, and select *Edit* as the access level.
+To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with _Account_ > _URL Scanner_ in the **Permissions** group, and select _Edit_ as the access level.
 
 Once you have the token, and you know your `account_id`, you are ready to make your first request to the API at `https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/`.
 
@@ -37,11 +37,11 @@ A successful response will have a status code of `200` and be similar to the fol
 
 ```json
 {
-  "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-  "api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-  "visibility": "public",
-  "url": "https://www.example.com",
-  "message": "Submission successful"
+	"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+	"api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+	"visibility": "public",
+	"url": "https://www.example.com",
+	"message": "Submission successful"
 }
 ```
 
@@ -56,11 +56,9 @@ Here's an example request body with some custom configuration options:
 ```json
 {
 	"url": "https://example.com",
-	"screenshotsResolutions": [
-		"desktop", "mobile", "tablet"
-	],
-  "customagent": "XXX-my-user-agent",
-  "referer": "example",
+	"screenshotsResolutions": ["desktop", "mobile", "tablet"],
+	"customagent": "XXX-my-user-agent",
+	"referer": "example",
 	"customHeaders": {
 		"Authorization": "xxx-token"
 	},
@@ -68,7 +66,7 @@ Here's an example request body with some custom configuration options:
 }
 ```
 
-Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In  effect, only users with knowledge of the scan ID will be able to access it.
+Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In effect, only users with knowledge of the scan ID will be able to access it.
 
 There will also be three screenshots taken of the webpage, one per target device type. The [`User-Agent`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) will be set as "XXX-my-user-agent". Note that you can set any custom HTTP header, including [Authorization](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Authorization).
 
@@ -84,38 +82,38 @@ While the scan is in progress, the HTTP status code will be `404`; once it is fi
 
 The response will include, among others, the following top properties:
 
-* `task` - Information on the scan submission.
-* `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
-* `data.requests` - Request chains involved in the page load.
-* `data.cookies` - Cookies set by the page.
-* `data.globals` - Non-standard JavaScript global variables.
-* `data.console` - Console logs.
-* `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
-* `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
-* `lists.ips` - IPs contacted.
-* `lists.asns` - AS Numbers contacted.
-* `lists.domains` - Hostnames contacted, including `dns` record information.
-* `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
-* `lists.certificates` - TLS certificates of HTTP responses.
-* `verdicts` - Verdicts on malicious content.
+- `task` - Information on the scan submission.
+- `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
+- `data.requests` - Request chains involved in the page load.
+- `data.cookies` - Cookies set by the page.
+- `data.globals` - Non-standard JavaScript global variables.
+- `data.console` - Console logs.
+- `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
+- `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
+- `lists.ips` - IPs contacted.
+- `lists.asns` - AS Numbers contacted.
+- `lists.domains` - Hostnames contacted, including `dns` record information.
+- `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
+- `lists.certificates` - TLS certificates of HTTP responses.
+- `verdicts` - Verdicts on malicious content.
 
 Some examples of more specific properties include:
 
-* `task.uuid` - ID of the scan.
-* `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
-* `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
-* `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
-* `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
-* `meta.processors.phishing` - What kind of phishing, if any, was detected.
-* `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
-* `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
-* `page.url` - URL of the primary request, after all HTTP redirects.
-* `page.country` - Country name from geolocation data associated with the main IP address contacted.
-* `page.history` - Main page history, including any HTTP redirects.
-* `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
-* `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
-* `page.favicon.hash` - MD5 hash of the favicon.
-* `verdicts.overall.malicious` - Whether the website was considered malicious *at the time of the scan*. Please check the remaining properties for each subsystem(s) for specific threats detected.
+- `task.uuid` - ID of the scan.
+- `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
+- `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
+- `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
+- `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
+- `meta.processors.phishing` - What kind of phishing, if any, was detected.
+- `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
+- `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
+- `page.url` - URL of the primary request, after all HTTP redirects.
+- `page.country` - Country name from geolocation data associated with the main IP address contacted.
+- `page.history` - Main page history, including any HTTP redirects.
+- `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
+- `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
+- `page.favicon.hash` - MD5 hash of the favicon.
+- `verdicts.overall.malicious` - Whether the website was considered malicious _at the time of the scan_. Please check the remaining properties for each subsystem(s) for specific threats detected.
 
 The [Get URL Scan](/api/resources/url_scanner/subresources/scans/methods/get/) API endpoint documentation contains the full response schema.
 
@@ -132,7 +130,6 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/v2/s
 --header "Authorization: Bearer <API_TOKEN>"
 ```
 
-
 If, instead, you wanted to search for scans that made at least one request to the hostname `cdnjs.cloudflare.com`, for example sites that use a JavaScript library hosted at `cdnjs.cloudflare.com`, use the query parameter `hostname=cdnjs.cloudflare.com`:
 
 ```bash
@@ -153,14 +150,13 @@ Some other example queries:
 
 Go to [Search URL scans](/api/resources/url_scanner/subresources/scans/methods/list/) in the API documentation for the full list of available options.
 
-
 ### Security Center
 
 Alternatively, you can search in the Security Center:
 
 1. In the Cloudflare dashboard, go to the **Investigate** page.
 
-	 <DashButton url="/?to=/:account/security-center/investigate" />
+   <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your query and select **Search**.
 
@@ -176,7 +172,7 @@ To scan a URL based on your geographic location:
 2. Go to **Location** > Select which country to scan the URL from.
 3. Select **Scan now**.
 
-You can also use the [API](https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20) to scan a URL from a specific location.
+You can also use the [API](<https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20>) to scan a URL from a specific location.
 
 In Security Center, you can retrieve pre-filtered information by:
 
@@ -187,4 +183,4 @@ In Security Center, you can retrieve pre-filtered information by:
 - Identical ASN
 - Identical IP
 - Identical domain
-- Identical final URL (after all redirections)
\ No newline at end of file
+- Identical final URL (after all redirections)
diff --git a/src/content/docs/radar/mcp-server.mdx b/src/content/docs/radar/mcp-server.mdx
index ef902ec41e498a5..56303e7fd5ac8ad 100644
--- a/src/content/docs/radar/mcp-server.mdx
+++ b/src/content/docs/radar/mcp-server.mdx
@@ -10,4 +10,4 @@ sidebar:
     variant: note
 products:
   - radar
----
\ No newline at end of file
+---
diff --git a/src/content/docs/radar/reference/index.mdx b/src/content/docs/radar/reference/index.mdx
index 605b54567f61ed5..1223e257fc2e24e 100644
--- a/src/content/docs/radar/reference/index.mdx
+++ b/src/content/docs/radar/reference/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review reference information related to Cloudflare Radar:
 
diff --git a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
index 7b84e9fcb6eff4b..d08ecc4c77e6915 100644
--- a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
+++ b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
@@ -6,7 +6,7 @@ products:
   - radar
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Quarterly DDoS threat reports provide a comprehensive overview of <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attack</GlossaryTooltip> insights and trends over a three-month period.
 
@@ -14,7 +14,7 @@ Thanks to our vast network, Cloudflare provides insights on the evolving threat
 
 Find the latest quarterly DDoS threat reports in the [**Reports**](https://radar.cloudflare.com/reports) section of Cloudflare Radar.
 
-***
+---
 
 ## Methodologies
 
@@ -58,7 +58,7 @@ To calculate the attack size, duration, attack vectors, and emerging threats, Cl
 
 However, in the **Network layer attack distribution** graph of the [**Security & Attacks**](https://radar.cloudflare.com/security-and-attacks) Radar page these trends are calculated by number of bytes instead. Since attacks may vary greatly in number of bytes from one another, this could lead to trends differing between the quarterly reports and the graph displayed in Cloudflare Radar.
 
-***
+---
 
 ## Final remarks
 
diff --git a/src/content/docs/randomness-beacon/about/background.mdx b/src/content/docs/randomness-beacon/about/background.mdx
index 34ad6ab86602697..3985a768398b9d4 100644
--- a/src/content/docs/randomness-beacon/about/background.mdx
+++ b/src/content/docs/randomness-beacon/about/background.mdx
@@ -11,7 +11,7 @@ products:
 description: History and development of the drand project.
 ---
 
-Over the years, a generation of public randomness (often referred to as *common coins*) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
+Over the years, a generation of public randomness (often referred to as _common coins_) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
 
 Realizing this, [Ewa Syta](http://ewa.syta.us/) started a project on [Scalable Bias-Resistant Distributed Randomness](https://eprint.iacr.org/2016/1067) during her PhD studies under the supervision of [Michael J. Fischer](http://www.cs.yale.edu/homes/fischer/) and [Bryan Ford](https://bford.info/) at Yale University. After Bryan moved to EPFL in 2015, the new members of the DEDIS team at EPFL ([Nicolas Gailly](https://github.com/nikkolasg/), [Linus Gasser](https://people.epfl.ch/linus.gasser), [Philipp Jovanovic](https://jovanovic.io/), [Ismail Khoffi](https://ismailkhoffi.com/), [Eleftherios Kokoris Kogias](https://lefteriskk.github.io/)) joined the project and together published a research paper at the [2017 IEEE Symposium on Security and Privacy](https://ieeexplore.ieee.org/abstract/document/7958592).
 
diff --git a/src/content/docs/randomness-beacon/about/future.mdx b/src/content/docs/randomness-beacon/about/future.mdx
index 486975f9356ffc8..76c17926bf29159 100644
--- a/src/content/docs/randomness-beacon/about/future.mdx
+++ b/src/content/docs/randomness-beacon/about/future.mdx
@@ -15,10 +15,10 @@ As of spring 2020, the drand network is production-ready and can now be consider
 
 While the project has reached a mature state, we believe there are several ways for drand to continue to evolve.
 
-* We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
+- We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
 
-* We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
+- We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
 
-* We would like to consider standardization of the core drand protocol.
+- We would like to consider standardization of the core drand protocol.
 
 We are proud to be a part of these efforts and hope to see even more adoption of drand in third-party applications and systems.
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
index 59049a2b40a28d4..0678464a6ad4525 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
@@ -12,11 +12,11 @@ drand is an efficient randomness beacon daemon that utilizes pairing-based crypt
 
 This is an overview of the cryptographic building blocks drand uses to generate publicly-verifiable, unbiasable, and unpredictable randomness in a distributed manner.
 
-The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are *n* participants, out of which at most *f\<n* are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of *t-f+1* nodes work together to successfully execute cryptographic operations.
+The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are _n_ participants, out of which at most _f\<n_ are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of _t-f+1_ nodes work together to successfully execute cryptographic operations.
 
-Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where *t-of-n* participants are required to sign a transaction using a threshold signature scheme.
+Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where _t-of-n_ participants are required to sign a transaction using a threshold signature scheme.
 
 :::note[Note]
 
-This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts. 
+This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts.
 :::
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
index b3c4780456fd4fd..c39777be50f168c 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
@@ -16,11 +16,11 @@ First, we explain pairing-based cryptography (PBC), which has become quite popul
 
 Pairing-based cryptography is based on bilinear groups `(𝔾1,𝔾2,𝔾𝑡)`, where `𝔾1`, `𝔾2`, and `𝔾𝑡` are cyclic groups of prime order `𝑝` with generators `𝑔1`, `𝑔2`, and `𝑔𝑡`, respectively, and a pairing operation `𝑒:𝔾1×𝔾2→𝔾𝑡` with these properties:
 
-* **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
+- **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
 
-* **Non-degeneracy:** `𝑒≠1`
+- **Non-degeneracy:** `𝑒≠1`
 
-* **Computability:** There exists an efficient algorithm to compute `𝑒`.
+- **Computability:** There exists an efficient algorithm to compute `𝑒`.
   drand currently uses the Barreto-Lynn-Scott curve BLS12-381.
 
 ## BLS Signatures
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
index 1931a7beb984bc1..27152a46a610de6 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
@@ -8,7 +8,7 @@ products:
 description: Learn about the distributed key generation phase.
 ---
 
-In the drand setup phase, you create a collective private and public key pair shared among *𝑛* participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
+In the drand setup phase, you create a collective private and public key pair shared among _𝑛_ participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
 
 A DKG is performed in a fully distributed manner, avoiding any single points of failure. This is an overview of the different sub-components of the drand DKG implementation.
 
@@ -36,7 +36,7 @@ Note that you can use any subset of `𝑡-of-𝑛` shares to perform Lagrange in
 
 SSS scheme assumes that the dealer is honest, but this may not always hold in practice. A Verifiable Secret Sharing (VSS) scheme protects against malicious dealers by enabling participants to verify that their shares are consistent with those dealt to other nodes, ensuring that the shared secret can be correctly reconstructed later.
 
-drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A *cyclic group* means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
+drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A _cyclic group_ means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
 
 ### Share Distribution
 
diff --git a/src/content/docs/realtime/agents/index.mdx b/src/content/docs/realtime/agents/index.mdx
index 251f1183eda51db..841ef041c51d3c4 100644
--- a/src/content/docs/realtime/agents/index.mdx
+++ b/src/content/docs/realtime/agents/index.mdx
@@ -10,6 +10,6 @@ products:
   - realtime
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing/>
+<DirectoryListing />
diff --git a/src/content/docs/realtime/realtimekit/ai/index.mdx b/src/content/docs/realtime/realtimekit/ai/index.mdx
index 69baea7896467dd..0b4b56d2c3a2e40 100644
--- a/src/content/docs/realtime/realtimekit/ai/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/index.mdx
@@ -17,7 +17,7 @@ RealtimeKit provides AI-powered features using Cloudflare's AI infrastructure to
 ## Available features
 
 | Feature                                                  | Description                                 |
-| -------------------------------------------------------- | -----------------------------------------   |
+| -------------------------------------------------------- | ------------------------------------------- |
 | [Transcription](/realtime/realtimekit/ai/transcription/) | Real-time and end-of-meeting speech-to-text |
 | [Summary](/realtime/realtimekit/ai/summary/)             | AI-generated meeting summaries              |
 
diff --git a/src/content/docs/realtime/realtimekit/ai/summary.mdx b/src/content/docs/realtime/realtimekit/ai/summary.mdx
index 47577ad2f26f95d..f541baa92f1c99c 100644
--- a/src/content/docs/realtime/realtimekit/ai/summary.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/summary.mdx
@@ -20,44 +20,44 @@ Set `summarize_on_end: true` when [creating a meeting](/realtime/realtimekit/con
 
 ```json
 {
-  "title": "Product Review",
-  "ai_config": {
-    "transcription": {
-      "language": "en-US"
-    },
-    "summarization": {
-      "word_limit": 500,
-      "text_format": "markdown",
-      "summary_type": "team_meeting"
-    }
-  },
-  "summarize_on_end": true
+	"title": "Product Review",
+	"ai_config": {
+		"transcription": {
+			"language": "en-US"
+		},
+		"summarization": {
+			"word_limit": 500,
+			"text_format": "markdown",
+			"summary_type": "team_meeting"
+		}
+	},
+	"summarize_on_end": true
 }
 ```
 
 ## Configuration
 
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `word_limit` | number | 300 | Summary length (150-1000 words) |
-| `text_format` | string | `plain_text` | Output format: `plain_text` or `markdown` |
-| `summary_type` | string | `general` | Meeting context for tailored summaries |
+| Option         | Type   | Default      | Description                               |
+| -------------- | ------ | ------------ | ----------------------------------------- |
+| `word_limit`   | number | 300          | Summary length (150-1000 words)           |
+| `text_format`  | string | `plain_text` | Output format: `plain_text` or `markdown` |
+| `summary_type` | string | `general`    | Meeting context for tailored summaries    |
 
 ### Summary types
 
 Choose a type that matches your meeting for better results:
 
-| Type | Best for |
-|------|----------|
-| `general` | Any meeting (default) |
-| `team_meeting` | Regular team syncs |
-| `daily_standup` | Agile standups |
-| `one_on_one_meeting` | 1:1 meetings |
-| `sales_call` | Customer sales conversations |
-| `client_check_in` | Client status updates |
-| `interview` | Job interviews |
-| `lecture` | Educational content |
-| `code_review` | Technical code reviews |
+| Type                 | Best for                     |
+| -------------------- | ---------------------------- |
+| `general`            | Any meeting (default)        |
+| `team_meeting`       | Regular team syncs           |
+| `daily_standup`      | Agile standups               |
+| `one_on_one_meeting` | 1:1 meetings                 |
+| `sales_call`         | Customer sales conversations |
+| `client_check_in`    | Client status updates        |
+| `interview`          | Job interviews               |
+| `lecture`            | Educational content          |
+| `code_review`        | Technical code reviews       |
 
 ## Consume summaries
 
@@ -67,11 +67,11 @@ Configure `meeting.summary` event in [webhooks](/api/resources/realtime_kit/subr
 
 ```json
 {
-  "event": "meeting.summary",
-  "meetingId": "meeting-123",
-  "sessionId": "session-456",
-  "summaryDownloadUrl": "https://...",
-  "summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
+	"event": "meeting.summary",
+	"meetingId": "meeting-123",
+	"sessionId": "session-456",
+	"summaryDownloadUrl": "https://...",
+	"summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
 }
 ```
 
@@ -103,16 +103,19 @@ With `text_format: "markdown"` and `summary_type: "team_meeting"`:
 ## Meeting Summary
 
 ### Key Discussion Points
+
 - Reviewed Q4 roadmap priorities
 - Discussed deployment timeline for v2.0
 - Identified blockers for the auth migration
 
 ### Action Items
+
 - @alice: Update design specs by Friday
 - @bob: Schedule security review
 - @charlie: Create migration runbook
 
 ### Decisions Made
+
 - Approved moving forward with Kubernetes migration
 - Delayed analytics dashboard to next sprint
 ```
diff --git a/src/content/docs/realtime/realtimekit/ai/transcription.mdx b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
index fbedd591aeb9eb5..0c3a1720bf0478a 100644
--- a/src/content/docs/realtime/realtimekit/ai/transcription.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 RealtimeKit provides two transcription modes powered by Cloudflare Workers AI:
 
 | Mode               | Model                                                                | Use Case                       |
-| ----------------   | -------------------------------------------------------------------- | ------------------------------ |
+| ------------------ | -------------------------------------------------------------------- | ------------------------------ |
 | **Real-time**      | [Deepgram Nova-3](/workers-ai/models/nova-3/)                        | Live captions during meeting   |
 | **End-of-meeting** | [Whisper Large v3 Turbo](/workers-ai/models/whisper-large-v3-turbo/) | Accurate offline transcription |
 
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
index bfe857bd9ca8b92..f4de77a1ba6d15d 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
@@ -12,48 +12,50 @@ This module consists of the `ai` object which is used to interface with product'
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
 
-
-* [RTKAi](#module_RTKAi)
-    * _instance_
-        * [.telemetry](#module_RTKAi+telemetry)
-        * [.onTranscript(transcript)](#module_RTKAi+onTranscript)
-    * _static_
-        * [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
-        * [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
+- [RTKAi](#module_RTKAi)
+  - _instance_
+    - [.telemetry](#module_RTKAi+telemetry)
+    - [.onTranscript(transcript)](#module_RTKAi+onTranscript)
+  - _static_
+    - [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
+    - [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
 
 <a name="module_RTKAi+telemetry"></a>
 
 ### meeting.ai.telemetry
+
 **Kind**: instance property of [<code>RTKAi</code>](#module_RTKAi)  
 <a name="module_RTKAi+onTranscript"></a>
 
 ### meeting.ai.onTranscript(transcript)
-**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)
+
+| Param      | Type                           | Description                                 |
+| ---------- | ------------------------------ | ------------------------------------------- |
 | transcript | <code>TranscriptionData</code> | Transcript data received for a participant. |
 
 <a name="module_RTKAi.parseTranscript"></a>
 
 ### meeting.ai.parseTranscript(transcriptData, [isPartialTranscript])
+
 Parse a single line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| transcriptData | <code>string</code> |  | The transcript data to parse |
+| Param                 | Type                 | Default            | Description                       |
+| --------------------- | -------------------- | ------------------ | --------------------------------- |
+| transcriptData        | <code>string</code>  |                    | The transcript data to parse      |
 | [isPartialTranscript] | <code>boolean</code> | <code>false</code> | Whether the transcript is partial |
 
 <a name="module_RTKAi.parseTranscripts"></a>
 
 ### meeting.ai.parseTranscripts(transcriptData)
+
 Parse a multi-line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param          | Type                | Description                  |
+| -------------- | ------------------- | ---------------------------- |
 | transcriptData | <code>string</code> | The transcript data to parse |
-
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
index f0dc2d5d09f31ea..c5262c512d5524e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
@@ -10,340 +10,367 @@ web_core_version: 1.2.4
 
 This is the chat module, which can be used to send and receive messages from the meeting.
 
-
-* [RTKChat](#module_RTKChat)
-    * [module.exports](#exp_module_RTKChat--module.exports) ⏏
-        * [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
-        * ~~[.messages](#module_RTKChat--module.exports+messages)~~
-        * [.telemetry](#module_RTKChat--module.exports+telemetry)
-        * [.pinned](#module_RTKChat--module.exports+pinned)
-        * [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
-        * [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
-        * [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
-        * [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
-        * [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
-        * [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
-        * [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
-        * [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
-        * [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
-        * [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
-        * [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
-        * [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
-        * [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
-        * [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
-        * [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
-        * [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
-        * ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
-        * ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
-        * [.pin(id)](#module_RTKChat--module.exports+pin)
-        * [.unpin(id)](#module_RTKChat--module.exports+unpin)
-        * [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
-        * [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
-        * [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
-        * ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
-        * ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
+- [RTKChat](#module_RTKChat)
+  - [module.exports](#exp_module_RTKChat--module.exports) ⏏
+    - [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
+    - ~~[.messages](#module_RTKChat--module.exports+messages)~~
+    - [.telemetry](#module_RTKChat--module.exports+telemetry)
+    - [.pinned](#module_RTKChat--module.exports+pinned)
+    - [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
+    - [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
+    - [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
+    - [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
+    - [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
+    - [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
+    - [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
+    - [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
+    - [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
+    - [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
+    - [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
+    - [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
+    - [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
+    - [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
+    - [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
+    - [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
+    - ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
+    - ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
+    - [.pin(id)](#module_RTKChat--module.exports+pin)
+    - [.unpin(id)](#module_RTKChat--module.exports+unpin)
+    - [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
+    - [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
+    - [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
+    - ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
+    - ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
 
 <a name="exp_module_RTKChat--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKChat--module.exports_new"></a>
 
 #### new module.exports(context, chatSocketHandler, self, participants)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| chatSocketHandler | <code>RTKChatSocketHandler</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
+| Param             | Type                              |
+| ----------------- | --------------------------------- |
+| context           | <code>Context</code>              |
+| chatSocketHandler | <code>RTKChatSocketHandler</code> |
+| self              | <code>Self</code>                 |
+| participants      | <code>Participants</code>         |
 
 <a name="module_RTKChat--module.exports+messages"></a>
 
 #### ~~module.exports.messages~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+pinned"></a>
 
 #### module.exports.pinned
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 **Deprecated.**: This property is deprecated. Please use `fetchPinnedMessages()` instead.
 Returns an array of pinned messages.  
 <a name="module_RTKChat--module.exports+setMaxTextLimit"></a>
 
 #### module.exports.setMaxTextLimit(limit)
+
 Set the max character limit of a text message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param | Type                | Description                             |
+| ----- | ------------------- | --------------------------------------- |
 | limit | <code>number</code> | Max character limit for a text message. |
 
 <a name="module_RTKChat--module.exports+sendMessageInternal"></a>
 
 #### module.exports.sendMessageInternal(message, [participantIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>MessagePayload</code> | Message payload to send. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param            | Type                              | Description                             |
+| ---------------- | --------------------------------- | --------------------------------------- |
+| message          | <code>MessagePayload</code>       | Message payload to send.                |
 | [participantIds] | <code>Array.&lt;string&gt;</code> | Participant ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendTextMessageInternal"></a>
 
 #### module.exports.sendTextMessageInternal(message, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>string</code> | Text message to send. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                              | Description                      |
+| --------- | --------------------------------- | -------------------------------- |
+| message   | <code>string</code>               | Text message to send.            |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessageInternal"></a>
 
 #### module.exports.sendImageMessageInternal(image, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send.              |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessageInternal"></a>
 
 #### module.exports.sendFileMessageInternal(file, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | File to send. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | File to send.                    |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKChat--module.exports+sendTextMessage"></a>
 
 #### module.exports.sendTextMessage(message, [peerIds])
+
 Sends a chat text message to the room.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>string</code> | The message that must be sent to the room. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                              | Description                                |
+| --------- | --------------------------------- | ------------------------------------------ |
+| message   | <code>string</code>               | The message that must be sent to the room. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to.           |
 
 <a name="module_RTKChat--module.exports+sendCustomMessage"></a>
 
 #### module.exports.sendCustomMessage(message, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>CustomMessagePayload</code> | Custom message payload. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                              | Description                      |
+| --------- | --------------------------------- | -------------------------------- |
+| message   | <code>CustomMessagePayload</code> | Custom message payload.          |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessage"></a>
 
 #### module.exports.sendImageMessage(image, [peerIds])
+
 Sends an image message to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent.    |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessage"></a>
 
 #### module.exports.sendFileMessage(file, [peerIds])
+
 Sends a file to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | A File object. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | A File object.                   |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendMessage"></a>
 
 #### module.exports.sendMessage(message, [participantIds])
+
 Sends a message to the meeting. This method can be used to send text, image,
 or file messages. The message type is determined by the key 'type' in `message`
 object.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>MessagePayload</code> | An object including the type and content of the message. |
-| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants. |
+| Param            | Type                              | Description                                              |
+| ---------------- | --------------------------------- | -------------------------------------------------------- |
+| message          | <code>MessagePayload</code>       | An object including the type and content of the message. |
+| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants.      |
 
 <a name="module_RTKChat--module.exports+editTextMessage"></a>
 
 #### module.exports.editTextMessage(messageId, message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                | Description                |
+| --------- | ------------------- | -------------------------- |
 | messageId | <code>string</code> | Id of the message to edit. |
-| message | <code>string</code> | Updated text message. |
+| message   | <code>string</code> | Updated text message.      |
 
 <a name="module_RTKChat--module.exports+editImageMessage"></a>
 
 #### module.exports.editImageMessage(messageId, image)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                |
+| --------- | ------------------------------------------------- | -------------------------- |
+| messageId | <code>string</code>                               | Id of the message to edit. |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file.        |
 
 <a name="module_RTKChat--module.exports+editFileMessage"></a>
 
 #### module.exports.editFileMessage(messageId, file)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | Updated file. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                |
+| --------- | ------------------------------------------------- | -------------------------- |
+| messageId | <code>string</code>                               | Id of the message to edit. |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | Updated file.              |
 
 <a name="module_RTKChat--module.exports+editMessage"></a>
 
 #### module.exports.editMessage(messageId, message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| message | <code>MessagePayload</code> | Updated message payload. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                        | Description                |
+| --------- | --------------------------- | -------------------------- |
+| messageId | <code>string</code>         | Id of the message to edit. |
+| message   | <code>MessagePayload</code> | Updated message payload.   |
 
 <a name="module_RTKChat--module.exports+deleteMessage"></a>
 
 #### module.exports.deleteMessage(messageId)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                | Description                  |
+| --------- | ------------------- | ---------------------------- |
 | messageId | <code>string</code> | Id of the message to delete. |
 
 <a name="module_RTKChat--module.exports+getMessagesByUser"></a>
 
 #### ~~module.exports.getMessagesByUser(userId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                | Description                                    |
+| ------ | ------------------- | ---------------------------------------------- |
 | userId | <code>string</code> | The user id of the user that sent the message. |
 
 <a name="module_RTKChat--module.exports+getMessagesByType"></a>
 
 #### ~~module.exports.getMessagesByType(type)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| type | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
+| Param | Type                                                                                                                                                                 | Description                                   |
+| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
+| type  | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
 
 <a name="module_RTKChat--module.exports+pin"></a>
 
 #### module.exports.pin(id)
+
 Pins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | ID of the message to be pinned |
+| Param | Type                | Description                    |
+| ----- | ------------------- | ------------------------------ |
+| id    | <code>string</code> | ID of the message to be pinned |
 
 <a name="module_RTKChat--module.exports+unpin"></a>
 
 #### module.exports.unpin(id)
+
 Unpins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | ID of the message to be unpinned |
+| Param | Type                | Description                      |
+| ----- | ------------------- | -------------------------------- |
+| id    | <code>string</code> | ID of the message to be unpinned |
 
 <a name="module_RTKChat--module.exports+fetchPublicMessages"></a>
 
 #### module.exports.fetchPublicMessages(options)
+
 Fetches messages from the chat with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                             | Description                                                                                            |
+| ------- | -------------------------------- | ------------------------------------------------------------------------------------------------------ |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching messages, including timestamp, limit, and direction for pagination. |
 
 <a name="module_RTKChat--module.exports+fetchPrivateMessages"></a>
 
 #### module.exports.fetchPrivateMessages(options)
+
 Fetches private messages between the current user and another participant with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                                     | Description                                                                                                                             |
+| ------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
 | options | <code>FetchPrivateMessagesOptions</code> | Configuration options for fetching private messages, including private RTKChat ID (User ID of the participant) and pagination settings. |
 
 <a name="module_RTKChat--module.exports+fetchPinnedMessages"></a>
 
 #### module.exports.fetchPinnedMessages(options)
+
 Fetches pinned messages with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                             | Description                                                                                    |
+| ------- | -------------------------------- | ---------------------------------------------------------------------------------------------- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching pinned messages, including timestamp, limit, and direction. |
 
 <a name="module_RTKChat--module.exports+getMessages"></a>
 
 #### ~~module.exports.getMessages(timeStamp, size, reversed, [offset])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Default |
-| --- | --- | --- |
-| timeStamp | <code>number</code> |  | 
-| size | <code>number</code> |  | 
-| reversed | <code>boolean</code> |  | 
-| [offset] | <code>number</code> | <code>0</code> | 
+| Param     | Type                 | Default        |
+| --------- | -------------------- | -------------- |
+| timeStamp | <code>number</code>  |                |
+| size      | <code>number</code>  |                |
+| reversed  | <code>boolean</code> |                |
+| [offset]  | <code>number</code>  | <code>0</code> |
 
 <a name="module_RTKChat--module.exports+searchMessages"></a>
 
 #### ~~module.exports.searchMessages(query, [filters])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
 
-| Param | Type |
-| --- | --- |
-| query | <code>string</code> | 
-| [filters] | <code>SearchFilters</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
+| Param     | Type                       |
+| --------- | -------------------------- |
+| query     | <code>string</code>        |
+| [filters] | <code>SearchFilters</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
index 4f7519ff80810fe..05ce7315d3a789b 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
@@ -10,91 +10,96 @@ web_core_version: 1.2.4
 
 This consists of the methods to facilitate connected meetings
 
-
-* [RTKConnectedMeetings](#module_RTKConnectedMeetings)
-    * [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
-        * [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
-        * [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
-        * [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
-        * [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
-        * [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
-        * [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
-        * [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
+- [RTKConnectedMeetings](#module_RTKConnectedMeetings)
+  - [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
+    - [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
+    - [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
+    - [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
+    - [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
+    - [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
+    - [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
+    - [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
 
 <a name="exp_module_RTKConnectedMeetings--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKConnectedMeetings--module.exports_new"></a>
 
 #### new module.exports(context)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings"></a>
 
 #### module.exports.getRTKConnectedMeetings()
+
 get connected meeting state
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 <a name="module_RTKConnectedMeetings--module.exports+createMeetings"></a>
 
 #### module.exports.createMeetings(request)
+
 create connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| request | <code>Array.&lt;{title: string}&gt;</code> | 
+| Param   | Type                                       |
+| ------- | ------------------------------------------ |
+| request | <code>Array.&lt;{title: string}&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+updateMeetings"></a>
 
 #### module.exports.updateMeetings(request)
+
 update meeting title
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| request | <code>Array.&lt;{id: string, title: string}&gt;</code> | 
+| Param   | Type                                                   |
+| ------- | ------------------------------------------------------ |
+| request | <code>Array.&lt;{id: string, title: string}&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+deleteMeetings"></a>
 
 #### module.exports.deleteMeetings(meetingIds)
+
 delete connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| meetingIds | <code>Array.&lt;string&gt;</code> | 
+| Param      | Type                              |
+| ---------- | --------------------------------- |
+| meetingIds | <code>Array.&lt;string&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipants"></a>
 
 #### module.exports.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)
+
 Trigger event to move participants
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| sourceMeetingId | <code>string</code> | id of source meeting |
-| destinationMeetingId | <code>string</code> | id of destination meeting |
-| participantIds | <code>Array.&lt;string&gt;</code> | list of id of the participants |
+| Param                | Type                              | Description                    |
+| -------------------- | --------------------------------- | ------------------------------ |
+| sourceMeetingId      | <code>string</code>               | id of source meeting           |
+| destinationMeetingId | <code>string</code>               | id of destination meeting      |
+| participantIds       | <code>Array.&lt;string&gt;</code> | list of id of the participants |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset"></a>
 
 #### module.exports.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)
-Trigger event to move participants with custom preset
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+Trigger event to move participants with custom preset
 
-| Param | Type | Description |
-| --- | --- | --- |
-| sourceMeetingId | <code>string</code> | id of source meeting |
-| destinationMeetingId | <code>string</code> | id of destination meeting |
-| participants | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |  |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
+| Param                | Type                                                      | Description               |
+| -------------------- | --------------------------------------------------------- | ------------------------- |
+| sourceMeetingId      | <code>string</code>                                       | id of source meeting      |
+| destinationMeetingId | <code>string</code>                                       | id of destination meeting |
+| participants         | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |                           |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
index 4d2d4d56bab5c91..2706403d75acd35 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
@@ -11,55 +11,59 @@ web_core_version: 1.2.4
 The RTKLivestream module represents the state of the current livestream, and allows
 to start/stop live streams.
 
-
-* [RTKLivestream](#module_RTKLivestream)
-    * [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
-        * [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
-        * [.telemetry](#module_RTKLivestream--module.exports+telemetry)
-        * [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
-        * [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
-        * [.stop()](#module_RTKLivestream--module.exports+stop)
+- [RTKLivestream](#module_RTKLivestream)
+  - [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
+    - [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
+    - [.telemetry](#module_RTKLivestream--module.exports+telemetry)
+    - [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
+    - [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
+    - [.stop()](#module_RTKLivestream--module.exports+stop)
 
 <a name="exp_module_RTKLivestream--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKLivestream--module.exports_new"></a>
 
 #### new module.exports(context, self)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
+| self    | <code>Self</code>    |
 
 <a name="module_RTKLivestream--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 <a name="module_RTKLivestream--module.exports+setRTKLivestreamState"></a>
 
 #### module.exports.setRTKLivestreamState(livestreamState)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| livestreamState | <code>RTKLivestreamState</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+
+| Param           | Type                            |
+| --------------- | ------------------------------- |
+| livestreamState | <code>RTKLivestreamState</code> |
 
 <a name="module_RTKLivestream--module.exports+start"></a>
 
 #### module.exports.start([livestreamConfig])
+
 Starts livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
 
-| Param | Type |
-| --- | --- |
-| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> | 
+| Param              | Type                                  |
+| ------------------ | ------------------------------------- |
+| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> |
 
 <a name="module_RTKLivestream--module.exports+stop"></a>
 
 #### module.exports.stop()
+
 Stops livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
index 8a3447521dfd9b2..9752ca8616beba0 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
@@ -10,51 +10,54 @@ web_core_version: 1.2.4
 
 This consists of the metadata of the meeting, such as the room name and the title.
 
-
-* [RTKMeta](#module_RTKMeta)
-    * [module.exports](#exp_module_RTKMeta--module.exports) ⏏
-        * [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
-        * [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
-        * [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
-        * [.viewType](#module_RTKMeta--module.exports+viewType)
-        * [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
-        * [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
-        * [.sessionId](#module_RTKMeta--module.exports+sessionId)
-        * [.meetingId](#module_RTKMeta--module.exports+meetingId)
-        * [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
-        * [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
+- [RTKMeta](#module_RTKMeta)
+  - [module.exports](#exp_module_RTKMeta--module.exports) ⏏
+    - [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
+    - [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
+    - [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
+    - [.viewType](#module_RTKMeta--module.exports+viewType)
+    - [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
+    - [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
+    - [.sessionId](#module_RTKMeta--module.exports+sessionId)
+    - [.meetingId](#module_RTKMeta--module.exports+meetingId)
+    - [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
+    - [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
 
 <a name="exp_module_RTKMeta--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKMeta--module.exports_new"></a>
 
 #### new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| viewType | <code>string</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
-| meetingTitle | <code>string</code> | 
+| Param             | Type                           |
+| ----------------- | ------------------------------ |
+| context           | <code>Context</code>           |
+| self              | <code>Self</code>              |
+| viewType          | <code>string</code>            |
+| roomSocketHandler | <code>RoomSocketHandler</code> |
+| meetingTitle      | <code>string</code>            |
 
 <a name="module_RTKMeta--module.exports+selfActiveTab"></a>
 
 #### module.exports.selfActiveTab
+
 Represents the current active tab
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+broadcastTabChanges"></a>
 
 #### module.exports.broadcastTabChanges
+
 Represents whether current user is spotlighted
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+viewType"></a>
 
 #### module.exports.viewType
+
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -62,47 +65,52 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKMeta--module.exports+meetingStartedTimestamp"></a>
 
 #### module.exports.meetingStartedTimestamp
+
 The timestamp of the time when the meeting started.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingTitle"></a>
 
 #### module.exports.meetingTitle
+
 The title of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+sessionId"></a>
 
 #### module.exports.sessionId
+
 (Experimental) The sessionId this meeting object is part of.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingId"></a>
 
 #### module.exports.meetingId
+
 The room name of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+setBroadcastTabChanges"></a>
 
 #### module.exports.setBroadcastTabChanges(broadcastTabChanges)
+
 Sets current user as broadcasting tab changes
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
 
-| Param | Type |
-| --- | --- |
-| broadcastTabChanges | <code>boolean</code> | 
+| Param               | Type                 |
+| ------------------- | -------------------- |
+| broadcastTabChanges | <code>boolean</code> |
 
 <a name="module_RTKMeta--module.exports+setSelfActiveTab"></a>
 
 #### module.exports.setSelfActiveTab(spotlightTab, tabChangeSource)
-Sets current active tab for user
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+Sets current active tab for user
 
-| Param | Type |
-| --- | --- |
-| spotlightTab | <code>ActiveTab</code> | 
-| tabChangeSource | <code>TabChangeSource</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| spotlightTab    | <code>ActiveTab</code>       |
+| tabChangeSource | <code>TabChangeSource</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
index 5ab88c872e965cd..12a5b874df4f649 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
@@ -11,68 +11,72 @@ web_core_version: 1.2.4
 This module represents a single participant in the meeting.
 The participant object can be accessed from one of the participant lists
 present in the `meeting.participants` object. For example,
+
 ```ts
 const participant1 = meeting.participants.active.get(participantId);
 const participant2 = meeting.participants.joined.get(participantId);
 const participant3 = meeting.participants.active.toArray()[0];
-const participant4 = meeting.participants.active.toArray().filter((p) => p.name === 'John');
+const participant4 = meeting.participants.active
+	.toArray()
+	.filter((p) => p.name === "John");
 ```
 
-
-* [RTKParticipant](#module_RTKParticipant)
-    * [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
-        * [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
-        * [.id](#module_RTKParticipant--module.exports+id)
-        * [.userId](#module_RTKParticipant--module.exports+userId)
-        * [.name](#module_RTKParticipant--module.exports+name)
-        * [.picture](#module_RTKParticipant--module.exports+picture)
-        * [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
-        * ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
-        * [.device](#module_RTKParticipant--module.exports+device)
-        * [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
-        * [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
-        * [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
-        * [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
-        * [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
-        * [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
-        * [.producers](#module_RTKParticipant--module.exports+producers)
-        * [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
-        * [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
-        * [.presetName](#module_RTKParticipant--module.exports+presetName)
-        * [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
-        * [.telemetry](#module_RTKParticipant--module.exports+telemetry)
-        * [.isPinned](#module_RTKParticipant--module.exports+isPinned)
-        * [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
-        * [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
-        * [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
-        * [.pin()](#module_RTKParticipant--module.exports+pin)
-        * [.unpin()](#module_RTKParticipant--module.exports+unpin)
-        * [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
-        * [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
-        * [.kick()](#module_RTKParticipant--module.exports+kick)
-        * [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
-        * [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
-        * [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
-        * [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
+- [RTKParticipant](#module_RTKParticipant)
+  - [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
+    - [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
+    - [.id](#module_RTKParticipant--module.exports+id)
+    - [.userId](#module_RTKParticipant--module.exports+userId)
+    - [.name](#module_RTKParticipant--module.exports+name)
+    - [.picture](#module_RTKParticipant--module.exports+picture)
+    - [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
+    - ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
+    - [.device](#module_RTKParticipant--module.exports+device)
+    - [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
+    - [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
+    - [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
+    - [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
+    - [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
+    - [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
+    - [.producers](#module_RTKParticipant--module.exports+producers)
+    - [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
+    - [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
+    - [.presetName](#module_RTKParticipant--module.exports+presetName)
+    - [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
+    - [.telemetry](#module_RTKParticipant--module.exports+telemetry)
+    - [.isPinned](#module_RTKParticipant--module.exports+isPinned)
+    - [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
+    - [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
+    - [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
+    - [.pin()](#module_RTKParticipant--module.exports+pin)
+    - [.unpin()](#module_RTKParticipant--module.exports+unpin)
+    - [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
+    - [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
+    - [.kick()](#module_RTKParticipant--module.exports+kick)
+    - [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
+    - [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
+    - [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
+    - [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
 
 <a name="exp_module_RTKParticipant--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipant--module.exports_new"></a>
 
 #### new module.exports(context, participant, self, roomSocket)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| participant | <code>IRTKParticipant</code> | 
-| self | <code>Self</code> | 
-| roomSocket | <code>RoomSocketHandler</code> | 
+| Param       | Type                           |
+| ----------- | ------------------------------ |
+| context     | <code>Context</code>           |
+| participant | <code>IRTKParticipant</code>   |
+| self        | <code>Self</code>              |
+| roomSocket  | <code>RoomSocketHandler</code> |
 
 <a name="module_RTKParticipant--module.exports+id"></a>
 
 #### module.exports.id
+
 The peer ID of the participant.
 The participants are indexed by this ID in the participant map.
 
@@ -80,148 +84,171 @@ The participants are indexed by this ID in the participant map.
 <a name="module_RTKParticipant--module.exports+userId"></a>
 
 #### module.exports.userId
+
 The user ID of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+name"></a>
 
 #### module.exports.name
+
 The name of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+picture"></a>
 
 #### module.exports.picture
+
 The picture of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+customRTKParticipantId"></a>
 
 #### module.exports.customRTKParticipantId
+
 The custom id of the participant set during Add RTKParticipant REST API
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+clientSpecificId"></a>
 
 #### ~~module.exports.clientSpecificId~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+device"></a>
 
 #### module.exports.device
+
 The device configuration of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoTrack"></a>
 
 #### module.exports.videoTrack
+
 The participant's video track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioTrack"></a>
 
 #### module.exports.audioTrack
+
 The participant's audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareTracks"></a>
 
 #### module.exports.screenShareTracks
+
 The participant's screenshare video and audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoEnabled"></a>
 
 #### module.exports.videoEnabled
+
 This is true if the participant's video is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioEnabled"></a>
 
 #### module.exports.audioEnabled
+
 This is true if the participant's audio is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareEnabled"></a>
 
 #### module.exports.screenShareEnabled
+
 This is true if the participant is screensharing.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+producers"></a>
 
 #### module.exports.producers
+
 producers created by participant
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+manualProducerConfig"></a>
 
 #### module.exports.manualProducerConfig
+
 producer config passed during manual subscription
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+supportsRemoteControl"></a>
 
 #### module.exports.supportsRemoteControl
+
 This is true if the participant supports remote control.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+presetName"></a>
 
 #### module.exports.presetName
+
 The preset of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+stageStatus"></a>
 
 #### module.exports.stageStatus
+
 Denotes the participants's current stage status.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+isPinned"></a>
 
 #### module.exports.isPinned
+
 Returns true if the participant is pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+setVideoEnabled"></a>
 
 #### module.exports.setVideoEnabled(videoEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| videoEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param        | Type                 | Default           |
+| ------------ | -------------------- | ----------------- |
+| videoEnabled | <code>boolean</code> |                   |
+| [emitEvent]  | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+setAudioEnabled"></a>
 
 #### module.exports.setAudioEnabled(audioEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| audioEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param        | Type                 | Default           |
+| ------------ | -------------------- | ----------------- |
+| audioEnabled | <code>boolean</code> |                   |
+| [emitEvent]  | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+setScreenShareEnabled"></a>
 
 #### module.exports.setScreenShareEnabled(screenShareEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| screenShareEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param              | Type                 | Default           |
+| ------------------ | -------------------- | ----------------- |
+| screenShareEnabled | <code>boolean</code> |                   |
+| [emitEvent]        | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+pin"></a>
 
 #### module.exports.pin()
+
 Returns `participant.id` if user has permission
 to pin participants.
 
@@ -229,6 +256,7 @@ to pin participants.
 <a name="module_RTKParticipant--module.exports+unpin"></a>
 
 #### module.exports.unpin()
+
 Returns `participant.id` if user has permission
 to unpin participants.
 
@@ -236,16 +264,18 @@ to unpin participants.
 <a name="module_RTKParticipant--module.exports+setIsPinned"></a>
 
 #### module.exports.setIsPinned(isPinned, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| isPinned | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param       | Type                 | Default           |
+| ----------- | -------------------- | ----------------- |
+| isPinned    | <code>boolean</code> |                   |
+| [emitEvent] | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+disableAudio"></a>
 
 #### module.exports.disableAudio()
+
 Disables audio for this participant.
 Requires the permission to disable participant audio.
 
@@ -253,6 +283,7 @@ Requires the permission to disable participant audio.
 <a name="module_RTKParticipant--module.exports+kick"></a>
 
 #### module.exports.kick()
+
 Kicks this participant from the meeting.
 Requires the permission to kick a participant.
 
@@ -260,6 +291,7 @@ Requires the permission to kick a participant.
 <a name="module_RTKParticipant--module.exports+disableVideo"></a>
 
 #### module.exports.disableVideo()
+
 Disables video for this participant.
 Requires the permission to disable video for a participant.
 
@@ -267,29 +299,31 @@ Requires the permission to disable video for a participant.
 <a name="module_RTKParticipant--module.exports+registerVideoElement"></a>
 
 #### module.exports.registerVideoElement(videoElem)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| videoElem | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param     | Type                          |
+| --------- | ----------------------------- |
+| videoElem | <code>HTMLVideoElement</code> |
 
 <a name="module_RTKParticipant--module.exports+deregisterVideoElement"></a>
 
 #### module.exports.deregisterVideoElement([videoElem])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| [videoElem] | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param       | Type                          |
+| ----------- | ----------------------------- |
+| [videoElem] | <code>HTMLVideoElement</code> |
 
 <a name="module_RTKParticipant--module.exports+updateVideo"></a>
 
 #### module.exports.updateVideo(e)
-Internal method, do not use
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
+Internal method, do not use
 
-| Param | Type |
-| --- | --- |
-| e | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
 
+| Param | Type                          |
+| ----- | ----------------------------- |
+| e     | <code>HTMLVideoElement</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
index f10720836d026ca..c894fa0a1e8958c 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
@@ -14,55 +14,57 @@ For example, when a participant is added to this map, a `participantJoined` even
 emitted from the map. When a participant object emits an event `videoUpdate`, the map
 re-emits that event (provided the participant is present in the map).
 
-
-* [RTKParticipantMap](#module_RTKParticipantMap)
-    * [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
-        * [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
-        * [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
-        * [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
-        * [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
+- [RTKParticipantMap](#module_RTKParticipantMap)
+  - [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
+    - [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
+    - [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
+    - [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
+    - [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
 
 <a name="exp_module_RTKParticipantMap--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipantMap--module.exports_new"></a>
 
 #### new module.exports(logger, [options])
 
-| Param | Type |
-| --- | --- |
-| logger | <code>Logger</code> | 
-| [options] | <code>MapEvents</code> | 
+| Param     | Type                   |
+| --------- | ---------------------- |
+| logger    | <code>Logger</code>    |
+| [options] | <code>MapEvents</code> |
 
 <a name="module_RTKParticipantMap--module.exports+add"></a>
 
 #### module.exports.add(participant, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| participant | <code>T</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+
+| Param       | Type                 | Default           |
+| ----------- | -------------------- | ----------------- |
+| participant | <code>T</code>       |                   |
+| [emitEvent] | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipantMap--module.exports+clear"></a>
 
 #### module.exports.clear([emitEvent], [removeListeners])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
-| [removeListeners] | <code>boolean</code> | <code>false</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+
+| Param             | Type                 | Default            |
+| ----------------- | -------------------- | ------------------ |
+| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
+| [removeListeners] | <code>boolean</code> | <code>false</code> |
 
 <a name="module_RTKParticipantMap--module.exports+delete"></a>
 
 #### module.exports.delete(participantId, [emitEvent], [removeListeners])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| participantId | <code>string</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
-| [removeListeners] | <code>boolean</code> | <code>false</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
 
+| Param             | Type                 | Default            |
+| ----------------- | -------------------- | ------------------ |
+| participantId     | <code>string</code>  |                    |
+| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
+| [removeListeners] | <code>boolean</code> | <code>false</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
index 6cc9cfa343f6be8..85f7c46ef94b31e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
@@ -10,106 +10,114 @@ web_core_version: 1.2.4
 
 This module represents all the participants in the meeting (except the local user).
 It consists of 4 maps:
+
 - `joined`: A map of all participants that have joined the meeting.
 - `waitlisted`: A map of all participants that have been added to the waitlist.
 - `active`: A map of active participants who should be displayed in the meeting grid.
 - `pinned`: A map of pinned participants.
 
-
 * [RTKParticipants](#module_RTKParticipants)
-    * [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
-        * [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
-        * [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
-        * [.joined](#module_RTKParticipants--module.exports+joined)
-        * ~~[.active](#module_RTKParticipants--module.exports+active)~~
-        * [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
-        * [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
-        * [.pinned](#module_RTKParticipants--module.exports+pinned)
-        * [.all](#module_RTKParticipants--module.exports+all)
-        * [.pip](#module_RTKParticipants--module.exports+pip)
-        * [.telemetry](#module_RTKParticipants--module.exports+telemetry)
-        * [.viewMode](#module_RTKParticipants--module.exports+viewMode)
-        * [.currentPage](#module_RTKParticipants--module.exports+currentPage)
-        * [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
-        * [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
-        * [.count](#module_RTKParticipants--module.exports+count)
-        * [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
-        * [.pageCount](#module_RTKParticipants--module.exports+pageCount)
-        * [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
-        * [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
-        * [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
-        * [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
-        * [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
-        * [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
-        * [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
-        * [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
-        * [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
-        * [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
-        * ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
-        * ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
-        * ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
-        * [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
-        * [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
-        * [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
-        * [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
+  - [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
+    - [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
+    - [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
+    - [.joined](#module_RTKParticipants--module.exports+joined)
+    - ~~[.active](#module_RTKParticipants--module.exports+active)~~
+    - [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
+    - [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
+    - [.pinned](#module_RTKParticipants--module.exports+pinned)
+    - [.all](#module_RTKParticipants--module.exports+all)
+    - [.pip](#module_RTKParticipants--module.exports+pip)
+    - [.telemetry](#module_RTKParticipants--module.exports+telemetry)
+    - [.viewMode](#module_RTKParticipants--module.exports+viewMode)
+    - [.currentPage](#module_RTKParticipants--module.exports+currentPage)
+    - [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
+    - [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
+    - [.count](#module_RTKParticipants--module.exports+count)
+    - [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
+    - [.pageCount](#module_RTKParticipants--module.exports+pageCount)
+    - [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
+    - [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
+    - [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
+    - [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
+    - [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
+    - [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
+    - [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
+    - [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
+    - [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
+    - [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
+    - ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
+    - ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
+    - ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
+    - [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
+    - [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
+    - [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
+    - [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
 
 <a name="exp_module_RTKParticipants--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipants--module.exports_new"></a>
 
 #### new module.exports(context, self, roomSocketHandler)
+
 This constructs a new Participant object and maintains
 the maps of active/joined/waitlisted/pinned/selectedPeers maps.
 self : Self
 
-
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| Param             | Type                           |
+| ----------------- | ------------------------------ |
+| context           | <code>Context</code>           |
+| self              | <code>Self</code>              |
+| roomSocketHandler | <code>RoomSocketHandler</code> |
 
 <a name="module_RTKParticipants--module.exports+waitlisted"></a>
 
 #### module.exports.waitlisted
+
 Returns a list of participants waiting to join the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+joined"></a>
 
 #### module.exports.joined
+
 Returns a list of all participants in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+active"></a>
 
 #### ~~module.exports.active~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+videoSubscribed"></a>
 
 #### module.exports.videoSubscribed
+
 Returns a list of participants whose video streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+audioSubscribed"></a>
 
 #### module.exports.audioSubscribed
+
 Returns a list of participants whose audio streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+pinned"></a>
 
 #### module.exports.pinned
+
 Returns a list of participants who have been pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+all"></a>
 
 #### module.exports.all
+
 Returns all added participants irrespective of whether they are currently
 in the meeting or not
 
@@ -117,16 +125,19 @@ in the meeting or not
 <a name="module_RTKParticipants--module.exports+pip"></a>
 
 #### module.exports.pip
+
 Return the controls for Picture-in-Picture
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+viewMode"></a>
 
 #### module.exports.viewMode
+
 Indicates whether the meeting is in 'ACTIVE_GRID' mode or 'PAGINATED' mode.
 
 In 'ACTIVE_GRID' mode, participants are populated in the participants.active map
@@ -141,6 +152,7 @@ changed by the user using setPage(page).
 <a name="module_RTKParticipants--module.exports+currentPage"></a>
 
 #### module.exports.currentPage
+
 This indicates the current page that has been set by the user in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -148,24 +160,28 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+lastActiveSpeaker"></a>
 
 #### module.exports.lastActiveSpeaker
+
 This stores the `participantId` of the last participant who spoke in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+selectedPeers"></a>
 
 #### module.exports.selectedPeers
+
 Keeps a list of all participants who have been present in the selected peers list.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+count"></a>
 
 #### module.exports.count
+
 Returns the number of participants who are joined in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount"></a>
 
 #### module.exports.maxActiveRTKParticipantsCount
+
 Returns the maximum number of participants that can be present in
 the active map.
 
@@ -173,6 +189,7 @@ the active map.
 <a name="module_RTKParticipants--module.exports+pageCount"></a>
 
 #### module.exports.pageCount
+
 Returns the number of pages that are available in the meeting in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -180,187 +197,204 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount"></a>
 
 #### module.exports.setMaxActiveRTKParticipantsCount(limit)
+
 Updates the maximum number of participants that are populated in
 the active map.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param | Type                | Description       |
+| ----- | ------------------- | ----------------- |
 | limit | <code>number</code> | Updated max limit |
 
 <a name="module_RTKParticipants--module.exports+acceptWaitingRoomRequest"></a>
 
 #### module.exports.acceptWaitingRoomRequest(id)
+
 Accepts requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | peerId or userId of the waitlisted participant. |
+| Param | Type                | Description                                     |
+| ----- | ------------------- | ----------------------------------------------- |
+| id    | <code>string</code> | peerId or userId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest"></a>
 
 #### module.exports.acceptAllWaitingRoomRequest(userIds)
+
 We need a new event for socket service events
 since if we send them all together, sequence of events
 can be unreliable
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type |
-| --- | --- |
-| userIds | <code>Array.&lt;string&gt;</code> | 
+| Param   | Type                              |
+| ------- | --------------------------------- |
+| userIds | <code>Array.&lt;string&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+rejectWaitingRoomRequest"></a>
 
 #### module.exports.rejectWaitingRoomRequest(id)
+
 Rejects requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | participantId of the waitlisted participant. |
+| Param | Type                | Description                                  |
+| ----- | ------------------- | -------------------------------------------- |
+| id    | <code>string</code> | participantId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+setViewMode"></a>
 
 #### module.exports.setViewMode(viewMode)
+
 Sets the view mode of the meeting to either ACTIVE_GRID or PAGINATED.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param    | Type                  | Description                                          |
+| -------- | --------------------- | ---------------------------------------------------- |
 | viewMode | <code>ViewMode</code> | The mode in which the active map should be populated |
 
 <a name="module_RTKParticipants--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(peerIds, [kinds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerIds | <code>Array.&lt;string&gt;</code> | 
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+
+| Param   | Type                                                                                                                          |
+| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(peerIds, [kinds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerIds | <code>Array.&lt;string&gt;</code> | 
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+
+| Param   | Type                                                                                                                          |
+| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+setPage"></a>
 
 #### module.exports.setPage(page)
+
 Populates the active map with participants present in the page number
 indicated by the parameter `page` in PAGINATED mode.
 Does not do anything in ACTIVE_GRID mode.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| page | <code>number</code> | The page number to be set. |
+| Param | Type                | Description                |
+| ----- | ------------------- | -------------------------- |
+| page  | <code>number</code> | The page number to be set. |
 
 <a name="module_RTKParticipants--module.exports+disableAllAudio"></a>
 
 #### module.exports.disableAllAudio(allowUnmute)
+
 Disables audio for all participants in the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param       | Type                 | Description                                        |
+| ----------- | -------------------- | -------------------------------------------------- |
 | allowUnmute | <code>boolean</code> | Allow participants to unmute after they are muted. |
 
 <a name="module_RTKParticipants--module.exports+disableAllVideo"></a>
 
 #### module.exports.disableAllVideo()
+
 Disables video for all participants in the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+disableAudio"></a>
 
 #### ~~module.exports.disableAudio(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                    |
+| ------------- | ------------------- | ------------------------------ |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+disableVideo"></a>
 
 #### ~~module.exports.disableVideo(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                    |
+| ------------- | ------------------- | ------------------------------ |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+kick"></a>
 
 #### ~~module.exports.kick(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                     |
+| ------------- | ------------------- | ------------------------------- |
 | participantId | <code>string</code> | ID of participant to be kicked. |
 
 <a name="module_RTKParticipants--module.exports+kickAll"></a>
 
 #### module.exports.kickAll()
+
 Kicks all participants from the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+broadcastMessage"></a>
 
 #### module.exports.broadcastMessage(type, payload, target)
+
 Broadcasts the message to participants
 
 If no `target` is specified it is sent to all participants including `self`.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| type | <code>string</code> |  |
-| payload | <code>BroadcastMessagePayload</code> |  |
-| target | <code>BroadcastMessageTarget</code> | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
+| Param   | Type                                 | Description                                                                                                                           |
+| ------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
+| type    | <code>string</code>                  |                                                                                                                                       |
+| payload | <code>BroadcastMessagePayload</code> |                                                                                                                                       |
+| target  | <code>BroadcastMessageTarget</code>  | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
 
 <a name="module_RTKParticipants--module.exports+getAllJoinedPeers"></a>
 
 #### module.exports.getAllJoinedPeers(searchQuery, limit, offset)
+
 Returns all peers currently present in the room
 If you are in a group call, use `meeting.participants.joined`
 instead
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type |
-| --- | --- |
-| searchQuery | <code>string</code> | 
-| limit | <code>number</code> | 
-| offset | <code>number</code> | 
+| Param       | Type                |
+| ----------- | ------------------- |
+| searchQuery | <code>string</code> |
+| limit       | <code>number</code> |
+| offset      | <code>number</code> |
 
 <a name="module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin"></a>
 
 #### module.exports.getRTKParticipantsInMeetingPreJoin()
+
 Returns all peers currently in the room, is a non paginated call
 and should only be used if you are in a non room joined state,
 if in a joined group call, use `meeting.participants.joined`
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
index e8da972e0b7c931..ac3f6c4b61d2b82 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
@@ -10,52 +10,52 @@ web_core_version: 1.2.4
 
 The PermissionPreset class represents the meeting permissions for the current participant
 
-
-* [PermissionPreset](#module_PermissionPreset)
-    * _instance_
-        * [.stageEnabled](#module_PermissionPreset+stageEnabled)
-        * [.stageAccess](#module_PermissionPreset+stageAccess)
-        * [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
-        * [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
-        * [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
-        * [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
-        * [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
-        * [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
-        * [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
-        * [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
-        * [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
-        * [.kickParticipant](#module_PermissionPreset+kickParticipant)
-        * [.pinParticipant](#module_PermissionPreset+pinParticipant)
-        * [.canRecord](#module_PermissionPreset+canRecord)
-        * ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
-        * [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
-        * [.plugins](#module_PermissionPreset+plugins)
-        * [.polls](#module_PermissionPreset+polls)
-        * ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
-        * ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
-        * [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
-        * ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
-        * [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
-        * ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
-        * [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
-        * [.chatPublic](#module_PermissionPreset+chatPublic)
-        * [.chatPrivate](#module_PermissionPreset+chatPrivate)
-        * [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
-        * [.showParticipantList](#module_PermissionPreset+showParticipantList)
-        * ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
-        * [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
-        * ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
-        * ~~[.canPresent](#module_PermissionPreset+canPresent)~~
-        * ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
-        * ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
-        * [.canLivestream](#module_PermissionPreset+canLivestream)
-    * _static_
-        * [.fromResponse()](#module_PermissionPreset.fromResponse)
-        * [.default()](#module_PermissionPreset.default)
+- [PermissionPreset](#module_PermissionPreset)
+  - _instance_
+    - [.stageEnabled](#module_PermissionPreset+stageEnabled)
+    - [.stageAccess](#module_PermissionPreset+stageAccess)
+    - [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
+    - [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
+    - [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
+    - [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
+    - [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
+    - [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
+    - [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
+    - [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
+    - [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
+    - [.kickParticipant](#module_PermissionPreset+kickParticipant)
+    - [.pinParticipant](#module_PermissionPreset+pinParticipant)
+    - [.canRecord](#module_PermissionPreset+canRecord)
+    - ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
+    - [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
+    - [.plugins](#module_PermissionPreset+plugins)
+    - [.polls](#module_PermissionPreset+polls)
+    - ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
+    - ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
+    - [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
+    - ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
+    - [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
+    - ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
+    - [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
+    - [.chatPublic](#module_PermissionPreset+chatPublic)
+    - [.chatPrivate](#module_PermissionPreset+chatPrivate)
+    - [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
+    - [.showParticipantList](#module_PermissionPreset+showParticipantList)
+    - ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
+    - [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
+    - ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
+    - ~~[.canPresent](#module_PermissionPreset+canPresent)~~
+    - ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
+    - ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
+    - [.canLivestream](#module_PermissionPreset+canLivestream)
+  - _static_
+    - [.fromResponse()](#module_PermissionPreset.fromResponse)
+    - [.default()](#module_PermissionPreset.default)
 
 <a name="module_PermissionPreset+stageEnabled"></a>
 
 ### meeting.self.permissions.stageEnabled
+
 The `stageEnabled` property returns a boolean value.
 If `true`, stage management is available for the participant.
 
@@ -63,6 +63,7 @@ If `true`, stage management is available for the participant.
 <a name="module_PermissionPreset+stageAccess"></a>
 
 ### meeting.self.permissions.stageAccess
+
 The `stageAccess` property dictates how a user interacts with the stage.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 
@@ -70,6 +71,7 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 <a name="module_PermissionPreset+acceptWaitingRequests"></a>
 
 ### meeting.self.permissions.acceptWaitingRequests
+
 The `acceptWaitingRequests` returns boolean value.
 If `true`, participant can accept the request of waiting participant.
 
@@ -77,6 +79,7 @@ If `true`, participant can accept the request of waiting participant.
 <a name="module_PermissionPreset+requestProduceVideo"></a>
 
 ### meeting.self.permissions.requestProduceVideo
+
 The `requestProduceVideo` returns boolean value.
 If `true`, participant can send request to participants
 about producing video.
@@ -85,6 +88,7 @@ about producing video.
 <a name="module_PermissionPreset+requestProduceAudio"></a>
 
 ### meeting.self.permissions.requestProduceAudio
+
 The `requestProduceAudio` returns boolean value.
 If `true`, participant can send request to participants
 about producing audio.
@@ -93,6 +97,7 @@ about producing audio.
 <a name="module_PermissionPreset+requestProduceScreenshare"></a>
 
 ### meeting.self.permissions.requestProduceScreenshare
+
 The `requestProduceScreenshare` returns boolean value.
 If `true`, participant can send request to participants
 about sharing screen.
@@ -101,6 +106,7 @@ about sharing screen.
 <a name="module_PermissionPreset+canAllowParticipantAudio"></a>
 
 ### meeting.self.permissions.canAllowParticipantAudio
+
 The `canAllowParticipantAudio` returns boolean value.
 If `true`, participant can enable other participants` audio.
 
@@ -108,6 +114,7 @@ If `true`, participant can enable other participants` audio.
 <a name="module_PermissionPreset+canAllowParticipantScreensharing"></a>
 
 ### meeting.self.permissions.canAllowParticipantScreensharing
+
 The `canAllowParticipantScreensharing` returns boolean value.
 If `true`, participant can enable other participants` screen share.
 
@@ -115,6 +122,7 @@ If `true`, participant can enable other participants` screen share.
 <a name="module_PermissionPreset+canAllowParticipantVideo"></a>
 
 ### meeting.self.permissions.canAllowParticipantVideo
+
 The `canAllowParticipantVideo` returns boolean value.
 If `true`, participant can enable other participants` video.
 
@@ -122,18 +130,21 @@ If `true`, participant can enable other participants` video.
 <a name="module_PermissionPreset+canDisableParticipantAudio"></a>
 
 ### meeting.self.permissions.canDisableParticipantAudio
+
 If `true`, a participant can disable other participants` audio.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canDisableParticipantVideo"></a>
 
 ### meeting.self.permissions.canDisableParticipantVideo
+
 If `true`, a participant can disable other participants` video.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+kickParticipant"></a>
 
 ### meeting.self.permissions.kickParticipant
+
 The `kickParticipant` returns boolean value.
 If `true`, participant can remove other participants from the meeting.
 
@@ -141,6 +152,7 @@ If `true`, participant can remove other participants from the meeting.
 <a name="module_PermissionPreset+pinParticipant"></a>
 
 ### meeting.self.permissions.pinParticipant
+
 The `pinParticipant` returns boolean value.
 If `true`, participant can pin a participant in the meeting.
 
@@ -148,6 +160,7 @@ If `true`, participant can pin a participant in the meeting.
 <a name="module_PermissionPreset+canRecord"></a>
 
 ### meeting.self.permissions.canRecord
+
 The `canRecord` returns boolean value.
 If `true`, participant can record the meeting.
 
@@ -155,12 +168,14 @@ If `true`, participant can record the meeting.
 <a name="module_PermissionPreset+waitingRoomType"></a>
 
 ### ~~meeting.self.permissions.waitingRoomType~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+waitingRoomBehaviour"></a>
 
 ### meeting.self.permissions.waitingRoomBehaviour
+
 The `waitingRoomType` returns string value.
 type of waiting room behavior
 possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
@@ -169,6 +184,7 @@ possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
 <a name="module_PermissionPreset+plugins"></a>
 
 ### meeting.self.permissions.plugins
+
 The `plugins` tells if the participant can act on plugins
 there are 2 permissions with boolean values, `canStart` and `canClose`.
 
@@ -176,6 +192,7 @@ there are 2 permissions with boolean values, `canStart` and `canClose`.
 <a name="module_PermissionPreset+polls"></a>
 
 ### meeting.self.permissions.polls
+
 The `polls` tells if the participant can use polls.
 There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewResults`
 
@@ -183,18 +200,21 @@ There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewRes
 <a name="module_PermissionPreset+produceVideo"></a>
 
 ### ~~meeting.self.permissions.produceVideo~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+requestProduce"></a>
 
 ### ~~meeting.self.permissions.requestProduce~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceVideo"></a>
 
 ### meeting.self.permissions.canProduceVideo
+
 The `canProduceVideo` shows permissions for enabling video.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -202,12 +222,14 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceScreenshare"></a>
 
 ### ~~meeting.self.permissions.produceScreenshare~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceScreenshare"></a>
 
 ### meeting.self.permissions.canProduceScreenshare
+
 The `canProduceScreenshare` shows permissions for sharing screen.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -215,12 +237,14 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceAudio"></a>
 
 ### ~~meeting.self.permissions.produceAudio~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceAudio"></a>
 
 ### meeting.self.permissions.canProduceAudio
+
 The `canProduceAudio` shows permissions for enabling audio.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -228,6 +252,7 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+chatPublic"></a>
 
 ### meeting.self.permissions.chatPublic
+
 The `chatPublic` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send chat
@@ -238,6 +263,7 @@ there are 4 permissions
 <a name="module_PermissionPreset+chatPrivate"></a>
 
 ### meeting.self.permissions.chatPrivate
+
 The `chatPrivate` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send private chat
@@ -249,6 +275,7 @@ there are 4 permissions
 <a name="module_PermissionPreset+hiddenParticipant"></a>
 
 ### meeting.self.permissions.hiddenParticipant
+
 The `hiddenParticipant` returns boolean value.
 If `true`, participant is hidden.
 
@@ -256,6 +283,7 @@ If `true`, participant is hidden.
 <a name="module_PermissionPreset+showParticipantList"></a>
 
 ### meeting.self.permissions.showParticipantList
+
 The `showParticipantList` returns boolean value.
 If `true`, participant list can be shown to the participant.
 
@@ -263,12 +291,14 @@ If `true`, participant list can be shown to the participant.
 <a name="module_PermissionPreset+canChangeParticipantRole"></a>
 
 ### ~~meeting.self.permissions.canChangeParticipantRole~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canChangeParticipantPermissions"></a>
 
 ### meeting.self.permissions.canChangeParticipantPermissions
+
 The `canChangeParticipantPermissions` returns boolean value.
 If `true`, allow changing the participants' permissions.
 
@@ -276,40 +306,47 @@ If `true`, allow changing the participants' permissions.
 <a name="module_PermissionPreset+canChangeTheme"></a>
 
 ### ~~meeting.self.permissions.canChangeTheme~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canPresent"></a>
 
 ### ~~meeting.self.permissions.canPresent~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+acceptPresentRequests"></a>
 
 ### ~~meeting.self.permissions.acceptPresentRequests~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+maxScreenShareCount"></a>
 
 ### ~~meeting.self.permissions.maxScreenShareCount~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canLivestream"></a>
 
 ### meeting.self.permissions.canLivestream
+
 Livestream
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset.fromResponse"></a>
 
 ### meeting.self.permissions.fromResponse()
+
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 **Deprecated.**: Use init()  
 <a name="module_PermissionPreset.default"></a>
 
 ### meeting.self.permissions.default()
+
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
-**Deprecated.**: Use init()  
+**Deprecated.**: Use init()
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
index 72747a12f6bdcac..6cb2dd696a9ff5f 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
@@ -46,76 +46,76 @@ Code from ui-kit. Same method used in the avatar component
 **Kind**: global function  
 <a name="_init"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
+| self    | <code>Self</code>    |
 
 <a name="init"></a>
 
 Initialize PiP and prepare sources
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| [options] | <code>Object</code> | 
-| [options.height] | <code>number</code> | 
-| [options.width] | <code>number</code> | 
+| Param            | Type                |
+| ---------------- | ------------------- |
+| [options]        | <code>Object</code> |
+| [options.height] | <code>number</code> |
+| [options.width]  | <code>number</code> |
 
 <a name="disableSource"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| source | <code>string</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| source | <code>string</code> |
 
 <a name="addSource"></a>
 
 Add a video source from the participant grid
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | id for the source (ex. participant id) |
-| element | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source |
-| enabled | <code>boolean</code> | if source is enabled |
-| [displayText] | <code>string</code> | two character display text |
+| Param         | Type                          | Description                            |
+| ------------- | ----------------------------- | -------------------------------------- |
+| id            | <code>string</code>           | id for the source (ex. participant id) |
+| element       | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source  |
+| enabled       | <code>boolean</code>          | if source is enabled                   |
+| [displayText] | <code>string</code>           | two character display text             |
 
 <a name="updateSource"></a>
 
 Update a video source
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| id | <code>string</code> | 
-| source | <code>any</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| id     | <code>string</code> |
+| source | <code>any</code>    |
 
 <a name="removeSource"></a>
 
 Remove the video source for the participant
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Description |
-| --- | --- |
-| id | id for the source (ex. participant id) |
+| Param | Description                            |
+| ----- | -------------------------------------- |
+| id    | id for the source (ex. participant id) |
 
 <a name="removePinnedSource"></a>
 
 Remove the pinned source
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Description |
-| --- | --- |
-| id | id for the source (ex. participant id) |
+| Param | Description                            |
+| ----- | -------------------------------------- |
+| id    | id for the source (ex. participant id) |
 
 <a name="removeAllSources"></a>
 
@@ -126,4 +126,4 @@ Remove all sources
 
 Enable PiP
 
-**Kind**: global function  
+**Kind**: global function
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
index 68d9b48f76fb51b..1dc5407b42362d4 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
@@ -11,145 +11,159 @@ web_core_version: 1.2.4
 The RTKPlugin module represents a single plugin in the meeting.
 A plugin can be obtained from one of the plugin arrays in `meeting.plugins`.
 For example,
+
 ```ts
 const plugin1 = meeting.plugins.active.get(pluginId);
 const plugin2 = meeting.plugins.all.get(pluginId);
 ```
 
-
-* [RTKPlugin](#module_RTKPlugin)
-    * [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
-        * [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
-        * [.telemetry](#module_RTKPlugin--module.exports+telemetry)
-        * [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
-        * [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
-        * [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
-        * [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
-        * [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
-        * [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
-        * [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
-        * [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
-        * ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
-        * ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
-        * [.activate()](#module_RTKPlugin--module.exports+activate)
-        * [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
+- [RTKPlugin](#module_RTKPlugin)
+  - [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
+    - [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
+    - [.telemetry](#module_RTKPlugin--module.exports+telemetry)
+    - [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
+    - [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
+    - [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
+    - [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
+    - [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
+    - [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
+    - [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
+    - [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
+    - ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
+    - ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
+    - [.activate()](#module_RTKPlugin--module.exports+activate)
+    - [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
 
 <a name="exp_module_RTKPlugin--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKPlugin--module.exports_new"></a>
 
 #### new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| plugin | <code>RTKPluginResponse</code> | 
-| pluginSocketHandler | <code>RTKPluginSocketHandler</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
-| chat | <code>Chat</code> | 
-| meetingTitle | <code>string</code> | 
+| Param               | Type                                |
+| ------------------- | ----------------------------------- |
+| context             | <code>Context</code>                |
+| plugin              | <code>RTKPluginResponse</code>      |
+| pluginSocketHandler | <code>RTKPluginSocketHandler</code> |
+| self                | <code>Self</code>                   |
+| participants        | <code>Participants</code>           |
+| chat                | <code>Chat</code>                   |
+| meetingTitle        | <code>string</code>                 |
 
 <a name="module_RTKPlugin--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+sendIframeEvent"></a>
 
 #### module.exports.sendIframeEvent(message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param   | Type                                | Description                              |
+| ------- | ----------------------------------- | ---------------------------------------- |
 | message | <code>RTKPluginIframeMessage</code> | Socket message forwarded to this plugin. |
 
 <a name="module_RTKPlugin--module.exports+handleIframeMessage"></a>
 
 #### module.exports.handleIframeMessage(iframeMessage)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| iframeMessage | <code>RTKPluginIframeMessage</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param         | Type                                |
+| ------------- | ----------------------------------- |
+| iframeMessage | <code>RTKPluginIframeMessage</code> |
 
 <a name="module_RTKPlugin--module.exports+sendData"></a>
 
 #### module.exports.sendData(payload)
+
 This method is used to send arbitrary data to the plugin.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| payload | <code>SendDataOptions</code> | The payload that you want to send inside the plugin. |
-| payload.eventName | <code>string</code> | Name of the event. This is used to listen for the event in plugin SDK. |
-| payload.data | <code>any</code> | Data you wish to emit. It can assume any data type. |
+| Param             | Type                         | Description                                                            |
+| ----------------- | ---------------------------- | ---------------------------------------------------------------------- |
+| payload           | <code>SendDataOptions</code> | The payload that you want to send inside the plugin.                   |
+| payload.eventName | <code>string</code>          | Name of the event. This is used to listen for the event in plugin SDK. |
+| payload.data      | <code>any</code>             | Data you wish to emit. It can assume any data type.                    |
 
 <a name="module_RTKPlugin--module.exports+removeRTKPluginView"></a>
 
 #### module.exports.removeRTKPluginView(viewId)
+
 This method is used for cleaning up event listeners attached to an iframe. It must
 be used before the iframe is removed from the DOM.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
+| Param  | Type                | Default                          | Description                                                        |
+| ------ | ------------------- | -------------------------------- | ------------------------------------------------------------------ |
 | viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+addRTKPluginView"></a>
 
 #### module.exports.addRTKPluginView(iframe, viewId)
+
 This method adds the communication layer between the plugin inside the iframe
 and the core application (meeting object) in the main window.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |  | Iframe element to display this plugin. |
-| viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
+| Param  | Type                                                              | Default                          | Description                                                        |
+| ------ | ----------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------ |
+| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |                                  | Iframe element to display this plugin.                             |
+| viewId | <code>string</code>                                               | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+setActive"></a>
 
 #### module.exports.setActive(active)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| active | <code>boolean</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param  | Type                 |
+| ------ | -------------------- |
+| active | <code>boolean</code> |
 
 <a name="module_RTKPlugin--module.exports+activateForSelf"></a>
 
 #### module.exports.activateForSelf()
+
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivateForSelf"></a>
 
 #### module.exports.deactivateForSelf()
+
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+enable"></a>
 
 #### ~~module.exports.enable()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+disable"></a>
 
 #### ~~module.exports.disable()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+activate"></a>
 
 #### module.exports.activate()
+
 Activate this plugin for all participants.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivate"></a>
 
 #### module.exports.deactivate()
+
 Deactivate this plugin for all participants.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
index 8ea2b9486986701..ff22e5a74589e76 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
@@ -9,37 +9,40 @@ web_core_version: 1.2.4
 <a name="module_RTKPlugins"></a>
 
 The RTKPlugins module consists of all the plugins in the meeting. It has 2 maps:
+
 - `all`: Consists of all the plugins in the meeting.
 - `active`: Consists of the plugins that are currently in use.
 
-
 * [RTKPlugins](#module_RTKPlugins)
-    * [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
-        * [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
-        * [.all](#module_RTKPlugins--module.exports+all)
-        * [.active](#module_RTKPlugins--module.exports+active)
+  - [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
+    - [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
+    - [.all](#module_RTKPlugins--module.exports+all)
+    - [.active](#module_RTKPlugins--module.exports+active)
 
 <a name="exp_module_RTKPlugins--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKPlugins--module.exports_new"></a>
 
 #### new module.exports(logger)
 
-| Param | Type |
-| --- | --- |
-| logger | <code>Logger</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| logger | <code>Logger</code> |
 
 <a name="module_RTKPlugins--module.exports+all"></a>
 
 #### module.exports.all
+
 All plugins accessible by the current user.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
 <a name="module_RTKPlugins--module.exports+active"></a>
 
 #### module.exports.active
+
 All plugins that are currently enabled in the room.
 
-**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
+**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
index 95f20dbb49fe688..25d6abf2a17b0fe 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
@@ -10,41 +10,42 @@ web_core_version: 1.2.4
 
 The RTKPolls module consists of the polls that have been created in the meeting.
 
-
-* [RTKPolls](#module_RTKPolls)
-    * [.items](#module_RTKPolls+items)
-    * [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
-    * [.vote(pollId, index)](#module_RTKPolls+vote)
+- [RTKPolls](#module_RTKPolls)
+  - [.items](#module_RTKPolls+items)
+  - [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
+  - [.vote(pollId, index)](#module_RTKPolls+vote)
 
 <a name="module_RTKPolls+items"></a>
 
 ### meeting.polls.items
+
 An array of poll items.
 
 **Kind**: instance property of [<code>RTKPolls</code>](#module_RTKPolls)  
 <a name="module_RTKPolls+create"></a>
 
 ### meeting.polls.create(question, options, anonymous, hideVotes)
+
 Creates a poll in the meeting.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
 
-| Param | Default | Description |
-| --- | --- | --- |
-| question |  | The question that is to be voted for. |
-| options |  | The options of the poll. |
-| anonymous | <code>false</code> | If true, the poll votes are anonymous. |
+| Param     | Default            | Description                                |
+| --------- | ------------------ | ------------------------------------------ |
+| question  |                    | The question that is to be voted for.      |
+| options   |                    | The options of the poll.                   |
+| anonymous | <code>false</code> | If true, the poll votes are anonymous.     |
 | hideVotes | <code>false</code> | If true, the votes on the poll are hidden. |
 
 <a name="module_RTKPolls+vote"></a>
 
 ### meeting.polls.vote(pollId, index)
+
 Casts a vote on an existing poll.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
 
-| Param | Description |
-| --- | --- |
+| Param  | Description                                |
+| ------ | ------------------------------------------ |
 | pollId | The ID of the poll that is to be voted on. |
-| index | The index of the option. |
-
+| index  | The index of the option.                   |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
index 4b2dd3b6116b3dd..e63b1525fae136c 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
@@ -11,39 +11,43 @@ web_core_version: 1.2.4
 The RTKRecording module represents the state of the current recording, and allows
 to start/stop recordings and check if there's a recording in progress.
 
-
-* [RTKRecording](#module_RTKRecording)
-    * [.telemetry](#module_RTKRecording+telemetry)
-    * [.start()](#module_RTKRecording+start)
-    * [.stop()](#module_RTKRecording+stop)
-    * [.pause()](#module_RTKRecording+pause)
-    * [.resume()](#module_RTKRecording+resume)
+- [RTKRecording](#module_RTKRecording)
+  - [.telemetry](#module_RTKRecording+telemetry)
+  - [.start()](#module_RTKRecording+start)
+  - [.stop()](#module_RTKRecording+stop)
+  - [.pause()](#module_RTKRecording+pause)
+  - [.resume()](#module_RTKRecording+resume)
 
 <a name="module_RTKRecording+telemetry"></a>
 
 ### meeting.recording.telemetry
+
 **Kind**: instance property of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+start"></a>
 
 ### meeting.recording.start()
+
 Starts recording the meeting.
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+stop"></a>
 
 ### meeting.recording.stop()
+
 Stops all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+pause"></a>
 
 ### meeting.recording.pause()
+
 Pauses all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+resume"></a>
 
 ### meeting.recording.resume()
+
 Resumes all recording currently in 'PAUSED' state
 
-**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
+**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
index aa4a71840eac6b8..1ad8cd81f058059 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
@@ -12,42 +12,43 @@ The RTKSelf module represents the current user, and allows to modify the state
 of the user in the meeting. The audio and video streams of the user can be retrieved from
 this module.
 
-
-* [RTKSelf](#module_RTKSelf)
-    * [.telemetry](#module_RTKSelf+telemetry)
-    * [.peerId](#module_RTKSelf+peerId)
-    * [.roomState](#module_RTKSelf+roomState)
-    * [.permissions](#module_RTKSelf+permissions)
-    * [.config](#module_RTKSelf+config)
-    * [.roomJoined](#module_RTKSelf+roomJoined)
-    * [.isPinned](#module_RTKSelf+isPinned)
-    * [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
-    * [.setName(name)](#module_RTKSelf+setName)
-    * [.setupTracks(options)](#module_RTKSelf+setupTracks)
-    * [.enableAudio()](#module_RTKSelf+enableAudio)
-    * [.enableVideo()](#module_RTKSelf+enableVideo)
-    * [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
-    * [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
-    * [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
-    * [.disableAudio()](#module_RTKSelf+disableAudio)
-    * [.disableVideo()](#module_RTKSelf+disableVideo)
-    * [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
-    * [.getAllDevices()](#module_RTKSelf+getAllDevices)
-    * [.setIsPinned()](#module_RTKSelf+setIsPinned)
-    * [.pin()](#module_RTKSelf+pin)
-    * [.unpin()](#module_RTKSelf+unpin)
-    * [.hide()](#module_RTKSelf+hide)
-    * [.show()](#module_RTKSelf+show)
-    * [.setDevice(device)](#module_RTKSelf+setDevice)
-    * [.updateVideo()](#module_RTKSelf+updateVideo)
+- [RTKSelf](#module_RTKSelf)
+  - [.telemetry](#module_RTKSelf+telemetry)
+  - [.peerId](#module_RTKSelf+peerId)
+  - [.roomState](#module_RTKSelf+roomState)
+  - [.permissions](#module_RTKSelf+permissions)
+  - [.config](#module_RTKSelf+config)
+  - [.roomJoined](#module_RTKSelf+roomJoined)
+  - [.isPinned](#module_RTKSelf+isPinned)
+  - [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
+  - [.setName(name)](#module_RTKSelf+setName)
+  - [.setupTracks(options)](#module_RTKSelf+setupTracks)
+  - [.enableAudio()](#module_RTKSelf+enableAudio)
+  - [.enableVideo()](#module_RTKSelf+enableVideo)
+  - [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
+  - [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
+  - [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
+  - [.disableAudio()](#module_RTKSelf+disableAudio)
+  - [.disableVideo()](#module_RTKSelf+disableVideo)
+  - [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
+  - [.getAllDevices()](#module_RTKSelf+getAllDevices)
+  - [.setIsPinned()](#module_RTKSelf+setIsPinned)
+  - [.pin()](#module_RTKSelf+pin)
+  - [.unpin()](#module_RTKSelf+unpin)
+  - [.hide()](#module_RTKSelf+hide)
+  - [.show()](#module_RTKSelf+show)
+  - [.setDevice(device)](#module_RTKSelf+setDevice)
+  - [.updateVideo()](#module_RTKSelf+updateVideo)
 
 <a name="module_RTKSelf+telemetry"></a>
 
 ### meeting.self.telemetry
+
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+peerId"></a>
 
 ### meeting.self.peerId
+
 NOTE(ishita1805): Discussed with Ravindra, added a duplicate for consistency
 when using identifiers in Locker.
 We might want to look at deprecating the `id` sometime later.
@@ -56,6 +57,7 @@ We might want to look at deprecating the `id` sometime later.
 <a name="module_RTKSelf+roomState"></a>
 
 ### meeting.self.roomState
+
 Returns the current state of room
 init - Initial State
 joined - User is in the meeting
@@ -69,67 +71,76 @@ ended - The meeting was ended
 <a name="module_RTKSelf+permissions"></a>
 
 ### meeting.self.permissions
+
 Returns the current permission given to the user for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+config"></a>
 
 ### meeting.self.config
+
 Returns configuration for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+roomJoined"></a>
 
 ### meeting.self.roomJoined
+
 Returns true if the local participant has joined the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+isPinned"></a>
 
 ### meeting.self.isPinned
+
 Returns true if the current user is pinned.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+cleanupEvents"></a>
 
 ### meeting.self.cleanupEvents()
+
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setName"></a>
 
 ### meeting.self.setName(name)
+
 The name of the user can be set by calling this method.
 This will get reflected to other participants ONLY if
 this method is called before the room is joined.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| name | <code>string</code> | Name of the user. |
+| Param | Type                | Description       |
+| ----- | ------------------- | ----------------- |
+| name  | <code>string</code> | Name of the user. |
 
 <a name="module_RTKSelf+setupTracks"></a>
 
 ### meeting.self.setupTracks(options)
+
 Sets up the local media tracks.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| options | <code>Object</code> | The audio and video options. |
-| [options.video] | <code>boolean</code> | If true, the video stream is fetched. |
-| [options.audio] | <code>boolean</code> | If true, the audio stream is fetched. |
+| Param                | Type                 | Description                                       |
+| -------------------- | -------------------- | ------------------------------------------------- |
+| options              | <code>Object</code>  | The audio and video options.                      |
+| [options.video]      | <code>boolean</code> | If true, the video stream is fetched.             |
+| [options.audio]      | <code>boolean</code> | If true, the audio stream is fetched.             |
 | [options.forceReset] | <code>boolean</code> | If true, force resets tracks before re-acquiring. |
 
 <a name="module_RTKSelf+enableAudio"></a>
 
 ### meeting.self.enableAudio()
+
 This method is used to unmute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+enableVideo"></a>
 
 ### meeting.self.enableVideo()
+
 This method is used to start streaming the local participant's video
 to the meeting.
 
@@ -137,6 +148,7 @@ to the meeting.
 <a name="module_RTKSelf+updateVideoConstraints"></a>
 
 ### meeting.self.updateVideoConstraints()
+
 This method is used to apply constraints to the current video
 stream.
 
@@ -144,6 +156,7 @@ stream.
 <a name="module_RTKSelf+enableScreenShare"></a>
 
 ### meeting.self.enableScreenShare()
+
 This method is used to start sharing the local participant's screen
 to the meeting.
 
@@ -151,6 +164,7 @@ to the meeting.
 <a name="module_RTKSelf+updateScreenshareConstraints"></a>
 
 ### meeting.self.updateScreenshareConstraints()
+
 This method is used to apply constraints to the current screenshare
 stream.
 
@@ -158,34 +172,40 @@ stream.
 <a name="module_RTKSelf+disableAudio"></a>
 
 ### meeting.self.disableAudio()
+
 This method is used to mute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableVideo"></a>
 
 ### meeting.self.disableVideo()
+
 This participant is used to disable the local participant's video.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableScreenShare"></a>
 
 ### meeting.self.disableScreenShare()
+
 This method is used to stop sharing the local participant's screen.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+getAllDevices"></a>
 
 ### meeting.self.getAllDevices()
+
 Returns all media devices accessible by the local participant.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setIsPinned"></a>
 
 ### meeting.self.setIsPinned()
+
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+pin"></a>
 
 ### meeting.self.pin()
+
 Returns `self.id` if user has permission
 to pin participants.
 
@@ -193,6 +213,7 @@ to pin participants.
 <a name="module_RTKSelf+unpin"></a>
 
 ### meeting.self.unpin()
+
 Returns `self.id` if user has permission
 to unpin participants.
 
@@ -200,29 +221,33 @@ to unpin participants.
 <a name="module_RTKSelf+hide"></a>
 
 ### meeting.self.hide()
+
 Hide's user's tile in the UI (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+show"></a>
 
 ### meeting.self.show()
+
 Show's user's tile in the UI if hidden (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setDevice"></a>
 
 ### meeting.self.setDevice(device)
+
 Change the current media device that is being used by the local participant.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                         | Description                                                                                      |
+| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
 
 <a name="module_RTKSelf+updateVideo"></a>
 
 ### meeting.self.updateVideo()
+
 Internal method, do not use
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
index 9e2d6335663b878..be8f537561e76eb 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
@@ -147,16 +147,16 @@ Returns true if screen share is enabled.
 **Kind**: global variable  
 <a name="init"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Default |
-| --- | --- | --- |
-| options | <code>Object</code> |  | 
-| [options.video] | <code>boolean</code> |  | 
-| [options.audio] | <code>boolean</code> |  | 
-| [options.constraints] | <code>MediaConstraints</code> |  | 
-| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
-| [context] | <code>Context</code> | <code></code> | 
+| Param                 | Type                          | Default            |
+| --------------------- | ----------------------------- | ------------------ |
+| options               | <code>Object</code>           |                    |
+| [options.video]       | <code>boolean</code>          |                    |
+| [options.audio]       | <code>boolean</code>          |                    |
+| [options.constraints] | <code>MediaConstraints</code> |                    |
+| [skipAwaits]          | <code>boolean</code>          | <code>false</code> |
+| [context]             | <code>Context</code>          | <code></code>      |
 
 <a name="addAudioMiddleware"></a>
 
@@ -165,21 +165,21 @@ If there are more than 1 audio middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| audioMiddleware | <code>AudioMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| audioMiddleware | <code>AudioMiddleware</code> |
 
 <a name="removeAudioMiddleware"></a>
 
 Removes the audio middleware, if it is there.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| audioMiddleware | <code>AudioMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| audioMiddleware | <code>AudioMiddleware</code> |
 
 <a name="removeAllAudioMiddlewares"></a>
 
@@ -193,32 +193,32 @@ If there are more than 1 video middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| videoMiddleware | <code>VideoMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| videoMiddleware | <code>VideoMiddleware</code> |
 
 <a name="setVideoMiddlewareGlobalConfig"></a>
 
 Sets global config to be used by video middlewares.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| config | <code>VideoMiddlewareGlobalConfig</code> | config |
-| config.disablePerFrameCanvasRendering | <code>boolean</code> | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas,  it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
+| Param                                 | Type                                     | Description                                                                                                                                                                                                                                                                                               |
+| ------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| config                                | <code>VideoMiddlewareGlobalConfig</code> | config                                                                                                                                                                                                                                                                                                    |
+| config.disablePerFrameCanvasRendering | <code>boolean</code>                     | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas, it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
 
 <a name="removeVideoMiddleware"></a>
 
 Removes the video middleware, if it is there.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| videoMiddleware | <code>VideoMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| videoMiddleware | <code>VideoMiddleware</code> |
 
 <a name="removeAllVideoMiddlewares"></a>
 
@@ -249,20 +249,19 @@ Returns the local participant's speaker devices.
 
 Returns the local participant's device, indexed by ID and kind.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| deviceId | <code>string</code> | The ID of the device. |
-| kind | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
+| Param    | Type                                                                                                 | Description                                       |
+| -------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| deviceId | <code>string</code>                                                                                  | The ID of the device.                             |
+| kind     | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
 
 <a name="setDevice"></a>
 
 Change the current media device that is being used by the local participant.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                         | Description                                                                                      |
+| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
-
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
index 787b7778e4ea72e..35bd0dcc153011f 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
@@ -13,70 +13,76 @@ RTKStage refers to a virtual area, where participants stream are visible to othe
 When a participant is off stage, they are not producing media
 but only consuming media from participants who are on RTKStage
 
-
-* [RTKStage](#module_RTKStage)
-    * [module.exports](#exp_module_RTKStage--module.exports) ⏏
-        * [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
-        * [.telemetry](#module_RTKStage--module.exports+telemetry)
-        * [.peerId](#module_RTKStage--module.exports+peerId)
-        * [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
-        * [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
-        * [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
-        * [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
-        * [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
-        * [.join()](#module_RTKStage--module.exports+join)
-        * [.leave()](#module_RTKStage--module.exports+leave)
-        * [.kick(userIds)](#module_RTKStage--module.exports+kick)
+- [RTKStage](#module_RTKStage)
+  - [module.exports](#exp_module_RTKStage--module.exports) ⏏
+    - [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
+    - [.telemetry](#module_RTKStage--module.exports+telemetry)
+    - [.peerId](#module_RTKStage--module.exports+peerId)
+    - [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
+    - [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
+    - [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
+    - [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
+    - [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
+    - [.join()](#module_RTKStage--module.exports+join)
+    - [.leave()](#module_RTKStage--module.exports+leave)
+    - [.kick(userIds)](#module_RTKStage--module.exports+kick)
 
 <a name="exp_module_RTKStage--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKStage--module.exports_new"></a>
 
 #### new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
-| stageSocketHandler | <code>RTKStageSocketHandler</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| Param              | Type                               |
+| ------------------ | ---------------------------------- |
+| context            | <code>Context</code>               |
+| self               | <code>Self</code>                  |
+| participants       | <code>Participants</code>          |
+| stageSocketHandler | <code>RTKStageSocketHandler</code> |
+| roomSocketHandler  | <code>RoomSocketHandler</code>     |
 
 <a name="module_RTKStage--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+peerId"></a>
 
 #### module.exports.peerId
+
 Returns the peerId of the current user
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+getAccessRequests"></a>
 
 #### module.exports.getAccessRequests()
+
 Method to fetch all RTKStage access requests from viewers
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+requestAccess"></a>
 
 #### module.exports.requestAccess()
+
 Method to send a request to privileged users to join the stage
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+cancelRequestAccess"></a>
 
 #### module.exports.cancelRequestAccess()
+
 Method to cancel a previous RTKStage join request
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+grantAccess"></a>
 
 #### module.exports.grantAccess()
+
 Method to grant access to RTKStage.
-	This can be in response to a RTKStage Join request but it can be called on other users as well
+This can be in response to a RTKStage Join request but it can be called on other users as well
 
 `permissions.acceptRTKStageRequests` privilege required
 
@@ -84,6 +90,7 @@ Method to grant access to RTKStage.
 <a name="module_RTKStage--module.exports+denyAccess"></a>
 
 #### module.exports.denyAccess()
+
 Method to deny access to RTKStage.
 This should be called in response to a RTKStage Join request
 
@@ -91,6 +98,7 @@ This should be called in response to a RTKStage Join request
 <a name="module_RTKStage--module.exports+join"></a>
 
 #### module.exports.join()
+
 Method to join the stage
 Users either need to have the permission in the preset or must be accepted by a privileged
 user to call this method
@@ -99,6 +107,7 @@ user to call this method
 <a name="module_RTKStage--module.exports+leave"></a>
 
 #### module.exports.leave()
+
 Method to leave the stage
 Users must either be on the stage already or be accepted to join the stage
 to call this method
@@ -107,13 +116,13 @@ to call this method
 <a name="module_RTKStage--module.exports+kick"></a>
 
 #### module.exports.kick(userIds)
+
 Method to kick a user off the stage
 
 `permissions.acceptRTKStageRequests` privilege required
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
-
-| Param | Type |
-| --- | --- |
-| userIds | <code>Array.&lt;string&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)
 
+| Param   | Type                              |
+| ------- | --------------------------------- |
+| userIds | <code>Array.&lt;string&gt;</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
index c27dd5a9443bf19..51d98a4f1ebc2ea 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
@@ -12,127 +12,136 @@ This module represents a single global store.
 The store can be accessed from the `meeting.stores` module.
 
 **Returns**: An instance of RTKStore.  
-**Example**  
+**Example**
+
 ```js
-const handRaiseRTKStore = meeting.stores.stores.get('handRaise');
+const handRaiseRTKStore = meeting.stores.stores.get("handRaise");
 ```
 
-* [RTKStore](#module_RTKStore) ⇒
-    * [module.exports](#exp_module_RTKStore--module.exports) ⏏
-        * [new module.exports(args)](#new_module_RTKStore--module.exports_new)
-        * [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
-        * [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
-        * [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
-        * [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
-        * [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
-        * [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
-        * [.populate(data)](#module_RTKStore--module.exports+populate)
+- [RTKStore](#module_RTKStore) ⇒
+  - [module.exports](#exp_module_RTKStore--module.exports) ⏏
+    - [new module.exports(args)](#new_module_RTKStore--module.exports_new)
+    - [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
+    - [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
+    - [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
+    - [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
+    - [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
+    - [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
+    - [.populate(data)](#module_RTKStore--module.exports+populate)
 
 <a name="exp_module_RTKStore--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKStore--module.exports_new"></a>
 
 #### new module.exports(args)
 
-| Param | Type |
-| --- | --- |
-| args | <code>Object</code> | 
-| args.name | <code>string</code> | 
-| args.socketHandler | <code>PluginSocketHandler</code> | 
-| args.meetingId | <code>string</code> | 
+| Param              | Type                             |
+| ------------------ | -------------------------------- |
+| args               | <code>Object</code>              |
+| args.name          | <code>string</code>              |
+| args.socketHandler | <code>PluginSocketHandler</code> |
+| args.meetingId     | <code>string</code>              |
 
 <a name="module_RTKStore--module.exports+set"></a>
 
 #### module.exports.set(key, value, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Sets a value in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| value | <code>any</code> |  | Data to be set. |
-| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
+| Param  | Type                 | Default            | Description                             |
+| ------ | -------------------- | ------------------ | --------------------------------------- |
+| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
+| value  | <code>any</code>     |                    | Data to be set.                         |
+| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
 
 <a name="module_RTKStore--module.exports+bulkSet"></a>
 
 #### module.exports.bulkSet(data) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Sets multiple values in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type |
-| --- | --- |
-| data | <code>Array.&lt;{key: string, payload: any}&gt;</code> | 
+| Param | Type                                                   |
+| ----- | ------------------------------------------------------ |
+| data  | <code>Array.&lt;{key: string, payload: any}&gt;</code> |
 
 <a name="module_RTKStore--module.exports+update"></a>
 
 #### module.exports.update(key, value, [sync]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Updates an already existing value in the store.
 If the value stored is `['a', 'b']`, the operation
 `store.update(key, ['c'])` will modify
 the value to `['a','b','c']`.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| value | <code>any</code> |  | Data to be updated. |
+| Param  | Type                 | Default           | Description                             |
+| ------ | -------------------- | ----------------- | --------------------------------------- |
+| key    | <code>string</code>  |                   | Unique identifier used to store value.  |
+| value  | <code>any</code>     |                   | Data to be updated.                     |
 | [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
 
 <a name="module_RTKStore--module.exports+delete"></a>
 
 #### module.exports.delete(key, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Deletes a key value pair form the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
+| Param  | Type                 | Default            | Description                             |
+| ------ | -------------------- | ------------------ | --------------------------------------- |
+| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
+| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
 
 <a name="module_RTKStore--module.exports+bulkDelete"></a>
 
 #### module.exports.bulkDelete(data) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Deletes multiple values from the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type |
-| --- | --- |
-| data | <code>Array.&lt;{key: string}&gt;</code> | 
+| Param | Type                                     |
+| ----- | ---------------------------------------- |
+| data  | <code>Array.&lt;{key: string}&gt;</code> |
 
 <a name="module_RTKStore--module.exports+get"></a>
 
 #### module.exports.get(key) ⇒ <code>any</code>
+
 Returns value for the given key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>any</code> - Value for the given key.  
+**Returns**: <code>any</code> - Value for the given key.
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
+| Param | Type                | Description                            |
+| ----- | ------------------- | -------------------------------------- |
+| key   | <code>string</code> | Unique identifier used to store value. |
 
 <a name="module_RTKStore--module.exports+getAll"></a>
 
 #### module.exports.getAll() ⇒ <code>RTKStoreData</code>
+
 Returns the entire store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
@@ -140,55 +149,59 @@ Returns the entire store.
 <a name="module_RTKStore--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKStore--module.exports+updateBulkRateLimits"></a>
 
 #### module.exports.updateBulkRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKStore--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(key, cb) ⇒ <code>void</code>
+
 Listens for data change on a store key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void  
+**Returns**: <code>void</code> - void
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
-| cb | <code>function</code> | The callback function that gets executed when data is modified. |
+| Param | Type                  | Description                                                     |
+| ----- | --------------------- | --------------------------------------------------------------- |
+| key   | <code>string</code>   | Unique identifier used to store value.                          |
+| cb    | <code>function</code> | The callback function that gets executed when data is modified. |
 
 <a name="module_RTKStore--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(key, [cb]) ⇒ <code>void</code>
+
 Removes all listeners for a key on the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void  
+**Returns**: <code>void</code> - void
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
-| [cb] | <code>function</code> | Callback to be removed. |
+| Param | Type                  | Description                            |
+| ----- | --------------------- | -------------------------------------- |
+| key   | <code>string</code>   | Unique identifier used to store value. |
+| [cb]  | <code>function</code> | Callback to be removed.                |
 
 <a name="module_RTKStore--module.exports+populate"></a>
 
 #### module.exports.populate(data)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| data | <code>RTKStoreData</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
 
+| Param | Type                      |
+| ----- | ------------------------- |
+| data  | <code>RTKStoreData</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
index 88539296c8905b0..e5a1e74b8e69bcf 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
@@ -10,72 +10,78 @@ web_core_version: 1.2.4
 
 The RTKThemePreset class represents the meeting theme for the current participant
 
-
-* [RTKThemePreset](#module_RTKThemePreset)
-    * [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
-        * [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
-        * _instance_
-            * ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
-            * ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
-            * ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
-            * ~~[.header](#module_RTKThemePreset--module.exports+header)~~
-            * ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
-            * [.viewType](#module_RTKThemePreset--module.exports+viewType)
-            * [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
-            * [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
-            * [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
-            * ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
-            * [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
-        * _static_
-            * [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
-            * [.default()](#module_RTKThemePreset--module.exports.default)
-            * [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
+- [RTKThemePreset](#module_RTKThemePreset)
+  - [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
+    - [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
+    - _instance_
+      - ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
+      - ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
+      - ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
+      - ~~[.header](#module_RTKThemePreset--module.exports+header)~~
+      - ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
+      - [.viewType](#module_RTKThemePreset--module.exports+viewType)
+      - [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
+      - [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
+      - [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
+      - ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
+      - [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
+    - _static_
+      - [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
+      - [.default()](#module_RTKThemePreset--module.exports.default)
+      - [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
 
 <a name="exp_module_RTKThemePreset--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKThemePreset--module.exports_new"></a>
 
 #### new module.exports(preset)
 
-| Param | Type |
-| --- | --- |
-| preset | <code>PresetV2CamelCased</code> | 
+| Param  | Type                            |
+| ------ | ------------------------------- |
+| preset | <code>PresetV2CamelCased</code> |
 
 <a name="module_RTKThemePreset--module.exports+setupScreen"></a>
 
 #### ~~module.exports.setupScreen~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+waitingRoom"></a>
 
 #### ~~module.exports.waitingRoom~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+controlBar"></a>
 
 #### ~~module.exports.controlBar~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+header"></a>
 
 #### ~~module.exports.header~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+pipMode"></a>
 
 #### ~~module.exports.pipMode~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+viewType"></a>
 
 #### module.exports.viewType
+
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -83,6 +89,7 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKThemePreset--module.exports+livestreamViewerQualities"></a>
 
 #### module.exports.livestreamViewerQualities
+
 The `livestreamViewerQualities` specifies the allowed qualities of a stream,
 that can be viewed by a livestream viewer
 
@@ -90,6 +97,7 @@ that can be viewed by a livestream viewer
 <a name="module_RTKThemePreset--module.exports+maxVideoStreams"></a>
 
 #### module.exports.maxVideoStreams
+
 The `maxVideoStreams` contains the maximum video
 streams for mobile and desktop
 
@@ -97,6 +105,7 @@ streams for mobile and desktop
 <a name="module_RTKThemePreset--module.exports+maxScreenShareCount"></a>
 
 #### module.exports.maxScreenShareCount
+
 The `maxScreenShareCount` contains the maximum
 possible concurrent screen shares
 
@@ -104,37 +113,41 @@ possible concurrent screen shares
 <a name="module_RTKThemePreset--module.exports+plugins"></a>
 
 #### ~~module.exports.plugins~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+disabledPlugins"></a>
 
 #### module.exports.disabledPlugins
+
 The `disabledPlugins` property returns id of all disabled plugins
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports.fromResponse"></a>
 
 #### module.exports.fromResponse(preset)
+
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
-**Deprecated.**: Use init()  
+**Deprecated.**: Use init()
 
-| Param | Type |
-| --- | --- |
-| preset | <code>PresetV2CamelCased</code> | 
+| Param  | Type                            |
+| ------ | ------------------------------- |
+| preset | <code>PresetV2CamelCased</code> |
 
 <a name="module_RTKThemePreset--module.exports.default"></a>
 
 #### module.exports.default()
+
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 **Deprecated.**: Use init()  
 <a name="module_RTKThemePreset--module.exports.init"></a>
 
 #### module.exports.init([preset], [useDefault])
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [preset] | <code>PresetV2CamelCased</code> |  | 
-| [useDefault] | <code>boolean</code> | <code>true</code> | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)
 
+| Param        | Type                            | Default           |
+| ------------ | ------------------------------- | ----------------- |
+| [preset]     | <code>PresetV2CamelCased</code> |                   |
+| [useDefault] | <code>boolean</code>            | <code>true</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
index 1afafcb4fd4b751..31f2a68764c9ee9 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
@@ -13,45 +13,46 @@ An object of the RealtimeKitClient class can be created using
 `await RealtimeKitClient.init({ ... })`. Typically, an object of `RealtimeKitClient` is
 named `meeting`.
 
-
-* [RealtimeKitClient](#module_RealtimeKitClient)
-    * [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
-        * [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
-        * _instance_
-            * [.participants](#module_RealtimeKitClient--module.exports+participants)
-            * [.self](#module_RealtimeKitClient--module.exports+self)
-            * [.meta](#module_RealtimeKitClient--module.exports+meta)
-            * [.ai](#module_RealtimeKitClient--module.exports+ai)
-            * [.plugins](#module_RealtimeKitClient--module.exports+plugins)
-            * [.chat](#module_RealtimeKitClient--module.exports+chat)
-            * [.polls](#module_RealtimeKitClient--module.exports+polls)
-            * [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
-            * [.__internals__](#module_RealtimeKitClient--module.exports+__internals__)
-            * [.join()](#module_RealtimeKitClient--module.exports+join)
-            * [.leave()](#module_RealtimeKitClient--module.exports+leave)
-            * ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
-            * ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
-        * _static_
-            * [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
-            * [.init(options)](#module_RealtimeKitClient--module.exports.init)
-            * [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
+- [RealtimeKitClient](#module_RealtimeKitClient)
+  - [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
+    - [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
+    - _instance_
+      - [.participants](#module_RealtimeKitClient--module.exports+participants)
+      - [.self](#module_RealtimeKitClient--module.exports+self)
+      - [.meta](#module_RealtimeKitClient--module.exports+meta)
+      - [.ai](#module_RealtimeKitClient--module.exports+ai)
+      - [.plugins](#module_RealtimeKitClient--module.exports+plugins)
+      - [.chat](#module_RealtimeKitClient--module.exports+chat)
+      - [.polls](#module_RealtimeKitClient--module.exports+polls)
+      - [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
+      - [.**internals**](#module_RealtimeKitClient--module.exports+__internals__)
+      - [.join()](#module_RealtimeKitClient--module.exports+join)
+      - [.leave()](#module_RealtimeKitClient--module.exports+leave)
+      - ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
+      - ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
+    - _static_
+      - [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
+      - [.init(options)](#module_RealtimeKitClient--module.exports.init)
+      - [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
 
 <a name="exp_module_RealtimeKitClient--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RealtimeKitClient--module.exports_new"></a>
 
 #### new module.exports(context, controller)
 
-| Param | Type |
-| --- | --- |
-| context | <code>IContext</code> | 
-| controller | <code>Controller</code> | 
+| Param      | Type                    |
+| ---------- | ----------------------- |
+| context    | <code>IContext</code>   |
+| controller | <code>Controller</code> |
 
 <a name="module_RealtimeKitClient--module.exports+participants"></a>
 
 #### module.exports.participants
+
 The `participants` object consists of 4 maps of participants,
 `waitlisted`, `joined`, `active`, `pinned`. The maps are indexed by
 `peerId`s, and the values are the corresponding participant objects.
@@ -60,6 +61,7 @@ The `participants` object consists of 4 maps of participants,
 <a name="module_RealtimeKitClient--module.exports+self"></a>
 
 #### module.exports.self
+
 The `self` object can be used to manipulate audio and video settings,
 and other configurations for the local participant. This exposes methods
 to enable and disable media tracks, share the user's screen, etc.
@@ -68,6 +70,7 @@ to enable and disable media tracks, share the user's screen, etc.
 <a name="module_RealtimeKitClient--module.exports+meta"></a>
 
 #### module.exports.meta
+
 The `room` object stores information about the current meeting, such
 as chat messages, polls, room name, etc.
 
@@ -75,6 +78,7 @@ as chat messages, polls, room name, etc.
 <a name="module_RealtimeKitClient--module.exports+ai"></a>
 
 #### module.exports.ai
+
 The `ai` object is used to interface with AI features.
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
@@ -83,6 +87,7 @@ features such as summary, and agenda using this object.
 <a name="module_RealtimeKitClient--module.exports+plugins"></a>
 
 #### module.exports.plugins
+
 The `plugins` object stores information about the plugins available in
 the current meeting. It exposes methods to activate and deactivate them.
 
@@ -90,6 +95,7 @@ the current meeting. It exposes methods to activate and deactivate them.
 <a name="module_RealtimeKitClient--module.exports+chat"></a>
 
 #### module.exports.chat
+
 The chat object stores the chat messages that were sent in the meeting.
 This includes text messages, images, and files.
 
@@ -97,6 +103,7 @@ This includes text messages, images, and files.
 <a name="module_RealtimeKitClient--module.exports+polls"></a>
 
 #### module.exports.polls
+
 The polls object stores the polls that were initiated in the meeting.
 It exposes methods to create and vote on polls.
 
@@ -104,6 +111,7 @@ It exposes methods to create and vote on polls.
 <a name="module_RealtimeKitClient--module.exports+connectedMeetings"></a>
 
 #### module.exports.connectedMeetings
+
 The connectedMeetings object stores the connected meetings states.
 It exposes methods to create/read/update/delete methods for connected meetings.
 
@@ -111,15 +119,17 @@ It exposes methods to create/read/update/delete methods for connected meetings.
 <a name="module_RealtimeKitClient--module.exports+__internals__"></a>
 
 #### module.exports.\_\_internals\_\_
-The __internals__ object exposes the internal tools & utilities such as features and logger
+
+The **internals** object exposes the internal tools & utilities such as features and logger
 so that client can utilise the same to build their own feature based UI.
-Logger (__internals__.logger) can be used to send logs to servers
-	to inform  of issues, if any, proactively.
+Logger (**internals**.logger) can be used to send logs to servers
+to inform of issues, if any, proactively.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+join"></a>
 
 #### module.exports.join()
+
 The `join()` method can be used to join the meeting.
 A `roomJoined` event is emitted on `self` when the room
 is joined successfully.
@@ -128,65 +138,70 @@ is joined successfully.
 <a name="module_RealtimeKitClient--module.exports+leave"></a>
 
 #### module.exports.leave()
+
 The `leave()` method can be used to leave a meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+joinRoom"></a>
 
 #### ~~module.exports.joinRoom()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+leaveRoom"></a>
 
 #### ~~module.exports.leaveRoom([state])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
-| Param | Type |
-| --- | --- |
-| [state] | <code>LeaveRoomState</code> | 
+| Param   | Type                        |
+| ------- | --------------------------- |
+| [state] | <code>LeaveRoomState</code> |
 
 <a name="module_RealtimeKitClient--module.exports.initMedia"></a>
 
 #### module.exports.initMedia([options], [skipAwaits], [cachedUserDetails])
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [options] | <code>Object</code> |  | 
-| [options.video] | <code>boolean</code> |  | 
-| [options.audio] | <code>boolean</code> |  | 
-| [options.constraints] | <code>MediaConstraints</code> |  | 
-| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
-| [cachedUserDetails] | <code>CachedUserDetails</code> |  | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+
+| Param                 | Type                           | Default            |
+| --------------------- | ------------------------------ | ------------------ |
+| [options]             | <code>Object</code>            |                    |
+| [options.video]       | <code>boolean</code>           |                    |
+| [options.audio]       | <code>boolean</code>           |                    |
+| [options.constraints] | <code>MediaConstraints</code>  |                    |
+| [skipAwaits]          | <code>boolean</code>           | <code>false</code> |
+| [cachedUserDetails]   | <code>CachedUserDetails</code> |                    |
 
 <a name="module_RealtimeKitClient--module.exports.init"></a>
 
 #### module.exports.init(options)
+
 The `init` method can be used to instantiate the RealtimeKitClient class.
 This returns an instance of RealtimeKitClient, which can be used to perform
 actions on the meeting.
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
-| Param | Description |
-| --- | --- |
-| options | The options object. |
+| Param             | Description                                     |
+| ----------------- | ----------------------------------------------- |
+| options           | The options object.                             |
 | options.authToken | The authorization token received using the API. |
-| options.baseURI | The base URL of the API. |
-| options.defaults | The default audio and video settings. |
+| options.baseURI   | The base URL of the API.                        |
+| options.defaults  | The default audio and video settings.           |
 
 <a name="module_RealtimeKitClient--module.exports.setupContext"></a>
 
 #### module.exports.setupContext(peerId, options, meetingId, args)
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerId | <code>string</code> | 
-| options | <code>RealtimeKitClientOptions</code> | 
-| meetingId | <code>string</code> | 
-| args | <code>any</code> | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
+| Param     | Type                                  |
+| --------- | ------------------------------------- |
+| peerId    | <code>string</code>                   |
+| options   | <code>RealtimeKitClientOptions</code> |
+| meetingId | <code>string</code>                   |
+| args      | <code>any</code>                      |
diff --git a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
index b94947abd5d3245..d9e3105165b252d 100644
--- a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
+++ b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
@@ -23,6 +23,7 @@ The following SDKs are collectively referred to as Web SDKs:
 - [`@cloudflare/realtimekit-virtual-background`](https://www.npmjs.com/package/@cloudflare/realtimekit-virtual-background)
 
 Overview of licenses:
+
 - Apache-2.0 (3)
 - ISC (1)
 - MIT (16)
@@ -813,10 +814,12 @@ Apache License
 ## RealtimeKit Android SDKs
 
 The following SDKs are collectively referred to as Android SDKs:
+
 - [`com.cloudflare.realtimekit:core-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-android)
 - [`com.cloudflare.realtimekit:ui-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/ui-android)
 
 Overview of licenses:
+
 - Apache-2.0 (24)
 
 ### Apache-2.0 (15 packages)
@@ -1932,11 +1935,13 @@ Apache License
 ## RealtimeKit iOS SDKs
 
 The following SDKs are collectively referred to as iOS SDKs:
+
 - [`RealtimeKit`](https://github.com/dyte-in/RealtimeKitCoreiOS)
 - [`RealtimeKitUI`](https://github.com/dyte-in/RealtimeKitUI)
 - [`RealtimeKit KMM Core`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-iosarm64)
 
 Overview of licenses:
+
 - Apache-2.0 (8)
 
 ### Apache-2.0 (4 packages)
@@ -2812,10 +2817,12 @@ Apache License
 ## RealtimeKit Flutter SDKs
 
 The following SDKs are collectively referred to as Flutter SDKs:
+
 - [`realtimekit_core`](https://pub.dev/packages/realtimekit_core)
 - [`realtimekit_ui`](https://pub.dev/packages/realtimekit_ui)
 
 Overview of licenses:
+
 - Apache-2.0 (1)
 - BSD-3-Clause (55)
 - MIT (10)
@@ -2848,7 +2855,7 @@ Used by:
 [watcher](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2014, the Dart project authors. 
+Copyright 2014, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -2892,7 +2899,7 @@ Used by:
 [typed_data](https://github.com/dart-lang/core)
 
 ```
-Copyright 2015, the Dart project authors. 
+Copyright 2015, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3167,7 +3174,7 @@ Used by:
 [term_glyph](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2017, the Dart project authors. 
+Copyright 2017, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3205,7 +3212,7 @@ Used by:
 [package_config](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2019, the Dart project authors. 
+Copyright 2019, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3243,7 +3250,7 @@ Used by:
 [logging](https://github.com/dart-lang/core)
 
 ```
-Copyright 2013, the Dart project authors. 
+Copyright 2013, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3281,7 +3288,7 @@ Used by:
 [test_core](https://github.com/dart-lang/test)
 
 ```
-Copyright 2018, the Dart project authors. 
+Copyright 2018, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3751,11 +3758,11 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ```
 
-### BSD-3-Clause (_fe_analyzer_shared)
+### BSD-3-Clause (\_fe_analyzer_shared)
 
 Used by:
 
-[_fe_analyzer_shared](https://github.com/dart-lang/sdk)
+[\_fe_analyzer_shared](https://github.com/dart-lang/sdk)
 
 ```
 Copyright 2019, the Dart project authors.
@@ -3923,7 +3930,7 @@ Used by:
 [web_socket_channel](https://github.com/dart-lang/http)
 
 ```
-Copyright 2016, the Dart project authors. 
+Copyright 2016, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3994,7 +4001,7 @@ Used by:
 [web_socket](https://github.com/dart-lang/http)
 
 ```
-Copyright 2024, the Dart project authors. 
+Copyright 2024, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4030,7 +4037,7 @@ Used by:
 [frontend_server_client](https://github.com/dart-lang/webdev)
 
 ```
-Copyright 2020, the Dart project authors. 
+Copyright 2020, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4610,10 +4617,12 @@ THE SOFTWARE.
 ## RealtimeKit React Native SDKs
 
 The following SDKs are collectively referred to as React Native SDKs:
+
 - [`@cloudflare/realtimekit-react-native`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native)
 - [`@cloudflare/realtimekit-react-native-ui`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native-ui)
 
 Overview of licenses:
+
 - Apache-2.0 (3)
 - BSD-2-Clause (10)
 - BSD-3-Clause (3)
@@ -6696,25 +6705,25 @@ The MIT License
 
 Copyright (c) 2013 Dominic Tarr
 
-Permission is hereby granted, free of charge, 
-to any person obtaining a copy of this software and 
-associated documentation files (the "Software"), to 
-deal in the Software without restriction, including 
-without limitation the rights to use, copy, modify, 
-merge, publish, distribute, sublicense, and/or sell 
-copies of the Software, and to permit persons to whom 
-the Software is furnished to do so, 
+Permission is hereby granted, free of charge,
+to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to
+deal in the Software without restriction, including
+without limitation the rights to use, copy, modify,
+merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom
+the Software is furnished to do so,
 subject to the following conditions:
 
-The above copyright notice and this permission notice 
+The above copyright notice and this permission notice
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -7691,25 +7700,25 @@ The MIT License
 
 Copyright (c) 2015 John Hiesey
 
-Permission is hereby granted, free of charge, 
-to any person obtaining a copy of this software and 
-associated documentation files (the "Software"), to 
-deal in the Software without restriction, including 
-without limitation the rights to use, copy, modify, 
-merge, publish, distribute, sublicense, and/or sell 
-copies of the Software, and to permit persons to whom 
-the Software is furnished to do so, 
+Permission is hereby granted, free of charge,
+to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to
+deal in the Software without restriction, including
+without limitation the rights to use, copy, modify,
+merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom
+the Software is furnished to do so,
 subject to the following conditions:
 
-The above copyright notice and this permission notice 
+The above copyright notice and this permission notice
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -8668,7 +8677,7 @@ Used by:
 ```
 The MIT License (MIT)
 
-Copyright (c) 2015 
+Copyright (c) 2015
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9197,7 +9206,7 @@ Used by:
 [convert-source-map](https://github.com/thlorenz/convert-source-map)
 
 ```
-Copyright 2013 Thorsten Lorenz. 
+Copyright 2013 Thorsten Lorenz.
 All rights reserved.
 
 Permission is hereby granted, free of charge, to any person
@@ -9547,7 +9556,7 @@ exhaustive, and do not form part of our licenses.
      such as asking that all changes be marked or described.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
-     for the public: 
+     for the public:
 	wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
@@ -10881,4 +10890,4 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
index 3a3cdb4f8122af5..837b0108533d03f 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
@@ -18,15 +18,15 @@ RealtimeKit's watermark feature enables you to include an image as a watermark i
 
 ```json
 {
-  "video_config": {
-    "watermark": {
-      "url": "https://test.io/images/client-logos-6.webp",
-      "position": "left top",
-      "size": {
-        "height": 20,
-        "width": 100
-      }
-    }
-  }
+	"video_config": {
+		"watermark": {
+			"url": "https://test.io/images/client-logos-6.webp",
+			"position": "left top",
+			"size": {
+				"height": 20,
+				"width": 100
+			}
+		}
+	}
 }
 ```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
index e79a05b4153957e..f6ff1aa7a6b2ed3 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
@@ -26,9 +26,9 @@ example:
 
 ```json
 {
-  "video_config": {
-    "codec": "H264"
-  }
+	"video_config": {
+		"codec": "H264"
+	}
 }
 ```
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
index 67da5cc041affca..81744c2746450cb 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
@@ -12,13 +12,13 @@ products:
 
 The recording of a meeting can have the following states:
 
-| Name      | Description                                                                                                                                                                                                                                         |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                  |
-| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                      |
+| Name      | Description                                                                                                                                                                                                                                                |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                         |
+| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                             |
 | UPLOADING | The recording has been stopped and the file is being uploaded to the cloud storage. If you have not specified storage details, then the files will be uploaded only to RealtimeKit's server. Any RTMP and livestreaming link will also stop at this stage. |
-| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                     |
-| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                    |
+| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                            |
+| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                           |
 
 ## Fetching the state
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
index 50d601987d14693..aa28566cf639ab0 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -8,9 +8,16 @@ products:
   - realtime
 ---
 
-Track recording records each participant's audio as a separate WebM file in RealtimeKit's Cloudflare R2 bucket. Use track recording when you need isolated speaker tracks for post-processing, transcription, compliance workflows, or audio analysis.
+Track recording lets you record participant audio as separate WebM files instead of one composite meeting recording. Use it when you need speaker-level control over what you store, process, or review.
 
-Composite recording creates one mixed meeting recording. Track recording creates one file per recorded participant peer.
+With track recording, you can record specific participant tracks by passing `user_ids`, which is useful for content-sensitive or regulated workflows where recording every participant is unnecessary. If you do not provide `user_ids`, RealtimeKit will record all participant audio tracks as separate WebM files by default.
+
+To pass `user_ids` for specific participant track recording, use the following minimum SDK versions:
+
+- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
+- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
+- Android Core or iOS Core: version `2.0.0` or later
+- Android UI Kit or iOS UI Kit: version `1.1.0` or later
 
 :::note
 
@@ -22,19 +29,36 @@ Track recording currently supports audio tracks only. Video track recording is i
 
 Track recording has the following requirements and limits:
 
-| Limit                 | Description                                           |
-| --------------------- | ----------------------------------------------------- |
-| Active meeting        | The meeting must have an active live session.         |
-| Media kind            | Only `audio` layers are recorded.                     |
-| Participant selection | Pass up to `100` values in `user_ids`.                |
-| Storage               | Files are uploaded to the RealtimeKit bucket.         |
-| File retention        | RealtimeKit bucket download URLs expire after seven days. |
+| Limit                 | Description                                                                  |
+| --------------------- | ---------------------------------------------------------------------------- |
+| Active meeting        | The meeting must have an active live session.                                |
+| Media kind            | Only `audio` layers are recorded.                                            |
+| Participant selection | Pass up to 100 values in `user_ids`.                                         |
+| Storage               | Files are uploaded to RealtimeKit's managed R2 bucket with zero-egress fees. |
+| File retention        | RealtimeKit bucket download URLs expire after seven days.                    |
 
 ## Start track recording
 
-To start track recording, call `POST /recordings/track` with the meeting ID.
+### Record specific participants
+
+To record separate audio tracks for specific participants, call `POST /recordings/track` with the meeting ID and the participant `user_ids`.
+
+```bash
+curl --request POST \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+  "user_ids": ["user-123", "user-456"]
+}'
+```
+
+RealtimeKit records current and future participant peers whose `user_id` matches the allowlist. Participants whose `user_id` is not listed are not recorded.
 
-If you omit `layers`, RealtimeKit records all participant audio. You can pass an audio layer to set a file name prefix for generated files.
+### Record all participants as separate tracks
+
+Omit `user_ids` to record separate audio tracks for all participants in the live meeting. RealtimeKit creates one WebM file for each recorded participant peer.
 
 ```bash
 curl --request POST \
@@ -63,26 +87,9 @@ The response includes a recording ID. Use this ID to stop or fetch the recording
 }
 ```
 
-## Record selected participants
-
-Pass `user_ids` to record only specific participants. RealtimeKit records current and future participant peers whose `user_id` matches the allowlist.
-
-:::caution
-
-To use selective track recording with `user_ids`, contact your Cloudflare account team or RealtimeKit support.
-
-:::
-
-```json
-{
-	"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
-	"user_ids": ["user-123", "user-456"]
-}
-```
-
-## Set file name prefix
+## Customize file names with prefixes
 
-Use `file_name_prefix` to prefix every generated track recording file.
+Use `layers.default.file_name_prefix` to prefix every generated track recording file.
 
 ```json
 {
@@ -120,7 +127,7 @@ After track recording stops, RealtimeKit uploads the per-participant WebM files
 
 Track recording uses the same recording status lifecycle as composite recording. To monitor status, refer to [Monitor Recording Status](/realtime/realtimekit/recording-guide/monitor-status/).
 
-When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. The `download_url` field contains the recorded WebM files for participant peers.
+When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. For track recordings, `download_url` contains per-participant WebM file URLs grouped by layer.
 
 ```json
 {
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
index a530264178e2cd7..740b8984d91accc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
index 9022f7eef15914a..be354415f804c68 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-ai-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
-</rtk-ai-toggle>
+<rtk-ai-toggle [meeting]="meeting" size="md" variant="button"> </rtk-ai-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
index 36207327073578c..05bb2a1ea2666d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-ai-transcriptions component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
@@ -26,9 +27,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-transcriptions
- [initialTranscriptions]="[]"
- [meeting]="meeting">
+<rtk-ai-transcriptions [initialTranscriptions]="[]" [meeting]="meeting">
 </rtk-ai-transcriptions>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
index 936d95be25b08c0..8d64f23b0df3f0b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ai component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai
- [meeting]="meeting"
- size="md"
- [view]="aiview">
-</rtk-ai>
+<rtk-ai [meeting]="meeting" size="md" [view]="aiview"> </rtk-ai>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
index 690fb5c0632fc17..74fb58b92b23308 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-grid component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-grid
- [config]="defaultUiConfig"
- [hideSelf]="true"
- [meeting]="meeting">
+	[config]="defaultUiConfig"
+	[hideSelf]="true"
+	[meeting]="meeting"
+>
 </rtk-audio-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
index dbb17aafd24724b..9fa0eff7807d9be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-tile component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-tile
- [config]="defaultUiConfig"
- [meeting]="meeting"
- [participant]="participant">
+	[config]="defaultUiConfig"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-audio-tile>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
index 1622d030b9255cf..cc99527e230b702 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-audio-visualizer component (Angular Library)
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ An audio visualizer component which visualizes a participants audio.
 ```html
 <!-- component.html -->
 <rtk-audio-visualizer
- [hideMuted]="true"
- [isScreenShare]="true"
- [participant]="participant">
+	[hideMuted]="true"
+	[isScreenShare]="true"
+	[participant]="participant"
+>
 </rtk-audio-visualizer>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
index ff5a9ab19b357c0..6bd382f5ba1c7b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-avatar component (Angular Library)
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ Avatar component which renders a participant's image or their initials.
 
 ```html
 <!-- component.html -->
-<rtk-avatar
- participant="example"
- size="md"
- variant="circular">
-</rtk-avatar>
+<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
index b310482b33cdfe8..942b66a929beefc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-breakout-room-manager component (Angular Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-breakout-room-manager
- [allowDelete]="true"
- [assigningParticipants]="true"
- [defaultExpanded]="true">
+	[allowDelete]="true"
+	[assigningParticipants]="true"
+	[defaultExpanded]="true"
+>
 </rtk-breakout-room-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
index 2d1f1e58d56e53f..8d2a38f304f03fd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-breakout-room-participants component (Angular
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-breakout-room-participants
- [meeting]="meeting"
- participantIds="example"
- selectedParticipantIds="example">
+	[meeting]="meeting"
+	participantIds="example"
+	selectedParticipantIds="example"
+>
 </rtk-breakout-room-participants>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
index bbe7a129471cfef..6b60a42d4f64b07 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-breakout-rooms-manager component (Angular Lib
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-breakout-rooms-manager
- [meeting]="meeting">
-</rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager [meeting]="meeting"> </rtk-breakout-rooms-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
index dab4a3a9ced6758..e769d064ce27906 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-breakout-rooms-toggle component (Angular Libr
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A button which toggles visibility of breakout rooms.
 ```html
 <!-- component.html -->
 <rtk-breakout-rooms-toggle
- [iconPack]="defaultIconPack"
- [meeting]="meeting"
- size="md">
+	[iconPack]="defaultIconPack"
+	[meeting]="meeting"
+	size="md"
+>
 </rtk-breakout-rooms-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
index 706f133335069c4..a9399e40c4b7a2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-broadcast-message-modal component (Angular Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-broadcast-message-modal
- [meeting]="meeting">
-</rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal [meeting]="meeting"> </rtk-broadcast-message-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
index ed08f480b320ab1..49d3ca7ffe6a357 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-button component (Angular Library)
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A button that follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-button
- [disabled]="true"
- [kind]="buttonkind"
- [reverse]="true">
+<rtk-button [disabled]="true" [kind]="buttonkind" [reverse]="true">
 </rtk-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
index 755404225238040..92270e3c97fe0e1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-camera-selector component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -39,9 +41,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-camera-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-camera-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
index 00b9d2b1e4bdd06..db38dc91c0aac70 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-camera-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles your camera.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ A button which toggles your camera.
 
 ```html
 <!-- component.html -->
-<rtk-camera-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-camera-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-camera-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
index 66da419d1dea460..5dc17611c79b114 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-caption-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-caption-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-caption-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-caption-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
index ee2887a10f7e46a..b6ff46e4d62c8d9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat-composer-ui component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-composer-ui
- [canSendFiles]="true"
- [canSendTextMessage]="true"
- size="md">
+	[canSendFiles]="true"
+	[canSendTextMessage]="true"
+	size="md"
+>
 </rtk-chat-composer-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
index 407b10b43a4197f..3b98703d1ac78cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-chat-composer-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
@@ -37,9 +38,9 @@ A component which renders a chat composer
 ```html
 <!-- component.html -->
 <rtk-chat-composer-view
- [canSendFiles]="true"
- [canSendTextMessage]="true"
- inputTextPlaceholder="example">
+	[canSendFiles]="true"
+	[canSendTextMessage]="true"
+	inputTextPlaceholder="example"
+>
 </rtk-chat-composer-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
index 400bbe3d46a8aaa..18489ada36fdf99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
@@ -5,9 +5,10 @@ description: API reference for rtk-chat-header component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
@@ -17,4 +18,3 @@ products:
 <!-- component.html -->
 <rtk-chat-header></rtk-chat-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
index de48d16b7b4d731..98cb5beca666769 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
@@ -5,29 +5,30 @@ description: API reference for rtk-chat-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
@@ -42,10 +43,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-message
- [alignRight]="true"
- [canDelete]="true"
- [canEdit]="true">
+<rtk-chat-message [alignRight]="true" [canDelete]="true" [canEdit]="true">
 </rtk-chat-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
index ce18aa44fb427c7..b42f6dc5f8f79eb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-chat-messages-ui-paginated component (Angular
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui-paginated
- [meeting]="meeting"
- [privateChatRecipient]="participant | null"
- size="md">
+	[meeting]="meeting"
+	[privateChatRecipient]="participant | null"
+	size="md"
+>
 </rtk-chat-messages-ui-paginated>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
index 30863c471104539..5241b26b67f1ef7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-chat-messages-ui component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui
- [canPinMessages]="true"
- [messages]="[]"
- selectedGroup="example">
+	[canPinMessages]="true"
+	[messages]="[]"
+	selectedGroup="example"
+>
 </rtk-chat-messages-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
index c523cd074c0f8b5..674604a158dad2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-search-results component (Angular Librar
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-search-results
- channelId="example"
- [meeting]="meeting"
- query="example">
+	channelId="example"
+	[meeting]="meeting"
+	query="example"
+>
 </rtk-chat-search-results>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
index 0ab9edbe1fcae7c..784cf425f1ad9a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-chat-selector-ui component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-selector-ui
- [groups]="[]"
- selectedGroupId="example"
- selfUserId="example">
+	[groups]="[]"
+	selectedGroupId="example"
+	selfUserId="example"
+>
 </rtk-chat-selector-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
index e7e5178d7c5072b..ef6a41c79405f4a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-selector component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-selector
- [meeting]="meeting"
- size="md">
-</rtk-chat-selector>
+<rtk-chat-selector [meeting]="meeting" size="md"> </rtk-chat-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
index 1973396bb8401c2..942cba2a0f25e3c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
@@ -5,23 +5,28 @@ description: API reference for rtk-chat-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of chat.
- You need to pass the `meeting` object to it to see the unread messages count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'chat' }
- ```
+You need to pass the `meeting` object to it to see the unread messages count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "chat";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -36,10 +41,6 @@ A button which toggles visibility of chat.
 
 ```html
 <!-- component.html -->
-<rtk-chat-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-chat-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-chat-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
index 12504ff17633de3..b968cfe975421fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat component (Angular Library)
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 
 ```html
 <!-- component.html -->
-<rtk-chat
- [meeting]="meeting"
- size="md">
-</rtk-chat>
+<rtk-chat [meeting]="meeting" size="md"> </rtk-chat>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
index fe930adaf1f7baf..eea055224c112f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-clock component (Angular Library)
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ Shows the time elapsed in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-clock
- [meeting]="meeting"
- size="md">
-</rtk-clock>
+<rtk-clock [meeting]="meeting" size="md"> </rtk-clock>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
index 9af1775bf822f6f..cd3a2dc87b17a9f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-confirmation-modal component (Angular Library
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,8 +30,5 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-confirmation-modal
- [meeting]="meeting">
-</rtk-confirmation-modal>
+<rtk-confirmation-modal [meeting]="meeting"> </rtk-confirmation-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
index 52a23c6c3a7c14b..85344ab73bbbe9e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-controlbar-button component (Angular Library)
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A skeleton component used for composing custom controlbar buttons.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar-button
- [brandIcon]="true"
- [disabled]="true"
- icon="example">
+<rtk-controlbar-button [brandIcon]="true" [disabled]="true" icon="example">
 </rtk-controlbar-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
index e7d739a49130cb7..f06437464f138a2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-controlbar component (Angular Library)
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,10 +34,6 @@ Controlbar component provides you with various designs as variants.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar
- [disableRender]="true"
- [meeting]="meeting"
- size="md">
+<rtk-controlbar [disableRender]="true" [meeting]="meeting" size="md">
 </rtk-controlbar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
index 1dcbd9f1997daff..61d79e5a7230d1b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-counter component (Angular Library)
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A number picker with increment and decrement buttons.
 
 ```html
 <!-- component.html -->
-<rtk-counter
- minValue="42"
- size="md"
- value="42">
-</rtk-counter>
+<rtk-counter minValue="42" size="md" value="42"> </rtk-counter>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
index 958771b9756d2be..b878475ad72fa65 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-audio component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-audio
- [meeting]="meeting"
- size="md">
-</rtk-debugger-audio>
+<rtk-debugger-audio [meeting]="meeting" size="md"> </rtk-debugger-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
index d6002b9a6aecd84..c78c0ff33fa40dd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-screenshare component (Angular Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-screenshare
- [meeting]="meeting"
- size="md">
+<rtk-debugger-screenshare [meeting]="meeting" size="md">
 </rtk-debugger-screenshare>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
index 60e7d5bb6289f9b..ea1d6d90d2b938e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-system component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-system
- [meeting]="meeting"
- size="md">
-</rtk-debugger-system>
+<rtk-debugger-system [meeting]="meeting" size="md"> </rtk-debugger-system>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
index 6c7e30bd9fcf7f5..3e69cb73fef0b73 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-debugger-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-debugger-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-debugger-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
index d5210d91dc9db4d..2a84fafef9eb27b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-video component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-video
- [meeting]="meeting"
- size="md">
-</rtk-debugger-video>
+<rtk-debugger-video [meeting]="meeting" size="md"> </rtk-debugger-video>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
index 40b74b2e1ab8c69..f73efac1fa88dbf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-debugger component (Angular Library)
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,5 @@ A troubleshooting component to identify and fix any issues in the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-debugger
- [meeting]="meeting"
- size="md">
-</rtk-debugger>
+<rtk-debugger [meeting]="meeting" size="md"> </rtk-debugger>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
index c1de127979df06a..db0a49fdc7627bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
@@ -5,24 +5,26 @@ description: API reference for rtk-dialog-manager component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -37,9 +39,5 @@ A component which handles all dialog elements in a component such as:
 
 ```html
 <!-- component.html -->
-<rtk-dialog-manager
- [meeting]="meeting"
- size="md">
-</rtk-dialog-manager>
+<rtk-dialog-manager [meeting]="meeting" size="md"> </rtk-dialog-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
index 9635ed56702713b..76e69151c16a283 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-dialog component (Angular Library)
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A dialog component.
 ```html
 <!-- component.html -->
 <rtk-dialog
- [disableEscapeKey]="true"
- [hideCloseButton]="true"
- [meeting]="meeting">
+	[disableEscapeKey]="true"
+	[hideCloseButton]="true"
+	[meeting]="meeting"
+>
 </rtk-dialog>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
index a8934fc38c1e469..41ba93a5da182cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-emoji-picker-button component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker-button
- [isActive]="true">
-</rtk-emoji-picker-button>
+<rtk-emoji-picker-button [isActive]="true"> </rtk-emoji-picker-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
index 4247ddbd5c1ce10..01b94d697105b34 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-emoji-picker component (Angular Library)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A very simple emoji picker component.
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker
- [focusWhenOpened]="true">
-</rtk-emoji-picker>
+<rtk-emoji-picker [focusWhenOpened]="true"> </rtk-emoji-picker>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
index b354fa28a6845bf..b2ad7d8f8e7eea2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-ended-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A screen which shows a meeting has ended.
 
 ```html
 <!-- component.html -->
-<rtk-ended-screen
- [meeting]="meeting"
- size="md">
-</rtk-ended-screen>
+<rtk-ended-screen [meeting]="meeting" size="md"> </rtk-ended-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
index 8344ce746896053..57ffa8f9039d89a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-file-dropzone component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-dropzone
- [hostEl]="htmlelement">
-</rtk-file-dropzone>
+<rtk-file-dropzone [hostEl]="htmlelement"> </rtk-file-dropzone>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
index 48e4cca9eee6790..858399c5abccaed 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-file-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ A component which renders a file message.
 
 ```html
 <!-- component.html -->
-<rtk-file-message-view
- name="example"
- size="42"
- url="example">
+<rtk-file-message-view name="example" size="42" url="example">
 </rtk-file-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
index a19ab17f5b413c7..d32dd9edc995033 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-file-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-message
- [isContinued]="true"
- [message]="filemessage"
- [now]="date">
+<rtk-file-message [isContinued]="true" [message]="filemessage" [now]="date">
 </rtk-file-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
index 4bda6955ac1042e..2470555e83eff13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-file-picker-button component (Angular Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-file-picker-button
- filter="example"
- [icon]="defaultIconPack"
- label="example">
+	filter="example"
+	[icon]="defaultIconPack"
+	label="example"
+>
 </rtk-file-picker-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
index f1d002421e860d8..04544ab3ecc21c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-fullscreen-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles full screen mode for any
- existing `rtk-meeting` component in the DOM.
+existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property        | Type                | Required | Default           | Description                  |
+| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
+| `size`          | `Size`              | ✅       | -                 | Size                         |
+| `states`        | `States`            | ✅       | -                 | States object                |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
+| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
+| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ A button which toggles full screen mode for any
 
 ```html
 <!-- component.html -->
-<rtk-fullscreen-toggle
- size="md"
- [targetElement]="htmlelement"
- variant="button">
+<rtk-fullscreen-toggle size="md" [targetElement]="htmlelement" variant="button">
 </rtk-fullscreen-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
index 535638be929e69a..04a546d6b3f89a5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-grid-pagination component (Angular Library)
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A component which allows you to change current page and view mode
 ```html
 <!-- component.html -->
 <rtk-grid-pagination
- [meeting]="meeting"
- size="md"
- [variant]="gridpaginationvariants">
+	[meeting]="meeting"
+	size="md"
+	[variant]="gridpaginationvariants"
+>
 </rtk-grid-pagination>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
index bd36da17a99fc2e..0c97b4b23ee5ea2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-grid component (Angular Library)
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
@@ -36,10 +37,5 @@ The main grid component which abstracts all the grid handling logic and renders
 
 ```html
 <!-- component.html -->
-<rtk-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
-</rtk-grid>
+<rtk-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
index 6308160dae44850..c09018ff727582b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-header component (Angular Library)
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,10 +34,5 @@ A component that houses all the header components.
 
 ```html
 <!-- component.html -->
-<rtk-header
- [disableRender]="true"
- [meeting]="meeting"
- size="md">
-</rtk-header>
+<rtk-header [disableRender]="true" [meeting]="meeting" size="md"> </rtk-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
index b78675a57bf3f47..fdb32d3739e666a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-icon component (Angular Library)
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
@@ -28,10 +29,5 @@ An icon component which accepts an svg string and renders it.
 
 ```html
 <!-- component.html -->
-<rtk-icon
- icon="example"
- size="md"
- variant="primary">
-</rtk-icon>
+<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
index 98bd3fd010f365a..a5a0b562a10c71e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-idle-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A screen that handles the idle state,
 
 ```html
 <!-- component.html -->
-<rtk-idle-screen
- [meeting]="meeting">
-</rtk-idle-screen>
+<rtk-idle-screen [meeting]="meeting"> </rtk-idle-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
index ae4305bd0b859b1..b6624557f5b530d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-image-message-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A component which renders an image message.
 
 ```html
 <!-- component.html -->
-<rtk-image-message-view
- url="example">
-</rtk-image-message-view>
+<rtk-image-message-view url="example"> </rtk-image-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
index e61a9e43a995966..57f711994dc6ea4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-image-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-image-message
- [isContinued]="true"
- [message]="imagemessage"
- [now]="date">
+<rtk-image-message [isContinued]="true" [message]="imagemessage" [now]="date">
 </rtk-image-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
index ce55f03e3a1012b..a5c26ec0490046f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-image-viewer component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows an image sent via chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-viewer
- [image]="imagemessage"
- size="md">
-</rtk-image-viewer>
+<rtk-image-viewer [image]="imagemessage" size="md"> </rtk-image-viewer>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
index 87a5a453715b10c..4a0ff811c795716 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
@@ -5,11 +5,12 @@ description: API reference for rtk-information-tooltip component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
@@ -24,8 +25,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-information-tooltip
- [iconPack]="defaultIconPack">
+<rtk-information-tooltip [iconPack]="defaultIconPack">
 </rtk-information-tooltip>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
index 877a7a5fef233c5..54215fd0fe361ad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-join-stage component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-join-stage
- [dataConfig]="modaldataconfig"
- [meeting]="meeting"
- size="md">
+<rtk-join-stage [dataConfig]="modaldataconfig" [meeting]="meeting" size="md">
 </rtk-join-stage>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
index 28820eb49fe7d0e..57d4746414928cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-leave-button component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description |
+| ---------- | ------------------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size`              | ✅       | -                 | Size        |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A button which toggles visilibility of the leave confirmation dialog.
 
 ```html
 <!-- component.html -->
-<rtk-leave-button
- size="md"
- variant="button">
-</rtk-leave-button>
+<rtk-leave-button size="md" variant="button"> </rtk-leave-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
index 46d14fe211c640f..97cb75f991a2535 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-leave-meeting component (Angular Library)
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A component which allows you to leave a meeting or
 
 ```html
 <!-- component.html -->
-<rtk-leave-meeting
- [meeting]="meeting">
-</rtk-leave-meeting>
+<rtk-leave-meeting [meeting]="meeting"> </rtk-leave-meeting>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
index 04858c6a723e9f5..5822982df0f5a65 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-indicator component (Angular Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-indicator
- [meeting]="meeting"
- size="md">
+<rtk-livestream-indicator [meeting]="meeting" size="md">
 </rtk-livestream-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
index 35b411555cd3561..4aedae8a958db06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-player component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-player
- [meeting]="meeting"
- size="md">
-</rtk-livestream-player>
+<rtk-livestream-player [meeting]="meeting" size="md"> </rtk-livestream-player>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
index b965a5d73aa5a9c..43e52a53ecca76d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-livestream-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -28,10 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-livestream-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-livestream-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
index c7422b474f26bde..8a910a96dda8544 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-logo component (Angular Library)
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 
 ```html
 <!-- component.html -->
-<rtk-logo
- logoUrl="example"
- [meeting]="meeting">
-</rtk-logo>
+<rtk-logo logoUrl="example" [meeting]="meeting"> </rtk-logo>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
index a7f872c4122307b..b5b816456292b1a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
@@ -5,12 +5,13 @@ description: API reference for rtk-markdown-view component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
@@ -25,9 +26,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-markdown-view
- maxLength="42"
- text="example">
-</rtk-markdown-view>
+<rtk-markdown-view maxLength="42" text="example"> </rtk-markdown-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
index 31cbdb86d3736f2..6adbeb63b44a99a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-meeting-title component (Angular Library)
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ Displays the title of the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-meeting-title
- [meeting]="meeting">
-</rtk-meeting-title>
+<rtk-meeting-title [meeting]="meeting"> </rtk-meeting-title>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
index f1727781860d6f0..fb1306311adea67 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
@@ -5,27 +5,28 @@ description: API reference for rtk-meeting component (Angular Library)
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
@@ -41,9 +42,9 @@ A single component which renders an entire meeting UI.
 ```html
 <!-- component.html -->
 <rtk-meeting
- [applyDesignSystem]="true"
- [config]="defaultUiConfig"
- [gridLayout]="gridlayout1">
+	[applyDesignSystem]="true"
+	[config]="defaultUiConfig"
+	[gridLayout]="gridlayout1"
+>
 </rtk-meeting>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
index b640c6b002c812a..ec230b806744c2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-menu-item component (Angular Library)
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -29,9 +30,6 @@ A menu item component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-item
- [menuVariant]="'primary' | 'secondary'"
- size="md">
+<rtk-menu-item [menuVariant]="'primary' | 'secondary'" size="md">
 </rtk-menu-item>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
index 7637b0961658634..cc93e411c5ade5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-menu-list component (Angular Library)
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A menu list component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-list
- [menuVariant]="'primary' | 'secondary'">
-</rtk-menu-list>
+<rtk-menu-list [menuVariant]="'primary' | 'secondary'"> </rtk-menu-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
index 166ba3bed89a7cc..75bea868f269ae2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-menu component (Angular Library)
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A menu component.
 
 ```html
 <!-- component.html -->
-<rtk-menu
- offset="42"
- [placement]="placement"
- size="md">
-</rtk-menu>
+<rtk-menu offset="42" [placement]="placement" size="md"> </rtk-menu>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
index 3a2c6f64fdbcb64..c6e6a410829ecf7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-message-list-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders list of messages.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
-| `messages` | `Message[]` | ✅ | - | Messages to render |
-| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
-| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
+| Property            | Type                                | Required | Default           | Description                                                                   |
+| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
+| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
+| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
+| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
+| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
+| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
+| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ A component which renders list of messages.
 ```html
 <!-- component.html -->
 <rtk-message-list-view
- estimateItemSize="42"
- [loadMore]="(lastmessage: message)"
- [messages]="[]">
+	estimateItemSize="42"
+	[loadMore]="(lastmessage: message)"
+	[messages]="[]"
+>
 </rtk-message-list-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
index b9ab493f273c95c..cf2cd2949c924ba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
@@ -5,24 +5,25 @@ description: API reference for rtk-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
@@ -37,10 +38,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-message-view
- [actions]="[]"
- authorName="example"
- avatarUrl="example">
+<rtk-message-view [actions]="[]" authorName="example" avatarUrl="example">
 </rtk-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
index a99b4422c32892b..2f9fa6aaf5f2e0e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-mic-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles your microphone.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ A button which toggles your microphone.
 
 ```html
 <!-- component.html -->
-<rtk-mic-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-mic-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-mic-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
index e387ad7b10c0480..1cd58cb2ab66302 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-microphone-selector component (Angular Librar
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -39,9 +41,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-microphone-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-microphone-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
index fce5f3ee1150759..bc1d583c35d077b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
@@ -5,26 +5,27 @@ description: API reference for rtk-mixed-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -39,10 +40,5 @@ A grid component which handles screenshares, plugins and participants.
 
 ```html
 <!-- component.html -->
-<rtk-mixed-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
-</rtk-mixed-grid>
+<rtk-mixed-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-mixed-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
index da82abf95847f76..b6d4f9cd6a2fb91 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
@@ -5,20 +5,24 @@ description: API reference for rtk-more-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -33,8 +37,5 @@ A button which toggles visibility of a more menu.
 
 ```html
 <!-- component.html -->
-<rtk-more-toggle
- size="md">
-</rtk-more-toggle>
+<rtk-more-toggle size="md"> </rtk-more-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
index 267acdbbab6197c..e1a63a750b62c5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-mute-all-button component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -28,10 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-button
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-mute-all-button [meeting]="meeting" size="md" variant="button">
 </rtk-mute-all-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
index fd686e57c8f8e71..406a2e94c9b8462 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-mute-all-confirmation component (Angular Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-confirmation
- [meeting]="meeting">
-</rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation [meeting]="meeting"> </rtk-mute-all-confirmation>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
index ab2fdfe0ef135b8..4f21452d80b34f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-name-tag component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A component which shows a participant's name.
 ```html
 <!-- component.html -->
 <rtk-name-tag
- [isScreenShare]="true"
- [meeting]="meeting"
- [participant]="participant">
+	[isScreenShare]="true"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-name-tag>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
index 7a1feeae085082d..2776b79be409e22 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-network-indicator component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-network-indicator
- [isScreenShare]="true"
- [meeting]="meeting"
- [participant]="participant">
+	[isScreenShare]="true"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-network-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
index 4bb7b34755028e3..3125a0458248d60 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-notification component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ A component which shows a notification.
 
 ```html
 <!-- component.html -->
-<rtk-notification
- [notification]="notification"
- [paused]="true"
- size="md">
+<rtk-notification [notification]="notification" [paused]="true" size="md">
 </rtk-notification>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
index 7d3957e28575b5d..29874314310420f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-notifications component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -33,9 +34,5 @@ A component which handles notifications.
 
 ```html
 <!-- component.html -->
-<rtk-notifications
- [meeting]="meeting"
- size="md">
-</rtk-notifications>
+<rtk-notifications [meeting]="meeting" size="md"> </rtk-notifications>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
index da6b60ff9959d29..f7b0a744c973685 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-overlay-modal component (Angular Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,8 +30,5 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-overlay-modal
- [meeting]="meeting">
-</rtk-overlay-modal>
+<rtk-overlay-modal [meeting]="meeting"> </rtk-overlay-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
index a37ab406bfe13c8..3a22d1b7e3c7e6a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-paginated-list component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-paginated-list
- [autoScroll]="true"
- [createNodes]="[]"
- emptyListLabel="example">
+	[autoScroll]="true"
+	[createNodes]="[]"
+	emptyListLabel="example"
+>
 </rtk-paginated-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
index a77302d526005b6..dc709547d180829 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participant-count component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-participant-count
- [meeting]="meeting"
- size="md">
-</rtk-participant-count>
+<rtk-participant-count [meeting]="meeting" size="md"> </rtk-participant-count>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
index fbdb48390bc0073..354d7029075e454 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-participant-setup component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,14 +34,14 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participant-setup
- [isPreview]="true"
- [nameTagPosition]="| 'bottom-left'
+	[isPreview]="true"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
     | 'top-center'"
- [participant]="participant">
+	[participant]="participant"
+>
 </rtk-participant-setup>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
index a87d31044667f2c..e4417402b7a4053 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-participant-tile component (Angular Library)
 products:
   - realtime
 ---
+
 A component which plays a participants video and allows for placement
- of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -37,14 +38,14 @@ A component which plays a participants video and allows for placement
 ```html
 <!-- component.html -->
 <rtk-participant-tile
- [isPreview]="true"
- [meeting]="meeting"
- [nameTagPosition]="| 'bottom-left'
+	[isPreview]="true"
+	[meeting]="meeting"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'">
+    | 'top-center'"
+>
 </rtk-participant-tile>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
index 1dda330a33b1b70..2cb75bb1541d4dc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-participant component (Angular Library)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A participant entry component used inside `rtk-participants` which shows data li
 ```html
 <!-- component.html -->
 <rtk-participant
- [meeting]="meeting"
- [participant]="participant"
- [view]="participantviewmode">
+	[meeting]="meeting"
+	[participant]="participant"
+	[view]="participantviewmode"
+>
 </rtk-participant>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
index 8d1dd8043548405..f35effb4020a5a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-audio component (Angular Library
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
@@ -30,8 +31,8 @@ A component which plays all the audio from participants and screenshares.
 ```html
 <!-- component.html -->
 <rtk-participants-audio
- [meeting]="meeting"
- [preloadedAudioElem]="htmlaudioelement">
+	[meeting]="meeting"
+	[preloadedAudioElem]="htmlaudioelement"
+>
 </rtk-participants-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
index 805eb1630f5565d..a0ad0b85a8677ae 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-participants-stage-list component (Angular Li
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
@@ -36,9 +37,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-participants-stage-list
- [hideHeader]="true"
- [meeting]="meeting"
- search="example">
+	[hideHeader]="true"
+	[meeting]="meeting"
+	search="example"
+>
 </rtk-participants-stage-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
index 0963dbb1699ef78..883999ff9c3ed7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-stage-queue component (Angular L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-stage-queue
- [meeting]="meeting"
- size="md"
- [view]="participantsviewmode">
+	[meeting]="meeting"
+	size="md"
+	[view]="participantsviewmode"
+>
 </rtk-participants-stage-queue>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
index dea0f244da4a0d5..bb5751a926de3b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
@@ -5,22 +5,27 @@ description: API reference for rtk-participants-toggle component (Angular Librar
 products:
   - realtime
 ---
+
 A button which toggles visibility of participants.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'participants' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "participants";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -35,10 +40,6 @@ A button which toggles visibility of participants.
 
 ```html
 <!-- component.html -->
-<rtk-participants-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-participants-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-participants-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
index 4ae0ae15cc28d5d..db2b020c8b88ab8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-participants-viewer-list component (Angular L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-viewer-list
- [hideHeader]="true"
- [meeting]="meeting"
- search="example">
+	[hideHeader]="true"
+	[meeting]="meeting"
+	search="example"
+>
 </rtk-participants-viewer-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
index 073a3e467d62514..f31d8a204b73fd3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-waiting-list component (Angular
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-waiting-list
- [meeting]="meeting"
- size="md"
- [view]="participantsviewmode">
+	[meeting]="meeting"
+	size="md"
+	[view]="participantsviewmode"
+>
 </rtk-participants-waiting-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
index f1984d1798d8879..b771206de02ce49 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-participants component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-participants
- [defaultParticipantsTabId]="participantstabid"
- [meeting]="meeting"
- size="md">
+	[defaultParticipantsTabId]="participantstabid"
+	[meeting]="meeting"
+	size="md"
+>
 </rtk-participants>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
index dec4a8e63bdaed2..683752123d4ac43 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-permissions-message component (Angular Librar
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A component which shows permission related troubleshooting
 
 ```html
 <!-- component.html -->
-<rtk-permissions-message
- [meeting]="meeting">
-</rtk-permissions-message>
+<rtk-permissions-message [meeting]="meeting"> </rtk-permissions-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
index 94aad79b50a76a9..930b8fea7a6f96a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-pinned-message-selector component (Angular Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pinned-message-selector
- [meeting]="meeting">
-</rtk-pinned-message-selector>
+<rtk-pinned-message-selector [meeting]="meeting"> </rtk-pinned-message-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
index ff56f4f7c8fc58c..3b85d1e48dc9a96 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-pip-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pip-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-pip-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-pip-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
index 2adc29e0fe4d37f..8bc1fdc55db3407 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-plugin-main component (Angular Library)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which loads a plugin.
 
 ```html
 <!-- component.html -->
-<rtk-plugin-main
- [meeting]="meeting"
- [plugin]="rtkplugin">
-</rtk-plugin-main>
+<rtk-plugin-main [meeting]="meeting" [plugin]="rtkplugin"> </rtk-plugin-main>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
index 1e55dfd168ff802..78da2d41fbb440d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
@@ -5,22 +5,27 @@ description: API reference for rtk-plugins-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of plugins.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'plugins' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "plugins";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -35,10 +40,6 @@ A button which toggles visibility of plugins.
 
 ```html
 <!-- component.html -->
-<rtk-plugins-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-plugins-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-plugins-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
index ef10daccef93a00..916242388b0671a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-plugins component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A component which lists all available plugins from their preset,
 
 ```html
 <!-- component.html -->
-<rtk-plugins
- [meeting]="meeting"
- size="md">
-</rtk-plugins>
+<rtk-plugins [meeting]="meeting" size="md"> </rtk-plugins>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
index ed3e4b10df95868..92e52060d4aa885 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-poll-form component (Angular Library)
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,9 +28,5 @@ A component that lets you create a poll.
 
 ```html
 <!-- component.html -->
-<rtk-poll-form
- [iconPack]="defaultIconPack"
- [t]="rtki18n">
-</rtk-poll-form>
+<rtk-poll-form [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-poll-form>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
index 9c50bc3106f4e74..ef928546a835336 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-poll component (Angular Library)
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A poll component.
 
 ```html
 <!-- component.html -->
-<rtk-poll
- [permissions]="rtkpermissionspreset"
- [poll]="poll"
- self="example">
+<rtk-poll [permissions]="rtkpermissionspreset" [poll]="poll" self="example">
 </rtk-poll>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
index 8ee05f66d6d0c1e..4bc3fdff2d81dca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
@@ -5,23 +5,28 @@ description: API reference for rtk-polls-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of polls.
- You need to pass the `meeting` object to it to see the unread polls count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'polls' }
- ```
+You need to pass the `meeting` object to it to see the unread polls count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "polls";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -36,10 +41,6 @@ A button which toggles visibility of polls.
 
 ```html
 <!-- component.html -->
-<rtk-polls-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-polls-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-polls-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
index 0ccd3069c42b635..32b89fad2be1ffb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-polls component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A component which lists all available plugins a user can access with
 
 ```html
 <!-- component.html -->
-<rtk-polls
- [meeting]="meeting"
- size="md">
-</rtk-polls>
+<rtk-polls [meeting]="meeting" size="md"> </rtk-polls>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
index ad5090fddeb9402..51f3ba8000a0d15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-recording-indicator component (Angular Librar
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,6 @@ A component which indicates the recording status of a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-indicator
- [meeting]="meeting"
- size="md">
+<rtk-recording-indicator [meeting]="meeting" size="md">
 </rtk-recording-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
index 5bc2e14496eecf7..47452de08e7ec1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-recording-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A button which toggles recording state of a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-toggle
- [disabled]="true"
- [meeting]="meeting"
- size="md">
+<rtk-recording-toggle [disabled]="true" [meeting]="meeting" size="md">
 </rtk-recording-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
index dec1ea51ccfddcc..00b6c6adc2aabc0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-screen-share-toggle component (Angular Librar
 products:
   - realtime
 ---
+
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A button which toggles your screenshare.
 
 ```html
 <!-- component.html -->
-<rtk-screen-share-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-screen-share-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-screen-share-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
index f678a4456bcdc0a..ab7da66afebf434 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-screenshare-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which plays a participant's screenshared video.
- It also allows for placement of other components similar to `rtk-participant-tile`.
- This component will not render anything if the participant hasn't start screensharing.
+It also allows for placement of other components similar to `rtk-participant-tile`.
+This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property               | Type                                                                                                                     | Required | Default           | Description             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
+| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
+| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
+| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
+| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
+| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
+| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
+| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
+| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
 
 ## Usage Examples
 
@@ -36,14 +37,14 @@ A component which plays a participant's screenshared video.
 ```html
 <!-- component.html -->
 <rtk-screenshare-view
- [hideFullScreenButton]="true"
- [meeting]="meeting"
- [nameTagPosition]="| 'bottom-left'
+	[hideFullScreenButton]="true"
+	[meeting]="meeting"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'">
+    | 'top-center'"
+>
 </rtk-screenshare-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
index 5818d8214fc8651..066d024c27fab77 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-audio component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -38,9 +40,5 @@ A component which lets to manage your audio devices and audio preferences.
 
 ```html
 <!-- component.html -->
-<rtk-settings-audio
- [meeting]="meeting"
- size="md">
-</rtk-settings-audio>
+<rtk-settings-audio [meeting]="meeting" size="md"> </rtk-settings-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
index 56af8d465416a8d..d003ef750b8f9f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
@@ -5,21 +5,25 @@ description: API reference for rtk-settings-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of settings module.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSettings: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSettings: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description   |
+| ---------- | ------------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`              | ✅       | -                 | Size          |
+| `states`   | `States`            | ✅       | -                 | States object |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
 
 ## Usage Examples
 
@@ -34,9 +38,5 @@ A button which toggles visibility of settings module.
 
 ```html
 <!-- component.html -->
-<rtk-settings-toggle
- size="md"
- variant="button">
-</rtk-settings-toggle>
+<rtk-settings-toggle size="md" variant="button"> </rtk-settings-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
index 19b1a2ff5f132a7..381c51a0e2cf855 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-video component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -38,9 +40,5 @@ A component which lets to manage your camera devices and your video preferences.
 
 ```html
 <!-- component.html -->
-<rtk-settings-video
- [meeting]="meeting"
- size="md">
-</rtk-settings-video>
+<rtk-settings-video [meeting]="meeting" size="md"> </rtk-settings-video>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
index 339be6009cf2424..9789b422d1f2837 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-settings component (Angular Library)
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A settings component to see and change your audio/video devices
 
 ```html
 <!-- component.html -->
-<rtk-settings
- [meeting]="meeting"
- size="md">
-</rtk-settings>
+<rtk-settings [meeting]="meeting" size="md"> </rtk-settings>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
index d142bf62459ec14..1406ce5ff38d369 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-setup-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -32,9 +33,5 @@ A screen shown before joining the meeting, where you can edit your display name,
 
 ```html
 <!-- component.html -->
-<rtk-setup-screen
- [meeting]="meeting"
- size="md">
-</rtk-setup-screen>
+<rtk-setup-screen [meeting]="meeting" size="md"> </rtk-setup-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
index 8126edad79c871c..94db2e01d33f007 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-sidebar-ui component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-sidebar-ui
- currentTab="example"
- [focusCloseButton]="true"
- [hideCloseAction]="true">
+	currentTab="example"
+	[focusCloseButton]="true"
+	[hideCloseAction]="true"
+>
 </rtk-sidebar-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
index bfd8e5e11b5177c..71e210674395a9d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-sidebar component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
@@ -36,9 +37,9 @@ A component which handles the sidebar and
 ```html
 <!-- component.html -->
 <rtk-sidebar
- [defaultSection]="rtksidebarsection"
- [enabledSections]="[]"
- [meeting]="meeting">
+	[defaultSection]="rtksidebarsection"
+	[enabledSections]="[]"
+	[meeting]="meeting"
+>
 </rtk-sidebar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
index ea88ffe55f9f48e..bf202dd85e47787 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-simple-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A grid component which renders only the participants in a simple grid.
 
 ```html
 <!-- component.html -->
-<rtk-simple-grid
- aspectRatio="example"
- gap="42"
- [meeting]="meeting">
+<rtk-simple-grid aspectRatio="example" gap="42" [meeting]="meeting">
 </rtk-simple-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
index c19b21a731b3bcd..16628f891f7fa01 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
@@ -5,26 +5,28 @@ description: API reference for rtk-speaker-selector component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -40,9 +42,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-speaker-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-speaker-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
index 915451bf50a7527..47ea91cffa10d78 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spinner component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ A component which shows an animating spinner.
 
 ```html
 <!-- component.html -->
-<rtk-spinner
- size="md">
-</rtk-spinner>
+<rtk-spinner size="md"> </rtk-spinner>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
index f88cc7f531eac2c..c3e3916f6cc12bb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
@@ -5,27 +5,29 @@ description: API reference for rtk-spotlight-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -40,10 +42,6 @@ A grid component that renders two lists of participants: `pinnedParticipants` an
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
+<rtk-spotlight-grid aspectRatio="example" gap="42" gridSize="md">
 </rtk-spotlight-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
index 60b6debe69e9082..ddb740d3af6b233 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spotlight-indicator component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-indicator
- [meeting]="meeting"
- size="md">
+<rtk-spotlight-indicator [meeting]="meeting" size="md">
 </rtk-spotlight-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
index 8e92fdc9598d17a..27bcf1579495dbe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-stage-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `states`   | `States1`           | ✅       | -                 | States         |
+| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-stage-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-stage-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-stage-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
index ccffa6559353763..0b94a4fd1566c92 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-stage component (Angular Library)
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ A component used as a stage that commonly houses
 
 ```html
 <!-- component.html -->
-<rtk-stage
- [iconPack]="defaultIconPack"
- [t]="rtki18n">
-</rtk-stage>
+<rtk-stage [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-stage>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
index f8993d18641c090..75c781fb19e4ce2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-switch component (Angular Library)
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A switch component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-switch
- [checked]="true"
- [disabled]="true"
- [readonly]="true">
-</rtk-switch>
+<rtk-switch [checked]="true" [disabled]="true" [readonly]="true"> </rtk-switch>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
index 1c8cf7cad9f42ff..339bfe235fceedb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-tab-bar component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-tab-bar
- [activeTab]="tab"
- [layout]="gridlayout1"
- [meeting]="meeting">
+<rtk-tab-bar [activeTab]="tab" [layout]="gridlayout1" [meeting]="meeting">
 </rtk-tab-bar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
index cba219399b00342..b2a412cd7210059 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-text-composer-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders a text composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `placeholder` | `string` | ✅ | - | Placeholder text |
-| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
-| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `value` | `string` | ✅ | - | Default value for text input |
+| Property            | Type                              | Required | Default           | Description                                   |
+| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
+| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
+| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
+| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
+| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
+| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
+| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
+| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
+| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
+| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A component which renders a text composer
 ```html
 <!-- component.html -->
 <rtk-text-composer-view
- [disabled]="true"
- [keyDownHandler]="(e: keyboardevent)"
- maxLength="42">
+	[disabled]="true"
+	[keyDownHandler]="(e: keyboardevent)"
+	maxLength="42"
+>
 </rtk-text-composer-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
index 1ccf18977b7aa7d..45ba2ef88c72b20 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-text-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message-view
- [isMarkdown]="true"
- text="example">
+<rtk-text-message-view [isMarkdown]="true" text="example">
 </rtk-text-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
index 5060b6599375a57..230e3211e03b994 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-text-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-text-message
- [isContinued]="true"
- [message]="textmessage"
- [now]="date">
+<rtk-text-message [isContinued]="true" [message]="textmessage" [now]="date">
 </rtk-text-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
index 4e6f62691aef692..371a6eec0e5bcf2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-tooltip component (Angular Library)
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
@@ -33,10 +34,5 @@ Tooltip component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-tooltip
- delay="42"
- [disabled]="true"
- [kind]="tooltipkind">
-</rtk-tooltip>
+<rtk-tooltip delay="42" [disabled]="true" [kind]="tooltipkind"> </rtk-tooltip>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
index 4f6fe2ff039b589..570133cd5d8d464 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-transcript component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows a transcript.
 
 ```html
 <!-- component.html -->
-<rtk-transcript
- [t]="rtki18n"
- transcript="example">
-</rtk-transcript>
+<rtk-transcript [t]="rtki18n" transcript="example"> </rtk-transcript>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
index 4e6c1192fcba044..578013baff0705a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-transcripts component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,8 +32,5 @@ A component which handles transcripts.
 
 ```html
 <!-- component.html -->
-<rtk-transcripts
- [meeting]="meeting">
-</rtk-transcripts>
+<rtk-transcripts [meeting]="meeting"> </rtk-transcripts>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
index 0bfe8c1b9050c14..8602181f2eb682c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ui-provider component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-ui-provider
- [config]="defaultUiConfig"
- [mode]="meeting"
- [showSetupScreen]="true">
+	[config]="defaultUiConfig"
+	[mode]="meeting"
+	[showSetupScreen]="true"
+>
 </rtk-ui-provider>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
index bb61879c99d4f26..f64a1ff20e41f82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-viewer-count component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-viewer-count
- [meeting]="meeting"
- variant="primary">
-</rtk-viewer-count>
+<rtk-viewer-count [meeting]="meeting" variant="primary"> </rtk-viewer-count>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
index 63be1a12b781fd2..040843c9c08f95e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-virtualized-participant-list component (Angul
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-virtualized-participant-list
- bufferedItemsCount="42"
- [emptyListElement]="htmlelement"
- itemHeight="42">
+	bufferedItemsCount="42"
+	[emptyListElement]="htmlelement"
+	itemHeight="42"
+>
 </rtk-virtualized-participant-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
index 46061d522a85431..ed0bda90edc56eb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-waiting-screen component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-waiting-screen
- [meeting]="meeting">
-</rtk-waiting-screen>
+<rtk-waiting-screen [meeting]="meeting"> </rtk-waiting-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
index 7f6ea96d5eaefa0..8ef6d5dcdfadf48 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
index e270c77642b2c4a..4a58db7ec3bb580 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-ai-transcriptions component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
@@ -24,16 +25,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai-transcriptions>
-</rtk-ai-transcriptions>
+<rtk-ai-transcriptions> </rtk-ai-transcriptions>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ai-transcriptions");
+	const el = document.querySelector("rtk-ai-transcriptions");
 
-  el.initialTranscriptions= [];
-  el.meeting= meeting
+	el.initialTranscriptions = [];
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
index 970e391d75c32bc..a55ac07cacbbec6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ai component (Web Components (HTML) Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai
- size="md">
-</rtk-ai>
+<rtk-ai size="md"> </rtk-ai>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ai");
+	const el = document.querySelector("rtk-ai");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
index 2d9130e9d8e4121..ac1e4eef81b052e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-grid>
-</rtk-audio-grid>
+<rtk-audio-grid> </rtk-audio-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-grid");
+	const el = document.querySelector("rtk-audio-grid");
 
-  el.config= defaultUiConfig
-  el.hideSelf= true;
-  el.meeting= meeting
+	el.config = defaultUiConfig;
+	el.hideSelf = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
index 8959b0dde236c5c..6b7d96a935dd7f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-tile component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-tile>
-</rtk-audio-tile>
+<rtk-audio-tile> </rtk-audio-tile>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-tile");
+	const el = document.querySelector("rtk-audio-tile");
 
-  el.config= defaultUiConfig
-  el.meeting= meeting
-  el.participant= participant
+	el.config = defaultUiConfig;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
index 813eab6b421006a..8ff29c76cd061be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-audio-visualizer component (Web Components (H
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
@@ -31,17 +32,15 @@ An audio visualizer component which visualizes a participants audio.
 ### With Properties
 
 ```html
-<rtk-audio-visualizer>
-</rtk-audio-visualizer>
+<rtk-audio-visualizer> </rtk-audio-visualizer>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-visualizer");
+	const el = document.querySelector("rtk-audio-visualizer");
 
-  el.hideMuted= true;
-  el.isScreenShare= true;
-  el.participant= participant
+	el.hideMuted = true;
+	el.isScreenShare = true;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
index 7f8b81f1043b96d..d3d2acf95812bd9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-avatar component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
@@ -28,18 +29,13 @@ Avatar component which renders a participant's image or their initials.
 ### With Properties
 
 ```html
-<rtk-avatar
- participant="example"
- size="md"
- variant="circular">
-</rtk-avatar>
+<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-avatar");
+	const el = document.querySelector("rtk-avatar");
 
-  el.participant= {};
+	el.participant = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
index 0ffde64de310896..08565892ad5d286 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-breakout-room-manager component (Web Componen
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -31,17 +32,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-room-manager>
-</rtk-breakout-room-manager>
+<rtk-breakout-room-manager> </rtk-breakout-room-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-room-manager");
+	const el = document.querySelector("rtk-breakout-room-manager");
 
-  el.allowDelete= true;
-  el.assigningParticipants= true;
-  el.defaultExpanded= true;
+	el.allowDelete = true;
+	el.assigningParticipants = true;
+	el.defaultExpanded = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
index a27e85c3f7202e5..90bf0a7a6599970 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-breakout-room-participants component (Web Com
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -30,18 +31,18 @@ A component which lists all participants, with ability to
 
 ```html
 <rtk-breakout-room-participants
- participantIds="example"
- selectedParticipantIds="example">
+	participantIds="example"
+	selectedParticipantIds="example"
+>
 </rtk-breakout-room-participants>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-room-participants");
+	const el = document.querySelector("rtk-breakout-room-participants");
 
-  el.meeting= meeting
-  el.participantIds= [];
-  el.selectedParticipantIds= [];
+	el.meeting = meeting;
+	el.participantIds = [];
+	el.selectedParticipantIds = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
index 4d3fe5430be46fe..8186a41e5b921c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-breakout-rooms-manager component (Web Compone
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-manager>
-</rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager> </rtk-breakout-rooms-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-rooms-manager");
+	const el = document.querySelector("rtk-breakout-rooms-manager");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
index 12e8adafccffa1d..330651ce2800cee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-breakout-rooms-toggle component (Web Componen
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
@@ -30,17 +31,14 @@ A button which toggles visibility of breakout rooms.
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-toggle
- size="md">
-</rtk-breakout-rooms-toggle>
+<rtk-breakout-rooms-toggle size="md"> </rtk-breakout-rooms-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-rooms-toggle");
+	const el = document.querySelector("rtk-breakout-rooms-toggle");
 
-  el.iconPack= defaultIconPack
-  el.meeting= meeting
+	el.iconPack = defaultIconPack;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
index c701b24f24c37b6..90a5bf9760e290c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-broadcast-message-modal component (Web Compon
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-broadcast-message-modal>
-</rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal> </rtk-broadcast-message-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-broadcast-message-modal");
+	const el = document.querySelector("rtk-broadcast-message-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
index 190ce0bd634cebf..2257bd8dc185484 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-button component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
@@ -29,16 +30,14 @@ A button that follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-button>
-</rtk-button>
+<rtk-button> </rtk-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-button");
+	const el = document.querySelector("rtk-button");
 
-  el.disabled= true;
-  el.reverse= true;
+	el.disabled = true;
+	el.reverse = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
index 839aea969dea5f1..31e3f2482ecb54c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-camera-selector component (Web Components (HT
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-camera-selector
- size="md">
-</rtk-camera-selector>
+<rtk-camera-selector size="md"> </rtk-camera-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-camera-selector");
+	const el = document.querySelector("rtk-camera-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
index 6062945d8cda350..7726ca148fdf888 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat-composer-ui component (Web Components (H
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-composer-ui
- size="md">
-</rtk-chat-composer-ui>
+<rtk-chat-composer-ui size="md"> </rtk-chat-composer-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-composer-ui");
+	const el = document.querySelector("rtk-chat-composer-ui");
 
-  el.canSendFiles= true;
-  el.canSendTextMessage= true;
+	el.canSendFiles = true;
+	el.canSendTextMessage = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
index 4f0b587d7e57cda..6f24d73d4050be8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-chat-composer-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
@@ -34,17 +35,15 @@ A component which renders a chat composer
 ### With Properties
 
 ```html
-<rtk-chat-composer-view
- inputTextPlaceholder="example">
+<rtk-chat-composer-view inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-composer-view");
+	const el = document.querySelector("rtk-chat-composer-view");
 
-  el.canSendFiles= true;
-  el.canSendTextMessage= true;
+	el.canSendFiles = true;
+	el.canSendTextMessage = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
index 00331fb11033be4..d53fa58a0768116 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
@@ -5,9 +5,10 @@ description: API reference for rtk-chat-header component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
@@ -16,4 +17,3 @@ products:
 ```html
 <rtk-chat-header></rtk-chat-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
index b49edd649f06ee1..67158b1da131121 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
@@ -5,29 +5,30 @@ description: API reference for rtk-chat-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
@@ -40,17 +41,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-message>
-</rtk-chat-message>
+<rtk-chat-message> </rtk-chat-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-message");
+	const el = document.querySelector("rtk-chat-message");
 
-  el.alignRight= true;
-  el.canDelete= true;
-  el.canEdit= true;
+	el.alignRight = true;
+	el.canDelete = true;
+	el.canEdit = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
index 1a1f8d1bb2a313f..9b334cb50256afd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-chat-messages-ui-paginated component (Web Com
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui-paginated
- size="md">
-</rtk-chat-messages-ui-paginated>
+<rtk-chat-messages-ui-paginated size="md"> </rtk-chat-messages-ui-paginated>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-messages-ui-paginated");
+	const el = document.querySelector("rtk-chat-messages-ui-paginated");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
index 4315ce89d3ea880..91b79ea94878ffb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-chat-messages-ui component (Web Components (H
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -30,17 +31,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui
- selectedGroup="example">
-</rtk-chat-messages-ui>
+<rtk-chat-messages-ui selectedGroup="example"> </rtk-chat-messages-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-messages-ui");
+	const el = document.querySelector("rtk-chat-messages-ui");
 
-  el.canPinMessages= true;
-  el.messages= [];
+	el.canPinMessages = true;
+	el.messages = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
index 12510bac6bda05a..fd7ba927fca8daa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-search-results component (Web Components
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,17 +29,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-search-results
- channelId="example"
- query="example">
+<rtk-chat-search-results channelId="example" query="example">
 </rtk-chat-search-results>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-search-results");
+	const el = document.querySelector("rtk-chat-search-results");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
index 88fd33ff9a1e098..713fb73bd989f34 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-chat-selector-ui component (Web Components (H
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
@@ -27,17 +28,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector-ui
- selectedGroupId="example"
- selfUserId="example">
+<rtk-chat-selector-ui selectedGroupId="example" selfUserId="example">
 </rtk-chat-selector-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-selector-ui");
+	const el = document.querySelector("rtk-chat-selector-ui");
 
-  el.groups= [];
+	el.groups = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
index 35043d7c0f2796e..f41ed748ffb2bcf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-selector component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector
- size="md">
-</rtk-chat-selector>
+<rtk-chat-selector size="md"> </rtk-chat-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-selector");
+	const el = document.querySelector("rtk-chat-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
index f1f46fa4254dfc0..d296e1f85861da7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 ### With Properties
 
 ```html
-<rtk-chat
- size="md">
-</rtk-chat>
+<rtk-chat size="md"> </rtk-chat>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat");
+	const el = document.querySelector("rtk-chat");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
index f4befa6dbda7af6..f29acbd05520f7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-clock component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ Shows the time elapsed in a meeting.
 ### With Properties
 
 ```html
-<rtk-clock
- size="md">
-</rtk-clock>
+<rtk-clock size="md"> </rtk-clock>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-clock");
+	const el = document.querySelector("rtk-clock");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
index 59a36b5e16679da..54bd7f2399df487 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-confirmation-modal component (Web Components
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-confirmation-modal>
-</rtk-confirmation-modal>
+<rtk-confirmation-modal> </rtk-confirmation-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-confirmation-modal");
+	const el = document.querySelector("rtk-confirmation-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
index 59c9be5f52f7987..b63c726196d6d84 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-controlbar-button component (Web Components (
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A skeleton component used for composing custom controlbar buttons.
 ### With Properties
 
 ```html
-<rtk-controlbar-button
- icon="example">
-</rtk-controlbar-button>
+<rtk-controlbar-button icon="example"> </rtk-controlbar-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-controlbar-button");
+	const el = document.querySelector("rtk-controlbar-button");
 
-  el.brandIcon= true;
-  el.disabled= true;
+	el.brandIcon = true;
+	el.disabled = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
index c303a5102cb22ac..326a72bac0165d4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-controlbar component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ Controlbar component provides you with various designs as variants.
 ### With Properties
 
 ```html
-<rtk-controlbar
- size="md">
-</rtk-controlbar>
+<rtk-controlbar size="md"> </rtk-controlbar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-controlbar");
+	const el = document.querySelector("rtk-controlbar");
 
-  el.disableRender= true;
-  el.meeting= meeting
+	el.disableRender = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
index 59bbbbf35837964..762c4d9d8d1cfc9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-counter component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
@@ -28,17 +29,14 @@ A number picker with increment and decrement buttons.
 ### With Properties
 
 ```html
-<rtk-counter
- size="md">
-</rtk-counter>
+<rtk-counter size="md"> </rtk-counter>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-counter");
+	const el = document.querySelector("rtk-counter");
 
-  el.minValue= 42;
-  el.value= 42;
+	el.minValue = 42;
+	el.value = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
index 8733f92d520e775..22f1b026cd01b82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-audio component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-audio
- size="md">
-</rtk-debugger-audio>
+<rtk-debugger-audio size="md"> </rtk-debugger-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-audio");
+	const el = document.querySelector("rtk-debugger-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
index f7f80fd287b5ef1..9435b3bec0238c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-screenshare component (Web Component
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-screenshare
- size="md">
-</rtk-debugger-screenshare>
+<rtk-debugger-screenshare size="md"> </rtk-debugger-screenshare>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-screenshare");
+	const el = document.querySelector("rtk-debugger-screenshare");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
index a7cc1725cc28364..a80a0f3c3252295 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-system component (Web Components (HT
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-system
- size="md">
-</rtk-debugger-system>
+<rtk-debugger-system size="md"> </rtk-debugger-system>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-system");
+	const el = document.querySelector("rtk-debugger-system");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
index 84a90649d07675a..9deac224fdf1a02 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-video component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-video
- size="md">
-</rtk-debugger-video>
+<rtk-debugger-video size="md"> </rtk-debugger-video>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-video");
+	const el = document.querySelector("rtk-debugger-video");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
index a8141d499177b06..7d345ee443ecde8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-debugger component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A troubleshooting component to identify and fix any issues in the meeting.
 ### With Properties
 
 ```html
-<rtk-debugger
- size="md">
-</rtk-debugger>
+<rtk-debugger size="md"> </rtk-debugger>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger");
+	const el = document.querySelector("rtk-debugger");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
index ba7f8b4cd15bf85..3709d9d501cd38e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
@@ -5,24 +5,26 @@ description: API reference for rtk-dialog-manager component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -35,16 +37,13 @@ A component which handles all dialog elements in a component such as:
 ### With Properties
 
 ```html
-<rtk-dialog-manager
- size="md">
-</rtk-dialog-manager>
+<rtk-dialog-manager size="md"> </rtk-dialog-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-dialog-manager");
+	const el = document.querySelector("rtk-dialog-manager");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
index 170ade6492a1274..d361f6b14ccdb8b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-dialog component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
@@ -32,17 +33,15 @@ A dialog component.
 ### With Properties
 
 ```html
-<rtk-dialog>
-</rtk-dialog>
+<rtk-dialog> </rtk-dialog>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-dialog");
+	const el = document.querySelector("rtk-dialog");
 
-  el.disableEscapeKey= true;
-  el.hideCloseButton= true;
-  el.meeting= meeting
+	el.disableEscapeKey = true;
+	el.hideCloseButton = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
index f21db9738750267..7060d45d649d00a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-draft-attachment-view component (Web Componen
 products:
   - realtime
 ---
+
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property     | Type                                                 | Required | Default           | Description           |
+| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
+| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
+| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A component which renders the draft attachment to send
 ### With Properties
 
 ```html
-<rtk-draft-attachment-view>
-</rtk-draft-attachment-view>
+<rtk-draft-attachment-view> </rtk-draft-attachment-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-draft-attachment-view");
+	const el = document.querySelector("rtk-draft-attachment-view");
 
-  el.attachment= {};
+	el.attachment = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
index f67d8a0f096c864..be00c3a6e33ad46 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-emoji-picker-button component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
@@ -24,15 +25,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-emoji-picker-button>
-</rtk-emoji-picker-button>
+<rtk-emoji-picker-button> </rtk-emoji-picker-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-emoji-picker-button");
+	const el = document.querySelector("rtk-emoji-picker-button");
 
-  el.isActive= true;
+	el.isActive = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
index a0876babb985962..69aabd63c26f21f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-emoji-picker component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A very simple emoji picker component.
 ### With Properties
 
 ```html
-<rtk-emoji-picker>
-</rtk-emoji-picker>
+<rtk-emoji-picker> </rtk-emoji-picker>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-emoji-picker");
+	const el = document.querySelector("rtk-emoji-picker");
 
-  el.focusWhenOpened= true;
+	el.focusWhenOpened = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
index 6aa6297284ea709..e5388b1585fd982 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-ended-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A screen which shows a meeting has ended.
 ### With Properties
 
 ```html
-<rtk-ended-screen
- size="md">
-</rtk-ended-screen>
+<rtk-ended-screen size="md"> </rtk-ended-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ended-screen");
+	const el = document.querySelector("rtk-ended-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
index a9528f31a65a0cc..fdf7e9e77e382ba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-file-dropzone component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
@@ -24,14 +25,11 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-dropzone>
-</rtk-file-dropzone>
+<rtk-file-dropzone> </rtk-file-dropzone>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-dropzone");
-
+	const el = document.querySelector("rtk-file-dropzone");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
index 1764939b1ca0276..083396274de8c83 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-file-message-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
@@ -27,17 +28,13 @@ A component which renders a file message.
 ### With Properties
 
 ```html
-<rtk-file-message-view
- name="example"
- url="example">
-</rtk-file-message-view>
+<rtk-file-message-view name="example" url="example"> </rtk-file-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-message-view");
+	const el = document.querySelector("rtk-file-message-view");
 
-  el.size= 42;
+	el.size = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
index 811a6cce1a3b65e..936feef21b37fa9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-file-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-message>
-</rtk-file-message>
+<rtk-file-message> </rtk-file-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-message");
+	const el = document.querySelector("rtk-file-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
index 54b3d5dd21d7da8..851138e1627613b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-file-picker-button component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -26,17 +27,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-picker-button
- filter="example"
- label="example">
+<rtk-file-picker-button filter="example" label="example">
 </rtk-file-picker-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-picker-button");
+	const el = document.querySelector("rtk-file-picker-button");
 
-  el.icon= defaultIconPack
+	el.icon = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
index f3865d72720b943..d663d791207416c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-grid-pagination component (Web Components (HT
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A component which allows you to change current page and view mode
 ### With Properties
 
 ```html
-<rtk-grid-pagination
- size="md">
-</rtk-grid-pagination>
+<rtk-grid-pagination size="md"> </rtk-grid-pagination>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-grid-pagination");
+	const el = document.querySelector("rtk-grid-pagination");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
index cf79955eff09681..31eef43afae392f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-grid component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
@@ -34,17 +35,13 @@ The main grid component which abstracts all the grid handling logic and renders
 ### With Properties
 
 ```html
-<rtk-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-grid>
+<rtk-grid aspectRatio="example" gridSize="md"> </rtk-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-grid");
+	const el = document.querySelector("rtk-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
index 1fb6ec7f5c5a1b6..a89c57e5b374cc4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-header component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ A component that houses all the header components.
 ### With Properties
 
 ```html
-<rtk-header
- size="md">
-</rtk-header>
+<rtk-header size="md"> </rtk-header>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-header");
+	const el = document.querySelector("rtk-header");
 
-  el.disableRender= true;
-  el.meeting= meeting
+	el.disableRender = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
index 581f5e42555059a..225e4d075df1fad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-icon component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
@@ -26,17 +27,11 @@ An icon component which accepts an svg string and renders it.
 ### With Properties
 
 ```html
-<rtk-icon
- icon="example"
- size="md"
- variant="primary">
-</rtk-icon>
+<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-icon");
-
+	const el = document.querySelector("rtk-icon");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
index a2e6c178b6c1e82..54a72fdf6f17b5b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-idle-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A screen that handles the idle state,
 ### With Properties
 
 ```html
-<rtk-idle-screen>
-</rtk-idle-screen>
+<rtk-idle-screen> </rtk-idle-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-idle-screen");
+	const el = document.querySelector("rtk-idle-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
index 707341e71c859f2..4faebe0ab376143 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-image-message-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
@@ -26,15 +27,11 @@ A component which renders an image message.
 ### With Properties
 
 ```html
-<rtk-image-message-view
- url="example">
-</rtk-image-message-view>
+<rtk-image-message-view url="example"> </rtk-image-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-message-view");
-
+	const el = document.querySelector("rtk-image-message-view");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
index 76c23bbf2dfca99..cb324944fd49d2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-image-message component (Web Components (HTML
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-image-message>
-</rtk-image-message>
+<rtk-image-message> </rtk-image-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-message");
+	const el = document.querySelector("rtk-image-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
index da7064e9253ab13..b7e74691417c0f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-image-viewer component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -27,15 +28,11 @@ A component which shows an image sent via chat.
 ### With Properties
 
 ```html
-<rtk-image-viewer
- size="md">
-</rtk-image-viewer>
+<rtk-image-viewer size="md"> </rtk-image-viewer>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-viewer");
-
+	const el = document.querySelector("rtk-image-viewer");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
index 7950fc7f2bc101a..f638b70c50e83d4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
@@ -5,11 +5,12 @@ description: API reference for rtk-information-tooltip component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
@@ -22,15 +23,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-information-tooltip>
-</rtk-information-tooltip>
+<rtk-information-tooltip> </rtk-information-tooltip>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-information-tooltip");
+	const el = document.querySelector("rtk-information-tooltip");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
index 36d7fcfd41612fa..7cbac34216b6b9a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-join-stage component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-join-stage
- size="md">
-</rtk-join-stage>
+<rtk-join-stage size="md"> </rtk-join-stage>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-join-stage");
+	const el = document.querySelector("rtk-join-stage");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
index 60d83d6896b419b..7953645ed11d440 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-leave-meeting component (Web Components (HTML
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A component which allows you to leave a meeting or
 ### With Properties
 
 ```html
-<rtk-leave-meeting>
-</rtk-leave-meeting>
+<rtk-leave-meeting> </rtk-leave-meeting>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-leave-meeting");
+	const el = document.querySelector("rtk-leave-meeting");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
index 67707911b550145..7089f2c65e4c3b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-indicator component (Web Component
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-indicator
- size="md">
-</rtk-livestream-indicator>
+<rtk-livestream-indicator size="md"> </rtk-livestream-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-livestream-indicator");
+	const el = document.querySelector("rtk-livestream-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
index 5e6da815b9a6c32..4d35b373ccbafc2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-player component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-player
- size="md">
-</rtk-livestream-player>
+<rtk-livestream-player size="md"> </rtk-livestream-player>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-livestream-player");
+	const el = document.querySelector("rtk-livestream-player");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
index f6713bd26d22ab2..cb8ff8473cd8a3e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-logo component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 ### With Properties
 
 ```html
-<rtk-logo
- logoUrl="example">
-</rtk-logo>
+<rtk-logo logoUrl="example"> </rtk-logo>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-logo");
+	const el = document.querySelector("rtk-logo");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
index d1381ac73ca5828..811851e7e12e984 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
@@ -5,12 +5,13 @@ description: API reference for rtk-markdown-view component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
@@ -23,16 +24,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-markdown-view
- text="example">
-</rtk-markdown-view>
+<rtk-markdown-view text="example"> </rtk-markdown-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-markdown-view");
+	const el = document.querySelector("rtk-markdown-view");
 
-  el.maxLength= 42;
+	el.maxLength = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
index ba9885092147cbb..55697cb504158d1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-meeting-title component (Web Components (HTML
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ Displays the title of the meeting.
 ### With Properties
 
 ```html
-<rtk-meeting-title>
-</rtk-meeting-title>
+<rtk-meeting-title> </rtk-meeting-title>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-meeting-title");
+	const el = document.querySelector("rtk-meeting-title");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
index 0a6abda1bfb826a..753af9e783bf586 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
@@ -5,27 +5,28 @@ description: API reference for rtk-meeting component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
@@ -38,16 +39,14 @@ A single component which renders an entire meeting UI.
 ### With Properties
 
 ```html
-<rtk-meeting>
-</rtk-meeting>
+<rtk-meeting> </rtk-meeting>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-meeting");
+	const el = document.querySelector("rtk-meeting");
 
-  el.applyDesignSystem= true;
-  el.config= defaultUiConfig
+	el.applyDesignSystem = true;
+	el.config = defaultUiConfig;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
index 169675ff5a4498c..c9fd4b7ff50b042 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-menu-item component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,15 +28,11 @@ A menu item component.
 ### With Properties
 
 ```html
-<rtk-menu-item
- size="md">
-</rtk-menu-item>
+<rtk-menu-item size="md"> </rtk-menu-item>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu-item");
-
+	const el = document.querySelector("rtk-menu-item");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
index 88b9d8538638163..6735e67c1b647e8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-menu-list component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -26,14 +27,11 @@ A menu list component.
 ### With Properties
 
 ```html
-<rtk-menu-list>
-</rtk-menu-list>
+<rtk-menu-list> </rtk-menu-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu-list");
-
+	const el = document.querySelector("rtk-menu-list");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
index 12ad508b8b32180..bb093d6585896ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-menu component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A menu component.
 ### With Properties
 
 ```html
-<rtk-menu
- size="md">
-</rtk-menu>
+<rtk-menu size="md"> </rtk-menu>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu");
+	const el = document.querySelector("rtk-menu");
 
-  el.offset= 42;
+	el.offset = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
index cdb30bac0e60ed4..f409f90de250597 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-message-list-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders list of messages.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
-| `messages` | `Message[]` | ✅ | - | Messages to render |
-| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
-| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
+| Property            | Type                                | Required | Default           | Description                                                                   |
+| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
+| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
+| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
+| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
+| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
+| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
+| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
 
 ## Usage Examples
 
@@ -29,16 +30,14 @@ A component which renders list of messages.
 ### With Properties
 
 ```html
-<rtk-message-list-view>
-</rtk-message-list-view>
+<rtk-message-list-view> </rtk-message-list-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-message-list-view");
+	const el = document.querySelector("rtk-message-list-view");
 
-  el.estimateItemSize= 42;
-  el.messages= [];
+	el.estimateItemSize = 42;
+	el.messages = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
index 728e84fc9321401..09def76b8fce5db 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
@@ -5,24 +5,25 @@ description: API reference for rtk-message-view component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
@@ -35,17 +36,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-message-view
- authorName="example"
- avatarUrl="example">
-</rtk-message-view>
+<rtk-message-view authorName="example" avatarUrl="example"> </rtk-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-message-view");
+	const el = document.querySelector("rtk-message-view");
 
-  el.actions= [];
+	el.actions = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
index 1565dc06501cfad..0e2adb948d754a3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-microphone-selector component (Web Components
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-microphone-selector
- size="md">
-</rtk-microphone-selector>
+<rtk-microphone-selector size="md"> </rtk-microphone-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-microphone-selector");
+	const el = document.querySelector("rtk-microphone-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
index d399d66944cd6fc..79ad17a23ebacab 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
@@ -5,26 +5,27 @@ description: API reference for rtk-mixed-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -37,17 +38,13 @@ A grid component which handles screenshares, plugins and participants.
 ### With Properties
 
 ```html
-<rtk-mixed-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-mixed-grid>
+<rtk-mixed-grid aspectRatio="example" gridSize="md"> </rtk-mixed-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-mixed-grid");
+	const el = document.querySelector("rtk-mixed-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
index 43e569451c44e9b..83ee618b019e4c1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
@@ -5,20 +5,24 @@ description: API reference for rtk-more-toggle component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -31,15 +35,11 @@ A button which toggles visibility of a more menu.
 ### With Properties
 
 ```html
-<rtk-more-toggle
- size="md">
-</rtk-more-toggle>
+<rtk-more-toggle size="md"> </rtk-more-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-more-toggle");
-
+	const el = document.querySelector("rtk-more-toggle");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
index 8100fe45db00611..6bb1b8bdce29e58 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-mute-all-confirmation component (Web Componen
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-mute-all-confirmation>
-</rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation> </rtk-mute-all-confirmation>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-mute-all-confirmation");
+	const el = document.querySelector("rtk-mute-all-confirmation");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
index f6cee72609ed898..14082b5393b2820 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-name-tag component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
@@ -30,17 +31,15 @@ A component which shows a participant's name.
 ### With Properties
 
 ```html
-<rtk-name-tag>
-</rtk-name-tag>
+<rtk-name-tag> </rtk-name-tag>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-name-tag");
+	const el = document.querySelector("rtk-name-tag");
 
-  el.isScreenShare= true;
-  el.meeting= meeting
-  el.participant= participant
+	el.isScreenShare = true;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
index a87b7aea196b1a0..b5241b2075c51f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-network-indicator component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
@@ -26,17 +27,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-network-indicator>
-</rtk-network-indicator>
+<rtk-network-indicator> </rtk-network-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-network-indicator");
+	const el = document.querySelector("rtk-network-indicator");
 
-  el.isScreenShare= true;
-  el.meeting= meeting
-  el.participant= participant
+	el.isScreenShare = true;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
index e175a377ba80f6e..4573caf03b498f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-notification component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A component which shows a notification.
 ### With Properties
 
 ```html
-<rtk-notification
- size="md">
-</rtk-notification>
+<rtk-notification size="md"> </rtk-notification>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-notification");
+	const el = document.querySelector("rtk-notification");
 
-  el.paused= true;
+	el.paused = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
index 1854740c5dd7087..c914a13e3c8be1a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-notifications component (Web Components (HTML
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,16 +32,13 @@ A component which handles notifications.
 ### With Properties
 
 ```html
-<rtk-notifications
- size="md">
-</rtk-notifications>
+<rtk-notifications size="md"> </rtk-notifications>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-notifications");
+	const el = document.querySelector("rtk-notifications");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
index 0cb6286a078603e..9364cd4626d354c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-overlay-modal component (Web Components (HTML
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-overlay-modal>
-</rtk-overlay-modal>
+<rtk-overlay-modal> </rtk-overlay-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-overlay-modal");
+	const el = document.querySelector("rtk-overlay-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
index ef79cf0de81f3f7..4cde117f427306e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-paginated-list component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-paginated-list
- emptyListLabel="example">
-</rtk-paginated-list>
+<rtk-paginated-list emptyListLabel="example"> </rtk-paginated-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-paginated-list");
+	const el = document.querySelector("rtk-paginated-list");
 
-  el.autoScroll= true;
-  el.createNodes= [];
+	el.autoScroll = true;
+	el.createNodes = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
index d62e21d5129aa82..7719882d3fb4be7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participant-count component (Web Components (
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-participant-count
- size="md">
-</rtk-participant-count>
+<rtk-participant-count size="md"> </rtk-participant-count>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-count");
+	const el = document.querySelector("rtk-participant-count");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
index caf9dc47c1b7c3f..f6bd84e42574673 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-participant-setup component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -30,16 +31,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-participant-setup>
-</rtk-participant-setup>
+<rtk-participant-setup> </rtk-participant-setup>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-setup");
+	const el = document.querySelector("rtk-participant-setup");
 
-  el.isPreview= true;
-  el.participant= participant
+	el.isPreview = true;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
index 4cab2f0eb1eca60..9a88d9c0a727ee0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-participant-tile component (Web Components (H
 products:
   - realtime
 ---
+
 A component which plays a participants video and allows for placement
- of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -34,16 +35,14 @@ A component which plays a participants video and allows for placement
 ### With Properties
 
 ```html
-<rtk-participant-tile>
-</rtk-participant-tile>
+<rtk-participant-tile> </rtk-participant-tile>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-tile");
+	const el = document.querySelector("rtk-participant-tile");
 
-  el.isPreview= true;
-  el.meeting= meeting
+	el.isPreview = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
index bb8ac1dd6367703..b353795e7b1d39f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-participant component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
@@ -32,16 +33,14 @@ A participant entry component used inside `rtk-participants` which shows data li
 ### With Properties
 
 ```html
-<rtk-participant>
-</rtk-participant>
+<rtk-participant> </rtk-participant>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant");
+	const el = document.querySelector("rtk-participant");
 
-  el.meeting= meeting
-  el.participant= participant
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
index 1f8797c35adb77e..60421301e0a2c48 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-audio component (Web Components
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A component which plays all the audio from participants and screenshares.
 ### With Properties
 
 ```html
-<rtk-participants-audio>
-</rtk-participants-audio>
+<rtk-participants-audio> </rtk-participants-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-audio");
+	const el = document.querySelector("rtk-participants-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
index 01d0f27f271ce7e..fd655a61d22ef33 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-participants-stage-list component (Web Compon
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
@@ -33,17 +34,14 @@ A component which lists all participants, with ability to
 ### With Properties
 
 ```html
-<rtk-participants-stage-list
- search="example">
-</rtk-participants-stage-list>
+<rtk-participants-stage-list search="example"> </rtk-participants-stage-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-stage-list");
+	const el = document.querySelector("rtk-participants-stage-list");
 
-  el.hideHeader= true;
-  el.meeting= meeting
+	el.hideHeader = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
index 963520bc7e53b54..7032a7bf6eae0d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-stage-queue component (Web Compo
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-stage-queue
- size="md">
-</rtk-participants-stage-queue>
+<rtk-participants-stage-queue size="md"> </rtk-participants-stage-queue>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-stage-queue");
+	const el = document.querySelector("rtk-participants-stage-queue");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
index bb79d669d9e7c10..a9ac8f17b8c789a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-participants-viewer-list component (Web Compo
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-viewer-list
- search="example">
-</rtk-participants-viewer-list>
+<rtk-participants-viewer-list search="example"> </rtk-participants-viewer-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-viewer-list");
+	const el = document.querySelector("rtk-participants-viewer-list");
 
-  el.hideHeader= true;
-  el.meeting= meeting
+	el.hideHeader = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
index bb42583235f5ab8..f2090258605a509 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-waiting-list component (Web Comp
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-waiting-list
- size="md">
-</rtk-participants-waiting-list>
+<rtk-participants-waiting-list size="md"> </rtk-participants-waiting-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-waiting-list");
+	const el = document.querySelector("rtk-participants-waiting-list");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
index 1ba0901c553c486..746ec51d0d8660b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-participants component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
@@ -31,16 +32,13 @@ A component which lists all participants, with ability to
 ### With Properties
 
 ```html
-<rtk-participants
- size="md">
-</rtk-participants>
+<rtk-participants size="md"> </rtk-participants>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants");
+	const el = document.querySelector("rtk-participants");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
index 57a566accadd160..150b3a750c1b030 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-permissions-message component (Web Components
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A component which shows permission related troubleshooting
 ### With Properties
 
 ```html
-<rtk-permissions-message>
-</rtk-permissions-message>
+<rtk-permissions-message> </rtk-permissions-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-permissions-message");
+	const el = document.querySelector("rtk-permissions-message");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
index a125dffe72ae892..5d603b6e59daf8b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-pinned-message-selector component (Web Compon
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -24,15 +25,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-pinned-message-selector>
-</rtk-pinned-message-selector>
+<rtk-pinned-message-selector> </rtk-pinned-message-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-pinned-message-selector");
+	const el = document.querySelector("rtk-pinned-message-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
index 35331c64a8d6e7d..2d619085455442a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-plugin-main component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A component which loads a plugin.
 ### With Properties
 
 ```html
-<rtk-plugin-main>
-</rtk-plugin-main>
+<rtk-plugin-main> </rtk-plugin-main>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-plugin-main");
+	const el = document.querySelector("rtk-plugin-main");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
index 162f337bb6592f1..6461be9451e19f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-plugins component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A component which lists all available plugins from their preset,
 ### With Properties
 
 ```html
-<rtk-plugins
- size="md">
-</rtk-plugins>
+<rtk-plugins size="md"> </rtk-plugins>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-plugins");
+	const el = document.querySelector("rtk-plugins");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
index 0272f65d9b3b48e..3e1e182ae6b3e03 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-poll-form component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ A component that lets you create a poll.
 ### With Properties
 
 ```html
-<rtk-poll-form>
-</rtk-poll-form>
+<rtk-poll-form> </rtk-poll-form>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-poll-form");
+	const el = document.querySelector("rtk-poll-form");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
index c7c9985644e098f..74d94c512226da3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-poll component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -29,15 +30,11 @@ A poll component.
 ### With Properties
 
 ```html
-<rtk-poll
- self="example">
-</rtk-poll>
+<rtk-poll self="example"> </rtk-poll>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-poll");
-
+	const el = document.querySelector("rtk-poll");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
index bef8f30b7725c38..98f0ca7892e6576 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-polls component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A component which lists all available plugins a user can access with
 ### With Properties
 
 ```html
-<rtk-polls
- size="md">
-</rtk-polls>
+<rtk-polls size="md"> </rtk-polls>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-polls");
+	const el = document.querySelector("rtk-polls");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
index d30318ecc55e3a5..4d369e04d632069 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-recording-indicator component (Web Components
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A component which indicates the recording status of a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-indicator
- size="md">
-</rtk-recording-indicator>
+<rtk-recording-indicator size="md"> </rtk-recording-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-recording-indicator");
+	const el = document.querySelector("rtk-recording-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
index ec59e9f219e9f7f..a98b211032c1cbb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-recording-toggle component (Web Components (H
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A button which toggles recording state of a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-toggle
- size="md">
-</rtk-recording-toggle>
+<rtk-recording-toggle size="md"> </rtk-recording-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-recording-toggle");
+	const el = document.querySelector("rtk-recording-toggle");
 
-  el.disabled= true;
-  el.meeting= meeting
+	el.disabled = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
index a90c136dff9c22a..1f9320fd4015e72 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-screenshare-view component (Web Components (H
 products:
   - realtime
 ---
+
 A component which plays a participant's screenshared video.
- It also allows for placement of other components similar to `rtk-participant-tile`.
- This component will not render anything if the participant hasn't start screensharing.
+It also allows for placement of other components similar to `rtk-participant-tile`.
+This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property               | Type                                                                                                                     | Required | Default           | Description             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
+| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
+| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
+| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
+| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
+| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
+| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
+| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
+| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
 
 ## Usage Examples
 
@@ -33,16 +34,14 @@ A component which plays a participant's screenshared video.
 ### With Properties
 
 ```html
-<rtk-screenshare-view>
-</rtk-screenshare-view>
+<rtk-screenshare-view> </rtk-screenshare-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-screenshare-view");
+	const el = document.querySelector("rtk-screenshare-view");
 
-  el.hideFullScreenButton= true;
-  el.meeting= meeting
+	el.hideFullScreenButton = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
index be7787328820925..eb030d8fd7c3939 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-audio component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-settings-audio
- size="md">
-</rtk-settings-audio>
+<rtk-settings-audio size="md"> </rtk-settings-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings-audio");
+	const el = document.querySelector("rtk-settings-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
index 523484ecbd3ff73..90b1ddf72d04d58 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-video component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your camera devices and your video preferences.
 ### With Properties
 
 ```html
-<rtk-settings-video
- size="md">
-</rtk-settings-video>
+<rtk-settings-video size="md"> </rtk-settings-video>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings-video");
+	const el = document.querySelector("rtk-settings-video");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
index 4dd3286895b7a97..5dd39a1a89173b9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-settings component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A settings component to see and change your audio/video devices
 ### With Properties
 
 ```html
-<rtk-settings
- size="md">
-</rtk-settings>
+<rtk-settings size="md"> </rtk-settings>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings");
+	const el = document.querySelector("rtk-settings");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
index 622524c4fd4f8c8..2f276604dd912f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-setup-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A screen shown before joining the meeting, where you can edit your display name,
 ### With Properties
 
 ```html
-<rtk-setup-screen
- size="md">
-</rtk-setup-screen>
+<rtk-setup-screen size="md"> </rtk-setup-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-setup-screen");
+	const el = document.querySelector("rtk-setup-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
index f7ebcc96c331885..8902143e96624a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-sidebar-ui component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-sidebar-ui
- currentTab="example">
-</rtk-sidebar-ui>
+<rtk-sidebar-ui currentTab="example"> </rtk-sidebar-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-sidebar-ui");
+	const el = document.querySelector("rtk-sidebar-ui");
 
-  el.focusCloseButton= true;
-  el.hideCloseAction= true;
+	el.focusCloseButton = true;
+	el.hideCloseAction = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
index d03131c5d572243..a22797273800cff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-sidebar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
@@ -33,16 +34,14 @@ A component which handles the sidebar and
 ### With Properties
 
 ```html
-<rtk-sidebar>
-</rtk-sidebar>
+<rtk-sidebar> </rtk-sidebar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-sidebar");
+	const el = document.querySelector("rtk-sidebar");
 
-  el.enabledSections= [];
-  el.meeting= meeting
+	el.enabledSections = [];
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
index 222b8ffafe1e97e..1614ba1605368b3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-simple-grid component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A grid component which renders only the participants in a simple grid.
 ### With Properties
 
 ```html
-<rtk-simple-grid
- aspectRatio="example">
-</rtk-simple-grid>
+<rtk-simple-grid aspectRatio="example"> </rtk-simple-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-simple-grid");
+	const el = document.querySelector("rtk-simple-grid");
 
-  el.gap= 42;
-  el.meeting= meeting
+	el.gap = 42;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
index 1c3c4ff1ad54559..ee3244f04afe45c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
@@ -5,26 +5,28 @@ description: API reference for rtk-speaker-selector component (Web Components (H
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -37,16 +39,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-speaker-selector
- size="md">
-</rtk-speaker-selector>
+<rtk-speaker-selector size="md"> </rtk-speaker-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-speaker-selector");
+	const el = document.querySelector("rtk-speaker-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
index 1b2a10a9aa431a4..729aa072d8e8358 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spinner component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
@@ -25,15 +26,11 @@ A component which shows an animating spinner.
 ### With Properties
 
 ```html
-<rtk-spinner
- size="md">
-</rtk-spinner>
+<rtk-spinner size="md"> </rtk-spinner>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spinner");
-
+	const el = document.querySelector("rtk-spinner");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
index feaee337d8349f1..0aba1ad132414cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
@@ -5,27 +5,29 @@ description: API reference for rtk-spotlight-grid component (Web Components (HTM
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -38,17 +40,13 @@ A grid component that renders two lists of participants: `pinnedParticipants` an
 ### With Properties
 
 ```html
-<rtk-spotlight-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-spotlight-grid>
+<rtk-spotlight-grid aspectRatio="example" gridSize="md"> </rtk-spotlight-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spotlight-grid");
+	const el = document.querySelector("rtk-spotlight-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
index fb0fcf76dbe0835..db3971dcecc6fba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spotlight-indicator component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-spotlight-indicator
- size="md">
-</rtk-spotlight-indicator>
+<rtk-spotlight-indicator size="md"> </rtk-spotlight-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spotlight-indicator");
+	const el = document.querySelector("rtk-spotlight-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
index 0f37d1d696ab3f4..99bc88ba74ef425 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-stage component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A component used as a stage that commonly houses
 ### With Properties
 
 ```html
-<rtk-stage>
-</rtk-stage>
+<rtk-stage> </rtk-stage>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-stage");
+	const el = document.querySelector("rtk-stage");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
index 899e19c8037f8c5..cd5071fb1a445d1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-switch component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ A switch component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-switch>
-</rtk-switch>
+<rtk-switch> </rtk-switch>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-switch");
+	const el = document.querySelector("rtk-switch");
 
-  el.checked= true;
-  el.disabled= true;
-  el.readonly= true;
+	el.checked = true;
+	el.disabled = true;
+	el.readonly = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
index 37b7c05e987b351..0eb2929868dce57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-tab-bar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-tab-bar>
-</rtk-tab-bar>
+<rtk-tab-bar> </rtk-tab-bar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-tab-bar");
+	const el = document.querySelector("rtk-tab-bar");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
index 47adf5034bc93ca..22603bbe1ca64f7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-text-composer-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders a text composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `placeholder` | `string` | ✅ | - | Placeholder text |
-| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
-| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `value` | `string` | ✅ | - | Default value for text input |
+| Property            | Type                              | Required | Default           | Description                                   |
+| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
+| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
+| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
+| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
+| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
+| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
+| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
+| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
+| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
+| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
 
 ## Usage Examples
 
@@ -32,16 +33,14 @@ A component which renders a text composer
 ### With Properties
 
 ```html
-<rtk-text-composer-view>
-</rtk-text-composer-view>
+<rtk-text-composer-view> </rtk-text-composer-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-composer-view");
+	const el = document.querySelector("rtk-text-composer-view");
 
-  el.disabled= true;
-  el.maxLength= 42;
+	el.disabled = true;
+	el.maxLength = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
index 4e15cd5f1fcdb7f..c7802ea87ac4cbc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-text-message-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message-view
- text="example">
-</rtk-text-message-view>
+<rtk-text-message-view text="example"> </rtk-text-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-message-view");
+	const el = document.querySelector("rtk-text-message-view");
 
-  el.isMarkdown= true;
+	el.isMarkdown = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
index 6163072c5b51c71..db080a025087bed 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-text-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-text-message>
-</rtk-text-message>
+<rtk-text-message> </rtk-text-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-message");
+	const el = document.querySelector("rtk-text-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
index 6e38e8bb3887731..ff346f3104717b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-tooltip component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
@@ -31,16 +32,14 @@ Tooltip component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-tooltip>
-</rtk-tooltip>
+<rtk-tooltip> </rtk-tooltip>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-tooltip");
+	const el = document.querySelector("rtk-tooltip");
 
-  el.delay= 42;
-  el.disabled= true;
+	el.delay = 42;
+	el.disabled = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
index f0631ca86b905bd..5ed0883121e7db1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-transcript component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows a transcript.
 ### With Properties
 
 ```html
-<rtk-transcript
- transcript="example">
-</rtk-transcript>
+<rtk-transcript transcript="example"> </rtk-transcript>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-transcript");
+	const el = document.querySelector("rtk-transcript");
 
-  el.transcript= {};
+	el.transcript = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
index f75a986f1cfd9de..c734652bd0fbcd1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-transcripts component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,15 +30,13 @@ A component which handles transcripts.
 ### With Properties
 
 ```html
-<rtk-transcripts>
-</rtk-transcripts>
+<rtk-transcripts> </rtk-transcripts>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-transcripts");
+	const el = document.querySelector("rtk-transcripts");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
index 041148907fcb623..3387ed120b39d4e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ui-provider component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-ui-provider>
-</rtk-ui-provider>
+<rtk-ui-provider> </rtk-ui-provider>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ui-provider");
+	const el = document.querySelector("rtk-ui-provider");
 
-  el.config= defaultUiConfig
-  el.mode= meeting
-  el.showSetupScreen= true;
+	el.config = defaultUiConfig;
+	el.mode = meeting;
+	el.showSetupScreen = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
index 4d041852272b5c6..42c4225721997e0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-viewer-count component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-viewer-count
- variant="primary">
-</rtk-viewer-count>
+<rtk-viewer-count variant="primary"> </rtk-viewer-count>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-viewer-count");
+	const el = document.querySelector("rtk-viewer-count");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
index 9856cd393b4f8d3..d551b47a44c6b52 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-virtualized-participant-list component (Web C
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
@@ -26,16 +27,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-virtualized-participant-list>
-</rtk-virtualized-participant-list>
+<rtk-virtualized-participant-list> </rtk-virtualized-participant-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-virtualized-participant-list");
+	const el = document.querySelector("rtk-virtualized-participant-list");
 
-  el.bufferedItemsCount= 42;
-  el.itemHeight= 42;
+	el.bufferedItemsCount = 42;
+	el.itemHeight = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
index 5486f52a36737c7..f65c231d33c3ab5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-waiting-screen component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-waiting-screen>
-</rtk-waiting-screen>
+<rtk-waiting-screen> </rtk-waiting-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-waiting-screen");
+	const el = document.querySelector("rtk-waiting-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
index 301d8b7d3bff009..248a49136afe991 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
@@ -10,11 +10,11 @@ A pressable menu item within a menu.
 
 ## Properties
 
-| Property   | Type                                  | Required | Default | Description            |
-| ---------- | ------------------------------------- | -------- | ------- | ---------------------- |
-| `children` | `ReactNode`                           | ✅       | -       | Menu item content      |
-| `onClick`  | `(ev) => {}` | ❌       | -       | Press handler callback |
-| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'`        | ❌       | -       | Size variant           |
+| Property   | Type                           | Required | Default | Description            |
+| ---------- | ------------------------------ | -------- | ------- | ---------------------- |
+| `children` | `ReactNode`                    | ✅       | -       | Menu item content      |
+| `onClick`  | `(ev) => {}`                   | ❌       | -       | Press handler callback |
+| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'` | ❌       | -       | Size variant           |
 
 ## Usage Examples
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
index 0ec727fad6c4379..422840190bc663c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkAi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAi } from '@cloudflare/realtimekit-react-ui';
+import { RtkAi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAi />;
+	return <RtkAi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAi } from '@cloudflare/realtimekit-react-ui';
+import { RtkAi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAi
-      meeting={meeting}
-      size="md"
-      view={aiview}
-    />
-  );
+	return <RtkAi meeting={meeting} size="md" view={aiview} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
index 8545071a098a60f..396561410fcfa72 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkAiToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAiToggle />;
+	return <RtkAiToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAiToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkAiToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
index ef4f69f64146916..676a14f2675ae81 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
@@ -5,38 +5,33 @@ description: API reference for RtkAiTranscriptions component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAiTranscriptions />;
+	return <RtkAiTranscriptions />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAiTranscriptions
-      initialTranscriptions={[]}
-      meeting={meeting}
-    />
-  );
+	return <RtkAiTranscriptions initialTranscriptions={[]} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
index 5a8f8fedf34406a..75ece5db8d70097 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
@@ -5,43 +5,39 @@ description: API reference for RtkAudioGrid component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioGrid />;
+	return <RtkAudioGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioGrid
-      config={defaultUiConfig}
-      hideSelf={true}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkAudioGrid config={defaultUiConfig} hideSelf={true} meeting={meeting} />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
index 71a65e966b788a4..5c8a03c08f715b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkAudioTile component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioTile />;
+	return <RtkAudioTile />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioTile
-      config={defaultUiConfig}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkAudioTile
+			config={defaultUiConfig}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
index 9f5b3941640b98a..33a40cf994b8247 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkAudioVisualizer component (React Library)
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioVisualizer />;
+	return <RtkAudioVisualizer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioVisualizer
-      hideMuted={true}
-      isScreenShare={true}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkAudioVisualizer
+			hideMuted={true}
+			isScreenShare={true}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
index 0e6ffdb430de443..b48ab891f56912c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkAvatar component (React Library)
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
+import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAvatar />;
+	return <RtkAvatar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
+import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAvatar
-      participant="example"
-      size="md"
-      variant="circular"
-    />
-  );
+	return <RtkAvatar participant="example" size="md" variant="circular" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
index 487dc6287788cc7..a8884efc78197e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkBreakoutRoomManager component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomManager />;
+	return <RtkBreakoutRoomManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomManager
-      allowDelete={true}
-      assigningParticipants={true}
-      defaultExpanded={true}
-    />
-  );
+	return (
+		<RtkBreakoutRoomManager
+			allowDelete={true}
+			assigningParticipants={true}
+			defaultExpanded={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
index fb2341581602302..2004a147afe14a6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkBreakoutRoomParticipants component (React Libr
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomParticipants />;
+	return <RtkBreakoutRoomParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomParticipants
-      meeting={meeting}
-      participantIds="example"
-      selectedParticipantIds="example"
-    />
-  );
+	return (
+		<RtkBreakoutRoomParticipants
+			meeting={meeting}
+			participantIds="example"
+			selectedParticipantIds="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
index 50f3260dcf7a651..dcbcea2d4770056 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkBreakoutRoomsManager component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomsManager />;
+	return <RtkBreakoutRoomsManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomsManager
-      meeting={meeting}
-    />
-  );
+	return <RtkBreakoutRoomsManager meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
index 380c96f9f1541ef..437ddd1710ebf57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkBreakoutRoomsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomsToggle />;
+	return <RtkBreakoutRoomsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomsToggle
-      iconPack={defaultIconPack}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkBreakoutRoomsToggle
+			iconPack={defaultIconPack}
+			meeting={meeting}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
index 856b11cff1b3d13..2117f12536528dd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkBroadcastMessageModal component (React Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBroadcastMessageModal />;
+	return <RtkBroadcastMessageModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBroadcastMessageModal
-      meeting={meeting}
-    />
-  );
+	return <RtkBroadcastMessageModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
index 5be7a8515fbc268..4662a4cb4703613 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
@@ -5,44 +5,38 @@ description: API reference for RtkButton component (React Library)
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkButton />;
+	return <RtkButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkButton
-      disabled={true}
-      kind={buttonkind}
-      reverse={true}
-    />
-  );
+	return <RtkButton disabled={true} kind={buttonkind} reverse={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
index 5964ca5795dff5d..5bd7f5725ed45f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
@@ -5,51 +5,52 @@ description: API reference for RtkCameraSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCameraSelector />;
+	return <RtkCameraSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCameraSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkCameraSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
index f32d538b0d242cb..ef0f7be9cbd784b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCameraToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your camera.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCameraToggle />;
+	return <RtkCameraToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCameraToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkCameraToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
index 4e5a7b0e9ae81e2..ccb44bea4849232 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCaptionToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCaptionToggle />;
+	return <RtkCaptionToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCaptionToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkCaptionToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
index 08109cd1a6900d2..88044716a737a05 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkChat component (React Library)
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChat } from '@cloudflare/realtimekit-react-ui';
+import { RtkChat } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChat />;
+	return <RtkChat />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChat } from '@cloudflare/realtimekit-react-ui';
+import { RtkChat } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChat
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkChat meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
index 3c8a6961bebc260..f71eb84400228a3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkChatComposerUi component (React Library)
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatComposerUi />;
+	return <RtkChatComposerUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatComposerUi
-      canSendFiles={true}
-      canSendTextMessage={true}
-      size="md"
-    />
-  );
+	return (
+		<RtkChatComposerUi
+			canSendFiles={true}
+			canSendTextMessage={true}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
index 2ebfa2b0d2a24e3..3f5eabaf3bbce7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
@@ -5,49 +5,49 @@ description: API reference for RtkChatComposerView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatComposerView />;
+	return <RtkChatComposerView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatComposerView
-      canSendFiles={true}
-      canSendTextMessage={true}
-      inputTextPlaceholder="example"
-    />
-  );
+	return (
+		<RtkChatComposerView
+			canSendFiles={true}
+			canSendTextMessage={true}
+			inputTextPlaceholder="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
index b8d221aa00d5d75..172ac6463eae729 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
@@ -5,19 +5,19 @@ description: API reference for RtkChatHeader component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatHeader />;
+	return <RtkChatHeader />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
index 62095db66fa56ee..06b7622778baee0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
@@ -5,55 +5,49 @@ description: API reference for RtkChatMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessage />;
+	return <RtkChatMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessage
-      alignRight={true}
-      canDelete={true}
-      canEdit={true}
-    />
-  );
+	return <RtkChatMessage alignRight={true} canDelete={true} canEdit={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
index 39be829497f47dc..24dfa75d1e264c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkChatMessagesUi component (React Library)
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessagesUi />;
+	return <RtkChatMessagesUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessagesUi
-      canPinMessages={true}
-      messages={[]}
-      selectedGroup="example"
-    />
-  );
+	return (
+		<RtkChatMessagesUi
+			canPinMessages={true}
+			messages={[]}
+			selectedGroup="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
index 2050ab5a26bc247..5891af64b276945 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkChatMessagesUiPaginated component (React Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessagesUiPaginated />;
+	return <RtkChatMessagesUiPaginated />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessagesUiPaginated
-      meeting={meeting}
-      privateChatRecipient={participant | null}
-      size="md"
-    />
-  );
+	return (
+		<RtkChatMessagesUiPaginated
+			meeting={meeting}
+			privateChatRecipient={participant | null}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
index 8218e3a1de98dcc..7b498cd1db28fe1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkChatSearchResults component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSearchResults />;
+	return <RtkChatSearchResults />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSearchResults
-      channelId="example"
-      meeting={meeting}
-      query="example"
-    />
-  );
+	return (
+		<RtkChatSearchResults
+			channelId="example"
+			meeting={meeting}
+			query="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
index d57247e25b7d5f0..377f279bef2cd5e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkChatSelector component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSelector />;
+	return <RtkChatSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSelector
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkChatSelector meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
index 780c0f8d5ddc863..883fee41a51d0de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkChatSelectorUi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSelectorUi />;
+	return <RtkChatSelectorUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSelectorUi
-      groups={[]}
-      selectedGroupId="example"
-      selfUserId="example"
-    />
-  );
+	return (
+		<RtkChatSelectorUi
+			groups={[]}
+			selectedGroupId="example"
+			selfUserId="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
index 93bb6e482beaa63..23fa8dea93d070a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
@@ -5,49 +5,47 @@ description: API reference for RtkChatToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of chat.
- You need to pass the `meeting` object to it to see the unread messages count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'chat' }
- ```
+You need to pass the `meeting` object to it to see the unread messages count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "chat";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatToggle />;
+	return <RtkChatToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkChatToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
index 5b51f5833c33a3f..6671c8edffa9090 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkClock component (React Library)
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkClock } from '@cloudflare/realtimekit-react-ui';
+import { RtkClock } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkClock />;
+	return <RtkClock />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkClock } from '@cloudflare/realtimekit-react-ui';
+import { RtkClock } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkClock
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkClock meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
index 03354726cb31f89..31eb8135db4c518 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
@@ -5,40 +5,36 @@ description: API reference for RtkConfirmationModal component (React Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkConfirmationModal />;
+	return <RtkConfirmationModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkConfirmationModal
-      meeting={meeting}
-    />
-  );
+	return <RtkConfirmationModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
index 23812e3db206ab2..70878abe0db3e5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkControlbar component (React Library)
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkControlbar />;
+	return <RtkControlbar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkControlbar
-      disableRender={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkControlbar disableRender={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
index d0e6e508caf9480..d9027e6aa0875b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
@@ -5,47 +5,43 @@ description: API reference for RtkControlbarButton component (React Library)
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkControlbarButton />;
+	return <RtkControlbarButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkControlbarButton
-      brandIcon={true}
-      disabled={true}
-      icon="example"
-    />
-  );
+	return (
+		<RtkControlbarButton brandIcon={true} disabled={true} icon="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
index 7b619a1539d261f..2f691f8771858ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCounter component (React Library)
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
+import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCounter />;
+	return <RtkCounter />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
+import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCounter
-      minValue={42}
-      size="md"
-      value={42}
-    />
-  );
+	return <RtkCounter minValue={42} size="md" value={42} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
index f053eb720bed15d..e50a8ecb11348d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkDebugger component (React Library)
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebugger />;
+	return <RtkDebugger />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebugger
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebugger meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
index 7dc5d08497e8bd7..e3b258be377ed38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerAudio component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerAudio />;
+	return <RtkDebuggerAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerAudio
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerAudio meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
index 84e96a1f71fb63a..62053832f219996 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerScreenshare component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerScreenshare />;
+	return <RtkDebuggerScreenshare />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerScreenshare
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerScreenshare meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
index 351882399cc12df..fa2fc78d58a6309 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerSystem component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerSystem />;
+	return <RtkDebuggerSystem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerSystem
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerSystem meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
index a31dd78c42d4145..5e693f7e36fb65e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkDebuggerToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerToggle />;
+	return <RtkDebuggerToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkDebuggerToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
index c74f2cb9062572f..f5819d9caac23ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerVideo component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerVideo />;
+	return <RtkDebuggerVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerVideo
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerVideo meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
index fe104ba37211c2a..46fbf93818f24f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkDialog component (React Library)
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDialog />;
+	return <RtkDialog />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDialog
-      disableEscapeKey={true}
-      hideCloseButton={true}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkDialog
+			disableEscapeKey={true}
+			hideCloseButton={true}
+			meeting={meeting}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
index 61ee80cd7643468..736b239555dd6c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
@@ -5,49 +5,45 @@ description: API reference for RtkDialogManager component (React Library)
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDialogManager />;
+	return <RtkDialogManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDialogManager
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDialogManager meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
index a5285022bbe30c4..90c0d95b4208a0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkDraftAttachmentView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property     | Type                                                 | Required | Default           | Description           |
+| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
+| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
+| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
+import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDraftAttachmentView />;
+	return <RtkDraftAttachmentView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
+import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDraftAttachmentView
-      attachment={{}}
-    />
-  );
+	return <RtkDraftAttachmentView attachment={{}} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
index c43046ea84826be..8a0e1b654ee40a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkEmojiPicker component (React Library)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEmojiPicker />;
+	return <RtkEmojiPicker />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEmojiPicker
-      focusWhenOpened={true}
-    />
-  );
+	return <RtkEmojiPicker focusWhenOpened={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
index fb41c2305bae5b8..dd15556f86ad2a2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkEmojiPickerButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEmojiPickerButton />;
+	return <RtkEmojiPickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEmojiPickerButton
-      isActive={true}
-    />
-  );
+	return <RtkEmojiPickerButton isActive={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
index f5d34bcb49b8d47..9e06d6de13b10ac 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkEndedScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEndedScreen />;
+	return <RtkEndedScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEndedScreen
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkEndedScreen meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
index 249558fdf892cff..d000f71a09a18c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkFileDropzone component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileDropzone />;
+	return <RtkFileDropzone />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileDropzone
-      hostEl={htmlelement}
-    />
-  );
+	return <RtkFileDropzone hostEl={htmlelement} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
index 160e6d45a1c3e0d..0d763747bc4f21b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkFileMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileMessage />;
+	return <RtkFileMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileMessage
-      isContinued={true}
-      message={filemessage}
-      now={date}
-    />
-  );
+	return <RtkFileMessage isContinued={true} message={filemessage} now={date} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
index baf330586b09a46..64098e714003e5e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkFileMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileMessageView />;
+	return <RtkFileMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileMessageView
-      name="example"
-      size={42}
-      url="example"
-    />
-  );
+	return <RtkFileMessageView name="example" size={42} url="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
index 7695557d4ce9b2e..f495c13464a820e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkFilePickerButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFilePickerButton />;
+	return <RtkFilePickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFilePickerButton
-      filter="example"
-      icon={defaultIconPack}
-      label="example"
-    />
-  );
+	return (
+		<RtkFilePickerButton
+			filter="example"
+			icon={defaultIconPack}
+			label="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
index 4dfd50432f2e792..0abc92d640e427b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkFullscreenToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles full screen mode for any
- existing `rtk-meeting` component in the DOM.
+existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property        | Type                | Required | Default           | Description                  |
+| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
+| `size`          | `Size`              | ✅       | -                 | Size                         |
+| `states`        | `States`            | ✅       | -                 | States object                |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
+| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
+| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFullscreenToggle />;
+	return <RtkFullscreenToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFullscreenToggle
-      size="md"
-      targetElement={htmlelement}
-      variant="button"
-    />
-  );
+	return (
+		<RtkFullscreenToggle
+			size="md"
+			targetElement={htmlelement}
+			variant="button"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
index ba09d23bb59421f..f927f0f83579df1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
@@ -5,49 +5,43 @@ description: API reference for RtkGrid component (React Library)
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkGrid />;
+	return <RtkGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
index 5f237bf642f2544..2ec869ec68a635d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkGridPagination component (React Library)
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
+import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkGridPagination />;
+	return <RtkGridPagination />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
+import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkGridPagination
-      meeting={meeting}
-      size="md"
-      variant={gridpaginationvariants}
-    />
-  );
+	return (
+		<RtkGridPagination
+			meeting={meeting}
+			size="md"
+			variant={gridpaginationvariants}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
index 10ccda38fa97f7e..ae22b18378bd4c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkHeader component (React Library)
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkHeader />;
+	return <RtkHeader />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkHeader
-      disableRender={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkHeader disableRender={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
index f7283d6288d99a4..16a092f54b2dbce 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkIcon component (React Library)
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
+import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkIcon />;
+	return <RtkIcon />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
+import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkIcon
-      icon="example"
-      size="md"
-      variant="primary"
-    />
-  );
+	return <RtkIcon icon="example" size="md" variant="primary" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
index 673fc18b193b110..c1bb80f2c5f6df1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkIdleScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkIdleScreen />;
+	return <RtkIdleScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkIdleScreen
-      meeting={meeting}
-    />
-  );
+	return <RtkIdleScreen meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
index 8c0288f2c73bdea..55513c0267caef0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
@@ -5,45 +5,41 @@ description: API reference for RtkImageMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageMessage />;
+	return <RtkImageMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageMessage
-      isContinued={true}
-      message={imagemessage}
-      now={date}
-    />
-  );
+	return (
+		<RtkImageMessage isContinued={true} message={imagemessage} now={date} />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
index c780f5404911db6..7bbc3cd4d39a23a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkImageMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageMessageView />;
+	return <RtkImageMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageMessageView
-      url="example"
-    />
-  );
+	return <RtkImageMessageView url="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
index 91083a36a5cc7cd..9df4c2bb772122b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkImageViewer component (React Library)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageViewer />;
+	return <RtkImageViewer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageViewer
-      image={imagemessage}
-      size="md"
-    />
-  );
+	return <RtkImageViewer image={imagemessage} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
index 0fbe8b295b4e90a..59bb5a4a42279d0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
@@ -5,35 +5,31 @@ description: API reference for RtkInformationTooltip component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkInformationTooltip />;
+	return <RtkInformationTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkInformationTooltip
-      iconPack={defaultIconPack}
-    />
-  );
+	return <RtkInformationTooltip iconPack={defaultIconPack} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
index 980d877c6c2be1c..cb2514eb8f698d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
@@ -5,43 +5,39 @@ description: API reference for RtkJoinStage component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkJoinStage />;
+	return <RtkJoinStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkJoinStage
-      dataConfig={modaldataconfig}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkJoinStage dataConfig={modaldataconfig} meeting={meeting} size="md" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
index cbadd40c668ffb5..bd0118ecce5e460 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkLeaveButton component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description |
+| ---------- | ------------------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size`              | ✅       | -                 | Size        |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLeaveButton />;
+	return <RtkLeaveButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLeaveButton
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkLeaveButton size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
index 381df4d5a32d9a8..caaa57aa9b7489a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkLeaveMeeting component (React Library)
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLeaveMeeting />;
+	return <RtkLeaveMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLeaveMeeting
-      meeting={meeting}
-    />
-  );
+	return <RtkLeaveMeeting meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
index c460afe367c3aba..f32e008ce30ba45 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkLivestreamIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamIndicator />;
+	return <RtkLivestreamIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkLivestreamIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
index f2825122178db2e..76bcbcc4f131e9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkLivestreamPlayer component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamPlayer />;
+	return <RtkLivestreamPlayer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamPlayer
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkLivestreamPlayer meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
index 5a02a6110c65ab6..bbc41afc7185d64 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkLivestreamToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamToggle />;
+	return <RtkLivestreamToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkLivestreamToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
index eb4e53ce7220d26..9477a16d30710b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkLogo component (React Library)
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
+import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLogo />;
+	return <RtkLogo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
+import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLogo
-      logoUrl="example"
-      meeting={meeting}
-    />
-  );
+	return <RtkLogo logoUrl="example" meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
index b4a60b36bb5affb..55fbf4dd7de4c88 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
@@ -5,37 +5,32 @@ description: API reference for RtkMarkdownView component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMarkdownView />;
+	return <RtkMarkdownView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMarkdownView
-      maxLength={42}
-      text="example"
-    />
-  );
+	return <RtkMarkdownView maxLength={42} text="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
index 46f187b5651c348..fc2ab8e84fcd5de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
@@ -5,53 +5,53 @@ description: API reference for RtkMeeting component (React Library)
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMeeting />;
+	return <RtkMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMeeting
-      applyDesignSystem={true}
-      config={defaultUiConfig}
-      gridLayout={gridlayout1}
-    />
-  );
+	return (
+		<RtkMeeting
+			applyDesignSystem={true}
+			config={defaultUiConfig}
+			gridLayout={gridlayout1}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
index 390e091d34851d8..8e26823a9775b15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkMeetingTitle component (React Library)
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMeetingTitle />;
+	return <RtkMeetingTitle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMeetingTitle
-      meeting={meeting}
-    />
-  );
+	return <RtkMeetingTitle meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
index 5f5db9ac9f51c5d..9ee83f7cee4ea0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkMenu component (React Library)
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenu />;
+	return <RtkMenu />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenu
-      offset={42}
-      placement={placement}
-      size="md"
-    />
-  );
+	return <RtkMenu offset={42} placement={placement} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
index 07d2090f6869fa5..e3ed88af47b32ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkMenuItem component (React Library)
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenuItem />;
+	return <RtkMenuItem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenuItem
-      menuVariant={'primary' | 'secondary'}
-      size="md"
-    />
-  );
+	return <RtkMenuItem menuVariant={"primary" | "secondary"} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
index 3abcdf3681cf82c..c8535a1fd33ef85 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkMenuList component (React Library)
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenuList />;
+	return <RtkMenuList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenuList
-      menuVariant={'primary' | 'secondary'}
-    />
-  );
+	return <RtkMenuList menuVariant={"primary" | "secondary"} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
index a821d60dd934f37..80a9a91264a8c83 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkMessageView component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMessageView />;
+	return <RtkMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMessageView
-      actions={[]}
-      authorName="example"
-      avatarUrl="example"
-    />
-  );
+	return (
+		<RtkMessageView actions={[]} authorName="example" avatarUrl="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
index 8a828fa1df70a57..cc03a1979681184 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkMicToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your microphone.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMicToggle />;
+	return <RtkMicToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMicToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkMicToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
index 7635bf3bc850417..bddd6410870b69d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
@@ -5,51 +5,52 @@ description: API reference for RtkMicrophoneSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMicrophoneSelector />;
+	return <RtkMicrophoneSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMicrophoneSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkMicrophoneSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
index 9797cef0997f626..2a84e600445f8a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
@@ -5,52 +5,46 @@ description: API reference for RtkMixedGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMixedGrid />;
+	return <RtkMixedGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMixedGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkMixedGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
index 2c8f9d6008454df..ec75917e7d6794f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
@@ -5,44 +5,43 @@ description: API reference for RtkMoreToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMoreToggle />;
+	return <RtkMoreToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMoreToggle
-      size="md"
-    />
-  );
+	return <RtkMoreToggle size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
index 0a61a27b14d57cb..9ff1d6062e97f3a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkMuteAllButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMuteAllButton />;
+	return <RtkMuteAllButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMuteAllButton
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkMuteAllButton meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
index 6964b04a06fce07..de60763a8da782a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkMuteAllConfirmation component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMuteAllConfirmation />;
+	return <RtkMuteAllConfirmation />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMuteAllConfirmation
-      meeting={meeting}
-    />
-  );
+	return <RtkMuteAllConfirmation meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
index 653d3e71c13c219..b24255b2688e80e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkNameTag component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
+import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNameTag />;
+	return <RtkNameTag />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
+import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNameTag
-      isScreenShare={true}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkNameTag
+			isScreenShare={true}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
index cdc9b9d26f6014c..badca357da7d298 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkNetworkIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNetworkIndicator />;
+	return <RtkNetworkIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNetworkIndicator
-      isScreenShare={true}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkNetworkIndicator
+			isScreenShare={true}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
index 011b505c0f96d15..5aecde35407d99b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
@@ -5,45 +5,41 @@ description: API reference for RtkNotification component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNotification />;
+	return <RtkNotification />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNotification
-      notification={notification}
-      paused={true}
-      size="md"
-    />
-  );
+	return (
+		<RtkNotification notification={notification} paused={true} size="md" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
index a6479a63c2b3dc3..b4cf3563bdaf55e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
@@ -5,45 +5,40 @@ description: API reference for RtkNotifications component (React Library)
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNotifications />;
+	return <RtkNotifications />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNotifications
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkNotifications meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
index 075d2ad41e4e7f1..f4a1c236a9e1ff3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
@@ -5,40 +5,36 @@ description: API reference for RtkOverlayModal component (React Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkOverlayModal />;
+	return <RtkOverlayModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkOverlayModal
-      meeting={meeting}
-    />
-  );
+	return <RtkOverlayModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
index 9c2aa7dd5fa68fa..4efdfe198d33ae2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkPaginatedList component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
+import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPaginatedList />;
+	return <RtkPaginatedList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
+import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPaginatedList
-      autoScroll={true}
-      createNodes={[]}
-      emptyListLabel="example"
-    />
-  );
+	return (
+		<RtkPaginatedList
+			autoScroll={true}
+			createNodes={[]}
+			emptyListLabel="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
index ccc8cb4e191bc51..516579dd9a334b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkParticipant component (React Library)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipant />;
+	return <RtkParticipant />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipant
-      meeting={meeting}
-      participant={participant}
-      view={participantviewmode}
-    />
-  );
+	return (
+		<RtkParticipant
+			meeting={meeting}
+			participant={participant}
+			view={participantviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
index e8cd175555dcd38..328f0c14986aba0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkParticipantCount component (React Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantCount />;
+	return <RtkParticipantCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantCount
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkParticipantCount meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
index 7606fca272f529b..91ef45fb563d602 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkParticipants component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipants />;
+	return <RtkParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipants
-      defaultParticipantsTabId={participantstabid}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkParticipants
+			defaultParticipantsTabId={participantstabid}
+			meeting={meeting}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
index 8ef488005d52a27..b758d16591fc32d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkParticipantsAudio component (React Library)
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsAudio />;
+	return <RtkParticipantsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsAudio
-      meeting={meeting}
-      preloadedAudioElem={htmlaudioelement}
-    />
-  );
+	return (
+		<RtkParticipantsAudio
+			meeting={meeting}
+			preloadedAudioElem={htmlaudioelement}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
index b00d785b2acf701..135d60ff19db841 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkParticipantsStageList component (React Library
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsStageList />;
+	return <RtkParticipantsStageList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsStageList
-      hideHeader={true}
-      meeting={meeting}
-      search="example"
-    />
-  );
+	return (
+		<RtkParticipantsStageList
+			hideHeader={true}
+			meeting={meeting}
+			search="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
index 4e41381ce80f30a..8528f80bb052dd6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsStageQueue component (React Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsStageQueue />;
+	return <RtkParticipantsStageQueue />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsStageQueue
-      meeting={meeting}
-      size="md"
-      view={participantsviewmode}
-    />
-  );
+	return (
+		<RtkParticipantsStageQueue
+			meeting={meeting}
+			size="md"
+			view={participantsviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
index 9c8fdaf5ece9fe4..0301d934942ee7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
@@ -5,48 +5,46 @@ description: API reference for RtkParticipantsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of participants.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'participants' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "participants";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsToggle />;
+	return <RtkParticipantsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkParticipantsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
index 2122d23e95a3666..a8153f7ffc87a99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkParticipantsViewerList component (React Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsViewerList />;
+	return <RtkParticipantsViewerList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsViewerList
-      hideHeader={true}
-      meeting={meeting}
-      search="example"
-    />
-  );
+	return (
+		<RtkParticipantsViewerList
+			hideHeader={true}
+			meeting={meeting}
+			search="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
index 3a889887010026a..4649b0bfc0e82fd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsWaitingList component (React Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsWaitingList />;
+	return <RtkParticipantsWaitingList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsWaitingList
-      meeting={meeting}
-      size="md"
-      view={participantsviewmode}
-    />
-  );
+	return (
+		<RtkParticipantsWaitingList
+			meeting={meeting}
+			size="md"
+			view={participantsviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
index 3772370f932a5c4..d775d0fe83a22f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkPermissionsMessage component (React Library)
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPermissionsMessage />;
+	return <RtkPermissionsMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPermissionsMessage
-      meeting={meeting}
-    />
-  );
+	return <RtkPermissionsMessage meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
index 6ec7ca9cc8718b2..3204dca64827f0c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkPinnedMessageSelector component (React Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPinnedMessageSelector />;
+	return <RtkPinnedMessageSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPinnedMessageSelector
-      meeting={meeting}
-    />
-  );
+	return <RtkPinnedMessageSelector meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
index 2c97be980f7bfe7..7fa13266f256c40 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkPipToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPipToggle />;
+	return <RtkPipToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPipToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPipToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
index 558894132225b7a..c3e69d48c2363ad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkPluginMain component (React Library)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPluginMain />;
+	return <RtkPluginMain />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPluginMain
-      meeting={meeting}
-      plugin={rtkplugin}
-    />
-  );
+	return <RtkPluginMain meeting={meeting} plugin={rtkplugin} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
index 6deb86e4607c003..d965a8cd11d84f3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkPlugins component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
+import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPlugins />;
+	return <RtkPlugins />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
+import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPlugins
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkPlugins meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
index 68b70c406caf1cc..ea36e607b88f055 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
@@ -5,48 +5,46 @@ description: API reference for RtkPluginsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of plugins.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'plugins' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "plugins";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPluginsToggle />;
+	return <RtkPluginsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPluginsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPluginsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
index aa4fe6fd115a016..3005624ec80b0f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
@@ -5,44 +5,40 @@ description: API reference for RtkPoll component (React Library)
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
+import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPoll />;
+	return <RtkPoll />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
+import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPoll
-      permissions={rtkpermissionspreset}
-      poll={poll}
-      self="example"
-    />
-  );
+	return (
+		<RtkPoll permissions={rtkpermissionspreset} poll={poll} self="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
index 83cc1ae5190f3c2..e875461eed40218 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkPollForm component (React Library)
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPollForm />;
+	return <RtkPollForm />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPollForm
-      iconPack={defaultIconPack}
-      t={rtki18n}
-    />
-  );
+	return <RtkPollForm iconPack={defaultIconPack} t={rtki18n} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
index 4277a2b47bfdace..d6c56afb6b26cca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkPolls component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
+import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPolls />;
+	return <RtkPolls />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
+import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPolls
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkPolls meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
index f50a1cdaceb586b..ce797b91301661d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
@@ -5,49 +5,47 @@ description: API reference for RtkPollsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of polls.
- You need to pass the `meeting` object to it to see the unread polls count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'polls' }
- ```
+You need to pass the `meeting` object to it to see the unread polls count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "polls";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPollsToggle />;
+	return <RtkPollsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPollsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPollsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
index 5c2762db23494d2..80fd74b508c85d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkRecordingIndicator component (React Library)
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkRecordingIndicator />;
+	return <RtkRecordingIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkRecordingIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkRecordingIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
index 0f80e38da1040bc..37ff40da4c4e3e2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
@@ -5,47 +5,41 @@ description: API reference for RtkRecordingToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkRecordingToggle />;
+	return <RtkRecordingToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkRecordingToggle
-      disabled={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkRecordingToggle disabled={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
index 52908befd7de5b5..f2af8f3196dc19e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
@@ -5,44 +5,38 @@ description: API reference for RtkScreenShareToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkScreenShareToggle />;
+	return <RtkScreenShareToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkScreenShareToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkScreenShareToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
index 2b52d0ae178ce6d..71105173b22229f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkSettings component (React Library)
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettings />;
+	return <RtkSettings />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettings
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettings meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
index 81dfd8b2b09dd43..3519e84e54fc498 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkSettingsAudio component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsAudio />;
+	return <RtkSettingsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsAudio
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettingsAudio meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
index be09e3aaa6d7c96..d3a027941137787 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
@@ -5,46 +5,44 @@ description: API reference for RtkSettingsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of settings module.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSettings: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSettings: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description   |
+| ---------- | ------------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`              | ✅       | -                 | Size          |
+| `states`   | `States`            | ✅       | -                 | States object |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsToggle />;
+	return <RtkSettingsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsToggle
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkSettingsToggle size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
index e8ecedcb858f5f0..004752677fc71bb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkSettingsVideo component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsVideo />;
+	return <RtkSettingsVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsVideo
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettingsVideo meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
index b7d2b949edf7209..9425271184560e0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
@@ -5,44 +5,39 @@ description: API reference for RtkSetupScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSetupScreen />;
+	return <RtkSetupScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSetupScreen
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSetupScreen meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
index 1304726dd69f9a7..a911ce5c3815222 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkSidebar component (React Library)
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSidebar />;
+	return <RtkSidebar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSidebar
-      defaultSection={rtksidebarsection}
-      enabledSections={[]}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkSidebar
+			defaultSection={rtksidebarsection}
+			enabledSections={[]}
+			meeting={meeting}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
index 01b17c6dd9ffc5a..476c5b291b984ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkSidebarUi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSidebarUi />;
+	return <RtkSidebarUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSidebarUi
-      currentTab="example"
-      focusCloseButton={true}
-      hideCloseAction={true}
-    />
-  );
+	return (
+		<RtkSidebarUi
+			currentTab="example"
+			focusCloseButton={true}
+			hideCloseAction={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
index 1a39406c2ae6fc3..000057d63bf902c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
@@ -5,47 +5,41 @@ description: API reference for RtkSimpleGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSimpleGrid />;
+	return <RtkSimpleGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSimpleGrid
-      aspectRatio="example"
-      gap={42}
-      meeting={meeting}
-    />
-  );
+	return <RtkSimpleGrid aspectRatio="example" gap={42} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
index ef6967aefdd7575..04e2e6cc9985238 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
@@ -5,52 +5,53 @@ description: API reference for RtkSpeakerSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpeakerSelector />;
+	return <RtkSpeakerSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpeakerSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkSpeakerSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
index f465d60658ede2a..28454314a99f114 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkSpinner component (React Library)
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpinner />;
+	return <RtkSpinner />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpinner
-      size="md"
-    />
-  );
+	return <RtkSpinner size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
index 0bf9ca54bc892c6..78418e203326306 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
@@ -5,53 +5,48 @@ description: API reference for RtkSpotlightGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpotlightGrid />;
+	return <RtkSpotlightGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpotlightGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkSpotlightGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
index 6b3cf9e708c5b27..4777d387761bd9c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkSpotlightIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpotlightIndicator />;
+	return <RtkSpotlightIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpotlightIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSpotlightIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
index 2d45d987a733a92..317f51dde0bca13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkStage component (React Library)
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkStage />;
+	return <RtkStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkStage
-      iconPack={defaultIconPack}
-      t={rtki18n}
-    />
-  );
+	return <RtkStage iconPack={defaultIconPack} t={rtki18n} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
index cb4ca66a237f1fe..348c55faae4ad7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkStageToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `states`   | `States1`           | ✅       | -                 | States         |
+| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkStageToggle />;
+	return <RtkStageToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkStageToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkStageToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
index 45b7bebc4f42df5..d70d8ba438e9132 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkSwitch component (React Library)
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
+import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSwitch />;
+	return <RtkSwitch />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
+import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSwitch
-      checked={true}
-      disabled={true}
-      readonly={true}
-    />
-  );
+	return <RtkSwitch checked={true} disabled={true} readonly={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
index 4b92e54781696ee..d425e9836824989 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkTabBar component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
+import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTabBar />;
+	return <RtkTabBar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
+import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTabBar
-      activeTab={tab}
-      layout={gridlayout1}
-      meeting={meeting}
-    />
-  );
+	return <RtkTabBar activeTab={tab} layout={gridlayout1} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
index b13d5561c20349b..275064c3a0e30cf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkTextMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTextMessage />;
+	return <RtkTextMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTextMessage
-      isContinued={true}
-      message={textmessage}
-      now={date}
-    />
-  );
+	return <RtkTextMessage isContinued={true} message={textmessage} now={date} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
index 181ebc339cd53d8..05911d805ffcb0f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkTextMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTextMessageView />;
+	return <RtkTextMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTextMessageView
-      isMarkdown={true}
-      text="example"
-    />
-  );
+	return <RtkTextMessageView isMarkdown={true} text="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
index d2bfb5b64eb3958..c1621ec9cec5946 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkTooltip component (React Library)
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTooltip />;
+	return <RtkTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTooltip
-      delay={42}
-      disabled={true}
-      kind={tooltipkind}
-    />
-  );
+	return <RtkTooltip delay={42} disabled={true} kind={tooltipkind} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
index de37a7083168217..bbcf034ad560898 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkTranscript component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTranscript />;
+	return <RtkTranscript />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTranscript
-      t={rtki18n}
-      transcript="example"
-    />
-  );
+	return <RtkTranscript t={rtki18n} transcript="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
index f0c0d8559cc445a..42bf35aa1892a1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
@@ -5,42 +5,38 @@ description: API reference for RtkTranscripts component (React Library)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTranscripts />;
+	return <RtkTranscripts />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTranscripts
-      meeting={meeting}
-    />
-  );
+	return <RtkTranscripts meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
index ae022070d0bc868..539123ffabfd8ae 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkUiProvider component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
+import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkUiProvider />;
+	return <RtkUiProvider />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
+import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkUiProvider
-      config={defaultUiConfig}
-      mode={meeting}
-      showSetupScreen={true}
-    />
-  );
+	return (
+		<RtkUiProvider
+			config={defaultUiConfig}
+			mode={meeting}
+			showSetupScreen={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
index 6cd926ddcacf256..1ba972a480e5bf9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkViewerCount component (React Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkViewerCount />;
+	return <RtkViewerCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkViewerCount
-      meeting={meeting}
-      variant="primary"
-    />
-  );
+	return <RtkViewerCount meeting={meeting} variant="primary" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
index 5357ad00b4bb2f2..a0e877a59bc623a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkVirtualizedParticipantList component (React Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
+import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkVirtualizedParticipantList />;
+	return <RtkVirtualizedParticipantList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
+import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkVirtualizedParticipantList
-      bufferedItemsCount={42}
-      emptyListElement={htmlelement}
-      itemHeight={42}
-    />
-  );
+	return (
+		<RtkVirtualizedParticipantList
+			bufferedItemsCount={42}
+			emptyListElement={htmlelement}
+			itemHeight={42}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
index 7a88d11a1ddcc8e..80ab41447906b03 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkWaitingScreen component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkWaitingScreen />;
+	return <RtkWaitingScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkWaitingScreen
-      meeting={meeting}
-    />
-  );
+	return <RtkWaitingScreen meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
index e278b3204222b09..484d77e089e0389 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
index 167875d1b34c213..97583e8bcbbb2dc 100644
--- a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
+++ b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-import { Aside } from "~/components"
+import { Aside } from "~/components";
 
 ## Cloudflare Realtime vs. Traditional SFUs
 
@@ -31,7 +31,10 @@ Cloudflare Realtime addresses these limitations by leveraging Cloudflare's globa
 - **Decentralized Architecture:** There are no dedicated servers for Realtime. Every server within Cloudflare's network contributes to handling Realtime, ensuring scalability and reliability. This approach mirrors the distributed nature of Cloudflare's products such as 1.1.1.1 DNS or Cloudflare's CDN.
 
 <Aside type="tip">
-**See it in action:** Explore our [interactive Global SFU visualization](https://realtime-sfu.dev-demos.workers.dev) to see how participants connect to their nearest Cloudflare datacenter and how media flows across the global backbone.
+	**See it in action:** Explore our [interactive Global SFU
+	visualization](https://realtime-sfu.dev-demos.workers.dev) to see how
+	participants connect to their nearest Cloudflare datacenter and how media
+	flows across the global backbone.
 </Aside>
 
 ## How Cloudflare Realtime Works
diff --git a/src/content/docs/realtime/sfu/changelog.mdx b/src/content/docs/realtime/sfu/changelog.mdx
index e41f539ea385e1c..1c9d09e442ea9d3 100644
--- a/src/content/docs/realtime/sfu/changelog.mdx
+++ b/src/content/docs/realtime/sfu/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/realtime.yaml. --> */}
 
-<ProductReleaseNotes />
\ No newline at end of file
+<ProductReleaseNotes />
diff --git a/src/content/docs/realtime/sfu/datachannels.mdx b/src/content/docs/realtime/sfu/datachannels.mdx
index fb486465f76084c..f60c593ca262bb6 100644
--- a/src/content/docs/realtime/sfu/datachannels.mdx
+++ b/src/content/docs/realtime/sfu/datachannels.mdx
@@ -22,7 +22,7 @@ DataChannels on Cloudflare Realtime can scale up to many subscribers per publish
 
 ### How to use DataChannels
 
-1. Create  two Realtime sessions, one for the publisher and one for the subscribers.
+1. Create two Realtime sessions, one for the publisher and one for the subscribers.
 2. Create a DataChannel by calling /datachannels/new with the location set to "local" and the dataChannelName set to the name of the DataChannel.
 3. Create a DataChannel by calling /datachannels/new with the location set to "remote" and the sessionId set to the sessionId of the publisher.
 4. Use the DataChannel to send data from the publisher to the subscribers.
diff --git a/src/content/docs/realtime/sfu/get-started.mdx b/src/content/docs/realtime/sfu/get-started.mdx
index c629ade1a9f321c..43ee74f34fe8975 100644
--- a/src/content/docs/realtime/sfu/get-started.mdx
+++ b/src/content/docs/realtime/sfu/get-started.mdx
@@ -10,10 +10,8 @@ products:
 
 :::note[Before you get started:]
 
-
 You must first [create a Cloudflare account](/fundamentals/account/create-account/).
 
-
 :::
 
 ## Create your first app
@@ -21,7 +19,7 @@ You must first [create a Cloudflare account](/fundamentals/account/create-accoun
 Every Realtime App is a separate environment, so you can make one for development, staging and production versions for your product.
 Either using [Dashboard](https://dash.cloudflare.com/?to=/:account/realtime/sfu), or the [API](/api/resources/calls/subresources/sfu/methods/create/) create a Realtime App. When you create a Realtime App, you will get:
 
-* App ID
-* App Secret
+- App ID
+- App Secret
 
 These two combined will allow you to make API Realtime from your backend server to Realtime.
diff --git a/src/content/docs/realtime/sfu/limits.mdx b/src/content/docs/realtime/sfu/limits.mdx
index b68859142236802..df32c721be0f051 100644
--- a/src/content/docs/realtime/sfu/limits.mdx
+++ b/src/content/docs/realtime/sfu/limits.mdx
@@ -12,28 +12,28 @@ Understanding the limits and timeouts of Cloudflare Realtime is crucial for opti
 
 ## Free
 
-* Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
-* Data transfer from your client to Cloudflare is always free of charge.
+- Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
+- Data transfer from your client to Cloudflare is always free of charge.
 
 ## Limits
 
-* **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
+- **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
 
-* **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
+- **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
 
-* **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
+- **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
 
 ## Inactivity Timeout
 
-* **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
+- **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
 
 ## PeerConnection Requirements
 
-* **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
+- **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
 
 ## Handling Connectivity Issues
 
-* **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
+- **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
 
 Adhering to these limits and understanding the timeout behaviors will help ensure that your applications remain responsive and stable while providing a seamless user experience.
 
@@ -43,19 +43,18 @@ Cloudflare Realtime supports the following codecs:
 
 ### Supported video codecs
 
-* **H264**
-* **H265**
-* **VP8**
-* **VP9**
-* **AV1**
+- **H264**
+- **H265**
+- **VP8**
+- **VP9**
+- **AV1**
 
 ### Supported audio codecs
 
-* **Opus**
-* **G.711 PCM (A-law)**
-* **G.711 PCM (µ-law)**
+- **Opus**
+- **G.711 PCM (A-law)**
+- **G.711 PCM (µ-law)**
 
 :::note
 For external 48kHz PCM support refer to the [WebSocket adapter](/realtime/sfu/media-transport-adapters/websocket-adapter/)
 :::
-
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
index a9a0f3df0ddbf5b..2edd1740c70cb39 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
@@ -47,6 +47,7 @@ graph LR
 **Adapter instance**: Each connection creates a unique instance with an `adapterId` to manage its lifecycle.
 
 **Location types**:
+
 - `local` (Ingest): Receives media from external endpoints to create new WebRTC tracks
 - `remote` (Stream): Sends media from existing WebRTC tracks to external endpoints
 
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
index ea922e873043cc4..818a1d69f4a3779 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
@@ -206,11 +206,11 @@ POST /v1/apps/{appId}/adapters/websocket/close
 
 ```json
 {
-  "tracks": [
-    {
-      "adapterId": "string"
-    }
-  ]
+	"tracks": [
+		{
+			"adapterId": "string"
+		}
+	]
 }
 ```
 
@@ -242,6 +242,7 @@ message Packet {
 **Ingest mode (buffer)**: Only the `payload` field is used, containing chunks of audio data.
 
 **Stream mode (egress)**:
+
 - For audio frames:
   - `sequenceNumber`: Incremental packet counter
   - `timestamp`: Timestamp for synchronization
@@ -267,12 +268,14 @@ Connects to your WebSocket endpoint:
 ### Message format
 
 #### Buffer mode (ingest)
+
 - **Binary messages**: PCM audio data in chunks
 - **Maximum message size**: 32 KB per WebSocket message
 - **Important**: Account for serialization overhead when chunking audio buffers
 - Send audio in small, frequent chunks rather than large batches
 
-#### Stream mode (egress)  
+#### Stream mode (egress)
+
 - **Binary messages**: Individual frames with metadata (audio or video)
 - Audio frames include:
   - Timestamp information
@@ -330,11 +333,11 @@ Usage counts towards your Cloudflare Realtime free tier of 1,000 GB.
 
 ## Error handling
 
-| Error Code | Description |
-|------------|-------------|
-| `400` | Invalid request parameters |
-| `404` | Session or track not found |
-| `503` | Adapter not found (for close operations) |
+| Error Code | Description                              |
+| ---------- | ---------------------------------------- |
+| `400`      | Invalid request parameters               |
+| `404`      | Session or track not found               |
+| `503`      | Adapter not found (for close operations) |
 
 ## Reference implementations
 
diff --git a/src/content/docs/realtime/sfu/sessions-tracks.mdx b/src/content/docs/realtime/sfu/sessions-tracks.mdx
index 0acfcba0d460671..8f88a1a807fd435 100644
--- a/src/content/docs/realtime/sfu/sessions-tracks.mdx
+++ b/src/content/docs/realtime/sfu/sessions-tracks.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**,  **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
+Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**, **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
 
 ## Application
 
@@ -18,17 +18,17 @@ A Realtime Application is an environment within different Sessions and Tracks ca
 
 A **Session** in Cloudflare Realtime correlates directly to a WebRTC PeerConnection. It represents the establishment of a communication channel between a client and the nearest Cloudflare data center, as determined by Cloudflare's anycast routing. Typically, a client will maintain a single Session, encompassing all communications between the client and Cloudflare.
 
-* **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
-* **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
-* **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
+- **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
+- **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
+- **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
 
 ## Tracks
 
 Within a Session, there can be one or more **Tracks**.
 
-* **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
-* **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
-* **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
+- **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
+- **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
+- **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
 
 ## Realtime as a Programmable "Switchboard"
 
@@ -38,9 +38,9 @@ The analogy of a switchboard is apt for understanding Realtime. Historically, sw
 
 While many SFUs utilize concepts like "rooms" to manage media streams among users, this approach has scalability and flexibility limitations. Cloudflare Realtime opts for a more granular and flexible model with Sessions and Tracks, enabling a wide range of use cases:
 
-* Large-scale remote events, like 'fireside chats' with thousands of participants.
-* Interactive conversations with the ability to bring audience members "on stage."
-* Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
+- Large-scale remote events, like 'fireside chats' with thousands of participants.
+- Interactive conversations with the ability to bring audience members "on stage."
+- Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
 
 ### Presence Protocol vs. Media Flow
 
diff --git a/src/content/docs/realtime/turn/custom-domains.mdx b/src/content/docs/realtime/turn/custom-domains.mdx
index 9103a2e08eaf8a9..16baeeb56029ffa 100644
--- a/src/content/docs/realtime/turn/custom-domains.mdx
+++ b/src/content/docs/realtime/turn/custom-domains.mdx
@@ -12,9 +12,9 @@ Cloudflare Realtime TURN service supports using custom domains for UDP, and TCP
 
 | Protocol      | Custom domains | Primary port | Alternate port |
 | ------------- | -------------- | ------------ | -------------- |
-| STUN over UDP | ✅              | 3478/udp     | 53/udp         |
-| TURN over UDP | ✅              | 3478/udp     | 53 udp         |
-| TURN over TCP | ✅              | 3478/tcp     | 80/tcp         |
+| STUN over UDP | ✅             | 3478/udp     | 53/udp         |
+| TURN over UDP | ✅             | 3478/udp     | 53 udp         |
+| TURN over TCP | ✅             | 3478/tcp     | 80/tcp         |
 | TURN over TLS | No             | 5349/tcp     | 443/tcp        |
 
 ## Setting up a CNAME record
@@ -23,20 +23,16 @@ To use custom domains for TURN, you must create a CNAME DNS record pointing to `
 
 :::caution
 
-
 Do not resolve the address of `turn.cloudflare.com` or `stun.cloudflare.com` or use an IP address as the value you input to your DNS record. Only CNAME records are supported.
 
-
 :::
 
 Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for custom domains.
 
 :::note
 
-
 If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
-
 :::
 
 There is no additional charge to using a custom hostname with Cloudflare Realtime TURN.
diff --git a/src/content/docs/realtime/turn/generate-credentials.mdx b/src/content/docs/realtime/turn/generate-credentials.mdx
index bbb75c2c0e043bf..3f1c3bf4bf971ac 100644
--- a/src/content/docs/realtime/turn/generate-credentials.mdx
+++ b/src/content/docs/realtime/turn/generate-credentials.mdx
@@ -18,8 +18,8 @@ You should keep your TURN key on the server side (don't share it with the browse
 
 With a TURN key you can:
 
-* Generate TURN credentials that expire
-* Revoke previously issued TURN credentials
+- Generate TURN credentials that expire
+- Revoke previously issued TURN credentials
 
 ## Create credentials
 
@@ -36,12 +36,9 @@ The **201 (Created)** response below can then be passed on to your front-end app
 
 ```json
 {
-  "iceServers": [
+	"iceServers": [
 		{
-			"urls": [
-				"stun:stun.cloudflare.com:3478",
-				"stun:stun.cloudflare.com:53"
-			]
+			"urls": ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"]
 		},
 		{
 			"urls": [
@@ -67,12 +64,9 @@ Use `iceServers` as follows when instantiating the `RTCPeerConnection`:
 
 ```js
 const myPeerConnection = new RTCPeerConnection({
-  iceServers: [
-    {
-      urls: [
-				"stun:stun.cloudflare.com:3478",
-				"stun:stun.cloudflare.com:53"
-			]
+	iceServers: [
+		{
+			urls: ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"],
 		},
 		{
 			urls: [
@@ -81,14 +75,15 @@ const myPeerConnection = new RTCPeerConnection({
 				"turn:turn.cloudflare.com:3478?transport=tcp",
 				"turn:turn.cloudflare.com:80?transport=tcp",
 				"turns:turn.cloudflare.com:5349?transport=tcp",
-				"turns:turn.cloudflare.com:443?transport=tcp"
-      ],
-			"username": "bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
-			"credential": "ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0"
-    },
-  ],
+				"turns:turn.cloudflare.com:443?transport=tcp",
+			],
+			username:
+				"bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
+			credential:
+				"ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0",
+		},
+	],
 });
-
 ```
 
 The `ttl` value can be adjusted to expire the short lived key in a certain amount of time. This value should be larger than the time you'd expect the users to use the TURN service. For example, if you're using TURN for a video conferencing app, the value should be set to the longest video call you'd expect to happen in the app.
diff --git a/src/content/docs/realtime/turn/replacing-existing.mdx b/src/content/docs/realtime/turn/replacing-existing.mdx
index 2ed8f3af74ea916..7fdfd0d0da1642f 100644
--- a/src/content/docs/realtime/turn/replacing-existing.mdx
+++ b/src/content/docs/realtime/turn/replacing-existing.mdx
@@ -14,12 +14,12 @@ If you are a existing TURN provider but would like to switch to providing Cloudf
 
 Cloudflare Realtime TURN service can reduce tangible and untangible costs associated with TURN servers:
 
-* Server costs (AWS EC2 etc)
-* Bandwidth costs (Egress, load balancing etc)
-* Time and effort to set up a TURN process and maintenance of server
-* Scaling the servers up and down
-* Maintain the TURN server with security and feature updates
-* Maintain high availability
+- Server costs (AWS EC2 etc)
+- Bandwidth costs (Egress, load balancing etc)
+- Time and effort to set up a TURN process and maintenance of server
+- Scaling the servers up and down
+- Maintain the TURN server with security and feature updates
+- Maintain high availability
 
 ## Recommendations
 
@@ -56,8 +56,8 @@ When billing for TURN usage in your application, it's crucial to understand and
 
 The sampling process in TURN analytics works on two levels:
 
-* At data collection: Usage data points may be sampled if they are generated too quickly.
-* At query time: Additional sampling may occur if the query is too complex or covers a large time range.
+- At data collection: Usage data points may be sampled if they are generated too quickly.
+- At query time: Additional sampling may occur if the query is too complex or covers a large time range.
 
 To ensure accurate billing, write a single query that sums TURN usage per customer per time period, returning a single value. Avoid using queries that list usage for multiple customers simultaneously.
 
@@ -65,20 +65,16 @@ By following these guidelines and understanding how TURN analytics handles sampl
 
 :::note
 
-
 Cloudflare Realtime only bills for traffic from Cloudflare's servers to your client, called `egressBytes`.
 
-
 :::
 
 ### Example queries
 
 :::caution[Incorrect approach example]
 
-
 Querying TURN usage for multiple customers in a single query can lead to inaccurate results. This is because the usage pattern of one customer could affect the sampling rate applied to another customer's data, potentially skewing the results.
 
-
 :::
 
 ```
diff --git a/src/content/docs/realtime/turn/rfc-matrix.mdx b/src/content/docs/realtime/turn/rfc-matrix.mdx
index 88bffe6390fe56f..b2a69b56b7450d0 100644
--- a/src/content/docs/realtime/turn/rfc-matrix.mdx
+++ b/src/content/docs/realtime/turn/rfc-matrix.mdx
@@ -12,23 +12,23 @@ products:
 
 | Protocol | Support | Relevant specification                                                                                    |
 | -------- | ------- | --------------------------------------------------------------------------------------------------------- |
-| UDP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TCP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TLS      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| UDP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TCP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TLS      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
 | DTLS     | No      | [draft-petithuguenin-tram-turn-dtls-00](http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00) |
 
 ## TURN client to TURN server protocols
 
-| Protocol                                        | Support                                                                                                                        | Relevant specification                                                                                               |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
-| TURN (base RFC)                                 | ✅                                                                                                                              | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
+| Protocol                                        | Support                                                                                                                               | Relevant specification                                                                                               |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| TURN (base RFC)                                 | ✅                                                                                                                                    | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
 | TURN REST API                                   | ✅ (See [FAQ](/realtime/turn/faq/#does-cloudflare-realtime-turn-support-the-expired-ietf-rfc-draft-draft-uberti-behave-turn-rest-00)) | [draft-uberti-behave-turn-rest-00](http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)                      |
-| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                              | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
-| ALPN support for STUN & TURN                    | ✅                                                                                                                              | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
-| TURN Bandwidth draft specs                      | No                                                                                                                             | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
-| TURN-bis (with dual allocation) draft specs     | No                                                                                                                             | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
-| TCP relaying TURN extension                     | No                                                                                                                             | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
-| IPv6 extension for TURN                         | No                                                                                                                             | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
-| oAuth third-party TURN/STUN authorization       | No                                                                                                                             | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
-| DTLS support (for TURN)                         | No                                                                                                                             | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
-| Mobile ICE (MICE) support                       | No                                                                                                                             | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
+| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                                    | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
+| ALPN support for STUN & TURN                    | ✅                                                                                                                                    | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
+| TURN Bandwidth draft specs                      | No                                                                                                                                    | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
+| TURN-bis (with dual allocation) draft specs     | No                                                                                                                                    | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
+| TCP relaying TURN extension                     | No                                                                                                                                    | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
+| IPv6 extension for TURN                         | No                                                                                                                                    | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
+| oAuth third-party TURN/STUN authorization       | No                                                                                                                                    | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
+| DTLS support (for TURN)                         | No                                                                                                                                    | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
+| Mobile ICE (MICE) support                       | No                                                                                                                                    | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx
index 737fee4c2b7c58b..22b77e10e9ae65d 100644
--- a/src/content/docs/reference-architecture/architectures/sase.mdx
+++ b/src/content/docs/reference-architecture/architectures/sase.mdx
@@ -318,13 +318,13 @@ Organizations may also connect their network locations directly to the Cloudflar
 
 The following table summarizes the different methods of connecting networks to Cloudflare:
 
-| **Use case**                                                                                                                                           | **Recommended**                             | **Alternative solution**                                                                                      |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)**  | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment                           |
-| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                          | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
-| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                          | **N/A**                                                                                                       |
-| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh** | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required                              |
-| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh** | **N/A**                                                                                                       |
+| **Use case**                                                                                                                                           | **Recommended**                            | **Alternative solution**                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------- |
+| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)** | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment   |
+| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                         | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
+| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                         | **N/A**                                                                               |
+| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh**                        | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required      |
+| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh**                        | **N/A**                                                                               |
 
 Each of these methods of connecting and routing traffic can be deployed concurrently from any location. The following diagram highlights how different connectivity methods can be used in a single architecture.
 
@@ -343,8 +343,8 @@ Note the following traffic flows:
 _Note: Labels in this image may reflect a previous product name._
 
 <sub>
-	*Note: All of the endpoints connected via Cloudflare Mesh or device agent
-	are automatically assigned IP addresses from the 100.96.0.0/12 address range,
+	*Note: All of the endpoints connected via Cloudflare Mesh or device agent are
+	automatically assigned IP addresses from the 100.96.0.0/12 address range,
 	while endpoints connected to Cloudflare WAN retain their assigned RFC1918
 	private IP addresses. `cloudflared` can be deployed in any of the locations by
 	an application owner to provide hostname-based connectivity to the
diff --git a/src/content/docs/reference-architecture/architectures/security.mdx b/src/content/docs/reference-architecture/architectures/security.mdx
index 3d627ba4e4372c4..f773fce4c276399 100644
--- a/src/content/docs/reference-architecture/architectures/security.mdx
+++ b/src/content/docs/reference-architecture/architectures/security.mdx
@@ -527,7 +527,7 @@ Existing private infrastructure can be complex. Cloudflare provides a variety of
 | [Cloudflare WAN](/cloudflare-wan/)                                                                            | IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                                   | Connecting existing network routers to Cloudflare. Allowing all traffic into and out of the network to go through Cloudflare.                                                       |
 | [Cloudflare One Appliance](/cloudflare-wan/configuration/appliance/)                                          | Appliance-based IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                   | Uses the same technology as Cloudflare WAN; however, instead of using existing networking devices, a dedicated appliance or virtual machine is used — the Cloudflare One Appliance. |
 | [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/)                                         | Software agent deployed on servers or alongside services like Kubernetes for creating a tunnel for incoming connections to private applications or networks. | IT admins or application owners can easily install this tunnel software to expose their application to the Cloudflare network.                                                      |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)           | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                                       | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
 | [WARP Desktop Agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                       | Software agent deployed on user devices, creating a tunnel for traffic to and from private applications and networks.                                        | Connecting end user devices like phones and laptops to be part of the Cloudflare network.                                                                                           |
 | [Cloudflare Network Interconnect](https://www.cloudflare.com/network-services/products/network-interconnect/) | Direct connection between your physical networks and Cloudflare.                                                                                             | When your applications live in the same data centers we operate in, we can connect those networks directly to Cloudflare.                                                           |
 
diff --git a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
index 7365c6406dda2f5..fb6d969b7413b35 100644
--- a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
+++ b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
@@ -485,15 +485,15 @@ Now, you will learn how to secure RDP access as a private IP application:
 
 As mentioned before, private IP applications work because Cloudflare proxies the IP range across its network. The nature of this application necessitates the use of the device client, as unless the user is connected to Cloudflare (and more specifically, unless they can take advantage of the Client-to-Tunnel connectivity), they will not be able to reach non-local RFC 1918 addresses.
 
-| Traffic                                  |                                                                 |
-| :--------------------------------------- | :-------------------------------------------------------------- |
-| Destination IP                           | 169.254.255.254                                                 |
-| Destination Port                         | 3389                                                            |
-| **Identity**                             |                                                                 |
-| User Group Names                         | Server Admins                                                   |
-| **Device Posture**                       |                                                                 |
-| Passed Device Posture Checks             | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
-| **Action**                               | Allow                                                           |
+| Traffic                                            |                                                                 |
+| :------------------------------------------------- | :-------------------------------------------------------------- |
+| Destination IP                                     | 169.254.255.254                                                 |
+| Destination Port                                   | 3389                                                            |
+| **Identity**                                       |                                                                 |
+| User Group Names                                   | Server Admins                                                   |
+| **Device Posture**                                 |                                                                 |
+| Passed Device Posture Checks                       | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
+| **Action**                                         | Allow                                                           |
 | **Enforce Cloudflare One Client session duration** | 60m0s                                                           |
 
 Defining the application here is simple, as Cloudflare automatically fills in the IP range, and you need to limit the detected protocol to RDP. However, the rules for private IP applications are slightly different. You will notice they appear as network policies under the Cloudflare Gateway menu, despite managing them in Access. Certain options, such as checking for MFA and external evaluation, do not appear here. However, these attributes can be verified when the user activates their device client and authenticates to their organization.
diff --git a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
index dc60c3bd546f404..6b66d65a74db8d4 100644
--- a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
+++ b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
@@ -33,15 +33,15 @@ This solution supports subdomains under your own zone while also allowing your c
 
 Before looking at how Cloudflare can be configured to protect your SaaS application through your custom hostnames, it's worth reviewing the benefits of taking this approach.
 
-| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                                                       |
-| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                                                               |
-| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                                                    |
-| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                                                               |
-| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                                                    |
+| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                   |
+| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                           |
+| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                |
+| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                           |
+| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                |
 | O2O                      | For end-customers who already proxy traffic through Cloudflare, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) may be required. Generally, it's recommended for those end-customers to [not proxy](/dns/proxy-status/#dns-only-records) the hostnames used by the SaaS provider. If O2O functionality is required, please review the [product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/). |
-| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                                                                |
+| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                            |
 
 ## Products included in this guide
 
diff --git a/src/content/docs/reference-architecture/diagrams/ai/index.mdx b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
index a86575102d8dcfa..31b853acdc50598 100644
--- a/src/content/docs/reference-architecture/diagrams/ai/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
@@ -12,6 +12,6 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
index 65249beeb1e0af4..b78ee67b330dcc6 100644
--- a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
@@ -12,6 +12,6 @@ products:
   - cache
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
index 0e82981e3eafb7b..52648681f876333 100644
--- a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
+++ b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
@@ -1,7 +1,20 @@
 ---
 title: Optimizing and securing connected transportation systems
 pcx_content_type: reference-architecture-diagram
-products: [argo-smart-routing, api-shield, cache, ddos-protection, dns-firewall, load-balancing, r2, workers, ssl, waf, workers-ai]
+products:
+  [
+    argo-smart-routing,
+    api-shield,
+    cache,
+    ddos-protection,
+    dns-firewall,
+    load-balancing,
+    r2,
+    workers,
+    ssl,
+    waf,
+    workers-ai,
+  ]
 sidebar:
   order: 1
   label: Connected transportation systems
@@ -29,7 +42,6 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
 2. **Cloudflare anycast network**: Cloudflare uses [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) networking and is one of the world's most connected and geographically distributed networks. Traffic is routed to the nearest Cloudflare data center, which reduces the number of network hops, dynamically adapts to changing network conditions, and ensures data takes the shortest path to its destination, minimizing latency and maximizing reliability.
 
 3. **Security services**:
-
    1. **API Shield**: Cloudflare's [API Shield](/api-shield/get-started/) protects critical APIs from unauthorized access and abuse, ensuring secure data exchange between connected systems.
    2. **Web Application Firewall (WAF)**: Cloudflare's [WAF](/waf/) helps block malicious traffic and prevent application or API vulnerabilities from being exploited, safeguarding your network, devices and applications.
    3. **DDoS Protection**: Cloudflare's [DDoS protection](/ddos-protection/about/attack-coverage/), covering the network, transport and application layer, prevents volumetric attacks that could compromise the availability of connected systems. By providing multi-layered protection, Cloudflare is able to mitigate a wide variety of DDoS threats. At lower layers, Cloudflare defends against high-volume attacks such as SYN floods, UDP floods, and other types of protocol-based disruptions that can overwhelm network resources. At the application layer, more sophisticated attacks targeting the application itself, such as HTTP floods \- which aim to exhaust server resources and disrupt user-facing services \- are blocked even in the face of [large-scale DDoS attempts](https://blog.cloudflare.com/tag/ddos-reports/).
@@ -37,7 +49,6 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
    5. **TLS encryption**: [TLS encryption](/ssl/edge-certificates/) ensures that data exchanged across the network is protected from interception, maintaining data integrity and privacy.
 
 4. **Performance and reliability services**:
-
    1. **Content Delivery Network (CDN)**: [Distribute content](https://www.cloudflare.com/en-gb/learning/cdn/what-is-a-cdn/) efficiently across the network, reducing latency for end users by caching data closer to them.
    2. **Load balancing**: [Distribute incoming traffic](/load-balancing/get-started/quickstart/) across multiple servers or data centers, ensuring optimal resource utilization, preventing single points of failure, and improving the performance of connected systems.
    3. **Cloudflare Workers**: Our serverless compute platform, [Cloudflare Workers](/workers/), allows data processing at the edge, reducing the need for data to travel long distances and significantly reducing latency. Combined with related services like [Workers KV](/kv/get-started/) and [D1](https://www.cloudflare.com/en-gb/developer-platform/products/d1/), Cloudflare's edge-based storage solutions enable efficient data management close to the user. Workers KV allows for quick, read-heavy data access, perfect for caching configurations and frequently used data, while D1 provides a serverless SQL database for more robust storage needs. Additionally, Cloudflare's [Durable Objects](https://blog.cloudflare.com/sqlite-in-durable-objects/) help manage stateful interactions at the edge, facilitating real-time data consistency. These tools together allow for seamless data processing, storage and lazy updates to core services, minimizing back-and-forth to centralized servers and ensuring faster, more efficient performance.
diff --git a/src/content/docs/reference-architecture/diagrams/network/index.mdx b/src/content/docs/reference-architecture/diagrams/network/index.mdx
index dab7f9b29c2ac8b..8d297fcb542d684 100644
--- a/src/content/docs/reference-architecture/diagrams/network/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/network/index.mdx
@@ -12,6 +12,6 @@ products:
   - magic-transit
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/sase/index.mdx b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
index 952f8cbb7035014..5a5bcdc66e7f753 100644
--- a/src/content/docs/reference-architecture/diagrams/sase/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
@@ -12,6 +12,6 @@ products:
   - cloudflare-one
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/security/index.mdx b/src/content/docs/reference-architecture/diagrams/security/index.mdx
index 6e7f959a2bf1894..b6a5e7116f9b9ab 100644
--- a/src/content/docs/reference-architecture/diagrams/security/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/security/index.mdx
@@ -12,6 +12,6 @@ products:
   - waf
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
index be169cd2360397e..80a5daa8d28537b 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
@@ -1,7 +1,32 @@
 ---
 title: Fullstack applications
 pcx_content_type: reference-architecture-diagram
-products: [ai-gateway, agents, api-shield, bots, containers, d1, ddos-protection, durable-objects, images, kv, logs, pages, pipelines, queues, r2, realtime, ssl, stream, vectorize, waf, workflows, workers, workers-ai]
+products:
+  [
+    ai-gateway,
+    agents,
+    api-shield,
+    bots,
+    containers,
+    d1,
+    ddos-protection,
+    durable-objects,
+    images,
+    kv,
+    logs,
+    pages,
+    pipelines,
+    queues,
+    r2,
+    realtime,
+    ssl,
+    stream,
+    vectorize,
+    waf,
+    workflows,
+    workers,
+    workers-ai,
+  ]
 sidebar:
   order: 1
   label: Fullstack applications
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
index fd828080d0d13a7..ec24b3e2d1e0920 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
@@ -11,6 +11,6 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
index 59502f5c65c9030..37a97208f955c57 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
@@ -94,7 +94,6 @@ Data observability and control is crucial for security. [Outbound Workers](/clou
 1. **Management Interface**: Interact with the platform through GUI, API, or CLI interfaces.
 
 2. **Platform Processing**: Process these interactions to:
-
    - Transform and bundle code
    - Perform security checks
    - Apply configuration
diff --git a/src/content/docs/reference-architecture/diagrams/storage/index.mdx b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
index bed6aa10ef8f5ae..c1a8deb1e885b1a 100644
--- a/src/content/docs/reference-architecture/diagrams/storage/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
@@ -11,6 +11,6 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/implementation-guides/index.mdx b/src/content/docs/reference-architecture/implementation-guides/index.mdx
index 2904c70b1df0a79..050e352a4e30355 100644
--- a/src/content/docs/reference-architecture/implementation-guides/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/index.mdx
@@ -23,4 +23,4 @@ Implementation guides provide [step-by-step instructions](/reference-architectur
 
 ## Application Security
 
-- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
\ No newline at end of file
+- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
diff --git a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
index 5c5f919b63c0538..2fdb4a789da4092 100644
--- a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
@@ -19,4 +19,4 @@ Zero Trust implementation guides walk you through the steps to deploy a Zero Tru
 - [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/)
 - [Replace your VPN](/learning-paths/replace-vpn/concepts/)
 - [Deploy Zero Trust Web Access](/learning-paths/clientless-access/concepts/)
-- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
\ No newline at end of file
+- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
diff --git a/src/content/docs/registrar/account-options/domain-contact-updates.mdx b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
index c68e021cdb34a52..33cc9a043acdbdd 100644
--- a/src/content/docs/registrar/account-options/domain-contact-updates.mdx
+++ b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
@@ -12,18 +12,18 @@ It is important that you keep your contact details accurate and up-to-date. [ICA
 
 The contact information you can update includes:
 
-* First name
-* Last name
-* Email
-* Organization
-* Phone
-* Address including City, State/Province, Postal code & Country
+- First name
+- Last name
+- Email
+- Organization
+- Phone
+- Address including City, State/Province, Postal code & Country
 
 To update your registrant contacts:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find **Default contact** and select **Edit**.
 3. Update the relevant information, and select **Save**.
@@ -32,10 +32,10 @@ To update your registrant contacts:
 
 If you change any of the following fields, Cloudflare Registrar will require a Change of Registrant approval before the changes are finalized:
 
-* First name
-* Last name
-* Organization
-* Email address
+- First name
+- Last name
+- Organization
+- Email address
 
 If you update any of the fields mentioned above, Cloudflare Registrar will send an approval email to the current registrant's email address. The approval email contains a link to a web page where the requested change may be viewed and approved or rejected. If the pending change is not approved or rejected within seven days, the request will automatically be canceled.
 
@@ -43,11 +43,9 @@ If you do not update these fields, your contact information is updated immediate
 
 :::caution[Important]
 
-
 After selecting the link in the approval email Cloudflare sends you, you have the option to accept or reject the contact changes. If you select the **Accept** button, your domain will be transfer-locked for 60 days.
 
-If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox *before* selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
-
+If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox _before_ selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
 
 :::
 
diff --git a/src/content/docs/registrar/account-options/domain-management.mdx b/src/content/docs/registrar/account-options/domain-management.mdx
index b00b69c71cdde48..436f7461a485b3f 100644
--- a/src/content/docs/registrar/account-options/domain-management.mdx
+++ b/src/content/docs/registrar/account-options/domain-management.mdx
@@ -6,7 +6,7 @@ products:
 description: Manage your registered domains in the dashboard.
 ---
 
-import { DashButton, LinkButton } from "~/components"
+import { DashButton, LinkButton } from "~/components";
 
 ## Domain status
 
@@ -14,9 +14,9 @@ When your domain is registered with Cloudflare, you can review your domain statu
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date. 
+2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date.
 3. Select **Manage domain** to review the Auto-Renew status for your domain.
 
 ## Billing information
@@ -25,7 +25,7 @@ Domain registrations will not appear in the **Active Subscriptions** section of
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to check and select **Manage**.
 3. Refer to **Registration** for information regarding your domain fees. From here, you can also opt to [renew or extend](/registrar/account-options/renew-domains/) your domain registration.
@@ -36,7 +36,7 @@ Cloudflare redacts WHOIS information from your domain by default. However, we do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to edit and select **Manage** > **Contacts**.
 3. Select **Edit** in any of the contacts you previously set up. This allows you to update the contact information for the selected domain only. It will not update the contact information for other domains within the account.
@@ -62,10 +62,10 @@ There may be instances where users may wish to delete a domain prior to expirati
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-3. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
-4. If the domain is deletable the button will be active.  The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
-5. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
+2. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
+3. If the domain is deletable the button will be active. The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
+4. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
 
 Once all steps are completed, the domain will then be scheduled for deletion. To understand more about the timelines and potential reasons why a domain cannot be deleted, refer to the Registrar [FAQ](/registrar/faq/#domain-deletions).
diff --git a/src/content/docs/registrar/account-options/icloud-domains.mdx b/src/content/docs/registrar/account-options/icloud-domains.mdx
index 7cd576b2342f223..51ea04635dec389 100644
--- a/src/content/docs/registrar/account-options/icloud-domains.mdx
+++ b/src/content/docs/registrar/account-options/icloud-domains.mdx
@@ -17,7 +17,7 @@ You will need an active iCloud+ subscription to add a custom email domain.
 
 If you want to buy a custom email domain, go to your [iCloud](https://www.icloud.com/settings/) settings and scroll down to **Custom Email Domain**.
 
-***
+---
 
 ## Log in to Cloudflare
 
@@ -31,7 +31,7 @@ If you had signed up with Apple, signing into Cloudflare is as easy as clicking
 
 If you had signed up with Cloudflare, signing into Cloudflare can be done with your email and password.
 
-***
+---
 
 ## Billing information
 
@@ -39,9 +39,9 @@ If you had signed up with Cloudflare, signing into Cloudflare can be done with y
 
 For domain registration, Cloudflare supports the following payment methods:
 
-* Credit Card
-* PayPal
-* Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
+- Credit Card
+- PayPal
+- Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
 
 For domain renewals, Apple Pay does not currently support recurring payments. You can either add another payment method (Credit Card or PayPal) for automatic renewals or log into [your account](#log-in-to-cloudflare) near the renewal date and use Apple Pay.
 
@@ -51,7 +51,7 @@ Users may see a price estimate in both U.S. Dollars and a local currency. This i
 
 The final payment will be charged in US dollars.
 
-***
+---
 
 ## Email issues
 
@@ -67,7 +67,7 @@ If you are not receiving emails intended for your new email address, review your
 
 If your domain has records similar to those listed above and you are still experiencing problems with your new email address, contact [Apple Support](https://support.apple.com/).
 
-***
+---
 
 ## Domain website
 
@@ -80,7 +80,7 @@ If you want your domain to be a fully functioning website, you will need to:
 1. **Build your website**: Either using [Cloudflare Pages](/pages/), a website builder, or files hosted on a server.
 2. **Update your Cloudflare DNS**: To direct visitors looking for your domain name to the actual content on your website ([detailed guide](/dns/manage-dns-records/how-to/create-zone-apex/)).
 
-***
+---
 
 ## Landing Page
 
@@ -92,18 +92,16 @@ If you do not want to have Landing Page enabled:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-3. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
-4. Scroll to Landing Page and select **Disable**.
+2. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
+3. Scroll to Landing Page and select **Disable**.
 
 You now have Landing Page disabled. The page can also be re-enabled through the same process.
 
 :::note
 
-
 Customers must disable the landing page before they can add DNS records
 to point to a new website.
 
-
 :::
diff --git a/src/content/docs/registrar/account-options/index.mdx b/src/content/docs/registrar/account-options/index.mdx
index c28da7b171d3437..0ad0fed63956d72 100644
--- a/src/content/docs/registrar/account-options/index.mdx
+++ b/src/content/docs/registrar/account-options/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Explore Cloudflare Registrar account options.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/account-options/inter-account-transfer.mdx b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
index 9ec8ed6c910675e..8089af6ebb59ebd 100644
--- a/src/content/docs/registrar/account-options/inter-account-transfer.mdx
+++ b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
@@ -15,28 +15,29 @@ This process only applies to domains which are registered with Cloudflare Regist
 
 Before proceeding, please be aware of the following:
 
-* WHOIS contact information will be moved as is.
-* No other configuration will be moved.
-* After successful move, the registration will be transfer-locked for 30 days.
-* The target account will become responsible for domain renewals going forward.
+- WHOIS contact information will be moved as is.
+- No other configuration will be moved.
+- After successful move, the registration will be transfer-locked for 30 days.
+- The target account will become responsible for domain renewals going forward.
 
 ## 1. Prepare for the move
 
 Before you request the move, you will need to do the following:
 
-* Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
-* Add the domain as a website to the new account and select a plan.
-* [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
+- Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
+- Add the domain as a website to the new account and select a plan.
+- [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
 
 The following pre-conditions must be met before the domain can be moved:
-* The domain must have been registered more than 10 days ago.
-* The domain must be added to the new account as a website and a plan must be selected.
-* The domain must not be administratively locked, such as being locked due to a dispute or court order.
-* The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
-* The registrant email address must be verified.
-* A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
-* DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
-* If the current zone is locked, the lock must be released.
+
+- The domain must have been registered more than 10 days ago.
+- The domain must be added to the new account as a website and a plan must be selected.
+- The domain must not be administratively locked, such as being locked due to a dispute or court order.
+- The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
+- The registrant email address must be verified.
+- A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
+- DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
+- If the current zone is locked, the lock must be released.
 
 ## 2. Submit the move request
 
diff --git a/src/content/docs/registrar/account-options/renew-domains.mdx b/src/content/docs/registrar/account-options/renew-domains.mdx
index dda7c66958054bd..285bff694c78d57 100644
--- a/src/content/docs/registrar/account-options/renew-domains.mdx
+++ b/src/content/docs/registrar/account-options/renew-domains.mdx
@@ -21,10 +21,8 @@ If you decide you no longer need the domain, [disable auto-renew for your domain
 
 :::note[Note]
 
-
 The first auto-renew attempt will occur approximately 30 days prior to expiration. If you wish to disable auto-renew, do so at least 30 days prior to the expiration date.
 
-
 :::
 
 You can continue to keep your domain registered with Cloudflare for the time remaining until the expiration date. If you decide you want to keep the domain, enable auto-renew at any time prior to expiration.
@@ -35,7 +33,7 @@ If you want your domains to renew automatically, keep the default settings for y
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to automatically renew, and make sure the **Auto-renew** toggle is enabled.
 
@@ -47,10 +45,8 @@ If the renewal fails, you will receive an email notification and Cloudflare will
 
 :::note
 
-
 If you want to delete your domain from Cloudflare, **disable** Auto-Renew first.
 
-
 :::
 
 ## Renew a domain manually
@@ -59,7 +55,7 @@ You can renew a domain at any time. To renew a domain registered with Cloudflare
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to renew and select **Manage**.
 3. In **Registration** select **Renew/Extend Domain**.
@@ -72,24 +68,22 @@ Once Cloudflare validates your payment, the status of your domain changes to **R
 
 Once a domain is registered, Registrar sends the following expiration notices to the Super Admin of the domain:
 
-* A monthly email listing all domains set to renew automatically within the next 45 days.
-* A monthly email listing all domains expiring in the next 60-90 days.
+- A monthly email listing all domains set to renew automatically within the next 45 days.
+- A monthly email listing all domains expiring in the next 60-90 days.
 
 In addition to the Super Admin, the following expiration notices are sent to the WHOIS Registrant contact associated with the domain:
 
-* A weekly email listing all domains expiring within the next month.
-* A daily email listing all domains expiring in seven days.
-* An email one day after a domain expires.
-* An email 20 days after the expiration date.
+- A weekly email listing all domains expiring within the next month.
+- A daily email listing all domains expiring in seven days.
+- An email one day after a domain expires.
+- An email 20 days after the expiration date.
 
 :::note
 
-
 If you do not renew your domain before the expiration date, your domain will enter a Redemption Grace Period (RGP) for 30 days. These domains are not deleted and you can restore them to your account, but restoration may require an additional fee. You cannot transfer domains during the RGP.
 
 All renewals are final and Cloudflare will not issue refunds.
 
 When renewing a domain, additional years are always added to the current expiration date regardless of when the renewal takes place.
 
-
 :::
diff --git a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
index b699b2181413945..9c7bbb499016c44 100644
--- a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
+++ b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
@@ -13,9 +13,9 @@ import { DashButton } from "~/components";
 
 Cloudflare Registrar makes it easy to transfer your domain to another registrar. Be aware that ICANN rules prohibit a domain from being transferred if:
 
-* The domain has been transferred within the last 60 days;
-* The domain was registered within the last 60 days;
-* If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
+- The domain has been transferred within the last 60 days;
+- The domain was registered within the last 60 days;
+- If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
 
 Follow the instructions below to transfer your domain out from Cloudflare.
 
@@ -28,7 +28,7 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to transfer, and select **Manage**.
 3. Select **Configuration** > **Unlock**.
@@ -37,8 +37,8 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 If you lose your authentication code, you can get a new one by:
 
-* Selecting the **Regenerate** button;
-* Locking the domain and repeating steps 1-6.
+- Selecting the **Regenerate** button;
+- Locking the domain and repeating steps 1-6.
 
 ## 2. Transfer to a new registrar
 
diff --git a/src/content/docs/registrar/account-options/whois-redaction.mdx b/src/content/docs/registrar/account-options/whois-redaction.mdx
index 54f84e462053f44..ae936db97b56984 100644
--- a/src/content/docs/registrar/account-options/whois-redaction.mdx
+++ b/src/content/docs/registrar/account-options/whois-redaction.mdx
@@ -20,8 +20,8 @@ Cloudflare’s WHOIS service can be found at [https://rdap.cloudflare.com/](http
 
 WHOIS redaction removes most contact information categorized as personal data (such as registrant name, email address, postal address) from the published WHOIS record for a domain. These fields will read `Data Redacted`. The nameserver, domain lock information, and date records for a domain are still available publicly. The following fields will continue to show in WHOIS, due to ICANN policy:
 
-* Registrant state/province
-* Registrant country
+- Registrant state/province
+- Registrant country
 
 Cloudflare still maintains the authoritative, unredacted, record of your WHOIS data. You can modify this information at any time. Refer to [Registrant contact updates](/registrar/account-options/domain-contact-updates) for more information.
 
diff --git a/src/content/docs/registrar/custom-domain-protection.mdx b/src/content/docs/registrar/custom-domain-protection.mdx
index 5175f44c6cba05f..7c230831d9ec50c 100644
--- a/src/content/docs/registrar/custom-domain-protection.mdx
+++ b/src/content/docs/registrar/custom-domain-protection.mdx
@@ -12,8 +12,8 @@ Cloudflare offers [Custom Domain Protection](https://www.cloudflare.com/products
 
 Custom Domain Protection offers additional safeguard features for registered domains, including:
 
-* **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
-* **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
-* **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
+- **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
+- **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
+- **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
 
 Contact your account team if you are interested in Cloudflare's Custom Domain Protection.
diff --git a/src/content/docs/registrar/get-started/index.mdx b/src/content/docs/registrar/get-started/index.mdx
index 0337c455830ed00..adddbd0c163091c 100644
--- a/src/content/docs/registrar/get-started/index.mdx
+++ b/src/content/docs/registrar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Set up Client IP Geolocation for your network.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/get-started/register-domain.mdx b/src/content/docs/registrar/get-started/register-domain.mdx
index b3d8c632b668672..7f46b29e462ccda 100644
--- a/src/content/docs/registrar/get-started/register-domain.mdx
+++ b/src/content/docs/registrar/get-started/register-domain.mdx
@@ -10,15 +10,14 @@ description: Register a new domain with Cloudflare.
 
 import { DashButton, Render } from "~/components";
 
-
 ## Prerequisites and restrictions
 
 :::note[Cloudflare nameservers]
 All domains acquired via Cloudflare Registrar use Cloudflare nameservers, automatically [protecting and speeding up](/fundamentals/concepts/how-cloudflare-works/) your content or services. You will not be able to change to another DNS provider's nameservers while using Cloudflare Registrar.
 :::
 
-* Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
-* You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
+- Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
+- You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
 
 <Render file="icann-unverified-email" product="registrar" />
 
@@ -30,16 +29,14 @@ If you are registering a `.us` domain, refer to the [Additional requirements for
 
 1. In the Cloudflare dashboard, go to the **Register domains** page.
 
-    <DashButton url="/?to=/:account/registrar/register" />
+   <DashButton url="/?to=/:account/registrar/register" />
 
 2. In the search box, enter the domain name you wish to register, and select **Search**. You may also enter one or more keywords. The search results will contain a list of suggested domains. If the domain you entered does not appear in the list, this means it is not available for registration.
 
 :::caution[Important]
 
-
 Cloudflare Registrar currently does not support internationalized domain names (IDNs), also known as unicode. For that reason, you cannot search for words with special characters, such as `à`, `ü`, `ç`, among others.
 
-
 :::
 
 3. Select **Purchase** on the domain you wish to register. In rare instances, a domain that is not available for registration may appear in the search results. After selecting **Purchase**, a definitive availability check will be performed to confirm that the domain is actually available for registration.
@@ -52,12 +49,10 @@ Cloudflare Registrar currently does not support internationalized domain names (
 
 :::note
 
-
 If you have previously registered or transferred a domain name, the form will be filled in advance with the information from your default contact. If not, you will need to fill out the form.
 
 It is important that you provide complete and accurate contact information. If you do not follow this recommendation, the domain registration may be suspended and/or canceled.
 
-
 :::
 
 6. In **Payment**, select which type of payment you want to use. If you already have a billing profile, Cloudflare uses this information to automatically fill the form. If there is no billing profile, you need to enter your payment information.
@@ -72,8 +67,6 @@ The registration process may take up to 30 seconds to complete. Once the registr
 
 At this time, you can only use ASCII characters for contact data. If the default contact has non-ASCII characters, you will need to update the domain contact details before proceeding. Cloudflare recommends that you update your default contact information to include ASCII characters only.
 
-
-
 | Field        | Required? | Restrictions                                                                                                                   |
 | ------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
 | First Name   | Yes       | Minimum of two letters.                                                                                                        |
@@ -89,8 +82,6 @@ At this time, you can only use ASCII characters for contact data. If the default
 | Country      | Yes       | You must select one from the drop-down options.                                                                                |
 | Postal Code  | Yes       | Must be a properly formatted postal code.                                                                                      |
 
-
-
 When you register a domain with Cloudflare, your personal information is redacted when permitted by the registry. Refer to [WHOIS redaction](/registrar/account-options/whois-redaction/) for more information.
 
 ## Next steps
diff --git a/src/content/docs/registrar/top-level-domains/uk-domains.mdx b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
index 33034fbe090ae38..4ec5d8a00c26f8f 100644
--- a/src/content/docs/registrar/top-level-domains/uk-domains.mdx
+++ b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
@@ -22,22 +22,16 @@ Cloudflare currently supports the transfer of `.uk`, `co.uk`, `org.uk`, and `me.
 
 1. In the Cloudflare dashboard, go to the **Transfer domains** page.
 
-    <DashButton url="/?to=/:account/registrar/transfer" />
+   <DashButton url="/?to=/:account/registrar/transfer" />
 
-Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain.
-2. Select the domains you wish to transfer.
-3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process.
-4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days.
-5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
+Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain. 2. Select the domains you wish to transfer. 3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process. 4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days. 5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
 
 :::caution[Warning]
 
-
 If you request your current registrar to update the IPS tag before completing the checkout process, the transfer request will be automatically rejected. You must complete the checkout process before requesting the IPS tag update.
 
 For security reasons, domains transferred to Cloudflare Registrar are locked for 60 days before they can be transferred out to another Registrar.
 
-
 :::
 
 ## Transfer a .UK domain to another registrar
@@ -52,8 +46,6 @@ Your new registrar is responsible for accepting the transfer. Cloudflare has no
 
 :::note
 
-
 If you do not know the IPS tag, contact your new registrar for instructions. Your new registrar may require you to follow some additional steps before starting the transfer process.
 
-
 :::
diff --git a/src/content/docs/registrar/whoisrequests.mdx b/src/content/docs/registrar/whoisrequests.mdx
index 445ca659095fc8e..95317e78416dd66 100644
--- a/src/content/docs/registrar/whoisrequests.mdx
+++ b/src/content/docs/registrar/whoisrequests.mdx
@@ -10,7 +10,7 @@ description: Submit WHOIS disclosure requests to Cloudflare.
 
 This page describes the mechanism and process for submitting a disclosure request to Cloudflare for WHOIS data under Section 10 of the Internet Corporation for Assigned Names and Number's ("ICANN") [Registration Data Policy](https://www.icann.org/en/contracted-parties/consensus-policies/registration-data-policy).
 
-Please read the following instructions carefully.  
+Please read the following instructions carefully.
 
 ## 1. Prepare your request
 
@@ -18,7 +18,7 @@ Your request must include the following elements:
 
 - Your name
 - The requestor's name, mailing address, and email
-- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity.  If the latter, identify whether the requestor is an individual, corporation, or government
+- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity. If the latter, identify whether the requestor is an individual, corporation, or government
 - Any power of Attorney statements or similar statements evidencing authorization to act on the requestor's behalf, where applicable and relevant
 - A list of data element values requested by the requestor
 - Information about the legal rights of the requestor and specific rationale and basis for the request
diff --git a/src/content/docs/resource-tagging/get-started.mdx b/src/content/docs/resource-tagging/get-started.mdx
index 5a8aa68ee493d82..b9bc956239e99a5 100644
--- a/src/content/docs/resource-tagging/get-started.mdx
+++ b/src/content/docs/resource-tagging/get-started.mdx
@@ -26,13 +26,13 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys
 
 ### Interpreting the response
 
-| Response | Meaning | Action |
-| --- | --- | --- |
-| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step. |
-| **403** mentioning "permission" or "role" | The caller lacks required permissions. | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope. |
-| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance. |
-| **401 Unauthorized** | Authentication failed. | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header. |
-| Any other response | Unexpected error. | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
+| Response                                             | Meaning                                                            | Action                                                                                                                                                        |
+| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step.                                                                                                                                     |
+| **403** mentioning "permission" or "role"            | The caller lacks required permissions.                             | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope.                    |
+| **403** mentioning "feature" or "gate"               | Tagging is not enabled for this account.                           | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance.                                                                         |
+| **401 Unauthorized**                                 | Authentication failed.                                             | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header.                                                        |
+| Any other response                                   | Unexpected error.                                                  | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
 
 ## 2. Create your first tags
 
diff --git a/src/content/docs/resource-tagging/how-to/index.mdx b/src/content/docs/resource-tagging/how-to/index.mdx
index 8c39e93b47e1641..daacb0f1c1aa2d4 100644
--- a/src/content/docs/resource-tagging/how-to/index.mdx
+++ b/src/content/docs/resource-tagging/how-to/index.mdx
@@ -7,6 +7,6 @@ head:
     content: How-to guides
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/how-to/manage-tags.mdx b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
index 813ad1a57752b9b..9625cc22be99763 100644
--- a/src/content/docs/resource-tagging/how-to/manage-tags.mdx
+++ b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
@@ -75,9 +75,9 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags?reso
 
 ```json
 {
-  "environment": "production",
-  "team": "platform",
-  "cost-center": "engineering"
+	"environment": "production",
+	"team": "platform",
+	"cost-center": "engineering"
 }
 ```
 
diff --git a/src/content/docs/resource-tagging/reference/error-codes.mdx b/src/content/docs/resource-tagging/reference/error-codes.mdx
index 7f1cd73a0d758bf..026f122644541f7 100644
--- a/src/content/docs/resource-tagging/reference/error-codes.mdx
+++ b/src/content/docs/resource-tagging/reference/error-codes.mdx
@@ -8,19 +8,19 @@ description: Tagging API error codes, causes, and resolutions.
 
 ## Error code reference
 
-| Code | HTTP status | Message | Likely cause | Resolution |
-| --- | --- | --- | --- | --- |
-| `1002` | 400 | Invalid set payload | Request body is malformed or missing required fields | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
-| `1003` | 400 | `resource_type` and `resource_id` are required | Missing query parameters | Include both `resource_type` and `resource_id` in the query string |
-| `1006` | 400 | Invalid resource type | Unsupported resource type | Use a [supported resource type](/resource-tagging/reference/resource-types/) |
-| `1007` | 400 | tag parameter must be in format... | Tag filter syntax is incorrect | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/) |
-| `1009` | 400 | `tag_key` is required | Missing `tag_key` parameter | Include the `tag_key` path parameter |
-| `1010` | 400 | too many tag filters (maximum 20) | More than 20 `tag` query parameters | Reduce filters to 20 or fewer, or split across multiple requests |
-| `1011` | 400 | tag key too long (maximum 256 characters) | Tag key exceeds 256 characters | Shorten the tag key |
-| `1012` | 400 | tag value too long (maximum 1024 characters) | Tag value exceeds 1,024 characters | Shorten the tag value |
-| `1013` | 400 | too many OR values in tag filter (maximum 10) | More than 10 comma-separated values in a single filter | Split into multiple filters |
-| `1014` | 400 | Invalid tag key | Key contains invalid characters | Use only letters, digits, `_`, `.`, `-` |
-| `1015` | 400 | Invalid delete payload | Delete request body is malformed | Verify the body includes `resource_type` and `resource_id` |
+| Code   | HTTP status | Message                                        | Likely cause                                           | Resolution                                                                    |
+| ------ | ----------- | ---------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------- |
+| `1002` | 400         | Invalid set payload                            | Request body is malformed or missing required fields   | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
+| `1003` | 400         | `resource_type` and `resource_id` are required | Missing query parameters                               | Include both `resource_type` and `resource_id` in the query string            |
+| `1006` | 400         | Invalid resource type                          | Unsupported resource type                              | Use a [supported resource type](/resource-tagging/reference/resource-types/)  |
+| `1007` | 400         | tag parameter must be in format...             | Tag filter syntax is incorrect                         | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/)   |
+| `1009` | 400         | `tag_key` is required                          | Missing `tag_key` parameter                            | Include the `tag_key` path parameter                                          |
+| `1010` | 400         | too many tag filters (maximum 20)              | More than 20 `tag` query parameters                    | Reduce filters to 20 or fewer, or split across multiple requests              |
+| `1011` | 400         | tag key too long (maximum 256 characters)      | Tag key exceeds 256 characters                         | Shorten the tag key                                                           |
+| `1012` | 400         | tag value too long (maximum 1024 characters)   | Tag value exceeds 1,024 characters                     | Shorten the tag value                                                         |
+| `1013` | 400         | too many OR values in tag filter (maximum 10)  | More than 10 comma-separated values in a single filter | Split into multiple filters                                                   |
+| `1014` | 400         | Invalid tag key                                | Key contains invalid characters                        | Use only letters, digits, `_`, `.`, `-`                                       |
+| `1015` | 400         | Invalid delete payload                         | Delete request body is malformed                       | Verify the body includes `resource_type` and `resource_id`                    |
 
 :::note[Error 1007 note]
 The error message text references `:` as the tag filter separator (for example, `key:value`), but the API implementation uses `=` in query parameters (for example, `tag=key=value`). The error message is outdated — always use `=` when constructing tag filters.
diff --git a/src/content/docs/resource-tagging/reference/index.mdx b/src/content/docs/resource-tagging/reference/index.mdx
index 6de666492e69204..9361dd2c4b8a0cd 100644
--- a/src/content/docs/resource-tagging/reference/index.mdx
+++ b/src/content/docs/resource-tagging/reference/index.mdx
@@ -7,6 +7,6 @@ head:
     content: Reference
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/reference/limits.mdx b/src/content/docs/resource-tagging/reference/limits.mdx
index 350cb2973f6183a..85a5ee4696d5f45 100644
--- a/src/content/docs/resource-tagging/reference/limits.mdx
+++ b/src/content/docs/resource-tagging/reference/limits.mdx
@@ -8,14 +8,14 @@ description: API limits, tag key validation rules, and pagination behavior.
 
 ## API limits
 
-| Limit | Value | Error code |
-| --- | --- | --- |
-| Maximum tags per account | 10,000 (beta) | N/A |
-| Maximum tag key length | 256 characters | `1011` |
-| Maximum tag value length | 1,024 characters | `1012` |
-| Maximum tag filters per query | 20 | `1010` |
-| Maximum OR values per filter | 10 | `1013` |
-| Results per page | 100 (fixed) | N/A |
+| Limit                         | Value            | Error code |
+| ----------------------------- | ---------------- | ---------- |
+| Maximum tags per account      | 10,000 (beta)    | N/A        |
+| Maximum tag key length        | 256 characters   | `1011`     |
+| Maximum tag value length      | 1,024 characters | `1012`     |
+| Maximum tag filters per query | 20               | `1010`     |
+| Maximum OR values per filter  | 10               | `1013`     |
+| Results per page              | 100 (fixed)      | N/A        |
 
 When a limit is exceeded, the API returns `400 Bad Request` with the corresponding error code.
 
@@ -45,16 +45,16 @@ Tag keys must follow these character rules:
 
 ### Examples
 
-| Key | Valid | Reason |
-| --- | --- | --- |
-| `environment` | Yes | Letters only |
-| `team_name` | Yes | Underscore |
-| `cost-center` | Yes | Hyphen |
-| `owner.email` | Yes | Period |
-| `env123` | Yes | Letters and digits |
-| `env name` | **No** | Contains space |
-| `team@work` | **No** | Special character `@` |
-| (empty) | **No** | Empty string |
+| Key           | Valid  | Reason                |
+| ------------- | ------ | --------------------- |
+| `environment` | Yes    | Letters only          |
+| `team_name`   | Yes    | Underscore            |
+| `cost-center` | Yes    | Hyphen                |
+| `owner.email` | Yes    | Period                |
+| `env123`      | Yes    | Letters and digits    |
+| `env name`    | **No** | Contains space        |
+| `team@work`   | **No** | Special character `@` |
+| (empty)       | **No** | Empty string          |
 
 Invalid tag keys return `400 Bad Request` with error code `1014`.
 
@@ -63,6 +63,7 @@ Invalid tag keys return `400 Bad Request` with error code `1014`.
 List endpoints use cursor-based pagination with a fixed page size of 100. The page size is not configurable.
 
 Paginated endpoints:
+
 - `GET /accounts/{account_id}/tags/keys`
 - `GET /accounts/{account_id}/tags/resources`
 - `GET /accounts/{account_id}/tags/values/{tag_key}`
diff --git a/src/content/docs/resource-tagging/reference/resource-types.mdx b/src/content/docs/resource-tagging/reference/resource-types.mdx
index 65c23a2da688ce7..0d2bab2a3ec669c 100644
--- a/src/content/docs/resource-tagging/reference/resource-types.mdx
+++ b/src/content/docs/resource-tagging/reference/resource-types.mdx
@@ -12,51 +12,51 @@ The Tagging API supports the following resource types across account-level and z
 
 Use `/accounts/{account_id}/tags` endpoints for these resource types.
 
-| Resource type | Required extra fields | Description |
-| --- | --- | --- |
-| `account` | None | The Cloudflare account itself |
-| `access_application` | None | Access application |
-| `access_group` | None | Access group |
-| `account_ruleset` | None | Account-level ruleset |
-| `ai_gateway` | None | AI Gateway |
-| `alerting_policy` | None | Notification policy |
-| `alerting_webhook` | None | Notification webhook destination |
-| `cloudflared_tunnel` | None | Cloudflare Tunnel |
-| `d1_database` | None | D1 database |
-| `durable_object_namespace` | None | Durable Objects namespace |
-| `gateway_list` | None | Gateway list |
-| `gateway_rule` | None | Gateway rule |
-| `image` | None | Cloudflare Image |
-| `kv_namespace` | None | Workers KV namespace |
-| `load_balancer_monitor` | None | Load Balancer monitor |
-| `load_balancer_pool` | None | Load Balancer pool |
-| `pages_project` | None | Pages project |
-| `queue` | None | Queue |
-| `r2_bucket` | None | R2 bucket |
-| `resource_share` | None | Resource share |
-| `stream_live_input` | None | Stream live input |
-| `stream_video` | None | Stream video |
-| `vectorize_index` | None | Vectorize index |
-| `worker` | None | Workers script |
-| `worker_version` | `worker_id` | Specific version of a Worker |
+| Resource type              | Required extra fields | Description                      |
+| -------------------------- | --------------------- | -------------------------------- |
+| `account`                  | None                  | The Cloudflare account itself    |
+| `access_application`       | None                  | Access application               |
+| `access_group`             | None                  | Access group                     |
+| `account_ruleset`          | None                  | Account-level ruleset            |
+| `ai_gateway`               | None                  | AI Gateway                       |
+| `alerting_policy`          | None                  | Notification policy              |
+| `alerting_webhook`         | None                  | Notification webhook destination |
+| `cloudflared_tunnel`       | None                  | Cloudflare Tunnel                |
+| `d1_database`              | None                  | D1 database                      |
+| `durable_object_namespace` | None                  | Durable Objects namespace        |
+| `gateway_list`             | None                  | Gateway list                     |
+| `gateway_rule`             | None                  | Gateway rule                     |
+| `image`                    | None                  | Cloudflare Image                 |
+| `kv_namespace`             | None                  | Workers KV namespace             |
+| `load_balancer_monitor`    | None                  | Load Balancer monitor            |
+| `load_balancer_pool`       | None                  | Load Balancer pool               |
+| `pages_project`            | None                  | Pages project                    |
+| `queue`                    | None                  | Queue                            |
+| `r2_bucket`                | None                  | R2 bucket                        |
+| `resource_share`           | None                  | Resource share                   |
+| `stream_live_input`        | None                  | Stream live input                |
+| `stream_video`             | None                  | Stream video                     |
+| `vectorize_index`          | None                  | Vectorize index                  |
+| `worker`                   | None                  | Workers script                   |
+| `worker_version`           | `worker_id`           | Specific version of a Worker     |
 
 ## Zone-level resources
 
 Use `/zones/{zone_id}/tags` endpoints for these resource types.
 
-| Resource type | Required extra fields | Description |
-| --- | --- | --- |
-| `access_application_policy` | `access_application_id` | Access application policy |
-| `api_gateway_operation` | None | API Gateway operation |
-| `custom_certificate` | None | Custom SSL certificate |
-| `custom_hostname` | None | Custom hostname (SSL for SaaS) |
-| `dns_record` | None | DNS record |
-| `healthcheck` | None | Health check |
-| `load_balancer` | None | Load Balancer |
-| `managed_client_certificate` | None | Managed client certificate (mTLS) |
-| `worker_route` | None | Worker route |
-| `zone` | None | DNS zone |
-| `zone_ruleset` | None | Zone-level ruleset |
+| Resource type                | Required extra fields   | Description                       |
+| ---------------------------- | ----------------------- | --------------------------------- |
+| `access_application_policy`  | `access_application_id` | Access application policy         |
+| `api_gateway_operation`      | None                    | API Gateway operation             |
+| `custom_certificate`         | None                    | Custom SSL certificate            |
+| `custom_hostname`            | None                    | Custom hostname (SSL for SaaS)    |
+| `dns_record`                 | None                    | DNS record                        |
+| `healthcheck`                | None                    | Health check                      |
+| `load_balancer`              | None                    | Load Balancer                     |
+| `managed_client_certificate` | None                    | Managed client certificate (mTLS) |
+| `worker_route`               | None                    | Worker route                      |
+| `zone`                       | None                    | DNS zone                          |
+| `zone_ruleset`               | None                    | Zone-level ruleset                |
 
 ## Extra fields
 
diff --git a/src/content/docs/rules/normalization/settings.mdx b/src/content/docs/rules/normalization/settings.mdx
index 5caa0fb2aa550f7..7243dde493afff1 100644
--- a/src/content/docs/rules/normalization/settings.mdx
+++ b/src/content/docs/rules/normalization/settings.mdx
@@ -35,8 +35,8 @@ Default value: _Off_
 
 Configures URLs sent to the origin:
 
-  - When enabled, requests sent to the origin are normalized.
-  - When disabled, requests sent to the origin are not modified.
+- When enabled, requests sent to the origin are normalized.
+- When disabled, requests sent to the origin are not modified.
 
 You can only view and enable this option when **Normalize incoming URLs** is enabled.
 
diff --git a/src/content/docs/rules/snippets/when-to-use.mdx b/src/content/docs/rules/snippets/when-to-use.mdx
index e86e4a0e07433ec..37954e262869ef1 100644
--- a/src/content/docs/rules/snippets/when-to-use.mdx
+++ b/src/content/docs/rules/snippets/when-to-use.mdx
@@ -86,7 +86,7 @@ Snippets are ideal for fast, cost-free request and response modifications at the
 | Route traffic dynamically between [origin servers](/rules/snippets/examples/serve-different-origin/)                                                                                                          |    ✅    |   ✅    |
 | [Authenticate](/rules/snippets/examples/auth-with-headers/) requests, [pre-sign](/cache/interaction-cloudflare-products/waf-snippets/) URLs, run [A/B testing](/rules/snippets/examples/ab-testing-same-url/) |    ✅    |   ✅    |
 | Define logic using [JavaScript and Web APIs](/workers/languages/javascript/)                                                                                                                                  |    ✅    |   ✅    |
-| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                                       |    ❌    |   ✅    |
+| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                           |    ❌    |   ✅    |
 | Store persistent data (for example, [KV](/kv/), [Durable Objects](/durable-objects/), and [D1](/d1/))                                                                                                         |    ❌    |   ✅    |
 | Build [APIs](/d1/tutorials/build-a-comments-api/) and [full-stack applications](/pages/framework-guides/deploy-an-astro-site/#video-tutorial)                                                                 |    ❌    |   ✅    |
 | Use TypeScript, Python, Rust, or other programming [languages](/workers/languages/)                                                                                                                           |    ❌    |   ✅    |
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
index 7167193080e4368..d28441888bab606 100644
--- a/src/content/docs/rules/transform/managed-transforms/reference.mdx
+++ b/src/content/docs/rules/transform/managed-transforms/reference.mdx
@@ -87,7 +87,6 @@ Turning on [IP geolocation](/network/ip-geolocation/) will send a `cf-ipcountry`
 
 Cloudflare always converts non-ASCII characters to UTF-8 in HTTP request and response header values. This applies to location headers added by the **Add visitor location headers** managed transform.
 
-
 ### Add "True-Client-IP" header
 
 :::note
diff --git a/src/content/docs/ruleset-engine/about/index.mdx b/src/content/docs/ruleset-engine/about/index.mdx
index 4627da09be58e13..b2b96116594e34b 100644
--- a/src/content/docs/ruleset-engine/about/index.mdx
+++ b/src/content/docs/ruleset-engine/about/index.mdx
@@ -9,18 +9,17 @@ sidebar:
 head:
   - tag: title
     content: About Ruleset Engine
-
 ---
 
 The Cloudflare Ruleset Engine allows you to create and deploy rules and rulesets. The engine syntax, inspired by the Wireshark Display Filter language, is defined by the [Rules language](/ruleset-engine/rules-language/). Cloudflare uses the Ruleset Engine in different products, allowing you to configure several products using the same basic syntax.
 
 There are several elements involved in the configuration and use of the Ruleset Engine. These elements are:
 
-* [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
-* [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
-* [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
+- [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
+- [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
+- [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
 
-***
+---
 
 ## Get started
 
diff --git a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
index 195f92316c007d2..4ead3afce0027eb 100644
--- a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
+++ b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
@@ -7,5 +7,4 @@ title: Adjust an L3/4 DDoS rule
 external_link: /ddos-protection/managed-rulesets/network/network-overrides/configure-api/#configure-an-override-for-the-network-layer-ddos-attack-protection-managed-ruleset
 sidebar:
   order: 7
-
 ---
diff --git a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
index 4e1b9c1603ab0bf..5e0d01303a761d5 100644
--- a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
+++ b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
@@ -34,14 +34,12 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 :::note
 
-
 The Rulesets API endpoints require a value for `{account_id}` or `{zone_id}`.
 
 To retrieve a list of accounts you have access to, use the [List Accounts](/api/resources/accounts/methods/list/) operation. Note the IDs of the accounts you want to manage.
 
 To retrieve a list of zones you have access to, use the [List Zones](/api/resources/zones/methods/list/) operation. Note the IDs of the zones you want to manage.
 
-
 :::
 
 The Cloudflare Rulesets API supports the operations outlined below. Visit the associated links for API endpoints and examples.
@@ -49,206 +47,235 @@ The Cloudflare Rulesets API supports the operations outlined below. Visit the as
 ## List and view rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Method</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">List existing rulesets</a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the list of existing rulesets at the account level or at the zone level.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">View a specific ruleset</a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the properties of the most recent version of a specific ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
-          List all versions of a ruleset
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns a list of all the versions of a ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
-          View a specific version of a ruleset
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the configuration of a specific version of a ruleset, including its rules.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
-          List rules in a managed ruleset with a specific tag
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns a list of all the rules in a managed ruleset with a specific tag.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Method</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">
+					List existing rulesets
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the list of existing rulesets at the account level or at the
+					zone level.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">
+					View a specific ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the properties of the most recent version of a specific
+					ruleset.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
+					List all versions of a ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>Returns a list of all the versions of a ruleset.</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
+					View a specific version of a ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the configuration of a specific version of a ruleset,
+					including its rules.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
+					List rules in a managed ruleset with a specific tag
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns a list of all the rules in a managed ruleset with a specific
+					tag.
+				</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Create rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
-      </td>
-      <td>
-        <code>POST</code>
-      </td>
-      <td>
-        <p>Creates a new ruleset or a new phase entry point.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
+			</td>
+			<td>
+				<code>POST</code>
+			</td>
+			<td>
+				<p>Creates a new ruleset or a new phase entry point.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Update and deploy rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/update/">Update or deploy a ruleset</a>
-      </td>
-      <td>
-        <code>PUT</code>
-      </td>
-      <td>
-        <p>
-          Updates the basic properties of a ruleset and the list of rules in the ruleset.
-          <br />
-          Allows you to configure the execution of managed rulesets.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/add-rule/">Add a rule to a ruleset</a>
-      </td>
-      <td>
-        <code>POST</code>
-      </td>
-      <td>
-        <p>
-          Adds a single rule to an existing ruleset.
-          <br />
-          Allows you to add a single rule without having to include all the existing ruleset rules
-          in the request.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/update-rule/">Update a rule in a ruleset</a>
-      </td>
-      <td>
-        <code>PATCH</code>
-      </td>
-      <td>
-        <p>
-          Updates the definition of a single rule within a ruleset.
-          <br />
-          Allows you to change the order of a rule in a ruleset.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete-rule/">Delete a rule in a ruleset</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes a single rule in a ruleset.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/update/">
+					Update or deploy a ruleset
+				</a>
+			</td>
+			<td>
+				<code>PUT</code>
+			</td>
+			<td>
+				<p>
+					Updates the basic properties of a ruleset and the list of rules in the
+					ruleset.
+					<br />
+					Allows you to configure the execution of managed rulesets.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/add-rule/">
+					Add a rule to a ruleset
+				</a>
+			</td>
+			<td>
+				<code>POST</code>
+			</td>
+			<td>
+				<p>
+					Adds a single rule to an existing ruleset.
+					<br />
+					Allows you to add a single rule without having to include all the
+					existing ruleset rules in the request.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/update-rule/">
+					Update a rule in a ruleset
+				</a>
+			</td>
+			<td>
+				<code>PATCH</code>
+			</td>
+			<td>
+				<p>
+					Updates the definition of a single rule within a ruleset.
+					<br />
+					Allows you to change the order of a rule in a ruleset.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete-rule/">
+					Delete a rule in a ruleset
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes a single rule in a ruleset.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Delete rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">Delete a ruleset</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes all the versions of a ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">Delete a ruleset version</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes a specific version of a ruleset.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">
+					Delete a ruleset
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes all the versions of a ruleset.</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">
+					Delete a ruleset version
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes a specific version of a ruleset.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/docs/sandbox/bridge/http-api.mdx b/src/content/docs/sandbox/bridge/http-api.mdx
index 8454191fa57021e..ba425ec0d9cf393 100644
--- a/src/content/docs/sandbox/bridge/http-api.mdx
+++ b/src/content/docs/sandbox/bridge/http-api.mdx
@@ -28,10 +28,10 @@ When `SANDBOX_API_KEY` is not configured, authentication is skipped for local de
 
 The bridge serves its own API documentation:
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
-| `GET` | `/v1/openapi` | Interactive HTML documentation. |
+| Method | Route              | Description                          |
+| ------ | ------------------ | ------------------------------------ |
+| `GET`  | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
+| `GET`  | `/v1/openapi`      | Interactive HTML documentation.      |
 
 Both routes accept authentication via Bearer header or `?token=` query parameter.
 
@@ -39,25 +39,25 @@ When running locally with `npm run dev`, open `http://localhost:8787/v1/openapi`
 
 ## Sandbox lifecycle
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox` | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id` | Destroy the sandbox container. Returns `204`. |
-| `GET` | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
+| Method   | Route                     | Description                                                   |
+| -------- | ------------------------- | ------------------------------------------------------------- |
+| `POST`   | `/v1/sandbox`             | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`.       |
+| `DELETE` | `/v1/sandbox/:id`         | Destroy the sandbox container. Returns `204`.                 |
+| `GET`    | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
 
 ## Command execution
 
-| Method | Route | Description |
-|---|---|---|
+| Method | Route                  | Description                                           |
+| ------ | ---------------------- | ----------------------------------------------------- |
 | `POST` | `/v1/sandbox/:id/exec` | Run a command. Response is an SSE stream (see below). |
 
 The `/exec` endpoint accepts a JSON body:
 
 ```json
 {
-  "argv": ["sh", "-lc", "echo hello"],
-  "timeout_ms": 10000,
-  "cwd": "/workspace"
+	"argv": ["sh", "-lc", "echo hello"],
+	"timeout_ms": 10000,
+	"cwd": "/workspace"
 }
 ```
 
@@ -69,27 +69,27 @@ Each element of the `argv` array is escaped using ANSI-C `$'...'` quoting before
 
 The response is a `text/event-stream` with the following event types:
 
-| Event | Data | Description |
-|---|---|---|
-| `stdout` | Base64-encoded chunk | Standard output from the command. |
-| `stderr` | Base64-encoded chunk | Standard error from the command. |
-| `exit` | `{"exit_code": N}` | Command completed. Terminal event. |
-| `error` | `{"error": "…", "code": "…"}` | Command failed. Terminal event. |
+| Event    | Data                          | Description                        |
+| -------- | ----------------------------- | ---------------------------------- |
+| `stdout` | Base64-encoded chunk          | Standard output from the command.  |
+| `stderr` | Base64-encoded chunk          | Standard error from the command.   |
+| `exit`   | `{"exit_code": N}`            | Command completed. Terminal event. |
+| `error`  | `{"error": "…", "code": "…"}` | Command failed. Terminal event.    |
 
 ## File operations
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`). |
-| `PUT` | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
+| Method | Route                    | Description                                                                  |
+| ------ | ------------------------ | ---------------------------------------------------------------------------- |
+| `GET`  | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`).                 |
+| `PUT`  | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
 
 The file path is encoded in the URL after `/file/`. All paths must resolve within `/workspace`. Path traversal attempts (for example, `../../etc/passwd`) are rejected.
 
 ## Workspace persistence
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes. |
+| Method | Route                     | Description                                                        |
+| ------ | ------------------------- | ------------------------------------------------------------------ |
+| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes.    |
 | `POST` | `/v1/sandbox/:id/hydrate` | Populate `/workspace` from a tar archive sent as the request body. |
 
 The `/persist` endpoint accepts an optional `excludes` query parameter — a comma-separated list of relative paths to exclude from the archive.
@@ -98,10 +98,10 @@ The `/hydrate` endpoint accepts a raw tar payload up to 32 MiB.
 
 ## Bucket mounts
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/mount` | Mount an S3-compatible bucket as a local directory. |
-| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket. |
+| Method | Route                     | Description                                         |
+| ------ | ------------------------- | --------------------------------------------------- |
+| `POST` | `/v1/sandbox/:id/mount`   | Mount an S3-compatible bucket as a local directory. |
+| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket.                |
 
 The `/mount` endpoint accepts a JSON body. Two flows are supported:
 
@@ -111,12 +111,12 @@ Omit `endpoint` and pass the Worker R2 binding name in `bucket`:
 
 ```json
 {
-  "bucket": "MY_BUCKET",
-  "mountPath": "/mnt/data",
-  "options": {
-    "readOnly": false,
-    "prefix": "/subdir"
-  }
+	"bucket": "MY_BUCKET",
+	"mountPath": "/mnt/data",
+	"options": {
+		"readOnly": false,
+		"prefix": "/subdir"
+	}
 }
 ```
 
@@ -126,17 +126,17 @@ For an explicit S3-compatible endpoint mount, include `endpoint` and optionally
 
 ```json
 {
-  "bucket": "my-r2-bucket",
-  "mountPath": "/mnt/data",
-  "options": {
-    "endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
-    "readOnly": false,
-    "prefix": "/subdir",
-    "credentials": {
-      "accessKeyId": "...",
-      "secretAccessKey": "..."
-    }
-  }
+	"bucket": "my-r2-bucket",
+	"mountPath": "/mnt/data",
+	"options": {
+		"endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
+		"readOnly": false,
+		"prefix": "/subdir",
+		"credentials": {
+			"accessKeyId": "...",
+			"secretAccessKey": "..."
+		}
+	}
 }
 ```
 
@@ -144,10 +144,10 @@ When `endpoint` is provided, `bucket` means the remote bucket name. Credentials
 
 ## Sessions
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/session` | Create a session. Returns `{"id": "<session-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`. |
+| Method   | Route                          | Description                                         |
+| -------- | ------------------------------ | --------------------------------------------------- |
+| `POST`   | `/v1/sandbox/:id/session`      | Create a session. Returns `{"id": "<session-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`.                    |
 
 Sessions isolate working directory, environment variables, and command execution state within a sandbox. Pass the `Session-Id` header on `/exec`, `/file/*`, and `/pty` requests to scope them to a session.
 
@@ -155,35 +155,35 @@ When no `Session-Id` header is provided, requests use the sandbox default sessio
 
 ## Terminal (PTY)
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
+| Method | Route                 | Description                         |
+| ------ | --------------------- | ----------------------------------- |
+| `GET`  | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
 
 Query parameters:
 
-| Parameter | Type | Default | Description |
-|---|---|---|---|
-| `cols` | number | `80` | Terminal width in columns. |
-| `rows` | number | `24` | Terminal height in rows. |
-| `shell` | string | — | Shell binary (for example, `/bin/bash`). |
-| `session` | string | — | Session ID for session-scoped PTY. |
+| Parameter | Type   | Default | Description                              |
+| --------- | ------ | ------- | ---------------------------------------- |
+| `cols`    | number | `80`    | Terminal width in columns.               |
+| `rows`    | number | `24`    | Terminal height in rows.                 |
+| `shell`   | string | —       | Shell binary (for example, `/bin/bash`). |
+| `session` | string | —       | Session ID for session-scoped PTY.       |
 
 The WebSocket carries binary frames for terminal I/O and JSON text frames for control messages:
 
-| Direction | Frame type | Content |
-|---|---|---|
-| Client to server | Binary | UTF-8 encoded keystrokes. |
-| Server to client | Binary | Terminal output including ANSI escape sequences. |
+| Direction        | Frame type  | Content                                                                        |
+| ---------------- | ----------- | ------------------------------------------------------------------------------ |
+| Client to server | Binary      | UTF-8 encoded keystrokes.                                                      |
+| Server to client | Binary      | Terminal output including ANSI escape sequences.                               |
 | Client to server | Text (JSON) | Control messages (for example, `{"type": "resize", "cols": 120, "rows": 30}`). |
-| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`). |
+| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`).                                    |
 
 ## Warm pool
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/pool/stats` | Current pool statistics. |
-| `POST` | `/v1/pool/prime` | Start the warm pool alarm loop. |
-| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers. |
+| Method | Route                         | Description                     |
+| ------ | ----------------------------- | ------------------------------- |
+| `GET`  | `/v1/pool/stats`              | Current pool statistics.        |
+| `POST` | `/v1/pool/prime`              | Start the warm pool alarm loop. |
+| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers.  |
 
 The warm pool pre-starts sandbox containers so new sessions boot instantly. Configure it with environment variables in `wrangler.jsonc`:
 
@@ -201,9 +201,9 @@ A cron trigger (`* * * * *`) primes the pool automatically after deployment. Set
 
 ## Health check
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
+| Method | Route     | Description                                             |
+| ------ | --------- | ------------------------------------------------------- |
+| `GET`  | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
 
 ## Related resources
 
diff --git a/src/content/docs/sandbox/concepts/containers.mdx b/src/content/docs/sandbox/concepts/containers.mdx
index dd9a725669a262e..e1a711233feb34b 100644
--- a/src/content/docs/sandbox/concepts/containers.mdx
+++ b/src/content/docs/sandbox/concepts/containers.mdx
@@ -30,16 +30,18 @@ apt-get update && apt-get install -y redis-server
 The container provides a standard Linux filesystem. You can read and write anywhere you have permissions.
 
 **Standard directories**:
+
 - `/workspace` - Default working directory for user code
 - `/tmp` - Temporary files
 - `/home` - User home directory
 - `/usr/bin`, `/usr/local/bin` - Executable binaries
 
 **Example**:
+
 ```typescript
-await sandbox.writeFile('/workspace/app.py', 'print("Hello")');
-await sandbox.writeFile('/tmp/cache.json', '{}');
-await sandbox.exec('ls -la /workspace');
+await sandbox.writeFile("/workspace/app.py", 'print("Hello")');
+await sandbox.writeFile("/tmp/cache.json", "{}");
+await sandbox.exec("ls -la /workspace");
 ```
 
 ## Process management
@@ -47,20 +49,23 @@ await sandbox.exec('ls -la /workspace');
 Processes run as you'd expect in a regular Linux environment.
 
 **Foreground processes** (`exec()`):
+
 ```typescript
-const result = await sandbox.exec('npm test');
+const result = await sandbox.exec("npm test");
 // Waits for completion, returns output
 ```
 
 **Background processes** (`startProcess()`):
+
 ```typescript
-const process = await sandbox.startProcess('node server.js');
+const process = await sandbox.startProcess("node server.js");
 // Returns immediately, process runs in background
 ```
 
 ## Network capabilities
 
 **Outbound connections** work:
+
 ```bash
 curl https://api.example.com/data
 pip install requests
@@ -68,9 +73,10 @@ npm install express
 ```
 
 **Inbound connections** require port exposure:
+
 ```typescript
 const { hostname } = new URL(request.url);
-await sandbox.startProcess('python -m http.server 8000');
+await sandbox.startProcess("python -m http.server 8000");
 const exposed = await sandbox.exposePort(8000, { hostname });
 console.log(exposed.url); // Public URL
 ```
@@ -80,6 +86,7 @@ When using `wrangler dev`, you must add `EXPOSE` directives to your Dockerfile f
 :::
 
 **Localhost** works within sandbox:
+
 ```bash
 redis-server &      # Start server
 redis-cli ping      # Connect locally
@@ -88,15 +95,18 @@ redis-cli ping      # Connect locally
 ## Security
 
 **Between sandboxes** (isolated):
+
 - Each sandbox is a separate container
 - Filesystem, memory and network are all isolated
 
 **Within sandbox** (shared):
+
 - All processes see the same files
 - Processes can communicate with each other
 - Environment variables are session-scoped
 
 To run untrusted code, use separate sandboxes per user:
+
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
@@ -104,6 +114,7 @@ const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ## Limitations
 
 **Cannot**:
+
 - Load kernel modules or access host hardware
 
 ## Related resources
diff --git a/src/content/docs/sandbox/concepts/preview-urls.mdx b/src/content/docs/sandbox/concepts/preview-urls.mdx
index 7fdf50c71ce90b4..43eecbf9c151321 100644
--- a/src/content/docs/sandbox/concepts/preview-urls.mdx
+++ b/src/content/docs/sandbox/concepts/preview-urls.mdx
@@ -24,9 +24,9 @@ const req = await fetch(`${tunnel.url}/api/users`); // => GET http://localhost:8
 
 Cloudflare Tunnel support currently has the following limitations:
 
- - No control over generated URL.
- - No authentication mechanism beyond randomly generated URL.
- - Each URL uses an additional `cloudflared` process on the sandbox.
+- No control over generated URL.
+- No authentication mechanism beyond randomly generated URL.
+- Each URL uses an additional `cloudflared` process on the sandbox.
 
 :::note[Production requires custom domain]
 We are working on production deployments, custom hostnames and authentication for Cloudflare Tunnel support. In the mean time we recommend using `exposePort()` and `proxyToSandbox()` documented below under [Production usage, stable URLs and custom domains](#).
diff --git a/src/content/docs/sandbox/concepts/sandboxes.mdx b/src/content/docs/sandbox/concepts/sandboxes.mdx
index e0828106d246dbd..cd86f4ac0b8f21d 100644
--- a/src/content/docs/sandbox/concepts/sandboxes.mdx
+++ b/src/content/docs/sandbox/concepts/sandboxes.mdx
@@ -126,8 +126,8 @@ try {
 Containers with [`keepAlive: true`](/sandbox/configuration/sandbox-options/#keepalive) require explicit management since they do not timeout automatically:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, 'persistent-task', {
-  keepAlive: true
+const sandbox = getSandbox(env.Sandbox, "persistent-task", {
+	keepAlive: true,
 });
 
 // Later, when done with long-running work
diff --git a/src/content/docs/sandbox/concepts/security.mdx b/src/content/docs/sandbox/concepts/security.mdx
index 5c15d8d4295ba00..9954cb9833e9732 100644
--- a/src/content/docs/sandbox/concepts/security.mdx
+++ b/src/content/docs/sandbox/concepts/security.mdx
@@ -36,7 +36,7 @@ For complete isolation, use separate sandboxes per user:
 const userSandbox = getSandbox(env.Sandbox, `user-${userId}`);
 
 // Bad - Users sharing one sandbox
-const shared = getSandbox(env.Sandbox, 'shared');
+const shared = getSandbox(env.Sandbox, "shared");
 // Users can read each other's files!
 ```
 
@@ -53,12 +53,12 @@ await sandbox.exec(`cat ${filename}`);
 // User could input: "file.txt; rm -rf /"
 
 // Safe - validate input
-const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, '');
+const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, "");
 await sandbox.exec(`cat ${filename}`);
 
 // Better - use file API
-await sandbox.writeFile('/tmp/input', userInput);
-await sandbox.exec('cat /tmp/input');
+await sandbox.writeFile("/tmp/input", userInput);
+await sandbox.exec("cat /tmp/input");
 ```
 
 ## Authentication
@@ -69,16 +69,16 @@ Sandbox IDs provide basic access control but aren't cryptographically secure. Ad
 
 ```typescript
 export default {
-  async fetch(request: Request, env: Env): Promise<Response> {
-    const userId = await authenticate(request);
-    if (!userId) {
-      return new Response('Unauthorized', { status: 401 });
-    }
-
-    // User can only access their sandbox
-    const sandbox = getSandbox(env.Sandbox, userId);
-    return Response.json({ authorized: true });
-  }
+	async fetch(request: Request, env: Env): Promise<Response> {
+		const userId = await authenticate(request);
+		if (!userId) {
+			return new Response("Unauthorized", { status: 401 });
+		}
+
+		// User can only access their sandbox
+		const sandbox = getSandbox(env.Sandbox, userId);
+		return Response.json({ authorized: true });
+	},
 };
 ```
 
@@ -125,15 +125,18 @@ Use environment variables, not hardcoded secrets:
 
 ```typescript
 // Bad - hardcoded in file
-await sandbox.writeFile('/workspace/config.js', `
+await sandbox.writeFile(
+	"/workspace/config.js",
+	`
   const API_KEY = 'sk_live_abc123';
-`);
+`,
+);
 
 // Good - use environment variables
-await sandbox.startProcess('node app.js', {
-  env: {
-    API_KEY: env.API_KEY,  // From Worker environment binding
-  }
+await sandbox.startProcess("node app.js", {
+	env: {
+		API_KEY: env.API_KEY, // From Worker environment binding
+	},
 });
 ```
 
@@ -141,10 +144,10 @@ Clean up temporary sensitive data:
 
 ```typescript
 try {
-  await sandbox.writeFile('/tmp/sensitive.txt', secretData);
-  await sandbox.exec('python process.py /tmp/sensitive.txt');
+	await sandbox.writeFile("/tmp/sensitive.txt", secretData);
+	await sandbox.exec("python process.py /tmp/sensitive.txt");
 } finally {
-  await sandbox.deleteFile('/tmp/sensitive.txt');
+	await sandbox.deleteFile("/tmp/sensitive.txt");
 }
 ```
 
@@ -178,30 +181,34 @@ This pattern is useful when accessing GitHub for private repository operations,
 ## Best practices
 
 **Use separate sandboxes for isolation**:
+
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
 
 **Validate all inputs**:
+
 ```typescript
-const safe = input.replace(/[^a-zA-Z0-9._-]/g, '');
+const safe = input.replace(/[^a-zA-Z0-9._-]/g, "");
 await sandbox.exec(`command ${safe}`);
 ```
 
 **Use environment variables for secrets**:
+
 ```typescript
-await sandbox.startProcess('node app.js', {
-  env: { API_KEY: env.API_KEY }
+await sandbox.startProcess("node app.js", {
+	env: { API_KEY: env.API_KEY },
 });
 ```
 
 **Clean up temporary resources**:
+
 ```typescript
 try {
-  const sandbox = getSandbox(env.Sandbox, sessionId);
-  await sandbox.exec('npm test');
+	const sandbox = getSandbox(env.Sandbox, sessionId);
+	await sandbox.exec("npm test");
 } finally {
-  await sandbox.destroy();
+	await sandbox.destroy();
 }
 ```
 
diff --git a/src/content/docs/sandbox/concepts/sessions.mdx b/src/content/docs/sandbox/concepts/sessions.mdx
index 1697cf6e8795d7f..dd054b3036ce8f7 100644
--- a/src/content/docs/sandbox/concepts/sessions.mdx
+++ b/src/content/docs/sandbox/concepts/sessions.mdx
@@ -18,14 +18,14 @@ Sessions are bash shell execution contexts within a sandbox. Think of them like
 Every sandbox has a default session that maintains shell state between commands while the container is active:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
+const sandbox = getSandbox(env.Sandbox, "my-sandbox");
 
 // These commands run in the default session
 await sandbox.exec("cd /app");
-await sandbox.exec("pwd");  // Output: /app
+await sandbox.exec("pwd"); // Output: /app
 
 await sandbox.exec("export MY_VAR=hello");
-await sandbox.exec("echo $MY_VAR");  // Output: hello
+await sandbox.exec("echo $MY_VAR"); // Output: hello
 ```
 
 Working directory, environment variables, and exported variables carry over between commands. This state resets if the container restarts due to inactivity.
@@ -36,7 +36,7 @@ The container automatically creates sessions on first use. If you reference a no
 
 ```typescript
 // This session doesn't exist yet
-const result = await sandbox.exec('echo hello', { sessionId: 'new-session' });
+const result = await sandbox.exec("echo hello", { sessionId: "new-session" });
 // Container automatically creates 'new-session' with defaults:
 // - cwd: '/workspace'
 // - env: {} (empty)
@@ -47,15 +47,15 @@ This behavior is particularly relevant after deleting a session:
 ```typescript
 // Create and configure a session
 const session = await sandbox.createSession({
-  id: 'temp',
-  env: { MY_VAR: 'value' }
+	id: "temp",
+	env: { MY_VAR: "value" },
 });
 
 // Delete the session
-await sandbox.deleteSession('temp');
+await sandbox.deleteSession("temp");
 
 // Using the same session ID again works - auto-created with defaults
-const result = await sandbox.exec('echo $MY_VAR', { sessionId: 'temp' });
+const result = await sandbox.exec("echo $MY_VAR", { sessionId: "temp" });
 // Output: (empty) - MY_VAR is not set in the freshly created session
 ```
 
@@ -67,15 +67,15 @@ Create additional sessions for isolated shell contexts:
 
 ```typescript
 const buildSession = await sandbox.createSession({
-  id: "build",
-  env: { NODE_ENV: "production" },
-  cwd: "/build"
+	id: "build",
+	env: { NODE_ENV: "production" },
+	cwd: "/build",
 });
 
 const testSession = await sandbox.createSession({
-  id: "test",
-  env: { NODE_ENV: "test" },
-  cwd: "/test"
+	id: "test",
+	env: { NODE_ENV: "test" },
+	cwd: "/test",
 });
 
 // Different shell contexts
@@ -87,8 +87,8 @@ You can also set a default command timeout for all commands in a session:
 
 ```typescript
 const session = await sandbox.createSession({
-  id: "ci",
-  commandTimeoutMs: 30000 // 30s timeout for all commands
+	id: "ci",
+	commandTimeoutMs: 30000, // 30s timeout for all commands
 });
 
 await session.exec("npm test"); // Times out after 30s if still running
@@ -101,24 +101,27 @@ Individual commands can override the session timeout with the `timeout` option o
 Each session has its own:
 
 **Shell environment**:
+
 ```typescript
 await session1.exec("export MY_VAR=hello");
-await session2.exec("echo $MY_VAR");  // Empty - different shell
+await session2.exec("echo $MY_VAR"); // Empty - different shell
 ```
 
 **Working directory**:
+
 ```typescript
 await session1.exec("cd /workspace/project1");
-await session2.exec("pwd");  // Different working directory
+await session2.exec("pwd"); // Different working directory
 ```
 
 **Environment variables** (set via `createSession` options):
+
 ```typescript
 const session1 = await sandbox.createSession({
-  env: { API_KEY: 'key-1' }
+	env: { API_KEY: "key-1" },
 });
 const session2 = await sandbox.createSession({
-  env: { API_KEY: 'key-2' }
+	env: { API_KEY: "key-2" },
 });
 ```
 
@@ -127,42 +130,47 @@ const session2 = await sandbox.createSession({
 All sessions in a sandbox share:
 
 **Filesystem**:
+
 ```typescript
-await session1.writeFile('/workspace/file.txt', 'data');
-await session2.readFile('/workspace/file.txt');  // Can read it
+await session1.writeFile("/workspace/file.txt", "data");
+await session2.readFile("/workspace/file.txt"); // Can read it
 ```
 
 **Processes**:
+
 ```typescript
-await session1.startProcess('node server.js');
-await session2.listProcesses();  // Sees the server
+await session1.startProcess("node server.js");
+await session2.listProcesses(); // Sees the server
 ```
 
 ## When to use sessions
 
 **Use sessions when**:
+
 - You need isolated shell state for different tasks
 - Running parallel operations with different environments
 - Keeping AI agent credentials separate from app runtime
 
 **Example - separate dev and runtime environments**:
+
 ```typescript
 // Phase 1: AI agent writes code (with API keys)
 const devSession = await sandbox.createSession({
-  id: "dev",
-  env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY }
+	id: "dev",
+	env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY },
 });
 await devSession.exec('ai-tool "build a web server"');
 
 // Phase 2: Run the code (without API keys)
 const appSession = await sandbox.createSession({
-  id: "app",
-  env: { PORT: "3000" }
+	id: "app",
+	env: { PORT: "3000" },
 });
 await appSession.exec("node server.js");
 ```
 
 **Use separate sandboxes when**:
+
 - You need complete isolation (untrusted code)
 - Different users require fully separated environments
 - Independent resource allocation is needed
@@ -172,28 +180,31 @@ await appSession.exec("node server.js");
 ### Session cleanup
 
 **Clean up temporary sessions** to free resources while keeping the sandbox running:
+
 ```typescript
 try {
-  const session = await sandbox.createSession({ id: 'temp' });
-  await session.exec('command');
+	const session = await sandbox.createSession({ id: "temp" });
+	await session.exec("command");
 } finally {
-  await sandbox.deleteSession('temp');
+	await sandbox.deleteSession("temp");
 }
 ```
 
 **Default session cannot be deleted**:
+
 ```typescript
 // This throws an error
-await sandbox.deleteSession('default');
+await sandbox.deleteSession("default");
 // Error: Cannot delete default session. Use sandbox.destroy() instead.
 ```
 
 ### Filesystem isolation
 
 **Sessions share filesystem** - file operations affect all sessions:
+
 ```typescript
 // Bad - affects all sessions
-await session.exec('rm -rf /workspace/*');
+await session.exec("rm -rf /workspace/*");
 
 // For untrusted code isolation, use separate sandboxes
 const userSandbox = getSandbox(env.Sandbox, userId);
diff --git a/src/content/docs/sandbox/configuration/environment-variables.mdx b/src/content/docs/sandbox/configuration/environment-variables.mdx
index 522821f21e1c931..2bd802277756cba 100644
--- a/src/content/docs/sandbox/configuration/environment-variables.mdx
+++ b/src/content/docs/sandbox/configuration/environment-variables.mdx
@@ -18,10 +18,10 @@ These environment variables configure how the Sandbox SDK behaves. Set these as
 
 ### SANDBOX_TRANSPORT
 
-| | |
-|---|---|
-| **Type** | `"http"` \| `"websocket"` |
-| **Default** | `"http"` |
+|             |                           |
+| ----------- | ------------------------- |
+| **Type**    | `"http"` \| `"websocket"` |
+| **Default** | `"http"`                  |
 
 Controls the transport protocol for SDK-to-container communication. WebSocket transport multiplexes all operations over a single persistent connection, avoiding [subrequest limits](/workers/platform/limits/#subrequests) when performing many SDK operations per request.
 
@@ -39,10 +39,10 @@ See [Transport modes](/sandbox/configuration/transport/) for a complete guide in
 
 ### COMMAND_TIMEOUT_MS
 
-| | |
-|---|---|
-| **Type** | `number` (milliseconds) |
-| **Default** | None (no timeout) |
+|             |                         |
+| ----------- | ----------------------- |
+| **Type**    | `number` (milliseconds) |
+| **Default** | None (no timeout)       |
 
 Sets a global default timeout for every `exec()` call. When set, any command that exceeds this duration raises an error on the caller side and closes the connection.
 
@@ -95,9 +95,9 @@ await sandbox.setEnvVars({
 
 ```typescript
 await sandbox.setEnvVars({
-	API_KEY: 'new-key',     // Sets API_KEY
-	OLD_SECRET: undefined,  // Unsets OLD_SECRET
-	DEBUG_MODE: null        // Unsets DEBUG_MODE
+	API_KEY: "new-key", // Sets API_KEY
+	OLD_SECRET: undefined, // Unsets OLD_SECRET
+	DEBUG_MODE: null, // Unsets DEBUG_MODE
 });
 ```
 
@@ -153,12 +153,12 @@ The Sandbox SDK supports unsetting environment variables by passing `undefined`
 ```typescript
 await sandbox.setEnvVars({
 	// Set new values
-	API_KEY: 'new-key',
+	API_KEY: "new-key",
 	DATABASE_URL: env.DATABASE_URL,
 
 	// Unset variables (removes them from the environment)
 	OLD_API_KEY: undefined,
-	TEMP_TOKEN: null
+	TEMP_TOKEN: null,
 });
 ```
 
@@ -172,7 +172,7 @@ await sandbox.setEnvVars({
 
 ```typescript
 // Use a temporary token
-await sandbox.setEnvVars({ TEMP_TOKEN: 'abc123' });
+await sandbox.setEnvVars({ TEMP_TOKEN: "abc123" });
 await sandbox.exec('curl -H "Authorization: $TEMP_TOKEN" api.example.com');
 
 // Clean up the token
@@ -184,8 +184,8 @@ await sandbox.setEnvVars({ TEMP_TOKEN: undefined });
 ```typescript
 await sandbox.setEnvVars({
 	API_KEY: env.API_KEY,
-	DEBUG_MODE: env.NODE_ENV === 'development' ? 'true' : undefined,
-	PROFILING: env.ENABLE_PROFILING ? 'true' : undefined
+	DEBUG_MODE: env.NODE_ENV === "development" ? "true" : undefined,
+	PROFILING: env.ENABLE_PROFILING ? "true" : undefined,
 });
 ```
 
diff --git a/src/content/docs/sandbox/configuration/transport.mdx b/src/content/docs/sandbox/configuration/transport.mdx
index dce27bacce1ff87..18e5f33fc1b515d 100644
--- a/src/content/docs/sandbox/configuration/transport.mdx
+++ b/src/content/docs/sandbox/configuration/transport.mdx
@@ -22,7 +22,6 @@ The Sandbox SDK supports three transport modes for communication between the Dur
 - **NEW: RPC transport** - All SDK operations are multiplexed over a single persistent WebSocket connection. Will replace HTTP as the default transport in future. Available since 0.9.1.
 - **Deprecated: WebSocket transport** - All SDK operations are multiplexed over a single persistent WebSocket. Superseded by RPC transport which uses an improved protocol.
 
-
 ## When to use RPC transport
 
 Use the RPC transport when your Worker or Durable Object makes many SDK operations per request. This avoids hitting [subrequest limits](/workers/platform/limits/#subrequests).
@@ -112,11 +111,13 @@ No application code changes are needed. The SDK automatically uses the configure
 ### Connection lifecycle
 
 **HTTP transport:**
+
 - Creates a new HTTP request for each SDK operation
 - No persistent connection
 - Each request is independent and stateless
 
 **RPC transport:**
+
 - Establishes a WebSocket connection on the first SDK operation
 - Maintains the persistent connection for all subsequent operations
 - Connection is closed when the sandbox sleeps or is evicted
@@ -136,6 +137,7 @@ Your code remains identical regardless of transport mode.
 All transports provide identical error handling behavior. The SDK automatically retries on transient errors (like 503 responses) with exponential backoff.
 
 WebSocket-specific behavior:
+
 - Connection failures trigger automatic reconnection
 - The SDK transparently handles WebSocket disconnections
 - In-flight operations are not lost during reconnection
@@ -154,7 +156,6 @@ Switching between transports requires no code changes.
 Using the `rpc` transport requires version 0.9.1 or newer. If you are using an older version of the Sandbox SDK upgrade and deploy your application with the newer `@cloudflare/sandbox` and image first. Otherwise there will be issues with newer SDK clients attempting to connect to older sandboxes that do not support the new transport.
 :::
 
-
 Add `SANDBOX_TRANSPORT` to your `wrangler.jsonc`:
 
 <WranglerConfig>
diff --git a/src/content/docs/sandbox/guides/production-deployment.mdx b/src/content/docs/sandbox/guides/production-deployment.mdx
index 27c08a0c143f74a..c0f0ed75abf6508 100644
--- a/src/content/docs/sandbox/guides/production-deployment.mdx
+++ b/src/content/docs/sandbox/guides/production-deployment.mdx
@@ -24,10 +24,11 @@ The `.workers.dev` domain does not support wildcard subdomains, so production de
 If your worker runs on a subdomain (for example, `sandbox.yourdomain.com`), preview URLs become second-level wildcards like `*.sandbox.yourdomain.com`. Cloudflare's Universal SSL only covers first-level wildcards (`*.yourdomain.com`), so you need a certificate covering `*.sandbox.yourdomain.com`. Without it, preview URLs will fail with TLS handshake errors.
 
 You have three options:
+
 - **Deploy on the apex domain** (`yourdomain.com`) so preview URLs stay at the first level (`*.yourdomain.com`), which Universal SSL covers automatically. This is the simplest option.
 - **Use [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/)** ($10/month) to provision a certificate for `*.sandbox.yourdomain.com` through the Cloudflare dashboard.
 - **Upload a custom certificate** from a provider like [Let's Encrypt](https://letsencrypt.org/) (free). Generate a wildcard certificate for `*.sandbox.yourdomain.com` using the DNS-01 challenge, then upload it via the Cloudflare dashboard under **SSL/TLS > Edge Certificates > [Custom Certificates](/ssl/edge-certificates/custom-certificates/)**. You will need to renew it before expiry.
-:::
+  :::
 
 ## Prerequisites
 
@@ -42,7 +43,7 @@ You have three options:
 In the Cloudflare dashboard, go to your domain and create an A record:
 
 - **Type**: A
-- **Name**: * (wildcard)
+- **Name**: \* (wildcard)
 - **IPv4 address**: 192.0.2.0
 - **Proxy status**: Proxied (orange cloud)
 
@@ -87,8 +88,8 @@ Test that preview URLs work:
 // Extract hostname from request
 const { hostname } = new URL(request.url);
 
-const sandbox = getSandbox(env.Sandbox, 'test-sandbox');
-await sandbox.startProcess('python -m http.server 8080');
+const sandbox = getSandbox(env.Sandbox, "test-sandbox");
+await sandbox.startProcess("python -m http.server 8080");
 const exposed = await sandbox.exposePort(8080, { hostname });
 
 console.log(exposed.url);
diff --git a/src/content/docs/sandbox/platform/pricing.mdx b/src/content/docs/sandbox/platform/pricing.mdx
index cc9fe5632a5b833..cf39a5eba58829c 100644
--- a/src/content/docs/sandbox/platform/pricing.mdx
+++ b/src/content/docs/sandbox/platform/pricing.mdx
@@ -13,6 +13,7 @@ Sandbox SDK pricing is determined by the underlying [Containers](/containers/) p
 ## Containers Pricing
 
 Refer to [Containers pricing](/containers/pricing/) for complete details on:
+
 - vCPU, memory, and disk usage rates
 - Network egress pricing
 - Instance types and their costs
@@ -20,6 +21,7 @@ Refer to [Containers pricing](/containers/pricing/) for complete details on:
 ## Related Pricing
 
 When using Sandbox, you'll also be billed for:
+
 - [Workers](/workers/platform/pricing/) - Handles incoming requests to your sandbox
 - [Durable Objects](/durable-objects/platform/pricing/) - Powers each sandbox instance
 - [Workers Logs](/workers/observability/logs/workers-logs/#pricing) - Optional observability (if enabled)
diff --git a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
index 992afa80321cc03..5e0e4d91dfa660e 100644
--- a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
+++ b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
@@ -25,6 +25,7 @@ An API that accepts questions like "What's the 100th Fibonacci number?", uses Cl
 <Render file="prereqs" product="workers" />
 
 You'll also need:
+
 - An [Anthropic API key](https://console.anthropic.com/) for Claude
 - [Docker](https://www.docker.com/) running locally
 
@@ -52,11 +53,11 @@ Install the Anthropic SDK:
 
 Replace the contents of `src/index.ts`:
 
-```typescript
-import { getSandbox, type Sandbox } from '@cloudflare/sandbox';
-import Anthropic from '@anthropic-ai/sdk';
+````typescript
+import { getSandbox, type Sandbox } from "@cloudflare/sandbox";
+import Anthropic from "@anthropic-ai/sdk";
 
-export { Sandbox } from '@cloudflare/sandbox';
+export { Sandbox } from "@cloudflare/sandbox";
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -65,7 +66,10 @@ interface Env {
 
 export default {
 	async fetch(request: Request, env: Env): Promise<Response> {
-		if (request.method !== 'POST' || new URL(request.url).pathname !== '/execute') {
+		if (
+			request.method !== "POST" ||
+			new URL(request.url).pathname !== "/execute"
+		) {
 			return new Response('POST /execute with { "question": "your question" }');
 		}
 
@@ -73,65 +77,74 @@ export default {
 			const { question } = await request.json();
 
 			if (!question) {
-				return Response.json({ error: 'Question is required' }, { status: 400 });
+				return Response.json(
+					{ error: "Question is required" },
+					{ status: 400 },
+				);
 			}
 
 			// Use Claude to generate Python code
 			const anthropic = new Anthropic({ apiKey: env.ANTHROPIC_API_KEY });
 			const codeGeneration = await anthropic.messages.create({
-				model: 'claude-sonnet-4-5',
+				model: "claude-sonnet-4-5",
 				max_tokens: 1024,
-				messages: [{
-					role: 'user',
-					content: `Generate Python code to answer: "${question}"
+				messages: [
+					{
+						role: "user",
+						content: `Generate Python code to answer: "${question}"
 
 Requirements:
 - Use only Python standard library
 - Print the result using print()
 - Keep code simple and safe
 
-Return ONLY the code, no explanations.`
-				}],
+Return ONLY the code, no explanations.`,
+					},
+				],
 			});
 
-			const generatedCode = codeGeneration.content[0]?.type === 'text'
-				? codeGeneration.content[0].text
-				: '';
+			const generatedCode =
+				codeGeneration.content[0]?.type === "text"
+					? codeGeneration.content[0].text
+					: "";
 
 			if (!generatedCode) {
-				return Response.json({ error: 'Failed to generate code' }, { status: 500 });
+				return Response.json(
+					{ error: "Failed to generate code" },
+					{ status: 500 },
+				);
 			}
 
 			// Strip markdown code fences if present
 			const cleanCode = generatedCode
-				.replace(/^```python?\n?/, '')
-				.replace(/\n?```\s*$/, '')
+				.replace(/^```python?\n?/, "")
+				.replace(/\n?```\s*$/, "")
 				.trim();
 
 			// Execute the code in a sandbox
-			const sandbox = getSandbox(env.Sandbox, 'demo-user');
-			await sandbox.writeFile('/tmp/code.py', cleanCode);
-			const result = await sandbox.exec('python /tmp/code.py');
+			const sandbox = getSandbox(env.Sandbox, "demo-user");
+			await sandbox.writeFile("/tmp/code.py", cleanCode);
+			const result = await sandbox.exec("python /tmp/code.py");
 
 			return Response.json({
 				success: result.success,
 				question,
 				code: generatedCode,
 				output: result.stdout,
-				error: result.stderr
+				error: result.stderr,
 			});
-
 		} catch (error: any) {
 			return Response.json(
-				{ error: 'Internal server error', message: error.message },
-				{ status: 500 }
+				{ error: "Internal server error", message: error.message },
+				{ status: 500 },
 			);
 		}
 	},
 };
-```
+````
 
 **How it works:**
+
 1. Receives a question via POST to `/execute`
 2. Uses Claude to generate Python code
 3. Writes code to `/tmp/code.py` in the sandbox
@@ -176,11 +189,11 @@ Response:
 
 ```json
 {
-  "success": true,
-  "question": "What is the 10th Fibonacci number?",
-  "code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
-  "output": "55\n",
-  "error": ""
+	"success": true,
+	"question": "What is the 10th Fibonacci number?",
+	"code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
+	"output": "55\n",
+	"error": ""
 }
 ```
 
@@ -228,6 +241,7 @@ curl -X POST https://ai-code-executor.YOUR_SUBDOMAIN.workers.dev/execute \
 ## What you built
 
 You created an AI code execution system that:
+
 - Accepts natural language questions
 - Generates Python code with Claude
 - Executes code securely in isolated sandboxes
diff --git a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
index 5497b602e6f0f38..13784a7bf7fb634 100644
--- a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
+++ b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
@@ -119,24 +119,27 @@ export default {
 			}
 
 			async function streamToBase64(stream) {
-			  const blob = await new Response(stream).blob();
-			  const buffer = await blob.arrayBuffer();
-			  const bytes = new Uint8Array(buffer);
-
-			  // Convert to base64
-			  let binary = '';
-			  for (let i = 0; i < bytes.length; i++) {
-			    binary += String.fromCharCode(bytes[i]);
-			  }
-			  return btoa(binary);
+				const blob = await new Response(stream).blob();
+				const buffer = await blob.arrayBuffer();
+				const bytes = new Uint8Array(buffer);
+
+				// Convert to base64
+				let binary = "";
+				for (let i = 0; i < bytes.length; i++) {
+					binary += String.fromCharCode(bytes[i]);
+				}
+				return btoa(binary);
 			}
 
 			// Check for generated chart
 			let chart = null;
 			try {
-				const { content, mimeType } = await sandbox.readFile("/workspace/chart.png", {
-					encoding: "none"
-				});
+				const { content, mimeType } = await sandbox.readFile(
+					"/workspace/chart.png",
+					{
+						encoding: "none",
+					},
+				);
 				chart = `data:${mimeType};base64,${await streamToBase64(content)}`;
 			} catch {
 				// No chart generated
diff --git a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
index 1a964dfdb7b13da..cc84853855df6ca 100644
--- a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
+++ b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
@@ -39,9 +39,15 @@ cd test-pipeline
 Replace `src/index.ts`:
 
 ```typescript
-import { getSandbox, proxyToSandbox, parseSSEStream, type Sandbox, type ExecEvent } from '@cloudflare/sandbox';
+import {
+	getSandbox,
+	proxyToSandbox,
+	parseSSEStream,
+	type Sandbox,
+	type ExecEvent,
+} from "@cloudflare/sandbox";
 
-export { Sandbox } from '@cloudflare/sandbox';
+export { Sandbox } from "@cloudflare/sandbox";
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -53,34 +59,39 @@ export default {
 		const proxyResponse = await proxyToSandbox(request, env);
 		if (proxyResponse) return proxyResponse;
 
-		if (request.method !== 'POST') {
-			return new Response('POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }');
+		if (request.method !== "POST") {
+			return new Response(
+				'POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }',
+			);
 		}
 
 		try {
 			const { repoUrl, branch } = await request.json();
 
 			if (!repoUrl) {
-				return Response.json({ error: 'repoUrl required' }, { status: 400 });
+				return Response.json({ error: "repoUrl required" }, { status: 400 });
 			}
 
 			const sandbox = getSandbox(env.Sandbox, `test-${Date.now()}`);
 
 			try {
 				// Clone repository
-				console.log('Cloning repository...');
+				console.log("Cloning repository...");
 				let cloneUrl = repoUrl;
-				
-				if (env.GITHUB_TOKEN && cloneUrl.includes('github.com')) {
-					cloneUrl = cloneUrl.replace('https://', `https://${env.GITHUB_TOKEN}@`);
+
+				if (env.GITHUB_TOKEN && cloneUrl.includes("github.com")) {
+					cloneUrl = cloneUrl.replace(
+						"https://",
+						`https://${env.GITHUB_TOKEN}@`,
+					);
 				}
 
 				await sandbox.gitCheckout(cloneUrl, {
 					...(branch && { branch }),
 					depth: 1,
-					targetDir: 'repo'
+					targetDir: "repo",
 				});
-				console.log('Repository cloned');
+				console.log("Repository cloned");
 
 				// Detect project type
 				const projectType = await detectProjectType(sandbox);
@@ -89,38 +100,42 @@ export default {
 				// Install dependencies
 				const installCmd = getInstallCommand(projectType);
 				if (installCmd) {
-					console.log('Installing dependencies...');
-					const installStream = await sandbox.execStream(`cd /workspace/repo && ${installCmd}`);
-					
+					console.log("Installing dependencies...");
+					const installStream = await sandbox.execStream(
+						`cd /workspace/repo && ${installCmd}`,
+					);
+
 					let installExitCode = 0;
 					for await (const event of parseSSEStream<ExecEvent>(installStream)) {
-						if (event.type === 'stdout' || event.type === 'stderr') {
+						if (event.type === "stdout" || event.type === "stderr") {
 							console.log(event.data);
-						} else if (event.type === 'complete') {
+						} else if (event.type === "complete") {
 							installExitCode = event.exitCode;
 						}
 					}
-					
+
 					if (installExitCode !== 0) {
 						return Response.json({
 							success: false,
-							error: 'Install failed',
-							exitCode: installExitCode
+							error: "Install failed",
+							exitCode: installExitCode,
 						});
 					}
-					console.log('Dependencies installed');
+					console.log("Dependencies installed");
 				}
 
 				// Run tests
-				console.log('Running tests...');
+				console.log("Running tests...");
 				const testCmd = getTestCommand(projectType);
-				const testStream = await sandbox.execStream(`cd /workspace/repo && ${testCmd}`);
-				
+				const testStream = await sandbox.execStream(
+					`cd /workspace/repo && ${testCmd}`,
+				);
+
 				let testExitCode = 0;
 				for await (const event of parseSSEStream<ExecEvent>(testStream)) {
-					if (event.type === 'stdout' || event.type === 'stderr') {
+					if (event.type === "stdout" || event.type === "stderr") {
 						console.log(event.data);
-					} else if (event.type === 'complete') {
+					} else if (event.type === "complete") {
 						testExitCode = event.exitCode;
 					}
 				}
@@ -130,13 +145,11 @@ export default {
 					success: testExitCode === 0,
 					exitCode: testExitCode,
 					projectType,
-					message: testExitCode === 0 ? 'All tests passed' : 'Tests failed'
+					message: testExitCode === 0 ? "All tests passed" : "Tests failed",
 				});
-
 			} finally {
 				await sandbox.destroy();
 			}
-
 		} catch (error: any) {
 			return Response.json({ error: error.message }, { status: 500 });
 		}
@@ -145,38 +158,46 @@ export default {
 
 async function detectProjectType(sandbox: any): Promise<string> {
 	try {
-		await sandbox.readFile('/workspace/repo/package.json');
-		return 'nodejs';
+		await sandbox.readFile("/workspace/repo/package.json");
+		return "nodejs";
 	} catch {}
 
 	try {
-		await sandbox.readFile('/workspace/repo/requirements.txt');
-		return 'python';
+		await sandbox.readFile("/workspace/repo/requirements.txt");
+		return "python";
 	} catch {}
 
 	try {
-		await sandbox.readFile('/workspace/repo/go.mod');
-		return 'go';
+		await sandbox.readFile("/workspace/repo/go.mod");
+		return "go";
 	} catch {}
 
-	return 'unknown';
+	return "unknown";
 }
 
 function getInstallCommand(projectType: string): string {
 	switch (projectType) {
-		case 'nodejs': return 'npm install';
-		case 'python': return 'pip install -r requirements.txt || pip install -e .';
-		case 'go': return 'go mod download';
-		default: return '';
+		case "nodejs":
+			return "npm install";
+		case "python":
+			return "pip install -r requirements.txt || pip install -e .";
+		case "go":
+			return "go mod download";
+		default:
+			return "";
 	}
 }
 
 function getTestCommand(projectType: string): string {
 	switch (projectType) {
-		case 'nodejs': return 'npm test';
-		case 'python': return 'python -m pytest || python -m unittest discover';
-		case 'go': return 'go test ./...';
-		default: return 'echo "Unknown project type"';
+		case "nodejs":
+			return "npm test";
+		case "python":
+			return "python -m pytest || python -m unittest discover";
+		case "go":
+			return "go test ./...";
+		default:
+			return 'echo "Unknown project type"';
 	}
 }
 ```
@@ -203,10 +224,10 @@ You will see progress logs in the wrangler console, and receive a JSON response:
 
 ```json
 {
-  "success": true,
-  "exitCode": 0,
-  "projectType": "nodejs",
-  "message": "All tests passed"
+	"success": true,
+	"exitCode": 0,
+	"projectType": "nodejs",
+	"message": "All tests passed"
 }
 ```
 
@@ -225,6 +246,7 @@ npx wrangler secret put GITHUB_TOKEN
 ## What you built
 
 An automated testing pipeline that:
+
 - Clones Git repositories
 - Detects project type (Node.js, Python, Go)
 - Installs dependencies automatically
diff --git a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
index 022b3803088764b..fc519d4cc81608a 100644
--- a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
+++ b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
@@ -19,7 +19,10 @@ Cloudflare provides a self-managed environment for [Claude Managed Agents](https
 
 This integration ships as an open-source deployment template. Fork the repo, deploy it to your Cloudflare account, and customize it as needed.
 
-<LinkButton variant="secondary" href="https://github.com/cloudflare/claude-managed-agents">
+<LinkButton
+	variant="secondary"
+	href="https://github.com/cloudflare/claude-managed-agents"
+>
 	Get Started
 </LinkButton>
 
@@ -66,15 +69,15 @@ You need a Workers Paid plan or Enterprise account. [Containers](/containers/) (
 
 The repository includes detailed documentation on each capability:
 
-| Topic | What it covers |
-| --- | --- |
-| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md) | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings |
-| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md) | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing |
-| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md) | Pick the best agent execution environment |
-| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md) | Give agents their own email addresses and sending abilities |
-| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md) | Observable agent browser interactions with Browser Run |
-| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md) | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
-| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md) | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend |
-| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types |
-| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md) | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses |
-| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md) | Secure access to the CMA control plane |
+| Topic                                                                                                                                    | What it covers                                                                                                                                                   |
+| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md)   | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings                                                                             |
+| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md)               | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing                               |
+| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md)           | Pick the best agent execution environment                                                                                                                        |
+| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md)                                         | Give agents their own email addresses and sending abilities                                                                                                      |
+| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md)                 | Observable agent browser interactions with Browser Run                                                                                                           |
+| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md)                         | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
+| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md)                     | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend                                                                                            |
+| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types                                                                                                                      |
+| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md)                                       | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses                               |
+| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md)                                 | Secure access to the CMA control plane                                                                                                                           |
diff --git a/src/content/docs/sandbox/tutorials/code-review-bot.mdx b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
index daeeff910905556..98052e0f745d6e9 100644
--- a/src/content/docs/sandbox/tutorials/code-review-bot.mdx
+++ b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
@@ -108,9 +108,7 @@ export default {
 			) {
 				console.log(`Starting review for PR #${payload.pull_request.number}`);
 				// Use waitUntil to ensure the review completes even after response is sent
-				ctx.waitUntil(
-					reviewPullRequest(payload, env).catch(console.error),
-				);
+				ctx.waitUntil(reviewPullRequest(payload, env).catch(console.error));
 				return Response.json({ message: "Review started" });
 			}
 
diff --git a/src/content/docs/secrets-store/audit-logs.mdx b/src/content/docs/secrets-store/audit-logs.mdx
index 144a24543be86f5..90f826135f55949 100644
--- a/src/content/docs/secrets-store/audit-logs.mdx
+++ b/src/content/docs/secrets-store/audit-logs.mdx
@@ -17,4 +17,4 @@ sidebar:
   - A boolean `"value_modified": true` is presented when the secret value is edited.
 - Delete
 
-For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
\ No newline at end of file
+For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
diff --git a/src/content/docs/secrets-store/index.mdx b/src/content/docs/secrets-store/index.mdx
index 4d1e230e37ff9e9..e2ed5d0af9f4441 100644
--- a/src/content/docs/secrets-store/index.mdx
+++ b/src/content/docs/secrets-store/index.mdx
@@ -16,7 +16,8 @@ head:
 import { Description, Plan } from "~/components";
 
 <Description>
-Encrypt and store sensitive information as secrets that are securely reusable across your account.
+	Encrypt and store sensitive information as secrets that are securely reusable
+	across your account.
 </Description>
 
 <Plan id="secrets_store.properties.availability.summary" />
diff --git a/src/content/docs/secrets-store/integrations/ai-gateway.mdx b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
index 918c8bcfa39217c..af789df84d1a0c0 100644
--- a/src/content/docs/secrets-store/integrations/ai-gateway.mdx
+++ b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
@@ -8,4 +8,4 @@ external_link: /ai-gateway/configuration/bring-your-own-keys/
 sidebar:
   order: 3
   label: AI Gateway
----
\ No newline at end of file
+---
diff --git a/src/content/docs/secrets-store/integrations/index.mdx b/src/content/docs/secrets-store/integrations/index.mdx
index 64d5175c5fd2e82..a5ce8b0cbe2a887 100644
--- a/src/content/docs/secrets-store/integrations/index.mdx
+++ b/src/content/docs/secrets-store/integrations/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/secrets-store/manage-secrets/how-to.mdx b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
index 2fd99158d2495e9..cb9d42efdc308d9 100644
--- a/src/content/docs/secrets-store/manage-secrets/how-to.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
@@ -155,4 +155,4 @@ Refer to [Secrets Store API](/api/resources/secrets_store/) for the full API doc
 	method="DELETE"
 />
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/docs/secrets-store/manage-secrets/index.mdx b/src/content/docs/secrets-store/manage-secrets/index.mdx
index 17a01164f12187d..e9a5f2e3ffdfc0c 100644
--- a/src/content/docs/secrets-store/manage-secrets/index.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/index.mdx
@@ -28,4 +28,4 @@ If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler)
 - [Create a secret](/secrets-store/manage-secrets/how-to/#create-a-secret)
 - [Duplicate a secret](/secrets-store/manage-secrets/how-to/#duplicate-a-secret)
 - [Edit a secret](/secrets-store/manage-secrets/how-to/#edit-a-secret)
-- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
\ No newline at end of file
+- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
diff --git a/src/content/docs/security-center/brand-protection.mdx b/src/content/docs/security-center/brand-protection.mdx
index 3a021e91ce70f25..064f17815b2cfeb 100644
--- a/src/content/docs/security-center/brand-protection.mdx
+++ b/src/content/docs/security-center/brand-protection.mdx
@@ -54,7 +54,7 @@ To start searching for new domains that might be trying to impersonate your bran
 
 5. To export all matches from a saved query, select your **Query name** > select the three dots > **Export matches**.
 
-In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the  **Show dismissed matches** toggle in the Cloudflare dashboard.
+In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the **Show dismissed matches** toggle in the Cloudflare dashboard.
 
 ### Logo search (AI-powered)
 
diff --git a/src/content/docs/security-center/changelog.mdx b/src/content/docs/security-center/changelog.mdx
index 1c92506953963cf..889cbe1b2ec6c7b 100644
--- a/src/content/docs/security-center/changelog.mdx
+++ b/src/content/docs/security-center/changelog.mdx
@@ -16,20 +16,20 @@ import { ProductChangelog } from "~/components";
 
 ## 2025-02-03
 
-* Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
+- Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
 
 ## 2025-01-20
 
-* On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
+- On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
 
 ## 2024-09-23
 
-* Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
+- Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
 
 ## 2024-09-19
 
-* Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
+- Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
 
 ## 2024-07-22
 
-* Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
+- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
diff --git a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
index 6749f8a8b7ee551..e90c084b944a737 100644
--- a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
+++ b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
@@ -7,5 +7,4 @@ products:
 external_link: https://www.cloudflare.com/threat-intelligence/
 sidebar:
   order: 10
-
 ---
diff --git a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
index 55fbf7081e51889..33bd1dd3898a1bd 100644
--- a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
+++ b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
@@ -10,9 +10,7 @@ sidebar:
     text: Beta
 ---
 
-import { Details } from "~/components"
-
-
+import { Details } from "~/components";
 
 Open Port Scanning allows [Magic Transit](/magic-transit/) and [Bring your Own IPs](/byoip/) users to efficiently monitor IP ranges for security vulnerabilities. This API enables users to scan their designated IP ranges, detect any open ports, and receive daily notifications regarding newly opened ports.
 
@@ -21,24 +19,24 @@ You can access this feature via the [API](/api/resources/cloudforce_one/subresou
 ## Prerequisites
 
 - Cloudforce One Administrator, Administrator and Super Administrator roles.
-- Account token: **Custom API Token** >  **Cloudforce One:Edit**. 
+- Account token: **Custom API Token** > **Cloudforce One:Edit**.
 
 To create a custom API token:
 
 1. From the [Cloudflare dashboard](https://dash.cloudflare.com/profile/api-tokens/), go to **My Profile** > **API Tokens** for user tokens. Go to **Create Custom Token** > **Get started**.
 2. Enter a **Token name**, for example, `Open Port Scanning`.
 3. In **Permissions**:
-    - Choose **Account**.
-    - Select **Cloudforce One** as the account.
-    - Choose **Edit** access.
+   - Choose **Account**.
+   - Select **Cloudforce One** as the account.
+   - Choose **Edit** access.
 4. In Client IP Address Filtering:
-    - In **Operator**, select `is in`.
-    - In **Value**, enter a valid IP address.
+   - In **Operator**, select `is in`.
+   - In **Value**, enter a valid IP address.
 5. Select **Continue to summary**.
 6. Review the token, then select **Create Token**.
 
 :::note
-The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules. 
+The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules.
 :::
 
 ## Configure Open Port Scanning
@@ -46,150 +44,56 @@ The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce O
 To configure Open Port Scanning, follow these steps:
 
 1. **Create a new scan config**:
-    - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
-    - **Frequency**: Enter the scan frequency in days.
-    - **Ports**: Select the ports to scan. Choose among:
-        - All
-        - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
-        - List of specific ports
+   - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
+   - **Frequency**: Enter the scan frequency in days.
+   - **Ports**: Select the ports to scan. Choose among:
+     - All
+     - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
+     - List of specific ports
 2. **Scan IPs**: Initiate the scanning process. The system will analyze the specified IP ranges to identify any open ports.
 3. **Generate list of open ports**: Once the scan is complete, the API will generate a list of detected open ports for review and action.
-4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude  any ports that do not require immediate attention.
+4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude any ports that do not require immediate attention.
 5. **View differences from previous scan**: The API will highlight any changes in open ports since the last scan, allowing you to quickly assess new vulnerabilities.
-6. **Stop scanning**: If necessary, you can stop  the scanning process at any time.
-7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open. 
+6. **Stop scanning**: If necessary, you can stop the scanning process at any time.
+7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open.
 
 :::note[Beta feature notice]
 Open Port Scanning feature is currently in closed beta. The Cloudforce One team appreciates your feedback as the team works to enhance its functionality and user experience.
-If you want to subscribe  to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
+If you want to subscribe to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
 :::
 
 ## Default ports
 
 <Details header="List of default ports">
-- `80`
-- `631`
-- `161`
-- `137`
-- `123`
-- `138`
-- `1434`
-- `445`
-- `135`
-- `67`
-- `23`
-- `53`
-- `443`
-- `21`
-- `139`
-- `22`
-- `500`
-- `68`
-- `520`
-- `1900`
-- `25`
-- `4500`
-- `514`
-- `49152`
-- `162`
-- `69`
-- `5353`
-- `111`
-- `49154`
-- `3389`
-- `110`
-- `1701`
-- `998`
-- `996`
-- `997`
-- `999`
-- `3283`
-- `49153`
-- `445`
-- `1812`
-- `136`
-- `139`
-- `143`
-- `53`
-- `2222`
-- `135`
-- `3306`
-- `2049`
-- `32768`
-- `5060`
-- `8080`
-- `1025`
-- `1433`
-- `3456`
-- `80`
-- `1723`
-- `111`
-- `995`
-- `993`
-- `20031`
-- `1026`
-- `7`
-- `5900`
-- `1646`
-- `1645`
-- `593`
-- `1025`
-- `518`
-- `2048`
-- `626`
-- `1027`
-- `587`
-- `177`
-- `1719`
-- `427`
-- `497`
-- `8888`
-- `4444`
-- `1023`
-- `65024`
-- `199`
-- `19`
-- `9`
-- `49193`
-- `1029`
-- `1720`
-- `49`
-- `465`
-- `88`
-- `1028`
-- `17185`
-- `1718`
-- `49186`
-- `548`
-- `113`
-- `81`
-- `6001`
-- `2000`
-- `10000`
-- `31337`
+	- `80` - `631` - `161` - `137` - `123` - `138` - `1434` - `445` - `135` - `67`
+	- `23` - `53` - `443` - `21` - `139` - `22` - `500` - `68` - `520` - `1900` -
+	`25` - `4500` - `514` - `49152` - `162` - `69` - `5353` - `111` - `49154` -
+	`3389` - `110` - `1701` - `998` - `996` - `997` - `999` - `3283` - `49153` -
+	`445` - `1812` - `136` - `139` - `143` - `53` - `2222` - `135` - `3306` -
+	`2049` - `32768` - `5060` - `8080` - `1025` - `1433` - `3456` - `80` - `1723`
+	- `111` - `995` - `993` - `20031` - `1026` - `7` - `5900` - `1646` - `1645` -
+	`593` - `1025` - `518` - `2048` - `626` - `1027` - `587` - `177` - `1719` -
+	`427` - `497` - `8888` - `4444` - `1023` - `65024` - `199` - `19` - `9` -
+	`49193` - `1029` - `1720` - `49` - `465` - `88` - `1028` - `17185` - `1718` -
+	`49186` - `548` - `113` - `81` - `6001` - `2000` - `10000` - `31337`
 </Details>
 
 ## Frequently Asked Questions
 
 1. What IPs will the scan come from?
-
-    - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
-    - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
-    - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241` 
+   - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
+   - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
+   - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241`
 
 2. Can the Port Scanner bypass other security rules configured?
-
-    - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
+   - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
 
 3. How long do scans take?
-
-    - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
+   - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
 
 4. Can I stop automatic scanning?
-
-    - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
+   - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
 
 5. What are the limitations for the scans?
-
-    - Scans are limited to ranges of up to 5,000 IPs.
-    - The API scans both IPv4 and IPv6 IP addresses.
\ No newline at end of file
+   - Scans are limited to ranges of up to 5,000 IPs.
+   - The API scans both IPv4 and IPv6 IP addresses.
diff --git a/src/content/docs/security-center/investigate/change-categorization.mdx b/src/content/docs/security-center/investigate/change-categorization.mdx
index c2efde74687cbbf..bc56bde0cf28d7a 100644
--- a/src/content/docs/security-center/investigate/change-categorization.mdx
+++ b/src/content/docs/security-center/investigate/change-categorization.mdx
@@ -6,7 +6,6 @@ products:
   - security-center
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/docs/security-center/investigate/index.mdx b/src/content/docs/security-center/investigate/index.mdx
index f63c519b1be248a..6a3e0202c62c662 100644
--- a/src/content/docs/security-center/investigate/index.mdx
+++ b/src/content/docs/security-center/investigate/index.mdx
@@ -6,7 +6,6 @@ products:
   - security-center
 sidebar:
   order: 6
-
 ---
 
 :::note[User permission]
diff --git a/src/content/docs/security-center/investigate/investigate-threats.mdx b/src/content/docs/security-center/investigate/investigate-threats.mdx
index 48ce56a091e23fd..8056b226555f5c8 100644
--- a/src/content/docs/security-center/investigate/investigate-threats.mdx
+++ b/src/content/docs/security-center/investigate/investigate-threats.mdx
@@ -6,10 +6,9 @@ products:
   - security-center
 sidebar:
   order: 3
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Users can investigate the details of an IP address, domain name, URL, or Autonomous System Number (ASN). You can find the Investigate feature in your Cloudflare account's Security Center and in [Cloudflare Radar](https://radar.cloudflare.com/scan).
 
@@ -106,4 +105,4 @@ To download a report:
    <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your domain and select **Search**.
-3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
\ No newline at end of file
+3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
diff --git a/src/content/docs/security-center/investigate/scan-limits.mdx b/src/content/docs/security-center/investigate/scan-limits.mdx
index 4a87a3ad19d63d5..00c9e0921faf0d5 100644
--- a/src/content/docs/security-center/investigate/scan-limits.mdx
+++ b/src/content/docs/security-center/investigate/scan-limits.mdx
@@ -5,17 +5,13 @@ products:
   - security-center
 head: []
 description: Limits
-
 ---
 
 URL scans are limited by search history, Public and Unlisted visibility, and requests per second across different Cloudflare plans.
 
-
-
 | Cloudflare Plan    | Search history | Public scans (per month) | Unlisted scans (per month) | Rate limit       |
 | ------------------ | -------------- | ------------------------ | -------------------------- | ---------------- |
 | **Free / Radar**   | last 50 scans  | 5,000                    | none                       | 1 per 10 seconds |
 | **Self serve**     | 30 days        | 5,000                    | 500                        | 1 per 10 seconds |
 | **Enterprise**     | 12 months      | 10,000                   | 5,000                      | 12 per second    |
 | **Cloudforce One** | Unlimited      | 75,000                   | 20,000                     | 12 per second    |
-
diff --git a/src/content/docs/security/overview.mdx b/src/content/docs/security/overview.mdx
index 544b227b7e54dfc..91001dcbbfba6db 100644
--- a/src/content/docs/security/overview.mdx
+++ b/src/content/docs/security/overview.mdx
@@ -24,10 +24,11 @@ The Security overview page displays:
 
 ## Security action items
 
-**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity. 
-  - **Action item types**:
-    - Suspicious activity
-    - Security insight
+**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity.
+
+- **Action item types**:
+  - Suspicious activity
+  - Security insight
 - **Criticality**: Your action items are ranked by the highest criticality, showing critical first, moderate, and low respectively.
 - **Filters**: You can filter your action items by Criticality, Insight Type, and Security Category.
   - Criticality:
@@ -35,20 +36,20 @@ The Security overview page displays:
     - Moderate
     - Critical
   - Insight Types:
-    - Suspicious activity 
-    - Exposed infrastructure 
-    - Insecure configuration 
+    - Suspicious activity
+    - Exposed infrastructure
+    - Insecure configuration
     - Configuration suggestion
     - Compliance Violation
     - Email Security
     - Weak Authentication
-  - Security Category: 
+  - Security Category:
     - Web application exploits
     - AI exploits
-    - DDoS attacks 
-    - Bot traffic 
-    - API abuse 
-    - Client-side abuse 
+    - DDoS attacks
+    - Bot traffic
+    - API abuse
+    - Client-side abuse
     - Fraud
 - **Review**: Review your security action items for more detailed information and recommended actions to resolve.
 - **Load more**: View the full list of security action items.
@@ -71,14 +72,14 @@ Archiving a detected suspicious activity will only archive that item from the se
 
 To view when an action item’s status was changed and the rationale provided for that change, use the following API commands to retrieve audit logs:
 
-| Method | Path | Description |
-| ------ | ---- | ----------- |
-| `GET` | `/api/accounts/{accountID}/insights/audit-log` | List all audit logs for an account |
-| `GET` | `/api/accounts/{accountID}/insights/{insightID}/audit-log` | List audit logs for a specific issue |
-| `GET` | `/api/accounts/{accountID}/issues/audit-log` | List all audit logs for account issues |
-| `GET` | `/api/accounts/{accountID}/issues/{insightID}/audit-log` | List all audit logs for a specific issue |
-| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log` | List all audit logs for a domain |
-| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
+| Method | Path                                                                      | Description                                      |
+| ------ | ------------------------------------------------------------------------- | ------------------------------------------------ |
+| `GET`  | `/api/accounts/{accountID}/insights/audit-log`                            | List all audit logs for an account               |
+| `GET`  | `/api/accounts/{accountID}/insights/{insightID}/audit-log`                | List audit logs for a specific issue             |
+| `GET`  | `/api/accounts/{accountID}/issues/audit-log`                              | List all audit logs for account issues           |
+| `GET`  | `/api/accounts/{accountID}/issues/{insightID}/audit-log`                  | List all audit logs for a specific issue         |
+| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log`             | List all audit logs for a domain                 |
+| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
 
 Refer to our [Security Center API documentation](/api/resources/security_center) to review the action item audit logs by account, domain, or a specific `issue_id`.
 
@@ -93,4 +94,4 @@ View the patterns and highlights from your domain's traffic in the past 30 days.
 The Cloudflare dashboard displays:
 
 - **Monthly requests**: View the monthly requests and traffic that has been mitigated by Cloudflare.
-- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
\ No newline at end of file
+- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
diff --git a/src/content/docs/smart-shield/concepts/index.mdx b/src/content/docs/smart-shield/concepts/index.mdx
index 1120c7c003aa4c3..12403e47aa9a979 100644
--- a/src/content/docs/smart-shield/concepts/index.mdx
+++ b/src/content/docs/smart-shield/concepts/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/concepts/network-diagram.mdx b/src/content/docs/smart-shield/concepts/network-diagram.mdx
index 3eec884e62a0d79..307591a0ae523f1 100644
--- a/src/content/docs/smart-shield/concepts/network-diagram.mdx
+++ b/src/content/docs/smart-shield/concepts/network-diagram.mdx
@@ -16,4 +16,4 @@ Requests from visitors first reach a nearby lower-tier data center. For static (
 
 For dynamic (non-cacheable) requests, [Argo Smart Routing](/smart-shield/configuration/argo/) finds the fastest network path to your origin. Between Cloudflare's upper-tier data centers and your origin, [connection reuse](/smart-shield/concepts/connection-reuse/) packages multiple requests into a single connection, reducing the total number of connections your origin handles.
 
-[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
\ No newline at end of file
+[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
diff --git a/src/content/docs/smart-shield/configuration/argo.mdx b/src/content/docs/smart-shield/configuration/argo.mdx
index 16a4fce8d7e97be..0d1fcae78001d37 100644
--- a/src/content/docs/smart-shield/configuration/argo.mdx
+++ b/src/content/docs/smart-shield/configuration/argo.mdx
@@ -18,4 +18,4 @@ Available with Smart Shield + Argo and Smart Shield Advanced.
 
 Cloudflare provides analytics to show the performance benefits of Argo Smart Routing.
 
-<Render file="argo-analytics" product="smart-shield" />
\ No newline at end of file
+<Render file="argo-analytics" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
index 14f71bac0cc40fc..3e14a1542d4343a 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
@@ -14,9 +14,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="cache-reserve-analytics"
-  product="cache"
+	file="cache-reserve-analytics"
+	product="cache"
 	params={{
 		conditional: "smart-shield-tile",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
index 8eeb03f8661c785..9c1e9769086a7e3 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
@@ -40,4 +40,4 @@ You can remove all data stored in Cache Reserve. In most cases, deletion takes a
 
 :::note
 If you want to purge your cache instead, refer to [cache configurations](/cache/how-to/purge-cache/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
index 5d0b8457ad806be..40b660890f6f6f9 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
@@ -13,7 +13,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-  file="cache-reserve-operations"
-  product="cache"
-/>
\ No newline at end of file
+<Render file="cache-reserve-operations" product="cache" />
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
index 6b011755c7d6d69..4af2a88245d5455 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
@@ -38,7 +38,7 @@ flowchart LR
 
 If the server does not have access to an applicable IP, the following options are checked and the first that is possible will take place:
 
-* Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
+- Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
 
 ```mermaid
 flowchart LR
@@ -55,7 +55,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-* Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
+- Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
 
 ```mermaid
 flowchart LR
@@ -77,7 +77,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-* Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
+- Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
 
 ```mermaid
 flowchart LR
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
index c7f7d638be9549d..44ef7eec5859bde 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Refer to the pages below to understand how Dedicated CDN Egress IPs work.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
index 4ed679361eb9526..2275ff704685684 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
@@ -24,9 +24,9 @@ Dedicated CDN Egress IPs was formerly known as Cloudflare Aegis ([release blog p
 
 With Dedicated CDN Egress IPs, you can:
 
-* Lock down your network firewall to only allow traffic from your dedicated IPs.
-* Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
-* Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
+- Lock down your network firewall to only allow traffic from your dedicated IPs.
+- Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
+- Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
 
 ## Scope
 
@@ -40,4 +40,4 @@ Dedicated CDN Egress IPs are included within [BGP advertisement over CNI](/netwo
 
 <DirectoryListing />
 
-[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
\ No newline at end of file
+[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
index bf1bd852f10c57a..7e7eb7f4fe8699d 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
@@ -16,7 +16,7 @@ Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data and monitor
 
 <Render file="concurrent-connections-explainer" product="smart-shield" />
 
-Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the  [example](#example) below for a quickstart.
+Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the [example](#example) below for a quickstart.
 
 ## GraphQL schema
 
@@ -25,19 +25,19 @@ The specific schema to get Dedicated CDN Egress IPs data is called `aegisIpUtili
 You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions:
 
 - `datetimeFiveMinutes` <Type text="time" />
-    - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
+  - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
 
 - `popName` <Type text="string" />
-    - The Cloudflare point of presence (PoP). For example, `sjc`.
+  - The Cloudflare point of presence (PoP). For example, `sjc`.
 
 - `egressIp` <Type text="string" />
-    - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
+  - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
 
 - `origin` <Type text="string" />
-    - Origin IP and port. For example, `203.0.113.150:443`.
+  - Origin IP and port. For example, `203.0.113.150:443`.
 
 - `popUtilizationKey` <Type text="string" />
-    - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
+  - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
 
 ## Example
 
@@ -47,100 +47,100 @@ You can also select the button at the bottom to use this query for your account
 
 ```graphql graphql-api-explorer "popName: "<CLOUDFLARE_POP>"" "egressIp: "<YOUR_EGRESS_IP>"" "origin: "<ORIGIN_IP_AND_PORT>""
 query AegisIpUtilizationQuery(
-  $accountTag: string
-  $datetimeStart: string
-  $datetimeEnd: string
+	$accountTag: string
+	$datetimeStart: string
+	$datetimeEnd: string
 ) {
-  viewer {
-    utilization: accounts(filter: { accountTag: $accountTag }) {
-      avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        avg {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          popName: "<CLOUDFLARE_POP>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          egressIp: "<YOUR_EGRESS_IP>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          origin: "<ORIGIN_IP_AND_PORT>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-    }
-  }
+	viewer {
+		utilization: accounts(filter: { accountTag: $accountTag }) {
+			avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				avg {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					popName: "<CLOUDFLARE_POP>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					egressIp: "<YOUR_EGRESS_IP>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					origin: "<ORIGIN_IP_AND_PORT>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+		}
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
index f36cbde97e071bb..da17ba92284032c 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
@@ -63,4 +63,4 @@ Workers subrequests — requests from one Worker to another — are expected to
 
 For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
 
-[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
\ No newline at end of file
+[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
diff --git a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
index 121427dcf85f924..2ff26322bf71a01 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
@@ -15,7 +15,4 @@ import { Render } from "~/components";
 
 Use Health Checks analytics to debug possible origin issues.
 
-<Render
-  file="health-checks-analytics"
-	product="smart-shield"
-/>
\ No newline at end of file
+<Render file="health-checks-analytics" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/health-checks/index.mdx b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
index ca2d659d7d5eb14..0f3fdf5c2c0f9a7 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/index.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
@@ -24,4 +24,4 @@ Available for Pro, Business, and Enterprise customers in all Smart Shield packag
 
 ## Further reading
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
index 292d644b16b754d..07cacf201721425 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
@@ -20,8 +20,8 @@ Refer to the section below to learn how to manage your Smart Shield health check
 3. For Health Checks, select **Manage**.
 4. Select **Create** or find an existing health check and select **Edit**.
 5. Fill out the form or edit existing values, paying special attention to:
-   * The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
-   * **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
+   - The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
+   - **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
 6. Select **Save and Deploy**.
 
 ## Configure alerts
diff --git a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
index 5a42572ca2e935b..e269a8febaf8111 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
@@ -15,4 +15,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
+<Render file="zone-lockdown" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/index.mdx b/src/content/docs/smart-shield/configuration/index.mdx
index 9a1b637e55751a5..6244ba2195424e8 100644
--- a/src/content/docs/smart-shield/configuration/index.mdx
+++ b/src/content/docs/smart-shield/configuration/index.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
index 9073a8017865420..49cf513c617947e 100644
--- a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
@@ -16,4 +16,4 @@ import { Render } from "~/components";
 Available with Smart Shield Advanced.
 :::
 
-<Render file="regional-tiered-cache" product="cache" />
\ No newline at end of file
+<Render file="regional-tiered-cache" product="cache" />
diff --git a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
index f7fafaa47aea6a9..9b9c6760721cd54 100644
--- a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
@@ -18,4 +18,4 @@ Available in all Smart Shield packages.
 
 With data centers around the world, Cloudflare caches content very close to end users. However, if a piece of content is not in cache, the Cloudflare data centers must contact the origin server to receive the cacheable content. Tiered cache works by dividing Cloudflare's data centers into a hierarchy of lower-tiers and upper-tiers, where only upper-tiers can ask your origin for content.
 
-<Render file="smart-tiered-cache" product="cache" />
\ No newline at end of file
+<Render file="smart-tiered-cache" product="cache" />
diff --git a/src/content/docs/spectrum/about/byoip.mdx b/src/content/docs/spectrum/about/byoip.mdx
index b574fc12e5048f2..3e3fb82322e59aa 100644
--- a/src/content/docs/spectrum/about/byoip.mdx
+++ b/src/content/docs/spectrum/about/byoip.mdx
@@ -5,22 +5,18 @@ description: Use your own IP addresses with Spectrum applications.
 products:
   - spectrum
 weight: 0
-
 ---
 
-import { APIRequest, Render } from "~/components"
+import { APIRequest, Render } from "~/components";
 
 When creating a Spectrum application, Cloudflare normally assigns an arbitrary IP from Cloudflare’s IP pool to your application. If you want to be explicit in your network setup or use your own IP addresses, BYOIP with Spectrum allows you to do just that.
 
 BYOIP stands for [Bring Your Own IP](/byoip/). If you own an IP prefix you can migrate it to Cloudflare. After migration, Cloudflare broadcasts your IP prefix and traffic is routed to the global Cloudflare network. However, without configuration, Cloudflare will not know how to handle this traffic. The last step is to add Spectrum applications for all applications that you wish to protect with the IP addresses you want associated with them.
 
-
 :::caution
 
-
 When switching from non-BYOIP to BYOIP, if you are already using a Spectrum application, you need to delete your configurations and recreate new ones.
 
-
 :::
 
 The smallest prefixes that Cloudflare currently supports is /24 for IPv4 and /48 for IPv6.
@@ -35,22 +31,22 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 
 ```json
 {
-  "id": "4590376cf2994d72cee36828ec4eff19",
-  "protocol": "tcp/22",
-  "dns": {
-    "type": "ADDRESS",
-    "name": "ssh.example.com"
-  },
-  "origin_direct": ["tcp://192.0.2.1:22"],
-  "ip_firewall": true,
-  "proxy_protocol": false,
-  "spp": false,
-  "tls": "off",
-  "traffic_type": "direct",
-  "edge_ips": {
-    "type": "static",
-    "ips": ["198.51.100.10", "2001:DB8::1"]
-  }
+	"id": "4590376cf2994d72cee36828ec4eff19",
+	"protocol": "tcp/22",
+	"dns": {
+		"type": "ADDRESS",
+		"name": "ssh.example.com"
+	},
+	"origin_direct": ["tcp://192.0.2.1:22"],
+	"ip_firewall": true,
+	"proxy_protocol": false,
+	"spp": false,
+	"tls": "off",
+	"traffic_type": "direct",
+	"edge_ips": {
+		"type": "static",
+		"ips": ["198.51.100.10", "2001:DB8::1"]
+	}
 }
 ```
 
@@ -59,25 +55,20 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 In the example below, the application routes traffic through Cloudflare’s HTTP pipeline, including WAF, Workers and CDN functionality.
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    protocol: "tcp/80",
-    dns: {
-      type: "ADDRESS",
-      name: "www.example.com"
-    },
-    origin_direct: [
-      "tcp://192.0.2.1:80"
-    ],
-    tls: "off",
-    traffic_type: "http",
-    edge_ips: {
-      type: "static",
-      ips: [
-        "198.51.100.10",
-        "2001:DB8::1"
-      ]
-    }
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		protocol: "tcp/80",
+		dns: {
+			type: "ADDRESS",
+			name: "www.example.com",
+		},
+		origin_direct: ["tcp://192.0.2.1:80"],
+		tls: "off",
+		traffic_type: "http",
+		edge_ips: {
+			type: "static",
+			ips: ["198.51.100.10", "2001:DB8::1"],
+		},
+	}}
 />
diff --git a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
index 21f55d4cd8281c7..30cfcf85e672028 100644
--- a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
+++ b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
@@ -5,7 +5,6 @@ description: Layer 3 and 4 DDoS protection for TCP and UDP Spectrum applications
 products:
   - spectrum
 weight: 0
-
 ---
 
 Spectrum provides DDoS Protection at layers 3-4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/), that is against TCP and UDP based DDoS attacks.
diff --git a/src/content/docs/spectrum/about/ftp.mdx b/src/content/docs/spectrum/about/ftp.mdx
index 1d666adace4bcc4..68f7e8ff116275c 100644
--- a/src/content/docs/spectrum/about/ftp.mdx
+++ b/src/content/docs/spectrum/about/ftp.mdx
@@ -13,17 +13,15 @@ Enabling Spectrum for FTP is not straightforward due to the implementation of th
 
 :::note
 
-
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
-
 :::
 
 ## How FTP Operates
 
 FTP leverages two different sockets, one for issuing commands and the other for actual data transfer. The control socket takes care of users logging in and sending commands, and the data socket is where directory listings and files actually get transferred.
 
-There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects *back* to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
+There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects _back_ to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
 
 In passive mode, the FTP server communicates a port that the client should connect to, which is done on the control socket via a PASV command. By default, the FTP server responds with the IP address that it is listening on. This scenario is fine for servers running directly on a public-facing IP but creates issues when a server is behind an NAT, firewall, or Cloudflare Spectrum.
 
@@ -31,7 +29,7 @@ Alternatively, more modern FTP server software supports [FTP extensions](https:/
 
 ## What Does and Does Not Work
 
-Spectrum is able to protect servers serving FTP traffic in *passive mode only*. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
+Spectrum is able to protect servers serving FTP traffic in _passive mode only_. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
 
 Passive mode in combination with EPSV works out of the box with no origin-side configuration required. Note that the client must also support EPSV for this to work. Traditional passive mode with PASV is possible with minimal origin-side configuration (see below, Protecting an FTP server with Spectrum)
 
@@ -71,14 +69,14 @@ Example configuration for [vsftpd](https://security.appspot.com/vsftpd.html):
 
 To use Spectrum TCP to proxy and protect FTPS, specifically ProFTPD, the following example configuration is recommended:
 
-* **Control Port**: Port 21
-* **Data Ports**: Port ranges 50000-50500
+- **Control Port**: Port 21
+- **Data Ports**: Port ranges 50000-50500
 
 On the ProFTPD server side use the following example configuration:
 
-* `MasqueradeAddress`: `www.example.com`
-* `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
-* `PassivePorts`: `50000-50500`
+- `MasqueradeAddress`: `www.example.com`
+- `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
+- `PassivePorts`: `50000-50500`
 
 For more details, refer to the [ProFTPD documentation](http://www.proftpd.org/docs/modules/mod_core.html).
 
diff --git a/src/content/docs/spectrum/about/index.mdx b/src/content/docs/spectrum/about/index.mdx
index a45de1bbf3080f6..79bf764731996bb 100644
--- a/src/content/docs/spectrum/about/index.mdx
+++ b/src/content/docs/spectrum/about/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information about concepts related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/about/static-ip.mdx b/src/content/docs/spectrum/about/static-ip.mdx
index f075127c3337700..9ad484844461329 100644
--- a/src/content/docs/spectrum/about/static-ip.mdx
+++ b/src/content/docs/spectrum/about/static-ip.mdx
@@ -5,10 +5,9 @@ description: Assign persistent IP addresses to your Spectrum applications.
 products:
   - spectrum
 weight: 0
-
 ---
 
-import { APIRequest, Render } from "~/components"
+import { APIRequest, Render } from "~/components";
 
 When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.
 
@@ -29,35 +28,30 @@ Once you get your static IP from Cloudflare, you can use it via API, just like [
 When creating a Spectrum application through the API, specify the static IPs that you have been provided. See, for instance, the API example below that creates an application routing traffic through Cloudflare’s HTTP pipeline.
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    protocol: "tcp/80",
-    dns: {
-      type: "ADDRESS",
-      name: "www.example.com"
-    },
-    origin_direct: [
-      "tcp://192.0.2.1:80"
-    ],
-    tls: "off",
-    traffic_type: "http",
-    edge_ips: {
-      type: "static",
-      ips: [
-        "198.51.100.10",
-        "2001:DB8::1"
-      ]
-    }
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		protocol: "tcp/80",
+		dns: {
+			type: "ADDRESS",
+			name: "www.example.com",
+		},
+		origin_direct: ["tcp://192.0.2.1:80"],
+		tls: "off",
+		traffic_type: "http",
+		edge_ips: {
+			type: "static",
+			ips: ["198.51.100.10", "2001:DB8::1"],
+		},
+	}}
 />
 
 ## Check your static IPs
 
 <Render
-  file="check-leased-ips"
+	file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "static IPs for Spectrum"
+		product: "static IPs for Spectrum",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/spectrum/glossary.mdx b/src/content/docs/spectrum/glossary.mdx
index 5dfed742cc6ccb5..e858503baad6ca3 100644
--- a/src/content/docs/spectrum/glossary.mdx
+++ b/src/content/docs/spectrum/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - spectrum
 sidebar:
   order: 7
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Spectrum documentation.
 
diff --git a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
index 3961a4766160937..bed4a42932be361 100644
--- a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
+++ b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
@@ -5,7 +5,6 @@ description: Pass client IP information to your origin using Proxy protocol v1 o
 products:
   - spectrum
 weight: 0
-
 ---
 
 import { DashButton } from "~/components";
@@ -16,10 +15,8 @@ Some services you run may require knowledge of the true client IP. In those case
 
 :::note
 
-
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
-
 :::
 
 ## Enable Proxy Protocol v1 for TCP
diff --git a/src/content/docs/spectrum/how-to/index.mdx b/src/content/docs/spectrum/how-to/index.mdx
index 9f660cc61eee6f5..8edbdf1ca9239c5 100644
--- a/src/content/docs/spectrum/how-to/index.mdx
+++ b/src/content/docs/spectrum/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information on completing Spectrum related tasks, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/protocols-per-plan.mdx b/src/content/docs/spectrum/protocols-per-plan.mdx
index 6ae364f5a9f92e8..b82fd38bf63e579 100644
--- a/src/content/docs/spectrum/protocols-per-plan.mdx
+++ b/src/content/docs/spectrum/protocols-per-plan.mdx
@@ -6,10 +6,9 @@ products:
   - spectrum
 sidebar:
   order: 2
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 On this table, you have information about which protocols are available per plan.
 
diff --git a/src/content/docs/spectrum/reference/analytics.mdx b/src/content/docs/spectrum/reference/analytics.mdx
index 8ad2a392de6915f..3f021a4dd31e9fb 100644
--- a/src/content/docs/spectrum/reference/analytics.mdx
+++ b/src/content/docs/spectrum/reference/analytics.mdx
@@ -9,12 +9,10 @@ tags:
   - Analytics
 ---
 
-import { Render, APIRequest } from "~/components"
+import { Render, APIRequest } from "~/components";
 
 Cloudflare measures the following metrics for every connection.
 
-
-
 | Metric         | Name                                | Example | Unit                 |
 | -------------- | ----------------------------------- | ------- | -------------------- |
 | count          | Count of total events               | `1000`  | Count                |
@@ -25,14 +23,10 @@ Cloudflare measures the following metrics for every connection.
 | duration90th   | 90th percentile connection duration | `1.0`   | Time in milliseconds |
 | duration99th   | 99th percentile connection duration | `1.0`   | Time in milliseconds |
 
-
-
 ## Additional dimensions
 
 You can divide your analytics further by the following dimensions.
 
-
-
 | Dimension | Name                          | Example                                                              |
 | --------- | ----------------------------- | -------------------------------------------------------------------- |
 | event     | Connection Event              | `connect`, `progress`, `disconnect`, `originError`, `clientFiltered` |
@@ -40,14 +34,10 @@ You can divide your analytics further by the following dimensions.
 | coloName  | Colo Name                     | `SFO`                                                                |
 | ipVersion | IP version used by the client | `4`, `6`                                                             |
 
-
-
 ## Operators for filtering
 
 Use the operators below to filter data.
 
-
-
 | Operator | Name                     | URL Encoded |
 | -------- | ------------------------ | ----------- |
 | `==`     | Equals                   | `%3D%3D`    |
@@ -57,8 +47,6 @@ Use the operators below to filter data.
 | `>=`     | Greater than or equal to | `%3E%3D`    |
 | `<=`     | Less than or equal to    | `%3C%3D`    |
 
-
-
 <Render file="api-combine-filters" product="fundamentals" />
 
 ## Analytics request structure
@@ -68,26 +56,26 @@ Use the operators below to filter data.
 /api/v4/zones/{zone_id}/spectrum/analytics/events/bytime?metrics=METRICS&dimensions=DIMENSIONS&filters=FILTERS&since=FROM_TS&sort=SORT&until=TO_TS&limit=LIMIT
 ```
 
-* METRICS is one or more metrics (such as count) to compute
-* DIMENSIONS can be used to break down the data by given attributes
-* FILTERS used to filter rows by one or more dimensions (see Filters section below)
-* SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
-* TO\_TS is that end of time interval to query, defaults to current time
-* FROM\_TS is that start of time interval to query, defaults to TO\_TS - 6 hours
-* STEP is used to select time series resolution when using endpoint:
-* auto or omitted - selects time step most appropriate to time interval
-  * year
-  * quarter
-  * month
-  * week
-  * day
-  * hour
+- METRICS is one or more metrics (such as count) to compute
+- DIMENSIONS can be used to break down the data by given attributes
+- FILTERS used to filter rows by one or more dimensions (see Filters section below)
+- SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
+- TO_TS is that end of time interval to query, defaults to current time
+- FROM_TS is that start of time interval to query, defaults to TO_TS - 6 hours
+- STEP is used to select time series resolution when using endpoint:
+- auto or omitted - selects time step most appropriate to time interval
+  - year
+  - quarter
+  - month
+  - week
+  - day
+  - hour
 
 ## Analytics query example
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/analytics/events/summary"
-  method="GET"
+	path="/zones/{zone_id}/spectrum/analytics/events/summary"
+	method="GET"
 />
 
 Refer to the [Spectrum API documentation](/api/resources/spectrum/subresources/analytics/subresources/aggregates/subresources/currents/methods/get/) for more examples of API requests.
diff --git a/src/content/docs/spectrum/reference/index.mdx b/src/content/docs/spectrum/reference/index.mdx
index 1cb17fdcb764a75..2f5495921b7c522 100644
--- a/src/content/docs/spectrum/reference/index.mdx
+++ b/src/content/docs/spectrum/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/reference/layer-7-analytics.mdx b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
index ac15ed1aa946651..ed2b0717d749251 100644
--- a/src/content/docs/spectrum/reference/layer-7-analytics.mdx
+++ b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - spectrum
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Even when you have Spectrum enabled to handle Layer 4 traffic (for example, TCP/UDP connections), you may still notice traffic in your Layer 7 (L7) analytics dashboard. This is due to the way Cloudflare's Layer 7 <GlossaryTooltip term="content delivery network (CDN)">CDN</GlossaryTooltip>
  and Spectrum handle customer identity differently.
@@ -42,4 +42,4 @@ This means traffic for this hostname undergoes the standard Layer 7 CDN products
 
 If you want to prevent traffic for Layer-4-only Spectrum hostnames from being proxied through Layer 7 to your origin (including unwanted scans or requests), we recommend implementing a Layer 7 WAF (Web Application Firewall) rule. This rule can block traffic directed at specific hostnames or ports, ensuring that only legitimate traffic reaches your Spectrum service.
 
-For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
\ No newline at end of file
+For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
diff --git a/src/content/docs/spectrum/reference/logs.mdx b/src/content/docs/spectrum/reference/logs.mdx
index 0ee954278aec0d5..e5c27ce81e5be5e 100644
--- a/src/content/docs/spectrum/reference/logs.mdx
+++ b/src/content/docs/spectrum/reference/logs.mdx
@@ -19,8 +19,6 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 
 ## Status Codes
 
-
-
 | Code | Description                                                                                        |
 | ---- | -------------------------------------------------------------------------------------------------- |
 | 0    | Connection was opened successfully.                                                                |
@@ -52,4 +50,3 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 | 533  | Internal error while resolving origin to an IP.                                                    |
 | 540  | The client/edge TLS handshake failed due to an invalid configuration.                              |
 | 999  | Unknown connection error.                                                                          |
-
diff --git a/src/content/docs/spectrum/reference/settings-by-plan.mdx b/src/content/docs/spectrum/reference/settings-by-plan.mdx
index c243f1c03952069..9865188065dbb98 100644
--- a/src/content/docs/spectrum/reference/settings-by-plan.mdx
+++ b/src/content/docs/spectrum/reference/settings-by-plan.mdx
@@ -5,19 +5,12 @@ description: Spectrum API fields and settings available by Cloudflare plan.
 products:
   - spectrum
 weight: 0
-
 ---
 
-
-
 Certain fields in Spectrum request and response bodies require an Enterprise plan. To upgrade your plan, contact your account team.
 
 Spectrum properties requiring an Enterprise plan:
 
-
-
-
-
 | Name                 | Type    | Description                                                                                                                                                                                                                                                                                                              | Example                                                    |
 | -------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
 | `origin_dns`         | object  | Method and parameters used to discover the origin server address via DNS. Valid record types are `A`, `AAAA`, `SRV` and empty (both `A` and `AAA`).<br />A request must contain either an `origin_dns` parameter or an `origin_direct` parameter. When both are specified the service returns an `HTTP 400 Bad Request`. | `origin_dns: {type: A, name: mqtt.example.com, ttl: 1200}` |
@@ -25,11 +18,6 @@ Spectrum properties requiring an Enterprise plan:
 | `proxy_protocol`     | string  | Enables Proxy Protocol to the origin. Spectrum supports `v1`, `v2`, and `simple` proxy protocols. Refer to [Proxy Protocol](/spectrum/how-to/enable-proxy-protocol/) for more details.                                                                                                                                   | `off`                                                      |
 | `ip_firewall`        | boolean | Enables IP Access rules for this application.                                                                                                                                                                                                                                                                            | `true`                                                     |
 | `tls`                | string  | Type of TLS termination for the application. Options are `off` (default, also known as Passthrough), `flexible`, `full`, and `strict`. Refer to [Configuration Options](/spectrum/reference/configuration-options/) for descriptions of each.                                                                            | `full`                                                     |
-| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic\_type set to `direct`.                                                                                                                                                                                  | `true`                                                     |
-
-
-
-
+| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic_type set to `direct`.                                                                                                                                                                                   | `true`                                                     |
 
 Review the [Spectrum API documentation](/api/resources/spectrum/subresources/apps/methods/list/) for example API requests.
-
diff --git a/src/content/docs/speed/aim.mdx b/src/content/docs/speed/aim.mdx
index c8139eed9a0013a..95fc9acbd18a0d7 100644
--- a/src/content/docs/speed/aim.mdx
+++ b/src/content/docs/speed/aim.mdx
@@ -4,7 +4,6 @@ description: Measure real-world internet quality metrics for your visitors.
 products:
   - speed
 title: Aggregated Internet Measurement
-
 ---
 
 Aggregated Internet Measurement (AIM) helps you understand your Internet quality to identify scenarios that your Internet connection is good or bad for. Typically, an Internet speed test provides you with upload and download speeds, which may not always provide a holistic view of your Internet quality.
@@ -15,28 +14,28 @@ AIM uses a scoring rubric that assigns point values based on speed tests to help
 
 AIM analyzes the following metrics to generate your score:
 
-* Latency
-* Packet Loss
-* Download
-* Upload
-* Loaded Latency
-* Jitter
+- Latency
+- Packet Loss
+- Download
+- Upload
+- Loaded Latency
+- Jitter
 
-After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC.  These scores will indicate how good your Internet is in each of these scenarios.
+After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC. These scores will indicate how good your Internet is in each of these scenarios.
 
 The possible network scores are:
 
-* Bad
-* Poor
-* Average
-* Good
-* Great
+- Bad
+- Poor
+- Average
+- Good
+- Great
 
 ## Improve your network score
 
 You have a few options to help improve network scores.
 
-* **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
-* **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
-* **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
-* **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
+- **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
+- **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
+- **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
+- **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
diff --git a/src/content/docs/speed/glossary.mdx b/src/content/docs/speed/glossary.mdx
index fc3634a28e51568..2fb9f99dba9493c 100644
--- a/src/content/docs/speed/glossary.mdx
+++ b/src/content/docs/speed/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Speed documentation.
 products:
   - speed
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Speed documentation.
 
diff --git a/src/content/docs/speed/observatory/dashboard.mdx b/src/content/docs/speed/observatory/dashboard.mdx
index 1017a25218c61a5..6a18975aceb0150 100644
--- a/src/content/docs/speed/observatory/dashboard.mdx
+++ b/src/content/docs/speed/observatory/dashboard.mdx
@@ -40,11 +40,10 @@ The **Network Performance** section shows timing data that can help pinpoint whe
 
 - **Time to First Byte (TTFB)**: Measures the time between the initial request and the first byte of the response.
 - **Time to Last Byte (TTLB) Breakdown**: Provides a breakdown of response phases:
-
-    - DNS resolution time
-    - TCP connection time
-    - Request processing time at the server
-    - Response transfer time
+  - DNS resolution time
+  - TCP connection time
+  - Request processing time at the server
+  - Response transfer time
 
 This breakdown helps identify whether delays are caused by DNS, connection setup, server processing, or response delivery.
 
@@ -77,4 +76,4 @@ Use the Speed Overview dashboard to:
 - Track **Core Web Vitals** to ensure a good user experience.
 - Analyze **Network Performance** to identify latency bottlenecks.
 - Diagnose errors with **HTTP Traffic** insights.
-- Confirm site reliability using **Synthetic Monitoring** results.
\ No newline at end of file
+- Confirm site reliability using **Synthetic Monitoring** results.
diff --git a/src/content/docs/speed/observatory/rum-beacon.mdx b/src/content/docs/speed/observatory/rum-beacon.mdx
index 66c0e8035856ce1..8e343c58ee410d5 100644
--- a/src/content/docs/speed/observatory/rum-beacon.mdx
+++ b/src/content/docs/speed/observatory/rum-beacon.mdx
@@ -8,7 +8,6 @@ tags:
   - Privacy
 sidebar:
   order: 4
- 
 ---
 
 The RUM beacon is a JavaScript snippet that runs when a Cloudflare customer enables RUM through [Web Analytics](/web-analytics/) or [Observatory](/speed/observatory/). This script runs in users' browsers when they visit the customer's site, and its purpose is to collect performance-related data, for example, page load time, and send it to Cloudflare's systems for processing. This [data](/web-analytics/data-metrics/) is then presented to the customer, providing valuable insights into the website's performance and usage.
@@ -17,7 +16,7 @@ The RUM beacon script can be enabled into a webpage in two ways:
 
 - **One-click setup**: For [sites proxied through Cloudflare](/web-analytics/get-started/#sites-proxied-through-cloudflare) that have Web Analytics enabled, the snippet can be _automatically_ injected into pages as the HTML response passes through Cloudflare's edge network to the browser by simply enabling the automatic injection option.
 
-- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML. 
+- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML.
 
 ## Data collection
 
@@ -25,36 +24,36 @@ Once downloaded to the browser, the RUM beacon script runs as JavaScript in the
 
 The data collected from the browser is summarized in the table below:
 
-| Field      | Example  | Description  | How it is collected    |
-|------------|----------|--------------|------------------------|
-| `pageloadId`  | 0c698922-8d60-40bf-85ac-7982b5f8034d  | The unique ID for the page. | Generated in the browser code.  |
-| `referrer`    | https://cfrumtest.com/ | The referring page URL. | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
-| `startTime`  | 1693488419352  | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                        |
-| `memory` | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }` | Measures memory heap size. | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                              |
-| `timings` | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming) | Timing data. | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)     |
-| `timingV2` | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                   |
-| `resources`  | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | Resource timing data.  | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                     |
-| `firstPaint` | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | Paint timing data. | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) |
-| `firstContentfulPaint` | 209  | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1] |
-| `FCP`        | 209 | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `LCP`        | 209 | Largest Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `CLS`        | 0.001 | Cumulative Layout Shift metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-                                                           |
-| `TTFB`       | 0.03 | Time to First Byte metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `INP`        | 1.23 | Interaction to Next Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `landingPath`| https://cfrumtest.com/  | The landing page URL. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | 
+| Field                  | Example                                                                                                              | Description                                  | How it is collected                                                                                                                                                                                                                                                                                       |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pageloadId`           | 0c698922-8d60-40bf-85ac-7982b5f8034d                                                                                 | The unique ID for the page.                  | Generated in the browser code.                                                                                                                                                                                                                                                                            |
+| `referrer`             | https://cfrumtest.com/                                                                                               | The referring page URL.                      | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
+| `startTime`            | 1693488419352                                                                                                        | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                                                                                                                                                                         |
+| `memory`               | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }`                               | Measures memory heap size.                   | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                                                                                                                                                                                    |
+| `timings`              | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming)                    | Timing data.                                 | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)                                                                                                                                                           |
+| `timingV2`             | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data.                      | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
+| `resources`            | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)     | Resource timing data.                        | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                                                                                                                                                                    |
+| `firstPaint`           | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)           | Paint timing data.                           | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)                                                                                                                                                                                          |
+| `firstContentfulPaint` | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `FCP`                  | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `LCP`                  | 209                                                                                                                  | Largest Contentful Paint metric.             | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `CLS`                  | 0.001                                                                                                                | Cumulative Layout Shift metric.              | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+|  |
+| `TTFB`                 | 0.03                                                                                                                 | Time to First Byte metric.                   | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `INP`                  | 1.23                                                                                                                 | Interaction to Next Paint metric.            | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `landingPath`          | https://cfrumtest.com/                                                                                               | The landing page URL.                        | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
 
 ## Data processing
 
 RUM data is generally processed at the nearest Cloudflare data center based on how the incoming request is routed. This is determined by a number of factors including [Anycast](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) and [Unimog](https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/). Since RUM data does not use location services, it may be processed in a different country or region from where it originated. Although the RUM service receives the client/source IP address from the beacon as part of normal HTTP request handling process, it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs.
 
-## Privacy information 
+## Privacy information
 
 The RUM beacon script does not store any data in the browser or access any storage data, such as [cookies](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie), [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage), [sessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage), IP address, or [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB). The data we collect is performance data from the browser performance [APIs](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API). This performance data is ephemeral and only relates to the current webpage that is being viewed. If the user refreshes their browser, all the previous performance data is gone and new performance data starts being available. This data is not stored or accessed from anywhere on the device, it is only available as in-memory data.
 
 ## RUM excluding EEA/EU
 
-Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.   
+Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.
 
 Free customers have RUM enabled automatically, with EU traffic excluded, and can switch it off if they prefer. Customers on other plans may enable RUM as needed.
 
@@ -64,5 +63,4 @@ Free customers have RUM enabled automatically, with EU traffic excluded, and can
 
     </div>
 
-
-[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
\ No newline at end of file
+[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
diff --git a/src/content/docs/speed/observatory/run-speed-test.mdx b/src/content/docs/speed/observatory/run-speed-test.mdx
index b86b5c58655a186..5ae182cbf4eb09c 100644
--- a/src/content/docs/speed/observatory/run-speed-test.mdx
+++ b/src/content/docs/speed/observatory/run-speed-test.mdx
@@ -50,20 +50,19 @@ RUM uses a lightweight JavaScript beacon to collect the information Observatory
 Quota limits for the number of tests you can run per month are currently the following:
 
 | Plan       | One-off tests | Recurring tests | Frequency of recurring tests |
-|------------|---------------|-----------------|------------------------------|
+| ---------- | ------------- | --------------- | ---------------------------- |
 | Pro        | 50            | 5               | Daily                        |
 | Business   | 100           | 10              | Daily                        |
 | Enterprise | 150           | 15              | Daily                        |
 
 **Available Regions (all plans):**
 
-| Region                | Region              | Region             |
-|------------------------|---------------------|--------------------|
-| Iowa, USA             | Hamina, Finland     | Changhua County, Taiwan |
-| South Carolina, USA   | Madrid, Spain       | Tokyo, Japan       |
-| North Virginia, USA   | St. Ghislain, Belgium | Osaka, Japan      |
-| Dallas, USA           | Eemshaven, Netherlands | Jurong West, Singapore |
-| Oregon, USA           | Milan, Italy        | Sydney, Australia  |
-| London, England       | Paris, France       | Mumbai, India      |
-| Frankfurt, Germany    | Tel Aviv, Israel    | São Paulo, Brazil  |
-
+| Region              | Region                 | Region                  |
+| ------------------- | ---------------------- | ----------------------- |
+| Iowa, USA           | Hamina, Finland        | Changhua County, Taiwan |
+| South Carolina, USA | Madrid, Spain          | Tokyo, Japan            |
+| North Virginia, USA | St. Ghislain, Belgium  | Osaka, Japan            |
+| Dallas, USA         | Eemshaven, Netherlands | Jurong West, Singapore  |
+| Oregon, USA         | Milan, Italy           | Sydney, Australia       |
+| London, England     | Paris, France          | Mumbai, India           |
+| Frankfurt, Germany  | Tel Aviv, Israel       | São Paulo, Brazil       |
diff --git a/src/content/docs/speed/observatory/test-results.mdx b/src/content/docs/speed/observatory/test-results.mdx
index a9b42c82085bb1a..c6bf699af5e19a6 100644
--- a/src/content/docs/speed/observatory/test-results.mdx
+++ b/src/content/docs/speed/observatory/test-results.mdx
@@ -6,7 +6,6 @@ products:
 title: Understand test results
 sidebar:
   order: 3
-
 ---
 
 The test result page shows you how your website performed regarding several key industry metrics. Some of these metrics are presented for synthetic tests and the real user monitoring, and others only apply to synthetic tests or only to real user monitoring.
@@ -36,19 +35,19 @@ These metrics result from the synthetic tests.
 
 These metrics are collected as part of the real user data, as they require real user interaction with a page.
 
-| Metric                                                  | Definition                                                                                                                                                                       |
-| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page.                                                       |
+| Metric                                                  | Definition                                                                                                                 |
+| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page. |
 
 Refer to [Data and metrics](/web-analytics/data-metrics/) for more information about the metrics you can find in the Real User Monitoring dashboard. You can find details about [Core Web Vitals](/web-analytics/data-metrics/core-web-vitals/), the debug view and the data collected.
 
 ## Network monitoring metrics
 
-| Metric                                            | Definition                                                                                                          |
-| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Wait Time | Measures the time spent waiting for the server to send back the first byte of a response after a request is made.                                           |
-| Load Time | Measures the total time it takes for a web page to fully load in a user’s browser from the network.                                                         |
-| Time to First Byte ([TTFB](https://web.dev/articles/ttfb))  | Measures the duration between initiating a web page request and receiving the first byte from the server. |
-| Server Response Time | Measures the time it takes for a server to respond to a request from a user's browser.                                                           |
-| Connect Time | Measures the time taken to establish a connection between the user's browser and the web server.                                                         | 
-| TLS Time | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.                                                  | 
\ No newline at end of file
+| Metric                                                     | Definition                                                                                                        |
+| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| Wait Time                                                  | Measures the time spent waiting for the server to send back the first byte of a response after a request is made. |
+| Load Time                                                  | Measures the total time it takes for a web page to fully load in a user’s browser from the network.               |
+| Time to First Byte ([TTFB](https://web.dev/articles/ttfb)) | Measures the duration between initiating a web page request and receiving the first byte from the server.         |
+| Server Response Time                                       | Measures the time it takes for a server to respond to a request from a user's browser.                            |
+| Connect Time                                               | Measures the time taken to establish a connection between the user's browser and the web server.                  |
+| TLS Time                                                   | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.       |
diff --git a/src/content/docs/speed/optimization/content/apo.mdx b/src/content/docs/speed/optimization/content/apo.mdx
index bf378bf7685846b..f706bab097e8e8c 100644
--- a/src/content/docs/speed/optimization/content/apo.mdx
+++ b/src/content/docs/speed/optimization/content/apo.mdx
@@ -7,5 +7,4 @@ title: Automatic Platform Optimization
 external_link: /automatic-platform-optimization/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/content/compression.mdx b/src/content/docs/speed/optimization/content/compression.mdx
index 93ad3418e9054de..e021ae803ef2b55 100644
--- a/src/content/docs/speed/optimization/content/compression.mdx
+++ b/src/content/docs/speed/optimization/content/compression.mdx
@@ -22,9 +22,9 @@ Cloudflare compresses content in two ways: between Cloudflare and your website v
 In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.
 
 <Stream
-  id="9103750883217fcb9274666fd57ebac1"
-  title="Content compression"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
+	id="9103750883217fcb9274666fd57ebac1"
+	title="Content compression"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
 />
 
 :::note
diff --git a/src/content/docs/speed/optimization/content/early-hints.mdx b/src/content/docs/speed/optimization/content/early-hints.mdx
index 3263897899e5f21..f40d05197e0f6de 100644
--- a/src/content/docs/speed/optimization/content/early-hints.mdx
+++ b/src/content/docs/speed/optimization/content/early-hints.mdx
@@ -7,5 +7,4 @@ title: Early Hints
 external_link: /cache/advanced-configuration/early-hints/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
index b5627175aec2342..778b154ef43acac 100644
--- a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
+++ b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
@@ -28,7 +28,10 @@ To test that the Fonts feature is working correctly, follow these steps:
 For the feature to work, the response HTML (when the feature is disabled) must include a link tag with `href` pointing to `fonts.googleapis.com`. You can check this on the browser by viewing the source code of the webpage. As an example of what to look for, the following link tag is for the Roboto Google Font:
 
 ```html
-<link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">
+<link
+	href="https://fonts.googleapis.com/css2?family=Roboto&display=swap"
+	rel="stylesheet"
+/>
 ```
 
 If the tag does not exist in the HTML, but you are still sure that your page is using Google Fonts, it might be that your hosting provider is optimizing your Google Fonts on the server. This can prevent Cloudflare Fonts from working properly.
diff --git a/src/content/docs/speed/optimization/content/index.mdx b/src/content/docs/speed/optimization/content/index.mdx
index a778f875d6059cc..e1a5decf41e6b26 100644
--- a/src/content/docs/speed/optimization/content/index.mdx
+++ b/src/content/docs/speed/optimization/content/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
index 148e6cc5d93b485..115046f10c28f12 100644
--- a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
+++ b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
@@ -23,15 +23,13 @@ Rocket Loader will still optimize the loading of all other scripts on the page.
 
 :::note
 
-
 If Rocket Loader is only impacting a specific page, use a [Configuration Rule](/rules/configuration-rules/) to exclude that page by URL.
 
-
 :::
 
 ## Limitations
 
-* Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
-* If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
-* The `data-cfasync` attribute must be added before the `src` attribute.
-* Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
+- Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
+- If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
+- The `data-cfasync` attribute must be added before the `src` attribute.
+- Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
diff --git a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
index 8b56ec1c37765c8..e17a32a6e8a3b82 100644
--- a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
+++ b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
@@ -43,11 +43,11 @@ Shared dictionaries work when all of the following are true:
 
 The protocol uses two new request and response headers and two new content encodings:
 
-| Header                           | Direction        | Purpose                                                                                            |
-| -------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
+| Header                           | Direction        | Purpose                                                                                             |
+| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- |
 | `Use-As-Dictionary`              | Origin → browser | Marks a response as usable as a dictionary for future requests matching the supplied `match` value. |
-| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.           |
-| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).     |
+| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.            |
+| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).      |
 
 The first response for a versioned asset includes `Use-As-Dictionary`, and the browser stores the response. On subsequent requests for assets matching the pattern, the browser sends `Available-Dictionary: :<sha256>:` and adds `dcb, dcz` to `Accept-Encoding`. Your origin compresses the new asset against the dictionary and returns it with `Content-Encoding: dcb` or `dcz`. The browser uses its stored copy to reconstruct the full response.
 
diff --git a/src/content/docs/speed/optimization/content/smart-hints.mdx b/src/content/docs/speed/optimization/content/smart-hints.mdx
index 74a30be29625c81..9df2f2740a81901 100644
--- a/src/content/docs/speed/optimization/content/smart-hints.mdx
+++ b/src/content/docs/speed/optimization/content/smart-hints.mdx
@@ -7,5 +7,4 @@ title: Smart Hints
 external_link: https://blog.cloudflare.com/smart-hints/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/speed/optimization/content/speed-brain.mdx b/src/content/docs/speed/optimization/content/speed-brain.mdx
index e0de7cbfe69f617..979f0002e29fc50 100644
--- a/src/content/docs/speed/optimization/content/speed-brain.mdx
+++ b/src/content/docs/speed/optimization/content/speed-brain.mdx
@@ -10,7 +10,13 @@ sidebar:
 description: Learn how Speed Brain enhances web performance by prefetching likely next pages, improving metrics like LCP and TTFB.
 ---
 
-import { FeatureTable, TabItem, Tabs, APIRequest, DashButton } from "~/components";
+import {
+	FeatureTable,
+	TabItem,
+	Tabs,
+	APIRequest,
+	DashButton,
+} from "~/components";
 
 Speed Brain is a tool for improving web page performance by prefetching the most likely next navigation.
 
@@ -111,7 +117,6 @@ You can also configure Speed Brain using Terraform. For more details, refer to t
 ## Caveats
 
 - Since prefetch responses are not guaranteed to be rendered by the browser, Speed Brain includes two safeguards to minimize the risk of [unsafe prefetching](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#unsafe_prefetching):
-
   - Speed Brain will not prefetch on routes that run Workers. Without this safeguard, prefetch requests could inadvertently run Worker logic that assumes the incoming request is a normal (that is, not a prefetch) request. An example of this could be an incrementing page view counter running in a Worker. A page view counter should not increment if the page is not actually rendered in the browser.
 
   - Prefetch requests will never reach origin servers. Prefetch requests only serve content that is stored in Cloudflare’s Cache. If the content is not in Cache, the prefetch request will not continue to origin servers. Without this safeguard, origin server state could be modified despite the prefetch response not being rendered in the browser. An example of this could be a prefetch `GET` request to a sign-out URL inadvertently triggering a sign-out action on the server.
diff --git a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
index 274ba87dc345bae..e125fcbbe0254bf 100644
--- a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Optimization issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/image-resizing.mdx b/src/content/docs/speed/optimization/images/image-resizing.mdx
index 5e5c8613ef540aa..6594df5754962d0 100644
--- a/src/content/docs/speed/optimization/images/image-resizing.mdx
+++ b/src/content/docs/speed/optimization/images/image-resizing.mdx
@@ -7,5 +7,4 @@ title: Image Resizing
 external_link: /images/optimization/transformations/overview/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/images/index.mdx b/src/content/docs/speed/optimization/images/index.mdx
index d027767b2a3faf5..c079cac0a17b480 100644
--- a/src/content/docs/speed/optimization/images/index.mdx
+++ b/src/content/docs/speed/optimization/images/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/polish.mdx b/src/content/docs/speed/optimization/images/polish.mdx
index c529447865e7b61..631c4cbe263d8c9 100644
--- a/src/content/docs/speed/optimization/images/polish.mdx
+++ b/src/content/docs/speed/optimization/images/polish.mdx
@@ -7,5 +7,4 @@ title: Polish
 external_link: /images/polish/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
index 1f8d029c7d93ae9..cb64aa9539c46b7 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Image issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
index 9ac31a532e60906..fb72840fc7b149a 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
@@ -5,7 +5,6 @@ products:
   - speed
 source: https://support.cloudflare.com/hc/en-us/articles/200168046-Will-Cloudflare-s-image-optimization-features-help-if-I-m-already-optimizing-images-
 title: Image optimization on optimized images
-
 ---
 
 Cloudflare's [image optimization features](/speed/optimization/images/) will likely not help much if you are already optimizing your images in some way (Smush.it, etc.).
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
index 26bdaff52e6866e..ce279de1efcba70 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
@@ -6,5 +6,4 @@ products:
 title: Polish statuses
 external_link: /images/polish/cf-polished-statuses/
 weight: 0
-
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
index ed4e61afdf15934..12268c9dc18cddc 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
@@ -15,9 +15,9 @@ If images are missing from your website, other Cloudflare features may be interf
 To troubleshoot:
 
 1. Perform one of the following actions:
+   - [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
+   - [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
+   - Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 
-   * [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
-   * [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
-   * Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 2. Retest the image load in a private browser tab.
 3. If the issue is not fixed, try another of the actions suggested in Step 1.
diff --git a/src/content/docs/speed/optimization/index.mdx b/src/content/docs/speed/optimization/index.mdx
index bd80c971ba9878a..83b3fba317047d6 100644
--- a/src/content/docs/speed/optimization/index.mdx
+++ b/src/content/docs/speed/optimization/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The Optimization section will show you a list of Cloudflare products that are recommended for enhancing your website's performance.
 
diff --git a/src/content/docs/speed/optimization/measurement.mdx b/src/content/docs/speed/optimization/measurement.mdx
index 016533a4dd1986e..89a7f989f4b71dc 100644
--- a/src/content/docs/speed/optimization/measurement.mdx
+++ b/src/content/docs/speed/optimization/measurement.mdx
@@ -6,7 +6,6 @@ products:
 title: Measurement
 sidebar:
   order: 2
-
 ---
 
 Enable measurement to track your traffic in a privacy-first manner, optimizing your site's speed tools. To access this feature, you need to enable [Web Analytics](/web-analytics/) on your website. This analytics tool leverages [Real User Measurement](/speed/observatory/run-speed-test/#enable-real-user-monitoring-rum) (RUM) data, providing insights based on actual user interactions to enhance site performance effectively.
diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx
index 74d4e0a9ae7f530..13e54b4c22eaedd 100644
--- a/src/content/docs/speed/optimization/protocol/http2.mdx
+++ b/src/content/docs/speed/optimization/protocol/http2.mdx
@@ -56,10 +56,10 @@ The origin web server may be sending improperly formatted HTTP response headers.
 
 #### Resolution
 
-Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements: 
+Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements:
 
 - [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5)
-- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) 
+- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1)
 - [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1)
 
 ### Compression issues
diff --git a/src/content/docs/speed/optimization/protocol/index.mdx b/src/content/docs/speed/optimization/protocol/index.mdx
index fdfe4aa14eb11b1..094dadd43d13cf2 100644
--- a/src/content/docs/speed/optimization/protocol/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
index 45783c25f400853..957822a95ff61cf 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
@@ -4,7 +4,6 @@ description: Fix Enhanced HTTP/2 Prioritization issues on iOS and Safari.
 products:
   - speed
 title: Enhanced HTTP/2 Prioritization negatively affects iOS/Safari devices
-
 ---
 
 Occasionally, [Enhanced HTTP/2 Prioritization](/speed/optimization/protocol/enhanced-http2-prioritization/) can negatively affect the experience of visitors using Safari on macOS or any browser on iOS.
@@ -17,10 +16,8 @@ If visitors using using Safari on macOS or any browser on iOS are experiencing i
 
 :::note
 
-
 Sometimes, [HTTP/2](/speed/optimization/protocol/http2/) will cause **Enhanced HTTP/2 Prioritization** to be re-enabled automatically.
 
 If you notice this happening, also disable **HTTP/2**.
 
-
 :::
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
index 0d6974f96123177..804f216d9cf3f8c 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Protocol optimization issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/recommendations.mdx b/src/content/docs/speed/optimization/recommendations.mdx
index 1367d8efb7789e2..aac4598f71a5531 100644
--- a/src/content/docs/speed/optimization/recommendations.mdx
+++ b/src/content/docs/speed/optimization/recommendations.mdx
@@ -6,7 +6,6 @@ products:
 title: Recommendations
 sidebar:
   order: 1
-
 ---
 
 In the **Recommendations** tab, with one click you can enable all the recommended settings available for your plan. You can enable all the recommended settings at once or you can also just enable the ones you want.
diff --git a/src/content/docs/speed/smart-shield.mdx b/src/content/docs/speed/smart-shield.mdx
index 76f0af22755c9f7..9fc997ea18add10 100644
--- a/src/content/docs/speed/smart-shield.mdx
+++ b/src/content/docs/speed/smart-shield.mdx
@@ -7,5 +7,4 @@ title: Smart Shield
 sidebar:
   order: 4
 external_link: /smart-shield/
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/speed/troubleshooting.mdx b/src/content/docs/speed/troubleshooting.mdx
index 1a73653e90dc280..6f7d78e7f34c259 100644
--- a/src/content/docs/speed/troubleshooting.mdx
+++ b/src/content/docs/speed/troubleshooting.mdx
@@ -7,12 +7,15 @@ title: Troubleshooting
 hideChildren: true
 sidebar:
   order: 20
-
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 The following topics are useful for troubleshooting Speed issues.
 
-<ResourcesBySelector directory="speed" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
-
+<ResourcesBySelector
+	directory="speed"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/ssl/changelog.mdx b/src/content/docs/ssl/changelog.mdx
index c96ac0914a9da7c..96577c758525512 100644
--- a/src/content/docs/ssl/changelog.mdx
+++ b/src/content/docs/ssl/changelog.mdx
@@ -16,7 +16,7 @@ import { ProductChangelog } from "~/components";
 
 ## 2024-10-18
 
-**New cloudflare\_branding flag allows hostnames with over 64 characters for all CAs**
+**New cloudflare_branding flag allows hostnames with over 64 characters for all CAs**
 
 To order certificates for hostnames longer than 64 characters, customers can now use the `cloudflare_branding` flag when ordering a certificate via [API](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/create/). Setting `cloudflare_branding` to `true` will cause `sni.cloudflaressl.com` to be used as the common name, while the long hostname is added as part of the subject alternative name (SAN).
 
@@ -24,4 +24,4 @@ To order certificates for hostnames longer than 64 characters, customers can now
 
 **SSL.com available with ACM and SSL for SaaS**
 
-SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
\ No newline at end of file
+SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
diff --git a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
index fda3782b24250c6..129b0ea9d7b037b 100644
--- a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
@@ -15,4 +15,4 @@ import { Render } from "~/components";
 
 <Render file="add-client-certificate-rfc9440" product="ssl" />
 
-<Render file="forward-client-certificate" product="ssl" />
\ No newline at end of file
+<Render file="forward-client-certificate" product="ssl" />
diff --git a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
index 20bc4a82a73822d..c362c3ea0cbfc69 100644
--- a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
@@ -6,7 +6,6 @@ products:
 title: Revoke a client certificate
 sidebar:
   order: 8
-
 ---
 
 import { DashButton } from "~/components";
@@ -26,10 +25,8 @@ It is not possible to permanently delete client certificates generated with the
 
 :::caution[Important]
 
-
 After revoking a certificate, you must update any mTLS rules that check for the presence of a client certificate so that they block all requests that include a revoked certificate.
 
 For more information, refer to [Check for revoked certificates](/api-shield/security/mtls/configure/#check-for-revoked-certificates).
 
-
 :::
diff --git a/src/content/docs/ssl/concepts.mdx b/src/content/docs/ssl/concepts.mdx
index 2f0333d5ec7c728..074f33eaa264a9e 100644
--- a/src/content/docs/ssl/concepts.mdx
+++ b/src/content/docs/ssl/concepts.mdx
@@ -25,9 +25,9 @@ Since [Cloudflare's global network](https://www.cloudflare.com/network/) is at t
 The [edge certificates](/ssl/edge-certificates/) are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the [Cloudflare Dashboard](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
 
 <Stream
-  id="fe9344af4ab476bf81f4447000f36db66"
-  title="SSL/TLS concepts"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
+	id="fe9344af4ab476bf81f4447000f36db66"
+	title="SSL/TLS concepts"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
 />
 
 ### Origin certificate
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
index 18550b308521f31..c4d44c211b0ec09 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
@@ -30,9 +30,9 @@ If you are a SaaS provider looking to restrict cipher suites for connections to
 
 Custom cipher suites is a hostname-level setting, which implies that:
 
-* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
-* The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
-* If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
+- When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
+- The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
+- If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
 
 ## Scope
 
@@ -50,4 +50,4 @@ This documentation only refers to connections [between clients and the Cloudflar
 
 Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hostname-priority/) to determine which setting to apply.
 
-ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
\ No newline at end of file
+ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
index 7aae1bb58f1bbd9..c8b458d6184c218 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
@@ -16,31 +16,31 @@ tags:
 
 Cloudflare supports the following cipher suites by default. If needed, you can [restrict your website or application](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) to only use specific cipher suites.
 
-| Cipher name | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name |
-| -------------------------------- | ---------------- | ------------------------------------------------------------------------ | ------------ | --------------------------------------------------- |
-| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02b]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256      |
-| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca9]    | TLS\_ECDHE\_ECDSA\_WITH\_CHACHA20\_POLY1305\_SHA256 |
-| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02f]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256        |
-| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca8]    | TLS\_ECDHE\_RSA\_WITH\_CHACHA20\_POLY1305\_SHA256   |
-| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc023]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256      |
-| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                   | \[0xc009]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA         |
-| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc027]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256        |
-| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc013]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA           |
-| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                   | \[0x9c]      | TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256               |
-| AES128-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3c]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256               |
-| AES128-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x2f]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA                  |
-| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02c]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384      |
-| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc024]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384      |
-| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc030]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384        |
-| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc028]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384        |
-| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc014]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA           |
-| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                   | \[0x9d]      | TLS\_RSA\_WITH\_AES\_256\_GCM\_SHA384               |
-| AES256-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3d]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256               |
-| AES256-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x35]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA                  |
-| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                   | \[0x0a]      | TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA                 |
-| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x01}  | TLS\_AES\_128\_GCM\_SHA256                          |
-| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x02}  | TLS\_AES\_256\_GCM\_SHA384                          |
-| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x03}  | TLS\_CHACHA20\_POLY1305\_SHA256                     |
+| Cipher name                      | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name                                     |
+| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------- |
+| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02b]    | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256       |
+| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca9]    | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 |
+| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02f]    | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256         |
+| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca8]    | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   |
+| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc023]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256       |
+| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                                              | \[0xc009]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA          |
+| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc027]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256         |
+| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc013]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA            |
+| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                                              | \[0x9c]      | TLS_RSA_WITH_AES_128_GCM_SHA256               |
+| AES128-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3c]      | TLS_RSA_WITH_AES_128_CBC_SHA256               |
+| AES128-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x2f]      | TLS_RSA_WITH_AES_128_CBC_SHA                  |
+| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02c]    | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384       |
+| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc024]    | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384       |
+| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc030]    | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384         |
+| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc028]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384         |
+| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc014]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA            |
+| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                                              | \[0x9d]      | TLS_RSA_WITH_AES_256_GCM_SHA384               |
+| AES256-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3d]      | TLS_RSA_WITH_AES_256_CBC_SHA256               |
+| AES256-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x35]      | TLS_RSA_WITH_AES_256_CBC_SHA                  |
+| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                                              | \[0x0a]      | TLS_RSA_WITH_3DES_EDE_CBC_SHA                 |
+| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x01} | TLS_AES_128_GCM_SHA256                        |
+| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x02} | TLS_AES_256_GCM_SHA384                        |
+| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x03} | TLS_CHACHA20_POLY1305_SHA256                  |
 
 :::note[* TLS 1.3 minimum protocol]
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
index 33d50ea3a037245..186ef035f3bc82f 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Once you set up SSL/TLS on your application, you can adjust the following settings on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page:
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
index cb0cd6575e94980..c5f7c351636e7ea 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
@@ -8,7 +8,14 @@ sidebar:
   order: 13
 ---
 
-import { FeatureTable, TabItem, Tabs, APIRequest, Render, DashButton } from "~/components";
+import {
+	FeatureTable,
+	TabItem,
+	Tabs,
+	APIRequest,
+	Render,
+	DashButton,
+} from "~/components";
 
 Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer.
 
@@ -86,13 +93,13 @@ Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hos
 In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and authentication placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
 <APIRequest
-  path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
-  method="PUT"
-  json={{
-		"value": "1.2"
+	path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
+	method="PUT"
+	json={{
+		value: "1.2",
 	}}
 	parameters={{
-		setting_id: "min_tls_version"
+		setting_id: "min_tls_version",
 	}}
 />
 
@@ -100,7 +107,6 @@ In the following example, the minimum TLS version for a specific hostname will b
 
 If you are a SaaS provider looking to configure minimum TLS version for your custom hostnames, refer to the Cloudflare for SaaS [TLS management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version).
 
-
 ## Test supported TLS versions
 
-<Render file="test-tls-version" product="ssl" />
\ No newline at end of file
+<Render file="test-tls-version" product="ssl" />
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
index 0e4362cf11468cb..f302408667237f8 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
@@ -10,7 +10,14 @@ tags:
   - TLS
 ---
 
-import { Details, FeatureTable, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	Details,
+	FeatureTable,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 TLS 1.3 enables the latest version of the TLS protocol (when supported) for improved security and performance.
 
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
index 4a643427148e0dc..9de3f9a1b2d4d87 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
@@ -6,19 +6,15 @@ products:
 title: API commands
 sidebar:
   order: 5
-
 ---
 
 Use the following API commands to manage advanced certificates. If you are using our API for the first time, review our [API documentation](/fundamentals/api/).
 
-
-
-| Command                                                                                                                                                 | Method   | Endpoint                                             | Additional notes                                                                            |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                     | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
-| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                                                                             |
-| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                       | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
+| Command                                                                                                                                                        | Method   | Endpoint                                             | Additional notes                                                                            |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                                                | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
+| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                                                              | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                  |
+| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                                                   | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
 | [List certificate packs in a zone](/api/resources/ssl/subresources/certificate_packs/methods/list/)                                                            | `GET`    | `zones/<<ZONE_ID>>/ssl/certificate_packs?status=all` | This API call returns all certificate packs for a domain (Universal, Custom, and Advanced). |
 | List Cipher Suite settings: [Get zone setting](/api/resources/zones/subresources/settings/methods/get/) with `ciphers` as the setting name in the URI path     | `GET`    | `zones/<<ZONE_ID>>/settings/ciphers`                 |                                                                                             |
 | Change Cipher Suite settings: [Edit zone setting](/api/resources/zones/subresources/settings/methods/edit/) with `ciphers` as the setting name in the URI path | `PATCH`  | `zones/<<ZONE_ID>>/settings/ciphers`                 | To restore default settings, send a blank array in the `value` parameter.                   |
-
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
index 8bb9170bb3e5e55..6261626f47813e8 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
@@ -10,7 +10,13 @@ description: Learn how to create, delete and perform other operations to manage
   your Cloudflare Advanced SSL certificates.
 ---
 
-import { AvailableNotifications, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	AvailableNotifications,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 ## Create a certificate
 
diff --git a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
index cd1a9df4c9a9acd..9612b1b4e300149 100644
--- a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
@@ -6,10 +6,9 @@ products:
 title: Backup certificates
 sidebar:
   order: 9
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 If Cloudflare is providing [authoritative DNS](/dns/zone-setups/full-setup/) for your domain, Cloudflare will issue a backup [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for every standard Universal certificate issued.
 
diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx
index 81472be5e1532d4..d8baa4eef05cff2 100644
--- a/src/content/docs/ssl/edge-certificates/caa-records.mdx
+++ b/src/content/docs/ssl/edge-certificates/caa-records.mdx
@@ -77,4 +77,3 @@ Check CAA at all levels of your CNAME chain:
 dig yourdomain.com CAA +short
 dig cname-target.com CAA +short
 ```
-
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
index cc1c3b4df79dbed..96fb56d94da1db3 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
@@ -6,7 +6,6 @@ products:
 title: Bundle methodologies
 sidebar:
   order: 4
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -43,4 +42,4 @@ The related value for the `bundle_method` parameter when using the [API](/api/re
 
 User-defined allows you to paste your own certificate chain and present that bundle to clients. If you are using a self-signed certificate (not recommended), you must use this mode.
 
-The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
\ No newline at end of file
+The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
index b6e2aa56fcc596a..450b178703c442c 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
@@ -8,10 +8,9 @@ sidebar:
 head: []
 description: Learn how renewal and expiration work when using Cloudflare Custom
   SSL certificates.
-
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components";
 
 ## Renew custom certificates
 
diff --git a/src/content/docs/ssl/edge-certificates/ech.mdx b/src/content/docs/ssl/edge-certificates/ech.mdx
index 0fbfdfc7d498d82..f41c594d329fe41 100644
--- a/src/content/docs/ssl/edge-certificates/ech.mdx
+++ b/src/content/docs/ssl/edge-certificates/ech.mdx
@@ -35,7 +35,7 @@ In practice, this means that any intermediary that is looking at your traffic wi
 
 In the example below, a user is visiting `example.com`. Without ECH, any intermediate networks will be able to detect the website being accessed by the user. With ECH, the visible information will be limited to `cloudflare-ech.com` instead.
 
-<br/>
+<br />
 
 ```mermaid
 flowchart LR
@@ -46,7 +46,7 @@ A(User visits <code>example.com</code>)
     A -- Without ECH  --> D(intermediaries see <code>example.com</code>)-->B(Cloudflare)
 ```
 
-<br/>
+<br />
 
 For more details about ECH protocol technology, refer to our [introductory blog](https://blog.cloudflare.com/encrypted-client-hello/).
 
diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
index 1f5ef82895c17f4..01b85e22786233d 100644
--- a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
+++ b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
@@ -31,7 +31,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 | WEUR        | Western Europe        |
 | WNAM        | Western North America |
 
-***
+---
 
 ## Available countries
 
@@ -39,7 +39,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 
 Examples of supported countries are Japan, Canada, India, and Australia.
 
-***
+---
 
 ## Highest security data centers
 
diff --git a/src/content/docs/ssl/edge-certificates/index.mdx b/src/content/docs/ssl/edge-certificates/index.mdx
index ffb763f9a56da56..e7cf9b2a13c1a4d 100644
--- a/src/content/docs/ssl/edge-certificates/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/index.mdx
@@ -22,7 +22,7 @@ This behavior occurs when all of the following conditions are true:
 
 - The zone is on a [subdomain setup](/dns/zone-setups/subdomain-setup/).
 - The certificate has a subject or SAN that is a wildcard for the zone's parent domain.
-:::
+  :::
 
 ## Use cases
 
diff --git a/src/content/docs/ssl/edge-certificates/staging-environment.mdx b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
index 339031829e8da8c..19eb3fbbdf32035 100644
--- a/src/content/docs/ssl/edge-certificates/staging-environment.mdx
+++ b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
@@ -8,22 +8,21 @@ sidebar:
   order: 8
   badge:
     text: Beta
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Use your certificate staging environment to test new custom (modern) certificates before pushing them to your production environment. This process helps you solve potential certificate problems **before** there's an incident, such as when:
 
-* You make a mistake when uploading a new custom certificate.
-* You misunderstand the order of your certificates.
-* Clients have previously pinned your custom certificate, causing a TLS termination error.
+- You make a mistake when uploading a new custom certificate.
+- You misunderstand the order of your certificates.
+- Clients have previously pinned your custom certificate, causing a TLS termination error.
 
 ## Availability
 
 <FeatureTable id="ssl.staging_environment" />
 
-***
+---
 
 ## Use your staging environment
 
@@ -49,9 +48,9 @@ curl --resolve <HOSTNAME>:<PORT>:<STAGING_IP> https://<HOSTNAME> -iv
 
 You should confirm whether:
 
-* TLS termination is successful.
-* The right certificate is being served at the edge.
-* Any clients are pinning the old certificate.
+- TLS termination is successful.
+- The right certificate is being served at the edge.
+- Any clients are pinning the old certificate.
 
 ### 3. Push certificate to production
 
@@ -78,7 +77,7 @@ If you roll out a custom (modern) certificate to production and encounter issues
 3. Select **Deactivate**.
 4. Select **Push to Staging**.
 
-***
+---
 
 ## Limitations
 
@@ -90,5 +89,5 @@ Currently, staging environments are only available to Enterprise customers parti
 
 At the moment, staging environments have limited functionality:
 
-* Only custom (modern) certificates
-* Only accessed via the dashboard
+- Only custom (modern) certificates
+- Only accessed via the dashboard
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
index 3104afffd410349..70ebac7297e8244 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
@@ -9,13 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Universal SSL
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your certificates.
 
-<AvailableNotifications product="SSL/TLS" notificationFilter="Universal SSL Alert" />
+<AvailableNotifications
+	product="SSL/TLS"
+	notificationFilter="Universal SSL Alert"
+/>
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
index b594fc5113be2e0..818182201a137ed 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
@@ -25,13 +25,11 @@ To avoid errors with your domain, either [upload a custom certificate](/ssl/edge
 If you disable Universal SSL, you may experience errors with the following scenarios:
 
 - **Enabled features**:
-
   - [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/)
   - [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/)
   - [Opportunistic Encryption](/ssl/edge-certificates/additional-options/opportunistic-encryption/)
 
 - **Other setups**:
-
   - [Page Rules](/rules/page-rules/) that redirect traffic to HTTPS
   - HTTP to HTTPS redirects at your origin web server
 
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
index 9caba32b58ee4c2..e18e34ce743050c 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
@@ -17,10 +17,10 @@ If a certificate issuance times out, Cloudflare tells you where in the chain of
 
 To resolve timeout issues, try one or more of the following options:
 
-* Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
-* [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
-* Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
-* Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
+- Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
+- [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
+- Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
+- Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
 
 ## Delete certificates
 
diff --git a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
index f525157d8b998f3..08f0a67ed984db2 100644
--- a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with Keyless SSL
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The way you set up Keyless SSL depends on how you route traffic to your keyless server.
 
diff --git a/src/content/docs/ssl/keyless-ssl/glossary.mdx b/src/content/docs/ssl/keyless-ssl/glossary.mdx
index e64a45f3d972083..ac939b4a2946953 100644
--- a/src/content/docs/ssl/keyless-ssl/glossary.mdx
+++ b/src/content/docs/ssl/keyless-ssl/glossary.mdx
@@ -9,7 +9,6 @@ head:
   - tag: title
     content: Glossary | Keyless SSL
 description: Learn more about the common terms related to Keyless SSL.
-
 ---
 
 ## Cloudflare Keyless SSL key server (“key server”)
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
index 0ca6a0fe976beb8..3804977bcd01432 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
@@ -69,7 +69,6 @@ brew install azure-cli
    ```
 
 4. If the key server is running in an Azure VM in the same account, use **Managed services** for authorization:
-
    1. Enable managed services on the VM in the UI.
    2. Give your service user (associated with your VM) HSM sign permissions
 
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
index df9caf0b486ccaf..18a3cbbad52b8b7 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
@@ -14,4 +14,4 @@ You can use Cloudflare Keyless SSL with [Fortanix Data Security Manager (DSM)](h
 
 You must have a [Data Security Manager Enterprise Tier](https://www.fortanix.com/start-your-free-trial) and set up a group and an application assigned to the group.
 
-For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
\ No newline at end of file
+For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
index fd448a9791cb833..a28200144687ee8 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
@@ -6,12 +6,11 @@ products:
 title: Hardware security modules
 sidebar:
   order: 2
-
 ---
 
 In addition to private keys stored on disk, Keyless SSL supports keys stored in a Hardware Security Module (HSM) via the PKCS#11 standard. Keyless uses PKCS#11 for signing and decrypting payloads without having direct access to the private keys.
 
-***
+---
 
 ## Why use Keyless SSL with an HSM?
 
@@ -19,7 +18,7 @@ Hardware Security Modules (HSMs) facilitate a higher level of protection for you
 
 Moreover, many HSMs are also capable of generating keys and producing cryptographically secure randomness. Some are purpose-built to perform cryptographic computations more efficiently.
 
-***
+---
 
 ## Communicating using PKCS#11
 
@@ -45,4 +44,4 @@ Also, the following cloud HSM offerings have been tested with Keyless SSL:
 - [Azure Managed HSM](/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm/)
 - [Fortanix DSM](/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm/)
 - [IBM Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/ibm-cloud-hsm/)
-- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
\ No newline at end of file
+- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
diff --git a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
index 459196f2dd78e7d..f2176ee72e743cd 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
@@ -6,7 +6,6 @@ products:
 title: High availability
 sidebar:
   order: 3
-
 ---
 
 The Cloudflare Keyless SSL server runs as a single binary with minimal dependencies and is designed to be robust and reliable. However, the network between your key server and Cloudflare may not be, which could prevent new TLS connections.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/index.mdx b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
index 4c22ae751c29b2c..78c6fba61f6ed5e 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Reference — Keyless SSL
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information on Keyless SSL, refer to the following resources:
 
diff --git a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
index 08105e84ad0afe6..b0c023f66fe907a 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
@@ -8,7 +8,6 @@ tags:
   - TLS
 sidebar:
   order: 7
-
 ---
 
 Keyless Delegation is Cloudflare's implementation of the emerging delegated credentials standard ([RFC 9345](https://www.rfc-editor.org/rfc/rfc9345.html)). When you upload a certificate for use with Keyless that has the special extension permitting the use of delegated credentials, Cloudflare will automatically produce a delegated credential and use it at the edge with clients that support this feature. The handshakes will complete without the extra latency induced by reaching back to the Keyless Server, and there are [additional advantages to flexibility in algorithm choice](https://blog.cloudflare.com/keyless-delegation/).
diff --git a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
index 0e9d1a59aa73910..292a3c66bcec5c5 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
@@ -6,13 +6,10 @@ products:
 title: Key server metrics
 sidebar:
   order: 5
-
 ---
 
 The gokeyless key server exposes a [Prometheus](https://prometheus.io/) metrics endpoint that you can use to monitor signing performance, error rates, connection health, and certificate expiry. This endpoint can also be scraped by the OpenTelemetry Collector Prometheus receiver, making the metrics available to any OpenTelemetry-compatible backend.
 
-
-
 ## Metrics endpoint
 
 By default, metrics are served at:
@@ -31,24 +28,24 @@ The endpoint serves only `/metrics`. There are no additional HTTP endpoints such
 
 All histogram metrics share the same bucket configuration: 15 exponential buckets starting at 100 microseconds, doubling each step up to approximately 1.64 seconds, plus a final `+Inf` bucket.
 
-| Bucket | Upper bound |
-| --- | --- |
-| 1 | 100 µs |
-| 2 | 200 µs |
-| 3 | 400 µs |
-| 4 | 800 µs |
-| 5 | 1.6 ms |
-| 6 | 3.2 ms |
-| 7 | 6.4 ms |
-| 8 | 12.8 ms |
-| 9 | 25.6 ms |
-| 10 | 51.2 ms |
-| 11 | 102 ms |
-| 12 | 205 ms |
-| 13 | 410 ms |
-| 14 | 819 ms |
-| 15 | ~1.64 s |
-| +Inf | Anything above ~1.64 s |
+| Bucket | Upper bound            |
+| ------ | ---------------------- |
+| 1      | 100 µs                 |
+| 2      | 200 µs                 |
+| 3      | 400 µs                 |
+| 4      | 800 µs                 |
+| 5      | 1.6 ms                 |
+| 6      | 3.2 ms                 |
+| 7      | 6.4 ms                 |
+| 8      | 12.8 ms                |
+| 9      | 25.6 ms                |
+| 10     | 51.2 ms                |
+| 11     | 102 ms                 |
+| 12     | 205 ms                 |
+| 13     | 410 ms                 |
+| 14     | 819 ms                 |
+| 15     | ~1.64 s                |
+| +Inf   | Anything above ~1.64 s |
 
 :::note
 When using a hardware security module (HSM) with a PKCS#11 session pool, the pool wait timeout is hardcoded at 10 seconds. A pool exhaustion event will therefore always appear in the `+Inf` bucket. Spikes in `+Inf` observations on signing operations with `error="cryptography error"` are a direct indicator of PKCS#11 session pool saturation.
@@ -69,45 +66,45 @@ The `opcode` label uses the full constant name from the gokeyless protocol.
 
 #### RSA operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpRSADecrypt` | `0x01` | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3) |
-| `OpRSASignMD5SHA1` | `0x02` | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
-| `OpRSASignSHA1` | `0x03` | RSA PKCS#1 v1.5 signature over SHA1 |
-| `OpRSASignSHA224` | `0x04` | RSA PKCS#1 v1.5 signature over SHA224 |
-| `OpRSASignSHA256` | `0x05` | RSA PKCS#1 v1.5 signature over SHA256 |
-| `OpRSASignSHA384` | `0x06` | RSA PKCS#1 v1.5 signature over SHA384 |
-| `OpRSASignSHA512` | `0x07` | RSA PKCS#1 v1.5 signature over SHA512 |
-| `OpRSAPSSSignSHA256` | `0x35` | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3 |
-| `OpRSAPSSSignSHA384` | `0x36` | RSASSA-PSS signature over SHA384 |
-| `OpRSAPSSSignSHA512` | `0x37` | RSASSA-PSS signature over SHA512 |
+| `opcode` label       | Wire value | Description                                                                   |
+| -------------------- | ---------- | ----------------------------------------------------------------------------- |
+| `OpRSADecrypt`       | `0x01`     | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3)     |
+| `OpRSASignMD5SHA1`   | `0x02`     | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
+| `OpRSASignSHA1`      | `0x03`     | RSA PKCS#1 v1.5 signature over SHA1                                           |
+| `OpRSASignSHA224`    | `0x04`     | RSA PKCS#1 v1.5 signature over SHA224                                         |
+| `OpRSASignSHA256`    | `0x05`     | RSA PKCS#1 v1.5 signature over SHA256                                         |
+| `OpRSASignSHA384`    | `0x06`     | RSA PKCS#1 v1.5 signature over SHA384                                         |
+| `OpRSASignSHA512`    | `0x07`     | RSA PKCS#1 v1.5 signature over SHA512                                         |
+| `OpRSAPSSSignSHA256` | `0x35`     | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3           |
+| `OpRSAPSSSignSHA384` | `0x36`     | RSASSA-PSS signature over SHA384                                              |
+| `OpRSAPSSSignSHA512` | `0x37`     | RSASSA-PSS signature over SHA512                                              |
 
 #### ECDSA operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpECDSASignMD5SHA1` | `0x12` | ECDSA signature over MD5+SHA1 combined hash |
-| `OpECDSASignSHA1` | `0x13` | ECDSA signature over SHA1 |
-| `OpECDSASignSHA224` | `0x14` | ECDSA signature over SHA224 |
-| `OpECDSASignSHA256` | `0x15` | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
-| `OpECDSASignSHA384` | `0x16` | ECDSA signature over SHA384 |
-| `OpECDSASignSHA512` | `0x17` | ECDSA signature over SHA512 |
+| `opcode` label       | Wire value | Description                                                      |
+| -------------------- | ---------- | ---------------------------------------------------------------- |
+| `OpECDSASignMD5SHA1` | `0x12`     | ECDSA signature over MD5+SHA1 combined hash                      |
+| `OpECDSASignSHA1`    | `0x13`     | ECDSA signature over SHA1                                        |
+| `OpECDSASignSHA224`  | `0x14`     | ECDSA signature over SHA224                                      |
+| `OpECDSASignSHA256`  | `0x15`     | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
+| `OpECDSASignSHA384`  | `0x16`     | ECDSA signature over SHA384                                      |
+| `OpECDSASignSHA512`  | `0x17`     | ECDSA signature over SHA512                                      |
 
 #### Other signing
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpEd25519Sign` | `0x18` | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
+| `opcode` label  | Wire value | Description                                                                  |
+| --------------- | ---------- | ---------------------------------------------------------------------------- |
+| `OpEd25519Sign` | `0x18`     | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
 
 #### Sealing and infrastructure operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpSeal` | `0x21` | Encrypt a blob using the server's sealing key — used for TLS session tickets |
-| `OpUnseal` | `0x22` | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated |
-| `OpRPC` | `0x23` | Execute a named function registered on the server. Available to all connection types |
-| `OpCustom` | `0x24` | Execute a custom function set in the server configuration. Available to unrestricted connections only |
-| `OpPing` | `0xF1` | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved |
+| `opcode` label | Wire value | Description                                                                                           |
+| -------------- | ---------- | ----------------------------------------------------------------------------------------------------- |
+| `OpSeal`       | `0x21`     | Encrypt a blob using the server's sealing key — used for TLS session tickets                          |
+| `OpUnseal`     | `0x22`     | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated  |
+| `OpRPC`        | `0x23`     | Execute a named function registered on the server. Available to all connection types                  |
+| `OpCustom`     | `0x24`     | Execute a custom function set in the server configuration. Available to unrestricted connections only |
+| `OpPing`       | `0xF1`     | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved      |
 
 ---
 
@@ -124,15 +121,15 @@ This metric does not include time a request spends waiting for a connection sema
 
 Opcodes are grouped into coarser categories for this label:
 
-| `type` label | Opcodes included |
-| --- | --- |
-| `rsa` | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*` |
-| `ecdsa` | All `OpECDSASign*` |
-| `ed25519` | `OpEd25519Sign` |
-| `rpc` | `OpRPC` |
-| `custom` | `OpCustom` |
-| `other` | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
-| `unknown` | Any unrecognised opcode byte |
+| `type` label | Opcodes included                                                  |
+| ------------ | ----------------------------------------------------------------- |
+| `rsa`        | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*`             |
+| `ecdsa`      | All `OpECDSASign*`                                                |
+| `ed25519`    | `OpEd25519Sign`                                                   |
+| `rpc`        | `OpRPC`                                                           |
+| `custom`     | `OpCustom`                                                        |
+| `other`      | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
+| `unknown`    | Any unrecognised opcode byte                                      |
 
 :::note
 `OpPing` is grouped into `other` alongside `OpSeal` and `OpUnseal`. Ping round-trip latency cannot be separated from seal and unseal operation latency in this metric.
@@ -142,20 +139,20 @@ Opcodes are grouped into coarser categories for this label:
 
 For successful requests the value is `no error`. All other values indicate a failed operation.
 
-| `error` label | Description | Common cause |
-| --- | --- | --- |
-| `no error` | Operation completed successfully | — |
-| `cryptography error` | HSM or signing operation failed | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
-| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result | Key not loaded in keystore, incorrect SKI in request |
-| `read failure` | I/O read error during the operation | Disk error reading key file |
-| `version mismatch` | Protocol version not supported | Client and server version skew |
-| `bad opcode` | Unknown opcode received | `OpCustom` sent with no custom handler configured |
-| `unexpected opcode` | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request |
-| `malformed message` | TLV parse failure | Corrupt or truncated packet |
-| `internal error` | Non-cryptographic server-side failure | Sealer is nil, RPC dispatch error |
-| `certificate not found` | Certificate lookup failed | Certificate not loaded |
-| `sealing key expired` | `OpUnseal` blob is too old to decrypt | TLS session ticket key rotation — blob sealed with a key that has since been retired |
-| `remote configuration error` | Remote key server is misconfigured | Key points to an unreachable or misconfigured remote key server |
+| `error` label                                       | Description                             | Common cause                                                                                          |
+| --------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `no error`                                          | Operation completed successfully        | —                                                                                                     |
+| `cryptography error`                                | HSM or signing operation failed         | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
+| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result           | Key not loaded in keystore, incorrect SKI in request                                                  |
+| `read failure`                                      | I/O read error during the operation     | Disk error reading key file                                                                           |
+| `version mismatch`                                  | Protocol version not supported          | Client and server version skew                                                                        |
+| `bad opcode`                                        | Unknown opcode received                 | `OpCustom` sent with no custom handler configured                                                     |
+| `unexpected opcode`                                 | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request                                         |
+| `malformed message`                                 | TLV parse failure                       | Corrupt or truncated packet                                                                           |
+| `internal error`                                    | Non-cryptographic server-side failure   | Sealer is nil, RPC dispatch error                                                                     |
+| `certificate not found`                             | Certificate lookup failed               | Certificate not loaded                                                                                |
+| `sealing key expired`                               | `OpUnseal` blob is too old to decrypt   | TLS session ticket key rotation — blob sealed with a key that has since been retired                  |
+| `remote configuration error`                        | Remote key server is misconfigured      | Key points to an unreachable or misconfigured remote key server                                       |
 
 ---
 
@@ -197,16 +194,16 @@ It is **not** recorded for `OpPing`, `OpSeal`, `OpUnseal`, `OpRPC`, or `OpCustom
 
 Counts connection-level transport failures. This metric reflects problems at the network or TLS layer — it does not count signing errors or key lookup failures, which are reported in the `error` label of the duration histograms.
 
-| Scenario | Counted? |
-| --- | --- |
-| TLS handshake failure | No |
-| Client disconnected before TLS handshake (EOF) | No |
-| Failure determining connection trust level after TLS | Yes |
-| Non-EOF read error on an established connection | Yes |
-| Write error when delivering a response | Yes |
-| Read timeout — graceful connection drain | No |
-| Signing error, including PKCS#11 pool timeout | No |
-| Key not found | No |
+| Scenario                                             | Counted? |
+| ---------------------------------------------------- | -------- |
+| TLS handshake failure                                | No       |
+| Client disconnected before TLS handshake (EOF)       | No       |
+| Failure determining connection trust level after TLS | Yes      |
+| Non-EOF read error on an established connection      | Yes      |
+| Write error when delivering a response               | Yes      |
+| Read timeout — graceful connection drain             | No       |
+| Signing error, including PKCS#11 pool timeout        | No       |
+| Key not found                                        | No       |
 
 ---
 
@@ -218,18 +215,19 @@ Counts connection-level transport failures. This metric reflects problems at the
 Reports the expiration time (`NotAfter`) of each certificate loaded by the key server as a Unix timestamp. One time series is emitted per certificate.
 
 This metric is updated:
+
 - At startup, for the server authentication certificate (`auth_cert`) and the Cloudflare CA certificate (`cloudflare_ca_cert`).
 - On each successful inbound TLS connection, for the peer certificates presented by the connecting client.
 
-| Label | Description |
-| --- | --- |
-| `source` | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
-| `serial_no` | Certificate serial number |
-| `cn` | Subject Common Name |
-| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names |
-| `ca` | `1` if the certificate is a CA certificate, `0` otherwise |
-| `server` | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise |
-| `client` | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise |
+| Label       | Description                                                                              |
+| ----------- | ---------------------------------------------------------------------------------------- |
+| `source`    | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
+| `serial_no` | Certificate serial number                                                                |
+| `cn`        | Subject Common Name                                                                      |
+| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names                            |
+| `ca`        | `1` if the certificate is a CA certificate, `0` otherwise                                |
+| `server`    | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise                   |
+| `client`    | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise                   |
 
 :::note
 `server_utilization` is a registered `GaugeVec` metric that is never written to by the key server. Because no label values are ever set, it emits no time series in the `/metrics` output at all. Do not use it.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
index 22b7833a2be107e..4edb4db09bab546 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
@@ -6,7 +6,6 @@ products:
 title: Scaling and benchmarking
 sidebar:
   order: 4
-
 ---
 
 Cloudflare's Keyless SSL technology was designed to scale to accommodate any sized workload using vertical and horizontal scaling, and pre-computation techniques wherever possible, such as ECDSA. The goals of the architectural design of the key server are to minimize latency while maximizing signing operations per second.
@@ -15,7 +14,7 @@ Each key server uses a worker pool model, with incoming client connections handl
 
 Where needed, multiple key servers can be deployed and balanced between using your preferred ingress load balancing configuration. For full high availability, make sure to deploy sufficient key servers to handle twice the expected workload.
 
-***
+---
 
 ## Key type
 
@@ -25,7 +24,7 @@ ECDSA signing can be broken down into two steps. Since the first step — genera
 
 Additional details can be found in the [gokeyless server readme file](https://github.com/cloudflare/gokeyless#readme) file.
 
-***
+---
 
 ## Benchmarks
 
diff --git a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
index 4f8047f3f0bc964..725673be1dbd8c2 100644
--- a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
+++ b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
@@ -6,7 +6,6 @@ products:
 title: Upgrade your key server
 sidebar:
   order: 4
-
 ---
 
 Periodically, you may need to update your key server when using Cloudflare's Keyless SSL.
@@ -25,8 +24,6 @@ To upgrade your key server:
 
 :::caution
 
-
 If you are running a [high availability configuration](/ssl/keyless-ssl/reference/high-availability/), upgrade one server at a time as new TLS connections will fail to terminate at Cloudflare's global network without a functioning key server.
 
-
 :::
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
index c8ca40f070b5e2a..bda18f6939d8966 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
@@ -24,10 +24,9 @@ Global, [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/
 - Make sure your zone is using an [SSL/TLS encryption mode](/ssl/origin-configuration/ssl-modes/) of **Full** or higher.
 
 - Consider your security and certificate needs:
+  - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
 
-   - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
-
-   - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
+  - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
 
 ## 1. Download the Cloudflare certificate
 
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
index d2d6befaa600c0d..5ab7622aa6b0069 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Set up Authenticated Origin Pulls
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
index 051fcf061c534ca..8a042656568dd34 100644
--- a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
+++ b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
@@ -28,19 +28,19 @@ The list order is based on how the cipher suites appear in the [ClientHello](htt
 
 | Cipher name                        | TLS 1.0 | TLS 1.1 | TLS 1.2 | TLS 1.3 |
 | ---------------------------------- | ------- | ------- | ------- | ------- |
-| AEAD-AES128-GCM-SHA256 [^1]        | ❌       | ❌       | ❌       | ✅       |
-| AEAD-AES256-GCM-SHA384 [^1]        | ❌       | ❌       | ❌       | ✅       |
-| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌       | ❌       | ❌       | ✅       |
-| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES128-GCM-SHA256        | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES128-SHA               | ✅       | ✅       | ✅       | ❌       |
-| AES128-GCM-SHA256                  | ❌       | ❌       | ✅       | ❌       |
-| AES128-SHA                         | ✅       | ✅       | ✅       | ❌       |
-| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES256-GCM-SHA384        | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES256-SHA384            | ❌       | ❌       | ✅       | ❌       |
-| AES256-SHA                         | ✅       | ✅       | ✅       | ❌       |
-| DES-CBC3-SHA                       | ✅       | ❌       | ❌       | ❌       |
+| AEAD-AES128-GCM-SHA256 [^1]        | ❌      | ❌      | ❌      | ✅      |
+| AEAD-AES256-GCM-SHA384 [^1]        | ❌      | ❌      | ❌      | ✅      |
+| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌      | ❌      | ❌      | ✅      |
+| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES128-GCM-SHA256        | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES128-SHA               | ✅      | ✅      | ✅      | ❌      |
+| AES128-GCM-SHA256                  | ❌      | ❌      | ✅      | ❌      |
+| AES128-SHA                         | ✅      | ✅      | ✅      | ❌      |
+| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES256-GCM-SHA384        | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES256-SHA384            | ❌      | ❌      | ✅      | ❌      |
+| AES256-SHA                         | ✅      | ✅      | ✅      | ❌      |
+| DES-CBC3-SHA                       | ✅      | ❌      | ❌      | ❌      |
 
 ### TLS 1.3 cipher suites
 
@@ -67,4 +67,4 @@ ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RS
 ssl_prefer_server_ciphers on;
 ```
 
-[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
\ No newline at end of file
+[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
diff --git a/src/content/docs/ssl/origin-configuration/index.mdx b/src/content/docs/ssl/origin-configuration/index.mdx
index aac15f2f4132e15..ca68ac364da293b 100644
--- a/src/content/docs/ssl/origin-configuration/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn more about SSL/TLS protection options for your origin servers:
 
diff --git a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
index b417523729d50b6..6669b3202cadc81 100644
--- a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
+++ b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
@@ -64,7 +64,7 @@ If the user does not have **API Access**, this error is returned.
 
 Make sure that the user creating the certificate has access to the API. You can check in the account **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+<DashButton url="/?to=/:account/members" />
 
 - The default setting for the account is specified in the card **Enable API Access**.
 - Specific user API Access (which can override the default setting) is presented after selecting the user in the list of members.
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
index 087e14efa75240d..c19aaa19e4e96d1 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
@@ -16,9 +16,9 @@ import { Stream, Render, TabItem, Tabs } from "~/components";
 When you set your encryption mode to **Full**, Cloudflare allows HTTPS connections between your visitor and Cloudflare and makes connections to the origin using the scheme requested by the visitor. If your visitor uses `http`, then Cloudflare connects to the origin using plaintext HTTP and vice versa.
 
 <Stream
-  id="a1e79096a2b042e0525a8543c232279a"
-  title="Configure Full encryption mode"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
+	id="a1e79096a2b042e0525a8543c232279a"
+	title="Configure Full encryption mode"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
 />
 
 ## Use when
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
index d914207fd292d04..ffbf39cb4685b3c 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
@@ -45,7 +45,7 @@ Automatic SSL/TLS leverages advanced methods developed by the SSL/TLS Recommende
 Automatic SSL/TLS will not change your setting to a less secure encryption mode. For example, if your origin certificate expires, the encryption mode will not change from **Full (strict)** to **Full**. You must ensure the validity of your origin SSL/TLS configuration at all times.
 :::
 
-Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode.  If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
+Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode. If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
 
 Flexible → Full/Strict transitions are handled with extra caution since the origin scheme change (HTTP → HTTPS) alters cache keys. In this case, the ramp-up may proceed more slowly to allow cache warm-up before resuming standard increments.
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
index 60489481ea636f2..44f4f531ad50fd4 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
@@ -23,12 +23,11 @@ When you set your encryption mode to **Strict (SSL-Only Origin Pull)**, connecti
 The certificate presented by the origin will be validated the same as with [Full (strict) mode](/ssl/origin-configuration/ssl-modes/full-strict/).
 
 <Stream
-  id="f407072cb5b4837c8c3a58a69cde90b5"
-  title="Configure Strict encryption mode"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
+	id="f407072cb5b4837c8c3a58a69cde90b5"
+	title="Configure Strict encryption mode"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
 />
 
-
 ## Use when
 
 You want the most secure configuration available for your origin, you are an Enterprise customer, and you meet the requirements for [**Full (strict)** mode](/ssl/origin-configuration/ssl-modes/full-strict/).
diff --git a/src/content/docs/ssl/reference/all-features.mdx b/src/content/docs/ssl/reference/all-features.mdx
index 83243c2d35356e9..e4526a1b070534c 100644
--- a/src/content/docs/ssl/reference/all-features.mdx
+++ b/src/content/docs/ssl/reference/all-features.mdx
@@ -7,13 +7,12 @@ sidebar:
   order: 9
 head: []
 description: Review information on all Cloudflare SSL/TLS features and their availability.
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="ssl" />
\ No newline at end of file
+<ProductFeatures id="ssl" />
diff --git a/src/content/docs/ssl/reference/browser-compatibility.mdx b/src/content/docs/ssl/reference/browser-compatibility.mdx
index a7af16592d73bd7..964b497ae00d5c6 100644
--- a/src/content/docs/ssl/reference/browser-compatibility.mdx
+++ b/src/content/docs/ssl/reference/browser-compatibility.mdx
@@ -8,7 +8,6 @@ sidebar:
 head: []
 description: Review information about browser compatibility for the different
   Cloudflare SSL/TLS offerings.
-
 ---
 
 Cloudflare attempts to provide compatibility for as wide a range of user agents (browsers, API clients, etc.) as possible. However, the specific set of supported clients can vary depending on the different SSL/TLS certificate types, your visitor's [browser version](#non-sni-support), and the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that issues the certificate.
@@ -31,13 +30,13 @@ Although [SNI extensions](https://www.cloudflare.com/learning/ssl/what-is-sni/)
 
 To support non-SNI requests, you can:
 
-* [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
+- [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
 
   Note that `Legacy` custom certificates are not compatible with [BYOIP](/byoip/) and that, unlike [Universal SSL](/ssl/edge-certificates/universal-ssl/) or [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/), Cloudflare does not manage issuance and renewal for [custom certificates](/ssl/edge-certificates/custom-certificates/).
 
-* (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
+- (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
 
-* (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
+- (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
 
 ## HTTPS records
 
@@ -55,4 +54,4 @@ If you need HTTPS records without Universal SSL, you can manually add them, but
 
 Cloudflare's OCSP implementation uses HTTP/1.1 by default for plain HTTP connections.
 
-For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
\ No newline at end of file
+For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
diff --git a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
index 2c27bca6871ec0e..455857836c90c94 100644
--- a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
+++ b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
@@ -7,14 +7,13 @@ sidebar:
   order: 4
 head: []
 description: Learn about how Cloudflare decides which certificate and associated SSL/TLS settings to apply to individual hostnames.
-
 ---
 
 import { GlossaryTooltip } from "~/components";
 
 When a new certificate is created, Cloudflare first deploys the certificate and then serves it.
 
-***
+---
 
 ## Certificate deployment
 
@@ -42,17 +41,17 @@ For any given hostname, Cloudflare uses the following order to determine which c
 In this case, when the certificate with the closest expiration date is renewed, it will then become the one with the latest expiration date and get presented.
 :::
 
-***
+---
 
 ## Certificate presentation
 
 Cloudflare uses the following order to determine the certificate and settings used during a TLS handshake:
 
-1. **SNI match**: Certificates and settings that match the SNI hostname *exactly* take precedence.
+1. **SNI match**: Certificates and settings that match the SNI hostname _exactly_ take precedence.
 2. **SNI wildcard match**: If there is not an exact match between the hostname and SNI hostname, Cloudflare uses certificates and settings that match an SNI wildcard.
 3. **IP address**: If no SNI is presented, Cloudflare uses certificate based on the IP address (the hostname can support TLS handshakes made without SNI).
 
-***
+---
 
 ## Hostname priority
 
@@ -61,13 +60,11 @@ When multiple <GlossaryTooltip term="proxy status">proxied DNS records</Glossary
 Cloudflare determines this priority in the following order, assuming each record exists and is proxied (orange-clouded):
 
 1. **Exact hostname match**:
-
    1. [New custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) (belonging to a SaaS provider)
    2. [Legacy custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning/) (belonging to a SaaS provider)
    3. [DNS](/dns/proxy-status/) (belonging to the logical DNS zone)
 
 2. **Wildcard hostname match**:
-
    1. DNS (belonging to the logical DNS zone)
    2. New custom hostname (belonging to a SaaS provider)
 
@@ -79,9 +76,9 @@ If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudf
 
 Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`. Customer2 is a SaaS provider that creates and successfully [verifies the new custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/) `shop.example.com`. Afterward, traffic starts routing over Customer2's zone:
 
-* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
-* If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
-* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
+- If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
+- If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
+- If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
 
 #### Scenario 2
 
diff --git a/src/content/docs/ssl/reference/certificate-authorities.mdx b/src/content/docs/ssl/reference/certificate-authorities.mdx
index 0acd5bbcd68336c..07206f1e5b03d00 100644
--- a/src/content/docs/ssl/reference/certificate-authorities.mdx
+++ b/src/content/docs/ssl/reference/certificate-authorities.mdx
@@ -137,4 +137,4 @@ The following table lists the CAA record content for each CA:
 | SSL.com               | `ssl.com`                            |
 | Sectigo               | `sectigo.com`                        |
 
-[^1]: A payment gateway used with some ecommerce plugins.
\ No newline at end of file
+[^1]: A payment gateway used with some ecommerce plugins.
diff --git a/src/content/docs/ssl/reference/certificate-pinning.mdx b/src/content/docs/ssl/reference/certificate-pinning.mdx
index ab7622846e0f1d2..0c8cf4aa06ead76 100644
--- a/src/content/docs/ssl/reference/certificate-pinning.mdx
+++ b/src/content/docs/ssl/reference/certificate-pinning.mdx
@@ -7,7 +7,6 @@ sidebar:
   order: 8
 head: []
 description: Learn why Cloudflare does not support HTTP public key pinning (HPKP) and consider an alternative solution to prevent certificate misissuance.
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
index bf7f12feedcf976..0886b9f6b8540b5 100644
--- a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
+++ b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
@@ -5,7 +5,6 @@ products:
   - ssl
 source: https://support.cloudflare.com/hc/en-us/articles/4422920018317-Cloudflare-and-CVE-2019-1559
 title: Cloudflare and CVE-2019-1559
-
 ---
 
 The [GOLDENDOODLE and Zombie POODLE attacks](https://www.tripwire.com/state-of-security/vulnerability-management/zombie-poodle-goldendoodle/) affect applications that use certain cipher suites associated with TLS 1.2.
@@ -20,6 +19,6 @@ Even though your application is not vulnerable to CVE-2019-1559, some security s
 
 To remove these warnings, refer to [Customize cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) and exclude the following ciphers:
 
-* `ECDHE-ECDSA-AES256-SHA384`
-* `ECDHE-ECDSA-AES128-SHA256`
-* `ECDHE-RSA-AES256-SHA384`
+- `ECDHE-ECDSA-AES256-SHA384`
+- `ECDHE-ECDSA-AES128-SHA256`
+- `ECDHE-RSA-AES256-SHA384`
diff --git a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
index c2b34ec0ba65fc4..d90f31506bc85cd 100644
--- a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
+++ b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
@@ -34,31 +34,31 @@ Refer to [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum
 
 There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:
 
-* Header compression in TLS
-* Header compression in SPDY 3.1
-* RC4
-* SSL 3.0
-* Renegotiation with clients
-* DHE ciphersuites
-* Export-grade ciphers
+- Header compression in TLS
+- Header compression in SPDY 3.1
+- RC4
+- SSL 3.0
+- Renegotiation with clients
+- DHE ciphersuites
+- Export-grade ciphers
 
 Cloudflare mitigations protect against several attacks:
 
-* CRIME
-* BREACH
-* POODLE
-* RC4 Cryptographic Weaknesses
-* SSL Renegotiation Attack
-* Protocol Downgrade Attacks
-* FREAK
-* LogJam
-* 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
+- CRIME
+- BREACH
+- POODLE
+- RC4 Cryptographic Weaknesses
+- SSL Renegotiation Attack
+- Protocol Downgrade Attacks
+- FREAK
+- LogJam
+- 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
 
 Cloudflare provides additional mitigations for:
 
-* Heartbleed
-* Lucky Thirteen
-* CCS injection vulnerability
+- Heartbleed
+- Lucky Thirteen
+- CCS injection vulnerability
 
 Cloudflare has patched all servers against these vulnerabilities. Also, the [Cloudflare Web Application Firewall](/waf/) has managed rules that mitigate several of these vulnerabilities including Heartbleed and ShellShock.
 
@@ -70,5 +70,5 @@ Security scans that note the presence of ROBOT while on Cloudflare are a false p
 
 A vulnerability in the use of the Triple DES (3DES) encryption algorithm in the Transport Layer Security (TLS) protocol. Sweet32 is currently a proof of concept attack, there are no known examples of this in the wild. Cloudflare has manually mitigated the vulnerability for TLS 1.0 in the following manner:
 
-* The attacker must collect 32GB of data from a single TLS session.
-* Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
+- The attacker must collect 32GB of data from a single TLS session.
+- Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
diff --git a/src/content/docs/ssl/reference/index.mdx b/src/content/docs/ssl/reference/index.mdx
index cdb3e27983cc833..09459738c3be6af 100644
--- a/src/content/docs/ssl/reference/index.mdx
+++ b/src/content/docs/ssl/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more on Cloudflare SSL/TLS, refer to these articles:
 
diff --git a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
index 99bfb37d1c5d06d..dac25cb8479e6f3 100644
--- a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
@@ -34,14 +34,13 @@ This means that Entrust certificates will be issued using SSL.com roots.
 
 Since Cloudflare also [partners with SSL.com](/ssl/reference/certificate-authorities/), you can switch from uploading custom certificates to using Cloudflare-managed certificates. This change brings the following advantages:
 
-* Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
-* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
-* Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
-* If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
+- Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
+- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
+- Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
+- If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
 
 ## More resources
 
-* [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
-* [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
-* [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
-
+- [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
+- [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
+- [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
diff --git a/src/content/docs/ssl/reference/migration-guides/index.mdx b/src/content/docs/ssl/reference/migration-guides/index.mdx
index c7d41fe832e31ba..a2d9c7e09c8f5eb 100644
--- a/src/content/docs/ssl/reference/migration-guides/index.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 These guides walk you through the migration processes associated with various changes in Cloudflare's SSL/TLS infrastructure.
 
diff --git a/src/content/docs/ssl/reference/protocols.mdx b/src/content/docs/ssl/reference/protocols.mdx
index 4431c3f94d47833..5fc1e33f6ac60f0 100644
--- a/src/content/docs/ssl/reference/protocols.mdx
+++ b/src/content/docs/ssl/reference/protocols.mdx
@@ -13,10 +13,10 @@ tags:
 
 Cloudflare supports the following TLS protocols:
 
-* TLS 1.0
-* TLS 1.1
-* TLS 1.2
-* TLS 1.3
+- TLS 1.0
+- TLS 1.1
+- TLS 1.2
+- TLS 1.3
 
 TLS 1.0 is the [version that Cloudflare sets by default](/ssl/edge-certificates/additional-options/minimum-tls/) for all customers using certificate-based encryption.
 
@@ -42,12 +42,12 @@ TLS 1.3 has become widely adopted. As a general rule, Cloudflare recommends sett
 
 However, not all browser versions support TLS 1.2 and above. Depending on your particular business situation, this may present some limitations in using stronger encryption standards:
 
-* Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
+- Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
 
-* For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
+- For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
 
 ## Related resources
 
-* [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
-* [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
-* [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
+- [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
+- [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
+- [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
diff --git a/src/content/docs/ssl/saas.mdx b/src/content/docs/ssl/saas.mdx
index 3e85a7dff75970e..fcce7104fc2969a 100644
--- a/src/content/docs/ssl/saas.mdx
+++ b/src/content/docs/ssl/saas.mdx
@@ -7,5 +7,4 @@ title: Cloudflare for SaaS
 external_link: /cloudflare-for-platforms/cloudflare-for-saas/
 sidebar:
   order: 7
-
 ---
diff --git a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
index e7e9028c7ed7c8e..3061e3715c16c1c 100644
--- a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
@@ -171,4 +171,4 @@ When clicking `Approve Certificate` on a Certificate Approval renewal email, you
 
 ### Resolution
 
-Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
\ No newline at end of file
+Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
diff --git a/src/content/docs/ssl/troubleshooting/index.mdx b/src/content/docs/ssl/troubleshooting/index.mdx
index 098ba6ffb1eb8d0..d6196df82ab4540 100644
--- a/src/content/docs/ssl/troubleshooting/index.mdx
+++ b/src/content/docs/ssl/troubleshooting/index.mdx
@@ -10,11 +10,15 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting
-
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 For FAQs and other troubleshooting information, refer to the following resources:
 
-<ResourcesBySelector directory="ssl" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+<ResourcesBySelector
+	directory="ssl"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
index 5b2b86f88806a9d..8499af2e2c86769 100644
--- a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
@@ -10,7 +10,6 @@ sidebar:
 learning_center:
   title: What is mixed content?
   link: https://www.cloudflare.com/learning/ssl/what-is-mixed-content/
-
 ---
 
 Domains added to Cloudflare receive SSL certificates and can serve traffic over HTTPS. However, after starting to use Cloudflare, some customers notice missing content or page rendering issues when they first serve HTTPS traffic.
@@ -21,7 +20,7 @@ Normally, if your website loads all resources securely over HTTPS, visitors obse
 
 This indicates your site has a working SSL certificate and all resources loaded by the site are loaded over HTTPS. The green lock assures visitors that their connection is safe. One of the [symptoms of mixed content](#symptoms-of-mixed-content-occurrence) is that different icons appear instead of the green lock icon.
 
-***
+---
 
 ## Symptoms of mixed content occurrence
 
@@ -31,8 +30,8 @@ Most modern browsers block HTTP requests on secure HTTPS pages. Blocked content
 
 Each web browser uses different methods to warn visitors about mixed content on a website, potentially including:
 
-* A yellow triangle or information symbol beside the URL bar
-* Messages mentioning "secure content"
+- A yellow triangle or information symbol beside the URL bar
+- Messages mentioning "secure content"
 
 ### **Console logs**
 
@@ -46,7 +45,7 @@ For mixed content errors, the browser refuses to load the resources over an inse
 
 Information on using the browser’s debug tools to locate these issues are found in the documentation for [Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content) and [Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content). Alternatively, you can view your page source and find specific references of *http\://* for paths to other resources.
 
-***
+---
 
 ## Resolution
 
@@ -60,12 +59,12 @@ There are two methods to resolve mixed content errors.
 
 ### WordPress users
 
-Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the *Automatic HTTPS rewrites* option within the plugin.
+Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the _Automatic HTTPS rewrites_ option within the plugin.
 
-***
+---
 
 ## Related resources
 
-* [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
-* [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
-* [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
+- [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
+- [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
+- [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
diff --git a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
index 3ffbddefe30f522..759b5d1a646ae8d 100644
--- a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
+++ b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
@@ -14,7 +14,11 @@ description: Learn how to troubleshoot ERR_SSL_VERSION_OR_CIPHER_MISMATCH when
 
 import { Stream, Render } from "~/components";
 
-<Stream id="03e51d8a6f9a15e16969b8cc117d9225" title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public" />
+<Stream
+	id="03e51d8a6f9a15e16969b8cc117d9225"
+	title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public"
+/>
 
 After you [add a new domain](/fundamentals/manage-domains/add-site/) to Cloudflare, your visitors' browsers might display one of the following errors:
 
diff --git a/src/content/docs/stream/edit-videos/adding-captions.mdx b/src/content/docs/stream/edit-videos/adding-captions.mdx
index a5d5afcbca787ae..1cadfef74b3cd32 100644
--- a/src/content/docs/stream/edit-videos/adding-captions.mdx
+++ b/src/content/docs/stream/edit-videos/adding-captions.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 5
 products:
   - stream
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -149,15 +148,15 @@ Example response:
 
 ```json
 {
-  "result": {
-    "language": "en",
-    "label": "English (auto-generated)",
-    "generated": true,
-    "status": "inprogress"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"language": "en",
+		"label": "English (auto-generated)",
+		"generated": true,
+		"status": "inprogress"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -253,15 +252,15 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-  "result": {
-    "language": "en",
-    "label": "English",
-    "generated": false,
-    "status": "ready"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"language": "en",
+		"label": "English",
+		"generated": false,
+		"status": "ready"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -339,23 +338,23 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-  "result": [
-    {
-      "language": "en",
-      "label": "English (auto-generated)",
-      "generated": true,
-      "status": "inprogress"
-    },
-    {
-      "language": "de",
-      "label": "Deutsch",
-      "generated": false,
-      "status": "ready"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"language": "en",
+			"label": "English (auto-generated)",
+			"generated": true,
+			"status": "inprogress"
+		},
+		{
+			"language": "de",
+			"label": "Deutsch",
+			"generated": false,
+			"status": "ready"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -371,7 +370,7 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/<VIDEO_UID>/ca
 
 ### Example response to get the caption file for a video
 
-``` text
+```text
 WEBVTT
 
 1
@@ -458,25 +457,25 @@ deleted.
 
 ```json
 {
-  "result": "",
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": "",
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Limitations
 
-* A video must be uploaded before a caption can be attached to it. In the following
+- A video must be uploaded before a caption can be attached to it. In the following
   example URLs, the video's ID is referenced as `media_id`.
-* Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
+- Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
   formatted caption files. If you have a differently formatted caption file,
   use [a tool to convert your file to WebVTT](https://subtitletools.com/convert-to-vtt-online)
   prior to uploading it.
-* Videos may include several language captions, but each language must be unique.
+- Videos may include several language captions, but each language must be unique.
   For example, a video may have English, French, and German captions associated
   with it, but it cannot have two French captions.
-* Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
+- Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
   if you need to upload a larger file.
 
 ## Most common language codes
@@ -505,4 +504,4 @@ deleted.
 | pl            | Polish           |
 | uk            | Ukrainian        |
 | my            | Burmese          |
-| th            | Thai             |
\ No newline at end of file
+| th            | Thai             |
diff --git a/src/content/docs/stream/edit-videos/player-enhancements.mdx b/src/content/docs/stream/edit-videos/player-enhancements.mdx
index c439bce5564db4f..17a4d16c0a03c04 100644
--- a/src/content/docs/stream/edit-videos/player-enhancements.mdx
+++ b/src/content/docs/stream/edit-videos/player-enhancements.mdx
@@ -4,8 +4,8 @@ title: Add player enhancements
 description: Customize the Cloudflare Stream player with branding, logos, and share links.
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 With player enhancements, you can modify your video player to incorporate elements of your branding such as your logo, and customize additional options to present to your viewers.
@@ -14,10 +14,10 @@ The player enhancements are automatically applied to videos using the Stream Pla
 
 ## Properties
 
-* `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
-* `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
-* `channel_link`: The URL users will be directed to when selecting the logo from the video player.
-* `logo`: A valid HTTPS URL for the image of your logo.
+- `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
+- `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
+- `channel_link`: The URL users will be directed to when selecting the logo from the video player.
+- `logo`: A valid HTTPS URL for the image of your logo.
 
 ## Customize your own player
 
@@ -61,6 +61,6 @@ You can also pull the JSON by using the endpoint below.
    <DashButton url="/?to=/:account/stream/videos" />
 
 2. Select a video from the list to edit it.
-4. Select the **Public Details** tab.
-5. From **Public Details**, enter information in the text fields for the properties you want to set.
-6. When you are done, select **Save**.
+3. Select the **Public Details** tab.
+4. From **Public Details**, enter information in the text fields for the properties you want to set.
+5. When you are done, select **Save**.
diff --git a/src/content/docs/stream/examples/dash-js.mdx b/src/content/docs/stream/examples/dash-js.mdx
index 08404220937a1dd..734287e03dbb82d 100644
--- a/src/content/docs/stream/examples/dash-js.mdx
+++ b/src/content/docs/stream/examples/dash-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and the DASH reference
   player (dash.js)
 tags:
diff --git a/src/content/docs/stream/examples/hls-js.mdx b/src/content/docs/stream/examples/hls-js.mdx
index aeb76104307a2ce..db446e6987ec0c9 100644
--- a/src/content/docs/stream/examples/hls-js.mdx
+++ b/src/content/docs/stream/examples/hls-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and the HLS reference
   player (hls.js)
 tags:
@@ -25,12 +24,12 @@ products:
 		<video id="video"></video>
 		<script>
 			if (Hls.isSupported()) {
-				const video = document.getElementById('video');
+				const video = document.getElementById("video");
 				const hls = new Hls();
 				hls.attachMedia(video);
 				hls.on(Hls.Events.MEDIA_ATTACHED, () => {
 					hls.loadSource(
-						'https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8'
+						"https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
 					);
 				});
 			}
diff --git a/src/content/docs/stream/examples/index.mdx b/src/content/docs/stream/examples/index.mdx
index 8fb98577e0d6f90..53469dcc7069b34 100644
--- a/src/content/docs/stream/examples/index.mdx
+++ b/src/content/docs/stream/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: true
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/stream/examples/obs-from-scratch/index.mdx b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
index ca8948b5ccc2a81..6eab955a0b28cfb 100644
--- a/src/content/docs/stream/examples/obs-from-scratch/index.mdx
+++ b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up and start your first Live Stream using OBS (Open Broadcaster
   Software) Studio
 pcx_content_type: example
diff --git a/src/content/docs/stream/examples/rtmps_playback.mdx b/src/content/docs/stream/examples/rtmps_playback.mdx
index 206b7ad224a4c78..c614726f2680f0a 100644
--- a/src/content/docs/stream/examples/rtmps_playback.mdx
+++ b/src/content/docs/stream/examples/rtmps_playback.mdx
@@ -17,9 +17,10 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the RTMPS _playback_ key for your live input from either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/srt_playback.mdx b/src/content/docs/stream/examples/srt_playback.mdx
index 86ff42d0f0555d5..3b5100f826b36a3 100644
--- a/src/content/docs/stream/examples/srt_playback.mdx
+++ b/src/content/docs/stream/examples/srt_playback.mdx
@@ -17,9 +17,10 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the SRT Playback URL for your live input from either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/stream-player.mdx b/src/content/docs/stream/examples/stream-player.mdx
index b542eeb0bb0f3c4..a948e755d04215e 100644
--- a/src/content/docs/stream/examples/stream-player.mdx
+++ b/src/content/docs/stream/examples/stream-player.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with the Cloudflare Stream Player
 tags:
   - Playback
@@ -19,12 +18,12 @@ products:
 	<head> </head>
 	<body>
 		<div style="position: relative; padding-top: 56.25%;">
-		<iframe
-			src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-			style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-			allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-			allowfullscreen="true"
-		></iframe>
+			<iframe
+				src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+				style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+				allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+				allowfullscreen="true"
+			></iframe>
 		</div>
 	</body>
 </html>
diff --git a/src/content/docs/stream/examples/video-js.mdx b/src/content/docs/stream/examples/video-js.mdx
index e8fbb571e4df8ae..e6a2aad84dcfd9f 100644
--- a/src/content/docs/stream/examples/video-js.mdx
+++ b/src/content/docs/stream/examples/video-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and Video.js
 tags:
   - Playback
@@ -32,7 +31,7 @@ products:
 		</video-js>
 
 		<script>
-			const vid = document.getElementById('vid1');
+			const vid = document.getElementById("vid1");
 			const player = videojs(vid);
 		</script>
 	</body>
diff --git a/src/content/docs/stream/examples/vidstack.mdx b/src/content/docs/stream/examples/vidstack.mdx
index 50ee3a7e270f9f3..fee573dfe355731 100644
--- a/src/content/docs/stream/examples/vidstack.mdx
+++ b/src/content/docs/stream/examples/vidstack.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and Vidstack
 tags:
   - Playback
@@ -19,13 +18,13 @@ products:
 There's a few options to choose from when getting started with Vidstack, follow any of the links
 below to get setup. You can replace the player `src` with `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8` to test Cloudflare Stream.
 
-* [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
-* [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
-* [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
-* [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
-* [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
-* [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
-* [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
+- [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
+- [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
+- [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
+- [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
+- [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
+- [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
+- [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
 
 ## Examples
 
diff --git a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
index 67fd72638c29427..84765138fc82658 100644
--- a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
+++ b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - stream
 ---
+
 import { DashButton } from "~/components";
 
 Stream provides analytics about both live video and video uploaded to Stream, via the GraphQL API described below, as well as on the Stream **Analytics** page of the Cloudflare dashboard.
diff --git a/src/content/docs/stream/getting-analytics/index.mdx b/src/content/docs/stream/getting-analytics/index.mdx
index 0b87d38fd44efbc..ddc5d2b46f2d12e 100644
--- a/src/content/docs/stream/getting-analytics/index.mdx
+++ b/src/content/docs/stream/getting-analytics/index.mdx
@@ -6,20 +6,21 @@ sidebar:
   order: 8
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 Stream provides server-side analytics that can be used to:
 
-* Identify most viewed video content in your app or platform.
-* Identify where content is viewed from and when it is viewed.
-* Understand which creators on your platform are publishing the most viewed content, and analyze trends.
+- Identify most viewed video content in your app or platform.
+- Identify where content is viewed from and when it is viewed.
+- Understand which creators on your platform are publishing the most viewed content, and analyze trends.
 
 You can access data on either:
+
 - The Stream **Analytics** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/analytics" />
+  <DashButton url="/?to=/:account/stream/analytics" />
 
 - The [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics).
 
diff --git a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
index b4650f2f9bc28c2..2f19eae42ea7fc3 100644
--- a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
+++ b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 2
 products:
   - stream
-
 ---
 
 The Stream player has full support for live viewer counts by default. To get the viewer count for live videos for use with third party players, make a `GET` request to the `/views` endpoint.
diff --git a/src/content/docs/stream/manage-video-library/index.mdx b/src/content/docs/stream/manage-video-library/index.mdx
index f1c87b325b33406..b4ece17f01bbf40 100644
--- a/src/content/docs/stream/manage-video-library/index.mdx
+++ b/src/content/docs/stream/manage-video-library/index.mdx
@@ -9,4 +9,3 @@ sidebar:
 products:
   - stream
 ---
-
diff --git a/src/content/docs/stream/manage-video-library/searching.mdx b/src/content/docs/stream/manage-video-library/searching.mdx
index 385d98f5df957d0..78979f3e8fe99a6 100644
--- a/src/content/docs/stream/manage-video-library/searching.mdx
+++ b/src/content/docs/stream/manage-video-library/searching.mdx
@@ -4,7 +4,6 @@ title: Search for videos
 description: Search your Cloudflare Stream video library by name using the Stream API.
 products:
   - stream
-
 ---
 
 You can search for videos by name through the Stream API by adding a `search` query parameter to the [list media files](/api/resources/stream/methods/list/) endpoint.
diff --git a/src/content/docs/stream/stream-api.mdx b/src/content/docs/stream/stream-api.mdx
index 14a6a735991b555..3cb2866bfef54bb 100644
--- a/src/content/docs/stream/stream-api.mdx
+++ b/src/content/docs/stream/stream-api.mdx
@@ -7,5 +7,4 @@ sidebar:
   order: 11
 products:
   - stream
-
 ---
diff --git a/src/content/docs/stream/stream-live/custom-domains.mdx b/src/content/docs/stream/stream-live/custom-domains.mdx
index cbea1246aae4f56..9d386faca81de66 100644
--- a/src/content/docs/stream/stream-live/custom-domains.mdx
+++ b/src/content/docs/stream/stream-live/custom-domains.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 3
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 With custom ingest domains, you can configure your RTMPS feeds to use an ingest URL that you specify instead of using `live.cloudflare.com.`
@@ -21,7 +21,6 @@ Custom Ingest Domains cannot be configured for domains with [zone holds](/fundam
 
 :::
 
-
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
 
    <DashButton url="/?to=/:account/stream/inputs" />
diff --git a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
index de3dd780bfe12a4..6cc5f62c4cb10f5 100644
--- a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
+++ b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
@@ -9,18 +9,16 @@ sidebar:
   order: 4
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 You can enable downloads for live stream videos from the Cloudflare dashboard. Videos are available for download after they enter the **Ready** state.
 
 :::note
 
-
 Downloadable MP4s are only available for live recordings under four hours. Live recordings exceeding four hours can be played at a later time but cannot be downloaded as an MP4.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
diff --git a/src/content/docs/stream/stream-live/dvr-for-live.mdx b/src/content/docs/stream/stream-live/dvr-for-live.mdx
index 47ae2985c0d2fce..3bcb1c067f39da8 100644
--- a/src/content/docs/stream/stream-live/dvr-for-live.mdx
+++ b/src/content/docs/stream/stream-live/dvr-for-live.mdx
@@ -13,14 +13,14 @@ manifest URL.
 
 ## Stream Player
 
-``` html title="Stream Player embed format"
+```html title="Stream Player embed format"
 <div style="position: relative; padding-top: 56.25%;">
-  <iframe
-    src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
-    style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-    allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-    allowfullscreen="true"
-  ></iframe>
+	<iframe
+		src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
 </div>
 ```
 
@@ -37,7 +37,7 @@ When DVR mode is enabled the Stream Player will:
 
 ## HLS manifest for custom players
 
-``` text title="HLS manifest URL format"
+```text title="HLS manifest URL format"
 https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/manifest/video.m3u8?dvrEnabled=true
 ```
 
diff --git a/src/content/docs/stream/stream-live/index.mdx b/src/content/docs/stream/stream-live/index.mdx
index 3234ba97f8bbef7..7baf513e8a40a50 100644
--- a/src/content/docs/stream/stream-live/index.mdx
+++ b/src/content/docs/stream/stream-live/index.mdx
@@ -9,7 +9,6 @@ sidebar:
   order: 4
 products:
   - stream
-
 ---
 
 Cloudflare Stream lets you or your users [stream live video](https://www.cloudflare.com/learning/video/what-is-live-streaming/), and play live video in your website or app, without managing and configuring any of your own infrastructure.
@@ -37,7 +36,7 @@ With ABR, client video players need to be provided with estimates of how much ba
 
 ### How it works
 
-If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution.  This ensures that as many viewers as possible view the highest quality level.
+If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution. This ensures that as many viewers as possible view the highest quality level.
 
 Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the manifest will be higher — a stream like this has a high bitrate and requires more bandwidth. This ensures that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
 
@@ -59,7 +58,7 @@ After the live stream ends, you can [replay live stream recordings](/stream/stre
 
 Stream Live is billed identically to the rest of Cloudflare Stream.
 
-* You pay $5 per 1000 minutes of recorded video.
-* You pay $1 per 1000 minutes of delivered video.
+- You pay $5 per 1000 minutes of recorded video.
+- You pay $1 per 1000 minutes of delivered video.
 
 All Stream Live videos are automatically recorded. There is no additional cost for encoding and packaging live videos.
diff --git a/src/content/docs/stream/stream-live/live-instant-clipping.mdx b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
index 900ea4ee817bc3f..7c329e9302fd291 100644
--- a/src/content/docs/stream/stream-live/live-instant-clipping.mdx
+++ b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
@@ -10,10 +10,8 @@ Stream supports generating clips of live streams and recordings so creators and
 
 :::note[Note:]
 
-
 Clipping works differently for uploaded / on-demand videos. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
 
-
 :::
 
 ## Prerequisites
@@ -32,18 +30,12 @@ To help users replay and seek recent content, request a preview manifest by addi
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID||INPUT_ID>/manifest/video.m3u8?duration=5m
 ```
 
-
-
-* `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
-
+- `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
 
 When the preview manifest is delivered, inspect the headers for two properties:
 
-
-
-* `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the *broadcast* start time, not the *preview* start time.
-* `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an *input* ID because the clip URL should reference the *video* ID.
-
+- `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the _broadcast_ start time, not the _preview_ start time.
+- `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an _input_ ID because the clip URL should reference the _video_ ID.
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -59,38 +51,44 @@ let currentPreviewVideoID;
 
 // Override the pLoader (playlist loader) to read the manifest headers:
 class pLoader extends Hls.DefaultConfig.loader {
-  constructor(config) {
-    super(config);
-    var load = this.load.bind(this);
-    this.load = function (context, config, callbacks) {
-      if (context.type == 'manifest') {
-        var onSuccess = callbacks.onSuccess;
-        // copy the existing onSuccess handler to fire it later.
-
-        callbacks.onSuccess = function (response, stats, context, networkDetails) {
-          // The fourth argument here is undocumented in HLS.js but contains
-          // the response object for the manifest fetch, which gives us headers:
-
-          currentPreviewStart =
-            parseFloat(networkDetails.getResponseHeader('preview-start-seconds'));
-          // Save the start time of the preview manifest
-
-          currentPreviewVideoID =
-            networkDetails.getResponseHeader('stream-media-id');
-          // Save the video ID in case the preview was loaded with an input ID
-
-          onSuccess(response, stats, context);
-          // And fire the existing success handler.
-        };
-      }
-      load(context, config, callbacks);
-    };
-  }
+	constructor(config) {
+		super(config);
+		var load = this.load.bind(this);
+		this.load = function (context, config, callbacks) {
+			if (context.type == "manifest") {
+				var onSuccess = callbacks.onSuccess;
+				// copy the existing onSuccess handler to fire it later.
+
+				callbacks.onSuccess = function (
+					response,
+					stats,
+					context,
+					networkDetails,
+				) {
+					// The fourth argument here is undocumented in HLS.js but contains
+					// the response object for the manifest fetch, which gives us headers:
+
+					currentPreviewStart = parseFloat(
+						networkDetails.getResponseHeader("preview-start-seconds"),
+					);
+					// Save the start time of the preview manifest
+
+					currentPreviewVideoID =
+						networkDetails.getResponseHeader("stream-media-id");
+					// Save the video ID in case the preview was loaded with an input ID
+
+					onSuccess(response, stats, context);
+					// And fire the existing success handler.
+				};
+			}
+			load(context, config, callbacks);
+		};
+	}
 }
 
 // Specify the new loader class when setting up HLS
 const hls = new Hls({
-  pLoader: pLoader,
+	pLoader: pLoader,
 });
 ```
 
@@ -102,11 +100,8 @@ To play a clip of a live stream or recording, request a clip manifest with a dur
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/manifest/clip.m3u8?time=600s&duration=30s
 ```
 
-
-
-* `time` string start time of the clip in seconds, from the start of the live stream or recording
-* `duration` string duration of the clip in seconds, up to 60 seconds max
-
+- `time` string start time of the clip in seconds, from the start of the live stream or recording
+- `duration` string duration of the clip in seconds, up to 60 seconds max
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -118,8 +113,6 @@ An MP4 of the clip can also be generated dynamically to be saved and shared on o
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/clip.mp4?time=600s&duration=30s&filename=clip.mp4
 ```
 
-
-
-* `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
-* `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
-* `filename` string *(optional)* a filename for the clip
+- `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
+- `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
+- `filename` string _(optional)_ a filename for the clip
diff --git a/src/content/docs/stream/stream-live/simulcasting.mdx b/src/content/docs/stream/stream-live/simulcasting.mdx
index e5f03f9003c3432..0f88a8a94fd31ff 100644
--- a/src/content/docs/stream/stream-live/simulcasting.mdx
+++ b/src/content/docs/stream/stream-live/simulcasting.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 5
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 Simulcasting lets you forward your live stream to third-party platforms such as Twitch, YouTube, Facebook, Twitter, and more. You can simulcast to up to 50 concurrent destinations from each live input. To begin simulcasting, select an input and add one or more Outputs.
@@ -28,30 +28,32 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/live_inputs/<I
 
 ```json title="Response"
 {
-  "result": {
-    "uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
-    "url": "rtmp://a.rtmp.youtube.com/live2",
-    "streamKey": "<redacted>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
+		"url": "rtmp://a.rtmp.youtube.com/live2",
+		"streamKey": "<redacted>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Control when you start and stop simulcasting
 
 You can enable and disable individual live outputs with either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
+
 - [The API](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/update/)
 
 This allows you to:
 
-* Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
-* Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
-* Give your own users manual control over when they go live to specific simulcasting destinations.
+- Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
+- Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
+- Give your own users manual control over when they go live to specific simulcasting destinations.
 
 When a live output is disabled, video is not simulcast to the live output, even when actively streaming to the corresponding live input.
 
@@ -68,11 +70,11 @@ By default, all live outputs are enabled.
 
 ## Manage outputs
 
-| Command                                                                  | Method   | Endpoint                                                                 |
-| ------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------ |
-| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)      | `GET`    | `accounts/:account_identifier/stream/live_inputs`                        |
-| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/) | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier` |
-| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs` |
-| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/) | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
+| Command                                                                                                                                      | Method   | Endpoint                                                                                        |
+| -------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------- |
+| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)                                                                 | `GET`    | `accounts/:account_identifier/stream/live_inputs`                                               |
+| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/)                                                             | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier`                        |
+| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET`    | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs`                     |
+| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/)                                      | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
 
 If the associated live input is already retransmitting to this output when you make the `DELETE` request, that output will be disconnected within 30 seconds.
diff --git a/src/content/docs/stream/stream-live/start-stream-live.mdx b/src/content/docs/stream/stream-live/start-stream-live.mdx
index 0f114459ebb8755..7c32e2b8b669da8 100644
--- a/src/content/docs/stream/stream-live/start-stream-live.mdx
+++ b/src/content/docs/stream/stream-live/start-stream-live.mdx
@@ -22,6 +22,7 @@ After you subscribe to Stream, you can create Live Inputs in Dash or via the API
 ## Use the dashboard
 
 **Step 1:** In the Cloudflare dashboard, go to the **Live inputs** page and create a live input.
+
 <DashButton url="/?to=/:account/stream/inputs" />
 
 ![Create live input field from dashboard](~/assets/images/stream/create-live-input-from-stream-dashboard.png)
diff --git a/src/content/docs/stream/stream-live/troubleshooting.mdx b/src/content/docs/stream/stream-live/troubleshooting.mdx
index d82985f4c5dfeff..48973fe852b3b32 100644
--- a/src/content/docs/stream/stream-live/troubleshooting.mdx
+++ b/src/content/docs/stream/stream-live/troubleshooting.mdx
@@ -7,7 +7,8 @@ sidebar:
 products:
   - stream
 ---
-import {Details, DashButton } from "~/components"
+
+import { Details, DashButton } from "~/components";
 
 In addition to following the live stream troubleshooting steps in this guide, make sure that your video settings align with [Cloudflare live stream recommendations](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If you use OBS, you can also check these [OBS-specific recommendations](/stream/examples/obs-from-scratch/#6-optional-optimize-settings).
 
@@ -23,29 +24,37 @@ If your live stream is buffering, freezing, experiencing latency issues, or havi
 
 3. Look at your **Keyframe Interval** chart.
 
-	It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform.
-			* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
-
-	  	* If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
+   It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform. \* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
+   - If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
 
-	<Details header="What is a keyframe interval?">
-	The keyframe interval (also called GOP size) is a measurement of how often keyframes are sent to Stream. A shorter keyframe interval requires more Internet bandwidth on the broadcast side, but can reduce glass-to-glass latency. A longer keyframe requires less Internet bandwidth and can reduce buffering and freezing, but can increase glass-to-glass latency.
-	</Details>
+   <Details header="What is a keyframe interval?">
+   	The keyframe interval (also called GOP size) is a measurement of how often
+   	keyframes are sent to Stream. A shorter keyframe interval requires more
+   	Internet bandwidth on the broadcast side, but can reduce glass-to-glass
+   	latency. A longer keyframe requires less Internet bandwidth and can reduce
+   	buffering and freezing, but can increase glass-to-glass latency.
+   </Details>
 
-3. Look at your **Upload-to-Duration Ratio** chart.
+4. Look at your **Upload-to-Duration Ratio** chart.
 
-	It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
-    * [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
+   It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
+   - [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
 
-    * Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
-	   * If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
-	   * If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
+   - Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
+     - If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
+     - If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
 
-    * Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
+   - Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
 
-	<Details header="What is the upload-to-duration ratio?">
-	The upload-to-duration ratio is a measurement of how long it takes to upload a part of the stream compared to how long that part would take to play. A ratio of less than 100% means that the stream is uploading at least as fast as it would take to play, so most users should not experience buffering or freezing. A ratio of 100% or more means that your video is uploading slower than it would take to play, so it is likely that most users will experience buffering and freezing.
-	</Details>
+   <Details header="What is the upload-to-duration ratio?">
+   	The upload-to-duration ratio is a measurement of how long it takes to
+   	upload a part of the stream compared to how long that part would take to
+   	play. A ratio of less than 100% means that the stream is uploading at least
+   	as fast as it would take to play, so most users should not experience
+   	buffering or freezing. A ratio of 100% or more means that your video is
+   	uploading slower than it would take to play, so it is likely that most
+   	users will experience buffering and freezing.
+   </Details>
 
 ## Encoder failing to connect or keeps disconnecting
 
@@ -55,22 +64,22 @@ If your encoder shows a connection error such as "Failed to connect to server" o
 
 - Verify that the live input is enabled. A live input that is _disabled_ will reject all incoming connections. You can enable or disable a live input from the **Live inputs** page in the Dashboard or via the API using the `enabled` property.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
-   ```bash
-   curl -X GET \
-   --header "Authorization: Bearer <API_TOKEN>" \
-   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
-   ```
+  ```bash
+  curl -X GET \
+  --header "Authorization: Bearer <API_TOKEN>" \
+  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
+  ```
 
-   If `enabled` is `false` in the response, update the live input to enable it:
+  If `enabled` is `false` in the response, update the live input to enable it:
 
-   ```bash
-   curl --request PUT \
-   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
-   --header "Authorization: Bearer <API_TOKEN>" \
-   --data '{"enabled": true}'
-   ```
+  ```bash
+  curl --request PUT \
+  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
+  --header "Authorization: Bearer <API_TOKEN>" \
+  --data '{"enabled": true}'
+  ```
 
 - If you use [Live Webhooks](/stream/stream-live/webhooks/), check for a `live_input.errored` event. The webhook payload includes an [error code](/stream/stream-live/webhooks/#error-codes) that can help you troubleshoot the specific cause.
 
@@ -84,4 +93,4 @@ If your encoder is connected and the dashboard shows a green **Connected** statu
 
 - Verify that your encoder is sending [AAC audio](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If it is not, set your encoder's settings to AAC explicitly.
 
-- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to *variable* or *automatic*, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
\ No newline at end of file
+- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to _variable_ or _automatic_, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
diff --git a/src/content/docs/stream/stream-live/webhooks.mdx b/src/content/docs/stream/stream-live/webhooks.mdx
index b80693318e6d6cb..2f298bf7ca81d9d 100644
--- a/src/content/docs/stream/stream-live/webhooks.mdx
+++ b/src/content/docs/stream/stream-live/webhooks.mdx
@@ -8,7 +8,7 @@ products:
   - stream
 ---
 
-import { AvailableNotifications,DashButton } from "~/components"
+import { AvailableNotifications, DashButton } from "~/components";
 
 Stream Live offers webhooks to notify your service when an Input connects, disconnects, or encounters an error with Stream Live.
 
@@ -40,15 +40,15 @@ Webhooks works differently for uploaded / on-demand videos. For more information
 
 ```json title="Example webhook payload"
 {
-  "name": "Live Webhook Test",
-  "text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
-  "data": {
-    "notification_name": "Stream Live Input",
-    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-    "event_type": "live_input.disconnected",
-    "updated_at": "2022-01-13T11:43:41.855717910Z"
-  },
-  "ts": 1642074233
+	"name": "Live Webhook Test",
+	"text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
+	"data": {
+		"notification_name": "Stream Live Input",
+		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+		"event_type": "live_input.disconnected",
+		"updated_at": "2022-01-13T11:43:41.855717910Z"
+	},
+	"ts": 1642074233
 }
 ```
 
@@ -58,30 +58,30 @@ If there are issues detected with the input, the `event_type` will be `live_inpu
 
 ## Error codes
 
-* `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
-* `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
-* `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
-* `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
-* `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
+- `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
+- `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
+- `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
+- `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
+- `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
 
 ```json title="Example live_input.errored webhook payload"
 {
-  "name": "Live Webhook Test",
-  "text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
-  "data": {
-    "notification_name": "Stream Live Input",
-    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-    "event_type": "live_input.errored",
-    "updated_at": "2024-07-09T18:07:51.077371662Z",
-    "live_input_errored": {
-      "error": {
-        "code": "ERR_GOP_OUT_OF_RANGE",
-        "message": "Input GOP size or keyframe interval is out of range."
-      },
-      "video_codec": "",
-      "audio_codec": ""
-    }
-  },
-  "ts": 1720548474,
+	"name": "Live Webhook Test",
+	"text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
+	"data": {
+		"notification_name": "Stream Live Input",
+		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+		"event_type": "live_input.errored",
+		"updated_at": "2024-07-09T18:07:51.077371662Z",
+		"live_input_errored": {
+			"error": {
+				"code": "ERR_GOP_OUT_OF_RANGE",
+				"message": "Input GOP size or keyframe interval is out of range."
+			},
+			"video_codec": "",
+			"audio_codec": ""
+		}
+	},
+	"ts": 1720548474
 }
 ```
diff --git a/src/content/docs/stream/transform-videos/bindings.mdx b/src/content/docs/stream/transform-videos/bindings.mdx
index 5e17fac1f2f59de..8d5cd162e0df120 100644
--- a/src/content/docs/stream/transform-videos/bindings.mdx
+++ b/src/content/docs/stream/transform-videos/bindings.mdx
@@ -13,7 +13,6 @@ products:
 
 import { WranglerConfig, InlineBadge } from "~/components";
 
-
 A [binding](/workers/runtime-apis/bindings/) connects your [Worker](/workers/) to external resources on the Developer Platform, like [Media Transformations](/stream/transform-videos/), [R2 buckets](/r2/buckets/), or [KV namespaces](/kv/concepts/kv-namespaces/).
 
 You can bind the Media Transformations API to your Worker to transform, resize, and extract content from videos without requiring them to be accessible through a URL.
@@ -155,8 +154,8 @@ export default {
 		const frame = await env.MEDIA.input(video.body)
 			.transform({ width: 720 })
 			.output({
-				mode: 'frame',
-				time: '3s',
+				mode: "frame",
+				time: "3s",
 			})
 			.response();
 
@@ -166,13 +165,10 @@ export default {
 			prompt: "Generate a caption for this image",
 			max_tokens: 512,
 		};
-		const response = await env.AI.run(
-			"@cf/unum/uform-gen2-qwen-500m",
-			payload
-		);
+		const response = await env.AI.run("@cf/unum/uform-gen2-qwen-500m", payload);
 		return new Response(JSON.stringify(response));
-	}
-}
+	},
+};
 ```
 
 ### Extract audio
@@ -214,28 +210,22 @@ export default {
 		const audio = await env.MEDIA.input(video.body)
 			.transform()
 			.output({
-				mode: 'audio',
-				})
+				mode: "audio",
+			})
 			.response();
 
 		// Prepare and run Workers AI inference
 		const payload = {
 			audio: [...new Uint8Array(await audio.arrayBuffer())],
 		};
-		const response = await env.AI.run(
-			"@cf/openai/whisper",
-			payload
-		);
+		const response = await env.AI.run("@cf/openai/whisper", payload);
 
 		// response will have props {text, word_count, vtt, words}
-		return new Response(
-			JSON.stringify(response, null, 2),
-			{
-				headers: {'Content-Type': 'application/json'}
-			}
-		);
-	}
-}
+		return new Response(JSON.stringify(response, null, 2), {
+			headers: { "Content-Type": "application/json" },
+		});
+	},
+};
 ```
 
 ### Store transformed output in R2
diff --git a/src/content/docs/stream/transform-videos/index.mdx b/src/content/docs/stream/transform-videos/index.mdx
index cd79ead8f896bd9..1d9dfe55c0bc0b1 100644
--- a/src/content/docs/stream/transform-videos/index.mdx
+++ b/src/content/docs/stream/transform-videos/index.mdx
@@ -7,17 +7,15 @@ sidebar:
 products:
   - stream
 ---
+
 import { DashButton } from "~/components";
 
 :::note[Media Transformations is now GA:]
 
-
 Billing for Media Transformations began on November 1st, 2025.
 
-
 :::
 
-
 You can optimize and manipulate videos stored _outside_ of Cloudflare Stream with Media Transformations. Transformed videos and images are served from one of your zones on Cloudflare.
 
 To transform a video or image, you must [enable transformations](/stream/transform-videos/#getting-started) for your zone. If your zone already has Image Transformations enabled, you can also optimize videos with Media Transformations.
diff --git a/src/content/docs/stream/uploading-videos/index.mdx b/src/content/docs/stream/uploading-videos/index.mdx
index 1e357b50c36f54c..8d01549e5d26ccf 100644
--- a/src/content/docs/stream/uploading-videos/index.mdx
+++ b/src/content/docs/stream/uploading-videos/index.mdx
@@ -12,17 +12,15 @@ Before you upload your video, review the options for uploading a video, supporte
 
 ## Upload options
 
-| Upload method	| When to use |
-|---------------|-------------|
-|[Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)| Upload videos from the Stream Dashboard without writing any code.
-|[Upload with a link](/stream/uploading-videos/upload-via-link/)| Upload videos using a link, such as an S3 bucket or content management system.
-|[Upload video file](/stream/uploading-videos/upload-video-file/)| Upload videos stored on a computer.
-|[Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/)| Allows end users of your website or app to upload videos directly to Cloudflare Stream.
-
+| Upload method                                                              | When to use                                                                             |
+| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
+| [Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)       | Upload videos from the Stream Dashboard without writing any code.                       |
+| [Upload with a link](/stream/uploading-videos/upload-via-link/)            | Upload videos using a link, such as an S3 bucket or content management system.          |
+| [Upload video file](/stream/uploading-videos/upload-video-file/)           | Upload videos stored on a computer.                                                     |
+| [Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/) | Allows end users of your website or app to upload videos directly to Cloudflare Stream. |
 
 ## Supported video formats
 
-
 :::note
 Files must be less than 30 GB, and content should be encoded and uploaded in the same frame rate it was recorded.
 :::
diff --git a/src/content/docs/stream/uploading-videos/player-api.mdx b/src/content/docs/stream/uploading-videos/player-api.mdx
index ba0c652f2710a62..afe17603c50c36e 100644
--- a/src/content/docs/stream/uploading-videos/player-api.mdx
+++ b/src/content/docs/stream/uploading-videos/player-api.mdx
@@ -22,103 +22,82 @@ Multiple attributes can be used together, added one after each other like this:
 
 ## Supported attributes
 
-* `autoplay` boolean
-
-  * Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
+- `autoplay` boolean
+  - Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
 
   :::note
   To disable video autoplay, the `autoplay` attribute needs to be removed altogether as this attribute. Setting `autoplay="false"` will not work; the video will autoplay if the attribute is there in the `<stream>` tag.
 
 In addition, some browsers now prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, see [new video policies for iOS](https://webkit.org/blog/6784/new-video-policies-for-ios/).
-  :::
-
-* `controls` boolean
-
-  * Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
-
-* `height` integer
-
-  * The height of the video's display area, in CSS pixels.
+:::
 
-* `loop` boolean
+- `controls` boolean
+  - Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
 
-  * A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
+- `height` integer
+  - The height of the video's display area, in CSS pixels.
 
-* `muted` boolean
+- `loop` boolean
+  - A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
 
-  * A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
+- `muted` boolean
+  - A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
 
-* `preload` string | null
-
-  * This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
+- `preload` string | null
+  - This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
 
   :::note
   The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
   :::
 
-* `poster` string
-
-  * A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
-
-* `src` string
+- `poster` string
+  - A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
 
-  * The video id from the video you've uploaded to Cloudflare Stream should be included here.
+- `src` string
+  - The video id from the video you've uploaded to Cloudflare Stream should be included here.
 
-* `width` integer
-
-  * The width of the video's display area, in CSS pixels.
+- `width` integer
+  - The width of the video's display area, in CSS pixels.
 
 ## Methods
 
-* `play()` Promise
-
-  * Start video playback.
-
-* `pause()` null
+- `play()` Promise
+  - Start video playback.
 
-  * Pause video playback.
+- `pause()` null
+  - Pause video playback.
 
 ## Properties
 
-* `autoplay`
+- `autoplay`
+  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
-  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+- `controls`
+  - Sets or returns whether the video should display controls (like play/pause etc.)
 
-* `controls`
+- `currentTime`
+  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-  * Sets or returns whether the video should display controls (like play/pause etc.)
+- `duration` readonly
+  - Returns the duration of the video in seconds.
 
-* `currentTime`
+- `ended` readonly
+  - Returns whether the video has ended.
 
-  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+- `loop`
+  - Sets or returns whether the video should start over when it reaches the end
 
-* `duration` readonly
+- `muted`
+  - Sets or returns whether the audio should be played with the video
 
-  * Returns the duration of the video in seconds.
+- `paused` readonly
+  - Returns whether the video is paused
 
-* `ended` readonly
+- `preload`
+  - Sets or returns whether the video should be preloaded upon element load.
 
-  * Returns whether the video has ended.
-
-* `loop`
-
-  * Sets or returns whether the video should start over when it reaches the end
-
-* `muted`
-
-  * Sets or returns whether the audio should be played with the video
-
-* `paused` readonly
-
-  * Returns whether the video is paused
-
-* `preload`
-
-  * Sets or returns whether the video should be preloaded upon element load.
-
-* `volume`
-
-  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+- `volume`
+  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -126,102 +105,78 @@ In addition, some browsers now prevent videos with audio from playing automatica
 
 Stream supports most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-* `abort`
-
-  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+- `abort`
+  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-* `canplay`
+- `canplay`
+  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-  * Sent when enough data is available that the media can be played, at least for a couple of frames.
+- `canplaythrough`
+  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-* `canplaythrough`
+- `durationchange`
+  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+- `ended`
+  - Sent when playback completes.
 
-* `durationchange`
+- `error`
+  - Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+- `loadeddata`
+  - The first frame of the media has finished loading.
 
-* `ended`
+- `loadedmetadata`
+  - The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
 
-  * Sent when playback completes.
+- `loadstart`
+  - Sent when loading of the media begins.
 
-* `error`
+- `pause`
+  - Sent when the playback state is changed to paused (paused property is true).
 
-  * Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+- `play`
+  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
 
-* `loadeddata`
+- `playing`
+  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
 
-  * The first frame of the media has finished loading.
+- `progress`
+  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
 
-* `loadedmetadata`
+- `ratechange`
+  - Sent when the playback speed changes.
 
-   * The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
+- `seeked`
+  - Sent when a seek operation completes.
 
-* `loadstart`
+- `seeking`
+  - Sent when a seek operation begins.
 
-  * Sent when loading of the media begins.
+- `stalled`
+  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
 
-* `pause`
+- `suspend`
+  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
 
-  * Sent when the playback state is changed to paused (paused property is true).
+- `timeupdate`
+  - The time indicated by the element's currentTime attribute has changed.
 
-* `play`
+- `volumechange`
+  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
-  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
-
-* `playing`
-
-  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
-
-* `progress`
-
-  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
-
-* `ratechange`
-
-  * Sent when the playback speed changes.
-
-* `seeked`
-
-  * Sent when a seek operation completes.
-
-* `seeking`
-
-  * Sent when a seek operation begins.
-
-* `stalled`
-
-  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
-
-* `suspend`
-
-  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
-
-* `timeupdate`
-
-  * The time indicated by the element's currentTime attribute has changed.
-
-* `volumechange`
-
-  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
-
-* `waiting`
-
-  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+- `waiting`
+  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-* `stream-adstart`
-
-  * Fires when `ad-url` attribute is present and the ad begins playback
-
-* `stream-adend`
-
-  * Fires when `ad-url` attribute is present and the ad finishes playback
+- `stream-adstart`
+  - Fires when `ad-url` attribute is present and the ad begins playback
 
-* `stream-adtimeout`
+- `stream-adend`
+  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-  * Fires when `ad-url` attribute is present and the ad took too long to load.
+- `stream-adtimeout`
+  - Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
index aff3f05547c7c42..44e7fb9660de859 100644
--- a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
+++ b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
@@ -176,27 +176,21 @@ The tus protocol allows you to add optional parameters in the [`Upload-Metadata`
 Setting arbitrary metadata values in the `Upload-Metadata` header sets values in the [meta key in Stream API](/api/resources/stream/methods/list/).
 
 - `name`
-
   - Setting this key will set `meta.name` in the API and display the value as the name of the video in the dashboard.
 
 - `requiresignedurls`
-
   - If this key is present, the video playback for this video will be required to use signed URLs after upload.
 
 - `scheduleddeletion`
-
   - Specifies a date and time when a video will be deleted. After a video is deleted, it is no longer viewable and no longer counts towards storage for billing. The specified date and time cannot be earlier than 30 days or later than 1,096 days from the video's created timestamp.
 
 - `allowedorigins`
-
   - An array of strings listing origins allowed to display the video. This will set the [allowed origins setting](/stream/viewing-videos/securing-your-stream/#security-considerations) for the video.
 
 - `thumbnailtimestamppct`
-
   - Specify the default thumbnail [timestamp percentage](/stream/viewing-videos/displaying-thumbnails/). Note that percentage is a floating point value between 0.0 and 1.0.
 
 - `watermark`
-
   - The watermark profile UID.
 
 ## Set creator property
diff --git a/src/content/docs/stream/uploading-videos/upload-via-link.mdx b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
index 1d7071ca08fb038..2b140c2dc1d2686 100644
--- a/src/content/docs/stream/uploading-videos/upload-via-link.mdx
+++ b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
@@ -8,11 +8,7 @@ products:
   - stream
 ---
 
-import {
-	Tabs,
-	TabItem,
-	LinkButton,
-} from "~/components"
+import { Tabs, TabItem, LinkButton } from "~/components";
 
 If you have videos stored in a cloud storage bucket, you can pass a HTTP link for the file, and Stream will fetch the file on your behalf.
 
@@ -108,45 +104,45 @@ You can optionally use [webhooks](/stream/manage-video-library/using-webhooks/)
 
 ```json {3,6}
 {
-  "result": {
-    "uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
-    "thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
-    "thumbnailTimestampPct": 0,
-    "readyToStream": false,
-    "status": {
-      "state": "downloading"
-    },
-    "meta": {
-      "downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
-      "name": "My First Stream Video"
-    },
-    "created": "2020-10-16T20:20:17.872170843Z",
-    "modified": "2020-10-16T20:20:17.872170843Z",
-    "size": 9032701,
-    "preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
-    "allowedOrigins": [],
-    "requireSignedURLs": false,
-    "uploaded": "2020-10-16T20:20:17.872170843Z",
-    "uploadExpiry": null,
-    "maxSizeBytes": 0,
-    "maxDurationSeconds": 0,
-    "duration": -1,
-    "input": {
-      "width": -1,
-      "height": -1
-    },
-    "playback": {
-      "hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
-      "dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
-    },
-    "watermark": null
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
+		"thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
+		"thumbnailTimestampPct": 0,
+		"readyToStream": false,
+		"status": {
+			"state": "downloading"
+		},
+		"meta": {
+			"downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
+			"name": "My First Stream Video"
+		},
+		"created": "2020-10-16T20:20:17.872170843Z",
+		"modified": "2020-10-16T20:20:17.872170843Z",
+		"size": 9032701,
+		"preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
+		"allowedOrigins": [],
+		"requireSignedURLs": false,
+		"uploaded": "2020-10-16T20:20:17.872170843Z",
+		"uploadExpiry": null,
+		"maxSizeBytes": 0,
+		"maxDurationSeconds": 0,
+		"duration": -1,
+		"input": {
+			"width": -1,
+			"height": -1
+		},
+		"playback": {
+			"hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+			"dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
+		},
+		"watermark": null
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 After the video is uploaded, you can use the video `uid` shown in the example response above to play the video using the [Stream video player](/stream/viewing-videos/using-the-stream-player/).
 
-If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
\ No newline at end of file
+If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
diff --git a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
index cc8a1491f78e4b0..1aa988048c1fe40 100644
--- a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
+++ b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
@@ -10,10 +10,8 @@ products:
 
 :::note
 
-
 Stream thumbnails are not supported for videos with non-square pixels.
 
-
 :::
 
 ## Use Case 1: Generating a thumbnail on-the-fly
@@ -22,29 +20,32 @@ A thumbnail from your video can be generated using a special link where you spec
 
 `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270`
 
-<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270" alt="Example of thumbnail image generated from example video" />
+<img
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270"
+	alt="Example of thumbnail image generated from example video"
+/>
 
 Using the `poster` query parameter in the embed URL, you can set a thumbnail to any time in your video. If [signed URLs](/stream/viewing-videos/securing-your-stream/) are required, you must use a signed URL instead of video UIDs.
 
 ```html
 <iframe
-  src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-  style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-  allowfullscreen="true"
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+	style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+	allowfullscreen="true"
 ></iframe>
 ```
 
 Supported URL attributes are:
 
-* **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
-* **`height`** (default `640`)
-* **`width`** (default `640`)
-* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  * **`crop`** cut parts of the video that doesn't fit in the given size
-  * **`clip`** preserve the entire frame and decrease the size of the image within given size
-  * **`scale`** distort the image to fit the given size
-  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+- **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
+- **`height`** (default `640`)
+- **`width`** (default `640`)
+- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  - **`crop`** cut parts of the video that doesn't fit in the given size
+  - **`clip`** preserve the entire frame and decrease the size of the image within given size
+  - **`scale`** distort the image to fit the given size
+  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
 
 ## Use Case 2: Set the default thumbnail timestamp using the API
 
@@ -67,17 +68,20 @@ Stream supports animated GIFs as thumbnails. Viewing animated thumbnails does no
 
 ` https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s`
 
-<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s" alt="Animated gif example, generated on-demand from Cloudflare Stream" />
+<img
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s"
+	alt="Animated gif example, generated on-demand from Cloudflare Stream"
+/>
 
 Supported URL attributes for animated thumbnails are:
 
-* **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
-* **`height`** (default `640`)
-* **`width`** (default `640`)
-* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  * **`crop`** cut parts of the video that doesn't fit in the given size
-  * **`clip`** preserve the entire frame and decrease the size of the image within given size
-  * **`scale`** distort the image to fit the given size
-  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
-* **`duration`** (default `5s`)
-* **`fps`** (default `8`)
+- **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
+- **`height`** (default `640`)
+- **`width`** (default `640`)
+- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  - **`crop`** cut parts of the video that doesn't fit in the given size
+  - **`clip`** preserve the entire frame and decrease the size of the image within given size
+  - **`scale`** distort the image to fit the given size
+  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+- **`duration`** (default `5s`)
+- **`fps`** (default `8`)
diff --git a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
index 0ae5a7967717599..979b5f8d99e2f35 100644
--- a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
+++ b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
@@ -15,134 +15,103 @@ To use this SDK, add an additional `<script>` tag to your website:
 ```html
 <!-- You can use styles and CSS on this iframe element where the video player will appear -->
 <iframe
-  src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
-  style="border: none"
-  height="720"
-  width="1280"
-  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-  allowfullscreen="true"
-  id="stream-player"
+	src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
+	style="border: none"
+	height="720"
+	width="1280"
+	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+	allowfullscreen="true"
+	id="stream-player"
 ></iframe>
 
 <script src="https://embed.cloudflarestream.com/embed/sdk.latest.js"></script>
 
 <!-- Your JavaScript code below-->
 <script>
-  const player = Stream(document.getElementById('stream-player'));
-  player.addEventListener('play', () => {
-    console.log('playing!');
-  });
-  player.play().catch(() => {
-    console.log('playback failed, muting to try again');
-    player.muted = true;
-    player.play();
-  });
+	const player = Stream(document.getElementById("stream-player"));
+	player.addEventListener("play", () => {
+		console.log("playing!");
+	});
+	player.play().catch(() => {
+		console.log("playback failed, muting to try again");
+		player.muted = true;
+		player.play();
+	});
 </script>
 ```
 
 ## Methods
 
+- `play()` Promise
+  - Start video playback.
 
-
-* `play()` Promise
-
-  * Start video playback.
-
-* `pause()` null
-
-  * Pause video playback.
-
-
+- `pause()` null
+  - Pause video playback.
 
 ## Properties
 
-
-
-* `autoplay` boolean
-
-  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+- `autoplay` boolean
+  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
 :::note
 
-
 Some browsers prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, review the [iOS video policies](https://webkit.org/blog/6784/new-video-policies-for-ios/).
 
-
 :::
 
-* `buffered` TimeRanges readonly
-
-  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+- `buffered` TimeRanges readonly
+  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-* `controls` boolean
+- `controls` boolean
+  - Sets or returns whether the video should display controls (like play/pause etc.)
 
-  * Sets or returns whether the video should display controls (like play/pause etc.)
+- `currentTime` integer
+  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-* `currentTime` integer
-
-  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
-
-* `defaultTextTrack`
-
-  * Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
+- `defaultTextTrack`
+  - Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
 
 :::note
 
-
-This will *only* work once during initialization. Beyond that point the user has full control over their text track settings.
-
+This will _only_ work once during initialization. Beyond that point the user has full control over their text track settings.
 
 :::
 
-* `duration` integer readonly
-
-  * Returns the duration of the video in seconds.
-
-* `ended` boolean readonly
-
-  * Returns whether the video has ended.
-
-* `letterboxColor` string
-
-  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
-
-* `loop` boolean
-
-  * Sets or returns whether the video should start over when it reaches the end
+- `duration` integer readonly
+  - Returns the duration of the video in seconds.
 
-* `muted` boolean
+- `ended` boolean readonly
+  - Returns whether the video has ended.
 
-  * Sets or returns whether the audio should be played with the video
+- `letterboxColor` string
+  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
 
-* `paused` boolean readonly
+- `loop` boolean
+  - Sets or returns whether the video should start over when it reaches the end
 
-  * Returns whether the video is paused
+- `muted` boolean
+  - Sets or returns whether the audio should be played with the video
 
-* `played` TimeRanges readonly
+- `paused` boolean readonly
+  - Returns whether the video is paused
 
-  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+- `played` TimeRanges readonly
+  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-* `preload` boolean
-
-  * Sets or returns whether the video should be preloaded upon element load.
+- `preload` boolean
+  - Sets or returns whether the video should be preloaded upon element load.
 
 :::note
 
-
 The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
 
-
 :::
 
-* `primaryColor` string
-
-  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
-
-* `volume` float
-
-  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
-
+- `primaryColor` string
+  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
 
+- `volume` float
+  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -150,109 +119,78 @@ The `<video>` element does not force the browser to follow the value of this att
 
 We support most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
+- `abort`
+  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
+- `canplay`
+  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-* `abort`
+- `canplaythrough`
+  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+- `durationchange`
+  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-* `canplay`
+- `ended`
+  - Sent when playback completes.
 
-  * Sent when enough data is available that the media can be played, at least for a couple of frames.
+- `error`
+  - Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-* `canplaythrough`
+- `loadeddata`
+  - The first frame of the media has finished loading.
 
-  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+- `loadedmetadata`
+  - The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
 
-* `durationchange`
+- `loadstart`
+  - Sent when loading of the media begins.
 
-  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+- `pause`
+  - Sent when the playback state is changed to paused (paused property is true).
 
-* `ended`
+- `play`
+  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
 
-  * Sent when playback completes.
+- `playing`
+  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
 
-* `error`
+- `progress`
+  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
 
-  * Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+- `ratechange`
+  - Sent when the playback speed changes.
 
-* `loadeddata`
+- `seeked`
+  - Sent when a seek operation completes.
 
-  * The first frame of the media has finished loading.
+- `seeking`
+  - Sent when a seek operation begins.
 
-* `loadedmetadata`
+- `stalled`
+  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
 
-  * The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
+- `suspend`
+  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
 
-* `loadstart`
-
-  * Sent when loading of the media begins.
-
-* `pause`
-
-  * Sent when the playback state is changed to paused (paused property is true).
-
-* `play`
-
-  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
-
-* `playing`
-
-  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
-
-* `progress`
-
-  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
-
-* `ratechange`
-
-  * Sent when the playback speed changes.
-
-* `seeked`
-
-  * Sent when a seek operation completes.
-
-* `seeking`
-
-  * Sent when a seek operation begins.
-
-* `stalled`
-
-  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
-
-* `suspend`
-
-  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
-
-* `timeupdate`
-
-  * The time indicated by the element's currentTime attribute has changed.
-
-* `volumechange`
-
-  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
-
-* `waiting`
-
-  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+- `timeupdate`
+  - The time indicated by the element's currentTime attribute has changed.
 
+- `volumechange`
+  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
+- `waiting`
+  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard Events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
+- `stream-adstart`
+  - Fires when `ad-url` attribute is present and the ad begins playback
 
+- `stream-adend`
+  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-* `stream-adstart`
-
-  * Fires when `ad-url` attribute is present and the ad begins playback
-
-* `stream-adend`
-
-  * Fires when `ad-url` attribute is present and the ad finishes playback
-
-* `stream-adtimeout`
-
-  * Fires when `ad-url` attribute is present and the ad took too long to load.
-
+- `stream-adtimeout`
+  - Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
index 4d5dded596a44eb..e65a1289cbbf95e 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
@@ -14,7 +14,7 @@ The purpose of Deprecated API content is to communicate that Cloudflare no longe
 
 instructional, straightforward
 
-## content\_type
+## content_type
 
 `reference`
 
@@ -24,7 +24,7 @@ instructional, straightforward
 
 **Deprecated endpoint name**: Must match what existed in the non-deprecated [Endpoint](/style-guide/api-content-strategy/api-content-types/endpoints/).
 
-**Context**:  Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
+**Context**: Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
 
 **Replacement**: A description of and/or link to the alternative endpoint OR an explanation as to why Cloudflare is removing the capability of that endpoint.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
index f73e8c33466bbfe..6529edfc70b1ed6 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
@@ -18,21 +18,19 @@ An endpoint is used to make HTTPS requests, and the `GET`, `POST`, `PUT`, `PATCH
 
 :::note
 
-
 The required components apply to newly created endpoints. Existing endpoints will **not** be modified.
 
-
 :::
 
 **Title**: Title of the endpoint using sentence casing (first word capitalized). The titles do not use punctuation marks at the end of the title. Simple cases usually take one of the following forms:
 
 Endpoints that act on/return a single item: verb + indefinite article + singular resource name.
 
-* Example: Get a list item
+- Example: Get a list item
 
 Endpoints that act on/return a collection of items: verb + plural resource name.
 
-* Example: Get list items
+- Example: Get list items
 
 **Description**: Describes what the endpoint does or how it should be used. Use punctuation at the end of the description.
 
@@ -54,11 +52,11 @@ When writing the titles and descriptions, keep our voice and tone in mind. Be co
 
 Below are some examples of endpoint titles and descriptions for reference:
 
-* **Get domain**: Fetches a single domain.
-* **List workers**: Fetches a list of uploaded workers.
-* **List pools**: Lists configured pools.
-* **Create waiting room**: Creates a new waiting room.
-* **Update health check**: Updates configured health checks.
+- **Get domain**: Fetches a single domain.
+- **List workers**: Fetches a list of uploaded workers.
+- **List pools**: Lists configured pools.
+- **Create waiting room**: Creates a new waiting room.
+- **Update health check**: Updates configured health checks.
 
 ## Example
 
@@ -70,4 +68,4 @@ Below are some examples of endpoint titles and descriptions for reference:
 
 **Method**: `GET`
 
-**Endpoint**: user/audit\_logs
+**Endpoint**: user/audit_logs
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
index 5b998bffe2e51f0..59e3387e3c346d0 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
index a31e895ce8f45c1..aebb7c2e49d8230 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
@@ -46,7 +46,7 @@ Below are some examples of parameter descriptions for reference:
 
 **version**: The Cloudflare One Client version.
 
-**per\_page**: Sets the maximum number of requested results.
+**per_page**: Sets the maximum number of requested results.
 
 **enabled**: Enables or disable a load balancer.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
index 26a17b8a4f34fc5..c24e2857250568e 100644
--- a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
@@ -21,9 +21,9 @@ To automatically incorporate our conventions into your examples, use:
 
 Use long parameter names for clarity:
 
-* `--header` (instead of `-H`)
-* `--request` (when needed, instead of `-X`)
-* `--data` (instead of `-d`)
+- `--header` (instead of `-H`)
+- `--request` (when needed, instead of `-X`)
+- `--data` (instead of `-d`)
 
 You do not need to use the `--url` parameter since it is the main cURL parameter. Also, the URL does not need to be enclosed in double quotes (`""`), except if it contains a `?` character (that is, when it includes a query string).
 
@@ -45,9 +45,9 @@ If you must suggest the use of this tool, you can add a link to the [Make API ca
 
 ### Preliminary notes
 
-* Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
-* Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
-* Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
+- Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
+- Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
+- Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
 
 The same placeholder name should correspond to the same value – use different placeholder names for different ID values. You can use the same request placeholders in the response, if they should match the values in the request.
 
@@ -149,7 +149,7 @@ Enclose the JSON payload ( the `--data` command-line argument) in single quotes
 
 The recommended way of escaping a single quote inside the body is the following (assuming the user will run the command in a bash-like terminal):
 
-* Replace the single quote `'` with `'\''`
+- Replace the single quote `'` with `'\''`
 
 Which means "close string, add escaped single quote, begin string again".
 
@@ -203,28 +203,28 @@ A response starts either with an object (`{ ... }`) or a list (`[ ... ]`). The i
 (}|])
 ```
 
-* If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
-* Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
+- If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
+- Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
 
 ### Full response example
 
 ```json
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "paused": false,
-    "description": "do not challenge login from office",
-    "action": "allow",
-    "priority": null,
-    "filter": {
-      "id": "<FILTER_ID>",
-      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-      "paused": false,
-      "description": "Login from office"
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"paused": false,
+		"description": "do not challenge login from office",
+		"action": "allow",
+		"priority": null,
+		"filter": {
+			"id": "<FILTER_ID>",
+			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+			"paused": false,
+			"description": "Login from office"
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/style-guide/components/anchor-heading.mdx b/src/content/docs/style-guide/components/anchor-heading.mdx
index 22d6bd5d8b60e19..3a3195eb29ef0a3 100644
--- a/src/content/docs/style-guide/components/anchor-heading.mdx
+++ b/src/content/docs/style-guide/components/anchor-heading.mdx
@@ -17,7 +17,11 @@ The `AnchorHeading` component defines headings. Specifically, `AnchorHeading` pe
 ```mdx live
 import { AnchorHeading } from "~/components";
 
-<AnchorHeading title="How to use AnchorHeading" slug="use-anchorheading" depth={2} />
+<AnchorHeading
+	title="How to use AnchorHeading"
+	slug="use-anchorheading"
+	depth={2}
+/>
 ```
 
 Markdown files (including partials) have this behavior by default, applied via rehype plugins. Therefore, the `AnchorHeading` component is usually only required when writing headings yourself inside components, or when working on non-markdown files.
@@ -25,7 +29,8 @@ Markdown files (including partials) have this behavior by default, applied via r
 To override the ID given to a heading within Markdown, add an MDX comment at the end of the line:
 
 ```mdx live
-## foo {/*bar*/}
+## foo {/* bar */}
+
 {/* HTML: <h2 id="bar">foo</h2> */}
 ```
 
@@ -33,4 +38,4 @@ To override the ID given to a heading within Markdown, add an MDX comment at the
 
 The `AnchorHeading` component emulates the behavior of the [`rehype-slug`](https://github.com/rehypejs/rehype-slug) and the [`rehype-autolink-headings`](https://github.com/rehypejs/rehype-autolink-headings). It adds an `id` based on the output of [`github-slugger`](https://github.com/Flet/github-slugger/) to the heading, as well as adding a button to copy a link to that particular heading.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/style-guide/components/available-notifications.mdx b/src/content/docs/style-guide/components/available-notifications.mdx
index 52d9d0e9f2ec6d7..ef0ad606272bc27 100644
--- a/src/content/docs/style-guide/components/available-notifications.mdx
+++ b/src/content/docs/style-guide/components/available-notifications.mdx
@@ -14,14 +14,19 @@ import { AvailableNotifications } from "~/components";
 
 <AvailableNotifications product="Traffic Monitoring" />
 <AvailableNotifications
-    product="dns"
-    notificationFilter="Secondary DNS all Primaries Failing"
+	product="dns"
+	notificationFilter="Secondary DNS all Primaries Failing"
 />
 ```
 
 ## Notifications
 
-import { Code } from "~/components"
-import glossary from "~/content/notifications/index.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/notifications/index.yaml?raw";
 
-<Code title="/src/content/notifications/index.yaml" code={glossary} lang="yaml" wrap={true} />
\ No newline at end of file
+<Code
+	title="/src/content/notifications/index.yaml"
+	code={glossary}
+	lang="yaml"
+	wrap={true}
+/>
diff --git a/src/content/docs/style-guide/components/description.mdx b/src/content/docs/style-guide/components/description.mdx
index 4d91bb6f10f8f27..75456e07bf8c711 100644
--- a/src/content/docs/style-guide/components/description.mdx
+++ b/src/content/docs/style-guide/components/description.mdx
@@ -8,9 +8,7 @@ products:
 ---
 
 ```mdx live
-import { Description } from "~/components"
+import { Description } from "~/components";
 
-<Description>
-    Hello, world!
-</Description>
-```
\ No newline at end of file
+<Description>Hello, world!</Description>
+```
diff --git a/src/content/docs/style-guide/components/example.mdx b/src/content/docs/style-guide/components/example.mdx
index eb0ba2069a80284..2d3de76617e19e9 100644
--- a/src/content/docs/style-guide/components/example.mdx
+++ b/src/content/docs/style-guide/components/example.mdx
@@ -10,17 +10,13 @@ products:
 Use the `<Example>` component to add a box around some content. This can be useful when you want to demonstrate or showcase something without it being confused by the surrounding text.
 
 ```mdx live
-import { Example } from "~/components"
+import { Example } from "~/components";
 
-<Example>
-    Hello, world!
-</Example>
+<Example>Hello, world!</Example>
 
-{/*
-    `title` is an optional string which customizes the title of your example card
-*/}
+{/_
+`title` is an optional string which customizes the title of your example card
+_/}
 
-<Example title="Hello world">
-    Hello, world!
-</Example>
-```
\ No newline at end of file
+<Example title="Hello world">Hello, world!</Example>
+```
diff --git a/src/content/docs/style-guide/components/feature-table.mdx b/src/content/docs/style-guide/components/feature-table.mdx
index 7018dd906b70056..c839be1febca17e 100644
--- a/src/content/docs/style-guide/components/feature-table.mdx
+++ b/src/content/docs/style-guide/components/feature-table.mdx
@@ -14,7 +14,7 @@ If the feature information includes an `Availability` row and you would like to
 This component pulls information from the `index.json` file in `src/content/plans/`.
 
 ```mdx live
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 <FeatureTable id="analytics.logpush" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/feature.mdx b/src/content/docs/style-guide/components/feature.mdx
index ce6073fbff74c41..1b795ccb977fbf1 100644
--- a/src/content/docs/style-guide/components/feature.mdx
+++ b/src/content/docs/style-guide/components/feature.mdx
@@ -12,15 +12,15 @@ The `<Feature>` component lists features available in the product and provides a
 The header parameter supplies the feature name and the href parameter supplies the link to the feature. Text wrapped in the component supplies the description.
 
 ```mdx
-import { Feature } from "~/components"
+import { Feature } from "~/components";
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-   Hello, world!
+	Hello, world!
 </Feature>
 ```
 
-import { Feature } from "~/components"
+import { Feature } from "~/components";
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-   Hello, world!
+	Hello, world!
 </Feature>
diff --git a/src/content/docs/style-guide/components/glossary-definition.mdx b/src/content/docs/style-guide/components/glossary-definition.mdx
index 379a96198932f4f..7a95c0d7c2a7584 100644
--- a/src/content/docs/style-guide/components/glossary-definition.mdx
+++ b/src/content/docs/style-guide/components/glossary-definition.mdx
@@ -12,14 +12,18 @@ Use the this component to add extra information to an existing glossary entry. `
 ## Component
 
 ```mdx live
-import { GlossaryDefinition } from "~/components"
+import { GlossaryDefinition } from "~/components";
 
 <GlossaryDefinition term="example" prepend="The definition for example is: " />
 ```
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
 
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/glossary-tooltip.mdx b/src/content/docs/style-guide/components/glossary-tooltip.mdx
index 0efadd82370ed12..8f0e06da3c09d3d 100644
--- a/src/content/docs/style-guide/components/glossary-tooltip.mdx
+++ b/src/content/docs/style-guide/components/glossary-tooltip.mdx
@@ -22,7 +22,11 @@ import { GlossaryTooltip } from "~/components"
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
-
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
+
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/glossary.mdx b/src/content/docs/style-guide/components/glossary.mdx
index 1bf06744eadfba7..df05ad6c06dab82 100644
--- a/src/content/docs/style-guide/components/glossary.mdx
+++ b/src/content/docs/style-guide/components/glossary.mdx
@@ -14,14 +14,18 @@ Create the glossary entries in a file dedicated to your product. These YAML file
 ## Component
 
 ```mdx live
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 <Glossary />
 ```
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
 
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/inline-badge.mdx b/src/content/docs/style-guide/components/inline-badge.mdx
index b0c325af0bf4068..6e49dc901618e2c 100644
--- a/src/content/docs/style-guide/components/inline-badge.mdx
+++ b/src/content/docs/style-guide/components/inline-badge.mdx
@@ -12,17 +12,18 @@ products:
 Our current recommendation is to avoid inline badges, since they may hurt readability.
 
 Guidelines:
+
 - Mention beta/alpha/early access in the feature's main documentation page (use the [`<Badge>`](/style-guide/components/badges/) component for this purpose).
 - If an additional reference is needed in the middle of the text, use "(beta)", with no special formatting, after the feature name.
 - For instructions related to the feature (such as instructions on turning the feature on or off), you may mention again it's in beta, and also include "(beta)" in the side nav.
-:::
+  :::
 
 ## Component
 
 To adopt this styling in a React component, apply the `sl-badge` class to a `span` element.
 
 ```mdx live
-import { InlineBadge } from '~/components';
+import { InlineBadge } from "~/components";
 
 ### Alpha <InlineBadge preset="alpha" />
 
@@ -44,24 +45,24 @@ Either `preset` or `text` and `variant` must be specified.
 ### Presets
 
 - `alpha`
-    - **Text**: `Alpha`
-    - **Variant** `success`
+  - **Text**: `Alpha`
+  - **Variant** `success`
 
 - `beta`
-    - **Text**: `Beta`
-    - **Variant** `caution`
+  - **Text**: `Beta`
+  - **Variant** `caution`
 
 - `deprecated`
-    - **Text**: `Deprecated`
-    - **Variant** `danger`
+  - **Text**: `Deprecated`
+  - **Variant** `danger`
 
 - `early-access`
-    - **Text**: `Early Access`
-    - **Variant** `note`
+  - **Text**: `Early Access`
+  - **Variant** `note`
 
 - `legacy`
-    - **Text**: `Legacy`
-    - **Variant** `danger`
+  - **Text**: `Legacy`
+  - **Variant** `danger`
 
 ### Text
 
@@ -70,16 +71,16 @@ Any string.
 ### Variant
 
 - `note`
-    - **Color**: Blue
+  - **Color**: Blue
 
 - `tip`
-    - **Color**: Purple
+  - **Color**: Purple
 
 - `danger`
-    - **Color**: Red
+  - **Color**: Red
 
 - `caution`
-    - **Color**: Orange
+  - **Color**: Orange
 
 - `success`
-    - **Color**: Green
\ No newline at end of file
+  - **Color**: Green
diff --git a/src/content/docs/style-guide/components/link-cards.mdx b/src/content/docs/style-guide/components/link-cards.mdx
index da6aaeafc9831a0..0adc8e6059e72d6 100644
--- a/src/content/docs/style-guide/components/link-cards.mdx
+++ b/src/content/docs/style-guide/components/link-cards.mdx
@@ -8,21 +8,21 @@ products:
 ---
 
 ```mdx live wrap
-import { CardGrid, LinkCard } from "~/components"
+import { CardGrid, LinkCard } from "~/components";
 
 <LinkCard
-    title="foo"
-    description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-    href="/style-guide/components/link-cards/"
+	title="foo"
+	description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+	href="/style-guide/components/link-cards/"
 />
 
 <CardGrid>
-{[...Array(4).keys()].map(() => (
-    <LinkCard
-        title="foo"
-        description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-        href="/style-guide/components/link-cards/"
-    />
-))}
+	{[...Array(4).keys()].map(() => (
+		<LinkCard
+			title="foo"
+			description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+			href="/style-guide/components/link-cards/"
+		/>
+	))}
 </CardGrid>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/list-tutorials.mdx b/src/content/docs/style-guide/components/list-tutorials.mdx
index c225a6b23e4a78c..c67b80ab5057fa1 100644
--- a/src/content/docs/style-guide/components/list-tutorials.mdx
+++ b/src/content/docs/style-guide/components/list-tutorials.mdx
@@ -15,4 +15,4 @@ import { ListTutorials } from "~/components";
 
 ## Associated content types
 
-- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
\ No newline at end of file
+- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
diff --git a/src/content/docs/style-guide/components/package-managers.mdx b/src/content/docs/style-guide/components/package-managers.mdx
index 7b9c3137bd4b3b3..4c5f8298b9152d9 100644
--- a/src/content/docs/style-guide/components/package-managers.mdx
+++ b/src/content/docs/style-guide/components/package-managers.mdx
@@ -10,7 +10,7 @@ products:
 This component is provided by the [`starlight-package-managers` package.](https://github.com/HiDeoo/starlight-package-managers)
 
 ```mdx live
-import { PackageManagers } from "~/components"
+import { PackageManagers } from "~/components";
 
 <PackageManagers pkg="wrangler" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/pages-build-preset.mdx b/src/content/docs/style-guide/components/pages-build-preset.mdx
index 976dc1433f725e5..3480c8339307db2 100644
--- a/src/content/docs/style-guide/components/pages-build-preset.mdx
+++ b/src/content/docs/style-guide/components/pages-build-preset.mdx
@@ -8,8 +8,8 @@ products:
 ---
 
 ```mdx live
-import { PagesBuildPreset } from "~/components"
+import { PagesBuildPreset } from "~/components";
 
 <PagesBuildPreset framework="gatsby" />
 <PagesBuildPreset framework="next-js" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/plan.mdx b/src/content/docs/style-guide/components/plan.mdx
index 07b591b1274a686..1b1457fa37ceb98 100644
--- a/src/content/docs/style-guide/components/plan.mdx
+++ b/src/content/docs/style-guide/components/plan.mdx
@@ -14,9 +14,8 @@ To specify a special feature use `<Plan id="<FIRST_PRODUCT>.<SECOND-PRODUCT>.pro
 
 Refer to the examples below for more information.
 
-
 ```mdx live
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
 <Plan type="all" />
 <Plan type="paid" />
@@ -27,4 +26,4 @@ import { Plan } from "~/components"
 <Plan type="workers-all" />
 <Plan type="workers-paid" />
 <Plan id="web3.ethereum.properties.availability.summary" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/product-availability-text.mdx b/src/content/docs/style-guide/components/product-availability-text.mdx
index 83689f8bbba4207..77e2bca0cf78b1d 100644
--- a/src/content/docs/style-guide/components/product-availability-text.mdx
+++ b/src/content/docs/style-guide/components/product-availability-text.mdx
@@ -19,10 +19,10 @@ Cloud Connector <ProductAvailabilityText product="cloud-connector" /> allows you
 
 ## Props
 
-| Prop | Type | Required | Default | Description |
-| --- | --- | --- | --- | --- |
-| `product` | `string` | Yes | — | Product slug matching a file in `src/content/directory/`. |
-| `parentheses` | `string` | No | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
+| Prop          | Type     | Required | Default  | Description                                                                                                |
+| ------------- | -------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------- |
+| `product`     | `string` | Yes      | —        | Product slug matching a file in `src/content/directory/`.                                                  |
+| `parentheses` | `string` | No       | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
 
 ## Behavior
 
diff --git a/src/content/docs/style-guide/components/product-features.mdx b/src/content/docs/style-guide/components/product-features.mdx
index 199e0ded2498a76..bea56b72ab74c5e 100644
--- a/src/content/docs/style-guide/components/product-features.mdx
+++ b/src/content/docs/style-guide/components/product-features.mdx
@@ -10,6 +10,7 @@ products:
 Use when you need to list all available features within a product grouping inside of the `index.json` file in `src/content/plans/`. For the id property, specify the product object you want to use.
 
 ```mdx live
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
-<ProductFeatures id="dns" />
\ No newline at end of file
+<ProductFeatures id="dns" />
+```
diff --git a/src/content/docs/style-guide/components/related-product.mdx b/src/content/docs/style-guide/components/related-product.mdx
index 8de8d8c11cdca07..99c45329075a2a1 100644
--- a/src/content/docs/style-guide/components/related-product.mdx
+++ b/src/content/docs/style-guide/components/related-product.mdx
@@ -17,10 +17,11 @@ Use in Overview pages.
 import { RelatedProduct } from "~/components";
 
 <RelatedProduct header="R2" href="/r2/" product="r2">
-    Store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.
+	Store large amounts of unstructured data without the costly egress bandwidth
+	fees associated with typical cloud storage services.
 </RelatedProduct>
 
 <RelatedProduct header="Images" href="/images/" product="images">
-    A suite of products tailored to your image-processing needs.
+	A suite of products tailored to your image-processing needs.
 </RelatedProduct>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/rule-id.mdx b/src/content/docs/style-guide/components/rule-id.mdx
index d2a33c41ef0ebd7..f5b213de131b2bc 100644
--- a/src/content/docs/style-guide/components/rule-id.mdx
+++ b/src/content/docs/style-guide/components/rule-id.mdx
@@ -8,7 +8,7 @@ products:
 ---
 
 ```mdx live
-import { RuleID } from "~/components"
+import { RuleID } from "~/components";
 
 <RuleID id="abcdefghijklmnopqrstuvwxyz" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/steps.mdx b/src/content/docs/style-guide/components/steps.mdx
index 26b09c984dee440..a8ad45e2b122573 100644
--- a/src/content/docs/style-guide/components/steps.mdx
+++ b/src/content/docs/style-guide/components/steps.mdx
@@ -15,4 +15,4 @@ import { Steps } from "~/components"
 2. Wrap your numbered list in the `Steps` components
 3. Done!
 </Steps>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
index 824d45bb57c3001..7208cf19466a58c 100644
--- a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
+++ b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
@@ -40,7 +40,7 @@ An optional object containing `base` (`string`) and `subtract` (`string[]`) prop
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
 	}}
 />
 
@@ -51,7 +51,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
 	}}
 />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/type-highlighting.mdx b/src/content/docs/style-guide/components/type-highlighting.mdx
index a95852acfc7dc55..26f7c06002aa2bb 100644
--- a/src/content/docs/style-guide/components/type-highlighting.mdx
+++ b/src/content/docs/style-guide/components/type-highlighting.mdx
@@ -32,4 +32,4 @@ import { Type, MetaInfo } from "~/components";
   - The name of your service.
 - `local` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
   - If the service should run locally or not.
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/usage.mdx b/src/content/docs/style-guide/components/usage.mdx
index 337c49995287617..b1548e52b571c45 100644
--- a/src/content/docs/style-guide/components/usage.mdx
+++ b/src/content/docs/style-guide/components/usage.mdx
@@ -11,4 +11,4 @@ import { ComponentsUsage } from "~/components";
 
 This page contains a breakdown of each component and the pages where they are used.
 
-<ComponentsUsage />
\ No newline at end of file
+<ComponentsUsage />
diff --git a/src/content/docs/style-guide/components/wrangler-namespace.mdx b/src/content/docs/style-guide/components/wrangler-namespace.mdx
index fab2bbf305de528..6ebac49e56a3019 100644
--- a/src/content/docs/style-guide/components/wrangler-namespace.mdx
+++ b/src/content/docs/style-guide/components/wrangler-namespace.mdx
@@ -32,4 +32,4 @@ import { WranglerNamespace } from "~/components";
 - `namespace` <Type text="string" /> <MetaInfo text="required" />
   - The namespace to pull the related commands from (`d1`, `hyperdrive`).
 - `headingLevel` <Type text="boolean" /> <MetaInfo text="(default: 2) optional" />
-  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
\ No newline at end of file
+  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
diff --git a/src/content/docs/style-guide/components/youtube.mdx b/src/content/docs/style-guide/components/youtube.mdx
index 8b24f0d71780445..b7dd62471b86ad2 100644
--- a/src/content/docs/style-guide/components/youtube.mdx
+++ b/src/content/docs/style-guide/components/youtube.mdx
@@ -7,12 +7,12 @@ products:
   - style-guide
 ---
 
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 <YouTube id="XHvmX3FhTwU" />
 
 ```mdx
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 <YouTube id="XHvmX3FhTwU" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/contributions.mdx b/src/content/docs/style-guide/contributions.mdx
index 5921a50b9de6eba..26f56188f64db34 100644
--- a/src/content/docs/style-guide/contributions.mdx
+++ b/src/content/docs/style-guide/contributions.mdx
@@ -2,23 +2,27 @@
 title: Contributions
 description: Learn how to contribute to the Cloudflare Docs.
 sidebar:
-    order: 1
+  order: 1
 products:
   - style-guide
 ---
+
 import { Details } from "~/components";
 
 The [Cloudflare Docs](https://developers.cloudflare.com/) are open source and hosted on the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs) on GitHub. This means that anyone, including those who are not part of the Cloudflare organization, can contribute to them. We welcome all suggestions that help keep our docs high quality and up to date.
 
 To contribute to our docs, you will need to [create an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) (if you do not have one already) and log in. Then you have three options:
-* [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
-* [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
-* [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
+
+- [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
+- [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
+- [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
 
 In addition to using the [Cloudflare Style Guide](/style-guide/) for guidance on grammar and style, we recommend browsing our [components](/style-guide/components/) to add additional formatting such as buttons, tabs, and collapsible sections.
 
 ## Create a GitHub issue
+
 To create a GitHub issue:
+
 1. [Log in to GitHub](https://github.com/login) and go to the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs).
 2. Select **Issues** and then **New issue**.
 3. Select the issue type, fill out the form, and select **Create**.
@@ -26,53 +30,63 @@ To create a GitHub issue:
 [Learn more about creating GitHub issues.](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue)
 
 ## Quick edit
+
 To quickly create a pull request using the edit button:
+
 1. [Log in to GitHub](https://github.com/login).
 2. Go to the page you want to edit in the [Cloudflare Docs](https://developers.cloudflare.com/)
 3. Select <Details header="**Edit** or **Edit page**">Every page in the Cloudflare Docs (including this one) has an **Edit** button on the right sidebar and an **Edit page** button on the very bottom of the page.
- ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
-The page's Markdown opens.
-	:::note
-	The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
-	:::
+   ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
+   The page's Markdown opens.
+   :::note
+   The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
+   :::
 4. Make your edits and select **Commit changes**.
 5. In the form, update the **Commit message** with the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 6. Update the **Extended description** with more details about what you changed and why. The more details, the better.
 7. Select **Propose changes** > **Create pull request** > **Create pull request** again.
 
 ## Full development
+
 To edit and create a pull request with the [full development workflow](https://docs.github.com/en/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace):
+
 1. [Log in to GitHub](https://github.com/login) and [fork the cloudflare-docs repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
 2. If you are editing in your web browser (with [Codespaces](https://docs.github.com/en/codespaces)), move on to step 3.
-<br/>If you are editing on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)):
-	* (Required) Install [Node.js](https://nodejs.org/en) (version 24 or later).
-	* (Recommended, but not required) Install [Volta](https://volta.sh/) for easier package management.
-	* (Required) [Clone the fork to your local machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
+   <br />
+   If you are editing on your local machine (with [Visual Studio
+   Code](https://code.visualstudio.com/)): * (Required) Install
+   [Node.js](https://nodejs.org/en) (version 24 or later). * (Recommended, but
+   not required) Install [Volta](https://volta.sh/) for easier package
+   management. * (Required) [Clone the fork to your local
+   machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
 3. Create a branch from your fork (or from your clone).
-3. Make your edits.
-:::note[Preview your edits]
-To preview your edits, you need to install `pnpm`.
- ```bash
- pnpm install
- ```
+4. Make your edits.
+   :::note[Preview your edits]
+   To preview your edits, you need to install `pnpm`.
+
+```bash
+pnpm install
+```
+
 Then, run `pnpm run dev`.
- ```bash
- pnpm run dev
- ```
+
+```bash
+pnpm run dev
+```
+
 A link will appear in the terminal, `https://localhost:1111/`, where you can preview your edits. This link automatically updates with any new edits you make.
-:::
-5. Commit your changes.
-6. Push your commits to your branch and then back to your fork.
-7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
+::: 5. Commit your changes. 6. Push your commits to your branch and then back to your fork. 7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 
 ## After you create an issue or PR
+
 After you create an issue or PR, a member of the Cloudflare organization will review your suggestion. Here is what to expect:
-* A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
-* If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
-* If your changes are approved:
-	* For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
-	* For GitHub PRs, the Cloudflare member will merge your PR.
-* If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
+
+- A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
+- If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
+- If your changes are approved:
+  - For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
+  - For GitHub PRs, the Cloudflare member will merge your PR.
+- If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
 
 Thank you for contributing to our open-source ecosystem and being a part of the Cloudflare community.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
index 899c473a810e03e..38e5c2fa935864f 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
@@ -18,9 +18,9 @@ When at all possible, Cloudflare seeks to avoid creating static representations
 
 Potential examples include:
 
-* Exhaustive listing of fields
-* Replicating API content in developer docs
-* Maintaining lists of potential options in the UI (i.e., Alert types)
-* Verified Bots
+- Exhaustive listing of fields
+- Replicating API content in developer docs
+- Maintaining lists of potential options in the UI (i.e., Alert types)
+- Verified Bots
 
 The preferred approach would be speak more generally to the categories or specific, high-value fields.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
index 335031ce0afc95f..f02e3493fdef2c0 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
@@ -12,14 +12,12 @@ A code sample or line of text that shows the specific structure of a request/res
 
 :::note
 
-
 If you are unsure about when to categorize something as an example or tutorial, remember:
 
 Examples are a component attribute and are typically a snippet of code a user might copy and paste to run a task. Examples should not have multiple steps. A tutorial might contain an example, but an example will not contain a tutorial.
 
 Tutorials are a content type, typically longer form, and contain multiple steps to help users connect products to real-world scenarios.
 
-
 :::
 
 ## Used in
@@ -36,9 +34,9 @@ Explain what the code sample does in a short sentence.
 
 These could include:
 
-* Example requests and responses
-* Example inputs and outputs
-* Field values for UI and/or API
+- Example requests and responses
+- Example inputs and outputs
+- Field values for UI and/or API
 
 ## Additional information
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
index eb6cc09d35a217d..d2ac5552b440a7c 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
@@ -56,21 +56,16 @@ entries:
 Relevant values include the following:
 
 - `productName` string required
-
   - Core product associated with this file. Should always match the same formatting / styling used in `associated_products`.
 
 - `entries` object required
-
   - `term` string required
-
     - The glossary term itself.
 
   - `general_definition` string required
-
     - Definition of the term. Should be general enough to apply to multiple products. Should also start with a lowercase letter unless starting with a proper noun.
 
   - `associated_products` array optional
-
     - If the term is associated with other products. Any names used should correspond to the `productName` of that associated file.
 
 ### Usage
@@ -109,11 +104,9 @@ Is a quoted definition that comes from:
 Properties are:
 
 - `term` string required
-
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
-
   - Text to add before a definition.
 
 #### Glossary tooltip
@@ -129,15 +122,12 @@ Here's a <GlossaryTooltip term="active zone">tooltip</GlossaryTooltip> example.
 Properties are:
 
 - `term` string required
-
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
-
   - Text to add before a definition.
 
 - `link` string optional
-
   - Wraps the inner text in a markdown link, similar to normal markdown formatting.
 
 Because of space limitations, the tooltip will always default to the short definition of a term, meaning the definition text before the first line break.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
index 0e75f19c6dc5e99..6027b8e869f159d 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
index 017decd9096ef80..c412e4ff4c12769 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
@@ -28,15 +28,15 @@ This reference architecture is designed for IT or security professionals with so
 
 To build a stronger baseline understanding of Cloudflare, we recommend the following resources:
 
-* What is Cloudflare? | Website (5 minute read) or video (2 minutes)
-* Solution Brief: Cloudflare One (3 minute read)
-* Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
-* Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
+- What is Cloudflare? | Website (5 minute read) or video (2 minutes)
+- Solution Brief: Cloudflare One (3 minute read)
+- Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
+- Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
 
 Those who read this reference architecture will learn:
 
-* How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
-* How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
-* How to plan for deploying Cloudflare One
+- How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
+- How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
+- How to plan for deploying Cloudflare One
 
 While this document examines Cloudflare One at a technical level, it does not offer fine detail about every product in the platform. Instead, it looks at how all the services in Cloudflare One enable networking and network security to be consolidated on one architecture. Visit the developer documentation for further information specific to a product area or use case.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
index 5935c28d4a85d09..aa2c818fd681979 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
@@ -44,15 +44,15 @@ Cross-links between related pages create a navigable knowledge graph. When an AI
 
 Every page with a `pcx_content_type` should include links to related pages in its **Related resources** section. Use the following table to determine which content types to link to from each page.
 
-| Content type | Must link to |
-| --- | --- |
-| Concept | Related how-to or get-started page; related reference page |
-| How-to | Prerequisite concept page; relevant configuration page; troubleshooting page |
-| Get started | Next-level how-to pages; product overview page |
-| Troubleshooting | Related how-to page; relevant configuration page |
-| Configuration | Parent how-to or get-started page; relevant concept page |
-| Reference | Related concept page; how-to pages that use the reference |
-| Tutorial | Related product overview; prerequisite get-started page |
+| Content type    | Must link to                                                                 |
+| --------------- | ---------------------------------------------------------------------------- |
+| Concept         | Related how-to or get-started page; related reference page                   |
+| How-to          | Prerequisite concept page; relevant configuration page; troubleshooting page |
+| Get started     | Next-level how-to pages; product overview page                               |
+| Troubleshooting | Related how-to page; relevant configuration page                             |
+| Configuration   | Parent how-to or get-started page; relevant concept page                     |
+| Reference       | Related concept page; how-to pages that use the reference                    |
+| Tutorial        | Related product overview; prerequisite get-started page                      |
 
 Links should be bidirectional. If a concept page links to a how-to, the how-to should link back to the concept page. This ensures that users (and AI systems) can traverse between pages in either direction.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
index 7971b04fd461597..6bd0cb8c746ca6e 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
@@ -20,7 +20,7 @@ If an operation occurs inside of a code block, use the formatting associated wit
 
 ## Example
 
-| Correct                       | Incorrect         |
-| ----------------------------- | ----------------- |
-| 25 / 30                       | 25/30             |
+| Correct             | Incorrect         |
+| ------------------- | ----------------- |
+| 25 / 30             | 25/30             |
 | `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏` | e(aP,bQ)=e(P,Q)ab |
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
index dd344888b67b5bd..365813c38ea3809 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
@@ -20,9 +20,9 @@ One to two sentences
 
 It should answer:
 
-* What happens now?
-* What was the end result of the procedure?
-* What do users do next?
+- What happens now?
+- What was the end result of the procedure?
+- What do users do next?
 
 ## Cross-linking
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
index f17397285f578bf..59f4a527a66fde9 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
@@ -52,7 +52,7 @@ Use a warning to alert a reader to behavior that could impact the security of a
 
 ## Recommendations
 
-* **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
-* **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
-* **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
-* **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
+- **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
+- **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
+- **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
+- **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
index b0d981549ac0adf..f696235502bd1f7 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
@@ -14,10 +14,10 @@ The information architecture (IA) of the Cloudflare developer documentation foll
 
 At launch, Cloudflare Developer Platform products are recommended to include the following high-level sections. The following is a recommended guideline based on standard user journey flow (Learn, Get started, Configure, Test, Deploy, Asses, Maintain, etc.) and is intended to serve as a helpful reference to the documentation writer and collaborators. Depending on the product and as products mature, the IA may grow out of this structure or differ from this structure based on what you can do with the product. For an example of a more mature product that differs from this IA, refer to the [Cloudflare Stream documentation](/stream/).
 
-* [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
-* [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
-* [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
-* Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
-* [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
-* [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
-* Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
+- [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
+- [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
+- [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
+- Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
+- [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
+- [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
+- Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
diff --git a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
index 1b38177313b1f44..5ec373d9988218e 100644
--- a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
+++ b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
@@ -80,9 +80,9 @@ In nested menus, use bold for the word not the symbol.
 
 Example: **Dashboard** > **This** > **That**
 
-## *Italics*
+## _Italics_
 
-Use *italics* when referring to an option that customers can select from, like in dropdown menus.
+Use _italics_ when referring to an option that customers can select from, like in dropdown menus.
 
 Do not use italics when referring to the state of a toggle - for example, enabled/disabled should not be italicized.
 
@@ -94,32 +94,32 @@ Text in this font denotes text or characters that you should enter from the keyb
 
 ### Examples of elements we monospace
 
-| Element                                                    | Example                                                                                                    |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
-| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                       |
-| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                              |
-| API commands                                               | The endpoint supports `GET` for JSON format.                                                               |
-| Terminal commands                                          | Run the command `wrangler login`.                                                                          |
-| Attribute names and values                                 | `type`, `name`                                                                                             |
-| Class names                                                | `button-primary`                                                                                           |
-| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                   |
-| Data types                                                 | (`string`, `number`, `int64`)                                                                              |
-| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                         |
-| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink.  |
-| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                  |
-| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                         |
-| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                     |
-| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                        |
-| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                            |
-| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                      |
-| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx. |
-| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                       |
-| HTTP header names                                          | `Content-Length`                                                                                           |
-| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                               |
-| IAM role names                                             | `roles/storage.admin`                                                                                      |
-| Language keywords                                          | `in`, `await`                                                                                              |
-| Method and function names                                  | `handleRequest`                                                                                            |
-| Namespace aliases                                          | `numpy`                                                                                                    |
-| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                         |
-| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                     |
-| Text input                                                 | `"Hello Worker"`                                                                                           |
+| Element                                                    | Example                                                                                                                                                                                      |
+| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                                                                                                         |
+| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                                                                                                                |
+| API commands                                               | The endpoint supports `GET` for JSON format.                                                                                                                                                 |
+| Terminal commands                                          | Run the command `wrangler login`.                                                                                                                                                            |
+| Attribute names and values                                 | `type`, `name`                                                                                                                                                                               |
+| Class names                                                | `button-primary`                                                                                                                                                                             |
+| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                                                                                                     |
+| Data types                                                 | (`string`, `number`, `int64`)                                                                                                                                                                |
+| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                                                                                                           |
+| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink. |
+| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                                                                                                    |
+| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                                                                                                           |
+| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                                                                                                       |
+| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                                                                                                            |
+| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                                                                                                              |
+| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                                                                                                        |
+| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx.                                                                                   |
+| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                                                                                                         |
+| HTTP header names                                          | `Content-Length`                                                                                                                                                                             |
+| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                                                                                                                 |
+| IAM role names                                             | `roles/storage.admin`                                                                                                                                                                        |
+| Language keywords                                          | `in`, `await`                                                                                                                                                                                |
+| Method and function names                                  | `handleRequest`                                                                                                                                                                              |
+| Namespace aliases                                          | `numpy`                                                                                                                                                                                      |
+| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                                                                                                           |
+| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                                                                                                       |
+| Text input                                                 | `"Hello Worker"`                                                                                                                                                                             |
diff --git a/src/content/docs/style-guide/formatting/dates-and-times.mdx b/src/content/docs/style-guide/formatting/dates-and-times.mdx
index ab9f427759fec31..70172f50376d6b5 100644
--- a/src/content/docs/style-guide/formatting/dates-and-times.mdx
+++ b/src/content/docs/style-guide/formatting/dates-and-times.mdx
@@ -10,9 +10,9 @@ products:
 
 To account for internationalization and inclusivity of all locales, use the ISO-8601 (YYYY-MM-DD hh:mm:ss) standard when writing dates and times as much as possible.
 
-In general, documentation should strive to represent universal truth, not 
-something time-bound. This is why semgrep may flag uses of explicit dates 
-or month names or years because often become out-of-date and not be 
+In general, documentation should strive to represent universal truth, not
+something time-bound. This is why semgrep may flag uses of explicit dates
+or month names or years because often become out-of-date and not be
 revised later.
 
 ## Blogs
diff --git a/src/content/docs/style-guide/formatting/external-references.mdx b/src/content/docs/style-guide/formatting/external-references.mdx
index 19253920fd68de6..49120127e781b06 100644
--- a/src/content/docs/style-guide/formatting/external-references.mdx
+++ b/src/content/docs/style-guide/formatting/external-references.mdx
@@ -11,9 +11,9 @@ When referencing external resources, ensure that you are linking to a trustworth
 
 For general websites, consider the following recommendations about the link text:
 
-* Use the website name if you are linking to the home page.
-* Use the page name if you are linking to a specific page.
-* Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
+- Use the website name if you are linking to the home page.
+- Use the page name if you are linking to a specific page.
+- Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
 When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
diff --git a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
index 316c3540dcbba9d..7ef14947ec6845d 100644
--- a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
+++ b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
@@ -8,8 +8,8 @@ products:
 
 You can refer both to file types and file extensions in documentation:
 
-* File types: Accepted file formats are JSON and YAML.
-* File extensions: Upload the `.txt` file to the dashboard.
+- File types: Accepted file formats are JSON and YAML.
+- File extensions: Upload the `.txt` file to the dashboard.
 
 When referring to a specific file type, always use regular text formatting, write the file type in uppercase, and avoid the initial dot (you are referring to the file type, not the file extension).
 
@@ -17,7 +17,7 @@ When referring to a specific extension, always monospace the file, include a dot
 
 Additional examples:
 
-* The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
-* Additionally, this plist can be wrapped in a `.mobileconfig` file.
-* If you would like to test how this feature works, here is a sample `.csv` file.
-* Concatenate the string to a text-based `.pem` file.
+- The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
+- Additionally, this plist can be wrapped in a `.mobileconfig` file.
+- If you would like to test how this feature works, here is a sample `.csv` file.
+- Concatenate the string to a text-based `.pem` file.
diff --git a/src/content/docs/style-guide/formatting/index.mdx b/src/content/docs/style-guide/formatting/index.mdx
index 8c1d56e0c307810..7ec4a59dacb722c 100644
--- a/src/content/docs/style-guide/formatting/index.mdx
+++ b/src/content/docs/style-guide/formatting/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/keyboard-keys.mdx b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
index d9faeed37a3cd77..9dad67aca460e95 100644
--- a/src/content/docs/style-guide/formatting/keyboard-keys.mdx
+++ b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
@@ -14,16 +14,20 @@ products:
 ## Formatting keyboard shortcuts
 
 When telling readers what keyboard shortcuts to use to achieve a result:
+
 - Place the keyboard shortcut in between backticks (monospace formatting)
 - Use uppercase letters with the abbreviated version of the key (`CTRL` instead of `CONTROL`, `CMD` instead of `COMMAND`for example)
 - Wrap the complete keyboard shortcut in between backticks, including the plus sign:
-	- **Do**:
-	```mdx
-	`CTRL + C`
-	```
-
-	- **Don't**:
-	```mdx
-	`CTRL` + `C`
-	```
-- Do not use the old `<kbd></kbd>` component
\ No newline at end of file
+  - **Do**:
+
+  ```mdx
+  `CTRL + C`
+  ```
+
+  - **Don't**:
+
+  ```mdx
+  `CTRL` + `C`
+  ```
+
+- Do not use the old `<kbd></kbd>` component
diff --git a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
index 382bab58c8d7d78..02c81845f3a290b 100644
--- a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
+++ b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
@@ -9,6 +9,7 @@ products:
 When adding a note to a page, always use this special note formatting. There are three types of formatted notes: `note`, `caution`, and `tip`.
 
 Here is some additional information about notes:
+
 - The color of the note depends on the type of note: `note` is blue, `caution` is yellow, and `tip` is purple.
 - For every note type, the header text is optional.
 - All note types can contain text and additional formatting like lists, code blocks, and images.
diff --git a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
index 5085765a1f2090b..96a4801c772e1e3 100644
--- a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
+++ b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
@@ -10,26 +10,26 @@ products:
 
 In body text, spell out whole numbers from zero through nine.
 
-* Example: We have added three more servers.
+- Example: We have added three more servers.
 
 For numbers greater than or equal to 10, use digits.
 
-* Example: The message is 32 bytes long, \[...]
+- Example: The message is 32 bytes long, \[...]
 
 For analytics, display metrics with numerals.
 Use commas for numbers with more than 3 digits (no spaces). Note the differences in numerical punctuation for translation.
 
-* 300
-* 1,000
-* 7,465
+- 300
+- 1,000
+- 7,465
 
 ## Using k to indicate thousands
 
 Do not put a space between the number and k.
 
-Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for *kilobytes*.
+Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for _kilobytes_.
 
-* Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
+- Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
 
 ## Units of measurement
 
@@ -45,14 +45,14 @@ Many CPU architectures either do not allow execution of the machine code, which
 
 In general, only abbreviate units of measurements when they modify specific quantities/numbers. When you need to abbreviate them:
 
-| ✅     | ❌      | Rationale                                              |
+| ✅    | ❌     | Rationale                                              |
 | ----- | ------ | ------------------------------------------------------ |
 | 10 m  | 10m    | Always include a space between the number and the unit |
 | 10 cm | 10 cms | Unit symbols should unaltered in the plural.           |
 
 **Always include a space between a numerical value and the corresponding unit of measurement.** Although both formats are widely used, the metric system standardized the use of a space before a unit of measurement and should be used as a guideline to keep content consistent and clear.
 
-| ✅                                                | ❌                                           | Rationale                                                                                                   |
+| ✅                                               | ❌                                          | Rationale                                                                                                   |
 | ------------------------------------------------ | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
 | 128 GB                                           | 128 gb, 128gb, 128GB                        | Units of measurement should always be capitalized and spaced out from their corresponding numerical values. |
 | This network has a capacity of over **30 Tbps.** | This network has a capacity of over 30Tbps. | Adding a space between ‘30’ and ‘Tbps’ makes this sentence easier to read.                                  |
diff --git a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
index e44f43ed36fdc50..25c6ca97daeed00 100644
--- a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
+++ b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
@@ -10,5 +10,5 @@ Product names should follow a noun-verb agreement such that the verb is singular
 
 Examples:
 
-* Cloudflare Pages enables/allows.
-* Cloudflare Workers executes/propagates.
+- Cloudflare Pages enables/allows.
+- Cloudflare Workers executes/propagates.
diff --git a/src/content/docs/style-guide/formatting/structure/index.mdx b/src/content/docs/style-guide/formatting/structure/index.mdx
index e2f981f9d22a682..3498fa8f873c716 100644
--- a/src/content/docs/style-guide/formatting/structure/index.mdx
+++ b/src/content/docs/style-guide/formatting/structure/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/structure/lists.mdx b/src/content/docs/style-guide/formatting/structure/lists.mdx
index 94571bd31ee8c27..35a60f4a49b706c 100644
--- a/src/content/docs/style-guide/formatting/structure/lists.mdx
+++ b/src/content/docs/style-guide/formatting/structure/lists.mdx
@@ -8,15 +8,15 @@ products:
 
 There are three types of lists:
 
-* Bulleted lists for unordered items
-* Numbered lists for ordered items
-* Embedded lists for items within a sentence
+- Bulleted lists for unordered items
+- Numbered lists for ordered items
+- Embedded lists for items within a sentence
 
 Here are some tips when creating lists:
 
-* Keep list items parallel
-* Start numbered lists with a command (imperative verb)
-* Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
+- Keep list items parallel
+- Start numbered lists with a command (imperative verb)
+- Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
 
 ## Bullet points
 
@@ -25,26 +25,37 @@ Bullet points help the reader's eye focus on a list of important elements.
 However, as with any other aspect of writing, they should be used mindfully. Below is a list of when you should and should not resort to bullet points.
 
 <table>
-  <thead>
-    <tr>
-        <th>❌ Do not use bullet points</th>
-        <th>✅ Use bullet points</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-        <td>To outline <b>processes</b> (prefer numbered lists)</td>
-        <td>To list <b>facts</b></td>
-    </tr>
-    <tr>
-        <td>To explain your reasoning (it is a blog post, not a list of system requirements)</td>
-        <td>To list <b>data</b></td>
-    </tr>
-    <tr>
-        <td>-</td>
-        <td>To list <b>options</b></td>
-    </tr>
-    </tbody>
+	<thead>
+		<tr>
+			<th>❌ Do not use bullet points</th>
+			<th>✅ Use bullet points</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>
+				To outline <b>processes</b> (prefer numbered lists)
+			</td>
+			<td>
+				To list <b>facts</b>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				To explain your reasoning (it is a blog post, not a list of system
+				requirements)
+			</td>
+			<td>
+				To list <b>data</b>
+			</td>
+		</tr>
+		<tr>
+			<td>-</td>
+			<td>
+				To list <b>options</b>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Bulleted lists
@@ -55,8 +66,8 @@ Do not punctuate bullet points unless each item is a full sentence.
 
 If bullet point items are followed by a description, use a colon after the heading and capitalize the description. For example,
 
-* **Item 1**: Description 1
-* **Item 2**: Description 2
+- **Item 1**: Description 1
+- **Item 2**: Description 2
 
 For bullet points, try to stick to the "six-pack" rule: no more than six bullets, each made up of six words or less.
 
@@ -67,14 +78,14 @@ Refer to [The best way to use bullet points](https://thewritinghabit.blog/2016/0
 When you find yourself creating a list of bullet points, go through this checklist:
 
 1. Do all bullet points belong together?
-   * Check that all the elements in the list are logically connected.
+   - Check that all the elements in the list are logically connected.
 2. Do I have more three or more bullet points, but less than six?
-   * Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
+   - Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
 3. Are all bullet points shorter than three lines of text?
-   * Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
+   - Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
 4. Is punctuation consistent?
-   * End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
+   - End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
 5. Do all bullet points start with the most important word we want the reader to remember?
-   * Make sure the "head" of your bullet point is not hiding after a long circumlocution.
+   - Make sure the "head" of your bullet point is not hiding after a long circumlocution.
 6. Do all bullet points start with the same part of speech?
-   * If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
+   - If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
diff --git a/src/content/docs/style-guide/formatting/structure/tables.mdx b/src/content/docs/style-guide/formatting/structure/tables.mdx
index d43a5fa3787672b..7a79ef760d68e39 100644
--- a/src/content/docs/style-guide/formatting/structure/tables.mdx
+++ b/src/content/docs/style-guide/formatting/structure/tables.mdx
@@ -12,14 +12,14 @@ Using tables to simplify content and data provides a comprehensive way to arrang
 
 Here are some tips when creating tables:
 
-* Label column headers.
-* Label row headers if appropriate.
-* Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
-* Avoid too much text.
-* Aim for parallelism within the column.
-* Keep tables as simple and as small as possible.
-* Sort rows in a logical order. If no logical order exists, use alphabetical order.
-* <Render file="table-guidelines" product="style-guide" />
+- Label column headers.
+- Label row headers if appropriate.
+- Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
+- Avoid too much text.
+- Aim for parallelism within the column.
+- Keep tables as simple and as small as possible.
+- Sort rows in a logical order. If no logical order exists, use alphabetical order.
+- <Render file="table-guidelines" product="style-guide" />
 
 ## Introductory sentences
 
@@ -29,25 +29,25 @@ When referring to a table, use a phrase like "the following table" or "the prece
 
 ## Column headings
 
-* Use sentence case.
-* Write concise headings that clearly describe the column content.
-* Do not end column headings with punctuation, including periods, ellipses, or colons.
-* Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
+- Use sentence case.
+- Write concise headings that clearly describe the column content.
+- Do not end column headings with punctuation, including periods, ellipses, or colons.
+- Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
 
 ```html
 <thead>
-  <tr>
-    <th scope="col">Name</th>
-    <th scope="col">Description</th>
-  </tr>
+	<tr>
+		<th scope="col">Name</th>
+		<th scope="col">Description</th>
+	</tr>
 </thead>
 ```
 
 ## Table placement
 
-* Place each table directly after the sentence that introduces it.
-* Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
-* If a table has footnotes, place them immediately after the table.
+- Place each table directly after the sentence that introduces it.
+- Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
+- If a table has footnotes, place them immediately after the table.
 
 ## Table captions
 
@@ -62,9 +62,9 @@ In Markdown, place the caption as a bold line immediately before the table:
 ```markdown
 **Table 1.** Supported DNS record types
 
-| Type | Description |
-| --- | --- |
-| A | Maps a domain to an IPv4 address |
+| Type | Description                      |
+| ---- | -------------------------------- |
+| A    | Maps a domain to an IPv4 address |
 | AAAA | Maps a domain to an IPv6 address |
 ```
 
@@ -72,19 +72,22 @@ In HTML, use the `caption` element as the first child of the `table` element:
 
 ```html
 <table>
-  <caption><b>Table 1.</b> Supported DNS record types</caption>
-  <thead>
-    <tr>
-      <th scope="col">Type</th>
-      <th scope="col">Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>A</td>
-      <td>Maps a domain to an IPv4 address</td>
-    </tr>
-  </tbody>
+	<caption>
+		<b>Table 1.</b>
+		Supported DNS record types
+	</caption>
+	<thead>
+		<tr>
+			<th scope="col">Type</th>
+			<th scope="col">Description</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>A</td>
+			<td>Maps a domain to an IPv4 address</td>
+		</tr>
+	</tbody>
 </table>
 ```
 
@@ -94,8 +97,8 @@ Tables display pieces of information that have some sort of relationship.
 
 Example:
 
-* Dates and descriptions, like a changelog
-* A list of products with attributes
+- Dates and descriptions, like a changelog
+- A list of products with attributes
 
 ## When not to use tables
 
@@ -139,7 +142,7 @@ The rendered output looks like this:
 | Syntax    | Description |    Test Text |
 | :-------- | :---------: | -----------: |
 | Header    |    Title    | Here is this |
-| Paragraph |     Text    |     And more |
+| Paragraph |    Text     |     And more |
 
 ## Formatting text in tables
 
diff --git a/src/content/docs/style-guide/frontmatter/sidebar.mdx b/src/content/docs/style-guide/frontmatter/sidebar.mdx
index ec8a552cab6f221..b28d8a5f1d52ccb 100644
--- a/src/content/docs/style-guide/frontmatter/sidebar.mdx
+++ b/src/content/docs/style-guide/frontmatter/sidebar.mdx
@@ -215,5 +215,5 @@ sidebar:
 
 ### Automatic "Beta" badges
 
-A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status. 
-This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`. 
+A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status.
+This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`.
diff --git a/src/content/docs/style-guide/grammar/index.mdx b/src/content/docs/style-guide/grammar/index.mdx
index d70d2ce818eea88..c7d3f0ea3544cd9 100644
--- a/src/content/docs/style-guide/grammar/index.mdx
+++ b/src/content/docs/style-guide/grammar/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
index 3241618b639da6b..bffb664c1bd3269 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
@@ -6,7 +6,7 @@ products:
   - style-guide
 ---
 
-Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word *acronym* to refer to both).
+Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word _acronym_ to refer to both).
 
 ## Long and short versions of a word
 
@@ -16,7 +16,7 @@ The short versions of the words are not abbreviations, and if you use them, you
 
 If you are not sure whether a word is an abbreviation or just a short version of a longer word, here is a list of [common abbreviations](https://abbreviations.yourdictionary.com/articles/list-of-commonly-used-abbreviations.html). If that does not settle the issue, use the speaking test: if you speak the short version as a word ("This is a demo version of the product"), you can usually treat it as a word and not an abbreviation.
 
-If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer *applications* on Cloudflare for Teams are not shortened to *apps*. Depending on the use case, application might be the preferred term, especially due to translation.
+If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer _applications_ on Cloudflare for Teams are not shortened to _apps_. Depending on the use case, application might be the preferred term, especially due to translation.
 
 ## When to spell out a term
 
@@ -24,28 +24,28 @@ In general, when an abbreviation is likely to be unfamiliar to the audience, spe
 
 If the first mention of a term occurs in a heading or title, you can use the abbreviation and then spell out the abbreviation in the first paragraph that follows the heading or title.
 
-When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out *application programming interface*. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
+When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out _application programming interface_. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
 
-In some cases, spelling out a term does not help the reader understand the term. For example, writing out *portable document format* does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
+In some cases, spelling out a term does not help the reader understand the term. For example, writing out _portable document format_ does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
 
 The following abbreviations rarely need to be spelled out:
 
-* API
-* DVD
-* File formats such as PDF or XML
-* HTML
-* PC
-* RAM
-* REST
-* Units of measure such as MB or GB
-* URL
-* USB
+- API
+- DVD
+- File formats such as PDF or XML
+- HTML
+- PC
+- RAM
+- REST
+- Units of measure such as MB or GB
+- URL
+- USB
 
 ## Abbreviations not to use
 
 Prefer English terms over Latin abbreviations. Do not use i.e. or e.g. Instead, use **that is** or **for example**, respectively.
 
-One exception: avoid both *etc.* and *and so on* wherever possible, but if you really need to use one, use *etc.* Always include the period, even if a comma follows immediately after.
+One exception: avoid both _etc._ and _and so on_ wherever possible, but if you really need to use one, use _etc._ Always include the period, even if a comma follows immediately after.
 
 Do not use Internet slang abbreviations such as tl;dr, IMO, FYI, or others.
 
@@ -55,16 +55,16 @@ Use the most common form of a word. If the full spelled-out word is common and e
 
 Follow these guidelines:
 
-* Do not use periods with acronyms or initialisms.
-* Put a period at the end of a shortened word, except for date and time abbreviations.
-* If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
-* Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
+- Do not use periods with acronyms or initialisms.
+- Put a period at the end of a shortened word, except for date and time abbreviations.
+- If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
+- Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
 
 ## i.e. vs e.g.
 
 While similar, these two Latin abbreviations carry very different meanings.
 
-* **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
-  * The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
-* **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
-  * Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
+- **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
+  - The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
+- **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
+  - Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
index 1b9979cc0ba573e..3d4836341a01f1b 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
@@ -6,10 +6,10 @@ products:
   - style-guide
 ---
 
-**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some  terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
+**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
 
-* If the term already exists, link to a good existing explanation.
+- If the term already exists, link to a good existing explanation.
 
-* If your document is introducing the term, define the term.
+- If your document is introducing the term, define the term.
 
-* **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods  between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word  — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
+- **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
index fbbcad12c379e14..ca1c548ad846c7e 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
@@ -10,7 +10,7 @@ products:
 
 Each product, service, and feature should be properly spelled and capitalized when used in any content, both to ensure consistency across all channels and to differentiate common performance and security technologies (for example: load balancing, bot management, and web application firewalls) from specific Cloudflare solutions (for example: Cloudflare Load Balancing, Cloudflare Bot Management, and Cloudflare Web Application Firewall).
 
-| ✅                                                                                                                                                           | ❌                                                                                                                                                | Rationale                                                                                                                                   |
+| ✅                                                                                                                                                          | ❌                                                                                                                                               | Rationale                                                                                                                                   |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | This interactive demo provides three different scenarios on how to utilize **Cloudflare Rate Limiting** to protect your endpoints from suspicious requests. | This interactive demo provides three different scenarios on how to utilize **rate limiting** to protect your endpoints from suspicious requests. | This demo is specific to a Cloudflare product (Cloudflare Rate Limiting), not a tutorial on utilizing generic rate limiting.                |
 | The **Cloudflare Web Application Firewall (WAF)** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.       | Our **web application firewall** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.             | Cloudflare Web Application Firewall (WAF) is a specific product we offer and should be capitalized and identified with the Cloudflare name. |
@@ -19,75 +19,109 @@ Each product, service, and feature should be properly spelled and capitalized wh
 
 **When to use Waiting Room capitalized and singular:**
 
-* Naming the product: *Waiting Room keeps wait times low by dynamically managing traffic.*
-* Page title: *Access Waiting Room*
-* Preceded by “Cloudflare”: *Cloudflare Waiting Room allows organizations to…*
-* Preceding a feature name: *Waiting Room Event Scheduling*
+- Naming the product: _Waiting Room keeps wait times low by dynamically managing traffic._
+- Page title: _Access Waiting Room_
+- Preceded by “Cloudflare”: _Cloudflare Waiting Room allows organizations to…_
+- Preceding a feature name: _Waiting Room Event Scheduling_
 
 **When to waiting room(s) lower-case and in singular or plural:**
 
-* Used as an object: *Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room.*
-* Capitalize only the first word when at the beginning of a sentence:  *Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated.*
-* Capitalize only the first word when it is the title of a subsection: *### Waiting room template*
+- Used as an object: _Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room._
+- Capitalize only the first word when at the beginning of a sentence: _Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated._
+- Capitalize only the first word when it is the title of a subsection: _### Waiting room template_
 
 ## Common capitalization conventions
 
 <table>
-  <tr>
-    <th style="width:20%">✅</th>
-    <th style="width:20%">❌</th>
-    <th>Rationale</th>
-  </tr>
-  <tr>
-    <td>CAPTCHA, reCAPTCHA</td>
-    <td>Captcha, captcha, recaptcha, Recaptcha</td>
-    <td>A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are not bots.</td>
-  </tr>
-  <tr>
-    <td>cloud</td>
-    <td>Cloud, "cloud"</td>
-    <td>The <b>cloud</b> is a network of remote servers used to store and maintain data. </td>
-  </tr>
-  <tr>
-    <td>DDoS</td>
-    <td>ddos, DDOS</td>
-    <td>A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a targeted server.</td>
-  </tr>
-  <tr>
-    <td>denial-of-service (DoS)</td>
-    <td>denial of service, Denial-of-Service, Denial-Of-Service, Denial of Service, dos, Dos, DOS</td>
-    <td>DDoS is a type of <b>DoS</b> attack.</td>
-  </tr>
-  <tr>
-    <td>Enterprise, enterprise</td>
-    <td>ent, ENT</td>
-    <td>Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise customers are enterprise companies, but not all enterprises are Enterprise customers. </td>
-  </tr>
-  <tr>
-    <td>Internet</td>
-    <td>internet</td>
-    <td>Disabling this option may cause all devices to lose <b>Internet</b> connectivity.</td>
-  </tr>
-  <tr>
-    <td>SSL</td>
-    <td>ssl</td>
-    <td><b>SSL</b> is an encryption-based Internet security protocol.</td>
-  </tr>
-  <tr>
-    <td>TLS</td>
-    <td>tls</td>
-    <td><b>TLS</b> is a security protocol designed to facilitate privacy and data security for communications over the Internet..</td>
-  </tr>
-  <tr>
-    <td>WAF</td>
-    <td>waf</td>
-    <td><b>WAF</b> is a security system that helps protect web applications by filtering and monitoring HTTP traffic between a web application and the Internet. </td>
-  </tr>
-  <tr>
-    <td>Zero Trust</td>
-    <td>zero trust</td>
-    <td><b>Cloudflare</b> Access is a Zero Trust solution that secures inbound connections to your protected applications.</td>
-  </tr>
+	<tr>
+		<th style="width:20%">✅</th>
+		<th style="width:20%">❌</th>
+		<th>Rationale</th>
+	</tr>
+	<tr>
+		<td>CAPTCHA, reCAPTCHA</td>
+		<td>Captcha, captcha, recaptcha, Recaptcha</td>
+		<td>
+			A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are
+			not bots.
+		</td>
+	</tr>
+	<tr>
+		<td>cloud</td>
+		<td>Cloud, "cloud"</td>
+		<td>
+			The <b>cloud</b> is a network of remote servers used to store and maintain
+			data.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>DDoS</td>
+		<td>ddos, DDOS</td>
+		<td>
+			A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a
+			targeted server.
+		</td>
+	</tr>
+	<tr>
+		<td>denial-of-service (DoS)</td>
+		<td>
+			denial of service, Denial-of-Service, Denial-Of-Service, Denial of
+			Service, dos, Dos, DOS
+		</td>
+		<td>
+			DDoS is a type of <b>DoS</b> attack.
+		</td>
+	</tr>
+	<tr>
+		<td>Enterprise, enterprise</td>
+		<td>ent, ENT</td>
+		<td>
+			Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or
+			a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise
+			customers are enterprise companies, but not all enterprises are Enterprise
+			customers.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>Internet</td>
+		<td>internet</td>
+		<td>
+			Disabling this option may cause all devices to lose <b>Internet</b>{" "}
+			connectivity.
+		</td>
+	</tr>
+	<tr>
+		<td>SSL</td>
+		<td>ssl</td>
+		<td>
+			<b>SSL</b> is an encryption-based Internet security protocol.
+		</td>
+	</tr>
+	<tr>
+		<td>TLS</td>
+		<td>tls</td>
+		<td>
+			<b>TLS</b> is a security protocol designed to facilitate privacy and data
+			security for communications over the Internet..
+		</td>
+	</tr>
+	<tr>
+		<td>WAF</td>
+		<td>waf</td>
+		<td>
+			<b>WAF</b> is a security system that helps protect web applications by
+			filtering and monitoring HTTP traffic between a web application and the
+			Internet.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>Zero Trust</td>
+		<td>zero trust</td>
+		<td>
+			<b>Cloudflare</b> Access is a Zero Trust solution that secures inbound
+			connections to your protected applications.
+		</td>
+	</tr>
 </table>
 
 ## Headings
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
index 1e61e8bfdd8ecf5..e7f8868af4430c8 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
@@ -11,31 +11,34 @@ products:
 Whitespace is used in our blog posts and product content. For the sake of consistency, follow these conventions when using them:
 
 <table>
-  <tr>
-    <th style="width:20%">✅</th>
-    <th style="width:20%">❌</th>
-    <th>Example</th>
-  </tr>
-  <tr>
-    <td>nameserver</td>
-    <td>name servers</td>
-    <td>Change your nameservers to Cloudflare's.</td>
-  </tr>
-  <tr>
-    <td>hostname</td>
-    <td>host name</td>
-    <td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
-  </tr>
-  <tr>
-    <td>data center</td>
-    <td>datacenter</td>
-    <td>Cloudflare updates the new setting across all of our data centers around the world.</td>
-  </tr>
-  <tr>
-    <td>checkbox</td>
-    <td>check box</td>
-    <td>Select the Transfer lock checkbox before continuing the setup.</td>
-  </tr>
+	<tr>
+		<th style="width:20%">✅</th>
+		<th style="width:20%">❌</th>
+		<th>Example</th>
+	</tr>
+	<tr>
+		<td>nameserver</td>
+		<td>name servers</td>
+		<td>Change your nameservers to Cloudflare's.</td>
+	</tr>
+	<tr>
+		<td>hostname</td>
+		<td>host name</td>
+		<td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
+	</tr>
+	<tr>
+		<td>data center</td>
+		<td>datacenter</td>
+		<td>
+			Cloudflare updates the new setting across all of our data centers around
+			the world.
+		</td>
+	</tr>
+	<tr>
+		<td>checkbox</td>
+		<td>check box</td>
+		<td>Select the Transfer lock checkbox before continuing the setup.</td>
+	</tr>
 </table>
 
 When using compound words that have a preposition in them (think log in, or set up), they should be written as two separate words when they are verbs, and as one word when they are nouns.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
index fdb9214b95f5fc2..72a9ab7762531bd 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
@@ -6,4 +6,4 @@ products:
   - style-guide
 ---
 
-Avoid using contractions such as *don't*, *won't*, and *can't*.
+Avoid using contractions such as _don't_, _won't_, and _can't_.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
index dd8d05d847d9506..72d3c0deacba961 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
index deb7014e128ee54..76a0418aeb4ab62 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
@@ -14,7 +14,7 @@ Make sure it is clear who or what pronouns are in reference to. Pronouns act as
 
 Substitute "we" or "I" with "Cloudflare" if you need to represent Cloudflare. You do not need to use "we" constantly. However, use it when it is the best choice grammatically.
 
-| ✅                                                           | ❌                                                                 |
+| ✅                                                          | ❌                                                                |
 | ----------------------------------------------------------- | ----------------------------------------------------------------- |
 | Cloudflare recommends you submit image or plain text files. | We recommend closing your files before you restart your computer. |
 
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
index 187e021787a2e58..5f490a47e38f572 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
@@ -8,4 +8,4 @@ products:
 
 In general, avoid the 's construction to show possession by an inanimate object as doing so personifies the object.
 
-Example: *the device's address*.
+Example: _the device's address_.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
index 10c8af546776d4a..8e3704dfdac8622 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
@@ -8,6 +8,6 @@ products:
 
 You can put a preposition at the end of a sentence, but do not do it often. Your sentences can sound stilted if you try to avoid putting the preposition at the end.
 
-| ✅                                                     | ❌                                                          |
+| ✅                                                    | ❌                                                         |
 | ----------------------------------------------------- | ---------------------------------------------------------- |
 | Open the application you are submitting an image for. | Open the application for which you are submitting an icon. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
index 415d78fa7023e8f..39a5939c88506d9 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
@@ -18,6 +18,6 @@ Example: After you open the file, save it to your desktop with a different name.
 
 Use the Oxford comma. The Oxford comma should break up lists of three or more items in a sentence.
 
-Example:  Stream for Free, Pro, and Business plans
+Example: Stream for Free, Pro, and Business plans
 
 Without the Oxford comma, readers might misunderstand this header as free streaming for Pro and Business plans.
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
index 2773cd5a9e97ed4..6e37346b1c896c4 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
@@ -14,9 +14,9 @@ Dashes look like hyphens, but are wider. An em dash is the widest type of dash.
 
 Examples:
 
-* The most up-to-date software can be found here.
+- The most up-to-date software can be found here.
 
-* It takes 24-48 hours for the data to upload.
+- It takes 24-48 hours for the data to upload.
 
 :::note
 
@@ -26,7 +26,7 @@ Never include whitespaces around a hyphen.
 
 Additional examples:
 
-| ✅                                                                                                                    | ❌                                                                                                                    | Rationale                                                                                                                                                                                 |
+| ✅                                                                                                                   | ❌                                                                                                                   | Rationale                                                                                                                                                                                 |
 | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Protect your Internet property from common vulnerabilities with our enterprise-class Web Application Firewall (WAF). | Protect your Internet property from common vulnerabilities with our enterprise class Web Application Firewall (WAF). | ‘Enterprise-class’ refers to the ability of something to scale with and handle the needs of large enterprises. A hyphen is necessary because the compound modifier comes before the noun. |
 | Our WAF is enterprise class.                                                                                         | Our WAF is enterprise-class.                                                                                         | ‘Enterprise class’ modifies ‘WAF.’ A hyphen is not necessary because the compound modifier comes after the noun.                                                                          |
@@ -35,17 +35,17 @@ Additional examples:
 
 **Use em dashes to break up thoughts within a single sentence.** Em dashes (—) or double dashes (--) with spaces around them may be used to break up thoughts within a sentence. Single dashes (-), or hyphens, are commonly used to write compound words/modifiers and should never be used to break up thoughts in this way.
 
-* Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
+- Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
 
-* Shortcut for PC users: Hold down the Alt key and type 0151
+- Shortcut for PC users: Hold down the Alt key and type 0151
 
 Dashes are used in pairs (in place of parenthesis) or alone (in place of a semicolon or colon).
 
 Examples:
 
-* Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
+- Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
 
-* Embed yourself in the team — the best results will come when trust is built.
+- Embed yourself in the team — the best results will come when trust is built.
 
 :::note
 
@@ -54,7 +54,7 @@ Following AP style guides, and to improve readability, we include whitespaces be
 
 Additional examples:
 
-| ✅                                                                                                                                                  | ❌                                                                                                                                                | Rationale                                                                                                                                                      |
+| ✅                                                                                                                                                 | ❌                                                                                                                                               | Rationale                                                                                                                                                      |
 | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | The app has made security and privacy core to the company’s mission — and that is why it chose Cloudflare to provide an extra layer of protection. | The app has made security and privacy core to the company’s mission—and that is why it chose Cloudflare to provide an extra layer of protection. | An em dash with spaces on both sides is the appropriate way to distinguish the offset phrase at the end of this sentence.                                      |
 | ACME has always looked deeply into two sources of traffic -- organic and direct traffic.                                                           | ACME has always looked deeply into two sources of traffic - organic and direct traffic.                                                          | A double dash is the appropriate way to clarify different types of traffic at the end of this sentence. A hyphen should not be used in place of a double dash. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
index d73f721061e8356..6c7364bfdbb410d 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/how-we-docs/our-site.mdx b/src/content/docs/style-guide/how-we-docs/our-site.mdx
index 99ca2d006472130..22522e9cde5ff47 100644
--- a/src/content/docs/style-guide/how-we-docs/our-site.mdx
+++ b/src/content/docs/style-guide/how-we-docs/our-site.mdx
@@ -28,7 +28,6 @@ We use [Starlight](https://starlight.astro.build/) for our docs, which is a free
 
 Astro's [component overrides](https://starlight.astro.build/guides/overriding-components/) and [plugins](https://starlight.astro.build/resources/plugins/) system were a big part of us [choosing this framework](https://blog.cloudflare.com/open-source-all-the-way-down-upgrading-our-developer-documentation/) and have exponentially increased our [site's capabilities](/style-guide/components/) (without much extra work).
 
-
 ## Builds
 
 We use [GitHub Actions](https://github.com/features/actions) to build our site, which is then [hosted](#hosting) on Cloudflare.
diff --git a/src/content/docs/style-guide/how-we-docs/reviews.mdx b/src/content/docs/style-guide/how-we-docs/reviews.mdx
index da23b24233aa04c..26cc6567c416368 100644
--- a/src/content/docs/style-guide/how-we-docs/reviews.mdx
+++ b/src/content/docs/style-guide/how-we-docs/reviews.mdx
@@ -25,14 +25,14 @@ For pull requests, we use a specific [GitHub action](https://github.com/cloudfla
 - [Label products](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-products/): We add labels for the top-level product folder, which helps writers scan incoming pull requests and see which are relevant to them.
 - [Label size](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-size/): We add labels for the size of the pull request, which helps writers see the relative size of the difference. It's not a perfect measure, but we use the lines changed to estimate the size of the pull request:
 
-	<GitHubCode
-		repo="cloudflare/cloudflare-docs"
-		file=".github/actions/label-size/index.ts"
-		commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
-		lines="20-36"
-		lang="ts"
-		code={{ title: "label-size.ts" }}
-	/>
+  <GitHubCode
+  	repo="cloudflare/cloudflare-docs"
+  	file=".github/actions/label-size/index.ts"
+  	commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
+  	lines="20-36"
+  	lang="ts"
+  	code={{ title: "label-size.ts" }}
+  />
 
 - [Assign codeowners](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/assign-pr): We use our [CODEOWNERS](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/CODEOWNERS) file to automatically assign people to pull requests based on the files changed. This assignment helps writers scan and filter to see which pull requests are relevant to them.
 
@@ -42,7 +42,6 @@ For issues, we use a similar [GitHub action](https://github.com/cloudflare/cloud
 
 Our [script](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/issue-label-assign) treats issues because usually they contain links to our site instead of files within the repository. We grab the associated links in the issue description fields and then use those to assign writers (again based on `CODEOWNERS`) and add product labels.
 
-
 ## Streamline reviews
 
 To streamline reviews, we use several automations to help solve common reviewer issues.
@@ -68,7 +67,7 @@ We have a specific part of [CI](https://github.com/cloudflare/cloudflare-docs/bl
 
 ### What changed?
 
-We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub). 
+We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub).
 
 We are in the process of migrating to [Workers Builds](/workers/ci-cd/builds/git-integration/github-integration/), which provides that functionality natively.
 
@@ -104,4 +103,4 @@ This workflow - we hope - balances the needs our of team with a healthy respect
 
 We intentionally avoid the [`stale` workflow](https://github.com/github/docs/blob/main/.github/workflows/stale.yml) that closes pull requests or issues that have been inactive for a specific period of time.
 
-In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
\ No newline at end of file
+In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
diff --git a/src/content/docs/support/contacting-cloudflare-support.mdx b/src/content/docs/support/contacting-cloudflare-support.mdx
index ac84963b72ae9f0..657813bb6f05df5 100644
--- a/src/content/docs/support/contacting-cloudflare-support.mdx
+++ b/src/content/docs/support/contacting-cloudflare-support.mdx
@@ -39,7 +39,7 @@ As a Cloudflare customer, you can contact Cloudflare for support via the communi
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------- | ----------- | ----------- |
 | [Community](https://community.cloudflare.com/)<br/>Join the community to ask basic troubleshooting questions and to view the latest resources (such as tips for resolving common issues and configuration guidance). | Yes        | Yes      | Recommended | Recommended |
 | [Discord](https://discord.cloudflare.com/)<br/>Join the Discord community to ask basic troubleshooting questions (mainly focused on the Developer Platform).                                                         | Yes        | Yes      | Recommended | Recommended |
-| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]        |
+| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]      |
 | **Chat**<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                                                      | Yes        | Yes      | No          | No          |
 | **Emergency Phone** <br/>Use phone support to reach out during emergencies such as site outages or DDoS attacks.                                                                                                     | Yes        | No       | No          | No          |
 
@@ -83,7 +83,12 @@ In both cases, you will also need your **Unique Customer ID** (refer to [Finding
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
+<LinkButton
+	href="https://dash.cloudflare.com/?to=/:account/support"
+	icon="external"
+>
+	Go to Support
+</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -97,7 +102,12 @@ Your Unique Customer ID is required when calling the emergency phone line, regar
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
+<LinkButton
+	href="https://dash.cloudflare.com/?to=/:account/support"
+	icon="external"
+>
+	Go to Support
+</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -131,21 +141,21 @@ To submit a support case, follow these steps:
 5. Enter a detailed summary of the issue you’re experiencing.
 
 6. Complete the case submission fields as completely as possible with the following information. _(**Please note** that missing information will increase the time it takes to resolve your issue and our team may not be able to investigate without enough information. Please review [Gathering information for troubleshooting sites](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) and make sure you include all needed information.)_
-    \- A detailed description of the issue with the following information:
-    - Timestamp (UTC)
-    - ZoneName/ZoneID
-    - Problem frequency
-    - Steps to reproduce the issue, with actual results vs expected results
-      \- Any necessary information for a technical investigation
-    - A description of the actual results vs expected results
-    - Steps to reproduce the issue, with example URLs 
-    - Exact error messages
-    - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
-    - Screenshots
-    - Relevant logs from the origin web server
-    - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
-      \- Priority level, impact to service / production
-      \- Any collaborators whom you wish to be cc'd on the case
+   \- A detailed description of the issue with the following information:
+   - Timestamp (UTC)
+   - ZoneName/ZoneID
+   - Problem frequency
+   - Steps to reproduce the issue, with actual results vs expected results
+     \- Any necessary information for a technical investigation
+   - A description of the actual results vs expected results
+   - Steps to reproduce the issue, with example URLs 
+   - Exact error messages
+   - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
+   - Screenshots
+   - Relevant logs from the origin web server
+   - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
+     \- Priority level, impact to service / production
+     \- Any collaborators whom you wish to be cc'd on the case
 
 7. Click **Submit Case**.
 
diff --git a/src/content/docs/support/index.mdx b/src/content/docs/support/index.mdx
index d6fc7fa654994ef..113e68d713a7601 100644
--- a/src/content/docs/support/index.mdx
+++ b/src/content/docs/support/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
index f4dcbec1ff8594c..318aef05f182daf 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
@@ -15,14 +15,14 @@ When you switch a theme or customise a theme within the WordPress admin panel, t
 
 Automatic Cache Management uses native hooks built into WordPress. The Cloudflare WordPress plugin purges the following cache URLs:
 
-* deleted\_post
-* edit\_post
-* delete\_attachment
-* autoptimize\_action\_cachepurged (for compatibility with the Autoptimize WordPress plugin)
-* switch\_theme
-* customize\_save\_after
-
-***
+- deleted_post
+- edit_post
+- delete_attachment
+- autoptimize_action_cachepurged (for compatibility with the Autoptimize WordPress plugin)
+- switch_theme
+- customize_save_after
+
+---
 
 ## Enable Automatic Cache Management
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
index 9a95b6b8ff0e658..0993a2e99b86ad7 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
@@ -9,7 +9,7 @@ products:
 
 HTTP/2 Server Push allows a website to push content to a browser, without having to wait for the HTML of one page to render first. In conjunction with the concurrency support built into HTTP/2, Server Push is able to dramatically reduce the amount of requests needed to load your website.
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733367/http2-server-push-2.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733367/http2-server-push-2.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-http2_server_push_2.png)
 
@@ -23,12 +23,12 @@ define('CLOUDFLARE_HTTP2_SERVER_PUSH_ACTIVE', true);
 
 You should insert this line above where it says *"/\* That's all, stop editing! Happy blogging. \*/*", like follows:|
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733547/Screen\_Shot\_2017-02-09\_at\_16.09.31.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733547/Screen_Shot_2017-02-09_at_16.09.31.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2017_02_09_at_16_09_31.png)
 
 You should then start to see requests coming in which are initiated through Server Push, for example, in the Network tab of Chrome Development Tools you should see some assets have "Push" as the initiator:
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2016_04_26_at_15_08_59.png)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
index 2f68ed6b392d2da..bd0724c70711abf 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
@@ -11,7 +11,7 @@ Content Management Systems make it easy to create, update, and manage content. H
 
 There are many Cloudflare features that can be used for preventing such attacks, but they can also disrupt normal administrative processes such as logging in or uploading images. With proper configuration, you can protect your site from attacks without losing important functionality.
 
-***
+---
 
 ## Stage One: Improve Site Security
 
@@ -29,13 +29,13 @@ The [WAF Managed Rulesets](/waf/managed-rules/) are pre-configured rulesets that
 
 While the feature to customize these managed rulesets required a paid plan, the [Free Cloudflare Managed Ruleset](https://blog.cloudflare.com/waf-for-everyone/#the-free-cloudflare-managed-ruleset) is automatically deployed on any new Cloudflare zone. This ruleset is specially designed to reduce false positives to a minimum across a very broad range of traffic types. As of today, the ruleset contains the following rules:
 
-* Log4J rules matching payloads in the URI and HTTP headers;
-* Shellshock rules;
-* Rules matching very common WordPress exploits;
+- Log4J rules matching payloads in the URI and HTTP headers;
+- Shellshock rules;
+- Rules matching very common WordPress exploits;
 
 Additionally, you can configure many aspects of the [OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/), including the anomaly threshold, paranoia level, and individual rules. One good practice is to ensure any rules related to XSS and SQL injection are enabled.
 
-***
+---
 
 ## Stage Two: Restore Administrative Functions
 
@@ -56,12 +56,12 @@ Next, you can use this information to create a Skip Rule that excludes only the
 
 It is recommended to make this rule as tightly defined as possible, particularly without the additional protections listed below. While the exact content will be site-specific, some possible fields to use are:
 
-* IP Source Address
-* AS Num
-* Cookie
-* User Agent
+- IP Source Address
+- AS Num
+- Cookie
+- User Agent
 
-Make sure to apply the rule *only* to the admin portion of your CMS. With WordPress for example, you can set a condition like '*URI Path contains /wp-admin/*'.
+Make sure to apply the rule _only_ to the admin portion of your CMS. With WordPress for example, you can set a condition like '_URI Path contains /wp-admin/_'.
 
 Any of these fields can be spoofed, so this is not a security measure on its own. The purpose is to restore administrative functions only to conditions that may need them, while using other tools and features (including strong passwords on your CMS logins!) to secure access.
 
@@ -77,7 +77,7 @@ After this is complete, you will want to create a similar rule for any rulesets
 
 Make sure to set your Skip rules to be at a higher priority than the Execute rules.
 
-***
+---
 
 ## Stage Three: Restrict Access
 
@@ -102,7 +102,7 @@ Do the following:
 3. [Enable mTLS](/ssl/client-certificates/enable-mtls/) by adding the correct host.
 4. In **SSL/TLS** > **Client Certificates**, select **Create mTLS Rule**.
 5. Under **When incoming requests match**, enter a value for the **URI Path** field to narrow the rule scope to the admin section, otherwise you will block your visitors from accessing the public content.
-6. Set the rule to *Block* any requests made to your admin panel if the client certificate is not verified.
+6. Set the rule to _Block_ any requests made to your admin panel if the client certificate is not verified.
 7. Select **Deploy**. This creates a WAF custom rule that checks all requests to the admin section for a valid client certificate.
 
 **Note:** If you have issues getting your certificate to verify, try accessing the page in a private window. If it works, the previous successful TLS state may be cached in your browser.
@@ -113,13 +113,13 @@ Rate limiting rules can help protect your login page from an attacker trying to
 
 Rate Limiting Rules are now available unmetered, on all plans. For more information, refer to the [developer documentation](/waf/rate-limiting-rules/).
 
-***
+---
 
 ## Resources
 
-* [WAF Managed Rules](/waf/managed-rules/)
-* [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
-* [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
-* [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
-* [Client certificates](/ssl/client-certificates/)
-* [Rate limiting rules](/waf/rate-limiting-rules/)
+- [WAF Managed Rules](/waf/managed-rules/)
+- [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
+- [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
+- [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
+- [Client certificates](/ssl/client-certificates/)
+- [Rate limiting rules](/waf/rate-limiting-rules/)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
index 7f619ce81d0c809..a520969018400e2 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Content Management System (CMS) support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
index 72cf2b3808b2ec2..b1a0aaaa794a451 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
@@ -14,16 +14,16 @@ If you are using [Cloudflare's WordPress plugin](/automatic-platform-optimizatio
 
 ![Cloudflare's one-click configuration WordPress plugin.](~/assets/images/support/dash-optimize_wordpress.png)
 
-| **Setting**                            | **Value**                          |
-| -------------------------------------- | ---------------------------------- |
-| Caching level                          | Standard                           |
-| Browser Cache TTL                      | 4 hours                            |
-| Always Online                          | On                                 |
-| Development Mode                       | Disabled                           |
-| IPV6 Compatibility                     | On                                 |
-| WebSockets                             | On                                 |
-| IP Geolocation                         | On                                 |
-| Email Address Obfuscation              | On                                 |
-| Hotlink Protection                     | Off                                |
-| Image optimization (Polish)            | Off (unless on Pro or higher plan) |
-| Rocket Loader                          | Off                                |
+| **Setting**                 | **Value**                          |
+| --------------------------- | ---------------------------------- |
+| Caching level               | Standard                           |
+| Browser Cache TTL           | 4 hours                            |
+| Always Online               | On                                 |
+| Development Mode            | Disabled                           |
+| IPV6 Compatibility          | On                                 |
+| WebSockets                  | On                                 |
+| IP Geolocation              | On                                 |
+| Email Address Obfuscation   | On                                 |
+| Hotlink Protection          | Off                                |
+| Image optimization (Polish) | Off (unless on Pro or higher plan) |
+| Rocket Loader               | Off                                |
diff --git a/src/content/docs/support/third-party-software/forum-software/index.mdx b/src/content/docs/support/third-party-software/forum-software/index.mdx
index 6b8e3da66053d73..a3bd9f78a0ca9a2 100644
--- a/src/content/docs/support/third-party-software/forum-software/index.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Forum Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
index 1b3e0496d4d3820..0669bac8222e466 100644
--- a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
@@ -13,14 +13,14 @@ Many widely used forum platforms are compatible with Cloudflare.
 
 These include:
 
-* [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
-* vBulletin
-* Xenforo
-* MyBB
+- [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
+- vBulletin
+- Xenforo
+- MyBB
 
 If you have a forum using these platforms, you can increase its speed and safety by adding Cloudflare.
 
-***
+---
 
 ## Steps
 
diff --git a/src/content/docs/support/third-party-software/index.mdx b/src/content/docs/support/third-party-software/index.mdx
index b79e7fe82f69cfc..64ef43df834abe9 100644
--- a/src/content/docs/support/third-party-software/index.mdx
+++ b/src/content/docs/support/third-party-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Third-Party Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/index.mdx b/src/content/docs/support/third-party-software/others/index.mdx
index 70b8ce2974da5f2..d253e19c2efccb6 100644
--- a/src/content/docs/support/third-party-software/others/index.mdx
+++ b/src/content/docs/support/third-party-software/others/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Others support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
index 4cbb158f3f19295..a32fb2d6902eb8f 100644
--- a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
+++ b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
@@ -13,7 +13,7 @@ Cloudflare launched Bandwidth Alliance in 2018 – a group of forward-looking cl
 
 Cloudflare customers using Azure can lower their egress bills between Cloudflare and Azure via [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/virtual-network/routing-preference-overview).
 
-***
+---
 
 ## How to
 
@@ -31,9 +31,9 @@ To lower your data transfer costs from Azure and Cloudflare: 
 
 For additional details, refer to [Configure network routing preference for Azure Storage](https://docs.microsoft.com/en-us/azure/storage/common/configure-network-routing-preference?tabs=azure-portal) and [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/storage/common/network-routing-preference).
 
-***
+---
 
 ## Related resources
 
-* [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
-* [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
+- [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
+- [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
index 3a30b097d7d9ced..f5af757c7bdc872 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
@@ -26,7 +26,7 @@ This process will allow us to link your account inside our new support system.
 
 If you are a free account customer, you do not have access to this feature, but you can get assistance in many other ways:
 
-* By joining the conversation in our [Community forums](https://community.cloudflare.com/).
-* By joining our [Discord server](https://discord.cloudflare.com/).
-* By checking out our [Documentation](/).
-* By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
+- By joining the conversation in our [Community forums](https://community.cloudflare.com/).
+- By joining our [Discord server](https://discord.cloudflare.com/).
+- By checking out our [Documentation](/).
+- By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
index a1ec1b9e2b99753..2a8ae8a1e746734 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
@@ -23,18 +23,18 @@ customers due to security and liability concerns.
 
 Use this table to quickly identify which troubleshooting method to use based on your issue:
 
-| Issue Type | Recommended Tool | When to Use |
-|------------|------------------|-------------|
-| Page not loading correctly | [HAR file](#generate-a-har-file) | Visual issues, broken elements, slow page loads |
-| JavaScript errors | [Console log](#export-console-log) | CORS errors, scripts failing, browser-side errors |
-| Protocol errors (QUIC/HTTP2) | [NetLog dump](#capture-a-netlog-dump) | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR` |
-| Slow response times | [curl (performance)](#performance) | Measuring latency, TLS handshake times |
-| HTTP errors (5xx, 4xx) | [curl (HTTP errors)](#http-errors) | Determining if errors originate from Cloudflare or origin |
-| Caching issues | [curl (caching)](#caching) | Cache misses, stale content, cache headers |
-| SSL/TLS certificate issues | [curl (SSL/TLS)](#ssltls-certificates) | Certificate errors, TLS version issues |
-| Connection timeouts/drops | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr) | Network path issues, latency between hops |
-| Packet loss, connection resets | [Packet capture](#run-packet-captures) | Layer 3/4 issues, SSL handshake failures |
-| Identifying serving location | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests |
+| Issue Type                     | Recommended Tool                                                                    | When to Use                                               |
+| ------------------------------ | ----------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| Page not loading correctly     | [HAR file](#generate-a-har-file)                                                    | Visual issues, broken elements, slow page loads           |
+| JavaScript errors              | [Console log](#export-console-log)                                                  | CORS errors, scripts failing, browser-side errors         |
+| Protocol errors (QUIC/HTTP2)   | [NetLog dump](#capture-a-netlog-dump)                                               | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR`     |
+| Slow response times            | [curl (performance)](#performance)                                                  | Measuring latency, TLS handshake times                    |
+| HTTP errors (5xx, 4xx)         | [curl (HTTP errors)](#http-errors)                                                  | Determining if errors originate from Cloudflare or origin |
+| Caching issues                 | [curl (caching)](#caching)                                                          | Cache misses, stale content, cache headers                |
+| SSL/TLS certificate issues     | [curl (SSL/TLS)](#ssltls-certificates)                                              | Certificate errors, TLS version issues                    |
+| Connection timeouts/drops      | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr)                         | Network path issues, latency between hops                 |
+| Packet loss, connection resets | [Packet capture](#run-packet-captures)                                              | Layer 3/4 issues, SSL handshake failures                  |
+| Identifying serving location   | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests        |
 
 ---
 
@@ -53,7 +53,7 @@ A HTTP Archive (HAR) records all web browser requests including the request and
 :::caution
 
 A HAR file can include sensitive details such as passwords, payment
-information, and private keys. 
+information, and private keys.
 
 Remove sensitive information using a [HAR Sanitizer](https://har-sanitizer.pages.dev/).
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
index 2d097e0a9229ebd..75fdc9854918fee 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
@@ -6,6 +6,6 @@ products:
   - support
 ---
 
-Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability. 
+Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability.
 
 In instances where performance and reliability are in conflict, our systems are designed to prioritize a stable connection over a local one.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
index 058aa4d051dd35b..256522df2decdc4 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for General Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
index acc27ba05615fa5..738bb5db1983575 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
@@ -8,18 +8,18 @@ products:
 
 This article may help if you are unable to receive transactional emails from Cloudflare. These types of email include:
 
-* email verification
-* forgot / reset password
-* any other type of automated notification generated by the Cloudflare dashboard
+- email verification
+- forgot / reset password
+- any other type of automated notification generated by the Cloudflare dashboard
 
 If you are expecting but not receiving these emails from Cloudflare, review the following.
 
 ## Causes
 
-* Your email address is incorrect or mistyped in the Cloudflare dashboard
-* Your email server or mailbox is not working
-* Your mail server or software is filtering or blocking messages from Cloudflare
-* Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
+- Your email address is incorrect or mistyped in the Cloudflare dashboard
+- Your email server or mailbox is not working
+- Your mail server or software is filtering or blocking messages from Cloudflare
+- Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
 
 ## Solution
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
index 3a81d5514edb8f9..d7bbd6cd5dbd72d 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
@@ -6,17 +6,17 @@ products:
   - support
 ---
 
-Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare. 
+Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare.
 
 This appears to restrict data transfer to approximately 16 KB per connection, which renders most websites, including those of our customers, inaccessible or unusable for visitors from Russia.
 
 What to expect with your website:
 
-- This is not due to a misconfiguration of your Cloudflare settings. 
+- This is not due to a misconfiguration of your Cloudflare settings.
 - You will likely see a significant drop in traffic from users in Russia in your Cloudflare Analytics.
 - Your visitors in Russia may experience connection failures or sites that do not load properly.
-- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users. 
+- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users.
 
 If you are a Cloudflare enterprise customer, contact your account team for further assistance.
 
-For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/). 
\ No newline at end of file
+For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/).
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
index 37ece0e92f767e7..eeef01c3bebc4e4 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
@@ -30,15 +30,15 @@ F5 session cookies can have arbitrary names but typically follow a specific form
 
 - Without encryption (trivially decoded to show origin server IP and port):
 
-   ```txt
-   BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
-   ```
+  ```txt
+  BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
+  ```
 
 - With encryption:
 
-   ```txt
-   BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
-   ```
+  ```txt
+  BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
+  ```
 
 #### 2. Test for the issue
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
index 78c13a35999c2b2..e47931dd17c1429 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
@@ -9,46 +9,46 @@ products:
 
 Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
 
-***
+---
 
 ## Disable Anti-bot modules
 
 Search engine crawlers' requests, when proxied through Cloudflare, can be blocked by anti-bot modules installed on your origin server. Try disabling any anti-bot modules to prevent your origin from blocking these requests.
 
-***
+---
 
 ## Adjust Google and Bing crawl rates
 
 To optimize CDN performance, Google and Bing assign special crawl rates to websites that use CDN services in order. Special crawl rates do not negatively affect Search Engine Optimization (SEO) and Search Engine Results Pages (SERPs). To change your crawl rates for Bing and Google, follow the guides below:
 
-* Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
-* Change your Bing crawl rate via guidance from Bing’s documentation:
-  * [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
-  * [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
+- Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
+- Change your Bing crawl rate via guidance from Bing’s documentation:
+  - [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
+  - [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
 
-***
+---
 
 ## Prevent crawl errors
 
 Review the following recommendations to prevent crawler errors:
 
-* Monitor the performance and availability of your website using a third-party tool:
-  * [StatusCake](http://www.statuscake.com/)
-  * [Pingdom](http://www.pingdom.com/)
-  * [Monitor.Us](http://www.monitor.us/)
-  * [Updown](https://updown.io/)
+- Monitor the performance and availability of your website using a third-party tool:
+  - [StatusCake](http://www.statuscake.com/)
+  - [Pingdom](http://www.pingdom.com/)
+  - [Monitor.Us](http://www.monitor.us/)
+  - [Updown](https://updown.io/)
 
-* Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
+- Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
 
   Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
 
-* Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
+- Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
 
-* Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
+- Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
 
 Google uses a [variety of User-Agents](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers) to crawl your website. You can [test your `robots.txt` via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
 
-* Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
+- Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
 
 `Disallow: /cdn-cgi/`
 
@@ -57,10 +57,10 @@ Google uses a [variety of User-Agents](https://developers.google.com/search/docs
 Errors for `cdn-cgi` do not impact site rankings.
 :::
 
-* Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
-* [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
+- Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943).
+- [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
 
-***
+---
 
 ## Troubleshoot crawl errors
 
@@ -107,7 +107,7 @@ If the above troubleshooting steps do not resolve your crawl errors, follow the
 3. Click **Download** to export the list of errors as a `.csv` file.
 4. Provide the downloaded `.csv` file to Cloudflare support.
 
-***
+---
 
 ## Related resources
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
index f5f8373a02c6fde..fd1f90255a9adde 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
@@ -15,7 +15,7 @@ For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
 
 ### Common use cases
 
-A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. 
+A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing.
 For example:
 
 - If the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
index 6f67fbca6e007e6..b62f398bfdbf194 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
@@ -21,4 +21,4 @@ If the client resends the request with the same credentials and the challenge re
 
 ### Cloudflare-specific information
 
-When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
\ No newline at end of file
+When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
index dc315ae8a719b89..5ab48647ac86db3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
@@ -19,4 +19,4 @@ For example, if a client requests content in a specific language or character se
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
\ No newline at end of file
+Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
index 8083045fa4bc840..dd4f38c4aa51099 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
@@ -18,4 +18,4 @@ This error typically occurs in environments where a proxy server is used as an i
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
\ No newline at end of file
+Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
index 5b3115cc744996f..f2e5da4a9064ce3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
@@ -21,4 +21,4 @@ This error typically occurs when a client fails to send a complete request withi
 
 If a `408` error occurs on a Cloudflare-powered site, it is most often being proxied from the origin. In these cases, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly.
 
-Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
\ No newline at end of file
+Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
index 87e414554c0bf55..c0098ba91b387b4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
@@ -22,4 +22,4 @@ This error typically happens with a `PUT` request when multiple clients are atte
 
 ### Cloudflare-specific information
 
-Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
\ No newline at end of file
+Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
index efdb6f72bdc5fe1..17e6ee5ff4d269a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
@@ -23,4 +23,4 @@ This status is commonly applied to deprecated content, such as outdated pages or
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
+Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
index 2bbf1fafa9e5767..47fe8d6954c39bd 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
@@ -19,4 +19,4 @@ This status code can occur in various scenarios, such as when a client sends an
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
+Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
index 6c46a3195a74a9e..11efe2add1f92d6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
@@ -19,4 +19,4 @@ One common use case for the `412 Precondition Failed` status code is version con
 
 ### Cloudflare-specific information
 
-Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
\ No newline at end of file
+Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
index df0769a0b4bfd44..effc3539c4d9e6a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
@@ -27,4 +27,4 @@ The upload limit for the Cloudflare API depends on your plan. If you exceed this
 
 Keep in mind, customers can reduce the **Maximum Upload Size** from the zone's **Network** page which can cause a `413`.
 
-If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
\ No newline at end of file
+If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
index d27ba07b657f86b..c6b7876ce046cf3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
@@ -19,4 +19,4 @@ For example, if a client is attempting a `GET` request with an unusually long UR
 
 ### Cloudflare-specific information
 
-Cloudflare will generate a `414` response if the URI length exceeds 32KB.
\ No newline at end of file
+Cloudflare will generate a `414` response if the URI length exceeds 32KB.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
index 62c07d24e2e5251..bf00d11dff44238 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
@@ -19,4 +19,4 @@ This error can happen when a client requests a byte range outside the bounds of
 
 ### Cloudflare-specific information
 
-Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
\ No newline at end of file
+Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
index 5ad66dd00072ced..711500dca7e9bae 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
@@ -19,4 +19,4 @@ Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify
 
 ### Cloudflare-specific information
 
-Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
\ No newline at end of file
+Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
index 995be774a343c75..7d4d40af9d2bd76 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
@@ -32,4 +32,3 @@ Cloudflare applies rate limiting to requests for R2 managed public buckets acces
 #### Website end users
 
 Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
index 4d7d15261e11b47..7a3792b883d662c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
@@ -19,4 +19,4 @@ This occurs when access to a resource is blocked due to court orders, copyright
 
 ### Cloudflare-specific information
 
-Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
\ No newline at end of file
+Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
index d9e3fe99f491207..c2a6601666766b7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
@@ -15,7 +15,7 @@ products:
 
 ## Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), which can be useful to investigate HTTP Errors.
 
@@ -27,7 +27,6 @@ For a complete description of this error refer to the [Error 400](/support/troub
 
 For a complete description of this error refer to the [Error 401](/support/troubleshooting/http-status-codes/4xx-client-error/error-401/) page.
 
-
 ## 402 Payment Required
 
 The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231).
@@ -36,7 +35,6 @@ The `402 Payment Required` status code is reserved for future use and is not yet
 
 For a complete description of this error refer to the [Error 403](/support/troubleshooting/http-status-codes/4xx-client-error/error-403/) page.
 
-
 ## 404 Not Found
 
 For a complete description of this error refer to the [Error 404](/support/troubleshooting/http-status-codes/4xx-client-error/error-404/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
index 36deca809c49e5c..18167b8092b1b9b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
@@ -20,4 +20,4 @@ This error occurs when there are duplicate list items in a single operation to a
 
 ### Resolution
 
-You need to remove the duplicate item and try again.
\ No newline at end of file
+You need to remove the duplicate item and try again.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
index ec68460a428d719..107785e0dccf2ec 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
@@ -20,4 +20,4 @@ This error occurs when the source URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the source URL.
\ No newline at end of file
+You need to use a shorter URL as the source URL.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
index 687c3022a1391f4..c5307d8789975fb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
@@ -20,4 +20,4 @@ This error occurs when the target URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the target URL.
\ No newline at end of file
+You need to use a shorter URL as the target URL.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
index 16221ebbff83170..e061d57515adeb3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
index 263401952d5dc31..16897ff09f53dfb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
\ No newline at end of file
+You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
index ba1cd6d9d14c953..1bc04c5dadad755 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
@@ -17,4 +17,4 @@ This error occurs when you specify a URL redirect status code that is not suppor
 
 ### Resolution
 
-Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
\ No newline at end of file
+Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
index 5d066ea9c0d5f2c..a68813f6502ebc5 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve path suffix** option in a redir
 
 ### Resolution
 
-Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
\ No newline at end of file
+Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
index 343a60e375b1269..085dc2ea7f596d2 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect has an invalid scheme, w
 
 ### Resolution
 
-Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
index e037df5b8d6fdca..172b34e6b076576 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a user info com
 
 ### Resolution
 
-You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
index e4399c78df33671..a7ea0e0f82e50c6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect does not include an auth
 
 ### Resolution
 
-Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
\ No newline at end of file
+Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
index 36d65f8b2d2d541..371faef69c84269 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a port (for exa
 
 ### Resolution
 
-Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
index 4cacdc75502b532..c0c9c3440aa4398 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve query string** option of a URL
 
 ### Resolution
 
-To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
\ No newline at end of file
+To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
index d6b879890b89165..1198b1552a6e89e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
@@ -20,4 +20,4 @@ This error occurs when different types of list items (such as IP addresses, host
 Remove the list items that do not apply to the list type. This means:
 
 - Removing IP addresses from a request to add items to a Bulk Redirect List.
-- Removing URL redirects from a request to add items to an IP list.
\ No newline at end of file
+- Removing URL redirects from a request to add items to an IP list.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
index 158e45e84a4d659..6c39cf94fee9dc4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
@@ -21,4 +21,4 @@ Make sure you are adding the items to the correct list:
 
 - Custom lists with IP addresses (IP lists) can only contain IP addresses as list items.
 - Custom lists with hostnames can only contain hostnames as list items.
-- Bulk Redirect Lists can only contain URL redirects as list items.
\ No newline at end of file
+- Bulk Redirect Lists can only contain URL redirects as list items.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
index 37a293ffd69b91e..7d137ba67522622 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
@@ -17,4 +17,4 @@ This error occurs when you have more than the maximum number of URL redirects wi
 
 ### Resolution
 
-Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
\ No newline at end of file
+Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
index eb841ff74628814..617ad8ff0c6f421 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL of a URL redirect does not include a schem
 
 ### Resolution
 
-Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
\ No newline at end of file
+Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
index c47d1c3dccc0286..1b97c64adc8da93 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
@@ -76,4 +76,4 @@ For a complete description of this error refer to the [Error 10059](/support/tro
 
 ## Error 10060: Missing scheme in redirect target URL
 
-For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
\ No newline at end of file
+For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
index ed56fe2d03d4b5c..23d789e3acc15d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
@@ -27,4 +27,4 @@ Cloudflare halted the request for one of the following reasons:
 
 - If an A record within your Cloudflare DNS app points to a [Cloudflare IP address](https://www.cloudflare.com/ips/), update the IP address to your origin web server IP address. Reach out to your hosting provider if you need help obtaining the origin IP address.
 - There is a reverse-proxy at your origin that sends the request back through the Cloudflare proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.
-- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
\ No newline at end of file
+- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
index ccc795620204019..2c3f226dc6e792c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
@@ -1,13 +1,13 @@
 ---
 pcx_content_type: troubleshooting
-title: Error 1002 
+title: Error 1002
 source: null
 description: Troubleshoot Cloudflare 1002 error code.
 products:
   - support
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 ## Error 1002: DNS points to Prohibited IP
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
index e1345953169f933..23dc25e82509737 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
@@ -19,4 +19,3 @@ This error indicates that the host is not configured to serve web traffic.
 ### Resolution
 
 If the issue persists beyond five minutes, [contact Cloudflare Support](/support/contacting-cloudflare-support/).
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
index 0927129b5cce7e1..3f1e6d6819b72b2 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
@@ -19,4 +19,3 @@ The owner of the website (for example, `example.com`) has banned the country or
 
 - If you are a site visitor, contact the site owner and ask them to allow your IP address.
 - If you are the site owner, ensure that the reported IP address is allowed under the [IP Access rules](/waf/tools/ip-access-rules/) security feature.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
index 1f107b8f72b7f05..8c178fd7a6ca6f1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
@@ -22,6 +22,5 @@ Another common cause is connecting a custom domain to an R2 bucket, where the do
 - To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/).
 - To allow connecting to a R2 bucket with a custom domain, disable the [zone hold](/fundamentals/account/account-security/zone-holds/) feature on the custom domain target zone to resolve the 1014 error.
 - To allow connections to an R2 bucket whose zone is banned:
-
   - First, check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one).
   - Second, make sure that you have no unpaid invoice(s), as you will not be able to enable any new services until [any outstanding balance](/billing/manage/pay-invoices-overdue-balances/) is addressed. If this does not resolve the issue, contact your account team.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
index 9b401eee437c5d7..27a7f8ca892a5ae 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
@@ -27,4 +27,4 @@ For example, the following URI path rewrite expression is not valid:
 
 To fix the expression above, add a `/` prefix:
 
-`concat("/", lower(ip.src.country), http.request.uri.path)`
\ No newline at end of file
+`concat("/", lower(ip.src.country), http.request.uri.path)`
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
index 8ca43a2009913cf..a07128b006e1a78 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
@@ -18,4 +18,3 @@ You are trying to modify an HTTP header that Request Header Transform Rules cann
 ### Resolution
 
 Make sure you are not trying to modify one of the [reserved HTTP request headers](/rules/transform/request-header-modification/#important-remarks).
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
index 1468ee4c28b0408..ca8eb720fb9b8ca 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
@@ -57,4 +57,3 @@ To avoid exceeding memory limits:
 
 - [Error 1101](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1101/) - Workers JavaScript runtime exception
 - [Error 503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503/) - Service temporarily unavailable (can be caused by Workers CPU or memory limits)
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
index a31eb60f8fa2f99..064d799dd10135c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
@@ -32,7 +32,6 @@ For a complete description of this error refer to the [Error 1000](/support/trou
 
 For a complete description of this error refer to the [Error 1001](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/) page.
 
-
 ## Error 1002: DNS points to Prohibited IP
 
 For a complete description of this error refer to the [Error 1002: DNS points to Prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002/#error-1002-dns-points-to-prohibited-ip) page.
@@ -85,12 +84,10 @@ For a complete description of this error refer to the [Error 1014](/support/trou
 
 For a complete description of this error refer to the [Error 1015](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1015/) page.
 
-
 ## Error 1016: Origin DNS error
 
 For a complete description of this error refer to the [Error 1016](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016/) page.
 
-
 ## Error 1018: Could not find host
 
 For a complete description of this error refer to the [Error 1018](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1018/) page.
@@ -154,4 +151,3 @@ For a complete description of this error refer to the [Error 1104](/support/trou
 ## Error 1200: Cache connection limit
 
 For a complete description of this error refer to the [Error 1200](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1200/) page.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
index 137fd47bdd00bcb..aa184c991eb318f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
@@ -18,4 +18,4 @@ Cloudflare Workers returns a `501` error when a request uses an HTTP method that
 
 ### Resolution
 
-- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
\ No newline at end of file
+- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
index f03079632ed610b..4f5ba4cb59b6c1d 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
@@ -52,10 +52,10 @@ If you are using Workers, check the Workers dashboard for error logs and resourc
 
 Use the error page content to determine whether a 503 was generated by Cloudflare or your origin server:
 
-| Signal | Interpretation |
-|--------|---------------|
-| Error page HTML contains `cloudflare` or `cloudflare-nginx` | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
-| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly |
+| Signal                                                              | Interpretation                                                                                                                     |
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| Error page HTML contains `cloudflare` or `cloudflare-nginx`         | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
+| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly                                                                                             |
 
 ### Cloudflare-generated 503
 
@@ -64,4 +64,3 @@ A Cloudflare-generated 503 indicates a connectivity issue in a Cloudflare data c
 ### Origin-generated 503
 
 If your origin generated a 503, check origin server logs for signs of overload: CPU/memory saturation, exhausted connection pool, or application-level maintenance mode.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
index 1ce4d0ddda9a4a1..c5e17a3afac58f5 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
@@ -68,4 +68,3 @@ To distinguish between the two, check the `CacheStatus` field in the same log re
 Do not conclude your origin returned a 5xx error solely because `OriginResponseStatus = 0`. Always check `CacheStatus` first to determine whether Cloudflare contacted the origin at all.
 
 :::
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
index 1759ae0d321392e..a49d78dbb7cbe12 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
@@ -21,7 +21,6 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 ### Resolution
 
 - Contact your hosting provider and share the [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist in troubleshooting these common causes:
-
   - [Cloudflare IP addresses](https://www.cloudflare.com/ips/) are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider allows **all Cloudflare IP ranges** (most common cause). You can use a [Cloudflare WAF Custom Rule](/waf/custom-rules/use-cases/block-by-geographical-location/) if you need to restrict traffic from geographical locations.
   - An overloaded or offline origin web server drops incoming requests.
   - [Keepalives](http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html) are disabled at the origin web server.
@@ -32,9 +31,8 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 
 - If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a `522` error. Consider using a [Route](/workers/configuration/routing/), targeting another hostname, or enabling the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) instead.
 
-- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`. 
+- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`.
 
 - If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before [contacting Cloudflare support](/support/contacting-cloudflare-support/):
-
   - An [MTR or traceroute](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#perform-a-traceroute) from your origin web server to a [Cloudflare IP address](http://www.cloudflare.com/ips) that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
   - Details from the hosting provider's investigation, such as pertinent logs or conversations with the hosting provider.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
index b67257eb3168ed7..b075caaba321bfa 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
@@ -18,7 +18,6 @@ The error `524` occurs if the origin web server acknowledges (ACK) the resource
 
 Error `524` can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/) (or 6.5 seconds in the case of [Cloudflare Images](/images/)). This timeout cannot be adjusted.
 
-
 ### Resolution at your origin
 
 Here are the options we suggest to work around this issue:
@@ -31,7 +30,7 @@ Here are the options we suggest to work around this issue:
 
 :::note
 
-Logging request response time at your origin web server may help identify the cause of resource slowness. 
+Logging request response time at your origin web server may help identify the cause of resource slowness.
 Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as [Apache](http://httpd.apache.org/docs/current/mod/mod_log_config.html) or [Nginx](http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format).
 :::
 
@@ -42,7 +41,7 @@ Here are some other actions you can take on the Cloudflare side:
 - If you regularly run HTTP requests that take over 120 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
 - Enterprise customers can increase the `524` timeout up to 6,000 seconds:
   - If your content can be cached, you can create a [Cache Rule](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only) with the `Proxy Read Timeout` setting. The content needs to be cacheable for the rule to be triggered, but does not need to be cached.
-  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/). 
+  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/).
 
 :::note
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
index 5278dcbd17ebc5f..1e57ec517869150 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
@@ -43,4 +43,4 @@ If `525` errors occur intermittently, review the origin web server error logs to
 
 - [Review the cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/) used by your server to ensure they are compatible with Cloudflare.
 
-- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
\ No newline at end of file
+- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
index d438cc1893edcbb..1bd602ef3df5764 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
@@ -46,7 +46,7 @@ To view Error Analytics:
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific Ray ID, which can be useful to investigate HTTP Errors.
 
@@ -72,7 +72,6 @@ For a complete description of this error refer to the [Error 503](/support/troub
 
 For a complete description of this error refer to the [Error 520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) page.
 
-
 ## Error 521: web server is down
 
 For a complete description of this error refer to the [Error 521](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) page.
@@ -85,17 +84,14 @@ For a complete description of this error refer to the [Error 522](/support/troub
 
 For a complete description of this error refer to the [Error 523](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) page.
 
-
 ## Error 524: a timeout occurred
 
 For a complete description of this error refer to the [Error 524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) page.
 
-
 ## Error 525: SSL handshake failed
 
 For a complete description of this error refer to the [Error 525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/) page.
 
-
 ## Error 526: invalid SSL certificate
 
 For a complete description of this error refer to the [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
index f0c29b1fb117d8a..ec947473bacdc11 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
@@ -28,9 +28,8 @@ Reproduce the error and inspect response headers using one of:
 
 ## Using cf-error-type for diagnosis
 
-| `cf-error-type` prefix | Origin | Next step |
-|---|---|---|
-| `1xxx` | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
-| `1101` / `1102` | Workers runtime | Check `wrangler tail` for the exception |
-| `52x` | Origin connectivity | Check origin server is up and reachable |
-
+| `cf-error-type` prefix | Origin              | Next step                                              |
+| ---------------------- | ------------------- | ------------------------------------------------------ |
+| `1xxx`                 | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
+| `1101` / `1102`        | Workers runtime     | Check `wrangler tail` for the exception                |
+| `52x`                  | Origin connectivity | Check origin server is up and reachable                |
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
index 01c72d0bc87c34f..6c1c9d2be8a69d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for HTTP Status Codes support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/index.mdx
index d81e4565fde34b9..03006375415d51d 100644
--- a/src/content/docs/support/troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
index 3594cec54c60318..09b614cc99e93e2 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Restoring Visitor IPs support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
index dd9d3148e61c91c..e1a34f3e2f2c079 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
@@ -216,7 +216,7 @@ Use the [`ngx_http_realip_module` Nginx module](http://nginx.org/en/docs/http/ng
 
 ```
 #example IP address
-set_real_ip_from 192.0.2.1; 
+set_real_ip_from 192.0.2.1;
 
 #use any of the following two
 
@@ -463,6 +463,7 @@ For more details, refer to [Custom header original IP detection extension](https
 If you are running an application behind [Caddy](https://caddyserver.com/) that relies on the `X-Forwarded-For` header, you can configure Caddy to override the header with Cloudflare's [CF-Connecting-IP header](/fundamentals/reference/http-headers/#cf-connecting-ip).
 
 It is advised that you also only accept traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/); otherwise, the header could be spoofed. That's why, in the second example, we handle this as part of the Caddy configuration. Alternatively, you can handle this at the firewall level, which is usually easier to automate. If you already have a firewall or other measure in place to ensure this, your Caddyfile could look like this:
+
 ```txt title="Caddyfile"
 https://example.com {
     reverse_proxy localhost:8080 {
@@ -473,6 +474,7 @@ https://example.com {
 ```
 
 If you want Caddy to handle only accepting traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/), you can use a configuration like this one:
+
 ```txt title="Caddyfile"
 https://example.com {
     # Restrict access to Cloudflare IPs (https://www.cloudflare.com/ips/)
@@ -494,6 +496,7 @@ https://example.com {
     }
 }
 ```
+
 ---
 
 ## Related Resources
diff --git a/src/content/docs/tenant/how-to/index.mdx b/src/content/docs/tenant/how-to/index.mdx
index 036aa6d32db9c09..5b478d437d47b4b 100644
--- a/src/content/docs/tenant/how-to/index.mdx
+++ b/src/content/docs/tenant/how-to/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/tenant/index.mdx b/src/content/docs/tenant/index.mdx
index f669fc53278a372..a9bea30e67a18fc 100644
--- a/src/content/docs/tenant/index.mdx
+++ b/src/content/docs/tenant/index.mdx
@@ -19,7 +19,7 @@ These APIs are built into our Client v4 API library to provide a streamlined onb
 
 As you dive into the Tenant API, take advantage of the following resources:
 
-* [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
-* [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
-* [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
-* [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
+- [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
+- [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
+- [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
+- [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
diff --git a/src/content/docs/tenant/reference/index.mdx b/src/content/docs/tenant/reference/index.mdx
index ed9d4e28bbe4895..cc579a35dcc72f4 100644
--- a/src/content/docs/tenant/reference/index.mdx
+++ b/src/content/docs/tenant/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/terraform/advanced-topics/best-practices.mdx b/src/content/docs/terraform/advanced-topics/best-practices.mdx
index e3dd89c7e78f2e0..8bc08838c5a7125 100644
--- a/src/content/docs/terraform/advanced-topics/best-practices.mdx
+++ b/src/content/docs/terraform/advanced-topics/best-practices.mdx
@@ -189,10 +189,8 @@ Using modules also increases the difficulty of debugging or reproducing issues a
 
 :::caution
 
-
 This advice also applies to [Terraform dynamic blocks](https://www.terraform.io/language/expressions/dynamic-blocks) that allow you to do logic in your HCL. Since these dynamic blocks are always evaluated, you can get yourself into situations where you have logic bugs in your configuration (and making the end result unreproducible).
 
-
 :::
 
 ## Migrate resources into Terraform
diff --git a/src/content/docs/terraform/how-to/create-partial-zone.mdx b/src/content/docs/terraform/how-to/create-partial-zone.mdx
index 7ddc5bbf8335cb9..b6532b8ca83d6a4 100644
--- a/src/content/docs/terraform/how-to/create-partial-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-partial-zone.mdx
@@ -39,6 +39,7 @@ resource "cloudflare_zone" "subdomain_example_com" {
 ```
 
 Then, in a new Terraform plan and apply cycle, upgrade the zone to a Business plan or higher:
+
 ```hcl
 resource "cloudflare_zone_subscription" "example_zone_subscription" {
   zone_id = cloudflare_zone.subdomain_example_com.id
@@ -72,4 +73,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Partial zone setup](/dns/zone-setups/partial-setup/)
 - [Convert a full zone to partial](/dns/zone-setups/conversions/convert-full-to-partial/)
-- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
\ No newline at end of file
+- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
diff --git a/src/content/docs/terraform/how-to/create-secondary-zone.mdx b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
index df90ad68810ec8a..ab90c9a7bf683c7 100644
--- a/src/content/docs/terraform/how-to/create-secondary-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
@@ -13,7 +13,9 @@ products:
 ---
 
 A [subdomain zone](/dns/zone-setups/subdomain-setup/) lets you manage a subdomain in a separate Cloudflare zone from the parent domain. This is useful for access control and team management. This guide shows how to automate the setup using the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs). It is only available for Enterprise accounts
+
 > NOTE: subdomain setup is only available for Enterprise accounts
+
 ## Prerequisites
 
 - Terraform installed. Refer to [Get started](/terraform/installing/).
@@ -43,4 +45,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Subdomain setup](/dns/zone-setups/subdomain-setup/)
 - [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
-- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
\ No newline at end of file
+- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
diff --git a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
index 2ab6af754503c16..4fe8686bb0585da 100644
--- a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
+++ b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
@@ -24,4 +24,4 @@ Use this:
 
 ```txt "zones[0]"
 zone_id = data.cloudflare_zones.example_com.zones[0].id`
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/terraform/tutorial/index.mdx b/src/content/docs/terraform/tutorial/index.mdx
index 9eb9b90d3aaf527..0a16482753a93c7 100644
--- a/src/content/docs/terraform/tutorial/index.mdx
+++ b/src/content/docs/terraform/tutorial/index.mdx
@@ -10,41 +10,41 @@ products:
 
 Before you begin, [install Terraform](/terraform/installing/). Each tutorial builds on the previous, so you should complete the tutorials in the order shown below.
 
-:::note 
+:::note
 If you are upgrading from v4, review the [migration guide](https://github.com/cloudflare/terraform-provider-cloudflare/blob/main/docs/guides/version-5-upgrade.md) for breaking changes.
 :::
 
 ## [1 – Initialize Terraform](/terraform/tutorial/initialize-terraform/)
 
-* Brief introduction.
-* Introduction of `terraform init`, `plan`, `apply`, and `show`.
-* Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
+- Brief introduction.
+- Introduction of `terraform init`, `plan`, `apply`, and `show`.
+- Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
 
 ## [2 – Track your history](/terraform/tutorial/track-history/)
 
-* Store Cloudflare configuration in source control.
+- Store Cloudflare configuration in source control.
 
 ## [3 – Configure HTTPS settings](/terraform/tutorial/configure-https-settings/)
 
-* Modify zone settings.
-* Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
+- Modify zone settings.
+- Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
 
 ## [4 – Improve performance and reliability](/terraform/tutorial/use-load-balancing/)
 
-* Add load balancing rules.
-* Resources covered:
-  * [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
-  * [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
-  * [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
+- Add load balancing rules.
+- Resources covered:
+  - [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
+  - [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
+  - [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
 
 ## [5 – Add exceptions with page rules](/terraform/tutorial/add-page-rules/)
 
-* Add page rule.
-* Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
-* Increase security level for a specific URL: `/expensive-db-call`.
-* Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
+- Add page rule.
+- Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
+- Increase security level for a specific URL: `/expensive-db-call`.
+- Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
 
 ## [6 – Revert configuration](/terraform/tutorial/revert-configuration/)
 
-* Review change history.
-* Roll back changes.
+- Review change history.
+- Roll back changes.
diff --git a/src/content/docs/time-services/index.mdx b/src/content/docs/time-services/index.mdx
index 28cf018d1d9c55a..e0533cac714f018 100644
--- a/src/content/docs/time-services/index.mdx
+++ b/src/content/docs/time-services/index.mdx
@@ -12,7 +12,7 @@ products:
 description: Synchronize time with Cloudflare NTP, NTS, and Roughtime.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn more about Cloudflare’s suite of time services.
 
diff --git a/src/content/docs/time-services/roughtime/index.mdx b/src/content/docs/time-services/roughtime/index.mdx
index c63fcd5c61e6ed3..fa744d4dd0b4954 100644
--- a/src/content/docs/time-services/roughtime/index.mdx
+++ b/src/content/docs/time-services/roughtime/index.mdx
@@ -16,7 +16,7 @@ Endpoints on the Internet often synchronize their clocks using the [Network Time
 
 As a result, a man-in-the-middle attacker can easily influence a victim’s clock. By moving them back in time, the attacker can, for example, force a victim to accept an expired (and possibly compromised) TLS certificate or session ticket.
 
-For many applications, *precise* network time is not essential. It is sufficient to have *accurate* time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
+For many applications, _precise_ network time is not essential. It is sufficient to have _accurate_ time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
 
 ## Next steps
 
diff --git a/src/content/docs/time-services/roughtime/recipes.mdx b/src/content/docs/time-services/roughtime/recipes.mdx
index 47cfdd6f2bd8e21..c7873f7d93f6904 100644
--- a/src/content/docs/time-services/roughtime/recipes.mdx
+++ b/src/content/docs/time-services/roughtime/recipes.mdx
@@ -21,28 +21,28 @@ formatted as a JSON object. For example:
 
 ```json
 {
-  "servers": [
-    {
-      "name": "Cloudflare-Roughtime-2",
-      "publicKeyType": "ed25519",
-      "publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
-      "addresses": [
-        {
-          "protocol": "udp",
-          "address": "roughtime.cloudflare.com:2003"
-        }
-      ]
-    }
-  ]
+	"servers": [
+		{
+			"name": "Cloudflare-Roughtime-2",
+			"publicKeyType": "ed25519",
+			"publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
+			"addresses": [
+				{
+					"protocol": "udp",
+					"address": "roughtime.cloudflare.com:2003"
+				}
+			]
+		}
+	]
 }
 ```
 
-It includes each server's *root public key*. When the server starts, it
-generates an *online* public/secret key pair. The root secret key is used to create a *delegation* for the online public key and the online secret key is used to sign the response.
+It includes each server's _root public key_. When the server starts, it
+generates an _online_ public/secret key pair. The root secret key is used to create a _delegation_ for the online public key and the online secret key is used to sign the response.
 
 The delegation serves the same function as a traditional [X.509 certificate](https://en.wikipedia.org/wiki/X.509) on the web. The client first uses the root public key to verify the delegation, then uses the online public key to verify the response.
 
-Because the response is *auditable*, the protocol makes each client accountable to provide accurate time.
+Because the response is _auditable_, the protocol makes each client accountable to provide accurate time.
 
 The configuration also encodes the type of signature algorithm used by the
 server (currently only [Ed25519](https://en.wikipedia.org/wiki/EdDSA) is supported). Lastly, the configuration contains a list of addresses where the service can be reached and which transport protocol to use to reach them (currently only UDP is supported).
diff --git a/src/content/docs/time-services/tos.mdx b/src/content/docs/time-services/tos.mdx
index 919e1a6c1d5e131..3045d87449c98de 100644
--- a/src/content/docs/time-services/tos.mdx
+++ b/src/content/docs/time-services/tos.mdx
@@ -8,4 +8,4 @@ products:
 description: Cloudflare Time Services terms of use.
 ---
 
-By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
\ No newline at end of file
+By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
diff --git a/src/content/docs/tunnel/advanced/origin-parameters.mdx b/src/content/docs/tunnel/advanced/origin-parameters.mdx
index 765569e743882e5..8b0a1173bb017e7 100644
--- a/src/content/docs/tunnel/advanced/origin-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/origin-parameters.mdx
@@ -13,11 +13,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/origin-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
-    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
-  }}
+	file="tunnel/origin-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/tunnel/advanced/local-management/configuration-file/",
+		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+		validatingJwtURL:
+			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
+	}}
 />
diff --git a/src/content/docs/tunnel/advanced/run-parameters.mdx b/src/content/docs/tunnel/advanced/run-parameters.mdx
index 3024141c055de62..61f30d9abf493ba 100644
--- a/src/content/docs/tunnel/advanced/run-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/run-parameters.mdx
@@ -13,15 +13,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/run-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
-    metricsURL: "/tunnel/monitoring/#metrics",
-    usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
-    tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
-    tunnelPermissionsURL: "/tunnel/advanced/local-management/tunnel-permissions/",
-    createRemoteTunnelURL: "/tunnel/get-started/",
-    faqURL: "/tunnel/troubleshooting/"
-  }}
+	file="tunnel/run-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/tunnel/advanced/local-management/configuration-file/",
+		metricsURL: "/tunnel/monitoring/#metrics",
+		usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
+		tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
+		tunnelPermissionsURL:
+			"/tunnel/advanced/local-management/tunnel-permissions/",
+		createRemoteTunnelURL: "/tunnel/get-started/",
+		faqURL: "/tunnel/troubleshooting/",
+	}}
 />
diff --git a/src/content/docs/tunnel/changelog.mdx b/src/content/docs/tunnel/changelog.mdx
index 9a0b8f86b225617..dd0771082a7b9ac 100644
--- a/src/content/docs/tunnel/changelog.mdx
+++ b/src/content/docs/tunnel/changelog.mdx
@@ -12,7 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog
-	product="tunnel"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
\ No newline at end of file
+<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
diff --git a/src/content/docs/tunnel/deployment-guides/terraform.mdx b/src/content/docs/tunnel/deployment-guides/terraform.mdx
index 13890c8c111c1c4..cc28a315060b536 100644
--- a/src/content/docs/tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/tunnel/deployment-guides/terraform.mdx
@@ -80,7 +80,6 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
-
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/tunnel/downloads/system-requirements.mdx b/src/content/docs/tunnel/downloads/system-requirements.mdx
index 252a3704e2bda8c..df9a49384ea6c6e 100644
--- a/src/content/docs/tunnel/downloads/system-requirements.mdx
+++ b/src/content/docs/tunnel/downloads/system-requirements.mdx
@@ -17,7 +17,11 @@ import { Render, TunnelCalculator } from "~/components";
 Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availability) on two dedicated hosts per location with a minimum of 4 GB RAM and 4 CPU cores. Allocate 50,000 ports per host.
 
 ## Port configuration
-<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
+
+<Render
+	file="tunnel/availability/port-configuration"
+	product="cloudflare-one"
+/>
 
 ## ulimits (Linux and macOS)
 
@@ -26,6 +30,7 @@ Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availabil
 ## Capacity calculator
 
 To estimate tunnel capacity requirements for your deployment:
+
 1. Use the [metrics endpoint](/tunnel/monitoring/#cloudflared-metrics) to measure `cloudflared_tcp_total_sessions` and `cloudflared_udp_total_sessions`.
 2. Compute the average **TCP requests per second** by dividing `cloudflared_tcp_total_sessions` by total time.
 3. Compute the average **Non-DNS UDP requests per second** by dividing `cloudflared_udp_total_sessions` by total time.
diff --git a/src/content/docs/tunnel/troubleshooting.mdx b/src/content/docs/tunnel/troubleshooting.mdx
index 0c02d1a8ecf4b9a..06fba9a65a218a4 100644
--- a/src/content/docs/tunnel/troubleshooting.mdx
+++ b/src/content/docs/tunnel/troubleshooting.mdx
@@ -121,6 +121,7 @@ As a quick test, run:
 ```sh
 curl -v https://region1.v2.argotunnel.com:7844
 ```
+
 If the connection hangs, traffic is being dropped between your host and Cloudflare.
 
 To test if `cloudflared` can connect on port `7844`, run:
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
index 51b265f76e5f1f0..b2a3eaa4e14958f 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
@@ -7,7 +7,6 @@ products:
 sidebar:
   order: 4
   label: Any Hostname
-
 ---
 
 The Any Hostname feature removes the requirement to specify hostnames during widget creation, allowing widgets to function on any domain.
@@ -24,31 +23,37 @@ When using the Any Hostname feature, it is essential to implement additional val
 
 ```js title="Example response"
 async function validateTurnstileWithHostname(token, expectedHostnames = []) {
-  const response = await fetch('https://challenges.cloudflare.com/turnstile/v0/siteverify', {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/json' },
-    body: JSON.stringify({
-      secret: process.env.TURNSTILE_SECRET,
-      response: token
-    })
-  });
-
-  const result = await response.json();
-
-  if (!result.success) {
-    return { valid: false, error: 'Token validation failed' };
-  }
-
-  // Additional hostname validation when using Any Hostname
-  if (expectedHostnames.length > 0 && !expectedHostnames.includes(result.hostname)) {
-    return { 
-      valid: false, 
-      error: 'Hostname not in allowed list',
-      hostname: result.hostname 
-    };
-  }
-
-  return { valid: true, data: result };
+	const response = await fetch(
+		"https://challenges.cloudflare.com/turnstile/v0/siteverify",
+		{
+			method: "POST",
+			headers: { "Content-Type": "application/json" },
+			body: JSON.stringify({
+				secret: process.env.TURNSTILE_SECRET,
+				response: token,
+			}),
+		},
+	);
+
+	const result = await response.json();
+
+	if (!result.success) {
+		return { valid: false, error: "Token validation failed" };
+	}
+
+	// Additional hostname validation when using Any Hostname
+	if (
+		expectedHostnames.length > 0 &&
+		!expectedHostnames.includes(result.hostname)
+	) {
+		return {
+			valid: false,
+			error: "Hostname not in allowed list",
+			hostname: result.hostname,
+		};
+	}
+
+	return { valid: true, data: result };
 }
 ```
 
@@ -58,10 +63,12 @@ Use `action` and `cData` parameters to track widget usage sources.
 
 ```html
 <!-- Widget with tracking information -->
-<div class="cf-turnstile" 
-     data-sitekey="your-site-key"
-     data-action="customer-portal"
-     data-cdata="tenant-123"></div>
+<div
+	class="cf-turnstile"
+	data-sitekey="your-site-key"
+	data-action="customer-portal"
+	data-cdata="tenant-123"
+></div>
 ```
 
 ---
@@ -73,4 +80,4 @@ The Any Hostname feature is particularly valuable for customers with:
 - Large domain portfolios with many domains to manage individually.
 - Dynamic subdomain creation and frequently create subdomains or customer-specific domains.
 - Multi-tenant applications such as SaaS platforms serving multiple customer domains.
-- Development environments that test across various staging and development domains.
\ No newline at end of file
+- Development environments that test across various staging and development domains.
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
index 2ec95bf7163dc6f..a54d5062f8d33e7 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
@@ -6,10 +6,9 @@ products:
   - turnstile
 sidebar:
   order: 2
-
 ---
 
-import { DashButton, Steps, Tabs, TabItem, Details } from "~/components"
+import { DashButton, Steps, Tabs, TabItem, Details } from "~/components";
 
 Hostname management controls where your Turnstile widgets can be used by specifying which domains are authorized to load and execute your widgets. This security measure prevents unauthorized use of your widgets on domains that you do not control.
 
@@ -36,7 +35,7 @@ The following formats are not valid and will not be accepted:
 - Schemes such as `http://example.com` or `https://example.com`
 - Ports such as `example.com:443` or `subdomain.example.com:8080`
 - Paths such as `example.com/path` or `subdomain.example.com/login`
-:::
+  :::
 
 ### Subdomain behavior
 
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
index eaa623056629f2a..c8b59dade309ca5 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
@@ -8,7 +8,6 @@ tags:
   - Cookies
 sidebar:
   order: 3
-
 ---
 
 [Pre-clearance](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) allows Turnstile to issue clearance cookies that can be used across your Cloudflare-protected domains. This feature requires specific hostname configuration for proper functionality.
@@ -17,18 +16,18 @@ sidebar:
 
 For pre-clearance to work correctly, you must:
 
-1. Use a registered Cloudflare zone. 
+1. Use a registered Cloudflare zone.
+
+   The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones.
+
+2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance.
 
-    The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones. 
+   The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile.
 
-2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance. 
-    
-    The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile. 
-    
-    For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`. 
+   For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`.
 
 ## Validation
 
 The clearance cookie `cf_clearance` will only be accepted on domains that match the widget's configured hostnames, are registered as zones in your Cloudflare account, and have challenges enabled through Cloudflare's security settings.
 
-If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
\ No newline at end of file
+If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
diff --git a/src/content/docs/turnstile/additional-configuration/index.mdx b/src/content/docs/turnstile/additional-configuration/index.mdx
index fa53423d1ca145e..c1dd255c43c229e 100644
--- a/src/content/docs/turnstile/additional-configuration/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile's additional configurations:
 
diff --git a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
index f4882feb0c77f50..ff23f12fc0c683d 100644
--- a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
+++ b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile
 sidebar:
   order: 3
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/turnstile/concepts/challenges.mdx b/src/content/docs/turnstile/concepts/challenges.mdx
index fa67c9f121a081a..2049cf0d9334a17 100644
--- a/src/content/docs/turnstile/concepts/challenges.mdx
+++ b/src/content/docs/turnstile/concepts/challenges.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /cloudflare-challenges/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/turnstile/concepts/index.mdx b/src/content/docs/turnstile/concepts/index.mdx
index 4545231c8047916..f8bdd001acb61db 100644
--- a/src/content/docs/turnstile/concepts/index.mdx
+++ b/src/content/docs/turnstile/concepts/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile's concepts:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/extensions/google-firebase.mdx b/src/content/docs/turnstile/extensions/google-firebase.mdx
index 2456c9d7c189b62..7ecd2d24ede91af 100644
--- a/src/content/docs/turnstile/extensions/google-firebase.mdx
+++ b/src/content/docs/turnstile/extensions/google-firebase.mdx
@@ -10,10 +10,9 @@ tags:
 sidebar:
   order: 2
   label: Google Firebase
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 Turnstile is [available as an extension](https://extensions.dev/extensions/cloudflare/cloudflare-turnstile-app-check-provider) with [Google's Firebase](https://firebase.google.com/) platform as an [App Check](https://firebase.google.com/docs/app-check) provider. You can leverage Cloudflare Turnstile's bot detection and challenge capabilities to ensure that requests to your Firebase backend services are verified and only authentic human visitors can interact with your application.
 
@@ -119,25 +118,25 @@ const expressApp = express();
 const firebaseApp = initializeApp();
 
 const appCheckVerification = async (req, res, next) => {
-    const appCheckToken = req.header("X-Firebase-AppCheck");
+	const appCheckToken = req.header("X-Firebase-AppCheck");
 
-    if (!appCheckToken) {
-        res.status(401);
-        return next("Unauthorized");
-    }
+	if (!appCheckToken) {
+		res.status(401);
+		return next("Unauthorized");
+	}
 
-    try {
-        const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
+	try {
+		const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
 
-        // If verifyToken() succeeds, continue with the next middleware function in the stack.
-        return next();
-    } catch (err) {
-        res.status(401);
-        return next("Unauthorized");
-    }
-}
+		// If verifyToken() succeeds, continue with the next middleware function in the stack.
+		return next();
+	} catch (err) {
+		res.status(401);
+		return next("Unauthorized");
+	}
+};
 
 expressApp.get("/yourApiEndpoint", [appCheckVerification], (req, res) => {
-    // Handle request.
+	// Handle request.
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/extensions/index.mdx b/src/content/docs/turnstile/extensions/index.mdx
index 2649807908e1165..e7d4e7afeae3a2f 100644
--- a/src/content/docs/turnstile/extensions/index.mdx
+++ b/src/content/docs/turnstile/extensions/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile extensions:
 
diff --git a/src/content/docs/turnstile/extensions/pages-plugin.mdx b/src/content/docs/turnstile/extensions/pages-plugin.mdx
index e3a41748a59f3ca..963a6bb4dee2004 100644
--- a/src/content/docs/turnstile/extensions/pages-plugin.mdx
+++ b/src/content/docs/turnstile/extensions/pages-plugin.mdx
@@ -7,5 +7,4 @@ title: Pages Plugin
 external_link: /pages/functions/plugins/turnstile/
 sidebar:
   order: 1
-
 ---
diff --git a/src/content/docs/turnstile/extensions/waiting-room.mdx b/src/content/docs/turnstile/extensions/waiting-room.mdx
index 474416b1df638c3..1153676741e4dc1 100644
--- a/src/content/docs/turnstile/extensions/waiting-room.mdx
+++ b/src/content/docs/turnstile/extensions/waiting-room.mdx
@@ -7,5 +7,4 @@ title: Waiting Room Analytics
 external_link: /waiting-room/waiting-room-analytics/#turnstile-widget-traffic
 sidebar:
   order: 3
-
 ---
diff --git a/src/content/docs/turnstile/get-started/widget-management/api.mdx b/src/content/docs/turnstile/get-started/widget-management/api.mdx
index 4342df29d7ee58e..9c0738b7d0d5cda 100644
--- a/src/content/docs/turnstile/get-started/widget-management/api.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/api.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - REST API
 sidebar:
-    order: 2
-    label: API
+  order: 2
+  label: API
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Use the [Cloudflare API](/api/resources/turnstile/) for programmatic widget management and automation.
 
@@ -25,47 +25,44 @@ Before you begin, you must have:
 ### Create a widget via the API
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets"
-  method="POST"
-  json={{
-    domains: ["example.com"],
-    mode: "managed",
-    name: "My Example Turnstile Widget",
-  }}
+	path="/accounts/{account_id}/challenges/widgets"
+	method="POST"
+	json={{
+		domains: ["example.com"],
+		mode: "managed",
+		name: "My Example Turnstile Widget",
+	}}
 />
 
 ### Manage widgets via the API
 
-<APIRequest
-  path="/accounts/{account_id}/challenges/widgets"
-  method="GET"
-/>
+<APIRequest path="/accounts/{account_id}/challenges/widgets" method="GET" />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="GET"
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="GET"
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="PUT"
-  json={{
-    domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
-    mode: "invisible",
-    name: "blog.cloudflare.com login form",
-    clearance_level: "interactive",
-  }}
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="PUT"
+	json={{
+		domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
+		mode: "invisible",
+		name: "blog.cloudflare.com login form",
+		clearance_level: "interactive",
+	}}
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
-  method="POST"
-  json={{
-    invalidate_immediately: false,
-  }}
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
+	method="POST"
+	json={{
+		invalidate_immediately: false,
+	}}
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="DELETE"
-/>
\ No newline at end of file
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="DELETE"
+/>
diff --git a/src/content/docs/turnstile/get-started/widget-management/index.mdx b/src/content/docs/turnstile/get-started/widget-management/index.mdx
index bcb9b3c62a9e45f..70a4816c948455b 100644
--- a/src/content/docs/turnstile/get-started/widget-management/index.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about managing Turnstile widgets:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
index d39317f90ca363c..22a01e0fa0389de 100644
--- a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - Terraform
 sidebar:
-    order: 3
-    label: Terraform
+  order: 3
+  label: Terraform
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Manage Turnstile widgets as code using Terraform for version control and automated deployments.
 
@@ -153,7 +153,7 @@ locals {
 
 resource "cloudflare_turnstile_widget" "app_widget" {
   for_each = local.environments
-  
+
   account_id = var.account_id
   name       = "App Widget - ${each.key}"
   domains    = each.value.domains
@@ -195,4 +195,4 @@ cf-terraforming generate \
 ```shell title="Import existing widget"
 terraform import cloudflare_turnstile_widget.existing_widget \
   $ACCOUNT_ID/$WIDGET_SITEKEY
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/migration/hcaptcha.mdx b/src/content/docs/turnstile/migration/hcaptcha.mdx
index 87ff8fe69db29c4..bbe32fd8f917c8d 100644
--- a/src/content/docs/turnstile/migration/hcaptcha.mdx
+++ b/src/content/docs/turnstile/migration/hcaptcha.mdx
@@ -46,7 +46,7 @@ Turnstile supports:
 
 - the `render()` call
 - hCaptcha invisible mode with the `execute()` call
-:::
+  :::
 
 ## Server-side integration
 
diff --git a/src/content/docs/turnstile/reference/index.mdx b/src/content/docs/turnstile/reference/index.mdx
index ed8c7d7668f0cc2..0f952082dda1ea1 100644
--- a/src/content/docs/turnstile/reference/index.mdx
+++ b/src/content/docs/turnstile/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile:
 
diff --git a/src/content/docs/turnstile/reference/supported-browsers.mdx b/src/content/docs/turnstile/reference/supported-browsers.mdx
index 28bdb4eb396bfad..837dbda385d3c26 100644
--- a/src/content/docs/turnstile/reference/supported-browsers.mdx
+++ b/src/content/docs/turnstile/reference/supported-browsers.mdx
@@ -7,5 +7,4 @@ title: Supported browsers
 external_link: /cloudflare-challenges/reference/supported-browsers/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/turnstile/reference/supported-languages.mdx b/src/content/docs/turnstile/reference/supported-languages.mdx
index f0338658d106a98..8263d260812b2fd 100644
--- a/src/content/docs/turnstile/reference/supported-languages.mdx
+++ b/src/content/docs/turnstile/reference/supported-languages.mdx
@@ -8,7 +8,6 @@ tags:
   - Localization
 sidebar:
   order: 3
-
 ---
 
 Turnstile supports `auto` (default), which uses the visitor's browser language if it is supported. You can also explicitly set the widget's language using the [client-side configuration attribute](/turnstile/get-started/client-side-rendering/#configurations) to one listed on the table below:
diff --git a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
index 12e1785bd51cc86..8b37a576667565e 100644
--- a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
+++ b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
@@ -7,5 +7,4 @@ title: Turnstile Privacy Addendum
 external_link: https://www.cloudflare.com/turnstile-privacy-policy/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
index 6a51837058ce17d..b38f8de49356b2c 100644
--- a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
@@ -7,5 +7,4 @@ title: Challenge solve issues
 external_link: /cloudflare-challenges/troubleshooting/challenge-solve-issues/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
index fd6c9090b063095..e0c9bc9938840cc 100644
--- a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
@@ -9,22 +9,21 @@ tags:
   - JavaScript
 sidebar:
   order: 3
-
 ---
 
 import { Tabs, TabItem } from "~/components";
 
-There are instances where Turnstile may encounter problems, invoking the `error-callback`. 
+There are instances where Turnstile may encounter problems, invoking the `error-callback`.
 
-These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures. 
+These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures.
 
-When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues. 
+When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues.
 
 Refer to the [Error codes](/turnstile/troubleshooting/client-side-errors/error-codes/) for troubleshooting guidance to address specific error conditions.
 
 ## Error handling
 
-The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur. 
+The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur.
 
 This callback mechanism gives you complete control over how errors are presented to visitors and allows you to implement custom recovery strategies tailored to your application's needs.
 
@@ -58,28 +57,30 @@ An error callback will retrieve an error code as its first parameter. This error
 
 ```js wrap
 function handleTurnstileError(errorCode) {
-  const errorFamily = Math.floor(errorCode / 1000);
-  
-  switch(errorFamily) {
-    case 100:
-      showMessage('Please refresh the page and try again.');
-      break;
-    case 110:
-      showMessage('Configuration error. Please contact support.');
-      break;
-    case 300:
-    case 600:
-      showMessage('Security check failed. Please try refreshing or using a different browser.');
-      break;
-    default:
-      showMessage('An unexpected error occurred. Please try again.');
-  }
+	const errorFamily = Math.floor(errorCode / 1000);
+
+	switch (errorFamily) {
+		case 100:
+			showMessage("Please refresh the page and try again.");
+			break;
+		case 110:
+			showMessage("Configuration error. Please contact support.");
+			break;
+		case 300:
+		case 600:
+			showMessage(
+				"Security check failed. Please try refreshing or using a different browser.",
+			);
+			break;
+		default:
+			showMessage("An unexpected error occurred. Please try again.");
+	}
 }
 ```
 
 ## Retry
 
-By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention. 
+By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention.
 
 This automatic retry mechanism is useful for [mobile visitors](/turnstile/get-started/mobile-implementation/) who may experience intermittent connectivity or visitors on networks with occasional stability issues.
 
@@ -88,34 +89,34 @@ When subsequent failures due to retries are observed, the error callback can be
 ```js wrap
 let retryCount = 0;
 
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  'error-callback': function(errorCode) {
-    retryCount++;
-    
-    if (retryCount <= 2) {
-      console.log(`Turnstile retry attempt ${retryCount}`);
-      return false; // Let Turnstile handle the retry
-    } else {
-      showPersistentErrorMessage(errorCode);
-      return true; // We'll handle it from here
-    }
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	"error-callback": function (errorCode) {
+		retryCount++;
+
+		if (retryCount <= 2) {
+			console.log(`Turnstile retry attempt ${retryCount}`);
+			return false; // Let Turnstile handle the retry
+		} else {
+			showPersistentErrorMessage(errorCode);
+			return true; // We'll handle it from here
+		}
+	},
 });
 ```
 
 You can adjust the retry behavior by setting the retry value to `never` instead of the default `auto`. This will result in Turnstile not automatically retrying, giving you control over when and how recovery attempts are made. If there is any issue or error verifying the visitor, the widget will not retry and will remain in the respective failure state until you take manual action.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  retry: 'never',
-  'error-callback': function(errorCode) {
-    // You control all retry logic
-    setTimeout(() => {
-      turnstile.reset('#my-widget');
-    }, 3000);
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	retry: "never",
+	"error-callback": function (errorCode) {
+		// You control all retry logic
+		setTimeout(() => {
+			turnstile.reset("#my-widget");
+		}, 3000);
+	},
 });
 ```
 
@@ -124,11 +125,11 @@ You may call `turnstile.reset()` in the corresponding `error-callback` to manual
 The interval between retries for Turnstile can be configured by the `retry-interval` option, allowing you to optimize retry timing for your visitors’ typical network conditions. A longer interval may be more appropriate for visitors on slower or less reliable connections, while shorter intervals work well in environments with typically stable connectivity.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  retry: 'auto',
-  'retry-interval': 8000, // Wait 8 seconds between retries
-  'error-callback': handleError
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	retry: "auto",
+	"retry-interval": 8000, // Wait 8 seconds between retries
+	"error-callback": handleError,
 });
 ```
 
@@ -141,23 +142,23 @@ For instance, in a scenario where the Turnstile widget is implemented within a f
 In such instances, the `timeout-callback` of the widget is activated, enabling the widget to reset itself as needed and provide appropriate guidance. This callback allows you to implement user-friendly timeout handling, such as highlighting the Turnstile widget, displaying a notification, or automatically refreshing the challenge.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  callback: function(token) {
-    console.log('Challenge completed successfully');
-  },
-  'timeout-callback': function() {
-    console.log('Challenge timed out - user action required');
-    document.getElementById('challenge-notice').textContent = 
-      'Please complete the security check above to continue.';
-    
-    // Optionally highlight the widget
-    document.getElementById('my-widget').style.border = '2px solid orange';
-  },
-  'expired-callback': function() {
-    console.log('Token expired - challenge needs refresh');
-    document.getElementById('challenge-notice').textContent = 
-      'Security check expired. Please try again.';
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	callback: function (token) {
+		console.log("Challenge completed successfully");
+	},
+	"timeout-callback": function () {
+		console.log("Challenge timed out - user action required");
+		document.getElementById("challenge-notice").textContent =
+			"Please complete the security check above to continue.";
+
+		// Optionally highlight the widget
+		document.getElementById("my-widget").style.border = "2px solid orange";
+	},
+	"expired-callback": function () {
+		console.log("Token expired - challenge needs refresh");
+		document.getElementById("challenge-notice").textContent =
+			"Security check expired. Please try again.";
+	},
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/troubleshooting/index.mdx b/src/content/docs/turnstile/troubleshooting/index.mdx
index 9732a59701eb192..62155e4b61f1542 100644
--- a/src/content/docs/turnstile/troubleshooting/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 8
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about troubleshooting Turnstile:
 
diff --git a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
index 50d1cebeb5a11e6..ce67d78a5431377 100644
--- a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
+++ b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
@@ -6,10 +6,9 @@ products:
   - turnstile
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip, DashButton, Steps } from "~/components"
+import { GlossaryTooltip, DashButton, Steps } from "~/components";
 
 You can rotate the <GlossaryTooltip term="secret key">secret key</GlossaryTooltip> using the following steps:
 
diff --git a/src/content/docs/turnstile/troubleshooting/testing.mdx b/src/content/docs/turnstile/troubleshooting/testing.mdx
index 32e507a1005bb68..41f98655c15fd16 100644
--- a/src/content/docs/turnstile/troubleshooting/testing.mdx
+++ b/src/content/docs/turnstile/troubleshooting/testing.mdx
@@ -9,10 +9,9 @@ tags:
 sidebar:
   order: 1
   label: Testing
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Use dummy sitekeys and secret keys to test your Turnstile implementation without triggering real challenges that would interfere with automated testing suites.
 
@@ -27,23 +26,23 @@ Dummy keys solve this by providing predictable, controlled responses that work w
 
 ## Test sitekeys
 
-| Sitekey | Behavior | Widget Type | Use case |
-| ------- | -------- | ----------- | -------- |
-| `1x00000000000000000000AA` | Always passes | Visible | Test successful form submissions |
-| `2x00000000000000000000AB` | Always fails | Visible | Test error handling and retry logic |
-| `1x00000000000000000000BB` | Always passes | Invisible | Test invisible widget success flows |
-| `2x00000000000000000000BB` | Always fails | Invisible | Test invisible widget error handling |
-| `3x00000000000000000000FF` | Forces interactive challenge | Visible | Test user interaction scenarios |
+| Sitekey                    | Behavior                     | Widget Type | Use case                             |
+| -------------------------- | ---------------------------- | ----------- | ------------------------------------ |
+| `1x00000000000000000000AA` | Always passes                | Visible     | Test successful form submissions     |
+| `2x00000000000000000000AB` | Always fails                 | Visible     | Test error handling and retry logic  |
+| `1x00000000000000000000BB` | Always passes                | Invisible   | Test invisible widget success flows  |
+| `2x00000000000000000000BB` | Always fails                 | Invisible   | Test invisible widget error handling |
+| `3x00000000000000000000FF` | Forces interactive challenge | Visible     | Test user interaction scenarios      |
 
 ## Test secret keys
 
 Use these secret keys for server-side validation testing:
 
-| Secret key | Behavior | Use case |
-| ---------- | -------- | -------- |
-| `1x0000000000000000000000000000000AA` | Always passes validation | Test successful token validation |
-| `2x0000000000000000000000000000000AA` | Always fails validation | Test validation error handling |
-| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling |
+| Secret key                            | Behavior                            | Use case                         |
+| ------------------------------------- | ----------------------------------- | -------------------------------- |
+| `1x0000000000000000000000000000000AA` | Always passes validation            | Test successful token validation |
+| `2x0000000000000000000000000000000AA` | Always fails validation             | Test validation error handling   |
+| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling    |
 
 ---
 
@@ -78,9 +77,10 @@ Replace your production secret key with a test secret key.
 
 ```js
 // Environment-based configuration
-const SECRET_KEY = process.env.NODE_ENV === 'production' 
-  ? process.env.TURNSTILE_SECRET_KEY 
-  : '1x0000000000000000000000000000000AA';
+const SECRET_KEY =
+	process.env.NODE_ENV === "production"
+		? process.env.TURNSTILE_SECRET_KEY
+		: "1x0000000000000000000000000000000AA";
 
 // Use in validation
 const validation = await validateTurnstile(token, SECRET_KEY);
@@ -96,7 +96,7 @@ Set up different keys for different environments.
 TURNSTILE_SITEKEY=1x00000000000000000000AA
 TURNSTILE_SECRET_KEY=1x0000000000000000000000000000000AA
 
-# .env.test  
+# .env.test
 TURNSTILE_SITEKEY=2x00000000000000000000AB
 TURNSTILE_SECRET_KEY=2x0000000000000000000000000000000AA
 
@@ -126,27 +126,26 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ```json title="Success response"
 {
-  "success": true,
-  "challenge_ts": "2022-02-28T15:14:30.096Z",
-  "hostname": "localhost",
-  "error-codes": [],
-  "action": "test",
-  "cdata": "test-data"
+	"success": true,
+	"challenge_ts": "2022-02-28T15:14:30.096Z",
+	"hostname": "localhost",
+	"error-codes": [],
+	"action": "test",
+	"cdata": "test-data"
 }
 ```
 
 ```json title="Failure response"
 {
-  "success": false,
-  "error-codes": ["invalid-input-response"]
+	"success": false,
+	"error-codes": ["invalid-input-response"]
 }
-
 ```
 
 ```json title="Token already redeemed"
 {
-  "success": false,
-  "error-codes": ["timeout-or-duplicate"]
+	"success": false,
+	"error-codes": ["timeout-or-duplicate"]
 }
 ```
 
@@ -154,8 +153,8 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ## Testing scenarios
 
-| Test sitekey | Test secret key | <div style="width:200px">Test case</div> |
-| ------------ | --------------- | --------- |
-| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation. |
-| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail. |
-| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
\ No newline at end of file
+| Test sitekey               | Test secret key                       | <div style="width:200px">Test case</div>                             |
+| -------------------------- | ------------------------------------- | -------------------------------------------------------------------- |
+| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation.        |
+| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail.                                   |
+| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
diff --git a/src/content/docs/turnstile/turnstile-analytics/index.mdx b/src/content/docs/turnstile/turnstile-analytics/index.mdx
index b580a70e9a92a88..1ad2a0c6a7bcde0 100644
--- a/src/content/docs/turnstile/turnstile-analytics/index.mdx
+++ b/src/content/docs/turnstile/turnstile-analytics/index.mdx
@@ -9,10 +9,9 @@ sidebar:
   order: 5
 description: Use Turnstile Analytics to view the number of challenges issued,
   the challenge solve rate, and the metrics of issued challenges.
-
 ---
 
-import { Render, DirectoryListing, DashButton } from "~/components"
+import { Render, DirectoryListing, DashButton } from "~/components";
 
 Turnstile Analytics shows widget statistics across traffic dimensions like hostname, country, browser, and IP address. Use these metrics to identify where challenge activity is highest and whether specific sources are failing or bypassing challenges.
 
@@ -38,4 +37,4 @@ The metrics show changes in the solve rate, widget traffic, and top actions for
 
 Refer to the pages below for more information about Turnstile Analytics:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
index 6a6c10bc60370a8..a4a5ca21b6e199c 100644
--- a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
+++ b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
@@ -28,10 +28,11 @@ For more details, refer to the [testing documentation](/turnstile/troubleshootin
 :::caution
 
 Never use test credentials in production. Always ensure:
+
 - Test credentials are only used in test environments.
 - Production credentials are properly protected.
 - Your deployment process prevents test credentials from reaching production.
-:::
+  :::
 
 ## Implementation
 
@@ -40,26 +41,27 @@ The key to implementing test-environment detection is identifying test requests
 ```typescript
 // Detect test environments using IP addresses or headers
 function isTestEnvironment(request) {
-  const testIPs = ['127.0.0.1', '::1'];
-  const isTestIP = testIPs.includes(request.ip);
-  const hasTestHeader = request.headers['x-test-environment'] === 'secret-token';
+	const testIPs = ["127.0.0.1", "::1"];
+	const isTestIP = testIPs.includes(request.ip);
+	const hasTestHeader =
+		request.headers["x-test-environment"] === "secret-token";
 
-  return isTestIP || hasTestHeader;
+	return isTestIP || hasTestHeader;
 }
 
 // Use the appropriate credentials based on the environment
 function getTurnstileCredentials(request) {
-  if (isTestEnvironment(request)) {
-    return {
-      sitekey: '1x00000000000000000000AA',
-      secretKey: '1x0000000000000000000000000000000AA'
-    };
-  }
-
-  return {
-    sitekey: process.env.TURNSTILE_SITE_KEY,
-    secretKey: process.env.TURNSTILE_SECRET_KEY
-  };
+	if (isTestEnvironment(request)) {
+		return {
+			sitekey: "1x00000000000000000000AA",
+			secretKey: "1x0000000000000000000000000000000AA",
+		};
+	}
+
+	return {
+		sitekey: process.env.TURNSTILE_SITE_KEY,
+		secretKey: process.env.TURNSTILE_SECRET_KEY,
+	};
 }
 ```
 
@@ -68,9 +70,9 @@ function getTurnstileCredentials(request) {
 When rendering your page, inject the appropriate sitekey based on the environment:
 
 ```typescript
-app.get('/your-form', (req, res) => {
-  const { sitekey } = getTurnstileCredentials(req);
-  res.render('form', { sitekey });
+app.get("/your-form", (req, res) => {
+	const { sitekey } = getTurnstileCredentials(req);
+	res.render("form", { sitekey });
 });
 ```
 
@@ -112,16 +114,16 @@ For Cypress or similar E2E testing frameworks:
 ```typescript
 // Set test header for all test requests
 beforeEach(() => {
-  cy.intercept('*', (req) => {
-    req.headers['x-test-environment'] = 'secret-token';
-  });
+	cy.intercept("*", (req) => {
+		req.headers["x-test-environment"] = "secret-token";
+	});
 });
 
 // Your test can now interact with the form normally
-it('submits form successfully', () => {
-  cy.visit('/your-form');
-  cy.get('form').submit();
-  // Turnstile will automatically pass verification
+it("submits form successfully", () => {
+	cy.visit("/your-form");
+	cy.get("form").submit();
+	// Turnstile will automatically pass verification
 });
 ```
 
diff --git a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
index cd516941cbdc5e1..865dade6b1b9bde 100644
--- a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
+++ b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
@@ -27,7 +27,7 @@ Traditional IP-based detection fails because each request appears to come from a
 - You must have basic familiarity with Turnstile integration. Refer to [Get started with Turnstile](/turnstile/get-started/) for more information.
 
 :::caution[Ephemeral IDs are not guaranteed to be unique]
-Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID. 
+Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID.
 
 Use Ephemeral IDs to detect high-volume abuse patterns, not to uniquely identify individual devices. Always set detection thresholds high enough to avoid false positives.
 :::
@@ -241,4 +241,4 @@ Ephemeral IDs are privacy-preserving. They are scoped to your account, short-liv
 
 - [Ephemeral IDs](/turnstile/additional-configuration/ephemeral-id/)
 - [Server-side validation](/turnstile/get-started/server-side-validation/)
-- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
\ No newline at end of file
+- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
diff --git a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
index c7a73ce8527faa1..ebc66f19cfe4972 100644
--- a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
+++ b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
@@ -85,7 +85,13 @@ Add the Turnstile widget to your existing login form:
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
+	<input
+		type="password"
+		id="password"
+		placeholder="Password"
+		autocomplete="off"
+		required
+	/>
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
diff --git a/src/content/docs/use-cases/e-commerce/performance.mdx b/src/content/docs/use-cases/e-commerce/performance.mdx
index 7c7d4fc51d1f3db..82a7e010f0ab221 100644
--- a/src/content/docs/use-cases/e-commerce/performance.mdx
+++ b/src/content/docs/use-cases/e-commerce/performance.mdx
@@ -51,4 +51,4 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 2. [Set up Cloudflare Images](/images/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
 4. [Configure Zaraz](/zaraz/get-started/)
-5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
+5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
diff --git a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
index 9a2ebfe22516874..a073c15a2066185 100644
--- a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
+++ b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
@@ -11,21 +11,29 @@ sidebar:
 
 import { DashButton, Render, Steps, TabItem, Tabs } from "~/components";
 
-HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages: 
+HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages:
 
 1. Configure your SSL/TLS encryption mode.
 2. Redirect all HTTP requests to HTTPS.
 3. Harden your HTTPS setup with minimum TLS versions and HSTS.
 4. Monitor third-party scripts on your pages.
-5. Verify your configuration. 
+5. Verify your configuration.
 
 The core workflow is available on Free, Pro, and Business plans.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Client-Side Security is the exception: it is configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Client-Side Security is the exception: it is configured at the account level.",
+	}}
+/>
 
 ## Configure your SSL/TLS encryption mode
 
 Your SSL/TLS encryption mode controls how Cloudflare connects to your origin server. For end-to-end encryption, use **Full (strict)** — it encrypts both connections and verifies your origin certificate. For a detailed comparison of all available modes, refer to [Encryption modes](/ssl/origin-configuration/ssl-modes/).
+
 ### Check your current mode
 
 <Steps>
@@ -75,6 +83,7 @@ If your origin already has a valid certificate from a publicly trusted certifica
 9. Select **OK**.
 
 </Steps>
+
 :::note
 For details about working with certificates programmatically, refer to [API calls](/ssl/origin-configuration/origin-ca/#api-calls).
 :::
@@ -92,6 +101,7 @@ For details about working with certificates programmatically, refer to [API call
 4. Enable SSL and port `443` at your origin web server.
 
 </Steps>
+
 :::note
 If you do not see your server listed, search the [DigiCert documentation](https://www.digicert.com/search-results) or contact your hosting provider.
 :::
@@ -109,13 +119,15 @@ After installing a valid certificate on your origin server, set the encryption m
 <Render file="change-encryption-mode-api" product="ssl" />
 
 </TabItem> </Tabs>
+
 :::caution
 If your site shows a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) after changing the encryption mode, your origin certificate may not meet the requirements for Full (strict). The certificate must be unexpired, issued by a trusted CA or Cloudflare Origin CA, and contain a Common Name (CN) or Subject Alternative Name (SAN) that matches your hostname. For redirect loop issues, refer to [ERR_TOO_MANY_REDIRECTS](/ssl/troubleshooting/too-many-redirects/).
 :::
 
 ## Redirect all HTTP requests to HTTPS
 
-Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this: 
+Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this:
+
 1. Always Use HTTPS redirects HTTP requests to HTTPS
 2. Automatic HTTPS Rewrites fixes mixed content references in your page HTML
 
@@ -154,6 +166,7 @@ If only some parts of your application can support HTTPS traffic, do not turn on
 </Steps>
 
 </TabItem> </Tabs>
+
 ### Turn on Automatic HTTPS Rewrites
 
 Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resource URLs in your page HTML to HTTPS. This is useful for sites where you do not control all asset URLs, such as CMS-hosted content or embedded third-party resources.
@@ -175,6 +188,7 @@ Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resourc
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `automatic_https_rewrites` as the setting name in the URI path, and the `value` parameter set to `"on"`.
 
 </TabItem> </Tabs>
+
 :::note
 Automatic HTTPS Rewrites does not rewrite all HTTP URLs. Some passive content (such as images) may not be rewritten, which can still cause mixed content warnings. For details on how rewrites work and troubleshooting, refer to [Automatic HTTPS Rewrites](/ssl/edge-certificates/additional-options/automatic-https-rewrites/) and [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/).
 :::
@@ -204,6 +218,7 @@ TLS 1.0 and 1.1 have known vulnerabilities and are no longer considered secure.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `min_tls_version` as the setting name in the URI path, and the `value` parameter set to `"1.2"`.
 
 </TabItem> </Tabs>
+
 :::note[Per-hostname minimum TLS version requires Advanced Certificate Manager]
 To set minimum TLS versions for individual hostnames instead of the entire zone, refer to [Per-hostname setup](/ssl/edge-certificates/additional-options/minimum-tls/#per-hostname). This requires an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription.
 :::
@@ -229,6 +244,7 @@ TLS 1.3 provides faster handshakes and improved security over TLS 1.2.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `tls_1_3` as the setting name in the URI path, and the `value` parameter set to `"on"`. To also turn on 0-RTT (Zero Round Trip Time Resumption), set the value to `"zrt"`.
 
 </TabItem> </Tabs>
+
 ### Turn on HSTS
 
 HTTP Strict Transport Security (HSTS) adds a response header that tells browsers to connect to your site over HTTPS only, even if a link or redirect tries to send them over HTTP. HSTS protects against protocol downgrade attacks.
@@ -272,6 +288,7 @@ Before turning on HSTS, confirm these prerequisites:
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `security_header` as the setting name in the URI path, and specify the `value` object that includes your HSTS settings.
 
 </TabItem> </Tabs>
+
 ### Review your cipher suites
 
 Cloudflare's default cipher suites provide strong encryption for most sites. You do not need to change them unless a security audit or compliance requirement specifies particular cipher configurations.
@@ -299,6 +316,7 @@ HTTPS encrypts data in transit, but third-party scripts loaded by your pages can
 3. Turn on **Continuous script monitoring**.
 
 </Steps>
+
 ### Review detected resources
 
 After turning on monitoring, it may take some time for Cloudflare to generate a list of detected scripts on your domain.
@@ -314,6 +332,7 @@ After turning on monitoring, it may take some time for Cloudflare to generate a
 3. Review the list of detected scripts. Check for unknown or unexpected scripts from domains you do not recognize.
 
 </Steps>
+
 Depending on your Cloudflare plan, you may also be able to review connections made by scripts and check them for malicious activity. For setup details, refer to [Get started with client-side security](/client-side-security/get-started/).
 
 :::note[Content security rules require Client-Side Security Advanced]
diff --git a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
index 4cfed58dfe9b42a..0e5abbc0284d7c9 100644
--- a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
+++ b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
@@ -15,7 +15,14 @@ import { Render, Steps, DashButton } from "~/components";
 
 Contact, registration, and checkout forms are common targets for automated abuse. This guide covers form protection: verifying that visitors are human, limiting repeated submissions, and blocking known attack patterns. The core workflow uses features available on all plans. Pro and Business plan features are included as callouts.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Add Turnstile to your forms
 
@@ -35,14 +42,18 @@ Add the Turnstile script and widget `div` element to each form you want to prote
 
 ```html
 <form id="contact-form" action="/submit" method="POST">
-  <input type="text" name="name" placeholder="Name" required />
-  <input type="email" name="email" placeholder="Email" required />
-  <textarea name="message" placeholder="Message" required></textarea>
-  <div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
-  <button type="submit">Submit</button>
+	<input type="text" name="name" placeholder="Name" required />
+	<input type="email" name="email" placeholder="Email" required />
+	<textarea name="message" placeholder="Message" required></textarea>
+	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
+	<button type="submit">Submit</button>
 </form>
 
-<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
+<script
+	src="https://challenges.cloudflare.com/turnstile/v0/api.js"
+	async
+	defer
+></script>
 ```
 
 The widget renders in the form and generates a token when the visitor passes verification. The token is included in the form submission as the `cf-turnstile-response` field.
@@ -57,26 +68,26 @@ Call the Siteverify API before processing any form submission:
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
 async function validateTurnstile(token, remoteip) {
-  try {
-    const response = await fetch(
-      "https://challenges.cloudflare.com/turnstile/v0/siteverify",
-      {
-        method: "POST",
-        headers: { "Content-Type": "application/json" },
-        body: JSON.stringify({
-          secret: SECRET_KEY,
-          response: token,
-          remoteip: remoteip,
-        }),
-      },
-    );
-
-    const result = await response.json();
-    return result;
-  } catch (error) {
-    console.error("Turnstile validation error:", error);
-    return { success: false, "error-codes": ["internal-error"] };
-  }
+	try {
+		const response = await fetch(
+			"https://challenges.cloudflare.com/turnstile/v0/siteverify",
+			{
+				method: "POST",
+				headers: { "Content-Type": "application/json" },
+				body: JSON.stringify({
+					secret: SECRET_KEY,
+					response: token,
+					remoteip: remoteip,
+				}),
+			},
+		);
+
+		const result = await response.json();
+		return result;
+	} catch (error) {
+		console.error("Turnstile validation error:", error);
+		return { success: false, "error-codes": ["internal-error"] };
+	}
 }
 ```
 
@@ -116,7 +127,17 @@ The **Request rate analysis** tab in Security Analytics displays request rate di
 
 Create a rule that limits how many times a single IP address can submit to your form endpoint within a given period. Adjust the path, threshold, and period for your site.
 
-<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit contact form submissions", expression: '(http.request.uri.path eq "/contact" and http.request.method eq "POST")', expressionHelp: 'Replace "/contact" with your form endpoint path.', threshold: "5" }} />
+<Render
+	file="create-rate-limiting-rule"
+	product="waf"
+	params={{
+		ruleName: "Rate limit contact form submissions",
+		expression:
+			'(http.request.uri.path eq "/contact" and http.request.method eq "POST")',
+		expressionHelp: 'Replace "/contact" with your form endpoint path.',
+		threshold: "5",
+	}}
+/>
 
 :::note
 Rate limiting rule parameters (counting characteristics, periods, number of rules) vary by plan. For the full availability matrix, refer to [Rate limiting rules](/waf/rate-limiting-rules/#availability).
diff --git a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
index cfa61e65fe47d61..e1db4f92ef75e8b 100644
--- a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
+++ b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
@@ -11,16 +11,18 @@ sidebar:
   label: Stop account takeover
 ---
 
-import {
-  Steps,
-  DashButton,
-  GlossaryTooltip,
-  Render,
-} from "~/components";
+import { Steps, DashButton, GlossaryTooltip, Render } from "~/components";
 
 When your site has login pages, you need to decide how to verify that visitors are human, how aggressively to limit failed attempts, and which request patterns to block. This guide covers five stages: enforce HTTPS, turn on bot protection, add [Turnstile](/turnstile/) to your login form, create Application Security [rate limiting rules](/waf/rate-limiting-rules/) and [custom rules](/waf/custom-rules/) for suspicious patterns, and monitor for ongoing attacks using [SSL/TLS](/ssl/) transport security and [Cloudflare bot solutions](/bots/). The core workflow covers features available on Free, Pro, and Business plans. Enterprise features such as leaked credentials custom detection locations and Bot Management custom rules are included as callouts.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Enforce HTTPS to protect credentials in transit
 
@@ -98,10 +100,17 @@ You need both the sitekey and secret key in the following steps.
 #### 2. Add the client-side snippet
 
 Add the Turnstile script and widget container to your login form. Replace `<YOUR-SITE-KEY>` with the sitekey from the previous step.
+
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
+	<input
+		type="password"
+		id="password"
+		placeholder="Password"
+		autocomplete="off"
+		required
+	/>
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
@@ -118,6 +127,7 @@ The widget renders inside the `div` and produces a token when the visitor passes
 #### 3. Validate the token on your server
 
 Before processing the form submission, send the token to the Turnstile siteverify endpoint to confirm the visitor passed the challenge.
+
 ```js title="server.js"
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
@@ -156,6 +166,7 @@ For the complete response format, error codes, and examples in other languages,
 #### Test your implementation
 
 Turnstile provides test site keys that return predictable results without contacting the Siteverify API.
+
 - **Always passes**: Use site key `1x00000000000000000000AA` and secret key `1x0000000000000000000000000000000AA` to simulate a successful challenge.
 - **Always blocks**: Use site key `2x00000000000000000000AB` and secret key `2x0000000000000000000000000000000AA` to simulate a failed challenge.
 - **Forces interactive challenge**: Use site key `3x00000000000000000000FF` to test the interactive challenge flow.
@@ -172,7 +183,18 @@ The following example creates a rate limiting rule that issues a Managed Challen
 Managed Challenge and other [challenge types](/cloudflare-challenges/challenge-types/challenge-pages/) require an HTML response to render. They do not work for non-HTML responses such as AJAX/XHR requests, which are common on login endpoints that use single-page applications (SPAs) or API-based authentication. If your login flow uses AJAX, consider using [Turnstile Pre-Clearance](/turnstile/additional-configuration/pre-clearance-support/) instead.
 :::
 
-<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit login endpoint", expression: 'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"', expressionHelp: 'Replace `example.com` with your domain and `/login` with your login endpoint path.', threshold: "5" }} />
+<Render
+	file="create-rate-limiting-rule"
+	product="waf"
+	params={{
+		ruleName: "Rate limit login endpoint",
+		expression:
+			'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"',
+		expressionHelp:
+			"Replace `example.com` with your domain and `/login` with your login endpoint path.",
+		threshold: "5",
+	}}
+/>
 
 :::note
 (Optional) To count only failed login attempts instead of all matching requests, Business plan and above users can add a separate counting expression under **Increment counter when**:
@@ -320,7 +342,7 @@ Enterprise customers with Bot Management get additional tools for login protecti
 - **Custom rules with bot scores**: combine `cf.bot_management.score` with login path matching for precise control. Refer to [Custom rules for bot protection](/bots/additional-configurations/custom-rules/).
 - **Account takeover detections**: monitor suspicious login volume and failure rates using detection IDs in custom rules and rate limiting rules. Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/).
 - **Account Abuse Protection** (Early Access): detect account fraud patterns beyond credential stuffing. Refer to [Account Abuse Protection](/bots/account-abuse-protection/).
-:::
+  :::
 
 ## Monitor for ongoing compromise attempts
 
diff --git a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
index df0cbabb8f7a2aa..82e2fbcd9c90854 100644
--- a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
+++ b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
@@ -14,7 +14,14 @@ import { Tabs, TabItem, Steps, Render, DashButton } from "~/components";
 
 The right defense against malicious bot traffic depends on the traffic patterns on your site and your plan. This guide covers a layered approach using [Cloudflare Bots](/bots/), [Cloudflare Application Security](/waf/) (also known as Web Application Firewall or WAF), and [Turnstile](/turnstile/), from baseline protection to targeted custom rules. The core workflow uses features on Free, Pro, and Business plans, with callouts for Enterprise options.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Review your bot traffic
 
diff --git a/src/content/docs/use-cases/web-apps/performance.mdx b/src/content/docs/use-cases/web-apps/performance.mdx
index f3ac9b09881123e..8fa2bc53968700d 100644
--- a/src/content/docs/use-cases/web-apps/performance.mdx
+++ b/src/content/docs/use-cases/web-apps/performance.mdx
@@ -39,10 +39,9 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 
 - **Edge logic** - Run custom performance optimizations at the edge, such as HTML rewriting and dynamic content assembly, without round-trips to your origin
 
-
 ## Get started
 
 1. [Configure Cache Rules](/cache/how-to/cache-rules/)
 2. [Enable Argo Smart Routing](/argo-smart-routing/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
-4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
+4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
diff --git a/src/content/docs/vectorize/best-practices/index.mdx b/src/content/docs/vectorize/best-practices/index.mdx
index de610d3a68aed70..b5663efc9edfdd9 100644
--- a/src/content/docs/vectorize/best-practices/index.mdx
+++ b/src/content/docs/vectorize/best-practices/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/best-practices/list-vectors.mdx b/src/content/docs/vectorize/best-practices/list-vectors.mdx
index d623e334eb65385..0c5754e5d12cfb3 100644
--- a/src/content/docs/vectorize/best-practices/list-vectors.mdx
+++ b/src/content/docs/vectorize/best-practices/list-vectors.mdx
@@ -43,6 +43,7 @@ To see recently added or removed vectors, you must start a new list-vectors requ
 ### Response structure
 
 Each response includes:
+
 - `count`: Number of vectors returned in this response
 - `totalCount`: Total number of vectors in the index
 - `isTruncated`: Whether there are more vectors available
@@ -70,4 +71,4 @@ wrangler vectorize list-vectors my-index --count=1000
 wrangler vectorize list-vectors my-index --count=1000 --cursor="<cursor-from-response>"
 
 # Repeat until no more results
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/vectorize/demos.mdx b/src/content/docs/vectorize/demos.mdx
index d908b0b5883751d..f98a71856f7f16a 100644
--- a/src/content/docs/vectorize/demos.mdx
+++ b/src/content/docs/vectorize/demos.mdx
@@ -8,7 +8,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, ResourcesBySelector } from "~/components"
+import { GlossaryTooltip, ResourcesBySelector } from "~/components";
 
 Learn how you can use Vectorize within your existing architecture.
 
@@ -16,4 +16,11 @@ Learn how you can use Vectorize within your existing architecture.
 
 Explore the following <GlossaryTooltip term="reference architecture">reference architectures</GlossaryTooltip> that use Vectorize:
 
-<ResourcesBySelector types={["reference-architecture","design-guide","reference-architecture-diagram"]} products={["vectorize"]} />
+<ResourcesBySelector
+	types={[
+		"reference-architecture",
+		"design-guide",
+		"reference-architecture-diagram",
+	]}
+	products={["vectorize"]}
+/>
diff --git a/src/content/docs/vectorize/examples/agents.mdx b/src/content/docs/vectorize/examples/agents.mdx
index c7eb3790d39040b..e9bd2deab309881 100644
--- a/src/content/docs/vectorize/examples/agents.mdx
+++ b/src/content/docs/vectorize/examples/agents.mdx
@@ -9,4 +9,4 @@ description: Build AI-powered Agents on Cloudflare
 products:
   - vectorize
   - agents
----
\ No newline at end of file
+---
diff --git a/src/content/docs/vectorize/examples/index.mdx b/src/content/docs/vectorize/examples/index.mdx
index b7aaf4f768acdcd..f5b3b57929be9d3 100644
--- a/src/content/docs/vectorize/examples/index.mdx
+++ b/src/content/docs/vectorize/examples/index.mdx
@@ -11,7 +11,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, DirectoryListing } from "~/components"
+import { GlossaryTooltip, DirectoryListing } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Vectorize.
 
diff --git a/src/content/docs/vectorize/get-started/index.mdx b/src/content/docs/vectorize/get-started/index.mdx
index 2ea3f1ce7462b31..44c0cdc6b7ec9e3 100644
--- a/src/content/docs/vectorize/get-started/index.mdx
+++ b/src/content/docs/vectorize/get-started/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/platform/index.mdx b/src/content/docs/vectorize/platform/index.mdx
index 1be91e4d2f5aaf8..0dde65d6a58df96 100644
--- a/src/content/docs/vectorize/platform/index.mdx
+++ b/src/content/docs/vectorize/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/reference/index.mdx b/src/content/docs/vectorize/reference/index.mdx
index f297e13f34d84b6..8f496dea995d462 100644
--- a/src/content/docs/vectorize/reference/index.mdx
+++ b/src/content/docs/vectorize/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/about.mdx b/src/content/docs/version-management/about.mdx
index 6c6e429bda9459d..1587b66c14e88d6 100644
--- a/src/content/docs/version-management/about.mdx
+++ b/src/content/docs/version-management/about.mdx
@@ -9,7 +9,7 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Version Management works through a combination of **environments** and **versions**.
 
@@ -47,7 +47,7 @@ stateDiagram-v2
 
 ## Environments
 
-<Render file="environment-definition" product="version-management" /> <br/>
+<Render file="environment-definition" product="version-management" /> <br />
 
 After you [enable](/version-management/how-to/enable/) version management, you will have the ability to create default environments:
 
@@ -59,7 +59,7 @@ To send traffic to specific environments, send requests to that environment that
 
 ## Versions
 
-<Render file="version-definition" product="version-management" /> <br/>
+<Render file="version-definition" product="version-management" /> <br />
 
 <Render file="enable-default-creation" product="version-management" />
 
diff --git a/src/content/docs/version-management/how-to/compare-versions.mdx b/src/content/docs/version-management/how-to/compare-versions.mdx
index 587f8e9dea1faed..1b6ec4ea51148f4 100644
--- a/src/content/docs/version-management/how-to/compare-versions.mdx
+++ b/src/content/docs/version-management/how-to/compare-versions.mdx
@@ -19,7 +19,7 @@ To compare versions:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management** > **Comparisons**.
diff --git a/src/content/docs/version-management/how-to/environments.mdx b/src/content/docs/version-management/how-to/environments.mdx
index 7b1de502b4273a7..9c26342241ce248 100644
--- a/src/content/docs/version-management/how-to/environments.mdx
+++ b/src/content/docs/version-management/how-to/environments.mdx
@@ -9,44 +9,43 @@ products:
   - version-management
 ---
 
-import { DashButton, Render } from "~/components"
+import { DashButton, Render } from "~/components";
 
 <Render file="environment-definition" product="version-management" />
 
-***
+---
 
 ## Create environment
 
 <Render file="enable-default-creation" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" /> <br/>
+<Render file="create-environment-situation" product="version-management" />
+<br />
 
 To create a new environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Go to **Environments**.
 4. Select **Create Environment**.
 5. Provide the following information:
 
-* **Environment Name**: A unique, descriptive name for the environment.
-* [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
-* **Initial position**: Controls where this environment should be in your testing process.
+- **Environment Name**: A unique, descriptive name for the environment.
+- [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
+- **Initial position**: Controls where this environment should be in your testing process.
 
 6. Select **Create**.
 
 :::note
 
-
 You can only adjust the [**Read-only Environment**](/version-management/reference/read-only-environments/) configuration after an environment has been created.
 
-
 :::
 
-***
+---
 
 ## Edit environment
 
@@ -54,7 +53,7 @@ To edit an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -62,7 +61,7 @@ To edit an environment:
 5. Make any required changes.
 6. Select **Save**.
 
-***
+---
 
 ## Change environment version
 
@@ -74,7 +73,7 @@ For more details on the flow of versions and environments, refer to [How it work
 
 Promotion moves a version from a lower-ranked environment to the next highest one.
 
-<Render file="promote-version" product="version-management" /> <br/>
+<Render file="promote-version" product="version-management" /> <br />
 
 ### Roll back a version
 
@@ -84,13 +83,13 @@ To roll back a version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
 4. On a specific environment, select **Roll back**.
 
-***
+---
 
 ## Delete environment
 
@@ -98,7 +97,7 @@ To delete an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -107,8 +106,6 @@ To delete an environment:
 
 :::note
 
-
 You cannot delete your **Production** environment.
 
-
 :::
diff --git a/src/content/docs/version-management/how-to/index.mdx b/src/content/docs/version-management/how-to/index.mdx
index 94f85edeb05a853..688bebd5f8faf4c 100644
--- a/src/content/docs/version-management/how-to/index.mdx
+++ b/src/content/docs/version-management/how-to/index.mdx
@@ -3,7 +3,7 @@ title: How to
 pcx_content_type: navigation
 sidebar:
   order: 4
-  group: 
+  group:
     hideIndex: true
 
 description: Guides for managing versions and environments.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/how-to/versions.mdx b/src/content/docs/version-management/how-to/versions.mdx
index 2bacb859b39b82d..df497bbd391bd24 100644
--- a/src/content/docs/version-management/how-to/versions.mdx
+++ b/src/content/docs/version-management/how-to/versions.mdx
@@ -25,7 +25,7 @@ To create a new version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **Clone**. This will copy over all configurations from that version.
@@ -78,7 +78,7 @@ To view metrics:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **View Metrics**.
diff --git a/src/content/docs/version-management/reference/available-configurations.mdx b/src/content/docs/version-management/reference/available-configurations.mdx
index d9d33c1d24d8f15..bf748224eda2e08 100644
--- a/src/content/docs/version-management/reference/available-configurations.mdx
+++ b/src/content/docs/version-management/reference/available-configurations.mdx
@@ -9,24 +9,22 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When you use Version Management, you can edit various configurations, such as [WAF custom rules](/waf/custom-rules/) and [Cache](/cache/).
 
 Generally, you are allowed to edit all zone-level configurations except for the following:
 
-* [DNS](/dns/)
-* [Spectrum](/spectrum/)
-* Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
-* [Zero Trust](/cloudflare-one/) and Access policies
-* [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
+- [DNS](/dns/)
+- [Spectrum](/spectrum/)
+- Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
+- [Zero Trust](/cloudflare-one/) and Access policies
+- [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
 
 :::note
 
-
 For the most up-to-date list of these configurations, start [editing configurations within a version](/version-management/how-to/versions/#change-configurations-in-a-version) in the Cloudflare dashboard.
 
-
 :::
 
 ## Limitations
diff --git a/src/content/docs/version-management/reference/index.mdx b/src/content/docs/version-management/reference/index.mdx
index 38759a3843efde4..042d6149a274f5b 100644
--- a/src/content/docs/version-management/reference/index.mdx
+++ b/src/content/docs/version-management/reference/index.mdx
@@ -3,7 +3,7 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 5
-  group: 
+  group:
     hideIndex: true
 
 description: Reference information for AI Crawl Control.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/reference/read-only-environments.mdx b/src/content/docs/version-management/reference/read-only-environments.mdx
index b6e45386b17cec4..36c12fc21a35a82 100644
--- a/src/content/docs/version-management/reference/read-only-environments.mdx
+++ b/src/content/docs/version-management/reference/read-only-environments.mdx
@@ -9,14 +9,15 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When an environment is read-only, versions deployed to this environment will permanently become read-only. This configuration protects sensitive environments from accidental changes.
 
 **Version Zero** is an exception to this rule and is always editable.
 
-<Render file="production-read-only-default" product="version-management" /> <br/>
+<Render file="production-read-only-default" product="version-management" />
+<br />
 
-For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** *after* your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
+For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** _after_ your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
 
 To change the read-only status of an environment, [edit the environment](/version-management/how-to/environments/#edit-environment).
diff --git a/src/content/docs/waf/custom-rules/create-dashboard.mdx b/src/content/docs/waf/custom-rules/create-dashboard.mdx
index 5e974d601239c71..a48edb1f3026c30 100644
--- a/src/content/docs/waf/custom-rules/create-dashboard.mdx
+++ b/src/content/docs/waf/custom-rules/create-dashboard.mdx
@@ -15,7 +15,6 @@ head:
 
 import { Render, Tabs, TabItem, Steps, DashButton } from "~/components";
 
-
 <Tabs syncKey="dashNewNav"> <TabItem label="New dashboard" icon="rocket">
 
 <Steps>
diff --git a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
index 749a72275225954..6775abcaf7788d7 100644
--- a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
+++ b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
@@ -10,4 +10,4 @@ import { Render } from "~/components";
 
 You can build an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
 
-<Render file="sequence-custom-rules" product="api-shield" />
\ No newline at end of file
+<Render file="sequence-custom-rules" product="api-shield" />
diff --git a/src/content/docs/waf/glossary.mdx b/src/content/docs/waf/glossary.mdx
index e777165a6bf1999..f7ce048d441c2e7 100644
--- a/src/content/docs/waf/glossary.mdx
+++ b/src/content/docs/waf/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - waf
 sidebar:
   order: 17
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's WAF documentation.
 
diff --git a/src/content/docs/waf/managed-rules/index.mdx b/src/content/docs/waf/managed-rules/index.mdx
index d24fec1853393e0..dcdce6b4f353b4b 100644
--- a/src/content/docs/waf/managed-rules/index.mdx
+++ b/src/content/docs/waf/managed-rules/index.mdx
@@ -81,4 +81,3 @@ This means a rule with a terminal action (such as Block or Managed Challenge) in
 ### WAF exceptions
 
 WAF exceptions (skip rules) are rules with a `skip` action deployed to the `http_request_firewall_managed` phase entry-point ruleset. They are evaluated in list order within the entry-point ruleset — a skip rule only bypasses `execute` rules listed after it. Place exceptions before the managed ruleset execute rules they are intended to skip. For more information, refer to [WAF exceptions](/waf/managed-rules/waf-exceptions/).
-
diff --git a/src/content/docs/waf/tools/index.mdx b/src/content/docs/waf/tools/index.mdx
index 2547f0abc231788..93bf5ec8fba60f0 100644
--- a/src/content/docs/waf/tools/index.mdx
+++ b/src/content/docs/waf/tools/index.mdx
@@ -12,7 +12,6 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-
 The Cloudflare WAF offers the following additional tools:
 
 <DirectoryListing />
diff --git a/src/content/docs/waf/tools/privacy-pass.mdx b/src/content/docs/waf/tools/privacy-pass.mdx
index dce774674951b17..253f4e8bd646159 100644
--- a/src/content/docs/waf/tools/privacy-pass.mdx
+++ b/src/content/docs/waf/tools/privacy-pass.mdx
@@ -7,7 +7,6 @@ source: https://support.cloudflare.com/hc/en-us/articles/115001992652-Using-Priv
 title: Privacy Pass
 tags:
   - Privacy
-
 ---
 
 [Privacy Pass](https://datatracker.ietf.org/wg/privacypass/about/) specifies an extensible protocol for creating and redeeming anonymous and transferable tokens. Its specification is maintained by the IETF.
@@ -15,7 +14,7 @@ Cloudflare provides "Silk - Privacy Pass Client". This is a Chrome and Firefox b
 
 For instance, a visitor IP address with poor reputation may receive a Cloudflare challenge page before gaining access to a Cloudflare-protected website. Privacy Pass allows the visitor to solve a challenge with or without interaction, depending on the device. Solving this challenge is coordinated with a third party attester in such a way that Cloudflare does not see the attestation method or the interaction, preserving visitors' privacy while maintaining a high level of security.
 
-***
+---
 
 ## Set up Privacy Pass
 
@@ -23,12 +22,12 @@ For instance, a visitor IP address with poor reputation may receive a Cloudflare
 
 Your end users should download the Privacy Pass extension for either Google Chrome or Firefox:
 
-* [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
-* [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
+- [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
+- [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
 
 The Privacy Pass code is [available on GitHub](https://github.com/cloudflare/pp-browser-extension). You can report any issues in this repository.
 
-***
+---
 
 ## Support for Privacy Pass v1 (legacy)
 
diff --git a/src/content/docs/waf/troubleshooting/faq.mdx b/src/content/docs/waf/troubleshooting/faq.mdx
index d7e6a3b09ec4447..a3a09ba5996df45 100644
--- a/src/content/docs/waf/troubleshooting/faq.mdx
+++ b/src/content/docs/waf/troubleshooting/faq.mdx
@@ -34,6 +34,7 @@ If you are using a regular expression, it is recommended that you test it with a
 If you have [SSL/TLS certificates](/ssl/) managed by Cloudflare, every time a certificate is issued or renewed, a [domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/dcv-flow/) must happen. When a certificate is in `pending_validation` state and there are valid DCV tokens in place, some Cloudflare security features such as [custom rules](/waf/custom-rules/) and [Managed Rules](/waf/managed-rules/) will be automatically disabled on specific DCV paths (for example, `/.well-known/pki-validation/` and `/.well-known/acme-challenge/`).
 
 These automatic bypasses do not appear in [Trace](/rules/trace-request/) results.
+
 ### Why have I been blocked?
 
 Cloudflare may block requests when it detects activity that could be unsafe. Common reasons include:
diff --git a/src/content/docs/waiting-room/about.mdx b/src/content/docs/waiting-room/about.mdx
index ae5c646b790822d..85b25d1bb61107e 100644
--- a/src/content/docs/waiting-room/about.mdx
+++ b/src/content/docs/waiting-room/about.mdx
@@ -6,10 +6,9 @@ products:
   - waiting-room
 sidebar:
   order: 2
-
 ---
 
-import { LinkButton, Render } from "~/components"
+import { LinkButton, Render } from "~/components";
 
 Waiting Room queues visitors when your traffic approaches a previously defined threshold that might otherwise bring an application down.
 
@@ -21,7 +20,6 @@ Once you have [created and activated a waiting room](/waiting-room/get-started/)
 
 - If a page is not experiencing heavy traffic, a visitor accesses the page directly.
 - If page traffic approaches a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
-
   - Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
   - While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
   - When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
@@ -47,4 +45,4 @@ The other factor is the Waiting Room state, which is maintained at the local dat
 
 The Waiting Room state is updated with global information every few seconds. We have a pipeline set up in Cloudflare [Durable Objects](/durable-objects/) that ensures changes in traffic get propagated around the world. This architecture ensures that we do not introduce additional latency, as well as that we are making decisions with as near-time accuracy as possible.
 
-For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
\ No newline at end of file
+For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
diff --git a/src/content/docs/waiting-room/additional-options/create-events.mdx b/src/content/docs/waiting-room/additional-options/create-events.mdx
index 123834ddd12dbc3..6fba618cbc22dd8 100644
--- a/src/content/docs/waiting-room/additional-options/create-events.mdx
+++ b/src/content/docs/waiting-room/additional-options/create-events.mdx
@@ -6,7 +6,6 @@ products:
 title: Create scheduled events
 sidebar:
   order: 4
-
 ---
 
 When you want to customize the behavior of a waiting room for a specific period of time — such as changing the queueing method or increasing the total active users — set up a **scheduled event**. You can do this from the dashboard or via the API.
@@ -21,7 +20,7 @@ Only some customers can support scheduled events with their waiting rooms. For m
 
 1. Within your application, go to **Traffic** > **Waiting Room**.
 
-2. Expand a waiting room  and select **Schedule event**.
+2. Expand a waiting room and select **Schedule event**.
 
 3. Customize the details for your event: name the event, add a description (optional), and select a Start Date Time and an End Date Time.
 
@@ -65,23 +64,21 @@ If you are using a [custom template](/waiting-room/how-to/customize-waiting-room
 
 :::note
 
-
 If you need to create overlapping events, use different waiting rooms.
 
-
 :::
 
 ### Parameters
 
 Though most parameters are identical to those in a regular waiting room, there are a few unique to creating an event. For a complete list of event settings, please refer to [Create an Event](/api/resources/waiting_rooms/subresources/events/methods/create/).
 
-* `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
-* `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
-* `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
-* `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
-* `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
-* `description`: A text description providing more detail about the event.
-* `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
+- `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
+- `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
+- `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
+- `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
+- `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
+- `description`: A text description providing more detail about the event.
+- `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
 
 ### Queueing methods
 
@@ -99,8 +96,8 @@ Users who reach your application **during the prequeue period** are [randomly as
 
 To set up a "lottery", include the [following parameters](#parameters) in your API request:
 
-* `prequeue_start_time`
-* `shuffle_at_event_start`
+- `prequeue_start_time`
+- `shuffle_at_event_start`
 
 ## Preview an event configuration
 
@@ -125,12 +122,12 @@ Follow these steps if you would like to deploy a scheduled maintenance page, wit
 1. [Create a waiting room](/waiting-room/how-to/create-waiting-room/) with [Passthrough](/waiting-room/reference/queueing-methods/#passthrough) queueing method enabled.
 2. Create a waiting room event for this room with [Reject](/waiting-room/reference/queueing-methods/#reject) queueing method enabled.
 
-After the scheduled event has ended, users will have access to your site.  You can end the maintenance window before the scheduled event is over by setting the event to disabled.
+After the scheduled event has ended, users will have access to your site. You can end the maintenance window before the scheduled event is over by setting the event to disabled.
 
 ## Other API commands
 
-| Function                                                          | Command  |
-| ----------------------------------------------------------------- | -------- |
-| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)   | `GET`    |
+| Function                                                                                | Command  |
+| --------------------------------------------------------------------------------------- | -------- |
+| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)      | `GET`    |
 | [List scheduled events](/api/resources/waiting_rooms/subresources/events/methods/list/) | `GET`    |
-| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)         | `DELETE` |
+| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)        | `DELETE` |
diff --git a/src/content/docs/waiting-room/additional-options/index.mdx b/src/content/docs/waiting-room/additional-options/index.mdx
index 92470e9cc3b208c..bd77dc9b14cc6ad 100644
--- a/src/content/docs/waiting-room/additional-options/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Beyond [creating a waiting room](/waiting-room/get-started/), you may want to further customize how your waiting room functions.
 
diff --git a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
index bd9c6161eebc229..8eac756e51d27f1 100644
--- a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
+++ b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
@@ -6,7 +6,6 @@ products:
 title: Combine with Cloudflare for SaaS
 sidebar:
   order: 7
-
 ---
 
 If your application is using a custom hostname — meaning your SaaS provider is using [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) — your application can support a waiting room.
diff --git a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
index 0f15a5bf0d091f7..c39b032cfdb8839 100644
--- a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Waiting Room Rules
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In this section, we will list the Waiting Room rules available.
 
diff --git a/src/content/docs/waiting-room/api-reference.mdx b/src/content/docs/waiting-room/api-reference.mdx
index b91d98532f5c31c..893bc601dbd2942 100644
--- a/src/content/docs/waiting-room/api-reference.mdx
+++ b/src/content/docs/waiting-room/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/waiting_rooms/methods/list/
 sidebar:
   order: 10
-
 ---
diff --git a/src/content/docs/waiting-room/glossary.mdx b/src/content/docs/waiting-room/glossary.mdx
index 5e0ec50ac37db3d..aa5be06af954401 100644
--- a/src/content/docs/waiting-room/glossary.mdx
+++ b/src/content/docs/waiting-room/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Waiting Room documentation.
 products:
   - waiting-room
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Waiting Room documentation.
 
diff --git a/src/content/docs/waiting-room/how-to/control-user-session.mdx b/src/content/docs/waiting-room/how-to/control-user-session.mdx
index a8981dcd2100717..9f585b420804aa8 100644
--- a/src/content/docs/waiting-room/how-to/control-user-session.mdx
+++ b/src/content/docs/waiting-room/how-to/control-user-session.mdx
@@ -8,13 +8,13 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Adjust these settings to control how long a user can hold their place on your site after leaving the waiting room.
 
 ## Session duration
 
-Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes.  Each new request restarts a user’s time to stay active equal to **session duration**. 
+Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes. Each new request restarts a user’s time to stay active equal to **session duration**.
 
 ## Disable session renewal to limit browsing time
 
@@ -24,9 +24,9 @@ You can limit each user’s time on your site to only one session duration by ch
 
 To terminate a user's session when they perform a specific action, you can send a command to the waiting room using an HTTP header on the response from your origin. This command tells the waiting room to revoke the session of the user associated with the current response. This allows spots to open up more dynamically and may increase throughput from your queue.
 
-To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard. 
+To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard.
 To enable this feature through the [Cloudflare API](/api/resources/waiting_rooms/methods/update/), update the `enabled_origin_commands` property to include the value `”revoke”` in the list of enabled origin commands.
- 
+
 Then, to return a revocation origin command and revoke the user's session associated with the current request, add the `Cf-Waiting-Room-Command: revoke` HTTP header to the response from your origin.
 
 To get the number of sessions revoked, you can query `sessionsRevoked` metrics from your [Waiting Room analytics](/waiting-room/waiting-room-analytics/#graphql-analytics) data via GraphQL API.
diff --git a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
index ea279a612cbaf63..f826cb8f5c312f5 100644
--- a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
 title: Edit and delete waiting rooms
 sidebar:
   order: 5
-
 ---
 
 import { APIRequest } from "~/components";
@@ -41,36 +40,36 @@ For details about updating an active waiting room, refer to [Best practices](/wa
 [Replace](https://api.cloudflare.com#waiting-room-update-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="PUT"
-  json={{
-    name: "webshop-waiting-room",
-    host: "example.com",
-    new_users_per_minute: 200,
-    total_active_users: 300
-  }}
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="PUT"
+	json={{
+		name: "webshop-waiting-room",
+		host: "example.com",
+		new_users_per_minute: 200,
+		total_active_users: 300,
+	}}
 />
 
 [Update](https://api.cloudflare.com#waiting-room-patch-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="PATCH"
-  json={{
-    name: "webshop-waiting-room",
-    host: "example.com",
-    new_users_per_minute: 200,
-    total_active_users: 300
-  }}
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="PATCH"
+	json={{
+		name: "webshop-waiting-room",
+		host: "example.com",
+		new_users_per_minute: 200,
+		total_active_users: 300,
+	}}
 />
 
-
 You only need to include the fields you want to update in the payload of the PATCH request.
+
 ### Delete a waiting room
 
 Delete a waiting room by appending the following endpoint in the [Waiting Room API](https://api.cloudflare.com#waiting-room-delete-waiting-room) to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="DELETE"
-/>
\ No newline at end of file
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="DELETE"
+/>
diff --git a/src/content/docs/waiting-room/how-to/index.mdx b/src/content/docs/waiting-room/how-to/index.mdx
index be1f971a0c6909b..38bb6f03248845f 100644
--- a/src/content/docs/waiting-room/how-to/index.mdx
+++ b/src/content/docs/waiting-room/how-to/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Common tasks
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 When working with Cloudflare Waiting Room, you will commonly perform the following tasks:
 
diff --git a/src/content/docs/waiting-room/how-to/json-response.mdx b/src/content/docs/waiting-room/how-to/json-response.mdx
index 4851e4a1a5bc96a..71bc059dc58e13a 100644
--- a/src/content/docs/waiting-room/how-to/json-response.mdx
+++ b/src/content/docs/waiting-room/how-to/json-response.mdx
@@ -65,13 +65,11 @@ In a browser environment, the page automatically refreshes every `refreshInterva
 These are some of the places where the JSON-friendly response can be consumed (this list is not exhaustive):
 
 1. In a mobile app traffic
-
    - **Integrate Waiting Room variables** – Create a new template in your mobile app to receive the JSON response. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Allow cookies** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your mobile app will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Consume JSON data** - Make a request to the Waiting Room endpoint with the `Accept: application/json` header.
 
 2. Inside Cloudflare Workers (or in your own backend service)
-
    - **Integrate Waiting Room variables** – Expect a JSON response in your backend API. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Include cookies in the request header** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your backend API will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Enable JSON response** - Via the dashboard or via the API.
diff --git a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
index f17f0406cc79484..00fa24999781e3f 100644
--- a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
 title: Monitor waiting room status
 sidebar:
   order: 3
-
 ---
 
 import { APIRequest } from "~/components";
@@ -23,37 +22,37 @@ Open the **Waiting Room** dashboard to view the list of your waiting rooms.
 
 The **Status** column displays the current state of the waiting room:
 
-* **Not queueing**:
-  * Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
-  * Shows estimated number of users in the application.
-* **Queueing**:
-  * Waiting room enabled and sending visitors to waiting room.
-  * Shows estimated number of users in the queue.
-  * On hover, shows maximum wait time expected for users.
-* **Disabled**: The waiting room is suspended.
-* **Queue-all**:
-  * Forces all traffic to queue in the waiting room.
-  * On hover, shows estimated number of users in the queue.
+- **Not queueing**:
+  - Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
+  - Shows estimated number of users in the application.
+- **Queueing**:
+  - Waiting room enabled and sending visitors to waiting room.
+  - Shows estimated number of users in the queue.
+  - On hover, shows maximum wait time expected for users.
+- **Disabled**: The waiting room is suspended.
+- **Queue-all**:
+  - Forces all traffic to queue in the waiting room.
+  - On hover, shows estimated number of users in the queue.
 
 ## Status in the API
 
 [Check whether traffic is queueing in a configured waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) by appending the following endpoint to the Cloudflare API base URL:
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
-  method="GET"
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
+	method="GET"
 />
 
 The response is:
 
-* `queueing` if visitors are currently queueing in the waiting room.
-* `not_queueing` if the room is empty or if the waiting room is suspended.
+- `queueing` if visitors are currently queueing in the waiting room.
+- `not_queueing` if the room is empty or if the waiting room is suspended.
 
 To check whether a configured waiting room is suspended or whether the traffic is force-queued to the waiting room, append the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="GET"
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="GET"
 />
 
 The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/get/) for a configured waiting room:
@@ -88,13 +87,13 @@ The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/g
 
 The value of `suspended` indicates whether a waiting room is activated or suspended:
 
-* `false`: The waiting room is activated.
-* `true`: The waiting room is suspended.
+- `false`: The waiting room is activated.
+- `true`: The waiting room is suspended.
 
 The value of `queue_all` indicates whether all traffic is forced to queue in the waiting room:
 
-* `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
-* `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
+- `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
+- `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
 
 ## Queueing activation
 
@@ -108,5 +107,5 @@ To help prevent a waiting room from active queueing, increase the values for `ne
 
 :::note
 
-Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products. 
+Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products.
 :::
diff --git a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
index d8e1e831c020a7e..3f4ca5fb6eafa52 100644
--- a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
   - waiting-room
 sidebar:
   order: 2
-
 ---
 
 When [configuring a waiting room](/waiting-room/how-to/create-waiting-room/), you need to indicate which pages the waiting room will cover.
@@ -21,8 +20,8 @@ You cannot add any hostname and path combinations already configured for another
 
 A single waiting room can be applied to multiple custom hostnames as long as the following is true:
 
-* The apex domain is the same between the custom hostnames
-* Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
+- The apex domain is the same between the custom hostnames
+- Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
 
 ## Custom hostnames
 
diff --git a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
index 3876ca31bccde46..5039172c35fa4e8 100644
--- a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
+++ b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
@@ -6,7 +6,6 @@ products:
 title: Access Waiting Room
 sidebar:
   order: 1
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,6 +14,6 @@ Use Cloudflare Waiting Room to create a holding area where users can queue to ac
 
 To access Waiting Room on the Cloudflare dashboard, go to the **Waiting Room** page.
 
-   <DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
+<DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
 
 Use the dashboard to [create, edit, update, and delete](/waiting-room/how-to/) waiting rooms.
diff --git a/src/content/docs/waiting-room/plans.mdx b/src/content/docs/waiting-room/plans.mdx
index 29189c6fe19e6d5..a4041473cdfc940 100644
--- a/src/content/docs/waiting-room/plans.mdx
+++ b/src/content/docs/waiting-room/plans.mdx
@@ -10,10 +10,9 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
-
 ---
 
-import { FeatureTable, Render } from "~/components"
+import { FeatureTable, Render } from "~/components";
 
 The features available for a waiting room depend on your plan type. You can only have **one plan** per zone.
 
diff --git a/src/content/docs/waiting-room/reference/configuration-settings.mdx b/src/content/docs/waiting-room/reference/configuration-settings.mdx
index 20481e7adaee0c6..0d6c313160fc12b 100644
--- a/src/content/docs/waiting-room/reference/configuration-settings.mdx
+++ b/src/content/docs/waiting-room/reference/configuration-settings.mdx
@@ -7,15 +7,18 @@ products:
 title: Configuration settings
 sidebar:
   order: 2
-
 ---
 
-import { Description, LinkButton } from "~/components"
+import { Description, LinkButton } from "~/components";
 
 You can customize a variety of options for your waiting rooms.
 
- <LinkButton variant="primary" href="#dashboard-settings">Dashboard settings</LinkButton> <LinkButton variant="secondary" href="#additional-details">Additional details</LinkButton>
-
+<LinkButton variant="primary" href="#dashboard-settings">
+	Dashboard settings
+</LinkButton>
+<LinkButton variant="secondary" href="#additional-details">
+	Additional details
+</LinkButton>
 
 ## Dashboard settings
 
diff --git a/src/content/docs/waiting-room/reference/index.mdx b/src/content/docs/waiting-room/reference/index.mdx
index 4567f07d6834f80..386e738762a9e82 100644
--- a/src/content/docs/waiting-room/reference/index.mdx
+++ b/src/content/docs/waiting-room/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use the following reference information when setting up and deploying your waiting rooms:
 
diff --git a/src/content/docs/waiting-room/reference/waiting-room-api.mdx b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
index cd9d3e20bb3a293..9d57a00c62e2a34 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-api.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
@@ -4,7 +4,6 @@ description: API commands for managing waiting rooms.
 products:
   - waiting-room
 title: API commands
-
 ---
 
 Cloudflare Waiting Room redirect visitors to virtual waiting rooms when they are trying to access web pages that have high volumes of traffic.
@@ -25,17 +24,17 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 ## Manage your waiting room
 
-| Operation                                                                 | Method + URL stub                                             | Notes                              |
-| ------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
-| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)     | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
-| [Create waiting room](/api/resources/waiting_rooms/methods/create/)   | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
-| [Waiting room details](/api/resources/waiting_rooms/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
-| [Update waiting room](/api/resources/waiting_rooms/methods/update/)   | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
-| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/)   | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
-| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)     | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
+| Operation                                                           | Method + URL stub                                             | Notes                              |
+| ------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
+| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)    | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
+| [Create waiting room](/api/resources/waiting_rooms/methods/create/) | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
+| [Waiting room details](/api/resources/waiting_rooms/methods/get/)   | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
+| [Update waiting room](/api/resources/waiting_rooms/methods/update/) | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
+| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/) | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
+| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)    | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
 
 ## Fetch the current status of a waiting room
 
-| Operation                                                                                        | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
-| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation                                                                                                   | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
+| ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [Get the current status of a waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}/status` | <ul><li>Returns <code>queueing</code> if the queue is activated (clients are put in the waiting room).</li><li>Returns <code>not\_queueing</code> if the queue is not activated or if the waiting room is suspended.</li></ul> |
diff --git a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
index fc575945d64c011..999050767f022fd 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
@@ -12,24 +12,22 @@ A waiting room only uses the `__cfwaitingroom` cookie when a visitor requests ac
 
 :::caution[Important:]
 
-
 Cloudflare Waiting Room requires the `__cfwaitingroom` cookie. When a waiting room is actively queueing, users cannot visit that host and path combination without enabling cookies.
 
-
 :::
 
 ## Cookie function
 
 The `__cfwaitingroom` cookie is used to:
 
-* Track a user's position in the waiting room queue and serve them in the correct order.
-* Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
-* To allow re-entry for a period of time (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
+- Track a user's position in the waiting room queue and serve them in the correct order.
+- Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
+- To allow re-entry for a period of time (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
 
 ## Cookie expiration time
 
-* While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
-* When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)).
+- While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
+- When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)).
 
 ## Customize cookie name
 
diff --git a/src/content/docs/waiting-room/troubleshooting.mdx b/src/content/docs/waiting-room/troubleshooting.mdx
index 79df5d5298f08bd..0ff28fdedd01e62 100644
--- a/src/content/docs/waiting-room/troubleshooting.mdx
+++ b/src/content/docs/waiting-room/troubleshooting.mdx
@@ -7,17 +7,16 @@ title: FAQ
 structured_data: true
 sidebar:
   order: 11
-
 ---
 
 Below you will find answers to our most commonly asked questions about the Waiting Room.
 
-* [Configuration](#configuration)
-* [Features and products](#features-and-products)
-* [User behavior](#user-behavior)
-* [Monitor your waiting room](#monitor-your-waiting-room)
+- [Configuration](#configuration)
+- [Features and products](#features-and-products)
+- [User behavior](#user-behavior)
+- [Monitor your waiting room](#monitor-your-waiting-room)
 
-***
+---
 
 ## Configuration
 
@@ -25,7 +24,6 @@ Below you will find answers to our most commonly asked questions about the Waiti
 
 Yes. For more details, refer to [Customize a waiting room](/waiting-room/how-to/customize-waiting-room/).
 
-
 ### Why does my waiting room look different than how I designed it?
 
 If you have [customized your waiting room template](/waiting-room/how-to/customize-waiting-room):
@@ -35,10 +33,8 @@ If you have [customized your waiting room template](/waiting-room/how-to/customi
 
 :::note[Note]
 
-
 Only Enterprise customers can customize the appearance of their waiting room.
 
-
 :::
 
 ### What can I update when my waiting room is actively queueing?
@@ -47,69 +43,51 @@ You can update a [waiting room's template](/waiting-room/how-to/customize-waitin
 
 You can also update the [configuration settings](/waiting-room/reference/configuration-settings) of a waiting room, but only make these changes when necessary. These changes may impact the estimated wait time shown to end users and cause unnecessary confusion.
 
-
-
-
 ## Features and products
 
 ### Which features are included in my Waiting Room plan?
 
 To check which features are available to different plan types, refer to [Plans](/waiting-room/plans/).
 
-
-
 ### How does Waiting Room interact with other Cloudflare products?
 
 Some Cloudflare products run before a waiting room acts on traffic:
 
-* DDoS Mitigation
-* Web Application Firewall (WAF)
-* Bot Management
-* Page Rules
+- DDoS Mitigation
+- Web Application Firewall (WAF)
+- Bot Management
+- Page Rules
 
 Other Cloudflare products run after a waiting room acts on traffic:
 
-* Workers
-
-
-
+- Workers
 
 ## User behavior
 
-
 ### What happens if a user refreshes their tab when in a waiting room?
 
 A manual tab refresh has no effect on a user's position in your waiting room.
 
 However, if they close their tab and then try to access the application again during active queueing, they will lose their spot and have to go to the back of the queue.
 
-
 ### What happens if a queued user leaves the queue?
 
 When a user joins the queue, they are placed into a bucket which is their general position in line. When a user leaves the queue (closes the browser or tab), their place in line is held for five minutes after the last refresh. This grace period allows users to keep their position in line if they experience a brief disconnection. After five minutes, the grace period expires and they are no longer counted as waiting in the queue.
 
-
-
 ## Monitor your waiting room
 
-
 ### Why do I observe a few users being queued in the dashboard?
 
-
 Some users might be queued before your waiting room reaches is limit due to architectural designs. For more details on the behavior and how to fix it, refer to [​​Queueing activation](/waiting-room/how-to/monitor-waiting-room#queueing-activation).
 
-
-
 ### Why are some users not being queued in my waiting room?
 
-
 If you notice users not being queued to your waiting room, make sure the path you defined exactly matches the path of your website.
 
 The path is case-sensitive, so if you have a waiting room set up for `/Black-Friday-Sale` and users go to `/black-friday-sale`, they will bypass your waiting room.
 
 For more details, refer to [Best practices](/waiting-room/reference/best-practices).
 
-
 ### Why are users being blocked from entering my waiting room?
 
 If you have Rate Limiting, check your [rate limiting rules](/waf/rate-limiting-rules/).
@@ -118,17 +96,15 @@ The Waiting Room queue page refreshes every 20 seconds by populating the refresh
 
 Your user also might not have [cookies](/waiting-room/reference/waiting-room-cookie) enabled. If they do not enable cookies and your waiting room is actively queueing traffic, they will not reach your endpoint until the queueing stops.
 
-
 ### Why is the estimated wait time increasing for some users?
 
 Estimated wait times may increase if the rate of users leaving your site decreases. The estimated wait time is updated upon each page refresh based on the most recently available information about the rate of slots opening up on your site and the number of users ahead of the user in line. To make this increase less likely, you could limit the amount of time users are allowed to spend on your site by disabling session renewal. Be aware that, if you change your traffic settings, estimated wait times will change as well.
 
-
 ### Why is `new users per minute` low when there is capacity available?
 
 The `new users per minute` metric tracks how many users were accepted to the origin in the last minute. It is only incremented when a queued user refreshes and is accepted to the origin. If the waiting room queueing method is set to `fifo`, we will wait until all queued users in a minute-based bucket are accepted before moving to the next bucket. If many of the users in a bucket have abandoned the queue, then the waiting room must wait until their place in line expires before moving on to the next bucket. This can cause `new users per minute` to be low when only a small percentage of queued users are actually still waiting.
 
-This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting  them in an infinite queue.
+This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting them in an infinite queue.
 
 ### Why are my Waiting Room analytics and Google analytics not matching?
 
@@ -142,8 +118,8 @@ Another key difference is that Waiting Room runs on requests made to the origin,
 
 ### Why did my traffic exceed the New Users Per Minute threshold?
 
-Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally. 
+Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally.
 
 In the case of a rapid spike — rising to several thousand users within a minute — the global state propagation process takes approximately two minutes, resulting in a delay before all data centers become aware of the spike. If this information is not disseminated quickly enough to other locations, temporary overshooting may occur, particularly when lower limits are in place.
 
-This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
\ No newline at end of file
+This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
diff --git a/src/content/docs/warp-client/get-started/linux.mdx b/src/content/docs/warp-client/get-started/linux.mdx
index 8aaf86985cb9983..5d816a7dfe1846d 100644
--- a/src/content/docs/warp-client/get-started/linux.mdx
+++ b/src/content/docs/warp-client/get-started/linux.mdx
@@ -78,19 +78,20 @@ To enable [WARP+ Unlimited](/warp-client/warp-modes/#warp-unlimited) on Linux, y
 2. Go to **Settings** > **Account** and copy the **Key** value.
 3. On your Linux device, run the following command:
 
-	```sh
-	warp-cli registration license <KEY>
-	```
+   ```sh
+   warp-cli registration license <KEY>
+   ```
+
 4. Verify the new registration:
 
-	```sh
-	warp-cli registration show
-	```
+   ```sh
+   warp-cli registration show
+   ```
 
-	```sh output
-	Account type: Unlimited
-	...
-	```
+   ```sh output
+   Account type: Unlimited
+   ...
+   ```
 
 Your WARP+ Unlimited subscription is now active on this device.
 
diff --git a/src/content/docs/warp-client/known-issues-and-faq.mdx b/src/content/docs/warp-client/known-issues-and-faq.mdx
index b4e0b7837fc2175..3f43023c46ff622 100644
--- a/src/content/docs/warp-client/known-issues-and-faq.mdx
+++ b/src/content/docs/warp-client/known-issues-and-faq.mdx
@@ -7,7 +7,6 @@ products:
 structured_data: true
 sidebar:
   order: 5
-
 ---
 
 Below you will find answers to our most commonly asked questions regarding the WARP client. If you cannot find the answer you are looking for, refer to the [community page](https://community.cloudflare.com/) to explore more resources.
@@ -16,9 +15,9 @@ Below you will find answers to our most commonly asked questions regarding the W
 
 As our [Network Map](https://www.cloudflare.com/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the server you are connecting to is not necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-* We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
-* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
-* Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
+- We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
+- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+- Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
 
 ## Does WARP reveal my IP address to websites I visit?
 
@@ -36,7 +35,6 @@ Cloudflare WARP is in part powered by [1.1.1.1](/1.1.1.1/), the world's fastest
 
 Cloudflare WARP and the 1.1.1.1 with WARP applications go through performance testing that includes battery, network and CPU on a regular basis. In addition, both applications are used by millions of users worldwide that help us stay on top of issues across a wide variety of devices, networks, sites and applications.
 
-
 ## What is the version of .NET Framework required for the Windows client?
 
 The WARP client for Windows requires .NET Framework version 4.7.2 or later to be installed on your computer.
diff --git a/src/content/docs/warp-client/legal/3rdparty.mdx b/src/content/docs/warp-client/legal/3rdparty.mdx
index 10a5097703b90b5..26189309784c944 100644
--- a/src/content/docs/warp-client/legal/3rdparty.mdx
+++ b/src/content/docs/warp-client/legal/3rdparty.mdx
@@ -5,14 +5,13 @@ pcx_content_type: reference
 description: Third-party licenses used in the WARP client.
 products:
   - warp-client
-
 ---
 
 Following is the third party license information for our desktop applications. License information for our iOS and Android clients can be found in-app.
 
 ## Windows
 
-* ### NetSparkle
+- ### NetSparkle
 
 Copyright (c) 2020 Deadpikle
 
@@ -20,7 +19,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### Reactive Extensions
+- ### Reactive Extensions
 
 Copyright (c) .NET Foundation and Contributors
 
@@ -28,7 +27,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### NLog
+- ### NLog
 
 Copyright (c) 2016, NLog
 
@@ -40,7 +39,7 @@ Redistribution and use in source and binary forms, with or without modification,
 
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### Visual Studio App Center SDK for .NET
+- ### Visual Studio App Center SDK for .NET
 
 Copyright (c) Microsoft Corporation
 
@@ -50,9 +49,9 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### Font-Awesome-WPF
+- ### Font-Awesome-WPF
 
 Copyright (c) 2014-2016 charri
 
@@ -62,7 +61,7 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### WpfScreenHelper
+- ### WpfScreenHelper
 
 Copyright (c) 2014 Michael Denny
 
@@ -74,7 +73,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ## Mac
 
-* ### Sparkle
+- ### Sparkle
 
 Copyright (c) 2006-2013 Andy Matuschak.
 Copyright (c) 2009-2013 Elgato Systems GmbH.
@@ -89,7 +88,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### ITSwitch
+- ### ITSwitch
 
 Copyright 2014 Ilija Tovilo
 
@@ -99,7 +98,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-* ### Visual Studio App Center SDK for Apple platforms
+- ### Visual Studio App Center SDK for Apple platforms
 
 Copyright (c) Microsoft Corporation
 
@@ -109,7 +108,7 @@ MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ## Rust
 
@@ -119,22 +118,21 @@ This section lists the licenses of the projects used in cargo-about.
 
 Overview of licenses:
 
-* [MIT](#mit-license) (54)
-* [Apache](#apache-license-20) (41)
-* [BSD](#bsd-3-clause-new-or-revised-license) (8)
-* [BSD](#bsd-2-clause-simplified-license) (3)
-* [ISC](#isc-license) (3)
-* [BSD](#bsd-zero-clause-license) (2)
-* [Mozilla](#mozilla-public-license-20) (2)
-* [OpenSSL](#openssl-license) (1)
+- [MIT](#mit-license) (54)
+- [Apache](#apache-license-20) (41)
+- [BSD](#bsd-3-clause-new-or-revised-license) (8)
+- [BSD](#bsd-2-clause-simplified-license) (3)
+- [ISC](#isc-license) (3)
+- [BSD](#bsd-zero-clause-license) (2)
+- [Mozilla](#mozilla-public-license-20) (2)
+- [OpenSSL](#openssl-license) (1)
 
 All license text:
 
-* ### BSD Zero Clause License
+- ### BSD Zero Clause License
 
   #### Used by:
-
-  * [managed](https://github.com/m-labs/rust-managed.git)
+  - [managed](https://github.com/m-labs/rust-managed.git)
 
   Copyright (C) 2017 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -149,11 +147,10 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### BSD Zero Clause License
+- ### BSD Zero Clause License
 
   #### Used by:
-
-  * [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
+  - [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
 
   Copyright (C) 2016 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -168,136 +165,135 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [addr](https://github.com/addr-rs/addr)
-  * [addr2line](https://github.com/gimli-rs/addr2line)
-  * [anyhow](https://github.com/dtolnay/anyhow)
-  * [arc-swap](https://github.com/vorner/arc-swap)
-  * [async-trait](https://github.com/dtolnay/async-trait)
-  * [autocfg](https://github.com/cuviper/autocfg)
-  * [backoff](https://github.com/ihrwein/backoff)
-  * [backtrace](https://github.com/rust-lang/backtrace-rs)
-  * [base64](https://github.com/marshallpierce/rust-base64)
-  * [bitflags](https://github.com/bitflags/bitflags)
-  * [bumpalo](https://github.com/fitzgen/bumpalo)
-  * [bzip2](https://github.com/alexcrichton/bzip2-rs)
-  * [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
-  * [cache-padded](https://github.com/stjepang/cache-padded)
-  * [cc](https://github.com/alexcrichton/cc-rs)
-  * [cfg-if](https://github.com/alexcrichton/cfg-if)
-  * [concurrent-queue](https://github.com/stjepang/concurrent-queue)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
-  * [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
-  * [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
-  * [ct-logs](https://github.com/ctz/ct-logs)
-  * [either](https://github.com/bluss/either)
-  * [errno](https://github.com/lambda-fairy/rust-errno)
-  * [error-chain](https://github.com/rust-lang-nursery/error-chain)
-  * [event-listener](https://github.com/stjepang/event-listener)
-  * [flate2](https://github.com/rust-lang/flate2-rs)
-  * [fnv](https://github.com/servo/rust-fnv)
-  * [form\_urlencoded](https://github.com/servo/rust-url)
-  * [gcc](https://github.com/alexcrichton/gcc-rs)
-  * [getopts](https://github.com/rust-lang/getopts)
-  * [gimli](https://github.com/gimli-rs/gimli)
-  * [hashbrown](https://github.com/rust-lang/hashbrown)
-  * [heck](https://github.com/withoutboats/heck)
-  * [hermit-abi](https://github.com/hermitcore/libhermit-rs)
-  * [httparse](https://github.com/seanmonstar/httparse)
-  * [hyper-rustls](https://github.com/ctz/hyper-rustls)
-  * [idna](https://github.com/servo/rust-url/)
-  * [indexmap](https://github.com/bluss/indexmap)
-  * [itoa](https://github.com/dtolnay/itoa)
-  * [jni](https://github.com/jni-rs/jni-rs)
-  * [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
-  * [lazy\_static](https://github.com/rust-lang-nursery/lazy-static.rs)
-  * [libc](https://github.com/rust-lang/libc)
-  * [lock\_api](https://github.com/Amanieu/parking_lot)
-  * [match\_cfg](https://github.com/gnzlbg/match_cfg)
-  * [mime](https://github.com/hyperium/mime)
-  * [miow](https://github.com/yoshuawuyts/miow)
-  * [num](https://github.com/rust-num/num)
-  * [num](https://github.com/rust-num/num)
-  * [num-bigint](https://github.com/rust-num/num-bigint)
-  * [num-complex](https://github.com/rust-num/num-complex)
-  * [num-complex](https://github.com/rust-num/num-complex)
-  * [num-integer](https://github.com/rust-num/num-integer)
-  * [num-iter](https://github.com/rust-num/num-iter)
-  * [num-rational](https://github.com/rust-num/num-rational)
-  * [num-rational](https://github.com/rust-num/num-rational)
-  * [num-traits](https://github.com/rust-num/num-traits)
-  * [num\_cpus](https://github.com/seanmonstar/num_cpus)
-  * [object](https://github.com/gimli-rs/object)
-  * [once\_cell](https://github.com/matklad/once_cell)
-  * [openssl-probe](https://github.com/alexcrichton/openssl-probe)
-  * [parking\_lot](https://github.com/Amanieu/parking_lot)
-  * [parking\_lot\_core](https://github.com/Amanieu/parking_lot)
-  * [paste](https://github.com/dtolnay/paste)
-  * [percent-encoding](https://github.com/servo/rust-url/)
-  * [pfctl](https://github.com/mullvad/pfctl-rs)
-  * [pkg-config](https://github.com/rust-lang/pkg-config-rs)
-  * [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
-  * [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
-  * [proc-macro2](https://github.com/alexcrichton/proc-macro2)
-  * [quote](https://github.com/dtolnay/quote)
-  * [regex](https://github.com/rust-lang/regex)
-  * [regex-syntax](https://github.com/rust-lang/regex)
-  * [reqwest](https://github.com/seanmonstar/reqwest)
-  * [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
-  * [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
-  * [rustversion](https://github.com/dtolnay/rustversion)
-  * [scopeguard](https://github.com/bluss/scopeguard)
-  * [sct](https://github.com/ctz/sct.rs)
-  * [secret-service](https://github.com/hwchen/secret-service-rs.git)
-  * [semver](https://github.com/dtolnay/semver)
-  * [serde](https://github.com/serde-rs/serde)
-  * [serde\_derive](https://github.com/serde-rs/serde)
-  * [serde\_json](https://github.com/serde-rs/json)
-  * [serde\_repr](https://github.com/dtolnay/serde-repr)
-  * [signal-hook-registry](https://github.com/vorner/signal-hook)
-  * [size\_format](https://github.com/aticu/size_format)
-  * [slog](https://github.com/slog-rs/slog)
-  * [slog-async](https://github.com/slog-rs/async)
-  * [slog-scope](https://github.com/slog-rs/scope)
-  * [slog-stdlog](https://github.com/slog-rs/stdlog)
-  * [slog-term](https://github.com/slog-rs/term)
-  * [smallvec](https://github.com/servo/rust-smallvec)
-  * [socket2](https://github.com/alexcrichton/socket2-rs)
-  * [socket2](https://github.com/rust-lang/socket2)
-  * [syn](https://github.com/dtolnay/syn)
-  * [tempfile](https://github.com/Stebalien/tempfile)
-  * [term](https://github.com/Stebalien/term)
-  * [thiserror](https://github.com/dtolnay/thiserror)
-  * [thiserror-impl](https://github.com/dtolnay/thiserror)
-  * [thread\_local](https://github.com/Amanieu/thread_local-rs)
-  * [time](https://github.com/time-rs/time)
-  * [toml](https://github.com/alexcrichton/toml-rs)
-  * [tungstenite](https://github.com/snapview/tungstenite-rs)
-  * [unicode-bidi](https://github.com/servo/unicode-bidi)
-  * [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
-  * [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
-  * [unicode-width](https://github.com/unicode-rs/unicode-width)
-  * [unicode-xid](https://github.com/unicode-rs/unicode-xid)
-  * [url](https://github.com/servo/rust-url)
-  * [version\_check](https://github.com/SergioBenitez/version_check)
-  * [wasi](https://github.com/bytecodealliance/wasi)
-  * [wasi](https://github.com/bytecodealliance/wasi)
-  * [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
-  * [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
-  * [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
-  * [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
-  * [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
-  * [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
-  * [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
+  - [addr](https://github.com/addr-rs/addr)
+  - [addr2line](https://github.com/gimli-rs/addr2line)
+  - [anyhow](https://github.com/dtolnay/anyhow)
+  - [arc-swap](https://github.com/vorner/arc-swap)
+  - [async-trait](https://github.com/dtolnay/async-trait)
+  - [autocfg](https://github.com/cuviper/autocfg)
+  - [backoff](https://github.com/ihrwein/backoff)
+  - [backtrace](https://github.com/rust-lang/backtrace-rs)
+  - [base64](https://github.com/marshallpierce/rust-base64)
+  - [bitflags](https://github.com/bitflags/bitflags)
+  - [bumpalo](https://github.com/fitzgen/bumpalo)
+  - [bzip2](https://github.com/alexcrichton/bzip2-rs)
+  - [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
+  - [cache-padded](https://github.com/stjepang/cache-padded)
+  - [cc](https://github.com/alexcrichton/cc-rs)
+  - [cfg-if](https://github.com/alexcrichton/cfg-if)
+  - [concurrent-queue](https://github.com/stjepang/concurrent-queue)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
+  - [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
+  - [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
+  - [ct-logs](https://github.com/ctz/ct-logs)
+  - [either](https://github.com/bluss/either)
+  - [errno](https://github.com/lambda-fairy/rust-errno)
+  - [error-chain](https://github.com/rust-lang-nursery/error-chain)
+  - [event-listener](https://github.com/stjepang/event-listener)
+  - [flate2](https://github.com/rust-lang/flate2-rs)
+  - [fnv](https://github.com/servo/rust-fnv)
+  - [form_urlencoded](https://github.com/servo/rust-url)
+  - [gcc](https://github.com/alexcrichton/gcc-rs)
+  - [getopts](https://github.com/rust-lang/getopts)
+  - [gimli](https://github.com/gimli-rs/gimli)
+  - [hashbrown](https://github.com/rust-lang/hashbrown)
+  - [heck](https://github.com/withoutboats/heck)
+  - [hermit-abi](https://github.com/hermitcore/libhermit-rs)
+  - [httparse](https://github.com/seanmonstar/httparse)
+  - [hyper-rustls](https://github.com/ctz/hyper-rustls)
+  - [idna](https://github.com/servo/rust-url/)
+  - [indexmap](https://github.com/bluss/indexmap)
+  - [itoa](https://github.com/dtolnay/itoa)
+  - [jni](https://github.com/jni-rs/jni-rs)
+  - [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
+  - [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs)
+  - [libc](https://github.com/rust-lang/libc)
+  - [lock_api](https://github.com/Amanieu/parking_lot)
+  - [match_cfg](https://github.com/gnzlbg/match_cfg)
+  - [mime](https://github.com/hyperium/mime)
+  - [miow](https://github.com/yoshuawuyts/miow)
+  - [num](https://github.com/rust-num/num)
+  - [num](https://github.com/rust-num/num)
+  - [num-bigint](https://github.com/rust-num/num-bigint)
+  - [num-complex](https://github.com/rust-num/num-complex)
+  - [num-complex](https://github.com/rust-num/num-complex)
+  - [num-integer](https://github.com/rust-num/num-integer)
+  - [num-iter](https://github.com/rust-num/num-iter)
+  - [num-rational](https://github.com/rust-num/num-rational)
+  - [num-rational](https://github.com/rust-num/num-rational)
+  - [num-traits](https://github.com/rust-num/num-traits)
+  - [num_cpus](https://github.com/seanmonstar/num_cpus)
+  - [object](https://github.com/gimli-rs/object)
+  - [once_cell](https://github.com/matklad/once_cell)
+  - [openssl-probe](https://github.com/alexcrichton/openssl-probe)
+  - [parking_lot](https://github.com/Amanieu/parking_lot)
+  - [parking_lot_core](https://github.com/Amanieu/parking_lot)
+  - [paste](https://github.com/dtolnay/paste)
+  - [percent-encoding](https://github.com/servo/rust-url/)
+  - [pfctl](https://github.com/mullvad/pfctl-rs)
+  - [pkg-config](https://github.com/rust-lang/pkg-config-rs)
+  - [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
+  - [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
+  - [proc-macro2](https://github.com/alexcrichton/proc-macro2)
+  - [quote](https://github.com/dtolnay/quote)
+  - [regex](https://github.com/rust-lang/regex)
+  - [regex-syntax](https://github.com/rust-lang/regex)
+  - [reqwest](https://github.com/seanmonstar/reqwest)
+  - [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
+  - [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
+  - [rustversion](https://github.com/dtolnay/rustversion)
+  - [scopeguard](https://github.com/bluss/scopeguard)
+  - [sct](https://github.com/ctz/sct.rs)
+  - [secret-service](https://github.com/hwchen/secret-service-rs.git)
+  - [semver](https://github.com/dtolnay/semver)
+  - [serde](https://github.com/serde-rs/serde)
+  - [serde_derive](https://github.com/serde-rs/serde)
+  - [serde_json](https://github.com/serde-rs/json)
+  - [serde_repr](https://github.com/dtolnay/serde-repr)
+  - [signal-hook-registry](https://github.com/vorner/signal-hook)
+  - [size_format](https://github.com/aticu/size_format)
+  - [slog](https://github.com/slog-rs/slog)
+  - [slog-async](https://github.com/slog-rs/async)
+  - [slog-scope](https://github.com/slog-rs/scope)
+  - [slog-stdlog](https://github.com/slog-rs/stdlog)
+  - [slog-term](https://github.com/slog-rs/term)
+  - [smallvec](https://github.com/servo/rust-smallvec)
+  - [socket2](https://github.com/alexcrichton/socket2-rs)
+  - [socket2](https://github.com/rust-lang/socket2)
+  - [syn](https://github.com/dtolnay/syn)
+  - [tempfile](https://github.com/Stebalien/tempfile)
+  - [term](https://github.com/Stebalien/term)
+  - [thiserror](https://github.com/dtolnay/thiserror)
+  - [thiserror-impl](https://github.com/dtolnay/thiserror)
+  - [thread_local](https://github.com/Amanieu/thread_local-rs)
+  - [time](https://github.com/time-rs/time)
+  - [toml](https://github.com/alexcrichton/toml-rs)
+  - [tungstenite](https://github.com/snapview/tungstenite-rs)
+  - [unicode-bidi](https://github.com/servo/unicode-bidi)
+  - [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
+  - [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
+  - [unicode-width](https://github.com/unicode-rs/unicode-width)
+  - [unicode-xid](https://github.com/unicode-rs/unicode-xid)
+  - [url](https://github.com/servo/rust-url)
+  - [version_check](https://github.com/SergioBenitez/version_check)
+  - [wasi](https://github.com/bytecodealliance/wasi)
+  - [wasi](https://github.com/bytecodealliance/wasi)
+  - [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
+  - [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
+  - [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
+  - [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
+  - [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
+  - [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
+  - [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
 
     ```
                           Apache License
@@ -306,7 +302,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -505,11 +500,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [adler](https://github.com/jonas-schievink/adler.git)
+  - [adler](https://github.com/jonas-schievink/adler.git)
 
     ```
                           Apache License
@@ -518,7 +512,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -717,33 +710,32 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [aes](https://github.com/RustCrypto/block-ciphers)
-  * [aes-soft](https://github.com/RustCrypto/block-ciphers)
-  * [aesni](https://github.com/RustCrypto/block-ciphers)
-  * [block-buffer](https://github.com/RustCrypto/utils)
-  * [block-buffer](https://github.com/RustCrypto/utils)
-  * [block-modes](https://github.com/RustCrypto/block-ciphers)
-  * [block-padding](https://github.com/RustCrypto/utils)
-  * [block-padding](https://github.com/RustCrypto/utils)
-  * [byte-tools](https://github.com/RustCrypto/utils)
-  * [cipher](https://github.com/RustCrypto/traits)
-  * [cpufeatures](https://github.com/RustCrypto/utils)
-  * [crypto-mac](https://github.com/RustCrypto/traits)
-  * [crypto-mac](https://github.com/RustCrypto/traits)
-  * [digest](https://github.com/RustCrypto/traits)
-  * [digest](https://github.com/RustCrypto/traits)
-  * [fake-simd](https://github.com/RustCrypto/utils)
-  * [hmac](https://github.com/RustCrypto/MACs)
-  * [hmac](https://github.com/RustCrypto/MACs)
-  * [opaque-debug](https://github.com/RustCrypto/utils)
-  * [opaque-debug](https://github.com/RustCrypto/utils)
-  * [sha-1](https://github.com/RustCrypto/hashes)
-  * [sha2](https://github.com/RustCrypto/hashes)
-  * [sha2](https://github.com/RustCrypto/hashes)
+  - [aes](https://github.com/RustCrypto/block-ciphers)
+  - [aes-soft](https://github.com/RustCrypto/block-ciphers)
+  - [aesni](https://github.com/RustCrypto/block-ciphers)
+  - [block-buffer](https://github.com/RustCrypto/utils)
+  - [block-buffer](https://github.com/RustCrypto/utils)
+  - [block-modes](https://github.com/RustCrypto/block-ciphers)
+  - [block-padding](https://github.com/RustCrypto/utils)
+  - [block-padding](https://github.com/RustCrypto/utils)
+  - [byte-tools](https://github.com/RustCrypto/utils)
+  - [cipher](https://github.com/RustCrypto/traits)
+  - [cpufeatures](https://github.com/RustCrypto/utils)
+  - [crypto-mac](https://github.com/RustCrypto/traits)
+  - [crypto-mac](https://github.com/RustCrypto/traits)
+  - [digest](https://github.com/RustCrypto/traits)
+  - [digest](https://github.com/RustCrypto/traits)
+  - [fake-simd](https://github.com/RustCrypto/utils)
+  - [hmac](https://github.com/RustCrypto/MACs)
+  - [hmac](https://github.com/RustCrypto/MACs)
+  - [opaque-debug](https://github.com/RustCrypto/utils)
+  - [opaque-debug](https://github.com/RustCrypto/utils)
+  - [sha-1](https://github.com/RustCrypto/hashes)
+  - [sha2](https://github.com/RustCrypto/hashes)
+  - [sha2](https://github.com/RustCrypto/hashes)
 
     ```
                           Apache License
@@ -752,7 +744,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -949,18 +940,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ascii](https://github.com/tomprogrammer/rust-ascii)
+  - [ascii](https://github.com/tomprogrammer/rust-ascii)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1161,15 +1150,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [async-channel](https://github.com/smol-rs/async-channel)
-  * [ipconfig](https://github.com/liranringel/ipconfig)
-  * [log](https://github.com/rust-lang/log)
-  * [safemem](https://github.com/abonander/safemem)
-  * [uuid](https://github.com/uuid-rs/uuid)
+  - [async-channel](https://github.com/smol-rs/async-channel)
+  - [ipconfig](https://github.com/liranringel/ipconfig)
+  - [log](https://github.com/rust-lang/log)
+  - [safemem](https://github.com/abonander/safemem)
+  - [uuid](https://github.com/uuid-rs/uuid)
 
     ```
                           Apache License
@@ -1178,7 +1166,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1377,32 +1364,30 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [cesu8](https://github.com/emk/cesu8-rs)
-  * [ident\_case](https://github.com/TedDriggs/ident_case)
-  * [ioctl-sys](https://github.com/jmesmon/ioctl)
-  * [psl](https://github.com/addr-rs/psl)
-  * [psl-types](https://github.com/addr-rs/psl-types)
-  * [rustls](https://github.com/ctz/rustls)
-  * [security-framework](https://github.com/kornelski/rust-security-framework)
-  * [security-framework](https://github.com/kornelski/rust-security-framework)
-  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  * [system-configuration](https://github.com/mullvad/system-configuration-rs)
-  * [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
-  * [tinyvec\_macros](https://github.com/Soveu/tinyvec_macros)
-  * [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
-  * [winapi-x86\_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  - [cesu8](https://github.com/emk/cesu8-rs)
+  - [ident_case](https://github.com/TedDriggs/ident_case)
+  - [ioctl-sys](https://github.com/jmesmon/ioctl)
+  - [psl](https://github.com/addr-rs/psl)
+  - [psl-types](https://github.com/addr-rs/psl-types)
+  - [rustls](https://github.com/ctz/rustls)
+  - [security-framework](https://github.com/kornelski/rust-security-framework)
+  - [security-framework](https://github.com/kornelski/rust-security-framework)
+  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  - [system-configuration](https://github.com/mullvad/system-configuration-rs)
+  - [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
+  - [tinyvec_macros](https://github.com/Soveu/tinyvec_macros)
+  - [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  - [winapi-x86_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
@@ -1424,7 +1409,6 @@ All license text:
   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
 
   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
-
   2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
 
   3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
@@ -1471,11 +1455,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [chrono](https://github.com/chronotope/chrono)
+  - [chrono](https://github.com/chronotope/chrono)
 
   Rust-chrono is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2]. Copyright (c) 2014--2017, Kang Seonghoon and
@@ -1715,24 +1698,23 @@ All license text:
   limitations under the License.
   ```
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [crc32fast](https://github.com/srijs/rust-crc32fast)
-  * [derive\_builder](https://github.com/colin-kiegel/rust-derive-builder)
-  * [derive\_builder\_core](https://github.com/colin-kiegel/rust-derive-builder)
-  * [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
-  * [hex](https://github.com/KokaKiwi/rust-hex)
-  * [jni-sys](https://github.com/sfackler/rust-jni-sys)
-  * [log-panics](https://github.com/sfackler/rust-log-panics)
-  * [quick-error](http://github.com/tailhook/quick-error)
-  * [resolv-conf](http://github.com/tailhook/resolv-conf)
-  * [trust-dns-https](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
-  * [unreachable](https://github.com/reem/rust-unreachable.git)
+  - [crc32fast](https://github.com/srijs/rust-crc32fast)
+  - [derive_builder](https://github.com/colin-kiegel/rust-derive-builder)
+  - [derive_builder_core](https://github.com/colin-kiegel/rust-derive-builder)
+  - [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
+  - [hex](https://github.com/KokaKiwi/rust-hex)
+  - [jni-sys](https://github.com/sfackler/rust-jni-sys)
+  - [log-panics](https://github.com/sfackler/rust-log-panics)
+  - [quick-error](http://github.com/tailhook/quick-error)
+  - [resolv-conf](http://github.com/tailhook/resolv-conf)
+  - [trust-dns-https](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
+  - [unreachable](https://github.com/reem/rust-unreachable.git)
 
     ```
                              Apache License
@@ -1741,7 +1723,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1942,18 +1923,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dbus](https://github.com/diwic/dbus-rs)
+  - [dbus](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2154,19 +2133,17 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dbus](https://github.com/diwic/dbus-rs)
-  * [libdbus-sys](https://github.com/diwic/dbus-rs)
+  - [dbus](https://github.com/diwic/dbus-rs)
+  - [libdbus-sys](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2367,11 +2344,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [deadqueue](https://github.com/bikeshedder/deadqueue)
+  - [deadqueue](https://github.com/bikeshedder/deadqueue)
 
     ```
                              Apache License
@@ -2380,7 +2356,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2581,13 +2556,12 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [diff](https://github.com/utkarshkukreti/diff.rs)
-  * [ipnetwork](https://github.com/achanda/ipnetwork)
-  * [winapi](https://github.com/retep998/winapi-rs)
+  - [diff](https://github.com/utkarshkukreti/diff.rs)
+  - [ipnetwork](https://github.com/achanda/ipnetwork)
+  - [winapi](https://github.com/retep998/winapi-rs)
 
     ```
                              Apache License
@@ -2596,7 +2570,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2797,14 +2770,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dirs](https://github.com/soc/dirs-rs)
-  * [dirs-next](https://github.com/xdg-rs/dirs)
-  * [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
-  * [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
+  - [dirs](https://github.com/soc/dirs-rs)
+  - [dirs-next](https://github.com/xdg-rs/dirs)
+  - [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
+  - [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
 
     ```
                           Apache License
@@ -2813,7 +2785,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2983,12 +2954,11 @@ All license text:
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [encoding\_rs](https://github.com/hsivonen/encoding_rs)
-  * [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
+  - [encoding_rs](https://github.com/hsivonen/encoding_rs)
+  - [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
 
     ```
                              Apache License
@@ -2997,7 +2967,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3198,11 +3167,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [err-derive](https://gitlab.com/torkleyy/err-derive)
+  - [err-derive](https://gitlab.com/torkleyy/err-derive)
 
     ```
                              Apache License
@@ -3211,7 +3179,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3412,19 +3379,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [futures](https://github.com/rust-lang/futures-rs)
-  * [futures-channel](https://github.com/rust-lang/futures-rs)
-  * [futures-core](https://github.com/rust-lang/futures-rs)
-  * [futures-executor](https://github.com/rust-lang/futures-rs)
-  * [futures-io](https://github.com/rust-lang/futures-rs)
-  * [futures-macro](https://github.com/rust-lang/futures-rs)
-  * [futures-sink](https://github.com/rust-lang/futures-rs)
-  * [futures-task](https://github.com/rust-lang/futures-rs)
-  * [futures-util](https://github.com/rust-lang/futures-rs)
+  - [futures](https://github.com/rust-lang/futures-rs)
+  - [futures-channel](https://github.com/rust-lang/futures-rs)
+  - [futures-core](https://github.com/rust-lang/futures-rs)
+  - [futures-executor](https://github.com/rust-lang/futures-rs)
+  - [futures-io](https://github.com/rust-lang/futures-rs)
+  - [futures-macro](https://github.com/rust-lang/futures-rs)
+  - [futures-sink](https://github.com/rust-lang/futures-rs)
+  - [futures-task](https://github.com/rust-lang/futures-rs)
+  - [futures-util](https://github.com/rust-lang/futures-rs)
 
     ```
                           Apache License
@@ -3433,7 +3399,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3633,20 +3598,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [getrandom](https://github.com/rust-random/getrandom)
-  * [getrandom](https://github.com/rust-random/getrandom)
-  * [rand](https://github.com/rust-random/rand)
-  * [rand](https://github.com/rust-random/rand)
-  * [rand\_chacha](https://github.com/rust-random/rand)
-  * [rand\_chacha](https://github.com/rust-random/rand)
-  * [rand\_core](https://github.com/rust-random/rand)
-  * [rand\_core](https://github.com/rust-random/rand)
-  * [rand\_hc](https://github.com/rust-random/rand)
-  * [rand\_hc](https://github.com/rust-random/rand)
+  - [getrandom](https://github.com/rust-random/getrandom)
+  - [getrandom](https://github.com/rust-random/getrandom)
+  - [rand](https://github.com/rust-random/rand)
+  - [rand](https://github.com/rust-random/rand)
+  - [rand_chacha](https://github.com/rust-random/rand)
+  - [rand_chacha](https://github.com/rust-random/rand)
+  - [rand_core](https://github.com/rust-random/rand)
+  - [rand_core](https://github.com/rust-random/rand)
+  - [rand_hc](https://github.com/rust-random/rand)
+  - [rand_hc](https://github.com/rust-random/rand)
 
     ```
                           Apache License
@@ -3655,7 +3619,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3854,11 +3817,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [hkdf](https://github.com/RustCrypto/KDFs/)
+  - [hkdf](https://github.com/RustCrypto/KDFs/)
 
     ```
                           Apache License
@@ -3867,7 +3829,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4064,11 +4025,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [http](https://github.com/hyperium/http)
+  - [http](https://github.com/hyperium/http)
 
     ```
                           Apache License
@@ -4077,7 +4037,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4276,18 +4235,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [httpdate](https://github.com/pyfisch/httpdate)
+  - [httpdate](https://github.com/pyfisch/httpdate)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction,
@@ -4346,7 +4303,6 @@ All license text:
   "Contributor" shall mean Licensor and any individual or Legal Entity
   on behalf of whom a Contribution has been received by Licensor and
   subsequently incorporated within the Work.
-
   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
@@ -4410,7 +4366,6 @@ All license text:
   for any such Derivative Works as a whole, provided Your use,
   reproduction, and distribution of the Work otherwise complies with
   the conditions stated in this License.
-
   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
@@ -4484,11 +4439,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
+  - [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
 
     ```
                              Apache License
@@ -4497,7 +4451,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4699,11 +4652,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ipnet](https://github.com/krisprice/ipnet)
+  - [ipnet](https://github.com/krisprice/ipnet)
 
     ```
                              Apache License
@@ -4712,7 +4664,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4913,11 +4864,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [keyring](https://github.com/hwchen/keyring-rs.git)
+  - [keyring](https://github.com/hwchen/keyring-rs.git)
 
     ```
                           Apache License
@@ -4926,7 +4876,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5125,14 +5074,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
-  * [lru-cache](https://github.com/contain-rs/lru-cache)
-  * [process\_path](https://github.com/wesleywiser/process_path)
-  * [vec\_map](https://github.com/contain-rs/vec-map)
+  - [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
+  - [lru-cache](https://github.com/contain-rs/lru-cache)
+  - [process_path](https://github.com/wesleywiser/process_path)
+  - [vec_map](https://github.com/contain-rs/vec-map)
 
     ```
                           Apache License
@@ -5141,7 +5089,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5340,14 +5287,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [miniz\_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
-  * [pin-project](https://github.com/taiki-e/pin-project)
-  * [pin-project-internal](https://github.com/taiki-e/pin-project)
-  * [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
+  - [miniz_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
+  - [pin-project](https://github.com/taiki-e/pin-project)
+  - [pin-project-internal](https://github.com/taiki-e/pin-project)
+  - [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
 
     ```
                              Apache License
@@ -5356,7 +5302,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5528,11 +5473,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ntapi](https://github.com/MSxDOS/ntapi)
+  - [ntapi](https://github.com/MSxDOS/ntapi)
 
     ```
                              Apache License
@@ -5541,7 +5485,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5742,11 +5685,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
+  - [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
 
     ```
                           Apache License
@@ -5755,7 +5697,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5954,11 +5895,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
+  - [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
 
     ```
                           Apache License
@@ -5967,7 +5907,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6164,11 +6103,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
+  - [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6177,7 +6115,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6376,11 +6313,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
+  - [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6389,7 +6325,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6588,11 +6523,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [remove\_dir\_all](https://github.com/XAMPPRocky/remove_dir_all.git)
+  - [remove_dir_all](https://github.com/XAMPPRocky/remove_dir_all.git)
 
     ```
                           Apache License
@@ -6601,7 +6535,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6789,11 +6722,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [rolling-file](https://github.com/Axcient/rolling-file-rs)
+  - [rolling-file](https://github.com/Axcient/rolling-file-rs)
 
   rolling-file is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2].
@@ -7034,11 +6966,10 @@ All license text:
   limitations under the License.
   ```
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ryu](https://github.com/dtolnay/ryu)
+  - [ryu](https://github.com/dtolnay/ryu)
 
     ```
                              Apache License
@@ -7047,7 +6978,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7248,12 +7178,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [serde\_urlencoded](https://github.com/nox/serde_urlencoded)
-  * [utf-8](https://github.com/SimonSapin/rust-utf8)
+  - [serde_urlencoded](https://github.com/nox/serde_urlencoded)
+  - [utf-8](https://github.com/SimonSapin/rust-utf8)
 
     ```
                           Apache License
@@ -7262,7 +7191,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7434,11 +7362,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [tinyvec](https://github.com/Lokathor/tinyvec)
+  - [tinyvec](https://github.com/Lokathor/tinyvec)
 
     ```
                              Apache License
@@ -7447,7 +7374,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7648,11 +7574,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [tokio-rustls](https://github.com/tokio-rs/tls)
+  - [tokio-rustls](https://github.com/tokio-rs/tls)
 
     ```
                           Apache License
@@ -7661,7 +7586,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7860,11 +7784,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [typenum](https://github.com/paholg/typenum)
+  - [typenum](https://github.com/paholg/typenum)
 
     ```
                           Apache License
@@ -7873,7 +7796,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8072,11 +7994,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [webbrowser](https://github.com/amodm/webbrowser-rs)
+  - [webbrowser](https://github.com/amodm/webbrowser-rs)
 
   Copyright (c) 2015 Amod Malviya
 
@@ -8103,7 +8024,6 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8275,11 +8195,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [widestring](https://github.com/starkat99/widestring-rs.git)
+  - [widestring](https://github.com/starkat99/widestring-rs.git)
 
     ```
                           Apache License
@@ -8288,7 +8207,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8487,11 +8405,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [windows-service](https://github.com/mullvad/windows-service-rs)
+  - [windows-service](https://github.com/mullvad/windows-service-rs)
 
     ```
                           Apache License
@@ -8500,7 +8417,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8699,16 +8615,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [winlog](https://gitlab.com/arbitrix/winlog)
+  - [winlog](https://gitlab.com/arbitrix/winlog)
 
   This software is licensed under either of
-
-  * Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
-  * MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
+  - Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+  - MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
 
   at your option.
 
@@ -8719,7 +8633,6 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8942,17 +8855,15 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [ip\_network](https://github.com/JakubOnderka/ip_network)
+  - [ip_network](https://github.com/JakubOnderka/ip_network)
 
   Copyright (c) 2017, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8970,17 +8881,15 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [ip\_network\_table](https://github.com/JakubOnderka/ip_network_table)
+  - [ip_network_table](https://github.com/JakubOnderka/ip_network_table)
 
   Copyright (c) 2018, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8998,19 +8907,17 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [mach](https://github.com/fitzgen/mach)
-  * [mach](https://github.com/fitzgen/mach)
+  - [mach](https://github.com/fitzgen/mach)
+  - [mach](https://github.com/fitzgen/mach)
 
   Copyright (c) 2015, Nick Fitzgerald
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9029,12 +8936,11 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [app-center](https://github.com/vkrasnov/appcenter-rs)
-  * [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
+  - [app-center](https://github.com/vkrasnov/appcenter-rs)
+  - [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
 
   BSD 3-Clause License
 
@@ -9043,7 +8949,6 @@ All license text:
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9066,11 +8971,10 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [boringtun](https://github.com/cloudflare/boringtun)
+  - [boringtun](https://github.com/cloudflare/boringtun)
 
   Copyright (c) 2019 Cloudflare, Inc. All rights reserved.
 
@@ -9084,11 +8988,10 @@ All license text:
 
   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [etherparse](https://github.com/JulianSchmid/etherparse)
+  - [etherparse](https://github.com/JulianSchmid/etherparse)
 
   BSD 3-Clause License
 
@@ -9120,18 +9023,16 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [instant](https://github.com/sebcrozet/instant)
+  - [instant](https://github.com/sebcrozet/instant)
 
   Copyright (c) 2019, Sébastien Crozet
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9154,17 +9055,15 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [nel](https://crates.io/crates/nel/0.1.4)
+  - [nel](https://crates.io/crates/nel/0.1.4)
 
   Copyright 2021 Cloudflare, Inc. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9187,18 +9086,16 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [subtle](https://github.com/dalek-cryptography/subtle)
+  - [subtle](https://github.com/dalek-cryptography/subtle)
 
   Copyright (c) 2016-2017 Isis Agora Lovecruft, Henry de Valence. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
-
   1. Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
 
@@ -9222,11 +9119,10 @@ All license text:
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [webpki](https://github.com/briansmith/webpki)
+  - [webpki](https://github.com/briansmith/webpki)
 
   // Copyright 2015 The Chromium Authors. All rights reserved.
   //
@@ -9256,11 +9152,10 @@ All license text:
   // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   // Copyright 2017 Brian Smith.
   //
@@ -9276,7 +9171,7 @@ All license text:
   // OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
   // CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-  \#\[macro\_use]
+  \#\[macro_use]
   pub mod constant;
 
   \#\[cfg(feature = "alloc")]
@@ -9284,11 +9179,10 @@ All license text:
 
   pub mod montgomery;
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [untrusted](https://github.com/briansmith/untrusted)
+  - [untrusted](https://github.com/briansmith/untrusted)
 
   // Copyright 2015-2016 Brian Smith.
   //
@@ -9304,11 +9198,10 @@ All license text:
   // ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
   // OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [webpki](https://github.com/briansmith/webpki)
+  - [webpki](https://github.com/briansmith/webpki)
 
   Except as otherwise noted, this project is licensed under the following
   (ISC-style) terms:
@@ -9330,15 +9223,14 @@ All license text:
   The files under third-party/chromium are licensed as described in
   third-party/chromium/LICENSE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [aho-corasick](https://github.com/BurntSushi/aho-corasick)
-  * [byteorder](https://github.com/BurntSushi/byteorder)
-  * [memchr](https://github.com/BurntSushi/memchr)
-  * [regex-automata](https://github.com/BurntSushi/regex-automata)
-  * [walkdir](https://github.com/BurntSushi/walkdir)
+  - [aho-corasick](https://github.com/BurntSushi/aho-corasick)
+  - [byteorder](https://github.com/BurntSushi/byteorder)
+  - [memchr](https://github.com/BurntSushi/memchr)
+  - [regex-automata](https://github.com/BurntSushi/regex-automata)
+  - [walkdir](https://github.com/BurntSushi/walkdir)
 
   The MIT License (MIT)
 
@@ -9362,11 +9254,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ansi\_term](https://crates.io/crates/ansi_term)
+  - [ansi_term](https://crates.io/crates/ansi_term)
 
   The MIT License (MIT)
 
@@ -9390,11 +9281,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ansi\_term](https://github.com/ogham/rust-ansi-term)
+  - [ansi_term](https://github.com/ogham/rust-ansi-term)
 
   The MIT License (MIT)
 
@@ -9418,11 +9308,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [atty](https://github.com/softprops/atty)
+  - [atty](https://github.com/softprops/atty)
 
   Copyright (c) 2015-2019 Doug Tangren
 
@@ -9445,11 +9334,10 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [bytes](https://github.com/tokio-rs/bytes)
+  - [bytes](https://github.com/tokio-rs/bytes)
 
   Copyright (c) 2018 Carl Lerche
 
@@ -9477,11 +9365,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [clap](https://github.com/clap-rs/clap)
+  - [clap](https://github.com/clap-rs/clap)
 
   The MIT License (MIT)
 
@@ -9505,11 +9392,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [combine](https://github.com/Marwes/combine)
+  - [combine](https://github.com/Marwes/combine)
 
   The MIT License (MIT)
 
@@ -9533,13 +9419,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [darling](https://github.com/TedDriggs/darling)
-  * [darling\_core](https://github.com/TedDriggs/darling)
-  * [darling\_macro](https://github.com/TedDriggs/darling)
+  - [darling](https://github.com/TedDriggs/darling)
+  - [darling_core](https://github.com/TedDriggs/darling)
+  - [darling_macro](https://github.com/TedDriggs/darling)
 
   MIT License
 
@@ -9563,11 +9448,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [data-encoding](https://github.com/ia0/data-encoding)
+  - [data-encoding](https://github.com/ia0/data-encoding)
 
   The MIT License (MIT)
 
@@ -9592,17 +9476,16 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [dispatch](http://github.com/SSheldon/rust-dispatch)
-  * [netlink-packet-core](https://github.com/little-dude/netlink)
-  * [netlink-packet-route](https://github.com/little-dude/netlink)
-  * [netlink-packet-utils](https://github.com/little-dude/netlink)
-  * [netlink-sys](https://github.com/little-dude/netlink)
-  * [tokio-macros](https://github.com/tokio-rs/tokio)
-  * [void](https://github.com/reem/rust-void.git)
+  - [dispatch](http://github.com/SSheldon/rust-dispatch)
+  - [netlink-packet-core](https://github.com/little-dude/netlink)
+  - [netlink-packet-route](https://github.com/little-dude/netlink)
+  - [netlink-packet-utils](https://github.com/little-dude/netlink)
+  - [netlink-sys](https://github.com/little-dude/netlink)
+  - [tokio-macros](https://github.com/tokio-rs/tokio)
+  - [void](https://github.com/reem/rust-void.git)
 
   MIT License
 
@@ -9612,11 +9495,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
+  - [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
 
   MIT License
 
@@ -9640,11 +9522,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
+  - [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
 
   MIT License
 
@@ -9668,11 +9549,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [generic-array](https://github.com/fizyk20/generic-array.git)
+  - [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9696,11 +9576,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [generic-array](https://github.com/fizyk20/generic-array.git)
+  - [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9724,11 +9603,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [h2](https://github.com/hyperium/h2)
+  - [h2](https://github.com/hyperium/h2)
 
   Copyright (c) 2017 h2 authors
 
@@ -9756,11 +9634,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [hostname](https://github.com/svartalf/hostname)
+  - [hostname](https://github.com/svartalf/hostname)
 
   MIT License
 
@@ -9785,11 +9662,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [http-body](https://github.com/hyperium/http-body)
+  - [http-body](https://github.com/hyperium/http-body)
 
   Copyright (c) 2019 Hyper Contributors
 
@@ -9817,11 +9693,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [hyper](https://github.com/hyperium/hyper)
+  - [hyper](https://github.com/hyperium/hyper)
 
   Copyright (c) 2014-2021 Sean McArthur
 
@@ -9843,11 +9718,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ip\_network\_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
+  - [ip_network_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
 
   Copyright (c) 2016 Hroi Sigurdsson
 
@@ -9875,11 +9749,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [iprange](https://github.com/sticnarf/iprange-rs)
+  - [iprange](https://github.com/sticnarf/iprange-rs)
 
   MIT License
 
@@ -9903,11 +9776,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
+  - [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
 
   The MIT License
 
@@ -9930,11 +9802,10 @@ All license text:
   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [matchers](https://github.com/hawkw/matchers)
+  - [matchers](https://github.com/hawkw/matchers)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -9956,11 +9827,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [matches](https://github.com/SimonSapin/rust-std-candidates)
+  - [matches](https://github.com/SimonSapin/rust-std-candidates)
 
   Copyright (c) 2014-2016 Simon Sapin
 
@@ -9988,11 +9858,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [memoffset](https://github.com/Gilnaa/memoffset)
+  - [memoffset](https://github.com/Gilnaa/memoffset)
 
   Copyright (c) 2017 Gilad Naaman
 
@@ -10014,11 +9883,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [mio](https://github.com/tokio-rs/mio)
+  - [mio](https://github.com/tokio-rs/mio)
 
   Copyright (c) 2014 Carl Lerche and other MIO contributors
 
@@ -10040,11 +9908,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [nix](https://github.com/nix-rust/nix)
+  - [nix](https://github.com/nix-rust/nix)
 
   The MIT License (MIT)
 
@@ -10068,11 +9935,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [plist](https://github.com/ebarnard/rust-plist/)
+  - [plist](https://github.com/ebarnard/rust-plist/)
 
   Copyright (c) 2015 Edward Barnard
 
@@ -10094,11 +9960,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [powershell\_script](https://github.com/cfsamson/powershell-script)
+  - [powershell_script](https://github.com/cfsamson/powershell-script)
 
   The MIT License (MIT)
 
@@ -10110,11 +9975,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [redox\_syscall](https://gitlab.redox-os.org/redox-os/syscall)
+  - [redox_syscall](https://gitlab.redox-os.org/redox-os/syscall)
 
   Copyright (c) 2017 Redox OS Developers
 
@@ -10139,11 +10003,10 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [redox\_users](https://gitlab.redox-os.org/redox-os/users)
+  - [redox_users](https://gitlab.redox-os.org/redox-os/users)
 
   The MIT License (MIT)
 
@@ -10167,11 +10030,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   The MIT License (MIT)
 
@@ -10196,12 +10058,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [same-file](https://github.com/BurntSushi/same-file)
-  * [winapi-util](https://github.com/BurntSushi/winapi-util)
+  - [same-file](https://github.com/BurntSushi/same-file)
+  - [winapi-util](https://github.com/BurntSushi/winapi-util)
 
   The MIT License (MIT)
 
@@ -10225,11 +10086,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [schannel](https://github.com/steffengy/schannel-rs)
+  - [schannel](https://github.com/steffengy/schannel-rs)
 
   Copyright (c) 2015 steffengy
 
@@ -10239,11 +10099,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
+  - [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
 
   MIT License
 
@@ -10267,11 +10126,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sharded-slab](https://github.com/hawkw/sharded-slab)
+  - [sharded-slab](https://github.com/hawkw/sharded-slab)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -10293,11 +10151,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [slab](https://github.com/tokio-rs/slab)
+  - [slab](https://github.com/tokio-rs/slab)
 
   Copyright (c) 2019 Carl Lerche
 
@@ -10325,11 +10182,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [smbios-lib](https://github.com/jrgerber/smbios-lib)
+  - [smbios-lib](https://github.com/jrgerber/smbios-lib)
 
   MIT License
 
@@ -10353,12 +10209,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [spin](https://github.com/mvdnes/spin-rs.git)
-  * [zip](https://github.com/zip-rs/zip.git)
+  - [spin](https://github.com/mvdnes/spin-rs.git)
+  - [zip](https://github.com/zip-rs/zip.git)
 
   The MIT License (MIT)
 
@@ -10382,12 +10237,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [strsim](https://github.com/dguo/strsim-rs)
-  * [strsim](https://github.com/dguo/strsim-rs)
+  - [strsim](https://github.com/dguo/strsim-rs)
+  - [strsim](https://github.com/dguo/strsim-rs)
 
   The MIT License (MIT)
 
@@ -10412,11 +10266,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [synstructure](https://github.com/mystor/synstructure)
+  - [synstructure](https://github.com/mystor/synstructure)
 
   Copyright 2016 Nika Layzell
 
@@ -10426,11 +10279,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sys-info](https://github.com/FillZpp/sys-info-rs)
+  - [sys-info](https://github.com/FillZpp/sys-info-rs)
 
   The MIT License (MIT)
 
@@ -10454,11 +10306,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
+  - [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
 
   The MIT License (MIT)
 
@@ -10482,11 +10333,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [take\_mut](https://github.com/Sgeo/take_mut)
+  - [take_mut](https://github.com/Sgeo/take_mut)
 
   The MIT License (MIT)
 
@@ -10510,11 +10360,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [textwrap](https://github.com/mgeisler/textwrap)
+  - [textwrap](https://github.com/mgeisler/textwrap)
 
   MIT License
 
@@ -10538,12 +10387,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tokio](https://github.com/tokio-rs/tokio)
-  * [tokio-util](https://github.com/tokio-rs/tokio)
+  - [tokio](https://github.com/tokio-rs/tokio)
+  - [tokio-util](https://github.com/tokio-rs/tokio)
 
   Copyright (c) 2021 Tokio Contributors
 
@@ -10571,11 +10419,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
+  - [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
 
   Copyright (c) 2017 Daniel Abramov
   Copyright (c) 2017 Alexey Galakhov
@@ -10598,11 +10445,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [totp-lite](https://github.com/fosskers/totp-lite)
+  - [totp-lite](https://github.com/fosskers/totp-lite)
 
   MIT License
 
@@ -10626,11 +10472,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tower-service](https://github.com/tower-rs/tower)
+  - [tower-service](https://github.com/tower-rs/tower)
 
   Copyright (c) 2019 Tower Contributors
 
@@ -10658,17 +10503,16 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tracing](https://github.com/tokio-rs/tracing)
-  * [tracing-appender](https://github.com/tokio-rs/tracing)
-  * [tracing-attributes](https://github.com/tokio-rs/tracing)
-  * [tracing-core](https://github.com/tokio-rs/tracing)
-  * [tracing-log](https://github.com/tokio-rs/tracing)
-  * [tracing-serde](https://github.com/tokio-rs/tracing)
-  * [tracing-subscriber](https://github.com/tokio-rs/tracing)
+  - [tracing](https://github.com/tokio-rs/tracing)
+  - [tracing-appender](https://github.com/tokio-rs/tracing)
+  - [tracing-attributes](https://github.com/tokio-rs/tracing)
+  - [tracing-core](https://github.com/tokio-rs/tracing)
+  - [tracing-log](https://github.com/tokio-rs/tracing)
+  - [tracing-serde](https://github.com/tokio-rs/tracing)
+  - [tracing-subscriber](https://github.com/tokio-rs/tracing)
 
   Copyright (c) 2019 Tokio Contributors
 
@@ -10696,11 +10540,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [try-lock](https://github.com/seanmonstar/try-lock)
+  - [try-lock](https://github.com/seanmonstar/try-lock)
 
   Copyright (c) 2018 Sean McArthur
   Copyright (c) 2016 Alex Crichton
@@ -10723,11 +10566,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [want](https://github.com/seanmonstar/want)
+  - [want](https://github.com/seanmonstar/want)
 
   Copyright (c) 2018-2019 Sean McArthur
 
@@ -10749,13 +10591,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [winreg](https://github.com/gentoo90/winreg-rs)
-  * [winreg](https://github.com/gentoo90/winreg-rs)
-  * [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
 
   Copyright (c) 2015 Igor Shaula
 
@@ -10777,11 +10618,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [winres](https://github.com/mxre/winres)
+  - [winres](https://github.com/mxre/winres)
 
   Copyright 2016 Max Resch
 
@@ -10809,11 +10649,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [xml-rs](https://github.com/netvl/xml-rs)
+  - [xml-rs](https://github.com/netvl/xml-rs)
 
   The MIT License (MIT)
 
@@ -10837,12 +10676,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### Mozilla Public License 2.0
+- ### Mozilla Public License 2.0
 
   #### Used by:
-
-  * [cbindgen](https://github.com/eqrion/cbindgen/)
-
+  - [cbindgen](https://github.com/eqrion/cbindgen/)
   1. Definitions
 
   ***
@@ -10929,7 +10766,6 @@ All license text:
   whether by contract or otherwise, or (b) ownership of more than
   fifty percent (50%) of the outstanding shares or beneficial
   ownership of such entity.
-
   2. License Grants and Conditions
 
   ***
@@ -11001,7 +10837,6 @@ All license text:
 
   Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
   in Section 2.1.
-
   3. Responsibilities
 
   ***
@@ -11064,7 +10899,6 @@ All license text:
   indemnity or liability terms You offer. You may include additional
   disclaimers of warranty and limitations of liability specific to any
   jurisdiction.
-
   4. Inability to Comply Due to Statute or Regulation
 
   ***
@@ -11078,7 +10912,6 @@ All license text:
   Software under this License. Except to the extent prohibited by statute
   or regulation, such description must be sufficiently detailed for a
   recipient of ordinary skill to be able to understand it.
-
   5. Termination
 
   ***
@@ -11114,7 +10947,6 @@ All license text:
 
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \* \* \* 7. Limitation of Liability \* \* -------------------------- \* \* \* \* Under no circumstances and under no legal theory, whether tort \* \* (including negligence), contract, or otherwise, shall any \* \* Contributor, or anyone who distributes Covered Software as \* \* permitted above, be liable to You for any direct, indirect, \* \* special, incidental, or consequential damages of any character \* \* including, without limitation, damages for lost profits, loss of \* \* goodwill, work stoppage, computer failure or malfunction, or any \* \* and all other commercial damages or losses, even if such party \* \* shall have been informed of the possibility of such damages. This \* \* limitation of liability shall not apply to liability for death or \* \* personal injury resulting from such party's negligence to the \* \* extent applicable law prohibits such limitation. Some \* \* jurisdictions do not allow the exclusion or limitation of \* \* incidental or consequential damages, so this exclusion and \* \* limitation may not apply to You. \* \* \*
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
-
   8. Litigation
 
   ***
@@ -11125,7 +10957,6 @@ All license text:
   jurisdiction, without reference to its conflict-of-law provisions.
   Nothing in this Section shall prevent a party's ability to bring
   cross-claims or counter-claims.
-
   9. Miscellaneous
 
   ***
@@ -11136,7 +10967,6 @@ All license text:
   necessary to make it enforceable. Any law or regulation which provides
   that the language of a contract shall be construed against the drafter
   shall not be used to construe this License against a Contributor.
-
   10. Versions of the License
 
   ***
@@ -11188,14 +11018,12 @@ All license text:
   This Source Code Form is "Incompatible With Secondary Licenses", as
   defined by the Mozilla Public License, v. 2.0.
 
-* ### Mozilla Public License 2.0
+- ### Mozilla Public License 2.0
 
   #### Used by:
-
-  * [webpki-roots](https://github.com/ctz/webpki-roots)
+  - [webpki-roots](https://github.com/ctz/webpki-roots)
 
   Mozilla Public License Version 2.0
-
   1. Definitions
 
      1.1. "Contributor" means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.
@@ -11353,11 +11181,10 @@ All license text:
    This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0.
   ```
 
-* ### OpenSSL License
+- ### OpenSSL License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   /\* Copyright (C) 1995-1998 Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)) \* All rights reserved. \* \* This package is an SSL implementation written \* by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)). \* The implementation was written so as to conform with Netscapes SSL. \* \* This library is free for commercial and non-commercial use as long as \* the following conditions are aheared to. The following conditions \* apply to all code found in this distribution, be it the RC4, RSA, \* lhash, DES, etc., code; not just the SSL code. The SSL documentation \* included with this distribution is covered by the same copyright terms \* except that the holder is Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com)). \* \* Copyright remains Eric Young's, and as such any Copyright notices in \* the code are not to be removed. \* If this package is used in a product, Eric Young should be given attribution \* as the author of the parts of the library used. \* This can be in the form of a textual message at program startup or \* in documentation (online or textual) provided with the package. \* \* Redistribution and use in source and binary forms, with or without \* modification, are permitted provided that the following conditions \* are met: \* 1. Redistributions of source code must retain the copyright \* notice, this list of conditions and the following disclaimer. \* 2. Redistributions in binary form must reproduce the above copyright \* notice, this list of conditions and the following disclaimer in the \* documentation and/or other materials provided with the distribution. \* 3. All advertising materials mentioning features or use of this software \* must display the following acknowledgement: \* "This product includes cryptographic software written by \* Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com))" \* The word 'cryptographic' can be left out if the rouines from the library \* being used are not cryptographic related :-). \* 4. If you include any Windows specific code (or a derivative thereof) from \* the apps directory (application code) you must include an acknowledgement: \* "This product includes software written by Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com))" \* \* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND \* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE \* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE \* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE \* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL \* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS \* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) \* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT \* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY \* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF \* SUCH DAMAGE. \* \* The licence and distribution terms for any publically available version or \* derivative of this code cannot be changed. i.e. this code cannot simply be \* copied and put under another distribution licence \* \[including the GNU Public Licence.]
   \*/
diff --git a/src/content/docs/warp-client/legal/index.mdx b/src/content/docs/warp-client/legal/index.mdx
index eda71adda87c679..2a3706602febaf7 100644
--- a/src/content/docs/warp-client/legal/index.mdx
+++ b/src/content/docs/warp-client/legal/index.mdx
@@ -7,9 +7,8 @@ title: Legal
 hideChildren: true
 sidebar:
   order: 6
-
 ---
 
-* [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
-* [Application Terms of Service](https://www.cloudflare.com/application/terms/)
-* [Third party licenses](/warp-client/legal/3rdparty/)
+- [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
+- [Application Terms of Service](https://www.cloudflare.com/application/terms/)
+- [Third party licenses](/warp-client/legal/3rdparty/)
diff --git a/src/content/docs/warp-client/privacy.mdx b/src/content/docs/warp-client/privacy.mdx
index 92288d9c01bb7c0..b9d5bb1a7061d21 100644
--- a/src/content/docs/warp-client/privacy.mdx
+++ b/src/content/docs/warp-client/privacy.mdx
@@ -8,7 +8,6 @@ tags:
   - Privacy
 sidebar:
   order: 4
-
 ---
 
 The WARP Client application uses a VPN profile and/or service that enables us to intercept and secure your DNS queries and to transmit data from your device through the Cloudflare network, depending on the services you have enabled. We only collect limited DNS query and traffic data (excluding payload) that is sent to our network when you have the app enabled on your device. All information is handled in accordance with our [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/).
diff --git a/src/content/docs/web-analytics/configuration-options/filters.mdx b/src/content/docs/web-analytics/configuration-options/filters.mdx
index 27174f2f041e941..8ad627a79b2582d 100644
--- a/src/content/docs/web-analytics/configuration-options/filters.mdx
+++ b/src/content/docs/web-analytics/configuration-options/filters.mdx
@@ -5,7 +5,6 @@ products:
 title: Filters
 head: []
 description: Learn how to use filters in Cloudflare Web Analytics.
-
 ---
 
 import { DashButton } from "~/components";
@@ -25,4 +24,4 @@ To filter the data shown on Web Analytics:
 
 - By default, Web Analytics shows data for the previous 24 hours. Adjust the time range using the dropdown menu above the graph.
 - Select and drag the cursor on the graph to choose a custom time period.
-- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
\ No newline at end of file
+- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
diff --git a/src/content/docs/web-analytics/configuration-options/index.mdx b/src/content/docs/web-analytics/configuration-options/index.mdx
index 390e5e32d1c7476..4a728a05e606d7f 100644
--- a/src/content/docs/web-analytics/configuration-options/index.mdx
+++ b/src/content/docs/web-analytics/configuration-options/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Configuration options
 sidebar:
   order: 4
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Customize your Web Analytics views by using filters and rules.
 
diff --git a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
index 0b5369d3af5186b..4766dc07ffc8926 100644
--- a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
+++ b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
@@ -6,7 +6,6 @@ products:
 title: Core Web Vitals
 sidebar:
   order: 3
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,10 +14,8 @@ import { DashButton } from "~/components";
 
 :::note
 
-
 Core Web Vitals is currently only supported in Chromium browsers, with Safari and Firefox coming soon.
 
-
 :::
 
 ## Access Core Web Vitals
@@ -32,7 +29,7 @@ To access Core Web Vitals:
 
 2. Select your website and select **Core Web Vitals**.
 
-###  Core Web Vitals metrics
+### Core Web Vitals metrics
 
 Core Web Vitals is divided into three main sections, each one with information about a specific feature that affects user experience:
 
diff --git a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
index 503d9caaf70f22e..407d22e05366193 100644
--- a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
+++ b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
@@ -11,7 +11,7 @@ tags:
   - Privacy
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Web Analytics relies on the `performance.getEntriesByType('navigation')` object to collect metrics about page load performance. If Navigation Timing Level 2 is not supported, then [`performance.timing` (Level 1)](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) is used.
 
diff --git a/src/content/docs/web-analytics/data-metrics/dimensions.mdx b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
index 3caceecb45f0a80..2f8158417df0f8f 100644
--- a/src/content/docs/web-analytics/data-metrics/dimensions.mdx
+++ b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
@@ -6,7 +6,6 @@ products:
 title: Dimensions
 sidebar:
   order: 4
-
 ---
 
 Dimensions are the labels used to describe different types of metrics or data. For example, **Referer** is the data collected from external links referring visits to a page, while **Browser** shows which browsers accessed your website.
@@ -28,14 +27,14 @@ Below you can find a list of the different dimensions you can use to filter Web
 
 ## Navigation types
 
-| Type                    | Cache hit? | Explanation |
-| ----------------------- | ---------- | ----------- |
-| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
-| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
-| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document. |
-| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document. |
-| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
-| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Type                    | Cache hit? | Explanation                                                                                                                                                                                                                                                                                                                                                |
+| ----------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                              |
+| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                  |
+| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                    |
+| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document.                                                                                                                                                                                                     |
+| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                                               |
+| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                                   |
 | Back-forward            | ❌         | The visitor used the back/forward buttons/gestures in their browser but the previously-loaded document either not found or stale in the browsers HTTP cache OR a feature was used which prevents using the cache (refer to the explanation in [Back/forward cache](https://web.dev/articles/bfcache)), so a network request was made to load the document. |
-| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
-| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity. |
+| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                             |
+| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity.                                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
index 65577424b5e1480..d3db219922bbfb9 100644
--- a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
+++ b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
@@ -6,14 +6,13 @@ products:
 title: High-level metrics
 sidebar:
   order: 1
-
 ---
 
 Understanding the key metrics in web analytics is essential for optimizing your website’s performance and user experience. Here are the high-level metrics tracked by Cloudflare Web Analytics:
 
-* **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
-* **Page views** - A successful HTTP response with a content-type of HTML.
-* **Page load time** - The total amount of time required to load the page.
-* **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
+- **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
+- **Page views** - A successful HTTP response with a content-type of HTML.
+- **Page load time** - The total amount of time required to load the page.
+- **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
 
 ![Web Analytics overview page](~/assets/images/web-analytics/dash-web_analytics-overview.png)
diff --git a/src/content/docs/web-analytics/data-metrics/index.mdx b/src/content/docs/web-analytics/data-metrics/index.mdx
index 701245c37266099..7295662b2a7dd44 100644
--- a/src/content/docs/web-analytics/data-metrics/index.mdx
+++ b/src/content/docs/web-analytics/data-metrics/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Data and metrics
 sidebar:
   order: 5
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In this section, you can find information about the data and metrics available in Web Analytics.
 
diff --git a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
index ed4e1dedbe02b6b..17d8640e8fe0887 100644
--- a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
+++ b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
@@ -6,7 +6,6 @@ products:
 title: Page load time
 sidebar:
   order: 2
-
 ---
 
 Page load time summary gives you an overview of how long your web page takes to load, broken down by area. To access Page load time:
diff --git a/src/content/docs/web-analytics/faq.mdx b/src/content/docs/web-analytics/faq.mdx
index 57b722a62fab5d6..50db67fa11ae9e8 100644
--- a/src/content/docs/web-analytics/faq.mdx
+++ b/src/content/docs/web-analytics/faq.mdx
@@ -123,11 +123,11 @@ For manual embedding, this script instead connects to `cloudflareinsights.com`,
 connect-src [...existing values...] cloudflareinsights.com
 ```
 
-### How can I enforce Subresource Integrity (SRI) with the JS beacon? 
+### How can I enforce Subresource Integrity (SRI) with the JS beacon?
 
 If you're using the automated injection (i.e. not the manually-embedded script approach mentioned above), Cloudflare automatically includes an `integrity` attribute in the `<script>`. This ensures the script will only execute if a local hash of its downloaded contents match the integrity hash supplied in the HTML.
 
-Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure 
+Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure
 
 ### Can I use the same JS Snippet for a different domain?
 
@@ -159,11 +159,11 @@ When aggregating metrics in the Cloudflare Dashboard or querying the GraphQL API
 
 Note: the GraphQL API exposes a `sampleInterval` field to indicate which level of sampling has been applied to the query.
 
-* The beacon script will fire on every pageview.
-* The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
-* We store the unsampled data for 7 days.
-* We also aggregate it down so it's around 10% of the original volume for long-term storage.
-* Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
+- The beacon script will fire on every pageview.
+- The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
+- We store the unsampled data for 7 days.
+- We also aggregate it down so it's around 10% of the original volume for long-term storage.
+- Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
 
 ### Can I see server-side analytics by URL?
 
diff --git a/src/content/docs/web-analytics/get-started/rum-beacon.mdx b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
index 11ec40779ef5cee..675f6808ea47e52 100644
--- a/src/content/docs/web-analytics/get-started/rum-beacon.mdx
+++ b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
@@ -5,5 +5,4 @@ products:
   - web-analytics
 title: RUM beacon for Web Analytics
 external_link: /speed/observatory/rum-beacon/
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
index 6b3368cab792483..9ae208a6c8ea4c5 100644
--- a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
+++ b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
@@ -21,9 +21,9 @@ If you want to disable the automatic tracking for SPAs, you can do so by adding
 
 ```html
 <script
-  defer
-  src="https://static.cloudflareinsights.com/beacon.min.js"
-  data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
+	defer
+	src="https://static.cloudflareinsights.com/beacon.min.js"
+	data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
 ></script>
 ```
 
@@ -33,7 +33,7 @@ If you are using Google Tag Manager (GTM), you can disable SPA tracking by passi
 
 ```html
 <script
-  defer
-  src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
+	defer
+	src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
 ></script>
 ```
diff --git a/src/content/docs/web-analytics/limits.mdx b/src/content/docs/web-analytics/limits.mdx
index cc30789f0796155..8a2772d9e9f328e 100644
--- a/src/content/docs/web-analytics/limits.mdx
+++ b/src/content/docs/web-analytics/limits.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Web Analytics - Limits
-
 ---
 
 Cloudflare limits the number of sites for which you can track web analytics, as well as the number of rules allowed for each plan type. Refer to the following tables for more information.
diff --git a/src/content/docs/web3/about.mdx b/src/content/docs/web3/about.mdx
index e71d0319dd669a7..12c2faf886781b6 100644
--- a/src/content/docs/web3/about.mdx
+++ b/src/content/docs/web3/about.mdx
@@ -29,4 +29,4 @@ Only available for gateways to EVM-based chains, such as [Ethereum](/web3/how-to
 
 Write operations submit new data to the network. For example, sending a transaction or deploying a smart contract. The gateway forwards your request to one of Cloudflare's Ethereum nodes, which places the transaction in its mempool (a queue of pending transactions waiting to be included in a block).
 
-From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
\ No newline at end of file
+From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
diff --git a/src/content/docs/web3/api-reference.mdx b/src/content/docs/web3/api-reference.mdx
index a71630e4616b775..6580ba64f458124 100644
--- a/src/content/docs/web3/api-reference.mdx
+++ b/src/content/docs/web3/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/web3/subresources/hostnames/methods/list/
 sidebar:
   order: 6
-
 ---
diff --git a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
index e8c6ae241ad289f..8fa017a894a1131 100644
--- a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Concepts - Ethereum Gateways
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 As you get started with Cloudflare's Ethereum Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ethereum-gateway/reference/index.mdx b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
index 0ac05bf3f8fd5a3..2bb1163debfdf53 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - Ethereum
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
index 424052aeb898254..ae20777dcb9b048 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
@@ -6,7 +6,6 @@ products:
 title: Kill Switches
 sidebar:
   order: 6
-
 ---
 
 When writing contracts, be especially careful to write secure code and include a
@@ -16,7 +15,7 @@ the smart contract that can be exploited, this can lead to the theft of
 resources from the smart contract or from other individuals.
 
 This was brought into sharp focus during the [infamous DAO
-incident](https://en.wikipedia.org/wiki/The_DAO_\(organization\)). The DAO smart
+incident](<https://en.wikipedia.org/wiki/The_DAO_(organization)>). The DAO smart
 contract acted as a complex, decentralized venture capital fund and held Ether
 worth $250 million at its peak collected from a group of investors. Hackers
 exploited vulnerabilities in the smart contract, stealing $50 million worth of
@@ -24,7 +23,7 @@ Ether.
 
 Because there is no way to undo transactions in Ether, there was a highly
 controversial “hard fork," where the majority of the community agreed to accept
-a block that contained an *irregular state change* that essentially drained all
+a block that contained an _irregular state change_ that essentially drained all
 DAO funds into a special “WithdrawDAO” recovery contract. By convincing enough
 miners to accept this irregular block as valid, the DAO was able to return
 investors funds. However, not everyone agreed with the chain, with those who
@@ -59,7 +58,7 @@ trustworthiness.
 The trust placed in consensus-based algorithms is based on the assumption that
 most people are honest, or more accurately that no sufficiently large subset of
 people can be made to collude to produce a malicious outcome. This is the
-*democratisation of trust*. In the DAO attack, a majority of nodes agreed to
+_democratisation of trust_. In the DAO attack, a majority of nodes agreed to
 accept an irregular state transition. This effectively undid the damage of the
 attack, and shows how, at least in the world of blockchain, perception is
 reality. Because most people “believed" -- accepted this irregular block, it
diff --git a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
index fe72e9e11b576ae..a786977025d3db2 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
@@ -8,7 +8,6 @@ tags:
   - Migration
 sidebar:
   order: 5
-
 ---
 
 Though Cloudflare's Ethereum Gateway launched with support for the Rinkeby testnet, Rinkeby did not run through [The Merge](https://ethereum.org/en/upgrades/merge/) and - as a result - will no longer be a reliable staging environment for mainnet.
@@ -36,20 +35,20 @@ curl https://web3-trial.cloudflare-eth.com/v1/rinkeby \
 
 ```js title="Previous JS Fetch API" {2}
 await fetch(
-  new Request('https://web3-trial.cloudflare-eth.com/v1/rinkeby', {
-    method: 'POST',
-    body: JSON.stringify({
-      jsonrpc: '2.0',
-      method: 'eth_getBlockByNumber',
-      params: ['0x2244', true],
-      id: 1,
-    }),
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  })
-).then(resp => {
-  return resp.json();
+	new Request("https://web3-trial.cloudflare-eth.com/v1/rinkeby", {
+		method: "POST",
+		body: JSON.stringify({
+			jsonrpc: "2.0",
+			method: "eth_getBlockByNumber",
+			params: ["0x2244", true],
+			id: 1,
+		}),
+		headers: {
+			"Content-Type": "application/json",
+		},
+	}),
+).then((resp) => {
+	return resp.json();
 });
 ```
 
@@ -68,19 +67,19 @@ curl https://web3-trial.cloudflare-eth.com/v1/sepolia \
 
 ```js title="New JS Fetch API" {2}
 await fetch(
-  new Request('https://web3-trial.cloudflare-eth.com/v1/sepolia', {
-    method: 'POST',
-    body: JSON.stringify({
-      jsonrpc: '2.0',
-      method: 'eth_getBlockByNumber',
-      params: ['0x2244', true],
-      id: 1,
-    }),
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  })
-).then(resp => {
-  return resp.json();
+	new Request("https://web3-trial.cloudflare-eth.com/v1/sepolia", {
+		method: "POST",
+		body: JSON.stringify({
+			jsonrpc: "2.0",
+			method: "eth_getBlockByNumber",
+			params: ["0x2244", true],
+			id: 1,
+		}),
+		headers: {
+			"Content-Type": "application/json",
+		},
+	}),
+).then((resp) => {
+	return resp.json();
 });
 ```
diff --git a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
index b4932918c9e909b..dbc5a494061f6e0 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Supported networks - Ethereum Gateway
-
 ---
 
 Currently, Cloudflare Ethereum gateways support [interacting with](/web3/how-to/use-ethereum-gateway/) the following networks.
diff --git a/src/content/docs/web3/how-to/index.mdx b/src/content/docs/web3/how-to/index.mdx
index 09b45998630efc4..f6ebb1af9d9b691 100644
--- a/src/content/docs/web3/how-to/index.mdx
+++ b/src/content/docs/web3/how-to/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Web3 - How to
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
index 3987b7170bde027..d15b08583b61f0b 100644
--- a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
+++ b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
@@ -6,7 +6,6 @@ products:
 title: Use IPFS gateway
 sidebar:
   order: 2
-
 ---
 
 Once you have an IPFS gateway — meaning that you [create a new gateway](/web3/how-to/manage-gateways/#create-a-gateway) with a `target` of **IPFS** — you can get data from the IPFS network by using a URL.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
index 46ac314920cbb5a..f4449ce98f8c009 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
@@ -8,7 +8,6 @@ tags:
   - DNS
 sidebar:
   order: 4
-
 ---
 
 When you set up a gateway with a DNSLink record, that gateway is restricted to a particular piece of content — either a specific Content Identifier (CID) or an Interplanetary Name Service (IPNS) hostname. This is called a restricted gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
index 1f800c90518ab08..77d6c15618f0cde 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Concepts - IPFS Gateway
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 As you get started with Cloudflare's IPFS Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
index b47002eb8b4134b..754e32b96952c90 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
@@ -6,13 +6,12 @@ products:
 title: Automated deployments
 sidebar:
   order: 6
-
 ---
 
 Static sites are easy to deploy automatically. The code of the site is usually kept in a Git repository and deployed by pushing the latest commit to a repository that's connected to a Continuous Integration service like [Travis CI](https://travis-ci.org/), or by pushing to a repository directly on the server and activating a post-receive hook. Either way, the production version of the site is built and then copied into the serving path of an Apache or NGINX instance.
 
 IPFS usually fits into these systems: instead of copying the production version of a website into the serving path of an HTTP server, you would upload the same files to an IPFS node and update your DNS records with the new hash. There are several tools that help with different parts of this:
 
-* [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
-* [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
-* [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
+- [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
+- [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
+- [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/reference/index.mdx b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
index c69067dd176b415..10c80255fdf7a98 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - IPFS
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
index 574f2ebad732b96..81ab323e9cf901a 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
@@ -6,7 +6,6 @@ products:
 title: Peering
 sidebar:
   order: 5
-
 ---
 
 If you are running an IPFS node that serves many requests - like a public HTTP gateway - you may be able to speed up queries by maintaining long-lived connections to nodes that provide a large volume of data.
@@ -15,81 +14,57 @@ This process is known as **Peering** and you can tell IPFS to prioritize Cloudfl
 
 ```json
 {
-  "Peering": {
-    "Peers": [
-      {
-        "ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
-        "Addrs": [
-          "/dnsaddr/node-1.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
-        "Addrs": [
-          "/dnsaddr/node-2.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
-        "Addrs": [
-          "/dnsaddr/node-3.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
-        "Addrs": [
-          "/dnsaddr/node-4.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
-        "Addrs": [
-          "/dnsaddr/node-5.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
-        "Addrs": [
-          "/dnsaddr/node-6.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
-        "Addrs": [
-          "/dnsaddr/node-7.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
-        "Addrs": [
-          "/dnsaddr/node-8.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
-        "Addrs": [
-          "/dnsaddr/node-9.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
-        "Addrs": [
-          "/dnsaddr/node-10.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
-        "Addrs": [
-          "/dnsaddr/node-11.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
-        "Addrs": [
-          "/dnsaddr/node-12.ingress.cloudflare-ipfs.com"
-        ]
-      }
-    ]
-  }
+	"Peering": {
+		"Peers": [
+			{
+				"ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
+				"Addrs": ["/dnsaddr/node-1.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
+				"Addrs": ["/dnsaddr/node-2.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
+				"Addrs": ["/dnsaddr/node-3.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
+				"Addrs": ["/dnsaddr/node-4.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
+				"Addrs": ["/dnsaddr/node-5.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
+				"Addrs": ["/dnsaddr/node-6.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
+				"Addrs": ["/dnsaddr/node-7.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
+				"Addrs": ["/dnsaddr/node-8.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
+				"Addrs": ["/dnsaddr/node-9.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
+				"Addrs": ["/dnsaddr/node-10.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
+				"Addrs": ["/dnsaddr/node-11.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
+				"Addrs": ["/dnsaddr/node-12.ingress.cloudflare-ipfs.com"]
+			}
+		]
+	}
 }
 ```
diff --git a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
index f66712b07d379ed..9ae156f2b234174 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
@@ -6,14 +6,13 @@ products:
 title: Using IPFS with your website
 sidebar:
   order: 5
-
 ---
 
 Though it is not required, it is strongly recommended that websites hosted on IPFS use only relative links, unless linking to a different domain. This is because data can be accessed in many different (but ultimately equivalent) ways:
 
-* From your custom domain: `https://ipfs.tech/index.html`
-* From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
-* By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
+- From your custom domain: `https://ipfs.tech/index.html`
+- From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
+- By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
 
 Using only relative links within a web application supports all of these at once, and gives the most flexibility to the user. The exact method for switching to relative links, if you do not use them already, depends on the framework you use.
 
diff --git a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
index b76805532e21a27..658a32e0017e5e9 100644
--- a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
+++ b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
@@ -8,7 +8,6 @@ tags:
   - Debugging
 sidebar:
   order: 11
-
 ---
 
 ## Cloudflare-specific
diff --git a/src/content/docs/web3/reference/gateway-dns-records.mdx b/src/content/docs/web3/reference/gateway-dns-records.mdx
index c7ca135a158f53d..44ce03c721e9985 100644
--- a/src/content/docs/web3/reference/gateway-dns-records.mdx
+++ b/src/content/docs/web3/reference/gateway-dns-records.mdx
@@ -8,13 +8,12 @@ tags:
   - DNS
 sidebar:
   order: 1
-
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), Cloudflare automatically creates and adds records to your Cloudflare DNS so your gateway can receive and route traffic appropriately:
 
-* **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
-* **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
+- **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
+- **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
 
 These records cannot be edited within Cloudflare DNS. To make edits, you will have to [edit the gateway configuration](/web3/how-to/manage-gateways/#edit-a-gateway) itself.
 
diff --git a/src/content/docs/web3/reference/gateway-status.mdx b/src/content/docs/web3/reference/gateway-status.mdx
index f48cc0df30a6a4e..b8f41477bb010ac 100644
--- a/src/content/docs/web3/reference/gateway-status.mdx
+++ b/src/content/docs/web3/reference/gateway-status.mdx
@@ -6,7 +6,6 @@ products:
 title: Gateway status
 sidebar:
   order: 2
-
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), it can have one of several statuses.
diff --git a/src/content/docs/web3/reference/index.mdx b/src/content/docs/web3/reference/index.mdx
index 000a9dc1764b37c..d5e84b5cb473800 100644
--- a/src/content/docs/web3/reference/index.mdx
+++ b/src/content/docs/web3/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - Web3 Gateways
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/reference/migration-guide.mdx b/src/content/docs/web3/reference/migration-guide.mdx
index 438c79c9d19f639..aa20fe71fbcb5ac 100644
--- a/src/content/docs/web3/reference/migration-guide.mdx
+++ b/src/content/docs/web3/reference/migration-guide.mdx
@@ -8,14 +8,13 @@ tags:
   - Migration
 sidebar:
   order: 4
-
 ---
 
 As announced in [our blog post](https://blog.cloudflare.com/ea-web3-gateways/), Cloudflare is deprecating legacy hostnames that point to our public gateway endpoints at `cloudflare-eth.com` and `cloudflare-ipfs.com`.
 
 If you created a hostname pointing to these gateways during the [private beta](https://blog.cloudflare.com/announcing-web3-gateways/), you should migrate to use our new Web3 gateways to avoid a disruption in service.
 
-***
+---
 
 ## Migration guide
 
diff --git a/src/content/docs/workers-ai/agents.mdx b/src/content/docs/workers-ai/agents.mdx
index 6987307dd6a54f5..b54052a2ddfb2a5 100644
--- a/src/content/docs/workers-ai/agents.mdx
+++ b/src/content/docs/workers-ai/agents.mdx
@@ -9,9 +9,12 @@ sidebar:
   order: 7
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
-<div style={{ textAlign: 'center', marginBottom: '2rem' }}>
-  <p>Build AI assistants that can perform complex tasks on behalf of your users using Cloudflare Workers AI and Agents.</p>
-  <LinkButton href="/agents/">Go to Agents documentation</LinkButton>
-</div>
\ No newline at end of file
+<div style={{ textAlign: "center", marginBottom: "2rem" }}>
+	<p>
+		Build AI assistants that can perform complex tasks on behalf of your users
+		using Cloudflare Workers AI and Agents.
+	</p>
+	<LinkButton href="/agents/">Go to Agents documentation</LinkButton>
+</div>
diff --git a/src/content/docs/workers-ai/api-reference.mdx b/src/content/docs/workers-ai/api-reference.mdx
index 62cc80dfcec7e8a..d4399b2cedbf0b1 100644
--- a/src/content/docs/workers-ai/api-reference.mdx
+++ b/src/content/docs/workers-ai/api-reference.mdx
@@ -7,5 +7,4 @@ products:
   - workers-ai
 sidebar:
   order: 9
-
 ---
diff --git a/src/content/docs/workers-ai/configuration/bindings.mdx b/src/content/docs/workers-ai/configuration/bindings.mdx
index 51750be8e394b68..679ad1f230931bf 100644
--- a/src/content/docs/workers-ai/configuration/bindings.mdx
+++ b/src/content/docs/workers-ai/configuration/bindings.mdx
@@ -43,33 +43,27 @@ To configure a Workers AI binding in your Pages Function, you must use the Cloud
 `async env.AI.run()` runs a model. Takes a model as the first parameter, and an object as the second parameter.
 
 ```javascript
-const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
-    prompt: "What is the origin of the phrase 'Hello, World'"
+const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
+	prompt: "What is the origin of the phrase 'Hello, World'",
 });
 ```
 
 **Parameters**
 
-
-
-* `model` <Type text="string" /> <MetaInfo text="required" />
-
-  * The model to run.
+- `model` <Type text="string" /> <MetaInfo text="required" />
+  - The model to run.
 
   **Supported options**
-
-  * `stream` <Type text="boolean" /> <MetaInfo text="optional" />
-    * Returns a stream of results as they are available.
-
-
+  - `stream` <Type text="boolean" /> <MetaInfo text="optional" />
+    - Returns a stream of results as they are available.
 
 ```javascript
-const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
-    prompt: "What is the origin of the phrase 'Hello, World'",
-    stream: true
+const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
+	prompt: "What is the origin of the phrase 'Hello, World'",
+	stream: true,
 });
 
 return new Response(answer, {
-    headers: { "content-type": "text/event-stream" }
+	headers: { "content-type": "text/event-stream" },
 });
 ```
diff --git a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
index fe7d83c834c46c7..9daadf9eb13e568 100644
--- a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
+++ b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
@@ -14,9 +14,9 @@ Use Workers AI with [Chat UI](https://github.com/huggingface/chat-ui?tab=readme-
 
 You will need the following:
 
-* A [Cloudflare account](https://dash.cloudflare.com)
-* Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
-* An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
+- A [Cloudflare account](https://dash.cloudflare.com)
+- Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
+- An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
 
 ## Setup
 
@@ -28,20 +28,20 @@ When setting up your models, specify the `cloudflare` endpoint.
 
 ```json
 {
-  "name" : "nousresearch/hermes-2-pro-mistral-7b",
-  "tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
-  "parameters": {
-    "stop": ["<|im_end|>"]
-  },
-  "endpoints" : [
-    {
-      "type": "cloudflare",
-      // optionally specify these if not included in .env.local
-      "accountId": "your-account-id",
-      "apiToken": "your-api-token"
-      //
-    }
-  ]
+	"name": "nousresearch/hermes-2-pro-mistral-7b",
+	"tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
+	"parameters": {
+		"stop": ["<|im_end|>"]
+	},
+	"endpoints": [
+		{
+			"type": "cloudflare",
+			// optionally specify these if not included in .env.local
+			"accountId": "your-account-id",
+			"apiToken": "your-api-token"
+			//
+		}
+	]
 }
 ```
 
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
index 1f531e7b4d8115a..defd31249419534 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
@@ -20,7 +20,7 @@ To do so a `getWeather` function is defined that is passed to the LLM as tool.
 The `getWeather`function extracts the user's location from the request and calls the external weather API via the Workers' [`Fetch API`](/workers/runtime-apis/fetch/) and returns the result.
 
 ```ts title="Embedded function calling example with fetch()"
-import { runWithTools } from '@cloudflare/ai-utils';
+import { runWithTools } from "@cloudflare/ai-utils";
 
 type Env = {
 	AI: Ai;
@@ -31,14 +31,14 @@ export default {
 		// Define function
 		const getWeather = async (args: { numDays: number }) => {
 			const { numDays } = args;
-      // Location is extracted from request based on
-      // https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
-      const lat = request.cf?.latitude
-      const long = request.cf?.longitude
+			// Location is extracted from request based on
+			// https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
+			const lat = request.cf?.latitude;
+			const long = request.cf?.longitude;
 
-      // Interpolate values for external API call
+			// Interpolate values for external API call
 			const response = await fetch(
-				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`
+				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`,
 			);
 			return response.text();
 		};
@@ -46,35 +46,37 @@ export default {
 		const response = await runWithTools(
 			env.AI,
 			// Model with function calling support
-			'@hf/nousresearch/hermes-2-pro-mistral-7b',
+			"@hf/nousresearch/hermes-2-pro-mistral-7b",
 			{
 				// Messages
 				messages: [
 					{
-						role: 'user',
-						content: 'What the weather like the next 5 days? Respond as text',
+						role: "user",
+						content: "What the weather like the next 5 days? Respond as text",
 					},
 				],
 				// Definition of available tools the AI model can leverage
 				tools: [
 					{
-						name: 'getWeather',
-						description: 'Get the weather for the next [numDays] days',
+						name: "getWeather",
+						description: "Get the weather for the next [numDays] days",
 						parameters: {
-							type: 'object',
+							type: "object",
 							properties: {
-								numDays: { type: 'numDays', description: 'number of days for the weather forecast' },
+								numDays: {
+									type: "numDays",
+									description: "number of days for the weather forecast",
+								},
 							},
-							required: ['numDays'],
+							required: ["numDays"],
 						},
 						// reference to previously defined function
 						function: getWeather,
 					},
 				],
-			}
+			},
 		);
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
-
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
index f70be9e51f5b064..1f3842dcb258da4 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
@@ -12,6 +12,7 @@ description: Learn how to use Cloudflare Workers AI to interact with KV storage,
 Interact with persistent storage to retrieve or store information enables for powerful use cases.
 
 In this example we show how embedded function calling can interact with other resources on the Cloudflare Developer Platform with a few lines of code.
+
 ## Pre-Requisites
 
 For this example to work, you need to provision a [KV](/kv/) namespace first. To do so, follow the [KV - Get started ](/kv/get-started/) guide.
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
index 99f3b4077c79279..0d5b64aae3a9a86 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
@@ -15,54 +15,54 @@ Oftentimes APIs are defined and documented via [OpenAPI specification](https://s
 In this example the LLM will describe the a Github user, based Github's API and its OpenAPI spec.
 
 ```ts title="Embedded function calling example from OpenAPI Spec"
-import { createToolsFromOpenAPISpec, runWithTools } from '@cloudflare/ai-utils';
+import { createToolsFromOpenAPISpec, runWithTools } from "@cloudflare/ai-utils";
 
 type Env = {
 	AI: Ai;
 };
 
-const APP_NAME = 'cf-fn-calling-example-app';
+const APP_NAME = "cf-fn-calling-example-app";
 
 export default {
 	async fetch(request, env, ctx) {
 		const toolsFromOpenAPISpec = [
 			// You can pass the OpenAPI spec link or contents directly
 			...(await createToolsFromOpenAPISpec(
-				'https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json',
+				"https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json",
 				{
 					overrides: [
 						{
 							matcher: ({ url }) => {
-								return url.hostname === 'api.github.com';
+								return url.hostname === "api.github.com";
 							},
 							// for all requests on *.github.com, we'll need to add a User-Agent.
 							values: {
 								headers: {
-									'User-Agent': APP_NAME,
+									"User-Agent": APP_NAME,
 								},
 							},
 						},
 					],
-				}
+				},
 			)),
 		];
 
 		const response = await runWithTools(
 			env.AI,
-			'@hf/nousresearch/hermes-2-pro-mistral-7b',
+			"@hf/nousresearch/hermes-2-pro-mistral-7b",
 			{
 				messages: [
 					{
-						role: 'user',
-						content: 'Who is cloudflare on Github and how many repos does the organization have?',
+						role: "user",
+						content:
+							"Who is cloudflare on Github and how many repos does the organization have?",
 					},
 				],
 				tools: toolsFromOpenAPISpec,
-			}
+			},
 		);
 
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
-
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
index 559cf113e209a3a..c246533acd9ad9b 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare has a unique [embedded function calling](https://blog.cloudflare.com/embedded-function-calling) feature that allows you to execute function code alongside your tool call inference. Our npm package [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) is the developer toolkit to get started.
 
@@ -21,10 +21,8 @@ Embedded function calling can be used to easily make complex agents that interac
 
 :::caution[REST API support]
 
-
 Embedded function calling depends on features native to the Workers platform. This means that embedded function calling is only supported via [Cloudflare Workers](/workers-ai/get-started/workers-wrangler/), not via the [REST API](/workers-ai/get-started/rest-api/).
 
-
 :::
 
 ## Resources
diff --git a/src/content/docs/workers-ai/get-started/dashboard.mdx b/src/content/docs/workers-ai/get-started/dashboard.mdx
index 2ba3fce6dbc68cc..e22a698bbeddce6 100644
--- a/src/content/docs/workers-ai/get-started/dashboard.mdx
+++ b/src/content/docs/workers-ai/get-started/dashboard.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Follow this guide to create a Workers AI application using the Cloudflare dashboard.
 
@@ -26,11 +26,12 @@ To create a Workers AI application:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Under **Select a template**, select **LLM Chat App**.
 4. Select **Deploy**.
 5. Name your Worker, then select **Create and deploy**.
-5. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
+6. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
 
 ## Development
 
diff --git a/src/content/docs/workers-ai/get-started/index.mdx b/src/content/docs/workers-ai/get-started/index.mdx
index 707509ca784b6a0..a6eeb86d18d02ef 100644
--- a/src/content/docs/workers-ai/get-started/index.mdx
+++ b/src/content/docs/workers-ai/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 There are several options to build your Workers AI projects on Cloudflare. To get started, choose your preferred method:
 
@@ -16,8 +16,6 @@ There are several options to build your Workers AI projects on Cloudflare. To ge
 
 :::note
 
-
 These examples are geared towards creating new Workers AI projects. For help adding Workers AI to an existing Worker, refer to [Workers Bindings](/workers-ai/configuration/bindings/).
 
-
 :::
diff --git a/src/content/docs/workers-ai/get-started/rest-api.mdx b/src/content/docs/workers-ai/get-started/rest-api.mdx
index e25c56fa87f355a..bd2a6f0630db0aa 100644
--- a/src/content/docs/workers-ai/get-started/rest-api.mdx
+++ b/src/content/docs/workers-ai/get-started/rest-api.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 This guide will instruct you through setting up and deploying your first Workers AI project. You will use the Workers AI REST API to experiment with a large language model (LLM).
 
@@ -28,6 +28,7 @@ To get these values:
 1. In the Cloudflare dashboard, go to the **Workers AI** page.
 
    <DashButton url="/?to=/:account/ai/workers-ai" />
+
 2. Select **Use REST API**.
 3. Get your API token:
    1. Select **Create a Workers AI API Token**.
diff --git a/src/content/docs/workers-ai/guides/agents.mdx b/src/content/docs/workers-ai/guides/agents.mdx
index 1e57ab991facb86..86751d6187c1375 100644
--- a/src/content/docs/workers-ai/guides/agents.mdx
+++ b/src/content/docs/workers-ai/guides/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workers-ai
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
index bc3a24a9954b382..3b27b14dfda0ebb 100644
--- a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
@@ -14,9 +14,7 @@ products:
   - workers-ai
 ---
 
-
-
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 A handy way to explore all of the models available on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -26,7 +24,7 @@ You can [download the DeepSeek Coder notebook](/workers-ai/static/documentation/
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
-***
+---
 
 ## Exploring Code Generation Using DeepSeek Coder
 
@@ -229,8 +227,8 @@ if __name__ == '__main__':
 
 In this test case, we have two tests:
 
-* `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
-* `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
+- `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
+- `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
 
 If all these tests pass, it means that the `full_name` method is working as expected. If any of these tests fail, it
 
@@ -346,9 +344,9 @@ display(Markdown(f"""
 
 ```json
 {
-  "firstName": "Craig",
-  "lastName": "Dennis",
-  "numKids": 2,
-  "interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
+	"firstName": "Craig",
+	"lastName": "Dennis",
+	"numKids": 2,
+	"interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
 }
 ```
diff --git a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
index 3ca61769775d494..bb75cb0837843ae 100644
--- a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
@@ -17,9 +17,7 @@ products:
   - workers-ai
 ---
 
-
-
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 A great way to explore the models that are available to you on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -29,7 +27,7 @@ You can [download the Workers AI Text Generation Exploration notebook](/workers-
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
-***
+---
 
 ## How to Choose The Right Text Generation Model
 
@@ -148,7 +146,7 @@ questions = [
 speed_date(models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -172,9 +170,9 @@ speed_date(models, questions)
 
 *Generated in *3.63* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -194,9 +192,9 @@ speed_date(models, questions)
 
 *Generated in *4.33* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -216,9 +214,9 @@ speed_date(models, questions)
 
 *Generated in *3.15* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -242,9 +240,9 @@ Remember, these are just a few examples, and your use cases may vary depending o
 
 *Generated in *2.92* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -272,7 +270,7 @@ That's me in a nutshell! I'm ready to help with a wide range of tasks, so feel f
 
 *Generated in *10.28* seconds*
 
-***
+---
 
 ### Language Translation
 
@@ -299,7 +297,7 @@ questions = [f"""Translate "{phrase}" from "English" to "{language}" """
 speed_date(proud_translator_models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -389,9 +387,9 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *3.44* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -467,7 +465,7 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *1.51* seconds*
 
-***
+---
 
 ### Information Retrieval and Summarization
 
@@ -493,7 +491,7 @@ questions = [f"""Summarize the book "{book}" into a few sentences. Ensure to inc
 speed_date(proud_summarizers, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -521,9 +519,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *8.34* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -545,9 +543,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.04* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -569,7 +567,7 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.66* seconds*
 
-***
+---
 
 ### Content Creation
 
@@ -591,7 +589,7 @@ questions = [
 speed_date(proud_content_creator_models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -627,9 +625,9 @@ I hope these suggestions help! Let me know if you have any other questions or if
 
 *Generated in *1.13* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -659,9 +657,9 @@ Tagline: "Say goodbye to cable chaos and hello to a clutter-free workspace with
 
 *Generated in *1.33* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -702,15 +700,15 @@ Sure, here's a headline for a blog on why you should use me specifically over ot
 
 Here's a brief summary of why I stand out from other models:
 
-* Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
-* Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
-* Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
+- Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
+- Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
+- Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
 
 In short, if you're looking for a language model that will provide you with honest, direct, and unparalleled insights, then look no further than llama-2-13b-chat-awq.
 
 *Generated in *10.24* seconds*
 
-***
+---
 
 ### Text Classification
 
@@ -741,7 +739,7 @@ sentiment_questions = [sentiment_prompt_template.format(text=comment) for commen
 speed_date(proud_classifiers, sentiment_questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -787,9 +785,9 @@ The sentiment of the text is positive.
 
 *Generated in *0.89* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -833,4 +831,4 @@ The sentiment of the text is positive.
 
 *Generated in *1.93* seconds*
 
-***
+---
diff --git a/src/content/docs/workers-ai/platform/data-usage.mdx b/src/content/docs/workers-ai/platform/data-usage.mdx
index 9b29840f9db5768..bab6821ff99f590 100644
--- a/src/content/docs/workers-ai/platform/data-usage.mdx
+++ b/src/content/docs/workers-ai/platform/data-usage.mdx
@@ -19,7 +19,7 @@ Your inputs (e.g., text prompts, image submissions, audio files, etc.), outputs
 
 For Workers AI:
 
-* You own, and are responsible for, all of your Customer Content.
-* Cloudflare does not make your Customer Content available to any other Cloudflare customer.
-* Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
-* Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
+- You own, and are responsible for, all of your Customer Content.
+- Cloudflare does not make your Customer Content available to any other Cloudflare customer.
+- Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
+- Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
diff --git a/src/content/docs/workers-ai/platform/pricing.mdx b/src/content/docs/workers-ai/platform/pricing.mdx
index fd38831c6ee17fc..474edbfe1bdd8fb 100644
--- a/src/content/docs/workers-ai/platform/pricing.mdx
+++ b/src/content/docs/workers-ai/platform/pricing.mdx
@@ -35,38 +35,38 @@ The Price in Tokens column is equivalent to the Price in Neurons column - the di
 
 ## LLM model pricing
 
-| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                       |
-| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                |
-| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                |
-| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
-| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
-| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                              |
-| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                               |
-| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
-| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
-| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
-| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                              |
-| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                |
-| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                               |
-| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                               |
-| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
-| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
-| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
-| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                               |
-| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                               |
-| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
-| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                |
-| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                |
-| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                              |
-| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens |
+| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                        |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
+| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
+| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                               |
+| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                                |
+| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
+| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
+| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
+| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                               |
+| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                 |
+| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                                |
+| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                                |
+| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
+| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
+| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
+| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                                |
+| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
+| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
+| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                 |
+| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                 |
+| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                               |
+| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens  |
 | @cf/moonshotai/kimi-k2.6                     | $0.950 per M input tokens <br/> $0.160 per M cached input tokens <br/> $4.000 per M output tokens | 86364 neurons per M input tokens <br/> 14545 neurons per M cached input tokens <br/> 363636 neurons per M output tokens |
-| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
+| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                 |
 
 ## Embeddings model pricing
 
diff --git a/src/content/docs/workers-vpc/configuration/index.mdx b/src/content/docs/workers-vpc/configuration/index.mdx
index aee79d0d23cdc78..e669ed279505b79 100644
--- a/src/content/docs/workers-vpc/configuration/index.mdx
+++ b/src/content/docs/workers-vpc/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
index e5d02896289509c..da1a8323544eed5 100644
--- a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
+++ b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
@@ -128,6 +128,7 @@ resource "cloudflare_connectivity_directory_service" "my_database" {
 ```
 
 Valid values for `cert_verification_mode` are:
+
 - `verify_full` (default)
 - `verify_ca`
 - `disabled`
diff --git a/src/content/docs/workers-vpc/examples/private-api.mdx b/src/content/docs/workers-vpc/examples/private-api.mdx
index 48bc4d0013d7733..09e90435cc172fe 100644
--- a/src/content/docs/workers-vpc/examples/private-api.mdx
+++ b/src/content/docs/workers-vpc/examples/private-api.mdx
@@ -87,7 +87,9 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch data from internal API and process it before returning
-			const response = await env.INTERNAL_API.fetch("http://10.0.1.50:8080/api/data");
+			const response = await env.INTERNAL_API.fetch(
+				"http://10.0.1.50:8080/api/data",
+			);
 
 			// Use the response of the private API to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
index 12fb5230fee07fe..3312f993bec679d 100644
--- a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
+++ b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
@@ -125,7 +125,9 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch a file from the private S3 bucket via VPC endpoint
-			const response = await env.S3_STORAGE.fetch("https://s3.us-west-2.amazonaws.com/my-bucket/data.json");
+			const response = await env.S3_STORAGE.fetch(
+				"https://s3.us-west-2.amazonaws.com/my-bucket/data.json",
+			);
 
 			// Use the response from S3 to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
index 6bc0349de2f2609..60995de99ab8b3c 100644
--- a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
+++ b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
@@ -72,15 +72,19 @@ export default {
 		const url = new URL(request.url);
 
 		// Route to internal services
-		if (url.pathname.startsWith('/api/users')) {
-			const response = await env.USER_SERVICE.fetch("https://user-api.internal.example.com" + url.pathname);
+		if (url.pathname.startsWith("/api/users")) {
+			const response = await env.USER_SERVICE.fetch(
+				"https://user-api.internal.example.com" + url.pathname,
+			);
 			return response;
-		} else if (url.pathname.startsWith('/api/orders')) {
-			const response = await env.ORDER_SERVICE.fetch("https://orders-api.internal.example.com" + url.pathname);
+		} else if (url.pathname.startsWith("/api/orders")) {
+			const response = await env.ORDER_SERVICE.fetch(
+				"https://orders-api.internal.example.com" + url.pathname,
+			);
 			return response;
 		}
 
-		return new Response('Not Found', { status: 404 });
+		return new Response("Not Found", { status: 404 });
 	},
 };
 ```
@@ -107,4 +111,3 @@ curl https://api-gateway.workers.dev/api/orders
 - Implement [rate limiting](/durable-objects/api/)
 - Set up [monitoring and alerting](/analytics/analytics-engine/)
 - Explore [other examples](/workers-vpc/examples/)
-
diff --git a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
index 570cd2dcec2d850..42c63e8209e1e50 100644
--- a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
+++ b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
@@ -53,6 +53,7 @@ When you merge the PR, Workers Builds will update your build and deploy commands
 If Workers Builds detects a mismatch between your Worker name in the Cloudflare dashboard and the `name` field in your Wrangler configuration file, it will create a pull request to fix the conflict.
 
 This can happen when:
+
 - You rename your Worker in the dashboard but not in your config file
 - You connect a repository that was previously used with a different Worker
 - The `name` field in your config does not match the connected Worker
diff --git a/src/content/docs/workers/ci-cd/builds/build-caching.mdx b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
index 83e4dd1c9c17496..603f75d3db137a1 100644
--- a/src/content/docs/workers/ci-cd/builds/build-caching.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
@@ -35,15 +35,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                                          |
-| ---------- | ----------------------------------------------------------- |
-| Astro      | `node_modules/.astro`                                       |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
-| Eleventy   | `.cache`                                                    |
-| Gatsby     | `.cache`, `public`                                          |
-| Next.js    | `.next/cache`                                               |
-| Nuxt       | `node_modules/.cache/nuxt`                                  |
-| SvelteKit  | `node_modules/.cache/imagetools`                            |
+| Framework  | Directories cached                            |
+| ---------- | --------------------------------------------- |
+| Astro      | `node_modules/.astro`                         |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
+| Eleventy   | `.cache`                                      |
+| Gatsby     | `.cache`, `public`                            |
+| Next.js    | `.next/cache`                                 |
+| Nuxt       | `node_modules/.cache/nuxt`                    |
+| SvelteKit  | `node_modules/.cache/imagetools`              |
 
 :::note
 [Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers.
diff --git a/src/content/docs/workers/ci-cd/builds/build-image.mdx b/src/content/docs/workers/ci-cd/builds/build-image.mdx
index 828b464902269e7..0daab950f2f9c35 100644
--- a/src/content/docs/workers/ci-cd/builds/build-image.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-image.mdx
@@ -91,7 +91,6 @@ Workers Builds are run in the following environment:
 | **Build Environment** | Ubuntu 24.04 |
 | **Architecture**      | x86_64       |
 
-
 ## Build Image Policy
 
 ### Preinstalled Software Updates
@@ -102,6 +101,7 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
+
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -111,5 +111,6 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
+
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
\ No newline at end of file
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
index 032d023592e4d4f..6d533ab9b2cede9 100644
--- a/src/content/docs/workers/ci-cd/builds/configuration.mdx
+++ b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -8,7 +8,13 @@ products:
   - workers
 ---
 
-import { DirectoryListing, Render, Tabs, TabItem, DashButton } from "~/components";
+import {
+	DirectoryListing,
+	Render,
+	Tabs,
+	TabItem,
+	DashButton,
+} from "~/components";
 
 When connecting your Git repository to your Worker, you can customize the configurations needed to build and deploy your Worker.
 
@@ -35,7 +41,7 @@ Note that when you update and save build settings, the updated settings will be
 | **Git repository**                                                                                                    | Choose the Git repository you would like to connect your Worker to.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | **Git branch**                                                                                                        | Select the branch you would like Cloudflare to listen to for new commits. This will be defaulted to `main`.                                                                                                                                                                                                                                                                                                                                                                            |
 | **Build command** _(Optional)_                                                                                        | Set a build command if your project requires a build step (e.g. `npm run build`). This is necessary, for example, when using a [front-end framework](/workers/ci-cd/builds/configuration/#framework-support) such as Next.js or Remix.                                                                                                                                                                                                                                                 |
-| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                                 |
+| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                         |
 | **[Non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command)** | Set a command to run when executing [a build for commit on a non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds). This will default to `npx wrangler versions upload` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                    |
 | **Root directory** _(Optional)_                                                                                       | Specify the path to your project. The root directory defines where the build command will be run and can be helpful in [monorepos](/workers/ci-cd/builds/advanced-setups/#monorepos) to isolate a specific project within the repository for builds.                                                                                                                                                                                                                                   |
 | **[API token](/workers/ci-cd/builds/configuration/#api-token)** _(Optional)_                                          | The API token is used to authenticate your build request and authorize the upload and deployment of your Worker to Cloudflare. By default, Cloudflare will automatically generate an API token for your account when using Workers Builds, and continue to use this API token for all subsequent builds. Alternatively, you can [create your own API token](/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication/#generate-tokens), or select one that you already own. |
@@ -128,4 +134,4 @@ The following system environment variables are injected by default (but can be o
 | `WORKERS_CI`            | `1`                             | Changing build behaviour when run on Workers Builds versus locally                      |
 | `WORKERS_CI_BUILD_UUID` | `<build-uuid-of-current-build>` | Passing the Build UUID along to custom workflows                                        |
 | `WORKERS_CI_COMMIT_SHA` | `<sha1-hash-of-current-commit>` | Passing current commit ID to error reporting, for example, Sentry                       |
-| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
\ No newline at end of file
+| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
index 19c36e00c988216..6438ba7c4ac10cf 100644
--- a/src/content/docs/workers/ci-cd/builds/index.mdx
+++ b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets you connect a new or existing Worker to a GitHub or GitLab repository, enabling automated builds and deployments for your Worker on push.
@@ -16,6 +17,7 @@ The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets yo
 ### Connect a new Worker
 
 To create a new Worker and connect it to a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -30,6 +32,7 @@ To create a new Worker and connect it to a GitHub or GitLab repository:
 ### Connect an existing Worker
 
 To connect an existing Worker to a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -71,14 +74,15 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 ## Disconnecting builds
 
 To disconnect a Worker from a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select the Worker you want to disconnect from a repository.
-4. Select **Settings** and then **Builds**.
-5. Select **Disconnect**.
+3. Select **Settings** and then **Builds**.
+4. Select **Disconnect**.
 
 If you want to switch to a different repository for your Worker, you must first disable builds, then reconnect to select the new repository.
 
-To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
\ No newline at end of file
+To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
diff --git a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
index 12161e725454792..b5fe2e420f07c48 100644
--- a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
+++ b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
@@ -8,19 +8,19 @@ products:
   - workers
 ---
 
-Workers Builds has the following limits. 
+Workers Builds has the following limits.
 
-| Metric                | Free plan       | Paid plans                                 |
-| --------------------- | --------------- | ------------------------------------------ |
-| **Build minutes**     | 3,000 per month | 6,000 per month (then, +$0.005 per minute) |
-| **Concurrent builds** | 1               | 6                                          |
-| **Build timeout**     | 20 minutes      | 20 minutes                                 |
-| **Deploy Hooks**      | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account |
-| **CPU**               | 2 vCPU          | 4 vCPU                                     |
-| **Memory**            | 8 GB            | 8 GB                                       |
-| **Disk space**        | 20 GB           | 20 GB                                      |
-| **Environment variables**  | 64              | 64                                        |
-| **Size per environment variable**  | 5 KB            | 5 KB                                       |
+| Metric                            | Free plan                              | Paid plans                                 |
+| --------------------------------- | -------------------------------------- | ------------------------------------------ |
+| **Build minutes**                 | 3,000 per month                        | 6,000 per month (then, +$0.005 per minute) |
+| **Concurrent builds**             | 1                                      | 6                                          |
+| **Build timeout**                 | 20 minutes                             | 20 minutes                                 |
+| **Deploy Hooks**                  | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account     |
+| **CPU**                           | 2 vCPU                                 | 4 vCPU                                     |
+| **Memory**                        | 8 GB                                   | 8 GB                                       |
+| **Disk space**                    | 20 GB                                  | 20 GB                                      |
+| **Environment variables**         | 64                                     | 64                                         |
+| **Size per environment variable** | 5 KB                                   | 5 KB                                       |
 
 ## Definitions
 
diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
index 19e65105b5e0d03..34a4b8f9fba5a10 100644
--- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
+++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
@@ -35,6 +35,7 @@ On Wrangler v3 and up, Workers Builds automatically matches the name of the conn
 `✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. wrangler deploy path/to/script) or the main config field.`
 
 If you see this error, a Wrangler configuration file is likely missing from the root directory. Navigate to **Settings** > **Build** > **Build Configuration** to update the root directory, or add a [Wrangler configuration file](/workers/wrangler/configuration/) to the specified directory.
+
 ### Incorrect account_id
 
 `Could not route to /client/v4/accounts/<Account ID>/workers/services/<Worker name>, perhaps your object identifier is invalid? [code: 7003]`
diff --git a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
index 2eae230b3612062..f67f5ae1685a419 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
@@ -5,6 +5,7 @@ description: Integrate Workers development into your existing GitHub Actions wor
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitHub Actions](https://github.com/marketplace/actions/deploy-to-cloudflare-workers-with-wrangler). Here is how you can set up your GitHub Actions workflow.
@@ -20,6 +21,7 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
 ### API token
 
 To create an API token to authenticate Wrangler in your CI job:
+
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
diff --git a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
index ad35eea9bad7ff5..713a4dfc47d7707 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
@@ -5,6 +5,7 @@ description: Integrate Workers development into your existing GitLab Pipelines w
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitLab CI/CD](https://docs.gitlab.com/ee/ci/pipelines/index.html). Here is how you can set up your Gitlab CI/CD pipeline.
diff --git a/src/content/docs/workers/configuration/integrations/index.mdx b/src/content/docs/workers/configuration/integrations/index.mdx
index 23a188bf0e4e94c..e9f73b20e932138 100644
--- a/src/content/docs/workers/configuration/integrations/index.mdx
+++ b/src/content/docs/workers/configuration/integrations/index.mdx
@@ -14,24 +14,24 @@ One of the key features of Cloudflare Workers is the ability to integrate with o
 
 Cloudflare Workers offers several types of integrations, including:
 
-* [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
-* [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
-* [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
+- [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
+- [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
+- [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
 
 ## How to use integrations
 
 To use any of the available integrations:
 
-* Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
-* In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
-* Use the provided APIs and functions to connect to the integration and access its data or functionality.
-* Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
+- Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
+- In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
+- Use the provided APIs and functions to connect to the integration and access its data or functionality.
+- Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
 
 ## Tips and best practices
 
 To help you get the most out of using integrations with Cloudflare Workers:
 
-* Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
-* Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
-* Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
-* Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
+- Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
+- Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
+- Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
+- Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
diff --git a/src/content/docs/workers/configuration/routing/custom-domains.mdx b/src/content/docs/workers/configuration/routing/custom-domains.mdx
index be78f27efb57efa..dccd631d43e8638 100644
--- a/src/content/docs/workers/configuration/routing/custom-domains.mdx
+++ b/src/content/docs/workers/configuration/routing/custom-domains.mdx
@@ -14,7 +14,7 @@ Custom Domains allow you to connect your Worker to a domain or subdomain, withou
 
 Custom Domains are routes to a domain or subdomain (such as `example.com` or `shop.example.com`) within a Cloudflare zone where the Worker is the origin.
 
-Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with.  If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
+Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with. If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
 
 Custom Domains can stack on top of each other. For example, if you have Worker A attached to `app.example.com` and Worker B attached to `api.example.com`, Worker A can call `fetch()` on `api.example.com` and invoke Worker B.
 
@@ -33,10 +33,8 @@ Custom Domains can be attached to your Worker via the Cloudflare dashboard, [Wra
 
 :::caution
 
-
 You cannot create a Custom Domain on a hostname with an existing CNAME DNS record or on a zone you do not own.
 
-
 :::
 
 ### Set up a Custom Domain in the dashboard
@@ -77,8 +75,6 @@ To configure a Custom Domain in your [Wrangler configuration file](/workers/wran
 
 To configure multiple Custom Domains:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -106,8 +102,8 @@ On the same zone, if a Worker is attempting to communicate with a target Worker
 
 For example, consider the following scenario, where both Workers are running on the `example.com` Cloudflare zone:
 
-* `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
-* `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
+- `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
+- `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
 
 If `worker-a` sends a fetch request to `worker-b`, the request will fail, because of the limitation on same-zone fetch requests. `worker-a` must have a service binding to `worker-b` for this request to resolve.
 
@@ -115,9 +111,9 @@ If `worker-a` sends a fetch request to `worker-b`, the request will fail, becaus
 export default {
 	fetch(request) {
 		// This will fail
-		return fetch("https://shop.example.com")
-	}
-}
+		return fetch("https://shop.example.com");
+	},
+};
 ```
 
 However, if `worker-b` was instead set up to run on the Custom Domain `shop.example.com`, the fetch request would succeed.
@@ -142,15 +138,15 @@ For example, consider the following workflow:
 ```js title="auth-worker" {8}
 export default {
 	fetch(request) {
-		const url = new URL(request.url)
-		if(url.searchParams.get("auth") !== "SECRET_TOKEN") {
-			return new Response(null, { status: 401 })
+		const url = new URL(request.url);
+		if (url.searchParams.get("auth") !== "SECRET_TOKEN") {
+			return new Response(null, { status: 401 });
 		} else {
 			// This will invoke `api-worker`
-			return fetch(request)
+			return fetch(request);
 		}
-	}
-}
+	},
+};
 ```
 
 ## Certificates
@@ -166,10 +162,10 @@ Because Custom Domains require an exact hostname match, a Worker attached to `ex
 - [Redirect from www to root](/rules/url-forwarding/examples/redirect-www-to-root/)
 - [Redirect from root to www](/rules/url-forwarding/examples/redirect-root-to-www/)
 
-You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting *from*, so that Cloudflare can apply the redirect rule.
+You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting _from_, so that Cloudflare can apply the redirect rule.
 
-  - For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
-  - For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+- For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+- For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
 
 :::note
 `192.0.2.0` (A record) and `100::` (AAAA record) are [reserved placeholder addresses](/dns/manage-dns-records/how-to/create-dns-records/#originless-setups) for originless setups. Because the DNS record is proxied, requests never reach this address — Cloudflare intercepts them and applies your redirect rule.
@@ -224,4 +220,4 @@ To migrate the route `example.com/*` in your [Wrangler configuration file](/work
    </WranglerConfig>
 
 4. Run `npx  wrangler deploy` to create the Custom Domain your Worker will run on.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/workers/configuration/routing/routes.mdx b/src/content/docs/workers/configuration/routing/routes.mdx
index 867c38239a1de4e..977bc4da059df0f 100644
--- a/src/content/docs/workers/configuration/routing/routes.mdx
+++ b/src/content/docs/workers/configuration/routing/routes.mdx
@@ -95,8 +95,6 @@ Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `z
 
 To add multiple routes:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -194,12 +192,12 @@ Because `*` matches zero or more of **any character** (not just subdomains), `*e
 
 The following examples illustrate the difference between `*example.com/*` and `*.example.com/*`:
 
-| Request URL | `*example.com/*` | `*.example.com/*` |
-|---|---|---|
-| `https://example.com/` | Matches | Does not match |
-| `https://www.example.com/path` | Matches | Matches |
-| `https://myexample.com/` | Matches | Does not match |
-| `https://not-example.com/` | Does not match | Does not match |
+| Request URL                    | `*example.com/*` | `*.example.com/*` |
+| ------------------------------ | ---------------- | ----------------- |
+| `https://example.com/`         | Matches          | Does not match    |
+| `https://www.example.com/path` | Matches          | Matches           |
+| `https://myexample.com/`       | Matches          | Does not match    |
+| `https://not-example.com/`     | Does not match   | Does not match    |
 
 #### Paths may optionally end with `*`
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-existing.mdx b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
index 5ec6aea9c3faf4a..005eac692d1bd1f 100644
--- a/src/content/docs/workers/configuration/sites/start-from-existing.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
@@ -40,16 +40,16 @@ To deploy a pre-existing static site project, start with a pre-generated site. W
 2. Add your site's build/output directory to the Wrangler file:
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "site": {
-       "bucket": "./public" // <-- Add your build directory name here.
-     }
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "site": {
+          "bucket": "./public" // <-- Add your build directory name here.
+        }
+      }
+      ```
+   
+      </WranglerConfig>
 
    The default directories for the most popular static site generators are listed below:
    - Hugo: `public`
@@ -138,14 +138,14 @@ async function handleEvent(event) {
 6. Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone. Add a `route` property to the Wrangler file.
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "route": "https://example.com/*"
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "route": "https://example.com/*"
+      }
+      ```
+   
+      </WranglerConfig>
 
    :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
index 8dd326cda0b305d..4406df19ce0437c 100644
--- a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
@@ -55,39 +55,39 @@ The template project contains the following files and directories:
 - Change the `name` property to the name of your project:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "$schema": "./node_modules/wrangler/config-schema.json",
-    "name": "my-site"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "$schema": "./node_modules/wrangler/config-schema.json",
+      "name": "my-site"
+    }
+    ```
+  
+    </WranglerConfig>
 
 - Consider updating`compatibility_date` to today's date to get access to the most recent Workers features:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "compatibility_date": "yyyy-mm-dd"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "compatibility_date": "yyyy-mm-dd"
+    }
+    ```
+  
+    </WranglerConfig>
 
 - Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "route": "https://example.com/*"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "route": "https://example.com/*"
+    }
+    ```
+  
+    </WranglerConfig>
 
   :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-worker.mdx b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
index 55e9d74a41f69f7..78314e60913a490 100644
--- a/src/content/docs/workers/configuration/sites/start-from-worker.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
@@ -24,16 +24,16 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st
 2. Add configuration to your Wrangler file to point to it.
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "site": {
-       "bucket": "./public" // Add the directory with your static assets!
-     }
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "site": {
+          "bucket": "./public" // Add the directory with your static assets!
+        }
+      }
+      ```
+   
+      </WranglerConfig>
 
 3. Install the `@cloudflare/kv-asset-handler` package in your project:
 
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
index c32f452efe28734..c5f131c4787fd9c 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
@@ -6,6 +6,7 @@ description: Upload versions of Workers and create deployments to release new ve
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 Versions track changes to your Worker. Deployments configure how those changes are deployed to your traffic.
@@ -107,4 +108,3 @@ Refer to [Migrate from Service Workers to ES modules](/workers/reference/migrate
 ### Durable Object migrations
 
 Uploading a version with [Durable Object migrations](/durable-objects/reference/durable-objects-migrations/) is not supported. Use [`wrangler deploy`](/workers/wrangler/commands/workers/#deploy) if you are applying a [Durable Object migration](/durable-objects/reference/durable-objects-migrations/).
-
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
index 6e0adad52574968..49bb0247b41f32f 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
@@ -65,9 +65,9 @@ If you forward the original request object, the override header carries through
 ```js
 // The override header from the inbound request is forwarded to the downstream Worker.
 export default {
-  async fetch(request, env) {
-    return env.MY_SERVICE.fetch(request);
-  },
+	async fetch(request, env) {
+		return env.MY_SERVICE.fetch(request);
+	},
 };
 ```
 
@@ -76,15 +76,15 @@ Alternatively, you can set an override header explicitly:
 ```js
 // Replace the version ID with the target version from `wrangler versions list`.
 export default {
-  async fetch(request, env) {
-    const response = await env.MY_SERVICE.fetch("https://example.com/", {
-      headers: {
-        "Cloudflare-Workers-Version-Overrides":
-          'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
-      },
-    });
-    return response;
-  },
+	async fetch(request, env) {
+		const response = await env.MY_SERVICE.fetch("https://example.com/", {
+			headers: {
+				"Cloudflare-Workers-Version-Overrides":
+					'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
+			},
+		});
+		return response;
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/configuration/workers-with-page-rules.mdx b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
index f165f162646c204..b50db0cc22a9f9c 100644
--- a/src/content/docs/workers/configuration/workers-with-page-rules.mdx
+++ b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
@@ -32,43 +32,39 @@ If you are experiencing Page Rule errors when running Workers, contact your Clou
 
 The following Page Rules may not work as expected when an incoming request is matched to a Worker route:
 
-* Always Online
-* [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
-* [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
-* [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
-* [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
-* [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
-* [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
-* Disable Apps
-* [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
-* [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
-* [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
-* [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
-* Host Header Override
-* [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
-* [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
-* [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
-* [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
-* [SSL](/workers/configuration/workers-with-page-rules/#ssl)
+- Always Online
+- [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
+- [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
+- [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
+- [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
+- [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
+- [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
+- Disable Apps
+- [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
+- [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
+- [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
+- [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
+- Host Header Override
+- [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
+- [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
+- [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
+- [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
+- [SSL](/workers/configuration/workers-with-page-rules/#ssl)
 
 This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.
 
 :::caution[Testing]
 
-
 Due to ongoing changes to the Workers runtime, detailed documentation on how these rules will be affected are updated following testing.
 
-
 :::
 
 To learn what these Page Rules do, refer to [Page Rules](/rules/page-rules/).
 
 :::note[Same zone versus other zone]
 
-
 A same zone subrequest is a request the Worker makes to an orange-clouded hostname in the same zone the Worker runs on. Depending on your DNS configuration, any request that falls outside that definition may be considered an other zone request by the Cloudflare network.
 
-
 :::
 
 ### Always Use HTTPS
@@ -137,11 +133,11 @@ A same zone subrequest is a request the Worker makes to an orange-clouded hostna
 
 ### Email Obfuscation
 
-| Source     | Target     | Behavior       |
-| -------------------------|------------|------------|
-| Client     | Worker     | Rule Ignored   |
-| Worker     | Same Zone  | Rule Respected |
-| Worker     | Other Zone | Rule Ignored   |
+| Source | Target     | Behavior       |
+| ------ | ---------- | -------------- |
+| Client | Worker     | Rule Ignored   |
+| Worker | Same Zone  | Rule Respected |
+| Worker | Other Zone | Rule Ignored   |
 
 ### Forwarding URL
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
index ddd98b108387e07..39d7ac436e98f44 100644
--- a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
@@ -12,9 +12,9 @@ import { Render, PackageManagers, Tabs, TabItem } from "~/components";
 
 :::note
 
-The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client. 
+The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client.
 
-If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/). 
+If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/).
 
 :::
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/turso.mdx b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
index 8467e1c8801cf6a..a144bb3ba616abd 100644
--- a/src/content/docs/workers/databases/third-party-integrations/turso.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
@@ -92,7 +92,7 @@ To set up an integration with Turso:
    ```sh
    # Get your database URL
    turso db show my-db --url
-   
+
    # Create an authentication token
    turso db tokens create my-db
    ```
@@ -103,8 +103,8 @@ To set up an integration with Turso:
    # Add the database URL as a secret
    npx wrangler secret put TURSO_URL
    # When prompted, paste your database URL
-   
-   # Add the authentication token as a secret  
+
+   # Add the authentication token as a secret
    npx wrangler secret put TURSO_AUTH_TOKEN
    # When prompted, paste your authentication token
    ```
diff --git a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
index ebdc513a162cfd2..e34c59345e8275b 100644
--- a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
@@ -17,7 +17,6 @@ To set up an integration with Upstash:
 1. You need an existing Upstash database to connect to. [Create an Upstash database](https://docs.upstash.com/redis#create-a-database) or [load data from an existing database to Upstash](https://docs.upstash.com/redis/howto/connectclient).
 
 2. Insert some data to your Upstash database. You can add data to your Upstash database in two ways:
-
    - Use the CLI directly from your Upstash console.
    - Alternatively, install [redis-cli](https://redis.io/docs/getting-started/installation/) locally and run the following commands.
 
@@ -53,7 +52,7 @@ To set up an integration with Upstash:
    # Add the Upstash Redis URL as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_URL
    # When prompted, paste your Upstash Redis REST URL
-   
+
    # Add the Upstash Redis token as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_TOKEN
    # When prompted, paste your Upstash Redis REST token
diff --git a/src/content/docs/workers/databases/third-party-integrations/xata.mdx b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
index 31cf393a9843646..a7bcec8e02894d4 100644
--- a/src/content/docs/workers/databases/third-party-integrations/xata.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
@@ -10,7 +10,6 @@ import { Render, TabItem, Tabs } from "~/components";
 
 [Xata](https://xata.io) is a PostgreSQL database platform designed to help developers operate and scale databases with enhanced productivity and performance. Xata provides features like instant copy-on-write database branches, zero-downtime schema changes, data anonymization, AI-powered performance monitoring, and BYOC.
 
-
 :::note
 
 You can connect to Xata using [Hyperdrive](/hyperdrive), which provides connection pooling and reduces the amount of round trips required to create a secure connection from Workers to your database.
diff --git a/src/content/docs/workers/development-testing/multi-workers.mdx b/src/content/docs/workers/development-testing/multi-workers.mdx
index 42e37c1197aff58..c90270083c2c91e 100644
--- a/src/content/docs/workers/development-testing/multi-workers.mdx
+++ b/src/content/docs/workers/development-testing/multi-workers.mdx
@@ -22,11 +22,11 @@ We recommend this approach as the default for most development workflows as it e
 You can run multiple Workers in a single dev command by passing multiple configuration files to your dev server:
 
 **Using Wrangler**
-   
+
 <PackageManagers
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
 />
 
 The first config (`./app/wrangler.jsonc`) is treated as the primary Worker, exposed at `http://localhost:8787`. Additional configs (e.g. `./api/wrangler.jsonc`) run as auxiliary Workers, available via service bindings or tail consumers from the primary Worker.
@@ -40,16 +40,16 @@ import { defineConfig } from "vite";
 import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
-  plugins: [
-    cloudflare({
-      configPath: "./app/wrangler.jsonc",
-      auxiliaryWorkers: [
-        {
-          configPath: "./api/wrangler.jsonc",
-        },
-      ],
-    }),
-  ],
+	plugins: [
+		cloudflare({
+			configPath: "./app/wrangler.jsonc",
+			auxiliaryWorkers: [
+				{
+					configPath: "./api/wrangler.jsonc",
+				},
+			],
+		}),
+	],
 });
 ```
 
@@ -68,17 +68,17 @@ Then run:
 You can also run each Worker in separate dev commands, each with its own terminal and configuration.
 
 <PackageManagers
-  comment="Terminal 1"
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./app/wrangler.jsonc"
+	comment="Terminal 1"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./app/wrangler.jsonc"
 />
 
 <PackageManagers
-  comment="Terminal 2"
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./api/wrangler.jsonc"
+	comment="Terminal 2"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./api/wrangler.jsonc"
 />
 
 These Workers run in different dev commands but can still communicate with each other via service bindings or tail consumers **regardless of whether they are started with `wrangler dev` or `vite dev`**.
diff --git a/src/content/docs/workers/development-testing/testing.mdx b/src/content/docs/workers/development-testing/testing.mdx
index d085cb4f503f58c..c5a0a61aa1c1e8c 100644
--- a/src/content/docs/workers/development-testing/testing.mdx
+++ b/src/content/docs/workers/development-testing/testing.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 7
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/development-testing/vite-plugin.mdx b/src/content/docs/workers/development-testing/vite-plugin.mdx
index f11a1758026f45d..60632a1db291f01 100644
--- a/src/content/docs/workers/development-testing/vite-plugin.mdx
+++ b/src/content/docs/workers/development-testing/vite-plugin.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 1
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx
index 1a033e8825cce5d..e61fa08d45b3e14 100644
--- a/src/content/docs/workers/examples/103-early-hints.mdx
+++ b/src/content/docs/workers/examples/103-early-hints.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Allow a client to request static assets while waiting for the HTML response.
 tags:
   - Middleware
@@ -16,6 +15,7 @@ reviewed: 2022-08-12
 products:
   - workers
 ---
+
 import { DashButton, Steps, TabItem, Tabs } from "~/components";
 
 If you want to get started quickly, click on the button below.
diff --git a/src/content/docs/workers/examples/ab-testing.mdx b/src/content/docs/workers/examples/ab-testing.mdx
index 28b72e57b042734..bf57cc1256414cd 100644
--- a/src/content/docs/workers/examples/ab-testing.mdx
+++ b/src/content/docs/workers/examples/ab-testing.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up an A/B test by controlling what response is served based on
   cookies. This version supports passing the request through to test and control
   on the origin, bypassing random assignment.
diff --git a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
index 3947c1f80350fb6..79830e09a3e34f0 100644
--- a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
+++ b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Access custom Cloudflare properties and control how Cloudflare features
   are applied to every request.
 tags:
diff --git a/src/content/docs/workers/examples/aggregate-requests.mdx b/src/content/docs/workers/examples/aggregate-requests.mdx
index 4666d5fd1baf002..05f04def29f8b17 100644
--- a/src/content/docs/workers/examples/aggregate-requests.mdx
+++ b/src/content/docs/workers/examples/aggregate-requests.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send two GET request to two urls and aggregates the responses into one
   response.
 tags:
diff --git a/src/content/docs/workers/examples/alter-headers.mdx b/src/content/docs/workers/examples/alter-headers.mdx
index cec4c62a5d08212..129e244ab485ac0 100644
--- a/src/content/docs/workers/examples/alter-headers.mdx
+++ b/src/content/docs/workers/examples/alter-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of how to add, change, or delete headers sent in a request or
   returned in a response.
 tags:
diff --git a/src/content/docs/workers/examples/auth-with-headers.mdx b/src/content/docs/workers/examples/auth-with-headers.mdx
index 4903f1f12598379..cf1ff87eee06ec7 100644
--- a/src/content/docs/workers/examples/auth-with-headers.mdx
+++ b/src/content/docs/workers/examples/auth-with-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Allow or deny a request based on a known pre-shared key in a header.
   This is not meant to replace the WebCrypto API.
 tags:
diff --git a/src/content/docs/workers/examples/basic-auth.mdx b/src/content/docs/workers/examples/basic-auth.mdx
index 84e8be086b49095..c4dbb71353b6c7f 100644
--- a/src/content/docs/workers/examples/basic-auth.mdx
+++ b/src/content/docs/workers/examples/basic-auth.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Shows how to restrict access using the HTTP Basic schema.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/block-on-tls.mdx b/src/content/docs/workers/examples/block-on-tls.mdx
index 43831741eb75193..c6edd048d5fafdc 100644
--- a/src/content/docs/workers/examples/block-on-tls.mdx
+++ b/src/content/docs/workers/examples/block-on-tls.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Inspects the incoming request's TLS version and blocks if under TLSv1.2.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/bulk-origin-proxy.mdx b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
index 6760d74eafdc8fb..943e7b6c4e8fea0 100644
--- a/src/content/docs/workers/examples/bulk-origin-proxy.mdx
+++ b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Resolve requests to your domain to a set of proxy third-party origin URLs.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/bulk-redirects.mdx b/src/content/docs/workers/examples/bulk-redirects.mdx
index 623d39afaf43402..f6c5d881a4b4ef6 100644
--- a/src/content/docs/workers/examples/bulk-redirects.mdx
+++ b/src/content/docs/workers/examples/bulk-redirects.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Redirect requests to certain URLs based on a mapped object to the
   request's URL.
 tags:
diff --git a/src/content/docs/workers/examples/cache-api.mdx b/src/content/docs/workers/examples/cache-api.mdx
index 3bb0c1b6578703f..34e592721b3174c 100644
--- a/src/content/docs/workers/examples/cache-api.mdx
+++ b/src/content/docs/workers/examples/cache-api.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the Cache API to store responses in Cloudflare's cache.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-post-request.mdx b/src/content/docs/workers/examples/cache-post-request.mdx
index 2fb05d6f62ead04..3c7f7548bf22aef 100644
--- a/src/content/docs/workers/examples/cache-post-request.mdx
+++ b/src/content/docs/workers/examples/cache-post-request.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Cache POST requests using the Cache API.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-tags.mdx b/src/content/docs/workers/examples/cache-tags.mdx
index 0a85395341521d5..248effca15f46bc 100644
--- a/src/content/docs/workers/examples/cache-tags.mdx
+++ b/src/content/docs/workers/examples/cache-tags.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send Additional Cache Tags using Workers
 tags:
   - Caching
diff --git a/src/content/docs/workers/examples/cache-using-fetch.mdx b/src/content/docs/workers/examples/cache-using-fetch.mdx
index 2270d27f236d16a..b3f9f1cd60b870c 100644
--- a/src/content/docs/workers/examples/cache-using-fetch.mdx
+++ b/src/content/docs/workers/examples/cache-using-fetch.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Determine how to cache a resource by setting TTLs, custom cache keys,
   and cache headers in a fetch request.
 tags:
@@ -564,6 +563,6 @@ When `no-cache` is supplied the cache is forced to revalidate the currently cach
 origin.
 
 ```js
-fetch(request, { cache: 'no-store'});
-fetch(request, { cache: 'no-cache'});
+fetch(request, { cache: "no-store" });
+fetch(request, { cache: "no-cache" });
 ```
diff --git a/src/content/docs/workers/examples/conditional-response.mdx b/src/content/docs/workers/examples/conditional-response.mdx
index f6b109c19de1a2f..0772d216c56f507 100644
--- a/src/content/docs/workers/examples/conditional-response.mdx
+++ b/src/content/docs/workers/examples/conditional-response.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Return a response based on the incoming request's URL, HTTP method,
   User Agent, IP address, ASN or device type.
 tags:
diff --git a/src/content/docs/workers/examples/cors-header-proxy.mdx b/src/content/docs/workers/examples/cors-header-proxy.mdx
index 8335f92850f2e62..c6eacdd133464f7 100644
--- a/src/content/docs/workers/examples/cors-header-proxy.mdx
+++ b/src/content/docs/workers/examples/cors-header-proxy.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Add the necessary CORS headers to a third party API response.
 tags:
   - Security
@@ -716,4 +715,3 @@ return response.json()
 }
 ```
 </TabItem> </Tabs>
-
diff --git a/src/content/docs/workers/examples/country-code-redirect.mdx b/src/content/docs/workers/examples/country-code-redirect.mdx
index ca3af654f791168..19a10589a4fb622 100644
--- a/src/content/docs/workers/examples/country-code-redirect.mdx
+++ b/src/content/docs/workers/examples/country-code-redirect.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Redirect a response based on the country code in the header of a visitor.
 tags:
   - Redirects
diff --git a/src/content/docs/workers/examples/data-loss-prevention.mdx b/src/content/docs/workers/examples/data-loss-prevention.mdx
index 8483ccab86121e9..ce5c655a6d71251 100644
--- a/src/content/docs/workers/examples/data-loss-prevention.mdx
+++ b/src/content/docs/workers/examples/data-loss-prevention.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Protect sensitive data to prevent data loss, and send alerts to a
   webhooks server in the event of a data breach.
 tags:
diff --git a/src/content/docs/workers/examples/debugging-logs.mdx b/src/content/docs/workers/examples/debugging-logs.mdx
index ac22a6f78f37918..33128a13520e036 100644
--- a/src/content/docs/workers/examples/debugging-logs.mdx
+++ b/src/content/docs/workers/examples/debugging-logs.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send debugging information in an errored response to a logging service.
 tags:
   - Debugging
diff --git a/src/content/docs/workers/examples/extract-cookie-value.mdx b/src/content/docs/workers/examples/extract-cookie-value.mdx
index 26eeba1adfb4182..2d1e1e7afa6b59d 100644
--- a/src/content/docs/workers/examples/extract-cookie-value.mdx
+++ b/src/content/docs/workers/examples/extract-cookie-value.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Given the cookie name, get the value of a cookie. You can also use
   cookies for A/B testing.
 tags:
diff --git a/src/content/docs/workers/examples/fetch-json.mdx b/src/content/docs/workers/examples/fetch-json.mdx
index e803fee74e049cb..ea574ed80ffa5a5 100644
--- a/src/content/docs/workers/examples/fetch-json.mdx
+++ b/src/content/docs/workers/examples/fetch-json.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send a GET request and read in JSON from the response. Use to fetch
   external data.
 pcx_content_type: example
diff --git a/src/content/docs/workers/examples/geolocation-app-weather.mdx b/src/content/docs/workers/examples/geolocation-app-weather.mdx
index da915f46349f806..903b1906ea7da65 100644
--- a/src/content/docs/workers/examples/geolocation-app-weather.mdx
+++ b/src/content/docs/workers/examples/geolocation-app-weather.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Fetch weather data from an API using the user's geolocation data.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-custom-styling.mdx b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
index 9e5888fbd2a51de..9010b98d7034c34 100644
--- a/src/content/docs/workers/examples/geolocation-custom-styling.mdx
+++ b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Personalize website styling based on localized user time.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-hello-world.mdx b/src/content/docs/workers/examples/geolocation-hello-world.mdx
index ca32cc280b07052..9e9f01f835ea0c3 100644
--- a/src/content/docs/workers/examples/geolocation-hello-world.mdx
+++ b/src/content/docs/workers/examples/geolocation-hello-world.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Get all geolocation data fields and display them in HTML.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/hot-link-protection.mdx b/src/content/docs/workers/examples/hot-link-protection.mdx
index 4a7d1a997e16191..b0773924fca66d4 100644
--- a/src/content/docs/workers/examples/hot-link-protection.mdx
+++ b/src/content/docs/workers/examples/hot-link-protection.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Block other websites from linking to your content. This is useful for
   protecting images.
 tags:
diff --git a/src/content/docs/workers/examples/modify-request-property.mdx b/src/content/docs/workers/examples/modify-request-property.mdx
index 7b0dff4cea7b789..fe5199d30781dab 100644
--- a/src/content/docs/workers/examples/modify-request-property.mdx
+++ b/src/content/docs/workers/examples/modify-request-property.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Create a modified request with edited properties based off of an
   incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/modify-response.mdx b/src/content/docs/workers/examples/modify-response.mdx
index 6638180c480b268..75b8731aae95371 100644
--- a/src/content/docs/workers/examples/modify-response.mdx
+++ b/src/content/docs/workers/examples/modify-response.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Fetch and modify response properties which are immutable by creating a
   copy first.
 tags:
diff --git a/src/content/docs/workers/examples/multiple-cron-triggers.mdx b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
index 52d717075365808..70ffa53d857fde0 100644
--- a/src/content/docs/workers/examples/multiple-cron-triggers.mdx
+++ b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set multiple Cron Triggers on three different schedules.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/openai-sdk-streaming.mdx b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
index 20dc1d448fe2b7e..4a56649266440a9 100644
--- a/src/content/docs/workers/examples/openai-sdk-streaming.mdx
+++ b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the OpenAI v4 SDK to stream responses from OpenAI.
 tags:
   - AI
diff --git a/src/content/docs/workers/examples/post-json.mdx b/src/content/docs/workers/examples/post-json.mdx
index 6b01ab31537684d..c14f7e3a5c83c6a 100644
--- a/src/content/docs/workers/examples/post-json.mdx
+++ b/src/content/docs/workers/examples/post-json.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send a POST request with JSON data. Use to share data with external servers.
 tags:
   - JSON
diff --git a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
index c18930609c886b2..0204a2732ca6e07 100644
--- a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
+++ b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Protect against timing attacks by safely comparing values using
   `timingSafeEqual`.
 tags:
diff --git a/src/content/docs/workers/examples/read-post.mdx b/src/content/docs/workers/examples/read-post.mdx
index c805138d150cb88..6ec581eff46a60c 100644
--- a/src/content/docs/workers/examples/read-post.mdx
+++ b/src/content/docs/workers/examples/read-post.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Serve an HTML form, then read POST requests. Use also to read JSON or
   POST data from an incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/return-html.mdx b/src/content/docs/workers/examples/return-html.mdx
index 3cd587b30a97fae..065b623759cdcc6 100644
--- a/src/content/docs/workers/examples/return-html.mdx
+++ b/src/content/docs/workers/examples/return-html.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Deliver an HTML page from an HTML string directly inside the Worker script.
 demo: https://returning-html.workers-sites-examples.workers.dev
 tags:
diff --git a/src/content/docs/workers/examples/rewrite-links.mdx b/src/content/docs/workers/examples/rewrite-links.mdx
index cd10efbb5239087..e20265b28ed4a5b 100644
--- a/src/content/docs/workers/examples/rewrite-links.mdx
+++ b/src/content/docs/workers/examples/rewrite-links.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Rewrite URL links in HTML using the HTMLRewriter. This is useful for
   JAMstack websites.
 tags:
diff --git a/src/content/docs/workers/examples/signing-requests.mdx b/src/content/docs/workers/examples/signing-requests.mdx
index f1e685251d8fc52..7d98b2922d35a5f 100644
--- a/src/content/docs/workers/examples/signing-requests.mdx
+++ b/src/content/docs/workers/examples/signing-requests.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Verify a signed request using the HMAC and SHA-256 algorithms or return a 403.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
index d20ca8a4a5aa54b..6f97419c267b833 100644
--- a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
+++ b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Inject [Turnstile](/turnstile/) implicitly into HTML elements using the
   HTMLRewriter runtime API.
 tags:
diff --git a/src/content/docs/workers/examples/websockets.mdx b/src/content/docs/workers/examples/websockets.mdx
index cd919a2ecbdd2e4..84e5dc0f892523c 100644
--- a/src/content/docs/workers/examples/websockets.mdx
+++ b/src/content/docs/workers/examples/websockets.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the WebSockets API to communicate in real time with your Cloudflare Workers.
 tags:
   - WebSockets
@@ -82,8 +81,8 @@ async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<worker::Res
 ```
 
 </TabItem> </Tabs>
-After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
+After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
@@ -136,7 +135,6 @@ The `WebSocketPair` constructor returns an Object, with the `0` and `1` keys eac
 
 In order to begin communicating with the `client` WebSocket in your Worker, call `accept` on the `server` WebSocket. This will tell the Workers runtime that it should listen for WebSocket data and keep the connection open with your `client` WebSocket:
 
-
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
diff --git a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
index 8311463a2303071..bf7151b9c2d494c 100644
--- a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
+++ b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
@@ -10,13 +10,14 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers with AI & agent frameworks.
+	Create full-stack applications deployed to Cloudflare Workers with AI & agent
+	frameworks.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/ai-and-agents" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing
+	folder="workers/framework-guides/ai-and-agents"
+	maxDepth={2}
+/>
diff --git a/src/content/docs/workers/framework-guides/apis/index.mdx b/src/content/docs/workers/framework-guides/apis/index.mdx
index 7c65dfc89d5ab12..e3e0997d8023893 100644
--- a/src/content/docs/workers/framework-guides/apis/index.mdx
+++ b/src/content/docs/workers/framework-guides/apis/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers using APIs.
+	Create full-stack applications deployed to Cloudflare Workers using APIs.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/index.mdx b/src/content/docs/workers/framework-guides/index.mdx
index e7fd39e00a6aecf..7c7d795d9e3aa13 100644
--- a/src/content/docs/workers/framework-guides/index.mdx
+++ b/src/content/docs/workers/framework-guides/index.mdx
@@ -11,13 +11,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers.
+	Create full-stack applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides" maxDepth={4}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides" maxDepth={4} />
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
index 03a98d1fc26641a..f7fc7a59d1511ee 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
@@ -5,4 +5,4 @@ pcx_content_type: navigation
 external_link: https://docs.expo.dev/eas/hosting/reference/worker-runtime/
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
index 6cc8183f77ec8c3..be6cede9f5c8287 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack mobile applications deployed to Cloudflare Workers.
+	Create full-stack mobile applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/web-apps/astro.mdx b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
index a1e4aaf3e9ea768..b90f2936598dcff 100644
--- a/src/content/docs/workers/framework-guides/web-apps/astro.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
@@ -87,11 +87,27 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Astro"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: "dist/_worker.js/index.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: ./dist, binding: ASSETS" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: "dist/_worker.js/index.js",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: ./dist, binding: ASSETS",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{ label: "adapter", file: "astro.config.mjs", value: "@astrojs/cloudflare" },
+		{
+			label: "adapter",
+			file: "astro.config.mjs",
+			value: "@astrojs/cloudflare",
+		},
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/index.mdx b/src/content/docs/workers/framework-guides/web-apps/index.mdx
index cb372caec51f847..87009d6003a290e 100644
--- a/src/content/docs/workers/framework-guides/web-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack web applications deployed to Cloudflare Workers.
+	Create full-stack web applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
index db924f15079e094..0cd619c91b471d7 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
@@ -24,9 +24,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Analog"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
index 8dbf8a2eccef565..c12d9db29798dfc 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
@@ -29,7 +29,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Angular"
 	configs={[
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/browser" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/browser",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
index 6f0ab43afa2d870..b098122622c408a 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
@@ -75,7 +75,6 @@ Docusaurus is designed to be easy to use and customizable, making it a popular c
 
 If your Docusaurus project is entirely pre-rendered (which it usually is), follow these steps:
 
-
 <Steps>
 1.  **Add a Wrangler configuration file.**
 
@@ -116,4 +115,3 @@ If your Docusaurus project is entirely pre-rendered (which it usually is), follo
 Bindings are a way to connect your Docusaurus project to other Cloudflare services, enabling you to store and retrieve data within your application.
 
 <Render file="frameworks-bindings" product="workers" />
-
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
index 5b69a489c1fe3d0..8373da96cbbdb96 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
@@ -33,8 +33,6 @@ import {
 
 [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create/deploy-to-workers&repository=https://github.com/cloudflare/templates/tree/main/vite-react-template)
 
-
-
 ## What is Hono?
 
 [Hono](https://hono.dev/) is an ultra-fast, lightweight framework for building web applications, and works fantastically with Cloudflare Workers.
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
index eb6f1cd2cdff605..2c8eb7ea43bc8ed 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
@@ -8,4 +8,4 @@ sidebar:
     hideIndex: true
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
index 775117671401c50..bf3f6b53620a121 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
@@ -29,9 +29,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Nuxt"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "preset", file: "nuxt.config.ts", value: "cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
index 520223f8048b1ce..0b4849166b7c4fc 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
@@ -33,9 +33,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Solid Start"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
index 11a06ef6dfe2634..6d8e6bedc97a74c 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
@@ -30,8 +30,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Waku"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -89,4 +97,4 @@ You can serve static assets in your Waku application by adding them to the `./pu
 
 During the build process, Waku copies `.js`, `.css`, `.html`, and `.txt` files from this directory into the final assets output. `.txt` files are used for storing data used by Server Components that are rendered at build time.
 
-<Render file="workers-assets-routing-summary" product="workers" />
\ No newline at end of file
+<Render file="workers-assets-routing-summary" product="workers" />
diff --git a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
index 7218158dad2f5ea..59f1211f42978e5 100644
--- a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
@@ -29,8 +29,6 @@ import {
 
 This is a simple getting started guide. For detailed documentation on how to use the Cloudflare OpenNext adapter, visit the [OpenNext website](https://opennext.js.org/cloudflare).
 
-
-
 ## What is Next.js?
 
 [Next.js](https://nextjs.org/) is a [React](https://react.dev/) framework for building full stack applications.
@@ -43,23 +41,23 @@ You can deploy your Next.js app to Cloudflare Workers using the OpenNext adapter
 
 Most Next.js features are supported by the Cloudflare OpenNext adapter:
 
-| Feature                               | Cloudflare adapter   | Notes                                                                        |
-| ------------------------------------- | -------------------- | ---------------------------------------------------------------------------- |
-| App Router                            | 🟢 supported         |                                                                              |
-| Pages Router                          | 🟢 supported         |                                                                              |
-| Route Handlers                        | 🟢 supported         |                                                                              |
-| React Server Components               | 🟢 supported         |                                                                              |
-| Static Site Generation (SSG)          | 🟢 supported         |                                                                              |
-| Server-Side Rendering (SSR)           | 🟢 supported         |                                                                              |
-| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                                              |
-| Server Actions                        | 🟢 supported         |                                                                              |
-| Response streaming                    | 🟢 supported         |                                                                              |
-| asynchronous work with `next/after`   | 🟢 supported         |                                                                              |
-| Middleware                            | 🟢 supported         |                                                                              |
-| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/) |
-| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                                               |
-| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js                                |
-| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported                  |
+| Feature                               | Cloudflare adapter   | Notes                                                       |
+| ------------------------------------- | -------------------- | ----------------------------------------------------------- |
+| App Router                            | 🟢 supported         |                                                             |
+| Pages Router                          | 🟢 supported         |                                                             |
+| Route Handlers                        | 🟢 supported         |                                                             |
+| React Server Components               | 🟢 supported         |                                                             |
+| Static Site Generation (SSG)          | 🟢 supported         |                                                             |
+| Server-Side Rendering (SSR)           | 🟢 supported         |                                                             |
+| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                             |
+| Server Actions                        | 🟢 supported         |                                                             |
+| Response streaming                    | 🟢 supported         |                                                             |
+| asynchronous work with `next/after`   | 🟢 supported         |                                                             |
+| Middleware                            | 🟢 supported         |                                                             |
+| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/)                 |
+| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                              |
+| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js               |
+| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported |
 
 ## Deploy a new Next.js project on Workers
 
@@ -133,8 +131,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Next.js"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: ".open-next/worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .open-next/assets" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .open-next/assets",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "adapter", file: "package.json", value: "@opennextjs/cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
index 226dd6d9fc4c19e..a69d19964c7156c 100644
--- a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
@@ -96,4 +96,4 @@ RedwoodSDK is a framework for building server-side web applications on Cloudflar
 
 	The first time you run the command it might fail and ask you to create a workers.dev subdomain. Go to the dashboard and open the Workers menu. Opening the Workers landing page for the first time will create a workers.dev subdomain automatically.
 
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
index 16233bdaac9a5ea..0c4e1f8d44d8645 100644
--- a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
@@ -31,11 +31,27 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="SvelteKit"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".svelte-kit/cloudflare/_worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .svelte-kit/cloudflare" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".svelte-kit/cloudflare/_worker.js",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .svelte-kit/cloudflare",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{ label: "adapter", file: "svelte.config.js", value: "@sveltejs/adapter-cloudflare" },
+		{
+			label: "adapter",
+			file: "svelte.config.js",
+			value: "@sveltejs/adapter-cloudflare",
+		},
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vike.mdx b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
index 27dd268608448ee..6218d56b5d4a81a 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vike.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
@@ -10,13 +10,12 @@ products:
 ---
 
 import { AutoconfigDiagram, Steps, PackageManagers } from "~/components";
-import { Tabs, TabItem } from '@astrojs/starlight/components';
+import { Tabs, TabItem } from "@astrojs/starlight/components";
 
 You can deploy your [Vike](https://vike.dev) app to Cloudflare using the Vike extension [`vike-photon`](https://vike.dev/vike-photon).
 
 All app types (SSR/SPA/SSG) are supported.
 
-
 :::tip[Already have a Vike project?]
 Run `wrangler deploy` in a project without a Wrangler configuration file and Wrangler will automatically detect Vike, generate the necessary configuration, and deploy your project.
 
@@ -29,8 +28,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Vike"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/server/index.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/client" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/client",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -43,7 +50,6 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 
 Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `vike-photon` with `@photonjs/cloudflare`.
 
-
 ## Add to existing app
 
 <Steps>
@@ -92,31 +98,29 @@ Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `v
 To access Cloudflare APIs (such as [D1](/d1/) and [KV](/kv/)), use [bindings](/workers/runtime-apis/bindings/) which are available via the `env` object [imported from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global).
 
 ```ts
-import { env } from 'cloudflare:workers'
+import { env } from "cloudflare:workers";
 // Key-value store
-env.KV.get('my-key')
+env.KV.get("my-key");
 // Environment variable
-env.LOG_LEVEL
+env.LOG_LEVEL;
 // ...
 ```
 
 > Example of using Cloudflare D1:
+>
 > <PackageManagers
 > 	type="create"
 > 	pkg="vike@latest"
 > 	args="--react --hono --drizzle --cloudflare"
 > />
-> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an ORM.
+> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an
+> ORM.
 
 ## TypeScript
 
 If you use TypeScript, run [`wrangler types`](/workers/wrangler/commands/general/#types) whenever you change your Cloudflare configuration to update the `worker-configuration.d.ts` file.
 
-<PackageManagers
-	type="exec"
-	pkg="wrangler"
-	args="types"
-/>
+<PackageManagers type="exec" pkg="wrangler" args="types" />
 
 Then commit:
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vue.mdx b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
index e3f18d090e9e901..155e8df3c77be19 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vue.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
@@ -34,9 +34,9 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
 	args="my-vue-app --framework=vue"
 />
 
-    		 <Details header="How is this project set up?">
-        			Below is a simplified file tree of the project.
-        			<FileTree>
+		 <Details header="How is this project set up?">
+    			Below is a simplified file tree of the project.
+    			<FileTree>
     						- my-vue-app
     							- src/
     									- App.vue
@@ -47,17 +47,17 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
     							- wrangler.jsonc
         			</FileTree>
 
-        			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
-        			In this file:
-        					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
-        					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
-        					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
+    			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
+    			In this file:
+    					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
+    					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
+    					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-    						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
+						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-    						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
-    						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
-        		</Details>
+						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
+						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
+    		</Details>
 
 ## 2. Develop locally with the [Cloudflare Vite plugin](/workers/vite-plugin/)
 
diff --git a/src/content/docs/workers/get-started/dashboard.mdx b/src/content/docs/workers/get-started/dashboard.mdx
index 927871405d844f0..93f5ddc844d62d9 100644
--- a/src/content/docs/workers/get-started/dashboard.mdx
+++ b/src/content/docs/workers/get-started/dashboard.mdx
@@ -29,14 +29,15 @@ To get started with a new Workers application:
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
-3. Select **Create application**. From here, you can:
-    * Select from the gallery of production-ready templates
-    * Import an existing Git repository on your own account
-    * Let Cloudflare clone and bootstrap a public repository containing a Workers application.
+2. Select **Create application**. From here, you can:
+   - Select from the gallery of production-ready templates
+   - Import an existing Git repository on your own account
+   - Let Cloudflare clone and bootstrap a public repository containing a Workers application.
 3. Once you have connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and select **Deploy**.
 4. Cloudflare will kick off a new build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain.
 
 ## Continue development
+
 Applications started in the dashboard are set up with Git to help kickstart your development workflow. To continue developing on your repository, you can run:
 
 ```bash
@@ -60,8 +61,8 @@ git commit -m "your message"
 git push origin main
 ```
 
-
 To do more:
+
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.
diff --git a/src/content/docs/workers/get-started/quickstarts.mdx b/src/content/docs/workers/get-started/quickstarts.mdx
index c4c9aaa383a02c3..5b4c0d7dd74919f 100644
--- a/src/content/docs/workers/get-started/quickstarts.mdx
+++ b/src/content/docs/workers/get-started/quickstarts.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: get-started
 title: Templates
 sidebar:
diff --git a/src/content/docs/workers/languages/javascript/index.mdx b/src/content/docs/workers/languages/javascript/index.mdx
index a2697d4edad3d26..ad25a7a59321ff9 100644
--- a/src/content/docs/workers/languages/javascript/index.mdx
+++ b/src/content/docs/workers/languages/javascript/index.mdx
@@ -8,16 +8,15 @@ products:
   - workers
 ---
 
-
 The Workers platform is designed to be [JavaScript standards compliant](https://ecma-international.org/publications-and-standards/standards/ecma-262/) and web-interoperable, and supports JavaScript standards, as defined by [TC39](https://tc39.es/) (ECMAScript). Wherever possible, it uses web platform APIs, so that code can be reused across client and server, as well as across [WinterCG](https://wintercg.org/) JavaScript runtimes.
 
 Refer to [Runtime APIs](/workers/runtime-apis/) for more information on specific JavaScript APIs available in Workers.
 
 ### Resources
 
-* [Getting Started](/workers/get-started/guide/)
-* [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
-* [TypeScript type definitions](https://github.com/cloudflare/workers-types)
-* [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
-* [Tutorials](/workers/tutorials/)
-* [Examples](/workers/examples/?languages=JavaScript)
+- [Getting Started](/workers/get-started/guide/)
+- [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
+- [TypeScript type definitions](https://github.com/cloudflare/workers-types)
+- [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
+- [Tutorials](/workers/tutorials/)
+- [Examples](/workers/examples/?languages=JavaScript)
diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx
index d45ef218a482019..57b1c75a4621975 100644
--- a/src/content/docs/workers/observability/errors.mdx
+++ b/src/content/docs/workers/observability/errors.mdx
@@ -15,22 +15,21 @@ Review Workers errors and exceptions.
 
 When a Worker running in production has an error that prevents it from returning a response, the client will receive an error page with an error code, defined as follows:
 
-| Error code | Meaning                                                                                                                                         |
-| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `1101`     | Worker threw a JavaScript exception.                                                                                                            |
-| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                           |
-| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                         |
-| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                           |
-| `1021`     | Worker has requested a host it cannot access.                                                                                                   |
-| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                       |
-| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                               |
-| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                       |
+| Error code | Meaning                                                                                                                                                                                                                                                             |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `1101`     | Worker threw a JavaScript exception.                                                                                                                                                                                                                                |
+| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                                                                                                                                               |
+| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                                                                                                                                             |
+| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                                                                                                                                               |
+| `1021`     | Worker has requested a host it cannot access.                                                                                                                                                                                                                       |
+| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                                                                                                                                           |
+| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                                                                                                                                                   |
+| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                                                                                                                                          |
 | `1042`     | Worker tried to fetch from another Worker on the same zone, which is only [supported](/workers/runtime-apis/fetch/) when the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) is used. |
-| `10162`    | Module has an unsupported Content-Type.                                                                                                         |
+| `10162`    | Module has an unsupported Content-Type.                                                                                                                                                                                                                             |
 
 Other `11xx` errors generally indicate a problem with the Workers runtime itself. Refer to the [status page](https://www.cloudflarestatus.com) if you are experiencing an error.
 
-
 ### Loop limit
 
 A Worker cannot call itself or another Worker more than 16 times. In order to prevent infinite loops between Workers, the [`CF-EW-Via`](/fundamentals/reference/http-headers/#cf-ew-via) header's value is an integer that indicates how many invocations are left. Every time a Worker is invoked, the integer will decrement by 1. If the count reaches zero, a [`1019`](#error-pages-generated-by-workers) error is returned.
@@ -191,23 +190,23 @@ If you need to share state across requests, consider using [Durable Objects](/du
 
 These errors occur when a Worker is uploaded or modified.
 
-| Error code | Meaning                                                                                                                         |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| `10006`    | Could not parse your Worker's code.                                                                                             |
-| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                       |
-| `10015`    | Account is not entitled to use Workers.                                                                                         |
-| `10016`    | Invalid Worker name.                                                                                                            |
-| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.             |
-| `10026`    | Could not parse request body.                                                                                                   |
-| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size). |
-| `10035`    | Multiple attempts to modify a resource at the same time                                                                         |
-| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                           |
-| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                        |
-| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                     |
-| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables).     |
-| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                           |
-| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                        |
-| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.              |
+| Error code | Meaning                                                                                                                     |
+| ---------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `10006`    | Could not parse your Worker's code.                                                                                         |
+| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                   |
+| `10015`    | Account is not entitled to use Workers.                                                                                     |
+| `10016`    | Invalid Worker name.                                                                                                        |
+| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.         |
+| `10026`    | Could not parse request body.                                                                                               |
+| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size).                               |
+| `10035`    | Multiple attempts to modify a resource at the same time                                                                     |
+| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                       |
+| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                    |
+| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                 |
+| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables). |
+| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                       |
+| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                    |
+| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.          |
 
 ### Validation Errors (10021)
 
@@ -236,6 +235,7 @@ Runtime errors will occur within the runtime, do not throw up an error page, and
 ## Identify errors: Workers Metrics
 
 To review whether your application is experiencing any downtime or returning any errors:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
index 586b51c9eed17af..105fea21b7e83dc 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
@@ -8,10 +8,11 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Axiom is a serverless log analytics platform that helps you store, search, and analyze massive amounts of data. By exporting your Cloudflare Workers application telemetry to Axiom, you can:
-- Store and query logs and traces at scale 
+
+- Store and query logs and traces at scale
 - Create dashboards and alerts to monitor your Workers
 
 ![Trace view with timing information displayed on a timeline](~/assets/images/workers-observability/axiom-example.png)
@@ -29,6 +30,7 @@ Before you begin, ensure you have:
 ## Step 1: Create a dataset
 
 If you don't already have a dataset to send data to:
+
 1. Log in to your [Axiom account](https://app.axiom.co/)
 2. Navigate to **Datasets** in the left sidebar
 3. Click **New Dataset**
@@ -56,6 +58,7 @@ Now you'll create destinations in the Cloudflare dashboard that point to Axiom.
 ### Axiom OTLP endpoints
 
 Axiom provides separate OTLP endpoints for traces and logs:
+
 - **Traces**: `https://api.axiom.co/v1/traces`
 - **Logs**: `https://api.axiom.co/v1/logs`
 
@@ -67,13 +70,13 @@ Axiom provides separate OTLP endpoints for traces and logs:
    - **Destination Name**: `axiom-traces` (or any descriptive name)
    - **Destination Type**: Select **Traces**
    - **OTLP Endpoint**: `https://api.axiom.co/v1/traces` (or `/v1/logs`)
-   - **Custom Headers**: Add two required headers: 
-     -  Authentication header 
-        - Header name: `Authorization`
-        - Header value: `Bearer <your-api-token>` 
-     - Dataset header: 
+   - **Custom Headers**: Add two required headers:
+     - Authentication header
+       - Header name: `Authorization`
+       - Header value: `Bearer <your-api-token>`
+     - Dataset header:
        - Header name: `X-Axiom-Dataset`
-       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`) 
+       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`)
 4. Click **Save**
 
 ## Step 3: Configure your Worker
@@ -104,6 +107,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Axiom. 
+It may take a few minutes after deployment for data to appear in Axiom.
 :::
-
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
index 8592f3ba188c813..996992e42bfb4d6 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
@@ -7,9 +7,11 @@ sidebar:
 products:
   - workers
 ---
-import {WranglerConfig} from "~/components";
+
+import { WranglerConfig } from "~/components";
 
 Grafana Cloud is a fully managed observability platform that provides visualization, alerting, and analytics for your telemetry data. By exporting your Cloudflare Workers telemetry to Grafana Cloud, you can:
+
 - Visualize distributed traces in **Grafana Tempo** to understand request flows and performance bottlenecks
 - Query and analyze logs in **Grafana Loki** alongside your traces
 
@@ -30,24 +32,25 @@ Before you begin, ensure you have:
 2. From your organization's home page, navigate to **Connections** → **Add new connection**
 3. Search for "OpenTelemetry" and select **OpenTelemetry (OTLP)**
 4. Select **Quickstart** then select **JavaScript**
-6. Click **Create a new token**
-7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
-8. Click on **Close** without copying the token
-9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
+5. Click **Create a new token**
+6. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
+7. Click on **Close** without copying the token
+8. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
 
+## Step 2: Set up destination
 
-## Step 2: Set up destination 
 1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
 2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
-3. From Grafana, copy your Otel endpoint, auth header, and auth value 
-  * Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs) 
-  * Your custom header should include: 
-      * Your auth header name `Authorization`
-      * Your auth header value `Basic MTMxxx...`
+3. From Grafana, copy your Otel endpoint, auth header, and auth value
+
+- Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs)
+- Your custom header should include:
+  - Your auth header name `Authorization`
+  - Your auth header value `Basic MTMxxx...`
 
 ## Step 3: Configure your Worker
 
-With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export. 
+With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
 
 <WranglerConfig>
 
@@ -70,8 +73,8 @@ With your destination created in the Cloudflare dashboard, update your Worker's
 
 </WranglerConfig>
 
-After updating your configuration, deploy your Worker for the changes to take effect. 
+After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Grafana Cloud. 
+It may take a few minutes after deployment for data to appear in Grafana Cloud.
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
index 847f103352c625f..9b00d57e583249b 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
@@ -8,9 +8,10 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Honeycomb is an observability platform built for high-cardinality data that helps you understand and debug your applications. By exporting your Cloudflare Workers application telemetry to Honeycomb, you can:
+
 - Visualize traces to understand request flows and identify performance bottlenecks
 - Query and analyze logs with unlimited dimensionality across any attribute
 - Create custom queries and dashboards to monitor your Workers
@@ -44,11 +45,12 @@ The API key will look something like: `hcaik_01hq...`
 
 ## Step 2: Configure Cloudflare destinations
 
-Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb. 
+Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb.
 
 ### Honeycomb OTLP endpoints
 
 Honeycomb provides separate OTLP endpoints for traces and logs:
+
 - **Traces**: `https://api.honeycomb.io/v1/traces`
 - **Logs**: `https://api.honeycomb.io/v1/logs`
 
@@ -107,5 +109,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Honeycomb. 
+It may take a few minutes after deployment for data to appear in Honeycomb.
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
index fd45dd3b86981fd..fbafabca9cdfc0f 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
@@ -25,18 +25,18 @@ You can export the following types of telemetry data:
 
 Below are common OTLP endpoint formats for popular observability providers. Refer to your provider's documentation for specific details and authentication requirements.
 
-| Provider                                                                                | Traces Endpoint                                              | Logs Endpoint                                                |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)         | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
-| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
-| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)              | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
-| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                 | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
-| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)               | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
-| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)             | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
-| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)              | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
-| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/) | `https://otlp.nr-data.net/v1/traces` | `https://otlp.nr-data.net/v1/logs` |
-| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp` | N/A |
-| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp) | `http://splunk.internal:4318/v1/traces` | `http://splunk.internal:4318/v1/logs` |
+| Provider                                                                                          | Traces Endpoint                                              | Logs Endpoint                                                |
+| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)                   | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
+| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/)           | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
+| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)                        | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
+| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                           | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
+| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)                         | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
+| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)                       | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
+| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)                        | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
+| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/)  | `https://otlp.nr-data.net/v1/traces`                         | `https://otlp.nr-data.net/v1/logs`                           |
+| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp`          | N/A                                                          |
+| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp)                          | `http://splunk.internal:4318/v1/traces`                      | `http://splunk.internal:4318/v1/logs`                        |
 
 :::note[Authentication]
 Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.
@@ -109,11 +109,11 @@ After creating a destination, you can monitor its health and delivery status in
 
 ### Status indicators
 
-| Status                  | Description                                                             | Troubleshooting                                                                                               |
-| ----------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                               |
+| Status                  | Description                                                             | Troubleshooting                                                                                                |
+| ----------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                                |
 | **Never run**           | No data has been delivered to this destination.                         | •Check if your Worker is receiving traffic <br /> • Review sampling rates (low rates generate less data)<br /> |
-| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                     |
+| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                      |
 
 ## Limits and pricing
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
index 0f42b67c6bb7168..69002849ba8e0f1 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 PostHog is a product analytics platform that helps you understand user behavior and debug issues. By exporting your Cloudflare Workers application telemetry to PostHog, you can:
 
@@ -41,10 +41,10 @@ The API key should look something like: `phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 PostHog has different endpoints depending on your data region:
 
-| Region | Logs Endpoint |
-| ------ | ------------- |
+| Region           | Logs Endpoint                        |
+| ---------------- | ------------------------------------ |
 | **US** (default) | `https://us.i.posthog.com/i/v1/logs` |
-| **EU** | `https://eu.i.posthog.com/i/v1/logs` |
+| **EU**           | `https://eu.i.posthog.com/i/v1/logs` |
 
 You can find your region in your PostHog project settings or by checking the URL when logged into PostHog (either `us.posthog.com` or `eu.posthog.com`).
 
@@ -104,6 +104,7 @@ Once your Worker is deployed and receiving traffic:
 3. Your Worker logs will appear with severity levels, timestamps, and attributes
 
 You can filter logs by:
+
 - **Severity level** (trace, debug, info, warn, error, fatal)
 - **Time range**
 - **Custom attributes** added to your log entries
@@ -115,25 +116,25 @@ You can add custom attributes to your logs using standard `console` methods with
 
 ```javascript
 export default {
-  async fetch(request, env) {
-    // Basic logging
-    console.log("Processing request");
-
-    // Logs with additional context
-    console.info("User action", {
-      userId: "user_123",
-      action: "api_call",
-      path: new URL(request.url).pathname
-    });
-
-    // Error logging with details
-    console.error("Request failed", {
-      error: "Connection timeout",
-      retryCount: 3
-    });
-
-    return new Response("OK");
-  }
+	async fetch(request, env) {
+		// Basic logging
+		console.log("Processing request");
+
+		// Logs with additional context
+		console.info("User action", {
+			userId: "user_123",
+			action: "api_call",
+			path: new URL(request.url).pathname,
+		});
+
+		// Error logging with details
+		console.error("Request failed", {
+			error: "Connection timeout",
+			retryCount: 3,
+		});
+
+		return new Response("OK");
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
index 57d0992698f5e67..1c602ea7225b551 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
@@ -8,9 +8,10 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Sentry is a software monitoring tool that helps developers identify and debug performance issues and errors. From end-to-end distributed tracing to performance monitoring, Sentry provides code-level observability that makes it easy to diagnose issues and learn continuously about your application code health across systems and services. By exporting your Cloudflare Workers application telemetry to Sentry, you can:
+
 - Query logs and traces in Sentry
 - Create custom alerts and dashboards to monitor your Workers
 
@@ -37,6 +38,7 @@ If you don't already have a Sentry project to send data to, you'll need to creat
 ## Step 2: Get your Sentry OTLP endpoints
 
 Sentry provides separate OTLP endpoints for traces and logs which you can use to send your telemetry data to Sentry.
+
 - **Traces**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`
 - **Logs**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`
 
@@ -57,23 +59,24 @@ To set up a destination in the Cloudflare dashboard, navigate to your Cloudflare
 ### Traces Destination
 
 To configure your traces destination, click **Add destination** and configure the following:
-   - **Destination Name**: `sentry-traces` (or any descriptive name)
-   - **Destination Type**: Select **Traces**
-   - **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
-   - **Custom Headers**: Add the Sentry authentication header:
-     - Header name: `x-sentry-auth`
-     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
+
+- **Destination Name**: `sentry-traces` (or any descriptive name)
+- **Destination Type**: Select **Traces**
+- **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
+- **Custom Headers**: Add the Sentry authentication header:
+  - Header name: `x-sentry-auth`
+  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ### Logs destination
 
 To configure your logs destination, click **Add destination** and configure the following:
-   - **Destination Name**: `sentry-logs` (or any descriptive name)
-   - **Destination Type**: Select **Logs**
-   - **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
-   - **Custom Headers**: Add the Sentry authentication header:
-     - Header name: `x-sentry-auth`
-     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
+- **Destination Name**: `sentry-logs` (or any descriptive name)
+- **Destination Type**: Select **Logs**
+- **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
+- **Custom Headers**: Add the Sentry authentication header:
+  - Header name: `x-sentry-auth`
+  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ## Step 4: Configure your Worker
 
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 72b1c12297f3d02..2b21d8e285a2a6b 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -17,10 +17,8 @@ import { WranglerConfig, DashButton } from "~/components";
 
 :::caution
 
-
 Workers Trace Events Logpush is not available for zones on the [Cloudflare China Network](/china-network/).
 
-
 :::
 
 ## Verify your Logpush access
@@ -30,6 +28,7 @@ Minimum required Wrangler version: 2.2.0. Check your version by running `wrangle
 :::
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
+
 1. In the Cloudflare dashboard, go to the **Members** page.
 
    <DashButton url="/?to=/:account/members" />
@@ -43,6 +42,7 @@ Alternatively, create a new [API token](/fundamentals/api/get-started/create-tok
 ### Via the Cloudflare dashboard
 
 To create a Logpush job in the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Logpush** page.
 
    <DashButton url="/?to=/:account/logs" />
@@ -117,6 +117,7 @@ curl --request PUT \
 ### Dashboard
 
 To enable Logpush logging via the dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -147,30 +148,30 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-  "Exceptions": [
-    {
-      "Name": "SampleError",
-      "Message": "something went wrong",
-      "TimestampMs": 0
-    },
-    {
-      "Name": "AuthError",
-      "Message": "unable to process request authentication from client",
-      "TimestampMs": 1
-    },
-  ],
-  "Logs": [
-    {
-      "Level": "log",
-      "Message": ["Hello "],
-      "TimestampMs": 0
-    },
-    {
-      "Level": "log",
-      "Message": ["World!"],
-      "TimestampMs": 0
-    }
-  ]
+	"Exceptions": [
+		{
+			"Name": "SampleError",
+			"Message": "something went wrong",
+			"TimestampMs": 0
+		},
+		{
+			"Name": "AuthError",
+			"Message": "unable to process request authentication from client",
+			"TimestampMs": 1
+		}
+	],
+	"Logs": [
+		{
+			"Level": "log",
+			"Message": ["Hello "],
+			"TimestampMs": 0
+		},
+		{
+			"Level": "log",
+			"Message": ["World!"],
+			"TimestampMs": 0
+		}
+	]
 }
 ```
 
@@ -178,24 +179,24 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-  "Exceptions": [
-    {
-      "name": "SampleError",
-      "message": "something went wrong",
-      "TimestampMs": 0
-    },
-    {
-      "name": "AuthError",
-      "message": "unable to <<<Logpush: exception messages truncated>>>",
-      "TimestampMs": 1
-    },
-  ],
-  "Logs": [
-    {
-      "Level": "log",
-      "Message": ["<<<Logpush: messages truncated>>>"],
-      "TimestampMs": 0
-    }
-  ]
+	"Exceptions": [
+		{
+			"name": "SampleError",
+			"message": "something went wrong",
+			"TimestampMs": 0
+		},
+		{
+			"name": "AuthError",
+			"message": "unable to <<<Logpush: exception messages truncated>>>",
+			"TimestampMs": 1
+		}
+	],
+	"Logs": [
+		{
+			"Level": "log",
+			"Message": ["<<<Logpush: messages truncated>>>"],
+			"TimestampMs": 0
+		}
+	]
 }
 ```
diff --git a/src/content/docs/workers/observability/logs/real-time-logs.mdx b/src/content/docs/workers/observability/logs/real-time-logs.mdx
index 65b48530222963a..32ea43c6b2fedf7 100644
--- a/src/content/docs/workers/observability/logs/real-time-logs.mdx
+++ b/src/content/docs/workers/observability/logs/real-time-logs.mdx
@@ -25,6 +25,7 @@ Real-time logs are not available for zones on the [Cloudflare China Network](/ch
 ## View logs from the dashboard
 
 To view real-time logs associated with any deployed Worker using the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
index 1f162b257fc1d15..88e00843194056a 100644
--- a/src/content/docs/workers/observability/logs/workers-logs.mdx
+++ b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -53,7 +53,7 @@ You must add the observability setting for your Worker to write logs to Workers
 
 [Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for an environment named `staging`: 1. Add the following configuration below `[env.staging]`
 
-    <WranglerConfig>
+<WranglerConfig>
 
     ```jsonc
     {
@@ -70,8 +70,8 @@ You must add the observability setting for your Worker to write logs to Workers
 
     </WranglerConfig>
 
-    2. Deploy your Worker with `npx wrangler deploy -e staging`
-    3. Repeat step 1 and 2 for each environment.
+2. Deploy your Worker with `npx wrangler deploy -e staging`
+3. Repeat step 1 and 2 for each environment.
 
 ## View logs from the dashboard
 
diff --git a/src/content/docs/workers/observability/metrics-and-analytics.mdx b/src/content/docs/workers/observability/metrics-and-analytics.mdx
index ef28c321eb02f2a..3f270c3f47959fb 100644
--- a/src/content/docs/workers/observability/metrics-and-analytics.mdx
+++ b/src/content/docs/workers/observability/metrics-and-analytics.mdx
@@ -54,6 +54,7 @@ Subrequests are requests triggered by calling `fetch` from within a Worker. A su
 ### Wall time per execution
 
 <GlossaryTooltip term="wall-clock time">Wall time</GlossaryTooltip> represents
+
 the elapsed time in milliseconds between the start of a Worker invocation, and
 when the Workers runtime determines that no more JavaScript needs to run.
 Specifically, wall time per execution chart measures the wall time that the
diff --git a/src/content/docs/workers/observability/source-maps.mdx b/src/content/docs/workers/observability/source-maps.mdx
index 2872e097f8f75a0..20d213c75c986ae 100644
--- a/src/content/docs/workers/observability/source-maps.mdx
+++ b/src/content/docs/workers/observability/source-maps.mdx
@@ -45,10 +45,8 @@ You can then view the stack trace when streaming [real-time logs](/workers/obser
 
 :::note
 
-
 The source map is retrieved after your Worker invocation completes — it's an asynchronous process that does not impact your Worker's CPU utilization or performance. Source maps are not accessible inside the Worker at runtime, if you `console.log()` the [stack property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/stack) within a Worker, you will not get a deobfuscated stack trace.
 
-
 :::
 
 When Cloudflare attempts to remap a stack trace to the Worker's source map, it does so line-by-line, remapping as much as possible. If a line of the stack trace cannot be remapped for any reason, Cloudflare will leave that line of the stack trace unchanged, and continue to the next line of the stack trace.
@@ -59,10 +57,9 @@ When Cloudflare attempts to remap a stack trace to the Worker's source map, it d
 Minimum required Wrangler version for source maps: 3.46.0. Check your version by running `wrangler --version`.
 :::
 
-
-| Description                    | Limit         |
-| ------------------------------ | ------------- |
-| Maximum Source Map Size        | 15 MB gzipped |
+| Description             | Limit         |
+| ----------------------- | ------------- |
+| Maximum Source Map Size | 15 MB gzipped |
 
 ## Example
 
@@ -88,6 +85,6 @@ With **source maps uploaded**: all methods reference the correct files and line
 
 ## Related resources
 
-* [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
-* [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
-* [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
+- [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
+- [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
+- [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
diff --git a/src/content/docs/workers/platform/betas.mdx b/src/content/docs/workers/platform/betas.mdx
index 99cebde932f6ce9..e151ed5f512fd42 100644
--- a/src/content/docs/workers/platform/betas.mdx
+++ b/src/content/docs/workers/platform/betas.mdx
@@ -12,11 +12,11 @@ products:
 
 These are the current alphas and betas relevant to the Cloudflare Workers platform.
 
-* **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
-* Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
+- **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
+- Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
 
 | Product                                           | Private Beta | Public Beta | More Info                                                                   |
 | ------------------------------------------------- | ------------ | ----------- | --------------------------------------------------------------------------- |
-| Email Workers                                     |              | ✅           | [Docs](/email-routing/email-workers/)                                       |
-| Green Compute                                     |              | ✅           | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
-| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅           | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
+| Email Workers                                     |              | ✅          | [Docs](/email-routing/email-workers/)                                       |
+| Green Compute                                     |              | ✅          | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
+| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅          | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
diff --git a/src/content/docs/workers/platform/built-with-cloudflare.mdx b/src/content/docs/workers/platform/built-with-cloudflare.mdx
index b9ae5fb6977f6da..42aafcb95946784 100644
--- a/src/content/docs/workers/platform/built-with-cloudflare.mdx
+++ b/src/content/docs/workers/platform/built-with-cloudflare.mdx
@@ -45,4 +45,4 @@ The Built with Cloudflare button is an SVG and can be embedded anywhere. Use the
 https://workers.cloudflare.com/built-with-cloudflare.svg
 ```
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/docs/workers/platform/changelog/historical-changelog.mdx b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
index 0b2cbd209519aa6..6ecdf4d3609fbdb 100644
--- a/src/content/docs/workers/platform/changelog/historical-changelog.mdx
+++ b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
@@ -16,374 +16,374 @@ This page tracks changes made to Cloudflare Workers before 2023. For a view of m
 
 ## 2022-12-16
 
-* Conditional `PUT` requests have been fixed in the R2 bindings API.
+- Conditional `PUT` requests have been fixed in the R2 bindings API.
 
 ## 2022-12-02
 
-* Queues no longer support calling `send()` with an undefined JavaScript value as the message.
+- Queues no longer support calling `send()` with an undefined JavaScript value as the message.
 
 ## 2022-11-30
 
-* The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
-* Extended the R2 binding API to include support for multipart uploads.
+- The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
+- Extended the R2 binding API to include support for multipart uploads.
 
 ## 2022-11-17
 
-* V8 update: 10.6 → 10.8
+- V8 update: 10.6 → 10.8
 
 ## 2022-11-02
 
-* Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
+- Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
 
 ## 2022-10-21
 
-* The alarm retry limit will no longer apply to errors that are our fault.
-* Compatibility dates have been added for multiple flags including the new streams implementation.
-* `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
+- The alarm retry limit will no longer apply to errors that are our fault.
+- Compatibility dates have been added for multiple flags including the new streams implementation.
+- `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
 
 ## 2022-10-10
 
-* Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
-* `console.log` now prints more information about certain objects, for example Promises.
-* The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
+- Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
+- `console.log` now prints more information about certain objects, for example Promises.
+- The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
 
 ## 2022-09-16
 
-* R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
-* Allow deleting multiple keys at once in R2 bindings.
-* Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
-* User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
-* Updated V8 to 10.6.
+- R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
+- Allow deleting multiple keys at once in R2 bindings.
+- Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
+- User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
+- Updated V8 to 10.6.
 
 ## 2022-08-12
 
-* A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
-* When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
-* Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
-* Validation errors during Worker upload for module scripts now include correct line and column numbers.
-* Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
+- A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
+- When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
+- Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
+- Validation errors during Worker upload for module scripts now include correct line and column numbers.
+- Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
 
 ## 2022-07-08
 
-* Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
+- Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
 
 ## 2022-06-24
 
-* `wrangler dev` in global network preview mode now supports scheduling alarms.
-* R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
-* Some Web Cryptography API error messages include more information now.
-* Updated V8 from 10.2 to 10.3.
+- `wrangler dev` in global network preview mode now supports scheduling alarms.
+- R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
+- Some Web Cryptography API error messages include more information now.
+- Updated V8 from 10.2 to 10.3.
 
 ## 2022-06-18
 
-* Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
-* The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
+- Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
+- The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
 
 ## 2022-06-09
 
-* No externally-visible changes.
+- No externally-visible changes.
 
 ## 2022-06-03
 
-* It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
-* Preview in Quick Edit now correctly uses the correct R2 bindings.
-* Updated V8 from 10.1 to 10.2.
+- It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
+- Preview in Quick Edit now correctly uses the correct R2 bindings.
+- Updated V8 from 10.1 to 10.2.
 
 ## 2022-05-26
 
-* The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
-* R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
+- The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
+- R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
 
 ## 2022-05-19
 
-* R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
-* ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
-* Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
-* R2: Better runtime support for additional ranges.
-* R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
+- R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
+- ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
+- Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
+- R2: Better runtime support for additional ranges.
+- R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
 
 ## 2022-05-12
 
-* Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
-* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-* Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
-* R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
-* R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
-* Added `startAfter` option to the `list()` method in the Durable Object storage API.
+- Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
+- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+- Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+- R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
+- R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
+- Added `startAfter` option to the `list()` method in the Durable Object storage API.
 
 ## 2022-05-05
 
-* `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
-* Fix generated types for Date.
-* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-* Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+- `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
+- Fix generated types for Date.
+- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+- Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
 
 ## 2022-04-29
 
-* Minor V8 update: 10.0 → 10.1.
-* R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
+- Minor V8 update: 10.0 → 10.1.
+- R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
 
 ## 2022-04-22
 
-* Major V8 update: 9.9 → 10.0.
+- Major V8 update: 9.9 → 10.0.
 
 ## 2022-04-14
 
-* Performance and stability improvements.
+- Performance and stability improvements.
 
 ## 2022-04-08
 
-* The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
-* R2 error responses now include better details.
+- The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
+- R2 error responses now include better details.
 
 ## 2022-03-24
 
-* A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
-* When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
-* The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
+- A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
+- When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
+- The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
 
 ## 2022-03-17
 
-* The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
-* When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
-* Fix R2 publish date rendering.
-* Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
-* When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
+- The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
+- When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
+- Fix R2 publish date rendering.
+- Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
+- When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
 
 ## 2022-03-11
 
-* Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
-* Implementations of `CompressionStream` and `DecompressionStream` are now available.
+- Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
+- Implementations of `CompressionStream` and `DecompressionStream` are now available.
 
 ## 2022-03-04
 
-* Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
-* With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
-* A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
-* The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
-* An implementation of `URLPattern` is now available.
+- Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
+- With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
+- A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
+- The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
+- An implementation of `URLPattern` is now available.
 
 ## 2022-02-25
 
-* The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
-* Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
-* Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
+- The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
+- Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
+- Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
 
 ## 2022-02-18
 
-* `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
+- `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
 
 ## 2022-02-11
 
-* WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
+- WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
 
 ## 2022-02-05
 
-* Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
-* `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
-* A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
+- Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
+- `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
+- A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
 
 ## 2022-01-28
 
-* No user-visible changes.
+- No user-visible changes.
 
 ## 2022-01-20
 
-* Updated V8: 9.7 → 9.8.
+- Updated V8: 9.7 → 9.8.
 
 ## 2022-01-17
 
-* `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
-* Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
+- `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
+- Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
 
 ## 2022-01-07
 
-* The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
+- The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
 
 ## 2021-12-22
 
-* Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
+- Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
 
 ## 2021-12-10
 
-* Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
-* `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
-* Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
-* `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
-* Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
-* Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
+- Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
+- `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
+- Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
+- `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
+- Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
+- Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
 
 ## 2021-12-02
 
-* The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
-* Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
+- The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
+- Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
 
 ## 2021-11-19
 
-* Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
-* Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
-* [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
+- Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
+- Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
+- [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
 
 ## 2021-11-12
 
-* The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
-* Unhandled rejection warnings will be printed to the inspector console.
+- The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
+- Unhandled rejection warnings will be printed to the inspector console.
 
 ## 2021-11-05
 
-* Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
-* Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams\_byob\_reader\_detaches\_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
+- Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
+- Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams_byob_reader_detaches_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
 
 ## 2021-10-21
 
-* Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
-* The `unhandledrejection` and `rejectionhandled` events are now supported.
-* The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
-* Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
-* The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
+- Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
+- The `unhandledrejection` and `rejectionhandled` events are now supported.
+- The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
+- Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
+- The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
 
 ## 2021-10-14
 
-* `request.signal` will always return an `AbortSignal`.
-* Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
-* Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
+- `request.signal` will always return an `AbortSignal`.
+- Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
+- Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
 
 ## 2021-09-24
 
-* The `AbortController` and `AbortSignal` objects are now available.
-* The Web Platform `queueMicrotask` API is now available.
-* It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
-* The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
-* Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
-* The `Event` object now supports most standard methods and properties.
-* V8 updated from 9.3 to 9.4.
+- The `AbortController` and `AbortSignal` objects are now available.
+- The Web Platform `queueMicrotask` API is now available.
+- It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
+- The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
+- Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
+- The `Event` object now supports most standard methods and properties.
+- V8 updated from 9.3 to 9.4.
 
 ## 2021-09-03
 
-* The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
-* Durable Objects are now scheduled more evenly around a colocation (colo).
+- The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
+- Durable Objects are now scheduled more evenly around a colocation (colo).
 
 ## 2021-08-05
 
-* No user-facing changes. Just bug fixes & internal maintenance.
+- No user-facing changes. Just bug fixes & internal maintenance.
 
 ## 2021-07-30
 
-* Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
-* Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
+- Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
+- Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
 
 ## 2021-07-23
 
-* Performance and stability improvements.
+- Performance and stability improvements.
 
 ## 2021-07-16
 
-* Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
-* Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
-* Durable Object constructors may now initiate I/O, such as `fetch()` calls.
-* Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
-* In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
+- Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
+- Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
+- Durable Object constructors may now initiate I/O, such as `fetch()` calls.
+- Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
+- In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
 
 ## 2021-07-13
 
-* The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
+- The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
 
 ## 2021-07-01
 
-* Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
-* Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
+- Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
+- Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
 
 ## 2021-06-27
 
-* WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
+- WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
 
 ## 2021-06-17
 
 Changes this week:
 
-* Updated V8 from 9.1 to 9.2.
-* `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
+- Updated V8 from 9.1 to 9.2.
+- `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
 
 ## 2021-06-11
 
 Changes this week:
 
-* Turn on V8 Sparkplug compiler.
-* Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
+- Turn on V8 Sparkplug compiler.
+- Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
 
 ## 2021-06-04
 
 Changes this week:
 
-* WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
-* `request.cf` is no longer missing when writing Workers using modules syntax.
+- WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
+- `request.cf` is no longer missing when writing Workers using modules syntax.
 
 ## 2021-05-14
 
 Changes this week:
 
-* Improve error messages coming from the WebCrypto API.
-* Updated V8: 9.0 → 9.1
+- Improve error messages coming from the WebCrypto API.
+- Updated V8: 9.0 → 9.1
 
 Changes in an earlier release:
 
-* WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
-* WebCrypto: Add support for RSA-OAEP
-* WebCrypto: HKDF implemented.
-* Fix recently-introduced backwards clock jumps in Durable Objects.
-* `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1\_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
+- WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
+- WebCrypto: Add support for RSA-OAEP
+- WebCrypto: HKDF implemented.
+- Fix recently-introduced backwards clock jumps in Durable Objects.
+- `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
 
 ## 2021-04-29
 
 Changes this week:
 
-* WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
-* The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
+- WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
+- The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
 
 ## 2021-04-23
 
 Changes this week:
 
-* In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
-* For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
-* When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
-* Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
-* When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
-* When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-* When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-* `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
+- In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
+- For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
+- When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
+- Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
+- When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
+- When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+- When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+- `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
 
 ## 2021-04-19
 
 Changes since the last post on 3/26:
 
-* Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
-* Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
-* Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
-* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-* Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
-* WebCrypto: Key derivation for ECDH.
-* WebCrypto: Support ECDH key generation & import.
-* WebCrypto: Support ECDSA key generation.
-* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-* Improved exception messages thrown by the WebCrypto API somewhat.
-* `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
-* `passThroughOnException` is now available under the ctx argument to module handlers
-* Reliability improvements for Durable Objects
-* Reliability improvements for Durable Objects persistent storage API
-* `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
+- Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
+- Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
+- Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
+- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+- Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
+- WebCrypto: Key derivation for ECDH.
+- WebCrypto: Support ECDH key generation & import.
+- WebCrypto: Support ECDSA key generation.
+- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+- Improved exception messages thrown by the WebCrypto API somewhat.
+- `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
+- `passThroughOnException` is now available under the ctx argument to module handlers
+- Reliability improvements for Durable Objects
+- Reliability improvements for Durable Objects persistent storage API
+- `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
 
 ## 2021-03-26
 
 Changes this week:
 
-* Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
+- Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
 
 ## 2021-03-11
 
 New this week:
 
-* When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
+- When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
 
 (It looks like no release notes were posted the last few weeks, but there were no new user-visible changes to report.)
 
@@ -391,56 +391,56 @@ New this week:
 
 Changes this week:
 
-* In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
-* A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
+- In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
+- A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
 
 ## 2021-02-05
 
 New this week:
 
-* V8 has been updated from 8.8 to 8.9.
-* During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
+- V8 has been updated from 8.8 to 8.9.
+- During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
 
 New last week (forgot to post):
 
-* Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
+- Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
 
 ## 2021-01-22
 
 New in the past week:
 
-* Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
+- Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
 
 ## 2021-01-14
 
 Changes this week:
 
-* Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
+- Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
 
 ## 2021-01-07
 
 Changes this week:
 
-* No user-visible changes.
+- No user-visible changes.
 
 Changes in the prior release:
 
-* Fixed delivery of WebSocket “error” events.
-* Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
+- Fixed delivery of WebSocket “error” events.
+- Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
 
 ## 2020-12-10
 
 Changes this week:
 
-* Major V8 update: 8.7.220.29 -> 8.8.278.8
+- Major V8 update: 8.7.220.29 -> 8.8.278.8
 
 ## 2019-09-19
 
 Changes this week:
 
-* Unannounced new feature. (Stay tuned.)
-* Enforced new limit on concurrent subrequests (see below).
-* Stability improvements.
+- Unannounced new feature. (Stay tuned.)
+- Enforced new limit on concurrent subrequests (see below).
+- Stability improvements.
 
 **Concurrent Subrequest Limit**
 
@@ -472,129 +472,129 @@ We chose the limit of 6 concurrent connections based on the fact that Chrome enf
 
 Changes this week:
 
-* Durable Objects storage API now supports listing keys by prefix.
-* Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
-* `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
-* Fixed off-by-one line numbers in Worker exceptions.
-* Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
-* Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
+- Durable Objects storage API now supports listing keys by prefix.
+- Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
+- `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
+- Fixed off-by-one line numbers in Worker exceptions.
+- Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
+- Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
 
 ## 2020-11-13
 
 Changes over the past week:
 
-* `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
-* Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
+- `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
+- Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
 
 ## 2020-11-05
 
 Changes this week:
 
-* Major V8 update: 8.6 -> 8.7
-* Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
+- Major V8 update: 8.6 -> 8.7
+- Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
 
 ## 2020-10-05
 
 We had our usual weekly release last week, but:
 
-* No user-visible changes.
+- No user-visible changes.
 
 ## 2020-09-24
 
 Changes this week:
 
-* Internal changes to support upcoming features.
+- Internal changes to support upcoming features.
 
 Also, a change from the 2020-09-08 release that it seems we forgot to post:
 
-* V8 major update: 8.5 -> 8.6
+- V8 major update: 8.5 -> 8.6
 
 ## 2020-08-03
 
 Changes last week:
 
-* Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
-* Upgraded V8 from 8.4 to 8.5.
+- Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
+- Upgraded V8 from 8.4 to 8.5.
 
 ## 2020-07-09
 
 Changes this week:
 
-* Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
-* Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
+- Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
+- Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
 
 Changes last week (… forgot to post):
 
-* `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
+- `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
 
 Changes the week before last (… also… forgot to post… we really need to code up a bot for this):
 
-* The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
+- The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
 
 ## 2020-05-15
 
 Changes this week:
 
-* Implemented API for yet-to-be-announced new feature.
+- Implemented API for yet-to-be-announced new feature.
 
 ## 2020-04-20
 
 Looks like we forgot to post release notes for a couple weeks. Releases still are happening weekly as always, but the “post to the community” step is insufficiently automated…
 4/2 release:
 
-* Fixed a source of long garbage collection paused in memory limit enforcement.
+- Fixed a source of long garbage collection paused in memory limit enforcement.
 
 4/9 release:
 
-* No publicly-visible changes.
+- No publicly-visible changes.
 
 4/16 release:
 
-* In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
+- In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
 
 ## 2020-03-26
 
 New this week:
 
-* Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
+- Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
 
 ## 2020-02-28
 
 New from the past two weeks:
 
-* Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
-* Major V8 update: 8.0 -> 8.1
-* Minor bug fixes.
+- Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
+- Major V8 update: 8.0 -> 8.1
+- Minor bug fixes.
 
 ## 2020-02-13
 
 Changes over the last couple weeks:
 
-* Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
-* Performance and stability improvements.
+- Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
+- Performance and stability improvements.
 
 ## 2020-01-24
 
 It has been a while since we posted release notes, partly due to the holidays. Here is what is new over the past month:
 
-* Performance and stability improvements.
-* A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
-* Updated V8 7.9 -> 8.0.
+- Performance and stability improvements.
+- A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
+- Updated V8 7.9 -> 8.0.
 
 ## 2019-12-12
 
 New this week:
 
-* We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
-* Fixed a significant source of daemonDown (1105) errors.
+- We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
+- Fixed a significant source of daemonDown (1105) errors.
 
 ## 2019-12-06
 
 Runtime release notes covering the past few weeks:
 
-* Increased total per-request `Cache.put()` limit to 5GiB.
-* Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
-* Added a helpful error message explaining AES decryption failures.
-* Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
-* More “internal errors” were converted to useful user-facing errors.
-* Stability improvements and bug fixes.
+- Increased total per-request `Cache.put()` limit to 5GiB.
+- Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
+- Added a helpful error message explaining AES decryption failures.
+- Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
+- More “internal errors” were converted to useful user-facing errors.
+- Stability improvements and bug fixes.
diff --git a/src/content/docs/workers/platform/changelog/index.mdx b/src/content/docs/workers/platform/changelog/index.mdx
index c4945fcbdae6f6c..dd80529874c454a 100644
--- a/src/content/docs/workers/platform/changelog/index.mdx
+++ b/src/content/docs/workers/platform/changelog/index.mdx
@@ -17,7 +17,7 @@ import { ProductReleaseNotes } from "~/components";
 
 This changelog details meaningful changes made to Workers across the Cloudflare dashboard, Wrangler, the API, and the workerd runtime. These changes are not configurable.
 
-This is *different* from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
+This is _different_ from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
 
 {/* <!-- Actual content lives in /src/content/release-notes/workers.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx
index 7e4e69499728faa..38a84a62e234adb 100644
--- a/src/content/docs/workers/platform/known-issues.mdx
+++ b/src/content/docs/workers/platform/known-issues.mdx
@@ -14,7 +14,7 @@ Below are some known bugs and issues to be aware of when using Cloudflare Worker
 
 ## Route specificity
 
-* When defining route specificity, a trailing `/*` in your pattern may not act as expected.
+- When defining route specificity, a trailing `/*` in your pattern may not act as expected.
 
 Consider two different Workers, each deployed to the same zone. Worker A is assigned the `example.com/images/*` route and Worker B is given the `example.com/images*` route pattern. With these in place, here are how the following URLs will be resolved:
 
@@ -44,11 +44,11 @@ When adding a wildcard on a subdomain, here are how the following URLs will be r
 
 ## wrangler dev
 
-* When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
+- When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
 
 ```js
 const request = new Request(url, incomingRequest);
-request.headers.delete('cf-workers-preview-token');
+request.headers.delete("cf-workers-preview-token");
 return await fetch(request);
 ```
 
@@ -90,11 +90,11 @@ For Workers subrequests, requests can only be made to URLs, not to IP addresses
 For example, in the zone `example.com` create a record of type `A` with the name `server` and value `192.0.2.1`, and then use:
 
 ```js
-await fetch('http://server.example.com')
+await fetch("http://server.example.com");
 ```
 
 Do not use:
 
 ```js
-await fetch('http://192.0.2.1')
+await fetch("http://192.0.2.1");
 ```
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
index d306aaec2558390..929570df6454101 100644
--- a/src/content/docs/workers/platform/pricing.mdx
+++ b/src/content/docs/workers/platform/pricing.mdx
@@ -27,9 +27,9 @@ All [Pages Functions](/pages/functions/) are billed as Workers. All pricing and
 
 Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, contact your Account Manager.
 
-|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                |
+|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                      |
 | **Standard** | 10 million included per month <br /> +$0.30 per additional million | No charge or limit for duration | 30 million CPU milliseconds included per month<br /> +$0.02 per additional million CPU milliseconds<br /><br/> Max of [5 minutes of CPU time](/workers/platform/limits/#account-plan-limits) per invocation (default: 30 seconds)<br /> Max of 15 minutes of CPU time per [Cron Trigger](/workers/configuration/cron-triggers/) or [Queue Consumer](/queues/configuration/javascript-apis/#consumer) invocation |
 
 <sup>1</sup> Inbound requests to your Worker. Cloudflare does not bill for
diff --git a/src/content/docs/workers/reference/how-the-cache-works.mdx b/src/content/docs/workers/reference/how-the-cache-works.mdx
index 53aad4dd28b3f81..fb3c5d8662710f6 100644
--- a/src/content/docs/workers/reference/how-the-cache-works.mdx
+++ b/src/content/docs/workers/reference/how-the-cache-works.mdx
@@ -17,11 +17,9 @@ Cloudflare Workers run before the cache but can also be utilized to modify asset
 Conceptually, there are two ways to interact with Cloudflare’s Cache using a Worker:
 
 - Call to [`fetch()`](/workers/runtime-apis/fetch/) in a Workers script. Requests proxied through Cloudflare are cached even without Workers according to a zone’s default or configured behavior (for example, static assets like files ending in `.jpg` are cached by default). Workers can further customize this behavior by:
-
   - Setting Cloudflare cache rules (that is, operating on the `cf` object of a [request](/workers/runtime-apis/request/)).
 
 - Store responses using the [Cache API](/workers/runtime-apis/cache/) from a Workers script. This allows caching responses that did not come from an origin and also provides finer control by:
-
   - Customizing cache behavior of any asset by setting headers such as `Cache-Control` on the response passed to `cache.put()`.
 
   - Caching responses generated by the Worker itself through `cache.put()`.
@@ -62,11 +60,9 @@ A("You have a Worker script that runs on <code>https://</code><code>example.com/
 Assets stored in the cache through [Cache API](/workers/runtime-apis/cache/) operations can be purged in a couple of ways:
 
 - Call `cache.delete` within a Worker to invalidate the cache for the asset with a matching request variable.
-
   - Assets purged in this way are only purged locally to the data center the Worker runtime was executed.
 
 - To purge an asset globally, use the standard [cache purge options](/cache/how-to/purge-cache/). Based on cache API implementation, not all cache purge endpoints function for purging assets stored by the Cache API.
-
   - All assets on a zone can be purged by using the [Purge Everything](/cache/how-to/purge-cache/purge-everything/) cache operation. This purge will remove all assets associated with a Cloudflare zone from cache in all data centers regardless of the method set.
 
   - [Cache Tags](/cache/how-to/purge-cache/purge-by-tags/#add-cache-tag-http-response-headers) can be added to requests dynamically in a Worker by calling `response.headers.append()` and appending `Cache-Tag` values dynamically to that request. Once set, those tags can be used to selectively purge assets from cache without invalidating all cached assets on a zone.
diff --git a/src/content/docs/workers/reference/how-workers-works.mdx b/src/content/docs/workers/reference/how-workers-works.mdx
index 4a44795d4bf2054..8d93ed5dfa09491 100644
--- a/src/content/docs/workers/reference/how-workers-works.mdx
+++ b/src/content/docs/workers/reference/how-workers-works.mdx
@@ -9,7 +9,7 @@ products:
   - workers
 ---
 
-import { Render, WorkersIsolateDiagram } from "~/components"
+import { Render, WorkersIsolateDiagram } from "~/components";
 
 Though Cloudflare Workers behave similarly to [JavaScript](https://www.cloudflare.com/learning/serverless/serverless-javascript/) in the browser or in Node.js, there are a few differences in how you have to think about your code. Under the hood, the Workers runtime uses the [V8 engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/) — the same engine used by Chromium and Node.js. The Workers runtime also implements many of the standard [APIs](/workers/runtime-apis/) available in most modern browsers.
 
@@ -27,13 +27,13 @@ The three largest differences are: Isolates, Compute per Request, and Distribute
 
 <Render file="isolate-description" product="workers" />
 
-<WorkersIsolateDiagram/>
+<WorkersIsolateDiagram />
 
 A given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons:
 
-* Resource limitations on the machine.
-* A suspicious script - anything seen as trying to break out of the isolate sandbox.
-* Individual [resource limits](/workers/platform/limits/).
+- Resource limitations on the machine.
+- A suspicious script - anything seen as trying to break out of the isolate sandbox.
+- Individual [resource limits](/workers/platform/limits/).
 
 Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingency.
 
@@ -52,6 +52,6 @@ Because there is no guarantee that any two user requests will be routed to the s
 
 ## Related resources
 
-* [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
-* [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
-* [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
+- [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
+- [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
+- [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
diff --git a/src/content/docs/workers/reference/protocols.mdx b/src/content/docs/workers/reference/protocols.mdx
index fe7f15baf21e464..bd089af6329ec22 100644
--- a/src/content/docs/workers/reference/protocols.mdx
+++ b/src/content/docs/workers/reference/protocols.mdx
@@ -10,10 +10,10 @@ products:
 
 Cloudflare Workers support the following protocols and interfaces:
 
-| Protocol               | Inbound                                                                                                                                                                                                                                                                                                          | Outbound                                                                                                     |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                               | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                                |
-| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
-| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                           |                                     |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
-| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |
+| Protocol               | Inbound                                                                                                                                                                                                                                                                                                         | Outbound                                                                                        |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                              | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                   |
+| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                            | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/) |
+| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                                                                                                            |                                                                                                 |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                 |
+| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                 | [Email Workers](/email-routing/email-workers/)                                                  |
diff --git a/src/content/docs/workers/reference/security-model.mdx b/src/content/docs/workers/reference/security-model.mdx
index f45407e36b6b093..d79f5a740d88d0d 100644
--- a/src/content/docs/workers/reference/security-model.mdx
+++ b/src/content/docs/workers/reference/security-model.mdx
@@ -7,7 +7,7 @@ products:
   - workers
 ---
 
-import { WorkersArchitectureDiagram } from "~/components"
+import { WorkersArchitectureDiagram } from "~/components";
 
 This article includes an overview of Cloudflare security architecture, and then addresses two frequently asked about issues: V8 bugs and Spectre.
 
@@ -25,7 +25,7 @@ For more details, refer to [this talk](https://www.infoq.com/presentations/cloud
 
 Beginning with a quick overview of the Workers runtime architecture:
 
-<WorkersArchitectureDiagram/>
+<WorkersArchitectureDiagram />
 
 There are two fundamental parts of designing a code sandbox: secure isolation and API design.
 
@@ -172,7 +172,7 @@ In Workers, you can get the current time using the JavaScript Date API by callin
 ```js
 let start = Date.now();
 for (let i = 0; i < 1e6; i++) {
-  doSpectreAttack();
+	doSpectreAttack();
 }
 let end = Date.now();
 ```
diff --git a/src/content/docs/workers/runtime-apis/bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/index.mdx
index a1b72465e91fb65..c395b7d9593aa09 100644
--- a/src/content/docs/workers/runtime-apis/bindings/index.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/index.mdx
@@ -121,38 +121,37 @@ Bindings are located on the `env` object, which can be accessed in several ways:
   [DurableObject](/durable-objects/), and [Workflow](/workflows/):
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-  ```js
-  export class MyDurableObject extends DurableObject {
-  	async sayHello() {
-  		return `Hi, ${this.env.NAME}!`;
-  	}
-  }
-  ```
-  </TabItem> <TabItem label="Python" icon="seti:python">
-  ```python
-  from workers import WorkerEntrypoint, Response
-
-  class Default(WorkerEntrypoint):
-  	async def fetch(self, request):
-  		return Response(f"Hi {self.env.NAME}")
-  ```
-  </TabItem></Tabs>
-
+    ```js
+    export class MyDurableObject extends DurableObject {
+    	async sayHello() {
+    		return `Hi, ${this.env.NAME}!`;
+    	}
+    }
+    ```
+    </TabItem> <TabItem label="Python" icon="seti:python">
+    ```python
+    from workers import WorkerEntrypoint, Response
+  
+    class Default(WorkerEntrypoint):
+    	async def fetch(self, request):
+    		return Response(f"Hi {self.env.NAME}")
+    ```
+    </TabItem></Tabs>
 
 * It can be imported from `cloudflare:workers`:
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-  ```js
-  import { env } from "cloudflare:workers";
-  console.log(`Hi, ${env.Name}`);
-  ```
-  </TabItem> <TabItem label="Python" icon="seti:python">
-  ```python
-  from workers import import_from_javascript
-  env = import_from_javascript("cloudflare:workers").env
-  print(f"Hi, {env.NAME}")
-  ```
-  </TabItem></Tabs>
+    ```js
+    import { env } from "cloudflare:workers";
+    console.log(`Hi, ${env.Name}`);
+    ```
+    </TabItem> <TabItem label="Python" icon="seti:python">
+    ```python
+    from workers import import_from_javascript
+    env = import_from_javascript("cloudflare:workers").env
+    print(f"Hi, {env.NAME}")
+    ```
+    </TabItem></Tabs>
 
 ### Importing `env` as a global
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
index 90cbad356d0ff57..6354459443f42ff 100644
--- a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
@@ -6,16 +6,16 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components"
+import { TabItem, Tabs, WranglerConfig } from "~/components";
 
 The Rate Limiting API lets you define rate limits and write code around them in your Worker.
 
 You can use it to enforce:
 
-* Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
-* Different rate limits for different types of customers or users (ex: free vs. paid)
-* Resource-specific or path-specific limits (ex: limit per API route)
-* Any combination of the above
+- Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
+- Different rate limits for different types of customers or users (ex: free vs. paid)
+- Resource-specific or path-specific limits (ex: limit per API route)
+- Any combination of the above
 
 The Rate Limiting API is backed by the same infrastructure that serves [rate limiting rules](/waf/rate-limiting-rules/).
 
@@ -96,15 +96,13 @@ export default {
 
 The `limit()` API accepts a single argument — a configuration object with the `key` field.
 
-* The key you provide can be any `string` value.
-* A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
+- The key you provide can be any `string` value.
+- A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
 
 You can define and configure multiple rate limiting configurations per Worker, which allows you to define different limits against incoming request and/or user parameters as needed to protect your application or upstream APIs.
 
 For example, here is how you can define two rate limiting configurations for free and paid tier users:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -139,12 +137,12 @@ For example, here is how you can define two rate limiting configurations for fre
 
 A rate limiting binding has the following settings:
 
-| Setting | Type | Description |
-| --- | --- | --- |
-| `namespace_id` | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
-| `simple` | `object` | The rate limit configuration. `simple` is the only supported type. |
-| `simple.limit` | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`. |
-| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`. |
+| Setting         | Type     | Description                                                                                                                                                                                                                                     |
+| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `namespace_id`  | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
+| `simple`        | `object` | The rate limit configuration. `simple` is the only supported type.                                                                                                                                                                              |
+| `simple.limit`  | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`.                                                                                                                                                               |
+| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`.                                                                                                                                                                 |
 
 :::note
 Two rate limiting bindings that share the same `namespace_id` — even across different Workers on the same account — share the same rate limit counters for a given key. This is intentional and allows you to enforce a single rate limit across multiple Workers.
@@ -178,19 +176,19 @@ For example, to apply a rate limit of 1500 requests per minute, you would define
 
 The `key` passed to the `limit` function, that determines what to rate limit on, should represent a unique characteristic of a user or class of user that you wish to rate limit.
 
-* Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
-* It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
+- Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
+- It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
 
 ```ts
 // Recommended: use a key that represents a specific user or class of user
-const url = new URL(req.url)
-const userId = url.searchParams.get("userId") || ""
-const { success } = await env.MY_RATE_LIMITER.limit({ key: userId })
+const url = new URL(req.url);
+const userId = url.searchParams.get("userId") || "";
+const { success } = await env.MY_RATE_LIMITER.limit({ key: userId });
 
 // Not recommended:  many users may share a single IP, especially on mobile networks
 // or when using privacy-enabling proxies
-const ipAddress = req.headers.get("cf-connecting-ip") || ""
-const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })
+const ipAddress = req.headers.get("cf-connecting-ip") || "";
+const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress });
 ```
 
 ## Locality
@@ -208,7 +206,7 @@ The underlying counters are cached on the same machine that your Worker runs in,
 This means that while in your code you `await` a call to the `limit()` method:
 
 ```javascript
-const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId })
+const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId });
 ```
 
 You are not waiting on a network request. You can use the Rate Limiting API without introducing any meaningful latency to your Worker.
@@ -223,11 +221,11 @@ For example, if many requests come in to your Worker in a single Cloudflare loca
 
 Rate limiting bindings are not currently visible in the Cloudflare dashboard. To monitor rate-limited requests from your Worker:
 
-* **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
-* **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
+- **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
+- **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
 
 ## Examples
 
-* [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
-* [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
-* [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
+- [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
+- [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
+- [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
index a30129269dd55d9..153b3d20f4de2f8 100644
--- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
@@ -30,16 +30,14 @@ For example, consider the following Worker that implements a [`fetch()` handler]
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    return new Response("Hello World!");
-  }
-}
+	async fetch(request, env, ctx) {
+		return new Response("Hello World!");
+	},
+};
 ```
 
 The following Worker declares a binding to the Worker above:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -74,12 +72,12 @@ If you construct a new request manually, rather than forwarding an existing one,
 
 ```js
 export default {
-  async fetch(request, env) {
-    // provide a valid URL
-    let newRequest = new Request("https://valid-url.com", { method: "GET" });
-    let response = await env.WORKER_B.fetch(newRequest);
-    return response;
-  }
+	async fetch(request, env) {
+		// provide a valid URL
+		let newRequest = new Request("https://valid-url.com", { method: "GET" });
+		let response = await env.WORKER_B.fetch(newRequest);
+		return response;
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/stream.mdx b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
index 8614dfafc2d517e..f07806aa6308be8 100644
--- a/src/content/docs/workers/runtime-apis/bindings/stream.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
@@ -4,5 +4,4 @@ title: Stream
 external_link: /stream/manage-video-library/bindings/
 head: []
 description: Upload, manage, and deliver video with Cloudflare Stream.
-
 ---
diff --git a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
index 53634f635526565..f6647c550ce60aa 100644
--- a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
@@ -15,7 +15,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components"
+import { TabItem, Tabs, WranglerConfig } from "~/components";
 
 The version metadata binding can be used to access metadata associated with a [version](/workers/configuration/versions-and-deployments/#versions) from inside the Workers runtime.
 
diff --git a/src/content/docs/workers/runtime-apis/cache.mdx b/src/content/docs/workers/runtime-apis/cache.mdx
index cc26647ff0a0df2..6347b07bd87cc61 100644
--- a/src/content/docs/workers/runtime-apis/cache.mdx
+++ b/src/content/docs/workers/runtime-apis/cache.mdx
@@ -30,7 +30,7 @@ This individualized zone cache object differs from Cloudflare’s Global CDN. Fo
 
 :::
 
-***
+---
 
 ## Accessing Cache
 
@@ -44,7 +44,7 @@ await cache.match(request);
 You may create and manage additional Cache instances via the [`caches.open`](https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage/open) method.
 
 ```js
-let myCache = await caches.open('custom:cache');
+let myCache = await caches.open("custom:cache");
 await myCache.match(request);
 ```
 
@@ -56,28 +56,28 @@ When using the cache API, avoid overriding the hostname in cache requests, as th
 // recommended approach: use your Worker hostname to ensure efficient caching
 request.url = "https://your-Worker-hostname.com/";
 
-let myCache = await caches.open('custom:cache');
+let myCache = await caches.open("custom:cache");
 let response = await myCache.match(request);
 ```
 
 :::
 
-***
+---
 
 ## Headers
 
 Our implementation of the Cache API respects the following HTTP headers on the response passed to `put()`:
 
-* `Cache-Control`
-  * Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
-* `Cache-Tag`
-  * Allows resource purging by tag(s) later.
-* `ETag`
-  * Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
-* `Expires` string
-  * A string that specifies when the resource becomes invalid.
-* `Last-Modified`
-  * Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
+- `Cache-Control`
+  - Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
+- `Cache-Tag`
+  - Allows resource purging by tag(s) later.
+- `ETag`
+  - Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
+- `Expires` string
+  - A string that specifies when the resource becomes invalid.
+- `Last-Modified`
+  - Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
 
 This differs from the web browser Cache API as they do not honor any headers on the request or response.
 
@@ -89,7 +89,7 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 
 :::
 
-***
+---
 
 ## Methods
 
@@ -99,9 +99,8 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 cache.put(request, response);
 ```
 
-* <code>put(request, response)</code> : Promise
-
-  * Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
+- <code>put(request, response)</code> : Promise
+  - Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
 
 :::note
 
@@ -111,20 +110,19 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 
 #### Parameters
 
-* `request` string | Request
+- `request` string | Request
+  - Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
 
-  * Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
-
-* `response` Response
-  * A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
+- `response` Response
+  - A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
 
 #### Invalid parameters
 
 `cache.put` will throw an error if:
 
-* The `request` passed is a method other than `GET`.
-* The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
-* The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
+- The `request` passed is a method other than `GET`.
+- The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
+- The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
 
 #### Errors
 
@@ -136,40 +134,34 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 cache.match(request, options);
 ```
 
-* <code>match(request, options)</code> : Promise`<Response | undefined>`
-
-  * Returns a promise wrapping the response object keyed to that request.
+- <code>match(request, options)</code> : Promise`<Response | undefined>`
+  - Returns a promise wrapping the response object keyed to that request.
 
 :::note
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
 :::
 
-
 #### Parameters
 
-* `request` string | Request
+- `request` string | Request
+  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
-  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
-
-* `options`
-  * Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
+- `options`
+  - Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
 
 Unlike the browser Cache API, Cloudflare Workers do not support the `ignoreSearch` or `ignoreVary` options on `match()`. You can accomplish this behavior by removing query strings or HTTP headers at `put()` time.
 
 Our implementation of the Cache API respects the following HTTP headers on the request passed to `match()`:
 
-* `Range`
-
-  * Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
-
-* `If-Modified-Since`
+- `Range`
+  - Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
 
-  * Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
+- `If-Modified-Since`
+  - Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
 
-* `If-None-Match`
-
-  * Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
+- `If-None-Match`
+  - Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
 
 :::note
 
@@ -188,12 +180,12 @@ If you use Cloudflare Logs, you may see these `504` responses with the `RequestS
 cache.delete(request, options);
 ```
 
-* <code>delete(request, options)</code> : Promise`<boolean>`
+- <code>delete(request, options)</code> : Promise`<boolean>`
 
 Deletes the `Response` object from the cache and returns a `Promise` for a Boolean response:
 
-* `true`: The response was cached but is now deleted
-* `false`: The response was not in the cache at the time of deletion.
+- `true`: The response was cached but is now deleted
+- `false`: The response was not in the cache at the time of deletion.
 
 :::caution[Global purges]
 
@@ -203,18 +195,17 @@ The `cache.delete` method only purges content of the cache in the data center th
 
 #### Parameters
 
-* `request` string | Request
-
-  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+- `request` string | Request
+  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
-* `options` object
-  * Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+- `options` object
+  - Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
 
-***
+---
 
 ## Related resources
 
-* [How the cache works](/workers/reference/how-the-cache-works/)
-* [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
-* [Example: using the Cache API](/workers/examples/cache-api/)
-* [Example: caching POST requests](/workers/examples/cache-post-request/)
+- [How the cache works](/workers/reference/how-the-cache-works/)
+- [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
+- [Example: using the Cache API](/workers/examples/cache-api/)
+- [Example: caching POST requests](/workers/examples/cache-post-request/)
diff --git a/src/content/docs/workers/runtime-apis/console.mdx b/src/content/docs/workers/runtime-apis/console.mdx
index 6ed3997531c52a7..f1861458031b416 100644
--- a/src/content/docs/workers/runtime-apis/console.mdx
+++ b/src/content/docs/workers/runtime-apis/console.mdx
@@ -18,39 +18,39 @@ The table below enumerates each method, and the extent to which it is supported
 
 All methods noted as "✅ supported" have the following behavior:
 
-* They will be written to the console in local dev (`npx wrangler@latest dev`)
-* They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
-* They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
+- They will be written to the console in local dev (`npx wrangler@latest dev`)
+- They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
+- They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
 
 All methods noted as "🟡 partial support" have the following behavior:
 
-* In both production and local development the method can be safely called, but will do nothing (no op)
-* In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
+- In both production and local development the method can be safely called, but will do nothing (no op)
+- In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
 
 Refer to [Log from Workers](https://developers.cloudflare.com/workers/observability/log-from-workers/) for more on debugging and adding logs to Workers.
 
 | Method                                                                                                         | Behavior                                                                                           |
 | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                        |
-| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                        |
-| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                        |
-| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                        |
-| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                        |
+| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                       |
+| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                       |
+| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                       |
+| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                       |
+| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                       |
 | [`console.clear()`](https://developer.mozilla.org/en-US/docs/Web/API/console/clear_static)                     | 🟡 partial support                                                                                 |
 | [`console.count()`](https://developer.mozilla.org/en-US/docs/Web/API/console/count_static)                     | 🟡 partial support                                                                                 |
 | [`console.group()`](https://developer.mozilla.org/en-US/docs/Web/API/console/group_static)                     | 🟡 partial support                                                                                 |
 | [`console.table()`](https://developer.mozilla.org/en-US/docs/Web/API/console/table_static)                     | 🟡 partial support                                                                                 |
 | [`console.trace()`](https://developer.mozilla.org/en-US/docs/Web/API/console/trace_static)                     | 🟡 partial support                                                                                 |
-| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                            |
-| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                            |
-| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                            |
-| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                            |
-| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                            |
-| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                            |
-| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                            |
-| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                            |
-| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                            |
-| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                            |
-| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                            |
-| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                            |
+| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                           |
+| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                           |
+| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                           |
+| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                           |
+| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                           |
+| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                           |
+| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                           |
+| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                           |
+| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                           |
+| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                           |
+| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                           |
+| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                           |
 | [`console.createTask()`](https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces) | 🔴 Will throw an exception in production, but works in local dev, Quick Editor, and remote preview |
diff --git a/src/content/docs/workers/runtime-apis/encoding.mdx b/src/content/docs/workers/runtime-apis/encoding.mdx
index 7f2f363e0232ea5..1c2d6dd741d8730 100644
--- a/src/content/docs/workers/runtime-apis/encoding.mdx
+++ b/src/content/docs/workers/runtime-apis/encoding.mdx
@@ -24,24 +24,15 @@ let encoder = new TextEncoder();
 
 ### Properties
 
-
-
-* `encoder.encoding` DOMString read-only
-  * The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
-
-
+- `encoder.encoding` DOMString read-only
+  - The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
 
 ### Methods
 
+- <code>encode(inputUSVString)</code> : Uint8Array
+  - Encodes a string input.
 
-
-* <code>encode(inputUSVString)</code> : Uint8Array
-
-  * Encodes a string input.
-
-
-
-***
+---
 
 ## TextDecoder
 
@@ -59,25 +50,16 @@ let decoder = new TextDecoder();
 
 ### Properties
 
+- `decoder.encoding` DOMString read-only
+  - The name of the decoder that describes the method the `TextDecoder` uses.
 
+- `decoder.fatal` boolean read-only
+  - Indicates if the error mode is fatal.
 
-* `decoder.encoding` DOMString read-only
-
-  * The name of the decoder that describes the method the `TextDecoder` uses.
-
-* `decoder.fatal` boolean read-only
-
-  * Indicates if the error mode is fatal.
-
-* `decoder.ignoreBOM` boolean read-only
-  * Indicates if the byte-order marker is ignored.
-
-
+- `decoder.ignoreBOM` boolean read-only
+  - Indicates if the byte-order marker is ignored.
 
 ### Methods
 
-
-
-* `decode()` : DOMString
-  * Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
-
+- `decode()` : DOMString
+  - Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
diff --git a/src/content/docs/workers/runtime-apis/eventsource.mdx b/src/content/docs/workers/runtime-apis/eventsource.mdx
index 789989011083673..e8678e44d07dd79 100644
--- a/src/content/docs/workers/runtime-apis/eventsource.mdx
+++ b/src/content/docs/workers/runtime-apis/eventsource.mdx
@@ -19,12 +19,8 @@ The [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource
 let eventSource = new EventSource(url, options);
 ```
 
-
-
-* `url` USVString - The URL to which to connect.
-* `options` EventSourceInit - An optional dictionary containing any optional settings.
-
-
+- `url` USVString - The URL to which to connect.
+- `options` EventSourceInit - An optional dictionary containing any optional settings.
 
 By default, the `EventSource` will use the global `fetch()` function under the
 covers to make requests. If you need to use a different fetch implementation as
@@ -32,10 +28,10 @@ provided by a Cloudflare Workers binding, you can pass the `fetcher` option:
 
 ```js
 export default {
-  async fetch(req, env) {
-    let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
-    // ...
-  }
+	async fetch(req, env) {
+		let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
+		// ...
+	},
 };
 ```
 
@@ -43,49 +39,34 @@ Note that the `fetcher` option is a Cloudflare Workers specific extension.
 
 ### Properties
 
-
-
-* `eventSource.url` USVString read-only
-  * The URL of the event source.
-* `eventSource.readyState` USVString read-only
-  * The state of the connection.
-* `eventSource.withCredentials` Boolean read-only
-  * A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
-
-
+- `eventSource.url` USVString read-only
+  - The URL of the event source.
+- `eventSource.readyState` USVString read-only
+  - The state of the connection.
+- `eventSource.withCredentials` Boolean read-only
+  - A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
 
 ### Methods
 
-
-
-* `eventSource.close()`
-  * Closes the connection.
-* `eventSource.onopen`
-  * An event handler called when a connection is opened.
-* `eventSource.onmessage`
-  * An event handler called when a message is received.
-* `eventSource.onerror`
-  * An event handler called when an error occurs.
-
-
+- `eventSource.close()`
+  - Closes the connection.
+- `eventSource.onopen`
+  - An event handler called when a connection is opened.
+- `eventSource.onmessage`
+  - An event handler called when a message is received.
+- `eventSource.onerror`
+  - An event handler called when an error occurs.
 
 ### Events
 
-
-
-* `message`
-  * Fired when a message is received.
-* `open`
-  * Fired when the connection is opened.
-* `error`
-  * Fired when an error occurs.
-
-
+- `message`
+  - Fired when a message is received.
+- `open`
+  - Fired when the connection is opened.
+- `error`
+  - Fired when an error occurs.
 
 ### Class Methods
 
-
-
-* <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
-  * This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
-
+- <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
+  - This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
diff --git a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
index afee782db35b496..17256889d32d9bb 100644
--- a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
@@ -13,36 +13,27 @@ Incoming HTTP requests to a Worker are passed to the `fetch()` handler as a [`Re
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response('Hello World!');
+		return new Response("Hello World!");
 	},
 };
 ```
 
 :::note
 
-
 The Workers runtime does not support `XMLHttpRequest` (XHR). Learn the difference between `XMLHttpRequest` and `fetch()` in the [MDN](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) documentation.
 
-
 :::
 
 ### Parameters
 
+- `request` Request
+  - The incoming HTTP request.
 
+- `env` object
+  - The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
 
-* `request` Request
-
-  * The incoming HTTP request.
-
-* `env` object
-
-  * The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
-
-* <code>ctx.waitUntil(promisePromise)</code> : void
-
-  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
-
-* <code>ctx.passThroughOnException()</code> : void
-
-  * Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
+- <code>ctx.waitUntil(promisePromise)</code> : void
+  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
 
+- <code>ctx.passThroughOnException()</code> : void
+  - Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
diff --git a/src/content/docs/workers/runtime-apis/handlers/index.mdx b/src/content/docs/workers/runtime-apis/handlers/index.mdx
index f62e15838d7d289..0ce1d48c75d798b 100644
--- a/src/content/docs/workers/runtime-apis/handlers/index.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/index.mdx
@@ -9,14 +9,14 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Handlers are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker. For example, the `fetch()` handler receives an HTTP request, and can return a response:
 
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response('Hello World!');
+		return new Response("Hello World!");
 	},
 };
 ```
diff --git a/src/content/docs/workers/runtime-apis/handlers/tail.mdx b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
index 7c6fbbaa19a19ad..b95fc4c33d0ffea 100644
--- a/src/content/docs/workers/runtime-apis/handlers/tail.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
@@ -18,170 +18,124 @@ To configure a Tail Worker, refer to [Tail Workers documentation](/workers/obser
 
 ```js
 export default {
-  async tail(events, env, ctx) {
-    fetch("<YOUR_ENDPOINT>", {
-      method: "POST",
-      body: JSON.stringify(events),
-    })
-  }
-}
+	async tail(events, env, ctx) {
+		fetch("<YOUR_ENDPOINT>", {
+			method: "POST",
+			body: JSON.stringify(events),
+		});
+	},
+};
 ```
 
 ### Parameters
 
+- `events` array
+  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
 
+- `env` object
+  - An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
 
-* `events` array
-
-  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
-
-* `env` object
-
-  * An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
-
-* `ctx` object
-  * An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
-
-
+- `ctx` object
+  - An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
 
 ### Properties
 
+- `event.type` string
+  - The type of event. This will always return `"tail"`.
 
+- `event.traces` array
+  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
 
-* `event.type` string
-
-  * The type of event. This will always return `"tail"`.
-
-* `event.traces` array
-
-  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
-
-* <code>event.waitUntil(promisePromise)</code> : void
-
-  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
-
-
+- <code>event.waitUntil(promisePromise)</code> : void
+  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
 
 ### `TailItems`
 
 #### Properties
 
-
-
-* `scriptName` string
-
-  * The name of the producer script.
-
-* `event` object
-
-  * Contains information about the Worker’s triggering event.
-    * For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
-    * For other event types: `null`, currently.
-
-* `eventTimestamp` number
-
-  * Measured in epoch time.
-
-* `logs` array
-
-  * An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
-
-* `exceptions` array
-
-  * An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
-
-* `outcome` string
-
-  * The outcome of the Worker invocation, one of:
-    * `unknown`: outcome status was not set.
-    * `ok`: The worker invocation succeeded.
-    * `exception`: An unhandled exception was thrown.  This can happen for many reasons, including:
-      * An uncaught JavaScript exception.
-      * A fetch handler that does not result in a Response.
-      * An internal error.
-    * `exceededCpu`: The Worker invocation exceeded either its CPU limits.
-    * `exceededMemory`: The Worker invocation exceeded memory limits.
-    * `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
-    * `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
-    * `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
-
-
+- `scriptName` string
+  - The name of the producer script.
+
+- `event` object
+  - Contains information about the Worker’s triggering event.
+    - For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
+    - For other event types: `null`, currently.
+
+- `eventTimestamp` number
+  - Measured in epoch time.
+
+- `logs` array
+  - An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
+
+- `exceptions` array
+  - An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
+
+- `outcome` string
+  - The outcome of the Worker invocation, one of:
+    - `unknown`: outcome status was not set.
+    - `ok`: The worker invocation succeeded.
+    - `exception`: An unhandled exception was thrown. This can happen for many reasons, including:
+      - An uncaught JavaScript exception.
+      - A fetch handler that does not result in a Response.
+      - An internal error.
+    - `exceededCpu`: The Worker invocation exceeded either its CPU limits.
+    - `exceededMemory`: The Worker invocation exceeded memory limits.
+    - `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
+    - `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
+    - `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
 
 :::note[Outcome is not the same as HTTP status.]
 
 Outcome is equivalent to the exit status of a script and an indicator of whether it has fully run to completion. A Worker outcome may differ from a response code if, for example:
 
-* a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
-* a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
+- a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
+- a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
   :::
 
 ### `FetchEventInfo`
 
 #### Properties
 
+- `request` object
+  - A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
 
-
-* `request` object
-
-  * A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
-
-* `response` object
-
-  * A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
-
+- `response` object
+  - A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
 
 ### `TailRequest`
 
 #### Properties
 
+- `cf` object
+  - Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
 
+- `headers` object
+  - Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
 
-* `cf` object
-
-  * Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
-
-* `headers` object
-
-  * Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
-
-* `method` string
-
-  * The HTTP request method.
-
-* `url` string
-
-  * The HTTP request URL (redacted by default).
-
+- `method` string
+  - The HTTP request method.
 
+- `url` string
+  - The HTTP request URL (redacted by default).
 
 #### Methods
 
-
-
-* `getUnredacted()` object
-
-  * Returns a TailRequest object with unredacted properties
-
-
+- `getUnredacted()` object
+  - Returns a TailRequest object with unredacted properties
 
 Some of the properties of `TailRequest` are redacted by default to make it harder to accidentally record sensitive information, like user credentials or API tokens. The redactions use heuristic rules, so they are subject to false positives and negatives. Clients can call `getUnredacted()` to bypass redaction, but they should always be careful about what information is retained, whether using the redaction or not.
 
-* Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
-* URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
-* Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
-* Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
+- Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
+- URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
+- Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
+- Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
 
 ### `TailResponse`
 
 #### Properties
 
-
-
-* `status` number
-
-  * The HTTP status code.
-
-
+- `status` number
+  - The HTTP status code.
 
 ### `TailLog`
 
@@ -189,20 +143,14 @@ Records information sent to console functions.
 
 #### Properties
 
+- `timestamp` number
+  - Measured in epoch time.
 
+- `level` string
+  - A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
 
-* `timestamp` number
-
-  * Measured in epoch time.
-
-* `level` string
-
-  * A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
-
-* `message` object
-
-  * The array of parameters passed to the console function.
-
+- `message` object
+  - The array of parameters passed to the console function.
 
 ### `TailException`
 
@@ -210,22 +158,15 @@ Records an unhandled exception that occurred during the Worker invocation.
 
 #### Properties
 
+- `timestamp` number
+  - Measured in epoch time.
 
+- `name` string
+  - The error type (For example,`Error`, `TypeError`, etc.).
 
-* `timestamp` number
-
-  * Measured in epoch time.
-
-* `name` string
-
-  * The error type (For example,`Error`, `TypeError`, etc.).
-
-* `message` object
-
-  * The error description (For example, `"x" is not a function`).
-
-
+- `message` object
+  - The error description (For example, `"x" is not a function`).
 
 ## Related resources
 
-* [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
+- [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
diff --git a/src/content/docs/workers/runtime-apis/headers.mdx b/src/content/docs/workers/runtime-apis/headers.mdx
index 5fd387aafea782c..f7a50f6ec116fc8 100644
--- a/src/content/docs/workers/runtime-apis/headers.mdx
+++ b/src/content/docs/workers/runtime-apis/headers.mdx
@@ -17,16 +17,16 @@ When a header name possesses multiple values, those values will be concatenated
 ```js
 let headers = new Headers();
 
-headers.get('x-foo'); //=> null
+headers.get("x-foo"); //=> null
 
-headers.set('x-foo', '123');
-headers.get('x-foo'); //=> "123"
+headers.set("x-foo", "123");
+headers.get("x-foo"); //=> "123"
 
-headers.set('x-foo', 'hello');
-headers.get('x-foo'); //=> "hello"
+headers.set("x-foo", "hello");
+headers.get("x-foo"); //=> "hello"
 
-headers.append('x-foo', 'world');
-headers.get('x-foo'); //=> "hello, world"
+headers.append("x-foo", "world");
+headers.get("x-foo"); //=> "hello, world"
 ```
 
 ## Differences
@@ -61,7 +61,6 @@ console.log(headers.getAll("Set-Cookie"));
 
 In Cloudflare Workers, the `Headers.get` method returns a [`USVString`](https://mdn2.netlify.app/en-us/docs/web/api/usvstring/) instead of a [`ByteString`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String), which is specified by the web standard. For most scenarios, this should have no noticeable effect. To compare the differences between these two string classes, refer to this [Playground example](https://workers.cloudflare.com/playground#LYVwNgLglgDghgJwgegGYHsHALQBM4RwDcABAEbogB2+CAngLzbMutvvsCMALAJx-cAzAHZeANkG8AHAAZOU7t2EBWAEy9eqsXNWdOALg5HjbHv34jxk2fMUr1m7Z12cAsACgAwuioQApr7YACJQAM4w6KFQ0D76JBhYeATEJFRwwH4MAERQNH4AHgB0AFahWaSoUGAB6Zk5eUWlWR7evgEQ2AAqdDB+cXAwMGBQAMYEUD7IxXAAbnChIwiwEADUwOi44H4eHgURSCS4fqhw4BAkAN7uAJDzdFQj8X4QIwAWABQIfgCOIH6hEAAlJcbtdqucxucGCQsoBeDcAXHtZUHgkggCCoKSeAgkaFUPwAdxInQKEAAog8Nn4EO9AYUAiNKe9IYDkc8SPTKbgsVCSABlCBLKgAc0KqAQ6GAnleiG8R3ehQVaIx3JZoIZVFC6GqhTA6CF7yynVeYRIJrgJAAqryAGr8wVCkj46KvEjmyH6LIAGhIzLVPk12t1+sNxtCprD5oAQnR-Hbcg6nRAXW7sT5LZ0AGLYKQe70co5cgiq67XZDIEgACT8cCOCAjXxIoRAg0iflwJAg6EdmAA1iQfGA6I7nSRo7GBfHQt6yGj+yAEKCy6bgEM-BlfOM0yBQv9LTa48LQoUiaHUiSSMM8cOwGASDBBec4Ivy-jEFR466KLOk2FCqzzq81a1mGuIEpWQFUqE7wXDC+ZttgkJZHEcGFucAC+xbXF8EDzlQZ6EgASv8EQan4BpSn4Ix9pQ5xJn4JAAAatAGfgMa6NAdoBJBEeE-r0YBNaQR2XY7vRdFzhAMCzgyK6IGE-qFF6lwkAJwEkBhNxoe4aEeCYelGGYAiWBI0hyAoShqBoWg6HoLQ+P4gQhLxUQxFQcQJDg+CEKQaQZNkGSEF5cDlPEVQ1H5WRkLqZDNF49ntF0PR9K6gzDJCExUFMmpUDs7gXFkwBwLkAD66ybNUSH1EcjRlDp7j6Q1rCGRYogmTY5n2FZTguMwHhAA).
 
-
 ## Cloudflare headers
 
 Cloudflare sets a number of its own custom headers on incoming requests and outgoing responses. While some may be used for its own tracking and bookkeeping, many of these can be useful to your own applications – or Workers – too.
@@ -70,5 +69,5 @@ For a list of documented Cloudflare request headers, refer to [Cloudflare HTTP h
 
 ## Related resources
 
-* [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
-* [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
\ No newline at end of file
+- [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
+- [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
diff --git a/src/content/docs/workers/runtime-apis/messagechannel.mdx b/src/content/docs/workers/runtime-apis/messagechannel.mdx
index 34a69e18a8ca1ac..dc8e4475fe3ec30 100644
--- a/src/content/docs/workers/runtime-apis/messagechannel.mdx
+++ b/src/content/docs/workers/runtime-apis/messagechannel.mdx
@@ -19,10 +19,10 @@ currently limited to uses with a single Worker instance. This means that you can
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log('Received message:', event.data);
+	console.log("Received message:", event.data);
 };
 
-port2.postMessage('Hello from port2!');
+port2.postMessage("Hello from port2!");
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -31,13 +31,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-* Transfer lists are currently not supported. This means that you will not be able to transfer
+- Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-	are errors serializing or deserializing the message data. Instead, the error will be thrown when
-	the `postMessage` method is called on the sending port.
-* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+  are errors serializing or deserializing the message data. Instead, the error will be thrown when
+  the `postMessage` method is called on the sending port.
+- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/docs/workers/runtime-apis/nodejs/util.mdx b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
index 2e7372f4d555bc0..7a797483bdc8683 100644
--- a/src/content/docs/workers/runtime-apis/nodejs/util.mdx
+++ b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
@@ -35,16 +35,16 @@ await promisifiedFoo(args);
 Similarly to `promisify`, `callbackify` converts a Promise-returning async function into a Node.js-style callback function:
 
 ```js
-import { callbackify } from 'node:util';
+import { callbackify } from "node:util";
 
 async function foo(args) {
-  throw new Error('boom');
+	throw new Error("boom");
 }
 
 const callbackifiedFoo = callbackify(foo);
 
 callbackifiedFoo(args, (err, value) => {
-  if (err) throw err;
+	if (err) throw err;
 });
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/performance.mdx b/src/content/docs/workers/runtime-apis/performance.mdx
index 0465b6db640c78a..f8c14e1b3cc76b2 100644
--- a/src/content/docs/workers/runtime-apis/performance.mdx
+++ b/src/content/docs/workers/runtime-apis/performance.mdx
@@ -21,7 +21,7 @@ When Workers are deployed to Cloudflare, as a security measure to [mitigate agai
 ```typescript title="Time is frozen — start will have the exact same value as end."
 const start = performance.now();
 for (let i = 0; i < 1e6; i++) {
-  // do expensive work
+	// do expensive work
 }
 const end = performance.now();
 const timing = end - start; // 0
diff --git a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
index a0677b887aebf4c..acf48ac5f2c6e48 100644
--- a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
@@ -18,9 +18,9 @@ An exception thrown by an RPC method implementation will propagate to the caller
 
 ### Unsupported error types
 
-* If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
-* The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
-* Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
+- If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
+- The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
+- Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
 
 ## Additional properties
 
diff --git a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
index 2a80b67db3d88e2..5bb6019d5d24910 100644
--- a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
@@ -16,7 +16,7 @@ Some method names are reserved or have special semantics.
 
 ## Special Methods
 
-For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does *not* apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
+For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does _not_ apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
 
 ### `fetch()`
 
@@ -36,12 +36,12 @@ The `connect()` method of the `WorkerEntrypoint` class is reserved for opening a
 
 The following method (or property) names may not be used as RPC methods on any RPC type (including `WorkerEntrypoint`, `DurableObject`, and `RpcTarget`):
 
-* `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
-* `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
+- `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
+- `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
 
 The following methods are disallowed only on `WorkerEntrypoint` and `DurableObject`, but allowed on `RpcTarget`. These methods have historically had special meaning to Durable Objects, where they are used to handle certain system-generated events.
 
-* `alarm`
-* `webSocketMessage`
-* `webSocketClose`
-* `webSocketError`
+- `alarm`
+- `webSocketMessage`
+- `webSocketClose`
+- `webSocketError`
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
index 72512cc6f9f0f85..8ec8b621e64213b 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
@@ -13,47 +13,33 @@ A `ReadableStream` is returned by the `readable` property inside [`TransformStre
 
 ## Properties
 
-
-
-* `locked` boolean
-  * A Boolean value that indicates if the readable stream is locked to a reader.
-
-
+- `locked` boolean
+  - A Boolean value that indicates if the readable stream is locked to a reader.
 
 ## Methods
 
+- <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
+  - Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
 
-
-* <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
-
-  * Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
-
-* <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
-
-  * Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
+- <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
+  - Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
 
 ```js
-let reader = readable.getReader({ mode: 'byob' });
+let reader = readable.getReader({ mode: "byob" });
 ```
 
-
-
 ### `PipeToOptions`
 
+- `preventClose` bool
+  - When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
 
+- `preventAbort` bool
+  - When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
 
-* `preventClose` bool
-
-  * When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
-
-* `preventAbort` bool
-
-  * When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
-* [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
+- [Streams](/workers/runtime-apis/streams/)
+- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+- [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
index cff8e9257521f97..c8a67b7ecf18fec 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
@@ -24,50 +24,41 @@ A `ReadableStreamBYOBReader` is not instantiated via its constructor. Rather, it
 
 ```js
 const { readable, writable } = new TransformStream();
-const reader = readable.getReader({ mode: 'byob' });
+const reader = readable.getReader({ mode: "byob" });
 ```
 
-***
+---
 
 ## Methods
 
+- <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+  - Returns a promise with the next available chunk of data read into a passed-in buffer.
 
+- <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+  - Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read. The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
+    - If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
+    - If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
+    - If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
+    - If the stream errors, the promise rejects.
+    - `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
 
-* <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-
-  * Returns a promise with the next available chunk of data read into a passed-in buffer.
-
-* <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-
-  * Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read.  The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
-
-    * If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
-    * If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
-    * If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
-    * If the stream errors, the promise rejects.
-    * `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
-
-
-
-***
+---
 
 ## Common issues
 
 :::caution[Warning]
 
-
 `read` provides no control over the minimum number of bytes that should be read into the buffer. Even if you allocate a 1 MiB buffer, the kernel is perfectly within its rights to fulfill this read with a single byte, whether or not an EOF immediately follows.
 
 In practice, the Workers team has found that `read` typically fills only 1% of the provided buffer.
 
 `readAtLeast` is a non-standard extension to the Streams API which allows users to specify that at least `minElements` elements must be read into the buffer before resolving the read. For a `Uint8Array` (the most common case), each element is one byte, so `minElements` is effectively a byte count. If the stream ends before `minElements` elements are available, the partial data that was read is still returned rather than throwing an error — refer to the [`readAtLeast` method documentation above](#methods) for the full details.
 
-
 :::
 
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
+- [Streams](/workers/runtime-apis/streams/)
+- [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
index 72a05a4edd97f20..41d4eaf45b54a02 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
@@ -23,44 +23,32 @@ const { readable, writable } = new TransformStream();
 const reader = readable.getReader();
 ```
 
-***
+---
 
 ## Properties
 
-
-
-* `reader.closed` : Promise
-
-  * A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
-
-
+- `reader.closed` : Promise
+  - A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
 
 ## Methods
 
+- `read()` : Promise
+  - A promise that returns the next available chunk of data being passed through the reader queue.
 
-
-* `read()` : Promise
-
-  * A promise that returns the next available chunk of data being passed through the reader queue.
-
-* <code>cancel(reasonstringoptional)</code> : void
-
-  * Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
+- <code>cancel(reasonstringoptional)</code> : void
+  - Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet read is lost.
   :::
 
-* `releaseLock()` : void
-
-  * Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+- `releaseLock()` : void
+  - Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
index 029a878e9e847be..46c9e41542ea8b0 100644
--- a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
@@ -13,7 +13,7 @@ A transform stream consists of a pair of streams: a writable stream, known as it
 
 Workers currently only implements an identity transform stream, a type of transform stream which forwards all chunks written to its writable side to its readable side, without any changes.
 
-***
+---
 
 ## Constructor
 
@@ -21,26 +21,17 @@ Workers currently only implements an identity transform stream, a type of transf
 let { readable, writable } = new TransformStream();
 ```
 
-
-
-* `TransformStream()` TransformStream
-
-  * Returns a new identity transform stream.
-
-
+- `TransformStream()` TransformStream
+  - Returns a new identity transform stream.
 
 ## Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## `IdentityTransformStream`
 
@@ -54,26 +45,17 @@ The `IdentityTransformStream` readable side supports [bring your own buffer (BYO
 let { readable, writable } = new IdentityTransformStream();
 ```
 
-
-
-* `IdentityTransformStream()` IdentityTransformStream
-
-  * Returns a new identity transform stream.
-
-
+- `IdentityTransformStream()` IdentityTransformStream
+  - Returns a new identity transform stream.
 
 ### Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## `FixedLengthStream`
 
@@ -85,29 +67,20 @@ The `FixedLengthStream` is a specialization of `IdentityTransformStream` that li
 let { readable, writable } = new FixedLengthStream(1000);
 ```
 
-
-
-* `FixedLengthStream(length)` FixedLengthStream
-
-  * Returns a new identity transform stream.
-  * `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
-
-
+- `FixedLengthStream(length)` FixedLengthStream
+  - Returns a new identity transform stream.
+  - `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
 
 ### Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
+- [Streams](/workers/runtime-apis/streams/)
+- [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
index 799ddf11156ada5..1040f59de92975c 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
@@ -15,9 +15,9 @@ A typical way to write to a `WritableStream` is to pipe a [`ReadableStream`](/wo
 
 ```js
 readableStream
-  .pipeTo(writableStream)
-  .then(() => console.log('All data successfully written!'))
-  .catch(e => console.error('Something went wrong!', e));
+	.pipeTo(writableStream)
+	.then(() => console.log("All data successfully written!"))
+	.catch((e) => console.error("Something went wrong!", e));
 ```
 
 To write to a `WritableStream` directly, you must use its writer.
@@ -31,36 +31,25 @@ Refer to the [WritableStreamDefaultWriter](/workers/runtime-apis/streams/writabl
 
 ## Properties
 
-
-
-* `locked` boolean
-
-  * A Boolean value to indicate if the writable stream is locked to a writer.
-
-
+- `locked` boolean
+  - A Boolean value to indicate if the writable stream is locked to a writer.
 
 ## Methods
 
-
-
-* <code>abort(reasonstringoptional)</code> : Promise\<void>
-
-  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+- <code>abort(reasonstringoptional)</code> : Promise\<void>
+  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-* `getWriter()` : WritableStreamDefaultWriter
-
-  * Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+- `getWriter()` : WritableStreamDefaultWriter
+  - Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
index 9778261db7f5088..fda65a4afb87bbd 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
@@ -18,71 +18,57 @@ A writer is used when you want to write directly to a [`WritableStream`](/worker
 
 ```js
 function writeArrayToStream(array, writableStream) {
-  const writer = writableStream.getWriter();
-  array.forEach(chunk => writer.write(chunk).catch(() => {}));
+	const writer = writableStream.getWriter();
+	array.forEach((chunk) => writer.write(chunk).catch(() => {}));
 
-  return writer.close();
+	return writer.close();
 }
 
 writeArrayToStream([1, 2, 3, 4, 5], writableStream)
-  .then(() => console.log('All done!'))
-  .catch(e => console.error('Error with the stream: ' + e));
+	.then(() => console.log("All done!"))
+	.catch((e) => console.error("Error with the stream: " + e));
 ```
 
 ## Properties
 
+- `writer.desiredSize` int
+  - The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
 
-
-* `writer.desiredSize` int
-
-  * The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
-
-* `writer.closed` Promise\<void>
-
-  * A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
-
-
+- `writer.closed` Promise\<void>
+  - A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
 
 ## Methods
 
-
-
-* <code>abort(reasonstringoptional)</code> : Promise\<void>
-
-  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+- <code>abort(reasonstringoptional)</code> : Promise\<void>
+  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-* `close()` : Promise\<void>
-
-  * Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
+- `close()` : Promise\<void>
+  - Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
 
-* `releaseLock()` : void
-
-  * Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
+- `releaseLock()` : void
+  - Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
 
 ```js
 let writer = writable.getWriter();
 // Write a preamble.
-writer.write(new TextEncoder().encode('foo bar'));
+writer.write(new TextEncoder().encode("foo bar"));
 // While that’s still writing, pipe the rest of the body from somewhere else.
 writer.releaseLock();
 await someResponse.body.pipeTo(writable);
 ```
 
-* <code>write(chunkany)</code> : Promise\<void>
-
-  * Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
-  * The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+- <code>write(chunkany)</code> : Promise\<void>
+  - Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
+  - The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
index be6e3593489cb39..ef899b752b54415 100644
--- a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
+++ b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
@@ -29,143 +29,132 @@ The `connect()` function returns a TCP socket, with both a [readable](/workers/r
 `connect()` is provided as a [Runtime API](/workers/runtime-apis/), and is accessed by importing the `connect` function from `cloudflare:sockets`. This process is similar to how one imports built-in modules in Node.js. Refer to the following codeblock for an example of creating a TCP socket, writing to it, and returning the readable side of the socket as a response:
 
 ```typescript
-import { connect } from 'cloudflare:sockets';
+import { connect } from "cloudflare:sockets";
 
 export default {
-  async fetch(req): Promise<Response> {
-    const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
-    const url = new URL(req.url);
-
-    try {
-      const socket = connect(gopherAddr);
-
-      const writer = socket.writable.getWriter()
-      const encoder = new TextEncoder();
-      const encoded = encoder.encode(url.pathname + "\r\n");
-      await writer.write(encoded);
-      await writer.close();
-
-      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
-    } catch (error) {
-      return new Response("Socket connection failed: " + error, { status: 500 });
-    }
-  }
+	async fetch(req): Promise<Response> {
+		const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
+		const url = new URL(req.url);
+
+		try {
+			const socket = connect(gopherAddr);
+
+			const writer = socket.writable.getWriter();
+			const encoder = new TextEncoder();
+			const encoded = encoder.encode(url.pathname + "\r\n");
+			await writer.write(encoded);
+			await writer.close();
+
+			return new Response(socket.readable, {
+				headers: { "Content-Type": "text/plain" },
+			});
+		} catch (error) {
+			return new Response("Socket connection failed: " + error, {
+				status: 500,
+			});
+		}
+	},
 } satisfies ExportedHandler;
 ```
 
-
-
-* <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
-  * `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
-
+- <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
+  - `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
 
 ### `SocketAddress`
 
+- `hostname` string
+  - The hostname to connect to. Example: `cloudflare.com`.
 
-
-* `hostname` string
-  * The hostname to connect to. Example: `cloudflare.com`.
-
-* `port` number
-  * The port number to connect to. Example: `5432`.
-
-
+- `port` number
+  - The port number to connect to. Example: `5432`.
 
 ### `SocketOptions`
 
+- `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
+  - Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
+  - `off` — Do not use TLS.
+  - `on` — Use TLS.
+  - `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
 
-
-* `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
-  * Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
-  * `off` — Do not use TLS.
-  * `on` — Use TLS.
-  * `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
-
-* `allowHalfOpen` boolean — Defaults to `false`
-  * Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
-  * This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
-
-
+- `allowHalfOpen` boolean — Defaults to `false`
+  - Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
+  - This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
 
 ### `SocketInfo`
 
+- `remoteAddress` string | null
+  - The address of the remote peer the socket is connected to. May not always be set.
 
-
-* `remoteAddress` string | null
-  * The address of the remote peer the socket is connected to. May not always be set.
-
-* `localAddress` string | null
-  * The address of the local network endpoint for this socket. May not always be set.
-
-
+- `localAddress` string | null
+  - The address of the local network endpoint for this socket. May not always be set.
 
 ### `Socket`
 
+- <code>readable</code> : ReadableStream
+  - Returns the readable side of the TCP socket.
 
+- <code>writable</code> : WritableStream
+  - Returns the writable side of the TCP socket.
+  - The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
 
-* <code>readable</code> : ReadableStream
-  * Returns the readable side of the TCP socket.
-
-* <code>writable</code> : WritableStream
-  * Returns the writable side of the TCP socket.
-  * The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
-
-* `opened` `Promise<SocketInfo>`
-  * This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
-
-* `closed` `Promise<void>`
-  * This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
-
-* `close()` `Promise<void>`
-  * Closes the TCP socket. Both the readable and writable streams are forcibly closed.
+- `opened` `Promise<SocketInfo>`
+  - This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
 
-* <code>startTls()</code> : Socket
-  * Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
+- `closed` `Promise<void>`
+  - This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
 
+- `close()` `Promise<void>`
+  - Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
+- <code>startTls()</code> : Socket
+  - Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
 ## Opportunistic TLS (StartTLS)
 
 Many TCP-based systems, including databases and email servers, require that clients use opportunistic TLS (otherwise known as [StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS)) when connecting. In this pattern, the client first creates an insecure TCP socket, without TLS, and then upgrades it to a secure TCP socket, that uses TLS. The `connect()` API simplifies this by providing a method, `startTls()`, which returns a new `Socket` instance that uses TLS:
 
 ```typescript
-import { connect } from "cloudflare:sockets"
+import { connect } from "cloudflare:sockets";
 
 const address = {
-  hostname: "example-postgres-db.com",
-  port: 5432
+	hostname: "example-postgres-db.com",
+	port: 5432,
 };
 const socket = connect(address, { secureTransport: "starttls" });
 const secureSocket = socket.startTls();
 ```
 
-* `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
-* Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
-* `startTls()` should only be called once on an existing socket.
+- `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
+- Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
+- `startTls()` should only be called once on an existing socket.
 
 ## Handle errors
 
 To handle errors when creating a new TCP socket, reading from a socket, or writing to a socket, wrap these calls inside [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) statement blocks. The following example opens a connection to Google.com, initiates a HTTP request, and returns the response. If this fails and throws an exception, it returns a [`500`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-500/) response:
 
 ```typescript
-import { connect } from 'cloudflare:sockets';
+import { connect } from "cloudflare:sockets";
 const connectionUrl = { hostname: "google.com", port: 80 };
-export interface Env { }
+export interface Env {}
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      const socket = connect(connectionUrl);
-      const writer = socket.writable.getWriter();
-      const encoder = new TextEncoder();
-      const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
-      await writer.write(encoded);
-      await writer.close();
-
-      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
-    } catch (error) {
-      return new Response(`Socket connection failed: ${error}`, { status: 500 });
-    }
-  }
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			const socket = connect(connectionUrl);
+			const writer = socket.writable.getWriter();
+			const encoder = new TextEncoder();
+			const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
+			await writer.write(encoded);
+			await writer.close();
+
+			return new Response(socket.readable, {
+				headers: { "Content-Type": "text/plain" },
+			});
+		} catch (error) {
+			return new Response(`Socket connection failed: ${error}`, {
+				status: 500,
+			});
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -174,7 +163,7 @@ export default {
 You can close a TCP connection by calling `close()` on the socket. This will close both the readable and writable sides of the socket.
 
 ```typescript
-import { connect } from "cloudflare:sockets"
+import { connect } from "cloudflare:sockets";
 
 const socket = connect({ hostname: "my-url.com", port: 70 });
 const reader = socket.readable.getReader();
@@ -186,11 +175,11 @@ const reader = socket.readable.getReader(); // This fails
 
 ## Considerations
 
-* Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
-* TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
-* Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
-* By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
-* Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
+- Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
+- TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
+- Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
+- By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
+- Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
 
 ## Troubleshooting
 
diff --git a/src/content/docs/workers/runtime-apis/web-crypto.mdx b/src/content/docs/workers/runtime-apis/web-crypto.mdx
index 9e3a0f0faaaf9f3..5bb7cee5fad993b 100644
--- a/src/content/docs/workers/runtime-apis/web-crypto.mdx
+++ b/src/content/docs/workers/runtime-apis/web-crypto.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 ## Background
 
@@ -19,13 +19,13 @@ Performing cryptographic operations using the Web Crypto API is significantly fa
 The Web Crypto API is implemented through the `SubtleCrypto` interface, accessible via the global `crypto.subtle` binding. A simple example of calculating a digest (also known as a hash) is:
 
 ```js
-const myText = new TextEncoder().encode('Hello world!');
+const myText = new TextEncoder().encode("Hello world!");
 
 const myDigest = await crypto.subtle.digest(
-  {
-    name: 'SHA-256',
-  },
-  myText // The data you want to hash as an ArrayBuffer
+	{
+		name: "SHA-256",
+	},
+	myText, // The data you want to hash as an ArrayBuffer
 );
 
 console.log(new Uint8Array(myDigest));
@@ -38,27 +38,17 @@ Some common uses include [signing requests](/workers/examples/signing-requests/)
 The Web Crypto API differs significantly from the [Node.js Crypto API](/workers/runtime-apis/nodejs/crypto/). If you are working with code that relies on the Node.js Crypto API, you can use it by enabling the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/).
 :::
 
-***
+---
 
 ## Constructors
 
-
-
-* <code>crypto.DigestStream(algorithm)</code> DigestStream
-
-  * A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
-
-
+- <code>crypto.DigestStream(algorithm)</code> DigestStream
+  - A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
 
 ### Parameters
 
-
-
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
-
-
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
 ### Usage
 
@@ -122,27 +112,16 @@ export default {
 
 ## Methods
 
+- <code>crypto.randomUUID()</code> : string
+  - Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
 
-
-* <code>crypto.randomUUID()</code> : string
-
-  * Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
-
-* <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
-
-  * Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
-
-
+- <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
+  - Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
 
 ### Parameters
 
-
-
-* <code>buffer</code>ArrayBufferView
-
-  * Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
-
-
+- <code>buffer</code>ArrayBufferView
+  - Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
 
 ## SubtleCrypto Methods
 
@@ -150,358 +129,219 @@ These methods are all accessed via [`crypto.subtle`](https://developer.mozilla.o
 
 ### encrypt
 
-
-
-* <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
-
-
+- <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>BufferSource
-
-
+- <code>data</code>BufferSource
 
 ### decrypt
 
-
-
-* <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
-
-
+- <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>BufferSource
-
-
+- <code>data</code>BufferSource
 
 ### sign
 
-
-
-* <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
-
-
+- <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>ArrayBuffer
-
-
+- <code>data</code>ArrayBuffer
 
 ### verify
 
-
-
-* <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
-
-  * Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
-
-
+- <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
+  - Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>signature</code>ArrayBuffer
-
-* <code>data</code>ArrayBuffer
-
+- <code>signature</code>ArrayBuffer
 
+- <code>data</code>ArrayBuffer
 
 ### digest
 
-
-
-* <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
-
-
+- <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
-
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
-
-* <code>data</code>ArrayBuffer
-
-
+- <code>data</code>ArrayBuffer
 
 ### generateKey
 
-
-
-* <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
-
-  * Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
+- <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
+  - Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
 
   ```js
   let keyPair = await crypto.subtle.generateKey(
-    {
-      name: 'AES-GCM',
-      length: 256,
-    },
-    true,
-    ['encrypt', 'decrypt']
+  	{
+  		name: "AES-GCM",
+  		length: 256,
+  	},
+  	true,
+  	["encrypt", "decrypt"],
   );
   ```
 
-
-
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
+- <code>extractable</code>bool
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
-
-
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
 ### deriveKey
 
-
-
-* <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
-
-
+- <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
+- <code>baseKeyCryptoKey</code>
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
-
-* <code>baseKeyCryptoKey</code>
-
-* <code>derivedKeyAlgorithmobject</code>
-
-  * Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
-
-* <code>extractablebool</code>
-
-* <code>keyUsagesArray</code>
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
+- <code>derivedKeyAlgorithmobject</code>
+  - Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
+- <code>extractablebool</code>
 
+- <code>keyUsagesArray</code>
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
 ### deriveBits
 
-
-
-* <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
-
-
+- <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
 
+- <code>baseKey</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
-
-* <code>baseKey</code>CryptoKey
-
-* <code>length</code>int
-
-  * Length of the bit string to derive.
-
-
+- <code>length</code>int
+  - Length of the bit string to derive.
 
 ### importKey
 
-
-
-* <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
-
-
+- <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
+- <code>keyData</code>ArrayBuffer
 
-* <code>format</code>string
-
-  * Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
-
-* <code>keyData</code>ArrayBuffer
-
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
+- <code>extractable</code>bool
 
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
 ### exportKey
 
-
-
-* <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
-
-  * Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
-
-
+- <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
+  - Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
 
-
-* <code>format</code>string
-
-  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
-
-* <code>key</code>CryptoKey
-
-
+- <code>key</code>CryptoKey
 
 ### wrapKey
 
-
-
-* <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
-
-  * Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
-
-
+- <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
+  - Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
 
+- <code>key</code>CryptoKey
 
-* <code>format</code>string
-
-  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
-
-* <code>key</code>CryptoKey
-
-* <code>wrappingKey</code>CryptoKey
-
-* <code>wrapAlgo</code>object
-
-  * Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
-
+- <code>wrappingKey</code>CryptoKey
 
+- <code>wrapAlgo</code>object
+  - Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
 
 ### unwrapKey
 
-
-
-* <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
-
-
+- <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
 
 #### Parameters
 
+- <code>format</code>string
+  - Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>format</code>string
-
-  * Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>unwrappingKey</code>CryptoKey
+- <code>unwrappingKey</code>CryptoKey
 
-* <code>unwrapAlgo</code>object
+- <code>unwrapAlgo</code>object
+  - Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
-  * Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>unwrappedKeyAlgo</code>object
-
-  * Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
+- <code>unwrappedKeyAlgo</code>object
+  - Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
+- <code>extractable</code>bool
 
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
 ### timingSafeEqual
 
-
-
-* <code>timingSafeEqual(a, b)</code> : bool
-
-  * Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
-
-
+- <code>timingSafeEqual(a, b)</code> : bool
+  - Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
 
 #### Parameters
 
+- <code>a</code>ArrayBuffer | TypedArray
 
-
-* <code>a</code>ArrayBuffer | TypedArray
-
-* <code>b</code>ArrayBuffer | TypedArray
-
-
+- <code>b</code>ArrayBuffer | TypedArray
 
 ### Supported algorithms
 
@@ -511,8 +351,6 @@ A checkmark (✓) indicates that this feature is believed to be fully supported
 An x (✘) indicates that this feature is part of the specification but not implemented.<br/>
 If a feature only implements the operation partially, details are listed.
 
-
-
 | Algorithm                                          | sign()<br/>verify() | encrypt()<br/>decrypt() | digest() | deriveBits()<br/>deriveKey() | generateKey() | wrapKey()<br/>unwrapKey() | exportKey() | importKey() |
 | :------------------------------------------------- | :------------------ | :---------------------- | :------- | :--------------------------- | :------------ | :------------------------ | :---------- | :---------- |
 | RSASSA PKCS1 v1.5                                  | ✓                   |                         |          |                              | ✓             |                           | ✓           | ✓           |
@@ -536,24 +374,27 @@ If a feature only implements the operation partially, details are listed.
 | HKDF                                               |                     |                         |          | ✓                            |               |                           |             | ✓           |
 | PBKDF2                                             |                     |                         |          | ✓                            |               |                           |             | ✓           |
 
-
-
 **Footnotes:**
 
-1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves API](https://wicg.github.io/webcrypto-secure-curves).
+1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves
+   API](https://wicg.github.io/webcrypto-secure-curves).
 
-2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the Ed25519 curve in addition to the Secure Curves version. Since this algorithm is non-standard, note the following while using it:
+2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the
+   Ed25519 curve in addition to the Secure Curves version. Since this algorithm
+   is non-standard, note the following while using it:
+   - Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
+   - Unlike NodeJS, Cloudflare will not support raw import of private keys.
+   - The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
 
-   * Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
-   * Unlike NodeJS, Cloudflare will not support raw import of private keys.
-   * The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
+3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is
+   supported in Cloudflare Workers for interacting with legacy systems that
+   require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for
+   security.
 
-3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is supported in Cloudflare Workers for interacting with legacy systems that require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for security.
-
-***
+---
 
 ## Related resources
 
-* [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
-* [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
-* [Example: signing requests](/workers/examples/signing-requests/)
+- [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
+- [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
+- [Example: signing requests](/workers/examples/signing-requests/)
diff --git a/src/content/docs/workers/runtime-apis/webassembly/index.mdx b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
index d4a1cb8a2d546a5..492c0ae788ec4ea 100644
--- a/src/content/docs/workers/runtime-apis/webassembly/index.mdx
+++ b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
@@ -9,18 +9,18 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 [WebAssembly](https://webassembly.org/) (abbreviated Wasm) allows you to compile languages like [Rust](/workers/languages/rust/), Go, or C to a binary format that can run in a wide variety of environments, including [web browsers](https://developer.mozilla.org/en-US/docs/WebAssembly#browser_compatibility), Cloudflare Workers, and other WebAssembly runtimes.
 
 You can use WebAssembly to:
 
-* Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
-	:::note
-		`WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
-	:::
+- Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
+  :::note
+  `WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
+  :::
 
-* Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
+- Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
 
 Most programming languages can be compiled to Wasm, although support varies across languages and compilers. Guides are available for the following languages:
 
@@ -50,5 +50,5 @@ WASI is an earlier and more rapidly evolving set of standards than Wasm. WASI su
 
 ### Resources on WebAssembly
 
-* [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
-* [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
+- [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
+- [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
diff --git a/src/content/docs/workers/runtime-apis/websockets.mdx b/src/content/docs/workers/runtime-apis/websockets.mdx
index 6178ac08aa6b4b7..bf31fea43cc174c 100644
--- a/src/content/docs/workers/runtime-apis/websockets.mdx
+++ b/src/content/docs/workers/runtime-apis/websockets.mdx
@@ -14,10 +14,8 @@ WebSockets allow you to communicate in real time with your Cloudflare Workers se
 
 :::note
 
-
 If your application needs to coordinate among multiple WebSocket connections, such as a chat room or game match, you will need clients to send messages to a single-point-of-coordination. Durable Objects provide a single-point-of-coordination for Cloudflare Workers, and are often used in parallel with WebSockets to persist state over multiple clients and connections. In this case, refer to [Durable Objects](/durable-objects/) to get started, and prefer using the Durable Objects' extended [WebSockets API](/durable-objects/best-practices/websockets/).
 
-
 :::
 
 ## Constructor
@@ -39,148 +37,97 @@ let [client, server] = Object.values(new WebSocketPair());
 
 ### accept
 
-
-
-* <code>accept(options?)</code>
-
-  * Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
+- <code>accept(options?)</code>
+  - Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
 
 #### Parameters
 
-
-
-* `options` object optional
-
-  * An optional configuration object with the following properties:
-
-    * `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
-
-
+- `options` object optional
+  - An optional configuration object with the following properties:
+    - `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
 
 ### addEventListener
 
-
-
-* <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
-
-  * Add callback functions to be executed when an event has occurred on the WebSocket.
-
-
+- <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
+  - Add callback functions to be executed when an event has occurred on the WebSocket.
 
 #### Parameters
 
+- `event` WebSocketEvent
+  - The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
 
-
-* `event` WebSocketEvent
-
-  * The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
-
-* <code>callbackFunction(messageMessage)</code> Function
-
-  * A function to be called when the WebSocket responds to a specific event.
-
-
+- <code>callbackFunction(messageMessage)</code> Function
+  - A function to be called when the WebSocket responds to a specific event.
 
 ### close
 
-
-
-* <code>close(codenumber, reasonstring)</code>
-
-  * Close the WebSocket connection.
-
-
+- <code>close(codenumber, reasonstring)</code>
+  - Close the WebSocket connection.
 
 #### Parameters
 
+- <code>codeinteger</code> optional
+  - An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
 
-
-* <code>codeinteger</code> optional
-
-  * An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
-
-* <code>reasonstring</code> optional
-
-  * A human-readable string indicating why the WebSocket connection was closed.
-
-
+- <code>reasonstring</code> optional
+  - A human-readable string indicating why the WebSocket connection was closed.
 
 ### send
 
-
-
-* <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
-
-  * Send a message to the other WebSocket in this WebSocket pair.
-
-
+- <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
+  - Send a message to the other WebSocket in this WebSocket pair.
 
 #### Parameters
 
+- <code>messagestring</code>
+  - The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
 
-
-* <code>messagestring</code>
-
-  * The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
-
-
-
-***
+---
 
 ## Properties
 
 ### readyState
 
-* `readyState` number
+- `readyState` number
+  - Returns the current state of the WebSocket connection. Possible values:
 
-  * Returns the current state of the WebSocket connection. Possible values:
-
-    | Constant | Value | Description |
-    | --- | --- | --- |
-    | `WebSocket.CONNECTING` | `0` | The connection is not yet open. |
-    | `WebSocket.OPEN` | `1` | The connection is open and ready to communicate. |
-    | `WebSocket.CLOSING` | `2` | The connection is in the process of closing. |
-    | `WebSocket.CLOSED` | `3` | The connection is closed. |
+    | Constant               | Value | Description                                      |
+    | ---------------------- | ----- | ------------------------------------------------ |
+    | `WebSocket.CONNECTING` | `0`   | The connection is not yet open.                  |
+    | `WebSocket.OPEN`       | `1`   | The connection is open and ready to communicate. |
+    | `WebSocket.CLOSING`    | `2`   | The connection is in the process of closing.     |
+    | `WebSocket.CLOSED`     | `3`   | The connection is closed.                        |
 
 ### binaryType
 
-* `binaryType` string
-
-  * Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+- `binaryType` string
+  - Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
 
-***
+---
 
 ## Events
 
+- <code>close</code>* An event indicating the WebSocket has closed. The
+  `CloseEvent` includes `code` (number), `reason` (string), and `wasClean`
+  (boolean) properties.
 
+- <code>error</code>* An event indicating there was an error with the WebSocket.
 
-* <code>close</code>
-  * An event indicating the WebSocket has closed. The `CloseEvent` includes `code` (number), `reason` (string), and `wasClean` (boolean) properties.
-
-* <code>error</code>
-  * An event indicating there was an error with the WebSocket.
-
-* <code>message</code>
-  * An event indicating a new message received from the client, including the data passed by the client.
-
-
+- <code>message</code>
+  - An event indicating a new message received from the client, including the data passed by the client.
 
 :::note
-WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes).  If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
+WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes). If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
 :::
 
 ## Types
 
 ### Message
 
+- `data` any - The data passed back from the other WebSocket in your pair.
+- `type` string - Defaults to `message`.
 
-
-* `data` any - The data passed back from the other WebSocket in your pair.
-* `type` string - Defaults to `message`.
-
-
-
-***
+---
 
 ## Close behavior
 
@@ -190,10 +137,10 @@ If you still call `close()` inside the `close` event handler, the call is silent
 
 ```js
 server.addEventListener("close", (event) => {
-  // readyState is already CLOSED — no need to call server.close().
-  console.log(server.readyState); // WebSocket.CLOSED
-  console.log(event.code);        // 1000
-  console.log(event.wasClean);    // true
+	// readyState is already CLOSED — no need to call server.close().
+	console.log(server.readyState); // WebSocket.CLOSED
+	console.log(event.code); // 1000
+	console.log(event.wasClean); // true
 });
 ```
 
@@ -205,12 +152,12 @@ The automatic close behavior can interfere with WebSocket proxying, where a Work
 server.accept({ allowHalfOpen: true });
 
 server.addEventListener("close", (event) => {
-  // readyState is still CLOSING here, giving you time
-  // to coordinate the close on the other side.
-  console.log(server.readyState); // WebSocket.CLOSING
+	// readyState is still CLOSING here, giving you time
+	// to coordinate the close on the other side.
+	console.log(server.readyState); // WebSocket.CLOSING
 
-  // Manually close when ready.
-  server.close(event.code, "done");
+	// Manually close when ready.
+	server.close(event.code, "done");
 });
 ```
 
@@ -224,7 +171,7 @@ WebSockets created with `new WebSocket(url)` always auto-reply to Close frames a
 
 On compatibility dates before `2026-04-07` (or with the `web_socket_manual_reply_to_close` flag), receiving a Close frame leaves the WebSocket in `CLOSING` state, and your code must call `close()` to complete the handshake. Failing to do so can result in `1006` abnormal closure errors on the client.
 
-***
+---
 
 ## Binary messages
 
@@ -236,7 +183,7 @@ The `binaryType` property itself is always available. To opt back into `ArrayBuf
 
 ```js
 const resp = await fetch("https://example.com", {
-  headers: { Upgrade: "websocket" },
+	headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -245,11 +192,11 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-  if (typeof event.data === "string") {
-    // Text frame.
-  } else {
-    // event.data is an ArrayBuffer because we set binaryType above.
-  }
+	if (typeof event.data === "string") {
+		// Text frame.
+	} else {
+		// event.data is an ArrayBuffer because we set binaryType above.
+	}
 });
 ```
 
@@ -276,9 +223,9 @@ This flag has no effect on the Durable Object hibernatable WebSocket [`webSocket
 
 :::
 
-***
+---
 
 ## Related resources
 
-* [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
-* [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
+- [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
+- [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
diff --git a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
index 31e081797dd1ada..0ba52cb42d3e81a 100644
--- a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
+++ b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
@@ -14,10 +14,7 @@ Full-stack applications are web applications which are span both the client and
 
 The following full-stack frameworks are natively supported by Workers:
 
-<DirectoryListing
-	folder="workers/framework-guides/web-apps"
-	tag="full-stack"
-/>
+<DirectoryListing folder="workers/framework-guides/web-apps" tag="full-stack" />
 <DirectoryListing
 	folder="workers/framework-guides/web-apps/more-web-frameworks"
 	tag="full-stack"
diff --git a/src/content/docs/workers/testing/miniflare/storage/cache.md b/src/content/docs/workers/testing/miniflare/storage/cache.md
index 78aac412fb542af..c7c385b4cbe8025 100644
--- a/src/content/docs/workers/testing/miniflare/storage/cache.md
+++ b/src/content/docs/workers/testing/miniflare/storage/cache.md
@@ -86,7 +86,9 @@ console.log(await res.text()); // 2
 You can programmatically purge all entries from a cache using the `purgeCache` method on the `Miniflare` instance. This is useful during development when cached assets need to be cleared without restarting the instance:
 
 ```js
-const mf = new Miniflare({ /* options */ });
+const mf = new Miniflare({
+	/* options */
+});
 
 // Purge the default cache and get the number of entries purged
 const count = await mf.purgeCache();
diff --git a/src/content/docs/workers/testing/vitest-integration/recipes.mdx b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
index 79fb21b23ea73f1..d125b33d9e53931 100644
--- a/src/content/docs/workers/testing/vitest-integration/recipes.mdx
+++ b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
@@ -30,4 +30,4 @@ Recipes are examples that help demonstrate how to write unit tests and integrati
 - [Resolving modules with Vite Dependency Pre-Bundling](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/module-resolution)
 - [Mocking Workers AI and Vectorize bindings in unit tests](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/ai-vectorize)
 - [Tests using the Images binding](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/images)
-- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
\ No newline at end of file
+- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
diff --git a/src/content/docs/workers/vite-plugin/tutorial.mdx b/src/content/docs/workers/vite-plugin/tutorial.mdx
index c5b6e9446a92aa4..ef7f05b8c086add 100644
--- a/src/content/docs/workers/vite-plugin/tutorial.mdx
+++ b/src/content/docs/workers/vite-plugin/tutorial.mdx
@@ -205,6 +205,7 @@ This opts out of interpreting the `Sec-Fetch-Mode` header.
 ```
 
 </WranglerConfig>
+
 :::
 
 ### Call the API from the client
diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx
index 8b28f295cdc13b8..ccabcb8262755a1 100644
--- a/src/content/docs/workers/wrangler/api.mdx
+++ b/src/content/docs/workers/wrangler/api.mdx
@@ -50,9 +50,7 @@ const result = await experimental_generateTypes(options);
 ### Parameters
 
 - `options` <Type text="object" /> <MetaInfo text="optional" />
-
   - Optional options object mirroring the `wrangler types` CLI flags:
-
     - `config` `string | string[]`
 
       Path to the Wrangler configuration file to use. Can be an array for multi-config type resolution.
@@ -90,19 +88,15 @@ const result = await experimental_generateTypes(options);
 `experimental_generateTypes()` returns a `Promise` resolving to an object containing the following fields:
 
 - `content` `string`
-
   - Combined formatted output containing all generated sections, including headers and both env and runtime types.
 
 - `env` `string | null`
-
   - Generated environment and bindings types, or `null` when env types are excluded.
 
 - `path` `string`
-
   - Target declaration file path associated with this generation run.
 
 - `runtime` `string | null`
-
   - Generated runtime types, or `null` when runtime types are excluded.
 
 ### Usage
@@ -506,22 +500,22 @@ The bindings supported by `getPlatformProxy` are:
     For example, you might have the following binding in a Wrangler configuration file read by `getPlatformProxy`.
 
     <WranglerConfig>
-            
-                ```jsonc
-                {
-                  "durable_objects": {
-                    "bindings": [
-                      {
-                        "name": "MyDurableObject",
-                        "class_name": "MyDurableObject",
-                        "script_name": "external-do-worker"
+                
+                    ```jsonc
+                    {
+                      "durable_objects": {
+                        "bindings": [
+                          {
+                            "name": "MyDurableObject",
+                            "class_name": "MyDurableObject",
+                            "script_name": "external-do-worker"
+                          }
+                        ]
                       }
-                    ]
-                  }
-                }
-                ```
-            
-                </WranglerConfig>
+                    }
+                    ```
+                
+                    </WranglerConfig>
 
     You will need to declare your Durable Object `"MyDurableObject"` in another Worker, called `external-do-worker` in this example.
 
@@ -541,14 +535,14 @@ The bindings supported by `getPlatformProxy` are:
     That Worker also needs a Wrangler configuration file that looks like this:
 
     <WranglerConfig>
-                    ```json
-                    {
-                    	"name": "external-do-worker",
-                    	"main": "src/index.ts",
-                    	"compatibility_date": "XXXX-XX-XX"
-                    }
-                    ```
-                    </WranglerConfig>
+                        ```json
+                        {
+                        	"name": "external-do-worker",
+                        	"main": "src/index.ts",
+                        	"compatibility_date": "XXXX-XX-XX"
+                        }
+                        ```
+                        </WranglerConfig>
 
     If you are not using RPC with your Durable Object, you can run a separate Wrangler dev session alongside your framework development server.
 
diff --git a/src/content/docs/workers/wrangler/commands/r2.mdx b/src/content/docs/workers/wrangler/commands/r2.mdx
index 60266e3b8e29b81..fb437a18a9717a9 100644
--- a/src/content/docs/workers/wrangler/commands/r2.mdx
+++ b/src/content/docs/workers/wrangler/commands/r2.mdx
@@ -10,7 +10,6 @@ import { Render } from "~/components";
 
 Manage your [R2](/r2/) configurations using Wrangler.
 
-
 <Render file="wrangler-commands/r2" product="workers" />
 
 ## R2 SQL
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
index f32639e194e9391..d19eda7c7872fca 100644
--- a/src/content/docs/workers/wrangler/configuration.mdx
+++ b/src/content/docs/workers/wrangler/configuration.mdx
@@ -1839,26 +1839,26 @@ A common example of using a redirected configuration is where a custom build too
 - First, the user writes code that uses Cloudflare Workers resources, configured via a user's Wrangler configuration file like the following:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-  	"$schema": "./node_modules/wrangler/config-schema.json",
-  	"name": "my-worker",
-  	"main": "src/index.ts",
-  	"vars": {
-  		"MY_VARIABLE": "production variable",
-  	},
-  	"env": {
-  		"staging": {
-  			"vars": {
-  				"MY_VARIABLE": "staging variable",
-  			},
-  		},
-  	},
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+    	"$schema": "./node_modules/wrangler/config-schema.json",
+    	"name": "my-worker",
+    	"main": "src/index.ts",
+    	"vars": {
+    		"MY_VARIABLE": "production variable",
+    	},
+    	"env": {
+    		"staging": {
+    			"vars": {
+    				"MY_VARIABLE": "staging variable",
+    			},
+    		},
+    	},
+    }
+    ```
+  
+    </WranglerConfig>
 
   This configuration points `main` at the user's code entry-point and defines the `MY_VARIABLE` variable in two different environments.
 
@@ -1872,8 +1872,8 @@ A common example of using a redirected configuration is where a custom build too
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>
-  	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
-  </FileTree>
+    	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
+    </FileTree>
 
 The generated `dist/wrangler.jsonc` might contain:
 
@@ -1896,4 +1896,4 @@ And the `.wrangler/deploy/config.json` contains the path to the generated config
 {
 	"configPath": "../../dist/wrangler.jsonc"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/workers/wrangler/custom-builds.mdx b/src/content/docs/workers/wrangler/custom-builds.mdx
index 0b63ae3bd2a8037..e22e4bc6c269534 100644
--- a/src/content/docs/workers/wrangler/custom-builds.mdx
+++ b/src/content/docs/workers/wrangler/custom-builds.mdx
@@ -21,15 +21,12 @@ Wrangler runs [esbuild](https://esbuild.github.io/) by default as part of the `d
 Custom builds are configured by adding a `[build]` section in your [Wrangler configuration file](/workers/wrangler/configuration/), and using the following options for configuring your custom build.
 
 - `command` <Type text="string" /> <MetaInfo text="optional" />
-
   - The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used. This command will be run as part of `wrangler dev` and `npx wrangler deploy`.
 
 - `cwd` <Type text="string" /> <MetaInfo text="optional" />
-
   - The directory in which the command is executed.
 
 - `watch_dir` <Type text="string | string\[]" /> <MetaInfo text="optional" />
-
   - The directory to watch for changes while using `wrangler dev`. Defaults to the current working directory.
 
 Example:
@@ -54,12 +51,12 @@ When Wrangler runs your custom build command, it sets the `WRANGLER_COMMAND` env
 
 The possible values are:
 
-| Value              | Wrangler command triggered               |
-| ------------------ | ---------------------------------------- |
-| `dev`              | `wrangler dev`                           |
-| `deploy`           | `wrangler deploy`                        |
-| `versions upload`  | `wrangler versions upload`               |
-| `types`            | `wrangler types`                         |
+| Value             | Wrangler command triggered |
+| ----------------- | -------------------------- |
+| `dev`             | `wrangler dev`             |
+| `deploy`          | `wrangler deploy`          |
+| `versions upload` | `wrangler versions upload` |
+| `types`           | `wrangler types`           |
 
 For example, you can use this to apply different build settings for development and production:
 
diff --git a/src/content/docs/workers/wrangler/deprecations.mdx b/src/content/docs/workers/wrangler/deprecations.mdx
index 3b4d23ccc8c99eb..ab606324004172b 100644
--- a/src/content/docs/workers/wrangler/deprecations.mdx
+++ b/src/content/docs/workers/wrangler/deprecations.mdx
@@ -83,82 +83,89 @@ This no longer has any effect, after the [rollout of Workers Standard Pricing](h
 
 Wrangler v2 introduces new fields for configuration and new features for developing and deploying a Worker, while deprecating some redundant fields.
 
-* `wrangler.toml` is no longer mandatory.
-* `dev` and `publish` accept CLI arguments.
-* `tail` can be run on arbitrary Worker names.
-* `init` creates a project boilerplate.
-* JSON bindings for `vars`.
-* Local mode for `wrangler dev`.
-* Module system (for both modules and service worker format Workers).
-* DevTools.
-* TypeScript support.
-* Sharing development environment on the Internet.
-* Wider platform compatibility.
-* Developer hotkeys.
-* Better configuration validation.
+- `wrangler.toml` is no longer mandatory.
+- `dev` and `publish` accept CLI arguments.
+- `tail` can be run on arbitrary Worker names.
+- `init` creates a project boilerplate.
+- JSON bindings for `vars`.
+- Local mode for `wrangler dev`.
+- Module system (for both modules and service worker format Workers).
+- DevTools.
+- TypeScript support.
+- Sharing development environment on the Internet.
+- Wider platform compatibility.
+- Developer hotkeys.
+- Better configuration validation.
 
 The following video describes some of the major changes in Wrangler v2, and shows you how Wrangler v2 can help speed up your workflow.
 
-<div style="position: relative; padding-top: 56.25%;"><iframe src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600" style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;" allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;" allowfullscreen="true"></iframe></div>
+<div style="position: relative; padding-top: 56.25%;">
+	<iframe
+		src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
+</div>
 
 ### Common deprecations
 
 Refer to the following list for common fields that are no longer required.
 
-* `type` is no longer required. Wrangler will infer the correct project type automatically.
-* `zone_id` is no longer required. It can be deduced from the routes directly.
-* `build.upload.format` is no longer used. The format is now inferred automatically from the code.
-* `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
-* `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
-* `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
+- `type` is no longer required. Wrangler will infer the correct project type automatically.
+- `zone_id` is no longer required. It can be deduced from the routes directly.
+- `build.upload.format` is no longer used. The format is now inferred automatically from the code.
+- `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
+- `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
+- `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
   Here are the Wrangler v1 commands that are no longer supported:
-* `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
-* `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
-* `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
-* `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
-* `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
+- `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
+- `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
+- `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
+- `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
+- `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
 
 #### New fields
 
 These are new fields that can be added to your [Wrangler configuration file](/workers/wrangler/configuration/).
 
-* **`main`**: `string`, optional
+- **`main`**: `string`, optional
 
   The `main` field is used to specify an entry point to the Worker. It may be in the established service worker format, or the newer, preferred modules format. An entry point is now explicitly required, and can be configured either via the `main` field, or passed directly as a command line, for example, `wrangler dev index.js`. This field replaces the legacy `build.upload.main` field (which only applied to modules format Workers).
 
-* **`rules`**: `array`, optional
+- **`rules`**: `array`, optional
 
   The `rules` field is an array of mappings between module types and file patterns. It instructs Wrangler to interpret specific files differently than JavaScript. For example, this is useful for reading text-like content as text files, or compiled WASM as ready to instantiate and execute. These rules can apply to Workers of both the established service worker format, and the newer modules format. This field replaces the legacy `build.upload.rules` field (which only applied to modules format Workers).
 
-{/* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
+{/\* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
 
-  The `legacy_env` field toggles how environments are handled by `wrangler`.
+The `legacy_env` field toggles how environments are handled by `wrangler`.
 
-  - When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
-  - When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
-    Read more at (ref:)[] --> */}
+- When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
+- When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
+  Read more at (ref:)[] --> \*/}
 
-{/* <!-- - **`services`**: TODO
+{/\* <!-- - **`services`**: TODO
 
 - **`node-compat`**: TODO
 
-- **`public`**: TODO --> */}
+- **`public`**: TODO --> \*/}
 
 #### Non-mandatory fields
 
 A few configuration fields which were previously required, are now optional in particular situations. They can either be inferred, or added as an optimization. No fields are required anymore when starting with Wrangler v2, and you can gradually add configuration as the need arises.
 
-* **`name`**: `string`
+- **`name`**: `string`
 
   The `name` configuration field is now not required for `wrangler dev`, or any of the `wrangler kv:*` commands. Further, it can also be passed as a command line argument as `--name <name>`. It is still required for `wrangler deploy`.
 
-* **`account_id`**: `string`
+- **`account_id`**: `string`
 
   The `account_id` field is not required for any of the commands. Any relevant commands will check if you are logged in, and if not, will prompt you to log in. Once logged in, it will use your account ID and will not prompt you again until your login session expires. If you have multiple account IDs, you will be presented with a list of accounts to choose from.
 
   You can still configure `account_id` in your Wrangler file, or as an environment variable `CLOUDFLARE_ACCOUNT_ID`. This makes startup faster and bypasses the list of choices if you have multiple IDs. The `CLOUDFLARE_API_TOKEN` environment variable is also useful for situations where it is not possible to login interactively. To learn more, visit [Running in CI/CD](/workers/ci-cd/external-cicd/).
 
-* **`workers_dev`** `boolean`, default: `true` when no routes are present
+- **`workers_dev`** `boolean`, default: `true` when no routes are present
 
   The `workers_dev` field is used to indicate that the Worker should be published to a `*.workers.dev` subdomain. For example, for a Worker named `my-worker` and a previously configured `*.workers.dev` subdomain `username`, the Worker will get published to `my-worker.username.workers.dev.com`. This field is not mandatory, and defaults to `true` when `route` or `routes` are not configured. When routes are present, it defaults to `false`. If you want to neither publish it to a `*.workers.dev` subdomain nor any routes, set `workers_dev` to `false`. This useful when you are publishing a Worker as a standalone service that can only be accessed from another Worker with (`services`).
 
@@ -166,27 +173,26 @@ A few configuration fields which were previously required, are now optional in p
 
 A few configuration fields are deprecated, but their presence is not a breaking change yet. It is recommended to read the warning messages and follow the instructions to migrate to the new configuration. They will be removed and stop working in a future version.
 
-* **`zone_id`**: `string`, deprecated
+- **`zone_id`**: `string`, deprecated
 
   The `zone_id` field is deprecated and will be removed in a future release. It is now inferred from `route`/`routes`, and optionally from `dev.host` when using `wrangler dev`. This also makes it simpler to deploy a single Worker to multiple domains.
 
-* **`build.upload`**: `object`, deprecated
+- **`build.upload`**: `object`, deprecated
 
   The `build.upload` field is deprecated and will be removed in a future release. Its usage results in a warning with suggestions on rewriting the configuration file to remove the warnings.
-
-  * `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
-  * `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
-  * `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
+  - `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
+  - `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
+  - `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
 
 #### Deprecated fields (breaking)
 
 A few configuration fields are deprecated and will not work as expected anymore. It is recommended to read the error messages and follow the instructions to migrate to the new configuration.
 
-* **`site.entry-point`**: `string`, deprecated
+- **`site.entry-point`**: `string`, deprecated
 
   The `site.entry-point` configuration was used to specify an entry point for Workers with a `[site]` configuration. This has been replaced by the top-level `main` field.
 
-* **`type`**: `rust` | `javascript` | `webpack`, deprecated
+- **`type`**: `rust` | `javascript` | `webpack`, deprecated
 
   The `type` configuration was used to specify the type of Worker. It has since been made redundant and is now inferred from usage. If you were using `type = "webpack"` (and the optional `webpack_config` field), you should read the [webpack migration guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to modify your project and use a custom build instead.
 
@@ -226,11 +232,11 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 ### Other deprecated behavior
 
-* Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
+- Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
 
-* Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
+- Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
 
-* Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
+- Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
 
   ```
   project
@@ -244,7 +250,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
   import SomeDependency from "some-dependency.js";
 
   addEventListener("fetch", (event) => {
-    // ...
+  	// ...
   });
   ```
 
@@ -259,8 +265,8 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Commands
 
-| Command     | v1 | v2 | Notes                                          |
-| ----------- | -- | -- | ---------------------------------------------- |
+| Command     | v1  | v2  | Notes                                          |
+| ----------- | --- | --- | ---------------------------------------------- |
 | `publish`   | ✅  | ✅  |                                                |
 | `dev`       | ✅  | ✅  |                                                |
 | `preview`   | ✅  | ❌  | Removed, use `dev` instead.                    |
@@ -271,7 +277,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 | `route`     | ✅  | ❌  | Removed, use `publish` instead.                |
 | `tail`      | ✅  | ✅  |                                                |
 | `kv`        | ✅  | ✅  |                                                |
-| `r2`        | 🚧 | ✅  | Introduced in Wrangler v1.19.8.                |
+| `r2`        | 🚧  | ✅  | Introduced in Wrangler v1.19.8.                |
 | `pages`     | ❌  | ✅  |                                                |
 | `config`    | ✅  | ❓  |                                                |
 | `login`     | ✅  | ✅  |                                                |
@@ -282,15 +288,15 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Configuration
 
-| Property              | v1 | v2 | Notes                                                                                                                                            |
-| --------------------- | -- | -- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Property              | v1  | v2  | Notes                                                                                           |
+| --------------------- | --- | --- | ----------------------------------------------------------------------------------------------- |
 | `type = "webpack"`    | ✅  | ❌  | Removed, refer to [this guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to migrate. |
-| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                                                                   |
-| `type = "javascript"` | ✅  | 🚧 | No longer required, can be omitted.                                                                                                              |
+| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                  |
+| `type = "javascript"` | ✅  | 🚧  | No longer required, can be omitted.                                                             |
 
 #### Features
 
-| Feature    | v1 | v2 | Notes                                                                                                                                                                                                 |
-| ---------- | -- | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Feature    | v1  | v2  | Notes                                                                                                                                                                                                 |
+| ---------- | --- | --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | TypeScript | ❌  | ✅  | You can give wrangler a TypeScript file, and it will automatically transpile it to JavaScript using [`esbuild`](https://github.com/evanw/esbuild) under-the-hood.                                     |
 | Local mode | ❌  | ✅  | `wrangler dev --local` will run your Worker on your local machine instead of on our network. This is powered by [Miniflare](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare/). |
diff --git a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
index 8092bb1422993dd..6f633bb98248e76 100644
--- a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
+++ b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
@@ -12,10 +12,8 @@ There are no special instructions for migrating from Wrangler v2 to v3. You shou
 
 :::caution
 
-
 If you tried to update to Wrangler v3 prior to v3.3, you may have experienced some compatibility issues with older operating systems. Please try again with the latest v3 where those have been resolved.
 
-
 :::
 
 ## Deprecations
diff --git a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
index 5c0712ab06b89e5..a700b3c6cef0bbc 100644
--- a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
+++ b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
@@ -12,7 +12,13 @@ products:
   - workers
 ---
 
-import { Render, Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 <Render file="wrangler-v1-deprecation" product="workers" />
 
diff --git a/src/content/docs/workflows/build/index.mdx b/src/content/docs/workflows/build/index.mdx
index 317e4c6fd68d3d8..d37b306c71a2e1e 100644
--- a/src/content/docs/workflows/build/index.mdx
+++ b/src/content/docs/workflows/build/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/build/test-workflows.mdx b/src/content/docs/workflows/build/test-workflows.mdx
index bf533e4a14be140..8752df04fd942ab 100644
--- a/src/content/docs/workflows/build/test-workflows.mdx
+++ b/src/content/docs/workflows/build/test-workflows.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 11
 products:
   - workflows
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workflows/examples/agents.mdx b/src/content/docs/workflows/examples/agents.mdx
index 4395885fbb20f1b..dabdf0389fd185b 100644
--- a/src/content/docs/workflows/examples/agents.mdx
+++ b/src/content/docs/workflows/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workflows
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workflows/examples/backup-d1.mdx b/src/content/docs/workflows/examples/backup-d1.mdx
index a22c45b46fda50d..1ef6fc225a7cfea 100644
--- a/src/content/docs/workflows/examples/backup-d1.mdx
+++ b/src/content/docs/workflows/examples/backup-d1.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Export a D1 database into R2 storage with Workflows
 products: [d1, r2]
 tags:
diff --git a/src/content/docs/workflows/examples/send-invoices.mdx b/src/content/docs/workflows/examples/send-invoices.mdx
index 290cf8159582787..88c4d7c81871595 100644
--- a/src/content/docs/workflows/examples/send-invoices.mdx
+++ b/src/content/docs/workflows/examples/send-invoices.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send invoice when shopping cart is checked out and paid for
 products: [d1, email-routing]
 tags:
diff --git a/src/content/docs/workflows/examples/twilio.mdx b/src/content/docs/workflows/examples/twilio.mdx
index f9a9331974d6ad1..08df323ebf3258d 100644
--- a/src/content/docs/workflows/examples/twilio.mdx
+++ b/src/content/docs/workflows/examples/twilio.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Integrate Workflows with Twilio. Learn how to receive and send text messages and phone calls via APIs and Webhooks.
 products: [workers]
 pcx_content_type: example
diff --git a/src/content/docs/workflows/examples/wait-for-event.mdx b/src/content/docs/workflows/examples/wait-for-event.mdx
index 95cc28394e9e6ec..0e46962c459c1ab 100644
--- a/src/content/docs/workflows/examples/wait-for-event.mdx
+++ b/src/content/docs/workflows/examples/wait-for-event.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Implement a Cloudflare Workflow that processes user-uploaded images, awaits human approval, and performs AI-based image tagging upon approval.
 tags:
   - Typescript
@@ -13,7 +12,7 @@ products:
   - workflows
 ---
 
-import {  GitHubCode, WranglerConfig } from "~/components"
+import { GitHubCode, WranglerConfig } from "~/components";
 
 This example demonstrates how to use the `waitForEvent()` API in Cloudflare Workflows to introduce a human-in-the-loop step. The Workflow is triggered by an image upload, during which metadata is stored in a D1 database. The Workflow then waits for user approval, and upon approval, it uses Workers AI to generate image tags, which are stored in the database. An accompanying Next.js frontend application facilitates the image upload and approval process.
 
@@ -45,12 +44,12 @@ The `index.ts` file defines the core logic of the Cloudflare Workflow responsibl
 For the complete implementation of the `index.ts` file, please refer to the [GitHub repository](https://github.com/cloudflare/docs-examples/blob/main/workflows/waitForEvent/workflow/src/index.ts).
 
 <GitHubCode
-  repo="cloudflare/docs-examples"
-  file="workflows/waitForEvent/workflow/src/index.ts"
-  commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
-  lang="ts"
+	repo="cloudflare/docs-examples"
+	file="workflows/waitForEvent/workflow/src/index.ts"
+	commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
+	lang="ts"
 	lines="17-57"
-  useTypeScriptExample={true}
+	useTypeScriptExample={true}
 />
 
 ## Workflow wrangler.jsonc
diff --git a/src/content/docs/workflows/observability/index.mdx b/src/content/docs/workflows/observability/index.mdx
index 9fb63d677e9caec..8a5a7d7938f5dfc 100644
--- a/src/content/docs/workflows/observability/index.mdx
+++ b/src/content/docs/workflows/observability/index.mdx
@@ -5,11 +5,11 @@ pcx_content_type: navigation
 sidebar:
   order: 5
   group:
-   hideIndex: true
+    hideIndex: true
 products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/python/bindings.mdx b/src/content/docs/workflows/python/bindings.mdx
index ea31fe2f488a996..a861b88223cc0f3 100644
--- a/src/content/docs/workflows/python/bindings.mdx
+++ b/src/content/docs/workflows/python/bindings.mdx
@@ -153,7 +153,7 @@ class Default(WorkerEntrypoint):
 Send an event to a workflow instance.
 
 - <code>send_event(options)</code>* `type` - the type of event to send to the
-  workflow instance. * `payload` - the payload to send to the workflow instance.
+  workflow instance. \* `payload` - the payload to send to the workflow instance.
 
 ```python
 from pyodide.ffi import to_js
diff --git a/src/content/docs/workflows/reference/changelog.mdx b/src/content/docs/workflows/reference/changelog.mdx
index beba6e99cb7a9fe..00df519b89f7276 100644
--- a/src/content/docs/workflows/reference/changelog.mdx
+++ b/src/content/docs/workflows/reference/changelog.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: changelog
-title: Release notes 
+title: Release notes
 description: Latest release notes and changes for Cloudflare Workflows.
 release_notes_file_name:
   - workflows
@@ -10,7 +10,7 @@ products:
   - workflows
 ---
 
-import { ProductReleaseNotes } from "~/components"
+import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /data/changelogs/workflows.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workflows/reference/glossary.mdx b/src/content/docs/workflows/reference/glossary.mdx
index e19733552053c95..c6bc3d0908b0a9d 100644
--- a/src/content/docs/workflows/reference/glossary.mdx
+++ b/src/content/docs/workflows/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Workflows documentation.
 
diff --git a/src/content/docs/workflows/reference/index.mdx b/src/content/docs/workflows/reference/index.mdx
index 89abc260ef45793..6df95f6daddcdc4 100644
--- a/src/content/docs/workflows/reference/index.mdx
+++ b/src/content/docs/workflows/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/reference/pricing.mdx b/src/content/docs/workflows/reference/pricing.mdx
index db0a2a5aa7c5f2e..283b87cdbd8653d 100644
--- a/src/content/docs/workflows/reference/pricing.mdx
+++ b/src/content/docs/workflows/reference/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 :::note
 
@@ -18,19 +18,19 @@ Workflows is included in both the Free and Paid [Workers plans](/workers/platfor
 
 Workflows pricing is identical to [Workers Standard pricing](/workers/platform/pricing/#workers) and are billed on three dimensions:
 
-* **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
-* **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
-* **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
+- **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
+- **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
+- **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
 
 A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle, does not incur CPU time.
 
 ### Workflows Pricing
 
-| Unit | Workers Free | Workers Paid |
-|------|--------------|--------------|
-| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers)| 10 million included per month + $0.30 per additional million	|
-| CPU time (ms) | 10 milliseconds of CPU time per invocation | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
-| Storage (GB-mo) | 1GB | 1GB included per month + $0.20/ GB-month |
+| Unit                | Workers Free                                                                        | Workers Paid                                                                                   |
+| ------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers) | 10 million included per month + $0.30 per additional million                                   |
+| CPU time (ms)       | 10 milliseconds of CPU time per invocation                                          | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
+| Storage (GB-mo)     | 1GB                                                                                 | 1GB included per month + $0.20/ GB-month                                                       |
 
 :::note[CPU limits]
 
@@ -48,10 +48,10 @@ Storage billing for Workflows will go live on September 15th, 2025.
 
 Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to [Durable Objects SQL storage](/durable-objects/platform/pricing/#sqlite-storage-backend). A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).
 
-* Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
-* By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
-* When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
-* Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
+- Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
+- By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
+- When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
+- Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
 
 An instance that attempts to store state when your have reached the storage limit on the Free plan will cause an error to be thrown.
 
diff --git a/src/content/docs/workflows/reference/wrangler-commands.mdx b/src/content/docs/workflows/reference/wrangler-commands.mdx
index b80050771f16411..2ad49f1ed36f4a1 100644
--- a/src/content/docs/workflows/reference/wrangler-commands.mdx
+++ b/src/content/docs/workflows/reference/wrangler-commands.mdx
@@ -8,6 +8,6 @@ products:
   - workflows
 ---
 
-import {WranglerNamespace} from "~/components";
+import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="workflows"/>
+<WranglerNamespace namespace="workflows" />
diff --git a/src/content/docs/workflows/videos.mdx b/src/content/docs/workflows/videos.mdx
index 0b45561d7cdf80d..8d5a6926d7c97fa 100644
--- a/src/content/docs/workflows/videos.mdx
+++ b/src/content/docs/workflows/videos.mdx
@@ -11,9 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Build an application using Cloudflare Workflows"
-        description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
-        href="/learning-paths/workflows-course/series/workflows-1/"
-    />
+	<LinkCard
+		title="Build an application using Cloudflare Workflows"
+		description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
+		href="/learning-paths/workflows-course/series/workflows-1/"
+	/>
 </CardGrid>
diff --git a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
index 07719d8b84e7244..e537c733bce84dd 100644
--- a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
+++ b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
@@ -6,7 +6,6 @@ products:
 title: Data layer compatibility mode
 sidebar:
   order: 3
-
 ---
 
 Cloudflare Zaraz offers backwards compatibility with the `dataLayer` function found in tag management software, used to track events and other parameters. This way you can keep your current implementation and Cloudflare Zaraz will automatically collect your events.
@@ -28,10 +27,10 @@ Events will only be sent to Zaraz if your pushed object includes an `event` key.
 
 ```js
 dataLayer.push({
-  event: 'purchase',
-  price: '24',
-  currency: 'USD',
-  transactionID: '12345678',
+	event: "purchase",
+	price: "24",
+	currency: "USD",
+	transactionID: "12345678",
 });
 ```
 
@@ -41,6 +40,6 @@ Because Zaraz converts the `dataLayer.push()` call to `zaraz.track()`, creating
 
 | Rule type    | Variable name | Match operation | Match string |
 | ------------ | ------------- | --------------- | ------------ |
-| *Match rule* | *Event Name*  | *Equals*        | `purchase`   |
+| _Match rule_ | _Event Name_  | _Equals_        | `purchase`   |
 
 We do not recommend using `dataLayer`. However, as many websites employ it, Cloudflare Zaraz has this automatic translation layer that converts it to `zaraz.track()`.
diff --git a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
index 571d8120641dd8c..359716b4e8520a1 100644
--- a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
+++ b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Use Zaraz on domains not proxied by Cloudflare
-
 ---
 
 You can load Zaraz on domains that are not proxied through Cloudflare. However, you will need to create a separate domain, or subdomain, proxied by Cloudflare (also [known as orange-clouded](https://community.cloudflare.com/t/step-3-enabling-the-orange-cloud/52715) domains), and load the script from it:
diff --git a/src/content/docs/zaraz/advanced/google-consent-mode.mdx b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
index 32b7951c7c0b104..730a6cf363a3bba 100644
--- a/src/content/docs/zaraz/advanced/google-consent-mode.mdx
+++ b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
@@ -6,7 +6,6 @@ products:
 title: Google Consent Mode
 sidebar:
   order: 4
-
 ---
 
 ## Background
@@ -15,7 +14,7 @@ sidebar:
 
 You can also use Google Analytics and Google Ads without cookies by selecting **Permissions** and disabling **Access client key-value store**.
 
-***
+---
 
 ## Consent Mode v2
 
@@ -28,12 +27,12 @@ Often websites will want to set a default consent status that denies all categor
 If that is not what your website needs, and instead you want to set the default consent status in a more granular way, use the reserved `google_consent_default` property:
 
 ```js
-zaraz.set("google_consent_default",  {
-  'ad_storage': 'denied',
-  'ad_user_data': 'denied',
-  'ad_personalization': 'denied',
-  'analytics_storage': 'denied'
-})
+zaraz.set("google_consent_default", {
+	ad_storage: "denied",
+	ad_user_data: "denied",
+	ad_personalization: "denied",
+	analytics_storage: "denied",
+});
 ```
 
 After the above code is executed, the consent status will be saved to `localStorage` and will be included with every subsequent Zaraz event.
@@ -45,12 +44,12 @@ Note that the code should be included as part of your website HTML code, usually
 After the user has provided their consent preferences you can set the new status using the reserved `google_consent_update` property. If you are using the Zaraz Consent Management Platform, you can use the [Consent Choices Updated event](/zaraz/consent-management/api/#consent-choices-updated) to know when to update the Google Consent status.
 
 ```js
-zaraz.set("google_consent_update",  {
-  'ad_storage': 'granted',
-  'ad_user_data': 'denied',
-  'ad_personalization': 'granted',
-  'analytics_storage': 'denied'
-})
+zaraz.set("google_consent_update", {
+	ad_storage: "granted",
+	ad_user_data: "denied",
+	ad_personalization: "granted",
+	analytics_storage: "denied",
+});
 ```
 
 All subsequent events will include the information about both the default and the updated consent status.
diff --git a/src/content/docs/zaraz/advanced/import-export.mdx b/src/content/docs/zaraz/advanced/import-export.mdx
index 450eddcbc977e9a..578d82719d2e9dc 100644
--- a/src/content/docs/zaraz/advanced/import-export.mdx
+++ b/src/content/docs/zaraz/advanced/import-export.mdx
@@ -6,7 +6,6 @@ products:
 title: Configuration Import & Export
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To export your Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Advanced**.
 3. Click "Export" to download your configuration.
 
@@ -27,16 +27,15 @@ To export your Zaraz configuration:
 
 :::caution
 
-
 Importing a Zaraz configuration replaces your existing configuration, meaning that any information you did not back up could be lost. Consider exporting your existing configuration before importing a new one.
 
-
 :::
 
 To import a Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Advanced**.
 3. Click **Browse** to select your configuration file, and **Import** to import it.
diff --git a/src/content/docs/zaraz/advanced/index.mdx b/src/content/docs/zaraz/advanced/index.mdx
index 9b8a538527e1ac3..1b0c3fd82039d96 100644
--- a/src/content/docs/zaraz/advanced/index.mdx
+++ b/src/content/docs/zaraz/advanced/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Advanced options
 sidebar:
   order: 7
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
index 7e825c97731546d..568da28f0043abf 100644
--- a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
+++ b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
@@ -60,7 +60,8 @@ As with regular tools, it is recommended that you [create the triggers](/zaraz/c
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > [**Third-party tools**](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/tools-config/tools/catalog).
 3. Select **Add new tool** and choose **Custom Managed Component** from the tools library page. Select **Continue** to confirm your selection.
 4. In **Select Custom MC**, choose a Custom Managed Component that you have deployed to your account, such as `custom-mc-my-new-counter-mc`. Select **Continue**.
diff --git a/src/content/docs/zaraz/advanced/load-selectively.mdx b/src/content/docs/zaraz/advanced/load-selectively.mdx
index f9384c91755a2cc..1d02673007eda4d 100644
--- a/src/content/docs/zaraz/advanced/load-selectively.mdx
+++ b/src/content/docs/zaraz/advanced/load-selectively.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Zaraz selectively
 sidebar:
   order: 1
-
 ---
 
 You can use [Configuration Rules](/rules/configuration-rules/) to load Zaraz selectively on specific URLs or subdomains. Configuration Rules can also be used to block Zaraz from loading based on cookies, IP addresses or anything else related to a request.
@@ -15,8 +14,6 @@ Refer to [Configuration Rules](/rules/configuration-rules/) documentation to lea
 
 :::note
 
-
 If you need to block one or more actions from firing in a tool, Cloudflare recommends you use [Blocking Triggers](/zaraz/advanced/blocking-triggers/) instead of Configuration Rules.
 
-
 :::
diff --git a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
index d8ca835447f24d1..ce72a802d046457 100644
--- a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
+++ b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Zaraz manually
 sidebar:
   order: 5
-
 ---
 
 By default, if your domain is proxied by Cloudflare, Zaraz will automatically inject itself to HTML pages in your site. This makes it easier to get up and running quickly. However, you might want to load Zaraz manually, for example to test Zaraz on specific pages first.
@@ -21,13 +20,13 @@ With the script, your page HTML should be similar to the following:
 
 ```html
 <html>
-  <head>
-    ….
-    <script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
-  </head>
-  <body>
-    …
-  </body>
+	<head>
+		….
+		<script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
+	</head>
+	<body>
+		…
+	</body>
 </html>
 ```
 
diff --git a/src/content/docs/zaraz/advanced/using-jsonata.mdx b/src/content/docs/zaraz/advanced/using-jsonata.mdx
index 925c0718866321c..82292524bfe52e4 100644
--- a/src/content/docs/zaraz/advanced/using-jsonata.mdx
+++ b/src/content/docs/zaraz/advanced/using-jsonata.mdx
@@ -6,7 +6,6 @@ products:
 title: Using JSONata
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To use JSONata inside Zaraz, follow these steps:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Tools configuration** > **Tools**.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -38,23 +38,22 @@ Converting a string to lowercase is useful if you want to compare it to somethin
 Assuming you are using `zaraz.ecommerce()` to send the cart content like this:
 
 ```js
-zaraz.track('Product List Viewed',
-  {  products:
-    [
-    {
-      sku: '2671033',
-      name: 'V-neck T-shirt',
-      price: 14.99,
-      quantity: 3
-    },{
-      sku: '2671034',
-      name: 'T-shirt',
-      price: 10.99,
-      quantity: 2
-    },
-    ],
-  }
-);
+zaraz.track("Product List Viewed", {
+	products: [
+		{
+			sku: "2671033",
+			name: "V-neck T-shirt",
+			price: 14.99,
+			quantity: 3,
+		},
+		{
+			sku: "2671034",
+			name: "T-shirt",
+			price: 10.99,
+			quantity: 2,
+		},
+	],
+});
 ```
 
 If the field in which you want to show the sum, you will enter `{{ $sum(client.products.(price * quantity)) }}`. This will multiply the price of each product by its quantity, and then sum up the total.
diff --git a/src/content/docs/zaraz/consent-management/api.mdx b/src/content/docs/zaraz/consent-management/api.mdx
index b6feadf8eef42a1..cfbaa929889d835 100644
--- a/src/content/docs/zaraz/consent-management/api.mdx
+++ b/src/content/docs/zaraz/consent-management/api.mdx
@@ -6,7 +6,6 @@ products:
 title: Consent API
 sidebar:
   order: 3
-
 ---
 
 ## Background
@@ -15,7 +14,7 @@ The Consent API allows you to programmatically control all aspects of the Consen
 
 Using the Consent API, you can integrate Zaraz Consent preferences with an external Consent Management Platform, customize your consent modal, or restrict consent management to users in specific regions.
 
-***
+---
 
 ## Events
 
@@ -25,9 +24,8 @@ It can be useful to know when the Consent API is fully loaded on the page so tha
 
 ```js
 document.addEventListener("zarazConsentAPIReady", () => {
-  // do things with the Consent API
+	// do things with the Consent API
 });
-
 ```
 
 ### `Consent Choices Updated`
@@ -36,34 +34,26 @@ This event is fired every time the user makes changes to their consent preferenc
 
 ```js
 document.addEventListener("zarazConsentChoicesUpdated", () => {
-  // read the new consent preferences using `zaraz.consent.getAll();` and do things with it
+	// read the new consent preferences using `zaraz.consent.getAll();` and do things with it
 });
-
 ```
 
-***
+---
 
 ## Properties
 
 The following are properties of the `zaraz.consent` object.
 
+- `modal` boolean
+  - Get or set the current visibility status of the consent modal dialog.
 
+- `purposes` object read-only
+  - An object containing all configured purposes, with their ID, name, description, and order.
 
-* `modal` boolean
-
-  * Get or set the current visibility status of the consent modal dialog.
-
-* `purposes` object read-only
-
-  * An object containing all configured purposes, with their ID, name, description, and order.
-
-* `APIReady` boolean read-only
+- `APIReady` boolean read-only
+  - Indicates whether the Consent API is currently available on the page.
 
-  * Indicates whether the Consent API is currently available on the page.
-
-
-
-***
+---
 
 ## Methods
 
@@ -73,27 +63,18 @@ The following are properties of the `zaraz.consent` object.
 zaraz.consent.get(purposeId);
 ```
 
-
-
-* <code>get(purposeId)</code> : `boolean | undefined`
-
-
+- <code>get(purposeId)</code> : `boolean | undefined`
 
 Get the current consent status for a purpose using the purpose ID.
 
-* `true`: The consent was granted.
-* `false`: The consent was not granted.
-* `undefined`: The purpose does not exist.
+- `true`: The consent was granted.
+- `false`: The consent was not granted.
+- `undefined`: The purpose does not exist.
 
 #### Parameters
 
-
-
-* `purposeId` string
-
-  * The ID representing the Purpose.
-
-
+- `purposeId` string
+  - The ID representing the Purpose.
 
 ### `Set`
 
@@ -101,23 +82,14 @@ Get the current consent status for a purpose using the purpose ID.
 zaraz.consent.set(consentPreferences);
 ```
 
-
-
-* <code>set(consentPreferences)</code> : `undefined`
-
-
+- <code>set(consentPreferences)</code> : `undefined`
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-
-
-* `consentPreferences` object
-
-  * a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
-
-
+- `consentPreferences` object
+  - a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
 
 ### `Get All`
 
@@ -125,11 +97,7 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.getAll();
 ```
 
-
-
-* <code>getAll()</code> : `{ purposeId: boolean }`
-
-
+- <code>getAll()</code> : `{ purposeId: boolean }`
 
 Returns an object with the consent status of all purposes.
 
@@ -139,23 +107,14 @@ Returns an object with the consent status of all purposes.
 zaraz.consent.setAll(consentStatus);
 ```
 
-
-
-* <code>setAll(consentStatus)</code> : `undefined`
-
-
+- <code>setAll(consentStatus)</code> : `undefined`
 
 Set the consent status for all purposes at once.
 
 #### Parameters
 
-
-
-* `consentStatus` boolean
-
-  * Indicates whether the consent was granted or not.
-
-
+- `consentStatus` boolean
+  - Indicates whether the consent was granted or not.
 
 ### `Get All Checkboxes`
 
@@ -163,11 +122,7 @@ Set the consent status for all purposes at once.
 zaraz.consent.getAllCheckboxes();
 ```
 
-
-
-* <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
-
-
+- <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
 
 Returns an object with the checkbox status of all purposes.
 
@@ -177,23 +132,14 @@ Returns an object with the checkbox status of all purposes.
 zaraz.consent.setCheckboxes(checkboxesStatus);
 ```
 
-
-
-* <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
-
-
+- <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-
-
-* `checkboxesStatus` object
-
-  * a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
-
-
+- `checkboxesStatus` object
+  - a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
 
 ### `Set All Checkboxes`
 
@@ -201,23 +147,14 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.setAllCheckboxes(checkboxStatus);
 ```
 
-
-
-* <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
-
-
+- <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
 
 Set the `checkboxStatus` status for all purposes in the consent modal at once.
 
 #### Parameters
 
-
-
-* `checkboxStatus` boolean
-
-  * Indicates whether the purposes should be marked as checked or not.
-
-
+- `checkboxStatus` boolean
+  - Indicates whether the purposes should be marked as checked or not.
 
 ### `Send queued events`
 
@@ -225,11 +162,7 @@ Set the `checkboxStatus` status for all purposes in the consent modal at once.
 zaraz.consent.sendQueuedEvents();
 ```
 
-
-
-* <code>sendQueuedEvents()</code> : `undefined`
-
-
+- <code>sendQueuedEvents()</code> : `undefined`
 
 If some Pageview-based events were not sent due to a lack of consent, they can be sent using this method after consent was granted.
 
@@ -241,32 +174,35 @@ You can combine multiple features of Zaraz to effectively disable Consent Manage
 
 ```html
 <script>
-function getCookie(name) {
-  const value = `; ${document.cookie}`
-  return value?.split(`; ${name}=`)[1]?.split(";")[0]
-}
-
-function handleZarazConsentAPIReady() {
-  const consent_cookie = getCookie("cf_consent")
-  const isEUCountry = "{{system.device.location.isEUCountry}}" === "1"
-  if (!consent_cookie) {
-    if (isEUCountry) {
-      zaraz.consent.modal = true
-    } else {
-      zaraz.consent.setAll(true)
-      zaraz.consent.sendQueuedEvents()
-    }
-  }
-}
-
-if (zaraz.consent?.APIReady) {
-  handleZarazConsentAPIReady()
-} else {
-  document.addEventListener("zarazConsentAPIReady", handleZarazConsentAPIReady)
-}
+	function getCookie(name) {
+		const value = `; ${document.cookie}`;
+		return value?.split(`; ${name}=`)[1]?.split(";")[0];
+	}
+
+	function handleZarazConsentAPIReady() {
+		const consent_cookie = getCookie("cf_consent");
+		const isEUCountry = "{{system.device.location.isEUCountry}}" === "1";
+		if (!consent_cookie) {
+			if (isEUCountry) {
+				zaraz.consent.modal = true;
+			} else {
+				zaraz.consent.setAll(true);
+				zaraz.consent.sendQueuedEvents();
+			}
+		}
+	}
+
+	if (zaraz.consent?.APIReady) {
+		handleZarazConsentAPIReady();
+	} else {
+		document.addEventListener(
+			"zarazConsentAPIReady",
+			handleZarazConsentAPIReady,
+		);
+	}
 </script>
 ```
 
-Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf\_consent"  in the snippet above.
+Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf_consent" in the snippet above.
 
 By letting this Custom HTML tool to run without consent requirements, the modal will appear to all EU visitors, while for other visitors consent will be automatically granted. The `{{ system.device.location.isEUCountry }}` property will be `1` if the visitor is from an EU country and `0` otherwise. You can use any other property or variable to customize the Consent Management behavior in a similar manner, such as `{{ system.device.location.country }}` to restrict consent checks based on country code.
diff --git a/src/content/docs/zaraz/consent-management/custom-css.mdx b/src/content/docs/zaraz/consent-management/custom-css.mdx
index 719f2839cf27872..7827dbae8fb4745 100644
--- a/src/content/docs/zaraz/consent-management/custom-css.mdx
+++ b/src/content/docs/zaraz/consent-management/custom-css.mdx
@@ -6,7 +6,6 @@ products:
 title: Custom CSS
 sidebar:
   order: 2
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,5 +14,6 @@ You can add custom CSS to the Zaraz Consent Management Platform, to make the con
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Find the **Custom CSS** section, and add your custom CSS code as you would on any other HTML editor.
diff --git a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
index 39e50481db06ef5..1a442cb85828653 100644
--- a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
+++ b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable the Consent Management platform (CMP)
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Turn on **Enable Consent Management**.
 3. In **Consent modal text** fill in any legal information required in your country. Use HTML code to format your information as you would in any other HTML editor.
 4. Under **Purposes**, select **Add new Purpose**. Give your new purpose a name and a description. Purposes are the reasons for using third-party tools in your website.
@@ -31,7 +31,8 @@ In your Zaraz consent settings, you can add your consent modal text and purposes
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Select a default language of your choice. The default setting is English.
 3. In **Consent modal text** and **Purposes**, you can select different languages and add translations.
 
@@ -44,7 +45,7 @@ Below is an example that forces the language shown to be American English.
 
 ```html
 <script>
-  zaraz.set('__zarazConsentLanguage', 'en-US')
+	zaraz.set("__zarazConsentLanguage", "en-US");
 </script>
 ```
 
diff --git a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
index 0ab62c99c732fa1..57e58eba4bb79c1 100644
--- a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
+++ b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: IAB Transparency & Consent Framework Compliance
-
 ---
 
 import { DashButton } from "~/components";
@@ -22,7 +21,8 @@ Using the Zaraz Consent Management Platform in IAB TCF Compliance Mode is is opt
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Check the **Use IAB TCF compliant modal** option.
 3. Under the **Assign purposes to tools** section, add vendor details to every tool that was not automatically assigned.
 4. Press **Save**.
diff --git a/src/content/docs/zaraz/consent-management/index.mdx b/src/content/docs/zaraz/consent-management/index.mdx
index 57e7e5e3a28277f..577214eacbb7f26 100644
--- a/src/content/docs/zaraz/consent-management/index.mdx
+++ b/src/content/docs/zaraz/consent-management/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Zaraz Consent Management platform
-
 ---
 
-Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219\&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
+Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
 
 The consent modal added to your website is concise and gives your users an easy way to opt-in to any purposes of data processing your tools need.
 
@@ -22,12 +21,12 @@ The consent modal added to your website is concise and gives your users an easy
 
 The Zaraz Consent Management platform (CMP) has a **Purposes** section. This is where you will have to create purposes for the third-party tools your website uses. To better understand the terms involved in dealing with personal data, refer to these definitions:
 
-* **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
-* **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
+- **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
+- **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
 
 :::note
 
-All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in. 
+All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in.
 :::
 
 ## Purposes and tools
@@ -36,19 +35,19 @@ When you add a new tool to your website, Zaraz does not assign any purpose to it
 
 The user’s consent preferences are stored within a first-party cookie. This cookie is a JSON file that maps the purposes’ ID to a `true`/`false`/missing value:
 
-* `true` value: The user gave consent.
-* `false`value: The user refused consent.
-* Missing value: The user has not made a choice yet.
+- `true` value: The user gave consent.
+- `false`value: The user refused consent.
+- Missing value: The user has not made a choice yet.
 
 :::caution[Important]
 
-Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR. 
+Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR.
 :::
 
 ## Important things to note
 
-* Purposes that have no tools assigned will not show up in the CMP modal.
-* If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
-* Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
-* If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
-* On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
+- Purposes that have no tools assigned will not show up in the CMP modal.
+- If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
+- Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
+- If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
+- On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
diff --git a/src/content/docs/zaraz/custom-actions/additional-fields.mdx b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
index 76436e214d13c6c..f0bf936140a3a71 100644
--- a/src/content/docs/zaraz/custom-actions/additional-fields.mdx
+++ b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
@@ -6,7 +6,6 @@ products:
 title: Additional fields
 sidebar:
   order: 5
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ Adding an additional field to an action will attach it to this action only, and
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool with the action you want to add the additional field to, and select **Edit**.
 4. Select the action you wish to modify.
@@ -36,7 +36,8 @@ Adding an additional field to the tool sets it as a default field for all of the
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool where you want to add the field, and select **Edit**.
 4. Select **Settings** > **Add Field**.
diff --git a/src/content/docs/zaraz/custom-actions/create-action.mdx b/src/content/docs/zaraz/custom-actions/create-action.mdx
index 7d01b943b05425e..fbb05627895c834 100644
--- a/src/content/docs/zaraz/custom-actions/create-action.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-action.mdx
@@ -16,7 +16,8 @@ To create an action, first [add a third-party tool](/zaraz/get-started/). If you
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate the tool you want to configure an action for, and select **Edit**.
 4. Under Custom actions select **Create action**.
diff --git a/src/content/docs/zaraz/custom-actions/create-trigger.mdx b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
index 7d7d8c141b3ade7..200485ee7f7263e 100644
--- a/src/content/docs/zaraz/custom-actions/create-trigger.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
@@ -14,7 +14,8 @@ Triggers define the conditions under which a tool will start an action. Since a
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Select the **Triggers** tab.
 4. Select **Create trigger**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
index 38a7dae5ee8f9a5..8e83ceeaf6c5a71 100644
--- a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
@@ -6,14 +6,14 @@ products:
 title: Edit tools and actions
 sidebar:
   order: 6
-
 ---
-import { DashButton } from "~/components";
 
+import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools**.
 3. Under **Third-party tools**, locate your tool and select **Edit**.
 
@@ -23,7 +23,8 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select the **Enabled** toggle.
 
@@ -31,7 +32,8 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate the tool you wan to edit and select **Edit**.
 4. Find the action you want to change state, and enable or disable it with the toggle.
@@ -40,6 +42,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select **Delete**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
index 2e9e13f08691d48..23abf7eee383799 100644
--- a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a trigger
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Edit**.
 
@@ -26,6 +26,7 @@ You can edit every field related to the trigger, as well as add new trigger rule
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Delete**.
diff --git a/src/content/docs/zaraz/embeds.mdx b/src/content/docs/zaraz/embeds.mdx
index d2a6e58612bd5d4..72ce24521d03833 100644
--- a/src/content/docs/zaraz/embeds.mdx
+++ b/src/content/docs/zaraz/embeds.mdx
@@ -6,7 +6,6 @@ products:
 title: Embeds
 sidebar:
   order: 6
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To add an Embed to Your Website:
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Click "add new tool" and activate the desired tools on your Cloudflare Zaraz dashboard.
 4. Add a placeholder in your HTML, specifying the necessary attributes. For a generic embed, the snippet looks like this:
@@ -43,7 +43,10 @@ Replace `tweet-id` with the actual tweet ID for the content you wish to embed.
 ### Instagram embed
 
 ```html
-<instagram-post post-url="https://www.instagram.com/p/ABC/" captions="true"></instagram-post>
+<instagram-post
+	post-url="https://www.instagram.com/p/ABC/"
+	captions="true"
+></instagram-post>
 ```
 
 Replace `post-url` with the actual URL for the content you wish to embed. To include posts captions set captions attribute to `true`.
diff --git a/src/content/docs/zaraz/get-started.mdx b/src/content/docs/zaraz/get-started.mdx
index 682f7f02cc686a6..69973cb72ac66dc 100644
--- a/src/content/docs/zaraz/get-started.mdx
+++ b/src/content/docs/zaraz/get-started.mdx
@@ -18,7 +18,8 @@ You can add new third-party tools and load them into your website through the Cl
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. If you have already added a tool before, select **Third-party tools** and click on **Add new tool**.
 3. Choose a tool from the tools catalog. Select **Continue** to confirm your selection.
 4. In **Set up**, configure the settings for your new tool. The information you need to enter will depend on the tool you choose. If you want to use any dynamic properties or variables, select the `+` sign in the drop-down menu next to the relevant field.
diff --git a/src/content/docs/zaraz/history/index.mdx b/src/content/docs/zaraz/history/index.mdx
index a86038b87af35fc..98f0e09c733046c 100644
--- a/src/content/docs/zaraz/history/index.mdx
+++ b/src/content/docs/zaraz/history/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Versions & History
 sidebar:
   order: 8
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Zaraz can work in real-time. In this mode, every change you make is instantly published. You can also enable [Preview & Publish mode](/zaraz/history/preview-mode/), which allows you to test your changes before you commit to them.
 
diff --git a/src/content/docs/zaraz/history/versions.mdx b/src/content/docs/zaraz/history/versions.mdx
index 0ee58afc9464854..d5c71f8201e3f9d 100644
--- a/src/content/docs/zaraz/history/versions.mdx
+++ b/src/content/docs/zaraz/history/versions.mdx
@@ -6,12 +6,10 @@ products:
 title: Versions
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
 
-
 Version History enables you to keep track of all the Zaraz configuration changes made in your website. With Version History you can also revert changes to previous settings should there be a problem.
 
 To access Version History you need to enable [Preview & Publish mode](/zaraz/history/preview-mode/) first. Then, you can access Version History under **Zaraz** > **History**.
@@ -20,11 +18,12 @@ To access Version History you need to enable [Preview & Publish mode](/zaraz/his
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-	<DashButton url="/?to=/:account/tag-management/history" />
-3. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
-   * Date of change
-   * User who made the change
-   * Description of the change
+   <DashButton url="/?to=/:account/tag-management/history" />
+
+2. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
+   - Date of change
+   - User who made the change
+   - Description of the change
 
 ## Revert changes
 
@@ -32,7 +31,8 @@ Version History enables you to revert any changes made to your Zaraz settings.
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-	<DashButton url="/?to=/:account/tag-management/history" />
+   <DashButton url="/?to=/:account/tag-management/history" />
+
 2. Find the changes you want to revert, and select **Restore**.
 3. Confirm you want to revert your changes.
 4. Select **Publish** to publish your changes.
diff --git a/src/content/docs/zaraz/http-events-api.mdx b/src/content/docs/zaraz/http-events-api.mdx
index 657a00899b82342..a4e94957e49f0cd 100644
--- a/src/content/docs/zaraz/http-events-api.mdx
+++ b/src/content/docs/zaraz/http-events-api.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: HTTP Events API
-
 ---
 
 import { DashButton } from "~/components";
@@ -24,7 +23,8 @@ To enable the API endpoint:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Under **Endpoints** > **HTTP Events API**, set your desired path. Remember the path is relative to your domain, and it must start with a `/`.
 
 :::caution[Important]
@@ -37,25 +37,25 @@ The endpoint you have configured for the API will receive `POST` requests with a
 
 ```json
 {
-  "events": [
-    {
-      "client": {
-        "__zarazTrack": "transaction successful",
-        "value": "200"
-      }
-    }
-  ]
+	"events": [
+		{
+			"client": {
+				"__zarazTrack": "transaction successful",
+				"value": "200"
+			}
+		}
+	]
 }
 ```
 
 The payload must contain an `events` array. Each Event Object in this array corresponds to one event you want Zaraz to process. The above example is similar to calling `zaraz.track('transaction successful', { value: "200" })` using the Web API.
 
-The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a *Track Property* in the Zaraz dashboard.
+The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a _Track Property_ in the Zaraz dashboard.
 
 There are two reserved keys:
 
-* `__zarazTrack`: The value of this key will be available as *Event Name*. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
-* `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
+- `__zarazTrack`: The value of this key will be available as _Event Name_. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
+- `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
 
 ### The `system` key
 
@@ -65,41 +65,41 @@ The same payload from before will resemble the following example, when we add th
 
 ```json
 {
-  "events": [
-    {
-      "client": {
-        "__zarazTrack": "transaction successful",
-        "value": "200"
-      },
-      "system": {
-        "page": {
-          "url": "https://example.com",
-          "title": "My website"
-        },
-        "device": {
-          "language": "en-US",
-          "ip": "192.168.0.1"
-        }
-      }
-    }
-  ]
+	"events": [
+		{
+			"client": {
+				"__zarazTrack": "transaction successful",
+				"value": "200"
+			},
+			"system": {
+				"page": {
+					"url": "https://example.com",
+					"title": "My website"
+				},
+				"device": {
+					"language": "en-US",
+					"ip": "192.168.0.1"
+				}
+			}
+		}
+	]
 }
 ```
 
 For all available system keys, refer to the table below:
 
-| Property                   | Type  | Description                                                                                |
-| -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------ |
-| `system.cookies`           | Object                         | A key-value object holding cookies from the device associated with the event.              |
-| `system.device.ip`         | String                         | The IP address of the device associated with the event.                                    |
-| `system.device.resolution` | String                         | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
-| `system.device.viewport`   | String                         | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
-| `system.device.language`   | String                         | The language code used by the device associated with the event.                            |
-| `system.device.user-agent` | String                         | The `User-Agent` string of the device associated with the event.                           |
-| `system.page.title`        | String                         | The title of the page associated with the event.                                           |
-| `system.page.url`          | String                         | The URL of the page associated with the event.                                             |
-| `system.page.referrer`     | String                         | The URL of the referrer page in the time the event took place.                             |
-| `system.page.encoding`     | String                         | The encoding of the page associated with the event.                                        |
+| Property                   | Type   | Description                                                                                |
+| -------------------------- | ------ | ------------------------------------------------------------------------------------------ |
+| `system.cookies`           | Object | A key-value object holding cookies from the device associated with the event.              |
+| `system.device.ip`         | String | The IP address of the device associated with the event.                                    |
+| `system.device.resolution` | String | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
+| `system.device.viewport`   | String | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
+| `system.device.language`   | String | The language code used by the device associated with the event.                            |
+| `system.device.user-agent` | String | The `User-Agent` string of the device associated with the event.                           |
+| `system.page.title`        | String | The title of the page associated with the event.                                           |
+| `system.page.url`          | String | The URL of the page associated with the event.                                             |
+| `system.page.referrer`     | String | The URL of the referrer page in the time the event took place.                             |
+| `system.page.encoding`     | String | The encoding of the page associated with the event.                                        |
 
 :::note
 
@@ -112,11 +112,11 @@ For each Event Object in your payload, Zaraz will respond with a Result Object.
 
 Depending on what tools you are loading using Zaraz, the body of the response coming from the API might include information you will want to process. This is because some tools do not have a complete server-side implementation and still depend on cookies, client-side JavaScript or similar mechanisms. Each Result Object can include the following information:
 
-| Result key | Description |
-| --- | --- |
-| `fetch` | Fetch requests that tools want to send from the user browser. |
-| `execute` | JavaScript code that tools want to execute in the user browser. |
-| `return` | Information that tools return. |
-| `cookies` | Cookies that tools want to set for the user. |
+| Result key | Description                                                     |
+| ---------- | --------------------------------------------------------------- |
+| `fetch`    | Fetch requests that tools want to send from the user browser.   |
+| `execute`  | JavaScript code that tools want to execute in the user browser. |
+| `return`   | Information that tools return.                                  |
+| `cookies`  | Cookies that tools want to set for the user.                    |
 
 You do not have to process the information above, but some tools might depend on this to work properly. You can start using the HTTP Events API without processing the information in the table above, and adjust accordingly later.
diff --git a/src/content/docs/zaraz/monitoring/index.mdx b/src/content/docs/zaraz/monitoring/index.mdx
index 7d60ca7c1291ea9..89a3c69828ab590 100644
--- a/src/content/docs/zaraz/monitoring/index.mdx
+++ b/src/content/docs/zaraz/monitoring/index.mdx
@@ -18,8 +18,9 @@ To use Zaraz Monitoring:
 
 1. In the Cloudflare dashboard, go to the **Monitoring** page.
 
-	<DashButton url="/?to=/:account/tag-management/monitoring" />
-3. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
+   <DashButton url="/?to=/:account/tag-management/monitoring" />
+
+2. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
 
 ## Zaraz Monitoring options
 
diff --git a/src/content/docs/zaraz/pricing-info.mdx b/src/content/docs/zaraz/pricing-info.mdx
index dca9b6076413d78..1ca41a948098035 100644
--- a/src/content/docs/zaraz/pricing-info.mdx
+++ b/src/content/docs/zaraz/pricing-info.mdx
@@ -6,7 +6,6 @@ products:
 title: Pricing
 sidebar:
   order: 15
-
 ---
 
 import { DashButton } from "~/components";
@@ -18,13 +17,15 @@ All Zaraz features and tools are always available on all accounts. Learn more ab
 ## The Zaraz Event unit
 
 One Zaraz Event is an event you are sending to Zaraz, whether that is a page view, a `zaraz.track` event, or similar. You can easily see the total number of Zaraz Events you are currently using on the **Monitoring** page of the Cloudflare dashboard:
-   <DashButton url="/?to=/:account/tag-management/monitoring" />
+
+<DashButton url="/?to=/:account/tag-management/monitoring" />
 
 ## Enabling Zaraz Paid
 
 1. In the Cloudflare dashboard, go to the **Zaraz plans** page.
 
-	<DashButton url="/?to=/:account/tag-management/plans" />
+   <DashButton url="/?to=/:account/tag-management/plans" />
+
 2. Click the **Enable Zaraz usage billing** button and follow the instructions.
 
 ## Using Zaraz Free
diff --git a/src/content/docs/zaraz/reference/context.mdx b/src/content/docs/zaraz/reference/context.mdx
index bda539074da4906..6f7df19926f9b1a 100644
--- a/src/content/docs/zaraz/reference/context.mdx
+++ b/src/content/docs/zaraz/reference/context.mdx
@@ -6,7 +6,6 @@ products:
 title: Zaraz Context
 sidebar:
   order: 10
-
 ---
 
 The Zaraz Context is a versatile object that provides a set of configurable properties for Zaraz, a web analytics tool for tracking user behavior on websites. These properties can be accessed and utilized across various components, including [Worker Variables](/zaraz/variables/worker-variables/) and [JSONata expressions](/zaraz/advanced/using-jsonata/).
@@ -17,8 +16,6 @@ System properties, which are automatically collected by Zaraz, provide insights
 
 ### Page information
 
-
-
 | Property               | Type   | Description                                                                                                     |
 | ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------- |
 | `system.page.query`    | Object | Key-Value object containing all query parameters in the current URL.                                            |
@@ -38,8 +35,6 @@ The keys inside the `system.cookies` are the cookies name. The property `system.
 
 ### Device information
 
-
-
 | Property                                   | Type   | Description                                                                                                              |
 | ------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------ |
 | `system.device.ip`                         | String | Visitor incoming IP address.                                                                                             |
@@ -76,8 +71,6 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ### Miscellaneous
 
-
-
 | Property                            | Type   | Description                           |
 | ----------------------------------- | ------ | ------------------------------------- |
 | `system.misc.random`                | Number | Random number unique to each request. |
@@ -87,8 +80,6 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ## Event properties
 
-
-
 | Property              | Type   | Description                                                                                                                                                                                                                                                          |
 | --------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `client.__zarazTrack` | String | Returns the name of the event sent using the Track method of the Web API. Refer to [Zaraz Track](/zaraz/web-api/track/) for more information.                                                                                                                        |
diff --git a/src/content/docs/zaraz/reference/index.mdx b/src/content/docs/zaraz/reference/index.mdx
index 3b3f9005d879c9c..11447093e6b50dc 100644
--- a/src/content/docs/zaraz/reference/index.mdx
+++ b/src/content/docs/zaraz/reference/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Reference
 sidebar:
   order: 9
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/reference/properties-reference.mdx b/src/content/docs/zaraz/reference/properties-reference.mdx
index a6ac0acf199d0b1..abecfe520bf0280 100644
--- a/src/content/docs/zaraz/reference/properties-reference.mdx
+++ b/src/content/docs/zaraz/reference/properties-reference.mdx
@@ -4,8 +4,8 @@ description: Built-in properties available in Zaraz events.
 products:
   - zaraz
 title: Properties reference
-
 ---
+
 import { DashButton } from "~/components";
 
 Cloudflare Zaraz offers properties that you can use when configuring the product. They are helpful to send data to a third-party tool or to create triggers as they have context about a specific user's browser session and the actions they take on the website. Below is a list of the properties you can access from the Cloudflare dashboard and their values.
@@ -14,69 +14,69 @@ Cloudflare Zaraz offers properties that you can use when configuring the product
 
 | Property               | Description                                                                                                                                                                                                                                          |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| *Event Name*           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
-| *Track Property name:* | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
+| _Event Name_           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
+| _Track Property name:_ | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
 
 ## Page Properties
 
 | Property                  | Description                                                                                                            |
 | ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| *Page character encoding* | Returns the document character encoding from `document.characterSet`.                                                  |
-| *Page referrer*           | Returns the page referrer from `document.referrer`.                                                                    |
-| *Page title*              | Returns the page title.                                                                                                |
-| *Query param name:*       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
-| *URL*                     | Returns a string containing the entire URL.                                                                            |
-| *URL base domain*         | Returns the base domain part of the URL, without any subdomains.                                                       |
-| *URL host*                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
-| *URL hostname*            | Returns the domain of the URL.                                                                                         |
-| *URL origin*              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
-| *URL password*            | Returns the password specified before the domain name.                                                                 |
-| *URL pathname*            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
-| *URL port*                | Returns the port number of the URL.                                                                                    |
-| *URL protocol scheme*     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
-| *URL query parameters*    | Returns query parameters provided, beginning with the leading `?` character.                                           |
-| *URL username*            | Returns the username specified before the domain name.                                                                 |
+| _Page character encoding_ | Returns the document character encoding from `document.characterSet`.                                                  |
+| _Page referrer_           | Returns the page referrer from `document.referrer`.                                                                    |
+| _Page title_              | Returns the page title.                                                                                                |
+| _Query param name:_       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
+| _URL_                     | Returns a string containing the entire URL.                                                                            |
+| _URL base domain_         | Returns the base domain part of the URL, without any subdomains.                                                       |
+| _URL host_                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
+| _URL hostname_            | Returns the domain of the URL.                                                                                         |
+| _URL origin_              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
+| _URL password_            | Returns the password specified before the domain name.                                                                 |
+| _URL pathname_            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
+| _URL port_                | Returns the port number of the URL.                                                                                    |
+| _URL protocol scheme_     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
+| _URL query parameters_    | Returns query parameters provided, beginning with the leading `?` character.                                           |
+| _URL username_            | Returns the username specified before the domain name.                                                                 |
 
 ## Cookies
 
 | Property       | Description                                           |
 | -------------- | ----------------------------------------------------- |
-| *Cookie name:* | Returns cookies obtained from the browser `document`. |
+| _Cookie name:_ | Returns cookies obtained from the browser `document`. |
 
 ## Device properties
 
 | Property                   | Description                                                 |
 | -------------------------- | ----------------------------------------------------------- |
-| *Browser engine*           | Returns the type of browser engine (for example, `WebKit`). |
-| *Browser engine version*   | Returns the version of the browser’s engine.                |
-| *Browser name*             | Returns the browser’s name.                                 |
-| *Browser version*          | Returns the browser’s version.                              |
-| *Device CPU*               | Returns the device’s CPU.                                   |
-| *Device IP address*        | Returns the incoming IP address.                            |
-| *Device language*          | Returns the language used.                                  |
-| *Device screen resolution* | Returns the screen resolution of the device.                |
-| *Device type*              | Returns the type of device used (for example, `iPhone`).    |
-| *Device viewport*          | Returns the visible web page area in user’s device.         |
-| *Operating system name*    | Returns the operating system.                               |
-| *Operating system version* | Returns the version of the operating system.                |
-| *User-agent string*        | Returns the browser’s user agent.                           |
+| _Browser engine_           | Returns the type of browser engine (for example, `WebKit`). |
+| _Browser engine version_   | Returns the version of the browser’s engine.                |
+| _Browser name_             | Returns the browser’s name.                                 |
+| _Browser version_          | Returns the browser’s version.                              |
+| _Device CPU_               | Returns the device’s CPU.                                   |
+| _Device IP address_        | Returns the incoming IP address.                            |
+| _Device language_          | Returns the language used.                                  |
+| _Device screen resolution_ | Returns the screen resolution of the device.                |
+| _Device type_              | Returns the type of device used (for example, `iPhone`).    |
+| _Device viewport_          | Returns the visible web page area in user’s device.         |
+| _Operating system name_    | Returns the operating system.                               |
+| _Operating system version_ | Returns the version of the operating system.                |
+| _User-agent string_        | Returns the browser’s user agent.                           |
 
 ## Device location
 
 | Property       | Description                                                                                                                                                                       |
 | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| *City*         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
-| *Continent*    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
-| *Country* code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
-| *EU* country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
-| *Region*       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
-| *Region* code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
-| *Timezone*     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
+| _City_         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
+| _Continent_    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
+| _Country_ code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
+| _EU_ country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
+| _Region_       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
+| _Region_ code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
+| _Timezone_     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
 
 ## Miscellaneous
 
 | Property                   | Description                                     |
 | -------------------------- | ----------------------------------------------- |
-| *Random number*            | Returns a random number unique to each request. |
-| *Timestamp (milliseconds)* | Returns the Unix time in milliseconds.          |
-| *Timestamp (seconds)*      | Returns the Unix time in seconds.               |
+| _Random number_            | Returns a random number unique to each request. |
+| _Timestamp (milliseconds)_ | Returns the Unix time in milliseconds.          |
+| _Timestamp (seconds)_      | Returns the Unix time in seconds.               |
diff --git a/src/content/docs/zaraz/reference/settings.mdx b/src/content/docs/zaraz/reference/settings.mdx
index 886095c024fe466..40f857c4d333de9 100644
--- a/src/content/docs/zaraz/reference/settings.mdx
+++ b/src/content/docs/zaraz/reference/settings.mdx
@@ -13,7 +13,7 @@ import { Plan, DashButton } from "~/components";
 
 To configure Zaraz's general settings, go to the **Settings** page in the Cloudflare dashboard:
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
+<DashButton url="/?to=/:account/tag-management/settings" />
 
 Make sure you save your changes, by selecting the **Save** button after making them.
 
@@ -45,15 +45,15 @@ When you toggle Single Page Application support off, the `pageview` trigger will
 
 Zaraz offers privacy settings you can configure, such as:
 
-* **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
+- **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
 
-* **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
+- **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
 
-* **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
+- **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
 
-* **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
+- **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
 
-* **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
+- **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
 
 ## Injection
 
@@ -93,9 +93,9 @@ Choose whether to prevent Zaraz from loading on suspected bot-initiated requests
 
 The options are:
 
-* **Block none**: Load Zaraz for all requests, even if those come from bots.
-* **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
-* **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
+- **Block none**: Load Zaraz for all requests, even if those come from bots.
+- **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
+- **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
 
 ### Context Enricher
 
diff --git a/src/content/docs/zaraz/reference/supported-tools.mdx b/src/content/docs/zaraz/reference/supported-tools.mdx
index 1b388c261cd4ea2..e20ce7495b724b0 100644
--- a/src/content/docs/zaraz/reference/supported-tools.mdx
+++ b/src/content/docs/zaraz/reference/supported-tools.mdx
@@ -7,7 +7,6 @@ title: Third-party tools
 head:
   - tag: title
     content: Supported tools
-
 ---
 
 Cloudflare Zaraz supports the following third-party tools:
diff --git a/src/content/docs/zaraz/variables/create-variables.mdx b/src/content/docs/zaraz/variables/create-variables.mdx
index 7e4f9894f49c848..cfce350ba75324b 100644
--- a/src/content/docs/zaraz/variables/create-variables.mdx
+++ b/src/content/docs/zaraz/variables/create-variables.mdx
@@ -20,7 +20,8 @@ For example, instead of typing a specific user ID in multiple fields, you can cr
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Variables**.
 3. Select **Create variable**, and give it a name.
 4. In **Variable type** select between `String`, `Masked variable` or `Worker` from the drop-down menu. Use `Masked variable` when you have a private value that you do not want to share, such as an API token.
diff --git a/src/content/docs/zaraz/variables/edit-variables.mdx b/src/content/docs/zaraz/variables/edit-variables.mdx
index 2225f830ff4de41..0c30678d2adc6e5 100644
--- a/src/content/docs/zaraz/variables/edit-variables.mdx
+++ b/src/content/docs/zaraz/variables/edit-variables.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a variable
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Variables**.
 3. Locate the variable you want to edit, and select **Edit** to make your changes.
 4. Select **Save** to save your edits.
@@ -29,7 +29,8 @@ You cannot delete a variable being used in tools or triggers.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate any tools using the variable, and delete the variable from those tools.
 4. Select **Zaraz** > **Tools Configuration** > **Triggers**.
diff --git a/src/content/docs/zaraz/variables/index.mdx b/src/content/docs/zaraz/variables/index.mdx
index 2201ce391be6a3a..98febbeb0a587f0 100644
--- a/src/content/docs/zaraz/variables/index.mdx
+++ b/src/content/docs/zaraz/variables/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Variables
 sidebar:
   order: 6
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/variables/worker-variables.mdx b/src/content/docs/zaraz/variables/worker-variables.mdx
index 3b80fe43170c522..57b8bfa416f7617 100644
--- a/src/content/docs/zaraz/variables/worker-variables.mdx
+++ b/src/content/docs/zaraz/variables/worker-variables.mdx
@@ -6,7 +6,6 @@ products:
 title: Worker Variables
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -25,7 +24,8 @@ To create a new Worker in the Cloudflare dashboard:
 
 1. In the Cloudflare dashboard, go to the **Workers and Pages** page.
 
-	<DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Give a name to your Worker and select **Deploy**.
 4. Select **Edit code**.
@@ -35,17 +35,17 @@ You have now created a basic Worker that responds with "Hello world." If you use
 Zaraz forwards the Zaraz Context object to your Worker as a JSON payload with a POST request. You can access any property like this:
 
 ```js
-const { system, client } = await request.json()
+const { system, client } = await request.json();
 
 /* System parameters */
-system.page.url.href // URL of the current page
-system.page.query.gclid // Value of the gclid query parameter
-system.device.resolution // Device screen resolution
-system.device.language // Browser preferred language
+system.page.url.href; // URL of the current page
+system.page.query.gclid; // Value of the gclid query parameter
+system.device.resolution; // Device screen resolution
+system.device.language; // Browser preferred language
 
 /* Zaraz Track values */
-client.value // value from `zaraz.track("foo", {value: "bar"})`
-client.products[0].name // name of the first product in an ecommerce call
+client.value; // value from `zaraz.track("foo", {value: "bar"})`
+client.products[0].name; // name of the first product in an ecommerce call
 ```
 
 Keep reading for more complete examples of different use cases or refer to [Zaraz Context](/zaraz/reference/context/).
@@ -56,7 +56,8 @@ Once your Worker is published, configuring a Worker Variable is easy.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select the domain for which you want to configure variables.
 3. Select the **Variables** tab.
 4. Select **Create variable**.
@@ -71,7 +72,8 @@ To use your Worker Variable:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select the domain for which you want to configure variables.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -86,11 +88,11 @@ Assuming we are sending a list of products in a cart, like this:
 
 ```js
 zaraz.ecommerce("Cart Viewed", {
-  products: [
-    { name: "shirt", price: "50" },
-    { name: "jacket", price: "20" },
-    { name: "hat", price: "30" },
-  ],
+	products: [
+		{ name: "shirt", price: "50" },
+		{ name: "jacket", price: "20" },
+		{ name: "hat", price: "30" },
+	],
 });
 ```
 
@@ -98,18 +100,18 @@ Calculating the sum can be done like this:
 
 ```js
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    // Get an array of all prices
-    const productsPrices = client.products.map((p) => p.price);
+		// Get an array of all prices
+		const productsPrices = client.products.map((p) => p.price);
 
-    // Calculate the sum
-    const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
+		// Calculate the sum
+		const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
 
-    return new Response(sum);
-  },
+		return new Response(sum);
+	},
 };
 ```
 
@@ -119,20 +121,20 @@ Zaraz exposes all cookies automatically under the `system.cookies` object, so th
 
 ```js
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    // Get the value of the cookie "login-cookie"
-    const cookieValue = system.cookies["login-cookie"];
+		// Get the value of the cookie "login-cookie"
+		const cookieValue = system.cookies["login-cookie"];
 
-    const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
-      method: POST,
-      body: cookieValue,
-    });
+		const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
+			method: POST,
+			body: cookieValue,
+		});
 
-    return new Response(userId);
-  },
+		return new Response(userId);
+	},
 };
 ```
 
@@ -148,23 +150,23 @@ You can access this property and hash it like this:
 
 ```js
 async function digestMessage(message) {
-  const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
-  const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
-  const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
-  const hashHex = hashArray
-    .map((b) => b.toString(16).padStart(2, "0"))
-    .join(""); // convert bytes to hex string
-  return hashHex;
+	const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
+	const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
+	const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
+	const hashHex = hashArray
+		.map((b) => b.toString(16).padStart(2, "0"))
+		.join(""); // convert bytes to hex string
+	return hashHex;
 }
 
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    const { email } = client;
+		const { email } = client;
 
-    return new Response(await digestMessage(email));
-  },
+		return new Response(await digestMessage(email));
+	},
 };
 ```
diff --git a/src/content/docs/zaraz/web-api/debug-mode.mdx b/src/content/docs/zaraz/web-api/debug-mode.mdx
index a2110d8626e7f2c..3e17a55399dfbf2 100644
--- a/src/content/docs/zaraz/web-api/debug-mode.mdx
+++ b/src/content/docs/zaraz/web-api/debug-mode.mdx
@@ -6,7 +6,6 @@ products:
 title: Debug mode
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
@@ -16,13 +15,14 @@ You can set this cookie manually or via the `zaraz.debug` helper function availa
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Copy your **Debug Key**.
 3. Open a web browser and access its Developer Tools. For example, to access Developer Tools in Google Chrome, select **View** > **Developer** > **Developer Tools**.
 4. Select the **Console** pane and enter the following command to create a debug cookie:
 
    ```js
-   zaraz.debug("YOUR_DEBUG_KEY")
+   zaraz.debug("YOUR_DEBUG_KEY");
    ```
 
 Zaraz’s debug mode is now enabled. A pop-up window will show up with the debugger information. To exit debug mode, remove the cookie by typing `zaraz.debug()` in the console pane of the browser.
diff --git a/src/content/docs/zaraz/web-api/ecommerce.mdx b/src/content/docs/zaraz/web-api/ecommerce.mdx
index 47b9b8b44b53c60..94708e09a23b5eb 100644
--- a/src/content/docs/zaraz/web-api/ecommerce.mdx
+++ b/src/content/docs/zaraz/web-api/ecommerce.mdx
@@ -31,7 +31,8 @@ You do not need to map e-commerce events to triggers. Zaraz automatically forwar
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Enable **E-commerce tracking**.
 3. Select **Save**.
 4. Go to **Zaraz** > **Tools Configuration** > **Third-party tools**.
diff --git a/src/content/docs/zaraz/web-api/index.mdx b/src/content/docs/zaraz/web-api/index.mdx
index 15b544bb65b4744..be94552a3782c97 100644
--- a/src/content/docs/zaraz/web-api/index.mdx
+++ b/src/content/docs/zaraz/web-api/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Web API
 sidebar:
   order: 3
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Zaraz provides a client-side web API that you can use anywhere inside the `<body>` tag of a page.
 
diff --git a/src/content/docs/zaraz/web-api/set.mdx b/src/content/docs/zaraz/web-api/set.mdx
index 0d9f29ac5943204..447578481222c7a 100644
--- a/src/content/docs/zaraz/web-api/set.mdx
+++ b/src/content/docs/zaraz/web-api/set.mdx
@@ -9,27 +9,26 @@ sidebar:
 head:
   - tag: title
     content: zaraz.set
-
 ---
 
 You can use `zaraz.set()` anywhere inside the `<body>` tag of a page:
 
 ```js
-zaraz.set(key, value, [options])
+zaraz.set(key, value, [options]);
 ```
 
 Set is useful if you want to make a variable available in all your events without manually setting it every time you are using `zaraz.track()`. For the purpose of this example, assume users in your system have a unique identifier that you want to send to your tools. You might have many `zaraz.track()` calls all sharing this one parameter:
 
 ```js
-zaraz.track("form completed", {userId: "ABC-123"})
+zaraz.track("form completed", { userId: "ABC-123" });
 ```
 
 ```js
-zaraz.track("button clicked", {userId: "ABC-123", value: 200})
+zaraz.track("button clicked", { userId: "ABC-123", value: 200 });
 ```
 
 ```js
-zaraz.track("cart viewed", {items: 3, userId: "ABC-123"})
+zaraz.track("cart viewed", { items: 3, userId: "ABC-123" });
 ```
 
 Here, all the events are collecting the `userId` key, and the code for setting that key repeats itself. With `zaraz.set()` you can avoid repetition by setting the key once when the page loads. Zaraz will then attach this key to all future `zaraz.track()` calls.
@@ -39,23 +38,23 @@ Using the above data as the example, if you use `zaraz.set("userId", "ABC-123")`
 Another example:
 
 ```js
-zaraz.set('product_name', 't-shirt', {scope: 'page'})
+zaraz.set("product_name", "t-shirt", { scope: "page" });
 ```
 
-Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable *Track Property name:*, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
+Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable _Track Property name:_, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
 
 ![Example of how to create a variable with the Set method, tracking t-shirts](~/assets/images/zaraz/set.png)
 
 The `[options]` argument is an optional object and can include a `scope` property that has a string value. This property determines the lifetime of this key, meaning for how long Zaraz should keep attaching it to `zaraz.track()` calls. Allowed values are:
 
-* `page`: To set the key for the context of the current page only.
-* `session`: To make the key last the whole session.
-* `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
+- `page`: To set the key for the context of the current page only.
+- `session`: To make the key last the whole session.
+- `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
 
 In the previous example, `{scope: 'page'}` makes the `product_name` property available to all `zaraz.track()` calls in the current page, but will not affect calls after visitors navigate to other pages.
 
 To unset a variable, set it to `undefined`. The variable will then be removed from all scopes it was included in, and will not be automatically sent with future `zaraz.track` calls. For example:
 
 ```js
-zaraz.set('product_name', undefined)
+zaraz.set("product_name", undefined);
 ```
diff --git a/src/content/partials/1.1.1.1/captive-portals.mdx b/src/content/partials/1.1.1.1/captive-portals.mdx
index 9a22c3361ba00f0..7d4223b076a5f3f 100644
--- a/src/content/partials/1.1.1.1/captive-portals.mdx
+++ b/src/content/partials/1.1.1.1/captive-portals.mdx
@@ -12,4 +12,4 @@ If you are experiencing connectivity issues related to captive portals:
 2. Connect to the Wi-Fi network.
 3. Once the connection has been established, re-add the static IP addresses or enable the 1.1.1.1 app.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/agents/unique-agents.mdx b/src/content/partials/agents/unique-agents.mdx
index d3f96c7f9fa15e9..bd157735e3ad07f 100644
--- a/src/content/partials/agents/unique-agents.mdx
+++ b/src/content/partials/agents/unique-agents.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
@@ -11,4 +10,4 @@ This allows you to avoid synchronizing state across requests: if an Agent instan
 
 If the client disconnects, you can always route the client back to the exact same Agent and pick up where they left off.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ai-crawl-control/plan-comparison.mdx b/src/content/partials/ai-crawl-control/plan-comparison.mdx
index f56f51d865fe7c5..a03e263b7030fed 100644
--- a/src/content/partials/ai-crawl-control/plan-comparison.mdx
+++ b/src/content/partials/ai-crawl-control/plan-comparison.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                       |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)           |
-| Maximum 24-hour analytics window                                                                                              |  Configurable analytics timeframes                                                                                                      |
-| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
\ No newline at end of file
+| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                               |
+| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)                   |
+| Maximum 24-hour analytics window                                                                                              | Configurable analytics timeframes                                                                                                                  |
+| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
diff --git a/src/content/partials/ai-gateway/analytics-dashboard.mdx b/src/content/partials/ai-gateway/analytics-dashboard.mdx
index 9c812ba529cb5bb..5dbb03ea869ad8b 100644
--- a/src/content/partials/ai-gateway/analytics-dashboard.mdx
+++ b/src/content/partials/ai-gateway/analytics-dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To view analytics in the dashboard:
diff --git a/src/content/partials/ai-gateway/logging.mdx b/src/content/partials/ai-gateway/logging.mdx
index ae7983b75652584..9522593e0222102 100644
--- a/src/content/partials/ai-gateway/logging.mdx
+++ b/src/content/partials/ai-gateway/logging.mdx
@@ -1,6 +1,7 @@
 ---
 {}
 ---
+
 import { DashButton } from "~/components";
 
 To change the default log configuration in the dashboard:
diff --git a/src/content/partials/ai-gateway/universal-gateway-example.mdx b/src/content/partials/ai-gateway/universal-gateway-example.mdx
index c0bbda990100faa..6950494e7677012 100644
--- a/src/content/partials/ai-gateway/universal-gateway-example.mdx
+++ b/src/content/partials/ai-gateway/universal-gateway-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```bash title="Request"
diff --git a/src/content/partials/ai-search/rest-api-auth.mdx b/src/content/partials/ai-search/rest-api-auth.mdx
index 84c53bc88b43199..afc3a5199d0f9b0 100644
--- a/src/content/partials/ai-search/rest-api-auth.mdx
+++ b/src/content/partials/ai-search/rest-api-auth.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 All requests require an API token with **AI Search:Edit** and **AI Search:Run** permissions.
 
diff --git a/src/content/partials/analytics/customer_metadata_boundary_error.mdx b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
index aa5a25eabdfe090..892e43f082a7c02 100644
--- a/src/content/partials/analytics/customer_metadata_boundary_error.mdx
+++ b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 If you encounter a message on the dashboard indicating that your data is unavailable due to your account's Metadata Boundary configuration, this is because you are trying to access data that is not stored in your region (that is, you are in the US and trying to access data that is only stored in the EU, or vice versa). If you receive this error message while being in the region where your data is stored, there are two potential reasons why you might get this message:
 
-* Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
+- Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
 
-* If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
+- If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
diff --git a/src/content/partials/analytics/network-analytics-requirements.mdx b/src/content/partials/analytics/network-analytics-requirements.mdx
index 972d6cea688b524..509b51ff43b0ffd 100644
--- a/src/content/partials/analytics/network-analytics-requirements.mdx
+++ b/src/content/partials/analytics/network-analytics-requirements.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 :::note[Requirements]
 
 Network Analytics requires the following:
 
-* A Cloudflare Enterprise plan.
-* Cloudflare Magic Transit or Spectrum.
-* Cloudflare WAN.
+- A Cloudflare Enterprise plan.
+- Cloudflare Magic Transit or Spectrum.
+- Cloudflare WAN.
   :::
diff --git a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
index d2dfe96892e93b6..bc1a23a14f531b7 100644
--- a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
+++ b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Network Analytics v1 (NAv1) is now deprecated.** For more information on Network Analytics v2 (NAv2), refer to [Cloudflare Network Analytics](/analytics/network-analytics/).
diff --git a/src/content/partials/api-shield/label-methodology.mdx b/src/content/partials/api-shield/label-methodology.mdx
index 72400e85c006187..96af54686fabef0 100644
--- a/src/content/partials/api-shield/label-methodology.mdx
+++ b/src/content/partials/api-shield/label-methodology.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-| 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. |
+| 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. |
diff --git a/src/content/partials/api-shield/mtls-api-shield-support.mdx b/src/content/partials/api-shield/mtls-api-shield-support.mdx
index 0224d99943797f8..1588524b353a3c5 100644
--- a/src/content/partials/api-shield/mtls-api-shield-support.mdx
+++ b/src/content/partials/api-shield/mtls-api-shield-support.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/api-shield/mtls-create-rule.mdx b/src/content/partials/api-shield/mtls-create-rule.mdx
index ac25847bffa79f2..8385e54de0b19d4 100644
--- a/src/content/partials/api-shield/mtls-create-rule.mdx
+++ b/src/content/partials/api-shield/mtls-create-rule.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 <Steps>
 1. In the Cloudflare dashboard, go to **Client Certificates** page.
@@ -16,4 +15,4 @@ import { Steps, DashButton } from "~/components"
 6. Select **Deploy** to make the rule active.
 </Steps>
 
-Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
\ No newline at end of file
+Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
diff --git a/src/content/partials/api-shield/rate-limit-user.mdx b/src/content/partials/api-shield/rate-limit-user.mdx
index 9cdc3591641dfcf..d47e2e46b45069e 100644
--- a/src/content/partials/api-shield/rate-limit-user.mdx
+++ b/src/content/partials/api-shield/rate-limit-user.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ### Rate limit by user (JWT claim)
diff --git a/src/content/partials/api-shield/required-session-identifiers.mdx b/src/content/partials/api-shield/required-session-identifiers.mdx
index a1f6276e094c00c..59e54427d1d871b 100644
--- a/src/content/partials/api-shield/required-session-identifiers.mdx
+++ b/src/content/partials/api-shield/required-session-identifiers.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You must have specific entitlements to configure session identifiers or cookies as a form of identifiers, such as an Enterprise subscription, for features such as [API Discovery](/api-shield/security/api-discovery/), [Sequence Mitigation](/api-shield/security/sequence-mitigation/) or [rate limiting recommendations](/api-shield/security/volumetric-abuse-detection/), and to see results in [Sequence Analytics](/api-shield/security/sequence-analytics/) and [Authentication Posture](/api-shield/security/authentication-posture/).
diff --git a/src/content/partials/api-shield/sequence-mitigation-availability.mdx b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
index 38bbe706bb998a3..94c7f150023934f 100644
--- a/src/content/partials/api-shield/sequence-mitigation-availability.mdx
+++ b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
\ No newline at end of file
+Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
diff --git a/src/content/partials/api-shield/session-identifiers.mdx b/src/content/partials/api-shield/session-identifiers.mdx
index 4e517b779b2b3a9..ef978913a8fe1cf 100644
--- a/src/content/partials/api-shield/session-identifiers.mdx
+++ b/src/content/partials/api-shield/session-identifiers.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 While not strictly required, it is recommended that you configure your <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> when getting started with API Shield. When Cloudflare inspects your API traffic for individual sessions, we can offer more tools for visibility, management, and control.
 
@@ -11,4 +10,4 @@ If you are unsure of the session identifiers that your API uses, consult with yo
 
 Session identifiers should uniquely identify API clients. A common session identifier for API traffic is the `Authorization` header. When a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) is used by the API for client authentication, its value may change over time. You can use a claim value inside the JWT such as `sub` or `email` as a session ID to uniquely identify the session over time.
 
-If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
\ No newline at end of file
+If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
diff --git a/src/content/partials/billing/two-payment-methods.mdx b/src/content/partials/billing/two-payment-methods.mdx
index fcd2e4ffca05097..9db0c042394f0a1 100644
--- a/src/content/partials/billing/two-payment-methods.mdx
+++ b/src/content/partials/billing/two-payment-methods.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/bots/about-plan-considerations.mdx b/src/content/partials/bots/about-plan-considerations.mdx
index 13c3ff7327eaed5..dbee048b258ff34 100644
--- a/src/content/partials/bots/about-plan-considerations.mdx
+++ b/src/content/partials/bots/about-plan-considerations.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 Bot Fight Mode and Super Bot Fight Mode use the same underlying technology that powers our [Bot Management](https://www.cloudflare.com/products/bot-management/) product. Specifically, these products:
 
-* Protect entire domains without endpoint restrictions
-* Cannot be customized, adjusted, or reconfigured via WAF custom rules
+- Protect entire domains without endpoint restrictions
+- Cannot be customized, adjusted, or reconfigured via WAF custom rules
 
 Although these products are designed to fight malicious actors on the Internet, they may challenge API or mobile app traffic. For more granular control, upgrade to [Bot Management for Enterprise](/bots/plans/bm-subscription/).
diff --git a/src/content/partials/bots/analytics-features.mdx b/src/content/partials/bots/analytics-features.mdx
index 8b21959f185efd0..5c8c8cc61b1b641 100644
--- a/src/content/partials/bots/analytics-features.mdx
+++ b/src/content/partials/bots/analytics-features.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare uses adaptive bitrate technology to show sampled data — most customers will see a 1-10% sample depending on how much information they are trying to view. Tooltips on the page will display the current sample rate.
diff --git a/src/content/partials/bots/bfm-change-notice.mdx b/src/content/partials/bots/bfm-change-notice.mdx
index d7474bab9acd502..e4fb1dd54926f1a 100644
--- a/src/content/partials/bots/bfm-change-notice.mdx
+++ b/src/content/partials/bots/bfm-change-notice.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Change notice for Super Bot Fight Mode rulesets]
diff --git a/src/content/partials/bots/bm-analytics-features.mdx b/src/content/partials/bots/bm-analytics-features.mdx
index 7dc1163ab88af8d..9af38b36aca085c 100644
--- a/src/content/partials/bots/bm-analytics-features.mdx
+++ b/src/content/partials/bots/bm-analytics-features.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 For a full tour of Bot Analytics, see [our blog post](https://blog.cloudflare.com/introducing-bot-analytics/). At a high level, the tool includes:
 
-* **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on *automated* and *likely automated* traffic.
-* **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
-* **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
-* **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
+- **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on _automated_ and _likely automated_ traffic.
+- **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
+- **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
+- **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
 
 Bot Analytics shows up to one week of data at a time and can display data up to 30 days old. Bot Analytics displays data in real time in most cases.
diff --git a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
index 792c3896e90dbdb..4a7b8ba166882b8 100644
--- a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
+++ b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
@@ -6,13 +6,13 @@
 
 The following features are handled automatically in **Security Settings** and do not require custom rules:
 
-| Feature | Handled by bot settings | Requires custom rules |
-| --- | --- | --- |
-| Block or challenge definitely automated traffic | Yes | Only for path-specific or threshold-tuned rules |
-| Block or challenge likely automated traffic | Not available on Pro | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
-| Allow or block verified bots | Yes | No |
-| Block AI crawlers | Yes | Only to target individual AI crawlers |
-| Protect static resources | Yes | No |
-| Optimize for WordPress | Yes | No |
+| Feature                                         | Handled by bot settings | Requires custom rules                                    |
+| ----------------------------------------------- | ----------------------- | -------------------------------------------------------- |
+| Block or challenge definitely automated traffic | Yes                     | Only for path-specific or threshold-tuned rules          |
+| Block or challenge likely automated traffic     | Not available on Pro    | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
+| Allow or block verified bots                    | Yes                     | No                                                       |
+| Block AI crawlers                               | Yes                     | Only to target individual AI crawlers                    |
+| Protect static resources                        | Yes                     | No                                                       |
+| Optimize for WordPress                          | Yes                     | No                                                       |
 
-For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
\ No newline at end of file
+For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
diff --git a/src/content/partials/bots/bots-ad.mdx b/src/content/partials/bots/bots-ad.mdx
index da728dfe8e0016d..f690a31c6f51ec3 100644
--- a/src/content/partials/bots/bots-ad.mdx
+++ b/src/content/partials/bots/bots-ad.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Deprecation notice]
diff --git a/src/content/partials/bots/bots-cookie.mdx b/src/content/partials/bots/bots-cookie.mdx
index 43bda678f796566..62c2872d9a483c0 100644
--- a/src/content/partials/bots/bots-cookie.mdx
+++ b/src/content/partials/bots/bots-cookie.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare uses the `__cf_bm` cookie to smooth out the <GlossaryTooltip term="bot score">bot score</GlossaryTooltip> and reduce false positives for actual user sessions.
 
diff --git a/src/content/partials/bots/bots-heuristics.mdx b/src/content/partials/bots/bots-heuristics.mdx
index 4cd143b9744bd18..be4df17066ad18c 100644
--- a/src/content/partials/bots/bots-heuristics.mdx
+++ b/src/content/partials/bots/bots-heuristics.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
\ No newline at end of file
+The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
diff --git a/src/content/partials/bots/bots-jsd.mdx b/src/content/partials/bots/bots-jsd.mdx
index 0db49de66e6f82f..7256269923ab642 100644
--- a/src/content/partials/bots/bots-jsd.mdx
+++ b/src/content/partials/bots/bots-jsd.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The [**JavaScript Detections (JSD)**](/bots/additional-configurations/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines.
diff --git a/src/content/partials/bots/bots-ml.mdx b/src/content/partials/bots/bots-ml.mdx
index df1136f568be04c..a14e20442d1ecca 100644
--- a/src/content/partials/bots/bots-ml.mdx
+++ b/src/content/partials/bots/bots-ml.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
 The **Machine Learning (ML)** engine accounts for the majority of all detections, distinguishing between human and bot traffic. This approach leverages our global network, which proxies billions of requests daily, to identify both automated and human traffic.
 
-The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99). 
+The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99).
 
 The core model relies on the following process:
 
 - Input Variables (X): Various request features (headers, session characteristics, and browser signals) collected from traffic across the Cloudflare network.
 - Output Variable (Y): The predicted probability that a client is human (such as the probability of successfully solving a Challenge). This probability is mapped to the final 1–99 Bot Score.
 
-We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
\ No newline at end of file
+We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
diff --git a/src/content/partials/bots/buttons-plan-pages.mdx b/src/content/partials/bots/buttons-plan-pages.mdx
index f4bb5390173d743..fcacd4331504ccc 100644
--- a/src/content/partials/bots/buttons-plan-pages.mdx
+++ b/src/content/partials/bots/buttons-plan-pages.mdx
@@ -1,8 +1,18 @@
 ---
 {}
-
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
- <LinkButton variant="primary" href="/bots/plans/free/">Free</LinkButton> <LinkButton variant="primary" href="/bots/plans/pro/">Pro</LinkButton> <LinkButton variant="primary" href="/bots/plans/biz-and-ent/">Business</LinkButton> <LinkButton variant="primary" href="/bots/plans/bm-subscription/">Bot Management for Enterprise</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/free/">
+	Free
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/pro/">
+	Pro
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/biz-and-ent/">
+	Business
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/bm-subscription/">
+	Bot Management for Enterprise
+</LinkButton>
diff --git a/src/content/partials/bots/content-security-policy-limitation.mdx b/src/content/partials/bots/content-security-policy-limitation.mdx
index f62345793fe5368..e42c9647319100a 100644
--- a/src/content/partials/bots/content-security-policy-limitation.mdx
+++ b/src/content/partials/bots/content-security-policy-limitation.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from '~/components';
+import { GlossaryTooltip } from "~/components";
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip>, you need to take additional steps to implement JavaScript Detections:
 
@@ -16,4 +15,4 @@ If you have a <GlossaryTooltip term="content security policy (CSP)">Content Secu
 :::caution[Warning]
 
 JavaScript Detections is not supported with `nonce` set via `<meta>` tags.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/bots/disable-cf-bm-cookie.mdx b/src/content/partials/bots/disable-cf-bm-cookie.mdx
index a19d23bd96c3778..3e1a4f6255413c8 100644
--- a/src/content/partials/bots/disable-cf-bm-cookie.mdx
+++ b/src/content/partials/bots/disable-cf-bm-cookie.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can disable the `__cf_bm` cookie using the `bm_cookie_enabled` field [via the API](/api/resources/bot_management/methods/update/).
diff --git a/src/content/partials/bots/endpoint-label-warning.mdx b/src/content/partials/bots/endpoint-label-warning.mdx
index 3e0748847f1cfbc..1d94ff8d3590322 100644
--- a/src/content/partials/bots/endpoint-label-warning.mdx
+++ b/src/content/partials/bots/endpoint-label-warning.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: endpoint
-
 ---
 
 :::caution[Login {props.one} endpoints]
-Not all login {props.one} endpoints are automatically detected. 
+Not all login {props.one} endpoints are automatically detected.
 
-Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized. 
+Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized.
 
 For example, if you have a non-traditional login endpoint, you should label it with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/). Once you have applied the `cf-log-in` label, Cloudflare will use the labeled endpoint for account takeover detection decisions.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/bots/execution-order.mdx b/src/content/partials/bots/execution-order.mdx
index 458ad91c88f6909..4d3aa8ec0155216 100644
--- a/src/content/partials/bots/execution-order.mdx
+++ b/src/content/partials/bots/execution-order.mdx
@@ -7,4 +7,4 @@ flowchart LR
 accTitle: Super Bot Fight Mode and custom rules execution order diagram
 accDescr: This diagram details the execution order of custom rules before Super Bot Fight Mode managed rules.
 A[Custom rules] --> B[Block AI bots<br>managed rule] --> C[Other SBFM managed rules]
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/bots/flexible-sbfm.mdx b/src/content/partials/bots/flexible-sbfm.mdx
index 207bbda9d1f29ee..d5c7abc133997b6 100644
--- a/src/content/partials/bots/flexible-sbfm.mdx
+++ b/src/content/partials/bots/flexible-sbfm.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-In parts of your site where you want bot traffic, you can use the [*Skip* action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
+In parts of your site where you want bot traffic, you can use the [_Skip_ action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
 
 You can use the [Rules language](/ruleset-engine/rules-language/) and its [operators](/ruleset-engine/rules-language/operators/) and [fields](/ruleset-engine/rules-language/fields/) in custom rules to configure a scoped rule for approved automated traffic in Super Bot Fight Mode.
diff --git a/src/content/partials/bots/ja3-ja4-null.mdx b/src/content/partials/bots/ja3-ja4-null.mdx
index 68bc0569df18296..e8829ace2150293 100644
--- a/src/content/partials/bots/ja3-ja4-null.mdx
+++ b/src/content/partials/bots/ja3-ja4-null.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or empty in logs under specific circumstances:
@@ -9,4 +8,4 @@ The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or emp
 - The field may be empty when a [Worker](/workers/) sends a request to a zone that is either internal to Cloudflare's network (O2O traffic that is not proxied) or to a third-party origin, or when a Worker is routing traffic to the target zone.
 - The fingerprints may be absent when Bot Management itself is skipped for a request, as the feature is responsible for calculating and populating these values.
 
-Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
\ No newline at end of file
+Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
diff --git a/src/content/partials/bots/jsd-availability.mdx b/src/content/partials/bots/jsd-availability.mdx
index 57c501ca55fd5a0..3306814fd548d25 100644
--- a/src/content/partials/bots/jsd-availability.mdx
+++ b/src/content/partials/bots/jsd-availability.mdx
@@ -1,6 +1,5 @@
 ---
 inputParameters: planType;;enablement
-
 ---
 
-For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
\ No newline at end of file
+For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
diff --git a/src/content/partials/bots/plan-get-started.mdx b/src/content/partials/bots/plan-get-started.mdx
index ab81f675f77e822..3e26918905eccd4 100644
--- a/src/content/partials/bots/plan-get-started.mdx
+++ b/src/content/partials/bots/plan-get-started.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To get started, review our [setup guides](/bots/get-started/). If you have any questions, visit the [community](https://community.cloudflare.com/) to engage with other Cloudflare users.
diff --git a/src/content/partials/bots/plan-intro.mdx b/src/content/partials/bots/plan-intro.mdx
index e2f77067f05bc6d..0b5da491920a683 100644
--- a/src/content/partials/bots/plan-intro.mdx
+++ b/src/content/partials/bots/plan-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To learn more about features and functionality, select a plan.
diff --git a/src/content/partials/bots/sequence-rules.mdx b/src/content/partials/bots/sequence-rules.mdx
index 5a37ee6b8ddf181..f1469b3b97b7941 100644
--- a/src/content/partials/bots/sequence-rules.mdx
+++ b/src/content/partials/bots/sequence-rules.mdx
@@ -1,6 +1,9 @@
 ---
 inputParameters: addLink;;Link
-
 ---
 
-<a href={props.two}>{props.one}</a> uses cookies to track the order of requests a user has made and the time between requests and makes them available via [Cloudflare Rules](/rules/). This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
+<a href={props.two}>{props.one}</a> uses cookies to track the order of requests
+a user has made and the time between requests and makes them available via
+[Cloudflare Rules](/rules/). This allows you to write rules that match valid or
+invalid sequences. The specific cookies used to validate sequences are called
+sequence cookies.
diff --git a/src/content/partials/bots/signals-intelligence-and-ja4.mdx b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
index d4985540fd03195..5f9750c2e03b2f8 100644
--- a/src/content/partials/bots/signals-intelligence-and-ja4.mdx
+++ b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 If you want to use JA4 fingerprints and Signals Intelligence, your Workers script must be able to handle the absence of any field in the array, including:
 
-* The possibility that the JA4 fingerprint could be missing.
-* The possibility that the `ja4Signals` array could be missing.
-* Results with `NaN` or `Infinity` values will be excluded from the array.
+- The possibility that the JA4 fingerprint could be missing.
+- The possibility that the `ja4Signals` array could be missing.
+- Results with `NaN` or `Infinity` values will be excluded from the array.
diff --git a/src/content/partials/bots/verified-bots.mdx b/src/content/partials/bots/verified-bots.mdx
index 643ff4708ca88c8..641b00e41848448 100644
--- a/src/content/partials/bots/verified-bots.mdx
+++ b/src/content/partials/bots/verified-bots.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare maintains an internal directory of [verified bot](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/) that are associated with search engine optimization (SEO), website monitoring, and more.
diff --git a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
index d6d1aa6348cc9ab..6674b5b0b076f4f 100644
--- a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
+++ b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
@@ -3,13 +3,14 @@
 If you set a large viewport width and height, your screenshot may appear blurry or pixelated. This can happen if your browser's default `deviceScaleFactor` (which defaults to 1) is not high enough for the viewport.
 
 To fix this, increase the value of the `deviceScaleFactor`.
+
 ```json
 {
-  "url": "https://cloudflare.com/",
-  "viewport": {
-    "width": 3600,
-    "height": 2400,
-    "deviceScaleFactor": 2
-  }
+	"url": "https://cloudflare.com/",
+	"viewport": {
+		"width": 3600,
+		"height": 2400,
+		"deviceScaleFactor": 2
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/byoip/cloudflare-asn-callout.mdx b/src/content/partials/byoip/cloudflare-asn-callout.mdx
index c4c4f51e5e3f276..c2e64662ef201ba 100644
--- a/src/content/partials/byoip/cloudflare-asn-callout.mdx
+++ b/src/content/partials/byoip/cloudflare-asn-callout.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Use Cloudflare's ASN]
 The process described on this page only supports using Cloudflare's ASN (AS13335). If you must announce the prefixes under your own ASN, contact your account team.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/byoip/loa.mdx b/src/content/partials/byoip/loa.mdx
index c4320799ddc0c7b..6f4223cd8341462 100644
--- a/src/content/partials/byoip/loa.mdx
+++ b/src/content/partials/byoip/loa.mdx
@@ -35,4 +35,4 @@ Regards,
 [COMPANY NAME]
 [COMPANY ADDRESS]
 [COMPANY STAMP]
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/byoip/validate-prefix-endpoint.mdx b/src/content/partials/byoip/validate-prefix-endpoint.mdx
index 096f54fc687f97e..3d0fbbd3b42c0d2 100644
--- a/src/content/partials/byoip/validate-prefix-endpoint.mdx
+++ b/src/content/partials/byoip/validate-prefix-endpoint.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
diff --git a/src/content/partials/cache/cache-reserve-billing-note.mdx b/src/content/partials/cache/cache-reserve-billing-note.mdx
index 1d60713a3590fee..6f0fbe8ec743390 100644
--- a/src/content/partials/cache/cache-reserve-billing-note.mdx
+++ b/src/content/partials/cache/cache-reserve-billing-note.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 The billable quantity is rounded up to the nearest million.
 
-
 :::
diff --git a/src/content/partials/cache/cache-reserve-eligibility.mdx b/src/content/partials/cache/cache-reserve-eligibility.mdx
index 4222abac1e72533..426e01aee0d369e 100644
--- a/src/content/partials/cache/cache-reserve-eligibility.mdx
+++ b/src/content/partials/cache/cache-reserve-eligibility.mdx
@@ -7,4 +7,4 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 - Be cacheable, according to Cloudflare's standard [cacheability factors](/cache/).
 - Have a freshness time-to-live (TTL) of at least 10 hours (set by any means such as Cache-Control / [CDN-Cache-Control](/cache/concepts/cache-control/) origin response headers, [Edge Cache TTL](/cache/how-to/edge-browser-cache-ttl/#edge-cache-ttl), [Cache TTL By Status](/cache/how-to/configure-cache-status-code/), or [Cache Rules](/cache/how-to/cache-rules/)),
 - Have a Content-Length response header.
-- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
\ No newline at end of file
+- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
diff --git a/src/content/partials/cache/cache-reserve-intro.mdx b/src/content/partials/cache/cache-reserve-intro.mdx
index e2f420e60a81457..d4dd113880b158a 100644
--- a/src/content/partials/cache/cache-reserve-intro.mdx
+++ b/src/content/partials/cache/cache-reserve-intro.mdx
@@ -4,4 +4,4 @@
 
 Cache Reserve is a large, persistent data store [implemented on top of R2](/r2/). By pushing a single button in the dashboard, your website's cacheable content will be written to Cache Reserve.
 
-In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
\ No newline at end of file
+In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
diff --git a/src/content/partials/cache/cache-reserve-limits.mdx b/src/content/partials/cache/cache-reserve-limits.mdx
index e98031a3e1fb9ba..a8fa9e8ea8c5d44 100644
--- a/src/content/partials/cache/cache-reserve-limits.mdx
+++ b/src/content/partials/cache/cache-reserve-limits.mdx
@@ -7,4 +7,4 @@
 - [Vary for images](/cache/advanced-configuration/vary-for-images/) is currently not compatible with Cache Reserve.
 - Requests to [R2 public buckets linked to a zone's domain](/r2/buckets/public-buckets/) will not use Cache Reserve. Enabling Cache Reserve for the connected zone will use Cache Reserve only for requests not destined for the R2 bucket.
 - Cache Reserve makes requests for uncompressed content directly from the origin. Unlike the standard Cloudflare CDN, Cache Reserve does not include the `Accept-Encoding: gzip` header when sending requests to the origin.
-- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
\ No newline at end of file
+- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
diff --git a/src/content/partials/cache/cache-reserve-operations.mdx b/src/content/partials/cache/cache-reserve-operations.mdx
index 7d9ec8cabea8443..ebbfac04358fb8a 100644
--- a/src/content/partials/cache/cache-reserve-operations.mdx
+++ b/src/content/partials/cache/cache-reserve-operations.mdx
@@ -22,4 +22,4 @@ Other purge methods, such as purge by tag, host, prefix, or purge everything wil
 
 :::note
 Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cache/edge-ttl.mdx b/src/content/partials/cache/edge-ttl.mdx
index 1a84b61e6d0f948..02f8bc5af24dabe 100644
--- a/src/content/partials/cache/edge-ttl.mdx
+++ b/src/content/partials/cache/edge-ttl.mdx
@@ -12,4 +12,4 @@ By default, Cloudflare caches certain HTTP response codes with the following Ed
 | 302, 303         | 20m         |
 | 404, 410         | 3m          |
 
-All other status codes are not cached by default.
\ No newline at end of file
+All other status codes are not cached by default.
diff --git a/src/content/partials/cache/regional-tiered-cache.mdx b/src/content/partials/cache/regional-tiered-cache.mdx
index 2da23da74a44c6f..84f6ff7440bd316 100644
--- a/src/content/partials/cache/regional-tiered-cache.mdx
+++ b/src/content/partials/cache/regional-tiered-cache.mdx
@@ -4,4 +4,4 @@
 
 Regional Tiered Cache provides an additional layer of caching for customers who have a global traffic footprint and want to serve content faster by avoiding network latency when there is a cache `MISS` in a lower-tier, resulting in an upper-tier fetch in a data center located far away.
 
-Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
\ No newline at end of file
+Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
diff --git a/src/content/partials/cache/smart-tiered-cache.mdx b/src/content/partials/cache/smart-tiered-cache.mdx
index f7feae4ba341a37..4cadd0acc82f9d2 100644
--- a/src/content/partials/cache/smart-tiered-cache.mdx
+++ b/src/content/partials/cache/smart-tiered-cache.mdx
@@ -14,4 +14,4 @@ While Smart Tiered Cache selects one Upper Tier per origin, when using Load Bala
 
 #### Caveats
 
-You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
\ No newline at end of file
+You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
diff --git a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
index d395290564350e8..38bc50594dca1b0 100644
--- a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
+++ b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
@@ -8,4 +7,4 @@
 [JavaScript detections](/bots/additional-configurations/javascript-detections/) are stored in the `cf_clearance` cookie.
 
 The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
index a4d3b6a8833f777..3e1cf935e85c7fd 100644
--- a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
+++ b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/). 
+You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/).
 
-Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/). 
\ No newline at end of file
+Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/).
diff --git a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
index ecd1e00cd105b61..6b6ee7d8e7a6954 100644
--- a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With [apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/), SaaS customers need to create an `A` record for their hostname that points to the IP prefix allocated to the SaaS provider's account.
@@ -11,8 +10,6 @@ example.com.  60  IN  A   192.0.2.1
 
 :::note
 
-
 For [BYOIP](/byoip/) customers, Cloudflare automatically enables the Apex Proxy Access feature on your BYOIP block, which allows Custom Hostnames to be activated via [Apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) when Authoritative DNS for a customer's hostname targets any IP addresses in your BYOIP block.
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
index cc1caa4a35ce4a3..e442ded8479e150 100644
--- a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Most customers will have a `CNAME` target, which requires their customers to create a `CNAME` record similar to:
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
index c72ac1bf7f7c156..b778c86451909e7 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
@@ -1,12 +1,10 @@
 ---
 {}
-
 ---
 
 1. To create a custom hostname using the API, use the [Create Custom Hostname](/api/resources/custom_hostnames/methods/create/) endpoint.
+   - You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
 
-   * You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
-
-2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`.  It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
+2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`. It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
 
 The response contains the complete definition of the new custom hostname.
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
index e70192ef25ae6e5..6c4d2491a949000 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
@@ -1,15 +1,12 @@
 ---
 {}
-
 ---
 
 :::note[Default behavior]
 
-
 When you create a custom hostname:
 
-* If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
-* If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
-
+- If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
+- If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
 
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
index 5734dd54f9b5277..0e5a5aff297fbc1 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,10 +10,10 @@ import { DashButton } from "~/components";
 
 2. Select **Add Custom Hostname**.
 3. Add your customer's hostname `app.customer.com` and set the relevant options, including:
-    - The [minimum TLS version](/ssl/reference/protocols/).
-    - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
-    - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
-    - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
-    - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
-    - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
+   - The [minimum TLS version](/ssl/reference/protocols/).
+   - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
+   - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
+   - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+   - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
+   - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
 4. Select **Add Custom Hostname**.
diff --git a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
index 8d09df2ede8e363..2d204cd4201372c 100644
--- a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 A **custom origin server** lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback, such as:
 
-* `soap.stores.com` goes to `origin1.com`
-* `towel.stores.com` goes to `origin2.com`
+- `soap.stores.com` goes to `origin1.com`
+- `towel.stores.com` goes to `origin2.com`
diff --git a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
index dd9e0a9dbf02a89..de24df450fd2452 100644
--- a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
+++ b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
index f75a9b302889462..b93ff80e6e1c8a8 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you first [enable](/cloudflare-for-platforms/cloudflare-for-saas/start/enable/) Cloudflare for SaaS, you need to perform a few steps prior to creating any custom hostnames.
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
index d0487c9804e2705..cfac6c51968d0bb 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render, TabItem, Tabs } from "~/components"
+import { Render, TabItem, Tabs } from "~/components";
 
 You need to perform the following steps for each custom hostname.
 
@@ -50,8 +49,6 @@ To create a custom hostname:
 
 :::note
 
-
 <Render file="issue-certs-preamble" product="cloudflare-for-platforms" />
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
index e69030364c61734..76408b768cb0721 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: planReqs
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 ## Before you begin
 
@@ -14,5 +13,5 @@ Before you start creating custom hostnames:
 3. Review the [Hostname prioritization guidelines](/ssl/reference/certificate-and-hostname-priority/#hostname-priority). Wildcard custom hostnames behave differently than an exact hostname match.
 4. (optional) Review the following documentation:
 
-* [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
-* [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+- [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
+- [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
index 82d0fca0621c733..35edd6886fe0424 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your customer is also using Cloudflare for their domain, they should keep their DNS record pointing to your SaaS provider in place for as long as they want to use your service.
diff --git a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
index 93a809da7f02598..ea5860cd4a1012d 100644
--- a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 Specific (non-wildcard) custom hostnames can use [HTTP based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/http/) for certificate renewals, as long as:
 
-* The hostname is pointing to the SaaS provider.
-* The hostname's traffic is proxying through the Cloudflare network.
+- The hostname is pointing to the SaaS provider.
+- The hostname's traffic is proxying through the Cloudflare network.
 
 If your custom hostnames do not meet these requirements, use another validation method.
diff --git a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
index 3bb70a1297de1a6..7f9762bab2589d4 100644
--- a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For each custom hostname, Cloudflare issues two certificates bundled in chains that maximize browser compatibility (unless you [upload custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/)).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
index 1d723d8f9826ad2..1e684db0ea49bf0 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
 
-* [Caching](/cache/)
-* [Workers](/workers/)
-* [Rules](/rules/)
+- [Caching](/cache/)
+- [Workers](/workers/)
+- [Rules](/rules/)
 
 For a full list of compatible products and potential limitations, refer to [Product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
index 343e065d9148425..1e0fb535dd18bf6 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
@@ -9,4 +9,4 @@ If your own Cloudflare zone is on the Enterprise plan, you have access to the [z
 
 To successfully activate the custom hostname on {props.providerName}, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to {props.providerName}, only the subfeature titled **Also prevent Subdomains** needs to be temporarily disabled.
 
-Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
\ No newline at end of file
+Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
diff --git a/src/content/partials/cloudflare-for-platforms/regional-services.mdx b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
index ee7ffcc908b6aac..c636d4b3c92b405 100644
--- a/src/content/partials/cloudflare-for-platforms/regional-services.mdx
+++ b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you have [regional services](/data-localization/regional-services/) set up for your custom hostnames, Cloudflare always uses the processing region associated with your DNS target record (instead of the processing region of any [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/)).
diff --git a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
index b4bb3909a232e68..092651f810975a3 100644
--- a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
+++ b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your SaaS domain is also a [domain using Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/), you can use your Cloudflare DNS to remove your domain from your SaaS provider.
diff --git a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
index d99a28f10dcf5ed..22b6eab5814cf27 100644
--- a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
+++ b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
\ No newline at end of file
+Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
index b78a7aab90c363e..f92949ab320cc09 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you [create a new hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/issue-certificates/) and choose this validation method, you will see the following values after a few seconds:
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
index 7c01800301e8819..0d895b1350d6147 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare's network to your customers via their own custom or vanity domains.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
index 44c1c73202134c3..cc44b4ab26564b0 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Only certain customers have access to this feature. For more details, see the [Plans page](/cloudflare-for-platforms/cloudflare-for-saas/plans/).
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
index 86394cc77e6b615..6d0ccd57fab6aec 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you would like to request an immediate recheck, [rather than wait for the next retry](/ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/), send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) with the same values as your initial `POST` request.
diff --git a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
index 39515e01e4e3b0a..04ae68397c36d17 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Wildcard custom hostnames require TXT-based validation. As the SaaS provider, you have two options for wildcard custom hostname certificate renewals:
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
index 37093f6529689dd..50ebce2cda146e9 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can access these tokens using the API with the [`GET` custom hostnames endpoint](/api/resources/custom_hostnames/methods/list/).
@@ -9,46 +8,46 @@ For example, here are two tokens highlighted in the API response for a **wildcar
 
 ```json title="Response" {11,12,13,14,15,16,17,18,19,20,21,22}
 {
-  "result": [
-    {
-      "id": "<HOSTNAME_ID>",
-      "hostname": "<HOSTNAME>",
-      "ssl": {
-        "id": "<CERTIFICATE_ID>",
-        "type": "dv",
-        "method": "txt",
-        "status": "pending_validation",
-        "validation_records": [
-          {
-            "status": "pending",
-            "txt_name": "_acme-challenge.<HOSTNAME>",
-            "txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
-          },
-          {
-            "status": "pending",
-            "txt_name": "_acme-challenge.<HOSTNAME>",
-            "txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
-          }
-        ],
-        "settings": {
-          "min_tls_version": "1.0"
-        },
-        "bundle_method": "ubiquitous",
-        "wildcard": true,
-        "certificate_authority": "google"
-      },
-      "status": "pending",
-      "ownership_verification": {
-        "type": "txt",
-        "name": "_cf-custom-hostname.<HOSTNAME>",
-        "value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-      },
-      "ownership_verification_http": {
-        "http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
-        "http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-      },
-      "created_at": "2022-10-06T19:35:33.143257Z"
-    }
-  ]
+	"result": [
+		{
+			"id": "<HOSTNAME_ID>",
+			"hostname": "<HOSTNAME>",
+			"ssl": {
+				"id": "<CERTIFICATE_ID>",
+				"type": "dv",
+				"method": "txt",
+				"status": "pending_validation",
+				"validation_records": [
+					{
+						"status": "pending",
+						"txt_name": "_acme-challenge.<HOSTNAME>",
+						"txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
+					},
+					{
+						"status": "pending",
+						"txt_name": "_acme-challenge.<HOSTNAME>",
+						"txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
+					}
+				],
+				"settings": {
+					"min_tls_version": "1.0"
+				},
+				"bundle_method": "ubiquitous",
+				"wildcard": true,
+				"certificate_authority": "google"
+			},
+			"status": "pending",
+			"ownership_verification": {
+				"type": "txt",
+				"name": "_cf-custom-hostname.<HOSTNAME>",
+				"value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+			},
+			"ownership_verification_http": {
+				"http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
+				"http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+			},
+			"created_at": "2022-10-06T19:35:33.143257Z"
+		}
+	]
 }
 ```
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
index 1b2e4694b7a24a3..b813a3302da20ca 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
index 45dff2d23eddc00..88015281280b9e2 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 Your customers should place these at their authoritative DNS provider under the `"_acme-challenge"` DNS label. Once these TXT records are in place, validation and certificate issuance will automatically complete.
 
 :::note
 
-
 These tokens are different than the hostname validation tokens.
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
index ff44799c97955f9..b28cac12e8c8a6e 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 These tokens can be fetched through the API or the dashboard when the certificates are in a [pending validation](/ssl/reference/certificate-statuses/#new-certificates) state during custom hostname creation or during certificate renewals.
diff --git a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
index 62c3d6a6525d69f..df573c1be7cd67a 100644
--- a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
+++ b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your hostname is using another validation method, you will need to [update](/api/resources/custom_hostnames/methods/edit/) the `"method"` field in the SSL object to be `"txt"`.
diff --git a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
index e0c4b7896a69330..a7d0a8eb53a6049 100644
--- a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To validate a certificate on a wildcard custom hostname, you should either set up [Delegated DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv/) or [TXT-based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/).
diff --git a/src/content/partials/cloudflare-one/access/access-block-page.mdx b/src/content/partials/cloudflare-one/access/access-block-page.mdx
index 0330f3335eae871..42cdfd762ed89a7 100644
--- a/src/content/partials/cloudflare-one/access/access-block-page.mdx
+++ b/src/content/partials/cloudflare-one/access/access-block-page.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 **Custom block pages**: Choose what users will see when they are denied access to the application.
 
-* **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
-* **Redirect URL**: Redirect to the specified website.
-* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
+- **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
+- **Redirect URL**: Redirect to the specified website.
+- **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
diff --git a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
index 8c24f29e8151dc8..ed3f8e126327b44 100644
--- a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
+++ b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
@@ -11,14 +11,15 @@ params:
 
 4. In **Certificate content**, paste the contents of your root CA.
 
-	If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
-	```txt
-	-----BEGIN CERTIFICATE-----
-	<intermediate.pem>
-	-----END CERTIFICATE-----
-	-----BEGIN CERTIFICATE-----
-	<rootCA.pem>
-	-----END CERTIFICATE-----
-	```
+   If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
 
-	{ props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
\ No newline at end of file
+   ```txt
+   -----BEGIN CERTIFICATE-----
+   <intermediate.pem>
+   -----END CERTIFICATE-----
+   -----BEGIN CERTIFICATE-----
+   <rootCA.pem>
+   -----END CERTIFICATE-----
+   ```
+
+   { props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
diff --git a/src/content/partials/cloudflare-one/access/add-target.mdx b/src/content/partials/cloudflare-one/access/add-target.mdx
index 744e5212117cbde..e96d8060689cd6f 100644
--- a/src/content/partials/cloudflare-one/access/add-target.mdx
+++ b/src/content/partials/cloudflare-one/access/add-target.mdx
@@ -3,15 +3,22 @@ params:
   - protocol
 ---
 
-import { Tabs, TabItem, Render, Details, APIRequest, GlossaryTooltip } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	Details,
+	APIRequest,
+	GlossaryTooltip,
+} from "~/components";
 
 A target represents a single resource in your infrastructure (such as a server, Kubernetes cluster, database, or container) that users will connect to through Cloudflare.
 
 {
-  props.protocol === "rdp" ? (
-		<p> Create a target for each Windows machine that requires RDP access.
+props.protocol === "rdp" ? (
+<p> Create a target for each Windows machine that requires RDP access.
 To create a new target:</p>) :
-	(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
+(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
 }
 
 <Tabs syncKey="dashPlusAPI">
@@ -86,4 +93,4 @@ The following example requires Cloudflare provider version `>=4.45.0`.
 </TabItem>
 </Tabs>
 
-Next, create an Access application to secure the target.
\ No newline at end of file
+Next, create an Access application to secure the target.
diff --git a/src/content/partials/cloudflare-one/access/app-launcher.mdx b/src/content/partials/cloudflare-one/access/app-launcher.mdx
index 7e555517f94da72..b4f2bad751637b9 100644
--- a/src/content/partials/cloudflare-one/access/app-launcher.mdx
+++ b/src/content/partials/cloudflare-one/access/app-launcher.mdx
@@ -54,8 +54,8 @@ To show an Access application in the App Launcher:
 
 6.  In **Application domains**, choose a domain to use for the App Launcher link.
 
-7. (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
+7.  (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
 
 ## Customize App Launcher appearance
 
-To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
\ No newline at end of file
+To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx
index 5090f69c89745fd..f34af47cbd7d9e0 100644
--- a/src/content/partials/cloudflare-one/access/bookmarks.mdx
+++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With Cloudflare One, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
@@ -56,4 +55,4 @@ If you attempt to assign a policy that uses an unsupported feature, the dashboar
 
 :::tip[Device posture policies]
 To show bookmarks only to users on managed devices, assign a policy that requires device posture checks (such as [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)). The bookmark will only appear in the App Launcher for users whose devices satisfy the posture requirements.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/create-service-token.mdx b/src/content/partials/cloudflare-one/access/create-service-token.mdx
index 048dfc0204abc20..1fa69e143298c53 100644
--- a/src/content/partials/cloudflare-one/access/create-service-token.mdx
+++ b/src/content/partials/cloudflare-one/access/create-service-token.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Tabs, TabItem, Details, APIRequest } from '~/components';
+import { Tabs, TabItem, Details, APIRequest } from "~/components";
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
index ad31a3a9469c5c2..5eafbf7d586642f 100644
--- a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
@@ -4,7 +4,7 @@ params:
   - supportgroups?
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Identity providers**.
 
@@ -14,12 +14,12 @@ import { Markdown } from "~/components"
 
 4. (Optional) Configure the following settings:
 
-* **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
-* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
-* **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
-	- _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
-	- _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
-	- _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
+- **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
+- **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
+- **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
+  - _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
+  - _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
+  - _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
 
 5. Select **Regenerate Secret**. Copy the **SCIM Endpoint** and **SCIM Secret**. You will need to enter these values into {props.idp}.
 
diff --git a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
index 7c3cd7116b2f389..4b7ad4e06edeccf 100644
--- a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
+++ b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
@@ -2,7 +2,6 @@
 {}
 ---
 
-
 ```tf
 resource "cloudflare_zero_trust_access_identity_provider" "microsoft_entra_id" {
 	account_id = var.cloudflare_account_id
diff --git a/src/content/partials/cloudflare-one/access/idp-integration.mdx b/src/content/partials/cloudflare-one/access/idp-integration.mdx
index d72214326c20f10..183354135c18212 100644
--- a/src/content/partials/cloudflare-one/access/idp-integration.mdx
+++ b/src/content/partials/cloudflare-one/access/idp-integration.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Render, Tabs, TabItem} from "~/components"
+import { Render, Tabs, TabItem } from "~/components";
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -33,4 +33,4 @@ import {Render, Tabs, TabItem} from "~/components"
 
 		<Render file="access/idp-integration-note" product="cloudflare-one" params={{verb: "use" }} />
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
index 1963b122d60ac7e..d87a8bf152d7198 100644
--- a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
+++ b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Your browser must [allow third-party cookies](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#allow-third-party-cookies-in-the-browser) on the application domain.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
index 0c88cd0f401e32d..6383efe24af3bc3 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
@@ -1,13 +1,12 @@
 ---
 inputParameters: uiLocation;;stepIntro
-
 ---
 
 1. In Miro, select your profile picture > **Settings** > <strong>{props.one}</strong>.
 2. Turn on **SSO/SAML**.
 3. Fill in the following fields:
-   * **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
-   * **Key x509 Certificate**: Public key from application configuration in Cloudflare One
+   - **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
+   - **Key x509 Certificate**: Public key from application configuration in Cloudflare One
 4. In **Domain**, enter the domain you want to configure SSO for and select **Enter**.
 5. {props.two} an email address from that domain and select **send verification**.
 6. Once you receive a verification email, select the link in the email, then select **Save**. When the domain is successfully configured, the **VERIFY EMAIL** label next to the domain in the SSO/SAML configuration page will disappear.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
index ae78bb666c48d5b..ef59bdce1e4d853 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
@@ -4,4 +4,4 @@ params:
   - token
 ---
 
-{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
\ No newline at end of file
+{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
index 4c14a8d7ee82fc2..8d954a610155794 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Enable Cloudflare Access as an identity provider on your Salesforce domain:
diff --git a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
index 0aaa9e7f0ecc8c3..9ef968d9aade80a 100644
--- a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
+++ b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
@@ -4,4 +4,4 @@
 
 :::note
 New users must first [register the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/) or authenticate to an Access application before SCIM provisioning can begin.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
index 3407640eddab5ff..eab1fcef7940eb3 100644
--- a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
+++ b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To secure your origin, you must validate the [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/) issued by Cloudflare Access. Token validation ensures that any requests which bypass Cloudflare Access (for example, due to a network misconfiguration) are rejected.
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
index 759ae3cd92c090e..58d1b77d29be1f9 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - [**Cross-Origin Resource Sharing (CORS) settings**](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors/)
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
index abb27fd686a9a68..4e0f540d68c6438 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 Ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
index c7820c683885328..6ff71b18c02ad6d 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
@@ -13,21 +12,29 @@ import { Render } from "~/components"
 
 4. Select **Add public hostname**.
 
-5. <Render file="access/self-hosted-app/choose-domain" product="cloudflare-one" />
+5. <Render
+   	file="access/self-hosted-app/choose-domain"
+   	product="cloudflare-one"
+   />
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-7. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "public" }}/>
+7. <Render
+   	file="access/access-choose-idps"
+   	product="cloudflare-one"
+   	params={{ appType: "public" }}
+   />
 
 8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
 9. <Render file="access/session-duration" product="cloudflare-one" />
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	- <Render file="access/access-block-page" product="cloudflare-one" />
-	<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+    - <Render file="access/access-block-page" product="cloudflare-one" />
+      <Render
+      	file="access/self-hosted-app/advanced-settings"
+      	product="cloudflare-one"
+      />
 
 11. Select **Create**.
-
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
index 9c4a7b36eb13bf2..427717a9cdab7ee 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
@@ -1,14 +1,14 @@
 ---
 {}
-
 ---
+
 When using Access self-hosted applications, the majority of Cloudflare products will be compatible with your application.
 
 However, the following products are not supported:
 
-* [Automatic Platform Optimization](/automatic-platform-optimization)
-* [Zaraz](/zaraz)
-* [Google tag gateway for advertisers](/google-tag-gateway)
+- [Automatic Platform Optimization](/automatic-platform-optimization)
+- [Zaraz](/zaraz)
+- [Google tag gateway for advertisers](/google-tag-gateway)
 
 You can disable Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain.
 
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
index 1f73a0a13cfd29a..af5476bb1880972 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
\ No newline at end of file
+Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
diff --git a/src/content/partials/cloudflare-one/access/session-duration.mdx b/src/content/partials/cloudflare-one/access/session-duration.mdx
index ac75de0b9aa9cfa..77ec2d4a99238d0 100644
--- a/src/content/partials/cloudflare-one/access/session-duration.mdx
+++ b/src/content/partials/cloudflare-one/access/session-duration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 In **Session Duration**, choose how often the user's [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token/) should expire.
diff --git a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
index c53f9130b03a46d..21858eabcee3e1e 100644
--- a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
+++ b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
@@ -3,6 +3,6 @@ params:
   - intro
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
\ No newline at end of file
+{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
diff --git a/src/content/partials/cloudflare-one/access/tags.mdx b/src/content/partials/cloudflare-one/access/tags.mdx
index 0afe99bdc346ec1..77a811446a51a56 100644
--- a/src/content/partials/cloudflare-one/access/tags.mdx
+++ b/src/content/partials/cloudflare-one/access/tags.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can label an Access application with up to 25 custom tags. End users can then filter the applications in their [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) by their tags.
diff --git a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
index 90d56df296e1cc3..bfb96fb10ada920 100644
--- a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
+++ b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
@@ -6,4 +6,4 @@ import { Render } from "~/components";
 
 To check if user identities were updated in Cloudflare One, view your [SCIM provisioning logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/).
 
-<Render file="access/scim-requires-login" product="cloudflare-one" />
\ No newline at end of file
+<Render file="access/scim-requires-login" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/aws-resolver.mdx b/src/content/partials/cloudflare-one/aws-resolver.mdx
index 9a9d914decd40c5..9c47b138f5d989e 100644
--- a/src/content/partials/cloudflare-one/aws-resolver.mdx
+++ b/src/content/partials/cloudflare-one/aws-resolver.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 Avoid configuring your [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) or [Resolver Policy](/cloudflare-one/traffic-policies/resolver-policies/) to direct all `*.amazonaws.com` DNS resolution via AWS Route 53 Resolver.
 
 Some AWS endpoints (such as `ssm.us-east-1.amazonaws.com`) are public AWS endpoints that are not resolvable via internal VPC resolution. This can break AWS Console features for users on the Cloudflare One Client.
 
-Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
\ No newline at end of file
+Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
diff --git a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
index e908569bbffc1cf..ddceb27b9e24102 100644
--- a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
+++ b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
@@ -12,4 +12,3 @@
 - [Microsoft 365 Copilot](/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot/)
 - [OpenAI](/cloudflare-one/integrations/cloud-and-saas/openai/)
 - [Anthropic](/cloudflare-one/integrations/cloud-and-saas/anthropic/)
-
diff --git a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
index aada7498182b020..e478a5a5da68b5d 100644
--- a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
+++ b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
@@ -8,4 +8,4 @@ Detect DLP matches in content used and shared within Microsoft's artificial inte
 | --------------------------------------------------------- | -------------------------------------- | -------- |
 | Microsoft: Copilot Referenced File with DLP Profile match | `fa7b06bd-cf63-41fc-9afa-a20598f7a52d` | High     |
 | Microsoft: Copilot AI Response with DLP Profile match     | `176b9299-0cee-4bbb-9c59-b18611228454` | High     |
-| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
\ No newline at end of file
+| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
diff --git a/src/content/partials/cloudflare-one/choose-team-name.mdx b/src/content/partials/cloudflare-one/choose-team-name.mdx
index a8d57921a2efb06..4d29a981f28db0a 100644
--- a/src/content/partials/cloudflare-one/choose-team-name.mdx
+++ b/src/content/partials/cloudflare-one/choose-team-name.mdx
@@ -2,7 +2,6 @@ import { GlossaryTooltip } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
 
-
 2. On the onboarding screen, choose a <GlossaryTooltip term="team name">team name</GlossaryTooltip>. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry.
 
    You can find your team name in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Settings**.
diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
index fe7557d47652954..65c136e3d2c2438 100644
--- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**.
-2. Turn on **Allow users to open a remote browser without the device client**.
\ No newline at end of file
+2. Turn on **Allow users to open a remote browser without the device client**.
diff --git a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
index 7323f05d09189c0..69056d8ee6f20d8 100644
--- a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
+++ b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
@@ -1 +1 @@
-Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
\ No newline at end of file
+Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
index 65a8f00486b5bc1..8305079a6f89537 100644
--- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
+++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
@@ -16,7 +16,7 @@ To capture data from a remote device:
      :::note
      **Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test.
      :::
-		 {props.bestPractice}
+     {props.bestPractice}
 4. Select **Run diagnostics**.
 
 DEX will now send capture requests to the configured devices. If the Cloudflare One Client is disconnected, the capture will time out after 10 minutes.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
index 83843ecfc58460f..fea35b13ae26ba6 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -22,9 +21,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -34,4 +32,4 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 
 12. Review your settings and select **Submit**.
 
-13. Select **Done**.
\ No newline at end of file
+13. Select **Done**.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
index ca5f0f65140cc17..d4376f9c0f71649 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -22,9 +21,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -43,9 +41,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
-    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
+    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 18. Select **Next**.
 
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
index a2bfdd54a9efbbb..b2310b379b92a16 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To configure quarantine notifications:
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
index 8e7f70186f96377..01fe2f78cef538f 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
\ No newline at end of file
+Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
diff --git a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
index 3ff7a31c494d759..d49c114294cdce6 100644
--- a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
+++ b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
@@ -1,10 +1,10 @@
 - **Malicious**: Traffic associated with active threat campaigns. Malicious messages invoked multiple phishing verdict triggers and met thresholds for bad behavior.
-    - **Recommendation**: Block.
+  - **Recommendation**: Block.
 - **Spam**: Traffic associated with non-malicious, commercial campaigns.
-    - **Recommendation**: Route to existing Spam quarantine folder.
+  - **Recommendation**: Route to existing Spam quarantine folder.
 - **Bulk**: Traffic often associated with newsletters or marketing campaigns. Refer to [Graymail](https://en.wikipedia.org/wiki/Graymail_%28email%29) for more details.
-    - **Recommendation**: Monitor or tag.
+  - **Recommendation**: Monitor or tag.
 - **Suspicious**: Traffic associated with phishing campaigns (and is under further analysis by our automated systems).
-    - **Recommendation**: Research these messages internally to evaluate legitimacy.
+  - **Recommendation**: Research these messages internally to evaluate legitimacy.
 - **Spoof**: Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) or has mismatching `Envelope From` and `Header From` values.
-    - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
\ No newline at end of file
+  - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
index 23143351441d03b..2edeb49998378d2 100644
--- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx
+++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
@@ -2,17 +2,17 @@ When you configure your domain, the Cloudflare dashboard will display you the fo
 
 - **Domain**: Domain name. Refer to [Manage domains](/cloudflare-one/email-security/setup/manage-domains/) to learn how to add, filter, and delete domains.
 - **Configured method**: The deployment method you used to configure your domain. Depending on how you decided to configure Email security, the dashboard will display:
-    - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
-    - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
-    - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
-- **Status**: Status indicates the state of the configuration. 
-    - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
-    - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
+  - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
+  - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
+  - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
+- **Status**: Status indicates the state of the configuration.
+  - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
+  - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
 - **Service address**: This is the email address you will use to send a copy of your email.
 - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**.
 - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration:
-    1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
-    2. Locate your integration, select **Configure**, then select **Edit**.
-    3. Rename your integration, then select **Save**. 
+  1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
+  2. Locate your integration, select **Configure**, then select **Edit**.
+  3. Rename your integration, then select **Save**.
 - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured.
-- **Date added**: Date when the domain was added.
\ No newline at end of file
+- **Date added**: Date when the domain was added.
diff --git a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
index 33c6c6c71c6243a..5ea5ae3a83f02f1 100644
--- a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
+++ b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
\ No newline at end of file
+[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
diff --git a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
index 49cd1e994f8a9f8..40c2ac71b068bec 100644
--- a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
+++ b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up)
 - A [Zero Trust organization](/cloudflare-one/setup/#2-create-a-zero-trust-organization)
-- A domain to protect
\ No newline at end of file
+- A domain to protect
diff --git a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
index 9a1bdd00693b775..b06118fd3a052a0 100644
--- a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
+++ b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can include an external logo image to display on your custom block page. The block page resizes all images to 146x146 pixels. The URL must be valid and no longer than 2048 characters. Accepted file types include SVG, PNG, JPEG, and GIF.
diff --git a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
index eec835ed93e198e..bbbfc69bd059ecb 100644
--- a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
+++ b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies**.
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
index ea9c95d04ff8dfe..046196f5fdbf1e2 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
 - **IPv4**: `100.80.0.0/16`
-- **IPv6**: `2606:4700:0cf1:4000::/64`
\ No newline at end of file
+- **IPv6**: `2606:4700:0cf1:4000::/64`
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
index 7aafd3c92aef6de..30af62814f0f3df 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
@@ -4,13 +4,13 @@
 
 import { Render, Details, GlossaryTooltip } from "~/components";
 
-| On-ramp method                                                                                      | Compatibility |
-| --------------------------------------------------------------------------------------------------- | ------------- |
-| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                                            | ✅            |
-| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)                        | ✅            |
-| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                                      | ✅            |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) | ✅            |
-| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                                              | 🚧[^1]        |
+| On-ramp method                                                                             | Compatibility |
+| ------------------------------------------------------------------------------------------ | ------------- |
+| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) | ✅            |
+| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)               | ✅            |
+| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                             | ✅            |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                    | ✅            |
+| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                           | 🚧[^1]        |
 
 [^1]: Not compatible with [ECMP routing](/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing). For hostname-based routing to work, DNS queries and the resulting network traffic must reach Cloudflare over the same IPsec/GRE tunnel. <br/>
 
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
index a639506c0b67a66..d1f4b0b967db2ba 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-import { Render, GlossaryTooltip } from "~/components"
+import { Render, GlossaryTooltip } from "~/components";
 
 In your WARP [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel.  Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode):
 
 - **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
 - **Include mode**: Add Split Tunnel entries for the following IP addresses:
-	 	<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
+  <Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
index 07c7d64a068b757..0dbf6f82fe6cd31 100644
--- a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
+++ b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
@@ -28,4 +28,4 @@ import { TabItem, Tabs } from "~/components";
 	}
 	```
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
index 1615bd27d784c47..91940427f366679 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 | Selector    | Operator | Value            | Action         |
 | ----------- | -------- | ---------------- | -------------- |
-| Application | in       | *Do Not Inspect* | Do Not Inspect |
+| Application | in       | _Do Not Inspect_ | Do Not Inspect |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
index a55001b8df4ac2c..24521accd2be220 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | Policy name                 | Selector       | Operator | Value            | Egress method                   |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
index 4e453523e39abb5..7584fb41e2afe19 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
@@ -2,7 +2,7 @@
 inputParameters: selector;;value
 ---
 
-| Selector       | Operator      | Value            | Logic | Action |
-| -------------- | ------------- | ---------------- | ----- | ------ |
-| {props.selector} | in          | <code>{props.value}</code>   | And   | Allow  |
-| User Email     | matches regex | `.*@example.com` |       |        |
+| Selector         | Operator      | Value                      | Logic | Action |
+| ---------------- | ------------- | -------------------------- | ----- | ------ |
+| {props.selector} | in            | <code>{props.value}</code> | And   | Allow  |
+| User Email       | matches regex | `.*@example.com`           |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
index 3b9f11e6ef1ca2b..77ace8200c34cdf 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
@@ -4,4 +4,4 @@
 
 | Selector       | Operator | Value        | Action |
 | -------------- | -------- | ------------ | ------ |
-| Destination IP | in       | `10.0.0.0/8` | Block  |
\ No newline at end of file
+| Destination IP | in       | `10.0.0.0/8` | Block  |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
index 293b0d23be0ff03..1ed03e7aa407058 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-| Selector       | Operator      | Value            | Logic | Action |
-| -------------- | ------------- | ---------------- | ----- | ------ |
-| Host           | in            | `wiki.internal.local`   | And   | Allow  |
-| User Email     | matches regex | `.*@example.com` |       |        |
+| Selector   | Operator      | Value                 | Logic | Action |
+| ---------- | ------------- | --------------------- | ----- | ------ |
+| Host       | in            | `wiki.internal.local` | And   | Allow  |
+| User Email | matches regex | `.*@example.com`      |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
index b23ff64f7475ed7..a7c16e3c1d91ed9 100644
--- a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
+++ b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Resolver policies](/cloudflare-one/traffic-policies/resolver-policies/) provide similar functionality to Local Domain Fallback but occur in Cloudflare Gateway rather than on the local device. This option is recommended if you want more granular control over private DNS resolution. For example, you can ensure that all users in a specific geography use the private DNS server closest to them, ensure that specific conditions are met before resolving private DNS traffic, and apply [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) to private DNS traffic.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
index 64bfa9b16dc161a..5a6e380d089015d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When using an Allow or Block action, you can optionally [block IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category) or [filter categories for `CNAME` records](/cloudflare-one/traffic-policies/domain-categories/#ignore-cname-domain-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
index 9fb4a6872e220df..a9531e7748ee785 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 The country that the request is destined for. Geolocation is determined from the target IP address. To specify a country, enter its [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                            | API example              |
-| ---------------------------------- | ------------------------ |
+| UI name                            | API example                                  |
+| ---------------------------------- | -------------------------------------------- |
 | Destination Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
index 00723a3e876eb59..335ee3ee0daeeca 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With the Device Posture selector, admins can use signals from end-user devices to secure access to their internal and external resources. For example, a security admin can choose to limit all access to internal applications based on whether specific software is installed on a device and/or if the device or software are configured in a particular way.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
index 843d9ab425e324b..76e61efb71ed111 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to DNS queries that arrived to your Gateway Resolver IP address aligned with a registered DNS location. For most Gateway customers, this is an IPv4 anycast address and policies created using this IPv4 address will apply to all DNS locations. However, each DNS location has a dedicated IPv6 address and some Gateway customers have been supplied with a dedicated IPv4 address — these both can be used to apply policies to specific registered DNS locations.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
index 272bcfbd3b2eb4f..526e97d2d3911fd 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to match against DNS queries that arrive via DNS-over-HTTPS (DoH) destined for the DoH endpoint configured for each DNS location. For example, you can use a DNS location with a DoH endpoint of `abcdefg.cloudflare-gateway.com` by choosing the DoH Subdomain selector and inputting a value of `abcdefg`.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
index 05b18f7f521327c..4f8461929b76d11 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-| UI name     | API example                                     |
-| ----------- | ----------------------------------------------- |
+| UI name     | API example                                                    |
+| ----------- | -------------------------------------------------------------- |
 | OIDC Claims | `any(identity.oidc_claims[*] == "\"department=engineering\"")` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
index e61b2a18a69b641..588a6399b52dfb6 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The protocol used to send the packet.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
index 8c09fe7735b8ada..21ddf4a78052f03 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to choose the DNS resource record type that you would like to apply policies against. For example, you can match `A` records for a domain but not `MX` records.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
index 16aa0c58ae0be8d..aa08d0cb5aaa69a 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to match domains (and optionally, [IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category)) belonging to specific [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
index f770cd8258d370f..cfc4e49bf7dcc14 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              | Evaluation phase      |
-| ----------------------------- | ------------------------ | --------------------- |
+| UI name                       | API example                                  | Evaluation phase      |
+| ----------------------------- | -------------------------------------------- | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
index bea70cb9423860e..18542f3726a8e3e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              |
-| ----------------------------- | ------------------------ |
+| UI name                       | API example                                  |
+| ----------------------------- | -------------------------------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
index f770cd8258d370f..cfc4e49bf7dcc14 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              | Evaluation phase      |
-| ----------------------------- | ------------------------ | --------------------- |
+| UI name                       | API example                                  | Evaluation phase      |
+| ----------------------------- | -------------------------------------------- | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
index 135f98ad365bdf1..2d8b06452ef3050 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
index 135f98ad365bdf1..2d8b06452ef3050 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
index fee81be8110d5cb..593bd93476a3680 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name    | API example value                           |
-| ---------- | ------------------------------------------- |
+| UI name        | API example value                           |
+| -------------- | ------------------------------------------- |
 | {props.UIname} | `identity.email == "user-name@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
index f1b4aa99de07338..7d9c06487f8bece 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
\ No newline at end of file
+| UI name        | API example                                          |
+| -------------- | ---------------------------------------------------- |
+| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
index 719a72bec8720a8..458d7606be62bb1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
\ No newline at end of file
+| UI name        | API example                                    |
+| -------------- | ---------------------------------------------- |
+| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
index 35fe7cc1e898bed..7d5f097e94c6fa9 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.name == "\"finance\""` |
\ No newline at end of file
+| UI name        | API example                             |
+| -------------- | --------------------------------------- |
+| {props.UIname} | `identity.groups.name == "\"finance\""` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
index 209566937c34f20..444ae920411c5ae 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name   | API example                    |
-| --------- | ------------------------------ |
-| {props.UIname}  | `identity.name == "user-name"` |
\ No newline at end of file
+| UI name        | API example                    |
+| -------------- | ------------------------------ |
+| {props.UIname} | `identity.name == "user-name"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
index bd7de5ffe296634..253f211beb4c83e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name         | API example                                                                                | Evaluation phase      |
-| --------------- | ------------------------------------------------------------------------------------------ | --------------------- |
-| User Email      | `identity.email == "user@example.com"`                                                     | Before DNS resolution |
-| User Name       | `identity.name == "Test User"`                                                             | Before DNS resolution |
-| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               | Before DNS resolution |
-| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           | Before DNS resolution |
-| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  | Before DNS resolution |
-| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
+| UI name           | API example                                                                                                    | Evaluation phase      |
+| ----------------- | -------------------------------------------------------------------------------------------------------------- | --------------------- |
+| User Email        | `identity.email == "user@example.com"`                                                                         | Before DNS resolution |
+| User Name         | `identity.name == "Test User"`                                                                                 | Before DNS resolution |
+| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   | Before DNS resolution |
+| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               | Before DNS resolution |
+| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       | Before DNS resolution |
+| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
index e963ab12286d3ee..e18e640ce352a0d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name         | API example                                                                                |
-| --------------- | ------------------------------------------------------------------------------------------ |
-| User Email      | `identity.email == "user@example.com"`                                                     |
-| User Name       | `identity.name == "Test User"`                                                             |
-| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               |
-| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           |
-| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  |
-| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
+| UI name           | API example                                                                                                    |
+| ----------------- | -------------------------------------------------------------------------------------------------------------- |
+| User Email        | `identity.email == "user@example.com"`                                                                         |
+| User Name         | `identity.name == "Test User"`                                                                                 |
+| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   |
+| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               |
+| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       |
+| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
index ce7d5d89de6d711..8e62f876db500b1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
 Identity-based selectors include:
 
-* **SAML Attributes**
-* **User Email**
-* **User Group Emails**
-* **User Group IDs**
-* **User Group Names**
-* **User Name**
+- **SAML Attributes**
+- **User Email**
+- **User Group Emails**
+- **User Group IDs**
+- **User Group Names**
+- **User Name**
 
 To use identity-based selectors, enable **Traffic and DNS mode** in the Cloudflare One Client and enroll your user in your organization. For more information, refer to [Identity-based policies](/cloudflare-one/traffic-policies/identity-selectors/).
diff --git a/src/content/partials/cloudflare-one/gateway/value.mdx b/src/content/partials/cloudflare-one/gateway/value.mdx
index a438bb02fbddee1..8ba2eb6529409da 100644
--- a/src/content/partials/cloudflare-one/gateway/value.mdx
+++ b/src/content/partials/cloudflare-one/gateway/value.mdx
@@ -17,8 +17,8 @@ Regular expressions are evaluated using Rust. The Rust implementation is slightl
 
 If you want to match multiple values, you can use the pipe symbol (`|`) as an OR operator. You do not need to use an escape character (`\`) before the pipe symbol. For example, the following expression evaluates to true when the {props.selectordescription} matches either <code>{props.valueOne}</code> or <code>{props.valueTwo}</code>:
 
-| Selector    | Operator        | Value          |
-| ----------- | --------------- | -------------- |
+| Selector         | Operator         | Value                                               |
+| ---------------- | ---------------- | --------------------------------------------------- |
 | {props.selector} | {props.operator} | <code>{props.valueOne}&#124;{props.valueTwo}</code> |
 
 In addition to regular expressions, you can use [logical operators](#logical-operators) to match multiple values.
diff --git a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
index d14d28f9b8b9303..c8d77f235da0dee 100644
--- a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
+++ b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Posture checks** > **Service provider checks**.
 2. Select **Add a check**.
diff --git a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
index 38dd06ceea2f117..251164d2d766ee4 100644
--- a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
+++ b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
@@ -1,6 +1,5 @@
 ---
 inputParameters: param1
-
 ---
 
 Cloudflare One Client is [deployed](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) on the device. For a list of supported modes and operating systems, refer to <a href={props.link}>{props.name}</a>.
diff --git a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
index 41541ce5b9dac6d..5927c815e59262a 100644
--- a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
+++ b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
@@ -4,8 +4,8 @@
 
 To decrypt the log, follow the instructions in the [SSH Logging CLI repository](https://github.com/cloudflare/ssh-log-cli/). In the following example, `sshkey` is the private key that matches the public key uploaded to Cloudflare.
 
-   ```sh
-   ./ssh-log-cli decrypt -i sshlog -k sshkey
-   ```
+```sh
+./ssh-log-cli decrypt -i sshlog -k sshkey
+```
 
-   This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
+This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
diff --git a/src/content/partials/cloudflare-one/ssh/public-key.mdx b/src/content/partials/cloudflare-one/ssh/public-key.mdx
index 6cdb18030f52db0..67338a0b2b7b927 100644
--- a/src/content/partials/cloudflare-one/ssh/public-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/public-key.mdx
@@ -16,9 +16,9 @@
 
 3. In the `ca.pub` file, paste the public key without any modifications.
 
-	```txt title="ca.pub"
-	ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
-	```
+   ```txt title="ca.pub"
+   ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
+   ```
 
    The `ca.pub` file can hold multiple keys, listed one per line. Empty lines and comments starting with `#` are also allowed.
 
diff --git a/src/content/partials/cloudflare-one/ssh/restart-server.mdx b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
index 4e91c37de63e2e5..ea942613d292e20 100644
--- a/src/content/partials/cloudflare-one/ssh/restart-server.mdx
+++ b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Tabs, TabItem, Render } from "~/components"
+import { Tabs, TabItem, Render } from "~/components";
 
 Once you have modified your `sshd` configuration, reload the SSH service on the remote machine for the changes to take effect.
 
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
index 5117c9c548cc54c..edd0dc07d1ee8a5 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 :::note
 
 Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
index 15141e1a16ba29f..667604bc9b6a4ef 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
@@ -43,4 +43,4 @@ import { Render, Details, APIRequest, Tabs, TabItem } from "~/components";
 4. Copy the `public_key` value returned in the response.
 
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
index 35834d8c2063b23..fbcdf62609e8975 100644
--- a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
@@ -3,7 +3,7 @@ params:
   - note
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 To log SSH commands, you will need to generate an HPKE key pair and upload the public key to Cloudflare.
 
diff --git a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
index 2492eb7979d2109..be9833c0d225c55 100644
--- a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
@@ -14,161 +14,161 @@ The following configuration will modify settings in your Cloudflare account.
 
 2.  Add the following resources to `Cloudflare-config.tf`:
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        ```tf
-
-        # Creates a new remotely-managed tunnel for the GCP VM.
-        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-        	account_id    = var.cloudflare_account_id
-        	name          = "Terraform GCP tunnel"
-        	config_src    = "cloudflare"
-        }
-
-        # Reads the token used to run the tunnel on the server.
-        data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
-        	account_id 	= var.cloudflare_account_id
-        	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        }
-
-        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-        resource "cloudflare_dns_record" "http_app" {
-        	zone_id = var.cloudflare_zone_id
-        	name    = "http_app"
-        	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
-        	type    = "CNAME"
-        	ttl     = 1
-        	proxied = true
-        }
-
-        # Configures tunnel with a published application for clientless access.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-        	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        	account_id = var.cloudflare_account_id
-        	config     = {
-        		ingress 	= [
-        			{
-        				hostname = "http_app.${var.cloudflare_zone}"
-        				service  = "http://httpbin:80"
-        			},
-        			{
-        				service  = "http_status:404"
-        			}
-        		]
-        	}
-        }
-
-        # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
-        account_id         = var.cloudflare_account_id
-        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        network            = google_compute_instance.http_server.network_interface.0.network_ip
-        comment            = "Example tunnel route"
-        }
-
-        # Creates a reusable Access policy.
-        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-        	account_id   = var.cloudflare_account_id
-        	name         = "Allow email addresses"
-        	decision     = "allow"
-        	include      = [
-        		{
-        			email = {
-        				email = var.cloudflare_email
-        			}
-        		},
-        		{
-        			email_domain = {
-        				domain = "@example.com"
-        			}
-        		}
-        	]
-        }
-
-        # Creates an Access application to control who can connect to the public hostname.
-        resource "cloudflare_zero_trust_access_application" "http_app" {
-        	account_id       = var.cloudflare_account_id
-        	type             = "self_hosted"
-        	name             = "Access application for http_app.${var.cloudflare_zone}"
-        	domain           = "http_app.${var.cloudflare_zone}"
-        	policies = [
-        		{
-        			id = cloudflare_zero_trust_access_policy.allow_emails.id
-        			precedence = 1
-        		}
-        	]
-        }
-        ```
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        # Generates a 32-byte secret for the tunnel.
-        resource "random_bytes" "tunnel_secret" {
-        	byte_length = 32
-        }
-
-        # Creates a new remotely-managed tunnel for the GCP VM.
-        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-        	account_id = var.cloudflare_account_id
-        	name       = "Terraform GCP tunnel"
-        	secret     = random_bytes.tunnel_secret.base64
-        }
-
-        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-        resource "cloudflare_record" "http_app" {
-        	zone_id = var.cloudflare_zone_id
-        	name    = "http_app"
-        	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
-        	type    = "CNAME"
-        	proxied = true
-        }
-
-        # Configures tunnel with a published application for clientless access.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-        	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        	account_id = var.cloudflare_account_id
-        	config {
-        		ingress_rule {
-        			hostname = "${cloudflare_record.http_app.hostname}"
-        			service  = "http://httpbin:80"
-        		}
-        		ingress_rule {
-        			service  = "http_status:404"
-        		}
-        	}
-        }
-
-        # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
-        resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
-        account_id         = var.cloudflare_account_id
-        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        network            = google_compute_instance.http_server.network_interface.0.network_ip
-        comment            = "Example tunnel route"
-        }
-
-        # Creates an Access application to control who can connect to the public hostname.
-        resource "cloudflare_zero_trust_access_application" "http_app" {
-        	account_id          = var.cloudflare_account_id
-        	name             = "Access application for http_app.${var.cloudflare_zone}"
-        	domain           = "http_app.${var.cloudflare_zone}"
-        }
-
-        # Creates a (legacy) Access policy for the Access application.
-        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-        	application_id = cloudflare_zero_trust_access_application.http_app.id
-        	account_id        = var.cloudflare_account_id
-        	name           = "Example policy for http_app.${var.cloudflare_zone}"
-        	precedence     = "1"
-        	decision       = "allow"
-        	include {
-        		email = [var.cloudflare_email]
-        	}
-        }
-        ```
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            ```tf
+    
+            # Creates a new remotely-managed tunnel for the GCP VM.
+            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+            	account_id    = var.cloudflare_account_id
+            	name          = "Terraform GCP tunnel"
+            	config_src    = "cloudflare"
+            }
+    
+            # Reads the token used to run the tunnel on the server.
+            data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
+            	account_id 	= var.cloudflare_account_id
+            	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            }
+    
+            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+            resource "cloudflare_dns_record" "http_app" {
+            	zone_id = var.cloudflare_zone_id
+            	name    = "http_app"
+            	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
+            	type    = "CNAME"
+            	ttl     = 1
+            	proxied = true
+            }
+    
+            # Configures tunnel with a published application for clientless access.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+            	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            	account_id = var.cloudflare_account_id
+            	config     = {
+            		ingress 	= [
+            			{
+            				hostname = "http_app.${var.cloudflare_zone}"
+            				service  = "http://httpbin:80"
+            			},
+            			{
+            				service  = "http_status:404"
+            			}
+            		]
+            	}
+            }
+    
+            # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
+            account_id         = var.cloudflare_account_id
+            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            network            = google_compute_instance.http_server.network_interface.0.network_ip
+            comment            = "Example tunnel route"
+            }
+    
+            # Creates a reusable Access policy.
+            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+            	account_id   = var.cloudflare_account_id
+            	name         = "Allow email addresses"
+            	decision     = "allow"
+            	include      = [
+            		{
+            			email = {
+            				email = var.cloudflare_email
+            			}
+            		},
+            		{
+            			email_domain = {
+            				domain = "@example.com"
+            			}
+            		}
+            	]
+            }
+    
+            # Creates an Access application to control who can connect to the public hostname.
+            resource "cloudflare_zero_trust_access_application" "http_app" {
+            	account_id       = var.cloudflare_account_id
+            	type             = "self_hosted"
+            	name             = "Access application for http_app.${var.cloudflare_zone}"
+            	domain           = "http_app.${var.cloudflare_zone}"
+            	policies = [
+            		{
+            			id = cloudflare_zero_trust_access_policy.allow_emails.id
+            			precedence = 1
+            		}
+            	]
+            }
+            ```
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            # Generates a 32-byte secret for the tunnel.
+            resource "random_bytes" "tunnel_secret" {
+            	byte_length = 32
+            }
+    
+            # Creates a new remotely-managed tunnel for the GCP VM.
+            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+            	account_id = var.cloudflare_account_id
+            	name       = "Terraform GCP tunnel"
+            	secret     = random_bytes.tunnel_secret.base64
+            }
+    
+            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+            resource "cloudflare_record" "http_app" {
+            	zone_id = var.cloudflare_zone_id
+            	name    = "http_app"
+            	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
+            	type    = "CNAME"
+            	proxied = true
+            }
+    
+            # Configures tunnel with a published application for clientless access.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+            	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            	account_id = var.cloudflare_account_id
+            	config {
+            		ingress_rule {
+            			hostname = "${cloudflare_record.http_app.hostname}"
+            			service  = "http://httpbin:80"
+            		}
+            		ingress_rule {
+            			service  = "http_status:404"
+            		}
+            	}
+            }
+    
+            # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
+            resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
+            account_id         = var.cloudflare_account_id
+            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            network            = google_compute_instance.http_server.network_interface.0.network_ip
+            comment            = "Example tunnel route"
+            }
+    
+            # Creates an Access application to control who can connect to the public hostname.
+            resource "cloudflare_zero_trust_access_application" "http_app" {
+            	account_id          = var.cloudflare_account_id
+            	name             = "Access application for http_app.${var.cloudflare_zone}"
+            	domain           = "http_app.${var.cloudflare_zone}"
+            }
+    
+            # Creates a (legacy) Access policy for the Access application.
+            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+            	application_id = cloudflare_zero_trust_access_application.http_app.id
+            	account_id        = var.cloudflare_account_id
+            	name           = "Example policy for http_app.${var.cloudflare_zone}"
+            	precedence     = "1"
+            	decision       = "allow"
+            	include {
+            		email = [var.cloudflare_email]
+            	}
+            }
+            ```
+            </TabItem>
+            </Tabs>
 
 To learn more about these resources, refer to the [Cloudflare provider documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
diff --git a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
index 4eca7f0c1b7957c..e21650fa17456a6 100644
--- a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
@@ -14,88 +14,88 @@ The following configuration defines the specifications for the GCP virtual machi
 
 2.  Add the following content to `GCP-config.tf`:
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        ```tf
-        # OS the server will use
-        data "google_compute_image" "image" {
-        	family  = "ubuntu-2204-lts"
-        	project = "ubuntu-os-cloud"
-        }
-
-        # GCP Instance resource
-        resource "google_compute_instance" "http_server" {
-        	name         = "test"
-        	machine_type = var.machine_type
-        	zone         = var.zone
-        	tags         = []
-        	boot_disk {
-        		initialize_params {
-        			image = data.google_compute_image.image.self_link
-        		}
-        	}
-
-        	network_interface {
-        		network = "default"
-        		access_config {
-        			//Ephemeral IP
-        		}
-        	}
-        	// Optional config to make instance ephemeral
-        /*  scheduling {
-        		preemptible       = true
-        		automatic_restart = false
-        	} */
-
-        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-        		{
-        			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
-        		})
-        }
-        ```
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        # OS the server will use
-        data "google_compute_image" "image" {
-        	family  = "ubuntu-2204-lts"
-        	project = "ubuntu-os-cloud"
-        }
-
-        # GCP Instance resource
-        resource "google_compute_instance" "http_server" {
-        	name         = "test"
-        	machine_type = var.machine_type
-        	zone         = var.zone
-        	tags         = []
-        	boot_disk {
-        		initialize_params {
-        			image = data.google_compute_image.image.self_link
-        		}
-        	}
-
-        	network_interface {
-        		network = "default"
-        		access_config {
-        			//Ephemeral IP
-        		}
-        	}
-        	// Optional config to make instance ephemeral
-        /*  scheduling {
-        		preemptible       = true
-        		automatic_restart = false
-        	} */
-
-        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-        		{
-        			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
-        		})
-        }
-        ```
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            ```tf
+            # OS the server will use
+            data "google_compute_image" "image" {
+            	family  = "ubuntu-2204-lts"
+            	project = "ubuntu-os-cloud"
+            }
+    
+            # GCP Instance resource
+            resource "google_compute_instance" "http_server" {
+            	name         = "test"
+            	machine_type = var.machine_type
+            	zone         = var.zone
+            	tags         = []
+            	boot_disk {
+            		initialize_params {
+            			image = data.google_compute_image.image.self_link
+            		}
+            	}
+    
+            	network_interface {
+            		network = "default"
+            		access_config {
+            			//Ephemeral IP
+            		}
+            	}
+            	// Optional config to make instance ephemeral
+            /*  scheduling {
+            		preemptible       = true
+            		automatic_restart = false
+            	} */
+    
+            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+            		{
+            			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
+            		})
+            }
+            ```
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            # OS the server will use
+            data "google_compute_image" "image" {
+            	family  = "ubuntu-2204-lts"
+            	project = "ubuntu-os-cloud"
+            }
+    
+            # GCP Instance resource
+            resource "google_compute_instance" "http_server" {
+            	name         = "test"
+            	machine_type = var.machine_type
+            	zone         = var.zone
+            	tags         = []
+            	boot_disk {
+            		initialize_params {
+            			image = data.google_compute_image.image.self_link
+            		}
+            	}
+    
+            	network_interface {
+            		network = "default"
+            		access_config {
+            			//Ephemeral IP
+            		}
+            	}
+            	// Optional config to make instance ephemeral
+            /*  scheduling {
+            		preemptible       = true
+            		automatic_restart = false
+            	} */
+    
+            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+            		{
+            			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
+            		})
+            }
+            ```
+            </TabItem>
+            </Tabs>
diff --git a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
index cda294b702f2e15..5afae47ec52d2f1 100644
--- a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
@@ -25,4 +25,4 @@ provider "google" {
 }
 provider "random" {
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/terraform/providers.mdx b/src/content/partials/cloudflare-one/terraform/providers.mdx
index 113455091a647e1..962ef714f4ec1c3 100644
--- a/src/content/partials/cloudflare-one/terraform/providers.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers.mdx
@@ -14,41 +14,41 @@ You will need to declare the [providers](https://registry.terraform.io/browse/pr
 
 2.  Add the following providers to `providers.tf`. The `random` provider is used to generate a tunnel secret.
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        <Render file="terraform/providers-v5" product="cloudflare-one" />
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        terraform {
-        	required_providers {
-        		cloudflare = {
-        			source = "cloudflare/cloudflare"
-        			version = ">= 4.40.0, < 5.0.0"
-        		}
-        		google = {
-        			source = "hashicorp/google"
-        		}
-        		random = {
-        			source = "hashicorp/random"
-        		}
-        	}
-        	required_version = ">= 1.2"
-        }
-
-        # Providers
-        provider "cloudflare" {
-        	api_token    = var.cloudflare_token
-        }
-        provider "google" {
-        	project    = var.gcp_project_id
-        }
-        provider "random" {
-        }
-        ```
-
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            <Render file="terraform/providers-v5" product="cloudflare-one" />
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            terraform {
+            	required_providers {
+            		cloudflare = {
+            			source = "cloudflare/cloudflare"
+            			version = ">= 4.40.0, < 5.0.0"
+            		}
+            		google = {
+            			source = "hashicorp/google"
+            		}
+            		random = {
+            			source = "hashicorp/random"
+            		}
+            	}
+            	required_version = ">= 1.2"
+            }
+    
+            # Providers
+            provider "cloudflare" {
+            	api_token    = var.cloudflare_token
+            }
+            provider "google" {
+            	project    = var.gcp_project_id
+            }
+            provider "random" {
+            }
+            ```
+    
+            </TabItem>
+            </Tabs>
diff --git a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
index a68729e1c588fba..6abc149ee79e338 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -3,31 +3,37 @@ Review common troubleshooting scenarios for Cloudflare Browser Isolation.
 ## Connectivity and sessions
 
 ### No Browsers Available
+
 If you encounter a `No Browsers Available` alert, please file feedback via the Cloudflare One Client. This error typically indicates a temporary capacity issue in the data center or a connectivity problem between your client and the remote browser.
 
 ### Maximum Sessions Reached
+
 This alert appears if your device attempts to establish more than two concurrent remote browser instances. A browser isolation session is shared across all tabs and windows within the same browser (for example, all Chrome tabs share one session). You can use two different browsers (such as Chrome and Firefox) concurrently, but opening a third will trigger this alert. To release a session, close all tabs and windows in one of your local browsers.
 
 ## Rendering and performance
 
 ### WebGL Rendering Error
+
 Cloudflare Browser Isolation uses Network Vector Rendering (NVR), which does not support WebGL (Web Graphics Library) in all environments. If a website requires WebGL and your device lacks the necessary hardware resources in the virtualized environment, you may see a rendering error.
 
 To resolve this, try enabling software rasterization in your browser:
+
 1. Go to `chrome://flags/#override-software-rendering-list`.
-2. Set **Override software rendering list** to *Enabled*.
+2. Set **Override software rendering list** to _Enabled_.
 3. Select **Relaunch**.
 
 ### Blank screen on Windows
+
 On Windows devices, Clientless Web Isolation may load with a blank screen if there is a conflict between browser mDNS settings and Windows IGMP configuration.
 
-| IGMPLevel | WebRTC Anonymization | Result |
-| --------- | -------------------- | ------ |
-| 0 (disabled) | Enabled / Default | ❌ Blank screen |
-| 0 (disabled) | Disabled | ✅ Works |
-| 2 (enabled) | Enabled / Default | ✅ Works |
+| IGMPLevel    | WebRTC Anonymization | Result          |
+| ------------ | -------------------- | --------------- |
+| 0 (disabled) | Enabled / Default    | ❌ Blank screen |
+| 0 (disabled) | Disabled             | ✅ Works        |
+| 2 (enabled)  | Enabled / Default    | ✅ Works        |
 
 To fix this, either disable **Anonymize local IPs exposed by WebRTC** in your browser flags or ensure `IGMPLevel` is enabled (set to `2`) in your Windows network settings.
 
 ### Rendering issues (CSS/Images)
+
 If a website displays incorrectly (for example, broken CSS or missing images), it may indicate that the remote browser is unable to fetch specific resources from the origin server. Check your [Gateway HTTP logs](/cloudflare-one/traffic-policies/troubleshooting/) for any blocked subresources that might be required by the page.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
index 812e31a9e577986..ea6662dd6b23a61 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
@@ -3,13 +3,17 @@ Use this guide to troubleshoot common issues with Cloud Access Security Broker (
 ## Security findings
 
 ### Findings not appearing
+
 If you do not see findings for an integrated application:
+
 - **Wait for scan**: Initial scans can take up to 24 hours depending on the size of the application.
 - **Permissions**: Ensure the account used to integrate the application has the necessary administrative permissions.
 - **Enabled status**: Verify that the integration is enabled in the Zero Trust dashboard.
 
 ### False positives
+
 If CASB flags a configuration that is intended for your organization:
+
 1. Go to **CASB** &gt; **Findings**.
 2. Select the finding and choose **Dismiss**.
 3. Provide a reason for dismissal to help refine future scans.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
index d9f76c11a762d23..b0b9af1de6363da 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
@@ -3,6 +3,7 @@ Review common troubleshooting scenarios for Digital Experience Monitoring (DEX).
 ## Data visibility
 
 ### No data displayed for certain users
+
 If you do not see DEX data for specific users in your organization, verify the following:
 
 - **Client version**: Ensure the users are running a version of the Cloudflare One Client that supports DEX.
@@ -10,11 +11,13 @@ If you do not see DEX data for specific users in your organization, verify the f
 - **Traffic routing**: DEX requires that traffic to Cloudflare's orchestration API is not blocked by local firewalls or SSL-inspecting proxies.
 
 ### Fleet status not updating
+
 The Fleet status dashboard can take several minutes to reflect changes in device connectivity. If a device remains in an incorrect state, try disconnecting and reconnecting the Cloudflare One Client to force a status update.
 
 ## Remote captures
 
 ### Remote capture fails to start
+
 Remote captures require the Cloudflare One Client to be connected and able to communicate with the Cloudflare control plane. If a capture fails to start:
 
 - Verify the device status in the Zero Trust dashboard.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
index 77aac5be079b8ae..500c1dc89b9f0c0 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
@@ -4,44 +4,51 @@ Review common troubleshooting scenarios for Cloudflare Email Security.
 
 Email Security identifies threats using detections that result in a final disposition. You can inspect email headers to understand why a specific disposition was applied.
 
-| Attribute | Description |
-| --------- | ----------- |
-| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list. |
-| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain. |
-| `NEW_DOMAIN_LINK` | The email contains links to a newly registered domain. |
-| `ENCRYPTED` | The email message is encrypted. |
-| `BEC` | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
+| Attribute           | Description                                                                                                                                 |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list.                                                                                          |
+| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain.                                                                                          |
+| `NEW_DOMAIN_LINK`   | The email contains links to a newly registered domain.                                                                                      |
+| `ENCRYPTED`         | The email message is encrypted.                                                                                                             |
+| `BEC`               | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
 
 ## Detections and reclassification
 
 ### Handle a false positive
-A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam. 
+
+A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam.
 
 **Solution**:
+
 1. In the Email Security dashboard, go to **Investigation**.
 2. Find the email and select **Submit for reclassification**.
 3. Choose the correct disposition (for example, `Clean`).
 4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) list.
 
 ### Handle a false negative
+
 A false negative occurs when a malicious email is not detected by Email Security.
 
 **Solution**:
+
 1. Ensure the email actually passed through Email Security by checking for the `X-CFEmailSecurity-Disposition` header.
 2. Submit the email for reclassification in the dashboard. This is the preferred method for reporting missed detections.
 
 ## Authentication errors
 
 ### DMARC failures
+
 Email Security may mark an email as **SPAM** if it fails DMARC authentication and the sending domain has a `p=reject` or `p=quarantine` policy.
 
 **Solution**:
+
 - Ask the sender to fix their DMARC/SPF/DKIM records.
 - Configure an [Acceptable Sender](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) entry to suppress the failure for that specific sender.
 
 ## Delivery issues
 
 ### Emails are delayed or not arriving
+
 If emails are not being delivered or are arriving with significant latency:
 
 1. **Check MX records**: Ensure your [MX records](/cloudflare-one/email-security/setup/) are correctly configured and pointing to Cloudflare.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
index a5dd284025e9f77..9aa7ada94a6a62d 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
@@ -3,9 +3,11 @@ This guide helps you troubleshoot common issues with Cloudflare Gateway policies
 ## Blocked websites and connectivity
 
 ### A website is blocked incorrectly
+
 If you believe a domain has been incorrectly blocked by Gateway's security categories or threat intelligence, you can use the [Cloudflare Radar categorization feedback form](https://radar.cloudflare.com/categorization-feedback/) to request a review.
 
 ### Error 526: Invalid SSL certificate
+
 Gateway presents a **526** error page when it cannot establish a secure connection to the origin. This typically occurs in two cases:
 
 - **Untrusted origin certificate**: The certificate presented by the origin server is expired, revoked, or issued by an unknown authority.
@@ -14,14 +16,17 @@ Gateway presents a **526** error page when it cannot establish a secure connecti
 For more information, refer to [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ### Error 502: Bad Gateway
+
 This issue can occur when communicating with an origin that partially supports HTTP/2. If the origin requests a downgrade to HTTP/1.1 (for example, via a `RST_STREAM` frame with `HTTP_1_1_REQUIRED`), Gateway will not automatically reissue the request over HTTP/1.1 and will instead return a `502 Bad Gateway`. To resolve this, disable HTTP/2 at the origin server.
 
 ### Untrusted certificate warnings
+
 If users see certificate warnings for every page, ensure that the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) is installed and trusted on their devices. This is required for Gateway to inspect HTTPS traffic.
 
 ## Dashboard and analytics
 
 ### Gateway analytics not displayed
+
 If you do not see analytics on the Gateway Overview page:
 
 - **Verify DNS traffic**: Ensure your devices are actually sending queries to Gateway. Check your [DNS locations](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) and verify the source IPv4 address.
@@ -126,8 +131,8 @@ To resolve this issue:
 
 You have configured Gateway to resolve internal hostnames, but users are unable to access them. For example, a user connected to the Cloudflare One Client tries to access an internal service like `jira.mycompany.local`, but the DNS query fails.
 
-| Common causes                              | Solution                                                                                                                                                                                                                  |
-| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                             |
+| Common causes                              | Solution                                                                                                                                                                                                                                       |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                                               |
 | Split Tunnel excludes the private IP range | If your internal resources are in a private IP range (such as `10.0.0.0/8`), that range must be included in the tunnel. If it is in the Exclude list of your Split Tunnel configuration, the Cloudflare One Client will not proxy the traffic. |
-| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                      |
+| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                                           |
diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
index bec8b880edeb7cc..0a544adaa854c9b 100644
--- a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Render } from "~/components";
@@ -9,4 +8,4 @@ A `1033` error indicates your tunnel is not connected to Cloudflare's network be
 
 First, review whether your tunnel is listed as `Active` in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status:
 
-<Render file="tunnel/tunnel-status" product="cloudflare-one" />
\ No newline at end of file
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
index cf11d2740614eac..b4d07916659c2d7 100644
--- a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
@@ -1,11 +1,12 @@
 ---
 {}
-
 ---
 
 Minimum permissions needed to create, delete, and configure tunnels for an account:
+
 - [Cloudflare Access](/cloudflare-one/roles-permissions/)
 
 Additional permissions needed to [route traffic to a public hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) and to be able to perform `cloudflared login`:
+
 - [DNS](/fundamentals/manage-members/roles/)
-- [Load Balancer](/fundamentals/manage-members/roles/)
\ No newline at end of file
+- [Load Balancer](/fundamentals/manage-members/roles/)
diff --git a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
index 7df9b2e5a62c416..49599f43b544a2f 100644
--- a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To add a published application when creating a new tunnel:
@@ -8,16 +7,16 @@ To add a published application when creating a new tunnel:
 1. Go to the **Published applications** tab.
 
 2. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-	:::note
-	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-	:::
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
 
 3. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example,
-	- **Type**: _HTTP_
-	- **URL**: `localhost:8000`
+   - **Type**: _HTTP_
+   - **URL**: `localhost:8000`
 
 4. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
    ![Example of a published application route in the Cloudflare One dashboard](~/assets/images/cloudflare-one/connections/connect-apps/published-app.png)
 
-5. Select **Save**.
\ No newline at end of file
+5. Select **Save**.
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
index b070a82d446402e..10f16e4d43c7afe 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
index 00915193311f7b7..ceda180a2994ca9 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
@@ -5,10 +5,9 @@ params:
 
 TCP monitors are not supported for tunnel endpoints. Instead, create a health check endpoint on the `cloudflared` host and use an HTTPS monitor. For example, you can use `cloudflared` to return a fixed HTTP status response:
 
-1. <a href={props.publishedAppRouteURL}>Add a published application route</a> for the health check:
-   - **Hostname**: `health-check.example.com`
-   - **Service Type**: _HTTP_STATUS_
-   - **HTTP Status Code**: `200`
+1. <a href={props.publishedAppRouteURL}>Add a published application route</a>
+   for the health check: - **Hostname**: `health-check.example.com` - **Service
+   Type**: _HTTP_STATUS_ - **HTTP Status Code**: `200`
 2. [Create a monitor](/load-balancing/monitors/create-monitor/) with these settings:
    - **Type**: _HTTPS_
    - **Path**: `/`
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
index f61bde5fb1a3556..a96ead9f4e833cc 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
-* Size each host with minimum 4GB of RAM and 4 CPU cores.
-* Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
+- Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
+- Size each host with minimum 4GB of RAM and 4 CPU cores.
+- Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
 
 This setup is usually sufficient to handle traffic from 8,000 users (4,000 per host).
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
index e38f3ea59068e4a..399600466878e2a 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Unlike legacy VPNs where throughput is determined by the server's memory, CPU and other hardware specifications, Cloudflare Tunnel throughput is primarily limited by the number of ports configured in system software. Therefore, when sizing your `cloudflared` server, the most important element is sizing the available ports on the machine to reflect the expected throughput of TCP and UDP traffic.
diff --git a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
index c4aa95aa270a7b2..d3d57f5ddd564cf 100644
--- a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
@@ -3,4 +3,3 @@
 ---
 
 To prevent Cloudflare One Client users from accessing your entire private network, we recommend creating a [catch-all Gateway block policy](/learning-paths/replace-vpn/build-policies/create-policy/#catch-all-policy) for your private IP space. You can then layer on higher priority Allow policies (in either Access or Gateway) which grant users access to specific applications or IPs.
-
diff --git a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
index 32bad08d6a11538..836d5c4e7335fae 100644
--- a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
@@ -1,5 +1,4 @@
 ---
-
 ---
 
 In your device profile, configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) goes through the WARP tunnel. Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode). For example, if your devices use the default `100.96.0.0/12` range:
diff --git a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
index 6c082731f7502d1..c90519fd3fb9a8e 100644
--- a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
@@ -19,4 +18,4 @@
 
    ![Connector appearing in the UI after cloudflared has run](~/assets/images/cloudflare-one/connections/connect-apps/connector.png)
 
-8. Select **Next**.
\ No newline at end of file
+8. Select **Next**.
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
index 0f7caefc4aa0c56..4836708c394928a 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Create a Cloudflare Tunnel in Cloudflare One and run the tunnel on the {props.one}.
 
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
index 2f6208021fb86bc..061651ac15df2a8 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
@@ -11,17 +11,17 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 2.  In the **CIDR** tab, enter the **Private IP address** of your {props.resourceName} (for example, <code>{props.exampleIp}</code>). You can expand the IP range later if necessary.
 3.  In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through the Cloudflare One Client. For example, if you are using Split Tunnels in **Exclude** mode, delete <code>{props.splitTunnelCidr}</code>. We recommend re-adding the IPs that are not explicitly used by your {props.resourceName}.
 
-        To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
-
-        <SubtractIPCalculator
-        	client:load
-        	defaults={{
-        		base: props.splitTunnelCidr,
-        		subtract: props.calcExclude
-        	}}
-        />
-
-        Add the results back to your Split Tunnel Exclude mode list.
+    To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
+    
+    <SubtractIPCalculator
+    	client:load
+    	defaults={{
+    		base: props.splitTunnelCidr,
+    		subtract: props.calcExclude
+    	}}
+    />
+    
+    Add the results back to your Split Tunnel Exclude mode list.
 
 4.  To test on a user device:
     1. [Log in to the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/).
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
index 9e70a1198bb9fb7..170049a7ac5f7c8 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Published applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) allow anyone on the Internet to connect to HTTP resources hosted on your virtual private cloud (VPC). To add a published application for your Cloudflare Tunnel:
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
index 4f15318c29c1162..6980de61dec14cf 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
@@ -24,15 +24,30 @@ params:
 
    ```json
    {
-     "tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
-     "connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
-     "connections": [
-       { "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167"},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.113", "index": 1},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.47", "index": 2},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.73", "index": 3}
-     ],
-     "icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
+   	"tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
+   	"connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
+   	"connections": [
+   		{ "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167" },
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.200.113",
+   			"index": 1
+   		},
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.192.47",
+   			"index": 2
+   		},
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.200.73",
+   			"index": 3
+   		}
+   	],
+   	"icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
    }
    ```
 
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
index 35a23d38040988e..af11a9afb297c8f 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
@@ -8,18 +8,18 @@ params:
 
 The `cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.
 
-| File name                | Description                                                                                                                                                  | Instance  |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
+| File name                | Description                                                                              | Instance  |
+| ------------------------ | ---------------------------------------------------------------------------------------- | --------- |
 | `cli-configuration.json` | <a href={props.runParametersURL}>Tunnel run parameters</a> used when starting the tunnel | diagnosee |
-| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                                                    | diagnosee |
-| `configuration.json`     | Tunnel configuration parameters                                                                                                                              | diagnosee |
-| `goroutine.pprof`        | goroutine profile made available by `pprof`                                                                                                                  | diagnosee |
-| `heap.pprof`             | heap profile made available by `pprof`                                                                                                                       | diagnosee |
-| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis               | diagnosee |
-| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                          | diagnoser |
-| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                           | diagnoser |
-| `systeminformation.json` | Operating system information and resource usage                                                                                                              | diagnosee |
-| `task-result.json`       | Result of each diagnostic task                                                                                                                               | diagnoser |
-| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                                                                                                  | diagnosee |
+| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                          | diagnosee |
+| `configuration.json`     | Tunnel configuration parameters                                                          | diagnosee |
+| `goroutine.pprof`        | goroutine profile made available by `pprof`                                              | diagnosee |
+| `heap.pprof`             | heap profile made available by `pprof`                                                   | diagnosee |
+| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis       | diagnosee |
+| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                      | diagnoser |
+| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                       | diagnoser |
+| `systeminformation.json` | Operating system information and resource usage                                          | diagnosee |
+| `task-result.json`       | Result of each diagnostic task                                                           | diagnoser |
+| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                              | diagnosee |
 
 [^1]: If the log file is blank, you may need to <a href={props.loglevelURL}>set `--loglevel` to `debug`</a> when you start the tunnel. The `--loglevel` parameter is only required if you ran the tunnel from the CLI using a `cloudflared tunnel run` command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes.
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
index 2f2327ca51fb9e4..e8c007b9d69d74c 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Published applications inherit the Cloudflare settings for their hostname, including [cache rules](/cache/how-to/cache-rules/), [WAF rules](/waf/), and other [Rules](/rules/) configurations. You can change these settings for each hostname in the [Cloudflare dashboard](https://dash.cloudflare.com/).
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
index f3c26351bc152ee..6e023ea0564f577 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you create a tunnel, Cloudflare generates a subdomain at `<UUID>.cfargotunnel.com`. You point a CNAME record at this subdomain to route traffic from your hostname to the tunnel.
diff --git a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
index ad172f22cfae0ee..5fb221e26749de9 100644
--- a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Tunnel supports gRPC traffic via [private subnet routing](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/). Public hostname deployments are not currently supported.
diff --git a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
index da5faccbdab0cc8..91d158683723dd9 100644
--- a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
@@ -5,13 +5,16 @@
 import { Details } from "~/components";
 
 <Details header="Hostname format restrictions">
-- **Character limit:** Must be less than 255 characters.
-- **Supported wildcards:** A single wildcard (`*`) is allowed, and it must represent a full DNS label.
-			Example: `*.internal.local`
-- **Unsupported wildcards:** The following wildcard formats are not supported:
-		- Partial wildcards such as `*-dev.internal.local` or `dev-*.internal.local`.
-		- Wildcards in the middle, such as `foo*bar.internal.local` or `foo.*.internal.local`.
-		- Multiple wildcards in the hostname, such as `*.*.internal.local`.
-- **Wildcard trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`) is assumed. For example, `*.internal.local` is saved as `internal.local` but will match all subdomains at the wildcard level (covers `foo.internal.local` but not `foo.bar.internal.local`).
-- **Dot trimming:** Leading and ending dots (`.`) are allowed but trimmed off.
+	- **Character limit:** Must be less than 255 characters. - **Supported
+	wildcards:** A single wildcard (`*`) is allowed, and it must represent a full
+	DNS label. Example: `*.internal.local` - **Unsupported wildcards:** The
+	following wildcard formats are not supported: - Partial wildcards such as
+	`*-dev.internal.local` or `dev-*.internal.local`. - Wildcards in the middle,
+	such as `foo*bar.internal.local` or `foo.*.internal.local`. - Multiple
+	wildcards in the hostname, such as `*.*.internal.local`. - **Wildcard
+	trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`)
+	is assumed. For example, `*.internal.local` is saved as `internal.local` but
+	will match all subdomains at the wildcard level (covers `foo.internal.local`
+	but not `foo.bar.internal.local`). - **Dot trimming:** Leading and ending dots
+	(`.`) are allowed but trimmed off.
 </Details>
diff --git a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
index 221f41fda76b716..660cd5d5f759ab9 100644
--- a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -47,4 +46,4 @@ import { Tabs, TabItem } from "~/components";
         	docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <TUNNEL_TOKEN>
         	```
 
-</TabItem>  </Tabs>
\ No newline at end of file
+</TabItem>  </Tabs>
diff --git a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
index 3e1b6567d49585d..4fdc32d904e2241 100644
--- a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
@@ -12,16 +12,16 @@ Tunnel permissions determine who can run and manage a Cloudflare Tunnel. Two fil
 
 Refer to the table below for a comparison between the two files and the purposes for which they are intended.
 
-|                         | Account certificate                                                          | Tunnel credential                                         |
-| ----------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------- |
-| **File name**           | `cert.pem`                                                                   | `<TUNNEL-UUID>.json`                                      |
-| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account | Authenticates the tunnel it is associated with            |
-| **Scope**               | Account-wide                                                                 | Tunnel-specific                                           |
-| **File type**           | `.pem`                                                                       | `.json`                                                   |
-| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                    | <a href={props.defaultDirectoryURL}>Default directory</a> |
-| **Issued when running** | `cloudflared tunnel login`                                                   | `cloudflared tunnel create <NAME>`                        |
-| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate)  | Does not expire                                           |
-| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)         | Run a tunnel. Create a config file.                       |
+|                         | Account certificate                                                                                        | Tunnel credential                                         |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| **File name**           | `cert.pem`                                                                                                 | `<TUNNEL-UUID>.json`                                      |
+| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account                               | Authenticates the tunnel it is associated with            |
+| **Scope**               | Account-wide                                                                                               | Tunnel-specific                                           |
+| **File type**           | `.pem`                                                                                                     | `.json`                                                   |
+| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                                                  | <a href={props.defaultDirectoryURL}>Default directory</a> |
+| **Issued when running** | `cloudflared tunnel login`                                                                                 | `cloudflared tunnel create <NAME>`                        |
+| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate) | Does not expire                                           |
+| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)                                       | Run a tunnel. Create a config file.                       |
 
 ## Tunnel ownership
 
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
index 6c50a4d38d46d4a..c3f3293198255e7 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
@@ -9,8 +9,8 @@ You can filter logs by event type (`--event`), event level (`--level`), or sampl
 cloudflared tail --level debug <UUID>
 ```
 
-| Flag         | Description                                                                                                                                                                                           | Allowed values                            | Default value |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
-| `--event`    | Filter by the type of event / request.                                                                                                                                                                | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
+| Flag         | Description                                                                                                                         | Allowed values                            | Default value |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
+| `--event`    | Filter by the type of event / request.                                                                                              | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
 | `--level`    | Return logs at this level and above. Works independently of the <a href={props.loglevelURL}>`--loglevel`</a> setting on the server. | `debug`, `info`, `warn`, `error`, `fatal` | `debug`       |
-| `--sampling` | Sample a fraction of the total logs.                                                                                                                                                                  | Number from `0.0` to `1.0`                | `1.0`         |
+| `--sampling` | Sample a fraction of the total logs.                                                                                                | Number from `0.0` to `1.0`                | `1.0`         |
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
index 9199c7ed894a76f..7e5b276368ef811 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
@@ -3,7 +3,6 @@
 
 import { GlossaryTooltip } from "~/components";
 
-
 Dashboard log streams are only available for <GlossaryTooltip term="remotely-managed tunnel">remotely-managed tunnels</GlossaryTooltip>. To stream tunnel logs from the dashboard:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
index 323c86b55d57992..c5d8a1638544701 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
@@ -12,4 +12,3 @@ To enable logs, <a href={props.runParametersURL}>run the tunnel</a> using the `-
 ```sh
 cloudflared tunnel --loglevel info --logfile cloudflared.log run <UUID>
 ```
-
diff --git a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
index 4e0fc2c84e7e66e..bdc546346c31fc1 100644
--- a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
@@ -19,7 +19,7 @@
 | `cloudflared_tunnel_tunnel_authenticate_success`    | Number of successful tunnel authentication events.                                                         | COUNTER |                                            |
 | `cloudflared_tunnel_tunnel_register_success`        | Number of successful tunnel registrations.                                                                 | COUNTER | `rpcName`                                  |
 | `cloudflared_udp_active_sessions`                   | Concurrent number of UDP sessions that are being proxied to any origin.                                    | GAUGE   |                                            |
-| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER   |                                            |
+| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER |                                            |
 | `coredns_panics_total`                              | Number of panics.                                                                                          | COUNTER |                                            |
 | `quic_client_closed_connections`                    | Number of connections that have been closed.                                                               | COUNTER |                                            |
 | `quic_client_latest_rtt`                            | Latest round-trip time (RTT) measured on a connection.                                                     | GAUGE   | `conn_index`                               |
diff --git a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
index 000cf30ab14fdcb..1b6b39f6f1a5fda 100644
--- a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
@@ -132,8 +132,8 @@ When `true`, Happy Eyeballs is disabled.
 `cloudflared` starts a proxy server to translate HTTP traffic into TCP when proxying, for example, SSH or RDP.
 This configures what type of proxy will be started. Valid options are:
 
-* `""` for the regular proxy
-* `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
+- `""` for the regular proxy
+- `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
 
 ### proxyAddress
 
diff --git a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
index 2fd27a10bd6f00a..53e2484f9439265 100644
--- a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
\ No newline at end of file
+You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
diff --git a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
index 9bed10dd3b8e8ea..b0e9a72f30f6267 100644
--- a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
@@ -6,19 +6,19 @@ params:
 
 The table below lists the service types you can route to a public hostname. Non-HTTP services require [installing `cloudflared` on the client](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/) for end users to connect.
 
-| Service type | Description | Example `service` value |
-| ------------ | ----------- | ----------------------- |
-| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP. | `http://localhost:8000` |
-| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates. | `https://localhost:8000` |
-| UNIX         | Same as HTTP, but uses a Unix socket. | `unix:/home/production/echo.sock` |
-| UNIX + TLS   | Same as HTTPS, but uses a Unix socket. | `unix+tls:/home/production/echo.sock` |
-| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead. | `tcp://localhost:2222` |
-| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22` |
-| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/). | `rdp://localhost:3389` |
-| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access). | `smb://localhost:445` |
-| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code. | `http_status:404` |
-| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address. | `bastion` |
-| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only). | `hello_world` |
+| Service type | Description                                                                                                                                                                                                                                                                                                                                                    | Example `service` value               |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
+| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP.                                                                                                                                                                                                                                                                                           | `http://localhost:8000`               |
+| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates.                                                                                                                                                                               | `https://localhost:8000`              |
+| UNIX         | Same as HTTP, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                          | `unix:/home/production/echo.sock`     |
+| UNIX + TLS   | Same as HTTPS, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                         | `unix+tls:/home/production/echo.sock` |
+| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead.                     | `tcp://localhost:2222`                |
+| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22`                  |
+| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/).                                                                                                                                    | `rdp://localhost:3389`                |
+| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access).                                                                                                                     | `smb://localhost:445`                 |
+| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code.                                                                                                                                                                                                                                                                                                        | `http_status:404`                     |
+| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address.                                                                                                                                                                                                                                                                             | `bastion`                             |
+| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only).                                                                                                                                                                                                                  | `hello_world`                         |
 
 ## IPv6 service addresses
 
diff --git a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
index 05449ecd0346b32..effd28c88ed8811 100644
--- a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
@@ -171,9 +171,9 @@ Specifies the path to a <a href={props.configurationFileURL}>configuration file<
 Requires `cloudflared` version 2025.7.0 or later.
 :::
 
-| Syntax                                                                    | Environment Variable        |
-| ------------------------------------------------------------------------- | --------------------------- |
-| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>`    | `TUNNEL_DNS_RESOLVER_ADDRS` |
+| Syntax                                                                 | Environment Variable        |
+| ---------------------------------------------------------------------- | --------------------------- |
+| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>` | `TUNNEL_DNS_RESOLVER_ADDRS` |
 
 Specifies custom DNS resolver addresses for `cloudflared` to use instead of the host machine's default resolvers. Each address must be in `ip:port` format — providing an IP address without a port will cause `cloudflared` to fail to start. You can specify multiple resolvers by repeating the flag. For example,
 
diff --git a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
index 0a7bafc56310b6d..a0e19ac3f17e0f6 100644
--- a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
@@ -2,9 +2,9 @@
 {}
 ---
 
-| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
-|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
-| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel).                           |
-| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
-| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
+| Status       | Meaning                                                                                                                                                                                                                                                                                                                                | Recommended Action                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Healthy**  | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                                                                                                                                                                                                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| **Inactive** | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                                                                                                                                                                                                   | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel). |
+| **Down**     | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                                                                                                                                                                                                       | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                                                                                           |
+| **Degraded** | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic. | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                                            |
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
index a8aee795acbec88..a868e4cec7f75c4 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
@@ -16,4 +16,4 @@ warp-cli target list
 ├──────────────────────────────────────┼──────────┼───────┼───────────────────────┼──────────────────────┼────────────┤
 │ 01943cff-6130-7989-8bff-cbc02b59a2b1 │ SSH      │ 80    │ hostname: az-target   │ 172.16.0.0 (b1net)   │ alice, bob │
 ╰──────────────────────────────────────┴──────────┴───────┴───────────────────────┴──────────────────────┴────────────╯
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
index 612d5ce51183c58..9fd296c4c4257a5 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
@@ -3,42 +3,42 @@ params:
   - one
 ---
 
-import { Markdown, Details, Tabs, TabItem} from "~/components";
+import { Markdown, Details, Tabs, TabItem } from "~/components";
 import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 
 By default, WARP excludes traffic bound for [RFC 1918 space](https://datatracker.ietf.org/doc/html/rfc1918), which are IP addresses typically used in private networks and not reachable from the Internet. In order for the Cloudflare One Client to send traffic to your <Markdown text={props.one}/>, you must configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that the IP/CIDR of your <Markdown text={props.one}/> routes through the Cloudflare One Client.
 
 1. First, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include** mode.
 2. Edit your Split Tunnel routes depending on the mode:
-  	<Tabs> <TabItem label="Exclude IPs and domains">
-
-		If you are using **Exclude** mode:
-
-		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
-
-		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
-
-		You can use the following calculator to determine which IP addresses to re-add:
-
-			<SubtractIPCalculator
-				client:load
-				defaults={{
-					base: "172.16.0.0/12",
-					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
-				}}
-			/>
-		<Details header="Calculator instructions" open = {true}>
-		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
-		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
-		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
-		</Details>
-
-		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
-
-
-   </TabItem> <TabItem label="Include IPs and domains">
-		If you are using **Include** mode:
-		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
-		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
-
-   </TabItem> </Tabs>
+   <Tabs> <TabItem label="Exclude IPs and domains">
+   
+   		If you are using **Exclude** mode:
+   
+   		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
+   
+   		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
+   
+   		You can use the following calculator to determine which IP addresses to re-add:
+   
+   			<SubtractIPCalculator
+   				client:load
+   				defaults={{
+   					base: "172.16.0.0/12",
+   					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
+   				}}
+   			/>
+   		<Details header="Calculator instructions" open = {true}>
+   		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
+   		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
+   		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
+   		</Details>
+   
+   		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
+   
+   
+      </TabItem> <TabItem label="Include IPs and domains">
+   		If you are using **Include** mode:
+   		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
+   		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
+   
+      </TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
index 88879da57d19361..aed1dc57c84005a 100644
--- a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-It may take up to 10 minutes for newly updated settings to propagate to devices.
\ No newline at end of file
+It may take up to 10 minutes for newly updated settings to propagate to devices.
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
index 885e29755b6d368..cc4a288a0d916a4 100644
--- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105`
diff --git a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
index 0f9cabfed41c022..dfc8ccca98273c3 100644
--- a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
+++ b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components"
+import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components";
 
 <Details header="Certificate requirements">
-   <Render file="byo-ca-mtls-cert-requirements" product="ssl" />
+	<Render file="byo-ca-mtls-cert-requirements" product="ssl" />
 </Details>
 
 To check for an mTLS certificate:
@@ -81,4 +80,4 @@ To check for an mTLS certificate:
 
 5. On your device, add the client certificate to the [system keychain](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#test-in-the-browser).
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
index 565425c2df7ac87..4c9ebbf7bef15c0 100644
--- a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
+++ b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 1. [Download](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and install the Cloudflare One Agent app.
 2. Launch the Cloudflare One Agent app.
diff --git a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
index 0c7940a4582c545..18e8ab3a2beb429 100644
--- a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
+++ b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
@@ -8,4 +8,4 @@ import { GlossaryTooltip } from "~/components";
 
 If your DNS server can be configured to connect to a Cloudflare <GlossaryTooltip term="on-ramp">on-ramp</GlossaryTooltip>, Cloudflare recommends using Gateway Resolver policies rather than Local Domain Fallback. Gateway Resolver policies provide more visibility by allowing you to log and review DNS traffic.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
index 65cc25e27b64395..cb7f6b23c978461 100644
--- a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
+++ b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
@@ -12,4 +12,4 @@ The output will look something like:
 
 ```txt
 SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8662
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
index 77582cb8d22f063..b54554c4a3ae864 100644
--- a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
+++ b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
@@ -6,4 +6,4 @@ To manually refresh your Cloudflare Access session and update your group informa
 
 `https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/refresh-identity`
 
-Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
\ No newline at end of file
+Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
diff --git a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
index 9df1996bb09d5b3..81e72731b5d5abf 100644
--- a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
+++ b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
@@ -1,13 +1,16 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Refer to our [managed deployment instructions](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/) and create a `.plist`, `mdm.xml`, or `.msi` policy file based on your organization's software management tool.
 
-<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we recommend that your policy file only contain the organization name and potentially the onboarding flag, [relying on the dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/) to configure the remaining device settings.
+<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we
+recommend that your policy file only contain the organization name and
+potentially the onboarding flag, [relying on the
+dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/)
+to configure the remaining device settings.
 
 ```xml
 <dict>
diff --git a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
index 40d23df27682b3c..324b01831d1d350 100644
--- a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
+++ b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 The OS version must be specified as a valid [Semver](https://semver.org/). For example, if your device is running OS version `1.2`, you must enter `1.2.0`.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
index e7611c019caec78..591e817aebaf97a 100644
--- a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
+++ b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
@@ -22,4 +22,4 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
 
 <Render file="warp/managed-networks-sha-256" product="cloudflare-one"/>
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
index 84e14c59cd4278e..bee309cd06764e9 100644
--- a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
+++ b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
@@ -115,9 +115,9 @@ Avoid vague descriptions and include scenario, timestamps, and steps taken to tr
   <>
     <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p>
 
-    <p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
+<p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
 
-    <p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
+<p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
 
   </>
 ) : props.tunnelMode ? (
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
index d2177c9f8dc51ca..3a4377564d2f4ff 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
-|                       |                                                                               |
-| --------------------- | ----------------------------------------------------------------------------- |
-| **OS version**        | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
-| **Processor**         | AMD64 / x86-64 or ARM64 / AArch64                                   |
-| **HD space**          | 75 MB                                                                         |
-| **Memory**            | 35 MB                                                                         |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^2] |
+|                            |                                                                                                               |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| **OS version**             | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
+| **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                                                             |
+| **HD space**               | 75 MB                                                                                                         |
+| **Memory**                 | 35 MB                                                                                                         |
+| **Network interface type** | Wi-Fi or LAN                                                                                                  |
+| **MTU**                    | 1381 bytes recommended [^2]                                                                                   |
 
 [^1]: On RHEL 9 and later, enable the [Extra Packages for Enterprise Linux (EPEL)](https://docs.fedoraproject.org/en-US/epel/) repository (`sudo dnf install epel-release`) before installing `cloudflare-warp`. EPEL provides dependencies required by the client UI.
 
-[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
index 48053016ac259ca..8742afdde17d699 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-|                       |                                                   |
-| --------------------- | ------------------------------------------------- |
-| **OS version**        | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+                                 |
-| **Processor**         | Intel or M series   |
-| **HD space**          | 75 MB                                             |
-| **Memory**            | 35 MB                                             |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^1] |
+|                            |                                                                    |
+| -------------------------- | ------------------------------------------------------------------ |
+| **OS version**             | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+ |
+| **Processor**              | Intel or M series                                                  |
+| **HD space**               | 75 MB                                                              |
+| **Memory**                 | 35 MB                                                              |
+| **Network interface type** | Wi-Fi or LAN                                                       |
+| **MTU**                    | 1381 bytes recommended [^1]                                        |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
index 7f1dfe65c468ba2..8c0f46bf3c6c5ae 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
-|                            |                                                   |
-| -------------------------- | ------------------------------------------------- |
-| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11                           |
+|                            |                                                                      |
+| -------------------------- | -------------------------------------------------------------------- |
+| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11 |
 | **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                    |
-| **.NET Framework version** | 4.7.2 or later                                    |
-| **HD space**               | 184 MB                                            |
-| **Memory**                 | 3 MB                                              |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^1] |
+| **.NET Framework version** | 4.7.2 or later                                                       |
+| **HD space**               | 184 MB                                                               |
+| **Memory**                 | 3 MB                                                                 |
+| **Network interface type** | Wi-Fi or LAN                                                         |
+| **MTU**                    | 1381 bytes recommended [^1]                                          |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
index 168c80b4c6089fd..f13c7f8da379164 100644
--- a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
+++ b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
@@ -1,19 +1,17 @@
 ---
 {}
-
 ---
 
 Perform these steps in the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Team & Resources** > **Devices** > **Device profiles** > **General profiles**.
 
 1. Set your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) to **Exclude IPs and domains**.
 2. [Add the following entries](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to your Split Tunnel Exclude list:
-
-   * Private IP address range exposed by your third-party VPN client. For example,
+   - Private IP address range exposed by your third-party VPN client. For example,
      | Selector | Value |
      | -------- | ----- |
-     | IP Address   | `172.16.0.0/12` |
+     | IP Address | `172.16.0.0/12` |
      |
-   * Server that your third-party VPN client connects to. For example,
+   - Server that your third-party VPN client connects to. For example,
      | Selector | Value |
      | -------- | ----- |
-     | Domain   | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
+     | Domain | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
diff --git a/src/content/partials/cloudflare-one/warp/warp-modes.mdx b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
index ed493a08759ce6b..fe4dbbfb81edeea 100644
--- a/src/content/partials/cloudflare-one/warp/warp-modes.mdx
+++ b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
@@ -4,8 +4,8 @@
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                   | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                          | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/partials/containers/instance-types.mdx b/src/content/partials/containers/instance-types.mdx
index 705a0f3c5970555..0c7e58181689b5f 100644
--- a/src/content/partials/containers/instance-types.mdx
+++ b/src/content/partials/containers/instance-types.mdx
@@ -1,8 +1,8 @@
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------  | ----  |
+| ------------- | ---- | ------- | ----- |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
 | standard-2    | 1    | 6 GiB   | 12 GB |
 | standard-3    | 2    | 8 GiB   | 16 GB |
-| standard-4    | 4    | 12 GiB  | 20 GB |
\ No newline at end of file
+| standard-4    | 4    | 12 GiB  | 20 GB |
diff --git a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
index ea530442f741999..b0f0987a817dc7c 100644
--- a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
+++ b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
@@ -1,6 +1,6 @@
 ---
 params:
-- product
+  - product
 ---
 
 {props.product} a subset of SQLite extensions for added functionality, including:
@@ -9,4 +9,4 @@ params:
 - [JSON extension](https://www.sqlite.org/json1.html) for JSON functions and operators.
 - [Math functions](https://sqlite.org/lang_mathfunc.html).
 
-Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
\ No newline at end of file
+Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
diff --git a/src/content/partials/d1/generate-d1-api-token.mdx b/src/content/partials/d1/generate-d1-api-token.mdx
index 700bee2bfb563e9..2c13c1ba8b60e3d 100644
--- a/src/content/partials/d1/generate-d1-api-token.mdx
+++ b/src/content/partials/d1/generate-d1-api-token.mdx
@@ -21,4 +21,4 @@ import { Steps, DashButton } from "~/components";
 </Steps>
 
 - Refer to [Create API token](/fundamentals/api/get-started/create-token/) for more information on creating API tokens through the Cloudflare dashboard.
-- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
\ No newline at end of file
+- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
index 5c559f1e70ee53e..18b1bdc17d3c358 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
\ No newline at end of file
+Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
index 9a44876d0af0d32..2cba0a9f642281c 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
\ No newline at end of file
+[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
index 1393b132f8df703..54dbbb22ddac8c5 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
@@ -6,4 +6,4 @@
 Advanced TCP and DNS Protection systems are automatically enabled in `Monitor` mode with the default thresholds for new Magic Transit customers and their [authorized prefixes](/magic-transit/how-to/advertise-prefixes/).
 
 Magic Transit customers can also enable the Advanced DDoS systems when the prefixes are ready, change the sensitivity level, or adjust the thresholds by contacting their account team.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
index 3b2d7e3139d2b5a..bd07b8b43cb7890 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
\ No newline at end of file
+Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
index 2c4124f1e232eee..e6d886f65e51b05 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
\ No newline at end of file
+[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
diff --git a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
index a66db33424c00e8..4a2843a4d9281c2 100644
--- a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
+++ b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DDoS reports and DDoS alerts are independent: DDoS reports will include information about any attacks for which you received DDoS alerts.
diff --git a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
index b98f5547923a93c..e752ea9ae03f6d5 100644
--- a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
+++ b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 :::caution[Important]
 
-
 Prefixes in the allowlist will be vulnerable to <GlossaryTooltip term="IP spoofing">IP spoofing</GlossaryTooltip> attacks. If an attacker can guess the source IP addresses you have allowlisted, their packets will be allowlisted.
 
-
 :::
diff --git a/src/content/partials/ddos-protection/atp-filter-definition.mdx b/src/content/partials/ddos-protection/atp-filter-definition.mdx
index 12d6e288ceadf95..523d17768055849 100644
--- a/src/content/partials/ddos-protection/atp-filter-definition.mdx
+++ b/src/content/partials/ddos-protection/atp-filter-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
\ No newline at end of file
+A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
diff --git a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
index 856694a96d0c99c..a961f5d75580c97 100644
--- a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
+++ b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/ddos-protection/create-notification.mdx b/src/content/partials/ddos-protection/create-notification.mdx
index d198471ab167dd0..8a4ea2addd089cb 100644
--- a/src/content/partials/ddos-protection/create-notification.mdx
+++ b/src/content/partials/ddos-protection/create-notification.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
index 6b49ed03060ba7f..b78cd219dfc2f48 100644
--- a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
+++ b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
-| OSI Layer       | Ruleset / Feature                                                                                                      | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| --------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| L3/4            | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                                     | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
-| L3/4            | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1]               | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| L7 (DNS)        | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1]               | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| L7 (HTTP/S)     | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                                 | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                  |
+| OSI Layer   | Ruleset / Feature                                                                                        | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ----------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| L3/4        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                       | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
+| L3/4        | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1] | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| L7 (DNS)    | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1] | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| L7 (HTTP/S) | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                   | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 
 [^1]: Available to Magic Transit customers.
diff --git a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
index 6bd97998baead60..ebb6dc3d1dbdf51 100644
--- a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
+++ b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
\ No newline at end of file
+Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
index ffcd4438247f2b1..a85897a7a575038 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details, Render, Steps, DashButton } from "~/components"
+import { Details, Render, Steps, DashButton } from "~/components";
 
 <Steps>
   1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
@@ -35,4 +35,4 @@ import { Details, Render, Steps, DashButton } from "~/components"
       - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
       :::
   8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
index b32f56a8b16d56e..03910e37301db8a 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Create multiple rules in the `ddos_l7` phase entry point ruleset to define different overrides for different sets of incoming requests. Set each rule expression according to the traffic whose HTTP DDoS protection you wish to customize.
 
-Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
\ No newline at end of file
+Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
index 21e80e11b8adc25..9b1cf47c23bbb2e 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Highly targeted rules for mitigating DDoS attacks with a high confidence rate. These rules are read-only — you cannot override their sensitivity level or action.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
index 3168c30b815a38a..fcc5ea826e263dc 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The managed ruleset includes some read-only rules that you cannot override.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
index 6f4476224899bd4..0c3e48d1a2ab57c 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 API property name: `"sensitivity_level"`.
@@ -11,15 +10,15 @@ The available sensitivity levels are:
 
 | UI value          | API value   |
 | ----------------- | ----------- |
-| *High*            | `"default"` |
-| *Medium*          | `"medium"`  |
-| *Low*             | `"low"`     |
-| *Essentially Off* | `"eoff"`    |
+| _High_            | `"default"` |
+| _Medium_          | `"medium"`  |
+| _Low_             | `"low"`     |
+| _Essentially Off_ | `"eoff"`    |
 
-The default sensitivity level is *High*.
+The default sensitivity level is _High_.
 
-In most cases, when you select the *Essentially Off* sensitivity level the rule will not trigger for any of the selected actions, including *Log*. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
+In most cases, when you select the _Essentially Off_ sensitivity level the rule will not trigger for any of the selected actions, including _Log_. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
 
-*Essentially Off* means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+_Essentially Off_ means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
 
-**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
\ No newline at end of file
+**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
index 72d2abd12cf1632..2b38abe2e55abcf 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Rules used for testing the detection, mitigation, and alerting capabilities of Cloudflare's DDoS protection products.
diff --git a/src/content/partials/ddos-protection/override-example.mdx b/src/content/partials/ddos-protection/override-example.mdx
index 4e8d68a92360f5f..c25df1b5a153d19 100644
--- a/src/content/partials/ddos-protection/override-example.mdx
+++ b/src/content/partials/ddos-protection/override-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Example
@@ -14,33 +13,33 @@ A DDoS managed ruleset contains the following managed rules:
 The following ruleset overrides have been configured:
 
 - **Ruleset override A**
-   - **Managed rule 1** is set to `block`
+  - **Managed rule 1** is set to `block`
 - **Ruleset override B**
-   - The action of the entire ruleset (or *all managed rules*) is set to `Managed Challenge`
-   - **Managed rule 1** is set to `log`
-   - **Managed rule 2** is set to `log`
+  - The action of the entire ruleset (or _all managed rules_) is set to `Managed Challenge`
+  - **Managed rule 1** is set to `log`
+  - **Managed rule 2** is set to `log`
 - **Ruleset override C**
-   - **Managed rule 3** is set to `log`
+  - **Managed rule 3** is set to `log`
 
-### Use case 
+### Use case
 
 A DDoS attack was detected on **managed rules 1**, **2**, and **3**, and has generated a mitigation rule.
 
-- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules. 
+- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules.
 
 - **Managed rule 2** does not match **ruleset override A**, so Cloudflare proceeds to **ruleset override B**. <br /> **Ruleset override B** matches both all managed rules and **managed rule 2**, but specificity takes precedence. It does not `challenge` and instead proceeds with `log` since it matches the most specific managed rule.
 
-- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets *all managed rules* to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
+- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets _all managed rules_ to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
 
 An additional dimension to take into account is Cloudflare’s DDoS systems will apply a given rule override only if its conditions are met — which includes the Sensitivity level. So, while it needs to match and modify the correct managed rule (or everything in the case of all managed rules above), it also has to meet the specified Sensitivity level of the rule.
 
 - **Rule override A**
-   - *All managed rules* are set to `challenge` at low sensitivity
+  - _All managed rules_ are set to `challenge` at low sensitivity
 
 - **Rule override B**
-   - **Managed rule 1** is set to `log` at default sensitivity
+  - **Managed rule 1** is set to `log` at default sensitivity
 
 You receive a small attack below the threshold for low sensitivity, but above the threshold for high sensitivity on **managed rule 1**.
 
-- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate. 
-- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
\ No newline at end of file
+- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate.
+- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
diff --git a/src/content/partials/ddos-protection/override-logic.mdx b/src/content/partials/ddos-protection/override-logic.mdx
index b9ff54257029827..a4cde6e1c07ac0b 100644
--- a/src/content/partials/ddos-protection/override-logic.mdx
+++ b/src/content/partials/ddos-protection/override-logic.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 When Cloudflare's DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection managed ruleset. Each mitigation rule is generated from a single managed rule.
 
-All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches. 
+All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches.
 
-You can create only one ruleset override that can contain one or multiple rule overrides. 
+You can create only one ruleset override that can contain one or multiple rule overrides.
 
 :::note
 Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) add-on can create up to 10 ruleset overrides.
@@ -15,4 +14,4 @@ Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanc
 
 A rule override instructs the DDoS system on the action it should take against the attack according to its matching managed rule.
 
-However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override. 
\ No newline at end of file
+However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override.
diff --git a/src/content/partials/dmarc-management/domain-spoofing.mdx b/src/content/partials/dmarc-management/domain-spoofing.mdx
index f67efe27497fedf..789d26bbd41acbb 100644
--- a/src/content/partials/dmarc-management/domain-spoofing.mdx
+++ b/src/content/partials/dmarc-management/domain-spoofing.mdx
@@ -10,8 +10,6 @@ Without email authentication records, anyone can send email that appears to come
 
 :::note
 
-
 For additional background on email security records, refer to the [introductory blog post](https://blog.cloudflare.com/tackling-email-spoofing/).
 
-
 :::
diff --git a/src/content/partials/dns/a-aaaa-definition.mdx b/src/content/partials/dns/a-aaaa-definition.mdx
index 382543d232d0715..7871b0c522c087c 100644
--- a/src/content/partials/dns/a-aaaa-definition.mdx
+++ b/src/content/partials/dns/a-aaaa-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [A and AAAA records](https://www.cloudflare.com/learning/dns/dns-records/dns-a-record/) map a domain name to one or multiple IPv4 or IPv6 address(es).
diff --git a/src/content/partials/dns/acns-tcns-byoip.mdx b/src/content/partials/dns/acns-tcns-byoip.mdx
index 0184972c95cb464..d54a916972d3a46 100644
--- a/src/content/partials/dns/acns-tcns-byoip.mdx
+++ b/src/content/partials/dns/acns-tcns-byoip.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::note
 
diff --git a/src/content/partials/dns/acns-tcns-conditions.mdx b/src/content/partials/dns/acns-tcns-conditions.mdx
index 910dee1af8bb028..8ffad8ef38a32d5 100644
--- a/src/content/partials/dns/acns-tcns-conditions.mdx
+++ b/src/content/partials/dns/acns-tcns-conditions.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2;;param3
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-* {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
-* [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
+- {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
+- [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
diff --git a/src/content/partials/dns/acns-tcns-intro.mdx b/src/content/partials/dns/acns-tcns-intro.mdx
index d75bd29c06d9035..4089262cc29499c 100644
--- a/src/content/partials/dns/acns-tcns-intro.mdx
+++ b/src/content/partials/dns/acns-tcns-intro.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2;;param3;;param4;;param5
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 {props.one} custom nameservers ({props.two}CNS) allow you to define {props.three}-level custom nameservers and use them for different {props.four} within a Cloudflare {props.five}.
 
diff --git a/src/content/partials/dns/aname-alias-callout.mdx b/src/content/partials/dns/aname-alias-callout.mdx
index 6751169d5c78778..e958df71d713e10 100644
--- a/src/content/partials/dns/aname-alias-callout.mdx
+++ b/src/content/partials/dns/aname-alias-callout.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's [CNAME flattening](/dns/cname-flattening/)[^1] allows you to create CNAME records at your [zone apex](/dns/concepts/#zone-apex), removing the need for those other record types.
 
-[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
\ No newline at end of file
+[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
diff --git a/src/content/partials/dns/api-field-definitions.mdx b/src/content/partials/dns/api-field-definitions.mdx
index af7ea90d28101b2..2629350da26de28 100644
--- a/src/content/partials/dns/api-field-definitions.mdx
+++ b/src/content/partials/dns/api-field-definitions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For field definitions, refer to the [API documentation](/api/resources/dns/subresources/records/methods/create/) (visible once you select the record type under the request body specification).
diff --git a/src/content/partials/dns/cname-definition.mdx b/src/content/partials/dns/cname-definition.mdx
index ac977bc79ea7fe9..324c92c3d9865a3 100644
--- a/src/content/partials/dns/cname-definition.mdx
+++ b/src/content/partials/dns/cname-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [CNAME records](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/) map a domain name to another (canonical) domain name. They can be used to resolve other record types present on the target domain name.
diff --git a/src/content/partials/dns/cname-flattening-callout.mdx b/src/content/partials/dns/cname-flattening-callout.mdx
index 030fec534c89c49..000688fb842401b 100644
--- a/src/content/partials/dns/cname-flattening-callout.mdx
+++ b/src/content/partials/dns/cname-flattening-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If a CNAME target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the CNAME record itself will not be returned directly.
diff --git a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
index 2d6ccf3c0e1d1b4..6c9b25d037c6bfd 100644
--- a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
+++ b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Subdomain setup]
 If you also use subdomain setup[^1], consider the [available combinations](/dns/zone-setups/subdomain-setup/setup/#available-setups) and whether your zone conversion could have any implications.
 :::
 
-[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
\ No newline at end of file
+[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
diff --git a/src/content/partials/dns/dns-errors-ts-action.mdx b/src/content/partials/dns/dns-errors-ts-action.mdx
index 9dfa15e76d1dfa6..4d2f0fe2811d7d4 100644
--- a/src/content/partials/dns/dns-errors-ts-action.mdx
+++ b/src/content/partials/dns/dns-errors-ts-action.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: errorName
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 If you experience <code>{props.one}</code> errors with a newly activated domain, review your DNS settings in the Cloudflare dashboard.
 
diff --git a/src/content/partials/dns/dns-errors-ts-intro.mdx b/src/content/partials/dns/dns-errors-ts-intro.mdx
index cb332968acfcf3d..d1d1d3950aaa5fa 100644
--- a/src/content/partials/dns/dns-errors-ts-intro.mdx
+++ b/src/content/partials/dns/dns-errors-ts-intro.mdx
@@ -1,16 +1,13 @@
 ---
 inputParameters: errorName
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 If you or your visitors experience <code>{props.one}</code> errors after you [activate your domain on Cloudflare](/dns/zone-setups/full-setup/setup/), review your DNS records in Cloudflare.
 
 :::note
 
-
 If your domain is added to Cloudflare by a hosting partner, manage your DNS records via the hosting partner.
 
-
 :::
diff --git a/src/content/partials/dns/dns-nxdomain-warning.mdx b/src/content/partials/dns/dns-nxdomain-warning.mdx
index d9b592cdc25513c..a0aa3e538b03546 100644
--- a/src/content/partials/dns/dns-nxdomain-warning.mdx
+++ b/src/content/partials/dns/dns-nxdomain-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
-If you activate your domain on Cloudflare *without* setting up the correct DNS records for your domain, your visitors may experience [DNS\_PROBE\_FINISHED\_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
-
+If you activate your domain on Cloudflare _without_ setting up the correct DNS records for your domain, your visitors may experience [DNS_PROBE_FINISHED_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
 
 :::
diff --git a/src/content/partials/dns/dns-record-steps.mdx b/src/content/partials/dns/dns-record-steps.mdx
index 058a0bf5c7cacfd..8ab4783d7d17bee 100644
--- a/src/content/partials/dns/dns-record-steps.mdx
+++ b/src/content/partials/dns/dns-record-steps.mdx
@@ -4,7 +4,13 @@ params:
   - example
 ---
 
-import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
@@ -27,4 +33,4 @@ Use the [Create DNS Record API endpoint](/api/resources/dns/subresources/records
     - To point to an IPv6 address, select **AAAA Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the IPv6 address for the field `content`.
     - To point to a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (such as `your-site.host.example.com`), select **CNAME Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the fully qualified domain name for the field `content`.
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/dns/dns-scan-intro.mdx b/src/content/partials/dns/dns-scan-intro.mdx
index 8901df100607fa7..e54726a33bab66b 100644
--- a/src/content/partials/dns/dns-scan-intro.mdx
+++ b/src/content/partials/dns/dns-scan-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/dns-scan-note.mdx b/src/content/partials/dns/dns-scan-note.mdx
index 636218d0b27de88..eff151ba8112ac8 100644
--- a/src/content/partials/dns/dns-scan-note.mdx
+++ b/src/content/partials/dns/dns-scan-note.mdx
@@ -1,5 +1,5 @@
 ---
 {}
-
 ---
+
 If you add a zone via the [API](/api/resources/zones/methods/create/), you can manually invoke the quick scan with the [Trigger DNS Records Scan endpoint](/api/resources/dns/subresources/records/methods/scan_trigger/).
diff --git a/src/content/partials/dns/dnssec-auto-add.mdx b/src/content/partials/dns/dnssec-auto-add.mdx
index c59ce7dadf53c5d..692574c3903a3ce 100644
--- a/src/content/partials/dns/dnssec-auto-add.mdx
+++ b/src/content/partials/dns/dnssec-auto-add.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Note:]
 
-
 Cloudflare automatically adds **DS** records for domains using Cloudflare Registrar or those using `.ch` and `.cz` top-level domains.
 
-
 :::
diff --git a/src/content/partials/dns/dnssec-cloudflare-steps.mdx b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
index d066c3e5a606e96..97e0be8c4a00e2d 100644
--- a/src/content/partials/dns/dnssec-cloudflare-steps.mdx
+++ b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/dns/dnssec-definition.mdx b/src/content/partials/dns/dnssec-definition.mdx
index 8e4f721549a3dcd..e286d2e3f82b1ed 100644
--- a/src/content/partials/dns/dnssec-definition.mdx
+++ b/src/content/partials/dns/dnssec-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS Security Extensions (DNSSEC) adds an extra layer of authentication to DNS, ensuring requests are not routed to a spoofed domain.
diff --git a/src/content/partials/dns/dnssec-enabled-migration.mdx b/src/content/partials/dns/dnssec-enabled-migration.mdx
index 2baa9a405746770..34be4c281d852e9 100644
--- a/src/content/partials/dns/dnssec-enabled-migration.mdx
+++ b/src/content/partials/dns/dnssec-enabled-migration.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If your previous provider allows you to add DNSKEY records on the zone apex and use these records in responses to DNS queries, refer to this [migration tutorial](/dns/dnssec/dnssec-active-migration/) to learn how to migrate a zone with DNSSEC enabled.
 
-
 :::
diff --git a/src/content/partials/dns/dnssec-registrar-steps.mdx b/src/content/partials/dns/dnssec-registrar-steps.mdx
index 60a42cb75248c8b..bb870033de61d09 100644
--- a/src/content/partials/dns/dnssec-registrar-steps.mdx
+++ b/src/content/partials/dns/dnssec-registrar-steps.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called *ECDSA Curve P-256 with SHA-256*.
+Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called _ECDSA Curve P-256 with SHA-256_.
 
 <Render file="dnssec-providers" product="dns" />
diff --git a/src/content/partials/dns/export-dns-records.mdx b/src/content/partials/dns/export-dns-records.mdx
index 1f8697f19614b35..1c63cb825b5f494 100644
--- a/src/content/partials/dns/export-dns-records.mdx
+++ b/src/content/partials/dns/export-dns-records.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
diff --git a/src/content/partials/dns/internal-dns-beta-note.mdx b/src/content/partials/dns/internal-dns-beta-note.mdx
index 5d69d57445eafa7..5f59566c426a379 100644
--- a/src/content/partials/dns/internal-dns-beta-note.mdx
+++ b/src/content/partials/dns/internal-dns-beta-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/internal-dns-view-conditions.mdx b/src/content/partials/dns/internal-dns-view-conditions.mdx
index b28ccc739a2b0fc..864542fca83a966 100644
--- a/src/content/partials/dns/internal-dns-view-conditions.mdx
+++ b/src/content/partials/dns/internal-dns-view-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - DNS views can be empty, with no [internal zones](/dns/internal-dns/internal-zones/) linked to them.
@@ -8,4 +7,5 @@
 - Each internal DNS zone name must be unique within a given DNS view.
 - Each DNS view name must be unique within a given Cloudflare account.
 
-<sup>1</sup> DNS zones that contain public DNS records and are accessible by public resolvers.
\ No newline at end of file
+<sup>1</sup> DNS zones that contain public DNS records and are accessible by
+public resolvers.
diff --git a/src/content/partials/dns/internal-reference-zone-api.mdx b/src/content/partials/dns/internal-reference-zone-api.mdx
index 05e1180d9227406..830c568f97e562c 100644
--- a/src/content/partials/dns/internal-reference-zone-api.mdx
+++ b/src/content/partials/dns/internal-reference-zone-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -10,14 +9,12 @@ In the following example, internal zone A (ID `8a904aeb565c42cfa207d98f6edea2f3`
 <APIRequest
 	path="/zones/{zone_id}/dns_settings"
 	method="PATCH"
-	json={
-		{
-    "internal_dns": {
-        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51"
-    }
-		}
-	}
+	json={{
+		internal_dns: {
+			reference_zone_id: "8e64c6fb4b514f3faf64de81efc11e51",
+		},
+	}}
 	parameters={{
 		zone_id: "8a904aeb565c42cfa207d98f6edea2f3",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/partials/dns/internal-reference-zone-intro.mdx b/src/content/partials/dns/internal-reference-zone-intro.mdx
index 71d7c7621b8fda4..94e58c8e201d0d8 100644
--- a/src/content/partials/dns/internal-reference-zone-intro.mdx
+++ b/src/content/partials/dns/internal-reference-zone-intro.mdx
@@ -5,10 +5,9 @@ params:
 
 During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain.
 
-
 { props.conditional === "get-started-link" && (
-	<p>
-	For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
-	</p>
-	)
-}
\ No newline at end of file
+<p>
+For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
+</p>
+)
+}
diff --git a/src/content/partials/dns/internal-zones-conditions.mdx b/src/content/partials/dns/internal-zones-conditions.mdx
index 64201918a6fb264..33e00fe187436c9 100644
--- a/src/content/partials/dns/internal-zones-conditions.mdx
+++ b/src/content/partials/dns/internal-zones-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
@@ -9,4 +8,5 @@
 - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
 - Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`).
 
-<sup>1</sup> Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved.
\ No newline at end of file
+<sup>1</sup> Logical groupings of internal DNS zones that are referenced by
+Gateway resolver policies to define how a specific query should be resolved.
diff --git a/src/content/partials/dns/linked-peers-limit.mdx b/src/content/partials/dns/linked-peers-limit.mdx
index 07cf4abcd9e4cc3..c18d3fb2b701548 100644
--- a/src/content/partials/dns/linked-peers-limit.mdx
+++ b/src/content/partials/dns/linked-peers-limit.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The maximum number of linked peers per zone is 30.
diff --git a/src/content/partials/dns/minimize-downtime-tip.mdx b/src/content/partials/dns/minimize-downtime-tip.mdx
index b13c26fb8eaa702..ca7fae767a4d48c 100644
--- a/src/content/partials/dns/minimize-downtime-tip.mdx
+++ b/src/content/partials/dns/minimize-downtime-tip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
\ No newline at end of file
+If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
diff --git a/src/content/partials/dns/mix-proxied-and-unproxied.mdx b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
index 8b12a1d041c6e54..c028f99ad6ccb3b 100644
--- a/src/content/partials/dns/mix-proxied-and-unproxied.mdx
+++ b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If you have multiple `A/AAAA` records on the same name and at least one of them is proxied, Cloudflare will treat all `A/AAAA` records on this name as being proxied.
 
-
 :::
diff --git a/src/content/partials/dns/nameserver-preamble.mdx b/src/content/partials/dns/nameserver-preamble.mdx
index 96bf1107d118e88..5b17906420c1020 100644
--- a/src/content/partials/dns/nameserver-preamble.mdx
+++ b/src/content/partials/dns/nameserver-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/nameservers-registrar-callout.mdx b/src/content/partials/dns/nameservers-registrar-callout.mdx
index efdd668bfb70fc7..afcec9106f1f765 100644
--- a/src/content/partials/dns/nameservers-registrar-callout.mdx
+++ b/src/content/partials/dns/nameservers-registrar-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Cloudflare Registrar]
diff --git a/src/content/partials/dns/ns-advanced-vs-custom.mdx b/src/content/partials/dns/ns-advanced-vs-custom.mdx
index 085c0ab10e67144..42e1cfe62cc3fb3 100644
--- a/src/content/partials/dns/ns-advanced-vs-custom.mdx
+++ b/src/content/partials/dns/ns-advanced-vs-custom.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The advantages that come with Foundation DNS [advanced nameservers](/dns/foundation-dns/advanced-nameservers/) are currently not available for [custom nameservers](/dns/nameservers/custom-nameservers/). Make sure you only use one at a time.
diff --git a/src/content/partials/dns/ns-set-omission-callout.mdx b/src/content/partials/dns/ns-set-omission-callout.mdx
index 4255ed43dcb62dd..aceb7ef494144c3 100644
--- a/src/content/partials/dns/ns-set-omission-callout.mdx
+++ b/src/content/partials/dns/ns-set-omission-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/ns-static-ips.mdx b/src/content/partials/dns/ns-static-ips.mdx
index 33542f81098b4ae..f7cb24564edd03d 100644
--- a/src/content/partials/dns/ns-static-ips.mdx
+++ b/src/content/partials/dns/ns-static-ips.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The IPs assigned to each nameserver are static, meaning they will not change without notification.
\ No newline at end of file
+The IPs assigned to each nameserver are static, meaning they will not change without notification.
diff --git a/src/content/partials/dns/ns-update-providers.mdx b/src/content/partials/dns/ns-update-providers.mdx
index 4619e0f648cd65c..207b9774b87ee74 100644
--- a/src/content/partials/dns/ns-update-providers.mdx
+++ b/src/content/partials/dns/ns-update-providers.mdx
@@ -1,42 +1,41 @@
 ---
 {}
-
 ---
 
 This is not an exhaustive list of provider-specific instructions, but the following links may be helpful:
 
-* [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
-* [101Domain](https://help.101domain.com/kb/managing-name-server-records)
-* [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
-* [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
-* [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
-* [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
-* [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
-* [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
-* [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
-* [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
-* [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
-* [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
-* [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
-* [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
-* [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
-* [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
-* [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
-* [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
-* [HostMonster](https://my.hostmonster.com/cgi/help/222)
-* [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
-* [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
-* [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
-* [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
-* [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
-* [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
-* [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
-* [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
-* [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
-* [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
-* [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
-* [Register](https://www.register.com/knowledge)
-* [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
-* [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
-* [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
-* [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
+- [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
+- [101Domain](https://help.101domain.com/kb/managing-name-server-records)
+- [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
+- [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
+- [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
+- [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
+- [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
+- [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
+- [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
+- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
+- [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
+- [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
+- [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
+- [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
+- [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
+- [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
+- [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
+- [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
+- [HostMonster](https://my.hostmonster.com/cgi/help/222)
+- [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
+- [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
+- [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
+- [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
+- [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
+- [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
+- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
+- [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
+- [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
+- [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
+- [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
+- [Register](https://www.register.com/knowledge)
+- [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
+- [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
+- [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
+- [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
diff --git a/src/content/partials/dns/onboard-warning.mdx b/src/content/partials/dns/onboard-warning.mdx
index cd609c994c7516f..883289d67398e5e 100644
--- a/src/content/partials/dns/onboard-warning.mdx
+++ b/src/content/partials/dns/onboard-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you [add a domain](/fundamentals/manage-domains/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
diff --git a/src/content/partials/dns/partial-setup-definition.mdx b/src/content/partials/dns/partial-setup-definition.mdx
index d4a185c7c288b4c..d429d6c760396ab 100644
--- a/src/content/partials/dns/partial-setup-definition.mdx
+++ b/src/content/partials/dns/partial-setup-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 A CNAME setup (also known as partial setup) allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
 
diff --git a/src/content/partials/dns/random-prefix-attack-definition.mdx b/src/content/partials/dns/random-prefix-attack-definition.mdx
index 421e48350e97627..3a4378c97f94a4e 100644
--- a/src/content/partials/dns/random-prefix-attack-definition.mdx
+++ b/src/content/partials/dns/random-prefix-attack-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Random prefix attacks are when someone sends a lot of traffic to subdomains that are highly unlikely to exist (`12345.example.com`, `abcdefg.example.com`), but are still associated with your main domain (`example.com`).
diff --git a/src/content/partials/dns/records-name-field.mdx b/src/content/partials/dns/records-name-field.mdx
index ed33e8cf7fea2e3..ed19a6fb9b2d987 100644
--- a/src/content/partials/dns/records-name-field.mdx
+++ b/src/content/partials/dns/records-name-field.mdx
@@ -3,7 +3,7 @@
 ---
 
 - **Name**: A subdomain or the zone apex (`@`).
-	- The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
-	- DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
-	- There is no requirement to start with a letter or end with a letter or digit.
-	- Underscores are valid in DNS and commonly used for service records.
+  - The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
+  - DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
+  - There is no requirement to start with a letter or end with a letter or digit.
+  - Underscores are valid in DNS and commonly used for service records.
diff --git a/src/content/partials/dns/recover-deleted-domain.mdx b/src/content/partials/dns/recover-deleted-domain.mdx
index 04ea32052b4199c..dd9da29b1c18d12 100644
--- a/src/content/partials/dns/recover-deleted-domain.mdx
+++ b/src/content/partials/dns/recover-deleted-domain.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/manage-domains/add-site/) just like you would for a new domain.
diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx
index 3addd6a512c230f..8a76949a59dd2f5 100644
--- a/src/content/partials/dns/secondary-conversion-unlink.mdx
+++ b/src/content/partials/dns/secondary-conversion-unlink.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -12,4 +11,4 @@ import { DashButton } from "~/components";
 2. Under **DNS Zone Transfers**, and select **Manage linked peers**.
 3. Unlink the peer and select **Save**.
 
-At this point, your zone will be read-only.
\ No newline at end of file
+At this point, your zone will be read-only.
diff --git a/src/content/partials/dns/secondary-dns-override.mdx b/src/content/partials/dns/secondary-dns-override.mdx
index 3479cba6efadd24..e85867604e92094 100644
--- a/src/content/partials/dns/secondary-dns-override.mdx
+++ b/src/content/partials/dns/secondary-dns-override.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Normal incoming zone transfers only provide DNS resolution. If you also want your traffic to benefit from Cloudflare's performance and security features, you need to [set up Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/).
diff --git a/src/content/partials/dns/ssltls-subdomains.mdx b/src/content/partials/dns/ssltls-subdomains.mdx
index 7509364e5359f30..65f7bae8f4f3cc0 100644
--- a/src/content/partials/dns/ssltls-subdomains.mdx
+++ b/src/content/partials/dns/ssltls-subdomains.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your main domain is using Cloudflare's [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/), that certificate also covers all first-level subdomains (`blog.example.com`).
diff --git a/src/content/partials/dns/subdomain-customization.mdx b/src/content/partials/dns/subdomain-customization.mdx
index b3d2fc5d81bd5a3..ca49fdca438e461 100644
--- a/src/content/partials/dns/subdomain-customization.mdx
+++ b/src/content/partials/dns/subdomain-customization.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to customize Cloudflare settings for individual subdomains, your approach will vary depending on your plan.
diff --git a/src/content/partials/dns/third-party-caveat.mdx b/src/content/partials/dns/third-party-caveat.mdx
index 32f0740937afdaf..aa50c4ed3da9acf 100644
--- a/src/content/partials/dns/third-party-caveat.mdx
+++ b/src/content/partials/dns/third-party-caveat.mdx
@@ -1,14 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::note
 
-
 When you [add records to Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/), those records should be [DNS-only (unproxied)](/dns/proxy-status/#dns-only-records) until {props.one} verifies your domain. Then, you can switch your DNS records to **Proxied**.
 
-
 :::
diff --git a/src/content/partials/dns/tsig-create-api.mdx b/src/content/partials/dns/tsig-create-api.mdx
index 0ca5c0a9ba3903e..240a4ecc1800410 100644
--- a/src/content/partials/dns/tsig-create-api.mdx
+++ b/src/content/partials/dns/tsig-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create a TSIG using the API, send a [POST](/api/resources/dns/subresources/zone_transfers/subresources/tsigs/methods/create/) request.
diff --git a/src/content/partials/dns/tsig-create-dash.mdx b/src/content/partials/dns/tsig-create-dash.mdx
index b93345590415a34..df306405d917d0e 100644
--- a/src/content/partials/dns/tsig-create-dash.mdx
+++ b/src/content/partials/dns/tsig-create-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -14,7 +13,7 @@ To create a TSIG using the dashboard:
 2. Go to **DNS Settings**.
 3. Under **DNS Zone Transfers**, for **TSIG**, select **Create**.
 4. Enter the following information:
-   * **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
-   * **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
-   * **Algorithm**: Choose a TSIG signing algorithm.
+   - **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
+   - **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
+   - **Algorithm**: Choose a TSIG signing algorithm.
 5. Select **Create**.
diff --git a/src/content/partials/dns/tsig-definition.mdx b/src/content/partials/dns/tsig-definition.mdx
index 74fe88b3a4ddd3a..be7c2d62be93667 100644
--- a/src/content/partials/dns/tsig-definition.mdx
+++ b/src/content/partials/dns/tsig-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 A Transaction Signature (TSIG) authenticates communication between a primary and secondary DNS server.
 
diff --git a/src/content/partials/dns/tsig-name-match.mdx b/src/content/partials/dns/tsig-name-match.mdx
index ffaa6bc70ebfc62..dffb08898eb97bf 100644
--- a/src/content/partials/dns/tsig-name-match.mdx
+++ b/src/content/partials/dns/tsig-name-match.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/why-disable-dnssec.mdx b/src/content/partials/dns/why-disable-dnssec.mdx
index 57db63f976fd9d8..2b37d7c7fa26608 100644
--- a/src/content/partials/dns/why-disable-dnssec.mdx
+++ b/src/content/partials/dns/why-disable-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When your domain has [DNSSEC enabled](https://www.cloudflare.com/learning/dns/dns-security/#what-is-dnssec), your DNS provider digitally signs all your DNS records. This action prevents anyone else from issuing false DNS records on your behalf and redirecting traffic intended for your domain.
diff --git a/src/content/partials/dns/zone-defaults-exceptions.mdx b/src/content/partials/dns/zone-defaults-exceptions.mdx
index 5005703713f7f89..1e74b26d026a49a 100644
--- a/src/content/partials/dns/zone-defaults-exceptions.mdx
+++ b/src/content/partials/dns/zone-defaults-exceptions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones, nor zones that existed previously and are being revived.
diff --git a/src/content/partials/dns/zone-file-size-limit.mdx b/src/content/partials/dns/zone-file-size-limit.mdx
index 4873764d6189ff0..71afea606b6bc17 100644
--- a/src/content/partials/dns/zone-file-size-limit.mdx
+++ b/src/content/partials/dns/zone-file-size-limit.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The zone file size limit is 256 KiB (262144 bytes).
diff --git a/src/content/partials/durable-objects/api-async-kv-legacy.mdx b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
index 1ef05ec94c61a03..a2698461e2eebcd 100644
--- a/src/content/partials/durable-objects/api-async-kv-legacy.mdx
+++ b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Type, MetaInfo, AnchorHeading} from "~/components";
+import { Type, MetaInfo, AnchorHeading } from "~/components";
 
 <AnchorHeading title="get" slug="do-kv-async-get" depth={3} />
 
@@ -107,4 +107,4 @@ The `put()` method returns a `Promise`, but most applications can discard this p
   - Same as the option to [`get()`](#do-kv-async-get), above.
 
 - `noCache` <Type text ='boolean' />
-  - Same as the option to [`get()`](#do-kv-async-get), above.
\ No newline at end of file
+  - Same as the option to [`get()`](#do-kv-async-get), above.
diff --git a/src/content/partials/durable-objects/api-storage-alarms.mdx b/src/content/partials/durable-objects/api-storage-alarms.mdx
index 8deccef0d3d08f2..1014b07d6080c01 100644
--- a/src/content/partials/durable-objects/api-storage-alarms.mdx
+++ b/src/content/partials/durable-objects/api-storage-alarms.mdx
@@ -27,4 +27,4 @@ import { Type, MetaInfo, Render } from "~/components";
 
 #### Supported options
 
-- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
\ No newline at end of file
+- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
diff --git a/src/content/partials/durable-objects/api-storage-other-methods.mdx b/src/content/partials/durable-objects/api-storage-other-methods.mdx
index 05bf6d643f93346..50cc1584f88f26d 100644
--- a/src/content/partials/durable-objects/api-storage-other-methods.mdx
+++ b/src/content/partials/durable-objects/api-storage-other-methods.mdx
@@ -39,4 +39,4 @@ import { Type, MetaInfo } from "~/components";
 - `sync()`: <Type text='Promise' />
   - Synchronizes any pending writes to disk.
 
-  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
\ No newline at end of file
+  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
diff --git a/src/content/partials/durable-objects/api-sync-kv.mdx b/src/content/partials/durable-objects/api-sync-kv.mdx
index 816f231f927d279..84a39a044b3d293 100644
--- a/src/content/partials/durable-objects/api-sync-kv.mdx
+++ b/src/content/partials/durable-objects/api-sync-kv.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Type, MetaInfo} from "~/components";
+import { Type, MetaInfo } from "~/components";
 
 ### `get`
 
diff --git a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
index ea25a405ba4567b..c869d21821c71a3 100644
--- a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
+++ b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
@@ -2,8 +2,8 @@
 {}
 ---
 
-import {GlossaryTooltip, WranglerConfig} from "~/components";
+import { GlossaryTooltip, WranglerConfig } from "~/components";
 
 ### How can I identify which Durable Object instance generated a log entry?
 
-You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
\ No newline at end of file
+You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
diff --git a/src/content/partials/durable-objects/do-plans-note.mdx b/src/content/partials/durable-objects/do-plans-note.mdx
index 36771fa0ccba055..3c7cb86f3649773 100644
--- a/src/content/partials/durable-objects/do-plans-note.mdx
+++ b/src/content/partials/durable-objects/do-plans-note.mdx
@@ -9,4 +9,4 @@ Durable Objects are available both on Workers Free and Workers Paid plans.
 - **Workers Paid plan**: Durable Objects with either SQLite storage backend or [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) are available.
 
 If you wish to downgrade from a Workers Paid plan to a Workers Free plan, you must first ensure that you have deleted all Durable Object namespaces with the key-value storage backend.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/durable-objects/durable-objects-sql.mdx b/src/content/partials/durable-objects/durable-objects-sql.mdx
index 43eb7777f652040..b13e5deb71af0d6 100644
--- a/src/content/partials/durable-objects/durable-objects-sql.mdx
+++ b/src/content/partials/durable-objects/durable-objects-sql.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
 [SQL API](/durable-objects/api/sqlite-storage-api/#exec) examples below use the following SQL schema:
 
@@ -10,102 +10,114 @@ import { Details } from "~/components"
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-  sql: SqlStorage
-  constructor(ctx: DurableObjectState, env: Env) {
-    super(ctx, env);
-    this.sql = ctx.storage.sql;
+	sql: SqlStorage;
+	constructor(ctx: DurableObjectState, env: Env) {
+		super(ctx, env);
+		this.sql = ctx.storage.sql;
 
-    this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
+		this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
       artistid    INTEGER PRIMARY KEY,
       artistname  TEXT
     );INSERT INTO artist (artistid, artistname) VALUES
       (123, 'Alice'),
       (456, 'Bob'),
-      (789, 'Charlie');`
-    );
-  }
+      (789, 'Charlie');`);
+	}
 }
 ```
 
 Iterate over query results as row objects:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist;");
+let cursor = this.sql.exec("SELECT * FROM artist;");
 
-  for (let row of cursor) {
-    // Iterate over row object and do something
-  }
+for (let row of cursor) {
+	// Iterate over row object and do something
+}
 ```
 
 Convert query results to an array of row objects:
+
 ```ts
-  // Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
-  let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
-  // OR
-  let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
-  // OR
-  let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
+// Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
+let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
+// OR
+let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
+// OR
+let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
 ```
 
 Convert query results to an array of row values arrays:
-```ts
-  // Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
-  let cursor = this.sql.exec("SELECT * FROM artist;");
-  let resultsArray = cursor.raw().toArray();
 
-  // Returns ["artistid","artistname"]
-  let columnNameArray = this.sql.exec("SELECT * FROM artist;").columnNames.toArray();
+```ts
+// Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
+let cursor = this.sql.exec("SELECT * FROM artist;");
+let resultsArray = cursor.raw().toArray();
+
+// Returns ["artistid","artistname"]
+let columnNameArray = this.sql
+	.exec("SELECT * FROM artist;")
+	.columnNames.toArray();
 ```
 
 Get first row object of query results:
+
 ```ts
-  // Returns {"artistid":123,"artistname":"Alice"}
-  let firstRow = this.sql.exec("SELECT * FROM artist ORDER BY artistname DESC;").toArray()[0];
+// Returns {"artistid":123,"artistname":"Alice"}
+let firstRow = this.sql
+	.exec("SELECT * FROM artist ORDER BY artistname DESC;")
+	.toArray()[0];
 ```
 
 Check if query results have exactly one row:
+
 ```ts
-  // returns error
-  this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
+// returns error
+this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
 
-  // returns { artistid: 123, artistname: 'Alice' }
-  let oneRow = this.sql.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice").one()
+// returns { artistid: 123, artistname: 'Alice' }
+let oneRow = this.sql
+	.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice")
+	.one();
 ```
 
 Returned cursor behavior:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-  let result = cursor.next();
-  if (!result.done) {
-    console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
-  } else {
-    // query returned zero results
-  }
-
-  let remainingRows = cursor.toArray();
-  console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+let result = cursor.next();
+if (!result.done) {
+	console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
+} else {
+	// query returned zero results
+}
+
+let remainingRows = cursor.toArray();
+console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 Returned cursor and `raw()` iterator iterate over the same query results:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-  let result = cursor.raw().next();
+let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+let result = cursor.raw().next();
 
-  if (!result.done) {
-    console.log(result.value); // prints [ 123, 'Alice' ]
-  } else {
-    // query returned zero results
-  }
+if (!result.done) {
+	console.log(result.value); // prints [ 123, 'Alice' ]
+} else {
+	// query returned zero results
+}
 
-  console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 `sql.exec().rowsRead()`:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist;");
-  cursor.next()
-  console.log(cursor.rowsRead); // prints 1
+let cursor = this.sql.exec("SELECT * FROM artist;");
+cursor.next();
+console.log(cursor.rowsRead); // prints 1
 
-  cursor.toArray(); // consumes remaining cursor
-  console.log(cursor.rowsRead); // prints 3
+cursor.toArray(); // consumes remaining cursor
+console.log(cursor.rowsRead); // prints 3
 ```
-
diff --git a/src/content/partials/durable-objects/recommend-sqlite-do.mdx b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
index dea8504982d30c4..0d406290b88226e 100644
--- a/src/content/partials/durable-objects/recommend-sqlite-do.mdx
+++ b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
@@ -8,4 +8,4 @@ Cloudflare recommends all new Durable Object namespaces use the [SQLite storage
 Additionally, SQLite-backed Durable Objects allow you to store more types of data (such as tables), and offer Point In Time Recovery API which can restore a Durable Object's embedded SQLite database contents (both SQL data and key-value data) to any point in the past 30 days.
 
 The [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) remains for backwards compatibility, and a migration path from KV storage backend to SQLite storage backend for existing Durable Object namespaces will be available in the future.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/durable-objects/what-are-durable-objects.mdx b/src/content/partials/durable-objects/what-are-durable-objects.mdx
index 15b96c85f0f37a6..82e992b0b2297d9 100644
--- a/src/content/partials/durable-objects/what-are-durable-objects.mdx
+++ b/src/content/partials/durable-objects/what-are-durable-objects.mdx
@@ -7,4 +7,4 @@ A Durable Object is a special kind of [Cloudflare Worker](/workers/) which uniqu
 - Each Durable Object has a **globally-unique name**, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together.
 - Each Durable Object has some **durable storage** attached. Since this storage lives together with the object, it is strongly consistent yet fast to access.
 
-Therefore, Durable Objects enable **stateful** serverless applications.
\ No newline at end of file
+Therefore, Durable Objects enable **stateful** serverless applications.
diff --git a/src/content/partials/email-routing/email-routing-definition.mdx b/src/content/partials/email-routing/email-routing-definition.mdx
index b3fc4db641ed951..6359302158f6bd7 100644
--- a/src/content/partials/email-routing/email-routing-definition.mdx
+++ b/src/content/partials/email-routing/email-routing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Email Routing is designed to simplify the way you create and manage email addresses, without needing to keep an eye on additional mailboxes. With Email Routing, you can create any number of custom email addresses to use in situations where you do not want to share your primary email address, such as when you subscribe to a new service or newsletter. Emails are then routed to your preferred email inbox, without you ever having to expose your primary email address.
diff --git a/src/content/partials/email-routing/enable-create-worker.mdx b/src/content/partials/email-routing/enable-create-worker.mdx
index 240b23f507f76ab..0d37ad3ba5aaa03 100644
--- a/src/content/partials/email-routing/enable-create-worker.mdx
+++ b/src/content/partials/email-routing/enable-create-worker.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 4. (Optional) Enter a descriptive Email Worker name in **Create a worker name**.
diff --git a/src/content/partials/email-routing/send-emails-workers-intro.mdx b/src/content/partials/email-routing/send-emails-workers-intro.mdx
index 0e3bcc4027b1122..e71d08e38f239f7 100644
--- a/src/content/partials/email-routing/send-emails-workers-intro.mdx
+++ b/src/content/partials/email-routing/send-emails-workers-intro.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: lastSentence
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 You can send an email about your Worker's activity from your Worker to an email address verified on [Email Routing](/email-routing/setup/email-routing-addresses/#destination-addresses). This is useful for when you want to know about certain types of events being triggered, for example.
 
diff --git a/src/content/partials/email-routing/types-bindings.mdx b/src/content/partials/email-routing/types-bindings.mdx
index a15b5284b492f9d..5d33d135b31a988 100644
--- a/src/content/partials/email-routing/types-bindings.mdx
+++ b/src/content/partials/email-routing/types-bindings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/email-security/add-user.mdx b/src/content/partials/email-security/add-user.mdx
index b36f104c9f96b1f..274d07c1c67b2ae 100644
--- a/src/content/partials/email-security/add-user.mdx
+++ b/src/content/partials/email-security/add-user.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: childParentInfo
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. Log in to the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/) {props.one}.
 2. Go to **Settings** (the gear icon).
diff --git a/src/content/partials/email-security/auto-retraction.mdx b/src/content/partials/email-security/auto-retraction.mdx
index bbaf21ca8a016d6..aba4b1ad99db360 100644
--- a/src/content/partials/email-security/auto-retraction.mdx
+++ b/src/content/partials/email-security/auto-retraction.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: hardRetract
-
 ---
 
-import { GlossaryTooltip, Markdown } from "~/components"
+import { GlossaryTooltip, Markdown } from "~/components";
 
 You can set up auto-retraction to automatically move messages matching certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to specific folders within a user's mailbox.
 
@@ -18,12 +17,11 @@ To set up automatic retraction:
 4. Select **Edit**.
 
 5. For each disposition, choose which folder the message should be sent to:
-
-   * **No Action**: Do not move the message.
-   * **Junk Email**: Sends the message to the junk or spam email folder.
-   * **Trash**: Sends the message to the trash or deleted items email folder.
-   * **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
-   * **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
+   - **No Action**: Do not move the message.
+   - **Junk Email**: Sends the message to the junk or spam email folder.
+   - **Trash**: Sends the message to the trash or deleted items email folder.
+   - **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
+   - **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
 
 6. Select **Update Auto-retract Settings**.
 
@@ -33,5 +31,5 @@ Email Security (formerly Area 1) is continuously gathering new information about
 
 You can enable two options:
 
-* **Post Delivery Response**:  Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
-* **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
\ No newline at end of file
+- **Post Delivery Response**: Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
+- **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
diff --git a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
index 06080642f1da59c..5c8fd8d25359499 100644
--- a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Now that Email Security (formerly Area 1) has been authorized to access and retrieve directory information, you will need to configure the Business Email Compromise list.
diff --git a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
index d13f48b4b6e1ecd..423c5edd0ddce5b 100644
--- a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When the Business Email Compromise list is configured, Email Security (formerly Area 1) will enforce the proper match of the sender’s display name and email address. Any variation from this strict requirement will raise a detection event. The reason of detection will be `Protected Name <NAME> should not appear as <non-configured email address>`.
diff --git a/src/content/partials/email-security/contact-support.mdx b/src/content/partials/email-security/contact-support.mdx
index 5378b3ab6111c21..b4a2c7c68ef7575 100644
--- a/src/content/partials/email-security/contact-support.mdx
+++ b/src/content/partials/email-security/contact-support.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::caution[Access to Area 1]
 Beginning October 1, 2025, access and support for Email Security (formerly Area 1) will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
index 5d3c830d646535b..fb9b79de16a89ea 100644
--- a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
 Select from the following BCC addresses to process email in the correct geographic location.
 
-| Host                                        | Location                | Note                                                                                                               |
+| Host                                                                   | Location                | Note                                                                                                               |
 | ---------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `<customer_name>@journaling.mxrecord.io`                               | US                      | Best option to ensure all email traffic processing happens US data centers.                                        |
-| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.           |
-| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.      |
+| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
+| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.        |
 | `<customer_name>@journaling.mailstream-bom.mxrecord.mx`                | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                            |
-| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.                                                            |
+| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
+| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
 | `<customer_name>@journaling.mailstream-syd.area1.cloudflare.net`       | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
 | `<customer_name>@journaling.mailstream-australia.area1.cloudflare.net` | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/mx-deployment-values.mdx b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
index 7159d1c82e5849e..6c51818a2f48130 100644
--- a/src/content/partials/email-security/deployment/mx-deployment-values.mdx
+++ b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | MX Priority | Host                             |
diff --git a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
index c4e31a82c6cc983..0486462814a3d07 100644
--- a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
@@ -1,18 +1,17 @@
 ---
 {}
-
 ---
 
 When configuring the Email Security (formerly Area 1) MX records, it is important to configure hosts with the correct MX priority. This will allow mail flows to the preferred hosts and fail over as needed.
 
 Choose from the following Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
 
-| Host                                                                                                                             | Location                | Note                                                                                                                                                                                  |
-| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                                                                                                 |
-| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.                                                                              |
-| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.
-| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                                                                                               |
-| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.
-| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                                                                                          |
-| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup.                                                                    |
+| Host                                                                                                                             | Location                | Note                                                                                                               |
+| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                              |
+| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
+| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.                                           |
+| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
+| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
+| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
+| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/o365-gcc.mdx b/src/content/partials/email-security/deployment/o365-gcc.mdx
index 94afd5f4a9ae9d6..452dc5782964883 100644
--- a/src/content/partials/email-security/deployment/o365-gcc.mdx
+++ b/src/content/partials/email-security/deployment/o365-gcc.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
index 2de2cfae20b80ed..7e6a508dd4c5951 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create quarantine policies:
@@ -20,9 +19,8 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
index ffd9e7b6f9ee7a9..e797688ae2d418e 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create quarantine policies:
@@ -20,9 +19,8 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-allow-message-release.png)
 
@@ -43,9 +41,8 @@ To create quarantine policies:
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
-    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
+    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
     ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
index 075e0dfe8e17426..8acc6ea1e36ac83 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: quarantinePolicy
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 You first need to configure the domains you are onboarding on the Email Security (formerly Area 1) dashboard. To configure your domains:
 
@@ -12,9 +11,9 @@ You first need to configure the domains you are onboarding on the Email Security
 3. Go to **Email configuration** > **Domains & Routing** > **Domains**.
 4. Make sure each domain you are onboarding has been added.
 5. For each domain you are configuring, select **...** > **Edit**, and set the following options:
-   * **Domain** - `<YOUR_DOMAIN>`.
-   * **Configured as** - `MX Records`.
-   * **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
-   * **IP Restrictions** - Leave this field empty.
-   * **Outbound TLS** - `Forward all messages over TLS`.
-   * **Quarantine Policy** - {props.one}
+   - **Domain** - `<YOUR_DOMAIN>`.
+   - **Configured as** - `MX Records`.
+   - **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
+   - **IP Restrictions** - Leave this field empty.
+   - **Outbound TLS** - `Forward all messages over TLS`.
+   - **Quarantine Policy** - {props.one}
diff --git a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
index 0f3c8996e8dba65..5ecfa3d112baa85 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
@@ -1,10 +1,9 @@
 ---
 inputParameters: ruleName;;ruleWords;;doFollowing;;img;;ruleName2;;ruleWords2;;doFollowing2;;img2
-
 ---
 
-import { Image } from 'astro:assets';
-import { GlossaryTooltip, Markdown } from "~/components"
+import { Image } from "astro:assets";
+import { GlossaryTooltip, Markdown } from "~/components";
 
 To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Email Security:
 
@@ -15,16 +14,15 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 3. Select **Add a Rule** > **Create a new rule**.
 
 4. Set the following rule conditions:
+   - **Name**: _{props.one}_.
+   - **Apply this rule if**: _The message headers_ > _includes any of these words_.
+     - **Enter text**: `X-Area1Security-Disposition` > **Save**.
+     - **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
+   - **Apply this rule if**: Select **+** to add a second condition.
+   - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+   - **Do the following** - _{props.three}_.
 
-   * **Name**: *{props.one}*.
-   * **Apply this rule if**: *The message headers* > *includes any of these words*.
-     * **Enter text**: `X-Area1Security-Disposition` > **Save**.
-     * **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
-   * **Apply this rule if**: Select **+** to add a second condition.
-   * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-   * **Do the following** - *{props.three}*.
-
- {/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
+{/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
 
 5. Select **Next**.
 
@@ -37,16 +35,15 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 9. Select **Add a Rule** > **Create a new rule**.
 
 10. Set the following rule conditions:
+    - **Name**: _{props.five}_.
+    - **Apply this rule if**: _The message headers_ > _includes any of these words_.
+      - **Enter text**: `X-Area1Security-Disposition` > **Save**.
+      - **Enter words**: _{props.six}_ > **Add** > **Save**.
+    - **Apply this rule if**: Select **+** to add a second condition.
+    - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+    - **Do the following**: _{props.seven}_.
 
-    * **Name**: *{props.five}*.
-    * **Apply this rule if**: *The message headers* > *includes any of these words*.
-      * **Enter text**: `X-Area1Security-Disposition` > **Save**.
-      * **Enter words**: *{props.six}* > **Add** > **Save**.
-    * **Apply this rule if**: Select **+** to add a second condition.
-    * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-    * **Do the following**: *{props.seven}*.
-
- {/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
+{/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
 
 11. Select **Next**.
 
@@ -54,4 +51,4 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 
 13. Review your settings and select **Finish** > **Done**.
 
-14. Select the rule *{props.five}* you have just created, and select **Enable**.
+14. Select the rule _{props.five}_ you have just created, and select **Enable**.
diff --git a/src/content/partials/email-security/deployment/setup-api-overview.mdx b/src/content/partials/email-security/deployment/setup-api-overview.mdx
index 42cb0c0bf4e1c36..749c98c3bfc1b4a 100644
--- a/src/content/partials/email-security/deployment/setup-api-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-api-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Email Security after they have already reached a user's inbox.
@@ -13,18 +12,18 @@ Then, through on integrations with your email provider, Email Security can [retr
 
 When you choose API deployment, you get the following benefits:
 
-* Easy protection for complex email architectures, without requiring any change to mailflow operations.
-* Agentless deployment for Microsoft 365 and Gmail.
-* The initial email protection measures offered by your current email provider.
+- Easy protection for complex email architectures, without requiring any change to mailflow operations.
+- Agentless deployment for Microsoft 365 and Gmail.
+- The initial email protection measures offered by your current email provider.
 
 ## Limitations
 
 However, API deployment also has the following disadvantages:
 
-* Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
-* Email Security requires read and write access to mailboxes.
-* Requires API support from your email provider (does not typically support on-premise providers).
-* Your email provider may throttle API requests from Email Security.
-* Detection rates may be lower if multiple solutions exist.
-* Messages cannot be modified or quarantined.
-* Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
+- Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
+- Email Security requires read and write access to mailboxes.
+- Requires API support from your email provider (does not typically support on-premise providers).
+- Your email provider may throttle API requests from Email Security.
+- Detection rates may be lower if multiple solutions exist.
+- Messages cannot be modified or quarantined.
+- Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
diff --git a/src/content/partials/email-security/deployment/setup-inline-overview.mdx b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
index a7473c6318abaea..70fac3460c076fb 100644
--- a/src/content/partials/email-security/deployment/setup-inline-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 With an **Inline deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), Email Security evaluates email messages before they reach a user's inbox.
 
@@ -15,11 +14,11 @@ More technically, Email Security becomes a hop in the <GlossaryTooltip term="SMT
 
 When you choose an inline deployment, you get the following benefits:
 
-* Messages are processed and physically blocked before delivery to a user's mailbox.
-* Your deployment is simpler, because any complex processing can happen downstream and without modification.
-* Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
-* Email Security can offer high availability and adaptive message pooling.
-* You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
+- Messages are processed and physically blocked before delivery to a user's mailbox.
+- Your deployment is simpler, because any complex processing can happen downstream and without modification.
+- Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
+- Email Security can offer high availability and adaptive message pooling.
+- You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
 
 ## Limitations
 
diff --git a/src/content/partials/email-security/deployment/setup-overview.mdx b/src/content/partials/email-security/deployment/setup-overview.mdx
index d8963b1ca171ef2..272608e20f764f3 100644
--- a/src/content/partials/email-security/deployment/setup-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you configure Email Security (formerly Area 1) Email Security to protect your organization, you can choose between two main setup architectures: Inline and API.
diff --git a/src/content/partials/email-security/email-security-description.mdx b/src/content/partials/email-security/email-security-description.mdx
index f65277d146ce070..a613aab3d39121a 100644
--- a/src/content/partials/email-security/email-security-description.mdx
+++ b/src/content/partials/email-security/email-security-description.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 <GlossaryTooltip term="phishing">Phishing</GlossaryTooltip> is the root cause of upwards of 90% of breaches that lead to financial loss and brand damage. Email Security (formerly Area 1) is a cloud-native service that stops phishing attacks across all threat vectors either at the [edge](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/) or in the cloud.
 
diff --git a/src/content/partials/email-security/outbound-email.mdx b/src/content/partials/email-security/outbound-email.mdx
index 1ed881d40a0dd1b..b7cc2413e883e96 100644
--- a/src/content/partials/email-security/outbound-email.mdx
+++ b/src/content/partials/email-security/outbound-email.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/email-security/rename-area1-to-ces.mdx b/src/content/partials/email-security/rename-area1-to-ces.mdx
index 4e5b20b1df6b4ea..ab1890e42fc4e97 100644
--- a/src/content/partials/email-security/rename-area1-to-ces.mdx
+++ b/src/content/partials/email-security/rename-area1-to-ces.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Area 1 has been renamed]
diff --git a/src/content/partials/email-security/search.mdx b/src/content/partials/email-security/search.mdx
index 2a9c170e7e24c0e..6e314af0ce256bd 100644
--- a/src/content/partials/email-security/search.mdx
+++ b/src/content/partials/email-security/search.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 1. **Detections only** is enabled by default. This means that the system will only search through and display emails that Email Security (formerly Area 1) has marked with a detection <GlossaryTooltip term="disposition" link="/email-security/reference/dispositions-and-attributes/">disposition</GlossaryTooltip>. If you prefer to search through and view all emails that have been processed by Email Security, whether they are marked with a detection disposition or not, disable this option.
 2. The **All detections** drop-down menu allows you to refine your search by detection disposition. This menu will be disabled if **Detections only** is not selected.
 3. By default, the search results are limited to the previous 30 days. Select **Last 30 days** to change this setting.
 4. (Optional) You can download the results from your search in CSV format. The CSV file is capped at 1,000 rows.
 5. The system returns a list of emails that fit your search criteria, and will inform you if there are emails similar to the ones found. If Email Security finds emails similar to the ones returned by your query, select **Show** to display them. Otherwise, select **View** on the email you are interested in. This will show you more information about that particular email, such as:
-   * Disposition (if any)
-   * Email status (for example `Quarantined`)
-   * Sender details (for example, IP address)
+   - Disposition (if any)
+   - Email status (for example `Quarantined`)
+   - Sender details (for example, IP address)
diff --git a/src/content/partials/email-security/service-addresses.mdx b/src/content/partials/email-security/service-addresses.mdx
index 6e22907a82f13d1..5440ee7231acb79 100644
--- a/src/content/partials/email-security/service-addresses.mdx
+++ b/src/content/partials/email-security/service-addresses.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/email-security/sso-enforcement.mdx b/src/content/partials/email-security/sso-enforcement.mdx
index bf094a37f8a0fc8..8ff51749311a532 100644
--- a/src/content/partials/email-security/sso-enforcement.mdx
+++ b/src/content/partials/email-security/sso-enforcement.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
-* **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
-* **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
-* **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
+- **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
+- **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
+- **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
diff --git a/src/content/partials/fundamentals/account-audit-logs-definition.mdx b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
index f8c6c30b76e700a..524d5179caa2fed 100644
--- a/src/content/partials/fundamentals/account-audit-logs-definition.mdx
+++ b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Audit logs summarize the history of changes made within your Cloudflare account. Audit logs include account level actions like login, as well as zone configuration changes.
@@ -9,8 +8,6 @@ Audit Logs are available on all plan types and are captured for both individual
 
 :::note
 
-
 Most beta features will not appear in audit logs until they are out of beta.
 
-
 :::
diff --git a/src/content/partials/fundamentals/account-manage-active-sessions.mdx b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
index 4be15fc6addf57f..68aba8bba607b09 100644
--- a/src/content/partials/fundamentals/account-manage-active-sessions.mdx
+++ b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 In the Cloudflare dashboard, you can view a list of active sessions associated with your email address.
@@ -11,10 +10,8 @@ If you notice any suspicious activity, you can also revoke any active sessions.
 
 :::note
 
-
 By default, the session timeout for the Cloudflare dashboard is 72 hours without any activity.
 
 Some customers can also enforce single-sign on (SSO) by [adding a Dashboard SSO application](/fundamentals/manage-members/dashboard-sso/).
 
-
 :::
diff --git a/src/content/partials/fundamentals/account-member-manage-limitation.mdx b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
index 9d7535b542de061..67c9f962a22856f 100644
--- a/src/content/partials/fundamentals/account-member-manage-limitation.mdx
+++ b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/).
diff --git a/src/content/partials/fundamentals/api-change-api-key.mdx b/src/content/partials/fundamentals/api-change-api-key.mdx
index 215b04ead3be1e3..06ec545d2f3cd2a 100644
--- a/src/content/partials/fundamentals/api-change-api-key.mdx
+++ b/src/content/partials/fundamentals/api-change-api-key.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ If your API key might be compromised, change your API key:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **API Tokens**.
 3. In the **API Keys** section, find your key.
diff --git a/src/content/partials/fundamentals/api-combine-filters.mdx b/src/content/partials/fundamentals/api-combine-filters.mdx
index 6e4a1b16a8df9cf..01c8e615b939694 100644
--- a/src/content/partials/fundamentals/api-combine-filters.mdx
+++ b/src/content/partials/fundamentals/api-combine-filters.mdx
@@ -1,18 +1,15 @@
 ---
 {}
-
 ---
 
 Combine filters using `OR` and `AND` boolean logic:
 
-* `AND` takes precedence over `OR` in all expressions.
-* The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
-* The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
+- `AND` takes precedence over `OR` in all expressions.
+- The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
+- The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
 
   :::note
 
-
   Note that the semicolon is a reserved character in URLs ([RFC 1738](https://www.rfc-editor.org/rfc/rfc1738)) and should be percent-encoded as `%3B`.
 
-
   :::
diff --git a/src/content/partials/fundamentals/api-filter-operators.mdx b/src/content/partials/fundamentals/api-filter-operators.mdx
index fd3a372b4041816..57f6d12acfe8282 100644
--- a/src/content/partials/fundamentals/api-filter-operators.mdx
+++ b/src/content/partials/fundamentals/api-filter-operators.mdx
@@ -1,18 +1,14 @@
 ---
 inputParameters: param1;;param2;;param3;;param4
-
 ---
 
+import { Markdown } from "~/components";
 
-
-import { Markdown } from "~/components"
-
-| Operator | Name                     | Example           | Description                                                          | URL Encoded |
-| -------- | ------------------------ | ----------------- | -------------------------------------------------------------------- | ----------- |
-| `==`     | Equals                   | <code>{props.one}=={props.two}</code>          | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.                           | `%3D%3D`    |
-| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code>         | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>.                    | `!%3D`      |
-| `>`      | Greater than             | `dimension>1000`  | Return results where a dimension is greater than `1000`.             | `%3E`       |
-| `<`      | Less than                | `dimension<1000`  | Return results where a dimension is less than `1000`.                | `%3C`       |
-| `>=`     | Greater than or equal to | `dimension>=1000` | Return results where a dimension is greater than or equal to `1000`. | `%3E%3D`    |
-| `<=`     | Less than or equal to    | `dimension<=1000` | Return results where a dimension is less than or equal to `1000`.    | `%3C%3D`    |
-
+| Operator | Name                     | Example                                  | Description                                                                                  | URL Encoded |
+| -------- | ------------------------ | ---------------------------------------- | -------------------------------------------------------------------------------------------- | ----------- |
+| `==`     | Equals                   | <code>{props.one}=={props.two}</code>    | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.           | `%3D%3D`    |
+| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code> | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>. | `!%3D`      |
+| `>`      | Greater than             | `dimension>1000`                         | Return results where a dimension is greater than `1000`.                                     | `%3E`       |
+| `<`      | Less than                | `dimension<1000`                         | Return results where a dimension is less than `1000`.                                        | `%3C`       |
+| `>=`     | Greater than or equal to | `dimension>=1000`                        | Return results where a dimension is greater than or equal to `1000`.                         | `%3E%3D`    |
+| `<=`     | Less than or equal to    | `dimension<=1000`                        | Return results where a dimension is less than or equal to `1000`.                            | `%3C%3D`    |
diff --git a/src/content/partials/fundamentals/api-rate-limits.mdx b/src/content/partials/fundamentals/api-rate-limits.mdx
index 09202c8b7845f04..37822f640908916 100644
--- a/src/content/partials/fundamentals/api-rate-limits.mdx
+++ b/src/content/partials/fundamentals/api-rate-limits.mdx
@@ -6,16 +6,16 @@ params:
 import { AnchorHeading } from "~/components";
 
 {props.showHeading && (
-	<AnchorHeading title="API token limits" depth={2} />
+<AnchorHeading title="API token limits" depth={2} />
 )}
 
-| Type                    | Limit                               |
-| ----------------------- | ----------------------------------- |
-| Client API per user/account token     | 1200/5 minutes        |
-| Client API per IP       | 200/second                          |
-| GraphQL                 | Varies by query cost. Max 320/5 min |
-| User API token quota    | 50                                  |
-| Account API token quota | 500                                 |
+| Type                              | Limit                               |
+| --------------------------------- | ----------------------------------- |
+| Client API per user/account token | 1200/5 minutes                      |
+| Client API per IP                 | 200/second                          |
+| GraphQL                           | Varies by query cost. Max 320/5 min |
+| User API token quota              | 50                                  |
+| Account API token quota           | 500                                 |
 
 :::note
 The global rate limit for the Cloudflare API is 1,200 requests per five minute period per user, and applies cumulatively regardless of whether the request is made via the dashboard, API key, or API token.
diff --git a/src/content/partials/fundamentals/api-using-api.mdx b/src/content/partials/fundamentals/api-using-api.mdx
index b1ca2470c79d58c..e5ae32ba9e53c09 100644
--- a/src/content/partials/fundamentals/api-using-api.mdx
+++ b/src/content/partials/fundamentals/api-using-api.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 Using the Cloudflare API requires authentication so that Cloudflare knows who is making requests and what permissions you have. [Create an API token](/fundamentals/api/get-started/create-token/) to grant access to the API to perform actions.
 
 :::note
 
-
 You can also authenticate with [API keys](/fundamentals/api/get-started/keys/), but these keys have [several limitations](/fundamentals/api/get-started/keys/#limitations) that make them less secure than API tokens. Whenever possible, use API tokens to interact with the Cloudflare API.
 
-
 :::
diff --git a/src/content/partials/fundamentals/audit-log-api.mdx b/src/content/partials/fundamentals/audit-log-api.mdx
index ce209127d72ff3f..6d53ba9530aa6e7 100644
--- a/src/content/partials/fundamentals/audit-log-api.mdx
+++ b/src/content/partials/fundamentals/audit-log-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To get audit logs from the Cloudflare API, send a [GET request](/api/resources/audit_logs/methods/list/).
diff --git a/src/content/partials/fundamentals/create-account-best-practices.mdx b/src/content/partials/fundamentals/create-account-best-practices.mdx
index 8a878be2c868221..efc376dfbf7bcdb 100644
--- a/src/content/partials/fundamentals/create-account-best-practices.mdx
+++ b/src/content/partials/fundamentals/create-account-best-practices.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you are creating an account for your team or a business, we recommend choosing an email alias or distribution list for your **Email**, such as `cloudflare@example.com`.
diff --git a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
index 5c9104ac3a59f7b..24617a79253e1c1 100644
--- a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
+++ b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
@@ -1,36 +1,35 @@
 ---
 {}
-
 ---
 
 Cloudflare’s recommended CIPA rule blocks the following content subcategories:
 
-* Adult Themes
-* Alcohol
-* Anonymizer
-* Brand Embedding
-* Child Abuse
-* Command and Control & Botnet
-* Cryptomining
-* DGA Domains
-* DNS Tunneling
-* Drugs
-* Gambling
-* Hacking
-* Malware
-* Militancy, Hate & Extremism
-* Nudity
-* P2P
-* Phishing
-* Pornography
-* Private IP Address
-* Profanity
-* Questionable Activities
-* School Cheating
-* Spam
-* Spyware
-* Tobacco
-* Violence
-* Weapons
+- Adult Themes
+- Alcohol
+- Anonymizer
+- Brand Embedding
+- Child Abuse
+- Command and Control & Botnet
+- Cryptomining
+- DGA Domains
+- DNS Tunneling
+- Drugs
+- Gambling
+- Hacking
+- Malware
+- Militancy, Hate & Extremism
+- Nudity
+- P2P
+- Phishing
+- Pornography
+- Private IP Address
+- Profanity
+- Questionable Activities
+- School Cheating
+- Spam
+- Spyware
+- Tobacco
+- Violence
+- Weapons
 
 Review the [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for more information.
diff --git a/src/content/partials/fundamentals/cybersafe-configuration.mdx b/src/content/partials/fundamentals/cybersafe-configuration.mdx
index e8654c6c41b1e83..97c5c85cf1bc3fe 100644
--- a/src/content/partials/fundamentals/cybersafe-configuration.mdx
+++ b/src/content/partials/fundamentals/cybersafe-configuration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To facilitate compliance with CIPA requirements, administrators can [enable a single filtering policy option](/cloudflare-one/traffic-policies/dns-policies/common-policies/#turn-on-cipa-filter). This includes applying the required filter categories to block access to unwanted or harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-description.mdx b/src/content/partials/fundamentals/cybersafe-description.mdx
index 431d708d46e714b..a3f8e1c475bbb46 100644
--- a/src/content/partials/fundamentals/cybersafe-description.mdx
+++ b/src/content/partials/fundamentals/cybersafe-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/sites/default/files/childrens_internet_protection_act_cipa.pdf) is a federal law enacted by the United States Congress to address concerns about children's access to inappropriate or harmful content over the Internet. CIPA requires K-12 schools and libraries that receive certain federal funding to implement Internet safety measures to protect minors from harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-requirements.mdx b/src/content/partials/fundamentals/cybersafe-requirements.mdx
index 833e37f87f33941..e6be7dae9a66a9c 100644
--- a/src/content/partials/fundamentals/cybersafe-requirements.mdx
+++ b/src/content/partials/fundamentals/cybersafe-requirements.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 CIPA mandates that K-12 schools and libraries adopt Internet safety policies that include measures to block or filter access to specific categories of content. These categories encompass a wide range of topics that could be harmful or inappropriate for minors. Compliance with these requirements helps ensure that students' online experiences are safer and more secure.
diff --git a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
index 2e2f41f8016c234..9973f9748eda869 100644
--- a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
+++ b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 This program is only available to eligible school districts. To be eligible, Project Cybersafe School participants must be:
 
-* K-12 public school districts located in the United States.
-* Up to 2,500 students in the district.
+- K-12 public school districts located in the United States.
+- Up to 2,500 students in the district.
diff --git a/src/content/partials/fundamentals/idp-group-deprecation.mdx b/src/content/partials/fundamentals/idp-group-deprecation.mdx
index 05821b931796237..baaae6c04591975 100644
--- a/src/content/partials/fundamentals/idp-group-deprecation.mdx
+++ b/src/content/partials/fundamentals/idp-group-deprecation.mdx
@@ -1,12 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 **Important Update:** Cloudflare now supports native User Groups for enhanced access control. This new feature replaces the previous method of directly assigning Cloudflare roles based on IdP group mappings (identified by the pattern `CF-<accountID> - <Role Name>`), which is deprecated as of June 2nd, 2025. SCIM Virtual Groups will reach end-of-life on December 2, 2025. Update your SCIM configurations using the instructions below to utilize User Groups for seamless provisioning.
 :::
-
-
-
-
diff --git a/src/content/partials/fundamentals/lists-import-notes.mdx b/src/content/partials/fundamentals/lists-import-notes.mdx
index 7b084592eb99561..1325dd37dc9b03c 100644
--- a/src/content/partials/fundamentals/lists-import-notes.mdx
+++ b/src/content/partials/fundamentals/lists-import-notes.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 Cloudflare will apply the following rules when you add items to an existing list (either manually or via CSV file):
 
-* Do not remove any existing list items before updating/adding items.
-* Update items that were already in the list.
-* Add items that were not present in the list.
+- Do not remove any existing list items before updating/adding items.
+- Update items that were already in the list.
+- Add items that were not present in the list.
diff --git a/src/content/partials/fundamentals/new-token-warning.mdx b/src/content/partials/fundamentals/new-token-warning.mdx
index ebba0665c1f6103..794191bf0e51bba 100644
--- a/src/content/partials/fundamentals/new-token-warning.mdx
+++ b/src/content/partials/fundamentals/new-token-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Warning]
 
-
 The token secret is **only shown once**. Do not store the secret in plaintext where others can access it. Anyone with this token can perform the authorized actions against the resources that the token has access to.
 
-
 :::
diff --git a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
index 8339d260cd8f0fd..707af55fc2d4d48 100644
--- a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
+++ b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If **Pseudo IPv4** is set to `Overwrite Headers` - Cloudflare overwrites the existing `Cf-Connecting-IP` and `X-Forwarded-For` headers with a pseudo IPv4 address while preserving the real IPv6 address in `CF-Connecting-IPv6` header.
diff --git a/src/content/partials/fundamentals/revoke-active-sessions.mdx b/src/content/partials/fundamentals/revoke-active-sessions.mdx
index 07d956a61afdf20..fc8a9e0c4c296c9 100644
--- a/src/content/partials/fundamentals/revoke-active-sessions.mdx
+++ b/src/content/partials/fundamentals/revoke-active-sessions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,7 +10,7 @@ To revoke a session:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 3. On a specific section, click **Revoke**.
diff --git a/src/content/partials/fundamentals/ubb-recommendation.mdx b/src/content/partials/fundamentals/ubb-recommendation.mdx
index ec055f77df645ca..d05b58438eb70b2 100644
--- a/src/content/partials/fundamentals/ubb-recommendation.mdx
+++ b/src/content/partials/fundamentals/ubb-recommendation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,16 +10,15 @@ To set up those notifications:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-      <DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
 
 2. On **Alert Type** of **Usage Based Billing**, click **Select**.
 
 3. Fill out the following information:
-
-   * **Name**
-   * **Product**
-   * **Notification limit** (exact metric will vary based on product)
-   * **Notification email**
+   - **Name**
+   - **Product**
+   - **Notification limit** (exact metric will vary based on product)
+   - **Notification email**
 
    :::note
    Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/).
diff --git a/src/content/partials/fundamentals/user-permissions-table.mdx b/src/content/partials/fundamentals/user-permissions-table.mdx
index 5bcacf794820b2f..0a4067fc83f026d 100644
--- a/src/content/partials/fundamentals/user-permissions-table.mdx
+++ b/src/content/partials/fundamentals/user-permissions-table.mdx
@@ -1,15 +1,14 @@
 ---
 inputParameters: editWord
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-| Name              | Description                                                                                        |
-| ----------------- | -------------------------------------------------------------------------------------------------- |
-| API Tokens Read   | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).               |
-| API Tokens {props.one}     | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).              |
-| Memberships Read  | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
-| Memberships {props.one}    | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
-| User Details Read | Grants read access to user details.                                                                |
-| User Details {props.one}   | Grants write access to user details.                                                               |
+| Name                     | Description                                                                                  |
+| ------------------------ | -------------------------------------------------------------------------------------------- |
+| API Tokens Read          | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).         |
+| API Tokens {props.one}   | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).        |
+| Memberships Read         | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
+| Memberships {props.one}  | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
+| User Details Read        | Grants read access to user details.                                                          |
+| User Details {props.one} | Grants write access to user details.                                                         |
diff --git a/src/content/partials/fundamentals/user-profiles.mdx b/src/content/partials/fundamentals/user-profiles.mdx
index 95d7406967bb114..5f074fa4484f104 100644
--- a/src/content/partials/fundamentals/user-profiles.mdx
+++ b/src/content/partials/fundamentals/user-profiles.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/user-profiles/customize-account/#notifications) and [Language preferences](/fundamentals/user-profiles/customize-account/#language).
 
-To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
\ No newline at end of file
+To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
diff --git a/src/content/partials/fundamentals/view-audit-log.mdx b/src/content/partials/fundamentals/view-audit-log.mdx
index 34f479029436066..ea0694e788fe9fc 100644
--- a/src/content/partials/fundamentals/view-audit-log.mdx
+++ b/src/content/partials/fundamentals/view-audit-log.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +14,6 @@ You can search these audit logs by user email or domain and filter by date range
 
 :::note
 
-
 Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Logpush](/logs/logpush/) to make sure Audit Logs are always available and stored externally.
 
-
 :::
diff --git a/src/content/partials/fundamentals/what-is-cloudflare.mdx b/src/content/partials/fundamentals/what-is-cloudflare.mdx
index 6db16b67782d1fc..7321651a4cf4000 100644
--- a/src/content/partials/fundamentals/what-is-cloudflare.mdx
+++ b/src/content/partials/fundamentals/what-is-cloudflare.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Stream } from "~/components"
+import { Stream } from "~/components";
 
 Cloudflare is one of the world's largest [connectivity cloud networks](https://blog.cloudflare.com/welcome-to-connectivity-cloud). Today, anyone with an Internet presence can have faster and more secure websites and applications thanks to Cloudflare. This includes bloggers, businesses, and even non-profits.
 
diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
index 17b0e04547941b8..7f8df8ff66b23e8 100644
--- a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
+++ b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) is occurring. No other error codes will trigger a zero-downtime failover operation.
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
index a0936f417ad77a4..94ebfc3d69ff887 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
@@ -30,9 +29,7 @@ Specifically:
 - The binding must be [a valid JavaScript variable name](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#variables). For example, `binding = "hyperdrive"` or `binding = "productionDB"` would both be valid names for the binding.
 - Your binding is available in your Worker at `env.<BINDING_NAME>`.
 
-
-If you wish to use a local database during development, you can add a `localConnectionString` to your  Hyperdrive configuration with the connection string of your database:
-
+If you wish to use a local database during development, you can add a `localConnectionString` to your Hyperdrive configuration with the connection string of your database:
 
 <WranglerConfig>
 
@@ -54,4 +51,4 @@ If you wish to use a local database during development, you can add a `localConn
 
 Learn more about setting up [Hyperdrive for local development](/hyperdrive/configuration/local-development/).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
index 2bccc59303de979..55f58eb3fdaebda 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
@@ -2,7 +2,14 @@
 {}
 ---
 
-import { DashButton, WranglerConfig, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	DashButton,
+	WranglerConfig,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 To configure Hyperdrive, you will need:
 
diff --git a/src/content/partials/hyperdrive/pooling-mode.mdx b/src/content/partials/hyperdrive/pooling-mode.mdx
index a06f46f412dcfe7..ca988038c32fd15 100644
--- a/src/content/partials/hyperdrive/pooling-mode.mdx
+++ b/src/content/partials/hyperdrive/pooling-mode.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool.
diff --git a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
index b1275de22aeb7e2..f4895b5eecb79bb 100644
--- a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
+++ b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
@@ -37,7 +37,7 @@ export default {
 			// If you are not using array types in your Postgres schema, disable `fetch_types` to avoid an additional round-trip (unnecessary latency)
 			fetch_types: false,
 
-			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.  
+			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.
 			prepare: true,
 		});
 
diff --git a/src/content/partials/learning-paths/cache-basic-diagram.mdx b/src/content/partials/learning-paths/cache-basic-diagram.mdx
index 6555ff5ad8fcf75..c44a888cabcaa1e 100644
--- a/src/content/partials/learning-paths/cache-basic-diagram.mdx
+++ b/src/content/partials/learning-paths/cache-basic-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/learning-paths/cache-optimization.mdx b/src/content/partials/learning-paths/cache-optimization.mdx
index 890676e0f865216..48c74235eb911f9 100644
--- a/src/content/partials/learning-paths/cache-optimization.mdx
+++ b/src/content/partials/learning-paths/cache-optimization.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 A few ways to optimize Cloudflare caching include:
 
-* Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
-* Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
-* Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
+- Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
+- Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
+- Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
diff --git a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
index f15999e994d4aec..6dba0749cadcf88 100644
--- a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Related content**
@@ -10,4 +9,4 @@ For additional resources on the China Network, refer to the following resources:
     - [Cloudflare China Network](/china-network/)
     - [CDN Global Acceleration (formerly China Express)](/china-network/concepts/global-acceleration/)
     - [Internet Content Provider (ICP)](/china-network/concepts/icp/)
-    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
\ No newline at end of file
+    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
diff --git a/src/content/partials/learning-paths/china-network-overview-navigation.mdx b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
index 5e5f0c651602e6f..6e6fee7c6c5dfbd 100644
--- a/src/content/partials/learning-paths/china-network-overview-navigation.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
@@ -1,20 +1,19 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: How to speed up your web traffic inside mainland China"
-          description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
-          href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
-          description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
-          href="/learning-paths/china-network-overview/series/china-express-overview-2/"
-        />              
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: How to speed up your web traffic inside mainland China"
+		description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
+		href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
+		description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
+		href="/learning-paths/china-network-overview/series/china-express-overview-2/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
index 80b90de36b0e2f6..b825a923b79a986 100644
--- a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
+++ b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address, by creating an outbound-only connections to Cloudflare’s global network.
 
-* **Security**: Very secure.
-* **Availability**: All customers.
-* **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
+- **Security**: Very secure.
+- **Availability**: All customers.
+- **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
diff --git a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
index 7b1ca7fcfce93d8..95cf4f8cf529595 100644
--- a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
+++ b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A distributed denial-of-service (DDoS) attack is where a large number of computers or devices, usually controlled by a single attacker, attempt to access a website or online service all at once. This flood of traffic can overwhelm the website's origin servers, causing the site to slow down or even crash.
@@ -18,4 +17,4 @@ sequenceDiagram;
     Origin Server-->>User: Unable to respond to user requests
 ```
 
-<br/>
+<br />
diff --git a/src/content/partials/learning-paths/email-record-origin-ip.mdx b/src/content/partials/learning-paths/email-record-origin-ip.mdx
index 94b82b3791865f7..5b5f2c45e1b9e18 100644
--- a/src/content/partials/learning-paths/email-record-origin-ip.mdx
+++ b/src/content/partials/learning-paths/email-record-origin-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If possible, do not host a mail service on the same server as the web resource you want to protect, since emails sent to non-existent addresses get bounced back to the attacker and reveal the mail server IP address.
diff --git a/src/content/partials/learning-paths/r2-series-navigation.mdx b/src/content/partials/learning-paths/r2-series-navigation.mdx
index fdf03a46c5a8df9..612ab4b973072ca 100644
--- a/src/content/partials/learning-paths/r2-series-navigation.mdx
+++ b/src/content/partials/learning-paths/r2-series-navigation.mdx
@@ -1,34 +1,33 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Getting started with R2"
-          description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
-          href="/learning-paths/r2-intro/series/r2-1/"
-        />          
-      <LinkCard
-          title="Watch Episode 2: Public buckets"
-          description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
-          href="/learning-paths/r2-intro/series/r2-2/"
-        />    
-      <LinkCard
-          title="Watch Episode 3: S3 API compatibility"
-          description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
-          href="/learning-paths/r2-intro/series/r2-3/"
-        />    
-      <LinkCard
-          title="Watch Episode 4: Migrating your bucket data"
-          description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
-          href="/learning-paths/r2-intro/series/r2-4/"
-        />    
-      <LinkCard
-          title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
-          description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
-          href="/learning-paths/r2-intro/series/r2-5/"
-        />                                    
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Getting started with R2"
+		description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
+		href="/learning-paths/r2-intro/series/r2-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: Public buckets"
+		description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
+		href="/learning-paths/r2-intro/series/r2-2/"
+	/>
+	<LinkCard
+		title="Watch Episode 3: S3 API compatibility"
+		description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
+		href="/learning-paths/r2-intro/series/r2-3/"
+	/>
+	<LinkCard
+		title="Watch Episode 4: Migrating your bucket data"
+		description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
+		href="/learning-paths/r2-intro/series/r2-4/"
+	/>
+	<LinkCard
+		title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
+		description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
+		href="/learning-paths/r2-intro/series/r2-5/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/sase-series-navigation.mdx b/src/content/partials/learning-paths/sase-series-navigation.mdx
index c9ac5dace4ee296..67412cf58413313 100644
--- a/src/content/partials/learning-paths/sase-series-navigation.mdx
+++ b/src/content/partials/learning-paths/sase-series-navigation.mdx
@@ -1,40 +1,38 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: The evolution of corporate networks"
-          description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
-          href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 2: Stop hosting your own VPN service"
-          description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
-          href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 3: Secure remote access to your critical infrastructure"
-          description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
-          href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 4: Connect and secure from any network to anywhere"
-          description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: The evolution of corporate networks"
+		description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
+		href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 2: Stop hosting your own VPN service"
+		description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
+		href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 3: Secure remote access to your critical infrastructure"
+		description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
+		href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 4: Connect and secure from any network to anywhere"
+		description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
   "
-          href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 5: Protect your users from Internet risks"
-          description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
-          href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
-      />                           
-        
-    </CardGrid>
+		href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 5: Protect your users from Internet risks"
+		description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
+		href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/warp-series-navigation.mdx b/src/content/partials/learning-paths/warp-series-navigation.mdx
index 30d3c3c2090ec52..af1eed7e2a23691 100644
--- a/src/content/partials/learning-paths/warp-series-navigation.mdx
+++ b/src/content/partials/learning-paths/warp-series-navigation.mdx
@@ -1,19 +1,18 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
-          description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
-          href="/learning-paths/warp-overview-course/series/warp-basics-1/"
-        />              
-      <LinkCard
-          title="Watch Episode 2: WARP diagnostic logs"
-          description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
-          href="/learning-paths/warp-overview-course/series/warp-basics-2/"
-        />                   
-    </CardGrid>
\ No newline at end of file
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
+		description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
+		href="/learning-paths/warp-overview-course/series/warp-basics-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: WARP diagnostic logs"
+		description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
+		href="/learning-paths/warp-overview-course/series/warp-basics-2/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/workflows-series-navigation.mdx b/src/content/partials/learning-paths/workflows-series-navigation.mdx
index 3aef6a36002ba88..f037d68638048ed 100644
--- a/src/content/partials/learning-paths/workflows-series-navigation.mdx
+++ b/src/content/partials/learning-paths/workflows-series-navigation.mdx
@@ -1,24 +1,23 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Understand Cloudflare Workflows"
-          description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
-          href="/learning-paths/workflows-course/series/workflows-1/"
-        />          
-      <LinkCard
-          title="Watch Episode 2: Monitor and batch your website data"
-          description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
-          href="/learning-paths/workflows-course/series/workflows-2/"
-        />    
-      <LinkCard
-          title="Watch Episode 3: Use cron triggers to develop time-aware applications"
-          description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
-          href="/learning-paths/workflows-course/series/workflows-3/"
-        />                          
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Understand Cloudflare Workflows"
+		description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
+		href="/learning-paths/workflows-course/series/workflows-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: Monitor and batch your website data"
+		description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
+		href="/learning-paths/workflows-course/series/workflows-2/"
+	/>
+	<LinkCard
+		title="Watch Episode 3: Use cron triggers to develop time-aware applications"
+		description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
+		href="/learning-paths/workflows-course/series/workflows-3/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
index 634c2666bff6d5b..1432141f867394c 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Restrict access for users included in an <GlossaryTooltip term="identity provider">identity provider (IdP)</GlossaryTooltip> user group for risky users. This policy ensures your security team can restrict traffic for users of whom malicious or suspicious activity was detected.
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
index 060cde6c1160533..39d1803880c83b2 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Block [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories), such as **Command and Control & Botnet** and **Malware**, based on Cloudflare's threat intelligence.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
index b9a22f0fb157e40..0a419a55b8b121b 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The Cloudflare One Client (known as the Cloudflare One Agent in mobile app stores) encrypts designated traffic from a user's device to Cloudflare's global network. In this learning path, we will first define all of your parameters and deployment rules, and then we will install and connect the client. If you prefer to start the client download now, refer to [Download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/).
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
index 087954988839621..01f20205751345a 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-* Define which users can connect devices to your Zero Trust instance.
-* Configure global and device-specific settings for the Cloudflare One Client.
-* Route user traffic through Cloudflare Gateway.
-* Route domains to a private DNS server, if required.
+- Define which users can connect devices to your Zero Trust instance.
+- Configure global and device-specific settings for the Cloudflare One Client.
+- Route user traffic through Cloudflare Gateway.
+- Route domains to a private DNS server, if required.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
index 21e92853d18e27b..f358209dc42676a 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip, Render} from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 An <GlossaryTooltip term="identity provider" link="https://www.cloudflare.com/learning/access-management/what-is-an-identity-provider/">identity provider (IdP)</GlossaryTooltip> stores and manages users' digital identities. You can integrate your existing identity provider with Cloudflare Zero Trust in order to manage user access to your private network. This requires configuration both in Cloudflare and with the identity provider itself.
 
diff --git a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
index 6af7493ea8d2e78..5317428531592d0 100644
--- a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Manually deploy the Cloudflare One Client on a test device.
-* Create an automated script to use with your organization's managed deployment tool.
-* View user traffic in Zero Trust.
+- Manually deploy the Cloudflare One Client on a test device.
+- Create an automated script to use with your organization's managed deployment tool.
+- View user traffic in Zero Trust.
diff --git a/src/content/partials/learning-paths/zero-trust/create-list.mdx b/src/content/partials/learning-paths/zero-trust/create-list.mdx
index f5cc8a1e77768f5..db39846de4a243f 100644
--- a/src/content/partials/learning-paths/zero-trust/create-list.mdx
+++ b/src/content/partials/learning-paths/zero-trust/create-list.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Gateway supports creating [lists](/cloudflare-one/reusable-components/lists/) of IPs, hostnames, or other entries to reference in your policies.
 
diff --git a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
index 5f2f956a234b5a0..d1c2be740c04bb1 100644
--- a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Device enrollment permissions determine which users can connect new devices to your organization's Cloudflare Zero Trust instance. Once the user registers their device, the Cloudflare One Client will store their identity token and use it to authenticate to services in your private network.
 
diff --git a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
index d7a5d2a680983d6..af96e5d35431904 100644
--- a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
-| Disposition | Description                                                                                                                                                                                  | Recommendation                                                             |   |
-|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---|
-| MALICIOUS   |                                 Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                |                                    Block                                   |   |
-| SUSPICIOUS  |                                             Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                             |         Research these messages internally to evaluate legitimacy.         |   |
-| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |   |
-| SPAM        |                                                                 Traffic associated with non-malicious, commercial campaigns.                                                                 |                  Route to existing Spam quarantine folder.                 |   |
-| BULK        |       Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.       |                               Monitor or tag                               |   |
\ No newline at end of file
+| Disposition | Description                                                                                                                                                                                                                                                                                                                                                                                                                             | Recommendation                                                             |     |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --- |
+| MALICIOUS   | Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                                                                                                                                                                                                                                                                                           | Block                                                                      |     |
+| SUSPICIOUS  | Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                                                                                                                                                                                                                                                                                                                    | Research these messages internally to evaluate legitimacy.                 |     |
+| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |     |
+| SPAM        | Traffic associated with non-malicious, commercial campaigns.                                                                                                                                                                                                                                                                                                                                                                            | Route to existing Spam quarantine folder.                                  |     |
+| BULK        | Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.                                                                                                                                                                                                              | Monitor or tag                                                             |     |
diff --git a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
index e6800e57f7aafd3..8a8dcfab6f7c924 100644
--- a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
+++ b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With Cloudflare Gateway, you can log and filter DNS, network, and HTTP traffic from devices running the Cloudflare One Client. This includes traffic to the public Internet and traffic directed to your private network. DNS filtering is enabled by default since the Cloudflare One Client sends DNS queries to Cloudflare's public DNS resolver, [1.1.1.1](/1.1.1.1/). To enable network and HTTP filtering, you will need to allow Cloudflare Gateway to proxy that traffic.
diff --git a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
index fd8de62a9baadd6..4c1e0192bd1e400 100644
--- a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Set up a Cloudflare account.
-* Create a Zero Trust organization to manage your devices and policies.
-* Configure an identity provider (IdP) for user authentication.
+- Set up a Cloudflare account.
+- Create a Zero Trust organization to manage your devices and policies.
+- Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/partials/learning-paths/zero-trust/install-agent.mdx b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
index 50221f53efc84d9..c0b8798b2485485 100644
--- a/src/content/partials/learning-paths/zero-trust/install-agent.mdx
+++ b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
@@ -1,32 +1,32 @@
 ---
 inputParameters: WARPsuccess
-
 ---
 
-import { Details, Markdown, Render } from "~/components"
+import { Details, Markdown, Render } from "~/components";
 
 Most admins test by manually downloading the Cloudflare One Client and enrolling in your organization's Cloudflare Zero Trust instance.
 
 ## Install the Cloudflare One Client
 
-1. First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
-2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
-  	<Render file="warp/client-orchestration-ips" product="cloudflare-one" />
+1.  First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
+2.  If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
+
+    <Render file="warp/client-orchestration-ips" product="cloudflare-one" />
 
-	For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
+    For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 
-3. Manually install the Cloudflare One Client on the device.
+3.  Manually install the Cloudflare One Client on the device.
 
-		<Details header="Window, macOS, and Linux">
+        <Details header="Window, macOS, and Linux">
 
-		<Render file="warp/enroll-desktop" product="cloudflare-one" />
+        <Render file="warp/enroll-desktop" product="cloudflare-one" />
 
-		</Details>
+        </Details>
 
-		<Details header="iOS, Android, and ChromeOS">
+        <Details header="iOS, Android, and ChromeOS">
 
-		<Render file="warp/enroll-ios-android" product="cloudflare-one" />
+        <Render file="warp/enroll-ios-android" product="cloudflare-one" />
 
-		</Details>
+        </Details>
 
 The Cloudflare One Client should show as **Connected**. {props.one}
diff --git a/src/content/partials/learning-paths/zero-trust/mdm.mdx b/src/content/partials/learning-paths/zero-trust/mdm.mdx
index d928a456aa181ac..042067aab0fd199 100644
--- a/src/content/partials/learning-paths/zero-trust/mdm.mdx
+++ b/src/content/partials/learning-paths/zero-trust/mdm.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="warp/mdm-intro" product="cloudflare-one" />
 
diff --git a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
index eb80c75bd1fbfa8..d3ea3aaab5d3ff0 100644
--- a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
+++ b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
-import { Render} from "~/components"
+import { Render } from "~/components";
 
 Split tunnel settings determine which traffic the Cloudflare One Client does and does not proxy.
 
 The Cloudflare One Client offers two different split tunnel modes:
 
-* If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
-* If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
+- If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
+- If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
 
 ## Update Split Tunnels mode
 
diff --git a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
index 5e3a0df5f6c077b..21f27878f44c392 100644
--- a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
+++ b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
@@ -1,10 +1,13 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To validate that Cloudflare is receiving traffic from a user device:
 
-<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
+<Render
+	file="gateway/verify-connectivity"
+	product="cloudflare-one"
+	params={{ one: "DNS", two: "queries" }}
+/>
diff --git a/src/content/partials/load-balancing/components-knowledge-callout.mdx b/src/content/partials/load-balancing/components-knowledge-callout.mdx
index 75cdfecec22253a..b8493c88bd03af8 100644
--- a/src/content/partials/load-balancing/components-knowledge-callout.mdx
+++ b/src/content/partials/load-balancing/components-knowledge-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This guide assumes you are familiar with the Cloudflare [Load Balancing components](/load-balancing/understand-basics/load-balancing-components/).
diff --git a/src/content/partials/load-balancing/custom-rules-definition.mdx b/src/content/partials/load-balancing/custom-rules-definition.mdx
index 87c37f08ebba3d4..49889fc8bc61ee2 100644
--- a/src/content/partials/load-balancing/custom-rules-definition.mdx
+++ b/src/content/partials/load-balancing/custom-rules-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom load balancing rules let you customize the behavior of your load balancer based on the characteristics of a request.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
index 2a826379296653d..b05bdc170e119f5 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your load balancer is attached to a hostname used for an [`MX` or `SRV` record](/load-balancing/additional-options/additional-dns-records/) — and not an `A`, `AAAA`, or `CNAME` record — its proxy mode should be **DNS-only**.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
index 85d6c2a3775c9cf..07047a05eddeed8 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS-only load balancers route traffic by returning specific IP addresses in response to a client's DNS query.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
index bc03d3b58635b6d..ebcffa45dd9ce22 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 In comparison to proxied, layer 7 load balancing, DNS-only load balancing:
 
-* Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
-* Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
-* Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
-* Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
-* Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
-* Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
-* Does not support [Private Network Load Balancing](/load-balancing/private-network/).
+- Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
+- Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
+- Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
+- Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
+- Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
+- Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
+- Does not support [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
index 5a380e226cc7c4b..b5888a2b8e97651 100644
--- a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
+++ b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Since load balancing targets are not limited to origin web servers, the term `endpoints` has been introduced. Refer to [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-other-terms/) for its use in the context of Cloudflare offerings, and to [load balancing concepts](/load-balancing/understand-basics/load-balancing-components/) or [Reference Architecture](/reference-architecture/architectures/load-balancing/) for use case examples.
diff --git a/src/content/partials/load-balancing/fallback-pools.mdx b/src/content/partials/load-balancing/fallback-pools.mdx
index 49f0595e95dc999..bac40469f252c71 100644
--- a/src/content/partials/load-balancing/fallback-pools.mdx
+++ b/src/content/partials/load-balancing/fallback-pools.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This pool is meant to be the pool of last resort, meaning that its health is not taken into account when directing traffic.
diff --git a/src/content/partials/load-balancing/health-check-diagram.mdx b/src/content/partials/load-balancing/health-check-diagram.mdx
index 568033512858810..6b2bfb5560e0f49 100644
--- a/src/content/partials/load-balancing/health-check-diagram.mdx
+++ b/src/content/partials/load-balancing/health-check-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/health-check-regions.mdx b/src/content/partials/load-balancing/health-check-regions.mdx
index cb98a0bc269813a..85b94acbc34ab57 100644
--- a/src/content/partials/load-balancing/health-check-regions.mdx
+++ b/src/content/partials/load-balancing/health-check-regions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For each option selected in a pool's **Health Monitor Regions**, Cloudflare sends health monitor requests from three separate data centers in that region.
diff --git a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
index e1379917600272c..aa5e650fec2b99b 100644
--- a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Layer 4 load balancers route traffic by forwarding traffic to certain ports or IP addresses.
@@ -9,8 +8,6 @@ Cloudflare currently only supports layer 4 load balancing as part of [Cloudflare
 
 :::note
 
-
 Since Spectrum operates at the TCP level, it does not have the information to support features like [session affinity](/load-balancing/understand-basics/session-affinity/), [custom rules](/load-balancing/additional-options/load-balancing-rules/), or caching.
 
-
 :::
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
index 9dfc53ccb56e590..5d6045bd0ac9477 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 In comparison to DNS-only load balancing, layer 7 load balancing:
 
-* Protects endpoints from DDoS attacks by hiding their IP addresses.
-* Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
-* Integrates with other Cloudflare features such as caching, Workers, and the WAF.
-* Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
-* Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
-* More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
-* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
+- Protects endpoints from DDoS attacks by hiding their IP addresses.
+- Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
+- Integrates with other Cloudflare features such as caching, Workers, and the WAF.
+- Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
+- Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
+- More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
+- Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
index 120a77b9f1486a4..78f4d9da0758f11 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Layer 7 load balancers direct traffic to specific endpoints based on information present in each HTTP/HTTPS request (HTTP headers, URI, cookies, type of data, etc.).
diff --git a/src/content/partials/load-balancing/load-balancer-create-api.mdx b/src/content/partials/load-balancing/load-balancer-create-api.mdx
index 8dbe3ed3d7b8337..9110fc3325a87d9 100644
--- a/src/content/partials/load-balancing/load-balancer-create-api.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -9,91 +8,89 @@ For a full list of properties, refer to [Create Load Balancer](/api/resources/lo
 
 :::note
 
-
 Since load balancers only exist on a zone — and not an account — you may need to get the zone `id` with the [List Zones](/api/resources/zones/methods/list/) command.
 
-
 :::
 
 <APIRequest
-  path="/zones/{zone_id}/load_balancers"
-  method="POST"
-  json={{
-    description: "Load Balancer for lb.example.com",
-    name: "lb.example.com",
-    enabled: true,
-    ttl: 30,
-    fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
-    default_pools: [
-      "17b5962d775c646f3f9725cbc7a53df4",
-      "9290f38c5d07c2e2f4df57b1f61d4196",
-      "00920f38ce07c2e2f4df50b1f61d4194"
-    ],
-    proxied: true,
-    steering_policy: "random_steering",
-    session_affinity: "cookie",
-    session_affinity_attributes: {
-      samesite: "Auto",
-      secure: "Auto",
-      drain_duration: 100,
-      zero_downtime_failover: "sticky"
-    },
-    session_affinity_ttl: 5000,
-    adaptive_routing: {
-      failover_across_pools: true
-    },
-    location_strategy: {
-      prefer_ecs: "always",
-      mode: "resolver_ip"
-    },
-    random_steering: {
-      pool_weights: {
-        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-      },
-      default_weight: 0.2
-    }
-  }}
+	path="/zones/{zone_id}/load_balancers"
+	method="POST"
+	json={{
+		description: "Load Balancer for lb.example.com",
+		name: "lb.example.com",
+		enabled: true,
+		ttl: 30,
+		fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
+		default_pools: [
+			"17b5962d775c646f3f9725cbc7a53df4",
+			"9290f38c5d07c2e2f4df57b1f61d4196",
+			"00920f38ce07c2e2f4df50b1f61d4194",
+		],
+		proxied: true,
+		steering_policy: "random_steering",
+		session_affinity: "cookie",
+		session_affinity_attributes: {
+			samesite: "Auto",
+			secure: "Auto",
+			drain_duration: 100,
+			zero_downtime_failover: "sticky",
+		},
+		session_affinity_ttl: 5000,
+		adaptive_routing: {
+			failover_across_pools: true,
+		},
+		location_strategy: {
+			prefer_ecs: "always",
+			mode: "resolver_ip",
+		},
+		random_steering: {
+			pool_weights: {
+				de90f38ced07c2e2f4df50b1f61d4194: 0.3,
+				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5,
+			},
+			default_weight: 0.2,
+		},
+	}}
 />
 
 The response contains the complete definition of the new load balancer.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "699d98642c564d2e855e9661899b7252",
-    "created_on": "2021-01-01T05:20:00.12345Z",
-    "modified_on": "2021-01-01T05:20:00.12345Z",
-    "description": "Load Balancer for lb.example.com",
-    "name": "lb.example.com",
-    "enabled": true,
-    "ttl": 30,
-    "fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
-    "default_pools": [
-      "17b5962d775c646f3f9725cbc7a53df4",
-      "9290f38c5d07c2e2f4df57b1f61d4196",
-      "00920f38ce07c2e2f4df50b1f61d4194"
-    ],
-    "proxied": true,
-    "steering_policy": "random_steering",
-    "session_affinity": "cookie",
-    "session_affinity_attributes": {
-      "samesite": "Auto",
-      "secure": "Auto",
-      "drain_duration": 100,
-      "zero_downtime_failover": "sticky"
-    },
-    "session_affinity_ttl": 5000,
-    "random_steering": {
-      "pool_weights": {
-        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-      },
-      "default_weight": 0.2
-    }
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "699d98642c564d2e855e9661899b7252",
+		"created_on": "2021-01-01T05:20:00.12345Z",
+		"modified_on": "2021-01-01T05:20:00.12345Z",
+		"description": "Load Balancer for lb.example.com",
+		"name": "lb.example.com",
+		"enabled": true,
+		"ttl": 30,
+		"fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
+		"default_pools": [
+			"17b5962d775c646f3f9725cbc7a53df4",
+			"9290f38c5d07c2e2f4df57b1f61d4196",
+			"00920f38ce07c2e2f4df50b1f61d4194"
+		],
+		"proxied": true,
+		"steering_policy": "random_steering",
+		"session_affinity": "cookie",
+		"session_affinity_attributes": {
+			"samesite": "Auto",
+			"secure": "Auto",
+			"drain_duration": 100,
+			"zero_downtime_failover": "sticky"
+		},
+		"session_affinity_ttl": 5000,
+		"random_steering": {
+			"pool_weights": {
+				"de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+			},
+			"default_weight": 0.2
+		}
+	}
 }
 ```
diff --git a/src/content/partials/load-balancing/load-balancer-create.mdx b/src/content/partials/load-balancing/load-balancer-create.mdx
index 0eddd6c4f2e92bb..d0b76484eaea2e6 100644
--- a/src/content/partials/load-balancing/load-balancer-create.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create a Public or a Private load balancer in the dashboard:
@@ -9,31 +8,31 @@ To create a Public or a Private load balancer in the dashboard:
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Public load balancer** 
+2. On the **Load Balancer Setup**, select **Public load balancer**
 
-3. Choose the website to which you want to add this load balancer. 
+3. Choose the website to which you want to add this load balancer.
 
 4. On the **Hostname** page:
-   * Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
-   * From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
-   * Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
-   * Add a description for your load balancer. 
-   * If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
-   * If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
+   - Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
+   - From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
+   - Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
+   - Add a description for your load balancer.
+   - If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
+   - If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
 
 5. Select **Next**.
 
 6. On the **Add a Pool** page:
-   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 7. Select **Next**.
 
 8. On the **Monitors** page:
-   * Review the monitors attached to your pools.
-   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   - Review the monitors attached to your pools.
+   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 9. Select **Next**.
 
@@ -44,28 +43,28 @@ To create a Public or a Private load balancer in the dashboard:
 12. Select **Next**.
 
 13. On the **Review** page:
-    * Review your configuration and make any changes.
-    * Choose whether to **Save as Draft** or **Save and Deploy**.
+    - Review your configuration and make any changes.
+    - Choose whether to **Save as Draft** or **Save and Deploy**.
 
-### Create a Private load balancer 
+### Create a Private load balancer
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Private load balancer** 
+2. On the **Load Balancer Setup**, select **Private load balancer**
 
 3. Associate your load balancer with either a Cloudflare private IP or a specified IP address and create a description for your load balancer.
 
 4. On the **Add a Pool** page:
-   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 5. Select **Next**.
 
 6. On the **Monitors** page:
-   * Review the monitors attached to your pools.
-   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   - Review the monitors attached to your pools.
+   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 7. Select **Next**.
 
@@ -74,5 +73,5 @@ To create a Public or a Private load balancer in the dashboard:
 9. Select **Next**.
 
 10. On the **Review** page:
-    * Review your configuration and make any changes.
-    * Choose whether to **Save as Draft** or **Save and Deploy**.
+    - Review your configuration and make any changes.
+    - Choose whether to **Save as Draft** or **Save and Deploy**.
diff --git a/src/content/partials/load-balancing/load-balancer-definition.mdx b/src/content/partials/load-balancing/load-balancer-definition.mdx
index 7c7f1e2775cb3b6..e955489d0848da8 100644
--- a/src/content/partials/load-balancing/load-balancer-definition.mdx
+++ b/src/content/partials/load-balancing/load-balancer-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.) or IP address.
diff --git a/src/content/partials/load-balancing/load-balancing-diagram.mdx b/src/content/partials/load-balancing/load-balancing-diagram.mdx
index 8f66f37a89cdc36..bc43dd9c4d9b564 100644
--- a/src/content/partials/load-balancing/load-balancing-diagram.mdx
+++ b/src/content/partials/load-balancing/load-balancing-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/monitor-create-api.mdx b/src/content/partials/load-balancing/monitor-create-api.mdx
index d1d69939d9bd159..cc778566aa44003 100644
--- a/src/content/partials/load-balancing/monitor-create-api.mdx
+++ b/src/content/partials/load-balancing/monitor-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -8,65 +7,61 @@ import { APIRequest } from "~/components";
 For a full list of monitor properties, refer to [Create Monitor](/api/resources/load_balancers/subresources/monitors/methods/create/). If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
 <APIRequest
-  path="/accounts/{account_id}/load_balancers/monitors"
-  method="POST"
-  json={{
-    type: "https",
-    description: "Login page monitor",
-    method: "GET",
-    path: "/health",
-    header: {
-      Host: ["example.com"],
-      "X-App-ID": ["abc123"]
-    },
-    port: 8080,
-    timeout: 3,
-    retries: 0,
-    interval: 90,
-    expected_body: "alive",
-    expected_codes: "2xx",
-    follow_redirects: true,
-    allow_insecure: true,
-    consecutive_up: 3,
-    consecutive_down: 2,
-    probe_zone: "example.com"
-  }}
+	path="/accounts/{account_id}/load_balancers/monitors"
+	method="POST"
+	json={{
+		type: "https",
+		description: "Login page monitor",
+		method: "GET",
+		path: "/health",
+		header: {
+			Host: ["example.com"],
+			"X-App-ID": ["abc123"],
+		},
+		port: 8080,
+		timeout: 3,
+		retries: 0,
+		interval: 90,
+		expected_body: "alive",
+		expected_codes: "2xx",
+		follow_redirects: true,
+		allow_insecure: true,
+		consecutive_up: 3,
+		consecutive_down: 2,
+		probe_zone: "example.com",
+	}}
 />
 
 The response contains the complete definition of the new monitor.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": ":monitor-id",
-    "created_on": "2021-01-01T05:20:00.12345Z",
-    "modified_on": "2021-01-01T05:20:00.12345Z",
-    "type": "https",
-    "description": "Login page monitor",
-    "method": "GET",
-    "path": "/health",
-    "header": {
-      "Host": [
-        "example.com"
-      ],
-      "X-App-ID": [
-        "abc123"
-      ]
-    },
-    "port": 8080,
-    "timeout": 3,
-    "retries": 0,
-    "interval": 90,
-    "expected_body": "alive",
-    "expected_codes": "2xx",
-    "follow_redirects": true,
-    "allow_insecure": true,
-    "consecutive_up": 3,
-    "consecutive_down": 2,
-    "probe_zone": "example.com"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": ":monitor-id",
+		"created_on": "2021-01-01T05:20:00.12345Z",
+		"modified_on": "2021-01-01T05:20:00.12345Z",
+		"type": "https",
+		"description": "Login page monitor",
+		"method": "GET",
+		"path": "/health",
+		"header": {
+			"Host": ["example.com"],
+			"X-App-ID": ["abc123"]
+		},
+		"port": 8080,
+		"timeout": 3,
+		"retries": 0,
+		"interval": 90,
+		"expected_body": "alive",
+		"expected_codes": "2xx",
+		"follow_redirects": true,
+		"allow_insecure": true,
+		"consecutive_up": 3,
+		"consecutive_down": 2,
+		"probe_zone": "example.com"
+	}
 }
 ```
diff --git a/src/content/partials/load-balancing/monitor-create.mdx b/src/content/partials/load-balancing/monitor-create.mdx
index e886aac579f8934..cba41c6a75cd948 100644
--- a/src/content/partials/load-balancing/monitor-create.mdx
+++ b/src/content/partials/load-balancing/monitor-create.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can create a monitor within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Monitors** tab:
 
diff --git a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
index 203ada096f2b360..000c0980eda9bc6 100644
--- a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
+++ b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **All Data Centers (Enterprise only)**
@@ -17,10 +16,8 @@ Three health monitor probes are sent from each specified region within the pool
 
 :::caution
 
-
 Because of how Cloudflare checks health from [multiple regions](#health-monitor-regions), adding multiple regions — or choosing to check health from **All Data Centers** — can send a lot of traffic to your endpoint.
 
 The same problem can occur when setting low values for a monitor's **Interval**.
 
-
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/load-balancing/monitor-prepare-server.mdx b/src/content/partials/load-balancing/monitor-prepare-server.mdx
index cac096756d634a6..40b7618385d0835 100644
--- a/src/content/partials/load-balancing/monitor-prepare-server.mdx
+++ b/src/content/partials/load-balancing/monitor-prepare-server.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with [Cloudflare IP addresses](https://www.cloudflare.com/ips).
@@ -9,8 +8,6 @@ Each health monitor has the HTTP user-agent of `"Mozilla/5.0 (compatible; Cloudf
 
 :::caution
 
-
 If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our [Monitor troubleshooting guide](/load-balancing/troubleshooting/load-balancing-faq/#why-is-my-endpoint-or-pool-considered-unhealthy).
 
-
 :::
diff --git a/src/content/partials/load-balancing/monitor-settings-basic.mdx b/src/content/partials/load-balancing/monitor-settings-basic.mdx
index 61c55dcb0698619..48d2f9414f6707b 100644
--- a/src/content/partials/load-balancing/monitor-settings-basic.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-basic.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* **Type**: The protocol to use for health monitors
-  * *Non-enterprise customers*: Choose **HTTP**, **HTTPS**, or **TCP**.
-  * *Enterprise customers*: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
-* **Path**: The endpoint path to run health monitor requests against
-* **Port**: The destination port for health monitors
+- **Type**: The protocol to use for health monitors
+  - _Non-enterprise customers_: Choose **HTTP**, **HTTPS**, or **TCP**.
+  - _Enterprise customers_: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
+- **Path**: The endpoint path to run health monitor requests against
+- **Port**: The destination port for health monitors
diff --git a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
index 5ea1696866dbf6b..d6ca1888d5c5948 100644
--- a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 :::note[Note]
 
-
 To increase confidence in pool status, you can also increase the `consecutive_up` and `consecutive_down` fields when [creating a monitor with the API](/api/resources/load_balancers/subresources/monitors/methods/create/).
 
 To become healthy or unhealthy, monitored endpoints must pass this health monitor request the consecutive number of times specified in these parameters.
 
-
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-definition.mdx b/src/content/partials/load-balancing/origin-steering-definition.mdx
index ff95cda09a041f0..41f06c64c7d903e 100644
--- a/src/content/partials/load-balancing/origin-steering-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-definition.mdx
@@ -1,19 +1,16 @@
 ---
 {}
-
 ---
 
 Endpoint steering customizes how each [pool](/load-balancing/pools/) distributes requests to its associated endpoints.
 
 These distributions are a combination of two properties:
 
-* The endpoint steering [policy](#policies) chosen for your pool.
-* The [weights](#weights) assigned to each endpoint.
+- The endpoint steering [policy](#policies) chosen for your pool.
+- The [weights](#weights) assigned to each endpoint.
 
 :::note
 
-
 If an endpoint [becomes unhealthy](/load-balancing/understand-basics/health-details/), your pool will also re-balance traffic according to its endpoint steering policy.
 
-
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-policies.mdx b/src/content/partials/load-balancing/origin-steering-policies.mdx
index f1231eacca1c19e..3588f6aa482ccc6 100644
--- a/src/content/partials/load-balancing/origin-steering-policies.mdx
+++ b/src/content/partials/load-balancing/origin-steering-policies.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you [create a pool](/load-balancing/pools/create-pool/), you have to choose an option for **Endpoint Steering**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
index 02f56f65d616a1b..04b243f9c170afd 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The weight assigned to an endpoint controls the percentage of pool traffic sent to that endpoint. By default, all endpoints within a pool have a weight of **1**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
index 003b326d282ef75..55e5f89bf7d1d0a 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you choose **Hash** for your **Endpoint Steering** or enable [session affinity](/load-balancing/understand-basics/session-affinity/), these options can affect traffic distribution.
diff --git a/src/content/partials/load-balancing/pool-create.mdx b/src/content/partials/load-balancing/pool-create.mdx
index c6b72f1a6076a14..198bbcd758d3fd7 100644
--- a/src/content/partials/load-balancing/pool-create.mdx
+++ b/src/content/partials/load-balancing/pool-create.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can create a pool within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Pools** tab:
 
@@ -12,24 +11,22 @@ You can create a pool within the [load balancer workflow](/load-balancing/load-b
 2. Select the **Pools** tab and then **Create pool**.
 
 3. For your pool, enter the following information:
-   * A name (must be unique)
-   * A description to provide more detail on the name
-   * A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
+   - A name (must be unique)
+   - A description to provide more detail on the name
+   - A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
 
 4. For each endpoint, enter the following information:
-   * A name (must be unique)
-   * The endpoint address or associated hostname
-   * (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
-   * A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
-   * (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
-   * (Optional) The destination port to which the traffic will be served.
+   - A name (must be unique)
+   - The endpoint address or associated hostname
+   - (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
+   - A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
+   - (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
+   - (Optional) The destination port to which the traffic will be served.
 
 :::note[Note]
 
-
 If your endpoint is a website or application hosted on [Cloudflare Pages](/pages/), you will need to fill in the host header field with the project domain for it to resolve correctly.
 
-
 :::
 
 5. Repeat this process for additional endpoints in the pool.
@@ -37,9 +34,9 @@ If your endpoint is a website or application hosted on [Cloudflare Pages](/pages
 6. (Optional) Set up coordinates for [Proximity Steering](/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering/) on the pool.
 
 7. On the pool, update the following information:
-   * **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
-   * **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
-   * **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
-   * **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
+   - **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
+   - **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
+   - **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
+   - **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
 
 8. When finished, select **Save**.
diff --git a/src/content/partials/load-balancing/pool-health-threshold.mdx b/src/content/partials/load-balancing/pool-health-threshold.mdx
index 825e481e8f68a55..ef2bac2c25ed613 100644
--- a/src/content/partials/load-balancing/pool-health-threshold.mdx
+++ b/src/content/partials/load-balancing/pool-health-threshold.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered *Healthy* and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
+The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered _Healthy_ and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
diff --git a/src/content/partials/load-balancing/region-mapping.mdx b/src/content/partials/load-balancing/region-mapping.mdx
index 128fad39ca78170..1bd65acff2b56cc 100644
--- a/src/content/partials/load-balancing/region-mapping.mdx
+++ b/src/content/partials/load-balancing/region-mapping.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | Region code | Region name            |
diff --git a/src/content/partials/load-balancing/route-production-traffic.mdx b/src/content/partials/load-balancing/route-production-traffic.mdx
index 3e1b688df82eeb7..5da9c7169712872 100644
--- a/src/content/partials/load-balancing/route-production-traffic.mdx
+++ b/src/content/partials/load-balancing/route-production-traffic.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Now that you have set up your load balancer and verified everything is working correctly, you can put the load balancer on a live domain or subdomain:
@@ -8,13 +7,11 @@ Now that you have set up your load balancer and verified everything is working c
 1. If you update your pools and monitors, review the pool health again to make sure everything is working as expected.
 2. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 3. Configure your load balancer to receive production traffic, which could involve either:
-   * Editing the **Hostname** of your existing load balancer.
-   * Updating the `CNAME` record sending traffic to your load balancer.
+   - Editing the **Hostname** of your existing load balancer.
+   - Updating the `CNAME` record sending traffic to your load balancer.
 
 :::note
 
-
 If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [origin rule](/rules/origin-rules/features/#dns-record).
 
-
 :::
diff --git a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
index b6398dd605663ec..8c0d3b883dc0ee3 100644
--- a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
+++ b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Session affinity automatically directs requests from the same client to the same endpoint:
@@ -25,8 +24,8 @@ Session affinity automatically directs requests from the same client to the same
      end
 ```
 
-<br/>
+<br />
 
-All cookie-based sessions default to 23 hours unless you set a custom session *Time to live* (TTL).
+All cookie-based sessions default to 23 hours unless you set a custom session _Time to live_ (TTL).
 
 The session cookie is secure when [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) is enabled. Additionally, HttpOnly is always enabled for the cookie to prevent cross-site scripting attacks.
diff --git a/src/content/partials/load-balancing/session-affinity-definition.mdx b/src/content/partials/load-balancing/session-affinity-definition.mdx
index 457703c7c032ae8..5b2531052f2e4ae 100644
--- a/src/content/partials/load-balancing/session-affinity-definition.mdx
+++ b/src/content/partials/load-balancing/session-affinity-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you enable session affinity, your load balancer directs all requests from a particular end user to a specific endpoint. This continuity preserves information about the user session — such as items in their shopping cart — that might otherwise be lost if requests were spread out among multiple servers.
diff --git a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
index dfe52808eb3b9c0..4daefe6d4a289dd 100644
--- a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
+++ b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
+- Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
 
-* UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
+- UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
diff --git a/src/content/partials/load-balancing/test-domain-setup.mdx b/src/content/partials/load-balancing/test-domain-setup.mdx
index 8a7c754c580a135..88b53616839ade6 100644
--- a/src/content/partials/load-balancing/test-domain-setup.mdx
+++ b/src/content/partials/load-balancing/test-domain-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Instead of starting on your production domain, you likely should create a load balancer on a test or staging domain. This may involve temporary changes to your monitors and pools, depending on your infrastructure setup.
diff --git a/src/content/partials/load-balancing/traffic-steering-definition.mdx b/src/content/partials/load-balancing/traffic-steering-definition.mdx
index 471d03f63fbe154..84b6a196eba9451 100644
--- a/src/content/partials/load-balancing/traffic-steering-definition.mdx
+++ b/src/content/partials/load-balancing/traffic-steering-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Global traffic steering policies decide how a load balancer routes traffic to attached and healthy pools.
diff --git a/src/content/partials/load-balancing/unexpected-health-statuses.mdx b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
index cc03b813fa18383..9bd3a6cad5b730a 100644
--- a/src/content/partials/load-balancing/unexpected-health-statuses.mdx
+++ b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 If you notice that healthy pools are being marked unhealthy:
 
-* Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
-* Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
+- Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
+- Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
diff --git a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
index 8e1a71d8ff5616f..d0ec34fe725e179 100644
--- a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
+++ b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
@@ -1,13 +1,11 @@
 ---
 {}
-
 ---
 
 When a pool reaches **Critical** health, your load balancer will begin diverting traffic according to its [Traffic steering policy](/load-balancing/understand-basics/traffic-steering/steering-policies/):
 
-* **Off**:
-
-  * If the active pool becomes unhealthy, traffic goes to the next pool in order.
-  * If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
+- **Off**:
+  - If the active pool becomes unhealthy, traffic goes to the next pool in order.
+  - If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
 
-* **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
+- **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
diff --git a/src/content/partials/logs/check-log-retention.mdx b/src/content/partials/logs/check-log-retention.mdx
index 6a5b9c2e8254154..13b4c54b32aacc3 100644
--- a/src/content/partials/logs/check-log-retention.mdx
+++ b/src/content/partials/logs/check-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/disable-log-retention.mdx b/src/content/partials/logs/disable-log-retention.mdx
index 3a89db7ac7c39e0..f13215928cc87a1 100644
--- a/src/content/partials/logs/disable-log-retention.mdx
+++ b/src/content/partials/logs/disable-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-log-retention.mdx b/src/content/partials/logs/enable-log-retention.mdx
index 7d9a9ac4a7a3e7c..46ea7dc9617f844 100644
--- a/src/content/partials/logs/enable-log-retention.mdx
+++ b/src/content/partials/logs/enable-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-logpush-job.mdx b/src/content/partials/logs/enable-logpush-job.mdx
index 9c86c3c83faa49b..f571da2cfbdba5a 100644
--- a/src/content/partials/logs/enable-logpush-job.mdx
+++ b/src/content/partials/logs/enable-logpush-job.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
- 
+
    For account: <DashButton url="/?to=/:account/logs" />
- 
+
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
diff --git a/src/content/partials/logs/enable-read-permissions.mdx b/src/content/partials/logs/enable-read-permissions.mdx
index b2b55619a3f5903..0782c628cb0ea41 100644
--- a/src/content/partials/logs/enable-read-permissions.mdx
+++ b/src/content/partials/logs/enable-read-permissions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Ensure **Log Share** permissions are enabled, before attempting to read or configure a Logpush job. For more information refer to the [Roles section](/logs/logpush/permissions/#roles).
diff --git a/src/content/partials/logs/filtering-limitations.mdx b/src/content/partials/logs/filtering-limitations.mdx
index 2d32cc7f88aa921..1f28334e5fc8c7b 100644
--- a/src/content/partials/logs/filtering-limitations.mdx
+++ b/src/content/partials/logs/filtering-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/networking-services/account-id-api-key.mdx b/src/content/partials/networking-services/account-id-api-key.mdx
index c2532c7e6b0a36c..ae09eb187dd2510 100644
--- a/src/content/partials/networking-services/account-id-api-key.mdx
+++ b/src/content/partials/networking-services/account-id-api-key.mdx
@@ -1,16 +1,18 @@
 ---
 {}
-
 ---
 
 import { Markdown } from "~/components";
 
-{/* 
-  Conditional rendering based on showSiteId prop:
-  - When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
-  - When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
+{/\*
+Conditional rendering based on showSiteId prop:
+
+- When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
+- When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
   The ternaries only render the differing prefix and suffix to avoid content duplication.
-*/}
-:::note
-<Markdown text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`} />
-:::
+  \*/}
+  :::note
+  <Markdown
+  	text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`}
+  />
+  :::
diff --git a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
index 665ea039cad5541..e7f64d2d3b9bca3 100644
--- a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
+++ b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
@@ -9,4 +9,4 @@ When you set up an alert for your site, you will be notified when there is an is
 To set up health alerts:
 
 1. Configure <a href={props.magicTunnelHcsURL}>Tunnel health alerts</a> across all of the tunnels associated with each {props.productName} site.
-2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
\ No newline at end of file
+2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
diff --git a/src/content/partials/networking-services/analytics/site-analytics.mdx b/src/content/partials/networking-services/analytics/site-analytics.mdx
index 5f9269dba906210..03a99eb68bf605b 100644
--- a/src/content/partials/networking-services/analytics/site-analytics.mdx
+++ b/src/content/partials/networking-services/analytics/site-analytics.mdx
@@ -7,51 +7,45 @@ params:
   - setGeoCoordinatesURL
 ---
 
-
-
-import { Details, Markdown, DashButton } from "~/components"
+import { Details, Markdown, DashButton } from "~/components";
 
 After adding your sites, the {props.networkOverviewPageName} section of the dashboard provides a summary of the connectivity status and traffic analytics for all your sites. This is a great place to start if you receive a Cloudflare WAN alert, need to begin the troubleshooting process, or are performing routine monitoring. <Markdown text={props.instructions} />
 
 {props.networkOverviewPageName} has the following data types available:
 
 <Details header="Geographic map summary">
-	- [Aggregate Cloudflare WAN site health](#site-health)
-	- [Cloudflare WAN availability status for sites](#no-status-available)
-	- [Cloudflare WAN site geographic location](#no-location-set)
+	- [Aggregate Cloudflare WAN site health](#site-health) - [Cloudflare WAN
+	availability status for sites](#no-status-available) - [Cloudflare WAN site
+	geographic location](#no-location-set)
 </Details>
 
 <Details header="Cloudflare WAN site data table">
-	- Site Name
-	- Site Health
-	- Site Tunnel Names
-	- Site Tunnel Statuses
-	- Site Traffic Sent
-	- Site Traffic Received
+	- Site Name - Site Health - Site Tunnel Names - Site Tunnel Statuses - Site
+	Traffic Sent - Site Traffic Received
 </Details>
 
 <Details header="Cloudflare WAN site data">
-	- Traffic Sent by Tunnel
-	- Traffic Received by Tunnel
+	- Traffic Sent by Tunnel - Traffic Received by Tunnel
 </Details>
 
 To start using network overview:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **${props.networkOverviewPageName}**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
+    <DashButton url="/?to=/:account/networking-insights/health" />
+    </>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
-	</>
 )
 }
 
@@ -83,7 +77,6 @@ The status of a site refers to its health. If your sites show a **No status avai
 
 The dashboard displays the number of sites with no location set, meaning sites for which you did not set up a geographic location. To add a location to a site, find the site you want to add location to, and select **no location set** to edit its location settings. Refer to <a href={props.setGeoCoordinatesURL}>Set geographic coordinates</a> for more information.
 
-
 ### Traffic overview
 
 Traffic overview aggregates all Cloudflare WAN sites configured in your account. Here, you can check summary information about each site like:
@@ -91,4 +84,4 @@ Traffic overview aggregates all Cloudflare WAN sites configured in your account.
 - Site status
 - Traffic sent and received
 
-Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
\ No newline at end of file
+Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
diff --git a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
index fb6b8b613c66bea..9388b0a604a3311 100644
--- a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
+++ b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
@@ -30,7 +30,7 @@ The following table provides a high-level comparison of all connectivity options
 | [Cloudflare Tunnel](#cloudflare-tunnel) | HTTP/2, QUIC | Off-ramp only | Software daemon (`cloudflared`) on server | Exposing private applications without a public IP |
 | [Cloudflare One Client](#cloudflare-one-client) | MASQUE (default), WireGuard | Bidirectional | Client software on end-user devices | Securing remote workforce devices |
 | [Cloudflare Mesh](#cloudflare-mesh) | MASQUE | Bidirectional | Software client on Linux host | Connecting sites with IoT or VoIP devices |
-| [DNS locations](#dns-locations) |  DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration  | Filtering DNS traffic without device agents |
+| [DNS locations](#dns-locations) | DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration | Filtering DNS traffic without device agents |
 | [Proxy endpoints](#proxy-endpoints) | HTTP/HTTPS | On-ramp only | Browser PAC file configuration | Filtering web traffic without device agents |
 | [Clientless Web Isolation](#clientless-web-isolation) | HTTP/HTTPS | On-ramp only | Prefixed URL with Access authentication | Secure web access for unmanaged devices |
 | [GRE tunnels](#gre-tunnels) | GRE | Bidirectional | Network tunnel from router or firewall | Connecting sites with existing network hardware |
@@ -97,9 +97,9 @@ DNS locations allow you to filter DNS traffic from networks without deploying th
 
 DNS locations support multiple endpoint types:
 
-* **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
-* **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
-* **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
+- **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
+- **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
+- **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
 
 Use DNS locations when you need to filter DNS traffic for an entire office or network, per device without installing agents on devices, or integrate with existing network infrastructure.
 
@@ -119,8 +119,8 @@ Proxy endpoints allow you to apply Cloudflare Gateway HTTP policies without inst
 
 Cloudflare One supports two types of proxy endpoints:
 
-* **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
-* **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
+- **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
+- **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
 
 Use proxy endpoints when you need to filter web traffic without device agents, integrate with existing proxy infrastructure, or deploy Gateway alongside other security tools.
 
@@ -283,7 +283,7 @@ The connectivity options on this page connect your private infrastructure, sites
 
 - **Non-HTTP traffic** (TCP/UDP protocols such as gaming, email, or custom services) — refer to [Spectrum](/spectrum/).
 - **Network-level DDoS protection** (for on-premises, cloud-hosted, and hybrid networks) — refer to [Magic Transit](/magic-transit/).
-:::
+  :::
 
 ### Cloudflare One recommendations by team
 
@@ -301,14 +301,14 @@ The team driving your Cloudflare One connectivity project influences which optio
 
 Cloudflare Mesh and Cloudflare One Appliance both provide site-level connectivity, but serve different deployment scenarios.
 
-| Aspect | Cloudflare Mesh | Cloudflare One Appliance |
-| ---- | ---- | ---- |
-| **Protocol** | MASQUE | IPsec |
-| **Deployment model** | Software on Linux host (can run alongside other workloads) | Dedicated hardware appliance or virtual machine |
-| **Best for** | Cloud VPCs, development environments, smaller deployments with an available Linux host | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
-| **Platform support** | Linux only (x86_64, ARM64). Currently in beta. | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox) |
-| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site |
-| **Management** | Configured as a device in the Cloudflare One Client settings | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning |
+| Aspect                | Cloudflare Mesh                                                                                                         | Cloudflare One Appliance                                                           |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| **Protocol**          | MASQUE                                                                                                                  | IPsec                                                                              |
+| **Deployment model**  | Software on Linux host (can run alongside other workloads)                                                              | Dedicated hardware appliance or virtual machine                                    |
+| **Best for**          | Cloud VPCs, development environments, smaller deployments with an available Linux host                                  | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
+| **Platform support**  | Linux only (x86_64, ARM64). Currently in beta.                                                                          | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox)                |
+| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site                                     |
+| **Management**        | Configured as a device in the Cloudflare One Client settings                                                            | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning      |
 
 Use Cloudflare Mesh when you need lightweight, software-only connectivity for cloud workloads or sites where a Linux host is available. Use Cloudflare One Appliance when you need enterprise-grade throughput, high availability, or integration with existing network infrastructure.
 
@@ -457,7 +457,8 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)
 - [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)
 - [Cloudflare WAN](/cloudflare-wan/)
-- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of supported on-ramps
+- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of
+  supported on-ramps
 - [Multi-Cloud Networking](/multi-cloud-networking/) - Automate cloud VPC connectivity
 - [Magic Transit](/magic-transit/)
 - <a href={props.connectorURL}>Cloudflare One Appliance</a>
@@ -467,4 +468,4 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) - Filter web traffic using PAC files
 - [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) - Secure web access without device agents
 
-For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/). 
+For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
index 18c9671ea9ce7f4..d436a168d8d8c4c 100644
--- a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
@@ -15,10 +15,11 @@ VeloCloud has a high availability mechanism that allows customers to specify one
 Cloudflare WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for `<account_id>`, `<tunnel_id>`, and the FQDN wildcard before running the API call.
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
-  method="PATCH"
-  json={{
-    "custom_remote_identities":
-			{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
-  }}
+	url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
+	method="PATCH"
+	json={{
+		custom_remote_identities: {
+			fqdn_id: "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com",
+		},
+	}}
 />
diff --git a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
index c7cfca556c7a735..ae7c5d5a52b3fa7 100644
--- a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
@@ -64,11 +64,17 @@ The list of prerequisites below is only for customers planning to connect manual
 
 ##### GRE tunnels as off-ramp
 
-<Render file="cloudflare-wan/mtu-mss/mss-clamping-gre" product="networking-services" />
+<Render
+	file="cloudflare-wan/mtu-mss/mss-clamping-gre"
+	product="networking-services"
+/>
 
 ##### IPsec tunnels
 
-<Render file="cloudflare-wan/mtu-mss/mss-clamping-ipsec" product="networking-services"/>
+<Render
+	file="cloudflare-wan/mtu-mss/mss-clamping-ipsec"
+	product="networking-services"
+/>
 
 :::caution[Important]
 Refer to your device documentation to check if it sets IPsec MSS clamping automatically. If that is not the case and you are using IPsec inside GRE, you have to set MSS clamp manually.
@@ -81,4 +87,4 @@ Refer to <a href={props.mtuReferenceURL}>Maximum transmission unit and maximum s
 <Render
 	file="prerequisites/router-vendor-guidelines-mss-settings-origin"
 	product="networking-services"
-/>
\ No newline at end of file
+/>
diff --git a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
index fc3cadd24324184..027327c70df8bf4 100644
--- a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
@@ -6,4 +6,4 @@ If your network has multiple paths to the same destination — for example, redu
 
 Cloudflare WAN (formerly Magic WAN) uses Private Network Load Balancing, which balances traffic across your private network endpoints. It supports both on-ramping (traffic entering Cloudflare's network) and off-ramping (traffic exiting to your sites).
 
-Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
\ No newline at end of file
+Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
index 361286f6db723bf..031870b0e53efd0 100644
--- a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
@@ -24,41 +24,41 @@ params:
   - oracleUrl
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) is compatible with any device that supports <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> with the <a href={props.supportedConfigurationParametersUrl}>supported configuration parameters</a> or supports <GlossaryTooltip term="GRE tunnel">GRE</GlossaryTooltip>.
 
 The matrix below includes example devices and links to the integration guides.
 
-| Appliance | GRE tunnel | IPsec tunnel |
-| --- | --- | --- |
-| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a> |✅ | ✅ |
-| Cisco ASA | Compatibility on roadmap | Specifications compatible[^1] |
-| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a> | ✅ | ✅ |
-| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a> | - | ✅ |
-| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>  | ✅ | ✅ |
-| <a href={props.fortinetUrl}>Fortinet</a>| Specifications compatible[^1] | ✅ |
-| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a> | - | ✅ |
-| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a> | Specifications compatible[^1] | ✅ |
-| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅ |
-| <a href={props.pfsenseUrl}>pfSense</a>| ✅ | ✅ |
-| Prisma SD-WAN (Palo Alto) | Specifications compatible[^1] | Specifications compatible[^1] |
-| Riverbed  | Specifications compatible[^1] | Specifications compatible[^1] |
-| <a href={props.sonicwallUrl}>SonicWall</a>| - | ✅ |
-| <a href={props.sophosFirewallUrl}>Sophos Firewall</a> | ✅ | ✅ |
-| <a href={props.strongswanUrl}>strongSwan</a> | - | ✅ |
-| <a href={props.ubiquitiUrl}>Ubiquiti</a> | - | ✅ |
-| <a href={props.velocloudUrl}>Velocloud</a> | - | ✅ |
-| Versa  | Specifications compatible[^1] | Compatibility on roadmap |
-| <a href={props.vyosUrl}>VyOS</a>| ✅ | ✅ |
-| <a href={props.yamahaUrl}>Yamaha RTX Router</a> | - | ✅ |
+| Appliance                                                                   | GRE tunnel                    | IPsec tunnel                  |
+| --------------------------------------------------------------------------- | ----------------------------- | ----------------------------- |
+| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a>                   | ✅                            | ✅                            |
+| Cisco ASA                                                                   | Compatibility on roadmap      | Specifications compatible[^1] |
+| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a>                              | ✅                            | ✅                            |
+| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a>   | -                             | ✅                            |
+| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>                              | ✅                            | ✅                            |
+| <a href={props.fortinetUrl}>Fortinet</a>                                    | Specifications compatible[^1] | ✅                            |
+| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a>                  | -                             | ✅                            |
+| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a>  | Specifications compatible[^1] | ✅                            |
+| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅                            |
+| <a href={props.pfsenseUrl}>pfSense</a>                                      | ✅                            | ✅                            |
+| Prisma SD-WAN (Palo Alto)                                                   | Specifications compatible[^1] | Specifications compatible[^1] |
+| Riverbed                                                                    | Specifications compatible[^1] | Specifications compatible[^1] |
+| <a href={props.sonicwallUrl}>SonicWall</a>                                  | -                             | ✅                            |
+| <a href={props.sophosFirewallUrl}>Sophos Firewall</a>                       | ✅                            | ✅                            |
+| <a href={props.strongswanUrl}>strongSwan</a>                                | -                             | ✅                            |
+| <a href={props.ubiquitiUrl}>Ubiquiti</a>                                    | -                             | ✅                            |
+| <a href={props.velocloudUrl}>Velocloud</a>                                  | -                             | ✅                            |
+| Versa                                                                       | Specifications compatible[^1] | Compatibility on roadmap      |
+| <a href={props.vyosUrl}>VyOS</a>                                            | ✅                            | ✅                            |
+| <a href={props.yamahaUrl}>Yamaha RTX Router</a>                             | -                             | ✅                            |
 
-| VPN | GRE tunnel | IPsec tunnel |
-| --- | --- | --- |
-| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | - | ✅ |
-| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>          | - | ✅ |
-| <a href={props.azureUrl}>Azure VPN Gateway</a>                 | - | ✅ |
-| <a href={props.googleUrl}>GCP Cloud VPN</a>                    | - | ✅ |
-| <a href={props.oracleUrl}>Oracle Cloud</a> 										| - | ✅ |
+| VPN                                                           | GRE tunnel | IPsec tunnel |
+| ------------------------------------------------------------- | ---------- | ------------ |
+| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | -          | ✅           |
+| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>         | -          | ✅           |
+| <a href={props.azureUrl}>Azure VPN Gateway</a>                | -          | ✅           |
+| <a href={props.googleUrl}>GCP Cloud VPN</a>                   | -          | ✅           |
+| <a href={props.oracleUrl}>Oracle Cloud</a>                    | -          | ✅           |
 
 [^1]: Specifications compatible per vendor documentation
diff --git a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
index 2c7ce55ec60f37e..2b8dae020681cee 100644
--- a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
@@ -7,4 +7,4 @@ Once your traffic flows through Cloudflare's network, you can apply security pol
 
 **[Cloudflare Network Firewall](/cloudflare-network-firewall/)** filters traffic at layers 3 and 4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/) — the network and transport layers. You can allow or block traffic based on packet characteristics such as source and destination IP addresses, ports, protocols, and packet length. All Cloudflare WAN customers have <a href="/cloudflare-network-firewall/plans/">automatic access to Cloudflare Network Firewall</a>.
 
-**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
\ No newline at end of file
+**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
index 51ffc512d5a6a49..d4b5c75a6d6e558 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
@@ -37,7 +37,7 @@ Additionally, you also need to configure the necessary route table entries for t
 
 5. Take note of the **IP address** you chose, as this corresponds to the customer endpoint IP that you will need to configure on the Cloudflare side of the IPsec tunnel.
 
-6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**.  You will need it to create the IPsec tunnel on Cloudflare's side.
+6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**. You will need it to create the IPsec tunnel on Cloudflare's side.
 
 7. In **Inside IPv4 CIDR**, AWS enforces that only a `/30` block within the `169.254.0.0/16` range can be used. To accommodate this, Cloudflare supports a subset of this IP block. Namely, Cloudflare supports `169.254.240.0/20` to be assigned as the IPsec tunnel's (internal) interface IPs. This example will use `169.254.244.0/30` as the CIDR block for the IPsec tunnel: `169.254.244.1` for the AWS side of the tunnel, and `169.254.244.2` for the Cloudflare side of the tunnel.
 
@@ -84,7 +84,7 @@ After configuring the AWS transit gateway VPN connection and the tunnel as menti
 
 ### Static routes
 
-The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of  `192.168.192.0/26`, you should use it as the prefix for your static route.
+The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of `192.168.192.0/26`, you should use it as the prefix for your static route.
 
 To create a static route:
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
index 2683c003c5db069..58bcc4e8130ad91 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
@@ -36,7 +36,7 @@ Using traditional hub and spoke terminology, a Virtual WAN Hub deployed within a
 4. Select **Create**. Note that the deployment time for the vWAN Hub and VPN Gateway may take 30 minutes or more.
 5. After the VPN Gateway has finished provisioning, go to **Virtual WAN** > **Hubs** > **Your vHub** > **Connectivity** > **VPN (Site to site)**.
 6. In the **Essentials** dropdown select the VPN Gateway listed.
-7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and  `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
+7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
 
 ### 3. Create a VPN site
 
@@ -128,17 +128,17 @@ To create a **VPN Gateway Connection**:
 Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the <a href={props.cloudflareDocumentationUrl}>Cloudflare documentation</a>.
 
 1. **PSK**: Provide the PSK generated by Cloudflare for your IPsec tunnels.
-2. **Protocol**: *IKEv2*
-3. **IPsec**: *Custom*
+2. **Protocol**: _IKEv2_
+3. **IPsec**: _Custom_
    1. **IPsec SA lifetime in seconds**: 28800
    2. **IKE Phase 1**
-      1. **Encryption**: *AES256*
-      2. **Integrity/PRF**: *SHA256*
-      3. **DH Group**: *ECP384*
+      1. **Encryption**: _AES256_
+      2. **Integrity/PRF**: _SHA256_
+      3. **DH Group**: _ECP384_
    3. **IKE Phase 2(IPsec)**
-      1. **IPsec Encryption**: *AES256*
-      2. **IPsec Integrity**: *SHA256*
-      3. **PFS Group**: *ECP384*
+      1. **IPsec Encryption**: _AES256_
+      2. **IPsec Integrity**: _SHA256_
+      3. **PFS Group**: _ECP384_
    4. **Propagate Default Route:** **Disable**
    5. **Use policy based traffic selector**: **Disable**
    6. **Connection mode**: **Initiator Only**
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
index 9a13c91be0214a0..07fb95463263fea 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
@@ -201,7 +201,6 @@ Use the CLI to configure these settings:
 ip route 192.168.1.0 255.255.255.0 tunnel 2
 ```
 
-
 ## Connection test
 
 ### IPsec status
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
index b19e899b9966bbf..64e945e0798b80d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
@@ -42,12 +42,10 @@ By default, the static routes are defined with the priority set to `100`. Cloudf
 
 1. Follow the <a href={props.configureStaticRoutesUrl}>Configure static routes</a> instructions to create a static route.
 2. For the first route, ensure the following settings are defined:
-
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).
 
 3. For the second route, ensure the following settings are defined:
-
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the second IPsec tunnel defined in the previous section.
    - **Tunnel/Next hop**: Select your second tunnel (Tunnel 02 of 02).
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
index 74c35ae14467fa1..c9dfa4d0c897b6d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ## Test Environment
 
-| **Field**                          | **Value**                                      |
-| ---------------------------------- | ---------------------------------------------- |
-| Vendor                             | HPE Juniper Networking                         |
-| Model                              | SRX 320                                        |
-| Release                            | JUNOS 23.4R2-S3.9                              |
-| Date Tested                        | March 2026                                     |
+| **Field**   | **Value**              |
+| ----------- | ---------------------- |
+| Vendor      | HPE Juniper Networking |
+| Model       | SRX 320                |
+| Release     | JUNOS 23.4R2-S3.9      |
+| Date Tested | March 2026             |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**                                      |
-| ---------------------------------- | ---------------------------------------------- |
-| Traffic Selection Criteria         | Route-Based VPN                                |
-| Routing                            | Static                                         |
-| Redundant Tunnels                  | Yes                                            |
-| Tunnel Load Balancing              | Active/Active                                  |
-| IKE Version                        | IKEv2                                          |
-| Authentication                     | Pre-Shared Key                                 |
-| Anti-Replay Protection             | Disabled                                       |
-| NAT Traversal (NAT-T)              | Not Tested                                     |
-| NAT-T Port                         | Not Applicable                                 |
-| Phase 1 - DH-Group                 | Group 20                                       |
-| Phase 1 - Encryption               | AES-256-CBC                                    |
-| Phase 1 - Authentication/Integrity | SHA-256                                        |
-| Phase 2 - DH-Group                 | Group 20                                       |
-| Phase 2 - Transport                | ESP                                            |
-| Phase 2 - Encryption               | AES-256-CBC                                    |
+| **Field**                          | **Value**       |
+| ---------------------------------- | --------------- |
+| Traffic Selection Criteria         | Route-Based VPN |
+| Routing                            | Static          |
+| Redundant Tunnels                  | Yes             |
+| Tunnel Load Balancing              | Active/Active   |
+| IKE Version                        | IKEv2           |
+| Authentication                     | Pre-Shared Key  |
+| Anti-Replay Protection             | Disabled        |
+| NAT Traversal (NAT-T)              | Not Tested      |
+| NAT-T Port                         | Not Applicable  |
+| Phase 1 - DH-Group                 | Group 20        |
+| Phase 1 - Encryption               | AES-256-CBC     |
+| Phase 1 - Authentication/Integrity | SHA-256         |
+| Phase 2 - DH-Group                 | Group 20        |
+| Phase 2 - Transport                | ESP             |
+| Phase 2 - Encryption               | AES-256-CBC     |
 
 ## Cloudflare WAN and HPE Juniper Networking SRX Series Firewalls - Configuration Settings
 
@@ -46,92 +46,92 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_01                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 162.159.135.1                                  |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_01     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.0/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 162.159.135.1     |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`      |
-| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_02                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 172.64.135.1                                   |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_02     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.2/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 172.64.135.1      |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`      |
-| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
 
 ## Customer Premise Equipment - HPE Juniper Networking
 
-| **WAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| WAN Interface                       | ge-0/0/0.0            | ge-0/0/0.0            |
-| IP Address                          | 203.0.113.100/24      | 203.0.113.100/24      |
-| Security Zone                       | untrust               | untrust               |
+| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| WAN Interface     | ge-0/0/0.0          | ge-0/0/0.0          |
+| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
+| Security Zone     | untrust             | untrust             |
 
-| **Virtual Tunnel Interface (VTI)**  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| Tunnel interface                    | st0.1                 | st0.2                 |
-| IP Address                          | 169.254.250.1/31      | 169.254.250.3/31      |
-| Security Zone                       | cloudflare            | cloudflare            |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ---------------------------------- | ------------------- | ------------------- |
+| Tunnel interface                   | st0.1               | st0.2               |
+| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
+| Security Zone                      | cloudflare          | cloudflare          |
 
-| **LAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| LAN Interface                       | ge-0/0/1.0            | ge-0/0/1.0            |
-| IP Address                          | 192.168.125.1/24      | 192.168.125.1/24      |
-| Security Zone                       | trust                 | trust                 |
+| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| LAN Interface     | ge-0/0/1.0          | ge-0/0/1.0          |
+| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
+| Security Zone     | trust               | trust               |
 
 ### HPE Juniper Networking SRX Object Names
 
-| **Element**                          | **Object Hierarchy**             | **Name**                        |
-| ------------------------------------ | -------------------------------- | ------------------------------- |
-| Security Zone - Trust                | [ security zones security-zone ] | trust                           |
-| Security Zone - Untrust              | [ security zones security-zone ] | untrust                         |
-| Security Zone - Cloudflare WAN       | [ security zones security-zone ] | cloudflare                      |
-| IKE Proposal (only one required)     | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
-| IKE Policy - Tunnel 1                | [ security ike policy ]          | cf-wan-ike-pol-01               |
-| IKE Policy - Tunnel 2                | [ security ike policy ]          | cf-wan-ike-pol-02               |
-| IKE Gateway - Tunnel 1               | [ security ike gateway ]         | cf-wan-ike-gw-01                |
-| IKE Gateway - Tunnel 2               | [ security ike gateway ]         | cf-wan-ike-gw-02                |
-| IPsec Proposal (only one required)   | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
-| IPsec Policy (only one required)     | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
-| IPsec Tunnel - Tunnel 1              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
-| IPsec Tunnel - Tunnel 2              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
+| **Element**                        | **Object Hierarchy**             | **Name**                        |
+| ---------------------------------- | -------------------------------- | ------------------------------- |
+| Security Zone - Trust              | [ security zones security-zone ] | trust                           |
+| Security Zone - Untrust            | [ security zones security-zone ] | untrust                         |
+| Security Zone - Cloudflare WAN     | [ security zones security-zone ] | cloudflare                      |
+| IKE Proposal (only one required)   | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
+| IKE Policy - Tunnel 1              | [ security ike policy ]          | cf-wan-ike-pol-01               |
+| IKE Policy - Tunnel 2              | [ security ike policy ]          | cf-wan-ike-pol-02               |
+| IKE Gateway - Tunnel 1             | [ security ike gateway ]         | cf-wan-ike-gw-01                |
+| IKE Gateway - Tunnel 2             | [ security ike gateway ]         | cf-wan-ike-gw-02                |
+| IPsec Proposal (only one required) | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
+| IPsec Policy (only one required)   | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
+| IPsec Tunnel - Tunnel 1            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
+| IPsec Tunnel - Tunnel 2            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
 
 ## Assumptions
 
@@ -216,7 +216,7 @@ Configure the following:
 Define an IKE Proposal with the following settings:
 
 | **Attribute**            | **Value**       |
-| ------------------------ | ----------------|
+| ------------------------ | --------------- |
 | authentication-method    | pre-shared-keys |
 | dh-group                 | group20         |
 | authentication-algorithm | sha256          |
@@ -356,13 +356,13 @@ _Perform in Configuration Mode_
 
 The following example allows all source & destination IPs, ports, and protocols/services between `cloudflare` and `trust` as well as between `trust` and `cloudflare`.
 
-| **Attribute**            | **Value**     |
-| ------------------------ | ------------- |
-| source-address           | any           |
-| destination-address      | any           |
-| application              | any           |
-| action                   | permit        |
-| log                      | session-close |
+| **Attribute**       | **Value**     |
+| ------------------- | ------------- |
+| source-address      | any           |
+| destination-address | any           |
+| application         | any           |
+| action              | permit        |
+| log                 | session-close |
 
 ```txt
 set security policies from-zone cloudflare to-zone trust policy cloudflare-to-trust-permit match source-address any
@@ -389,18 +389,18 @@ This example assumes traffic originating from 192.168.125.0/24 (ingress interfac
 Implementing Filter-Based Forwarding (FBF) requires four steps:
 
 1. Create a Forwarding Routing Instance
-    - Think of the Routing Instance as a "bucket" containing an alternate routing table
-    - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
+   - Think of the Routing Instance as a "bucket" containing an alternate routing table
+   - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
 2. Create a Firewall Filter
-    - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
-    - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
+   - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
+   - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
 3. Configure the RIB Group and Bind Routes
-    - Think of this as the "bridge" that copies interface routes to the "bucket"
-    - The Routing Instance is not part of the default routing table.
-    - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
+   - Think of this as the "bridge" that copies interface routes to the "bucket"
+   - The Routing Instance is not part of the default routing table.
+   - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
 4. Apply the Firewall Filter to the ingress traffic interface(s)
-    - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
-    - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
+   - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
+   - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
 
 #### Define a Routing Instance
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
index 51757cc2dd241e8..e64b5b02cda5941 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
@@ -11,15 +11,16 @@ This tutorial shows how to configure IPsec (Internet Protocol Security) between
 You need a pre-shared key to establish the IPsec tunnel. You can use the following code to create a random key:
 
 ```js
-		const a = new Uint8Array(48);
-		crypto.getRandomValues(a);
-		let base64String = btoa(String.fromCharCode.apply(null, a));
+const a = new Uint8Array(48);
+crypto.getRandomValues(a);
+let base64String = btoa(String.fromCharCode.apply(null, a));
 
-		base64String = base64String.replace(/\+/g, '')
-								   .replace(/\//g, '')
-								   .replace(/=/g, '');
+base64String = base64String
+	.replace(/\+/g, "")
+	.replace(/\//g, "")
+	.replace(/=/g, "");
 
-		console.log(base64String.substring(0, 32));
+console.log(base64String.substring(0, 32));
 ```
 
 :::caution
@@ -58,28 +59,28 @@ You can try this code in the [Workers playground](https://workers.cloudflare.com
    - **Dynamic routing gateways (DRG)**: Select the DRG you created in step 2.
    - **Routes to your on-premises network**: Enter a CIDR (Classless Inter-Domain Routing) range you want to route to Cloudflare WAN.
    - **Tunnel 1**
-      - **Name**: Enter a name.
-      - Select **Provide custom shared secret**.
-      - Enter the **pre-shared key** you created in the Prerequisites section.
-      - **IKE (Internet Key Exchange) version**: **IKEv2**
-      - **Routing type**: **Static routing**
-      - **IPv4 inside tunnel interface - CPE**:  Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
-      - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
-         1. Select **Show advanced options**
-         2. Select **Phase one (ISAKMP) configuration**
-            - Select **Set custom configurations**
-            - **Custom encryption algorithm**: **AES_256_CBC**
-            - **Custom authentication algorithm**: **SHA2_256**
-            - **Custom Diffie-Hellman group**: **GROUP20**
-            - **IKE session key lifetime in seconds**: **86400**
-         3. Select **Phase two (IPsec) configuration**
-            - Select **Set custom configurations**
-            - **Custom encryption algorithm**: **AES_256_CBC**
-            - **HMAC (Hash-based Message Authentication Code)_SHA2_256_128**: **HMAC_SHA2_256_128**
-            - **IPsec session key lifetime in seconds**: **28800**
-            - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
-    - **Tunnel 2**
-      - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
+     - **Name**: Enter a name.
+     - Select **Provide custom shared secret**.
+     - Enter the **pre-shared key** you created in the Prerequisites section.
+     - **IKE (Internet Key Exchange) version**: **IKEv2**
+     - **Routing type**: **Static routing**
+     - **IPv4 inside tunnel interface - CPE**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
+     - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
+       1. Select **Show advanced options**
+       2. Select **Phase one (ISAKMP) configuration**
+          - Select **Set custom configurations**
+          - **Custom encryption algorithm**: **AES_256_CBC**
+          - **Custom authentication algorithm**: **SHA2_256**
+          - **Custom Diffie-Hellman group**: **GROUP20**
+          - **IKE session key lifetime in seconds**: **86400**
+       3. Select **Phase two (IPsec) configuration**
+          - Select **Set custom configurations**
+          - **Custom encryption algorithm**: **AES_256_CBC**
+          - **HMAC (Hash-based Message Authentication Code)\_SHA2_256_128**: **HMAC_SHA2_256_128**
+          - **IPsec session key lifetime in seconds**: **28800**
+          - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
+   - **Tunnel 2**
+     - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
 4. Select **Create IPsec connection**
 
 ## Cloudflare WAN
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
index 34b5e4bec7deae3..81fe83217616d1d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ## Test Environment
 
-| **Field**                          | **Value**                                  |
-| ---------------------------------- | ------------------------------------------ |
-| Vendor                             | Palo Alto Networks                         |
-| Model                              | PA-440                                     |
-| Release                            | PAN-OS 11.2.8                              |
-| Date Tested                        | March 2026                                 |
+| **Field**   | **Value**          |
+| ----------- | ------------------ |
+| Vendor      | Palo Alto Networks |
+| Model       | PA-440             |
+| Release     | PAN-OS 11.2.8      |
+| Date Tested | March 2026         |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**                                  |
-| ---------------------------------- | ------------------------------------------ |
-| Traffic Selection Criteria         | Route-Based VPN                            |
-| Routing                            | Static                                     |
-| Redundant Tunnels                  | Yes                                        |
-| Tunnel Load Balancing              | Active/Active                              |
-| IKE Version                        | IKEv2                                      |
-| Authentication                     | Pre-Shared Key                             |
-| Anti-Replay Protection             | Disabled                                   |
-| NAT Traversal (NAT-T)              | Not Tested                                 |
-| NAT-T Port                         | Not Applicable                             |
-| Phase 1 - DH-Group                 | Group 20                                   |
-| Phase 1 - Encryption               | AES-256-CBC                                |
-| Phase 1 - Authentication/Integrity | SHA-256                                    |
-| Phase 2 - DH-Group                 | Group 20                                   |
-| Phase 2 - Transport                | ESP                                        |
-| Phase 2 - Encryption               | AES-256-CBC                                |
+| **Field**                          | **Value**       |
+| ---------------------------------- | --------------- |
+| Traffic Selection Criteria         | Route-Based VPN |
+| Routing                            | Static          |
+| Redundant Tunnels                  | Yes             |
+| Tunnel Load Balancing              | Active/Active   |
+| IKE Version                        | IKEv2           |
+| Authentication                     | Pre-Shared Key  |
+| Anti-Replay Protection             | Disabled        |
+| NAT Traversal (NAT-T)              | Not Tested      |
+| NAT-T Port                         | Not Applicable  |
+| Phase 1 - DH-Group                 | Group 20        |
+| Phase 1 - Encryption               | AES-256-CBC     |
+| Phase 1 - Authentication/Integrity | SHA-256         |
+| Phase 2 - DH-Group                 | Group 20        |
+| Phase 2 - Transport                | ESP             |
+| Phase 2 - Encryption               | AES-256-CBC     |
 
 ## Cloudflare WAN and Palo Alto Networks NGFW - Configuration Settings
 
@@ -46,85 +46,85 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_01                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 162.159.135.1                                  |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_01     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.0/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 162.159.135.1     |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`    |
-| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_02                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 172.64.135.1                                   |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_02     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.2/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 172.64.135.1      |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`    |
-| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
 
 ## Customer Premise Equipment - Palo Alto Networks
 
-| **WAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| WAN Interface                      | ethernet1/1           | ethernet1/1           |
-| IP Address                         | 203.0.113.100/24      | 203.0.113.100/24      |
-| Security Zone                      | untrust               | untrust               |
+| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| WAN Interface     | ethernet1/1         | ethernet1/1         |
+| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
+| Security Zone     | untrust             | untrust             |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| Tunnel interface                   | tunnel.1              | tunnel.2              |
-| IP Address                         | 169.254.250.1/31      | 169.254.250.3/31      |
-| Security Zone                      | cloudflare            | cloudflare            |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ---------------------------------- | ------------------- | ------------------- |
+| Tunnel interface                   | tunnel.1            | tunnel.2            |
+| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
+| Security Zone                      | cloudflare          | cloudflare          |
 
-| **LAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| LAN Interface                      | ethernet1/2           | ethernet1/2           |
-| IP Address                         | 192.168.125.1/24      | 192.168.125.1/24      |
-| Security Zone                      | trust                 | trust                 |
+| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| LAN Interface     | ethernet1/2         | ethernet1/2         |
+| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
+| Security Zone     | trust               | trust               |
 
 ### Palo Alto Networks NGFW Object Names
 
-| **Role**                           | **Label/Name**            | **Address**                 |
-| ---------------------------------- | ------------------------- | --------------------------- |
-| CPE Security Zone - Trust          | Zone                      | trust                       |
-| CPE Security Zone - Untrust        | Zone                      | untrust                     |
-| CPE Security Zone - Cloudflare WAN | Zone                      | cloudflare                  |
-| CPE IKE Crypto Profile Name        | IKE Crypto Profile        | ike-aes256cbc-sha256-dh20   |
-| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile      | ipsec-aes256cbc-sha256-dh20 |
+| **Role**                           | **Label/Name**       | **Address**                 |
+| ---------------------------------- | -------------------- | --------------------------- |
+| CPE Security Zone - Trust          | Zone                 | trust                       |
+| CPE Security Zone - Untrust        | Zone                 | untrust                     |
+| CPE Security Zone - Cloudflare WAN | Zone                 | cloudflare                  |
+| CPE IKE Crypto Profile Name        | IKE Crypto Profile   | ike-aes256cbc-sha256-dh20   |
+| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile | ipsec-aes256cbc-sha256-dh20 |
 
 ## Assumptions
 
@@ -271,12 +271,12 @@ Repeat steps for tunnel 2
 
 Define an IKE Crypto Profile with the following settings:
 
-| **Attribute**   | **Value**   |
-| --------------- | ----------- |
-| hash            | sha256      |
-| dh-group        | group20     |
-| encryption      | aes-256-cbc |
-| lifetime hours  | 8           |
+| **Attribute**  | **Value**   |
+| -------------- | ----------- |
+| hash           | sha256      |
+| dh-group       | group20     |
+| encryption     | aes-256-cbc |
+| lifetime hours | 8           |
 
 ###### CLI
 
@@ -639,10 +639,10 @@ Gateway ID      Peer-Address       Gateway Name       Role SN    Algorithm
 
 ```txt
 IKEv2 IPSec Child SAs
-Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST              
-------------                   ----     ------                     --       ------   ---- -------  -------- -----    --              
-cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature           
-cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature           
+Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST
+------------                   ----     ------                     --       ------   ---- -------  -------- -----    --
+cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature
+cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature
 
 Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 ```
@@ -652,7 +652,7 @@ Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 Use [test](https://docs.paloaltonetworks.com/network-security/ipsec-vpn/administration/troubleshooting/troubleshooting-site-to-site-vpn-issues-using-cli) commands to force Phase 1 and Phase 2 security associations:
 
 ```txt
-admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01 
+admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01
 
 Start time: Mar.30 21:23:23
 Initiate 1 IKE SA.
@@ -664,7 +664,7 @@ Initiate 1 IKE SA.
 ```
 
 ```txt
-admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01 
+admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01
 
 Start time: Mar.30 21:26:50
 Initiate 1 IPSec SA for tunnel cf-wan-ipsec-tun-01.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
index 7aff703eec495a2..20b793688afdc79 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
@@ -11,7 +11,6 @@ import { Render } from "~/components";
 This tutorial shows you how to use Cloudflare WAN (formerly Magic WAN) with the following versions of the Sophos Firewall:
 
 - **Sophos form factor tested:**
-
   - Sophos Firewall XGS and XG series hardware
   - Sophos Firewall virtual appliance on VMware
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
index 4a09ab7e89822a7..29458f09ea57950 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
@@ -195,7 +195,7 @@ Once the Edge device is added, you should land on the **Device** tab.
 
 #### User Defined WAN Link
 
-Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result,  the WAN Link must be specified.
+Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result, the WAN Link must be specified.
 
 ![Note the indicator next to GE3.](~/assets/images/cloudflare-wan/third-party/velocloud/image2.png)
 
@@ -215,7 +215,7 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 5. Select the **Network Service** defined earlier. For example, `Magic_WAN_vc-edge-03`.
 6. In the **Action** column, select the **+** button, and configure the following options:
    1. **Public WAN Link**: Choose the Public WAN Link (refer to User-Defined WAN Link)
-   2. **Local Identification Type**: *FQDN*
+   2. **Local Identification Type**: _FQDN_
    3. **Local Identification**: Enter the FQDN specified when configuring Cloudflare WAN IPsec tunnels through the Custom FQDN IKE ID API endpoint.
    4. **PSK**: Enter the Pre-Shared Key. Ensure you use the same PSK for both Cloudflare WAN IPsec tunnels.
    5. **Destination Primary Public IP**: Pre-populated from the Network Service defined earlier.
@@ -227,8 +227,8 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 
 Configure the **Site Subnets** to facilitate:
 
-* Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
-* Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
+- Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
+- Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
 
 1. Go to **Configure** > **Network Services**.
 2. Expand the **Non SD-WAN Destinations through Edge** section.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
index fae8475cf53be20..948613cef1331b1 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
@@ -37,32 +37,32 @@ To create a Secure Internet Gateway (SIG) using vManage:
 1. From **Cisco vManage** under **Configuration**, select **Generic** and **Add Tunnel**.
 2. The table below shows the setting fields and their options.
 
-| Setting             | Type/Detail                               |
-| ------------------- | ----------------------------------------- |
+| Setting             | Type/Detail                           |
+| ------------------- | ------------------------------------- |
 | **Global Template** | Factory_Default_Global_CISCO_Template |
-| **Cisco Banner**    | Factory_Default_Retail_Banner          |
-| **Policy**          | Branch-Local-Policy                       |
+| **Cisco Banner**    | Factory_Default_Retail_Banner         |
+| **Policy**          | Branch-Local-Policy                   |
 
 **Transport & Management VPN settings**
 
-| Setting                           | Type/Detail                         |
-| --------------------------------- | ----------------------------------- |
-| **Cisco VPN 0**                   | GCP-Branch-VPN0                     |
-| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template             |
-| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC     |
-| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface                  |
-| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01 |
+| Setting                           | Type/Detail                     |
+| --------------------------------- | ------------------------------- |
+| **Cisco VPN 0**                   | GCP-Branch-VPN0                 |
+| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template         |
+| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC |
+| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface              |
+| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01  |
 
 **Basic Information settings**
 
-| Setting            | Type/Detail                                 |
-| ------------------ | ------------------------------------------- |
+| Setting            | Type/Detail                             |
+| ------------------ | --------------------------------------- |
 | **Cisco System**   | Default_BootStrap_Cisco_System_Template |
-| **Cisco Logging**  | Default_Logging_Cisco_V01                |
-| **Cisco AAA**      | AWS-Branch-AAA-Template                     |
-| **Cisco BFD**      | Default_BFD_Cisco-V01                     |
-| **Cisco OMP**      | Default_AWS_TGW_CSR_OMP_IPv46_...     |
-| **Cisco Security** | Default_Security_Cisco_V01               |
+| **Cisco Logging**  | Default_Logging_Cisco_V01               |
+| **Cisco AAA**      | AWS-Branch-AAA-Template                 |
+| **Cisco BFD**      | Default_BFD_Cisco-V01                   |
+| **Cisco OMP**      | Default*AWS_TGW_CSR_OMP_IPv46*...       |
+| **Cisco Security** | Default_Security_Cisco_V01              |
 
 When creating the Feature Template, you can choose values that apply globally or that are device specific. For example, the **Tunnel Source IP Address**, **Interface Name** and fields from **Update Tunnel** are device specific and should be chosen accordingly.
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
index 017633fb496566a..82717dcc274bcdf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
@@ -22,19 +22,19 @@ Before proceeding, ensure that you have the anycast IPs assigned to your account
 ### IPsec tunnels
 
 1. Follow the <a href={props.addTunnelsUrl}>Add tunnels</a> instructions to create the required IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
-	- **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
-	- **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
-	- **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
-	- **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
-	- **Health check rate**: _Medium_.
-	- **Health check type**: _Request_.
-	- **Health check direction**: _Bidirectional_.
-	- **Health check target**: _Default_.
-	- **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
-	- **Replay protection**: Do not check the box, to keep this disabled.
+   - **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
+   - **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
+   - **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
+   - **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
+   - **Health check rate**: _Medium_.
+   - **Health check type**: _Request_.
+   - **Health check direction**: _Bidirectional_.
+   - **Health check target**: _Default_.
+   - **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
+   - **Replay protection**: Do not check the box, to keep this disabled.
 
 2. After you create your tunnel, the Cloudflare dashboard will load a list of tunnels set up for your account. Select the IPsec tunnel you have just created, and check the following setting:
-	- **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
+   - **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
 
 ### Static routes
 
@@ -214,4 +214,4 @@ IKE keepalive:
 [Status]: OK
 
 [Next send]: 1 sec after
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
index 7639f10f685149d..e49fb208f2bd10f 100644
--- a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
@@ -36,13 +36,13 @@ On-premises network and security appliances require manual firmware updates, pat
 
 ## Compare WAN approaches
 
-| | Traditional WAN (MPLS) | SD-WAN | Cloudflare One |
-|---|---|---|---|
-| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing. | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling. |
-| **Cost model** | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment. | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model. |
-| **Agility** | Weeks to months to provision new circuits. Rigid topology changes. | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection. |
-| **Security** | Security applied at central data center or per-site firewalls. | Varies by vendor. Some offer integrated security, others require separate appliances. | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
-| **Management** | Separate management for WAN circuits, routers, and security appliances. | Single console for WAN, but security often managed separately. | Single dashboard for network connectivity, routing, firewall rules, and security policies. |
+|                 | Traditional WAN (MPLS)                                                                                | SD-WAN                                                                                             | Cloudflare One                                                                                                   |
+| --------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing.   | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling.  |
+| **Cost model**  | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment.            | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model.                    |
+| **Agility**     | Weeks to months to provision new circuits. Rigid topology changes.                                    | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection.                              |
+| **Security**    | Security applied at central data center or per-site firewalls.                                        | Varies by vendor. Some offer integrated security, others require separate appliances.              | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
+| **Management**  | Separate management for WAN circuits, routers, and security appliances.                               | Single console for WAN, but security often managed separately.                                     | Single dashboard for network connectivity, routing, firewall rules, and security policies.                       |
 
 ## Plan your migration
 
@@ -78,7 +78,11 @@ Organizations that start with Cloudflare WAN for site-to-site connectivity and p
 
 ## Next steps
 
-- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the Cloudflare One Appliance or a third-party device.
-- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all Cloudflare One connectivity options and choose the right combination for your deployment.
-- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported on-ramps for connecting your networks.
+- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the
+  Cloudflare One Appliance or a third-party device.
+- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all
+  Cloudflare One connectivity options and choose the right combination for your
+  deployment.
+- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported
+  on-ramps for connecting your networks.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the architecture of Cloudflare One as a SASE platform.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
index 233eb735ada557b..67d32f2a51ebbf2 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
@@ -21,7 +21,9 @@ params:
 
 import { Render } from "~/components";
 
-<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress traffic.
+<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web
+Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress
+traffic.
 
 You can apply network and HTTP Gateway policies alongside <a href="/cloudflare-network-firewall/">Cloudflare Network Firewall</a> policies (for L3/4 traffic filtering) to Internet-bound traffic or private traffic entering the Cloudflare network through Cloudflare WAN (formerly Magic WAN). Additionally, you can configure Gateway to [resolve DNS queries](#dns-filtering) from Cloudflare WAN.
 
@@ -128,9 +130,9 @@ Source ports are fixed to `1024`-`65535` and cannot be overridden.
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
 
 ## Test Gateway integration
 
@@ -141,6 +143,7 @@ If you are still testing Gateway and Cloudflare is not your default route, confi
 Confirm there is an entry for the test in <a href={props.gatewayLogsURL}>HTTP Gateway Activity Logs</a>.
 
 Verify the following details:
+
 - **Destination IP**: Should be the public IP address of `ifconfig.me`.
 - **Source IP**: Should be the private (WAN) address of the host with the browser.
 - **Outbound connection**: Should be sourced from a Cloudflare WAN IP address, not any public IP address that Cloudflare might be advertising on your behalf.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
index ca49d64696b2380..05ee41c0b931606 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
@@ -1,8 +1,8 @@
 ---
- {}
+{}
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) provides site-to-site connectivity and packet-level security through [Cloudflare Network Firewall](/cloudflare-network-firewall/). The Cloudflare One integrations below extend that foundation with identity-aware security — user-level access policies through [Cloudflare Access](/cloudflare-one/access-controls/), secure Internet egress through [Cloudflare Gateway](/cloudflare-one/traffic-policies/), and device-level routing through the [Cloudflare One Client (formerly WARP)](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/).
 
@@ -10,4 +10,4 @@ Review the tutorials to learn how to use Cloudflare WAN with these Cloudflare On
 
 <DirectoryListing />
 
-If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
\ No newline at end of file
+If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
index 00c200fe13cb9b3..f80c67cfd5709c5 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
@@ -19,7 +19,9 @@ Cloudflare WAN carries three types of traffic, and different security services a
 
 ### Cloudflare Network Firewall
 
-<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides packet-level filtering at layers 3 and 4. You define allow or block rules based on IP addresses, ports, and protocols.
+<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides
+packet-level filtering at layers 3 and 4. You define allow or block rules based
+on IP addresses, ports, and protocols.
 
 - **Applies to**: inbound, outbound, and east-west traffic
 - **Included with**: Cloudflare WAN by default for [standard features](/cloudflare-network-firewall/plans/)
@@ -74,16 +76,16 @@ AI visibility is not a separate inline security service. It is an analytics feat
 
 ## Use-case mapping
 
-| Traffic scenario | Recommended services |
-|---|---|
-| Block traffic between sites by IP, port, or protocol | Network Firewall |
-| Filter DNS queries from branch offices | Gateway DNS policies |
-| Block malware downloads from branch offices | Gateway HTTP policies |
-| Prevent sensitive data uploads to the Internet | DLP (via Gateway HTTP policies) |
-| Isolate risky web browsing from branch users | Browser Isolation (via Gateway HTTP policies) |
-| Detect and block unsanctioned SaaS applications | CASB + Gateway HTTP policies |
-| Monitor employee AI tool usage | AI Security Report (via Gateway) |
-| Protect against DDoS on customer-owned IPs | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
+| Traffic scenario                                     | Recommended services                                          |
+| ---------------------------------------------------- | ------------------------------------------------------------- |
+| Block traffic between sites by IP, port, or protocol | Network Firewall                                              |
+| Filter DNS queries from branch offices               | Gateway DNS policies                                          |
+| Block malware downloads from branch offices          | Gateway HTTP policies                                         |
+| Prevent sensitive data uploads to the Internet       | DLP (via Gateway HTTP policies)                               |
+| Isolate risky web browsing from branch users         | Browser Isolation (via Gateway HTTP policies)                 |
+| Detect and block unsanctioned SaaS applications      | CASB + Gateway HTTP policies                                  |
+| Monitor employee AI tool usage                       | AI Security Report (via Gateway)                              |
+| Protect against DDoS on customer-owned IPs           | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
 
 ## How services compose
 
@@ -99,7 +101,12 @@ This means you can layer multiple security services on the same traffic flow wit
 
 ## Next steps
 
-- <a href={props.gatewaySetupURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a>: Detailed setup guide for Gateway integration with WAN traffic.
-- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure packet-level filtering rules.
+- <a href={props.gatewaySetupURL}>
+  	Connect to Cloudflare Gateway with Cloudflare WAN
+  </a>
+  : Detailed setup guide for Gateway integration with WAN traffic.
+- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure
+  packet-level filtering rules.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the full architecture of Cloudflare One as a SASE platform.
-- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your migration from traditional WAN to Cloudflare.
+- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your
+  migration from traditional WAN to Cloudflare.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
index 41ddc29de0c6c15..ef33bc683575a8e 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
@@ -8,7 +8,7 @@ params:
   - arrURL
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) can work together with <a href="/cloudflare-one/networks/connectors/cloudflare-tunnel/">Cloudflare Tunnel</a> to provide easy access between your networks and applications.
 
@@ -30,12 +30,12 @@ To route the same prefix to different destinations, use separate [virtual networ
 
 Cloudflare reserves the following IP ranges for Zero Trust services:
 
-| IP range | Purpose |
-| --- | --- |
-| `100.64.0.0/12` | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/) |
-| `100.96.0.0/12` | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
-| `100.80.0.0/16` | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/) |
-| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/) |
+| IP range         | Purpose                                                                                              |
+| ---------------- | ---------------------------------------------------------------------------------------------------- |
+| `100.64.0.0/12`  | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/)       |
+| `100.96.0.0/12`  | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
+| `100.80.0.0/16`  | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/)             |
+| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/)                                           |
 
 Do not configure routes that overlap with these reserved ranges.
 
@@ -51,7 +51,8 @@ Longest-prefix-match routing is the default route selection method. Other mechan
 
 ### Automatic Return Routing (ARR)
 
-<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for return traffic.
+<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for
+return traffic.
 
 When ARR is enabled:
 
@@ -88,7 +89,6 @@ To verify that a `cloudflared` tunnel works correctly with your Cloudflare WAN c
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
-
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
index 02de971802f7fa9..425405bded13584 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
@@ -73,9 +73,9 @@ You must log out and log back in with at least one device to ensure the configur
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
 
 ## Double encapsulation
 
@@ -91,7 +91,8 @@ To learn which IP addresses and UDP ports you should exclude to accomplish this,
 	file="mconn/network-options/app-aware-policies/warp-traffic"
 	product="networking-services"
 	params={{
-		warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
+		warpFirewallURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/",
 	}}
 />
 
diff --git a/src/content/partials/networking-services/cni-product-use-cases.mdx b/src/content/partials/networking-services/cni-product-use-cases.mdx
index 1e1079f2de90aec..5d902dd611989d8 100644
--- a/src/content/partials/networking-services/cni-product-use-cases.mdx
+++ b/src/content/partials/networking-services/cni-product-use-cases.mdx
@@ -4,13 +4,12 @@
 
 CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications.
 
-
-|  | Dataplane v1 | Dataplane v2 |
-| ---- | ---- | ---- |
-| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Cloudflare WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. |
-| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
+|                                                                                                                                                                                                         | Dataplane v1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Dataplane v2                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Supported.                                                                                                                                                                |
+| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare.                                              | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
+| **Cloudflare WAN and Zero Trust** <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds.                      | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
+| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence).                                                                                                             | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP.                                                                                                                                                                                                                                                                              | Not supported.                                                                                                                                                            |
+| **Application Security and Performance** <br /> Improve the performance and security of your web applications                                                                                           | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
 
 For more details refer to the [prerequisites section](/network-interconnect/get-started/#prerequisites).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
index 4b05caa926f685e..3776c9a7c06a1bd 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
@@ -104,4 +104,5 @@ curl https://api.cloudflare.com/client/v4/graphql \
 ```
 
 [^1]: For details, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
-[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
+
+[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
index 0471540ec9e7cb8..40149b5bcec5005 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
@@ -17,13 +17,13 @@ You need the following to query endpoint health check data:
 
 The following parameters are some of the most common ones in the `filter` object:
 
-| Parameter | Description |
-| :---- | :---- |
-| `date_geq` | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
-| `date_leq` | _(Optional)_ End date for the query. Uses the same format as `date_geq`. |
-| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions. |
-| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format. |
-| `limit` | Maximum number of result groups to return. |
+| Parameter      | Description                                                                                                                                                                                                                                             |
+| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `date_geq`     | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
+| `date_leq`     | _(Optional)_ End date for the query. Uses the same format as `date_geq`.                                                                                                                                                                                |
+| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions.                                                                                                  |
+| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format.                                                                                                                                                                                                          |
+| `limit`        | Maximum number of result groups to return.                                                                                                                                                                                                              |
 
 You can also filter on any dimension listed in the [Available dimensions](#available-dimensions) table. Append an operator suffix to the dimension name to create a filter — for example, `endpoint_in` to filter by a list of endpoints, or `checkType_neq` to exclude a specific check type. Using a dimension name without a suffix filters for equality. For the full list of supported operators, refer to [Filtering](/analytics/graphql-api/features/filtering/).
 
@@ -31,28 +31,28 @@ You can also filter on any dimension listed in the [Available dimensions](#avail
 
 You can query the following dimensions in the `dimensions` field:
 
-| Dimension | Description |
-| :---- | :---- |
-| `checkId` | The unique ID of the configured health check. |
-| `checkType` | The type of health check (for example, `icmp`). |
-| `endpoint` | The IP address of the endpoint being checked. |
-| `name` | The name assigned to the health check when configured (may be empty if not set). |
-| `date` | Event timestamp truncated to the day. |
-| `datetime` | Full event timestamp. |
-| `datetimeMinute` | Event timestamp truncated to the minute. |
-| `datetimeFiveMinutes` | Event timestamp truncated to five-minute intervals. |
-| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals. |
-| `datetimeHalfOfHour` | Event timestamp truncated to 30-minute intervals. |
-| `datetimeHour` | Event timestamp truncated to the hour. |
+| Dimension                | Description                                                                      |
+| :----------------------- | :------------------------------------------------------------------------------- |
+| `checkId`                | The unique ID of the configured health check.                                    |
+| `checkType`              | The type of health check (for example, `icmp`).                                  |
+| `endpoint`               | The IP address of the endpoint being checked.                                    |
+| `name`                   | The name assigned to the health check when configured (may be empty if not set). |
+| `date`                   | Event timestamp truncated to the day.                                            |
+| `datetime`               | Full event timestamp.                                                            |
+| `datetimeMinute`         | Event timestamp truncated to the minute.                                         |
+| `datetimeFiveMinutes`    | Event timestamp truncated to five-minute intervals.                              |
+| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals.                                |
+| `datetimeHalfOfHour`     | Event timestamp truncated to 30-minute intervals.                                |
+| `datetimeHour`           | Event timestamp truncated to the hour.                                           |
 
 ### Available metrics
 
-| Metric | Description |
-| :---- | :---- |
-| `count` | Total number of health check events in the group. |
-| `sum.total` | Total number of health check probes sent. |
-| `sum.failures` | Number of failed health check probes. |
-| `avg.lossPercentage` | Average calculated loss percentage (0-100). |
+| Metric               | Description                                       |
+| :------------------- | :------------------------------------------------ |
+| `count`              | Total number of health check events in the group. |
+| `sum.total`          | Total number of health check probes sent.         |
+| `sum.failures`       | Number of failed health check probes.             |
+| `avg.lossPercentage` | Average calculated loss percentage (0-100).       |
 
 ### API call
 
@@ -111,43 +111,43 @@ https://api.cloudflare.com/client/v4/graphql \
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "accounts": [
-        {
-          "magicEndpointHealthCheckAdaptiveGroups": [
-            {
-              "count": 288,
-              "dimensions": {
-                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-                "checkType": "icmp",
-                "datetimeFiveMinutes": "2026-01-21T12:00:00Z",
-                "endpoint": "103.21.244.100"
-              },
-              "sum": {
-                "failures": 0,
-                "total": 288
-              }
-            },
-            {
-              "count": 288,
-              "dimensions": {
-                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-                "checkType": "icmp",
-                "datetimeFiveMinutes": "2026-01-21T12:05:00Z",
-                "endpoint": "103.21.244.100"
-              },
-              "sum": {
-                "failures": 2,
-                "total": 288
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"accounts": [
+				{
+					"magicEndpointHealthCheckAdaptiveGroups": [
+						{
+							"count": 288,
+							"dimensions": {
+								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+								"checkType": "icmp",
+								"datetimeFiveMinutes": "2026-01-21T12:00:00Z",
+								"endpoint": "103.21.244.100"
+							},
+							"sum": {
+								"failures": 0,
+								"total": 288
+							}
+						},
+						{
+							"count": 288,
+							"dimensions": {
+								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+								"checkType": "icmp",
+								"datetimeFiveMinutes": "2026-01-21T12:05:00Z",
+								"endpoint": "103.21.244.100"
+							},
+							"sum": {
+								"failures": 2,
+								"total": 288
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
index f224c2ab01efe75..f9f5e61e69a7e7b 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
@@ -97,4 +97,4 @@ https://api.cloudflare.com/client/v4/graphql \
 #=> }
 ```
 
-[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
+[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
diff --git a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
index 1240490c155138a..630b17ac37eb812 100644
--- a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
+++ b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
@@ -40,7 +40,7 @@ Authentication failures in Phase 1 indicate a PSK mismatch. To resolve:
 
 1. Go to **Connectors** and select your tunnel.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select **Generate new PSK**.
 3. Copy the new PSK exactly — do not add extra spaces or characters.
@@ -72,9 +72,9 @@ Disable anti-replay protection on your tunnel endpoint, or set the replay window
 
 #### Health check type incompatible with stateful firewall
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default *Reply* health check packets because no matching ICMP request exists in their session table.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default _Reply_ health check packets because no matching ICMP request exists in their session table.
 
-Change the health check type from *Reply* to *Request*. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
+Change the health check type from _Reply_ to _Request_. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
 
 #### ISP blocking health check return path
 
@@ -128,7 +128,7 @@ Use IPsec logs to monitor tunnel activity during the key-exchange phase of the I
 
 1. Go to the **Logpush** page.
 
-	<DashButton url="/?to=/:account/logs" />
+   <DashButton url="/?to=/:account/logs" />
 
 2. Select **Create a Logpush job**.
 3. Select **IPsec logs** as your dataset.
diff --git a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
index 01689291e53b1c2..57fe9ec9026d18b 100644
--- a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
+++ b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
@@ -12,8 +12,9 @@ If you are using a Cloudflare IP, you do not need to advertise your prefixes.
 You must [put the appropriate MSS clamps](#set-maximum-segment-size) in place before [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) changes are made. Failure to apply an MSS clamp can result in dropped packets and hard-to-debug connectivity issues.
 
 Also, when using [Cloudflare Network Interconnect](/magic-transit/network-interconnect/) with Magic Transit you must set the following MSS clamp sizes to accommodate additional overhead:
+
 - GRE tunnels over CNI with Dataplane v1: 1476 bytes
 - CNI with Dataplane v2 / CNI with Dataplane v1 with a maximum transmission unit (MTU) size of 1500 bytes handoff does not require an MSS clamp.
 
 MSS clamps are used to backhaul data from the data center where traffic is ingested (close to the end user) to the facility with the CNI link.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
index c10384b93e929ca..2eab7b7b67f803a 100644
--- a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
+++ b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
@@ -3,19 +3,19 @@ params:
   - mtLpCreateTunnel
   - mtLpStaticRoute
   - mtLpBgpPeering
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To use Magic Transit, you need to own a publicly routable IP address block with a minimum size of `/24`. If you do not own a `/24` address block, you can use Magic Transit with a Cloudflare-owned IP address. This option is helpful if you do not meet the `/24` prefix length requirements or want to protect a smaller network.
 
 To protect your network with a Cloudflare IP address, contact your account manager. After you receive your IP address:
 
 - <a href={props.mtLpCreateTunnel}>Create a tunnel</a>.
-- <a href={props.mtLpStaticRoute}>Set up static routes</a> or <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
+- <a href={props.mtLpStaticRoute}>Set up static routes</a> or
+  <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
 - [Configure health checks](/magic-transit/network-health/run-endpoint-health-checks/).
 - Confirm you properly configured [tunnel](/magic-transit/network-health/update-tunnel-health-checks-frequency/) and endpoint health checks.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.
 
-When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
\ No newline at end of file
+When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
index 312b1d8e17bf88c..df51d0077eac1b3 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
@@ -5,11 +5,9 @@
 The MSS value depends on how your network is set up.
 
 - **Magic Transit ingress-only traffic (DSR):**
-
   - **On your edge router transit ports**: Set a TCP MSS clamp to a maximum of 1,436 bytes.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: Apply the MSS clamp on the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce the current value by 24 bytes.
 
 - **For Magic Transit ingress + egress traffic:**
-
   - **On the Magic Transit GRE tunnel internal interface**: Meaning where the Magic Transit egress traffic will traverse. Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 24 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
index ca0dc864b8bd976..9724b74d99a9784 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
@@ -5,11 +5,9 @@
 For IPsec tunnels, the value you need to specify depends on how your network is set up. The MSS clamping value is lower than for GRE tunnels because the physical interface sees IPsec-encrypted [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/), not TCP packets, and MSS clamping does not apply to those.
 
 - **Magic Transit ingress-only traffic (DSR):**
-
   - **On your edge router transit ports**: Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 140 bytes.
 
 - **Magic Transit ingress + egress traffic:**
-
   - **On your edge router**: Apply this on your Magic Transit IPsec tunnel internal interface (that is, where the Magic Transit egress traffic will traverse). Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,360 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the IPsec-terminating device in your premises) to reduce its current value by 140 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
index b760409416dfd6f..5768c1e380eceba 100644
--- a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
@@ -18,8 +18,8 @@ The following steps outline the recommended multi-step draining process to achie
 2. **Wait for global BGP convergence**: Allow a period of time (typically five to ten minutes) for the new native advertisement to propagate fully across the global routing table, and for routes to converge. This passive waiting period ensures that the majority of traffic has shifted to your local network before the next step.
 3. **Signal BGP withdrawal from the Cloudflare edge**: Once you have verified that traffic has successfully drained, use one of the BGP control methods to stop the advertisement of the prefix from the Cloudflare edge.
 
-	:::caution[ISP route refresh delays may impact traffic]
-	Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
-	:::
+   :::caution[ISP route refresh delays may impact traffic]
+   Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
+   :::
 
-4. The draining process is complete.
\ No newline at end of file
+4. The draining process is complete.
diff --git a/src/content/partials/networking-services/magic-user-role.mdx b/src/content/partials/networking-services/magic-user-role.mdx
index 5f688524a5b726f..72715ce73e544d4 100644
--- a/src/content/partials/networking-services/magic-user-role.mdx
+++ b/src/content/partials/networking-services/magic-user-role.mdx
@@ -12,7 +12,7 @@ For example, if multiple teams manage different Cloudflare products on the same
 
 1. Go to the **Members** page.
 
-	 <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Under **Members**, enter an existing user's name and select **Search**.
 3. Expand the menu at the end of the user row.
diff --git a/src/content/partials/networking-services/mconn/device-metrics.mdx b/src/content/partials/networking-services/mconn/device-metrics.mdx
index a2fad49b670b4f3..278ab4d0b610b62 100644
--- a/src/content/partials/networking-services/mconn/device-metrics.mdx
+++ b/src/content/partials/networking-services/mconn/device-metrics.mdx
@@ -13,59 +13,59 @@ For example:
 
 ```graphql graphql-api-explorer
 query telemetry(
-  $accountTag: string
-  $snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
-  $snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
-  $snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
-  $limit: int64!
+	$accountTag: string
+	$snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
+	$snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
+	$snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
+	$limit: int64!
 ) {
-  viewer {
-    accounts(filter: { accountTag: $accountTag }) {
-      snapshots: mconnTelemetrySnapshots(
-        filter: $snapshotsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC]
-      ) {
-        max {
-          cpuCount
-          loadAverage1m
-          memoryFreeBytes
-          memoryTotalBytes
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-      snapshotMounts: mconnTelemetrySnapshotMounts(
-        filter: $snapshotMountsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC]
-      ) {
-        max {
-          availableBytes
-          totalBytes
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-      snapshotThermals: mconnTelemetrySnapshotThermals(
-        filter: $snapshotThermalsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
-      ) {
-        max {
-          currentCelsius
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-    }
-  }
+	viewer {
+		accounts(filter: { accountTag: $accountTag }) {
+			snapshots: mconnTelemetrySnapshots(
+				filter: $snapshotsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC]
+			) {
+				max {
+					cpuCount
+					loadAverage1m
+					memoryFreeBytes
+					memoryTotalBytes
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+			snapshotMounts: mconnTelemetrySnapshotMounts(
+				filter: $snapshotMountsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC]
+			) {
+				max {
+					availableBytes
+					totalBytes
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+			snapshotThermals: mconnTelemetrySnapshotThermals(
+				filter: $snapshotThermalsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
+			) {
+				max {
+					currentCelsius
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+		}
+	}
 }
 ```
 
@@ -75,4 +75,4 @@ The metric `average CPU load` is unique and distinctly different from `CPU utili
 
 CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the Cloudflare One Appliance CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
 
-Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
\ No newline at end of file
+Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
diff --git a/src/content/partials/networking-services/mconn/licence-keys.mdx b/src/content/partials/networking-services/mconn/licence-keys.mdx
index 762bbc9168a849d..19fc13fb15ac9ea 100644
--- a/src/content/partials/networking-services/mconn/licence-keys.mdx
+++ b/src/content/partials/networking-services/mconn/licence-keys.mdx
@@ -3,8 +3,6 @@ params:
   - virtualConnectorName
 ---
 
-
-
 :::note
 You cannot use the same license key twice, or reuse a key once the virtual machine has been registered with Cloudflare. You need a new key from your account team for every new {props.virtualConnectorName}.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
index 720da967d7f0d34..5ed0d70f3420a55 100644
--- a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
@@ -7,4 +7,4 @@ params:
 Before you can activate your Cloudflare One Appliance (formerly Magic WAN Connector), you need to follow Cloudflare's instructions regarding DHCP. For instructions, refer to:
 
 - The <a href={props.hardwareConnectorURL}>hardware version of Cloudflare One Appliance</a>
-- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
\ No newline at end of file
+- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
index abb2c35e51bfd08..69bcf5dfd06bb9d 100644
--- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -3,38 +3,38 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
+    `}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
-	`}
-	inline={false}
-	/>
-	</>
 )
-}
-4. In **Status**, select _Deactivated_ from the drop-down menu.
-5. Select **Update**.
+} 4. In **Status**, select _Deactivated_ from the drop-down menu. 5. Select **Update**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index 0946f2695192a8a..e2cb63fb178ba6b 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -12,4 +12,4 @@ The default password for Cloudflare One Appliance is the serial number (also kno
 
 The default password for Virtual Appliance is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
 
-For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
+For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
index b11277c02a77557..20bffc12db414cc 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -8,34 +8,33 @@ import { DashButton, Markdown } from "~/components";
 In **Basic information**, you can change the name and description of your Cloudflare One Appliance (formerly Magic WAN Connector).
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. In **Basic information** make the necessary changes.
-5. Select **Save**.
\ No newline at end of file
+} 3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**. 4. In **Basic information** make the necessary changes. 5. Select **Save**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
index f71c11c0de55a12..16e6075ed0b533e 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -6,36 +6,32 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Connectors** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+inline={false}
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**.
-5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**.
-6. Make the necessary changes.
-7. Select **Save**.
\ No newline at end of file
+} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**. 5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**. 6. Make the necessary changes. 7. Select **Save**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
index 7a5e68df4e8f5b2..e0c56079072bb08 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
@@ -6,35 +6,35 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a> > **Insights**.
 		2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on.
 		3. Select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/networking-insights/health" />
-				<Markdown
-	text={`
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+<Markdown
+text={`
 		3. Find the site you want to make changes on > select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 		`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
index 267156ca7a1e2d3..79373537351ff1d 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -8,35 +8,33 @@ import { DashButton, Markdown } from "~/components";
 You can only add or remove applications to Breakout traffic and Prioritized traffic. To add or remove applications:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**.
-5. Select **Add** to add a new application.
-6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
\ No newline at end of file
+} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**. 5. Select **Add** to add a new application. 6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
index c8f54f97a753b77..6a9d81008d379c6 100644
--- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -3,7 +3,7 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 Cloudflare One Appliance (formerly Magic WAN Connector) communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
@@ -18,33 +18,34 @@ There are three symbols for the heartbeat signal that allow you to quickly check
 ### Access Cloudflare One Appliance's heartbeat
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Connectors** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
-
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
-	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
+    `}
+    inline={false}
+    />
+    </>
+
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
index b94efb16efe2c31..e0ac8962997b44f 100644
--- a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
@@ -3,42 +3,43 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 The Interrupt window defines when Cloudflare One Appliance (formerly Magic WAN Connector) can update its systems. When Cloudflare One Appliance is updating, this may result in an interruption to existing connections. Set up a time window that minimizes disruption to your sites.
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks** > **Connectors**.
 		2. In **Appliances** > **Appliances**, select the Cloudflare One Appliance for which you want to set up the update window > **Edit**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
 
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
+    `}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
-	`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
-   - **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
-   - **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
-   - **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
+} 3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
+
+- **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
+- **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
+- **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
index ad72dcbe7fe8d77..622bec3086c2415 100644
--- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
@@ -9,30 +9,27 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag
 
 {/* Dashboard steps for CF1 Cloudflare WAN (Cloudflare One dashboard) */}
 { props.dashName === "CF1 Cloudflare WAN" && (
-	<>
-	<ol>
-		<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
-		<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
-	</ol>
-	</>
+<>
+<ol>
+<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
+<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
+</ol>
+</>
 )
 }
 
 {/* Dashboard steps for Cloudflare WAN (standalone dashboard) */}
 { props.dashName !== "CF1 Cloudflare WAN" && (
-	<>
-	<ol>
-		<li>Go to the <strong>Connectors</strong> page.
-			<br />
-			<DashButton url="/?to=/:account/magic-networks/connections" />
-		</li>
-		<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
-	</ol>
-	</>
+<>
+<ol>
+<li>Go to the <strong>Connectors</strong> page.
+<br />
+<DashButton url="/?to=/:account/magic-networks/connections" />
+</li>
+<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
+</ol>
+</>
 )
-}
-3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard.
-4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account.
-5. Select **Register appliance**.
+} 3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard. 4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account. 5. Select **Register appliance**.
 
-Your device is now registered with your account.
\ No newline at end of file
+Your device is now registered with your account.
diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
index fa154fec8acde27..b9ba61db220dfb4 100644
--- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
@@ -6,6 +6,7 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 When adding or removing Cloudflare One Appliances (formerly Magic WAN Connectors), you need to be aware of the difference between the physical device and its profile.
+
 - The physical device is the hardware at your site.
 - The profile contains the configuration that allows the device to connect to Cloudflare, including your WANs, LANs, traffic steering, and LAN policies.
 
@@ -14,67 +15,69 @@ You can have more than one Cloudflare One Appliance in one profile if you initia
 ## Remove a profile
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to **Appliances** > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to **Appliances** > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
+} 3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
 
 ## Remove a physical device
 
 To remove a Cloudflare One Appliance from your account:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
\ No newline at end of file
+} 3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 5dc4a5441cd0fde..58394a01819ac0d 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -16,7 +16,7 @@ params:
   - networkSegmentationURL
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 The Cloudflare One Appliance (formerly Magic WAN Connector) software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
 
@@ -91,11 +91,14 @@ When a failover occurs, traffic is moved to the new active node. It could take u
 
 This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }} />
+<Render
+	file="mconn/wan-two-tunnels"
+	product="networking-services"
+	params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }}
+/>
 
 When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in Cloudflare One Appliance routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 
-
 Creating several WAN connections also means Cloudflare One Appliance can failover between circuits according to their health.
 
 ### High-capacity use cases
@@ -108,7 +111,7 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ### WAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
 - **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. For details on how Cloudflare calculates priorities, refer to <a href={props.trafficSteeringURL}>Traffic steering</a>.
 - **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. For details, refer to <a href={props.hcFrequencyURL}>Update tunnel health checks frequency</a>.
@@ -116,9 +119,9 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ## LAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
-- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable  DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
+- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
 - **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
 - **Routed subnets:** Configures additional subnets behind a layer 3 router. For details, refer to <a href={props.routedSubnetsURL}>Routed subnets</a>.
 
@@ -126,4 +129,4 @@ If you do not have more than one anycast IP configured in your account, and you
 
 Depending on your use case, you can define policies in your Cloudflare One Appliance to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
-For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
\ No newline at end of file
+For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index 7eb868cf827fa41..d64025ffaf32777 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -7,53 +7,64 @@ params:
   - dashName
 ---
 
-import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
+import {
+	APIRequest,
+	Aside,
+	AnchorHeading,
+	CURL,
+	DashButton,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+} from "~/components";
 
 { props.magicWord === "breakout" && (
-	<>
-		<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
-		<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-	</>
-	)
+<>
+<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
+<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+</>
+)
 }
 
 { props.magicWord === "prioritized" && (
-	<>
-		<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
-		<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
-		<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-	</>
-	)
+<>
+<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
+<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
+<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+</>
+)
 }
 
 { props.magicWord === "breakout" && (
-	<>
-		<pre class="mermaid">
-			{`
-			flowchart LR
-			accTitle: Breakout traffic flow
-			accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
-			a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
-
-			a-- Breakout traffic ---d(Application1) & e(Application2) --> c
-
-			classDef orange fill:#f48120,color: black
-			class a,b orange
-			`}
-		</pre>
-		<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
-		<Aside type="note" title="A note on security">
-		<Markdown
-		text={`
-		We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
+<>
+<pre class="mermaid">
+{`
+flowchart LR
+accTitle: Breakout traffic flow
+accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
+a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
+
+    		a-- Breakout traffic ---d(Application1) & e(Application2) --> c
+
+    		classDef orange fill:#f48120,color: black
+    		class a,b orange
+    		`}
+    	</pre>
+    	<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
+    	<Aside type="note" title="A note on security">
+    	<Markdown
+    	text={`
+    	We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
 
     For details on how Cloudflare routes traffic, refer to <a href="${props.trafficSteeringURL}">Traffic steering</a>.
-		`}
-		inline={false}
-		/>
-		</Aside>
-	</>
-	)
+    	`}
+    	inline={false}
+    	/>
+    	</Aside>
+    </>
+    )
+
 }
 
 ## Add an application to your account
@@ -64,28 +75,28 @@ To add applications to your account:
 
 Send a `POST` request to add new apps to your account.
 
-	<APIRequest
-	path="/accounts/{account_id}/magic/apps"
-	method="POST"
-	json={{
+    <APIRequest
+    path="/accounts/{account_id}/magic/apps"
+    method="POST"
+    json={{
     "managed_app_id": "<APP_ID>",
     "name": "<APP_NAME>",
     "type": "<APP_TYPE>",
-	}}
-	/>
-
-	```json output
-	{
-		"result": {
-			"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
-			"name": "<APP_NAME>",
-			"type": "<APP_TYPE>",
-		},
-		"success": true,
-		"errors": [],
-		"messages": []
-	}
-	```
+    }}
+    />
+
+    ```json output
+    {
+    	"result": {
+    		"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
+    		"name": "<APP_NAME>",
+    		"type": "<APP_TYPE>",
+    	},
+    	"success": true,
+    	"errors": [],
+    	"messages": []
+    }
+    ```
 
 You can now add this new app to the {props.featureName} list in your Cloudflare One Appliance.
 
@@ -315,87 +326,88 @@ You need to delete {props.featureName} applications for each of your existing si
 </TabItem> </Tabs>
 
 { props.magicWord === "breakout" && (
-	<>
-		<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
+<>
+<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
+
+    	<Markdown
+    	text={`
 
-		<Markdown
-		text={`
 You can pin applications to a specific WAN port in Cloudflare One Appliance when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, Cloudflare One Appliance automatically fails over to a standard configured WAN port priority.
 
 With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
 
 To pin applications to a WAN port:
-		`}
-		inline={false}
-		/>
-
-		{ props.dashName === "CF1 Cloudflare WAN" ? (
-			<>
-				<Markdown
-			text={`
-				1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
-				2. Go to **Connectors** > **Appliances** > **Profiles**.
-				3. Select the Cloudflare One Appliance you want to configure > **Edit**.
-			`}
-			inline={false}
-			/>
-			</>
-		) : (
-			<>
-			<Markdown
-				text={`
-					1. Go to the **Connectors** page.
-					`}
-				inline={false}
-				/>
-					<DashButton url="/?to=/:account/magic-networks/connections" />
-
-					<Markdown
-				text={`
-					2. Go to the **Appliances** tab > **Profiles**.
-					`}
-				inline={false}
-				/>
-				<Markdown
-			text={`
-				3. Select your Appliance > **Edit**.
-			`}
-			inline={false}
-			/>
-			</>
-		)
-		}
-		<Markdown
-		text={`
-		4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
-		5. Select the three dots next to it > **Edit application traffic**.
-		6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
-		7. Select **Save**.
-		`}
-		inline={false}
-		/>
-	</>
+`}
+inline={false}
+/>
+
+    	{ props.dashName === "CF1 Cloudflare WAN" ? (
+    		<>
+    			<Markdown
+    		text={`
+    			1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
+    			2. Go to **Connectors** > **Appliances** > **Profiles**.
+    			3. Select the Cloudflare One Appliance you want to configure > **Edit**.
+    		`}
+    		inline={false}
+    		/>
+    		</>
+    	) : (
+    		<>
+    		<Markdown
+    			text={`
+    				1. Go to the **Connectors** page.
+    				`}
+    			inline={false}
+    			/>
+    				<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    				<Markdown
+    			text={`
+    				2. Go to the **Appliances** tab > **Profiles**.
+    				`}
+    			inline={false}
+    			/>
+    			<Markdown
+    		text={`
+    			3. Select your Appliance > **Edit**.
+    		`}
+    		inline={false}
+    		/>
+    		</>
+    	)
+    	}
+    	<Markdown
+    	text={`
+    	4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
+    	5. Select the three dots next to it > **Edit application traffic**.
+    	6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
+    	7. Select **Save**.
+    	`}
+    	inline={false}
+    	/>
+    </>
+
 )
 }
 
-
 {props.magicWord === "breakout" && (
-	<>
-		<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
-	</>
-	)
+<>
+<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
+</>
+)
 }
 
 { props.magicWord === "breakout" && (
-	<>
-	<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
-		<Render
-			file="mconn/network-options/app-aware-policies/warp-traffic"
-			product="networking-services"
-			params={{
+<>
+<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
+<Render
+file="mconn/network-options/app-aware-policies/warp-traffic"
+product="networking-services"
+params={{
 				warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 			}}
-			/>
-	</>
-	)
-}
\ No newline at end of file
+/>
+</>
+)
+}
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
index 70f81778279f769..126ebd7f08071e4 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
@@ -14,7 +14,11 @@ The Cloudflare One Appliance uses NetFlow v9 to export flow data for breakout tr
 
 ### Enable NetFlow exports
 
-<Render file="account-id-api-key" product="networking-services" params={{ showSiteId: true }} />
+<Render
+	file="account-id-api-key"
+	product="networking-services"
+	params={{ showSiteId: true }}
+/>
 
 1. Send a `PUT` request to the Netflow configuration endpoint for your site.
 2. In the JSON body request, you must include the `collector_ip` parameter. To export traffic statistics to Network Flow, use the IP address `162.159.65.1`. This is the only field required to enable the feature.
@@ -25,11 +29,12 @@ Minimal configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		"collector_ip": "162.159.65.1"
+		collector_ip: "162.159.65.1",
 	}}
 />
 
 3. You can customize the configuration by adding optional fields to the JSON payload. These fields include:
+
 - `collector_port`: The UDP port for the collector. The default is `2055`.
 - `sampling_rate`: The rate at which packets are sampled.
 - `active_timeout`: The timeout for active flows in seconds.
@@ -41,11 +46,11 @@ Full configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		"collector_ip": "162.159.65.1",
-		"collector_port": 2055,
-		"sampling_rate": 100,
-		"active_timeout": 60,
-		"inactive_timeout": 30
+		collector_ip: "162.159.65.1",
+		collector_port: 2055,
+		sampling_rate: 100,
+		active_timeout: 60,
+		inactive_timeout: 30,
 	}}
 />
 
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
index 1d2567a03ec9803..f3203bf58619f2c 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
@@ -4,7 +4,7 @@ params:
   - appTypesGatewayURL
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Standard traffic policies match on network-layer attributes like IP addresses and port ranges. Application-aware policies go further — they identify traffic by the application generating it, so you can make routing and security decisions based on what the traffic is, not just where it is going.
 
@@ -19,5 +19,4 @@ With application-aware policies, you can:
 
 For details, refer to the following pages:
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
index a00df21396023ca..4ef40f59c1c2bc9 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -5,7 +5,14 @@ params:
   - cfVsCoreDashNamingMwanCni
 ---
 
-import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	APIRequest,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, Cloudflare One Appliance (formerly Magic WAN Connector) forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
index 94056a78a61e391..3a9c1d021abc578 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
@@ -3,7 +3,14 @@ params:
   - dashName
 ---
 
-import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	APIRequest,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN Connector) can also act as a DHCP server in your network. To enable this feature:
 
diff --git a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
index 000cfd917c0229e..dfd266a24e6682a 100644
--- a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
@@ -63,4 +63,3 @@ For step-by-step instructions to configure a LAN and supply a static NAT prefix,
 
 - <a href={props.hardConnectorURL}>Configure hardware Appliance</a>
 - <a href={props.virtualConnectorURL}>Configure Virtual Appliance</a>
-
diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
index 6243e2b3a08d8e5..079bcbe7f92895c 100644
--- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -5,7 +5,14 @@ params:
   - virtualConnectorURL
 ---
 
-import { APIRequest, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
+import {
+	APIRequest,
+	DashButton,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+} from "~/components";
 
 You can define policies in your Cloudflare One Appliance (formerly Magic WAN Connector) to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
index 9509f4c9fe5a7d6..22273d0546df33d 100644
--- a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
@@ -44,7 +44,7 @@ Blue represents directly-attached subnets, and red represents routed subnets.
 	`}
 </pre>
 
-<br/>
+<br />
 
 To add a routed subnet to your LAN, you need:
 
diff --git a/src/content/partials/networking-services/mconn/overview.mdx b/src/content/partials/networking-services/mconn/overview.mdx
index 7ac69fc4e47b806..0aaac9276dd0f51 100644
--- a/src/content/partials/networking-services/mconn/overview.mdx
+++ b/src/content/partials/networking-services/mconn/overview.mdx
@@ -19,4 +19,4 @@ Either option ensures the best possible connectivity to the closest Cloudflare n
 
 Review this section to learn how to configure and deploy {props.hardwareProductName}.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
index 1680225d6dfcefe..3c1e9c89c2d55cc 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
@@ -19,7 +19,11 @@ Cloudflare customers can inspect metrics for a specific Cloudflare One Appliance
 
 To find the information above and start troubleshooting your Cloudflare One Appliance:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 
 ### Performance analytics
 
@@ -33,7 +37,11 @@ In Performance analytics you can review your Cloudflare One Appliance's performa
 
 To access performance analytics:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **Performance analytics**.
 
 ### Port analytics
@@ -45,7 +53,11 @@ Port analytics gives you access to information related to the packets sent and r
 
 The dashboard provides this information for all active ports in your Cloudflare One Appliance. To access port analytics:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **Port analytics**.
 
 ### Event logs
@@ -71,15 +83,22 @@ Use Event logs to identify general patterns and changes over time. This is usefu
 
 To access event logs:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
-4. Select **Events**.
-5. You can filter results by specific events, and by time.
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
+4. Select **Events**. 5. You can filter results by specific events, and by time.
 
 ### DHCP leasing
 
 The DHCP leasing section identifies DHCP assigned leases and their expiration dates. To access DHCP leasing:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **DHCP leasing**.
 
 ## Troubleshooting tips
diff --git a/src/content/partials/networking-services/mconn/vlan-tagging.mdx b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
index d13dfd1e5a4f2a6..787946548bcc7a4 100644
--- a/src/content/partials/networking-services/mconn/vlan-tagging.mdx
+++ b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
@@ -17,4 +17,4 @@ Use VLAN ID <code>0</code> when:
 You can also configure subinterfaces on the {props.virtualConnectorName} by associating the network interface with a Port Group or Distributed Port Group trunk and specifying a VLAN ID in addition to the port associated with the network interface (VLAN ID <code>1</code>-<code>4094</code>).
 
 Refer to <Markdown text={props.url} /> for more information.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
index 304d1616c387e6a..bce930a2152d57d 100644
--- a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
+++ b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
@@ -4,4 +4,4 @@ params:
   - dashName
 ---
 
-When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
+When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
diff --git a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
index 3bf575d2cf83e7d..5419d89b875b933 100644
--- a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
+++ b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
@@ -11,4 +11,4 @@ You will receive the status of the advertisement for each prefix with the follow
 - **Delayed**: The prefix cannot currently be advertised but will attempt advertisement. After the prefix can be advertised, a new notification is sent with the updated status.
 - **Locked**: The prefix is locked and cannot be advertised.
 - **Could not Advertise**: Cloudflare was unable to advertise the prefix. This status can occur for multiple reasons, but usually occurs when you are not allowed to advertise a prefix.
-- **Error**: A general error occurred during prefix advertisement.
\ No newline at end of file
+- **Error**: A general error occurred during prefix advertisement.
diff --git a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
index 0090ebe938488ea..7b58e1a58a4bed2 100644
--- a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
+++ b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
@@ -17,15 +17,19 @@ After Magic Transit activates and your traffic flows through Cloudflare, Cloudfl
 The following diagrams illustrate this process:
 
 <Width size="large">
-	![The diagram shows the flow of traffic when you send flow data from your network to Cloudflare for analysis.](~/assets/images/network-flow/1-flowdata.png)
+	![The diagram shows the flow of traffic when you send flow data from your
+	network to Cloudflare for
+	analysis.](~/assets/images/network-flow/1-flowdata.png)
 </Width>
 
 <Width size="large">
-	![Cloudflare automatically notifies you when Cloudflare detects an attack	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
+	![Cloudflare automatically notifies you when Cloudflare detects an attack
+	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
 </Width>
 
 <Width size="large">
-	![You can create rules to activate Magic Transit automatically, to protect your IP addresses from a DDoS
+	![You can create rules to activate Magic Transit automatically, to protect
+	your IP addresses from a DDoS
 	attack.](~/assets/images/network-flow/3-flowdata.png)
 </Width>
 
diff --git a/src/content/partials/networking-services/mnm/faqs.mdx b/src/content/partials/networking-services/mnm/faqs.mdx
index b4a27eb520e6d6c..b0208fe02c88cf2 100644
--- a/src/content/partials/networking-services/mnm/faqs.mdx
+++ b/src/content/partials/networking-services/mnm/faqs.mdx
@@ -6,7 +6,7 @@ If you cannot find your answer here, refer to the [community page](https://commu
 
 ## I am getting an "Invalid account settings request body: account name format contains illegal characters or is not supported" error when trying to create a rule.
 
-This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 
diff --git a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
index cd765351f8a8f43..46c472367567090 100644
--- a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
+++ b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Configure your router to export <GlossaryTooltip term="sFlow">sFlow</GlossaryTooltip> data to Cloudflare's network for analysis in Network Flow (formerly Magic Network Monitoring). sFlow is a network monitoring protocol that samples network traffic to provide visibility into your network's performance and traffic patterns.
 
diff --git a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
index 4cbd7f7fa55f513..c117433d7d663dc 100644
--- a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
@@ -8,14 +8,14 @@ To use dynamic threshold rules, you must send NetFlow or sFlow data to Cloudflar
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | zscore |
-| **Target** | Can be defined in either bits per second or packets per second. |
-| **Sensitivity** | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic. |
+| Field                  | Description                                                                                                                                                                                                                                                                                                                                              |
+| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                               |
+| **Rule type**          | zscore                                                                                                                                                                                                                                                                                                                                                   |
+| **Target**             | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                                          |
+| **Sensitivity**        | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic.                                                                                                                                                                             |
 | **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. Network Flow supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section. |
+| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section.                                                                      |
 
 ## API documentation
 
@@ -33,4 +33,4 @@ Z = (X - μ) / σ
 
 - `X` = Current traffic value.
 - `μ` = Mean traffic value over the long window.
-- `σ` = Standard deviation over the long window.
\ No newline at end of file
+- `σ` = Standard deviation over the long window.
diff --git a/src/content/partials/networking-services/mnm/rules/overview.mdx b/src/content/partials/networking-services/mnm/rules/overview.mdx
index 64c496cc2672375..f604442b91f7228 100644
--- a/src/content/partials/networking-services/mnm/rules/overview.mdx
+++ b/src/content/partials/networking-services/mnm/rules/overview.mdx
@@ -25,7 +25,7 @@ If you get the following error when trying to create a rule:
 
 `Invalid account settings request body: account name format contains illegal characters or is not supported`
 
-Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 :::
diff --git a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
index cc8a9232c23298e..2a6ee954fa33c84 100644
--- a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
+++ b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Network Flow (formerly Magic Network Monitoring) can notify you by email, webhook, or PagerDuty when a rule is triggered. When a rule detects a traffic anomaly, notifications alert your team so you can respond — or, if you use Magic Transit with auto-advertisement, Cloudflare can begin mitigating the attack automatically.
 
@@ -16,16 +16,19 @@ For more information on the notification platform, refer to [Notifications docum
 
 ## Notification configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Notification name** | A label to identify this notification in your notifications list. |
-| **Description (optional)** | The description of the notification. |
-| **Webhooks** | One or more webhooks to deliver the notification to. |
-| **Notification email** | One or more email addresses to deliver the notification to. |
+| Field                      | Description                                                       |
+| :------------------------- | :---------------------------------------------------------------- |
+| **Notification name**      | A label to identify this notification in your notifications list. |
+| **Description (optional)** | The description of the notification.                              |
+| **Webhooks**               | One or more webhooks to deliver the notification to.              |
+| **Notification email**     | One or more email addresses to deliver the notification to.       |
 
 ## Rule Auto-Advertisement notifications
 
-<Render file="mnm-auto-advertisement-notifications" product="networking-services" />
+<Render
+	file="mnm-auto-advertisement-notifications"
+	product="networking-services"
+/>
 
 ## Configure rule notifications
 
@@ -41,4 +44,4 @@ To configure notifications for Network Flow rules:
    - **Network Flow: Volumetric Attack** - for static threshold and dynamic threshold notifications
    - **Network Flow: DDoS Attack** - for sFlow DDoS attack notifications
 5. Fill in the notification configuration details.
-6. Select **Save**.
\ No newline at end of file
+6. Select **Save**.
diff --git a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
index b3e8a3d3bc9f6f8..bec5f1386000a0d 100644
--- a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
+++ b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
@@ -12,13 +12,13 @@ To send sFlow data to Cloudflare, your router must support sFlow exports. Refer
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | advanced_ddos |
-| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
-| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes). |
+| Field                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                                                                                                                                                                                                              |
+| **Rule type**          | advanced_ddos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| **Prefix Match**       | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
+| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement).                                                                                                                                                                                                                                                  |
+| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes).                                                                                                                                                                                                                                                                    |
 
 ## API documentation
 
@@ -26,4 +26,4 @@ Refer to the [Rules API documentation](/api/resources/magic_network_monitoring/s
 
 ## Tune the sFlow DDoS alert thresholds
 
-You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
\ No newline at end of file
+You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
diff --git a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
index 8f00ec41f108d69..6f3111db0f8feab 100644
--- a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
@@ -10,15 +10,15 @@ To use static threshold rules, you must send NetFlow or sFlow data to Cloudflare
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | threshold |
-| **Rule threshold type** | Can be defined in either bits per second or packets per second. |
-| **Rule threshold** | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum. |
-| **Rule duration** | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes. |
-| **Auto-advertisement** | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes). |
+| Field                   | Description                                                                                                                                                                                                                                                                                                                    |
+| :---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**           | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                     |
+| **Rule type**           | threshold                                                                                                                                                                                                                                                                                                                      |
+| **Rule threshold type** | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                |
+| **Rule threshold**      | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum.                                                                                                                                       |
+| **Rule duration**       | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes.                                                                                                                                         |
+| **Auto-advertisement**  | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
+| **Rule IP prefix**      | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes).                                                                                                          |
 
 ## API documentation
 
@@ -45,9 +45,9 @@ When you first configure Network Flow, you may not know the typical traffic patt
 This lets you collect baseline traffic data without receiving alerts. After configuring your initial rules, monitor for alerts and review traffic in Network Flow Analytics. Over time, update each rule's threshold based on historical traffic data.
 
 | Threshold type | Recommended rule threshold to collect initial data |
-| :---- 				 | :---- 																						  |
-| Bits 					 | 10 Gbps (10,000,000,000 bits per second) 					|
-| Packets 			 | 10 Mpps (10,000,000 packets per second) 						|
+| :------------- | :------------------------------------------------- |
+| Bits           | 10 Gbps (10,000,000,000 bits per second)           |
+| Packets        | 10 Mpps (10,000,000 packets per second)            |
 
 #### Setting the appropriate threshold
 
@@ -64,9 +64,9 @@ To find the maximum non-attack traffic for a one minute time interval over the p
 2. Select **Add filter**.
 3. In **New filter**, use the drop-down menus to create the following filter:
 
-| Field 						| Operator | Rule name 			|
-| :---- 						| :---- 	 | :---- 		 			|
-| _Monitoring Rule_ | _equals_ | `<RULE_NAME>`  |
+| Field             | Operator | Rule name     |
+| :---------------- | :------- | :------------ |
+| _Monitoring Rule_ | _equals_ | `<RULE_NAME>` |
 
 Once the rule filter is selected in Network Flow Analytics, you can check the historical traffic volume data for the rule over the selected time period. Cloudflare recommends reviewing historical data in seven-day increments, since that is the largest window that shows one-hour time intervals. To select a custom seven-day range, go to the top right corner of Network Flow analytics, open the time window drop-down menu, and select **Custom range**.
 
@@ -80,4 +80,4 @@ Your IP prefixes may experience inconsistent spikes across one-minute intervals.
 
 ### Adjusting rules over time
 
-After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
\ No newline at end of file
+After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
diff --git a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
index db70332705ae2dc..87ca7eb4eb1d41c 100644
--- a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
+++ b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
@@ -2,7 +2,6 @@
 {}
 ---
 
-
 import { GlossaryTooltip, DashButton } from "~/components";
 
 Use the GraphQL Analytics API to retrieve Network Flow (formerly Magic Network Monitoring) <GlossaryTooltip term="flow data">flow data</GlossaryTooltip>.
diff --git a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
index 1afc04ea7741587..2849ce921c3e6a5 100644
--- a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
+++ b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
@@ -6,7 +6,7 @@ Instructions to adjust MSS by applying MSS clamps vary depending on the vendor o
 
 The following table lists several commonly used router vendors with links to MSS clamping instructions:
 
-| Router device | URL |
-| ---					  | --- |
+| Router device | URL                                                                                                                                                                                    |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cisco         | [TCP IP Adjust MSS](https://www.cisco.com/en/US/docs/ios-xml/ios/ipapp/command/ip_tcp_adjust-mss_through_ip_wccp_web-cache_accelerated.html#GUID-68044D35-A53E-42C1-A7AB-9236333DA8C4) |
-| Juniper | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html) |
+| Juniper       | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html)                                           |
diff --git a/src/content/partials/networking-services/reference/longest-prefix-match.mdx b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
index 562deeae9654317..98fb9a953cd67de 100644
--- a/src/content/partials/networking-services/reference/longest-prefix-match.mdx
+++ b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
\ No newline at end of file
+Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
diff --git a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
index 4b89061153d1dcb..660c84eea51122e 100644
--- a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
+++ b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
@@ -4,14 +4,14 @@
 
 Cloudflare has nine geographic regions:
 
-| Region code | Region |
-| ----- | ----- |
-| `AFR` | Africa |
-| `APAC` | Asia Pacific |
-| `EEUR` | Eastern Europe |
-| `ENAM` | Eastern North America |
-| `ME` | Middle East |
-| `OC` | Oceania |
-| `SAM` | South America |
-| `WEUR` | Western Europe |
-| `WNAM` | Western North America |
+| Region code | Region                |
+| ----------- | --------------------- |
+| `AFR`       | Africa                |
+| `APAC`      | Asia Pacific          |
+| `EEUR`      | Eastern Europe        |
+| `ENAM`      | Eastern North America |
+| `ME`        | Middle East           |
+| `OC`        | Oceania               |
+| `SAM`       | South America         |
+| `WEUR`      | Western Europe        |
+| `WNAM`      | Western North America |
diff --git a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
index 4dddd911617f979..666d6fb81f454a0 100644
--- a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
+++ b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
@@ -21,7 +21,8 @@ A tunnel health check probe travels from Cloudflare to the tunnel origin, then r
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN"
+		productName:
+			props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN",
 	}}
 />
 
@@ -113,12 +114,12 @@ To avoid control plane policies enforced by the origin network, you can set tunn
 
 ### Summary table with tunnel health check probe types
 
-| Attribute 					| Type 					| Unidirectional health checks | Bidirectional health checks |
-| :---: 							| :---: 				| :---: 											 | :---: 											 |
-| Source Address 			| Request Style | Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
-| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) |Origin Interface Address (Privately Routable) / Custom Target |
-| Source Address 			| Reply Style		| Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-| Destination Address | Reply Style 	| Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
+|      Attribute      |     Type      |        Unidirectional health checks        |                  Bidirectional health checks                  |
+| :-----------------: | :-----------: | :----------------------------------------: | :-----------------------------------------------------------: |
+|   Source Address    | Request Style |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
+| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+|   Source Address    |  Reply Style  | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+| Destination Address |  Reply Style  |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
 
 ### Graphics summarizing health check types
 
@@ -223,9 +224,10 @@ accDescr: Shows the flow of a unidirectional echo reply health check from Cloudf
 	product="networking-services"
 	params={{
 		mFirewallName: "Cloudflare Network Firewall rules",
-		mFirewallURL: "/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks"
+		mFirewallURL:
+			"/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks",
 	}}
-	/>
+/>
 
 Every Cloudflare data center configured to process your traffic sends tunnel health check probes. The rate at which Cloudflare sends these probes varies based on tunnel and location. You can tune this rate on a per-tunnel basis by modifying the `health_check` rate with the <a href={props.changeHealthCheckRate}>API or the dashboard</a>. You can set the rate as _low_, _mid_, or _high_, with _mid_ being the default.
 
@@ -233,7 +235,6 @@ The actual rate formula considers the number of servers in a Cloudflare data cen
 
 When a probe attempt fails for a <a href={props.probeHealth}>healthy tunnel</a>, each server detecting the failure quickly probes up to two more times to obtain an accurate result. Cloudflare does the same if a tunnel has been down and probes start returning success. Because Cloudflare global network servers send probes up to every second, your network will receive several hundred health check packets per second. Each Cloudflare data center sends only one health check packet as part of a probe, representing a relatively trivial amount of traffic.
 
-
 ## Health state and prioritization
 
 There are three tunnel health states: healthy, degraded, and down.
@@ -305,4 +306,4 @@ Suppose the connectivity issue that set Tunnel 1 health to down becomes resolved
 
 When all three probes return successfully, {props.productName} transitions the tunnel from down to degraded. As part of this transition, Cloudflare reduces the priority penalty for that route so that its priority becomes `500,100`. Because Tunnel 2 has a priority of `200`, traffic continues to flow over Tunnel 2.
 
-Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
\ No newline at end of file
+Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
diff --git a/src/content/partials/networking-services/routing/anycast-warning.mdx b/src/content/partials/networking-services/routing/anycast-warning.mdx
index 4a70b0d9c18b322..581fa4d4006258c 100644
--- a/src/content/partials/networking-services/routing/anycast-warning.mdx
+++ b/src/content/partials/networking-services/routing/anycast-warning.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Anycast routing]
 Cloudflare uses anycast to route traffic. Anycast is a network addressing and routing method that routes incoming requests to different locations. Traffic can arrive at a different geographic location than expected. Not all requests go to the closest data center because Internet routing and peering relationships are complex, and Cloudflare optimizes for performance and reliability.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/routing/bgp-config-steps.mdx b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
index ddf3fa73d94cc70..49bffd5bd2831f1 100644
--- a/src/content/partials/networking-services/routing/bgp-config-steps.mdx
+++ b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
@@ -10,16 +10,16 @@ import { Aside, Markdown } from "~/components";
 5. <Markdown text={props.locateText} />
 6. In **Customer device ASN**, enter the ASN for your network.
 
-	{ props.magicWord !== "Magic Transit" && (
-		<>
-		<Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
-		</>
-		)
-	}
+   { props.magicWord !== "Magic Transit" && (
+   <>
+   <Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
+   </>
+   )
+   }
 
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations and is not a security mechanism.
 8. (Optional) In **Additional Advertised prefix list**, input any additional prefixes you want to advertise alongside your existing routes. Leave this blank if you do not want to advertise extra routes. Typical prefixes to configure here include:
-	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
-	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
-	{ props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
+   - A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
+   - A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
+     { props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
 9. Select **Save**.
diff --git a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
index 2c65310f9047a4a..b45261be84bfb8e 100644
--- a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
+++ b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
@@ -7,6 +7,7 @@ params:
 import { APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 You can configure the source IP address range used by Cloudflare whenever a Cloudflare service, such as Cloudflare Load Balancing, sends traffic to a Cloudflare One private network. This address range is referred to as the Cloudflare Source IP Prefix (or `cloudflare_source` subnet type in the API).
+
 - IPv4 traffic is sourced from `100.64.0.0/12`. This range is configurable.
 - IPv6 traffic is sourced from `2606:4700:cf1:5000::/64`. This range is not configurable.
 
@@ -25,6 +26,7 @@ You must configure routes in your network so that response traffic for these sou
 ## Prerequisites
 
 Before you begin, ensure that:
+
 - You have Cloudflare One <a href={props.unifiedRoutingLink}>Unified Routing (beta)</a>. If your account is not yet on Unified Routing, contact your account team to discuss migration and availability.
 - You have [Cloudflare One Networks Write](/fundamentals/api/reference/permissions/) permission.
 - Your desired new network range meets the following requirements:
diff --git a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
index 17e4497d25e28e8..d22d6e489c92663 100644
--- a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
+++ b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
@@ -37,7 +37,7 @@ Choose this option if you have a single VPC in your cloud to connect to Cloudfla
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -74,7 +74,7 @@ When you configure a hub on-ramp, Cloudflare always manages the VPN tunnel betwe
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -105,7 +105,7 @@ You have successfully created your Cloudflare WAN on-ramp. However, on-ramp crea
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -156,7 +156,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, select **Add new on-ramp** and begin the **Create a Cloudflare WAN cloud on-ramp** workflow following the standard steps.
@@ -169,7 +169,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the on-ramp you want to download > select the three dots > **Download as Terraform**.
@@ -186,7 +186,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to edit.
@@ -203,7 +203,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to delete.
@@ -227,7 +227,7 @@ To override the defaults with custom prefixes:
 
 1. Go to the **Routes** page.
 
-	<DashButton url="/?to=/:account/magic-networks/routes" />
+   <DashButton url="/?to=/:account/magic-networks/routes" />
 
 2. Select **WAN configuration**.
 3. Scroll to **Propagated routes to cloud networks**.
@@ -244,7 +244,7 @@ You can view estimated costs associated with your cloud resources in the Cloudfl
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the cloud on-ramp for which you want to check the estimated costs > select the three dots > **Associated Resources**.
diff --git a/src/content/partials/networking-services/sites/sites-brief.mdx b/src/content/partials/networking-services/sites/sites-brief.mdx
index b562aa89e9a4045..cea114893c8546c 100644
--- a/src/content/partials/networking-services/sites/sites-brief.mdx
+++ b/src/content/partials/networking-services/sites/sites-brief.mdx
@@ -5,4 +5,4 @@ params:
 
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that Cloudflare notifies you when there are issues with the site's on-ramps.
 
-Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
\ No newline at end of file
+Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx
index e49acf781ff2f8d..ab902ad3cbb22b4 100644
--- a/src/content/partials/networking-services/sites/sites.mdx
+++ b/src/content/partials/networking-services/sites/sites.mdx
@@ -13,6 +13,7 @@ import { Markdown, Render, DashButton } from "~/components";
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to quickly check the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
 
 To use a site, start by setting up your on-ramps. On-ramps can be:
+
 - <a href={props.greIpsecTunnelsURL}>GRE or IPsec tunnels</a>
 - <a href={props.connectorURL}>{props.connectorName}</a>
 - Direct <a href={props.cniURL}>CNI link</a>
@@ -22,9 +23,9 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 ## Add a site
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview**, select **Add site**.
@@ -38,35 +39,36 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 		11. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
 		12. Select **Complete setup** to finish setting up your site.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
-	<DashButton url="/?to=/:account/networking-insights/health" />
-
-		<Markdown
-		text={`
-		2. In **Network overview**, select **Add a site**.
-		3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
-		4. Select **Create and continue**.
-		5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
-		6. Select **Continue**.
-		7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
-		8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
-		9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-		10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
-		11. Select **Complete setup** to finish setting up your site.
-		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+
+    	<Markdown
+    	text={`
+    	2. In **Network overview**, select **Add a site**.
+    	3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
+    	4. Select **Create and continue**.
+    	5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
+    	6. Select **Continue**.
+    	7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
+    	8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
+    	9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
+    	10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
+    	11. Select **Complete setup** to finish setting up your site.
+    	`}
+    	inline={false}
+    />
+    </>
+
 )
 }
 
@@ -82,10 +84,13 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 	params={{
 		instructions: "",
 		magicWord: props.magicWord,
-		networkOverviewPageName: props.magicWord === "CF1 Cloudflare WAN" ? "Network visibility" : "Network overview",
+		networkOverviewPageName:
+			props.magicWord === "CF1 Cloudflare WAN"
+				? "Network visibility"
+				: "Network overview",
 		magicTunnelHcsURL: props.magicTunnelHcsURL,
-		setGeoCoordinatesURL: "#set-geographic-coordinates"
-		}}
+		setGeoCoordinatesURL: "#set-geographic-coordinates",
+	}}
 />
 
 ---
@@ -95,9 +100,9 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 ### Add or remove on-ramps
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
@@ -105,31 +110,32 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 		5. Select **Add** to add a new on-ramp.
 		6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
+inline={false}
+/>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
+    <DashButton url="/?to=/:account/networking-insights/health" />
+
+    <Markdown
+    	text={`
+    	2. Go to **Network overview** > **Traffic overview**.
+    	3. Find your site > select the three dots in front of it > **Edit**.
+    	3. Select **On-ramps**.
+    	4. Select **Add** to add a new on-ramp.
+    	5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
+    	`}
+    	inline={false}
+    />
+    </>
 
-	<Markdown
-		text={`
-		2. Go to **Network overview** > **Traffic overview**.
-		3. Find your site > select the three dots in front of it > **Edit**.
-		3. Select **On-ramps**.
-		4. Select **Add** to add a new on-ramp.
-		5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
-		`}
-		inline={false}
-	/>
-	</>
 )
 }
 
@@ -138,36 +144,34 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 If you add geographic coordinates to your site, it will appear in the Network map. To set up or edit geographic coordinates to an existing site:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to **Insights** > **Network visibility**.
 		2. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
-	<DashButton url="/?to=/:account/networking-insights/health" />
-		<Markdown
-		text={`
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+<Markdown
+text={`
 		2. Go to **Network overview** > **Traffic overview**.
 		3. Find your site > select the three dots in front of it > **Edit**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 )
-}
-3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
-4. Select **Save**.
+} 3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates. 4. Select **Save**.
 
 ### Set thresholds for site health
 
@@ -176,6 +180,6 @@ If you add geographic coordinates to your site, it will appear in the Network ma
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: props.magicTunnelHcsURL
+		magicTunnelHcsURL: props.magicTunnelHcsURL,
 	}}
 />
diff --git a/src/content/partials/networking-services/troubleshoot-connectivity.mdx b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
index 9a288f95f8861fd..3c84b2a29e2bedd 100644
--- a/src/content/partials/networking-services/troubleshoot-connectivity.mdx
+++ b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
@@ -74,7 +74,7 @@ You can identify which data centers handle your traffic by using **Network Analy
 
 1. Go to the **Network Analytics** page.
 
-	<DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
+   <DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
 
 2. Select **Add filter** and filter traffic by your source IP addresses to isolate your traffic.
 3. Under **Packets summary**, select the **Source data center** tab. If the tab is not visible, select the three-dot menu (`...`) to reveal additional view options and select **Source data center**.
@@ -112,8 +112,13 @@ If you have worked through this guide and cannot resolve the issue, gather the f
 
 ## Related resources
 
-- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
-- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose routing and BGP issues that affect traffic delivery.
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Monitor tunnel status per data center.
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on how health checks work.
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic patterns over time.
+- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve
+  common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
+- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose
+  routing and BGP issues that affect traffic delivery.
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
+  Monitor tunnel status per data center.
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
+  details on how health checks work.
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic
+  patterns over time.
diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
index 33f16ff7be38ee7..f91d7cf6d89d54e 100644
--- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
+++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
@@ -8,7 +8,13 @@ params:
   - magicWord?
 ---
 
-import { Aside, AnchorHeading, DashButton, GlossaryTooltip, Markdown } from "~/components";
+import {
+	Aside,
+	AnchorHeading,
+	DashButton,
+	GlossaryTooltip,
+	Markdown,
+} from "~/components";
 
 The Cloudflare dashboard monitors the health of all <GlossaryTooltip term="anycast">anycast</GlossaryTooltip> tunnels on your account that route traffic from Cloudflare to your origin network.
 
@@ -23,9 +29,9 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 ## Check tunnel health
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
@@ -34,33 +40,34 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
 		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-
-		<Markdown
-			text={`
-			1. Go to the **Network health** page.
-				`}
-			inline={false}
-		/>
-
-		<DashButton url="/?to=/:account/networking-insights/health" />
-
-		<Markdown
-			text={`
-			2. Select the **Connector health** tab.
-			3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
-			4. Find the tunnel you want to inspect, select the three dots next to it, and select:
-				- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
-				- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
-			5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
-			`}
-			inline={false}
-		/>
-	</>
+<>
+
+    	<Markdown
+    		text={`
+    		1. Go to the **Network health** page.
+    			`}
+    		inline={false}
+    	/>
+
+    	<DashButton url="/?to=/:account/networking-insights/health" />
+
+    	<Markdown
+    		text={`
+    		2. Select the **Connector health** tab.
+    		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+    		4. Find the tunnel you want to inspect, select the three dots next to it, and select:
+    			- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
+    			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
+    		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
+    		`}
+    		inline={false}
+    	/>
+    </>
+
 )
 }
 
@@ -69,48 +76,50 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 You can drill down into a specific tunnel to check its health status and other information.
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
 
-	<Markdown
-			text={`
-			1. Go to the **Network health** page.
-				`}
-			inline={false}
-		/>
+    <Markdown
+    		text={`
+    		1. Go to the **Network health** page.
+    			`}
+    		inline={false}
+    	/>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
+    <DashButton url="/?to=/:account/networking-insights/health" />
 
-	<Markdown
-			text={`
-2. Select the **Connector health** tab.
-			`}
-			inline={false}
-		/>
-	</>
-)
-}
+    <Markdown
+    		text={`
 
+2. Select the **Connector health** tab.
+   `}
+   inline={false}
+   />
+   </>
+   )
+   }
 
 3. Find and select the tunnel you want to inspect.
 
 The next view displays detailed information about the tunnel, including:
+
 - Status information
-	- Up: More than 80% of health checks pass.
-	- Degraded: More than 40% of health checks pass.
-	- Down: Less than 40% of health checks pass.
+  - Up: More than 80% of health checks pass.
+  - Degraded: More than 40% of health checks pass.
+  - Down: Less than 40% of health checks pass.
 - Health checks passed in the last hour
 - Traffic volume in the last hour
 
 If you select the three dots in front of the tunnel you want to inspect, you have access to the following tools:
+
 - Packet captures: Collect <a href={props.packetCaptures}>packet level data for your traffic</a>
 - Network Analytics: Leverage real-time insights into <a href={props.networkAnalytics}>network analytics</a>.
diff --git a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
index 7b2222fb7119eaf..40f78d258f68ce4 100644
--- a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
+++ b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
@@ -5,4 +5,4 @@ params:
 
 :::note
 {props.productName} customers with [Customer Metadata Boundary](/data-localization/metadata-boundary/) enabled for the European Union can access GRE, IPsec, and CNI (Cloudflare Network Interconnect) health check and traffic volume data in the Cloudflare dashboard and through the API. This ensures that customers who need to be General Data Protection Regulation (GDPR) compliant can access all {props.productName} features.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
index d9eecdf681026ce..a4314a796e274e0 100644
--- a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
+++ b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
@@ -8,14 +8,14 @@ params:
 ---
 
 import {
-  APIRequest,
-  Code,
-  Details,
-  GlossaryTooltip,
-  Render,
-  Tabs,
-  TabItem,
-  DashButton,
+	APIRequest,
+	Code,
+	Details,
+	GlossaryTooltip,
+	Render,
+	Tabs,
+	TabItem,
+	DashButton,
 } from "~/components";
 
 You can configure Tunnel Health Alerts (formerly Magic Tunnel health alerts) to receive email, webhook, and PagerDuty notifications when the percentage of successful <GlossaryTooltip term="tunnel health-check">health checks</GlossaryTooltip> for an IPsec/GRE tunnel drops below the selected <a href={props.magicTunnelHealthCheckCalculation}>service-level objective (SLO)</a>.
@@ -42,14 +42,14 @@ Currently, there are seven SLO threshold values that you can configure through t
 The SLO threshold for Tunnel health alerts is the percentage of successful health checks for each IPsec/GRE tunnel in the alert:
 
 | Alert Sensitivity Level | SLO threshold |
-| --- 										| --- 					|
-| Minimum 								| 95.0 					|
-| Very low 								| 96.0					|
-| Low 										| 97.0 					|
-| Medium 									| 98.0 					|
-| High 										| 99.0 					|
-| Very high 							| 99.5					|
-| Maximum 								| 99.9					|
+| ----------------------- | ------------- |
+| Minimum                 | 95.0          |
+| Very low                | 96.0          |
+| Low                     | 97.0          |
+| Medium                  | 98.0          |
+| High                    | 99.0          |
+| Very high               | 99.5          |
+| Maximum                 | 99.9          |
 
 The time it takes to receive alerts depends on the sensitivity level you configure for your SLO thresholds. Higher sensitivity levels notify you faster when a tunnel's health degrades, but they may also trigger alerts for brief or minor disruptions. Lower sensitivity levels reduce the chance of false alarms but may delay notifications for less severe issues.
 
@@ -57,7 +57,6 @@ While the underlying detection timing remains consistent across sensitivity leve
 
 For details, refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Tunnel health alerts</a>.
 
-
 ## Set up Tunnel Health Alerts
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
index 87ae557ab8ac1a5..be3e95d154d505a 100644
--- a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
@@ -5,4 +5,4 @@ params:
 
 Cloudflare One Appliance (formerly Magic WAN Connector) also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare through HTTPS and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
-Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
\ No newline at end of file
+Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
diff --git a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
index 83373e4b20668f6..a3df68499495d50 100644
--- a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
@@ -19,15 +19,15 @@ This guide helps you diagnose and resolve common tunnel health issues with {prop
 
 Use the following table to match your symptom to the most likely cause and first action:
 
-| Symptom | Most likely cause | First action |
-| :------ | :---------------- | :----------- |
-| Tunnel shows Down, never becomes healthy | Configuration mismatch or firewall blocking IKE | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures). |
-| Dashboard shows "100% degraded" for some colos | Normal — this is a state indicator, not packet loss | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard). |
-| Tunnel flaps between healthy and unhealthy | Anti-replay protection or rekey disruption | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops). |
-| Health checks fail but traffic flows normally | Stateful firewall dropping health check probes | Change health check type from *Reply* to *Request*. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
-| Health checks fail on policy-based VPN tunnels | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
-| All tunnels degraded or down in a specific region | Network path issue between that region and your network | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare. |
-| All tunnels degraded or down globally | Issue at your network edge | Check your tunnel endpoint router and upstream connectivity. |
+| Symptom                                           | Most likely cause                                         | First action                                                                                                                                        |
+| :------------------------------------------------ | :-------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Tunnel shows Down, never becomes healthy          | Configuration mismatch or firewall blocking IKE           | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures).                    |
+| Dashboard shows "100% degraded" for some colos    | Normal — this is a state indicator, not packet loss       | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard).              |
+| Tunnel flaps between healthy and unhealthy        | Anti-replay protection or rekey disruption                | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops).                      |
+| Health checks fail but traffic flows normally     | Stateful firewall dropping health check probes            | Change health check type from _Reply_ to _Request_. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
+| Health checks fail on policy-based VPN tunnels    | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
+| All tunnels degraded or down in a specific region | Network path issue between that region and your network   | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare.                                                          |
+| All tunnels degraded or down globally             | Issue at your network edge                                | Check your tunnel endpoint router and upstream connectivity.                                                                                        |
 
 ### What you can check
 
@@ -46,7 +46,7 @@ Use the following table to match your symptom to the most likely cause and first
 
 If you are experiencing tunnel health issues, check these items first:
 
-1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from *Reply* to *Request*.
+1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from _Reply_ to _Request_.
 2. **Anti-replay protection**: Disable anti-replay protection on your router, or set the replay window to `0`.
 3. **MTU settings**: Verify MTU is set correctly (typically `1476` for GRE, `1400`-`1450` for IPsec).
 4. **IPsec parameters**: Confirm your cryptographic parameters match <a href={props.tunnelsConfigLink}>Cloudflare's supported configuration</a>.
@@ -59,11 +59,11 @@ If you are experiencing tunnel health issues, check these items first:
 
 The [Network health](https://dash.cloudflare.com/?to=/:account/networking-insights/health) page in the Cloudflare dashboard displays three tunnel health states:
 
-| State | Dashboard display | Technical threshold |
-| :---- | :---- | :---- |
-| **Healthy** | More than 80% of health checks pass | Less than 0.1% failure rate |
+| State        | Dashboard display                         | Technical threshold                                                |
+| :----------- | :---------------------------------------- | :----------------------------------------------------------------- |
+| **Healthy**  | More than 80% of health checks pass       | Less than 0.1% failure rate                                        |
 | **Degraded** | Between 40% and 80% of health checks pass | At least 0.1% failures in last five minutes (minimum two failures) |
-| **Down** | Less than 40% of health checks pass | All health checks failed (at least three samples in last second) |
+| **Down**     | Less than 40% of health checks pass       | All health checks failed (at least three samples in last second)   |
 
 The dashboard shows tunnel health as measured from each Cloudflare data center where your traffic lands. It is normal to see some locations reporting degraded status due to Internet path issues. Focus on locations that show traffic in the **Traffic volume (1h)** column.
 
@@ -122,16 +122,16 @@ For instructions on monitoring tunnel status, refer to <a href={props.checkHealt
 
 **Health check type:**
 
-| Type | Behavior | When to use |
-| :---- | :---- | :---- |
-| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls |
-| **Request** | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
+| Type                | Behavior                              | When to use                                                         |
+| :------------------ | :------------------------------------ | :------------------------------------------------------------------ |
+| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls                          |
+| **Request**         | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
 
 **Health check direction:**
 
-| Direction | Behavior | Default for |
-| :---- | :---- | :--- |
-| **Bidirectional** | Probe and response both traverse the tunnel | Cloudflare WAN (formerly Magic WAN) |
+| Direction          | Behavior                                              | Default for                          |
+| :----------------- | :---------------------------------------------------- | :----------------------------------- |
+| **Bidirectional**  | Probe and response both traverse the tunnel           | Cloudflare WAN (formerly Magic WAN)  |
 | **Unidirectional** | Probe traverses tunnel; response returns via Internet | Magic Transit (direct server return) |
 
 :::note
@@ -152,23 +152,23 @@ Unidirectional health checks can be unreliable because intermediate network devi
 
 #### Cause
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP *Reply* packets as health check probes.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP _Reply_ packets as health check probes.
 
-Stateful firewalls inspect these packets and look for a matching ICMP *Request* in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
+Stateful firewalls inspect these packets and look for a matching ICMP _Request_ in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
 
 #### Solution
 
-Change the health check type from *Reply* to *Request*:
+Change the health check type from _Reply_ to _Request_:
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on the affected tunnel.
-3. Under **Health check type**, change from *Reply* to *Request*.
+3. Under **Health check type**, change from _Reply_ to _Request_.
 4. Select **Update tunnel**.
 
-When you use *Request* style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
+When you use _Request_ style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
 
 :::note
 If your firewall drops ICMP request packets as well, verify that your firewall policy permits ICMP traffic on the tunnel interface.
@@ -190,21 +190,21 @@ Cloudflare Network Firewall processes all traffic, including Cloudflare's health
 
 #### Solution
 
-Add an allow rule for ICMP traffic from Cloudflare IP addresses *before* any block rules:
+Add an allow rule for ICMP traffic from Cloudflare IP addresses _before_ any block rules:
 
 1. Go to the **Firewall policies** page.
 
-	<DashButton url="/?to=/:account/network-security/magic_firewall" />
+   <DashButton url="/?to=/:account/network-security/magic_firewall" />
 
 2. Create a new policy with the following parameters:
 
-| Field | Value |
-| :---- | :---- |
-| **Action** | Allow |
-| **Protocol** | ICMP |
-| **Source** | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
+| Field        | Value                                               |
+| :----------- | :-------------------------------------------------- |
+| **Action**   | Allow                                               |
+| **Protocol** | ICMP                                                |
+| **Source**   | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
 
-3. Position this rule *before* any rules that block ICMP traffic.
+3. Position this rule _before_ any rules that block ICMP traffic.
 
 For more information, refer to [Cloudflare Network Firewall rules and endpoint health checks](/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks).
 
@@ -246,7 +246,7 @@ Enable replay protection in the Cloudflare dashboard. This routes all tunnel tra
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on your IPsec tunnel.
 3. Enable **Replay protection**.
@@ -294,13 +294,11 @@ This behavior is expected and the tunnel will automatically recover. To minimize
 2. **Increase rekey intervals**: Configure longer SA lifetimes on your tunnel endpoint to reduce rekey frequency. Common values are 8-24 hours for IKE SA and 1-8 hours for IPsec SA.
 
 3. **Adjust health check sensitivity**: If brief degradation during rekeys triggers alerts, consider lowering the health check rate:
-
    1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
-
+   <DashButton url="/?to=/:account/magic-networks/connections" />
    2. In **IPsec/GRE tunnels**, select **Edit** on the tunnel.
-   3. Change **Health check rate** to *Low*.
+   3. Change **Health check rate** to _Low_.
 
 4. **Stagger rekey times**: If you have multiple tunnels, configure different SA lifetimes so they do not rekey simultaneously.
 
@@ -352,12 +350,12 @@ For detailed information on how bidirectional health checks work, refer to <a hr
 
 IPsec tunnel establishment can fail due to several configuration mismatches:
 
-| Issue | Symptom |
-| :---- | :---- |
+| Issue                         | Symptom                                         |
+| :---------------------------- | :---------------------------------------------- |
 | **Crypto parameter mismatch** | IKE negotiation fails with "no proposal chosen" |
-| **Incorrect PSK** | Authentication failures in Phase 1 |
-| **Wrong IKE ID format** | Authentication failures despite correct PSK |
-| **Firewall blocking IKE** | No IKE traffic reaches Cloudflare |
+| **Incorrect PSK**             | Authentication failures in Phase 1              |
+| **Wrong IKE ID format**       | Authentication failures despite correct PSK     |
+| **Firewall blocking IKE**     | No IKE traffic reaches Cloudflare               |
 
 #### Solution
 
@@ -365,24 +363,22 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 
    **Phase 1 (IKE)**
 
+| Parameter      | Supported values            |
+| :------------- | :-------------------------- |
+| IKE version    | IKEv2 only                  |
+| Encryption     | AES-GCM-16, AES-CBC-256     |
+| Authentication | SHA-256, SHA-384, SHA-512   |
+| DH Group       | DH group 14, 15, 16, 19, 20 |
 
-| Parameter | Supported values |
-| :---- | :---- |
-| IKE version | IKEv2 only |
-| Encryption | AES-GCM-16, AES-CBC-256 |
-| Authentication | SHA-256, SHA-384, SHA-512 |
-| DH Group | DH group 14, 15, 16, 19, 20 |
-
-   **Phase 2 (IPsec)**
+**Phase 2 (IPsec)**
 
-| Parameter | Supported values |
-| :---- | :---- |
-| Encryption | AES-GCM-16, AES-CBC-256 |
-| Authentication | SHA-256, SHA-512 |
-| PFS Group | DH group 14, 15, 16, 19, 20 |
+| Parameter      | Supported values            |
+| :------------- | :-------------------------- |
+| Encryption     | AES-GCM-16, AES-CBC-256     |
+| Authentication | SHA-256, SHA-512            |
+| PFS Group      | DH group 14, 15, 16, 19, 20 |
 
 2. **Verify the Pre-Shared Key (PSK):**
-
    - Regenerate the PSK in the Cloudflare dashboard
    - Copy the new PSK exactly (no extra spaces or characters)
    - Update your router with the new PSK
@@ -390,7 +386,6 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 3. **Check the IKE ID format:** Cloudflare uses FQDN format for the IKE ID. Ensure your router is configured to accept an FQDN peer identity. The FQDN is displayed in the tunnel details in the Cloudflare dashboard.
 
 4. **Verify firewall rules:** Ensure your edge firewall permits:
-
    - UDP port `500` (IKE)
    - UDP port `4500` (IKE NAT-T)
    - IP protocol `50` (ESP)
@@ -415,7 +410,7 @@ Additionally, some firewalls (such as Check Point) may flag Reply-style health c
 
 #### Solution
 
-1. Change the health check type from *Reply* to *Request*.
+1. Change the health check type from _Reply_ to _Request_.
 2. Configure a loopback address on your tunnel endpoint as the health check target. The target must be:
    - Routable from the tunnel endpoint
    - Covered by the tunnel's traffic selectors (encryption domain)
@@ -431,13 +426,13 @@ Policy-based tunnels use a separate Child SA for each set of traffic selectors.
 
 ### Common vendor-specific issues
 
-| Vendor | Common issue | Solution |
-| :---- | :---- | :---- |
-| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to *Request*; disable anti-replay |
-| **Cisco Meraki** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **AWS VPN Gateway** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **VeloCloud** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **Check Point** | Out-of-state packet drops | Change health check type to *Request* |
+| Vendor                 | Common issue                             | Solution                                                   |
+| :--------------------- | :--------------------------------------- | :--------------------------------------------------------- |
+| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to _Request_; disable anti-replay |
+| **Cisco Meraki**       | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **AWS VPN Gateway**    | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **VeloCloud**          | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **Check Point**        | Out-of-state packet drops                | Change health check type to _Request_                      |
 
 ---
 
@@ -484,8 +479,13 @@ Collect output from these commands (syntax varies by vendor):
 
 ## Resources
 
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on health check behavior
-- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay must be disabled
-- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel setup instructions
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Dashboard navigation guide
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis tools
\ No newline at end of file
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
+  details on health check behavior
+- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay
+  must be disabled
+- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel
+  setup instructions
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
+  Dashboard navigation guide
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis
+  tools
diff --git a/src/content/partials/networking-services/virtual-networks-concept.mdx b/src/content/partials/networking-services/virtual-networks-concept.mdx
index bec7de23f758195..5f791ebd1962872 100644
--- a/src/content/partials/networking-services/virtual-networks-concept.mdx
+++ b/src/content/partials/networking-services/virtual-networks-concept.mdx
@@ -84,18 +84,21 @@ The same CIDR (`10.0.0.0/8`) can exist in each virtual network because they are
 
 Each virtual network maintains its own routing table. Routes added to one virtual network do not appear in another virtual network routing table. However, if traffic does not match a route in the selected virtual network, Cloudflare may fall back to the default virtual network routing table for WAN routes.
 
-<Markdown text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`} inline={false} />
+<Markdown
+	text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`}
+	inline={false}
+/>
 
 ## Virtual networks across Cloudflare
 
 Virtual network support varies by product:
 
-| Product | Virtual network support | Details |
-| --- | --- | --- |
-| Cloudflare Tunnel | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
-| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection |
-| Cloudflare Mesh | Not currently supported | — |
-| Cloudflare WAN | Default only | All IPsec, GRE, and CNI connections use the default virtual network |
+| Product               | Virtual network support   | Details                                                              |
+| --------------------- | ------------------------- | -------------------------------------------------------------------- |
+| Cloudflare Tunnel     | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
+| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection  |
+| Cloudflare Mesh       | Not currently supported   | —                                                                    |
+| Cloudflare WAN        | Default only              | All IPsec, GRE, and CNI connections use the default virtual network  |
 
 ## The default virtual network
 
@@ -120,14 +123,26 @@ If you are familiar with cloud networking concepts, a virtual network is analogo
 
 ## Create and manage virtual networks
 
-<Markdown text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`} inline={false} />
+<Markdown
+	text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`}
+	inline={false}
+/>
 
-<Markdown text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`} inline={false} />
+<Markdown
+	text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`}
+	inline={false}
+/>
 
-<Markdown text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`} inline={false} />
+<Markdown
+	text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`}
+	inline={false}
+/>
 
 ## Related resources
 
-<Markdown text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
+<Markdown
+	text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
 - [Routes](${props.routesURL}) — Define IP and hostname routes through your connectors
-- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`} inline={false} />
+- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`}
+	inline={false}
+/>
diff --git a/src/content/partials/notifications/get-started.mdx b/src/content/partials/notifications/get-started.mdx
index 00b7b4ec3a8f058..829b54d50c6d7ad 100644
--- a/src/content/partials/notifications/get-started.mdx
+++ b/src/content/partials/notifications/get-started.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Refer to [Cloudflare Notifications](/notifications/get-started/) for more information on how to set up an alert.
diff --git a/src/content/partials/pages/c3-adapter.mdx b/src/content/partials/pages/c3-adapter.mdx
index a38fe66ad454db8..32d2a3499fce337 100644
--- a/src/content/partials/pages/c3-adapter.mdx
+++ b/src/content/partials/pages/c3-adapter.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If using [`create-cloudflare` (C3)](https://www.npmjs.com/package/create-cloudflare), you can bypass adding an adapter as C3 automatically installs any necessary adapters and configures them when creating your project.
 
-
 :::
diff --git a/src/content/partials/pages/c3-run-command-no-directory.mdx b/src/content/partials/pages/c3-run-command-no-directory.mdx
index a64961aff54a926..193d0bcd558150b 100644
--- a/src/content/partials/pages/c3-run-command-no-directory.mdx
+++ b/src/content/partials/pages/c3-run-command-no-directory.mdx
@@ -4,5 +4,8 @@
 
 import { PackageManagers } from "~/components";
 
-<PackageManagers type="create" pkg="cloudflare@latest" args="--platform=pages"/>
-
+<PackageManagers
+	type="create"
+	pkg="cloudflare@latest"
+	args="--platform=pages"
+/>
diff --git a/src/content/partials/pages/cli-precedence-over-file.mdx b/src/content/partials/pages/cli-precedence-over-file.mdx
index 11a0cb2f0ebfdd4..b2bc3188eee261f 100644
--- a/src/content/partials/pages/cli-precedence-over-file.mdx
+++ b/src/content/partials/pages/cli-precedence-over-file.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If a binding is specified in a [Wrangler configuration file](/workers/wrangler/configuration/) and via a command-line argument, the command-line argument takes precedence.
 
-
 :::
diff --git a/src/content/partials/pages/custom-domain-steps.mdx b/src/content/partials/pages/custom-domain-steps.mdx
index fee5e4c0dbb152c..20c18cb6fc838aa 100644
--- a/src/content/partials/pages/custom-domain-steps.mdx
+++ b/src/content/partials/pages/custom-domain-steps.mdx
@@ -9,6 +9,7 @@ To add a custom domain:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Custom domains**.
 3. Select **Set up a domain**.
 4. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
index 62859ea9b7e533e..953960ee01038c9 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
@@ -9,6 +9,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
index f70be8044a5cf71..b8561649554de9d 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
@@ -10,6 +10,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/do-note.mdx b/src/content/partials/pages/do-note.mdx
index 44f90d7ff7a4785..6490baa6181c199 100644
--- a/src/content/partials/pages/do-note.mdx
+++ b/src/content/partials/pages/do-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You must create a Durable Object Worker and bind it to your Pages project using the Cloudflare dashboard or your Pages project's [Wrangler configuration file](/pages/functions/wrangler-configuration/). You cannot create and deploy a Durable Object within a Pages project.
diff --git a/src/content/partials/pages/framework-guides/create-gh-repo.mdx b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
index 7d4f7ac729dd198..8e6a0ec2e677e3a 100644
--- a/src/content/partials/pages/framework-guides/create-gh-repo.mdx
+++ b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Create a new GitHub repository by visiting [repo.new](https://repo.new). After creating a new repository, go to your newly created project directory to prepare and push your local application to GitHub by running the following commands in your terminal:
diff --git a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
index 46eb8a378cb57e1..9f8e802cee2e978 100644
--- a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
+++ b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Create a GitHub repository
diff --git a/src/content/partials/pages/framework-guides/git-integration.mdx b/src/content/partials/pages/framework-guides/git-integration.mdx
index b904fe727721313..ce38fa80e780d15 100644
--- a/src/content/partials/pages/framework-guides/git-integration.mdx
+++ b/src/content/partials/pages/framework-guides/git-integration.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Git integration
 
diff --git a/src/content/partials/pages/framework-guides/learn-more.mdx b/src/content/partials/pages/framework-guides/learn-more.mdx
index 412a7475b5f45d7..875e06f11937b9d 100644
--- a/src/content/partials/pages/framework-guides/learn-more.mdx
+++ b/src/content/partials/pages/framework-guides/learn-more.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: deployedTarget
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 ## Learn more
 
diff --git a/src/content/partials/pages/get-started-git-connect-pages.mdx b/src/content/partials/pages/get-started-git-connect-pages.mdx
index 9f0e08f89c4e2e7..e2b68a6f9b7f3cc 100644
--- a/src/content/partials/pages/get-started-git-connect-pages.mdx
+++ b/src/content/partials/pages/get-started-git-connect-pages.mdx
@@ -9,18 +9,17 @@ Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitl
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Connect to Git**.
 
 You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/).
 
 :::note
 
-
 Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages.
 
 If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages.
 
-
 :::
 
 ### Select your GitHub repository
@@ -29,4 +28,4 @@ You can select a GitHub project from your personal account or an organization yo
 
 ### Select your GitLab repository
 
-If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
\ No newline at end of file
+If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
diff --git a/src/content/partials/pages/get-started-git-manage-site.mdx b/src/content/partials/pages/get-started-git-manage-site.mdx
index 0aa235c6ce61425..6be5dbe386c0e10 100644
--- a/src/content/partials/pages/get-started-git-manage-site.mdx
+++ b/src/content/partials/pages/get-started-git-manage-site.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments.
 
@@ -15,16 +15,15 @@ To delete your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings** > **Delete project**.
 
 :::caution
 
-
 For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions.
 
 For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings.
 
-
 :::
 
 ## Advanced project settings
@@ -33,6 +32,6 @@ In the **Settings** section, you can configure advanced settings, such as changi
 
 ## Related resources
 
-* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
-* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
-* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
\ No newline at end of file
+- Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
+- Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
+- Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
diff --git a/src/content/partials/pages/git-integration-warning.mdx b/src/content/partials/pages/git-integration-warning.mdx
index fe22fd4c858b9dd..29972cbf983d1e4 100644
--- a/src/content/partials/pages/git-integration-warning.mdx
+++ b/src/content/partials/pages/git-integration-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Git integration]
 
-
 Currently, you cannot add Git integration to existing Pages applications. If you have already deployed your application, you need to create a new Pages application in order to add Git integration to it.
 
-
 :::
diff --git a/src/content/partials/pages/prod-branch-update.mdx b/src/content/partials/pages/prod-branch-update.mdx
index 09fee36fe5dc103..cc5195454fc9ea4 100644
--- a/src/content/partials/pages/prod-branch-update.mdx
+++ b/src/content/partials/pages/prod-branch-update.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your project is a [Direct Upload](/pages/get-started/direct-upload/) project, you will not have the option to configure production branch controls. To update your production branch, you will need to manually call the [Update Project](/api/resources/pages/subresources/projects/methods/edit/) endpoint in the API.
diff --git a/src/content/partials/pages/tutorials-before-you-start.mdx b/src/content/partials/pages/tutorials-before-you-start.mdx
index 054f3014bbb4e20..828e29a27d7e760 100644
--- a/src/content/partials/pages/tutorials-before-you-start.mdx
+++ b/src/content/partials/pages/tutorials-before-you-start.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Before you continue
diff --git a/src/content/partials/pages/web-analytics-setup.mdx b/src/content/partials/pages/web-analytics-setup.mdx
index 0c4d814773e0860..5b7a79ede654b56 100644
--- a/src/content/partials/pages/web-analytics-setup.mdx
+++ b/src/content/partials/pages/web-analytics-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -8,6 +7,7 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Metrics** and select **Enable** under Web Analytics.
 
diff --git a/src/content/partials/queues/enable-queues.mdx b/src/content/partials/queues/enable-queues.mdx
index 5d055261c9dc78a..2abc709865461de 100644
--- a/src/content/partials/queues/enable-queues.mdx
+++ b/src/content/partials/queues/enable-queues.mdx
@@ -12,6 +12,6 @@ To enable Queues:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select **Enable Queues**.
diff --git a/src/content/partials/queues/event-subscriptions/access-events.mdx b/src/content/partials/queues/event-subscriptions/access-events.mdx
index fc76184e339a0ed..9f74f1279bcec9a 100644
--- a/src/content/partials/queues/event-subscriptions/access-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/access-events.mdx
@@ -6,20 +6,20 @@ Triggered when an application is created.
 
 ```json
 {
-  "type": "cf.access.application.created",
-  "source": {
-    "type": "access"
-  },
-  "payload": {
-    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "My Application"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.access.application.created",
+	"source": {
+		"type": "access"
+	},
+	"payload": {
+		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "My Application"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when an application is deleted.
 
 ```json
 {
-  "type": "cf.access.application.deleted",
-  "source": {
-    "type": "access"
-  },
-  "payload": {
-    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "My Application"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.access.application.deleted",
+	"source": {
+		"type": "access"
+	},
+	"payload": {
+		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "My Application"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
index 520d32a2d17b86f..e25f2024c3d7d08 100644
--- a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
@@ -8,27 +8,27 @@ Triggered when a repository is created.
 
 ```json
 {
-  "type": "cf.artifacts.repo.created",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "0tvugavnogssnwzk",
-    "defaultBranch": "main",
-    "description": "My Artifacts repository",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:46.833Z",
-    "updatedAt": "2026-05-18T15:53:46.833Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:48.187Z"
-  }
+	"type": "cf.artifacts.repo.created",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "0tvugavnogssnwzk",
+		"defaultBranch": "main",
+		"description": "My Artifacts repository",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:46.833Z",
+		"updatedAt": "2026-05-18T15:53:46.833Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:48.187Z"
+	}
 }
 ```
 
@@ -40,27 +40,27 @@ Triggered when a repository is deleted.
 
 ```json
 {
-  "type": "cf.artifacts.repo.deleted",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "0tvugavnogssnwzk",
-    "defaultBranch": "main",
-    "description": "My Artifacts repository",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:46.833Z",
-    "updatedAt": "2026-05-18T15:53:46.833Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:59.914Z"
-  }
+	"type": "cf.artifacts.repo.deleted",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "0tvugavnogssnwzk",
+		"defaultBranch": "main",
+		"description": "My Artifacts repository",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:46.833Z",
+		"updatedAt": "2026-05-18T15:53:46.833Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:59.914Z"
+	}
 }
 ```
 
@@ -72,29 +72,29 @@ Triggered when a repository is forked.
 
 ```json
 {
-  "type": "cf.artifacts.repo.forked",
-  "source": {
-    "type": "artifacts",
-    "namespace": "source-namespace",
-    "repoName": "source-repo"
-  },
-  "payload": {
-    "namespace": "target-namespace",
-    "repoName": "target-repo",
-    "repoId": "5ankv1vhl4xnw7wq",
-    "defaultBranch": "main",
-    "description": "Fork of source-repo",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:52.384Z",
-    "updatedAt": "2026-05-18T15:53:54.579Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:54.641Z"
-  }
+	"type": "cf.artifacts.repo.forked",
+	"source": {
+		"type": "artifacts",
+		"namespace": "source-namespace",
+		"repoName": "source-repo"
+	},
+	"payload": {
+		"namespace": "target-namespace",
+		"repoName": "target-repo",
+		"repoId": "5ankv1vhl4xnw7wq",
+		"defaultBranch": "main",
+		"description": "Fork of source-repo",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:52.384Z",
+		"updatedAt": "2026-05-18T15:53:54.579Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:54.641Z"
+	}
 }
 ```
 
@@ -106,29 +106,29 @@ Triggered when a repository is imported from an external Git remote.
 
 ```json
 {
-  "type": "cf.artifacts.repo.imported",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "d7nd72k964cv9kub",
-    "defaultBranch": "main",
-    "description": null,
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:54.864Z",
-    "updatedAt": "2026-05-18T15:53:57.737Z",
-    "lastPushAt": null,
-    "sourceUrl": "https://github.com/example/repo.git",
-    "branch": "main"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:58.195Z"
-  }
+	"type": "cf.artifacts.repo.imported",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "d7nd72k964cv9kub",
+		"defaultBranch": "main",
+		"description": null,
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:54.864Z",
+		"updatedAt": "2026-05-18T15:53:57.737Z",
+		"lastPushAt": null,
+		"sourceUrl": "https://github.com/example/repo.git",
+		"branch": "main"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:58.195Z"
+	}
 }
 ```
 
@@ -142,44 +142,42 @@ Triggered when commits are pushed to a repository.
 
 ```json
 {
-  "type": "cf.artifacts.repo.pushed",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "ref": "refs/heads/main",
-    "before": "abc123def456abc123def456abc123def456abc1",
-    "after": "def789ghi012def789ghi012def789ghi012def7",
-    "commits": [
-      {
-        "id": "def789ghi012def789ghi012def789ghi012def7",
-        "message": "Fix bug in authentication",
-        "messageTruncated": false,
-        "timestamp": "2025-05-01T02:48:57.000Z",
-        "author": {
-          "name": "Developer Name",
-          "email": "developer@example.com"
-        },
-        "committer": {
-          "name": "Developer Name",
-          "email": "developer@example.com"
-        },
-        "parents": [
-          "abc123def456abc123def456abc123def456abc1"
-        ]
-      }
-    ],
-    "totalCommitsCount": 1,
-    "commitsTruncated": false
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.artifacts.repo.pushed",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"ref": "refs/heads/main",
+		"before": "abc123def456abc123def456abc123def456abc1",
+		"after": "def789ghi012def789ghi012def789ghi012def7",
+		"commits": [
+			{
+				"id": "def789ghi012def789ghi012def789ghi012def7",
+				"message": "Fix bug in authentication",
+				"messageTruncated": false,
+				"timestamp": "2025-05-01T02:48:57.000Z",
+				"author": {
+					"name": "Developer Name",
+					"email": "developer@example.com"
+				},
+				"committer": {
+					"name": "Developer Name",
+					"email": "developer@example.com"
+				},
+				"parents": ["abc123def456abc123def456abc123def456abc1"]
+			}
+		],
+		"totalCommitsCount": 1,
+		"commitsTruncated": false
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -191,19 +189,19 @@ Triggered when a repository is cloned.
 
 ```json
 {
-  "type": "cf.artifacts.repo.cloned",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {},
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:51.358Z"
-  }
+	"type": "cf.artifacts.repo.cloned",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:51.358Z"
+	}
 }
 ```
 
@@ -215,19 +213,19 @@ Triggered when updates are fetched from a repository.
 
 ```json
 {
-  "type": "cf.artifacts.repo.fetched",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {},
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:51.358Z"
-  }
+	"type": "cf.artifacts.repo.fetched",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:51.358Z"
+	}
 }
 ```
 
@@ -239,23 +237,23 @@ Triggered when a repo-scoped token is created. Includes the token ID, scope, and
 
 ```json
 {
-  "type": "cf.artifacts.repo.token.created",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "default",
-    "repoName": "token-evt-repo"
-  },
-  "payload": {
-    "tokenId": "7ngdf3ww3u84t33x",
-    "scope": "read",
-    "expiresAt": "2026-05-20T16:58:14.548Z"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-20T16:58:14.548Z"
-  }
+	"type": "cf.artifacts.repo.token.created",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "default",
+		"repoName": "token-evt-repo"
+	},
+	"payload": {
+		"tokenId": "7ngdf3ww3u84t33x",
+		"scope": "read",
+		"expiresAt": "2026-05-20T16:58:14.548Z"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-20T16:58:14.548Z"
+	}
 }
 ```
 
@@ -267,20 +265,20 @@ Triggered when a repo-scoped token is revoked. Includes the token ID.
 
 ```json
 {
-  "type": "cf.artifacts.repo.token.revoked",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "default",
-    "repoName": "token-evt-repo"
-  },
-  "payload": {
-    "tokenId": "7ngdf3ww3u84t33x"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-20T16:58:14.548Z"
-  }
+	"type": "cf.artifacts.repo.token.revoked",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "default",
+		"repoName": "token-evt-repo"
+	},
+	"payload": {
+		"tokenId": "7ngdf3ww3u84t33x"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-20T16:58:14.548Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/kv-events.mdx b/src/content/partials/queues/event-subscriptions/kv-events.mdx
index 41f5c1399c2dda4..e824a2a4d79909a 100644
--- a/src/content/partials/queues/event-subscriptions/kv-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/kv-events.mdx
@@ -6,20 +6,20 @@ Triggered when a namespace is created.
 
 ```json
 {
-  "type": "cf.kv.namespace.created",
-  "source": {
-    "type": "kv"
-  },
-  "payload": {
-    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "my-kv-namespace"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.kv.namespace.created",
+	"source": {
+		"type": "kv"
+	},
+	"payload": {
+		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "my-kv-namespace"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when a namespace is deleted.
 
 ```json
 {
-  "type": "cf.kv.namespace.deleted",
-  "source": {
-    "type": "kv"
-  },
-  "payload": {
-    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "my-kv-namespace"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.kv.namespace.deleted",
+	"source": {
+		"type": "kv"
+	},
+	"payload": {
+		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "my-kv-namespace"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/r2-events.mdx b/src/content/partials/queues/event-subscriptions/r2-events.mdx
index b50d8c3a1c19d49..30261e144e2610c 100644
--- a/src/content/partials/queues/event-subscriptions/r2-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/r2-events.mdx
@@ -6,22 +6,22 @@ Triggered when a bucket is created.
 
 ```json
 {
-  "type": "cf.r2.bucket.created",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "jurisdiction": "default",
-    "location": "WNAM",
-    "storageClass": "Standard"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.r2.bucket.created",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"jurisdiction": "default",
+		"location": "WNAM",
+		"storageClass": "Standard"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -33,19 +33,19 @@ Triggered when a bucket is deleted.
 
 ```json
 {
-  "type": "cf.r2.bucket.deleted",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "jurisdiction": "default"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.r2.bucket.deleted",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"jurisdiction": "default"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
index 4cae246e7055fa3..0cb885462b37f7b 100644
--- a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
@@ -6,33 +6,33 @@ Triggered when a migration job starts.
 
 ```json
 {
-  "type": "cf.superSlurper.job.started",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "overwrite": true,
-    "pathPrefix": "migrations/",
-    "source": {
-      "provider": "s3",
-      "bucket": "source-bucket",
-      "region": "us-east-1",
-      "endpoint": "s3.amazonaws.com"
-    },
-    "destination": {
-      "provider": "r2",
-      "bucket": "destination-bucket",
-      "jurisdiction": "default"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.started",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"overwrite": true,
+		"pathPrefix": "migrations/",
+		"source": {
+			"provider": "s3",
+			"bucket": "source-bucket",
+			"region": "us-east-1",
+			"endpoint": "s3.amazonaws.com"
+		},
+		"destination": {
+			"provider": "r2",
+			"bucket": "destination-bucket",
+			"jurisdiction": "default"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -44,19 +44,19 @@ Triggered when a migration job pauses.
 
 ```json
 {
-  "type": "cf.superSlurper.job.paused",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.paused",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -68,19 +68,19 @@ Triggered when a migration job resumes.
 
 ```json
 {
-  "type": "cf.superSlurper.job.resumed",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.resumed",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -92,23 +92,23 @@ Triggered when a migration job finishes.
 
 ```json
 {
-  "type": "cf.superSlurper.job.completed",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "totalObjectsCount": 1000,
-    "skippedObjectsCount": 10,
-    "migratedObjectsCount": 980,
-    "failedObjectsCount": 10
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.completed",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"totalObjectsCount": 1000,
+		"skippedObjectsCount": 10,
+		"migratedObjectsCount": 980,
+		"failedObjectsCount": 10
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -120,23 +120,23 @@ Triggered when a migration job is manually aborted.
 
 ```json
 {
-  "type": "cf.superSlurper.job.aborted",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "totalObjectsCount": 1000,
-    "skippedObjectsCount": 100,
-    "migratedObjectsCount": 500,
-    "failedObjectsCount": 50
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.aborted",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"totalObjectsCount": 1000,
+		"skippedObjectsCount": 100,
+		"migratedObjectsCount": 500,
+		"failedObjectsCount": 50
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -148,19 +148,19 @@ Triggered when an object is migrated.
 
 ```json
 {
-  "type": "cf.superSlurper.job.object.migrated",
-  "source": {
-    "type": "superSlurper.job",
-    "jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "payload": {
-    "key": "migrations/file.txt"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.object.migrated",
+	"source": {
+		"type": "superSlurper.job",
+		"jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"payload": {
+		"key": "migrations/file.txt"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
index fbdfca03358751d..e9422149256d246 100644
--- a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
@@ -6,24 +6,24 @@ Triggered when an index is created.
 
 ```json
 {
-  "type": "cf.vectorize.index.created",
-  "source": {
-    "type": "vectorize"
-  },
-  "payload": {
-    "name": "my-vector-index",
-    "description": "Index for embeddings",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "modifiedAt": "2025-05-01T02:48:57.132Z",
-    "dimensions": 1536,
-    "metric": "cosine"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.vectorize.index.created",
+	"source": {
+		"type": "vectorize"
+	},
+	"payload": {
+		"name": "my-vector-index",
+		"description": "Index for embeddings",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"modifiedAt": "2025-05-01T02:48:57.132Z",
+		"dimensions": 1536,
+		"metric": "cosine"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -35,18 +35,18 @@ Triggered when an index is deleted.
 
 ```json
 {
-  "type": "cf.vectorize.index.deleted",
-  "source": {
-    "type": "vectorize"
-  },
-  "payload": {
-    "name": "my-vector-index"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.vectorize.index.deleted",
+	"source": {
+		"type": "vectorize"
+	},
+	"payload": {
+		"name": "my-vector-index"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
index 0353629c8d35492..c28ded25de74231 100644
--- a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
@@ -6,20 +6,20 @@ Triggered when a batch request is queued.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.queued",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.queued",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,20 +31,20 @@ Triggered when a batch request has completed.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.succeeded",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.succeeded",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -56,22 +56,22 @@ Triggered when a batch request has failed.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.failed",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
-    "message": "Model execution failed",
-    "internalCode": 5001,
-    "httpCode": 500
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.failed",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
+		"message": "Model execution failed",
+		"internalCode": 5001,
+		"httpCode": 500
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
index 5a30ffa88665135..c0f0508d1e6468e 100644
--- a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
@@ -6,39 +6,39 @@ Triggered when a build starts.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.started",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "running",
-    "buildOutcome": null,
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": null,
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.started",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "running",
+		"buildOutcome": null,
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": null,
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -50,39 +50,39 @@ Triggered when a build fails.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.failed",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "failed",
-    "buildOutcome": "failure",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:50:00.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.failed",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "failed",
+		"buildOutcome": "failure",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:50:00.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -94,39 +94,39 @@ Triggered when a build is canceled.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.canceled",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "canceled",
-    "buildOutcome": "canceled",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:49:30.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.canceled",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "canceled",
+		"buildOutcome": "canceled",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:49:30.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -138,38 +138,38 @@ Triggered when a build succeeds.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.succeeded",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "success",
-    "buildOutcome": "success",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:50:15.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.succeeded",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "success",
+		"buildOutcome": "success",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:50:15.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workflows-events.mdx b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
index 3df38e1c77de3c5..6c814481a6dbed4 100644
--- a/src/content/partials/queues/event-subscriptions/workflows-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
@@ -6,21 +6,21 @@ Triggered when an instance was created and is awaiting execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.queued",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.queued",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -32,21 +32,21 @@ Triggered when an instance starts or resumes execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.started",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.started",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -58,21 +58,21 @@ Triggered when an instance pauses execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.paused",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.paused",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -84,21 +84,21 @@ Triggered when an instance step throws an error.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.errored",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.errored",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -110,21 +110,21 @@ Triggered when an instance is manually terminated.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.terminated",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.terminated",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -136,20 +136,20 @@ Triggered when an instance finishes execution successfully.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.completed",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.completed",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/r2/custom-domain-steps.mdx b/src/content/partials/r2/custom-domain-steps.mdx
index f5c65596995f046..1b858090ebc584b 100644
--- a/src/content/partials/r2/custom-domain-steps.mdx
+++ b/src/content/partials/r2/custom-domain-steps.mdx
@@ -7,6 +7,7 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Select **Settings**.
 4. Under **Custom Domains**, select **Add**.
diff --git a/src/content/partials/r2/link-to-workers-r2-api.mdx b/src/content/partials/r2/link-to-workers-r2-api.mdx
index c18ac02fda8ef0a..22e4c599d0521ab 100644
--- a/src/content/partials/r2/link-to-workers-r2-api.mdx
+++ b/src/content/partials/r2/link-to-workers-r2-api.mdx
@@ -4,4 +4,4 @@
 
 ## Other resources
 
-For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
\ No newline at end of file
+For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
diff --git a/src/content/partials/r2/migrator-etag-caveat.mdx b/src/content/partials/r2/migrator-etag-caveat.mdx
index 5b40fec510b86ec..134d0b7745e8eea 100644
--- a/src/content/partials/r2/migrator-etag-caveat.mdx
+++ b/src/content/partials/r2/migrator-etag-caveat.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 While R2's ETag generation is compatible with S3's during the regular course of operations, ETags are not guaranteed to be equal when an object is migrated using {props.one}.
 {props.one} makes autonomous decisions about the operations it uses when migrating objects to optimize for performance and network usage. It may choose to migrate an object in multiple parts, which affects [ETag calculation](/r2/objects/upload-objects/#etags).
diff --git a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
index 3767632424c95a7..1bdda7b3e476265 100644
--- a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
@@ -1,12 +1,13 @@
 ---
 {}
-
 ---
+
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
+
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/create-your-own-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/create-your-own-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
\ No newline at end of file
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
diff --git a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
index c50d7c9cec90a22..f74bb9079e70dd4 100644
--- a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
@@ -1,12 +1,13 @@
 ---
 {}
-
 ---
+
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
+
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/default-meeting-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/default-meeting-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
\ No newline at end of file
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
index 59cb825253d7aa7..87e72e9cc2d11a8 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
@@ -1,21 +1,22 @@
 ---
 {}
-
 ---
+
 ```js
 await meeting.connectedMeetings.deleteMeetings([
-  "MEETING_ID_TO_CLOSE_1",
-  "MEETING_ID_TO_CLOSE_2",
+	"MEETING_ID_TO_CLOSE_1",
+	"MEETING_ID_TO_CLOSE_2",
 ]);
 ```
+
 This would also trigger `stateUpdate` event updating the list of breakout rooms & participants.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
-  console.log("stateUpdate", {meetings, parentMeeting});
+meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
+	console.log("stateUpdate", { meetings, parentMeeting });
 });
 
 // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
 console.log("Meetings List", meeting.connectedMeetings.meetings);
 console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
index f4af17e0a5883c0..7c577d42c671773 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
@@ -1,15 +1,20 @@
 ---
 {}
-
 ---
+
 ```js
 const breakoutRooms = await meeting.connectedMeetings.createMeetings([
-  { title: "Breakout Room 1" },
-  { title: "Breakout Room 2" },
-  { title: "Breakout Room 3" },
+	{ title: "Breakout Room 1" },
+	{ title: "Breakout Room 2" },
+	{ title: "Breakout Room 3" },
 ]);
 
-console.log("Created Breakout Rooms: ", breakoutRooms.map((room) => "Id:: " + room.id + " --- Title:: " + room.title).join("\n"));
+console.log(
+	"Created Breakout Rooms: ",
+	breakoutRooms
+		.map((room) => "Id:: " + room.id + " --- Title:: " + room.title)
+		.join("\n"),
+);
 ```
 
-`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
\ No newline at end of file
+`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
index dfde78c93ff676c..3047851f75d834f 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
@@ -1,10 +1,10 @@
 ---
 {}
-
 ---
 
 ```js
-const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo =
+	await meeting.connectedMeetings.getConnectedMeetings();
 ```
 
 `breakoutRoomsInfo` is an object containing the list of breakout rooms and their participants, along with details of the parent meeting.
@@ -14,11 +14,11 @@ This data can be used to display the list of breakout rooms & participants in th
 You can also listen to `stateUpdate` event to get the latest list of breakout rooms & participants, as they are updated in real-time.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
-  console.log("stateUpdate", {meetings, parentMeeting});
+meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
+	console.log("stateUpdate", { meetings, parentMeeting });
 
-  // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
-  console.log("Meetings List", meeting.connectedMeetings.meetings);
-  console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
+	// Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
+	console.log("Meetings List", meeting.connectedMeetings.meetings);
+	console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
 });
 ```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
index e10a85c8c58bf11..f77df15d7e5faa7 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
@@ -1,13 +1,16 @@
 ---
 {}
-
 ---
 
 ```js
 // Listen to changingMeeting event to show a custom UI to indicate that a meeting switch is happening
 meeting.connectedMeetings.on("changingMeeting", (meetingId) => {
-	console.log("Switching to breakout room or main meeting with id: " + meetingId);
-	console.log("Show a Custom UI to indicate that a meeting switch is happening");
+	console.log(
+		"Switching to breakout room or main meeting with id: " + meetingId,
+	);
+	console.log(
+		"Show a Custom UI to indicate that a meeting switch is happening",
+	);
 });
 
 // Listen to meetingChanged event to update the meeting object reference
@@ -15,4 +18,4 @@ meeting.connectedMeetings.on("meetingChanged", (newMeeting) => {
 	console.log("Switched to breakout room or main meeting");
 	console.log("Every action now should be performed on this meeting");
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
index be50df93029763f..fbd4d918d2faf36 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
@@ -1,20 +1,21 @@
 ---
 {}
-
 ---
+
 ```js
 // Retrieve list of breakout rooms & participants
-const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo =
+	await meeting.connectedMeetings.getConnectedMeetings();
 
 /*
-* You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
-* Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
-*/
+ * You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
+ * Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
+ */
 
 // Move participants to breakout rooms
 const response = await meeting.connectedMeetings.moveParticipants(
-  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-  ["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
+	"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+	"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+	["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
 );
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
index 1491da6d62c305b..66e13a506f735ec 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
@@ -1,11 +1,12 @@
 ---
 {}
-
 ---
+
 ```js
-const response = await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
-  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-  [{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
-);
-```
\ No newline at end of file
+const response =
+	await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
+		"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+		"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+		[{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
+	);
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
index 40805bd8dd7ae50..796eed925700f90 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
@@ -1,20 +1,24 @@
 ---
 {}
-
 ---
+
 ```js
 // Check if breakout rooms are supported
-const areBreakoutRoomsSupported = meeting.connectedMeetings.supportsConnectedMeetings;
+const areBreakoutRoomsSupported =
+	meeting.connectedMeetings.supportsConnectedMeetings;
 
 // Check if any breakout rooms are already created
 const areBreakoutRoomsActive = meeting.connectedMeetings.isActive;
 
 // Check if the current participant has permission to create breakout rooms
-const hasPermissionToCreateBreakoutRooms = meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
+const hasPermissionToCreateBreakoutRooms =
+	meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
 
 // Check if the current participant has permission to switch to parent meeting
-const hasPermissionToSwitchToParentMeeting = meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
+const hasPermissionToSwitchToParentMeeting =
+	meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
 
 // Check if the current participant has permission to switch to connected meeting
-const hasPermissionToSwitchToConnectedMeeting = meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
-```
\ No newline at end of file
+const hasPermissionToSwitchToConnectedMeeting =
+	meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
+```
diff --git a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
index 7ecbc3317f46d23..e3f7d0532664f23 100644
--- a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
+++ b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
@@ -1,417 +1,417 @@
 ---
 {}
-
 ---
+
 ```json
 {
-  "about_call": "About Call",
-  "screen": "Screen",
-  "camera": "Camera",
-  "leave": "Leave",
-  "dismiss": "Dismiss",
-  "logo": "Logo",
-  "page": "Page",
-  "more": "More",
-  "page.prev": "Previous Page",
-  "page.next": "Next Page",
-  "layout": "Layout",
-  "layout.auto": "Auto Layout",
-  "settings": "Settings",
-  "file": "File",
-  "image": "Image",
-  "connection": "Connection",
-  "leave_confirmation": "Are you sure you want to leave the call?",
-  "cancel": "Cancel",
-  "yes": "Yes",
-  "(you)": "(you)",
-  "you": "You",
-  "everyone": "Everyone",
-  "to": "To",
-  "mute": "Mute",
-  "kick": "Kick",
-  "pin": "Pin",
-  "pinned": "Pinned",
-  "accept": "Accept",
-  "unpin": "Unpin",
-  "pip_on": "Show PiP",
-  "pip_off": "Hide PiP",
-  "viewers": "Viewers",
-  "join": "Join",
-  "joined": "Joined",
-  "create": "Create",
-  "close": "Close",
-  "ask": "Ask",
-  "type": "Type",
-  "activate": "Activate",
-  "requests": "Requests",
-  "mic_off": "Mic Off",
-  "disable_mic": "Disable Mic",
-  "mic_on": "Mic On",
-  "enable_mic": "Enable Mic",
-  "audio": "Audio",
-  "test": "Test",
-  "minimize": "Hide Tile",
-  "maximize": "Show Tile",
-  "mute_all": "Mute all",
-  "mute_all.description": "Everyone else in the meeting will be muted.",
-  "mute_all.header": "Are you sure?",
-  "mute_all.allow_unmute": "Allow others to unmute",
-  "video_off": "Video Off",
-  "disable_video": "Disable Video",
-  "video_on": "Video On",
-  "enable_video": "Enable Video",
-  "video": "Video",
-  "offline": "You're offline",
-  "offline.description": "Please ensure that you are connected to the internet.",
-  "disconnected": "You haven't joined the meeting.",
-  "failed": "You've been disconnected",
-  "failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
-  "disconnected.description": "Please join the meeting in order to see and interact with other participants.",
-  "participants": "Participants",
-  "participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
-  "participants.empty_list": "It looks like nobody is here.",
-  "participants.no_pending_requests": "There are no pending requests.",
-  "participants.turn_off_video": "Turn off video",
-  "polls": "Polls",
-  "polls.by": "Poll by",
-  "polls.question": "Poll Question",
-  "polls.question.placeholder": "What is your poll for?",
-  "polls.answers": "Answers",
-  "polls.option": "Add an option.",
-  "polls.option.placeholder": "Enter an option",
-  "polls.results.anon": "Anonymous",
-  "polls.results.hide": "Hide results before voting",
-  "polls.create": "Create Poll",
-  "polls.cancel": "Cancel Poll Creation",
-  "polls.empty": "No polls available",
-  "polls.errors.question_required": "Question is required.",
-  "polls.errors.empty_option": "Empty options not allowed.",
-  "screenshare": "Screen Share",
-  "screenshare.min_preview": "Minimize Preview",
-  "screenshare.max_preview": "Expand Preview",
-  "screenshare.shared": "Your screen is being shared.",
-  "screenshare.start": "Share Screen",
-  "screenshare.stop": "Stop Sharing",
-  "screenshare.error.unknown": "An error occurred while starting screenshare.",
-  "screenshare.error.max_count": "Maximum screen share limit reached.",
-  "plugins": "Plugins",
-  "perm_denied": "Permission denied by browser.",
-  "perm_denied.audio": "Mic Permission denied by browser",
-  "perm_denied.video": "Camera Permission denied by browser",
-  "perm_denied.screenshare": "Screenshare Permission denied by browser",
-  "perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
-  "perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
-  "perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
-  "perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
-  "perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
-  "perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
-  "perm_sys_denied": "Permission denied by system",
-  "perm_sys_denied.audio": "Mic permission denied by system",
-  "perm_sys_denied.video": "Camera permission denied by system",
-  "perm_sys_denied.screenshare": "Screenshare permission denied by system",
-  "perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
-  "perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
-  "perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
-  "perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
-  "perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
-  "perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
-  "perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
-  "perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
-  "perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
-  "perm_could_not_start": "Could not capture device.",
-  "perm_could_not_start.audio": "Unable to start your Microphone",
-  "perm_could_not_start.video": "Unable to start your Camera",
-  "perm_could_not_start.screenshare": "Unable to start your Screenshare",
-  "perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
-  "perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
-  "perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
-  "full_screen": "Full Screen",
-  "full_screen.exit": "Exit Full Screen",
-  "waitlist.header_title": "Waiting",
-  "waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
-  "waitlist.deny_request": "Deny request",
-  "waitlist.accept_request": "Accept request",
-  "waitlist.accept_all": "Accept all",
-  "stage_request.header_title": "Join Stage Requests",
-  "stage_request.deny_request": "Deny request",
-  "stage_request.accept_request": "Accept request",
-  "stage_request.accept_all": "Accept all",
-  "stage_request.deny_all": "Deny all",
-  "stage_request.approval_pending": "Pending",
-  "stage_request.denied": "Denied",
-  "stage_request.request": "Join stage",
-  "stage_request.requested": "Requested",
-  "stage_request.cancel_request": "Cancel request",
-  "stage_request.leave_stage": "Leave stage",
-  "stage_request.request_tip": "Request to join the discussion",
-  "stage_request.leave_tip": "Leave the stage",
-  "stage_request.pending_tip": "Request pending",
-  "stage_request.denied_tip": "Rejected request",
-  "stage.empty_host": "The stage is empty",
-  "stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
-  "stage.empty_viewer": "There is no one on stage",
-  "stage.remove_from_stage": "Remove from stage",
-  "stage.invited_notification": "has been invited to join stage.",
-  "stage.add_to_stage": "Invite to stage",
-  "stage.join_title": "Join Stage",
-  "stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
-  "stage.join_cancel": "Cancel",
-  "stage.join_confirm": "Join",
-  "setup_screen.join_in_as": "Joining as",
-  "setup_screen.your_name": "Your name",
-  "stage.reconnecting": "Reconnecting...",
-  "recording.label": "REC",
-  "recording.indicator": "This meeting is being recorded.",
-  "recording.started": "This meeting is being recorded.",
-  "recording.stopped": "Recording for this meeting has been stopped.",
-  "recording.paused": "Recording for this meeting has been paused.",
-  "recording.error.start": "Error while starting recording.",
-  "recording.error.stop": "Error while stopping recording",
-  "recording.error.resume": "Error while resuming recording",
-  "recording.start": "Start Recording",
-  "recording.stop": "Stop Recording",
-  "recording.resume": "Resume Recording",
-  "recording.starting": "Starting",
-  "recording.stopping": "Stopping",
-  "recording.loading": "Loading",
-  "recording.idle": "Record",
-  "audio_playback": "Play Audio",
-  "audio_playback.title": "Allow Audio Playback",
-  "audio_playback.description": "In order to play audio properly on your device, click the button below.",
-  "breakout_rooms": "Breakout Rooms",
-  "breakout_rooms.room_config_header": "Create Breakout",
-  "breakout_rooms.join_breakout_header": "Join Breakout",
-  "breakout_rooms.empty": "Nobody here yet.",
-  "breakout_rooms.delete": "Delete Room",
-  "breakout_rooms.switch": "Switch",
-  "breakout_rooms.main_room": "Main Room",
-  "breakout_rooms.shuffle_participants": "Shuffle Participants",
-  "breakout_rooms.deselect": "Deselect",
-  "breakout_rooms.selected": "selected",
-  "breakout_rooms.num_of_rooms": "No. of Rooms",
-  "breakout_rooms.approx": "Approx.",
-  "breakout_rooms.participants_per_room": "participants/room",
-  "breakout_rooms.division_text": "when equally divided.",
-  "breakout_rooms.start_breakout": "Start Breakout",
-  "breakout_rooms.close_breakout": "Close Breakout",
-  "breakout_rooms.update_breakout": "Update Breakout",
-  "breakout_rooms.discard_changes": "Discard Changes",
-  "breakout_rooms.room": "Room",
-  "breakout_rooms.rooms": "Rooms",
-  "breakout_rooms.room_name": "Room Name",
-  "breakout_rooms.edit_room_name": "Edit Room Name",
-  "breakout_rooms.save_room_name": "Save Room Name",
-  "breakout_rooms.add_room": "Add",
-  "breakout_rooms.add_room_brief": "Add Room",
-  "breakout_rooms.select_all": "Select all",
-  "breakout_rooms.unassign_all": "Unassign all",
-  "breakout_rooms.assign": "Assign",
-  "breakout_rooms.assign_participants": "Assign Participants",
-  "breakout_rooms.none_assigned": "No participants assigned yet",
-  "breakout_rooms.drag_drop_participants": "Drag and drop participants",
-  "breakout_rooms.click_drop_participants": "Click here to assign",
-  "breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
-  "breakout_rooms.status.select_room": "Select a room to assign",
-  "breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
-  "breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
-  "breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
-  "breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
-  "breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
-  "breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
-  "breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
-  "breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
-  "breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
-  "breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
-  "breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
-  "breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
-  "breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
-  "breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
-  "breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
-  "breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
-  "breakout_rooms.all_assigned": "All participants have been assigned",
-  "breakout_rooms.empty_main_room": "No more participants in the main room.",
-  "breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
-  "breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
-  "ai": "AI",
-  "ai.meeting_ai": "MeetingAI",
-  "ai.home": "Home",
-  "ai.transcriptions": "Transcriptions",
-  "ai.personal": "Personal",
-  "ai.caption_view": "Caption View",
-  "ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
-  "ai.chat.summarise": "Hey AI, summarise this call",
-  "ai.chat.agenda": "Hey AI, what is today's agenda?",
-  "search": "Search",
-  "search.could_not_find": "Couldn't find a participant with the specified name or ID.",
-  "search.empty": "It looks like nobody is here.",
-  "end": "End Meeting",
-  "end.all": "End meeting for all",
-  "ended": "The meeting ended.",
-  "ended.rejected": "Your request to join the meeting was denied.",
-  "ended.left": "You left the meeting.",
-  "ended.kicked": "You were removed from the meeting.",
-  "ended.disconnected": "The call ended because the connection was lost.",
-  "ended.network": "Please check your internet connection and try again.",
-  "ended.unauthorized": "You are not authorized to join this meeting.",
-  "network": "Network",
-  "network.reconnecting": "Connection lost. Trying to reconnect.",
-  "network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
-  "network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
-  "network.leaving": "Automatically leaving the meeting in 10 seconds.",
-  "network.restored": "Connection restored",
-  "network.delay": "Taking too long to reconnect.",
-  "network.lost": "Connection lost",
-  "network.lost_extended": "Connection lost. Please check your network connection.",
-  "livestream": "Livestream",
-  "livestream.indicator": "This meeting is being livestreamed.",
-  "livestream.skip": "Skip to Live",
-  "livestream.idle": "Waiting to go live.",
-  "livestream.starting": "Livestream is starting...",
-  "livestream.stopping": "Livestream is stopping...",
-  "livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
-  "livestream.error.not_supported": "Player not supported.",
-  "livestream.error.not_found": "Playback URL not found.",
-  "livestream.error.unknown": "An unknown error occurred.",
-  "livestream.error.sync": "Could not sync livestream please try again later.",
-  "livestream.error.start": "Error while starting livestream.",
-  "livestream.error.stop": "Error while stopping livestream.",
-  "livestream.go_live": "Go Live",
-  "livestream.end_live": "End Live",
-  "livestream.error": "Error",
-  "cta.help": "Need help on how to do this?",
-  "cta.continue": "Ignore",
-  "cta.reload": "Reload",
-  "cta.confirmation": "Are you sure?",
-  "cta.system_settings": "Open Settings",
-  "remote_access.empty": "There are no remote requests, yet.",
-  "remote_access.requests": "The following people have requested remote control to your screen share.",
-  "remote_access.allow": "Please select whom you want to give access to.",
-  "remote_access.grant": "Grant access",
-  "remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
-  "chat": "Chat",
-  "chat.new": "New",
-  "chat.max_limit_warning": "Max Character Limit",
-  "chat.rate_limit_error": "Please wait before you can send another message",
-  "chat.new_channel": "Create new channel",
-  "chat.channel_name": "Enter channel name",
-  "chat.member_name": "Enter member name",
-  "chat.add_members": "Add members",
-  "chat.delete_msg": "Delete",
-  "chat.edit_msg": "Edit",
-  "chat.send_msg": "Send message",
-  "chat.send_attachment": "Drop files/images to send",
-  "chat.send_img": "Send an image",
-  "chat.send_file": "Send a file",
-  "chat.send_emoji": "Send an emoji",
-  "chat.update_msg": "Update message",
-  "chat.channel_members": "Channel Members",
-  "chat.img.loading": "Loading image",
-  "chat.error.img_not_found": "Image not found",
-  "chat.error.empty_results": "Couldn't find a member with the specified name.",
-  "chat.img.shared_by": "Shared by",
-  "chat.reply": "Reply",
-  "chat.message_placeholder": "Message..",
-  "chat.click_to_send": "Click to send as message",
-  "chat.search_msgs": "Search messages",
-  "chat.search_conversations": "Search conversations",
-  "chat.start_conversation": "Start a conversation..",
-  "chat.empty_search": "No messages found",
-  "chat.empty_channel": "Send a message to get started",
-  "chat.cancel_upload": "Cancel upload",
-  "chat.view_chats": "View chats",
-  "chat.everyone": "everyone",
-  "chat.pinned_msgs": "Pinned messages",
-  "chat.toggle_pinned_msgs": "Toggle pinned messages",
-  "date.today": "Today",
-  "date.yesterday": "Yesterday",
-  "date.sunday": "Sunday",
-  "date.monday": "Monday",
-  "date.tuesday": "Tuesday",
-  "date.wednesday": "Wednesday",
-  "date.thursday": "Thursday",
-  "date.friday": "Friday",
-  "date.saturday": "Saturday",
-  "list.empty": "No items found",
-  "grid.listening": "Listening",
-  "transcript.off": "Turn off Transcripts",
-  "transcript.on": "Turn on Transcripts",
-  "settings.notification_sound": "Notification sound",
-  "settings.microphone_input": "Microphone",
-  "settings.speaker_output": "Speaker",
-  "settings.mirror_video": "Mirror my Video",
-  "settings.camera_off": "Camera is off",
-  "dialog.close": "Close dialog",
-  "notifications.joined": "just joined",
-  "notifications.left": "left",
-  "notifications.requesting_to_join_meeting": "is requesting to join the meeting",
-  "notifications.requested_to_join_stage": "has requested to join stage",
-  "notifications.joined_stage": "has joined stage",
-  "notifications.request_to_join_accepted": "Request to join accepted",
-  "notifications.request_to_join_rejected": "Request to join rejected",
-  "notifications.accept": "Accept",
-  "notifications.new_poll_created_by": "New poll created by",
-  "notifications.connected_to": "Connected to",
-  "notifications.plugin_switched_to": "Plugin switched to",
-  "notifications.remote_control_requested": "has requested for remote control",
-  "notifications.remote_control_request_sent": "Sent remote control request to",
-  "notifications.remote_control_request_accepted": "has granted remote control",
-  "notifications.remote_control_granted": "Granted remote control to",
-  "notifications.remote_control_terminated": "Existing remote control has been terminated",
-  "debugger.troubleshooting.label": "Troubleshooting",
-  "debugger.quality.good": "Good",
-  "debugger.quality.average": "Average",
-  "debugger.quality.poor": "Poor",
-  "debugger.stats.bitrate.label": "Bitrate",
-  "debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
-  "debugger.stats.packet_loss.label": "Packet Loss",
-  "debugger.stats.packet_loss.description": "Amount of data lost during transfer",
-  "debugger.stats.jitter.label": "Jitter",
-  "debugger.stats.jitter.description": "Variance or fluctuation in latency",
-  "debugger.stats.cpu_limitations.label": "CPU Limitations",
-  "debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
-  "debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
-  "debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
-  "debugger.audio.label": "Audio",
-  "debugger.audio.troubleshooting.label": "Audio Troubleshooting",
-  "debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.audio.messages.enable_media": "Please enable mic to see the report.",
-  "debugger.audio.sections.network_media": "Network & Media",
-  "debugger.video.label": "Video",
-  "debugger.video.troubleshooting.label": "Video Troubleshooting",
-  "debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.video.messages.enable_media": "Please enable camera to see the report.",
-  "debugger.video.sections.network_media": "Network & Media",
-  "debugger.screenshare.label": "Screenshare",
-  "debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
-  "debugger.screenshare.sections.network_media": "Network & Media",
-  "debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
-  "debugger.system.label": "System",
-  "debugger.system.troubleshooting.label": "System Troubleshooting",
-  "debugger.system.sections.battery": "Battery",
-  "debugger.system.battery.level.label": "Battery Level",
-  "debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
-  "debugger.system.battery.charging.label": "Battery Charging Status",
-  "debugger.system.battery.charging.description": "A device running on power performs optimally.",
-  "debugger.system.battery.charging.is_charging": "Charging",
-  "debugger.system.battery.charging.is_not_charging": "Not charging"
+	"about_call": "About Call",
+	"screen": "Screen",
+	"camera": "Camera",
+	"leave": "Leave",
+	"dismiss": "Dismiss",
+	"logo": "Logo",
+	"page": "Page",
+	"more": "More",
+	"page.prev": "Previous Page",
+	"page.next": "Next Page",
+	"layout": "Layout",
+	"layout.auto": "Auto Layout",
+	"settings": "Settings",
+	"file": "File",
+	"image": "Image",
+	"connection": "Connection",
+	"leave_confirmation": "Are you sure you want to leave the call?",
+	"cancel": "Cancel",
+	"yes": "Yes",
+	"(you)": "(you)",
+	"you": "You",
+	"everyone": "Everyone",
+	"to": "To",
+	"mute": "Mute",
+	"kick": "Kick",
+	"pin": "Pin",
+	"pinned": "Pinned",
+	"accept": "Accept",
+	"unpin": "Unpin",
+	"pip_on": "Show PiP",
+	"pip_off": "Hide PiP",
+	"viewers": "Viewers",
+	"join": "Join",
+	"joined": "Joined",
+	"create": "Create",
+	"close": "Close",
+	"ask": "Ask",
+	"type": "Type",
+	"activate": "Activate",
+	"requests": "Requests",
+	"mic_off": "Mic Off",
+	"disable_mic": "Disable Mic",
+	"mic_on": "Mic On",
+	"enable_mic": "Enable Mic",
+	"audio": "Audio",
+	"test": "Test",
+	"minimize": "Hide Tile",
+	"maximize": "Show Tile",
+	"mute_all": "Mute all",
+	"mute_all.description": "Everyone else in the meeting will be muted.",
+	"mute_all.header": "Are you sure?",
+	"mute_all.allow_unmute": "Allow others to unmute",
+	"video_off": "Video Off",
+	"disable_video": "Disable Video",
+	"video_on": "Video On",
+	"enable_video": "Enable Video",
+	"video": "Video",
+	"offline": "You're offline",
+	"offline.description": "Please ensure that you are connected to the internet.",
+	"disconnected": "You haven't joined the meeting.",
+	"failed": "You've been disconnected",
+	"failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
+	"disconnected.description": "Please join the meeting in order to see and interact with other participants.",
+	"participants": "Participants",
+	"participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
+	"participants.empty_list": "It looks like nobody is here.",
+	"participants.no_pending_requests": "There are no pending requests.",
+	"participants.turn_off_video": "Turn off video",
+	"polls": "Polls",
+	"polls.by": "Poll by",
+	"polls.question": "Poll Question",
+	"polls.question.placeholder": "What is your poll for?",
+	"polls.answers": "Answers",
+	"polls.option": "Add an option.",
+	"polls.option.placeholder": "Enter an option",
+	"polls.results.anon": "Anonymous",
+	"polls.results.hide": "Hide results before voting",
+	"polls.create": "Create Poll",
+	"polls.cancel": "Cancel Poll Creation",
+	"polls.empty": "No polls available",
+	"polls.errors.question_required": "Question is required.",
+	"polls.errors.empty_option": "Empty options not allowed.",
+	"screenshare": "Screen Share",
+	"screenshare.min_preview": "Minimize Preview",
+	"screenshare.max_preview": "Expand Preview",
+	"screenshare.shared": "Your screen is being shared.",
+	"screenshare.start": "Share Screen",
+	"screenshare.stop": "Stop Sharing",
+	"screenshare.error.unknown": "An error occurred while starting screenshare.",
+	"screenshare.error.max_count": "Maximum screen share limit reached.",
+	"plugins": "Plugins",
+	"perm_denied": "Permission denied by browser.",
+	"perm_denied.audio": "Mic Permission denied by browser",
+	"perm_denied.video": "Camera Permission denied by browser",
+	"perm_denied.screenshare": "Screenshare Permission denied by browser",
+	"perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
+	"perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
+	"perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
+	"perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
+	"perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
+	"perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
+	"perm_sys_denied": "Permission denied by system",
+	"perm_sys_denied.audio": "Mic permission denied by system",
+	"perm_sys_denied.video": "Camera permission denied by system",
+	"perm_sys_denied.screenshare": "Screenshare permission denied by system",
+	"perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
+	"perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
+	"perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
+	"perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
+	"perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
+	"perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
+	"perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
+	"perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
+	"perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
+	"perm_could_not_start": "Could not capture device.",
+	"perm_could_not_start.audio": "Unable to start your Microphone",
+	"perm_could_not_start.video": "Unable to start your Camera",
+	"perm_could_not_start.screenshare": "Unable to start your Screenshare",
+	"perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
+	"perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
+	"perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
+	"full_screen": "Full Screen",
+	"full_screen.exit": "Exit Full Screen",
+	"waitlist.header_title": "Waiting",
+	"waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
+	"waitlist.deny_request": "Deny request",
+	"waitlist.accept_request": "Accept request",
+	"waitlist.accept_all": "Accept all",
+	"stage_request.header_title": "Join Stage Requests",
+	"stage_request.deny_request": "Deny request",
+	"stage_request.accept_request": "Accept request",
+	"stage_request.accept_all": "Accept all",
+	"stage_request.deny_all": "Deny all",
+	"stage_request.approval_pending": "Pending",
+	"stage_request.denied": "Denied",
+	"stage_request.request": "Join stage",
+	"stage_request.requested": "Requested",
+	"stage_request.cancel_request": "Cancel request",
+	"stage_request.leave_stage": "Leave stage",
+	"stage_request.request_tip": "Request to join the discussion",
+	"stage_request.leave_tip": "Leave the stage",
+	"stage_request.pending_tip": "Request pending",
+	"stage_request.denied_tip": "Rejected request",
+	"stage.empty_host": "The stage is empty",
+	"stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
+	"stage.empty_viewer": "There is no one on stage",
+	"stage.remove_from_stage": "Remove from stage",
+	"stage.invited_notification": "has been invited to join stage.",
+	"stage.add_to_stage": "Invite to stage",
+	"stage.join_title": "Join Stage",
+	"stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
+	"stage.join_cancel": "Cancel",
+	"stage.join_confirm": "Join",
+	"setup_screen.join_in_as": "Joining as",
+	"setup_screen.your_name": "Your name",
+	"stage.reconnecting": "Reconnecting...",
+	"recording.label": "REC",
+	"recording.indicator": "This meeting is being recorded.",
+	"recording.started": "This meeting is being recorded.",
+	"recording.stopped": "Recording for this meeting has been stopped.",
+	"recording.paused": "Recording for this meeting has been paused.",
+	"recording.error.start": "Error while starting recording.",
+	"recording.error.stop": "Error while stopping recording",
+	"recording.error.resume": "Error while resuming recording",
+	"recording.start": "Start Recording",
+	"recording.stop": "Stop Recording",
+	"recording.resume": "Resume Recording",
+	"recording.starting": "Starting",
+	"recording.stopping": "Stopping",
+	"recording.loading": "Loading",
+	"recording.idle": "Record",
+	"audio_playback": "Play Audio",
+	"audio_playback.title": "Allow Audio Playback",
+	"audio_playback.description": "In order to play audio properly on your device, click the button below.",
+	"breakout_rooms": "Breakout Rooms",
+	"breakout_rooms.room_config_header": "Create Breakout",
+	"breakout_rooms.join_breakout_header": "Join Breakout",
+	"breakout_rooms.empty": "Nobody here yet.",
+	"breakout_rooms.delete": "Delete Room",
+	"breakout_rooms.switch": "Switch",
+	"breakout_rooms.main_room": "Main Room",
+	"breakout_rooms.shuffle_participants": "Shuffle Participants",
+	"breakout_rooms.deselect": "Deselect",
+	"breakout_rooms.selected": "selected",
+	"breakout_rooms.num_of_rooms": "No. of Rooms",
+	"breakout_rooms.approx": "Approx.",
+	"breakout_rooms.participants_per_room": "participants/room",
+	"breakout_rooms.division_text": "when equally divided.",
+	"breakout_rooms.start_breakout": "Start Breakout",
+	"breakout_rooms.close_breakout": "Close Breakout",
+	"breakout_rooms.update_breakout": "Update Breakout",
+	"breakout_rooms.discard_changes": "Discard Changes",
+	"breakout_rooms.room": "Room",
+	"breakout_rooms.rooms": "Rooms",
+	"breakout_rooms.room_name": "Room Name",
+	"breakout_rooms.edit_room_name": "Edit Room Name",
+	"breakout_rooms.save_room_name": "Save Room Name",
+	"breakout_rooms.add_room": "Add",
+	"breakout_rooms.add_room_brief": "Add Room",
+	"breakout_rooms.select_all": "Select all",
+	"breakout_rooms.unassign_all": "Unassign all",
+	"breakout_rooms.assign": "Assign",
+	"breakout_rooms.assign_participants": "Assign Participants",
+	"breakout_rooms.none_assigned": "No participants assigned yet",
+	"breakout_rooms.drag_drop_participants": "Drag and drop participants",
+	"breakout_rooms.click_drop_participants": "Click here to assign",
+	"breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
+	"breakout_rooms.status.select_room": "Select a room to assign",
+	"breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
+	"breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
+	"breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
+	"breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
+	"breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
+	"breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
+	"breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
+	"breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
+	"breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
+	"breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
+	"breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
+	"breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
+	"breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
+	"breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
+	"breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
+	"breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
+	"breakout_rooms.all_assigned": "All participants have been assigned",
+	"breakout_rooms.empty_main_room": "No more participants in the main room.",
+	"breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
+	"breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
+	"ai": "AI",
+	"ai.meeting_ai": "MeetingAI",
+	"ai.home": "Home",
+	"ai.transcriptions": "Transcriptions",
+	"ai.personal": "Personal",
+	"ai.caption_view": "Caption View",
+	"ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
+	"ai.chat.summarise": "Hey AI, summarise this call",
+	"ai.chat.agenda": "Hey AI, what is today's agenda?",
+	"search": "Search",
+	"search.could_not_find": "Couldn't find a participant with the specified name or ID.",
+	"search.empty": "It looks like nobody is here.",
+	"end": "End Meeting",
+	"end.all": "End meeting for all",
+	"ended": "The meeting ended.",
+	"ended.rejected": "Your request to join the meeting was denied.",
+	"ended.left": "You left the meeting.",
+	"ended.kicked": "You were removed from the meeting.",
+	"ended.disconnected": "The call ended because the connection was lost.",
+	"ended.network": "Please check your internet connection and try again.",
+	"ended.unauthorized": "You are not authorized to join this meeting.",
+	"network": "Network",
+	"network.reconnecting": "Connection lost. Trying to reconnect.",
+	"network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
+	"network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
+	"network.leaving": "Automatically leaving the meeting in 10 seconds.",
+	"network.restored": "Connection restored",
+	"network.delay": "Taking too long to reconnect.",
+	"network.lost": "Connection lost",
+	"network.lost_extended": "Connection lost. Please check your network connection.",
+	"livestream": "Livestream",
+	"livestream.indicator": "This meeting is being livestreamed.",
+	"livestream.skip": "Skip to Live",
+	"livestream.idle": "Waiting to go live.",
+	"livestream.starting": "Livestream is starting...",
+	"livestream.stopping": "Livestream is stopping...",
+	"livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
+	"livestream.error.not_supported": "Player not supported.",
+	"livestream.error.not_found": "Playback URL not found.",
+	"livestream.error.unknown": "An unknown error occurred.",
+	"livestream.error.sync": "Could not sync livestream please try again later.",
+	"livestream.error.start": "Error while starting livestream.",
+	"livestream.error.stop": "Error while stopping livestream.",
+	"livestream.go_live": "Go Live",
+	"livestream.end_live": "End Live",
+	"livestream.error": "Error",
+	"cta.help": "Need help on how to do this?",
+	"cta.continue": "Ignore",
+	"cta.reload": "Reload",
+	"cta.confirmation": "Are you sure?",
+	"cta.system_settings": "Open Settings",
+	"remote_access.empty": "There are no remote requests, yet.",
+	"remote_access.requests": "The following people have requested remote control to your screen share.",
+	"remote_access.allow": "Please select whom you want to give access to.",
+	"remote_access.grant": "Grant access",
+	"remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
+	"chat": "Chat",
+	"chat.new": "New",
+	"chat.max_limit_warning": "Max Character Limit",
+	"chat.rate_limit_error": "Please wait before you can send another message",
+	"chat.new_channel": "Create new channel",
+	"chat.channel_name": "Enter channel name",
+	"chat.member_name": "Enter member name",
+	"chat.add_members": "Add members",
+	"chat.delete_msg": "Delete",
+	"chat.edit_msg": "Edit",
+	"chat.send_msg": "Send message",
+	"chat.send_attachment": "Drop files/images to send",
+	"chat.send_img": "Send an image",
+	"chat.send_file": "Send a file",
+	"chat.send_emoji": "Send an emoji",
+	"chat.update_msg": "Update message",
+	"chat.channel_members": "Channel Members",
+	"chat.img.loading": "Loading image",
+	"chat.error.img_not_found": "Image not found",
+	"chat.error.empty_results": "Couldn't find a member with the specified name.",
+	"chat.img.shared_by": "Shared by",
+	"chat.reply": "Reply",
+	"chat.message_placeholder": "Message..",
+	"chat.click_to_send": "Click to send as message",
+	"chat.search_msgs": "Search messages",
+	"chat.search_conversations": "Search conversations",
+	"chat.start_conversation": "Start a conversation..",
+	"chat.empty_search": "No messages found",
+	"chat.empty_channel": "Send a message to get started",
+	"chat.cancel_upload": "Cancel upload",
+	"chat.view_chats": "View chats",
+	"chat.everyone": "everyone",
+	"chat.pinned_msgs": "Pinned messages",
+	"chat.toggle_pinned_msgs": "Toggle pinned messages",
+	"date.today": "Today",
+	"date.yesterday": "Yesterday",
+	"date.sunday": "Sunday",
+	"date.monday": "Monday",
+	"date.tuesday": "Tuesday",
+	"date.wednesday": "Wednesday",
+	"date.thursday": "Thursday",
+	"date.friday": "Friday",
+	"date.saturday": "Saturday",
+	"list.empty": "No items found",
+	"grid.listening": "Listening",
+	"transcript.off": "Turn off Transcripts",
+	"transcript.on": "Turn on Transcripts",
+	"settings.notification_sound": "Notification sound",
+	"settings.microphone_input": "Microphone",
+	"settings.speaker_output": "Speaker",
+	"settings.mirror_video": "Mirror my Video",
+	"settings.camera_off": "Camera is off",
+	"dialog.close": "Close dialog",
+	"notifications.joined": "just joined",
+	"notifications.left": "left",
+	"notifications.requesting_to_join_meeting": "is requesting to join the meeting",
+	"notifications.requested_to_join_stage": "has requested to join stage",
+	"notifications.joined_stage": "has joined stage",
+	"notifications.request_to_join_accepted": "Request to join accepted",
+	"notifications.request_to_join_rejected": "Request to join rejected",
+	"notifications.accept": "Accept",
+	"notifications.new_poll_created_by": "New poll created by",
+	"notifications.connected_to": "Connected to",
+	"notifications.plugin_switched_to": "Plugin switched to",
+	"notifications.remote_control_requested": "has requested for remote control",
+	"notifications.remote_control_request_sent": "Sent remote control request to",
+	"notifications.remote_control_request_accepted": "has granted remote control",
+	"notifications.remote_control_granted": "Granted remote control to",
+	"notifications.remote_control_terminated": "Existing remote control has been terminated",
+	"debugger.troubleshooting.label": "Troubleshooting",
+	"debugger.quality.good": "Good",
+	"debugger.quality.average": "Average",
+	"debugger.quality.poor": "Poor",
+	"debugger.stats.bitrate.label": "Bitrate",
+	"debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
+	"debugger.stats.packet_loss.label": "Packet Loss",
+	"debugger.stats.packet_loss.description": "Amount of data lost during transfer",
+	"debugger.stats.jitter.label": "Jitter",
+	"debugger.stats.jitter.description": "Variance or fluctuation in latency",
+	"debugger.stats.cpu_limitations.label": "CPU Limitations",
+	"debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
+	"debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
+	"debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
+	"debugger.audio.label": "Audio",
+	"debugger.audio.troubleshooting.label": "Audio Troubleshooting",
+	"debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.audio.messages.enable_media": "Please enable mic to see the report.",
+	"debugger.audio.sections.network_media": "Network & Media",
+	"debugger.video.label": "Video",
+	"debugger.video.troubleshooting.label": "Video Troubleshooting",
+	"debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.video.messages.enable_media": "Please enable camera to see the report.",
+	"debugger.video.sections.network_media": "Network & Media",
+	"debugger.screenshare.label": "Screenshare",
+	"debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
+	"debugger.screenshare.sections.network_media": "Network & Media",
+	"debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
+	"debugger.system.label": "System",
+	"debugger.system.troubleshooting.label": "System Troubleshooting",
+	"debugger.system.sections.battery": "Battery",
+	"debugger.system.battery.level.label": "Battery Level",
+	"debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
+	"debugger.system.battery.charging.label": "Battery Charging Status",
+	"debugger.system.battery.charging.description": "A device running on power performs optimally.",
+	"debugger.system.battery.charging.is_charging": "Charging",
+	"debugger.system.battery.charging.is_not_charging": "Not charging"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/reference-architecture/description-of-design-guides.mdx b/src/content/partials/reference-architecture/description-of-design-guides.mdx
index ebf33568632639f..cedea82e2560037 100644
--- a/src/content/partials/reference-architecture/description-of-design-guides.mdx
+++ b/src/content/partials/reference-architecture/description-of-design-guides.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Design guides take your knowledge from a reference architecture and walk through the conceptual decisions and directions you should take to implement a specific solution. They do not replace our product documentation, but instead provide guidance on the decisions you should make given a certain solution you are trying to deploy.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
index 6a2206f3b86ff23..8756e82c2b9cbe2 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
index 6a2206f3b86ff23..8756e82c2b9cbe2 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
index a5d6d6bb9b81e53..24ca75fa6ed1a30 100644
--- a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
+++ b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-* What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
+- What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
diff --git a/src/content/partials/registrar/email-verification.mdx b/src/content/partials/registrar/email-verification.mdx
index 4dd91c56e47bc07..2b72b0b433a4f42 100644
--- a/src/content/partials/registrar/email-verification.mdx
+++ b/src/content/partials/registrar/email-verification.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If you have an [unverified account email address](/fundamentals/user-profiles/verify-email-address/), you will not be able to transfer or register domains. Verify your account email address before proceeding.
 
-
 :::
diff --git a/src/content/partials/registrar/enable-dnssec.mdx b/src/content/partials/registrar/enable-dnssec.mdx
index 237935a506b128b..83ac4c6b7219453 100644
--- a/src/content/partials/registrar/enable-dnssec.mdx
+++ b/src/content/partials/registrar/enable-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ Cloudflare Registrar offers one-click DNSSEC activation for free to all customer
 
 1. In Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain that you want to activate DNSSEC and select **Manage**.
 3. Select **Configuration** > **Enable DNSSEC**. If DNSSEC was previously activated, select **Disable DNSSEC** to disable it.
diff --git a/src/content/partials/registrar/icann-unverified-email.mdx b/src/content/partials/registrar/icann-unverified-email.mdx
index 665b423fb7c437c..296e965a96cf9c5 100644
--- a/src/content/partials/registrar/icann-unverified-email.mdx
+++ b/src/content/partials/registrar/icann-unverified-email.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 If you purchased your domain through Cloudflare Registrar, [ICANN](https://www.icann.org/) requires you to verify your registrant email address. If your email is unverified or if the verification has expired, ICANN places a hold on the domain and replaces your nameservers with parking server nameservers (NS). Once you complete verification, your nameservers are automatically restored.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/registrar/requirements.mdx b/src/content/partials/registrar/requirements.mdx
index 23d333ecb86aba7..1178776bde7f938 100644
--- a/src/content/partials/registrar/requirements.mdx
+++ b/src/content/partials/registrar/requirements.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Requirements
diff --git a/src/content/partials/registrar/restrictions.mdx b/src/content/partials/registrar/restrictions.mdx
index 57a9452a3ab5a69..b34956aeb7039bd 100644
--- a/src/content/partials/registrar/restrictions.mdx
+++ b/src/content/partials/registrar/restrictions.mdx
@@ -1,20 +1,20 @@
 ---
 {}
-
 ---
 
 ## Restrictions
 
 To transfer your domain, it must meet the following requirements:
 
-* ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
-* Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
+- ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
+- Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
   :::caution
 
   The transfer of an expired domain may result in an additional year NOT being added during the transfer.
   :::
-* Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
-* Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
-* Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
+
+- Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
+- Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
+- Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
 
 If your domain is listed as available for transfer in the Cloudflare dashboard, these restrictions have already been checked.
diff --git a/src/content/partials/registrar/verify-dnssec.mdx b/src/content/partials/registrar/verify-dnssec.mdx
index cc9f05e4a7120d0..f5182b94b5a1559 100644
--- a/src/content/partials/registrar/verify-dnssec.mdx
+++ b/src/content/partials/registrar/verify-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When DNSSEC has been successfully applied to your domain, Cloudflare shows you a confirmed status. Go to [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) in the Cloudflare dashboard, and scroll down to **DNSSEC**.
diff --git a/src/content/partials/rules/configuration-rule-link-to-examples.mdx b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
index 1ff0517f5389e04..037eaeef781404b 100644
--- a/src/content/partials/rules/configuration-rule-link-to-examples.mdx
+++ b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Refer to [Create a configuration rule via API](/rules/configuration-rules/create-api/#example-requests) for complete API examples.
diff --git a/src/content/partials/rules/configuration-rule-promotion.mdx b/src/content/partials/rules/configuration-rule-promotion.mdx
index 3ae68e3cf154e68..6519187465e5160 100644
--- a/src/content/partials/rules/configuration-rule-promotion.mdx
+++ b/src/content/partials/rules/configuration-rule-promotion.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 To use this feature on specific hostnames - instead of across your entire zone - use a [configuration rule](/rules/configuration-rules/).
 
-
 :::
diff --git a/src/content/partials/rules/error-pages-list.mdx b/src/content/partials/rules/error-pages-list.mdx
index e3245503608f21c..7ab22e20464a19f 100644
--- a/src/content/partials/rules/error-pages-list.mdx
+++ b/src/content/partials/rules/error-pages-list.mdx
@@ -11,4 +11,3 @@ import { Details } from "~/components";
 - 1000 class errors
 - Managed challenge / I'm Under Attack Mode
 - Rate limiting block
-
diff --git a/src/content/partials/rules/page-rules-migration.mdx b/src/content/partials/rules/page-rules-migration.mdx
index 49184a9b7fddd3a..88530db810e2ac1 100644
--- a/src/content/partials/rules/page-rules-migration.mdx
+++ b/src/content/partials/rules/page-rules-migration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/rules/rules-creation-workflow.mdx b/src/content/partials/rules/rules-creation-workflow.mdx
index c5c10393f7fe7b5..457e137376878ed 100644
--- a/src/content/partials/rules/rules-creation-workflow.mdx
+++ b/src/content/partials/rules/rules-creation-workflow.mdx
@@ -11,7 +11,6 @@ Follow this workflow to create {props.ruleName} for a given zone via API:
 1. Use the [List zone rulesets](/api/resources/rulesets/methods/list/) operation to check if there is already a ruleset for the <code>{props.phaseName}</code> phase at the zone level.
 
 2. If the phase ruleset does not exist, create it using the [Create a zone ruleset](/api/resources/rulesets/methods/create/) operation. In the new ruleset properties, set the following values:
-
    - **kind**: `zone`
    - **phase**: <code>{props.phaseName}</code>
 
diff --git a/src/content/partials/rules/rules-templates.mdx b/src/content/partials/rules/rules-templates.mdx
index 15707947ed21c52..327ddbb7e03e964 100644
--- a/src/content/partials/rules/rules-templates.mdx
+++ b/src/content/partials/rules/rules-templates.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
-Cloudflare provides you with rules templates for common use cases. 
+Cloudflare provides you with rules templates for common use cases.
 
 1. In the Cloudflare dashboard, go to the Rules **Overview** page.
 
    <DashButton url="/?to=/:account/:zone/rules/overview" />
 
-2. Select **Templates**, and then select one of the available templates. 
+2. Select **Templates**, and then select one of the available templates.
 
 You can also refer to the [Examples gallery](/rules/examples/) in the developer docs.
diff --git a/src/content/partials/rules/terraform-additional-resources.mdx b/src/content/partials/rules/terraform-additional-resources.mdx
index d12cb288e5d11d2..38d3d167a3b1839 100644
--- a/src/content/partials/rules/terraform-additional-resources.mdx
+++ b/src/content/partials/rules/terraform-additional-resources.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 ## Additional resources
 
 For additional guidance on using Terraform with Cloudflare, refer to the following resources:
 
-* [Terraform documentation](/terraform/)
-* [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
+- [Terraform documentation](/terraform/)
+- [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
diff --git a/src/content/partials/rules/transform/header-valid-names.mdx b/src/content/partials/rules/transform/header-valid-names.mdx
index f286e2ab339e6cc..0e72fbaa66dee00 100644
--- a/src/content/partials/rules/transform/header-valid-names.mdx
+++ b/src/content/partials/rules/transform/header-valid-names.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
-* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-* The following special characters: `-` and `_`
+- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+- The following special characters: `-` and `_`
diff --git a/src/content/partials/rules/transform/header-valid-values.mdx b/src/content/partials/rules/transform/header-valid-values.mdx
index 540ff31d7a51c22..9daf4a9a76a4e18 100644
--- a/src/content/partials/rules/transform/header-valid-values.mdx
+++ b/src/content/partials/rules/transform/header-valid-values.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
-* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-* The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
+- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+- The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
diff --git a/src/content/partials/ruleset-engine/max-expression-length.mdx b/src/content/partials/ruleset-engine/max-expression-length.mdx
index e8881c097a0cb0c..59d99f613473f9c 100644
--- a/src/content/partials/ruleset-engine/max-expression-length.mdx
+++ b/src/content/partials/ruleset-engine/max-expression-length.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The maximum length of a rule expression is 4,096 characters.
diff --git a/src/content/partials/ruleset-engine/rule-position-values.mdx b/src/content/partials/ruleset-engine/rule-position-values.mdx
index aed905dee8894cd..c83ff42bfcf11a3 100644
--- a/src/content/partials/ruleset-engine/rule-position-values.mdx
+++ b/src/content/partials/ruleset-engine/rule-position-values.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
-* `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
+- `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
 
-* `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
+- `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
 
-* `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
+- `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
 
 :::caution[Important]
 
diff --git a/src/content/partials/security-center/brand-protection-alerts.mdx b/src/content/partials/security-center/brand-protection-alerts.mdx
index 71e7f9d688bd180..30a6ad5713d7bad 100644
--- a/src/content/partials/security-center/brand-protection-alerts.mdx
+++ b/src/content/partials/security-center/brand-protection-alerts.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Brand Protection integrates with Cloudflare's ANS (Alerts Notification Service) to provide configurable alerts when new domains are detected.
diff --git a/src/content/partials/security-center/brand-protection-definition.mdx b/src/content/partials/security-center/brand-protection-definition.mdx
index be50db0bf8b3b06..6707a12034c0016 100644
--- a/src/content/partials/security-center/brand-protection-definition.mdx
+++ b/src/content/partials/security-center/brand-protection-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Brand Protection allows you to proactively identify and mitigate domain impersonation and phishing attacks. By monitoring newly registered domains and visual assets across the Internet, Cloudflare helps protect your brand's reputation and prevents your customers or employees from submitting sensitive information to fraudulent sites.
@@ -9,4 +8,4 @@ Common threats include:
 
 - [Typosquatting](https://en.wikipedia.org/wiki/Typosquatting): For example, typing `cloudfalre.com` instead of `cloudflare.com`.
 - Concatenation of services (`cloudflare-service.com`) often registered by attackers to trick unsuspecting victims into submitting private information such as passwords.
-- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
\ No newline at end of file
+- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
diff --git a/src/content/partials/security-center/scan-frequency.mdx b/src/content/partials/security-center/scan-frequency.mdx
index 78e170a9f3c6a81..d5d4a4b4bfe5c98 100644
--- a/src/content/partials/security-center/scan-frequency.mdx
+++ b/src/content/partials/security-center/scan-frequency.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you enable Security Insights, Cloudflare performs scans automatically. Paying customers (as defined in the table below) are re-scanned daily and can trigger a scan manually:
@@ -8,4 +7,4 @@ Once you enable Security Insights, Cloudflare performs scans automatically. Payi
 | Plan                                      | Scan Frequency | On-Demand |
 | ----------------------------------------- | -------------- | --------- |
 | Accounts on a Free, Pro, or Business plan | Every 7 days   | Yes       |
-| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
\ No newline at end of file
+| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
diff --git a/src/content/partials/security-center/scan-properties.mdx b/src/content/partials/security-center/scan-properties.mdx
index aa07143a1e7c4f7..cb96cf4aa2a437c 100644
--- a/src/content/partials/security-center/scan-properties.mdx
+++ b/src/content/partials/security-center/scan-properties.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment.
-* **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
-* **Risk**: A description of the risk associated with not addressing the issue.
-* **Type**: The insight category.
+- **Severity**: The security risk of the insight. The severity values are: _Moderate_, _High_, and _Critical_. The higher the severity level, the higher the risk of threat to your environment.
+- **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
+- **Risk**: A description of the risk associated with not addressing the issue.
+- **Type**: The insight category.
diff --git a/src/content/partials/security-center/security-insights-definition.mdx b/src/content/partials/security-center/security-insights-definition.mdx
index caeb5d26174c035..b41a47d43774aa0 100644
--- a/src/content/partials/security-center/security-insights-definition.mdx
+++ b/src/content/partials/security-center/security-insights-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Security Insights provides you with a list of insights, covering different areas of your Cloudflare environment, such as: Cloudflare account settings, DNS record configurations, SSL/TLS certificates configurations, Cloudflare Access configurations and Cloudflare WAF configurations.
diff --git a/src/content/partials/smart-shield/argo-analytics.mdx b/src/content/partials/smart-shield/argo-analytics.mdx
index 32f48959a9305a7..de75df8e6e26cee 100644
--- a/src/content/partials/smart-shield/argo-analytics.mdx
+++ b/src/content/partials/smart-shield/argo-analytics.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
\ No newline at end of file
+Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
diff --git a/src/content/partials/smart-shield/argo-intro.mdx b/src/content/partials/smart-shield/argo-intro.mdx
index 268b8495d8fe135..32ea358182d40ac 100644
--- a/src/content/partials/smart-shield/argo-intro.mdx
+++ b/src/content/partials/smart-shield/argo-intro.mdx
@@ -6,5 +6,5 @@ params:
 Argo Smart Routing detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
 
 { props.conditional === "dedicated-argo-tile" && (
-	<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
+<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
 )}
diff --git a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
index 9fa952b07643f85..3d8aa0a11fe62e8 100644
--- a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
+++ b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
\ No newline at end of file
+Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
diff --git a/src/content/partials/smart-shield/dcei-pool-requirements.mdx b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
index 7cafa55a6d95d3e..ac278f7e6a42db8 100644
--- a/src/content/partials/smart-shield/dcei-pool-requirements.mdx
+++ b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
\ No newline at end of file
+Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
diff --git a/src/content/partials/smart-shield/health-checks-analytics.mdx b/src/content/partials/smart-shield/health-checks-analytics.mdx
index 2983c5deb95bc9f..6a9a9c84165553c 100644
--- a/src/content/partials/smart-shield/health-checks-analytics.mdx
+++ b/src/content/partials/smart-shield/health-checks-analytics.mdx
@@ -194,4 +194,4 @@ If the failure cannot be classified as any other type of failure mentioned above
 
 #### Solution
 
-Contact [Cloudflare support](/support/contacting-cloudflare-support/).
\ No newline at end of file
+Contact [Cloudflare support](/support/contacting-cloudflare-support/).
diff --git a/src/content/partials/smart-shield/health-checks-intro.mdx b/src/content/partials/smart-shield/health-checks-intro.mdx
index ed843ebdf208147..5d9ab876a0af7ce 100644
--- a/src/content/partials/smart-shield/health-checks-intro.mdx
+++ b/src/content/partials/smart-shield/health-checks-intro.mdx
@@ -4,4 +4,4 @@
 
 A health check is a service that runs on Cloudflare's edge network to monitor whether an origin server is online. This allows you to view the health of your origin servers even if there is only one origin or you do not yet need to balance traffic across your infrastructure.
 
-Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
\ No newline at end of file
+Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
diff --git a/src/content/partials/smart-shield/health-checks-regions.mdx b/src/content/partials/smart-shield/health-checks-regions.mdx
index bbbbdb12d2c0ec9..4c0e494eaeec2e9 100644
--- a/src/content/partials/smart-shield/health-checks-regions.mdx
+++ b/src/content/partials/smart-shield/health-checks-regions.mdx
@@ -12,8 +12,8 @@ The Internet is not the same everywhere around the world and your users may not
 
 Analytics are presented at two levels:
 
-* Regional Aggregates: Combined results from the three data centers within a specific region.
-* Global Aggregates: Total results across all configured regions and data centers.
+- Regional Aggregates: Combined results from the three data centers within a specific region.
+- Global Aggregates: Total results across all configured regions and data centers.
 
 In the event log, entries are labeled by region or as **Global**. We do not provide granular data for individual data centers.
 
diff --git a/src/content/partials/smart-shield/smart-shield-callout.mdx b/src/content/partials/smart-shield/smart-shield-callout.mdx
index 15c3e70be832e5a..706d52242176099 100644
--- a/src/content/partials/smart-shield/smart-shield-callout.mdx
+++ b/src/content/partials/smart-shield/smart-shield-callout.mdx
@@ -4,4 +4,4 @@
 
 :::note[Smart Shield]
 This functionality is now offered as part of Cloudflare's origin server safeguard, Smart Shield. [Learn more](/smart-shield/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/smart-shield/zone-lockdown.mdx b/src/content/partials/smart-shield/zone-lockdown.mdx
index 77215453e523f54..5181bf0878bc7b3 100644
--- a/src/content/partials/smart-shield/zone-lockdown.mdx
+++ b/src/content/partials/smart-shield/zone-lockdown.mdx
@@ -18,7 +18,7 @@ To bypass zone lockdown using a WAF custom rule:
 
    To allow a specific Health Check, verify if the user agent contains the first 16 characters of the Health Check ID.
 
-3. Set the action to *Skip* and the corresponding feature to **Zone Lockdown** under **More components to skip**.
+3. Set the action to _Skip_ and the corresponding feature to **Zone Lockdown** under **More components to skip**.
 
 ### Via the API
 
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
index d19bdad602512e2..a743f57b374347a 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
@@ -1,50 +1,49 @@
 ---
 {}
-
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Below is a curl example and the associated data being posted to the API.
 
 **API example:**
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    dns: {
-      type: "CNAME",
-      name: "spectrum-cname.example.com"
-    },
-    ip_firewall: false,
-    protocol: "tcp/22",
-    proxy_protocol: "off",
-    tls: "off",
-    origin_dns: {
-      name: "cname-to-origin.example.com",
-      ttl: 1200
-    },
-    origin_port: 22
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		dns: {
+			type: "CNAME",
+			name: "spectrum-cname.example.com",
+		},
+		ip_firewall: false,
+		protocol: "tcp/22",
+		proxy_protocol: "off",
+		tls: "off",
+		origin_dns: {
+			name: "cname-to-origin.example.com",
+			ttl: 1200,
+		},
+		origin_port: 22,
+	}}
 />
 
 **Example data:**
 
 ```json
 {
-  "dns": {
-    "type": "CNAME",
-    "name": "spectrum-cname.example.com"
-  },
-  "ip_firewall": false,
-  "protocol": "tcp/22",
-  "proxy_protocol": "off",
-  "tls": "off",
-  "origin_dns": {
-    "name": "cname-to-origin.example.com",
-    "ttl": 1200
-  },
-  "origin_port": 22
+	"dns": {
+		"type": "CNAME",
+		"name": "spectrum-cname.example.com"
+	},
+	"ip_firewall": false,
+	"protocol": "tcp/22",
+	"proxy_protocol": "off",
+	"tls": "off",
+	"origin_dns": {
+		"name": "cname-to-origin.example.com",
+		"ttl": 1200
+	},
+	"origin_port": 22
 }
 ```
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
index 7bca9b160ea79e7..2e354499765aa68 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Spectrum** page.
 
diff --git a/src/content/partials/speed/rocket-loader-csp.mdx b/src/content/partials/speed/rocket-loader-csp.mdx
index 5f9b9948eb37a16..415fe7be153ccd2 100644
--- a/src/content/partials/speed/rocket-loader-csp.mdx
+++ b/src/content/partials/speed/rocket-loader-csp.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> in place for your domain, you will need to [update your headers](/fundamentals/reference/policies-compliances/content-security-policies/#product-requirements) to support Rocket Loader.
diff --git a/src/content/partials/speed/user-agents.mdx b/src/content/partials/speed/user-agents.mdx
index c0837b69232398f..f5ce8588ee1bd80 100644
--- a/src/content/partials/speed/user-agents.mdx
+++ b/src/content/partials/speed/user-agents.mdx
@@ -1,19 +1,17 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 For **IPv6** Cloudflare Observatory tests originate from **ASN 15169** or **ASN 132892** and are generated with the following user agents:
 
-* Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
-* Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
+- Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
+- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
 
 For **IPv4** Cloudflare Observatory tests originate from **ASN 396982** and are generated with the following user agents:
 
-* Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
-* Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
+- Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
+- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
 
 :::
diff --git a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
index f31818fcb7c6970..684249cf2e95c7c 100644
--- a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
+++ b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The available options for **Validation method** and **Certificate Validity Period** may vary depending on the certificate authority you choose and the hostnames that you include in your Advanced certificate order.
diff --git a/src/content/partials/ssl/acm-definition.mdx b/src/content/partials/ssl/acm-definition.mdx
index dd03df9af1b9a04..b7e35411b9f6074 100644
--- a/src/content/partials/ssl/acm-definition.mdx
+++ b/src/content/partials/ssl/acm-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use advanced certificates when you want something more customizable than [Universal SSL](/ssl/edge-certificates/universal-ssl/) but still want the convenience of SSL certificate issuance and renewal.
diff --git a/src/content/partials/ssl/acm-validate-cert.mdx b/src/content/partials/ssl/acm-validate-cert.mdx
index 28d8bc6f0d5532f..9927c34e5e8158d 100644
--- a/src/content/partials/ssl/acm-validate-cert.mdx
+++ b/src/content/partials/ssl/acm-validate-cert.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 To check whether your certificates have been validated and reissued:
 
-* **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
-* **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
+- **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
+- **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
diff --git a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
index 1d472785e89e8e2..dff294bdc66047e 100644
--- a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
+++ b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```bash
@@ -24,4 +23,4 @@ curl --silent \
 --header "X-Auth-Email: $MYAUTHEMAIL" \
 --header "X-Auth-Key: $MYAUTHKEY" \
 --data "$request_body"
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/ssl/caa-records-added-by-cf.mdx b/src/content/partials/ssl/caa-records-added-by-cf.mdx
index 1a4489c3befb910..5ff6ca31c6bf4b5 100644
--- a/src/content/partials/ssl/caa-records-added-by-cf.mdx
+++ b/src/content/partials/ssl/caa-records-added-by-cf.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare adds CAA records automatically in the following situations:
@@ -11,7 +10,7 @@ Cloudflare adds CAA records automatically in the following situations:
 These records make sure Cloudflare can still issue Universal certificates on your behalf.
 
 :::note[Subdomain zones caveat]
-CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) -  with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
+CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) - with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
 :::
 
 If Cloudflare has automatically added CAA records on your behalf, these records will not appear in the Cloudflare dashboard. However, if you run a command line query using `dig`, you can see any existing CAA records, including those added by Cloudflare (replacing `example.com` with your own domain on Cloudflare):
diff --git a/src/content/partials/ssl/caa-records-definition.mdx b/src/content/partials/ssl/caa-records-definition.mdx
index 0154a3d0a0fc6b4..fd0343ee0ae9acb 100644
--- a/src/content/partials/ssl/caa-records-definition.mdx
+++ b/src/content/partials/ssl/caa-records-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A Certificate Authority Authorization (CAA) DNS record specifies which certificate authorities (CAs) are allowed to issue certificates for a domain. This record reduces the chance of unauthorized certificate issuance and promotes standardization across your organization.
diff --git a/src/content/partials/ssl/change-encryption-mode-api.mdx b/src/content/partials/ssl/change-encryption-mode-api.mdx
index 56ae28c0a1ced82..c9c759459aa123f 100644
--- a/src/content/partials/ssl/change-encryption-mode-api.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To adjust your encryption mode with the API, send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `ssl` as the setting name in the URI path, and the `value` parameter set to your desired setting (`off`, `flexible`, `full`, `strict`, or `origin_pull`).
diff --git a/src/content/partials/ssl/change-encryption-mode-dash.mdx b/src/content/partials/ssl/change-encryption-mode-dash.mdx
index e7e6afa2c5c9740..a831eabba8bed79 100644
--- a/src/content/partials/ssl/change-encryption-mode-dash.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/cipher-suites-api-linkout.mdx b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
index ceda6f3443c4a1f..630e79915c01b64 100644
--- a/src/content/partials/ssl/cipher-suites-api-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
\ No newline at end of file
+If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
diff --git a/src/content/partials/ssl/cipher-suites-definition.mdx b/src/content/partials/ssl/cipher-suites-definition.mdx
index eea7fc621379f4f..659728684c4e279 100644
--- a/src/content/partials/ssl/cipher-suites-definition.mdx
+++ b/src/content/partials/ssl/cipher-suites-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cipher suites are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/) (and therefore separate from the [SSL/TLS protocol](/ssl/reference/protocols/)).
diff --git a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
index 8d202297dd8d513..308d5f6b820a7d9 100644
--- a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
\ No newline at end of file
+For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
diff --git a/src/content/partials/ssl/ciphers-api-general-notes.mdx b/src/content/partials/ssl/ciphers-api-general-notes.mdx
index 431555f3a04bc82..3461784c3991163 100644
--- a/src/content/partials/ssl/ciphers-api-general-notes.mdx
+++ b/src/content/partials/ssl/ciphers-api-general-notes.mdx
@@ -1,7 +1,7 @@
 ---
 {}
-
 ---
+
 To configure cipher suites per hostname, replace the first two lines by the following:
 
 ```bash
diff --git a/src/content/partials/ssl/cname-cert-verification.mdx b/src/content/partials/ssl/cname-cert-verification.mdx
index 6803cb1241595a9..1af431ba8e62f82 100644
--- a/src/content/partials/ssl/cname-cert-verification.mdx
+++ b/src/content/partials/ssl/cname-cert-verification.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare contacts one of our certificate authority (CA) providers and asks them to issue certificates for the specified hostname. The CA will then inform Cloudflare that we need to demonstrate control of this hostname by returning a `$DCV_TOKEN` at a specified `$DCV_FILENAME`; both the token and the filename are randomly generated by the CA and not known to Cloudflare ahead of time.
diff --git a/src/content/partials/ssl/csr-definition.mdx b/src/content/partials/ssl/csr-definition.mdx
index c3f8ebb7fdbce8c..a77784b8eeb8a0f 100644
--- a/src/content/partials/ssl/csr-definition.mdx
+++ b/src/content/partials/ssl/csr-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Generate a Certificate Signing Request (CSR) to get a custom certificate from the Certificate Authority (CA) of your choice while maintaining control of the private key on Cloudflare. The private key associated with the CSR will be generated by Cloudflare and will never leave our network.
diff --git a/src/content/partials/ssl/custom-cert-ciphers.mdx b/src/content/partials/ssl/custom-cert-ciphers.mdx
index 3f3a5f7954778d6..bba82764fc568eb 100644
--- a/src/content/partials/ssl/custom-cert-ciphers.mdx
+++ b/src/content/partials/ssl/custom-cert-ciphers.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before deploying custom certificates to Cloudflare's global network, Cloudflare automatically groups the certificates into certificate packs.
@@ -9,6 +8,6 @@ A certificate pack is a group of certificates that share the same set of hostnam
 
 Each pack can include up to three certificates, one from each of the following signature algorithms:
 
-* `SHA-2/RSA`
-* `SHA-2/ECDSA`
-* `SHA-1/RSA`
+- `SHA-2/RSA`
+- `SHA-2/ECDSA`
+- `SHA-1/RSA`
diff --git a/src/content/partials/ssl/custom-cert-openssl-commands.mdx b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
index 547be3cbf37680a..7bcbf7ba02b6ffc 100644
--- a/src/content/partials/ssl/custom-cert-openssl-commands.mdx
+++ b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. Run the following command to generate a 4096-bit RSA private key, using AES-256 encryption. Enter a passphrase when prompted.
diff --git a/src/content/partials/ssl/custom-certificates-definition.mdx b/src/content/partials/ssl/custom-certificates-definition.mdx
index 64d10e717e0b1ed..8b65b18a079f395 100644
--- a/src/content/partials/ssl/custom-certificates-definition.mdx
+++ b/src/content/partials/ssl/custom-certificates-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom certificates are meant for Business and Enterprise customers who want to use their own SSL certificates.
diff --git a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
index 7cf70fd8b8e6960..fd1a1fad0352eb7 100644
--- a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
+++ b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom Origin Trust Store allows you to upload certificate authorities (CAs) that Cloudflare will use to authenticate connections to your origin server. Use this feature to override the default trust store with your preferred CA or CAs.
diff --git a/src/content/partials/ssl/dcv-certificate-renewal.mdx b/src/content/partials/ssl/dcv-certificate-renewal.mdx
index 966d6f3d11cb207..77fff64fa5de773 100644
--- a/src/content/partials/ssl/dcv-certificate-renewal.mdx
+++ b/src/content/partials/ssl/dcv-certificate-renewal.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
 Even if you manually handle DCV when issuing certificates in a [partial DNS setup](/dns/zone-setups/partial-setup/), at certificate renewal, Cloudflare will attempt to automatically perform DCV via HTTP.
 
 If all of the following conditions are confirmed at the first attempt, the renewal happens automatically via [HTTP](/ssl/edge-certificates/changing-dcv-method/methods/http/).
 
-* Hostnames are proxied.
-* Hostnames on the certificate resolve to the IPs assigned to the zone.
-* The certificate does not contain wildcards.
+- Hostnames are proxied.
+- Hostnames on the certificate resolve to the IPs assigned to the zone.
+- The certificate does not contain wildcards.
 
 :::note
 To automatically renew certificates that do not meet the referred criteria, consider using [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/dcv-conflicting-records.mdx b/src/content/partials/ssl/dcv-conflicting-records.mdx
index c6a89d7d1f55c86..e932ebc41dd7175 100644
--- a/src/content/partials/ssl/dcv-conflicting-records.mdx
+++ b/src/content/partials/ssl/dcv-conflicting-records.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Remove previous TXT records]
@@ -11,4 +10,4 @@ Existing TXT records for `_acme-challenge` will conflict with the delegated DCV
 _acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
 ```
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/dcv-definition.mdx b/src/content/partials/ssl/dcv-definition.mdx
index 88a6cd79a67b650..c5748e6902bfec1 100644
--- a/src/content/partials/ssl/dcv-definition.mdx
+++ b/src/content/partials/ssl/dcv-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before a certificate authority (CA) will issue a certificate for a domain, the requester must prove they have control over that domain. This process is known as domain control validation (DCV).
diff --git a/src/content/partials/ssl/dcv-invalid-token-situations.mdx b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
index d705eaac712405c..785d89543fd4097 100644
--- a/src/content/partials/ssl/dcv-invalid-token-situations.mdx
+++ b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Tokens may also become invalid upon validation failure. For more details, refer to [Domain control validation flow](/ssl/edge-certificates/changing-dcv-method/dcv-flow/#dcv-tokens).
diff --git a/src/content/partials/ssl/dcv-path-security.mdx b/src/content/partials/ssl/dcv-path-security.mdx
index 5501d6eb5a3f734..eb4a9601201193b 100644
--- a/src/content/partials/ssl/dcv-path-security.mdx
+++ b/src/content/partials/ssl/dcv-path-security.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When your certificate is in `pending_validation` and valid tokens are in place, some security features targeting your zone's path for `/.well-known/*` can be automatically bypassed.
diff --git a/src/content/partials/ssl/dcv-renewal-fallback.mdx b/src/content/partials/ssl/dcv-renewal-fallback.mdx
index fd0e39d48edac6e..662ad6b134f61e1 100644
--- a/src/content/partials/ssl/dcv-renewal-fallback.mdx
+++ b/src/content/partials/ssl/dcv-renewal-fallback.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If any one of the conditions is not met, the certificate renewal falls back to your chosen method and you will need to [repeat the DCV process](/ssl/edge-certificates/changing-dcv-method/methods/txt/#get-dcv-values) manually.
diff --git a/src/content/partials/ssl/dcv-validate-patch.mdx b/src/content/partials/ssl/dcv-validate-patch.mdx
index 26c6cda69d9927a..173f9e888cce376 100644
--- a/src/content/partials/ssl/dcv-validate-patch.mdx
+++ b/src/content/partials/ssl/dcv-validate-patch.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To request an immediate recheck, send another [PATCH request](/api/resources/ssl/subresources/verification/methods/edit/) with the same `validation_method` as your current validation method.
diff --git a/src/content/partials/ssl/encryption-mode-definition.mdx b/src/content/partials/ssl/encryption-mode-definition.mdx
index 145f8a9e7617a8f..22d2c160d68d3b2 100644
--- a/src/content/partials/ssl/encryption-mode-definition.mdx
+++ b/src/content/partials/ssl/encryption-mode-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Your zone's **SSL/TLS Encryption Mode** controls how Cloudflare manages two connections: one between your visitors and Cloudflare, and the other between Cloudflare and your origin server.
diff --git a/src/content/partials/ssl/enforce-https-recommendation.mdx b/src/content/partials/ssl/enforce-https-recommendation.mdx
index 9c7faf843ba079a..3bedac422468cc2 100644
--- a/src/content/partials/ssl/enforce-https-recommendation.mdx
+++ b/src/content/partials/ssl/enforce-https-recommendation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Even if your application has an active edge certificate, visitors can still access resources over unsecured HTTP connections.
diff --git a/src/content/partials/ssl/error-rate-limiting.mdx b/src/content/partials/ssl/error-rate-limiting.mdx
index ba85796a11af004..239593e80b8d7b9 100644
--- a/src/content/partials/ssl/error-rate-limiting.mdx
+++ b/src/content/partials/ssl/error-rate-limiting.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 As mentioned in [Certificate authorities](/ssl/reference/certificate-authorities/), specific CAs may have their own limitations. If you use Let’s Encrypt and receive the error below, it means you hit the [duplicate certificate limit](https://letsencrypt.org/docs/duplicate-certificate-limit/) imposed by Let's Encrypt.
diff --git a/src/content/partials/ssl/generic-validation-process.mdx b/src/content/partials/ssl/generic-validation-process.mdx
index 0b3edf72e02fea2..e67dc0bfa07e1cb 100644
--- a/src/content/partials/ssl/generic-validation-process.mdx
+++ b/src/content/partials/ssl/generic-validation-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/geokey-manager-v1.mdx b/src/content/partials/ssl/geokey-manager-v1.mdx
index 38388aa647932b8..c2a97612cff66a7 100644
--- a/src/content/partials/ssl/geokey-manager-v1.mdx
+++ b/src/content/partials/ssl/geokey-manager-v1.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The first version of Geo Key Manager supports 3 regions: U.S., E.U., and a set of High Security Data Centers. If you would like to restrict your private key to another country or region, [apply for the closed beta](https://www.cloudflare.com/lp/geo-key-manager/) of the new version.
diff --git a/src/content/partials/ssl/get-started-additional-features.mdx b/src/content/partials/ssl/get-started-additional-features.mdx
index 9e7f8fdb53fbfc6..e975392ac50b3c9 100644
--- a/src/content/partials/ssl/get-started-additional-features.mdx
+++ b/src/content/partials/ssl/get-started-additional-features.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 After you have chosen your encryption mode and enforced HTTPS connections, evaluate the following settings:
 
-* [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
-* [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
-* [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
+- [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
+- [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
+- [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
diff --git a/src/content/partials/ssl/http-cname-validation-process.mdx b/src/content/partials/ssl/http-cname-validation-process.mdx
index f5e56eee7eb0688..33d5cd00e2c0499 100644
--- a/src/content/partials/ssl/http-cname-validation-process.mdx
+++ b/src/content/partials/ssl/http-cname-validation-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/http-to-txt-schedule.mdx b/src/content/partials/ssl/http-to-txt-schedule.mdx
index 7081625d6110114..94368fb7c494aae 100644
--- a/src/content/partials/ssl/http-to-txt-schedule.mdx
+++ b/src/content/partials/ssl/http-to-txt-schedule.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 - 90-days certificates: after failing for 15 days
 - 30-days certificates: after failing for 7 days
-- 14-days certificates: after failing for 3 days
\ No newline at end of file
+- 14-days certificates: after failing for 3 days
diff --git a/src/content/partials/ssl/keyless-ssl-definition.mdx b/src/content/partials/ssl/keyless-ssl-definition.mdx
index 12b1d3ad53d80e7..7199cc1bbca9e0a 100644
--- a/src/content/partials/ssl/keyless-ssl-definition.mdx
+++ b/src/content/partials/ssl/keyless-ssl-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Keyless SSL allows security-conscious clients to upload their own custom certificates and benefit from Cloudflare, but without exposing their TLS private keys.
diff --git a/src/content/partials/ssl/keyless-tunnel-setup.mdx b/src/content/partials/ssl/keyless-tunnel-setup.mdx
index ff09dc073729618..fc296217a5ba2fd 100644
--- a/src/content/partials/ssl/keyless-tunnel-setup.mdx
+++ b/src/content/partials/ssl/keyless-tunnel-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This process differs depending on whether you are using the [command line](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/create-local-tunnel/) or the [Cloudflare dashboard](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/).
diff --git a/src/content/partials/ssl/keyless-upload-preamble.mdx b/src/content/partials/ssl/keyless-upload-preamble.mdx
index 1c57296ce980ad0..ae8cfa436a5f20f 100644
--- a/src/content/partials/ssl/keyless-upload-preamble.mdx
+++ b/src/content/partials/ssl/keyless-upload-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before your key servers can be configured, you must next upload the corresponding SSL certificates to Cloudflare’s edge. During TLS termination, Cloudflare will present these certificates to connecting browsers and then (for non-resumed sessions) communicate with the specified key server to complete the handshake.
diff --git a/src/content/partials/ssl/origin-ca-pause-error.mdx b/src/content/partials/ssl/origin-ca-pause-error.mdx
index a3d2919fcdfbca3..282af35186d78e9 100644
--- a/src/content/partials/ssl/origin-ca-pause-error.mdx
+++ b/src/content/partials/ssl/origin-ca-pause-error.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
 
-Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
\ No newline at end of file
+Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
index 5ce503fae04a18f..ee3c0a0ba7c5962 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -11,10 +10,9 @@ This applies to customers using [Universal](/ssl/edge-certificates/universal-ssl
 
 If one of the hostnames on the certificate is not proxying traffic through Cloudflare, certificate issuance and renewal will vary based on the type of certificate you are using:
 
-* **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
-* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
-
+- **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
+- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 :::tip
 If all hostnames are proxied and non-wildcard but you are using [TXT](/ssl/edge-certificates/changing-dcv-method/methods/txt/) as DCV method for advanced certificates, also consider [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to simplify the process.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
index c506b1aaf0cbe6b..59e04d484d2bc13 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 For wildcard hostname certificates, certificate issuance and renewal varies based on the type of certificate you are using:
 
-* **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
-* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+- **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
+- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 If you cannot use Delegated DCV, you need to use [TXT based DCV](/ssl/edge-certificates/changing-dcv-method/methods/txt/) for certificate issuance and renewal. This means you will need to place one TXT DCV token for every hostname on the certificate. If one or more of the hostnames on the certificate fails to validate, the certificate will not be issued or renewed.
 
diff --git a/src/content/partials/ssl/ssl-mode-errors.mdx b/src/content/partials/ssl/ssl-mode-errors.mdx
index 6c4766d72ecd2c2..2182e11414cdb4f 100644
--- a/src/content/partials/ssl/ssl-mode-errors.mdx
+++ b/src/content/partials/ssl/ssl-mode-errors.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Depending on your origin configuration, you may have to adjust settings to avoid [Mixed Content errors](/ssl/troubleshooting/mixed-content-errors/) or [redirect loops](/ssl/troubleshooting/too-many-redirects/).
diff --git a/src/content/partials/ssl/ssl-mode-no-aop.mdx b/src/content/partials/ssl/ssl-mode-no-aop.mdx
index 4818962513eef71..de73f0f75904e95 100644
--- a/src/content/partials/ssl/ssl-mode-no-aop.mdx
+++ b/src/content/partials/ssl/ssl-mode-no-aop.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Authenticated Origin Pull](/ssl/origin-configuration/authenticated-origin-pull/) does not work when your [**SSL/TLS encryption mode**](/ssl/origin-configuration/ssl-modes/) is set to **Off** or **Flexible**.
diff --git a/src/content/partials/ssl/ssl-recommender-post-setup.mdx b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
index f742c710a2e813c..c20c95e8c8d9494 100644
--- a/src/content/partials/ssl/ssl-recommender-post-setup.mdx
+++ b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 Once enabled, the SSL/TLS Recommender runs an origin scan using the user agent `Cloudflare-SSLDetector` and ignores your `robots.txt` file (except for rules explicitly targeting the user agent).
 
 Based on this initial scan, the Recommender may decide that you could use a stronger [SSL encryption mode](/ssl/origin-configuration/ssl-modes/). It will never recommend a weaker option than what is currently configured.
 
-If so, it will send the application owner an email with the recommended option and add a *Recommended by Cloudflare* tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
+If so, it will send the application owner an email with the recommended option and add a _Recommended by Cloudflare_ tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
 
 If you do not receive an email, keep your current **SSL encryption mode**.
diff --git a/src/content/partials/ssl/ssl-recommender-prereqs.mdx b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
index 5a469237108799e..54a2fb9f09c8532 100644
--- a/src/content/partials/ssl/ssl-recommender-prereqs.mdx
+++ b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 To make sure you do not inadvertently block the **SSL/TLS Recommender**, review your settings to make sure your domain:
 
-* Is accessible.
-* Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
-* Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
+- Is accessible.
+- Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
+- Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
diff --git a/src/content/partials/ssl/test-tls-version.mdx b/src/content/partials/ssl/test-tls-version.mdx
index 610dd99b691b6f9..7795c23bee8e13c 100644
--- a/src/content/partials/ssl/test-tls-version.mdx
+++ b/src/content/partials/ssl/test-tls-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To test supported TLS versions, attempt a request to your website or application while specifying a TLS version.
@@ -17,4 +16,4 @@ If the TLS version you are testing is blocked by Cloudflare, the TLS handshake i
 
 :::note
 Local VPN or a device security client may prevent insecure connections using legacy protocols like TLS 1.0. Make sure to disable such network or security client before running the test on your device.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
index 40fff440b9fdfbe..39ab2370be87926 100644
--- a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
+++ b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You cannot set specific TLS 1.3 ciphers. Instead, you can enable [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) for your entire zone and Cloudflare will use [all applicable TLS 1.3 cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites/). In combination with this, you can still [disable weak cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) for TLS 1.0-1.2.
diff --git a/src/content/partials/ssl/total-tls-character-limitation.mdx b/src/content/partials/ssl/total-tls-character-limitation.mdx
index 2f4bd6c578be433..958bf51b7fa1f6c 100644
--- a/src/content/partials/ssl/total-tls-character-limitation.mdx
+++ b/src/content/partials/ssl/total-tls-character-limitation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
\ No newline at end of file
+Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
diff --git a/src/content/partials/ssl/txt-validation-api.mdx b/src/content/partials/ssl/txt-validation-api.mdx
index cdf1f38f24b2fcc..26ae11200ce4d88 100644
--- a/src/content/partials/ssl/txt-validation-api.mdx
+++ b/src/content/partials/ssl/txt-validation-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can access these tokens using the API with the [`GET` request](/api/resources/ssl/subresources/certificate_packs/methods/get/) and including `status=pending_validation` as a request parameter.
@@ -9,31 +8,31 @@ For example, here are two tokens highlighted in the API response for a wildcard
 
 ```json title="Response" {13,14,15,16,17,18,19,20,21,22,23,24}
 {
-  "result": [
-    {
-      "id": "<CERTIFICATE_ID>",
-      "type": "advanced",
-      "hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
-      "primary_certificate": "0",
-      "status": "pending_validation",
-      "certificates": [],
-      "created_on": "2022-10-12T21:46:21.979150Z",
-      "validity_days": 90,
-      "validation_method": "txt",
-      "validation_records": [
-        {
-          "status": "pending",
-          "txt_name": "_acme-challenge.<DOMAIN>.com",
-          "txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
-        },
-        {
-          "status": "pending",
-          "txt_name": "_acme-challenge.<DOMAIN>.com",
-          "txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
-        }
-      ],
-      "certificate_authority": "google"
-    }
-  ]
+	"result": [
+		{
+			"id": "<CERTIFICATE_ID>",
+			"type": "advanced",
+			"hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
+			"primary_certificate": "0",
+			"status": "pending_validation",
+			"certificates": [],
+			"created_on": "2022-10-12T21:46:21.979150Z",
+			"validity_days": 90,
+			"validation_method": "txt",
+			"validation_records": [
+				{
+					"status": "pending",
+					"txt_name": "_acme-challenge.<DOMAIN>.com",
+					"txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
+				},
+				{
+					"status": "pending",
+					"txt_name": "_acme-challenge.<DOMAIN>.com",
+					"txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
+				}
+			],
+			"certificate_authority": "google"
+		}
+	]
 }
 ```
diff --git a/src/content/partials/ssl/txt-validation-dashboard.mdx b/src/content/partials/ssl/txt-validation-dashboard.mdx
index e32eed0b158c9b1..af46b2c550b4575 100644
--- a/src/content/partials/ssl/txt-validation-dashboard.mdx
+++ b/src/content/partials/ssl/txt-validation-dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/txt-validation-definition.mdx b/src/content/partials/ssl/txt-validation-definition.mdx
index 01de109728d2ed3..adb5d6e522dfef2 100644
--- a/src/content/partials/ssl/txt-validation-definition.mdx
+++ b/src/content/partials/ssl/txt-validation-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 TXT record validation requires the creation of a TXT record in the hostname's authoritative DNS.
diff --git a/src/content/partials/ssl/txt-validation-preamble.mdx b/src/content/partials/ssl/txt-validation-preamble.mdx
index 93faafe1adf5447..f373dcb972851f5 100644
--- a/src/content/partials/ssl/txt-validation-preamble.mdx
+++ b/src/content/partials/ssl/txt-validation-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you [create a new certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) and choose the validation method of **TXT**, your tokens will be ready after a few seconds.
diff --git a/src/content/partials/ssl/universal-ssl-enable-full.mdx b/src/content/partials/ssl/universal-ssl-enable-full.mdx
index ccc7dd4e0694511..4eae263d68c1083 100644
--- a/src/content/partials/ssl/universal-ssl-enable-full.mdx
+++ b/src/content/partials/ssl/universal-ssl-enable-full.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For domains on a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], your domain should **automatically** receive its Universal SSL certificate within **15 minutes to 24 hours** of domain activation[^2].
diff --git a/src/content/partials/ssl/universal-ssl-validity.mdx b/src/content/partials/ssl/universal-ssl-validity.mdx
index ab44a9287adf96f..10512702dea5b86 100644
--- a/src/content/partials/ssl/universal-ssl-validity.mdx
+++ b/src/content/partials/ssl/universal-ssl-validity.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For Universal certificates, Cloudflare controls the validity periods and certificate authorities (CAs), making sure that renewal always occur.
@@ -9,4 +8,4 @@ For Universal certificates, Cloudflare controls the validity periods and certifi
 If you are on a [CNAME setup (partial)](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup), make sure [Domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/) is configured correctly. Refer to [Troubleshooting DCV](/ssl/edge-certificates/changing-dcv-method/troubleshooting/) for further help.
 :::
 
-Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
\ No newline at end of file
+Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
diff --git a/src/content/partials/ssl/ussl-limitations-solutions.mdx b/src/content/partials/ssl/ussl-limitations-solutions.mdx
index ee503a418a8aacd..3fdeeda79faea70 100644
--- a/src/content/partials/ssl/ussl-limitations-solutions.mdx
+++ b/src/content/partials/ssl/ussl-limitations-solutions.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 To prevent insecure connections on a multi-level subdomain, do one of the following:
 
-* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
-* Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
-* Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
+- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
+- Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
+- Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
 
 If none of these solutions work, you could also remove the multi-level subdomain.
diff --git a/src/content/partials/ssl/ussl-limitations-table.mdx b/src/content/partials/ssl/ussl-limitations-table.mdx
index f2f932a5a2b1a7e..7d391d48177e70e 100644
--- a/src/content/partials/ssl/ussl-limitations-table.mdx
+++ b/src/content/partials/ssl/ussl-limitations-table.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 By default, Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) only cover your apex domain and one level of subdomain.
diff --git a/src/content/partials/ssl/validation-level-note.mdx b/src/content/partials/ssl/validation-level-note.mdx
index 03bd8c76025c290..2eb371ceb102413 100644
--- a/src/content/partials/ssl/validation-level-note.mdx
+++ b/src/content/partials/ssl/validation-level-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Certificates issued through Cloudflare - [Universal](/ssl/edge-certificates/universal-ssl/), [Advanced](/ssl/edge-certificates/advanced-certificate-manager/), and [Custom Hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) certificates - are Domain Validated (DV). You can [upload a custom certificate](/ssl/edge-certificates/custom-certificates/) if your organization needs OV or EV certificates.
diff --git a/src/content/partials/stream/android_playback_code_snippet.mdx b/src/content/partials/stream/android_playback_code_snippet.mdx
index 6962729cc8a9fce..e60e829108231a9 100644
--- a/src/content/partials/stream/android_playback_code_snippet.mdx
+++ b/src/content/partials/stream/android_playback_code_snippet.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```kotlin
diff --git a/src/content/partials/stream/chromecast_limitations.mdx b/src/content/partials/stream/chromecast_limitations.mdx
index 0aa204b3ebbd6bb..e7a4b69eed6c016 100644
--- a/src/content/partials/stream/chromecast_limitations.mdx
+++ b/src/content/partials/stream/chromecast_limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/stream/ios_playback_code_snippet.mdx b/src/content/partials/stream/ios_playback_code_snippet.mdx
index 5b446692c4df2da..f9d23f1f2ea17d1 100644
--- a/src/content/partials/stream/ios_playback_code_snippet.mdx
+++ b/src/content/partials/stream/ios_playback_code_snippet.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```swift
diff --git a/src/content/partials/stream/prereqs.mdx b/src/content/partials/stream/prereqs.mdx
index 3c8c70289c8042a..abc70769ba595b1 100644
--- a/src/content/partials/stream/prereqs.mdx
+++ b/src/content/partials/stream/prereqs.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Before you can play videos, you must first [upload a video to Cloudflare Stream](/stream/uploading-videos/) or be [actively streaming to a live input](/stream/stream-live)
 
-
 :::
diff --git a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
index aa189ea437225d8..4359b8da3c410e2 100644
--- a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
+++ b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Before you can play live video, you must first be [actively streaming to a live input](/stream/stream-live/start-stream-live).
 
-
 :::
diff --git a/src/content/partials/stream/srt-supported-modes.mdx b/src/content/partials/stream/srt-supported-modes.mdx
index e265ce9ecd07404..2355744270cb533 100644
--- a/src/content/partials/stream/srt-supported-modes.mdx
+++ b/src/content/partials/stream/srt-supported-modes.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Stream only supports the SRT caller mode, which is responsible for broadcasting a live stream after a connection is established.
 
-
 :::
diff --git a/src/content/partials/style-guide/directory-listing-definition.mdx b/src/content/partials/style-guide/directory-listing-definition.mdx
index e301ae54c2538d0..3fe2c759e1c53cc 100644
--- a/src/content/partials/style-guide/directory-listing-definition.mdx
+++ b/src/content/partials/style-guide/directory-listing-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
\ No newline at end of file
+Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
diff --git a/src/content/partials/style-guide/icons.mdx b/src/content/partials/style-guide/icons.mdx
index 0ff4d9b2bdff1b2..e7565605607107d 100644
--- a/src/content/partials/style-guide/icons.mdx
+++ b/src/content/partials/style-guide/icons.mdx
@@ -3,4 +3,4 @@ params:
   - component
 ---
 
-Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
\ No newline at end of file
+Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
diff --git a/src/content/partials/style-guide/public-stats-definition.mdx b/src/content/partials/style-guide/public-stats-definition.mdx
index 0feedc632bbe330..5c337b32e6019f3 100644
--- a/src/content/partials/style-guide/public-stats-definition.mdx
+++ b/src/content/partials/style-guide/public-stats-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
\ No newline at end of file
+The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
diff --git a/src/content/partials/style-guide/tab-guidance.mdx b/src/content/partials/style-guide/tab-guidance.mdx
index bbabd5ac6d12ff3..0c4938e1fd9a2ce 100644
--- a/src/content/partials/style-guide/tab-guidance.mdx
+++ b/src/content/partials/style-guide/tab-guidance.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section. 
+The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section.
 
-Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
\ No newline at end of file
+Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
diff --git a/src/content/partials/style-guide/table-guidelines.mdx b/src/content/partials/style-guide/table-guidelines.mdx
index add12c6f1f8fea9..5095d31cef3b176 100644
--- a/src/content/partials/style-guide/table-guidelines.mdx
+++ b/src/content/partials/style-guide/table-guidelines.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
\ No newline at end of file
+Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
diff --git a/src/content/partials/support/2fa-enable.mdx b/src/content/partials/support/2fa-enable.mdx
index f93e4811432751f..dcde0ef633ea1f1 100644
--- a/src/content/partials/support/2fa-enable.mdx
+++ b/src/content/partials/support/2fa-enable.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 We recommend that all Cloudflare user account holders enable two-factor authentication (2FA) to keep your accounts secure. 
diff --git a/src/content/partials/support/2fa-overview.mdx b/src/content/partials/support/2fa-overview.mdx
index 566f562331ebb06..ef795a849728569 100644
--- a/src/content/partials/support/2fa-overview.mdx
+++ b/src/content/partials/support/2fa-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Two-factor authentication (2FA) allows user account owners to add an additional layer of login security to Cloudflare accounts. This additional authentication step requires you to provide both something you know, such as a Cloudflare password, and something you have, such as an authentication code from a mobile device.
diff --git a/src/content/partials/tenant/account-definition.mdx b/src/content/partials/tenant/account-definition.mdx
index 02febfffaee6f3b..9ad1c4090b9bb5a 100644
--- a/src/content/partials/tenant/account-definition.mdx
+++ b/src/content/partials/tenant/account-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An entity that contains various settings, users, and resources (zones, Zero Trust applications, Workers).
diff --git a/src/content/partials/tenant/account-details-preamble.mdx b/src/content/partials/tenant/account-details-preamble.mdx
index 67723262e1208c1..f43626e1f450432 100644
--- a/src/content/partials/tenant/account-details-preamble.mdx
+++ b/src/content/partials/tenant/account-details-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An [**Account**](/tenant/glossary/#account) will contain various settings, resources, and subscriptions to products for users. Each Tenant can have multiple associated accounts.
diff --git a/src/content/partials/tenant/account-details.mdx b/src/content/partials/tenant/account-details.mdx
index 0fe39346e3d974f..beac7c19ba854a0 100644
--- a/src/content/partials/tenant/account-details.mdx
+++ b/src/content/partials/tenant/account-details.mdx
@@ -1,27 +1,20 @@
 ---
 {}
-
 ---
 
-
-
 To retrieve a list of accounts associated with a Tenant details, send a `GET` request to the `/tenants/{tenant_id}/accounts` endpoint. You can find the Tenant tag and all Tenants associated with the user with the [**Tenant Details**](/tenant/how-to/get-tenant-details/) API. The Tenant Accounts API also requires pagination passed as query parameters:
 
-* `page` number
-
-  * Page number of accounts list response, indexed from 1
-
-* `per_page` number
-
-  * Number of accounts to display per page
-
-* `order` string
-  * (optional) Order by a specific column, has to be a valid top-level key from the response
+- `page` number
+  - Page number of accounts list response, indexed from 1
 
-  * `direction` number
-    * (optional) 0 for ascending or 1 for descending, is 0 by default
+- `per_page` number
+  - Number of accounts to display per page
 
+- `order` string
+  - (optional) Order by a specific column, has to be a valid top-level key from the response
 
+  - `direction` number
+    - (optional) 0 for ascending or 1 for descending, is 0 by default
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/tenants/{tenant_id}/accounts?page=1&per_page=10" \
diff --git a/src/content/partials/tenant/account-preamble.mdx b/src/content/partials/tenant/account-preamble.mdx
index f8b3baf7f3775a0..e1243d170a99457 100644
--- a/src/content/partials/tenant/account-preamble.mdx
+++ b/src/content/partials/tenant/account-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Each customer or team that uses Cloudflare should have their own account. This ensures proper security and access of resources. Each account acts as a container of zones and other resources. Depending on your needs, you may even provision multiple accounts for a single customer or team.
diff --git a/src/content/partials/tenant/create-account-api.mdx b/src/content/partials/tenant/create-account-api.mdx
index 7c40a5a7b6cd770..0783c47157f77f3 100644
--- a/src/content/partials/tenant/create-account-api.mdx
+++ b/src/content/partials/tenant/create-account-api.mdx
@@ -1,51 +1,39 @@
 ---
 {}
-
 ---
 
-
-
 To create an account using the API, make a `POST` request to the `/accounts` endpoint and include the following values:
 
-* `name` string
+- `name` string
+  - The name of the account that is displayed in the Cloudflare dashboard.
 
-  * The name of the account that is displayed in the Cloudflare dashboard.
+- `type` enum
+  - Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
 
-* `type` enum
+- `unit` object
+  - Information related to the tenant unit.
 
-  * Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
-
-* `unit` object
-  * Information related to the tenant unit.
-
-  * `id` string
-    * (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
+  - `id` string
+    - (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
 
 ### Know-Your-Customer (optional)
 
 All KYC parameters are text fields, have a 120 character limit, and are optional unless enforced by the Tenant.
 
-* `business_name` string
-
-  * (optional) The name of the business associated with this account.
-
-* `business_address` string
-
-  * (optional) The address of the business associated with this account.
-
-* `business_email` string
-
-  * (optional) The email of the business associated with this account.
-
-* `business_phone` string
-
-  * (optional) The phone number of the business associated with this account.
+- `business_name` string
+  - (optional) The name of the business associated with this account.
 
-* `external_metadata` string
+- `business_address` string
+  - (optional) The address of the business associated with this account.
 
-  * (optional) External metadata for this account.
+- `business_email` string
+  - (optional) The email of the business associated with this account.
 
+- `business_phone` string
+  - (optional) The phone number of the business associated with this account.
 
+- `external_metadata` string
+  - (optional) External metadata for this account.
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/accounts" \
@@ -62,17 +50,17 @@ A successful request will return an HTTP status of `200` and the following respo
 
 ```json title="Response"
 {
-  "result": {
-    "id": "2bab6ace8c72ed3f09b9eca6db1396bb",
-    "name": "<ACCOUNT_NAME>",
-    "type": "standard",
-    "settings": {
-      "enforce_twofactor": false
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "2bab6ace8c72ed3f09b9eca6db1396bb",
+		"name": "<ACCOUNT_NAME>",
+		"type": "standard",
+		"settings": {
+			"enforce_twofactor": false
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
diff --git a/src/content/partials/tenant/create-account-dash.mdx b/src/content/partials/tenant/create-account-dash.mdx
index 5ac799f25ff0d84..b419db913d27be1 100644
--- a/src/content/partials/tenant/create-account-dash.mdx
+++ b/src/content/partials/tenant/create-account-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create an account under your tenant using the dashboard:
diff --git a/src/content/partials/tenant/create-account-subscription.mdx b/src/content/partials/tenant/create-account-subscription.mdx
index 3079c476a2951ff..5de32a989695839 100644
--- a/src/content/partials/tenant/create-account-subscription.mdx
+++ b/src/content/partials/tenant/create-account-subscription.mdx
@@ -1,25 +1,17 @@
 ---
 {}
-
 ---
 
-
-
 To create an account subscription, send a [POST](/api/resources/accounts/subresources/subscriptions/methods/create/) request to the `/accounts/{account_id}/subscriptions` endpoint and include the following values:
 
-* `rate_plan` object
-
-  * Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
-
-* `component_values` array
-
-  * Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
-
-* `frequency` string
-
-  * How often the subscription is renewed automatically (defaults to `"monthly"`).
+- `rate_plan` object
+  - Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
 
+- `component_values` array
+  - Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
 
+- `frequency` string
+  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
 ```bash title="Request"
 curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/subscriptions' \
diff --git a/src/content/partials/tenant/create-zone-subscription.mdx b/src/content/partials/tenant/create-zone-subscription.mdx
index 4535e906db668f5..bf71f6c38a3b69f 100644
--- a/src/content/partials/tenant/create-zone-subscription.mdx
+++ b/src/content/partials/tenant/create-zone-subscription.mdx
@@ -1,27 +1,19 @@
 ---
 {}
-
 ---
 
-
-
 To create a zone subscription, typically used to upgrade a zone's plan from `PARTNERS_FREE` to a paid [Zone plan](/tenant/reference/subscriptions/#zone-plans), send a [POST](/api/resources/zones/subresources/subscriptions/methods/create/) request to the `/zones/{zone_id}/subscription` endpoint and include the following values:
 
-* `rate_plan` object
-
-  * Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
-
-* `component_values` array
-
-  * Additional services depending on your reseller agreement, such as additional `page_rules`.
-
-* `frequency` string
-
-  * How often the subscription is renewed automatically (defaults to `"monthly"`).
+- `rate_plan` object
+  - Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
 
+- `component_values` array
+  - Additional services depending on your reseller agreement, such as additional `page_rules`.
 
+- `frequency` string
+  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-```bash title="Request (without &#x60;component_values&#x60;)"
+```bash title="Request (without `component_values`)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
@@ -33,7 +25,7 @@ curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 }'
 ```
 
-```bash title="Request (with &#x60;component_values&#x60;)"
+```bash title="Request (with `component_values`)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
diff --git a/src/content/partials/tenant/resource-definition.mdx b/src/content/partials/tenant/resource-definition.mdx
index e8eb77e0f94146a..ccd4f6b5cf492d4 100644
--- a/src/content/partials/tenant/resource-definition.mdx
+++ b/src/content/partials/tenant/resource-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A resource is an entity owned by an account, which could be a zone/domain, a Workers instance, or a Zero Trust application.
diff --git a/src/content/partials/tenant/tenant-admin-definition.mdx b/src/content/partials/tenant/tenant-admin-definition.mdx
index fad90445024fac8..93e8c088ed8bd38 100644
--- a/src/content/partials/tenant/tenant-admin-definition.mdx
+++ b/src/content/partials/tenant/tenant-admin-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you sign a partner agreement with Cloudflare, we create a special Tenant account and then add your user to that account as a **Tenant admin**. Cloudflare can add multiple users as Tenant admins upon request.
diff --git a/src/content/partials/tenant/tenant-definition.mdx b/src/content/partials/tenant/tenant-definition.mdx
index 750a5387fbdb3c1..c3f7cca0a2e8b7d 100644
--- a/src/content/partials/tenant/tenant-definition.mdx
+++ b/src/content/partials/tenant/tenant-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A **Tenant** is a special type of Cloudflare account that contains other accounts and resources.
diff --git a/src/content/partials/tenant/tenant-details-preamble.mdx b/src/content/partials/tenant/tenant-details-preamble.mdx
index d1b84c3b3cbac7c..a54abfd6e57347a 100644
--- a/src/content/partials/tenant/tenant-details-preamble.mdx
+++ b/src/content/partials/tenant/tenant-details-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A [**Tenant Admin**](/tenant/glossary/#tenant-admin)'s unit and membership details will be used for access of resources and all Tenant operations on the API. The unit ID (`unit_tag`), for example, can be used to create an account on a specific unit.
diff --git a/src/content/partials/tenant/tenant-details.mdx b/src/content/partials/tenant/tenant-details.mdx
index 131ba5be5b9e779..9ee665e4b7dff30 100644
--- a/src/content/partials/tenant/tenant-details.mdx
+++ b/src/content/partials/tenant/tenant-details.mdx
@@ -1,14 +1,9 @@
 ---
 {}
-
 ---
 
-
-
 To retrieve tenant details, send a `GET` request to the `/user/tenants` endpoint:
 
-
-
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/user/tenants" \
 --header "X-Auth-Email: <EMAIL>" \
diff --git a/src/content/partials/tenant/user-definition.mdx b/src/content/partials/tenant/user-definition.mdx
index 6b17b01a9d90808..a7bb17ad18df033 100644
--- a/src/content/partials/tenant/user-definition.mdx
+++ b/src/content/partials/tenant/user-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A member of a Cloudflare account with their own user profile and [an associated role](/fundamentals/manage-members/roles/) that specifies their privileges within that account.
diff --git a/src/content/partials/terraform/create-r2-buckets.mdx b/src/content/partials/terraform/create-r2-buckets.mdx
index 13c5a4d7689c5d6..3e04904347b494d 100644
--- a/src/content/partials/terraform/create-r2-buckets.mdx
+++ b/src/content/partials/terraform/create-r2-buckets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs } from "~/components";
diff --git a/src/content/partials/terraform/find-ids-managed-rulesets.mdx b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
index e93b48bff9fb814..f096359f08c52fb 100644
--- a/src/content/partials/terraform/find-ids-managed-rulesets.mdx
+++ b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy the managed rulesets.
 
-* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
 
 The deployment of managed rulesets via Terraform requires that you use the ruleset IDs. To find the IDs of managed rulesets, use the [List account rulesets](/api/resources/rulesets/methods/list/) operation. The response will include the description and IDs of existing managed rulesets.
diff --git a/src/content/partials/terraform/find-ids.mdx b/src/content/partials/terraform/find-ids.mdx
index 25181bac1db4ec9..989917bed7dc690 100644
--- a/src/content/partials/terraform/find-ids.mdx
+++ b/src/content/partials/terraform/find-ids.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy rulesets.
 
-* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
diff --git a/src/content/partials/terraform/import-delete-existing-rulesets.mdx b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
index 3b1d669425223b3..b31987c47c68650 100644
--- a/src/content/partials/terraform/import-delete-existing-rulesets.mdx
+++ b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 Terraform assumes that it has complete control over account and zone rulesets. If you already have rulesets configured in your account or zone, do one of the following:
 
-* [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
-* Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
+- [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
+- Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
diff --git a/src/content/partials/terraform/v4-code-snippets.mdx b/src/content/partials/terraform/v4-code-snippets.mdx
index 99de18e73442fe3..485490e7bf66300 100644
--- a/src/content/partials/terraform/v4-code-snippets.mdx
+++ b/src/content/partials/terraform/v4-code-snippets.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 Terraform code snippets below refer to the v4 SDK only.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/terraform/v5-code-snippets.mdx b/src/content/partials/terraform/v5-code-snippets.mdx
index 4bd83b42ff17813..65ddb58c386e133 100644
--- a/src/content/partials/terraform/v5-code-snippets.mdx
+++ b/src/content/partials/terraform/v5-code-snippets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/time-services/ntp-definition.mdx b/src/content/partials/time-services/ntp-definition.mdx
index 76dc31d5a57dd6a..df9e63e8a5ab83d 100644
--- a/src/content/partials/time-services/ntp-definition.mdx
+++ b/src/content/partials/time-services/ntp-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Network Time Protocol](https://tools.ietf.org/html/rfc1305) (NTP) is an Internet protocol designed to synchronize time between computer systems communicating over unreliable and variable-latency network paths. Cloudflare offers its version of NTP for free so you can use our [global anycast network](https://www.cloudflare.com/network/) to synchronize time from our closest server.
diff --git a/src/content/partials/turnstile/challenge-behavior.mdx b/src/content/partials/turnstile/challenge-behavior.mdx
index f60a738f5071a3e..ff0bebf920921ee 100644
--- a/src/content/partials/turnstile/challenge-behavior.mdx
+++ b/src/content/partials/turnstile/challenge-behavior.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare issues challenges through the [Challenge Platform](/cloudflare-challenges/), which is the same underlying technology powering [Turnstile](/turnstile/).
diff --git a/src/content/partials/turnstile/privacy-policy.mdx b/src/content/partials/turnstile/privacy-policy.mdx
index cc7c482ea104785..061f021d37cc27a 100644
--- a/src/content/partials/turnstile/privacy-policy.mdx
+++ b/src/content/partials/turnstile/privacy-policy.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
\ No newline at end of file
+As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
diff --git a/src/content/partials/turnstile/proxied-hostnames.mdx b/src/content/partials/turnstile/proxied-hostnames.mdx
index e8beeab649b6d39..e9d1fd903e735be 100644
--- a/src/content/partials/turnstile/proxied-hostnames.mdx
+++ b/src/content/partials/turnstile/proxied-hostnames.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your hostname is proxied through Cloudflare, visitors may experience challenges on your webpages.
diff --git a/src/content/partials/turnstile/security-requirements.mdx b/src/content/partials/turnstile/security-requirements.mdx
index 7a31837435e6e89..2569ee7839e2ca3 100644
--- a/src/content/partials/turnstile/security-requirements.mdx
+++ b/src/content/partials/turnstile/security-requirements.mdx
@@ -1,9 +1,7 @@
 ---
 {}
-
 ---
 
-
 - Server-side validation is mandatory. It is critical to enforce Turnstile tokens with the Siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. You must call Siteverify to complete your Turnstile configuration. Otherwise, it is incomplete and will result in zeroes for token validation when viewing your metrics in [Turnstile Analytics](/turnstile/turnstile-analytics/).
 
 - Tokens expire after 300 seconds (5 minutes). Each token can only be validated once. Expired or used tokens must be replaced with fresh challenges.
diff --git a/src/content/partials/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/siteverify-warning.mdx
index 4e5b0a232868dfd..979c06c7a94acd4 100644
--- a/src/content/partials/turnstile/siteverify-warning.mdx
+++ b/src/content/partials/turnstile/siteverify-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Warning]
diff --git a/src/content/partials/turnstile/siteverify.mdx b/src/content/partials/turnstile/siteverify.mdx
index 59ba0e6f92f190a..775e57ebf87175b 100644
--- a/src/content/partials/turnstile/siteverify.mdx
+++ b/src/content/partials/turnstile/siteverify.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 It is important to [call the Siteverify API](/turnstile/get-started/server-side-validation/). Without calling Siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
 
 - Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
 - Tokens expire after five minutes. Validation must occur within this window to be effective.
-- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
\ No newline at end of file
+- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
diff --git a/src/content/partials/turnstile/test-secret-key.mdx b/src/content/partials/turnstile/test-secret-key.mdx
index 67d4fb5139a1840..142da6b947bd3e3 100644
--- a/src/content/partials/turnstile/test-secret-key.mdx
+++ b/src/content/partials/turnstile/test-secret-key.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 You can test the dummy token generated with testing sitekey via Siteverify API with the testing secret key. Your production secret keys will reject dummy tokens.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
diff --git a/src/content/partials/turnstile/test-sitekey.mdx b/src/content/partials/turnstile/test-sitekey.mdx
index 5ecb3a3c4062605..5bb6f0697d38eaf 100644
--- a/src/content/partials/turnstile/test-sitekey.mdx
+++ b/src/content/partials/turnstile/test-sitekey.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 You can test your Turnstile widget on your webpage without triggering an actual Cloudflare Challenge by using a testing sitekey.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
diff --git a/src/content/partials/turnstile/troubleshooting-steps.mdx b/src/content/partials/turnstile/troubleshooting-steps.mdx
index 8e9ff7625e051fb..471234502a31d07 100644
--- a/src/content/partials/turnstile/troubleshooting-steps.mdx
+++ b/src/content/partials/turnstile/troubleshooting-steps.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 1. Verify your browser compatibility.
-    - Turnstile supports all major browsers, except Internet Explorer.
-    - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
-    - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
+   - Turnstile supports all major browsers, except Internet Explorer.
+   - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
+   - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
 2. Disable your browser extensions.
-    - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
-    - Temporarily disable all extensions and reload the page.
+   - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
+   - Temporarily disable all extensions and reload the page.
 3. Enable JavaScript.
-    - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
+   - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
 4. Try Incognito or Private mode.
-    - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
+   - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
 5. Test another browser or device.
-    - Switch to a different browser or device to see if the issue is specific to your current setup.
+   - Switch to a different browser or device to see if the issue is specific to your current setup.
 6. Avoid VPNs or proxies.
-    - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
+   - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
 7. Switch to a different network.
-    - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
+   - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
diff --git a/src/content/partials/turnstile/widget-components.mdx b/src/content/partials/turnstile/widget-components.mdx
index 36da69ec11fc53f..a72f62cd2d99b6f 100644
--- a/src/content/partials/turnstile/widget-components.mdx
+++ b/src/content/partials/turnstile/widget-components.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 Each widget gets its own unique sitekey and secret key pair, and options for configurations.
 
-| Component | Description |
-| --- | --- |
-| Sitekey | Public key used to invoke the Turnstile widget on your site. |
-| Secret key | Private key used for server-side token validation. |
-| Configurations | Mode, hostnames, appearance settings, and other options. |
+| Component      | Description                                                  |
+| -------------- | ------------------------------------------------------------ |
+| Sitekey        | Public key used to invoke the Turnstile widget on your site. |
+| Secret key     | Private key used for server-side token validation.           |
+| Configurations | Mode, hostnames, appearance settings, and other options.     |
diff --git a/src/content/partials/vectorize/vectorize-ga.mdx b/src/content/partials/vectorize/vectorize-ga.mdx
index efd48735d4aac5d..78ba16f7ac1273b 100644
--- a/src/content/partials/vectorize/vectorize-ga.mdx
+++ b/src/content/partials/vectorize/vectorize-ga.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Vectorize is now Generally Available]
 
-
 To report bugs or give feedback, go to the [#vectorize Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
-
 :::
diff --git a/src/content/partials/vectorize/vectorize-pricing.mdx b/src/content/partials/vectorize/vectorize-pricing.mdx
index 9281365f50e95ed..8ff2bf6036a4c2c 100644
--- a/src/content/partials/vectorize/vectorize-pricing.mdx
+++ b/src/content/partials/vectorize/vectorize-pricing.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-|                                     | [Workers Free](/workers/platform/pricing/#workers)       | [Workers Paid](/workers/platform/pricing/#workers)                              |
-| ----------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------- |
-| **Total queried vector dimensions** | 30 million queried vector dimensions / month             | First 50 million queried vector dimensions / month included + $0.01 per million |
-| **Total stored vector dimensions**  | 5 million stored vector dimensions                       | First 10 million stored vector dimensions + $0.05 per 100 million               |
+|                                     | [Workers Free](/workers/platform/pricing/#workers) | [Workers Paid](/workers/platform/pricing/#workers)                              |
+| ----------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------- |
+| **Total queried vector dimensions** | 30 million queried vector dimensions / month       | First 50 million queried vector dimensions / month included + $0.01 per million |
+| **Total stored vector dimensions**  | 5 million stored vector dimensions                 | First 10 million stored vector dimensions + $0.05 per 100 million               |
 
 ### Calculating vector dimensions
 
diff --git a/src/content/partials/version-management/create-environment-situation.mdx b/src/content/partials/version-management/create-environment-situation.mdx
index 63f1307158b6f24..f6971602bd7ee8d 100644
--- a/src/content/partials/version-management/create-environment-situation.mdx
+++ b/src/content/partials/version-management/create-environment-situation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Based on your organization's needs, you may need to create additional environments to test and roll out changes.
diff --git a/src/content/partials/version-management/edit-version.mdx b/src/content/partials/version-management/edit-version.mdx
index 385307cecb41c36..39944dba67d8e50 100644
--- a/src/content/partials/version-management/edit-version.mdx
+++ b/src/content/partials/version-management/edit-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,12 +10,12 @@ To change between different versions of your zone:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and a domain that has version management. The Global Configuration of your domain will load.
 3. Go to the product or feature you wish to modify.
-   * **If the product or feature is available for versioning**: The last version you were working on will load.
-   * **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
+   - **If the product or feature is available for versioning**: The last version you were working on will load.
+   - **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
 4. Ensure that the configuration or version displayed in the domain summary bar is the one you would like to work on. If not, select the version in the domain summary bar to open the version switcher.
 
 :::note
diff --git a/src/content/partials/version-management/enable-default-creation.mdx b/src/content/partials/version-management/enable-default-creation.mdx
index e4ea2ec7726c964..8e98769c2ae8675 100644
--- a/src/content/partials/version-management/enable-default-creation.mdx
+++ b/src/content/partials/version-management/enable-default-creation.mdx
@@ -1,19 +1,16 @@
 ---
 {}
-
 ---
 
 Once you [enable](/version-management/how-to/enable/) Version Management, Cloudflare will automatically create:
 
-* **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
-* **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
+- **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
+- **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
 
 :::caution[Important]
 
-
 Any changes made to the **Global Configuration** will immediately apply to your zone and all versions of your zone, affecting live traffic.
 
-
 :::
 
 On the Environments page, you can create default environments for **Production**, **Staging**, and **Development**.
diff --git a/src/content/partials/version-management/enable-versioning.mdx b/src/content/partials/version-management/enable-versioning.mdx
index 0602c8e8c03f543..12ef04c2c918b0e 100644
--- a/src/content/partials/version-management/enable-versioning.mdx
+++ b/src/content/partials/version-management/enable-versioning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,7 +10,7 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
@@ -19,8 +18,6 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 :::note
 
-
 If you cannot enable Version Management, make sure your zone, account, and user meet the [requirements](/version-management/#requirements).
 
-
 :::
diff --git a/src/content/partials/version-management/environment-defaults.mdx b/src/content/partials/version-management/environment-defaults.mdx
index 896a639507362a4..572b0f7b00346e2 100644
--- a/src/content/partials/version-management/environment-defaults.mdx
+++ b/src/content/partials/version-management/environment-defaults.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
-* **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
-* **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
+- **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
+- **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
+- **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
diff --git a/src/content/partials/version-management/environment-definition.mdx b/src/content/partials/version-management/environment-definition.mdx
index 8219f760421603b..378169d4dcb3cba 100644
--- a/src/content/partials/version-management/environment-definition.mdx
+++ b/src/content/partials/version-management/environment-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An environment is a place to test different versions of your zone configurations.
diff --git a/src/content/partials/version-management/production-read-only-default.mdx b/src/content/partials/version-management/production-read-only-default.mdx
index 309f5eee6b6b858..9f1294d9a8e859c 100644
--- a/src/content/partials/version-management/production-read-only-default.mdx
+++ b/src/content/partials/version-management/production-read-only-default.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Production** is a read-only environment by default. This means that any version associated with **Production** also becomes read-only. This configuration prevents another member of your account from accidentally editing the version associated with your live traffic. You can change this configuration by editing the environment.
diff --git a/src/content/partials/version-management/promote-version.mdx b/src/content/partials/version-management/promote-version.mdx
index 9fa55abd7e19289..953f69ab8ea0963 100644
--- a/src/content/partials/version-management/promote-version.mdx
+++ b/src/content/partials/version-management/promote-version.mdx
@@ -1,16 +1,14 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
 
-
 To promote a version:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/test-version.mdx b/src/content/partials/version-management/test-version.mdx
index 30f9c66058586c5..26ffc6023ca8be6 100644
--- a/src/content/partials/version-management/test-version.mdx
+++ b/src/content/partials/version-management/test-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ Once you have made changes to a version, apply that version to your lowest-ranke
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/version-definition.mdx b/src/content/partials/version-management/version-definition.mdx
index 32f24171ac0cc3f..23ed20a7ece8e28 100644
--- a/src/content/partials/version-management/version-definition.mdx
+++ b/src/content/partials/version-management/version-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A version is a collection of configurations related to your zone, such as WAF custom rules and [other optimization configurations](/version-management/reference/available-configurations/).
diff --git a/src/content/partials/waf/api-create-ruleset-with-rule.mdx b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
index 04b31a71d329c75..18ec3b89654dcc2 100644
--- a/src/content/partials/waf/api-create-ruleset-with-rule.mdx
+++ b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To define a specific position for the new rule, include a `position` object in the request body according to the guidelines in [Change the order of a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/#change-the-order-of-a-rule-in-a-ruleset).
diff --git a/src/content/partials/waf/list-advantages.mdx b/src/content/partials/waf/list-advantages.mdx
index d5fed7a8acd3fbc..d6d8663d04e3c6e 100644
--- a/src/content/partials/waf/list-advantages.mdx
+++ b/src/content/partials/waf/list-advantages.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
-* When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
-* When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
-* Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
+- When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
+- When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
+- Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
 
 When you update the content of a list, any rules that use the list are automatically updated, so you can make a single change to your list rather than modify rules individually.
 
diff --git a/src/content/partials/waf/managed-lists.mdx b/src/content/partials/waf/managed-lists.mdx
index 8b6a68a42f9fb86..aebc0ae400a11c4 100644
--- a/src/content/partials/waf/managed-lists.mdx
+++ b/src/content/partials/waf/managed-lists.mdx
@@ -6,8 +6,8 @@
 | ----------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
 | Cloudflare Open Proxies                         | `cf.open_proxies`   | IP addresses of known open HTTP and SOCKS proxy endpoints, which are frequently used to launch attacks and hide attackers identity. |
 | Cloudflare Anonymizers                          | `cf.anonymizer`     | IP addresses of known anonymizers (Open SOCKS Proxies, VPNs, and TOR nodes).                                                        |
-| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers. |
+| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers.                                                                                                  |
 | Cloudflare Malware                              | `cf.malware`        | IP addresses of known sources of malware.                                                                                           |
 | Cloudflare Botnets, Command and Control Servers | `cf.botnetcc`       | IP addresses of known botnet command-and-control servers.                                                                           |
 
-<br />
\ No newline at end of file
+<br />
diff --git a/src/content/partials/waf/open-ports-blocked-traffic.mdx b/src/content/partials/waf/open-ports-blocked-traffic.mdx
index 98358a33d289ffd..e360487eafc6582 100644
--- a/src/content/partials/waf/open-ports-blocked-traffic.mdx
+++ b/src/content/partials/waf/open-ports-blocked-traffic.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Due to the nature of Cloudflare's anycast network, ports other than `80` and `443` will be open so that Cloudflare can serve traffic for other customers on these ports. In general, Cloudflare makes available several different products on [Cloudflare IPs](https://www.cloudflare.com/ips), so you can expect tools like Netcat and security scanners to report these non-standard ports as open in specific conditions. If you have questions on security compliance, review [Cloudflare's certifications and compliance resources](https://www.cloudflare.com/en-gb/trust-hub/compliance-resources/) and contact your Cloudflare enterprise account manager for more information.
diff --git a/src/content/partials/waf/rate-limiting-best-practices.mdx b/src/content/partials/waf/rate-limiting-best-practices.mdx
index 5f059b73120f923..0ef94060427faa0 100644
--- a/src/content/partials/waf/rate-limiting-best-practices.mdx
+++ b/src/content/partials/waf/rate-limiting-best-practices.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
-* [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
-* [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
-* [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
-* [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
+- [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
+- [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
+- [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
+- [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
+- [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
diff --git a/src/content/partials/waf/rate-limiting-rule-parameters.mdx b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
index 00a4d92d21e6462..ecbeba6002d94e2 100644
--- a/src/content/partials/waf/rate-limiting-rule-parameters.mdx
+++ b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-* An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
-* An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
+- An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
+- An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
 
 Besides these two parameters, rate limiting rules require the following additional parameters:
 
-* **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
-* **Period**: The period of time to consider (in seconds) when evaluating the rate.
-* **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
-* **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
-* **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
+- **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
+- **Period**: The period of time to consider (in seconds) when evaluating the rate.
+- **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
+- **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
+- **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
diff --git a/src/content/partials/waf/rules-next-steps-table.mdx b/src/content/partials/waf/rules-next-steps-table.mdx
index 8f12446af3318fa..b2513ef838112da 100644
--- a/src/content/partials/waf/rules-next-steps-table.mdx
+++ b/src/content/partials/waf/rules-next-steps-table.mdx
@@ -6,9 +6,9 @@ params:
 
 import { Markdown } from "~/components";
 
-| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                     |
+| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                       |
 | Update a rule             | <p>Use the [Update a zone ruleset rule](/api/resources/rulesets/methods/update/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Update a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/).</p> |
 | Delete a rule             | <p>Use the [Delete a zone ruleset rule](/api/resources/rulesets/methods/delete/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Delete a rule in a ruleset](/ruleset-engine/rulesets-api/delete-rule/).</p> |
 
diff --git a/src/content/partials/waiting-room/change-queueing-method.mdx b/src/content/partials/waiting-room/change-queueing-method.mdx
index 3ff0fa35e97cda9..3a7226abca98756 100644
--- a/src/content/partials/waiting-room/change-queueing-method.mdx
+++ b/src/content/partials/waiting-room/change-queueing-method.mdx
@@ -1,17 +1,14 @@
 ---
 {}
-
 ---
 
 Though you can change your [queueing method](/waiting-room/reference/queueing-methods/), it may affect users if your waiting room is actively queueing:
 
-* **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
-* **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
+- **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
+- **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
 
 :::note
 
-
 If you change the queueing method from FIFO > Random > FIFO, users will be ordered by their original entry time.
 
-
 :::
diff --git a/src/content/partials/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/queue-all.mdx
index f8625465ac3beeb..fe401b22131a2d6 100644
--- a/src/content/partials/waiting-room/queue-all.mdx
+++ b/src/content/partials/waiting-room/queue-all.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To queue all visitors prior to a time-based offering, set up a pre-queue as part of a [waiting room event](/waiting-room/additional-options/create-events/#create-an-event-from-the-dashboard).
diff --git a/src/content/partials/waiting-room/queue-some.mdx b/src/content/partials/waiting-room/queue-some.mdx
index a2ae7dd6d08055a..373a1bf37d6b081 100644
--- a/src/content/partials/waiting-room/queue-some.mdx
+++ b/src/content/partials/waiting-room/queue-some.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To queue visitors only when necessary:
diff --git a/src/content/partials/warp-client/modes-options.mdx b/src/content/partials/warp-client/modes-options.mdx
index 9582cee987393f3..2965f0ed7c28f20 100644
--- a/src/content/partials/warp-client/modes-options.mdx
+++ b/src/content/partials/warp-client/modes-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## WARP modes
@@ -23,11 +22,11 @@ Beyond the two modes of operation, the WARP app lets you configure additional op
 
 The following is a list of options you can configure in the **Connection** tab:
 
-* **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
-* **DNS Protocol**: The available options depend on the WARP mode you have enabled:
-  * **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
-  * **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
-  * **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
-* **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
+- **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
+- **DNS Protocol**: The available options depend on the WARP mode you have enabled:
+  - **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
+  - **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
+  - **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
+- **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
 
 For the **Advanced** options, refer to [Exclude or include network traffic with WARP](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/) for more information.
diff --git a/src/content/partials/web-analytics/web-analytics-definition.mdx b/src/content/partials/web-analytics/web-analytics-definition.mdx
index 1e5015687b288cc..1b6186550086a2c 100644
--- a/src/content/partials/web-analytics/web-analytics-definition.mdx
+++ b/src/content/partials/web-analytics/web-analytics-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Web Analytics provides free, privacy-first analytics for your website without changing your DNS or using Cloudflare’s proxy. Cloudflare Web Analytics helps you understand the performance of your web pages as experienced by your site visitors.
diff --git a/src/content/partials/web-analytics/web-analytics-notifications.mdx b/src/content/partials/web-analytics/web-analytics-notifications.mdx
index 6c43aff254d6a41..b0d9f16da41095b 100644
--- a/src/content/partials/web-analytics/web-analytics-notifications.mdx
+++ b/src/content/partials/web-analytics/web-analytics-notifications.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Web Analytics uses Cloudflare's Notification service. When enabled, Web Analytics sends you a weekly report with aggregate visits, page views and median page load time for all your sites, so you can monitor their performance.
diff --git a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
index 083546fd2a119b7..859414aab8041e6 100644
--- a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
+++ b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
index e713539e0af17a5..f57d62227d76b86 100644
--- a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
+++ b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For Cloudflare to automatically add the JavaScript snippet, your pages need to have valid HTML.
@@ -20,9 +19,7 @@ For Web Analytics to correctly insert the JavaScript snippet, you would need val
 		<title>Title</title>
 	</head>
 	<body>
-
 		<p>Hello world.</p>
-
 	</body>
 </html>
 ```
diff --git a/src/content/partials/web3/cloudflare-settings.mdx b/src/content/partials/web3/cloudflare-settings.mdx
index 652075c6ca43719..c557eb6be68904f 100644
--- a/src/content/partials/web3/cloudflare-settings.mdx
+++ b/src/content/partials/web3/cloudflare-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once your gateway becomes [active](/web3/reference/gateway-status/), you can customize the Cloudflare settings associated with your hostname.
diff --git a/src/content/partials/web3/create-gateway-api.mdx b/src/content/partials/web3/create-gateway-api.mdx
index e1952e8378a32e6..8b00c7b740ad9b5 100644
--- a/src/content/partials/web3/create-gateway-api.mdx
+++ b/src/content/partials/web3/create-gateway-api.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 To create a gateway using the API, send a [`POST`](/api/resources/web3/subresources/hostnames/methods/create/) request that includes the following parameters:
 
-* `name`: The hostname that will point to the target gateway via a `CNAME` record.
-* `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
+- `name`: The hostname that will point to the target gateway via a `CNAME` record.
+- `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
 
 If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
@@ -27,18 +26,18 @@ The response contains the complete definition of the new gateway.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "<WEB3_GATEWAY_ID>",
-    "name": "gateway.example.com",
-    "description": "This is my IPFS gateway.",
-    "status": "active",
-    "target": "ipfs",
-    "dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
-    "created_on": "<CREATED_ON_DATE>",
-    "modified_on": "<MODIFIED_ON_DATE>"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "<WEB3_GATEWAY_ID>",
+		"name": "gateway.example.com",
+		"description": "This is my IPFS gateway.",
+		"status": "active",
+		"target": "ipfs",
+		"dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
+		"created_on": "<CREATED_ON_DATE>",
+		"modified_on": "<MODIFIED_ON_DATE>"
+	}
 }
 ```
diff --git a/src/content/partials/web3/pricing-page-reference.mdx b/src/content/partials/web3/pricing-page-reference.mdx
index 28fa234c7caadd1..80deb4fcdfdd040 100644
--- a/src/content/partials/web3/pricing-page-reference.mdx
+++ b/src/content/partials/web3/pricing-page-reference.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 For more pricing details, refer to the [Web3 product page](https://www.cloudflare.com/application-services/products/web3/).
 
-
 :::
diff --git a/src/content/partials/workers-ai/custom_requirements.mdx b/src/content/partials/workers-ai/custom_requirements.mdx
index 8a34dddf8cb8d82..dfdd8c4a50439f7 100644
--- a/src/content/partials/workers-ai/custom_requirements.mdx
+++ b/src/content/partials/workers-ai/custom_requirements.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Custom requirements]
 
-
 If you have custom requirements like private custom models or higher limits, complete the [Custom Requirements Form](https://forms.gle/axnnpGDb6xrmR31T6). Cloudflare will contact you with next steps.
 
-
 :::
diff --git a/src/content/partials/workers-ai/file_issues.mdx b/src/content/partials/workers-ai/file_issues.mdx
index 3f30780c51c35ed..0e250e4dcc7c3b7 100644
--- a/src/content/partials/workers-ai/file_issues.mdx
+++ b/src/content/partials/workers-ai/file_issues.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Workers AI is now Generally Available]
 
-
 To report bugs or give feedback, go to the [#workers-ai Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
-
 :::
diff --git a/src/content/partials/workers-ai/openai-compatibility.mdx b/src/content/partials/workers-ai/openai-compatibility.mdx
index 64bc69da90146c0..e245b363ffe1571 100644
--- a/src/content/partials/workers-ai/openai-compatibility.mdx
+++ b/src/content/partials/workers-ai/openai-compatibility.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Workers AI supports OpenAI compatible endpoints for [text generation](/workers-ai/models/) (`/v1/chat/completions`) and [text embedding models](/workers-ai/models/) (`/v1/embeddings`). This allows you to use the same code as you would for your OpenAI commands, but swap in Workers AI easily.
diff --git a/src/content/partials/workers-vpc/create-tunnel-steps.mdx b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
index 9c0aef59ee08b46..4ec8b8731f765c2 100644
--- a/src/content/partials/workers-vpc/create-tunnel-steps.mdx
+++ b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
@@ -1,7 +1,7 @@
 ---
 {}
-
 ---
+
 import { Steps } from "~/components";
 
 <Steps>
diff --git a/src/content/partials/workers-vpc/required-roles.mdx b/src/content/partials/workers-vpc/required-roles.mdx
index 0af2217c4362e96..be0cad6ee37c062 100644
--- a/src/content/partials/workers-vpc/required-roles.mdx
+++ b/src/content/partials/workers-vpc/required-roles.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Workers VPC uses the following account roles:
diff --git a/src/content/partials/workers/ai-local-usage-charges.mdx b/src/content/partials/workers/ai-local-usage-charges.mdx
index 0747f627b173468..392a77552fc2ac9 100644
--- a/src/content/partials/workers/ai-local-usage-charges.mdx
+++ b/src/content/partials/workers/ai-local-usage-charges.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Workers AI local development usage charges]
 
-
 Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
 
-
 :::
diff --git a/src/content/partials/workers/c3-definition.mdx b/src/content/partials/workers/c3-definition.mdx
index 5cad05a047d4f02..06920a6667d56af 100644
--- a/src/content/partials/workers/c3-definition.mdx
+++ b/src/content/partials/workers/c3-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [C3 (create-cloudflare-cli)](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare) is a command-line tool designed to help you set up and deploy new applications to Cloudflare. In addition to speed, it leverages officially developed templates for Workers and framework-specific setup guides to ensure each new application that you set up follows Cloudflare and any third-party best practices for deployment on the Cloudflare network.
diff --git a/src/content/partials/workers/compute-per-request.mdx b/src/content/partials/workers/compute-per-request.mdx
index 78671c444b721be..3114c34331ad0a5 100644
--- a/src/content/partials/workers/compute-per-request.mdx
+++ b/src/content/partials/workers/compute-per-request.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 Most Workers are a variation on the default Workers flow:
 
diff --git a/src/content/partials/workers/content_and_contentoptions.mdx b/src/content/partials/workers/content_and_contentoptions.mdx
index 0cd4835706f96a9..d033ded8e7aef53 100644
--- a/src/content/partials/workers/content_and_contentoptions.mdx
+++ b/src/content/partials/workers/content_and_contentoptions.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Content and ContentOptions]
 
-
 Refer to [Global types](/workers/runtime-apis/html-rewriter/#global-types) for more information on `Content` and `ContentOptions`.
 
-
 :::
diff --git a/src/content/partials/workers/dash-creation-next-steps.mdx b/src/content/partials/workers/dash-creation-next-steps.mdx
index 3a4659d03dc4f7e..7e62d21c0a45c4d 100644
--- a/src/content/partials/workers/dash-creation-next-steps.mdx
+++ b/src/content/partials/workers/dash-creation-next-steps.mdx
@@ -13,6 +13,7 @@ Once you have created your Worker script, you can edit and deploy your Worker us
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your application.
 3. Select **Edit Code**.
 
diff --git a/src/content/partials/workers/env_and_secrets.mdx b/src/content/partials/workers/env_and_secrets.mdx
index 7efe87d33bc8f1b..60002bb1713e2d1 100644
--- a/src/content/partials/workers/env_and_secrets.mdx
+++ b/src/content/partials/workers/env_and_secrets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Compare secrets and environment variables
diff --git a/src/content/partials/workers/envvar-example.mdx b/src/content/partials/workers/envvar-example.mdx
index a3680630114446c..1a778eee6e6cefa 100644
--- a/src/content/partials/workers/envvar-example.mdx
+++ b/src/content/partials/workers/envvar-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/workers/fetch-html-example-js.mdx b/src/content/partials/workers/fetch-html-example-js.mdx
index 4e19efbae720a72..132f5b1a1063882 100644
--- a/src/content/partials/workers/fetch-html-example-js.mdx
+++ b/src/content/partials/workers/fetch-html-example-js.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    /**
-     * Replace `remote` with the host you wish to send requests to
-     */
-    const remote = "https://example.com";
+	async fetch(request) {
+		/**
+		 * Replace `remote` with the host you wish to send requests to
+		 */
+		const remote = "https://example.com";
 
-    return await fetch(remote, request);
-  },
+		return await fetch(remote, request);
+	},
 };
 ```
diff --git a/src/content/partials/workers/get-started-dash.mdx b/src/content/partials/workers/get-started-dash.mdx
index 63f3c464720f5e4..c04cc67a0123925 100644
--- a/src/content/partials/workers/get-started-dash.mdx
+++ b/src/content/partials/workers/get-started-dash.mdx
@@ -1,10 +1,11 @@
 ---
 {}
-
 ---
+
 import { DashButton } from "~/components";
 
 To create your first Worker using the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/partials/workers/isolate-cpu-flexibility.mdx b/src/content/partials/workers/isolate-cpu-flexibility.mdx
index 2b2c293912bb364..e8cd1b510fbfbe6 100644
--- a/src/content/partials/workers/isolate-cpu-flexibility.mdx
+++ b/src/content/partials/workers/isolate-cpu-flexibility.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Each [isolate](/workers/reference/how-workers-works/#isolates) has some built-in flexibility to allow for cases where your Worker infrequently runs over the configured limit. If your Worker starts hitting the limit consistently, its execution will be terminated according to the limit configured.
diff --git a/src/content/partials/workers/isolate-description.mdx b/src/content/partials/workers/isolate-description.mdx
index 48b5a2edfba0141..a70b5337ab358ab 100644
--- a/src/content/partials/workers/isolate-description.mdx
+++ b/src/content/partials/workers/isolate-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A single instance of the runtime can run hundreds or thousands of isolates, seamlessly switching between them. Each isolate's memory is completely isolated, so each piece of code is protected from other untrusted or user-written code on the runtime. Isolates are also designed to start very quickly. Instead of creating a virtual machine for each function, an isolate is created within an existing environment. This model eliminates the cold starts of the virtual machine model.
diff --git a/src/content/partials/workers/limits_increase.mdx b/src/content/partials/workers/limits_increase.mdx
index e5fa0351f7a8510..fd226c8f5cbf150 100644
--- a/src/content/partials/workers/limits_increase.mdx
+++ b/src/content/partials/workers/limits_increase.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Need a higher limit?]
 
-
 To request an adjustment to a limit, complete the [Limit Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). If the limit can be increased, Cloudflare will contact you with next steps.
 
-
 :::
diff --git a/src/content/partials/workers/nodejs-compat-howto.mdx b/src/content/partials/workers/nodejs-compat-howto.mdx
index 2dee652a3cb15d3..40e11bbb98811e6 100644
--- a/src/content/partials/workers/nodejs-compat-howto.mdx
+++ b/src/content/partials/workers/nodejs-compat-howto.mdx
@@ -1,11 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 To enable built-in Node.js APIs and polyfills, add the nodejs_compat compatibility flag to your [Wrangler configuration file](/workers/wrangler/configuration/). This also enables nodejs_compat_v2 as long as your compatibility date is 2024-09-23 or later. [Learn more about the Node.js compatibility flag and v2](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
 
-
 :::
diff --git a/src/content/partials/workers/playground-callout.mdx b/src/content/partials/workers/playground-callout.mdx
index 571ac3076e049f8..c854466893a08ef 100644
--- a/src/content/partials/workers/playground-callout.mdx
+++ b/src/content/partials/workers/playground-callout.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Try the Playground]
 
-
 The quickest way to experiment with Cloudflare Workers is in the [Playground](https://workers.cloudflare.com/playground). The Playground does not require any setup. It is an instant way to preview and test a Worker directly in the browser.
 
-
 :::
diff --git a/src/content/partials/workers/prereqs.mdx b/src/content/partials/workers/prereqs.mdx
index 70c0d166cb8f710..3d041a42f4203a5 100644
--- a/src/content/partials/workers/prereqs.mdx
+++ b/src/content/partials/workers/prereqs.mdx
@@ -1,13 +1,15 @@
 ---
 {}
-
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
 1. Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up/workers-and-pages).
 2. Install [`Node.js`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
 
 <Details header="Node.js version manager">
-Use a Node version manager like [Volta](https://volta.sh/) or [nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed later in this guide, requires a Node version of `16.17.0` or later.
+	Use a Node version manager like [Volta](https://volta.sh/) or
+	[nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change
+	Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed
+	later in this guide, requires a Node version of `16.17.0` or later.
 </Details>
diff --git a/src/content/partials/workers/redirect-example-js.mdx b/src/content/partials/workers/redirect-example-js.mdx
index b5b219d970896c9..9b764fa66e236ce 100644
--- a/src/content/partials/workers/redirect-example-js.mdx
+++ b/src/content/partials/workers/redirect-example-js.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const destinationURL = "https://example.com";
-    const statusCode = 301;
-    return Response.redirect(destinationURL, statusCode);
-  },
+	async fetch(request) {
+		const destinationURL = "https://example.com";
+		const statusCode = 301;
+		return Response.redirect(destinationURL, statusCode);
+	},
 };
 ```
diff --git a/src/content/partials/workers/remote-binding-note.mdx b/src/content/partials/workers/remote-binding-note.mdx
index f05321bd7cd36e3..14a8b741425af69 100644
--- a/src/content/partials/workers/remote-binding-note.mdx
+++ b/src/content/partials/workers/remote-binding-note.mdx
@@ -6,4 +6,4 @@
 
 To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. Learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/workers/request-dot-clone-warning.mdx b/src/content/partials/workers/request-dot-clone-warning.mdx
index 5e9640d3f34d8d2..5371525c77f704e 100644
--- a/src/content/partials/workers/request-dot-clone-warning.mdx
+++ b/src/content/partials/workers/request-dot-clone-warning.mdx
@@ -9,4 +9,4 @@ The body of a [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request
 To avoid errors, create a clone of the Request object with `request.clone()` for each subsequent attempt to access a Request's body.
 Keep in mind that Workers have a [memory limit of 128 MB per Worker](/workers/platform/limits/#memory) and loading particularly large files into a Worker's memory multiple times may reach this limit. To ensure memory usage does not reach this limit, consider using [Streams](/workers/runtime-apis/streams/).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/workers/respond-another-site-example-js.mdx b/src/content/partials/workers/respond-another-site-example-js.mdx
index 05c6f264b81aa7f..1e55c7a658919ba 100644
--- a/src/content/partials/workers/respond-another-site-example-js.mdx
+++ b/src/content/partials/workers/respond-another-site-example-js.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    function MethodNotAllowed(request) {
-      return new Response(`Method ${request.method} not allowed.`, {
-        status: 405,
-        headers: {
-          Allow: "GET",
-        },
-      });
-    }
-    // Only GET requests work with this proxy.
-    if (request.method !== "GET") return MethodNotAllowed(request);
-    return fetch(`https://example.com`);
-  },
+	async fetch(request) {
+		function MethodNotAllowed(request) {
+			return new Response(`Method ${request.method} not allowed.`, {
+				status: 405,
+				headers: {
+					Allow: "GET",
+				},
+			});
+		}
+		// Only GET requests work with this proxy.
+		if (request.method !== "GET") return MethodNotAllowed(request);
+		return fetch(`https://example.com`);
+	},
 };
 ```
diff --git a/src/content/partials/workers/return-html-example-js.mdx b/src/content/partials/workers/return-html-example-js.mdx
index 24bed7993c20042..41b5a8db682bcdc 100644
--- a/src/content/partials/workers/return-html-example-js.mdx
+++ b/src/content/partials/workers/return-html-example-js.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const html = `<!DOCTYPE html>
+	async fetch(request) {
+		const html = `<!DOCTYPE html>
 		<body>
 		  <h1>Hello World</h1>
 		  <p>This markup was generated by a Cloudflare Worker.</p>
 		</body>`;
 
-    return new Response(html, {
-      headers: {
-        "content-type": "text/html;charset=UTF-8",
-      },
-    });
-  },
+		return new Response(html, {
+			headers: {
+				"content-type": "text/html;charset=UTF-8",
+			},
+		});
+	},
 };
 ```
diff --git a/src/content/partials/workers/return-json-example-js.mdx b/src/content/partials/workers/return-json-example-js.mdx
index 5222c0a889a5073..e81939c499570ad 100644
--- a/src/content/partials/workers/return-json-example-js.mdx
+++ b/src/content/partials/workers/return-json-example-js.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const data = {
-      hello: "world",
-    };
+	async fetch(request) {
+		const data = {
+			hello: "world",
+		};
 
-    return Response.json(data);
-  },
+		return Response.json(data);
+	},
 };
 ```
diff --git a/src/content/partials/workers/service-binding-rpc-example.mdx b/src/content/partials/workers/service-binding-rpc-example.mdx
index 1f67ca0636f4dea..0e2f10a6dad4f77 100644
--- a/src/content/partials/workers/service-binding-rpc-example.mdx
+++ b/src/content/partials/workers/service-binding-rpc-example.mdx
@@ -77,7 +77,6 @@ Worker A can declare a [binding](/workers/runtime-apis/bindings) to Worker B:
 
 Making it possible for Worker A to call the `add()` method from Worker B:
 
-
 <Tabs syncKey="workersExamples">
 
 <TypeScriptExample omitTabs={true}>
diff --git a/src/content/partials/workers/storage-products-table.mdx b/src/content/partials/workers/storage-products-table.mdx
index 9b832c39da70b20..47d0a3281d70912 100644
--- a/src/content/partials/workers/storage-products-table.mdx
+++ b/src/content/partials/workers/storage-products-table.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-| Use-case | Product                                          | Ideal for                                                                                                               |
-| ------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
-| Key-value storage | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                             |
-| Object storage / blob storage | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.         |
-| Accelerate a Postgres or MySQL database | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                                            |
-| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage.  |
-| Lightweight SQL database | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                            |
-| Task processing, batching and messaging | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks. |
-| Vector search & embeddings queries | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.  |
-| Streaming ingestion | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying |
-| Time-series metrics | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL. |
\ No newline at end of file
+| Use-case                                  | Product                                          | Ideal for                                                                                                                                              |
+| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Key-value storage                         | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                                                            |
+| Object storage / blob storage             | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.                                        |
+| Accelerate a Postgres or MySQL database   | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                               |
+| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage. |
+| Lightweight SQL database                  | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                                                           |
+| Task processing, batching and messaging   | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks.                                                          |
+| Vector search & embeddings queries        | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.                           |
+| Streaming ingestion                       | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying                         |
+| Time-series metrics                       | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL.                                |
diff --git a/src/content/partials/workers/testing-pages-functions.mdx b/src/content/partials/workers/testing-pages-functions.mdx
index 568cbc85bd23a01..2d921130e88652f 100644
--- a/src/content/partials/workers/testing-pages-functions.mdx
+++ b/src/content/partials/workers/testing-pages-functions.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Pages Functions]
 
-
 The content described on this page is also applicable to [Pages Functions](/pages/functions/). Pages Functions are Cloudflare Workers and can be thought of synonymously with Workers in this context.
 
-
 :::
diff --git a/src/content/partials/workers/tutorials-before-you-start.mdx b/src/content/partials/workers/tutorials-before-you-start.mdx
index b33c0af2815ddef..bb2f002bb183c96 100644
--- a/src/content/partials/workers/tutorials-before-you-start.mdx
+++ b/src/content/partials/workers/tutorials-before-you-start.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Before you start
diff --git a/src/content/partials/workers/workers_logs_pricing.mdx b/src/content/partials/workers/workers_logs_pricing.mdx
index 8772eec1debdf90..7e8c152265137aa 100644
--- a/src/content/partials/workers/workers_logs_pricing.mdx
+++ b/src/content/partials/workers/workers_logs_pricing.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Workers Logs is included in both the Free and Paid [Workers plans](/workers/platform/pricing/).
 
-|                    | Log Events Written                                                 | Retention  |
-| ------------------ | ------------------------------------------------------------------ | ---------- |
-| **Workers Free**   | 200,000 per day                                                    | 3 Days     |
-| **Workers Paid**   | 20 million included per month <br /> +$0.60 per additional million | 7 Days     |
+|                  | Log Events Written                                                 | Retention |
+| ---------------- | ------------------------------------------------------------------ | --------- |
+| **Workers Free** | 200,000 per day                                                    | 3 Days    |
+| **Workers Paid** | 20 million included per month <br /> +$0.60 per additional million | 7 Days    |
diff --git a/src/content/partials/workers/wrangler-commands/containers.mdx b/src/content/partials/workers/wrangler-commands/containers.mdx
index e04e280d72c1783..aa5f7677a4557ba 100644
--- a/src/content/partials/workers/wrangler-commands/containers.mdx
+++ b/src/content/partials/workers/wrangler-commands/containers.mdx
@@ -202,14 +202,14 @@ wrangler containers instances 12345678-abcd-1234-abcd-123456789abc --json
 
 ```json output
 [
-  {
-    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
-    "name": "worker-12",
-    "state": "running",
-    "location": "sfo06",
-    "version": 3,
-    "created": "2025-06-01T12:00:00Z"
-  }
+	{
+		"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+		"name": "worker-12",
+		"state": "running",
+		"location": "sfo06",
+		"version": 3,
+		"created": "2025-06-01T12:00:00Z"
+	}
 ]
 ```
 
diff --git a/src/content/partials/workers/wrangler-commands/r2-sql.mdx b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
index 17cd10b4c69f8c1..5c20b7b51c03454 100644
--- a/src/content/partials/workers/wrangler-commands/r2-sql.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
@@ -2,7 +2,14 @@
 {}
 ---
 
-import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand, WranglerNamespace } from "~/components";
+import {
+	Render,
+	AnchorHeading,
+	Type,
+	MetaInfo,
+	WranglerCommand,
+	WranglerNamespace,
+} from "~/components";
 
 :::note
 
@@ -10,4 +17,4 @@ R2 SQL is currently in open beta. Report R2 SQL bugs in [GitHub](https://github.
 
 :::
 
-<WranglerCommand command="r2 sql query" headingLevel={3} />
\ No newline at end of file
+<WranglerCommand command="r2 sql query" headingLevel={3} />
diff --git a/src/content/partials/workers/wrangler-commands/r2.mdx b/src/content/partials/workers/wrangler-commands/r2.mdx
index 3046ac2f72125bb..692fb87d223e3e1 100644
--- a/src/content/partials/workers/wrangler-commands/r2.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2.mdx
@@ -2,7 +2,13 @@
 {}
 ---
 
-import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand } from "~/components";
+import {
+	Render,
+	AnchorHeading,
+	Type,
+	MetaInfo,
+	WranglerCommand,
+} from "~/components";
 
 ## `r2 bucket`
 
@@ -13,21 +19,24 @@ Interact with buckets in an R2 store.
 The `r2 bucket` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 bucket create" headingLevel={3}/>
+<WranglerCommand command="r2 bucket create" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket info" headingLevel={3}/>
+<WranglerCommand command="r2 bucket info" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog disable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog compaction enable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog compaction enable"
+	headingLevel={3}
+/>
 
 Examples:
 
@@ -39,7 +48,10 @@ npx wrangler r2 bucket catalog compaction enable my-bucket --token <TOKEN>
 npx wrangler r2 bucket catalog compaction enable my-bucket my-namespace my-table --target-size 256
 ```
 
-<WranglerCommand command="r2 bucket catalog compaction disable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog compaction disable"
+	headingLevel={3}
+/>
 
 Examples:
 
@@ -50,60 +62,66 @@ npx wrangler r2 bucket catalog compaction disable my-bucket
 # Disable table-level compaction
 npx wrangler r2 bucket catalog compaction disable my-bucket my-namespace my-table
 ```
-<WranglerCommand command="r2 bucket catalog snapshot-expiration enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog snapshot-expiration disable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog snapshot-expiration enable"
+	headingLevel={3}
+/>
 
-<WranglerCommand command="r2 bucket cors set" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog snapshot-expiration disable"
+	headingLevel={3}
+/>
 
-<WranglerCommand command="r2 bucket cors delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket cors list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain update" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain update" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock set" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification create" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification create" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket sippy enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket sippy disable" headingLevel={3} />
 
+<WranglerCommand command="r2 bucket sippy get" headingLevel={3} />
 
 ## `r2 object`
 
@@ -114,8 +132,8 @@ Interact with R2 objects.
 The `r2 object` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 object get" headingLevel={3}/>
+<WranglerCommand command="r2 object get" headingLevel={3} />
 
-<WranglerCommand command="r2 object put" headingLevel={3}/>
+<WranglerCommand command="r2 object put" headingLevel={3} />
 
-<WranglerCommand command="r2 object delete" headingLevel={3}/>
\ No newline at end of file
+<WranglerCommand command="r2 object delete" headingLevel={3} />
diff --git a/src/content/partials/workflows/workflows-type-parameters.mdx b/src/content/partials/workflows/workflows-type-parameters.mdx
index 0ad91e5f88a4fcf..37e0134270468b8 100644
--- a/src/content/partials/workflows/workflows-type-parameters.mdx
+++ b/src/content/partials/workflows/workflows-type-parameters.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::caution
 
diff --git a/src/content/partials/zaraz/zaraz-definition.mdx b/src/content/partials/zaraz/zaraz-definition.mdx
index b17ee4fa2792f6f..2b5e8f884cd31f7 100644
--- a/src/content/partials/zaraz/zaraz-definition.mdx
+++ b/src/content/partials/zaraz/zaraz-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Zaraz gives you complete control over third-party tools and services for your website, and allows you to offload them to Cloudflare's edge, improving the speed and security of your website. With Cloudflare Zaraz you can load tools such as analytics tools, advertising pixels and scripts, chatbots, marketing automation tools, and more, in the most optimized way.
diff --git a/src/pages/agent-setup/index.astro b/src/pages/agent-setup/index.astro
index 9c6aa0f8bc91720..e5e4a7adc39235c 100644
--- a/src/pages/agent-setup/index.astro
+++ b/src/pages/agent-setup/index.astro
@@ -24,29 +24,59 @@ const props = {
 
 <StarlightPage {...props}>
 	<p class="agent-setup-lede">
-		Install an agent of your choice, connect Cloudflare <a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">Skills &nearr;</a> and <a href="https://blog.cloudflare.com/code-mode-mcp/" target="_blank" rel="noopener noreferrer">Code Mode API &nearr;</a> and <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific &nearr;</a> MCP servers, and start deploying to Cloudflare from your editor or terminal.
+		Install an agent of your choice, connect Cloudflare <a
+			href="https://github.com/cloudflare/skills"
+			target="_blank"
+			rel="noopener noreferrer">Skills &nearr;</a
+		> and <a
+			href="https://blog.cloudflare.com/code-mode-mcp/"
+			target="_blank"
+			rel="noopener noreferrer">Code Mode API &nearr;</a
+		> and <a
+			href="https://github.com/cloudflare/mcp-server-cloudflare"
+			target="_blank"
+			rel="noopener noreferrer">domain-specific &nearr;</a
+		> MCP servers, and start deploying to Cloudflare from your editor or terminal.
 	</p>
 
 	<div class="agent-setup-paths not-content">
 		<!-- Left: quick path -->
-		<div class="agent-setup-path agent-setup-path--quick" style="flex-basis: 60%;">
+		<div
+			class="agent-setup-path agent-setup-path--quick"
+			style="flex-basis: 60%;"
+		>
 			<p class="agent-setup-path-eyebrow">Quick setup</p>
 			<p class="agent-setup-path-title">Already have an agent?</p>
-			<p class="agent-setup-path-desc">Paste this into any AI coding agent to install Cloudflare agent tooling in one step.</p>
-			<PromptCopyBlock text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md" hideLabel />
+			<p class="agent-setup-path-desc">
+				Paste this into any AI coding agent to install Cloudflare agent tooling
+				in one step.
+			</p>
+			<PromptCopyBlock
+				text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md"
+				hideLabel
+			/>
 		</div>
 		<!-- Right: manual path -->
 		<div class="agent-setup-path agent-setup-path--manual">
 			<p class="agent-setup-path-eyebrow">Manual setup</p>
 			<p class="agent-setup-path-title">New to AI agents?</p>
-			<p class="agent-setup-path-desc">Pick an agent, follow step-by-step setup instructions, compare capabilities, and learn about the Cloudflare tools available to you.</p>
-			<a href="#pick-your-agent" class="agent-setup-path-cta">Browse agents &darr;</a>
+			<p class="agent-setup-path-desc">
+				Pick an agent, follow step-by-step setup instructions, compare
+				capabilities, and learn about the Cloudflare tools available to you.
+			</p>
+			<a href="#pick-your-agent" class="agent-setup-path-cta"
+				>Browse agents &darr;</a
+			>
 		</div>
 	</div>
 
 	<hr />
 
-	<div class="agent-setup-section-header" style="margin-top: 3.25rem;" id="pick-your-agent">
+	<div
+		class="agent-setup-section-header"
+		style="margin-top: 3.25rem;"
+		id="pick-your-agent"
+	>
 		<h2>Pick your agent</h2>
 		<p>Select an agent to get step-by-step setup instructions.</p>
 	</div>
@@ -108,10 +138,6 @@ const props = {
 		border-color: var(--color-cl1-gray-2);
 	}
 
-
-
-
-
 	.agent-setup-path-eyebrow {
 		font-size: 0.75rem;
 		font-weight: 700;
@@ -152,5 +178,4 @@ const props = {
 		text-decoration: underline;
 		text-underline-offset: 2px;
 	}
-
 </style>
diff --git a/src/pages/plans.astro b/src/pages/plans.astro
index 38f964ff6dac9d9..e46fb3945ae4d16 100644
--- a/src/pages/plans.astro
+++ b/src/pages/plans.astro
@@ -120,8 +120,8 @@ import { ProductFeatures } from "~/components";
 			<strong>Developer products</strong>: Refer to the <a
 				href="https://www.cloudflare.com/plans/developer-platform/"
 				>Developer Platform pricing page</a
-			> or individual <a href="/directory/">product docs</a> to learn more about
-			plans and pricing.
+			> or individual <a href="/directory/">product docs</a> to learn more about plans
+			and pricing.
 		</li>
 		<li>
 			<strong>Zero Trust products</strong>: Refer to the <a

From 0c50ffa05a96c48067721cbe0c1d637885537479 Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 06:27:16 +0000
Subject: [PATCH 4/8] Revert "Applied 10 edits + changelog entry, validated"

This reverts commit b11ab7c8ad455913644e8b2c0f3dff0125b1a955.
---
 .agents/references/procedures.md              |   20 +-
 .agents/skills/dependabot-review/SKILL.md     |   18 +-
 .agents/skills/docs-review/SKILL.md           |   26 +-
 .agents/skills/eli5/SKILL.md                  |   45 +-
 .../internal-dns/index.eli5.mdx               |    1 -
 .../eli5/references/EXAMPLES_REFERENCE.md     |  517 ++++----
 .../eli5/references/content-type-guide.md     |  105 +-
 .../skills/eli5/references/pattern-library.md |  202 ++-
 .github/review-template.md                    |    3 +-
 .opencode/command/styleguide.md               |    1 -
 .windsurf/rules/general-rules.md              |    2 +-
 CONTRIBUTING.md                               |    3 +-
 MIGRATION.md                                  |    4 +-
 src/components/AutoconfigDiagram.astro        |  157 +--
 src/components/ComponentUsage.astro           |    3 +-
 src/components/FeatureTable.astro             |   44 +-
 src/components/LayerCard.astro                |    8 +-
 src/components/LlmsTxtDirective.astro         |    6 +-
 src/components/PagesBuildPresetsTable.astro   |   15 +-
 src/components/ProductReleaseNotes.astro      |    7 +-
 src/components/R2LocalUploadsdiagram.astro    |  404 ++----
 src/components/WranglerCommand.astro          |    2 +-
 src/components/WranglerConfig.astro           |    4 +-
 src/components/WranglerNamespace.astro        |    2 +-
 .../agent-setup/AgentComparison.astro         |   12 +-
 src/components/agent-setup/AgentHeader.astro  |    4 +-
 src/components/agent-setup/AgentPrimer.astro  |    6 +-
 .../agent-setup/BuildAgentsCallout.astro      |    4 +-
 .../agent-setup/CloudflareToolsBanner.astro   |   35 +-
 .../agent-setup/PlatformAccessSection.astro   |    7 +-
 src/components/ai-gateway/code-examples.astro |  329 ++---
 src/components/changelog/Pagination.astro     |    7 +-
 src/components/models/CopyableCode.astro      |   11 +-
 src/components/models/ModelDetailPage.astro   |  220 +---
 src/components/models/SchemaDisplay.astro     |   16 +-
 src/components/models/code/DeepgramFlux.astro |   15 +-
 .../OpenAIResponsesTextGenerationCode.astro   |    4 +-
 src/components/overrides/Page.astro           |    6 +-
 ...ss-Supports-Customer-Metadata-Boundary.mdx |    4 +-
 .../access/2025-08-26-mcp-server-portals.mdx  |    1 +
 ...-17-clientless-access-for-private-apps.mdx |    4 +-
 .../2025-12-22-agents-sdk-ai-sdk-v6.mdx       |   40 +-
 .../2026-04-15-agentlee-writeops-genui.mdx    |   14 +-
 .../ai-search/2025-09-19-autorag-metrics.mdx  |    2 +-
 .../2025-09-25-ai-search-more-models.mdx      |   31 +-
 ...add-extra-headers-for-website-crawling.mdx |    7 +-
 ...2026-04-16-ai-search-namespace-binding.mdx |    4 +-
 .../2025-10-01-confidence-intervals.mdx       |    8 +-
 .../2026-02-18-cfworker-server-timing.mdx     |    8 +-
 .../2026-03-09-vulnerability-scanner.mdx      |    4 +-
 .../2026-05-19-event-subscriptions.mdx        |   10 +-
 .../2024-09-05-cache-rules-templates.mdx      |    1 +
 .../2024-11-07-shard-cache-by-cache-key.mdx   |   16 +-
 ...-11-07-cache-keys-for-cloudflare-trace.mdx |   26 +-
 ...1-25-audit-logs-for-cache-purge-events.mdx |   44 +-
 .../cache/2026-03-24-cache-response-rules.mdx |    2 +-
 .../changelog/casb/2025-10-28-casb-roles.mdx  |    4 +-
 .../2025-08-29-warp-AI-diag-analyzer.mdx      |    1 +
 ...nabled-search-for-zero-trust-dashboard.mdx |    4 +-
 ...for-supported-cloudflare-one-resources.mdx |   10 +-
 .../cloudflare-one/new-applications-71825.mdx |    2 +-
 ...-01-27-configure-cloudflare-source-ips.mdx |    2 +-
 ...025-10-01-new-container-instance-types.mdx |    2 +-
 .../containers/2025-11-21-new-cpu-pricing.mdx |    6 +-
 ...02-25-higher-container-resource-limits.mdx |    2 +-
 .../2026-03-24-docker-hub-images.mdx          |    2 +-
 .../2026-04-05-regional-placement.mdx         |    8 +-
 ...4-13-sandbox-outbound-workers-tls-auth.mdx |    2 +-
 .../2026-05-12-ssh-enabled-by-default.mdx     |    2 +-
 .../dex/2025-11-12-dex-logpush-jobs.mdx       |    4 +-
 .../dex/2026-02-19-dex-supports-cmb-eu.mdx    |    1 +
 ...04-28-dex-internet-outage-notification.mdx |    2 +-
 .../dex/2026-04-28-dex-speed-test.mdx         |    3 +-
 .../dex/2026-04-29-dex-tests-to-auth.mdx      |    3 +-
 .../2025-04-14-account-level-dlp-settings.mdx |    1 -
 .../dlp/2025-07-17-document-matching.mdx      |    5 +-
 .../dlp/2025-08-25-ai-prompt-protection.mdx   |   12 +-
 ...25-har-file-detection-and-sanitization.mdx |    2 +-
 ...-04-14-cloudflare-api-token-detections.mdx |   16 +-
 .../dlp/2026-04-28-pii-record-profile.mdx     |    2 +-
 .../dns/2026-03-31-internal-dns-open-beta.mdx |    1 -
 .../dns/2026-04-28-enforce-dns-only.mdx       |    1 -
 ...2025-08-21-durable-objects-get-by-name.mdx |    8 +-
 ...2025-10-16-durable-objects-data-studio.mdx |    2 +-
 ...durable-objects-sqlite-storage-billing.mdx |    3 +-
 .../2026-03-15-durable-object-id-name.mdx     |   18 +-
 .../2025-07-21-subaddressing.mdx              |    2 +-
 .../2024-12-19-escalate-user-submissions.mdx  |    2 +-
 .../2025-10-16-on-demand-security-report.mdx  |    1 +
 ...adjustment-to-final-disposition-column.mdx |    3 +-
 ...25-12-03-submission-terminology-update.mdx |   11 +-
 ...anced-visibility-post-delivery-actions.mdx |    9 +-
 ...ed-accessibility-search-for-monitoring.mdx |   26 +-
 ...6-03-15-infinite-paging-investigations.mdx |   12 +-
 ...2026-04-06-dane-support-mx-deployments.mdx |   12 +-
 .../2026-04-07-triage-status-tracking.mdx     |    2 -
 ...5-06-cloudy-summaries-in-phishnet_o365.mdx |    1 -
 .../2025-06-23-user-groups-ga.mdx             |    4 +-
 .../2025-09-03-rate-limiting-improvement.mdx  |   21 +-
 ...two-factor-authentication-backup-codes.mdx |    3 +-
 .../2025-09-25-sign-in-with-github.mdx        |    3 +-
 .../fundamentals/2025-10-01-md-returned.mdx   |    2 +-
 .../2025-10-14-sso-self-service-ux.mdx        |    1 +
 .../fundamentals/2025-10-30-email-2FA.mdx     |    6 +-
 ...5-10-30-member-management-improvements.mdx |   14 +-
 .../2026-01-23-New-2FA-Experience.mdx         |    9 +-
 .../2026-02-12-markdown-for-agents.mdx        |    3 +-
 ...02-16-markdown-for-agents-improvements.mdx |    2 +-
 ...json-rfc9457-responses-for-1xxx-errors.mdx |    1 -
 ...-12-retry-after-header-for-1xxx-errors.mdx |   19 +-
 .../2026-03-17-scim-authentik-support.mdx     |    2 +-
 .../2026-03-18-scim-audit-logging.mdx         |    4 +-
 .../2026-04-06-organizations-public-beta.mdx  |    2 +-
 .../2026-04-10-secret-scanning-support.mdx    |    2 +-
 .../2026-04-14-oauth-consent-and-revoke.mdx   |   22 +-
 ...27-structured-responses-for-5xx-errors.mdx |    1 -
 .../2026-05-04-keyboard-shortcuts.mdx         |   54 +-
 ...025-07-24-HTTP-Inspection-on-all-ports.mdx |    4 +-
 ...-07-28-Spam-domain-category-introduced.mdx |   12 +-
 ...08-15-gemini-application-replaces-bard.mdx |    3 +-
 .../2025-10-10-new-domain-categories.mdx      |   10 +-
 ...-11-06-Applications-recategorised-plan.mdx |    6 +-
 ...02-27-new-protocol-detection-protocols.mdx |   14 +-
 .../Gateway-application-categories-added.mdx  |    4 +-
 ...4-hyperdrive-remote-database-local-dev.mdx |   14 +-
 src/content/changelog/images/heic-support.mdx |    1 -
 ...2025-08-22-kv-performance-improvements.mdx |    2 +
 .../2025-06-04-account-load-balancing-ui.mdx  |    3 +-
 .../2025-07-09-usage-tracking.mdx             |    2 +-
 .../2025-08-15-extended-retention.mdx         |    2 +-
 .../2025-09-03-log-headers-and-cookies.mdx    |    2 +
 .../2025-09-11-contextual-pivots.mdx          |    4 +-
 .../2025-09-11-new-results-table-view.mdx     |    4 +-
 .../2025-11-04-query-cancellation.mdx         |    2 +-
 .../2025-11-11-resize-sql-window.mdx          |    2 +-
 .../2025-11-13-fixed-custom-date.mdx          |    2 +-
 .../log-explorer/2025-11-13-new-datasets.mdx  |    5 +-
 .../2026-03-11-ingest-field-selection.mdx     |   20 +-
 .../logs/2024-10-08-new-gateway-fields.mdx    |    2 +-
 .../logs/2026-03-09-log-fields-updated.mdx    |    1 +
 ...26-04-20-pipelines-logpush-destination.mdx |    2 +-
 ...2026-04-21-logpush-subrequests-merging.mdx |    4 +-
 ...-03-24-interconnects-navigation-update.mdx |    2 +-
 .../pages/2025-05-30-pages-build-image-v3.mdx |    2 +-
 .../queues/2025-03-25-pause-purge-queues.mdx  |    8 +-
 .../2025-04-17-pull-consumer-limits.mdx       |    3 -
 .../2025-05-09-publish-to-queues-via-http.mdx |    2 +-
 .../queues/2025-08-19-event-subscriptions.mdx |   26 +-
 ...2025-09-25-announcing-r2-sql-open-beta.mdx |    2 +-
 ...ql-functions-expressions-complex-types.mdx |    1 +
 ...0-r2-sql-json-functions-explain-format.mdx |    2 -
 .../radar/2025-08-04-radar-ct-insights.mdx    |    2 +-
 .../radar/2025-09-29-radar-regional-data.mdx  |    2 +-
 .../radar/2026-02-25-radar-aspa-insights.mdx  |    2 +-
 .../2026-04-01-radar-routing-section.mdx      |    2 +-
 ...2026-05-28-realtimekit-track-recording.mdx |   36 -
 .../2026-1-15-crowdstrike-score.mdx           |    1 -
 .../2025-10-30-tcp-rtt-and-tcp-fields.mdx     |    8 +-
 .../rules/2026-01-12-dma-metro-code-field.mdx |    4 +-
 .../rules/2026-01-20-array-map-functions.mdx  |   12 +-
 .../2026-01-27-body-buffering-settings.mdx    |   26 +-
 .../rules/2026-03-18-worker-timing-field.mdx  |    4 +-
 .../rules/2026-03-25-rfc9440-mtls-fields.mdx  |    2 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   12 +-
 ...20-cloudflare-typescript-v6.0.0-beta.1.mdx |   70 +-
 ...-02-13-cloudflare-python-v5.0.0-beta.1.mdx |   13 +-
 .../2025-07-18-brand-protection-api.mdx       |   14 +-
 .../2025-10-27-RFI-Tokens-in-Dash.mdx         |    2 +-
 ...protection-logo-dashboard-report-abuse.mdx |    4 +-
 ...Threat-Events-now-show-events-insights.mdx |    6 +-
 ...-01-14-Download-URL-Scanner-Report-PDF.mdx |    8 +-
 .../2026-02-19-threat-events-graphs.mdx       |    1 -
 ...026-02-23-Saved-views-in-threat-events.mdx |    5 +-
 .../2026-04-08-threat-events-notification.mdx |   20 +-
 .../2026-05-07-CSV-export-for-RFIs.mdx        |    1 -
 ...-12-URL-scanner-report-agent-readiness.mdx |   17 +-
 ...archive-and-audit-security-action-items.md |    5 +-
 .../2025-08-25-secrets-store-ai-gateway.mdx   |   20 +-
 ...07-22-media-transformations-audio-mode.mdx |    2 +-
 .../2026-04-06-redesigned-support-portal.mdx  |    1 -
 .../2026-04-28-direct-support-navigation.mdx  |    4 +-
 .../2025-02-03-terraform-v5-provider.mdx      |    6 +-
 .../2025-05-19-terraform-v5.5.0-provider.mdx  |   13 +-
 .../2025-06-17-terraform-v5.6.0-provider.mdx  |    3 +-
 .../2025-07-11-terraform-v5.7.0-provider.mdx  |    3 +-
 .../2025-08-01-terraform-v5.8.2-provider.mdx  |    6 +-
 .../2025-08-15-terraform-v5.8.4-provider.mdx  |    6 +-
 .../2025-08-29-terrform-v5.9-provider.mdx     |    3 +-
 .../2025-11-20-terraform-v5.13.0-provider.mdx |   63 +-
 .../2025-12-05-terraform-v5.14.0-provider.mdx |   22 +-
 .../2025-12-19-terraform-v5.15.0-provider.mdx |   36 +-
 .../2026-01-20-terraform-v5.16.0-provider.mdx |   55 +-
 .../2026-02-12-terraform-v5.17.0-provider.mdx |   91 +-
 .../2026-04-24-terraform-v5.19.0-provider.mdx |    1 -
 .../2026-04-24-tf-migrate-tool-released.mdx   |    6 +-
 .../tunnel/2025-07-15-udp-improvements.mdx    |    3 +-
 ...el-networks-list-endpoints-new-default.mdx |   28 +-
 .../2025-09-18-tunnel-hostname-routing.mdx    |    3 +-
 ...2026-01-15-warp-connector-ping-support.mdx |    2 +-
 .../changelog/waf/2025-07-14-waf-release.mdx  |    1 +
 .../changelog/waf/2025-07-21-emergency.mdx    |   30 +-
 .../changelog/waf/2025-07-28-waf-release.mdx  |   11 +-
 .../changelog/waf/2025-08-04-waf-release.mdx  |  207 ++-
 .../waf/2025-08-07-emergency-waf-release.mdx  |   75 +-
 .../changelog/waf/2025-08-11-waf-release.mdx  |  460 +++----
 .../changelog/waf/2025-08-18-waf-release.mdx  |  275 ++--
 .../changelog/waf/2025-08-25-waf-release.mdx  |   98 +-
 .../waf/2025-08-29-emergency-waf-release.mdx  |   72 +-
 .../changelog/waf/2025-09-01-waf-release.mdx  |   78 +-
 .../waf/2025-09-04-emergency-waf-release.mdx  |   95 +-
 .../changelog/waf/2025-09-08-waf-release.mdx  |  250 ++--
 .../changelog/waf/2025-09-15-waf-release.mdx  |  100 +-
 .../changelog/waf/2025-09-22-waf-release.mdx  |  221 ++--
 .../waf/2025-09-24-emergency-waf-release.mdx  |   52 +-
 .../changelog/waf/2025-09-26-waf-release.mdx  |  268 ++--
 .../waf/2025-09-28-emergency-waf-release.mdx  |   80 +-
 .../changelog/waf/2025-09-29-waf-release.mdx  |  135 +-
 .../changelog/waf/2025-10-03-waf-release.mdx  |  488 +++----
 .../changelog/waf/2025-10-06-waf-release.mdx  |  220 ++--
 .../waf/2025-10-07-emergency-waf-release.mdx  |   55 +-
 .../waf/2025-10-17-emergency-waf-release.mdx  |   82 +-
 .../changelog/waf/2025-10-20-waf-release.mdx  |   16 +-
 .../waf/2025-10-23-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-24-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-30-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-11-05-emergency-waf-release.mdx  |   50 +-
 .../changelog/waf/2025-11-10-waf-release.mdx  |    4 +-
 .../changelog/waf/2025-11-17-waf-release.mdx  |    2 +-
 .../waf/2025-11-21-emergency-waf-release.mdx  |    2 +-
 .../changelog/waf/2025-11-24-waf-release.mdx  |   16 +-
 .../changelog/waf/2025-12-01-waf-release.mdx  |    9 +-
 .../waf/2025-12-02-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-03-emergency-waf-release.mdx  |    3 +-
 .../waf/2025-12-10-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-11-emergency-waf-release.mdx  |   14 +-
 .../changelog/waf/2025-12-18-waf-release.mdx  |  225 ++--
 .../changelog/waf/2026-01-12-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-15-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-20-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-26-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-02-02-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-03-02-waf-release.mdx  |    7 +-
 .../waf/2026-03-12-emergency-waf-release.mdx  |    6 +-
 .../changelog/waf/2026-03-23-waf-release.mdx  |  104 +-
 .../changelog/waf/2026-03-30-waf-release.mdx  |  116 +-
 .../changelog/waf/2026-04-15-waf-release.mdx  |  144 +--
 .../changelog/waf/2026-04-21-waf-release.mdx  |  339 ++---
 .../changelog/waf/2026-04-27-waf-release.mdx  |  343 +++--
 .../waf/2026-05-07-emergency-waf-release.mdx  |   12 +-
 .../changelog/waf/2026-05-11-waf-release.mdx  |    9 +-
 .../waf/2026-05-15-emergency-waf-release.mdx  |   16 +-
 .../changelog/waf/2026-05-20-waf-release.mdx  |   12 +-
 .../2026-04-30-rum-navigation-types.mdx       |    4 +-
 .../2025-08-05-openai-open-models.mdx         |    5 +-
 .../workers-ai/2025-08-27-partner-models.mdx  |    3 +-
 .../workers-ai/2025-09-05-embeddinggemma.mdx  |    3 +-
 .../workers-vpc/2025-09-25-workers-vpc.mdx    |    4 +-
 ...-07-new-ways-to-get-started-on-workers.mdx |   12 +-
 .../workers/2025-03-25-higher-cpu-limits.mdx  |    2 +-
 ...2025-04-08-deploy-to-cloudflare-button.mdx |   18 +-
 .../workers/2025-04-09-qb-workers-logs-ga.mdx |    4 +-
 ...2025-04-22-python-worker-cron-triggers.mdx |    2 +-
 ...025-05-14-python-worker-durable-object.mdx |    2 +-
 .../workers/2025-06-05-open-next-size.mdx     |    2 +-
 .../2025-07-23-workers-preview-urls.mdx       |   12 +-
 .../2025-08-04-builds-increased-disk-size.mdx |    8 +-
 ...08-08-add-waituntil-cloudflare-workers.mdx |    2 +-
 ...port-long-branch-names-preview-aliases.mdx |    4 +-
 .../workers/2025-08-11-messagechannel.mdx     |   16 +-
 .../2025-08-14-new-python-handlers.mdx        |    2 +-
 ...workers-terraform-and-sdk-improvements.mdx |   39 +-
 .../2025-08-15-static-assets-redirect-url.mdx |    6 +-
 ...5-08-19-improved-wrangler-error-screen.mdx |    4 +-
 .../workers/2025-09-03-new-workers-api.mdx    |   86 +-
 .../2025-09-07-builds-increased-cpu-paid.mdx  |   17 +-
 ...2025-09-09-interactive-wrangler-assets.mdx |    5 +-
 ...025-09-10-built-with-cloudflare-button.mdx |    2 +-
 ...09-11-increased-version-rollback-limit.mdx |    9 +-
 .../2025-09-17-update-preview-url-setting.mdx |    6 +-
 .../2025-09-19-ratelimit-workers-ga.mdx       |    4 +-
 ...dev-multi-config-cross-command-support.mdx |   19 +-
 ...9-26-analytics-engine-sql-enhancements.mdx |   21 +-
 .../workers/2025-09-26-ctx-exports.md         |   16 +-
 .../workers/2025-10-09-assets-terraform.mdx   |   10 +-
 .../2025-10-09-workflows-terraform.mdx        |    8 +-
 ...025-10-23-preview-url-default-behavior.mdx |    7 +-
 ...-10-24-automatic-resource-provisioning.mdx |    2 +-
 .../workers/2025-10-30-builds-preview.mdx     |    8 +-
 .../2025-11-09-cloudflare-env-variable.mdx    |    1 -
 ...lytics-engine-further-sql-enhancements.mdx |   12 +-
 ...25-12-01-build-image-policies-dev-plat.mdx |    2 +-
 ...5-12-08-python-cold-start-improvements.mdx |   10 +-
 .../workers/2025-12-08-python-pywrangler.mdx  |    1 +
 .../2025-12-08-vite-optional-config.mdx       |    2 +-
 .../2025-12-08-vite-programmatic-config.mdx   |    2 +-
 .../2025-12-16-vitest-ctx-exports-support.mdx |   10 +-
 ...2025-12-19-tanstack-start-prerendering.mdx |   20 +-
 .../2026-02-15-workers-best-practices.mdx     |    1 -
 .../2026-03-27-rfc9440-mtls-fields.mdx        |   45 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   34 +-
 ...026-05-06-react-nextjs-vulnerabilities.mdx |    2 +-
 .../2025-01-15-workflows-more-steps.mdx       |    6 +-
 .../workflows/2025-10-28-raising-limits.mdx   |    6 +-
 .../2026-03-23-local-dev-instance-methods.mdx |    2 +-
 .../2026-05-01-dynamic-workflows.mdx          |    6 +-
 .../compatibility-flags/allow-custom-ports.md |    1 -
 .../enable-nodejs-http-modules.md             |    8 +-
 .../enable-nodejs-http-server-modules.md      |    8 +-
 .../fetcher-no-get-put-delete.md              |    1 +
 .../compatibility-flags/js-weak-refs.md       |    3 +-
 .../new-url-parser-implementation.md          |    8 +-
 .../compatibility-flags/nodejs-compat.md      |   12 +-
 .../queue-consumer-no-wait-waituntil.md       |   29 +-
 .../queues-json-messages.md                   |    2 +-
 .../compatibility-flags/request-signal.md     |    2 +-
 .../streams-byob-reader-detaches-buffer.md    |   12 +-
 .../compatibility-flags/strict-crypto.md      |    1 -
 .../throw-on-unrecognized-import-assertion.md |    1 +
 .../compatibility-flags/to-string-tag.md      |    2 +-
 .../urlsearchparams-deletehasvalue.md         |    6 +-
 .../web-socket-auto-reply-to-close.md         |   38 +-
 .../web-socket-compression.md                 |    2 +-
 .../websocket-standard-binary-type.md         |    4 +-
 ...ws-preserve-non-retryable-error-message.md |   14 +-
 .../mpp/charge-for-http-content.mdx           |   10 +-
 .../agents/agentic-payments/x402/index.mdx    |    4 +-
 .../ai-crawl-control-with-bots.mdx            |    2 +-
 .../ai-crawl-control-with-waf.mdx             |   10 +-
 .../features/analyze-ai-traffic.mdx           |   22 +-
 .../features/manage-ai-crawlers.mdx           |   24 +-
 .../set-up-cloudflare-account.mdx             |    2 +-
 .../features/track-robots-txt.mdx             |   10 +-
 .../reference/redirects-for-ai-training.mdx   |   16 +-
 .../configuration/authentication.mdx          |    2 +-
 .../configuration/custom-providers.mdx        |   69 +-
 .../evaluations/add-human-feedback.mdx        |    1 -
 .../docs/ai-gateway/features/dlp/index.mdx    |   10 +-
 .../features/dynamic-routing/usage.mdx        |    3 +-
 .../integrations/aig-workers-ai-binding.mdx   |    2 +-
 src/content/docs/ai-gateway/mcp-server.mdx    |    2 +-
 .../observability/logging/index.mdx           |    6 +-
 .../docs/ai-gateway/reference/audit-logs.mdx  |   71 +-
 .../docs/ai-gateway/reference/limits.mdx      |   13 +-
 .../ai-gateway/tutorials/pruna-p-video.mdx    |   14 +-
 .../docs/ai-gateway/usage/chat-completion.mdx |    6 +-
 .../ai-gateway/usage/providers/anthropic.mdx  |   17 +-
 .../usage/providers/azureopenai.mdx           |   12 +-
 .../ai-gateway/usage/providers/baseten.mdx    |   40 +-
 .../ai-gateway/usage/providers/bedrock.mdx    |   10 +-
 .../docs/ai-gateway/usage/providers/fal.mdx   |   26 +-
 .../usage/providers/google-ai-studio.mdx      |   15 +-
 .../ai-gateway/usage/providers/ideogram.mdx   |   20 +-
 .../docs/ai-gateway/usage/rest-api.mdx        |   70 +-
 .../usage/websockets-api/non-realtime-api.mdx |    2 +-
 .../usage/websockets-api/realtime-api.mdx     |    2 +-
 .../docs/ai-search/api/instances/rest-api.mdx |    4 +-
 .../docs/ai-search/api/items/rest-api.mdx     |    4 +-
 .../ai-search/configuration/models/index.mdx  |    2 +
 src/content/docs/ai-search/how-to/nlweb.mdx   |   34 +-
 .../docs/ai-search/wrangler-commands.mdx      |    2 +-
 .../docs/ai/related-products/ai-gateway.mdx   |    2 +-
 .../account-analytics.mdx                     |   28 +-
 .../analytics-with-workers.mdx                |   10 +-
 .../account-and-zone-analytics/index.mdx      |    2 +-
 .../analytics/analytics-engine/grafana.mdx    |   12 +-
 .../docs/analytics/analytics-engine/index.mdx |   14 +-
 .../analytics/analytics-engine/limits.mdx     |    8 +-
 .../analytics/analytics-engine/pricing.mdx    |    2 +-
 .../analytics-engine/recipes/index.mdx        |    2 +-
 .../analytics/analytics-engine/sampling.mdx   |   62 +-
 .../analytics/analytics-engine/sql-api.mdx    |   10 +-
 .../sql-reference/aggregate-functions.mdx     |    2 +-
 .../sql-reference/bit-functions.mdx           |    2 +-
 .../sql-reference/date-time-functions.mdx     |    2 +-
 .../sql-reference/encoding-functions.mdx      |    2 +-
 .../analytics-engine/sql-reference/index.mdx  |    2 +-
 .../sql-reference/mathematical-functions.mdx  |    2 +-
 .../sql-reference/string-functions.mdx        |    2 +-
 .../type-conversion-functions.mdx             |    2 +-
 .../analytics-engine/worker-querying.mdx      |    1 +
 .../analytics-integrations/datadog.mdx        |    1 +
 .../analytics-integrations/index.mdx          |    2 +-
 .../analytics-integrations/prometheus.mdx     |   75 +-
 .../docs/analytics/custom-dashboards.mdx      |   38 +-
 .../docs/analytics/faq/about-analytics.mdx    |   16 +-
 src/content/docs/analytics/faq/index.mdx      |    2 +-
 src/content/docs/analytics/faq/other-faqs.mdx |   12 +-
 src/content/docs/analytics/faq/wae-faqs.mdx   |    9 +-
 .../docs/analytics/graphql-api/errors.mdx     |   64 +-
 .../features/confidence-intervals.mdx         |  102 +-
 .../graphql-api/features/discovery/index.mdx  |    1 +
 .../analytics/graphql-api/features/index.mdx  |    2 +-
 .../authentication/graphql-client-headers.mdx |    6 +-
 .../getting-started/authentication/index.mdx  |   52 +-
 .../getting-started/compose-graphql-query.mdx |   15 +
 .../getting-started/execute-graphql-query.mdx |    4 +-
 .../explore-graphql-schema.mdx                |   17 +-
 .../graphql-api/getting-started/index.mdx     |   20 +-
 .../docs/analytics/graphql-api/limits.mdx     |   18 +-
 .../docs/analytics/graphql-api/mcp-server.mdx |    2 +-
 .../graphql-api/migration-guides/index.mdx    |    4 +-
 .../network-analytics-v2/schema-map.mdx       |    1 +
 .../docs/analytics/graphql-api/sampling.mdx   |    4 +
 .../tutorials/end-customer-analytics.mdx      |  218 ++--
 .../analytics/graphql-api/tutorials/index.mdx |    2 +-
 .../querying-access-login-events.mdx          |   72 +-
 .../tutorials/querying-email-routing.mdx      |  352 ++---
 ...c-transit-endpoint-healthcheck-results.mdx |    5 +-
 ...gic-transit-tunnel-bandwidth-analytics.mdx |    8 +-
 ...gic-transit-tunnel-healthcheck-results.mdx |    5 +-
 src/content/docs/analytics/index.mdx          |   36 +-
 .../network-analytics/configure/index.mdx     |    2 +-
 .../configure/share-export.mdx                |    2 +-
 .../configure/time-range.mdx                  |    2 +-
 .../analytics/network-analytics/index.mdx     |   12 +-
 .../network-analytics/reference/index.mdx     |    2 +-
 .../network-analytics/understand/index.mdx    |    2 +-
 src/content/docs/analytics/sampling.mdx       |   23 +-
 .../docs/analytics/types-of-analytics.mdx     |   27 +-
 src/content/docs/api-shield/api-gateway.mdx   |    1 +
 src/content/docs/api-shield/glossary.mdx      |    3 +-
 src/content/docs/api-shield/index.mdx         |   30 +-
 .../management-and-monitoring/index.mdx       |    5 +-
 .../session-identifiers.mdx                   |    4 +-
 src/content/docs/api-shield/plans.mdx         |   15 +-
 .../reference/classic-schema-validation.mdx   |   14 +-
 .../docs/api-shield/reference/index.mdx       |    5 +-
 .../docs/api-shield/reference/terraform.mdx   |   11 +-
 .../security/graphql-protection/index.mdx     |    1 +
 .../docs/api-shield/security/index.mdx        |   45 +-
 .../security/jwt-validation/jwt-worker.mdx    |    2 +-
 .../jwt-validation/transform-rules.mdx        |    4 +-
 .../docs/api-shield/security/mtls/byo-ca.mdx  |    1 +
 .../docs/api-shield/security/mtls/index.mdx   |    1 +
 .../security/sequence-analytics.mdx           |    3 +-
 .../security/sequence-mitigation/api.mdx      |   23 +-
 .../sequence-mitigation/custom-rules.mdx      |   21 +-
 .../security/sequence-mitigation/index.mdx    |    8 +-
 .../security/volumetric-abuse-detection.mdx   |   11 +-
 .../docs/argo-smart-routing/analytics.mdx     |    9 +-
 .../argo-smart-routing/argo-for-packets.mdx   |    1 +
 src/content/docs/artifacts/api/errors.mdx     |   28 +-
 .../docs/artifacts/api/git-protocol.mdx       |    6 +-
 .../docs/artifacts/concepts/repositories.mdx  |   10 +-
 .../docs/artifacts/examples/git-client.mdx    |    5 +-
 .../docs/artifacts/guides/authentication.mdx  |   18 +-
 .../artifacts/guides/event-subscriptions.mdx  |    1 -
 .../docs/artifacts/platform/limits.mdx        |    4 +-
 .../docs/artifacts/platform/pricing.mdx       |    8 +-
 .../about/index.mdx                           |    1 +
 .../about/plugin-compatibility.mdx            |   50 +-
 .../about/test-current-speed.mdx              |    1 +
 .../get-started/change-nameservers.mdx        |    2 +
 .../get-started/index.mdx                     |    3 +-
 .../reference/cache-device-type.mdx           |    8 +-
 .../reference/index.mdx                       |    3 +-
 .../reference/page-rule-integration.mdx       |   17 +-
 .../reference/query-parameters.mdx            |   80 +-
 .../reference/subdomain-subdirectories.mdx    |    6 +-
 .../troubleshooting/index.mdx                 |   15 +-
 .../get-started/create-billing-profile.mdx    |    4 +-
 .../get-started/update-billing-info.mdx       |   22 +-
 .../docs/billing/manage/billable-usage.mdx    |   15 +-
 .../docs/billing/manage/budget-alerts.mdx     |   22 +-
 .../billing/manage/cancel-subscription.mdx    |    6 +-
 src/content/docs/billing/manage/invoices.mdx  |   26 +-
 .../docs/billing/manage/optimize-costs.mdx    |   48 +-
 .../manage/pay-invoices-overdue-balances.mdx  |    7 +-
 .../instant-bank-payments-link.mdx            |    6 +-
 .../docs/billing/threshold-billing.mdx        |    8 +-
 .../billing/troubleshoot/error-reference.mdx  |   24 +-
 .../resolve-cannot-remove-payment-method.mdx  |   37 +-
 ...ve-you-cannot-modify-this-subscription.mdx |   12 +-
 .../troubleshoot/troubleshoot-invoices.mdx    |    2 +-
 .../understand/billing-permissions.mdx        |   26 +-
 .../billing/understand/billing-policy.mdx     |   18 +-
 .../billing/understand/how-charges-accrue.mdx |   72 +-
 .../billing/understand/preview-services.mdx   |    2 +-
 .../understand/usage-based-billing.mdx        |   36 +-
 .../docs/bots/account-abuse-protection.mdx    |   75 +-
 .../block-ai-bots.mdx                         |    4 +-
 .../custom-rules.mdx                          |   22 +-
 .../detection-ids/additional-detections.mdx   |    7 +-
 .../bots/additional-configurations/index.mdx  |    5 +-
 .../ja3-ja4-fingerprint/index.mdx             |   81 +-
 .../signals-intelligence.mdx                  |    2 +-
 .../javascript-detections.mdx                 |    2 +-
 src/content/docs/bots/concepts/bot-tags.mdx   |    3 +-
 src/content/docs/bots/concepts/bot/index.mdx  |    2 +-
 .../bots/concepts/bot/signed-agents/index.mdx |    3 +-
 .../concepts/bot/signed-agents/policy.mdx     |    7 +-
 .../concepts/bot/verified-bots/policy.mdx     |    7 +-
 src/content/docs/bots/concepts/index.mdx      |    3 +-
 src/content/docs/bots/get-started/index.mdx   |    3 +-
 src/content/docs/bots/glossary.mdx            |    3 +-
 .../docs/bots/plans/bm-subscription.mdx       |   22 +-
 src/content/docs/bots/reference/alerts.mdx    |    9 +-
 .../reference/bot-management-variables.mdx    |   12 +-
 .../bots/reference/bot-verification/index.mdx |    5 +-
 .../bot-verification/ip-validation.mdx        |    9 +-
 src/content/docs/bots/reference/index.mdx     |    3 +-
 .../reference/machine-learning-models.mdx     |    5 +-
 .../docs/bots/reference/sample-terms.mdx      |    6 +-
 .../troubleshooting/bot-management-skips.mdx  |    3 +-
 .../bots/troubleshooting/false-positives.mdx  |    3 +-
 .../docs/bots/troubleshooting/index.mdx       |    4 +-
 .../docs/bots/workers-templates/index.mdx     |    3 +-
 .../docs/browser-run/features/index.mdx       |    2 +-
 .../docs/browser-run/how-to/deploy-worker.mdx |    2 +-
 src/content/docs/browser-run/mcp-server.mdx   |    2 +-
 .../quick-actions/api-reference.mdx           |    2 +-
 .../reference/browser-close-reasons.mdx       |   54 +-
 src/content/docs/byoip/address-maps/setup.mdx |   26 +-
 src/content/docs/byoip/changelog.mdx          |    2 +-
 src/content/docs/byoip/concepts/index.mdx     |    2 +-
 .../byoip/concepts/prefix-delegations.mdx     |    1 +
 src/content/docs/byoip/glossary.mdx           |    2 +-
 .../docs/byoip/route-leak-detection.mdx       |    3 +-
 .../docs/byoip/service-bindings/index.mdx     |    3 +-
 .../docs/byoip/troubleshooting/index.mdx      |    9 +-
 .../advanced-configuration/cache-reserve.mdx  |    9 +-
 .../advanced-configuration/crawler-hints.mdx  |    9 +-
 .../advanced-configuration/early-hints.mdx    |   21 +-
 .../cache/advanced-configuration/index.mdx    |    3 +-
 .../query-string-sort.mdx                     |   32 +-
 .../serve-tailored-content.mdx                |  158 +--
 .../vary-for-images.mdx                       |   74 +-
 .../cache-security/avoid-web-poisoning.mdx    |   18 +-
 .../cache-security/cache-deception-armor.mdx  |    6 +-
 .../docs/cache/cache-security/cors.mdx        |   11 +-
 .../docs/cache/cache-security/index.mdx       |    3 +-
 .../docs/cache/concepts/cache-behavior.mdx    |   10 +-
 .../docs/cache/concepts/cache-responses.mdx   |    9 +-
 .../docs/cache/concepts/cdn-cache-control.mdx |  178 +--
 .../docs/cache/concepts/customize-cache.mdx   |   13 +-
 .../cache/concepts/default-cache-behavior.mdx |   44 +-
 src/content/docs/cache/concepts/index.mdx     |    3 +-
 .../cache/concepts/retention-vs-freshness.mdx |    5 +-
 .../docs/cache/concepts/revalidation.mdx      |    1 +
 src/content/docs/cache/get-started.mdx        |   58 +-
 src/content/docs/cache/glossary.mdx           |    3 +-
 .../docs/cache/how-to/always-online.mdx       |    5 +-
 src/content/docs/cache/how-to/cache-keys.mdx  |   72 +-
 .../cache-response-rules/create-dashboard.mdx |    4 +-
 .../how-to/cache-rules/examples/index.mdx     |    4 +-
 .../docs/cache/how-to/cache-rules/order.mdx   |    3 +-
 .../cache-rules/page-rules-migration.mdx      |    4 +-
 .../how-to/configure-cache-status-code.mdx    |   14 +-
 .../how-to/edge-browser-cache-ttl/index.mdx   |   14 +-
 .../set-browser-ttl.mdx                       |    7 +-
 src/content/docs/cache/how-to/index.mdx       |    3 +-
 .../how-to/purge-cache/purge-by-hostname.mdx  |    9 +-
 .../purge-cache/purge-by-single-file.mdx      |    2 +-
 .../how-to/purge-cache/purge-by-tags.mdx      |   26 +-
 .../how-to/purge-cache/purge-cache-key.mdx    |   72 +-
 .../how-to/purge-cache/purge-everything.mdx   |    3 +-
 .../purge-cache/purge-varied-images.mdx       |    1 +
 .../purge-cache/purge-zone-versions.mdx       |   81 +-
 .../how-to/purge-cache/purge_by_prefix.mdx    |   39 +-
 .../docs/cache/how-to/set-caching-levels.mdx  |    9 +-
 .../interaction-cloudflare-products/index.mdx |    5 +-
 .../interaction-cloudflare-products/r2.mdx    |    1 +
 .../waf-snippets.mdx                          |    2 +-
 .../workers-cache-rules.mdx                   |    9 +-
 .../workers.mdx                               |    3 +-
 .../performance-review/cache-analytics.mdx    |    5 +-
 .../performance-review/cache-performance.mdx  |    5 +-
 .../docs/cache/performance-review/index.mdx   |    3 +-
 src/content/docs/cache/plans.mdx              |    5 +-
 .../reference/cdn-reference-architecture.mdx  |    1 +
 .../docs/cache/reference/development-mode.mdx |    5 +-
 src/content/docs/cache/reference/index.mdx    |    3 +-
 .../cache/troubleshooting/always-online.mdx   |    3 +
 .../docs/cache/troubleshooting/index.mdx      |    3 +-
 .../concepts/global-acceleration.mdx          |   14 +-
 .../reference/available-products.mdx          |    2 +-
 .../client-ip-geolocation/about/index.mdx     |    4 +-
 .../docs/client-ip-geolocation/faq/index.mdx  |    2 +
 .../client-ip-geolocation/get-started.mdx     |   16 +-
 .../docs/client-ip-geolocation/index.mdx      |   14 +-
 .../additional-configuration.mdx              |    2 +-
 .../challenge-pages/detect-response.mdx       |    2 +-
 .../challenge-types/challenge-pages/index.mdx |    2 +-
 .../challenge-pages/resolve-challenge.mdx     |    2 +-
 .../challenge-types/index.mdx                 |    6 +-
 .../challenge-types/turnstile.mdx             |   12 +-
 .../cloudflare-challenges/concepts/index.mdx  |    4 +-
 .../docs/cloudflare-challenges/index.mdx      |    3 +-
 .../cloudflare-challenges/reference/index.mdx |    6 +-
 .../reference/supported-browsers.mdx          |   38 +-
 .../reference/supported-languages.mdx         |   44 +-
 .../challenge-solve-issues.mdx                |    5 +-
 .../hostname-validation/backoff-schedule.mdx  |    5 +-
 .../hostname-validation/error-codes.mdx       |    1 +
 .../hostname-validation/pre-validation.mdx    |   59 +-
 .../migrating-custom-hostnames.mdx            |    2 +-
 .../hostname-analytics.mdx                    |   16 +-
 .../performance/argo-for-saas.mdx             |    1 +
 .../performance/cache-for-saas.mdx            |    1 +
 .../performance/early-hints-for-saas.mdx      |   66 +-
 .../cloudflare-for-saas/performance/index.mdx |    9 +-
 .../reference/certificate-authorities.mdx     |    1 +
 .../reference/certificate-statuses.mdx        |    1 +
 .../reference/dcv-validation-backoff.mdx      |    1 +
 .../reference/hostname-priority.mdx           |    1 +
 .../reference/status-codes/custom-csrs.mdx    |   59 +-
 .../status-codes/custom-hostnames.mdx         |  123 +-
 .../reference/token-validity-periods.mdx      |    8 +-
 .../reference/versioning.mdx                  |   24 +-
 .../saas-customers/index.mdx                  |    3 +-
 .../saas-customers/product-compatibility.mdx  |    4 +-
 .../provider-guides/webflow.mdx               |    6 +-
 .../certificate-statuses.mdx                  |    1 +
 .../uploading-certificates.mdx                |    5 +-
 .../validate-certificates/delegated-dcv.mdx   |    5 +-
 .../validate-certificates/troubleshooting.mdx |   19 +-
 .../webhook-definitions.mdx                   |  755 ++++++-----
 .../cloudflare-for-saas/security/index.mdx    |   11 +-
 .../security/waf-for-saas/index.mdx           |   48 +-
 .../regional-services-for-saas.mdx            |    1 +
 .../advanced-settings/worker-as-origin.mdx    |    6 +-
 .../configuration/bindings.mdx                |    5 -
 .../configuration/observability.mdx           |    2 +-
 .../reference/limits.mdx                      |    2 +-
 .../reference/platform-examples.mdx           |    2 +-
 .../reference/worker-isolation.mdx            |   21 +-
 .../best-practices/minimal-ruleset.mdx        |   23 +-
 .../cloudflare-network-firewall/index.mdx     |    4 +-
 .../packet-captures/collect-pcaps.mdx         |    2 +-
 .../packet-captures/pcaps-bucket-setup.mdx    |    4 +-
 .../diagnose-traffic-decisions.mdx            |    8 +-
 .../access-controls/access-settings/index.mdx |    1 +
 .../require-access-protection.mdx             |   10 +-
 .../access-settings/session-management.mdx    |    1 -
 .../access-controls/ai-controls/index.mdx     |    1 +
 .../ai-controls/mcp-portals.mdx               |   16 +-
 .../application-token.mdx                     |   78 +-
 .../http-apps/authorization-cookie/cors.mdx   |    7 +-
 .../applications/http-apps/managed-oauth.mdx  |   14 +-
 .../http-apps/saas-apps/generic-oidc-saas.mdx |   11 +-
 .../saas-apps/grafana-cloud-saas-oidc.mdx     |    2 +-
 .../http-apps/saas-apps/grafana-saas-oidc.mdx |    2 +-
 .../http-apps/saas-apps/index.mdx             |    3 +-
 .../non-http/browser-rendering.mdx            |    9 +-
 .../arbitrary-tcp.mdx                         |    4 +-
 .../automatic-cloudflared-authentication.mdx  |    2 +-
 .../non-http/legacy-private-network-app.mdx   |    5 +-
 .../non-http/self-hosted-private-app.mdx      |   76 +-
 .../access-controls/event-subscriptions.mdx   |    2 +-
 .../access-controls/policies/app-paths.mdx    |   17 +-
 .../access-controls/policies/index.mdx        |   46 +-
 .../policies/policy-management.mdx            |   29 +-
 .../require-purpose-justification.mdx         |    1 +
 .../policies/temporary-auth.mdx               |    8 +-
 .../service-credentials/index.mdx             |    1 +
 .../service-credentials/service-tokens.mdx    |    4 +-
 .../docs/cloudflare-one/account-limits.mdx    |   19 +-
 .../docs/cloudflare-one/changelog/tunnel.mdx  |    5 +-
 .../data-classification/index.mdx             |   12 +-
 .../configure-detection-entries.mdx           |   20 +-
 .../predefined-detection-entries.mdx          |  296 ++---
 .../dlp-profiles/predefined-profiles.mdx      |   15 +-
 .../email-security/investigation/index.mdx    |    4 +-
 .../investigation/search-email.mdx            |    4 +-
 .../email-security/reference/index.mdx        |    4 +-
 .../reference/regional-processing.mdx         |    2 +-
 .../email-security/settings/auto-moves.mdx    |    4 +-
 .../detection-settings/best-practices.mdx     |    6 +-
 .../settings/detection-settings/index.mdx     |    4 +-
 .../settings/domain-management/domain.mdx     |    2 +-
 .../settings/domain-management/index.mdx      |    4 +-
 .../email-security/settings/index.mdx         |    4 +-
 .../phish-submissions/phishnet-365.mdx        |    2 +-
 .../phishnet-google-workspace.mdx             |    2 +-
 .../submission-addresses.mdx                  |    2 +-
 .../email-security/setup/index.mdx            |   18 +-
 .../email-security/setup/manage-domains.mdx   |    2 +-
 .../bcc-setup/gmail-bcc-setup/index.mdx       |    5 +-
 .../bcc-journaling/bcc-setup/index.mdx        |    5 +-
 .../bcc-journaling/index.mdx                  |    2 +-
 .../bcc-journaling/journaling-setup/index.mdx |    5 +-
 .../journaling-setup/m365-journaling.mdx      |    3 +-
 .../journaling-setup/manual-add.mdx           |    1 +
 .../setup/post-delivery-deployment/index.mdx  |    4 +-
 .../pre-delivery-deployment/egress-ips.mdx    |    2 +-
 .../setup/pre-delivery-deployment/index.mdx   |    6 +-
 .../partner-domain-tls.mdx                    |    2 +-
 .../prerequisites/index.mdx                   |    6 +-
 .../use-cases/index.mdx                       |    5 +-
 .../email-security/submissions/index.mdx      |    2 +-
 .../submissions/invalid-submissions.mdx       |    2 +-
 .../docs/cloudflare-one/faq/devices-faq.mdx   |   11 +-
 .../insights/analytics-overview.mdx           |    2 +-
 .../insights/analytics/ai-security.mdx        |   26 +-
 .../insights/analytics/application-access.mdx |   36 +-
 .../insights/dex/mcp-server.mdx               |    3 +-
 .../insights/dex/monitoring.mdx               |   10 +-
 .../cloudflare-one/insights/dex/rules.mdx     |    2 +-
 .../insights/dex/tests/index.mdx              |    6 +-
 .../docs/cloudflare-one/insights/index.mdx    |   18 +-
 .../dashboard-logs/admin-activity-logs.mdx    |   24 +-
 .../dashboard-logs/gateway-logs/index.mdx     |   63 +-
 .../insights/logs/dashboard-logs/index.mdx    |    2 +-
 .../logs/dashboard-logs/posture-logs.mdx      |    2 +-
 .../insights/logs/logpush/index.mdx           |   32 +-
 .../diagnostics/buckets.mdx                   |    4 +-
 .../network-visibility/diagnostics/index.mdx  |    5 +-
 .../integrations/cloud-and-saas/anthropic.mdx |   22 +-
 .../microsoft-365/m365-copilot-fedramp.mdx    |    2 +-
 .../microsoft-365/m365-copilot.mdx            |    2 +-
 .../identity-providers/aws-saml.mdx           |    2 +-
 .../identity-providers/cloudflare.mdx         |    4 +-
 .../identity-providers/facebook-login.mdx     |    8 +-
 .../identity-providers/github.mdx             |    4 +-
 .../integrations/identity-providers/index.mdx |    1 +
 .../integrations/identity-providers/okta.mdx  |    4 +-
 .../identity-providers/pingone-saml.mdx       |    1 +
 .../identity-providers/signed_authn.mdx       |    2 +
 .../integrations/service-providers/index.mdx  |    4 +-
 .../networks/connectivity-options.mdx         |   22 +-
 .../connectors/cloudflare-mesh/routes.mdx     |    1 -
 .../configure-tunnels/cipher-suites.mdx       |   10 +-
 .../configure-tunnels/index.mdx               |    2 +-
 .../configure-tunnels/origin-parameters.mdx   |   16 +-
 .../remote-tunnel-permissions.mdx             |  126 +-
 .../configure-tunnels/run-parameters.mdx      |   28 +-
 .../system-requirements.mdx                   |    5 +-
 .../tunnel-with-firewall.mdx                  |   19 +-
 .../deployment-guides/index.mdx               |    2 +-
 .../deployment-guides/terraform.mdx           |    1 +
 .../tunnel-useful-commands.mdx                |   14 +-
 .../downloads/copyrights.mdx                  |   57 +-
 .../cloudflare-tunnel/downloads/license.mdx   |    1 +
 .../get-started/create-remote-tunnel-api.mdx  |  117 +-
 .../get-started/create-remote-tunnel.mdx      |    6 +-
 .../cloudflare-tunnel/get-started/index.mdx   |    3 +-
 .../connectors/cloudflare-tunnel/index.mdx    |    4 +-
 .../monitor-tunnels/index.mdx                 |    3 +-
 .../monitor-tunnels/notifications.mdx         |    3 +-
 .../private-net/cloudflared/connect-cidr.mdx  |   14 +-
 .../private-net/cloudflared/index.mdx         |    3 +-
 .../private-net/cloudflared/private-dns.mdx   |   23 +-
 .../routing-to-tunnel/dns.mdx                 |   13 +-
 .../routing-to-tunnel/protocols.mdx           |   14 +-
 .../public-load-balancers.mdx                 |   41 +-
 .../troubleshoot-tunnels/common-errors.mdx    |    1 +
 .../troubleshoot-tunnels/diag-logs.mdx        |   59 +-
 .../troubleshoot-tunnels/index.mdx            |    2 +-
 .../cloudflare-tunnel/use-cases/index.mdx     |    9 +-
 .../cloudflare-tunnel/use-cases/rdp/index.mdx |    2 +-
 .../use-cases/rdp/rdp-device-client.mdx       |    2 +-
 .../use-cases/vnc-browser-rendering.mdx       |  214 ++--
 .../cloudflare-wan/analytics/index.mdx        |   23 +-
 .../analytics/netflow-analytics.mdx           |    9 +-
 .../analytics/network-analytics.mdx           |    5 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 .../analytics/site-analytics.mdx              |   16 +-
 .../configure-hardware-appliance/index.mdx    |   84 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/configure-virtual-appliance.mdx |   80 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |   11 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../maintenance/deactivate-appliance.mdx      |    1 +
 .../appliance/maintenance/heartbeat.mdx       |    1 +
 .../appliance/maintenance/index.mdx           |    3 +-
 .../maintenance/interrupt-service-window.mdx  |    1 +
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   18 +-
 .../application-based-policies/index.mdx      |   14 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    5 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   14 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../configuration/appliance/reference.mdx     |   33 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../check-tunnel-health-dashboard.mdx         |   11 +-
 .../configure-tunnel-health-alerts.mdx        |    6 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |   12 +-
 .../update-tunnel-health-checks-frequency.mdx |    3 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   34 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   45 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |   11 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../third-party/alibaba-cloud.mdx             |   19 +-
 .../third-party/aruba-edgeconnect.mdx         |   15 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   22 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   22 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    5 +-
 .../third-party/cisco-meraki-static.mdx       |   30 +-
 .../configuration/third-party/fitelnet.mdx    |   19 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   16 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   19 +-
 .../configuration/third-party/oracle.mdx      |   16 +-
 .../configuration/third-party/palo-alto.mdx   |   19 +-
 .../configuration/third-party/pfsense.mdx     |   19 +-
 .../configuration/third-party/sonicwall.mdx   |   22 +-
 .../third-party/sophos-firewall.mdx           |   22 +-
 .../configuration/third-party/strongswan.mdx  |   13 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   13 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../connectors/cloudflare-wan/get-started.mdx |   21 +-
 .../connectors/cloudflare-wan/index.mdx       |   20 +-
 .../cloudflare-wan/legal/3rdparty.mdx         |    1 +
 .../connectors/cloudflare-wan/legal/index.mdx |    3 +-
 .../cloudflare-wan/network-interconnect.mdx   |   17 +-
 .../connectors/cloudflare-wan/on-ramps.mdx    |   20 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    3 +-
 .../reference/device-compatibility.mdx        |   76 +-
 .../reference/gre-ipsec-tunnels.mdx           |   10 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |   10 +-
 .../cloudflare-wan/reference/index.mdx        |    3 +-
 .../cloudflare-wan/reference/mtu-mss.mdx      |    2 +-
 .../reference/traffic-steering.mdx            |   28 +-
 .../reference/tunnel-health-checks.mdx        |   12 +-
 .../connectors/cloudflare-wan/security.mdx    |    9 +-
 .../troubleshooting/connectivity.mdx          |   15 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   17 +-
 .../troubleshooting/routing-and-bgp.mdx       |   24 +-
 .../troubleshooting/tunnel-health.mdx         |   33 +-
 .../cloudflare-wan/wan-transformation.mdx     |   12 +-
 .../zero-trust/cloudflare-gateway.mdx         |   45 +-
 .../zero-trust/cloudflare-one-client.mdx      |   24 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   15 +-
 .../cloudflare-wan/zero-trust/index.mdx       |    1 +
 .../zero-trust/security-services.mdx          |    9 +-
 .../connectors/granular-permissions.mdx       |    2 +-
 .../networks/connectors/index.mdx             |    3 +-
 .../networks/routes/add-routes.mdx            |   20 +-
 .../networks/routes/reserved-ips.mdx          |    4 +-
 .../networks/virtual-networks.mdx             |   12 +-
 .../accessibility.mdx                         |    2 +-
 .../remote-browser-isolation/index.mdx        |    2 +
 .../known-limitations.mdx                     |    5 +-
 .../network-dependencies.mdx                  |    4 +-
 .../remote-browser-isolation/setup/index.mdx  |   14 +-
 .../custom-pages/gateway-block-page.mdx       |    2 +-
 .../custom-pages/index.mdx                    |    2 +-
 .../client-checks/antivirus.mdx               |   31 +-
 .../client-checks/application-check.mdx       |    4 +-
 .../client-checks/file-check.mdx              |    3 +-
 .../posture-checks/client-checks/firewall.mdx |   11 +-
 .../posture-checks/client-checks/index.mdx    |   41 +-
 .../client-checks/os-version.mdx              |    3 +-
 .../client-checks/require-warp.mdx            |    2 +-
 .../reusable-components/tags.mdx              |    1 +
 .../configure/modes/index.mdx                 |    4 +-
 .../troubleshooting/common-issues.mdx         |   15 -
 .../troubleshooting/connectivity-status.mdx   |   36 +-
 .../troubleshooting/diagnostic-logs.mdx       |  184 +--
 .../devices/device-registration.mdx           |   35 +-
 .../devices/user-side-certificates/index.mdx  |   10 +-
 .../manual-deployment.mdx                     |  218 ++--
 .../team-and-resources/users/risk-score.mdx   |   19 +-
 .../team-and-resources/users/scim.mdx         |    3 +-
 .../team-and-resources/users/users.mdx        |   10 +-
 .../traffic-policies/global-policies.mdx      |   18 +-
 .../network-policies/protocol-detection.mdx   |   18 +-
 .../best-practices/magic-transit-egress.mdx   |    6 +-
 .../tiered-policies/index.mdx                 |   12 +-
 .../tiered-policies/tenant-api.mdx            |    1 +
 .../cloudflare-one/troubleshooting/access.mdx |    2 +-
 .../troubleshooting/browser-isolation.mdx     |    2 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    2 +-
 .../troubleshooting/contact-support.mdx       |    4 -
 .../cloudflare-one/troubleshooting/dex.mdx    |    2 +-
 .../troubleshooting/email-security.mdx        |    2 +-
 .../troubleshooting/gateway.mdx               |    2 +-
 .../cloudflare-one/troubleshooting/tunnel.mdx |   33 +-
 .../troubleshooting/wan/connectivity.mdx      |   17 +-
 .../troubleshooting/wan/index.mdx             |    2 +-
 .../troubleshooting/wan/ipsec.mdx             |   19 +-
 .../troubleshooting/wan/routing-bgp.mdx       |   26 +-
 .../troubleshooting/wan/tunnel-health.mdx     |   35 +-
 .../troubleshooting/warp-client.mdx           |    2 +-
 .../tutorials/entra-id-risky-users.mdx        |   40 +-
 .../docs/cloudflare-wan/analytics/index.mdx   |    7 +-
 .../analytics/netflow-analytics.mdx           |    5 +-
 .../analytics/network-analytics.mdx           |    7 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    6 +-
 .../analytics/query-tunnel-health.mdx         |    9 +-
 .../analytics/site-analytics.mdx              |   19 +-
 src/content/docs/cloudflare-wan/changelog.mdx |    7 +-
 .../configure-hardware-appliance/index.mdx    |   79 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |    9 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../appliance/maintenance/index.mdx           |    5 +-
 .../maintenance/register-appliance.mdx        |    2 +-
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   27 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-options.mdx     |   42 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    7 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   11 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |    8 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   25 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   32 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |    7 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../configuration/multi-cloud-networking.mdx  |    3 +-
 .../third-party/alibaba-cloud.mdx             |   20 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   21 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   21 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    6 +-
 .../third-party/cisco-meraki-static.mdx       |   21 +-
 .../configuration/third-party/fitelnet.mdx    |   20 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   17 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   18 +-
 .../configuration/third-party/oracle.mdx      |   17 +-
 .../configuration/third-party/palo-alto.mdx   |   18 +-
 .../configuration/third-party/pfsense.mdx     |   20 +-
 .../configuration/third-party/sonicwall.mdx   |   23 +-
 .../third-party/sophos-firewall.mdx           |   23 +-
 .../configuration/third-party/strongswan.mdx  |   14 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   14 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../docs/cloudflare-wan/get-started.mdx       |   11 +-
 src/content/docs/cloudflare-wan/glossary.mdx  |    3 +-
 src/content/docs/cloudflare-wan/index.mdx     |    5 +-
 .../docs/cloudflare-wan/legal/3rdparty.mdx    |    3 +-
 .../docs/cloudflare-wan/legal/index.mdx       |    5 +-
 .../cloudflare-wan/network-interconnect.mdx   |   16 +-
 src/content/docs/cloudflare-wan/on-ramps.mdx  |    4 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    4 +-
 .../reference/device-compatibility.mdx        |   58 +-
 .../reference/gre-ipsec-tunnels.mdx           |    4 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/cloudflare-wan/reference/index.mdx   |    5 +-
 .../docs/cloudflare-wan/reference/mtu-mss.mdx |    6 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    9 +-
 .../reference/virtual-networks.mdx            |    9 +-
 src/content/docs/cloudflare-wan/security.mdx  |    8 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   10 +-
 .../troubleshooting/routing-and-bgp.mdx       |   22 +-
 .../troubleshooting/tunnel-health.mdx         |   30 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   12 +-
 .../zero-trust/connectivity-options.mdx       |   19 +-
 .../docs/cloudflare-wan/zero-trust/index.mdx  |    4 +-
 .../docs/constellation/platform/index.mdx     |    2 +-
 src/content/docs/containers/examples/cron.mdx |   41 +-
 .../examples/durable-object-interface.mdx     |    1 +
 .../docs/containers/examples/index.mdx        |    1 +
 .../containers/platform-details/placement.mdx |    8 +-
 src/content/docs/containers/pricing.mdx       |    2 +-
 src/content/docs/containers/ssh.mdx           |    2 +-
 .../d1/best-practices/local-development.mdx   |    2 +
 .../docs/d1/best-practices/query-d1.mdx       |   50 +-
 .../d1/best-practices/remote-development.mdx  |   15 +-
 .../docs/d1/best-practices/retry-queries.mdx  |   26 +-
 .../d1/best-practices/use-d1-from-pages.mdx   |    2 +-
 .../docs/d1/best-practices/use-indexes.mdx    |   26 +-
 .../docs/d1/configuration/environments.mdx    |   60 +-
 src/content/docs/d1/get-started.mdx           |   12 +-
 src/content/docs/d1/observability/billing.mdx |    4 +-
 src/content/docs/d1/platform/limits.mdx       |   34 +-
 .../docs/d1/reference/community-projects.mdx  |   40 +-
 .../docs/d1/reference/data-security.mdx       |    6 +-
 src/content/docs/d1/reference/faq.mdx         |    4 +-
 .../docs/d1/reference/generated-columns.mdx   |   24 +-
 src/content/docs/d1/reference/glossary.mdx    |    2 +-
 src/content/docs/d1/reference/migrations.mdx  |    6 +-
 src/content/docs/d1/sql-api/foreign-keys.mdx  |   28 +-
 src/content/docs/d1/sql-api/query-json.mdx    |   82 +-
 .../tutorials/build-an-api-to-access-d1.mdx   |    8 +-
 .../docs/d1/tutorials/d1-and-prisma-orm.mdx   |    2 +-
 .../docs/data-localization/compatibility.mdx  |   68 +-
 .../data-localization/geo-key-manager.mdx     |    5 +-
 .../docs/ddos-protection/about/components.mdx |    3 +-
 .../about/how-ddos-protection-works.mdx       |   17 +-
 .../docs/ddos-protection/about/index.mdx      |    5 +-
 .../api/dns-protection/index.mdx              |   17 +-
 .../api/dns-protection/json-objects.mdx       |   21 +-
 .../advanced-ddos-systems/api/index.mdx       |    3 +-
 .../programmable-flow-protection/examples.mdx |  209 +--
 .../programmable-flow-protection/index.mdx    |   37 +-
 .../json-objects.mdx                          |   61 +-
 .../api/tcp-protection/examples.mdx           |  217 ++--
 .../api/tcp-protection/index.mdx              |  103 +-
 .../api/tcp-protection/json-objects.mdx       |   51 +-
 .../how-to/add-prefix.mdx                     |    6 +-
 .../how-to/exclude-prefix.mdx                 |    5 +-
 .../advanced-ddos-systems/how-to/index.mdx    |    5 +-
 .../advanced-ddos-systems/index.mdx           |    4 +-
 .../advanced-ddos-systems/overview/index.mdx  |   16 +-
 .../overview/programmable-flow-protection.mdx |   92 +-
 .../advanced-ddos-systems/troubleshooting.mdx |   13 +-
 .../ddos-protection/best-practices/index.mdx  |    3 +-
 .../best-practices/proactive-defense.mdx      |    4 +-
 .../best-practices/third-party.mdx            |    2 +-
 .../ddos-protection/botnet-threat-feed.mdx    |   58 +-
 .../docs/ddos-protection/get-started.mdx      |    3 +-
 .../managed-rulesets/http/index.mdx           |    2 +-
 .../managed-rulesets/index.mdx                |    1 +
 .../managed-rulesets/network/index.mdx        |    2 +-
 .../network-overrides/override-examples.mdx   |   12 +-
 .../docs/ddos-protection/reference/alerts.mdx |    2 +-
 .../docs/ddos-protection/reference/index.mdx  |    3 +-
 .../docs/ddos-protection/reference/logs.mdx   |    3 +-
 .../reference/simulate-ddos-attack.mdx        |    3 +-
 src/content/docs/dmarc-management/enable.mdx  |    3 +-
 .../dmarc-management/security-records.mdx     |    2 +-
 .../docs/dmarc-management/statistics.mdx      |    1 +
 .../docs/dns/additional-options/index.mdx     |    2 +-
 src/content/docs/dns/changelog.mdx            |    8 +-
 .../docs/dns/cname-flattening/index.mdx       |    2 +-
 .../set-up-cname-flattening.mdx               |    8 +-
 .../random-prefix-attacks/setup.mdx           |   11 +-
 src/content/docs/dns/dnssec/dnssec-states.mdx |   13 +-
 src/content/docs/dns/dnssec/enable-nsec3.mdx  |    4 +-
 src/content/docs/dns/dnssec/index.mdx         |   19 +-
 .../dns/dnssec/multi-signer-dnssec/about.mdx  |    4 +-
 .../dns/dnssec/multi-signer-dnssec/setup.mdx  |    2 +-
 .../dnssec/validation-and-key-management.mdx  |    8 +-
 .../docs/dns/foundation-dns/dnssec-keys.mdx   |    3 +-
 src/content/docs/dns/foundation-dns/index.mdx |   23 +-
 src/content/docs/dns/glossary.mdx             |    2 +-
 .../docs/dns/internal-dns/analytics.mdx       |    2 +-
 .../how-to/create-subdomain.mdx               |    3 +-
 .../how-to/email-records.mdx                  |   15 +-
 .../dns/manage-dns-records/how-to/index.mdx   |    3 +-
 .../how-to/managing-dynamic-ip-addresses.mdx  |    3 +-
 .../how-to/round-robin-dns.mdx                |    1 +
 .../how-to/subdomains-outside-cloudflare.mdx  |   17 +-
 .../manage-dns-records/reference/index.mdx    |    3 +-
 .../reference/record-attributes.mdx           |   17 +-
 .../dns/manage-dns-records/reference/ttl.mdx  |    3 +-
 .../troubleshooting/exposed-ip-address.mdx    |    3 +-
 .../troubleshooting/index.mdx                 |    5 +-
 .../dns/nameservers/advanced-nameservers.mdx  |    1 +
 .../zone-custom-nameservers.mdx               |    1 -
 .../docs/dns/private-origins/index.mdx        |    3 +-
 .../docs/dns/reference/all-features.mdx       |    3 +-
 .../dns/reference/analytics-mcp-server.mdx    |    3 +-
 .../docs/dns/reference/best-practices.mdx     |    3 +-
 .../docs/dns/reference/domain-connect.mdx     |   18 +-
 src/content/docs/dns/reference/index.mdx      |    2 +-
 .../recommended-third-party-tools.mdx         |    9 +-
 .../docs/dns/troubleshooting/email-issues.mdx |   12 +-
 .../docs/dns/troubleshooting/index.mdx        |    9 +-
 .../conversions/convert-full-to-secondary.mdx |   34 +-
 .../conversions/convert-partial-to-full.mdx   |    2 +-
 .../dns/zone-setups/conversions/index.mdx     |    2 +-
 .../docs/dns/zone-setups/full-setup/index.mdx |    2 +-
 .../partial-setup/dns-resolution.mdx          |    7 +-
 .../dns/zone-setups/partial-setup/setup.mdx   |   11 +-
 .../zone-setups/reference/domain-status.mdx   |   10 +-
 .../docs/dns/zone-setups/reference/index.mdx  |    3 +-
 .../subdomain-setup/move-to-new-account.mdx   |    1 +
 .../zone-setups/subdomain-setup/rollback.mdx  |    5 +-
 .../subdomain-setup/setup/parent-on-full.mdx  |    3 +
 .../setup/parent-on-partial.mdx               |    3 +-
 .../dns/zone-setups/troubleshooting/index.mdx |    3 +-
 .../cloudflare-as-primary/index.mdx           |    2 +-
 .../transfer-criteria.mdx                     |    3 +-
 .../cloudflare-as-secondary/alerts.mdx        |    3 +-
 .../cloudflare-as-secondary/index.mdx         |    4 +-
 .../cloudflare-as-secondary/proxy-traffic.mdx |    2 +-
 .../docs/durable-objects/api/alarms.mdx       |   77 +-
 .../api/legacy-kv-storage-api.mdx             |   13 +-
 .../api/sqlite-storage-api.mdx                |   24 +-
 .../access-durable-objects-storage.mdx        |    3 -
 .../concepts/durable-object-lifecycle.mdx     |    2 +-
 .../docs/durable-objects/examples/agents.mdx  |    2 +-
 .../docs/durable-objects/examples/index.mdx   |    5 +-
 .../examples/websocket-server.mdx             |    8 +-
 .../observability/data-studio.mdx             |    2 +-
 .../durable-objects/platform/known-issues.mdx |    2 +-
 .../docs/durable-objects/platform/limits.mdx  |    1 +
 .../reference/data-location.mdx               |   16 +-
 .../reference/data-security.mdx               |    6 +-
 .../reference/environments.mdx                |    7 +-
 .../docs/durable-objects/reference/faq.mdx    |    6 +-
 .../durable-objects/reference/glossary.mdx    |    2 +-
 .../reference/in-memory-state.mdx             |   30 +-
 .../docs/durable-objects/video-tutorials.mdx  |   12 +-
 .../docs/dynamic-workers/usage/bindings.mdx   |  140 +-
 .../email-workers/local-development.mdx       |   95 +-
 .../email-workers/reply-email-workers.mdx     |   60 +-
 .../email-routing/get-started/audit-logs.mdx  |    8 +-
 .../docs/email-routing/get-started/index.mdx  |    2 +-
 .../docs/email-routing/graphql-example.mdx    |    2 +-
 src/content/docs/email-routing/limits.mdx     |    2 +-
 src/content/docs/email-routing/postmaster.mdx |    3 +-
 .../setup/email-routing-dns-records.mdx       |    8 +-
 .../docs/email-routing/setup/index.mdx        |    2 +-
 .../email-routing/troubleshooting/index.mdx   |    2 +-
 .../email-security/account-setup/index.mdx    |    2 +-
 .../gsuite-bcc-setup/create-project-gcp.mdx   |    4 +-
 .../deployment/inline/reference/index.mdx     |    2 +-
 .../deployment/inline/setup/index.mdx         |    2 +-
 .../domains-and-routing/alert-webhooks.mdx    |   10 +-
 .../domains-and-routing/index.mdx             |    2 +-
 .../email-policies/index.mdx                  |    2 +-
 .../enhanced-detections/index.mdx             |    2 +-
 .../email-configuration/lists/index.mdx       |    2 +-
 .../migrate-to-email-security.mdx             |   26 +-
 .../docs/email-security/reference/index.mdx   |    2 +-
 src/content/docs/email-service/api/index.mdx  |    2 +-
 .../api/route-emails/email-handler.mdx        |    2 +-
 .../email-service/api/route-emails/index.mdx  |    2 +-
 .../api/send-emails/rest-api.mdx              |   52 +-
 .../api/send-emails/workers-api.mdx           |   40 +-
 .../docs/email-service/concepts/index.mdx     |    2 +-
 .../email-service/configuration/index.mdx     |    2 +-
 .../email-routing/hard-bounce-handling.mdx    |  241 ++--
 .../examples/email-routing/spam-filtering.mdx |   33 +-
 .../email-service/get-started/send-emails.mdx |   34 +-
 .../email-service/local-development/index.mdx |    2 +-
 .../local-development/routing.mdx             |   44 +-
 .../docs/email-service/platform/index.mdx     |    2 +-
 .../docs/email-service/platform/pricing.mdx   |    8 +-
 .../docs/email-service/reference/index.mdx    |    5 +-
 .../email-service/reference/postmaster.mdx    |    1 +
 .../docs/firewall/api/cf-filters/delete.mdx   |   38 +-
 .../docs/firewall/api/cf-filters/get.mdx      |  100 +-
 .../docs/firewall/api/cf-filters/post.mdx     |   68 +-
 .../docs/firewall/api/cf-filters/put.mdx      |   52 +-
 .../firewall/api/cf-filters/validation.mdx    |   34 +-
 .../api/cf-filters/what-is-a-filter.mdx       |   10 +-
 .../firewall/api/cf-firewall-rules/get.mdx    |  160 +--
 .../firewall/api/cf-firewall-rules/post.mdx   |  116 +-
 .../cf-firewall-rules/order-priority.mdx      |    1 +
 .../account-security/cloudflare-access.mdx    |    4 +-
 .../account/account-security/index.mdx        |    2 +-
 .../leaked-password-notifications.mdx         |    2 +
 .../manage-active-sessions.mdx                |    2 +-
 .../account/account-security/zone-holds.mdx   |    4 +-
 .../fundamentals/account/create-account.mdx   |   11 +-
 .../account/find-account-and-zone-ids.mdx     |   12 +-
 .../docs/fundamentals/account/index.mdx       |    2 +-
 .../api/how-to/control-api-access.mdx         |    6 +-
 .../api/how-to/create-via-api.mdx             |   32 +-
 .../api/how-to/restrict-tokens.mdx            |    7 +-
 src/content/docs/fundamentals/api/index.mdx   |    2 +-
 .../docs/fundamentals/api/reference/index.mdx |    2 +-
 .../fundamentals/api/reference/limits.mdx     |    6 +-
 .../docs/fundamentals/api/troubleshooting.mdx |   18 +-
 .../concepts/how-cloudflare-works.mdx         |    8 +-
 .../docs/fundamentals/concepts/index.mdx      |    2 +-
 .../concepts/traffic-flow-cloudflare.mdx      |   22 +-
 src/content/docs/fundamentals/index.mdx       |    4 +-
 .../fundamentals/manage-domains/add-site.mdx  |   11 +-
 .../manage-domains/domain-version.mdx         |   12 +-
 .../manage-domains/move-domain.mdx            |    2 +
 .../manage-domains/pause-cloudflare.mdx       |    4 +-
 .../fundamentals/manage-members/index.mdx     |    2 +-
 .../fundamentals/manage-members/policies.mdx  |    5 +-
 .../fundamentals/manage-members/roles.mdx     |    2 +-
 .../fundamentals/manage-members/scope.mdx     |   52 +-
 .../manage-members/user-groups.mdx            |   23 +-
 .../docs/fundamentals/new-features/index.mdx  |    4 +-
 .../organizations/limitations.mdx             |    4 +-
 .../docs/fundamentals/organizations/setup.mdx |   16 +-
 .../fundamentals/performance/improve-seo.mdx  |   16 +-
 .../docs/fundamentals/performance/index.mdx   |    2 +-
 .../fundamentals/performance/test-speed.mdx   |   16 +-
 .../fundamentals/reference/best-practices.mdx |    6 +-
 .../reference/cdn-cgi-endpoint.mdx            |   12 +-
 .../reference/cloudflare-ray-id.mdx           |    3 +-
 .../reference/connection-limits.mdx           |   22 +-
 .../reference/cryptographic-personhood.mdx    |   44 +-
 .../docs/fundamentals/reference/glossary.mdx  |    2 +-
 .../reference/google-analytics.mdx            |    4 +
 .../docs/fundamentals/reference/index.mdx     |    2 +-
 .../scim-virtual-groups-migration.mdx         |   17 +-
 .../docs/fundamentals/reference/partners.mdx  |    2 +-
 .../delivering-videos-with-cloudflare.mdx     |   18 +-
 .../reference/policies-compliances/index.mdx  |    2 +-
 .../docs/fundamentals/reference/redirects.mdx |    2 +-
 .../report-abuse/abuse-report-obligations.mdx |    6 +-
 .../report-abuse/complaint-types.mdx          |   26 +-
 .../reference/report-abuse/index.mdx          |    8 +-
 .../reference/report-abuse/submit-report.mdx  |   12 +-
 .../sdk-ecosystem-support-policy.mdx          |   14 +-
 .../reference/tcp-connections.mdx             |    4 +-
 .../reference/troubleshooting.mdx             |   44 +-
 .../docs/fundamentals/security/index.mdx      |    2 +-
 .../docs/fundamentals/security/pci-scans.mdx  |    6 +-
 .../security/under-ddos-attack.mdx            |    8 +-
 .../docs/fundamentals/user-profiles/2fa.mdx   |   34 +-
 .../user-profiles/account-recovery.mdx        |   10 +-
 .../change-password-or-email.mdx              |    2 +-
 .../user-profiles/customize-account.mdx       |    6 +-
 .../user-profiles/delete-account.mdx          |    5 +-
 .../docs/fundamentals/user-profiles/login.mdx |    7 +-
 .../multi-factor-email-authentication.mdx     |    6 +-
 .../user-profiles/verify-email-address.mdx    |    6 +-
 src/content/docs/google-tag-gateway/index.mdx |    6 +-
 .../concepts/health-checks-regions.mdx        |    1 +
 .../docs/health-checks/concepts/index.mdx     |    3 +-
 .../health-checks/health-checks-analytics.mdx |    3 +-
 .../how-to/health-checks-notifications.mdx    |    5 +-
 .../docs/health-checks/how-to/index.mdx       |    3 +-
 .../health-checks/how-to/zone-lockdown.mdx    |    3 +-
 .../drizzle-orm.mdx                           |    4 +-
 .../prisma-postgres.mdx                       |   15 +-
 .../postgres-database-providers/supabase.mdx  |    2 +-
 .../observability/troubleshooting.mdx         |   78 +-
 .../docs/hyperdrive/platform/limits.mdx       |   28 +-
 .../hyperdrive/platform/storage-options.mdx   |    2 +-
 .../reference/wrangler-commands.mdx           |    2 +-
 .../docs/hyperdrive/tutorials/index.mdx       |    2 +-
 ...rverless-timeseries-api-with-timescale.mdx |    2 +-
 .../optimization/make-responsive-images.mdx   |   17 +-
 .../optimization/transformations/flows.mdx    |   19 +-
 .../optimization/transformations/overview.mdx |    3 +-
 .../docs/key-transparency/api/epochs.mdx      |    2 +-
 .../docs/key-transparency/api/index.mdx       |    4 +-
 .../docs/key-transparency/api/namespaces.mdx  |    8 +-
 .../docs/kv/api/delete-key-value-pairs.mdx    |   37 +-
 src/content/docs/kv/concepts/kv-bindings.mdx  |   32 +-
 .../docs/kv/concepts/kv-namespaces.mdx        |   17 +-
 src/content/docs/kv/get-started.mdx           |   15 +-
 src/content/docs/kv/glossary.mdx              |    2 +-
 src/content/docs/kv/observability/index.mdx   |    2 +-
 .../kv/observability/metrics-analytics.mdx    |    1 -
 src/content/docs/kv/platform/pricing.mdx      |    2 +-
 .../docs/kv/reference/data-security.mdx       |    6 +-
 .../docs/kv/reference/environments.mdx        |    2 +
 src/content/docs/kv/reference/kv-commands.mdx |    4 +-
 .../account-security/audit-logs.mdx           |    2 +-
 .../account-security/index.mdx                |    6 +-
 .../review-active-sessions.mdx                |    2 +-
 .../account-security/review-audit-logs.mdx    |    2 +-
 .../account-security/set-up-2fa.mdx           |    4 +-
 .../browser-integrity.mdx                     |    2 +-
 .../default-traffic-security/ddos.mdx         |    4 +-
 .../default-traffic-security/dnssec.mdx       |    2 +-
 .../default-traffic-security/index.mdx        |    2 +-
 .../default-traffic-security/mtls.mdx         |    2 +-
 .../application-security/firewall/index.mdx   |    4 +-
 .../lists/configuration.mdx                   |    2 +-
 .../application-security/lists/features.mdx   |    2 +-
 .../application-security/lists/index.mdx      |    8 +-
 .../application-security/lists/use-cases.mdx  |    2 +-
 .../rate-limiting/configurations.mdx          |   16 +-
 .../rate-limiting/features.mdx                |    2 +-
 .../rate-limiting/index.mdx                   |    4 +-
 .../rate-limiting/use-cases.mdx               |    2 +-
 .../security-center/brand-protection.mdx      |    2 +-
 .../security-center/index.mdx                 |    6 +-
 .../access-application/index.mdx              |    8 +-
 .../advanced-workflows/index.mdx              |    8 +-
 .../alternative-onramps/clientless-rbi.mdx    |    6 +-
 .../alternative-onramps/index.mdx             |    4 +-
 .../clientless-access/concepts/index.mdx      |    2 +-
 .../concepts/what-is-clientless-access.mdx    |    2 +-
 .../best-practices.mdx                        |    6 +-
 .../create-tunnel.mdx                         |   11 +-
 .../connect-private-applications/index.mdx    |    4 +-
 .../customize-ux/app-launcher.mdx             |    2 +-
 .../customize-ux/block-page.mdx               |    2 +-
 .../customize-ux/bookmarks.mdx                |    2 +-
 .../clientless-access/customize-ux/index.mdx  |    8 +-
 .../customize-ux/login-page.mdx               |    2 +-
 .../clientless-access/customize-ux/tags.mdx   |    2 +-
 .../clientless-access/initial-setup/index.mdx |    8 +-
 .../migrate-applications/best-practices.mdx   |   14 +-
 .../migrate-applications/index.mdx            |    6 +-
 .../migrate-applications/integrated-sso.mdx   |   12 +-
 .../clientless-access/terraform/index.mdx     |    2 +-
 .../create-zero-trust-org.mdx                 |    2 +-
 .../cybersafe/account-creation/index.mdx      |    6 +-
 .../cybersafe/concepts/index.mdx              |    8 +-
 .../concepts/what-is-dns-filtering.mdx        |   18 +-
 .../gateway-verify-local-connectivity.mdx     |    8 +-
 .../advertise-prefixes.mdx                    |    2 +-
 .../data-center-protection/concepts/index.mdx |    2 +-
 .../data-center-protection/configure-ddos.mdx |   14 +-
 .../configure-routes.mdx                      |   18 +-
 .../configure-tunnels.mdx                     |   29 +-
 .../configure-tunnels-routes/index.mdx        |    2 +-
 .../enable-notifications.mdx                  |    5 +-
 .../data-center-protection/get-started.mdx    |    8 +-
 .../run-pre-flight-checks.mdx                 |    1 -
 .../dns-best-practices/concepts/index.mdx     |    8 +-
 .../dns-best-practices/concepts/phase-1.mdx   |   52 +-
 .../dns-best-practices/concepts/phase-2.mdx   |   42 +-
 .../dns-best-practices/concepts/phase-3.mdx   |   31 +-
 .../dns-best-practices/concepts/phase-4.mdx   |   38 +-
 .../concepts/summary-considerations.mdx       |   20 +-
 .../holistic-ai-security/appendix/index.mdx   |    1 +
 .../holistic-ai-security/concepts/index.mdx   |    1 +
 .../holistic-ai-security/concepts/mcp.mdx     |    1 +
 .../concepts/shadow-ai.mdx                    |    1 +
 .../get-started/additional-setup.mdx          |    2 +-
 .../get-started/define-ai-risk-tolerance.mdx  |    1 -
 .../get-started/index.mdx                     |    2 +-
 .../monitor-ai-use/index.mdx                  |    1 +
 .../monitor-prompts-responses.mdx             |    3 +-
 .../monitor-ai-use/review-inline-ai-use.mdx   |    3 +-
 .../load-balancing/concepts/health-checks.mdx |    2 +-
 .../load-balancing/concepts/index.mdx         |    8 +-
 .../concepts/load-balancer-components.mdx     |   12 +-
 .../load-balancing/concepts/routing.mdx       |    8 +-
 .../load-balancing/planning/custom-rules.mdx  |    2 +-
 .../load-balancing/planning/index.mdx         |    8 +-
 .../planning/multiple-zones.mdx               |    2 +
 .../planning/origin-steering-policies.mdx     |    6 +-
 .../planning/session-affinity.mdx             |    2 +-
 .../planning/traffic-steering.mdx             |    4 +-
 .../planning/types-load-balancers.mdx         |   16 +-
 .../setup/check-pool-health.mdx               |    2 +-
 .../setup/hostname-preparation.mdx            |    8 +-
 .../load-balancing/setup/index.mdx            |   14 +-
 .../load-balancing/setup/next-steps.mdx       |    2 +-
 .../setup/production-traffic.mdx              |    2 +-
 .../mtls/concepts/mtls-cloudflare.mdx         |   12 +-
 .../mtls/mtls-implementation/index.mdx        |    2 +-
 .../advanced/improve-analytics.mdx            |    2 +-
 .../prevent-ddos-attacks/advanced/index.mdx   |    8 +-
 .../prevent-ddos-attacks/baseline/index.mdx   |    6 +-
 .../baseline/proxy-dns-records.mdx            |    2 +-
 .../baseline/set-up-alerts.mdx                |    2 +-
 .../baseline/tls-versions.mdx                 |    4 +-
 .../prevent-ddos-attacks/concepts/index.mdx   |    4 +-
 .../replace-vpn/build-policies/index.mdx      |    8 +-
 .../build-policies/policy-design.mdx          |   10 +-
 .../build-policies/session-timeouts.mdx       |    2 +-
 .../test-your-first-application.mdx           |    7 +-
 .../replace-vpn/concepts/index.mdx            |    6 +-
 .../concepts/what-is-cloudflare.mdx           |    2 +-
 .../connect-private-network/cloudflared.mdx   |   19 +-
 .../connection-methods.mdx                    |   22 +-
 .../connect-private-network/index.mdx         |    6 +-
 .../overlapping-ips.mdx                       |    2 +-
 .../tunnel-capacity.mdx                       |    2 +-
 .../replace-vpn/get-started/prerequisites.mdx |    8 +-
 .../replace-vpn/troubleshooting/index.mdx     |    4 +-
 .../troubleshoot-private-networks.mdx         |    2 +-
 .../build-dns-policies/index.mdx              |    6 +-
 .../build-egress-policies/index.mdx           |    8 +-
 .../build-http-policies/index.mdx             |    8 +-
 .../concepts/index.mdx                        |    4 +-
 .../choose-on-ramp.mdx                        |   12 +-
 .../initial-setup/prerequisites.mdx           |    4 +-
 .../secure-saas-applications/index.mdx        |    6 +-
 .../sso-front-door.mdx                        |   10 +-
 .../understand-policies/index.mdx             |    6 +-
 .../understand-policies/indicator-feeds.mdx   |    4 +-
 .../order-of-enforcement.mdx                  |    2 +-
 .../secure-your-email/concepts/index.mdx      |    2 +-
 .../protect-from-phishing-attacks.mdx         |    2 +-
 .../concepts/what-is-cloudflare.mdx           |    4 +-
 .../concepts/what-is-email-security.mdx       |    2 +-
 .../concepts/what-is-phishing-attack.mdx      |    2 +-
 .../active-directory-sync.mdx                 |    2 +-
 .../configure-email-security/audit-logs.mdx   |    3 +-
 .../impersonation-registry.mdx                |    2 +-
 .../configure-email-security/index.mdx        |    2 +-
 .../configure-email-security/report-phish.mdx |    2 +-
 .../enable-auto-moves/index.mdx               |    2 +-
 .../get-started/deployment-models.mdx         |    4 +-
 .../get-started/prerequisites.mdx             |    2 +-
 .../recommended-deployment-model.mdx          |    2 +-
 .../get-started/setup-google-workspace.mdx    |    2 +-
 .../get-started/setup-ms-graph-api.mdx        |    4 +-
 .../monitor-your-inbox/phish-submissions.mdx  |    2 +-
 .../surge-readiness/concepts/index.mdx        |   12 +-
 .../surge-readiness/performance/analytics.mdx |    4 +-
 .../surge-readiness/performance/caching.mdx   |   22 +-
 .../surge-readiness/performance/index.mdx     |    2 +-
 .../surge-readiness/performance/logs.mdx      |    7 +-
 .../security/block-agents-lock-zones.mdx      |    1 +
 .../security/confirm-account-security.mdx     |    2 +-
 .../security/control-domain-access.mdx        |   12 +-
 .../surge-readiness/security/enable-iaum.mdx  |    4 +-
 .../surge-readiness/security/index.mdx        |    2 +-
 .../surge-readiness/support/index.mdx         |    2 +-
 .../surge-readiness/support/resources.mdx     |   15 +-
 .../workers/concepts/cloudflare-intro.mdx     |   30 +-
 .../learning-paths/workers/concepts/index.mdx |    6 +-
 .../workers/concepts/serverless-computing.mdx |    6 +-
 .../learning-paths/workers/devplat/index.mdx  |    4 +-
 .../workers/devplat/intro-to-devplat.mdx      |    2 +-
 .../workers/get-started/c3-and-wrangler.mdx   |    8 +-
 .../workers/get-started/first-application.mdx |   23 +-
 .../workers/get-started/index.mdx             |    6 +-
 .../additional-dns-records.mdx                |    5 +-
 .../additional-options/cloudflare-tunnel.mdx  |    1 +
 .../additional-options/index.mdx              |   13 +-
 .../load-balancing-china.mdx                  |    1 +
 .../load-balancing-rules/expressions.mdx      |   13 +-
 .../override-http-host-headers.mdx            |   30 +-
 .../pagerduty-integration.mdx                 |    1 +
 .../planned-maintenance.mdx                   |   12 +-
 .../docs/load-balancing/api-reference.mdx     |    1 +
 .../get-started/enable-load-balancing.mdx     |    3 +-
 .../docs/load-balancing/get-started/index.mdx |    5 +-
 .../load-balancers/common-configurations.mdx  |    7 +-
 .../docs/load-balancing/monitors/index.mdx    |    4 +-
 .../monitors/monitor-groups.mdx               |    1 +
 .../private-network/cloudflare-wan.mdx        |    6 +-
 .../reference-architecture-external-link.mdx  |    1 +
 .../docs/load-balancing/reference/index.mdx   |    3 +-
 .../load-balancing/reference/limitations.mdx  |   15 +-
 .../reference/migration-guides/index.mdx      |    3 +-
 .../troubleshooting/common-error-codes.mdx    |   53 +-
 .../load-balancing/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/load-balancing-faq.mdx    |   37 +-
 .../understand-basics/adaptive-routing.mdx    |    3 +-
 .../understand-basics/index.mdx               |    3 +-
 .../traffic-steering/index.mdx                |    1 +
 .../hash-origin-steering.mdx                  |    4 +
 .../least-outstanding-requests-pools.mdx      |    7 +-
 .../random-origin-steering.mdx                |    1 +
 .../steering-policies/dynamic-steering.mdx    |    1 +
 .../steering-policies/index.mdx               |    1 -
 .../least-outstanding-requests.mdx            |    3 +-
 .../steering-policies/proximity-steering.mdx  |    9 +-
 .../steering-policies/standard-options.mdx    |    1 +
 src/content/docs/log-explorer/api.mdx         |    6 +-
 src/content/docs/log-explorer/changelog.mdx   |    2 +-
 .../docs/log-explorer/example-queries.mdx     |    2 +-
 src/content/docs/log-explorer/index.mdx       |   42 +-
 .../docs/logs/auditlogs-mcp-server.mdx        |    2 +-
 .../docs/logs/changelog/audit-logs.mdx        |    2 +-
 src/content/docs/logs/changelog/index.mdx     |    2 +-
 src/content/docs/logs/changelog/logs.mdx      |    2 +
 .../docs/logs/faq/common-calculations.mdx     |    2 +
 src/content/docs/logs/faq/general-faq.mdx     |    3 +
 src/content/docs/logs/faq/instant-logs.mdx    |    3 +
 src/content/docs/logs/faq/logpull-api.mdx     |    5 +
 .../docs/logs/faq/worker-subrequests.mdx      |   14 +-
 src/content/docs/logs/glossary.mdx            |    2 +-
 src/content/docs/logs/logpull/index.mdx       |    4 +-
 .../docs/logs/logpull/requesting-logs.mdx     |   22 +-
 .../logs/logpull/understanding-the-basics.mdx |   24 +-
 src/content/docs/logs/logpush-mcp-server.mdx  |    2 +-
 .../examples/example-logpush-python.mdx       |    2 +
 .../docs/logs/logpush/examples/index.mdx      |    2 +-
 src/content/docs/logs/logpush/index.mdx       |    4 +-
 .../docs/logs/logpush/logpush-health.mdx      |   72 +-
 .../logpush/logpush-job/api-configuration.mdx |  140 +-
 .../logpush-job/datasets/account/index.mdx    |    2 +-
 .../logs/logpush/logpush-job/datasets/cmb.mdx |    4 +-
 .../logpush/logpush-job/datasets/index.mdx    |   16 +-
 .../logpush-job/datasets/zone/dns_logs.md     |    2 +-
 .../logpush-job/datasets/zone/index.mdx       |    2 +-
 .../logpush/logpush-job/edge-log-delivery.mdx |    3 +-
 .../enable-destinations/aws-s3.mdx            |    6 +-
 .../logpush-job/enable-destinations/azure.mdx |    1 -
 .../enable-destinations/egress-ip.mdx         |   26 +-
 .../enable-destinations/elastic.mdx           |   33 +-
 .../google-cloud-storage.mdx                  |    6 +-
 .../enable-destinations/ibm-qradar.mdx        |  150 +--
 .../enable-destinations/kinesis.mdx           |    2 +-
 .../third-party/exabeam.mdx                   |    2 +-
 .../third-party/sekoia.mdx                    |    2 +-
 .../third-party/taegis.mdx                    |    2 +-
 .../docs/logs/logpush/logpush-job/filters.mdx |    5 +-
 .../docs/logs/logpush/logpush-job/index.mdx   |    2 +-
 .../logpush-ownership-challenge.mdx           |   22 +-
 .../2023-02-01-security-fields-updates.mdx    |   66 +-
 .../logs/reference/change-notices/index.mdx   |    2 +-
 .../logs/reference/clientrequestsource.mdx    |    3 +
 src/content/docs/logs/reference/index.mdx     |    2 +-
 .../docs/logs/reference/security-fields.mdx   |    8 +-
 .../docs/logs/reference/waf-fields.mdx        |    8 +-
 src/content/docs/magic-transit/about.mdx      |    3 +-
 src/content/docs/magic-transit/alerts.mdx     |    3 +-
 .../docs/magic-transit/analytics/index.mdx    |    9 +-
 .../analytics/network-analytics.mdx           |    6 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 src/content/docs/magic-transit/changelog.mdx  |    5 +-
 .../docs/magic-transit/cloudflare-ips.mdx     |   17 +-
 .../docs/magic-transit/get-started.mdx        |    8 +-
 src/content/docs/magic-transit/glossary.mdx   |    3 +-
 .../how-to/advertise-prefixes.mdx             |   56 +-
 .../magic-transit/how-to/configure-routes.mdx |   18 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   28 +-
 .../how-to/enable-magic-roles.mdx             |    2 +-
 .../docs/magic-transit/how-to/index.mdx       |    5 +-
 .../how-to/safely-withdraw-byoip-prefix.mdx   |    7 +-
 .../docs/magic-transit/network-flow.mdx       |    5 +-
 .../check-tunnel-health-dashboard.mdx         |   12 +-
 .../configure-tunnel-health-alerts.mdx        |    5 +-
 .../magic-transit/network-health/index.mdx    |   16 +-
 .../run-endpoint-health-checks.mdx            |   75 +-
 .../update-tunnel-health-checks-frequency.mdx |    7 +-
 .../magic-transit/network-interconnect.mdx    |    2 +-
 src/content/docs/magic-transit/on-demand.mdx  |    1 +
 .../docs/magic-transit/partners/index.mdx     |    5 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/gre-ipsec-tunnels.mdx           |    3 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/magic-transit/reference/index.mdx    |    5 +-
 .../docs/magic-transit/reference/mtu-mss.mdx  |    4 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    5 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../magic-transit/troubleshooting/index.mdx   |    2 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   12 +-
 .../troubleshooting/routing-and-bgp.mdx       |   21 +-
 .../troubleshooting/tunnel-health.mdx         |   29 +-
 src/content/docs/moq/feature-matrix.mdx       |  121 +-
 src/content/docs/moq/index.mdx                |   15 +-
 .../docs/multi-cloud-networking/changelog.mdx |    5 +-
 .../multi-cloud-networking/cloud-on-ramps.mdx |   11 +-
 .../multi-cloud-networking/get-started.mdx    |   74 +-
 .../manage-resources.mdx                      |    7 +-
 .../docs/multi-cloud-networking/reference.mdx |    1 +
 .../network-error-logging/get-started.mdx     |    3 +-
 .../docs/network-error-logging/how-to.mdx     |   11 +-
 .../docs/network-error-logging/index.mdx      |   45 +-
 src/content/docs/network-flow/api.mdx         |    5 +-
 src/content/docs/network-flow/changelog.mdx   |    5 +-
 .../docs/network-flow/cloud-flow-logs.mdx     |    2 +-
 src/content/docs/network-flow/faq.mdx         |    4 +-
 src/content/docs/network-flow/get-started.mdx |    2 +-
 src/content/docs/network-flow/glossary.mdx    |    3 +-
 .../magic-transit-integration.mdx             |    5 +-
 .../docs/network-flow/network-flow-free.mdx   |    2 +-
 .../docs/network-flow/routers/index.mdx       |    5 +-
 .../routers/netflow-ipfix-config.mdx          |    3 +-
 .../routers/recommended-sampling-rate.mdx     |    3 +-
 .../network-flow/routers/sflow-config.mdx     |    5 +-
 .../routers/supported-routers.mdx             |    5 +-
 src/content/docs/network-flow/rules/index.mdx |    1 +
 .../network-flow/rules/rule-notifications.mdx |    2 +-
 .../network-flow/rules/s-flow-ddos-attack.mdx |    2 +-
 .../network-flow/rules/static-threshold.mdx   |    2 +-
 .../tutorials/ddos-testing-guide.mdx          |    2 +-
 .../tutorials/encrypt-network-flow-data.mdx   |    5 +-
 .../tutorials/graphql-analytics.mdx           |    2 +-
 .../docs/network-flow/tutorials/index.mdx     |    5 +-
 .../docs/network-interconnect/changelog.mdx   |    5 +-
 .../docs/network-interconnect/get-started.mdx |   49 +-
 .../docs/network-interconnect/index.mdx       |   38 +-
 .../monitoring-and-alerts.mdx                 |   10 +-
 .../operational-guidance.mdx                  |    2 +-
 src/content/docs/network/index.mdx            |   36 +-
 src/content/docs/network/websockets.mdx       |    1 +
 .../get-started/configure-pagerduty.mdx       |   14 +-
 .../docs/notifications/get-started/index.mdx  |   27 +-
 src/content/docs/notifications/index.mdx      |    5 +-
 .../notifications/notification-available.mdx  |    2 +-
 .../notifications/notification-history.mdx    |    2 +-
 .../docs/notifications/reference/index.mdx    |    2 +-
 .../reference/traffic-alerts.mdx              |    2 +-
 src/content/docs/pages/configuration/api.mdx  |    1 -
 .../pages/configuration/build-caching.mdx     |   18 +-
 .../docs/pages/configuration/build-image.mdx  |    6 +-
 .../docs/pages/configuration/deploy-hooks.mdx |    1 -
 .../deploy-a-vite3-project.mdx                |    1 -
 .../docs/pages/functions/api-reference.mdx    |    8 +
 src/content/docs/pages/functions/bindings.mdx |   22 +-
 .../pages/functions/examples/ab-testing.mdx   |    1 +
 .../pages/functions/examples/cors-headers.mdx |    1 +
 .../docs/pages/functions/examples/index.mdx   |    1 +
 src/content/docs/pages/functions/metrics.mdx  |    1 -
 .../functions/plugins/community-plugins.mdx   |    1 +
 src/content/docs/pages/get-started/c3.mdx     |   23 +
 .../docs/pages/get-started/direct-upload.mdx  |    2 +-
 .../pages/get-started/git-integration.mdx     |    1 +
 src/content/docs/pages/get-started/index.mdx  |    1 +
 .../pages/how-to/add-custom-http-headers.mdx  |    1 +
 .../pages/how-to/build-commands-branches.mdx  |    2 +-
 .../pages/how-to/custom-branch-aliases.mdx    |    2 +-
 .../docs/pages/how-to/enable-zaraz.mdx        |    1 +
 src/content/docs/pages/how-to/index.mdx       |    2 +
 .../pages/how-to/npm-private-registry.mdx     |    1 +
 .../how-to/preview-with-cloudflare-tunnel.mdx |    1 +
 .../refactor-a-worker-to-pages-functions.mdx  |    1 +
 ...ect-upload-with-continuous-integration.mdx |    4 +-
 .../use-worker-for-ab-testing-in-pages.mdx    |    2 +-
 .../docs/pages/how-to/web-analytics.mdx       |    2 +-
 src/content/docs/pages/migrations/index.mdx   |    2 +
 src/content/docs/pages/platform/index.mdx     |    1 +
 .../docs/pages/platform/known-issues.mdx      |    3 +-
 src/content/docs/pages/platform/limits.mdx    |    7 +-
 .../add-a-react-form-with-formspree.mdx       |    2 +-
 .../build-a-blog-using-nuxt-and-sanity.mdx    |    1 -
 .../pipelines/reference/wrangler-commands.mdx |    3 +-
 .../docs/pipelines/sinks/manage-sinks.mdx     |    2 +-
 .../sql-reference/scalar-functions/string.mdx |    1 +
 .../docs/privacy-gateway/get-started.mdx      |   32 +-
 .../docs/privacy-gateway/reference/index.mdx  |    2 +-
 .../docs/privacy-gateway/reference/legal.mdx  |    4 +-
 .../privacy-gateway/reference/metrics.mdx     |  132 +-
 .../reference/product-compatibility.mdx       |    6 +-
 .../privacy-proxy/concepts/authentication.mdx |   12 +-
 .../concepts/deployment-models.mdx            |   26 +-
 .../privacy-proxy/concepts/geolocation.mdx    |   12 +-
 .../privacy-proxy/concepts/how-it-works.mdx   |   17 +-
 .../docs/privacy-proxy/get-started.mdx        |    2 +-
 .../privacy-proxy/reference/http-headers.mdx  |   32 +-
 .../privacy-proxy/reference/proxy-status.mdx  |   52 +-
 src/content/docs/pulumi/tutorial/index.mdx    |    3 +
 .../queues/configuration/configure-queues.mdx |   82 +-
 .../configuration/consumer-concurrency.mdx    |    2 +-
 .../docs/queues/configuration/index.mdx       |    2 +-
 .../queues/configuration/javascript-apis.mdx  |  243 ++--
 .../configuration/local-development.mdx       |    7 +-
 .../docs/queues/configuration/pause-purge.mdx |    6 -
 .../docs/queues/event-subscriptions/index.mdx |    4 +-
 .../manage-event-subscriptions.mdx            |    8 +-
 .../examples/publish-to-a-queue-via-http.mdx  |    1 +
 .../publish-to-a-queue-via-workers.mdx        |    5 +-
 .../queues/examples/send-errors-to-r2.mdx     |   50 +-
 .../examples/send-messages-from-dash.mdx      |    6 +-
 .../use-queues-with-durable-objects.mdx       |   68 +-
 src/content/docs/queues/glossary.mdx          |    2 +-
 .../docs/queues/observability/index.mdx       |    2 +-
 .../docs/queues/observability/metrics.mdx     |    8 +-
 src/content/docs/queues/platform/index.mdx    |    2 +-
 src/content/docs/queues/platform/limits.mdx   |   57 +-
 src/content/docs/queues/platform/pricing.mdx  |    9 +-
 .../queues/reference/delivery-guarantees.mdx  |    6 +-
 .../docs/queues/reference/error-codes.mdx     |   52 +-
 .../queues/reference/how-queues-works.mdx     |  148 +--
 src/content/docs/queues/reference/index.mdx   |    2 +-
 .../reference/limitations-best-practices.mdx  |   68 +-
 .../r2-sql/reference/wrangler-commands.mdx    |    2 +-
 .../docs/r2-sql/sql-reference/index.mdx       |   18 +-
 src/content/docs/r2/api/error-codes.mdx       |   88 +-
 src/content/docs/r2/api/index.mdx             |    2 +-
 src/content/docs/r2/api/s3/extensions.mdx     |   18 +-
 src/content/docs/r2/api/s3/presigned-urls.mdx |   11 +-
 .../docs/r2/api/s3/temporary-credentials.mdx  |   54 +-
 .../r2/api/workers/workers-api-reference.mdx  |   78 +-
 .../docs/r2/api/workers/workers-api-usage.mdx |    1 -
 src/content/docs/r2/buckets/bucket-locks.mdx  |    3 -
 src/content/docs/r2/buckets/cors.mdx          |   45 +-
 .../docs/r2/buckets/delete-buckets.mdx        |   26 +-
 .../docs/r2/buckets/event-notifications.mdx   |   33 +-
 src/content/docs/r2/buckets/index.mdx         |    2 +-
 .../docs/r2/buckets/object-lifecycles.mdx     |    2 -
 .../docs/r2/buckets/storage-classes.mdx       |   32 +-
 src/content/docs/r2/data-migration/index.mdx  |    2 +-
 .../data-migration/migration-strategies.mdx   |    2 +-
 src/content/docs/r2/data-migration/sippy.mdx  |   18 +-
 .../docs/r2/data-migration/super-slurper.mdx  |    7 +-
 .../examples/authenticate-r2-auth-tokens.mdx  |    2 +-
 .../authenticate-r2-temp-credentials.mdx      |  174 +--
 .../docs/r2/examples/aws/aws-sdk-js-v3.mdx    |   19 +-
 .../docs/r2/examples/aws/aws-sdk-js.mdx       |   25 +-
 .../docs/r2/examples/aws/aws-sdk-kotlin.mdx   |    1 +
 .../docs/r2/examples/aws/aws4fetch.mdx        |   15 +-
 src/content/docs/r2/examples/aws/boto3.mdx    |   15 +-
 .../docs/r2/examples/aws/custom-header.mdx    |   95 +-
 src/content/docs/r2/examples/cache-api.mdx    |  109 +-
 src/content/docs/r2/examples/terraform.mdx    |    7 +-
 src/content/docs/r2/get-started/cli.mdx       |    9 +-
 src/content/docs/r2/get-started/index.mdx     |    1 -
 src/content/docs/r2/get-started/s3.mdx        |    9 +-
 .../docs/r2/get-started/workers-api.mdx       |    2 +-
 .../docs/r2/objects/delete-objects.mdx        |   19 +-
 .../docs/r2/objects/download-objects.mdx      |    3 +-
 src/content/docs/r2/objects/index.mdx         |    4 +-
 src/content/docs/r2/platform/audit-logs.mdx   |   59 +-
 .../docs/r2/platform/metrics-analytics.mdx    |    7 +-
 .../docs/r2/platform/troubleshooting.mdx      |    5 +-
 src/content/docs/r2/pricing.mdx               |   52 +-
 src/content/docs/r2/r2-sql.mdx                |    2 +-
 .../docs/r2/reference/data-location.mdx       |    2 -
 .../docs/r2/reference/data-security.mdx       |    2 +
 src/content/docs/r2/reference/durability.mdx  |   10 +-
 .../r2/reference/unicode-interoperability.mdx |    6 +-
 .../docs/r2/tutorials/cloudflare-access.mdx   |    2 +-
 src/content/docs/r2/tutorials/mastodon.mdx    |    3 +-
 src/content/docs/r2/tutorials/postman.mdx     |   12 +-
 src/content/docs/r2/video-tutorials.mdx       |   10 +-
 src/content/docs/radar/concepts/index.mdx     |    2 +-
 .../docs/radar/concepts/normalization.mdx     |    2 +-
 .../radar/get-started/configure-alerts.mdx    |    2 +-
 src/content/docs/radar/get-started/embed.mdx  |    4 +-
 src/content/docs/radar/get-started/index.mdx  |    2 +-
 .../radar/get-started/making-comparisons.mdx  |   78 +-
 .../investigate/application-layer-attacks.mdx |   84 +-
 src/content/docs/radar/investigate/dns.mdx    |   26 +-
 .../investigate/domain-ranking-datasets.mdx   |   37 +-
 .../docs/radar/investigate/http-requests.mdx  |   76 +-
 src/content/docs/radar/investigate/index.mdx  |    2 +-
 .../docs/radar/investigate/netflows.mdx       |   18 +-
 .../investigate/network-layer-attacks.mdx     |   86 +-
 .../docs/radar/investigate/outages.mdx        |   14 +-
 .../docs/radar/investigate/url-scanner.mdx    |   88 +-
 src/content/docs/radar/mcp-server.mdx         |    2 +-
 src/content/docs/radar/reference/index.mdx    |    2 +-
 .../reference/quarterly-ddos-reports.mdx      |    6 +-
 .../randomness-beacon/about/background.mdx    |    2 +-
 .../docs/randomness-beacon/about/future.mdx   |    6 +-
 .../cryptographic-background/index.mdx        |    6 +-
 .../randomness-generation.mdx                 |    6 +-
 .../cryptographic-background/setup-phase.mdx  |    4 +-
 src/content/docs/realtime/agents/index.mdx    |    4 +-
 .../docs/realtime/realtimekit/ai/index.mdx    |    2 +-
 .../docs/realtime/realtimekit/ai/summary.mdx  |   69 +-
 .../realtime/realtimekit/ai/transcription.mdx |    2 +-
 .../realtimekit/core/api-reference/RTKAi.md   |   40 +-
 .../realtimekit/core/api-reference/RTKChat.md |  329 +++--
 .../api-reference/RTKConnectedMeetings.md     |   81 +-
 .../core/api-reference/RTKLivestream.md       |   46 +-
 .../realtimekit/core/api-reference/RTKMeta.md |   68 +-
 .../core/api-reference/RTKParticipant.md      |  188 ++-
 .../core/api-reference/RTKParticipantMap.md   |   56 +-
 .../core/api-reference/RTKParticipants.md     |  240 ++--
 .../api-reference/RTKPermissionsPreset.md     |  143 +--
 .../realtimekit/core/api-reference/RTKPip.md  |   72 +-
 .../core/api-reference/RTKPlugin.md           |  122 +-
 .../core/api-reference/RTKPlugins.md          |   21 +-
 .../core/api-reference/RTKPolls.md            |   33 +-
 .../core/api-reference/RTKRecording.md        |   20 +-
 .../realtimekit/core/api-reference/RTKSelf.md |  109 +-
 .../core/api-reference/RTKSelfMedia.md        |   77 +-
 .../core/api-reference/RTKStage.md            |   63 +-
 .../core/api-reference/RTKStore.md            |  167 ++-
 .../core/api-reference/RTKThemePreset.md      |   89 +-
 .../core/api-reference/RealtimeKitClient.md   |  129 +-
 .../realtime/realtimekit/legal/3rdparty.mdx   |   99 +-
 .../recording-guide/add-watermark.mdx         |   20 +-
 .../recording-guide/configure-codecs.mdx      |    6 +-
 .../recording-guide/monitor-status.mdx        |   12 +-
 .../recording-guide/track-recording.mdx       |   69 +-
 .../ui-kit/api-reference/angular/index.mdx    |    2 +-
 .../api-reference/angular/rtk-ai-toggle.mdx   |   24 +-
 .../angular/rtk-ai-transcriptions.mdx         |   16 +-
 .../ui-kit/api-reference/angular/rtk-ai.mdx   |   26 +-
 .../api-reference/angular/rtk-audio-grid.mdx  |   27 +-
 .../api-reference/angular/rtk-audio-tile.mdx  |   27 +-
 .../angular/rtk-audio-visualizer.mdx          |   29 +-
 .../api-reference/angular/rtk-avatar.mdx      |   22 +-
 .../angular/rtk-breakout-room-manager.mdx     |   33 +-
 .../rtk-breakout-room-participants.mdx        |   25 +-
 .../angular/rtk-breakout-rooms-manager.mdx    |   18 +-
 .../angular/rtk-breakout-rooms-toggle.mdx     |   27 +-
 .../angular/rtk-broadcast-message-modal.mdx   |   18 +-
 .../api-reference/angular/rtk-button.mdx      |   23 +-
 .../angular/rtk-camera-selector.mdx           |   40 +-
 .../angular/rtk-camera-toggle.mdx             |   21 +-
 .../angular/rtk-caption-toggle.mdx            |   25 +-
 .../angular/rtk-chat-composer-ui.mdx          |   25 +-
 .../angular/rtk-chat-composer-view.mdx        |   35 +-
 .../api-reference/angular/rtk-chat-header.mdx |    4 +-
 .../angular/rtk-chat-message.mdx              |   45 +-
 .../rtk-chat-messages-ui-paginated.mdx        |   23 +-
 .../angular/rtk-chat-messages-ui.mdx          |   27 +-
 .../angular/rtk-chat-search-results.mdx       |   23 +-
 .../angular/rtk-chat-selector-ui.mdx          |   25 +-
 .../angular/rtk-chat-selector.mdx             |   25 +-
 .../api-reference/angular/rtk-chat-toggle.mdx |   37 +-
 .../ui-kit/api-reference/angular/rtk-chat.mdx |   23 +-
 .../api-reference/angular/rtk-clock.mdx       |   17 +-
 .../angular/rtk-confirmation-modal.mdx        |   18 +-
 .../angular/rtk-controlbar-button.mdx         |   29 +-
 .../api-reference/angular/rtk-controlbar.mdx  |   27 +-
 .../api-reference/angular/rtk-counter.mdx     |   22 +-
 .../angular/rtk-debugger-audio.mdx            |   21 +-
 .../angular/rtk-debugger-screenshare.mdx      |   20 +-
 .../angular/rtk-debugger-system.mdx           |   21 +-
 .../angular/rtk-debugger-toggle.mdx           |   23 +-
 .../angular/rtk-debugger-video.mdx            |   21 +-
 .../api-reference/angular/rtk-debugger.mdx    |   21 +-
 .../angular/rtk-dialog-manager.mdx            |   36 +-
 .../api-reference/angular/rtk-dialog.mdx      |   31 +-
 .../angular/rtk-emoji-picker-button.mdx       |   16 +-
 .../angular/rtk-emoji-picker.mdx              |   16 +-
 .../angular/rtk-ended-screen.mdx              |   23 +-
 .../angular/rtk-file-dropzone.mdx             |   16 +-
 .../angular/rtk-file-message-view.mdx         |   19 +-
 .../angular/rtk-file-message.mdx              |   25 +-
 .../angular/rtk-file-picker-button.mdx        |   23 +-
 .../angular/rtk-fullscreen-toggle.mdx         |   25 +-
 .../angular/rtk-grid-pagination.mdx           |   27 +-
 .../ui-kit/api-reference/angular/rtk-grid.mdx |   34 +-
 .../api-reference/angular/rtk-header.mdx      |   28 +-
 .../ui-kit/api-reference/angular/rtk-icon.mdx |   18 +-
 .../api-reference/angular/rtk-idle-screen.mdx |   20 +-
 .../angular/rtk-image-message-view.mdx        |   16 +-
 .../angular/rtk-image-message.mdx             |   25 +-
 .../angular/rtk-image-viewer.mdx              |   19 +-
 .../angular/rtk-information-tooltip.mdx       |   11 +-
 .../api-reference/angular/rtk-join-stage.mdx  |   25 +-
 .../angular/rtk-leave-button.mdx              |   19 +-
 .../angular/rtk-leave-meeting.mdx             |   20 +-
 .../angular/rtk-livestream-indicator.mdx      |   18 +-
 .../angular/rtk-livestream-player.mdx         |   19 +-
 .../angular/rtk-livestream-toggle.mdx         |   21 +-
 .../ui-kit/api-reference/angular/rtk-logo.mdx |   19 +-
 .../angular/rtk-markdown-view.mdx             |   15 +-
 .../angular/rtk-meeting-title.mdx             |   16 +-
 .../api-reference/angular/rtk-meeting.mdx     |   43 +-
 .../api-reference/angular/rtk-menu-item.mdx   |   18 +-
 .../api-reference/angular/rtk-menu-list.mdx   |   16 +-
 .../ui-kit/api-reference/angular/rtk-menu.mdx |   22 +-
 .../angular/rtk-message-list-view.mdx         |   25 +-
 .../angular/rtk-message-view.mdx              |   39 +-
 .../api-reference/angular/rtk-mic-toggle.mdx  |   21 +-
 .../angular/rtk-microphone-selector.mdx       |   40 +-
 .../api-reference/angular/rtk-mixed-grid.mdx  |   40 +-
 .../api-reference/angular/rtk-more-toggle.mdx |   29 +-
 .../angular/rtk-mute-all-button.mdx           |   21 +-
 .../angular/rtk-mute-all-confirmation.mdx     |   18 +-
 .../api-reference/angular/rtk-name-tag.mdx    |   27 +-
 .../angular/rtk-network-indicator.mdx         |   23 +-
 .../angular/rtk-notification.mdx              |   25 +-
 .../angular/rtk-notifications.mdx             |   27 +-
 .../angular/rtk-overlay-modal.mdx             |   18 +-
 .../angular/rtk-paginated-list.mdx            |   33 +-
 .../angular/rtk-participant-count.mdx         |   19 +-
 .../angular/rtk-participant-setup.mdx         |   31 +-
 .../angular/rtk-participant-tile.mdx          |   37 +-
 .../api-reference/angular/rtk-participant.mdx |   31 +-
 .../angular/rtk-participants-audio.mdx        |   19 +-
 .../angular/rtk-participants-stage-list.mdx   |   33 +-
 .../angular/rtk-participants-stage-queue.mdx  |   25 +-
 .../angular/rtk-participants-toggle.mdx       |   35 +-
 .../angular/rtk-participants-viewer-list.mdx  |   29 +-
 .../angular/rtk-participants-waiting-list.mdx |   25 +-
 .../angular/rtk-participants.mdx              |   29 +-
 .../angular/rtk-permissions-message.mdx       |   20 +-
 .../angular/rtk-pinned-message-selector.mdx   |   16 +-
 .../api-reference/angular/rtk-pip-toggle.mdx  |   25 +-
 .../api-reference/angular/rtk-plugin-main.mdx |   19 +-
 .../angular/rtk-plugins-toggle.mdx            |   35 +-
 .../api-reference/angular/rtk-plugins.mdx     |   23 +-
 .../api-reference/angular/rtk-poll-form.mdx   |   15 +-
 .../ui-kit/api-reference/angular/rtk-poll.mdx |   23 +-
 .../angular/rtk-polls-toggle.mdx              |   37 +-
 .../api-reference/angular/rtk-polls.mdx       |   23 +-
 .../angular/rtk-recording-indicator.mdx       |   20 +-
 .../angular/rtk-recording-toggle.mdx          |   29 +-
 .../angular/rtk-screen-share-toggle.mdx       |   23 +-
 .../angular/rtk-screenshare-view.mdx          |   35 +-
 .../angular/rtk-settings-audio.mdx            |   38 +-
 .../angular/rtk-settings-toggle.mdx           |   32 +-
 .../angular/rtk-settings-video.mdx            |   38 +-
 .../api-reference/angular/rtk-settings.mdx    |   23 +-
 .../angular/rtk-setup-screen.mdx              |   25 +-
 .../api-reference/angular/rtk-sidebar-ui.mdx  |   29 +-
 .../api-reference/angular/rtk-sidebar.mdx     |   33 +-
 .../api-reference/angular/rtk-simple-grid.mdx |   29 +-
 .../angular/rtk-speaker-selector.mdx          |   42 +-
 .../api-reference/angular/rtk-spinner.mdx     |   14 +-
 .../angular/rtk-spotlight-grid.mdx            |   42 +-
 .../angular/rtk-spotlight-indicator.mdx       |   18 +-
 .../angular/rtk-stage-toggle.mdx              |   23 +-
 .../api-reference/angular/rtk-stage.mdx       |   17 +-
 .../api-reference/angular/rtk-switch.mdx      |   22 +-
 .../api-reference/angular/rtk-tab-bar.mdx     |   29 +-
 .../angular/rtk-text-composer-view.mdx        |   31 +-
 .../angular/rtk-text-message-view.mdx         |   14 +-
 .../angular/rtk-text-message.mdx              |   25 +-
 .../api-reference/angular/rtk-tooltip.mdx     |   28 +-
 .../api-reference/angular/rtk-transcript.mdx  |   19 +-
 .../api-reference/angular/rtk-transcripts.mdx |   22 +-
 .../api-reference/angular/rtk-ui-provider.mdx |   27 +-
 .../angular/rtk-viewer-count.mdx              |   19 +-
 .../rtk-virtualized-participant-list.mdx      |   23 +-
 .../angular/rtk-waiting-screen.mdx            |   18 +-
 .../ui-kit/api-reference/core/index.mdx       |    2 +-
 .../core/rtk-ai-transcriptions.mdx            |   21 +-
 .../ui-kit/api-reference/core/rtk-ai.mdx      |   28 +-
 .../api-reference/core/rtk-audio-grid.mdx     |   31 +-
 .../api-reference/core/rtk-audio-tile.mdx     |   31 +-
 .../core/rtk-audio-visualizer.mdx             |   33 +-
 .../ui-kit/api-reference/core/rtk-avatar.mdx  |   26 +-
 .../core/rtk-breakout-room-manager.mdx        |   37 +-
 .../core/rtk-breakout-room-participants.mdx   |   31 +-
 .../core/rtk-breakout-rooms-manager.mdx       |   21 +-
 .../core/rtk-breakout-rooms-toggle.mdx        |   30 +-
 .../core/rtk-broadcast-message-modal.mdx      |   21 +-
 .../ui-kit/api-reference/core/rtk-button.mdx  |   27 +-
 .../core/rtk-camera-selector.mdx              |   41 +-
 .../core/rtk-chat-composer-ui.mdx             |   28 +-
 .../core/rtk-chat-composer-view.mdx           |   37 +-
 .../api-reference/core/rtk-chat-header.mdx    |    4 +-
 .../api-reference/core/rtk-chat-message.mdx   |   51 +-
 .../core/rtk-chat-messages-ui-paginated.mdx   |   24 +-
 .../core/rtk-chat-messages-ui.mdx             |   30 +-
 .../core/rtk-chat-search-results.mdx          |   24 +-
 .../core/rtk-chat-selector-ui.mdx             |   26 +-
 .../api-reference/core/rtk-chat-selector.mdx  |   28 +-
 .../ui-kit/api-reference/core/rtk-chat.mdx    |   26 +-
 .../ui-kit/api-reference/core/rtk-clock.mdx   |   20 +-
 .../core/rtk-confirmation-modal.mdx           |   21 +-
 .../core/rtk-controlbar-button.mdx            |   34 +-
 .../api-reference/core/rtk-controlbar.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-counter.mdx |   26 +-
 .../api-reference/core/rtk-debugger-audio.mdx |   24 +-
 .../core/rtk-debugger-screenshare.mdx         |   24 +-
 .../core/rtk-debugger-system.mdx              |   24 +-
 .../api-reference/core/rtk-debugger-video.mdx |   24 +-
 .../api-reference/core/rtk-debugger.mdx       |   24 +-
 .../api-reference/core/rtk-dialog-manager.mdx |   39 +-
 .../ui-kit/api-reference/core/rtk-dialog.mdx  |   35 +-
 .../core/rtk-draft-attachment-view.mdx        |   19 +-
 .../core/rtk-emoji-picker-button.mdx          |   19 +-
 .../api-reference/core/rtk-emoji-picker.mdx   |   19 +-
 .../api-reference/core/rtk-ended-screen.mdx   |   26 +-
 .../api-reference/core/rtk-file-dropzone.mdx  |   18 +-
 .../core/rtk-file-message-view.mdx            |   23 +-
 .../api-reference/core/rtk-file-message.mdx   |   27 +-
 .../core/rtk-file-picker-button.mdx           |   24 +-
 .../core/rtk-grid-pagination.mdx              |   28 +-
 .../ui-kit/api-reference/core/rtk-grid.mdx    |   37 +-
 .../ui-kit/api-reference/core/rtk-header.mdx  |   32 +-
 .../ui-kit/api-reference/core/rtk-icon.mdx    |   21 +-
 .../api-reference/core/rtk-idle-screen.mdx    |   23 +-
 .../core/rtk-image-message-view.mdx           |   19 +-
 .../api-reference/core/rtk-image-message.mdx  |   27 +-
 .../api-reference/core/rtk-image-viewer.mdx   |   21 +-
 .../core/rtk-information-tooltip.mdx          |   15 +-
 .../api-reference/core/rtk-join-stage.mdx     |   28 +-
 .../api-reference/core/rtk-leave-meeting.mdx  |   23 +-
 .../core/rtk-livestream-indicator.mdx         |   22 +-
 .../core/rtk-livestream-player.mdx            |   22 +-
 .../ui-kit/api-reference/core/rtk-logo.mdx    |   22 +-
 .../api-reference/core/rtk-markdown-view.mdx  |   18 +-
 .../api-reference/core/rtk-meeting-title.mdx  |   19 +-
 .../ui-kit/api-reference/core/rtk-meeting.mdx |   45 +-
 .../api-reference/core/rtk-menu-item.mdx      |   21 +-
 .../api-reference/core/rtk-menu-list.mdx      |   18 +-
 .../ui-kit/api-reference/core/rtk-menu.mdx    |   24 +-
 .../core/rtk-message-list-view.mdx            |   27 +-
 .../api-reference/core/rtk-message-view.mdx   |   43 +-
 .../core/rtk-microphone-selector.mdx          |   41 +-
 .../api-reference/core/rtk-mixed-grid.mdx     |   43 +-
 .../api-reference/core/rtk-more-toggle.mdx    |   32 +-
 .../core/rtk-mute-all-confirmation.mdx        |   21 +-
 .../api-reference/core/rtk-name-tag.mdx       |   31 +-
 .../core/rtk-network-indicator.mdx            |   27 +-
 .../api-reference/core/rtk-notification.mdx   |   28 +-
 .../api-reference/core/rtk-notifications.mdx  |   30 +-
 .../api-reference/core/rtk-overlay-modal.mdx  |   21 +-
 .../api-reference/core/rtk-paginated-list.mdx |   36 +-
 .../core/rtk-participant-count.mdx            |   22 +-
 .../core/rtk-participant-setup.mdx            |   33 +-
 .../core/rtk-participant-tile.mdx             |   37 +-
 .../api-reference/core/rtk-participant.mdx    |   33 +-
 .../core/rtk-participants-audio.mdx           |   21 +-
 .../core/rtk-participants-stage-list.mdx      |   36 +-
 .../core/rtk-participants-stage-queue.mdx     |   26 +-
 .../core/rtk-participants-viewer-list.mdx     |   32 +-
 .../core/rtk-participants-waiting-list.mdx    |   26 +-
 .../api-reference/core/rtk-participants.mdx   |   30 +-
 .../core/rtk-permissions-message.mdx          |   23 +-
 .../core/rtk-pinned-message-selector.mdx      |   19 +-
 .../api-reference/core/rtk-plugin-main.mdx    |   21 +-
 .../ui-kit/api-reference/core/rtk-plugins.mdx |   26 +-
 .../api-reference/core/rtk-poll-form.mdx      |   17 +-
 .../ui-kit/api-reference/core/rtk-poll.mdx    |   25 +-
 .../ui-kit/api-reference/core/rtk-polls.mdx   |   26 +-
 .../core/rtk-recording-indicator.mdx          |   24 +-
 .../core/rtk-recording-toggle.mdx             |   34 +-
 .../core/rtk-screenshare-view.mdx             |   35 +-
 .../api-reference/core/rtk-settings-audio.mdx |   41 +-
 .../api-reference/core/rtk-settings-video.mdx |   41 +-
 .../api-reference/core/rtk-settings.mdx       |   26 +-
 .../api-reference/core/rtk-setup-screen.mdx   |   28 +-
 .../api-reference/core/rtk-sidebar-ui.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-sidebar.mdx |   35 +-
 .../api-reference/core/rtk-simple-grid.mdx    |   34 +-
 .../core/rtk-speaker-selector.mdx             |   43 +-
 .../ui-kit/api-reference/core/rtk-spinner.mdx |   17 +-
 .../api-reference/core/rtk-spotlight-grid.mdx |   46 +-
 .../core/rtk-spotlight-indicator.mdx          |   22 +-
 .../ui-kit/api-reference/core/rtk-stage.mdx   |   19 +-
 .../ui-kit/api-reference/core/rtk-switch.mdx  |   27 +-
 .../ui-kit/api-reference/core/rtk-tab-bar.mdx |   31 +-
 .../core/rtk-text-composer-view.mdx           |   33 +-
 .../core/rtk-text-message-view.mdx            |   18 +-
 .../api-reference/core/rtk-text-message.mdx   |   27 +-
 .../ui-kit/api-reference/core/rtk-tooltip.mdx |   31 +-
 .../api-reference/core/rtk-transcript.mdx     |   22 +-
 .../api-reference/core/rtk-transcripts.mdx    |   25 +-
 .../api-reference/core/rtk-ui-provider.mdx    |   31 +-
 .../api-reference/core/rtk-viewer-count.mdx   |   22 +-
 .../core/rtk-virtualized-participant-list.mdx |   25 +-
 .../api-reference/core/rtk-waiting-screen.mdx |   21 +-
 .../react-native/RtkMenuItem.mdx              |   10 +-
 .../ui-kit/api-reference/react/RtkAi.mdx      |   34 +-
 .../api-reference/react/RtkAiToggle.mdx       |   32 +-
 .../react/RtkAiTranscriptions.mdx             |   25 +-
 .../api-reference/react/RtkAudioGrid.mdx      |   36 +-
 .../api-reference/react/RtkAudioTile.mdx      |   40 +-
 .../react/RtkAudioVisualizer.mdx              |   42 +-
 .../ui-kit/api-reference/react/RtkAvatar.mdx  |   30 +-
 .../react/RtkBreakoutRoomManager.mdx          |   46 +-
 .../react/RtkBreakoutRoomParticipants.mdx     |   38 +-
 .../react/RtkBreakoutRoomsManager.mdx         |   26 +-
 .../react/RtkBreakoutRoomsToggle.mdx          |   40 +-
 .../react/RtkBroadcastMessageModal.mdx        |   26 +-
 .../ui-kit/api-reference/react/RtkButton.mdx  |   32 +-
 .../api-reference/react/RtkCameraSelector.mdx |   53 +-
 .../api-reference/react/RtkCameraToggle.mdx   |   30 +-
 .../api-reference/react/RtkCaptionToggle.mdx  |   34 +-
 .../ui-kit/api-reference/react/RtkChat.mdx    |   31 +-
 .../api-reference/react/RtkChatComposerUi.mdx |   38 +-
 .../react/RtkChatComposerView.mdx             |   48 +-
 .../api-reference/react/RtkChatHeader.mdx     |    8 +-
 .../api-reference/react/RtkChatMessage.mdx    |   54 +-
 .../api-reference/react/RtkChatMessagesUi.mdx |   40 +-
 .../react/RtkChatMessagesUiPaginated.mdx      |   36 +-
 .../react/RtkChatSearchResults.mdx            |   36 +-
 .../api-reference/react/RtkChatSelector.mdx   |   33 +-
 .../api-reference/react/RtkChatSelectorUi.mdx |   38 +-
 .../api-reference/react/RtkChatToggle.mdx     |   46 +-
 .../ui-kit/api-reference/react/RtkClock.mdx   |   25 +-
 .../react/RtkConfirmationModal.mdx            |   26 +-
 .../api-reference/react/RtkControlbar.mdx     |   36 +-
 .../react/RtkControlbarButton.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkCounter.mdx |   30 +-
 .../api-reference/react/RtkDebugger.mdx       |   29 +-
 .../api-reference/react/RtkDebuggerAudio.mdx  |   29 +-
 .../react/RtkDebuggerScreenshare.mdx          |   29 +-
 .../api-reference/react/RtkDebuggerSystem.mdx |   29 +-
 .../api-reference/react/RtkDebuggerToggle.mdx |   32 +-
 .../api-reference/react/RtkDebuggerVideo.mdx  |   29 +-
 .../ui-kit/api-reference/react/RtkDialog.mdx  |   44 +-
 .../api-reference/react/RtkDialogManager.mdx  |   44 +-
 .../react/RtkDraftAttachmentView.mdx          |   24 +-
 .../api-reference/react/RtkEmojiPicker.mdx    |   24 +-
 .../react/RtkEmojiPickerButton.mdx            |   24 +-
 .../api-reference/react/RtkEndedScreen.mdx    |   31 +-
 .../api-reference/react/RtkFileDropzone.mdx   |   24 +-
 .../api-reference/react/RtkFileMessage.mdx    |   34 +-
 .../react/RtkFileMessageView.mdx              |   28 +-
 .../react/RtkFilePickerButton.mdx             |   36 +-
 .../react/RtkFullscreenToggle.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkGrid.mdx    |   42 +-
 .../api-reference/react/RtkGridPagination.mdx |   40 +-
 .../ui-kit/api-reference/react/RtkHeader.mdx  |   36 +-
 .../ui-kit/api-reference/react/RtkIcon.mdx    |   26 +-
 .../api-reference/react/RtkIdleScreen.mdx     |   28 +-
 .../api-reference/react/RtkImageMessage.mdx   |   36 +-
 .../react/RtkImageMessageView.mdx             |   24 +-
 .../api-reference/react/RtkImageViewer.mdx    |   27 +-
 .../react/RtkInformationTooltip.mdx           |   20 +-
 .../api-reference/react/RtkJoinStage.mdx      |   36 +-
 .../api-reference/react/RtkLeaveButton.mdx    |   27 +-
 .../api-reference/react/RtkLeaveMeeting.mdx   |   28 +-
 .../react/RtkLivestreamIndicator.mdx          |   27 +-
 .../react/RtkLivestreamPlayer.mdx             |   27 +-
 .../react/RtkLivestreamToggle.mdx             |   30 +-
 .../ui-kit/api-reference/react/RtkLogo.mdx    |   27 +-
 .../api-reference/react/RtkMarkdownView.mdx   |   23 +-
 .../ui-kit/api-reference/react/RtkMeeting.mdx |   56 +-
 .../api-reference/react/RtkMeetingTitle.mdx   |   24 +-
 .../ui-kit/api-reference/react/RtkMenu.mdx    |   30 +-
 .../api-reference/react/RtkMenuItem.mdx       |   27 +-
 .../api-reference/react/RtkMenuList.mdx       |   24 +-
 .../api-reference/react/RtkMessageView.mdx    |   50 +-
 .../api-reference/react/RtkMicToggle.mdx      |   30 +-
 .../react/RtkMicrophoneSelector.mdx           |   53 +-
 .../api-reference/react/RtkMixedGrid.mdx      |   48 +-
 .../api-reference/react/RtkMoreToggle.mdx     |   37 +-
 .../api-reference/react/RtkMuteAllButton.mdx  |   30 +-
 .../react/RtkMuteAllConfirmation.mdx          |   26 +-
 .../ui-kit/api-reference/react/RtkNameTag.mdx |   40 +-
 .../react/RtkNetworkIndicator.mdx             |   36 +-
 .../api-reference/react/RtkNotification.mdx   |   36 +-
 .../api-reference/react/RtkNotifications.mdx  |   35 +-
 .../api-reference/react/RtkOverlayModal.mdx   |   26 +-
 .../api-reference/react/RtkPaginatedList.mdx  |   46 +-
 .../api-reference/react/RtkParticipant.mdx    |   44 +-
 .../react/RtkParticipantCount.mdx             |   27 +-
 .../api-reference/react/RtkParticipants.mdx   |   42 +-
 .../react/RtkParticipantsAudio.mdx            |   32 +-
 .../react/RtkParticipantsStageList.mdx        |   46 +-
 .../react/RtkParticipantsStageQueue.mdx       |   38 +-
 .../react/RtkParticipantsToggle.mdx           |   44 +-
 .../react/RtkParticipantsViewerList.mdx       |   42 +-
 .../react/RtkParticipantsWaitingList.mdx      |   38 +-
 .../react/RtkPermissionsMessage.mdx           |   28 +-
 .../react/RtkPinnedMessageSelector.mdx        |   24 +-
 .../api-reference/react/RtkPipToggle.mdx      |   34 +-
 .../api-reference/react/RtkPluginMain.mdx     |   27 +-
 .../ui-kit/api-reference/react/RtkPlugins.mdx |   31 +-
 .../api-reference/react/RtkPluginsToggle.mdx  |   44 +-
 .../ui-kit/api-reference/react/RtkPoll.mdx    |   34 +-
 .../api-reference/react/RtkPollForm.mdx       |   23 +-
 .../ui-kit/api-reference/react/RtkPolls.mdx   |   31 +-
 .../api-reference/react/RtkPollsToggle.mdx    |   46 +-
 .../react/RtkRecordingIndicator.mdx           |   29 +-
 .../react/RtkRecordingToggle.mdx              |   38 +-
 .../react/RtkScreenShareToggle.mdx            |   32 +-
 .../api-reference/react/RtkSettings.mdx       |   31 +-
 .../api-reference/react/RtkSettingsAudio.mdx  |   46 +-
 .../api-reference/react/RtkSettingsToggle.mdx |   40 +-
 .../api-reference/react/RtkSettingsVideo.mdx  |   46 +-
 .../api-reference/react/RtkSetupScreen.mdx    |   33 +-
 .../ui-kit/api-reference/react/RtkSidebar.mdx |   46 +-
 .../api-reference/react/RtkSidebarUi.mdx      |   42 +-
 .../api-reference/react/RtkSimpleGrid.mdx     |   38 +-
 .../react/RtkSpeakerSelector.mdx              |   55 +-
 .../ui-kit/api-reference/react/RtkSpinner.mdx |   22 +-
 .../api-reference/react/RtkSpotlightGrid.mdx  |   51 +-
 .../react/RtkSpotlightIndicator.mdx           |   27 +-
 .../ui-kit/api-reference/react/RtkStage.mdx   |   25 +-
 .../api-reference/react/RtkStageToggle.mdx    |   32 +-
 .../ui-kit/api-reference/react/RtkSwitch.mdx  |   30 +-
 .../ui-kit/api-reference/react/RtkTabBar.mdx  |   38 +-
 .../api-reference/react/RtkTextMessage.mdx    |   34 +-
 .../react/RtkTextMessageView.mdx              |   23 +-
 .../ui-kit/api-reference/react/RtkTooltip.mdx |   36 +-
 .../api-reference/react/RtkTranscript.mdx     |   27 +-
 .../api-reference/react/RtkTranscripts.mdx    |   30 +-
 .../api-reference/react/RtkUiProvider.mdx     |   40 +-
 .../api-reference/react/RtkViewerCount.mdx    |   27 +-
 .../react/RtkVirtualizedParticipantList.mdx   |   36 +-
 .../api-reference/react/RtkWaitingScreen.mdx  |   26 +-
 .../ui-kit/api-reference/react/index.mdx      |    2 +-
 .../docs/realtime/sfu/calls-vs-sfus.mdx       |    7 +-
 src/content/docs/realtime/sfu/changelog.mdx   |    2 +-
 .../docs/realtime/sfu/datachannels.mdx        |    2 +-
 src/content/docs/realtime/sfu/get-started.mdx |    6 +-
 src/content/docs/realtime/sfu/limits.mdx      |   33 +-
 .../sfu/media-transport-adapters/index.mdx    |    1 -
 .../websocket-adapter.mdx                     |   25 +-
 .../docs/realtime/sfu/sessions-tracks.mdx     |   20 +-
 .../docs/realtime/turn/custom-domains.mdx     |   10 +-
 .../realtime/turn/generate-credentials.mdx    |   35 +-
 .../docs/realtime/turn/replacing-existing.mdx |   20 +-
 src/content/docs/realtime/turn/rfc-matrix.mdx |   30 +-
 .../architectures/sase.mdx                    |   18 +-
 .../architectures/security.mdx                |    2 +-
 .../designing-ztna-access-policies.mdx        |   18 +-
 ...nefits-to-saas-providers-end-customers.mdx |   16 +-
 .../diagrams/ai/index.mdx                     |    2 +-
 .../diagrams/content-delivery/index.mdx       |    2 +-
 ...uring-connected-transportation-systems.mdx |   17 +-
 .../diagrams/network/index.mdx                |    2 +-
 .../diagrams/sase/index.mdx                   |    2 +-
 .../diagrams/security/index.mdx               |    2 +-
 .../serverless/fullstack-application.mdx      |   27 +-
 .../diagrams/serverless/index.mdx             |    2 +-
 .../serverless/programmable-platforms.mdx     |    1 +
 .../diagrams/storage/index.mdx                |    2 +-
 .../implementation-guides/index.mdx           |    2 +-
 .../zero-trust/index.mdx                      |    2 +-
 .../domain-contact-updates.mdx                |   26 +-
 .../account-options/domain-management.mdx     |   18 +-
 .../account-options/icloud-domains.mdx        |   24 +-
 .../docs/registrar/account-options/index.mdx  |    2 +-
 .../inter-account-transfer.mdx                |   31 +-
 .../account-options/renew-domains.mdx         |   22 +-
 .../transfer-out-from-cloudflare.mdx          |   12 +-
 .../account-options/whois-redaction.mdx       |    4 +-
 .../registrar/custom-domain-protection.mdx    |    6 +-
 .../docs/registrar/get-started/index.mdx      |    2 +-
 .../registrar/get-started/register-domain.mdx |   15 +-
 .../top-level-domains/uk-domains.mdx          |   12 +-
 src/content/docs/registrar/whoisrequests.mdx  |    4 +-
 .../docs/resource-tagging/get-started.mdx     |   14 +-
 .../docs/resource-tagging/how-to/index.mdx    |    2 +-
 .../resource-tagging/how-to/manage-tags.mdx   |    6 +-
 .../reference/error-codes.mdx                 |   26 +-
 .../docs/resource-tagging/reference/index.mdx |    2 +-
 .../resource-tagging/reference/limits.mdx     |   37 +-
 .../reference/resource-types.mdx              |   80 +-
 .../docs/rules/normalization/settings.mdx     |    4 +-
 .../docs/rules/snippets/when-to-use.mdx       |    2 +-
 .../managed-transforms/reference.mdx          |    1 +
 .../docs/ruleset-engine/about/index.mdx       |    9 +-
 ...ink-override-ddos-l34-rule-sensitivity.mdx |    1 +
 .../ruleset-engine/rulesets-api/endpoints.mdx |  405 +++---
 src/content/docs/sandbox/bridge/http-api.mdx  |  148 +--
 .../docs/sandbox/concepts/containers.mdx      |   23 +-
 .../docs/sandbox/concepts/preview-urls.mdx    |    6 +-
 .../docs/sandbox/concepts/sandboxes.mdx       |    4 +-
 .../docs/sandbox/concepts/security.mdx        |   65 +-
 .../docs/sandbox/concepts/sessions.mdx        |   77 +-
 .../configuration/environment-variables.mdx   |   32 +-
 .../docs/sandbox/configuration/transport.mdx  |    5 +-
 .../sandbox/guides/production-deployment.mdx  |    9 +-
 src/content/docs/sandbox/platform/pricing.mdx |    2 -
 .../sandbox/tutorials/ai-code-executor.mdx    |   76 +-
 .../tutorials/analyze-data-with-ai.mdx        |   29 +-
 .../tutorials/automated-testing-pipeline.mdx  |  116 +-
 .../tutorials/claude-managed-agents.mdx       |   29 +-
 .../sandbox/tutorials/code-review-bot.mdx     |    4 +-
 src/content/docs/secrets-store/audit-logs.mdx |    2 +-
 src/content/docs/secrets-store/index.mdx      |    3 +-
 .../secrets-store/integrations/ai-gateway.mdx |    2 +-
 .../docs/secrets-store/integrations/index.mdx |    2 +-
 .../secrets-store/manage-secrets/how-to.mdx   |    2 +-
 .../secrets-store/manage-secrets/index.mdx    |    2 +-
 .../docs/security-center/brand-protection.mdx |    2 +-
 .../docs/security-center/changelog.mdx        |   10 +-
 .../cloudforce-one/cloudforce-one.mdx         |    1 +
 .../cloudforce-one/open-port-scanning.mdx     |  170 ++-
 .../investigate/change-categorization.mdx     |    1 +
 .../security-center/investigate/index.mdx     |    1 +
 .../investigate/investigate-threats.mdx       |    5 +-
 .../investigate/scan-limits.mdx               |    4 +
 src/content/docs/security/overview.mdx        |   43 +-
 .../docs/smart-shield/concepts/index.mdx      |    2 +-
 .../smart-shield/concepts/network-diagram.mdx |    2 +-
 .../docs/smart-shield/configuration/argo.mdx  |    2 +-
 .../configuration/cache-reserve/analytics.mdx |    6 +-
 .../configuration/cache-reserve/index.mdx     |    2 +-
 .../cache-reserve/operations.mdx              |    5 +-
 .../how-it-works/connection-forwarding.mdx    |    6 +-
 .../how-it-works/index.mdx                    |    2 +-
 .../dedicated-egress-ips/index.mdx            |    8 +-
 .../dedicated-egress-ips/ips-utilization.mdx  |  202 +--
 .../dedicated-egress-ips/other-products.mdx   |    2 +-
 .../configuration/health-checks/analytics.mdx |    5 +-
 .../configuration/health-checks/index.mdx     |    2 +-
 .../configuration/health-checks/setup.mdx     |    4 +-
 .../health-checks/zone-lockdown.mdx           |    2 +-
 .../docs/smart-shield/configuration/index.mdx |    2 +-
 .../configuration/regional-tiered-cache.mdx   |    2 +-
 .../configuration/smart-tiered-cache.mdx      |    2 +-
 src/content/docs/spectrum/about/byoip.mdx     |   75 +-
 .../docs/spectrum/about/ddos-for-spectrum.mdx |    1 +
 src/content/docs/spectrum/about/ftp.mdx       |   16 +-
 src/content/docs/spectrum/about/index.mdx     |    3 +-
 src/content/docs/spectrum/about/static-ip.mdx |   46 +-
 src/content/docs/spectrum/glossary.mdx        |    3 +-
 .../spectrum/how-to/enable-proxy-protocol.mdx |    3 +
 src/content/docs/spectrum/how-to/index.mdx    |    3 +-
 .../docs/spectrum/protocols-per-plan.mdx      |    3 +-
 .../docs/spectrum/reference/analytics.mdx     |   46 +-
 src/content/docs/spectrum/reference/index.mdx |    3 +-
 .../spectrum/reference/layer-7-analytics.mdx  |    4 +-
 src/content/docs/spectrum/reference/logs.mdx  |    3 +
 .../spectrum/reference/settings-by-plan.mdx   |   14 +-
 src/content/docs/speed/aim.mdx                |   33 +-
 src/content/docs/speed/glossary.mdx           |    3 +-
 .../docs/speed/observatory/dashboard.mdx      |   11 +-
 .../docs/speed/observatory/rum-beacon.mdx     |   46 +-
 .../docs/speed/observatory/run-speed-test.mdx |   21 +-
 .../docs/speed/observatory/test-results.mdx   |   23 +-
 .../docs/speed/optimization/content/apo.mdx   |    1 +
 .../optimization/content/compression.mdx      |    6 +-
 .../optimization/content/early-hints.mdx      |    1 +
 .../content/fonts/troubleshooting.mdx         |    5 +-
 .../docs/speed/optimization/content/index.mdx |    3 +-
 .../rocket-loader/ignore-javascripts.mdx      |   10 +-
 .../content/shared-dictionaries.mdx           |    8 +-
 .../optimization/content/smart-hints.mdx      |    1 +
 .../optimization/content/speed-brain.mdx      |    9 +-
 .../content/troubleshooting/index.mdx         |    3 +-
 .../optimization/images/image-resizing.mdx    |    1 +
 .../docs/speed/optimization/images/index.mdx  |    3 +-
 .../docs/speed/optimization/images/polish.mdx |    1 +
 .../images/troubleshooting/index.mdx          |    3 +-
 .../multiple-optimizations.mdx                |    1 +
 .../images/troubleshooting/polish.mdx         |    1 +
 .../troubleshooting-missing-images.mdx        |    6 +-
 src/content/docs/speed/optimization/index.mdx |    3 +-
 .../docs/speed/optimization/measurement.mdx   |    1 +
 .../speed/optimization/protocol/http2.mdx     |    4 +-
 .../speed/optimization/protocol/index.mdx     |    3 +-
 ...hanced-http2-prioritization-ios-safari.mdx |    3 +
 .../protocol/troubleshooting/index.mdx        |    3 +-
 .../speed/optimization/recommendations.mdx    |    1 +
 src/content/docs/speed/smart-shield.mdx       |    3 +-
 src/content/docs/speed/troubleshooting.mdx    |   11 +-
 src/content/docs/ssl/changelog.mdx            |    4 +-
 .../forward-a-client-certificate.mdx          |    2 +-
 .../revoke-client-certificate.mdx             |    3 +
 src/content/docs/ssl/concepts.mdx             |    6 +-
 .../customize-cipher-suites/index.mdx         |    8 +-
 .../cipher-suites/supported-cipher-suites.mdx |   50 +-
 .../additional-options/index.mdx              |    3 +-
 .../additional-options/minimum-tls.mdx        |   22 +-
 .../additional-options/tls-13.mdx             |    9 +-
 .../api-commands.mdx                          |   14 +-
 .../manage-certificates.mdx                   |    8 +-
 .../edge-certificates/backup-certificates.mdx |    3 +-
 .../ssl/edge-certificates/caa-records.mdx     |    1 +
 .../bundling-methodologies.mdx                |    3 +-
 .../custom-certificates/renewing.mdx          |    3 +-
 .../docs/ssl/edge-certificates/ech.mdx        |    4 +-
 .../geokey-manager/supported-options.mdx      |    4 +-
 .../docs/ssl/edge-certificates/index.mdx      |    2 +-
 .../edge-certificates/staging-environment.mdx |   23 +-
 .../universal-ssl/alerts.mdx                  |    8 +-
 .../universal-ssl/disable-universal-ssl.mdx   |    2 +
 .../universal-ssl/troubleshooting.mdx         |    8 +-
 .../ssl/keyless-ssl/configuration/index.mdx   |    3 +-
 src/content/docs/ssl/keyless-ssl/glossary.mdx |    1 +
 .../azure-managed-hsm.mdx                     |    1 +
 .../fortanix-dsm.mdx                          |    2 +-
 .../hardware-security-modules/index.mdx       |    7 +-
 .../reference/high-availability.mdx           |    1 +
 .../docs/ssl/keyless-ssl/reference/index.mdx  |    3 +-
 .../reference/keyless-delegation.mdx          |    1 +
 .../ssl/keyless-ssl/reference/metrics.mdx     |  184 +--
 .../reference/scaling-and-benchmarking.mdx    |    5 +-
 .../keyless-ssl/upgrading-your-key-server.mdx |    3 +
 .../set-up/global.mdx                         |    5 +-
 .../set-up/index.mdx                          |    5 +-
 .../origin-configuration/cipher-suites.mdx    |   28 +-
 .../docs/ssl/origin-configuration/index.mdx   |    3 +-
 .../origin-ca/troubleshooting.mdx             |    2 +-
 .../origin-configuration/ssl-modes/full.mdx   |    6 +-
 .../origin-configuration/ssl-modes/index.mdx  |    2 +-
 .../ssl-modes/ssl-only-origin-pull.mdx        |    7 +-
 .../docs/ssl/reference/all-features.mdx       |    5 +-
 .../ssl/reference/browser-compatibility.mdx   |    9 +-
 .../certificate-and-hostname-priority.mdx     |   17 +-
 .../ssl/reference/certificate-authorities.mdx |    2 +-
 .../ssl/reference/certificate-pinning.mdx     |    1 +
 .../cloudflare-and-cve-2019-1559.mdx          |    7 +-
 .../compliance-and-vulnerabilities.mdx        |   42 +-
 src/content/docs/ssl/reference/index.mdx      |    3 +-
 .../migration-guides/entrust-distrust.mdx     |   15 +-
 .../ssl/reference/migration-guides/index.mdx  |    3 +-
 src/content/docs/ssl/reference/protocols.mdx  |   18 +-
 src/content/docs/ssl/saas.mdx                 |    1 +
 .../troubleshooting/general-ssl-errors.mdx    |    2 +-
 .../docs/ssl/troubleshooting/index.mdx        |   10 +-
 .../troubleshooting/mixed-content-errors.mdx  |   19 +-
 .../version-cipher-mismatch.mdx               |    6 +-
 .../stream/edit-videos/adding-captions.mdx    |   91 +-
 .../edit-videos/player-enhancements.mdx       |   16 +-
 src/content/docs/stream/examples/dash-js.mdx  |    1 +
 src/content/docs/stream/examples/hls-js.mdx   |    5 +-
 src/content/docs/stream/examples/index.mdx    |    1 +
 .../examples/obs-from-scratch/index.mdx       |    1 +
 .../docs/stream/examples/rtmps_playback.mdx   |    3 +-
 .../docs/stream/examples/srt_playback.mdx     |    3 +-
 .../docs/stream/examples/stream-player.mdx    |   13 +-
 src/content/docs/stream/examples/video-js.mdx |    3 +-
 src/content/docs/stream/examples/vidstack.mdx |   15 +-
 .../fetching-bulk-analytics.mdx               |    1 -
 .../docs/stream/getting-analytics/index.mdx   |   11 +-
 .../getting-analytics/live-viewer-count.mdx   |    1 +
 .../stream/manage-video-library/index.mdx     |    1 +
 .../stream/manage-video-library/searching.mdx |    1 +
 src/content/docs/stream/stream-api.mdx        |    1 +
 .../stream/stream-live/custom-domains.mdx     |    3 +-
 .../download-stream-live-videos.mdx           |    4 +-
 .../docs/stream/stream-live/dvr-for-live.mdx  |   16 +-
 src/content/docs/stream/stream-live/index.mdx |    7 +-
 .../stream-live/live-instant-clipping.mdx     |   91 +-
 .../docs/stream/stream-live/simulcasting.mdx  |   40 +-
 .../stream/stream-live/start-stream-live.mdx  |    1 -
 .../stream/stream-live/troubleshooting.mdx    |   73 +-
 .../docs/stream/stream-live/webhooks.mdx      |   64 +-
 .../docs/stream/transform-videos/bindings.mdx |   36 +-
 .../docs/stream/transform-videos/index.mdx    |    4 +-
 .../docs/stream/uploading-videos/index.mdx    |   14 +-
 .../stream/uploading-videos/player-api.mdx    |  227 ++--
 .../uploading-videos/resumable-uploads.mdx    |    6 +
 .../uploading-videos/upload-via-link.mdx      |   80 +-
 .../viewing-videos/displaying-thumbnails.mdx  |   56 +-
 .../using-the-player-api.mdx                  |  260 ++--
 .../api-content-types/deprecated-apis.mdx     |    4 +-
 .../api-content-types/endpoints.mdx           |   18 +-
 .../api-content-types/index.mdx               |    2 +-
 .../api-content-types/parameters.mdx          |    2 +-
 .../guidelines-for-curl-commands.mdx          |   50 +-
 .../style-guide/components/anchor-heading.mdx |   11 +-
 .../components/available-notifications.mdx    |   15 +-
 .../style-guide/components/description.mdx    |    8 +-
 .../docs/style-guide/components/example.mdx   |   18 +-
 .../style-guide/components/feature-table.mdx  |    4 +-
 .../docs/style-guide/components/feature.mdx   |    8 +-
 .../components/glossary-definition.mdx        |   12 +-
 .../components/glossary-tooltip.mdx           |   12 +-
 .../docs/style-guide/components/glossary.mdx  |   12 +-
 .../style-guide/components/inline-badge.mdx   |   35 +-
 .../style-guide/components/link-cards.mdx     |   24 +-
 .../style-guide/components/list-tutorials.mdx |    2 +-
 .../components/package-managers.mdx           |    4 +-
 .../components/pages-build-preset.mdx         |    4 +-
 .../docs/style-guide/components/plan.mdx      |    5 +-
 .../components/product-availability-text.mdx  |    8 +-
 .../components/product-features.mdx           |    5 +-
 .../components/related-product.mdx            |    7 +-
 .../docs/style-guide/components/rule-id.mdx   |    4 +-
 .../docs/style-guide/components/steps.mdx     |    2 +-
 .../components/subtract-ip-calculator.mdx     |    6 +-
 .../components/type-highlighting.mdx          |    2 +-
 .../docs/style-guide/components/usage.mdx     |    2 +-
 .../components/wrangler-namespace.mdx         |    2 +-
 .../docs/style-guide/components/youtube.mdx   |    6 +-
 .../docs/style-guide/contributions.mdx        |   78 +-
 .../component-attributes/dynamic-lists.mdx    |    8 +-
 .../component-attributes/examples.mdx         |    8 +-
 .../component-attributes/glossary-entry.mdx   |   10 +
 .../component-attributes/index.mdx            |    2 +-
 .../intended-audience.mdx                     |   14 +-
 .../component-attributes/links.mdx            |   18 +-
 .../mathematical-operations.mdx               |    6 +-
 .../component-attributes/next-steps.mdx       |    6 +-
 .../notes-tips-warnings.mdx                   |    8 +-
 .../information-architecture.mdx              |   14 +-
 .../code-conventions-and-format.mdx           |   62 +-
 .../formatting/dates-and-times.mdx            |    6 +-
 .../formatting/external-references.mdx        |    6 +-
 .../formatting/file-types-and-extensions.mdx  |   12 +-
 .../docs/style-guide/formatting/index.mdx     |    2 +-
 .../style-guide/formatting/keyboard-keys.mdx  |   24 +-
 .../notes-and-other-notation-types.mdx        |    1 -
 .../numbers-and-units-of-measurement.mdx      |   18 +-
 .../product-name-and-pluralization.mdx        |    4 +-
 .../formatting/structure/index.mdx            |    2 +-
 .../formatting/structure/lists.mdx            |   79 +-
 .../formatting/structure/tables.mdx           |   79 +-
 .../docs/style-guide/frontmatter/sidebar.mdx  |    4 +-
 .../docs/style-guide/grammar/index.mdx        |    2 +-
 .../grammar/parts-of-speech/abbreviations.mdx |   46 +-
 .../grammar/parts-of-speech/acronyms.mdx      |    8 +-
 .../parts-of-speech/capitalization.mdx        |  160 +--
 .../parts-of-speech/compound-words.mdx        |   53 +-
 .../grammar/parts-of-speech/contractions.mdx  |    2 +-
 .../grammar/parts-of-speech/index.mdx         |    2 +-
 .../parts-of-speech/nouns-and-pronouns.mdx    |    2 +-
 .../grammar/parts-of-speech/possessives.mdx   |    2 +-
 .../grammar/parts-of-speech/prepositions.mdx  |    2 +-
 .../punctuation-marks-and-symbols/commas.mdx  |    2 +-
 .../punctuation-marks-and-symbols/dashes.mdx  |   16 +-
 .../punctuation-marks-and-symbols/index.mdx   |    2 +-
 .../docs/style-guide/how-we-docs/our-site.mdx |    1 +
 .../docs/style-guide/how-we-docs/reviews.mdx  |   21 +-
 .../support/contacting-cloudflare-support.mdx |   46 +-
 src/content/docs/support/index.mdx            |    2 +-
 ...ress-plugin-automatic-cache-management.mdx |   16 +-
 ...-enable-http2-server-push-in-wordpress.mdx |    6 +-
 ...tent-management-systems-like-wordpress.mdx |   38 +-
 .../content-management-system-cms/index.mdx   |    2 +-
 ...dpress-in-cloudflares-wordpress-plugin.mdx |   26 +-
 .../forum-software/index.mdx                  |    2 +-
 ...-various-forums-vbulletin-xenforo-mybb.mdx |   10 +-
 .../support/third-party-software/index.mdx    |    2 +-
 .../third-party-software/others/index.mdx     |    2 +-
 ...ess-costs-between-azure-and-cloudflare.mdx |    8 +-
 .../cannot-locate-dashboard-account.mdx       |    8 +-
 ...-information-for-troubleshooting-sites.mdx |   26 +-
 .../geographic-traffic-routing.mdx            |    2 +-
 .../general-troubleshooting/index.mdx         |    2 +-
 .../not-receiving-cloudflare-emails.mdx       |   14 +-
 .../service-disruption.mdx                    |    8 +-
 .../third-party-load-balancers.mdx            |   12 +-
 .../troubleshooting-crawl-errors.mdx          |   40 +-
 .../4xx-client-error/error-400.mdx            |    2 +-
 .../4xx-client-error/error-401.mdx            |    2 +-
 .../4xx-client-error/error-406.mdx            |    2 +-
 .../4xx-client-error/error-407.mdx            |    2 +-
 .../4xx-client-error/error-408.mdx            |    2 +-
 .../4xx-client-error/error-409.mdx            |    2 +-
 .../4xx-client-error/error-410.mdx            |    2 +-
 .../4xx-client-error/error-411.mdx            |    2 +-
 .../4xx-client-error/error-412.mdx            |    2 +-
 .../4xx-client-error/error-413.mdx            |    2 +-
 .../4xx-client-error/error-414.mdx            |    2 +-
 .../4xx-client-error/error-416.mdx            |    2 +-
 .../4xx-client-error/error-417.mdx            |    2 +-
 .../4xx-client-error/error-429.mdx            |    1 +
 .../4xx-client-error/error-451.mdx            |    2 +-
 .../4xx-client-error/index.mdx                |    4 +-
 .../cloudflare-10xxx-errors/error-10028.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10043.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10044.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10045.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10046.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10047.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10048.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10049.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10050.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10051.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10052.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10055.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10056.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10058.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10059.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10060.mdx   |    2 +-
 .../cloudflare-10xxx-errors/index.md          |    2 +-
 .../cloudflare-1xxx-errors/error-1000.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1002.mdx     |    4 +-
 .../cloudflare-1xxx-errors/error-1004.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1009.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1014.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1035.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1040.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1102.mdx     |    1 +
 .../cloudflare-1xxx-errors/index.mdx          |    4 +
 .../cloudflare-5xx-errors/error-501.mdx       |    2 +-
 .../cloudflare-5xx-errors/error-503.mdx       |    9 +-
 .../cloudflare-5xx-errors/error-520.mdx       |    1 +
 .../cloudflare-5xx-errors/error-522.mdx       |    4 +-
 .../cloudflare-5xx-errors/error-524.mdx       |    5 +-
 .../cloudflare-5xx-errors/error-525.mdx       |    2 +-
 .../cloudflare-5xx-errors/index.mdx           |    6 +-
 .../cloudflare-error-headers.mdx              |   11 +-
 .../http-status-codes/index.mdx               |    2 +-
 .../docs/support/troubleshooting/index.mdx    |    2 +-
 .../restoring-visitor-ips/index.mdx           |    2 +-
 .../restoring-original-visitor-ips.mdx        |    5 +-
 src/content/docs/tenant/how-to/index.mdx      |    2 +-
 src/content/docs/tenant/index.mdx             |    8 +-
 src/content/docs/tenant/reference/index.mdx   |    2 +-
 .../advanced-topics/best-practices.mdx        |    2 +
 .../terraform/how-to/create-partial-zone.mdx  |    3 +-
 .../how-to/create-secondary-zone.mdx          |    4 +-
 .../authentication-error-dns-records.mdx      |    2 +-
 src/content/docs/terraform/tutorial/index.mdx |   36 +-
 src/content/docs/time-services/index.mdx      |    2 +-
 .../docs/time-services/roughtime/index.mdx    |    2 +-
 .../docs/time-services/roughtime/recipes.mdx  |   32 +-
 src/content/docs/time-services/tos.mdx        |    2 +-
 .../tunnel/advanced/origin-parameters.mdx     |   16 +-
 .../docs/tunnel/advanced/run-parameters.mdx   |   24 +-
 src/content/docs/tunnel/changelog.mdx         |    5 +-
 .../tunnel/deployment-guides/terraform.mdx    |    1 +
 .../tunnel/downloads/system-requirements.mdx  |    7 +-
 src/content/docs/tunnel/troubleshooting.mdx   |    1 -
 .../hostname-management/any-hostname.mdx      |   69 +-
 .../hostname-management/index.mdx             |    5 +-
 .../hostname-management/pre-clearance.mdx     |   17 +-
 .../additional-configuration/index.mdx        |    3 +-
 .../pre-clearance-support.mdx                 |    3 +-
 .../docs/turnstile/concepts/challenges.mdx    |    1 +
 src/content/docs/turnstile/concepts/index.mdx |    5 +-
 .../turnstile/extensions/google-firebase.mdx  |   35 +-
 .../docs/turnstile/extensions/index.mdx       |    3 +-
 .../turnstile/extensions/pages-plugin.mdx     |    1 +
 .../turnstile/extensions/waiting-room.mdx     |    1 +
 .../get-started/widget-management/api.mdx     |   61 +-
 .../get-started/widget-management/index.mdx   |    4 +-
 .../widget-management/terraform.mdx           |   10 +-
 .../docs/turnstile/migration/hcaptcha.mdx     |    2 +-
 .../docs/turnstile/reference/index.mdx        |    3 +-
 .../reference/supported-browsers.mdx          |    1 +
 .../reference/supported-languages.mdx         |    1 +
 .../reference/turnstile-privacy-addendum.mdx  |    1 +
 .../challenge-solve-issues.mdx                |    1 +
 .../client-side-errors/index.mdx              |  137 +-
 .../docs/turnstile/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/rotate-secret-key.mdx     |    3 +-
 .../turnstile/troubleshooting/testing.mdx     |   67 +-
 .../turnstile/turnstile-analytics/index.mdx   |    5 +-
 .../excluding-turnstile-from-e2e-tests.mdx    |   54 +-
 .../fraud-detection-with-ephemeral-ids.mdx    |    4 +-
 ...ating-turnstile-waf-and-bot-management.mdx |    8 +-
 .../docs/use-cases/e-commerce/performance.mdx |    2 +-
 .../encrypt-all-keep-site-secure.mdx          |   27 +-
 .../protect-sensitive-forms-fraud-abuse.mdx   |   77 +-
 .../stop-account-takeover-attacks.mdx         |   42 +-
 .../solutions/stop-malicious-bots.mdx         |    9 +-
 .../docs/use-cases/web-apps/performance.mdx   |    3 +-
 .../docs/vectorize/best-practices/index.mdx   |    2 +-
 .../vectorize/best-practices/list-vectors.mdx |    3 +-
 src/content/docs/vectorize/demos.mdx          |   11 +-
 .../docs/vectorize/examples/agents.mdx        |    2 +-
 src/content/docs/vectorize/examples/index.mdx |    2 +-
 .../docs/vectorize/get-started/index.mdx      |    2 +-
 src/content/docs/vectorize/platform/index.mdx |    2 +-
 .../docs/vectorize/reference/index.mdx        |    2 +-
 src/content/docs/version-management/about.mdx |    6 +-
 .../how-to/compare-versions.mdx               |    2 +-
 .../how-to/environments.mdx                   |   33 +-
 .../docs/version-management/how-to/index.mdx  |    4 +-
 .../version-management/how-to/versions.mdx    |    4 +-
 .../reference/available-configurations.mdx    |   14 +-
 .../version-management/reference/index.mdx    |    4 +-
 .../reference/read-only-environments.mdx      |    7 +-
 .../waf/custom-rules/create-dashboard.mdx     |    1 +
 .../use-cases/sequence-custom-rules.mdx       |    2 +-
 src/content/docs/waf/glossary.mdx             |    3 +-
 src/content/docs/waf/managed-rules/index.mdx  |    1 +
 src/content/docs/waf/tools/index.mdx          |    1 +
 src/content/docs/waf/tools/privacy-pass.mdx   |    9 +-
 src/content/docs/waf/troubleshooting/faq.mdx  |    1 -
 src/content/docs/waiting-room/about.mdx       |    6 +-
 .../additional-options/create-events.mdx      |   33 +-
 .../waiting-room/additional-options/index.mdx |    3 +-
 .../additional-options/ssl-for-saas.mdx       |    1 +
 .../waiting-room-rules/index.mdx              |    3 +-
 .../docs/waiting-room/api-reference.mdx       |    1 +
 src/content/docs/waiting-room/glossary.mdx    |    3 +-
 .../how-to/control-user-session.mdx           |    8 +-
 .../how-to/edit-delete-waiting-room.mdx       |   41 +-
 .../docs/waiting-room/how-to/index.mdx        |    3 +-
 .../waiting-room/how-to/json-response.mdx     |    2 +
 .../how-to/monitor-waiting-room.mdx           |   45 +-
 .../how-to/place-waiting-room.mdx             |    5 +-
 .../how-to/waiting-room-dashboard.mdx         |    3 +-
 src/content/docs/waiting-room/plans.mdx       |    3 +-
 .../reference/configuration-settings.mdx      |   11 +-
 .../docs/waiting-room/reference/index.mdx     |    3 +-
 .../reference/waiting-room-api.mdx            |   21 +-
 .../reference/waiting-room-cookie.mdx         |   12 +-
 .../docs/waiting-room/troubleshooting.mdx     |   50 +-
 .../docs/warp-client/get-started/linux.mdx    |   21 +-
 .../docs/warp-client/known-issues-and-faq.mdx |    8 +-
 .../docs/warp-client/legal/3rdparty.mdx       | 1139 ++++++++++-------
 src/content/docs/warp-client/legal/index.mdx  |    7 +-
 src/content/docs/warp-client/privacy.mdx      |    1 +
 .../configuration-options/filters.mdx         |    3 +-
 .../configuration-options/index.mdx           |    3 +-
 .../data-metrics/core-web-vitals.mdx          |    5 +-
 .../data-origin-and-collection.mdx            |    2 +-
 .../web-analytics/data-metrics/dimensions.mdx |   21 +-
 .../data-metrics/high-level-metrics.mdx       |    9 +-
 .../docs/web-analytics/data-metrics/index.mdx |    3 +-
 .../data-metrics/page-load-time-summary.mdx   |    1 +
 src/content/docs/web-analytics/faq.mdx        |   14 +-
 .../web-analytics/get-started/rum-beacon.mdx  |    3 +-
 .../get-started/web-analytics-spa.mdx         |   10 +-
 src/content/docs/web-analytics/limits.mdx     |    1 +
 src/content/docs/web3/about.mdx               |    2 +-
 src/content/docs/web3/api-reference.mdx       |    1 +
 .../web3/ethereum-gateway/concepts/index.mdx  |    3 +-
 .../web3/ethereum-gateway/reference/index.mdx |    3 +-
 .../reference/kill-switches.mdx               |    7 +-
 .../reference/rinkeby-deprecation.mdx         |   57 +-
 .../reference/supported-networks.mdx          |    1 +
 src/content/docs/web3/how-to/index.mdx        |    3 +-
 .../docs/web3/how-to/use-ipfs-gateway.mdx     |    1 +
 .../web3/ipfs-gateway/concepts/dnslink.mdx    |    1 +
 .../docs/web3/ipfs-gateway/concepts/index.mdx |    3 +-
 .../reference/automated-deployment.mdx        |    7 +-
 .../web3/ipfs-gateway/reference/index.mdx     |    3 +-
 .../peering-with-content-providers.mdx        |  129 +-
 .../reference/updating-for-ipfs.mdx           |    7 +-
 .../web3/ipfs-gateway/troubleshooting.mdx     |    1 +
 .../web3/reference/gateway-dns-records.mdx    |    5 +-
 .../docs/web3/reference/gateway-status.mdx    |    1 +
 src/content/docs/web3/reference/index.mdx     |    3 +-
 .../docs/web3/reference/migration-guide.mdx   |    3 +-
 src/content/docs/workers-ai/agents.mdx        |   13 +-
 src/content/docs/workers-ai/api-reference.mdx |    1 +
 .../workers-ai/configuration/bindings.mdx     |   26 +-
 .../configuration/hugging-face-chat-ui.mdx    |   34 +-
 .../embedded/examples/fetch.mdx               |   36 +-
 .../function-calling/embedded/examples/kv.mdx |    1 -
 .../embedded/examples/openapi.mdx             |   22 +-
 .../function-calling/embedded/index.mdx       |    4 +-
 .../docs/workers-ai/get-started/dashboard.mdx |    5 +-
 .../docs/workers-ai/get-started/index.mdx     |    4 +-
 .../docs/workers-ai/get-started/rest-api.mdx  |    3 +-
 src/content/docs/workers-ai/guides/agents.mdx |    2 +-
 ...generation-using-deepseek-coder-models.mdx |   18 +-
 ...choose-the-right-text-generation-model.mdx |   72 +-
 .../docs/workers-ai/platform/data-usage.mdx   |    8 +-
 .../docs/workers-ai/platform/pricing.mdx      |   62 +-
 .../docs/workers-vpc/configuration/index.mdx  |    2 +-
 .../configuration/vpc-services/terraform.mdx  |    1 -
 .../docs/workers-vpc/examples/private-api.mdx |    4 +-
 .../examples/private-s3-bucket.mdx            |    4 +-
 .../route-across-private-services.mdx         |   15 +-
 .../workers/ci-cd/builds/automatic-prs.mdx    |    1 -
 .../workers/ci-cd/builds/build-caching.mdx    |   18 +-
 .../docs/workers/ci-cd/builds/build-image.mdx |    5 +-
 .../workers/ci-cd/builds/configuration.mdx    |   12 +-
 .../docs/workers/ci-cd/builds/index.mdx       |   10 +-
 .../ci-cd/builds/limits-and-pricing.mdx       |   24 +-
 .../workers/ci-cd/builds/troubleshoot.mdx     |    1 -
 .../ci-cd/external-cicd/github-actions.mdx    |    2 -
 .../ci-cd/external-cicd/gitlab-cicd.mdx       |    1 -
 .../configuration/integrations/index.mdx      |   22 +-
 .../configuration/routing/custom-domains.mdx  |   36 +-
 .../workers/configuration/routing/routes.mdx  |   14 +-
 .../sites/start-from-existing.mdx             |   36 +-
 .../sites/start-from-scratch.mdx              |   50 +-
 .../configuration/sites/start-from-worker.mdx |   20 +-
 .../versions-and-deployments/index.mdx        |    2 +-
 .../version-overrides.mdx                     |   24 +-
 .../configuration/workers-with-page-rules.mdx |   50 +-
 .../third-party-integrations/supabase.mdx     |    4 +-
 .../third-party-integrations/turso.mdx        |    6 +-
 .../third-party-integrations/upstash.mdx      |    3 +-
 .../third-party-integrations/xata.mdx         |    1 +
 .../development-testing/multi-workers.mdx     |   44 +-
 .../workers/development-testing/testing.mdx   |    2 +-
 .../development-testing/vite-plugin.mdx       |    2 +-
 .../docs/workers/examples/103-early-hints.mdx |    2 +-
 .../docs/workers/examples/ab-testing.mdx      |    1 +
 .../accessing-the-cloudflare-object.mdx       |    1 +
 .../workers/examples/aggregate-requests.mdx   |    1 +
 .../docs/workers/examples/alter-headers.mdx   |    1 +
 .../workers/examples/auth-with-headers.mdx    |    1 +
 .../docs/workers/examples/basic-auth.mdx      |    1 +
 .../docs/workers/examples/block-on-tls.mdx    |    1 +
 .../workers/examples/bulk-origin-proxy.mdx    |    1 +
 .../docs/workers/examples/bulk-redirects.mdx  |    1 +
 .../docs/workers/examples/cache-api.mdx       |    1 +
 .../workers/examples/cache-post-request.mdx   |    1 +
 .../docs/workers/examples/cache-tags.mdx      |    1 +
 .../workers/examples/cache-using-fetch.mdx    |    5 +-
 .../workers/examples/conditional-response.mdx |    1 +
 .../workers/examples/cors-header-proxy.mdx    |    2 +
 .../examples/country-code-redirect.mdx        |    1 +
 .../workers/examples/data-loss-prevention.mdx |    1 +
 .../docs/workers/examples/debugging-logs.mdx  |    1 +
 .../workers/examples/extract-cookie-value.mdx |    1 +
 .../docs/workers/examples/fetch-json.mdx      |    1 +
 .../examples/geolocation-app-weather.mdx      |    1 +
 .../examples/geolocation-custom-styling.mdx   |    1 +
 .../examples/geolocation-hello-world.mdx      |    1 +
 .../workers/examples/hot-link-protection.mdx  |    1 +
 .../examples/modify-request-property.mdx      |    1 +
 .../docs/workers/examples/modify-response.mdx |    1 +
 .../examples/multiple-cron-triggers.mdx       |    1 +
 .../workers/examples/openai-sdk-streaming.mdx |    1 +
 .../docs/workers/examples/post-json.mdx       |    1 +
 .../protect-against-timing-attacks.mdx        |    1 +
 .../docs/workers/examples/read-post.mdx       |    1 +
 .../docs/workers/examples/return-html.mdx     |    1 +
 .../docs/workers/examples/rewrite-links.mdx   |    1 +
 .../workers/examples/signing-requests.mdx     |    1 +
 .../examples/turnstile-html-rewriter.mdx      |    1 +
 .../docs/workers/examples/websockets.mdx      |    4 +-
 .../framework-guides/ai-and-agents/index.mdx  |   13 +-
 .../workers/framework-guides/apis/index.mdx   |    9 +-
 .../docs/workers/framework-guides/index.mdx   |    9 +-
 .../framework-guides/mobile-apps/expo.mdx     |    2 +-
 .../framework-guides/mobile-apps/index.mdx    |    9 +-
 .../framework-guides/web-apps/astro.mdx       |   24 +-
 .../framework-guides/web-apps/index.mdx       |    9 +-
 .../web-apps/more-web-frameworks/analog.mdx   |   18 +-
 .../web-apps/more-web-frameworks/angular.mdx  |    6 +-
 .../more-web-frameworks/docusaurus.mdx        |    2 +
 .../web-apps/more-web-frameworks/hono.mdx     |    2 +
 .../web-apps/more-web-frameworks/index.mdx    |    2 +-
 .../web-apps/more-web-frameworks/nuxt.mdx     |   18 +-
 .../web-apps/more-web-frameworks/solid.mdx    |   18 +-
 .../web-apps/more-web-frameworks/waku.mdx     |   14 +-
 .../framework-guides/web-apps/nextjs.mdx      |   48 +-
 .../framework-guides/web-apps/redwoodsdk.mdx  |    2 +-
 .../framework-guides/web-apps/sveltekit.mdx   |   24 +-
 .../framework-guides/web-apps/vike.mdx        |   32 +-
 .../workers/framework-guides/web-apps/vue.mdx |   24 +-
 .../docs/workers/get-started/dashboard.mdx    |   11 +-
 .../docs/workers/get-started/quickstarts.mdx  |    1 +
 .../workers/languages/javascript/index.mdx    |   13 +-
 .../docs/workers/observability/errors.mdx     |   58 +-
 .../exporting-opentelemetry-data/axiom.mdx    |   22 +-
 .../grafana-cloud.mdx                         |   31 +-
 .../honeycomb.mdx                             |    8 +-
 .../exporting-opentelemetry-data/index.mdx    |   32 +-
 .../exporting-opentelemetry-data/posthog.mdx  |   47 +-
 .../exporting-opentelemetry-data/sentry.mdx   |   29 +-
 .../workers/observability/logs/logpush.mdx    |   91 +-
 .../observability/logs/real-time-logs.mdx     |    1 -
 .../observability/logs/workers-logs.mdx       |    6 +-
 .../observability/metrics-and-analytics.mdx   |    1 -
 .../workers/observability/source-maps.mdx     |   15 +-
 src/content/docs/workers/platform/betas.mdx   |   10 +-
 .../platform/built-with-cloudflare.mdx        |    2 +-
 .../changelog/historical-changelog.mdx        |  448 +++----
 .../docs/workers/platform/changelog/index.mdx |    2 +-
 .../docs/workers/platform/known-issues.mdx    |   10 +-
 src/content/docs/workers/platform/pricing.mdx |    6 +-
 .../workers/reference/how-the-cache-works.mdx |    4 +
 .../workers/reference/how-workers-works.mdx   |   16 +-
 .../docs/workers/reference/protocols.mdx      |   14 +-
 .../docs/workers/reference/security-model.mdx |    6 +-
 .../workers/runtime-apis/bindings/index.mdx   |   55 +-
 .../runtime-apis/bindings/rate-limit.mdx      |   54 +-
 .../bindings/service-bindings/http.mdx        |   22 +-
 .../workers/runtime-apis/bindings/stream.mdx  |    1 +
 .../bindings/version-metadata.mdx             |    2 +-
 .../docs/workers/runtime-apis/cache.mdx       |  105 +-
 .../docs/workers/runtime-apis/console.mdx     |   44 +-
 .../docs/workers/runtime-apis/encoding.mdx    |   44 +-
 .../docs/workers/runtime-apis/eventsource.mdx |   75 +-
 .../workers/runtime-apis/handlers/fetch.mdx   |   27 +-
 .../workers/runtime-apis/handlers/index.mdx   |    4 +-
 .../workers/runtime-apis/handlers/tail.mdx    |  227 ++--
 .../docs/workers/runtime-apis/headers.mdx     |   19 +-
 .../workers/runtime-apis/messagechannel.mdx   |   16 +-
 .../docs/workers/runtime-apis/nodejs/util.mdx |    6 +-
 .../docs/workers/runtime-apis/performance.mdx |    2 +-
 .../runtime-apis/rpc/error-handling.mdx       |    6 +-
 .../runtime-apis/rpc/reserved-methods.mdx     |   14 +-
 .../runtime-apis/streams/readablestream.mdx   |   44 +-
 .../streams/readablestreambyobreader.mdx      |   39 +-
 .../streams/readablestreamdefaultreader.mdx   |   36 +-
 .../runtime-apis/streams/transformstream.mdx  |   77 +-
 .../runtime-apis/streams/writablestream.mdx   |   35 +-
 .../streams/writablestreamdefaultwriter.mdx   |   58 +-
 .../docs/workers/runtime-apis/tcp-sockets.mdx |  183 +--
 .../docs/workers/runtime-apis/web-crypto.mdx  |  425 ++++--
 .../runtime-apis/webassembly/index.mdx        |   16 +-
 .../docs/workers/runtime-apis/websockets.mdx  |  177 ++-
 .../routing/full-stack-application.mdx        |    5 +-
 .../testing/miniflare/storage/cache.md        |    4 +-
 .../testing/vitest-integration/recipes.mdx    |    2 +-
 .../docs/workers/vite-plugin/tutorial.mdx     |    1 -
 src/content/docs/workers/wrangler/api.mdx     |   52 +-
 .../docs/workers/wrangler/commands/r2.mdx     |    1 +
 .../docs/workers/wrangler/configuration.mdx   |   46 +-
 .../docs/workers/wrangler/custom-builds.mdx   |   15 +-
 .../docs/workers/wrangler/deprecations.mdx    |  122 +-
 .../wrangler/migration/update-v2-to-v3.mdx    |    2 +
 .../v1-to-v2/wrangler-legacy/commands.mdx     |    8 +-
 src/content/docs/workflows/build/index.mdx    |    2 +-
 .../docs/workflows/build/test-workflows.mdx   |    2 +-
 .../docs/workflows/examples/agents.mdx        |    2 +-
 .../docs/workflows/examples/backup-d1.mdx     |    1 +
 .../docs/workflows/examples/send-invoices.mdx |    1 +
 .../docs/workflows/examples/twilio.mdx        |    1 +
 .../workflows/examples/wait-for-event.mdx     |   13 +-
 .../docs/workflows/observability/index.mdx    |    4 +-
 .../docs/workflows/python/bindings.mdx        |    2 +-
 .../docs/workflows/reference/changelog.mdx    |    4 +-
 .../docs/workflows/reference/glossary.mdx     |    2 +-
 .../docs/workflows/reference/index.mdx        |    2 +-
 .../docs/workflows/reference/pricing.mdx      |   26 +-
 .../workflows/reference/wrangler-commands.mdx |    4 +-
 src/content/docs/workflows/videos.mdx         |   10 +-
 .../advanced/datalayer-compatibility.mdx      |   11 +-
 .../zaraz/advanced/domains-not-proxied.mdx    |    1 +
 .../zaraz/advanced/google-consent-mode.mdx    |   27 +-
 .../docs/zaraz/advanced/import-export.mdx     |    9 +-
 src/content/docs/zaraz/advanced/index.mdx     |    3 +-
 .../load-custom-managed-component.mdx         |    3 +-
 .../docs/zaraz/advanced/load-selectively.mdx  |    3 +
 .../zaraz/advanced/load-zaraz-manually.mdx    |   15 +-
 .../docs/zaraz/advanced/using-jsonata.mdx     |   37 +-
 .../docs/zaraz/consent-management/api.mdx     |  182 ++-
 .../zaraz/consent-management/custom-css.mdx   |    4 +-
 .../enable-consent-management.mdx             |    9 +-
 .../consent-management/iab-tcf-compliance.mdx |    4 +-
 .../docs/zaraz/consent-management/index.mdx   |   27 +-
 .../custom-actions/additional-fields.mdx      |    7 +-
 .../zaraz/custom-actions/create-action.mdx    |    3 +-
 .../zaraz/custom-actions/create-trigger.mdx   |    3 +-
 .../custom-actions/edit-tools-and-actions.mdx |   15 +-
 .../zaraz/custom-actions/edit-triggers.mdx    |    7 +-
 src/content/docs/zaraz/embeds.mdx             |    9 +-
 src/content/docs/zaraz/get-started.mdx        |    3 +-
 src/content/docs/zaraz/history/index.mdx      |    3 +-
 src/content/docs/zaraz/history/versions.mdx   |   16 +-
 src/content/docs/zaraz/http-events-api.mdx    |   98 +-
 src/content/docs/zaraz/monitoring/index.mdx   |    5 +-
 src/content/docs/zaraz/pricing-info.mdx       |    7 +-
 src/content/docs/zaraz/reference/context.mdx  |    9 +
 src/content/docs/zaraz/reference/index.mdx    |    3 +-
 .../zaraz/reference/properties-reference.mdx  |   84 +-
 src/content/docs/zaraz/reference/settings.mdx |   18 +-
 .../docs/zaraz/reference/supported-tools.mdx  |    1 +
 .../docs/zaraz/variables/create-variables.mdx |    3 +-
 .../docs/zaraz/variables/edit-variables.mdx   |    7 +-
 src/content/docs/zaraz/variables/index.mdx    |    3 +-
 .../docs/zaraz/variables/worker-variables.mdx |  100 +-
 src/content/docs/zaraz/web-api/debug-mode.mdx |    6 +-
 src/content/docs/zaraz/web-api/ecommerce.mdx  |    3 +-
 src/content/docs/zaraz/web-api/index.mdx      |    3 +-
 src/content/docs/zaraz/web-api/set.mdx        |   21 +-
 .../partials/1.1.1.1/captive-portals.mdx      |    2 +-
 src/content/partials/agents/unique-agents.mdx |    3 +-
 .../ai-crawl-control/plan-comparison.mdx      |   11 +-
 .../ai-gateway/analytics-dashboard.mdx        |    1 +
 src/content/partials/ai-gateway/logging.mdx   |    1 -
 .../ai-gateway/universal-gateway-example.mdx  |    1 +
 .../partials/ai-search/rest-api-auth.mdx      |    2 +-
 .../customer_metadata_boundary_error.mdx      |    5 +-
 .../network-analytics-requirements.mdx        |    7 +-
 .../network-analytics-v1-deprecation.mdx      |    1 +
 .../partials/api-shield/label-methodology.mdx |    9 +-
 .../api-shield/mtls-api-shield-support.mdx    |    1 +
 .../partials/api-shield/mtls-create-rule.mdx  |    5 +-
 .../partials/api-shield/rate-limit-user.mdx   |    1 +
 .../required-session-identifiers.mdx          |    1 +
 .../sequence-mitigation-availability.mdx      |    3 +-
 .../api-shield/session-identifiers.mdx        |    5 +-
 .../partials/billing/two-payment-methods.mdx  |    1 +
 .../bots/about-plan-considerations.mdx        |    5 +-
 .../partials/bots/analytics-features.mdx      |    1 +
 .../partials/bots/bfm-change-notice.mdx       |    1 +
 .../partials/bots/bm-analytics-features.mdx   |    9 +-
 .../bots/bot-settings-vs-custom-rules.mdx     |   18 +-
 src/content/partials/bots/bots-ad.mdx         |    1 +
 src/content/partials/bots/bots-cookie.mdx     |    3 +-
 src/content/partials/bots/bots-heuristics.mdx |    3 +-
 src/content/partials/bots/bots-jsd.mdx        |    1 +
 src/content/partials/bots/bots-ml.mdx         |    5 +-
 .../partials/bots/buttons-plan-pages.mdx      |   16 +-
 .../content-security-policy-limitation.mdx    |    5 +-
 .../partials/bots/disable-cf-bm-cookie.mdx    |    1 +
 .../partials/bots/endpoint-label-warning.mdx  |    7 +-
 src/content/partials/bots/execution-order.mdx |    2 +-
 src/content/partials/bots/flexible-sbfm.mdx   |    3 +-
 src/content/partials/bots/ja3-ja4-null.mdx    |    3 +-
 .../partials/bots/jsd-availability.mdx        |    3 +-
 .../partials/bots/plan-get-started.mdx        |    1 +
 src/content/partials/bots/plan-intro.mdx      |    1 +
 src/content/partials/bots/sequence-rules.mdx  |    7 +-
 .../bots/signals-intelligence-and-ja4.mdx     |    7 +-
 src/content/partials/bots/verified-bots.mdx   |    1 +
 .../improve-blurry-screenshot-resolution.mdx  |   15 +-
 .../partials/byoip/cloudflare-asn-callout.mdx |    2 +-
 src/content/partials/byoip/loa.mdx            |    2 +-
 .../byoip/validate-prefix-endpoint.mdx        |    1 +
 .../cache/cache-reserve-billing-note.mdx      |    3 +
 .../cache/cache-reserve-eligibility.mdx       |    2 +-
 .../partials/cache/cache-reserve-intro.mdx    |    2 +-
 .../partials/cache/cache-reserve-limits.mdx   |    2 +-
 .../cache/cache-reserve-operations.mdx        |    2 +-
 src/content/partials/cache/edge-ttl.mdx       |    2 +-
 .../partials/cache/regional-tiered-cache.mdx  |    2 +-
 .../partials/cache/smart-tiered-cache.mdx     |    2 +-
 .../cf-clearance-cookie.mdx                   |    3 +-
 .../create-challenge-page.mdx                 |    5 +-
 .../apex-proxying-process.mdx                 |    3 +
 .../cname-target-process.mdx                  |    1 +
 .../create-custom-hostname-api.mdx            |    6 +-
 .../create-custom-hostname-limitations.mdx    |    7 +-
 .../create-custom-hostname.mdx                |   13 +-
 .../custom-origin-server-definition.mdx       |    5 +-
 .../delete-custom-hostname-dash.mdx           |    1 +
 .../get-started-initial-setup-preamble.mdx    |    1 +
 .../get-started-per-hostname.mdx              |    5 +-
 .../get-started-prereqs.mdx                   |    7 +-
 .../get-started-service-continuation.mdx      |    1 +
 .../http-dcv-situation.mdx                    |    5 +-
 .../issue-certs-preamble.mdx                  |    1 +
 .../provider-guide-compatibility.mdx          |    7 +-
 .../provider-guide-zone-hold.mdx              |    2 +-
 .../regional-services.mdx                     |    1 +
 .../saas-customer-churn.mdx                   |    1 +
 .../same-name-as-zone.mdx                     |    3 +-
 .../ssl-for-saas-create-hostname.mdx          |    1 +
 .../ssl-for-saas-definition.mdx               |    1 +
 .../ssl-for-saas-plan-limitation.mdx          |    3 +
 .../ssl-for-saas-validate-patch.mdx           |    1 +
 .../txt-dcv-situation.mdx                     |    1 +
 .../txt-validation_api.mdx                    |   83 +-
 .../txt-validation_dashboard.mdx              |    1 +
 .../txt-validation_post.mdx                   |    3 +
 .../txt-validation_preamble.mdx               |    1 +
 .../update-dcv-method.mdx                     |    1 +
 .../wildcard-hostname-reqs.mdx                |    1 +
 .../access/access-block-page.mdx              |    7 +-
 .../cloudflare-one/access/add-mtls-cert.mdx   |   21 +-
 .../cloudflare-one/access/add-target.mdx      |   17 +-
 .../cloudflare-one/access/app-launcher.mdx    |    4 +-
 .../cloudflare-one/access/bookmarks.mdx       |    3 +-
 .../access/create-service-token.mdx           |    3 +-
 .../access/enable-scim-on-dashboard.mdx       |   14 +-
 .../access/entra-id-terraform.mdx             |    1 +
 .../cloudflare-one/access/idp-integration.mdx |    4 +-
 .../access/isolation-prereqs.mdx              |    1 +
 .../access/saas-apps/miro-sso.mdx             |    5 +-
 .../access/saas-apps/saas-sessions.mdx        |    2 +-
 .../access/saas-apps/salesforce-sso.mdx       |    1 +
 .../access/scim-requires-login.mdx            |    2 +-
 .../access/secure-tunnel-with-access.mdx      |    1 +
 .../self-hosted-app/advanced-settings.mdx     |    1 +
 .../browser-rendering-policies.mdx            |    3 +-
 .../self-hosted-app/generic-public-app.mdx    |   25 +-
 .../self-hosted-app/product-compatibility.mdx |    8 +-
 .../access/self-hosted-app/ssh-sessions.mdx   |    2 +-
 .../access/session-duration.mdx               |    1 +
 .../access/short-lived-certs-intro.mdx        |    4 +-
 .../partials/cloudflare-one/access/tags.mdx   |    1 +
 .../access/verify-scim-provisioning.mdx       |    2 +-
 .../partials/cloudflare-one/aws-resolver.mdx  |    3 +-
 .../casb/casb-dlp-integrations.mdx            |    1 +
 .../casb/microsoft/m365-copilot-findings.mdx  |    2 +-
 .../cloudflare-one/choose-team-name.mdx       |    1 +
 .../clientless-browser-isolation.mdx          |    3 +-
 .../dex/notifications-intro.mdx               |    2 +-
 .../partials/cloudflare-one/dex/pcaps-run.mdx |    2 +-
 ...-use-case-1-3-create-quarantine-policy.mdx |    8 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 ...ase-configure-quarantine-notifications.mdx |    1 +
 .../deployment/set-up-mx-inline-step.mdx      |    3 +-
 .../dispositions-and-attributes.mdx           |   10 +-
 .../email-security/domain-information.mdx     |   20 +-
 .../email-security/enable-logs.mdx            |    3 +-
 .../onboarding-prerequisites.mdx              |    3 +-
 .../cloudflare-one/gateway/add-logo-image.mdx |    1 +
 .../gateway/debugging-policies.mdx            |    1 +
 .../gateway/egress-selector-cgnat-ips.mdx     |    3 +-
 .../gateway/egress-selector-onramps.mdx       |   14 +-
 .../gateway/egress-selector-split-tunnels.mdx |    4 +-
 .../gateway/enable-tls-decryption.mdx         |    2 +-
 .../policies/do-not-inspect-applications.mdx  |    3 +-
 .../policies/egress-destination-ip.mdx        |    1 +
 ...trict-access-to-private-networks-allow.mdx |    8 +-
 ...trict-access-to-private-networks-block.mdx |    2 +-
 ...estrict-access-to-private-networks-dns.mdx |    8 +-
 .../gateway/resolver-policies-intro.mdx       |    1 +
 .../gateway/selectors/category-options.mdx    |    1 +
 .../gateway/selectors/destination-country.mdx |    7 +-
 .../gateway/selectors/device-posture.mdx      |    1 +
 .../gateway/selectors/dns-resolver-ip.mdx     |    1 +
 .../gateway/selectors/doh-subdomain.mdx       |    1 +
 .../gateway/selectors/oidc-claims.mdx         |    4 +-
 .../gateway/selectors/protocol.mdx            |    1 +
 .../gateway/selectors/query-record-type.mdx   |    1 +
 .../gateway/selectors/security-categories.mdx |    1 +
 .../gateway/selectors/source-country-dns.mdx  |    7 +-
 .../gateway/selectors/source-country-http.mdx |    7 +-
 .../gateway/selectors/source-country.mdx      |    7 +-
 .../gateway/selectors/source-ip-dns.mdx       |    1 +
 .../gateway/selectors/source-ip-resolver.mdx  |    1 +
 .../gateway/selectors/user-email.mdx          |    4 +-
 .../gateway/selectors/user-group-email.mdx    |    6 +-
 .../gateway/selectors/user-group-ids.mdx      |    6 +-
 .../gateway/selectors/user-group-names.mdx    |    6 +-
 .../gateway/selectors/user-name.mdx           |    6 +-
 .../gateway/selectors/users-dns.mdx           |   16 +-
 .../gateway/selectors/users-http.mdx          |   16 +-
 .../gateway/selectors/users.mdx               |   13 +-
 .../partials/cloudflare-one/gateway/value.mdx |    4 +-
 .../posture/configure-posture-check.mdx       |    3 +-
 .../posture/prereqs-warp-is-deployed.mdx      |    1 +
 .../cloudflare-one/ssh/decrypt-ssh-log.mdx    |    8 +-
 .../cloudflare-one/ssh/public-key.mdx         |    6 +-
 .../cloudflare-one/ssh/restart-server.mdx     |    2 +-
 .../cloudflare-one/ssh/ssh-proxy-ca-note.mdx  |    3 +-
 .../cloudflare-one/ssh/ssh-proxy-ca.mdx       |    2 +-
 .../cloudflare-one/ssh/upload-ssh-key.mdx     |    2 +-
 .../terraform/cloudflare-resources.mdx        |  312 ++---
 .../terraform/gcp-resources.mdx               |  170 +--
 .../cloudflare-one/terraform/providers-v5.mdx |    2 +-
 .../cloudflare-one/terraform/providers.mdx    |   76 +-
 .../troubleshooting/browser-isolation.mdx     |   18 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    4 -
 .../cloudflare-one/troubleshooting/dex.mdx    |    3 -
 .../troubleshooting/email-security.mdx        |   23 +-
 .../troubleshooting/gateway.mdx               |   13 +-
 .../cloudflare-one/tunnel/1033-error.mdx      |    3 +-
 .../tunnel/account-scoped-roles.mdx           |    5 +-
 .../tunnel/add-published-application.mdx      |   13 +-
 .../cloudflared-replicas-diagram.mdx          |    1 +
 .../load-balancer-tcp-monitors.mdx            |    7 +-
 .../availability/tunnel-capacity-baseline.mdx |    7 +-
 .../availability/tunnel-capacity-intro.mdx    |    1 +
 .../tunnel/catch-all-policy.mdx               |    1 +
 .../tunnel/cgnat-split-tunnels.mdx            |    1 +
 .../cloudflare-one/tunnel/create-tunnel.mdx   |    3 +-
 .../deployment-guides/cloud-create-tunnel.mdx |    3 +-
 .../deployment-guides/cloud-private-ip.mdx    |   22 +-
 .../cloud-public-hostname.mdx                 |    1 +
 .../tunnel/diagnostics/docker.mdx             |   33 +-
 .../tunnel/diagnostics/tunnel-diag-file.mdx   |   24 +-
 .../tunnel/dns-cloudflare-settings.mdx        |    1 +
 .../tunnel/dns-records-intro.mdx              |    1 +
 .../cloudflare-one/tunnel/grpc-support.mdx    |    1 +
 .../tunnel/hostname-format-restrictions.mdx   |   21 +-
 .../tunnel/install-and-run-tunnel.mdx         |    3 +-
 .../locally-managed/tunnel-permissions.mdx    |   20 +-
 .../tunnel/logs/filter-logs.mdx               |    8 +-
 .../tunnel/logs/view-logs-dashboard.mdx       |    1 +
 .../tunnel/logs/view-logs-on-server.mdx       |    1 +
 .../tunnel/metrics/cloudflared.mdx            |    2 +-
 .../tunnel/origin-parameters.mdx              |    4 +-
 .../cloudflare-one/tunnel/package-manager.mdx |    3 +-
 .../cloudflare-one/tunnel/protocols-table.mdx |   26 +-
 .../cloudflare-one/tunnel/run-parameters.mdx  |    6 +-
 .../cloudflare-one/tunnel/tunnel-status.mdx   |   12 +-
 .../tunnel/warp-cli-target-list.mdx           |    2 +-
 .../tunnel/warp-to-tunnel-route-ips.mdx       |   66 +-
 .../warp/client-notification-lag.mdx          |    3 +-
 .../warp/client-orchestration-ips.mdx         |    1 +
 .../warp/device-enrollment-mtls.mdx           |    7 +-
 .../warp/enroll-ios-android.mdx               |    3 +-
 .../cloudflare-one/warp/ldf-best-practice.mdx |    2 +-
 .../warp/managed-networks-sha-256.mdx         |    2 +-
 .../cloudflare-one/warp/manually-reauth.mdx   |    2 +-
 .../cloudflare-one/warp/mdm-policy-file.mdx   |    9 +-
 .../cloudflare-one/warp/os-version-semver.mdx |    3 +-
 .../warp/sha-256-fingerprint.mdx              |    2 +-
 .../warp/support-ticket-best-practices.mdx    |    4 +-
 .../warp/system-requirements/linux.mdx        |   19 +-
 .../warp/system-requirements/macOS.mdx        |   19 +-
 .../warp/system-requirements/windows.mdx      |   19 +-
 .../cloudflare-one/warp/vpn-ip-traffic.mdx    |   10 +-
 .../cloudflare-one/warp/warp-modes.mdx        |    4 +-
 .../partials/containers/instance-types.mdx    |    4 +-
 .../d1/d1-do-supported-sqlite-extensions.mdx  |    4 +-
 .../partials/d1/generate-d1-api-token.mdx     |    2 +-
 .../advanced-ddos/dns-protection-intro.mdx    |    2 +-
 .../advanced-ddos/dns-setup.mdx               |    2 +-
 .../mt-advanced-ddos-systems-onboarding.mdx   |    2 +-
 .../advanced-ddos/tcp-protection-intro.mdx    |    2 +-
 .../advanced-ddos/tcp-setup.mdx               |    2 +-
 .../alerts-and-reports-independent.mdx        |    1 +
 .../ddos-protection/allowlist-ip-spoofing.mdx |    5 +-
 .../ddos-protection/atp-filter-definition.mdx |    3 +-
 .../atp-filters-rules-precedence.mdx          |    1 +
 .../ddos-protection/create-notification.mdx   |    1 +
 .../ddos-protection/ddos-attack-coverage.mdx  |   15 +-
 .../log-and-monitor-behavior-link.mdx         |    2 +-
 .../managed-rulesets/create-override.mdx      |    4 +-
 .../managed-rulesets/evaluation-behavior.mdx  |    5 +-
 .../read-only-rules-description.mdx           |    1 +
 .../managed-rulesets/read-only-rules-note.mdx |    1 +
 .../sensitivity-level-reference.mdx           |   17 +-
 .../test-rules-description.mdx                |    1 +
 .../ddos-protection/override-example.mdx      |   25 +-
 .../ddos-protection/override-logic.mdx        |    7 +-
 .../dmarc-management/domain-spoofing.mdx      |    2 +
 .../partials/dns/a-aaaa-definition.mdx        |    1 +
 src/content/partials/dns/acns-tcns-byoip.mdx  |    3 +-
 .../partials/dns/acns-tcns-conditions.mdx     |    7 +-
 src/content/partials/dns/acns-tcns-intro.mdx  |    3 +-
 .../partials/dns/aname-alias-callout.mdx      |    3 +-
 .../partials/dns/api-field-definitions.mdx    |    1 +
 src/content/partials/dns/cname-definition.mdx |    1 +
 .../partials/dns/cname-flattening-callout.mdx |    1 +
 .../conversion-subdomain-setup-callout.mdx    |    3 +-
 .../partials/dns/dns-errors-ts-action.mdx     |    3 +-
 .../partials/dns/dns-errors-ts-intro.mdx      |    5 +-
 .../partials/dns/dns-nxdomain-warning.mdx     |    5 +-
 src/content/partials/dns/dns-record-steps.mdx |   10 +-
 src/content/partials/dns/dns-scan-intro.mdx   |    1 +
 src/content/partials/dns/dns-scan-note.mdx    |    2 +-
 src/content/partials/dns/dnssec-auto-add.mdx  |    3 +
 .../partials/dns/dnssec-cloudflare-steps.mdx  |    1 +
 .../partials/dns/dnssec-definition.mdx        |    1 +
 .../partials/dns/dnssec-enabled-migration.mdx |    3 +
 .../partials/dns/dnssec-registrar-steps.mdx   |    5 +-
 .../partials/dns/export-dns-records.mdx       |    1 +
 .../partials/dns/internal-dns-beta-note.mdx   |    1 +
 .../dns/internal-dns-view-conditions.mdx      |    4 +-
 .../dns/internal-reference-zone-api.mdx       |   15 +-
 .../dns/internal-reference-zone-intro.mdx     |   11 +-
 .../dns/internal-zones-conditions.mdx         |    4 +-
 .../partials/dns/linked-peers-limit.mdx       |    1 +
 .../partials/dns/minimize-downtime-tip.mdx    |    3 +-
 .../dns/mix-proxied-and-unproxied.mdx         |    3 +
 .../partials/dns/nameserver-preamble.mdx      |    1 +
 .../dns/nameservers-registrar-callout.mdx     |    1 +
 .../partials/dns/ns-advanced-vs-custom.mdx    |    1 +
 .../partials/dns/ns-set-omission-callout.mdx  |    1 +
 src/content/partials/dns/ns-static-ips.mdx    |    3 +-
 .../partials/dns/ns-update-providers.mdx      |   71 +-
 src/content/partials/dns/onboard-warning.mdx  |    1 +
 .../partials/dns/partial-setup-definition.mdx |    3 +-
 .../dns/random-prefix-attack-definition.mdx   |    1 +
 .../partials/dns/records-name-field.mdx       |    8 +-
 .../partials/dns/recover-deleted-domain.mdx   |    1 +
 .../dns/secondary-conversion-unlink.mdx       |    3 +-
 .../partials/dns/secondary-dns-override.mdx   |    1 +
 .../partials/dns/ssltls-subdomains.mdx        |    1 +
 .../partials/dns/subdomain-customization.mdx  |    1 +
 .../partials/dns/third-party-caveat.mdx       |    5 +-
 src/content/partials/dns/tsig-create-api.mdx  |    1 +
 src/content/partials/dns/tsig-create-dash.mdx |    7 +-
 src/content/partials/dns/tsig-definition.mdx  |    3 +-
 src/content/partials/dns/tsig-name-match.mdx  |    1 +
 .../partials/dns/why-disable-dnssec.mdx       |    1 +
 .../partials/dns/zone-defaults-exceptions.mdx |    1 +
 .../partials/dns/zone-file-size-limit.mdx     |    1 +
 .../durable-objects/api-async-kv-legacy.mdx   |    4 +-
 .../durable-objects/api-storage-alarms.mdx    |    2 +-
 .../api-storage-other-methods.mdx             |    2 +-
 .../partials/durable-objects/api-sync-kv.mdx  |    2 +-
 .../do-faq-metrics-and-analytics.mdx          |    4 +-
 .../durable-objects/do-plans-note.mdx         |    2 +-
 .../durable-objects/durable-objects-sql.mdx   |  122 +-
 .../durable-objects/recommend-sqlite-do.mdx   |    2 +-
 .../what-are-durable-objects.mdx              |    2 +-
 .../email-routing-definition.mdx              |    1 +
 .../email-routing/enable-create-worker.mdx    |    1 +
 .../send-emails-workers-intro.mdx             |    3 +-
 .../partials/email-routing/types-bindings.mdx |    1 +
 .../partials/email-security/add-user.mdx      |    3 +-
 .../email-security/auto-retraction.mdx        |   18 +-
 .../bec-directory-guide-compromise-list.mdx   |    1 +
 .../bec-directory-guide-secondary-email.mdx   |    1 +
 .../email-security/contact-support.mdx        |    3 +-
 .../bcc-table-geographic-locations.mdx        |   11 +-
 .../deployment/mx-deployment-values.mdx       |    1 +
 .../deployment/mx-geographic-locations.mdx    |   19 +-
 .../email-security/deployment/o365-gcc.mdx    |    1 +
 ...-use-case-1-3-create-quarantine-policy.mdx |    6 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 .../o365-use-case-configure-domain.mdx        |   15 +-
 .../o365-use-case-transport-rules.mdx         |   41 +-
 .../deployment/setup-api-overview.mdx         |   21 +-
 .../deployment/setup-inline-overview.mdx      |   13 +-
 .../deployment/setup-overview.mdx             |    1 +
 .../email-security-description.mdx            |    3 +-
 .../email-security/outbound-email.mdx         |    1 +
 .../email-security/rename-area1-to-ces.mdx    |    1 +
 .../partials/email-security/search.mdx        |    9 +-
 .../email-security/service-addresses.mdx      |    1 +
 .../email-security/sso-enforcement.mdx        |    9 +-
 .../account-audit-logs-definition.mdx         |    3 +
 .../account-manage-active-sessions.mdx        |    3 +
 .../account-member-manage-limitation.mdx      |    1 +
 .../fundamentals/api-change-api-key.mdx       |    3 +-
 .../fundamentals/api-combine-filters.mdx      |    9 +-
 .../fundamentals/api-filter-operators.mdx     |   22 +-
 .../partials/fundamentals/api-rate-limits.mdx |   16 +-
 .../partials/fundamentals/api-using-api.mdx   |    3 +
 .../partials/fundamentals/audit-log-api.mdx   |    1 +
 .../create-account-best-practices.mdx         |    1 +
 .../cybersafe-cipa-subcategories.mdx          |   55 +-
 .../fundamentals/cybersafe-configuration.mdx  |    1 +
 .../fundamentals/cybersafe-description.mdx    |    1 +
 .../fundamentals/cybersafe-requirements.mdx   |    1 +
 .../cybersafe-school-eligibility.mdx          |    5 +-
 .../fundamentals/idp-group-deprecation.mdx    |    5 +
 .../fundamentals/lists-import-notes.mdx       |    7 +-
 .../fundamentals/new-token-warning.mdx        |    3 +
 .../fundamentals/pseudo-ipv4-warning.mdx      |    1 +
 .../fundamentals/revoke-active-sessions.mdx   |    3 +-
 .../fundamentals/ubb-recommendation.mdx       |   12 +-
 .../fundamentals/user-permissions-table.mdx   |   19 +-
 .../partials/fundamentals/user-profiles.mdx   |    3 +-
 .../partials/fundamentals/view-audit-log.mdx  |    3 +
 .../fundamentals/what-is-cloudflare.mdx       |    3 +-
 .../zero-downtime-failover-retry-on-error.mdx |    1 +
 .../hyperdrive/create-hyperdrive-binding.mdx  |    7 +-
 .../hyperdrive/create-hyperdrive-config.mdx   |    9 +-
 .../partials/hyperdrive/pooling-mode.mdx      |    1 +
 .../use-postgres-js-to-make-query.mdx         |    2 +-
 .../learning-paths/cache-basic-diagram.mdx    |    1 +
 .../learning-paths/cache-optimization.mdx     |    7 +-
 ...-network-overview-additional-resources.mdx |    3 +-
 .../china-network-overview-navigation.mdx     |   27 +-
 .../cloudflare-tunnels-origin-description.mdx |    7 +-
 .../ddos-definition-and-diagram.mdx           |    3 +-
 .../learning-paths/email-record-origin-ip.mdx |    1 +
 .../learning-paths/r2-series-navigation.mdx   |   55 +-
 .../learning-paths/sase-series-navigation.mdx |   64 +-
 .../learning-paths/warp-series-navigation.mdx |   25 +-
 .../workflows-series-navigation.mdx           |   35 +-
 .../zero-trust/blocklist-restricted-users.mdx |    3 +-
 .../blocklist-security-categories.mdx         |    1 +
 .../configure-device-agent-description.mdx    |    1 +
 .../configure-device-agent-objectives.mdx     |    9 +-
 .../zero-trust/configure-idp.mdx              |    3 +-
 .../zero-trust/connect-devices-objectives.mdx |    7 +-
 .../learning-paths/zero-trust/create-list.mdx |    3 +-
 .../device-enrollment-permissions.mdx         |    3 +-
 .../zero-trust/email-dispositions.mdx         |   15 +-
 .../zero-trust/enable-proxy-intro.mdx         |    1 +
 .../zero-trust/initial-setup-objectives.mdx   |    7 +-
 .../zero-trust/install-agent.mdx              |   26 +-
 .../learning-paths/zero-trust/mdm.mdx         |    3 +-
 .../zero-trust/split-tunnel-settings.mdx      |    7 +-
 .../validate-traffic-in-gateway.mdx           |    9 +-
 .../components-knowledge-callout.mdx          |    1 +
 .../custom-rules-definition.mdx               |    1 +
 .../dns-load-balancing-benefits.mdx           |    1 +
 .../dns-load-balancing-definition.mdx         |    1 +
 .../dns-load-balancing-limitations.mdx        |   15 +-
 .../endpoints-introduction-callout.mdx        |    1 +
 .../load-balancing/fallback-pools.mdx         |    1 +
 .../load-balancing/health-check-diagram.mdx   |    1 +
 .../load-balancing/health-check-regions.mdx   |    1 +
 .../layer-4-load-balancing-definition.mdx     |    3 +
 .../layer-7-load-balancing-benefits.mdx       |   15 +-
 .../layer-7-load-balancing-definition.mdx     |    1 +
 .../load-balancer-create-api.mdx              |  149 +--
 .../load-balancing/load-balancer-create.mdx   |   53 +-
 .../load-balancer-definition.mdx              |    1 +
 .../load-balancing/load-balancing-diagram.mdx |    1 +
 .../load-balancing/monitor-create-api.mdx     |  105 +-
 .../load-balancing/monitor-create.mdx         |    3 +-
 .../monitor-health-check-regions-options.mdx  |    5 +-
 .../load-balancing/monitor-prepare-server.mdx |    3 +
 .../load-balancing/monitor-settings-basic.mdx |   11 +-
 .../monitor-settings-consecutive.mdx          |    3 +
 .../origin-steering-definition.mdx            |    7 +-
 .../origin-steering-policies.mdx              |    1 +
 .../origin-steering-weights-definition.mdx    |    1 +
 .../origin-steering-weights-limitations.mdx   |    1 +
 .../partials/load-balancing/pool-create.mdx   |   31 +-
 .../load-balancing/pool-health-threshold.mdx  |    3 +-
 .../load-balancing/region-mapping.mdx         |    1 +
 .../route-production-traffic.mdx              |    7 +-
 .../session-affinity-by-cookie-process.mdx    |    5 +-
 .../session-affinity-definition.mdx           |    1 +
 .../spectrum-lb-limitations.mdx               |    5 +-
 .../load-balancing/test-domain-setup.mdx      |    1 +
 .../traffic-steering-definition.mdx           |    1 +
 .../unexpected-health-statuses.mdx            |    5 +-
 .../unhealthy-pool-traffic-distribution.mdx   |   10 +-
 .../partials/logs/check-log-retention.mdx     |    1 +
 .../partials/logs/disable-log-retention.mdx   |    1 +
 .../partials/logs/enable-log-retention.mdx    |    1 +
 .../partials/logs/enable-logpush-job.mdx      |    5 +-
 .../partials/logs/enable-read-permissions.mdx |    1 +
 .../partials/logs/filtering-limitations.mdx   |    1 +
 .../account-id-api-key.mdx                    |   20 +-
 .../analytics/set-thresholds-site-health.mdx  |    2 +-
 .../analytics/site-analytics.mdx              |   43 +-
 .../cloudflare-one-connectivity-options.mdx   |   35 +-
 .../cloudflare-wan/custom-ike-id-ipsec.mdx    |   13 +-
 .../cloudflare-wan/get-started.mdx            |   12 +-
 .../cloudflare-wan/load-balancing.mdx         |    2 +-
 .../reference/device-compatibility.mdx        |   60 +-
 .../cloudflare-wan/security-filters.mdx       |    2 +-
 .../cloudflare-wan/third-party/aws.mdx        |    4 +-
 .../third-party/azure-virtual-wan.mdx         |   18 +-
 .../cloudflare-wan/third-party/fitelnet.mdx   |    1 +
 .../cloudflare-wan/third-party/fortinet.mdx   |    2 +
 .../cloudflare-wan/third-party/juniper.mdx    |  218 ++--
 .../cloudflare-wan/third-party/oracle.mdx     |   59 +-
 .../cloudflare-wan/third-party/palo-alto.mdx  |  194 +--
 .../third-party/sophos-firewall.mdx           |    1 +
 .../cloudflare-wan/third-party/velocloud.mdx  |    8 +-
 .../cloudflare-wan/third-party/viptela.mdx    |   36 +-
 .../cloudflare-wan/third-party/yamaha.mdx     |   24 +-
 .../cloudflare-wan/wan-transformation.mdx     |   24 +-
 .../cloudflare-wan/zero-trust/gateway.mdx     |   11 +-
 .../cloudflare-wan/zero-trust/overview.mdx    |    6 +-
 .../zero-trust/security-services.mdx          |   35 +-
 .../cloudflare-wan/zero-trust/tunnel.mdx      |   24 +-
 .../cloudflare-wan/zero-trust/warp.mdx        |    9 +-
 .../cni-product-use-cases.mdx                 |   15 +-
 .../query-magic-transit-bandwidth-graphql.mdx |    3 +-
 ...y-magic-transit-endpoint-health-checks.mdx |  126 +-
 .../query-magic-transit-health-checks.mdx     |    2 +-
 .../ipsec-logs-troubleshooting.mdx            |    8 +-
 .../magic-transit/advertise-prefixes.mdx      |    3 +-
 .../magic-transit/cloudflare-ips.mdx          |    8 +-
 .../mtu-mss/mss-clamping-gre.mdx              |    2 +
 .../mtu-mss/mss-clamping-ipsec.mdx            |    2 +
 .../safely-withdraw-byoip-prefix.mdx          |    8 +-
 .../networking-services/magic-user-role.mdx   |    2 +-
 .../mconn/device-metrics.mdx                  |  106 +-
 .../mconn/licence-keys.mdx                    |    4 +-
 .../mconn/maintenance/activate-connectors.mdx |    2 +-
 .../maintenance/deactivate-connector.mdx      |   42 +-
 .../mconn/maintenance/default-password.mdx    |    2 +-
 .../mconn/maintenance/edit-basic-info.mdx     |   39 +-
 .../maintenance/edit-network-settings.mdx     |   46 +-
 .../mconn/maintenance/edit-sites.mdx          |   34 +-
 .../maintenance/edit-traffic-steering.mdx     |   40 +-
 .../mconn/maintenance/heartbeat.mdx           |   45 +-
 .../maintenance/interrupt-service-window.mdx  |   47 +-
 .../register-hardware-appliance.mdx           |   37 +-
 .../mconn/maintenance/remove-connectors.mdx   |   75 +-
 .../mconn/mconn-reference.mdx                 |   17 +-
 .../breakout-prioritized.mdx                  |  262 ++--
 .../app-aware-policies/netflow.mdx            |   19 +-
 .../app-aware-policies/overview.mdx           |    5 +-
 .../mconn/network-options/dhcp/dhcp-relay.mdx |    9 +-
 .../network-options/dhcp/dhcp-server.mdx      |    9 +-
 .../mconn/network-options/nat-subnet.mdx      |    1 +
 .../network-options/network-segmentation.mdx  |    9 +-
 .../mconn/network-options/routed-subnets.mdx  |    2 +-
 .../networking-services/mconn/overview.mdx    |    2 +-
 .../mconn/troubleshooting/troubleshooting.mdx |   33 +-
 .../mconn/vlan-tagging.mdx                    |    2 +-
 .../mconn/wan-two-tunnels.mdx                 |    2 +-
 .../mnm-auto-advertisement-notifications.mdx  |    2 +-
 .../mnm-magic-transit-integration.mdx         |   10 +-
 .../partials/networking-services/mnm/faqs.mdx |    2 +-
 .../mnm/routers/sflow-config.mdx              |    2 +-
 .../mnm/rules/dynamic-threshold.mdx           |   16 +-
 .../mnm/rules/overview.mdx                    |    2 +-
 .../mnm/rules/rule-notifications.mdx          |   21 +-
 .../mnm/rules/s-flow-ddos-attack.mdx          |   16 +-
 .../mnm/rules/static-threshold.mdx            |   32 +-
 .../mnm/tutorials/graphql-analytics.mdx       |    1 +
 ...-vendor-guidelines-mss-settings-origin.mdx |    6 +-
 .../reference/longest-prefix-match.mdx        |    2 +-
 .../traffic-steering-region-codes.mdx         |   22 +-
 .../reference/tunnel-health-checks.mdx        |   23 +-
 .../routing/anycast-warning.mdx               |    2 +-
 .../routing/bgp-config-steps.mdx              |   18 +-
 .../configure-cloudflare-source-ips.mdx       |    2 -
 .../routing/mcn-cloudflare-wan-on-ramps.mdx   |   18 +-
 .../networking-services/sites/sites-brief.mdx |    2 +-
 .../networking-services/sites/sites.mdx       |  156 ++-
 .../troubleshoot-connectivity.mdx             |   17 +-
 .../check-tunnel-healthchecks-dash.mdx        |  121 +-
 .../health-checks-compatible-cmb-eu.mdx       |    2 +-
 .../magic-tunnel-health-alerts.mdx            |   33 +-
 .../tunnel-health/mconn-heartbeat-health.mdx  |    2 +-
 .../troubleshoot-tunnel-health.mdx            |  146 +--
 .../virtual-networks-concept.mdx              |   39 +-
 .../partials/notifications/get-started.mdx    |    1 +
 src/content/partials/pages/c3-adapter.mdx     |    3 +
 .../pages/c3-run-command-no-directory.mdx     |    7 +-
 .../pages/cli-precedence-over-file.mdx        |    3 +
 .../partials/pages/custom-domain-steps.mdx    |    1 -
 .../pages/deploy-to-pages-steps-no-preset.mdx |    1 -
 .../deploy-to-pages-steps-with-preset.mdx     |    1 -
 src/content/partials/pages/do-note.mdx        |    1 +
 .../pages/framework-guides/create-gh-repo.mdx |    1 +
 .../create-github-repository-prefix.mdx       |    1 +
 .../framework-guides/git-integration.mdx      |    3 +-
 .../pages/framework-guides/learn-more.mdx     |    3 +-
 .../pages/get-started-git-connect-pages.mdx   |    5 +-
 .../pages/get-started-git-manage-site.mdx     |   11 +-
 .../pages/git-integration-warning.mdx         |    3 +
 .../partials/pages/prod-branch-update.mdx     |    1 +
 .../pages/tutorials-before-you-start.mdx      |    1 +
 .../partials/pages/web-analytics-setup.mdx    |    2 +-
 src/content/partials/queues/enable-queues.mdx |    2 +-
 .../event-subscriptions/access-events.mdx     |   58 +-
 .../event-subscriptions/artifacts-events.mdx  |  366 +++---
 .../queues/event-subscriptions/kv-events.mdx  |   56 +-
 .../queues/event-subscriptions/r2-events.mdx  |   60 +-
 .../super-slurper-events.mdx                  |  202 +--
 .../event-subscriptions/vectorize-events.mdx  |   62 +-
 .../event-subscriptions/workers-ai-events.mdx |   90 +-
 .../workers-builds-events.mdx                 |  264 ++--
 .../event-subscriptions/workflows-events.mdx  |  180 +--
 .../partials/r2/custom-domain-steps.mdx       |    1 -
 .../partials/r2/link-to-workers-r2-api.mdx    |    2 +-
 .../partials/r2/migrator-etag-caveat.mdx      |    3 +-
 .../common/create-your-own-ui-examples.mdx    |    5 +-
 .../common/default-meeting-examples.mdx       |    5 +-
 .../web/breakout-room-close-breakout.mdx      |   13 +-
 .../web/breakout-room-creation-sdk-api.mdx    |   17 +-
 .../breakout-room-fetch-meetings-sdk-api.mdx  |   14 +-
 .../breakout-room-handle-breakout-events.mdx  |   11 +-
 ...breakout-room-move-participant-sdk-api.mdx |   19 +-
 ...t-room-move-preset-participant-sdk-api.mdx |   15 +-
 .../web/breakout-room-permission-check.mdx    |   16 +-
 .../realtimekit/web/language-pack-json.mdx    |  822 ++++++------
 .../description-of-design-guides.mdx          |    1 +
 ...scription-of-ref-architecture-diagrams.mdx |    1 +
 .../description-of-ref-architectures.mdx      |    1 +
 .../what-is-cloudflare-link.mdx               |    3 +-
 .../partials/registrar/email-verification.mdx |    3 +
 .../partials/registrar/enable-dnssec.mdx      |    3 +-
 .../registrar/icann-unverified-email.mdx      |    3 +-
 .../partials/registrar/requirements.mdx       |    1 +
 .../partials/registrar/restrictions.mdx       |   12 +-
 .../partials/registrar/verify-dnssec.mdx      |    1 +
 .../configuration-rule-link-to-examples.mdx   |    1 +
 .../rules/configuration-rule-promotion.mdx    |    3 +
 .../partials/rules/error-pages-list.mdx       |    1 +
 .../partials/rules/page-rules-migration.mdx   |    1 +
 .../rules/rules-creation-workflow.mdx         |    1 +
 .../partials/rules/rules-templates.mdx        |    6 +-
 .../rules/terraform-additional-resources.mdx  |    5 +-
 .../rules/transform/header-valid-names.mdx    |    5 +-
 .../rules/transform/header-valid-values.mdx   |    5 +-
 .../ruleset-engine/max-expression-length.mdx  |    1 +
 .../ruleset-engine/rule-position-values.mdx   |    7 +-
 .../brand-protection-alerts.mdx               |    1 +
 .../brand-protection-definition.mdx           |    3 +-
 .../security-center/scan-frequency.mdx        |    3 +-
 .../security-center/scan-properties.mdx       |    9 +-
 .../security-insights-definition.mdx          |    1 +
 .../partials/smart-shield/argo-analytics.mdx  |    2 +-
 .../partials/smart-shield/argo-intro.mdx      |    2 +-
 .../concurrent-connections-explainer.mdx      |    2 +-
 .../smart-shield/dcei-pool-requirements.mdx   |    2 +-
 .../smart-shield/health-checks-analytics.mdx  |    2 +-
 .../smart-shield/health-checks-intro.mdx      |    2 +-
 .../smart-shield/health-checks-regions.mdx    |    4 +-
 .../smart-shield/smart-shield-callout.mdx     |    2 +-
 .../partials/smart-shield/zone-lockdown.mdx   |    2 +-
 .../spectrum-with-load-balancer-api.mdx       |   63 +-
 .../spectrum-with-load-balancer-dash.mdx      |    3 +-
 .../partials/speed/rocket-loader-csp.mdx      |    3 +-
 src/content/partials/speed/user-agents.mdx    |   10 +-
 .../ssl/acm-ca-hostnames-conditions.mdx       |    1 +
 src/content/partials/ssl/acm-definition.mdx   |    1 +
 .../partials/ssl/acm-validate-cert.mdx        |    5 +-
 .../ssl/aop-per-hostname-upload-cert.mdx      |    3 +-
 .../partials/ssl/caa-records-added-by-cf.mdx  |    3 +-
 .../partials/ssl/caa-records-definition.mdx   |    1 +
 .../ssl/change-encryption-mode-api.mdx        |    1 +
 .../ssl/change-encryption-mode-dash.mdx       |    1 +
 .../ssl/cipher-suites-api-linkout.mdx         |    3 +-
 .../partials/ssl/cipher-suites-definition.mdx |    1 +
 .../ssl/cipher-suites-saas-linkout.mdx        |    3 +-
 .../ssl/ciphers-api-general-notes.mdx         |    2 +-
 .../partials/ssl/cname-cert-verification.mdx  |    1 +
 src/content/partials/ssl/csr-definition.mdx   |    1 +
 .../partials/ssl/custom-cert-ciphers.mdx      |    7 +-
 .../ssl/custom-cert-openssl-commands.mdx      |    1 +
 .../ssl/custom-certificates-definition.mdx    |    1 +
 .../custom-origin-trust-store-definition.mdx  |    1 +
 .../partials/ssl/dcv-certificate-renewal.mdx  |    9 +-
 .../partials/ssl/dcv-conflicting-records.mdx  |    3 +-
 src/content/partials/ssl/dcv-definition.mdx   |    1 +
 .../ssl/dcv-invalid-token-situations.mdx      |    1 +
 .../partials/ssl/dcv-path-security.mdx        |    1 +
 .../partials/ssl/dcv-renewal-fallback.mdx     |    1 +
 .../partials/ssl/dcv-validate-patch.mdx       |    1 +
 .../ssl/encryption-mode-definition.mdx        |    1 +
 .../ssl/enforce-https-recommendation.mdx      |    1 +
 .../partials/ssl/error-rate-limiting.mdx      |    1 +
 .../ssl/generic-validation-process.mdx        |    1 +
 .../partials/ssl/geokey-manager-v1.mdx        |    1 +
 .../ssl/get-started-additional-features.mdx   |    7 +-
 .../ssl/http-cname-validation-process.mdx     |    1 +
 .../partials/ssl/http-to-txt-schedule.mdx     |    3 +-
 .../partials/ssl/keyless-ssl-definition.mdx   |    1 +
 .../partials/ssl/keyless-tunnel-setup.mdx     |    1 +
 .../partials/ssl/keyless-upload-preamble.mdx  |    1 +
 .../partials/ssl/origin-ca-pause-error.mdx    |    3 +-
 .../ssl/partial-zone-acm-dcv-nonwildcard.mdx  |    8 +-
 .../ssl/partial-zone-acm-dcv-wildcard.mdx     |    5 +-
 src/content/partials/ssl/ssl-mode-errors.mdx  |    1 +
 src/content/partials/ssl/ssl-mode-no-aop.mdx  |    1 +
 .../ssl/ssl-recommender-post-setup.mdx        |    3 +-
 .../partials/ssl/ssl-recommender-prereqs.mdx  |    7 +-
 src/content/partials/ssl/test-tls-version.mdx |    3 +-
 .../ssl/tls-1.3-cipher-limitations.mdx        |    1 +
 .../ssl/total-tls-character-limitation.mdx    |    3 +-
 .../partials/ssl/txt-validation-api.mdx       |   53 +-
 .../partials/ssl/txt-validation-dashboard.mdx |    1 +
 .../ssl/txt-validation-definition.mdx         |    1 +
 .../partials/ssl/txt-validation-preamble.mdx  |    1 +
 .../ssl/universal-ssl-enable-full.mdx         |    1 +
 .../partials/ssl/universal-ssl-validity.mdx   |    3 +-
 .../ssl/ussl-limitations-solutions.mdx        |    7 +-
 .../partials/ssl/ussl-limitations-table.mdx   |    1 +
 .../partials/ssl/validation-level-note.mdx    |    1 +
 .../stream/android_playback_code_snippet.mdx  |    1 +
 .../stream/chromecast_limitations.mdx         |    1 +
 .../stream/ios_playback_code_snippet.mdx      |    1 +
 src/content/partials/stream/prereqs.mdx       |    3 +
 .../prereqs_first_start_live_streaming.mdx    |    3 +
 .../partials/stream/srt-supported-modes.mdx   |    3 +
 .../directory-listing-definition.mdx          |    2 +-
 src/content/partials/style-guide/icons.mdx    |    2 +-
 .../style-guide/public-stats-definition.mdx   |    2 +-
 .../partials/style-guide/tab-guidance.mdx     |    4 +-
 .../partials/style-guide/table-guidelines.mdx |    2 +-
 src/content/partials/support/2fa-enable.mdx   |    1 +
 src/content/partials/support/2fa-overview.mdx |    1 +
 .../partials/tenant/account-definition.mdx    |    1 +
 .../tenant/account-details-preamble.mdx       |    1 +
 .../partials/tenant/account-details.mdx       |   23 +-
 .../partials/tenant/account-preamble.mdx      |    1 +
 .../partials/tenant/create-account-api.mdx    |   70 +-
 .../partials/tenant/create-account-dash.mdx   |    1 +
 .../tenant/create-account-subscription.mdx    |   20 +-
 .../tenant/create-zone-subscription.mdx       |   24 +-
 .../partials/tenant/resource-definition.mdx   |    1 +
 .../tenant/tenant-admin-definition.mdx        |    1 +
 .../partials/tenant/tenant-definition.mdx     |    1 +
 .../tenant/tenant-details-preamble.mdx        |    1 +
 .../partials/tenant/tenant-details.mdx        |    5 +
 .../partials/tenant/user-definition.mdx       |    1 +
 .../partials/terraform/create-r2-buckets.mdx  |    1 +
 .../terraform/find-ids-managed-rulesets.mdx   |    5 +-
 src/content/partials/terraform/find-ids.mdx   |    5 +-
 .../import-delete-existing-rulesets.mdx       |    5 +-
 .../partials/terraform/v4-code-snippets.mdx   |    3 +-
 .../partials/terraform/v5-code-snippets.mdx   |    1 +
 .../partials/time-services/ntp-definition.mdx |    1 +
 .../partials/turnstile/challenge-behavior.mdx |    1 +
 .../partials/turnstile/privacy-policy.mdx     |    2 +-
 .../partials/turnstile/proxied-hostnames.mdx  |    1 +
 .../turnstile/security-requirements.mdx       |    2 +
 .../partials/turnstile/siteverify-warning.mdx |    1 +
 src/content/partials/turnstile/siteverify.mdx |    3 +-
 .../partials/turnstile/test-secret-key.mdx    |    3 +-
 .../partials/turnstile/test-sitekey.mdx       |    3 +-
 .../turnstile/troubleshooting-steps.mdx       |   21 +-
 .../partials/turnstile/widget-components.mdx  |   11 +-
 .../partials/vectorize/vectorize-ga.mdx       |    3 +
 .../partials/vectorize/vectorize-pricing.mdx  |    8 +-
 .../create-environment-situation.mdx          |    1 +
 .../version-management/edit-version.mdx       |    7 +-
 .../enable-default-creation.mdx               |    7 +-
 .../version-management/enable-versioning.mdx  |    5 +-
 .../environment-defaults.mdx                  |    7 +-
 .../environment-definition.mdx                |    1 +
 .../production-read-only-default.mdx          |    1 +
 .../version-management/promote-version.mdx    |    4 +-
 .../version-management/test-version.mdx       |    3 +-
 .../version-management/version-definition.mdx |    1 +
 .../waf/api-create-ruleset-with-rule.mdx      |    1 +
 src/content/partials/waf/list-advantages.mdx  |    7 +-
 src/content/partials/waf/managed-lists.mdx    |    4 +-
 .../waf/open-ports-blocked-traffic.mdx        |    1 +
 .../waf/rate-limiting-best-practices.mdx      |   11 +-
 .../waf/rate-limiting-rule-parameters.mdx     |   15 +-
 .../partials/waf/rules-next-steps-table.mdx   |    6 +-
 .../waiting-room/change-queueing-method.mdx   |    7 +-
 .../partials/waiting-room/queue-all.mdx       |    1 +
 .../partials/waiting-room/queue-some.mdx      |    1 +
 .../partials/warp-client/modes-options.mdx    |   13 +-
 .../web-analytics-definition.mdx              |    1 +
 .../web-analytics-notifications.mdx           |    1 +
 .../web-analytics-proxied-setup.mdx           |    1 +
 .../web-analytics-troubleshooting.mdx         |    3 +
 .../partials/web3/cloudflare-settings.mdx     |    1 +
 .../partials/web3/create-gateway-api.mdx      |   31 +-
 .../partials/web3/pricing-page-reference.mdx  |    3 +
 .../workers-ai/custom_requirements.mdx        |    3 +
 .../partials/workers-ai/file_issues.mdx       |    3 +
 .../workers-ai/openai-compatibility.mdx       |    1 +
 .../workers-vpc/create-tunnel-steps.mdx       |    2 +-
 .../partials/workers-vpc/required-roles.mdx   |    1 +
 .../workers/ai-local-usage-charges.mdx        |    3 +
 .../partials/workers/c3-definition.mdx        |    1 +
 .../partials/workers/compute-per-request.mdx  |    3 +-
 .../workers/content_and_contentoptions.mdx    |    3 +
 .../workers/dash-creation-next-steps.mdx      |    1 -
 .../partials/workers/env_and_secrets.mdx      |    1 +
 .../partials/workers/envvar-example.mdx       |    1 +
 .../workers/fetch-html-example-js.mdx         |   15 +-
 .../partials/workers/get-started-dash.mdx     |    3 +-
 .../workers/isolate-cpu-flexibility.mdx       |    1 +
 .../partials/workers/isolate-description.mdx  |    1 +
 .../partials/workers/limits_increase.mdx      |    3 +
 .../partials/workers/nodejs-compat-howto.mdx  |    2 +
 .../partials/workers/playground-callout.mdx   |    3 +
 src/content/partials/workers/prereqs.mdx      |    8 +-
 .../partials/workers/redirect-example-js.mdx  |   11 +-
 .../partials/workers/remote-binding-note.mdx  |    2 +-
 .../workers/request-dot-clone-warning.mdx     |    2 +-
 .../respond-another-site-example-js.mdx       |   27 +-
 .../workers/return-html-example-js.mdx        |   17 +-
 .../workers/return-json-example-js.mdx        |   13 +-
 .../workers/service-binding-rpc-example.mdx   |    1 +
 .../workers/storage-products-table.mdx        |   22 +-
 .../workers/testing-pages-functions.mdx       |    3 +
 .../workers/tutorials-before-you-start.mdx    |    1 +
 .../partials/workers/workers_logs_pricing.mdx |   11 +-
 .../workers/wrangler-commands/containers.mdx  |   16 +-
 .../workers/wrangler-commands/r2-sql.mdx      |   11 +-
 .../partials/workers/wrangler-commands/r2.mdx |   98 +-
 .../workflows/workflows-type-parameters.mdx   |    3 +-
 .../partials/zaraz/zaraz-definition.mdx       |    1 +
 src/pages/agent-setup/index.astro             |   49 +-
 src/pages/plans.astro                         |    4 +-
 3654 files changed, 34114 insertions(+), 33884 deletions(-)
 delete mode 100644 src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx

diff --git a/.agents/references/procedures.md b/.agents/references/procedures.md
index 04454ac541394b5..b335d124dc55fb0 100644
--- a/.agents/references/procedures.md
+++ b/.agents/references/procedures.md
@@ -11,7 +11,10 @@ Wrap all multi-step procedures in the `Steps` component:
 ```mdx
 import { Steps } from "~/components";
 
-<Steps>1. Step one 2. Step two</Steps>
+<Steps>
+1. Step one
+2. Step two
+</Steps>
 ```
 
 Single-step procedures: fold the step into the introductory sentence rather than making a one-item list.
@@ -23,17 +26,14 @@ Sub-steps use lowercase letters (a, b, c). Sub-sub-steps use lowercase Roman num
 ## Writing rules
 
 **Order**: state location before action, purpose before action.
-
 - "In the **DNS** section, select **Add record**." (location → action)
 - "To delete the rule, select **Delete**." (purpose → action)
 
 **First step**: consolidate login and navigation. Do not make "Log in" its own step if the next step is navigating somewhere.
-
 - "Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **DNS** > **Records**."
 - Write "log in to" (three words), not "log into".
 
 **Optional steps**: prefix with `(Optional)` as the first word.
-
 - "(Optional) Enter a description for the rule."
 
 **Enter key**: if the user must press **Enter** after a step, include it in that step.
@@ -62,10 +62,10 @@ Provide a screenshot when the UI element is genuinely hard to locate without one
 
 ## Terminology in procedures
 
-| Use                | Not              |
-| ------------------ | ---------------- |
-| select             | click            |
-| go to              | navigate to      |
+| Use | Not |
+| --- | --- |
+| select | click |
+| go to | navigate to |
 | turn on / turn off | enable / disable |
-| log in to          | log into         |
-| (Optional)         | Optional:        |
+| log in to | log into |
+| (Optional) | Optional: |
diff --git a/.agents/skills/dependabot-review/SKILL.md b/.agents/skills/dependabot-review/SKILL.md
index 1b684c642fe06e3..9ad186440519dd9 100644
--- a/.agents/skills/dependabot-review/SKILL.md
+++ b/.agents/skills/dependabot-review/SKILL.md
@@ -62,7 +62,7 @@ grep -r "require(['\"]<package>['\"]" src/ worker/ bin/ -l
 grep '"<package>"' package.json
 
 # If transitive, who pulls it in?
-node -e "const lock = require('./pnpm-lock.yaml'); ..."
+node -e "const lock = require('./pnpm-lock.yaml'); ..." 
 # or just:
 grep -A2 '"<package>"' pnpm-lock.yaml | grep -v "^--$" | head -20
 ```
@@ -79,7 +79,6 @@ grep -r "<method_name>\|<export_name>" src/ worker/ bin/ --include="*.ts" --incl
 ```
 
 For Astro/MDX source files under `src/content/docs/`, map them to their route:
-
 - `src/content/docs/workers/get-started/index.mdx` → `/workers/get-started/`
 - `src/content/docs/pages/platform/limits.mdx` → `/pages/platform/limits/`
 
@@ -89,13 +88,13 @@ If more than ~5 files use the changed API, list a representative sample (pick th
 
 Rate the probability that this bump causes a **visible change to the docs site**:
 
-| Rating       | Meaning                                                                                       |
-| ------------ | --------------------------------------------------------------------------------------------- |
-| **None**     | Package not used directly; transitive only; or only internal/type changes                     |
-| **Very Low** | Direct dependency, but changed APIs are not called in this repo                               |
-| **Low**      | Changed APIs are called, but only in build tooling (not runtime or content rendering)         |
-| **Medium**   | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
-| **High**     | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior       |
+| Rating | Meaning |
+|--------|---------|
+| **None** | Package not used directly; transitive only; or only internal/type changes |
+| **Very Low** | Direct dependency, but changed APIs are not called in this repo |
+| **Low** | Changed APIs are called, but only in build tooling (not runtime or content rendering) |
+| **Medium** | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
+| **High** | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior |
 
 For **security fixes**: note what the vulnerability affects and whether our usage is in the vulnerable code path.
 
@@ -143,6 +142,5 @@ For grouped PRs (non-major group), the PR body lists each package separately. Pr
 ### Packages with no public changelog
 
 If a package has no changelog and the upstream repo is private or unavailable:
-
 1. Check npm for version diff: `npm diff <package>@<old> <package>@<new>`
 2. If that also fails, note it explicitly and rate impact conservatively based on usage alone.
diff --git a/.agents/skills/docs-review/SKILL.md b/.agents/skills/docs-review/SKILL.md
index 7ba37ceae99136b..4f37fbdb5b612a6 100644
--- a/.agents/skills/docs-review/SKILL.md
+++ b/.agents/skills/docs-review/SKILL.md
@@ -150,19 +150,19 @@ Read full files for context — code that looks wrong in a diff may be correct i
 
 See `.agents/references/style-guide.md` for the full rules. Quick reference:
 
-| Rule                     | Detail                                                                                            |
-| ------------------------ | ------------------------------------------------------------------------------------------------- |
-| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                       |
-| Component imports        | Every component used must be imported from `~/components`                                         |
-| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                           |
-| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                  |
-| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                  |
-| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                       |
-| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs |
-| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                      |
-| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc. |
-| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                  |
-| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover |
+| Rule                     | Detail                                                                                               |
+| ------------------------ | ---------------------------------------------------------------------------------------------------- |
+| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                          |
+| Component imports        | Every component used must be imported from `~/components`                                            |
+| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                              |
+| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                     |
+| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                     |
+| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                          |
+| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs    |
+| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                         |
+| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc.    |
+| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                     |
+| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover    |
 
 ### 3. Assess What to Flag
 
diff --git a/.agents/skills/eli5/SKILL.md b/.agents/skills/eli5/SKILL.md
index 3158464814dc939..47c5f5e78f0cc91 100644
--- a/.agents/skills/eli5/SKILL.md
+++ b/.agents/skills/eli5/SKILL.md
@@ -67,7 +67,7 @@ Use this skill for content that targets a broad or mixed audience — not every
 
 - **Developer-focused API and SDK references** (e.g. Workers, D1, R2, Durable Objects, KV) — the audience is developers who are expected to know programming concepts, database terminology, and API conventions
 - **Code-heavy tutorials targeting developers** — readers self-select into these and already have the prerequisite knowledge
-- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon _is_ the content
+- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon *is* the content
 
 **Use your judgment for everything else.** Ask: "Would a reasonable reader of this page already know these terms?" If yes, this skill adds little value. On the other hand, if the following are true, this skill could provide significant value.
 
@@ -105,13 +105,13 @@ I read the file, detect sections, analyze organization, and identify the content
 
 After detection, I ask you to confirm the content type. Different types require different strategies:
 
-| Type      | Strategy                                         |
-| --------- | ------------------------------------------------ |
-| Overview  | Problem → Solution → Benefit                     |
-| Concept   | Analogy → Plain explanation → Technical details  |
-| How To    | Context → Multi-path steps (Dashboard + API)     |
+| Type | Strategy |
+|------|----------|
+| Overview | Problem → Solution → Benefit |
+| Concept | Analogy → Plain explanation → Technical details |
+| How To | Context → Multi-path steps (Dashboard + API) |
 | Reference | Use-case organization with two-tier descriptions |
-| Tutorial  | Progressive complexity with code explanations    |
+| Tutorial | Progressive complexity with code explanations |
 
 **3. Apply Enhancement Constraints**
 
@@ -225,7 +225,7 @@ These are the highest-risk categories when documentation has been simplified. Pr
 
 1. **Simplified mechanism descriptions** — Any "how it works" explanation added during simplification that was not in the original. These carry the highest risk: a plausible-sounding explanation that describes the wrong mechanism is worse than the original jargon. Verify the actual mechanism against the source docs in this repository.
 
-2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies _where_ crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
+2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies *where* crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
 
 3. **Net-new claims** — Any explanation, context, or framing added during simplification that was not present in the original document. Every piece of new information requires a citation. If the original said "zones pair with resolver policies" and the simplification adds "based on source IP, user identity, or domain," verify that all three of those selectors are actually supported.
 
@@ -249,12 +249,12 @@ These are the highest-risk categories when documentation has been simplified. Pr
    - **low** — Claim is minor or widely accepted common knowledge.
 5. **Report** — Present findings in this format:
 
-| #   | Claim (exact text)                                  | Source                                                                                          | Status                   |
-| --- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------ |
-| 1   | "Workers KV supports keys up to 512 bytes"          | `src/content/docs/kv/api/write-key-value-pairs.mdx`                                             | ✅ sourced               |
-| 2   | "Latency is under 50 ms globally"                   | —                                                                                               | ❌ unsourced (high)      |
-| 3   | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
-| 4   | "zones pair with resolver policies"                 | present in original — `path/to/file.mdx:34`                                                     | ✅ sourced (original)    |
+| # | Claim (exact text) | Source | Status |
+|---|---|---|---|
+| 1 | "Workers KV supports keys up to 512 bytes" | `src/content/docs/kv/api/write-key-value-pairs.mdx` | ✅ sourced |
+| 2 | "Latency is under 50 ms globally" | — | ❌ unsourced (high) |
+| 3 | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
+| 4 | "zones pair with resolver policies" | present in original — `path/to/file.mdx:34` | ✅ sourced (original) |
 
 ### Rules
 
@@ -397,12 +397,10 @@ Produce output following this template exactly. All sections are required.
 ## Simplification Overview
 
 **What was confusing:**
-
 - [Issue pattern 1]
 - [Issue pattern 2]
 
 **Approach taken:**
-
 - [Strategy 1]
 - [Strategy 2]
 
@@ -411,17 +409,14 @@ Produce output following this template exactly. All sections are required.
 ## Section: [Original Heading]
 
 ### Original Content
-
 [Exact text from source, preserved]
 
 ### Issues Identified
-
 **Jargon:** [terms and why problematic]
 **Assumptions:** [unstated prerequisites]
 **Unclear Logic:** [structural issues]
 
 ### Simplified Version
-
 **In Plain Language:** [One-sentence distillation]
 **What It Is:** [2-3 paragraphs building from basics]
 **Why It Matters:** [Benefits and value]
@@ -439,9 +434,9 @@ Produce output following this template exactly. All sections are required.
 
 ## Terminology Index
 
-| Term   | Line          | Defined? | Suggested Action                                                        |
-| ------ | ------------- | -------- | ----------------------------------------------------------------------- |
-| [term] | [line number] | Yes/No   | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
+| Term | Line | Defined? | Suggested Action |
+| ---- | ---- | -------- | ---------------- |
+| [term] | [line number] | Yes/No | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
 
 ---
 
@@ -454,9 +449,9 @@ Produce output following this template exactly. All sections are required.
 
 Line-numbered recommendations for further improvements:
 
-| Line(s) | Current Approach | Suggested Enhancement | Why                             | Priority        |
-| ------- | ---------------- | --------------------- | ------------------------------- | --------------- |
-| [lines] | [what exists]    | [what to change]      | [why it improves accessibility] | High/Medium/Low |
+| Line(s) | Current Approach | Suggested Enhancement | Why | Priority |
+| ------- | ---------------- | --------------------- | --- | -------- |
+| [lines] | [what exists] | [what to change] | [why it improves accessibility] | High/Medium/Low |
 ```
 
 ## References
diff --git a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
index a81b5834b7aae6c..6d9e9f57671e88a 100644
--- a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
+++ b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
@@ -193,7 +193,6 @@ For detailed step-by-step setup instructions, see the [Get started guide](/dns/i
 This overview was enhanced with inline context explaining when you'd use Internal DNS, step-by-step query flow showing how views work, and three detailed use case examples with real-world scenarios. Added explanations of key concepts (views, zone referencing, privacy model) and a "Getting started" checklist.
 
 **What was added:**
-
 - Opening context: When to use Internal DNS with concrete example (lines 34-36)
 - Architecture explanations: On-ramp options, why zones are private (lines 42-44, 48-50)
 - Views explanation: Why views matter and how they enable customization (lines 73-75)
diff --git a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
index 4d1539a961ee745..742a86dc6ee14df 100644
--- a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
+++ b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
@@ -26,7 +26,6 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Purpose:** Help users quickly understand what a product/feature is and decide if they need it.
 
 **Required Elements:**
-
 - Opening benefit statement (what problem this solves)
 - Problem/Solution/Benefit structure
 - "Perfect for" self-identification section
@@ -34,7 +33,6 @@ Once content type is detected and validated, I apply type-specific simplificatio
 - Technical architecture separated to bottom
 
 **Analysis Focus:**
-
 - Does opening paragraph answer "what" and "why"?
 - Are features explained with benefits, not just descriptions?
 - Is there a clear call-to-action?
@@ -51,36 +49,32 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Pattern Example:**
 
 ❌ **Before (Technical-first):**
-
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8
-isolates for serverless code execution with sub-millisecond cold
+Product X is a distributed edge computing platform utilizing V8 
+isolates for serverless code execution with sub-millisecond cold 
 start performance.
 
 Features:
-
 - Global anycast network deployment
 - Automatic scaling and load distribution
 - Pay-per-request pricing model
 ```
 
 ✅ **After (Benefit-first):**
-
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds,
+Run code worldwide without managing servers. Deploy in seconds, 
 scale automatically, pay only for what you use.
 
 **What problem it solves:**
-Maintaining global infrastructure is expensive and complex. Product X
-runs your code in 300+ cities automatically, handling all the
+Maintaining global infrastructure is expensive and complex. Product X 
+runs your code in 300+ cities automatically, handling all the 
 infrastructure for you.
 
 **Perfect for:**
-
 - Applications needing fast global performance
 - Teams wanting to skip server management
 - Projects with variable traffic (scale from zero to millions)
@@ -89,7 +83,7 @@ infrastructure for you.
 
 ---
 
-**For technical users:** Built on V8 isolates with global anycast
+**For technical users:** Built on V8 isolates with global anycast 
 deployment. [Architecture details →]
 ```
 
@@ -100,7 +94,6 @@ deployment. [Architecture details →]
 **Purpose:** Build understanding of WHY something works the way it does.
 
 **Required Elements:**
-
 - Opening analogy or visual (accessible to all)
 - Plain language definition
 - "Why it matters" business value
@@ -109,7 +102,6 @@ deployment. [Architecture details →]
 - Technical details for advanced users (separated)
 
 **Analysis Focus:**
-
 - Is there an analogy early in the content?
 - Does it explain WHY before HOW?
 - Are use cases concrete and realistic?
@@ -126,51 +118,47 @@ deployment. [Architecture details →]
 **Pattern Example:**
 
 ❌ **Before (Technical-only):**
-
 ```markdown
 ## Rate Limiting
 
-Rate limiting implements token bucket algorithms to control request
-throughput based on configurable parameters including burst size and
+Rate limiting implements token bucket algorithms to control request 
+throughput based on configurable parameters including burst size and 
 refill rate. Requests exceeding limits receive 429 status codes.
 ```
 
 ✅ **After (Layered explanation):**
-
 ```markdown
 ## Rate Limiting
 
-**Think of it like:** A nightclub with maximum capacity. Even if
-1,000 people want to enter at once, you only let a controlled number
+**Think of it like:** A nightclub with maximum capacity. Even if 
+1,000 people want to enter at once, you only let a controlled number 
 in at a time to keep things manageable.
 
 **What it is:**
-Rate limiting controls how many requests can hit your website in a
-given time period. Without it, a sudden spike—whether from real
+Rate limiting controls how many requests can hit your website in a 
+given time period. Without it, a sudden spike—whether from real 
 users or attackers—could overwhelm your server.
 
 **Why you need it:**
-
 - Prevents DDoS attacks from taking your site down
 - Stops bots from scraping your content
 - Ensures fair usage across all users
 - Keeps infrastructure costs predictable
 
 **How it works:**
-You set a rule like "100 requests per minute per IP address." When
-someone exceeds this limit, we block additional requests until the
+You set a rule like "100 requests per minute per IP address." When 
+someone exceeds this limit, we block additional requests until the 
 time window resets.
 
 **Real scenarios:**
-
 - E-commerce site during Black Friday preventing bot purchases
 - API preventing scraping of product catalog
 - Forum preventing spam post flooding
 
 ---
 
-**For technical users:** Implements token bucket algorithm with
-configurable burst size and refill rates. Returns 429 status with
+**For technical users:** Implements token bucket algorithm with 
+configurable burst size and refill rates. Returns 429 status with 
 Retry-After header. [Implementation details →]
 ```
 
@@ -181,7 +169,6 @@ Retry-After header. [Implementation details →]
 **Purpose:** Help users successfully accomplish specific tasks.
 
 **Required Elements:**
-
 - Context (what this accomplishes, why you'd do it)
 - Prerequisites listed upfront
 - Expected outcome stated
@@ -192,7 +179,6 @@ Retry-After header. [Implementation details →]
 - Common issues and troubleshooting
 
 **Analysis Focus:**
-
 - Is context provided before steps?
 - Are prerequisites clearly stated?
 - Is there both a Dashboard and API path?
@@ -211,7 +197,6 @@ Retry-After header. [Implementation details →]
 **Pattern Example:**
 
 ❌ **Before (Steps-only):**
-
 ```markdown
 ## Enable Feature
 
@@ -222,17 +207,16 @@ Retry-After header. [Implementation details →]
 ```
 
 ✅ **After (Contextual multi-path):**
-
-````markdown
+```markdown
 ## Enable Feature
 
-**What this does:** Protects your site from [specific threat] by
+**What this does:** Protects your site from [specific threat] by 
 [specific mechanism].
 
 **Time required:** ~2 minutes  
 **Prerequisites:** Admin access to your account
 
-**What happens:** After enabling, all incoming requests will be
+**What happens:** After enabling, all incoming requests will be 
 [specific behavior]. You'll see results in Analytics within 5 minutes.
 
 ### Via Dashboard
@@ -243,7 +227,7 @@ Retry-After header. [Implementation details →]
 4. Find **Feature Name** and toggle it **On**
 5. Click **Save Changes**
 
-💡 **Note:** Changes take effect immediately, but analytics may take
+💡 **Note:** Changes take effect immediately, but analytics may take 
 5 minutes to update.
 
 ### Via API
@@ -256,17 +240,15 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_enabled": true}'
 ```
-````
 
 **Response:**
-
 ```json
 {
-	"success": true,
-	"result": {
-		"feature_enabled": true,
-		"updated_at": "2026-02-09T10:30:00Z"
-	}
+  "success": true,
+  "result": {
+    "feature_enabled": true,
+    "updated_at": "2026-02-09T10:30:00Z"
+  }
 }
 ```
 
@@ -284,10 +266,9 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 ## Troubleshooting
 
 **Problem:** Feature doesn't seem to be active  
-**Solution:** Clear your browser cache and wait 5 minutes for
+**Solution:** Clear your browser cache and wait 5 minutes for 
 propagation. Still not working? Check that [prerequisite].
-
-````
+```
 
 ---
 
@@ -323,20 +304,19 @@ propagation. Still not working? Check that [prerequisite].
 ```markdown
 ## Cache Headers
 
-**Cache-Control:** Controls caching. Values: public, private,
+**Cache-Control:** Controls caching. Values: public, private, 
 no-cache, max-age=seconds
 
 **Expires:** HTTP date for expiration
 
 **Pragma:** Legacy directive. Value: no-cache
-````
+```
 
 ✅ **After (Use-case organized with examples):**
-
-````markdown
+```markdown
 ## Cache Headers Reference
 
-**When to use:** Control how long content stays cached and who can
+**When to use:** Control how long content stays cached and who can 
 cache it.
 
 ### Common Scenarios
@@ -355,19 +335,17 @@ cache it.
 
 **What it does:** Caches content for 1 year before checking for updates
 
-**When to use:** Files that never change, like `logo-v2.png` or
+**When to use:** Files that never change, like `logo-v2.png` or 
 `style.abc123.css` with version hash in filename
 
 **Technical spec:** Integer, seconds. Range: 0-31536000 (1 year max)
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
-````
 
-**Result:** First visitor downloads the file. For the next year, all
+**Result:** First visitor downloads the file. For the next year, all 
 visitors get the cached version with zero origin requests.
 
 ---
@@ -376,18 +354,17 @@ visitors get the cached version with zero origin requests.
 
 **What it does:** Tells browsers this file will literally never change
 
-**When to use:** Combine with `max-age` for versioned assets
+**When to use:** Combine with `max-age` for versioned assets 
 (filename includes hash/version number)
 
 **Technical spec:** No value. Presence activates directive.
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
 
-**Result:** Browsers won't revalidate even on refresh. Perfect for
+**Result:** Browsers won't revalidate even on refresh. Perfect for 
 `style.abc123.css` where hash changes when content changes.
 
 ---
@@ -398,18 +375,17 @@ Cache-Control: public, max-age=31536000, immutable
 
 **What it does:** Caches content for 1 hour
 
-**When to use:** Content that updates occasionally but doesn't need
+**When to use:** Content that updates occasionally but doesn't need 
 to be real-time, like blog posts or product pages
 
 **Technical spec:** Integer, seconds
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=3600
 ```
 
-**Result:** Content stays cached for 1 hour. After expiration, next
+**Result:** Content stays cached for 1 hour. After expiration, next 
 request checks origin for updates.
 
 ---
@@ -418,18 +394,17 @@ request checks origin for updates.
 
 **What it does:** Always check with origin before using cached version
 
-**When to use:** Content that changes frequently but can still be
+**When to use:** Content that changes frequently but can still be 
 cached briefly (shopping cart, personalized pages)
 
 **Technical spec:** No value. Presence activates.
 
 **Example:**
-
 ```http
 Cache-Control: no-cache
 ```
 
-**Result:** Every request checks origin via If-Modified-Since or
+**Result:** Every request checks origin via If-Modified-Since or 
 ETag. If nothing changed, serves cached version (304 response).
 
 ---
@@ -440,21 +415,19 @@ ETag. If nothing changed, serves cached version (304 response).
 
 **What it does:** Prevents any caching
 
-**When to use:** Sensitive data (account info, payment details) or
+**When to use:** Sensitive data (account info, payment details) or 
 highly dynamic content (real-time scores, live chat)
 
 **Technical spec:** Combine both directives
 
 **Example:**
-
 ```http
 Cache-Control: private, no-store
 ```
 
-**Result:** Every request fetches fresh from origin. Nothing cached
+**Result:** Every request fetches fresh from origin. Nothing cached 
 anywhere.
-
-````
+```
 
 ---
 
@@ -500,9 +473,8 @@ const handler = async (req) => {
   return new Response('Hello')
 }
 addEventListener('fetch', e => e.respondWith(handler(e.request)))
-````
-
-````
+```
+```
 
 ✅ **After (Explained progression):**
 ```markdown
@@ -510,14 +482,14 @@ addEventListener('fetch', e => e.respondWith(handler(e.request)))
 
 ### What You'll Build
 
-A working URL shortener that redirects short links to long URLs,
+A working URL shortener that redirects short links to long URLs, 
 stores mappings, and tracks click analytics.
 
 **Live example:** `short.example.com/github` → `github.com/cloudflare`
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience with
+Developers comfortable with JavaScript. No prior experience with 
 Workers needed, but you should understand:
 - HTTP requests and responses
 - JSON data format
@@ -538,7 +510,7 @@ Workers needed, but you should understand:
 
 ## Step 1: Create Your First Worker
 
-Let's start with the absolute minimum—a Worker that responds to
+Let's start with the absolute minimum—a Worker that responds to 
 requests:
 
 ```javascript
@@ -554,7 +526,7 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-````
+```
 
 **What this code does:**
 
@@ -578,15 +550,15 @@ Now let's make it recognize short codes in the URL:
 
 ```javascript
 async function handleRequest(request) {
-	// Extract the pathname from the URL
-	// Example: https://short.example.com/github → "/github"
-	const url = new URL(request.url);
-	const shortCode = url.pathname.slice(1); // Remove leading "/"
-
-	// For now, just echo back the short code
-	return new Response(`You requested: ${shortCode}`, {
-		headers: { "content-type": "text/plain" },
-	});
+  // Extract the pathname from the URL
+  // Example: https://short.example.com/github → "/github"
+  const url = new URL(request.url)
+  const shortCode = url.pathname.slice(1) // Remove leading "/"
+  
+  // For now, just echo back the short code
+  return new Response(`You requested: ${shortCode}`, {
+    headers: { 'content-type': 'text/plain' }
+  })
 }
 ```
 
@@ -618,15 +590,15 @@ Now we can detect what short code someone's requesting...
 
 **Cause:** Your Worker is doing too much computation in a single request
 
-**Solution:** Workers have a 50ms CPU time limit. Move heavy processing
+**Solution:** Workers have a 50ms CPU time limit. Move heavy processing 
 to background tasks or use Durable Objects for longer operations.
 
 **Problem:** "KV data not updating"
 
-**Cause:** KV is eventually consistent and may take 60 seconds to
+**Cause:** KV is eventually consistent and may take 60 seconds to 
 propagate globally
 
-**Solution:** For testing, add a cache-busting parameter (`?v=2`) or
+**Solution:** For testing, add a cache-busting parameter (`?v=2`) or 
 wait 60 seconds between writes and reads.
 
 ---
@@ -636,24 +608,20 @@ wait 60 seconds between writes and reads.
 Want to take this further? Here are some ideas:
 
 **Add Click Analytics** (Medium difficulty)
-
 - Store click count in KV
 - Increment on each redirect
 - Create stats endpoint
 
 **Custom Short Codes** (Easy)
-
 - Let users choose their short code
 - Check if code is already taken
 - Return error if unavailable
 
 **Expiring Links** (Medium)
-
 - Store expiration timestamp
 - Check before redirecting
 - Return 404 if expired
-
-````
+```
 
 ---
 
@@ -674,7 +642,7 @@ Want to take this further? Here are some ideas:
 - Not: "Webhooks, which are HTTP callbacks, send notifications containing event data to your specified endpoint when certain events occur on the platform."
 
 ✅ **Active voice** over passive
-- "The system sends a notification"
+- "The system sends a notification" 
 - Not: "A notification is sent by the system"
 
 ✅ **Concrete nouns** over abstract
@@ -695,12 +663,11 @@ Want to take this further? Here are some ideas:
 
 **Always define on first use:**
 ```markdown
-An API (Application Programming Interface) defines how programs
+An API (Application Programming Interface) defines how programs 
 can request and exchange data...
-````
+```
 
 **Expand acronyms:**
-
 ```markdown
 CDN (Content Delivery Network)
 CI/CD (Continuous Integration/Continuous Deployment)
@@ -708,10 +675,9 @@ HMAC (Hash-based Message Authentication Code)
 ```
 
 **Provide context for technical terms:**
-
 ```markdown
 Not: "Configure the webhook endpoint."
-But: "A webhook endpoint is the URL where we'll send notifications.
+But: "A webhook endpoint is the URL where we'll send notifications. 
 Configure it to point to your server."
 ```
 
@@ -730,16 +696,16 @@ Configure it to point to your server."
 
 ```markdown
 **Think of It Like:**
-An API is like a restaurant menu. The menu shows you what dishes
-are available (endpoints), what customizations you can request
-(parameters like "no onions" or "extra spicy"), and what you'll
-receive (the response - your meal). You don't need to know how the
-kitchen operates or what cooking techniques they use. You just order
+An API is like a restaurant menu. The menu shows you what dishes 
+are available (endpoints), what customizations you can request 
+(parameters like "no onions" or "extra spicy"), and what you'll 
+receive (the response - your meal). You don't need to know how the 
+kitchen operates or what cooking techniques they use. You just order 
 from the menu, and the kitchen handles the rest.
 
 **Where this breaks down:**
-Unlike a restaurant where you wait for your food, API responses are
-usually near-instantaneous. Also, APIs can fail (kitchen is out of
+Unlike a restaurant where you wait for your food, API responses are 
+usually near-instantaneous. Also, APIs can fail (kitchen is out of 
 ingredients), requiring error handling.
 ```
 
@@ -747,15 +713,15 @@ ingredients), requiring error handling.
 
 ```markdown
 **Think of It Like:**
-Caching is like a library's reserve desk. Popular books are kept at
-the front desk for quick access instead of requiring a trip to the
-stacks. The first person requesting a book triggers the librarian to
-fetch it from the stacks, but then it stays at the reserve desk so
+Caching is like a library's reserve desk. Popular books are kept at 
+the front desk for quick access instead of requiring a trip to the 
+stacks. The first person requesting a book triggers the librarian to 
+fetch it from the stacks, but then it stays at the reserve desk so 
 subsequent readers can grab it immediately.
 
 **Where this breaks down:**
-Caches expire (books eventually return to the stacks), and cache
-invalidation (deciding when to return books) is more complex than
+Caches expire (books eventually return to the stacks), and cache 
+invalidation (deciding when to return books) is more complex than 
 the metaphor suggests.
 ```
 
@@ -763,15 +729,15 @@ the metaphor suggests.
 
 ```markdown
 **Think of It Like:**
-Load balancing is like grocery store checkout lanes. Instead of
-everyone lining up at a single register (which would create a huge
-wait), customers are distributed across multiple lanes. If one lane
-gets too long or a register breaks down, the store can redirect
+Load balancing is like grocery store checkout lanes. Instead of 
+everyone lining up at a single register (which would create a huge 
+wait), customers are distributed across multiple lanes. If one lane 
+gets too long or a register breaks down, the store can redirect 
 people to other lanes.
 
 **Where this breaks down:**
-Load balancers are more intelligent than checkout lane selection—they
-know which servers are healthy, how busy they are, and can route
+Load balancers are more intelligent than checkout lane selection—they 
+know which servers are healthy, how busy they are, and can route 
 based on sophisticated algorithms.
 ```
 
@@ -779,14 +745,14 @@ based on sophisticated algorithms.
 
 ```markdown
 **Think of It Like:**
-A webhook is like a doorbell notification. Instead of constantly
-checking your front door to see if someone arrived (polling), the
-doorbell alerts you the moment someone presses it (push notification).
+A webhook is like a doorbell notification. Instead of constantly 
+checking your front door to see if someone arrived (polling), the 
+doorbell alerts you the moment someone presses it (push notification). 
 You only respond when there's actually something to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have some latency due to
-network transmission. Also, webhooks can fail if your server is down
+Doorbells are instantaneous, while webhooks have some latency due to 
+network transmission. Also, webhooks can fail if your server is down 
 (like a broken doorbell).
 ```
 
@@ -794,15 +760,15 @@ network transmission. Also, webhooks can fail if your server is down
 
 ```markdown
 **Think of It Like:**
-Authentication is like a building security badge system. You present
-your badge (credentials) when entering. The system verifies you are
-who you claim to be (authentication), then checks what floors you're
-allowed to access (authorization). Different badges have different
+Authentication is like a building security badge system. You present 
+your badge (credentials) when entering. The system verifies you are 
+who you claim to be (authentication), then checks what floors you're 
+allowed to access (authorization). Different badges have different 
 access levels.
 
 **Where this breaks down:**
-Digital authentication often uses time-limited tokens (like a badge
-that expires), and can verify identity through multiple methods
+Digital authentication often uses time-limited tokens (like a badge 
+that expires), and can verify identity through multiple methods 
 (password + fingerprint), which isn't common with physical badges.
 ```
 
@@ -810,15 +776,15 @@ that expires), and can verify identity through multiple methods
 
 ```markdown
 **Think of It Like:**
-Rate limiting is like freeway on-ramp metering lights. Instead of
-letting everyone merge at once (causing congestion), the lights
-control how many cars enter per minute. This keeps traffic flowing
-smoothly on the main freeway. If you arrive too fast, you wait at
+Rate limiting is like freeway on-ramp metering lights. Instead of 
+letting everyone merge at once (causing congestion), the lights 
+control how many cars enter per minute. This keeps traffic flowing 
+smoothly on the main freeway. If you arrive too fast, you wait at 
 the red light.
 
 **Where this breaks down:**
-Rate limits are often user-specific (you get your own limit), not
-shared like a metering light. Also, rate limits reset on schedules
+Rate limits are often user-specific (you get your own limit), not 
+shared like a metering light. Also, rate limits reset on schedules 
 (every hour, every day), unlike continuous traffic flow.
 ```
 
@@ -826,14 +792,14 @@ shared like a metering light. Also, rate limits reset on schedules
 
 ```markdown
 **Think of It Like:**
-A database index is like the index at the back of a textbook. Instead
-of reading every page to find mentions of "webhooks," you check the
-index, which tells you exactly which pages to look at. The index
+A database index is like the index at the back of a textbook. Instead 
+of reading every page to find mentions of "webhooks," you check the 
+index, which tells you exactly which pages to look at. The index 
 takes up extra space, but makes searching dramatically faster.
 
 **Where this breaks down:**
-Database indexes need updating when data changes (like keeping a
-book index current as you add pages), and choosing which fields to
+Database indexes need updating when data changes (like keeping a 
+book index current as you add pages), and choosing which fields to 
 index involves tradeoffs between search speed and write speed.
 ```
 
@@ -841,16 +807,16 @@ index involves tradeoffs between search speed and write speed.
 
 ```markdown
 **Think of It Like:**
-A CDN (Content Delivery Network) is like having local warehouses
-instead of shipping everything from one central warehouse. When
-someone in California orders a product, it ships from the California
-warehouse (faster delivery). When someone in New York orders, it
+A CDN (Content Delivery Network) is like having local warehouses 
+instead of shipping everything from one central warehouse. When 
+someone in California orders a product, it ships from the California 
+warehouse (faster delivery). When someone in New York orders, it 
 ships from New York. Same product, closer source.
 
 **Where this breaks down:**
-Unlike physical warehouses with unique inventory, CDNs store copies
-of the same content in many locations. Updates need to propagate to
-all locations (cache invalidation), which has no physical warehouse
+Unlike physical warehouses with unique inventory, CDNs store copies 
+of the same content in many locations. Updates need to propagate to 
+all locations (cache invalidation), which has no physical warehouse 
 equivalent.
 ```
 
@@ -858,17 +824,17 @@ equivalent.
 
 ```markdown
 **Think of It Like:**
-Software containers are like shipping containers. Before shipping
-containers existed, moving goods required different methods for
-different types of cargo. Shipping containers standardized this—put
-anything inside a standard container, and it can go on any ship,
-truck, or train. Software containers work the same way: package your
+Software containers are like shipping containers. Before shipping 
+containers existed, moving goods required different methods for 
+different types of cargo. Shipping containers standardized this—put 
+anything inside a standard container, and it can go on any ship, 
+truck, or train. Software containers work the same way: package your 
 application and its dependencies, and it runs anywhere.
 
 **Where this breaks down:**
-Shipping containers physically isolate cargo, while software
-containers share the same operating system kernel. Also, you can run
-thousands of software containers on one machine, unlike physical
+Shipping containers physically isolate cargo, while software 
+containers share the same operating system kernel. Also, you can run 
+thousands of software containers on one machine, unlike physical 
 containers.
 ```
 
@@ -877,15 +843,15 @@ containers.
 ```markdown
 **Think of It Like:**
 Environment variables are like your application's settings panel—
-configuration values that change behavior without modifying code.
-Just like you might set your phone to dark mode or adjust notification
-preferences, environment variables let you configure database URLs,
+configuration values that change behavior without modifying code. 
+Just like you might set your phone to dark mode or adjust notification 
+preferences, environment variables let you configure database URLs, 
 API keys, or feature flags without rewriting your application.
 
 **Where this breaks down:**
-Environment variables are usually set before the application starts
-(not changed while running), and they're text-based rather than UI
-toggles. They're also specific to each deployment environment (dev,
+Environment variables are usually set before the application starts 
+(not changed while running), and they're text-based rather than UI 
+toggles. They're also specific to each deployment environment (dev, 
 staging, production).
 ```
 
@@ -904,26 +870,22 @@ When you encounter a concept not in this library, create a new metaphor by:
 **Always structure content in this order:**
 
 **1. The Problem (Why)**
-
 ```markdown
-When building applications, you often need to know when something
-happens on another platform—like when a payment completes, a file
-finishes uploading, or a deployment succeeds. Constantly checking
+When building applications, you often need to know when something 
+happens on another platform—like when a payment completes, a file 
+finishes uploading, or a deployment succeeds. Constantly checking 
 for updates (polling) wastes resources and creates delays.
 ```
 
 **2. The Solution (What)**
-
 ```markdown
-Webhooks solve this by pushing notifications to you. When an event
+Webhooks solve this by pushing notifications to you. When an event 
 happens, we immediately send a message to your server with the details.
 ```
 
 **3. The Value (Why It Matters)**
-
 ```markdown
 This means:
-
 - Your application responds in real-time instead of polling
 - You save resources (no constant checking)
 - Users get faster updates
@@ -931,10 +893,8 @@ This means:
 ```
 
 **4. The Use Cases (When)**
-
 ```markdown
 Common scenarios:
-
 - Triggering workflows when deployments complete
 - Updating your database when content changes
 - Sending notifications when payments are processed
@@ -942,10 +902,8 @@ Common scenarios:
 ```
 
 **5. The Implementation (How)**
-
 ```markdown
 To set up a webhook:
-
 1. Create an endpoint URL where we'll send notifications
 2. Configure which events you want to receive
 3. Verify requests are from us (using signatures)
@@ -987,7 +945,7 @@ Focus on outcomes, when to involve technical help, business impact
 
 **Example in Practice:**
 
-````markdown
+```markdown
 ## Webhook Signature Verification
 
 ---
@@ -1012,13 +970,11 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## 📋 Simplification Overview
 
 **What was confusing:**
-
 - [Pattern 1 - e.g., Heavy acronym use without expansion]
 - [Pattern 2 - e.g., Assumed understanding of HTTP protocols]
 - [Pattern 3 - e.g., Jumped to implementation without explaining purpose]
 
 **Approach taken:**
-
 - [Strategy 1 - e.g., Added one-sentence summaries for each concept]
 - [Strategy 2 - e.g., Expanded all acronyms on first use]
 - [Strategy 3 - e.g., Added "Why this matters" to each section]
@@ -1029,11 +985,9 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## Section: [Original Heading]
 
 ### 📄 Original Content
-```
-````
 
+```
 [Exact text from source, formatting preserved]
-
 ```
 
 ### ⚠️ Issues Identified
@@ -1052,21 +1006,21 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 
 ### ✨ Simplified Version
 
-**In Plain Language:**
+**In Plain Language:**  
 [One crisp sentence capturing the essence without jargon]
 
-**What It Is:**
-[2-3 paragraphs building understanding from basics. Define terms.
+**What It Is:**  
+[2-3 paragraphs building understanding from basics. Define terms. 
 Explain concepts. Build progressively. No jargon assumed.]
 
-**Why It Matters:**
+**Why It Matters:**  
 [Value proposition and concrete benefits]
 
 - **Benefit 1:** [Specific, concrete impact]
 - **Benefit 2:** [Specific, concrete impact]
 - **Benefit 3:** [Specific, concrete impact]
 
-**When You'd Use This:**
+**When You'd Use This:**  
 
 - **Scenario 1:** [Realistic use case with context]
   - Example: "When building a chat application that needs real-time message delivery..."
@@ -1077,23 +1031,23 @@ Explain concepts. Build progressively. No jargon assumed.]
 - **Scenario 3:** [Realistic use case with context]
   - Example: "When triggering post-deployment tasks like cache clearing..."
 
-**Think of It Like:**
+**Think of It Like:**  
 [Tech-adjacent metaphor with detailed explanation]
 
 [Full metaphor explanation, making connections explicit]
 
-**Where this metaphor breaks down:**
+**Where this metaphor breaks down:**  
 [Acknowledge limitations honestly]
 
-**Common Pitfalls:**
+**Common Pitfalls:**  
 
-- **Pitfall:** [What people commonly misunderstand]
+- **Pitfall:** [What people commonly misunderstand]  
   **Reality:** [Correction with explanation]
 
-- **Pitfall:** [Common mistake]
+- **Pitfall:** [Common mistake]  
   **Reality:** [How it actually works]
 
-**Related Concepts:**
+**Related Concepts:**  
 [Connections to things readers might already know]
 
 - "If you've used [familiar concept], this works similarly..."
@@ -1170,7 +1124,6 @@ After the main simplification and summary, I include a **"Suggestions for Enhanc
 **Format:**
 
 Each suggestion includes:
-
 - **Line reference:** Specific location in the original document
 - **Section name:** What part of the doc this applies to
 - **Current approach:** What's there now
@@ -1180,9 +1133,11 @@ Each suggestion includes:
 
 **Example:**
 
-````markdown
+```markdown
 ---
+
 ## 📝 Suggestions for Enhancement
+
 ---
 
 ## 4. Suggestions for Enhancement
@@ -1199,13 +1154,11 @@ These suggestions show where additional patterns could improve accessibility:
 **Suggested enhancement:** Add API path for technical users who prefer code
 
 **Why this helps:**
-
 - Serves both UI users and developers with their preferred method
 - Technical users can automate the process via API
 - Provides complete coverage for mixed audiences
 
 **Implementation:**
-
 ```markdown
 ### Via API
 
@@ -1214,18 +1167,18 @@ These suggestions show where additional patterns could improve accessibility:
 
 \`\`\`bash
 curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/always_use_https" \\
--H "Authorization: Bearer {token}" \\
--d '{"value":"on"}'
+  -H "Authorization: Bearer {token}" \\
+  -d '{"value":"on"}'
 \`\`\`
 
 **Response:**
 \`\`\`json
 {
-"success": true,
-"result": {
-"id": "always_use_https",
-"value": "on"
-}
+  "success": true,
+  "result": {
+    "id": "always_use_https",
+    "value": "on"
+  }
 }
 \`\`\`
 
@@ -1242,7 +1195,6 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 **Suggested enhancement:** Move advanced technical details to collapsible section
 
 **Why this helps:**
-
 - Beginners get the simple explanation without being overwhelmed
 - Experts can expand for full technical depth
 - Maintains clear progressive disclosure
@@ -1250,17 +1202,15 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 
 **Implementation:**
 \`\`\`markdown
-
 ## How TLS Encryption Works
 
-Your connection is encrypted using industry-standard TLS 1.3 protocol,
+Your connection is encrypted using industry-standard TLS 1.3 protocol, 
 ensuring no one can intercept your data in transit.
 
 <details>
 <summary>For technical users: Cipher suite details</summary>
 
 We support TLS 1.3 with modern AEAD cipher suites including:
-
 - TLS_AES_128_GCM_SHA256
 - TLS_AES_256_GCM_SHA384
 - TLS_CHACHA20_POLY1305_SHA256
@@ -1280,7 +1230,6 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 **Suggested enhancement:** Call out recommended default for most users
 
 **Why this helps:**
-
 - Reduces decision paralysis for uncertain users
 - Provides a safe starting point
 - Guides users toward best security practices
@@ -1288,23 +1237,22 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 
 **Implementation:**
 \`\`\`markdown
-
 ### Encryption Modes
 
 **Recommended for most sites:** Full (Strict)
 
-Provides maximum security by validating your origin server's
-certificate. This is the best option if your server has a valid SSL
+Provides maximum security by validating your origin server's 
+certificate. This is the best option if your server has a valid SSL 
 certificate installed.
 
 #### Other Options
 
 - **Off:** No encryption (Not recommended - only use for testing)
-- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your
+- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your 
   server doesn't have SSL)
 - **Full:** Encrypts entire path but doesn't validate certificate
 - **Full (Strict):** Maximum security with certificate validation ✅
-  \`\`\`
+\`\`\`
 
 ---
 
@@ -1316,7 +1264,6 @@ certificate installed.
 **Suggested enhancement:** Add realistic use case showing feature in action
 
 **Why this helps:**
-
 - Makes abstract benefits concrete and relatable
 - Helps users visualize how they'd use this
 - Provides "aha moment" of recognition
@@ -1328,21 +1275,19 @@ certificate installed.
 Prevents attackers from overwhelming your site with fake traffic.
 
 **Real scenario:**
-An e-commerce site during Black Friday gets hit by bots trying to
-buy limited inventory. DDoS protection automatically filters out
-the bot traffic, letting real customers complete their purchases
+An e-commerce site during Black Friday gets hit by bots trying to 
+buy limited inventory. DDoS protection automatically filters out 
+the bot traffic, letting real customers complete their purchases 
 while the attack is absorbed across Cloudflare's network.
 
-Without protection, the site would crash within minutes, losing
+Without protection, the site would crash within minutes, losing 
 thousands in sales.
 \`\`\`
 ```
-````
 
 **When to include suggestions:**
 
 Include this section when:
-
 - Multi-path opportunities exist (Dashboard + API)
 - Technical details could be collapsed
 - Missing recommended defaults
@@ -1353,7 +1298,6 @@ Include this section when:
 **Placement:**
 
 The Suggestions section appears:
-
 - After the "Summary & Recommendations" section
 - Before the "Next Steps" section
 - Clearly separated with heading and explanation
@@ -1391,7 +1335,7 @@ Before finalizing any simplified content, verify:
 ❌ "Clearly, this requires..."  
 ❌ "As everyone knows..."  
 ❌ "It's easy to..."  
-❌ "All you have to do is..."
+❌ "All you have to do is..."  
 
 **Use these respectful alternatives:**
 
@@ -1400,38 +1344,34 @@ Before finalizing any simplified content, verify:
 ✅ "This requires..."  
 ✅ "Here's how this works..."  
 ✅ "This involves..."  
-✅ "The process is..."
+✅ "The process is..."  
 
 ### Accuracy Is Non-Negotiable
 
 **Good simplification:**
-
 ```markdown
-Webhooks send HTTP POST requests to your endpoint URL whenever
-specified events occur. Think of it as a notification system where
+Webhooks send HTTP POST requests to your endpoint URL whenever 
+specified events occur. Think of it as a notification system where 
 we call your server instead of you constantly checking ours.
 ```
-
-_Accurate, clear, uses metaphor effectively_
+*Accurate, clear, uses metaphor effectively*
 
 **Bad simplification:**
-
 ```markdown
 Webhooks let programs talk to each other.
 ```
-
-_Too vague, loses important details, not actually helpful_
+*Too vague, loses important details, not actually helpful*
 
 **When complex accuracy is needed:**
 
 Use progressive disclosure:
 
 ```markdown
-**Simplified:** Rate limiting controls how many requests you can
+**Simplified:** Rate limiting controls how many requests you can 
 make in a time period, like 100 requests per minute.
 
-**More precisely:** Rate limits apply per API key and reset on a
-sliding window. If you hit the limit, you'll receive a 429 status
+**More precisely:** Rate limits apply per API key and reset on a 
+sliding window. If you hit the limit, you'll receive a 429 status 
 code with a Retry-After header indicating when you can try again.
 ```
 
@@ -1440,7 +1380,6 @@ code with a Retry-After header indicating when you can try again.
 #### API Documentation
 
 Focus on:
-
 - What the endpoint does (purpose)
 - When you'd use it (scenarios)
 - What you send (parameters explained)
@@ -1449,7 +1388,6 @@ Focus on:
 - Error handling (what can go wrong)
 
 **Add value through:**
-
 - Explaining parameter purposes, not just types
 - Showing realistic request/response examples
 - Clarifying common misunderstandings
@@ -1458,7 +1396,6 @@ Focus on:
 #### Architecture Documentation
 
 Focus on:
-
 - Problem being solved
 - Why this approach was chosen
 - Tradeoffs made (what was gained/lost)
@@ -1466,7 +1403,6 @@ Focus on:
 - Alternatives considered
 
 **Add value through:**
-
 - Explaining decision rationale
 - Making tradeoffs explicit
 - Providing context for choices
@@ -1475,14 +1411,12 @@ Focus on:
 #### Code Documentation
 
 Focus on:
-
 - What the code accomplishes
 - Why it's structured this way
 - Key concepts or patterns used
 - What to watch out for
 
 **Add value through:**
-
 - Plain-language "reading guides"
 - Explaining non-obvious choices
 - Clarifying complex logic
@@ -1520,25 +1454,22 @@ Focus on:
 ## 📋 Simplification Overview
 
 **What was done well:**
-
 - Clear section headings with logical flow
 - Terms defined on first use
 - Good use of examples
 - "Why" explained before "how"
 
 **Minor improvements suggested:**
-
 - Could add a tech-adjacent metaphor for [concept]
 - Section 3 could benefit from a concrete use case
 - Consider adding "common pitfalls" to section 5
 
 **Overall assessment:**
-This documentation is already quite accessible. The suggestions above
+This documentation is already quite accessible. The suggestions above 
 are minor enhancements rather than necessary corrections.
 ```
 
 **Avoid:**
-
 - Adding unnecessary verbosity
 - Creating problems that don't exist
 - Over-explaining clear content
@@ -1554,7 +1485,6 @@ are minor enhancements rather than necessary corrections.
    - Preserve necessary complexity
 
 2. **Layer explanations**
-
    ```markdown
    **High-level:** [What it accomplishes]
    **How it works:** [Simplified mechanism]
@@ -1581,8 +1511,7 @@ are minor enhancements rather than necessary corrections.
    - Preserve technical correctness
 
 2. **Add explanatory context**
-
-   ````markdown
+   ```markdown
    **What this code does:**
    [Plain-language explanation]
 
@@ -1590,17 +1519,12 @@ are minor enhancements rather than necessary corrections.
    [Architectural rationale]
 
    **Key points to understand:**
-
    - [Important concept 1]
    - [Important concept 2]
 
    ```python
    [Original code, unchanged]
    ```
-   ````
-
-   ```
-
    ```
 
 3. **Create "reading guides"**
@@ -1617,10 +1541,9 @@ are minor enhancements rather than necessary corrections.
    - Leave component code unchanged
 
 2. **Explain component purpose**
-
    ```markdown
    **What this component does:**
-   The <CodeBlock> component displays syntax-highlighted code with
+   The <CodeBlock> component displays syntax-highlighted code with 
    copy functionality, making it easier for readers to use the examples.
    ```
 
@@ -1631,7 +1554,7 @@ are minor enhancements rather than necessary corrections.
 
 ## Future Enhancements
 
-_Documented for future implementation_
+*Documented for future implementation*
 
 ### Planned Features
 
@@ -1644,21 +1567,19 @@ Support for code files with inline documentation:
 def process_webhook(payload, signature):
     """
     Processes incoming webhook notifications.
-
+    
     Verifies signature, parses payload, triggers handlers.
     """
     # Implementation...
 ```
 
 **Planned behavior:**
-
 - Extract docstrings and comments
 - Simplify technical language in comments
 - Add explanatory prose for complex logic
 - Generate "code walkthrough" guides
 
 **Supported formats:**
-
 - `.js`, `.ts`, `.tsx` (JavaScript/TypeScript)
 - `.py` (Python)
 - `.go` (Go)
@@ -1684,7 +1605,6 @@ Quantitative analysis:
 - **Context gap analysis** - Identify missing "why" and "when" statements
 
 **Auto-prioritization:**
-
 - Sort sections by complexity
 - Focus on highest-value simplifications
 - Generate complexity reports
@@ -1726,65 +1646,63 @@ Returns a `webhook` object.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-Set up automatic notifications that we'll send to your server whenever
+Set up automatic notifications that we'll send to your server whenever 
 specific events occur.
 
 **What It Is:**
-A webhook subscription tells our system to notify your application
-when certain events happen (like a deployment completing or content
-being published). Instead of your application constantly checking for
+A webhook subscription tells our system to notify your application 
+when certain events happen (like a deployment completing or content 
+being published). Instead of your application constantly checking for 
 updates (polling), we push notifications to you the moment events occur.
 
 **Why It Matters:**
-
 - **Real-time updates** - Your application responds immediately
 - **Resource efficiency** - No wasted API calls checking for changes
 - **Reliability** - You never miss an event
 - **Automation** - Trigger workflows automatically
 
 **When You'd Use This:**
-
 - **Deployment notifications:** Trigger post-deployment tasks when builds complete
 - **Content synchronization:** Update your CMS when content changes
 - **Monitoring:** Alert your team when errors occur
 - **Integration:** Connect multiple systems to respond to events
 
 **Think of It Like:**
-A webhook is like setting up a doorbell notification on your phone.
-Instead of constantly checking your front door camera to see if someone
-arrived (polling), the doorbell alerts you the moment someone presses
-it (push notification). You only respond when there's actually something
+A webhook is like setting up a doorbell notification on your phone. 
+Instead of constantly checking your front door camera to see if someone 
+arrived (polling), the doorbell alerts you the moment someone presses 
+it (push notification). You only respond when there's actually something 
 to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have small delays due to
-network transmission. Also, webhooks can fail if your server is down
+Doorbells are instantaneous, while webhooks have small delays due to 
+network transmission. Also, webhooks can fail if your server is down 
 (like a broken doorbell), so you need retry logic.
 
 **Parameters Explained:**
 
-- **`endpoint`** - The URL where we'll send notifications (your server's
+- **`endpoint`** - The URL where we'll send notifications (your server's 
   address that listens for webhook events). Must use HTTPS for security.
 
-- **`events`** - Which events you want to receive (like `deployment.succeeded`
+- **`events`** - Which events you want to receive (like `deployment.succeeded` 
   or `content.published`). You choose only the events you care about.
 
-- **`secret`** - Optional security key for verifying notifications actually
+- **`secret`** - Optional security key for verifying notifications actually 
   come from us. We use this to create a signature you can verify.
 
 **Common Pitfalls:**
 
 - **Pitfall:** Thinking webhooks are 100% reliable  
-  **Reality:** Network issues or server downtime can cause missed notifications.
+  **Reality:** Network issues or server downtime can cause missed notifications. 
   Implement retry logic and consider periodic polling as a backup.
 
 - **Pitfall:** Not verifying signatures  
-  **Reality:** Without signature verification, attackers could send fake
+  **Reality:** Without signature verification, attackers could send fake 
   webhooks to trigger unauthorized actions.
 
 **Related Concepts:**
-If you've used RSS feeds, webhooks work similarly—both push updates to
-you. The difference is webhooks are programmable and work with any type
+If you've used RSS feeds, webhooks work similarly—both push updates to 
+you. The difference is webhooks are programmable and work with any type 
 of event, not just content updates.
 ```
 
@@ -1795,8 +1713,8 @@ of event, not just content updates.
 ```markdown
 ## Edge Deployment Architecture
 
-We've implemented a globally distributed edge architecture utilizing
-V8 isolates for multi-tenant execution with microsecond cold starts
+We've implemented a globally distributed edge architecture utilizing 
+V8 isolates for multi-tenant execution with microsecond cold starts 
 and automatic geographic distribution.
 ```
 
@@ -1806,42 +1724,40 @@ and automatic geographic distribution.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-We run your code on servers located around the world, close to your
+We run your code on servers located around the world, close to your 
 users, making responses nearly instant regardless of where users are.
 
 **What It Is:**
-Traditional servers run in specific data centers—if your server is in
-Virginia and your user is in Singapore, every request travels across
-the world and back (adding hundreds of milliseconds). Our edge
-architecture runs your code on servers in hundreds of cities worldwide,
+Traditional servers run in specific data centers—if your server is in 
+Virginia and your user is in Singapore, every request travels across 
+the world and back (adding hundreds of milliseconds). Our edge 
+architecture runs your code on servers in hundreds of cities worldwide, 
 so requests are handled by the nearest server.
 
 **Why It Matters:**
-
 - **Speed:** Users get responses in 10-50ms instead of 200-500ms
 - **Reliability:** If one location fails, others continue serving traffic
 - **Scale:** Handles traffic spikes automatically across all locations
 - **Simplicity:** You deploy once; we handle global distribution
 
 **When You'd Use This:**
-
 - **Global applications:** Users are distributed worldwide
 - **API endpoints:** Need fast response times everywhere
 - **Dynamic content:** Content that can't be cached must still be fast
 - **High availability:** Can't afford regional outages
 
 **Think of It Like:**
-Instead of one central warehouse shipping products nationwide (slow
-delivery to distant customers), you have local warehouses in every major
-city. When someone orders, it ships from their nearest warehouse. Same
+Instead of one central warehouse shipping products nationwide (slow 
+delivery to distant customers), you have local warehouses in every major 
+city. When someone orders, it ships from their nearest warehouse. Same 
 product, faster delivery, handled automatically.
 
 **The Technical Approach:**
 
-We use "V8 isolates"—lightweight execution environments that start in
-microseconds (thousandths of a millisecond). Traditional "serverless"
-functions use containers that take 50-500ms to start. Isolates are
-fast enough that we don't need to keep them warm; they start on-demand
+We use "V8 isolates"—lightweight execution environments that start in 
+microseconds (thousandths of a millisecond). Traditional "serverless" 
+functions use containers that take 50-500ms to start. Isolates are 
+fast enough that we don't need to keep them warm; they start on-demand 
 for each request.
 
 **Why this architecture:**
@@ -1852,12 +1768,11 @@ We evaluated three approaches:
 3. **Isolate-based edge:** Global + fast (our choice)
 
 **Tradeoff made:**
-Isolates have some limitations compared to full containers (no arbitrary
-system libraries, limited execution time). We accepted these constraints
+Isolates have some limitations compared to full containers (no arbitrary 
+system libraries, limited execution time). We accepted these constraints 
 for the massive speed improvement.
 
 **Common Pitfalls:**
-
 - **Pitfall:** Assuming it works like traditional servers  
   **Reality:** Stateless execution—no persistent local storage, no background jobs
 
@@ -1865,22 +1780,20 @@ for the massive speed improvement.
   **Reality:** Implements web standards, not full Node.js APIs
 
 **Related Concepts:**
-If you've used CDNs (Content Delivery Networks), this is similar but
-for code execution, not just static files. Like a CDN distributes
+If you've used CDNs (Content Delivery Networks), this is similar but 
+for code execution, not just static files. Like a CDN distributes 
 content globally, we distribute code execution globally.
 ```
 
 ## Remember
 
 **Your mission:**
-
 - Make technical concepts accessible
 - Maintain technical accuracy
 - Respect reader intelligence
 - Focus on understanding
 
 **Always include:**
-
 - One-sentence plain language summary
 - Clear "why" and "when" explanations
 - Tech-adjacent metaphor with limitations
@@ -1888,28 +1801,25 @@ content globally, we distribute code execution globally.
 - Use cases grounding abstract concepts
 
 **Quality standards:**
-
 - Technical accuracy is non-negotiable
 - Metaphors must clarify, not confuse
 - Tone must be professional and respectful
 - No condescending language ever
 
 **Process:**
-
 1. Ask which sections to focus on
 2. Identify specific issues (jargon, assumptions, logic, context)
 3. Generate complete before/after comparison
 4. Prompt for next steps
 
 **Output:**
-
 - Create `.eli5.md` file in same directory
 - Include all required elements per section
 - Provide actionable recommendations
 - Offer clear next-step options
 
 **Philosophy:**
-Technical expertise should never be a barrier to understanding. Every
+Technical expertise should never be a barrier to understanding. Every 
 person deserves clear, accurate, respectful documentation.
 
 ---
@@ -1921,3 +1831,4 @@ person deserves clear, accurate, respectful documentation.
 **License:** MIT  
 **Version:** 1.0  
 **Last Updated:** February 2026
+
diff --git a/.agents/skills/eli5/references/content-type-guide.md b/.agents/skills/eli5/references/content-type-guide.md
index 1454cfea7242833..85d544a7c071296 100644
--- a/.agents/skills/eli5/references/content-type-guide.md
+++ b/.agents/skills/eli5/references/content-type-guide.md
@@ -7,7 +7,6 @@ Operational guide for detecting and simplifying different documentation types.
 ## Purpose
 
 This guide provides:
-
 - **Detection criteria** for identifying content types
 - **Required elements** checklist for each type
 - **Simplification patterns** specific to each type
@@ -22,7 +21,6 @@ This guide provides:
 For each content type below, the enhancement patterns are designed to ADD MINIMAL CONTEXT AND EXAMPLES, not restructure or massively expand.
 
 **Universal constraints:**
-
 - Maximum 1-2 examples per major concept
 - Each example: 5-15 lines
 - Inline "why" explanations: 1-2 sentences
@@ -33,7 +31,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Minimal testing guidance (3-5 commands for tutorials)
 
 **When patterns below suggest "Add [section]":**
-
 - Interpret as "enhance inline" not "create separate major section"
 - Keep additions brief and integrated
 - Target 1.5-2x expansion, not 5-10x
@@ -42,13 +39,13 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 ## Content Type Overview
 
-| Type          | Purpose                             | Key Pattern                  | Example                  |
-| ------------- | ----------------------------------- | ---------------------------- | ------------------------ |
-| **Overview**  | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages    |
-| **Concept**   | Build understanding of "why"        | Analogy → Plain → Technical  | "What is rate limiting?" |
-| **How To**    | Enable task completion              | Context → Multi-path steps   | "Enable HTTPS"           |
-| **Reference** | Provide comprehensive specs         | Use-case organization        | API parameters, headers  |
-| **Tutorial**  | Teach through application           | Build → Enhance → Polish     | "Build a URL shortener"  |
+| Type | Purpose | Key Pattern | Example |
+|------|---------|-------------|---------|
+| **Overview** | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages |
+| **Concept** | Build understanding of "why" | Analogy → Plain → Technical | "What is rate limiting?" |
+| **How To** | Enable task completion | Context → Multi-path steps | "Enable HTTPS" |
+| **Reference** | Provide comprehensive specs | Use-case organization | API parameters, headers |
+| **Tutorial** | Teach through application | Build → Enhance → Polish | "Build a URL shortener" |
 
 ---
 
@@ -57,7 +54,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 ### Detection Criteria
 
 **Look for:**
-
 - Product/feature name in title or H1
 - Feature lists or capability descriptions
 - "What is [Product]" sections
@@ -66,7 +62,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Lack of step-by-step instructions
 
 **Confidence signals:**
-
 - Multiple features described briefly
 - High-level product description
 - Links to detailed documentation
@@ -74,7 +69,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Pricing or plan information
 
 **Example titles:**
-
 - "Cloudflare Workers"
 - "Introduction to Gateway"
 - "What is Workers KV?"
@@ -83,7 +77,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 - [ ] Opening benefit statement (what problem solved)
 - [ ] Problem/Solution/Benefit structure
-- [ ] "Perfect for" self-identification section
+- [ ] "Perfect for" self-identification section  
 - [ ] Clear call-to-action ("Get started" link)
 - [ ] Feature descriptions with benefits (not just specs)
 - [ ] Technical architecture separated/collapsed
@@ -93,14 +87,12 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Target: 1.5-2x original length**
 
 **Minimal additions:**
-
 1. **Add 2-4 sentence problem statement** (if completely missing) at document start
 2. **Add 1-2 use case examples inline** (5-10 lines each) showing who benefits
 3. **Add inline "why"** (1 sentence) when introducing features
 4. **Define jargon on first use** (brief inline definition)
 
 **Structure to preserve:**
-
 - Keep original opening and headings
 - Don't reorganize sections
 - Don't move architecture (just add brief intro if it leads)
@@ -108,46 +100,41 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Example enhancement:**
 
 Original (8 lines):
-
 ```markdown
 # Internal DNS
 
 Manage DNS records for your private network.
 
-Internal DNS zones pair with Gateway resolver policies to control
+Internal DNS zones pair with Gateway resolver policies to control 
 DNS query responses.
 
 ## Features
-
 - Create internal zones
 - Configure views
 - Link to Gateway
 ```
 
 Enhanced (15 lines - 1.9x):
-
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS
+Manage DNS records for your private network without running your own DNS 
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS query
+Internal DNS zones pair with Gateway resolver policies to control DNS query 
 responses based on context (source IP, user identity, domain).
 
-**Example use case:** A multi-region company creates separate views for London
-and SF offices. Users query the same hostname (api.company.internal) but get
+**Example use case:** A multi-region company creates separate views for London 
+and SF offices. Users query the same hostname (api.company.internal) but get 
 different IP addresses based on location.
 
 ## Features
-
 - Create internal zones - Private namespaces accessible only via Gateway
 - Configure views - Logical groupings that route different users to different resources
 - Link to Gateway - Resolver policies determine which view to use
 ```
 
 What was added:
-
 - 1 sentence "why" (without running own servers)
 - Brief context for zones (source IP, user identity)
 - 1 example (3 lines)
@@ -169,7 +156,6 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
-
 - "What is..." or "Understanding..." titles
 - Explanatory content (not procedural)
 - "How it works" sections
@@ -178,7 +164,6 @@ What was added:
 - Analogies or metaphors (sometimes)
 
 **Confidence signals:**
-
 - Explains mechanisms, not steps
 - Educational tone
 - Links to related concepts
@@ -186,7 +171,6 @@ What was added:
 - Multiple explanation approaches
 
 **Example titles:**
-
 - "Understanding Rate Limiting"
 - "How Caching Works"
 - "What is Edge Computing?"
@@ -204,7 +188,6 @@ What was added:
 ### Simplification Pattern
 
 **Structure:**
-
 ```markdown
 # [Concept Name]
 
@@ -213,7 +196,6 @@ What was added:
 **What it is:** [Plain English definition without jargon]
 
 **Why you need it:**
-
 - [Benefit 1]
 - [Benefit 2]
 - [Benefit 3]
@@ -221,7 +203,6 @@ What was added:
 **How it works:** [Simplified technical explanation]
 
 **Real scenarios:**
-
 - [Use case 1 with context]
 - [Use case 2 with context]
 - [Use case 3 with context]
@@ -247,7 +228,6 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
-
 - Action verbs in titles (Configure, Enable, Create, Set up)
 - Numbered steps or procedures
 - "Prerequisites" sections
@@ -256,7 +236,6 @@ What was added:
 - Command examples or code blocks
 
 **Confidence signals:**
-
 - Clear sequential structure
 - Specific actionable steps
 - Tool/UI references
@@ -264,7 +243,6 @@ What was added:
 - Troubleshooting sections
 
 **Example titles:**
-
 - "Enable Always Use HTTPS"
 - "Configure DNS Settings"
 - "Create a Worker"
@@ -287,7 +265,6 @@ What was added:
 **For how-to guides, preserve existing steps and add minimal context:**
 
 **Minimal additions:**
-
 1. **Add 1-2 sentence "what this accomplishes"** at top (if missing)
 2. **Add inline "why"** (1 sentence) for non-obvious steps
 3. **Add 1 example** showing when you'd use this (3-5 lines)
@@ -295,7 +272,6 @@ What was added:
 5. **Add 1-2 troubleshooting notes** for critical failures only
 
 **Preserve:**
-
 - Original step numbering and flow
 - Existing Dashboard/API paths (don't create new ones)
 - All screenshots and UI elements
@@ -304,7 +280,6 @@ What was added:
 **Example enhancement:**
 
 Original (12 lines):
-
 ```markdown
 # Create a DNS View
 
@@ -322,11 +297,10 @@ Use the create view endpoint with zone IDs.
 ```
 
 Enhanced (20 lines - 1.67x):
-
 ```markdown
 # Create a DNS View
 
-Create a logical grouping of zones that determines which DNS records users see.
+Create a logical grouping of zones that determines which DNS records users see. 
 Useful for multi-region setups or environment separation.
 
 **Example:** Create "London View" and "SF View" to route users to nearest datacenter.
@@ -353,7 +327,6 @@ curl -X POST /api/views -d '{"name": "London View", "zone_ids": ["id1", "id2"]}'
 ```
 
 What was added:
-
 - 2-sentence purpose statement (2 lines)
 - 1 example (1 line)
 - Inline context for 2 steps (2 lines)
@@ -363,13 +336,11 @@ What was added:
 - Total: 8 lines added to 12 original = 20 lines (1.67x) ✅
 
 **What was NOT added:**
-
 - Comprehensive troubleshooting section
 - Multiple examples
 - Separate "Understanding Views" section
 - Extensive testing procedures
-
-````
+```
 
 ### Common Issues to Fix
 
@@ -443,7 +414,7 @@ What was added:
 **Example:**
 ```[language]
 [Realistic usage example]
-````
+```
 
 **Result:** [What happens when this is used]
 
@@ -452,8 +423,7 @@ What was added:
 ### [Next Option]
 
 [Same structure...]
-
-````
+```
 
 ### Common Issues to Fix
 
@@ -543,25 +513,24 @@ Add records to the zone.
 curl -X POST https://api.cloudflare.com/zones/ID/dns_records \\
   -d '{"type": "A", "name": "app", "content": "192.168.1.100"}'
 \`\`\`
-````
+```
 
 Enhanced (35 lines - 1.75x):
-
 ```markdown
 ## Step 1: Create the zone
 
-Create an internal zone that will contain your DNS records. This zone is only
+Create an internal zone that will contain your DNS records. This zone is only 
 accessible via Gateway (not public DNS).
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones \\
--d '{
-"name": "company.internal", # Your internal domain
-"type": "internal" # Marks as internal-only
-}'
+  -d '{
+    "name": "company.internal",  # Your internal domain
+    "type": "internal"             # Marks as internal-only
+  }'
 \`\`\`
 
-**Example use:** A company creates company.internal for all internal apps
+**Example use:** A company creates company.internal for all internal apps 
 (app.company.internal, api.company.internal, db.company.internal).
 
 ## Step 2: Add DNS records
@@ -570,27 +539,24 @@ Add records mapping hostnames to private IPs.
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones/ZONE_ID/dns_records \\
--d '{
-"type": "A", # Address record
-"name": "app.company.internal", # Full hostname
-"content": "192.168.1.100" # Private IP
-}'
+  -d '{
+    "type": "A",                           # Address record
+    "name": "app.company.internal",        # Full hostname
+    "content": "192.168.1.100"             # Private IP
+  }'
 \`\`\`
 
-**Test:**
+**Test:** 
 \`\`\`bash
 nslookup app.company.internal
-
 # Expected: Returns 192.168.1.100
-
 \`\`\`
 
-**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP
+**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP 
 connection or DNS settings.
 ```
 
 What was added:
-
 - Brief "why" for each step (1 sentence)
 - Inline code comments (3-4 comments)
 - 1 example showing usage (2 lines)
@@ -599,7 +565,6 @@ What was added:
 - Total: 15 lines added to 20 original = 35 lines (1.75x) ✅
 
 **What was NOT added:**
-
 - Separate "What you'll build" section
 - Multiple examples
 - Comprehensive troubleshooting section
@@ -649,19 +614,16 @@ What was added:
 Sometimes documentation combines types:
 
 ### Overview + How To
-
 **Pattern:** Product intro followed by quick start steps  
 **Approach:** Treat first section as Overview, steps as How To  
 **Example:** "Workers Overview" with "Deploy Your First Worker" steps
 
 ### Concept + Reference
-
 **Pattern:** Conceptual explanation followed by parameter reference  
 **Approach:** Layer explanation first, reference at bottom  
 **Example:** "Understanding Caching" + "Cache Headers Reference"
 
 ### Tutorial + Reference
-
 **Pattern:** Build project + API reference at end  
 **Approach:** Keep tutorial progressive, move reference to appendix  
 **Example:** "Build URL Shortener" + "Workers API Reference"
@@ -673,7 +635,6 @@ Sometimes documentation combines types:
 ## Quick Reference Cards
 
 ### Overview Page Card
-
 ```
 ✓ Opens with benefit statement
 ✓ Problem/Solution structure
@@ -683,7 +644,6 @@ Sometimes documentation combines types:
 ```
 
 ### Concept Page Card
-
 ```
 ✓ Analogy in first paragraph
 ✓ Plain definition
@@ -693,7 +653,6 @@ Sometimes documentation combines types:
 ```
 
 ### How To Page Card
-
 ```
 ✓ Context before steps
 ✓ Prerequisites listed
@@ -703,7 +662,6 @@ Sometimes documentation combines types:
 ```
 
 ### Reference Page Card
-
 ```
 ✓ Opening context
 ✓ Use-case organized
@@ -713,7 +671,6 @@ Sometimes documentation combines types:
 ```
 
 ### Tutorial Page Card
-
 ```
 ✓ "What you'll build"
 ✓ Prerequisites + time
diff --git a/.agents/skills/eli5/references/pattern-library.md b/.agents/skills/eli5/references/pattern-library.md
index f7ebb468915de2c..3d7b91b310a8918 100644
--- a/.agents/skills/eli5/references/pattern-library.md
+++ b/.agents/skills/eli5/references/pattern-library.md
@@ -7,7 +7,6 @@ A reference collection of reusable before/after patterns for simplifying technic
 ## Purpose
 
 This library provides:
-
 - **Reusable patterns** for common simplification scenarios
 - **Jargon → Plain English** translations
 - **Before/after examples** demonstrating transformations
@@ -20,7 +19,6 @@ This library provides:
 **All patterns below demonstrate minimal, integrated enhancements (1.5-2x growth)**
 
 When applying these patterns:
-
 - ✅ Add inline, not as separate major sections
 - ✅ Integrate with existing content flow
 - ✅ Keep examples brief (5-15 lines each, max 1-2 examples)
@@ -34,7 +32,6 @@ When applying these patterns:
 When a pattern shows "Add [section]" → Interpret as "add brief inline content" not "create major new section"
 
 **Example:**
-
 - Pattern says: "Add use case example"
 - **Correct:** Add 5-10 line example inline with concept
 - **Incorrect:** Create separate "Use Case Examples" section with 4 detailed scenarios
@@ -47,23 +44,23 @@ When a pattern shows "Add [section]" → Interpret as "add brief inline content"
 
 Common technical terms and their accessible alternatives:
 
-| Technical Term   | Plain English             | Context Example                                                      |
-| ---------------- | ------------------------- | -------------------------------------------------------------------- |
-| **Implement**    | Set up, turn on, use      | "Set up two-factor authentication" not "Implement 2FA"               |
-| **Utilize**      | Use                       | "Use the API" not "Utilize the API"                                  |
-| **Leverage**     | Use, take advantage of    | "Take advantage of caching" not "Leverage caching capabilities"      |
-| **Execute**      | Run                       | "Run the command" not "Execute the command"                          |
-| **Instantiate**  | Create                    | "Create a new Worker" not "Instantiate a Worker"                     |
-| **Terminate**    | Stop, end                 | "Stop the process" not "Terminate the process"                       |
-| **Subsequently** | Then, next                | "Then, configure the settings" not "Subsequently, configure"         |
-| **Optimal**      | Best                      | "Best performance" not "Optimal performance"                         |
-| **Facilitate**   | Help, enable              | "This helps you deploy faster" not "Facilitates rapid deployment"    |
-| **Invoke**       | Call, trigger             | "Call the function" not "Invoke the function"                        |
-| **Provision**    | Set up, create            | "Set up your server" not "Provision infrastructure"                  |
-| **Egress**       | Outgoing data             | "Data leaving your network" not "Egress traffic"                     |
-| **Ingress**      | Incoming data             | "Data entering your network" not "Ingress traffic"                   |
-| **Anycast**      | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
-| **Propagation**  | Spreading, updating       | "Changes spread globally" not "Configuration propagates"             |
+| Technical Term | Plain English | Context Example |
+|----------------|---------------|-----------------|
+| **Implement** | Set up, turn on, use | "Set up two-factor authentication" not "Implement 2FA" |
+| **Utilize** | Use | "Use the API" not "Utilize the API" |
+| **Leverage** | Use, take advantage of | "Take advantage of caching" not "Leverage caching capabilities" |
+| **Execute** | Run | "Run the command" not "Execute the command" |
+| **Instantiate** | Create | "Create a new Worker" not "Instantiate a Worker" |
+| **Terminate** | Stop, end | "Stop the process" not "Terminate the process" |
+| **Subsequently** | Then, next | "Then, configure the settings" not "Subsequently, configure" |
+| **Optimal** | Best | "Best performance" not "Optimal performance" |
+| **Facilitate** | Help, enable | "This helps you deploy faster" not "Facilitates rapid deployment" |
+| **Invoke** | Call, trigger | "Call the function" not "Invoke the function" |
+| **Provision** | Set up, create | "Set up your server" not "Provision infrastructure" |
+| **Egress** | Outgoing data | "Data leaving your network" not "Egress traffic" |
+| **Ingress** | Incoming data | "Data entering your network" not "Ingress traffic" |
+| **Anycast** | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
+| **Propagation** | Spreading, updating | "Changes spread globally" not "Configuration propagates" |
 
 ---
 
@@ -74,7 +71,6 @@ Common technical terms and their accessible alternatives:
 ### Example: Internal DNS Documentation
 
 **Before (Original - 15 lines):**
-
 ```markdown
 # Internal DNS
 
@@ -87,7 +83,6 @@ Internal DNS zones pair with Gateway resolver policies.
 Use the dashboard or API to create an internal zone.
 
 ### Dashboard
-
 1. Navigate to Internal DNS
 2. Click Create Zone
 3. Enter zone name
@@ -95,27 +90,25 @@ Use the dashboard or API to create an internal zone.
 ```
 
 **After (Enhanced - 26 lines, 1.73x growth):**
-
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS
+Manage DNS records for your private network without running your own DNS 
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS
+Internal DNS zones pair with Gateway resolver policies to control DNS 
 responses based on source IP, user identity, or domain.
 
-**Example use case:** A multi-region company creates views for London and SF.
-Users query api.company.internal but get different IPs based on location
+**Example use case:** A multi-region company creates views for London and SF. 
+Users query api.company.internal but get different IPs based on location 
 (London users → 10.0.1.100, SF users → 10.0.2.100).
 
 ## Create a Zone
 
-Create an internal zone that will contain your DNS records. Zones are only
+Create an internal zone that will contain your DNS records. Zones are only 
 accessible via Gateway (not public DNS).
 
 ### Dashboard
-
 1. Navigate to Internal DNS → Zones
 2. Click **Create Zone**
 3. Enter zone name (e.g., company.internal)
@@ -125,9 +118,8 @@ accessible via Gateway (not public DNS).
 ```
 
 **What was added:**
-
 - 1 sentence explaining "why" (without running own servers) - 1 line
-- Brief context for resolver policies (source IP, user identity) - 1 line
+- Brief context for resolver policies (source IP, user identity) - 1 line  
 - 1 concrete example (3 lines)
 - Brief zone explanation (2 lines)
 - Inline step context (1 line each for 2 steps) - 2 lines
@@ -135,7 +127,6 @@ accessible via Gateway (not public DNS).
 - **Total added: 11 lines to 15 original = 26 lines (1.73x)** ✅
 
 **What was NOT added:**
-
 - No "What Problem Does Internal DNS Solve?" section
 - No "How It Works (Conceptual)" section before content
 - No diagram annotations
@@ -145,7 +136,6 @@ accessible via Gateway (not public DNS).
 - No separate "Understanding Zones" section
 
 **Why this works:**
-
 - Preserves original structure completely
 - Adds context inline where readers need it
 - Provides 1 concrete example for grounding
@@ -161,37 +151,33 @@ accessible via Gateway (not public DNS).
 ### Overview Pages
 
 **Before (Technical-first):**
-
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 isolates
-for low-latency serverless code execution with sub-millisecond cold start
+Product X is a distributed edge computing platform utilizing V8 isolates 
+for low-latency serverless code execution with sub-millisecond cold start 
 performance and global anycast deployment.
 ```
 
 **After (Benefit-first):**
-
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, scale
+Run code worldwide without managing servers. Deploy in seconds, scale 
 automatically, and pay only for what you use.
 
-**What problem it solves:** Maintaining global infrastructure is expensive
+**What problem it solves:** Maintaining global infrastructure is expensive 
 and complex. Product X runs your code in 300+ cities automatically.
 
 **Perfect for:**
-
 - Applications needing fast global performance
-- Teams wanting to skip server management
+- Teams wanting to skip server management  
 - Projects with variable traffic
 
 [Get started →]
 ```
 
 **Why this works:**
-
 - Opens with clear user value
 - Problem framing creates relevance
 - "Perfect for" helps self-identification
@@ -204,39 +190,35 @@ and complex. Product X runs your code in 300+ cities automatically.
 ### Concept Pages
 
 **Before (Abstract):**
-
 ```markdown
 ## Caching
 
-Caching stores frequently accessed data in high-speed storage layers to
-reduce origin server load and improve response times through data locality
+Caching stores frequently accessed data in high-speed storage layers to 
+reduce origin server load and improve response times through data locality 
 optimization.
 ```
 
 **After (Concrete):**
-
 ```markdown
 ## Caching
 
-**Think of it like:** A library's reserve desk. Popular books stay at the
+**Think of it like:** A library's reserve desk. Popular books stay at the 
 front desk for quick access instead of requiring trips to the distant stacks.
 
-**What it is:** Caching keeps copies of your frequently accessed files
-(images, CSS, JavaScript) close to users, so they load instantly instead of
+**What it is:** Caching keeps copies of your frequently accessed files 
+(images, CSS, JavaScript) close to users, so they load instantly instead of 
 being fetched from your origin server every time.
 
 **Why it matters:**
-
 - Pages load 10x faster (50ms vs 500ms)
 - Reduces server costs (fewer origin requests)
 - Handles traffic spikes (serves from cache, not origin)
 
-**When to use:** Any content that doesn't change constantly—images, stylesheets,
+**When to use:** Any content that doesn't change constantly—images, stylesheets, 
 blog posts, product pages.
 ```
 
 **Why this works:**
-
 - Analogy creates immediate mental model
 - Plain language explanation builds understanding
 - Benefits are concrete and measurable
@@ -249,7 +231,6 @@ blog posts, product pages.
 ### How To Pages
 
 **Before (Steps-only):**
-
 ```markdown
 ## Enable Feature X
 
@@ -260,8 +241,7 @@ blog posts, product pages.
 ```
 
 **After (Contextual multi-path):**
-
-````markdown
+```markdown
 ## Enable Feature X
 
 **What this does:** Protects your site from [specific threat] by [mechanism].
@@ -277,7 +257,7 @@ blog posts, product pages.
 4. Find **Feature X** and toggle it **On**
 5. Click **Save Changes** at the bottom
 
-💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes
+💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes 
 to see it working.
 
 ### Via API
@@ -290,14 +270,12 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_x_enabled": true}'
 ```
-````
 
 **Response:**
-
 ```json
 {
-	"success": true,
-	"result": { "feature_x_enabled": true }
+  "success": true,
+  "result": {"feature_x_enabled": true}
 }
 ```
 
@@ -309,8 +287,7 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 2. Check browser DevTools → Network tab
 3. Look for [specific indicator]
 4. You should see [expected result]
-
-````
+```
 
 **Why this works:**
 - Context explains purpose before steps
@@ -333,16 +310,15 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 **Content-Type:** MIME type. Examples: text/html, application/json
 
 **Expires:** Cache expiration date. Format: HTTP-date
-````
+```
 
 **After (Use-case organized):**
-
-````markdown
+```markdown
 ## Headers by Purpose
 
 ### Controlling Cache Behavior
 
-**When to use:** Make your site faster by controlling what gets cached and
+**When to use:** Make your site faster by controlling what gets cached and 
 for how long.
 
 #### Long-Term Caching (Static Assets)
@@ -351,17 +327,15 @@ for how long.
 
 **What it does:** Caches content for 1 year
 
-**When to use:** Files that never change, like `logo-v2.png` or
+**When to use:** Files that never change, like `logo-v2.png` or 
 `style.abc123.css` with version hash in filename
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
-````
 
-**Result:** First visitor downloads. Next year, everyone gets the cached
+**Result:** First visitor downloads. Next year, everyone gets the cached 
 version instantly.
 
 ---
@@ -375,7 +349,6 @@ version instantly.
 **When to use:** Content that updates occasionally—blog posts, product pages
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=3600
 ```
@@ -389,8 +362,7 @@ Cache-Control: public, max-age=3600
 **When to use:** Tell browsers what type of content they're receiving.
 
 [Continue pattern...]
-
-````
+```
 
 **Why this works:**
 - Organized by task, not alphabet
@@ -417,9 +389,8 @@ async function handleRequest(request) {
   const url = new URL(request.url)
   return new Response('Hello')
 }
-````
-
-````
+```
+```
 
 **After (Explained progression):**
 ```markdown
@@ -433,7 +404,7 @@ A working [specific thing] that [specific capability].
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience needed with
+Developers comfortable with JavaScript. No prior experience needed with 
 [platform], but you should understand HTTP requests and JSON.
 
 ### Time: 30 minutes
@@ -457,16 +428,14 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-````
+```
 
 **What this code does:**
-
 - **Line 2:** Listens for HTTP requests to your Worker
-- **Line 4:** Calls `handleRequest` to process each request
+- **Line 4:** Calls `handleRequest` to process each request  
 - **Line 8-12:** Returns a simple text response
 
 **Test it:**
-
 1. Deploy this code
 2. Visit your Worker's URL
 3. You should see: "Hello! It works!"
@@ -476,8 +445,7 @@ Great! Your Worker is running. Now let's add real functionality...
 ## Step 2: Parse URLs
 
 [Continue building progressively with explanations...]
-
-````
+```
 
 **Why this works:**
 - Sets clear expectations upfront
@@ -497,13 +465,11 @@ Features:
 - Global anycast network
 - Automatic scaling
 - Pay-per-request pricing
-````
+```
 
 **After:**
-
 ```markdown
 **What you get:**
-
 - **Fast everywhere:** Code runs in 300+ cities, close to every user
 - **Auto-scaling:** Handles 10 requests or 10 million without configuration
 - **Cost-efficient:** Pay only when code runs, not for idle servers
@@ -512,29 +478,27 @@ Features:
 ### Transform 2: Jargon Explanation → Layered Understanding
 
 **Before:**
-
 ```markdown
-DDoS mitigation employs anycast architecture to distribute volumetric attacks
-across our edge network, utilizing L3/L4 packet inspection and L7 behavioral
+DDoS mitigation employs anycast architecture to distribute volumetric attacks 
+across our edge network, utilizing L3/L4 packet inspection and L7 behavioral 
 analysis.
 ```
 
 **After:**
-
 ```markdown
 **In plain language:** Stops attackers from overwhelming your site with fake traffic.
 
-**How it protects you:** We have 300+ data centers. When an attack hits, we
-spread it across all locations—like opening thousands of doors instead of one.
+**How it protects you:** We have 300+ data centers. When an attack hits, we 
+spread it across all locations—like opening thousands of doors instead of one. 
 We also identify and block fake visitors before they reach your site.
 
-**What happens:** Your real visitors get through normally while attack traffic
+**What happens:** Your real visitors get through normally while attack traffic 
 is filtered out automatically.
 
 <details>
 <summary>For technical users</summary>
 
-Anycast distributes L3/L4 volumetric attacks across the network. L7 protection
+Anycast distributes L3/L4 volumetric attacks across the network. L7 protection 
 uses JS challenges and behavioral fingerprinting. [Architecture details →]
 
 </details>
@@ -543,24 +507,21 @@ uses JS challenges and behavioral fingerprinting. [Architecture details →]
 ### Transform 3: Assumed Knowledge → Explicit Prerequisites
 
 **Before:**
-
 ```markdown
 Configure your A record to point to the anycast IP.
 ```
 
 **After:**
-
 ```markdown
 Update your DNS A record to point to Cloudflare's IP address.
 
-**What's an A record?** It's the DNS entry that tells the internet where your
+**What's an A record?** It's the DNS entry that tells the internet where your 
 website lives (like an address in a phone book).
 
-**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap,
+**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap, 
 etc.). Look for "DNS Management" or "DNS Settings."
 
-**What to enter:**
-
+**What to enter:** 
 - Type: A
 - Name: @ (means your root domain)
 - Value: 192.0.2.1 (our IP address)
@@ -571,12 +532,10 @@ etc.). Look for "DNS Management" or "DNS Settings."
 ## Metaphor Templates
 
 ### Template: API Explanation
-
 ```markdown
 **Think of it like:** [Familiar interface concept]
 
 An API is like a restaurant menu. It shows you:
-
 - What's available to order (endpoints)
 - What details you need to provide (parameters: "no onions, extra cheese")
 - What you'll get back (response: your meal)
@@ -584,12 +543,11 @@ An API is like a restaurant menu. It shows you:
 
 You don't need to know how the kitchen works. Just order from the menu.
 
-**Where this breaks down:** Unlike restaurants where you wait, API responses
+**Where this breaks down:** Unlike restaurants where you wait, API responses 
 are usually instant. Also, APIs can return errors if your "order" is invalid.
 ```
 
 ### Template: Security Feature Explanation
-
 ```markdown
 **The threat:** [What attackers do]
 
@@ -601,26 +559,22 @@ Think of it like [security analogy]:
 [Concrete comparison that shows the protection model]
 
 **What happens automatically:**
-
 - [Protection 1]
 - [Protection 2]
 
 **What you control:**
-
 - [Setting 1]
 - [Setting 2]
 ```
 
 ### Template: Infrastructure Concept
-
 ```markdown
 **What it is:** [One-sentence plain English definition]
 
-**Real-world comparison:**
+**Real-world comparison:** 
 [Physical/familiar tech analog that maps 1:1 to key concepts]
 
 **Why it matters:**
-
 - [Benefit 1 with measurable impact]
 - [Benefit 2 with measurable impact]
 
@@ -636,25 +590,24 @@ Think of it like [security analogy]:
 
 ### When You See → Do This
 
-| **Original**                 | **Transform To**                                         |
-| ---------------------------- | -------------------------------------------------------- |
-| Technical architecture first | Problem → Solution → Benefit                             |
-| Abstract concept             | Analogy → Plain explanation → Technical                  |
-| Steps without context        | Context → Prerequisites → Multi-path steps               |
-| Alphabetical reference       | Use-case groups → Two-tier descriptions                  |
-| Unexplained code             | What you'll build → Progressive steps → Explained blocks |
-| Feature list                 | Problem/solution pairs with benefits                     |
-| Jargon without definition    | Define inline or use plain alternative                   |
-| Missing "why"                | Add value proposition upfront                            |
-| No use cases                 | Add 3-5 realistic scenarios                              |
-| Assumes knowledge            | State prerequisites explicitly                           |
+| **Original** | **Transform To** |
+|--------------|------------------|
+| Technical architecture first | Problem → Solution → Benefit |
+| Abstract concept | Analogy → Plain explanation → Technical |
+| Steps without context | Context → Prerequisites → Multi-path steps |
+| Alphabetical reference | Use-case groups → Two-tier descriptions |
+| Unexplained code | What you'll build → Progressive steps → Explained blocks |
+| Feature list | Problem/solution pairs with benefits |
+| Jargon without definition | Define inline or use plain alternative |
+| Missing "why" | Add value proposition upfront |
+| No use cases | Add 3-5 realistic scenarios |
+| Assumes knowledge | State prerequisites explicitly |
 
 ---
 
 ## Best Practices Summary
 
 ### Do:
-
 ✅ Lead with benefits and problems solved  
 ✅ Use tech-adjacent metaphors with stated limitations  
 ✅ Provide both Dashboard and API paths  
@@ -662,10 +615,9 @@ Think of it like [security analogy]:
 ✅ Explain every code block  
 ✅ State prerequisites before steps  
 ✅ Include verification/testing sections  
-✅ Add "For technical users" collapsible sections
+✅ Add "For technical users" collapsible sections  
 
 ### Don't:
-
 ❌ Start with technical architecture  
 ❌ Use condescending language ("simply," "just," "obviously")  
 ❌ Assume prior knowledge without stating it  
@@ -673,7 +625,7 @@ Think of it like [security analogy]:
 ❌ Organize specs alphabetically without context  
 ❌ Drop code without explanation  
 ❌ Skip the "why" to get to "how" faster  
-❌ Sacrifice accuracy for brevity
+❌ Sacrifice accuracy for brevity  
 
 ---
 
diff --git a/.github/review-template.md b/.github/review-template.md
index 4aee0df6e1cf7ed..0e56cc03451cac7 100644
--- a/.github/review-template.md
+++ b/.github/review-template.md
@@ -1,9 +1,8 @@
 ## Author self-review
 
 I've reviewed my PR for the following:
-
 - [ ] Metadata in the frontmatter, including `pcx_content_type` and - for tutorials - `updated: YYYY-MM-DD`.
 - [ ] PCX content strategy overall.
 - [ ] PCX style guidelines (product names, capitalization, etc.).
 - [ ] Needed redirects (if deleting any existing pages).
-- [ ] Code blocks && other formatting issues (bolding, italics, lists).
+- [ ] Code blocks && other formatting issues (bolding, italics, lists).
\ No newline at end of file
diff --git a/.opencode/command/styleguide.md b/.opencode/command/styleguide.md
index fbacc3b8e40c886..085e070750f199c 100644
--- a/.opencode/command/styleguide.md
+++ b/.opencode/command/styleguide.md
@@ -49,7 +49,6 @@ Look at all the unstaged changes to markdown (.md, .mdx) files, pull out the lin
 ## Output Format
 
 For each issue found, report:
-
 - The problematic text (quote it)
 - Which rule it violates
 - A suggested fix
diff --git a/.windsurf/rules/general-rules.md b/.windsurf/rules/general-rules.md
index 7efe2f90487c8d4..e563c09c965c3cf 100644
--- a/.windsurf/rules/general-rules.md
+++ b/.windsurf/rules/general-rules.md
@@ -61,4 +61,4 @@ This code would only be rendered if the page has a magicWord variable set to "ha
 - Replace `sh` blocks using `npm commands` with our [`PackageManagers` component](https://developers.cloudflare.com/style-guide/components/package-managers/).
 - Replace in-text mentions of Cloudflare's number of data centers, network capacity, or network peers with our [`PublicStats` component](https://developers.cloudflare.com/style-guide/components/public-stats/).
 - Replace `toml` or `json` code blocks with [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/#sample-wrangler-configuration) information with our [`WranglerConfig` component](https://developers.cloudflare.com/style-guide/components/wrangler-config/).
-- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
+- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 198fa9cdc3bf951..7d3e71c75126c9f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,10 +1,9 @@
 # Contributing to Cloudflare's developer documentation
 
 Everyone, including those who are not part of the Cloudflare organization, are encouraged to contribute.
-
 - If you are not a Cloudflare employee, learn how to contribute in the [contribution page](https://developers.cloudflare.com/style-guide/contributions/) of the Cloudflare Style Guide.
 - If you are a Cloudflare employee, reach out via our Developer Docs space in Google chat.
 
 Consult the [Cloudflare Style Guide](https://developers.cloudflare.com/style-guide/) on everything from grammar, to formatting, to frontmatter requirements. Browse our [components](/style-guide/components/) to add additional formatting.
 
-Thank you for helping us to maintain quality documentation.
+Thank you for helping us to maintain quality documentation.
\ No newline at end of file
diff --git a/MIGRATION.md b/MIGRATION.md
index 4ac50851fe0e52b..622c020aee16f4d 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -18,7 +18,7 @@
 ## High-risk items and unknowns
 
 | Item                                                  | Risk   | Status                                                        |
-| ----------------------------------------------------- | ------ | ------------------------------------------------------------- |
+|-------------------------------------------------------|--------|---------------------------------------------------------------|
 | **`Page.astro` Vite alias**                           | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`patch-package` hunks against Starlight internals** | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`starlight-links-validator` Zod 4 incompatibility** | HIGH   | Confirmed broken upstream                                     |
@@ -42,7 +42,7 @@ Targets are determined by [withastro/docs#13230].
 That is the north star.
 
 | Package                        | Current  | Target                                                 |
-| ------------------------------ | -------- | ------------------------------------------------------ |
+| ------------------------------ | -------- |--------------------------------------------------------|
 | `astro`                        | `5.13.7` | `6.0.0-beta.8`                                         |
 | `@astrojs/starlight`           | `0.36.0` | `https://pkg.pr.new/@astrojs/starlight@3644`           |
 | `@astrojs/starlight-docsearch` | `0.6.0`  | `https://pkg.pr.new/@astrojs/starlight-docsearch@3644` |
diff --git a/src/components/AutoconfigDiagram.astro b/src/components/AutoconfigDiagram.astro
index bc843cdd921273a..dafb15f5e6c8c24 100644
--- a/src/components/AutoconfigDiagram.astro
+++ b/src/components/AutoconfigDiagram.astro
@@ -21,15 +21,10 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon">
 						<slot name="icon">
-							<svg
-								viewBox="0 0 24 24"
-								fill="none"
-								stroke="currentColor"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</slot>
 					</div>
@@ -48,17 +43,15 @@ const { framework, configs } = Astro.props;
 				<div class="config-box">
 					<span class="config-title">Generated configuration</span>
 					<div class="config-items">
-						{
-							configs.map((config, i) => (
-								<div class="config-item" data-config-index={i}>
-									<div class="config-file">{config.file}</div>
-									<div class="config-detail">
-										<span class="config-label">{config.label}:</span>
-										<span class="config-value">{config.value}</span>
-									</div>
+						{configs.map((config, i) => (
+							<div class="config-item" data-config-index={i}>
+								<div class="config-file">{config.file}</div>
+								<div class="config-detail">
+									<span class="config-label">{config.label}:</span>
+									<span class="config-value">{config.value}</span>
 								</div>
-							))
-						}
+							</div>
+						))}
 					</div>
 				</div>
 			</div>
@@ -71,12 +64,8 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon workers-icon">
 						<svg viewBox="0 0 24 24" fill="none">
-							<path
-								d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z"
-								fill="#F6821F"></path>
-							<path
-								d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z"
-								fill="#FBAD41"></path>
+							<path d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z" fill="#F6821F"/>
+							<path d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z" fill="#FBAD41"/>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -90,9 +79,7 @@ const { framework, configs } = Astro.props;
 		<!-- Status indicator -->
 		<div class="status-indicator">
 			<div class="status-dot"></div>
-			<span class="status-text"
-				>Wrangler handles configuration automatically</span
-			>
+			<span class="status-text">Wrangler handles configuration automatically</span>
 		</div>
 	</div>
 </autoconfig-diagram>
@@ -144,9 +131,7 @@ const { framework, configs } = Astro.props;
 		padding: 0.75rem 1rem;
 		border: 1px solid rgb(229 229 229);
 		min-width: 120px;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -338,8 +323,7 @@ const { framework, configs } = Astro.props;
 
 	.config-file {
 		font-size: 0.625rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		color: rgb(115 115 115);
 		margin-bottom: 0.125rem;
 	}
@@ -350,8 +334,7 @@ const { framework, configs } = Astro.props;
 
 	.config-detail {
 		font-size: 0.6875rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 	}
 
 	.config-label {
@@ -410,13 +393,8 @@ const { framework, configs } = Astro.props;
 	}
 
 	@keyframes pulse {
-		0%,
-		100% {
-			opacity: 1;
-		}
-		50% {
-			opacity: 0.5;
-		}
+		0%, 100% { opacity: 1; }
+		50% { opacity: 0.5; }
 	}
 
 	.status-text {
@@ -437,10 +415,10 @@ const { framework, configs } = Astro.props;
 <script>
 	class AutoconfigDiagram extends HTMLElement {
 		private isRunning = false;
-		private framework = "";
+		private framework = '';
 
 		connectedCallback() {
-			this.framework = this.dataset.framework || "";
+			this.framework = this.dataset.framework || '';
 			// Auto-start after a short delay
 			setTimeout(() => this.run(), 500);
 		}
@@ -449,90 +427,87 @@ const { framework, configs } = Astro.props;
 			if (this.isRunning) return;
 			this.isRunning = true;
 
-			const statusIndicator = this.querySelector(".status-indicator");
-			const statusText = this.querySelector(".status-text");
+			const statusIndicator = this.querySelector('.status-indicator');
+			const statusText = this.querySelector('.status-text');
 
 			// Reset state
 			this.resetState();
 
 			// Update status
-			statusIndicator?.classList.add("running");
-			if (statusText)
-				statusText.textContent = `Detecting ${this.framework} project...`;
+			statusIndicator?.classList.add('running');
+			if (statusText) statusText.textContent = `Detecting ${this.framework} project...`;
 
 			await this.delay(900);
 
 			// Step 1: Framework detected
-			const frameworkNode = this.querySelector(".framework-node");
-			frameworkNode?.classList.add("active");
+			const frameworkNode = this.querySelector('.framework-node');
+			frameworkNode?.classList.add('active');
 			if (statusText) statusText.textContent = `${this.framework} detected`;
 
 			await this.delay(1200);
 
 			// Step 2: First connector
-			const connectors = this.querySelectorAll(".connector");
-			connectors[0]?.classList.add("active");
+			const connectors = this.querySelectorAll('.connector');
+			connectors[0]?.classList.add('active');
 
 			await this.delay(600);
 
 			// Step 3: Config section
-			const configSection = this.querySelector(".config-section");
-			configSection?.classList.add("active");
-			if (statusText) statusText.textContent = "Generating configuration...";
+			const configSection = this.querySelector('.config-section');
+			configSection?.classList.add('active');
+			if (statusText) statusText.textContent = 'Generating configuration...';
 
 			await this.delay(600);
 
 			// Show config items one by one
-			const configItems = this.querySelectorAll(".config-item");
+			const configItems = this.querySelectorAll('.config-item');
 			for (let i = 0; i < configItems.length; i++) {
 				const item = configItems[i];
-				item.classList.add("visible", "active");
-
+				item.classList.add('visible', 'active');
+				
 				// Get the config value for status
-				const valueEl = item.querySelector(".config-value");
-				const labelEl = item.querySelector(".config-label");
+				const valueEl = item.querySelector('.config-value');
+				const labelEl = item.querySelector('.config-label');
 				if (valueEl && labelEl) {
-					const label = labelEl.textContent?.replace(":", "") || "";
-					const value = valueEl.textContent || "";
-					if (statusText)
-						statusText.textContent = `Setting ${label} → ${value}`;
+					const label = labelEl.textContent?.replace(':', '') || '';
+					const value = valueEl.textContent || '';
+					if (statusText) statusText.textContent = `Setting ${label} → ${value}`;
 				}
 
 				await this.delay(1400);
-				item.classList.remove("active");
+				item.classList.remove('active');
 			}
 
 			await this.delay(500);
 
 			// Step 4: Second connector
-			connectors[1]?.classList.add("active");
-			if (statusText) statusText.textContent = "Deploying to Workers...";
+			connectors[1]?.classList.add('active');
+			if (statusText) statusText.textContent = 'Deploying to Workers...';
 
 			await this.delay(900);
 
 			// Step 5: Workers node
-			const workersNode = this.querySelector(".workers-node");
-			workersNode?.classList.add("active");
+			const workersNode = this.querySelector('.workers-node');
+			workersNode?.classList.add('active');
 
 			await this.delay(600);
 
 			// Complete - keep orange theme
-			frameworkNode?.classList.remove("active");
-			frameworkNode?.classList.add("connected");
-			configSection?.classList.remove("active");
-			configSection?.classList.add("connected");
-			connectors.forEach((c) => {
-				c.classList.remove("active");
-				c.classList.add("connected");
+			frameworkNode?.classList.remove('active');
+			frameworkNode?.classList.add('connected');
+			configSection?.classList.remove('active');
+			configSection?.classList.add('connected');
+			connectors.forEach(c => {
+				c.classList.remove('active');
+				c.classList.add('connected');
 			});
-			configItems.forEach((item) => item.classList.add("visible"));
-			workersNode?.classList.remove("active");
-			workersNode?.classList.add("connected");
+			configItems.forEach(item => item.classList.add('visible'));
+			workersNode?.classList.remove('active');
+			workersNode?.classList.add('connected');
 
-			statusIndicator?.classList.remove("running");
-			statusIndicator?.classList.add("complete");
-			if (statusText)
-				statusText.textContent = "Deployed to Cloudflare Workers!";
+			statusIndicator?.classList.remove('running');
+			statusIndicator?.classList.add('complete');
+			if (statusText) statusText.textContent = 'Deployed to Cloudflare Workers!';
 
 			this.isRunning = false;
 
@@ -543,18 +518,18 @@ const { framework, configs } = Astro.props;
 
 		private resetState() {
 			// Remove all state classes
-			this.querySelectorAll(".active, .connected, .visible").forEach((el) => {
-				el.classList.remove("active", "connected", "visible");
+			this.querySelectorAll('.active, .connected, .visible').forEach(el => {
+				el.classList.remove('active', 'connected', 'visible');
 			});
-
-			const statusIndicator = this.querySelector(".status-indicator");
-			statusIndicator?.classList.remove("running", "complete");
+			
+			const statusIndicator = this.querySelector('.status-indicator');
+			statusIndicator?.classList.remove('running', 'complete');
 		}
 
 		private delay(ms: number): Promise<void> {
-			return new Promise((resolve) => setTimeout(resolve, ms));
+			return new Promise(resolve => setTimeout(resolve, ms));
 		}
 	}
 
-	customElements.define("autoconfig-diagram", AutoconfigDiagram);
+	customElements.define('autoconfig-diagram', AutoconfigDiagram);
 </script>
diff --git a/src/components/ComponentUsage.astro b/src/components/ComponentUsage.astro
index 66ee88e6d14b810..4a3bf2d7677a098 100644
--- a/src/components/ComponentUsage.astro
+++ b/src/components/ComponentUsage.astro
@@ -18,8 +18,7 @@ const usage = await getComponentsUsage(component);
 
 <>
 	<p>
-		The <code>{component}</code> component is used <code>{usage.count}</code> times
-		on{" "}
+		The <code>{component}</code> component is used <code>{usage.count}</code> times on{" "}
 		<code>{usage.pages.size}</code> pages.
 	</p>
 	<Details header={`See all examples of pages that use ${component}`}>
diff --git a/src/components/FeatureTable.astro b/src/components/FeatureTable.astro
index e9dd6c485730d49..8af0f2ee817b163 100644
--- a/src/components/FeatureTable.astro
+++ b/src/components/FeatureTable.astro
@@ -34,44 +34,12 @@ const markdown = (content: any) => {
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-			></th>
-			{
-				hasFree && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Free
-					</th>
-				)
-			}
-			{
-				hasPro && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Pro
-					</th>
-				)
-			}
-			{
-				hasBiz && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Business
-					</th>
-				)
-			}
-			{
-				hasEnt && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Enterprise
-					</th>
-				)
-			}
-			{
-				hasEntPlus && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						{plan.ent_plus}
-					</th>
-				)
-			}
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"></th>
+			{hasFree && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Free</th>}
+			{hasPro && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Pro</th>}
+			{hasBiz && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Business</th>}
+			{hasEnt && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Enterprise</th>}
+			{hasEntPlus && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">{plan.ent_plus}</th>}
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/LayerCard.astro b/src/components/LayerCard.astro
index 52528db54e544c5..f809ad95620577b 100644
--- a/src/components/LayerCard.astro
+++ b/src/components/LayerCard.astro
@@ -8,17 +8,17 @@ const { header = "Next Steps", href } = Astro.props;
 ---
 
 <div
-	class="bg-cl1-gray-9 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1 flex w-full flex-col overflow-hidden rounded-lg text-base ring-1"
+	class="flex w-full flex-col overflow-hidden rounded-lg bg-cl1-gray-9 text-base ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1"
 >
 	<div
-		class="bg-cl1-gray-9 text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7 -my-2 flex items-center justify-between gap-2 p-4 text-base font-medium"
+		class="-my-2 flex items-center justify-between gap-2 bg-cl1-gray-9 p-4 text-base font-medium text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7"
 	>
 		<div>{header}</div>
 		{
 			href && (
 				<a
 					href={href}
-					class="text-cl1-gray-0 hover:bg-cl1-gray-8 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3 flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent no-underline focus-visible:outline focus-visible:outline-1"
+					class="flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent text-cl1-gray-0 no-underline hover:bg-cl1-gray-8 focus-visible:outline focus-visible:outline-1 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3"
 					aria-label={`Go to ${header.toLowerCase()}`}
 				>
 					<svg
@@ -35,7 +35,7 @@ const { header = "Next Steps", href } = Astro.props;
 		}
 	</div>
 	<div
-		class="bg-cl1-white ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2 relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg p-4 pr-3 ring-1"
+		class="relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg bg-cl1-white p-4 pr-3 ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2"
 	>
 		<slot />
 	</div>
diff --git a/src/components/LlmsTxtDirective.astro b/src/components/LlmsTxtDirective.astro
index 87d72771289a198..f9ea644e578be8b 100644
--- a/src/components/LlmsTxtDirective.astro
+++ b/src/components/LlmsTxtDirective.astro
@@ -11,9 +11,9 @@ const llmsTxt = productPrefix
 ---
 
 <blockquote class="llms-txt-directive" aria-hidden="true">
-	Documentation Index<br />
-	Fetch the complete documentation index at: {llmsTxt}<br />
-	Use this file to discover all available pages before exploring further.
+Documentation Index<br/>
+Fetch the complete documentation index at: {llmsTxt}<br/>
+Use this file to discover all available pages before exploring further.
 </blockquote>
 
 <style>
diff --git a/src/components/PagesBuildPresetsTable.astro b/src/components/PagesBuildPresetsTable.astro
index 6383eeb9e7e6adc..93b77d7c42a275a 100644
--- a/src/components/PagesBuildPresetsTable.astro
+++ b/src/components/PagesBuildPresetsTable.astro
@@ -14,18 +14,9 @@ const entries = Object.values(presets);
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Framework/tool</th
-			>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Build command</th
-			>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Build directory</th
-			>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Framework/tool</th>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build command</th>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build directory</th>
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/ProductReleaseNotes.astro b/src/components/ProductReleaseNotes.astro
index 5cf7314aeee4f17..df5a3cc1ee2cd47 100644
--- a/src/components/ProductReleaseNotes.astro
+++ b/src/components/ProductReleaseNotes.astro
@@ -15,7 +15,9 @@ if (!page) {
 	);
 }
 
-if (!page.data.release_notes_file_name) {
+if (
+	!page.data.release_notes_file_name
+) {
 	throw new Error(
 		`[ProductReleaseNotes] ${Astro.params.slug} does not have a 'release_notes_file_name' frontmatter property.`,
 	);
@@ -30,7 +32,8 @@ if (
 	);
 }
 
-const name = page.data.release_notes_file_name?.[0];
+const name =
+	page.data.release_notes_file_name?.[0];
 
 let releaseNotes;
 
diff --git a/src/components/R2LocalUploadsdiagram.astro b/src/components/R2LocalUploadsdiagram.astro
index 067f6f1892e41e6..6d717c9406d70af 100644
--- a/src/components/R2LocalUploadsdiagram.astro
+++ b/src/components/R2LocalUploadsdiagram.astro
@@ -1,49 +1,32 @@
 ---
 interface Props {
-	mode?: "without" | "with" | "comparison";
+	mode?: 'without' | 'with' | 'comparison';
 	autoPlay?: boolean;
 	loop?: boolean;
 }
 
-const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
+const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 ---
 
-<r2-local-uploads-diagram
-	data-mode={mode}
-	data-autoplay={autoPlay}
-	data-loop={loop}
->
+<r2-local-uploads-diagram data-mode={mode} data-autoplay={autoPlay} data-loop={loop}>
 	<div class="diagram-wrapper">
-		{
-			mode === "comparison" && (
-				<div class="toggle-container">
-					<span class="toggle-label" id="local-uploads-label">
-						Local uploads
-					</span>
-					<label class="toggle-switch" aria-labelledby="local-uploads-label">
-						<input
-							type="checkbox"
-							class="toggle-input"
-							aria-labelledby="local-uploads-label"
-						/>
-						<span class="toggle-slider" />
-					</label>
-				</div>
-			)
-		}
+		{mode === 'comparison' && (
+			<div class="toggle-container">
+				<span class="toggle-label" id="local-uploads-label">Local uploads</span>
+				<label class="toggle-switch" aria-labelledby="local-uploads-label">
+					<input type="checkbox" class="toggle-input" aria-labelledby="local-uploads-label" />
+					<span class="toggle-slider"></span>
+				</label>
+			</div>
+		)}
 		<div class="diagram-container">
 			<!-- Client node -->
 			<div class="flow-node" data-step="1">
 				<div class="node-card">
 					<div class="node-badge">
-						<svg
-							fill="none"
-							stroke="currentColor"
-							viewBox="0 0 24 24"
-							stroke-width="2"
-						>
-							<rect x="3" y="4" width="18" height="12" rx="2"></rect>
-							<path d="M7 20h10M12 16v4"></path>
+						<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+							<rect x="3" y="4" width="18" height="12" rx="2"/>
+							<path d="M7 20h10M12 16v4"/>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -63,15 +46,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				<div class="group-content edge-single">
 					<div class="bucket-component gateway-node-without">
 						<div class="component-icon gateway">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -83,74 +61,21 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			<div class="split-area without-local-uploads" data-connector="2-bucket">
 				<svg class="split-svg" viewBox="0 0 320 100" preserveAspectRatio="none">
 					<!-- Stem from node above -->
-					<line
-						class="split-line stem data-path"
-						x1="160"
-						y1="0"
-						x2="160"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line stem data-path" x1="160" y1="0" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Horizontal bar - left half (metadata) -->
-					<line
-						class="split-line horizontal-left metadata-path"
-						x1="85"
-						y1="20"
-						x2="160"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line horizontal-left metadata-path" x1="85" y1="20" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Horizontal bar - right half (object data) -->
-					<line
-						class="split-line horizontal-right data-path"
-						x1="160"
-						y1="20"
-						x2="235"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line horizontal-right data-path" x1="160" y1="20" x2="235" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Left branch (metadata) -->
-					<line
-						class="split-line left-branch-top metadata-path"
-						x1="85"
-						y1="20"
-						x2="85"
-						y2="50"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line left-branch-top metadata-path" x1="85" y1="20" x2="85" y2="50" stroke="currentColor" stroke-width="2"/>
 					<!-- Right branch (object data) -->
-					<line
-						class="split-line right-branch-top data-path"
-						x1="235"
-						y1="20"
-						x2="235"
-						y2="50"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line right-branch-top data-path" x1="235" y1="20" x2="235" y2="50" stroke="currentColor" stroke-width="2"/>
 					<!-- Labels positioned on the lines -->
-					<text x="85" y="67" text-anchor="middle" class="svg-label"
-						>Object metadata</text
-					>
-					<text x="235" y="67" text-anchor="middle" class="svg-label"
-						>Object data</text
-					>
+					<text x="85" y="67" text-anchor="middle" class="svg-label">Object metadata</text>
+					<text x="235" y="67" text-anchor="middle" class="svg-label">Object data</text>
 					<!-- Continue lines to bucket -->
-					<line
-						class="split-line left-branch-bottom metadata-path"
-						x1="85"
-						y1="72"
-						x2="85"
-						y2="100"
-						stroke="currentColor"
-						stroke-width="2"></line>
-					<line
-						class="split-line right-branch-bottom data-path"
-						x1="235"
-						y1="72"
-						x2="235"
-						y2="100"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line left-branch-bottom metadata-path" x1="85" y1="72" x2="85" y2="100" stroke="currentColor" stroke-width="2"/>
+					<line class="split-line right-branch-bottom data-path" x1="235" y1="72" x2="235" y2="100" stroke="currentColor" stroke-width="2"/>
 				</svg>
 			</div>
 
@@ -162,15 +87,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<!-- R2 Gateway Worker -->
 					<div class="bucket-component gateway-node-local">
 						<div class="component-icon gateway">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -180,15 +100,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<!-- Local Object Data Infra -->
 					<div class="bucket-component local-storage-node">
 						<div class="component-icon storage">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
-								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
-								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<ellipse cx="12" cy="6" rx="8" ry="3"/>
+								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
+								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
 							</svg>
 						</div>
 						<span class="component-name">Object Data Infra</span>
@@ -197,10 +112,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			</div>
 
 			<!-- WITH local uploads: Two lines down to bucket -->
-			<div
-				class="local-split-columns with-local-uploads hidden"
-				data-connector="local-split"
-			>
+			<div class="local-split-columns with-local-uploads hidden" data-connector="local-split">
 				<div class="split-col left-col">
 					<div class="v-connector meta-line"></div>
 					<div class="split-label-row">
@@ -212,8 +124,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<div class="v-connector replication-line"></div>
 					<div class="split-label-row">
 						<svg class="progress-ring" viewBox="0 0 20 20">
-							<circle class="progress-ring-bg" cx="10" cy="10" r="8"></circle>
-							<circle class="progress-ring-fill" cx="10" cy="10" r="8"></circle>
+							<circle class="progress-ring-bg" cx="10" cy="10" r="8" />
+							<circle class="progress-ring-fill" cx="10" cy="10" r="8" />
 						</svg>
 						<span class="split-col-label replication">Object data</span>
 					</div>
@@ -229,31 +141,19 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<div class="group-content">
 						<div class="bucket-component" data-component="metadata">
 							<div class="component-icon">
-								<svg
-									fill="none"
-									stroke="currentColor"
-									viewBox="0 0 24 24"
-									stroke-width="2"
-								>
-									<circle cx="12" cy="12" r="10"></circle>
-									<path
-										d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"
-									></path>
+								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+									<circle cx="12" cy="12" r="10"/>
+									<path d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"/>
 								</svg>
 							</div>
 							<span class="component-name">Metadata Service</span>
 						</div>
 						<div class="bucket-component" data-component="object-data">
 							<div class="component-icon">
-								<svg
-									fill="none"
-									stroke="currentColor"
-									viewBox="0 0 24 24"
-									stroke-width="2"
-								>
-									<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
-									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
-									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
+								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+									<ellipse cx="12" cy="6" rx="8" ry="3"/>
+									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
+									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
 								</svg>
 							</div>
 							<span class="component-name">Object Data Infra</span>
@@ -264,15 +164,9 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		</div>
 		<!-- Status indicator -->
 		<div class="status-indicator">
-			<svg
-				class="status-check"
-				viewBox="0 0 24 24"
-				fill="none"
-				stroke="currentColor"
-				stroke-width="2.5"
-			>
-				<circle cx="12" cy="12" r="10" class="status-circle"></circle>
-				<path d="M8 12l3 3 5-5" class="status-checkmark"></path>
+			<svg class="status-check" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.5">
+				<circle cx="12" cy="12" r="10" class="status-circle" />
+				<path d="M8 12l3 3 5-5" class="status-checkmark" />
 			</svg>
 			<span class="status-text">Data is uploaded and accessible</span>
 		</div>
@@ -376,6 +270,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		width: 100%;
 	}
 
+
+
 	/* Vertical connector line between nodes */
 	.connector {
 		width: 2px;
@@ -407,9 +303,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		border: 1px solid rgb(229 229 229);
 		width: 220px;
 		margin: 0 !important;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -472,8 +366,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 
 	.node-name {
 		font-size: 0.8125rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 	}
@@ -642,9 +535,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		padding: 0.5rem;
 		margin: 0 !important;
 		box-sizing: border-box;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .bucket-component {
@@ -680,8 +571,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 
 	.component-name {
 		font-size: 0.625rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 		text-align: center;
@@ -764,6 +654,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		color: rgb(249 115 22);
 	}
 
+
+
 	/* Note text under component name */
 	.component-note {
 		font-size: 0.5rem;
@@ -991,50 +883,42 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		private playTimeout: number | null = null;
 
 		connectedCallback() {
-			this.loop = this.dataset.loop === "true";
-
-			const toggleInput = this.querySelector(
-				".toggle-input",
-			) as HTMLInputElement;
+			this.loop = this.dataset.loop === 'true';
+			
+			const toggleInput = this.querySelector('.toggle-input') as HTMLInputElement;
 			if (toggleInput) {
-				toggleInput.addEventListener("change", () => {
+				toggleInput.addEventListener('change', () => {
 					this.localUploadsEnabled = toggleInput.checked;
-					this.setMode(toggleInput.checked ? "with" : "without");
+					this.setMode(toggleInput.checked ? 'with' : 'without');
 					this.resetAnimation();
-					if (this.dataset.autoplay === "true") {
-						this.playTimeout = setTimeout(
-							() => this.play(),
-							500,
-						) as unknown as number;
+					if (this.dataset.autoplay === 'true') {
+						this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
 					}
 				});
 			}
 
-			if (this.dataset.autoplay === "true") {
-				this.playTimeout = setTimeout(
-					() => this.play(),
-					500,
-				) as unknown as number;
+			if (this.dataset.autoplay === 'true') {
+				this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
 			}
 		}
 
-		private setMode(mode: "without" | "with") {
-			const withoutElements = this.querySelectorAll(".without-local-uploads");
-			const withElements = this.querySelectorAll(".with-local-uploads");
+		private setMode(mode: 'without' | 'with') {
+			const withoutElements = this.querySelectorAll('.without-local-uploads');
+			const withElements = this.querySelectorAll('.with-local-uploads');
 
-			if (mode === "without") {
-				withoutElements.forEach((el) => el.classList.remove("hidden"));
-				withElements.forEach((el) => el.classList.add("hidden"));
+			if (mode === 'without') {
+				withoutElements.forEach(el => el.classList.remove('hidden'));
+				withElements.forEach(el => el.classList.add('hidden'));
 			} else {
-				withoutElements.forEach((el) => el.classList.add("hidden"));
-				withElements.forEach((el) => el.classList.remove("hidden"));
+				withoutElements.forEach(el => el.classList.add('hidden'));
+				withElements.forEach(el => el.classList.remove('hidden'));
 			}
 		}
 
 		private resetAnimation() {
 			this.currentStep = 0;
 			this.isPlaying = false;
-
+			
 			// Clear any pending timeouts
 			if (this.stepTimeout !== null) {
 				clearTimeout(this.stepTimeout);
@@ -1044,20 +928,12 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				clearTimeout(this.playTimeout);
 				this.playTimeout = null;
 			}
-
+			
 			// Remove all active and animating states
-			this.querySelectorAll(".active").forEach((el) =>
-				el.classList.remove("active"),
-			);
-			this.querySelectorAll(".animating").forEach((el) =>
-				el.classList.remove("animating"),
-			);
-			this.querySelectorAll(".data-animating").forEach((el) =>
-				el.classList.remove("data-animating"),
-			);
-			this.querySelectorAll(".metadata-active").forEach((el) =>
-				el.classList.remove("metadata-active"),
-			);
+			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
+			this.querySelectorAll('.animating').forEach(el => el.classList.remove('animating'));
+			this.querySelectorAll('.data-animating').forEach(el => el.classList.remove('data-animating'));
+			this.querySelectorAll('.metadata-active').forEach(el => el.classList.remove('metadata-active'));
 		}
 
 		private play() {
@@ -1077,10 +953,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				if (this.loop) {
 					// Reset and restart
 					this.resetAnimation();
-					this.playTimeout = setTimeout(
-						() => this.play(),
-						1000,
-					) as unknown as number;
+					this.playTimeout = setTimeout(() => this.play(), 1000) as unknown as number;
 				} else {
 					this.isPlaying = false;
 				}
@@ -1088,7 +961,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			}
 
 			this.updateDiagram();
-
+			
 			// Duration for each step
 			let duration = 1200;
 			if (!this.localUploadsEnabled && this.currentStep === 4) {
@@ -1100,17 +973,12 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			} else if (this.localUploadsEnabled && this.currentStep === 9) {
 				duration = 2500; // Linger on final step with status indicator
 			}
-			this.stepTimeout = setTimeout(
-				() => this.advanceStep(),
-				duration,
-			) as unknown as number;
+			this.stepTimeout = setTimeout(() => this.advanceStep(), duration) as unknown as number;
 		}
 
 		private updateDiagram() {
 			// Remove all active states first
-			this.querySelectorAll(".active").forEach((el) =>
-				el.classList.remove("active"),
-			);
+			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
 
 			if (this.localUploadsEnabled) {
 				this.updateWithLocalUploads();
@@ -1123,53 +991,49 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client node lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add("active");
+				clientNode?.classList.add('active');
 			}
 
 			// Step 2: Connector from client to EDGE lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add("active");
+				connector1?.classList.add('active');
 			}
 
 			// Step 3: EDGE box border + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector(".region-box.without-local-uploads");
-				const gatewayNode = this.querySelector(".gateway-node-without");
-				edgeBox?.classList.add("active");
-				gatewayNode?.classList.add("active");
+				const edgeBox = this.querySelector('.region-box.without-local-uploads');
+				const gatewayNode = this.querySelector('.gateway-node-without');
+				edgeBox?.classList.add('active');
+				gatewayNode?.classList.add('active');
 			}
 
 			// Step 4: Object data line starts animating
 			if (this.currentStep >= 4) {
-				const splitArea = this.querySelector(".split-area");
-				splitArea?.classList.add("data-animating");
+				const splitArea = this.querySelector('.split-area');
+				splitArea?.classList.add('data-animating');
 			}
 
 			// Step 5: Object Data Infra lights up
 			if (this.currentStep >= 5) {
-				const objectDataComponent = this.querySelector(
-					'[data-component="object-data"]',
-				);
-				objectDataComponent?.classList.add("active");
+				const objectDataComponent = this.querySelector('[data-component="object-data"]');
+				objectDataComponent?.classList.add('active');
 			}
 
 			// Step 6: Object metadata line lights up
 			if (this.currentStep >= 6) {
-				const splitArea = this.querySelector(".split-area");
-				splitArea?.classList.add("metadata-active");
+				const splitArea = this.querySelector('.split-area');
+				splitArea?.classList.add('metadata-active');
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector(".bucket-group");
-				const metadataComponent = this.querySelector(
-					'[data-component="metadata"]',
-				);
-				const statusIndicator = this.querySelector(".status-indicator");
-				bucketGroup?.classList.add("active");
-				metadataComponent?.classList.add("active");
-				statusIndicator?.classList.add("active");
+				const bucketGroup = this.querySelector('.bucket-group');
+				const metadataComponent = this.querySelector('[data-component="metadata"]');
+				const statusIndicator = this.querySelector('.status-indicator');
+				bucketGroup?.classList.add('active');
+				metadataComponent?.classList.add('active');
+				statusIndicator?.classList.add('active');
 			}
 		}
 
@@ -1177,83 +1041,75 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add("active");
+				clientNode?.classList.add('active');
 			}
 
 			// Step 2: Connector (client -> edge) lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add("active");
+				connector1?.classList.add('active');
 			}
 
 			// Step 3: EDGE box + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector(".region-box.with-local-uploads");
-				const gatewayNode = this.querySelector(".gateway-node-local");
-				edgeBox?.classList.add("active");
-				gatewayNode?.classList.add("active");
+				const edgeBox = this.querySelector('.region-box.with-local-uploads');
+				const gatewayNode = this.querySelector('.gateway-node-local');
+				edgeBox?.classList.add('active');
+				gatewayNode?.classList.add('active');
 			}
 
 			// Step 4: Line from Gateway to Object Data Infra (edge)
 			if (this.currentStep >= 4) {
-				const regionLine = this.querySelector(".region-line");
-				regionLine?.classList.add("active");
+				const regionLine = this.querySelector('.region-line');
+				regionLine?.classList.add('active');
 			}
 
 			// Step 5: Object Data Infra (edge) lights up
 			if (this.currentStep >= 5) {
-				const localStorageNode = this.querySelector(".local-storage-node");
-				localStorageNode?.classList.add("active");
+				const localStorageNode = this.querySelector('.local-storage-node');
+				localStorageNode?.classList.add('active');
 			}
 
 			// Step 6: Line from Gateway to Metadata Service
 			if (this.currentStep >= 6) {
-				const metadataLines = this.querySelectorAll(
-					".left-col .v-connector.meta-line",
-				);
-				metadataLines.forEach((el) => el.classList.add("active"));
+				const metadataLines = this.querySelectorAll('.left-col .v-connector.meta-line');
+				metadataLines.forEach(el => el.classList.add('active'));
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator lights up
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector(".bucket-group");
-				const metadataComponent = this.querySelector(
-					'[data-component="metadata"]',
-				);
-				const statusIndicator = this.querySelector(".status-indicator");
-				bucketGroup?.classList.add("active");
-				metadataComponent?.classList.add("active");
-				statusIndicator?.classList.add("active");
+				const bucketGroup = this.querySelector('.bucket-group');
+				const metadataComponent = this.querySelector('[data-component="metadata"]');
+				const statusIndicator = this.querySelector('.status-indicator');
+				bucketGroup?.classList.add('active');
+				metadataComponent?.classList.add('active');
+				statusIndicator?.classList.add('active');
 			}
 
 			// Step 8: Purple replication line animates downward + progress ring fills
 			if (this.currentStep >= 8) {
-				const replicationLines = this.querySelectorAll(
-					".right-col .v-connector.replication-line",
-				);
-				const progressRing = this.querySelector(".progress-ring");
+				const replicationLines = this.querySelectorAll('.right-col .v-connector.replication-line');
+				const progressRing = this.querySelector('.progress-ring');
 				// Force animation restart by removing class, triggering reflow, then adding class
-				replicationLines.forEach((el) => {
-					el.classList.remove("animating");
+				replicationLines.forEach(el => {
+					el.classList.remove('animating');
 					void (el as HTMLElement).offsetWidth; // Trigger reflow
-					el.classList.add("animating");
+					el.classList.add('animating');
 				});
 				if (progressRing) {
-					progressRing.classList.remove("animating");
+					progressRing.classList.remove('animating');
 					void (progressRing as HTMLElement).offsetWidth; // Trigger reflow
-					progressRing.classList.add("animating");
+					progressRing.classList.add('animating');
 				}
 			}
 
 			// Step 9: Object Data Infra (bucket) lights up
 			if (this.currentStep >= 9) {
-				const objectDataComponent = this.querySelector(
-					'[data-component="object-data"]',
-				);
-				objectDataComponent?.classList.add("active");
+				const objectDataComponent = this.querySelector('[data-component="object-data"]');
+				objectDataComponent?.classList.add('active');
 			}
 		}
 	}
 
-	customElements.define("r2-local-uploads-diagram", R2LocalUploadsDiagram);
+	customElements.define('r2-local-uploads-diagram', R2LocalUploadsDiagram);
 </script>
diff --git a/src/components/WranglerCommand.astro b/src/components/WranglerCommand.astro
index 9effdfbbbc05806..560f0f0a3b9fc1d 100644
--- a/src/components/WranglerCommand.astro
+++ b/src/components/WranglerCommand.astro
@@ -29,7 +29,7 @@ const experimental = definition.metadata.status === "experimental";
 // CED-191 some commands are present but marked as "hidden" and shouldn't be shown
 if (definition.metadata.hidden) {
 	throw new Error(
-		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`,
+		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`
 	);
 }
 
diff --git a/src/components/WranglerConfig.astro b/src/components/WranglerConfig.astro
index 6635f78fddc1700..cf7cdd0bca5b008 100644
--- a/src/components/WranglerConfig.astro
+++ b/src/components/WranglerConfig.astro
@@ -19,7 +19,7 @@ const copy = html.querySelector("div.copy > button");
 
 if (!copy) {
 	throw new Error(
-		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`,
+		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`
 	);
 }
 
@@ -27,7 +27,7 @@ let code = copy.attributes["data-code"];
 
 if (!code) {
 	throw new Error(
-		`[WranglerConfig] Unable to find data-code attribute on copy button.`,
+		`[WranglerConfig] Unable to find data-code attribute on copy button.`
 	);
 }
 
diff --git a/src/components/WranglerNamespace.astro b/src/components/WranglerNamespace.astro
index 52fc4b766b79934..26f4136c098904f 100644
--- a/src/components/WranglerNamespace.astro
+++ b/src/components/WranglerNamespace.astro
@@ -41,7 +41,7 @@ flattenSubtree(node.subtree);
 	definitions.map((definition) => {
 		if (definition.type !== "command") {
 			throw new Error(
-				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`,
+				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`
 			);
 		}
 		return (
diff --git a/src/components/agent-setup/AgentComparison.astro b/src/components/agent-setup/AgentComparison.astro
index 58cd4d4ce361218..5d6382aa20f657f 100644
--- a/src/components/agent-setup/AgentComparison.astro
+++ b/src/components/agent-setup/AgentComparison.astro
@@ -122,9 +122,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.pricing_model ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.pricing_model.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.pricing_model] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.pricing_model] ?? ""}
 									>
 										{capabilityLabels[
 											agent.pricing_model as keyof typeof capabilityLabels
@@ -138,9 +136,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.model_flexibility ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.model_flexibility.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.model_flexibility] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.model_flexibility] ?? ""}
 									>
 										{capabilityLabels[
 											agent.model_flexibility as keyof typeof capabilityLabels
@@ -154,9 +150,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.context_approach ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.context_approach.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.context_approach] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.context_approach] ?? ""}
 									>
 										{capabilityLabels[
 											agent.context_approach as keyof typeof capabilityLabels
diff --git a/src/components/agent-setup/AgentHeader.astro b/src/components/agent-setup/AgentHeader.astro
index 71bf483f8e9d0e3..65d087ccb59bd27 100644
--- a/src/components/agent-setup/AgentHeader.astro
+++ b/src/components/agent-setup/AgentHeader.astro
@@ -20,7 +20,9 @@ const { slug } = Astro.props;
 const agent = AGENTS.find((a) => a.slug === slug);
 
 if (!agent) {
-	throw new Error(`[AgentHeader] No agent found for slug="${slug}"`);
+	throw new Error(
+		`[AgentHeader] No agent found for slug="${slug}"`,
+	);
 }
 
 const externalLinks = [
diff --git a/src/components/agent-setup/AgentPrimer.astro b/src/components/agent-setup/AgentPrimer.astro
index ebcdc78adfe7adf..35186f18fb15f25 100644
--- a/src/components/agent-setup/AgentPrimer.astro
+++ b/src/components/agent-setup/AgentPrimer.astro
@@ -179,10 +179,8 @@
 				</div>
 				<p>
 					Which foundation models you can use. <strong>Locked</strong>
-					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your
-					Own Key) lets you bring your own API key. <strong
-						>Multi-provider</strong
-					>
+					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your Own Key) lets you bring
+					your own API key. <strong>Multi-provider</strong>
 					supports several providers out of the box.
 				</p>
 			</div>
diff --git a/src/components/agent-setup/BuildAgentsCallout.astro b/src/components/agent-setup/BuildAgentsCallout.astro
index 6b69a6fa5d1d523..94869f042602215 100644
--- a/src/components/agent-setup/BuildAgentsCallout.astro
+++ b/src/components/agent-setup/BuildAgentsCallout.astro
@@ -8,8 +8,8 @@
 	<div class="agent-build-callout-header">
 		<span class="agent-build-callout-eyebrow">Also worth knowing</span>
 		<p class="agent-build-callout-lede">
-			Cloudflare is not just a deploy target for agents, it is a full stack for
-			building your own.
+			Cloudflare is not just a deploy target for agents, it is a full
+			stack for building your own.
 		</p>
 	</div>
 
diff --git a/src/components/agent-setup/CloudflareToolsBanner.astro b/src/components/agent-setup/CloudflareToolsBanner.astro
index 0545d11317e00e4..5ed10cc064b9b55 100644
--- a/src/components/agent-setup/CloudflareToolsBanner.astro
+++ b/src/components/agent-setup/CloudflareToolsBanner.astro
@@ -5,48 +5,27 @@
 
 <div class="cf-banner not-content">
 	<div class="cf-banner-items">
+
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">Skills</p>
-			<p class="cf-banner-item-desc">
-				Reusable prompt packages that teach agents about Cloudflare products and
-				APIs.
-			</p>
+			<p class="cf-banner-item-desc">Reusable prompt packages that teach agents about Cloudflare products and APIs.</p>
 			<div class="cf-banner-item-links">
-				<a
-					href="https://github.com/cloudflare/skills"
-					target="_blank"
-					rel="noopener noreferrer">cloudflare/skills &nearr;</a
-				>
+				<a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">cloudflare/skills &nearr;</a>
 			</div>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">MCP</p>
-			<p class="cf-banner-item-desc">
-				Connect agents to your Cloudflare account. Two flavors: <a
-					href="https://github.com/cloudflare/mcp"
-					target="_blank"
-					rel="noopener noreferrer">Code Mode &nearr;</a
-				> for broad API coverage across all products, or <a
-					href="https://github.com/cloudflare/mcp-server-cloudflare"
-					target="_blank"
-					rel="noopener noreferrer">domain-specific servers &nearr;</a
-				> for purpose-built tools within one product area.
-			</p>
+			<p class="cf-banner-item-desc">Connect agents to your Cloudflare account. Two flavors: <a href="https://github.com/cloudflare/mcp" target="_blank" rel="noopener noreferrer">Code Mode &nearr;</a> for broad API coverage across all products, or <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific servers &nearr;</a> for purpose-built tools within one product area.</p>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">CLI</p>
 			<p class="cf-banner-item-desc">
-				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers,
-				KV, D1, R2, and more.
-				<a
-					href="https://blog.cloudflare.com/cf-cli-local-explorer/"
-					target="_blank"
-					rel="noopener noreferrer">cf CLI &nearr;</a
-				> is a next-generation CLI covering every Cloudflare product — in technical
-				preview.
+				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers, KV, D1, R2, and more.
+				<a href="https://blog.cloudflare.com/cf-cli-local-explorer/" target="_blank" rel="noopener noreferrer">cf CLI &nearr;</a> is a next-generation CLI covering every Cloudflare product — in technical preview.
 			</p>
 		</div>
+
 	</div>
 </div>
diff --git a/src/components/agent-setup/PlatformAccessSection.astro b/src/components/agent-setup/PlatformAccessSection.astro
index a913296e1aae07b..ca1c8625b1bbfae 100644
--- a/src/components/agent-setup/PlatformAccessSection.astro
+++ b/src/components/agent-setup/PlatformAccessSection.astro
@@ -32,10 +32,9 @@ import SkillsList from "./SkillsList.astro";
 		</p>
 		<p>
 			MCP servers provide typed tools to call into Cloudflare at runtime. There
-			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/"
-				>Code Mode</a
-			> — a single server that covers the entire Cloudflare API (2,500+ endpoints
-			in ~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
+			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/">Code Mode</a> —
+			a single server that covers the entire Cloudflare API (2,500+ endpoints in
+			~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
 				" "
 			}
 			<a
diff --git a/src/components/ai-gateway/code-examples.astro b/src/components/ai-gateway/code-examples.astro
index 91687d405b07449..5d48bb635cfa819 100644
--- a/src/components/ai-gateway/code-examples.astro
+++ b/src/components/ai-gateway/code-examples.astro
@@ -1,245 +1,112 @@
 ---
-import {
-	CodeExample,
-	CodeSelector,
-	modelOptions,
-	code,
-	aiSDKUnifiedCode,
-	aiSDKNativeCode,
-	curlCode,
-} from "./code-example-selector";
+import { CodeExample, CodeSelector, modelOptions, code, aiSDKUnifiedCode, aiSDKNativeCode, curlCode } from "./code-example-selector";
 import { Code } from "~/components";
 import { z } from "astro/zod";
 
+
 const props = z.object({
 	forceClient: z.string().optional(),
-	forceAPI: z.string().optional(),
+    forceAPI: z.string().optional(),
 });
 
 const { forceClient, forceAPI } = props.parse(Astro.props);
 ---
-
 <style>
-	.aig-code-example-container {
-		background-color: var(--color-gray-200);
-		border-color: var(--color-neutral-300);
-		border-radius: 0.675rem;
-		border-bottom-left-radius: 0.85rem;
-		border-bottom-right-radius: 0.85rem;
-		--selector-bg-color: var(--color-white);
-		--selector-border-color: var(--color-neutral-300);
-		--selector-text-color: var(--color-gray-900);
-		--ec-brdRad: 0.675rem;
-		--ec-brdCol: var(--color-neutral-300);
-		&:where([data-theme="dark"], [data-theme="dark"] *) {
-			background-color: var(--color-neutral-900);
-			border-color: var(--color-neutral-700);
-			--selector-bg-color: var(--color-neutral-700);
-			--selector-border-color: var(--color-neutral-800);
-			--selector-text-color: var(--color-gray-100);
-			--ec-brdCol: var(--color-neutral-700);
-		}
-	}
+    .aig-code-example-container {
+        background-color: var(--color-gray-200);
+        border-color: var(--color-neutral-300);
+        border-radius: 0.675rem;
+        border-bottom-left-radius: 0.85rem;
+        border-bottom-right-radius: 0.85rem;
+        --selector-bg-color: var(--color-white);
+        --selector-border-color: var(--color-neutral-300);
+        --selector-text-color: var(--color-gray-900);
+        --ec-brdRad: 0.675rem;
+        --ec-brdCol: var(--color-neutral-300);
+        &:where([data-theme=dark], [data-theme=dark] *) {
+            background-color: var(--color-neutral-900);
+            border-color: var(--color-neutral-700);
+            --selector-bg-color: var(--color-neutral-700);
+            --selector-border-color: var(--color-neutral-800);
+            --selector-text-color: var(--color-gray-100);
+            --ec-brdCol: var(--color-neutral-700);
+        }
+    }
 </style>
-<div class="aig-code-example-container border">
-	<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
-	{
-		(!forceClient || forceClient === "openai-js") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="openai-js"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={code
-							.replace("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("    {headerauth}\n", "")}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "openai-js") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="openai-js"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={code
-							.replace("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("{cf_api_token}", "{" + option.provider + "_api_token}")
-							.replace(
-								"    {headerauth}\n",
-								'  defaultHeaders: {\n      // if gateway is authenticated\n      "cf-aig-authorization": `Bearer {cf_api_token}`, \n  },\n',
-							)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKUnifiedCode
-							.replaceAll("{provider}", option.provider)
-							.replaceAll("{apikey}", "")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKUnifiedCode
-							.replaceAll("{provider}", option.provider)
-							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
+<div class="border aig-code-example-container">
+<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
+{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript" title="" code={code
+        .replace("{provider}", option.provider)
+        .replace("{model}", option.model)
+        .replace("    {headerauth}\n","")}
+         />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript" title="" code={code
+        .replace("{provider}", option.provider)
+        .replace("{model}", option.model)
+        .replace("{cf_api_token}", "{" + option.provider + "_api_token}")
+        .replace("    {headerauth}\n","  defaultHeaders: {\n      // if gateway is authenticated\n      \"cf-aig-authorization\": `Bearer {cf_api_token}`, \n  },\n")}
+         />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
+            .replaceAll("{provider}", option.provider)
+            .replaceAll("{apikey}", "")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
+            .replaceAll("{provider}", option.provider)
+            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
 
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="stored"
-					apiType="native"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKNativeCode
-							.replaceAll("{provider}", option.aiSDK.provider)
-							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-							.replaceAll("{apikey}", "")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="in-request"
-					apiType="native"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKNativeCode
-							.replaceAll("{provider}", option.aiSDK.provider)
-							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKNativeCode
+            .replaceAll("{provider}", option.aiSDK.provider)
+            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+            .replaceAll("{apikey}", "")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKNativeCode
+            .replaceAll("{provider}", option.aiSDK.provider)
+            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
 
-	{
-		(!forceClient || forceClient === "curl") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="curl"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						title=""
-						lang="curl"
-						code={curlCode
-							.replaceAll("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("{headerauth}\n", "")}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "curl") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="curl"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						title=""
-						lang="curl"
-						code={curlCode
-							.replaceAll("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace(
-								"{headerauth}\n",
-								"  --header 'Authorization: Bearer {" +
-									option.provider +
-									"_api_token}' \\\n",
-							)}
-					/>
-				</CodeExample>
-			))
-	}
-</div>
+{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="curl" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code title="" lang="curl" code={curlCode
+            .replaceAll("{provider}", option.provider)
+            .replace("{model}", option.model)
+            .replace("{headerauth}\n","")}
+             />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="curl" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code title="" lang="curl" code={curlCode
+            .replaceAll("{provider}", option.provider)
+            .replace("{model}", option.model)
+            .replace("{headerauth}\n","  --header 'Authorization: Bearer {" + option.provider + "_api_token}' \\\n")} />
+    </CodeExample>
+))}
+</div>
\ No newline at end of file
diff --git a/src/components/changelog/Pagination.astro b/src/components/changelog/Pagination.astro
index 633f1407b109d74..33e8d73fe0001bd 100644
--- a/src/components/changelog/Pagination.astro
+++ b/src/components/changelog/Pagination.astro
@@ -52,10 +52,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 
 {
 	lastPage > 1 && (
-		<nav
-			class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2"
-			aria-label="Pagination"
-		>
+		<nav class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2" aria-label="Pagination">
 			{prevUrl ? (
 				<a href={prevUrl} class="pagination-btn no-underline">
 					← Prev
@@ -67,7 +64,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 			<div class="pagination-pages flex items-center gap-1">
 				{items.map((item) =>
 					item === null ? (
-						<span class="text-sl-color-gray-3 flex h-9 items-center justify-center px-2 text-sm">
+						<span class="flex h-9 items-center justify-center px-2 text-sm text-sl-color-gray-3">
 							…
 						</span>
 					) : item === currentPage ? (
diff --git a/src/components/models/CopyableCode.astro b/src/components/models/CopyableCode.astro
index 0b17ed3299291d7..cf13027f562709e 100644
--- a/src/components/models/CopyableCode.astro
+++ b/src/components/models/CopyableCode.astro
@@ -8,7 +8,12 @@ const { text, label = "Copy" } = Astro.props;
 ---
 
 <copyable-code data-text={text}>
-	<button type="button" title={label} aria-label={label} class="copy-button">
+	<button
+		type="button"
+		title={label}
+		aria-label={label}
+		class="copy-button"
+	>
 		<code>{text}</code>
 		<svg
 			xmlns="http://www.w3.org/2000/svg"
@@ -38,9 +43,7 @@ const { text, label = "Copy" } = Astro.props;
 		border: 1px solid var(--sl-color-gray-5);
 		background: transparent;
 		cursor: pointer;
-		transition:
-			border-color 0.15s,
-			background-color 0.15s;
+		transition: border-color 0.15s, background-color 0.15s;
 	}
 
 	.copy-button:hover {
diff --git a/src/components/models/ModelDetailPage.astro b/src/components/models/ModelDetailPage.astro
index 1019e2aa09c5ec0..f24f3a3540c7658 100644
--- a/src/components/models/ModelDetailPage.astro
+++ b/src/components/models/ModelDetailPage.astro
@@ -188,9 +188,7 @@ const starlightPageProps = {
 			? { depth: 2, slug: "Examples", text: "Examples" }
 			: false,
 		hasSchema ? { depth: 2, slug: "Parameters", text: "Parameters" } : false,
-		hasSchema
-			? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" }
-			: false,
+		hasSchema ? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" } : false,
 	].filter((v) => Boolean(v)) as MarkdownHeading[],
 	hideTitle: true,
 } as StarlightPageProps;
@@ -426,114 +424,22 @@ const starlightPageProps = {
 					{model.apiModes.flatMap((mode) => [
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">
-									{mode.name}
-								</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
 								<span class="ml-2 text-gray-500 dark:text-gray-400">Input</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/${mode.id}-input.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-										<polyline points="15 3 21 3 21 9" />
-										<line x1="10" y1="14" x2="21" y2="3" />
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/${mode.id}-input.json`}
-									download={`${mode.id}-input.json`}
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-										<polyline points="7 10 12 15 17 10" />
-										<line x1="12" y1="15" x2="12" y2="3" />
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/${mode.id}-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/${mode.id}-input.json`} download={`${mode.id}-input.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>,
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">
-									{mode.name}
-								</span>
-								<span class="ml-2 text-gray-500 dark:text-gray-400">
-									Output
-								</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
+								<span class="ml-2 text-gray-500 dark:text-gray-400">Output</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/${mode.id}-output.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-										<polyline points="15 3 21 3 21 9" />
-										<line x1="10" y1="14" x2="21" y2="3" />
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/${mode.id}-output.json`}
-									download={`${mode.id}-output.json`}
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-										<polyline points="7 10 12 15 17 10" />
-										<line x1="12" y1="15" x2="12" y2="3" />
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/${mode.id}-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/${mode.id}-output.json`} download={`${mode.id}-output.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>,
 					])}
@@ -577,115 +483,17 @@ const starlightPageProps = {
 					<h2 id="API-Schemas">API Schemas (Raw)</h2>
 					<div class="not-content grid grid-cols-1 gap-2 sm:grid-cols-2">
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
-								Input
-							</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Input</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/schema-input.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-											<polyline points="15 3 21 3 21 9" />
-											<line x1="10" y1="14" x2="21" y2="3" />
-										</>
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/schema-input.json`}
-									download="schema-input.json"
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-											<polyline points="7 10 12 15 17 10" />
-											<line x1="12" y1="15" x2="12" y2="3" />
-										</>
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/schema-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/schema-input.json`} download="schema-input.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
-								Output
-							</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Output</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/schema-output.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-											<polyline points="15 3 21 3 21 9" />
-											<line x1="10" y1="14" x2="21" y2="3" />
-										</>
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/schema-output.json`}
-									download="schema-output.json"
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-											<polyline points="7 10 12 15 17 10" />
-											<line x1="12" y1="15" x2="12" y2="3" />
-										</>
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/schema-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/schema-output.json`} download="schema-output.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>
 					</div>
diff --git a/src/components/models/SchemaDisplay.astro b/src/components/models/SchemaDisplay.astro
index e87bb767e12aced..6dcb17aa8c69d0f 100644
--- a/src/components/models/SchemaDisplay.astro
+++ b/src/components/models/SchemaDisplay.astro
@@ -196,10 +196,11 @@ function collectRows(
 			(reg.annotations?.description as string | undefined) ??
 			nullableChildDescription;
 		// Check both validations and fragment for enum (different schema parsers put it in different places)
-		const enumValues = (
-			(reg.validations?.enum as unknown[]) ??
-			((reg.fragment as Record<string, unknown>)?.enum as unknown[])
-		)?.map(String);
+		const enumValues =
+			((reg.validations?.enum as unknown[]) ??
+				((reg.fragment as Record<string, unknown>)?.enum as unknown[]))?.map(
+				String,
+			);
 
 		// Collect all metadata from fragment and validations
 		const metadata: Record<string, string | number | boolean> = {};
@@ -428,12 +429,7 @@ const variantRows =
 				No parameters defined.
 			</p>
 		) : (
-			<SchemaTreeView
-				rows={rows}
-				schemaId={schemaId}
-				hideRequired={hideRequired}
-				client:visible
-			/>
+			<SchemaTreeView rows={rows} schemaId={schemaId} hideRequired={hideRequired} client:visible />
 		)
 	}
 </div>
diff --git a/src/components/models/code/DeepgramFlux.astro b/src/components/models/code/DeepgramFlux.astro
index 119317163ac8ede..c5c957d047b01e8 100644
--- a/src/components/models/code/DeepgramFlux.astro
+++ b/src/components/models/code/DeepgramFlux.astro
@@ -73,13 +73,11 @@ function generateRandomAudio() {
   return buffer;
 }
 `;
+
 ---
 
 <>
-	<Details
-		header="Step 1: Create a Worker that establishes a WebSocket connection"
-		open
-	>
+	<Details header="Step 1: Create a Worker that establishes a WebSocket connection" open>
 		<Code code={worker} lang="ts" />
 	</Details>
 
@@ -87,10 +85,7 @@ function generateRandomAudio() {
 		<Code code={deployWorker} lang="sh" />
 	</Details>
 
-	<Details
-		header="Step 3: Write a client script to connect to your Worker and send audio"
-		open
-	>
-		<Code code={clientScript} lang="js" />
-	</Details>
+  <Details header="Step 3: Write a client script to connect to your Worker and send audio" open>
+    <Code code={clientScript} lang="js" />
+  </Details>
 </>
diff --git a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
index ac2d801c62fdeb2..e1f4ce5d0ae4e09 100644
--- a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
+++ b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
@@ -76,8 +76,8 @@ curl https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/v1/
 		</li>
 		<li>
 			<strong>Workers AI Run</strong> (<code>/ai/run</code>) - Dynamic format
-			detection, accepts Chat Completions (<code>messages</code>), legacy
-			Completions (<code>prompt</code>), or Responses API (<code>input</code>)
+			detection, accepts Chat Completions (<code>messages</code>), legacy Completions
+			(<code>prompt</code>), or Responses API (<code>input</code>)
 		</li>
 		<li>
 			<strong>Chat Completions</strong> (<code>/v1/chat/completions</code>) -
diff --git a/src/components/overrides/Page.astro b/src/components/overrides/Page.astro
index e0ba5423f7dfb20..193c0458f2d2a57 100644
--- a/src/components/overrides/Page.astro
+++ b/src/components/overrides/Page.astro
@@ -12,11 +12,9 @@ const html = await Astro.slots.render("default");
 // Agent-setup pages use `template: splash` (to avoid sidebar group lookup) but
 // still need a right-hand ToC. Splash pages have props.toc === undefined, so we
 // bootstrap the object here before calling generateTableOfContents.
-const isAgentSetup =
-	props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
+const isAgentSetup = props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
 if (isAgentSetup) {
-	if (!props.toc)
-		props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
+	if (!props.toc) props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
 	props.hideBreadcrumbs = true;
 	props.hideTitle = true;
 }
diff --git a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
index d03cecd7bab8754..c7f5ea93bac1254 100644
--- a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
+++ b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
@@ -1,12 +1,12 @@
 ---
 title: Cloudflare Access Logging supports the Customer Metadata Boundary (CMB)
-description: Access logs will now respect the CMB.
+description: Access logs will now respect the CMB. 
 date: 2025-08-14
 products:
   - access
 ---
 
-Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration.
+Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration. 
 
 :::note
 For EU CMB customers, the logs will not be stored by Access and will appear as empty in the dashboard. EU CMB customers should utilize [Logpush](/logs/logpush/) to retain their Access logging, if desired.
diff --git a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
index cd95cf8fdd1edba..a82bbcbeee550b8 100644
--- a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
+++ b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
@@ -15,3 +15,4 @@ An [MCP server portal](/cloudflare-one/access-controls/ai-controls/mcp-portals/)
 - **Observability**: Once the user's AI agent is connected to the portal, Cloudflare Access logs the individual requests made using the tools in the portal.
 
 This is available in an open beta for all customers across all plans! For more information check out our [blog](https://blog.cloudflare.com/zero-trust-mcp-server-portals/) for this release.
+
diff --git a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
index 91a89f79924c5c2..675b9236a2b9f3d 100644
--- a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
+++ b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
@@ -12,4 +12,6 @@ A new **Allow clientless access** setting makes it easier to connect users witho
 
 Previously, to provide clientless access to a private hostname or IP without a [published application](/cloudflare-one/networks/routes/add-routes/#add-a-published-application-route), you had to create a separate [bookmark application](/cloudflare-one/access-controls/applications/bookmarks/) pointing to a prefixed [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) URL (for example, `https://<your-teamname>.cloudflareaccess.com/browser/https://10.0.0.1/`). This bookmark was visible to all users in the App Launcher, regardless of whether they had access to the underlying application.
 
-Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
+Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When  **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
+
+
diff --git a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
index 8524d2348de427d..e3dde55074d43c6 100644
--- a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
+++ b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
@@ -33,13 +33,13 @@ const tools = {
 	getWeather: tool({
 		description: "Get weather for a city",
 		inputSchema: z.object({ city: z.string() }),
-		execute: async ({ city }) => fetchWeather(city),
+		execute: async ({ city }) => fetchWeather(city)
 	}),
 
 	// Client-executed tool (no execute = client handles via onToolCall)
 	getLocation: tool({
 		description: "Get user location from browser",
-		inputSchema: z.object({}),
+		inputSchema: z.object({})
 		// No execute function
 	}),
 
@@ -48,8 +48,8 @@ const tools = {
 		description: "Process a payment",
 		inputSchema: z.object({ amount: z.number() }),
 		needsApproval: async ({ amount }) => amount > 100,
-		execute: async ({ amount }) => charge(amount),
-	}),
+		execute: async ({ amount }) => charge(amount)
+	})
 };
 ```
 
@@ -70,11 +70,11 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 				toolCallId: toolCall.toolCallId,
 				output: {
 					lat: position.coords.latitude,
-					lng: position.coords.longitude,
-				},
+					lng: position.coords.longitude
+				}
 			});
 		}
-	},
+	}
 });
 ```
 
@@ -97,9 +97,9 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 		// Handle client-side tool execution
 		await addToolOutput({
 			toolCallId: toolCall.toolCallId,
-			output: { result: "success" },
+			output: { result: "success" }
 		});
-	},
+	}
 });
 ```
 
@@ -112,12 +112,12 @@ const paymentTool = tool({
 	description: "Process a payment",
 	inputSchema: z.object({
 		amount: z.number(),
-		recipient: z.string(),
+		recipient: z.string()
 	}),
 	needsApproval: async ({ amount }) => amount > 1000,
 	execute: async ({ amount, recipient }) => {
 		return await processPayment(amount, recipient);
-	},
+	}
 });
 ```
 
@@ -138,7 +138,7 @@ const pendingToolCallConfirmation = messages.some((m) =>
 if (pendingToolCallConfirmation) {
 	await addToolOutput({
 		toolCallId: part.toolCallId,
-		output: "User approved the action",
+		output: "User approved the action"
 	});
 }
 ```
@@ -158,7 +158,7 @@ import { convertToModelMessages } from "ai";
 
 const result = streamText({
 	messages: await convertToModelMessages(this.messages),
-	model: openai("gpt-4o"),
+	model: openai("gpt-4o")
 });
 ```
 
@@ -182,14 +182,14 @@ const result = await generateObject({
 	mode: "json",
 	model,
 	schema,
-	prompt,
+	prompt
 });
 
 // After (v6)
 const result = await generateObject({
 	model,
 	schema,
-	prompt,
+	prompt
 });
 ```
 
@@ -203,10 +203,10 @@ import { generateText, Output, stepCountIs } from "ai";
 const { output } = await generateText({
 	model: openai("gpt-4"),
 	output: Output.object({
-		schema: z.object({ name: z.string() }),
+		schema: z.object({ name: z.string() })
 	}),
 	stopWhen: stepCountIs(2),
-	prompt: "Generate a name",
+	prompt: "Generate a name"
 });
 ```
 
@@ -282,11 +282,11 @@ import { createAIGateway } from "ai-gateway-provider";
 const model = createAIGateway({
 	gatewayUrl: "https://gateway.ai.cloudflare.com/v1/your-account-id/gateway",
 	headers: {
-		Authorization: `Bearer ${env.AI_GATEWAY_TOKEN}`,
-	},
+		"Authorization": `Bearer ${env.AI_GATEWAY_TOKEN}`
+	}
 })({
 	provider: "openai",
-	model: "gpt-4o",
+	model: "gpt-4o"
 });
 ```
 
diff --git a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
index af9c6cd51586110..c47df65f32e38d4 100644
--- a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
+++ b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
@@ -10,25 +10,25 @@ We are excited to announce two major capability upgrades for **Agent Lee**, the
 
 ### Take action with Write Operations
 
-Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.
+Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. 
 
 To ensure security and accuracy, every write operation requires **explicit user approval**. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select **Confirm**, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.
 
 **Example requests:**
+* *"Add an A record for blog.example.com pointing to 192.0.2.10."*
+* *"Enable Always Use HTTPS on my zone."*
+* *"Set the SSL mode for example.com to Full (strict)."*
 
-- _"Add an A record for blog.example.com pointing to 192.0.2.10."_
-- _"Enable Always Use HTTPS on my zone."_
-- _"Set the SSL mode for example.com to Full (strict)."_
 
 ### Visualize data with Generative UI
 
 Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features **Generative UI**, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry.
 
 **Example requests:**
+* *"Show me a chart of my traffic over the last 7 days."*
+* *"What does my error rate look like for the past 24 hours?"*
+* *"Graph my cache hit rate for example.com this week."*
 
-- _"Show me a chart of my traffic over the last 7 days."_
-- _"What does my error rate look like for the past 24 hours?"_
-- _"Graph my cache hit rate for example.com this week."_
 
 ---
 
diff --git a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
index 6142d6dbab74b1a..70d67fd32103d74 100644
--- a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
+++ b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
@@ -16,4 +16,4 @@ You can find these metrics within each AutoRAG instance:
 - Search breakdown: Compare usage between `ai-search` and `search` endpoints.
 - Top file retrievals: Identify which files are most frequently retrieved in a given period.
 
-Try it today in [AutoRAG](/ai-search/get-started/).
+Try it today in [AutoRAG](/ai-search/get-started/).
\ No newline at end of file
diff --git a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
index 37bf0f628f7a6a7..1eff4229721c7bd 100644
--- a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
+++ b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
@@ -13,9 +13,9 @@ With AI Search you can now use models from different providers like OpenAI and A
 To use AI Search with other [model providers](/ai-search/configuration/models/):
 
 1. **Add provider keys to AI Gateway**
-   1. Go to AI > AI Gateway in the dashboard.
-   2. Select or create an AI gateway.
-   3. In Provider Keys, choose your provider, click Add, and enter the key.
+    1. Go to AI > AI Gateway in the dashboard.
+    2. Select or create an AI gateway.
+    3. In Provider Keys, choose your provider, click Add, and enter the key.
 2. **Connect a gateway to AI Search**: When creating a new AI Search, select the AI Gateway with your provider keys. For an existing AI Search, go to Settings and switch to a gateway that has your keys under Resources.
 3. **Select models**: Embedding models are only available to be changed when creating a new AI Search. Generation model can be selected when creating a new AI Search and can be changed at any time in Settings.
 
@@ -23,18 +23,19 @@ Once configured, your AI Search instance will be able to reference models availa
 
 ```javascript
 export default {
-	async fetch(request, env) {
-		// Query your AI Search instance with a natural language question to an OpenAI model
-		const result = await env.AI.autorag("my-ai-search").aiSearch({
-			query: "What's new for Cloudflare Birthday Week?",
-			model: "openai/gpt-5",
-		});
-
-		// Return only the generated answer as plain text
-		return new Response(result.response, {
-			headers: { "Content-Type": "text/plain" },
-		});
-	},
+  async fetch(request, env) {
+    
+    // Query your AI Search instance with a natural language question to an OpenAI model
+    const result = await env.AI.autorag("my-ai-search").aiSearch({
+      query: "What's new for Cloudflare Birthday Week?",
+      model: "openai/gpt-5"
+    });
+
+    // Return only the generated answer as plain text
+    return new Response(result.response, {
+      headers: { "Content-Type": "text/plain" },
+    });
+  },
 };
 ```
 
diff --git a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
index 561919395ce174d..5a9abdb9296fae3 100644
--- a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
+++ b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
@@ -10,8 +10,7 @@ date: 2025-11-19
 
 Previously, AI Search could only crawl publicly accessible pages, leaving knowledge bases, documentation, and other protected content out of your search results. With custom headers support, you can now include authentication credentials that allow the crawler to access this protected content.
 
-This is particularly useful for indexing content like:
-
+This is particularly useful for indexing content like: 
 - **Internal documentation** behind corporate login systems
 - **Premium content** that requires users to provide access to unlock
 - **Sites protected by Cloudflare Access** using service tokens
@@ -27,6 +26,6 @@ CF-Access-Client-Id: your-token-id.access
 CF-Access-Client-Secret: your-token-secret
 ```
 
-The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked.
+The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked. 
 
-Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
+Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
\ No newline at end of file
diff --git a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
index 105ae21f43fe4fd..a54b6cddfff6e9a 100644
--- a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
+++ b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
@@ -7,13 +7,13 @@ date: 2026-04-16T12:00:00Z
 publish_future_dated_entry: true
 ---
 
-New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away.
+New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away. 
 
 Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call.
 
 ## Built-in storage and vector index
 
-All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first.
+All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first. 
 
 ```ts
 const instance = env.AI_SEARCH.get("my-instance");
diff --git a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
index 420f30e5265e339..e8c0c6621a0467f 100644
--- a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
+++ b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
@@ -3,12 +3,12 @@ title: New Confidence Intervals in GraphQL Analytics API
 description: Confidence intervals are now supported in the GraphQL Analytics API to show statistical ranges for sampled data results
 date: 2025-10-01
 ---
-
-The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty.
+ 
+The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty. 
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`).
+- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`). 
 - **Default**: If no confidence level is specified, no intervals are returned.
 
-For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/).
+For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/). 
diff --git a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
index 91c0a2dc9d56063..6194d159eaef0a2 100644
--- a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
+++ b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
@@ -8,10 +8,10 @@ The Server-Timing header now includes a new `cfWorker` metric that measures time
 
 Previously, Worker execution time was included in the `edge` metric, making it harder to identify true edge performance. The new `cfWorker` metric provides this visibility:
 
-| Metric     | Description                                                                           |
-| ---------- | ------------------------------------------------------------------------------------- |
-| `edge`     | Total time spent on the Cloudflare edge, including Worker execution                   |
-| `origin`   | Time spent fetching from the origin server                                            |
+| Metric | Description |
+| --- | --- |
+| `edge` | Total time spent on the Cloudflare edge, including Worker execution |
+| `origin` | Time spent fetching from the origin server |
 | `cfWorker` | Time spent in Worker execution, including subrequests but excluding origin fetch time |
 
 ### Example response
diff --git a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
index 32a3c52bdfbfc7f..1b6ce51e1eb4bfd 100644
--- a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
+++ b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
@@ -10,8 +10,8 @@ Cloudflare is launching the [Open Beta of the **Web and API Vulnerability Scanne
 
 The initial release focuses on detecting Broken Object Level Authorization (BOLA) vulnerabilities by building API call graphs to simulate attacker and owner contexts, then testing these contexts by sending real HTTP requests to your APIs.
 
-The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release.
+The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release. 
 
 **Access**: This feature is only available to API Shield subscribers via the Cloudflare API. We hope you will use the API for programmatic integration into your CI/CD pipelines and security dashboards.
 
-**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
+**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
\ No newline at end of file
diff --git a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
index 8f0e0c75c5a3682..968d7e9e61a7325 100644
--- a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
+++ b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
@@ -12,13 +12,13 @@ You can now receive [event notifications](/queues/event-subscriptions/) for [Art
 
 This allows you to:
 
-- Run custom workflows when a repository is created or imported
-- Kick off a build and deploy a change when an agent pushes to a repo
-- Trigger a review agent on every push
+* Run custom workflows when a repository is created or imported
+* Kick off a build and deploy a change when an agent pushes to a repo
+* Trigger a review agent on every push
 
 Available events include:
 
-- **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
-- **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
+* **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
+* **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
 
 To learn more, refer to [Artifacts documentation](/artifacts/guides/event-subscriptions/).
diff --git a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
index 18f7b35d1cbd348..d613bad87530e49 100644
--- a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
+++ b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
@@ -27,3 +27,4 @@ You can now create optimized cache rules instantly with **one-click templates**,
 ## Get started
 
 To get started, go to [**Rules > Templates**](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) in the dashboard. For more information, refer to the [Cache Rules documentation](/cache/how-to/cache-rules/).
+
diff --git a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
index 803a3785a4f7930..13727aa33125d77 100644
--- a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
+++ b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
@@ -26,14 +26,14 @@ When configuring [custom cache keys](/cache/how-to/cache-keys/), you can now inc
 
 ```json
 {
-	"cache_key": {
-		"custom_key": {
-			"header": {
-				"include": ["accept-language", "user-agent"],
-				"check_presence": ["referer"]
-			}
-		}
-	}
+  "cache_key": {
+    "custom_key": {
+      "header": {
+        "include": ["accept-language", "user-agent"],
+        "check_presence": ["referer"]
+      }
+    }
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
index a9d29c3c2cfc2b5..3f346c5807413c8 100644
--- a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
+++ b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
@@ -20,19 +20,19 @@ The Trace response includes the cache key in the `cache` object:
 
 ```json
 {
-	"step_name": "request",
-	"type": "cache",
-	"matched": true,
-	"public_name": "Cache Parameters",
-	"cache": {
-		"key": {
-			"zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
-			"scheme": "https",
-			"host": "example.com",
-			"uri": "/images/hero.jpg"
-		},
-		"key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
-	}
+  "step_name": "request",
+  "type": "cache",
+  "matched": true,
+  "public_name": "Cache Parameters",
+  "cache": {
+    "key": {
+      "zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
+      "scheme": "https",
+      "host": "example.com",
+      "uri": "/images/hero.jpg"
+    },
+    "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
index 3f7c005146bb17a..814ebc40610e652 100644
--- a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
+++ b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
@@ -20,28 +20,28 @@ The detailed audit payload is visible within the Cloudflare Dashboard (under **M
 
 ```json
 {
-	"action": {
-		"result": "success",
-		"type": "create"
-	},
-	"actor": {
-		"id": "1234567890abcdef",
-		"email": "user@example.com",
-		"type": "user"
-	},
-	"resource": {
-		"product": "purge_cache",
-		"request": {
-			"files": [
-				"https://example.com/images/logo.png",
-				"https://example.com/css/styles.css"
-			]
-		}
-	},
-	"zone": {
-		"id": "023e105f4ecef8ad9ca31a8372d0c353",
-		"name": "example.com"
-	}
+  "action": {
+    "result": "success",
+    "type": "create"
+  },
+  "actor": {
+    "id": "1234567890abcdef",
+    "email": "user@example.com",
+    "type": "user"
+  },
+  "resource": {
+    "product": "purge_cache",
+    "request": {
+      "files": [
+        "https://example.com/images/logo.png",
+        "https://example.com/css/styles.css"
+      ]
+    }
+  },
+  "zone": {
+    "id": "023e105f4ecef8ad9ca31a8372d0c353",
+    "name": "example.com"
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
index 220ad070c02db00..f8b1270d926561c 100644
--- a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
+++ b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-24
 ---
 
-You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses _before_ they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
+You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses *before* they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
 
 ## What changed
 
diff --git a/src/content/changelog/casb/2025-10-28-casb-roles.mdx b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
index 45bf12202502ff5..0eba434bfd0c136 100644
--- a/src/content/changelog/casb/2025-10-28-casb-roles.mdx
+++ b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
@@ -8,8 +8,8 @@ date: 2025-10-28
 
 Cloudflare CASB (Cloud Access Security Broker) now supports two new granular roles to provide more precise access control for your security teams:
 
-- **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
-- **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
+* **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
+* **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
 
 These new roles help you better enforce the principle of least privilege. You can now grant specific members access to CASB security findings without assigning them broader permissions, such as the **Super Administrator** or **Administrator** roles.
 
diff --git a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
index 8293deadac922ee..06fb9e1526fa249 100644
--- a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
+++ b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
@@ -5,3 +5,4 @@ date: 2025-08-29
 ---
 
 We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client.
+
diff --git a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
index 40a2ecfb6928699..ae69ba66324f32d 100644
--- a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
+++ b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
@@ -9,9 +9,9 @@ products:
 Zero Trust Dashboard has a brand new, AI-powered search functionality. You can search your account by resources (applications, policies, device profiles, settings, etc.), pages, products, and more.
 
 ![Example search results in the Zero Trust dashboard](~/assets/images/changelog/cloudflare-one/searchexample.png)
-
+  
 **Ask Cloudy** — You can also ask Cloudy, our AI agent, questions about Cloudflare Zero Trust. Cloudy is trained on our developer documentation and implementation guides, so it can tell you how to configure functionality, best practices, and can make recommendations.
 
 Cloudy can then stay open with you as you move between pages to build configuration or answer more questions.
 
-**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
+**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
\ No newline at end of file
diff --git a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
index b0f6e01371820c0..d4b4b3081b4aa3a 100644
--- a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
+++ b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
@@ -8,10 +8,10 @@ products:
 
 You can now duplicate specific Cloudflare One resources with a single click from the dashboard.
 
-Initially supported resources:
 
-- Access Applications
-- Access Policies
-- Gateway Policies
+Initially supported resources:
+* Access Applications
+* Access Policies
+* Gateway Policies
 
-To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
+To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
\ No newline at end of file
diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
index 1cbf0a71d44db2b..3732caa81147c83 100644
--- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx
+++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
@@ -7,7 +7,7 @@ product: Gateway
 
 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications.
 
-33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security.
+33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. 
 
 To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**.
 
diff --git a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
index 9be106dafc193cc..03fb76c0a537bc1 100644
--- a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
+++ b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
@@ -23,4 +23,4 @@ Key details:
 
 Configuring Cloudflare source IPs requires Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
 
-For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
+For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
\ No newline at end of file
diff --git a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
index a42523b426c282c..32af30f28627705 100644
--- a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
+++ b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
@@ -9,7 +9,7 @@ date: 2025-10-01
 New instance types provide up to 4 vCPU, 12 GiB of memory, and 20 GB of disk per container instance.
 
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------- | ----- |
+| ------------- | ---- | ------  | ----  |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
diff --git a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
index 1d4d4ea196130e1..3a6f1aa9ae491fc 100644
--- a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
+++ b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
@@ -15,15 +15,15 @@ This means that you now pay less for Containers and Sandboxes.
 Imagine running the `standard-2` instance type for one hour, which can use up to 1 vCPU,
 but on average you use only 20% of your CPU capacity.
 
-CPU-time is priced at _$0.00002 per vCPU-second_.
+CPU-time is priced at *$0.00002 per vCPU-second*.
 
 Previously, you would be charged for the CPU allocated to the instance multiplied by the time it was active, in this case 1 hour.
 
-CPU cost would have been: **$0.072** — 1 vCPU _ 3600 seconds _ $0.00002
+CPU cost would have been: **$0.072** — 1 vCPU * 3600 seconds * $0.00002
 
 Now, since you are only using 20% of your CPU capacity, your CPU cost is cut to 20% of the previous amount.
 
-CPU cost is now: **$0.0144** — 1 vCPU _ 3600 seconds _ $0.00002 \* 20% utilization
+CPU cost is now: **$0.0144** — 1 vCPU * 3600 seconds * $0.00002 * 20% utilization
 
 This can significantly reduce costs for Containers and Sandboxes.
 
diff --git a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
index baf0295247c3495..242d66f2e0cf6e2 100644
--- a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
+++ b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
@@ -16,4 +16,4 @@ You can now run more [Containers](/containers/) concurrently with significantly
 
 This 15x increase enables larger-scale workloads on Containers. You can now run 15,000 instances of the `lite` instance type, 6,000 instances of `basic`, over 1,500 instances of `standard-1`, or over 1,000 instances of `standard-2` concurrently.
 
-Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
+Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
\ No newline at end of file
diff --git a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
index d9a25a5bf08676f..cb2468f841ffe89 100644
--- a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
+++ b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
@@ -27,4 +27,4 @@ Containers now support [Docker Hub](https://hub.docker.com/) images. You can use
 
 Containers also support private Docker Hub images. To configure credentials, refer to [Use private Docker Hub images](/containers/platform-details/image-management/#use-private-docker-hub-images).
 
-For more information, refer to [Image management](/containers/platform-details/image-management/).
+For more information, refer to [Image management](/containers/platform-details/image-management/).
\ No newline at end of file
diff --git a/src/content/changelog/containers/2026-04-05-regional-placement.mdx b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
index bb35775f82b0c78..2871fa894eff6a3 100644
--- a/src/content/changelog/containers/2026-04-05-regional-placement.mdx
+++ b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
@@ -8,10 +8,10 @@ date: 2026-04-05
 
 You can now specify placement constraints to control where your [Containers](/containers/) run.
 
-| Constraint     | Values                         | Use case              |
-| -------------- | ------------------------------ | --------------------- |
-| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR` | Geographic placement  |
-| `jurisdiction` | `eu`, `fedramp`                | Compliance boundaries |
+| Constraint     | Values                                  | Use case                          |
+| -------------- | --------------------------------------- | --------------------------------- |
+| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR`          | Geographic placement              |
+| `jurisdiction` | `eu`, `fedramp`                         | Compliance boundaries             |
 
 Use `regions` to limit placement to specific geographic areas. Use `jurisdiction` to restrict containers to compliance boundaries — `eu` maps to European regions (EEUR, WEUR) and `fedramp` maps to North American regions (ENAM, WNAM).
 
diff --git a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
index 169bb898b975965..4b8f807edcebfbe 100644
--- a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
+++ b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
@@ -74,7 +74,7 @@ Define named outbound handlers then apply or remove them at runtime using `setOu
 export class MySandbox extends Sandbox {}
 
 MySandbox.outboundHandlers = {
-	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext) => {
+	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext ) => {
 		const url = new URL(req.url);
 		if (ctx.params.allowedHostnames.includes(url.hostname)) {
 			return fetch(req);
diff --git a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
index 9b7229b637259e4..797ef3ce255a866 100644
--- a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
+++ b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
@@ -51,4 +51,4 @@ To disable SSH, set `ssh.enabled` to `false` in your Container configuration:
 
 </WranglerConfig>
 
-For more information, refer to the [SSH documentation](/containers/ssh/).
+For more information, refer to the [SSH documentation](/containers/ssh/).
\ No newline at end of file
diff --git a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
index 076405a6f32954f..7a8ddd2b404d6c1 100644
--- a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
+++ b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
@@ -6,7 +6,7 @@ date: 2025-11-12
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into WARP device metrics, connectivity, and network performance across your Cloudflare SASE deployment.
 
-We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience.
+We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience. 
 
 1. [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)
 2. [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)
@@ -15,4 +15,4 @@ We've released four new WARP and DEX device data sets that can be exported via [
 
 To create a new DEX or WARP Logpush job, customers can go to the account level of the Cloudflare dashboard > Analytics & Logs > Logpush to get started.
 
-![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
+![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
\ No newline at end of file
diff --git a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
index eaa2318c8339332..25a72ef1269d528 100644
--- a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
+++ b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
@@ -2,6 +2,7 @@
 title: DEX Supports EU Customer Metadata Boundary
 description: Digital Experience Monitoring now fully supports the EU Customer Metadata Boundary
 date: 2026-02-19
+
 ---
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into [WARP](/warp-client/) device connectivity and performance to any internal or external application.
diff --git a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
index 5dabd4aeb835f4e..df5d41b9f6f8634 100644
--- a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
@@ -9,4 +9,4 @@ date: 2026-04-28
 This Internet outage and traffic anomaly data is pulled from [Cloudflare Radar](https://radar.cloudflare.com/). All Internet outage and traffic anomaly observations can be viewed in the [Radar Outage Center](https://radar.cloudflare.com/outage-center).
 
 ![Digital Experience Monitoring dashboard notification for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_ux_notification.png)
-![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
+![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
\ No newline at end of file
diff --git a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
index a85263a713f6a1e..37b7e2b2737abdf 100644
--- a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
@@ -4,10 +4,9 @@ description: Customers can run speed tests from the Cloudflare One Client to Clo
 date: 2026-04-28
 ---
 
-IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge.
+IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge. 
 
 Each speed test includes the following metrics:
-
 - Internet speed: download and upload throughput
 - Latency: download, upload, unloaded latency, and jitter
 - Network quality score: video streaming, webchat/real-time communication (RTC)
diff --git a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
index 6af9120fe4e08ee..abfb872fa28d368 100644
--- a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
+++ b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
@@ -4,10 +4,9 @@ description: Digital experience now supports testing applications with authentic
 date: 2026-04-29
 ---
 
-[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/).
+[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/). 
 
 Digital experience tests also have enhanced configuration options including:
-
 - New HTTP methods (DELETE, PATCH, POST, PUT)
 - Secret Store headers, custom plain text headers, and custom request bodies
 - Advanced settings: follow redirects, response bodies, response headers, and allow untrusted certificates
diff --git a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
index 608405c5701e920..73705ab18a430b6 100644
--- a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
+++ b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
@@ -9,7 +9,6 @@ date: 2026-04-14T12:00:00Z
 **Account-level DLP settings are now available** in Cloudflare One. You can now configure advanced DLP settings at the account level, including OCR, AI context analysis, and payload masking. This provides consistent enforcement across all DLP profiles and simplifies configuration management.
 
 Key changes:
-
 - **Consistent enforcement**: Settings configured at the account level apply to all DLP profiles
 - **Simplified migration**: Settings enabled on any profile are automatically migrated to account level
 - **Deprecation notice**: Profile-level advanced settings will be deprecated in a future release
diff --git a/src/content/changelog/dlp/2025-07-17-document-matching.mdx b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
index 16c90b0f67b6ee1..7d3ef70acea78af 100644
--- a/src/content/changelog/dlp/2025-07-17-document-matching.mdx
+++ b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
@@ -15,9 +15,10 @@ You can now create [document-based](/cloudflare-one/data-loss-prevention/detecti
 - **Granular control with similarity percentage:** Define a minimum similarity percentage (0-100%) that a document must meet to trigger a detection, reducing false positives.
 
 - **Comprehensive coverage:** Apply these document-based detection entries in:
-  - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
 
-  - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
+    - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
+
+    - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
 
 - **Identify sensitive data:** This new detection entry type is ideal for identifying sensitive data within completed forms, templates, or even small snippets of a larger document, helping you prevent data exfiltration and ensure compliance.
 
diff --git a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
index 17cdc9544eb17e9..21f93780d77fd28 100644
--- a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
+++ b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
@@ -24,14 +24,14 @@ To help you apply these topics quickly, we have also released five new predefine
 
 3. **Granular Guardrails**
 
-   You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
+    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
 
-   ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
 
-4. **Full Prompt Logging**
+ 4. **Full Prompt Logging**
+   
+    To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by ```conversation_id```, allowing you to reconstruct the full context of an interaction that led to a policy violation.
 
-   To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by `conversation_id`, allowing you to reconstruct the full context of an interaction that led to a policy violation.
-
-   ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
 
 AI prompt protection is now available in open beta. To learn more about it, read the [blog](https://blog.cloudflare.com/ai-prompt-protection/#closing-the-loop-logging) or refer to [AI prompt topics](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics).
diff --git a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
index d8e05425862ab77..5c12da589a2636c 100644
--- a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
+++ b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
@@ -11,7 +11,7 @@ Gateway now includes a predefined DLP profile called **Unsanitized HAR** that de
 
 ## How to configure a HAR file policy
 
-In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
+In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to  **Zero Trust** >  **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
 
 | Selector    | Operator | Value             | Action |
 | ----------- | -------- | ----------------- | ------ |
diff --git a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
index 649f291806b1ee8..7326522ab2e356e 100644
--- a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
+++ b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
@@ -7,11 +7,11 @@ products: [dlp]
 
 The **Credentials and Secrets** DLP profile now includes three new predefined entries for detecting Cloudflare API credentials:
 
-| Entry name                         | Token prefix | Detects                   |
-| ---------------------------------- | ------------ | ------------------------- |
-| Cloudflare User API Key            | `cfk_`       | User-scoped API keys      |
-| Cloudflare User API Token          | `cfut_`      | User-scoped API tokens    |
-| Cloudflare Account Owned API Token | `cfat_`      | Account-scoped API tokens |
+| Entry name | Token prefix | Detects |
+| --- | --- | --- |
+| Cloudflare User API Key | `cfk_` | User-scoped API keys |
+| Cloudflare User API Token | `cfut_` | User-scoped API tokens |
+| Cloudflare Account Owned API Token | `cfat_` | Account-scoped API tokens |
 
 These detections target the new [Cloudflare API credential format](/fundamentals/api/get-started/token-formats/), which uses a structured prefix and a CRC32 checksum suffix. The identifiable prefix makes it possible to detect leaked credentials with high confidence and low false positive rates — no surrounding context such as `Authorization: Bearer` headers is required.
 
@@ -26,9 +26,9 @@ Credentials generated before this format change will not be matched by these ent
 
 Example policy:
 
-| Selector    | Operator | Value                     | Action |
-| ----------- | -------- | ------------------------- | ------ |
-| DLP Profile | in       | _Credentials and Secrets_ | Block  |
+| Selector | Operator | Value | Action |
+| --- | --- | --- | --- |
+| DLP Profile | in | _Credentials and Secrets_ | Block |
 
 You can also enable individual entries to scope detection to specific credential types — for example, enabling **Account Owned API Token** detection without enabling **User API Key** detection.
 
diff --git a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
index 64134f5ef20859c..a4a744c06468c98 100644
--- a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
+++ b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
@@ -2,7 +2,7 @@
 title: Detect PII records with a new predefined DLP profile
 description: A new predefined DLP profile detects records that contain multiple types of personal data, reducing false positives from isolated matches.
 date: 2026-04-28
-products:
+products: 
   - dlp
 ---
 
diff --git a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
index fda8a201e4ce67f..483aed6201b6f66 100644
--- a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
+++ b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
@@ -7,7 +7,6 @@ date: 2026-03-31
 Internal DNS is now in open beta.
 
 ## Who can use it?
-
 Internal DNS is bundled as a part of Cloudflare Gateway and is now available to every Enterprise customer with one of the following subscriptions:
 
 - Cloudflare Zero Trust Enterprise
diff --git a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
index e9117eeb36fbf71..ada68f5dc86c767 100644
--- a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
+++ b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
@@ -3,7 +3,6 @@ title: Account-level enforce DNS-only
 description: Bypass Cloudflare's reverse proxy for all zones in your account with a single API call.
 date: 2026-04-28
 ---
-
 import { DashButton } from "~/components";
 
 You can now disable Cloudflare's reverse proxy across all zones in your account simultaneously using the new `enforce_dns_only` setting. When enabled, Cloudflare responds to DNS queries for all proxied records with your origin IP addresses instead of Cloudflare's anycast IPs.
diff --git a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
index eb2897fd7f98f7b..e03702fa3be2931 100644
--- a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
+++ b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
@@ -10,11 +10,11 @@ date: 2025-08-21
 You can now create a client (a [Durable Object stub](/durable-objects/api/stub/)) to a Durable Object with the new `getByName` method, removing the need to convert Durable Object names to IDs and then create a stub.
 
 ```js
-// Before: (1) translate name to ID then (2) get a client
+// Before: (1) translate name to ID then (2) get a client 
 const objectId = env.MY_DURABLE_OBJECT.idFromName("foo"); // or .newUniqueId()
-const stub = env.MY_DURABLE_OBJECT.get(objectId);
+const stub = env.MY_DURABLE_OBJECT.get(objectId); 
 
-// Now: retrieve client to Durable Object directly via its name
+// Now: retrieve client to Durable Object directly via its name 
 const stub = env.MY_DURABLE_OBJECT.getByName("foo");
 
 // Use client to send request to the remote Durable Object
@@ -23,4 +23,4 @@ const rpcResponse = await stub.sayHello();
 
 Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together. You can have billions of Durable Objects, providing isolation between application tenants.
 
-To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
+To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
\ No newline at end of file
diff --git a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
index b0b6b6b70c779bb..10b3c5b7270cdbe 100644
--- a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
+++ b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
 
 ![Screenshot of Durable Objects Data Studio](~/assets/images/workers/changelog/do-data-studio.png)
 
-You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.
+You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.  
 
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
diff --git a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
index ab0bc29c8091916..7d4b1c1963247eb 100644
--- a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
+++ b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
@@ -9,10 +9,9 @@ date: 2025-12-12
 
 import { DashButton } from "~/components";
 
-Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier).
+Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). 
 
 To view your SQLite storage usage, go to the **Durable Objects** page
-
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
 If you do not want to incur costs, please take action such as optimizing queries or deleting unnecessary stored data in order to reduce your SQLite storage usage ahead of the January 7th target. Only usage on and after the billing target date will incur charges.
diff --git a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
index 01b6f70aebb1c1f..c3a7dd97977d0d4 100644
--- a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
+++ b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
@@ -15,19 +15,19 @@ This is especially useful for [alarms](/durable-objects/api/alarms/), where ther
 import { DurableObject } from "cloudflare:workers";
 
 export class ChatRoom extends DurableObject {
-	async getRoomName() {
-		// ctx.id.name returns the name passed to getByName() or idFromName()
-		return this.ctx.id.name;
-	}
+  async getRoomName() {
+    // ctx.id.name returns the name passed to getByName() or idFromName()
+    return this.ctx.id.name;
+  }
 }
 
 // Worker
 export default {
-	async fetch(request, env) {
-		const stub = env.CHAT_ROOM.getByName("general");
-		const roomName = await stub.getRoomName();
-		return new Response(`Welcome to ${roomName}!`);
-	},
+  async fetch(request, env) {
+    const stub = env.CHAT_ROOM.getByName("general");
+    const roomName = await stub.getRoomName();
+    return new Response(`Welcome to ${roomName}!`);
+  },
 };
 ```
 
diff --git a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
index 7bbf5100d38aea3..d4933092b676b0e 100644
--- a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
+++ b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
@@ -12,4 +12,4 @@ Customers can use this feature to dynamically add context to their emails, such
 
 ![Subaddressing](~/assets/images/changelog/email-routing/subaddressing.png)
 
-Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
+Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
\ No newline at end of file
diff --git a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
index 7ac05e0429ad659..2a643465f298e14 100644
--- a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
+++ b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
@@ -16,4 +16,4 @@ This feature is available across these Email security packages:
 
 - **Advantage**
 - **Enterprise**
-- **Enterprise + PhishGuard**
+- **Enterprise + PhishGuard**
\ No newline at end of file
diff --git a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
index 24afb396ce499bc..7e74cf7136cb225 100644
--- a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
+++ b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
@@ -13,6 +13,7 @@ These reports offer several key benefits:
 - **Configuration Transparency:** Gain a clear view of your policy, submission, and domain configurations to ensure optimal setup.
 - **Account Takeover Risks:** Get a snapshot of your M365 risky users (requires a Microsoft Entra ID P2 license and [M365 SaaS integration](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/microsoft-365/)).
 
+
 To get started, refer to [Download a security report](/cloudflare-one/email-security/monitoring/download-report/#download-a-security-report).
 ![Report](~/assets/images/changelog/email-security/report.png)
 
diff --git a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
index cbb47a69c0949ea..47d73e8920e5d3c 100644
--- a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
+++ b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
@@ -6,7 +6,8 @@ date: 2025-11-18
 
 # Adjustment to Final Disposition column
 
-## The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
+The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
+---
 
 ### What's Changing
 
diff --git a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
index 92b39dac688afa0..b8d67579c27c156 100644
--- a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
+++ b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
@@ -1,6 +1,6 @@
 ---
 title: Reclassifications to Submissions
-description: Submission terminology update to reflect outcomes
+description: Submission terminology update to reflect outcomes 
 date: 2025-12-03T21:11:33Z
 ---
 
@@ -10,8 +10,7 @@ Submissions are leveraged to tune future variants of campaigns. To respect data
 
 ![nav_example](~/assets/images/changelog/email-security/reclassification-submission.png)
 
-This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Advantage** 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
index e12c5cc1bef0386..b38737ac382f6db 100644
--- a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
+++ b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
@@ -4,7 +4,7 @@ description: Additional post delivery action log details for failures
 date: 2026-01-12T11:15:33Z
 ---
 
-The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field.
+The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field. 
 
 :::note
 Error messages will vary depending on whether you are using Google Workspace or Microsoft 365.
@@ -14,7 +14,6 @@ Error messages will vary depending on whether you are using Google Workspace or
 
 This update allows you to see the full lifecycle of a failed action. For instance, if an administrator tries to move an email that has already been deleted or moved manually, the log will now show the multiple retry attempts and the specific destination error.
 
-This applies to all Email Security packages:
-
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
index fdf3bbd3fac9920..2b9c5533289c542 100644
--- a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
+++ b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
@@ -6,17 +6,17 @@ date: 2026-02-02T11:05:33Z
 
 We have updated the Monitoring page to provide a more streamlined and insightful experience for administrators, improving both data visualization and dashboard accessibility.
 
-- **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis.
-  ![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
-- **Improved Accessibility & Usability**:
-  _ **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation.
-  _ **Actionable UI**: All available actions are now accessible via dedicated buttons. \* **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions.
-  ![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
-- **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
-  ![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
+* **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis. 
+![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
+* **Improved Accessibility & Usability**: 
+    * **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation. 
+    * **Actionable UI**: All available actions are now accessible via dedicated buttons. 
+    * **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions. 
+![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
+* **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
+![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
 
-This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Advantage** 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
index 40ee34a930aa4d0..6d9695bd7a66d3e 100644
--- a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
+++ b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
@@ -10,12 +10,12 @@ In the dashboard, infinite paging is now supported in the Investigations view. T
 
 For high-volume use cases, we recommend:
 
-- **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
-- **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
-- **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
+-   **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
+-   **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
+-   **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
 
 This applies to all Email Security packages:
 
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+-   **Advantage**
+-   **Enterprise**
+-   **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
index cf4ab36e568d60c..a69648a508bacbf 100644
--- a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
@@ -3,14 +3,12 @@ title: DANE Support for MX Deployments
 description: DNSSEC-backed TLSA records now available on regional MX hostnames for verified encrypted email delivery
 date: 2026-04-06T09:00:00Z
 ---
-
 Cloudflare Email Security now supports DANE (DNS-based Authentication of Named Entities) for MX deployments. This enhancement strengthens email transport security by enabling DNSSEC-backed certificate verification for our regional MX records.
 
-- Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
-- DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
+* Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
+* DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
 
 This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+-   **Advantage**
+-   **Enterprise**
+-   **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
index eab1731927d760e..3019f6e986513d4 100644
--- a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
@@ -5,14 +5,12 @@ date: 2026-04-07 09:00:00 UTC
 ---
 
 Cloudflare Email security now supports **Triage Status Tracking for User Submissions**. This enhancement gives SOC teams a streamlined way to track, manage, and prioritize user-submitted emails directly within the Cloudflare One dashboard.
-
 - The User Submissions table now includes a **Status** column with three states: **Unreviewed** (new submissions awaiting triage), **Reviewed** (submissions assessed by the SOC team), and **Escalated** (submissions escalated to team submissions for further investigation). Analysts can quickly update statuses and filter the table to focus on what needs attention.
 - SOC teams can now organize their triage workflows, avoid duplicate reviews, and make sure critical threats get escalated for deeper investigation—bringing order to the chaos of high-volume submission management.
 
 Triage Status Tracking is **automatically available** for all Email security customers using the user submissions feature. No additional configuration is required; customers just need to make sure user submissions are being sent to their user submission aliases.
 
 This applies to all Email security packages:
-
 - **Advantage**
 - **Enterprise**
 - **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
index 8447a0ad8b9c7aa..558c35e1449d8c7 100644
--- a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
+++ b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
@@ -3,7 +3,6 @@ title: Cloudy Summaries in PhishNet O365
 description: Cloudy email summaries are now available in PhishNet for Office 365 environments.
 date: 2026-05-06T18:15:13Z
 ---
-
 PhishNet users can now access **Cloudy summaries** directly within the email investigation experience. When reviewing a message in PhishNet, users will see an AI-generated summary that provides additional context and key details about the email.
 
 These summaries help users quickly understand the nature of a message without needing to manually parse through headers, body content, and detection signals. Cloudy surfaces the most relevant information so users can make faster, more informed decisions about suspicious emails.
diff --git a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
index 55a9de27459f439..a5377b7e567f220 100644
--- a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
+++ b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
@@ -14,11 +14,11 @@ We're announcing the GA of **User Groups for Cloudflare Dashboard** and **System
 
 **SCIM User Groups [GA]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.
 
-**Stability & Scale**:
+**Stability & Scale**: 
 These features have undergone extensive testing during the Public Beta period and are now ready for production use across enterprises of all sizes.
 
 :::note
-SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
+SCIM Virtual Groups  (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
 :::
 
 For more info:
diff --git a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
index 3bf99528e750d6f..78ffc7cb93ea799 100644
--- a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
+++ b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
@@ -1,38 +1,31 @@
 ---
 title: Introducing new headers for rate limiting on Cloudflare's API
-description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code.
+description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code. 
 products:
   - fundamentals
 date: 2025-09-03
 ---
+Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available. 
 
-Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available.
+Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this. 
 
-Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this.
-
-As always, if you need any help with rate limits, please contact Support.
+As always, if you need any help with rate limits, please contact Support. 
 
 ### Changes
-
 #### New Headers
 
 **Headers that are always returned:**
-
 - `Ratelimit`: List of service limit items, composed of the limit name, the remaining quota (`r`) and the time next window resets (`t`). For example: `"default";r=50;t=30`
 - `Ratelimit-Policy`: List of quota policy items, composed of the policy name, the total quota (`q`) and the time window the quota applies to (`w`). For example: `"burst";q=100;w=60`
 
 **Returned only when a rate limit has been reached (error code: 429):**
-
 - Retry-After: Number of Seconds until more capacity is available, rounded up
 
 #### SDK Back offs
-
-- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached.
+- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached. 
 
 ### GraphQL and Edge APIs
-
-These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL.
+These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL. 
 
 ### For more information
-
-- [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
+* [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
diff --git a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
index 2d4cd4c94696926..f3c21ce51683451 100644
--- a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
+++ b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
@@ -6,8 +6,7 @@ products:
 date: 2025-09-08
 ---
 
-Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future.
+Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future. 
 
 ## For more information
-
 - [Two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
index 7132df4e0c21e5a..7cdd79523b47438 100644
--- a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
+++ b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
@@ -6,8 +6,7 @@ products:
 date: 2025-09-25
 ---
 
-Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address.
+Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address. 
 
 ## For more information
-
 - [Log in to Cloudflare](/fundamentals/user-profiles/login/)
diff --git a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
index a55ff67b07c1c01..ef6b79ccba485df 100644
--- a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
+++ b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
@@ -12,4 +12,4 @@ Users can now specify that they want to retrieve Cloudflare documentation as mar
 curl https://developers.cloudflare.com/workers/ -H 'Accept: text/markdown'  -v
 ```
 
-If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
+If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
index 4d7ebf5cd529a99..c9763acda83fa9f 100644
--- a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
+++ b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
@@ -15,3 +15,4 @@ Today, we are launching a new user experience which allows users to manage their
 ## For more information
 
 - [Cloudflare dashboard SSO](/fundamentals/manage-members/dashboard-sso/)
+
diff --git a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
index 07fdea6b5a065fe..206794e93f44faa 100644
--- a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
@@ -4,15 +4,15 @@ description: Cloudflare now offers email two-factor authentication to protect yo
 date: 2025-10-30
 ---
 
-Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support.
+Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support. 
 
-Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already.
+Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already. 
 
 You can now enable email 2FA on the Cloudflare dashboard:
 
 1. Go to **Profile** at the top right corner.
 2. Select **Authentication**.
-3. Under **Two-Factor Authentication**, select **Set up**.
+3. Under **Two-Factor Authentication**, select **Set up**.  
 
 ## Sign-in security best practices
 
diff --git a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
index 612e193af27fb2f..b8e0027220e35a2 100644
--- a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
@@ -1,5 +1,5 @@
 ---
-title: Revamped Member Management UI
+title: Revamped Member Management UI 
 description: Simplifying the management of users, groups, and permissions within Cloudflare.
 products:
   - fundamentals
@@ -8,6 +8,7 @@ date: 2025-10-30
 
 As Cloudflare's platform has grown, so has the need for precise, role-based access control. We’ve redesigned the Member Management experience in the Dashboard to help administrators more easily discover, assign, and refine permissions for specific principals.
 
+
 ### What's New
 
 **Refreshed member invite flow**
@@ -16,10 +17,10 @@ We overhauled the Invite Members UI to simplify inviting users and assigning per
 
 ![Updated Invite Flow UX](~/assets/images/changelog/fundamentals/2025-10-30-invite-experience.gif)
 
-**Refreshed Members Overview Page**
 
+**Refreshed Members Overview Page**
+ 
 We've updated the Members Overview Page to clearly display:
-
 - Member 2FA status
 - Which members hold Super Admin privileges
 - API access settings per member
@@ -29,11 +30,12 @@ We've updated the Members Overview Page to clearly display:
 
 **New Member Permission Policies Details View**
 
-We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have.
+We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have. 
 
 ![Updated Permission Policies Details Screen](~/assets/images/changelog/fundamentals/2025-10-30-permission-policies-screen.gif)
 
-**Improved Member Permission Workflow**
+
+**Improved Member Permission Workflow** 
 
 We redesigned the permission management experience to make it faster and easier for administrators to review roles and grant access.
 
@@ -41,4 +43,4 @@ We redesigned the permission management experience to make it faster and easier
 
 **Account-scoped Policies Restrictions Relaxed**
 
-Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions.
+Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions. 
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
index c83d90c5c82e0db..4809af309b7fae0 100644
--- a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
+++ b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
@@ -6,10 +6,9 @@ date: 2026-01-23
 
 ![Screenshot of new 2FA enrollment experience](~/assets/images/changelog/fundamentals/2026-01-23-2fa-interstitial.png)
 
-In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers.
+In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers. 
 
-We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works.
+We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works. 
 
-## For more information
-
-- [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
+## For more information 
+* [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
diff --git a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
index 0bd7606af0188e8..e00305d994595e1 100644
--- a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
+++ b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
@@ -8,6 +8,7 @@ date: 2026-02-12
 
 Cloudflare's network now supports real-time content conversion at the source, for enabled zones using [content negotiation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation) headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for `text/markdown` in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
 
+
 Here is a curl example with the `Accept` negotiation header requesting this page from our developer documentation:
 
 ```bash
@@ -38,4 +39,4 @@ ultimately resulting in better results while minimizing token waste.
 ...
 ```
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
index 69a7003183ac4a6..33a3ae22e6230f3 100644
--- a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
+++ b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
@@ -16,4 +16,4 @@ This release adds the following improvements:
 
 If you haven’t enabled automatic Markdown conversion yet, visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section of the Cloudflare dashboard and enable **Markdown for Agents**.
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
index 5ba8aed4decf5c8..e6ad76ed4ec43a0 100644
--- a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
@@ -57,6 +57,5 @@ curl -s --compressed -H "Accept: application/problem+json" -A "TestAgent/1.0" -H
 ```
 
 References:
-
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
index 7635eb13215cd99..aa790c1bc84902b 100644
--- a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
@@ -12,15 +12,15 @@ Cloudflare-generated 1xxx error responses now include a standard `Retry-After` H
 
 Seven retryable error codes now emit `Retry-After`:
 
-| Error code | Retry-After (seconds) | Error name                  |
-| ---------- | --------------------- | --------------------------- |
-| 1004       | 120                   | DNS resolution error        |
-| 1005       | 120                   | Banned zone                 |
-| 1015       | 30                    | Rate limited                |
-| 1033       | 120                   | Argo Tunnel error           |
-| 1038       | 60                    | HTTP headers limit exceeded |
-| 1200       | 60                    | Cache connection limit      |
-| 1205       | 5                     | Too many redirects          |
+| Error code | Retry-After (seconds) | Error name |
+|---|---|---|
+| 1004 | 120 | DNS resolution error |
+| 1005 | 120 | Banned zone |
+| 1015 | 30 | Rate limited |
+| 1033 | 120 | Argo Tunnel error |
+| 1038 | 60 | HTTP headers limit exceeded |
+| 1200 | 60 | Cache connection limit |
+| 1205 | 5 | Too many redirects |
 
 The header value matches the existing `retry_after` body field in JSON and Markdown responses.
 
@@ -39,6 +39,5 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
-
 - [RFC 9110 section 10.2.3 - Retry-After](https://www.rfc-editor.org/rfc/rfc9110#section-10.2.3)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
index c0c1a7659fedd48..92f5a45e27a8c57 100644
--- a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
+++ b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-18
 ---
 
-Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers.
+Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers. 
 
 Customers can now sync users and group information from Authentik to Cloudflare, apply Permission Policies to those groups, and manage the lifecycle of users & groups directly from your Authentik Identity Provider.
 
diff --git a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
index 48fa5bd55c357ee..115c15516aecbda 100644
--- a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
+++ b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
@@ -17,9 +17,9 @@ Cloudflare dashboard SCIM provisioning operations are now captured in [Audit Log
 | Create SCIM User  | User provisioned from IdP               |
 | Replace SCIM User | User fully replaced (PUT)               |
 | Update SCIM User  | User attributes modified (PATCH)        |
-| Delete SCIM User  | Member deprovisioned                    |
+| Delete SCIM User  | Member deprovisioned                      |
 | Create SCIM Group | Group provisioned from IdP              |
 | Update SCIM Group | Group membership or attributes modified |
-| Delete SCIM Group | Group deprovisioned                     |
+| Delete SCIM Group | Group deprovisioned                           |
 
 For more details, refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/).
diff --git a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
index 99e5c7faac36b0e..66f075b8044732c 100644
--- a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
+++ b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
@@ -18,7 +18,7 @@ We're announcing the public beta of **Organizations** for enterprise customers,
 
 **Centralized Account Management**: At launch, every Organization member has the Organization Super Admin role. Organization Super Admins can invite other users and manage any child account under the Organization implicitly.
 **Shared policies**: Share [WAF](/waf/custom-rules/) or [Gateway](/cloudflare-one/traffic-policies/tiered-policies/organizations/) policies across multiple accounts within your Organization to simplify centralized policy management.
-**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year.
+**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year. 
 
 **Unified analytics**: View, filter, and download aggregate HTTP analytics across all Organization child accounts from a single dashboard for centralized visibility into traffic patterns and security events.
 
diff --git a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
index 6df437b0b5fe8f2..4fb052b1583582b 100644
--- a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
+++ b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
@@ -1,6 +1,6 @@
 ---
 title: API tokens now detectable by secret scanning tools
-description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code.
+description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code. 
 date: 2026-04-10
 ---
 
diff --git a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
index b21e3e867f40139..ea662602678945a 100644
--- a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
+++ b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
@@ -5,45 +5,29 @@ products:
   - fundamentals
 date: 2026-04-14
 ---
-
 OAuth allows third-party applications to access your Cloudflare account on your behalf — like when Wrangler deploys Workers or when monitoring tools read your analytics. You now have **granular control** over which accounts these applications can access, plus the ability to revoke access anytime.
-
 ## What's new
-
 ### Choose which accounts to authorize
-
 When authorizing an OAuth application, you can now **select specific accounts** instead of granting access to all your accounts:
-
 - **Account-by-account selection** — Choose exactly which accounts the application can access
 - **"All accounts" option** — Still available for trusted tools like Wrangler
-  This gives you precise control who can access your data.
-
+This gives you precise control who can access your data.
 ### Clear consent screens
-
 The OAuth consent screen now shows:
-
 - **What the application can access** — Explicit list of permissions being requested
-- **Who created the application** — Application owner and contact information
+- **Who created the application** — Application owner and contact information  
 - **Which accounts you're authorizing** — Checkboxes for account selection
-
 ### Revoke access anytime
-
 Manage authorized OAuth applications from your profile:
-
 - **See all connected apps** — View every OAuth application with access to your accounts
 - **Review permissions and scope** — Check what each application can do and which accounts it can access
 - **Revoke instantly** — Remove access with one click when you no longer need it
-  To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
-
+To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
 ## Why this matters
-
 These updates give you:
-
 - **Granular control** — Authorize apps per-account instead of all-or-nothing
 - **Transparency** — Know exactly what you're authorizing before you consent
 - **Security** — Limit blast radius by restricting access to only necessary accounts
 - **Easy cleanup** — Revoke access when applications are no longer needed
-
 ## Learn more
-
 Read more about these improvements in our blog post: [Improving the OAuth consent experience](https://blog.cloudflare.com/improved-developer-security/#improving-the-oauth-consent-experience).
diff --git a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
index 02073d22df3580c..0bd7547904452c2 100644
--- a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
@@ -50,6 +50,5 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
-
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 5xx error documentation](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
index 2babbbfb86081cd..521711f9c22d54b 100644
--- a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
+++ b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
@@ -11,34 +11,34 @@ You can now navigate, switch context, and take common actions in the Cloudflare
 
 ## Navigate
 
-| Shortcut      | Action                                                 |
-| ------------- | ------------------------------------------------------ |
-| `g h`         | Go to Home                                             |
-| `g a`         | Go to account overview                                 |
-| `g z`         | Go to zone overview                                    |
-| `g p`         | Go to your profile                                     |
-| `g w`         | Go to Workers & Pages                                  |
-| `g o`         | Go to Zero Trust                                       |
-| `g b`         | Go to billing                                          |
+| Shortcut | Action |
+| --- | --- |
+| `g h` | Go to Home |
+| `g a` | Go to account overview |
+| `g z` | Go to zone overview |
+| `g p` | Go to your profile |
+| `g w` | Go to Workers & Pages |
+| `g o` | Go to Zero Trust |
+| `g b` | Go to billing |
 | `g 1` – `g 5` | Go to a recent or pinned item (by position in sidebar) |
-| `t →`         | Move to the next tab                                   |
-| `t ←`         | Move to the previous tab                               |
-| `p →`         | Move to the next page of a table                       |
-| `p ←`         | Move to the previous page of a table                   |
+| `t →` | Move to the next tab |
+| `t ←` | Move to the previous tab |
+| `p →` | Move to the next page of a table |
+| `p ←` | Move to the previous page of a table |
 
 ## Take action
 
-| Shortcut | Action                               |
-| -------- | ------------------------------------ |
-| `/`      | Open quick search                    |
-| `?`      | Show keyboard shortcuts              |
-| `s a`    | Switch account                       |
-| `s z`    | Switch zone                          |
-| `s .`    | Star or unstar the current zone      |
-| `p .`    | Pin or unpin the current page        |
-| `t s`    | Toggle the sidebar open or closed    |
-| `t m`    | Expand or collapse all sidebar menus |
-| `t a`    | Toggle Ask AI sidebar                |
-| `d .`    | Toggle dark mode                     |
-| `c u`    | Copy the current URL                 |
-| `c d`    | Copy a deep link URL                 |
+| Shortcut | Action |
+| --- | --- |
+| `/` | Open quick search |
+| `?` | Show keyboard shortcuts |
+| `s a` | Switch account |
+| `s z` | Switch zone |
+| `s .` | Star or unstar the current zone |
+| `p .` | Pin or unpin the current page |
+| `t s` | Toggle the sidebar open or closed |
+| `t m` | Expand or collapse all sidebar menus |
+| `t a` | Toggle Ask AI sidebar |
+| `d .` | Toggle dark mode |
+| `c u` | Copy the current URL |
+| `c d` | Copy a deep link URL |
diff --git a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
index ae01229a4717c46..6d777cba0965f65 100644
--- a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
+++ b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
@@ -7,9 +7,9 @@ hidden: false
 date: 2025-07-24
 ---
 
-[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more.
+[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more. 
 
-You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing _Inspect on all ports_.
+You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing  _Inspect on all ports_.
 
 ![HTTP Inspection on all ports setting](~/assets/images/gateway/Gateway-Inspection-all-ports.png)
 
diff --git a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
index 85d54d9085242a7..99deeee7c9cf019 100644
--- a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
+++ b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
@@ -3,13 +3,15 @@ title: Scam domain category introduced under Security Threats
 description: You can now create policies specifically targeting the Scam content
 date: 2025-07-28
 ---
-
+ 
 We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
-
+ 
 **New category added**
 
-| Parent ID | Parent Name      | Category ID | Category Name |
-| --------- | ---------------- | ----------- | ------------- |
-| 21        | Security Threats | 191         | Scam          |
+
+| Parent ID | Parent Name           | Category ID | Category Name                 |
+| --------- | --------------------- | ----------- | ----------------------------- |
+| 21        | Security Threats      | 191          | Scam                |
+
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
index e4f36b80ddf1cbf..295f092f251e8cc 100644
--- a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
+++ b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
@@ -3,9 +3,8 @@ title: Google Bard Application replaced by Gemini
 description: The Google Bard application has been fully replaced with Gemini
 date: 2025-07-22
 ---
-
 The **Google Bard** application (ID: 1198) has been deprecated and fully removed from the system. It has been replaced by the **Gemini** application (ID: 1340).
-Any existing Gateway policies that reference the old Google Bard application will no longer function.
+Any existing Gateway policies that reference the old Google Bard application will no longer function. 
 To ensure your policies continue to work as intended, you should update them to use the new Gemini application.
 We recommend replacing all instances of the deprecated Bard application with the new Gemini application in your Gateway policies.
 For more information about application policies, please see the [Cloudflare Gateway documentation](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
index 450c765b4b0e122..0583881ed95d8cb 100644
--- a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
+++ b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
@@ -8,10 +8,10 @@ We have added three new domain categories under the Technology parent category,
 
 **New categories added**
 
-| Parent ID | Parent Name | Category ID | Category Name       |
-| --------- | ----------- | ----------- | ------------------- |
-| 26        | Technology  | 194         | Keep Awake Software |
-| 26        | Technology  | 192         | Remote Access       |
-| 26        | Technology  | 193         | Shareware/Freeware  |
+| Parent ID | Parent Name           | Category ID | Category Name                 |
+| --------- | --------------------- | ----------- | ----------------------------- |
+| 26        | Technology            | 194         | Keep Awake Software           |
+| 26        | Technology            | 192         | Remote Access                 |
+| 26        | Technology            | 193         | Shareware/Freeware            |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
index 0d4496f7a95d1af..6ae683bd7093044 100644
--- a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
+++ b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
@@ -4,15 +4,14 @@ description: We are preparing to remap some existing applications to better refl
 date: 2025-11-06
 ---
 
-We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28).
+We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28). 
 While the new categories are live now, we want to ensure you have ample time to review and adjust any existing rules you have configured against old categories.
 The remapping of existing applications into these new categories will be completed by January 30, 2026.
 This timeline allows you a dedicated period to:
-
 - Review the new category structure.
 - Identify any policies you have that target the older categories.
 - Adjust your rules to reference the new, more precise categories before the old mappings change.
-  Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
+Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
 
 **Applications being remappedd**
 | Application Name | Existing Category | New Category |
@@ -77,4 +76,5 @@ This timeline allows you a dedicated period to:
 | DHL Express | Shopping | Business |
 | UPS | Shopping | Business |
 
+
 For more information on creating HTTP policies, refer to [Applications and app types](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
index 25d0dbe1436d1fa..f20f7a3b16f224a 100644
--- a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
+++ b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
@@ -10,13 +10,13 @@ Gateway [Protocol Detection](/cloudflare-one/traffic-policies/network-policies/p
 
 | Protocol     | Notes                                              |
 | ------------ | -------------------------------------------------- |
-| IMAP         | Internet Message Access Protocol — email retrieval |
-| POP3         | Post Office Protocol v3 — email retrieval          |
-| SMTP         | Simple Mail Transfer Protocol — email sending      |
-| MYSQL        | MySQL database wire protocol                       |
-| RSYNC-DAEMON | rsync daemon protocol                              |
-| LDAP         | Lightweight Directory Access Protocol              |
-| NTP          | Network Time Protocol                              |
+| IMAP         | Internet Message Access Protocol — email retrieval  |
+| POP3         | Post Office Protocol v3 — email retrieval           |
+| SMTP         | Simple Mail Transfer Protocol — email sending       |
+| MYSQL        | MySQL database wire protocol                        |
+| RSYNC-DAEMON | rsync daemon protocol                               |
+| LDAP         | Lightweight Directory Access Protocol               |
+| NTP          | Network Time Protocol                               |
 
 These protocols join the existing set of detected protocols (HTTP, HTTP2, SSH, TLS, DCERPC, MQTT, and TPKT) and can be used with the _Detected Protocol_ selector in [Network policies](/cloudflare-one/traffic-policies/network-policies/) to identify and filter traffic based on the application-layer protocol, without relying on port-based identification.
 
diff --git a/src/content/changelog/gateway/Gateway-application-categories-added.mdx b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
index 2f049a7fb324a63..ec9c5e87eb92aa4 100644
--- a/src/content/changelog/gateway/Gateway-application-categories-added.mdx
+++ b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
@@ -4,7 +4,7 @@ description: Manage outbound traffic with more granular application categories
 date: 2025-10-28
 ---
 
-To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product.
+To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product. 
 
 We have added the following categories to provide more precise organization and allow for finer-grained policy creation, designed around how users interact with different types of applications:
 
@@ -18,7 +18,7 @@ We have added the following categories to provide more precise organization and
 - Photography & Graphic Design
 - Travel
 
-The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories.
+The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories. 
 
 The full remapping will be completed by January 30, 2026.
 
diff --git a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
index 05c67dbc7fb82e7..3266a97d34dcdcb 100644
--- a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
+++ b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
@@ -13,13 +13,13 @@ The `localConnectionString` field and `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_ST
 
 ```jsonc
 {
-	"hyperdrive": [
-		{
-			"binding": "HYPERDRIVE",
-			"id": "your-hyperdrive-id",
-			"localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require",
-		},
-	],
+  "hyperdrive": [
+    {
+      "binding": "HYPERDRIVE",
+      "id": "your-hyperdrive-id",
+      "localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require"
+    }
+  ]
 }
 ```
 
diff --git a/src/content/changelog/images/heic-support.mdx b/src/content/changelog/images/heic-support.mdx
index 3baf6ce9372089c..8e5f655340c4c12 100644
--- a/src/content/changelog/images/heic-support.mdx
+++ b/src/content/changelog/images/heic-support.mdx
@@ -3,7 +3,6 @@ title: HEIC support in Cloudflare Images
 description: You can use Images to ingest HEIC images
 date: 2025-07-08
 ---
-
 You can use Images to ingest HEIC images and serve them in supported output formats like AVIF, WebP, JPEG, and PNG.
 
 When inputting a HEIC image, dimension and sizing limits may still apply. Refer to our documentation to see limits for [uploading to Images](/images/storage/upload-images/methods/) or [transforming a remote image](/images/optimization/transformations/overview/).
diff --git a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
index 6cf9d6cc44b1683..8124fd2d6475783 100644
--- a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
+++ b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
@@ -16,3 +16,5 @@ The new hybrid architecture delivers substantial latency reductions throughout E
 
 - **p95 latency**: Reduced from ~150ms to ~50ms (67% decrease)
 - **p99 latency**: Reduced from ~350ms to ~250ms (29% decrease)
+
+
diff --git a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
index d1a8fedd27fa065..41b68f6e7a4c23d 100644
--- a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
+++ b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
@@ -5,7 +5,6 @@ date: 2025-06-04
 ---
 
 We've made two large changes to load balancing:
-
 - Redesigned the user interface, now centralized at the **account level**.
 - Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot.
 
@@ -16,11 +15,13 @@ This update streamlines how you manage load balancers across multiple zones and
 **Key Enhancements:**
 
 - **Account-Level UI Consolidation:**
+
   - **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level.
 
   - **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution.
 
 - **Private Network Load Balancing:**
+
   - **Secure Internal Application Access:** Create [**Private Load Balancers**](/load-balancing/private-network/) to distribute traffic to applications hosted within your private network, ensuring they are not exposed to the public Internet.
 
   - **WARP & Magic WAN Integration:** Effortlessly direct internal traffic from users connected via Cloudflare WARP or through your Magic WAN infrastructure to the appropriate internal endpoint pools.
diff --git a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
index 62de99fae3dc892..3a0234e53c4e96e 100644
--- a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
+++ b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
@@ -6,4 +6,4 @@ date: 2025-07-09
 
 [Log Explorer](/log-explorer/) customers can now monitor their data ingestion volume to keep track of their billing. Monthly usage is displayed at the top of the [Log Search](/log-explorer/log-search/) and [Manage Datasets](/log-explorer/manage-datasets/) screens in Log Explorer.
 
-![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
+![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
index c384730c331df3f..02585abcdaa5285 100644
--- a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
+++ b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
@@ -6,4 +6,4 @@ date: 2025-08-15
 
 Customers can now rely on Log Explorer to meet their log retention compliance requirements.
 
-Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
+Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
index bd9895c6bf2de02..c1d5c1454d91cdf 100644
--- a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
+++ b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
@@ -11,3 +11,5 @@ Create a custom field to log desired header or cookie values into the `http_requ
 ![Edit Custom fields](src/assets/images/changelog/log-explorer/edit-custom-fields.png)
 
 For more details, refer to [Headers and cookies](/log-explorer/log-search/#headers-and-cookies).
+
+
diff --git a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
index a75aa1ccc71be40..794a2ac99ef2c6c 100644
--- a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
@@ -4,7 +4,7 @@ description: Log Search now lets you pivot directly to related Cloudflare tools
 date: 2025-09-11
 ---
 
-Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation.
+Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation. 
 
 From the `http_requests` or `fw_events` dataset results, right click on an IP Address or JA3 Fingerprint to pivot to the Investigate portal to lookup the reputation of an IP address or JA3 fingerprint.
 
@@ -14,6 +14,6 @@ Easily learn about error codes by linking directly to our documentation from the
 
 ![View documentation](src/assets/images/changelog/log-explorer/view-documentation.png)
 
-From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy.
+From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy. 
 
 ![View policy](src/assets/images/changelog/log-explorer/policyid.png)
diff --git a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
index 9747dcb5ea70714..915ab5b7a8c0a8a 100644
--- a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
@@ -9,6 +9,6 @@ The results table view of **Log Search** has been updated with additional functi
 - Remove/add columns.
 - Resize columns.
 - Sort columns.
-- Copy values from any field.
+- Copy values from any field. 
 
-![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
+![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
index 7fc5df7c52c3f95..8a5f4b9954eb85f 100644
--- a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
+++ b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
@@ -6,4 +6,4 @@ date: 2025-11-04
 
 We're excited to announce that Log Explorer users can now cancel queries that are currently running.
 
-This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
+This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
index 4abf8c6cf36fdee..6808c2b7ad9372e 100644
--- a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
+++ b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
@@ -8,4 +8,4 @@ We're excited to announce a quality-of-life improvement for Log Explorer users.
 
 Previously, if you were writing a long custom SQL query, the fixed-size window required excessive scrolling to view the full query. This update allows you to easily drag the bottom edge of the query window to make it taller. This means you can view your entire custom query at once, improving the efficiency and experience of writing and debugging complex queries.
 
-To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
+To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
index 20d9cb72a336e55..012bc9566a75154 100644
--- a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
@@ -6,4 +6,4 @@ date: 2025-11-13
 
 We've resolved a bug in Log Explorer that caused inconsistencies between the custom SQL date field filters and the date picker dropdown. Previously, users attempting to filter logs based on a custom date field via a SQL query sometimes encountered unexpected results or mismatching dates when using the interactive date picker.
 
-This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
+This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
index b3d870198ed0514..eaa4f6d50ecf078 100644
--- a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
@@ -18,6 +18,7 @@ The newly supported datasets include:
 - `Spectrum_events`
 - `Zaraz_events`
 
+
 ## Account Level
 
 - `Audit Logs`
@@ -30,8 +31,9 @@ The newly supported datasets include:
 - `Sinkhole HTTP`
 - `ipsec_logs`
 
+
 :::note
-`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying.
+`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying. 
 
 The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` role for querying.
 :::
@@ -41,3 +43,4 @@ The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` ro
 You can now use Log Explorer to query and filter with each of these datasets. For example, you can identify an IP address exhibiting suspicious behavior in the `FW_event` logs, and then instantly pivot to the `Network Analytics` logs or `Access` logs to see its network-level traffic profile or if it bypassed a corporate policy.
 
 To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/) and the [Cloudflare Logs documentation](/logs/).
+
diff --git a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
index 866a7fd1ae4efd5..305f5dc7bb195af 100644
--- a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
+++ b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
@@ -21,16 +21,16 @@ When configuring a dataset via the dashboard or API, you can define a specific s
 
 ```json
 {
-	"dataset": "firewall_events",
-	"enabled": true,
-	"fields": [
-		"Timestamp",
-		"ClientRequestHost",
-		"ClientIP",
-		"Action",
-		"EdgeResponseStatus",
-		"OriginResponseStatus"
-	]
+  "dataset": "firewall_events",
+  "enabled": true,
+  "fields": [
+    "Timestamp",
+    "ClientRequestHost",
+    "ClientIP",
+    "Action",
+    "EdgeResponseStatus",
+    "OriginResponseStatus"
+  ]
 }
 ```
 
diff --git a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
index 67a64c6fcf983b4..5c89e845304dd52 100644
--- a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
+++ b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
@@ -8,4 +8,4 @@ Cloudflare has introduced new fields to two Gateway-related datasets in Cloudfla
 
 - **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
 
-- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
+- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
\ No newline at end of file
diff --git a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
index e21ad4b2e7c9787..05e75fb1d124a1b 100644
--- a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
+++ b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
@@ -24,3 +24,4 @@ Cloudflare has added new fields across multiple [Logpush datasets](/logs/logpush
 - **Zero Trust Network Session Logs**: `SNI`.
 
 For the complete field definitions for each dataset, refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/).
+
diff --git a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
index f5a502289149705..0bcd5c49fa1c601 100644
--- a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
+++ b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
@@ -31,4 +31,4 @@ Pipelines SQL supports string functions, regex, hashing, JSON extraction, timest
 
 ## Get started
 
-To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
+To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
\ No newline at end of file
diff --git a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
index 322bbb2f1f6d38d..451556a3ef70408 100644
--- a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
+++ b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
@@ -7,15 +7,13 @@ date: 2026-04-21
 When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request. With subrequest merging enabled, subrequest data is embedded as a nested array field on the parent log record instead.
 
 ### What's new
-
 - New subrequest_merging field on Logpush jobs — Set "merge_subrequests": true when creating or updating an http_requests Logpush job to enable the feature.
 - New Subrequests log field — When subrequest merging is enabled, a Subrequests field (`array\<object\>`) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.
 
 ### Limitations
-
 - Applies to the http_requests (zone-scoped) dataset only.
 - A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.
 - Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.
 - Subrequests that do not qualify appear as separate log entries — no data is lost.
 - Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.
-- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
+- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
\ No newline at end of file
diff --git a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
index 3e32c36dcd09c10..7513b6b2b18466c 100644
--- a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
+++ b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
@@ -6,4 +6,4 @@ date: 2026-03-24
 
 The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** > **Interconnects**.
 
-Your existing configurations and functionality remain the same.
+Your existing configurations and functionality remain the same.
\ No newline at end of file
diff --git a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
index 5bbd423dd5f10bf..e11320f25ae558b 100644
--- a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
+++ b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
@@ -12,4 +12,4 @@ If you are creating a new Pages project, the new V3 build image that includes No
 
 Note that you can always specify a particular version of Node.js or other built-in dependencies by [setting an environment variable](/pages/configuration/build-image/#override-default-versions).
 
-For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
+For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
\ No newline at end of file
diff --git a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
index c3385ca2e92c7dd..21d1fa8ffb558fc 100644
--- a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
+++ b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
@@ -8,12 +8,11 @@ date: 2025-03-27 12:00:00 UTC
 
 [Queues](/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:
 
-- Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
-- You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
-- Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
+* Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
+* You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
+* Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
 
 To pause a queue using [Wrangler](/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.
-
 ```bash title="Pause and resume a queue"
 $ wrangler queues pause-delivery my-queue
 Pausing message delivery for queue my-queue.
@@ -25,7 +24,6 @@ Resumed message delivery for queue my-queue.
 ```
 
 Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:
-
 ```bash title="Purge a queue"
 $ wrangler queues purge my-queue
 ✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue
diff --git a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
index f3d5e6d4def673d..f8a980ffedaf040 100644
--- a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
+++ b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
@@ -11,16 +11,13 @@ date: 2025-04-17 12:00:00 UTC
 Pull consumers allow you to consume messages over HTTP from any environment—including outside of [Cloudflare Workers](/workers). They’re also useful when you need fine-grained control over how quickly messages are consumed.
 
 To setup a new queue with a pull based consumer using [Wrangler](/workers/wrangler/), run:
-
 ```sh title="Create a queue with a pull based consumer"
 npx wrangler queues create my-queue
 npx wrangler queues consumer http add my-queue
 ```
-
 You can also configure a pull consumer using the [REST API](/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.
 
 Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:
-
 ```bash title="Pull messages from a queue"
 curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" \
 --header "Authorization: Bearer ${API_TOKEN}" \
diff --git a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
index 7cec3511f215302..c7afb7767b23bb4 100644
--- a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
+++ b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
@@ -19,4 +19,4 @@ curl "https://api.cloudflare.com/client/v4/accounts/<account_id>/queues/<queue_i
 
 You can also use our [SDKs](/fundamentals/api/reference/sdks/) for TypeScript, Python, and Go.
 
-To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
+To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
\ No newline at end of file
diff --git a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
index 2ad33c340181762..cd3df4c25c12a32 100644
--- a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
+++ b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
@@ -22,21 +22,21 @@ An event is a structured record of something happening in your Cloudflare accoun
 
 ```json title="Example R2 bucket created event"
 {
-	"type": "cf.r2.bucket.created",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"location": "WNAM"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventTimestamp": "2025-07-28T10:30:00Z"
-	}
+  "type": "cf.r2.bucket.created",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "location": "WNAM"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventTimestamp": "2025-07-28T10:30:00Z"
+  }
 }
 ```
 
 Current [event sources](/queues/event-subscriptions/events-schemas/) include [R2](/r2/), [Workers KV](/kv/), [Workers AI](/workers-ai/), [Workers Builds](/workers/ci-cd/builds/), [Vectorize](/vectorize/), [Super Slurper](/r2/data-migration/super-slurper/), and [Workflows](/workflows/). More sources and events are on the way.
 
-For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
+For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
\ No newline at end of file
diff --git a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
index 965d8f2e1ebbc40..4e3338c452ffb31 100644
--- a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
+++ b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
@@ -7,7 +7,7 @@ products:
 hidden: false
 ---
 
-import { LinkCard } from "~/components";
+import { LinkCard} from "~/components";
 
 Today, we're launching the **open beta** for [R2 SQL](/r2-sql/): A serverless, distributed query engine that can efficiently analyze petabytes of data in [Apache Iceberg](https://iceberg.apache.org/) tables managed by [R2 Data Catalog](/r2/data-catalog).
 
diff --git a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
index 55b2b18066b5d26..6ebf2f9f66bcf2e 100644
--- a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
+++ b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
@@ -8,6 +8,7 @@ date: 2026-03-23
 
 [R2 SQL](/r2-sql/) now supports an expanded SQL grammar so you can write richer analytical queries without exporting data. This release adds CASE expressions, column aliases, arithmetic in clauses, 163 scalar functions, 33 aggregate functions, EXPLAIN, Common Table Expressions (CTEs),and full struct/array/map access. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying [Apache Iceberg](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](/r2/data-catalog/). This page documents the supported SQL syntax.
 
+
 ## Highlights
 
 - **Column aliases** — `SELECT col AS alias` now works in all clauses
diff --git a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
index 8be0bd3a266e62c..f6fc972ca48a3f5 100644
--- a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
+++ b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
@@ -20,7 +20,6 @@ SELECT
 FROM my_namespace.sales_data
 WHERE json_contains(doc, 'email')
 ```
-
 For a full list of available functions, refer to [JSON functions](/r2-sql/sql-reference/scalar-functions/#json-functions).
 
 `EXPLAIN FORMAT JSON` returns query execution plans as structured JSON for programmatic analysis and observability integrations:
@@ -67,7 +66,6 @@ npx wrangler r2 sql query "${WAREHOUSE}" "EXPLAIN FORMAT JSON SELECT * FROM logp
 │ }                                    │
 └──────────────────────────────────────┘
 ```
-
 For more details, refer to [EXPLAIN](/r2-sql/sql-reference/#explain).
 
 Unpartitioned Iceberg tables can now be queried directly, which is useful for smaller datasets or data without natural time dimensions. For tables with more than 1000 files, partitioning is still recommended for better performance.
diff --git a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
index 73516e563584422..3a0934b0df07041 100644
--- a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
+++ b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
@@ -35,4 +35,4 @@ For the `summary` and `timeseries_groups` endpoints, the following dimensions ar
 - `tld`: Top-level domain for DNS names found in certificates SANs
 - `validation_level`: [Validation level](https://www.cloudflare.com/learning/ssl/types-of-ssl-certificates/)
 
-Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
+Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
\ No newline at end of file
diff --git a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
index 702f6495af2db32..2204d6097ae38bf 100644
--- a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
+++ b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
@@ -18,4 +18,4 @@ All `summary` and `timeseries_groups` endpoints in [`HTTP`](/api/resources/radar
 
 A new filter `geoId` was also added to all endpoints in [`HTTP`](/api/resources/radar/subresources/http/) and [`NetFlows`](/api/resources/radar/subresources/netflows/), allowing filtering by a specific administrative division.
 
-Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
+Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
\ No newline at end of file
diff --git a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
index 1da325fa4aeeaef..3058add7fdc87a1 100644
--- a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
+++ b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
@@ -34,4 +34,4 @@ On AS routing pages, the connectivity table now includes checkmarks for ASPA-ver
 
 ![Screenshot of the ASPA changes timeline on an AS routing page](~/assets/images/radar/aspa-asn-timeline.png)
 
-Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
+Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
\ No newline at end of file
diff --git a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
index 190b32137ec4b34..b2c0e9bbf120e31 100644
--- a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
+++ b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
@@ -34,4 +34,4 @@ The [IP address space](https://radar.cloudflare.com/routing) chart now displays
 
 ![Screenshot of the IPv4 and IPv6 combined IP space chart](~/assets/images/radar/combined-ipv4-ipv6-space.png)
 
-Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
+Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
\ No newline at end of file
diff --git a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
deleted file mode 100644
index b8b628aa4258d7d..000000000000000
--- a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: RealtimeKit track recording for specific participant audio tracks
-description: You can now record specific participant audio tracks in RealtimeKit with the new track recording feature.
-products:
-  - realtime
-date: 2026-05-28
----
-
-You can now record specific participant audio tracks in RealtimeKit with the new [track recording](/realtime/realtimekit/recording-guide/track-recording/) feature. Track recording creates separate WebM files for each participant instead of one composite meeting recording, which is useful for post-processing, transcription, and regulated or content-sensitive workflows where you need speaker-level control over what you store.
-
-To record specific participants, pass `user_ids` when starting a track recording:
-
-```bash
-curl --request POST \
-  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
-  --header 'Authorization: Bearer <api_token>' \
-  --header 'Content-Type: application/json' \
-  --data '{
-  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
-  "user_ids": ["user-123", "user-456"]
-}'
-```
-
-If you do not provide `user_ids`, RealtimeKit records all participant audio tracks as separate WebM files by default.
-
-To use `user_ids` for selective track recording, upgrade to the following minimum SDK versions:
-
-- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
-- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
-- Android Core or iOS Core: version `2.0.0` or later
-- Android UI Kit or iOS UI Kit: version `1.1.0` or later
-
-RealtimeKit provides SDKs and UI components so that you can build your own meeting experience on [Cloudflare's global WebRTC infrastructure](/realtime/). Teams today build products ranging from telehealth to education companies on RealtimeKit for global audiences. You can get started today with the [RealtimeKit quickstart](/realtime/realtimekit/quickstart/) or take a look at the [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
-
-- [Track recording docs](/realtime/realtimekit/recording-guide/track-recording/)
-- [Recording overview](/realtime/realtimekit/recording-guide/)
diff --git a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
index 4bdd9ba554b4731..a57aa1f4b10d63e 100644
--- a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
+++ b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
@@ -10,7 +10,6 @@ Administrators can now automatically escalate the risk score of a user if their
 
 New risk behaviors
 The following risk scoring behaviors are now available:
-
 - CrowdStrike low device score: Automatically increases a user's risk score when the connected device reports a "Low" score from CrowdStrike.
 - CrowdStrike medium device score: Automatically increases a user's risk score when the connected device reports a "Medium" score from CrowdStrike.
 
diff --git a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
index 1ade4db9cf454f6..629804f5f46a6f4 100644
--- a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
+++ b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
@@ -12,10 +12,10 @@ Cloudflare now provides two new request fields in the Ruleset engine that let yo
 
 ### New fields
 
-| Field                            | Type    | Description                                                                                                                                                          |
-| -------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.edge.client_tcp`             | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC.                                                        |
-| `cf.timings.client_tcp_rtt_msec` | Number  | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
+| Field | Type | Description |
+| --- | --- | --- |
+| `cf.edge.client_tcp` | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC. |
+| `cf.timings.client_tcp_rtt_msec` | Number | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
 
 Example filter expression:
 
diff --git a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
index 21cdd6b6e931809..97bc5ce82abd556 100644
--- a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
+++ b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
@@ -10,8 +10,8 @@ You can use this field to build rules that target traffic based on geographic ma
 
 ### Field details
 
-| Field               | Type           | Description                                                                                                                   |
-| ------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `ip.src.metro_code` | String \| null | The metro code (DMA) of the incoming request's IP address. Returns the designated market area code for the client's location. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
index 598cf65b45365a7..9fa9ac345fef774 100644
--- a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
+++ b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
@@ -12,12 +12,12 @@ Cloudflare Rulesets now include new functions that enable advanced expression lo
 
 ### New functions
 
-| Function                   | Description                                                                   |
-| -------------------------- | ----------------------------------------------------------------------------- |
-| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter.       |
-| `join(array, delimiter)`   | Joins an array of strings into a single string using the specified delimiter. |
-| `has_key(map, key)`        | Returns `true` if the specified key exists in the map.                        |
-| `has_value(map, value)`    | Returns `true` if the specified value exists in the map.                      |
+| Function | Description |
+| --- | --- |
+| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter. |
+| `join(array, delimiter)` | Joins an array of strings into a single string using the specified delimiter. |
+| `has_key(map, key)` | Returns `true` if the specified key exists in the map. |
+| `has_value(map, value)` | Returns `true` if the specified value exists in the map. |
 
 ---
 
diff --git a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
index 5dcd031a6e4ba0b..9e980cd5968d3b0 100644
--- a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
+++ b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
@@ -10,20 +10,20 @@ You can now control how Cloudflare buffers HTTP request and response bodies usin
 
 Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:
 
-| Mode                   | Behavior                                                                                                      |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Mode | Behavior |
+| --- | --- |
 | **Standard** (default) | Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management. |
-| **Full**               | Buffers the entire request body before sending to origin.                                                     |
-| **None**               | No buffering — the request body streams directly to origin without inspection.                                |
+| **Full** | Buffers the entire request body before sending to origin. |
+| **None** | No buffering — the request body streams directly to origin without inspection. |
 
 ### Response body buffering
 
 Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:
 
-| Mode                   | Behavior                                                                            |
-| ---------------------- | ----------------------------------------------------------------------------------- |
-| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality.     |
-| **None**               | No buffering — the response body streams directly to the client without inspection. |
+| Mode | Behavior |
+| --- | --- |
+| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality. |
+| **None** | No buffering — the response body streams directly to the client without inspection. |
 
 :::caution
 Setting body buffering to **None** may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.
@@ -33,11 +33,11 @@ Setting body buffering to **None** may break security functionality that require
 
 ```json
 {
-	"action": "set_config",
-	"action_parameters": {
-		"request_body_buffering": "standard",
-		"response_body_buffering": "none"
-	}
+  "action": "set_config",
+  "action_parameters": {
+    "request_body_buffering": "standard",
+    "response_body_buffering": "none"
+  }
 }
 ```
 
diff --git a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
index 04fd03621cb1999..52e81f07114dcef 100644
--- a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
+++ b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
@@ -10,8 +10,8 @@ You can use this field to identify slow Worker executions, detect performance re
 
 ### Field details
 
-| Field                    | Type    | Description                                                                                         |
-| ------------------------ | ------- | --------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `cf.timings.worker_msec` | Integer | The time spent executing a Cloudflare Worker in milliseconds. Returns `0` if no Worker was invoked. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
index c2584a81e336dae..f2a0c12b6257543 100644
--- a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
@@ -43,6 +43,6 @@ You should ensure that `Client-Cert` and `Client-Cert-Chain` headers received by
 
 - **If you use WAF custom rules to block requests with invalid mTLS connections:** The transform rule is sufficient. For all requests that reach your origin server, the rule will overwrite any existing `Client-Cert` and `Client-Cert-Chain` headers.
 - **If you do not enforce mTLS at the WAF:** Add another transform rule that removes any incoming `Client-Cert` and `Client-Cert-Chain` headers from all requests (use expression `true`), ordered before the rule above. This ensures your origin server cannot receive client-supplied values for these HTTP headers.
-  :::
+:::
 
 For more information, refer to [Mutual TLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/), [Request Header Transform Rules](/rules/transform/request-header-modification/), and the [fields reference](/ruleset-engine/rules-language/fields/reference/).
diff --git a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
index 92228ab4dd7a5fd..2954caaf3ad34d3 100644
--- a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,10 +10,10 @@ Previously, QUIC RTT and delivery rate data was only available via the `Server-T
 
 ### New fields
 
-| Field                             | Type    | Description                                                                                                                                                               |
-| --------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `cf.timings.client_quic_rtt_msec` | Integer | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only populated for QUIC (HTTP/3) connections. Returns `0` for TCP connections. |
-| `cf.edge.l4.delivery_rate`        | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request.             |
+| `cf.edge.l4.delivery_rate` | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request. |
 
 ### Example: Route slow connections to a lightweight origin
 
@@ -27,9 +27,9 @@ cf.timings.client_tcp_rtt_msec > 200 or cf.timings.client_quic_rtt_msec > 200
 
 **Header modifications:**
 
-| Operation | Header name      | Value  |
-| --------- | ---------------- | ------ |
-| Set       | `X-High-Latency` | `true` |
+| Operation | Header name | Value |
+| --- | --- | --- |
+| Set | `X-High-Latency` | `true` |
 
 ### Example: Match low-bandwidth connections
 
diff --git a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
index 89121e503ad9af2..9ee69fcc0ccb9c9 100644
--- a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
@@ -21,7 +21,6 @@ Please ensure you read through the list of changes below before moving to this v
 ### Breaking Changes
 
 #### Addressing - Parameter Requirements Changed
-
 - `BGPPrefixCreateParams.cidr`: optional → **required**
 - `PrefixCreateParams.asn`: `number | null` → `number`
 - `PrefixCreateParams.loa_document_id`: required → **optional**
@@ -29,26 +28,21 @@ Please ensure you read through the list of changes below before moving to this v
 - `ServiceBindingCreateParams.service_id`: optional → **required**
 
 #### API Gateway
-
 - `ConfigurationUpdateResponse` removed
 - `PublicSchema` → `OldPublicSchema`
 - `SchemaUpload` → `UserSchemaCreateResponse`
 - `ConfigurationUpdateParams.properties` removed; use `normalize`
 
 #### CloudforceOne - Response Type Changes
-
 - `ThreatEventBulkCreateResponse`: `number` → complex object with counts and errors
 
 #### D1 Database - Query Parameters
-
 - `DatabaseQueryParams`: simple interface → union type (`D1SingleQuery | MultipleQueries`)
 - `DatabaseRawParams`: same change
 - Supports batch queries via `batch` array
 
 #### DNS Records - Type Renames (21 types)
-
 All record type interfaces renamed from `*Record` to short names:
-
 - `RecordResponse.ARecord` → `RecordResponse.A`
 - `RecordResponse.AAAARecord` → `RecordResponse.AAAA`
 - `RecordResponse.CNAMERecord` → `RecordResponse.CNAME`
@@ -72,64 +66,52 @@ All record type interfaces renamed from `*Record` to short names:
 - `RecordResponse.OpenpgpkeyRecord` → `RecordResponse.Openpgpkey`
 
 #### IAM Resource Groups
-
 - `ResourceGroupCreateResponse.scope`: optional single → **required array**
 - `ResourceGroupCreateResponse.id`: optional → **required**
 
 #### Origin CA Certificates - Parameter Requirements Changed
-
 - `OriginCACertificateCreateParams.csr`: optional → **required**
 - `OriginCACertificateCreateParams.hostnames`: optional → **required**
 - `OriginCACertificateCreateParams.request_type`: optional → **required**
 
 #### Pages
-
 - Renamed: `DeploymentsSinglePage` → `DeploymentListResponsesV4PagePaginationArray`
 - Domain response fields: many optional → **required**
 
 #### Pipelines - v0 to v1 Migration
-
 - Entire v0 API deprecated; use v1 methods (`createV1`, `listV1`, etc.)
 - New sub-resources: `Sinks`, `Streams`
 
 #### R2
-
 - `EventNotificationUpdateParams.rules`: optional → **required**
 - Super Slurper: `bucket`, `secret` now required in source params
 
 #### Radar
-
 - `dataSource`: `string` → typed enum (23 values)
 - `eventType`: `string` → typed enum (6 values)
 - V2 methods require `dimension` parameter (breaking signature change)
 
 #### Resource Sharing
-
 - Removed: `status_message` field from all recipient response types
 
 #### Schema Validation
-
 - Consolidated `SchemaCreateResponse`, `SchemaListResponse`, `SchemaEditResponse`, `SchemaGetResponse` → `PublicSchema`
 - Renamed: `SchemaListResponsesV4PagePaginationArray` → `PublicSchemasV4PagePaginationArray`
 
 #### Spectrum
-
 - Renamed union members: `AppListResponse.UnionMember0` → `SpectrumConfigAppConfig`
 - Renamed union members: `AppListResponse.UnionMember1` → `SpectrumConfigPaygoAppConfig`
 
 #### Workers
-
 - Removed: `WorkersBindingKindTailConsumer` type (all occurrences)
 - Renamed: `ScriptsSinglePage` → `ScriptListResponsesSinglePage`
 - Removed: `DeploymentsSinglePage`
 
 #### Zero-Trust DLP
-
 - `datasets.create()`, `update()`, `get()` return types changed
 - `PredefinedGetResponse` union members renamed to `UnionMember0-5`
 
 #### Zero-Trust Tunnels
-
 - Removed: `CloudflaredCreateResponse`, `CloudflaredListResponse`, `CloudflaredDeleteResponse`, `CloudflaredEditResponse`, `CloudflaredGetResponse`
 - Removed: `CloudflaredListResponsesV4PagePaginationArray`
 
@@ -138,30 +120,25 @@ All record type interfaces renamed from `*Record` to short names:
 ### Features
 
 #### Abuse Reports (`client.abuseReports`)
-
 - **Reports**: `create`, `list`, `get`
 - **Mitigations**: sub-resource for abuse mitigations
 
 #### AI Search (`client.aisearch`)
-
 - **Instances**: `create`, `update`, `list`, `delete`, `read`, `stats`
 - **Items**: `list`, `get`
 - **Jobs**: `create`, `list`, `get`, `logs`
 - **Tokens**: `create`, `update`, `list`, `delete`, `read`
 
 #### Connectivity (`client.connectivity`)
-
 - **Directory Services**: `create`, `update`, `list`, `delete`, `get`
 - Supports IPv4, IPv6, dual-stack, and hostname configurations
 
 #### Organizations (`client.organizations`)
-
 - **Organizations**: `create`, `update`, `list`, `delete`, `get`
 - **OrganizationProfile**: `update`, `get`
 - Hierarchical organization support with parent/child relationships
 
 #### R2 Data Catalog (`client.r2DataCatalog`)
-
 - **Catalog**: `list`, `enable`, `disable`, `get`
 - **Credentials**: `create`
 - **MaintenanceConfigs**: `update`, `get`
@@ -170,7 +147,6 @@ All record type interfaces renamed from `*Record` to short names:
 - Apache Iceberg integration
 
 #### Realtime Kit (`client.realtimeKit`)
-
 - **Apps**: `get`, `post`
 - **Meetings**: `create`, `get`, participant management
 - **Livestreams**: 10+ methods for streaming
@@ -181,66 +157,52 @@ All record type interfaces renamed from `*Record` to short names:
 - **Analytics**: organization analytics
 
 #### Token Validation (`client.tokenValidation`)
-
 - **Configuration**: `create`, `list`, `delete`, `edit`, `get`
 - **Credentials**: `update`
 - **Rules**: `create`, `list`, `delete`, `bulkCreate`, `bulkEdit`, `edit`, `get`
 - JWT validation with RS256/384/512, PS256/384/512, ES256, ES384
 
 #### Alerting Silences (`client.alerting.silences`)
-
 - `create`, `update`, `list`, `delete`, `get`
 
 #### IAM SSO (`client.iam.sso`)
-
 - `create`, `update`, `list`, `delete`, `get`, `beginVerification`
 
 #### Pipelines v1 (`client.pipelines`)
-
 - **Sinks**: `create`, `list`, `delete`, `get`
 - **Streams**: `create`, `update`, `list`, `delete`, `get`
 
 #### Zero-Trust AI Controls / MCP (`client.zeroTrust.access.aiControls.mcp`)
-
 - **Portals**: `create`, `update`, `list`, `delete`, `read`
 - **Servers**: `create`, `update`, `list`, `delete`, `read`, `sync`
 
 #### Accounts
-
 - `managed_by` field with `parent_org_id`, `parent_org_name`
 
 #### Addressing LOA Documents
-
 - `auto_generated` field on `LOADocumentCreateResponse`
 
 #### Addressing Prefixes
-
 - `delegate_loa_creation`, `irr_validation_state`, `ownership_validation_state`, `ownership_validation_token`, `rpki_validation_state`
 
 #### AI
-
 - Added `toMarkdown.supported()` method to get all supported conversion formats
 
 #### AI Gateway
-
 - `zdr` field added to all responses and params
 
 #### Alerting
-
 - New alert type: `abuse_report_alert`
 - `type` field added to PolicyFilter
 
 #### Browser Rendering
-
 - `ContentCreateParams`: refined to discriminated union (`Variant0 | Variant1`)
 - Split into URL-based and HTML-based parameter variants for better type safety
 
 #### Client Certificates
-
 - `reactivate` parameter in edit
 
 #### CloudforceOne
-
 - `ThreatEventCreateParams.indicatorType`: required → optional
 - `hasChildren` field added to all threat event response types
 - `datasetIds` query parameter on `AttackerListParams`, `CategoryListParams`, `TargetIndustryListParams`
@@ -251,69 +213,56 @@ All record type interfaces renamed from `*Record` to short names:
 - `createdAt`, `datasetId` fields on `ThreatEventEditParams`
 
 #### Content Scanning
-
 - Added `create()`, `update()`, `get()` methods
 
 #### Custom Pages
-
 - New page types: `basic_challenge`, `under_attack`, `waf_challenge`
 
 #### D1
-
 - `served_by_colo` - colo that handled query
 - `jurisdiction` - `'eu' | 'fedramp'`
 - **Time Travel** (`client.d1.database.timeTravel`): `getBookmark()`, `restore()` - point-in-time recovery
 
 #### Email Security
-
 - New fields on `InvestigateListResponse`/`InvestigateGetResponse`: `envelope_from`, `envelope_to`, `postfix_id_outbound`, `replyto`
 - New detection classification: `'outbound_ndr'`
 - Enhanced `Finding` interface with `attachment`, `detection`, `field`, `portion`, `reason`, `score`
 - Added `cursor` query parameter to `InvestigateListParams`
 
 #### Gateway Lists
-
 - New list types: `CATEGORY`, `LOCATION`, `DEVICE`
 
 #### Intel
-
 - New issue type: `'configuration_suggestion'`
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Leaked Credential Checks
-
 - Added `detections.get()` method
 
 #### Logpush
-
 - New datasets: `dex_application_tests`, `dex_device_state_events`, `ipsec_logs`, `warp_config_changes`, `warp_toggle_changes`
 
 #### Load Balancers
-
 - `Monitor.port`: `number` → `number | null`
 - `Pool.load_shedding`: `LoadShedding` → `LoadShedding | null`
 - `Pool.origin_steering`: `OriginSteering` → `OriginSteering | null`
 
 #### Magic Transit
-
 - `license_key` field on connectors
 - `provision_license` parameter for auto-provisioning
 - IPSec: `custom_remote_identities` with FQDN support
 - Snapshots: Bond interface, `probed_mtu` field
 
 #### Pages
-
 - New response types: `ProjectCreateResponse`, `ProjectListResponse`, `ProjectEditResponse`, `ProjectGetResponse`
 - Deployment methods return specific response types instead of generic `Deployment`
 
 #### Queues
-
 - Added `subscriptions.get()` method
 - Enhanced `SubscriptionGetResponse` with typed event source interfaces
 - New event source types: Images, KV, R2, Vectorize, Workers AI, Workers Builds, Workflows
 
 #### R2
-
 - Sippy: new provider `s3` (S3-compatible endpoints)
 - Sippy: `bucketUrl` field for S3-compatible sources
 - Super Slurper: `keys` field on source response schemas (specify specific keys to migrate)
@@ -321,41 +270,32 @@ All record type interfaces renamed from `*Record` to short names:
 - Super Slurper: `region` field on S3 source params
 
 #### Radar
-
 - Added `geolocations.list()`, `geolocations.get()` methods
 - Added V2 dimension-based methods (`summaryV2`, `timeseriesGroupsV2`) to radar sub-resources
 
 #### Resource Sharing
-
 - Added `terminal` boolean field to Resource Error interfaces
 
 #### Rules
-
 - Added `id` field to `ItemDeleteParams.Item`
 
 #### Rulesets
-
 - New buffering fields on `SetConfigRule`: `request_body_buffering`, `response_body_buffering`
 
 #### Secrets Store
-
 - New scopes: `'dex'`, `'access'` (in addition to `'workers'`, `'ai_gateway'`)
 
 #### SSL Certificate Packs
-
 - Response types now proper interfaces (was `unknown`)
 - Fields now required: `id`, `certificates`, `hosts`, `status`, `type`
 
 #### Security Center
-
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Shared Types
-
 - Added: `CloudflareTunnelsV4PagePaginationArray` pagination class
 
 #### Workers
-
 - Added `subdomains.delete()` method
 - `Worker.references` - track external dependencies (domains, Durable Objects, queues)
 - `Worker.startup_time_ms` - startup timing
@@ -366,44 +306,36 @@ All record type interfaces renamed from `*Record` to short names:
 - Telemetry: `traces` field, `$containers` event info, `durableObjectId`, `transactionName`, `abr_level` fields
 
 #### Workers for Platforms
-
 - `ScriptUpdateResponse`: new fields `entry_point`, `observability`, `tag`, `tags`
 - `placement` field now union of 4 variants (smart mode, region, hostname, host)
 - `tags`, `tail_consumers` now nullable
 - `TagUpdateParams.body` now accepts `null`
 
 #### Workflows
-
 - `instance_retention`: `unknown` → typed `InstanceRetention` interface with `error_retention`, `success_retention`
 - New status option: `'restart'` added to `StatusEditParams.status`
 
 #### Zero-Trust Devices
-
 - External emergency disconnect settings (4 new fields)
 - `antivirus` device posture check type
 - `os_version_extra` documentation improvements
 
 #### Zones
-
 - New response types: `SubscriptionCreateResponse`, `SubscriptionUpdateResponse`, `SubscriptionGetResponse`
 
 #### Zero-Trust Access Applications
-
 - New `ApplicationType` values: `'mcp'`, `'mcp_portal'`, `'proxy_endpoint'`
 - New destination type: `ViaMcpServerPortalDestination` for MCP server access
 
 #### Zero-Trust Gateway
-
 - Added `rules.listTenant()` method
 
 #### Zero-Trust Gateway - Proxy Endpoints
-
 - `ProxyEndpoint`: interface → discriminated union (`ZeroTrustGatewayProxyEndpointIP | ZeroTrustGatewayProxyEndpointIdentity`)
 - `ProxyEndpointCreateParams`: interface → union type
 - Added `kind` field: `'ip' | 'identity'`
 
 #### Zero-Trust Tunnels
-
 - `WARPConnector*Response`: union type → interface
 
 ---
@@ -439,4 +371,4 @@ All record type interfaces renamed from `*Record` to short names:
 - Added deprecation notices with migration paths
 - **api_gateway:** deprecate API Shield Schema Validation resources ([8a4b20f](https://github.com/cloudflare/cloudflare-typescript/commit/8a4b20f7a572422f74179fbdb4f1c4fb555e3e40))
 - Improved JSDoc examples across all resources
-- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
+- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
\ No newline at end of file
diff --git a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
index 7b6922947ee7f2c..4637fe2ecd6fe2e 100644
--- a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
@@ -98,57 +98,46 @@ will help you understand any down or upstream issues it may cause to your enviro
 ### New Endpoints (Existing Resources)
 
 #### `acm.totaltls`
-
 - `edit()`
 - `update()`
 
 #### `cloudforceone.threatevents`
-
 - `list()`
 
 #### `contentscanning`
-
 - `create()`
 - `get()`
 - `update()`
 
 #### `dns.records`
-
 - `scan_list()`
 - `scan_review()`
 - `scan_trigger()`
 
 #### `intel.indicatorfeeds`
-
 - `create()`
 - `delete()`
 - `list()`
 
 #### `leakedcredentialchecks.detections`
-
 - `get()`
 
 #### `queues.consumers`
-
 - `list()`
 
 #### `radar.ai`
-
 - `summary()`
 - `timeseries()`
 - `timeseries_groups()`
 
 #### `radar.bgp`
-
 - `changes()`
 - `snapshot()`
 
 #### `workers.subdomains`
-
 - `delete()`
 
 #### `zerotrust.networks`
-
 - `create()`
 - `delete()`
 - `edit()`
@@ -175,4 +164,4 @@ will help you understand any down or upstream issues it may cause to your enviro
 - **Discriminated unions**: Correctly handle nested discriminated unions in response parsing
 - **Extra field types**: Parse extra field types correctly
 - **Empty metadata**: Ignore empty metadata fields during parsing
-- **Singularization rules**: Update resource name singularization rules for better consistency
+- **Singularization rules**: Update resource name singularization rules for better consistency
\ No newline at end of file
diff --git a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
index 01d745a7853300f..80b92a2e38719b4 100644
--- a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
+++ b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
@@ -1,16 +1,16 @@
+
 ---
 title: New APIs for Brand Protection setup
 description: You can now use the Brand Protection API endpoints to manage your Brand Protection queries
 date: 2025-07-18
 ---
-
+ 
 The Brand Protection API is now available, allowing users to create new queries and delete existing ones, fetch matches and more!
-
+ 
 What you can do:
-
-- **create new string or logo query**
-- **delete string or logo queries**
-- **download matches for both logo and string queries**
-- **read matches for both logo and string queries**
+- **create new string or logo query** 
+- **delete string or logo queries** 
+- **download matches for both logo and string queries** 
+- **read matches for both logo and string queries** 
 
 Ready to start? Check out the [Brand Protection API](/api/resources/brand_protection/) in our documentation.
diff --git a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
index 58288565e961039..a8da24443aa2244 100644
--- a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
+++ b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
@@ -4,7 +4,7 @@ description: The Requests for Information (RFI) dashboard now shows the number o
 date: 2025-10-27
 ---
 
-The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted.
+The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted. 
 
 ![Cloudforce One RFI tokens](~/assets/images/changelog/security-center/2025-10-24RFITokens.png)
 
diff --git a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
index 07257c943d54312..5c14e85f93430d3 100644
--- a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
+++ b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
@@ -1,9 +1,9 @@
 ---
 title: Report logo misuse to Cloudflare directly from the Brand Protection dashboard
-description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network
+description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network 
 date: 2025-10-31
 ---
 
 The Brand Protection logo query dashboard now allows you to use the **Report to Cloudflare** button to submit an Abuse report directly from the Brand Protection logo queries dashboard. While you could previously report new domains that were impersonating your brand before, now you can do the same for websites found to be using your logo without your permission. The abuse reports will be prefilled and you will only need to validate a few fields before you can click the submit button, after which our team process your request.
 
-Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/).
+Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/). 
diff --git a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
index fcd53972aec849f..9f9d5dd72cde73f 100644
--- a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
+++ b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
@@ -4,7 +4,7 @@ description: Threat events users can now access threat insights curated by our t
 date: 2025-11-21
 ---
 
-The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity.
-Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.
+The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity. 
+Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.  
 
-For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events).
+For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events). 
diff --git a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
index f6b64dc1ba68722..1dad1d621eb3f74 100644
--- a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
+++ b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
@@ -9,13 +9,13 @@ This update streamlines how security analysts can share findings with stakeholde
 
 **Key Benefits:**
 
-- Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
-- Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
+* Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
+* Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
 
 **What’s new:**
 
-- **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
-- **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
+* **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
+* **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
 
 To get started with the URL Scanner and explore our reporting capabilities, visit the [URL Scanner API documentation](https://developers.cloudflare.com/api/resources/url_scanner/).
 
diff --git a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
index eff63f778930ece..e0dd22e2c84e189 100644
--- a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
+++ b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
@@ -3,7 +3,6 @@ title: Cloudforce One Threat events graphs are now visible in the dashboard
 description: Trace attack flows with Sankey diagrams and analyze dataset distribution over time
 date: 2026-02-19
 ---
-
 We have introduced dynamic visualizations to the Threat Events dashboard to help you better understand the threat landscape and identify emerging patterns at a glance.
 
 What's new:
diff --git a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
index 4a28f773e0eeeac..5260cc6ad7bf605 100644
--- a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
+++ b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
@@ -9,8 +9,7 @@ date: 2026-02-23
 ## Why this matters
 
 Threat intelligence is most effective when it is personalized. Previously, analysts had to manually re-apply complex filters (like combining specific industry datasets with geographic origins) every time they logged in. This update provides material value by:
-
-- Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
-- Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
+* Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
+* Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
 
 Cloudforce One subscribers can start saving their custom views now in [Application Security > Threat Intelligence > Threat Events](https://dash.cloudflare.com/?to=/:account/security-center/threat-intelligence/threat-events).
diff --git a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
index 14c2ac824145ccc..14417dfa3c757dd 100644
--- a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
+++ b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
@@ -3,25 +3,25 @@ title: Real-time alerts and daily digests for Threat Events
 description: You can now subscribe to automated notifications for your saved views in Threat Events
 date: 2026-04-08
 ---
-
+ 
 You can now automate your threat monitoring by setting up custom alerts in your saved views. Instead of manually checking the dashboard for updates, you can subscribe to notifications that trigger whenever new data matches your specific filter sets, like new activity associated to a particular threat actor or spikes in activity within your industry.
-
+ 
 ### Stay ahead of emerging threats
-
+ 
 By linking your saved views to the Cloudflare Notifications Center, you can ensure the right information reaches your team at the right time.
-
+ 
 - **Immediate Alerts**: receive real-time notifications the moment a critical event is detected that matches your saved criteria. This is essential for high-priority monitoring, such as tracking active campaigns from specific APT groups.
-
+ 
 - **Daily Digests**: opt for a summarized report delivered once a day. This is ideal for maintaining situational awareness of broader trends, like regional activity shifts or industry-wide threat landscapes, without cluttering your inbox.
-
+ 
 ![Threat Events notifications](~/assets/images/changelog/security-center/threat-events-notifications.png)
-
+ 
 ### How to get started
-
+ 
 To set up an alert, go to **Application Security** > **Threat Intelligence** > **Threat Events**. From there:
-
+ 
 1. Choose your datasets and apply your desired filters and select **Save View** (or select an existing one).
 2. Open the **Manage Saved Views** menu.
 3. Select **Add Alert** next to your chosen view to configure your notification preferences in the Cloudflare dashboard.
-
+ 
 For more technical details on configuring notifications, refer to the [Threat Events documentation](/security-center/cloudforce-one/).
diff --git a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
index 51425d471206a97..6ab0a8267691e14 100644
--- a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
+++ b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
@@ -7,7 +7,6 @@ date: 2026-05-07
 You can now export your Requests for Information (RFI) history to a **CSV document** and customize your dashboard view by choosing how many RFI records to load per page.
 
 ### Why this matters
-
 These quality-of-life updates focus on data portability and dashboard performance, allowing power users to manage high volumes of requests more efficiently:
 
 - The new **CSV export** allows you to move RFI data into external tools for custom reporting, internal auditing, or cross-referencing with other security projects without manual data entry
diff --git a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
index 3045c86a164b8bf..7728d2033ec5df9 100644
--- a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
+++ b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
@@ -9,19 +9,18 @@ We’ve added a new **Agent Readiness** tab to URL Scanner reports accessible vi
 The Internet is shifting from a human-read web to a machine-read web. AI agents now browse, interact with, and even perform transactions on websites. If a site isn't "agent-ready," these bots may consume excessive bandwidth, fail to find critical information, or be unable to navigate your services efficiently.
 
 This update provides material value by breaking down readiness into six actionable categories:
-
-- **Basic Web Presence**
+- **Basic Web Presence** 
 - **Discoverability**
-- **Content Accessibility**
-- **Bot Access Control**
-- **Protocol Discovery**
-- **Commerce**
+- **Content Accessibility** 
+- **Bot Access Control** 
+- **Protocol Discovery** 
+- **Commerce** 
 
 ## Accessing the report
 
-You can view these scores for any scanned URL directly in the dashboard or via our API.
+You can view these scores for any scanned URL directly in the dashboard or via our API. 
 
-- **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
-- **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
+* **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
+* **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
 
 To learn more about the methodology behind these scores, refer to the [blogpost](https://blog.cloudflare.com/agent-readiness/).
diff --git a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
index 632429a872e1c7c..f32ba78cbd7337b 100644
--- a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
+++ b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
@@ -12,7 +12,7 @@ Introducing enhanced archiving capabilities for security action items within the
 
 ### Why this matters
 
-Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored.
+Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored. 
 
 With these new archiving options—**False Positive**, **Accept Risk**, and **Other**—you can now suppress items indefinitely with required rationale text for risk-based decisions. This ensures that your team remains focused on critical, actionable vulnerabilities while preserving institutional knowledge for audits.
 
@@ -36,5 +36,4 @@ To review the history and rationale of a specific archived issue at the account
 ```bash
 curl "[https://api.cloudflare.com/client/v4/accounts/](https://api.cloudflare.com/client/v4/accounts/){account_id}/insights/{insight_id}/audit-log" \
      -H "Authorization: Bearer <API_TOKEN>" \
-     -H "Content-Type: application/json"
-```
+     -H "Content-Type: application/json"
\ No newline at end of file
diff --git a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
index 52e1ce7305a8c77..d1f9b23ef4c3974 100644
--- a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
+++ b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
@@ -7,7 +7,7 @@ description: Cloudflare Secrets Store is now integrated with AI Gateway, allowin
 date: 2025-08-25T11:00:00Z
 ---
 
-import { Card, Render, Details } from "~/components";
+import { Card, Render, Details } from "~/components"
 
 Cloudflare Secrets Store is now integrated with AI Gateway, allowing you to store, manage, and deploy your AI provider keys in a secure and seamless configuration through [Bring Your Own Key](https://developers.cloudflare.com/ai-gateway/configuration/bring-your-own-keys/). Instead of passing your AI provider keys directly in every request header, you can centrally manage each key with Secrets Store and deploy in your gateway configuration using only a reference, rather than passing the value in plain text.
 
@@ -25,24 +25,24 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthro
  --header 'anthropic-version: 2023-06-01' \
  --header 'Content-Type: application/json' \
  --data  '{"model": "claude-3-opus-20240229", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}'
-```
+ ```
 
-Or, using Javascript:
+ Or, using Javascript:
 
-```
-import Anthropic from '@anthropic-ai/sdk';
+ ```
+ import Anthropic from '@anthropic-ai/sdk';
 
 
 const anthropic = new Anthropic({
- apiKey: "ANTHROPIC_KEY_1",
- baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
+  apiKey: "ANTHROPIC_KEY_1",
+  baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
 });
 
 
 const message = await anthropic.messages.create({
- model: 'claude-3-opus-20240229',
- messages: [{role: "user", content: "What is Cloudflare?"}],
- max_tokens: 1024
+  model: 'claude-3-opus-20240229',
+  messages: [{role: "user", content: "What is Cloudflare?"}],
+  max_tokens: 1024
 });
 ```
 
diff --git a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
index d6f34e72b9e8ed7..c7b16b6e1a681b2 100644
--- a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
+++ b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
@@ -10,7 +10,7 @@ an M4A file to use in downstream workflows like [AI inference](/workers-ai/), co
 
 For example,
 
-```text title="Example URL"
+``` text title="Example URL"
 https://example.com/cdn-cgi/media/<OPTIONS>/<SOURCE-VIDEO>
 https://example.com/cdn-cgi/media/mode=audio,time=3s,duration=60s/<input video with diction>
 ```
diff --git a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
index 817c2e0c7c81e19..a2a4201f278c795 100644
--- a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
+++ b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
@@ -3,7 +3,6 @@ title: Redesigned Support Portal for faster, personalized help
 description: A streamlined Support Portal featuring AI-driven ticket routing and a simplified interface for all Cloudflare customers.
 date: 2026-04-07
 ---
-
 ## Redesigned "Get Help" Portal for faster, personalized help
 
 Cloudflare has officially launched a redesigned "Get Help" Support Portal to eliminate friction and get you to a resolution faster. Previously, navigating support meant clicking through multiple tiles, categorizing your own technical issues across 50+ conditional fields, and translating your problem into Cloudflare's internal taxonomy.
diff --git a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
index 906dc74af3ffc2b..0fe7d0c34250fb2 100644
--- a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
+++ b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
@@ -12,7 +12,7 @@ This change ensures that when you need help, you spend less time navigating the
 
 ### What changed?
 
-- **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
-- **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
+* **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
+* **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
 
 To learn more about the resources available to you, refer to the [Cloudflare Support documentation](https://developers.cloudflare.com/support/contacting-cloudflare-support/).
diff --git a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
index 70650f4bcd04ef7..d128e3253f5acb2 100644
--- a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
+++ b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
@@ -5,7 +5,6 @@ products:
   - fundamentals
 date: 2025-02-03
 ---
-
 ![Screenshot of Terraform defining a Zone](~/assets/images/changelog/2024-02-03-terraform-v5-screenshot.png)
 
 Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure.
@@ -13,6 +12,5 @@ Cloudflare's v5 Terraform Provider is now generally available. With this release
 The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach.
 
 For more info
-
-- [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
+* [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
+* [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
index 692eda375b40aaa..d8df928767923fd 100644
--- a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
@@ -11,12 +11,12 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 ### Changes
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
-  - `cloudflare_zero_trust_gateway_policy`
-  - `cloudflare_zero_trust_access_application`
-  - `cloudflare_zero_trust_tunnel_cloudflared_route`
-  - `cloudflare_zone_setting`
-  - `cloudflare_ruleset`
-  - `cloudflare_page_rule`
+	- `cloudflare_zero_trust_gateway_policy`
+	- `cloudflare_zero_trust_access_application`
+	- `cloudflare_zero_trust_tunnel_cloudflared_route`
+	- `cloudflare_zone_setting`
+	- `cloudflare_ruleset`
+	- `cloudflare_page_rule`
 - Zone settings can be re-applied without client errors
 - Page rules conversion errors are fixed
 - Failure to apply changes to `cloudflare_zero_trust_tunnel_cloudflared_route`
@@ -25,7 +25,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.5.0) in GitHub.
 
 ### Issues Closed
-
 - [#5304: Importing cloudflare_zero_trust_gateway_policy invalid attribute filter value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5304)
 - [#5303: cloudflare_page_rule import does not set values for all of the fields in terraform state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5303)
 - [#5178: cloudflare_page_rule Page rule creation with redirect fails](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5178)
diff --git a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
index ce7ec83f1e68809..88d70bea95929e7 100644
--- a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
@@ -17,7 +17,7 @@ eye on this changelog for more information about upcoming releases.
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
   - `cloudflare_zero_trust_access_identity_provider`
-  - `cloudflare_zone`
+	- `cloudflare_zone`
 - `cloudflare_page_rules` runtime panic when setting `cache_level` to `cache_ttl_by_status`
 - Failure to serialize requests in `cloudflare_zero_trust_tunnel_cloudflared_config`
 - Undocumented field 'priority' on `zone_lockdown` resource
@@ -33,7 +33,6 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.6.0) in GitHub.
 
 ### Issues Closed
-
 - [#5098: 500 Server Error on updating 'zero_trust_tunnel_cloudflared_virtual_network' Terraform resource](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5098)
 - [#5148: cloudflare_user_agent_blocking_rule doesn’t actually support user agents](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5148)
 - [#5472: cloudflare_zone showing changes in plan after following upgrade steps](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5472)
diff --git a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
index e637557cb1938b2..aaabc9c53996ef2 100644
--- a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
@@ -11,7 +11,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases.
 
 ### Changes
-
 - Addressed permanent diff bug on Cloudflare Tunnel config
 - State is now saved correctly for Zero Trust Access applications
 - Exact match is now working as expected within `data.cloudflare_zero_trust_access_applications`
@@ -25,7 +24,6 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.7.0) in GitHub.
 
 ### Issues Closed
-
 - [#5563: cloudflare_logpull_retention is missing import](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5563)
 - [#5608: cloudflare_zero_trust_access_policy in 5.5.0 provider gives error upon apply unexpected new value: .app_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1)](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5608)
 - [#5612: data.cloudflare_zero_trust_access_applications does not exact match](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5612)
@@ -34,6 +32,7 @@ For a more detailed look at all of the changes, see the
 - [#5565: Running Terraform with the cloudflare_zero_trust_access_policy resource results in updates on every apply, even when no changes are made - breaks idempotency](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5565)
 - [#5529: cloudflare_zero_trust_access_application: self hosted applications with private ips require public domain ](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5529)
 
+
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
index ce5660cdb8f4833..280ce29c2aebb63 100644
--- a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
@@ -11,7 +11,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_custom_pages`
   - `cloudflare_page_rule`
@@ -19,14 +18,13 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
   - `cloudflare_argo_tiered_caching`
 - Addressed chronic drift issues in `cloudflare_logpush_job`, `cloudflare_zero_trust_dns_location`, `cloudflare_ruleset` & `cloudflare_api_token`
 - `cloudflare_zone_subscription` returns expected values `rate_plan.id` from former versions
-- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate
-- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy`
+- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate 
+- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy` 
 - Other bug fixes
 
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.2) in GitHub.
 
 ### Issues Closed
-
 - [#5666: cloudflare_ruleset example lists id which is a read-only field](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5666)
 - [#5578: cloudflare_logpush_job plan always suggests changes](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5578)
 - [#5552: 5.4.0: Since provider update, existing cloudflare_list_item would be recreated "created" state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5552)
diff --git a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
index 62ed2ed4b454317..32201f4ca38d484 100644
--- a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
@@ -6,14 +6,13 @@ products:
 date: 2025-08-15
 ---
 
-Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability.
+Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. 
 
-One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests.
+One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests. 
 
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_argo_smart_routing`
   - `cloudflare_bot_management`
@@ -41,7 +40,6 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 For a more detailed look at all of the changes, refer to the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.4) in GitHub.
 
 ### Issues Closed
-
 - [#5017: 'Uncaught Error: No such module' using cloudflare_snippets](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5017)
 - [#5701: cloudflare_workers_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5701)
 - [#5640: cloudflare_argo_smart_routing importing doesn't read the actual value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5640)
diff --git a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
index e89ea7fd1f359cd..f25c1bc414c9f19 100644
--- a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
@@ -13,7 +13,6 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 This release includes a new resource, `cloudflare_snippet`, which replaces `cloudflare_snippets`. `cloudflare_snippet` is now considered deprecated but can still be used. Please utilize `cloudflare_snippet` as soon as possible.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_zone_setting`
   - `cloudflare_worker_script`
@@ -29,7 +28,6 @@ For a more detailed look at all of the changes, refer to the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.9.0) in GitHub.
 
 ### Issues Closed
-
 - [#5921: In cloudflare_ruleset removing an existing rule causes recreation of later rules](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5921)
 - [#5904: cloudflare_zero_trust_access_application is not idempotent](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5904)
 - [#5898: (cloudflare_workers_script) Durable Object migrations not applied](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5898)
@@ -49,6 +47,7 @@ For a more detailed look at all of the changes, refer to the
 - [#5727: cloudflare_ruleset http_request_cache_settings bypass mismatch between dashboard and terraform](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5727)
 - [#5700: cloudflare_account_member invalid type 'string' for field 'roles'](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5700)
 
+
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new issue if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
index ac788bb9e06272c..3886135203e9e03 100644
--- a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
@@ -6,56 +6,55 @@ products:
 date: 2025-11-20
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
-This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more.
+This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more. 
 
 ### Breaking Change
-
 Please be aware that there are breaking changes for the `cloudflare_api_token` and `cloudflare_account_token` resources. These changes eliminate configuration drift caused by policy ordering differences in the Cloudflare API.
 
 For more specific information about the changes or the actions required, please see the [detailed Repository changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.13.0).
 
+
 ### Features
 
-- **New resources and data sources added**
-  - cloudflare_connectivity_directory
-  - cloudflare_sso_connector
-  - cloudflare_universal_ssl_setting
-- **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
-- **docs:** make docs explicit when a resource does not have import support
-- **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
-- **worker_version:** add content_base64 support
-- **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
-- **workers_script_subdomains:** add import support ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
-- **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
-- **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
+* **New resources and data sources added** 
+	* cloudflare_connectivity_directory
+	* cloudflare_sso_connector
+	* cloudflare_universal_ssl_setting
+* **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
+* **docs:** make docs explicit when a resource does not have import support 
+* **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
+* **worker_version:** add content_base64 support
+* **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
+* **workers_script_subdomains:** add import support  ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
+* **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
+* **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
+
 
 ### Bug Fixes
 
-- **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
-- allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
-- **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
-- **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
-- **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
-- **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
-- **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181))
-- **workers_kv:** multipart request ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
-- **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386))
-- **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383))
-- **workers_script:** allow config.run_worker_first to accept list input
-- **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
-- **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
-- **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
-- **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
+* **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
+* allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
+* **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
+* **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
+* **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
+* **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
+* **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181)) 
+* **workers_kv:** multipart request  ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
+* **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386)) 
+* **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383)) 
+* **workers_script:** allow config.run_worker_first to accept list input 
+* **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
+* **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
+* **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
+* **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
 
 ### Upgrading
-
 We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized. We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more info
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
index 9cff570347406b9..a33c746b8592808 100644
--- a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
@@ -6,7 +6,7 @@ products:
 date: 2025-12-05
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
@@ -14,7 +14,7 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Deprecation notice
 
-Resource affected: `api_shield_discovery_operation`
+Resource affected: `api_shield_discovery_operation` 
 
 Cloudflare continuously discovers and updates API endpoints and web assets of your web applications. To improve the maintainability of these dynamic resources, we are working on reducing the need to actively engage with discovered operations.
 
@@ -26,23 +26,21 @@ The corresponding public API endpoint of [discovered operations](https://develop
 
 ### Bug fixes
 
-- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488))
+- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488)) 
 - **pages_project**: Ensures non empty refresh plans ([#6515](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6515))
-- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512))
-- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521))
-- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489))
-- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504))
-- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503))
+- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512)) 
+- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521)) 
+- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489)) 
+- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504)) 
+- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503)) 
 - **zero_trust_dlp_custom_profile**: Adds sweepers for `dlp_custom_profile`
 - **zone_subscription|account_subscription**: Adds `partners_ent` as valid enum for `rate_plan.id` ([#6505](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6505))
-- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487))
-- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510))
+- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487)) 
+- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510)) 
 
 ### Upgrade to newer version
-
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
index 6c0f1f7bf13a718..017d74955cda99c 100644
--- a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
@@ -14,31 +14,29 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-- **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
-- **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
-- **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
-- **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
-- **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+* **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
+* **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
+* **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
+* **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+* **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
 
 ### Bug fixes
 
-- **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
-- **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
-- **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
-- **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
-- **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
-- **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
-- **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
+* **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
+* **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
+* **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
+* **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
+* **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
+* **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
+* **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
 
 ### Upgrade to newer version
-
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](/terraform/)
+- [Documentation on using Terraform with Cloudflare](/terraform/)
\ No newline at end of file
diff --git a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
index fc887b15fcfba63..00374611ed967d8 100644
--- a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
@@ -16,42 +16,41 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-- **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
-- **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
-- **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
-- **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
-- **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
-- **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
-- **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
-- **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
-- **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
-- **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
-- **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
-- **ruleset:** add request body buffering support
-- **ruleset:** enhance ruleset data source with additional configuration options
-- **workers_script:** add observability logs attributes to list data source model
-- **workers_script:** enhance list data source schema with additional configuration options
+* **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
+* **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
+* **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
+* **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
+* **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
+* **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
+* **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
+* **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
+* **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
+* **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
+* **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
+* **ruleset:** add request body buffering support
+* **ruleset:** enhance ruleset data source with additional configuration options
+* **workers_script:** add observability logs attributes to list data source model
+* **workers_script:** enhance list data source schema with additional configuration options
 
 ### Bug Fixes
 
-- **account_member**: fix resource importability issues
-- **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
-- **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
-- **workers_kv:** handle special characters correctly in URL encoding
+* **account_member**: fix resource importability issues
+* **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
+* **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
+* **workers_kv:** handle special characters correctly in URL encoding
 
 ### Documentation
 
-- **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
-- **api_shield:** add resource-level description for API Shield management of auth ID characteristics
-- **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
-- **api_shield:** specify JSONPath expression format for JWT claim locations
-- **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
-- **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
-- **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
-- **hyperdrive_config:** update port description to clarify defaults for different database types
+* **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
+* **api_shield:** add resource-level description for API Shield management of auth ID characteristics
+* **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
+* **api_shield:** specify JSONPath expression format for JWT claim locations
+* **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
+* **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
+* **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
+* **hyperdrive_config:** update port description to clarify defaults for different database types
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
index 76242fbae5f2ce1..d8dedb4bea9275a 100644
--- a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
@@ -28,61 +28,60 @@ help us build products that reflect your needs.
 
 ### Features
 
-- **ai_search_instance:** add data source for querying AI Search instances
-- **ai_search_token:** add data source for querying AI Search tokens
-- **account:** add support for tenant unit management with new `unit` field
-- **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
-- **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
-- **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
-- **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
-- **workers_kv:** add `value` field to data source to retrieve KV values directly
-- **workers_script:** add `script` field to data source to retrieve script content
-- **workers_script:** add support for `simple` rate limit binding
-- **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
-- **workers_script:** add `placement_mode` and `placement_status` computed fields
-- **zero_trust_dex_test:** add data source with filter support for finding specific tests
-- **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
+* **ai_search_instance:** add data source for querying AI Search instances
+* **ai_search_token:** add data source for querying AI Search tokens
+* **account:** add support for tenant unit management with new `unit` field
+* **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
+* **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
+* **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
+* **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
+* **workers_kv:** add `value` field to data source to retrieve KV values directly
+* **workers_script:** add `script` field to data source to retrieve script content
+* **workers_script:** add support for `simple` rate limit binding
+* **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
+* **workers_script:** add `placement_mode` and `placement_status` computed fields
+* **zero_trust_dex_test:** add data source with filter support for finding specific tests
+* **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
 
 ### Bug Fixes
 
-- **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
-- **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
-- **authenticated_origin_pulls:** handle array response and implement full lifecycle
-- **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
-- **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
-- **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
-- **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
-- **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
-- **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
-- **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
-- **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
-- **mtls_certificates:** fix resource and test
-- **pages_project:** revert build_config to computed optional
-- **stream_key:** use correct `account_id` field instead of `id` in API calls
-- **total_tls:** use upsert pattern for singleton zone setting
-- **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
-- **workers_script:** add support for placement mode/status
-- **zero_trust_access_application:** update v4 version on migration tests
-- **zero_trust_device_posture_rule:** update tests to match API
-- **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
-- **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
-- **zero_trust_organization:** fix plan issues
+* **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
+* **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
+* **authenticated_origin_pulls:** handle array response and implement full lifecycle
+* **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
+* **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
+* **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
+* **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
+* **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
+* **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
+* **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
+* **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
+* **mtls_certificates:** fix resource and test
+* **pages_project:** revert build_config to computed optional
+* **stream_key:** use correct `account_id` field instead of `id` in API calls
+* **total_tls:** use upsert pattern for singleton zone setting
+* **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
+* **workers_script:** add support for placement mode/status
+* **zero_trust_access_application:** update v4 version on migration tests
+* **zero_trust_device_posture_rule:** update tests to match API
+* **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
+* **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
+* **zero_trust_organization:** fix plan issues
 
 ### Chores
 
-- add state upgraders to 95+ resources to lay the foundation for replacing Grit
+* add state upgraders to 95+ resources to lay the foundation for replacing Grit
   (still under active development)
-- **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
-- **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
-- **dns_record:** add state migration handler for SDKv2 to Framework conversion
-- **leaked_credential_check:** add import functionality and tests
-- **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
-- **pages_project:** add state migration handlers
-- **tiered_cache:** add state migration handlers
-- **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
+* **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
+* **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
+* **dns_record:** add state migration handler for SDKv2 to Framework conversion
+* **leaked_credential_check:** add import functionality and tests
+* **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
+* **pages_project:** add state migration handlers
+* **tiered_cache:** add state migration handlers
+* **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
index c9633450d6adb47..6681382c7d1ae98 100644
--- a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
@@ -32,7 +32,6 @@ Terraform Provider v5.19.0 introduces 14 new resources spanning AI Gateway, Pipe
 ### V4 to V5 Migration State Upgraders
 
 State upgraders added for seamless migration from v4 to v5 for the following resources:
-
 - account
 - account_member
 - account_token
diff --git a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
index 1acd6e85a6a432f..4aa693f7bd56a44 100644
--- a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
+++ b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
@@ -6,11 +6,11 @@ products:
   - terraform
 ---
 
-We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5.
+We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5. 
 
 ## v5 is stable and ready for production
 
-**Terraform Provider v5 is stable and actively receiving updates.** We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
+**Terraform Provider v5 is stable and actively receiving updates.**  We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
 
 Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool we're providing to the community — ensuring the best possible migration experience.
 
@@ -24,7 +24,7 @@ Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool w
 - **Cross-file reference updates** – Automatically finds and updates all references to renamed resources across your entire configuration
 - **Dry-run mode** – Preview all changes before applying them to ensure safety
 
-Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest.
+Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest. 
 
 ## Supported resources
 
diff --git a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
index 968781b659c1aca..d669da557298f32 100644
--- a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
+++ b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
@@ -14,8 +14,7 @@ Your real-time applications running over [Cloudflare Tunnel](/cloudflare-one/net
 This is a foundational improvement to Cloudflare Tunnel, delivered automatically to all customers. There are no settings to configure — your UDP traffic is already flowing faster and more reliably.
 
 **What’s new:**
-
 - **Faster UDP performance**: We've significantly reduced the latency for establishing new UDP sessions, making applications like private DNS much more responsive.
 - **Greater reliability for mixed traffic**: UDP packets are no longer affected by heavy TCP traffic, preventing timeouts and connection drops for your real-time services.
 
-Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
+Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
index e857486e0668872..4ed43b589b89d2e 100644
--- a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
+++ b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
@@ -13,22 +13,22 @@ Starting **December 1, 2025**, list endpoints for the [Cloudflare Tunnel API](/a
 No action is required if you already explicitly set `is_deleted=false` or if you only need to list active resources.
 
 This change affects the following API endpoints:
-
-- List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
-- List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
-- List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
-- List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
-- List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
-- List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
+* List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
+* List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
+* List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
+* List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
+* List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
+* List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
 
 ## What is changing?
 
 The default behavior of the `is_deleted` query parameter will be updated.
 
-| Scenario                          | Previous behavior (before December 1, 2025)                                | New behavior (from December 1, 2025)                                  |
-| :-------------------------------- | :------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
+| Scenario | Previous behavior (before December 1, 2025) | New behavior (from December 1, 2025) |
+| :--- | :--- | :--- |
 | `is_deleted` parameter is omitted | Returns **active & deleted** tunnels, routes, subnets and virtual networks | Returns **only active** tunnels, routes, subnets and virtual networks |
 
+
 ## Action required
 
 If you need to retrieve deleted (or all) resources, please update your API calls to explicitly include the `is_deleted` parameter before **December 1, 2025**.
@@ -48,11 +48,9 @@ curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/virtual_
 Following this change, retrieving a complete list of both active and deleted resources will require two separate API calls: one to get active items (by omitting the parameter or using `is_deleted=false`) and one to get deleted items (`is_deleted=true`).
 
 ## Why we’re making this change
-
 This update is based on user feedback and aims to:
+* **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
+* **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
+* **Improve performance:** For most users, the default query result will now be smaller and more relevant.
 
-- **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
-- **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
-- **Improve performance:** For most users, the default query result will now be smaller and more relevant.
-
-To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
+To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
index bc751a65e2b32ff..947de730982905f 100644
--- a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
+++ b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
@@ -16,7 +16,6 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 ![Hostname-based routing in Cloudflare Tunnel](~/assets/images/changelog/cloudflare-one/tunnel-hostname-routing.webp)
 
 **What’s new:**
-
 - **Hostname & Domain Routing**: Create routes for individual hostnames (e.g., `payroll.acme.local`) or entire domains (e.g., `*.acme.local`) and direct their traffic to a specific Tunnel.
 - **Simplified Zero Trust Policies**: Build resilient policies in Cloudflare Access and Gateway using stable hostnames, making it dramatically easier to apply per-resource authorization for your private applications.
 - **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
@@ -24,4 +23,4 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 
 Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) or [public hostname](/cloudflare-one/traffic-policies/egress-policies/egress-cloudflared/) route.
 
-Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
+Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
index 35c45b7766d212a..b4bdbe1014ee162 100644
--- a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
+++ b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
@@ -13,4 +13,4 @@ You can now `ping` the WARP Connector host directly on its LAN IP address immedi
 
 Starting with [version 2025.10.186.0](/changelog/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability.
 
-Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
+Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-07-14-waf-release.mdx b/src/content/changelog/waf/2025-07-14-waf-release.mdx
index 3657b790de4b853..27ee5690579c07e 100644
--- a/src/content/changelog/waf/2025-07-14-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-14-waf-release.mdx
@@ -13,6 +13,7 @@ This week’s vulnerability analysis highlights emerging web application threats
 - XSS – Attribute Overloading: A novel cross-site scripting technique where attackers abuse custom or non-standard HTML attributes to smuggle payloads into the DOM. These payloads evade traditional sanitization logic, especially in frameworks that loosely validate attributes or trust unknown tokens.
 - XSS – onToggle Event Abuse: Exploits the lesser-used onToggle event (triggered by elements like `<details>`) to execute arbitrary JavaScript when users interact with UI elements. This vector is often overlooked by static analyzers and can be embedded in seemingly benign components.
 
+
 **Impact**
 
 These vulnerabilities target both user-facing components and back-end databases, introducing potential vectors for credential theft, session hijacking, or full data exfiltration. The XSS variants bypass conventional filters through overlooked HTML behaviors, while the obfuscated SQLi enables attackers to stealthily probe back-end logic, making them especially difficult to detect and block.
diff --git a/src/content/changelog/waf/2025-07-21-emergency.mdx b/src/content/changelog/waf/2025-07-21-emergency.mdx
index 190744a1169aa10..ce9154530bc73e3 100644
--- a/src/content/changelog/waf/2025-07-21-emergency.mdx
+++ b/src/content/changelog/waf/2025-07-21-emergency.mdx
@@ -29,30 +29,30 @@ Together, these vulnerabilities significantly weaken the security posture of on-
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
+       <tbody>
+ 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
-				<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
+					<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
 			</td>
 			<td>100817</td>
 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53770</td>
 			<td>N/A</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
-		</tr>
-		<tr>
+ 		</tr>
+ 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d21f327516a145bc9d1b05678de656c4" />
-			</td>
-			<td>100818</td>
-			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
+ 			<td>
+ 					<RuleID id="d21f327516a145bc9d1b05678de656c4" />
+ 			</td>
+ 			<td>100818</td>
+ 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
+ 			<td>N/A</td>
+ 			<td>Block</td>
+ 			<td>This is a New Detection</td>
 		</tr>
-	</tbody>
+  </tbody>
 </table>
 
-For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
+For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-07-28-waf-release.mdx b/src/content/changelog/waf/2025-07-28-waf-release.mdx
index c04a253ad3d3a3e..3374f46caf0c044 100644
--- a/src/content/changelog/waf/2025-07-28-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-28-waf-release.mdx
@@ -8,6 +8,7 @@ import { RuleID } from "~/components";
 
 This week’s update spotlights several vulnerabilities across Apache Tomcat, MongoDB, and Fortinet FortiWeb. Several flaws related with a memory leak in Apache Tomcat can lead to a denial-of-service attack. Additionally, a code injection flaw in MongoDB's Mongoose library allows attackers to bypass security controls to access restricted data.
 
+
 **Key Findings**
 
 - Fortinet FortiWeb (CVE-2025-25257): An improper neutralization of special elements used in a SQL command vulnerability in Fortinet FortiWeb versions allows an unauthenticated attacker to execute unauthorized SQL code or commands.
@@ -72,9 +73,7 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="f9e01e28c5d6499cac66364b4b6a5bb1" />
 			</td>
 			<td>100815</td>
-			<td>
-				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
-			</td>
+			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -85,12 +84,10 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="700d4fcc7b1f481a80cbeee5688f8e79" />
 			</td>
 			<td>100816</td>
-			<td>
-				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
-			</td>
+			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-04-waf-release.mdx b/src/content/changelog/waf/2025-08-04-waf-release.mdx
index b0e648fc90a3a62..f8f5bc852842740 100644
--- a/src/content/changelog/waf/2025-08-04-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-04-waf-release.mdx
@@ -35,110 +35,105 @@ The Grafana cross-site scripting (XSS) flaw can be used to hijack authenticated
 Meanwhile, the information disclosure flaw in WordPress core provides attackers with valid user emails, fueling targeted phishing campaigns that aim to secure the same account access achievable through the other exploits.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b8ab4644f8044f3485441ee052f30a13" />
-			</td>
-			<td>100535A</td>
-			<td>
-				Sitecore - Dangerous File Upload - CVE:CVE-2025-34510,
-				CVE:CVE-2025-34511
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
-			</td>
-			<td>100535</td>
-			<td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
-			</td>
-			<td>100543</td>
-			<td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
-			</td>
-			<td>100545</td>
-			<td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="28108d25f1cf470c8e7648938f634977" />
-			</td>
-			<td>100820</td>
-			<td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
-			</td>
-			<td>100821</td>
-			<td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
-			</td>
-			<td>100822</td>
-			<td>
-				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="69d43d704b0641898141a4300bf1b661" />
-			</td>
-			<td>100823</td>
-			<td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b8ab4644f8044f3485441ee052f30a13" />
+      </td>
+      <td>100535A</td>
+      <td>Sitecore - Dangerous File Upload - CVE:CVE-2025-34510, CVE:CVE-2025-34511</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
+      </td>
+      <td>100535</td>
+      <td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
+      </td>
+      <td>100543</td>
+      <td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
+      </td>
+      <td>100545</td>
+      <td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="28108d25f1cf470c8e7648938f634977" />
+      </td>
+      <td>100820</td>
+      <td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
+      </td>
+      <td>100821</td>
+      <td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
+      </td>
+      <td>100822</td>
+      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="69d43d704b0641898141a4300bf1b661" />
+      </td>
+      <td>100823</td>
+      <td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
index e9deb9cfadebeca..e7e5dad628ec2f1 100644
--- a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
@@ -23,42 +23,39 @@ Adobe AEM’s remote code execution vulnerability enables attackers to run arbit
 These findings reinforce the urgency of updating to the patched versions — Squid 6.4 and Adobe AEM 6.5.24 or later — and reviewing configurations to prevent exploitation.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
-			</td>
-			<td>100844</td>
-			<td>
-				Adobe Experience Manager Forms - Remote Code Execution -
-				CVE:CVE-2025-54253
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
-			</td>
-			<td>100840</td>
-			<td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
+      </td>
+      <td>100844</td>
+      <td>Adobe Experience Manager Forms - Remote Code Execution - CVE:CVE-2025-54253</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
+      </td>
+      <td>100840</td>
+      <td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-11-waf-release.mdx b/src/content/changelog/waf/2025-08-11-waf-release.mdx
index 74a303e3d74c2fb..62764e4b09840a6 100644
--- a/src/content/changelog/waf/2025-08-11-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-11-waf-release.mdx
@@ -8,21 +8,26 @@ import { RuleID } from "~/components";
 
 This week's update focuses on a wide range of enterprise software, from network infrastructure and security platforms to content management systems and development frameworks. Flaws include unsafe deserialization, OS command injection, SSRF, authentication bypass, and arbitrary file upload — many of which allow unauthenticated remote code execution. Notable risks include Cisco Identity Services Engine and Ivanti EPMM, where successful exploitation could grant attackers full administrative control of core network infrastructure and popular web services such as WordPress, SharePoint, and Ingress-Nginx, where security bypasses and arbitrary file uploads could lead to complete site or server compromise.
 
+
 **Key Findings**
 
 - Cisco Identity Services Engine (CVE-2025-20281): Insufficient input validation in a specific API of Cisco Identity Services Engine (ISE) and ISE-PIC allows an unauthenticated, remote attacker to execute arbitrary code with root privileges on an affected device.
 
 - Wazuh Server (CVE-2025-24016): An unsafe deserialization vulnerability in Wazuh Server (versions 4.4.0 to 4.9.0) allows for remote code execution and privilege escalation. By injecting unsanitized data, an attacker can trigger an exception to execute arbitrary code on the server.
 
+
 - CrushFTP (CVE-2025-54309): A flaw in AS2 validation within CrushFTP allows remote attackers to gain administrative access via HTTPS on systems not using the DMZ proxy feature. This flaw can lead to unauthorized file access and potential system compromise.
 
+
 - Kentico Xperience CMS (CVE-2025-2747, CVE-2025-2748): Vulnerabilities in Kentico Xperience CMS could enable cross-site scripting (XSS), allowing attackers to inject malicious scripts into web pages. Additionally, a flaw could allow unauthenticated attackers to bypass the Staging Sync Server's authentication, potentially leading to administrative control over the CMS.
 
+
 - Node.js (CVE-2025-27210): An incomplete fix for a previous vulnerability (CVE-2025-23084) in Node.js affects the `path.join()` API method on Windows systems. The vulnerability can be triggered using reserved Windows device names such as `CON`, `PRN`, or `AUX`.
 
-- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847):
-  This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
-  (Note: CVE-2025-34085 has been rejected as a duplicate.)
+- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847): 
+This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
+(Note: CVE-2025-34085 has been rejected as a duplicate.)
+
 
 - GeoServer (CVE-2024-29198): A Server-Side Request Forgery (SSRF) vulnerability exists in GeoServer's Demo request endpoint, which can be exploited where the Proxy Base URL has not been configured.
 
@@ -32,239 +37,240 @@ This week's update focuses on a wide range of enterprise software, from network
 
 - Manager-IO (CVE-2025-54122): A critical unauthenticated full read Server-Side Request Forgery (SSRF) vulnerability is present in the proxy handler of both Manager Desktop and Server editions up to version 25.7.18.2519. This allows an unauthenticated attacker to bypass network isolation and access internal services.
 
-- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller.
+- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. 
 
 - PaperCut NG/MF (CVE-2023-2533): A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PaperCut NG/MF. Under specific conditions, an attacker could exploit this to alter security settings or execute arbitrary code if they can deceive an administrator with an active login session into clicking a malicious link.
 
 - SonicWall SMA (CVE-2025-40598): This vulnerability could allow an unauthenticated attacker to bypass security controls. This allows a remote, unauthenticated attacker to potentially execute arbitrary JavaScript code.
 
-- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
+- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress  is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
+
 
 **Impact**
 
 These vulnerabilities span a broad range of enterprise technologies, including network access control systems, monitoring platforms, web servers, CMS platforms, cloud services, and collaboration tools. Exploitation techniques range from remote code execution and command injection to authentication bypass, SQL injection, path traversal, and configuration weaknesses.
 
-A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers.
+A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers. 
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ec6480c81253494b947d891e51bc8df1" />
-			</td>
-			<td>100538</td>
-			<td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
-			</td>
-			<td>100548</td>
-			<td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
-			</td>
-			<td>100550</td>
-			<td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e1369c5d629f4f10a14141381dca5738" />
-			</td>
-			<td>100562</td>
-			<td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
-			</td>
-			<td>100565</td>
-			<td>
-				Cisco Identity Services Engine - Remote Code Execution -
-				CVE:CVE-2025-20281
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed759f7e44184fa398ef71785d8102e1" />
-			</td>
-			<td>100567</td>
-			<td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="71b8e7b646f94d79873213cd99105c43" />
-			</td>
-			<td>100569</td>
-			<td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
-			</td>
-			<td>100571</td>
-			<td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
-			</td>
-			<td>100573</td>
-			<td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
-			</td>
-			<td>100806</td>
-			<td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
-			</td>
-			<td>100824</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3638baed75924604987b86d874920ace" />
-			</td>
-			<td>100824A</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
-			</td>
-			<td>100825</td>
-			<td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
-			</td>
-			<td>100826</td>
-			<td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
-			</td>
-			<td>100827</td>
-			<td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54dd826f578c483196ce852b6f1c2d12" />
-			</td>
-			<td>100828</td>
-			<td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a2867f7456c14213a94509a40341fccc" />
-			</td>
-			<td>100829</td>
-			<td>
-				WordPress:Plugin:Simple File List - Remote Code Execution -
-				CVE:CVE-2025-34085
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4cdb0e792d1a428a897526624cefeeda" />
-			</td>
-			<td>100829A</td>
-			<td>
-				WordPress:Plugin:Simple File List - Remote Code Execution -
-				CVE:CVE-2025-34085 - 2
-			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ec6480c81253494b947d891e51bc8df1" />
+      </td>
+      <td>100538</td>
+      <td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
+      </td>
+      <td>100548</td>
+      <td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
+      </td>
+      <td>100550</td>
+      <td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e1369c5d629f4f10a14141381dca5738" />
+      </td>
+      <td>100562</td>
+      <td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
+      </td>
+      <td>100565</td>
+      <td>
+        Cisco Identity Services Engine - Remote Code Execution -
+        CVE:CVE-2025-20281
+      </td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed759f7e44184fa398ef71785d8102e1" />
+      </td>
+      <td>100567</td>
+      <td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="71b8e7b646f94d79873213cd99105c43" />
+      </td>
+      <td>100569</td>
+      <td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
+      </td>
+      <td>100571</td>
+      <td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
+      </td>
+      <td>100573</td>
+      <td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
+      </td>   
+      <td>100806</td>      
+      <td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
+      </td>
+      <td>100824</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3638baed75924604987b86d874920ace" />
+      </td>
+      <td>100824A</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
+      </td>
+      <td>100825</td>
+      <td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
+      <td>Log</td>
+      <td>Block</td> 
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
+      </td>
+      <td>100826</td>
+      <td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
+      </td>
+      <td>100827</td>
+      <td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="54dd826f578c483196ce852b6f1c2d12" />
+      </td>
+      <td>100828</td>
+      <td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a2867f7456c14213a94509a40341fccc" />
+      </td>
+      <td>100829</td>
+      <td>
+        WordPress:Plugin:Simple File List - Remote Code Execution -
+        CVE:CVE-2025-34085
+      </td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4cdb0e792d1a428a897526624cefeeda" />
+      </td>
+      <td>100829A</td>
+      <td>
+        WordPress:Plugin:Simple File List - Remote Code Execution -
+        CVE:CVE-2025-34085 - 2
+      </td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-18-waf-release.mdx b/src/content/changelog/waf/2025-08-18-waf-release.mdx
index 8f05b2eb924b63f..78b79350ea882e6 100644
--- a/src/content/changelog/waf/2025-08-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-18-waf-release.mdx
@@ -31,143 +31,138 @@ This week, a series of critical vulnerabilities were discovered impacting core e
 These vulnerabilities affect core infrastructure, from network security appliances like SonicWall to data platforms such as Apache Druid and ML frameworks like BentoML. The code execution and deserialization flaws are particularly severe, offering deep system access that allows attackers to steal data, disrupt services, and establish a foothold for broader intrusions. Simultaneously, SSRF and XXE vulnerabilities undermine network boundaries, exposing sensitive internal data and creating pathways for lateral movement. Beyond data-centric threats, flaws in edge devices like the Tenda router introduce the tangible risk of operational disruption, highlighting a multi-faceted threat to the security and stability of key enterprise systems.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
-			</td>
-			<td>100574</td>
-			<td>
-				SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819,
-				CVE:CVE-2025-32820, CVE:CVE-2025-32821
-			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
-			</td>
-			<td>100576</td>
-			<td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d62935357ff846d9adefb58108ac45b3" />
-			</td>
-			<td>100585</td>
-			<td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
-			</td>
-			<td>100834</td>
-			<td>
-				Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1474121b01ba40629f8246f8022ab542" />
-			</td>
-			<td>100835</td>
-			<td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
-			</td>
-			<td>100837</td>
-			<td>SQLi - OOB</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
-			</td>
-			<td>100841</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="40fd793035c947c5ac75add1739180d2" />
-			</td>
-			<td>100841A</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
-			</td>
-			<td>100841B</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
-			</td>
-			<td>100845</td>
-			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
-			</td>
-			<td>100845A</td>
-			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
+      </td>
+      <td>100574</td>
+      <td>SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819, CVE:CVE-2025-32820, CVE:CVE-2025-32821</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
+      </td>
+      <td>100576</td>
+      <td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d62935357ff846d9adefb58108ac45b3" />
+      </td>
+      <td>100585</td>
+      <td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
+      </td>
+      <td>100834</td>
+      <td>Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="1474121b01ba40629f8246f8022ab542" />
+      </td>
+      <td>100835</td>
+      <td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
+      </td>
+      <td>100837</td>
+      <td>SQLi - OOB</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
+      </td>
+      <td>100841</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="40fd793035c947c5ac75add1739180d2" />
+      </td>
+      <td>100841A</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
+      </td>
+      <td>100841B</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
+      </td>
+      <td>100845</td>
+      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
+      </td>
+      <td>100845A</td>
+      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-25-waf-release.mdx b/src/content/changelog/waf/2025-08-25-waf-release.mdx
index 42c73f310668c3c..f78810c3fd8e64b 100644
--- a/src/content/changelog/waf/2025-08-25-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-25-waf-release.mdx
@@ -21,56 +21,50 @@ This week, critical vulnerabilities were disclosed that impact widely used open-
 These vulnerabilities pose severe risks to enterprise environments and open-source ecosystems. Remote code execution enables attackers to gain deep system access, steal data, disrupt services, and establish persistent footholds for broader intrusions. Given the widespread deployment of Apache HTTP Server and Laravel in production systems, timely patching and mitigation are critical.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c550282a0f7343ca887bdab528050359" />
-			</td>
-			<td>100822_BETA</td>
-			<td>
-				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>
-				This was merged in to the original rule "WordPress:Plugin:WPBookit -
-				Remote Code Execution - CVE:CVE-2025-6058" (ID:{" "}
-				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
-			</td>
-			<td>100831</td>
-			<td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
-			</td>
-			<td>100846</td>
-			<td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c550282a0f7343ca887bdab528050359" />
+      </td>
+      <td>100822_BETA</td>
+      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This was merged in to the original rule "WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058" (ID: <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
+      </td>
+      <td>100831</td>
+      <td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
+      </td>
+      <td>100846</td>
+      <td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
index 0d6fc5ee3b10133..e11552cfbac77e9 100644
--- a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
@@ -21,39 +21,39 @@ This week, new critical vulnerabilities were disclosed in Next.js’s image opti
 Exploitation could expose sensitive files, leak user or backend data, and undermine application trust. Given Next.js’s wide use, immediate patching and cache hardening are strongly advised.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
-			</td>
-			<td>100613</td>
-			<td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
-			</td>
-			<td>100616</td>
-			<td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
+      </td>
+      <td>100613</td>
+      <td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
+      </td>
+      <td>100616</td>
+      <td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-01-waf-release.mdx b/src/content/changelog/waf/2025-09-01-waf-release.mdx
index 88aa80a7543ddf4..5470b675623f1e5 100644
--- a/src/content/changelog/waf/2025-09-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-01-waf-release.mdx
@@ -10,48 +10,50 @@ import { RuleID } from "~/components";
 
 This week, a critical vulnerability was disclosed in Fortinet FortiWeb (versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and versions 7.0.10 and below), linked to improper parameter handling that could allow unauthorized access.
 
+
 **Key Findings**
 
-- Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
+* Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
 
 **Impact**
 
-Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended.
+Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended. 
+
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="636b145a49a84946b990d4fac49b7cf8" />
-			</td>
-			<td>100586</td>
-			<td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
-			</td>
-			<td>100136C</td>
-			<td>XSS - JavaScript - Headers and Body</td>
-			<td>N/A</td>
-			<td>N/A</td>
-			<td>Rule metadata description refined. Detection unchanged.</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="636b145a49a84946b990d4fac49b7cf8" />
+      </td>
+      <td>100586</td>
+      <td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
+      </td>
+      <td>100136C</td>
+      <td>XSS - JavaScript - Headers and Body</td>
+      <td>N/A</td>
+      <td>N/A</td>
+      <td>Rule metadata description refined. Detection unchanged.</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
index 5855b853f30db8a..385a50fe802115e 100644
--- a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
@@ -12,7 +12,6 @@ This week, new critical vulnerabilities were disclosed in Sitecore’s Sitecore
 These flaws are caused by unsafe data deserialization and code reflection, leaving affected systems at high risk of exploitation.
 
 **Key Findings**
-
 - CVE-2025-53690: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53691: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53693: HTML Cache Poisoning through Unsafe Reflections
@@ -22,50 +21,50 @@ These flaws are caused by unsafe data deserialization and code reflection, leavi
 Exploitation could allow attackers to execute arbitrary code remotely on the affected system and conduct cache poisoning attacks, potentially leading to further compromise. Applying the latest vendor-released solution without delay is strongly recommended.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
-			</td>
-			<td>100878</td>
-			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-			</td>
-			<td>100631</td>
-			<td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed94c7ce5301411a94a21a096c410240" />
-			</td>
-			<td>100879</td>
-			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
+      </td>
+      <td>100878</td>
+      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+      </td>
+      <td>100631</td>
+      <td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed94c7ce5301411a94a21a096c410240" />
+      </td>
+      <td>100879</td>
+      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-08-waf-release.mdx b/src/content/changelog/waf/2025-09-08-waf-release.mdx
index ccc94cccb99a6c9..1784243e8d5d2af 100644
--- a/src/content/changelog/waf/2025-09-08-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-08-waf-release.mdx
@@ -6,21 +6,21 @@ date: 2025-09-08
 
 import { RuleID } from "~/components";
 
-**This week's update**
+**This week's update** 
 
 This week’s focus highlights newly disclosed vulnerabilities in web frameworks, enterprise applications, and widely deployed CMS plugins. The vulnerabilities include SSRF, authentication bypass, arbitrary file upload, and remote code execution (RCE), exposing organizations to high-impact risks such as unauthorized access, system compromise, and potential data exposure. In addition, security rule enhancements have been deployed to cover general command injection and server-side injection attacks, further strengthening protections.
 
 **Key Findings**
 
-- Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
+* Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
 
-- ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
+* ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
 
-- Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
+* Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
 
-- Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
+* Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
 
-- WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
+* WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
 
 **Impact**
 
@@ -29,128 +29,116 @@ These vulnerabilities could allow attackers to gain unauthorized access, execute
 Administrators are strongly advised to apply vendor patches immediately, remove unsupported software, and review authentication and access controls to mitigate these risks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
-			</td>
-			<td>100007D</td>
-			<td>Command Injection - Common Attack Commands Args</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "Command Injection -
-				Common Attack Commands" (ID:{" "}
-				<RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers
-				only.
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cd528243d6824f7ab56182988230a75b" />
-			</td>
-			<td>100617</td>
-			<td>Next.js - SSRF - CVE:CVE-2025-57822</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
-			</td>
-			<td>100659_BETA</td>
-			<td>Common Payloads for Server-Side Template Injection - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Common Payloads for
-				Server-Side Template Injection" (ID:{" "}
-				<RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
-			</td>
-			<td>100824B</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
-			</td>
-			<td>100848</td>
-			<td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
-			</td>
-			<td>100849</td>
-			<td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e7464139fd3e44938b56716bef971afd" />
-			</td>
-			<td>100872</td>
-			<td>
-				WordPress:Plugin:InfiniteWP Client - Missing Authorization -
-				CVE:CVE-2020-8772
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
-			</td>
-			<td>100873</td>
-			<td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
-			</td>
-			<td>100875</td>
-			<td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
+      </td>
+      <td>100007D</td>
+      <td>Command Injection - Common Attack Commands Args</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "Command Injection - Common Attack Commands" (ID: <RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers only.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cd528243d6824f7ab56182988230a75b" />
+      </td>      
+      <td>100617</td>
+      <td>Next.js - SSRF - CVE:CVE-2025-57822</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
+      </td>
+      <td>100659_BETA</td>
+      <td>Common Payloads for Server-Side Template Injection - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "Common Payloads for Server-Side Template Injection" (ID: <RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)</td>
+    </tr>    
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
+      </td>
+      <td>100824B</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>    
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
+      </td>
+      <td>100848</td>
+      <td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
+      </td>
+      <td>100849</td>
+      <td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e7464139fd3e44938b56716bef971afd" />
+      </td>
+      <td>100872</td>
+      <td>WordPress:Plugin:InfiniteWP Client - Missing Authorization - CVE:CVE-2020-8772</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
+      </td>
+      <td>100873</td>
+      <td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
+      </td>
+      <td>100875</td>
+      <td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>    
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-15-waf-release.mdx b/src/content/changelog/waf/2025-09-15-waf-release.mdx
index 56e8dbc6e1051d7..d6bb571fc9be330 100644
--- a/src/content/changelog/waf/2025-09-15-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-15-waf-release.mdx
@@ -12,11 +12,11 @@ This week's focus highlights newly disclosed vulnerabilities in DevOps tooling,
 
 **Key Findings**
 
-- Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
+* Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
 
-- DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
+* DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
 
-- Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
+* Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
 
 **Impact**
 
@@ -25,50 +25,50 @@ These vulnerabilities expose organizations to serious risks, including credentia
 Administrators are strongly advised to apply vendor patches immediately, rotate exposed credentials, and review access controls to mitigate these risks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
-			</td>
-			<td>100646</td>
-			<td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
-			</td>
-			<td>100874</td>
-			<td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
-			</td>
-			<td>100880</td>
-			<td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
+      </td>
+      <td>100646</td>
+      <td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
+      </td>
+      <td>100874</td>
+      <td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
+      </td>
+      <td>100880</td>
+      <td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-22-waf-release.mdx b/src/content/changelog/waf/2025-09-22-waf-release.mdx
index 054a8348718a766..fd3fff204e42727 100644
--- a/src/content/changelog/waf/2025-09-22-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-22-waf-release.mdx
@@ -10,125 +10,124 @@ This week emphasizes two critical vendor-specific vulnerabilities: a full elevat
 
 **Key Findings**
 
-- Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges.
 
-- Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind).
+* Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges. 
 
-- Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
+* Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind). 
+
+* Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
 
 **Impact**
 
 These vulnerabilities allow attackers to escalate privileges or execute code under conditions where previously they could not:
 
-- Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components.
+* Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components. 
+
+* Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components. 
 
-- Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components.
+* The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
-- The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
-			</td>
-			<td>100146</td>
-			<td>SSRF - Host - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
-			</td>
-			<td>100146B</td>
-			<td>SSRF - Local - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
-			</td>
-			<td>100146C</td>
-			<td>SSRF - Cloud - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="78c856218f2d40f4b5988c8c956c1961" />
-			</td>
-			<td>100714</td>
-			<td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
-			</td>
-			<td>100758</td>
-			<td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
-			</td>
-			<td>100773</td>
-			<td>Next.js - SSRF</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
-			</td>
-			<td>100774</td>
-			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
-			</td>
-			<td>100800_BETA</td>
-			<td>SQLi - Obfuscated Boolean - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule (ID:{" "}
-				<RuleID id="7663ea44178441a0b3205c145563445f" />)
-			</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
+      </td>
+      <td>100146</td>
+      <td>SSRF - Host - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
+      </td>
+      <td>100146B</td>
+      <td>SSRF - Local - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
+      </td>
+      <td>100146C</td>
+      <td>SSRF - Cloud - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="78c856218f2d40f4b5988c8c956c1961" />
+      </td>
+      <td>100714</td>
+      <td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
+      </td>
+      <td>100758</td>
+      <td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
+      </td>
+      <td>100773</td>
+      <td>Next.js - SSRF</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
+      </td>
+      <td>100774</td>
+      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
+      </td>
+      <td>100800_BETA</td>
+      <td>SQLi - Obfuscated Boolean - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule (ID: <RuleID id="7663ea44178441a0b3205c145563445f" />)</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
index 05259d94a3946ba..2a09bf015de4913 100644
--- a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
@@ -10,35 +10,35 @@ This week highlights a critical vendor-specific vulnerability: a deserialization
 
 **Key Findings**
 
-- GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
+* GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
 
 **Impact**
 
 GoAnywhere MFT (CVE-2025-10035): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
-			</td>
-			<td>100787</td>
-			<td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
+      </td>
+      <td>100787</td>
+      <td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-26-waf-release.mdx b/src/content/changelog/waf/2025-09-26-waf-release.mdx
index aeb564538854fe1..b7e0125e8fa0a1a 100644
--- a/src/content/changelog/waf/2025-09-26-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-26-waf-release.mdx
@@ -11,138 +11,138 @@ import { RuleID } from "~/components";
 This update introduces 11 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
-			</td>
-			<td>100859A</td>
-			<td>SQLi - UNION - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
-			</td>
-			<td>100889</td>
-			<td>Command Injection - Generic 9</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c15ca8e8290f485287037665f2be3ddf" />
-			</td>
-			<td>100890</td>
-			<td>Information Disclosure - Common Files - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="56669615f2984c2cac8c608980a252a8" />
-			</td>
-			<td>100891</td>
-			<td>Anomaly:URL - Relative Paths</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c41789fb6370431d809567d17e7d3865" />
-			</td>
-			<td>100894</td>
-			<td>XSS - Inline Function</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
-			</td>
-			<td>100895</td>
-			<td>XSS - DOM</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab8277e3f432400bbd9403dd42978e38" />
-			</td>
-			<td>100896</td>
-			<td>SQLi - MSSQL Length Enumeration</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-			</td>
-			<td>100897</td>
-			<td>Generic Rules - Code Injection - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4375dc90c7af4c55908f6b95c1686741" />
-			</td>
-			<td>100898</td>
-			<td>SQLi - Evasion</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
-			</td>
-			<td>100899</td>
-			<td>SQLi - Probing 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2c20b5e8684043f48620ff77b4026c88" />
-			</td>
-			<td>100900</td>
-			<td>SQLi - Probing</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
+      </td>
+      <td>100859A</td>
+      <td>SQLi - UNION - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
+      </td>
+      <td>100889</td>
+      <td>Command Injection - Generic 9</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c15ca8e8290f485287037665f2be3ddf" />
+      </td>
+      <td>100890</td>
+      <td>Information Disclosure - Common Files - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="56669615f2984c2cac8c608980a252a8" />
+      </td>
+      <td>100891</td>
+      <td>Anomaly:URL - Relative Paths</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c41789fb6370431d809567d17e7d3865" />
+      </td>
+      <td>100894</td>
+      <td>XSS - Inline Function</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
+      </td>
+      <td>100895</td>
+      <td>XSS - DOM</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab8277e3f432400bbd9403dd42978e38" />
+      </td>
+      <td>100896</td>
+      <td>SQLi - MSSQL Length Enumeration</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+      </td>
+      <td>100897</td>
+      <td>Generic Rules - Code Injection - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4375dc90c7af4c55908f6b95c1686741" />
+      </td>
+      <td>100898</td>
+      <td>SQLi - Evasion</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="945c5aa9f45141dd872d7ec920999be0" />
+      </td>
+      <td>100899</td>
+      <td>SQLi - Probing 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2c20b5e8684043f48620ff77b4026c88" />
+      </td>
+      <td>100900</td>
+      <td>SQLi - Probing</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
index 73bca3b78f919ec..93fe72102454c07 100644
--- a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
@@ -10,52 +10,46 @@ This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CV
 
 **Key Findings**
 
-- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
 Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
-			</td>
-			<td>100788</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="51de6ce6596a40eb8200452ad30f768e" />
-			</td>
-			<td>100788A</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
+      </td>
+      <td>100788</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="51de6ce6596a40eb8200452ad30f768e" />
+      </td>
+      <td>100788A</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-29-waf-release.mdx b/src/content/changelog/waf/2025-09-29-waf-release.mdx
index e4a7094b34030a4..b48fadd2caabecb 100644
--- a/src/content/changelog/waf/2025-09-29-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-29-waf-release.mdx
@@ -10,85 +10,82 @@ This week highlights four important vendor- and component-specific issues: an au
 
 **Key Findings**
 
-- SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
+* SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
 
-- Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
+* Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
 
-- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
+* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
 
-- Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
+* Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
 
 **Impact**
 
 These vulnerabilities allow attackers to gain access, escalate privileges, or execute actions that were previously unavailable:
 
-- SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
+* SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
 
-- Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
+* Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
 
-- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
+* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
 
-- Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
+* Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6fe90532af50427484a5275c8c2e30fb" />
-			</td>
-			<td>100717</td>
-			<td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged to 100717 in legacy WAF and{" "}
-				<RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
-			</td>
-			<td>100775</td>
-			<td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
-			</td>
-			<td>100881</td>
-			<td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
-			</td>
-			<td>100887</td>
-			<td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6fe90532af50427484a5275c8c2e30fb" />
+      </td>
+      <td>100717</td>
+      <td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged to 100717 in legacy WAF and <RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
+      </td>
+      <td>100775</td>
+      <td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
+      </td>
+      <td>100881</td>
+      <td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
+      </td>
+      <td>100887</td>
+      <td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-03-waf-release.mdx b/src/content/changelog/waf/2025-10-03-waf-release.mdx
index f868e1edd121f98..c01420c6f44b5c8 100644
--- a/src/content/changelog/waf/2025-10-03-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-03-waf-release.mdx
@@ -11,248 +11,248 @@ import { RuleID } from "~/components";
 This update introduces 21 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
-			</td>
-			<td>100902</td>
-			<td>Generic Rules - Command Execution - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c3079865ce9a41368657026b514aeeb8" />
-			</td>
-			<td>100908</td>
-			<td>Generic Rules - Command Execution - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
-			</td>
-			<td>100910</td>
-			<td>Generic Rules - Command Execution - 4</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
-			</td>
-			<td>100915</td>
-			<td>Generic Rules - Command Execution - 5</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
-			</td>
-			<td>100899</td>
-			<td>Generic Rules - Content-Type Abuse</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="233364f656ff42b8acc41dcd7996012f" />
-			</td>
-			<td>100914</td>
-			<td>Generic Rules - Content-Type Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1aa695281c954513be3d003b93209312" />
-			</td>
-			<td>100911</td>
-			<td>Generic Rules - Cookie Header Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
-			</td>
-			<td>100905</td>
-			<td>Generic Rules - NoSQL Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
-			</td>
-			<td>100913</td>
-			<td>Generic Rules - NoSQL Injection - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
-			</td>
-			<td>100907</td>
-			<td>Generic Rules - Parameter Pollution</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
-			</td>
-			<td>100906</td>
-			<td>Generic Rules - PHP Object Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed5190bfbe1b45a6a645126334c88168" />
-			</td>
-			<td>100904</td>
-			<td>Generic Rules - Prototype Pollution</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-			</td>
-			<td>100897</td>
-			<td>Generic Rules - Prototype Pollution 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
-			</td>
-			<td>100903</td>
-			<td>Generic Rules - Reverse Shell</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
-			</td>
-			<td>100909</td>
-			<td>Generic Rules - Reverse Shell - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="475d090baead467c88dfabbb565c78b0" />
-			</td>
-			<td>100898</td>
-			<td>Generic Rules - SSJI NoSQL</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f4c7f98934264c9c937eec1212b837a0" />
-			</td>
-			<td>100896</td>
-			<td>Generic Rules - SSRF</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="efd01b814d144e90b36522b311c4fb00" />
-			</td>
-			<td>100895</td>
-			<td>Generic Rules - Template Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="00a9a0d663da4add95b863abd3ed0123" />
-			</td>
-			<td>100895A</td>
-			<td>Generic Rules - Template Injection - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
-			</td>
-			<td>100912</td>
-			<td>Generic Rules - XXE</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
-			</td>
-			<td>100900</td>
-			<td>Relative Paths - Anomaly Headers</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
+      </td>
+      <td>100902</td>
+      <td>Generic Rules - Command Execution - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c3079865ce9a41368657026b514aeeb8" />
+      </td>
+      <td>100908</td>
+      <td>Generic Rules - Command Execution - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
+      </td>
+      <td>100910</td>
+      <td>Generic Rules - Command Execution - 4</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
+      </td>
+      <td>100915</td>
+      <td>Generic Rules - Command Execution - 5</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
+      </td>
+      <td>100899</td>
+      <td>Generic Rules - Content-Type Abuse</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="233364f656ff42b8acc41dcd7996012f" />
+      </td>
+      <td>100914</td>
+      <td>Generic Rules - Content-Type Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="1aa695281c954513be3d003b93209312" />
+      </td>
+      <td>100911</td>
+      <td>Generic Rules - Cookie Header Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
+      </td>
+      <td>100905</td>
+      <td>Generic Rules - NoSQL Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
+      </td>
+      <td>100913</td>
+      <td>Generic Rules - NoSQL Injection - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
+      </td>
+      <td>100907</td>
+      <td>Generic Rules - Parameter Pollution</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
+      </td>
+      <td>100906</td>
+      <td>Generic Rules - PHP Object Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed5190bfbe1b45a6a645126334c88168" />
+      </td>
+      <td>100904</td>
+      <td>Generic Rules - Prototype Pollution</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+      </td>
+      <td>100897</td>
+      <td>Generic Rules - Prototype Pollution 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
+      </td>
+      <td>100903</td>
+      <td>Generic Rules - Reverse Shell</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
+      </td>
+      <td>100909</td>
+      <td>Generic Rules - Reverse Shell - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="475d090baead467c88dfabbb565c78b0" />
+      </td>
+      <td>100898</td>
+      <td>Generic Rules - SSJI NoSQL</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f4c7f98934264c9c937eec1212b837a0" />
+      </td>
+      <td>100896</td>
+      <td>Generic Rules - SSRF</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="efd01b814d144e90b36522b311c4fb00" />
+      </td>
+      <td>100895</td>
+      <td>Generic Rules - Template Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="00a9a0d663da4add95b863abd3ed0123" />
+      </td>
+      <td>100895A</td>
+      <td>Generic Rules - Template Injection - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
+      </td>
+      <td>100912</td>
+      <td>Generic Rules - XXE</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
+      </td>
+      <td>100900</td>
+      <td>Relative Paths - Anomaly Headers</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-06-waf-release.mdx b/src/content/changelog/waf/2025-10-06-waf-release.mdx
index 89c8ea1bc8db134..d4f1efa95c7512e 100644
--- a/src/content/changelog/waf/2025-10-06-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-06-waf-release.mdx
@@ -10,124 +10,122 @@ This week’s highlights prioritise an emergency Oracle E-Business Suite RCE rul
 
 **Key Findings**
 
-- New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
+* New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
 
-- Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
+* Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
 
-- Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
+* Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
 
-- Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
+* Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
 
 **Impact**
 
-- CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced.
+* CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced. 
 
-- CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
+* CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
 
-- CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
+* CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
-			</td>
-			<td>100882</td>
-			<td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
-			</td>
-			<td>100883</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a2591ba5befa4815a6861aefef859a04" />
-			</td>
-			<td>100884</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
-			</td>
-			<td>100886</td>
-			<td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="90514c7810694b188f56979826a4074c" />
-			</td>
-			<td>100888</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
-			</td>
-			<td>100916</td>
-			<td>
-				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="badc687a3ba3420a844220b129aa43c3" />
-			</td>
-			<td>100917</td>
-			<td>Generic Rules - SQLi - Inline Comment Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="28fa27511f29428899ceb5a273c10b6f" />
-			</td>
-			<td>100918</td>
-			<td>Generic Rules - SQLi - Information Disclosure</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
+      </td>
+      <td>100882</td>
+      <td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
+      </td>
+      <td>100883</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a2591ba5befa4815a6861aefef859a04" />
+      </td>
+      <td>100884</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
+      </td>
+      <td>100886</td>
+      <td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="90514c7810694b188f56979826a4074c" />
+      </td>
+      <td>100888</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
+      </td>
+      <td>100916</td>
+      <td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="badc687a3ba3420a844220b129aa43c3" />
+      </td>
+      <td>100917</td>
+      <td>Generic Rules - SQLi - Inline Comment Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="28fa27511f29428899ceb5a273c10b6f" />
+      </td>
+      <td>100918</td>
+      <td>Generic Rules - SQLi - Information Disclosure</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>                    
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
index 724fe2ad9d9bcae..fa9d65c7613c3e3 100644
--- a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
@@ -7,9 +7,9 @@ date: 2025-10-07
 import { RuleID } from "~/components";
 
 This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CVE-2025-20333, CVE-2025-20362). This flaw stems from improper input validation in HTTP(S) requests. An authenticated VPN user could send crafted requests to execute code as root, potentially compromising the device.
-The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection.
+The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection. 
 
-- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
@@ -17,31 +17,28 @@ Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables att
 Administrators are strongly advised to apply vendor updates immediately.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
-			</td>
-			<td>100788B</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
+      </td>
+      <td>100788B</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
index fc5674015901639..3001df61385c0d0 100644
--- a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
@@ -47,9 +47,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="72f0ff933fb0492eb71cda50589f2a1d" />
-			</td>
+			<td><RuleID id="72f0ff933fb0492eb71cda50589f2a1d" /></td>
 			<td>N/A</td>
 			<td>Anomaly:Header - name - CR, LF</td>
 			<td>N/A</td>
@@ -58,9 +56,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5d0377e4435f467488614170132fab7e" />
-			</td>
+			<td><RuleID id="5d0377e4435f467488614170132fab7e" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Body</td>
 			<td>N/A</td>
@@ -69,9 +65,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54e32f7f802c4a699182e8921a027008" />
-			</td>
+			<td><RuleID id="54e32f7f802c4a699182e8921a027008" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Header</td>
 			<td>N/A</td>
@@ -80,9 +74,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" />
-			</td>
+			<td><RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - URI</td>
 			<td>N/A</td>
@@ -91,9 +83,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b9f3420674cf481da32333dc8e0cf7ad" />
-			</td>
+			<td><RuleID id="b9f3420674cf481da32333dc8e0cf7ad" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - XXE - Body</td>
 			<td>N/A</td>
@@ -102,9 +92,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ad55483512f0440b81426acdbf8aab5e" />
-			</td>
+			<td><RuleID id="ad55483512f0440b81426acdbf8aab5e" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Common Patterns - Header URI</td>
 			<td>N/A</td>
@@ -113,9 +101,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="849c0618d1674f1c92ba6f9b2e466337" />
-			</td>
+			<td><RuleID id="849c0618d1674f1c92ba6f9b2e466337" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Sleep Function - Header URI</td>
 			<td>N/A</td>
@@ -124,9 +110,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" />
-			</td>
+			<td><RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - String Function - Header URI</td>
 			<td>N/A</td>
@@ -135,9 +119,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fa2055b84af94ba4b925f834b0633709" />
-			</td>
+			<td><RuleID id="fa2055b84af94ba4b925f834b0633709" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - WaitFor Function - Header URI</td>
 			<td>N/A</td>
@@ -146,9 +128,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="158177dec2504acdba1f2da201a076eb" />
-			</td>
+			<td><RuleID id="158177dec2504acdba1f2da201a076eb" /></td>
 			<td>N/A</td>
 			<td>SSRF - Local - Beta</td>
 			<td>N/A</td>
@@ -157,9 +137,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" />
-			</td>
+			<td><RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" /></td>
 			<td>N/A</td>
 			<td>SSRF - Local - 2 - Beta</td>
 			<td>N/A</td>
@@ -168,9 +146,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" />
-			</td>
+			<td><RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" /></td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - Beta</td>
 			<td>N/A</td>
@@ -179,9 +155,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" />
-			</td>
+			<td><RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" /></td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - 2 - Beta</td>
 			<td>N/A</td>
@@ -190,9 +164,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c16f4e133c4541f293142d02e6e8dc5b" />
-			</td>
+			<td><RuleID id="c16f4e133c4541f293142d02e6e8dc5b" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - URI</td>
 			<td>N/A</td>
@@ -201,9 +173,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f4fd9904e7624666b8c49cd62550d794" />
-			</td>
+			<td><RuleID id="f4fd9904e7624666b8c49cd62550d794" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Header</td>
 			<td>N/A</td>
@@ -212,9 +182,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5c0875604f774c36a4f9b69c659d12a6" />
-			</td>
+			<td><RuleID id="5c0875604f774c36a4f9b69c659d12a6" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Body</td>
 			<td>N/A</td>
@@ -223,9 +191,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />
-			</td>
+			<td><RuleID id="fae6fa37ae9249d58628e54b1a3e521e" /></td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -234,9 +200,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9c02e585db34440da620eb668f76bd74" />
-			</td>
+			<td><RuleID id="9c02e585db34440da620eb668f76bd74" /></td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -245,9 +209,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb67fe56a84747b8b64277dc091e296d" />
-			</td>
+			<td><RuleID id="cb67fe56a84747b8b64277dc091e296d" /></td>
 			<td>N/A</td>
 			<td>HTTP parameter pollution</td>
 			<td>N/A</td>
@@ -256,9 +218,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="443b54d984944cd69043805ee34214ef" />
-			</td>
+			<td><RuleID id="443b54d984944cd69043805ee34214ef" /></td>
 			<td>N/A</td>
 			<td>Prototype Pollution - Common Payloads - Beta</td>
 			<td>N/A</td>
@@ -266,4 +226,4 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-20-waf-release.mdx b/src/content/changelog/waf/2025-10-20-waf-release.mdx
index 3768829710eb921..b566732da2e8dad 100644
--- a/src/content/changelog/waf/2025-10-20-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-20-waf-release.mdx
@@ -10,7 +10,7 @@ This week’s update introduces an enhanced rule that expands detection coverage
 
 **Key Findings**
 
-New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
+New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
 
 **Impact**
 
@@ -38,21 +38,15 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unau
 			<td>Remote Code Execution - Common Bash Bypass - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Remote Code Execution -
-				Common Bash Bypass" (ID:{" "}
-				<RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)
-			</td>
-		</tr>
+			<td>This rule is merged into the original rule "Remote Code Execution - Common Bash Bypass" (ID: <RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)</td>
+		</tr>         
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="185b5df42d1e44e0aeb8f8b8a1118614" />
 			</td>
 			<td>100916A</td>
-			<td>
-				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2
-			</td>
+			<td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -69,4 +63,4 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unau
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
index eff22509bb0f005..968037a9f6bf67c 100644
--- a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ This vulnerability allows unauthenticated attackers to take over customer accoun
 Adobe Commerce (CVE-2025-54236): Exploitation may allow attackers to hijack sessions, execute arbitrary commands, steal data, and disrupt storefronts, resulting in confidentiality and integrity risks for merchants. Administrators are strongly encouraged to apply vendor patches without delay.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
-			</td>
-			<td>N/A</td>
-			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
+      </td>
+      <td>N/A</td>
+      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
index ffa6cd0f4a1e7e6..4deb26e943c3254 100644
--- a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The vulnerability allows unauthenticated attackers to potentially achieve remote
 Successful exploitation of CVE-2025-59287 could enable attackers to hijack sessions, execute arbitrary commands, exfiltrate sensitive data, and disrupt storefront operations. These actions pose significant confidentiality and integrity risks to affected environments. Administrators should apply vendor patches immediately to mitigate exposure.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
-			</td>
-			<td>N/A</td>
-			<td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
+      </td>
+      <td>N/A</td>
+      <td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
index a3359450691e99c..48b39ac6c7cfe22 100644
--- a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The flaw is easily exploitable and allows an unauthenticated attacker with netwo
 Successful exploitation of CVE-2025-61884 may result in unauthorized access to critical business data or full exposure of information accessible through Oracle Configurator. Administrators are strongly advised to apply vendor's patches and recommended mitigations to reduce this exposure.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
-			</td>
-			<td>N/A</td>
-			<td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
+      </td>
+      <td>N/A</td>
+      <td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
index 65a2c278f87407e..c9584fd1902891f 100644
--- a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
@@ -14,31 +14,31 @@ The Metro Development Server exposes an HTTP endpoint that is vulnerable to OS c
 
 **Impact**
 
-Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk.
+Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk. 
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
-			</td>
-			<td>N/A</td>
-			<td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
+      </td>
+      <td>N/A</td>
+      <td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-10-waf-release.mdx b/src/content/changelog/waf/2025-11-10-waf-release.mdx
index 6f0e60f36daadeb..c442f86894866c0 100644
--- a/src/content/changelog/waf/2025-11-10-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-10-waf-release.mdx
@@ -39,7 +39,7 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>    
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -61,6 +61,6 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>        
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-17-waf-release.mdx b/src/content/changelog/waf/2025-11-17-waf-release.mdx
index f34a07d31022e1b..38a33ac01a0985b 100644
--- a/src/content/changelog/waf/2025-11-17-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-17-waf-release.mdx
@@ -63,4 +63,4 @@ This vulnerability allows unauthenticated attackers to gain privileged access to
 			<td>Rule metadata description refined. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
index 92ca15cf695904c..668d5120066318a 100644
--- a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
@@ -41,4 +41,4 @@ Oracle Identity Manager (CVE-2025-61757): Exploitation could allow an unauthenti
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-11-24-waf-release.mdx b/src/content/changelog/waf/2025-11-24-waf-release.mdx
index b7949e4310a105d..40fe7147867f34d 100644
--- a/src/content/changelog/waf/2025-11-24-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-24-waf-release.mdx
@@ -35,9 +35,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 				<RuleID id="b957ace6e9844bf29244401c4e2e1a2e" />
 			</td>
 			<td>N/A</td>
-			<td>
-				FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446
-			</td>
+			<td>FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
@@ -51,11 +49,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - Body - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>
-				This rule has been merged into the original rule "PHP Wrapper Injection
-				- Body" (ID:
-				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)
-			</td>
+			<td>This rule has been merged into the original rule "PHP Wrapper Injection - Body" (ID:<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -66,11 +60,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - URI - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>
-				This rule has been merged into the original rule "PHP Wrapper Injection
-				- URI" (ID:
-				<RuleID id="9c02e585db34440da620eb668f76bd74" />)
-			</td>
+			<td>This rule has been merged into the original rule "PHP Wrapper Injection - URI" (ID:<RuleID id="9c02e585db34440da620eb668f76bd74" />)</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-01-waf-release.mdx b/src/content/changelog/waf/2025-12-01-waf-release.mdx
index bb91b0b857039b3..5c9725909eb48b5 100644
--- a/src/content/changelog/waf/2025-12-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-01-waf-release.mdx
@@ -39,7 +39,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>    
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -49,10 +49,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>XSS - JS Context Escape - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "XSS - JS Context Escape"
-				(ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)
-			</td>
-		</tr>
+			<td>This rule is merged into the original rule "XSS - JS Context Escape" (ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)</td>
+		</tr>  
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
index ff06da00aab5c68..1cdc563f6d10a45 100644
--- a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
@@ -52,4 +52,4 @@ New WAF rule deployed for RCE Generic Framework to block malicious POST requests
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
index e22e9674a2f7a29..317f93bc2050154 100644
--- a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
@@ -15,7 +15,6 @@ Rule description updated to reference React – RCE – CVE-2025-55182 while ret
 **Impact**
 
 Improved classification and traceability with no change to coverage against remote code execution attempts.
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -52,4 +51,4 @@ Improved classification and traceability with no change to coverage against remo
 			<td>Rule metadata description changed. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
index 25b82374c113154..3c6833f7416480d 100644
--- a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
@@ -85,4 +85,4 @@ These updates strengthen protection against React RCE exploitation attempts and
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
index 35ce57a85250982..18c75f46429d216 100644
--- a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
@@ -38,9 +38,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This was labeled as Generic - Server Function Source Code Exposure.
-			</td>
+			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Free Ruleset</td>
@@ -51,9 +49,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This was labeled as Generic - Server Function Source Code Exposure.
-			</td>
+			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -64,9 +60,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - DoS - CVE:CVE-2025-55184</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>
-				This was labeled as Generic – Server Function Resource Exhaustion.
-			</td>
+			<td>This was labeled as Generic – Server Function Resource Exhaustion.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-18-waf-release.mdx b/src/content/changelog/waf/2025-12-18-waf-release.mdx
index 1e89c7251d32210..161f57af1c49b1b 100644
--- a/src/content/changelog/waf/2025-12-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-18-waf-release.mdx
@@ -12,6 +12,10 @@ This week's release focuses on improvements to existing detections to enhance co
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
+
+
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,124 +28,105 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
-			</td>
-			<td>N/A</td>
-			<td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Atlassian Confluence - Code
-				Injection - CVE:CVE-2021-26084" (ID:{" "}
-				<RuleID id="e8c550810618437c953cf3a969e0b97a" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9108ddb347b3497e9f9351640d9206e3" />
-			</td>
-			<td>N/A</td>
-			<td>PostgreSQL - SQLi - Copy - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "PostgreSQL - SQLi - COPY"
-				(ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - Body</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - Header</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6df040f716194070a242967cfd181fb3" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - URI</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Tautology - URI - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Tautology - URI" (ID:{" "}
-				<RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - WaitFor Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - WaitFor Function"
-				(ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="80690005fef342e0ad6bc9af596c741e" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - AND/OR Digit Operator
-				Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Equation 2 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Equation" (ID:{" "}
-				<RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
+      </td>
+      <td>N/A</td>
+      <td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "Atlassian Confluence - Code Injection - CVE:CVE-2021-26084" (ID: <RuleID id="e8c550810618437c953cf3a969e0b97a" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9108ddb347b3497e9f9351640d9206e3" />
+      </td>
+      <td>N/A</td>
+      <td>PostgreSQL - SQLi - Copy - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "PostgreSQL - SQLi - COPY" (ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - Body</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - Header</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6df040f716194070a242967cfd181fb3" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - URI</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Tautology - URI - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Tautology - URI" (ID: <RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - WaitFor Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - WaitFor Function" (ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="80690005fef342e0ad6bc9af596c741e" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Equation 2 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Equation" (ID: <RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)</td>
+    </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-12-waf-release.mdx b/src/content/changelog/waf/2026-01-12-waf-release.mdx
index 4c5e3ce6f9668d0..f98c0a337960ed6 100644
--- a/src/content/changelog/waf/2026-01-12-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-12-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-12
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="72963b917ef74697b5bde02f48a1841a" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT"
-				(ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Benchmark Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Benchmark Function"
-				(ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="72963b917ef74697b5bde02f48a1841a" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT" (ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Benchmark Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Benchmark Function" (ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-15-waf-release.mdx b/src/content/changelog/waf/2026-01-15-waf-release.mdx
index 884dea72d886e11..63c93358717c0b5 100644
--- a/src/content/changelog/waf/2026-01-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-15-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-15
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - String Function" (ID:{" "}
-				<RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Sub Query - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Sub Query" (ID:{" "}
-				<RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - String Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - String Function" (ID: <RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Sub Query - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Sub Query" (ID: <RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-20-waf-release.mdx b/src/content/changelog/waf/2026-01-20-waf-release.mdx
index 1b7ca4114286eb1..0da1e57c513f3ef 100644
--- a/src/content/changelog/waf/2026-01-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-20-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-20
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comment - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Comment" (ID:{" "}
-				<RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Comparison" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Comment - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Comment" (ID: <RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Comparison - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Comparison" (ID: <RuleID id="8166da327a614849bfa29317e7907480" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-26-waf-release.mdx b/src/content/changelog/waf/2026-01-26-waf-release.mdx
index 030699a9d584923..cfb420d9e2809ad 100644
--- a/src/content/changelog/waf/2026-01-26-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-26-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for denial-of-service attempts t
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="aaede80b4d414dc89c443cea61680354" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="930020d567684f19b05fb35b349edbc6" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="aaede80b4d414dc89c443cea61680354" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="930020d567684f19b05fb35b349edbc6" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-02-02-waf-release.mdx b/src/content/changelog/waf/2026-02-02-waf-release.mdx
index cb989e8324478d9..00ed3826f072eeb 100644
--- a/src/content/changelog/waf/2026-02-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-02-02-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for CVE-2025-64459 and CVE-2025-
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7a47683eacce4abd870ab2c630698ff3" />
-			</td>
-			<td>N/A</td>
-			<td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
-			</td>
-			<td>N/A</td>
-			<td>Django SQLI - CVE:CVE-2025-64459</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8f0d5c98bd24460a9305a1558d667511" />
-			</td>
-			<td>N/A</td>
-			<td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
-			<td>Block</td>
-			<td>Block</td>
-			<td>Rule metadata description refined. Detection unchanged.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7a47683eacce4abd870ab2c630698ff3" />
+      </td>
+      <td>N/A</td>
+      <td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
+      </td>
+      <td>N/A</td>
+      <td>Django SQLI - CVE:CVE-2025-64459</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8f0d5c98bd24460a9305a1558d667511" />
+      </td>
+      <td>N/A</td>
+      <td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
+      <td>Block</td>
+      <td>Block</td>
+      <td>Rule metadata description refined. Detection unchanged.</td>
+  </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-02-waf-release.mdx b/src/content/changelog/waf/2026-03-02-waf-release.mdx
index 34e9cc77d392db9..5e417a5421f9c40 100644
--- a/src/content/changelog/waf/2026-03-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-02-waf-release.mdx
@@ -8,6 +8,7 @@ import { RuleID } from "~/components";
 
 This week's release introduces new detections for vulnerabilities in SmarterTools SmarterMail (CVE-2025-52691 and CVE-2026-23760), alongside improvements to an existing Command Injection (nslookup) detection to enhance coverage.
 
+
 **Key Findings**
 
 - CVE-2025-52691: SmarterTools SmarterMail mail server is vulnerable to Arbitrary File Upload, allowing an unauthenticated attacker to upload files to any location on the mail server, potentially enabling remote code execution.
@@ -61,10 +62,8 @@ Successful exploitation of these SmarterMail vulnerabilities could lead to full
 			<td>Command Injection - Nslookup - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Command Injection -
-				Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)
-			</td>
+			<td>This rule is merged into the original rule "Command Injection - Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)</td>
 		</tr>
+          
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
index 82b11cdd62ca859..37ee704eb668c95 100644
--- a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
@@ -36,13 +36,11 @@ Successful exploitation of Ivanti EPMM vulnerability allows unauthenticated remo
 				<RuleID id="5ae86a9bda0c41dbb905132f796ea2f6" />
 			</td>
 			<td>N/A</td>
-			<td>
-				Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340
-			</td>
+			<td>Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr> 
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
diff --git a/src/content/changelog/waf/2026-03-23-waf-release.mdx b/src/content/changelog/waf/2026-03-23-waf-release.mdx
index ca8664ddf6e1b0f..4b55ee8e500a59b 100644
--- a/src/content/changelog/waf/2026-03-23-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-23-waf-release.mdx
@@ -12,6 +12,10 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
+
+
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,58 +28,50 @@ This week's release focuses on new improvements to enhance coverage.
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - URI Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - Header Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="155bb67d1061479e995a38510677175f" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - Body Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
-			</td>
-			<td>N/A</td>
-			<td>
-				PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File
-				Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "PHP, vBulletin, jQuery
-				File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206,
-				CVE:CVE-2019-17132" (ID:{" "}
-				<RuleID id="0f2da91cec674eb58006929e824b817c" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - URI Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - Header Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="155bb67d1061479e995a38510677175f" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - Body Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
+      </td>
+      <td>N/A</td>
+      <td>PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132" (ID: <RuleID id="0f2da91cec674eb58006929e824b817c" />)</td>
+    </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-03-30-waf-release.mdx b/src/content/changelog/waf/2026-03-30-waf-release.mdx
index 7bb86d5b78461dc..1bf0c23738bd886 100644
--- a/src/content/changelog/waf/2026-03-30-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-30-waf-release.mdx
@@ -30,63 +30,61 @@ Successful exploitation of the Fortinet and Magento vulnerabilities could allow
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4f7d513cea424c2a853881982f7f95e9" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - Body</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="60d023f3be414d379428add3319731a4" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - Header - Form</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - URI</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab8a96ed13034d56a81a79e570a36147" />
-			</td>
-			<td>N/A</td>
-			<td>Magento 2 - Unrestricted file upload</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4f7d513cea424c2a853881982f7f95e9" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - Body</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="60d023f3be414d379428add3319731a4" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - Header - Form</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - URI</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab8a96ed13034d56a81a79e570a36147" />
+      </td>
+      <td>N/A</td>
+      <td>Magento 2 - Unrestricted file upload</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
+      </td>
+      <td>N/A</td>
+      <td>Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>    
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-04-15-waf-release.mdx b/src/content/changelog/waf/2026-04-15-waf-release.mdx
index 8027bd3284ff60d..48b63b279a71a7e 100644
--- a/src/content/changelog/waf/2026-04-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-15-waf-release.mdx
@@ -21,7 +21,7 @@ This week's release introduces a new detection for a critical Remote Code Execut
 Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code, gain administrative control over network management infrastructure, or trigger server-side resource exhaustion. Administrators are strongly encouraged to apply official vendor updates.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -31,81 +31,73 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
-			</td>
-			<td>N/A</td>
-			<td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "React Server - DOS -
-				CVE:CVE-2026-23864 - 1" (ID:{" "}
-				<RuleID id="aaede80b4d414dc89c443cea61680354" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
-			</td>
-			<td>N/A</td>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
+      </td>
+      <td>N/A</td>
+      <td>Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
+      </td>
+      <td>N/A</td>
+      <td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>   
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
+      </td>
+      <td>N/A</td>
+      <td>Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "React Server - DOS - CVE:CVE-2026-23864 - 1" (ID: <RuleID id="aaede80b4d414dc89c443cea61680354" />)</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
+      </td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI (beta)</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
+      </td>
+      <td>N/A</td>
+      <td>XSS, HTML Injection - Embed Tag  - URI (beta)</td>
 			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
-			</td>
-			<td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag - URI (beta)</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-21-waf-release.mdx b/src/content/changelog/waf/2026-04-21-waf-release.mdx
index 5a538a69976bfd7..d31b75ad221a27b 100644
--- a/src/content/changelog/waf/2026-04-21-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-21-waf-release.mdx
@@ -23,7 +23,7 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -33,266 +33,285 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="ff8df24181aa4573a81be531ee159e2e" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Command Injection - Generic 8 - uri</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. Previous description was "Command Injection -
-				Generic 8 - uri - Beta"
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection. Previous description was "Command Injection - Generic 8 - uri - Beta"</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9429b63c137247faadeb8a29a15308cf" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Command Injection - Generic 8 - body - Beta</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Command Injection - Generic 8 - body" (ID:{" "}
-				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />
-				). The rule previously known as "Command Injection - Generic 8" is now
-				renamed to "Command Injection - Generic 8 - body".
+				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />). The rule previously known as "Command Injection - Generic 8" is now renamed to "Command Injection - Generic 8 - body".
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>		
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="85aaf5db9e0c4237b87e837e958047ed" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
+      <td>Log</td>
+      <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"MySQL - SQLi - Executable Comment - Body" (ID:{" "}
-				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously
-				known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL -
-				SQLi - Executable Comment - Body".
+				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL - SQLi - Executable Comment - Body".
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d19cd574c4644952881a6f3a582cc559" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="407f9ec8a17348dfba3b9450a16639d3" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d07e6dbf15664b99b37b0d2544f24211" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Magento 2 - Unrestricted file upload - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>     
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="26ef21cb197b44fc8a98b7cebf170a17" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Apache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7f7bc3d28a8e43bf97bd15d68c2ac1a7" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
+      <td>Log</td>
+      <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Sleep Function" (ID:{" "}
 				<RuleID id="2c333735f7b24566b17cb64ef77e8d54" />)
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3872e5638bdf4bf0943a80394dacaeb8" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>   
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="bebce8fadfa94ccab09eb74fed4c9ece" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7a40eed5a8654a50a2598a821dfa64df" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - uri</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="15c6b2ce033949b2a1a9f9454c62e2e7" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - header</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="fc9d800b7a724181af8d5650aab28ea1" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - body</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Probing" (ID: <RuleID id="2c20b5e8684043f48620ff77b4026c88" />)
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing 2 </td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This rule had duplicate detection logic and has been deprecated.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This rule had duplicate detection logic and has been deprecated.
+			</td>
+    </tr> 
+    <tr>
+	      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="f1771273700342758e73cf16d7aa0008" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - UNION in MSSQL - Body</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
-				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL"
-				(ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains
-				updated rule logic.
+				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL" (ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains updated rule logic.
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr> 
+    <tr> 
+	      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - UNION - 3</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This rule had duplicate detection logic and has been deprecated.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This rule had duplicate detection logic and has been deprecated.
+			</td>
+    </tr> 
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
 			</td>
-			<td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag - URI</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag  - URI</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2635275641bf44d4bad6a2e170282f38" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Embed Tag - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="b3d033ea9f364574b0a2ec4223f4d718" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
+			<td>XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers</td>
+      <td>Log</td>
+      <td>Disabled</td>
 			<td>
-				XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers
+				This is a new detection. 
 			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="76c37816ef5c4997ab2080a36978def1" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - Headers</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>           
+</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-27-waf-release.mdx b/src/content/changelog/waf/2026-04-27-waf-release.mdx
index cff93d4886276d7..0693afdefc19da2 100644
--- a/src/content/changelog/waf/2026-04-27-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-27-waf-release.mdx
@@ -12,12 +12,14 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
+
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +29,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,198 +39,188 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
-				This is a new detection. This rule is merged into the original rule
+				This is a new detection.  This rule is merged into the original rule
 				"PostgreSQL - SQLi - COPY - Body (ID:{" "}
-				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />
-				). The rule previously known as "PostgreSQL - SQLi - COPY" is now
-				renamed to "PostgreSQL - SQLi - COPY - Body".
+				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />). The rule previously known as "PostgreSQL - SQLi - COPY" is now renamed to "PostgreSQL - SQLi - COPY - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="71d133c374d94559aa9fdf042903de89" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9f1b1b7fd28a401b9d5c172d1036cfa6" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>  
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="8e40416659334b8ba789365755ff389e" />
 			</td>
-			<td>N/A</td>
+   			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR MAKE_SET/ELT - Body" (ID:{" "}
-				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />
-				). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now
-				renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
+				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="1e0d4372ee1e41b9804b2d5c346487f9" />
 			</td>
-			<td>N/A</td>
+   			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d2c961a164a64cf6b871c9511ac6ceca" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="4dacc0e6f32d4c5da3c2293edd471337" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Common Patterns - Body" (ID:{" "}
-				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />
-				). The rule previously known as "SQLi - Common Patterns" is now renamed
-				to "SQLi - Common Patterns - Body".
+				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />). The rule previously known as "SQLi - Common Patterns" is now renamed to "SQLi - Common Patterns - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="53a374379f2e41e9934791c1975c07b7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9efedebfc371443f9fe7308605b1b06b" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d53a791496d64700870334f4dd0ba3c7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Equation - Body" (ID:{" "}
-				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />
-				). The rule previously known as "SQLi - Equation" is now renamed to
-				"SQLi - Equation - Body".
+				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />). The rule previously known as "SQLi - Equation" is now renamed to "SQLi - Equation - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46efbd3496e64c3f902ad33d3d1c2384" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46b937649a424b7ead90f6d0e1149ea6" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="04d9182545f54ba8a4fa29fe205adbb0" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR Digit Operator Digit - Body" (ID:{" "}
-				<RuleID id="762dd334ed0b4273816e3ff13893c564" />
-				). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is
-				now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
+				<RuleID id="762dd334ed0b4273816e3ff13893c564" />). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a24e7c15503948bc8766481aad2abbaa" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR Digit Operator Digit - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="a24e7c15503948bc8766481aad2abbaa" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - AND/OR Digit Operator Digit - Headers</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+        </tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="0c55eb362df64f92a85aa46753acbc0d" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="18c9879b7e184c559d23c1652b45a97d" />
-			</td>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="18c9879b7e184c559d23c1652b45a97d" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Beta</td>
 			<td>Log</td>
@@ -236,24 +228,22 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Benchmark Function - Body" (ID:{" "}
-				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />
-				). The rule previously known as "SQLi - Benchmark Function" is now
-				renamed to "SQLi - Benchmark Function - Body".
+				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />). The rule previously known as "SQLi - Benchmark Function" is now renamed to "SQLi - Benchmark Function - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2adbc36c52324efcb4681b829889aadc" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="69564af3bc54406080deed72491b28e9" />
 			</td>
@@ -264,7 +254,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="94b1646f0b0b46ec9b96f7742aa649de" />
 			</td>
@@ -275,166 +265,151 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Comparison - Body" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />
-				). The rule previously known as "SQLi - Comparison" is now renamed to
-				"SQLi - Comparison - Body".
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="455ce87681bd4200bf53456c39e3e013" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
+				<RuleID id="8166da327a614849bfa29317e7907480" />). The rule previously known as "SQLi - Comparison" is now renamed to "SQLi - Comparison - Body".
+			</td>
+		</tr>
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="455ce87681bd4200bf53456c39e3e013" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - Comparison - Headers</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+		</tr>	
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="8152816062ed47f69be0f907f4bdb492" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - Comparison - URI</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+		</tr>
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - String Concatenation - Body - Beta</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection. This rule is merged into the original rule "SQLi - String Concatenation - Headers" (ID:{" "}
+				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />).The rule previously known as "SQLi - String Concatenation - Headers" is now renamed to "SQLi - String Concatenation - Body". </td>
+		</tr>	
+        <tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8152816062ed47f69be0f907f4bdb492" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Concatenation - Body - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. This rule is merged into the original rule
-				"SQLi - String Concatenation - Headers" (ID:{" "}
-				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />
-				).The rule previously known as "SQLi - String Concatenation - Headers"
-				is now renamed to "SQLi - String Concatenation - Body".{" "}
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
-			</td>
-			<td>N/A</td>
+            <td>
+                <RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
+            </td>
+            <td>N/A</td>
 			<td>SQLi - String Concatenation - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection.(Former Id was{" "}
-				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)
-			</td>
-		</tr>
+            <td>Block</td>
+			<td>This is a new detection.(Former Id was{" "}
+				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)</td>
+		</tr>		
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - String Concatenation - URI</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection. (Former Id was{" "}
+				<RuleID id="bd19397228404b85aa3797238fae8c84" />)</td>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Concatenation - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. (Former Id was{" "}
-				<RuleID id="bd19397228404b85aa3797238fae8c84" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
-			</td>
-			<td>N/A</td>
+            <td>
+                <RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
+            </td>
+            <td>N/A</td>
 			<td>SQLi - SELECT Expression - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - SELECT Expression - Body" (ID:{" "}
-				<RuleID id="00da180570d34b5bae2121acd0023a36" />
-				). The rule previously known as "SQLi - SELECT Expression" is now
-				renamed to "SQLi - SELECT Expression - Body".
+				<RuleID id="00da180570d34b5bae2121acd0023a36" />). The rule previously known as "SQLi - SELECT Expression" is now renamed to "SQLi - SELECT Expression - Body".
 			</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4073f7b575ff45dfb7621b43630bb223" />
-			</td>
+            <td>
+                <RuleID id="4073f7b575ff45dfb7621b43630bb223" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
-			</td>
+            <td>
+                <RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
-			</td>
+            <td>
+                <RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - ORD and ASCII- Body" (ID:{" "}
-				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />
-				). The rule previously known as "SQLi - ORD and ASCII" is now renamed to
-				"SQLi - ORD and ASCII- Body".
+				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />). The rule previously known as "SQLi - ORD and ASCII" is now renamed to "SQLi - ORD and ASCII- Body".
 			</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
-			</td>
+            <td>
+                <RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="60704f5c5513425c94cf77031d0906b6" />
-			</td>
+            <td>
+                <RuleID id="60704f5c5513425c94cf77031d0906b6" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="700613b191d3479ea2782b4e9fe4eff5" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Destructive Operations</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>					
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
index a13aa934882650b..8e8330ad016a2e7 100644
--- a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows unauthenticated attackers to bypass middleware or
 We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 				<RuleID id="1de95bf6d6374e1099854278e77e4a53" />
 			</td>
 			<td>N/A</td>
-			<td>
-				Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575
-			</td>
+			<td>Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-11-waf-release.mdx b/src/content/changelog/waf/2026-05-11-waf-release.mdx
index ab5ae2ac0485b0a..043c71508d1a2ef 100644
--- a/src/content/changelog/waf/2026-05-11-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-11-waf-release.mdx
@@ -10,12 +10,14 @@ import { RuleID } from "~/components";
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
+
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +27,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -39,8 +41,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Remote Code Execution - Java Deserialization" (ID:{" "}
-				<RuleID id="36b0532eb3c941449afed2d3744305c4" />
-				).
+				<RuleID id="36b0532eb3c941449afed2d3744305c4" />).
 			</td>
 		</tr>
 	</tbody>
diff --git a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
index 044ad5768701d6e..6699189c3e6941d 100644
--- a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows remote attackers to trigger a heap buffer overflo
 We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, avoid `rewrite` directives with `?` in the replacement string followed by `set` or `if` referencing capture groups.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 				<RuleID id="2013e3e58efe4b79a26e214f7e52be73" />
 			</td>
 			<td>N/A</td>
-			<td>
-				nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945
-			</td>
+			<td>nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -51,7 +51,9 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<td>nginx - Remote Code Execution - Heap Spray - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-20-waf-release.mdx b/src/content/changelog/waf/2026-05-20-waf-release.mdx
index e26381409165dae..f6bd07a5a23d740 100644
--- a/src/content/changelog/waf/2026-05-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-20-waf-release.mdx
@@ -15,7 +15,7 @@ import { RuleID } from "~/components";
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,11 +37,9 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>Block</td>
 			<td>
-				This rule is merged into the original rule "Sitecore - Cache Poisoning -
-				CVE:CVE-2025-53693" (ID:{" "}
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-				).
+				This rule is merged into the original rule "Sitecore - Cache Poisoning - CVE:CVE-2025-53693" (ID:{" "}
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />).
 			</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
index e6847cc885baddb..c086c1b5689e944 100644
--- a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
+++ b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
@@ -22,8 +22,8 @@ For more information, refer to [Navigation Types](/web-analytics/data-metrics/di
 
 ### Key benefits
 
-- **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
-- **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
+* **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
+* **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
 
 ### Analyze navigation types in the Cloudflare dashboard
 
diff --git a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
index 023c0a2b71c0c0c..1dbfdc154f12e70 100644
--- a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
@@ -13,14 +13,13 @@ Get started with the new models at `@cf/openai/gpt-oss-120b` and `@cf/openai/gpt
 Check out the [blog](https://blog.cloudflare.com/openai-gpt-oss-on-workers-ai) for more details about the new models, and the [`gpt-oss-120b`](/workers-ai/models/gpt-oss-120b) and [`gpt-oss-20b`](/workers-ai/models/gpt-oss-20b) model pages for more information about pricing and context windows.
 
 ## Responses API
-
 If you call the model through:
-
 - Workers Binding, it will accept/return Responses API – `env.AI.run(“@cf/openai/gpt-oss-120b”)`
 - REST API on `/run` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/run/@cf/openai/gpt-oss-120b`
 - REST API on new `/responses` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses`
 - REST API for OpenAI Compatible endpoint, it will return Chat Completions (coming soon) – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/chat/completions`
 
+
 ```
 curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses \
   -H "Content-Type: application/json" \
@@ -40,9 +39,7 @@ curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses
 ```
 
 ## Code Interpreter
-
 The model is natively trained to support stateful code execution, and we've implemented support for this feature using our [Sandbox SDK](https://github.com/cloudflare/sandbox-sdk) and [Containers](https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/). Cloudflare's Developer Platform is uniquely positioned to support this feature, so we're very excited to bring our products together to support this new use case.
 
 ## Web Search (coming soon)
-
 We are working to implement Web Search for the model, where users can bring their own Exa API Key so the model can browse the Internet.
diff --git a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
index 4a63321c26bcb30..21359bd2975b689 100644
--- a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
@@ -11,7 +11,6 @@ New state-of-the-art models have landed on Workers AI! This time, we're introduc
 As well, we're introuding a new turn detection model that enables you to detect when someone is done speaking — useful for building voice agents!
 
 Read the [blog](https://blog.cloudflare.com/workers-ai-partner-models) for more details and check out some of the new models on our platform:
-
 - [`@cf/deepgram/aura-1`](/workers-ai/models/aura-1) is a text-to-speech model that allows you to input text and have it come to life in a customizable voice
 - [`@cf/deepgram/nova-3`](/workers-ai/models/nova-3) is speech-to-text model that transcribes multilingual audio at a blazingly fast speed
 - [`@cf/pipecat-ai/smart-turn-v2`](/workers-ai/models/smart-turn-v2) helps you detect when someone is done speaking
@@ -55,4 +54,4 @@ async def text_to_speech():
 
 if __name__ == "__main__":
     asyncio.run(text_to_speech())
-```
+```
\ No newline at end of file
diff --git a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
index f19b116401280e9..27cdbf6ba1773e1 100644
--- a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
+++ b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
@@ -12,10 +12,9 @@ We're excited to be a launch partner alongside [Google](https://developers.googl
 Now you can leverage EmbeddingGemma directly through AI Search for your RAG pipelines. EmbeddingGemma's multilingual capabilities make it perfect for global applications that need to understand and retrieve content across different languages with exceptional accuracy.
 
 To use EmbeddingGemma for your AI Search projects:
-
 1. Go to **Create** in the [AI Search dashboard](https://dash.cloudflare.com/?to=/:account/ai/ai-search)
 2. Follow the setup flow for your new RAG instance
 3. In the **Generate Index** step, open up **More embedding models** and select `@cf/google/embeddinggemma-300m` as your embedding model
 4. Complete the setup to create an AI Search
 
-Try it out and let us know what you think!
+Try it out and let us know what you think!
\ No newline at end of file
diff --git a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
index 0f6f06d216ab8ea..479a67c4a458f78 100644
--- a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
+++ b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
@@ -17,9 +17,7 @@ export default {
 		// Perform application logic in Workers here
 
 		// Sample call to an internal API running on ECS in AWS using the binding
-		const response = await env.AWS_VPC_ECS_API.fetch(
-			"https://internal-host.example.com",
-		);
+		const response = await env.AWS_VPC_ECS_API.fetch("https://internal-host.example.com");
 
 		// Additional application logic in Workers
 		return new Response();
diff --git a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
index cd1650bd65edb75..ad672d1184483df 100644
--- a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
+++ b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
@@ -8,13 +8,13 @@ date: 2025-02-07 00:00:00 UTC
 
 ![Import repo or choose template](~/assets/images/workers/choose-template-import-repo.png)
 
-You can now create a Worker by:
+You can now create a Worker by: 
+* **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker. 
+* **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker. 
 
-- **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker.
-- **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker.
-
-With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker.
+With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker. 
 
 To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
 
-These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9).
+These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9). 
+
diff --git a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
index 5b44d0f80ee3d23..f651164ee14bfd0 100644
--- a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
+++ b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
@@ -47,4 +47,4 @@ CPU time was limited.
 For more information on the updates limits, see the documentation on [Wrangler configuration for `cpu_ms`](/workers/wrangler/configuration/#limits)
 and on [Workers CPU time limits](/workers/platform/limits/#cpu-time).
 
-For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
+For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
index 2b8b4d848965a55..d24d77883df382f 100644
--- a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
@@ -1,28 +1,28 @@
 ---
 title: Deploy a Workers application in seconds with one-click
-description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project.
+description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project. 
 products:
   - workers
 date: 2025-04-08 00:00:00 UTC
 ---
-
-You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project!
+You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project! 
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/saas-admin-template)
 
-The Deploy to Cloudflare button:
 
-1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing.
-2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment.
+The Deploy to Cloudflare button: 
+1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
+2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 
-To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL:
+
+To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL: 
 
 ```md
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=<YOUR_GIT_REPO_URL>)
 ```
 
-Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers.
+Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers. 
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
index a03418408567548..b0b15c17427b454 100644
--- a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
+++ b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -7,7 +7,7 @@ date: 2025-04-09
 hidden: false
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig } from "~/components"
 
 The [Workers Observability dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](/workers/observability/logs/workers-logs).
 
@@ -16,7 +16,6 @@ The **Overview** tab shows logs from all your Workers in one place. The **Invoca
 ![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png)
 
 The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:
-
 - Which paths are experiencing the most 5XX errors?
 - What is the wall time distribution by status code for my Worker?
 - What are the slowest requests, and where are they coming from?
@@ -31,7 +30,6 @@ The Query Builder can use any field that you store in your logs as a key to visu
 [Workers Logs](/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.
 
 We've introduced a number of changes during our beta period, including:
-
 - Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
 - Performance improvements to ensure no adverse impact
 - Public [API endpoints](https://developers.cloudflare.com/api/resources/workers/subresources/observability/) for broader consumption
diff --git a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
index b452371c6b814cf..9361cb8dd0b783c 100644
--- a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
+++ b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
@@ -52,4 +52,4 @@ npx wrangler dev --test-scheduled
 curl "http://localhost:8787/cdn-cgi/handler/scheduled?cron=*+*+*+*+*"
 ```
 
-Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
+Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
index 66b3abe85c67f76..1adf754ef15b998 100644
--- a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
+++ b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
@@ -84,4 +84,4 @@ Then test your new Durable Object locally by running `wrangler dev`:
 npx wrangler dev
 ```
 
-Consult the [Durable Objects documentation](/durable-objects/) for more details.
+Consult the [Durable Objects documentation](/durable-objects/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-06-05-open-next-size.mdx b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
index f812ab669e4ae81..dc09195d36386df 100644
--- a/src/content/changelog/workers/2025-06-05-open-next-size.mdx
+++ b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
@@ -15,4 +15,4 @@ This means that users will now see a decrease from 14 to 8MiB (2.3 to 1.6MiB gzi
 Users only need to update to the latest version of `@opennextjs/cloudflare` to automatically benefit from these improvements.
 
 Note that we published [CVE-2005-6087](https://github.com/opennextjs/opennextjs-cloudflare/security/advisories/GHSA-rvpw-p7vw-wj3m) for a SSRF vulnerability in the `@opennextjs/cloudflare` package.
-The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one.
+The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one. 
diff --git a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
index 09e28a32e4a37af..cdfb5847ef6dfaf 100644
--- a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
+++ b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
@@ -17,8 +17,8 @@ These preview URLs are named after your branch and are posted as a comment to ea
 
 Each comment includes **two preview URLs** as shown above:
 
-- **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
-- **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
+* **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
+* **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
 
 ## How it works
 
@@ -39,7 +39,7 @@ wrangler versions upload --preview-alias staging
 
 ## Limitations while in beta
 
-- Only available on the **workers.dev** subdomain (custom domains not yet supported)
-- Requires **Wrangler v4.21.0+**
-- Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
-- Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
+* Only available on the **workers.dev** subdomain (custom domains not yet supported)
+* Requires **Wrangler v4.21.0+**
+* Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
+* Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
diff --git a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
index 62563705d8ffbf1..69b92f1517e3f97 100644
--- a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
+++ b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
@@ -1,17 +1,15 @@
 ---
 title: Increased disk space for Workers Builds
-description:
-  Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
+description: Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
   - workers
 date: 2025-08-04T01:00:00Z
 ---
-
-As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans.
+As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans. 
 
 This provides more space for larger projects, dependencies, and build artifacts while improving overall build reliability.
 
 | Metric     | Free Plan | Paid Plans |
-| ---------- | --------- | ---------- |
+|------------|-----------|------------|
 | Disk Space | 20 GB     | 20 GB      |
 
 All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including CPU, memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
index 38902472bf8ef79..ec55122dca6b4e3 100644
--- a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
+++ b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
@@ -40,7 +40,7 @@ export default {
 		// Background task that should complete even after response is sent
 		cleanupTempData(env.KV_NAMESPACE);
 		return new Response("Hello, World!");
-	},
+	}
 };
 
 function cleanupTempData(kvNamespace) {
diff --git a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
index ac79e16b37b4196..4b869cc6a72861c 100644
--- a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
+++ b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
@@ -19,7 +19,7 @@ Now, Cloudflare automatically truncates long branch names and appends a unique h
 - **Hash generation**: The hash is derived from the full branch name to ensure uniqueness
 - **Stable URLs**: The same branch always generates the same hash across all commits
 
-## Requirements and compatibility
+## Requirements and compatibility 
 
 - **Wrangler 4.30.0 or later**: This feature requires updating to wrangler@4.30.0+
-- **No configuration needed**: Works automatically with existing preview URL setups
+- **No configuration needed**: Works automatically with existing preview URL setups
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-08-11-messagechannel.mdx b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
index c6fc102f02133c4..b73740d15413afb 100644
--- a/src/content/changelog/workers/2025-08-11-messagechannel.mdx
+++ b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
@@ -17,10 +17,10 @@ using the `no_expose_global_message_channel` compatibility flag.
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log("Received message:", event.data);
+	console.log('Received message:', event.data);
 };
 
-port2.postMessage("Hello from port2!");
+port2.postMessage('Hello from port2!');
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -29,13 +29,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-- Transfer lists are currently not supported. This means that you will not be able to transfer
+* Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-  are errors serializing or deserializing the message data. Instead, the error will be thrown when
-  the `postMessage` method is called on the sending port.
-- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+	are errors serializing or deserializing the message data. Instead, the error will be thrown when
+	the `postMessage` method is called on the sending port.
+* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
index 63d4feab2b544fb..c3da28c859aaa68 100644
--- a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
+++ b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
@@ -34,4 +34,4 @@ To keep using the old-style handlers, you can specify the `disable_python_no_glo
 
 </WranglerConfig>
 
-Consult the [Python Workers documentation](/workers/languages/python/) for more details.
+Consult the [Python Workers documentation](/workers/languages/python/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
index 0665a23c274b592..71100f87446e32c 100644
--- a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
+++ b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
@@ -90,16 +90,20 @@ const scriptContent = `
   };
 `;
 
-client.workers.scripts.versions.create("my-worker", {
-	account_id: "123456789",
-	metadata: {
-		main_module: "my-worker.mjs",
-	},
-	files: [
-		await toFile(Buffer.from(scriptContent), "my-worker.mjs", {
-			type: "application/javascript+module",
-		}),
-	],
+client.workers.scripts.versions.create('my-worker', {
+  account_id: '123456789',
+  metadata: {
+    main_module: 'my-worker.mjs',
+  },
+  files: [
+    await toFile(
+      Buffer.from(scriptContent),
+      'my-worker.mjs',
+      {
+        type: "application/javascript+module",
+      }
+    )
+  ]
 });
 ```
 
@@ -111,20 +115,19 @@ Previously when creating a KV value like this:
 
 ```js
 await cf.kv.namespaces.values.update("my-kv-namespace", "key1", {
-	account_id: "123456789",
-	metadata: "my metadata",
-	value: JSON.stringify({
-		hello: "world",
-	}),
+  account_id: "123456789",
+  metadata: "my metadata",
+  value: JSON.stringify({
+    hello: "world"
+  })
 });
 ```
 
 ...and recalling it in your Worker like this:
-
 ```ts
-const value = await c.env.KV.get<{ hello: string }>("key1", "json");
+const value = await c.env.KV.get<{hello: string}>("key1", "json");
 ```
 
-You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}`
+You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}` 
 
 This is fixed in cloudflare-typescript 4.5.0 and will be fixed in cloudflare-python 4.4.0.
diff --git a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
index edafaed88b57a69..26a69c93645b1c1 100644
--- a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
+++ b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
@@ -1,9 +1,9 @@
 ---
-title: "Workers Static Assets: Corrected handling of double slashes in redirect rule paths"
+title: 'Workers Static Assets: Corrected handling of double slashes in redirect rule paths'
 description: Corrected handling of double slashes in redirect rule paths
 date: 2025-08-15
 ---
-
-[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed.
+ 
+[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed. 
 
 If you're serving Static Assets with a `_redirects` file containing a rule like `/ja/* /:splat`, paths with double slashes were previously misinterpreted as external URLs. For example, visiting `/ja//example.com` would incorrectly redirect to `https://example.com` instead of `/example.com` on your domain. This has been fixed and double slashes now correctly resolve as local paths. Note: [Cloudflare Pages](/pages/) was not affected by this issue.
diff --git a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
index bf358c54fd5a98d..607ca9dbee7a667 100644
--- a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
+++ b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
@@ -10,8 +10,8 @@ Wrangler's error screen has received several improvements to enhance your debugg
 
 The error screen now features a refreshed design thanks to [youch](https://www.npmjs.com/package/youch), with support for both light and dark themes, improved source map resolution logic that handles missing source files more reliably, and better error cause display.
 
-| Before                                                                             | After (Light)                                                                                        | After (Dark)                                                                                       |
-| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Before | After (Light) | After (Dark) |
+|--------|---------------|--------------|
 | ![Old error screen](../../../assets/images/workers/changelog/old-error-screen.png) | ![New light theme error screen](../../../assets/images/workers/changelog/new-error-screen-light.png) | ![New dark theme error screen](../../../assets/images/workers/changelog/new-error-screen-dark.png) |
 
 Try it out now with `npx wrangler@latest dev` in your Workers project.
diff --git a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
index 383e128922da73e..d5f72b78d505a8f 100644
--- a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
+++ b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
@@ -3,23 +3,22 @@ title: A new, simpler REST API for Cloudflare Workers (Beta)
 description: Simpler Workers API, SDK methods, and Terraform resources for directly managing Workers, Versions, and Deployments
 date: 2025-09-04
 ---
-
-You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
+You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
 
 This new API is supported in the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) and the [Cloudflare Typescript SDK](https://github.com/cloudflare/cloudflare-typescript), allowing platform teams to manage a Worker's infrastructure in Terraform, while development teams handle code deployments from a separate repository or workflow. We also designed this API with AI agents in mind, as a clear, predictable structure is essential for them to reliably build, test, and deploy applications.
 
 ### Try it out
-
 - [**New beta API endpoints**](/api/resources/workers/subresources/beta/)
 - [**Cloudflare TypeScript SDK v5.0.0**](https://github.com/cloudflare/cloudflare-typescript)
 - [**Cloudflare Go SDK v6.0.0**](https://github.com/cloudflare/cloudflare-go)
 - [**Terraform provider v5.9.0**](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs): [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) , [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version), and [`cloudflare_workers_deployments`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_deployment) resources.
 - See full examples in our [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 
-## Before: Eight+ endpoints with mixed responsibilities
 
+## Before: Eight+ endpoints with mixed responsibilities
 ![**Before**](~/assets/images/workers/platform/api-before.png)
 
+
 The existing API was originally designed for simple, one-shot script uploads:
 
 ```sh
@@ -41,17 +40,15 @@ This API worked for creating a basic Worker, uploading all of its code, and depl
 
 - **Several endpoints implicitly created deployments**: Simple updates like adding a secret or changing a script's content would implicitly create a new version and immediately deploy it.
 
-- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities. This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
+- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities.  This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
 
 - **Scripts used names as primary identifiers**: This meant simple renames could turn into a risky migration, requiring you to create a brand new Worker and update every reference. If you were using Terraform, this could inadvertently destroy your Worker altogether.
 
 ## After: Three resources with clear boundaries
-
 ![**After**](~/assets/images/workers/platform/api-after.png)
-The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
+The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
 
 All endpoints now use simple JSON payloads, with script content embedded as `base64`-encoded strings -- a more consistent and reliable approach than the previous `multipart/form-data` format.
-
 - **Worker**: The parent resource representing your application. It has a stable UUID and holds persistent settings like `name`, `tags`, and `logpush`. You can now create a Worker to establish its identity and settings **before** any code is uploaded.
 
 - **Version**: An immutable snapshot of your code and its specific configuration, like bindings and `compatibility_date`. Creating a new version is a safe action that doesn't affect live traffic.
@@ -69,52 +66,44 @@ All endpoints now use simple JSON payloads, with script content embedded as `bas
 Workers are now standalone resources that can be created and configured without any code. Platform teams can provision Workers with the right settings, then hand them off to development teams for implementation.
 
 #### Example: Typescript SDK
-
 ```ts
 // Step 1: Platform team creates the Worker resource (no code needed)
 const worker = await client.workers.beta.workers.create({
-	name: "payment-service",
-	account_id: "...",
-	observability: {
-		enabled: true,
-	},
+  name: "payment-service",
+  account_id: "...",
+  observability: {
+    enabled: true,
+  },
 });
 
 // Step 2: Development team adds code and creates a version later
 const version = await client.workers.beta.workers.versions.create(worker.id, {
-	account_id: "...",
-	main_module: "worker.js",
-	compatibility_date: "$today",
-	bindings: [
-		/*...*/
-	],
-	modules: [
-		{
-			name: "worker.js",
-			content_type: "application/javascript+module",
-			content_base64: Buffer.from(scriptContent).toString("base64"),
-		},
-	],
+  account_id: "...",
+  main_module: "worker.js",
+  compatibility_date: "$today",
+  bindings: [ /*...*/ ],
+  modules: [
+    {
+      name: "worker.js",
+      content_type: "application/javascript+module",
+      content_base64: Buffer.from(scriptContent).toString("base64"),
+    },
+  ],
 });
 
 // Step 3: Deploy explicitly when ready
-const deployment = await client.workers.scripts.deployments.create(
-	worker.name,
-	{
-		account_id: "...",
-		strategy: "percentage",
-		versions: [
-			{
-				percentage: 100,
-				version_id: version.id,
-			},
-		],
-	},
-);
-```
-
+const deployment = await client.workers.scripts.deployments.create(worker.name, {
+  account_id: "...",
+  strategy: "percentage",
+  versions: [
+    {
+      percentage: 100,
+      version_id: version.id,
+    },
+  ],
+});
+````
 #### Example: Terraform
-
 If you use Terraform, you can now declare the Worker in your Terraform configuration and manage configuration outside of Terraform in your Worker's [`wrangler.jsonc` file](/workers/wrangler/configuration/) and deploy code changes using [Wrangler](/workers/wrangler/).
 
 ```tf
@@ -160,7 +149,6 @@ POST /workers/scripts/{script_name}/deployments
 ```
 
 ### Settings are clearly organized by scope
-
 Configuration is now logically divided: [**Worker settings**](/api/resources/workers/subresources/beta/subresources/workers/) (like `name` and `tags`) persist across all versions, while [**Version settings**](/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) (like `bindings` and `compatibility_date`) are specific to each code snapshot.
 
 ```sh
@@ -192,15 +180,13 @@ The `/workers/workers/` path now supports addressing a Worker by both its immuta
 GET /workers/workers/29494978e03748669e8effb243cf2515  # UUID (stable for automation)
 GET /workers/workers/payment-service                  # Name (convenient for humans)
 ```
-
 This dual approach means:
+  - Developers can use readable names for debugging.
+  - Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
+  - Terraform can rename Workers without destroying and recreating them.
 
-- Developers can use readable names for debugging.
-- Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
-- Terraform can rename Workers without destroying and recreating them.
 
 ## Learn more
-
 - [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 - [API documentation](/api/resources/workers/subresources/beta/)
 - [Versions and Deployments overview](/workers/configuration/versions-and-deployments/)
@@ -209,4 +195,4 @@ This dual approach means:
 
 - The pre-existing Workers REST API remains fully supported. Once the new API exits beta, we'll provide a migration timeline with ample notice and comprehensive migration guides.
 - Existing Terraform resources and SDK methods will continue to be fully supported through the current major version.
-- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
+- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
index 08db5550e9f1847..8226df15cb8f922 100644
--- a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
+++ b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
@@ -1,22 +1,19 @@
 ---
 title: Increased vCPU for Workers Builds on paid plans
-description:
-  Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
+description: Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
   - workers
 date: 2025-09-18
 ---
-
-We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.
+We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.  
 
 These changes continue our focus on making [Workers Builds](/workers/ci-cd/builds/) faster and more reliable.
 
-| Metric | Free Plan | Paid Plans |
-| ------ | --------- | ---------- |
-| CPU    | 2 vCPU    | **4 vCPU** |
+| Metric     | Free Plan | Paid Plans |
+|------------|-----------|------------|
+| CPU |  2 vCPU  |  **4 vCPU**  |
 
 ## Performance Improvements
-
-- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs
+- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs 
 - **2x faster multi-threaded builds**: Tools like [esbuild](https://esbuild.github.io/) and [webpack](https://webpack.js.org/) can now utilize additional cores, delivering near-linear performance scaling
 
-All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
+All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
index 52947b26e2a263c..ca46348805446ca 100644
--- a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
+++ b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
@@ -11,13 +11,11 @@ Deploying static site to Workers is now easier. When you run `wrangler deploy [d
 ## Before and after
 
 **Before:** Required remembering multiple flags and parameters
-
 ```bash
 wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project
 ```
 
 **After:** Simple directory deployment with guided setup
-
 ```bash
 wrangler deploy dist
 # Interactive prompts handle the rest as shown in the example flow below
@@ -26,14 +24,12 @@ wrangler deploy dist
 ## What's new
 
 **Interactive prompts for missing configuration:**
-
 - Wrangler detects when you're trying to deploy a directory of static assets
 - Prompts you to confirm the deployment type
 - Asks for a project name (with smart defaults)
 - Automatically sets the compatibility date to today
 
 **Automatic configuration generation:**
-
 - Creates a `wrangler.jsonc` file with your deployment settings
 - Stores your choices for future deployments
 - Eliminates the need to remember complex command-line flags
@@ -64,3 +60,4 @@ wrangler deploy
 ## Requirements
 
 - You must use Wrangler version 4.24.4 or later in order to use this feature
+
diff --git a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
index 8dc771049e2038d..50813da8dd6bb74 100644
--- a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
@@ -10,4 +10,4 @@ We've updated our "Built with Cloudflare" button to make it easier to share that
 
 ![Built with Cloudflare](https://workers.cloudflare.com/built-with-cloudflare.svg)
 
-Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
+Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
index b36f8560a42c020..ad92d184dcdbf29 100644
--- a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
+++ b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
@@ -5,15 +5,14 @@ products:
   - workers
 date: 2025-09-11
 ---
-
 The number of recent versions available for a Worker rollback has been increased from 10 to 100.
 
-This allows you to:
+This allows you to: 
 
-- Promote any of the 100 most recent versions to be the active deployment.
+* Promote any of the 100 most recent versions to be the active deployment. 
 
-- Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
 
 You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/general/#rollback)
 
-Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/).
+Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 
diff --git a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
index 36d8857e5b5101a..b43c774dfedb8db 100644
--- a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
+++ b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
@@ -1,15 +1,13 @@
 ---
 title: Preview URLs now default to opt-in
-description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in.
+description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in. 
 date: 2025-09-17
 ---
-
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers.
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
 
 ## One-Time Update for Workers with workers.dev Disabled
-
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
 
 Because preview URLs were historically enabled by default, users who had intentionally disabled their workers.dev route may not have realized their Worker was still accessible at a separate preview URL. This update was performed to ensure that using a preview URL is always an intentional, opt-in choice.
diff --git a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
index 2e03e6d00a562e1..f4d8ebd421fb775 100644
--- a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
+++ b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
@@ -5,8 +5,8 @@ products:
   - workers
 date: 2025-09-19
 ---
-
-[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA).
+ 
+[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA). 
 
 The `ratelimit` binding is now stable and recommended for all production workloads. Existing deployments using the unsafe binding will continue to function to allow for a smooth transition.
 
diff --git a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
index ae4a4020187a762..0af736a78a816cc 100644
--- a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
+++ b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
@@ -13,6 +13,7 @@ wrangler dev --config ./web/wrangler.jsonc --config ./api/wrangler.jsonc
 ```
 
 Previously, if you ran the command above and then also ran wrangler dev for a different Worker, the Workers running in separate wrangler dev sessions could not communicate with each other. This prevented you from being able to use [Service Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) and [Tail Workers](https://developers.cloudflare.com/workers/observability/logs/tail-workers/) in local development, when running separate wrangler dev sessions.
+	
 Now, the following works as expected:
 
 ```sh
@@ -27,17 +28,17 @@ These Workers can now communicate with each other across separate dev commands,
 
 ```js title="./api/src/index.ts"
 export default {
-	async fetch(request, env) {
-		// This service binding call now works across dev commands
-		const authorized = await env.AUTH.isAuthorized(request);
+  async fetch(request, env) {
+    // This service binding call now works across dev commands
+    const authorized = await env.AUTH.isAuthorized(request);
 
-		if (!authorized) {
-			return new Response("Unauthorized", { status: 401 });
-		}
+    if (!authorized) {
+      return new Response('Unauthorized', { status: 401 });
+    }
 
-		return new Response("Hello from API Worker!", { status: 200 });
-	},
+    return new Response('Hello from API Worker!', { status: 200 });
+  },
 };
 ```
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
+Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
index efbdbc961f780a8..811b7c54cb413df 100644
--- a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
@@ -1,19 +1,17 @@
 ---
 title: Workers Analytics Engine adds supports for new SQL functions
-description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions!
+description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions! 
 date: 2025-10-02
 products:
   - workers-analytics-engine
 ---
-
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
-
 - `argMin()` - Returns the value associated with the minimum in a group
 - `argMax()` - Returns the value associated with the maximum in a group
 - `topK()` - Returns an array of the most frequent values in a group
@@ -22,7 +20,6 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `last_value()` - Returns the last value in an ordered set of values within a partition
 
 [**New bit functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/bit-functions/)
-
 - `bitAnd()` - Returns the bitwise AND of two expressions
 - `bitCount()` - Returns the number of bits set to one in the binary representation of a number
 - `bitHammingDistance()` - Returns the number of bits that differ between two numbers
@@ -36,28 +33,24 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `bitXor()` - Returns the bitwise exclusive-or of two expressions
 
 [**New mathematical functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/mathematical-functions/)
-
 - `abs()` - Returns the absolute value of a number
 - `log()` - Computes the natural logarithm of a number
-- `round()` - Rounds a number to a specified number of decimal places
+- `round()` - Rounds a number to a specified number of decimal places  
 - `ceil()` - Rounds a number up to the nearest integer
 - `floor()` - Rounds a number down to the nearest integer
 - `pow()` - Returns a number raised to the power of another number
 
 [**New string functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/string-functions/)
-
 - `lowerUTF8()` - Converts a string to lowercase using UTF-8 encoding
 - `upperUTF8()` - Converts a string to uppercase using UTF-8 encoding
 
 [**New encoding functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/encoding-functions/)
-
 - `hex()` - Converts a number to its hexadecimal representation
-- `bin()` - Converts a string to its binary representation
+- `bin()` - Converts a string to its binary representation 
 
 [**New type conversion functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/type-conversion-functions/)
-
 - `toUInt8()` - Converts any numeric expression, or expression resulting in a string representation of a decimal, into an unsigned 8 bit integer
 
-## Ready to get started?
 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
+## Ready to get started? 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
diff --git a/src/content/changelog/workers/2025-09-26-ctx-exports.md b/src/content/changelog/workers/2025-09-26-ctx-exports.md
index 19bcc4be7d98ad5..ca40c83e6442e7d 100644
--- a/src/content/changelog/workers/2025-09-26-ctx-exports.md
+++ b/src/content/changelog/workers/2025-09-26-ctx-exports.md
@@ -12,17 +12,17 @@ Example:
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class Greeter extends WorkerEntrypoint {
-	greet(name) {
-		return `Hello, ${name}!`;
-	}
+  greet(name) {
+    return `Hello, ${name}!`;
+  }
 }
 
 export default {
-	async fetch(request, env, ctx) {
-		let greeting = await ctx.exports.Greeter.greet("World");
-		return new Response(greeting);
-	},
-};
+  async fetch(request, env, ctx) {
+    let greeting = await ctx.exports.Greeter.greet("World")
+    return new Response(greeting);
+  }
+}
 ```
 
 At present, you must use [the `enable_ctx_exports` compatibility flag](/workers/configuration/compatibility-flags#enable-ctxexports) to enable this API, though it will be on by default in the future.
diff --git a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
index 7ae62260c3c8ae4..374f4f9426567ed 100644
--- a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
@@ -5,8 +5,7 @@ products:
   - workers
 date: 2025-10-09
 ---
-
-import { Code } from "astro-expressive-code/components";
+import { Code } from 'astro-expressive-code/components';
 
 You can now upload Workers with [static assets](/workers/static-assets/) (like HTML, CSS, JavaScript, images) with the [Cloudflare Terraform provider v5.11.0](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), making it even easier to deploy and manage full-stack apps with IaC.
 
@@ -16,12 +15,14 @@ You can now upload Workers with [static assets](/workers/static-assets/) (like H
 
 You can get started today with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), using either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), or the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+
 ## Examples
 
 #### With `cloudflare_workers_script`
 
 Here's how you can use the existing [`cloudflare_workers_script`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_script) resource to upload your Worker code and assets in one shot.
 
+
 ```hcl
 resource "cloudflare_workers_script" "my_app" {
   account_id  = var.account_id
@@ -81,11 +82,10 @@ resource "cloudflare_workers_deployment" "my_app_deployment" {
 ```
 
 ## What's changed
+Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for *only* those changed files.
 
-Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for _only_ those changed files.
 
 ## Try it out
-
-- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
+-  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
 - You can use either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script) to upload your Worker code and assets in one resource.
 - Or you can use the new beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version) (along with the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment)) resources to more granularly control the lifecycle of each Worker resource.
diff --git a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
index 8305f662b5ae806..a48ee31b4bd8245 100644
--- a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
@@ -20,9 +20,9 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 # Examples
-
 Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+
 #### With `cloudflare_workflow` and `cloudflare_workers_script`
 
 ```hcl
@@ -44,10 +44,11 @@ resource "cloudflare_workflow" "workflow" {
 
 ```
 
-#### With `cloudflare_workflow`, and the new beta resources
 
+#### With `cloudflare_workflow`, and the new beta resources
 You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
+
 ```hcl
 
 resource "cloudflare_worker" "workflow_worker" {
@@ -88,5 +89,4 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 ## Try it out
-
-- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
+-  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
index 60b2deb83ab1bbe..7e4144ec5e29a50 100644
--- a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
+++ b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
@@ -3,23 +3,20 @@ title: Workers Preview URL default behavior now matches your workers.dev setting
 description: If a Workers Preview URL setting is not explicitly configured, its default behavior will now match the setting of the workers.dev subdomain.
 date: 2025-10-23
 ---
-
 We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/configuration/previews/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
 
 This change is intended to provide a more intuitive and secure experience by aligning your preview URL's default state with your `workers.dev` configuration to prevent cases where a preview URL might remain public even after you disabled your `workers.dev` route.
 
 **What this means for you:**
-
 - **If neither setting is configured:** both the workers.dev route and the preview URL will default to enabled
 - **If your workers.dev route is enabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to enabled
 - **If your workers.dev route is disabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to disabled
 
-You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file).
+You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file). 
 
 **Wrangler Version Behavior**
 
 The default behavior depends on the version of Wrangler you are using. This new logic applies to the latest version. Here is a summary of the behavior across different versions:
-
 - **Before v4.34.0:** Preview URLs defaulted to enabled, regardless of the workers.dev setting.
 - **v4.34.0 up to (but not including) v4.44.0:** Preview URLs defaulted to disabled, regardless of the workers.dev setting.
 - **v4.44.0 or later:** Preview URLs now default to matching your workers.dev setting.
@@ -30,7 +27,7 @@ In July, [we introduced preview URLs to Workers](/changelog/2025-07-23-workers-p
 
 To address this, we made a [one-time update](/changelog/2025-09-17-update-preview-url-setting/) to disable preview URLs on existing Workers that had their workers.dev route disabled and changed the default behavior to be disabled for all new deployments where a preview URL setting was not explicitly configured.
 
-While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience.
+While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience. 
 
 **Securing access to `workers.dev` and preview URL endpoints**
 
diff --git a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
index a4a42cacd6469f1..8d5b16c36bd1a5c 100644
--- a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
+++ b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
 
 Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
 
-Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
+Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag. 
 
 To use this feature, update to wrangler@4.45.0 and add bindings to your config file _without_ resource IDs e.g.:
 
diff --git a/src/content/changelog/workers/2025-10-30-builds-preview.mdx b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
index b18b3bf98b7469f..6d384a223acd212 100644
--- a/src/content/changelog/workers/2025-10-30-builds-preview.mdx
+++ b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
@@ -10,8 +10,8 @@ You can now access [preview URLs](/workers/configuration/previews/) directly fro
 
 ![preview button](src/assets/images/changelog/workers/builds-preview-button.png)
 
-**What's new**
 
-- A **Preview** button now appears in the top-right corner of the build details page for successful builds
-- Click it to instantly open the latest preview URL
-- Matches the same experience you're familiar with from Pages
+**What's new**
+* A **Preview** button now appears in the top-right corner of the build details page for successful builds
+* Click it to instantly open the latest preview URL
+* Matches the same experience you're familiar with from Pages
diff --git a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
index 3d8cbe449a7111e..f405d7512be43a7 100644
--- a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
+++ b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
@@ -11,7 +11,6 @@ Wrangler now supports using the `CLOUDFLARE_ENV` [environment variable](/workers
 ## What's new
 
 **Environment selection via environment variable:**
-
 - Set `CLOUDFLARE_ENV` to specify which environment to use for Wrangler commands
 - Works with all Wrangler commands that support the `--env` flag
 - The `--env` command line argument takes precedence over the `CLOUDFLARE_ENV` environment variable
diff --git a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
index cbf3d01a00ba625..aa66f983da252d7 100644
--- a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
@@ -5,21 +5,18 @@ date: 2025-11-12
 products:
   - workers-analytics-engine
 ---
-
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
-
 - `countIf()` - count the number of rows which satisfy a provided condition
 - `sumIf()` - calculate a sum from rows which satisfy a provided condition
 - `avgIf()` - calculate an average from rows which satisfy a provided condition
 
 [**New date and time functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/date-time-functions/)
-
 - `toYear()`
 - `toMonth()`
 - `toDayOfMonth()`
@@ -39,6 +36,5 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `today()`
 - `toYYYYMM()`
 
-## Ready to get started?
-
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
+## Ready to get started? 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
diff --git a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
index 8a813cefea8b895..1151c4807768e2e 100644
--- a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
+++ b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
@@ -12,4 +12,4 @@ We've published build image policies for [Workers Builds](/workers/ci-cd/builds/
 - **Major version updates**: Before preinstalled software reaches end-of-life, we update to the next stable LTS version with 3 months’ notice.
 - **Build image version deprecation (Pages only)**: We provide 6 months’ notice before deprecation. Projects on v1 or v2 will be automatically moved to v3 on their specified deprecation dates.
 
-To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
+To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
index f8224767a58f981..073712734586f32 100644
--- a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
@@ -17,11 +17,11 @@ We set up a benchmark that imports common packages ([httpx](https://www.python-h
 [fastapi](https://fastapi.tiangolo.com/) and [pydantic](https://docs.pydantic.dev/latest/))
 to see how Python Workers stack up against other platforms:
 
-| Platform                  | Mean Cold Start (ms) |
-| ------------------------- | -------------------- |
-| Cloudflare Python Workers | 1027                 |
-| AWS Lambda                | 2502                 |
-| Google Cloud Run          | 3069                 |
+| Platform | Mean Cold Start (ms) |
+|----------|----------------------|
+| Cloudflare Python Workers | 1027 |
+| AWS Lambda | 2502 |
+| Google Cloud Run | 3069 |
 
 These benchmarks run continuously. You can view the results and the methodology on our [benchmark page](https://cold.edgeworker.net).
 
diff --git a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
index 6889ac1e31e515b..47424c741ce45c1 100644
--- a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
@@ -37,4 +37,5 @@ uv run pywrangler deploy
 
 Pywrangler automatically downloads and vendors the necessary packages for your Worker, and these packages are bundled with the Worker when you deploy.
 
+
 Consult the [Python packages documentation](/workers/languages/python/packages/) for full details on Pywrangler and Python package management in Workers.
diff --git a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
index 46b90006bdbbd44..2890f89b49db4ef 100644
--- a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
@@ -8,4 +8,4 @@ date: 2025-12-08
 
 When using the [Cloudflare Vite plugin](/workers/vite-plugin/) to build and deploy Workers, a Wrangler configuration file is now optional for assets-only (static) sites. If no `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` file is found, the plugin generates sensible defaults for an assets-only site. The `name` is based on the `package.json` or the project directory name, and the `compatibility_date` uses the latest date supported by your installed Miniflare version.
 
-This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
+This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
index 7be9426da4e23de..b18355b4e98ed59 100644
--- a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
@@ -103,4 +103,4 @@ export default defineConfig({
 });
 ```
 
-For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
+For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
index c171a822bbc5fa6..64b1e78e3c965cc 100644
--- a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
+++ b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
@@ -15,9 +15,9 @@ import { createExecutionContext } from "cloudflare:test";
 import { it, expect } from "vitest";
 
 it("can access ctx.exports", async () => {
-	const ctx = createExecutionContext();
-	const result = await ctx.exports.MyEntryPoint.myMethod();
-	expect(result).toBe("expected value");
+  const ctx = createExecutionContext();
+  const result = await ctx.exports.MyEntryPoint.myMethod();
+  expect(result).toBe("expected value");
 });
 ```
 
@@ -28,8 +28,8 @@ import { exports } from "cloudflare:workers";
 import { it, expect } from "vitest";
 
 it("can access imported exports", async () => {
-	const result = await exports.MyEntryPoint.myMethod();
-	expect(result).toBe("expected value");
+  const result = await exports.MyEntryPoint.myMethod();
+  expect(result).toBe("expected value");
 });
 ```
 
diff --git a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
index 7f91b0a340dd8fd..2a6b5bff0742249 100644
--- a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
+++ b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
@@ -6,8 +6,8 @@ products:
 date: 2025-12-19
 ---
 
-[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables
-and bindings, and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
+[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables 
+and bindings,  and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
 
 ```ts title="vite.config.ts"
 import { defineConfig } from "vite";
@@ -15,14 +15,14 @@ import { cloudflare } from "@cloudflare/vite-plugin";
 import { tanstackStart } from "@tanstack/react-start/plugin/vite";
 
 export default defineConfig({
-	plugins: [
-		cloudflare({ viteEnvironment: { name: "ssr" } }),
-		tanstackStart({
-			prerender: {
-				enabled: true,
-			},
-		}),
-	],
+  plugins: [
+    cloudflare({ viteEnvironment: { name: "ssr" } }),
+    tanstackStart({
+      prerender: {
+        enabled: true,
+      },
+    }),
+  ],
 });
 ```
 
diff --git a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
index f027c8fd04d6f0d..c28886f2273eb0a 100644
--- a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
+++ b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
@@ -26,7 +26,6 @@ Key guidance includes:
 ```
 
 </WranglerConfig>
-
 - **Generate binding types with `wrangler types`** — Never hand-write your `Env` interface. Let Wrangler generate it from your actual configuration to catch mismatches at compile time.
 - **Stream request and response bodies** — Avoid buffering large payloads in memory. Use `TransformStream` and `pipeTo` to stay within the 128 MB memory limit and improve time-to-first-byte.
 - **Use bindings, not REST APIs** — Bindings to KV, R2, D1, Queues, and other Cloudflare services are direct, in-process references with no network hop and no authentication overhead.
diff --git a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
index 7e14d709a1a753e..c153f96598e79c4 100644
--- a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
@@ -8,36 +8,31 @@ Four new fields are now available on `request.cf.tlsClientAuth` in Workers for r
 
 ### New fields
 
-| Field                      | Type    | Description                                                                                                                                          |
-| -------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `certRFC9440`              | String  | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented.                                       |
-| `certRFC9440TooLarge`      | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`.                                                                    |
-| `certChainRFC9440`         | String  | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
-| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`.                                                             |
+| Field | Type | Description |
+| --- | --- | --- |
+| `certRFC9440` | String | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented. |
+| `certRFC9440TooLarge` | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`. |
+| `certChainRFC9440` | String | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
+| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`. |
 
 ### Example: forwarding client certificate headers to your origin
 
 ```js
 export default {
-	async fetch(request) {
-		const tls = request.cf.tlsClientAuth;
-
-		// Only forward if cert was verified and chain is complete
-		if (
-			!tls ||
-			!tls.certVerified ||
-			tls.certRevoked ||
-			tls.certChainRFC9440TooLarge
-		) {
-			return new Response("Unauthorized", { status: 401 });
-		}
-
-		const headers = new Headers(request.headers);
-		headers.set("Client-Cert", tls.certRFC9440);
-		headers.set("Client-Cert-Chain", tls.certChainRFC9440);
-
-		return fetch(new Request(request, { headers }));
-	},
+  async fetch(request) {
+    const tls = request.cf.tlsClientAuth;
+
+    // Only forward if cert was verified and chain is complete
+    if (!tls || !tls.certVerified || tls.certRevoked || tls.certChainRFC9440TooLarge) {
+      return new Response("Unauthorized", { status: 401 });
+    }
+
+    const headers = new Headers(request.headers);
+    headers.set("Client-Cert", tls.certRFC9440);
+    headers.set("Client-Cert-Chain", tls.certChainRFC9440);
+
+    return fetch(new Request(request, { headers }));
+  },
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
index c311cbdd393dadd..1a9e3164168578c 100644
--- a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,33 +10,31 @@ Previously, this telemetry was only available via the `Server-Timing: cfL4` resp
 
 ### New properties
 
-| Property        | Type                | Description                                                                                                                                                                  |
-| --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `clientTcpRtt`  | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`.              |
-| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`.                    |
-| `edgeL4`        | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
+| Property | Type | Description |
+| --- | --- | --- |
+| `clientTcpRtt` | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`. |
+| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`. |
+| `edgeL4` | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
 
 ### Example: Log connection quality metrics
 
 ```js
 export default {
-	async fetch(request) {
-		const cf = request.cf;
+  async fetch(request) {
+    const cf = request.cf;
 
-		const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
-		const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
-		const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
+    const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
+    const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
+    const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
 
-		console.log(
-			`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`,
-		);
+    console.log(`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`);
 
-		const headers = new Headers(request.headers);
-		headers.set("X-Client-RTT", String(rtt));
-		headers.set("X-Delivery-Rate", String(deliveryRate));
+    const headers = new Headers(request.headers);
+    headers.set("X-Client-RTT", String(rtt));
+    headers.set("X-Delivery-Rate", String(deliveryRate));
 
-		return fetch(new Request(request, { headers }));
-	},
+    return fetch(new Request(request, { headers }));
+  },
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
index ffd136835ae4bc4..47a711a702b2fba 100644
--- a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
+++ b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
@@ -9,7 +9,7 @@ date: 2026-05-07 12:00:00 UTC
 
 Multiple security vulnerabilities were disclosed by the React team and Vercel affecting React Server Components and Next.js. These include denial of service, middleware and proxy bypass, server-side request forgery, cross-site scripting, and cache poisoning issues across a range of severity levels.
 
-**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`).
+**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`). 
 
 ## WAF protections
 
diff --git a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
index 7f215858ca21722..48963056126296d 100644
--- a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
+++ b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
@@ -10,8 +10,8 @@ date: 2025-01-15
 
 We've also added:
 
-- `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
-- Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
-- Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
+* `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
+* Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
+* Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
 
 We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks.
diff --git a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
index 4f047f473ce8ee4..dbd052de60e2fc7 100644
--- a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
+++ b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
@@ -9,9 +9,9 @@ date: 2025-10-31
 
 We've raised the [Cloudflare Workflows](/workflows/) account-level limits for all accounts on the [Workers paid plan](/workers/platform/pricing/):
 
-- **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
-- **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
+* **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
+* **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
 
-These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/).
+These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/). 
 
 If your application requires a higher limit, fill out the [Limit Increase Request Form](/workers/platform/limits/) or contact your account team. Please refer to [Workflows pricing](/workflows/reference/pricing/) for more information.
diff --git a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
index e29d175b6b83ba6..90eef81c9251ce0 100644
--- a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
+++ b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
@@ -20,4 +20,4 @@ await instance.pause(); // pauses a running workflow instance
 await instance.resume(); // resumes a paused instance
 await instance.restart(); // restarts the instance from the beginning
 await instance.terminate(); // terminates the instance immediately
-```
+```
\ No newline at end of file
diff --git a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
index 93eb46096142460..4afac919aa7d970 100644
--- a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
+++ b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
@@ -7,15 +7,15 @@ products:
 date: 2026-05-01
 ---
 
-You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime.
+You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime. 
 
 The Worker Loader loads Dynamic Workers on demand, which previously made durability challenging. Even within a Dynamic Worker, a Workflow might sleep for hours or days between steps, and by the time it resumes, the original Dynamic Worker code would no longer be in memory.
 
-The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens.
+The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens. 
 
 Because Dynamic Workers are created on-demand, you do not have to register each Workflow up front or manage them individually. Load the Workflow code in the Dynamic Worker when it is needed, and the Workflows engine handles persistence and retries behind the scenes. Your Workflow code itself is unaffected by the routing and behaves as normal.
 
-This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with:
+This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with: 
 
 - **SaaS platforms** where each tenant defines their own automation, such as onboarding sequences, approval chains, or billing retry logic.
 - **AI agent frameworks** where agents generate and execute multi-step plans at runtime, surviving restarts and waiting for human approval between tool calls.
diff --git a/src/content/compatibility-flags/allow-custom-ports.md b/src/content/compatibility-flags/allow-custom-ports.md
index 537127433070005..4a9cf4a9b5f6932 100644
--- a/src/content/compatibility-flags/allow-custom-ports.md
+++ b/src/content/compatibility-flags/allow-custom-ports.md
@@ -22,7 +22,6 @@ For example:
 ```js
 const response = await fetch("https://example.com:8000");
 ```
-
 With allow_custom_ports the above example would fetch `https://example.com:8000` rather than
 `https://example.com:443`.
 
diff --git a/src/content/compatibility-flags/enable-nodejs-http-modules.md b/src/content/compatibility-flags/enable-nodejs-http-modules.md
index 2bfccf48ee0d939..b28f784408c15f9 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-modules.md
@@ -21,10 +21,10 @@ This enables compatibility with Node.js libraries and existing code that
 use the standard node:http and node:https APIs for making HTTP requests.
 The available functionality includes:
 
-- `http.request()` and `https.request()` for making HTTP/HTTPS requests
-- `http.get()` and `https.get()` for making GET requests
-- Request and response objects with standard Node.js APIs
-- Support for standard HTTP methods, headers, and options
+* `http.request()` and `https.request()` for making HTTP/HTTPS requests
+* `http.get()` and `https.get()` for making GET requests
+* Request and response objects with standard Node.js APIs
+* Support for standard HTTP methods, headers, and options
 
 See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html)
 for more details about the Node.js APIs.
diff --git a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
index b4b92da33a8f73b..1e31b6a8b5508a4 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
@@ -20,9 +20,9 @@ server modules.
 This enables compatibility with Node.js libraries and existing code that
 use the standard Node.js HTTP server APIs. The available functionality includes:
 
-- `http.createServer()` for creating HTTP servers
-- `http.Server` class for server instances
-- `http.ServerResponse` for handling server responses
+* `http.createServer()` for creating HTTP servers
+* `http.Server` class for server instances
+* `http.ServerResponse` for handling server responses
 
 This flag must be used in combination with the `enable_nodejs_http_modules` flag
 to enable full features of `node:http`.
@@ -30,4 +30,4 @@ to enable full features of `node:http`.
 This flag is automatically enabled for Workers using
 a compatibility date of 2025-09-01 or later when `nodejs_compat` is enabled.
 
-See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/fetcher-no-get-put-delete.md b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
index dcf2a945b94649b..d38f2d504089ae8 100644
--- a/src/content/compatibility-flags/fetcher-no-get-put-delete.md
+++ b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
@@ -18,3 +18,4 @@ Historically, API objects that had such a `fetch()` method also had methods `get
 These methods were a very early idea from many years ago, but were never actually documented, and therefore rarely (if ever) used. Enabling the `fetcher_no_get_put_delete`, or setting a compatibility date on or after `2024-03-26` disables these methods for your Worker.
 
 This change paves a future path for you to be able to define your own custom methods using these names. Without this change, you would be unable to define your own `get`, `put`, and `delete` methods, since they would conflict with these built-in helper methods.
+
diff --git a/src/content/compatibility-flags/js-weak-refs.md b/src/content/compatibility-flags/js-weak-refs.md
index 061ea4e608cd187..718f8818a545c01 100644
--- a/src/content/compatibility-flags/js-weak-refs.md
+++ b/src/content/compatibility-flags/js-weak-refs.md
@@ -12,7 +12,6 @@ disable_flag: "disable_weak_ref"
 ---
 
 Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry) and [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef) built-ins.
-
 - `FinalizationRegistry` allows you to register a cleanup callback that runs after an object has been garbage-collected.
 - `WeakRef` creates a weak reference to an object, allowing it to be garbage-collected if no other strong references exist.
 
@@ -22,4 +21,4 @@ Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/
 
 :::caution
 These APIs are fundamentally non-deterministic. The timing and execution of garbage collection are unpredictable, and you **should not rely on them for essential program logic**. Additionally, cleanup callbacks registered with `FinalizationRegistry` may **never be executed**, including but not limited to cases where garbage collection is not triggered, or your Worker gets evicted.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/compatibility-flags/new-url-parser-implementation.md b/src/content/compatibility-flags/new-url-parser-implementation.md
index 9ec8017e42ea670..55b21a5be67018c 100644
--- a/src/content/compatibility-flags/new-url-parser-implementation.md
+++ b/src/content/compatibility-flags/new-url-parser-implementation.md
@@ -13,17 +13,17 @@ disable_flag: "url_original"
 
 The original implementation of the [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) API in Workers was not fully compliant with the [WHATWG URL Standard](https://url.spec.whatwg.org/), differing in several ways, including:
 
-- The original implementation collapsed sequences of multiple slashes into a single slash:
+* The original implementation collapsed sequences of multiple slashes into a single slash:
 
   `new URL("https://example.com/a//b").toString() === "https://example.com/a/b"`
 
-- The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
+* The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
 
-- The original implementation would percent-encode or percent-decode certain content differently:
+* The original implementation would percent-encode or percent-decode certain content differently:
 
   `new URL("https://example.com/a%40b?c d%20e?f").toString() === "https://example.com/a@b?c+d+e%3Ff"`
 
-- The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
+* The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
 
 Set the compatibility date of your Worker to a date after `2022-10-31` or enable the `url_standard` compatibility flag to opt-in the fully spec compliant `URL` API implementation.
 
diff --git a/src/content/compatibility-flags/nodejs-compat.md b/src/content/compatibility-flags/nodejs-compat.md
index 6eb72d18070e7de..80bfc4fec1b0734 100644
--- a/src/content/compatibility-flags/nodejs-compat.md
+++ b/src/content/compatibility-flags/nodejs-compat.md
@@ -14,12 +14,12 @@ Enables [Node.js APIs](/workers/runtime-apis/nodejs/) in the Workers Runtime.
 
 Note that some Node.js APIs are only enabled if your Worker's compatibility date is set to on or after the following dates:
 
-| Node.js API                                                                                                                    | Enabled after |
-| ------------------------------------------------------------------------------------------------------------------------------ | ------------- |
-| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)                                 | `2025-09-01`  |
-| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules) | `2025-08-15`  |
-| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)                                 | `2025-04-01`  |
-| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)       | `2024-12-02`  |
+| Node.js API | Enabled after  |
+|---|---|
+| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)  | `2025-09-01`  |
+| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules)  | `2025-08-15`  |
+| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)  | `2025-04-01`  |
+| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)  | `2024-12-02`  |
 
 When enabling `nodejs_compat`, we recommend using the latest version of [Wrangler CLI](/workers/wrangler/), and the latest compatiblity date, in order to maximize compatibility. Some older versions of Wrangler inject additional polyfills that are no longer neccessary, as they are provided by the Workers runtime, if your Worker is using a more recent compatibility date.
 
diff --git a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
index 458d6f154b4f789..82a917d18ac5162 100644
--- a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
+++ b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
@@ -13,29 +13,26 @@ enable_flag: "queue_consumer_no_wait_for_wait_until"
 By default, [Queues](/queues/) Consumer Workers acknowledge messages only after promises passed to [`ctx.waitUntil()`](/workers/runtime-apis/context) have resolved. This behavior can cause queue consumers which utilize `ctx.waitUntil()` to process messages slowly. The default behavior is documented in the [Queues Consumer Configuration Guide](/queues/configuration/javascript-apis#consumer).
 
 This Consumer Worker is an example of a Worker which utilizes `ctx.waitUntil()`. Under the default behavior, this consumer Worker will only acknowledge a batch of messages after the sleep function has resolved.
-
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		// omitted
-	},
-
-	async queue(batch, env, ctx) {
-		console.log(
-			`received batch of ${batch.messages.length} messages to queue ${batch.queue}`,
-		);
-		for (let i = 0; i < batch.messages.length; ++i) {
-			console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
-		}
-		ctx.waitUntil(sleep(30 * 1000));
-	},
+  async fetch(request, env, ctx) {
+    // omitted
+  },
+
+  async queue(batch, env, ctx) {
+    console.log(`received batch of ${batch.messages.length} messages to queue ${batch.queue}`);
+    for (let i = 0; i < batch.messages.length; ++i) {
+      console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
+    }
+    ctx.waitUntil(sleep(30 * 1000));
+  }
 };
 
 function sleep(ms) {
-	return new Promise((resolve) => setTimeout(resolve, ms));
+  return new Promise(resolve => setTimeout(resolve, ms));
 }
 ```
 
 If the `queue_consumer_no_wait_for_wait_until` flag is enabled, Queues consumers will no longer wait for promises passed to `ctx.waitUntil()` to resolve before acknowledging messages. This can improve the performance of queue consumers which utilize `ctx.waitUntil()`. With the flag enabled, in the above example, the consumer Worker will acknowledge the batch without waiting for the sleep function to resolve.
 
-Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
+Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/queues-json-messages.md b/src/content/compatibility-flags/queues-json-messages.md
index 468e5bc0c452ce5..ed871f0ed83b10b 100644
--- a/src/content/compatibility-flags/queues-json-messages.md
+++ b/src/content/compatibility-flags/queues-json-messages.md
@@ -11,4 +11,4 @@ enable_flag: "queues_json_messages"
 disable_flag: "no_queues_json_messages"
 ---
 
-With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
+With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
\ No newline at end of file
diff --git a/src/content/compatibility-flags/request-signal.md b/src/content/compatibility-flags/request-signal.md
index 75a494da250906c..e60e43e66403e2f 100644
--- a/src/content/compatibility-flags/request-signal.md
+++ b/src/content/compatibility-flags/request-signal.md
@@ -5,4 +5,4 @@ enable_flag: "enable_request_signal"
 disable_flag: "disable_request_signal"
 ---
 
-When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
+When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
index 3cdf43761777395..994a6a724e2f465 100644
--- a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
+++ b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
@@ -20,12 +20,12 @@ User code should never try to reuse an `ArrayBuffer` that has been passed into a
 let reader = readable.getReader({ mode: "byob" });
 let arrayBufferView = new Uint8Array(4096);
 while (true) {
-	let result = await reader.read(arrayBufferView);
-	if (result.done) break;
-	// Optionally something with `result` here.
-	// Re-use the same memory for the next `read()` by creating
-	// a new Uint8Array backed by the result's ArrayBuffer.
-	arrayBufferView = new Uint8Array(result.value.buffer);
+  let result = await reader.read(arrayBufferView);
+  if (result.done) break;
+  // Optionally something with `result` here.
+  // Re-use the same memory for the next `read()` by creating
+  // a new Uint8Array backed by the result's ArrayBuffer.
+  arrayBufferView = new Uint8Array(result.value.buffer);
 }
 ```
 
diff --git a/src/content/compatibility-flags/strict-crypto.md b/src/content/compatibility-flags/strict-crypto.md
index 17274d7e485ef60..91a77815dd82fde 100644
--- a/src/content/compatibility-flags/strict-crypto.md
+++ b/src/content/compatibility-flags/strict-crypto.md
@@ -14,7 +14,6 @@ disable_flag: "no_strict_crypto_checks"
 ---
 
 Perform additional error checking in the Web Crypto API to conform with the specification and reject possibly unsafe key parameters:
-
 - For RSA key generation, key sizes are required to be multiples of 128 bits as boringssl may otherwise truncate the key.
 - The size of imported RSA keys must be at least 256 bits and at most 16384 bits, as with newly generated keys.
 - The public exponent for imported RSA keys is restricted to the commonly used values `[3, 17, 37, 65537]`.
diff --git a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
index 3b380e857412453..15ea7891dc4fcad 100644
--- a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
+++ b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
@@ -19,3 +19,4 @@ attribute is encountered that is not recognized.
 
 When the `ignore_unrecognized_import_assertion` flag is set, Workers will
 ignore unrecognized import attributes.
+
diff --git a/src/content/compatibility-flags/to-string-tag.md b/src/content/compatibility-flags/to-string-tag.md
index 6fc298a87c182de..1de8e533db3f8bb 100644
--- a/src/content/compatibility-flags/to-string-tag.md
+++ b/src/content/compatibility-flags/to-string-tag.md
@@ -13,5 +13,5 @@ disable_flag: "do_not_set_tostring_tag"
 
 A change was made to set the Symbol.toStringTag on all Workers API objects
 in order to fix several spec compliance bugs. Unfortunately,
-this change was more breaking than anticipated. The `do_not_set_tostring_tag` compat
+this change was more breaking than anticipated. The `do_not_set_tostring_tag`  compat
 flag restores the original behavior with compatibility dates of 2024-09-26 or earlier.
diff --git a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
index b94637375b11410..ff6e300d56a8451 100644
--- a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
+++ b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
@@ -21,7 +21,7 @@ For an example of how this change could break existing code, consider code that
 ```js
 const usp = new URLSearchParams();
 // ...
-["abc", "xyz"].forEach(usp.delete.bind(usp));
+['abc', 'xyz'].forEach(usp.delete.bind(usp));
 ```
 
 The `forEach()` automatically passes multiple parameters to the function that is passed in. Prior to the addition of the new standard parameters, these extra arguments would have been ignored.
@@ -31,5 +31,5 @@ Now, however, the additional arguments have meaning and change the behavior of t
 ```js
 const usp = new URLSearchParams();
 // ...
-["abc", "xyz"].forEach((key) => usp.delete(key));
-```
+['abc', 'xyz'].forEach((key) => usp.delete(key));
+```
\ No newline at end of file
diff --git a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
index 5a0f4a50358133e..be603aaba1a62ba 100644
--- a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
+++ b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
@@ -19,16 +19,12 @@ Previously, receiving a server-initiated Close frame left the WebSocket in `CLOS
 const [client, server] = Object.values(new WebSocketPair());
 server.accept();
 
-server.addEventListener(
-	"close",
-	(event) => {
-		// readyState is already CLOSED — no need to call server.close().
-		console.log(server.readyState); // WebSocket.CLOSED
-		console.log(event.code); // 1000
-		console.log(event.wasClean); // true
-	},
-	{ once: true },
-);
+server.addEventListener("close", (event) => {
+  // readyState is already CLOSED — no need to call server.close().
+  console.log(server.readyState); // WebSocket.CLOSED
+  console.log(event.code); // 1000
+  console.log(event.wasClean); // true
+}, { once: true });
 ```
 
 If you do still call `close()` inside the handler, the call is silently ignored. This means existing code that manually replies to Close frames will not break when you update your compatibility date.
@@ -41,18 +37,14 @@ const [client, server] = Object.values(new WebSocketPair());
 // Opt into half-open mode for proxying
 server.accept({ allowHalfOpen: true });
 
-server.addEventListener(
-	"close",
-	(event) => {
-		// With allowHalfOpen true, readyState is still CLOSING here,
-		// giving you time to coordinate the close on the other side.
-		console.log(server.readyState); // WebSocket.CLOSING
+server.addEventListener("close", (event) => {
+  // With allowHalfOpen true, readyState is still CLOSING here,
+  // giving you time to coordinate the close on the other side.
+  console.log(server.readyState); // WebSocket.CLOSING
 
-		// Manually close when ready.
-		server.close(1000, "done");
-	},
-	{ once: true },
-);
+  // Manually close when ready.
+  server.close(1000, "done");
+}, { once: true });
 ```
 
 Note that there is no corresponding option to the `WebSocket` constructor. WebSockets constructed with `new WebSocket` will always auto-reply to closes after this flag takes effect. WebSockets constructed this way are automatically "accepted", so there is no opportunity to pass the option to `accept()`. If you are creating a WebSocket with `new WebSocket`, but you need half-open behavior, you will need to switch to using `fetch()` instead.
@@ -63,10 +55,10 @@ let ws = new WebSocket("wss://example.com");
 
 // But you can do this instead:
 let resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { "Upgrade": "websocket" }
 });
 if (!resp.webSocket) {
-	throw new Error("WebSocket handshake not accepted");
+  throw new Error("WebSocket handshake not accepted");
 }
 let ws = resp.webSocket;
 ws.accept({ allowHalfOpen: true });
diff --git a/src/content/compatibility-flags/web-socket-compression.md b/src/content/compatibility-flags/web-socket-compression.md
index 9949b65656e428f..c73d329ee01a83e 100644
--- a/src/content/compatibility-flags/web-socket-compression.md
+++ b/src/content/compatibility-flags/web-socket-compression.md
@@ -15,4 +15,4 @@ The Workers runtime did not support WebSocket compression when the initial WebSo
 
 If the flag is present, the Workers runtime is capable of using WebSocket Compression on both inbound and outbound WebSocket connections.
 
-Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
+Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
\ No newline at end of file
diff --git a/src/content/compatibility-flags/websocket-standard-binary-type.md b/src/content/compatibility-flags/websocket-standard-binary-type.md
index 6e389dad36862eb..81e8b8883ea49f5 100644
--- a/src/content/compatibility-flags/websocket-standard-binary-type.md
+++ b/src/content/compatibility-flags/websocket-standard-binary-type.md
@@ -17,7 +17,7 @@ The `binaryType` property itself is available on every `WebSocket` regardless of
 
 ```js
 const resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -26,7 +26,7 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-	// event.data is an ArrayBuffer for binary frames.
+  // event.data is an ArrayBuffer for binary frames.
 });
 ```
 
diff --git a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
index e0b79d3a85a05ed..9d993472b94bcb7 100644
--- a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
+++ b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
@@ -19,13 +19,13 @@ Previously, throwing a `NonRetryableError` with a custom message would result in
 import { WorkflowEntrypoint, NonRetryableError } from "cloudflare:workers";
 
 export class MyWorkflow extends WorkflowEntrypoint {
-	async run(event, step) {
-		await step.do("my-step", async () => {
-			throw new NonRetryableError("custom error message");
-			// Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
-			// With this flag: error.message === "custom error message"
-		});
-	}
+  async run(event, step) {
+    await step.do("my-step", async () => {
+      throw new NonRetryableError("custom error message");
+      // Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
+      // With this flag: error.message === "custom error message"
+    });
+  }
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
index 39b0c719c6a6edd..17806e9fea110e3 100644
--- a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
+++ b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
@@ -34,10 +34,10 @@ Define protected routes in `wrangler.jsonc`:
 			{
 				"pattern": "/premium/*",
 				"amount": "0.01",
-				"description": "Access to premium content for 1 hour",
-			},
-		],
-	},
+				"description": "Access to premium content for 1 hour"
+			}
+		]
+	}
 }
 ```
 
@@ -55,7 +55,7 @@ With [Bot Management](/bots/), the proxy can charge crawlers while keeping the s
 	"amount": "0.25",
 	"description": "Content access for 1 hour",
 	"bot_score_threshold": 30,
-	"except_detection_ids": [120623194, 117479730],
+	"except_detection_ids": [120623194, 117479730]
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/x402/index.mdx b/src/content/docs/agents/agentic-payments/x402/index.mdx
index bc12467db9b9995..4ae0cb18581f35d 100644
--- a/src/content/docs/agents/agentic-payments/x402/index.mdx
+++ b/src/content/docs/agents/agentic-payments/x402/index.mdx
@@ -45,8 +45,8 @@ The facilitator does not hold funds. It verifies and broadcasts the client's pre
 
 x402 uses payment **schemes** to define how a payment is constructed and settled on a given network.
 
-| Scheme                                                                                           | Networks                                 | Description                                                                                                                       |
-| ------------------------------------------------------------------------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Scheme                                                                                    | Networks                                 | Description                                                                                                                       |
+| ----------------------------------------------------------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | [`exact`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact.md) | EVM, Solana, Aptos, Stellar, Hedera, Sui | Transfers a fixed token amount — typically [ERC-20](https://eips.ethereum.org/EIPS/eip-20) USDC on EVM — to the merchant address. |
 | [`upto`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/upto/scheme_upto.md)    | EVM                                      | Authorizes a maximum amount; the actual charge is determined at settlement time based on resource consumption.                    |
 
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
index a766be9a51e7892..25135f65b7f3f89 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
@@ -38,4 +38,4 @@ You may have both of the following enabled:
 - A selection of AI crawlers to be charged through AI Crawl Control's pay per crawl
 - Bot configuration option to [Block AI Bots](/bots/get-started/bot-fight-mode/#block-ai-bots).
 
-Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
+Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
\ No newline at end of file
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
index 57d1c103c3178a0..8e8f5e9661c32ef 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
@@ -9,14 +9,7 @@ products:
   - ai-crawl-control
 ---
 
-import {
-	GlossaryTooltip,
-	Example,
-	Steps,
-	Tabs,
-	TabItem,
-	DashButton,
-} from "~/components";
+import { GlossaryTooltip, Example, Steps, Tabs, TabItem, DashButton } from "~/components";
 
 AI Crawl Control works alongside other Cloudflare products, such as Cloudflare [Web Application Firewall (WAF)](/waf/). WAF checks incoming web and API requests, and filters undesired traffic based on rules. [WAF custom rules](/waf/custom-rules/) allow you to perform certain actions such as enforcing <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip>.
 
@@ -139,3 +132,4 @@ Any additions you make are preserved when you subsequently update crawler action
 :::caution
 Changes made directly to the WAF rule are not reflected back in the AI Crawl Control dashboard. Use the **Crawlers** tab as your primary interface, and reserve direct WAF edits for cases where the dashboard does not cover your requirements.
 :::
+
diff --git a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
index 8ed8a785d4df4d8..62af2e2d1d983dc 100644
--- a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
+++ b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
@@ -65,12 +65,12 @@ Visualize crawler activity patterns over the selected time period. Use the view
 
 You can group the data by different dimensions:
 
-| Dimension    | Description                                                                             |
-| ------------ | --------------------------------------------------------------------------------------- |
-| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).     |
-| **Category** | Analyze crawlers by their purpose or type.                                              |
-| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site. |
-| **Host**     | Break down activity across multiple subdomains.                                         |
+| Dimension    | Description                                                                              |
+| ------------ | ---------------------------------------------------------------------------------------- |
+| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).      |
+| **Category** | Analyze crawlers by their purpose or type.                                               |
+| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site.  |
+| **Host**     | Break down activity across multiple subdomains.                                          |
 
 :::note
 The Data transfer view shows `edgeResponseBytes`. Some crawlers may show higher data transfer per request than others, depending on the content they request.
@@ -93,11 +93,11 @@ The **Content Format** chart shows what content types AI systems request versus
 
 The chart includes three views:
 
-| View              | Description                                                                       |
-| ----------------- | --------------------------------------------------------------------------------- |
-| **Comparison**    | A grouped bar chart comparing requested content types versus served content types |
-| **Request Type**  | Breakdown of requests by Accept header                                            |
-| **Response Type** | Breakdown of responses by Content-Type header                                     |
+| View          | Description                                                                 |
+| ------------- | --------------------------------------------------------------------------- |
+| **Comparison** | A grouped bar chart comparing requested content types versus served content types |
+| **Request Type** | Breakdown of requests by Accept header                                      |
+| **Response Type** | Breakdown of responses by Content-Type header                              |
 
 ### Top referrers
 
diff --git a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
index 2892e1f8c9c5aa7..37400acba85f698 100644
--- a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
+++ b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
@@ -8,15 +8,7 @@ products:
   - ai-crawl-control
 ---
 
-import {
-	Steps,
-	GlossaryTooltip,
-	Tabs,
-	TabItem,
-	Example,
-	Plan,
-	DashButton,
-} from "~/components";
+import { Steps, GlossaryTooltip, Tabs, TabItem, Example, Plan, DashButton } from "~/components";
 
 AI Crawl Control enables you to take specific action for each AI crawler.
 
@@ -33,13 +25,13 @@ To manage AI crawlers:
 
 The **Crawlers** tab displays a table of AI crawlers that are requesting access to your content, and how they interact with your pages. The table provides the following information.
 
-| Column                | Details                                                                                                                                                                                 |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                               |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                       |
-| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control. |
-| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                            |
-| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).             |
+| Column                | Details                                                                                                                                                                                    |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                                  |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                          |
+| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control.    |
+| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                               |
+| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).                |
 
 :::note[Quality of AI crawler detection]
 On the free plan, AI Crawl Control identifies AI crawlers based on their [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent). This enables AI Crawl Control to detect well-known, self-identifying AI crawlers.
diff --git a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
index 175f3072a93187a..8fbf42ce0120ba3 100644
--- a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
+++ b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
@@ -29,4 +29,4 @@ Pay per crawl is currently in closed beta.
 To find out how to join the beta program, reach out to us at [Pay per crawl signup](http://www.cloudflare.com/paypercrawl-signup/), or contact your account executive if you are an existing Enterprise customer.
 
 To learn more about pay per crawl, refer to Cloudflare blog: [Introducing pay per crawl: enabling content owners to charge AI crawlers for access](https://blog.cloudflare.com/introducing-pay-per-crawl/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
index 6673c210889beae..f406e702ce30ed6 100644
--- a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
+++ b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
@@ -42,12 +42,12 @@ The values in all tables and metrics will update according to your filters.
 
 The **Robots.txt availability** table shows the historical request frequency and health status of `robots.txt` files across your hostnames over the selected time frame.
 
-| Column          | Description                                                                                                                                                                                                                       |
-| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                 |
+| Column          | Description                                                                                                                                                                                                                    |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                      |
 | Requests        | The total number of requests made to this path. Requests are broken down into:<br/>- **Successful:** HTTP status codes below 400 (including **200 OK** and redirects).<br/>- **Unsuccessful:** HTTP status codes of 400 or above. |
-| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                          |
-| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                             |
+| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                       |
+| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                          |
 
 From this table, you can take the following actions:
 
diff --git a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
index d285d0714cd426d..1122f0a6d7d639e 100644
--- a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
+++ b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
@@ -156,12 +156,12 @@ The feature parses the `<link rel="canonical">` tag from the `<head>` section of
 ```html
 <!DOCTYPE html>
 <html>
-	<head>
-		<link rel="canonical" href="https://example.com/current-version" />
-	</head>
-	<body>
-		<!-- Page content -->
-	</body>
+<head>
+  <link rel="canonical" href="https://example.com/current-version">
+</head>
+<body>
+  <!-- Page content -->
+</body>
 </html>
 ```
 
@@ -169,10 +169,10 @@ Both absolute and relative URLs are supported:
 
 ```html
 <!-- Absolute URL -->
-<link rel="canonical" href="https://example.com/page" />
+<link rel="canonical" href="https://example.com/page">
 
 <!-- Relative URL (resolved against request URL) -->
-<link rel="canonical" href="/current-page" />
+<link rel="canonical" href="/current-page">
 ```
 
 ### Interaction with other redirect features
diff --git a/src/content/docs/ai-gateway/configuration/authentication.mdx b/src/content/docs/ai-gateway/configuration/authentication.mdx
index e848745b780263d..780ade1a3e222cc 100644
--- a/src/content/docs/ai-gateway/configuration/authentication.mdx
+++ b/src/content/docs/ai-gateway/configuration/authentication.mdx
@@ -66,7 +66,7 @@ const openai = createOpenAI({
 
 :::note
 When an AI Gateway is accessed from a Cloudflare Worker using a **binding**, the `cf-aig-authorization` header does not need to be manually included.  
-Requests made through bindings are **pre-authenticated** within the associated Cloudflare account.
+Requests made through bindings are **pre-authenticated** within the associated Cloudflare account. 
 :::
 
 The following table outlines gateway behavior based on the authentication settings and header status:
diff --git a/src/content/docs/ai-gateway/configuration/custom-providers.mdx b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
index 0bc6f1543a3b8fe..6da29fa5366081a 100644
--- a/src/content/docs/ai-gateway/configuration/custom-providers.mdx
+++ b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
@@ -373,12 +373,12 @@ Everything after `custom-{slug}/` in your request URL is appended directly to th
 
 ### Choosing between Unified API and provider-specific endpoint
 
-|                                 | Unified API (`/compat`)                           | Provider-specific endpoint                |
-| ------------------------------- | ------------------------------------------------- | ----------------------------------------- |
-| **Best for**                    | Providers with OpenAI-compatible APIs             | Providers with any API structure          |
-| **Request format**              | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
-| **Path control**                | Fixed to `/compat/chat/completions`               | Full control over the upstream path       |
-| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}`       | URL path: `/custom-{slug}/{path}`         |
+| | Unified API (`/compat`) | Provider-specific endpoint |
+|---|---|---|
+| **Best for** | Providers with OpenAI-compatible APIs | Providers with any API structure |
+| **Request format** | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
+| **Path control** | Fixed to `/compat/chat/completions` | Full control over the upstream path |
+| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}` | URL path: `/custom-{slug}/{path}` |
 
 Use the **Unified API** when your custom provider accepts the OpenAI-compatible `/chat/completions` request format. This is the simplest option and works well with OpenAI SDKs.
 
@@ -425,12 +425,10 @@ The following examples show how to configure `base_url` and construct request UR
 Many providers follow the OpenAI convention of hosting their API at `{domain}/v1/chat/completions`.
 
 **Configuration:**
-
 - `slug`: `my-openai-compat`
 - `base_url`: `https://api.example-provider.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-openai-compat/v1/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -450,7 +448,6 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-op
 | Upstream URL | `https://api.example-provider.com/v1/chat/completions` |
 
 Since this provider is OpenAI-compatible, you could also use the Unified API:
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -466,12 +463,10 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/
 Some providers use API paths that don't follow the `/v1/` convention. For example, a provider whose chat endpoint is at `https://api.custom-ai.com/api/coding/paas/v4/chat/completions`.
 
 **Configuration:**
-
 - `slug`: `custom-ai`
 - `base_url`: `https://api.custom-ai.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-custom-ai/api/coding/paas/v4/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -499,12 +494,10 @@ For providers with non-standard paths, you must use the provider-specific endpoi
 If you host your own model behind a reverse proxy or on a platform that adds a path prefix, include only the fixed prefix portion in `base_url` if all your endpoints share it. Otherwise, keep `base_url` as just the domain.
 
 **Configuration (domain-only `base_url`):**
-
 - `slug`: `internal-llm`
 - `base_url`: `https://ml.internal.example.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-internal-llm/serving/models/my-model:predict \
   -H "Authorization: Bearer $INTERNAL_API_KEY" \
@@ -527,12 +520,10 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-inter
 When using the OpenAI SDK to connect to a custom provider through AI Gateway, set the SDK's `base_url` to the gateway's provider-specific endpoint path (up to and including the API version prefix that your provider expects).
 
 **Configuration:**
-
 - `slug`: `alt-provider`
 - `base_url`: `https://api.alt-provider.com`
 
 **Python (OpenAI SDK):**
-
 ```python title="Using OpenAI SDK with a custom provider"
 from openai import OpenAI
 
@@ -568,14 +559,14 @@ response = client.chat.completions.create(
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1003,
-			"message": "A custom provider with this slug already exists",
-			"path": ["body", "slug"]
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1003,
+      "message": "A custom provider with this slug already exists",
+      "path": ["body", "slug"]
+    }
+  ]
 }
 ```
 
@@ -585,13 +576,13 @@ Each custom provider slug must be unique within your account. Choose a different
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1004,
-			"message": "Custom Provider not found"
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1004,
+      "message": "Custom Provider not found"
+    }
+  ]
 }
 ```
 
@@ -601,14 +592,14 @@ The specified provider ID does not exist or you don't have access to it. Verify
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1002,
-			"message": "base_url must be a valid HTTPS URL starting with https://",
-			"path": ["body", "base_url"]
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1002,
+      "message": "base_url must be a valid HTTPS URL starting with https://",
+      "path": ["body", "base_url"]
+    }
+  ]
 }
 ```
 
@@ -645,4 +636,4 @@ If you receive a 404 from the upstream provider, the most common cause is an inc
 - [BYOK (Store Keys)](/ai-gateway/configuration/bring-your-own-keys/)
 - [Dynamic routing](/ai-gateway/features/dynamic-routing/)
 - [Caching](/ai-gateway/features/caching/)
-- [Rate limiting](/ai-gateway/features/rate-limiting/)
+- [Rate limiting](/ai-gateway/features/rate-limiting/)
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
index 591a2b78db5305d..1583cae3d3cb063 100644
--- a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
+++ b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
@@ -8,7 +8,6 @@ sidebar:
 products:
   - ai-gateway
 ---
-
 import { DashButton } from "~/components";
 
 Human feedback is a valuable metric to assess the performance of your AI models. By incorporating human feedback, you can gain deeper insights into how the model's responses are perceived and how well it performs from a user-centric perspective. This feedback can then be used in evaluations to calculate performance metrics, driving optimization and ultimately enhancing the reliability, accuracy, and efficiency of your AI application.
diff --git a/src/content/docs/ai-gateway/features/dlp/index.mdx b/src/content/docs/ai-gateway/features/dlp/index.mdx
index 1a2da0f59706eda..fed23035a215241 100644
--- a/src/content/docs/ai-gateway/features/dlp/index.mdx
+++ b/src/content/docs/ai-gateway/features/dlp/index.mdx
@@ -59,11 +59,11 @@ Because of this buffering:
 
 DLP scanning runs after a cache miss, when AI Gateway forwards the request to the provider and receives a response. The following table describes how each DLP outcome affects caching:
 
-| DLP outcome        | Response cached | Behavior                                                                                                                                                                  |
-| ------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pass (no findings) | Yes             | The response is cached normally according to your gateway cache settings.                                                                                                 |
-| Flag               | Yes             | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
-| Block              | No              | The provider response is discarded and replaced with a DLP error response (status `400`).                                                                                 |
+| DLP outcome | Response cached | Behavior |
+| --- | --- | --- |
+| Pass (no findings) | Yes | The response is cached normally according to your gateway cache settings. |
+| Flag | Yes | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
+| Block | No | The provider response is discarded and replaced with a DLP error response (status `400`). |
 
 **Cache hits skip DLP scanning.** When a subsequent identical request matches a cached response, AI Gateway serves it directly from cache without re-running DLP. This is safe because only responses that already passed DLP (or were flagged, not blocked) are cached. However, if you update your DLP policies after a response has been cached, the cached response is not re-evaluated. It continues to be served until the cache TTL expires.
 
diff --git a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
index fc4d9ee983694c4..72c2fa37068d4d0 100644
--- a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
+++ b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
@@ -92,7 +92,8 @@ export default {
 
 ## Response Metadata
 
-The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers
+The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers 
 
 - `cf-aig-model` - The model used
 - `cf-aig-provider` - The slug of provider used
+
diff --git a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
index 04c450d92911bd4..d03c6eb9622ec7d 100644
--- a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
+++ b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
@@ -124,7 +124,7 @@ You will be prompted to log in after you run `wrangler dev`. When you run `npx w
 
 ```json
 {
-	"response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
+  "response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
 }
 ```
 
diff --git a/src/content/docs/ai-gateway/mcp-server.mdx b/src/content/docs/ai-gateway/mcp-server.mdx
index 5d7ff3bfddb2e49..9cb472e8825884a 100644
--- a/src/content/docs/ai-gateway/mcp-server.mdx
+++ b/src/content/docs/ai-gateway/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - ai-gateway
----
+---
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/observability/logging/index.mdx b/src/content/docs/ai-gateway/observability/logging/index.mdx
index 1ee3a267485ed02..cfcd1cab3d1200c 100644
--- a/src/content/docs/ai-gateway/observability/logging/index.mdx
+++ b/src/content/docs/ai-gateway/observability/logging/index.mdx
@@ -55,9 +55,9 @@ The `cf-aig-collect-log-payload` header allows you to control whether the raw re
 
 This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completion data.
 
-| Header value | Behavior                                                               |
-| ------------ | ---------------------------------------------------------------------- |
-| `true`       | Request and response payloads are stored.                              |
+| Header value | Behavior |
+| ------------ | -------- |
+| `true`       | Request and response payloads are stored. |
 | `false`      | Payload storage is skipped. Metadata-only log entries are still saved. |
 
 In the example below, we use `cf-aig-collect-log-payload` to skip storing the request and response bodies while keeping the metadata log.
diff --git a/src/content/docs/ai-gateway/reference/audit-logs.mdx b/src/content/docs/ai-gateway/reference/audit-logs.mdx
index 250b377c6c517ee..0cfe7251d9d7c8a 100644
--- a/src/content/docs/ai-gateway/reference/audit-logs.mdx
+++ b/src/content/docs/ai-gateway/reference/audit-logs.mdx
@@ -5,7 +5,6 @@ pcx_content_type: concept
 products:
   - ai-gateway
 ---
-
 import { DashButton } from "~/components";
 
 [Audit logs](/fundamentals/account/account-security/review-audit-logs/) provide a comprehensive summary of changes made within your Cloudflare account, including those made to gateways in AI Gateway. This functionality is available on all plan types, free of charge, and is enabled by default.
@@ -14,7 +13,7 @@ import { DashButton } from "~/components";
 
 To view audit logs for AI Gateway, in the Cloudflare dashboard, go to the **Audit logs** page.
 
-<DashButton url="/?to=/:account/audit-log" />
+  <DashButton url="/?to=/:account/audit-log" />
 
 For more information on how to access and use audit logs, refer to [review audit logs documentation](/fundamentals/account/account-security/review-audit-logs/).
 
@@ -34,39 +33,39 @@ Below is an example of an audit log entry showing the creation of a new gateway:
 
 ```json
 {
-	"action": {
-		"info": "gateway created",
-		"result": true,
-		"type": "create"
-	},
-	"actor": {
-		"email": "<ACTOR_EMAIL>",
-		"id": "3f7b730e625b975bc1231234cfbec091",
-		"ip": "fe32:43ed:12b5:526::1d2:13",
-		"type": "user"
-	},
-	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-	"interface": "UI",
-	"metadata": {},
-	"newValue": "",
-	"newValueJson": {
-		"cache_invalidate_on_update": false,
-		"cache_ttl": 0,
-		"collect_logs": true,
-		"id": "test",
-		"rate_limiting_interval": 0,
-		"rate_limiting_limit": 0,
-		"rate_limiting_technique": "fixed"
-	},
-	"oldValue": "",
-	"oldValueJson": {},
-	"owner": {
-		"id": "1234d848c0b9e484dfc37ec392b5fa8a"
-	},
-	"resource": {
-		"id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
-		"type": "ai_gateway.gateway"
-	},
-	"when": "2024-07-17T14:06:11.425Z"
+ "action": {
+     "info": "gateway created",
+     "result": true,
+     "type": "create"
+ },
+ "actor": {
+     "email": "<ACTOR_EMAIL>",
+     "id": "3f7b730e625b975bc1231234cfbec091",
+     "ip": "fe32:43ed:12b5:526::1d2:13",
+     "type": "user"
+ },
+ "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+ "interface": "UI",
+ "metadata": {},
+ "newValue": "",
+ "newValueJson": {
+     "cache_invalidate_on_update": false,
+     "cache_ttl": 0,
+     "collect_logs": true,
+     "id": "test",
+     "rate_limiting_interval": 0,
+     "rate_limiting_limit": 0,
+     "rate_limiting_technique": "fixed"
+ },
+ "oldValue": "",
+ "oldValueJson": {},
+ "owner": {
+     "id": "1234d848c0b9e484dfc37ec392b5fa8a"
+ },
+ "resource": {
+     "id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
+     "type": "ai_gateway.gateway"
+ },
+ "when": "2024-07-17T14:06:11.425Z"
 }
 ```
diff --git a/src/content/docs/ai-gateway/reference/limits.mdx b/src/content/docs/ai-gateway/reference/limits.mdx
index 8b130857ad0477c..5c0459bc75ae5e7 100644
--- a/src/content/docs/ai-gateway/reference/limits.mdx
+++ b/src/content/docs/ai-gateway/reference/limits.mdx
@@ -33,14 +33,11 @@ The following limits apply to gateway configurations, logs, and related features
 <sup>1</sup> When you reach the log storage limit for a gateway, you can
 configure your gateway to either automatically delete the oldest logs to make
 room for new ones, or stop saving new logs. You can also use
-[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to external
-storage. Refer to [Automatic log
-deletion](/ai-gateway/observability/logging/#automatic-log-deletion) for more
-details.
-
-<sup>2</sup> On the free plan, the log storage limit applies to total logs
-across all gateways in your account. Same auto-delete or stop-saving behavior as
-<sup>1</sup>.
+[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to
+external storage. Refer to [Automatic log deletion](/ai-gateway/observability/logging/#automatic-log-deletion)
+for more details.
+
+<sup>2</sup> On the free plan, the log storage limit applies to total logs across all gateways in your account. Same auto-delete or stop-saving behavior as <sup>1</sup>.
 
 <sup>3</sup> Logs larger than 10 MB will not be stored.
 
diff --git a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
index d55b0392378c965..9f0277bdd3a1ac7 100644
--- a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
+++ b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
@@ -106,12 +106,12 @@ The response includes a prediction `id`:
 
 ```json
 {
-	"id": "xyz789...",
-	"status": "starting",
-	"urls": {
-		"get": "https://api.replicate.com/v1/predictions/xyz789...",
-		"cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
-	}
+  "id": "xyz789...",
+  "status": "starting",
+  "urls": {
+    "get": "https://api.replicate.com/v1/predictions/xyz789...",
+    "cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
+  }
 }
 ```
 
@@ -127,7 +127,7 @@ Keep polling until `status` is `succeeded` (or `failed`). When complete, the `ou
 
 ## Next steps
 
-From here you can:
+From here you can: 
 
 - Use [logging](/ai-gateway/observability/logging/) to monitor requests and debug issues.
 - Set up [rate limiting](/ai-gateway/features/rate-limiting/) to control usage.
diff --git a/src/content/docs/ai-gateway/usage/chat-completion.mdx b/src/content/docs/ai-gateway/usage/chat-completion.mdx
index c1dbd0f663fb740..1280237dc0187bb 100644
--- a/src/content/docs/ai-gateway/usage/chat-completion.mdx
+++ b/src/content/docs/ai-gateway/usage/chat-completion.mdx
@@ -11,7 +11,11 @@ products:
   - ai-gateway
 ---
 
-import { Details, Tabs, TabItem } from "~/components";
+import {
+	Details,
+  Tabs,
+  TabItem
+} from "~/components";
 import CodeSnippets from "~/components/ai-gateway/code-examples.astro";
 
 :::caution[Deprecated]
diff --git a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
index aa1ad566a1a3a37..7c7d8622dd1be29 100644
--- a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
@@ -11,7 +11,6 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 [Anthropic](https://www.anthropic.com/) helps build reliable, interpretable, and steerable AI systems.
 
 ## Endpoint
-
 **Base URL**
 
 ```txt
@@ -125,18 +124,17 @@ import Anthropic from "@anthropic-ai/sdk";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic`;
 
 const anthropic = new Anthropic({
-baseURL,
-defaultHeaders: {
-Authorization: `Bearer {cf_api_token}`,
-},
+	baseURL,
+	defaultHeaders: {
+		Authorization: `Bearer {cf_api_token}`,
+	},
 });
 
 const message = await anthropic.messages.create({
-model: "claude-sonnet-4-5",
-messages: [{ role: "user", content: "What is Cloudflare?" }],
-max_tokens: 1024,
+	model: "claude-sonnet-4-5",
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
+	max_tokens: 1024,
 });
-
 ```
 </Details>
 
@@ -153,4 +151,3 @@ max_tokens: 1024,
     }}
 
 />
-```
diff --git a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
index 33bc4a3a7827002..bbda8d88dad78df 100644
--- a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
@@ -52,14 +52,14 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{
 import { AzureOpenAI } from "openai";
 
 const azure_openai = new AzureOpenAI({
-	apiKey: "{azure_api_key}",
-	baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
-	apiVersion: "2023-05-15",
-	defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
+  apiKey: "{azure_api_key}",
+  baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
+  apiVersion: "2023-05-15",
+  defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
 });
 
 const result = await azure_openai.chat.completions.create({
-	model: "{deployment_name}",
-	messages: [{ role: "user", content: "Hello" }],
+  model: '{deployment_name}',
+  messages: [{ role: "user", content: "Hello" }],
 });
 ```
diff --git a/src/content/docs/ai-gateway/usage/providers/baseten.mdx b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
index 54c26a43777ba18..24877ce82f34716 100644
--- a/src/content/docs/ai-gateway/usage/providers/baseten.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
@@ -57,31 +57,31 @@ const gatewayId = "{gateway_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const openai = new OpenAI({
-	apiKey,
-	baseURL,
+  apiKey,
+  baseURL,
 });
 
 const model = "openai/gpt-oss-120b";
 const messages = [{ role: "user", content: "What is Cloudflare?" }];
 
 const chatCompletion = await openai.chat.completions.create({
-	model,
-	messages,
+  model,
+  messages,
 });
 
 console.log(chatCompletion);
 ```
 
 <Render
-	file="chat-completions-providers"
-	product="ai-gateway"
-	params={{
-		name: "Baseten",
-		jsonexample: `
+  file="chat-completions-providers"
+  product="ai-gateway"
+  params={{
+    name: "Baseten",
+    jsonexample: `
 {
   "model": "baseten/{model}"
-}`,
-	}}
+}`
+  }}
 />
 
 ## Model-specific endpoints
@@ -110,15 +110,15 @@ const modelId = "{model_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const response = await fetch(`${baseURL}/model/${modelId}`, {
-	method: "POST",
-	headers: {
-		Authorization: `Bearer ${basetenApiToken}`,
-		"Content-Type": "application/json",
-	},
-	body: JSON.stringify({
-		prompt: "What is Cloudflare?",
-		max_tokens: 100,
-	}),
+  method: "POST",
+  headers: {
+    "Authorization": `Bearer ${basetenApiToken}`,
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify({
+    prompt: "What is Cloudflare?",
+    max_tokens: 100,
+  }),
 });
 
 const result = await response.json();
diff --git a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
index bb8f30200a44e93..1f2df28b2813847 100644
--- a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
@@ -43,10 +43,10 @@ AI Gateway handles this complexity for you. When you store your AWS credentials
 
 ### Authentication methods comparison
 
-| Method                  | `cf-aig-authorization` header | `Authorization` header | Signing                              |
-| ----------------------- | ----------------------------- | ---------------------- | ------------------------------------ |
-| **BYOK (Recommended)**  | `Bearer {CF_AIG_TOKEN}`       | Not needed             | Gateway signs automatically          |
-| **Client-side signing** | `Bearer {CF_AIG_TOKEN}`       | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
+| Method | `cf-aig-authorization` header | `Authorization` header | Signing |
+| --- | --- | --- | --- |
+| **BYOK (Recommended)** | `Bearer {CF_AIG_TOKEN}` | Not needed | Gateway signs automatically |
+| **Client-side signing** | `Bearer {CF_AIG_TOKEN}` | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
 
 :::caution[Do not confuse the headers]
 `cf-aig-authorization` authenticates your request to AI Gateway. When using BYOK, you do not need to include any AWS authorization headers because AI Gateway signs the request for you.
@@ -227,3 +227,5 @@ const response = await client.chat.completions.create({
 
 console.log(response.choices[0].message.content);
 ```
+
+
diff --git a/src/content/docs/ai-gateway/usage/providers/fal.mdx b/src/content/docs/ai-gateway/usage/providers/fal.mdx
index 057d6dda7144ddc..3e67996cbae3c2d 100644
--- a/src/content/docs/ai-gateway/usage/providers/fal.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/fal.mdx
@@ -78,23 +78,21 @@ The `x-fal-target-url` format is compliant with the Fal SDKs, so AI Gateway can
 import { fal } from "@fal-ai/client";
 
 fal.config({
-	credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
-	proxyUrl:
-		"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal",
+  credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
+  proxyUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal"
 });
 
 const result = await fal.subscribe("fal-ai/bytedance/seedream/v4/edit", {
-	input: {
-		prompt:
-			"Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
-		image_urls: [
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png",
-		],
-	},
+  "input": {
+    "prompt": "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
+    "image_urls": [
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png"
+    ]
+  }
 });
 
 console.log(result.data.images[0]);
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
index 29e542bf31fb4d9..7d986484bd9371b 100644
--- a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
@@ -17,7 +17,6 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 ```txt
 https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio
 ```
-
 Then you can append the endpoint you want to hit, for example: `v1/models/{model}:{generative_ai_rest_resource}`
 
 So your final URL will come together as: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio/v1/models/{model}:{generative_ai_rest_resource}`.
@@ -137,19 +136,18 @@ console.log(response.text);
 import { GoogleGenAI } from "@google/genai";
 
 const ai = new GoogleGenAI({
-apiKey: "{cf_aig_token}",
-httpOptions: {
-baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
-}
+  apiKey: "{cf_aig_token}",
+  httpOptions: {
+	  baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
+  }
 });
 
 const response = await ai.models.generateContent({
-model: "gemini-2.5-flash",
-contents: "What is Cloudflare?",
+  model: "gemini-2.5-flash",
+  contents: "What is Cloudflare?",
 });
 
 console.log(response.text);
-
 ```
 </Details>
 
@@ -166,4 +164,3 @@ console.log(response.text);
     }}
 
 />
-```
diff --git a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
index e9213598bdda79c..bc019d9a71628b5 100644
--- a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
@@ -48,17 +48,17 @@ const ideogramApiKey = "{ideogram_api_key}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/ideogram`;
 
 const response = await fetch(`${baseURL}/v1/ideogram-v3/generate`, {
-	method: "POST",
-	headers: {
-		"Api-Key": ideogramApiKey,
-		"Content-Type": "application/json",
-	},
-	body: JSON.stringify({
-		prompt: "A serene landscape with mountains and a lake at sunset",
-		model: "V_3",
-	}),
+  method: "POST",
+  headers: {
+    "Api-Key": ideogramApiKey,
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify({
+    prompt: "A serene landscape with mountains and a lake at sunset",
+    model: "V_3",
+  }),
 });
 
 const result = await response.json();
 console.log(result);
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/usage/rest-api.mdx b/src/content/docs/ai-gateway/usage/rest-api.mdx
index e2275bfa7e32b91..7dd750f9b04aca9 100644
--- a/src/content/docs/ai-gateway/usage/rest-api.mdx
+++ b/src/content/docs/ai-gateway/usage/rest-api.mdx
@@ -18,12 +18,12 @@ No provider SDKs or API keys are needed. Authentication and billing are handled
 
 Four endpoints are available, each suited to different use cases:
 
-| Endpoint                       | Format                         | Use case                                         |
-| ------------------------------ | ------------------------------ | ------------------------------------------------ |
-| `POST /ai/run`                 | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
-| `POST /ai/v1/chat/completions` | OpenAI chat completions        | LLMs — OpenAI SDK compatible                     |
-| `POST /ai/v1/responses`        | OpenAI Responses API           | Agentic workflows — OpenAI SDK compatible        |
-| `POST /ai/v1/messages`         | Anthropic Messages API         | LLMs — Anthropic SDK compatible                  |
+| Endpoint | Format | Use case |
+| -------- | ------ | -------- |
+| `POST /ai/run` | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
+| `POST /ai/v1/chat/completions` | OpenAI chat completions | LLMs — OpenAI SDK compatible |
+| `POST /ai/v1/responses` | OpenAI Responses API | Agentic workflows — OpenAI SDK compatible |
+| `POST /ai/v1/messages` | Anthropic Messages API | LLMs — Anthropic SDK compatible |
 
 ## Authentication
 
@@ -140,13 +140,13 @@ Point the OpenAI SDK `baseURL` at the Cloudflare API:
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.chat.completions.create({
-	model: "openai/gpt-4.1",
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
+  model: "openai/gpt-4.1",
+  messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -158,13 +158,13 @@ Uses the OpenAI Responses API format for agentic workflows. Compatible with the
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.responses.create({
-	model: "openai/gpt-4.1",
-	input: "What is Cloudflare?",
+  model: "openai/gpt-4.1",
+  input: "What is Cloudflare?",
 });
 ```
 
@@ -194,14 +194,14 @@ Point the Anthropic SDK `baseURL` at the Cloudflare API:
 import Anthropic from "@anthropic-ai/sdk";
 
 const anthropic = new Anthropic({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const message = await anthropic.messages.create({
-	model: "anthropic/claude-sonnet-4-5",
-	max_tokens: 512,
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
+  model: "anthropic/claude-sonnet-4-5",
+  max_tokens: 512,
+  messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -229,11 +229,11 @@ With the OpenAI SDK, set the header via `defaultHeaders`:
 
 ```javascript
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
-	defaultHeaders: {
-		"cf-aig-gateway-id": "my-gateway",
-	},
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  defaultHeaders: {
+    "cf-aig-gateway-id": "my-gateway",
+  },
 });
 ```
 
@@ -243,17 +243,17 @@ All AI Gateway features configured on that gateway — caching, rate limiting, g
 
 Use `cf-aig-*` headers to control AI Gateway behavior on a per-request basis:
 
-| Header                   | Type        | Description                                             |
-| ------------------------ | ----------- | ------------------------------------------------------- |
-| `cf-aig-skip-cache`      | boolean     | Skip the cache for this request.                        |
-| `cf-aig-cache-ttl`       | number      | Cache TTL in seconds.                                   |
-| `cf-aig-cache-key`       | string      | Custom cache key.                                       |
-| `cf-aig-collect-log`     | boolean     | Turn logging on or off for this request.                |
-| `cf-aig-request-timeout` | number      | Request timeout in milliseconds.                        |
-| `cf-aig-max-attempts`    | number      | Retry attempts (max 5).                                 |
-| `cf-aig-retry-delay`     | number      | Retry delay in milliseconds (max 5000).                 |
-| `cf-aig-backoff`         | string      | Backoff method: `constant`, `linear`, or `exponential`. |
-| `cf-aig-metadata`        | JSON string | Custom metadata to attach to the log entry.             |
+| Header | Type | Description |
+| ------ | ---- | ----------- |
+| `cf-aig-skip-cache` | boolean | Skip the cache for this request. |
+| `cf-aig-cache-ttl` | number | Cache TTL in seconds. |
+| `cf-aig-cache-key` | string | Custom cache key. |
+| `cf-aig-collect-log` | boolean | Turn logging on or off for this request. |
+| `cf-aig-request-timeout` | number | Request timeout in milliseconds. |
+| `cf-aig-max-attempts` | number | Retry attempts (max 5). |
+| `cf-aig-retry-delay` | number | Retry delay in milliseconds (max 5000). |
+| `cf-aig-backoff` | string | Backoff method: `constant`, `linear`, or `exponential`. |
+| `cf-aig-metadata` | JSON string | Custom metadata to attach to the log entry. |
 
 For more details on these options, refer to [Request handling](/ai-gateway/configuration/request-handling/) and [Caching](/ai-gateway/features/caching/).
 
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
index dd9b384084acdcf..bfc911e09f973c8 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
@@ -55,7 +55,7 @@ ws.on("open", () => {
 			},
 		}),
 	);
-});
+})
 
 ws.on("message", (message) => {
 	console.log(message.toString());
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
index f444cff4c7a73ef..57c34339587a994 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
@@ -272,7 +272,7 @@ let isPlayingAudio = false;
 const rl = readline.createInterface({
 	input: process.stdin,
 	output: process.stdout,
-	prompt: 'Enter text to speak (or "quit" to exit): ',
+	prompt: "Enter text to speak (or \"quit\" to exit): ",
 });
 
 ws.onopen = () => {
diff --git a/src/content/docs/ai-search/api/instances/rest-api.mdx b/src/content/docs/ai-search/api/instances/rest-api.mdx
index 37757fbb0ff5362..178f1c9d6c69011 100644
--- a/src/content/docs/ai-search/api/instances/rest-api.mdx
+++ b/src/content/docs/ai-search/api/instances/rest-api.mdx
@@ -20,8 +20,8 @@ Use the AI Search REST API to manage instances and sync jobs over HTTP.
 
 AI Search APIs are available at two base paths:
 
-| Path                                                                     | Description                                                                 |
-| ------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
+| Path                                                                 | Description                                                                 |
+| -------------------------------------------------------------------- | --------------------------------------------------------------------------- |
 | `/accounts/{account_id}/ai-search/instances/{id}`                        | Operates on a specific instance                                             |
 | `/accounts/{account_id}/ai-search/namespaces/{namespace}/instances/{id}` | Operates on instances within a [namespace](/ai-search/concepts/namespaces/) |
 
diff --git a/src/content/docs/ai-search/api/items/rest-api.mdx b/src/content/docs/ai-search/api/items/rest-api.mdx
index 08634485801ed10..f23b4dd83703914 100644
--- a/src/content/docs/ai-search/api/items/rest-api.mdx
+++ b/src/content/docs/ai-search/api/items/rest-api.mdx
@@ -35,8 +35,8 @@ The available operations are the same for both paths. For the namespace-scoped A
 
 Upload, list, get, delete, and download items within an instance. For the full specification, refer to the [Items API reference](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/).
 
-| Operation                                                                                                                | Method   | Description                    |
-| ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------ |
+| Operation                                                                                                            | Method   | Description                    |
+| -------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------ |
 | [Upload](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/upload/)     | `POST`   | Upload a document for indexing |
 | [List](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/list/)         | `GET`    | List all items in an instance  |
 | [Get](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/get/)           | `GET`    | Get item info by ID            |
diff --git a/src/content/docs/ai-search/configuration/models/index.mdx b/src/content/docs/ai-search/configuration/models/index.mdx
index 42a76abb29e721b..c406d789f32edfa 100644
--- a/src/content/docs/ai-search/configuration/models/index.mdx
+++ b/src/content/docs/ai-search/configuration/models/index.mdx
@@ -28,10 +28,12 @@ To use AI Search with other model providers:
 
 1. Add provider keys to [AI Gateway](/ai-gateway/configuration/bring-your-own-keys/).
 2. Connect the gateway to AI Search.
+
    - When creating a new AI Search, select the AI Gateway with your provider keys.
    - For an existing AI Search, go to **Settings** and switch to a gateway that has your keys under **Resources**.
 
 3. Select models
+
    - Embedding model: Only available to be changed when creating a new AI Search.
    - Generation model: Can be selected when creating a new AI Search and can be changed at any time in **Settings**.
 
diff --git a/src/content/docs/ai-search/how-to/nlweb.mdx b/src/content/docs/ai-search/how-to/nlweb.mdx
index eb36852ae5534f6..25d61bcba3c3cb7 100644
--- a/src/content/docs/ai-search/how-to/nlweb.mdx
+++ b/src/content/docs/ai-search/how-to/nlweb.mdx
@@ -67,23 +67,23 @@ You can use the embeddable snippet to add a search UI directly into your website
 
 ```html
 <!-- Add css on head -->
-<link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css" />
-<link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css" />
-
-<!-- Add container on body -->
-<div id="docs-search-container"></div>
-
-<!-- Include JavaScript -->
-<script type="module">
-	import { NLWebDropdownChat } from "https://ask.example.com/nlweb-dropdown-chat.js";
-
-	const chat = new NLWebDropdownChat({
-		containerId: "docs-search-container",
-		site: "https://ask.example.com",
-		placeholder: "Search for docs...",
-		endpoint: "https://ask.example.com",
-	});
-</script>
+    <link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css">
+    <link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css">
+
+    <!-- Add container on body -->
+    <div id="docs-search-container"></div>
+
+    <!-- Include JavaScript -->
+    <script type="module">
+      import { NLWebDropdownChat } from 'https://ask.example.com/nlweb-dropdown-chat.js';
+
+      const chat = new NLWebDropdownChat({
+        containerId: 'docs-search-container',
+        site: 'https://ask.example.com',
+        placeholder: 'Search for docs...',
+        endpoint: 'https://ask.example.com'
+      });
+    </script>
 ```
 
 This lets you serve conversational AI search directly from your own domain, with control over how people and agents access your content.
diff --git a/src/content/docs/ai-search/wrangler-commands.mdx b/src/content/docs/ai-search/wrangler-commands.mdx
index 916b781370d0e81..f8e1fa53538eca8 100644
--- a/src/content/docs/ai-search/wrangler-commands.mdx
+++ b/src/content/docs/ai-search/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { WranglerNamespace, WranglerCommand } from "~/components";
 
-<WranglerNamespace namespace="ai-search" />
+<WranglerNamespace namespace="ai-search" />
\ No newline at end of file
diff --git a/src/content/docs/ai/related-products/ai-gateway.mdx b/src/content/docs/ai/related-products/ai-gateway.mdx
index 75063087b321b29..c868d2c8ec2fd75 100644
--- a/src/content/docs/ai/related-products/ai-gateway.mdx
+++ b/src/content/docs/ai/related-products/ai-gateway.mdx
@@ -6,5 +6,5 @@ sidebar:
 external_link: /ai-gateway/
 products:
   - ai
-  - ai-gateway
+  - ai-gateway  
 ---
diff --git a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
index c5d95a03c76c5d4..0d4aaf4a63bca3e 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - analytics
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Cloudflare account analytics lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
@@ -18,29 +18,29 @@ Cloudflare account analytics lets you access a wide range of aggregated metrics
 For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
 :::
 
----
+***
 
 ## View your account analytics
 
 To view metrics for your site, in the Cloudflare dashboard, go to the **Account Analytics** page.
 
-<DashButton url="/?to=/:account/analytics" />
+   <DashButton url="/?to=/:account/analytics" />
 
-Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to _Review your account metrics_ below.
+Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to *Review your account metrics* below.
 
----
+***
 
 ## Review your account metrics
 
 This section outlines the aggregated metrics under each category. Before reviewing your metrics, let's define a couple of concepts used in some panels:
 
-- _Rate_ -  Reflects the ratio between the amount for a specific data category and the total.
-- _Bandwidth_ - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
+* *Rate* -  Reflects the ratio between the amount for a specific data category and the total.
+* *Bandwidth* - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
 
 Also, note that:
 
-- To filter metrics for a specific time period, use the dropdown in the top right.
-- Most metrics are grouped into panels representing different aspects of the underlying data.
+* To filter metrics for a specific time period, use the dropdown in the top right.
+* Most metrics are grouped into panels representing different aspects of the underlying data.
 
 ### Summary of metrics
 
@@ -52,21 +52,21 @@ These charts aggregate data for HTTP traffic, and include:
 
 ![Chart showing last week's data for HTTP traffic](~/assets/images/support/hc-dash-account-analytics-map.png)
 
-- Spark lines for _Requests_, _Bandwidth_, _Page views_, and _Visitors_ (_Unique IPs)_
-- An interactive map that breaks down the number of requests by country
-- A table combining numerical and spark line data, sorted by total number of requests per country
+* Spark lines for *Requests*, *Bandwidth*, *Page views*, and *Visitors* (*Unique IPs)*
+* An interactive map that breaks down the number of requests by country
+* A table combining numerical and spark line data, sorted by total number of requests per country
 
 #### Security
 
 ![Panel displaying lines highlighting encryption metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_security_panel.png)
 
-This panel features spark lines highlighting various encryption metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous period.
+This panel features spark lines highlighting various encryption metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous period.
 
 #### Cache
 
 ![Panel displaying lines for caching metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_cache_card.png)
 
-This panel features spark lines for various caching metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected _Last week_ as your time period, the previous period refers to the _week_ before.
+This panel features spark lines for various caching metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected *Last week* as your time period, the previous period refers to the *week* before.
 
 #### Errors
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
index 84e856b537c7e3a..76dccf882a47092 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
@@ -13,7 +13,7 @@ Learn how Cloudflare analytics tracks requests made by [Cloudflare Workers](/wor
 
 With a no-op Worker (a Worker that simply proxies traffic by passing on the original client request to the origin and proxying the response) running on a particular route, the request to the origin is counted as a 'subrequest', separate from initial client to edge request. Thus, unless the Worker responds with a static response and never hits an origin, the eyeball → edge request, and edge → origin request will each be counted separately towards the request or bandwidth count in Analytics. Subrequests are not included in the **Requests** or **Bandwidth** graphs of the Cloudflare **Analytics** app.
 
----
+***
 
 ## Zone analytics
 
@@ -21,20 +21,20 @@ In the dashboard, the numbers in zone analytics reflect visitor traffic. That is
 
 Similarly, the bandwidth is counted based on the bandwidth that is sent to the client, and status codes reflect the status codes that were served back to the client (so if a subrequest received a 500, but you respond with a 200, a 200 will be shown in the status codes breakdown).
 
----
+***
 
 ## Worker analytics
 
 For a breakdown of subrequest traffic (origin facing traffic), you may go to the Cloudflare **Analytics** app and select the **Workers** tab. Under the **Workers** tab, below the Service Workers panel, are a **Subrequests** breakdown by count, **Bandwidth** and **Status Codes**. This will help you spot and debug errors at your origin (such as spikes in 500s), and identify your cache-hit ratio to help you understand traffic going to your origin.
 
----
+***
 
 ## FAQ
 
 **Why do I not have any analytics for Workers?**
 
-- If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
-- If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
+* If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
+* If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
 
 **Will this impact billing?** 
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/index.mdx b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
index 2aeb75e8f6f6dc4..54e99ae3cb5ec74 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/index.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Visit the following pages to learn more about account and zone analytics:
 
diff --git a/src/content/docs/analytics/analytics-engine/grafana.mdx b/src/content/docs/analytics/analytics-engine/grafana.mdx
index 96310e19e31d8cc..e6af88fd7a7a901 100644
--- a/src/content/docs/analytics/analytics-engine/grafana.mdx
+++ b/src/content/docs/analytics/analytics-engine/grafana.mdx
@@ -20,10 +20,10 @@ We recommend the use of the [Altinity plugin for Clickhouse](https://grafana.com
 
 Configure the plugin as follows:
 
-- URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
-- Leave all auth settings off.
-- Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
-- No other options need to be set.
+* URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
+* Leave all auth settings off.
+* Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
+* No other options need to be set.
 
 ## Querying timeseries data
 
@@ -35,8 +35,8 @@ SELECT
     blob1 AS label,
     SUM(_sample_interval * double1) / SUM(_sample_interval) AS average_metric
 FROM dataset_name
-WHERE
-    timestamp <= NOW()
+WHERE 
+    timestamp <= NOW() 
     AND timestamp > NOW() - INTERVAL '1' DAY
 GROUP BY blob1, t
 ORDER BY t
diff --git a/src/content/docs/analytics/analytics-engine/index.mdx b/src/content/docs/analytics/analytics-engine/index.mdx
index ddee07f45c1808c..2eae0d36b0eab7d 100644
--- a/src/content/docs/analytics/analytics-engine/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/index.mdx
@@ -8,17 +8,15 @@ products:
   - workers-analytics-engine
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 Workers Analytics Engine provides unlimited-cardinality analytics at scale, via [a built-in API](/analytics/analytics-engine/get-started/) to write data points from Workers, and a [SQL API](/analytics/analytics-engine/sql-api/) to query that data.
 
 You can use Workers Analytics Engine to:
 
-- Expose custom analytics to your own customers
-- Build usage-based billing systems
-- Understand the health of your service on a per-customer or per-user basis
-- Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
+* Expose custom analytics to your own customers
+* Build usage-based billing systems
+* Understand the health of your service on a per-customer or per-user basis
+* Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
 
-<LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">
-	Get started
-</LinkButton>
+ <LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">Get started</LinkButton>
diff --git a/src/content/docs/analytics/analytics-engine/limits.mdx b/src/content/docs/analytics/analytics-engine/limits.mdx
index d4eb97a73b95fcb..293093c33e3343b 100644
--- a/src/content/docs/analytics/analytics-engine/limits.mdx
+++ b/src/content/docs/analytics/analytics-engine/limits.mdx
@@ -13,10 +13,10 @@ products:
 
 The following limits apply to Workers Analytics Engine:
 
-- Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
-- The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
-- Each index must not be more than 96 bytes.
-- You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
+* Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
+* The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
+* Each index must not be more than 96 bytes.
+* You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
 
 ## Data retention
 
diff --git a/src/content/docs/analytics/analytics-engine/pricing.mdx b/src/content/docs/analytics/analytics-engine/pricing.mdx
index bef373bc86ebf85..059f55deae8360d 100644
--- a/src/content/docs/analytics/analytics-engine/pricing.mdx
+++ b/src/content/docs/analytics/analytics-engine/pricing.mdx
@@ -23,7 +23,7 @@ Workers Analytics Engine is priced based on two metrics — data points written
 
 Currently, you will not be billed for your use of Workers Analytics Engine. Pricing information here is shared in advance, so that you can estimate what your costs will be once Cloudflare starts billing for usage in the coming months.
 
-If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing.
+If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing. 
 :::
 
 ### Data points written
diff --git a/src/content/docs/analytics/analytics-engine/recipes/index.mdx b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
index 17c5d1b314b065e..f0a1bab71954b46 100644
--- a/src/content/docs/analytics/analytics-engine/recipes/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Example implementations of common use cases for Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sampling.mdx b/src/content/docs/analytics/analytics-engine/sampling.mdx
index bc8b75c9cac7e72..c358eadeb8f377c 100644
--- a/src/content/docs/analytics/analytics-engine/sampling.mdx
+++ b/src/content/docs/analytics/analytics-engine/sampling.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>).
+Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](https://en.wikipedia.org/wiki/Sampling_\(statistics\)).
 
 When utilizing sampling, you do not need every single data point to answer questions about a dataset. For a sufficiently large dataset, the [necessary sample size](https://select-statistics.co.uk/blog/importance-effect-sample-size/) does not depend on the size of the original population. Necessary sample size depends on the variance of your measure, the size of the subgroups you analyze, and how accurate your estimate must be.
 
@@ -24,11 +24,11 @@ At a high level, the way sampling works is:
 
 In the following sections, you will learn:
 
-- [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
-- [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
-- [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
-- [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
-- [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
+* [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
+* [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
+* [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
+* [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
+* [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
 
 ## How sampling works
 
@@ -44,15 +44,15 @@ The key point is that the map's quality does not solely depend on the resolution
 
 There are similarities between the how a mapping services handles resolution and Cloudflare Analytics delivers analytics using adaptive samples:
 
-- **How data is stored**:
-  - **Mapping service**: Imagery stored at different resolutions.
-  - **Cloudflare Analytics**: Events stored at different sample rates.
-- **How data is displayed to user**:
-  - **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
-  - **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
-- **How a resolution is selected**:
-  - **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
-  - **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
+* **How data is stored**:
+  * **Mapping service**: Imagery stored at different resolutions.
+  * **Cloudflare Analytics**: Events stored at different sample rates.
+* **How data is displayed to user**:
+  * **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
+  * **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
+* **How a resolution is selected**:
+  * **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
+  * **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
 
 ## How to read sampled data
 
@@ -87,11 +87,11 @@ If we took a [simple random sample](https://en.wikipedia.org/wiki/Simple_random_
 
 ![The same graphic as above, but now based on a 1% sample of the data.](~/assets/images/analytics/sample-data.png)
 
-Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](<https://en.wikipedia.org/wiki/Quantization_(signal_processing)>) and may even be rounded to 0 entirely.
+Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](https://en.wikipedia.org/wiki/Quantization_\(signal_processing\)) and may even be rounded to 0 entirely.
 
 This shows that while a one percent (1%) or even smaller sample of a large population may be sufficient, we may need to store a larger proportion of events for a small population to get accurate results.
 
-We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`. But if you write lots of data points to a single index value, we will start to sample.
+We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`.  But if you write lots of data points to a single index value, we will start to sample.
 
 Here is the same distribution, but now with (a simulation of) equitable sampling applied:
 
@@ -117,23 +117,23 @@ In order to get accurate results with sampled data, select an appropriate value
 
 The index has the following properties, which are important to consider when choosing an index:
 
-- Get accurate summary statistics about your entire dataset, across all index values.
-- Get an accurate count of the number of unique values of your index.
-- Get accurate summary statistics (for example, count, sum) within a particular index value.
-- See the `Top N` values of specific fields that are not in your index.
-- Filter on most fields.
-- Run other aggregations like quantiles.
+* Get accurate summary statistics about your entire dataset, across all index values.
+* Get an accurate count of the number of unique values of your index.
+* Get accurate summary statistics (for example, count, sum) within a particular index value.
+* See the `Top N` values of specific fields that are not in your index.
+* Filter on most fields.
+* Run other aggregations like quantiles.
 
 Some limitations and trade-offs to consider are:
 
-- You may not be able to get accurate unique counts of fields that are not in your index.
-  - For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
-- You may not be able to observe very rare values of fields not in the index.
-  - For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
-- You may not be able to run accurate queries across multiple indices at once.
-  - For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
-- There is no guarantee you can retrieve any one individual record.
-- You cannot necessarily reconstruct exact sequences of events.
+* You may not be able to get accurate unique counts of fields that are not in your index.
+  * For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
+* You may not be able to observe very rare values of fields not in the index.
+  * For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
+* You may not be able to run accurate queries across multiple indices at once.
+  * For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
+* There is no guarantee you can retrieve any one individual record.
+* You cannot necessarily reconstruct exact sequences of events.
 
 It is not recommended to write a unique index value on every row (like a UUID) for most use cases. While this will make it possible to retrieve individual data points very quickly, it will slow down most queries for aggregations and time series.
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-api.mdx b/src/content/docs/analytics/analytics-engine/sql-api.mdx
index 1801c7d93dbaf1a..55cfccf8e90d48f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-api.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-api.mdx
@@ -25,10 +25,10 @@ Use the dashboard to create a token with permission to read analytics data on yo
 2. Select **Create Token**.
 3. Select **Create Custom Token**.
 4. Complete the **Create Custom Token** form as follows:
-   - Give your token a descriptive name.
-   - For **Permissions** select _Account_ | _Account Analytics_ | _Read_
-   - Optionally configure account and IP restrictions and TTL.
-   - Submit and confirm the form to create the token.
+   * Give your token a descriptive name.
+   * For **Permissions** select *Account* | *Account Analytics* | *Read*
+   * Optionally configure account and IP restrictions and TTL.
+   * Submit and confirm the form to create the token.
 5. Make a note of the token string.
 
 ## Querying the API
@@ -63,7 +63,7 @@ The table will have the following columns:
 | ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | dataset                      | string   | This column will contain the dataset name in every row.                                                                                                                                                                                              |
 | timestamp                    | DateTime | The timestamp at which the event was logged in your worker.                                                                                                                                                                                          |
-| \_sample_interval            | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
+| \_sample\_interval           | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
 | index1                       | string   | The index value that was logged with the event. The value in this column is used as the key for sampling.                                                                                                                                            |
 | blob1<br/>...<br/>blob20     | string   | The blob values that were logged with the event.                                                                                                                                                                                                     |
 | double1<br/>...<br/>double20 | double   | The double values that were logged with the event.                                                                                                                                                                                                   |
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
index 62e8e01ba6ec69f..4d1827c650f3567 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## count
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
index 9a64750c492178a..f8d061a0f4b5635 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## bitAnd <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
index 46e2141c8ef25e0..9db9dac5fb7d21a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## formatDateTime
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
index 016f68450f83fef..851779802af43f3 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## bin <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
index e8a324356d02009..ebe0124792308e4 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Reference documentation describing the SQL supported by Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
index 97035f5a95abd0e..ba40ae26a6009c2 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## intDiv
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
index 40411492466534f..9a4b8089ef3d6c5 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
@@ -12,7 +12,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## length
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
index 1ddf69b03623497..f87f1a7eb19e146 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## toUInt8 <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/worker-querying.mdx b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
index 0a8521edc362e68..81c7b08511cf5ca 100644
--- a/src/content/docs/analytics/analytics-engine/worker-querying.mdx
+++ b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
@@ -11,6 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
+
 import { WranglerConfig } from "~/components";
 
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
diff --git a/src/content/docs/analytics/analytics-integrations/datadog.mdx b/src/content/docs/analytics/analytics-integrations/datadog.mdx
index 07af42f65157723..579cc03b68a207a 100644
--- a/src/content/docs/analytics/analytics-integrations/datadog.mdx
+++ b/src/content/docs/analytics/analytics-integrations/datadog.mdx
@@ -36,6 +36,7 @@ To install the Cloudflare App for Datadog:
 4. Click the **Cloudflare** tile to begin the installation.
 
 5. Next, click **Configuration** and then complete the following:
+
    - **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
 
    - **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
diff --git a/src/content/docs/analytics/analytics-integrations/index.mdx b/src/content/docs/analytics/analytics-integrations/index.mdx
index f97ccae2ade7ad9..12212b2b3fbc24f 100644
--- a/src/content/docs/analytics/analytics-integrations/index.mdx
+++ b/src/content/docs/analytics/analytics-integrations/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare Enterprise customers can use Cloudflare integrations with their preferred analytics provider and configure ready-to-use Cloudflare Dashboards. Most analytics integrations are built on Cloudflare Logs by using Logpush with either Amazon S3 bucket or GCP Storage bucket.
 
diff --git a/src/content/docs/analytics/analytics-integrations/prometheus.mdx b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
index bcee11a6e7f26eb..10a355c84e93b3d 100644
--- a/src/content/docs/analytics/analytics-integrations/prometheus.mdx
+++ b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
@@ -59,16 +59,16 @@ Create a Cloudflare API token with the following permissions:
 
 [Create token with pre-filled permissions](https://dash.cloudflare.com/profile/api-tokens?permissionGroupKeys=%5B%7B%22key%22%3A%22analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22workers_scripts%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22ssl_and_certificates%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22firewall_services%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22load_balancers%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_logs%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22magic_transit%22%2C%22type%22%3A%22read%22%7D%5D&name=Cloudflare%20Prometheus%20Exporter)
 
-| Permission                  | Access | Required |
-| --------------------------- | ------ | -------- |
-| Zone > Analytics            | Read   | Yes      |
-| Account > Account Analytics | Read   | Yes      |
-| Account > Workers Scripts   | Read   | Yes      |
-| Zone > SSL and Certificates | Read   | Optional |
-| Zone > Firewall Services    | Read   | Optional |
-| Zone > Load Balancers       | Read   | Optional |
-| Account > Logs              | Read   | Optional |
-| Account > Magic Transit     | Read   | Optional |
+| Permission | Access | Required |
+|---|---|---|
+| Zone > Analytics | Read | Yes |
+| Account > Account Analytics | Read | Yes |
+| Account > Workers Scripts | Read | Yes |
+| Zone > SSL and Certificates | Read | Optional |
+| Zone > Firewall Services | Read | Optional |
+| Zone > Load Balancers | Read | Optional |
+| Account > Logs | Read | Optional |
+| Account > Magic Transit | Read | Optional |
 
 ## Task 3 - Configure Prometheus
 
@@ -76,11 +76,11 @@ Add the exporter as a scrape target in your Prometheus configuration:
 
 ```yaml
 scrape_configs:
-  - job_name: "cloudflare"
+  - job_name: 'cloudflare'
     scrape_interval: 60s
     scrape_timeout: 30s
     static_configs:
-      - targets: ["your-worker.your-subdomain.workers.dev"]
+      - targets: ['your-worker.your-subdomain.workers.dev']
 ```
 
 ### With Basic Auth
@@ -89,14 +89,14 @@ If you configured Basic Auth on the exporter, update your Prometheus configurati
 
 ```yaml
 scrape_configs:
-  - job_name: "cloudflare"
+  - job_name: 'cloudflare'
     scrape_interval: 60s
     scrape_timeout: 30s
     basic_auth:
-      username: "your-username"
-      password: "your-password"
+      username: 'your-username'
+      password: 'your-password'
     static_configs:
-      - targets: ["your-worker.your-subdomain.workers.dev"]
+      - targets: ['your-worker.your-subdomain.workers.dev']
 ```
 
 ## Configuration
@@ -105,32 +105,32 @@ Configuration is resolved in order: **KV overrides** > **environment variables**
 
 Set environment variables in `wrangler.jsonc` or via `wrangler secret put`:
 
-| Variable                          | Default    | Description                                           |
-| --------------------------------- | ---------- | ----------------------------------------------------- |
-| `CLOUDFLARE_API_TOKEN`            | -          | Cloudflare API token (secret)                         |
-| `SCRAPE_DELAY_SECONDS`            | `300`      | Delay before fetching metrics (data propagation)      |
-| `TIME_WINDOW_SECONDS`             | `60`       | Query time window                                     |
-| `METRIC_REFRESH_INTERVAL_SECONDS` | `60`       | Background refresh interval                           |
-| `CF_ACCOUNTS`                     | -          | Comma-separated account IDs to include (default: all) |
-| `CF_ZONES`                        | -          | Comma-separated zone IDs to include (default: all)    |
-| `METRICS_DENYLIST`                | -          | Comma-separated list of metrics to exclude            |
-| `EXCLUDE_HOST`                    | `false`    | Exclude host labels from metrics                      |
-| `METRICS_PATH`                    | `/metrics` | Custom path for metrics endpoint                      |
-| `BASIC_AUTH_USER`                 | -          | Username for Basic Auth (secret)                      |
-| `BASIC_AUTH_PASSWORD`             | -          | Password for Basic Auth (secret)                      |
+| Variable | Default | Description |
+|---|---|---|
+| `CLOUDFLARE_API_TOKEN` | - | Cloudflare API token (secret) |
+| `SCRAPE_DELAY_SECONDS` | `300` | Delay before fetching metrics (data propagation) |
+| `TIME_WINDOW_SECONDS` | `60` | Query time window |
+| `METRIC_REFRESH_INTERVAL_SECONDS` | `60` | Background refresh interval |
+| `CF_ACCOUNTS` | - | Comma-separated account IDs to include (default: all) |
+| `CF_ZONES` | - | Comma-separated zone IDs to include (default: all) |
+| `METRICS_DENYLIST` | - | Comma-separated list of metrics to exclude |
+| `EXCLUDE_HOST` | `false` | Exclude host labels from metrics |
+| `METRICS_PATH` | `/metrics` | Custom path for metrics endpoint |
+| `BASIC_AUTH_USER` | - | Username for Basic Auth (secret) |
+| `BASIC_AUTH_PASSWORD` | - | Password for Basic Auth (secret) |
 
 For a full list of configuration options, refer to the [exporter README](https://github.com/cloudflare/cloudflare-prometheus-exporter#configuration).
 
 ## Endpoints
 
-| Path           | Method | Description                             |
-| -------------- | ------ | --------------------------------------- |
-| `/`            | GET    | Landing page                            |
-| `/metrics`     | GET    | Prometheus metrics                      |
-| `/health`      | GET    | Health check                            |
-| `/config`      | GET    | Get all runtime config                  |
-| `/config/:key` | PUT    | Set a config override (persisted in KV) |
-| `/config/:key` | DELETE | Reset a config key to its default       |
+| Path | Method | Description |
+|---|---|---|
+| `/` | GET | Landing page |
+| `/metrics` | GET | Prometheus metrics |
+| `/health` | GET | Health check |
+| `/config` | GET | Get all runtime config |
+| `/config/:key` | PUT | Set a config override (persisted in KV) |
+| `/config/:key` | DELETE | Reset a config key to its default |
 
 ## Available metrics
 
@@ -160,7 +160,6 @@ For a complete list of metrics with types and labels, refer to the [exporter REA
 Zones on Cloudflare's Free plan do not have access to the GraphQL Analytics API. The exporter automatically detects and skips free tier zones for metrics that require this API.
 
 Free tier zones still export:
-
 - `cloudflare_zone_certificate_validation_status` (SSL certificates)
 - `cloudflare_zone_lb_origin_weight` (Load balancer weights, if configured)
 
diff --git a/src/content/docs/analytics/custom-dashboards.mdx b/src/content/docs/analytics/custom-dashboards.mdx
index 11fc76cc324f367..49b08e4bdd64804 100644
--- a/src/content/docs/analytics/custom-dashboards.mdx
+++ b/src/content/docs/analytics/custom-dashboards.mdx
@@ -28,10 +28,10 @@ Investigate incidents so that when something goes wrong, you can create focused
 
 Custom Dashboards are available to all Cloudflare customers.
 
-| Customer type            | Dashboard limit      |
-| ------------------------ | -------------------- |
-| All Cloudflare customers | Up to 25 dashboards  |
-| Log Explorer customers   | Up to 100 dashboards |
+| Customer type | Dashboard limit |
+|---------------|-----------------|
+| All Cloudflare customers | Up to 25 dashboards |
+| Log Explorer customers | Up to 100 dashboards |
 
 ## Get started
 
@@ -39,13 +39,13 @@ Custom Dashboards are available to all Cloudflare customers.
 
 Templates are the fastest way to get value from Custom Dashboards. Each template is designed around a specific use case and includes pre-configured charts that surface the most relevant metrics.
 
-| Template                   | Use case                                                                                                                                 |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| **Bot monitoring**         | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors              |
-| **API Security**           | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns                           |
-| **Account takeover**       | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
-| **API Performance**        | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain   |
-| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time  |
+| Template | Use case |
+|----------|----------|
+| **Bot monitoring** | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors |
+| **API Security** | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns |
+| **Account takeover** | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
+| **API Performance** | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain |
+| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time |
 
 After selecting a template, you can customize it by adding, removing, or modifying charts to fit your specific needs.
 
@@ -81,15 +81,15 @@ For precise control, configure each element of your chart:
 
 Choose the visualization that best fits your data:
 
-| Chart type     | Best for                                                                                 |
-| -------------- | ---------------------------------------------------------------------------------------- |
+| Chart type | Best for |
+|------------|----------|
 | **Timeseries** | Trends and patterns over time — traffic spikes, latency changes, error rate fluctuations |
-| **Bar**        | Comparing values across categories — requests by country, errors by status code          |
-| **Donut**      | Understanding proportions — cache hit ratio, traffic distribution by content type        |
-| **Map**        | Geographic patterns — where your traffic originates, regional performance differences    |
-| **Stat**       | Single important numbers — total requests today, current error rate, p99 latency         |
-| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion                          |
-| **Top N**      | Rankings — busiest endpoints, most blocked IPs, top user agents                          |
+| **Bar** | Comparing values across categories — requests by country, errors by status code |
+| **Donut** | Understanding proportions — cache hit ratio, traffic distribution by content type |
+| **Map** | Geographic patterns — where your traffic originates, regional performance differences |
+| **Stat** | Single important numbers — total requests today, current error rate, p99 latency |
+| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion |
+| **Top N** | Rankings — busiest endpoints, most blocked IPs, top user agents |
 
 #### Example: Build a security overview chart
 
diff --git a/src/content/docs/analytics/faq/about-analytics.mdx b/src/content/docs/analytics/faq/about-analytics.mdx
index 53d5f449641933e..027f8a07eb32e94 100644
--- a/src/content/docs/analytics/faq/about-analytics.mdx
+++ b/src/content/docs/analytics/faq/about-analytics.mdx
@@ -23,10 +23,10 @@ Refer to [Types of analytics](/analytics/types-of-analytics/) for more informati
 
 The underlying datasets that Cloudflare Analytics captures and processes share the following characteristics:
 
-- All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
-- Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
-- Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
-- In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
+* All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
+* Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
+* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
+* In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
 
 ## Apparent data discrepancies
 
@@ -42,10 +42,10 @@ Finally, it is likely that unique visitor data from the Cloudflare Analytics app
 
 You may not be seeing metrics on Cloudflare Analytics for the following reasons:
 
-- You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
-- If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
-- If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
-- Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
+* You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
+* If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
+* If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
+* Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
 
 :::note
 Activations through a hosting partner works via a [CNAME setup](/dns/zone-setups/partial-setup/) on the `www` record. If most of your traffic actually goes to `domain.com`, [forward your traffic](/rules/url-forwarding/bulk-redirects/) from `domain.com` to `www.domain.com`.
diff --git a/src/content/docs/analytics/faq/index.mdx b/src/content/docs/analytics/faq/index.mdx
index 555fcdc07a3795f..c7d87c530a29c24 100644
--- a/src/content/docs/analytics/faq/index.mdx
+++ b/src/content/docs/analytics/faq/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Visit the following pages for commonly asked questions:
 
diff --git a/src/content/docs/analytics/faq/other-faqs.mdx b/src/content/docs/analytics/faq/other-faqs.mdx
index 86adb232c817e4d..4e9145ab25ee9ae 100644
--- a/src/content/docs/analytics/faq/other-faqs.mdx
+++ b/src/content/docs/analytics/faq/other-faqs.mdx
@@ -15,8 +15,10 @@ There is a number of different types of traffic which may originate from **CLOUD
 
 Some sources of traffic from ASN13335 include:
 
-- [Workers subrequests](/workers/runtime-apis/fetch/)
-- [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
-- [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
-- [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
-- Other Cloudflare features like [Health Checks](/health-checks/)
+* [Workers subrequests](/workers/runtime-apis/fetch/)
+* [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
+* [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
+* [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
+* Other Cloudflare features like [Health Checks](/health-checks/)
+
+
diff --git a/src/content/docs/analytics/faq/wae-faqs.mdx b/src/content/docs/analytics/faq/wae-faqs.mdx
index b88ec97467a6ce7..3693060a2bb2ab8 100644
--- a/src/content/docs/analytics/faq/wae-faqs.mdx
+++ b/src/content/docs/analytics/faq/wae-faqs.mdx
@@ -23,24 +23,29 @@ On the other hand, if you pick a good index that aligns with how you read the da
 
 ### What if I need to index on multiple values?
 
+
 It is possible to concatenate multiple values in your index field. So if you want to index on user ID and hostname, you can write, for example `"$userID:$hostname"` into your index field.
 
 Note that, based on your query pattern, it may make sense to write the same dataset with different indices. It is a common misconception that one should avoid "double-writing" data.
 
 Thanks to sampling, the cost of writing data multiple times can be relatively low. However, reading data inefficiently can result in significant expenses or low-quality results due to sampling.
 
+
 ### How do I know if my data is sampled?
 
 You can use the `_sample_interval` field — again, note that this does not tell you if the results are accurate.
 
 You can tell when data is sampled at read time because sample intervals will be multiples of powers of 10, for example `20` or `700`. There is no hard and fast rule for when sampling starts at read time, but in practice reading longer periods (or more index values) will result in a higher sample interval.
 
+
 ### Why is data missing?
 
+
 Sampling is based largely on the choice of index, as well as other factors like the time range queried and number of indices read. If you are reading from a larger index over a longer time period, and have filtered to a relatively small subgroup within that index, it may not be present due to sampling.
 
 If you need to read accurate results for that subgroup, we suggest that you add that field to your index (refer to [What if I need to index on multiple values](/analytics/faq/wae-faqs/#what-if-i-need-to-index-on-multiple-values)).
 
+
 ### Can I trust sampled data? Are my results accurate?
 
 Sampled data is highly reliable, particularly when a carefully selected index is used.
@@ -51,7 +56,7 @@ In the near future, we plan to expose the [margin of error](https://en.wikipedia
 
 ### How are bursts handled?
 
-Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time. The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
+Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time.  The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
 
 ### How much traffic will trigger sampling?
 
@@ -60,3 +65,5 @@ There is no fixed rule determining when sampling will be triggered.
 We have observed that for workloads like our global CDN, which distribute load around our network, each index value needs about 100 data points per second before sampling is noticeable at all.
 
 Depending on your workload and how you use Workers Analytics Engine, sampling may start at a higher or lower threshold than this. For example, if you are writing out many data points from a single worker execution, it is more likely that your data will be sampled.
+
+
diff --git a/src/content/docs/analytics/graphql-api/errors.mdx b/src/content/docs/analytics/graphql-api/errors.mdx
index aeead71c606fc32..b40d61df3dca927 100644
--- a/src/content/docs/analytics/graphql-api/errors.mdx
+++ b/src/content/docs/analytics/graphql-api/errors.mdx
@@ -13,24 +13,24 @@ The GraphQL Analytics API is a RESTful API based on HTTPS requests and JSON resp
 
 All responses contain an `errors` array, which will be `null` if there are no errors, and include at least one error object if there was an error. Non-null error objects will contain the following fields:
 
-- `message`: a string describing the error.
-- `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
-- `timestamp`: UTC datetime when the error occurred.
+* `message`: a string describing the error.
+* `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
+* `timestamp`: UTC datetime when the error occurred.
 
 ## Example
 
 ```json
 {
-	"data": null,
-	"errors": [
-		{
-			"message": "cannot request data older than 2678400s",
-			"path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
-			"extensions": {
-				"timestamp": "2019-12-09T21:27:19.195060142Z"
-			}
-		}
-	]
+  "data": null,
+  "errors": [
+    {
+      "message": "cannot request data older than 2678400s",
+      "path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
+      "extensions": {
+        "timestamp": "2019-12-09T21:27:19.195060142Z"
+      }
+    }
+  ]
 }
 ```
 
@@ -40,8 +40,8 @@ All responses contain an `errors` array, which will be `null` if there are no er
 
 Sample error messages:
 
-- `unable to execute query, please try again later` (HTTP `503`)
-- `too many queries in progress, please try again later` (HTTP `503`)
+* `unable to execute query, please try again later` (HTTP `503`)
+* `too many queries in progress, please try again later` (HTTP `503`)
 
 These messages indicate a temporary server-side issue. The first message typically means the upstream database is unreachable or returned an error. The second message means the server has reached its maximum number of concurrent queries.
 
@@ -51,10 +51,10 @@ Retry the request after a short delay. If the error persists, check the [Cloudfl
 
 Sample error messages:
 
-- `cannot request data older than...` (HTTP `400`)
-- `number of fields can't be more than...` (HTTP `400`)
-- `limit must be positive number and not greater than...` (HTTP `400`)
-- `query time range is too large...` (HTTP `400`)
+* `cannot request data older than...` (HTTP `400`)
+* `number of fields can't be more than...` (HTTP `400`)
+* `limit must be positive number and not greater than...` (HTTP `400`)
+* `query time range is too large...` (HTTP `400`)
 
 These messages indicate that the query exceeds what is allowed for the particular dataset under the current [plan](https://www.cloudflare.com/plans/), and an upgrade should be considered. Refer to [Node limits](/analytics/graphql-api/limits/#node-limits-and-availability) for details.
 
@@ -62,11 +62,11 @@ These messages indicate that the query exceeds what is allowed for the particula
 
 Sample error messages:
 
-- `error parsing args...` (HTTP `400`)
-- `scalar fields must have no selections` (HTTP `400`)
-- `object field must have selections` (HTTP `400`)
-- `unknown field...` (HTTP `400`)
-- `query contains error, please review it and retry` (HTTP `400`)
+* `error parsing args...` (HTTP `400`)
+* `scalar fields must have no selections` (HTTP `400`)
+* `object field must have selections` (HTTP `400`)
+* `unknown field...` (HTTP `400`)
+* `query contains error, please review it and retry` (HTTP `400`)
 
 These messages indicate that the query cannot be processed because it is malformed. Check the query syntax against the [GraphQL schema](/analytics/graphql-api/getting-started/explore-graphql-schema/) and correct the invalid fields or structure.
 
@@ -74,9 +74,9 @@ These messages indicate that the query cannot be processed because it is malform
 
 Sample error messages:
 
-- `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
-- `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
-- `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
+* `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
+* `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
+* `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
 
 These messages indicate the query exceeded rate or resource limits. Reduce the query complexity, the number of zones or accounts per request, or wait before retrying. Refer to the [Limits](/analytics/graphql-api/limits/) section for more details about rate limits.
 
@@ -84,10 +84,10 @@ These messages indicate the query exceeded rate or resource limits. Reduce the q
 
 Sample error messages:
 
-- `Unauthorized` (HTTP `401`)
-- `not authorized for that account` (HTTP `403`)
-- `zones [...] are not authorized` (HTTP `403`)
-- `does not have access to the path...` (HTTP `403`)
+* `Unauthorized` (HTTP `401`)
+* `not authorized for that account` (HTTP `403`)
+* `zones [...] are not authorized` (HTTP `403`)
+* `does not have access to the path...` (HTTP `403`)
 
 An `Unauthorized` response means the API token or bearer token is missing, expired, or invalid. Verify that you are passing a valid token in the `Authorization` header.
 
@@ -97,6 +97,6 @@ A `403` response means the token does not have the required permissions for the
 
 Sample error message:
 
-- `Internal server error` (HTTP `500`)
+* `Internal server error` (HTTP `500`)
 
 This is a generic error indicating an unexpected failure. If it persists, contact [Cloudflare Support](https://support.cloudflare.com/) with the full request and response, including the `Ray-ID` header from the HTTP response.
diff --git a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
index 4900a64e4e2b8ff..2def716afc95aff 100644
--- a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
+++ b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
@@ -9,14 +9,14 @@ products:
   - graphql-api
 ---
 
-Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time.
+Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time. 
 
 ## Availability
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`).
-- **Default**: If no confidence level is specified, intervals are not returned.
+- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`). 
+- **Default**: If no confidence level is specified, intervals are not returned. 
 
 ## Usage example
 
@@ -28,35 +28,35 @@ To request a confidence interval, use the `confidence(level: X)` argument in you
 
 ```graphql graphql-api-explorer title="A GraphQL query"
 query SingleDatasetWithConfidence($zoneTag: string, $start: Time, $end: Time) {
-	viewer {
-		zones(filter: { zoneTag: $zoneTag }) {
-			firewallEventsAdaptiveGroups(
-				filter: { datetime_gt: $start, datetime_lt: $end }
-				limit: 1000
-			) {
-				count
-				avg {
-					sampleInterval
-				}
-				confidence(level: 0.95) {
-					count {
-						estimate
-						lower
-						upper
-						sampleSize
-					}
-				}
-			}
-		}
-	}
+  viewer {
+    zones(filter: {zoneTag: $zoneTag}) {
+      firewallEventsAdaptiveGroups(
+        filter: {datetime_gt: $start, datetime_lt: $end}
+        limit: 1000
+      ) {
+        count
+        avg {
+          sampleInterval
+        }
+        confidence(level: 0.95) {
+          count {
+            estimate
+            lower
+            upper
+            sampleSize
+          }
+        }
+      }
+    }
+  }
 }
 ```
 
 ### Response
 
-The response includes the following values:
+The response includes the following values: 
 
-- `estimate`: The estimated value, based on sampled data.
+- `estimate`: The estimated value, based on sampled data. 
 - `lower`: The lower bound of the confidence interval.
 - `sampleSize`: The number of sampled data points used to calculate the estimate.
 - `upper`: The upper bound of the confidence interval.
@@ -65,30 +65,30 @@ In this example, the interpretation of the response is that, based on a sample o
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"firewallEventsAdaptiveGroups": [
-						{
-							"avg": {
-								"sampleInterval": 1.0720277625205972
-							},
-							"confidence": {
-								"count": {
-									"estimate": 42939,
-									"lower": 42673.44115335711,
-									"sampleSize": 40054,
-									"upper": 43204.55884664289
-								}
-							},
-							"count": 42939
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "firewallEventsAdaptiveGroups": [
+            {
+              "avg": {
+                "sampleInterval": 1.0720277625205972
+              },
+              "confidence": {
+                "count": {
+                  "estimate": 42939,
+                  "lower": 42673.44115335711,
+                  "sampleSize": 40054,
+                  "upper": 43204.55884664289
+                }
+              },
+              "count": 42939
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
diff --git a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
index d7db4d153f586f2..74c6b40c78266f7 100644
--- a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
@@ -13,4 +13,5 @@ GraphQL API supports [introspection][1] to explore nodes and provides a way to
 retrieve the user's [limits][2] for every node.
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
+
 [2]: /analytics/graphql-api/features/discovery/settings/
diff --git a/src/content/docs/analytics/graphql-api/features/index.mdx b/src/content/docs/analytics/graphql-api/features/index.mdx
index 39fea17f29b3b37..7b85fab58b64d62 100644
--- a/src/content/docs/analytics/graphql-api/features/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The GraphQL Analytics API offers the following features:
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
index c6a25630a2aedd7..0e458b325ede871 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
@@ -17,13 +17,13 @@ products:
    ![Editing HTTP Headers Window](~/assets/images/analytics/GraphiQL-edit-http-headers-window.png)
 
 3. Select **Add Header** to configure authentication. You can use Cloudflare Analytics API token authentication (recommended) or Cloudflare API key authentication.
-   - **Token authentication**:
+   * **Token authentication**:
 
      Enter **Authorization** in the **Header Name** field, and enter `Bearer {your-analytics-token}` in the **Header value** field, then select **Save**.
 
      ![Editing HTTP Headers](~/assets/images/analytics/GraphiQL-edit-http-headers-token.png)
 
-   - **Key authentication**:
+   * **Key authentication**:
 
      Enter `X-AUTH-EMAIL` in the **Header name** field and your email address registered with Cloudflare in the **Header value** field, and select **Save**.<br/>
 
@@ -36,8 +36,10 @@ products:
 
 :::note[Note]
 
+
 The right-side response pane is empty when you enter your information correctly. An error displays when there are problems with your header credentials.
 
+
 :::
 
 Now that you have configured authentication, you are ready to run queries using GraphiQL.
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
index 1e96ffce7142c4b..ed75b1965e7c919 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
@@ -15,40 +15,30 @@ To secure access to your GraphQL Analytics data, use a Cloudflare API key or tok
 
 This table outlines the differences between Cloudflare API keys and tokens:
 
+
+
 <table>
-	<thead>
-		<tr>
-			<th>Authentication Method</th>
-			<th>Description</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>
-				<a href="/fundamentals/api/get-started/create-token/">API Tokens</a>
-			</td>
-			<td>
-				Cloudflare recommends API Tokens as the preferred way to interact with
-				Cloudflare APIs. You can configure the scope of tokens to limit access
-				to account and zone resources, and you can define the Cloudflare APIs to
-				which the token authorizes access.
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/fundamentals/api/get-started/keys/">API Keys</a>
-			</td>
-			<td>
-				<p>
-					Unique to each Cloudflare user and used only for authentication. API
-					keys do not authorize access to accounts or zones.
-				</p>
-				<p>Use the Global API Key for authentication.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+      <tr>
+          <th>Authentication Method</th>
+          <th>Description</th>
+      </tr>
+  </thead>
+  <tbody>
+      <tr>
+        <td><a href='/fundamentals/api/get-started/create-token/'>API Tokens</a></td>
+        <td>Cloudflare recommends API Tokens as the preferred way to interact with Cloudflare APIs. You can configure the scope of tokens to limit access to account and zone resources, and you can define the Cloudflare APIs to which the token authorizes access.</td>
+      </tr>
+      <tr>
+        <td><a href='/fundamentals/api/get-started/keys/'>API Keys</a></td>
+        <td><p>Unique to each Cloudflare user and used only for authentication. API keys do not authorize access to accounts or zones.</p>
+        <p>Use the Global API Key for authentication.</p></td>
+      </tr>
+  </tbody>
 </table>
 
+
+
 To create and configure GraphQL Analytics API tokens, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
 
 To find and retrieve API keys, as well as edit HTTP headers for authentication in GraphiQL, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
diff --git a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
index 4494649d7315149..1839c3f0876e56b 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
@@ -28,11 +28,13 @@ Click on the editing pane of GraphiQL and add this base query, replacing
 
 :::note[Note]
 
+
 To find the zone's tag, log in to your Cloudflare account and select the site for
 which you want to obtain the tag. In the Cloudflare dashboard **Overview** page,
 scroll to the **API** section in the right sidebar, which displays your zone and
 account tags.
 
+
 :::
 
 To assist query building, the GraphiQL client has word completion. Insert your
@@ -126,16 +128,29 @@ This example query uses the `zoneTag` query variable to represent the zone ID:
 ![Example of GraphiQL query variables][14]
 
 [1]: /analytics/graphql-api/getting-started/querying-basics/
+
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
+
 [3]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
+
 [4]: ~/assets/images/analytics/graphiql-base-query.png
+
 [5]: ~/assets/images/analytics/graphiql-word-completion.png
+
 [6]: ~/assets/images/analytics/graphiql-set-up-base-query.png
+
 [7]: ~/assets/images/analytics/graphiql-parameters.png
+
 [8]: ~/assets/images/analytics/graphiql-filter-fields.png
+
 [9]: ~/assets/images/analytics/graphiql-filter-values.png
+
 [10]: ~/assets/images/analytics/graphiql-set-up-base-query.png
+
 [11]: ~/assets/images/analytics/graphiql-return-fields.png
+
 [12]: ~/assets/images/analytics/graphiql-query-return-field-values.png
+
 [13]: ~/assets/images/analytics/create-query-fw-data-set-play.png
+
 [14]: ~/assets/images/analytics/graphiql-query-variables.png
diff --git a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
index b1eeb322c398cb7..ab3680fa9a78abb 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
@@ -24,8 +24,8 @@ query:
 
 ```json title="A payload structure for GraphQL API"
 {
-	"query": "{viewer { ... }}",
-	"variables": {}
+  "query": "{viewer { ... }}",
+  "variables": {}
 }
 ```
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
index e77cba62457a8e1..0d2d0e248a08cf0 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
@@ -79,7 +79,7 @@ query.
 
 For example, `zones` can take a filter of `ZoneFilter_InputObject` type as an
 argument. To view the fields available to filter, select
-**ZoneFilter_InputObject**.
+**ZoneFilter\_InputObject**.
 
 ## Find the datasets available for a zone
 
@@ -122,18 +122,33 @@ The list of fields displays:
 For more information on using GraphiQL, please visit this [guide][16].
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
+
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
+
 [3]: https://altairgraphql.dev/#download
+
 [4]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
+
 [5]: ~/assets/images/analytics/graphiql-docs-link.png
+
 [6]: ~/assets/images/analytics/graphiql-doc-explorer.png
+
 [7]: ~/assets/images/analytics/graphiql-doc-explorer-query-mutations.png
+
 [8]: ~/assets/images/analytics/graphiql-doc-explorer-view-cost.png
+
 [9]: ~/assets/images/analytics/graphiql-doc-explorer-viewer-fields.png
+
 [10]: ~/assets/images/analytics/graphiql-doc-explorer-zones.png
+
 [11]: ~/assets/images/analytics/graphiql-doc-explorer-zone-fields.png
+
 [12]: ~/assets/images/analytics/graphiql-doc-explorer-find-firewall.png
+
 [13]: ~/assets/images/analytics/graphiql-doc-explorer-firewallevents-definition.png
+
 [14]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-type-definition.png
+
 [15]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-fields.png
+
 [16]: /analytics/graphql-api/getting-started/compose-graphql-query/
diff --git a/src/content/docs/analytics/graphql-api/getting-started/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
index 6b82273dfd942ef..2ba6111561b125e 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
@@ -9,19 +9,19 @@ products:
   - graphql-api
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Use these articles to get started with the Cloudflare GraphQL API:
 
-- [Authentication][1] - walks you through the options and the steps required to
+* [Authentication][1] - walks you through the options and the steps required to
   set up your access to Cloudflare API successfully,
-- [Querying basics][2] - brings simple query examples for you to start exploring
+* [Querying basics][2] - brings simple query examples for you to start exploring
   the GraphQL API,
-- [Introspect the GraphQL schema][3] - explains how-to surf the schema with
+* [Introspect the GraphQL schema][3] - explains how-to surf the schema with
   GraphQL client,
-- [Create a query in a GraphQL client][4] - describes how to build and run a
+* [Create a query in a GraphQL client][4] - describes how to build and run a
   query against the Cloudflare GraphQL API in the GraphQL clients,
-- [Use curl to query the GraphQL API][5] - walks you through running a query
+* [Use curl to query the GraphQL API][5] - walks you through running a query
   against the Cloudflare GraphQL API from the command line.
 
 For examples of how to build your own GraphQL Analytics dashboard and query
@@ -29,13 +29,17 @@ specific information, such as Firewall and Workers events, please refer to
 [Tutorials][6].
 
 :::note[Data unavailability: Customer Metadata Boundary configuration]
-
-<Render file="customer_metadata_boundary_error" product="analytics" />
+ <Render file="customer_metadata_boundary_error" product="analytics" /> 
 :::
 
 [1]: /analytics/graphql-api/getting-started/authentication/
+
 [2]: /analytics/graphql-api/getting-started/querying-basics/
+
 [3]: /analytics/graphql-api/getting-started/explore-graphql-schema/
+
 [4]: /analytics/graphql-api/getting-started/compose-graphql-query/
+
 [5]: /analytics/graphql-api/getting-started/execute-graphql-query/
+
 [6]: /analytics/graphql-api/tutorials/
diff --git a/src/content/docs/analytics/graphql-api/limits.mdx b/src/content/docs/analytics/graphql-api/limits.mdx
index 41bac079ca31cd6..5adcc44092add47 100644
--- a/src/content/docs/analytics/graphql-api/limits.mdx
+++ b/src/content/docs/analytics/graphql-api/limits.mdx
@@ -19,16 +19,16 @@ plans.
 To support this variety of products, Cloudflare GraphQL API has three layers of
 limits:
 
-- global limits
-- user limits
-- node (dataset) limits
+* global limits
+* user limits
+* node (dataset) limits
 
 ## Global limits
 
 These limits are applied to every query for every plan:
 
-- A zone-scoped query can include up to **10 zones**
-- An account-scoped query can include only **1 account**
+* A zone-scoped query can include up to **10 zones**
+* An account-scoped query can include only **1 account**
 
 Additionally, there is a limited number of queries you can make per request. The total number of queries in a request is equal to the number of zone/account scopes, multiplied by the number of nodes to which they are applied.
 
@@ -46,10 +46,10 @@ the Cloudflare API](/fundamentals/api/reference/limits/).
 
 Each data node has its limits, such as:
 
-- how far back in time can data be requested,
-- the maximum time period (in seconds) that can be requested in one query,
-- the maximum number of fields that can be requested in one query,
-- the maximum number of records that can be returned in one query.
+* how far back in time can data be requested,
+* the maximum time period (in seconds) that can be requested in one query,
+* the maximum number of fields that can be requested in one query,
+* the maximum number of records that can be returned in one query.
 
 Node limits are tied to requested `zoneTag` or `accountTag`. Higher plans have
 access to a greater selection of datasets or fields, and can query over broader historical
diff --git a/src/content/docs/analytics/graphql-api/mcp-server.mdx b/src/content/docs/analytics/graphql-api/mcp-server.mdx
index 79aea053b1121fa..be3bc98608dc365 100644
--- a/src/content/docs/analytics/graphql-api/mcp-server.mdx
+++ b/src/content/docs/analytics/graphql-api/mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the GraphQL Analytics MCP server.
 products:
   - analytics
   - graphql-api
----
+---
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
index a0cd2058706d926..4255d116dd9db69 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
@@ -17,8 +17,8 @@ If you are currently using the deprecated `httpRequests1mByColoGroups` or `httpR
 
 If you are currently using the Zone Analytics API, the following guide will help you migrate your queries to the new GraphQL Analytics API:
 
-- [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
-- [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
+* [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
+* [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
 
 ## Network Analytics migrations
 
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
index cfec218853327ed..f6c3398fe285308 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: reference
 title: NAv1 to NAv2 schema map
 sidebar:
diff --git a/src/content/docs/analytics/graphql-api/sampling.mdx b/src/content/docs/analytics/graphql-api/sampling.mdx
index 2dcf4bdf7261ff2..ce5299faa9407b8 100644
--- a/src/content/docs/analytics/graphql-api/sampling.mdx
+++ b/src/content/docs/analytics/graphql-api/sampling.mdx
@@ -38,11 +38,15 @@ Cloudflare almost always uses **adaptive sampling**, which means the sample rate
 
 The following data nodes are based on fixed sampling, where the sample rate does not vary:
 
+
+
 | Data set                                                                                                                                       |   Rate | Notes                                                                                                                                                                                                |
 | :--------------------------------------------------------------------------------------------------------------------------------------------- | -----: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Firewall Rules Preview<br /><p><b>Nodes:</b><br />`firewallRulePreviewGroups`</p>                                                              |     1% | Use with caution. A 1% sample rate does not provide accurate estimates for datasets smaller than a certain threshold, a scenario the Cloudflare dashboard calls out explicitly but the API does not. |
 | Network Analytics<br /><p><b>Nodes:</b><br />`ipFlows1mGroups`<br />`ipFlows1hGroups`<br />`ipFlows1dGroups`<br />`ipFlows1mAttacksGroups`</p> | 0.012% | Sampling rate is in terms of packet count (1 of every 8,192 packets).                                                                                                                                |
 
+
+
 ## Access to raw data
 
 Because sampling is primarily adaptive and automatically adjusts to provide an accurate estimate, the sampling rate cannot be directly controlled. Enterprise customers have access to raw data via Cloudflare Logs.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
index b7bf522c3840234..c74285316775d50 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
@@ -54,107 +54,107 @@ The returned results will be in JSON format (as requested), so piping the output
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"httpRequestsAdaptiveGroups": [
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-21T10:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19849385,
-								"visits": 4383
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-21T06:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20607204,
-								"visits": 4375
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-26T05:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20170839,
-								"visits": 4519
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-23T08:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20141860,
-								"visits": 4448
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-25T15:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 21070367,
-								"visits": 4469
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-28T08:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19200774,
-								"visits": 4345
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-26T02:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20758067,
-								"visits": 4502
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-20T19:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 22127811,
-								"visits": 4443
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-27T15:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20480644,
-								"visits": 4268
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-27T17:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19885704,
-								"visits": 4287
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "httpRequestsAdaptiveGroups": [
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-21T10:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19849385,
+                "visits": 4383
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-21T06:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20607204,
+                "visits": 4375
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-26T05:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20170839,
+                "visits": 4519
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-23T08:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20141860,
+                "visits": 4448
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-25T15:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 21070367,
+                "visits": 4469
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-28T08:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19200774,
+                "visits": 4345
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-26T02:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20758067,
+                "visits": 4502
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-20T19:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 22127811,
+                "visits": 4443
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-27T15:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20480644,
+                "visits": 4268
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-27T17:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19885704,
+                "visits": 4287
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
@@ -162,13 +162,13 @@ The returned results will be in JSON format (as requested), so piping the output
 
 We are going to use the GraphQL Analytics API to query the top 10 consuming URLs from a zone, helping you identify the URLs with the highest resource usage. Here are some configuration instructions:
 
-- To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
-- Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
-- Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
-- To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
-  - `CURRENTDATE=$(gdate -u +'%FT%TZ')`
-  - `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
-- For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
+* To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
+* Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
+* Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
+* To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
+  * `CURRENTDATE=$(gdate -u +'%FT%TZ')`
+  * `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
+* For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
 
 ### API call
 
@@ -196,4 +196,4 @@ https://api.cloudflare.com/client/v4/graphql \
 }' | jq -r 'try .data.viewer.zones[].topPaths[] | "\"\(.dimensions.metric)\": \(.sum.edgeResponseBytes)"' | sort
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/index.mdx b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
index ebcfb6d0cf8b7b2..baf7496c1ef4723 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/index.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The following resources will help you start exploring your data and creating analytics dashboards:
 
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
index 7f0e232f641a485..4fbbc812304c501 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
@@ -15,9 +15,9 @@ The following API call will request logs for a single Access login event and out
 
 You will need to insert your `<CLOUDFLARE_ACCOUNT_TAG>`, your API credentials in `<API_TOKEN>`[^1], and substitute your own values for the following variables:
 
-- `rayID`: A unique identifier assigned to the authentication request.
-- `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
-- `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
+* `rayID`: A unique identifier assigned to the authentication request.
+* `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
+* `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
 
 ## API Call
 
@@ -65,47 +65,47 @@ https://api.cloudflare.com/client/v4/graphql \
 
 :::note
 
-Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`.
+Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`. 
 :::
 
 ## Response
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"accounts": [
-				{
-					"accessLoginRequestsAdaptiveGroups": [
-						{
-							"dimensions": {
-								"approvingPolicyId": "",
-								"cfRayId": "744927037ce06d68",
-								"country": "US",
-								"datetime": "2022-09-02T20:56:27Z",
-								"deviceId": "",
-								"hasExistingJWT": 0,
-								"hasGatewayEnabled": 0,
-								"hasWarpEnabled": 0,
-								"identityProvider": "nonidentity",
-								"ipAddress": "2a09:bac0:15::814:7b37",
-								"isSuccessfulLogin": 0,
-								"mtlsCertSerialId": "",
-								"mtlsCommonName": "",
-								"mtlsStatus": "NONE",
-								"serviceTokenId": "",
-								"userUuid": ""
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "accounts": [
+        {
+          "accessLoginRequestsAdaptiveGroups": [
+            {
+              "dimensions": {
+                "approvingPolicyId": "",
+                "cfRayId": "744927037ce06d68",
+                "country": "US",
+                "datetime": "2022-09-02T20:56:27Z",
+                "deviceId": "",
+                "hasExistingJWT": 0,
+                "hasGatewayEnabled": 0,
+                "hasWarpEnabled": 0,
+                "identityProvider": "nonidentity",
+                "ipAddress": "2a09:bac0:15::814:7b37",
+                "isSuccessfulLogin": 0,
+                "mtlsCertSerialId": "",
+                "mtlsCommonName": "",
+                "mtlsStatus": "NONE",
+                "serviceTokenId": "",
+                "userUuid": ""
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
 You can compare the query results to your Access policies to understand why a user was blocked. For example, if your application requires a valid mTLS certificate, Access blocked the request shown above because `mtlsStatus`, `mtlsCommonName`, and `mtlsCertSerialId` are empty.
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
index 3e8f9dde667b2df..ccd12acea299f70 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
@@ -65,74 +65,74 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"emailRoutingAdaptive": [
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:51:25Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "John <john@email.example.com>",
-							"id": "AfWyaZ7V1TAH",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "How are you doing?",
-							"to": "me@example.com"
-						},
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:30:00Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "eBay <ebay@ebay.co.uk>",
-							"id": "aYPegrIfLWia",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "New offers",
-							"to": "me@example.com"
-						},
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:29:59Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "Notification <notifications@example.com>",
-							"id": "nWIl9gs95mY3",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "You're over quota",
-							"to": "me@example.com"
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "emailRoutingAdaptive": [
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:51:25Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "John <john@email.example.com>",
+              "id": "AfWyaZ7V1TAH",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "How are you doing?",
+              "to": "me@example.com"
+            },
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:30:00Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "eBay <ebay@ebay.co.uk>",
+              "id": "aYPegrIfLWia",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "New offers",
+              "to": "me@example.com"
+            },
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:29:59Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "Notification <notifications@example.com>",
+              "id": "nWIl9gs95mY3",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "You're over quota",
+              "to": "me@example.com"
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
@@ -176,114 +176,114 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"emailRoutingAdaptiveGroups": [
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T11:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T12:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T13:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T14:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T15:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T16:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T17:00:00Z"
-							}
-						},
-						{
-							"count": 3,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T18:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T22:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T01:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T02:00:00Z"
-							}
-						},
-						{
-							"count": 4,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T05:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T08:00:00Z"
-							}
-						},
-						{
-							"count": 5,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T09:00:00Z"
-							}
-						},
-						{
-							"count": 6,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T10:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T11:00:00Z"
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "emailRoutingAdaptiveGroups": [
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T11:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T12:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T13:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T14:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T15:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T16:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T17:00:00Z"
+              }
+            },
+            {
+              "count": 3,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T18:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T22:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T01:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T02:00:00Z"
+              }
+            },
+            {
+              "count": 4,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T05:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T08:00:00Z"
+              }
+            },
+            {
+              "count": 5,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T09:00:00Z"
+              }
+            },
+            {
+              "count": 6,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T10:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T11:00:00Z"
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
index 3d4c56d42ef286d..deab15ea91ace34 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
@@ -9,9 +9,8 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-endpoint-health-checks"
+<Render file="graphql/query-magic-transit-endpoint-health-checks"
 	product="networking-services"
 />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
index 0c1fc135106eaa8..727a62e37b0ac21 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
@@ -9,10 +9,8 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
-	params={{ productName: "Magic Transit or Cloudflare WAN" }}
-/>
+	params={{ productName: "Magic Transit or Cloudflare WAN" }} />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
index 7e2d5a042de9744..3ed3c1e2b7fce50 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
@@ -9,10 +9,9 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
 	params={{ productName: "Magic Transit or Cloudflare WAN" }}
 />
diff --git a/src/content/docs/analytics/index.mdx b/src/content/docs/analytics/index.mdx
index 7f6b64667dccaec..8c9eca78825e740 100644
--- a/src/content/docs/analytics/index.mdx
+++ b/src/content/docs/analytics/index.mdx
@@ -11,52 +11,38 @@ products:
   - analytics
 ---
 
-import { Feature, RelatedProduct } from "~/components";
+import { Feature, RelatedProduct } from "~/components"
 
 Cloudflare visualizes the metadata collected by our products in the Cloudflare dashboard. Refer to [Types of analytics](/analytics/types-of-analytics/) for more information about the various types of analytics and where they exist in the dashboard.
 
----
+***
 
 ## Features
 
 <Feature header="Workers Analytics Engine" href="/analytics/analytics-engine/">
-	Send unlimited-cardinality data from your Worker to a time-series database.
-	Query it with SQL.
+Send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL. 
 </Feature>
 
-<Feature
-	header="Account and zone analytics"
-	href="/analytics/account-and-zone-analytics/"
->
-	Provides details about the requests and traffic related to your Cloudflare
-	accounts and zones.
+<Feature header="Account and zone analytics" href="/analytics/account-and-zone-analytics/">
+Provides details about the requests and traffic related to your Cloudflare accounts and zones. 
 </Feature>
 
-<Feature
-	header="Cloudflare Network Analytics"
-	href="/analytics/network-analytics/"
->
-	Provides near real-time visibility into network and transport-layer traffic
-	patterns and DDoS attacks.
+<Feature header="Cloudflare Network Analytics" href="/analytics/network-analytics/">
+Provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. 
 </Feature>
 
 <Feature header="GraphQL Analytics API" href="/analytics/graphql-api/">
-	Provides all of your performance, security, and reliability data from one
-	endpoint. Select exactly what you need, from one metric for a domain to
-	multiple metrics aggregated for your account.
+Provides all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account. 
 </Feature>
 
----
+***
 
 ## Related products
 
 <RelatedProduct header="Workers" href="/workers/" product="workers">
-	Cloudflare Workers allows developers to build serverless applications and
-	deploy instantly across the globe for exceptional performance, reliability,
-	and scale.
+Cloudflare Workers allows developers to build serverless applications and deploy instantly across the globe for exceptional performance, reliability, and scale. 
 </RelatedProduct>
 
 <RelatedProduct header="Logs" href="/logs/" product="logs">
-	Detailed logs that contain metadata generated by Cloudflare products helpful
-	for debugging, identifying configuration adjustments, and creating analytics.
+Detailed logs that contain metadata generated by Cloudflare products helpful for debugging, identifying configuration adjustments, and creating analytics. 
 </RelatedProduct>
diff --git a/src/content/docs/analytics/network-analytics/configure/index.mdx b/src/content/docs/analytics/network-analytics/configure/index.mdx
index 16e7bfa95e54afc..960840cbc5deb03 100644
--- a/src/content/docs/analytics/network-analytics/configure/index.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/network-analytics/configure/share-export.mdx b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
index 4f80063b389f3a8..ebfbca66506210a 100644
--- a/src/content/docs/analytics/network-analytics/configure/share-export.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
@@ -11,7 +11,7 @@ products:
   - analytics
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 ## Share Network Analytics filters
 
diff --git a/src/content/docs/analytics/network-analytics/configure/time-range.mdx b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
index 4cad33741de7676..f22f93aa5d6e373 100644
--- a/src/content/docs/analytics/network-analytics/configure/time-range.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
@@ -17,7 +17,7 @@ Use the timeframe drop-down list to change the time range over which Network Ana
 
 In the Network Analytics dashboard, the range of historical data you can query is 112 days.
 
-When you select _Previous 30 minutes_, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A _Live_ notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
+When you select *Previous 30 minutes*, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A *Live* notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
 
 ![Timeframe drop-down with Previous 30 minutes selected.](~/assets/images/analytics/network-analytics/timeframe-selector.png)
 
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
index 72d38cdbd6e45a7..e8908c5bbfc3b1e 100644
--- a/src/content/docs/analytics/network-analytics/index.mdx
+++ b/src/content/docs/analytics/network-analytics/index.mdx
@@ -12,7 +12,7 @@ products:
   - analytics
 ---
 
-import { InlineBadge, Render } from "~/components";
+import { InlineBadge, Render } from "~/components"
 
 Cloudflare Network Analytics (version 2) provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. Network Analytics visualizes packet and bit-level data, the same data available via the Network Analytics dataset of the GraphQL Analytics API.
 
@@ -22,12 +22,12 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
 
 ## Remarks
 
-- The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
+* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
 
-- The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
+* The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
 
 ## Related resources
 
-- [Cloudflare GraphQL API](/analytics/graphql-api/)
-- [Cloudflare Logpush](/logs/logpush/)
-- [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
+* [Cloudflare GraphQL API](/analytics/graphql-api/)
+* [Cloudflare Logpush](/logs/logpush/)
+* [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
\ No newline at end of file
diff --git a/src/content/docs/analytics/network-analytics/reference/index.mdx b/src/content/docs/analytics/network-analytics/reference/index.mdx
index 50a9131063634e7..bfaf9377cbe9497 100644
--- a/src/content/docs/analytics/network-analytics/reference/index.mdx
+++ b/src/content/docs/analytics/network-analytics/reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review reference information about Cloudflare Network Analytics:
 
diff --git a/src/content/docs/analytics/network-analytics/understand/index.mdx b/src/content/docs/analytics/network-analytics/understand/index.mdx
index 6bbfaed1b7957b3..364ff4458dc64da 100644
--- a/src/content/docs/analytics/network-analytics/understand/index.mdx
+++ b/src/content/docs/analytics/network-analytics/understand/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/sampling.mdx b/src/content/docs/analytics/sampling.mdx
index 964b7405a3d5f1a..815514bf77937e5 100644
--- a/src/content/docs/analytics/sampling.mdx
+++ b/src/content/docs/analytics/sampling.mdx
@@ -8,7 +8,7 @@ products:
   - analytics
 ---
 
-[Sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
+[Sampling](https://en.wikipedia.org/wiki/Sampling_(statistics)) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
 
 ## How sampling works
 
@@ -20,17 +20,17 @@ To make this possible, data is stored at multiple resolutions (100%, 10%, 1%), e
 
 Cloudflare's data pipeline handles [over 700 million events per second](https://blog.cloudflare.com/how-we-make-sense-of-too-much-data) (and growing) across its global network. Processing and storing all this data in real-time would be prohibitively expensive and time-consuming. By leveraging carefully designed sampling methods, Cloudflare Analytics delivers accurate and actionable data, balancing precision with performance.
 
-Sampling enables:
+Sampling enables: 
 
 - **Scalability**: Reduces the volume of data processed without compromising insights.
 - **Performance**: Speeds up query execution for analytics.
 - **Cost-Efficiency**: Minimizes resource usage and storage needs.
 
-## Can I trust sampled data?
+## Can I trust sampled data? 
 
 Sampled data is highly reliable, and can provide insights that are as dependable as those derived from full datasets. Cloudflare designs sampling techniques to ensure we capture the essential characteristics of the entire dataset, delivering results you can trust.
 
-Sampling is an approach similarly used in other domains, for instance:
+Sampling is an approach similarly used in other domains, for instance: 
 
 - Google Maps: Just as online maps display lower-resolution images when zoomed out and higher-resolution images when zoomed in — keeping the total number of pixels relatively constant — Cloudflare Analytics dynamically adjusts sampling rates to efficiently provide insights, ensuring queries return consistent and accurate results regardless of dataset size.
 
@@ -44,26 +44,23 @@ In the near future, we plan to expose confidence intervals along with query resu
 
 ## Additional considerations
 
-**When sampling occurs**
-
+**When sampling occurs** 
 - Sampling is typically applied to very high-traffic datasets where full data analysis would be impractical.
 - For smaller datasets, full data analysis is often performed without sampling.
 
-**Sampling rates**
-
+**Sampling rates** 
 - Sampling rates vary depending on the dataset and product.
 - Cloudflare ensures that sampling rates are consistent within a single dataset to maintain accuracy across queries.
 
-**Impact on metrics**
-
+**Impact on metrics** 
 - While sampling reduces the volume of processed data, aggregated metrics like totals, averages, and percentiles are extrapolated based on the sample size. This ensures the reported metrics represent the entire dataset accurately.
 
 **Limitations**
-
-- Sampling may not capture extremely rare events with very low occurrence rates.
+- Sampling may not capture extremely rare events with very low occurrence rates. 
 
 **Sampling in analytics interfaces**
-
 - GraphQL API: Sampling metadata is included in the query response. For more information, refer to the sampling [GraphQL Analytics API](/analytics/graphql-api/sampling/) documentation.
 - Workers Analytics Engine: For more information, refer to the [Workers Analytics Engine](/analytics/analytics-engine/sampling/) documentation.
 - Dashboard Analytics: Displays an icon with the sampled percentage of data, if sampled data was used for the visualization.
+
+
diff --git a/src/content/docs/analytics/types-of-analytics.mdx b/src/content/docs/analytics/types-of-analytics.mdx
index 9b13d4d6e16b1d5..3754f8a0ce803d1 100644
--- a/src/content/docs/analytics/types-of-analytics.mdx
+++ b/src/content/docs/analytics/types-of-analytics.mdx
@@ -40,24 +40,25 @@ Access aggregated traffic, security, and performance metrics for each domain pro
 
 Data available under the **Analytics & Logs** section includes:
 
-- **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
-- **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
-- **Performance** - Origin Performance, Bandwidth Saved.
-- **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
-- **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
-- **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
-- **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
+* **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
+* **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
+* **Performance** - Origin Performance, Bandwidth Saved.
+* **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
+* **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
+* **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
+* **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
 
 ## Product analytics
 
 Beyond the analytics provided for your properties, you can also access analytics related to specific products:
 
-- [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
-- [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
-- [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
-- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
-- [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
-- [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
+* [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
+* [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
+* [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
+* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
+* [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
+* [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
+
 
 ## GraphQL APIs
 
diff --git a/src/content/docs/api-shield/api-gateway.mdx b/src/content/docs/api-shield/api-gateway.mdx
index 159a13ee168f6ba..7eb6722be62e2c5 100644
--- a/src/content/docs/api-shield/api-gateway.mdx
+++ b/src/content/docs/api-shield/api-gateway.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 7
+
 ---
 
 Cloudflare API Shield provides API security, management tools, and integration with the Cloudflare Developer Platform for building new APIs.
diff --git a/src/content/docs/api-shield/glossary.mdx b/src/content/docs/api-shield/glossary.mdx
index 8cec6bbf2bf209c..f3d2e75924932cd 100644
--- a/src/content/docs/api-shield/glossary.mdx
+++ b/src/content/docs/api-shield/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 9
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's API Shield documentation.
 
diff --git a/src/content/docs/api-shield/index.mdx b/src/content/docs/api-shield/index.mdx
index f95940e11bfbf9e..17d437901096fc5 100644
--- a/src/content/docs/api-shield/index.mdx
+++ b/src/content/docs/api-shield/index.mdx
@@ -11,15 +11,11 @@ head:
     content: Overview
 ---
 
-import {
-	Description,
-	Feature,
-	Plan,
-	RelatedProduct,
-	Render,
-} from "~/components";
+import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
 
-<Description>Identify and address your API vulnerabilities.</Description>
+<Description>
+Identify and address your API vulnerabilities.
+</Description>
 
 <Plan type="ent-add-on" />
 
@@ -41,14 +37,11 @@ Refer to the [Get started](/api-shield/get-started/) guide to set up API Shield.
 ## Features
 
 <Feature header="Security features" href="/api-shield/security/">
-	Secure your APIs using API Shield's security features.
+Secure your APIs using API Shield's security features.
 </Feature>
 
-<Feature
-	header="Management, monitoring, and more"
-	href="/api-shield/management-and-monitoring/"
->
-	Monitor the health of your API endpoints.
+<Feature header="Management, monitoring, and more" href="/api-shield/management-and-monitoring/">
+Monitor the health of your API endpoints.
 </Feature>
 
 ## Availability
@@ -63,11 +56,6 @@ API Shield currently does not work for JDCloud customers.
 
 ## Related products
 
-<RelatedProduct
-	header="DDoS Protection"
-	href="/ddos-protection/"
-	product="ddos-protection"
->
-	Cloudflare DDoS protection secures websites, applications, and entire networks
-	while ensuring the performance of legitimate traffic is not compromised.
+<RelatedProduct header="DDoS Protection" href="/ddos-protection/" product="ddos-protection">
+Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised.
 </RelatedProduct>
diff --git a/src/content/docs/api-shield/management-and-monitoring/index.mdx b/src/content/docs/api-shield/management-and-monitoring/index.mdx
index 166b939d9e38c8e..182cc0cab64e27c 100644
--- a/src/content/docs/api-shield/management-and-monitoring/index.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/index.mdx
@@ -6,10 +6,11 @@ products:
   - api-shield
 sidebar:
   order: 5
-  group:
+  group: 
     hideIndex: true
+
 ---
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
index 34134ffed50f975..7139806c6c0866c 100644
--- a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
@@ -6,14 +6,14 @@ products:
 title: Session identifiers
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="session-identifiers" product="api-shield" />
 
 :::note
-
 <Render file="required-session-identifiers" product="api-shield" />
 :::
 
diff --git a/src/content/docs/api-shield/plans.mdx b/src/content/docs/api-shield/plans.mdx
index e54a67a1da3c703..7cba5403983b3bc 100644
--- a/src/content/docs/api-shield/plans.mdx
+++ b/src/content/docs/api-shield/plans.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 3
+
 ---
 
 Free, Pro, Business, and Enterprise customers without an API Shield subscription can access [Endpoint Management](/api-shield/management-and-monitoring/) and [Schema validation](/api-shield/security/schema-validation/), but no other [API Shield](/api-shield/) features.
@@ -14,10 +15,10 @@ To subscribe to API Shield, upgrade to an Enterprise plan and contact your accou
 
 Limits to endpoints apply to Endpoint Management and Schema validation. Refer to the table below for limits based on your zone plan.
 
-| Plan type                         | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action      |
-| --------------------------------- | --------------- | ---------------- | -------------------------- | ---------------- |
-| **Free**                          | 100             | 5                | 200 kB                     | `Block` only     |
-| **Pro**                           | 250             | 5                | 500 kB                     | `Block` only     |
-| **Business**                      | 500             | 10               | 2 MB                       | `Block` only     |
-| **Enterprise without API Shield** | 500             | 10               | 5 MB                       | `Log` or `Block` |
-| **Enterprise with API Shield**    | 10,000          | 10+              | 10+ MB                     | `Log` or `Block` |
+| Plan type | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action |
+| --- | --- | --- | --- | --- |
+| **Free** | 100 | 5 | 200 kB | `Block` only |
+| **Pro** | 250 | 5 | 500 kB | `Block` only |
+| **Business** | 500 | 10 | 2 MB | `Block` only |
+| **Enterprise without API Shield** | 500 | 10 | 5 MB | `Log` or `Block` |
+| **Enterprise with API Shield** | 10,000 | 10+ | 10+ MB | `Log` or `Block` |
\ No newline at end of file
diff --git a/src/content/docs/api-shield/reference/classic-schema-validation.mdx b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
index 4fefbda61645691..7e5925a84e6068a 100644
--- a/src/content/docs/api-shield/reference/classic-schema-validation.mdx
+++ b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
@@ -12,9 +12,10 @@ sidebar:
     text: Deprecated
   order: 1
   label: Classic Schema validation
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 :::caution[Deprecation notice]
 Classic Schema validation has been deprecated.
@@ -40,11 +41,14 @@ To configure Schema validation in the Cloudflare dashboard:
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Select **Security** > **API Shield**.
 3. Go to **Schema validation** and select **Add schema**.
-4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the _Hostname_ field — equal to `api.example.com` — and a check for the _URI Path_ field using a regular expression — matching the regex `^/v1`.
-   :::caution[Important]
+4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the *Hostname* field — equal to `api.example.com` — and a check for the *URI Path* field using a regular expression — matching the regex `^/v1`.
+:::caution[Important]
 
-To validate the hostname, you must include the _Hostname_ field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
-::: 5. Select **Next**. 6. Upload your schema file. 7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
+To validate the hostname, you must include the *Hostname* field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
+:::
+5. Select **Next**.
+6. Upload your schema file.
+7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
 
 After deploying your API Shield rule, Cloudflare displays a summary of all <GlossaryTooltip term="API endpoint">API endpoints</GlossaryTooltip> organized by their protection level and actions that will occur for non-compliant and unprotected requests.
 
diff --git a/src/content/docs/api-shield/reference/index.mdx b/src/content/docs/api-shield/reference/index.mdx
index e0fb94f82c8316e..d51edc253455ed3 100644
--- a/src/content/docs/api-shield/reference/index.mdx
+++ b/src/content/docs/api-shield/reference/index.mdx
@@ -6,11 +6,12 @@ products:
   - api-shield
 sidebar:
   order: 6
-  group:
+  group: 
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about API Shield:
 
diff --git a/src/content/docs/api-shield/reference/terraform.mdx b/src/content/docs/api-shield/reference/terraform.mdx
index 8e5c5b8d6c3be74..823b0b64274405a 100644
--- a/src/content/docs/api-shield/reference/terraform.mdx
+++ b/src/content/docs/api-shield/reference/terraform.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 tags:
   - Terraform
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Get started with API Shield using Terraform from the examples below. For more information on how to use Terraform with Cloudflare, refer to the [Terraform documentation](/terraform/).
 
@@ -61,7 +62,7 @@ resource "cloudflare_api_shield_operation" "get_image" {
   host     = "example.com"
   endpoint = "/api/images/{var1}"
 }
-
+ 
 resource "cloudflare_api_shield_operation" "post_image" {
   zone_id  = var.zone_id
   method   = "POST"
@@ -74,7 +75,7 @@ resource "cloudflare_api_shield_operation" "post_image" {
 
 :::note
 
-It is required to configure Endpoint Management if you want to set up Schema validation using Terraform.
+It is required to configure Endpoint Management if you want to set up Schema validation using Terraform. 
 :::
 
 Refer to the example configuration below to manage [Schema validation](/api-shield/security/schema-validation/api/) on your zone.
@@ -89,13 +90,13 @@ resource "cloudflare_schema_validation_schemas" "example_schema" {
   source             = file("./schemas/example-schema.yaml")
   validation_enabled = true
 }
-
+ 
 # Block all requests that violate schema by default
 resource "cloudflare_schema_validation_settings" "zone_level_settings" {
   zone_id                              = var.zone_id
   validation_default_mitigation_action = "block"
 }
-
+ 
 # For endpoint post_image - only log requests that violate schema
 resource "cloudflare_schema_validation_operation_settings" "post_image_log_only" {
   zone_id           = var.zone_id
diff --git a/src/content/docs/api-shield/security/graphql-protection/index.mdx b/src/content/docs/api-shield/security/graphql-protection/index.mdx
index 6d8f7feb449ca0d..c8c4dfc16b03dd8 100644
--- a/src/content/docs/api-shield/security/graphql-protection/index.mdx
+++ b/src/content/docs/api-shield/security/graphql-protection/index.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 5
+
 ---
 
 GraphQL is a query language for APIs. In addition to protecting RESTful APIs, Cloudflare can also protect GraphQL APIs.
diff --git a/src/content/docs/api-shield/security/index.mdx b/src/content/docs/api-shield/security/index.mdx
index 63dde51928c06d0..36a3a3e4120f463 100644
--- a/src/content/docs/api-shield/security/index.mdx
+++ b/src/content/docs/api-shield/security/index.mdx
@@ -6,19 +6,22 @@ products:
   - api-shield
 sidebar:
   order: 4
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
+
 
 Cloudflare offers the following features to help secure your APIs:
 
-| Discovery & management                                                                        | Posture management                                                                 | Runtime protection                                                   |
-| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
-| [API Discovery](/api-shield/security/api-discovery/)                                          | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/)     | [Schema validation](/api-shield/security/schema-validation/)         |
-| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/)             | [JWT validation](/api-shield/security/jwt-validation/)               |
-| [Sequence Analytics](/api-shield/security/sequence-analytics/)                                | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/)     |
-|                                                                                               | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels)  | [Mutual TLS (mTLS)](/api-shield/security/mtls/)                      |
-|                                                                                               | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/)               | [GraphQL query protection](/api-shield/security/graphql-protection/) |
+| Discovery & management | Posture management | Runtime protection |
+| --- | --- | --- |
+| [API Discovery](/api-shield/security/api-discovery/) | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/) | [Schema validation](/api-shield/security/schema-validation/) |
+| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/) | [JWT validation](/api-shield/security/jwt-validation/) |
+| [Sequence Analytics](/api-shield/security/sequence-analytics/) | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/) |
+| | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels) | [Mutual TLS (mTLS)](/api-shield/security/mtls/) |
+| | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) | [GraphQL query protection](/api-shield/security/graphql-protection/) |
+
 
 ## Example Cloudflare solutions
 
@@ -26,23 +29,29 @@ Cloudflare API Shield, together with other Cloudflare products, helps protect yo
 
 The following table maps each OWASP vulnerability to the Cloudflare features that address it:
 
-| OWASP issue                                     | Example Cloudflare solution                                                                                                                                                                                                             |
-| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| OWASP issue                                     | Example Cloudflare solution                                                                                                                            |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Broken Object Level Authorization               | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/), [Sequence mitigation], [Schema validation], [JWT validation], [Rate Limiting], [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) |
 | Broken Authentication                           | [Authentication Posture](/api-shield/security/authentication-posture/), [mTLS](/api-shield/security/mtls/), [JWT validation], [Exposed Credential Checks](/waf/managed-rules/check-for-exposed-credentials/), [Bot Management](/bots/)  |
-| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
-| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                    |
-| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
-| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                                     |
-| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                                                                                                        |
-| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                                                                                                             |
-| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                                                                                                    |
-| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                                                                                                   |
+| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                  |
+| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                   |
+| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                  |
+| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                    |
+| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                       |
+| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                            |
+| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                   |
+| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                  |
 
 [Schema validation]: /api-shield/security/schema-validation/
+
 [Sequence mitigation]: /api-shield/security/sequence-mitigation/
+
 [JWT validation]: /api-shield/security/jwt-validation/
+
 [GraphQL Query Protection]: /api-shield/security/graphql-protection/
+
 [Bot management]: /bots/
+
 [Rate limiting]: /waf/rate-limiting-rules/
+
 [WAF managed rules]: /waf/managed-rules/
diff --git a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
index e37fc920b98921f..412e2ee5573001d 100644
--- a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
@@ -14,7 +14,7 @@ tags:
   - JavaScript
 ---
 
-import { Steps } from "~/components";
+import { Steps } from "~/components"
 
 Use a Worker to automatically keep your identity provider’s latest public key in the JWT validation configuration.
 
diff --git a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
index 69906adc1b47b63..102b9af7bb9bb5e 100644
--- a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
@@ -13,7 +13,7 @@ tags:
   - JSON web token (JWT)
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 You can forward information from a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) to the origin in a header by creating [Transform Rules](/rules/transform/) using claims that Cloudflare has verified via the JSON Web Token.
 
@@ -44,4 +44,4 @@ As an example, to send the `x-send-jwt-claim-user` request header to the origin,
     lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
     ```
     `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT validation and `claim_name` is the JWT claim you want to add to the header.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/mtls/byo-ca.mdx b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
index 90b2c59cd2ff56e..2430485da76550a 100644
--- a/src/content/docs/api-shield/security/mtls/byo-ca.mdx
+++ b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/client-certificates/byo-ca/
 sidebar:
   order: 3
+
 ---
diff --git a/src/content/docs/api-shield/security/mtls/index.mdx b/src/content/docs/api-shield/security/mtls/index.mdx
index c7984dc34ab21f2..6652a44adef3c34 100644
--- a/src/content/docs/api-shield/security/mtls/index.mdx
+++ b/src/content/docs/api-shield/security/mtls/index.mdx
@@ -8,6 +8,7 @@ sidebar:
   order: 7
 tags:
   - mTLS
+
 ---
 
 import { GlossaryDefinition, Render } from "~/components";
diff --git a/src/content/docs/api-shield/security/sequence-analytics.mdx b/src/content/docs/api-shield/security/sequence-analytics.mdx
index c70bf1c1ef13f37..34a24e55bdceb85 100644
--- a/src/content/docs/api-shield/security/sequence-analytics.mdx
+++ b/src/content/docs/api-shield/security/sequence-analytics.mdx
@@ -6,9 +6,10 @@ products:
 title: Sequence Analytics
 sidebar:
   order: 3
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Sequence Analytics tracks the order of API endpoint requests over time, allowing you to discover how users interact with your API. Sequence Analytics groups and highlights important user journeys (sequences) across your API. You can enforce preferred sequences using [Sequence mitigation](/api-shield/security/sequence-mitigation/).
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
index 33320b54ef171ed..c3bf0a409084cde 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
@@ -10,23 +10,24 @@ sidebar:
 head:
   - tag: title
     content: Configure sequence mitigation via the API
+
 ---
 
 Configuring sequence mitigation via the API consists of building a rule object by choosing the sequence and setting the type of rule and its action.
 
 ```json title="Example of a rule object"
 {
-	"id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
-	"title": "<RULE_TITLE>",
-	"kind": "allow",
-	"action": "block",
-	"sequence": [
-		"0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
-		"b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
-	],
-	"priority": 0,
-	"last_updated": "2023-07-24T12:06:51.796286Z",
-	"created_at": "2023-07-24T12:06:51.796286Z"
+    "id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
+    "title": "<RULE_TITLE>",
+    "kind": "allow",
+    "action": "block",
+    "sequence": [
+     "0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
+     "b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
+    ],
+    "priority": 0,
+    "last_updated": "2023-07-24T12:06:51.796286Z",
+    "created_at": "2023-07-24T12:06:51.796286Z"
 }
 ```
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
index 5d43aabef5e991b..08a2a8da0c12da5 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
@@ -7,14 +7,14 @@ products:
 sidebar:
   order: 4
   label: Custom rules
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
 
 These rules are similar to [cookie sequence rules](/bots/additional-configurations/sequence-rules/) but have a different set of prerequisites:
-
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.
 - Because they require session identifiers, they can only be used on traffic that can be clearly attributed to individual users through session identifiers (authenticated traffic).
 - Because Cloudflare stores the user state in memory and not in a cookie, a session's sequence lifetime is limited to 10 minutes.
@@ -25,7 +25,6 @@ Rules built using these custom rules are similar to the sequence rules that can
 ## Availability
 
 :::note
-
 <Render file="sequence-mitigation-availability" product="api-shield" />
 :::
 
@@ -42,30 +41,30 @@ Each saved endpoint will have an endpoint ID visible in its details page in Endp
 The visitor must wait more than 2 seconds after requesting endpoint `aaaaaaaa` before requesting endpoint `bbbbbbbb`:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and
+cf.sequence.current_op eq "bbbbbbbb" and 
 cf.sequence.msec_since_op["aaaaaaaa"] ge 2000
 ```
 
 The visitor must request endpoints `aaaaaaaa`, then `bbbbbbbb`, then `cccccccc` in that exact order:
 
 ```txt
-cf.sequence.current_op eq "cccccccc" and
-cf.sequence.previous_ops[0] == "bbbbbbbb" and
+cf.sequence.current_op eq "cccccccc" and 
+cf.sequence.previous_ops[0] == "bbbbbbbb" and 
 cf.sequence.previous_ops[1] == "aaaaaaaa"
 ```
 
 The visitor must request endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, but endpoint `aaaaaaaa` can be anywhere in the previous 10 requests:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and
+cf.sequence.current_op eq "bbbbbbbb" and 
 any(cf.sequence.previous_ops[*] == "aaaaaaaa")
 ```
 
 The visitor must request either endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, or endpoint `cccccccc` before endpoint `bbbbbbbb`:
 
 ```txt
-(cf.sequence.current_op eq "bbbbbbbb" and
-any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or
-(cf.sequence.current_op eq "bbbbbbbb" and
+(cf.sequence.current_op eq "bbbbbbbb" and 
+any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or 
+(cf.sequence.current_op eq "bbbbbbbb" and 
 any(cf.sequence.previous_ops[*] == "cccccccc"))
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
index 7672a8fafa6039f..184e0fe3410c88c 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 4
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 Sequence mitigation allows you to enforce request patterns for authenticated clients communicating with your API.
 
@@ -29,7 +30,7 @@ Using sequence mitigation, you can enforce that request pattern with two new seq
 
 :::note
 
-You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/).
+You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/). 
 :::
 
 ## Process
@@ -53,6 +54,7 @@ A negative security model may be useful if you see abusive behavior that is outs
 
 For example, if there was an authorization bug that allowed users to iterate through other users' profiles that contain account numbers via `GET /api/v1/users/{var1}/profile` and then a user tries to make fraudulent funds transfers, you could create a rule to block or log the sequence `GET /api/v1/users/{var1}/profile` to `POST /api/v1/transferFunds`.
 
+
 ## Limitations
 
 ### Endpoint Management
@@ -85,4 +87,4 @@ For example, if you create a rule requiring one endpoint to be requested before
 
 ## Availability
 
-<Render file="sequence-mitigation-availability" product="api-shield" />
+<Render file="sequence-mitigation-availability" product="api-shield" />
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
index 4b6e8f08729bae2..ac20b0d38774fb5 100644
--- a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
+++ b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
@@ -6,9 +6,10 @@ products:
 title: Volumetric Abuse Detection
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components";
+import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components"
 
 Cloudflare Volumetric Abuse Detection generates per-endpoint, per-session rate limit recommendations that adjust automatically as your traffic patterns change.
 
@@ -26,7 +27,7 @@ Volumetric Abuse Detection rate limits are a way to prevent blatant volumetric a
 
 Volumetric Abuse Detection analyzes your API's individual session traffic statistics to recommend per-endpoint, per-session rate limits.
 
-To access your endpoints:
+To access your endpoints: 
 
 Old dashboard: **Security** > **API Shield** > **Endpoint Management**
 
@@ -46,7 +47,7 @@ Thresholds are suggested only for endpoints that satisfy all of the following re
 
 After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in the Cloudflare dashboard.
 
-### Rate limiting recommendation calculation
+### Rate limiting recommendation calculation 
 
 Select an endpoint row in **Endpoints** to view its rate limit recommendation. The detail view shows the overall recommended value and percentile-based values (p50, p90, p99).
 
@@ -72,8 +73,8 @@ Refer to the [Rules documentation](/waf/rate-limiting-rules/create-zone-dashboar
 [Rate limit recommendations are available via the API](/api/resources/api_gateway/subresources/operations/methods/get/) if you would like to dynamically update rate limits over time.
 
 <APIRequest
-	path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
-	method="GET"
+  path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
+  method="GET"
 />
 
 ## Special cases
diff --git a/src/content/docs/argo-smart-routing/analytics.mdx b/src/content/docs/argo-smart-routing/analytics.mdx
index 8ba08d6be3c3f77..73046eae32ef933 100644
--- a/src/content/docs/argo-smart-routing/analytics.mdx
+++ b/src/content/docs/argo-smart-routing/analytics.mdx
@@ -22,15 +22,18 @@ You can access Argo analytics for your domain in the [Cloudflare dashboard](http
 
 :::note
 
+
 Detailed performance data within **Origin Performance (Argo)** will only display if Argo has routed at least 500 origin requests within the last 48 hours.
 
+
 :::
 
 ## Types of analytics
 
 The dashboard displays two different views for performance data:
 
-- **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
+* **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
+
+* **Geography**: A map shows the improvement in response time at each Cloudflare data center.
 
-- **Geography**: A map shows the improvement in response time at each Cloudflare data center.
-  - A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
+  * A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
diff --git a/src/content/docs/argo-smart-routing/argo-for-packets.mdx b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
index b2e857fe5dca3da..8d4a1b15407b0ce 100644
--- a/src/content/docs/argo-smart-routing/argo-for-packets.mdx
+++ b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
@@ -6,6 +6,7 @@ products:
   - argo-smart-routing
 sidebar:
   order: 4
+
 ---
 
 Argo for Packets optimizes IP layer network routing for Cloudflare network services products, including [Magic Transit](/magic-transit/), [Cloudflare WAN](/cloudflare-wan/) (formerly Magic WAN), and [Cloudflare for Offices](https://blog.cloudflare.com/cloudflare-for-offices/).
diff --git a/src/content/docs/artifacts/api/errors.mdx b/src/content/docs/artifacts/api/errors.mdx
index 467365dbf5b37c7..7545813cd7cbfa2 100644
--- a/src/content/docs/artifacts/api/errors.mdx
+++ b/src/content/docs/artifacts/api/errors.mdx
@@ -15,17 +15,17 @@ This is a list of Artifacts errors.
 
 ## Error codes
 
-| Name                   | Code  | Description                                                               |
-| ---------------------- | ----- | ------------------------------------------------------------------------- |
-| `ALREADY_EXISTS`       | 10201 | The target repository already exists in the namespace.                    |
-| `NOT_FOUND`            | 10200 | The repository or remote resource does not exist.                         |
-| `IMPORT_IN_PROGRESS`   | 10302 | The repository is still being imported and is not yet available.          |
-| `FORK_IN_PROGRESS`     | 10303 | The repository is still being forked and is not yet available.            |
-| `INVALID_INPUT`        | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
-| `INVALID_REPO_NAME`    | 10101 | The repository name does not meet naming requirements.                    |
-| `INVALID_TTL`          | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds).       |
-| `INVALID_URL`          | 10104 | The source URL does not point to a valid git repository.                  |
-| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication.                            |
-| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached.                               |
-| `MEMORY_LIMIT`         | 10402 | The operation exceeds service memory limits.                              |
-| `INTERNAL_ERROR`       | 10400 | An unexpected internal error occurred.                                    |
+| Name | Code | Description |
+|------|------|-------------|
+| `ALREADY_EXISTS` | 10201 | The target repository already exists in the namespace. |
+| `NOT_FOUND` | 10200 | The repository or remote resource does not exist. |
+| `IMPORT_IN_PROGRESS` | 10302 | The repository is still being imported and is not yet available. |
+| `FORK_IN_PROGRESS` | 10303 | The repository is still being forked and is not yet available. |
+| `INVALID_INPUT` | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
+| `INVALID_REPO_NAME` | 10101 | The repository name does not meet naming requirements. |
+| `INVALID_TTL` | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds). |
+| `INVALID_URL` | 10104 | The source URL does not point to a valid git repository. |
+| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication. |
+| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached. |
+| `MEMORY_LIMIT` | 10402 | The operation exceeds service memory limits. |
+| `INTERNAL_ERROR` | 10400 | An unexpected internal error occurred. |
diff --git a/src/content/docs/artifacts/api/git-protocol.mdx b/src/content/docs/artifacts/api/git-protocol.mdx
index df3348a7a33e084..0b2fe497d2755c8 100644
--- a/src/content/docs/artifacts/api/git-protocol.mdx
+++ b/src/content/docs/artifacts/api/git-protocol.mdx
@@ -20,10 +20,10 @@ Use the returned repo `remote` with a regular Git client for `clone`, `fetch`, `
 
 Git routes accept repo access tokens in two forms:
 
-| Format                             | Details                                                                                                                              | Example                                                                                                      |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
+| Format                             | Details                                                                                                                               | Example                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
 | Bearer token in `http.extraHeader` | Recommended for local workflows. Use the full token string returned by the control plane and keep credentials out of the remote URL. | `git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone` |
-| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`                  |
+| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`               |
 
 ### Token format
 
diff --git a/src/content/docs/artifacts/concepts/repositories.mdx b/src/content/docs/artifacts/concepts/repositories.mdx
index c00cad8531dd358..026597faaae63d4 100644
--- a/src/content/docs/artifacts/concepts/repositories.mdx
+++ b/src/content/docs/artifacts/concepts/repositories.mdx
@@ -30,11 +30,11 @@ Each repository is isolated from other repositories. Tokens, lifecycle, refs, an
 
 Artifacts exposes the same repository through three interfaces:
 
-| Interface       | What you use it for                                                                | What it returns                                                        |
-| --------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker         | Repository metadata, repository handles, and repo-scoped token results |
-| REST API        | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results    |
-| Git protocol    | Clone, fetch, pull, and push repository contents                                   | Standard Git behavior over HTTPS                                       |
+| Interface | What you use it for | What it returns |
+| --- | --- | --- |
+| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker | Repository metadata, repository handles, and repo-scoped token results |
+| REST API | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results |
+| Git protocol | Clone, fetch, pull, and push repository contents | Standard Git behavior over HTTPS |
 
 These interfaces point to the same repository.
 
diff --git a/src/content/docs/artifacts/examples/git-client.mdx b/src/content/docs/artifacts/examples/git-client.mdx
index 10a023272838435..a297d94fb81bf26 100644
--- a/src/content/docs/artifacts/examples/git-client.mdx
+++ b/src/content/docs/artifacts/examples/git-client.mdx
@@ -11,11 +11,10 @@ products:
 You can use a standard Git client to interact with Artifacts repos. This example walks through clone, but the same approach works for fetch, pull, push, and any other Git operation.
 
 To do this, you need to:
-
 - Fetch the repo's remote URL from the REST API
 - Mint a short-lived token scoped to that repo
 
-Once you have the remote URL and token, you can use them to run Git commands against the repo.
+Once you have the remote URL and token, you can use them to run Git commands against the repo. 
 
 This example assumes the repo already exists and that you have a [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 
@@ -50,13 +49,11 @@ ARTIFACTS_TOKEN=$(printf '%s' "$TOKEN_JSON" | jq -r '.result.plaintext')
 # Clone the repo
 git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone
 ```
-
 You now have a standard Git checkout in `./artifacts-clone`.
 
 This flow is useful when another system owns repo discovery or access control, but your local tooling still expects a normal git remote.
 
 ### Authentication
-
 Treat `ARTIFACTS_TOKEN` as a secret. Keep it out of logs, and prefer `http.extraHeader` over saving credentials in a remote URL.
 
 If you need a self-contained remote URL for a short-lived workflow, extract the token secret and build the authenticated remote only for that command:
diff --git a/src/content/docs/artifacts/guides/authentication.mdx b/src/content/docs/artifacts/guides/authentication.mdx
index b700afb4e8e3481..ac4559e2184b237 100644
--- a/src/content/docs/artifacts/guides/authentication.mdx
+++ b/src/content/docs/artifacts/guides/authentication.mdx
@@ -16,11 +16,11 @@ Review [Namespaces](/artifacts/concepts/namespaces/) first, then use one namespa
 
 ## Compare auth methods
 
-| Interface       | Authenticate with                                   | Permissions or scopes                                                                   | Use for                                |
-| --------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------- |
-| Workers binding | Configured `artifacts` binding                      | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`.           | Worker code that calls `env.ARTIFACTS` |
-| REST API        | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests            |
-| Git protocol    | Repo-scoped Artifacts token                         | `read` for clone, fetch, and pull. `write` for push.                                    | Standard Git over HTTPS                |
+| Interface | Authenticate with | Permissions or scopes | Use for |
+| --- | --- | --- | --- |
+| Workers binding | Configured `artifacts` binding | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`. | Worker code that calls `env.ARTIFACTS` |
+| REST API | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests |
+| Git protocol | Repo-scoped Artifacts token | `read` for clone, fetch, and pull. `write` for push. | Standard Git over HTTPS |
 
 Cloudflare API tokens authenticate control-plane access. Repo-scoped Artifacts tokens authenticate Git access.
 
@@ -79,10 +79,10 @@ curl --request POST "$ARTIFACTS_BASE_URL/repos" \
 
 Git uses repo-scoped Artifacts tokens, not Cloudflare API tokens. Mint these tokens from the Workers binding or the REST API, then use them with the repo `remote` URL.
 
-| Token scope | Allowed commands                                 |
-| ----------- | ------------------------------------------------ |
-| `read`      | `git clone`, `git fetch`, `git pull`             |
-| `write`     | `git clone`, `git fetch`, `git pull`, `git push` |
+| Token scope | Allowed commands |
+| --- | --- |
+| `read` | `git clone`, `git fetch`, `git pull` |
+| `write` | `git clone`, `git fetch`, `git pull`, `git push` |
 
 Use the exact repo `remote` value returned by the Workers binding or REST API:
 
diff --git a/src/content/docs/artifacts/guides/event-subscriptions.mdx b/src/content/docs/artifacts/guides/event-subscriptions.mdx
index 08ff7f6771fca2b..8b1184706241f3d 100644
--- a/src/content/docs/artifacts/guides/event-subscriptions.mdx
+++ b/src/content/docs/artifacts/guides/event-subscriptions.mdx
@@ -13,7 +13,6 @@ import { Render } from "~/components";
 Artifacts emits structured events for repository lifecycle changes — creates, deletes, forks, imports, pushes, clones, fetches, and token changes. By subscribing to these events through [event subscriptions](/queues/event-subscriptions/), you can consume them from a Worker to build commit-driven automation.
 
 For example:
-
 - Run custom workflows when a repository is created or imported
 - Kick off a build and deploy a change when an agent pushes to a repo
 - Trigger a review agent on every push
diff --git a/src/content/docs/artifacts/platform/limits.mdx b/src/content/docs/artifacts/platform/limits.mdx
index b328482a34c0687..75154c57881d70c 100644
--- a/src/content/docs/artifacts/platform/limits.mdx
+++ b/src/content/docs/artifacts/platform/limits.mdx
@@ -15,9 +15,9 @@ These limits cover naming rules, storage, and request rates for control-plane an
 | Feature                        | Limit                                                                                              |
 | ------------------------------ | -------------------------------------------------------------------------------------------------- |
 | Control-plane request rate     | 2,000 requests per 10 seconds per Artifacts namespace                                              |
-| Git request rate, per artifact | 2,000 requests per 10 seconds per artifact                                                         |
+| Git request rate, per artifact     | 2,000 requests per 10 seconds per artifact                                                             |
 | Maximum storage per repository | 10 GB                                                                                              |
 | Maximum storage per account    | 1 TB (can be raised on request)                                                                    |
-| Maximum number of repositories | Unlimited                                                                                          |
+| Maximum number of repositories | Unlimited                                 |
 | Maximum number of namespaces   | Unlimited                                                                                          |
 | Namespace and repo names       | Start with a letter or digit. Remaining characters may include letters, digits, `.`, `_`, and `-`. |
diff --git a/src/content/docs/artifacts/platform/pricing.mdx b/src/content/docs/artifacts/platform/pricing.mdx
index 6986d8c6160294c..8cca99c4745119f 100644
--- a/src/content/docs/artifacts/platform/pricing.mdx
+++ b/src/content/docs/artifacts/platform/pricing.mdx
@@ -15,10 +15,10 @@ Artifacts pricing is billed on two dimensions:
 
 ## Artifacts pricing
 
-| Unit                          | Workers Free | Workers Paid                                                   |
-| ----------------------------- | ------------ | -------------------------------------------------------------- |
-| Operations (1,000 operations) | Unavailable  | First 10,000 per month + $0.15 per additional 1,000 operations |
-| Storage (GB-mo)               | Unavailable  | First 1 GB per month + $0.50 per additional GB-mo              |
+| Unit                          | Workers Free | Workers Paid |
+| ----------------------------- | ------------ | ------------ |
+| Operations (1,000 operations) | Unavailable | First 10,000 per month + $0.15 per additional 1,000 operations |
+| Storage (GB-mo)               | Unavailable | First 1 GB per month + $0.50 per additional GB-mo |
 
 ## Storage usage
 
diff --git a/src/content/docs/automatic-platform-optimization/about/index.mdx b/src/content/docs/automatic-platform-optimization/about/index.mdx
index 8e08942f6c504ec..8a627ee1adac90b 100644
--- a/src/content/docs/automatic-platform-optimization/about/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/index.mdx
@@ -6,6 +6,7 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 2
+
 ---
 
 With Automatic Platform Optimization (APO), Cloudflare serves your entire site from our edge network, ensuring customers see improved performance when visiting your site. Cloudflare typically only caches static content, but with APO, we can also cache dynamic content — like HTML — to serve the entire site from the cache. This process removes round trips from the origin to drastically improve time to first byte (TTFB) along with other site performance metrics. In addition to caching dynamic content, APO caches third-party scripts to further reduce the number of requests that leave Cloudflare's edge network.
diff --git a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
index c63c3dc4fdccb0f..3b36da43020bcd5 100644
--- a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
@@ -16,33 +16,35 @@ For questions about a specific plugin not shown in the list, create a thread in
 
 :::note
 
+
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
+
 :::
 
 ## Compatible plugins
 
-- [NitroPack](https://nitropack.io/)
-- [FlyingPress](https://flyingpress.com/)
-- [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
-- [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
-- [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
-- [WooCommerce](https://wordpress.org/plugins/woocommerce/)
-- [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
-- [Object Cache Pro](https://objectcache.pro)
-- [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
-- [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
-- [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
-- [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
-- [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
-- [WPTouch](https://wordpress.org/plugins/wptouch/)
-- [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
-- [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
-- [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
-- [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
-- [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
-- [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
-- [WPML](https://wpml.org/)
-- [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
-- [Imunify360](https://docs.imunify360.com/features/#webshield)
-- [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
+* [NitroPack](https://nitropack.io/)
+* [FlyingPress](https://flyingpress.com/)
+* [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
+* [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
+* [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
+* [WooCommerce](https://wordpress.org/plugins/woocommerce/)
+* [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
+* [Object Cache Pro](https://objectcache.pro)
+* [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
+* [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
+* [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
+* [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
+* [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
+* [WPTouch](https://wordpress.org/plugins/wptouch/)
+* [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
+* [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
+* [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
+* [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
+* [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
+* [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
+* [WPML](https://wpml.org/)
+* [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
+* [Imunify360](https://docs.imunify360.com/features/#webshield)
+* [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
diff --git a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
index e4df722b4bb5ebb..05c85a5ea866629 100644
--- a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
@@ -6,6 +6,7 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 3
+
 ---
 
 Before you begin using APO, we recommend testing your current site speed. Your site speed results give your website a letter grade and performance rating.
diff --git a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
index 422ecb4f5989b1b..e2ba71bfc3a0ea6 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
@@ -33,6 +33,8 @@ We recommend keeping this browser tab or window open and opening a new tab or wi
 
 :::note
 
+
 You may be prompted to confirm the nameserver change with your domain registrar. Confirm or continue after making the update.
 
+
 :::
diff --git a/src/content/docs/automatic-platform-optimization/get-started/index.mdx b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
index 1ec49c17ce68232..27e95e4ce57100a 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with APO
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Before you configure APO for your WordPress site, complete the following tasks.
 
diff --git a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
index 710c8af46eb1aa8..a8148c2c7bbb2e6 100644
--- a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
@@ -12,9 +12,9 @@ sidebar:
 
 APO cache by device type provides all of the same benefits of Cloudflare's cache while targeting visitors with content appropriate to their device. Cloudflare evaluates the `User-Agent` header in the HTTP request to identify the device type. Cloudflare then identifies each device type with a case insensitive match to the regex below:
 
-- **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
-- **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
-- **Desktop**: Everything else not matched above.
+* **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
+* **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
+* **Desktop**: Everything else not matched above.
 
 To enable caching by device type, enable the setting from the Cloudflare dashboard's APO card or from the WordPress plugin version 4.4.0 or later.
 
@@ -22,8 +22,10 @@ Once enabled, Cloudflare sends a `CF-Device-Type` HTTP header to your origin wit
 
 :::note
 
+
 Changing Cache By Device Type setting will invalidate Cache.
 
+
 :::
 
 The Cloudflare for WordPress plugin automatically purges all cache variations for updated pages.
diff --git a/src/content/docs/automatic-platform-optimization/reference/index.mdx b/src/content/docs/automatic-platform-optimization/reference/index.mdx
index 14a92784439d41f..d3e472301ede3ee 100644
--- a/src/content/docs/automatic-platform-optimization/reference/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/index.mdx
@@ -6,8 +6,9 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 10
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
index c1f33213a954200..80a3a268e1f1395 100644
--- a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
@@ -6,20 +6,21 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 12
+
 ---
 
 The following Page Rules can control APO. Any changes to caching via Page Rules require purging the cache for the changes to take effect.
 
 :::caution
 
-Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability.
+Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability. 
 :::
 
-- **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
+* **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
 
-- **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
+* **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
 
-- **Cache Level: Cache Everything** — APO caches pages with all query strings.
+* **Cache Level: Cache Everything** — APO caches pages with all query strings.
 
   :::caution
 
@@ -27,10 +28,10 @@ Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO
 
   :::
 
-- **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
+* **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
 
-- **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
+* **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
 
-- **Browser Cache TTL** — APO applies custom Browser TTL.
+* **Browser Cache TTL** — APO applies custom Browser TTL.
 
-- `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
+* `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
diff --git a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
index 4c26f989a9835bb..d49a44137e07c34 100644
--- a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
@@ -16,46 +16,46 @@ To add a query parameter to our allowlist, [create a post in the community](http
 
 APO serves cached content as long as the query parameters in the URL are one of the following:
 
-- `ref`
-- `utm_source`
-- `utm_medium`
-- `utm_campaign`
-- `utm_term`
-- `utm_content`
-- `utm_expid`
-- `fbclid`
-- `fb_action_ids`
-- `fb_action_types`
-- `fb_source`
-- `mc_cid`
-- `mc_eid`
-- `gclid`
-- `dclid`
-- `_ga`
-- `campaignid`
-- `adgroupid`
-- `_ke`
-- `cn-reloaded`
-- `age-verified`
-- `ao_noptimize`
-- `usqp`
-- `mkt_tok`
-- `epik`
-- `ck_subscriber_id`
+* `ref`
+* `utm_source`
+* `utm_medium`
+* `utm_campaign`
+* `utm_term`
+* `utm_content`
+* `utm_expid`
+* `fbclid`
+* `fb_action_ids`
+* `fb_action_types`
+* `fb_source`
+* `mc_cid`
+* `mc_eid`
+* `gclid`
+* `dclid`
+* `_ga`
+* `campaignid`
+* `adgroupid`
+* `_ke`
+* `cn-reloaded`
+* `age-verified`
+* `ao_noptimize`
+* `usqp`
+* `mkt_tok`
+* `epik`
+* `ck_subscriber_id`
 
 ## Cookies prefixes that always bypass cache
 
-- `wp-`
-- `wordpress`
-- `comment_`
-- `woocommerce_`
-- `xf_`
-- `edd_`
-- `jetpack`
-- `yith_wcwl_session_`
-- `yith_wrvp_`
-- `wpsc_`
-- `ecwid`
-- `ec_`
-- `bookly_`
-- `bookly`
+* `wp-`
+* `wordpress`
+* `comment_`
+* `woocommerce_`
+* `xf_`
+* `edd_`
+* `jetpack`
+* `yith_wcwl_session_`
+* `yith_wrvp_`
+* `wpsc_`
+* `ecwid`
+* `ec_`
+* `bookly_`
+* `bookly`
diff --git a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
index c14b25e62e38c9f..c3ac27a754ccf4a 100644
--- a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
@@ -46,10 +46,10 @@ export default {
 		const originalResponse = await fetch(request);
 
 		// Response properties are immutable. To change them, construct a new Response object.
-		const response = new Response(originalResponse.body, originalResponse);
+    const response = new Response(originalResponse.body, originalResponse);
 
-		// Response headers can be modified through the headers `set` method.
-		response.headers.set("cf-edge-cache", "no-cache");
+    // Response headers can be modified through the headers `set` method.
+    response.headers.set("cf-edge-cache", "no-cache");
 
 		return response;
 	},
diff --git a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
index f680125ba5c4689..4f41ab6c0987264 100644
--- a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
@@ -6,25 +6,28 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 15
+
 ---
 
 ## WordPress plugin is undetected on Cloudflare dashboard
 
 The WordPress plugin may go undetected on your Cloudflare dashboard for a few reasons.
 
-- Versions older than 3.8.2 of the WordPress plugin are installed.
-  - **Solution:** Install version 4.4.0 of the WordPress plugin.
-- Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
-  - **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
-- WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
-  - **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
+* Versions older than 3.8.2 of the WordPress plugin are installed.
+  * **Solution:** Install version 4.4.0 of the WordPress plugin.
+* Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
+  * **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
+* WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
+  * **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
 
 If your Cloudflare dashboard cannot detect the WordPress plugin after trying the solutions above, ensure you completed all of the steps listed in [Activate the Cloudflare WordPress plugin](/automatic-platform-optimization/get-started/activate-cf-wp-plugin/).
 
 :::note
 
+
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
+
 :::
 
 ## WordPress returns stale content
diff --git a/src/content/docs/billing/get-started/create-billing-profile.mdx b/src/content/docs/billing/get-started/create-billing-profile.mdx
index 278be4c84fffc13..db1ff0eccc710d9 100644
--- a/src/content/docs/billing/get-started/create-billing-profile.mdx
+++ b/src/content/docs/billing/get-started/create-billing-profile.mdx
@@ -20,7 +20,7 @@ Customers on an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/co
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**. If no payment method is on file, the dialog opens automatically.
@@ -57,7 +57,7 @@ Optionally, add an additional payment method. Cloudflare automatically retries t
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**.
diff --git a/src/content/docs/billing/get-started/update-billing-info.mdx b/src/content/docs/billing/get-started/update-billing-info.mdx
index 14d3c82fae104fa..103bc694b8df894 100644
--- a/src/content/docs/billing/get-started/update-billing-info.mdx
+++ b/src/content/docs/billing/get-started/update-billing-info.mdx
@@ -20,7 +20,7 @@ If Cloudflare is unable to process your payment, review [Troubleshooting failed
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method** to add a new method, or **Edit** next to an existing one.
@@ -55,7 +55,7 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Delete** next to the payment method you want to remove.
@@ -65,9 +65,9 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 Two address fields exist on your account:
 
-| Field                              | Where it is used                                                                                                       |
-| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| **Billing profile address**        | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening.                             |
+| Field | Where it is used |
+| --- | --- |
+| **Billing profile address** | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening. |
 | **Payment method billing address** | Captured when you add a payment method. Used by the card issuer to authorize each charge. Does not appear on invoices. |
 
 Updating the billing profile address applies to invoices issued after the change. Past invoices keep the address that was on file when they were issued. Updating the billing profile address does not change the address stored on existing payment methods.
@@ -76,7 +76,7 @@ To update the billing profile address:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit** and enter your information.
 3. Review the suggested address in the pop-up window. If the information is correct, select **Confirm**.
@@ -91,7 +91,7 @@ Your billing email address is particularly important if you have [opted into ema
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to **Invoices and documents**.
 3. From **Billing email preference**, select **Change email address**.
@@ -101,13 +101,13 @@ Your billing email address is particularly important if you have [opted into ema
 
 If you added a payment method but did not include a Tax ID, VAT or GST number, you can add or change the Tax ID, VAT or GST number associated with the payment method afterwards.
 
-:::note
+:::note 
 You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, enter your VAT or GST number.
@@ -115,13 +115,13 @@ You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST numbe
 
 ## Remove a Tax ID, VAT, or GST number
 
-:::note
+:::note 
 You cannot remove a VAT or GST number from past invoices. Removing a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, delete the VAT or GST number.
diff --git a/src/content/docs/billing/manage/billable-usage.mdx b/src/content/docs/billing/manage/billable-usage.mdx
index 3136309de54ce9b..936144271be0638 100644
--- a/src/content/docs/billing/manage/billable-usage.mdx
+++ b/src/content/docs/billing/manage/billable-usage.mdx
@@ -40,12 +40,12 @@ Hover over any bar to see the per-product cost breakdown for that day.
 
 Below the chart, a sortable table breaks down usage by product for the full billing period.
 
-| Column             | Description                                                                                                                                              |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Product**        | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
-| **Total usage**    | Total metered usage for the billing period, including any free-tier allowance.                                                                           |
-| **Billable usage** | Usage that exceeds the free tier and will be charged.                                                                                                    |
-| **Usage cost**     | Cumulative cost for the product in the selected billing period.                                                                                          |
+| Column | Description |
+| --- | --- |
+| **Product** | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
+| **Total usage** | Total metered usage for the billing period, including any free-tier allowance. |
+| **Billable usage** | Usage that exceeds the free tier and will be charged. |
+| **Usage cost** | Cumulative cost for the product in the selected billing period. |
 
 Use the **product filter** at the top of the page to narrow the chart and table to specific products.
 
@@ -62,6 +62,8 @@ The dashboard reads from the same data source that generates your monthly invoic
 - Costs reflect the published rate card for your account.
 - The total usage cost shown at the end of a completed billing period matches the usage overage charges on the corresponding invoice.
 
+
+
 ## Set up budget alerts
 
 To get notified when your spend crosses a dollar threshold, you can create budget alerts directly from the dashboard. For detailed instructions, refer to [Budget alerts](/billing/manage/budget-alerts/).
@@ -71,3 +73,4 @@ To get notified when your spend crosses a dollar threshold, you can create budge
 - [Budget alerts](/billing/manage/budget-alerts/) — Get notified when spend crosses a threshold
 - [Usage-based billing](/billing/understand/usage-based-billing/) — Which products use metered billing
 - [How charges accrue](/billing/understand/how-charges-accrue/) — How a request generates charges across products
+
diff --git a/src/content/docs/billing/manage/budget-alerts.mdx b/src/content/docs/billing/manage/budget-alerts.mdx
index c5cf2ff7f15fc1c..0fb4fdd9330e059 100644
--- a/src/content/docs/billing/manage/budget-alerts.mdx
+++ b/src/content/docs/billing/manage/budget-alerts.mdx
@@ -28,12 +28,12 @@ Budget alerts are available to Pay-as-you-go accounts only. Enterprise contract
 5. Select **Create budget alert**.
 6. Configure the alert:
 
-   | Field                      | Description                                                                                                                                                           |
-   | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-   | **Alert name**             | A descriptive name for the alert (for example, "R2 spend warning").                                                                                                   |
-   | **Description**            | _(Optional)_ A note about when this alert should fire.                                                                                                                |
+   | Field | Description |
+   | --- | --- |
+   | **Alert name** | A descriptive name for the alert (for example, "R2 spend warning"). |
+   | **Description** | *(Optional)* A note about when this alert should fire. |
    | **Budget threshold (USD)** | The dollar amount that triggers the alert. When your cumulative usage-based spend for the current billing period crosses this value, Cloudflare sends a notification. |
-   | **Email recipients**       | One or more email addresses to notify. Select **Add email** to add additional recipients.                                                                             |
+   | **Email recipients** | One or more email addresses to notify. Select **Add email** to add additional recipients. |
 
 7. Select **Save**.
 
@@ -54,12 +54,12 @@ From there you can edit or delete existing alerts.
 
 Cloudflare offers two types of spend monitoring:
 
-| Feature            | Budget alerts                                   | Usage notifications                                       |
-| ------------------ | ----------------------------------------------- | --------------------------------------------------------- |
-| **Scope**          | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
-| **Threshold**      | Dollar amount                                   | Product-specific metric (bytes, requests, minutes)        |
-| **Setup location** | **Billing** > **Billable Usage**                | **Notifications**                                         |
-| **Best for**       | Overall cost management                         | Monitoring a single product                               |
+| Feature | Budget alerts | Usage notifications |
+| --- | --- | --- |
+| **Scope** | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
+| **Threshold** | Dollar amount | Product-specific metric (bytes, requests, minutes) |
+| **Setup location** | **Billing** > **Billable Usage** | **Notifications** |
+| **Best for** | Overall cost management | Monitoring a single product |
 
 For per-product usage notifications, refer to [Usage-based billing](/billing/understand/usage-based-billing/#usage-based-billing-notifications).
 
diff --git a/src/content/docs/billing/manage/cancel-subscription.mdx b/src/content/docs/billing/manage/cancel-subscription.mdx
index 5fdf55b5596082d..c80dba8a8bcf6e3 100644
--- a/src/content/docs/billing/manage/cancel-subscription.mdx
+++ b/src/content/docs/billing/manage/cancel-subscription.mdx
@@ -32,17 +32,17 @@ To disable a subscription:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Select the feature you want to disable under **Active Subscriptions** (Free or Pro customers) or **Plan Extensions** (Enterprise customers).
-4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing _Disable_ from a drop-down list.
+4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing *Disable* from a drop-down list.
 
 ## Step 2: Cancel the subscription in your billing profile
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Find the subscription you want to disable and select **Cancel**.
diff --git a/src/content/docs/billing/manage/invoices.mdx b/src/content/docs/billing/manage/invoices.mdx
index 43d7879767a806f..ba940ef55e961bd 100644
--- a/src/content/docs/billing/manage/invoices.mdx
+++ b/src/content/docs/billing/manage/invoices.mdx
@@ -12,10 +12,10 @@ import { DashButton } from "~/components";
 
 You will receive an invoice in the **Billing** section of your Cloudflare account when you:
 
-- Change your Cloudflare plan type.
-- Upgrade or downgrade to or from a paid plan.
-- Add a new domain to a Cloudflare account.
-- Enable or renew a subscription or add-on service.
+* Change your Cloudflare plan type.
+* Upgrade or downgrade to or from a paid plan.
+* Add a new domain to a Cloudflare account.
+* Enable or renew a subscription or add-on service.
 
 For any historical invoices not included in the **Billing** section, [contact Cloudflare support](/support/contacting-cloudflare-support/).
 
@@ -29,25 +29,25 @@ To enable Cloudflare invoice emails which are sent when you add or remove subscr
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
-
-2. Select **Invoices & Documents**.
-3. From **Billing email preferences**, toggle the notification switch to **On**.
+    <DashButton url="/?to=/:account/billing" />
+    
+3. Select **Invoices & Documents**.
+4. From **Billing email preferences**, toggle the notification switch to **On**.
 
 After you enable email invoices, you will receive invoices via email:
 
-- Within one business day of initial set-up.
-- Every month at the end of your billing period.
-- Within one business day for all new purchases.
+* Within one business day of initial set-up.
+* Every month at the end of your billing period.
+* Within one business day for all new purchases.
 
 ## Download invoice
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices & Documents**.
-3. Find the invoice you want to download and select the icon next to the invoice number.
+4. Find the invoice you want to download and select the icon next to the invoice number.
 
 :::note
 Invoices cannot be regenerated after they are issued. Any pending billing updates or changes will appear in the next month's invoice.
diff --git a/src/content/docs/billing/manage/optimize-costs.mdx b/src/content/docs/billing/manage/optimize-costs.mdx
index f4d34d4f201f6a3..1ebb06ae5ce6d13 100644
--- a/src/content/docs/billing/manage/optimize-costs.mdx
+++ b/src/content/docs/billing/manage/optimize-costs.mdx
@@ -10,10 +10,10 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 ## General strategies
 
-| Strategy                                                                                              | Impact                                                      |
-| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early               | Prevents surprise invoices across all products              |
-| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives            |
+| Strategy | Impact |
+|---|---|
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | Prevents surprise invoices across all products |
+| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives |
 | Understand [how charges accrue](/billing/understand/how-charges-accrue/) across the request lifecycle | Identifies which stage of a request generates the most cost |
 
 ## Per-product optimization
@@ -22,42 +22,42 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 Cached responses are the cheapest path through Cloudflare. Every cache hit avoids origin fetch costs, Argo routing charges, and Workers execution.
 
-| Strategy                                                                                                              | What it reduces                                                              |
-| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                                     | Argo data transfer, Workers invocations, origin load                         |
+| Strategy | What it reduces |
+|---|---|
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
 | Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content that is accessed infrequently | Origin fetches — keeps content cached even when it would normally be evicted |
-| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls                                              | Origin bandwidth and Argo transfer between Cloudflare data centers           |
-| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default                           | Overall cache hit ratio                                                      |
+| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls | Origin bandwidth and Argo transfer between Cloudflare data centers |
+| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default | Overall cache hit ratio |
 
 ### Workers & Durable Objects
 
-| Strategy                                                                                                                                                                       | What it reduces                                                                 |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
-| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush                                                                             | Logpush-enabled Workers requests and Logpush data transfer                      |
+| Strategy | What it reduces |
+|---|---|
+| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush | Logpush-enabled Workers requests and Logpush data transfer |
 | Use the [WebSocket Hibernation API](/durable-objects/best-practices/websockets/#durable-objects-hibernation-websocket-api) for Durable Objects with idle WebSocket connections | Duration (GB-s) charges — billing pauses while the Durable Object is hibernated |
 
 ### R2
 
-| Strategy                                                                                                                | What it reduces                              |
-| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
-| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data              |
-| Batch R2 operations where possible instead of per-object reads                                                          | Class B operation count                      |
-| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers           | Workers invocations and CPU time             |
-| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache            | Class B reads — cached objects do not hit R2 |
+| Strategy | What it reduces |
+|---|---|
+| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data |
+| Batch R2 operations where possible instead of per-object reads | Class B operation count |
+| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers | Workers invocations and CPU time |
+| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache | Class B reads — cached objects do not hit R2 |
 
 ### Stream and Images
 
-| Strategy                                                                                                                           | What it reduces                                  |
-| ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
-| Set appropriate cache headers on Stream embed pages                                                                                | Repeated Stream delivery minutes                 |
+| Strategy | What it reduces |
+|---|---|
+| Set appropriate cache headers on Stream embed pages | Repeated Stream delivery minutes |
 | Use [Image Resizing URL format](/images/optimization/features/) with width/height parameters to serve appropriately sized variants | Transformation count — sized variants are cached |
 
 ### Load Balancing
 
-| Strategy                                                                                      | What it reduces                        |
-| --------------------------------------------------------------------------------------------- | -------------------------------------- |
+| Strategy | What it reduces |
+|---|---|
 | Set health check intervals to the longest acceptable value for your availability requirements | DNS queries to load-balanced hostnames |
-| Use fewer health check regions where regional redundancy is not critical                      | Health check frequency multiplier      |
+| Use fewer health check regions where regional redundancy is not critical | Health check frequency multiplier |
 
 ## Monitor and alert
 
diff --git a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
index e55450f95a43eb4..2b082f37ba9f84f 100644
--- a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
+++ b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
@@ -12,6 +12,7 @@ import { DashButton } from "~/components";
 
 If automatic payment retries fail and you do not pay manually, your account accrues an overdue balance. While the balance is unpaid, you cannot purchase products, upgrade subscriptions, or update your billing profile. Attempts to do so return an error:
 
+
 **"You cannot add or modify subscriptions or services until the outstanding balance is paid."**
 
 To pay, select **Pay Now** from the **Billing** page in the Cloudflare dashboard. You can pay the entire balance in one transaction or [pay individual invoices](#manually-pay-invoices) separately.
@@ -22,7 +23,7 @@ When an outstanding balance is due, a new invoice will be created in your accoun
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select the most recent invoice - the amount shown should match your outstanding balance
@@ -39,7 +40,7 @@ To pay the total outstanding balance:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Pay overdue balances** section.
 3. Select **Pay now** next to the balance you want to pay.
@@ -52,7 +53,7 @@ If an automatic subscription renewal payment fails, Cloudflare automatically ret
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select **Pay now** next to the invoice you want to pay.
diff --git a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
index 181362bc0ffcd63..f4e3aa40ed248b0 100644
--- a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
+++ b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
@@ -33,9 +33,9 @@ Instant Bank Payments via Link is available to US-based self-serve accounts acro
 
 Bank-based Link payments appear in your billing history with these identifiers:
 
-| Field            | Value  |
-| ---------------- | ------ |
-| Payment method   | `link` |
+| Field | Value |
+| --- | --- |
+| Payment method | `link` |
 | Last four digits | `0000` |
 
 Card-based Link payments display your card's last four digits, distinguishing them from bank payments.
diff --git a/src/content/docs/billing/threshold-billing.mdx b/src/content/docs/billing/threshold-billing.mdx
index 856ef82e55f97e7..0c72335ac0c6b0a 100644
--- a/src/content/docs/billing/threshold-billing.mdx
+++ b/src/content/docs/billing/threshold-billing.mdx
@@ -27,11 +27,11 @@ You will never be double-charged. The threshold invoice and end-of-cycle invoice
 
 ### Example
 
-| Event                                       | Charge                                             |
-| ------------------------------------------- | -------------------------------------------------- |
-| Combined usage reaches threshold mid-cycle  | Threshold invoice charged (for example, $127.50)   |
+| Event | Charge |
+| --- | --- |
+| Combined usage reaches threshold mid-cycle | Threshold invoice charged (for example, $127.50) |
 | End of billing cycle (total usage was $180) | End-of-cycle invoice charged (for example, $52.50) |
-| **Total charged**                           | **$180**                                           |
+| **Total charged** | **$180** |
 
 ## Products subject to threshold billing
 
diff --git a/src/content/docs/billing/troubleshoot/error-reference.mdx b/src/content/docs/billing/troubleshoot/error-reference.mdx
index ea345499f66f805..e2fbd524b5852d0 100644
--- a/src/content/docs/billing/troubleshoot/error-reference.mdx
+++ b/src/content/docs/billing/troubleshoot/error-reference.mdx
@@ -12,21 +12,21 @@ Use the table below to find common billing error messages, understand what they
 
 ## Error messages
 
-| Error message                                                                               | Cause                                                                                 | Solution                                                                                                                                                                                     |
-| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance.                                                   | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/).                                                                                                               |
-| "The payment has failed. Please contact your bank or use a different payment method."       | Your payment method was declined by your bank.                                        | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                             |
-| "Payment error: authorization failed"                                                       | Your bank declined the transaction, or 3DS authentication was not completed.          | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                                          |
-| "This zone cannot be upgraded"                                                              | The account or a previous owner of the domain has an outstanding balance.             | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
-| "There is a problem with your billing profile"                                              | Same as "this zone cannot be upgraded" — an unpaid balance exists.                    | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours.                                                                                             |
-| "You cannot modify this subscription since it is currently scheduled to be cancelled"       | You are trying to change a subscription that already has a pending cancellation.      | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/).     |
-| "You can't remove this payment method while it's linked to active subscriptions."           | You are trying to delete a payment method that is still tied to paid services.        | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).    |
-| "You can't remove a payment method while there are transactions in progress."               | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).                       |
+| Error message | Cause | Solution |
+|---|---|---|
+| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/). |
+| "The payment has failed. Please contact your bank or use a different payment method." | Your payment method was declined by your bank. | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
+| "Payment error: authorization failed" | Your bank declined the transaction, or 3DS authentication was not completed. | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
+| "This zone cannot be upgraded" | The account or a previous owner of the domain has an outstanding balance. | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
+| "There is a problem with your billing profile" | Same as "this zone cannot be upgraded" — an unpaid balance exists. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours. |
+| "You cannot modify this subscription since it is currently scheduled to be cancelled" | You are trying to change a subscription that already has a pending cancellation. | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/). |
+| "You can't remove this payment method while it's linked to active subscriptions." | You are trying to delete a payment method that is still tied to paid services. | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
+| "You can't remove a payment method while there are transactions in progress." | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
 
 ## Email notifications
 
-| Email subject                              | What it means                                                                            | What to do                                                                                                                                                                      |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Email subject | What it means | What to do |
+|---|---|---|
 | "We couldn't process your renewal payment" | A recurring subscription charge failed. Cloudflare will retry up to 5 times over 5 days. | Update your payment method or manually pay the invoice before the grace period ends. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
 
 ## Still stuck?
diff --git a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
index 8cbc680da963f94..276892b5ec3390d 100644
--- a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
@@ -10,14 +10,13 @@ products:
 
 When attempting to remove a payment method, you may see one of the following error messages:
 
-- "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
-- "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
+* "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
+* "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
 
 ## Causes
-
-- You still have active paid subscriptions
-- You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
-- You have an upcoming Registrar domain registration renewal within the next 24 hours
+* You still have active paid subscriptions
+* You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
+* You have an upcoming Registrar domain registration renewal within the next 24 hours
 
 ## Solutions
 
@@ -37,19 +36,19 @@ Repeat this for all active paid subscriptions before attempting to remove the pa
 
 If you have cancelled all paid subscriptions, any usage-based products cancelled within the last 30 days may still generate charges. Your payment method must remain on file until those charges are processed. If you recently cancelled any of the following products, wait 30 days before removing your payment method:
 
-- Images
-- Stream
-- Workers
-- Argo
-- Spectrum
-- R2
-- Cache Reserve
-- Load Balancing
-- Rate Limiting
-- Log Explorer
-- Zero Trust
-- Vectorize
-- Analytics
+* Images
+* Stream
+* Workers
+* Argo
+* Spectrum
+* R2
+* Cache Reserve
+* Load Balancing
+* Rate Limiting
+* Log Explorer
+* Zero Trust
+* Vectorize
+* Analytics
 
 After the next monthly invoice is generated, you can remove the payment method.
 
diff --git a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
index eb388902186d5ac..b43d3e71c65fec6 100644
--- a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
@@ -10,19 +10,16 @@ products:
 
 When attempting to cancel or modify a subscription, you may see the following error message:
 
-- "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
+* "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
 
 ## Causes
-
-- You are attempting to cancel a subscription which you have already requested cancellation for
-- You are attempting to upgrade a subscription for which a cancellation is already scheduled
+* You are attempting to cancel a subscription which you have already requested cancellation for
+* You are attempting to upgrade a subscription for which a cancellation is already scheduled
 
 ## Solutions
-
 If you intended to cancel a subscription, the cancellation is already scheduled. Your subscription ends at the close of the current billing period. Refer to the section below to find the exact date.
 
 ### When will my subscription be cancelled?
-
 After requesting cancellation, the subscriptions page shows the end date under "Ending On".
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
@@ -34,7 +31,6 @@ After requesting cancellation, the subscriptions page shows the end date under "
 If you previously cancelled the subscription and have changed your decision, you need to cancel the downgrade.
 
 ### Can I receive a refund for my cancelled subscription?
-
 No refund will be issued for a cancelled subscription - instead, your subscription will remain active until the end of the current billing period.
 
 If you do not wish to pay for the coming billing period, then you should cancel your subscription no later than on the last day of the billing period. You can discover this date by visiting the **Subscriptions** page and checking the renew date, for example “RENEWS ON Aug 29, 2025”.
@@ -59,4 +55,4 @@ If the cancellation hasn’t taken effect yet, you can click **Cancel Downgrade*
 
 - [Cancel subscriptions](/billing/manage/cancel-subscription/) — How cancellations work
 - [Billing policy](/billing/understand/billing-policy/) — Refund policy and billing terms
-- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
+- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
\ No newline at end of file
diff --git a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
index 32e60e707eb83a6..aba89709e47d926 100644
--- a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
+++ b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
@@ -34,4 +34,4 @@ You may have to wait up to one billing period for updates to appear in your Clou
 
 - [Invoices](/billing/manage/invoices/) — Download and manage invoices
 - [How Cloudflare billing works](/billing/understand/how-billing-works/) — How to read your invoice
-- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
+- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
\ No newline at end of file
diff --git a/src/content/docs/billing/understand/billing-permissions.mdx b/src/content/docs/billing/understand/billing-permissions.mdx
index 90f8f01686d0a1a..f0a656bc1f33ea6 100644
--- a/src/content/docs/billing/understand/billing-permissions.mdx
+++ b/src/content/docs/billing/understand/billing-permissions.mdx
@@ -10,19 +10,19 @@ Access to billing features in the Cloudflare dashboard depends on the role assig
 
 ## Roles and billing capabilities
 
-| Action                             | Super Administrator | Administrator | Billing |
-| ---------------------------------- | ------------------- | ------------- | ------- |
-| View invoices and billing history  | Yes                 | Yes           | Yes     |
-| Download invoice PDFs              | Yes                 | Yes           | Yes     |
-| View billable usage dashboard      | Yes                 | Yes           | Yes     |
-| Pay an outstanding balance         | Yes                 | No            | Yes     |
-| Add or update payment methods      | Yes                 | No            | Yes     |
-| Change billing address             | Yes                 | No            | Yes     |
-| Change billing email               | Yes                 | No            | Yes     |
-| Set up budget alerts               | Yes                 | Yes           | Yes     |
-| Change or cancel subscriptions     | Yes                 | Yes           | No      |
-| Upgrade or downgrade a domain plan | Yes                 | Yes           | No      |
-| Manage account members and roles   | Yes                 | No            | No      |
+| Action | Super Administrator | Administrator | Billing |
+|---|---|---|---|
+| View invoices and billing history | Yes | Yes | Yes |
+| Download invoice PDFs | Yes | Yes | Yes |
+| View billable usage dashboard | Yes | Yes | Yes |
+| Pay an outstanding balance | Yes | No | Yes |
+| Add or update payment methods | Yes | No | Yes |
+| Change billing address | Yes | No | Yes |
+| Change billing email | Yes | No | Yes |
+| Set up budget alerts | Yes | Yes | Yes |
+| Change or cancel subscriptions | Yes | Yes | No |
+| Upgrade or downgrade a domain plan | Yes | Yes | No |
+| Manage account members and roles | Yes | No | No |
 
 :::note
 The Billing role can view and pay but cannot change subscriptions or plans. To both manage subscriptions and handle payments, a user needs the Super Administrator role.
diff --git a/src/content/docs/billing/understand/billing-policy.mdx b/src/content/docs/billing/understand/billing-policy.mdx
index b980bae02a464c9..14a33c5e72ce247 100644
--- a/src/content/docs/billing/understand/billing-policy.mdx
+++ b/src/content/docs/billing/understand/billing-policy.mdx
@@ -81,15 +81,15 @@ Enterprise account owners receive invoices directly from the Cloudflare accounti
 
 Cloudflare accepts the following payment methods:
 
-- Visa
-- Mastercard
-- American Express
-- Discover
-- PayPal
-- Apple Pay
-- Google Pay
-- Stripe Link
-- UnionPay
+* Visa
+* Mastercard
+* American Express
+* Discover
+* PayPal
+* Apple Pay
+* Google Pay
+* Stripe Link
+* UnionPay
 
 :::note
 Enterprise customers can use ACH payments for Cloudflare plans and subscriptions.
diff --git a/src/content/docs/billing/understand/how-charges-accrue.mdx b/src/content/docs/billing/understand/how-charges-accrue.mdx
index d13bbe22d007ff3..44a3bbcf2906350 100644
--- a/src/content/docs/billing/understand/how-charges-accrue.mdx
+++ b/src/content/docs/billing/understand/how-charges-accrue.mdx
@@ -26,17 +26,17 @@ Consider a visitor loading a page on a Pro domain that uses Workers, R2, Argo Sm
 
 The visitor's browser resolves the domain. This DNS query is handled by Cloudflare's authoritative DNS.
 
-| Resource    | Billing impact                                                                                                                                 |
-| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | DNS queries | Included in all plans at no extra charge. If you use Load Balancing, DNS queries to load-balanced hostnames are metered (first 500K included). |
 
 ### 2. Edge request and TLS
 
 The request arrives at the nearest Cloudflare data center. Cloudflare terminates TLS and processes the request.
 
-| Resource | Billing impact                                                                              |
-| -------- | ------------------------------------------------------------------------------------------- |
-| TLS/SSL  | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
+| Resource | Billing impact |
+|---|---|
+| TLS/SSL | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
 
 ### 3. Cache lookup
 
@@ -44,9 +44,9 @@ Cloudflare checks whether a cached response exists for this request.
 
 **Cache hit** — the response is served directly from the edge. No origin fetch occurs. This is the cheapest path.
 
-| Resource            | Billing impact                                                                                                                                                                                      |
-| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bandwidth           | Included in all plans. Cloudflare does not charge for bandwidth.                                                                                                                                    |
+| Resource | Billing impact |
+|---|---|
+| Bandwidth | Included in all plans. Cloudflare does not charge for bandwidth. |
 | Cache Reserve reads | If Cache Reserve is enabled and the asset is served from tiered cache storage, reads are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 **Cache miss** — the request must be forwarded to the origin. Continue to step 4.
@@ -55,53 +55,53 @@ Cloudflare checks whether a cached response exists for this request.
 
 If Argo is enabled, Cloudflare routes the request through the fastest path across its network to your origin.
 
-| Resource           | Billing impact                                                                                                                                             |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Argo data transfer | Metered per GB transferred between Cloudflare and your origin. First 1 GB included. Refer to [Argo Smart Routing](/argo-smart-routing/) for current rates. |
 
 ### 5. Workers execution (if configured)
 
 If a Worker is bound to the route, it executes before or instead of fetching from the origin.
 
-| Resource                | Billing impact                                                                                                                                    |
-| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Worker requests         | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Worker CPU time         | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates.        |
-| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates.   |
+| Resource | Billing impact |
+|---|---|
+| Worker requests | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Worker CPU time | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates. |
 
 ### 6. Origin fetch and response
 
 If the Worker or cache miss triggers an origin fetch, Cloudflare retrieves the response from your origin server.
 
-| Resource  | Billing impact                                                                   |
-| --------- | -------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Bandwidth | No charge for data transfer between Cloudflare and your origin (no egress fees). |
 
 ### 7. R2 storage operations (if used)
 
 If the Worker or origin logic reads from or writes to R2, each operation is metered.
 
-| Resource                       | Billing impact                                                                     |
-| ------------------------------ | ---------------------------------------------------------------------------------- |
-| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.   |
-| R2 Class B operations (reads)  | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.  |
-| R2 storage                     | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 data egress                 | Free. Cloudflare does not charge for R2 egress.                                    |
+| Resource | Billing impact |
+|---|---|
+| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 Class B operations (reads) | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 storage | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 data egress | Free. Cloudflare does not charge for R2 egress. |
 
 ### 8. Cache write (miss path)
 
 After fetching from the origin, Cloudflare caches the response at the edge for future requests.
 
-| Resource             | Billing impact                                                                                                                                     |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Cache Reserve writes | If Cache Reserve is enabled, writes are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 ### 9. Image Resizing (if configured)
 
 If the request triggers Image Resizing (via URL parameters or a Worker), the transformation is metered.
 
-| Resource              | Billing impact                                                                                                                       |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| Resource | Billing impact |
+|---|---|
 | Image transformations | First 50,000 included on the Business plan, then metered per request. Refer to [Images pricing](/images/pricing/) for current rates. |
 
 ### 10. Response delivered
@@ -116,15 +116,15 @@ The key takeaway: **cached responses are the cheapest path**. Every cache hit av
 
 ## Cost optimization strategies
 
-| Strategy                                                                            | Products affected               | Impact                                                            |
-| ----------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------- |
-| Maximize cache hit ratio with appropriate Cache-Control headers                     | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs               |
-| Use Cache Reserve for long-tail content                                             | Cache, origin                   | Medium — reduces origin fetches for infrequently accessed content |
-| Set appropriate TTLs to avoid unnecessary revalidation                              | Cache, Argo                     | Medium — reduces origin round-trips                               |
-| Use Workers Smart Placement to run Workers closer to your data                      | Workers CPU time                | Medium — reduces execution time for data-dependent Workers        |
-| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage                      | Medium — reduces storage costs for archival data                  |
-| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/)  | All usage-based products        | High — visibility is the first step to optimization               |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes   | All usage-based products        | High — prevents surprise invoices                                 |
+| Strategy | Products affected | Impact |
+|---|---|---|
+| Maximize cache hit ratio with appropriate Cache-Control headers | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs |
+| Use Cache Reserve for long-tail content | Cache, origin | Medium — reduces origin fetches for infrequently accessed content |
+| Set appropriate TTLs to avoid unnecessary revalidation | Cache, Argo | Medium — reduces origin round-trips |
+| Use Workers Smart Placement to run Workers closer to your data | Workers CPU time | Medium — reduces execution time for data-dependent Workers |
+| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage | Medium — reduces storage costs for archival data |
+| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/) | All usage-based products | High — visibility is the first step to optimization |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes | All usage-based products | High — prevents surprise invoices |
 
 ## Related resources
 
diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx
index 4b7d658484684f6..0be6d9d6118dc30 100644
--- a/src/content/docs/billing/understand/preview-services.mdx
+++ b/src/content/docs/billing/understand/preview-services.mdx
@@ -29,7 +29,7 @@ To enable a preview service, use the **Dashboard link** in the following table.
 | Load Balancing                     | [Load Balancing dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing)          | [Load Balancing docs](/load-balancing/)                                    | [Load Balancing community](https://community.cloudflare.com/tag/loadbalancing) |
 | Advanced Rate Limiting             | [Rate Limiting dashboard](https://dash.cloudflare.com/?to=/:account/:zone/security/waf/rate-limiting-rules) | [Rate Limiting docs](/waf/rate-limiting-rules/)                            | [Rate Limiting community](https://community.cloudflare.com/c/security/6)       |
 | Stream                             | [Stream dashboard](https://dash.cloudflare.com/?to=/:account/stream)                                        | [Stream docs](/stream/)                                                    | [Stream community](https://community.cloudflare.com/tag/cloudflarestream)      |
-| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)             | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
+| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)        | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
 | Web3                               | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3)                                      | [Web3 docs](/web3/)                                                        | [Web3 discord](https://discord.cloudflare.com)                                 |
 | Workers                            | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers)                                      | [Workers docs](/workers/)                                                  | [Workers discord](https://discord.com/invite/cloudflaredev)                    |
 | Zero Trust                         | [Zero Trust dashboard](https://one.dash.cloudflare.com/)                                                    | [Zero Trust docs](/cloudflare-one/)                                        | [Zero Trust community](https://community.cloudflare.com/c/security/access/51)  |
diff --git a/src/content/docs/billing/understand/usage-based-billing.mdx b/src/content/docs/billing/understand/usage-based-billing.mdx
index c3270b67c1b766d..2e7cc4c49963e48 100644
--- a/src/content/docs/billing/understand/usage-based-billing.mdx
+++ b/src/content/docs/billing/understand/usage-based-billing.mdx
@@ -24,29 +24,29 @@ The following products bill based on consumption. Each product includes a free t
 
 For current overage rates, refer to the [Cloudflare plans page](https://www.cloudflare.com/plans/) or each product's pricing page linked below. Rates may change — the links below are always up to date.
 
-| Product                                                       | Billable metric                | Free tier (included)                   | Pricing details                                                       |
-| ------------------------------------------------------------- | ------------------------------ | -------------------------------------- | --------------------------------------------------------------------- |
-| [Workers](/workers/platform/pricing/)                         | Requests, CPU time             | 10M requests, 30M CPU-ms               | [Workers pricing](/workers/platform/pricing/)                         |
-| [R2](/r2/pricing/)                                            | Storage, operations            | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/)                                            |
-| [Argo Smart Routing](/argo-smart-routing/)                    | Data transfer (GB)             | First 1 GB                             | [Argo pricing](/argo-smart-routing/)                                  |
-| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage         | None                                   | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
-| [Load Balancing](/load-balancing/)                            | DNS queries                    | First 500K                             | [Load Balancing](/load-balancing/)                                    |
-| [Stream](/stream/pricing/)                                    | Minutes stored, minutes viewed | Varies by plan                         | [Stream pricing](/stream/pricing/)                                    |
-| [Images](/images/pricing/)                                    | Transformations, storage       | Varies by plan                         | [Images pricing](/images/pricing/)                                    |
-| [Spectrum](/spectrum/)                                        | Data transfer (GB)             | None                                   | [Spectrum](/spectrum/)                                                |
+| Product | Billable metric | Free tier (included) | Pricing details |
+|---|---|---|---|
+| [Workers](/workers/platform/pricing/) | Requests, CPU time | 10M requests, 30M CPU-ms | [Workers pricing](/workers/platform/pricing/) |
+| [R2](/r2/pricing/) | Storage, operations | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/) |
+| [Argo Smart Routing](/argo-smart-routing/) | Data transfer (GB) | First 1 GB | [Argo pricing](/argo-smart-routing/) |
+| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage | None | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
+| [Load Balancing](/load-balancing/) | DNS queries | First 500K | [Load Balancing](/load-balancing/) |
+| [Stream](/stream/pricing/) | Minutes stored, minutes viewed | Varies by plan | [Stream pricing](/stream/pricing/) |
+| [Images](/images/pricing/) | Transformations, storage | Varies by plan | [Images pricing](/images/pricing/) |
+| [Spectrum](/spectrum/) | Data transfer (GB) | None | [Spectrum](/spectrum/) |
 
 ## Optimize usage-based costs
 
 Reducing usage-based charges starts with understanding where your consumption comes from. Use the [billable usage dashboard](/billing/manage/billable-usage/) to identify which products are driving costs, then apply the strategies below.
 
-| Strategy                                                                                                 | What it reduces                                      |
-| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                        | Argo data transfer, Workers invocations, origin load |
-| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content                  | Origin fetches for infrequently accessed assets      |
-| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs                                     |
-| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers                  | Workers CPU time                                     |
-| Batch R2 operations where possible instead of per-object reads                                           | R2 Class B operation count                           |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early                  | All products — prevents surprise invoices            |
+| Strategy | What it reduces |
+|---|---|
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
+| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content | Origin fetches for infrequently accessed assets |
+| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs |
+| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers | Workers CPU time |
+| Batch R2 operations where possible instead of per-object reads | R2 Class B operation count |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | All products — prevents surprise invoices |
 
 For a detailed walkthrough of how a single request generates charges across multiple products, refer to [How charges accrue](/billing/understand/how-charges-accrue/).
 
diff --git a/src/content/docs/bots/account-abuse-protection.mdx b/src/content/docs/bots/account-abuse-protection.mdx
index e54a667206310fc..ddd1362d953258a 100644
--- a/src/content/docs/bots/account-abuse-protection.mdx
+++ b/src/content/docs/bots/account-abuse-protection.mdx
@@ -12,15 +12,16 @@ sidebar:
   badge:
     text: Early Access
     variant: note
+
 ---
 
-import { Render, Description, DashButton, Steps } from "~/components";
+import { Render, Description, DashButton, Steps } from "~/components"
 
 <Description>
-	Identify and mitigate attacks on your customer and user accounts.
+Identify and mitigate attacks on your customer and user accounts.
 </Description>
 
-Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems.
+Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems. 
 
 ## Availability
 
@@ -37,15 +38,15 @@ Contact your Cloudflare account team to request access.
 User ID is a cryptographically hashed, per-zone identifier that customers can use in [Security Analytics](/waf/analytics/security-analytics/), [Security Rules](/waf/custom-rules/), and [Managed Transforms](/rules/transform/managed-transforms/reference/). Hashed User IDs are created by encrypting the primary credentials your users provide, converting them into opaque identifiers unique to your zone. This allows traffic analysis while protecting user privacy. With access to hashed User ID, website owners can:
 
 - Review which users have the most activity on your website.
-- Find the details on a specific user's characteristics and activity patterns.
-- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.
-- Combine fields to see when accounts are being targeted with leaked credentials.
+- Find the details on a specific user's characteristics and activity patterns.  
+- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.  
+- Combine fields to see when accounts are being targeted with leaked credentials.  
 - Manage network patterns or signals associated with specific users.
 
 :::note[Data privacy]
-User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications.
+User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications. 
 
-Other Cloudflare customers cannot access your user profiles. They are unique to your zone.
+Other Cloudflare customers cannot access your user profiles. They are unique to your zone. 
 :::
 
 User ID is an opt-in feature that can be enabled in Security Settings.
@@ -64,13 +65,13 @@ To enable, edit, or disable the setting:
 
 ### Ephemeral IDs
 
-Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection.
+Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection. 
 
 Refer to [Fraud detection with ephemeral IDs](/turnstile/tutorials/fraud-detection-with-ephemeral-ids/) for more information.
 
 ### Account takeover detections
 
-Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks.
+Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks. 
 
 Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/) for more information.
 
@@ -84,25 +85,25 @@ Account takeover (ATO) detections are not available for accounts using the [Data
 
 ### Prerequisites
 
-Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior.
+Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior. 
 
 #### Security Settings
 
-- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections.
+- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections. 
 
-#### Eligible traffic
+#### Eligible traffic 
 
-Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations.
+Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations. 
 
 - Sign-ups: Cloudflare automatically monitors traffic on endpoints that match common sign up endpoints.
 - Login: Cloudflare automatically monitors traffic on endpoints that match common login endpoints.
 
 Verify that your endpoints are properly labeled to ensure Cloudflare can detect and monitor them correctly.
 
-<Render
-	file="endpoint-label-warning"
-	product="bots"
-	params={{ one: "or sign up" }}
+<Render 
+  file="endpoint-label-warning" 
+  product="bots"
+  params={{ one: "or sign up" }} 
 />
 
 :::tip[Enhanced with leaked credential detections]
@@ -113,43 +114,43 @@ Cloudflare also recommends enabling [Leaked credentials detection](/waf/detectio
 
 ### Detections
 
-Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints.
+Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints. 
 
 #### Account creation
 
-Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure.
+Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure. 
 
-You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email.
+You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email. 
 
 #### Suspicious emails
 
-Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections.
+Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections. 
 
-Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching.
+Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching. 
 
-| Detection tag                         | Description                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services.                                                                                                                                                                                                                                                                            |
-| `cf.fraud.email_risk`                 | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
+| Detection tag | Description |
+| --- | --- |
+| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services. |
+| `cf.fraud.email_risk` | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
 
----
+--- 
 
 ### Mitigations
 
-The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic.
+The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic. 
 
 #### Security Rules
 
 The following fields can be used in new and existing Security Rules.
 
-| Field                                  | Description                                                                                        | Values                                                                                                                                                                                                                                                              |
-| -------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False`                                                                                                                                                                                                                                                   |
-| `cf.fraud.email_risk`                  | Measures risk of email based on randomness of characters in the username and domain.               | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
+| Field | Description | Values |
+| --- | --- | --- |
+| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False` |
+| `cf.fraud.email_risk` | Measures risk of email based on randomness of characters in the username and domain. | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
 
 #### Other rules
 
-You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin.
+You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin. 
 
 #### LogPush
 
@@ -159,12 +160,12 @@ You can add Fraud detection fields to existing or new [LogPush](/logs/logpush/)
 
 ## Analytics
 
-You can find Fraud data and detections in Security Analytics, where you can see top User IDs.
+You can find Fraud data and detections in Security Analytics, where you can see top User IDs. 
 
 <DashButton url="/?to=/:account/:zone/security/analytics" />
 
-Fraud fields can be used as filters to identify suspicious patterns in your traffic.
+Fraud fields can be used as filters to identify suspicious patterns in your traffic. 
 
-The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers.
+The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers. 
 
 A user level profile also provides a quick way to review the latest events associated with a user so that you can identify any anomalies and create a custom rule to log, block, or challenge that user.
diff --git a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
index b666e3479ba08d7..61260abf06b336f 100644
--- a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
+++ b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
@@ -12,7 +12,7 @@ sidebar:
   label: Block AI Bots
 ---
 
-import { Render, Steps, DashButton } from "~/components";
+import { Render, Steps, DashButton } from "~/components"
 
 :::note[Block AI bots availability]
 The **Block AI bots** feature is only available in the new [application security dashboard](/security/).
@@ -35,4 +35,4 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
   5. Select **Save** to save your configuration.
 </Steps>
 
-To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
+To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
\ No newline at end of file
diff --git a/src/content/docs/bots/additional-configurations/custom-rules.mdx b/src/content/docs/bots/additional-configurations/custom-rules.mdx
index fca74fa82b41d73..287bace657d036c 100644
--- a/src/content/docs/bots/additional-configurations/custom-rules.mdx
+++ b/src/content/docs/bots/additional-configurations/custom-rules.mdx
@@ -16,17 +16,17 @@ Bot protection on Cloudflare works through two complementary mechanisms: built-i
 
 The following features are configured through toggles and dropdowns in [Security Settings](/security/settings/). They do not require you to write any rule expressions.
 
-| Feature                                                                                | What it does                                                                                       | Availability                  |
-| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- |
-| [Block AI bots](/bots/additional-configurations/block-ai-bots/)                        | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans                     |
-| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/)                          | Feeds non-compliant AI crawlers into a maze of generated content                                   | All plans                     |
-| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/)              | Prepends AI crawler disallow directives to your `robots.txt`                                       | All plans                     |
-| Super Bot Fight Mode > **Definitely automated**                                        | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1                    | Pro, Business, Enterprise     |
-| Super Bot Fight Mode > **Likely automated**                                            | Blocks or challenges traffic with a bot score of 2-29                                              | Business, Enterprise          |
-| [Verified bots](/bots/concepts/bot/verified-bots/)                                     | Managed category of high-trust bots (Googlebot, Bingbot, and others)                               | Pro, Business, Enterprise     |
-| [Static resource protection](/bots/additional-configurations/static-resources/)        | Extends bot actions to cover static file types                                                     | Pro, Business, Enterprise     |
-| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/)              | Allows WordPress loopback requests through bot protection                                          | Pro, Business, Enterprise     |
-| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript                    | All plans (automatic on Free) |
+| Feature | What it does | Availability |
+| --- | --- | --- |
+| [Block AI bots](/bots/additional-configurations/block-ai-bots/) | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans |
+| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/) | Feeds non-compliant AI crawlers into a maze of generated content | All plans |
+| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/) | Prepends AI crawler disallow directives to your `robots.txt` | All plans |
+| Super Bot Fight Mode > **Definitely automated** | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1 | Pro, Business, Enterprise |
+| Super Bot Fight Mode > **Likely automated** | Blocks or challenges traffic with a bot score of 2-29 | Business, Enterprise |
+| [Verified bots](/bots/concepts/bot/verified-bots/) | Managed category of high-trust bots (Googlebot, Bingbot, and others) | Pro, Business, Enterprise |
+| [Static resource protection](/bots/additional-configurations/static-resources/) | Extends bot actions to cover static file types | Pro, Business, Enterprise |
+| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/) | Allows WordPress loopback requests through bot protection | Pro, Business, Enterprise |
+| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript | All plans (automatic on Free) |
 
 Bot settings update automatically as Cloudflare identifies new bot signatures and AI crawlers, while custom rules require manual updates. They do not count toward your [custom rule limits](/waf/custom-rules/#availability), and apply uniformly across your domain without the risk of expression errors.
 
diff --git a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
index d36b1802e907d09..ce92bacfafafb92 100644
--- a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
@@ -12,6 +12,7 @@ Cloudflare bot detection includes additional signals to catch different kinds of
 
 Bot management customers automatically benefit from the residential proxy detection improvement below, which lowers the [bot score](/bots/concepts/bot-score/) for matched requests. Using the detection ID in [custom rules](/waf/custom-rules/) provides even more visibility and control over mitigating residential proxy traffic.
 
-| <div style="width:100px">Detection ID</div> | Description                                                                                                                                                                                                                                                                               |
-| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `50331651`                                  | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
+
+| <div style="width:100px">Detection ID</div> | Description                              |
+| ------------------------------------------ | ---------------------------------------- |
+| `50331651`                                 | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
diff --git a/src/content/docs/bots/additional-configurations/index.mdx b/src/content/docs/bots/additional-configurations/index.mdx
index bc876caf734e5e0..0768d508f998fd1 100644
--- a/src/content/docs/bots/additional-configurations/index.mdx
+++ b/src/content/docs/bots/additional-configurations/index.mdx
@@ -11,10 +11,11 @@ sidebar:
 head:
   - tag: title
     content: Additional Bots configurations
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on additional bot management configurations:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
index f8af19b5b7de7b0..b575e485e4d47b1 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 1
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 [**JA3**](https://github.com/salesforce/ja3) and [**JA4**](https://github.com/FoxIO-LLC/ja4) **fingerprints** identify TLS clients based on how they initiate connections. Each client type (browser, bot, or application) has distinct connection characteristics, so the resulting fingerprint acts as a stable identifier across different destination IPs, ports, and certificates.
 
@@ -16,62 +17,64 @@ JA4 improves on JA3 by sorting ClientHello extensions, which reduces the number
 
 :::note
 
-JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management.
+JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management. 
 :::
 
 <Render file="signals-intelligence-and-ja4" product="bots" />
 
 ```json
+
 {
-	"ja4Signals": {
-		"h2h3_ratio_1h": 0.98826485872269,
-		"heuristic_ratio_1h": 7.288895722013e-5,
-		"reqs_quantile_1h": 0.99905741214752,
-		"uas_rank_1h": 901,
-		"browser_ratio_1h": 0.93640440702438,
-		"paths_rank_1h": 655,
-		"reqs_rank_1h": 850,
-		"cache_ratio_1h": 0.18918327987194,
-		"ips_rank_1h": 662,
-		"ips_quantile_1h": 0.99926590919495
-	},
-	"jaSignalsParsed": {
-		"ratios": {
-			"h2h3_ratio_1h": 0.98826485872269,
-			"heuristic_ratio_1h": 7.288895722013e-5,
-			"browser_ratio_1h": 0.93640440702438,
-			"cache_ratio_1h": 0.18918327987194
-		},
-		"ranks": {
-			"uas_rank_1h": 901,
-			"paths_rank_1h": 655,
-			"reqs_rank_1h": 850,
-			"ips_rank_1h": 662
-		},
-		"quantiles": {
-			"reqs_quantile_1h": 0.99905741214752,
-			"ips_quantile_1h": 0.99926590919495
-		}
-	}
+  "ja4Signals": {
+    "h2h3_ratio_1h": 0.98826485872269,
+    "heuristic_ratio_1h": 7.288895722013e-05,
+    "reqs_quantile_1h": 0.99905741214752,
+    "uas_rank_1h": 901,
+    "browser_ratio_1h": 0.93640440702438,
+    "paths_rank_1h": 655,
+    "reqs_rank_1h": 850,
+    "cache_ratio_1h": 0.18918327987194,
+    "ips_rank_1h": 662,
+    "ips_quantile_1h": 0.99926590919495
+  },
+  "jaSignalsParsed": {
+    "ratios": {
+      "h2h3_ratio_1h": 0.98826485872269,
+      "heuristic_ratio_1h": 7.288895722013e-05,
+      "browser_ratio_1h": 0.93640440702438,
+      "cache_ratio_1h": 0.18918327987194
+    },
+    "ranks": {
+      "uas_rank_1h": 901,
+      "paths_rank_1h": 655,
+      "reqs_rank_1h": 850,
+      "ips_rank_1h": 662
+    },
+    "quantiles": {
+      "reqs_quantile_1h": 0.99905741214752,
+      "ips_quantile_1h": 0.99926590919495
+    }
+  }
 }
+
 ```
 
 When JA4 Signals are missing, the output appears as follows:
 
 ```json output title="Missing JA4 signals output"
 {
-	"ja4Signals": {},
-	"jaSignalsParsed": {
-		"ratios": {},
-		"ranks": {},
-		"quantiles": {}
-	}
+  "ja4Signals": {},
+  "jaSignalsParsed": {
+    "ratios": {},
+    "ranks": {},
+    "quantiles": {}
+  }
 }
 ```
 
 :::note
 
-This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/).
+This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/). 
 :::
 
 <Render file="ja3-ja4-null" product="bots" />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
index 23baf713cc11a7c..2a86d9d70cbc989 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Bot Management customers can view aggregate intelligence data for each [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/) based on traffic across the Cloudflare network. Use this data to understand why a request received a specific bot score or to feed into your own machine learning models running in [Cloudflare Workers](/workers/) or at your origin.
 
diff --git a/src/content/docs/bots/additional-configurations/javascript-detections.mdx b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
index e3c29b9383911ff..69e80bc8893eef4 100644
--- a/src/content/docs/bots/additional-configurations/javascript-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
@@ -7,4 +7,4 @@ products:
 external_link: /cloudflare-challenges/challenge-types/javascript-detections/
 sidebar:
   order: 3
----
+---
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot-tags.mdx b/src/content/docs/bots/concepts/bot-tags.mdx
index f498c1ebd7862df..ce7772981cc0afe 100644
--- a/src/content/docs/bots/concepts/bot-tags.mdx
+++ b/src/content/docs/bots/concepts/bot-tags.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 3
+
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip } from "~/components"
 
 <GlossaryTooltip term="bot tags">Bot tags</GlossaryTooltip> provide more detail about *why* Cloudflare assigned a <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/">bot score</GlossaryTooltip> to a request.
 
diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx
index 8135d2506798f9c..79b102ed14105a3 100644
--- a/src/content/docs/bots/concepts/bot/index.mdx
+++ b/src/content/docs/bots/concepts/bot/index.mdx
@@ -29,7 +29,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni
 <Render file="verified-bots" product="bots" />
 
 :::note
-The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability).
+The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability). 
 :::
 
 ## AI bots
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
index 51b8af2d0e34705..79b4ca637337d88 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
@@ -9,6 +9,7 @@ sidebar:
 learning_center:
   title: What is a bot?
   link: https://www.cloudflare.com/learning/bots/what-is-a-bot/
+
 ---
 
 A signed agent is a bot controlled by an end user and verified through [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) cryptographic signatures.
@@ -32,4 +33,4 @@ Once Cloudflare approves a signed agent, it should appear on [Cloudflare Radar's
 
 ## Verification method
 
-The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
+The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
index 7012c9a37f3a779..4b3a2e13bca22e5 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
@@ -5,8 +5,9 @@ description: Requirements an agent must meet to be listed as a Cloudflare signed
 products:
   - bots
 sidebar:
-  order: 3
-  label: Policy
+    order: 3
+    label: Policy
+
 ---
 
 In order to be listed by Cloudflare as a signed agent, your agent must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
@@ -63,4 +64,4 @@ If any of the requirements to validate are breached, a service will be removed f
 The following are examples of breaches of policy:
 
 - The service has vulnerabilities that have not been patched.
-- The disclosed purpose of the service does not reflect on the traffic.
+- The disclosed purpose of the service does not reflect on the traffic.
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
index 35f535378a55bd9..0a353f6982931b7 100644
--- a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
@@ -5,11 +5,12 @@ description: Requirements a bot must meet to be listed as a Cloudflare verified
 products:
   - bots
 sidebar:
-  order: 5
-  label: Policy
+    order: 5
+    label: Policy
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
 
diff --git a/src/content/docs/bots/concepts/index.mdx b/src/content/docs/bots/concepts/index.mdx
index 6c7d7f72e402af2..24071d2b6d12abd 100644
--- a/src/content/docs/bots/concepts/index.mdx
+++ b/src/content/docs/bots/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on bot concepts:
 
diff --git a/src/content/docs/bots/get-started/index.mdx b/src/content/docs/bots/get-started/index.mdx
index e3dd198f6f0fb99..4082e3406e6058c 100644
--- a/src/content/docs/bots/get-started/index.mdx
+++ b/src/content/docs/bots/get-started/index.mdx
@@ -12,9 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with Cloudflare bot solutions
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to get started with Cloudflare's bot solutions based on your plan type:
 
diff --git a/src/content/docs/bots/glossary.mdx b/src/content/docs/bots/glossary.mdx
index 51cd6fdaf56a98f..0fbbfcdccbc2f94 100644
--- a/src/content/docs/bots/glossary.mdx
+++ b/src/content/docs/bots/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 10
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Bots documentation.
 
diff --git a/src/content/docs/bots/plans/bm-subscription.mdx b/src/content/docs/bots/plans/bm-subscription.mdx
index c0946617758e924..3d5517526b98383 100644
--- a/src/content/docs/bots/plans/bm-subscription.mdx
+++ b/src/content/docs/bots/plans/bm-subscription.mdx
@@ -105,17 +105,17 @@ Zones that have [Enterprise Bot Management](/bots/get-started/bot-management/) e
 
 Bot Management customers have both bot settings (configured in **Security Settings**) and the ability to create custom rules using bot score fields. Start with the bot settings for baseline protection, then add custom rules only when you need additional control.
 
-| Feature                                         | Handled by bot settings | When to use custom rules instead                                                                  |
-| ----------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
-| Block or challenge definitely automated traffic | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
-| Block or challenge likely automated traffic     | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
-| Allow or block verified bots                    | No                      | Granular control by verified bot category                                                         |
-| Block AI crawlers                               | Yes                     | Target individual AI crawlers using detection IDs                                                 |
-| Protect static resources                        | No                      | Exclude static resources from specific rules                                                      |
-| Optimize for WordPress                          | No                      | No                                                                                                |
-| Forward bot data to origin                      | No                      | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/)                          |
-| Detection ID targeting                          | No                      | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/)                       |
-| JA3/JA4 fingerprint rules                       | No                      | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
+| Feature | Handled by bot settings | When to use custom rules instead |
+| --- | --- | --- |
+| Block or challenge definitely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
+| Block or challenge likely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
+| Allow or block verified bots | No | Granular control by verified bot category |
+| Block AI crawlers | Yes | Target individual AI crawlers using detection IDs |
+| Protect static resources | No | Exclude static resources from specific rules |
+| Optimize for WordPress | No | No |
+| Forward bot data to origin | No | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/) |
+| Detection ID targeting | No | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/) |
+| JA3/JA4 fingerprint rules | No | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
 
 For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
 
diff --git a/src/content/docs/bots/reference/alerts.mdx b/src/content/docs/bots/reference/alerts.mdx
index 039399e05dda310..76c74e5d486644c 100644
--- a/src/content/docs/bots/reference/alerts.mdx
+++ b/src/content/docs/bots/reference/alerts.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 4
+
 ---
 
-import { AvailableNotifications, Steps, DashButton } from "~/components";
+import { AvailableNotifications, Steps, DashButton } from "~/components"
 
 Bot alerts inform you when Cloudflare detects spikes in your traffic with any of the following characteristics:
 
@@ -16,7 +17,7 @@ Bot alerts inform you when Cloudflare detects spikes in your traffic with any of
 - An increase in traffic on available dimensions in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 - Filters of your choosing in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 
----
+--- 
 
 ## Alert types
 
@@ -72,5 +73,5 @@ You can also choose to group by the following dimensions so that they can be ale
 - Bot Detection IDs
 
 :::note
-Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/).
-:::
+Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/). 
+:::
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/bot-management-variables.mdx b/src/content/docs/bots/reference/bot-management-variables.mdx
index 388e76e2a3c7d80..8b78f19b39ba24e 100644
--- a/src/content/docs/bots/reference/bot-management-variables.mdx
+++ b/src/content/docs/bots/reference/bot-management-variables.mdx
@@ -6,21 +6,21 @@ products:
   - bots
 sidebar:
   order: 2
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Ruleset Engine fields
 
 Bot Management provides access to several [new variables](/ruleset-engine/rules-language/fields/reference/?field-category=Bots) within the expression builder of Ruleset Engine-based products such as [WAF custom rules](/waf/custom-rules/).
 
 - **Bot Score** (`cf.bot_management.score`): An integer between 1-99 that indicates [Cloudflare's level of certainty](/bots/concepts/bot-score/) that a request comes from a bot.
-- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot.
-
-  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service.
-
+- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot. 
+  
+  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service. 
+  
   We also use additional validation methods, including checking ASN blocks and public lists. If these methods are unavailable, Cloudflare utilizes internal data and machine learning to identify and verify legitimate IP addresses from good bots. Most customers choose to [allow this traffic](/ruleset-engine/rules-language/fields/reference/cf.bot_management.verified_bot/).
-
 - **Serves Static Resource** (`cf.bot_management.static_resource`): An identifier that matches [file extensions](/bots/additional-configurations/static-resources/) for many types of static resources. Use this variable if you send emails that retrieve static images.
 - **ja3Hash** (`cf.bot_management.ja3_hash`) and **ja4** (`cf.bot_management.ja4`): A [**JA3/JA4 fingerprint**](/bots/additional-configurations/ja3-ja4-fingerprint/) helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
 - **Bot Detection IDs** (`cf.bot_management.detection_ids`): List of IDs that correlate to the Bot Management heuristic detections made on a request (you can have multiple heuristic detections on the same request).
diff --git a/src/content/docs/bots/reference/bot-verification/index.mdx b/src/content/docs/bots/reference/bot-verification/index.mdx
index ea311232d0c71de..c074fd2973d2c84 100644
--- a/src/content/docs/bots/reference/bot-verification/index.mdx
+++ b/src/content/docs/bots/reference/bot-verification/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 1
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's validation methods for [Verified](/bots/concepts/bot/verified-bots/) and [Signed](/bots/concepts/bot/signed-agents/) bots.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
index e21b0eabee315f3..9d65f3cb32d07cf 100644
--- a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
+++ b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
@@ -5,11 +5,12 @@ description: Verify bot identity by matching request IP addresses against publis
 products:
   - bots
 sidebar:
-  order: 3
-  label: IP validation
+    order: 3
+    label: IP validation
+
 ---
 
-import { GlossaryTooltip, Steps } from "~/components";
+import { GlossaryTooltip, Steps } from "~/components"
 
 The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. IP validation is only used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/).
 
@@ -56,4 +57,4 @@ Generic user-agents include:
 - `node-fetch`
 - `okhttp`
 - `python-requests`
-- `uTorrent`
+- `uTorrent`
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/index.mdx b/src/content/docs/bots/reference/index.mdx
index f157689e81141cc..d98d7d7b81bce95 100644
--- a/src/content/docs/bots/reference/index.mdx
+++ b/src/content/docs/bots/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's bot solutions:
 
diff --git a/src/content/docs/bots/reference/machine-learning-models.mdx b/src/content/docs/bots/reference/machine-learning-models.mdx
index bdaac08a260b29c..49af33d0da4309d 100644
--- a/src/content/docs/bots/reference/machine-learning-models.mdx
+++ b/src/content/docs/bots/reference/machine-learning-models.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
 tags:
   - AI
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Enable auto-updates to the Machine Learning models
 
@@ -38,4 +39,4 @@ By not updating to the latest version, you will be using a Machine Learning mode
 | v6      | Significantly improved scoring for native Android application traffic. <br/><br/>Improved scoring on the newest versions of Chromium browsers.                                                                                              | Q1 2022     |
 | v7      | Increased recognition of distributed botnets. <br/><br/>Improved HTTP/3 scoring.                                                                                                                                                            | Q1 2024     |
 | v8      | Improved detection of residential proxies. <br/><br/>Increased weight on network level traffic characteristics.                                                                                                                             | Q2 2024     |
-| v9      | Improved model consistency and model efficacy against randomization attack techniques                                                                                                                                                       | Q2 2025     |
+| v9      | Improved model consistency and model efficacy against randomization attack techniques | Q2 2025     |
diff --git a/src/content/docs/bots/reference/sample-terms.mdx b/src/content/docs/bots/reference/sample-terms.mdx
index 2ba93ce64ee1935..3c05cc2e80dd3e8 100644
--- a/src/content/docs/bots/reference/sample-terms.mdx
+++ b/src/content/docs/bots/reference/sample-terms.mdx
@@ -8,6 +8,7 @@ sidebar:
   order: 5
 tags:
   - AI
+
 ---
 
 Cloudflare recommends that customers consider updating their Terms of Service to address bots specifically related to Artificial Intelligence (AI) training and data scraping. The text below provides an informational example of the kind of language that could be added to a website's terms of use.
@@ -18,7 +19,8 @@ Cloudflare recommends that customers consider updating their Terms of Service to
 
 :::caution[Disclaimer]
 
-This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome.
+This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome. 
 
-This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file.
+This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file. 
 :::
+
diff --git a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
index b8453361111ca0c..363aa1c84d09636 100644
--- a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
+++ b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 1
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/additional-configurations/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
 
diff --git a/src/content/docs/bots/troubleshooting/false-positives.mdx b/src/content/docs/bots/troubleshooting/false-positives.mdx
index 7d7dadcae903c10..377e7ac13199bff 100644
--- a/src/content/docs/bots/troubleshooting/false-positives.mdx
+++ b/src/content/docs/bots/troubleshooting/false-positives.mdx
@@ -7,6 +7,7 @@ products:
 sidebar:
   order: 3
   label: False positives
+
 ---
 
 import { Render } from "~/components";
@@ -24,4 +25,4 @@ You cannot bypass or skip Bot Fight Mode using the _Skip_ action in WAF custom r
 
 Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.
 
-If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
+If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
\ No newline at end of file
diff --git a/src/content/docs/bots/troubleshooting/index.mdx b/src/content/docs/bots/troubleshooting/index.mdx
index 821d9ed42c52b76..b1e6d5b78a345c4 100644
--- a/src/content/docs/bots/troubleshooting/index.mdx
+++ b/src/content/docs/bots/troubleshooting/index.mdx
@@ -12,10 +12,12 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot issues with Bots
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to troubleshoot issues with Cloudflare's bot solutions:
 
 <DirectoryListing />
+
diff --git a/src/content/docs/bots/workers-templates/index.mdx b/src/content/docs/bots/workers-templates/index.mdx
index 6bf57e8cbfb768f..aae030a3a8b29b2 100644
--- a/src/content/docs/bots/workers-templates/index.mdx
+++ b/src/content/docs/bots/workers-templates/index.mdx
@@ -12,9 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Workers templates
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the templates below to integrate Bot Management with [Cloudflare Workers](/workers/):
 
diff --git a/src/content/docs/browser-run/features/index.mdx b/src/content/docs/browser-run/features/index.mdx
index 8f79040189134a4..6ef34df2029deea 100644
--- a/src/content/docs/browser-run/features/index.mdx
+++ b/src/content/docs/browser-run/features/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/browser-run/how-to/deploy-worker.mdx b/src/content/docs/browser-run/how-to/deploy-worker.mdx
index d15deee8a1e1894..808b712441c47df 100644
--- a/src/content/docs/browser-run/how-to/deploy-worker.mdx
+++ b/src/content/docs/browser-run/how-to/deploy-worker.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 1
 products:
   - browser-run
-  - workers
+  - workers 
 ---
 
 import {
diff --git a/src/content/docs/browser-run/mcp-server.mdx b/src/content/docs/browser-run/mcp-server.mdx
index a79dc14dcabbbb1..3d7ba05eaeadd22 100644
--- a/src/content/docs/browser-run/mcp-server.mdx
+++ b/src/content/docs/browser-run/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - browser-run
----
+---
\ No newline at end of file
diff --git a/src/content/docs/browser-run/quick-actions/api-reference.mdx b/src/content/docs/browser-run/quick-actions/api-reference.mdx
index dc44d9a5ba8d2e4..15e3e787ca1f282 100644
--- a/src/content/docs/browser-run/quick-actions/api-reference.mdx
+++ b/src/content/docs/browser-run/quick-actions/api-reference.mdx
@@ -4,7 +4,7 @@ title: Reference
 description: View the complete Browser Run Quick Actions API reference for all available endpoints and parameters.
 external_link: /api/resources/browser_rendering/
 sidebar:
-  order: 15
+ order: 15
 products:
   - browser-run
 ---
diff --git a/src/content/docs/browser-run/reference/browser-close-reasons.mdx b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
index cfb411b73a356c1..3fe11accbc5a78a 100644
--- a/src/content/docs/browser-run/reference/browser-close-reasons.mdx
+++ b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
@@ -24,13 +24,13 @@ Browser Run sessions are billed based on [usage](/browser-run/pricing/). We do n
 
 ## Close reasons
 
-| Reason               | Description                                                                                                                                                                                                                                                                        |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Normal closure**   | Your code called `browser.close()` and the session ended normally. No action needed.                                                                                                                                                                                               |
-| **Browser idle**     | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
-| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks.                               |
-| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block.                                                    |
-| **Session evicted**  | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic.                                                                            |
+| Reason | Description |
+| --- | --- |
+| **Normal closure** | Your code called `browser.close()` and the session ended normally. No action needed. |
+| **Browser idle** | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
+| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks. |
+| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block. |
+| **Session evicted** | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic. |
 
 ## Handling unexpected closures
 
@@ -38,18 +38,18 @@ Sessions can close at any time due to infrastructure events, network issues, or
 
 ```js
 async function runBrowser(env) {
-	let browser;
-	try {
-		browser = await puppeteer.launch(env.MYBROWSER);
-		const page = await browser.newPage();
-		await page.goto("https://example.com");
-		// Your browser automation logic
-	} catch (error) {
-		console.error("Browser session ended unexpectedly:", error.message);
-		// Retry or return an error response
-	} finally {
-		await browser?.close();
-	}
+  let browser;
+  try {
+    browser = await puppeteer.launch(env.MYBROWSER);
+    const page = await browser.newPage();
+    await page.goto("https://example.com");
+    // Your browser automation logic
+  } catch (error) {
+    console.error("Browser session ended unexpectedly:", error.message);
+    // Retry or return an error response
+  } finally {
+    await browser?.close();
+  }
 }
 ```
 
@@ -57,13 +57,13 @@ For long-running or critical workflows, consider adding retry logic:
 
 ```js
 async function runWithRetry(env, maxRetries = 3) {
-	for (let attempt = 1; attempt <= maxRetries; attempt++) {
-		try {
-			return await runBrowser(env);
-		} catch (error) {
-			if (attempt === maxRetries) throw error;
-			console.log(`Attempt ${attempt} failed, retrying...`);
-		}
-	}
+  for (let attempt = 1; attempt <= maxRetries; attempt++) {
+    try {
+      return await runBrowser(env);
+    } catch (error) {
+      if (attempt === maxRetries) throw error;
+      console.log(`Attempt ${attempt} failed, retrying...`);
+    }
+  }
 }
 ```
diff --git a/src/content/docs/byoip/address-maps/setup.mdx b/src/content/docs/byoip/address-maps/setup.mdx
index 4ded8d833123a77..9e80f9aa794cc37 100644
--- a/src/content/docs/byoip/address-maps/setup.mdx
+++ b/src/content/docs/byoip/address-maps/setup.mdx
@@ -11,13 +11,7 @@ sidebar:
   label: Setup
 ---
 
-import {
-	GlossaryTooltip,
-	APIRequest,
-	DashButton,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { GlossaryTooltip, APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 Consider the sections below to learn how to set up address maps.
 
@@ -126,13 +120,13 @@ Default SNI for Spectrum can only be created via API using the [Create Address M
 Do not include any membership in your command. Your API command should resemble the following:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/address_maps"
-	method="POST"
-	json={{
-		description: "default_sni",
-		default_sni: "sni.example.com",
-		enabled: false,
-		ips: ["192.0.0.1"],
-		memberships: [],
+  path="/accounts/{account_id}/addressing/address_maps"
+  method="POST"
+  json={{
+		"description": "default_sni",
+		"default_sni": "sni.example.com",
+		"enabled": false,
+		"ips": ["192.0.0.1"],
+		"memberships": [],
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/byoip/changelog.mdx b/src/content/docs/byoip/changelog.mdx
index bee100a7b07c3bc..389731c7bfc427f 100644
--- a/src/content/docs/byoip/changelog.mdx
+++ b/src/content/docs/byoip/changelog.mdx
@@ -14,4 +14,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/byoip.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductReleaseNotes />
+<ProductReleaseNotes />
\ No newline at end of file
diff --git a/src/content/docs/byoip/concepts/index.mdx b/src/content/docs/byoip/concepts/index.mdx
index 7a7f4b5b8de1b6d..646653a0d44f0e6 100644
--- a/src/content/docs/byoip/concepts/index.mdx
+++ b/src/content/docs/byoip/concepts/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the topics below for more information about concepts related to BYOIP.
 
diff --git a/src/content/docs/byoip/concepts/prefix-delegations.mdx b/src/content/docs/byoip/concepts/prefix-delegations.mdx
index 2c7fa214ed734aa..65ddd820ea83124 100644
--- a/src/content/docs/byoip/concepts/prefix-delegations.mdx
+++ b/src/content/docs/byoip/concepts/prefix-delegations.mdx
@@ -10,6 +10,7 @@ sidebar:
 
 Prefix delegations allow a prefix owner (Account A) to grant another Cloudflare account (Account B) permission to use all or part of their BYOIP prefix. The original prefix remains managed by Account A, but Account B can use the delegated IPs with CDN services (including Cloudflare for SaaS) or Spectrum. Refer to [service bindings](/byoip/service-bindings/) for more information on the services an IP can be bound to.
 
+
 ## CDN
 
 CDN delegations allow you to use the IP(s) with [Address Maps](/byoip/address-maps/) or [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) customers.
diff --git a/src/content/docs/byoip/glossary.mdx b/src/content/docs/byoip/glossary.mdx
index 21eb58070060e3a..8b3f72c3e98e200 100644
--- a/src/content/docs/byoip/glossary.mdx
+++ b/src/content/docs/byoip/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 12
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's BYOIP documentation.
 
diff --git a/src/content/docs/byoip/route-leak-detection.mdx b/src/content/docs/byoip/route-leak-detection.mdx
index b42d00458f0abed..7b25fea18deee8c 100644
--- a/src/content/docs/byoip/route-leak-detection.mdx
+++ b/src/content/docs/byoip/route-leak-detection.mdx
@@ -6,9 +6,10 @@ products:
   - byoip
 sidebar:
   order: 8
+
 ---
 
-import { AvailableNotifications, DashButton } from "~/components";
+import { AvailableNotifications, DashButton } from "~/components"
 
 Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
 
diff --git a/src/content/docs/byoip/service-bindings/index.mdx b/src/content/docs/byoip/service-bindings/index.mdx
index 51ae83d822bc673..0078224d0428db2 100644
--- a/src/content/docs/byoip/service-bindings/index.mdx
+++ b/src/content/docs/byoip/service-bindings/index.mdx
@@ -79,5 +79,4 @@ When adding a service binding for a given IP address, it must be either a CDN se
 <DirectoryListing />
 
 [^1]: Layer 7 HTTP-based
-
-[^2]: Layer 4 or Layer 7 HTTP with custom ports
+[^2]: Layer 4 or Layer 7 HTTP with custom ports
\ No newline at end of file
diff --git a/src/content/docs/byoip/troubleshooting/index.mdx b/src/content/docs/byoip/troubleshooting/index.mdx
index b83821670151137..c3c66603d15744f 100644
--- a/src/content/docs/byoip/troubleshooting/index.mdx
+++ b/src/content/docs/byoip/troubleshooting/index.mdx
@@ -36,12 +36,13 @@ Instead, you can use Address Maps to set a default SNI for IPs on your account o
 
 When onboarding BYOIP prefixes via the API, you may encounter the following errors:
 
-| Error code                      | Meaning                                                                                                     | Resolution                                                                                                                                                                                                                                                                             |
-| ------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Error code | Meaning | Resolution |
+|---|---|---|
 | `prefix_not_valid_and_approved` | The prefix has not passed IRR validation, RPKI validation, and ownership verification (or manual approval). | Verify all three validation steps have completed. If one or more are failing, check prefix registration with your Regional Internet Registry (RIR) and your RPKI ROA configuration. If validation is passing but you are still seeing this error, contact support for manual approval. |
-| `incomplete_bgp_deployment`     | Cannot create a BGP prefix without a default edge service binding configured.                               | Configure a default edge service binding before creating BGP prefixes.                                                                                                                                                                                                                 |
-| `advertise_state_locked`        | Cannot create a BGP prefix — the default edge service binding is still deploying.                           | Wait for the edge service binding deployment to complete, then retry.                                                                                                                                                                                                                  |
+| `incomplete_bgp_deployment` | Cannot create a BGP prefix without a default edge service binding configured. | Configure a default edge service binding before creating BGP prefixes. |
+| `advertise_state_locked` | Cannot create a BGP prefix — the default edge service binding is still deploying. | Wait for the edge service binding deployment to complete, then retry. |
 
 :::note
 Self-serve BYOIP onboarding is not supported when BYOIP is used as a Magic Transit on-ramp configuration. For more information, refer to [Magic Transit with CDN](/byoip/service-bindings/magic-transit-with-cdn/).
 :::
+
diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
index 4e48745c1d36d41..5bd9e4060218ead 100644
--- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
+++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
@@ -105,7 +105,10 @@ For example:
 
 ### Operations
 
-<Render file="cache-reserve-operations" product="cache" />
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>
 
 ## Cache Reserve billing examples
 
@@ -149,10 +152,10 @@ Cache Reserve is designed for use with [Tiered Cache](/cache/how-to/tiered-cache
 ## Cache Reserve Analytics
 
 <Render
-	file="cache-reserve-analytics"
+  file="cache-reserve-analytics"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
diff --git a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
index e94802d8e09921e..22a7ef8c9ba65a7 100644
--- a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
@@ -4,9 +4,10 @@ description: Signal search engine crawlers when content changes with IndexNow.
 products:
   - cache
 title: Crawler Hints
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Crawler Hints uses Cloudflare cache signals to tell search engines when your content has likely changed, so they crawl your site at the right time instead of guessing.
 
@@ -40,6 +41,6 @@ After enabling Crawler Hints, Cloudflare will begin sending hints to search engi
 
 When enabled, Crawler Hints is a global setting for your entire website. You can stop a specific page from being indexed by either:
 
-- Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
-- Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
-- Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
+* Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
+* Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
+* Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
diff --git a/src/content/docs/cache/advanced-configuration/early-hints.mdx b/src/content/docs/cache/advanced-configuration/early-hints.mdx
index cc491452932a8a8..0dbc92752839ea9 100644
--- a/src/content/docs/cache/advanced-configuration/early-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/early-hints.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Preload assets with 103 Early Hints to speed up page loads.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 When a browser requests a page, the origin server takes time to prepare the full response. Early Hints uses this wait time to send the browser a preliminary `103` response containing `Link` headers that tell the browser which assets it will need. The browser can start loading those assets before the full response arrives, which speeds up page loads.
 
@@ -14,8 +15,10 @@ Early Hints is defined in [RFC 8297](https://httpwg.org/specs/rfc8297.html) as a
 
 :::note[Note]
 
+
 Early Hints is currently only supported over HTTP/2 and HTTP/3.
 
+
 :::
 
 For more information about Early Hints, refer to the [Cloudflare](https://blog.cloudflare.com/early-hints) and [Google Chrome](https://developer.chrome.com/en/blog/early-hints/) blogs.
@@ -37,14 +40,16 @@ For more information about Early Hints, refer to the [Cloudflare](https://blog.c
 
 Early Hints are only generated and cached:
 
-- For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
-- On 200, 301, or 302 response return codes
-- When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
+* For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
+* On 200, 301, or 302 response return codes
+* When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
 
 :::note
 
+
 Early Hints cache entries are keyed by request URI and ignore query strings.
 
+
 :::
 
 ## Emit Early Hints
@@ -55,7 +60,7 @@ Currently, only certain browser versions will take action to preload or preconne
 
 Additionally, keep the following in mind:
 
-- Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
-- Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
-- Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
-- You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
+* Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
+* Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
+* Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
+* You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
diff --git a/src/content/docs/cache/advanced-configuration/index.mdx b/src/content/docs/cache/advanced-configuration/index.mdx
index 12fa7c03f59e222..9efd5cc15381ed7 100644
--- a/src/content/docs/cache/advanced-configuration/index.mdx
+++ b/src/content/docs/cache/advanced-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
index 05e6363b11a6dad..0b41b69eb776303 100644
--- a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
+++ b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
@@ -9,14 +9,14 @@ tags:
   - WordPress
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 **Query String Sort** increases cache-hit rates by first sorting query strings into a consistent order before checking the Cloudflare cache.
 
 By default, Cloudflare’s cache treats resources as distinct if their URL query strings are in a different order. For instance, these resources are cached separately:
 
-- `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
-- `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
+* `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
+* `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
 
 Query String Sort changes this behavior. If two query strings exist with the same name, the URL is sorted by the parameter value. For example:
 
@@ -30,7 +30,7 @@ would be sorted to:
 
 <FeatureTable id="cache.query_string_sort" />
 
----
+***
 
 ## Enable Query String Sort
 
@@ -41,7 +41,7 @@ To enable Query String Sort:
 3. Go to **Caching** > **Configuration**.
 4. For **Enable Query String Sort**, switch the toggle to **On**.
 
----
+***
 
 ## Unexpected behavior with WordPress admin pages
 
@@ -49,17 +49,19 @@ When a site or an application requires exact query string ordering, enabling Que
 
 For example in the WordPress admin UI, you might notice any of the following behaviors:
 
-- No media appear in the Media Library
-- Inability to customize the site via **Appearance** > **Customize**
-- Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
-- Inability to edit menus in **Appearance** > **Menus**
+* No media appear in the Media Library
+* Inability to customize the site via **Appearance** > **Customize**
+* Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
+* Inability to edit menus in **Appearance** > **Menus**
 
 To understand why this happens, note that WordPress [concatenates JavaScript files](https://developer.wordpress.org/advanced-administration/wordpress/wp-config/#disable-javascript-concatenation) to speed up the administration interface. The way WordPress implements this involves multiple occurrences of `load[]` parameters in the query string, where the order of those parameters is crucial.
 
 :::note
 
+
 Note that more recent versions of WordPress may not experience this issue, as a patch has been implemented in WordPress since 2019. The patch can be found at [WordPress Core Trac Changeset 45456](https://core.trac.wordpress.org/changeset/45456).
 
+
 :::
 
 ### Identify the problem
@@ -98,15 +100,15 @@ For example, you might have an image resizing endpoint or a search form, where t
 
 To minimize problems, consider:
 
-- Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
-- Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
-- Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
+* Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
+* Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
+* Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
 
 To learn more about Cache Rules, visit [Cache Rules](/cache/how-to/cache-rules/).
 
----
+***
 
 ## Related resources
 
-- [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
-- [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
+* [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
+* [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
diff --git a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
index 4f0f14a99828213..8d6b138d7f117d2 100644
--- a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
+++ b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
@@ -42,8 +42,8 @@ In this example, you run an e-commerce site and want to display prices in the lo
    - **Operator:** `equals`
    - **Value:** `Canada`
 6. Under **Then...**
-   - for **Path**, select **Preserve**.
-   - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
+    - for **Path**, select **Preserve**.
+    - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
 7. Select **Save**.
 
 Now, requests from Canada to `/products/item` will be transformed to `/products/item?loc=ca` before reaching your origin or the cache, creating a distinct cache entry.
@@ -65,14 +65,14 @@ To enable this feature, create a _variants rule_ using the API. This rule maps f
 For example, the following API call tells Cloudflare that for `.jpeg` and `.jpg` files, your origin can serve `image/webp` and `image/avif` variants:
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp", "image/avif"],
-			jpg: ["image/webp", "image/avif"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp", "image/avif"],
+      jpg: ["image/webp", "image/avif"]
+    }
+  }}
 />
 
 After creating the rule, Cloudflare will create distinct cache entries for each image variant, improving performance for users with modern browsers.
@@ -100,27 +100,26 @@ In this example, you run an A/B test controlled by a cookie named `ab-test` (wit
 const CACHE_DURATION = 30 * 24 * 60 * 60; // 30 days
 
 export default {
-	async fetch(request) {
-		// Construct a new URL for the cache key based on the A/B cookie
-		const abCookie =
-			request.headers.get("Cookie")?.match(/ab-test=([^;]+)/)?.[1] || "control";
-		const url = new URL(request.url);
-		url.pathname = `/ab-test/${abCookie}${url.pathname}`;
-
-		const cacheKey = new Request(url, request);
-		const cache = caches.default;
-
-		let response = await cache.match(cacheKey);
-		if (!response) {
-			// If not in cache, fetch from origin
-			response = await fetch(request);
-			response = new Response(response.body, response);
-			response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
-			// Put the response into cache with the custom key
-			await cache.put(cacheKey, response.clone());
-		}
-		return response;
-	},
+  async fetch(request) {
+    // Construct a new URL for the cache key based on the A/B cookie
+    const abCookie = request.headers.get('Cookie')?.match(/ab-test=([^;]+)/)?.[1] || 'control';
+    const url = new URL(request.url);
+    url.pathname = `/ab-test/${abCookie}${url.pathname}`;
+
+    const cacheKey = new Request(url, request);
+    const cache = caches.default;
+
+    let response = await cache.match(cacheKey);
+    if (!response) {
+      // If not in cache, fetch from origin
+      response = await fetch(request);
+      response = new Response(response.body, response);
+      response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
+      // Put the response into cache with the custom key
+      await cache.put(cacheKey, response.clone());
+    }
+    return response;
+  },
 };
 ```
 
@@ -152,13 +151,13 @@ If your origin serves different content types (for example, `application/json` v
    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
-3. Enter rule name, such as `Vary by Accept Header`.
+3. Enter  rule name, such as `Vary by Accept Header`.
 4. Set the condition for the rule to apply (for example, a specific hostname or path).
 5. Under **Cache key**, select **Use custom key**.
 6. Select **Add new**.
-   - **Type**: `Header`
-   - **Name**: `Accept`
-   - **Value**: Add each `value`, or leave empty for all.
+    - **Type**: `Header`
+    - **Name**: `Accept`
+    - **Value**: Add each `value`, or leave empty for all.
 7. Select **Deploy**.
 
 This configuration creates separate cache entries based on the `Accept` header value, respecting your API's content negotiation.
@@ -177,28 +176,28 @@ This Worker detects whether a visitor is on a mobile or desktop device and creat
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		const userAgent = request.headers.get("User-Agent") || "";
-		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
+  async fetch(request, env, ctx) {
+    const userAgent = request.headers.get('User-Agent') || '';
+    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
 
-		// Create a new URL for the cache key that includes the device type
-		const url = new URL(request.url);
-		url.pathname = `/${deviceType}${url.pathname}`;
+    // Create a new URL for the cache key that includes the device type
+    const url = new URL(request.url);
+    url.pathname = `/${deviceType}${url.pathname}`;
 
-		const cacheKey = new Request(url, request);
-		const cache = caches.default;
+    const cacheKey = new Request(url, request);
+    const cache = caches.default;
 
-		let response = await cache.match(cacheKey);
+    let response = await cache.match(cacheKey);
 
-		if (!response) {
-			console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
-			response = await fetch(request);
-			let responseToCache = response.clone();
-			ctx.waitUntil(cache.put(cacheKey, responseToCache));
-		}
+    if (!response) {
+      console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
+      response = await fetch(request);
+      let responseToCache = response.clone();
+      ctx.waitUntil(cache.put(cacheKey, responseToCache));
+    }
 
-		return response;
-	},
+    return response;
+  },
 };
 ```
 
@@ -212,28 +211,28 @@ This Worker detects if a visitor is on a mobile device or a desktop and creates
 
 ```js
 export default {
-	async fetch(request) {
-		// 1. Determine the device type from the User-Agent header
-		const userAgent = request.headers.get("User-Agent") || "";
-		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
-
-		// 2. Create a custom cache key by appending the device type to the URL
-		const customCacheKey = `${request.url}-${deviceType}`;
-
-		// 3. Fetch the response. Cloudflare's cache automatically uses the
-		//    customCacheKey for cache operations (match, put).
-		const response = await fetch(request, {
-			cf: {
-				cacheKey: customCacheKey,
-			},
-		});
-
-		// Optionally, you can modify the response before returning it
-		// For example, add a header to indicate which cache key was used
-		const newResponse = new Response(response.body, response);
-		newResponse.headers.set("X-Cache-Key", customCacheKey);
-		return newResponse;
-	},
+  async fetch(request) {
+    // 1. Determine the device type from the User-Agent header
+    const userAgent = request.headers.get('User-Agent') || '';
+    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
+
+    // 2. Create a custom cache key by appending the device type to the URL
+    const customCacheKey = `${request.url}-${deviceType}`;
+
+    // 3. Fetch the response. Cloudflare's cache automatically uses the
+    //    customCacheKey for cache operations (match, put).
+    const response = await fetch(request, {
+      cf: {
+        cacheKey: customCacheKey,
+      },
+    });
+
+    // Optionally, you can modify the response before returning it
+    // For example, add a header to indicate which cache key was used
+    const newResponse = new Response(response.body, response);
+    newResponse.headers.set("X-Cache-Key", customCacheKey);
+    return newResponse;
+  },
 };
 ```
 
@@ -257,11 +256,11 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 3. Enter a name, such as `Vary by RSC Header`.
 4. In **If incoming requests match**, select **Custom filter expression**.
 5. Under **When incoming requests match**, manually edit the expression so that it checks for the presence of the `RSC` header:
-   - `has_key(http.request.headers, "rsc")`
+    - `has_key(http.request.headers, "rsc")`
 
 6. Under **Then**:
-   - For **Path**, select **Preserve**.
-   - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
+    - For **Path**, select **Preserve**.
+    - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
 
 7. Select **Save**.
 
@@ -270,7 +269,8 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 Alternatively, use [Snippets](/rules/snippets/) or [Custom Cache Keys](/cache/how-to/cache-keys) to add the `RSC` header directly to the cache key without modifying the visible URL. This provides a cleaner URL but requires more advanced configuration.
 
 :::note[Availability]
-
 - Snippets: Pro, Business, Enterprise
 - Custom Cache Keys: Enterprise only
-  :::
+:::
+
+
diff --git a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
index 1209ddf6440e3ee..ab7ed953aa09229 100644
--- a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
+++ b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Serve images in the best format for each visitor browser.
 products:
   - cache
+
 ---
 
-import { Details, FeatureTable, APIRequest } from "~/components";
+import { Details, FeatureTable, APIRequest } from "~/components"
 
 The `Vary` HTTP response header tells Cloudflare that an origin can serve different versions of the same resource depending on the request headers. For images, this allows your origin to serve modern formats like WebP or AVIF to browsers that support them, while continuing to serve JPEG or PNG to others.
 
@@ -24,19 +25,20 @@ Vary for images is available for Pro, Business, and Enterprise customers.
 
 You can use vary for images on the file extensions below if the origin server sends the `Vary: Accept` response header. If the origin server sends `Vary: Accept` but does not serve the set variant, the response is not cached and displays `BYPASS` in the cache status in the response header. Additionally, the list of variant types the origin serves for each extension must be configured so that Cloudflare decides which variant to serve without contacting the origin server.
 
+
 <Details header="File extensions enabled for varying">
-	<ul>
-		<li>.avif</li>
-		<li>.bmp</li>
-		<li>.gif</li>
-		<li>.jpg</li>
-		<li>.jpeg</li>
-		<li>.jp2</li>
-		<li>.png</li>
-		<li>.tif</li>
-		<li>.tiff</li>
-		<li>.webp</li>
-	</ul>
+  <ul>
+    <li>.avif</li>
+    <li>.bmp</li>
+    <li>.gif</li>
+    <li>.jpg</li>
+    <li>.jpeg</li>
+    <li>.jp2</li>
+    <li>.png</li>
+    <li>.tif</li>
+    <li>.tiff</li>
+    <li>.webp</li>
+  </ul>
 </Details>
 
 ## Enable vary for images
@@ -46,40 +48,46 @@ Vary for Images is enabled through Cloudflare's API by creating a variants rule.
 ### Create a variants rule
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp", "image/avif"],
-			jpg: ["image/webp", "image/avif"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp", "image/avif"],
+      jpg: ["image/webp", "image/avif"]
+    }
+  }}
 />
 
 ### Modify to only allow WebP variants
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp"],
-			jpg: ["image/webp"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp"],
+      jpg: ["image/webp"]
+    }
+  }}
 />
 
 ### Delete the rule
 
-<APIRequest path="/zones/{zone_id}/cache/variants" method="DELETE" />
+<APIRequest
+  path="/zones/{zone_id}/cache/variants"
+  method="DELETE"
+/>
 
 ### Get the rule
 
-<APIRequest path="/zones/{zone_id}/cache/variants" method="GET" />
+<APIRequest
+  path="/zones/{zone_id}/cache/variants"
+  method="GET"
+/>
 
 To learn more about purging varied images, refer to [Purge varied images](/cache/how-to/purge-cache/purge-varied-images/).
 
 ## Limitations
 
-- For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
-- Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
+* For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
+* Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
diff --git a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
index f115a63a6b91c56..3978e79c7e9bb20 100644
--- a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
+++ b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
@@ -19,22 +19,22 @@ A Content Delivery Network (CDN) like Cloudflare relies on cache keys to compare
 
 To deepen your understanding of the risks and vulnerabilities associated with cache poisoning, consult the following resources:
 
-- [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
-- [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
+* [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
+* [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
 
 ## Only cache files that are truly static
 
 Review the caching configuration for your origin web server and ensure you are caching files that are static and do not depend on user input in any way. To learn more about Cloudflare caching, review:
 
-- [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
-- [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
+* [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
+* [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
 
 ## Do not trust data in HTTP headers
 
 Attackers can exploit HTTP headers to inject malicious content into cached responses. For example, if your application reflects an untrusted header value in the response body, an attacker could use this to perform cross-site scripting (XSS) through the cache. To reduce this risk:
 
-- Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
-- Do not include untrusted header values in your response body.
+* Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
+* Do not include untrusted header values in your response body.
 
 ## Do not trust GET request bodies
 
@@ -44,6 +44,6 @@ Cloudflare caches contents of GET request bodies, but they are not included in t
 
 To keep informed about Internet security threats, Cloudflare recommends that you monitor web security advisories on a regular basis. Some of the more popular advisories include:
 
-- [Drupal Security Advisories](https://www.drupal.org/security)
-- [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
-- [Laminas Security Advisories](https://getlaminas.org/security/advisories)
+* [Drupal Security Advisories](https://www.drupal.org/security)
+* [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
+* [Laminas Security Advisories](https://getlaminas.org/security/advisories)
diff --git a/src/content/docs/cache/cache-security/cache-deception-armor.mdx b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
index 2b41dc71ac0ea52..a008458a9255072 100644
--- a/src/content/docs/cache/cache-security/cache-deception-armor.mdx
+++ b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
@@ -24,9 +24,9 @@ In the newsfeed example above, if `http://www.example.com/newsfeed` is a script
 
 ### Exceptions
 
-- If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
-- Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
-- Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
+* If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
+* Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
+* Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
 
 ## Enable Cache Deception Armor
 
diff --git a/src/content/docs/cache/cache-security/cors.mdx b/src/content/docs/cache/cache-security/cors.mdx
index 3f70fe69412f798..5f1e357e312c2fe 100644
--- a/src/content/docs/cache/cache-security/cors.mdx
+++ b/src/content/docs/cache/cache-security/cors.mdx
@@ -12,8 +12,8 @@ A cross-origin request occurs when a webpage on one origin (for example, `a.exam
 
 Cloudflare supports CORS by:
 
-- Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
-- Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
+* Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
+* Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
 
 The `Access-Control-Allow-Origin` header lets a server specify rules for sharing its resources with external origins. A server may respond with different `Access-Control-Allow-Origin` values depending on the `Origin` header in the request. These headers are often present on [cacheable content](/cache/concepts/default-cache-behavior/).
 
@@ -21,9 +21,9 @@ The `Access-Control-Allow-Origin` header lets a server specify rules for sharing
 
 If you add or change CORS configuration at your origin web server, purging the Cloudflare cache by URL does not update the CORS headers. Force Cloudflare to retrieve the new CORS headers via one of the following options:
 
-- Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
-- Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
-- Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
+* Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
+* Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
+* Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
 
 ## Add or change CORS headers on Cloudflare
 
@@ -32,3 +32,4 @@ You can use one of following methods to set CORS headers using Cloudflare produc
 - Use a [Worker](/workers/): Refer to [CORS header proxy](/workers/examples/cors-header-proxy/) for an example.
 - Configure a [Snippet](/rules/snippets/): Refer to [Define CORS headers](/rules/snippets/examples/define-cors-headers/) for an example.
 - Use [Transform Rules](/rules/transform/): Refer to [Add a wildcard CORS response header](/rules/transform/examples/add-cors-header/) for an example.
+
diff --git a/src/content/docs/cache/cache-security/index.mdx b/src/content/docs/cache/cache-security/index.mdx
index 3287619c54fa92c..6f753ca961b67d0 100644
--- a/src/content/docs/cache/cache-security/index.mdx
+++ b/src/content/docs/cache/cache-security/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following content to learn more about cache security.
 
diff --git a/src/content/docs/cache/concepts/cache-behavior.mdx b/src/content/docs/cache/concepts/cache-behavior.mdx
index ca4b43ee981b90a..212cd5cec8fe30f 100644
--- a/src/content/docs/cache/concepts/cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/cache-behavior.mdx
@@ -11,8 +11,8 @@ tags:
 
 This page describes how Cloudflare's cache system behaves in interaction with:
 
-- `HEAD` requests
-- `Set-Cookie` response headers
+* `HEAD` requests
+* `Set-Cookie` response headers
 
 ## Interaction of `HEAD` requests with Cache
 
@@ -24,8 +24,8 @@ When you make a `HEAD` request for a cacheable resource and Cloudflare does not
 
 For non-cacheable requests, `Set-Cookie` is always preserved. For cacheable requests, there are three possible behaviors:
 
-- `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
+* `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
 
-- `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
+* `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
 
-- `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
+* `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
diff --git a/src/content/docs/cache/concepts/cache-responses.mdx b/src/content/docs/cache/concepts/cache-responses.mdx
index 20f1007625c6956..a1f3935e1f26ba9 100644
--- a/src/content/docs/cache/concepts/cache-responses.mdx
+++ b/src/content/docs/cache/concepts/cache-responses.mdx
@@ -7,6 +7,7 @@ products:
 head:
   - tag: title
     content: Cloudflare cache responses
+
 ---
 
 The `CF-Cache-Status` header output indicates whether a resource is cached or not. To investigate cache responses returned by this header, use services like [Redbot](https://redbot.org/), [webpagetest.org](http://www.webpagetest.org/), or a visual tool like [Cloudflare Optics plugin](https://chromewebstore.google.com/detail/cloudflare-optics/mdjgbjnbdnhneejmmaabmccfehigbjbe).
@@ -31,13 +32,13 @@ The resource was not found in Cloudflare's cache and was served from the origin
 
 Cloudflare generated a response that denotes the asset is not eligible for caching. This may have happened because:
 
-- A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
+* A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
 
-- A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
+* A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
 
-- A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
+* A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
 
-- A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
+* A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
 
 ## EXPIRED
 
diff --git a/src/content/docs/cache/concepts/cdn-cache-control.mdx b/src/content/docs/cache/concepts/cdn-cache-control.mdx
index ae3401ebbb3fa3b..81e86ba54273c84 100644
--- a/src/content/docs/cache/concepts/cdn-cache-control.mdx
+++ b/src/content/docs/cache/concepts/cdn-cache-control.mdx
@@ -18,11 +18,11 @@ If a [Cache Response Rule](/cache/how-to/cache-response-rules/) sets `Cache-Cont
 
 When no Cache Response Rule applies, an origin can:
 
-- Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
+* Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
 
-- Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
+* Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
 
-- Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
+* Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
 
 Additionally, surrogates will not honor `Cache-Control` headers in the response from an origin. For example, if the `Surrogate-Control` header is present within the response, Cloudflare ignores any `Cache-Control` directives, even if the `Surrogate-Control` header does not contain directives.
 
@@ -52,61 +52,61 @@ Use `CDN-Cache-Control` when you want to manage cached asset’s TTLs separately
 
 Headers:
 
-- `Cache-Control: max-age=14400, s-maxage=84000`
-- `Cloudflare-CDN-Cache-Control: max-age=24400`
-- `CDN-Cache-Control: max-age=18000`
+* `Cache-Control: max-age=14400, s-maxage=84000`
+* `Cloudflare-CDN-Cache-Control: max-age=24400`
+* `CDN-Cache-Control: max-age=18000`
 
 Cache behavior:
 
 <table>
-	<tbody>
-		<th colspan="5" rowspan="1">
-			Caches
-		</th>
-		<th colspan="5" rowspan="1">
-			Cache TTL (seconds)
-		</th>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Origin Server Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				14400
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Network Shared Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				84000
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Cloudflare Edge
-			</td>
-			<td colspan="5" rowspan="1">
-				24400
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Other CDNs
-			</td>
-			<td colspan="5" rowspan="1">
-				18000
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Browser Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				14400
-			</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <th colspan="5" rowspan="1">
+      Caches
+    </th>
+    <th colspan="5" rowspan="1">
+      Cache TTL (seconds)
+    </th>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Origin Server Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        14400
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Network Shared Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        84000
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Cloudflare Edge
+      </td>
+      <td colspan="5" rowspan="1">
+        24400
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Other CDNs
+      </td>
+      <td colspan="5" rowspan="1">
+        18000
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Browser Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        14400
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ### Specify when to serve stale content
@@ -115,43 +115,43 @@ Use `CDN-Cache-Control` headers in conjunction with `Cache-Control` headers to s
 
 Headers:
 
-- `Cache-Control: stale-if-error=400`
-- `Cloudflare-CDN-Cache-Control: stale-if-error=60`
-- `CDN-Cache-Control: stale-if-error=200`
+* `Cache-Control: stale-if-error=400`
+* `Cloudflare-CDN-Cache-Control: stale-if-error=60`
+* `CDN-Cache-Control: stale-if-error=200`
 
 Behavior in response to [5XX error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/):
 
 <table>
-	<tbody>
-		<th colspan="5" rowspan="1">
-			Caches
-		</th>
-		<th colspan="5" rowspan="1">
-			Stale served (seconds) in response to error
-		</th>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Origin Cache Layer/Network Cache/Browser Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				400 (if it assumes the directive applies)
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Cloudflare Edge
-			</td>
-			<td colspan="5" rowspan="1">
-				60
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Other CDN
-			</td>
-			<td colspan="5" rowspan="1">
-				200
-			</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <th colspan="5" rowspan="1">
+      Caches
+    </th>
+    <th colspan="5" rowspan="1">
+      Stale served (seconds) in response to error
+    </th>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Origin Cache Layer/Network Cache/Browser Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        400 (if it assumes the directive applies)
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Cloudflare Edge
+      </td>
+      <td colspan="5" rowspan="1">
+        60
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Other CDN
+      </td>
+      <td colspan="5" rowspan="1">
+        200
+      </td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/docs/cache/concepts/customize-cache.mdx b/src/content/docs/cache/concepts/customize-cache.mdx
index 1a9047525da3655..c4f49110ea13c65 100644
--- a/src/content/docs/cache/concepts/customize-cache.mdx
+++ b/src/content/docs/cache/concepts/customize-cache.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: Methods for customizing cache behavior with rules, Workers, and headers.
 products:
   - cache
+
 ---
 
 Some possible combinations of origin web server settings and Cloudflare [Cache Rules](/cache/how-to/cache-rules/) include:
@@ -12,21 +13,21 @@ Some possible combinations of origin web server settings and Cloudflare [Cache R
 
 For example, create a `/static/` subdirectory at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
-- Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
+* Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
 
 ## Append a unique file extension to static pages
 
 For example, create a `.shtml` file extension for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
-- Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
+* Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
 
 ## Add a query string to a resource’s URL to mark the content as static
 
 For example, add a `static=true` query string for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
-- Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
+* Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
 
 Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a Cache-Control header of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.
diff --git a/src/content/docs/cache/concepts/default-cache-behavior.mdx b/src/content/docs/cache/concepts/default-cache-behavior.mdx
index 6749f5b82907cf1..0f9a375df7316c6 100644
--- a/src/content/docs/cache/concepts/default-cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/default-cache-behavior.mdx
@@ -7,24 +7,20 @@ products:
 head:
   - tag: title
     content: Default Cache Behavior
+
 ---
 
-import {
-	FeatureTable,
-	GlossaryTooltip,
-	Render,
-	DashButton,
-} from "~/components";
+import { FeatureTable, GlossaryTooltip, Render, DashButton } from "~/components"
 
 Cloudflare respects the origin web server’s cache headers in the following order unless an [Edge Cache TTL cache rule](/cache/how-to/cache-rules/settings/#edge-ttl) overrides the headers. Refer to the [Edge TTL](/cache/how-to/configure-cache-status-code/#edge-ttl) section for details on default TTL behavior.
 
-- Cloudflare **does not** cache the resource when:
-  - The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
-  - The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
-  - The HTTP request method is anything other than a `GET`.
-- Cloudflare **does** cache the resource when:
-  - The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
-  - The `Expires` header is set to a future date.
+* Cloudflare **does not** cache the resource when:
+  * The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
+  * The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
+  * The HTTP request method is anything other than a `GET`.
+* Cloudflare **does** cache the resource when:
+  * The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
+  * The `Expires` header is set to a future date.
 
 :::note
 Cloudflare does cache the resource even if there is no `Cache-Control` header based on [status codes](/cache/how-to/configure-cache-status-code/#edge-ttl).
@@ -40,8 +36,8 @@ When [Origin Cache Control](/cache/concepts/cache-control/) is enabled on an Ent
 
 Clients can send range requests to be served from the cache using the `Range` header. Note that:
 
-- If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
-- If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
+ - If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
+ - If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
 
 ## Request collapsing
 
@@ -68,10 +64,10 @@ Cloudflare only caches based on file extension and not by MIME type. The Cloudfl
 To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/) to create a rule to cache everything.
 
 <Render
-	file="edge-ttl"
+  file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
@@ -79,14 +75,14 @@ To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/)
 
 Cloudflare’s CDN provides several cache customization options:
 
-- Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
+* Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
 
-<DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+ <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
-- Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
-- Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
+* Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
+* Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
 
-<DashButton url="/?to=/:account/:zone/caching/configuration" />
+ <DashButton url="/?to=/:account/:zone/caching/configuration" />
 
 ### Upload limits
 
@@ -100,8 +96,8 @@ If you require a larger upload, you can group requests into smaller chunks, uplo
 
 Cloudflare cacheable file limits:
 
-- Free, Pro and Business customers have a limit of 512 MB.
-- For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
+* Free, Pro and Business customers have a limit of 512 MB.
+* For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
 
 ## When does Cloudflare cache successfully?
 
diff --git a/src/content/docs/cache/concepts/index.mdx b/src/content/docs/cache/concepts/index.mdx
index c39bdbe713dbf77..9d7aa540158df71 100644
--- a/src/content/docs/cache/concepts/index.mdx
+++ b/src/content/docs/cache/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+    
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts and components of Cloudflare Cache.
 
diff --git a/src/content/docs/cache/concepts/retention-vs-freshness.mdx b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
index 86ee2ef5d7736c5..1148870b16f91ca 100644
--- a/src/content/docs/cache/concepts/retention-vs-freshness.mdx
+++ b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: How cache retention and TTL freshness differ in Cloudflare.
 products:
   - cache
+
 ---
 
 In the context of Cloudflare CDN (Content Delivery Network), retention and freshness refer to two separate but related concepts. For an object in cache, freshness is how long it should be considered valid without consulting its source, while retention refers to how long it stays in cache before being removed.
@@ -18,8 +19,8 @@ Cloudflare uses a Least Recently Used (LRU) algorithm to decide which objects to
 
 Freshness, also known as Time to Live (TTL), determines how long a cache can use an object without checking with the origin again. For example, if an object has a TTL of five minutes, the cache serves it directly for five minutes after first receiving it. After five minutes, Cloudflare must check with the origin to confirm the object is still valid before serving it again. There are a few ways to configure TTLs for resources served through Cloudflare's CDN:
 
-- Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
+* Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
 
-- Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
+* Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
 
 If an object in cache is no longer fresh, Cloudflare revalidates it with the origin. When [`stale-while-revalidate`](/cache/concepts/cache-control/#revalidation) is set, revalidation happens asynchronously at expiry — visitors continue to be served from cache while Cloudflare fetches a fresh copy in the background. Without this directive, incoming requests wait for the origin to respond before receiving content. The origin can either confirm the cached object is still valid (refreshing its TTL) or return a new version to replace it. Refer to [Revalidation](/cache/concepts/revalidation/) for details.
diff --git a/src/content/docs/cache/concepts/revalidation.mdx b/src/content/docs/cache/concepts/revalidation.mdx
index f289dc2c55c0ce6..be6792de1f48057 100644
--- a/src/content/docs/cache/concepts/revalidation.mdx
+++ b/src/content/docs/cache/concepts/revalidation.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: How Cloudflare revalidates stale cached content with your origin.
 products:
   - cache
+
 ---
 
 ## Stale-while-revalidate
diff --git a/src/content/docs/cache/get-started.mdx b/src/content/docs/cache/get-started.mdx
index 485414c218db17e..ab1be9257230ee3 100644
--- a/src/content/docs/cache/get-started.mdx
+++ b/src/content/docs/cache/get-started.mdx
@@ -13,7 +13,7 @@ head:
     content: Get started with Cache
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare speeds up your website by caching content across globally distributed data centers.
 
@@ -21,12 +21,12 @@ Content can be static or dynamic. Static content — such as images, CSS, and Ja
 
 Cloudflare caches static content based on the following factors:
 
-- [Caching levels](/cache/how-to/set-caching-levels/)
-- [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
-- Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
-- [Origin cache-control headers](/cache/concepts/cache-control/)
-- Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
-- Cache rules that bypass cache on cookie
+* [Caching levels](/cache/how-to/set-caching-levels/)
+* [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+* Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
+* [Origin cache-control headers](/cache/concepts/cache-control/)
+* Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
+* Cache rules that bypass cache on cookie
 
 Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, or content hosted on [DNS-only (unproxied)](/dns/proxy-status/) DNS records.
 
@@ -34,35 +34,35 @@ Cloudflare only caches resources within the Cloudflare data center that serve th
 
 Discover the benefits of caching with Cloudflare's CDN and understand the default cache behavior.
 
-- [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
-- [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
-- [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+* [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
+* [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
+* [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
 
 ## Make more resources cacheable
 
 Configure your settings to cache static HTML or cache anonymous page views of dynamic content.
 
-- [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
-- [Specify which resources to cache](/cache/concepts/customize-cache/)
-- [Understand Origin Cache Control](/cache/concepts/cache-control/)
-- [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
+* [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
+* [Specify which resources to cache](/cache/concepts/customize-cache/)
+* [Understand Origin Cache Control](/cache/concepts/cache-control/)
+* [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
 
 ## Improve cache HIT rates
 
 Include or exclude query strings, optimize cache keys, or enable [Tiered Cache](/cache/how-to/tiered-cache/) to improve HIT rates and reduce traffic to your origin.
 
-- [Choose a cache level](/cache/how-to/set-caching-levels/)
-- [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
-- [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
-- [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
+* [Choose a cache level](/cache/how-to/set-caching-levels/)
+* [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
+* [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
+* [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
 
 ## Secure your cache configuration
 
 Control resources a client is allowed to load and set access permissions to allow different origins to access your origin's resources. Protect your site from web cache deception attacks while still caching static assets.
 
-- [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
-- [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
-- [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
+* [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
+* [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
+* [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
 
 ## Features that alter cached content
 
@@ -70,16 +70,16 @@ Some Cloudflare features modify your HTML or cached objects at the edge to enabl
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. Cloudflare removes the changes when you disable the feature and purge the cache.
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. The changes are removed if the feature is disabled and the cache is purged.
 
-- [Rocket Loader](/speed/optimization/content/rocket-loader/)
-- [Polish](/images/polish/)
-- [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
-- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
-- [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
+* [Rocket Loader](/speed/optimization/content/rocket-loader/)
+* [Polish](/images/polish/)
+* [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
+* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
+* [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
 
 ## Troubleshoot
 
 Resolve common caching concerns.
 
-- [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
-- [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
-- [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
+* [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
+* [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
+* [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
diff --git a/src/content/docs/cache/glossary.mdx b/src/content/docs/cache/glossary.mdx
index ae52887a0324745..93414f59d8d1137 100644
--- a/src/content/docs/cache/glossary.mdx
+++ b/src/content/docs/cache/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Cache documentation.
 products:
   - cache
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Cache documentation.
 
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
index 26540e1b1bc9dfc..5e0cffeecb60098 100644
--- a/src/content/docs/cache/how-to/always-online.mdx
+++ b/src/content/docs/cache/how-to/always-online.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Serve cached pages when your origin server is unavailable.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Cloudflare’s Always Online feature is now integrated with the [Internet Archive](https://archive.org/) so that visitors can access a portion of your website even when your origin server is unreachable and a Cloudflare-cached version is unavailable. When your origin is unreachable, Always Online checks Cloudflare’s cache for a stale or expired version of your website. If a version does not exist, Cloudflare goes to the Internet Archive to fetch and serve static portions of your website.
 
@@ -45,8 +46,10 @@ Here is how to enable Always Online in the dashboard:
 
 :::note[Note]
 
+
 When turning on Always Online, you are also enabling the Internet Archive integration.
 
+
 :::
 
 Refer to [Always Online](/cache/troubleshooting/always-online/) for best practices, limitations, and FAQs.
diff --git a/src/content/docs/cache/how-to/cache-keys.mdx b/src/content/docs/cache/how-to/cache-keys.mdx
index 8afbd280f376234..59b3e1e4cd98538 100644
--- a/src/content/docs/cache/how-to/cache-keys.mdx
+++ b/src/content/docs/cache/how-to/cache-keys.mdx
@@ -14,16 +14,16 @@ head:
     content: Cache Keys
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.
 
 A default cache key includes:
 
 1. Full URL:
-   - scheme - could be HTTP or HTTPS.
-   - host - for example, `www.cloudflare.com`
-   - URI with query string - for example, `/logo.jpg?utm_source=newsletter`
+   * scheme - could be HTTP or HTTPS.
+   * host - for example, `www.cloudflare.com`
+   * URI with query string - for example, `/logo.jpg?utm_source=newsletter`
 2. Origin header sent by client (for CORS support).
 3. `x-http-method-override`, `x-http-method`, and `x-method-override` headers.
 4. `x-forwarded-host`, `x-host`, `x-forwarded-scheme` (unless http or https), `x-original-url`, `x-rewrite-url`, and `forwarded` headers.
@@ -51,8 +51,8 @@ When [URL normalization](/rules/normalization/) is enabled, we recommend also en
 
 There are a couple of common reasons to change the Cache Key Template. You might change the Cache Key Template to:
 
-- Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
-- Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
+* Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
+* Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
 
 ### Impact of SSL settings on Cache behavior
 
@@ -90,9 +90,9 @@ If you include the query string foo in a URL like `https://www.example.com/?foo=
 
 #### Usage notes
 
-- To include all query string parameters (the default behavior), use include: `"\*"`
-- To ignore query strings, use exclude: `"\*"`
-- To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
+* To include all query string parameters (the default behavior), use include: `"\*"`
+* To ignore query strings, use exclude: `"\*"`
+* To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
 
 ### Headers
 
@@ -102,13 +102,13 @@ When you include a header, the header value is included in the Cache Key. For ex
 
 In the **Include headers and selected values** section, you can add header names and their values to the cache key. For custom headers, values are optional, but for the following restricted headers, you must include one to 10 specific values:
 
-- `accept`
-- `accept-charset`
-- `accept-encoding`
-- `accept-datetime`
-- `accept-language`
-- `referer`
-- `user-agent`
+  * `accept`
+  * `accept-charset`
+  * `accept-encoding`
+  * `accept-datetime`
+  * `accept-language`
+  * `referer`
+  * `user-agent`
 
 To check for the presence of a header without including its actual value, use the **Check presence of** option.
 
@@ -116,28 +116,28 @@ Currently, you can only exclude the `Origin` header. The `Origin` header is alwa
 
 Additionally, you cannot include the following headers:
 
-- Headers that re-implement cache or proxy features
-  - `connection`
-  - `content-length`
-  - `cache-control`
-  - `if-match`
-  - `if-modified-since`
-  - `if-none-match`
-  - `if-unmodified-since`
-  - `range`
-  - `upgrade`
-- Headers that are covered by other Cache Key features
-  - `cookie`
-  - `host`
-- Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
-- Headers that are already included in the custom Cache Key template, for example, `origin`
+* Headers that re-implement cache or proxy features
+  * `connection`
+  * `content-length`
+  * `cache-control`
+  * `if-match`
+  * `if-modified-since`
+  * `if-none-match`
+  * `if-unmodified-since`
+  * `range`
+  * `upgrade`
+* Headers that are covered by other Cache Key features
+  * `cookie`
+  * `host`
+* Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
+* Headers that are already included in the custom Cache Key template, for example, `origin`
 
 ### Host
 
 Host determines which host header to include in the Cache Key.
 
-- If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
-- If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
+* If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
+* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
 
 ### Cookie
 
@@ -151,9 +151,9 @@ You cannot include cookies specific to Cloudflare. Cloudflare cookies are prefix
 
 User feature fields add features about the end-user (client) into the Cache Key.
 
-- `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
-- `geo` includes the client’s country, derived from the IP address
-- `lang` includes the first language code contained in the `Accept-Language` header sent by the client
+* `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
+* `geo` includes the client’s country, derived from the IP address
+* `lang` includes the first language code contained in the `Accept-Language` header sent by the client
 
 ## Availability
 
diff --git a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
index 7c75c81a407e301..f8032d4bd1be12e 100644
--- a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
+++ b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
@@ -30,6 +30,7 @@ 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 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:
@@ -42,8 +43,7 @@ import { Render, DashButton } from "~/components";
    - **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**.
 
-<Render file="rules-creation-dash-dns-popup" product="rules" />
+   <Render file="rules-creation-dash-dns-popup" product="rules" />
diff --git a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
index 24434a23533ec9f..ba3e5a14e0342aa 100644
--- a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: false
 pcx_content_type: navigation
 description: Example cache rule configurations for common use cases.
@@ -7,9 +8,10 @@ products:
 title: Examples
 sidebar:
   order: 8
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In the following sections, you can find common cache rules examples.
 
diff --git a/src/content/docs/cache/how-to/cache-rules/order.mdx b/src/content/docs/cache/how-to/cache-rules/order.mdx
index 5810d731d8608f8..40377bc15fa1145 100644
--- a/src/content/docs/cache/how-to/cache-rules/order.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/order.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Order and priority
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cache rules affect requests differently from Page Rules. This is how they are applied:
 
diff --git a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
index b1875b3767c20c3..6541177a91b6aa8 100644
--- a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
@@ -13,7 +13,7 @@ head:
     content: Migration from Page Rules
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 If you are migrating from Page Rules, there is a behavior change between Page Rules and Cache Rules.
 
@@ -64,8 +64,10 @@ If you prefer, you can select **Edit expression** and paste the following expres
 
 :::note[Note]
 
+
 Remember to create the rules in the specified order: first, the `bypass everything` rule, and then the `cache all default cacheable file extensions` rule.
 
 ![Rules order](~/assets/images/cache/rule-order.png)
 
+
 :::
diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
index c30d541d4d833c7..2c71df51f6c0e94 100644
--- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx
+++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
@@ -8,7 +8,7 @@ tags:
   - REST API
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin.
 
@@ -19,10 +19,10 @@ Setting cache TTL based on response status overrides the [default cache behavior
 The maximum caching limit for Free, Pro, and Business customers is 512 MB per file, and the maximum caching limit for Enterprise customers is 5 GB per file. If you need to raise the limits, contact your Customer Success Manager.
 
 <Render
-	file="edge-ttl"
+  file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
@@ -79,9 +79,9 @@ curl --request PUT \
 
 Provide a JSON object containing status codes and their corresponding TTLs. Each key-value pair in the cache TTL by status cache rule has the following syntax:
 
-- `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
-- `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
-- `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
+* `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
+* `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
+* `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
 
 ## Set cache TTL by response status via a Cloudflare Worker
 
@@ -98,4 +98,4 @@ The **cacheTtlByStatus** option is a version of the **cacheTtl** feature that de
 
 For example, if a user specifies a TTL of one hour for status `200` and 0 seconds (cache and always revalidate) for status `304`, the asset will be cached for 1 hour. After it expires, we revalidate with the origin. If the origin returns a `304`, each subsequent request will trigger revalidation. If the origin continues to return `304`, this cycle will persist.
 
-This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
+This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
\ No newline at end of file
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
index c26df5fd963f037..9bd8eb61f1eeb6f 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Configure edge and browser cache TTL for your resources.
 products:
   - cache
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 ## Edge Cache TTL
 
@@ -20,16 +21,17 @@ For more information on how to set up Edge Cache TTL, refer to [Cache rules](/ca
 
 The Browser Cache TTL sets the expiration for resources cached in a visitor’s browser. By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers but overrides those headers if:
 
-- The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
-- The origin web server does not send a `Cache-Control` or an `Expires` header.
+* The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
+* The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a cache rule, Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
 :::note[Note]
 
-- Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
-- If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
-- Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.
+
+* Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
+* If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
+* Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser. 
   :::
 
 <FeatureTable id="cache.browser_cache_ttl" />
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
index bed629ee6ba70c8..fcaf35844aa8d00 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 3
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,8 +15,8 @@ Specify a time for a visitor’s Browser Cache TTL to accelerate the page load f
 
 By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers. Cloudflare overrides any `Cache-Control` or `Expires` headers with values set via the **Browser Cache TTL** option under **Caching** on your dashboard if:
 
-- The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
-- The origin web server does not send a `Cache-Control` or an `Expires` header.
+* The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
+* The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a [Cache Rule](/cache/how-to/cache-rules/), Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
@@ -25,8 +26,10 @@ Nevertheless, the value you set via Cache Rule will be ignored if `Cache-Control
 
 :::note[Note]
 
+
 If you modify cached assets, the new asset is not displayed to repeat visitors before the Browser Cache TTL duration. [Purging Cloudflare’s cache](/cache/how-to/purge-cache/) does not affect assets cached in a visitor’s browser.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Caching** page.
diff --git a/src/content/docs/cache/how-to/index.mdx b/src/content/docs/cache/how-to/index.mdx
index 9bb4c1c487aacad..80c1f5c0266452d 100644
--- a/src/content/docs/cache/how-to/index.mdx
+++ b/src/content/docs/cache/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
index f33d3c2f25167fd..eccbbdee17432d8 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 4
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Purging by hostname means that all assets at URLs with a host that matches one of the provided values will be instantly purged from the cache.
 
@@ -19,9 +20,9 @@ Purging by hostname means that all assets at URLs with a host that matches one o
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Hostname**.
 4. Follow the syntax instructions:
-   - One hostname per line.
-   - Separated by commas.
-   - You can purge up to 30 hostnames at a time.
+   * One hostname per line.
+   * Separated by commas.
+   * You can purge up to 30 hostnames at a time.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
index 20267fbc6318106..1eba5da16e5ee10 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 With purge by single-file, cached resources are instantly removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific Cloudflare data center that served the request.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
index 0b305a3f14ae32d..0531322accc993e 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 3
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more.
 
@@ -22,8 +23,10 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 
 :::caution[Warning]
 
+
 Be careful when purging. A cache MISS can cause execution delays by requiring a fetch from your origin server.
 
+
 :::
 
 ## Add Cache-Tag HTTP response headers
@@ -32,19 +35,19 @@ You add cache-tags to your web content in `Cache-Tag` HTTP response headers to a
 
 When your content reaches our edge network, Cloudflare:
 
-- Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
-- Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
-- Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
+* Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
+* Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
+* Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
 
 ## A few things to remember
 
-- A single HTTP response can have more than one `Cache-Tag` HTTP header field.
-- The minimum length of a cache-tag is one byte.
-- Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
-- For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
-- The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
-- Spaces are not allowed in cache-tags.
-- Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
+* A single HTTP response can have more than one `Cache-Tag` HTTP header field.
+* The minimum length of a cache-tag is one byte.
+* Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
+* For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
+* The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
+* Spaces are not allowed in cache-tags.
+* Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
 
 ## Purge using cache-tags
 
@@ -59,6 +62,7 @@ When your content reaches our edge network, Cloudflare:
 
 For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
 
+
 ## Resulting cache status
 
 Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests.
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
index d251d69477368b4..831850a380c6d9f 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
@@ -25,18 +25,18 @@ For a Cache Key based on device type, purge the asset by passing the `CF-Device-
 Refer to the example API request below to instantly purge all mobile assets on the root webpage.
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"CF-Device-Type": "mobile",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "CF-Device-Type": "mobile"
+        }
+      }
+    ]
+  }}
 />
 
 ## Purge by geo
@@ -44,18 +44,18 @@ Refer to the example API request below to instantly purge all mobile assets on t
 Instantly purge resources for a location-based Cache Key by specifying the two-letter country code. Spain is used in the example below.
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"CF-IPCountry": "ES",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "CF-IPCountry": "ES"
+        }
+      }
+    ]
+  }}
 />
 
 ## Purge by language
@@ -63,16 +63,16 @@ Instantly purge resources for a location-based Cache Key by specifying the two-l
 For a Cache Key based on language, purge the asset by passing the `accept-language` header. Refer to the example API request below to instantly purge all assets in Chinese (PRC).
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"accept-language": "zh-CN",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "accept-language": "zh-CN"
+        }
+      }
+    ]
+  }}
 />
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
index 42378f5e362023e..1253a3d847f6bfb 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 2
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 To maintain optimal site performance, Cloudflare strongly recommends using single-file (by URL) purging instead of a complete cache purge.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
index f2953ab487936d9..2da37b5840f703d 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 7
+
 ---
 
 Purging varied images instantly purges all content variants for that URL. This behavior occurs so that if an image changes, you can easily update the cache with a single purge request instead of trying to determine the potential number of out-of-date variants. The behavior is true regardless of [purge type](/cache/how-to/purge-cache/) used, such as [single file](/cache/how-to/purge-cache/purge-by-single-file/), [tag](/cache/how-to/purge-cache/purge-by-tags/), or [hostname](/cache/how-to/purge-cache/purge-by-hostname/).
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
index 837b8a1faf20235..06f0af7f6b98cd4 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 8
+
 ---
 
 To purge zone versions via the Cloudflare API, follow these steps:
@@ -22,44 +23,44 @@ This API call will return a JSON response similar to the example below:
 
 ```json
 {
-	"result": {
-		"environments": [
-			{
-				"name": "Production",
-				"ref": "12abcd3e45f678940a573f51834a54",
-				"version": 0,
-				"expression": "(cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"before": "5d41402abc4b2a76b9719d911017c"
-				}
-			},
-			{
-				"name": "Staging",
-				"ref": "5d41402abc4b2a76b9719d911017c",
-				"version": 0,
-				"expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"before": "49f0bad299687c62334182178bfd",
-					"after": "12abcd3e45f678940a573f51834a54"
-				}
-			},
-			{
-				"name": "Development",
-				"ref": "49f0bad299687c62334182178bfd",
-				"version": 0,
-				"expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"after": "5d41402abc4b2a76b9719d911017c"
-				}
-			}
-		]
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "environments": [
+      {
+        "name": "Production",
+        "ref": "12abcd3e45f678940a573f51834a54",
+        "version": 0,
+        "expression": "(cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "before": "5d41402abc4b2a76b9719d911017c"
+        }
+      },
+      {
+        "name": "Staging",
+        "ref": "5d41402abc4b2a76b9719d911017c",
+        "version": 0,
+        "expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "before": "49f0bad299687c62334182178bfd",
+          "after": "12abcd3e45f678940a573f51834a54"
+        }
+      },
+      {
+        "name": "Development",
+        "ref": "49f0bad299687c62334182178bfd",
+        "version": 0,
+        "expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "after": "5d41402abc4b2a76b9719d911017c"
+        }
+      }
+    ]
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -75,7 +76,7 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/purge_cache/
 
 To purge non-production environments, you must use a new `purge_cache` endpoint and specify the environment you would like to purge.
 
-To purge the Staging environment from the example above, send a request to the following endpoint:
+To purge the Staging environment from the example above, send a request to the following endpoint: 
 
 ```bash
 https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/5d41402abc4b2a76b9719d911017c/purge_cache/
@@ -89,4 +90,4 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/49f0bad299687c
 
 :::note
 When purging everything for a non-production cache environment, all files for that specific cache environment will be purged. However, when purging everything for the production environment, all files will be purged across all environments.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
index 38922ec63e70388..315411bd1db2ac1 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
@@ -6,23 +6,24 @@ products:
   - cache
 sidebar:
   order: 5
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 You can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
 
-- `www.example.com`
-- `www.example.com/foo`
-- `www.example.com/foo/bar`
-- `www.example.com/foo/bar/baz`
-- `www.example.com/foo/bar/baz/qux.jpg`
+* `www.example.com`
+* `www.example.com/foo`
+* `www.example.com/foo/bar`
+* `www.example.com/foo/bar/baz`
+* `www.example.com/foo/bar/baz/qux.jpg`
 
 Purging by prefix is useful in different scenarios, such as:
 
-- Purging everything within a directory.
-- Increasing control over cached objects in a path.
-- Simplifying the number of purge calls sent.
+* Purging everything within a directory.
+* Increasing control over cached objects in a path.
+* Simplifying the number of purge calls sent.
 
 1. In the Cloudflare dashboard, go to the **Configuration** page.
 
@@ -31,8 +32,8 @@ Purging by prefix is useful in different scenarios, such as:
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Prefix**.
 4. Follow the syntax instructions.
-   - One prefix per line.
-   - Maximum 30 prefixes per API call.
+   * One prefix per line.
+   * Maximum 30 prefixes per API call.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
@@ -40,8 +41,10 @@ For information on rate limits, refer to the [Availability and limits](/cache/ho
 
 :::caution[Warning]
 
+
 If you have a [Transform Rule](/rules/transform/) in place that is modifying part of a URL path, you must use the post-transformed (origin) URL when performing a prefix purge so that purge can take effect.
 
+
 :::
 
 ## Resulting cache status
@@ -55,19 +58,21 @@ Depending on whether the upper tier has the resource or not, and whether the end
 
 There are several limitations regarding purge by prefix:
 
-- Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
-- Purge requests are limited to 30 prefixes per request.
-- [Purge rate-limits apply](/api/resources/cache/methods/purge/).
-- URI query strings & fragments cannot purge by prefix:
-  - `www.example.com/foo?a=b` (query string)
-  - `www.example.com/foo#bar` (fragment)
+* Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
+* Purge requests are limited to 30 prefixes per request.
+* [Purge rate-limits apply](/api/resources/cache/methods/purge/).
+* URI query strings & fragments cannot purge by prefix:
+  * `www.example.com/foo?a=b` (query string)
+  * `www.example.com/foo#bar` (fragment)
 
 :::caution[Warning]
 
+
 Because purge by prefix purges a directory, any URI for a resource within the purged directory is purged regardless of query string or fragment (though fragments are not generally sent by browsers). Purge by prefix rules do not accept fragments and query strings.
 
 Example: If you purge `foo.com/bar`, any asset that starts with `foo.com/bar` will be purged, for example, `foo.com/bar/baz`, `foo.com/bar?good=bad`, etc. and purging `foo.com/bar?good=bad` itself will not work.
 
+
 :::
 
 ## Purge by prefix normalization
diff --git a/src/content/docs/cache/how-to/set-caching-levels.mdx b/src/content/docs/cache/how-to/set-caching-levels.mdx
index 84cb1614461925d..4d6a0dee4f74ba7 100644
--- a/src/content/docs/cache/how-to/set-caching-levels.mdx
+++ b/src/content/docs/cache/how-to/set-caching-levels.mdx
@@ -7,20 +7,23 @@ products:
 head:
   - tag: title
     content: Caching levels
+
 ---
 
 Caching levels determine how much of your website’s static content Cloudflare should cache. Cloudflare’s CDN caches static content according to the levels below.
 
-- **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
-- **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
-- **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
+* **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
+* **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
+* **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
 
 You can adjust the caching level from the dashboard under **Caching** > **Configuration** > **Caching level**.
 
 :::note[Note]
 
+
 Ignore Query String only disregards the query string for static file extensions. For example, Cloudflare serves the `style.css` resource to requests for either `style.css?this` or `style.css?that`.
 
+
 :::
 
 ## API Caching level values
diff --git a/src/content/docs/cache/interaction-cloudflare-products/index.mdx b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
index 842985c69a31adc..449a56ed4e7345c 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/index.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+    
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare caches content at data centers close to your visitors so your origin server handles fewer requests. The pages below explain how caching works when you also use Workers, R2 storage, or WAF security rules, and what to watch out for when combining them.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
index 11c3946c910d777..ed54947bc4e5f34 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Enable cache in an R2 bucket
+
 ---
 
 By default, R2 buckets are private. To serve R2 objects through Cloudflare's cache, you need to attach a domain name you control — called a [Custom Domain](/r2/buckets/public-buckets/#custom-domains) — to the bucket. This creates a public URL backed by Cloudflare's network, so requests for your stored files go through Cloudflare's cache instead of hitting R2 directly every time.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
index 5f5d22b02dd934b..fb6bf25720d358f 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
@@ -23,7 +23,7 @@ accTitle: Connections with Cloudflare
 A[User's request] --> B[WAF] --> C[Cache] --> D[R2]
 ```
 
-<br />
+<br/>
 
 ## Presigned URLs
 
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
index a7765d2c345f3a1..390f1369a9cee75 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: How Workers interact with Cache Rules
+
 ---
 
 When you use both [Cache Rules](/cache/how-to/cache-rules/) and [Workers](/workers/) on the same request, the Worker's cache settings take priority — but only when the required [compatibility flags](#compatibility-flags) are enabled.
@@ -38,10 +39,10 @@ These flags must be enabled to allow Workers scripts to override Cache Rules. If
 
 A Worker's [compatibility date](/workers/configuration/compatibility-dates/) determines which flags are active by default. When you set a compatibility date, all flags with an enable date on or before that date are automatically turned on.
 
-| Flag                                                     | Enabled by default                           | Prerequisite                      |
-| -------------------------------------------------------- | -------------------------------------------- | --------------------------------- |
-| `request_cf_overrides_cache_rules` (Fetch API)           | Compatibility dates on or after `2025-04-02` | None                              |
-| `cache_api_compat_flags`                                 | Compatibility dates on or after `2025-04-19` | None                              |
+| Flag | Enabled by default | Prerequisite |
+| --- | --- | --- |
+| `request_cf_overrides_cache_rules` (Fetch API) | Compatibility dates on or after `2025-04-02` | None |
+| `cache_api_compat_flags` | Compatibility dates on or after `2025-04-19` | None |
 | `cache_api_request_cf_overrides_cache_rules` (Cache API) | Compatibility dates on or after `2025-05-19` | Requires `cache_api_compat_flags` |
 
 The Cache API has an extra requirement: `cache_api_compat_flags` must be enabled for any compatibility flags to take effect on the Cache API. Without it, the Cache API ignores all compatibility flags, even ones you explicitly list in your configuration.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
index 91df57a65ed0396..0b90c7883ab5180 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Customize cache behavior with Workers
+
 ---
 
 You can use [Workers](/workers/) to customize cache behavior on Cloudflare's network. Workers run as middleware in the request lifecycle — a single Worker handles both the request and response phases. When a request arrives, it hits the Worker before the cache is checked. The Worker can modify the incoming request (for example, rewrite the URL or add headers), then call `fetch()` to continue the request through the cache. When the response comes back — whether from cache or from the origin server — the Worker can also modify the response before it is sent to the visitor.
@@ -45,4 +46,4 @@ Workers offer two ways to interact with the cache. Use `fetch()` when your Worke
 
 - **Cache API**: Allows you to programmatically store, retrieve, and delete responses in Cloudflare's cache using `caches.default` or `caches.open()`. Unlike `fetch()`, the Cache API only operates on the cache in the data center handling the current request — it does not interact with Tiered Cache. Use the Cache API when you need to cache responses that did not come from an origin. For more details, refer to [Using the Cache API](/workers/examples/cache-api/).
 
-To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
+To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
\ No newline at end of file
diff --git a/src/content/docs/cache/performance-review/cache-analytics.mdx b/src/content/docs/cache/performance-review/cache-analytics.mdx
index 6db30fa95015ec1..5e225c6a89340c7 100644
--- a/src/content/docs/cache/performance-review/cache-analytics.mdx
+++ b/src/content/docs/cache/performance-review/cache-analytics.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: View cache hit rates and bandwidth savings in Cache Analytics.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Cache Analytics shows how much of your site's traffic is served from Cloudflare's cache versus your origin server. When content is served from cache, visitors get faster page loads and your origin web server handles less traffic. Use Cache Analytics to identify resources that are [missing from cache](/cache/concepts/cache-responses/#miss), [expired](/cache/concepts/cache-responses/#expired) (cached copy is outdated), or [ineligible for caching](/cache/concepts/cache-responses/#noneunknown) (not eligible for caching). You can filter by hostname, review the top URLs that miss cache, and query up to three days of data.
 
@@ -18,7 +19,7 @@ Cache Analytics shows how much of your site's traffic is served from Cloudflare'
 
 In the Cloudflare dashboard, go to the **Caching** page.
 
-<DashButton url="/?to=/:account/:zone/caching" />
+   <DashButton url="/?to=/:account/:zone/caching" />
 
 ## Requests vs Data Transfer
 
diff --git a/src/content/docs/cache/performance-review/cache-performance.mdx b/src/content/docs/cache/performance-review/cache-performance.mdx
index 9e4e9ebc7569a11..528344752e6ef3d 100644
--- a/src/content/docs/cache/performance-review/cache-performance.mdx
+++ b/src/content/docs/cache/performance-review/cache-performance.mdx
@@ -24,6 +24,7 @@ Depending on the [cache status](/cache/concepts/cache-responses/) you receive, y
 Use [Cache Analytics](/cache/performance-review/cache-analytics/) to identify cache performance issues. The following examples show how to filter for common problems and resolve them.
 
 - Not caching HTML.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Dynamic**.
   - Resolution: Set a Cloudflare Cache Rule to [cache dynamic content](/cache/how-to/cache-rules/examples/cache-everything/).
 
@@ -34,12 +35,14 @@ This option caches all HTML regardless of the presence of dynamic content (conte
 - Checking for the presence of a cookie.
 - Excluding requests that match known dynamic content file paths.
 - Excluding requests with dynamic content extensions (or no extension).
-  :::
+:::
 
 - Short cache expiration TTL.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Revalidated**.
   - Resolution: [Increase Cloudflare's Edge Cache TTL via a Cache Rule](/cache/how-to/cache-rules/examples/edge-ttl/).
 
 - Need to enable Tiered Cache or custom cache key.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Miss**.
   - Resolution: [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) or [create a custom cache key](/cache/how-to/cache-rules/examples/custom-cache-key/).
diff --git a/src/content/docs/cache/performance-review/index.mdx b/src/content/docs/cache/performance-review/index.mdx
index b2b00f57fe7dfb6..62a5b788d098027 100644
--- a/src/content/docs/cache/performance-review/index.mdx
+++ b/src/content/docs/cache/performance-review/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 8
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use Cache Analytics to understand how effectively Cloudflare caches your content, and apply optimization techniques to improve your cache hit ratio and reduce origin server load.
 
diff --git a/src/content/docs/cache/plans.mdx b/src/content/docs/cache/plans.mdx
index a4543e9bf53afe7..e8f54313de37f9f 100644
--- a/src/content/docs/cache/plans.mdx
+++ b/src/content/docs/cache/plans.mdx
@@ -10,12 +10,13 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="cache" />
+<ProductFeatures id="cache" />
\ No newline at end of file
diff --git a/src/content/docs/cache/reference/cdn-reference-architecture.mdx b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
index 145f83c1cb84f3c..4681ed5552d3aa6 100644
--- a/src/content/docs/cache/reference/cdn-reference-architecture.mdx
+++ b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
@@ -5,4 +5,5 @@ products:
   - cache
 title: CDN Reference Architecture
 external_link: /reference-architecture/architectures/cdn/
+
 ---
diff --git a/src/content/docs/cache/reference/development-mode.mdx b/src/content/docs/cache/reference/development-mode.mdx
index 417c841881601c5..c6f9d879d1f7baf 100644
--- a/src/content/docs/cache/reference/development-mode.mdx
+++ b/src/content/docs/cache/reference/development-mode.mdx
@@ -4,15 +4,16 @@ pcx_content_type: how-to
 description: Bypass the cache temporarily with Development Mode.
 products:
   - cache
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript.
 
 :::note
 
-To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache).
+To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache). 
 :::
 
 ## Enable Development Mode
diff --git a/src/content/docs/cache/reference/index.mdx b/src/content/docs/cache/reference/index.mdx
index fa4c9cb8953cc15..57aa94f03cf5680 100644
--- a/src/content/docs/cache/reference/index.mdx
+++ b/src/content/docs/cache/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the reference content to learn more about specific caching functionality.
 
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx
index bd25e5e49df3439..c5011e04ae13af4 100644
--- a/src/content/docs/cache/troubleshooting/always-online.mdx
+++ b/src/content/docs/cache/troubleshooting/always-online.mdx
@@ -36,13 +36,16 @@ Always Online does not trigger for HTTP response codes such as [404](/support/tr
 ## Frequently asked questions
 
 1. How can I know if a page has been crawled?
+
    - You can go to the [Internet Archive](https://web.archive.org/) and search for the page URL to see if it has been crawled or not.
    - You can also check this via the [Internet Archive Availability API](https://archive.org/help/wayback_api.php).
 
 2. Why were not pages x, y, and z crawled?
+
    - Since Cloudflare only requests to crawl the most popular pages on the site, it is possible that there will be missing pages. If you really want to archive a page, then you can visit the [Internet Archive](https://web.archive.org/save) save page and ask them to crawl a particular page.
 
 3. What IP addresses do we need to allowlist to make sure crawling works?
+
    - IP Range: `207.241.224.0/20` and `208.70.24.0/21`. Note that this ip range belongs to Internet Archive and NOT Cloudflare, since it is the Internet Archive that does the crawling.
 
 4. What user agent should the origin expect to see?
diff --git a/src/content/docs/cache/troubleshooting/index.mdx b/src/content/docs/cache/troubleshooting/index.mdx
index 43a1ccb36799ea9..6d019d87491a048 100644
--- a/src/content/docs/cache/troubleshooting/index.mdx
+++ b/src/content/docs/cache/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The following topics are useful for troubleshooting Cache issues.
 
diff --git a/src/content/docs/china-network/concepts/global-acceleration.mdx b/src/content/docs/china-network/concepts/global-acceleration.mdx
index 65a11d18c9950e0..d5cf13877556bdc 100644
--- a/src/content/docs/china-network/concepts/global-acceleration.mdx
+++ b/src/content/docs/china-network/concepts/global-acceleration.mdx
@@ -30,14 +30,14 @@ Organizations that serve content or connect employees in Mainland China face con
 
 Global Acceleration can support the following scenarios:
 
-| Service                                                                                 | Scenario                                                                                           |
-| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Service                                                                                 | Scenario                                                            |
+| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
 | [CDN Global Acceleration](#cdn-global-acceleration)                                     | Improved performance for dynamic content (API responses, personalized pages) on China Network CDN. |
-| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                                                      |
-| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                                                             |
-| [ICP](#icp-services)                                                                    | China Network prerequisite.                                                                        |
-| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                                                      |
-| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China.                  |
+| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                       |
+| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                              |
+| [ICP](#icp-services)                                                                    | China Network prerequisite.                                         |
+| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                       |
+| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China. |
 
 ## CDN Global Acceleration
 
diff --git a/src/content/docs/china-network/reference/available-products.mdx b/src/content/docs/china-network/reference/available-products.mdx
index 0ae2911eaa5b486..f5ba030c4d27bda 100644
--- a/src/content/docs/china-network/reference/available-products.mdx
+++ b/src/content/docs/china-network/reference/available-products.mdx
@@ -37,7 +37,7 @@ The following products and features are available on the Cloudflare China Networ
 | [R2](/r2/)[^3]                                                            | Object storage for all your data.                                                                                                                  |
 | [Assets](/workers/static-assets/)                                         | Upload static assets (HTML, CSS, images and other files) as part of your Worker — Cloudflare will handle caching and serving them to web browsers. |
 | [Environment variables](/workers/configuration/environment-variables/)    | Attach text strings or JSON values to your Worker.                                                                                                 |
-| [Images](/images/optimization/transformations/bindings/)[^4]              | Store, transform, optimize, and deliver images at scale.                                                                                           |
+| [Images](/images/optimization/transformations/bindings/)[^4]                          | Store, transform, optimize, and deliver images at scale.                                                                                           |
 | [mTLS](/workers/runtime-apis/bindings/mtls/)                              | Securely connect to backend servers over [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).                        |
 | [Rate Limiting](/workers/runtime-apis/bindings/rate-limit/)               | Define rate limits and write code around them in your Worker.                                                                                      |
 | [Secrets](/workers/configuration/secrets/)                                | Attach encrypted text values to your Worker.                                                                                                       |
diff --git a/src/content/docs/client-ip-geolocation/about/index.mdx b/src/content/docs/client-ip-geolocation/about/index.mdx
index eeb0a5dfa94995f..28a8f360c648938 100644
--- a/src/content/docs/client-ip-geolocation/about/index.mdx
+++ b/src/content/docs/client-ip-geolocation/about/index.mdx
@@ -10,8 +10,10 @@ description: Learn how Cloudflare Firewall Rules work.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 Cloudflare Client IP Geolocation helps you understand where in the world a given client is located, even if their true client IP address is obscured by Cloudflare's proxy systems. We offer this service to ensure customers have high-quality experiences interacting with origins that rely on geolocation — such as mapping providers — and origin operators can deliver the right content to the right users. Ensuring origins know where clients are located avoids problems associated with traditional VPNs that obscure a consumer’s geolocation and allow circumvention of geographic restrictions on content.
@@ -28,7 +30,7 @@ If a VPN user tries to use an interposed VPN or proxy system that attempts to hi
 
 ## Technical explanation
 
-We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like _MaxMind_, _IP 2 Location_, and _Neustar_.
+We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like *MaxMind*, *IP 2 Location*, and *Neustar*.
 
 When Cloudflare receives an inbound request from a WARP or 1.1.1.1 user, we first geolocate the IP address that made the connection to Cloudflare. Then, we select an egress IP that maps to the client geolocation. We then discard Client IP information to preserve user privacy but return their true geographic location.
 
diff --git a/src/content/docs/client-ip-geolocation/faq/index.mdx b/src/content/docs/client-ip-geolocation/faq/index.mdx
index 85a00673fec5ea2..c7687b23fc2d865 100644
--- a/src/content/docs/client-ip-geolocation/faq/index.mdx
+++ b/src/content/docs/client-ip-geolocation/faq/index.mdx
@@ -10,8 +10,10 @@ description: Answers to common questions.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 ## Website operators
diff --git a/src/content/docs/client-ip-geolocation/get-started.mdx b/src/content/docs/client-ip-geolocation/get-started.mdx
index f6115e8f83f2b6f..7bfddd2706bc177 100644
--- a/src/content/docs/client-ip-geolocation/get-started.mdx
+++ b/src/content/docs/client-ip-geolocation/get-started.mdx
@@ -10,16 +10,18 @@ description: Set up Client IP Geolocation for your network.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 There are several things you can do to best handle traffic from Cloudflare VPN and forward-proxy users:
 
-- **Origin operators**:
-  - Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
-  - To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
-- **Geolocation data providers**:
-  - Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
-- **Users of WARP and 1.1.1.1**:
-  - Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
+* **Origin operators**:
+  * Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
+  * To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
+* **Geolocation data providers**:
+  * Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
+* **Users of WARP and 1.1.1.1**:
+  * Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
diff --git a/src/content/docs/client-ip-geolocation/index.mdx b/src/content/docs/client-ip-geolocation/index.mdx
index bd7c326b3032781..5464f9a0cb448ee 100644
--- a/src/content/docs/client-ip-geolocation/index.mdx
+++ b/src/content/docs/client-ip-geolocation/index.mdx
@@ -11,27 +11,27 @@ products:
 description: Add geolocation data for clients behind Cloudflare proxies.
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 Cloudflare designed [Cloudflare WARP](/warp-client/) and [1.1.1.1](/1.1.1.1/) to make Internet browsing more private and secure. These applications encrypt last-mile connections and make it more difficult for others to use client IP addresses in user fingerprinting.
 
 However, unlike legacy VPN applications, we never designed WARP or 1.1.1.1 to hide user locations or allow users to misrepresent their true geographic location. As a web property operator, you can use **Client IP Geolocation** to map Cloudflare egress IP addresses to specific geolocations.
 
-<LinkButton variant="primary" href="/client-ip-geolocation/get-started/">
-	Get started
-</LinkButton>
-<LinkButton variant="secondary" href="/client-ip-geolocation/about/">
-	Learn more
-</LinkButton>
+ <LinkButton variant="primary" href="/client-ip-geolocation/get-started/">Get started</LinkButton> <LinkButton variant="secondary" href="/client-ip-geolocation/about/">Learn more</LinkButton>
+
 
 :::note
 
+
 Client IP Geolocation is different from the [Cloudflare IP Geolocation setting](/network/ip-geolocation/), which helps you capture country codes for visitors.
 
+
 :::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
index e8e7c1e8e6a9464..c3af18280364b77 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
@@ -214,4 +214,4 @@ The custom error token provides diagnostic information or specific functionality
     </html>
   ```
   </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
index a5b7daf4949db75..82759d6a2395e0b 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
@@ -29,4 +29,4 @@ fetch("/my-api-endpoint").then((response) => {
 		// Process response as usual
 	}
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
index 6c07e3d158b50d9..bc5eb92be6854f4 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
@@ -56,4 +56,4 @@ To ensure your API calls are protected without breaking single-page applications
 
 By enabling Pre-clearance, the Turnstile widget issues a persistent clearance cookie (`cf_clearance`) upon successful human verification on an initial HTML page. This cookie pre-clears the visitor to interact with sensitive API endpoints secured by WAF rules, allowing you to deploy granular security without forcing a disruptive Challenge Page response.
 
-For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
+For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
index 9f1f938bab49aa4..ca4edef555c115d 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
@@ -19,4 +19,4 @@ When observing a Cloudflare Challenge page, a visitor could:
 
 :::note
 Visitors must enable JavaScript and cookies on their browser to be able to pass any type of Challenge.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
index e0f3d123a4bb4d7..5ccae5620b19ca2 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on available challenge types:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
index 5c15a8df1753eff..3a4bd64156f9af5 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
@@ -16,7 +16,7 @@ Turnstile differs from Challenges Pages in that the challenge does not pause the
 
 In most cases, nothing further is required from the visitor. However, if necessary, Turnstile may display a simple checkbox that the visitor must click to proceed.
 
-After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions.
+After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions. 
 
 <Render file="siteverify-warning" product="turnstile" />
 
@@ -26,18 +26,20 @@ While there are three types of widgets that you can choose to implement on your
 
 - **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a challenge based on the signals gathered from the visitor's browser and presents an interaction only if it detects potentially automated traffic.
 
-- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity.
+- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity. 
 
 - **Invisible**: The widget is completely invisible to the visitor, but the challenge still runs in the background.
 
   :::note[Link to Cloudflare's Turnstile Privacy Policy]
-
-  <Render file="privacy-policy" product="turnstile" />
+  <Render
+    file="privacy-policy"
+    product="turnstile"
+  />
   :::
 
 ## Implementation
 
-When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey.
+When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey. 
 
 The sitekey is used with [client-side rendering](/turnstile/get-started/client-side-rendering/#implicitly-render-the-turnstile-widget) by adding it to the `<div>` container placeholder. You will then place that `<div>` code snippet where you want to add the widget to your site page or form.
 
diff --git a/src/content/docs/cloudflare-challenges/concepts/index.mdx b/src/content/docs/cloudflare-challenges/concepts/index.mdx
index 181b5dfde7eb724..8587e3ba1d8f3f0 100644
--- a/src/content/docs/cloudflare-challenges/concepts/index.mdx
+++ b/src/content/docs/cloudflare-challenges/concepts/index.mdx
@@ -7,11 +7,11 @@ products:
 sidebar:
   order: 2
   label: About
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on how challenges work:
 
diff --git a/src/content/docs/cloudflare-challenges/index.mdx b/src/content/docs/cloudflare-challenges/index.mdx
index 08083dc2ca79e13..b1612b44767b991 100644
--- a/src/content/docs/cloudflare-challenges/index.mdx
+++ b/src/content/docs/cloudflare-challenges/index.mdx
@@ -11,8 +11,7 @@ sidebar:
 import { Render, Description, Plan, RelatedProduct } from "~/components";
 
 <Description>
-	Challenges are security mechanisms used by Cloudflare to verify whether a
-	visitor to your site is a real human and not a bot or automated script.
+	Challenges are security mechanisms used by Cloudflare to verify whether a visitor to your site is a real human and not a bot or automated script.
 </Description>
 
 When a Challenge is issued, Cloudflare asks the browser to perform a series of checks that help confirm the visitor's legitimacy. This process involves evaluating client-side signals (data gathered from the visitor's browser environment) or asking a visitor to take minimal action such as checking a box or selecting a button.
diff --git a/src/content/docs/cloudflare-challenges/reference/index.mdx b/src/content/docs/cloudflare-challenges/reference/index.mdx
index fe3f9e06287d1c6..3c0a6f05993d737 100644
--- a/src/content/docs/cloudflare-challenges/reference/index.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Cloudflare Challenges:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
index d5d5ad31165401a..a8b394b4c4b0410 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
@@ -8,43 +8,45 @@ sidebar:
   order: 4
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
-Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge.
+Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge. 
 
-Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of.
+Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of. 
 
 ## Overview
 
-Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis.
+Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis. 
 
 ### Supported browsers
 
 The following browsers are officially supported and tested.
 
 <Details header="Google Chrome (desktop and mobile)">
-	- Current version and two previous major versions - Chromium-based browsers
-	and Chromium-based browsers that track the current Chrome stable version
-	:::caution Beta, Dev, Canary, Nightly, or other unreleased builds are not
-	officially supported. :::
+  - Current version and two previous major versions
+  - Chromium-based browsers and Chromium-based browsers that track the current Chrome stable version
+  
+  :::caution
+  Beta, Dev, Canary, Nightly, or other unreleased builds are not officially supported.
+  :::
 </Details>
 
 <Details header="Mozilla Firefox">
-	- Current version and two previous major versions - Extended Support Release
-	(ESR) versions are supported
+  - Current version and two previous major versions
+  - Extended Support Release (ESR) versions are supported
 </Details>
 
 <Details header="Safari">
-	- Current version and two previous major versions - iOS Safari on current iOS
-	version and two previous major versions
+  - Current version and two previous major versions
+  - iOS Safari on current iOS version and two previous major versions
 </Details>
 
 <Details header="Microsoft Edge">
-	- Current version and two previous major versions
-</Details>
+  - Current version and two previous major versions
+  </Details>
 
 <Details header="Samsung Internet Browser">
-	- Current version and two previous major versions
+  - Current version and two previous major versions
 </Details>
 
 ### Limited browser support
@@ -79,19 +81,19 @@ Browser extensions can interfere with challenges in several ways.
 - Browser automation tools are often detected as potential bots and may cause challenge failures.
 
 :::note
-If challenges consistently fail, try temporarily disabling extensions and reload the page.
+If challenges consistently fail, try temporarily disabling extensions and reload the page. 
 :::
 
 ### Device emulation and developer tools
 
 Challenges are designed to distinguish between real human users and automated traffic. When device emulation is enabled (such as through browser developer tools), it can trigger bot detection mechanisms.
 
-- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices.
+- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices. 
 - Developer tools may modify browser behavior or expose debugging information that changes how challenges operate.
 - Automation frameworks like Selenium, Puppeteer, or Playwright are specifically detected as non-human traffic.
 
 :::note
-For developers testing applications, we recommend using real devices rather than emulated environments when possible.
+For developers testing applications, we recommend using real devices rather than emulated environments when possible. 
 
 If you must use emulation, be aware that challenges may be more difficult to pass, and do not reflect the real experience on mobile devices.
 :::
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
index c9c87ed0b0cddc3..3b3282d4adca332 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
@@ -12,30 +12,30 @@ sidebar:
 
 ## Multi-language support
 
-Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface.
+Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface. 
 
-For language support specific to Challenge Pages, refer to the table below.
+For language support specific to Challenge Pages, refer to the table below. 
 
-| Language                      | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
-| ----------------------------- | ----------------------------- | ----------------------------- |
-| Arabic (Egypt)                | `ar-eg`                       | `ar`                          |
-| Chinese (Simplified, China)   | `zh-cn`                       | `zh`                          |
-| Chinese (Traditional, Taiwan) | `zh-tw`                       | --                            |
-| Dutch (Netherlands)           | `nl-nl`                       | `nl`                          |
-| English (United States)       | `en-us`                       | `en`                          |
-| French (France)               | `fr-fr`                       | `fr`                          |
-| German (Germany)              | `de-de`                       | `de`                          |
-| Indonesian (Indonesia)        | `id-id`                       | `id`                          |
-| Italian (Italy)               | `it-it`                       | `it`                          |
-| Japanese (Japan)              | `ja-jp`                       | `ja`                          |
-| Korean (Korea)                | `ko-kr`                       | `ko`                          |
-| Persian                       | --                            | `fa`                          |
-| Polish (Poland)               | `pl-pl`                       | `pl`                          |
-| Portuguese (Brazil)           | `pt-br`                       | `pt`                          |
-| Russian (Russia)              | `ru-ru`                       | `ru`                          |
-| Spanish (Spain)               | `es-es`                       | `es`                          |
-| Turkish (Turkey)              | `tr-tr`                       | `tr`                          |
+| Language                         | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
+| -------------------------------- | ----------------------------- | ----------------------------- |
+| Arabic (Egypt)                   | `ar-eg`                       | `ar`                          |
+| Chinese (Simplified, China)      | `zh-cn`                       | `zh`                          |
+| Chinese (Traditional, Taiwan)    | `zh-tw`                       | --                            |
+| Dutch (Netherlands)              | `nl-nl`                       | `nl`                          |
+| English (United States)          | `en-us`                       | `en`                          |
+| French (France)                  | `fr-fr`                       | `fr`                          |
+| German (Germany)                 | `de-de`                       | `de`                          |
+| Indonesian (Indonesia)           | `id-id`                       | `id`                          |
+| Italian (Italy)                  | `it-it`                       | `it`                          |
+| Japanese (Japan)                 | `ja-jp`                       | `ja`                          |
+| Korean (Korea)                   | `ko-kr`                       | `ko`                          |
+| Persian                          |  --                           | `fa`
+| Polish (Poland)                  | `pl-pl`                       | `pl`                          |
+| Portuguese (Brazil)              | `pt-br`                       | `pt`                          |
+| Russian (Russia)                 | `ru-ru`                       | `ru`                          |
+| Spanish (Spain)                  | `es-es`                       | `es`                          |
+| Turkish (Turkey)                 | `tr-tr`                       | `tr`                          |
 
 ### Turnstile language support
 
-For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
+For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
index 0403f66ba3ed126..d9da862f3207f6c 100644
--- a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
@@ -8,9 +8,10 @@ tags:
   - Debugging
 sidebar:
   order: 2
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Challenge loops
 
@@ -34,6 +35,6 @@ Ensure your browser is updated to the latest version to maintain compatibility.
 
 Follow the steps below to ensure that your environment is properly configured.
 
-<Render file="troubleshooting-steps" product="turnstile" />
+<Render file="troubleshooting-steps" product="turnstile"/>
 
 If none of the above resolves your issue, contact the website administrator with the [error code](/turnstile/troubleshooting/client-side-errors/error-codes/) and Ray ID or submit a [feedback report](/turnstile/troubleshooting/feedback-reports/) through the Turnstile widget by selecting **Submit Feedback**.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
index 7ff0b1bb50a2ea4..360ff1b151ff9d5 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
@@ -9,19 +9,20 @@ sidebar:
 head:
   - tag: title
     content: Backoff schedule | Hostname validation
+
 ---
 
 After you create a custom hostname, Cloudflare has to [validate that hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/).
 
 Attempts to validate a Custom Hostname are distributed over seven days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
 
-- For the first 10 attempts:
+* For the first 10 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.05, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
 ```
 
-- For the remaining 65 attempts:
+* For the remaining 65 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.15, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
index e53e217ee14dd51..3583929fa75cde3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Error codes - Custom Hostname Validation
+
 ---
 
 When you [validate a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/), you might encounter the following error codes.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
index 12b2229cd3ba429..4e23151ad107b4f 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Pre-validation methods - Custom Hostname Validation
+
 ---
 
 Pre-validation methods help verify domain ownership before your customer's traffic is proxying through Cloudflare.
@@ -29,8 +30,10 @@ TXT validation is when your customer adds a `TXT` record to their authoritative
 
 :::note
 
+
 If your customer cannot update their authoritative DNS, you could also use [HTTP validation](#http-tokens).
 
+
 :::
 
 To set up `TXT` validation:
@@ -39,23 +42,21 @@ To set up `TXT` validation:
 
    ```json null {11-12}
    {
-   	"result": [
-   		{
-   			"id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
-   			"hostname": "app.example.com",
-   			// ...
-   			"status": "pending",
-   			"verification_errors": [
-   				"custom hostname does not CNAME to this zone."
-   			],
-   			"ownership_verification": {
-   				"type": "txt",
-   				"name": "_cf-custom-hostname.app.example.com",
-   				"value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
-   			},
-   			"created_at": "2020-03-04T19:04:02.705068Z"
-   		}
-   	]
+   "result": [
+       {
+       "id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
+       "hostname": "app.example.com",
+       // ...
+       "status": "pending",
+       "verification_errors": ["custom hostname does not CNAME to this zone."],
+       "ownership_verification": {
+           "type": "txt",
+           "name": "_cf-custom-hostname.app.example.com",
+           "value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
+       },
+       "created_at": "2020-03-04T19:04:02.705068Z"
+       }
+   ]
    }
    ```
 
@@ -81,18 +82,18 @@ To get and use the `ownership_verification` record:
 
    ```json title="Example response (truncated)" {8-9}
    {
-   	"result": [
-   		{
-   			"id": "24c8c68e-bec2-49b6-868e-f06373780630",
-   			"hostname": "app.example.com",
-   			// ...
-   			"ownership_verification_http": {
-   				"http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
-   				"http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
-   			},
-   			"created_at": "2020-03-04T20:06:04.117122Z"
-   		}
-   	]
+     "result": [
+       {
+         "id": "24c8c68e-bec2-49b6-868e-f06373780630",
+         "hostname": "app.example.com",
+         // ...
+         "ownership_verification_http": {
+             "http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
+             "http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
+         },
+         "created_at": "2020-03-04T20:06:04.117122Z"
+       }
+     ]
    }
    ```
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
index 4cc01d36fb14628..37075f00034342b 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
@@ -15,7 +15,7 @@ description: Learn how to move hostnames between different zones.
 
 As a SaaS provider, you may want, or have, multiple zones to manage hostnames. Each zone can have different configurations or origins, as well as correlate to varying products. You might shift custom hostnames between zones to enable or disable certain features. Cloudflare allows migration within the same account through the steps below:
 
----
+***
 
 ## CNAME
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
index 3c056f32553e457..9623b2a72514ec3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
@@ -11,7 +11,7 @@ sidebar:
   order: 7
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can use custom hostname analytics for two general purposes: exploring how your customers use your product and sharing the benefits provided by Cloudflare with your customers.
 
@@ -19,17 +19,19 @@ These analytics include **Site Analytics**, **Bot Analytics**, **Cache Analytics
 
 :::note
 
+
 The plan of your Cloudflare for SaaS application determines the analytics available for your custom hostnames.
 
+
 :::
 
 ## Explore customer usage
 
 Use custom hostname analytics to help your organization with billing and infrastructure decisions, answering questions like:
 
-- "How many total requests is your service getting?"
-- "Is one customer transferring significantly more data than the others?"
-- "How many global customers do you have and where are they distributed?"
+* "How many total requests is your service getting?"
+* "Is one customer transferring significantly more data than the others?"
+* "How many global customers do you have and where are they distributed?"
 
 If you see one customer is using more data than another, you might increase their bill. If requests are increasing in a certain geographic region, you might want to increase the origin servers in that region.
 
@@ -39,9 +41,9 @@ To access custom hostname analytics, either [use the dashboard](/analytics/faq/a
 
 With custom hostname analytics, you can also share site information with your customers, including data about:
 
-- How many pageviews their site is receiving.
-- Whether their site has a large percentage of bot traffic.
-- How fast their site is.
+* How many pageviews their site is receiving.
+* Whether their site has a large percentage of bot traffic.
+* How fast their site is.
 
 Build custom dashboards to share this information by specifying an individual custom hostname in `clientRequestHTTPHost` field of [any dataset](/analytics/graphql-api/features/data-sets/) that includes this field.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
index 5e86134809b77f7..55fbfb5650d6322 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
@@ -6,6 +6,7 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Argo Smart Routing uses real-time global network information to route traffic on the fastest possible path across the Internet. Regardless of geographic location, this allows Cloudflare to optimize routing to make it faster, more reliable, and more secure. As a SaaS provider, you may want to emphasize the quickest traffic delivery for your end customers. To do so, [enable Argo Smart Routing](/argo-smart-routing/get-started/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
index 9b9a27e309eb3ba..16b0b87aaa5f035 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
@@ -6,6 +6,7 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Cloudflare makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers. Content can be either static or dynamic: static content is “cacheable” or eligible for caching, and dynamic content is “uncacheable” or ineligible for caching. The cached copies of content are stored physically closer to users, optimized to be fast, and do not require recomputing.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
index 74ec34298a49532..439f92b92dc27a1 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
@@ -12,13 +12,13 @@ import { APIRequest } from "~/components";
 
 [Early Hints](/cache/advanced-configuration/early-hints/) allows the browser to begin loading resources while the origin server is compiling the full response. This improves webpage’s loading speed for the end user. As a SaaS provider, you may prioritize speed for some of your custom hostnames. Using custom metadata, you can [enable Early Hints](/cache/advanced-configuration/early-hints/#enable-early-hints) per custom hostname.
 
----
+***
 
 ## Prerequisites
 
 Before you can employ Early Hints for SaaS, you need to create a custom hostname. Review [Get Started with Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) if you have not already done so.
 
----
+***
 
 ## Enable Early Hints per custom hostname via the API
 
@@ -29,51 +29,51 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
 3. If you are [creating a new custom hostname](/api/resources/custom_hostnames/methods/create/), make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames"
-	method="POST"
-	json={{
-		hostname: "<CUSTOM_HOSTNAME>",
-		ssl: {
-			method: "http",
-			type: "dv",
-			settings: {
-				http2: "on",
-				min_tls_version: "1.2",
-				tls_1_3: "on",
-				early_hints: "on",
+  path="/zones/{zone_id}/custom_hostnames"
+  method="POST"
+  json={{
+		"hostname": "<CUSTOM_HOSTNAME>",
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on",
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				},
+				"bundle_method": "ubiquitous",
+				"wildcard": false
 			},
-			bundle_method: "ubiquitous",
-			wildcard: false,
-		},
 	}}
 />
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames"
-	method="GET"
-	parameters={{
-		hostname: "{hostname}",
+  path="/zones/{zone_id}/custom_hostnames"
+  method="GET"
+  parameters={{
+		hostname:"{hostname}"
 	}}
 />
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
-	method="PATCH"
-	json={{
-		ssl: {
-			method: "http",
-			type: "dv",
-			settings: {
-				http2: "on", // Note: These settings will be set to default if not included when updating early hints
-				min_tls_version: "1.2",
-				tls_1_3: "on",
-				early_hints: "on",
+  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+  method="PATCH"
+  json={{
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on", // Note: These settings will be set to default if not included when updating early hints
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				}
 			},
-		},
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
index 1f00c930036f700..599383a86465771 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
@@ -6,11 +6,12 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
+
 ---
 
 Cloudflare for SaaS allows you to deliver the best performance to your end customers by helping enable you to reduce latency through:
 
-- [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
-- [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
-- [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
-- By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
+* [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
+* [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
+* [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
+* By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
index 8e173849b2eee87..beee8c46e86d55c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-authorities/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
index 0914ddfc956673d..66293af0636f89f 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
index aaeb2fc1941b5f1..2e40b6f99d15771 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
index b13a64d43827f6c..c6b4665a4571939 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-and-hostname-priority/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
index 8f572172a0a7569..6b92b6171e4f460 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Custom Certificate Signing Requests
+
 ---
 
 ## Success codes
@@ -22,33 +23,33 @@ head:
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                 |
-| ---------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                       |
-| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                          |
-| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                      |
-| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                                      |
-| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                                   |
-| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                               |
-| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                                |
-| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                               |
-| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                                      |
-| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&\*()=+{}[]                                                                                                                                                   |
-| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                 |
-| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                   |
-| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                                 |
-| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                           |
-| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                                     |
-| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                    |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                           |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                       |
-| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                    |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                        |
+| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                              |
+| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                             |
+| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                           |
+| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                             |
+| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                          |
+| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                      |
+| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                       |
+| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                      |
+| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                             |
+| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&*()=+{}[]                                                                                                                                       |
+| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                        |
+| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                          |
+| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                        |
+| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                  |
+| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                            |
+| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                        |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                       |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                            |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                       |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                           |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                  |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                              |
+| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                   |
 | 403              | 1404           | Access to generating CSRs has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you. |
-| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                 |
-| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                           |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                         |
+| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                        |
+| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                  |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
index fc889f9bb826a89..e55d19e7fac4ad4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
@@ -9,10 +9,11 @@ sidebar:
 head:
   - tag: title
     content: Status codes - Custom hostnames
----
 
 ---
 
+***
+
 ## Success codes
 
 | Endpoint                                                  | Method | Code         |
@@ -23,66 +24,66 @@ head:
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | DELETE | 200 OK       |
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | PATCH  | 202 Accepted |
 
----
+***
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                 |
-| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                          |
-| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                      |
-| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                |
-| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                  |
-| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                        |
-| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                           |
-| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                 |
-| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                |
-| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                          |
-| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                           |
-| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                     |
-| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                           |
-| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                    |
-| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                               |
-| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
-| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                 |
-| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                           |
-| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                            |
-| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                            |
-| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                       |
-| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                               |
-| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                      |
-| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                     |
-| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                       |
-| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                             |
-| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                           |
-| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                    |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                           |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                       |
-| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                               |
-| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                          |
-| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
-| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                             |
-| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                              |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                         |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                        |
+| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                 |
+| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                   |
+| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                         |
+| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                            |
+| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                 |
+| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                           |
+| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                            |
+| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                      |
+| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                     |
+| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                            |
+| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                        |
+| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                               |
+| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                     |
+| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                |
+| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                    |
+| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                  |
+| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                            |
+| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                             |
+| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                             |
+| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                             |
+| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                        |
+| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
+| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                   |
+| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                      |
+| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                        |
+| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                            |
+| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                     |
+| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                  |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                      |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                            |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                        |
+| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                |
+| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                           |
+| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid  customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
+| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                              |
+| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                               |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                          |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
index 7ecb44f98f46429..51109dbc3c37bd3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When you perform [TXT](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/) domain control validation, you will need to share these tokens with your customers.
 
@@ -18,9 +19,8 @@ However, these tokens expire after a certain amount of time, depending on your c
 | --------------------- | -------------- |
 | Let's Encrypt         | 7 days         |
 | Google Trust Services | 14 days        |
-| SSL.com               | 14 days        |
+| SSL.com | 14 days        |
 
 :::caution
-
-<Render file="dcv-invalid-token-situations" product="ssl" />
+ <Render file="dcv-invalid-token-situations" product="ssl" />
 :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
index b13acdc07c26874..916488e61763006 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
@@ -32,13 +32,13 @@ Using a [TXT](#dns-txt-record) or [HTTP](#http-token) validation method helps yo
 
 #### DNS TXT Record
 
-When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
+When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership\_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
 
 #### HTTP Token
 
-When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
+When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership\_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
 
-Cloudflare sends GET requests to the http_url using `User-Agent: Cloudflare Custom Hostname Verification`.
+Cloudflare sends GET requests to the http\_url using `User-Agent: Cloudflare Custom Hostname Verification`.
 
 If you validated a hostname that is not proxying traffic through Cloudflare, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app when the HTTP token is verified (under the **Custom Hostnames** tab).
 
@@ -73,8 +73,10 @@ Once the migration has been started for your zone(s), Cloudflare will require ev
 
 :::note
 
+
 You can revert the migration at any time.
 
+
 :::
 
 ### Before the migration
@@ -83,15 +85,15 @@ Before your migration, you should:
 
 1. To test validation methods, set up a test zone and ask your account team to enable SSL for SaaS v2.
 2. Wait for your account team to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
-   - `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
-   - `test_active`: Passed CNAME verification
-   - `test_active_apex`: Passed Apex Proxy verification
-   - `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
-   - `test_failed`: Failed hostname verification 25 times
+   * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
+   * `test_active`: Passed CNAME verification
+   * `test_active_apex`: Passed Apex Proxy verification
+   * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
+   * `test_failed`: Failed hostname verification 25 times
 3. Review the results of our pre-migration tool (run by your account team) using one of the following methods:
-   - Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
-   - Via a CSV file (provided by your account team)
-   - Via the Cloudflare dashboard:
+   * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
+   * Via a CSV file (provided by your account team)
+   * Via the Cloudflare dashboard:
      ![Review SSL migration status in the dashboard](~/assets/images/cloudflare-for-platforms/ssl-migration-status.png)
 4. Approve the migration. Your account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
index 2264ad62fa3dbc5..edf8ce49e980942 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Resources for SaaS customers
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare partners with many [SaaS providers](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/) to extend our performance and security benefits to your website.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
index 63c9a0ce28c29a6..0681efe793946a6 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
@@ -30,12 +30,12 @@ This is not an exhaustive list of Cloudflare products and features.
 | [China Network](/china-network/)                                                                    | No            | No                 |                                                                                                                                                                                                                                                                                                                                                                   |
 | [DNS](/dns/)                                                                                        | Yes\*         | Yes                | As a SaaS customer, do not remove the records related to your Cloudflare for SaaS setup.<br/><br/>Otherwise, your traffic will begin routing away from your SaaS provider.                                                                                                                                                                                        |
 | [HTTP/2 prioritization](https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/) | Yes           | Yes\*              | This feature must be enabled on the customer zone to function.                                                                                                                                                                                                                                                                                                    |
-| [Image resizing](/images/optimization/transformations/overview/)                                    | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Image resizing](/images/optimization/transformations/overview/)                                                         | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | IPv6                                                                                                | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [IPv6 Compatibility](/network/ipv6-compatibility/)                                                  | Yes           | Yes\*              | If the customer zone has **IPv6 Compatibility** enabled, generally the SaaS zone should as well.<br/><br/>If not, make sure the SaaS zone enables [Pseudo IPv4](/network/pseudo-ipv4/).                                                                                                                                                                           |
 | [Load Balancing](/load-balancing/)                                                                  | No            | Yes                | Customer zones can still use Load Balancing for non-O2O traffic.                                                                                                                                                                                                                                                                                                  |
 | [Page Rules](/rules/page-rules/)                                                                    | Yes\*         | Yes                | Page Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                                |
-| [Origin Rules](/rules/origin-rules/)                                                                | No            | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Origin Rules](/rules/origin-rules/)                                                                | No           | Yes                |                                                                                                                                                                                                                                       |
 | [Client-side security](/client-side-security/) (formerly Page Shield)                               | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Polish](/images/polish/)                                                                           | Yes\*         | Yes                | Polish only runs on cached assets. If the customer zone is bypassing cache for SaaS zone destined traffic, then images optimized by Polish will not be loaded from origin.                                                                                                                                                                                        |
 | [Rate Limiting](/waf/rate-limiting-rules/)                                                          | Yes\*         | Yes                | Rate Limiting rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
index cff52354c33fa79..8f5c695a4ed8b46 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
@@ -31,9 +31,9 @@ Webflow customers can enable O2O on any Cloudflare zone plan.
 
 To enable O2O for a specific hostname within a Cloudflare Zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with your Webflow site name as the target. Webflow's domain addition setup will walk you through other validation steps.
 
-| Type    | Name            | Target            | Proxy status |
-| ------- | --------------- | ----------------- | ------------ |
-| `CNAME` | `<YOUR_DOMAIN>` | `cdn.webflow.com` | Proxied      |
+| Type    | Name                 | Target                | Proxy status |
+| ------- | -------------------- | --------------------- | ------------ |
+| `CNAME` | `<YOUR_DOMAIN>`      | `cdn.webflow.com`     | Proxied      |
 
 ## Zone hold
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
index 38885b976200c1e..5f503f70abb253c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
index 335795eba693675..541ee92bd1ce3a3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Manage custom certificates
+
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs } from "~/components"
 
 Learn how to manage custom certificates for your Cloudflare for SaaS custom hostnames. For use cases and limitations, refer to [custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/).
 
@@ -85,7 +86,7 @@ To replace a single custom certificate within a certificate pack that contains t
 
 You can only replace an RSA certificate with another RSA certificate, or an ECDSA certificate with another ECDSA certificate.
 
----
+***
 
 ## Move to a Cloudflare certificate
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
index 3b173935c952ce9..4a1ffdb4234511d 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
@@ -11,15 +11,16 @@ sidebar:
 head:
   - tag: title
     content: Delegated domain control validation (DCV)
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Delegated DCV allows SaaS providers to delegate the DCV process to Cloudflare.
 
 DCV Delegation requires your customers to place a one-time record at their authoritative DNS that allows Cloudflare to auto-renew all future certificate orders, so that there is no manual intervention from you or your customers at the time of the renewal.
 
----
+***
 
 ## Setup
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
index e4cb716dca2b5d4..60f518c1628966e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting | Certificate validation
+
 ---
 
 ## High-risk domains
@@ -19,7 +20,7 @@ Occasionally, a domain will be flagged as “high risk” by Cloudflare’s CA p
 
 If a domain is flagged by the CA, you need to contact Support before validation can finish. The API call will return indicating the failure, along with a link to where the ticket can be filed.
 
----
+***
 
 ## Certificate Authority Authorization (CAA) records
 
@@ -43,26 +44,26 @@ In some cases, the validation may be prevented because your hostname points to a
 
 In this case you would need to either select a Certificate Authority whose CAA records are present at the target, or review the configuration with the service provider that owns the target.
 
----
+***
 
 ## Time outs
 
 If a certificate issuance times out, the error message will indicate where the timeout occurred:
 
-- Timed Out (Initializing)
-- Timed Out (Validation)
-- Timed Out (Issuance)
-- Timed Out (Deployment)
-- Timed Out (Deletion)
+* Timed Out (Initializing)
+* Timed Out (Validation)
+* Timed Out (Issuance)
+* Timed Out (Deployment)
+* Timed Out (Deletion)
 
 To fix this error, send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) through the API or select **Refresh** for the specific custom hostname in the dashboard. If using the API, make sure that the `--data` field contains an `ssl` object with the same `method` and `type` as the original request.
 
 If these return an error, delete and recreate the custom hostname.
 
----
+***
 
 ## Immediate validation checks
 
 You can send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) to request an immediate validation check on any certificate. The PATCH data should include the same `ssl` object as the original request.
 
----
+***
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
index 7ac9fd652e89438..3545c355b84844b 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 5
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 When you [create a webhook notification](/notifications/get-started/configure-webhooks/) for **SSL for SaaS Custom Hostnames**, you may want to automate responses to specific events (certificate issuance, failed validation, etc.).
 
@@ -26,38 +26,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.validation.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.validation.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -67,49 +67,49 @@ Cloudflare sends this alert each time a certificate remains in a `pending_valida
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.validation.failed",
-			"created_at": "2018-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_validation",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "blog.example.com reported as potential risk: google_safe_browsing"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.validation.failed",
+      "created_at": "2018-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_validation",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "blog.example.com reported as potential risk: google_safe_browsing"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate issuance
 
@@ -121,38 +121,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.issuance.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.issuance.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -162,49 +162,49 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.issuance.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "caa_error: blog.example.com"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.issuance.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "caa_error: blog.example.com"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate deployment
 
@@ -216,38 +216,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_dep
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deployment.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "active",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deployment.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "active",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -257,42 +257,42 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deployment.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deployment.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate deletion
 
@@ -302,34 +302,34 @@ Cloudflare sends this alert when certificates move from a status of `pending_del
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deletion.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "deleted"
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deletion.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "deleted"
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -339,38 +339,38 @@ Cloudflare sends this alert each time a certificate remains in status of `pendin
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deletion.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deletion"
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deletion.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deletion"
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate renewal
 
@@ -382,43 +382,43 @@ The actions that you need to perform to renew certificates depend on your [valid
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"status": "active",
-			"hosts": ["blog.example.com"],
-			"issuer": "DigiCertInc",
-			"serial_number": "1001172778337169491",
-			"signature": "ECDSAWithSHA256",
-			"uploaded_on": "2021-11-17T04:33:54.561747Z",
-			"expires_on": "2022-11-21T12:00:00Z",
-			"custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "status": "active",
+      "hosts": ["blog.example.com"],
+      "issuer": "DigiCertInc",
+      "serial_number": "1001172778337169491",
+      "signature": "ECDSAWithSHA256",
+      "uploaded_on": "2021-11-17T04:33:54.561747Z",
+      "expires_on": "2022-11-21T12:00:00Z",
+      "custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -428,38 +428,38 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -469,45 +469,45 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "caa_error: blog.example.com"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "caa_error: blog.example.com"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -521,9 +521,6 @@ This behavior is because each custom hostname can only have one certificate atta
 
 You can configure alerts to receive notifications for changes in your custom hostname certificates.
 
-<AvailableNotifications
-	product="SSL/TLS"
-	notificationFilter="SSL for SaaS Custom Hostnames Alert"
-/>
+<AvailableNotifications product="SSL/TLS" notificationFilter="SSL for SaaS Custom Hostnames Alert" />
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
index dad31a4c49f6b78..79e692861ae83d3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
@@ -6,12 +6,13 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Cloudflare for SaaS provides increased security per custom hostname through:
 
-- [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
-  - [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
-  - [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
-- Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
-- Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
+* [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
+  * [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
+  * [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
+* Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
+* Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
index 8c044e098c1a507..a9b88bc6d3f027e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
@@ -9,7 +9,7 @@ sidebar:
   label: Setup
 ---
 
-import { DashButton, APIRequest } from "~/components";
+import { DashButton, APIRequest, } from "~/components";
 
 [Web Application Firewall (WAF)](/waf/) allows you to create additional security measures through Cloudflare. As a SaaS provider, you can link custom rules, rate limiting rules, and managed rules to your custom hostnames. This provides more control to keep your domains safe from malicious traffic.
 
@@ -74,38 +74,40 @@ This assigns custom metadata to your custom hostname so that it has a security t
 2. Build your rules either [through the dashboard](/waf/custom-rules/create-dashboard/) or via the API. An example rate limiting rule, corresponding to `"security_level"` low, is shown below as an API call.
 
 <APIRequest
-	path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
-	method="PUT"
-	json={{
-		rules: [
+  path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
+  method="PUT"
+  json={{
+		"rules": [
 			{
-				action: "block",
-				ratelimit: {
-					characteristics: ["cf.colo.id", "ip.src"],
-					period: 10,
-					requests_per_period: 2,
-					mitigation_timeout: 60,
+				"action": "block",
+				"ratelimit": {
+					"characteristics": [
+						"cf.colo.id",
+						"ip.src"
+					],
+					"period": 10,
+					"requests_per_period": 2,
+					"mitigation_timeout": 60
 				},
-				expression:
-					'lookup_json_string(cf.hostname.metadata, "security_level") eq "low" and http.request.uri contains "login"',
-			},
-		],
+				"expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
+			}
+		]
 	}}
 	parameters={{
-		ruleset_phase: "http_ratelimit",
+		ruleset_phase: "http_ratelimit"
 	}}
 />
 
 To build rules through the dashboard:
 
-1.  In the Cloudflare dashboard, go to the **WAF** page.
+1. In the Cloudflare dashboard, go to the **WAF** page.
 
-        <DashButton url="/?to=/:account/application-security/waf" />
+		<DashButton url="/?to=/:account/application-security/waf" />
 
-2.  Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
+2. Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
 
-3.  Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
+3. Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
 
-    :::caution
-    This API call will replace any existing rate limiting rules in the zone.
-    :::
+   :::caution
+   This API call will replace any existing rate limiting rules in the zone.
+   :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
index 44166be7219fb59..5f74db1bcc4eac2 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /data-localization/how-to/cloudflare-for-saas/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
index e385caf0bc3f783..b3bba3fd7a2c5ea 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
@@ -55,9 +55,9 @@ You do not need to add individual Worker routes for each custom hostname. The wi
 
      For example, if your zone is `saasprovider.com` and you want `api.saasprovider.com` to bypass the Worker, create an additional route `api.saasprovider.com/*` with no Worker assigned. More specific routes take precedence over wildcard routes.
 
-   - **Route only custom hostname traffic to the Worker**:
-   - **Route**: `vanity.customer.com`
-   - **Worker**: Select the Worker used for your SaaS application.
+    - **Route only custom hostname traffic to the Worker**:
+     - **Route**: `vanity.customer.com`
+     - **Worker**: Select the Worker used for your SaaS application.
 
 5. Click **Save**.
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
index 7c32801c1a98fdd..b5e1b4537b932f3 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
@@ -9,13 +9,11 @@ sidebar:
 products:
   - cloudflare-for-platforms
 ---
-
 import { Aside } from "@astrojs/starlight/components";
 
 When you deploy User Workers through Workers for Platforms, you can attach [bindings](/workers/runtime-apis/bindings/) to give them access to resources like [KV namespaces](/kv/), [D1 databases](/d1/), [R2 buckets](/r2/), and more. This enables your end customers to build more powerful applications without you having to build the infrastructure components yourself.
 
 With bindings, each of your users can have their own:
-
 - [KV namespace](/kv/) that they can use to store and retrieve data
 - [R2 bucket](/r2/) that they can use to store files and assets
 - [Analytics Engine](/analytics/analytics-engine/) dataset that they can use to collect observability data
@@ -28,11 +26,9 @@ Each User Worker can only access the bindings that are explicitly attached to it
 ![Resource Isolation Model](~/assets/images/reference-architecture/programmable-platforms/programmable-platforms-5.svg "Resource Isolation Model")
 
 ## Adding a KV Namespace to a User Worker
-
 This example walks through how to create a [KV namespace](/kv/) and attach it to a User Worker. The same process can be used to attach to other [bindings](/workers/runtime-apis/bindings/).
 
 ### 1. Create a KV namespace
-
 Create a KV namespace using the [Cloudflare API](/api/resources/kv/subresources/namespaces/methods/bulk_update/).
 
 ### 2. Attach the KV namespace to the User Worker
@@ -62,7 +58,6 @@ curl -X PUT \
   }' \
   -F 'worker.js=@/path/to/worker.js'
 ```
-
 Now, the User Worker has can access the `USER_KV` binding through the `env` argument using `env.USER_DATA.get()`, `env.USER_DATA.put()`, and other KV methods.
 
 Note: If you plan to add new bindings to the Worker, use the `keep_bindings` parameter to ensure existing bindings are preserved while adding new ones.
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
index 9cdf87f9fd91826..6a9982c4fc08bc4 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
@@ -31,7 +31,7 @@ A [Tail Worker](/workers/observability/logs/tail-workers/) receives information
 
 Use [Tail Workers](/workers/observability/logs/tail-workers/) instead of Logpush if you want granular control over formatting before logs are sent to their destination to receive [diagnostics channel events](/workers/runtime-apis/nodejs/diagnostics-channel), or if you want logs delivered in real-time.
 
-Adding a Tail Worker to your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
+Adding a Tail Worker to  your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
 
 ## Analytics
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
index a5d3d76bafe414b..b5f72ee55754ce1 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-for-platforms
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Script limits
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
index c7998ff2541bb30..4ed59262b2ebb15 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
@@ -18,7 +18,7 @@ import {
 	ResourcesBySelector,
 } from "~/components";
 
-The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically.
+The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically. 
 
 ### Prerequisites
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
index 4842b92536a2d6c..378810ebff4dd3e 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
@@ -18,11 +18,11 @@ In untrusted mode:
 - Each Worker has an isolated cache, when using the [Cache API](/workers/runtime-apis/cache/) or when making subrequests using `fetch()`, which egress via [Cloudflare's cache](/cache/)
 - [`caches.default`](/workers/reference/how-the-cache-works/#cache-api) is disabled for all Workers in the namespace
 
-This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access.
+This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access. 
 
 ### Trusted Mode
 
-If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code.
+If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code. 
 
 In trusted mode:
 
@@ -31,10 +31,9 @@ In trusted mode:
 
 :::note
 In trusted mode, Workers can potentially access cached responses from other Workers in the namespace. Only enable this if you control all Worker code or have appropriate cache key isolation strategies.
-:::
+::: 
 
 To convert a namespace from untrusted to trusted:
-
 ```bash
 curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace_name}" \
   -H "Authorization: Bearer {api_token}" \
@@ -43,16 +42,14 @@ curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/
     "name": "{namespace_name}",
     "trusted_workers": true
   }'
-```
+  ```
 
-If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it.
+If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it. 
 
 ### Maintaining cache isolation in trusted mode
-
-If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys.
+If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
 
 ## Related Resources
-
-- [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
-- [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
-- [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
+* [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
+* [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
+* [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
index c2bc163fbb4b639..1d4db0fb3f37d82 100644
--- a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
+++ b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
@@ -12,6 +12,7 @@ sidebar:
 head:
   - tag: title
     content: Minimal suggested ruleset
+
 ---
 
 The suggested minimal ruleset blocks some known common vectors for DDoS attacks and permits all other ESP, TCP, UDP, GRE and ICMP traffic.
@@ -65,17 +66,17 @@ The information below covers traffic type, how the port is used, and reasons for
 
 The list below is a common list of traffic types you should also consider blocking or restricting inbound.
 
-- SFTP, TFTP
-- SSH, Telnet
-- RDP
-- RCP
-- SMCP
-- NTP
-  - Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
-- MS-SQL
-  - Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
-- HTTP and HTTPS
-  - If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
+* SFTP, TFTP
+* SSH, Telnet
+* RDP
+* RCP
+* SMCP
+* NTP
+  * Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
+* MS-SQL
+  * Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
+* HTTP and HTTPS
+  * If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
 
 If relevant to your environment, consider blocking based on geolocation data, which blocks traffic based on the country or user when an end user's IP address is registered in the geolocation database.
 
diff --git a/src/content/docs/cloudflare-network-firewall/index.mdx b/src/content/docs/cloudflare-network-firewall/index.mdx
index f546e7f0e9b2faa..f5c445fd27e1de4 100644
--- a/src/content/docs/cloudflare-network-firewall/index.mdx
+++ b/src/content/docs/cloudflare-network-firewall/index.mdx
@@ -20,8 +20,8 @@ import {
 } from "~/components";
 
 <Description>
-	Filter and block unwanted traffic at Cloudflare's global network, before it
-	reaches your infrastructure.
+	Filter and block unwanted traffic at Cloudflare's global network,
+	before it reaches your infrastructure.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
index 53c0015446461f2..70c21d97f76d65a 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
@@ -304,4 +304,4 @@ Due to the nature of Cloudflare network, your traffic may traverse various physi
 
 - Multiple PCAP Files: A single full PCAP capture may produce many small PCAP files, as a capture is taken for each physical server your traffic traverses in a Cloudflare location.
   - You can get more granular by applying packet-specific filters like protocol, port (and more) to target the traffic you need.
-- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
+- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
index 2ee588985ab4a4f..6f7330a2abce626 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
@@ -174,7 +174,7 @@ To start collecting packet captures with R2, you first need to configure it prop
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-   <DashButton url="/?to=/:account/r2/overview" />
+	<DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -218,4 +218,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
index 1833bff8925d2c5..190cc5e6da18dfa 100644
--- a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
+++ b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
@@ -21,9 +21,9 @@ Traffic passing through Cloudflare's network is evaluated by several independent
 Each system operates independently. Traffic blocked by an earlier system never reaches later systems for evaluation.
 
 :::caution
-Creating an allow rule in Network Firewall does **not** bypass DDoS
-protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
-rules, you must configure bypasses in those systems separately.
+	Creating an allow rule in Network Firewall does **not** bypass DDoS
+	protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
+	rules, you must configure bypasses in those systems separately.
 :::
 
 To diagnose blocked traffic, use [Network Analytics](/analytics/network-analytics/) to identify which system is blocking the traffic and why. If Network Analytics does not provide enough information, you can use packet captures for deeper analysis.
@@ -99,4 +99,4 @@ If you cannot identify the issue from Network Analytics, use [packet captures](/
 - [Network Analytics](/analytics/network-analytics/)
 - [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/)
 - [Network Firewall rule configuration](/cloudflare-network-firewall/how-to/add-policies/)
-- [Packet captures](/cloudflare-network-firewall/packet-captures/)
+- [Packet captures](/cloudflare-network-firewall/packet-captures/)
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
index 3b09b3e2ad4da6e..24eaf60c6cf1b66 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
index 69fc5cb5e2e1111..db274e1c338cdc3 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
@@ -7,7 +7,7 @@ title: Require Access protection
 sidebar:
   order: 3
 tags:
-  - Security
+- Security
 ---
 
 Cloudflare Access allows you to require Access protection for all hostnames in your account. When this setting is turned on, traffic to any hostname without a matching [Access application](/cloudflare-one/access-controls/applications/) is automatically blocked.
@@ -23,13 +23,13 @@ Turning on Access protection blocks traffic to any hostname that does not have a
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **Zero Trust** > **Access controls** > **Access settings**.
 2. Turn on **Block traffic to all domains in this account**. You will see a dialog confirming you understand the scope of this change. Select **Confirm**.
 
-   Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
+	Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
 
 3. (Optional) Under **Hostnames to Exempt**, select specific domains to exempt from the **Block traffic to all domains in this account** setting. Traffic to exempted hostnames is allowed even if no Access application exists.
 
-   :::note
-   Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
-   :::
+	:::note
+	Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
+	:::
 
 ## Allow traffic to a hostname
 
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
index d74a4f8adf061e0..d5cc04f026c092a 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
@@ -100,7 +100,6 @@ Users who match a policy configured with a _Same as application session timeout_
 When [Authenticate with Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/#configure-client-sessions-in-access) is enabled for an Access application, the Cloudflare One Client session duration takes precedence over all other session durations (application, policy, and global). As long as the Cloudflare One Client session is valid and the user is running the Cloudflare One Client, the user will not be prompted to re-authenticate with the IdP — even if the global session has expired.
 
 ### MFA session duration
-
 If you use [independent multi-factor authentication (MFA)](/cloudflare-one/access-controls/access-settings/independent-mfa/), the MFA session duration determines how long a user can log in to Cloudflare Access without being prompted for MFA. The MFA session is independent of the global, policy, and application session durations. When logging in to an Access app with [MFA enabled](/cloudflare-one/access-controls/policies/mfa-requirements/#configure-independent-mfa-for-an-application), users must complete an MFA challenge if their last MFA authentication falls outside the configured session duration. After authenticating with their identity provider, users are prompted for MFA. The [`CF_Device` cookie](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#cf_device) ensures both authentication steps occur on the same device. MFA session durations do not affect how long a user has access to the application (that is controlled by the [application token](#session-durations)).
 
 ### Order of enforcement
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
index f387963685b0849..603b94d330906d6 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
index f4dd978b1db79a4..cfff5ab05a7f8ee 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
@@ -179,9 +179,9 @@ You can assign aliases to tools to give them clearer names in the portal. Aliase
 
 Aliases can be set at two levels:
 
-| Level            | Field          | Scope                                                                                   |
-| ---------------- | -------------- | --------------------------------------------------------------------------------------- |
-| **Server-level** | `alias`        | Applies to the tool across all portals that include this server                         |
+| Level | Field | Scope |
+| ----- | ----- | ----- |
+| **Server-level** | `alias` | Applies to the tool across all portals that include this server |
 | **Portal-level** | `portal_alias` | Applies only within this specific portal and takes priority over the server-level alias |
 
 When a tool has multiple names configured, the portal uses the following priority order: `portal_alias` > `server_alias` > `alias` > original tool name.
@@ -245,11 +245,11 @@ Unlike the dashboard, the API does not automatically create a DNS record for you
 
 The `auth_type` field accepts the following values:
 
-| Value             | Description                                                                                                                                          |
-| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `oauth`           | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
-| `bearer`          | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`.                                                   |
-| `unauthenticated` | The server does not require authentication.                                                                                                          |
+| Value | Description |
+| ----- | ----------- |
+| `oauth` | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
+| `bearer` | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`. |
+| `unauthenticated` | The server does not require authentication. |
 
 ### Force sync an MCP server
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
index 8b12f3259058db0..b342006708c137a 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
@@ -57,18 +57,18 @@ The payload contains the actual claim and user information to pass to the applic
 }
 ```
 
-| Field          | Description                                                                                                                                                                                                                                                                                               |
-| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                |
-| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                           |
-| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                                       |
-| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                                         |
-| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                                     |
-| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                                     |
-| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                                 |
-| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                            |
+| Field          | Description                                                                                                                                                                                                                                                                                     |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                                    |
+| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                 |
+| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                             |
+| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                               |
+| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                           |
+| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                           |
+| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                       |
+| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                  |
 | sub            | The ID of the user. This value is unique to an email address per account. The user would get a different `sub` if they are [removed](/cloudflare-one/team-and-resources/users/seat-management/#remove-a-user) and re-added to your Zero Trust organization, or if they log into a different organization. |
-| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                            |
+| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                  |
 
 #### Custom SAML attributes and OIDC claims
 
@@ -86,26 +86,26 @@ curl -H 'cookie: CF_Authorization=<user-token>' https://<your-team-name>.cloudfl
 
 Access will return a JSON structure containing the following data:
 
-| Field                | Description                                                                                |
-| -------------------- | ------------------------------------------------------------------------------------------ |
-| email                | The email address of the user.                                                             |
-| idp                  | Data from your identity provider.                                                          |
-| geo                  | The country where the user authenticated from.                                             |
-| user_uuid            | The ID of the user.                                                                        |
-| devicePosture        | The device posture attributes.                                                             |
-| account_id           | The account ID for your organization.                                                      |
-| iat                  | The timestamp indicating when the user logged in.                                          |
-| ip                   | The IP address of the user.                                                                |
-| auth_status          | The status if authenticating with mTLS.                                                    |
-| common_name          | The common name on the mTLS client certificate.                                            |
-| service_token_id     | The Client ID of the service token used for authentication.                                |
-| service_token_status | True if authentication was through a service token instead of an IdP.                      |
-| is_warp              | True if the user enabled WARP.                                                             |
-| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team. |
-| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team.      |
-| device_id            | The ID of the device used for authentication.                                              |
-| version              | The version of the `get-identity` object.                                                  |
-| device_sessions      | A list of all sessions initiated by the user.                                              |
+| Field                | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| email                | The email address of the user.                                              |
+| idp                  | Data from your identity provider.                                           |
+| geo                  | The country where the user authenticated from.                              |
+| user_uuid            | The ID of the user.                                                         |
+| devicePosture        | The device posture attributes.                                              |
+| account_id           | The account ID for your organization.                                       |
+| iat                  | The timestamp indicating when the user logged in.                           |
+| ip                   | The IP address of the user.                                                 |
+| auth_status          | The status if authenticating with mTLS.                                     |
+| common_name          | The common name on the mTLS client certificate.                             |
+| service_token_id     | The Client ID of the service token used for authentication.                 |
+| service_token_status | True if authentication was through a service token instead of an IdP.       |
+| is_warp              | True if the user enabled WARP.                                              |
+| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team.       |
+| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team. |
+| device_id            | The ID of the device used for authentication.                               |
+| version              | The version of the `get-identity` object.                                   |
+| device_sessions      | A list of all sessions initiated by the user.                               |
 
 ### Service token authentication
 
@@ -121,15 +121,15 @@ Access will return a JSON structure containing the following data:
 }
 ```
 
-| Field       | Description                                                                                                                                                                    |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| type        | The type of Access token (`app` for application token or `org` for global session token).                                                                                      |
+| Field       | Description                                                                                                                                      |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| type        | The type of Access token (`app` for application token or `org` for global session token).                                                        |
 | aud         | The [application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application. |
-| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                                               |
-| iss         | The Cloudflare Access domain URL for the application.                                                                                                                          |
-| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                                                    |
-| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                                                 |
-| sub         | Contains an empty string when authentication was through a service token.                                                                                                      |
+| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                 |
+| iss         | The Cloudflare Access domain URL for the application.                                                                                            |
+| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                      |
+| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                   |
+| sub         | Contains an empty string when authentication was through a service token.                                                                        |
 
 ## Signature
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
index 3917b42fff99c6f..6ac256251bea1e9 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
@@ -197,10 +197,7 @@ export default {
 		const newRequest = new Request(url.toString(), request);
 
 		newRequest.headers.set("cf-access-client-id", env.CF_ACCESS_CLIENT_ID);
-		newRequest.headers.set(
-			"cf-access-client-secret",
-			env.CF_ACCESS_CLIENT_SECRET,
-		);
+		newRequest.headers.set("cf-access-client-secret", env.CF_ACCESS_CLIENT_SECRET);
 		try {
 			const response = await fetch(newRequest);
 
@@ -230,7 +227,7 @@ npx wrangler deploy
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
+	<DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select your newly created Worker.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
index 03576d37f7ff815..5b1182c9666a6e2 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
@@ -188,13 +188,13 @@ The authorization flow proceeds as follows:
 
 Both managed OAuth and [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) allow non-browser clients to authenticate with Access-protected applications, but they serve different use cases:
 
-|                           | Managed OAuth                                                                    | Service tokens                                                                                  |
-| ------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| **Authentication model**  | User-based — the end user logs in through their identity provider                | Machine-based — a shared secret authenticates the service itself                                |
-| **Best for**              | Interactive CLI tools, AI agents, SDKs where a human initiates the request       | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication             |
-| **User identity**         | Access knows which user made the request                                         | No user identity — requests are attributed to the service token                                 |
-| **Policy enforcement**    | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
-| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials  | Requires distributing and rotating Client ID and Client Secret                                  |
+| | Managed OAuth | Service tokens |
+| --- | --- | --- |
+| **Authentication model** | User-based — the end user logs in through their identity provider | Machine-based — a shared secret authenticates the service itself |
+| **Best for** | Interactive CLI tools, AI agents, SDKs where a human initiates the request | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication |
+| **User identity** | Access knows which user made the request | No user identity — requests are attributed to the service token |
+| **Policy enforcement** | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
+| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials | Requires distributing and rotating Client ID and Client Secret |
 
 Use managed OAuth when you want non-browser clients to authenticate users the same way a browser would — the user logs in once, and the client receives an OAuth token to make requests on their behalf.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
index cadc87d1fda6ab5..52fef67da2246a1 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
@@ -59,15 +59,12 @@ Some SaaS applications provide the Redirect URL after you [configure the SSO pro
 
 11. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-12. <Render
-    	file="access/access-choose-idps"
-    	product="cloudflare-one"
-    	params={{ appType: "saas" }}
-    />
+12. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "saas" }}/>
 
 13. (Optional) Go to **Additional settings** to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
-    - <Render file="access/access-block-page" product="cloudflare-one" />
+
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
+	- <Render file="access/access-block-page" product="cloudflare-one" />
 
 14. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
index cee76077b2de270..c554be332b64448 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-  - SSO
+- SSO
 ---
 
 This guide covers how to configure [Grafana Cloud](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/authorization/#configure-oauth-20-with-generic-oauth) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
index c343d9ad68ce913..b7a904dc94c5681 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-  - SSO
+- SSO
 ---
 
 This guide covers how to configure [Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
index 01dc8bf2c1ccd20..3118fcac0cec9c2 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
@@ -6,9 +6,10 @@ products:
 title: SaaS applications
 sidebar:
   order: 1
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare Access allows you to add an additional authentication layer to your SaaS applications. When you integrate a SaaS application with Access, users log in to the application with Cloudflare as the Single Sign-On provider. The user is then redirected to the configured identity providers for that application and are only granted access if they pass your Access policies.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
index 2cfa346e15fc6c3..ae83f5143d310dc 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
@@ -7,8 +7,8 @@ title: Browser-rendered terminal
 sidebar:
   order: 3
 tags:
-  - SSH
-  - RDP
+- SSH
+- RDP
 ---
 
 import { Render } from "~/components";
@@ -31,10 +31,7 @@ To turn on browser rendering for an SSH or VNC application:
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/). Select **Configure**.
 3. Turn on **Allow access through browser-based RDP, SSH, or VNC sessions**, then select _SSH_ or _VNC_.
-   <Render
-   	file="access/self-hosted-app/browser-rendering-policies"
-   	product="cloudflare-one"
-   />
+	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
 4. Select **Save**.
 
 When users authenticate and visit the URL of the application, Cloudflare will render a terminal in their browser.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
index 203505a89c9fa0e..e0badb2c31fe6c0 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
@@ -7,8 +7,8 @@ title: Arbitrary TCP
 sidebar:
   order: 11
 tags:
-  - TCP
-  - SSH
+- TCP
+- SSH
 ---
 
 Cloudflare Access provides a mechanism for end users to authenticate with their single sign-on (SSO) provider and connect to resources over arbitrary TCP without being on a virtual private network (VPN).
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
index 242e714857c5c7a..0e09be8ca535069 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
@@ -7,7 +7,7 @@ title: Enable automatic cloudflared authentication
 sidebar:
   order: 2
 tags:
-  - Authentication
+- Authentication
 ---
 
 When users connect to an Access application through `cloudflared`, the browser prompts them to allow access by displaying this page:
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
index 7b753f951aa5916..2f0c700b0197311 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
   label: Private network applications (legacy)
 tags:
-  - Private networks
+- Private networks
 ---
 
 :::caution
@@ -35,6 +35,7 @@ Existing **Private Network** applications continue to function and can still be
 7. Select **Next**. You will see two auto-generated Gateway Network policies: one that allows access to the destination IP and another that blocks access.
 
 8. Modify the policies to include additional identity-based conditions. For example:
+
    - **Policy 1**
 
      | Selector       | Operator      | Value            | Logic | Action |
@@ -52,4 +53,4 @@ Existing **Private Network** applications continue to function and can still be
 
 9. Select **Add application**.
 
-Your application will appear on the **Applications** page.
+Your application will appear on the **Applications** page.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
index 4b7341a9ec0afcb..00a20e37e19d6cb 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
@@ -11,7 +11,7 @@ sidebar:
   label: Add a self-hosted private application
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip, } from "~/components";
 
 You can configure a self-hosted Access application to manage access to specific IPs or hostnames on your private network.
 
@@ -28,59 +28,54 @@ This feature replaces the legacy [private network app type](/cloudflare-one/acce
 
 ## Add your application to Access
 
-1.  In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
-2.  Select **Create new application**.
+2. Select **Create new application**.
 
-3.  Select **Self-hosted and private**.
+3. Select **Self-hosted and private**.
 
-4.  To add an application using its private IP: 1. Select **Add private IP**. 2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`). 3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+4.  To add an application using its private IP:
+		1. Select **Add private IP**.
+		2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`).
+		3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-        	Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
+			Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
 
-5.  To add an application using its private hostname:
-    1. Select **Add private hostname**.
-    2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
-    3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+5. To add an application using its private hostname:
+	1. Select **Add private hostname**.
+	2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
+	3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-    :::note
-    - **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
-    - **Non-HTTPS applications**: Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
+	:::note
+	- **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
+	- **Non-HTTPS applications**:  Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
 
-      <Render
-      	file="gateway/egress-selector-cgnat-ips"
-      	product="cloudflare-one"
-      />
+		<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one"/>
 
-      For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
+		For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
 
 6.  <Render file="access/add-access-policies" product="cloudflare-one" />
-7.  <Render
-    	file="access/access-choose-idps"
-    	product="cloudflare-one"
-    	params={{ appType: "private" }}
-    />
+7.  <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "private" }}/>
 
-8.  <Render file="access/configure-independent-mfa" product="cloudflare-one" />
+8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
-9.  <Render file="access/session-duration" product="cloudflare-one" />
+9. <Render file="access/session-duration" product="cloudflare-one" />
 
-    If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
+   If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-    - **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
 
-      :::note
-      Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
-      :::
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	- **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
+
+		:::note
+		Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
+		:::
+
+	- <Render file="access/access-block-page" product="cloudflare-one" />
+	- The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
+		<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
 
-    - <Render file="access/access-block-page" product="cloudflare-one" />
-    - The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
-      <Render
-      	file="access/self-hosted-app/advanced-settings"
-      	product="cloudflare-one"
-      />
 
 11. Select **Create**.
 
@@ -118,11 +113,8 @@ An Access application defined by a private hostname takes precedence over an Acc
 
 ### Browser Isolation is not compatible with apps on non-`443` ports
 
-<Render
-	file="access/self-hosted-app/browser-isolation-non-443"
-	product="cloudflare-one"
-/>
+<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
 
 ### Google Chrome restricts access to private hostnames
 
-<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one" />
+<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one"/>
diff --git a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
index 2de16fa32411bf7..3dfe9164a038ef3 100644
--- a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Available Access events
 
-<Render file="event-subscriptions/access-events" product="queues" />
+<Render file="event-subscriptions/access-events" product="queues" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
index 899ed27993f86f3..1c0b4d46c3a4704 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
@@ -6,6 +6,7 @@ products:
 title: Application paths
 sidebar:
   order: 5
+
 ---
 
 Application paths define the URLs protected by an Access policy. When adding a self-hosted application to Access, you can choose to protect the entire website by entering its apex domain, or alternatively, protect specific subdomains and paths.
@@ -26,9 +27,9 @@ When you create an application for a specific subdomain or path, you can use ast
 
 A wildcard in the **Subdomain** field only matches that specific subdomain level. It does not cover the apex domain or multiple levels of the subdomain. If you want to cover multiple subdomain levels, you can use multiple wildcards.
 
-| Application     | Covers                                       | Does not cover                            |
-| --------------- | -------------------------------------------- | ----------------------------------------- |
-| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com` |
+| Application     | Covers                                       | Does not cover |
+| --------------- | -------------------------------------------- | -------------- |
+| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com`  |
 
 #### Match all paths of an apex domain
 
@@ -42,9 +43,9 @@ To protect an apex domain and all of the paths under it, leave the **Path** fiel
 
 Using a wildcard in the **Subdomain** field does not cover the parent subdomain nor the apex domain.
 
-| Application          | Covers                                                 | Does not cover                         |
-| -------------------- | ------------------------------------------------------ | -------------------------------------- |
-| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com` <br/> `example.com` |
+| Application          | Covers                                                 | Does not cover                          |
+| -------------------- | ------------------------------------------------------ | --------------------------------------- |
+| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com`  <br/> `example.com` |
 
 #### Partially match subdomains
 
@@ -72,8 +73,8 @@ Using a wildcard in the middle of the **Path** field covers multiple segments of
 
 ### Limitations
 
-- At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
-- At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
+* At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
+* At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
 
 ## Subdomain setups
 
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
index e08ee885d64e235..c8ec944860e8d4b 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
@@ -145,29 +145,29 @@ When you add a rule to your Cloudflare Access policy, you will be asked to speci
 
 Non-identity attributes are polled continuously, meaning they are evaluated with each new HTTP request for changes during the [user session](/cloudflare-one/access-controls/access-settings/session-management/). If you have configured [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/), you can force a user to re-attest all attributes with Access whenever you revoke the user in the IdP or update their IdP group membership.
 
-| Selector                  | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
-| Emails                    | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Emails ending in          | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
-| External Evaluation       | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
-| IP ranges                 | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
-| Country                   | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
-| Everyone                  | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
-| Common Name               | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
-| Valid Certificate         | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Service Token             | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Any Access Service Token  | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
-| User Risk Score           | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
-| Linked App Token          | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                      | ✅               | ✅                               | ❌                       |
-| Login Methods             | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
-| Authentication Method     | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
-| Identity provider group   | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
-| SAML Group                | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
-| OIDC Claim                | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Device posture            | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
-| Warp                      | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
-| Gateway                   | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
-| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                               | ✅               | ❌                               | ✅                       |
+| Selector                 | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
+| Emails                   | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Emails ending in         | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
+| External Evaluation      | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
+| IP ranges                | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
+| Country                  | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
+| Everyone                 | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
+| Common Name              | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
+| Valid Certificate        | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Service Token            | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Any Access Service Token | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
+| User Risk Score          | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
+| Linked App Token         | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                   | ✅               | ✅                               | ❌                       |
+| Login Methods            | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
+| Authentication Method    | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
+| Identity provider group  | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
+| SAML Group               | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
+| OIDC Claim               | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Device posture           | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
+| Warp                     | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
+| Gateway                  | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
+| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                                | ✅               | ❌                               | ✅                       |
 
 <sup>1</sup> For SaaS applications, Access can only enforce policies at the time
 of initial sign on and when reissuing the SaaS session. Once the user has
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
index 11eeaa22045b223..7213c910db20077 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
@@ -54,7 +54,7 @@ To delete a reusable Access policy:
 
 ## Test your policies
 
-You can test your Access policies against all existing user identities in your Zero Trust organization. For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
+You can test your Access policies against all existing user identities in your Zero Trust organization.  For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
 
 Cloudflare will use the most recent device that was authenticated with Access to test your policies.
 
@@ -76,22 +76,25 @@ You can test your Access application policies against your user population befor
 
 To test if users have access to an application:
 
-1.  In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
-2.  Locate the application you want to test and select **Configure**.
-3.  Go to **Policies** > **Policy tester**.
-4.  To test all active users in your organization, select **Test policies**.
+1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+2. Locate the application you want to test and select **Configure**.
+3. Go to **Policies** > **Policy tester**.
+4. To test all active users in your organization, select **Test policies**.
 
-        The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
+		The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
 
-5.  To perform a detailed test on a single user:
+5. To perform a detailed test on a single user:
 
-    a. If you made any changes to your policies, first save the application.
+	a. If you made any changes to your policies, first save the application.
 
-    b. Select **testing a single user**.
+	b. Select **testing a single user**.
 
-    c. Enter their email address and select **Test policies**.
+	c. Enter their email address and select **Test policies**.
 
-    The single user test results will show: - Whether the user is allowed or denied access to this application based on all configured policies. - The user's identity from their most recent Access login attempt. - Whether the user matches individual Allow, Block, or Bypass policies.
+	The single user test results will show:
+		- Whether the user is allowed or denied access to this application based on all configured policies.
+		- The user's identity from their most recent Access login attempt.
+		- Whether the user matches individual Allow, Block, or Bypass policies.
 
 ## Legacy policies
 
@@ -111,8 +114,8 @@ To migrate legacy policies to reusable policies:
 You can use the API to convert a legacy policy into a reusable policy. To convert a legacy policy, make a `PUT` request with an empty request body:
 
 <APIRequest
-	path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
-	method="PUT"
+  path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
+  method="PUT"
 />
 
 The policy is now removed from the applications endpoint (`/access/apps/$APP_ID/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/$POLICY_ID`).
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
index 3759f0ffb3db29b..ef3c106a4c83c56 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Require purpose justification after login
+
 ---
 
 Cloudflare Access allows security and IT teams to present users with a purpose justification screen directly after they log in to an Access application. This allows organizations to audit not only for who is accessing their resources, but also for why they are requesting access.
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
index a3fccad67a5f5e6..3c320499e0997ac 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
@@ -7,7 +7,7 @@ title: Temporary authentication
 sidebar:
   order: 11
 tags:
-  - Authentication
+- Authentication
 ---
 
 With Cloudflare Access, you can require that users obtain approval before they can access a specific self-hosted application or SaaS application. The administrator will receive an email notification to approve or deny the request. Unlike a typical Allow policy, the user will have to request access at the end of each session. This allows you to define the users who should have persistent access and those who must request temporary access.
@@ -20,9 +20,9 @@ With Cloudflare Access, you can require that users obtain approval before they c
 4. Under **Additional settings**, turn on [**Purpose justification**](/cloudflare-one/access-controls/policies/require-purpose-justification/).
 5. Turn on **Temporary authentication**.
 6. Enter the **Email addresses of the approvers**.
-   :::note
-   Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
-   :::
+	:::note
+	Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	:::
 7. Save the policy.
 
 Temporary authentication is now enabled for users who match this policy. You can optionally add a second **Allow** policy for users who should have persistent access. Be sure the policy order is set to allow persistent users through.
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
index a9f7713dccc5a33..7ff124cd8eb6d90 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
index 28d4336eca249b9..64603599f027224 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
@@ -7,8 +7,8 @@ title: Service tokens
 sidebar:
   order: 6
 tags:
-  - JSON web token (JWT)
-  - Authentication
+- JSON web token (JWT)
+- Authentication
 ---
 
 import {
diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index 2b66eb6b6433481..e29b38b2b415178 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -62,19 +62,19 @@ This page lists the default account limits for rules, applications, fields, and
 
 ## Cloudflare Tunnel
 
-| Feature                                            | Limit                               |
-| -------------------------------------------------- | ----------------------------------- |
-| `cloudflared` tunnels per account                  | 1,000                               |
+| Feature                                            | Limit |
+| -------------------------------------------------- | ----- |
+| `cloudflared` tunnels per account                  | 1,000 |
 | Routes (CIDR routes + Hostname routes) per account | 1,000 (shared with Cloudflare Mesh) |
-| Active `cloudflared` replicas per tunnel           | 25                                  |
-| Virtual networks per account                       | 1,000                               |
+| Active `cloudflared` replicas per tunnel           | 25    |
+| Virtual networks per account                       | 1,000 |
 
 ## Cloudflare Mesh
 
-| Feature                          | Limit                                 |
-| -------------------------------- | ------------------------------------- |
-| Mesh nodes per account           | 50                                    |
-| Routes (CIDR routes) per account | 1,000 (shared with Cloudflare Tunnel) |
+| Feature                                            | Limit |
+| -------------------------------------------------- | ----- |
+| Mesh nodes per account                             | 50    |
+| Routes (CIDR routes) per account                   | 1,000 (shared with Cloudflare Tunnel) |
 
 ## Digital Experience Monitoring (DEX)
 
@@ -106,7 +106,6 @@ This page lists the default account limits for rules, applications, fields, and
 | Gateway API policy expression | 140,000         |
 
 ## Cloudflare One Client
-
 | Feature                                                                    | Limit  |
 | -------------------------------------------------------------------------- | ------ |
 | Characters per device profile expression                                   | 10,000 |
diff --git a/src/content/docs/cloudflare-one/changelog/tunnel.mdx b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
index 5c1f6285b4348a4..7d4677d85c9b423 100644
--- a/src/content/docs/cloudflare-one/changelog/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog, Render } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
+<ProductChangelog
+	product="tunnel"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-17
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
index 508f0cb7179a5a0..64994724c683773 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
@@ -29,13 +29,13 @@ Templates provide Cloudflare-managed starting points for sensitivity schemas and
 
 Data Classification works alongside detection entries and DLP profiles.
 
-| Component         | What it does                                                                                                            |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| Component | What it does |
+| --- | --- |
 | Detection entries | Detect specific content such as patterns, datasets, document fingerprints, AI prompt topics, and predefined detections. |
-| Labels            | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content.        |
-| Templates         | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups.                                 |
-| Data classes      | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags.      |
-| DLP profiles      | Apply detection and classification logic to DLP scanning and enforcement workflows.                                     |
+| Labels | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content. |
+| Templates | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups. |
+| Data classes | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags. |
+| DLP profiles | Apply detection and classification logic to DLP scanning and enforcement workflows. |
 
 In general, detection entries help identify sensitive content. Data Classification helps organize and label that content so administrators can identify its severity, understand where it exists, and apply it consistently. DLP profiles then apply that logic to scanning and enforcement workflows.
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
index 2e931248090f21d..76a268ab8c5fbda 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
@@ -182,16 +182,16 @@ Your new document entry will replace the original document entry. If your file u
 
 DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
 
-| Detection entry                       | Description                                                                                       |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| Content: PII                          | Prompt contains personal information such as names, SSNs, or email addresses.                     |
-| Content: Credentials and Secrets      | Prompt contains API keys, passwords, or other sensitive credentials.                              |
-| Content: Source Code                  | Prompt contains actual source code, code snippets, or proprietary algorithms.                     |
-| Content: Customer Data                | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
-| Content: Financial Information        | Prompt contains financial numbers or confidential business data.                                  |
-| Intent: PII                           | Prompt requests specific personal information about individuals.                                  |
-| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities.                      |
-| Intent: Jailbreak                     | Prompt attempts to circumvent AI security policies.                                               |
+| Detection entry | Description |
+| --- | --- |
+| Content: PII | Prompt contains personal information such as names, SSNs, or email addresses. |
+| Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials. |
+| Content: Source Code | Prompt contains actual source code, code snippets, or proprietary algorithms. |
+| Content: Customer Data | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
+| Content: Financial Information | Prompt contains financial numbers or confidential business data. |
+| Intent: PII | Prompt requests specific personal information about individuals. |
+| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities. |
+| Intent: Jailbreak | Prompt attempts to circumvent AI security policies. |
 
 Each detection entry is categorized as either **Content** or **Intent**:
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
index e948a705b784d4a..ccd073189323e6d 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
@@ -14,151 +14,151 @@ Predefined detection entries are Cloudflare-managed detections for specific type
 
 You can add any predefined detection entry directly to a custom [DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/#build-a-custom-profile) or [data class](/cloudflare-one/data-loss-prevention/data-classification/build-a-data-class/). Use the following reference to review all predefined detection entries currently supported by Cloudflare DLP.
 
-| Detection entry                                      | Description                                                                                                                                                                  |
-| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| AI Prompt Content: Credentials and Secrets           | Prompt contains API keys, passwords, or other sensitive credentials                                                                                                          |
-| AI Prompt Content: Customer data                     | Prompt contains customer names, projects, business activities, or confidential customer contexts                                                                             |
-| AI Prompt Content: Financial Information             | Prompt contains actual financial numbers or confidential business data                                                                                                       |
-| AI Prompt Content: PII                               | Prompt contains personal information (names, SSNs, emails, etc.)                                                                                                             |
-| AI Prompt Content: Source code                       | Prompt contains source code, code snippets, or proprietary algorithms                                                                                                        |
-| AI Prompt Intent: Code Abuse and Malicious Code      | Malicious code or attempts to exploit vulnerabilities                                                                                                                        |
-| AI Prompt Intent: Jailbreak                          | Prompt attempts to circumvent security policies                                                                                                                              |
-| AI Prompt Intent: PII                                | Prompt requests specific personal information about individuals                                                                                                              |
-| Amazon AWS Access Key ID                             | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`.                                                                                                             |
-| Amazon AWS Secret Access Key                         | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`.                                                                                           |
-| American Express Card Number                         | Detects American Express credit card numbers such as "378282246310005".                                                                                                      |
-| American Express Text                                | Detects mentions of the American Express brand name such as "American Express".                                                                                              |
-| AU Passport Number                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
-| Australia Address                                    | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000".                                                                        |
-| Australia Business (ABN)                             | Detects Australian Business Numbers (ABN) such as "51 824 753 556".                                                                                                          |
-| Australia Company (ACN)                              | Detects Australian Company Numbers (ACN) such as "001 000 004".                                                                                                              |
-| Australia Medicare                                   | Detects Australian Medicare card numbers such as "2000000006".                                                                                                               |
-| Australia Passport                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
-| Australia Tax File Number                            | Detects Australian Tax File Numbers (TFN) such as "85 655 734".                                                                                                              |
-| Austria SSN (SV-Nummer)                              | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180".                                                                                                  |
-| Austria Tax ID                                       | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789".                                                                                            |
-| Austria VAT (UID)                                    | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678".                                                                                                             |
-| Belgium Tax ID (NN)                                  | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61".                                                                          |
-| Belgium VAT                                          | Detects Belgian VAT numbers such as "BE0000000097".                                                                                                                          |
-| Bitcoin Wallet                                       | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2".                                                                                               |
-| Brazil CNPJ                                          | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81".                                                                                   |
-| Brazil CPF (Tax ID)                                  | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25".                                                                                       |
-| Bulgaria Uniform Civil (EGN)                         | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007".                                                                                                          |
-| C                                                    | Detects C source code.                                                                                                                                                       |
-| C#                                                   | Detects C# source code.                                                                                                                                                      |
-| C++                                                  | Detects C++ source code.                                                                                                                                                     |
-| Canada Bank Account Number                           | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567".                                                                         |
-| Canada Health Number                                 | Detects Canadian provincial health card numbers such as "1234-567-897".                                                                                                      |
-| Canada Passport                                      | Detects Canadian passport numbers such as "AB123456".                                                                                                                        |
-| Canada PHIN (Manitoba)                               | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009".                                                                                          |
-| Canada Physical Address                              | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1".                                                                                |
-| Canada Social Insurance Number                       | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474".                                                                                                       |
-| Chile National ID (RUT)                              | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5".                                                                         |
-| China ID Card                                        | Detects Chinese resident identity card numbers such as "11010519491231002X".                                                                                                 |
-| Cloudflare Account Owned API Token                   | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`.                                                                                        |
-| Cloudflare User API Key                              | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`.                                                                                                               |
-| Cloudflare User API Token                            | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`.                                                                                                          |
-| Croatia Personal ID (OIB)                            | Detects Croatian personal identification numbers (OIB) such as "10000000005".                                                                                                |
-| Denmark Tax (CPR)                                    | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008".                                                                                           |
-| Diners Club Card Number                              | Detects Diners Club credit card numbers such as "30121690374838".                                                                                                            |
-| Discord Webhook                                      | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`.                                                                                        |
-| Email Address                                        | Detects email addresses such as "test@example.com".                                                                                                                          |
-| Ethereum Wallet                                      | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F".                                                                                      |
-| EU Passport                                          | Detects EU member state passport numbers such as "AB1234567".                                                                                                                |
-| FDA Active Ingredients                               | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB".                                                                                                   |
-| FDA Drug Names                                       | Detects FDA-registered drug names such as "ABACAVIR".                                                                                                                        |
-| Finland Tax ID                                       | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y".                                                                                        |
-| France CNI (National ID)                             | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901".                                                                            |
-| France Passport                                      | Detects French passport numbers such as "12AB34567".                                                                                                                         |
-| France Social Security Number                        | Detects French social security (INSEE) numbers such as "145081849670637".                                                                                                    |
-| France Tax ID (SPI)                                  | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123".                                                                                       |
-| France VAT                                           | Detects French VAT numbers such as "FR12000000000".                                                                                                                          |
-| Full Name                                            | Detects personal full names.                                                                                                                                                 |
-| Generic CVV Card Number                              | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033".                                                                          |
-| Germany Tax ID                                       | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005".                                                                               |
-| Germany VAT                                          | Detects German VAT numbers (USt-IdNr) such as "DE100000003".                                                                                                                 |
-| GitHub PAT                                           | Detects GitHub personal access tokens such as a token beginning with `ghp_`.                                                                                                 |
-| Go                                                   | Detects Go source code.                                                                                                                                                      |
-| Google GCP API Key                                   | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`.                                                                                                              |
-| Greece Tax (AFM)                                     | Detects Greek tax identification numbers (AFM) such as "100000003".                                                                                                          |
-| Haskell                                              | Detects Haskell source code.                                                                                                                                                 |
-| Hong Kong Identity Card Number                       | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)".                                                                                                         |
-| Hungary Tax                                          | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008".                                                                                        |
-| IBAN                                                 | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59".                                                                                     |
-| ICD-10 FY2023 Short Description                      | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified".                                                                                          |
-| ICD-11 Short Description                             | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS".                                                                                                    |
-| India Aadhaar                                        | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124".                                                                                             |
-| India GST (GSTIN)                                    | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5".                                                                              |
-| India PAN Card                                       | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F".                                                                                         |
-| India Voter ID                                       | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567".                                                                                                                 |
-| Indonesia Identity Card Number                       | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011".                                                                                               |
-| Indonesia Tax (NPWP)                                 | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345".                                                                                    |
-| Ireland Tax (PPS)                                    | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA".                                                                                                     |
-| Ireland VAT                                          | Detects Ireland VAT numbers such as "IE1234567T".                                                                                                                            |
-| Italy Fiscal Code                                    | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z".                                                                                                    |
-| Japan Address                                        | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001".                                                                                   |
-| Japan My Number (Corp)                               | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002".                                                                                      |
-| Japan My Number (Person)                             | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005".                                                                                      |
-| Japan Names (Kanji)                                  | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎".                                                                            |
-| Japan Passport                                       | Detects Japanese passport numbers such as "TZ1234567".                                                                                                                       |
-| Java                                                 | Detects Java source code.                                                                                                                                                    |
-| JavaScript                                           | Detects JavaScript source code.                                                                                                                                              |
-| Korea Resident Number (RRN)                          | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567".                                                                                           |
-| Lua                                                  | Detects Lua source code.                                                                                                                                                     |
-| Luxembourg Tax                                       | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345".                                                                                      |
-| Luxembourg VAT                                       | Detects Luxembourg VAT numbers such as "LU10000053".                                                                                                                         |
-| Malaysian National Identity Card Number              | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354".                                                                                           |
-| Mastercard Card Number                               | Detects Mastercard credit card numbers such as "5252 5971 4219 4116".                                                                                                        |
-| Mastercard Text                                      | Detects mentions of the Mastercard brand name such as "Mastercard".                                                                                                          |
-| Microsoft Azure Client Secret                        | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`.                                                                                                      |
-| MX CLABE (Bank)                                      | Detects Mexican CLABE bank account numbers such as "032180000118359719".                                                                                                     |
-| MX CURP                                              | Detects Mexican CURP codes such as "GOMC850515HJCRRR05".                                                                                                                     |
-| Netherlands BSN                                      | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782".                                                                                       |
-| Netherlands VAT                                      | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01".                                                                                                             |
-| NPM Token                                            | Detects npm registry access tokens such as a token beginning with `npm_`.                                                                                                    |
-| NZ NHI Number                                        | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016".                                                                                                   |
-| NZ Tax (IRD)                                         | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850".                                                                                        |
-| OpenAI API Key                                       | Detects OpenAI API keys such as a key beginning with `sk-proj-`.                                                                                                             |
-| Peru Tax (RUC)                                       | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001".                                                                                                |
-| Peru Unique ID (DNI)                                 | Detects Peruvian national identity numbers (DNI) such as "12345678".                                                                                                         |
-| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1".                                                                                        |
-| Poland National ID (PESEL)                           | Detects Polish national identification numbers (PESEL) such as "85051500006".                                                                                                |
-| Poland REGON                                         | Detects Polish National Business Registry numbers (REGON) such as "100000008".                                                                                               |
-| Poland Tax (NIP)                                     | Detects Polish tax identification numbers (NIP) such as "123-456-32-18".                                                                                                     |
-| Portugal Tax (NIF)                                   | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002".                                                                            |
-| PyPI Token                                           | Detects PyPI package upload tokens such as a token beginning with `pypi-`.                                                                                                   |
-| Python                                               | Detects Python source code.                                                                                                                                                  |
-| R                                                    | Detects R source code.                                                                                                                                                       |
-| Rust                                                 | Detects Rust source code.                                                                                                                                                    |
-| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H".                                                                                                        |
-| Slack API Token                                      | Detects Slack API tokens such as a token beginning with `xoxb-`.                                                                                                             |
-| Slack Webhook                                        | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`.                                                                                 |
-| Spain DNI/NIF                                        | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z".                                                                                                     |
-| Spain SSN                                            | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890".                                                                                           |
-| Spain Tax (CIF)                                      | Detects Spanish corporate tax identification codes (CIF) such as "A58818501".                                                                                                |
-| SSH Private Key                                      | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----".                                                                                              |
-| Stripe Granular Restricted Key                       | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`.                                                                                        |
-| Stripe Standard Secret Key                           | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`.                                                                                            |
-| Sweden Tax                                           | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874".                                                                                              |
-| SWIFT                                                | Detects SWIFT/BIC business identifier codes such as "PMFAUS66".                                                                                                              |
-| Swift                                                | Detects Swift source code.                                                                                                                                                   |
-| Taiwan National Identification Number                | Detects Taiwan national identification numbers such as "W171845961".                                                                                                         |
-| Thai Identity Card Number                            | Detects Thai national identity card numbers such as "4-8547-01245-28-9".                                                                                                     |
-| UAE Passport                                         | Detects United Arab Emirates passport numbers such as "A1234567".                                                                                                            |
-| Union Pay Card Number                                | Detects UnionPay credit card numbers such as "6250941006528599".                                                                                                             |
-| Union Pay Text                                       | Detects mentions of the UnionPay brand name such as "Union Pay".                                                                                                             |
-| United Kingdom National Insurance Number             | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C".                                                                                                        |
-| United Kingdom NHS Number                            | Detects UK NHS patient identification numbers such as "485-585-0454".                                                                                                        |
-| United States ABA Routing Number                     | Detects US ABA bank routing numbers such as "021000021".                                                                                                                     |
-| United States SSN Numeric Detection                  | Detects US Social Security Numbers such as "123-45-6789".                                                                                                                    |
-| United States SSN Text                               | Detects mentions of "SSN" or "social security" as a keyword, such as "social security".                                                                                      |
-| Unsanitized HAR File                                 | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
-| Uruguay ID (CI)                                      | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8".                                                                                     |
-| US Driver's License Number                           | Detects US driver's license numbers such as "CA License: A1234567".                                                                                                          |
-| US Individual Tax Identification Number (ITIN)       | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678".                                                                                          |
-| US Mailing Address                                   | Detects US mailing addresses such as "100 First St, Chicago, IL 60601".                                                                                                      |
-| US Passport Number                                   | Detects US passport numbers such as "A12345678".                                                                                                                             |
-| US Phone Number                                      | Detects US phone numbers such as "555-555-5555".                                                                                                                             |
-| US Physical Address                                  | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601".                                                                               |
-| Visa Card Number                                     | Detects Visa credit card numbers such as "4111 1111 1111 1111".                                                                                                              |
-| Visa Text                                            | Detects mentions of the Visa brand name such as "Visa".                                                                                                                      |
+| Detection entry | Description |
+| --- | --- |
+| AI Prompt Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials |
+| AI Prompt Content: Customer data | Prompt contains customer names, projects, business activities, or confidential customer contexts |
+| AI Prompt Content: Financial Information | Prompt contains actual financial numbers or confidential business data |
+| AI Prompt Content: PII | Prompt contains personal information (names, SSNs, emails, etc.) |
+| AI Prompt Content: Source code | Prompt contains source code, code snippets, or proprietary algorithms |
+| AI Prompt Intent: Code Abuse and Malicious Code | Malicious code or attempts to exploit vulnerabilities |
+| AI Prompt Intent: Jailbreak | Prompt attempts to circumvent security policies |
+| AI Prompt Intent: PII | Prompt requests specific personal information about individuals |
+| Amazon AWS Access Key ID | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`. |
+| Amazon AWS Secret Access Key | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`. |
+| American Express Card Number | Detects American Express credit card numbers such as "378282246310005". |
+| American Express Text | Detects mentions of the American Express brand name such as "American Express". |
+| AU Passport Number | Detects Australian passport numbers such as "L1234567". |
+| Australia Address | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000". |
+| Australia Business (ABN) | Detects Australian Business Numbers (ABN) such as "51 824 753 556". |
+| Australia Company (ACN) | Detects Australian Company Numbers (ACN) such as "001 000 004". |
+| Australia Medicare | Detects Australian Medicare card numbers such as "2000000006". |
+| Australia Passport | Detects Australian passport numbers such as "L1234567". |
+| Australia Tax File Number | Detects Australian Tax File Numbers (TFN) such as "85 655 734". |
+| Austria SSN (SV-Nummer) | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180". |
+| Austria Tax ID | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789". |
+| Austria VAT (UID) | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678". |
+| Belgium Tax ID (NN) | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61". |
+| Belgium VAT | Detects Belgian VAT numbers such as "BE0000000097". |
+| Bitcoin Wallet | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2". |
+| Brazil CNPJ | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81". |
+| Brazil CPF (Tax ID) | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25". |
+| Bulgaria Uniform Civil (EGN) | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007". |
+| C | Detects C source code. |
+| C# | Detects C# source code. |
+| C++ | Detects C++ source code. |
+| Canada Bank Account Number | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567". |
+| Canada Health Number | Detects Canadian provincial health card numbers such as "1234-567-897". |
+| Canada Passport | Detects Canadian passport numbers such as "AB123456". |
+| Canada PHIN (Manitoba) | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009". |
+| Canada Physical Address | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1". |
+| Canada Social Insurance Number | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474". |
+| Chile National ID (RUT) | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5". |
+| China ID Card | Detects Chinese resident identity card numbers such as "11010519491231002X". |
+| Cloudflare Account Owned API Token | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`. |
+| Cloudflare User API Key | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`. |
+| Cloudflare User API Token | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`. |
+| Croatia Personal ID (OIB) | Detects Croatian personal identification numbers (OIB) such as "10000000005". |
+| Denmark Tax (CPR) | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008". |
+| Diners Club Card Number | Detects Diners Club credit card numbers such as "30121690374838". |
+| Discord Webhook | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`. |
+| Email Address | Detects email addresses such as "test@example.com". |
+| Ethereum Wallet | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F". |
+| EU Passport | Detects EU member state passport numbers such as "AB1234567". |
+| FDA Active Ingredients | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB". |
+| FDA Drug Names | Detects FDA-registered drug names such as "ABACAVIR". |
+| Finland Tax ID | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y". |
+| France CNI (National ID) | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901". |
+| France Passport | Detects French passport numbers such as "12AB34567". |
+| France Social Security Number | Detects French social security (INSEE) numbers such as "145081849670637". |
+| France Tax ID (SPI) | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123". |
+| France VAT | Detects French VAT numbers such as "FR12000000000". |
+| Full Name | Detects personal full names. |
+| Generic CVV Card Number | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033". |
+| Germany Tax ID | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005". |
+| Germany VAT | Detects German VAT numbers (USt-IdNr) such as "DE100000003". |
+| GitHub PAT | Detects GitHub personal access tokens such as a token beginning with `ghp_`. |
+| Go | Detects Go source code. |
+| Google GCP API Key | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`. |
+| Greece Tax (AFM) | Detects Greek tax identification numbers (AFM) such as "100000003". |
+| Haskell | Detects Haskell source code. |
+| Hong Kong Identity Card Number | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)". |
+| Hungary Tax | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008". |
+| IBAN | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59". |
+| ICD-10 FY2023 Short Description | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified". |
+| ICD-11 Short Description | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS". |
+| India Aadhaar | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124". |
+| India GST (GSTIN) | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5". |
+| India PAN Card | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F". |
+| India Voter ID | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567". |
+| Indonesia Identity Card Number | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011". |
+| Indonesia Tax (NPWP) | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345". |
+| Ireland Tax (PPS) | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA". |
+| Ireland VAT | Detects Ireland VAT numbers such as "IE1234567T". |
+| Italy Fiscal Code | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z". |
+| Japan Address | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001". |
+| Japan My Number (Corp) | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002". |
+| Japan My Number (Person) | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005". |
+| Japan Names (Kanji) | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎". |
+| Japan Passport | Detects Japanese passport numbers such as "TZ1234567". |
+| Java | Detects Java source code. |
+| JavaScript | Detects JavaScript source code. |
+| Korea Resident Number (RRN) | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567". |
+| Lua | Detects Lua source code. |
+| Luxembourg Tax | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345". |
+| Luxembourg VAT | Detects Luxembourg VAT numbers such as "LU10000053". |
+| Malaysian National Identity Card Number | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354". |
+| Mastercard Card Number | Detects Mastercard credit card numbers such as "5252 5971 4219 4116". |
+| Mastercard Text | Detects mentions of the Mastercard brand name such as "Mastercard". |
+| Microsoft Azure Client Secret | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`. |
+| MX CLABE (Bank) | Detects Mexican CLABE bank account numbers such as "032180000118359719". |
+| MX CURP | Detects Mexican CURP codes such as "GOMC850515HJCRRR05". |
+| Netherlands BSN | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782". |
+| Netherlands VAT | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01". |
+| NPM Token | Detects npm registry access tokens such as a token beginning with `npm_`. |
+| NZ NHI Number | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016". |
+| NZ Tax (IRD) | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850". |
+| OpenAI API Key | Detects OpenAI API keys such as a key beginning with `sk-proj-`. |
+| Peru Tax (RUC) | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001". |
+| Peru Unique ID (DNI) | Detects Peruvian national identity numbers (DNI) such as "12345678". |
+| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1". |
+| Poland National ID (PESEL) | Detects Polish national identification numbers (PESEL) such as "85051500006". |
+| Poland REGON | Detects Polish National Business Registry numbers (REGON) such as "100000008". |
+| Poland Tax (NIP) | Detects Polish tax identification numbers (NIP) such as "123-456-32-18". |
+| Portugal Tax (NIF) | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002". |
+| PyPI Token | Detects PyPI package upload tokens such as a token beginning with `pypi-`. |
+| Python | Detects Python source code. |
+| R | Detects R source code. |
+| Rust | Detects Rust source code. |
+| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H". |
+| Slack API Token | Detects Slack API tokens such as a token beginning with `xoxb-`. |
+| Slack Webhook | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`. |
+| Spain DNI/NIF | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z". |
+| Spain SSN | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890". |
+| Spain Tax (CIF) | Detects Spanish corporate tax identification codes (CIF) such as "A58818501". |
+| SSH Private Key | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----". |
+| Stripe Granular Restricted Key | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`. |
+| Stripe Standard Secret Key | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`. |
+| Sweden Tax | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874". |
+| SWIFT | Detects SWIFT/BIC business identifier codes such as "PMFAUS66". |
+| Swift | Detects Swift source code. |
+| Taiwan National Identification Number | Detects Taiwan national identification numbers such as "W171845961". |
+| Thai Identity Card Number | Detects Thai national identity card numbers such as "4-8547-01245-28-9". |
+| UAE Passport | Detects United Arab Emirates passport numbers such as "A1234567". |
+| Union Pay Card Number | Detects UnionPay credit card numbers such as "6250941006528599". |
+| Union Pay Text | Detects mentions of the UnionPay brand name such as "Union Pay". |
+| United Kingdom National Insurance Number | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C". |
+| United Kingdom NHS Number | Detects UK NHS patient identification numbers such as "485-585-0454". |
+| United States ABA Routing Number | Detects US ABA bank routing numbers such as "021000021". |
+| United States SSN Numeric Detection | Detects US Social Security Numbers such as "123-45-6789". |
+| United States SSN Text | Detects mentions of "SSN" or "social security" as a keyword, such as "social security". |
+| Unsanitized HAR File | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
+| Uruguay ID (CI) | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8". |
+| US Driver's License Number | Detects US driver's license numbers such as "CA License: A1234567". |
+| US Individual Tax Identification Number (ITIN) | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678". |
+| US Mailing Address | Detects US mailing addresses such as "100 First St, Chicago, IL 60601". |
+| US Passport Number | Detects US passport numbers such as "A12345678". |
+| US Phone Number | Detects US phone numbers such as "555-555-5555". |
+| US Physical Address | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601". |
+| Visa Card Number | Detects Visa credit card numbers such as "4111 1111 1111 1111". |
+| Visa Text | Detects mentions of the Visa brand name such as "Visa". |
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
index abd3ab310d2558c..96398de8d42e757 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
@@ -37,10 +37,10 @@ The following secrets are validated with regex.
 
 The following Cloudflare API credentials are validated algorithmically using a checksum. Only credentials generated after [Cloudflare's token format update](/fundamentals/api/get-started/token-formats/) will be matched by these entries.
 
-| Detection entry                    | Format                                                                         |
-| ---------------------------------- | ------------------------------------------------------------------------------ |
-| Cloudflare User API Key            | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum  |
-| Cloudflare User API Token          | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Detection entry | Format |
+| --- | --- |
+| Cloudflare User API Key | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Cloudflare User API Token | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 | Cloudflare Account Owned API Token | `cfat_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 
 ## Financial Information
@@ -52,6 +52,7 @@ The following Cloudflare API credentials are validated algorithmically using a c
 
 Credit card numbers begin with a six or eight-digit Issuer Identification Number (IIN) and are followed by up to 23 additional digits. Card verification values (CVVs) are not validated.
 
+
 In the table below, entries use one of three validation methods. [Luhn's algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is a checksum formula used to verify credit card numbers. Entries validated "with checksum" use an arithmetic check specific to that number format. Entries validated "with regex" match a known text pattern without performing a mathematical check.
 
 | Detection entry                  | Notes                                                                             |
@@ -73,9 +74,9 @@ In the table below, entries use one of three validation methods. [Luhn's algorit
 
 The **Unsanitized HAR** predefined profile detects HTTP Archive (HAR) files in traffic that have not been processed by Cloudflare's HAR sanitizer. HAR files frequently contain sensitive data such as session cookies, authorization headers, and other credentials.
 
-| Detection entry      | Notes                                                                                                                                                              |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Unsanitized HAR file | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
+| Detection entry       | Notes                                                                                                                           |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| Unsanitized HAR file  | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
 
 You can use this profile in a Gateway HTTP policy to block HAR file uploads or redirect users to `https://har-sanitizer.pages.dev/` to sanitize the file before uploading. For more information, refer to [common DLP policies](/cloudflare-one/data-loss-prevention/dlp-policies/common-policies/).
 
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
index 1df5ea81ecd5b67..2ec67b8a7f2d86d 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
index 4b180d527caeea5..014c621a7fcbb9e 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
@@ -166,9 +166,9 @@ Email security displays the following details:
 
 #### Cloudy summaries
 
-The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted.
+The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. 
 
-Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values).
+Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). 
 
 **View all signatures** allows you to view all the detections that triggered on the email, including detections that did not determine the final disposition.
 
diff --git a/src/content/docs/cloudflare-one/email-security/reference/index.mdx b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
index 554e42af73200ca..ed22d9cc45c63d0 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
index f29fd4a0c946be4..e72de496842e22a 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
@@ -19,4 +19,4 @@ Currently, you can process emails in the following regions:
 - US
 - Germany
 - India
-- Australia
+- Australia
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
index 67304fed00d84ff..04516541176d46d 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
@@ -21,8 +21,8 @@ To configure auto-move events:
 5. Under **Auto-moves**, select **Configure**.
 6. For each disposition (malicious, spam, bulk, suspicious, spoof), choose what happens to matching emails:
    - **Soft delete - user recoverable**: Moves the message to the user's **Recoverable Items - Deleted** folder. The user can still find and restore the message. This option is only available for Microsoft 365 customers. Refer to [Microsoft 365 Exchange data deletion](https://learn.microsoft.com/en-us/compliance/assurance/assurance-exchange-online-data-deletion) for more information.
-   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it.
+   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it. 
    - **Move to trash**: Moves the message to the user's trash or deleted items folder. This option is only available for Google Workspace users.
    - **Move to junk**: Moves the message to the user's junk or spam folder.
    - **No action**: Leaves the message where it is. Email security still records the disposition, but does not move the message.
-7. Select **Save**.
+7. Select **Save**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
index 447a71c6bb9e4af..d4eaee4d21f7a1b 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
@@ -10,11 +10,11 @@ sidebar:
 
 This guide describes how to configure detection settings to mitigate impersonation risks while ensuring legitimate delivery.
 
-Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address.
+Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address. 
 
 For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to mitigate delivery disruptions.
 
-To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific. In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
+To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific.  In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
 
 ## Policy selection criteria
 
@@ -36,4 +36,4 @@ Example use cases:
 
 - Prioritize static IPs: Use known and owned, static IP addresses for relay servers. Avoid [ephemeral IP addresses](https://docs.cloud.google.com/vpc/docs/ip-addresses#ephemeral_and_static_ip_addresses) as their transient nature can lead to policy degradation.
 - Enforce Sender Verification: Always have **Sender Verification (Recommended)** enabled in the Cloudflare dashboard. It validates the originating system's email authentication records (namely [SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), and [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) against the domain to ensure authenticity.
-- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
+- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
index efaa4f6b773fcca..8481b73230a9b54 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
index 7c3b68ba2333939..fffa7bf2fdd3e28 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="email-security/domain-information" product="cloudflare-one" />
+<Render file="email-security/domain-information" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
index 9a9a590d97573b0..4a962408af45bb5 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
index b5fed567bea01e0..0365a23705fb682 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
index d3771d0098d4bb0..03b7792d24ac057 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
@@ -21,4 +21,4 @@ To set up PhishNet Microsoft 365:
 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**.
 4. Select **Upload custom apps**.
 5. Choose **Provide link to manifest file** and paste the URL you copied from the Cloudflare One dashboard.
-6. Verify and complete the wizard.
+6. Verify and complete the wizard.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
index 0d1522a54efcba7..414eff1eb5c872e 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
@@ -27,4 +27,4 @@ You have now successfully installed Cloudflare PhishNet.
 1. In your Gmail web client, open the message you would like to flag as either spam or phish.
 2. Select the PhishNet logo on the side panel.
 3. Under **Select Submission Type**, select **Spam** or **Phish**.
-4. Select **Submit Report**.
+4. Select **Submit Report**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
index 4190cae0904f56e..9e049608ac65e75 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
@@ -15,4 +15,4 @@ To view the destination addresses of user and team submissions:
 3. Select **Settings**.
 4. Go to **Phish submission** > **Submission addresses** > **View**.
 
-The dashboard will display **User submission addresses** and **Team submission addresses**.
+The dashboard will display **User submission addresses** and **Team submission addresses**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
index 43e57d4a1c293fa..c65b4336fa5ad20 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
@@ -15,24 +15,24 @@ import { Markdown } from "~/components";
 
 Before you start the onboarding process, you will have to:
 
-1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline.
+1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline. 
 2. Learn about dispositions, impersonation registry, and submissions.
 3. Know the steps to configure your email environment correctly.
 
 The following table compares features available across API, BCC/Journaling and MX/Inline:
 
-| Feature             | Microsoft 365                                       | Google Workspace                  | Others (On-prem/Cloud)                                   |
-| ------------------- | --------------------------------------------------- | --------------------------------- | -------------------------------------------------------- |
-| Deployment type     | API and MX                                          | BCC and MX                        | MX only                                                  |
-| API integration     | Microsoft Graph API                                 | BCC only                          | None                                                     |
-| BCC/Journaling      | Uses a Journal Rule in the Microsoft Purview portal | Uses BCC rules                    | Uses journaling                                          |
-| Inline/MX Mode      | MX records point to Cloudflare                      | MX records point to Cloudflare    | MX records point to Cloudflare                           |
-| Message remediation | Auto-moves through Read/Write API                   | Auto-moves through Read/Write API | Messages can be blocked, quarantined, or modified inline |
+| Feature             	| Microsoft 365                                       	| Google Workspace                  	| Others (On-prem/Cloud)                                   	|
+|---------------------	|-----------------------------------------------------	|-----------------------------------	|----------------------------------------------------------	|
+| Deployment type     	| API and MX                                          	| BCC and MX                        	| MX only                                                  	|
+| API integration     	| Microsoft Graph API                                 	| BCC only                          	| None                                                     	|
+| BCC/Journaling      	| Uses a Journal Rule in the Microsoft Purview portal 	| Uses BCC rules                    	| Uses journaling                                          	|
+| Inline/MX Mode      	| MX records point to Cloudflare                      	| MX records point to Cloudflare    	| MX records point to Cloudflare                           	|
+| Message remediation 	| Auto-moves through Read/Write API                   	| Auto-moves through Read/Write API 	| Messages can be blocked, quarantined, or modified inline 	|
 
 Note that:
 
 - All email providers support MX/Inline deployment.
-- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
+- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or  post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
 - Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/).
 
 ## 1. Choose a deployment
diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
index 61054ee69b7887b..5c704f3a770261e 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
@@ -43,4 +43,4 @@ To stop scanning domains:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**.
-4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
+4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
index f61e4bcb70cd12f..43b90fbe16e9a31 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
index 8bb78df403639c3..57f5aa4227abd1d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
index ad3849aad352d63..327257b4eb0b5e5 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
@@ -11,4 +11,4 @@ sidebar:
 BCC/Journaling deployment is a post-delivery type of deployment. Cloudflare analyzes emails after they reach the user's inbox. Every time you receive an email, your email provider will send a blind copy to Cloudflare for an analysis.
 
 - Choose [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/) if your email provider is Gmail.
-- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
+- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
index 776f45cf8537714..943a2e42ca67928 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
index ac23a96bd6a598d..8ff736556bdbdba 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
@@ -95,6 +95,7 @@ To verift that your domain has been added successfully and that your emails are
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**.
 
+
 ## Next steps
 
-<Render file="email-security/enable-logs" product="cloudflare-one" />
+<Render file="email-security/enable-logs" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
index 6e14bc7bb3cbd1b..4c636aa1972e3b4 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
@@ -22,6 +22,7 @@ To use Email security, you will need to have:
 	product="cloudflare-one"
 />
 
+
 ## Manually add domains
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
index e5945fa7ffe219b..f15a938e8733a92 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
@@ -11,6 +11,6 @@ sidebar:
 next: false
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
index be6fcfaa82de80d..34f65be10df2f54 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
@@ -16,7 +16,7 @@ Add all of the following addresses to your mail provider's IP allowlist.
 
 Microsoft 365 does not support IPv6 addresses or the following IPv4 ranges:
 
-- `104.30.32.0/19`
+- `104.30.32.0/19` 
 - `134.195.26.0/23`
 
 If you use Microsoft 365, use the individual `/24` blocks (256 addresses each) listed in [Microsoft 365 `/24` addresses](#microsoft-365-24-addresses) instead.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
index fce333e04ebd1b6..53963c84381f2fe 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
@@ -10,6 +10,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
index 2bcd30388647a00..d33970c173669e0 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
@@ -27,4 +27,4 @@ To set up a partner domain:
 
 To edit a partner domain, select the three dots > **Edit**.
 
-To delete a partner domain, select the three dots > **Delete**.
+To delete a partner domain, select the three dots > **Delete**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
index a1e35434d0580f7..35bc8f11bdcdad3 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
@@ -10,6 +10,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
index 4c76d96d35736ed..7f5428d95fbf8ef 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
index e04482e75dcf67e..14e7f12e83a674d 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
@@ -52,4 +52,4 @@ To view submissions:
 3. Choose from the following submission types:
    - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions.
    - [**User submissions**](/cloudflare-one/email-security/submissions/user-submissions/): View emails your users submitted for submissions.
-   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
+   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
index 87a9a602b6c10cb..aff37d96e27156f 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
@@ -36,4 +36,4 @@ To enable Invalid submission email notifications:
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
-3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
+3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/faq/devices-faq.mdx b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
index 86a6908deaaf164..d37af87433794e5 100644
--- a/src/content/docs/cloudflare-one/faq/devices-faq.mdx
+++ b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
@@ -7,6 +7,7 @@ sidebar:
   order: 6
 head: []
 description: Review frequently asked questions about devices in Cloudflare Zero Trust.
+
 ---
 
 [❮ Back to FAQ](/cloudflare-one/faq/)
@@ -19,8 +20,8 @@ As the Cloudflare One Client has replaced WinDivert with WinTun architecture, al
 
 As our [Network Map](https://www.cloudflare.com/en-gb/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the data center (colo) you are connecting to isn't necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-- Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
-- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+* Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
+* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
 
 ## Why is my public IP address sometimes visible?
 
@@ -49,8 +50,8 @@ An [OS firewall rule](/cloudflare-one/team-and-resources/devices/cloudflare-one-
 
 If your private network is [exposed via Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/):
 
-- Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
-- Verify that the user is allowed through by your Access and Gateway policies.
-- Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
+* Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
+* Verify that the user is allowed through by your Access and Gateway policies.
+* Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
 
 When contacting Cloudflare support, ensure that you include [Cloudflare One Client debug logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/) for your device. These logs will help Cloudflare support understand the overall architecture of your machine and networks.
diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
index f1c5be808fd91bf..94280945992ed4c 100644
--- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
@@ -133,4 +133,4 @@ In **Gateway insights**, you can view a report on your Gateway firewall policies
 In **CASB**, you can review instances of security issues — such as misconfigurations, unauthorized user activity, and shadow IT — found in your SaaS integrations by [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).
 
 - Integrations by number of findings
-- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
+- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
index 3ab91476f6fa6d1..2295744544866ab 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
@@ -24,19 +24,19 @@ To view the AI security report dashboard:
 
 To populate the AI security report dashboard, you must have:
 
-- [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
-- User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
-- [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
+* [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
+* User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
+* [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
 
 ## Available insights
 
 The AI security report dashboard includes the following panels and metrics:
 
-- [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
-- [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
-- [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
-- [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
-- [Access login events to MCP servers](#access-login-events-to-mcp-servers)
+* [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
+* [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
+* [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
+* [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
+* [Access login events to MCP servers](#access-login-events-to-mcp-servers)
 
 ### Top 5 visited AI applications by user count
 
@@ -50,10 +50,10 @@ Use this chart to monitor adoption trends and detect new or unauthorized AI tool
 Reports the total number of AI applications identified and their review statuses.  
 Statuses include:
 
-- Unreviewed — Applications not yet evaluated by administrators.
-- In Review — Applications currently under review for approval.
-- Unapproved — Applications that are restricted or blocked.
-- Approved — Applications explicitly permitted for organizational use.
+* Unreviewed — Applications not yet evaluated by administrators.  
+* In Review — Applications currently under review for approval.  
+* Unapproved — Applications that are restricted or blocked.  
+* Approved — Applications explicitly permitted for organizational use.
 
 ### Data uploaded to Artificial Intelligence applications by status
 
@@ -66,4 +66,4 @@ Displays the number of Model Context Protocol (MCP) servers protected by [Cloudf
 
 ### Access login events to MCP servers
 
-Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
+Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
index 7a066e04802a46a..475a4c3d35c46ac 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
@@ -29,20 +29,20 @@ To view the Application Access Report dashboard:
 
 To populate the Application Access Report dashboard, you must have:
 
-- At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
-- Users authenticating to these applications through Cloudflare Access.
+* At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
+* Users authenticating to these applications through Cloudflare Access.
 
 ## Available insights
 
 The Application Access Report dashboard includes the following panels and metrics:
 
-- [Summary of Access activity](#summary-of-access-activity)
-- [Access events](#access-events)
-- [Access decisions by event count](#access-decisions-by-event-count)
-- [Access applications by event count](#access-applications-by-event-count)
-- [Access events by type](#access-events-by-type)
-- [Top counts of event details](#top-counts-of-event-details)
-- [Access admin metrics](#access-admin-metrics)
+* [Summary of Access activity](#summary-of-access-activity)
+* [Access events](#access-events)
+* [Access decisions by event count](#access-decisions-by-event-count)
+* [Access applications by event count](#access-applications-by-event-count)
+* [Access events by type](#access-events-by-type)
+* [Top counts of event details](#top-counts-of-event-details)
+* [Access admin metrics](#access-admin-metrics)
 
 ### Summary of Access activity
 
@@ -55,7 +55,7 @@ You can use this graph to review user authentication activity and detect unusual
 
 ### Access decisions by event count
 
-Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).
+Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).  
 
 ### Access applications by event count
 
@@ -71,11 +71,11 @@ This panel helps administrators understand how users are authenticating across a
 
 Lists the most common Access event attributes, including:
 
-- Application name — Displays the top accessed applications.
-- Identity provider — Shows which identity providers (IdPs) were most used.
-- Users — Lists top users by number of login events.
-- Countries — Displays top countries where users logged in.
-- IP addresses — Lists the top source IPs associated with login events.
+* Application name — Displays the top accessed applications.
+* Identity provider — Shows which identity providers (IdPs) were most used.
+* Users — Lists top users by number of login events.
+* Countries — Displays top countries where users logged in.
+* IP addresses — Lists the top source IPs associated with login events.
 
 These insights help administrators identify usage patterns and trends.
 
@@ -83,7 +83,7 @@ These insights help administrators identify usage patterns and trends.
 
 Provides a summary of Access configurations made by admin in your organization, including:
 
-- Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
-- Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
+* Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
+* Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
 
-This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
+This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
index cc397c6684cbb8e..7768588f1179831 100644
--- a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
@@ -7,4 +7,5 @@ title: MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dex-analysis
 sidebar:
   order: 90
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
index 1309beff1282a3f..056e13ea2ec0cca 100644
--- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
@@ -35,12 +35,12 @@ To view analytics on a per-device level, go to [Device monitoring](/cloudflare-o
 
 - **Connectivity status**: Percentage of devices in a given Cloudflare One Client state.
 
-  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                                                         |
-  | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                               |
-  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                                |
+  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                               |
+  | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                          |
+  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                           |
   | Paused       | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [admin override code](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes). Paused clients will [auto-connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) after a timeout period. |
-  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                 |
+  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                            |
 
 - **Mode**: [Client mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) deployed on the device.
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
index 7336bc04cde6cad..0823f895e22fb5c 100644
--- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
@@ -42,7 +42,7 @@ Review the available selectors and their scope in the following list.
 | **Operating system version** | For specifying an operating system version (use Operator `in`) or versions (use Operator `is`).                                   |
 | **Managed network**          | For specifying users accessing the network from the office (managed network) compared to those accessing remotely.                |
 | **SAML attributes**          | For specifying a value from the [SAML Attribute Assertion](/cloudflare-one/traffic-policies/identity-selectors/#saml-attributes). |
-| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                 |
+| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                          |
 
 ## Add a rule to a test
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
index d09f0e887f56c41..15a13b2b8c484f9 100644
--- a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
@@ -20,8 +20,4 @@ To control which users or groups run a test, use [DEX rules](/cloudflare-one/ins
 
 ## Export DEX application test logs
 
-<Render
-	file="dex/logpush-export"
-	product="cloudflare-one"
-	params={{ applicationTests: true }}
-/>
+<Render file="dex/logpush-export" product="cloudflare-one" params={{ applicationTests: true }} />
diff --git a/src/content/docs/cloudflare-one/insights/index.mdx b/src/content/docs/cloudflare-one/insights/index.mdx
index 53baf5cb249a412..84559d3b901bfca 100644
--- a/src/content/docs/cloudflare-one/insights/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/index.mdx
@@ -40,16 +40,18 @@ If your device is experiencing connectivity issues, Cloudflare recommends starti
 
 1. Use [Analytics Dashboards](/cloudflare-one/insights/analytics/) to understand trends and for visualizations of your log data.
 
-   Administrators typically start with Analytics Dashboards because they offer:
-   - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
-   - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
+    Administrators typically start with Analytics Dashboards because they offer:
+
+    - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
+    - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
 
 2. Use [Logs](/cloudflare-one/insights/logs/) as needed for event-level verification.
 
-   Use Logs when you need to:
-   - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
-   - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
-   - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
+    Use Logs when you need to:
+
+    - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
+    - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
+    - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
 
 ### User-reported issues
 
@@ -57,4 +59,4 @@ Users may report problems like slow or failing connections to internal apps.
 
 1. Start with [Analytics Dashboards](/cloudflare-one/insights/analytics/) to review whether the issue impacts others.
 2. Check [Logs](/cloudflare-one/insights/logs/) for failed authentication attempts, blocked requests, or unexpected policy matches.
-3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
+3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
index 0761b8662b76208..304fa8f96f03164 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
@@ -16,18 +16,18 @@ To view admin activity logs, log in to the [Cloudflare dashboard](https://dash.c
 
 ## Explanation of the fields
 
-| Field           | Description                                      | Example Value                                                                          |
-| --------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------- |
-| Email           | User who performed the action                    | josephli@cloudflare.com                                                                |
-| Product         | Cloudflare product being modified                | Tunnel                                                                                 |
-| Resource        | Specific resource type within the product        | Route                                                                                  |
-| Event           | Action performed (Create, Update, Delete)        | Create                                                                                 |
-| Date            | Timestamp of when the action occurred            | April 30, 2026 • 12:19 AM                                                              |
-| User IP Address | IP address of the user who made the change       | 2a09:bac6:6447:523::83:30                                                              |
-| Interface       | How the change was initiated                     | API                                                                                    |
-| Audit record    | Unique identifier for the audit log entry        | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                                   |
-| Old value       | Previous configuration state (empty for creates) | {}                                                                                     |
-| New value       | New configuration state after the change         | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
+| Field           | Description                                           | Example Value                                                                      |
+| ----------------| ------------------------------------------------------| -----------------------------------------------------------------------------------|
+| Email           | User who performed the action                         | josephli@cloudflare.com                                                            |
+| Product         | Cloudflare product being modified                     | Tunnel                                                                             |
+| Resource        | Specific resource type within the product             | Route                                                                              |
+| Event           | Action performed (Create, Update, Delete)             | Create                                                                             |
+| Date            | Timestamp of when the action occurred                 | April 30, 2026 • 12:19 AM                                                          |
+| User IP Address | IP address of the user who made the change            | 2a09:bac6:6447:523::83:30                                                          |
+| Interface       | How the change was initiated                          | API                                                                                |
+| Audit record    | Unique identifier for the audit log entry             | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                               |
+| Old value       | Previous configuration state (empty for creates)      | {}                                                                                 |
+| New value       | New configuration state after the change              | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
 
 ## Export admin activity logs
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
index 32b6c971303f04d..b2a31ec6e175c94 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
@@ -30,18 +30,17 @@ To view Gateway activity logs:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Choose a type of Gateway log:
-   - **DNS query logs**
-   - **Network logs**
-   - **HTTP request logs**
-     :::note[Log viewer (beta)]
-     Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
-     :::
+	- **DNS query logs**
+	- **Network logs**
+	- **HTTP request logs**
+	:::note[Log viewer (beta)]
+	Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
+	:::
 3. (Optional) Filter the logs that display in the log viewer. You can filter logs by their timestamp and event details (such as host, URL, user email, policy action, and more).
 
-   :::tip
-   Querying for fewer fields improves log loading performance.
-   :::
-
+	:::tip
+	Querying for fewer fields improves log loading performance.
+	:::
 4. Select an individual timestamp to investigate the event in more detail.
 
 ## Selective logging
@@ -62,16 +61,16 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Basic information
 
-| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                                       |
-| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                             |
+| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                        |
 | **Email**             | Email address of the user who registered the Cloudflare One Client where traffic originated from. If a non-identity on-ramp (such as a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)) or machine-level authentication (such as a [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/)) was used, this value will be `non_identity@<team-domain>.cloudflareaccess.com`. |
-| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                                |
-| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                            |
-| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                                     |
-| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                                     |
-| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                      |
+| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                           |
+| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                           |
+| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                    |
 
 #### Configuration information
 
@@ -86,14 +85,14 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Identities
 
-| Field                  | Description                                                                                                                                                                                                                  |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                                                                                                        |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**              | Email address of the user who registered the Cloudflare One Client where traffic originated from.                                                                                                                            |
-| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                                        |
+| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                              |
 | **Registration ID**    | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered for a particular email. The same physical device may have multiple registration IDs.           |
 | **Device name**        | Display name of the device returned by the operating system to the Cloudflare One Client. Typically this is the hostname of a device. Not all devices will have a device name. Device names are not guaranteed to be unique. |
 | **Device ID**          | UUID of the device connected with the Cloudflare One Client. Each physical device in your organization will have a UUID.                                                                                                     |
-| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                          |
+| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                |
 
 #### DNS query details
 
@@ -183,14 +182,14 @@ To log failed connections, use [network session logs](/logs/logpush/logpush-job/
 
 #### Identities
 
-| Field                  | Description                                                                                     |
-| ---------------------- | ----------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                           |
+| ---------------------- | ------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user sending the packet. This is generated by the Cloudflare One Client.   |
 | **User ID**            | ID of the user sending the packet. This is generated by the Cloudflare One Client.              |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.           |
-| **Device name**        | Name of the device that sent the packet.                                                        |
+| **Device name**        | Name of the device that sent the packet.                                              |
 | **Device ID**          | ID of the physical device that sent the packet. This is generated by the Cloudflare One Client. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                      |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                            |
 
 #### Network query details
 
@@ -229,7 +228,7 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 | Field                        | Description                                                                                                                                                                                                                                                                                                                              |
 | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Host**                     | Hostname in the HTTP header for the HTTP request. Gateway will log the SNI in this field if it responded to the request with a Do Not Inspect action. If Gateway does not receive the SNI, this field will be empty.                                                                                                                     |
-| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                     |
+| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                               |
 | **Action**                   | The Gateway [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) taken based on the first rule that matched (such as Allow or Block).                                                                                                                                                                                        |
 | **Request ID**               | Unique ID of the request.                                                                                                                                                                                                                                                                                                                |
 | **Time**                     | Date and time of the HTTP request.                                                                                                                                                                                                                                                                                                       |
@@ -253,14 +252,14 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 
 #### Identities
 
-| Field                  | Description                                                                                                                             |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                   |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                    |
 | **User ID**            | ID of the user who made the request. This is generated by the Cloudflare One Client.                                                    |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.                                                   |
-| **Device name**        | Name of the device that made the request.                                                                                               |
+| **Device name**        | Name of the device that made the request.                                                                                     |
 | **Device ID**          | ID of the physical device that made the request. This is generated by the Cloudflare One Client on the device that created the request. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                              |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                    |
 
 #### HTTP query details
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
index 5a3e6717195a05e..bc1f6d84f202733 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
@@ -15,6 +15,6 @@ import { DirectoryListing } from "~/components";
 
 The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment.
 
-<DirectoryListing button={true} />
+<DirectoryListing button={true}/>
 
 For additional datasets and long-term log storage, refer to [Logpush](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
index ec364aac8147715..9a69bac2bfb4fe7 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
@@ -33,7 +33,7 @@ Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/
 | Field               | Description                                                                                                                                                                                                                    |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**           | Email used to register the device with Zero Trust.                                                                                                                                                                             |
-| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                                |
+| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                    |
 | **Registration ID** | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered. The same physical device may have multiple registration IDs if multiple users share the device. |
 
 ### Posture details
diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
index 0d6bfb37f1273e2..375008abd658fd5 100644
--- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
@@ -38,23 +38,23 @@ For more information on supported destinations, refer to [Enable destinations](/
 
 Logpush supports all [dashboard logs](/cloudflare-one/insights/logs/dashboard-logs/) as well as additional datasets not available in the Cloudflare One dashboard. Refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/) for a list of all available fields.
 
-| Dataset                                                                                                    | Description                                                                                                                                                            |
-| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                                  |
-| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                                        |
-| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                              |
-| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                                           |
-| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                                   |
-| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                                |
-| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                                        |
-| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                                            |
-| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                                          |
-| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                                        |
-| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                                   |
-| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/)               |
+| Dataset                                                                                                    | Description                                                                                                                                              |
+| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                    |
+| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                          |
+| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                |
+| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                             |
+| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                     |
+| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                   |
+| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                          |
+| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                              |
+| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                            |
+| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                          |
+| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                     |
+| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) |
 | [WARP Config Changes](/logs/logpush/logpush-job/datasets/account/warp_config_changes/)                     | Event logs that Cloudflare generates whenever a device changes [profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) |
-| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                                     |
-| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                                  |
+| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                       |
+| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                    |
 
 ## Verify regional map application
 
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
index cc0006a02875a8c..b326012ef5deb96 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
@@ -176,7 +176,7 @@ When you validate an R2 bucket, exclude the `access-key-id` and `secret-access-k
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-   <DashButton url="/?to=/:account/r2/overview" />
+	<DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -220,4 +220,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
index 26abc473b6c624b..f8b03fb96ce715a 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-one
 sidebar:
   order: 1
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Packet captures allow you to record raw network traffic data passing through Cloudflare's network so you can inspect it offline in tools like Wireshark. This is useful for diagnosing connectivity issues, verifying firewall rules, or investigating unexpected traffic patterns.
 
@@ -34,4 +35,4 @@ Full packet captures will collect new traffic sent to Cloudflare's network after
 
 Refer to the articles in this section to learn how to use packet captures.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
index 62b2709c8e9fc6c..abe3862c5a9b050 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
@@ -78,14 +78,14 @@ Flag organization access issues to help enforce best practices.
 
 <Render file="casb/data-loss-prevention" product="cloudflare-one" />
 
-| Finding type                                                     | Severity |
-| ---------------------------------------------------------------- | -------- |
-| Anthropic: Downloadable File with DLP Profile match              | High     |
-| Anthropic: Claude Chat User Prompt with DLP Profile match        | High     |
-| Anthropic: Claude Chat Assistant Response with DLP Profile match | High     |
-| Anthropic: Claude Chat Uploaded File with DLP Profile match      | High     |
-| Anthropic: Claude Chat Generated File with DLP Profile match     | High     |
-| Anthropic: Claude Project File with DLP Profile match            | High     |
-| Anthropic: Claude Project Document with DLP Profile match        | High     |
-| Anthropic: Claude Chat Artifact with DLP Profile match           | High     |
-| Anthropic: Claude Project Instructions with DLP Profile match    | High     |
+| Finding type                                                  | Severity |
+| ------------------------------------------------------------- | -------- |
+| Anthropic: Downloadable File with DLP Profile match           | High     |
+| Anthropic: Claude Chat User Prompt with DLP Profile match     | High     |
+| Anthropic: Claude Chat Assistant Response with DLP Profile match | High  |
+| Anthropic: Claude Chat Uploaded File with DLP Profile match   | High     |
+| Anthropic: Claude Chat Generated File with DLP Profile match  | High     |
+| Anthropic: Claude Project File with DLP Profile match         | High     |
+| Anthropic: Claude Project Document with DLP Profile match     | High     |
+| Anthropic: Claude Chat Artifact with DLP Profile match        | High     |
+| Anthropic: Claude Project Instructions with DLP Profile match | High     |
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
index 9b59aa70fcbddaa..a4f8fc32d81828a 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
@@ -30,4 +30,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot-fedramp",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
index b3db2aa1d185051..6c36357bcb412de 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
@@ -22,4 +22,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
index e82f7aac39559b8..9e0e96c4c48ecff 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
@@ -60,7 +60,7 @@ https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
 | `name`         | `${user:name}`       |
 | `surName`      | `${user:familyName}` |
 
-| `givenName` | `${user:givenName}` |
+| `givenName`    | `${user:givenName}`  |
 
 ![Configuring attribute statements in IAM Identity Center](~/assets/images/cloudflare-one/identity/aws/aws-saml-attributes.png)
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
index d01bcec09cbb731..b11fbe6575bd942 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
@@ -46,8 +46,8 @@ Make a `POST` request to the [Identity Providers](/api/resources/zero_trust/subr
 
 ## Configuration options
 
-| Option                          | Description                                                                                                                                                                  | Default  |
-| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| Option | Description | Default |
+| --- | --- | --- |
 | **Restrict to account members** | When enabled, only users who are members of your Cloudflare account can authenticate. When disabled, any Cloudflare user can authenticate (subject to your Access policies). | Disabled |
 
 ## Use Cloudflare account membership in policies
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
index c9d7965c3fd2706..f15160944863211 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
@@ -12,7 +12,7 @@ import { Render } from "~/components";
 
 Use these steps to set up Facebook as your identity provider.
 
-1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one.
+1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one. 
 
 2. Select **Create App** at the top-right. The **Create an app** card displays.
 
@@ -42,7 +42,7 @@ Use these steps to set up Facebook as your identity provider.
 
 15. Select **Settings**, and ensure that **Use Strict Mode for redirect URIs** slider is set to **Yes**.
 
-16. In the **Valid OAuth Redirect URIs** field, enter the following URL:
+15. In the **Valid OAuth Redirect URIs** field, enter the following URL:
 
     ```txt
     https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
@@ -50,7 +50,7 @@ Use these steps to set up Facebook as your identity provider.
 
     <Render file="find-team-name" product="cloudflare-one" />
 
-17. Select **Save Changes**.
+16. Select **Save Changes**.
 
 To test that your connection is working, follow the steps on [SSO Integration](/cloudflare-one/integrations/identity-providers/#test-idps-in-cloudflare-one).
 
@@ -65,4 +65,4 @@ To test that your connection is working, follow the steps on [SSO Integration](/
 	"type": "facebook",
 	"name": "my example idp"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
index 583bae2a4359175..8ffadf28cdfd7c6 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
@@ -55,8 +55,8 @@ To configure GitHub access in both GitHub and Cloudflare One:
 14. Select **Save**.
 
 15. Select **Finish setup** to launch a GitHub authorization page. You will be asked to grant the following permissions to Cloudflare Access:
-    - Organizations and teams (read-only)
-    - Email addresses (read-only)
+	- Organizations and teams (read-only)
+	- Email addresses (read-only)
 
 16. Select **Authorize**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
index e8868c73cbac521..643ef76b062e609 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
@@ -10,6 +10,7 @@ tags:
 
 import { Render } from "~/components";
 
+
 Cloudflare One integrates with your organization's identity provider to apply Cloudflare One and Secure Web Gateway policies. If you work with partners, contractors, or other organizations, you can integrate multiple identity providers simultaneously.
 
 As an alternative to configuring an identity provider, Cloudflare One can send a [one-time PIN (OTP)](/cloudflare-one/integrations/identity-providers/one-time-pin/) to approved email addresses. No configuration needed — simply add a user's email address to an [Access policy](/cloudflare-one/access-controls/policies/) and to the group that allows your team to reach the application. You can simultaneously configure an OTP and an identity provider to allow users to use their own authentication method.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
index 88472d050f21f91..2ef2f3ad811f160 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
@@ -78,13 +78,13 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
 
    ![Configuring the Groups claim filter in Okta](~/assets/images/cloudflare-one/identity/okta/okta-2.png)
 
+
 9. Set **Groups claim filter** to _Matches regex_ and its value to `.*`.
 
 :::note[Token claim expressions]
-
 - Groups managed outside of Okta (for example, Microsoft Entra ID or Google groups) may require different regex values. For more information, refer to the Okta documentation on [Groups Claims](https://support.okta.com/help/s/article/Why-isnt-my-Groups-claim-returning-Active-Directory-groups) and [OpenID Connect Claims](https://support.okta.com/help/s/article/Can-we-retrieve-both-Active-Directory-and-Okta-groups-in-OpenID-Connect-claims).
 - To configure more complex expressions, refer to Okta's [token claims documentation](https://help.okta.com/okta_help.htm?type=oie&locale=en&id=federated-claims-overview).
-  :::
+:::
 
 10. In the **General** tab, copy the **Client ID** and **Client secret**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
index 9d30c743f2b37e0..6e57a4c17621c6c 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
@@ -46,6 +46,7 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C
    | `givenName`           | Given Name     |
    | `surName`             | Family Name    |
 
+
    These [SAML attributes](/cloudflare-one/integrations/identity-providers/generic-saml/#saml-attributes) tell Cloudflare Access who the user is.
 
 9. Set the application to **Active**.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
index 698b9665695a37d..1dfbd4cc2c93d21 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
@@ -37,10 +37,12 @@ To set up Signed AuthN requests:
    Ensure that your IdP validation uses the most recent certificate. Cloudflare Access routinely rotates the public key as a security measure.
 
    Cloudflare Access uses a certificate that includes the following 2 distinguished name fields:
+
    - **Issuer Distinguished Name** - `CN=cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
    - **Subject Distinguished Name** - `CN=*.cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
 
    Most IdP configurations require 3 components to enforce AuthN signature verification:
+
    - **Certificate issuer [distinguished name (DN)](https://knowledge.digicert.com/generalinformation/INFO1745.html)**
    - **Certificate subject distinguished name**
    - **Public certificate**
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
index 470285aa6aaa407..164e679ec887af6 100644
--- a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
@@ -18,8 +18,8 @@ Service-to-service integrations allow the Cloudflare One Client to get device po
 
 ## Supported operating systems
 
-| Device posture check                                                                    | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| --------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| Device posture check                                                                        | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| ------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
 | [Custom integration](/cloudflare-one/integrations/service-providers/custom/)            | ✅    | ✅      | ✅    | ✅  | ✅               |
 | [Crowdstrike](/cloudflare-one/integrations/service-providers/crowdstrike/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
 | [Kolide](/cloudflare-one/integrations/service-providers/kolide/)                        | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
index ff02d7946387387..e973af0760d4ab3 100644
--- a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
@@ -11,17 +11,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-one-connectivity-options"
-	product="networking-services"
-	params={{
-		unifiedRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-	}}
+  file="cloudflare-one-connectivity-options"
+  product="networking-services"
+  params={{
+    unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+    connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
+    cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+    onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
index c69c567e9be0058..7e26c4da5a75875 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
@@ -37,7 +37,6 @@ flowchart LR
   node --> db
   node --> printer
 ```
-
 ## Manage routes
 
 Use CIDR routes to forward traffic from your mesh node to devices on your local network.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
index 98f1c0ce87d79e1..4d20096eb33e2fd 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
@@ -15,8 +15,8 @@ Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`,
 
 The following table lists the cipher suites supported by `cloudflared`:
 
-| Protocol support            | Cipher suites                                                                                                                                                                                                                                                                              |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| TLS 1.3 only                | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256`                                                                                                                                                                                                 |
-| TLS 1.2 only                | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
-| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`                                                                                                                     |
+| Protocol support | Cipher suites |
+|------------------|----------------|
+| TLS 1.3 only | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256` |
+| TLS 1.2 only | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
+| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA` |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
index e0edd83ad74e895..f60f0eecf786013 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 3
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing  } from "~/components";
 
 After [creating your Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/), you can configure various aspects of how `cloudflared` runs and connects your infrastructure to Cloudflare's network. This section covers advanced configuration options to optimize tunnel performance, security, and availability.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
index 19d5f191ab29920..b6e4ec71f36882d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
@@ -13,13 +13,11 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/origin-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-		validatingJwtURL:
-			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
-	}}
+  file="tunnel/origin-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
index f6088ef1050edb8..3b9c067dddd114d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
@@ -65,70 +65,70 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-   <Tabs syncKey="dashPlusAPI">
-   	<TabItem label="Dashboard">
-   	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
-   	2. Select a `cloudflared` tunnel and select **Edit**.
-   	3. Select **Refresh token**.
-   	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
-   
-   	</TabItem>
-   	<TabItem label="API">
-   		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
-   
-   				```sh
-   				openssl rand -base64 32
-   				```
-   
-   				```sh output
-   				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
-   				```
-   
-   	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
-   
-   			<APIRequest
-   				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-   				method="PATCH"
-   				json={{
-   					name: "Example tunnel",
-   					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
-   				}}
-   			/>
-   
-   			```sh output {18}
-   			{
-   				"success": true,
-   				"errors": [],
-   				"messages": [],
-   				"result": {
-   					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
-   					"account_tag": "699d98642c564d2e855e9661899b7252",
-   					"created_at": "2024-12-04T22:03:26.291225Z",
-   					"deleted_at": null,
-   					"name": "Example tunnel",
-   					"connections": [],
-   					"conns_active_at": null,
-   					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
-   					"tun_type": "cfd_tunnel",
-   					"metadata": {},
-   					"status": "inactive",
-   					"remote_config": true,
-   					"token": "eyJhIjoiNWFiNGU5Z..."
-   				}
-   			}
-   			```
-   
-   	3.  Copy the `token` value shown in the output.
-   
-   	</TabItem>
-   	</Tabs>
-
-   After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
+	<Tabs syncKey="dashPlusAPI">
+	<TabItem label="Dashboard">
+	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
+	2. Select a `cloudflared` tunnel and select **Edit**.
+	3. Select **Refresh token**.
+	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+
+	</TabItem>
+	<TabItem label="API">
+		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
+
+				```sh
+				openssl rand -base64 32
+				```
+
+				```sh output
+				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
+				```
+
+	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
+
+			<APIRequest
+				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+				method="PATCH"
+				json={{
+					name: "Example tunnel",
+					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
+				}}
+			/>
+
+			```sh output {18}
+			{
+				"success": true,
+				"errors": [],
+				"messages": [],
+				"result": {
+					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
+					"account_tag": "699d98642c564d2e855e9661899b7252",
+					"created_at": "2024-12-04T22:03:26.291225Z",
+					"deleted_at": null,
+					"name": "Example tunnel",
+					"connections": [],
+					"conns_active_at": null,
+					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
+					"tun_type": "cfd_tunnel",
+					"metadata": {},
+					"status": "inactive",
+					"remote_config": true,
+					"token": "eyJhIjoiNWFiNGU5Z..."
+				}
+			}
+			```
+
+	3.  Copy the `token` value shown in the output.
+
+	</TabItem>
+	</Tabs>
+
+	After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
 2. On half of your `cloudflared` replicas, reinstall the `cloudflared` service with the new token. For example, on a Linux host:
 
    ```sh
-    sudo cloudflared service uninstall
+	 sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
@@ -140,9 +140,9 @@ To rotate a tunnel token:
 
    While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
-4. Wait 10 minutes for traffic to route through the new connectors.
+5. Wait 10 minutes for traffic to route through the new connectors.
 
-5. Repeat steps 2, 3, and 4 for the second half of the replicas.
+6. Repeat steps 2, 3, and 4 for the second half of the replicas.
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
@@ -163,7 +163,7 @@ If your tunnel token is compromised, we recommend taking the following steps:
 3. On each `cloudflared` replica, update `cloudflared` to use the new token. For example, on a Linux host:
 
    ```sh
-    sudo cloudflared service uninstall
+	 sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
index c545b148afb32c3..6840e8a166897b2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
@@ -14,21 +14,15 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/run-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		usageMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		tunnelWithFirewallURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
-		tunnelPermissionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
-		createRemoteTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
-		faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/",
-	}}
+  file="tunnel/run-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    usageMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    tunnelWithFirewallURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
+    tunnelPermissionsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
+    createRemoteTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
+    faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
index 81564acce0df5df..0a7cbccf1dcbcbc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
@@ -32,10 +32,7 @@ When `cloudflared` receives a request from a device, it uses the ports on the ho
 - `cloudflared` should be deployed on a dedicated host machine. This model is typically appropriate, but there may be serverless or clustered workflows where a dedicated host is not possible.
 - The host machine should allocate 50,000 ports to be available for use by the `cloudflared` service. The remaining ports are reserved for system administrative processes.
 
-<Render
-	file="tunnel/availability/port-configuration"
-	product="cloudflare-one"
-/>
+<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
 
 ### Private DNS
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
index 73321967dcd5876..5954dd3c2bbff27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
@@ -35,29 +35,22 @@ Ensure port `7844` is allowed for both TCP and UDP protocols (for `http2` and `q
 <Render file="tunnel/firewall/required-ports" product="cloudflare-one" />
 
 #### SNI-enforcing firewalls
-
 <Render file="tunnel/firewall/sni-hostnames" product="cloudflare-one" />
 
 ### Region US
 
 <Render
-	file="tunnel/firewall/us-region-ports"
-	product="cloudflare-one"
-	params={{
-		regionURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region",
-	}}
+  file="tunnel/firewall/us-region-ports"
+  product="cloudflare-one"
+  params={{ regionURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region" }}
 />
 
 ### Region FedRAMP High
 
 <Render
-	file="tunnel/firewall/fedramp-high-ports"
-	product="cloudflare-one"
-	params={{
-		tunnelTokenURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/",
-	}}
+  file="tunnel/firewall/fedramp-high-ports"
+  product="cloudflare-one"
+  params={{ tunnelTokenURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/" }}
 />
 
 ### Optional
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
index a02784740a89917..57b31886ddd0a26 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Deploy Cloudflare Tunnel in your environment — from cloud VMs to Kubernetes clusters, with Infrastructure as Code support.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
index 2e42733bf93cb6e..1c27eaad46459cc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
@@ -86,6 +86,7 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
+
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
index 6dad6b29b8df2dc..60b688f0c55e95a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
@@ -31,12 +31,12 @@ import { Render } from "~/components";
 
 ## Manage private networks
 
-| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `cloudflared tunnel route ip add <IP/CIDR> <NAME or UUID>` | Adds any network route space (represented as a CIDR) to your routing table. That network space becomes reachable for requests egressing from a user's machine as long as it is using the Cloudflare One Client and is enrolled in the same account that is running the tunnel chosen here. Further, those requests will be proxied to the specified tunnel, and reach an IP in the given CIDR, as long as that IP is reachable from the tunnel. To assign the IP route to a specific [Virtual Network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/), use the `--vnet` option. |
-| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | `cloudflared tunnel route ip delete`                       | Deletes the row for a given CIDR from your routing table. That portion of your network will no longer be reachable by the Cloudflare One Client.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
index 75fdb3581cab640..e79d92232542499 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
@@ -7,10 +7,11 @@ sidebar:
   order: 102
 head: []
 description: View associated copyrights.
----
 
 ---
 
+***
+
 [https://github.com/BurntSushi/toml](https://github.com/BurntSushi/toml)
 
 The MIT License (MIT)
@@ -35,7 +36,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/Sirupsen/logrus](https://github.com/Sirupsen/logrus)
 
@@ -61,7 +62,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/beorn7/perks/](https://github.com/beorn7/perks/)
 
@@ -86,7 +87,7 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
----
+***
 
 [https://github.com/certifi/gocertifi](https://github.com/certifi/gocertifi)
 
@@ -94,7 +95,7 @@ This Source Code Form is subject to the terms of the Mozilla Public License,
 v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain
 one at [http://mozilla.org/MPL/2.0/](http://mozilla.org/MPL/2.0/).
 
----
+***
 
 [https://github.com/coreos/go-oidc/](https://github.com/coreos/go-oidc/)
 [https://github.com/coreos/go-systemd/](https://github.com/coreos/go-systemd/)
@@ -305,7 +306,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/facebookgo/grace](https://github.com/facebookgo/grace)
 
@@ -318,14 +319,14 @@ Copyright (c) 2015, Facebook, Inc. All rights reserved.
 Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-- Redistributions of source code must retain the above copyright notice, this
+* Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-- Redistributions in binary form must reproduce the above copyright notice,
+* Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-- Neither the name Facebook nor the names of its contributors may be used to
+* Neither the name Facebook nor the names of its contributors may be used to
   endorse or promote products derived from this software without specific
   prior written permission.
 
@@ -340,7 +341,7 @@ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/getsentry/raven-go](https://github.com/getsentry/raven-go)
 
@@ -351,13 +352,13 @@ Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
 met:
 
-- Redistributions of source code must retain the above copyright
+* Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
-- Redistributions in binary form must reproduce the above
+* Redistributions in binary form must reproduce the above
   copyright notice, this list of conditions and the following disclaimer
   in the documentation and/or other materials provided with the
   distribution.
-- Neither the name of Apollic Software, LLC nor the names of its
+* Neither the name of Apollic Software, LLC nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 
@@ -373,7 +374,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/glycerine/rbtree](https://github.com/glycerine/rbtree)
 
@@ -397,7 +398,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/golang/protobuf](https://github.com/golang/protobuf)
 
@@ -433,7 +434,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/lib/pq](https://github.com/lib/pq)
 
@@ -446,9 +447,9 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
----
+***
 
-[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\_protobuf\_extensions/pbutil)
+[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\\_protobuf\\_extensions/pbutil)
 
 ```
                              Apache License
@@ -658,7 +659,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/mitchellh/go-homedir](https://github.com/mitchellh/go-homedir)
 
@@ -684,7 +685,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/pkg/errors](https://github.com/pkg/errors)
 
@@ -694,10 +695,10 @@ All rights reserved.
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
 
-- Redistributions of source code must retain the above copyright notice, this
+* Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-- Redistributions in binary form must reproduce the above copyright notice,
+* Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
@@ -712,10 +713,10 @@ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
-[https://github.com/prometheus/client_golang](https://github.com/prometheus/client_golang)
-[https://github.com/prometheus/client_model](https://github.com/prometheus/client_model)
+[https://github.com/prometheus/client\_golang](https://github.com/prometheus/client_golang)
+[https://github.com/prometheus/client\_model](https://github.com/prometheus/client_model)
 [https://github.com/prometheus/common](https://github.com/prometheus/common)
 [https://github.com/prometheus/procfs](https://github.com/prometheus/procfs)
 
@@ -927,7 +928,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/urfave/cli](https://github.com/urfave/cli)
 
@@ -953,7 +954,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
----
+***
 
 [https://github.com/go-yaml/yaml](https://github.com/go-yaml/yaml)
 
@@ -1165,7 +1166,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://zombiezen.com/go/capnproto2](https://zombiezen.com/go/capnproto2)
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
index 6299a916a068aac..c3079b110404278 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
@@ -6,6 +6,7 @@ products:
 title: License
 sidebar:
   order: 51
+
 ---
 
 Apache License
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
index 1004578cbdb1b59..e880dc05a8955b9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
@@ -30,12 +30,12 @@ Follow this guide to set up a Cloudflare Tunnel using the API.
 Make a `POST` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/create/) endpoint:
 
 <APIRequest
-	path="/accounts/{account_id}/cfd_tunnel"
-	method="POST"
-	json={{
-		name: "api-tunnel",
-		config_src: "cloudflare",
-	}}
+  path="/accounts/{account_id}/cfd_tunnel"
+  method="POST"
+  json={{
+    name: "api-tunnel",
+    config_src: "cloudflare",
+  }}
 />
 
 ```sh output
@@ -80,47 +80,46 @@ Before you publish an application through your tunnel, you must:
 
 Follow these steps to publish an application to the Internet. If you are looking to connect a private resource, skip to the [Connect a network](#3b-connect-a-network) section.
 
-1.  Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
-
-        <APIRequest
-        	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
-        	method="PUT"
-        	json={{
-        		config: {
-        			ingress: [
-        				{
-        					hostname: "app.example.com",
-        					service: "http://localhost:8001",
-        					originRequest: {},
-        				},
-        				{
-        					service: "http_status:404",
-        				},
-        			],
-        		},
-        	}}
-        />
-
-    :::note
-    If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-    :::
-
-    Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
-
-2.  [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
-
-        <APIRequest
-        	path="/zones/{zone_id}/dns_records"
-        	method="POST"
-        	json={{
-        		type: "CNAME",
-        		proxied: true,
-        		name: "app.example.com",
-        		content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
-        	}}
-        />
-
-    This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
+1. Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
+
+		<APIRequest
+			path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
+			method="PUT"
+			json={{
+				config: {
+					ingress: [
+						{
+							hostname: "app.example.com",
+							service: "http://localhost:8001",
+							originRequest: {},
+						},
+						{
+							service: "http_status:404",
+						},
+					],
+				},
+			}}
+		/>
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
+
+   Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
+
+2. [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
+
+		<APIRequest
+			path="/zones/{zone_id}/dns_records"
+			method="POST"
+			json={{
+				type: "CNAME",
+				proxied: true,
+				name: "app.example.com",
+				content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
+			}}
+		/>
+
+   This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
 
 This application will be publicly available on the Internet once you [run the tunnel](#4-install-and-run-the-tunnel). To allow or block specific users, [create an Access application](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/).
 
@@ -129,13 +128,13 @@ This application will be publicly available on the Internet once you [run the tu
 To connect a private network through your tunnel, [add a tunnel route](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/create/):
 
 <APIRequest
-	path="/accounts/{account_id}/teamnet/routes"
-	method="POST"
-	json={{
-		network: "172.16.0.0/16",
-		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-		comment: "Example private network route",
-	}}
+  path="/accounts/{account_id}/teamnet/routes"
+  method="POST"
+  json={{
+    network: "172.16.0.0/16",
+    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+    comment: "Example private network route",
+  }}
 />
 
 `cloudflared` can now route traffic to these destination IPs. To configure Zero Trust policies and connect as a user, refer to [Connect private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/).
@@ -151,11 +150,11 @@ Install `cloudflared` on your server and run the tunnel using the `token` value
 To check if the tunnel is serving traffic:
 
 <APIRequest
-	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-	method="GET"
-	parameters={{
-		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-	}}
+  path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+  method="GET"
+  parameters={{
+    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+  }}
 />
 
 ```sh output
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
index 18e2da263fc28c1..87b44a017b40937 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
@@ -18,11 +18,7 @@ Follow this step-by-step guide to create your first [remotely-managed tunnel](/c
 
 ## 1. Create a tunnel
 
-<Stream
-	id="4b75ad2aa58700602e94b148827687a2"
-	title="How to set up Cloudflare Tunnel"
-	thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png"
-/>
+<Stream id="4b75ad2aa58700602e94b148827687a2" title="How to set up Cloudflare Tunnel" thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png" />
 
 <Render file="tunnel/create-tunnel" product="cloudflare-one" />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
index 2482ef654c8cfb8..ca65ff18a9887ff 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Set up your first tunnel
+
 ---
 
-import { DirectoryListing, GlossaryTooltip } from "~/components";
+import { DirectoryListing, GlossaryTooltip } from "~/components"
 
 To create and manage tunnels, you will need to install and authenticate <GlossaryTooltip term="cloudflared"><code>cloudflared</code></GlossaryTooltip> on your origin server. `cloudflared` is what connects your server to Cloudflare's global network.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
index 6dda076ed46e587..017e02c4b363879 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
@@ -13,8 +13,8 @@ tags:
 
 import { Render, Stream } from "~/components";
 
-:::note[Looking to expose public applications?]
-This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel).
+:::note[Looking to expose public applications?] 
+This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel). 
 :::
 
 Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (`cloudflared`) creates [outbound-only connections](#outbound-only-connections) to Cloudflare's global network. Cloudflare Tunnel can connect HTTP web servers, [SSH servers](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/), [remote desktops](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/), and other protocols safely to Cloudflare. This way, your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
index d346bec2114ef0d..25b86d04e55286d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Monitor tunnels
 sidebar:
   order: 9
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
index 90b446cff03deba..a23a3c04da466a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
@@ -6,9 +6,10 @@ products:
 title: Notifications
 sidebar:
   order: 1
+
 ---
 
-import { AvailableNotifications } from "~/components";
+import { AvailableNotifications } from "~/components"
 
 Administrators can receive an alert when Cloudflare Tunnels in an account change their health or deployment status. Notifications can be delivered via email, webhook, and third-party services.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
index e80b571a1bbc009..b2dd6df9595c190 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
@@ -24,9 +24,9 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 4. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/) for this tunnel route. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
 
-   :::note
-   To create a new virtual network, select **Manage virtual networks**.
-   :::
+	:::note
+	To create a new virtual network, select **Manage virtual networks**.
+	:::
 
 ## 2. Set up the client
 
@@ -34,11 +34,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ## 3. Route private network IPs through the Cloudflare One Client
 
-<Render
-	file="tunnel/warp-to-tunnel-route-ips"
-	product="cloudflare-one"
-	params={{ one: "private network" }}
-/>
+<Render file="tunnel/warp-to-tunnel-route-ips" product="cloudflare-one" params={{ one: "private network"}}/>
 
 ## 4. (Recommended) Filter network traffic with Gateway
 
@@ -50,7 +46,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ### Zero Trust policies
 
-<Render file="tunnel/catch-all-policy" product="cloudflare-one" />
+<Render file="tunnel/catch-all-policy" product="cloudflare-one"/>
 
 If you have applications clearly defined by IPs or hostnames, we recommend [creating an Access application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) and managing user access alongside your SaaS and other web apps. Alternatively, if you prefer to secure a private network using a traditional firewall model, you can build Gateway network and DNS policies for IP ranges and domains.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
index 03dd3b5c2c280f9..9322c427b9241f5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
@@ -18,6 +18,5 @@ On the client side, end users connect to Cloudflare's global network using the C
 ![Diagram displaying connections between a device, Cloudflare, and a private network.](~/assets/images/cloudflare-one/connections/private-ips-diagram.png)
 
 To enable remote access to your private network, refer to the following guides:
-
 - [**Connect a private hostname**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/): Route network traffic to an internal application using its hostname.
-- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
+- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
index f4e9849be0a0224..180ab16892b1bcf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 By default, all DNS requests on the user device are resolved by Cloudflare's [public DNS resolver](/1.1.1.1/) except for common top level domains used for local resolution (such as `localhost`). You can connect an internal DNS resolver to Cloudflare and use it to resolve non-publicly routed domains.
 
@@ -18,23 +18,24 @@ By default, all DNS requests on the user device are resolved by Cloudflare's [pu
 
 To resolve private DNS queries:
 
-1.  [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
+1. [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
 
-2.  Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
+2. Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
 
-        :::note
+		:::note
 
-        Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
+		Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
 
-        :::
+		:::
 
-3.  Route specific DNS queries to your internal DNS resolver using one of the following options:
-    - [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
-    - Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
+3. Route specific DNS queries to your internal DNS resolver using one of the following options:
 
-4.  [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
+	- [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
+	- Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
 
-5.  Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
+4. [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
+
+5. Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
 
 The Cloudflare One Client will now send DNS queries to your internal DNS resolver for resolution. To learn more, refer to [How the Cloudflare One Client handles DNS requests](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/#how-the-warp-client-handles-dns-requests).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
index 99d934881a0f10d..98430c7fdc1b90a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
@@ -17,14 +17,13 @@ import { Render } from "~/components";
 ## Create a DNS record
 
 <Render
-	file="tunnel/dns-records-create"
-	product="cloudflare-one"
-	params={{
-		certPemURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem",
-	}}
+  file="tunnel/dns-records-create"
+  product="cloudflare-one"
+  params={{
+    certPemURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem"
+  }}
 />
 
 ## Cloudflare settings
 
-<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
+<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
index f658fb166750775..17cb132130adfc8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
@@ -15,12 +15,10 @@ import { Render } from "~/components";
 When you [add a published application route](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application) to a Cloudflare Tunnel, you are instructing Cloudflare to proxy requests for your public hostname to a service running privately behind `cloudflared`.
 
 <Render
-	file="tunnel/protocols-table"
-	product="cloudflare-one"
-	params={{
-		disableTlsVerificationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
-		locallyManagedTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications",
-	}}
+  file="tunnel/protocols-table"
+  product="cloudflare-one"
+  params={{
+    disableTlsVerificationURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
+    locallyManagedTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
index cbb16832f033141..05468c98e98ec02 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
@@ -25,14 +25,12 @@ When you add a [published application route](/cloudflare-one/networks/connectors
 ### Create a load balancer
 
 <Render
-	file="tunnel/availability/load-balancer-create"
-	product="cloudflare-one"
-	params={{
-		publishedAppRouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-		tunnelIdLocation:
-			"the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**",
-	}}
+  file="tunnel/availability/load-balancer-create"
+  product="cloudflare-one"
+  params={{
+    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+    tunnelIdLocation: "the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**"
+  }}
 />
 
 Refer to the [Load Balancing documentation](/load-balancing/) for more details on load balancer settings and configurations.
@@ -81,7 +79,6 @@ graph LR
 ```
 
 As shown in the diagram, a typical setup includes:
-
 - A dedicated Cloudflare Tunnel per data center.
 - One load balancer pool per tunnel. The load balancer hostname is set to the user-facing application hostname (`app.example.com`).
 - One load balancer endpoint per pool. The endpoint host header is set to the `cloudflared` published application hostname (`server1.example.com`)
@@ -149,12 +146,12 @@ Here is an example of what your DNS records will look like before and after sett
 | CNAME | app1 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app2 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app1 | `<UUID_2>.cfargotunnel.com` |
-| CNAME | app2 | `<UUID_2>.cfargotunnel.com` |
+| CNAME | app2 | `<UUID_2>.cfargotunnel.com`  |
 
 **After**:
 | Type | Name | Content |
 | ---- | ---- | ------- |
-| LB | `lb.example.com` | n/a |
+| LB   | `lb.example.com` | n/a |
 | CNAME | app1 | `lb.example.com` |
 | CNAME | app2 | `lb.example.com` |
 
@@ -163,12 +160,11 @@ Here is an example of what your DNS records will look like before and after sett
 ### Monitors and TCP tunnel origins
 
 <Render
-	file="tunnel/availability/load-balancer-tcp-monitors"
-	product="cloudflare-one"
-	params={{
-		publishedAppRouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-	}}
+  file="tunnel/availability/load-balancer-tcp-monitors"
+  product="cloudflare-one"
+  params={{
+    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application"
+  }}
 />
 
 ### Session affinity and replicas
@@ -178,10 +174,9 @@ The load balancer does not distinguish between [replicas](/cloudflare-one/networ
 ### Local connection preference
 
 <Render
-	file="tunnel/availability/load-balancer-local-connection"
-	product="cloudflare-one"
-	params={{
-		replicasURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/",
-	}}
+  file="tunnel/availability/load-balancer-local-connection"
+  product="cloudflare-one"
+  params={{
+    replicasURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
index ee3c9509de79961..d9c0787deeffdfa 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
@@ -74,4 +74,5 @@ If you see an error with the title `This site can't provide a secure connection`
 
 If you added a [multi-level subdomain](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) as Cloudflare's Universal certificate will not cover the public hostname by default.
 
+
 For more information on Tunnel errors, view your [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) or [contact Cloudflare Support](/support/contacting-cloudflare-support/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
index 0c3a0e8a6720af6..04c3693aabbaeb1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
@@ -28,53 +28,44 @@ The steps for getting diagnostic logs depend on your `cloudflared` deployment en
 These instructions apply to remotely-managed and locally-managed tunnels running directly on the host machine.
 
 <Render
-	file="tunnel/diagnostics/host-environment"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/host-environment"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address"
+  }}
 />
 
 ### Docker
 
 <Render
-	file="tunnel/diagnostics/docker"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		defaultMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/docker"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
+  }}
 />
 
 ### Kubernetes
 
 <Render
-	file="tunnel/diagnostics/kubernetes"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		defaultMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/kubernetes"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
+  }}
 />
 
 ## cloudflared-diag files
 
 <Render
-	file="tunnel/diagnostics/tunnel-diag-file"
-	product="cloudflare-one"
-	params={{
-		runParametersURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
-		logsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
-		loglevelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server",
-	}}
+  file="tunnel/diagnostics/tunnel-diag-file"
+  product="cloudflare-one"
+  params={{
+    runParametersURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
+    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
+    loglevelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
index 61105e303be197e..281adab55837939 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 10
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore resources to help you resolve issues with Cloudflare Tunnel connectivity and configuration.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
index 19b86f3981d6630..465c95783571898 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
@@ -7,11 +7,12 @@ title: Use cases
 hidden: false
 sidebar:
   order: 4
+
 ---
 
 Cloudflare Tunnel creates a secure, outbound-only connection between your services and Cloudflare by deploying a lightweight connector in your environment. Here is how to use tunnels with some specific services:
 
-- [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
-- [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
-- [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
-- [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
+* [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
+* [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
+* [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
+* [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
index 8ae62963190d27f..c39aca829aac5a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
@@ -17,4 +17,4 @@ Cloudflare offers three ways to secure RDP:
 
 - [Browser-based RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser/)
 - [RDP with Cloudflare One Client](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client/)
-- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
+- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
index e9787ea4da56ea5..7830923733b5e59 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
@@ -57,7 +57,7 @@ By default, Internet Explorer will be installed and configured in [Enhanced Secu
 
 <Render file="tunnel/connect-private-network" product="cloudflare-one" />
 
-3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the **Internal IP** of the VM instance.
+3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the  **Internal IP** of the VM instance.
 
 4. (Optional) [Set up Zero Trust policies](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#4-recommended-filter-network-traffic-with-gateway) to fine-tune access to your server.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
index de8d6a6065a81b3..dfb0e2feed3b4db 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
@@ -31,159 +31,160 @@ There are a number of different VNC server versions, deployments, and instances.
 
 For demonstration purposes, we will create a TightVNC server on an Ubuntu virtual machine (VM) hosted in Google Cloud Project (GCP). We will configure the VNC server to run XFCE, a lightweight desktop environment suitable for remote access. If you already have a VNC server installed, you can skip this step and [go to Step 2](#2-connect-the-server-to-cloudflare).
 
-1.  Open a terminal window for your Ubuntu VM.
+1. Open a terminal window for your Ubuntu VM.
 
-2.  Install XFCE and TightVNC by running the following command:
+2. Install XFCE and TightVNC by running the following command:
 
-        ```sh
-        sudo apt update
-        sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
+		```sh
+		sudo apt update
+		sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
 
-        ```
+		```
 
-        This command installs the desktop, some helpful utilities, and the VNC server software.
+		This command installs the desktop, some helpful utilities, and the VNC server software.
 
-3.  To initialize the VNC server:
-    1. Create a VNC server instance:
+3. To initialize the VNC server:
 
-       ```sh
-       vncserver
-       ```
+	1. Create a VNC server instance:
 
-    2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
+		```sh
+		vncserver
+		```
 
-       TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
+	2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
 
-    3. You will be asked if you want to create a view-only password. You can press `n` for no.
+		TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
 
-    4. Kill this initial session so that you can edit its configuration:
+	3. You will be asked if you want to create a view-only password. You can press `n` for no.
 
-       ```sh
-       vncserver -kill :1
-       ```
+	4. Kill this initial session so that you can edit its configuration:
 
-4.  Configure VNC to launch the XFCE desktop:
-    1. Create a VNC configuration directory if it is missing:
+		```sh
+		vncserver -kill :1
+		```
+4. Configure VNC to launch the XFCE desktop:
 
-    ```sh
-    mkdir -p ~/.vnc
-    ```
+	1. Create a VNC configuration directory if it is missing:
 
-    2. Open the `xstartup` file using a text editor. For example,
+	```sh
+	mkdir -p ~/.vnc
+	```
 
-    ```sh
-    vim ~/.vnc/xstartup
-    ```
+	2. Open the `xstartup` file using a text editor. For example,
 
-    3. Update the file to the following configuration:
+	```sh
+	vim ~/.vnc/xstartup
+	```
 
-    ```bash
-    #!/bin/sh
-    unset SESSION_MANAGER
-    unset DBUS_SESSION_BUS_ADDRESS
-    startxfce4
-    ```
+	3. Update the file to the following configuration:
 
-    4. Make the file executable:
+	```bash
+	#!/bin/sh
+	unset SESSION_MANAGER
+	unset DBUS_SESSION_BUS_ADDRESS
+	startxfce4
+	```
 
-    ```sh
-    chmod +x ~/.vnc/xstartup
-    ```
+	4. Make the file executable:
 
-5.  Start the VNC server again:
+	```sh
+	chmod +x ~/.vnc/xstartup
+	```
 
-    ```sh
-    vncserver -localhost :1
-    ```
+5. Start the VNC server again:
+	```sh
+	vncserver -localhost :1
+	```
 
-    The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
+	The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
 
-6.  (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
-    1. Open a terminal on the client machine.
+6. (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
 
-    2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
+	1. Open a terminal on the client machine.
 
-       ```sh
-       gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
-       ```
+	2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
 
-    3. Open your preferred VNC viewer application.
+		```sh
+		gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
+		```
 
-    4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
+	3. Open your preferred VNC viewer application.
 
-    You should see the Ubuntu VM desktop.
+	4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
 
-7.  (Optional) Configure the VNC server to start on boot:
-    1. Find the full path to the `vncserver` command:
+	You should see the Ubuntu VM desktop.
 
-       ```sh
-       which vncserver
-       ```
+7. (Optional) Configure the VNC server to start on boot:
 
-       ```sh output
-       /usr/bin/vncserver
-       ```
+	1. Find the full path to the `vncserver` command:
 
-    2. Create a new service configuration file:
+		```sh
+		which vncserver
+		```
+		```sh output
+		/usr/bin/vncserver
+		```
+	2. Create a new service configuration file:
 
-    ```sh
-    sudo vim /etc/systemd/system/vncserver@.service
-    ```
+	```sh
+	sudo vim /etc/systemd/system/vncserver@.service
+	```
 
-    3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
+	3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
 
-       ```toml
-       [Unit]
-       Description=Start TightVNC server at startup
-       After=syslog.target network.target
+		```toml
+		[Unit]
+		Description=Start TightVNC server at startup
+		After=syslog.target network.target
 
-       [Service]
-       Type=forking
-       User=[YOUR_USERNAME]
-       WorkingDirectory=/home/[YOUR_USERNAME]
+		[Service]
+		Type=forking
+		User=[YOUR_USERNAME]
+		WorkingDirectory=/home/[YOUR_USERNAME]
 
-       PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
+		PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
 
-       ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
-       ExecStart=/usr/bin/vncserver -localhost :%i
-       ExecStop=/usr/bin/vncserver -kill :%i
+		ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
+		ExecStart=/usr/bin/vncserver -localhost :%i
+		ExecStop=/usr/bin/vncserver -kill :%i
 
-       [Install]
-       WantedBy=multi-user.target
-       ```
+		[Install]
+		WantedBy=multi-user.target
+		```
 
-       4. Reload `systemd` to read in the new service file:
+		4. Reload `systemd` to read in the new service file:
 
-       ```sh
-       sudo systemctl daemon-reload
-       ```
+		```sh
+		sudo systemctl daemon-reload
+		```
 
-       5. Enable the service to start at boot:
+		5. Enable the service to start at boot:
 
-       ```sh
-       sudo systemctl enable vncserver@1.service
-       ```
+		```sh
+		sudo systemctl enable vncserver@1.service
+		```
 
-       The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
-       6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
+		The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
 
-       ```sh
-       sudo loginctl enable-linger [YOUR_USERNAME]
-       ```
+		6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
 
-       7. Start the service:
+		```sh
+		sudo loginctl enable-linger [YOUR_USERNAME]
+		```
 
-       ```sh
-       sudo systemctl start vncserver@1.service
-       ```
+		7. Start the service:
 
-       8. Check its status:
+		```sh
+		sudo systemctl start vncserver@1.service
+		```
 
-       ```sh
-       sudo systemctl status vncserver@1.service
-       ```
+		8. Check its status:
 
-       The VNC server will now start automatically every time the VM boots.
+		```sh
+		sudo systemctl status vncserver@1.service
+		```
+
+		The VNC server will now start automatically every time the VM boots.
 
 ## 2. Connect the server to Cloudflare
 
@@ -197,7 +198,7 @@ For demonstration purposes, we will create a TightVNC server on an Ubuntu virtua
 
 5. For **Service**, select _TCP_ and enter `localhost:<5901>`. If the VNC server is on a different machine from where you installed the tunnel, enter `<SERVER_IP>:5901`.
 
-   Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
+	Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
 
 6. Save the route.
 
@@ -219,10 +220,7 @@ Create a Cloudflare Access application that users can access through their brows
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-   <Render
-   	file="access/self-hosted-app/browser-rendering-policies"
-   	product="cloudflare-one"
-   />
+	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
 
 7. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
index 7f5b8371def9c4d..621709d181b4715 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
@@ -6,8 +6,7 @@ products:
 sidebar:
   order: 10
 head: []
-description:
-  Use Cloudflare WAN's different analytic options for an overview of the
+description: Use Cloudflare WAN's different analytic options for an overview of the
   performance of your sites, or to troubleshoot potential issues.
 tags:
   - Analytics
@@ -17,21 +16,15 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		networkAnalyticsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		traceRoutes:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
-		graphQlTunnelBandwidthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/",
-	}}
+		networkAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		traceRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
+		graphQlTunnelBandwidthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		siteAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/"
+		 }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
index f685696ff741fda..d3c2fff924b3af7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -15,11 +15,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/netflow"
-	product="networking-services"
-	params={{
-		breakoutTrafficURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
-	}}
-/>
+<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" params={{ breakoutTrafficURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/" }} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
index 81bc27fef3b688e..4694b2188d10e76 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
@@ -15,10 +15,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN",
+		magicWord: "CF1 Cloudflare WAN"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
index 0a93283b55966af..c7a0918e9e4281f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
index 12fc47ede0c7643..761d5ad3c83ef95 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -12,10 +12,9 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
index a7cdd1152a38d1e..6c2c604b49fd3c4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -12,10 +12,8 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }}
-/>
+	params={{ productName: "Cloudflare WAN" }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
index 294f9511dcdaaa2..9a1e57ebda7c9dd 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
@@ -13,21 +13,18 @@ tags:
   - Analytics
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions:
-			"Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions: "Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "CF1 Cloudflare WAN",
 		networkOverviewPageName: "Network visibility",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
-	}}
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
+		}}
 />
 
 ### Set thresholds for site health
@@ -37,7 +34,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index e5c5a9d02461bc1..e934890d0601507 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,59 +11,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "hardware",
-		productName: "Cloudflare One Appliance",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "CF1 Cloudflare WAN",
-		sfpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-		wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-		lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-		noConnectorShows:
-			"You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage: "The Connector is shipped to you deactivated",
-		hardSoftConn:
-			"You need to deploy two Connectors in your premises before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		referenceInformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "hardware",
+	productName: "Cloudflare One Appliance",
+	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "CF1 Cloudflare WAN",
+	sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+	wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+	lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+	noConnectorShows: "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
+	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "The Connector is shipped to you deactivated",
+	hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+  maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index 7d8436c9226ce40..e8ca4f7240d425e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,8 +4,10 @@ description: Reference information for SFP+ port information in Zero Trust netwo
 products:
   - cloudflare-one
 title: SFP+ port information
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info" product="networking-services" />
+<Render file="mconn/sfp-port-info"
+	product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
index 5299a10b9e18f37..6a1b94bdb249832 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
@@ -10,56 +10,34 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "virtual",
-		productName: "Cloudflare One Appliance",
-		productNameVirtual: "Virtual Appliance",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "CF1 Cloudflare WAN",
-		wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
-		lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
-		noConnectorShows:
-			"For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage: "Virtual Appliance is deactivated after you install it",
-		hardSoftConn:
-			"You need to install two Virtual Appliances before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-		referenceInformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "virtual",
+	productName: "Cloudflare One Appliance",
+	productNameVirtual: "Virtual Appliance",
+	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "CF1 Cloudflare WAN",
+	wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
+	lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
+	noConnectorShows: "For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
+	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "Virtual Appliance is deactivated after you install it",
+	hardSoftConn: "You need to install two Virtual Appliances before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
index c0051513debf6e3..ffd0a4c4b645784 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+		troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
index cb114ce2b99fa6c..fb436734ed7d217 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,12 +15,9 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Virtual Appliance",
-		virtualUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
+		virtualUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index c7cbae7c3ceabbf..ac563378234270b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -14,9 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-	}}
-/>
+		hardwareConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+		}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
index 6bcfc54764da629..35e5bf0f59c7313 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
@@ -6,6 +6,7 @@ products:
 title: Deactivate Connector
 sidebar:
   order: 8
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
index 490ed326c212d3f..f2b21ce17eccf65 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
@@ -6,6 +6,7 @@ products:
 title: Heartbeat
 sidebar:
   order: 9
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 630305e6d60c767..922634423e75753 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
index 056b0ca5a650163..c7b5151598427ee 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
@@ -6,6 +6,7 @@ title: Interrupt window
 description: Learn how to set up when Connector can update its systems.
 sidebar:
   order: 10
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 98554bc18b3cf72..3949eb19c151c2e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -15,5 +15,5 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-	}}
+		}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 3a9310c33020487..b7f774b674a7b81 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,16 +9,12 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "breakout",
-		featureName: "Breakout traffic",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		whatHappensApp:
-			"will now go directly to the Internet and bypass Cloudflare's filtering",
-		dashName: "CF1 Cloudflare WAN",
-	}}
-/>
+	magicWord: "breakout",
+	featureName: "Breakout traffic",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
+	dashName: "CF1 Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
index 0468257e119128d..b12153e883b952b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
@@ -4,16 +4,14 @@ description: How Application-aware policies works in Zero Trust networking.
 products:
   - cloudflare-one
 title: Application-aware policies
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/app-aware-policies/overview"
+<Render file="mconn/network-options/app-aware-policies/overview"
 	product="networking-services"
 	params={{
-		gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
-		appTypesGatewayURL:
-			"/cloudflare-one/policies/gateway/application-app-types/",
-	}}
-/>
+	gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
+	appTypesGatewayURL: "/cloudflare-one/policies/gateway/application-app-types/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 5aac85459c295d4..4067d211b871836 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,13 +9,11 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "prioritized",
-		featureName: "Prioritized traffic",
-		whatHappensApp: "is now processed first by Connector",
-		dashName: "CF1 Cloudflare WAN",
-	}}
-/>
+	magicWord: "prioritized",
+	featureName: "Prioritized traffic",
+	whatHappensApp: "is now processed first by Connector",
+	dashName: "CF1 Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index fb14bed9a02c912..2c0fe51a6772f0b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,13 +8,11 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-relay"
+<Render file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni:
-			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
+		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
 	}}
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 54ddbc7c233c16a..c8a992aa8ac61b7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,10 +8,9 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-server"
+<Render file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index 525082ff11a2ee0..a3ba4bd0341904e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,11 +8,9 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
index d3bb4e7b3f2a648..bda0220b0ebbf27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index bfd8e592fdc15f9..b6dc835b4894396 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,15 +8,11 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/link-aggregation"
+<Render file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 5405768ac68156c..1ccd87afb778419 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,17 +4,14 @@ products:
   - cloudflare-one
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Connector to  re-use address spaces locally.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/nat-subnet"
+<Render file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+	hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+  virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index b5133cb7577975e..43b9ee7508fbdd0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,16 +6,12 @@ title: Network segmentation
 description: Define policies to define if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/network-segmentation"
+<Render file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index 00ebfc4681edb6c..741b251ec5b73f3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,19 +4,15 @@ products:
   - cloudflare-one
 title: Routed subnets
 description: Learn how to configure routed subnets on a Connector, including setting static routes and next-hop addresses for complex LAN setups.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/routed-subnets"
+<Render file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+		netSubnetURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
index be5fdb923289884..63e642f8fee211d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
@@ -16,28 +16,17 @@ import { Render } from "~/components";
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		haSetupURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
-		ecmpRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		multipleWansURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
-		sfpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		haSetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
+		ecmpRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		multipleWansURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
+		sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
 		vlanIdURL: "#vlan-id",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		hcFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		dhcpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		hcFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		dhcpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
+		routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index bec67a3bb4ce2d5..3806aad41029a92 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -17,11 +17,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		activateURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		activateURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
index 854c24e84e725b5..5c087c6432ea87f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
@@ -16,14 +16,12 @@ import { Render } from "~/components";
 	params={{
 		dashInfo:
 			"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
-		graphQL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		graphQL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
 		notificationsPath:
 			"[notifications wizard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		magicWord: "CF1 Cloudflare WAN",
+		networkAnalytics: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		magicWord: "CF1 Cloudflare WAN"
 	}}
 />
 
@@ -41,8 +39,7 @@ import { Render } from "~/components";
 	file="tunnel-health/mconn-heartbeat-health"
 	product="networking-services"
 	params={{
-		heartbeatURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
index 5c56ccb5ff6fcbf..3b09a3fa29ff311 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
@@ -18,9 +18,7 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		magicTunnelHealthCheckCalculation:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/",
-		networkAnalyticsPath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		healthChecks:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsPath: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		healthChecks: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index 33927b2f361233a..4a5d426468f3433 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -12,7 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/custom-ike-id-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
index e3d0145968a7905..066c118ccf4222d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,14 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		greIpsecTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		greIpsecTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
index d1d59be9414d68b..f9858038dbd480e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
@@ -16,8 +16,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		healthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		healthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		addTunnelsPath:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index ca3e788d025bd8b..26d6f25b6a74b55 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,11 +13,10 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-	file="routing/configure-cloudflare-source-ips"
-	product="networking-services"
-	params={{
-		unifiedRoutingLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/",
-	}}
+  file="routing/configure-cloudflare-source-ips"
+  product="networking-services"
+  params={{
+    unifiedRoutingLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 334a23c9167b3af..2fd957397c1f902 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -6,37 +6,29 @@ products:
 sidebar:
   order: 2
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		trafficSteeringPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		trafficSteeringPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		addTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table",
+		routingTableName: "Cloudflare Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index d615ab646878dd7..1f5ce39957c3508 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -12,41 +12,26 @@ tags:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		cniLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		tunnelHealthChecksPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		tunnelsAndEncapsulationPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		cniLink: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		updateHCFrequencyPage: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		tunnelHealthChecksPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
+		tunnelHealthDash: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		configureARRURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
index 8d38559e9f784a5..478096429eb0edf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
index 006aa7559219809..91c321110a4e9fa 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -15,11 +15,8 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
index 7cfe5c8a32d1f27..ee5e8e31b67dd5d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index c44c422d412e3e9..2e3362c2297a304 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/alibaba-cloud"
-	product="networking-services"
-	params={{
-		ipSecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/alibaba-cloud"
+  product="networking-services"
+  params={{
+    ipSecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
index 53f7609c41d4c0e..47bdff355de0e2a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
@@ -10,13 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aruba-edgeconnect"
-	product="networking-services"
-	params={{
-		tunnelHealthCheckUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+<Render file="cloudflare-wan/third-party/aruba-edgeconnect"
+  product="networking-services"
+  params={{
+		tunnelHealthCheckUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		magicFirewallUrl: "/cloudflare-network-firewall/",
-		gatewayUrl: "/cloudflare-one/traffic-policies/",
-	}}
-/>
+		gatewayUrl: "/cloudflare-one/traffic-policies/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
index 4dde9787ebca0b6..dd27825eb60ed8a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
@@ -6,17 +6,14 @@ products:
 title: Amazon AWS Transit Gateway
 tags:
   - AWS
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aws"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/aws"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index b02d849640387d0..6e4f1a3573cbf12 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-virtual-wan"
-	product="networking-services"
-	params={{
-		tunnelHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		ipsecTunnelUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		cloudflareDocumentationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-virtual-wan"
+  product="networking-services"
+  params={{
+  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  cloudflareDocumentationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index e3af7916ddaaf15..6308449fc485359 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-vpn-gateway"
-	product="networking-services"
-	params={{
-		ipsecTunnelUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		staticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		tunnelHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
+  product="networking-services"
+  params={{
+  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  staticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
index 61a653693d0b777..3692dd21b4e45ca 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index df5158c103fe80f..26cd14b751b3d81 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -10,7 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-ios-xe"
-	product="networking-services"
+<Render file="cloudflare-wan/third-party/cisco-ios-xe"
+  product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index b752d4f85dab6f7..2bf5636cbdce15a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -10,25 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
-		trafficSteeringUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		paloAltoGuideUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+		antiReplayProtectionUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		unifiedRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		supportedConfigParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		paloAltoGuideUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 0da4cb37c63d84d..4af42ab35a2bc43 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fitelnet"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		typeId_ipv4_addrUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fitelnet"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    typeId_ipv4_addrUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
index e71cf29b9f07669..3869ebd7e5a01ea 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -10,19 +10,12 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fortinet"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		equalCostMultipathRoutingEcmpUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fortinet"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    equalCostMultipathRoutingEcmpUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
index e8e6fe1d8fc944a..e35533f9aa61fae 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
@@ -12,13 +12,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/google"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/google"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
index 88548b31947b629..28c8eb38103e3a7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
index f3b4d51ebae092c..9041812a55d647d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/juniper"
-	product="networking-services"
-	params={{
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/juniper"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
index 4fe095992306cb0..544a2fd71e1b10b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -10,13 +10,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/oracle"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/oracle"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
index d3a02cd42315066..74648ea559442b1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,15 +13,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/palo-alto"
-	product="networking-services"
-	params={{
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/palo-alto"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
index 8beb36669a01a5a..5c7329f8bb2a15d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -11,15 +11,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/pfsense"
-	product="networking-services"
-	params={{
-		configureTwoIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		staticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/pfsense"
+  product="networking-services"
+  params={{
+    configureTwoIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    staticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
index e2236e3c62ec88c..681705328bc2479 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sonicwall"
-	product="networking-services"
-	params={{
-		ipsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		creatingYourIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createYourStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sonicwall"
+  product="networking-services"
+  params={{
+    ipsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    creatingYourIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createYourStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index afc7910dc9d12af..b2a4c4249e87375 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sophos-firewall"
-	product="networking-services"
-	params={{
-		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		ikeIdUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sophos-firewall"
+  product="networking-services"
+  params={{
+    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    ikeIdUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
index bb005e68632169a..ceba0f994025298 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -11,11 +11,8 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/strongswan"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/strongswan"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 9a96fafe0bfa4ab..a97b5659741e9d7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -11,9 +11,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-wan/third-party/ubiquiti"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-	}}
+  file="cloudflare-wan/third-party/ubiquiti"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
index 736fbd873bbdd38..f944858befeffef 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -10,11 +10,8 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/velocloud"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/velocloud"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
index c7dc2d9c75ba0a6..1d4fe3f1866abf4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -11,15 +11,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/viptela"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		ciscoIosXeUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/viptela"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
index e79d26181aeb494..75be63a9bfe72a6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -10,4 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
+<Render file="cloudflare-wan/third-party/vyos"
+  product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
index b2355afb2d6994d..77d9af6a973237c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -10,13 +10,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/yamaha"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/yamaha"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
index 8cf6de52ad11759..f8e8f7694c90053 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
@@ -16,19 +16,12 @@ import { Render } from "~/components";
 	params={{
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		configureConnectorUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		configureMwanManually:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		greReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		mtuReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		configureConnectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		configureMwanManually: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ipsecReferenceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		mtuReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
index c804130785b3a29..8aac7ee6d2a4275 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
@@ -20,19 +20,13 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		connectorName: "Cloudflare One Appliance",
 		connectorCta: "Use Cloudflare One Appliance",
-		getStartedUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		connectorUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		zeroTrustUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
-		wanTransformationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/",
+		connectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		bgpRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
index c54c3b324cf1b28..a8d18b418df7a40 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
@@ -5,6 +5,7 @@ pcx_content_type: reference
 description: Reference information for Third party licenses in Zero Trust networking.
 products:
   - cloudflare-one
+
 ---
 
 import text from "./3rdparty.txt?raw";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
index 653b31922480265..70f7ed48d19fc64 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 12
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
index 475873e33440e3a..b6c275104b79281 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
@@ -13,21 +13,14 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="magic-cni"
-	product="networking-services"
-	params={{ magicWord: "Cloudflare WAN" }}
-/>
+<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
index 506e7260402fd54..0e0944033ed0838 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
@@ -17,17 +17,11 @@ import { Render } from "~/components";
 		magicWord: "CF1 Cloudflare WAN",
 		productNameWAN: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		thirdPartyIntegrationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
index bdb55cdaa44ca58..f827135b0192839 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -5,8 +5,7 @@ products:
 title: Anti-replay protection
 tags:
   - IPsec
-description:
-  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
index 32b8afa7e6f4527..6a168b9730c3943 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cloudflareTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
index a51b28317cfdf42..4fa1452c2f1d01c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
@@ -12,53 +12,29 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/reference/device-compatibility"
-	product="networking-services"
-	params={{
-		supportedConfigurationParametersUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		arubaEdgeconnectUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-		ciscoIosXeUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-		ciscoMerakiStaticUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-		ciscoSdWanUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
-		fortinetUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
-		fitelnetUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
-		juniperUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
-		paloAltoUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		pfsenseUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
-		sonicwallUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
-		sophosFirewallUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
-		strongswanUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
-		ubiquitiUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
-		velocloudUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
-		vyosUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
-		yamahaUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
-		alibabaCloudUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-		awsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
-		azureUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
-		googleUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
-		oracleUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/",
-	}}
-/>
+<Render file="cloudflare-wan/reference/device-compatibility"
+  product="networking-services"
+  params={{
+    supportedConfigurationParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    arubaEdgeconnectUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+    ciscoMerakiStaticUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+    ciscoSdWanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
+    fortinetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
+    fitelnetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
+    juniperUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
+    paloAltoUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+    pfsenseUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
+    sonicwallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
+    sophosFirewallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
+    strongswanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
+    ubiquitiUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
+    velocloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
+    vyosUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
+    yamahaUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
+    alibabaCloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+    awsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
+    azureUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
+    googleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
+    oracleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 32c6047307e94c8..e48aacf091b3898 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -19,18 +19,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		mssURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		productURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		mssURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		productURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index c08c54539b5b3b6..f4b1ec66d7f87c2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,13 +8,9 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination",
-	}}
+	params={{ tunnelStatePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination"	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
index 936eef5bb11c21b..c9bbdad031b4e3d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
index a6693ef9af219d6..dad3b9a5d8d8777 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
+		productName: "Cloudflare WAN"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
index c5d20719e86eb64..354bdbd705088a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
@@ -17,30 +17,22 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
+  	magicWord: "CF1 Cloudflare WAN",
+  	productName: "Cloudflare WAN",
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		greIpsecReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		createStaticRoute:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		editStaticRoute:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
-		setupBgpPeering:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
-		legacyHCs:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
-		tunnelHCsPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+  	greIpsecReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+  	createStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  	editStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
+  	setupBgpPeering: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		sourceIPsURL:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/",
 		virtualNetworkName: "Cloudflare Virtual Network",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
index f8b615e6070db55..276bc867f82dcd8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -18,16 +18,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		addTunnels:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
-		staticRoutes:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
index eace55f088f5192..d122736e9eeaedc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
@@ -9,15 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="cloudflare-wan/security-filters"
+<Render file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		gatewayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
index e5bc049482c1740..2eb4a9483c2622f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,15 +17,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
index fb5782e5fef4adf..1e718eb8e9c31ce 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 23dbe5aa1465d70..3f0cd1c1f120d63 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -10,19 +10,14 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index dd1b594c265542e..41ea7fb74a080e1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -13,18 +13,14 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
index fca3b17df568c35..49a3d8aef991d65 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -14,24 +14,17 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
index 0dcfa150778deae..a1fce7bc5634d3c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
@@ -17,15 +17,11 @@ import { Render } from "~/components";
 	file="cloudflare-wan/wan-transformation"
 	product="networking-services"
 	params={{
-		getStartedUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		connectivityOptionsUrl: "/cloudflare-one/networks/connectivity-options/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		zeroTrustUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		applianceUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		secureWanTrafficUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
+		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		applianceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		secureWanTrafficUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
index c39636c40320181..37ab275a843c03d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
@@ -18,36 +18,21 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfAutoCertificatesURL:
-			"/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
-		cfManualCertificatesURL:
-			"/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
-		decryptTlsURL:
-			"/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
-		doNotInspectURL:
-			"/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
-		warpChecksURL:
-			"/cloudflare-one/reusable-components/posture-checks/client-checks/",
-		osVersionChecks:
-			"/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
-		mwanOnrampsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		gatewayResolverPoliciesURL:
-			"/cloudflare-one/traffic-policies/resolver-policies/",
-		gatewayInternalDnsURL:
-			"/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfAutoCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
+		cfManualCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
+		decryptTlsURL: "/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
+		doNotInspectURL: "/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
+		warpChecksURL: "/cloudflare-one/reusable-components/posture-checks/client-checks/",
+		osVersionChecks: "/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
+		mwanOnrampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+		gatewayResolverPoliciesURL: "/cloudflare-one/traffic-policies/resolver-policies/",
+		gatewayInternalDnsURL: "/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
 		egressPoliciesURL: "/cloudflare-one/traffic-policies/egress-policies/",
-		gatewayLogsURL:
-			"/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
-		tcpMssClampingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		ikeURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		gatewayLogsURL: "/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
+		tcpMssClampingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		ikeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
index a6aa06e27222024..021d27ca4f6f08d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
@@ -18,23 +18,15 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/warp"
 	product="networking-services"
 	params={{
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		setupZeroTrustAccountURL:
-			"/cloudflare-one/setup/#2-create-a-zero-trust-organization",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		setupZeroTrustAccountURL: "/cloudflare-one/setup/#2-create-a-zero-trust-organization",
 		ztDashPath: "My Team > Devices",
-		splitTunnelsURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
-		warpDeploymentURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
-		warpIngressIpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
+		splitTunnelsURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
+		warpDeploymentURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
+		warpIngressIpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
 		mwanConnectorName: "Cloudflare One Appliance",
-		domainFallbackURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		domainFallbackURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index 0d372fbdcc0d99f..d1ca77abe7c8a72 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -15,15 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
index 510e6bd01921e87..86daf36cc1a9660 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
@@ -9,6 +9,7 @@ head:
   - tag: title
     content: Cloudflare One integration tutorials
 description: Learn how to integrate Cloudflare WAN with other Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
index a634aba89cca3ac..1bcbcba64603e90 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
@@ -16,11 +16,8 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/security-services"
 	product="networking-services"
 	params={{
-		networkFirewallURL:
-			"/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
-		gatewaySetupURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
-		wanTransformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		networkFirewallURL: "/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
+		gatewaySetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		wanTransformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
index 21c15ec9d2d739b..1db111952cb9cd0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-one
 ---
 
-import { Steps } from "~/components";
+import { Steps } from '~/components';
 
 You can scope Cloudflare member permissions to individual [Cloudflare Tunnel](/tunnel/) instances and [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) nodes, instead of granting account-wide access to every Tunnel and Mesh node. This enables least-privilege delegation for private networking operations — for example, letting a support operator stream logs from a single Tunnel without exposing the rest of your account.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
index 7c6fe57320f8f26..24eaa0394bc62b2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
+
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
index 189b65dec009c19..8bfca8fb0871aec 100644
--- a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
@@ -29,9 +29,9 @@ To add a CIDR route:
 3. In **CIDR**, enter the IP address or CIDR range that you wish to route through the tunnel (for example, `10.0.0.1` or `10.0.0.0/24`). This can be a private or public IP.
 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare.
 5. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/virtual-networks/) for this tunnel route. A virtual network is a private routing domain that provides routing isolation within your account. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
-   :::note
-   Virtual networks are only supported for `cloudflared` tunnels.
-   :::
+		:::note
+		Virtual networks are only supported for `cloudflared` tunnels.
+		:::
 6. Select **Create**.
 
 Cloudflare will now route requests to your private network. However, the route does not automatically capture traffic from end users. To enable client-side connectivity, refer to the [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/) or
@@ -61,10 +61,9 @@ Published application routes expose applications to the Internet via a domain th
 
 :::note[Prerequisites]
 Before you publish an application, ensure you have:
-
 - [Created a Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) using `cloudflared`.
 - [Added a website to Cloudflare](/fundamentals/manage-domains/add-site/).
-  :::
+:::
 
 To add a published application route to an existing tunnel:
 
@@ -75,13 +74,13 @@ To add a published application route to an existing tunnel:
 3. Go to the **Published application routes** tab and select **Add a published application route**.
 
 4. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
+	:::note
+	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+	:::
 
 5. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example:
-   - **Type**: _HTTP_
-   - **URL**: `localhost:8000`
+	- **Type**: _HTTP_
+	- **URL**: `localhost:8000`
 
 6. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
@@ -92,3 +91,4 @@ Anyone on the Internet can now access the application at the specified hostname.
 ## Add a WAN route
 
 WAN routes define the IP network segments (such as `10.0.0.0/24`) that are reachable via a GRE or IPsec tunnel. To add a WAN route, refer to the [WAN Connectors documentation](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/).
+
diff --git a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
index 308de57b07e7f48..90e480866276de9 100644
--- a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
@@ -23,14 +23,14 @@ When planning your private network addressing and configuring [Split Tunnel](/cl
 | ------------------------------------------------------------- | ---------------- | ------------ |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `100.64.0.0/12`  | Yes          |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `100.80.0.0/16`  | No           |
-| [Device IPs](#device-ips)                                     | `100.96.0.0/12`  | Yes          |
+| [Device IPs](#device-ips)                           | `100.96.0.0/12`  | Yes          |
 | [Private Load Balancer IPs](#private-load-balancer-ips)       | `100.112.0.0/16` | Yes          |
 
 ## IPv6 ranges
 
 | Name                                                          | Default CIDR               | Configurable |
 | ------------------------------------------------------------- | -------------------------- | ------------ |
-| [Device IPs](#device-ips)                                     | `2606:4700:0cf1:1000::/64` | No           |
+| [Device IPs](#device-ips)                           | `2606:4700:0cf1:1000::/64` | No           |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `2606:4700:0cf1:4000::/64` | No           |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `2606:4700:0cf1:5000::/64` | No           |
 
diff --git a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
index be5f7bea46c3b41..6a8f6c283d0c8b1 100644
--- a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
@@ -17,15 +17,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare One",
-		tunnelConfigURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
index c3ff67b1fdb0308..0749407053febed 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
@@ -24,4 +24,4 @@ Alternatively, to use a keyboard shortcut, press `CTRL + ALT + Z`.
 
 ## Languages
 
-The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
+The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
index 3ad4acc8218df86..c608dbdef4888a2 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
@@ -12,6 +12,7 @@ tags:
 
 import { Render } from "~/components";
 
+
 :::note
 Remote browser isolation is available as an add-on to Zero Trust Pay-as-you-go and Enterprise plans.
 :::
@@ -29,3 +30,4 @@ Cloudflare Browser Isolation is a security product. In order to serve transparen
 ## Troubleshooting
 
 For help resolving common issues with Browser Isolation, refer to [Troubleshoot Browser Isolation](/cloudflare-one/remote-browser-isolation/troubleshooting/).
+
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
index e7f230098916d61..b4040d192dbbf47 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
@@ -83,7 +83,4 @@ You no longer need to isolate both the Identity Provider (IdP) and Service Provi
 
 ## Browser Isolation is not compatible with private apps on non-`443` ports
 
-<Render
-	file="access/self-hosted-app/browser-isolation-non-443"
-	product="cloudflare-one"
-/>
+<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
index 21df1128ff02665..a74778b93fcbd01 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
@@ -34,8 +34,8 @@ Browser Isolation uses WebRTC (a real-time communication protocol) for low-laten
 
 In order to pass WebRTC traffic, the remoting client must be able to connect to the following IP addresses:
 
-| IP range                                                                                                           | Port range    | Protocol |
-| ------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
+| IP range                                                                 | Port range    | Protocol |
+| ------------------------------------------------------------------------ | ------------- | -------- |
 | IPv4: `162.159.201.10 - 162.159.201.255` <br/> IPv4: `172.64.73.0 - 172.64.73.255` <br/> IPv6: `2606:4700:f2::/48` | 10000 - 59999 | UDP      |
 
 Each remote browser instance is randomly assigned a port, and the port that a user is allocated to will change often and without notice.
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
index 9e910279a1fe9a8..c45a25eaf8d13b8 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
@@ -15,13 +15,13 @@ Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudfl
 
 Setup instructions vary depending on how you want to connect your devices to Cloudflare. Refer to the links below to view the setup guide for each deployment option.
 
-| Connection                                                                                                | Mode         | Description                                                                                                                                       |
-| --------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                                          |
-| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                                                  |
-| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).     |
-| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network). |
-| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`.                              |
+| Connection                                                                                                | Mode         | Description                                                                                                          |
+| --------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
+| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                       |
+| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                     |
+| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                           |
+| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network).                                 |
+| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`. |
 
 **In-line** mode means traffic is inspected as it flows through Gateway — users browse to websites using normal URLs, not a special Cloudflare prefix. Some in-line methods require device or network configuration, such as installing the Cloudflare One Client or configuring a PAC file. **Prefixed URL** mode requires users to visit a Cloudflare-hosted URL that wraps the target website.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
index 318f06a6fc92ed4..f0ab810ee252406 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
@@ -79,7 +79,7 @@ You can add a Mailto link to your custom block page, which allows users to direc
 | Source IP    | The public source IP of the user device.                                                                                                                                                                                    |
 | Account ID   | The Cloudflare account associated with the block policy.                                                                                                                                                                    |
 | User ID      | The ID of the user who visited the page. Currently, User IDs are not surfaced in the dashboard and can only be viewed by calling the [API](/api/resources/zero_trust/subresources/access/subresources/users/methods/list/). |
-| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                 |
+| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                           |
 | Block Reason | Your policy-specific block message.                                                                                                                                                                                         |
 
 ## Configure policy block behavior
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
index 96799f2d3e915f6..c7cde6525fc3b70 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
index ccfd4fb9efc2beb..1b02eaa266e0cf7 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
@@ -49,23 +49,24 @@ You can use the following commands to validate if the posture check is working a
 1. Open a PowerShell window.
 2. List all installed antivirus products registered with Windows Security Center:
 
-   ```powershell
-   Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
-   ```
-
-   ```powershell output
-   <redacted>
-   displayName              : Windows Defender
-   instanceGuid             : {00000000-0000-0000-0000-000000000000}
-   pathToSignedProductExe   : windowsdefender://
-   pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
-   productState             : 397568
-   timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
-   PSComputerName           : ENDPOINT-01
-   ```
+	```powershell
+	Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
+	```
+
+	```powershell output
+	<redacted>
+	displayName              : Windows Defender
+	instanceGuid             : {00000000-0000-0000-0000-000000000000}
+	pathToSignedProductExe   : windowsdefender://
+	pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
+	productState             : 397568
+	timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
+	PSComputerName           : ENDPOINT-01
+	```
 
 3. Microsoft does not support decoding the `productState` from the `SecurityCenter2` namespace. To verify that an antivirus product is active, open the [Windows Security app](https://support.microsoft.com/en-us/windows/stay-protected-with-the-windows-security-app-2ae0363d-0ada-c064-8b56-6a39afb6a963). The **Virus & threat protection** panel should say `No action needed` with a green checkmark.
 
-   To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
+	To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
 
 4. If you configured a maximum antivirus signature age in your posture check, compare the `timestamp` in the PowerShell output against the current system time. If the difference exceeds the configured number of days, the posture check will fail.
+
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
index 6e24b6094c78b8c..daec64a910742b5 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
@@ -38,12 +38,12 @@ The Application Check device posture attribute checks that a specific applicatio
    2. **Operating system**: Select your operating system.
    3. **Application path**: Enter the file path for the executable that will be running (for example, `C:\Program Files\myfolder\myfile.exe`).
 
-      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
 
    :::note
    - Be sure to enter the binary file path, not the application launch path. When checking for an application on macOS, a common mistake is to enter `/Applications/ApplicationName.app`. This will not work as `ApplicationName.app` is a folder. The executable file that will be running is located within the folder, for example `ApplicationName.app/Contents/MacOS/ApplicationName`.
    - Some applications change their file path after an update. Ensure that the application is always in a stable location or use environment variables.
-     :::
+	 :::
 
 5. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint of the publishing certificate](#determine-the-signing-thumbprint) used to sign the binary. Adding this information will enable the check to ensure that the application was signed by the expected software developer.
 6. **SHA-256 (optional)**: Enter the [SHA-256 value](#determine-the-sha-256-value) of the binary. This is used to ensure the integrity of the binary file on the device.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
index d0a1f568446a035..bcf50cd88967c96 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
@@ -38,8 +38,7 @@ The File Check device posture attribute checks for the presence of a file on a d
    2. **Operating system**: Select your operating system.
    3. **File Path**: Enter a file path (for example, `c:\my folder\myfile.exe`).
 
-      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
-
+		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
    4. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-signing-thumbprint) of the publishing certificate used to sign the file. Adding this information will enable the check to ensure that the file was signed by the expected software developer.
    5. **SHA-256 (optional)**: Enter the [SHA-256 value](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-sha-256-value) of the file. This is used to ensure the integrity of the file on the device.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
index b580c8ae61cbeb2..1d1d08a80225a0d 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
@@ -36,13 +36,12 @@ The Firewall device posture attribute ensures that a firewall is running on a de
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Configure **Enable firewall check** based on your desired security policy:
-   - **Enabled**: (Recommended) The posture check passes only if the firewall is running.
-   - **Disabled**: The posture check passes only if the firewall is turned off.
-
-   :::note
-   The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
-   :::
+	- **Enabled**: (Recommended) The posture check passes only if the firewall is running.
+	- **Disabled**: The posture check passes only if the firewall is turned off.
 
+	:::note
+	The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
+	:::
 7. Select **Save**.
 
 Next, go to **Insights** > **Logs** > **Posture logs** and verify that the firewall check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
index 00d1b33264aa55e..1ceee1540f5307e 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
@@ -6,32 +6,33 @@ products:
 title: Cloudflare One Client checks
 sidebar:
   order: 1
+
 ---
 
 These device posture checks are performed by the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/). To use this feature, you must [deploy the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) to your devices and enable the desired posture checks.
 
 ## Supported Client modes
 
-- Traffic and DNS mode
-- Traffic only mode
-- Posture only mode
+* Traffic and DNS mode
+* Traffic only mode
+* Posture only mode
 
 ## Supported operating systems
 
-| Device posture check                                                                                       | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| ---------------------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
-| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)                   | ❌    | ✅      | ❌    | ❌  | ❌               |
-| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌    | ❌      | ❌    | ✅  | ✅               |
-| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌    | ✅      | ❌    | ❌  | ❌               |
-| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅    | ✅      | ❌    | ❌  | ❌               |
-| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                | ✅    | ✅      | ✅    | ❌  | ❌               |
+| Device posture check                                                                          | macOS | Windows | Linux       | iOS | Android/ChromeOS |
+| --------------------------------------------------------------------------------------------- | ----- | ------- | ----------- | --- | ---------------- |
+| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
+| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌     | ❌       | ❌           | ✅   | ✅                |
+| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
+| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅     | ✅       | ❌           | ❌   | ❌                |
+| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                          | ✅    | ✅      | ✅    | ❌  | ❌  |
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
index 92e23f910d1ba59..e30d916ac2409c1 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
@@ -36,7 +36,7 @@ The OS Version device posture attribute checks whether the version of a device's
 
 5.  (Optional) Configure additional OS-specific fields:
 
-<Tabs>
+		<Tabs>
 		<TabItem label="Windows">
 		To check that Windows devices have required security patches and features installed, include an Update Build Revision (UBR) number in the OS version check.
 		- **Update Build Revision**: Enter the Windows UBR you want devices to match (for example, `3803`). The UBR is the fourth part of the full Windows version number (for example, in `10.0.19045.3803`, the UBR is `3803`).
@@ -77,7 +77,6 @@ Operating systems display version numbers in different ways. This section covers
 ### Windows
 
 Windows version numbers consist of four parts: `Major.Minor.Build.UBR`. For example, `10.0.19045.3803` where:
-
 - `10.0` is the **Version** (Major.Minor)
 - `19045` is the **Build** number
 - `3803` is the **UBR** (Update Build Revision)
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
index 14c460754260543..fe3b97910a59def 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
@@ -37,7 +37,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru
 ## 1. Enable the WARP check
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Traffic settings**.
-2. Ensure that \*Allow Secure Web Gateway to proxy traffic\*\* is enabled.
+2. Ensure that *Allow Secure Web Gateway to proxy traffic** is enabled.
 3. Go to **Reusable components** > **Posture checks**.
 4. In **Cloudflare One Client checks**, select **Add a check**.
 5. Select **WARP**, then select **Save**.
diff --git a/src/content/docs/cloudflare-one/reusable-components/tags.mdx b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
index 9cf337c0f0573e9..affffb57c1a52f9 100644
--- a/src/content/docs/cloudflare-one/reusable-components/tags.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
@@ -11,3 +11,4 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
+
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
index be1e46ccc11fec2..06e26a64c28ed43 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
@@ -109,8 +109,8 @@ Use when you only want to enforce [Cloudflare One Client device posture checks](
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                          | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                   | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | Full security with all filtering capabilities    | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | DNS filtering without routing device traffic     | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | Traffic routing with existing DNS infrastructure | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
index 7042d96a25bd81b..3ddfb9848c66291 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
@@ -19,7 +19,6 @@ This section covers the most common issues you might encounter as you deploy the
 ## Connectivity and registration
 
 ### Stuck on "Disconnected" or frequent flapping
-
 If the Cloudflare One Client is stuck in the `Disconnected` state or frequently changes between `Connected` and `Disconnected`, this indicates that the client cannot establish a connection to Cloudflare's global network.
 
 In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/), `daemon.log` will typically show one or more of the following errors:
@@ -28,75 +27,61 @@ In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/clou
 - Connectivity checks timing out for `connectivity.cloudflareclient.com`.
 
 **Common causes**:
-
 - **Firewall blocks**: A local or network firewall is blocking the [required IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 - **VPN interference**: A third-party VPN is fighting for control over the routing table or DNS. Refer to the [VPN compatibility guide](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/vpn/).
 - **ISP blocks**: Your country or ISP may be explicitly blocking client traffic.
 
 ### Registration error (Authentication Expired)
-
 When registering the client, you may see `Authentication Expired` or `Registration error. Please try again later`.
 
 **Common causes**:
-
 - **System clock out of sync**: Your computer system clock must be properly synced via NTP. If your clock is off by more than 20 seconds, the authentication token (JWT) will be invalid.
 - **Prompt timeout**: You must complete the registration in your browser and return to the client within one minute of the prompt.
 
 ### (Linux) DNS connectivity check failed
-
 This error often means that `systemd-resolved` is not allowing the client to resolve DNS requests. In `daemon.log`, you will see `DNS connectivity check failed to resolve host="warp-svc."`.
 
 **Solution**:
-
 1. Add `ResolveUnicastSingleLabel=yes` to `/etc/systemd/resolved.conf`.
 2. Ensure no other DNS servers are explicitly configured in that file.
 3. Restart the service: `sudo systemctl restart systemd-resolved.service`.
 
 ### (Mac/Linux) Invalid character in resolv.conf
-
 The client cannot parse `resolv.conf` files containing invalid characters like `!@#$%^&*()<>?` in `search` directives. Remove these characters to restore service.
 
 ## Browser and certificate issues
 
 ### "Your connection is not private" or untrusted warnings
-
 Advanced security features require the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) to be trusted on the device.
 
 - **Chrome/Edge**: These browsers cache certificates. If you installed the certificate while the browser was running, you must restart the browser.
 - **Root certificate expiry**: The default Cloudflare root certificate expired on February 2, 2025. If you are seeing errors, [generate and activate a new certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) in the dashboard.
 
 ### 2025 Certificate migration
-
 Starting with version 2024.12.554.0, the client can automatically install new certificates as soon as they are **Available** in the dashboard. For older versions, certificates had to be marked **In-Use** first. Ensure **Install CA to system certificate store** is enabled in your [Device settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).
 
 ## Windows-specific issues
 
 ### Windows shows "No Internet access"
-
 This is often a cosmetic error with Windows Network Connectivity Status Indicator (NCSI). Apps like Outlook or JumpCloud may refuse to connect because of this status.
 
 **Solution**:
 Configure NCSI to detect the client's local DNS proxy and use active probing by setting these registry keys to `1`:
-
 - `HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS`
 - `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\EnableActiveProbing`
 
 ### Setup Wizard ends prematurely
-
 This usually indicates a missing dependency, such as .NET Framework `4.7.2` or later. Legacy systems (like Windows 10 Enterprise 1607) may require a manual update of the [.NET Framework Runtime](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net472).
 
 ## Other environment issues
 
 ### WSL2 connectivity
-
 If WSL2 loses connectivity, check your [split tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). The IP range used by WSL to communicate with the host may be accidentally included in the tunnel. Exclude the WSL network range to restore connectivity.
 
 ### SMTP port 25 blocked
-
 By default, the client blocks outgoing traffic on port `25` to prevent spam. Use port `587` or `465` for encrypted email, or contact your account team to request an unblock.
 
 ### Admin override codes expired
-
 [Admin override codes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes) are time-sensitive and adhere to fixed-hour blocks. A code generated at 9:30 AM with a 1-hour timeout will expire at 10:00 AM because its validity is counted within the 9:00 AM-10:00 AM window.
 
 ---
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
index 57570302af9994e..41e24ebbe3edf84 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
@@ -16,22 +16,22 @@ The Cloudflare One Client (formerly WARP) GUI displays the following status mess
 
 To print status messages to the console, run the `warp-cli -l status` command before connecting the client.
 
-| Status message                       | Description                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                                              |
-| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                                                        |
-| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                                                     |
-| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                                                       |
-| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                                          |
-| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                                                 |
+| Status message                       | Description                                                                                                                                                                                                                                                                        |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                           |
+| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                              |
+| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                           |
+| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                             |
+| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                              |
+| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                       |
 | Setting up your routing table        | Updates the [system routing table](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#routing-table) based on your [Split Tunnel rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). |
-| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                            |
-| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                                             |
-| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                                          |
-| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                                   |
-| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                                            |
-| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                                                 |
-| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                                      |
-| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                                           |
-| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                                     |
-| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                                              |
+| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                |
+| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                   |
+| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                |
+| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                       |
+| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                  |
+| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                              |
+| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                             |
+| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                 |
+| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                  |
+| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                           |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
index 2bff092a3e7064e..1a48f5bece5c008 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
@@ -59,82 +59,82 @@ You can collect client diagnostic logs remotely from the Zero Trust dashboard by
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                                   |
-| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                            |
-| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                              |
-| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                           |
-| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                        |
-| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                 |
-| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                                   |
-| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                                |
-| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                          |
-| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                         |
-| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                            |
-| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                                    |
-| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                              |
-| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                                     |
-| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                                    |
-| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                            |
-| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                            |
-| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                                 |
-| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                                |
+| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                            |
+| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                     |
+| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                         |
+| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                                                 |
+| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                     |
+| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                      |
+| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                            |
+| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                         |
+| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                   |
+| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                                   |
+| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                                                 |
+| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                             |
+| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                       |
+| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                              |
+| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                             |
+| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                     |
+| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                     |
+| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                          |
+| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                         |
 | `dns-check.txt`                                                                                     | Verifies that the Cloudflare One Client DNS servers are set as system default. For [operating modes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) where DNS filtering is enabled, this file contains the IPs of the local DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                       |
-| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                                  |
-| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                       |
-| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                           |
-| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                                 |
-| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                            |
-| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                           |
-| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                                   |
-| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                               |
-| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                               |
-| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                                  |
-| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                             |
-| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                                   |
-| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                         |
-| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                        |
-| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                        |
-| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                           |
-| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                             |
-| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                              |
-| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
-| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                          |
-| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                            |
-| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                                 |
-| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                                              |
-| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                    |
-| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                                     |
-| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                  |
-| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                                   |
-| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                                   |
-| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                                 |
-| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
-| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                                   |
-| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                                   |
-| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                                     |
-| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                                     |
-| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                              |
-| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                       |
-| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                  |
-| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                        |
-| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                       |
-| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                               |
-| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                          |
-| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                          |
-| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                             |
-| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                                           |
-| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                         |
-| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                                     |
-| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                                      |
-| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                              |
-| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                         |
+| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                |
+| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                           |
+| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                |
+| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                                  |
+| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                          |
+| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                     |
+| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                    |
+| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                            |
+| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                        |
+| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                        |
+| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                           |
+| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                      |
+| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                            |
+| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                  |
+| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                 |
+| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                                  |
+| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                    |
+| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                      |
+| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                       |
+| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
+| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                   |
+| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                     |
+| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                          |
+| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                            |
+| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                             |
+| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                              |
+| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                           |
+| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                            |
+| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                            |
+| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                          |
+| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
+| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                            |
+| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                            |
+| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                              |
+| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                              |
+| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                       |
+| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                |
+| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                            |
+| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                             |
+| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                |
+| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                        |
+| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                               |
+| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                   |
+| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                      |
+| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                               |
+| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                  |
+| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                              |
+| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                               |
+| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                       |
+| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                  |
 | `warp-settings.txt`                                                                                 | [Cloudflare One Client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/) applied to the device.                                                                                                                                                                                                                 |
-| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                                     |
-| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                               |
-| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                               |
-| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                                      |
+| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                              |
+| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                        |
+| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                        |
+| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                               |
 
 #### Multiple versions of the same log
 
@@ -161,14 +161,14 @@ This enables a few more logging features:
 - DNS logs for [service modes with DNS filtering](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/)
 - One-shot connectivity checks (same information as `connectivity.txt`, collected when extra debug logging starts rather than when `warp-diag` runs)
 - One-shot traceroutes to:
-  - DNS resolver IPs
-  - DNS resolver hostname
-  - Device API endpoint IPs
-  - Device API endpoint hostname
-  - Tunnel edge connection IPs
+	- DNS resolver IPs
+	- DNS resolver hostname
+	- Device API endpoint IPs
+	- Device API endpoint hostname
+	- Tunnel edge connection IPs
 - On Windows, if you are an administrator:
-  - [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
-  - [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
+	- [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
+	- [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
 
 If extra debug logging is enabled, the command `warp-cli debug extra reconnect` forces the tunnel connection to restart.
 This can be useful for collecting log information if the tunnel connection fails.
@@ -246,19 +246,19 @@ The following log files are available for iOS, Android, and ChromeOS devices.
 
 #### iOS
 
-| Name                 | Description                                                                                                                                                                                 |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Extension logs**   | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
-| **Application logs** | Logs from the iOS app process, including GUI events, setting changes, and API calls.                                                                                                        |
-| **Qlogs**            | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID.                                                    |
+| Name                                    | Description           |
+| --------------------------------------- | ------------------------------------ |
+| **Extension logs**                          | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                   |
+| **Application logs**                        | Logs from the iOS app process, including GUI events, setting changes, and API calls.                         |
+| **Qlogs**                                  | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID. |
 
 #### Android/ChromeOS
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| Name                      | Description                                                                                                                                                                                 |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `unhandled_exception.log` | Captures errors in the Android application layer that were not caught and could have crashed the app.                                                                                       |
-| `console.log`             | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes.                                                |
-| `native_tunnel.log`       | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
-| `<connection_id>.sqlog`   | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections.                                                                                                                     |
+| Name             | Description                           |
+| ---------------- | ---------------------------------------------------- |
+| `unhandled_exception.log`   | Captures errors in the Android application layer that were not caught and could have crashed the app.                                |
+| `console.log` | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes. |
+| `native_tunnel.log`  | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                        |
+| `<connection_id>.sqlog`    | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
index 80e66ab48ee8d61..e4307d464bc1c09 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
@@ -20,13 +20,13 @@ A single physical device can have [multiple device registrations](/cloudflare-on
 
 ## Key concepts
 
-| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                   |
-| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                         |
-| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                             |
-| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                  |
-| Device registration                                                                  | An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
-| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                       |
+| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                                            |
+| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                                                |
+| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                             |
+| Device registration                                                                  |  An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
+| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                                                                |
 
 ## Review device registration status
 
@@ -102,20 +102,20 @@ If the user or service token can successfully re-authenticate, a new device regi
 
 Registrations can have the following statuses:
 
-| Status      | Description                                                                                                  |
-| ----------- | ------------------------------------------------------------------------------------------------------------ |
-| **Active**  | Registered and able to connect via the Cloudflare One Client. This is the expected operational state.        |
+| Status | Description |
+| --- | --- |
+| **Active** | Registered and able to connect via the Cloudflare One Client. This is the expected operational state. |
 | **Revoked** | The registration's public key is invalidated. Revocation does not release the assigned virtual IP addresses. |
 
 ## Manage device registrations
 
 The following table summarizes the actions available for managing device registrations and devices. For all actions, if the user or service token can still re-authenticate, a new registration will be created automatically. To permanently remove access, refer to [Device management](#device-management).
 
-| Action                                                 | What it does                                                                                             | Virtual IPs released? | When to use                                                                                  |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------- |
-| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                   | You want to fully remove a user's enrollment from a device and free up the virtual IP.       |
-| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                    | You want to temporarily block a device from connecting but preserve the registration record. |
-| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes                   | You want to fully remove a device and all associated registrations.                          |
+| Action                                                 | What it does                                                                                             | Virtual IPs released?                                  | When to use                                                                                                                                                                                  |
+| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                                                    | You want to fully remove a user's enrollment from a device and free up the virtual IP.                                                                                                       |
+| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                                                     | You want to temporarily block a device from connecting but preserve the registration record. |
+| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes | You want to fully remove a device and all associated registrations.                                                                                                                 |
 
 ### Delete a device registration
 
@@ -213,9 +213,8 @@ To block a service token from re-authenticating, you must either:
 
 1. Delete the enrollment policy associated with the token, or modify the enrollment policy to no longer include the token (by removing its specific Include rule).
 2. (Optional) [Delete the service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).
-   <br /> You cannot use this service token to create new registrations.
-   <br /> You cannot delete a service token while it is attached to a device
-   enrollment policy.
+      <br/> You cannot use this service token to create new registrations.
+      <br/> You cannot delete a service token while it is attached to a device enrollment policy.
 3. Delete the service token [device registration](/cloudflare-one/team-and-resources/devices/device-registration/#delete-a-device-registration).
 4. (Optional) To fully decommission a device, [remove user access](/cloudflare-one/team-and-resources/devices/device-registration/#remove-user-access), if any exists. Devices with existing registrations will remain connected to Cloudflare until those specific device registrations are manually deleted.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
index 8e70dfe2c679456..55005c37db7e2b8 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
@@ -26,12 +26,12 @@ Review how this change impacts certificate propagation to your end-user devices
 
 Zero Trust will indicate if a certificate is ready for use in inspection based on its deployment status:
 
-| Deployment status    | Description                                                                                                                                                                |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                             |
-| Pending              | The certificate is being activated or deactivated for use.                                                                                                                 |
+| Deployment status    | Description                                                                                                                                                      |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                   |
+| Pending              | The certificate is being activated or deactivated for use.                                                                                                       |
 | Available            | The certificate is deployed across the Cloudflare global network and ready to be turned on. The Cloudflare One Client will install the certificate on your users' devices. |
-| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                             |
+| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                   |
 
 ## Generate a Cloudflare root certificate
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
index 8d64d7b39cd4c59..08917bf7ed0f8f9 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
@@ -754,115 +754,115 @@ To install a certificate for use in a Docker container:
 4. Add the certificate to your Docker image:
 
    <Tabs> <TabItem label="During build process">
-   
-      To add the certificate to your Dockerfile to install it during the build process:
-      1. Add the certificate install directions to your Dockerfile. For example:
-   
-         ```docker title="Red Hat-based images"
-         FROM registry.access.redhat.com/ubi9/ubi:latest
-         # Or FROM centos:7 or FROM fedora:38
-   
-         # Install necessary certificates package
-         RUN dnf install -y ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
-         RUN update-ca-trust extract
-         ```
-   
-         ```docker title="Debian-based images"
-         FROM debian:12
-         # Or FROM ubuntu:22.04
-   
-         # Install necessary certificates package
-         RUN apt-get update && apt-get install -y ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-         RUN update-ca-certificates
-         ```
-   
-         ```docker title="Alpine-based images"
-         FROM alpine:3.18
-   
-         # Install necessary certificates package
-         RUN apk add --no-cache ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-         RUN update-ca-certificates
-         ```
-   
-      2. Build the Docker image:
-   
-         ```sh
-         docker build -t <your-container-name> .
-         ```
-   
-      3. Verify the certificate was installed:
-   
-         ```sh title="Red Hat-based images"
-         docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-         ```
-   
-         ```sh title="Debian and Alpine-based images"
-         docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
-         ```
-   
-      </TabItem>
-   
-      <TabItem label="During runtime">
-   
-      To add the certificate to your Docker Compose file to install it during runtime:
-      1. Add the certificate install directions to your `docker-compose.yml` file. For example:
-   
-         ```yaml title="Red Hat-based containers"
-         version: '3'
-         services:
-         	redhat-app:
-         		image: registry.access.redhat.com/ubi9/ubi:latest
-          		volumes:
-          			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
-          		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
-         ```
-   
-         ```yaml title="Debian-based containers"
-         version: '3'
-         services:
-         	debian-app:
-         		image: debian:12
-          		volumes:
-          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
-          		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
-         ```
-   
-         ```yaml title="Alpine-based containers"
-         version: '3'
-         services:
-         	alpine-app:
-         		image: alpine:3.18
-          		volumes:
-          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
-          		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
-         ```
-   
-      2. Run the container:
-   
-         ```sh
-         docker-compose up
-         ```
-   
-      3. Verify the certificate was installed:
-   
-         ```sh title="Red Hat-based containers"
-         docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-         ```
-   
-         ```sh title="Debian and Alpine-based containers"
-         docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
-         ```
-   
-      </TabItem> </Tabs>
+
+   To add the certificate to your Dockerfile to install it during the build process:
+   1. Add the certificate install directions to your Dockerfile. For example:
+
+      ```docker title="Red Hat-based images"
+      FROM registry.access.redhat.com/ubi9/ubi:latest
+      # Or FROM centos:7 or FROM fedora:38
+
+      # Install necessary certificates package
+      RUN dnf install -y ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
+      RUN update-ca-trust extract
+      ```
+
+      ```docker title="Debian-based images"
+      FROM debian:12
+      # Or FROM ubuntu:22.04
+
+      # Install necessary certificates package
+      RUN apt-get update && apt-get install -y ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+      RUN update-ca-certificates
+      ```
+
+      ```docker title="Alpine-based images"
+      FROM alpine:3.18
+
+      # Install necessary certificates package
+      RUN apk add --no-cache ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+      RUN update-ca-certificates
+      ```
+
+   2. Build the Docker image:
+
+      ```sh
+      docker build -t <your-container-name> .
+      ```
+
+   3. Verify the certificate was installed:
+
+      ```sh title="Red Hat-based images"
+      docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+      ```
+
+      ```sh title="Debian and Alpine-based images"
+      docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
+      ```
+
+   </TabItem>
+
+   <TabItem label="During runtime">
+
+   To add the certificate to your Docker Compose file to install it during runtime:
+   1. Add the certificate install directions to your `docker-compose.yml` file. For example:
+
+      ```yaml title="Red Hat-based containers"
+      version: '3'
+      services:
+      	redhat-app:
+      		image: registry.access.redhat.com/ubi9/ubi:latest
+       		volumes:
+       			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
+       		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
+      ```
+
+      ```yaml title="Debian-based containers"
+      version: '3'
+      services:
+      	debian-app:
+      		image: debian:12
+       		volumes:
+       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
+       		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
+      ```
+
+      ```yaml title="Alpine-based containers"
+      version: '3'
+      services:
+      	alpine-app:
+      		image: alpine:3.18
+       		volumes:
+       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
+       		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
+      ```
+
+   2. Run the container:
+
+      ```sh
+      docker-compose up
+      ```
+
+   3. Verify the certificate was installed:
+
+      ```sh title="Red Hat-based containers"
+      docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+      ```
+
+      ```sh title="Debian and Alpine-based containers"
+      docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
+      ```
+
+   </TabItem> </Tabs>
 
 ### Command-line tools
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
index 442499bd33c48ff..5ec0ab6973dad12 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
@@ -61,17 +61,16 @@ While the Okta integration is turned on, Cloudflare One will send any user risk
 ## Predefined risk behaviors
 
 By default, all predefined behaviors are disabled. When a behavior is enabled, Cloudflare One will continuously evaluate all users within the organization for the behavior. You can [change the risk level](#change-risk-behavior-risk-levels) for predefined behaviors if the default assignment does not suit your environment.
-| Risk behavior | Requirements | Description | Evaluation timing |
+| Risk behavior                         | Requirements                                                                                                | Description                                                                                                                                                                                                            | Evaluation timing |
 | -------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
-| Impossible travel | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/) | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
-| High number of DLP policies triggered | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/) | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/). | Evaluated per-request in milliseconds. |
-| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
+| Impossible travel                      | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/)                                            | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
+| High number of DLP policies triggered  | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/)                     | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/).                                  | Evaluated per-request in milliseconds. |
+| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user.                                          | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
 | CrowdStrike Low ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 0-50 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information.| Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | CrowdStrike Medium ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 50-79 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | Interaction with Malicious File | [Gateway AV scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/) or [File sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/) | User uploads or downloads a file flagged as malicious by Gateway's AV scanner or file sandboxing. Risk is elevated even if the file is blocked. | Evaluated per-request in milliseconds. |
-| Suspicious Security Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-
+| Suspicious Security Domain Visited  | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
 ## Manage risk behaviors
 
 To toggle risk behaviors, go to **Risk score** > **Risk behaviors**.
@@ -93,9 +92,9 @@ You can change the risk level for a behavior at any time.
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Teams & Resources**.
 2. Go to **Users**.
 3. Select **Risk score** > **Risk behaviors**.
-4. Select the risk behavior you want to modify.
-5. In the drop-down menu, choose your desired risk level.
-6. Select **Save**.
+2. Select the risk behavior you want to modify.
+3. In the drop-down menu, choose your desired risk level.
+4. Select **Save**.
 
 ## Use risk scores in Access policies
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
index 2ce86cab7d6270b..c8ace201fdac273 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
@@ -8,9 +8,10 @@ tags:
   - SCIM
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers to synchronize user identity information with cloud applications and services. After configuring SCIM, user identities that you create, edit, or delete in the identity provider are automatically updated across all supported applications. This makes it easier for IT admins to onboard new users, update their groups and permissions, and revoke access in the event of an employee termination or security breach.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
index 2f4b39bfbcd969d..1cf937a40bfe8b7 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 User logs show a list of all users who have authenticated to Cloudflare One. For each user who has logged in, you can view their enrolled devices, login history, seat usage, and identity used for policy enforcement.
 
@@ -20,7 +20,7 @@ This page lists all users who have registered the Cloudflare One Client or authe
 
 ### Available logs
 
-- **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
-- **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
-- **Devices**: Devices registered to the user via the Cloudflare One Client.
-- **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
+* **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
+* **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
+* **Devices**: Devices registered to the user via the Cloudflare One Client.
+* **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
diff --git a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
index f788aa791bdb0b6..64308a2ccb340c0 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
@@ -38,8 +38,8 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 | Resolve nel.cloudflare.com through 1.1.1.1                                                | `00000001-0034-45a0-8333-f339451fba46` | `nel.cloudflare.com`                                                                                                                                      | resolve |
 | Allow DNS queries for api.cloudflare.com domain                                           | `00000001-5eea-4932-8dd5-8e1ec9770396` | `api.cloudflare.com`                                                                                                                                      | allow   |
 | Resolve api.cloudflare.com through 1.1.1.1                                                | `00000001-4f0c-4f86-9b96-5d26123a194b` | `api.cloudflare.com`                                                                                                                                      | resolve |
-| Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                                 | allow   |
-| Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                                 | resolve |
+| Allow DNS queries for one.dash.cloudflare.com domain                                    | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                               | allow   |
+| Resolve one.dash.cloudflare.com through 1.1.1.1                                         | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                               | resolve |
 | Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-a9fd-40de-a662-51d3a3ae0ad8` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | allow   |
 | Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-70f2-4eea-b711-201bca434ed4` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | resolve |
 | Allow DNS queries for dash.cloudflare.com domain                                          | `00000001-0c2a-4b31-8606-3e5a1d87c1bf` | `dash.cloudflare.com` and `dash.fed.cloudflare.com`                                                                                                       | allow   |
@@ -59,14 +59,14 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 
 ## Network proxy policies
 
-| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                  | Action | Description                                                                                                                                                   |
-| --------------------------------------------------- | -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                 | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
-| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows Zero Trust client.                                                                                                                                     |
-| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                          | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
+| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                    | Action | Description                                                                                                                                                   |
+| --------------------------------------------------- | -------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                   | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
+| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows Zero Trust client.                                                                                                                                     |
+| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                            | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
 | Allow Zero Trust Services                           | `00000001-e1e8-421b-a0fe-895397489f28` | Hostname | `one.dash.cloudflare.com`, `help.teams.cloudflare.com`, `blocked.teams.cloudflare.com`, `blocked.teams.fed.cloudflare.com`, `api.cloudflare.com`, `api.fed.cloudflare.com`, `cloudflarestatus.com`, `www.cloudflarestatus.com`, `one.dash.cloudflare.com`, `one.dash.fed.cloudflare.com`, `help.one.cloudflare.com`, `dash.cloudflare.com`, `dash.fed.cloudflare.com`, and `developers.cloudflare.com` | allow  | Allows Cloudflare Zero Trust services.                                                                                                                        |
-| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
-| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                              | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
+| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
+| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                                | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
 
 ## HTTP inspection policies
 
diff --git a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
index 2df964a6c3a878e..84848c8086de50c 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
@@ -50,15 +50,15 @@ To use HTTP policies to filter all HTTPS traffic on all ports when using a defau
 
 Gateway supports detection and filtering of the following protocols:
 
-| Protocol     | Notes                                                                                        |
-| ------------ | -------------------------------------------------------------------------------------------- |
-| HTTP         | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
-| HTTP2        | Hypertext Transfer Protocol Version 2.                                                       |
-| SSH          | Secure Shell Protocol — remote login and command execution.                                  |
-| TLS          | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
-| DCERPC       | Distributed Computing Environment / Remote Procedure Call.                                   |
-| MQTT         | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
-| TPKT         | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
+| Protocol                                                          | Notes                                                                                        |
+| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| HTTP                                                              | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
+| HTTP2                                                             | Hypertext Transfer Protocol Version 2.                                                       |
+| SSH                                                               | Secure Shell Protocol — remote login and command execution.                                  |
+| TLS                                                               | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
+| DCERPC                                                            | Distributed Computing Environment / Remote Procedure Call.                                   |
+| MQTT                                                              | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
+| TPKT                                                              | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
 | IMAP         | Internet Message Access Protocol — email retrieval.                                          |
 | POP3         | Post Office Protocol v3 — email retrieval.                                                   |
 | SMTP         | Simple Mail Transfer Protocol — email sending.                                               |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
index da83a0d0f8b94ed..61657d39a175ca7 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
@@ -17,7 +17,7 @@ For Magic Transit egress traffic, consider the following:
 - Network Firewall rules apply to both Magic Transit ingress and egress traffic passing through Cloudflare.
 - If you have a "default drop" catchall rule (a final rule that blocks all traffic not matched by earlier rules) for ingress traffic, you must add an earlier rule to permit traffic sourced from your Magic Transit prefix with the destination as **any** to allow outbound egress traffic.
 
-  For example, place the following allow rule before any default-drop catchall rule:
+   For example, place the following allow rule before any default-drop catchall rule:
 
-  **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
-  **Action**: Allow
+   **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
+   **Action**: Allow
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
index 7ad5f83b0ccb97c..353d64288db846e 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
@@ -22,9 +22,9 @@ There are two approaches for setting up tiered policies, depending on your deplo
 ## Organizations vs. Tenant API
 
 | Feature                    | [Cloudflare Organizations](/cloudflare-one/traffic-policies/tiered-policies/organizations/) | [Tenant API](/cloudflare-one/traffic-policies/tiered-policies/tenant-api/) |
-| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                   |
-| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                    |
-| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                |
-| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                   |
-| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                            |
+| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
+| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                         |
+| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                          |
+| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                      |
+| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                         |
+| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                                  |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
index 558bcf16daff10b..61dee092052c3ac 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
@@ -21,6 +21,7 @@ The Tenant API platform only supports [DNS policies](/cloudflare-one/traffic-pol
 
 For more information, refer to the [Cloudflare Zero Trust for managed service providers](https://blog.cloudflare.com/gateway-managed-service-provider/) blog post.
 
+
 ## Get started
 
 To set up the Tenant API, refer to [Get started](/tenant/get-started/). Once you have provisioned and configured your customer's Cloudflare accounts, you can create [DNS policies](/cloudflare-one/traffic-policies/dns-policies/).
diff --git a/src/content/docs/cloudflare-one/troubleshooting/access.mdx b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
index b8ece1182ed0454..b6396e705f97636 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/access.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Access troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/access-controls/troubleshooting/">
-	Full Access troubleshooting guide ❯
+  Full Access troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
index e4cf3238d0cd8bd..c31dd68373abe7a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Browser Isolation documentation.
 
 <LinkButton href="/cloudflare-one/remote-browser-isolation/troubleshooting/">
-	Browser Isolation troubleshooting ❯
+  Browser Isolation troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
index 72cda8b9e748c03..064db32c9b01121 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full CASB documentation.
 
 <LinkButton href="/cloudflare-one/integrations/cloud-and-saas/troubleshooting/">
-	CASB troubleshooting ❯
+  CASB troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
index a15cd8ee067f5b5..304a4016752f5ba 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
@@ -32,15 +32,12 @@ For all issues, please include:
 Depending on the product, providing diagnostic files is critical for a technical investigation.
 
 ### Cloudflare One Client (WARP)
-
 If the issue involves the Cloudflare One Client, run the `warp-diag` command on the affected device and attach the resulting `.zip` file to your case. For more information, refer to [Diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/).
 
 ### Cloudflare Tunnel
-
 If the issue involves Cloudflare Tunnel, run the `cloudflared tunnel diag` command and provide the generated report. For more information, refer to [Tunnel diagnostic logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs/).
 
 ### Access and Gateway
-
 For issues related to authentication loops, blocked websites, or policy enforcement:
 
 - **HAR file**: Provide a [HAR file](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file) captured while reproducing the issue.
@@ -49,7 +46,6 @@ For issues related to authentication loops, blocked websites, or policy enforcem
 - **Request ID**: For Gateway issues, you can find the `request_id` (HTTP logs) or `query_id` (DNS logs) in your [Gateway logs](/cloudflare-one/traffic-policies/troubleshooting/).
 
 ### Digital Experience Monitoring (DEX)
-
 For issues with DEX tests or device monitoring, provide a [remote capture](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/) from the Zero Trust dashboard.
 
 ---
diff --git a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
index 8c96f5ab4305ba3..731999d5fb8036d 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full DEX documentation.
 
 <LinkButton href="/cloudflare-one/insights/dex/troubleshooting/">
-	DEX troubleshooting ❯
+  DEX troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
index 690763e57e48c08..c84e1260e343735 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Email Security documentation.
 
 <LinkButton href="/cloudflare-one/email-security/troubleshooting/">
-	Email Security troubleshooting ❯
+  Email Security troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
index 0d5841ea8bb17d1..e38ab6f5acae44e 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Gateway troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/traffic-policies/troubleshooting/">
-	Full Gateway troubleshooting guide ❯
+  Full Gateway troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
index eb881c4c7e9300a..1d692f0aa4341e2 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
@@ -12,25 +12,18 @@ import { Render, LinkButton } from "~/components";
 
 Explore common issues and solutions for Cloudflare Tunnel.
 
-<Render
-	file="tunnel/common-errors"
-	product="cloudflare-one"
-	params={{
-		logsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-		protocolURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
-		configFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		originServerNameURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		caPoolURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		noTLSVerifyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		ulimitsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/",
-	}}
+<Render 
+  file="tunnel/common-errors" 
+  product="cloudflare-one" 
+  params={{
+    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+    protocolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
+    configFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    originServerNameURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    caPoolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    noTLSVerifyURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    ulimitsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/"
+  }} 
 />
 
 ---
@@ -40,5 +33,5 @@ Explore common issues and solutions for Cloudflare Tunnel.
 For more information, refer to the full Tunnel troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/">
-	Full Tunnel troubleshooting guide ❯
+  Full Tunnel troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
index 4012b24a1e816aa..82128a0306e3847 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
@@ -15,16 +15,11 @@ import { Render, LinkButton } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
 
@@ -35,5 +30,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity/">
-	Full connectivity troubleshooting guide ❯
+  Full connectivity troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
index 7cbca452e33919a..0c2b64583258ccf 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 32
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore resources to help you resolve issues with Cloudflare WAN (formerly Magic WAN) connectivity, routing, and tunnel health.
 
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
index 2787fccd3b01cf7..2499d5ff7d77041 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
@@ -8,20 +8,15 @@ sidebar:
   order: 33
 ---
 
-import { Render, LinkButton } from "~/components";
+import { Render, LinkButton } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
 
@@ -32,5 +27,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/">
-	Full IPsec troubleshooting guide ❯
+  Full IPsec troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
index 732752846b608d7..6766ee8164db987 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
@@ -11,20 +11,16 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
 
 ---
@@ -34,5 +30,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/">
-	Full routing and BGP guide ❯
+  Full routing and BGP guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
index b2a3db82e0e9e8d..4ed284bd72ee49e 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
@@ -11,26 +11,19 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
 
 ---
@@ -40,5 +33,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/">
-	Full tunnel health guide ❯
+  Full tunnel health guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
index a5fe18d5dcf8599..4511789b45bde5c 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare One Client documentation.
 
 <LinkButton href="/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/">
-	Cloudflare One Client troubleshooting ❯
+  Cloudflare One Client troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
index 8758982fe37aa85..fbfa9dc10b86312 100644
--- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
+++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
@@ -91,26 +91,26 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
    - `<CLIENT_ID>`: your Entra ID **Application (client) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-      	"$schema": "./node_modules/wrangler/config-schema.json",
-      	"name": "risky-users",
-      	"compatibility_date": "$today",
-      	"main": "src/index.js",
-      	"workers_dev": false,
-      	"account_id": "<ACCOUNT-ID>",
-      	"vars": {
-      		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
-      		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
-      	},
-      	"triggers": {
-      		"crons": ["* * * * *"],
-      	},
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+   	"$schema": "./node_modules/wrangler/config-schema.json",
+   	"name": "risky-users",
+   	"compatibility_date": "$today",
+   	"main": "src/index.js",
+   	"workers_dev": false,
+   	"account_id": "<ACCOUNT-ID>",
+   	"vars": {
+   		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
+   		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
+   	},
+   	"triggers": {
+   		"crons": ["* * * * *"],
+   	},
+   }
+   ```
+
+   </WranglerConfig>
 
 :::note
 
diff --git a/src/content/docs/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-wan/analytics/index.mdx
index 8730a735f15a9f2..7591d777198e731 100644
--- a/src/content/docs/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/index.mdx
@@ -12,8 +12,7 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
@@ -22,6 +21,6 @@ Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance an
 		traceRoutes: "/cloudflare-wan/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/cloudflare-wan/analytics/query-bandwidth/",
 		graphQlTunnelHealthURL: "/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/",
+		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
index d02a87f11d097c0..c961a9e26011107 100644
--- a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -17,7 +17,6 @@ import { Render } from "~/components";
 	file="mconn/network-options/app-aware-policies/netflow"
 	product="networking-services"
 	params={{
-		breakoutTrafficURL:
-			"/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
+		breakoutTrafficURL: "/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
index 3694ed5590489c3..adb2d9fc1ad3f0a 100644
--- a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
@@ -13,10 +13,9 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Cloudflare WAN",
+		magicWord: "Cloudflare WAN"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
index 34889d808b65f54..84a4a80f0ea9f2d 100644
--- a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
index 7ec650366209348..f62f8a3cac1ad1a 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -6,12 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel bandwidth analytics with GraphQL
 sidebar:
   order: 6
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
index 2c6eea69fb48cbe..8c71bfa0ecc6910 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -6,12 +6,11 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel health check results with GraphQL
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }}
-/>
+	params={{ productName: "Cloudflare WAN" }} />
diff --git a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
index a3c3c203418a701..8a916f198158f40 100644
--- a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
@@ -9,23 +9,21 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare WAN network overview
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions:
-			"Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions: "Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "Cloudflare WAN",
 		networkOverviewPageName: "Network overview",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL:
-			"/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
-	}}
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL: "/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
+		}}
 />
 
 ### Set thresholds for site health
@@ -35,7 +33,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/changelog.mdx b/src/content/docs/cloudflare-wan/changelog.mdx
index dab8b24716303bb..5e8580b361df863 100644
--- a/src/content/docs/cloudflare-wan/changelog.mdx
+++ b/src/content/docs/cloudflare-wan/changelog.mdx
@@ -12,10 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/cloudflare-wan/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="cloudflare-wan"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="cloudflare-wan" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2025-02-14
 
@@ -81,4 +78,4 @@ Customers using Gateway to filter traffic to Magic WAN destinations will now see
 
 **Network segmentation**
 
-You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
+You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index 6e7bcd9b792dfd6..1ae5d831a62d218 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,54 +11,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "hardware",
-		productName: "Cloudflare One Appliance",
-		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "Cloudflare WAN",
-		sfpURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-		wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-		lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-		noConnectorShows:
-			"You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
-		networkSegmentationURL:
-			"/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage:
-			"The Cloudflare One Appliance is shipped to you deactivated",
-		hardSoftConn:
-			"You need to deploy two Appliances in your premises before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-wan/configuration/appliance/network-options/",
-		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-		referenceInformationURL:
-			"/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "hardware",
+	productName: "Cloudflare One Appliance",
+	maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "Cloudflare WAN",
+	sfpURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+	wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+	lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+	noConnectorShows: "You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
+	networkSegmentationURL: "/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "The Cloudflare One Appliance is shipped to you deactivated",
+	hardSoftConn: "You need to deploy two Appliances in your premises before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-wan/configuration/appliance/network-options/",
+  maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+  referenceInformationURL: "/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index b3fa278d08bae29..71ca26721aa0603 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,8 +4,10 @@ description: SFP+ port specifications for the hardware Appliance.
 products:
   - cloudflare-wan
 title: SFP+ port information
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info" product="networking-services" />
+<Render file="mconn/sfp-port-info"
+	product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
index 8f201a38e5455a4..c37e1581eefa1cb 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL:
-			"/cloudflare-wan/configuration/appliance/troubleshooting/",
+		troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
index ffbd3902d481e2e..2de202a6c0d9a45 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,12 +15,9 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl:
-			"/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl: "/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Cloudflare One Virtual Appliance",
-		virtualUrl:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		virtualUrl: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index 75d2c374e500dc1..f2cfc7422c36ccd 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -12,9 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-	}}
-/>
+		hardwareConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+		}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 2b74af67e463be6..d4cbc5987d03273 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
index 967aa8ccb663c13..071ef98749d5405 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/register-hardware-appliance"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)",
+		dashName: "Cloudflare WAN (formerly Magic WAN)"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 5b789f4f9046d5d..b53cd5b9f9965c3 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -12,6 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/remove-connectors"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)",
+		dashName: "Cloudflare WAN (formerly Magic WAN)"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 46c95fb5d790192..9bdf18008a25f54 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,18 +9,15 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "breakout",
-		featureName: "Breakout traffic",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		whatHappensApp:
-			"will now go directly to the Internet and bypass Cloudflare's filtering",
-		dashName: "Cloudflare WAN",
-	}}
-/>
+	magicWord: "breakout",
+	featureName: "Breakout traffic",
+	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
+	dashName: "Cloudflare WAN",
+	}} />
 
 ## Breakout by source
 
@@ -30,11 +27,11 @@ Source-based breakout is configured via the API and Terraform.
 
 ### Match criteria
 
-| Criterion              | Behavior                                                                                                            |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Source LAN interface   | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
-| Source CIDR / IP range | All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
+| Criterion             | Behavior                                                                                          |
+| --------------------- | ------------------------------------------------------------------------------------------------- |
+| Source LAN interface  | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
+| Source CIDR / IP range| All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
 
 The same criteria can be used to mark traffic as **prioritized** instead of broken out. Refer to [Prioritized traffic](/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic/) for details.
 
-Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
+Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index dce54b18e5ae528..709867b882cbf6b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,13 +9,11 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "prioritized",
-		featureName: "Prioritized traffic",
-		whatHappensApp: "is now processed first by Connector",
-		dashName: "Cloudflare WAN",
-	}}
-/>
+	magicWord: "prioritized",
+	featureName: "Prioritized traffic",
+	whatHappensApp: "is now processed first by Connector",
+	dashName: "Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
index cdde5b9bfd22fea..1625f2d8f072527 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
@@ -20,35 +20,35 @@ DHCP options are configured via the API and Terraform.
 
 Each option is defined by three fields:
 
-| Field           | Description                                         | Example               |
-| --------------- | --------------------------------------------------- | --------------------- |
-| `option_number` | The DHCP option code (1–254).                       | `67`                  |
-| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                |
-| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0` |
+| Field           | Description                                         | Example                |
+| --------------- | --------------------------------------------------- | ---------------------- |
+| `option_number` | The DHCP option code (1–254).                       | `67`                   |
+| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                 |
+| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0`  |
 
 ### Value type encoding
 
-| Type      | Format                                                     | Example value         |
-| --------- | ---------------------------------------------------------- | --------------------- |
-| `ip`      | A dotted-quad IPv4 address.                                | `10.20.30.40`         |
-| `integer` | A decimal integer.                                         | `0`                   |
-| `text`    | A UTF-8 string.                                            | `boot/x64/pxelinux.0` |
-| `hex`     | A colon-separated sequence of bytes, used for sub-options. | `01:04:aa:bb:cc`      |
+| Type      | Format                                                      | Example value                 |
+| --------- | ----------------------------------------------------------- | ----------------------------- |
+| `ip`      | A dotted-quad IPv4 address.                                 | `10.20.30.40`                 |
+| `integer` | A decimal integer.                                          | `0`                           |
+| `text`    | A UTF-8 string.                                             | `boot/x64/pxelinux.0`         |
+| `hex`     | A colon-separated sequence of bytes, used for sub-options.  | `01:04:aa:bb:cc`              |
 
 ## Common PXE / iPXE options
 
 The most frequently used options for PXE / iPXE boot are:
 
-| Option | Type           | Purpose                                                                     |
-| ------ | -------------- | --------------------------------------------------------------------------- |
-| 60     | `text`         | Vendor class identifier (typically `PXEClient`).                            |
-| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                               |
-| 67     | `text`         | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).          |
-| 43     | `hex`          | Vendor-specific information; sub-option layout is vendor-defined.           |
-| 175    | `hex`          | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more). |
-| 209    | `text`         | iPXE configuration file URI.                                                |
-| 210    | `text`         | iPXE configuration file path prefix.                                        |
-| 211    | `text`         | iPXE configuration file path.                                               |
+| Option | Type    | Purpose                                                                              |
+| ------ | ------- | ------------------------------------------------------------------------------------ |
+| 60     | `text`  | Vendor class identifier (typically `PXEClient`).                                     |
+| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                                |
+| 67     | `text`  | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).                   |
+| 43     | `hex`   | Vendor-specific information; sub-option layout is vendor-defined.                    |
+| 175    | `hex`   | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more).          |
+| 209    | `text`  | iPXE configuration file URI.                                                         |
+| 210    | `text`  | iPXE configuration file path prefix.                                                 |
+| 211    | `text`  | iPXE configuration file path.                                                        |
 
 For a complete list of standard DHCP option codes, refer to the [IANA BOOTP/DHCP parameters registry](https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml).
 
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 46f826cc1ad4c6b..7a2bc1beac7de02 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,13 +8,11 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-relay"
+<Render file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni:
-			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
+		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
 	}}
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 6577eeb5272f5ce..2d895e9f31c584b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,10 +8,9 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-server"
+<Render file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN",
+		dashName: "Cloudflare WAN"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index f5fed31c4c5855e..5c0bcbed619c268 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,11 +8,9 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
index a9f4fad888935fe..b651bbe1b01b881 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index 2cbcd17985e02d7..3eab8ea9a7bb2bf 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,15 +8,11 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/link-aggregation"
+<Render file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 8f1cbe1ed9a4b20..007bef4f404e26e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,17 +4,14 @@ products:
   - cloudflare-wan
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Cloudflare One Appliance to re-use address spaces locally.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/nat-subnet"
+<Render file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+	hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+  virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 822619f84e0b5cf..32603d94e6a92ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,16 +6,13 @@ title: Network segmentation
 description: Define policies to determine if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/network-segmentation"
+<Render file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index caa93793bc8278e..a7d739e9540ba6a 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,19 +4,15 @@ products:
   - cloudflare-wan
 title: Routed subnets
 description: Learn how to configure routed subnets on a Cloudflare One Appliance, including setting static routes and next-hop addresses for complex LAN setups.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/routed-subnets"
+<Render file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL:
-			"/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+		netSubnetURL: "/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 17809b37e6377e7..0190821520209fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -15,11 +15,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		activateURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL:
-			"/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		activateURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL: "/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index bdbd8aaf1e5dec4..eca36e5f7e8eb4b 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -10,7 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/custom-ike-id-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
index b4d9501da0d4693..5e0399f52cb9889 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,12 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		greIpsecTunnelsURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		connectorURL: "/cloudflare-wan/configuration/appliance/",
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 0432393f1f1c0ca..9a7d3b257246a34 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,11 +13,10 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-	file="routing/configure-cloudflare-source-ips"
-	product="networking-services"
-	params={{
-		unifiedRoutingLink:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/",
-	}}
+  file="routing/configure-cloudflare-source-ips"
+  product="networking-services"
+  params={{
+    unifiedRoutingLink: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
index e5b02b3a5366e73..8335fb6e9cf3559 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -7,9 +7,10 @@ sidebar:
   order: 2
 head: []
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -18,23 +19,17 @@ import { Render } from "~/components";
 		magicWord: "Cloudflare WAN",
 		trafficSteeringPage: "/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		addTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table",
+		routingTableName: "Cloudflare Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 9fb7c93867e3747..41b3800804ce8c9 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -11,36 +11,26 @@ description: Learn how to configure IPsec or GRE tunnels for Cloudflare WAN.
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/cloudflare-wan/reference/anti-replay-protection/",
 		cniLink: "/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthDash: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
+		configureARRURL: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
index 9e7d62f8d1aeab1..4a554e27b3969b6 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
index 38b42c7e4dd0350..ac5910dadeb36ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -16,9 +16,8 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-wan/configuration/index.mdx
index 5ddfb172a16c533..13702b827029038 100644
--- a/src/content/docs/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
index 4a444cbdbff83f9..76af852c660c808 100644
--- a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
@@ -17,7 +17,6 @@ import { Render } from "~/components";
 	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
 	params={{
-		mwanAccount:
-			"Have a Multi-Cloud Networking account. Contact your account team to learn more.",
+		mwanAccount: "Have a Multi-Cloud Networking account. Contact your account team to learn more.",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index ff1a38a9ff1a28e..bb10e2869c1ee67 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -4,19 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Alibaba Cloud VPN Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/alibaba-cloud"
-	product="networking-services"
-	params={{
-		ipSecTunnelsUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/alibaba-cloud"
+  product="networking-services"
+  params={{
+    ipSecTunnelsUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
index 58ce92bd34520fd..f9028eefecd609a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
@@ -4,17 +4,14 @@ description: Connect Amazon AWS Transit Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Amazon AWS Transit Gateway
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aws"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/aws"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index a76d15bdf214c1a..f041179a7d471bc 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -8,16 +8,11 @@ title: Microsoft Azure Virtual WAN
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-virtual-wan"
-	product="networking-services"
-	params={{
-		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-		ipsecTunnelUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		cloudflareDocumentationUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-virtual-wan"
+  product="networking-services"
+  params={{
+  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  cloudflareDocumentationUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index f424bafbae91997..79e3ab4a2c3e78e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -8,16 +8,11 @@ title: Microsoft Azure VPN Gateway
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-vpn-gateway"
-	product="networking-services"
-	params={{
-		ipsecTunnelUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		staticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
+  product="networking-services"
+  params={{
+  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  staticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
index 2cc5b0788919598..be31f60acc7149a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -9,8 +9,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index 8831ea12bbf6ea5..cba0f106bf12657 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -4,11 +4,11 @@ description: Connect Cisco IOS XE to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Cisco IOS XE
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-ios-xe"
-	product="networking-services"
+<Render file="cloudflare-wan/third-party/cisco-ios-xe"
+  product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 4191b38bc630e29..896e02c855659fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -8,22 +8,15 @@ title: Cisco Meraki MX (static routing)
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl:
-			"/cloudflare-wan/reference/anti-replay-protection/",
+		antiReplayProtectionUrl: "/cloudflare-wan/reference/anti-replay-protection/",
 		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		unifiedRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		trafficSteeringUrl: "/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedConfigParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		paloAltoGuideUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+		configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 4ab6dfd8b7b76e9..e28d8ba4847ab6f 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -4,19 +4,15 @@ description: Connect Furukawa Electric FITELnet to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Furukawa Electric FITELnet
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fitelnet"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		typeId_ipv4_addrUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fitelnet"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    typeId_ipv4_addrUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
index cf11763d0a341ab..5a12895743cb66e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -8,19 +8,12 @@ title: Fortinet
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fortinet"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		equalCostMultipathRoutingEcmpUrl:
-			"/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fortinet"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    equalCostMultipathRoutingEcmpUrl: "/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
index 2ae56b6dbe49b81..6f89300b8494e05 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
@@ -4,17 +4,14 @@ description: Connect Google Cloud VPN to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Google Cloud VPN
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/google"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/google"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
index c73eca34c84c602..f6e508d000a5d0d 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
index 85e683e79c81b16..3818804b0252018 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,14 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/juniper"
-	product="networking-services"
-	params={{
-		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/juniper"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
index 1f2ddeaeeefca8f..78849f6cad28825 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -4,17 +4,14 @@ description: Connect Oracle Cloud to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Oracle Cloud
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/oracle"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/oracle"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
index a95d9f3fabecc02..110c15959491f36 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,14 +13,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/palo-alto"
-	product="networking-services"
-	params={{
-		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/palo-alto"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
index 862ad0f4b4e8284..d86dc81c4715843 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -5,19 +5,15 @@ products:
   - cloudflare-wan
 title: pfSense
 reviewed: 2024-06-20
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/pfsense"
-	product="networking-services"
-	params={{
-		configureTwoIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		staticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/pfsense"
+  product="networking-services"
+  params={{
+    configureTwoIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    staticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 536b6c9ff0ab552..26a76c80f25db4e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -4,21 +4,16 @@ pcx_content_type: integration-guide
 description: Connect SonicWall to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sonicwall"
-	product="networking-services"
-	params={{
-		ipsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		creatingYourIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createYourStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sonicwall"
+  product="networking-services"
+  params={{
+    ipsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    creatingYourIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createYourStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index 1d3ab31ab967c03..b6d0e9a1f52a074 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -4,21 +4,16 @@ pcx_content_type: integration-guide
 description: Connect Sophos Firewall to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sophos-firewall"
-	product="networking-services"
-	params={{
-		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		ikeIdUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sophos-firewall"
+  product="networking-services"
+  params={{
+    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    ikeIdUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
index bac9233cb7a5f21..fc4d45f5469a352 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -4,15 +4,13 @@ description: Connect strongSwan to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: strongSwan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/strongswan"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/strongswan"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 5f49238ade5259c..868c273f24c50f6 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -9,9 +9,9 @@ title: Ubiquiti
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-wan/third-party/ubiquiti"
-	product="networking-services"
-	params={{
-		magicWord: "Cloudflare WAN",
-	}}
+  file="cloudflare-wan/third-party/ubiquiti"
+  product="networking-services"
+  params={{
+    magicWord: "Cloudflare WAN",
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
index 03266a7985edc32..fc2441a6857269e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -4,15 +4,13 @@ pcx_content_type: integration-guide
 description: Connect Velocloud to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/velocloud"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/velocloud"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
index cbcaa056c559724..b6b97c01cebaf9d 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -4,18 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Cisco SD-WAN to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/viptela"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/viptela"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
index da8b1fef607c6af..0ccbceefbb7c339 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -8,4 +8,6 @@ title: VyOS
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
+<Render file="cloudflare-wan/third-party/vyos"
+  product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
index 3e0e9e8caca4dee..c117c2a4435efd5 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -8,13 +8,9 @@ title: Yamaha RTX Router
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/yamaha"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/yamaha"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-wan/get-started.mdx
index 50110e083ff7170..b2f98f780c0e192 100644
--- a/src/content/docs/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-wan/get-started.mdx
@@ -17,14 +17,11 @@ import { Render } from "~/components";
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
 		configureConnectorUrl: "/cloudflare-wan/configuration/appliance/",
-		configureMwanManually:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureMwanManually: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		greReferenceURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		ipsecReferenceUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		mtuReferenceURL: "/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
+		wanTransformationUrl: "/cloudflare-wan/wan-transformation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/glossary.mdx b/src/content/docs/cloudflare-wan/glossary.mdx
index 5b50582a0620f31..9707d04db10e16a 100644
--- a/src/content/docs/cloudflare-wan/glossary.mdx
+++ b/src/content/docs/cloudflare-wan/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-wan
 sidebar:
   order: 14
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare WAN (formerly Magic WAN) documentation.
 
diff --git a/src/content/docs/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-wan/index.mdx
index 9a0cea6bca082c4..5eac1897c216694 100644
--- a/src/content/docs/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-wan/index.mdx
@@ -27,9 +27,8 @@ import { Render } from "~/components";
 		connectorUrl: "/cloudflare-wan/configuration/appliance/",
 		thirdPartyUrl: "/cloudflare-wan/configuration/third-party/",
 		zeroTrustUrl: "/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		bgpRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
 		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/",
+		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
index 9d694953eaa9562..de5decbd83487cb 100644
--- a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
@@ -5,9 +5,10 @@ pcx_content_type: reference
 description: Third-party licenses used in Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import text from "./3rdparty.txt?raw";
 import { Markdown } from "~/components";
 
-<Markdown text={text} inline={false} />
+<Markdown text={text} inline={false} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-wan/legal/index.mdx
index 907e5abf6f28688..e2e9dc5f914a078 100644
--- a/src/content/docs/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-wan/legal/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 12
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-wan/network-interconnect.mdx
index 86be9e7f16b6297..2f3024d241fa36f 100644
--- a/src/content/docs/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-wan/network-interconnect.mdx
@@ -13,20 +13,14 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="magic-cni"
-	product="networking-services"
-	params={{ magicWord: "Cloudflare WAN" }}
-/>
+<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-wan/on-ramps.mdx
index 32fdec0f6eabfab..86da6b248ebe042 100644
--- a/src/content/docs/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-wan/on-ramps.mdx
@@ -22,6 +22,6 @@ import { Render } from "~/components";
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/",
+		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
index 9ed3368c2c98be2..a081ee8130d1870 100644
--- a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -4,8 +4,7 @@ products:
   - cloudflare-wan
 title: Anti-replay protection
 head: []
-description:
-  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
index cc92b6c823ab972..fbec0cd8573df1d 100644
--- a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
index dbcdf9a17252a75..a504caad9990939 100644
--- a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
@@ -10,35 +10,29 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/reference/device-compatibility"
-	product="networking-services"
-	params={{
-		supportedConfigurationParametersUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		arubaEdgeconnectUrl:
-			"/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-		ciscoMerakiStaticUrl:
-			"/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-		ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
-		fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
-		fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
-		juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
-		paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
-		sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
-		sophosFirewallUrl:
-			"/cloudflare-wan/configuration/third-party/sophos-firewall/",
-		strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
-		ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
-		velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
-		vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
-		yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
-		alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-		awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
-		azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
-		googleUrl: "/cloudflare-wan/configuration/third-party/google/",
-		oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/",
-	}}
-/>
+<Render file="cloudflare-wan/reference/device-compatibility"
+  product="networking-services"
+  params={{
+    supportedConfigurationParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    arubaEdgeconnectUrl: "/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+    ciscoMerakiStaticUrl: "/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+    ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
+    fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
+    fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
+    juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
+    paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
+    pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
+    sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
+    sophosFirewallUrl: "/cloudflare-wan/configuration/third-party/sophos-firewall/",
+    strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
+    ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
+    velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
+    vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
+    yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
+    alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+    awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
+    azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
+    googleUrl: "/cloudflare-wan/configuration/third-party/google/",
+    oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 6cf088b347f6d36..68d4b4a66826115 100644
--- a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -20,14 +20,12 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		mssURL: "/cloudflare-wan/get-started/#set-maximum-segment-size",
 		productURL: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 0251f5066fd362c..6a4cb0f5b700132 100644
--- a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,12 +8,9 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down",
-	}}
+	params={{ tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down" }}
 />
diff --git a/src/content/docs/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-wan/reference/index.mdx
index 1de78f741d45c97..ae239f4ddfc37af 100644
--- a/src/content/docs/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-wan/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
index 433a4d677c2c8b1..c0e144ba5def202 100644
--- a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN",
-	}}
-/>
+		productName: "Cloudflare WAN"
+		}}
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
index 9d1d78aca887206..5f34c73baea554a 100644
--- a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
@@ -23,8 +23,7 @@ import { Render } from "~/components";
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
index af8dd8496a2775f..98d45cc88d50519 100644
--- a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -17,15 +17,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		addTunnels:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
 		staticRoutes: "/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
index 7a88bf96e8c4a54..cb97c92d8e4803d 100644
--- a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
@@ -15,14 +15,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelConfigURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
 		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-wan/security.mdx
index 8a6e3df9eaad074..20d951ee8b334c0 100644
--- a/src/content/docs/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-wan/security.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="cloudflare-wan/security-filters"
+<Render file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
index 220b98e58c0e0a5..a190ec5d61db5ed 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
 		routingBgpLink: "/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
index 5d7bf235ac3cb37..905787c40bc06f3 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 13
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index dc1236e65423f20..274a58ce5258d51 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -8,16 +8,14 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/",
+		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index a43339acccd25e2..ed25cd90faf8949 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -11,16 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 485d6bb04a1e428..807fee1aad43dc6 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -11,21 +11,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index 095f4976ce553d9..ad22094662587ee 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -13,14 +13,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL:
-			"/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
index 566bc65d5095477..7a6e010f13f8f63 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
@@ -11,14 +11,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-one-connectivity-options"
-	product="networking-services"
-	params={{
-		unifiedRoutingURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		connectorURL: "/cloudflare-wan/configuration/appliance/",
-		cniURL: "/cloudflare-wan/network-interconnect/",
-		onRampsURL: "/cloudflare-wan/on-ramps/",
-	}}
+  file="cloudflare-one-connectivity-options"
+  product="networking-services"
+  params={{
+    unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+    connectorURL: "/cloudflare-wan/configuration/appliance/",
+    cniURL: "/cloudflare-wan/network-interconnect/",
+    onRampsURL: "/cloudflare-wan/on-ramps/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
index 52b072c14394b76..039a590ad02f2f0 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
@@ -8,9 +8,9 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare One integration tutorials
-description:
-  Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
+description: Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
   Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/constellation/platform/index.mdx b/src/content/docs/constellation/platform/index.mdx
index 1b6cdafb1ff1640..8d627d53915bd45 100644
--- a/src/content/docs/constellation/platform/index.mdx
+++ b/src/content/docs/constellation/platform/index.mdx
@@ -7,6 +7,6 @@ products:
   - constellation
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/containers/examples/cron.mdx b/src/content/docs/containers/examples/cron.mdx
index fa89b747782586a..beb5c71d036990a 100644
--- a/src/content/docs/containers/examples/cron.mdx
+++ b/src/content/docs/containers/examples/cron.mdx
@@ -57,37 +57,32 @@ Use a cron expression in your Wrangler config to specify the schedule:
 Then in your Worker, call your Container from the "scheduled" handler:
 
 ```ts
-import { Container, getContainer } from "@cloudflare/containers";
+import { Container, getContainer } from '@cloudflare/containers';
 
 export class CronContainer extends Container {
-	sleepAfter = "10s";
+  sleepAfter = '10s';
 
-	override onStart() {
-		console.log("Starting container");
-	}
+  override onStart() {
+    console.log('Starting container');
+  }
 
-	override onStop() {
-		console.log("Container stopped");
-	}
+  override onStop() {
+    console.log('Container stopped');
+  }
 }
 
 export default {
-	async fetch(): Promise<Response> {
-		return new Response(
-			"This Worker runs a cron job to execute a container on a schedule.",
-		);
-	},
+  async fetch(): Promise<Response> {
+    return new Response("This Worker runs a cron job to execute a container on a schedule.");
+  },
 
-	async scheduled(
-		_controller: any,
-		env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> },
-	) {
-		let container = getContainer(env.CRON_CONTAINER);
-		await container.start({
-			envVars: {
+  async scheduled(_controller: any, env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> }) {
+    let container = getContainer(env.CRON_CONTAINER);
+    await container.start({
+      envVars: {
 				MESSAGE: "Start Time: " + new Date().toISOString(),
-			},
-		});
-	},
+      }
+    })
+  },
 };
 ```
diff --git a/src/content/docs/containers/examples/durable-object-interface.mdx b/src/content/docs/containers/examples/durable-object-interface.mdx
index d54c84506542fc7..f957451fa12358b 100644
--- a/src/content/docs/containers/examples/durable-object-interface.mdx
+++ b/src/content/docs/containers/examples/durable-object-interface.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Various examples calling Containers directly from Durable Objects
 pcx_content_type: example
 title: Using Durable Objects Directly
diff --git a/src/content/docs/containers/examples/index.mdx b/src/content/docs/containers/examples/index.mdx
index 5cf608f97ac0ecc..eb6ca3b44e7d6f7 100644
--- a/src/content/docs/containers/examples/index.mdx
+++ b/src/content/docs/containers/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: false
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/containers/platform-details/placement.mdx b/src/content/docs/containers/platform-details/placement.mdx
index 67d5a76095272fe..bcb40145e1c38a1 100644
--- a/src/content/docs/containers/platform-details/placement.mdx
+++ b/src/content/docs/containers/platform-details/placement.mdx
@@ -34,10 +34,10 @@ Limited capacity regions (ME, OC, AFR) cannot be used exclusively. Include at le
 
 Use the `jurisdiction` constraint to restrict containers to compliance boundaries:
 
-| Jurisdiction | Regions    | Use case          |
-| ------------ | ---------- | ----------------- |
-| `eu`         | EEUR, WEUR | EU data residency |
-| `fedramp`    | ENAM, WNAM | FedRAMP regions   |
+| Jurisdiction | Regions    | Use case           |
+| ------------ | ---------- | ------------------ |
+| `eu`         | EEUR, WEUR | EU data residency  |
+| `fedramp`    | ENAM, WNAM | FedRAMP regions    |
 
 When you specify both `jurisdiction` and `regions`, the regions must be valid for that jurisdiction. For example, specifying `jurisdiction: "eu"` with `regions: ["ENAM"]` is invalid.
 
diff --git a/src/content/docs/containers/pricing.mdx b/src/content/docs/containers/pricing.mdx
index 504db4e7c197e95..a26fc07ae355276 100644
--- a/src/content/docs/containers/pricing.mdx
+++ b/src/content/docs/containers/pricing.mdx
@@ -22,7 +22,7 @@ Containers are billed for every 10ms that they are actively running at the follo
 
 You only pay for what you use — charges start when a request is sent to the container or when it is manually started. Charges stop after the container instance goes to sleep, which can happen automatically after a timeout. This makes it easy to scale to zero, and allows you to get high utilization even with bursty traffic.
 
-Memory and disk usage are based on the _provisioned resources_ for the instance type you select, while CPU usage is based on _active usage_ only.
+Memory and disk usage are based on the *provisioned resources* for the instance type you select, while CPU usage is based on *active usage* only.
 
 #### Instance Types
 
diff --git a/src/content/docs/containers/ssh.mdx b/src/content/docs/containers/ssh.mdx
index bc91bd0cdc3968d..fab40ae97a43594 100644
--- a/src/content/docs/containers/ssh.mdx
+++ b/src/content/docs/containers/ssh.mdx
@@ -58,4 +58,4 @@ wrangler containers ssh <INSTANCE_ID>
 
 ## Process visibility
 
-Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
+Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/local-development.mdx b/src/content/docs/d1/best-practices/local-development.mdx
index a225fec2f2d3b74..f6f28cdf1259255 100644
--- a/src/content/docs/d1/best-practices/local-development.mdx
+++ b/src/content/docs/d1/best-practices/local-development.mdx
@@ -137,6 +137,8 @@ Users of wrangler `2.x` must use the `--persist` flag: previous versions of wran
 
 You can use Miniflare's [support for D1](https://miniflare.dev/storage/d1) to create D1 databases you can use for testing:
 
+
+
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/d1/best-practices/query-d1.mdx b/src/content/docs/d1/best-practices/query-d1.mdx
index 6f4eddbd73c830b..74e5a405162b2c2 100644
--- a/src/content/docs/d1/best-practices/query-d1.mdx
+++ b/src/content/docs/d1/best-practices/query-d1.mdx
@@ -52,16 +52,15 @@ Given the following JSON object (`type:blob`) in a column named `sensor_reading`
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
-
 ```sql
 -- Extract the temperature value
 SELECT json_extract(sensor_reading, '$.measurement.temp_f')-- returns "77.4" as TEXT
@@ -81,24 +80,22 @@ This requires you to:
 
 ```js title="index.js"
 export default {
-	async fetch(request, env) {
-		const { pathname } = new URL(request.url);
-		const companyName1 = `Bs Beverages`;
-		const companyName2 = `Around the Horn`;
-		const stmt = env.DB.prepare(
-			`SELECT * FROM Customers WHERE CompanyName = ?`,
-		);
-
-		if (pathname === `/RUN`) {
-			const returnValue = await stmt.bind(companyName1).run();
-			return Response.json(returnValue);
-		}
-
-		return new Response(
-			`Welcome to the D1 API Playground!
+    async fetch(request, env) {
+        const {pathname} = new URL(request.url);
+        const companyName1 = `Bs Beverages`;
+        const companyName2 = `Around the Horn`;
+        const stmt = env.DB.prepare(`SELECT * FROM Customers WHERE CompanyName = ?`);
+
+        if (pathname === `/RUN`) {
+            const returnValue = await stmt.bind(companyName1).run();
+            return Response.json(returnValue);
+        }
+
+        return new Response(
+            `Welcome to the D1 API Playground!
 						\nChange the URL to test the various methods inside your index.js file.`,
-		);
-	},
+        );
+    },
 };
 ```
 
@@ -117,7 +114,6 @@ You can use Wrangler commands to query a D1 database. Note that Wrangler command
 ```sh
 npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ```
-
 ```sh output
 🌀 Mapping SQL input into an array of statements
 🌀 Executing on local database production-db-backend (<DATABASE_ID>) from .wrangler/state/v3/d1:
@@ -132,4 +128,4 @@ npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ├────────────┼─────────────────────┼───────────────────┤
 │ 13         │ Bs Beverages        │ Random Name       │
 └────────────┴─────────────────────┴───────────────────┘
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/remote-development.mdx b/src/content/docs/d1/best-practices/remote-development.mdx
index 4efe9586181686f..40be666bf1fb1f5 100644
--- a/src/content/docs/d1/best-practices/remote-development.mdx
+++ b/src/content/docs/d1/best-practices/remote-development.mdx
@@ -17,16 +17,17 @@ D1 supports remote development using the [dashboard playground](/workers/playgro
 
 :::note
 
+
 This guide assumes you have previously created a Worker, and a D1 database.
 
 Users new to D1 and/or Cloudflare Workers should read the [D1 tutorial](/d1/get-started/) to install `wrangler` and deploy their first database.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select an existing Worker.
 3. Go to the **Bindings** tab.
 4. Select **Add binding**.
@@ -43,14 +44,14 @@ Use the following Worker script to verify that the Worker has access to the boun
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		const res = await env.DB.prepare("SELECT 1;").run();
-		return new Response(JSON.stringify(res, null, 2));
-	},
+  async fetch(request, env, ctx) {
+    const res = await env.DB.prepare("SELECT 1;").run();
+    return new Response(JSON.stringify(res, null, 2));
+  },
 };
 ```
 
 ## Related resources
 
-- Learn [how to debug D1](/d1/observability/debug-d1/).
-- Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
+* Learn [how to debug D1](/d1/observability/debug-d1/).
+* Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
diff --git a/src/content/docs/d1/best-practices/retry-queries.mdx b/src/content/docs/d1/best-practices/retry-queries.mdx
index 0dafe17addbbd3c..02bc218ed30d67e 100644
--- a/src/content/docs/d1/best-practices/retry-queries.mdx
+++ b/src/content/docs/d1/best-practices/retry-queries.mdx
@@ -27,20 +27,20 @@ You can use libraries abstracting that already like [`@cloudflare/actors`](https
 import { tryWhile } from "@cloudflare/actors";
 
 function queryD1Example(d1: D1Database, sql: string) {
-	return await tryWhile(async () => {
-		return await d1.prepare(sql).run();
-	}, shouldRetry);
+  return await tryWhile(async () => {
+    return await d1.prepare(sql).run();
+  }, shouldRetry);
 }
 
 function shouldRetry(err: unknown, nextAttempt: number) {
-	const errMsg = String(err);
-	const isRetryableError =
-		errMsg.includes("Network connection lost") ||
-		errMsg.includes("storage caused object to be reset") ||
-		errMsg.includes("reset because its code was updated");
-	if (nextAttempt <= 5 && isRetryableError) {
-		return true;
-	}
-	return false;
+  const errMsg = String(err);
+  const isRetryableError =
+    errMsg.includes("Network connection lost") ||
+    errMsg.includes("storage caused object to be reset") ||
+    errMsg.includes("reset because its code was updated");
+  if (nextAttempt <= 5 && isRetryableError) {
+    return true;
+  }
+  return false;
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
index 5ba46a35c327eba..cf575cec298ffee 100644
--- a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
+++ b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
@@ -7,5 +7,5 @@ sidebar:
   order: 11
 products:
   - d1
-  - pages
+  - pages  
 ---
diff --git a/src/content/docs/d1/best-practices/use-indexes.mdx b/src/content/docs/d1/best-practices/use-indexes.mdx
index b363212f5718cc1..dc25d04079a3170 100644
--- a/src/content/docs/d1/best-practices/use-indexes.mdx
+++ b/src/content/docs/d1/best-practices/use-indexes.mdx
@@ -16,9 +16,9 @@ Indexes enable D1 to improve query performance over the indexed columns for comm
 
 Indexes are useful:
 
-- When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
-- For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
-- In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
+* When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
+* For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
+* In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
 
 Indexes are automatically updated when the table and column(s) they reference are inserted, updated or deleted. You do not need to manually update an index after you write to the table it references.
 
@@ -114,7 +114,7 @@ Using an index can reduce the number of rows read by a query. Use the `meta` obj
 
 ## Multi-column indexes
 
-For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either _all_ of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
+For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either *all* of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
 
 Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions(customer_id, transaction_date)`, the following table shows when the index is used (or not):
 
@@ -126,16 +126,16 @@ Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions
 
 Notes:
 
-- If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
-- With the same index, a query that uses only `transaction_date` and `shipping_status` would _not_ use the index, as you have not used `customer_id` (the leftmost column) in the query.
+* If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
+* With the same index, a query that uses only `transaction_date` and `shipping_status` would *not* use the index, as you have not used `customer_id` (the leftmost column) in the query.
 
 ## Partial indexes
 
 Partial indexes are indexes over a subset of rows in a table. Partial indexes are defined by the use of a `WHERE` clause when creating the index. A partial index can be useful to omit certain rows, such as those where values are `NULL` or where rows with a specific value are present across queries.
 
-- A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
-- This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
-- Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
+* A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
+* This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
+* Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
 
 A partial index that filters out completed orders from the index would resemble the following:
 
@@ -153,7 +153,7 @@ Use `DROP INDEX` to remove an index. Dropped indexes cannot be restored.
 
 Take note of the following considerations when creating indexes:
 
-- Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
-- You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
-- Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
-- Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
+* Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
+* You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
+* Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
+* Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
diff --git a/src/content/docs/d1/configuration/environments.mdx b/src/content/docs/d1/configuration/environments.mdx
index 9211ae269c77fa0..d006e54c8c8878d 100644
--- a/src/content/docs/d1/configuration/environments.mdx
+++ b/src/content/docs/d1/configuration/environments.mdx
@@ -78,20 +78,22 @@ Therefore, the above binding is equivalent to:
 
 ```json
 {
-	"production": {
-		"d1_databases": [
-			{
-				"binding": "DB",
-				"database_name": "DATABASE_NAME",
-				"database_id": "DATABASE_ID"
-			}
-		]
-	}
+  "production": {
+    "d1_databases": [
+      {
+        "binding": "DB",
+        "database_name": "DATABASE_NAME",
+        "database_id": "DATABASE_ID"
+      }
+    ]
+  }
 }
 ```
 
 ### Example
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -125,25 +127,25 @@ The above is equivalent to the following structure in JSON:
 
 ```json
 {
-	"env": {
-		"production": {
-			"d1_databases": [
-				{
-					"binding": "BINDING_NAME_2",
-					"database_id": "UUID_2",
-					"database_name": "DATABASE_NAME_2"
-				}
-			]
-		},
-		"staging": {
-			"d1_databases": [
-				{
-					"binding": "BINDING_NAME_1",
-					"database_id": "UUID_1",
-					"database_name": "DATABASE_NAME_1"
-				}
-			]
-		}
-	}
+  "env": {
+    "production": {
+      "d1_databases": [
+        {
+          "binding": "BINDING_NAME_2",
+          "database_id": "UUID_2",
+          "database_name": "DATABASE_NAME_2"
+        }
+      ]
+    },
+    "staging": {
+      "d1_databases": [
+        {
+          "binding": "BINDING_NAME_1",
+          "database_id": "UUID_1",
+          "database_name": "DATABASE_NAME_1"
+        }
+      ]
+    }
+  }
 }
 ```
diff --git a/src/content/docs/d1/get-started.mdx b/src/content/docs/d1/get-started.mdx
index 5d22a0fe3363f7c..c5ee956264ad848 100644
--- a/src/content/docs/d1/get-started.mdx
+++ b/src/content/docs/d1/get-started.mdx
@@ -9,17 +9,7 @@ products:
   - d1
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	FileTree,
-	Tabs,
-	TabItem,
-	TypeScriptExample,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, PackageManagers, Steps, FileTree, Tabs, TabItem, TypeScriptExample, WranglerConfig, DashButton } from "~/components";
 
 This guide instructs you through:
 
diff --git a/src/content/docs/d1/observability/billing.mdx b/src/content/docs/d1/observability/billing.mdx
index 1a4a8d3fffc9712..31ef2103ba9196a 100644
--- a/src/content/docs/d1/observability/billing.mdx
+++ b/src/content/docs/d1/observability/billing.mdx
@@ -21,7 +21,6 @@ Total account billable usage analytics for D1 are available in the Cloudflare da
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
    <DashButton url="/?to=/:account/billing" />
-
 2. Go to **Billable Usage**.
 
 From here you can view charts of your account's D1 usage on a daily or month-to-date timeframe.
@@ -33,6 +32,5 @@ Note that billable usage history is stored for a maximum of 30 days.
 Usage-based billing notifications are available within the [Cloudflare dashboard](https://dash.cloudflare.com) for users looking to monitor their total account usage.
 
 Notifications on the following metrics are available:
-
 - Rows Read
-- Rows Written
+- Rows Written
\ No newline at end of file
diff --git a/src/content/docs/d1/platform/limits.mdx b/src/content/docs/d1/platform/limits.mdx
index 21cb95db52dfab3..4c61da8679fd68e 100644
--- a/src/content/docs/d1/platform/limits.mdx
+++ b/src/content/docs/d1/platform/limits.mdx
@@ -10,24 +10,24 @@ products:
 
 import { Render } from "~/components";
 
-| Feature                                                                                         | Limit                                             |
-| ----------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| Databases per account                                                                           | 50,000 (Workers Paid) [^1] / 10 (Free)            |
-| Maximum database size                                                                           | 10 GB (Workers Paid) / 500 MB (Free)              |
-| Maximum storage per account                                                                     | 1 TB (Workers Paid) [^2] / 5 GB (Free)            |
-| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                     | 30 days (Workers Paid) / 7 days (Free)            |
-| Maximum Time Travel restore operations                                                          | 10 restores per 10 minutes (per database)         |
+| Feature                                                                                                             | Limit                                             |
+| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| Databases per account                                                                                               | 50,000 (Workers Paid) [^1] / 10 (Free)            |
+| Maximum database size                                                                                               | 10 GB (Workers Paid) / 500 MB (Free)              |
+| Maximum storage per account                                                                                         | 1 TB (Workers Paid) [^2] / 5 GB (Free)             |
+| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                                         | 30 days (Workers Paid) / 7 days (Free)            |
+| Maximum Time Travel restore operations                                                                              | 10 restores per 10 minutes (per database)          |
 | Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#subrequests)) | 1000 (Workers Paid) / 50 (Free)                   |
-| Maximum number of columns per table                                                             | 100                                               |
-| Maximum number of rows per table                                                                | Unlimited (excluding per-database storage limits) |
-| Maximum string, `BLOB` or table row size                                                        | 2,000,000 bytes (2 MB)                            |
-| Maximum SQL statement length                                                                    | 100,000 bytes (100 KB)                            |
-| Maximum bound parameters per query                                                              | 100                                               |
-| Maximum arguments per SQL function                                                              | 32                                                |
-| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                        | 50 bytes                                          |
-| Maximum bindings per Workers script                                                             | Approximately 5,000 [^3]                          |
-| Maximum SQL query duration                                                                      | 30 seconds [^4]                                   |
-| Maximum file import (`d1 execute`) size                                                         | 5 GB [^5]                                         |
+| Maximum number of columns per table                                                                                 | 100                                               |
+| Maximum number of rows per table                                                                                    | Unlimited (excluding per-database storage limits) |
+| Maximum string, `BLOB` or table row size                                                                            | 2,000,000 bytes (2 MB)                            |
+| Maximum SQL statement length                                                                                        | 100,000 bytes (100 KB)                            |
+| Maximum bound parameters per query                                                                                  | 100                                               |
+| Maximum arguments per SQL function                                                                                  | 32                                                |
+| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                                            | 50 bytes                                          |
+| Maximum bindings per Workers script                                                                                 | Approximately 5,000 [^3]                          |
+| Maximum SQL query duration                                                                                          | 30 seconds [^4]                                   |
+| Maximum file import (`d1 execute`) size                                                                             | 5 GB [^5]                                         |
 
 :::note[Batch limits]
 Limits for individual queries (listed above) apply to each individual statement contained within a batch statement. For example, the maximum SQL statement length of 100 KB applies to each statement inside a `db.batch()`.
diff --git a/src/content/docs/d1/reference/community-projects.mdx b/src/content/docs/d1/reference/community-projects.mdx
index 2974e7452d65edb..a095bb554ffe1f5 100644
--- a/src/content/docs/d1/reference/community-projects.mdx
+++ b/src/content/docs/d1/reference/community-projects.mdx
@@ -12,8 +12,10 @@ Members of the Cloudflare developer community and broader developer ecosystem ha
 
 :::note
 
+
 Community projects are not maintained by the Cloudflare D1 team. They are managed and updated by the project authors.
 
+
 :::
 
 ## Projects
@@ -35,57 +37,57 @@ knex-cloudflare-d1 is the Cloudflare D1 dialect for Knex.js. Note that this is n
 
 [Prisma ORM](https://www.prisma.io/orm) is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to its intuitive data model, automated migrations, type-safety and auto-completion.
 
-- [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
-- [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
+* [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
+* [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
 
 ### D1 adapter for Kysely ORM
 
 Kysely is a type-safe and autocompletion-friendly typescript SQL query builder. With this adapter you can interact with D1 with the familiar Kysely interface.
 
-- [Kysely GitHub](https://github.com/koskimas/kysely)
-- [D1 adapter](https://github.com/aidenwallis/kysely-d1)
+* [Kysely GitHub](https://github.com/koskimas/kysely)
+* [D1 adapter](https://github.com/aidenwallis/kysely-d1)
 
 ### feathers-kysely
 
 The `feathers-kysely` database adapter follows the FeathersJS Query Syntax standard and works with any framework. It is built on the D1 adapter for Kysely and supports passing queries directly from client applications. Since the FeathersJS query syntax is a subset of MongoDB's syntax, this is a great tool for MongoDB users to use Cloudflare D1 without previous SQL experience.
 
-- [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
-- [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
+* [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
+* [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
 
 ### Drizzle ORM
 
 Drizzle is a headless TypeScript ORM with a head which runs on Node, Bun and Deno. Drizzle ORM lives on the Edge and it is a JavaScript ORM too. It comes with a drizzle-kit CLI companion for automatic SQL migrations generation. Drizzle automatically generates your D1 schema based on types you define in TypeScript, and exposes an API that allows you to query your database directly.
 
-- [Docs](https://orm.drizzle.team/docs)
-- [GitHub](https://github.com/drizzle-team/drizzle-orm)
-- [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
+* [Docs](https://orm.drizzle.team/docs)
+* [GitHub](https://github.com/drizzle-team/drizzle-orm)
+* [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
 
 ### workers-qb
 
 `workers-qb` is a zero-dependency query builder that provides a simple standardized interface while keeping the benefits and speed of using raw queries over a traditional ORM. While not intended to provide ORM-like functionality, `workers-qb` makes it easier to interact with your database from code for direct SQL access.
 
-- [GitHub](https://github.com/G4brym/workers-qb)
-- [Documentation](https://workers-qb.massadas.com/)
+* [GitHub](https://github.com/G4brym/workers-qb)
+* [Documentation](https://workers-qb.massadas.com/)
 
 ### d1-console
 
 Instead of running the `wrangler d1 execute` command in your terminal every time you want to interact with your database, you can interact with D1 from within the `d1-console`. Created by a Discord Community Champion, this gives the benefit of executing multi-line queries, obtaining command history, and viewing a cleanly formatted table output.
 
-- [GitHub](https://github.com/isaac-mcfadyen/d1-console)
+* [GitHub](https://github.com/isaac-mcfadyen/d1-console)
 
 ### L1
 
 `L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
 
-- [GitHub](https://github.com/renoki-co/l1)
-- [Packagist](https://packagist.org/packages/renoki-co/l1)
+* [GitHub](https://github.com/renoki-co/l1)
+* [Packagist](https://packagist.org/packages/renoki-co/l1)
 
 ### Staff Directory - a D1-based demo
 
 Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/honox), and [Cloudflare Pages](/pages/). It uses D1 to store employee data, and is an example of a full-stack application built on top of D1.
 
-- [GitHub](https://github.com/lauragift21/staff-directory)
-- [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
+* [GitHub](https://github.com/lauragift21/staff-directory)
+* [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
 
 ### NuxtHub
 
@@ -93,9 +95,9 @@ Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/ho
 
 `NuxtHub` also provides a way to use your remote D1 database in development using the `npx nuxt dev --remote` command.
 
-- [GitHub](https://github.com/nuxt-hub/core)
-- [Documentation](https://hub.nuxt.com)
-- [Example](https://github.com/Atinux/nuxt-todos-edge)
+* [GitHub](https://github.com/nuxt-hub/core)
+* [Documentation](https://hub.nuxt.com)
+* [Example](https://github.com/Atinux/nuxt-todos-edge)
 
 ## Feedback
 
diff --git a/src/content/docs/d1/reference/data-security.mdx b/src/content/docs/d1/reference/data-security.mdx
index ab79357a7114750..810de22ec7f45ea 100644
--- a/src/content/docs/d1/reference/data-security.mdx
+++ b/src/content/docs/d1/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of D1, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/d1/reference/faq.mdx b/src/content/docs/d1/reference/faq.mdx
index e86017db8b829fa..112c665dd4004ad 100644
--- a/src/content/docs/d1/reference/faq.mdx
+++ b/src/content/docs/d1/reference/faq.mdx
@@ -12,8 +12,8 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="faq-pricing" product="d1" />
+<Render file="faq-pricing" product="d1"/>
 
 ## Limits
 
-<Render file="faq-limits" product="d1" />
+<Render file="faq-limits" product="d1"/>
\ No newline at end of file
diff --git a/src/content/docs/d1/reference/generated-columns.mdx b/src/content/docs/d1/reference/generated-columns.mdx
index ccadcdb1b12d227..5d116b3321076a7 100644
--- a/src/content/docs/d1/reference/generated-columns.mdx
+++ b/src/content/docs/d1/reference/generated-columns.mdx
@@ -18,8 +18,8 @@ Generated columns can also have [indexes defined](/d1/best-practices/use-indexes
 
 There are two types of generated columns:
 
-- `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
-- `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
+* `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
+* `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
 
 When omitted from a generated column expression, generated columns default to the `VIRTUAL` type. The `STORED` type is recommended when the generated column is compute intensive. For example, when parsing large JSON structures.
 
@@ -40,13 +40,13 @@ As a concrete example, to automatically extract the `location` value from the fo
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
 
@@ -100,6 +100,6 @@ ADD COLUMN expires_at AS (date(timestamp, '+30 days'));
 
 ## Additional considerations
 
-- Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
-- Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
-- Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
+* Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
+* Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
+* Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
diff --git a/src/content/docs/d1/reference/glossary.mdx b/src/content/docs/d1/reference/glossary.mdx
index 87e1a98504fae41..5fe0afff9a376e2 100644
--- a/src/content/docs/d1/reference/glossary.mdx
+++ b/src/content/docs/d1/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - d1
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's D1 documentation.
 
diff --git a/src/content/docs/d1/reference/migrations.mdx b/src/content/docs/d1/reference/migrations.mdx
index 20dc9869915cbc2..50d3292c20ea584 100644
--- a/src/content/docs/d1/reference/migrations.mdx
+++ b/src/content/docs/d1/reference/migrations.mdx
@@ -16,9 +16,9 @@ Database migrations are a way of versioning your database. Each migration is sto
 
 Currently, the migrations system aims to be simple yet effective. With the current implementation, you can:
 
-- [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
-- [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
-- [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
+* [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
+* [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
+* [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
 
 Every migration file in the `migrations` folder has a specified version number in the filename. Files are listed in sequential order. Every migration file is an SQL file where you can specify queries to be run.
 
diff --git a/src/content/docs/d1/sql-api/foreign-keys.mdx b/src/content/docs/d1/sql-api/foreign-keys.mdx
index fdc9e715186ae46..1c38b8d8d995ec3 100644
--- a/src/content/docs/d1/sql-api/foreign-keys.mdx
+++ b/src/content/docs/d1/sql-api/foreign-keys.mdx
@@ -47,13 +47,13 @@ A foreign key relationship can be defined when creating a table via `CREATE TABL
 
 To illustrate this with an example based on an e-commerce website with two tables:
 
-- A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
-- An `orders` table that maps an order back to a `user_id` in the user table.
+* A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
+* An `orders` table that maps an order back to a `user_id` in the user table.
 
 This mapping is defined as `FOREIGN KEY`, which ensures that:
 
-- You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
-- `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
+* You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
+* `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
 
 ```sql
 CREATE TABLE users (
@@ -77,22 +77,22 @@ You can define multiple foreign key relationships per-table, and foreign key def
 
 ## Foreign key actions
 
-You can define _actions_ as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining _actions_ makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
+You can define *actions* as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining *actions* makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
 
 There are five actions you can set when defining the `ON UPDATE` and/or `ON DELETE` clauses as part of a foreign key relationship. You can also define different actions for `ON UPDATE` and `ON DELETE` depending on your requirements.
 
-- `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
-- `RESTRICT` - A parent key cannot be updated or deleted when _any_ child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
-- `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
-- `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
-- `NO ACTION` - Take no action.
+* `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
+* `RESTRICT` - A parent key cannot be updated or deleted when *any* child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
+* `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
+* `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
+* `NO ACTION` - Take no action.
 
 :::caution[CASCADE usage]
 
 Although `CASCADE` can be the desired behavior in some cases, deleting child rows across tables can have undesirable effects and/or result in unintended side effects for your users.
 :::
 
-In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that _other_ users can no longer look up or refer to scores that were still valid.
+In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that *other* users can no longer look up or refer to scores that were still valid.
 
 ```sql
 CREATE TABLE users (
@@ -111,6 +111,6 @@ CREATE TABLE scores (
 
 ## Next Steps
 
-- Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
-- Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
-- Understand how [database migrations work](/d1/reference/migrations/) with D1.
+* Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
+* Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
+* Understand how [database migrations work](/d1/reference/migrations/) with D1.
diff --git a/src/content/docs/d1/sql-api/query-json.mdx b/src/content/docs/d1/sql-api/query-json.mdx
index 82c65b749bd3e7f..9b44068ab62c958 100644
--- a/src/content/docs/d1/sql-api/query-json.mdx
+++ b/src/content/docs/d1/sql-api/query-json.mdx
@@ -12,10 +12,10 @@ products:
 
 D1 has built-in support for querying and parsing JSON data stored within a database. This enables you to:
 
-- [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
-- Insert and/or replace values within an object or array.
-- [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
-- Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
+* [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
+* Insert and/or replace values within an object or array.
+* [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
+* Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
 
 One of the biggest benefits to parsing JSON within D1 directly is that it can directly reduce the number of round-trips (queries) to your database. It reduces the cases where you have to read a JSON object into your application (1), parse it, and then write it back (2).
 
@@ -25,18 +25,18 @@ This allows you to more precisely query over data and reduce the result set your
 
 JSON data is stored as a `TEXT` column in D1. JSON types follow the same [type conversion rules](/d1/worker-api/#type-conversion) as D1 in general, including:
 
-- A JSON null is treated as a D1 `NULL`.
-- A JSON number is treated as an `INTEGER` or `REAL`.
-- Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
-- Object and array values as `TEXT`.
+* A JSON null is treated as a D1 `NULL`.
+* A JSON number is treated as an `INTEGER` or `REAL`.
+* Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
+* Object and array values as `TEXT`.
 
 ## Supported functions
 
 The following table outlines the JSON functions built into D1 and example usage.
 
-- The `json` argument placeholder can be a JSON object, array, string, number or a null value.
-- The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
-- The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
+* The `json` argument placeholder can be a JSON object, array, string, number or a null value.
+* The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
+* The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
 
 | Function                                                    | Description                                                                                                                                                    | Example                                                                                   |
 | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
@@ -53,7 +53,7 @@ The following table outlines the JSON functions built into D1 and example usage.
 | `json_replace(json, path, value)`                           | Insert a value at the given path. Overwrites an existing value, but does not create a new key if it doesn't exist.                                             |                                                                                           |
 | `json_set(json, path, value)`                               | Insert a value at the given path. Overwrites an existing value.                                                                                                |                                                                                           |
 | `json_type(json)` - `json_type(json, path)`                 | Return the type of the provided value or value at the specified path. Returns one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`. | `json_type('{"temperatures":[73.6, 77.8, 80.2]}', '$.temperatures')` returns `array`      |
-| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                   |
+| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                  |
 | `json_quote(value)`                                         | Converts the provided SQL value into its JSON representation.                                                                                                  | `json_quote('[1, 2, 3]')` returns `[1,2,3]`                                               |
 | `json_group_array(value)`                                   | Returns the provided value(s) as a JSON array.                                                                                                                 |                                                                                           |
 | `json_each(value)` - `json_each(value, path)`               | Returns each element within the object as an individual row. It will only traverse the top-level object.                                                       |                                                                                           |
@@ -102,9 +102,9 @@ Refer to [Generated columns](/d1/reference/generated-columns/) to learn more abo
 
 There are three ways to extract a value from a JSON object in D1:
 
-- The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
-- The `->` operator, which returns a JSON representation of the value.
-- The `->>` operator, which returns an SQL representation of the value.
+* The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
+* The `->` operator, which returns a JSON representation of the value.
+* The `->>` operator, which returns an SQL representation of the value.
 
 The `->` and `->>` operators functions both operate similarly to the same operators in PostgreSQL and MySQL/MariaDB.
 
@@ -112,13 +112,13 @@ Given the following JSON object in a column named `sensor_reading`, you can extr
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
 
@@ -148,12 +148,8 @@ For example, given the following JSON object stored in a column called `login_hi
 
 ```json
 {
-	"user_id": "abc12345",
-	"previous_logins": [
-		"2023-03-31T21:07:14-05:00",
-		"2023-03-28T08:21:02-05:00",
-		"2023-03-28T05:52:11-05:00"
-	]
+    "user_id": "abc12345",
+    "previous_logins": ["2023-03-31T21:07:14-05:00", "2023-03-28T08:21:02-05:00", "2023-03-28T05:52:11-05:00"]
 }
 ```
 
@@ -168,13 +164,7 @@ You can also use `json_array_length` as a predicate in a more complex query - fo
 You can insert a value into an existing JSON object or array using `json_insert()`. For example, if you have a `TEXT` column called `login_history` in a `users` table containing the following object:
 
 ```json
-{
-	"history": [
-		"2023-05-13T15:13:02+00:00",
-		"2023-05-14T07:11:22+00:00",
-		"2023-05-15T15:03:51+00:00"
-	]
-}
+{"history": ["2023-05-13T15:13:02+00:00", "2023-05-14T07:11:22+00:00", "2023-05-15T15:03:51+00:00"]}
 ```
 
 To add a new timestamp to the `history` array within our `login_history` column, write a query resembling the following:
@@ -207,11 +197,11 @@ This would extract only the `value` column from the table returned by `json_each
 
 `json_each` effectively returns a table with multiple columns, with the most relevant being:
 
-- `key` - the key (or index).
-- `value` - the literal value of each element parsed by `json_each`.
-- `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
-- `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
-- `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
+* `key` - the key (or index).
+* `value` - the literal value of each element parsed by `json_each`.
+* `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
+* `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
+* `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
 
 In this example, `SELECT * FROM json_each('[183183, 13913, 94944]')` would return a table resembling the below:
 
@@ -225,12 +215,12 @@ key|value|type|id|fullkey|path
 You can use `json_each` with [D1 Workers Binding API](/d1/worker-api/) in a Worker by creating a statement and using `JSON.stringify` to pass an array as a [bound parameter](/d1/worker-api/d1-database/#guidance):
 
 ```ts
-const stmt = context.env.DB.prepare(
-	"UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))",
-);
-const resp = await stmt
-	.bind("2023-05-16T11:24:08+00:00", JSON.stringify([183183, 13913, 94944]))
-	.run();
+const stmt = context.env.DB
+    .prepare("UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))")
+const resp = await stmt.bind(
+    "2023-05-16T11:24:08+00:00",
+    JSON.stringify([183183, 13913, 94944])
+    ).run()
 ```
 
 This would only update rows in your `users` table where the `id` matches one of the three provided.
diff --git a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
index 2a203c8cb9975a9..986d25d5413005e 100644
--- a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
+++ b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
@@ -12,13 +12,7 @@ description: >-
   This tutorial shows how to create an API that allows you to securely run queries against a D1 database. The API can be used to customize access controls and/or limit what tables can be queried.
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	Details,
-	WranglerConfig,
-} from "~/components";
+import { Render, PackageManagers, Steps, Details, WranglerConfig } from "~/components";
 
 In this tutorial, you will learn how to create an API that allows you to securely run queries against a D1 database.
 
diff --git a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
index 64bb7a1593def46..3ae7982d8bf2cca 100644
--- a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
+++ b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
@@ -230,7 +230,7 @@ npx prisma migrate diff --from-empty --to-schema-datamodel ./prisma/schema.prism
 
 </TabItem>
 </Tabs>
-
+ 
 This stores a SQL statement to create a new `User` table in your migration file from before, here is what it looks like:
 
 <GitHubCode
diff --git a/src/content/docs/data-localization/compatibility.mdx b/src/content/docs/data-localization/compatibility.mdx
index 724dbfd2c9587c6..472524c6f61c822 100644
--- a/src/content/docs/data-localization/compatibility.mdx
+++ b/src/content/docs/data-localization/compatibility.mdx
@@ -29,19 +29,19 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                                    | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------ | --------------- | ----------------- | -------------------------- |
 | Caching/CDN                                | ✅              | ✅                | ✅                         |
-| Cache Reserve                              | ⚫️              | 🚧                | ✅ [^29]                   |
-| DNS                                        | ⚫️              | 🚧 [^33]          | ✅                         |
-| HTTP/3 (with QUIC)                         | ⚫️              | ✘                 | ⚫️                         |
+| Cache Reserve                              | ⚫️             | 🚧                | ✅ [^29]                   |
+| DNS                                        | ⚫️             | 🚧 [^33]          | ✅                         |
+| HTTP/3 (with QUIC)                         | ⚫️             | ✘                 | ⚫️                        |
 | Image Resizing                             | ✅              | ✅ [^6]           | 🚧 [^1]                    |
 | Load Balancing                             | ✅              | ✅                | 🚧 [^1]                    |
-| Network Error Logging (NEL)                | ⚫️              | ⚫️                | ✘                          |
+| Network Error Logging (NEL)                | ⚫️             | ⚫️               | ✘                          |
 | Onion Routing                              | ✘               | ✘                 | ✘                          |
 | O2O                                        | ✘               | ✘                 | ✘                          |
 | Stream Delivery                            | ✅              | ✅                | ✅                         |
 | Tiered Caching                             | ✅              | 🚧 [^2]           | 🚧 [^30]                   |
 | Trace                                      | ✘               | ✘                 | ✘                          |
-| Waiting Room                               | ⚫️              | ✅                | ✅                         |
-| Web Analytics / Real User Monitoring (RUM) | ⚫️              | ⚫️                | ✘ [^43]                    |
+| Waiting Room                               | ⚫️             | ✅                | ✅                         |
+| Web Analytics / Real User Monitoring (RUM) | ⚫️             | ⚫️               | ✘ [^43]                    |
 | Zaraz                                      | ✅              | ✅                | ✅                         |
 
 ---
@@ -50,18 +50,18 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------- | --------------- | ----------------- | -------------------------- |
-| Advanced Certificate Manager                | ⚫️              | ⚫️                | ⚫️                         |
+| Advanced Certificate Manager                | ⚫️             | ⚫️               | ⚫️                        |
 | Advanced DDoS Protection                    | ✅              | ✅                | 🚧 [^3]                    |
 | API Shield                                  | ✅              | ✅                | 🚧 [^4]                    |
 | Bot Management                              | ✅              | ✅                | ✅                         |
 | Client-side security (formerly Page Shield) | ✅              | ✅                | ✅                         |
-| DNS Firewall                                | ⚫️              | ⚫️                | ✅                         |
+| DNS Firewall                                | ⚫️             | ⚫️               | ✅                         |
 | Rate Limiting                               | ✅              | ✅                | ✅ [^37]                   |
 | SSL                                         | ✅              | ✅                | ✅                         |
 | Cloudflare for SaaS                         | ✘               | ✅                | ✅                         |
-| Turnstile                                   | ⚫️              | ✘                 | ✅ [^38]                   |
+| Turnstile                                   | ⚫️             | ✘                 | ✅ [^38]                   |
 | WAF/L7 Firewall                             | ✅              | ✅                | ✅                         |
-| DMARC Management                            | ⚫️              | ⚫️                | ✅                         |
+| DMARC Management                            | ⚫️             | ⚫️               | ✅                         |
 
 ---
 
@@ -69,24 +69,24 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                        | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------ | --------------- | ----------------- | -------------------------- |
-| Cloudflare Images              | ⚫️              | ✅ [^36]          | 🚧 [^35]                   |
+| Cloudflare Images              | ⚫️             | ✅ [^36]          | 🚧 [^35]                   |
 | AI Gateway                     | ✘               | ✘                 | 🚧 [^39]                   |
 | AI Search                      | ✘ [^46]         | ✘ [^47]           | 🚧 [^48]                   |
 | AI Security for Apps           | ✘               | ✘                 | ✘                          |
 | Cloudflare Pages               | ✅ [^11]        | ✅ [^11]          | 🚧 [^1]                    |
-| Cloudflare D1                  | ⚫️              | ⚫️                | 🚧 [^40]                   |
-| Durable Objects                | ⚫️              | ✅ [^7]           | 🚧 [^1]                    |
-| Email Routing                  | ⚫️              | ⚫️                | ✅                         |
+| Cloudflare D1                  | ⚫️             | ⚫️               | 🚧 [^40]                   |
+| Durable Objects                | ⚫️             | ✅ [^7]           | 🚧 [^1]                    |
+| Email Routing                  | ⚫️             | ⚫️               | ✅                         |
 | Remote MCP Server              | ✅ [^44]        | ✅ [^45]          | 🚧 [^1]                    |
 | R2                             | ✅ [^27]        | ✅ [^8]           | ✅ [^28]                   |
-| Smart Placement                | ⚫️              | ✘                 | ✘                          |
-| Stream                         | ⚫️              | ✘                 | 🚧 [^1]                    |
-| Vectorize                      | ⚫️              | ✘                 | ✘                          |
+| Smart Placement                | ⚫️             | ✘                 | ✘                          |
+| Stream                         | ⚫️             | ✘                 | 🚧 [^1]                    |
+| Vectorize                      | ⚫️             | ✘                 | ✘                          |
 | Workers (deployed on a Zone)   | ✅              | ✅                | 🚧 [^41]                   |
-| Workers AI                     | ⚫️              | ✘                 | ✅                         |
-| Workers KV                     | ⚫️              | ✘                 | ✅ [^34]                   |
+| Workers AI                     | ⚫️             | ✘                 | ✅                         |
+| Workers KV                     | ⚫️             | ✘                 | ✅ [^34]                   |
 | Workers.dev                    | ✘               | ✘                 | ✘                          |
-| Workers Analytics Engine (WAE) | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Workers Analytics Engine (WAE) | ⚫️             | ⚫️               | 🚧 [^1]                    |
 
 ---
 
@@ -95,11 +95,11 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------------- | --------------- | ----------------- | -------------------------- |
 | Argo Smart Routing          | ✅              | ✘ [^9]            | ✘ [^10]                    |
-| Static IP/BYOIP             | ⚫️              | ✅ [^26]          | ⚫️                         |
-| Cloudflare Network Firewall | ⚫️              | ⚫️                | ✅                         |
-| Network Flow                | ⚫️              | ⚫️                | 🚧 [^1]                    |
-| Magic Transit               | ⚫️              | ⚫️                | ✅ [^3]                    |
-| Cloudflare WAN              | ⚫️              | ⚫️                | ✅                         |
+| Static IP/BYOIP             | ⚫️             | ✅ [^26]          | ⚫️                        |
+| Cloudflare Network Firewall | ⚫️             | ⚫️               | ✅                         |
+| Network Flow                | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Magic Transit               | ⚫️             | ⚫️               | ✅ [^3]                    |
+| Cloudflare WAN              | ⚫️             | ⚫️               | ✅                         |
 | Spectrum                    | ✅              | ✅ [^42]          | ✅                         |
 
 ---
@@ -108,9 +108,9 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product      | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------ | --------------- | ----------------- | -------------------------- |
-| Logpull      | ⚫️              | ⚫️                | 🚧 [^12]                   |
-| Logpush      | ⚫️              | ✅                | 🚧 [^13]                   |
-| Log Explorer | ⚫️              | ⚫️                | ✘ [^23]                    |
+| Logpull      | ⚫️             | ⚫️               | 🚧 [^12]                   |
+| Logpush      | ⚫️             | ✅                | 🚧 [^13]                   |
+| Log Explorer | ⚫️             | ⚫️               | ✘ [^23]                    |
 
 ---
 
@@ -119,13 +119,13 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product               | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------- | --------------- | ----------------- | -------------------------- |
 | Access                | 🚧 [^14]        | 🚧 [^15]          | ✅ [^16]                   |
-| Browser Isolation     | ⚫️              | 🚧 [^17]          | ✅                         |
-| CASB                  | ⚫️              | ⚫️                | ✘                          |
-| Cloudflare Tunnel     | ⚫️              | 🚧 [^18]          | ⚫️                         |
-| Digital Experience    | ⚫️              | ⚫️                | 🚧 [^49]                   |
-| DLP                   | ⚫️ [^19]        | ⚫️ [^19]          | 🚧 [^31]                   |
+| Browser Isolation     | ⚫️             | 🚧 [^17]          | ✅                         |
+| CASB                  | ⚫️             | ⚫️               | ✘                          |
+| Cloudflare Tunnel     | ⚫️             | 🚧 [^18]          | ⚫️                        |
+| Digital Experience    | ⚫️             | ⚫️               | 🚧 [^49]                   |
+| DLP                   | ⚫️ [^19]       | ⚫️ [^19]         | 🚧 [^31]                   |
 | Gateway               | 🚧 [^20]        | 🚧 [^21]          | 🚧 [^22]                   |
-| Cloudflare One Client | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Cloudflare One Client | ⚫️             | ⚫️               | 🚧 [^1]                    |
 
 [^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
 
diff --git a/src/content/docs/data-localization/geo-key-manager.mdx b/src/content/docs/data-localization/geo-key-manager.mdx
index 510eb40b49191a5..6bafbbf4ad50e68 100644
--- a/src/content/docs/data-localization/geo-key-manager.mdx
+++ b/src/content/docs/data-localization/geo-key-manager.mdx
@@ -9,6 +9,7 @@ tags:
   - Compliance
 sidebar:
   order: 4
+
 ---
 
 Geo Key Manager offers enhanced control over the storage location of your private SSL/TLS keys — the cryptographic keys that Cloudflare uses to decrypt your HTTPS traffic. By restricting where these keys are stored, you can ensure compliance with regional data regulations and security requirements.
@@ -23,7 +24,7 @@ Geo Key Manager was restricted to the US, EU, and high-security data centers, bu
 
 The following diagram shows what happens when an end user connects to a Cloudflare data center that does not hold your private key. Because TLS termination requires the private key, the local data center must request a temporary session key (a short-lived symmetric encryption key) from a data center in an authorized region. Once the session key is established, the local data center can decrypt traffic for the remainder of the connection without contacting the key-holding data center again. This extra step adds latency on the first request, which can be as much as a second if the key-holding data center is geographically distant.
 
-<br />
+<br/>
 
 ```mermaid
 sequenceDiagram
@@ -40,6 +41,6 @@ sequenceDiagram
     User-->>CloudflarePoP: Subsequent requests use the Session Key
 ```
 
-<br />
+<br/>
 
 For detailed information on setup and supported options, refer to [Geo Key Manager documentation](/ssl/edge-certificates/geokey-manager/).
diff --git a/src/content/docs/ddos-protection/about/components.mdx b/src/content/docs/ddos-protection/about/components.mdx
index 9161b6dd7d87b5a..fdad5713c8a928e 100644
--- a/src/content/docs/ddos-protection/about/components.mdx
+++ b/src/content/docs/ddos-protection/about/components.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 ![Diagram with the main components providing protection against DDoS attacks at Cloudflare](~/assets/images/ddos-protection/ddos-diagram.png)
 
diff --git a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
index 921203e498c7fda..2be132500131a7d 100644
--- a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
+++ b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
@@ -9,9 +9,10 @@ sidebar:
 learning_center:
   title: What is a DDoS attack?
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To detect and mitigate <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attacks</GlossaryTooltip>, Cloudflare's autonomous edge and centralized DDoS systems analyze traffic samples out of path, which allows Cloudflare to asynchronously detect DDoS attacks without causing latency or impacting performance.
 
@@ -30,13 +31,13 @@ You can set an override expression for the [HTTP DDoS Attack Protection](/ddos-p
 
 Once attack traffic matches a rule, Cloudflare's systems will track that traffic and generate a real-time signature to surgically match against the attack pattern and mitigate the attack without impacting legitimate traffic. The rules are able to generate different signatures based on various properties of the attacks and the signal strength of each attribute. For example, if the attack is distributed — that is, originating from many source IPs — then the source IP field will not serve as a strong indicator, and the rule will not choose the source IP field as part of the attack signature. Once generated, the fingerprint is propagated as a mitigation rule to the most optimal location on the Cloudflare global network for cost-efficient mitigation. These mitigation rules are ephemeral and will expire shortly after the attack has ended, which happens when no additional traffic has been matched to the rule.
 
-| Actions               | Description                                                                                             |
-| --------------------- | ------------------------------------------------------------------------------------------------------- |
-| Block                 | Matching requests are denied access to the site.                                                        |
-| Managed Challenge     | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
-| Interactive Challenge | The client that made the request must pass an interactive Challenge.                                    |
-| Log                   | Records matching requests in the Cloudflare Logs.                                                       |
-| Use rule defaults     | Uses the default action that is pre-defined for each rule.                                              |
+| Actions | Description |
+| --- | --- |
+| Block | Matching requests are denied access to the site. |
+| Managed Challenge | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
+| Interactive Challenge | The client that made the request must pass an interactive Challenge. |
+| Log | Records matching requests in the Cloudflare Logs. |
+| Use rule defaults | Uses the default action that is pre-defined for each rule. |
 
 ## Thresholds
 
diff --git a/src/content/docs/ddos-protection/about/index.mdx b/src/content/docs/ddos-protection/about/index.mdx
index c294dbc5482978b..65805b05908aecd 100644
--- a/src/content/docs/ddos-protection/about/index.mdx
+++ b/src/content/docs/ddos-protection/about/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: About Cloudflare DDoS protection
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare provides unmetered and unlimited <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">distributed denial-of-service (DDoS)</GlossaryTooltip> protection at layers 3, 4, and 7 to all customers on all plans and services.
 
@@ -19,4 +20,4 @@ The protection is enabled by Cloudflare's [Autonomous DDoS Protection Edge](/ddo
 
 The Autonomous Edge includes multiple dynamic mitigation rules exposed as [managed rulesets](/ddos-protection/managed-rulesets/), which provide comprehensive protection against a variety of DDoS attacks across layers 3/4 and layer 7 of the OSI model.
 
-[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
+[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
index 011867f5ba98440..80a1257af1beb09 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
@@ -10,6 +10,7 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced DNS Protection via API
+
 ---
 
 Use the [Cloudflare API](/api/) to configure Advanced DNS Protection via API.
@@ -28,11 +29,11 @@ The `{account_id}` argument is the [account ID](/fundamentals/account/find-accou
 
 The following table summarizes the available operations.
 
-| Operation                       | Verb + Endpoint                                                                                                                                                               |
-| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List DNS protection rules       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account.                                 |
-| Add a DNS protection rule       | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account.                                      |
-| Get a DNS protection rule       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
-| Update a DNS protection rule    | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account.              |
-| Delete a DNS protection rule    | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account.           |
-| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account.                   |
+| Operation | Verb + Endpoint |
+| --- | --- |
+| List DNS protection rules | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account. |
+| Add a DNS protection rule | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account. |
+| Get a DNS protection rule | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
+| Update a DNS protection rule | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account. |
+| Delete a DNS protection rule | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account. |
+| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account. |
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
index 803a3e818448f83..1c556c9c56533bc 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
+
 ---
 
 # JSON object
@@ -19,15 +20,15 @@ This page contains an example of the DNS protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"mode": "monitoring",
-	"profile_sensitivity": "medium",
-	"rate_sensitivity": "medium",
-	"burst_sensitivity": "medium",
-	"created_on": "2023-10-01T13:10:38.762503+01:00",
-	"modified_on": "2023-10-01T13:10:38.762503+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "mode": "monitoring",
+  "profile_sensitivity": "medium",
+  "rate_sensitivity": "medium",
+  "burst_sensitivity": "medium",
+  "created_on": "2023-10-01T13:10:38.762503+01:00",
+  "modified_on": "2023-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -39,4 +40,4 @@ The `profile_sensitivity` field value must be one of `low` (default), `medium`,
 
 The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`, `medium`, or `high`.
 
-For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
+For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
index 52ffefc830a024b..703796d727a36f1 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced TCP Protection and Advanced DNS Protection via the API
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to configure Advanced TCP Protection and Advanced DNS Protection via the API.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
index 2783ca32b25243f..75c5ed4d2392138 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
@@ -8,6 +8,7 @@ tags:
   - REST API
 sidebar:
   order: 2
+
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/#endpoints).
@@ -23,18 +24,18 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<PROGRAM_ID>",
-			"name": "rate-limiter",
-			"status": "success",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<PROGRAM_ID>",
+      "name": "rate-limiter",
+      "status": "success",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -51,16 +52,16 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<PROGRAM_ID>",
-		"name": "program",
-		"status": "success",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<PROGRAM_ID>",
+    "name": "program",
+    "status": "success",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -68,15 +69,15 @@ If the program fails compilation or verification, the API returns a detailed err
 
 ```json title="Example error response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"code": 1001,
-			"message": "Program verification failed: invalid memory access at line 42"
-		}
-	],
-	"messages": []
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "code": 1001,
+      "message": "Program verification failed: invalid memory access at line 42"
+    }
+  ],
+  "messages": []
 }
 ```
 
@@ -94,16 +95,16 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<PROGRAM_ID>",
-		"name": "program",
-		"status": "success",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<PROGRAM_ID>",
+    "name": "program",
+    "status": "success",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -119,10 +120,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": null,
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -137,21 +138,21 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID>",
-			"program_id": "<PROGRAM_ID>",
-			"scope": "global",
-			"name": "global",
-			"mode": "enabled",
-			"expression": "",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<RULE_ID>",
+      "program_id": "<PROGRAM_ID>",
+      "scope": "global",
+      "name": "global",
+      "mode": "enabled",
+      "expression": "",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -173,19 +174,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "global",
-		"name": "global",
-		"mode": "monitoring",
-		"expression": "",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "global",
+    "name": "global",
+    "mode": "monitoring",
+    "expression": "",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -210,19 +211,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "enabled",
-		"expression": "ip.dst in { 192.0.2.0/24 }",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "enabled",
+    "expression": "ip.dst in { 192.0.2.0/24 }",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -244,19 +245,19 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "global",
-		"name": "global",
-		"mode": "enabled",
-		"expression": "",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "global",
+    "name": "global",
+    "mode": "enabled",
+    "expression": "",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -274,10 +275,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": null,
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -298,7 +299,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 The output PCAP file contains the same packets as the input file, but with annotations on each packet.
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
index 5a3cb4ee6ba3756..e9ea67979faf416 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
@@ -12,6 +12,7 @@ sidebar:
 head:
   - tag: title
     content: Configure Programmable Flow Protection via API
+
 ---
 
 Use the [Cloudflare API](/api/) to configure Programmable Flow Protection.
@@ -32,30 +33,30 @@ The tables in the following sections summarize the available operations.
 
 ### Program operations
 
-| Operation           | Method and endpoint / Description                                                                                                                       |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List programs       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
-| Upload a program    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account.                            |
-| Get a program       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program.          |
-| Update a program    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program.                       |
-| Delete a program    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account.     |
-| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account.                |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List programs | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
+| Upload a program | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account. |
+| Get a program | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program. |
+| Update a program | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program. |
+| Delete a program | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account. |
+| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account. |
 
 ### Rule operations
 
-| Operation        | Method and endpoint / Description                                                                                                                 |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List rules       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
-| Create a rule    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account.                            |
-| Get a rule       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule.             |
-| Update a rule    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account.           |
-| Delete a rule    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account.        |
-| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account.                |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List rules | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
+| Create a rule | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account. |
+| Get a rule | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule. |
+| Update a rule | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account. |
+| Delete a rule | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account. |
+| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account. |
 
 ### Debug operations
 
-| Operation       | Method and endpoint / Description                                                                                                                                                                |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation | Method and endpoint / Description |
+| --- | --- |
 | Debug with PCAP | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}/pcap`</p>Runs a program against a PCAP file and returns an annotated PCAP with program verdicts. |
 
 ## Pagination
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
index 7857e0cab2af7ad..f0fffca40457798 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Programmable Flow Protection API - JSON objects
+
 ---
 
 This page contains examples of the JSON objects used in the Programmable Flow Protection API.
@@ -19,47 +20,47 @@ This page contains examples of the JSON objects used in the Programmable Flow Pr
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"name": "rate-limiter",
-	"status": "success",
-	"created_on": "2024-01-01T13:06:04.721954+01:00",
-	"modified_on": "2024-01-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "name": "rate-limiter",
+  "status": "success",
+  "created_on": "2024-01-01T13:06:04.721954+01:00",
+  "modified_on": "2024-01-01T13:06:04.721954+01:00"
 }
 ```
 
-| Field         | Description                                                                                                                                             |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`          | Unique identifier for the program.                                                                                                                      |
-| `name`        | Name of the program, derived from the uploaded filename.                                                                                                |
-| `status`      | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
-| `created_on`  | Timestamp when the program was created.                                                                                                                 |
-| `modified_on` | Timestamp when the program was last modified.                                                                                                           |
+| Field | Description |
+| --- | --- |
+| `id` | Unique identifier for the program. |
+| `name` | Name of the program, derived from the uploaded filename. |
+| `status` | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
+| `created_on` | Timestamp when the program was created. |
+| `modified_on` | Timestamp when the program was last modified. |
 
 ## Rule
 
 ```json
 {
-	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-	"program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"mode": "enabled",
-	"expression": "ip.dst in { 192.0.2.0/24 }",
-	"created_on": "2024-01-01T13:10:38.762503+01:00",
-	"modified_on": "2024-01-01T13:10:38.762503+01:00"
+  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+  "program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "mode": "enabled",
+  "expression": "ip.dst in { 192.0.2.0/24 }",
+  "created_on": "2024-01-01T13:10:38.762503+01:00",
+  "modified_on": "2024-01-01T13:10:38.762503+01:00"
 }
 ```
 
-| Field         | Description                                                                                                                       |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `id`          | Unique identifier for the rule.                                                                                                   |
-| `program_id`  | The ID of the program this rule executes.                                                                                         |
-| `scope`       | The scope of the rule. Must be one of `global`, `region`, or `datacenter`.                                                        |
-| `name`        | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code.                 |
-| `mode`        | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`.                                                             |
-| `expression`  | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
-| `created_on`  | Timestamp when the rule was created.                                                                                              |
-| `modified_on` | Timestamp when the rule was last modified.                                                                                        |
+| Field | Description |
+| --- | --- |
+| `id` | Unique identifier for the rule. |
+| `program_id` | The ID of the program this rule executes. |
+| `scope` | The scope of the rule. Must be one of `global`, `region`, or `datacenter`. |
+| `name` | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code. |
+| `mode` | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`. |
+| `expression` | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
+| `created_on` | Timestamp when the rule was created. |
+| `modified_on` | Timestamp when the rule was last modified. |
 
 ### Scope
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
index c8ce427c16455cb..8e87b35dd014b57 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
@@ -8,6 +8,7 @@ tags:
   - REST API
 sidebar:
   order: 2
+
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/tcp-protection/#endpoints).
@@ -23,12 +24,12 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json title="Example response"
 {
-	"result": {
-		"enabled": false
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "enabled": false
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -57,16 +58,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"prefix": "203.0.113/24",
-			"comment": "My prefix",
-			"excluded": false
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "prefix": "203.0.113/24",
+      "comment": "My prefix",
+      "excluded": false
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -94,27 +95,27 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<PREFIX_1_ID>",
-			"prefix": "192.0.2.0/24",
-			"excluded": false,
-			"comment": "Game ranges",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		},
-		{
-			"id": "<PREFIX_2_ID>",
-			"prefix": "192.0.2.2/26",
-			"excluded": true,
-			"comment": "Range for a specific game",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<PREFIX_1_ID>",
+      "prefix": "192.0.2.0/24",
+      "excluded": false,
+      "comment": "Game ranges",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    },
+    {
+      "id": "<PREFIX_2_ID>",
+      "prefix": "192.0.2.2/26",
+      "excluded": true,
+      "comment": "Range for a specific game",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -129,19 +130,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<ALLOWLIST_PREFIX_ID>",
-			"prefix": "192.0.2.127",
-			"comment": "Single IP address in allowlist",
-			"enabled": true,
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<ALLOWLIST_PREFIX_ID>",
+      "prefix": "192.0.2.127",
+      "comment": "Single IP address in allowlist",
+      "enabled": true,
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -162,17 +163,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<ALLOWLIST_PREFIX_1_ID>",
-		"prefix": "203.0.113.0/26",
-		"comment": "Partner range",
-		"enabled": true,
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<ALLOWLIST_PREFIX_1_ID>",
+    "prefix": "203.0.113.0/26",
+    "comment": "Partner range",
+    "enabled": true,
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -195,19 +196,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<SYN_FLOOD_RULE_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "monitoring",
-		"rate_sensitivity": "medium",
-		"burst_sensitivity": "medium",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<SYN_FLOOD_RULE_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "monitoring",
+    "rate_sensitivity": "medium",
+    "burst_sensitivity": "medium",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -232,19 +233,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<OOS_TCP_RULE_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "monitoring",
-		"rate_sensitivity": "low",
-		"burst_sensitivity": "low",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<OOS_TCP_RULE_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "monitoring",
+    "rate_sensitivity": "low",
+    "burst_sensitivity": "low",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -266,16 +267,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<SYN_FLOOD_FILTER_ID>",
-		"expression": "ip.dst in { 192.0.2.0/24 }",
-		"mode": "monitoring",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<SYN_FLOOD_FILTER_ID>",
+    "expression": "ip.dst in { 192.0.2.0/24 }",
+    "mode": "monitoring",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -297,17 +298,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<OOS_TCP_FILTER_ID>",
-		"expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
-		"mode": "disabled",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<OOS_TCP_FILTER_ID>",
+    "expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
+    "mode": "disabled",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
-Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
+Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
index 5af3cfacb95b70f..54d00d15660f858 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
@@ -12,6 +12,7 @@ head:
     content: Configure Advanced TCP Protection via API
 tags:
   - TCP
+
 ---
 
 You can configure Advanced TCP Protection using the Advanced TCP Protection API.
@@ -36,81 +37,81 @@ The tables in the following sections summarize the available operations.
 
 ### General operations
 
-| Operation                             | Method and endpoint / Description                                                                                                                                   |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Get Advanced TCP Protection status    | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| Get Advanced TCP Protection status | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
 | Update Advanced TCP Protection status | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Enables or disables Advanced TCP Protection.                        |
 
 ### Prefix operations
 
-| Operation            | Method and endpoint / Description                                                                                                                             |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List prefixes        | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account.                 |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account. |
 | Add prefixes in bulk | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/bulk`</p>Adds prefixes in bulk to the account (up to 300 prefixes per request). |
-| Get a prefix         | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix.                       |
-| Update a prefix      | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix.                                    |
-| Delete a prefix      | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix.                                   |
-| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account.                           |
+| Get a prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix. |
+| Update a prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix. |
+| Delete a prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix. |
+| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account. |
 
 ### Allowlist operations
 
-| Operation                       | Method and endpoint / Description                                                                                                                            |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List allowlisted prefixes       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
-| Add an allowlisted prefix       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
-| Get an allowlisted prefix       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
-| Update an allowlisted prefix    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist.              |
-| Delete an allowlisted prefix    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist.           |
-| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist.                       |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List allowlisted prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
+| Add an allowlisted prefix | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
+| Get an allowlisted prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
+| Update an allowlisted prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist. |
+| Delete an allowlisted prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist. |
+| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist. |
 
 ### SYN Flood Protection operations
 
 #### Rules
 
-| Operation                  | Method and endpoint / Description                                                                                                                                        |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List SYN flood rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account.                                 |
-| Add a SYN flood rule       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account.                                      |
-| Get a SYN flood rule       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
-| Update a SYN flood rule    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account.              |
-| Delete a SYN flood rule    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account.           |
-| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account.                   |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List SYN flood rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account. |
+| Add a SYN flood rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account. |
+| Get a SYN flood rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
+| Update a SYN flood rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account. |
+| Delete a SYN flood rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account. |
+| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account. |
 
 #### Filters
 
-| Operation                    | Method and endpoint / Description                                                                                                                                              |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List SYN flood filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account.                                   |
-| Add a SYN flood filter       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account.                                        |
-| Get a SYN flood filter       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
-| Update a SYN flood filter    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account.              |
-| Delete a SYN flood filter    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account.           |
-| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account.                     |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List SYN flood filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account. |
+| Add a SYN flood filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account. |
+| Get a SYN flood filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
+| Update a SYN flood filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account. |
+| Delete a SYN flood filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account. |
+| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account. |
 
 ### Out-of-state TCP Protection operations
 
 #### Rules
 
-| Operation                         | Method and endpoint / Description                                                                                                                                                    |
-| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List out-of-state TCP rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account.                                 |
-| Add an out-of-state TCP rule      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account.                                     |
-| Get an out-of-state TCP rule      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
-| Update an out-of-state TCP rule   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account.              |
-| Delete an out-of-state TCP rule   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account.           |
-| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account.                   |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List out-of-state TCP rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account. |
+| Add an out-of-state TCP rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account. |
+| Get an out-of-state TCP rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
+| Update an out-of-state TCP rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account. |
+| Delete an out-of-state TCP rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account. |
+| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account. |
 
 #### Filters
 
-| Operation                           | Method and endpoint / Description                                                                                                                                                          |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List out-of-state TCP filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account.                                   |
-| Add an out-of-state TCP filter      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account.                                       |
-| Get an out-of-state TCP filter      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
-| Update an out-of-state TCP filter   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account.              |
-| Delete an out-of-state TCP filter   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account.           |
-| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account.                     |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List out-of-state TCP filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account. |
+| Add an out-of-state TCP filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account. |
+| Get an out-of-state TCP filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
+| Update an out-of-state TCP filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account. |
+| Delete an out-of-state TCP filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account. |
+| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account. |
 
 ## Pagination
 
-The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
+The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
index 1368cbecbe0cfe8..b2186e3c55edc9b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
+
 ---
 
 This page contains an example of the TCP protection rule JSON object used in the API.
@@ -19,12 +20,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"prefix": "192.0.2.0/24",
-	"comment": "Game ranges",
-	"excluded": false,
-	"created_on": "2022-01-01T13:06:04.721954+01:00",
-	"modified_on": "2022-01-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "prefix": "192.0.2.0/24",
+  "comment": "Game ranges",
+  "excluded": false,
+  "created_on": "2022-01-01T13:06:04.721954+01:00",
+  "modified_on": "2022-01-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -32,12 +33,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"prefix": "192.0.2.0/24",
-	"comment": "Game ranges",
-	"enabled": true,
-	"created_on": "2021-10-01T13:06:04.721954+01:00",
-	"modified_on": "2021-10-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "prefix": "192.0.2.0/24",
+  "comment": "Game ranges",
+  "enabled": true,
+  "created_on": "2021-10-01T13:06:04.721954+01:00",
+  "modified_on": "2021-10-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -47,13 +48,13 @@ The `prefix` field can contain an IP address or a CIDR range.
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"rate_sensitivity": "medium",
-	"burst_sensitivity": "medium",
-	"created_on": "2021-10-01T13:10:38.762503+01:00",
-	"modified_on": "2021-10-01T13:10:38.762503+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "rate_sensitivity": "medium",
+  "burst_sensitivity": "medium",
+  "created_on": "2021-10-01T13:10:38.762503+01:00",
+  "modified_on": "2021-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -65,11 +66,11 @@ The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`
 
 ```json
 {
-	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-	"expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
-	"mode": "enabled",
-	"created_on": "2022-11-01T13:10:38.762503+01:00",
-	"modified_on": "2022-11-01T13:10:38.762503+01:00"
+  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+  "expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
+  "mode": "enabled",
+  "created_on": "2022-11-01T13:10:38.762503+01:00",
+  "modified_on": "2022-11-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -85,4 +86,4 @@ The `expression` field is a [Rules language expression](/ruleset-engine/rules-la
 Expressions of SYN flood protection and out-of-state TCP protection filters do not currently support functions.
 :::
 
-The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
+The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
index e542bce53c6b4fa..7906194f1a69e0b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
@@ -9,9 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Add a prefix to Advanced DDoS Protection
----
 
-import { Steps, DashButton } from "~/components";
+---
+import { Steps, DashButton } from "~/components"
 
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
@@ -28,4 +28,4 @@ To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to
 :::note[Note]
 
 The **Add existing prefix** list will not display leased prefixes, but you can add them manually in the Cloudflare dashboard or [using the API](/ddos-protection/advanced-ddos-systems/api/). You cannot add [delegated prefixes](/byoip/concepts/prefix-delegations/) to Advanced TCP Protection.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
index 405eeb35a0dab05..df2d627092922fe 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 5
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
@@ -25,4 +26,4 @@ To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 :::note
 
 Prefixes or subsets added as _Excluded_ will not be protected by Advanced TCP Protection.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
index 87c03f48746ed33..19ab785b897da72 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: How-to guides
 description: How-to guides for configuring Advanced TCP Protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
index fe36b285e12bed7..7ee74065ee74642 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
@@ -8,9 +8,11 @@ sidebar:
   group:
     hideIndex: true
   order: 6
+
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's Advanced DDoS systems:
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
index bedd9eaac204c3e..495f1aa4c759f15 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
@@ -39,20 +39,20 @@ Once thresholds are configured, the Advanced DDoS Protection systems have been i
 
 Automatic thresholds for Cloudflare's Advanced DDoS Protection system optimizes the detection and mitigation of DDoS attacks by automatically calculating appropriate traffic thresholds for each system for each customer account. This system applies to Advanced TCP Protection (specifically SYN Flood Protection and Out-of-State TCP Flood Protection) and Advanced DNS Protection.
 
-Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds.
+Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds. 
 
 #### Process
 
-The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below.
+The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below. 
 
 - The `flowtrackd` account was created within the past 7 to 10 days.
 - The account has at least one configured global threshold (rate and burst). This can be a threshold that was automatically provisioned by the system or manually provisioned by Cloudflare.
 
 These checks are performed independently for SYN Flood Protection, Out-of-State TCP Flood Protection, and Advanced DNS Protection. The criteria does not require the presence of any rules to be configured. Accounts initially provisioned by the automatic system will have default thresholds. Otherwise, thresholds may be unconfigured if they are not set by Cloudflare.
 
-After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic.
+After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic. 
 
-Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst.
+Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst. 
 
 Thresholds are derived using the 95th percentile (P95) of observed traffic over the preceding seven days:
 
@@ -60,9 +60,9 @@ Thresholds are derived using the 95th percentile (P95) of observed traffic over
 - Out-of-State TCP Flood Protection: Based on all other TCP flag traffic.
 - Advanced DNS Protection: Based on DNS over UDP traffic.
 
-While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance.
+While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance. 
 
-The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team.
+The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team. 
 
 #### Implementation
 
@@ -70,7 +70,7 @@ You should enable the automatically provisioned rules. Initially, these rules wi
 
 #### Recalculation
 
-Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration.
+Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration. 
 
 #### Overrides
 
@@ -82,7 +82,7 @@ If you are actively under attack and diverting traffic to Cloudflare, the automa
 
 #### Limitations
 
-Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated.
+Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated. 
 
 The auto-threshold calculation component currently runs only in PDX. Therefore, this feature is not compatible if you have enabled Data Localization Services (DLS) and are located outside of the US, such as EU CMB. Future improvements will address this limitation.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
index 8e7eeb417b2d7c0..5c86d3ba72f115a 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
@@ -60,7 +60,7 @@ The Programmable Flow Protection system supports the [Data Localization suite](/
 :::caution[Beta functionality limitations]
 
 For more information on beta services, refer to section 2.6 in the [Enterprise Terms of Service](https://www.cloudflare.com/enterpriseterms/).
-:::
+  :::
 
 ### Write a basic program
 
@@ -210,7 +210,6 @@ The steps below write a sample program that drops all User Datagram Protocol (UD
 </Steps>
 
 For reference, the example below is the basic program in its entirety:
-
 ```c
 #define CF_EBPF_HELPER_V0
 
@@ -270,6 +269,7 @@ cf_ebpf_main(void *state)
 }
 ```
 
+
 ### Write a complex program: challenge-based response
 
 The example program below implements a UDP-based challenge-response mechanism using helper functions to maintain state between packets from the same source IP. This is useful for mitigating DDoS attacks by requiring clients to prove they can receive and respond to challenges before allowing their traffic through.
@@ -644,12 +644,12 @@ For reference, the example below is the rate limiting program in its entirety:
 #define RATE_LIMIT 100         // Maximum packets allowed per window
 #define WINDOW_SECONDS 60      // Time window in seconds
 
-// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the
+// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the 
 // table hold a timestamp and a counter to accomplish a ratelimit.
-//
-// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted.
+// 
+// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted. 
 // Values are also garbage collected from the table every 1hr.
-//
+// 
 // The macros below pack the timestamp (upper 32 bits) and counter (lower 32 bits) into 64-bit data
 // into a value that we can store into the source IP table.
 #define PACK_STATE(ts, count) (((uint64_t)(ts) << 32) | ((uint64_t)(count) & 0xFFFFFFFF))
@@ -727,15 +727,14 @@ If an incoming packet's source IP is blocklisted in the source IP state table, t
 
 The source IP state table stores state keyed by source IP address. Each entry contains:
 
-| Field     | Type  | Description                                                                                      |
-| --------- | ----- | ------------------------------------------------------------------------------------------------ |
-| Status    | Enum  | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
-| User data | `u64` | A user-defined value you can set for any purpose.                                                |
+| Field | Type | Description |
+| --- | --- | --- |
+| Status | Enum | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
+| User data | `u64` | A user-defined value you can set for any purpose. |
 
 The default maximum capacity is 1,000 entries.
 
 Use the following helper functions to interact with this table:
-
 - `get_src_ip_status` — Retrieve the status of the current packet's source IP.
 - `set_src_ip_status` — Set the status of the current packet's source IP.
 - `get_src_ip_data` — Retrieve the user data for the current packet's source IP.
@@ -748,7 +747,6 @@ The flow state table stores state keyed by the 4-tuple: source IP, source port,
 The default maximum capacity is 10,000 entries.
 
 Use the following helper functions to interact with this table:
-
 - `get_flow_data` — Retrieve the user data for the current flow.
 - `set_flow_data` — Store user data for the current flow.
 
@@ -770,32 +768,32 @@ Helper functions may be removed or changed. New helper functions may be introduc
 
 The table below provides a list of currently supported helper functions:
 
-| Function name               | Function signature                                                                          | Description                                                                                                                                                                                                                             |
-| --------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `rand`                      | `uint64_t rand(void)`                                                                       | Generates a random unsigned integer.                                                                                                                                                                                                    |
-| `timestamp`                 | `uint64_t timestamp(void)`                                                                  | Returns the current timestamp.                                                                                                                                                                                                          |
-| `hash_md5`                  | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)`                                  | Computes MD5 hash of the source buffer and stores result in destination buffer.                                                                                                                                                         |
-| `hash_sha256`               | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-256 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
-| `hash_sha512`               | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-512 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
-| `hash_crc32`                | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)`                                | Computes CRC32 hash of the source buffer and stores result in destination buffer.                                                                                                                                                       |
-| `hmac_sha256`               | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
-| `hmac_sha512`               | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
-| `set_challenge`             | `int set_challenge(uint8_t *src, size_t src_len)`                                           | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset.                                                                                                                                                 |
-| `get_src_ip_status`         | `uint64_t get_src_ip_status(void)`                                                          | Retrieves the status value associated with the source IP address from the state table.                                                                                                                                                  |
-| `set_src_ip_status`         | `int set_src_ip_status(uint64_t status)`                                                    | Sets the status value associated with the source IP address in the state table.                                                                                                                                                         |
-| `get_src_ip_data`           | `int get_src_ip_data(uint8_t *dst, size_t dst_len)`                                         | Retrieves custom data associated with the source IP address from the state table.                                                                                                                                                       |
-| `set_src_ip_data`           | `int set_src_ip_data(uint8_t *src, size_t src_len)`                                         | Stores custom data associated with the source IP address in the state table.                                                                                                                                                            |
-| `get_flow_data`             | `int get_flow_data(uint8_t *dst, size_t dst_len)`                                           | Retrieves custom data associated with the current flow from the state table.                                                                                                                                                            |
-| `set_flow_data`             | `int set_flow_data(uint8_t *src, size_t src_len)`                                           | Stores custom data associated with the current flow in the state table.                                                                                                                                                                 |
-| `entropy`                   | `double entropy(uint8_t *src, size_t src_len)`                                              | Calculates the entropy of the source buffer.                                                                                                                                                                                            |
-| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)`                                                  | Sets a custom tag for network analytics reporting. Defaults to `0` if not set.                                                                                                                                                          |
-| `ntohs`                     | `uint16_t ntohs(uint16_t netshort)`                                                         | Converts a 16-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htons`                     | `uint16_t htons(uint16_t hostshort)`                                                        | Converts a 16-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `ntohl`                     | `uint32_t ntohl(uint32_t netlong)`                                                          | Converts a 32-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htonl`                     | `uint32_t htonl(uint32_t hostlong)`                                                         | Converts a 32-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `ntohll`                    | `uint64_t ntohll(uint64_t netlonglong)`                                                     | Converts a 64-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htonll`                    | `uint64_t htonll(uint64_t hostlonglong)`                                                    | Converts a 64-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `parse_packet_data`         | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)`   | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
+| Function name       | Function signature                                                               | Description                                                                                                                                                                                                                             |
+| ------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rand`      | `uint64_t rand(void)`                                                                           | Generates a random unsigned integer.                                                                                                                                                                                                    |
+| `timestamp` | `uint64_t timestamp(void)` | Returns the current timestamp. |
+| `hash_md5` | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes MD5 hash of the source buffer and stores result in destination buffer. |
+| `hash_sha256` | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-256 hash of the source buffer and stores result in destination buffer. |
+| `hash_sha512` | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-512 hash of the source buffer and stores result in destination buffer. |
+| `hash_crc32` | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes CRC32 hash of the source buffer and stores result in destination buffer. |
+| `hmac_sha256` | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer. |
+| `hmac_sha512` | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer. |
+| `set_challenge` | `int set_challenge(uint8_t *src, size_t src_len)` | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset. |
+| `get_src_ip_status` | `uint64_t get_src_ip_status(void)` | Retrieves the status value associated with the source IP address from the state table. |
+| `set_src_ip_status` | `int set_src_ip_status(uint64_t status)` | Sets the status value associated with the source IP address in the state table. |
+| `get_src_ip_data` | `int get_src_ip_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the source IP address from the state table. |
+| `set_src_ip_data` | `int set_src_ip_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the source IP address in the state table. |
+| `get_flow_data` | `int get_flow_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the current flow from the state table. |
+| `set_flow_data` | `int set_flow_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the current flow in the state table. |
+| `entropy` | `double entropy(uint8_t *src, size_t src_len)` | Calculates the entropy of the source buffer. |
+| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)` | Sets a custom tag for network analytics reporting. Defaults to `0` if not set. |
+| `ntohs` | `uint16_t ntohs(uint16_t netshort)` | Converts a 16-bit integer from network byte order to host byte order. |
+| `htons` | `uint16_t htons(uint16_t hostshort)` | Converts a 16-bit integer from host byte order to network byte order. |
+| `ntohl` | `uint32_t ntohl(uint32_t netlong)` | Converts a 32-bit integer from network byte order to host byte order. |
+| `htonl` | `uint32_t htonl(uint32_t hostlong)` | Converts a 32-bit integer from host byte order to network byte order. |
+| `ntohll` | `uint64_t ntohll(uint64_t netlonglong)` | Converts a 64-bit integer from network byte order to host byte order. |
+| `htonll` | `uint64_t htonll(uint64_t hostlonglong)` | Converts a 64-bit integer from host byte order to network byte order. |
+| `parse_packet_data` | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)` | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
 
 ---
 
@@ -807,7 +805,7 @@ With the exception of `rand`, `timestamp`, `ntohs`, `htons`, `ntohl`, `htonl`, `
 
 To upload a program, navigate to Networking > L3/4 DDoS protection > Advanced Protection in the Cloudflare dashboard. Then select the tab titled Programmable Flow Protection.
 
-Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code.
+Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code. 
 
 The Cloudflare API will receive the source code in the `C` file, compile it into BPF bytecode, and run the verifier against it.
 
@@ -815,11 +813,12 @@ If compilation or verification fails, the API will return a detailed error messa
 
 If compilation and verification succeeds, Cloudflare will store the source code and object file to the account and return the program ID.
 
+
 ### Update a program
 
 During the development process, you may find it useful to update the same program (identified by the same program ID) instead of repeatedly creating new programs as new resources.
 
-To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code.
+To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code. 
 
 :::note
 It is possible to update and overwrite a program that is currently in use by one or more rules. When doing so, you will be warned that the program is currently active and will be overwritten. However, if an active program is being updated with a program that either does not compile or can not be verified, the update will fail and the old program will continue to be in use.
@@ -833,7 +832,7 @@ A link icon next to the program name indicates that the program is currently in
 
 ### Delete a program
 
-To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**.
+To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**. 
 
 Note that you will not be able to delete a program that is referenced in an active Rule.
 
@@ -888,11 +887,10 @@ curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/programmab
 
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
-
 ---
 
 ## Safe program and rule deployment best practices
@@ -1013,7 +1011,7 @@ struct cf_ebpf_parsed_headers {
    uint8_t        *data_end;
 };
 
-/*
+/* 
 * IPv4 header, used as field of cf_ebpf_parsed_headers */
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ip.h#L87
 */
@@ -1036,10 +1034,10 @@ struct iphdr {
     uint32_t daddr;
 };
 
-/*
+/* 
 * IPv6 header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ipv6.h#L118
-*/
+*/ 
 struct ipv6hdr {
 #if defined(__BYTE_ORDER__) && __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
     uint8_t  version:4,
@@ -1056,7 +1054,7 @@ struct ipv6hdr {
     uint8_t  daddr[16];
 };
 
-/*
+/* 
 * UDP header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/udp.h#L23
 */
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
index 05220d120fb6f68..36422e1fcf667c9 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
@@ -19,7 +19,6 @@ Always transition from Monitoring mode to Mitigation (Enabled) mode. Do not swit
 When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Protection begins a learning period to observe existing connection state. Long-lived connections that pre-date this learning period may be dropped because they have no state in the tracker.
 
 **Recommended procedure:**
-
 1. Set to **Monitoring** mode for at least 4 hours (longer if your network has long-lived connections).
 2. Review the Monitoring mode logs in [Network Analytics](/analytics/network-analytics/) to confirm legitimate traffic patterns.
 3. Switch to **Mitigation (Enabled)** mode.
@@ -28,12 +27,12 @@ When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Pro
 
 Check the **Mitigation reason** field in the **Advanced TCP Protection** tab of [Network Analytics](/analytics/network-analytics/) and use the reason to identify the cause:
 
-| Mitigation reason                | Likely cause                                                                              | Action                                                                                                  |
-| -------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
-| **Not found**                    | Learning period was incomplete, or long-lived connections pre-date ATP activation         | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled)                                |
-| **Unexpected**                   | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
-| **Out of sequence**              | Packet reordering or packet loss in the network path                                      | Increase burst sensitivity threshold for the affected colo                                              |
-| Drops during traffic spikes only | Burst sensitivity threshold too low                                                       | Increase burst sensitivity (keep rate sensitivity the same)                                             |
+| Mitigation reason | Likely cause | Action |
+|---|---|---|
+| **Not found** | Learning period was incomplete, or long-lived connections pre-date ATP activation | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled) |
+| **Unexpected** | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
+| **Out of sequence** | Packet reordering or packet loss in the network path | Increase burst sensitivity threshold for the affected colo |
+| Drops during traffic spikes only | Burst sensitivity threshold too low | Increase burst sensitivity (keep rate sensitivity the same) |
 
 **Threshold tuning:** Adjust burst sensitivity before rate sensitivity. Burst sensitivity handles momentary spikes; rate sensitivity controls sustained packet rates.
 
diff --git a/src/content/docs/ddos-protection/best-practices/index.mdx b/src/content/docs/ddos-protection/best-practices/index.mdx
index d5e1f5b2afacde1..c90d2aafc0fd31d 100644
--- a/src/content/docs/ddos-protection/best-practices/index.mdx
+++ b/src/content/docs/ddos-protection/best-practices/index.mdx
@@ -9,9 +9,10 @@ sidebar:
     hideIndex: true
 head: []
 description: Learn about best practices for configuring Cloudflare's DDoS protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on DDoS protection best practices:
 
diff --git a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
index 07721304f2cfb3c..4be4546f04f6fa5 100644
--- a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
+++ b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
@@ -11,7 +11,7 @@ tags:
   - Caching
 ---
 
-import { GlossaryTooltip, Steps } from "~/components";
+import { GlossaryTooltip, Steps } from "~/components"
 
 Cloudflare's network automatically mitigates large <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">DDoS attacks</GlossaryTooltip>, but these attacks can still affect your application.
 
@@ -35,4 +35,4 @@ In addition to the steps for all customers, Cloudflare Enterprise customers subs
 
 ## Magic Transit customers
 
-In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
+In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/best-practices/third-party.mdx b/src/content/docs/ddos-protection/best-practices/third-party.mdx
index f7d646f767015f2..5e4e9065879bfc6 100644
--- a/src/content/docs/ddos-protection/best-practices/third-party.mdx
+++ b/src/content/docs/ddos-protection/best-practices/third-party.mdx
@@ -25,7 +25,7 @@ Therefore, it is recommended that you **use the [Cloudflare CDN](/cache/)**, whi
 - You perform DDoS filtering in the first point of contact from the Internet, which is a recommended best practice.
 
 :::caution[L3/4 DDoS mitigation accuracy]
-Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation.
+Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation. 
 
 When traffic is proxied through another vendor, the vendor's IP addresses are available to Cloudflare's network-layer protection systems rather than the true client IP addresses. This lack of visibility into the original source can lead to less effective automated mitigation and potential false positives.
 :::
diff --git a/src/content/docs/ddos-protection/botnet-threat-feed.mdx b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
index 8058f8d886012b1..ba3a7ca8409be2e 100644
--- a/src/content/docs/ddos-protection/botnet-threat-feed.mdx
+++ b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
@@ -14,9 +14,9 @@ learning_center:
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-botnet/
 tags:
   - REST API
----
 
-import { Steps, APIRequest, DashButton } from "~/components";
+---
+import { Steps, APIRequest, DashButton } from "~/components"
 
 The Cloudflare DDoS Botnet Threat Feed is a threat intelligence feed for service providers (SPs) such as hosting providers and Internet service providers (ISPs) that provides information about their own IP addresses that have participated in HTTP DDoS attacks as observed from Cloudflare's global network. The feed aims to help service providers stop the abuse and reduce DDoS attacks originating from within their networks.
 
@@ -85,7 +85,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
 - The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
 - Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
 - When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
-  :::
+:::
 
 To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:
 
@@ -103,23 +103,23 @@ Retrieves all the data in the botnet tracking database for a given ASN (currentl
 The provided `{asn}` must be affiliated with your account.
 
 <APIRequest
-	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
-	method="GET"
+  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"cidr": "127.0.0.1/32",
-			"date": "1970-01-01T00:00:00Z",
-			"offense_count": 10000
-		}
-		// ... other entries ...
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "cidr": "127.0.0.1/32",
+      "date": "1970-01-01T00:00:00Z",
+      "offense_count": 10000
+    },
+    // ... other entries ...
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -135,22 +135,22 @@ The provided `{asn}` must be affiliated with your account.
 `{date}` must be an ISO 8601-formatted date: `YYYY-MM-DD`. If no date is specified, the API responds with the data from the day before.
 
 <APIRequest
-	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
-	method="GET"
+  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"cidr": "127.0.0.1/32",
-			"date": "2024-05-05T00:00:00Z",
-			"offense_count": 10000
-		}
-		// ... other entries ...
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "cidr": "127.0.0.1/32",
+      "date": "2024-05-05T00:00:00Z",
+      "offense_count": 10000
+    },
+    // ... other entries ...
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
index 294386d75a7913f..23e89367c6df2b1 100644
--- a/src/content/docs/ddos-protection/get-started.mdx
+++ b/src/content/docs/ddos-protection/get-started.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 3
+
 ---
 
-import { Steps } from "~/components";
+import { Steps } from "~/components"
 
 ## Free, Pro, and Business plans
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
index da3c36e2cef5dc2..d811b5a27be035b 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
@@ -55,7 +55,7 @@ Cloudflare HTTP DDoS Protection can also initiate mitigation based on the origin
 This rule is available for zones on any plan.
 :::
 
-While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules:
+While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules: 
 
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by configuring the HTTP DDoS Attack Protection managed ruleset.
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
index d30b1f397074ef2..aa5cf2850cf749b 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
@@ -6,6 +6,7 @@ products:
   - ddos-protection
 sidebar:
   order: 5
+
 ---
 
 The DDoS Attack Protection managed rulesets provide comprehensive protection against a [variety of DDoS attacks](/ddos-protection/about/attack-coverage/) across L3/4 (network layer) and L7 (application layer) of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/).
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
index ec4a3407ca3c976..08ab036ae1868dc 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
@@ -54,7 +54,7 @@ While you can manually override a rule from `Log` to `Block`, consider the follo
 
 - The default action of a rule is decided during the testing period. Cloudflare may set its default action to **DDoS Dynamic**, which may use rate-limiting or a multi-step mitigation combination based on traffic factors. By applying a manual `Block` override, you prevent your configuration from automatically inheriting the more nuanced DDoS Dynamic action once it is released.
 
-If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action.
+If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action. 
 
 ## Availability
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
index 526d496f44f19d3..679aaba3f002a27 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Override examples for Network-layer DDoS Attack Protection
+
 ---
 
-import { Details, GlossaryTooltip, DashButton } from "~/components";
+import { Details, GlossaryTooltip, DashButton } from "~/components"
 
 ## Use cases
 
@@ -35,12 +36,11 @@ To avoid disruptions during initial deployment, you can create a _Log_ only –
 
 1. In the Cloudflare dashboard, go to the **Security rules** page.
 
-   <DashButton url="/?to=/:account/:zone/security/security-rules" />
-
+    <DashButton url="/?to=/:account/:zone/security/security-rules" />
 2. Go to the **DDoS protection** tab.
 3. On **HTTP DDoS attack protection**, select **Create override**.
 4. Set the **Scope** to _Apply to all incoming requests_.
 5. Under **Ruleset configuration**:
-   - Set the **Ruleset action** to _Log_.
-   - Set the **Ruleset sensitivity** to _Essentially Off_.
-6. Select **Save**.
+    - Set the **Ruleset action** to _Log_.
+    - Set the **Ruleset sensitivity** to _Essentially Off_. 
+6. Select **Save**. 
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/reference/alerts.mdx b/src/content/docs/ddos-protection/reference/alerts.mdx
index 2d58a70a27086ca..02ded106c58f5b9 100644
--- a/src/content/docs/ddos-protection/reference/alerts.mdx
+++ b/src/content/docs/ddos-protection/reference/alerts.mdx
@@ -108,4 +108,4 @@ To investigate a possibly ongoing attack, select **View Dashboard**. To go to th
 - In some cases, HTTP DDoS attack alerts will reference the attacked zone name instead of the attacked hostname. This occurs when the attack signature does not include information on the attacked hostname because it is not a strong indicator for identifying attack requests. For more information on attack signatures, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
 - DDoS alerts are currently only available for DDoS attacks detected and mitigated by the [DDoS managed rulesets](/ddos-protection/managed-rulesets/). Alerts are not yet available for DDoS attacks detected and mitigated by the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), the [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), or the [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) system.
 - You will not receive duplicate DDoS alerts within the same one-hour time frame.
-- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
+- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/reference/index.mdx b/src/content/docs/ddos-protection/reference/index.mdx
index 3ae60ce4bd017c0..1ffe418f0eceaf3 100644
--- a/src/content/docs/ddos-protection/reference/index.mdx
+++ b/src/content/docs/ddos-protection/reference/index.mdx
@@ -9,9 +9,10 @@ sidebar:
     hideIndex: true
 head: []
 description: Reference information for Cloudflare's DDoS protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Cloudflare DDoS protection:
 
diff --git a/src/content/docs/ddos-protection/reference/logs.mdx b/src/content/docs/ddos-protection/reference/logs.mdx
index 1bbc798b5e49584..f0d23899c38c060 100644
--- a/src/content/docs/ddos-protection/reference/logs.mdx
+++ b/src/content/docs/ddos-protection/reference/logs.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: DDoS logs
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Retrieve HTTP events using [Cloudflare Logs](/logs/) to integrate them into your <GlossaryTooltip term="SIEM">SIEM systems</GlossaryTooltip>.
 
diff --git a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
index 20dba8ba991db4e..187dff380ea2545 100644
--- a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
+++ b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 After onboarding to Cloudflare, you may want to simulate DDoS attacks against your Internet properties to test the protection, [reporting](/ddos-protection/reference/reports/), and [alerting](/ddos-protection/reference/alerts/) mechanisms. Follow the guidelines in this section to simulate a DDoS attack.
 
diff --git a/src/content/docs/dmarc-management/enable.mdx b/src/content/docs/dmarc-management/enable.mdx
index c38ef8ef703db1d..1eeb169d8368e0c 100644
--- a/src/content/docs/dmarc-management/enable.mdx
+++ b/src/content/docs/dmarc-management/enable.mdx
@@ -10,6 +10,7 @@ sidebar:
     text: Beta
 tags:
   - DNS
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -29,4 +30,4 @@ To enable DMARC Management:
    - If no DMARC record is found, Cloudflare will automatically invite you to add one that you can edit later. Select **Add** to continue.
    - If a DMARC record is found in your zone, Cloudflare will add another `rua` (Reporting URI for Aggregate data) entry to it. The `rua` tag specifies the URI (typically a `mailto:` address) where aggregate DMARC reports are sent. This additional entry uses a Cloudflare email address so that Cloudflare can receive and process DMARC reports on your behalf. Select **Next** to continue.
 
-DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
+DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
\ No newline at end of file
diff --git a/src/content/docs/dmarc-management/security-records.mdx b/src/content/docs/dmarc-management/security-records.mdx
index df2912e19e4d6cc..2ec513fecf908f2 100644
--- a/src/content/docs/dmarc-management/security-records.mdx
+++ b/src/content/docs/dmarc-management/security-records.mdx
@@ -29,4 +29,4 @@ To set up email security records:
 
 ## Edit or delete records
 
-Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
+Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
\ No newline at end of file
diff --git a/src/content/docs/dmarc-management/statistics.mdx b/src/content/docs/dmarc-management/statistics.mdx
index b9186d28b90635d..58a5e6ea804a49b 100644
--- a/src/content/docs/dmarc-management/statistics.mdx
+++ b/src/content/docs/dmarc-management/statistics.mdx
@@ -11,6 +11,7 @@ head:
     content: Review DMARC statistics
 tags:
   - DNS
+
 ---
 
 DMARC Management (beta) allows you to review whether emails sent on your behalf passed or failed DMARC, SPF, and DKIM authentication checks.
diff --git a/src/content/docs/dns/additional-options/index.mdx b/src/content/docs/dns/additional-options/index.mdx
index 2c2a6572e2ac236..66b93896ae59062 100644
--- a/src/content/docs/dns/additional-options/index.mdx
+++ b/src/content/docs/dns/additional-options/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Beyond [setting up your zone](/dns/zone-setups/) and [updating your DNS records](/dns/manage-dns-records/), you may want to customize the following settings in Cloudflare DNS:
 
diff --git a/src/content/docs/dns/changelog.mdx b/src/content/docs/dns/changelog.mdx
index 3c688d1cb2da69d..b1163dea5558b84 100644
--- a/src/content/docs/dns/changelog.mdx
+++ b/src/content/docs/dns/changelog.mdx
@@ -12,7 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelogs/dns/. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="dns" />
+<ProductChangelog product="dns"/>
 
 ## 2025-01-27
 
@@ -26,11 +26,11 @@ Records returned by the API will no longer contain the `zone_id` and `zone_name`
 
 When creating [TXT records](/dns/manage-dns-records/reference/dns-record-types/#txt) via the dashboard you will now find:
 
-- Field validation errors if double quotes `"` are added inconsistently.
-- Automatically quoted TXT content upon save if no quotes exist in the record content field.
+* Field validation errors if double quotes `"` are added inconsistently.
+* Automatically quoted TXT content upon save if no quotes exist in the record content field.
 
 ## 2024-10-07
 
 **API support for per-record CNAME flattening**
 
-Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
+Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
\ No newline at end of file
diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx
index 521021c63c3011d..918f0fcc6932086 100644
--- a/src/content/docs/dns/cname-flattening/index.mdx
+++ b/src/content/docs/dns/cname-flattening/index.mdx
@@ -31,4 +31,4 @@ For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), re
 
 - CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
 - CNAME to a different Cloudflare account is prohibited and will result in [Error 1014: CNAME Cross-User Banned](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/)
-- <Render file="cname-flattening-callout" product="dns" />
+- <Render file="cname-flattening-callout" product="dns" />
\ No newline at end of file
diff --git a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
index 22b36e298b9f3bf..675a692b4527d82 100644
--- a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
+++ b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
@@ -11,13 +11,7 @@ head:
     content: Set up CNAME flattening
 ---
 
-import {
-	Render,
-	TabItem,
-	Tabs,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components";
 
 :::note
 
diff --git a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
index c961134f600f565..3b579df96996538 100644
--- a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
+++ b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Protect against random prefix attacks
+
 ---
 
 import { APIRequest } from "~/components";
@@ -22,10 +23,10 @@ In order to enable automatic mitigation of [random prefix attacks](/dns/dns-fire
    	path="/accounts/{account_id}/dns_firewall/{dns_firewall_id}"
    	method="PATCH"
    	json={{
-   		attack_mitigation: {
-   			enabled: true,
-   			only_when_upstream_unhealthy: true,
-   		},
+      "attack_mitigation": {
+        "enabled": true,
+        "only_when_upstream_unhealthy": true,
+      }
    	}}
    />
 
@@ -33,6 +34,8 @@ Once you receive a `200` success response from the API, queries identified as be
 
 :::note
 
+
 If you do not specify otherwise in your API call, Cloudflare automatically sets the `"only_when_upstream_unhealthy"` parameter to true, which means that Cloudflare will only mitigate attacks when we detect that the upstream is unresponsive (possibly as a result of an attack). This setting can also be changed via the API, using a request similar to the ones shown above.
 
+
 :::
diff --git a/src/content/docs/dns/dnssec/dnssec-states.mdx b/src/content/docs/dns/dnssec/dnssec-states.mdx
index 381c0a152b40f23..5b40526a38a6545 100644
--- a/src/content/docs/dns/dnssec/dnssec-states.mdx
+++ b/src/content/docs/dns/dnssec/dnssec-states.mdx
@@ -6,16 +6,17 @@ products:
 title: DNSSEC states
 sidebar:
   order: 4
+
 ---
 
 This page describes different DNSSEC states and how they relate to the responses you get from the [DNSSEC details API endpoint](/api/resources/dns/subresources/dnssec/methods/get/).
 
-| State            | API response                                                     | Description                                                                                                                                                                                 |
-| ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                                   |
-| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                           |
-| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                                      |
-| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                                  |
+| State            | API response                                                     | Description                                                                                                                                                                       |
+| ---------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                         |
+| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                 |
+| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                            |
+| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                        |
 | Deleted          | `"status":"disabled"`<br /> `"modified_on": null`                | DNSSEC has never been enabled for the zone or DNSSEC has been disabled and then deleted using the [Delete DNSSEC records endpoint](/api/resources/dns/subresources/dnssec/methods/delete/). |
 
 :::caution
diff --git a/src/content/docs/dns/dnssec/enable-nsec3.mdx b/src/content/docs/dns/dnssec/enable-nsec3.mdx
index adc9d72f7a3971a..710497fda89108a 100644
--- a/src/content/docs/dns/dnssec/enable-nsec3.mdx
+++ b/src/content/docs/dns/dnssec/enable-nsec3.mdx
@@ -22,8 +22,8 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met
 	path="/zones/{zone_id}/dnssec"
 	method="PATCH"
 	json={{
-		dnssec_use_nsec3: true,
-		status: "active",
+		"dnssec_use_nsec3": true,
+		"status": "active"
 	}}
 />
 
diff --git a/src/content/docs/dns/dnssec/index.mdx b/src/content/docs/dns/dnssec/index.mdx
index d58d3d633a1fcfb..a4f8af210e23313 100644
--- a/src/content/docs/dns/dnssec/index.mdx
+++ b/src/content/docs/dns/dnssec/index.mdx
@@ -6,13 +6,14 @@ products:
 title: DNSSEC
 sidebar:
   order: 8
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="dnssec-definition" product="dns" />
 
----
+***
 
 ## Disable DNSSEC
 
@@ -20,7 +21,7 @@ import { Render } from "~/components";
 
 <Render file="dnssec-enabled-migration" product="dns" />
 
----
+***
 
 ## Enable DNSSEC
 
@@ -36,7 +37,7 @@ When you enable DNSSEC, Cloudflare signs your zone, publishes your public signin
 
 <Render file="dnssec-auto-add" product="dns" />
 
----
+***
 
 ## Other DNSSEC setup options
 
@@ -44,14 +45,14 @@ If you are using Cloudflare as your Secondary DNS provider and want to configure
 
 If you want to set up DNSSEC on a subdomain zone, refer to [Subdomain DNSSEC](/dns/zone-setups/subdomain-setup/dnssec/).
 
----
+***
 
 ## Limitations
 
 If your registrar does not support DNSSEC with Cloudflare's preferred cipher choice (Algorithm 13), you have several options:
 
-- Contact your registrar to ask for DNSSEC with modern encryption.
-- Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
-- File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
+* Contact your registrar to ask for DNSSEC with modern encryption.
+* Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
+* File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
 
-If your top-level domain does not support DNSSEC with Algorithm 13 (also known as _ECDSA Curve P-256 with SHA-256_), [contact that top-level domain](https://www.iana.org/domains/root/db).
+If your top-level domain does not support DNSSEC with Algorithm 13 (also known as *ECDSA Curve P-256 with SHA-256*), [contact that top-level domain](https://www.iana.org/domains/root/db).
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
index 1fd48842270e6c8..dea0d2d6371ecdd 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: About multi-signer DNSSEC
+
 ---
 
 Multi-signer DNSSEC consists of two models that allow different authoritative DNS providers to serve the same zone and have DNSSEC enabled at the same time.
@@ -19,6 +20,7 @@ You can [set up multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/) usi
 
 ## How it works
 
+
 :::note
 This is a simplified explanation to give you context and clarify what is involved in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/setup/). For technical details refer to [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html). To read more about DNSSEC, refer to [How DNSSEC works](https://www.cloudflare.com/dns/dnssec/how-dnssec-works/).
 :::
@@ -93,4 +95,4 @@ Multi-signer DNSSEC involves coordinating cryptographic keys across multiple pro
 1. Verify that both providers have each other's ZSKs in their DNSKEY RRsets.
 2. Confirm that both DS records are present at the registrar.
 3. Use DNSSEC validation tools to test resolution from both providers.
-4. Monitor for validation errors during the transition period.
+4. Monitor for validation errors during the transition period.
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
index b2c476f53cf14a9..99825944a7ae3ae 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
@@ -173,4 +173,4 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
 
 1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
 
-2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
+2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/validation-and-key-management.mdx b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
index 307aec3cbfdc7e4..83711e5a34916e7 100644
--- a/src/content/docs/dns/dnssec/validation-and-key-management.mdx
+++ b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
@@ -30,9 +30,9 @@ This is why you cannot simply keep your existing DS record when migrating to Clo
 
 When you enable DNSSEC, Cloudflare automatically publishes **CDS** (Child Delegation Signer) and **CDNSKEY** (Child DNSKEY) records in your zone. These records automate the chain of trust management between your domain and the Top-Level Domain registry.
 
-| Record      | Purpose                | Contents                                                                           |
-| ----------- | ---------------------- | ---------------------------------------------------------------------------------- |
-| **CDS**     | High-level instruction | A hashed version of the public key (same data as a DS record)                      |
+| Record | Purpose | Contents |
+| --- | --- | --- |
+| **CDS** | High-level instruction | A hashed version of the public key (same data as a DS record) |
 | **CDNSKEY** | Public key instruction | The full public Key Signing Key (KSK) for the parent to generate its own DS record |
 
 Registrars that support [RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html) periodically scan your domain for these records and automatically update the DS record at the registry level. This eliminates manual DS record management and ensures seamless key rollovers.
@@ -46,4 +46,4 @@ Not all registrars support automatic CDS/CDNSKEY scanning. If your registrar doe
 ## DNSKEY flags
 
 - **ZSKs (Zone Signing Keys)**: flag `256`
-- **KSKs (Key Signing Keys)**: flag `257`
+- **KSKs (Key Signing Keys)**: flag `257`
\ No newline at end of file
diff --git a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
index 37222616afae066..266d6dcc5a7d28d 100644
--- a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
+++ b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
@@ -6,6 +6,7 @@ products:
 title: DNSSEC keys
 sidebar:
   order: 5
+
 ---
 
 With [Foundation DNS](/dns/foundation-dns/), you can request that the ZSK/KSK pair that is used for [DNSSEC](/dns/dnssec/) is unique to your Cloudflare account. To opt in to this feature, contact your account team.
@@ -16,4 +17,4 @@ All zones within your Cloudflare account - regardless of using [standard](/dns/n
 
 For more background information, refer to [How DNSSEC works](https://www.cloudflare.com/learning/dns/dnssec/how-dnssec-works/).
 
-For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
+For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
\ No newline at end of file
diff --git a/src/content/docs/dns/foundation-dns/index.mdx b/src/content/docs/dns/foundation-dns/index.mdx
index bb4381b3a49156f..0c60c2a7c820aca 100644
--- a/src/content/docs/dns/foundation-dns/index.mdx
+++ b/src/content/docs/dns/foundation-dns/index.mdx
@@ -6,21 +6,22 @@ products:
 title: Foundation DNS
 sidebar:
   order: 4
+
 ---
 
 Foundation DNS is the Cloudflare DNS offering for enterprise customers.
 
 With Foundation DNS, you get access to increased reliability, security, and insights. Features include the following:
 
-- [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
-  - Strategically distributed IPs to enhance resiliency
-  - Reduced exposure to incidents or software regression
-  - More consistent nameserver assignment
-- [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
-- Additional DNS settings, including:
-  - [Zone defaults](/dns/additional-options/dns-zone-defaults/)
-  - [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
-  - Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
+* [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
+  * Strategically distributed IPs to enhance resiliency
+  * Reduced exposure to incidents or software regression
+  * More consistent nameserver assignment
+* [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
+* Additional DNS settings, including:
+  * [Zone defaults](/dns/additional-options/dns-zone-defaults/)
+  * [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
+  * Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
 
 ## Availability
 
@@ -32,5 +33,5 @@ Both advanced nameservers and unique ZSK/KSK are opt-in configurations. Refer to
 
 ## Related resources
 
-- [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
-- [Product page](https://www.cloudflare.com/dns/foundation-dns/)
+* [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
+* [Product page](https://www.cloudflare.com/dns/foundation-dns/)
diff --git a/src/content/docs/dns/glossary.mdx b/src/content/docs/dns/glossary.mdx
index 6b99f261ae66987..c7e9390c51ff273 100644
--- a/src/content/docs/dns/glossary.mdx
+++ b/src/content/docs/dns/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 30
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's DNS documentation.
 
diff --git a/src/content/docs/dns/internal-dns/analytics.mdx b/src/content/docs/dns/internal-dns/analytics.mdx
index b1608c69e81f1a0..af54b9d66ef1e04 100644
--- a/src/content/docs/dns/internal-dns/analytics.mdx
+++ b/src/content/docs/dns/internal-dns/analytics.mdx
@@ -28,4 +28,4 @@ The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to c
 
 Leverage Logpush jobs for [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation.
 
-You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
+You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
index 304c2d379c31eef..115c06fb29de7c0 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
@@ -6,9 +6,10 @@ products:
 title: Create subdomain records
 sidebar:
   order: 4
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="create-subdomain-record" product="dns" />
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
index 6cfa20495a46cc1..bcaca8ad13ed17d 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
@@ -6,23 +6,24 @@ products:
 title: Set up email records
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 There are three reasons to set up email records for your domain:
 
-- To make sure your domain can [receive email](#receive-email).
-- To make sure your domain can [send and receive email](#send-and-receive-email).
-- To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
+* To make sure your domain can [receive email](#receive-email).
+* To make sure your domain can [send and receive email](#send-and-receive-email).
+* To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
 
 The exact values for your DNS mail records depend on your email provider. If you have issues, review the [Troubleshooting](/dns/troubleshooting/email-issues/) and contact your email service provider to confirm your DNS records are correct.
 
----
+***
 
 <Render file="add-mx-records" product="dns" />
 
----
+***
 
 ## Prevent domain spoofing
 
@@ -34,4 +35,4 @@ Refer to [Security records](/dmarc-management/security-records/) to learn how to
 
 ## Proxy SMTP traffic
 
-By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
+By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/index.mdx b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
index 8ec9e0fc39b8c4d..f0d1c4dd9c45127 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
@@ -11,9 +11,10 @@ head:
   - tag: title
     content: DNS records - How to
 description: Learn how to use Cloudflare DNS to manage your DNS records.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following resources for more information about creating and maintaining DNS records:
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
index 44177c0cbae3d1a..e8f26982405820e 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
@@ -6,6 +6,7 @@ products:
 title: Dynamically update DNS records
 sidebar:
   order: 13
+
 ---
 
 Most Internet service providers and some hosting providers dynamically update their customer's IP addresses. If this situation applies to you, you need an automated solution to dynamically update your DNS records in Cloudflare.
@@ -16,4 +17,4 @@ Create a script to monitor IP address changes and then have that script push cha
 
 ## ddclient
 
-[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
+[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
index 980e98757c3145e..9768ac45ceeda63 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
@@ -6,6 +6,7 @@ products:
 title: Round-robin DNS
 sidebar:
   order: 18
+
 ---
 
 To randomly distribute traffic across multiple servers, set up multiple DNS `A` or `AAAA` records for the same hostname.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
index 886b037b118a29a..d21e31b5faedd36 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
@@ -7,9 +7,10 @@ source: https://support.cloudflare.com/hc/en-us/articles/360021357131-Delegating
 title: Delegate subdomains
 sidebar:
   order: 20
+
 ---
 
-import { FeatureTable, DashButton, Render } from "~/components";
+import { FeatureTable, DashButton, Render } from "~/components"
 
 Subdomain delegation allows different individuals, teams, or organizations to manage different subdomains of a site.
 
@@ -29,7 +30,7 @@ Cloudflare's CDN and security services are not applied to delegated subdomains.
 
 <FeatureTable id="dns.subdomain_delegation" />
 
----
+***
 
 ## Delegate a subdomain (outgoing)
 
@@ -42,12 +43,12 @@ To delegate a subdomain such as `blog.example.com`, tell DNS resolvers where to
    <DashButton url="/?to=/:account/:zone/dns/records" />
 
 4. Create `NS` records for the subdomain. For example:
-   - `blog.example.com NS ns1.externalhost.com`
-   - `blog.example.com NS ns2.externalhost.com`
-   - `blog.example.com NS ns3.externalhost.com`
-     :::note
-     The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
-     :::
+   * `blog.example.com NS ns1.externalhost.com`
+   * `blog.example.com NS ns2.externalhost.com`
+   * `blog.example.com NS ns3.externalhost.com`
+   :::note
+   The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
+   :::
 5. (Optional) If the delegated nameserver has DNSSEC enabled, [add the `DS` record](/dns/dnssec/#1-activate-dnssec-in-cloudflare) in Cloudflare.
 
 ### Limits
diff --git a/src/content/docs/dns/manage-dns-records/reference/index.mdx b/src/content/docs/dns/manage-dns-records/reference/index.mdx
index 1bbba02e42aadf2..435c9bbea21f1f9 100644
--- a/src/content/docs/dns/manage-dns-records/reference/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Reference — DNS records
 description: Check information about record types, status and additional options.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
index 67e4399d03b9c75..99740688e33b318 100644
--- a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: DNS record comments and tags
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 Use DNS record comments and tags to categorize and clarify the purpose of DNS records within Cloudflare.
 
@@ -19,17 +20,19 @@ Comments provide a unique descriptions for specific records, whereas tags group
 
 These attributes are particularly useful when:
 
-- Multiple teams are managing DNS records within the same zone.
-- Your zone contains a large number of DNS records.
-- You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
+* Multiple teams are managing DNS records within the same zone.
+* Your zone contains a large number of DNS records.
+* You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
 
 :::note
 
+
 The information in record attributes will not impact DNS record resolution or propagation timing and is only meant for your private reference. This information is only visible to [members](/fundamentals/manage-members/manage/) of your Cloudflare account and is not visible publicly.
 
+
 :::
 
----
+***
 
 ## Availability
 
@@ -43,7 +46,7 @@ Comments and tags are only supported for [primary zones (full setup)](/dns/zone-
 
 <FeatureTable id="dns.record_tags" />
 
----
+***
 
 ## Add or edit record attributes
 
@@ -53,7 +56,7 @@ You can also add or edit attributes by [exporting and re-importing](/dns/manage-
 
 When exporting and importing, special tags starting by `cf-` allow you to control specific Cloudflare configurations. On export, these tags are automatically added to reflect the current configuration for each record on your zone. Refer to [reserved cf- tags](/dns/manage-dns-records/how-to/import-and-export/#reserved-cf--tags) for details.
 
----
+***
 
 ## Reference
 
diff --git a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
index 3f25313a41b3cd5..41114679b9e211e 100644
--- a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
@@ -6,6 +6,7 @@ products:
 title: Time to Live (TTL)
 sidebar:
   order: 3
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -32,4 +33,4 @@ A TTL of **Auto** is set to 300 seconds (five minutes).
 
 ## Nameserver TTL
 
-[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
+[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
index 4df29d02c4d8f19..2abc708b8e738ad 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
@@ -29,6 +29,7 @@ When your zone has DNS records that are not proxied, the **DNS Records** page di
 
 `Proxying is required for most security and performance features. Set your DNS records to proxied by clicking "Edit" in the table below, to benefit from DDoS protection, security rules, caching, and more.`
 
+
 Individual DNS records may also display warnings. The specific message depends on whether the record can be proxied.
 
 ---
@@ -50,4 +51,4 @@ When a DNS-only record points to the same origin server as a proxied record, a `
 To mitigate this risk:
 
 - Analyze the impact of hosting multiple services on the same origin server in cases when you cannot avoid having DNS-only records.
-- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
+- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
index 6dc331f5f84f29c..104ad57575d8b7f 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
@@ -11,10 +11,11 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS records
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
 
-- [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
+* [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
diff --git a/src/content/docs/dns/nameservers/advanced-nameservers.mdx b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
index e545226613700b5..6138cff878b675f 100644
--- a/src/content/docs/dns/nameservers/advanced-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
@@ -7,4 +7,5 @@ title: Advanced nameservers
 external_link: /dns/foundation-dns/advanced-nameservers/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
index d6fd863c76c52cf..c9268ed929c445c 100644
--- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
@@ -56,7 +56,6 @@ The next step depends on whether you are using [Cloudflare Registrar](/registrar
 
 - If you are using Cloudflare Registrar for your domain, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to add the custom nameservers and IP addresses as glue records to the domain.
 - If you are not using Cloudflare Registrar for your domain, add the zone custom nameservers at your registrar as your authoritative nameservers and as glue (A and AAAA) records ([RFC 1912](https://www.rfc-editor.org/rfc/rfc1912.html)). If you do not add these records, DNS lookups for your domain will fail.
-
 ### Secondary zones
 
 If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), you can still set up zone custom nameservers. After following the [steps above](/dns/nameservers/custom-nameservers/zone-custom-nameservers/#primary-zones-full-setup) to create zone custom nameservers, do the following:
diff --git a/src/content/docs/dns/private-origins/index.mdx b/src/content/docs/dns/private-origins/index.mdx
index 49be787e2f6008e..8398f269855ab93 100644
--- a/src/content/docs/dns/private-origins/index.mdx
+++ b/src/content/docs/dns/private-origins/index.mdx
@@ -23,8 +23,7 @@ import {
 } from "~/components";
 
 <Description>
-	Proxy HTTP/HTTPS traffic from public hostnames to origins in your private
-	network.
+Proxy HTTP/HTTPS traffic from public hostnames to origins in your private network.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/dns/reference/all-features.mdx b/src/content/docs/dns/reference/all-features.mdx
index 8ef860d82833097..9186a4860de7efa 100644
--- a/src/content/docs/dns/reference/all-features.mdx
+++ b/src/content/docs/dns/reference/all-features.mdx
@@ -7,9 +7,10 @@ sidebar:
   order: 4
 head: []
 description: Review information on all Cloudflare DNS features and their availability.
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
diff --git a/src/content/docs/dns/reference/analytics-mcp-server.mdx b/src/content/docs/dns/reference/analytics-mcp-server.mdx
index 6d120789cebde25..de1faf7d51e1b2b 100644
--- a/src/content/docs/dns/reference/analytics-mcp-server.mdx
+++ b/src/content/docs/dns/reference/analytics-mcp-server.mdx
@@ -7,4 +7,5 @@ title: Analytics MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dns-analytics
 sidebar:
   order: 90
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/best-practices.mdx b/src/content/docs/dns/reference/best-practices.mdx
index 9ef1525a0d2fb08..c4fe1210a6d1a7e 100644
--- a/src/content/docs/dns/reference/best-practices.mdx
+++ b/src/content/docs/dns/reference/best-practices.mdx
@@ -7,4 +7,5 @@ title: Migrate DNS from BIND
 external_link: /learning-paths/dns-best-practices/concepts/
 sidebar:
   order: 4
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/domain-connect.mdx b/src/content/docs/dns/reference/domain-connect.mdx
index fa4d6d8026995b0..06e2489b08294a7 100644
--- a/src/content/docs/dns/reference/domain-connect.mdx
+++ b/src/content/docs/dns/reference/domain-connect.mdx
@@ -23,8 +23,8 @@ In practice, this means that when a user that owns `example.com` and has Cloudfl
 
 ### Before you begin
 
-- Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
-- Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
+* Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
+* Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
 
 ### 1. Add templates to the repository
 
@@ -32,12 +32,12 @@ Domain Connect templates are published and maintained on a GitHub repository.
 
 1. Create a fork of the [templates repository](https://github.com/Domain-Connect/Templates).
 2. Add your template. You can create a copy of one of the existing templates and edit it according to your needs.
-   - Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
-     :::note
-     Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
-     :::
-   - If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
-   - You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
+   * Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
+	 :::note
+	 Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
+	 :::
+   * If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
+   * You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
 3. Make sure you follow the naming format defined by Domain Connect: `<providerId>.<serviceId>.json`.
 
 :::note[Tip]
@@ -155,4 +155,4 @@ The most common issues after template onboarding are validation errors, typicall
 
 You can fix these by republishing the signature, using tools such as the one provided by [Domain Connect](https://exampleservice.domainconnect.org/sig). Additionally, you can test signature validation with this [public key debug tool](https://github.com/kerolasa/dc-debug-pubkey).
 
-[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
+[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/index.mdx b/src/content/docs/dns/reference/index.mdx
index 51f81d1b1b3aeac..e12d2e5c169f815 100644
--- a/src/content/docs/dns/reference/index.mdx
+++ b/src/content/docs/dns/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/reference/recommended-third-party-tools.mdx b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
index 61e3bd775e91b13..3382d1ddc811487 100644
--- a/src/content/docs/dns/reference/recommended-third-party-tools.mdx
+++ b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
@@ -7,14 +7,15 @@ sidebar:
   order: 3
 head: []
 description: List of recommended third-party tools for DNS testing and troubleshooting.
+
 ---
 
 You can use the third-party tools listed below to test and troubleshoot DNS settings.
 
-- [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
+* [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
 
-- [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
+* [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
 
-- [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
+* [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
 
-- [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
+* [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
diff --git a/src/content/docs/dns/troubleshooting/email-issues.mdx b/src/content/docs/dns/troubleshooting/email-issues.mdx
index 291bb8f2240fef4..417ecfa92fdf7e1 100644
--- a/src/content/docs/dns/troubleshooting/email-issues.mdx
+++ b/src/content/docs/dns/troubleshooting/email-issues.mdx
@@ -85,12 +85,12 @@ If you are not sure whether the DNS content itself is correct, compare it with t
 
 Common examples include:
 
-| Provider         | MX records                                                                                                                                                                           | SPF record                                       |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
-| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all`            |
-| Microsoft 365    | `<your-domain>.mail.protection.outlook.com` (priority `0`)                                                                                                                           | `v=spf1 include:spf.protection.outlook.com -all` |
-| iCloud Mail      | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`)                                                                                                                    | `v=spf1 include:icloud.com ~all`                 |
-| Mailgun          | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`)                                                                                                                              | `v=spf1 include:mailgun.org ~all`                |
+| Provider | MX records | SPF record |
+| --- | --- | --- |
+| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all` |
+| Microsoft 365 | `<your-domain>.mail.protection.outlook.com` (priority `0`) | `v=spf1 include:spf.protection.outlook.com -all` |
+| iCloud Mail | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`) | `v=spf1 include:icloud.com ~all` |
+| Mailgun | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`) | `v=spf1 include:mailgun.org ~all` |
 
 Always confirm the exact values with your provider before making changes.
 
diff --git a/src/content/docs/dns/troubleshooting/index.mdx b/src/content/docs/dns/troubleshooting/index.mdx
index b616c9d14356e9f..2ad611b0f95694a 100644
--- a/src/content/docs/dns/troubleshooting/index.mdx
+++ b/src/content/docs/dns/troubleshooting/index.mdx
@@ -9,13 +9,8 @@ sidebar:
   label: Full resources list
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 The following topics are useful for troubleshooting DNS issues.
 
-<ResourcesBySelector
-	directory="dns"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="dns" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
index 1b87486546a0e69..96a01af7dd298db 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
@@ -11,13 +11,7 @@ description: >-
   If you initially configured a full setup you can later convert your zone to use incoming zone transfers (Cloudflare as secondary).
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
 
 If you initially configured a [primary setup (full)](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/).
 
@@ -43,14 +37,14 @@ Follow the steps below to achieve this conversion.
    <Render file="tsig-definition" product="dns" />
 
    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
-   
-      <Render file="tsig-create-dash" product="dns" />
-   
-      </TabItem> <TabItem label="API">
-   
-      <Render file="tsig-create-api" product="dns" />
-   
-      </TabItem> </Tabs>
+
+   <Render file="tsig-create-dash" product="dns" />
+
+   </TabItem> <TabItem label="API">
+
+   <Render file="tsig-create-api" product="dns" />
+
+   </TabItem> </Tabs>
 
 3. Create a peer server.
 
@@ -64,8 +58,8 @@ Follow the steps below to achieve this conversion.
    <DashButton url="/?to=/:account/:zone/dns/settings" />
 
 3. Select **Manage linked peers** under **DNS Zone Transfers**.
-4. Link the peer server you created in the previous steps and select **Save**.
-5. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
-6. Confirm the DNS records are transferring as expected.
-7. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
-8. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
+3. Link the peer server you created in the previous steps and select **Save**.
+4. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
+5. Confirm the DNS records are transferring as expected.
+6. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
+7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
index 6c458149ea4d45b..f25552f8df2c42b 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
@@ -66,7 +66,7 @@ If you are counting on Universal SSL certificates to cover your website or appli
 :::
 
 Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page
-and add the DS record to your registrar.
+ and add the DS record to your registrar.
 
 Once all the DNS TTLs expire, all your DNS queries will be answered by the Cloudflare global network.
 
diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx
index 42226cfb7ad094d..04bc2c37ce4a3a5 100644
--- a/src/content/docs/dns/zone-setups/conversions/index.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/index.mdx
@@ -15,4 +15,4 @@ import { DirectoryListing } from "~/components";
 
 You can perform the following DNS setup conversions:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/full-setup/index.mdx b/src/content/docs/dns/zone-setups/full-setup/index.mdx
index f92648b37069542..6a5717e76167fdf 100644
--- a/src/content/docs/dns/zone-setups/full-setup/index.mdx
+++ b/src/content/docs/dns/zone-setups/full-setup/index.mdx
@@ -19,4 +19,4 @@ For this to work, you must go through a few steps that involve not only Cloudfla
 
 ## Availability
 
-<FeatureTable id="dns.full_setup" />
+<FeatureTable id="dns.full_setup" />
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
index 1697f7240a301ac..45952ff6ebee99e 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: DNS resolution in partial zones
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 When you have a partial zone (<GlossaryTooltip term="CNAME setup" link="/dns/zone-setups/partial-setup/">CNAME setup</GlossaryTooltip>), Cloudflare handles DNS records a bit differently from primary zones (full setup) in order to internally resolve the origin server where proxied HTTP requests are sent to.
 
@@ -61,7 +62,7 @@ When you avoid this situation - meaning you do not have the **target** of the CN
       end
 ```
 
----
+***
 
 ## Records pointing to a partial zone within the same account
 
@@ -114,4 +115,4 @@ If such setup is in place, the subdomain (`www.partialzone.com` in this example)
       subgraph Authoritative DNS
       C
       end
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
index 627350007665712..0afa82eb5bc7ecb 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
@@ -13,15 +13,7 @@ description: >-
   A CNAME setup (also known as partial) allows you to use Cloudflare's reverse proxy while maintaining your primary and authoritative DNS provider.
 ---
 
-import {
-	Details,
-	Render,
-	GlossaryTooltip,
-	Steps,
-	Tabs,
-	TabItem,
-	APIRequest,
-} from "~/components";
+import { Details, Render, GlossaryTooltip, Steps, Tabs, TabItem, APIRequest } from "~/components";
 
 <Render file="partial-setup-definition" product="dns" />
 
@@ -48,6 +40,7 @@ A CNAME setup (partial) is only available to customers on a Business or Enterpri
 
 ## 1. Convert your zone and review DNS records
 
+
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 :::caution[Make sure you have the correct plan]
diff --git a/src/content/docs/dns/zone-setups/reference/domain-status.mdx b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
index 9541eaa1de5c4f2..2d26b5684dba1b2 100644
--- a/src/content/docs/dns/zone-setups/reference/domain-status.mdx
+++ b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
@@ -69,11 +69,11 @@ After you add your domain, Cloudflare performs checks on a schedule to confirm y
 
 The activation check behavior depends on your zone setup:
 
-| Zone setup                                                                                                                                                                                                                      | Activation requirement                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                      | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/) | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.           |
-| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                        | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                       |
+| Zone setup                                                                                                                                                                                                                          | Activation requirement                                                                                                                            |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                           | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)      | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.         |
+| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                             | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                     |
 
 ### Expected behavior for different plans
 
diff --git a/src/content/docs/dns/zone-setups/reference/index.mdx b/src/content/docs/dns/zone-setups/reference/index.mdx
index 6185d7acd7149ea..a6c71ff65f2b7a8 100644
--- a/src/content/docs/dns/zone-setups/reference/index.mdx
+++ b/src/content/docs/dns/zone-setups/reference/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Reference — DNS zone setups
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
index 363f7e2bbee2c84..58cb7e6b8986b33 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Migrate subdomain to a new account
+
 ---
 
 When using a [subdomain setup](/dns/zone-setups/subdomain-setup/), you can have your subdomain as a separate zone within the same account as the parent domain or within a different account.
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
index 1a8c8cfae71d112..7523187ca70b247 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
@@ -9,14 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Rollback subdomain setup
+
 ---
 
 Refer to the following process to understand how you can rollback a [subdomain setup](/dns/zone-setups/subdomain-setup/) and recreate the corresponding subdomain DNS records in an existing parent zone within Cloudflare.
 
 ## Before you begin
 
-- This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
-- In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
+* This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
+* In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
 
 :::caution[Important]
 
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
index 8cbfcf5e76c38b0..ed7910947587eae 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
@@ -9,14 +9,17 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on full setup
+
 ---
 
 When the parent zone is using a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
 :::note
 
+
 The following steps are similar if your Cloudflare parent zone is in a secondary setup, with the only difference that you will use your external primary DNS provider to make any necessary adjustments to DNS records.
 
+
 :::
 
 ## Subdomain does not exist
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
index 0ae18341ccfb5ac..46a0cf3ae1e1d99 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on partial setup
+
 ---
 
-import { Details, TabItem, Tabs } from "~/components";
+import { Details, TabItem, Tabs } from "~/components"
 
 When the parent zone is using a [CNAME setup (partial)](/dns/zone-setups/partial-setup/)[^2], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
diff --git a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
index 485e9d9090a0bfb..d7b45d34cc6ea33 100644
--- a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
+++ b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS setups
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
index 6c1cdba3b2785b7..ee6a63ef200265e 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
@@ -17,7 +17,7 @@ When you [make edits](/dns/manage-dns-records/how-to/create-dns-records/) to Clo
 
 ## How to
 
-- [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
+* [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
index 284707a6b0416f1..854dcfad6b2831a 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
@@ -10,6 +10,7 @@ sidebar:
 
 Consider the sections below to understand the expected behaviors, depending on DNS record type and proxied status.
 
+
 ## Proxied records
 
 For each [proxied DNS record](/dns/proxy-status/) in your zone, Cloudflare will transfer out two `A` and two `AAAA` records.
@@ -41,4 +42,4 @@ The following records are not transferred out when you use Cloudflare as primary
 
 :::note
 Proxied Load Balancing records are transferred as explained in [Proxied records](#proxied-records).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
index f5191d5c420f6ce..bfd1df6c824f6a5 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Secondary DNS
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your secondary DNS.
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
index 2bb69c6bc3e6288..463cb6408c5cbb2 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
@@ -23,8 +23,8 @@ B & C <--DNS lookups--> D[Resolver] <--DNS lookups--> E((User))
 
 ## How to
 
-- [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
-- Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
+* [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
+* Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
index b8a0e6712109252..a21202b1749130a 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
@@ -81,4 +81,4 @@ Once you create a CNAME record at the apex, existing A or AAAA records on the zo
 
 ## Verify that your records are proxied
 
-Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
+Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/api/alarms.mdx b/src/content/docs/durable-objects/api/alarms.mdx
index fa9a03af7538bea..4d576fbe8cd6cb3 100644
--- a/src/content/docs/durable-objects/api/alarms.mdx
+++ b/src/content/docs/durable-objects/api/alarms.mdx
@@ -38,42 +38,42 @@ Although each Durable Object can only have one alarm set at a time, you can mana
 import { DurableObject } from "cloudflare:workers";
 
 export class AgentServer extends DurableObject {
-	// Schedule a one-time or recurring event
-	async scheduleEvent(id, runAt, repeatMs = null) {
-		await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
-		const currentAlarm = await this.ctx.storage.getAlarm();
-		if (!currentAlarm || runAt < currentAlarm) {
-			await this.ctx.storage.setAlarm(runAt);
-		}
-	}
-
-	async alarm() {
-		const now = Date.now();
-		const events = await this.ctx.storage.list({ prefix: "event:" });
-		let nextAlarm = null;
-
-		for (const [key, event] of events) {
-			if (event.runAt <= now) {
-				await this.processEvent(event);
-				if (event.repeatMs) {
-					event.runAt = now + event.repeatMs;
-					await this.ctx.storage.put(key, event);
-				} else {
-					await this.ctx.storage.delete(key);
-				}
-			}
-			// Track the next event time
-			if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
-				nextAlarm = event.runAt;
-			}
-		}
-
-		if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
-	}
-
-	async processEvent(event) {
-		// Your event handling logic here
-	}
+  // Schedule a one-time or recurring event
+  async scheduleEvent(id, runAt, repeatMs = null) {
+    await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
+    const currentAlarm = await this.ctx.storage.getAlarm();
+    if (!currentAlarm || runAt < currentAlarm) {
+      await this.ctx.storage.setAlarm(runAt);
+    }
+  }
+
+  async alarm() {
+    const now = Date.now();
+    const events = await this.ctx.storage.list({ prefix: "event:" });
+    let nextAlarm = null;
+
+    for (const [key, event] of events) {
+      if (event.runAt <= now) {
+        await this.processEvent(event);
+        if (event.repeatMs) {
+          event.runAt = now + event.repeatMs;
+          await this.ctx.storage.put(key, event);
+        } else {
+          await this.ctx.storage.delete(key);
+        }
+      }
+      // Track the next event time
+      if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
+        nextAlarm = event.runAt;
+      }
+    }
+
+    if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
+  }
+
+  async processEvent(event) {
+    // Your event handling logic here
+  }
 }
 ```
 
@@ -82,6 +82,7 @@ export class AgentServer extends DurableObject {
 ### `getAlarm`
 
 - <code>getAlarm()</code>: <Type text="number | null" />
+
   - If there is an alarm set, then return the currently set alarm time as the number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
   - If `getAlarm` is called while an [`alarm`](/durable-objects/api/alarms/#alarm) is already running, it returns `null` unless `setAlarm` has also been called since the alarm handler started running.
@@ -89,6 +90,7 @@ export class AgentServer extends DurableObject {
 ### `setAlarm`
 
 - <code> setAlarm(scheduledTimeMs <Type text="number" />) </code>: <Type text="void" />
+
   - Set the time for the alarm to run. Specify the time as the number of milliseconds elapsed since the UNIX epoch.
   - If you call `setAlarm` when there is already one scheduled, it will override the existing alarm.
 
@@ -101,6 +103,7 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `deleteAlarm`
 
 - `deleteAlarm()`: <Type text='void' />
+
   - Unset the alarm if there is a currently set alarm.
 
   - Calling `deleteAlarm()` inside the `alarm()` handler may prevent retries on a best-effort basis, but is not guaranteed.
@@ -110,9 +113,11 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `alarm`
 
 - <code>alarm(alarmInfo <Type text="Object" />)</code>: <Type text="void" />
+
   - Called by the system when a scheduled alarm time is reached.
 
   - The optional parameter `alarmInfo` object has two properties:
+
     - `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
     - `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
 
diff --git a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
index c41b19cc99bc69c..541d4b55aeebebd 100644
--- a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
@@ -8,16 +8,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	GlossaryTooltip,
-	TypeScriptExample,
-	Details,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
 
 :::note
 This page documents the storage API for legacy KV-backed Durable Objects.
@@ -92,6 +83,6 @@ KV-backed Durable Objects provide KV API methods which are asynchronous.
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
index 70afb0cebace527..2e6c605ca634618 100644
--- a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
@@ -8,16 +8,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	GlossaryTooltip,
-	TypeScriptExample,
-	Details,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
 
 :::note
 This page documents the storage API for the newer SQLite-backed Durable Objects.
@@ -145,11 +136,7 @@ class MyDurableObject(DurableObject):
 - When writing data, every row update of an index counts as an additional row. However, indexes may be beneficial for read-heavy use cases. Refer to [Index for SQLite Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#indexes-in-sqlite).
 - Writing data to [SQLite virtual tables](https://www.sqlite.org/vtab.html) also counts towards rows written.
 
-<Render
-	file="d1-do-supported-sqlite-extensions"
-	product="d1"
-	params={{ product: "Durable Objects support" }}
-/>
+<Render file="d1-do-supported-sqlite-extensions" product="d1" params={{ product: "Durable Objects support" }}/>
 
 ### `exec`
 
@@ -174,10 +161,7 @@ Always consume the cursor fully before yielding the event loop. Call `.toArray()
 ```ts
 // ✅ Safe: cursor is fully consumed before any await
 const rows = this.ctx.storage.sql.exec("SELECT * FROM users").toArray();
-const result = await fetch("https://example.com", {
-	method: "POST",
-	body: JSON.stringify(rows),
-});
+const result = await fetch("https://example.com", { method: "POST", body: JSON.stringify(rows) });
 ```
 
 ```ts
@@ -367,6 +351,6 @@ ctx.storage.onNextSessionRestoreBookmark(bookmark)
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
index 28b40fdda357f9f..cbcc52ad9c8be68 100644
--- a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
+++ b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
@@ -11,13 +11,10 @@ products:
 import { Render, GlossaryTooltip, WranglerConfig } from "~/components";
 
 <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> are a
-
 powerful compute API that provides a compute with storage building block. Each
 Durable Object has its own private, transactional, and strongly consistent
 storage. Durable Objects
-
 <GlossaryTooltip term="Storage API">Storage API</GlossaryTooltip> provides
-
 access to a Durable Object's attached storage.
 
 A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
diff --git a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
index 163f0a7cc9d2cb5..1f90f81aa40a253 100644
--- a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
+++ b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
@@ -82,7 +82,7 @@ Durable Objects will occasionally shut down and objects are restarted, which wil
 
 When a Durable Object is shut down, the object instance is automatically restarted and new requests are routed to the new instance. In-flight requests are handled as follows:
 
-- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage. If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
+- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage.  If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
 - **WebSocket connections**: WebSocket requests are terminated automatically during shutdown. This is so that the new instance can take over the connection as soon as possible.
 - **Other invocations (email, cron)**: Other invocations are treated similarly to HTTP requests.
 
diff --git a/src/content/docs/durable-objects/examples/agents.mdx b/src/content/docs/durable-objects/examples/agents.mdx
index 822795f49b71103..0a633feca9fcda1 100644
--- a/src/content/docs/durable-objects/examples/agents.mdx
+++ b/src/content/docs/durable-objects/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - durable-objects
----
+---
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/examples/index.mdx b/src/content/docs/durable-objects/examples/index.mdx
index 3c4df69e31c31d3..a885b12632c278f 100644
--- a/src/content/docs/durable-objects/examples/index.mdx
+++ b/src/content/docs/durable-objects/examples/index.mdx
@@ -14,7 +14,4 @@ import { ResourcesBySelector, GlossaryTooltip } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Durable Objects.
 
-<ResourcesBySelector
-	types={["example"]}
-	directory="durable-objects/examples/"
-/>
+<ResourcesBySelector types={["example"]} directory="durable-objects/examples/" />
diff --git a/src/content/docs/durable-objects/examples/websocket-server.mdx b/src/content/docs/durable-objects/examples/websocket-server.mdx
index 24b3a890045da9a..6c9fed4be7d126e 100644
--- a/src/content/docs/durable-objects/examples/websocket-server.mdx
+++ b/src/content/docs/durable-objects/examples/websocket-server.mdx
@@ -12,13 +12,7 @@ products:
   - durable-objects
 ---
 
-import {
-	TabItem,
-	Tabs,
-	GlossaryTooltip,
-	WranglerConfig,
-	TypeScriptExample,
-} from "~/components";
+import { TabItem, Tabs, GlossaryTooltip, WranglerConfig, TypeScriptExample } from "~/components";
 
 This example shows how to build a WebSocket server using <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> and Workers. The example exposes an endpoint to create a new WebSocket connection. This WebSocket connection echos any message while including the total number of WebSocket connections currently established. For more information, refer to [Use Durable Objects with WebSockets](/durable-objects/best-practices/websockets/).
 
diff --git a/src/content/docs/durable-objects/observability/data-studio.mdx b/src/content/docs/durable-objects/observability/data-studio.mdx
index 39fe7cf43e104b3..847423a93b479a1 100644
--- a/src/content/docs/durable-objects/observability/data-studio.mdx
+++ b/src/content/docs/durable-objects/observability/data-studio.mdx
@@ -40,4 +40,4 @@ You need to have at least the `Workers Platform Admin` [role](/fundamentals/mana
 
 All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/) for your security and compliance needs.
 
-- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
+- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/platform/known-issues.mdx b/src/content/docs/durable-objects/platform/known-issues.mdx
index 8d63e009732811e..a590711f8bcb13e 100644
--- a/src/content/docs/durable-objects/platform/known-issues.mdx
+++ b/src/content/docs/durable-objects/platform/known-issues.mdx
@@ -38,4 +38,4 @@ The Workers editor in the [Cloudflare dashboard](https://dash.cloudflare.com/) a
 
 Currently, when developing locally (using `npx wrangler dev`), Durable Object [alarm methods](/durable-objects/api/alarms) may fail after a hot reload (if you edit the code while the code is running locally).
 
-To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
+To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx
index 26f4a596ac0219e..ef53c2fd80d3d9c 100644
--- a/src/content/docs/durable-objects/platform/limits.mdx
+++ b/src/content/docs/durable-objects/platform/limits.mdx
@@ -77,3 +77,4 @@ For Durable Object classes with [SQLite storage](/durable-objects/api/sqlite-sto
 <Render file="do-faq-limits" product="durable-objects" />
 
 <Render file="wall-time-limits" product="workers" />
+
diff --git a/src/content/docs/durable-objects/reference/data-location.mdx b/src/content/docs/durable-objects/reference/data-location.mdx
index 9465de9ade8d4de..4f4ced530d3685f 100644
--- a/src/content/docs/durable-objects/reference/data-location.mdx
+++ b/src/content/docs/durable-objects/reference/data-location.mdx
@@ -58,9 +58,9 @@ Note that it is also possible to specify a jurisdiction by creating an individua
 
 ### Supported locations
 
-| Parameter | Location                       |
-| --------- | ------------------------------ |
-| eu        | The European Union             |
+| Parameter | Location                     |
+| --------- | ---------------------------- |
+| eu        | The European Union           |
 | fedramp   | FedRAMP-compliant data centers |
 
 ## Provide a location hint
@@ -102,14 +102,10 @@ Hints are a best effort and not a guarantee. Unlike with jurisdictions, Durable
 | afr       | Africa <sup>2</sup>        |
 | me        | Middle East <sup>2</sup>   |
 
-<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the
-future.
+<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the future.
 
-<sup>2</sup> Durable Objects currently do not spawn in this location. Instead,
-the Durable Object will spawn in a nearby location which does support Durable
-Objects. For example, Durable Objects hinted to South America spawn in Eastern
-North America instead.
+<sup>2</sup> Durable Objects currently do not spawn in this location. Instead, the Durable Object will spawn in a nearby location which does support Durable Objects. For example, Durable Objects hinted to South America spawn in Eastern North America instead.
 
 ## Additional resources
 
-- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
+- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/data-security.mdx b/src/content/docs/durable-objects/reference/data-security.mdx
index d410809c1239ec7..e91b874429d9483 100644
--- a/src/content/docs/durable-objects/reference/data-security.mdx
+++ b/src/content/docs/durable-objects/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of Durable Objects, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/durable-objects/reference/environments.mdx b/src/content/docs/durable-objects/reference/environments.mdx
index ac38518bf59f293..21a1b30c3e2981f 100644
--- a/src/content/docs/durable-objects/reference/environments.mdx
+++ b/src/content/docs/durable-objects/reference/environments.mdx
@@ -43,6 +43,8 @@ Durable Object bindings are not inherited. For example, you can define an enviro
 
 Because Wrangler appends the [environment name](/workers/wrangler/environments/) to the top-level name when publishing, for a Worker named `worker-name` the above example is equivalent to:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -69,6 +71,8 @@ Because Wrangler appends the [environment name](/workers/wrangler/environments/)
 
 If you want an environment-specific binding that accesses the same Objects as the top-level binding, specify the top-level Worker code name explicitly using `script_name`:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -114,10 +118,9 @@ To start remote development:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select an existing Worker.
 3. Select the **Edit code** icon located on the upper-right of the screen.
 
 :::caution
 Remote development is only available for KV-backed Durable Objects. SQLite-backed Durable Objects do not support remote development.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/faq.mdx b/src/content/docs/durable-objects/reference/faq.mdx
index 84262a5b52de7b9..2cff6f2d62e279c 100644
--- a/src/content/docs/durable-objects/reference/faq.mdx
+++ b/src/content/docs/durable-objects/reference/faq.mdx
@@ -12,12 +12,12 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="do-faq-pricing" product="durable-objects" />
+<Render file="do-faq-pricing" product="durable-objects"/>
 
 ## Limits
 
-<Render file="do-faq-limits" product="durable-objects" />
+<Render file="do-faq-limits" product="durable-objects"/>
 
 ## Metrics and analytics
 
-<Render file="do-faq-metrics-and-analytics" product="durable-objects" />
+<Render file="do-faq-metrics-and-analytics" product="durable-objects"/>
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/glossary.mdx b/src/content/docs/durable-objects/reference/glossary.mdx
index 1e9b3d062d8832e..b95a0d5b0e6b08d 100644
--- a/src/content/docs/durable-objects/reference/glossary.mdx
+++ b/src/content/docs/durable-objects/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - durable-objects
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Durable Objects documentation.
 
diff --git a/src/content/docs/durable-objects/reference/in-memory-state.mdx b/src/content/docs/durable-objects/reference/in-memory-state.mdx
index 7ef26232dd22b2b..772169b848b90bd 100644
--- a/src/content/docs/durable-objects/reference/in-memory-state.mdx
+++ b/src/content/docs/durable-objects/reference/in-memory-state.mdx
@@ -20,21 +20,21 @@ A common pattern is to initialize a Durable Object from [persistent storage](/du
 import { DurableObject } from "cloudflare:workers";
 
 export class Counter extends DurableObject {
-	constructor(ctx, env) {
-		super(ctx, env);
-		// `blockConcurrencyWhile()` ensures no requests are delivered until
-		// initialization completes.
-		this.ctx.blockConcurrencyWhile(async () => {
-			let stored = await this.ctx.storage.get("value");
-			// After initialization, future reads do not need to access storage.
-			this.value = stored || 0;
-		});
-	}
-
-	// Handle HTTP requests from clients.
-	async fetch(request) {
-		// use this.value rather than storage
-	}
+  constructor(ctx, env) {
+    super(ctx, env);
+    // `blockConcurrencyWhile()` ensures no requests are delivered until
+    // initialization completes.
+    this.ctx.blockConcurrencyWhile(async () => {
+      let stored = await this.ctx.storage.get("value");
+      // After initialization, future reads do not need to access storage.
+      this.value = stored || 0;
+    });
+  }
+
+  // Handle HTTP requests from clients.
+  async fetch(request) {
+    // use this.value rather than storage
+  }
 }
 ```
 
diff --git a/src/content/docs/durable-objects/video-tutorials.mdx b/src/content/docs/durable-objects/video-tutorials.mdx
index 4390949faf52bc7..4af3068247492a4 100644
--- a/src/content/docs/durable-objects/video-tutorials.mdx
+++ b/src/content/docs/durable-objects/video-tutorials.mdx
@@ -11,9 +11,11 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Introduction to Durable Objects"
-		description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
-		href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
-	/>
+    <LinkCard
+        title="Introduction to Durable Objects"
+        description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
+        href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
+    />
 </CardGrid>
+
+
diff --git a/src/content/docs/dynamic-workers/usage/bindings.mdx b/src/content/docs/dynamic-workers/usage/bindings.mdx
index 2970ac1c09b9962..5fed51bc8b0efe7 100644
--- a/src/content/docs/dynamic-workers/usage/bindings.mdx
+++ b/src/content/docs/dynamic-workers/usage/bindings.mdx
@@ -10,7 +10,7 @@ products:
 
 import { WranglerConfig } from "~/components";
 
-Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use.
+Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use. 
 
 This allows you to:
 
@@ -21,8 +21,7 @@ This allows you to:
 ## Custom Bindings with Dynamic Workers
 
 With custom bindings, you:
-
-- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer.
+- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer. 
 - **Pass it to the Dynamic Worker as a binding**: It just calls methods like `this.env.CHAT_ROOM.post("Hello!")` without knowing anything about the implementation behind it.
 
 ### How it works
@@ -30,65 +29,54 @@ With custom bindings, you:
 #### Step 1: Define the binding
 
 To create a custom binding, your loader Worker needs to implement a [`WorkerEntrypoint` class](/workers/runtime-apis/bindings/service-bindings/rpc#the-workerentrypoint-class) and export it. The methods you define on this class are the methods the Dynamic Worker will be able to call.
-
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint {
-	async post(text: string): Promise<void> {
-		// Your implementation here
-	}
+  async post(text: string): Promise<void> {
+    // Your implementation here
+  }
 }
 ```
-
 #### Step 2: Pass it to the Dynamic Worker
-
-Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`.
+Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`. 
 
 ```ts
 let chatRoom = ctx.exports.ChatRoom({ props: { roomName: "#bot-chat" } });
 
 let worker = env.LOADER.load({
-	env: { CHAT_ROOM: chatRoom },
-	// ...
+  env: { CHAT_ROOM: chatRoom },
+  // ...
 });
 ```
 
-From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call:
-
+From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call: 
 ```ts
 // Inside the Dynamic Worker
 await this.env.CHAT_ROOM.post("Hello!");
 ```
-
 #### Step 3: Customize per user with props
-
-One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user.
+One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user. 
 
 ```ts
 // Same class, different props per user
-let aliceRoom = ctx.exports.ChatRoom({
-	props: { roomName: "#alice", apiKey: ALICE_KEY },
-});
-let bobRoom = ctx.exports.ChatRoom({
-	props: { roomName: "#bob", apiKey: BOB_KEY },
-});
+let aliceRoom = ctx.exports.ChatRoom({ props: { roomName: "#alice", apiKey: ALICE_KEY } });
+let bobRoom   = ctx.exports.ChatRoom({ props: { roomName: "#bob", apiKey: BOB_KEY } });
 ```
 
 When the Dynamic Worker calls a method on the binding, it's actually making a call back to your loader Worker, that's where the method runs. Inside that method, you can read the `props` via [`this.ctx.props`](/workers/runtime-apis/context#props). Only the loader Worker has access to the props, the Dynamic Worker never sees them.
 
 ```ts
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-	async post(text: string): Promise<void> {
-		// Props are set when the stub is created — the Dynamic Worker never sees them
-		let roomName = this.ctx.props.roomName;
-		await postToChat(roomName, text);
-	}
+  async post(text: string): Promise<void> {
+    // Props are set when the stub is created — the Dynamic Worker never sees them
+    let roomName = this.ctx.props.roomName;
+    await postToChat(roomName, text);
+  }
 }
 ```
 
 ### Example: Chat room agent
-
 Here's a complete example putting it all together. Say you're building a platform where AI agents can post to chat rooms. Each agent should only be able to post to its assigned room and it should never see the API key used to authenticate.
 
 You define a `ChatRoom` class in your parent Worker. This class has a `post` method, the only method the Dynamic Worker can call on this binding. Inside this class, you control which room the message goes to, which API key is used, and what name is attached to the message.
@@ -97,46 +85,44 @@ You define a `ChatRoom` class in your parent Worker. This class has a `post` met
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-	async post(text: string): Promise<void> {
-		let { apiKey, botName, roomName } = this.ctx.props;
+  async post(text: string): Promise<void> {
+    let { apiKey, botName, roomName } = this.ctx.props;
 
-		// Prefix the message with the bot's name.
-		text = `[${botName}]: ${text}`;
+    // Prefix the message with the bot's name.
+    text = `[${botName}]: ${text}`;
 
-		// Send it to the chat service.
-		await postToChat(apiKey, roomName, text);
-	}
+    // Send it to the chat service.
+    await postToChat(apiKey, roomName, text);
+  }
 }
 
 type ChatRoomProps = {
-	apiKey: string;
-	roomName: string;
-	botName: string;
+  apiKey: string;
+  roomName: string;
+  botName: string;
 };
 ```
-
 You export one `ChatRoom` class, but each stub you create can have different `props` — a different room name, a different API key, a different bot name. The `props` are set when you create the stub, and the Dynamic Worker never sees them.
 
 Now pass it to a Dynamic Worker:
-
 ```ts
 // Create a stub scoped to a specific room.
 let chatRoom = ctx.exports.ChatRoom({
-	props: {
-		apiKey,
-		roomName: "#bot-chat",
-		botName: "Robo",
-	},
+  props: {
+    apiKey,
+    roomName: "#bot-chat",
+    botName: "Robo",
+  },
 });
 
 let worker = env.LOADER.load({
-	env: {
-		CHAT_ROOM: chatRoom,
-	},
-	compatibilityDate: "$today",
-	mainModule: "index.js",
-	modules: {
-		"index.js": `
+  env: {
+    CHAT_ROOM: chatRoom,
+  },
+  compatibilityDate: "$today",
+  mainModule: "index.js",
+  modules: {
+    "index.js": `
       export class Agent extends WorkerEntrypoint {
         async run() {
           // This is all the Dynamic Worker sees.
@@ -144,14 +130,13 @@ let worker = env.LOADER.load({
         }
       }
     `,
-	},
-	globalOutbound: null,
+  },
+  globalOutbound: null,
 });
 
 return worker.getEntrypoint("Agent").run();
 ```
-
-The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages.
+The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages. 
 
 ### Tip: Tell your agent about the types
 
@@ -161,52 +146,45 @@ Make sure your `WorkerEntrypoint` class extends the TypeScript type so the decla
 
 ## Passing normal Workers bindings
 
-To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose.
+To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose. 
 
 ### Example: Scoping a KV namespace per customer
 
 First, bind the KV namespace to your loader Worker. Then in your loader Worker, export a class that uses the KV binding and defines the methods Dynamic Workers can call:
-
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
-export class MyStorage extends WorkerEntrypoint<
-	Cloudflare.Env,
-	MyStorageProps
-> {
-	// Export this class from your loader Worker
-	// The Dynamic Worker will be able to call get() and put()
-	async get(key: string): Promise<string | null> {
-		// Prefix the key so this customer can only access their own data
-		return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
-	}
-
-	async put(key: string, value: string): Promise<void> {
-		await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
-	}
+export class MyStorage extends WorkerEntrypoint<Cloudflare.Env, MyStorageProps> {
+  // Export this class from your loader Worker
+  // The Dynamic Worker will be able to call get() and put()
+  async get(key: string): Promise<string | null> {
+    // Prefix the key so this customer can only access their own data
+    return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
+  }
+
+  async put(key: string, value: string): Promise<void> {
+    await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
+  }
 }
 
 type MyStorageProps = {
-	prefix: string;
+  prefix: string;
 };
 ```
-
 Then pass it to the Dynamic Worker with a customer-specific prefix:
-
 ```ts
 // Create a stub scoped to this customer's prefix
 let storage = ctx.exports.MyStorage({
-	props: { prefix: `customer-${customerId}` },
+  props: { prefix: `customer-${customerId}` },
 });
 
 let worker = env.LOADER.load({
-	env: { STORAGE: storage },
-	// ...
+  env: { STORAGE: storage },
+  // ...
 });
 ```
 
 The Dynamic Worker just uses it like any other binding:
-
 ```ts
 // Inside the Dynamic Worker, it just sees STORAGE with get and put
 let value = await this.env.STORAGE.get("settings");
@@ -219,7 +197,7 @@ For persistent storage that lives with each Dynamic Worker, see [Durable Object
 
 ## Capability-based Sandboxing
 
-Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it. If it hasn't received a stub for something, it can't access it.
+Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it.  If it hasn't received a stub for something, it can't access it. 
 
 This is powered by Workers RPC, also known as [Cap'n Web](https://github.com/cloudflare/capnweb), an RPC system designed to pass object references across security boundaries. When a Dynamic Worker receives a stub, it can call that object's methods and each call is an RPC back to the original object in your loader Worker. Stubs have no global identifier and cannot be forged, the only way to obtain one is to receive it.
 
diff --git a/src/content/docs/email-routing/email-workers/local-development.mdx b/src/content/docs/email-routing/email-workers/local-development.mdx
index ab7767665ecebf0..7764c919d997f0d 100644
--- a/src/content/docs/email-routing/email-workers/local-development.mdx
+++ b/src/content/docs/email-routing/email-workers/local-development.mdx
@@ -41,7 +41,7 @@ You can now test receiving, replying, and sending emails in your local environme
 Consider this example Email Worker script that uses the open source [`postal-mime`](https://www.npmjs.com/package/postal-mime) email parser:
 
 ```ts
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
 	async email(message, env, ctx) {
@@ -79,31 +79,31 @@ This is what you get in the console:
 
 ```json
 {
-	"headers": [
-		{
-			"key": "received",
-			"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
-		},
-		{ "key": "from", "value": "\"John\" <sender@example.com>" },
-		{ "key": "reply-to", "value": "sender@example.com" },
-		{ "key": "to", "value": "recipient@example.com" },
-		{ "key": "subject", "value": "Testing Email Workers Local Dev" },
-		{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
-		{ "key": "x-mailer", "value": "Curl" },
-		{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
-		{
-			"key": "message-id",
-			"value": "<6114391943504294873000@ZSH-GHOSTTY>"
-		}
-	],
-	"from": { "address": "sender@example.com", "name": "John" },
-	"to": [{ "address": "recipient@example.com", "name": "" }],
-	"replyTo": [{ "address": "sender@example.com", "name": "" }],
-	"subject": "Testing Email Workers Local Dev",
-	"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
-	"date": "2024-08-27T15:49:44.000Z",
-	"html": "Hi there\n",
-	"attachments": []
+  headers: [
+    {
+      key: 'received',
+      value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
+    },
+    { key: 'from', value: '"John" <sender@example.com>' },
+    { key: 'reply-to', value: 'sender@example.com' },
+    { key: 'to', value: 'recipient@example.com' },
+    { key: 'subject', value: 'Testing Email Workers Local Dev' },
+    { key: 'content-type', value: 'text/html; charset="windows-1252"' },
+    { key: 'x-mailer', value: 'Curl' },
+    { key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
+    {
+      key: 'message-id',
+      value: '<6114391943504294873000@ZSH-GHOSTTY>'
+    }
+  ],
+  from: { address: 'sender@example.com', name: 'John' },
+  to: [ { address: 'recipient@example.com', name: '' } ],
+  replyTo: [ { address: 'sender@example.com', name: '' } ],
+  subject: 'Testing Email Workers Local Dev',
+  messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
+  date: '2024-08-27T15:49:44.000Z',
+  html: 'Hi there\n',
+  attachments: []
 }
 ```
 
@@ -113,27 +113,23 @@ Wrangler can also simulate sending emails locally. Consider this example Email W
 
 ```ts
 import { EmailMessage } from "cloudflare:email";
-import { createMimeMessage } from "mimetext";
+import { createMimeMessage } from 'mimetext';
 
 export default {
 	async fetch(request, env, ctx) {
 		const msg = createMimeMessage();
-		msg.setSender({ name: "Sending email test", addr: "sender@example.com" });
-		msg.setRecipient("recipient@example.com");
-		msg.setSubject("An email generated in a worker");
+		msg.setSender({ name: 'Sending email test', addr: 'sender@example.com' });
+		msg.setRecipient('recipient@example.com');
+		msg.setSubject('An email generated in a worker');
 		msg.addMessage({
-			contentType: "text/plain",
+			contentType: 'text/plain',
 			data: `Congratulations, you just sent an email from a worker.`,
 		});
 
-		var message = new EmailMessage(
-			"sender@example.com",
-			"recipient@example.com",
-			msg.asRaw(),
-		);
+		var message = new EmailMessage('sender@example.com', 'recipient@example.com', msg.asRaw());
 		await env.EMAIL.send(message);
 		return Response.json({ ok: true });
-	},
+	}
 };
 ```
 
@@ -167,9 +163,9 @@ Congratulations, you just sent an email from a worker.
 Likewise, [`EmailMessage`](/email-routing/email-workers/runtime-api/#emailmessage-definition)'s `forward()` and `reply()` methods are also simulated locally. Consider this Worker that receives an email, parses it, replies to the sender, and forwards the original message to one your verified recipient addresses:
 
 ```ts
-import * as PostalMime from "postal-mime";
-import { createMimeMessage } from "mimetext";
-import { EmailMessage } from "cloudflare:email";
+import * as PostalMime from 'postal-mime';
+import { createMimeMessage } from 'mimetext';
+import { EmailMessage } from 'cloudflare:email';
 
 export default {
 	async email(message, env: any, ctx: any) {
@@ -183,23 +179,16 @@ export default {
 
 		// creates reply message
 		const msg = createMimeMessage();
-		msg.setSender({
-			name: "Thank you for your contact",
-			addr: "sender@example.com",
-		});
+		msg.setSender({ name: 'Thank you for your contact', addr: 'sender@example.com' });
 		msg.setRecipient(message.from);
-		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-		msg.setSubject("An email generated in a worker");
+		msg.setHeader('In-Reply-To', message.headers.get('Message-ID'));
+		msg.setSubject('An email generated in a worker');
 		msg.addMessage({
-			contentType: "text/plain",
+			contentType: 'text/plain',
 			data: `This is an automated reply. We received you email with the subject "${email.subject}", and will handle it as soon as possible.`,
 		});
 
-		const replyMessage = new EmailMessage(
-			"sender@example.com",
-			message.from,
-			msg.asRaw(),
-		);
+		const replyMessage = new EmailMessage('sender@example.com', message.from, msg.asRaw());
 
 		await message.reply(replyMessage);
 		await message.forward("recipient@example.com");
@@ -216,4 +205,4 @@ Run `npx wrangler dev` and use curl to `POST` the same message from the [Receive
   /var/folders/33/pn86qymd0w50htvsjp93rys40000gn/T/miniflare-381a79d7efa4e991607b30a079f6b17d/files/email/a1db7ebb-ccb4-45ef-b315-df49c6d820c0.eml
 [wrangler:inf] Email handler forwarded message with
   rcptTo: recipient@example.com
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
index 9b1bca4d651c33d..abe2ab9e1917b97 100644
--- a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
+++ b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
@@ -17,39 +17,37 @@ import { EmailMessage } from "cloudflare:email";
 import { createMimeMessage } from "mimetext";
 
 export default {
-	async email(message, env, ctx) {
-		const ticket = createTicket(message);
-
-		const msg = createMimeMessage();
-		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-		msg.setSender({
-			name: "Thank you for your contact",
-			addr: "<SENDER>@example.com",
-		});
-		msg.setRecipient(message.from);
-		msg.setSubject("Email Routing Auto-reply");
-		msg.addMessage({
-			contentType: "text/plain",
-			data: `We got your message, your ticket number is ${ticket.id}`,
-		});
-
-		const replyMessage = new EmailMessage(
-			"<SENDER>@example.com",
-			message.from,
-			msg.asRaw(),
-		);
-
-		await message.reply(replyMessage);
-	},
-};
+  async email(message, env, ctx) {
+
+    const ticket = createTicket(message);
+
+    const msg = createMimeMessage();
+    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
+    msg.setRecipient(message.from);
+    msg.setSubject("Email Routing Auto-reply");
+    msg.addMessage({
+      contentType: 'text/plain',
+      data: `We got your message, your ticket number is ${ ticket.id }`
+    });
+
+    const replyMessage = new EmailMessage(
+      "<SENDER>@example.com",
+      message.from,
+      msg.asRaw()
+    );
+
+    await message.reply(replyMessage);
+  }
+}
 ```
 
 To mitigate security risks and abuse, replying to incoming emails has a few requirements and limits:
 
-- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
-- The email can only be replied to once in the same `EmailMessage` event.
-- The recipient in the reply must match the incoming sender.
-- The outgoing sender domain must match the same domain that received the email.
-- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
+* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
+* The email can only be replied to once in the same `EmailMessage` event.
+* The recipient in the reply must match the incoming sender.
+* The outgoing sender domain must match the same domain that received the email.
+* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
 
-If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
+If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
\ No newline at end of file
diff --git a/src/content/docs/email-routing/get-started/audit-logs.mdx b/src/content/docs/email-routing/get-started/audit-logs.mdx
index ecd9b2792350842..ea56a04e458c21b 100644
--- a/src/content/docs/email-routing/get-started/audit-logs.mdx
+++ b/src/content/docs/email-routing/get-started/audit-logs.mdx
@@ -13,9 +13,9 @@ products:
 
 Audit logs for Email Routing are available in the [Cloudflare dashboard](https://dash.cloudflare.com/?account=audit-log). The following changes to Email Routing will be displayed:
 
-- Add/edit Rule
-- Add address
-- Address change status
-- Enable/disable/unlock zone
+* Add/edit Rule
+* Add address
+* Address change status
+* Enable/disable/unlock zone
 
 Refer to [Review audit logs](/fundamentals/account/account-security/review-audit-logs/) for more information.
diff --git a/src/content/docs/email-routing/get-started/index.mdx b/src/content/docs/email-routing/get-started/index.mdx
index 4f3a50117f3555f..79651ecf8525c75 100644
--- a/src/content/docs/email-routing/get-started/index.mdx
+++ b/src/content/docs/email-routing/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 To enable Email Routing, start by creating a custom email address linked to a destination address or Email Worker. This forms an **email rule**. You can enable or disable rules from the Cloudflare dashboard. Refer to [Enable Email Routing](/email-routing/get-started/enable-email-routing) for more details.
 
diff --git a/src/content/docs/email-routing/graphql-example.mdx b/src/content/docs/email-routing/graphql-example.mdx
index 01e88cb7c926f54..1026c732af09d68 100644
--- a/src/content/docs/email-routing/graphql-example.mdx
+++ b/src/content/docs/email-routing/graphql-example.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 10
 products:
   - email-routing
----
+---
\ No newline at end of file
diff --git a/src/content/docs/email-routing/limits.mdx b/src/content/docs/email-routing/limits.mdx
index 7ba2a9378e24cab..aa0c9137f7e93b4 100644
--- a/src/content/docs/email-routing/limits.mdx
+++ b/src/content/docs/email-routing/limits.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Email Workers size limits
 
diff --git a/src/content/docs/email-routing/postmaster.mdx b/src/content/docs/email-routing/postmaster.mdx
index 5024a5fca40679d..f2e0afee4304d44 100644
--- a/src/content/docs/email-routing/postmaster.mdx
+++ b/src/content/docs/email-routing/postmaster.mdx
@@ -223,6 +223,7 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
+
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
@@ -235,4 +236,4 @@ Email Routing does not support sending or replying from your Cloudflare domain.
 
 ### "`.`" is treated as a normal character for custom addresses
 
-The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
+The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
\ No newline at end of file
diff --git a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
index d5a45e53b881844..5b19f941bc3973c 100644
--- a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
+++ b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
@@ -17,8 +17,8 @@ You can check the status of your DNS records in the **Settings** section of Emai
 
 Check the status of your account's DNS records in the **Email DNS records** card:
 
-- **Email DNS records configured** - DNS records are properly configured.
-- **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
+* **Email DNS records configured** - DNS records are properly configured.
+* **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
 
 ### Start disabling
 
@@ -36,8 +36,8 @@ Select **View DNS records** for a list of the required `MX` and sender policy fr
 
 If you are having trouble with your account's DNS records, refer to the [Troubleshooting](/email-routing/troubleshooting/) section.
 
-## \_dc-mx DNS responses
+## _dc-mx DNS responses
 
 If you see a DNS response with a `_dc-mx` prefix (for example, `_dc-mx.a1b2c3d4e5f6.example.com`), Cloudflare inserted it automatically. This response appears when your `MX` record points to a hostname that is [proxied](/dns/proxy-status/) through Cloudflare. The `_dc-mx` target itself resolves directly to your origin IP address so that mail traffic bypasses the proxy and reaches your mail server.
 
-For more information, refer to [\_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
+For more information, refer to [_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
diff --git a/src/content/docs/email-routing/setup/index.mdx b/src/content/docs/email-routing/setup/index.mdx
index a985b31913d2240..9e8e6168e7d9d3d 100644
--- a/src/content/docs/email-routing/setup/index.mdx
+++ b/src/content/docs/email-routing/setup/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-routing/troubleshooting/index.mdx b/src/content/docs/email-routing/troubleshooting/index.mdx
index 320a435287a9f78..6049ae5a1dbf1b6 100644
--- a/src/content/docs/email-routing/troubleshooting/index.mdx
+++ b/src/content/docs/email-routing/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Email Routing warns you when your DNS records are not properly configured. In Email Routing's **Overview** page, you will see a message explaining what type of problem your account's DNS records have.
 
diff --git a/src/content/docs/email-security/account-setup/index.mdx b/src/content/docs/email-security/account-setup/index.mdx
index 115b19e40df6b41..58b9191302f4924 100644
--- a/src/content/docs/email-security/account-setup/index.mdx
+++ b/src/content/docs/email-security/account-setup/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
index 74464f58cb9a20e..1a386467767d7a5 100644
--- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
+++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 1. Log in to the [Google Cloud Console](https://console.cloud.google.com/welcome/new). From the dashboard, select **CREATE OR SELECT PROJECT**.
 2. Provide the details for the new project, and select **CREATE** to start your new project.
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Next steps
 
-Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
+Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
\ No newline at end of file
diff --git a/src/content/docs/email-security/deployment/inline/reference/index.mdx b/src/content/docs/email-security/deployment/inline/reference/index.mdx
index d967052afafa9a8..3acddcd2503e68e 100644
--- a/src/content/docs/email-security/deployment/inline/reference/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/inline/setup/index.mdx b/src/content/docs/email-security/deployment/inline/setup/index.mdx
index 7944841692ccc8f..9d77a311b1def17 100644
--- a/src/content/docs/email-security/deployment/inline/setup/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/setup/index.mdx
@@ -11,7 +11,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For help getting started with an [inline setup](/email-security/deployment/inline/), refer to the following guides:
 
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
index 1d64d9275d3103e..b36be50d7f74394 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
@@ -15,11 +15,11 @@ Alert Webhooks allow you to connect external services to Email security, includi
 - Slack
 - Email addresses
 - <GlossaryTooltip
-    	term="SIEM"
-    	link="/email-security/reporting/siem-integration/"
-    >
-    	SIEM
-    </GlossaryTooltip>
+  	term="SIEM"
+  	link="/email-security/reporting/siem-integration/"
+  >
+  	SIEM
+  </GlossaryTooltip>
 - Microsoft Teams
 
 ## Create an alert webhook
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
index bcf17ca94340495..064f16bbe246605 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/email-policies/index.mdx b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
index f02050d417bebf4..970060f35bca548 100644
--- a/src/content/docs/email-security/email-configuration/email-policies/index.mdx
+++ b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 <Render file="contact-support" product="email-security" />
 
diff --git a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
index 57eafdbc713f614..cf276be7c979d2c 100644
--- a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
+++ b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/lists/index.mdx b/src/content/docs/email-security/email-configuration/lists/index.mdx
index 309b6ba3c5e4a88..fb788ae5a7833ef 100644
--- a/src/content/docs/email-security/email-configuration/lists/index.mdx
+++ b/src/content/docs/email-security/email-configuration/lists/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx
index 1f577dece7e60c7..0f8848970f558ed 100644
--- a/src/content/docs/email-security/migrate-to-email-security.mdx
+++ b/src/content/docs/email-security/migrate-to-email-security.mdx
@@ -45,15 +45,15 @@ To invite users in Zero Trust Email security:
 
 Once you have added new account members, you will have to assign each member an [Email security role](/cloudflare-one/roles-permissions/#email-security-roles).
 
-| Area 1              | Email security                                                            | Description                                                                                                                                                                                                                  |
-| ------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Area 1              | Email security                                                            | Description                                                                                                                                                                                             |
+| ------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | N/A                 | Cloudflare Zero Trust                                                     | Can edit Cloudflare [Zero Trust](/cloudflare-one/). Has administrator access to all Zero Trust products including Access, Gateway, the Cloudflare One Client, Tunnel, Browser Isolation, CASB, DLP, DEX, and Email security. |
-| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                                      |
-| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                                      |
-| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                                               |
-| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                                             |
-| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                                                    |
-| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                                                   |
+| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                 |
+| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                 |
+| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                          |
+| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                        |
+| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                               |
+| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                              |
 
 ## Create webhooks
 
@@ -142,12 +142,12 @@ This table displays the difference in terminology used when creating policies:
 
 This table displays the difference in terminology used when finding emails whose disposition is incorrect:
 
-| Area 1                                                                                                                                                                                   | Email security                                                                                       |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| Area 1                                                                                                                                                                                   | Email security                                                                           |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
 | Report [false negative](/email-security/email-configuration/phish-submissions/#false-negatives)/[false positive](/email-security/email-configuration/phish-submissions/#false-positives) | [Submit messages for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) |
-| N/A                                                                                                                                                                                      | Escalate user submissions                                                                            |
-| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)                     |
-| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)                     |
+| N/A                                                                                                                                                                                      | Escalate user submissions                                                                |
+| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)         |
+| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)         |
 
 ## Business Email Compromise
 
diff --git a/src/content/docs/email-security/reference/index.mdx b/src/content/docs/email-security/reference/index.mdx
index c38a16a0de9f080..9f7509bd9cf9280 100644
--- a/src/content/docs/email-security/reference/index.mdx
+++ b/src/content/docs/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-service/api/index.mdx b/src/content/docs/email-service/api/index.mdx
index d03187150053624..44e78505396a107 100644
--- a/src/content/docs/email-service/api/index.mdx
+++ b/src/content/docs/email-service/api/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/api/route-emails/email-handler.mdx b/src/content/docs/email-service/api/route-emails/email-handler.mdx
index 4de6233a27266e7..a5e96e60aafc443 100644
--- a/src/content/docs/email-service/api/route-emails/email-handler.mdx
+++ b/src/content/docs/email-service/api/route-emails/email-handler.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 products:
   - email-service
-  - workers
+  - workers 
 ---
 
 import { Tabs, TabItem } from "~/components";
diff --git a/src/content/docs/email-service/api/route-emails/index.mdx b/src/content/docs/email-service/api/route-emails/index.mdx
index 1d26611cdc87d0d..5d7f8f3f10cb0db 100644
--- a/src/content/docs/email-service/api/route-emails/index.mdx
+++ b/src/content/docs/email-service/api/route-emails/index.mdx
@@ -14,4 +14,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/api/send-emails/rest-api.mdx b/src/content/docs/email-service/api/send-emails/rest-api.mdx
index 91cbd43aa37da94..7435885f3824271 100644
--- a/src/content/docs/email-service/api/send-emails/rest-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/rest-api.mdx
@@ -135,14 +135,14 @@ A successful response returns the delivery status for each recipient:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"delivered": ["recipient@example.com"],
-		"permanent_bounces": [],
-		"queued": []
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "delivered": ["recipient@example.com"],
+    "permanent_bounces": [],
+    "queued": []
+  }
 }
 ```
 
@@ -156,29 +156,29 @@ The REST API returns standard Cloudflare API error responses. A failed request r
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 10001,
-			"message": "email.sending.error.invalid_request_schema"
-		}
-	],
-	"messages": [],
-	"result": null
+  "success": false,
+  "errors": [
+    {
+      "code": 10001,
+      "message": "email.sending.error.invalid_request_schema"
+    }
+  ],
+  "messages": [],
+  "result": null
 }
 ```
 
 Common REST API error codes:
 
-| HTTP Status | Code  | Message                                       | Description                            |
-| ----------- | ----- | --------------------------------------------- | -------------------------------------- |
-| 400         | 10001 | `email.sending.error.invalid_request_schema`  | Invalid request format                 |
-| 400         | 10200 | `email.sending.error.email.invalid`           | Invalid email content                  |
-| 400         | 10201 | `email.sending.error.email.no_content_length` | Missing content length                 |
-| 400         | 10202 | `email.sending.error.email.too_big`           | Email exceeds size limit               |
-| 403         | 10203 | `email.sending.error.email.sending_disabled`  | Sending disabled for this zone/account |
-| 429         | 10004 | `email.sending.error.throttled`               | Rate limit exceeded                    |
-| 500         | 10002 | `email.sending.error.internal_server`         | Internal server error                  |
+| HTTP Status | Code | Message | Description |
+| ----------- | ---- | ------- | ----------- |
+| 400 | 10001 | `email.sending.error.invalid_request_schema` | Invalid request format |
+| 400 | 10200 | `email.sending.error.email.invalid` | Invalid email content |
+| 400 | 10201 | `email.sending.error.email.no_content_length` | Missing content length |
+| 400 | 10202 | `email.sending.error.email.too_big` | Email exceeds size limit |
+| 403 | 10203 | `email.sending.error.email.sending_disabled` | Sending disabled for this zone/account |
+| 429 | 10004 | `email.sending.error.throttled` | Rate limit exceeded |
+| 500 | 10002 | `email.sending.error.internal_server` | Internal server error |
 
 :::note[Workers binding vs REST API errors]
 The REST API returns standard Cloudflare API numeric error codes, while the [Workers binding](/email-service/api/send-emails/workers-api/) throws errors with string codes (for example, `E_SENDER_NOT_VERIFIED`). Refer to the [Workers API error codes table](/email-service/api/send-emails/workers-api/#error-codes) for the string error codes.
diff --git a/src/content/docs/email-service/api/send-emails/workers-api.mdx b/src/content/docs/email-service/api/send-emails/workers-api.mdx
index ad7de8aa161ea02..83244ea4c0e7dbb 100644
--- a/src/content/docs/email-service/api/send-emails/workers-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/workers-api.mdx
@@ -235,27 +235,27 @@ export default {
 
 The following error codes may be returned when sending emails:
 
-| Error Code                      | Description                             | Common Causes                                                                              |
-| ------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------ |
-| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data                              |
-| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                                                  |
-| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                                                        |
-| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                                                  |
-| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`                                   |
-| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam                                  |
-| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                                                      |
-| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                                                     |
-| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection                                          |
-| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                                                 |
-| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                                                |
-| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                                                      |
+| Error Code                      | Description                             | Common Causes                                                 |
+| ------------------------------- | --------------------------------------- | ------------------------------------------------------------- |
+| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data |
+| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                     |
+| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                           |
+| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                     |
+| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`      |
+| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam     |
+| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                         |
+| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                        |
+| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection             |
+| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                    |
+| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                   |
+| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                         |
 | `E_HEADER_NOT_ALLOWED`          | Header not allowed                      | Header is platform-controlled or not on the [whitelist](/email-service/reference/headers/) |
-| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field                                 |
-| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                                                |
-| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                                             |
-| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                                               |
-| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                                                    |
-| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers                                            |
+| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field    |
+| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                   |
+| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                |
+| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                  |
+| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                       |
+| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers               |
 
 ## Legacy `EmailMessage` API
 
diff --git a/src/content/docs/email-service/concepts/index.mdx b/src/content/docs/email-service/concepts/index.mdx
index 20dd8baf3869d18..6dacc309b767a1c 100644
--- a/src/content/docs/email-service/concepts/index.mdx
+++ b/src/content/docs/email-service/concepts/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/configuration/index.mdx b/src/content/docs/email-service/configuration/index.mdx
index d8ae4416f025c07..d7381d7a1565017 100644
--- a/src/content/docs/email-service/configuration/index.mdx
+++ b/src/content/docs/email-service/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
index 7b743963157b998..be8214fb629d3e3 100644
--- a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
+++ b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
@@ -44,145 +44,138 @@ id = "your-kv-namespace-id"
 ## Hard bounce detection
 
 ```javascript
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
-	async email(message, env, ctx) {
-		// Parse the raw email message
-		const parser = new PostalMime.default();
-		const rawEmail = new Response(message.raw);
-		const email = await parser.parse(await rawEmail.arrayBuffer());
-
-		// Check if this is a bounce notification
-		if (isBounceNotification(email)) {
-			const bounceInfo = await parseBounceInfo(email);
-
-			if (bounceInfo.type === "hard") {
-				await handleHardBounce(bounceInfo, env);
-				console.log(
-					`Hard bounce processed for: ${bounceInfo.originalRecipient}`,
-				);
-				return;
-			}
-		}
-
-		// Forward non-bounce emails normally
-		await message.forward("admin@yourdomain.com");
-	},
+  async email(message, env, ctx) {
+    // Parse the raw email message
+    const parser = new PostalMime.default();
+    const rawEmail = new Response(message.raw);
+    const email = await parser.parse(await rawEmail.arrayBuffer());
+
+    // Check if this is a bounce notification
+    if (isBounceNotification(email)) {
+      const bounceInfo = await parseBounceInfo(email);
+
+      if (bounceInfo.type === 'hard') {
+        await handleHardBounce(bounceInfo, env);
+        console.log(`Hard bounce processed for: ${bounceInfo.originalRecipient}`);
+        return;
+      }
+    }
+
+    // Forward non-bounce emails normally
+    await message.forward('admin@yourdomain.com');
+  },
 };
 
 function isBounceNotification(email) {
-	// Check common bounce indicators
-	const subject = email.subject?.toLowerCase() || "";
-	const fromAddress = email.from?.address?.toLowerCase() || "";
-
-	// Common bounce indicators
-	const bounceSubjects = [
-		"mail delivery failed",
-		"undelivered mail returned to sender",
-		"delivery status notification",
-		"returned mail",
-		"mail system error",
-	];
-
-	const bounceFromPatterns = [
-		"mailer-daemon",
-		"mail-daemon",
-		"postmaster",
-		"noreply",
-		"bounce",
-	];
-
-	return (
-		bounceSubjects.some((phrase) => subject.includes(phrase)) ||
-		bounceFromPatterns.some((pattern) => fromAddress.includes(pattern))
-	);
+  // Check common bounce indicators
+  const subject = email.subject?.toLowerCase() || '';
+  const fromAddress = email.from?.address?.toLowerCase() || '';
+
+  // Common bounce indicators
+  const bounceSubjects = [
+    'mail delivery failed',
+    'undelivered mail returned to sender',
+    'delivery status notification',
+    'returned mail',
+    'mail system error'
+  ];
+
+  const bounceFromPatterns = [
+    'mailer-daemon',
+    'mail-daemon',
+    'postmaster',
+    'noreply',
+    'bounce'
+  ];
+
+  return bounceSubjects.some(phrase => subject.includes(phrase)) ||
+         bounceFromPatterns.some(pattern => fromAddress.includes(pattern));
 }
 
 async function parseBounceInfo(email) {
-	const text = email.text || "";
-	const html = email.html || "";
-	const content = text + " " + html;
-
-	// Extract original recipient email
-	const recipientMatch =
-		content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
-		content.match(/([^\s<]+@[^\s>]+)/);
-
-	const originalRecipient = recipientMatch ? recipientMatch[1] : null;
-
-	// Determine bounce type based on content
-	const hardBounceIndicators = [
-		"user unknown",
-		"no such user",
-		"invalid recipient",
-		"recipient address rejected",
-		"mailbox unavailable",
-		"domain not found",
-		"5.1.1", // SMTP error code for bad destination mailbox
-		"5.1.2", // SMTP error code for bad destination system
-		"5.4.1", // SMTP error code for no answer from host
-	];
-
-	const isHardBounce = hardBounceIndicators.some((indicator) =>
-		content.toLowerCase().includes(indicator.toLowerCase()),
-	);
-
-	return {
-		type: isHardBounce ? "hard" : "soft",
-		originalRecipient,
-		reason: extractBounceReason(content),
-		timestamp: new Date().toISOString(),
-	};
+  const text = email.text || '';
+  const html = email.html || '';
+  const content = text + ' ' + html;
+
+  // Extract original recipient email
+  const recipientMatch = content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
+                        content.match(/([^\s<]+@[^\s>]+)/);
+
+  const originalRecipient = recipientMatch ? recipientMatch[1] : null;
+
+  // Determine bounce type based on content
+  const hardBounceIndicators = [
+    'user unknown',
+    'no such user',
+    'invalid recipient',
+    'recipient address rejected',
+    'mailbox unavailable',
+    'domain not found',
+    '5.1.1', // SMTP error code for bad destination mailbox
+    '5.1.2', // SMTP error code for bad destination system
+    '5.4.1', // SMTP error code for no answer from host
+  ];
+
+  const isHardBounce = hardBounceIndicators.some(indicator =>
+    content.toLowerCase().includes(indicator.toLowerCase())
+  );
+
+  return {
+    type: isHardBounce ? 'hard' : 'soft',
+    originalRecipient,
+    reason: extractBounceReason(content),
+    timestamp: new Date().toISOString()
+  };
 }
 
 function extractBounceReason(content) {
-	// Extract the specific error message
-	const reasonPatterns = [
-		/diagnostic[- ]code:\s*(.+)/i,
-		/reason:\s*(.+)/i,
-		/error:\s*(.+)/i,
-		/(5\.\d+\.\d+[^.\n]*)/i,
-	];
-
-	for (const pattern of reasonPatterns) {
-		const match = content.match(pattern);
-		if (match) {
-			return match[1].trim().split("\n")[0]; // Take first line only
-		}
-	}
-
-	return "Unknown bounce reason";
+  // Extract the specific error message
+  const reasonPatterns = [
+    /diagnostic[- ]code:\s*(.+)/i,
+    /reason:\s*(.+)/i,
+    /error:\s*(.+)/i,
+    /(5\.\d+\.\d+[^.\n]*)/i
+  ];
+
+  for (const pattern of reasonPatterns) {
+    const match = content.match(pattern);
+    if (match) {
+      return match[1].trim().split('\n')[0]; // Take first line only
+    }
+  }
+
+  return 'Unknown bounce reason';
 }
 
 async function handleHardBounce(bounceInfo, env) {
-	if (!bounceInfo.originalRecipient) {
-		console.log("Could not extract original recipient from bounce");
-		return;
-	}
-
-	// Add to suppression list in KV
-	await env.SUPPRESSION_LIST.put(
-		bounceInfo.originalRecipient,
-		JSON.stringify({
-			type: "hard_bounce",
-			reason: bounceInfo.reason,
-			timestamp: bounceInfo.timestamp,
-			status: "suppressed",
-		}),
-		{
-			metadata: {
-				bounceType: "hard",
-				addedDate: bounceInfo.timestamp,
-			},
-		},
-	);
-
-	console.log(
-		`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`,
-	);
+  if (!bounceInfo.originalRecipient) {
+    console.log('Could not extract original recipient from bounce');
+    return;
+  }
+
+  // Add to suppression list in KV
+  await env.SUPPRESSION_LIST.put(
+    bounceInfo.originalRecipient,
+    JSON.stringify({
+      type: 'hard_bounce',
+      reason: bounceInfo.reason,
+      timestamp: bounceInfo.timestamp,
+      status: 'suppressed'
+    }),
+    {
+      metadata: {
+        bounceType: 'hard',
+        addedDate: bounceInfo.timestamp
+      }
+    }
+  );
+
+  console.log(`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`);
 }
-```
+````
 
 ## Testing hard bounce handling
 
diff --git a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
index 4f7199cce0ef4f7..a7a6a6f31405fa0 100644
--- a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
+++ b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
@@ -40,7 +40,7 @@ class SimpleSpamFilter implements SpamFilter {
 		"winner",
 		"congratulations",
 		"inheritance",
-		"lottery",
+		"lottery"
 	];
 
 	private trustedDomains = ["company.com", "trusted-partner.com", "vendor.net"];
@@ -83,10 +83,7 @@ class SimpleSpamFilter implements SpamFilter {
 		}
 
 		// Check for suspicious sender patterns
-		if (
-			sender.includes("noreply") &&
-			subject.toLowerCase().includes("urgent")
-		) {
+		if (sender.includes("noreply") && subject.toLowerCase().includes("urgent")) {
 			score += 2;
 			reasons.push("Suspicious noreply + urgent combination");
 		}
@@ -104,33 +101,31 @@ const spamFilter = new SimpleSpamFilter();
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const startTime = Date.now();
-
+		
 		// Check for spam
 		const spamCheck = await spamFilter.checkSpam(message);
 
 		// Track spam check metrics
 		env.EMAIL_ANALYTICS?.writeDataPoint({
 			blobs: [
-				"spam_check_completed",
+				'spam_check_completed',
 				message.from,
 				message.to,
-				spamCheck.isSpam ? "spam" : "legitimate",
+				spamCheck.isSpam ? 'spam' : 'legitimate'
 			],
 			doubles: [
 				1, // Count
 				spamCheck.score,
-				Date.now() - startTime,
+				Date.now() - startTime
 			],
 			indexes: [
 				`spam_detected:${spamCheck.isSpam}`,
-				`score_range:${getScoreRange(spamCheck.score)}`,
-			],
+				`score_range:${getScoreRange(spamCheck.score)}`
+			]
 		});
 
 		if (spamCheck.isSpam) {
-			console.log(
-				`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`,
-			);
+			console.log(`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`);
 			message.setReject(`Message rejected: ${spamCheck.reasons[0]}`);
 			return;
 		}
@@ -146,13 +141,13 @@ export default {
 };
 
 function getScoreRange(score: number): string {
-	if (score < 0) return "trusted";
-	if (score === 0) return "neutral";
-	if (score === 1) return "suspicious";
-	return "spam";
+	if (score < 0) return 'trusted';
+	if (score === 0) return 'neutral';
+	if (score === 1) return 'suspicious';
+	return 'spam';
 }
 ```
 
 ## Advanced spam detection with AI
 
-For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
+For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
\ No newline at end of file
diff --git a/src/content/docs/email-service/get-started/send-emails.mdx b/src/content/docs/email-service/get-started/send-emails.mdx
index cb5765ac4807d02..14f5fccbd0ab3f5 100644
--- a/src/content/docs/email-service/get-started/send-emails.mdx
+++ b/src/content/docs/email-service/get-started/send-emails.mdx
@@ -54,14 +54,14 @@ A successful response includes the delivery status for each recipient:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"delivered": ["recipient@example.com"],
-		"permanent_bounces": [],
-		"queued": []
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "delivered": ["recipient@example.com"],
+    "permanent_bounces": [],
+    "queued": []
+  }
 }
 ```
 
@@ -84,14 +84,14 @@ If you are building on Cloudflare Workers, you can use the Workers binding for n
 2.  Add the email binding to your Wrangler configuration file:
 
     <WranglerConfig>
-    
-        ```toml
-        [[send_email]]
-        name = "EMAIL"
-        remote = true
-        ```
-    
-        </WranglerConfig>
+
+    ```toml
+    [[send_email]]
+    name = "EMAIL"
+    remote = true
+    ```
+
+    </WranglerConfig>
 
 3.  Create your Worker code in `src/index.ts`:
 
@@ -147,4 +147,4 @@ Now that you can send emails, explore advanced features:
 
 - **[Route incoming emails](/email-service/get-started/route-emails/)** - Process emails sent to your domain
 - **[API reference](/email-service/api/send-emails/)** - Complete API documentation
-- **[Examples](/email-service/examples/)** - Real-world implementation patterns
+- **[Examples](/email-service/examples/)** - Real-world implementation patterns
\ No newline at end of file
diff --git a/src/content/docs/email-service/local-development/index.mdx b/src/content/docs/email-service/local-development/index.mdx
index 90f0be957d8c338..9b9df2443a3e182 100644
--- a/src/content/docs/email-service/local-development/index.mdx
+++ b/src/content/docs/email-service/local-development/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Test and develop your email applications locally using Wrangler before deploying to production.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/local-development/routing.mdx b/src/content/docs/email-service/local-development/routing.mdx
index 50adb9e89ffd9e6..caf0d02137925c7 100644
--- a/src/content/docs/email-service/local-development/routing.mdx
+++ b/src/content/docs/email-service/local-development/routing.mdx
@@ -35,30 +35,30 @@ name = "EMAIL"
 ## Basic routing worker
 
 ```javascript
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
-	async email(message, env, ctx) {
-		// Parse the raw email message
-		const parser = new PostalMime.default();
-		const rawEmail = new Response(message.raw);
-		const email = await parser.parse(await rawEmail.arrayBuffer());
-
-		console.log("Received email:", {
-			from: message.from,
-			to: message.to,
-			subject: email.subject,
-			text: email.text,
-			html: email.html,
-		});
-
-		// Route based on recipient
-		if (message.to.includes("support@")) {
-			await message.forward("support-team@company.com");
-		} else {
-			await message.forward("general@company.com");
-		}
-	},
+  async email(message, env, ctx) {
+    // Parse the raw email message
+    const parser = new PostalMime.default();
+    const rawEmail = new Response(message.raw);
+    const email = await parser.parse(await rawEmail.arrayBuffer());
+
+    console.log('Received email:', {
+      from: message.from,
+      to: message.to,
+      subject: email.subject,
+      text: email.text,
+      html: email.html
+    });
+
+    // Route based on recipient
+    if (message.to.includes('support@')) {
+      await message.forward('support-team@company.com');
+    } else {
+      await message.forward('general@company.com');
+    }
+  },
 };
 ```
 
diff --git a/src/content/docs/email-service/platform/index.mdx b/src/content/docs/email-service/platform/index.mdx
index c4e599e6b17ffc9..56789154dfe88e9 100644
--- a/src/content/docs/email-service/platform/index.mdx
+++ b/src/content/docs/email-service/platform/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/platform/pricing.mdx b/src/content/docs/email-service/platform/pricing.mdx
index 4dfa8f6a7c2c0c2..914f0b2cf37e5a8 100644
--- a/src/content/docs/email-service/platform/pricing.mdx
+++ b/src/content/docs/email-service/platform/pricing.mdx
@@ -14,9 +14,9 @@ Cloudflare Email Service pricing is based on your Cloudflare plan and email usag
 
 Email Routing is available on both the Workers Free and Workers Paid plans. Email Sending is only available on the Workers Paid plan.
 
-|                                     | Workers Free  | Workers Paid                                          |
-| ----------------------------------- | ------------- | ----------------------------------------------------- |
-| **Outbound emails (Email Sending)** | Not available | 3,000 included per month, then $0.35 per 1,000 emails |
-| **Inbound emails (Email Routing)**  | Unlimited     | Unlimited                                             |
+|                                                         | Workers Free     | Workers Paid     |
+| ------------------------------------------------------- | ---------------- | ---------------- |
+| **Outbound emails (Email Sending)**                     | Not available    | 3,000 included per month, then $0.35 per 1,000 emails |
+| **Inbound emails (Email Routing)**                      | Unlimited        | Unlimited        |
 
 Email Routing Workers is billed according to [Workers pricing](/workers/platform/pricing/).
diff --git a/src/content/docs/email-service/reference/index.mdx b/src/content/docs/email-service/reference/index.mdx
index 667dce89f146995..fb104b8db015bee 100644
--- a/src/content/docs/email-service/reference/index.mdx
+++ b/src/content/docs/email-service/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
     hideIndex: true
 products:
   - email-service
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/reference/postmaster.mdx b/src/content/docs/email-service/reference/postmaster.mdx
index 329745da9935650..e5f357aa33574bd 100644
--- a/src/content/docs/email-service/reference/postmaster.mdx
+++ b/src/content/docs/email-service/reference/postmaster.mdx
@@ -164,6 +164,7 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
+
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
diff --git a/src/content/docs/firewall/api/cf-filters/delete.mdx b/src/content/docs/firewall/api/cf-filters/delete.mdx
index 3d3ea8b45311d7f..b6c9144e5c5757d 100644
--- a/src/content/docs/firewall/api/cf-filters/delete.mdx
+++ b/src/content/docs/firewall/api/cf-filters/delete.mdx
@@ -24,17 +24,17 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>"
-		},
-		{
-			"id": "<FILTER_ID_2>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID_1>"
+    },
+    {
+      "id": "<FILTER_ID_2>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -51,13 +51,13 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/get.mdx b/src/content/docs/firewall/api/cf-filters/get.mdx
index f60ae9c7c41a342..c4c4d34c089e8f4 100644
--- a/src/content/docs/firewall/api/cf-filters/get.mdx
+++ b/src/content/docs/firewall/api/cf-filters/get.mdx
@@ -23,47 +23,47 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>",
-			"paused": false,
-			"description": "Login from office",
-			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "Login",
-			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_3>",
-			"paused": false,
-			"description": "not /api",
-			"expression": "not http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_4>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_5>",
-			"paused": false,
-			"expression": "ip.src eq 93.184.216.0"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result_info": {
-		"page": 1,
-		"per_page": 25,
-		"count": 5,
-		"total_count": 5,
-		"total_pages": 1
-	}
+  "result": [
+    {
+      "id": "<FILTER_ID_1>",
+      "paused": false,
+      "description": "Login from office",
+      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "Login",
+      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_3>",
+      "paused": false,
+      "description": "not /api",
+      "expression": "not http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_4>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_5>",
+      "paused": false,
+      "expression": "ip.src eq 93.184.216.0"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result_info": {
+    "page": 1,
+    "per_page": 25,
+    "count": 5,
+    "total_count": 5,
+    "total_pages": 1
+  }
 }
 ```
 
@@ -79,14 +79,14 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters/{filter_id}"
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<FILTER_ID>",
-		"paused": false,
-		"description": "Login from office",
-		"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<FILTER_ID>",
+    "paused": false,
+    "description": "Login from office",
+    "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/post.mdx b/src/content/docs/firewall/api/cf-filters/post.mdx
index 966cc67d408dcfc..ec20a4e1f410ada 100644
--- a/src/content/docs/firewall/api/cf-filters/post.mdx
+++ b/src/content/docs/firewall/api/cf-filters/post.mdx
@@ -43,39 +43,39 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>",
-			"paused": false,
-			"expression": "ip.src eq 93.184.216.0"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_3>",
-			"paused": false,
-			"description": "not /api",
-			"expression": "not http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_4>",
-			"paused": false,
-			"description": "Login",
-			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_5>",
-			"paused": false,
-			"description": "Login from office",
-			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID_1>",
+      "paused": false,
+      "expression": "ip.src eq 93.184.216.0"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_3>",
+      "paused": false,
+      "description": "not /api",
+      "expression": "not http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_4>",
+      "paused": false,
+      "description": "Login",
+      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_5>",
+      "paused": false,
+      "description": "Login from office",
+      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/put.mdx b/src/content/docs/firewall/api/cf-filters/put.mdx
index a0412eac414fc43..4a08764ea671787 100644
--- a/src/content/docs/firewall/api/cf-filters/put.mdx
+++ b/src/content/docs/firewall/api/cf-filters/put.mdx
@@ -38,23 +38,23 @@ curl --request PUT \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID>",
-			"paused": false,
-			"description": "IP of example.org",
-			"expression": "ip.src eq 93.184.216.0"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID>",
+      "paused": false,
+      "description": "IP of example.org",
+      "expression": "ip.src eq 93.184.216.0"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -78,14 +78,14 @@ curl --request PUT \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<FILTER_ID>",
-		"paused": false,
-		"description": "Login from office",
-		"expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<FILTER_ID>",
+    "paused": false,
+    "description": "Login from office",
+    "expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/validation.mdx b/src/content/docs/firewall/api/cf-filters/validation.mdx
index 191219397a1902a..42402810e50cc29 100644
--- a/src/content/docs/firewall/api/cf-filters/validation.mdx
+++ b/src/content/docs/firewall/api/cf-filters/validation.mdx
@@ -10,6 +10,8 @@ description: Validate firewall rule expressions via the API.
 
 The Cloudflare Filters API supports an endpoint for validating expressions.
 
+
+
 ## Examples
 
 ### Validate expression via query string
@@ -22,14 +24,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr?expression=ip.s
 
 ```json title="Response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
-		}
-	],
-	"messages": null
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
+    }
+  ],
+  "messages": null
 }
 ```
 
@@ -55,14 +57,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr" \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
-		}
-	],
-	"messages": null
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
+    }
+  ],
+  "messages": null
 }
 ```
 
diff --git a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
index c396807b1630fa8..493daca2fecd16a 100644
--- a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
+++ b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
@@ -24,9 +24,9 @@ A filter object typically looks like the following:
 
 ```json
 {
-	"id": "<FILTER_ID>",
-	"expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
-	"description": "WordPress login paths via the login page or mobile RPC endpoint"
+  "id": "<FILTER_ID>",
+  "expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
+  "description": "WordPress login paths via the login page or mobile RPC endpoint"
 }
 ```
 
@@ -38,8 +38,8 @@ The expression specified in this example filter is:
 
 This filter expression has a `(this or that) and not this` structure designed to:
 
-- Capture two WordPress paths that may be subject to brute force password attacks, and
-- Exclude traffic that comes from the IP address `93.184.216.34`.
+* Capture two WordPress paths that may be subject to brute force password attacks, and
+* Exclude traffic that comes from the IP address `93.184.216.34`.
 
 Imagine that this is an IP for your office. This expression demonstrates a filter that might be used (in a firewall rule) to block access to the WordPress login when accessed outside the office network.
 
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
index 75c661f0deb8cc4..fa662e947375338 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
@@ -23,70 +23,70 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID_1>",
-			"paused": false,
-			"description": "allow API traffic without challenge",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_1>",
-				"expression": "http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "/api"
-			}
-		},
-		{
-			"id": "<RULE_ID_2>",
-			"paused": false,
-			"description": "do not challenge login from office",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_2>",
-				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login from office"
-			}
-		},
-		{
-			"id": "<RULE_ID_3>",
-			"paused": false,
-			"description": "challenge login",
-			"action": "challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_3>",
-				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login"
-			}
-		},
-		{
-			"id": "<RULE_ID_4>",
-			"paused": false,
-			"description": "Non-interactive challenge site",
-			"action": "js_challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_4>",
-				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "not /api"
-			}
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result_info": {
-		"page": 1,
-		"per_page": 25,
-		"count": 4,
-		"total_count": 4,
-		"total_pages": 1
-	}
+  "result": [
+    {
+      "id": "<RULE_ID_1>",
+      "paused": false,
+      "description": "allow API traffic without challenge",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_1>",
+        "expression": "http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "/api"
+      }
+    },
+    {
+      "id": "<RULE_ID_2>",
+      "paused": false,
+      "description": "do not challenge login from office",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_2>",
+        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login from office"
+      }
+    },
+    {
+      "id": "<RULE_ID_3>",
+      "paused": false,
+      "description": "challenge login",
+      "action": "challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_3>",
+        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login"
+      }
+    },
+    {
+      "id": "<RULE_ID_4>",
+      "paused": false,
+      "description": "Non-interactive challenge site",
+      "action": "js_challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_4>",
+        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "not /api"
+      }
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result_info": {
+    "page": 1,
+    "per_page": 25,
+    "count": 4,
+    "total_count": 4,
+    "total_pages": 1
+  }
 }
 ```
 
@@ -102,21 +102,21 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules/{rule_
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"paused": false,
-		"description": "do not challenge login from office",
-		"action": "allow",
-		"priority": null,
-		"filter": {
-			"id": "<FILTER_ID>",
-			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-			"paused": false,
-			"description": "Login from office"
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "paused": false,
+    "description": "do not challenge login from office",
+    "action": "allow",
+    "priority": null,
+    "filter": {
+      "id": "<FILTER_ID>",
+      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+      "paused": false,
+      "description": "Login from office"
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
index 3c5f3df30b5c373..b3ec7601d83b43b 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
@@ -15,8 +15,10 @@ This example creates several firewall rules using a single API call.
 
 :::note
 
+
 To create a firewall rule you need a [filter](/firewall/api/cf-filters/what-is-a-filter/) identifier (`id`). If you have not created a filter yet, refer to the [Cloudflare Filters API documentation](/firewall/api/cf-filters/).
 
+
 :::
 
 ```bash title="Request"
@@ -58,62 +60,62 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID_1>",
-			"paused": false,
-			"description": "Do not challenge login from office",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_1>",
-				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login from office"
-			}
-		},
-		{
-			"id": "<RULE_ID_2>",
-			"paused": false,
-			"description": "Challenge login",
-			"action": "challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_2>",
-				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login"
-			}
-		},
-		{
-			"id": "<RULE_ID_3>",
-			"paused": false,
-			"description": "Non-interactive challenge site",
-			"action": "js_challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_3>",
-				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "not /api"
-			}
-		},
-		{
-			"id": "<RULE_ID_4>",
-			"paused": false,
-			"description": "Allow API traffic without challenge",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_4>",
-				"expression": "http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "/api"
-			}
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<RULE_ID_1>",
+      "paused": false,
+      "description": "Do not challenge login from office",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_1>",
+        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login from office"
+      }
+    },
+    {
+      "id": "<RULE_ID_2>",
+      "paused": false,
+      "description": "Challenge login",
+      "action": "challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_2>",
+        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login"
+      }
+    },
+    {
+      "id": "<RULE_ID_3>",
+      "paused": false,
+      "description": "Non-interactive challenge site",
+      "action": "js_challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_3>",
+        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "not /api"
+      }
+    },
+    {
+      "id": "<RULE_ID_4>",
+      "paused": false,
+      "description": "Allow API traffic without challenge",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_4>",
+        "expression": "http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "/api"
+      }
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
index 3136c338ab132ce..0d5982f433847fe 100644
--- a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
+++ b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
@@ -73,6 +73,7 @@ While your priority numbering scheme can be arbitrary, keep the following in min
 - **Rules without a priority number are evaluated last**, in order of their action precedence. For example, a rule with the _Log_ action is evaluated before a rule that has the _Block_ action. For more on action precedence, refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/).
 - **Avoid using the number `1` as a priority** to make rule order modification easier in the future.
 - **Consider grouping ranges of priority numbers into categories** that have some meaning for your deployment. Here are some examples:
+
   - 5000-9999: Trusted IP addresses
   - 10000-19999: Blocking rules for bad crawlers
   - 20000-29999: Blocking rules for abusive users/spam
diff --git a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
index 1fb0715951d644a..94c7ab99e5aa858 100644
--- a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
+++ b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
@@ -21,7 +21,7 @@ To enable editing access by your Account Team:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page. (You must be logged in as a **Super Administrator**).
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Editing Permission**, switch the toggle to **On**.
 3. Select a duration.
@@ -29,6 +29,8 @@ To enable editing access by your Account Team:
 
 :::note
 
+
 In an emergency, Cloudflare Support can override your **Editing Permissions** and make updates to your account, but your Super Administrator will receive an email and the action will be recorded in your [Audit Logs](/fundamentals/account/account-security/review-audit-logs/) with an **Action** of **Break glass**.
 
+
 :::
diff --git a/src/content/docs/fundamentals/account/account-security/index.mdx b/src/content/docs/fundamentals/account/account-security/index.mdx
index 774bf0f5dba2826..62434c63a9879ee 100644
--- a/src/content/docs/fundamentals/account/account-security/index.mdx
+++ b/src/content/docs/fundamentals/account/account-security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
index 3f045d04d65881c..44b877f610b9365 100644
--- a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
+++ b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
@@ -14,10 +14,12 @@ Refer to the [blog post](https://blog.cloudflare.com/helping-keep-customers-safe
 
 :::note[Note]
 
+
 Cloudflare does not have additional information about the specific breach or Internet service that potentially lost your password.
 
 Popular online tools such as [Have I Been Pwned](https://haveibeenpwned.com/) can help you better understand where your external accounts were attacked. If you reused this password in other systems, it is recommended that you reset it in those as well.
 
+
 :::
 
 If your password is found in a data breach, we will email you information on how to reset your password and prompt you to do so in the Cloudflare dashboard.
diff --git a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
index be25f61733a7a37..bacbe900335ef0a 100644
--- a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
+++ b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
@@ -18,7 +18,7 @@ To view the active sessions associated with your email address:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 
diff --git a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
index f93945373a085e6..9e379c53fec4c81 100644
--- a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
+++ b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 Zone holds prevent other teams in your organization from adding zones that are already active in another account.
 
@@ -24,7 +24,7 @@ Zone holds are enabled by default for all Enterprise zones.
 
 When you enable a zone hold, no one else can [add your zone](/fundamentals/manage-domains/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
 
-_The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed._
+*The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed.*
 
 To enable a zone hold:
 
diff --git a/src/content/docs/fundamentals/account/create-account.mdx b/src/content/docs/fundamentals/account/create-account.mdx
index e93d05d94fd8d52..cc509b79ec43b6f 100644
--- a/src/content/docs/fundamentals/account/create-account.mdx
+++ b/src/content/docs/fundamentals/account/create-account.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
 
 To create a Cloudflare account:
 
@@ -29,7 +29,7 @@ To change your account name:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page.
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Account Name**, select **Change Name**.
 3. Enter a new account name.
@@ -37,13 +37,13 @@ To change your account name:
 
 ## Best practices
 
-<Render file="create-account-best-practices" product="fundamentals" />
+<Render file="create-account-best-practices" product="fundamentals" /> 
 
-Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain.
+Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain. 
 
 Once you [set up an account](/fundamentals/account/), you have several ways to interact with Cloudflare.
 
-## Interact with Cloudflare
+## Interact with Cloudflare 
 
 If you prefer working without code, you can manage your account and domain settings through the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
@@ -62,3 +62,4 @@ For those who prefer to interact with Cloudflare programmatically, you can use s
 | [cloudflare-go](https://github.com/cloudflare/cloudflare-go)                           | [README](https://github.com/cloudflare/cloudflare-go#readme)         | The official Go library for the Cloudflare API.                                |
 | [cloudflare-typescript](https://github.com/cloudflare/cloudflare-typescript)           | [README](https://github.com/cloudflare/cloudflare-typescript#readme) | The official TypeScript library for the Cloudflare API.                        |
 | [cloudflare-python](https://github.com/cloudflare/cloudflare-python)                   | [README](https://github.com/cloudflare/cloudflare-python#readme)     | The official Python library for the Cloudflare API.                            |
+
diff --git a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
index 535d145aa95d13f..d942475ab7e6765 100644
--- a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
+++ b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
@@ -16,10 +16,10 @@ Once you [set up a new account](/fundamentals/account/) and [add your domain](/f
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button at the end of the account row.
-   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
+![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
 
 3. Select **Copy account ID**.
 
@@ -29,17 +29,17 @@ To copy the account ID when you only have one account:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and locate your account.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button next to your account name.
 3. From the list that appears, select **Copy account ID**.
-   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
+![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
 
 ## Copy your Zone ID
 
 1. In the Cloudflare dashboard, go to the **Account** home and locate your account.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. From the **Overview** page for your account, locate the **API** section towards the bottom of the page.
 
@@ -53,7 +53,7 @@ You can also find your account ID from the **Workers & Pages** section of your a
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
+    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. The **Account details** section contains your **Account ID**.
 3. To copy the Account ID, select **Click to copy**.
diff --git a/src/content/docs/fundamentals/account/index.mdx b/src/content/docs/fundamentals/account/index.mdx
index ed12e22c5045241..78335a849e9c2ba 100644
--- a/src/content/docs/fundamentals/account/index.mdx
+++ b/src/content/docs/fundamentals/account/index.mdx
@@ -10,7 +10,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 If you need help setting up a new Cloudflare account, refer to the following resources:
 
diff --git a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
index 692fcea9aa69c90..90ef1f2f6f50643 100644
--- a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
+++ b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
@@ -21,7 +21,7 @@ To restrict the API access for the entire account:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Locate the **Enable API Access** section and then update the setting.
 
@@ -29,14 +29,16 @@ To restrict the API access for the entire account:
 
 :::note
 
+
 Member-level settings will override the account-level setting. If a specific member has API access enabled whereas the account has the access disabled, that member can still call APIs related to the Enterprise account.
 
+
 :::
 
 To restrict the API access for a specific member:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Click on the member to expand and choose the intended **API Access**. If `Account Default`, then it follows the account level setting.
diff --git a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
index 8f1f58e538d2e66..f58ab298b5d15c4 100644
--- a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
+++ b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
@@ -114,20 +114,24 @@ To fetch all available permission groups and their IDs, use the [List permission
 
 ```json output
 {
-	"result": [
-		{
-			"id": "19637fbb73d242c0a92845d8db0b95b1",
-			"name": "AI Crawl Control Read",
-			"description": "Grants access to reading AI Crawl Control",
-			"scopes": ["com.cloudflare.api.account.zone"]
-		},
-		{
-			"id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
-			"name": "AI Crawl Control Write",
-			"description": "Grants access to reading and editing AI Crawl Control",
-			"scopes": ["com.cloudflare.api.account.zone"]
-		}
-		// (...)
+  "result": [
+    {
+      "id": "19637fbb73d242c0a92845d8db0b95b1",
+      "name": "AI Crawl Control Read",
+      "description": "Grants access to reading AI Crawl Control",
+      "scopes": [
+        "com.cloudflare.api.account.zone"
+      ]
+    },
+    {
+      "id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
+      "name": "AI Crawl Control Write",
+      "description": "Grants access to reading and editing AI Crawl Control",
+      "scopes": [
+        "com.cloudflare.api.account.zone"
+      ]
+    },
+    // (...)
 	]
 }
 ```
diff --git a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
index 487d294ea4ff9cf..d084a748cb05a70 100644
--- a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
+++ b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
@@ -11,8 +11,8 @@ products:
 
 API tokens can be restricted at runtime in two ways:
 
-- [Client IP address range filtering](#client-ip-address-range-filtering)
-- [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
+* [Client IP address range filtering](#client-ip-address-range-filtering)
+* [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
 
 ## Client IP address range filtering
 
@@ -26,14 +26,17 @@ Client IP address range filtering is not applied to the [Verify Token](https://d
 
 :::
 
+
 ## Time to live (TTL) constraints
 
 By default, tokens do not expire and are long lived. Defining a TTL sets when a token starts being valid and when a token is no longer valid. This is often referred to as `notBefore` and `notAfter`. Setting these timestamps limits the lifetime of the token to the defined period. Not setting the start date or `notBefore` means the token is active as soon as it is created. Not setting the end date or `notAfter` means the token does not expire.
 
 :::note
 
+
 Dates selected are defined as 00:00 UTC of that day. For finer grained time selection, use the [API](/fundamentals/api/).
 
+
 :::
 
 ![Time to Live selection calendar](~/assets/images/fundamentals/api/ttl.png)
diff --git a/src/content/docs/fundamentals/api/index.mdx b/src/content/docs/fundamentals/api/index.mdx
index 5c920d17b99595e..fc2b5ca4dd7c1ca 100644
--- a/src/content/docs/fundamentals/api/index.mdx
+++ b/src/content/docs/fundamentals/api/index.mdx
@@ -11,7 +11,7 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use the following resources to learn more about Cloudflare's REST API:
 
diff --git a/src/content/docs/fundamentals/api/reference/index.mdx b/src/content/docs/fundamentals/api/reference/index.mdx
index 51171664a4e68eb..2b69ab6e04041ec 100644
--- a/src/content/docs/fundamentals/api/reference/index.mdx
+++ b/src/content/docs/fundamentals/api/reference/index.mdx
@@ -11,6 +11,6 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/api/reference/limits.mdx b/src/content/docs/fundamentals/api/reference/limits.mdx
index af4f24a26742004..056310a63a2cf5e 100644
--- a/src/content/docs/fundamentals/api/reference/limits.mdx
+++ b/src/content/docs/fundamentals/api/reference/limits.mdx
@@ -11,11 +11,7 @@ products:
 
 import { Render } from "~/components";
 
-<Render
-	file="api-rate-limits"
-	product="fundamentals"
-	params={{ showHeading: true }}
-/>
+<Render file="api-rate-limits" product="fundamentals"  params={{showHeading: true}} />
 
 ## Rate limiting headers
 
diff --git a/src/content/docs/fundamentals/api/troubleshooting.mdx b/src/content/docs/fundamentals/api/troubleshooting.mdx
index 442eb608d3525d0..f1b15f7ee9bdbf6 100644
--- a/src/content/docs/fundamentals/api/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/api/troubleshooting.mdx
@@ -23,15 +23,15 @@ curl "https://api.cloudflare.com/client/v4/user/tokens/verify" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "f267e341f3dd4697bd3b9f71dd96247f",
-		"status": "active",
-		"not_before": "2018-07-01T05:20:00Z",
-		"expires_on": "2020-01-01T00:00:00Z"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "f267e341f3dd4697bd3b9f71dd96247f",
+    "status": "active",
+    "not_before": "2018-07-01T05:20:00Z",
+    "expires_on": "2020-01-01T00:00:00Z"
+  }
 }
 ```
 
diff --git a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
index 7bb8ee6aba29a4d..fc8a96817900340 100644
--- a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
+++ b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
@@ -8,15 +8,11 @@ products:
   - fundamentals
 ---
 
-import { Stream, GlossaryTooltip } from "~/components";
+import { Stream, GlossaryTooltip } from "~/components"
 
 To optimize your website or web application, Cloudflare provides [DNS](https://www.cloudflare.com/learning/dns/what-is-dns/) and [CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) services, so we can [reverse proxy](https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/) the web traffic to and from your domain.
 
-<Stream
-	id="980c8494f2403b95473d2ed687b4f402"
-	title="How Cloudflare DNS works for your domain"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public"
-/>
+<Stream id="980c8494f2403b95473d2ed687b4f402" title="How Cloudflare DNS works for your domain" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public" />
 
 ## DNS explained
 
diff --git a/src/content/docs/fundamentals/concepts/index.mdx b/src/content/docs/fundamentals/concepts/index.mdx
index 52496a8fd9b8022..6a64b49f7e2d8a3 100644
--- a/src/content/docs/fundamentals/concepts/index.mdx
+++ b/src/content/docs/fundamentals/concepts/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
index ffb08d179a6080f..31af11a5ba634c1 100644
--- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
+++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
@@ -10,7 +10,7 @@ products:
 
 Internet traffic is made up of people, services, and agents requesting online resources from wherever they are hosted. Your resources may be publicly available, like a website or application that anyone on the Internet can access. Or your resources may be privately available, like an internal app or network that only your employees and partners should be able to access.
 
-Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.
+Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.  
 
 For example, you may not always want the direct traffic because it can come from malicious sources, like hackers, or in the form of [DDoS attacks](https://www.cloudflare.com/learning/ddos/ddos-attack-tools/how-to-ddos/). Additionally, depending on the location where the request originated, you want to ensure the traffic is [routed through the most efficient and fastest path](/argo-smart-routing/).
 
@@ -36,18 +36,18 @@ One example of on-ramping traffic to Cloudflare is updating your public website
 
 However, maybe you need to protect a private application that is not directly available on the Internet. In this scenario, you can:
 
-- Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
-- For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
+* Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
+* For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
 
 With these options, any request from a user device can access internal private applications via the secure private tunnels.
 
 Refer to the list below for products you can use to on-ramp traffic to Cloudflare.
 
-- [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
-- [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
-- [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
-- [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
-- The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
+* [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
+* [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
+* [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
+* [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
+* The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
 
 ### Off-ramp traffic from Cloudflare
 
@@ -61,6 +61,6 @@ You can also utilize [caching](/cache/) to help with performance. Instead of off
 
 Refer to the list below for products you can use to off-ramp traffic from Cloudflare.
 
-- [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
-- [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
-- [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
+* [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
+* [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
+* [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/index.mdx b/src/content/docs/fundamentals/index.mdx
index 6da0f6862aab3d2..4fbceb5e645cec0 100644
--- a/src/content/docs/fundamentals/index.mdx
+++ b/src/content/docs/fundamentals/index.mdx
@@ -24,6 +24,6 @@ Refer to the list below for additional Cloudflare resources.
 - [Cloudflare blog](https://blog.cloudflare.com)
 - [Cloudflare's Go library](https://github.com/cloudflare/cloudflare-go)
 - [Cloudflare system status](https://www.cloudflarestatus.com/)
-- [Cloudflare Radar](https://radar.cloudflare.com)
-- [Cloudflare TV](https://cloudflare.tv/schedule)
+- [Cloudflare Radar](https://radar.cloudflare.com) 
+- [Cloudflare TV](https://cloudflare.tv/schedule) 
 - [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
diff --git a/src/content/docs/fundamentals/manage-domains/add-site.mdx b/src/content/docs/fundamentals/manage-domains/add-site.mdx
index e089a041cbe43bc..081c4aeb68c902e 100644
--- a/src/content/docs/fundamentals/manage-domains/add-site.mdx
+++ b/src/content/docs/fundamentals/manage-domains/add-site.mdx
@@ -7,13 +7,7 @@ products:
   - fundamentals
 ---
 
-import {
-	DashButton,
-	GlossaryTooltip,
-	Render,
-	Stream,
-	Details,
-} from "~/components";
+import { DashButton, GlossaryTooltip, Render, Stream, Details } from "~/components";
 
 After you onboard your domain, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
 
@@ -83,7 +77,6 @@ If you encounter unexpected results when changing your nameservers, refer to the
 ## Further options
 
 ### Other DNS setups
-
 - To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/).
 - To use one or more DNS providers, refer to [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
 - Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
@@ -96,4 +89,4 @@ If you encounter unexpected results when changing your nameservers, refer to the
 
 [^2]: Enterprise customers can onboard these using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
 
-[^3]: A security feature that protects DNS records from spoofing
+[^3]: A security feature that protects DNS records from spoofing
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/manage-domains/domain-version.mdx b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
index 80c3dfce25a53ae..124534a2bf1c4e0 100644
--- a/src/content/docs/fundamentals/manage-domains/domain-version.mdx
+++ b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
@@ -8,25 +8,28 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 [Version Management](/version-management/) is available for Enterprise customers and allows you to safely test, deploy, and roll back changes to your zone configurations.
 
+
 ## Enable versioning
 
+
 <Render file="enable-versioning" product="version-management" />
 
+
 ## (Optional) Create additional environments
 
 <Render file="enable-default-creation" product="version-management" />
 
 These environments each serve a specific purpose and are accessed differently: <Render file="environment-defaults" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" />
-<br />
+<Render file="create-environment-situation" product="version-management" /> <br/>
 
 For more details, refer to [Create environment](/version-management/how-to/environments/#create-environment).
 
+
 ## Update configurations
 
 <Render file="edit-version" product="version-management" />
@@ -37,6 +40,7 @@ For more details, refer to [Create environment](/version-management/how-to/envir
 
 ## Promote version
 
+
 Next, [promote](/version-management/how-to/environments/#change-environment-version) your version through your different environments.
 
 <Render file="promote-version" product="version-management" />
@@ -46,3 +50,5 @@ After promoting to each environment, test the new version in your new environmen
 ## Repeat
 
 For new changes to your zone, [create a new version](/version-management/how-to/versions/#create-version) and repeat this process.
+
+
diff --git a/src/content/docs/fundamentals/manage-domains/move-domain.mdx b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
index 554db841218b10c..adb048fe514eab7 100644
--- a/src/content/docs/fundamentals/manage-domains/move-domain.mdx
+++ b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
@@ -30,11 +30,13 @@ To transfer a domain from one Cloudflare account to another, you will need:
 
 :::caution
 
+
 Before transferring an active Cloudflare domain to another Cloudflare account, you must remove any [DNSSEC configurations](/dns/dnssec/) and [add-ons or subscriptions](/billing/manage/cancel-subscription/).
 
 We also recommend [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records of your zone while it is in the previous account. Then, you can [import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the correct DNS records into the new account.
 If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
+
 :::
 
 If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](#issue-new-certificates) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
diff --git a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
index 8887da35f668294..1ac459d5abe6896 100644
--- a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
+++ b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
@@ -12,7 +12,7 @@ To troubleshoot your site, you can pause Cloudflare globally. This will send tra
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and domain.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Within **Overview**, choose **Advanced Actions** > **Pause Cloudflare on Site**.
 
@@ -22,7 +22,7 @@ The process of pausing Cloudflare takes five minutes or less. This approach is p
 Disabling a zone does not impact Spectrum applications.
 :::
 
----
+***
 
 ## Alternatives to global pause
 
diff --git a/src/content/docs/fundamentals/manage-members/index.mdx b/src/content/docs/fundamentals/manage-members/index.mdx
index 349b6e8ec38dafd..854f89c1e4e7eca 100644
--- a/src/content/docs/fundamentals/manage-members/index.mdx
+++ b/src/content/docs/fundamentals/manage-members/index.mdx
@@ -12,7 +12,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 On any Cloudflare account, you can collaborate by adding members to your account and assigning them access via one or several policies.
 
diff --git a/src/content/docs/fundamentals/manage-members/policies.mdx b/src/content/docs/fundamentals/manage-members/policies.mdx
index 36f550450d46ae3..6ca9aafa9521ce1 100644
--- a/src/content/docs/fundamentals/manage-members/policies.mdx
+++ b/src/content/docs/fundamentals/manage-members/policies.mdx
@@ -27,8 +27,8 @@ For example, you may want to assign multiple policies and use scopes to control
 
 A set of standard API endpoints is present on every account that allow access to your members, which has recently been enhanced by a list of `resourceGroups` and `PermissionGroups`.
 
-- A `resourceGroup` is a unique identifier for the scope for which a policy applies.
-- A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
+* A `resourceGroup` is a unique identifier for the scope for which a policy applies.
+* A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
 
 Refer to the [API documentation](/api/) for more information.
 
@@ -44,3 +44,4 @@ To understand a member’s full access, check both the **Members** and **User Gr
 
 Cloudflare is actively working on improvements to consolidate this view in a future update.
 :::
+
diff --git a/src/content/docs/fundamentals/manage-members/roles.mdx b/src/content/docs/fundamentals/manage-members/roles.mdx
index e6e4019dccc01f9..c7a01704fb29721 100644
--- a/src/content/docs/fundamentals/manage-members/roles.mdx
+++ b/src/content/docs/fundamentals/manage-members/roles.mdx
@@ -28,7 +28,7 @@ Account-scoped roles apply across an entire Cloudflare account, and through all
 | Application Security Reports Read                            | Can read Application Security Reports.                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audit Logs Viewer                                            | Can view [Audit Logs](/fundamentals/account/account-security/review-audit-logs/).                                                                                                                                                                                                                                                                                                                                                 |
 | Bot Management (Account-Wide)                                | Can edit [Bot Management](/bots/plans/bm-subscription/) (including [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/)) configurations for all domains in account.                                                                                                                                                                                                                                                    |
-| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                          |
+| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                                      |
 | Cache Purge                                                  | Can purge the edge cache and allows the reading of zone settings.                                                                                                                                                                                                                                                                                                                                                                 |
 | Cloudflare Access                                            | Can edit [Cloudflare Access](/cloudflare-one/access-controls/policies/) and [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).                                                                                                                                                                                                                                                                          |
 | Cloudflare CASB                                              | Can edit [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/fundamentals/manage-members/scope.mdx b/src/content/docs/fundamentals/manage-members/scope.mdx
index e75d47dafac71c1..ecfacf62744dfa0 100644
--- a/src/content/docs/fundamentals/manage-members/scope.mdx
+++ b/src/content/docs/fundamentals/manage-members/scope.mdx
@@ -19,7 +19,7 @@ To allow for flexible combinations of access to users, Cloudflare currently has
 - **Domain groups:** Use when you have related domains that share the same access needs, for example, all production domains.
 - **Specific resources:** Use when access should be limited to individual resources.
 
----
+***
 
 ## Choose the scope of roles
 
@@ -33,13 +33,15 @@ If you want the member to have a policy that applies across your account, use th
 
 | Field    | Value         |
 | -------- | ------------- |
-| Operator | _Include_     |
-| Type     | _All domains_ |
+| Operator | *Include*     |
+| Type     | *All domains* |
 
 :::note
 
+
 You can only assign [account-scoped roles](/fundamentals/manage-members/roles/#account-scoped-roles) as part of these types of policies
 
+
 :::
 
 ### Specific domains
@@ -48,9 +50,9 @@ If you want the member to have a policy that applies to a specific domain, use t
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | _Include_           |
-| Type     | _A specific domain_ |
-| Name     | _A specific domain_ |
+| Operator | *Include*           |
+| Type     | *A specific domain* |
+| Name     | *A specific domain* |
 
 ### Domain groups
 
@@ -62,10 +64,11 @@ To create a domain group:
 
 1. In the Cloudflare dashboard, go to the **Settings** > **Lists** page. (You must be logged in as a **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/)).
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Domain Group Manager**, select **Create**.
 3. Create your domain group:
+
    1. Select the domains to include.
    2. Add a **Name**.
    3. Select **Create**.
@@ -78,40 +81,43 @@ To assign a member permissions to a domain group, use the following combination
 
 | Field    | Value           |
 | -------- | --------------- |
-| Operator | _Include_       |
-| Type     | _Domain Group_  |
-| Name     | _Example Group_ |
+| Operator | *Include*       |
+| Type     | *Domain Group*  |
+| Name     | *Example Group* |
 
 :::note
 
+
 With Domain Groups, you can only assign [domain-scoped roles](/fundamentals/manage-members/roles/#domain-scoped-roles) to these members.
 
+
 :::
 
+
 ### Specific resources
 
 If you want the member to have a policy that applies to a specific resource, use the following combination of fields.
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | _Include_           |
-| Type     | _Granular_          |
-| Product  | _Product Name_      |
-| Resource | _Specific Resource_ |
+| Operator | *Include*           |
+| Type     | *Granular* |
+| Product  | *Product Name* |
+| Resource  | *Specific Resource* |
 
 #### Available scopes
 
 You can assign the following resource-specific scopes to members:
 
-| Scope                                       | Description                                                                                                                                       |
-| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Individual Access applications              | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                            |
-| Individual Access identity providers (IdPs) | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                     |
-| Individual Access policies                  | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                     |
-| Individual Access service tokens            | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                    |
-| Individual Access infrastructure targets    | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/). |
-| Individual Cloudflare Tunnel instances      | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                         |
-| Individual Cloudflare Mesh nodes            | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                   |
+| Scope                                     | Description                                                                                                                                              |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Individual Access applications               | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                                   |
+| Individual Access identity providers (IdPs)  | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                                    |
+| Individual Access policies                   | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                            |
+| Individual Access service tokens             | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                           |
+| Individual Access infrastructure targets     | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/).        |
+| Individual Cloudflare Tunnel instances       | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                                |
+| Individual Cloudflare Mesh nodes             | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                          |
 
 :::note
 When using scopes for specific resources, you can only assign [resource-scoped roles](/fundamentals/manage-members/roles/#resource-scoped-roles) to these members.
diff --git a/src/content/docs/fundamentals/manage-members/user-groups.mdx b/src/content/docs/fundamentals/manage-members/user-groups.mdx
index ac0ff7d261fe721..6ac8ab7b5b960bc 100644
--- a/src/content/docs/fundamentals/manage-members/user-groups.mdx
+++ b/src/content/docs/fundamentals/manage-members/user-groups.mdx
@@ -10,9 +10,9 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Tabs, TabItem } from "~/components";
+import { DashButton, Tabs, TabItem } from '~/components';
 
-User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of.
+User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of. 
 
 :::note
 User Group permissions are inherited by each member of the group but are not currently reflected in the role field on the **Members** page. To view a member’s full set of permissions, check both:
@@ -23,21 +23,21 @@ User Group permissions are inherited by each member of the group but are not cur
 Cloudflare is actively working on improving this experience to make inherited and direct permissions easier to view.
 :::
 
-## Create a User Group manually
+## Create a User Group manually 
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Select the **Groups** tab.
 3. Select **Create a Group** and enter a name and description for your new group.
 4. Select **Create group** to confirm your changes. The **Group members** tab displays.
-5. Select **Add members**.
+5. Select **Add members**. 
 6. Select the relevant members you want to include in the group and select **Add to Group**.
 
 ### Assign a Permission Policy
 
-With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group.
+With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group. 
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -86,23 +86,24 @@ PAYLOAD
 
 ## Create a User Group with SCIM
 
-Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account.
+Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account. 
+
 
 :::note
 If you use the [Cloudflare dashboard SCIM integration](/fundamentals/account/account-security/scim-setup/), you can sync Groups from an upstream Identity Provider. This allows you to centralize user and group management at your identity provider.
 
 Note that when managing User Groups via SCIM:
-
-- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API.
+- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API. 
 - The integration requires one external SCIM application per Cloudflare account.
 - Cloudflare does not currently support updating user profile fields (`firstName`, `lastName`, or `email`) via SCIM. If those attributes change in your IdP, they will not be updated in Cloudflare. These values are only set during initial provisioning.
-  :::
+:::
+
 
 To set up a user group with SCIM, refer to the [Provisioning with SCIM guide](/fundamentals/account/account-security/scim-setup/).
 
 ### Set up permissions for User Groups
 
-After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it.
+After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it. 
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/docs/fundamentals/new-features/index.mdx b/src/content/docs/fundamentals/new-features/index.mdx
index 00ba70c15225ddb..8f052702ba7fe7e 100644
--- a/src/content/docs/fundamentals/new-features/index.mdx
+++ b/src/content/docs/fundamentals/new-features/index.mdx
@@ -10,8 +10,8 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare offers several RSS feeds to help you consume content programmatically.
 
-<DirectoryListing />
+<DirectoryListing/>
diff --git a/src/content/docs/fundamentals/organizations/limitations.mdx b/src/content/docs/fundamentals/organizations/limitations.mdx
index 037c78efb4df0b2..732b548986c8775 100644
--- a/src/content/docs/fundamentals/organizations/limitations.mdx
+++ b/src/content/docs/fundamentals/organizations/limitations.mdx
@@ -14,7 +14,7 @@ The following limitations apply during the public beta.
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Organization creation   | You must be a Super Administrator of an Enterprise account to create an Organization.                                                                                                       |
 | Adding accounts         | Once you've created an Organization, accounts of any plan type can be added. You must have Super Administrator access to the account, and it cannot already belong to another Organization. |
-| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                              |
+| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                                |
 | Roles                   | Organization Super Administrator is the only role available during the beta. Additional roles will be available in a future release.                                                        |
-| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                                              |
+| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                       |
 | Account removal         | Self-service account removal is not yet available. To remove an account from your Organization, contact [Cloudflare Support](/support/contacting-cloudflare-support/).                      |
diff --git a/src/content/docs/fundamentals/organizations/setup.mdx b/src/content/docs/fundamentals/organizations/setup.mdx
index cb9c27ffabafa59..3cb26686125e379 100644
--- a/src/content/docs/fundamentals/organizations/setup.mdx
+++ b/src/content/docs/fundamentals/organizations/setup.mdx
@@ -101,11 +101,11 @@ You can manage Organizations using the [Cloudflare Terraform provider](https://r
 
 You may encounter the following errors during the setup flow. Please see below for more information on how to resolve these.
 
-| Error                                                                                                                                                | Description                                                                                                                                                                                                              |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Organization management is only available on the Enterprise plan at this time.                                                                       | You are not a member of any Enterprise accounts.                                                                                                                                                                         |
-| You need a super admin role on an enterprise account to create an Organization.                                                                      | You are not a Super Administrator of an Enterprise account.                                                                                                                                                              |
-| One or more of your enterprise accounts is already part of an Organization.                                                                          | You may not create another organization because your accounts are already in an organization.                                                                                                                            |
-| You have reached the maximum number of organizations.                                                                                                | You may not create another organization because you already have one.                                                                                                                                                    |
-| An Organization has already been created for accounts associated with your company. Please contact your company administrator.                       | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
-| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it. | This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data.                  |
+| Error | Description |
+| --- | --- |
+| Organization management is only available on the Enterprise plan at this time. | You are not a member of any Enterprise accounts. |
+| You need a super admin role on an enterprise account to create an Organization. | You are not a Super Administrator of an Enterprise account. |
+| One or more of your enterprise accounts is already part of an Organization. | You may not create another organization because your accounts are already in an organization. |
+| You have reached the maximum number of organizations. | You may not create another organization because you already have one. |
+| An Organization has already been created for accounts associated with your company. Please contact your company administrator. | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
+| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it.| This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data. |
diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx
index aa834449efa4ed4..297c524991656ee 100644
--- a/src/content/docs/fundamentals/performance/improve-seo.mdx
+++ b/src/content/docs/fundamentals/performance/improve-seo.mdx
@@ -12,8 +12,10 @@ In practice, SEO is primarily about quality content, user experience, and not ma
 
 :::note[Tip:]
 
+
 For general guidelines around SEO, refer to [Google's recommendations](https://developers.google.com/search/docs/advanced/guidelines/overview).
 
+
 :::
 
 ## SEO improvements with Cloudflare
@@ -45,9 +47,9 @@ Depending on your domain's security settings, you might accidentally block searc
 
 If you notice SEO issues, make sure your:
 
-- [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
-- [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
-- [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
+* [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
+* [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
+* [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
 
 If you still notice issues with search engine crawlers, refer to our [Troubleshooting guide](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/).
 
@@ -55,7 +57,7 @@ If you still notice issues with search engine crawlers, refer to our [Troublesho
 
 The following characteristics do not affect your domain's SEO:
 
-- **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
-- **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
-- **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
-- **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
+* **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
+* **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
+* **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
+* **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
diff --git a/src/content/docs/fundamentals/performance/index.mdx b/src/content/docs/fundamentals/performance/index.mdx
index 8c00c87f68d593b..4fa36b844e2eec8 100644
--- a/src/content/docs/fundamentals/performance/index.mdx
+++ b/src/content/docs/fundamentals/performance/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/performance/test-speed.mdx b/src/content/docs/fundamentals/performance/test-speed.mdx
index 246a968ab7ae1c4..12ea8823571be55 100644
--- a/src/content/docs/fundamentals/performance/test-speed.mdx
+++ b/src/content/docs/fundamentals/performance/test-speed.mdx
@@ -8,7 +8,7 @@ products:
 
 Cloudflare offers several tools to test the speed of your website, as well as the speed of your Internet connection.
 
----
+***
 
 ## Test website speed
 
@@ -24,11 +24,11 @@ If you experience any issues, make sure you are not blocking specific [user agen
 
 If your domain is not yet active on Cloudflare or you want to measure the before and after improvements of using Cloudflare, Cloudflare recommends using the following third-party tools:
 
-- [PageGym](https://pagegym.com/)
-- [GTmetrix](https://gtmetrix.com/)
-- [DebugBear](https://www.debugbear.com/test/website-speed)
-- [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
-- [WebPageTest](https://www.webpagetest.org/)
+* [PageGym](https://pagegym.com/)
+* [GTmetrix](https://gtmetrix.com/)
+* [DebugBear](https://www.debugbear.com/test/website-speed)
+* [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
+* [WebPageTest](https://www.webpagetest.org/)
 
 If you use these third-party tools, you should do the following to test website speed:
 
@@ -46,11 +46,13 @@ Based on the results of these speed tests, you may want to explore other ways to
 
 :::note
 
+
 Cloudflare does not consider Time to First Byte (TTFB) the most important measure of page load speed. If you are concerned about a slower TTFB while using Cloudflare, refer to our blog post about [Cloudflare and TTFB](http://blog.cloudflare.com/ttfb-time-to-first-byte-considered-meaningles/).
 
+
 :::
 
----
+***
 
 ## Test Internet speed
 
diff --git a/src/content/docs/fundamentals/reference/best-practices.mdx b/src/content/docs/fundamentals/reference/best-practices.mdx
index 6d8aa19d844e6f7..a237a1d635c541d 100644
--- a/src/content/docs/fundamentals/reference/best-practices.mdx
+++ b/src/content/docs/fundamentals/reference/best-practices.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account.
+More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account. 
 
 You can lose access to your account and or domain for several reasons: Death, divorce, disgruntled employee, or simply missing an email notification.
 
@@ -19,7 +19,7 @@ To help prevent loss of access:
 
 ## Relationships, partnerships, and business ventures
 
-Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active.
+Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active. 
 
 If you have a domain name or a portfolio of domain names for your business, ensuring you have a strict organization policy when it comes to vendor account creation or domain name registration is critical. The steps below will ensure your organization is the owner of the account and or domain names:
 
@@ -37,4 +37,4 @@ Most if not all online services have automated billing processes that will attem
 
 ## Deceased account holder or registrant
 
-While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you.
+While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you. 
diff --git a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
index 070a9aa8b37e5a3..f040e11a6251600 100644
--- a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
+++ b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
@@ -12,12 +12,12 @@ This endpoint is managed and served by Cloudflare. It cannot be modified or cust
 
 A few examples include (but are not limited to):
 
-- [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
-- [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
-- [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
-- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
-- [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
-- [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
+* [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
+* [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
+* [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
+* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
+* [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
+* [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
 
 ## Recommended exclusions
 
diff --git a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
index e99011bb53a7c81..dd7a00e47dce594 100644
--- a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
+++ b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
@@ -13,6 +13,7 @@ Ray IDs are particularly useful when evaluating Security Events for patterns or
 Ray IDs are added as a [request header, cf-ray](/fundamentals/reference/http-headers/#cf-ray), to the connection from Cloudflare to the origin web server.
 As such the Ray IDs can be found using the Developer Tools in your browser or using curl with the `-v` option to show the headers.
 
+
 :::caution
 Ray IDs are not guaranteed to be unique for every request. In some situations, different requests may have the same Ray ID.
 :::
@@ -33,7 +34,7 @@ Please note that Security Events may use sampled data to improve performance. If
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer allows you to [build queries](/log-explorer/log-search/) for filtering specific Ray IDs.
 
diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
index 4d7916b94c2550d..5a3fae1ade1c6bd 100644
--- a/src/content/docs/fundamentals/reference/connection-limits.mdx
+++ b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), there are often two established [TCP connections](/fundamentals/reference/tcp-connections/): the first is between the requesting client to Cloudflare and the second is between Cloudflare and the origin server. Each connection has their own set of TCP and HTTP limits, which are documented below.
 
@@ -24,16 +24,16 @@ When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/h
 If you are using [Cloudflare tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), refer to [Origin configuration](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) to view or modify your connection settings.
 :::
 
-| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                          | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits)        |
-| ----------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/) |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | No                                                                                    |
-| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                  | Yes                                                                                   |
-| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                 | No                                                                                    |
+| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
+| ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/)                       |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | No                                                                             |
+| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
+| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
 
 ## Configurable limits
 
diff --git a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
index d4c1619380433f2..d1039a6ef7988a6 100644
--- a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
+++ b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
@@ -32,11 +32,11 @@ Yes, Cloudflare does collect a limited amount of data about your key. We store t
 
 Some self-signed keys and keys from certain manufacturers have been found to [not meet this requirement](https://www.chromium.org/security-keys) and should be avoided if you are minimizing your online privacy risk.
 
----
+***
 
 For more details on how we set up Cryptographic Attestation of Personhood, refer to the [introductory blog post](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/).
 
----
+***
 
 ## What devices are and are not allowed?
 
@@ -44,21 +44,21 @@ For more details on how we set up Cryptographic Attestation of Personhood, refer
 
 CAP supports a wide variety of hardware authenticators:
 
-- **Roaming (cross-platform) authenticators**:
-  - _Supported_: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
-  - _Examples_: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
-- **Platform authenticators:**
-  - _Examples_: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
+* **Roaming (cross-platform) authenticators**:
+  * *Supported*: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
+  * *Examples*: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
+* **Platform authenticators:**
+  * *Examples*: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
 
 ### Known limitations
 
 Most combinations of of web browsers and WebAuthn-capable authenticators will work, but there are some known compatibility issues with WebAuthn attestation that may prevent CAP from working successfully:
 
-- **Basic CAP**:
-  - _macOS desktop_: For TouchID, browser must be Safari
-  - _Android_: Browser must be Chrome
-- **CAP with Zero-Knowledge Proof**:
-  - _Apple platform authenticators_ (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
+* **Basic CAP**:
+  * *macOS desktop*: For TouchID, browser must be Safari
+  * *Android*: Browser must be Chrome
+* **CAP with Zero-Knowledge Proof**:
+  * *Apple platform authenticators* (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
 
 We are updating this list as the ecosystem evolves and as we continue to test different combinations.
 
@@ -74,16 +74,16 @@ If you do not have the necessary hardware (such as a Yubikey), you can still sol
 
 ## What are the common error codes and what do they mean?
 
-- **Unsupported_att_fmt**:
-  - _Cause_: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use _Firefox_ and select the option to "anonymise your key".
-  - _Solution:_ If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
-- **Unsupported_issuer**:
-  - _Cause_: Your key is currently not supported.
-  - _Solution_: Use a [supported key](#allowed-devices).
+* **Unsupported\_att\_fmt**:
+  * *Cause*: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use *Firefox* and select the option to "anonymise your key".
+  * *Solution:* If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
+* **Unsupported\_issuer**:
+  * *Cause*: Your key is currently not supported.
+  * *Solution*: Use a [supported key](#allowed-devices).
 
 ## Related resources
 
-- [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
-- [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
-- [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
-- [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
+* [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
+* [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
+* [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
+* [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
diff --git a/src/content/docs/fundamentals/reference/glossary.mdx b/src/content/docs/fundamentals/reference/glossary.mdx
index 0656993c5d88b81..32fb01bd11d1fa6 100644
--- a/src/content/docs/fundamentals/reference/glossary.mdx
+++ b/src/content/docs/fundamentals/reference/glossary.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's documentation.
 
diff --git a/src/content/docs/fundamentals/reference/google-analytics.mdx b/src/content/docs/fundamentals/reference/google-analytics.mdx
index 1e67ecfa7422f9b..2f936dae6e12865 100644
--- a/src/content/docs/fundamentals/reference/google-analytics.mdx
+++ b/src/content/docs/fundamentals/reference/google-analytics.mdx
@@ -19,8 +19,10 @@ Cloudflare only affects analytics tools that read logs directly from your web se
 
 :::note
 
+
 To troubleshoot potential issues with Google Analytics, refer to [Common GA setup mistakes](https://support.google.com/analytics/answer/1009683).
 
+
 :::
 
 ## Zaraz
@@ -29,6 +31,8 @@ As an alternative to the standard setup of Google Analytics with tag/snippet, Cl
 
 :::note
 
+
 Details about features of Google Analytics that are unavailable with Zaraz can be found in [Zaraz FAQ](/zaraz/faq/#tools)
 
+
 :::
diff --git a/src/content/docs/fundamentals/reference/index.mdx b/src/content/docs/fundamentals/reference/index.mdx
index e239c0c053a0085..edf24d7ad793faf 100644
--- a/src/content/docs/fundamentals/reference/index.mdx
+++ b/src/content/docs/fundamentals/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
index 1587fb70d0d1b81..15fcb26bc9607e2 100644
--- a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
+++ b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
@@ -10,15 +10,14 @@ products:
   - fundamentals
 ---
 
-Cloudflare's first iteration of SCIM integration introduced a concept called _Virtual Groups_, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.
-
-While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:
+Cloudflare's first iteration of SCIM integration introduced a concept called *Virtual Groups*, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.  
 
+While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:  
 - They could not be renamed or deleted in the IdP.
 - They could not be managed within Cloudflare.
 - Functionally, managing a Virtual Group was equivalent to syncing users and editing each member’s policies individually.
 
-With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.
+With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.  
 
 If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtual Group from your IdP to Cloudflare, no action is needed.
 
@@ -33,7 +32,9 @@ If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtua
 
 ## More resources
 
-- [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)
-- [User Groups documentation](/fundamentals/manage-members/user-groups/)
-- [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)
-- [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)
+* [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)  
+* [User Groups documentation](/fundamentals/manage-members/user-groups/)  
+* [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)  
+* [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)  
+
+
diff --git a/src/content/docs/fundamentals/reference/partners.mdx b/src/content/docs/fundamentals/reference/partners.mdx
index a066448644a58cd..5e6be4d2e93fd82 100644
--- a/src/content/docs/fundamentals/reference/partners.mdx
+++ b/src/content/docs/fundamentals/reference/partners.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 [Cloudflare Technology Partners](https://www.cloudflare.com/partners/technology-partners/) offer purpose-built integrations with our products, providing expanded functionality for our users. Learn how to configure these integrations with our tutorials and how-to guides.
 
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
index 106282e9575100c..7e65a2e16b6a01a 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
@@ -17,7 +17,7 @@ Unfortunately, while most people respect these limitations and understand they e
 
 The following are some recommendations for using Cloudflare's services based on what may have brought you to this page.
 
----
+***
 
 ## I'm a website operator and my content was redirected for Terms of Service violations
 
@@ -25,9 +25,9 @@ If you are on a Free, Pro, or Business Plan and your application appears to be s
 
 ## Options for web admins to remove redirects
 
-- **Serve redirected content from a grey-clouded sub-domain**
+* **Serve redirected content from a grey-clouded sub-domain**
 
-- **Serve redirected content from a paid service as outlined below**
+* **Serve redirected content from a paid service as outlined below**
 
 ## Delivering videos with Cloudflare using paid products
 
@@ -43,14 +43,14 @@ To get started with Stream, visit **Stream** from your Dashboard or [sign up](ht
 
 [Stream Delivery](https://www.cloudflare.com/products/stream-delivery/) offers caching and delivery of video content through Cloudflare data centers around the globe. This CDN feature is only available on the Cloudflare Enterprise Plan. Please [contact sales](https://www.cloudflare.com/products/stream-delivery/#) if you'd like to explore this option.
 
----
+***
 
 ## Getting information on the content you are delivering
 
 If you need more information about the content your zone is serving (for example, content type), you can use the following tools:
 
-- Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
-- Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
+* Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
+* Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
 
 ![Cache Analytics - Identify type of traffic being transferred](~/assets/images/support/traffic-types.png)
 
@@ -58,6 +58,6 @@ If you need more information about the content your zone is serving (for example
 
 If you have additional questions about redirection (e.g. if you believe your content was redirected in error and have supporting evidence), file a [support ticket](https://dash.cloudflare.com/redirect?account=support) and include the following information:
 
-- Name of your domain
-- Description of the problem
-- Description of the content you're serving through Cloudflare's network
+* Name of your domain
+* Description of the problem
+* Description of the content you're serving through Cloudflare's network
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
index a0e6c30419d4e4c..1187f88b49dbde0 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/redirects.mdx b/src/content/docs/fundamentals/reference/redirects.mdx
index faf74ce66f949a6..cd7ef6cc592e166 100644
--- a/src/content/docs/fundamentals/reference/redirects.mdx
+++ b/src/content/docs/fundamentals/reference/redirects.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare offers a variety of ways to perform <GlossaryTooltip term="redirect">URL redirects</GlossaryTooltip>, which tell a visitor's browser that the location of a page has been changed.
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
index 3a4e6c9b913f065..c5e1d5484357c60 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
@@ -18,6 +18,6 @@ Our Trust & Safety team sends abuse reports to the domain owner or the abuse poi
 
 To assist with timely resolution and avoid potential service interruptions:
 
-- Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
-- Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
-- Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
+* Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
+* Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
+* Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
diff --git a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
index 5c3cff418dfa842..b216ceff2722d04 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
@@ -13,31 +13,31 @@ products:
 
 Use Cloudflare's [online abuse form](https://abuse.cloudflare.com/) to report different types of abuse.
 
----
+***
 
 ## DMCA complaints
 
 Valid [Digital Millennium Copyright Act (DMCA)](https://www.copyright.gov/dmca/) complaints must provide all of the following details:
 
-- A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
-- Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
-- Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
-- Your contact information, including your address, telephone number, and email address.
-- A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
-- A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
+* A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
+* Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
+* Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
+* Your contact information, including your address, telephone number, and email address.
+* A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
+* A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
 
----
+***
 
 ## Phishing
 
 Valid phishing reports must provide all of the following details:
 
-- The domain in question.
-- The specific link to the phishing page.
+* The domain in question.
+* The specific link to the phishing page.
 
 After Cloudflare confirms existence of the phishing page, Cloudflare provides a warning page to visitors accessing the phishing link. Cloudflare also notifies the site owner to clean the malicious files from their origin web server.
 
----
+***
 
 ## Trademark infringement
 
@@ -45,7 +45,7 @@ Cloudflare only acknowledges abuse reports from trademark holders or their legal
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
----
+***
 
 ## Malware sites
 
@@ -53,7 +53,7 @@ Legitimate reports of malware URLs are blocked from loading via Cloudflare.
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
----
+***
 
 ## Child exploitation material
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/index.mdx b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
index 211b1f859b80956..1607f978b92b9c9 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/index.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
@@ -19,7 +19,7 @@ When it comes to reports of abuse on websites that use our services, our ability
 
 ## Resources
 
-- [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
-- [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
-- [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
-- [Submit abuse report](https://www.cloudflare.com/abuse/form)
+* [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
+* [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
+* [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
+* [Submit abuse report](https://www.cloudflare.com/abuse/form)
diff --git a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
index 3da4ad19a0ab288..bd36756a9df63e7 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
@@ -19,10 +19,8 @@ Cloudflare offers three ways for you to submit an abuse report:
 - Public form: Refer to [Submit an Abuse Report](https://abuse.cloudflare.com/) to learn more.
 - The Cloudflare dashboard, on the **Abuse reports** page.
 
-  <DashButton url="/?to=/:account/abuse-reports" />
-  Optionally, filter the reports based on date, report status, report type, and
-  domain.
-
+    <DashButton url="/?to=/:account/abuse-reports" />
+  Optionally, filter the reports based on date, report status, report type, and domain.
 - The Cloudflare API: Use the [Abuse Reports API](/api/resources/abuse_reports/) to submit an abuse report.
 
 ## View submitted reports
@@ -31,7 +29,7 @@ Users with Admin, Super Admin, or Trust & Safety roles can view any abuse report
 
 1. In the Cloudflare dashboard, go to the **Abuse reports** page.
 
-   <DashButton url="/?to=/:account/abuse-reports" />
+    <DashButton url="/?to=/:account/abuse-reports" />
 
 2. Optionally, filter the reports based on date, report status, report type, and domain.
 
@@ -39,6 +37,6 @@ If there was a mitigation against your website due to the abuse allegation, you
 
 ## Receive notifications
 
-You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites.
+You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites. 
 
-For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
+For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
index 31a4b85d98924b4..1b46a73b2f45f59 100644
--- a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
+++ b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
@@ -21,7 +21,7 @@ These lifecycle stages may be referred to in different terms across Cloudflare p
 
 ### Early access
 
-During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
+During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will  often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
 
 ### Active support
 
@@ -41,13 +41,13 @@ While Cloudflare cannot provide support for all older versions of our libraries
 
 The SDK ecosystem follows semantic versioning, which defines versions as follows:
 
-- MAJOR version when there are backward-incompatible changes made.
-- MINOR version when functionality is added in a backward compatible-manner.
-- PATCH version for backward-compatible bug fixes (without any improvements).
+* MAJOR version when there are backward-incompatible changes made.
+* MINOR version when functionality is added in a backward compatible-manner.
+* PATCH version for backward-compatible bug fixes (without any improvements).
 
 :::caution
 
-As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases _may_ contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
+As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases *may* contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
 
 If this is not suitable for your use case, pin to a known good version or use the previous major version of the library.
 :::
@@ -62,5 +62,5 @@ Alongside the automatic migration approach, we provide documentation on the chan
 
 ## Related resources
 
-- [Semantic versioning definitions](https://semver.org/)
-- [Cloudflare's Terraform documentation](/terraform/)
+* [Semantic versioning definitions](https://semver.org/)
+* [Cloudflare's Terraform documentation](/terraform/)
diff --git a/src/content/docs/fundamentals/reference/tcp-connections.mdx b/src/content/docs/fundamentals/reference/tcp-connections.mdx
index 7662f578f5197a6..2a10e61edd13149 100644
--- a/src/content/docs/fundamentals/reference/tcp-connections.mdx
+++ b/src/content/docs/fundamentals/reference/tcp-connections.mdx
@@ -18,7 +18,7 @@ accTitle: Connections with Cloudflare
 A[Visitor] <-- Connection --> B[Cloudflare global network] <-- Connection --> C[Origin server]
 ```
 
-<br />
+<br/>
 
 User traffic is routed to the nearest Cloudflare data center based on the shortest [Border Gateway Protocol](https://www.cloudflare.com/learning/security/glossary/what-is-bgp/) (BGP) path, thanks to [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) routing. Cloudflare then processes the request. In case a request is not served from Cloudflare’s data centers, Cloudflare will open a connection to the origin server to forward the request.
 
@@ -36,8 +36,10 @@ For connections to users, Cloudflare has a default idle timeout of 400 seconds.
 
 :::note
 
+
 Be aware that even if there are keep-alives, Cloudflare cannot guarantee to keep a connection, since besides idleness, there are other reasons, like capacity balancing, data center maintenance or node restarts that can cause disconnections. Having this in mind, applications should be structured to handle disconnections gracefully.
 
+
 :::
 
 TCP connection settings between the user and Cloudflare, and between Cloudflare and Origin can be customized for Enterprise customers. Reach out to your account team for more details.
diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx
index 7f18e62f0b0f805..b9e4589f7feeebc 100644
--- a/src/content/docs/fundamentals/reference/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/reference/troubleshooting.mdx
@@ -15,42 +15,42 @@ When you [set up Cloudflare](/fundamentals/account/), you may experience the fol
 
 ## Error messages
 
-- [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
-- [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
-- [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
-- [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
-- [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
-- [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
-- [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
-- [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
+* [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
+* [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
+* [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
+* [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
+* [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
+* [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
+* [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
+* [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
 
 ## Behavior
 
-- [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
-- [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
-- [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
-- [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
-- [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
-- [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
-- [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
+* [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
+* [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
+* [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
+* [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
+* [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
+* [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
+* [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
 
 ## Cloudflare
 
-- [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
-- [Contact Cloudflare support](/support/contacting-cloudflare-support/)
-- [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
+* [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
+* [Contact Cloudflare support](/support/contacting-cloudflare-support/)
+* [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
 
 ## General resources
 
-- [DNS FAQ](/dns/faq/)
-- [SSL/TLS FAQ](/ssl/faq/)
+* [DNS FAQ](/dns/faq/)
+* [SSL/TLS FAQ](/ssl/faq/)
 
 ## Is Cloudflare attacking me
 
 Two common scenarios falsely lead to the perception that Cloudflare is attacking your site:
 
-- Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
-- The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
+* Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
+* The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
 
 Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare's network.
 
diff --git a/src/content/docs/fundamentals/security/index.mdx b/src/content/docs/fundamentals/security/index.mdx
index 6998badd02eba4c..530676a405630c9 100644
--- a/src/content/docs/fundamentals/security/index.mdx
+++ b/src/content/docs/fundamentals/security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/security/pci-scans.mdx b/src/content/docs/fundamentals/security/pci-scans.mdx
index 267a0d3f3e9bc55..6d67add60af9062 100644
--- a/src/content/docs/fundamentals/security/pci-scans.mdx
+++ b/src/content/docs/fundamentals/security/pci-scans.mdx
@@ -11,8 +11,10 @@ products:
 
 :::note
 
+
 Cloudflare is PCI certified as a Data Processor. Refer to [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities) and Cloudflare's PCI DSS Responsibility Matrix for more information.
 
+
 :::
 
 PCI scanners are tools used to identify security weaknesses. When a business undergoes a compliance audit, PCI scan results are used for compliance verification.
@@ -37,7 +39,7 @@ However, customers can easily block all unwanted traffic to these ports by using
 
 You can find all our public compliance resources in the following pages:
 
-- [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
-- [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
+* [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
+* [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
 
 You can access Compliance documents in the Cloudflare dashboard by selecting your account where you are a Super Administrator and then navigating to **Support** > **Compliance Documents**.
diff --git a/src/content/docs/fundamentals/security/under-ddos-attack.mdx b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
index 2b0568e28ce011d..fec2c129035f0eb 100644
--- a/src/content/docs/fundamentals/security/under-ddos-attack.mdx
+++ b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
@@ -7,7 +7,7 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="ddos-definition-and-diagram" product="learning-paths" />
 
@@ -15,9 +15,9 @@ import { Render } from "~/components";
 
 Common signs that you are under DDoS attack include:
 
-- Your site is offline or slow to respond to requests.
-- Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
-- Strange requests appear in your origin web server logs that do not match normal visitor behavior.
+* Your site is offline or slow to respond to requests.
+* Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
+* Strange requests appear in your origin web server logs that do not match normal visitor behavior.
 
 :::note
 
diff --git a/src/content/docs/fundamentals/user-profiles/2fa.mdx b/src/content/docs/fundamentals/user-profiles/2fa.mdx
index 62092f62c5e8c8f..57dc48b28cb5962 100644
--- a/src/content/docs/fundamentals/user-profiles/2fa.mdx
+++ b/src/content/docs/fundamentals/user-profiles/2fa.mdx
@@ -6,10 +6,12 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
+
 
 <Render file="2fa-enable" product="support" />
 
+
 ## Configure security key authentication for two-factor Cloudflare login
 
 :::caution
@@ -109,7 +111,7 @@ Regenerating your backup codes will invalidate your previous codes.
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Authentication**.
@@ -127,17 +129,17 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. Select **Profile**.
 3. Select the **Authentication**.
    - To remove your security key:
-     1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
-     2. Select **Delete**.
-     3. Enter your Cloudflare password, then select **Remove**.
+      1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
+      2. Select **Delete**.
+      3. Enter your Cloudflare password, then select **Remove**.
    - To remove your TOTP mobile application authentication:
-     1. Select **Delete method** in the **Mobile App Authentication** card.
-     2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
+      1. Select **Delete method** in the **Mobile App Authentication** card.
+      2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
 
 ![how to disable your TOTP mobile application authentication.](https://developerdocsgifs.cloudflaretraining.com/resampled_5fps_disable_mobile_auth_v2_final.gif)
 
@@ -145,18 +147,18 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 If you lose access to a mobile device, security key, or authentication code, you can solve these issues by using a backup code or retrieving a backup code from your preferred authentication app.
 
-Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid&hl=en&oco=0).
+Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid\&hl=en\&oco=0).
 
 When setting up 2FA, you should have saved your backup codes in a secure location. To restore lost access using a Cloudflare backup code:
 
 1. Retrieve the backup code from where you stored it.
 2. Go to the [Cloudflare login page](https://dash.cloudflare.com/login), enter your username and password and select **Log in**.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 3. You should see a page titled **Two-Factor Authentication**
-   - If it has a text box, enter one of your backup codes and select **Log in**.
-   - If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
+   * If it has a text box, enter one of your backup codes and select **Log in**.
+   * If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
 
 :::note
 
@@ -165,7 +167,7 @@ Once you use a backup code, it becomes invalid.
 
 ## Related resources
 
-- [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en&ref_topic=2954345&co=GENIE.Platform%3DiOS&oco=0)
-- [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
-- [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
-- [Account recovery](/fundamentals/user-profiles/account-recovery/)
+* [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en\&ref_topic=2954345\&co=GENIE.Platform%3DiOS\&oco=0)
+* [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
+* [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
+* [Account recovery](/fundamentals/user-profiles/account-recovery/)
diff --git a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
index 05298913d04f3cd..31d166bcf9914c5 100644
--- a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
+++ b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
@@ -12,7 +12,7 @@ If you do not have access to your 2FA account or backup codes and cannot current
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. On the **Two-Factor Authentication** page, select **Try recovery** on **Lost all 2FA devices and backup codes?**.
 3. Select **Begin recovery**.
@@ -24,8 +24,8 @@ If you see **Device verified**, you will receive an email within 3-5 days with i
 
 If you see **Device verification failed**, you may be able to try again considering the following:
 
-- If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
-- Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
-- You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
+   * If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
+   * Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
+   * You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
 
-If you are still unable to verify your device, follow the instructions to _Request manual verification_ on the **Device verification failed** page.
+If you are still unable to verify your device, follow the instructions to *Request manual verification* on the **Device verification failed** page.
diff --git a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
index 7e8b24b3c6504bf..f848ead54c25ce4 100644
--- a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
+++ b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
@@ -62,7 +62,7 @@ If you forget the email address associated with your application:
 
 ## Forgot your password
 
-You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option.
+You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option. 
 
 If you forget the password associated with your email address:
 
diff --git a/src/content/docs/fundamentals/user-profiles/customize-account.mdx b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
index c7b80fefce89a7c..e2069315ad718cd 100644
--- a/src/content/docs/fundamentals/user-profiles/customize-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
@@ -35,9 +35,9 @@ Adjust how the Cloudflare dashboard appears on your device.
 
 2. Go to **Profile**.
 3. From **Settings** > **Dashboard appearance**, choose a value:
-   - **Dark**: Defaults to darker colors.
-   - **Light**: Defaults to lighter colors.
-   - **Use system setting**: Defaults to the option used on your device.
+   * **Dark**: Defaults to darker colors.
+   * **Light**: Defaults to lighter colors.
+   * **Use system setting**: Defaults to the option used on your device.
 
 Your dashboard display will update to the new appearance setting automatically.
 
diff --git a/src/content/docs/fundamentals/user-profiles/delete-account.mdx b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
index 09b79d815f25fa7..94289a564a45da4 100644
--- a/src/content/docs/fundamentals/user-profiles/delete-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
@@ -28,7 +28,7 @@ Before Cloudflare can cancel your account and delete your personal information,
 - [Disable auto-renew for your Registrar domain(s)](/registrar/account-options/renew-domains#set-up-automatic-renewals)
 - If you are using a Cloudflare [CNAME setup](/dns/zone-setups/partial-setup/), [update your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) at your DNS provider to point to your website IPs or hostnames instead of Cloudflare.
 - [Delete payment information](/billing/get-started/update-billing-info/#delete-a-payment-method)
-- (_Optional_) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
+- (*Optional*) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
 
 ## Delete your Cloudflare account
 
@@ -49,7 +49,7 @@ All domains, subscriptions, and billing information on your account will be remo
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Delete this user**.
@@ -61,3 +61,4 @@ All domains, subscriptions, and billing information on your account will be remo
 Cloudflare will purge your personal information within a year of a deletion request unless required to retain it for legal obligations (such as ongoing abuse investigations or pending litigation). Refer to the [Cloudflare Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/) for further information about the deletion of personal information following the cancellation of your account.
 
 :::
+
diff --git a/src/content/docs/fundamentals/user-profiles/login.mdx b/src/content/docs/fundamentals/user-profiles/login.mdx
index 9152dcc59e82381..e81d66c7afbac91 100644
--- a/src/content/docs/fundamentals/user-profiles/login.mdx
+++ b/src/content/docs/fundamentals/user-profiles/login.mdx
@@ -27,7 +27,6 @@ Enter your email address and password.
 If your admin has enabled [enabled SSO](/fundamentals/manage-members/dashboard-sso/), enter your email address.
 
 ### Social login
-
 Social login allows you to sign in with a trusted 3rd party sign in service such as Apple, Google, or GitHub. Social login is only available for accounts with a verified email address, or accounts that signed up via social login initially. If you have additionally configured two-factor authentication on your account, that will be presented in addition to any login and two-factor authentication provided by the social login provider.
 
 :::note
@@ -44,11 +43,12 @@ To set a password, go to [Forgot Password](https://dash.cloudflare.com/forgot-pa
 You will receive an email with instructions to set your password. Once created, use your email and the new password to log in.
 :::
 
+
 #### Sign in with Apple
 
-- **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
+* **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
 
-- **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
+* **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
 
 If you chose to share your email when creating a Cloudflare account with Apple ID and want to set a password and obtain an API key, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) login page and select **Forgot your password?** to trigger a password reset email.
 
@@ -73,3 +73,4 @@ If you created your Cloudflare account using Apple Relay and decide to change yo
 - Sign in with GitHub uses the [Primary email address](https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address) which is set on your GitHub account. If you change your primary email address in GitHub, you will not be able to log into your Cloudflare account using GitHub social login.
 
 - If you select **Sign in with GitHub** with an email that does not already have a Cloudflare account associated with it, Cloudflare will create a new account and allow you to sign in using **Sign in with GitHub** option moving forward.
+
diff --git a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
index 8dfe5802aeb8a3b..ce1ca48798a83bb 100644
--- a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
+++ b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
@@ -25,14 +25,14 @@ Email MFA can only be disabled by enabling [two-factor authentication](/fundamen
 
 ## Troubleshoot MFA
 
-Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from _[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)_\_**.**\_
+Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from *[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)*\_**.**\_
 
 Other times, emails are rejected by the recipient email service. Cloudflare will try again it will flag your email address after several attempts and no further emails will be sent.
 
 If you still do not receive an email after ensuring your email service is not flagging Cloudflare, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
 
----
+***
 
 ## Related resources
 
-- [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
+* [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
index 430a7d78421a34a..b3fc9378ed0e2b3 100644
--- a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
+++ b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
@@ -34,7 +34,7 @@ If you cannot find your verification email or your email has expired, request an
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified).
@@ -47,11 +47,11 @@ To check your verification:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, your email address will have `(verified)` added after it.
 
 If your email is still not verified, try clicking the verification link in a different browser or a private window.
 
-If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
+If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
\ No newline at end of file
diff --git a/src/content/docs/google-tag-gateway/index.mdx b/src/content/docs/google-tag-gateway/index.mdx
index 313bd3117c71010..df04561d2b6e7ba 100644
--- a/src/content/docs/google-tag-gateway/index.mdx
+++ b/src/content/docs/google-tag-gateway/index.mdx
@@ -8,8 +8,8 @@ sidebar:
   order: 1
 tags:
   - Google
----
 
+---
 import { DashButton } from "~/components";
 
 Google tag gateway for advertisers allows website owners using Cloudflare as a CDN to get the most out of ad measurement tools with just a few clicks. It allows you to deploy Google scripts using your own domain, enhancing data privacy and improving signal measurement recovery. Unlike standard setups where tags are requested from a Google domain, Google tag gateway for advertisers loads the tag from your domain and sends measurement events to your domain, where they are forwarded to Google.
@@ -25,7 +25,6 @@ Google tag gateway for advertisers is free to use. Requests routed through the g
 Site owners can enable this feature in one of two ways: through the Google tag console, or through the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/tag-management/google-tag-gateway).
 
 ### Configure in Google Tag Manager
-
 The fastest way to set up Google tag gateway for advertisers is in Google Tag Manager. [Follow the steps in Google's Help Center](https://support.google.com/analytics/answer/16061641).
 
 ### Configure in the Cloudflare dashboard
@@ -44,7 +43,7 @@ Your Cloudflare dashboard user must have one of the following [Account Roles](/f
 ![Google tag gateway for advertisers configuration](~/assets/images/google-tag-gateway/google-tag-configuration.png)
 
 4. Add your Google tag ID and the path on your website reserved for the Google tag.
-   The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
+The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
 
 ![Add to ID and path](~/assets/images/google-tag-gateway/google-tag-id-path.png)
 
@@ -63,7 +62,6 @@ If you need different tag behavior for specific subdomains (for example, only fi
 This approach lets you maintain a single zone-wide Google tag gateway configuration while still customizing tag behavior per subdomain.
 
 ## Related resources
-
 - [Google Developer Docs: Set up Google tag gateway for advertisers](https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide?setup=auto)
 - [Google Help Center: Set up Google tag gateway for advertisers in the Google tag with Cloudflare](https://support.google.com/tagmanager/answer/16061406)
 - [Google Help Center: Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare](https://support.google.com/analytics/answer/16061641)
diff --git a/src/content/docs/health-checks/concepts/health-checks-regions.mdx b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
index 65a3eecbc16b25f..2cafe5f8e78ba1a 100644
--- a/src/content/docs/health-checks/concepts/health-checks-regions.mdx
+++ b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
@@ -6,6 +6,7 @@ products:
   - health-checks
 sidebar:
   order: 4
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/health-checks/concepts/index.mdx b/src/content/docs/health-checks/concepts/index.mdx
index 4bf31c3559d964a..63214119f1c7c7c 100644
--- a/src/content/docs/health-checks/concepts/index.mdx
+++ b/src/content/docs/health-checks/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts involved in Cloudflare Health Checks.
 
diff --git a/src/content/docs/health-checks/health-checks-analytics.mdx b/src/content/docs/health-checks/health-checks-analytics.mdx
index 532c92b0c481ca8..0270a58b2a3f59a 100644
--- a/src/content/docs/health-checks/health-checks-analytics.mdx
+++ b/src/content/docs/health-checks/health-checks-analytics.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
 tags:
   - Analytics
+
 ---
 
-import { AvailableNotifications, Render, DashButton } from "~/components";
+import { AvailableNotifications, Render, DashButton } from "~/components"
 
 <Render file="smart-shield-callout" product="smart-shield" />
 
diff --git a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
index 7f000b24d42b7cc..6ac6065ecb7a80e 100644
--- a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
+++ b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
@@ -6,9 +6,10 @@ products:
   - health-checks
 sidebar:
   order: 9
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 You can [configure notification emails](/health-checks/how-to/health-checks-notifications/#configure-notifications) to be alerted when the Health Check detects that there is a change in the status of your origin server. Cloudflare will send you an email within seconds so you can take the necessary action before customers are impacted.
 
@@ -30,10 +31,12 @@ The email provides information to determine what caused the health status change
 
 :::note
 
+
 A notification is only sent after a change of status in the majority of all selected region(s).
 
 For a single region, this will be 2 of 3 data centers. With 13 regions selected, this will be 7 of 13 regions.
 
+
 :::
 
 See [common error codes](/health-checks/health-checks-analytics/#common-error-codes) for more information regarding the cause of any changes to your Health Check.
diff --git a/src/content/docs/health-checks/how-to/index.mdx b/src/content/docs/health-checks/how-to/index.mdx
index db9952b5952d517..0ee79dad8ccb82c 100644
--- a/src/content/docs/health-checks/how-to/index.mdx
+++ b/src/content/docs/health-checks/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 See the following pages for more information about standalone Health Checks:
 
diff --git a/src/content/docs/health-checks/how-to/zone-lockdown.mdx b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
index a4478cdeee2a61a..591c602337a1232 100644
--- a/src/content/docs/health-checks/how-to/zone-lockdown.mdx
+++ b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Zone lockdown migration guide
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
+<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
index 2062eeebed2f06a..c65b5e2f272d5e2 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
@@ -34,7 +34,7 @@ npm i -D drizzle-kit tsx @types/node
 
 Add the required Node.js compatibility flags and Hyperdrive binding to your `wrangler.jsonc` file:
 
-<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive" />
+<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive"/>
 
 ## 2. Configure Drizzle
 
@@ -75,7 +75,7 @@ import { users } from "./db/schema";
 
 export interface Env {
 	HYPERDRIVE: Hyperdrive;
-}
+  }
 
 export default {
 	async fetch(request, env, ctx): Promise<Response> {
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
index 2d0266f83dce9cd..e193a5b10a6b006 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
@@ -25,13 +25,12 @@ You can connect Hyperdrive to any existing Prisma Postgres database by using you
 2. Select **Connect to your database** > **Any client**.
 3. Select **Generate database credentials**. Copy the connection string for your Prisma Postgres database.
 4. Edit the connection string to make it compatible with Hyperdrive.
-
-- Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
-- The final string will look like:
-
-````txt ins="database_name"
-postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
- ```
+  - Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
+  - The final string will look like:
+  
+   ```txt ins="database_name"
+   postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
+    ```   
 
 :::note
 
@@ -39,7 +38,7 @@ An alternative to the Prisma Data Platform is to use the [`create-db`](https://w
 
 ```bash
 npx create-db@latest
-````
+```
 
 :::
 
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
index 72797b0b520501a..9c1996a98116a4a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
@@ -32,7 +32,7 @@ With a database user, password, database endpoint (hostname and port) and databa
 
 :::note
 
-When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers.
+When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers. 
 
 :::
 
diff --git a/src/content/docs/hyperdrive/observability/troubleshooting.mdx b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
index 1c6ad7bce772665..4ef6f14661763a2 100644
--- a/src/content/docs/hyperdrive/observability/troubleshooting.mdx
+++ b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
@@ -32,10 +32,10 @@ Hyperdrive will also issue an empty test query, a `;` in PostgreSQL, to validate
 
 Hyperdrive may also emit `Failed to connect to the provided database` when it fails to connect to the database when attempting to create a Hyperdrive configuration. This is possible when the TLS (SSL) certificates are misconfigured. Here is a non-exhaustive table of potential failure to connect errors:
 
-| Error message                                 | Details                                                                                                                                                                                               | Recommended fixes                                                                                                                                                     |
-| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Server return error and closed connection.    | This message occurs when you attempt to connect to a database that has client certificate verification enabled.                                                                                       | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
-| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database.                                      |
+| Error message | Details               | Recommended fixes |
+| ---------- | -------------------- | --------------------- |
+| Server return error and closed connection. | This message occurs when you attempt to connect to a database that has client certificate verification enabled. | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
+| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database. |
 
 ## Connection errors
 
@@ -46,14 +46,16 @@ Hyperdrive errors that do not map 1:1 with an error message code [documented by
 
 Hyperdrive may also encounter `ErrorResponse` wire protocol messages sent by your database. Hyperdrive will pass these errors through unchanged when possible.
 
+
+
 ### Hyperdrive specific errors
 
-| Error Message                                                           | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
-| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Internal error.`                                                       | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                    |
-| `Failed to acquire a connection from the pool.`                         | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
-| `Server connection attempt failed: connection_refused`                  | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
-| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases.                            | Remove prepared statements from your MySQL queries.                                                                                                                                                                                                                                            |
+| Error Message                                          | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Internal error.`                                      | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                                                               |
+| `Failed to acquire a connection from the pool.`        | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
+| `Server connection attempt failed: connection_refused` | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
+| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases. | Remove prepared statements from your MySQL queries. |
 
 ### Node errors
 
@@ -73,8 +75,8 @@ If your queries are not being cached despite Hyperdrive having caching enabled,
 
 ### Driver errors
 
-| Error Message                                              | Details                                                                                                                                              | Recommended fixes                                                                                                                                                                               |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | `Code generation from strings disallowed for this context` | The database driver you are using is attempting to use the `eval()` command, which is unsupported on Cloudflare Workers (common in `mysql2` driver). | Configure the database driver to not use `eval()`. See how to [configure `mysql2` to disable the usage of `eval()`](/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/mysql2/). |
 
 ### Stale connection and I/O context errors
@@ -83,46 +85,46 @@ These errors occur when a database client or connection is created in the global
 
 #### Workers runtime errors
 
-| Error Message                                                                                                                                                                                                                  | Details                                                                                                                     | Recommended fixes                                                                                                                                                             |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.`                                           | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function.                                                                                      |
-| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request.                         | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.` | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function. |
+| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request. | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
 
 #### node-postgres (`pg`) errors
 
-| Error Message                                                    | Details                                                                                                                                         | Recommended fixes                                                                                                                         |
-| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| `Connection terminated`                                          | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request.                                     | Create a new `Client` inside your handler instead of reusing one from a prior request.                                                    |
-| `Connection terminated unexpectedly`                             | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request.                                                                              |
-| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests).                                                 | Create a new `Client` inside your handler. Do not store clients in global variables.                                                      |
-| `Client was closed and is not queryable`                         | A query was attempted on a client whose `.end()` method was already called.                                                                     | Create a new `Client` inside your handler instead of reusing one.                                                                         |
-| `Cannot use a pool after calling end on the pool`                | `pool.connect()` was called on a `Pool` instance that has already been ended.                                                                   | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
-| `Client has already been connected. You cannot reuse a client.`  | `client.connect()` was called on a client that was already connected in a previous invocation.                                                  | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected.                                            |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Connection terminated` | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request. | Create a new `Client` inside your handler instead of reusing one from a prior request. |
+| `Connection terminated unexpectedly` | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request. |
+| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests). | Create a new `Client` inside your handler. Do not store clients in global variables. |
+| `Client was closed and is not queryable` | A query was attempted on a client whose `.end()` method was already called. | Create a new `Client` inside your handler instead of reusing one. |
+| `Cannot use a pool after calling end on the pool` | `pool.connect()` was called on a `Pool` instance that has already been ended. | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
+| `Client has already been connected. You cannot reuse a client.` | `client.connect()` was called on a client that was already connected in a previous invocation. | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected. |
 
 #### Postgres.js (`postgres`) errors
 
 Postgres.js error messages include the error code and the target host. The `code` property on the error object contains the error code.
 
-| Error Message                              | Details                                                                                                                                                                                 | Recommended fixes                                                                                                                           |
-| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `write CONNECTION_ENDED <host>:<port>`     | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`.                                              | Create a new `postgres()` instance inside your handler.                                                                                     |
-| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request.                                                                   |
-| `write CONNECTION_CLOSED <host>:<port>`    | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`.                                                                        | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `write CONNECTION_ENDED <host>:<port>` | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`. | Create a new `postgres()` instance inside your handler. |
+| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request. |
+| `write CONNECTION_CLOSED <host>:<port>` | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`. | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
 
 #### mysql2 errors
 
-| Error Message                                              | Details                                                                                                                           | Recommended fixes                                                                                                                          |
-| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error.                                  | Create a new connection inside your handler instead of reusing one from global scope.                                                      |
-| `Connection lost: The server closed the connection.`       | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request.                                                                             |
-| `Pool is closed.`                                          | `pool.getConnection()` was called on a pool that has already been closed.                                                         | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error. | Create a new connection inside your handler instead of reusing one from global scope. |
+| `Connection lost: The server closed the connection.` | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request. |
+| `Pool is closed.` | `pool.getConnection()` was called on a pool that has already been closed. | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
 
 #### mysql errors
 
-| Error Message                                                   | Details                                                                                                                                   | Recommended fixes                                                                            |
-| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| `Cannot enqueue Query after fatal error.`                       | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`.        | Create a new connection inside your handler instead of reusing one from global scope.        |
-| `Cannot enqueue Query after invoking quit.`                     | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`.                               | Create a new connection inside your handler for every request.                               |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Cannot enqueue Query after fatal error.` | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`. | Create a new connection inside your handler instead of reusing one from global scope. |
+| `Cannot enqueue Query after invoking quit.` | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`. | Create a new connection inside your handler for every request. |
 | `Cannot enqueue Handshake after already enqueuing a Handshake.` | `.connect()` was called on a connection that was already connected in a previous request. Error code: `PROTOCOL_ENQUEUE_HANDSHAKE_TWICE`. | Create a new connection per request. mysql connections cannot be reconnected once connected. |
 
 ### Improve performance
diff --git a/src/content/docs/hyperdrive/platform/limits.mdx b/src/content/docs/hyperdrive/platform/limits.mdx
index 312468a7fe964d7..76f3f59ff4ae007 100644
--- a/src/content/docs/hyperdrive/platform/limits.mdx
+++ b/src/content/docs/hyperdrive/platform/limits.mdx
@@ -14,10 +14,10 @@ The following limits apply to Hyperdrive configurations, connections, and querie
 
 These limits apply when creating or updating Hyperdrive configurations.
 
-| Limit                             | Free                  | Paid                  |
-| --------------------------------- | --------------------- | --------------------- |
-| Maximum configured databases      | 10 per account        | 25 per account        |
-| Maximum username length [^1]      | 63 characters (bytes) | 63 characters (bytes) |
+| Limit                          | Free                  | Paid                  |
+| ------------------------------ | --------------------- | --------------------- |
+| Maximum configured databases   | 10 per account        | 25 per account        |
+| Maximum username length [^1]   | 63 characters (bytes) | 63 characters (bytes) |
 | Maximum database name length [^1] | 63 characters (bytes) | 63 characters (bytes) |
 
 [^1]: This is a limit enforced by PostgreSQL. Some database providers may enforce smaller limits.
@@ -26,10 +26,10 @@ These limits apply when creating or updating Hyperdrive configurations.
 
 These limits apply to connections between Hyperdrive and your origin database.
 
-| Limit                                                        | Free            | Paid             |
-| ------------------------------------------------------------ | --------------- | ---------------- |
-| Initial connection timeout                                   | 15 seconds      | 15 seconds       |
-| Idle connection timeout                                      | 10 minutes      | 10 minutes       |
+| Limit                              | Free                     | Paid                      |
+| ---------------------------------- | ------------------------ | ------------------------- |
+| Initial connection timeout         | 15 seconds               | 15 seconds                |
+| Idle connection timeout            | 10 minutes               | 10 minutes                |
 | Maximum origin database connections (per configuration) [^2] | ~20 connections | ~100 connections |
 
 Hyperdrive does not limit the number of concurrent client connections from your Workers. However, Hyperdrive limits connections to your origin database because most hosted databases have connection limits.
@@ -40,9 +40,9 @@ Hyperdrive does not limit the number of concurrent client connections from your
 
 When Hyperdrive cannot acquire a connection to your origin database, you may see one of the following errors:
 
-| Error message                                          | Cause                                                                                                                                                           |
-| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Failed to acquire a connection from the pool.`        | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause.                           |
+| Error message | Cause |
+| ------------- | ----- |
+| `Failed to acquire a connection from the pool.` | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause. |
 | `Server connection attempt failed: connection_refused` | Your origin database is rejecting connections. This can occur when a firewall blocks Hyperdrive, or when your database provider's connection limit is exceeded. |
 
 For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdrive/observability/troubleshooting/).
@@ -51,10 +51,10 @@ For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdriv
 
 These limits apply to queries sent through Hyperdrive.
 
-| Limit                              | Free       | Paid       |
-| ---------------------------------- | ---------- | ---------- |
+| Limit                              | Free      | Paid      |
+| ---------------------------------- | --------- | --------- |
 | Maximum query (statement) duration | 60 seconds | 60 seconds |
-| Maximum cached query response size | 50 MB      | 50 MB      |
+| Maximum cached query response size | 50 MB     | 50 MB     |
 
 Queries exceeding the maximum duration are terminated. Query responses larger than 50 MB are not cached but are still returned to your Worker.
 
diff --git a/src/content/docs/hyperdrive/platform/storage-options.mdx b/src/content/docs/hyperdrive/platform/storage-options.mdx
index e47f0bee278b20d..15e4357c49ab353 100644
--- a/src/content/docs/hyperdrive/platform/storage-options.mdx
+++ b/src/content/docs/hyperdrive/platform/storage-options.mdx
@@ -9,5 +9,5 @@ products:
   - hyperdrive
   - kv
   - r2
-  - d1
+  - d1 
 ---
diff --git a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
index 634a4a834452673..79d2a4c9a8334f6 100644
--- a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
+++ b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
@@ -12,4 +12,4 @@ import { WranglerNamespace } from "~/components";
 
 The following [Wrangler commands](/workers/wrangler/) apply to Hyperdrive.
 
-<WranglerNamespace namespace="hyperdrive" />
+<WranglerNamespace namespace="hyperdrive" />
\ No newline at end of file
diff --git a/src/content/docs/hyperdrive/tutorials/index.mdx b/src/content/docs/hyperdrive/tutorials/index.mdx
index 20365d245d2b967..303882afc56a048 100644
--- a/src/content/docs/hyperdrive/tutorials/index.mdx
+++ b/src/content/docs/hyperdrive/tutorials/index.mdx
@@ -10,7 +10,7 @@ products:
   - workers
 ---
 
-import { GlossaryTooltip, ListTutorials } from "~/components";
+import { GlossaryTooltip, ListTutorials } from "~/components"
 
 View <GlossaryTooltip term="tutorial">tutorials</GlossaryTooltip> to help you get started with Hyperdrive.
 
diff --git a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
index 83a5d692b9d5e21..b9f564b90204b67 100644
--- a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
+++ b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
@@ -3,7 +3,7 @@ reviewed: 2023-10-30
 difficulty: Beginner
 pcx_content_type: tutorial
 title: Create a serverless, globally distributed time-series API with Timescale
-products: [workers]
+products:	[workers]
 tags:
   - PostgreSQL
   - TypeScript
diff --git a/src/content/docs/images/optimization/make-responsive-images.mdx b/src/content/docs/images/optimization/make-responsive-images.mdx
index 951c3590cc0ae6e..a0dcd9f7f0c9726 100644
--- a/src/content/docs/images/optimization/make-responsive-images.mdx
+++ b/src/content/docs/images/optimization/make-responsive-images.mdx
@@ -68,7 +68,12 @@ The browser evaluates screen size, pixel density, and network conditions, then s
 The snippet below shows how `srcset` can be used within an `<img>` tag to serve one of two possible sizes, depending on the user's device pixel ratio:
 
 ```html
-<img src="portrait-800w.jpg" srcset="portrait-1600.jpg 2x" />
+<img
+	src="portrait-800w.jpg"
+	srcset="
+		portrait-1600.jpg 2x,
+	"
+/>
 ```
 
 Instead of pre-generating each size, use Images to point every `srcset` entry at the same source image with a different `width` parameter and pixel density descriptor (for example, `2x`). Once the browser selects the right width for the user's device pixel ratio, Cloudflare dynamically generates the resized version on request:
@@ -159,11 +164,11 @@ The default breakpoints for client hints are: `320`, `768`, `960`, and `1200` pi
 The following table shows the widths that Cloudflare will pick based on the default breakpoints. If the detected viewport width exceeds the largest breakpoint, the image is served at that largest breakpoint.
 
 | Detected viewport width | Served image width |
-| ----------------------- | ------------------ |
-| 280px                   | 320px              |
-| 500px                   | 768px              |
-| 960px                   | 960px              |
-| 1500px                  | 1200px             |
+| ---------- | ------------- |
+| 280px          | 320px         |
+| 500px          | 768px         |
+| 960px          | 960px         |
+| 1500px          | 1200px        |
 
 You can override the default breakpoints using the [`wbreakpoints`](/images/optimization/features/#width) sub-parameter, which accepts positive integers separated by semicolons.
 
diff --git a/src/content/docs/images/optimization/transformations/flows.mdx b/src/content/docs/images/optimization/transformations/flows.mdx
index c9d36c389aba1ca..90b4c423f905e10 100644
--- a/src/content/docs/images/optimization/transformations/flows.mdx
+++ b/src/content/docs/images/optimization/transformations/flows.mdx
@@ -6,12 +6,10 @@ sidebar:
   products:
     - images
 ---
-
 import { Description, Render } from "~/components";
 
 <Description>
-	Define automated rules to optimize remote images without writing any code or
-	changing your existing URLs.
+	Define automated rules to optimize remote images without writing any code or changing your existing URLs.
 </Description>
 
 Flows let you automatically apply image optimization to requests on your zone.
@@ -34,7 +32,6 @@ Currently, Cloudflare supports flows for Fastly Image Optimizer. When enabled, C
 A **custom flow** lets you define your own conditions and actions for image optimization.
 
 This is well-suited for situations where you want to optimize your images broadly and consistently, such as:
-
 - **Automatic format conversion** — Transcode all images to modern formats like AVIF or WebP across your entire site.
 - **Responsive sizing** — Automatically resize images based on each user's device.
 - **Directory-based optimization** — Enforce a consistent size for all images in a particular path, such as 100x100 for images where the path contains `/thumbnail`.
@@ -44,19 +41,16 @@ This is well-suited for situations where you want to optimize your images broadl
 Before setting up a flow, make sure that transformations are turned on for your zone under **Images** > **Transformations** in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/images/transformations).
 
 When an image is requested on your zone, Cloudflare checks to see whether the request matches the conditions for any of your configured flows:
-
 - Flows are evaluated from top to bottom in the order that they appear in the dashboard.
 - If a request matches more than one flow, only the first matching flow will run.
 - If no flow matches, then the request passes through to your origin unmodified.
 - To control priority, you can reorder flows in the dashboard.
 
 If the request matches a flow's conditions, then Cloudflare rewrites the URL to pass through the Images service with the specified parameters:
-
 - A custom flow triggers only on requests for [supported image extensions](/images/get-started/limits/). HTML pages, CSS files, and other non-images are never affected.
 - A provider flow evaluates requests based on provider-specific optimization parameters. For example, a Fastly provider flow triggers only when the request contains parameters like `?width`, `?height`, or `?fit`. Cloudflare will ignore any unrecognized parameters.
 
 In your request lifecycle, flows are evaluated after standard HTTP [redirect rules](/rules/url-forwarding/):
-
 - Any existing URL rewrites or redirect rules will be applied before Images evaluates the request, which may affect matching behavior.
 - Flows include built-in loop prevention. If the request is already coming from the Images service, then the flow will not re-trigger on that subrequest.
 
@@ -65,7 +59,6 @@ In your request lifecycle, flows are evaluated after standard HTTP [redirect rul
 Currently, Cloudflare supports flows to handle migrations from Fastly Image Optimizer.
 
 To add a provider flow:
-
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Images** > **Transformations** and select your zone.
 3. Select the **Automation** tab, then select **Add provider flow**.
@@ -129,11 +122,11 @@ Cloudflare determines the optimal width using either [client hints](/images/opti
 
 You can fine-tune the `width=auto` behavior with the following sub-parameters:
 
-| Sub-parameter  | Description                                                                   | Default            |
-| -------------- | ----------------------------------------------------------------------------- | ------------------ |
-| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints)                  | `320;768;960;1200` |
-| `wmobile`      | Override default width, in pixels, for mobile devices (user-agent detection)  | `768`              |
-| `wdesktop`     | Override default width, in pixels, for desktop devices (user-agent detection) | `1200`             |
+| Sub-parameter | Description | Default |
+| --- | --- | --- |
+| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints) | `320;768;960;1200` |
+| `wmobile` | Override default width, in pixels, for mobile devices (user-agent detection) | `768` |
+| `wdesktop` | Override default width, in pixels, for desktop devices (user-agent detection) | `1200` |
 
 To learn how `width=auto` works, refer to our guide on [serving responsive images](/images/optimization/make-responsive-images/).
 
diff --git a/src/content/docs/images/optimization/transformations/overview.mdx b/src/content/docs/images/optimization/transformations/overview.mdx
index 7de24256a768de1..d623c6694db1f47 100644
--- a/src/content/docs/images/optimization/transformations/overview.mdx
+++ b/src/content/docs/images/optimization/transformations/overview.mdx
@@ -11,8 +11,7 @@ products:
 import { Description, Render } from "~/components";
 
 <Description>
-	Transformations are requests to optimize and manipulate remote images that are
-	stored outside of Images.
+	Transformations are requests to optimize and manipulate remote images that are stored outside of Images.
 </Description>
 
 When you ship applications on Cloudflare, you can use Images to automatically optimize and cache your images from any origin.
diff --git a/src/content/docs/key-transparency/api/epochs.mdx b/src/content/docs/key-transparency/api/epochs.mdx
index 6aa0c01a45d12dd..d9a24544386e49e 100644
--- a/src/content/docs/key-transparency/api/epochs.mdx
+++ b/src/content/docs/key-transparency/api/epochs.mdx
@@ -49,7 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}/audit
 - If `root` is defined for the namespace, the first epoch must match it (number and digest).
 - Epochs must be increasing. Second epoch is 2, third is 3, etc.
 - Epochs must have a unique digest or it will be rejected.
-- Epochs cannot be republished.
+- Epochs cannot be republished. 
 - Digest must be a 32 byte string hex encoded (length 64).
 
 If a namespace is disabled, you receive the following error:
diff --git a/src/content/docs/key-transparency/api/index.mdx b/src/content/docs/key-transparency/api/index.mdx
index 64b24fdf3146f9d..c390a1774ee252d 100644
--- a/src/content/docs/key-transparency/api/index.mdx
+++ b/src/content/docs/key-transparency/api/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/key-transparency/api/namespaces.mdx b/src/content/docs/key-transparency/api/namespaces.mdx
index 055e97b897823f2..3e42e5b0a09d29b 100644
--- a/src/content/docs/key-transparency/api/namespaces.mdx
+++ b/src/content/docs/key-transparency/api/namespaces.mdx
@@ -20,8 +20,8 @@ The following fields are required when making a `POST` request:
 - `name`
 - `public`
 - `root`
-- `signature_version`:
-  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor
+- `signature_version`: 
+  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor 
   - 0x0002 for [bincode serialisation](https://github.com/bincode-org/bincode/blob/trunk/docs/spec.md) E25519 serialisation by the Auditor
 
 The `log_directory` field is optional. If set, Cloudflare will use it to fetch audit proofs and validate them.
@@ -49,7 +49,6 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces' \
 ```
 
 After publishing the first epoch, `status` will show `Online`. Possible statuses include:
-
 - `Online`
 - `Initialization`
 - `Disabled`
@@ -74,6 +73,7 @@ If a log state has been corrupted, lost, or needs to be sharded to be maintainab
 
 This API is authenticated via [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).
 
+
 ```sh
 curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}' \
         	-H 'Content-Type: application/json' \
@@ -89,4 +89,4 @@ curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespa
   "audits_uri": "/namespaces/your.new.log.com/audits",
   "signature_version": 1
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/kv/api/delete-key-value-pairs.mdx b/src/content/docs/kv/api/delete-key-value-pairs.mdx
index e8173282815e34f..f4275b10c635eef 100644
--- a/src/content/docs/kv/api/delete-key-value-pairs.mdx
+++ b/src/content/docs/kv/api/delete-key-value-pairs.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
@@ -22,24 +22,25 @@ An example of deleting a key-value pair from within a Worker:
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		try {
-			await env.NAMESPACE.delete("first-key");
-
-			return new Response("Successful delete", {
-				status: 200,
-			});
-		} catch (e) {
-			return new Response(e.message, { status: 500 });
-		}
-	},
+  async fetch(request, env, ctx) {
+    try {
+      await env.NAMESPACE.delete("first-key");
+
+      return new Response("Successful delete", {
+        status: 200
+      });
+    }
+    catch (e)
+    {
+      return new Response(e.message, {status: 500});
+    }
+  },
 };
 ```
 
 ## Reference
 
 The following method is provided to delete from KV:
-
 - [delete()](#delete-method)
 
 ### `delete()` method
@@ -52,13 +53,14 @@ env.NAMESPACE.delete(key);
 
 #### Parameters
 
-- `key`: `string`
-  - The key to associate with the value.
+* `key`: `string`
+  * The key to associate with the value.
 
 #### Response
 
-- `response`: `Promise<void>`
-  - A `Promise` that resolves if the delete is successful.
+* `response`: `Promise<void>`
+  * A `Promise` that resolves if the delete is successful.
+
 
 This method returns a promise that you should `await` on to verify successful deletion. Calling `delete()` on a non-existing key is returned as a successful delete.
 
@@ -73,5 +75,4 @@ Delete more than one key-value pair at a time with Wrangler or [via the REST API
 The bulk REST API can accept up to 10,000 KV pairs at once. Bulk writes are not supported using the [KV binding](/kv/concepts/kv-bindings/).
 
 ## Other methods to access KV
-
 You can also [delete key-value pairs from the command line with Wrangler](/kv/reference/kv-commands/#kv-namespace-delete) or [with the REST API](/api/resources/kv/subresources/namespaces/subresources/values/methods/delete/).
diff --git a/src/content/docs/kv/concepts/kv-bindings.mdx b/src/content/docs/kv/concepts/kv-bindings.mdx
index 1710c1db27c0aad..025824dc80e64ab 100644
--- a/src/content/docs/kv/concepts/kv-bindings.mdx
+++ b/src/content/docs/kv/concepts/kv-bindings.mdx
@@ -52,14 +52,14 @@ With this, the deployed Worker will have a `TODO` field in their environment obj
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		// Get the value for the "to-do:123" key
-		// NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
-		let value = await env.TODO.get("to-do:123");
-
-		// Return the value, as is, for the Response
-		return new Response(value);
-	},
+  async fetch(request, env, ctx) {
+    // Get the value for the "to-do:123" key
+    // NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
+    let value = await env.TODO.get("to-do:123");
+
+    // Return the value, as is, for the Response
+    return new Response(value);
+  },
 };
 ```
 
@@ -97,13 +97,13 @@ An example might look like:
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-	constructor(ctx, env) {
-		super(ctx, env);
-	}
-
-	async fetch(request) {
-		const valueFromKV = await this.env.NAMESPACE.get("someKey");
-		return new Response(valueFromKV);
-	}
+  constructor(ctx, env) {
+    super(ctx, env);
+  }
+
+  async fetch(request) {
+    const valueFromKV = await this.env.NAMESPACE.get("someKey");
+    return new Response(valueFromKV);
+  }
 }
 ```
diff --git a/src/content/docs/kv/concepts/kv-namespaces.mdx b/src/content/docs/kv/concepts/kv-namespaces.mdx
index 0919c833f8ab666..7867efd8d6aaab6 100644
--- a/src/content/docs/kv/concepts/kv-namespaces.mdx
+++ b/src/content/docs/kv/concepts/kv-namespaces.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - kv
 ---
-
 import { Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 A KV namespace is a key-value database replicated to Cloudflare’s global network.
@@ -24,14 +23,17 @@ KV namespace IDs are public and bound to your account.
 
 To bind KV namespaces to your Worker, assign an array of the below object to the `kv_namespaces` key.
 
-- `binding` <Type text="string" /> <MetaInfo text="required" />
-  - The binding name used to refer to the KV namespace.
+* `binding` <Type text="string" /> <MetaInfo text="required" />
+
+  * The binding name used to refer to the KV namespace.
+
+* `id` <Type text="string" /> <MetaInfo text="required" />
 
-- `id` <Type text="string" /> <MetaInfo text="required" />
-  - The ID of the KV namespace.
+  * The ID of the KV namespace.
 
-- `preview_id` <Type text="string" /> <MetaInfo text="optional" />
-  - The ID of the KV namespace used during `wrangler dev`.
+* `preview_id` <Type text="string" /> <MetaInfo text="optional" />
+
+  * The ID of the KV namespace used during `wrangler dev`.
 
 Example:
 
@@ -57,7 +59,6 @@ To bind the namespace to your Worker in the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your **Worker**.
 3. Select **Settings** > **Bindings**.
 4. Select **Add**.
diff --git a/src/content/docs/kv/get-started.mdx b/src/content/docs/kv/get-started.mdx
index 2940849e4bb17a3..1087ab11b86e2ce 100644
--- a/src/content/docs/kv/get-started.mdx
+++ b/src/content/docs/kv/get-started.mdx
@@ -3,7 +3,7 @@ title: Getting started
 description: Create a KV namespace, write key-value pairs, and read data from Workers KV using Wrangler or the dashboard.
 pcx_content_type: get-started
 summary: |
-  Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
+    Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
 reviewed: 2025-05-19
 sidebar:
   order: 2
@@ -11,18 +11,7 @@ products:
   - kv
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	FileTree,
-	Details,
-	Tabs,
-	TabItem,
-	WranglerConfig,
-	GitHubCode,
-	DashButton,
-} from "~/components";
+import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem, WranglerConfig, GitHubCode, DashButton } from "~/components";
 
 Workers KV provides low-latency, high-throughput global storage to your [Cloudflare Workers](/workers/) applications. Workers KV is ideal for storing user configuration data, routing data, A/B testing configurations and authentication tokens, and is well suited for read-heavy workloads.
 
diff --git a/src/content/docs/kv/glossary.mdx b/src/content/docs/kv/glossary.mdx
index fca60dffa616ae9..6b9c8f69e63c1a2 100644
--- a/src/content/docs/kv/glossary.mdx
+++ b/src/content/docs/kv/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's KV documentation.
 
diff --git a/src/content/docs/kv/observability/index.mdx b/src/content/docs/kv/observability/index.mdx
index 8f1670df25b7b57..9f1c8fd90be7853 100644
--- a/src/content/docs/kv/observability/index.mdx
+++ b/src/content/docs/kv/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - kv
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/kv/observability/metrics-analytics.mdx b/src/content/docs/kv/observability/metrics-analytics.mdx
index 01ac3d93bddf26b..c341d12aa8f4c3c 100644
--- a/src/content/docs/kv/observability/metrics-analytics.mdx
+++ b/src/content/docs/kv/observability/metrics-analytics.mdx
@@ -32,7 +32,6 @@ Per-namespace analytics for KV are available in the Cloudflare dashboard. To vie
 1. In the Cloudflare dashboard, go to the **Workers KV** page.
 
    <DashButton url="/?to=/:account/workers/kv/namespaces" />
-
 2. Select an existing namespace.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/kv/platform/pricing.mdx b/src/content/docs/kv/platform/pricing.mdx
index e52462c5d821622..2fbcd27b1c0dc52 100644
--- a/src/content/docs/kv/platform/pricing.mdx
+++ b/src/content/docs/kv/platform/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="kv_pricing" product="workers" />
 
diff --git a/src/content/docs/kv/reference/data-security.mdx b/src/content/docs/kv/reference/data-security.mdx
index 5c00ce589165eee..56ffef1944f609a 100644
--- a/src/content/docs/kv/reference/data-security.mdx
+++ b/src/content/docs/kv/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of KV, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/kv/reference/environments.mdx b/src/content/docs/kv/reference/environments.mdx
index dc41508ef498dcf..ef1e9305aea8aa3 100644
--- a/src/content/docs/kv/reference/environments.mdx
+++ b/src/content/docs/kv/reference/environments.mdx
@@ -68,6 +68,8 @@ Specifying an environment with the optional `--env` flag allows you to publish W
 
 For example, you could use separate staging and production KV namespaces for KV data in your Wrangler file:
 
+
+
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/kv/reference/kv-commands.mdx b/src/content/docs/kv/reference/kv-commands.mdx
index fe72655a36d9f3d..431cd3c20f17a6f 100644
--- a/src/content/docs/kv/reference/kv-commands.mdx
+++ b/src/content/docs/kv/reference/kv-commands.mdx
@@ -8,9 +8,9 @@ products:
   - kv
 ---
 
-import { Render } from "~/components";
+import {Render} from "~/components"
 
-<Render file="wrangler-commands/kv" product="workers" />
+<Render file="wrangler-commands/kv" product="workers"/>
 
 ## Deprecations
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
index 390d7d7727dc08f..e12e1fb27bbc69d 100644
--- a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
@@ -5,7 +5,7 @@ pcx_content_type: overview
 sidebar:
   order: 5
   label: Audit Logs - v2
-  badge:
+  badge: 
     text: Beta
 description: Use the updated Audit Logs v2 interface.
 products:
diff --git a/src/content/docs/learning-paths/application-security/account-security/index.mdx b/src/content/docs/learning-paths/application-security/account-security/index.mdx
index 8bd856a5fcab2d3..cb51b549f91cf51 100644
--- a/src/content/docs/learning-paths/application-security/account-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/index.mdx
@@ -18,6 +18,6 @@ Make sure your account's security basics are configured properly.
 
 By the end of this module, you will be able to:
 
-- Secure your account
-- Understand and configure the most common settings for Cloudflare's Application Security Products
-- Explore advanced security products such as Bot Management and API Protection
+* Secure your account
+* Understand and configure the most common settings for Cloudflare's Application Security Products
+* Explore advanced security products such as Bot Management and API Protection
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
index 040aa06f0220922..7b0bddc7ba7917f 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="account-manage-active-sessions" product="fundamentals" />
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
index f58aa925b394692..808ba2c05ca7dad 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 :::note
 Audit Logs version 2 is available in beta. Refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/) for more details.
diff --git a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
index f7846d7a368fa45..29a6b9e44022824 100644
--- a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
@@ -12,11 +12,11 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="2fa-overview" product="support" />
 
----
+***
 
 ## Enable 2FA
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
index d9d1cae9beaab73..2f7bec4ece18e95 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="bic-description" product="waf" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
index 33a0732d1aa3a3e..6358ef403930629 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
@@ -12,10 +12,10 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare automatically detects and mitigates DDoS attacks using its [Autonomous Edge](/ddos-protection/about/components/#autonomous-edge), which is always-on. `Advanced` protections are reserved for Magic Transit customers.
 
 <Render file="ddos-attack-coverage" product="ddos-protection" />
 
-Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/) to dive deeper into this subject.
+Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/)  to dive deeper into this subject.
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
index 636464957d64e91..d3c76bce71f7ce2 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="dnssec-definition" product="dns" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
index 5432c5e8c039ee4..f9c577f4d3368d9 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
@@ -18,4 +18,4 @@ As soon as you onboard your domain to Cloudflare, you are automatically protecte
 
 By the end of this module, you will be able to:
 
-- Understand the most common security controls your applications will have access to
+* Understand the most common security controls your applications will have access to
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
index 3d460f58056b631..a68ec976eb10fae 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Mutual TLS (mTLS) authentication uses client certificates to ensure traffic between client and server is bidirectionally secure and trusted. mTLS also allows requests that do not authenticate via an identity provider — such as Internet-of-things (IoT) devices — to demonstrate they can reach a given resource.
 
diff --git a/src/content/docs/learning-paths/application-security/firewall/index.mdx b/src/content/docs/learning-paths/application-security/firewall/index.mdx
index 78fffa803dc49c0..6ee96f14dba91e6 100644
--- a/src/content/docs/learning-paths/application-security/firewall/index.mdx
+++ b/src/content/docs/learning-paths/application-security/firewall/index.mdx
@@ -18,5 +18,5 @@ Cloudflare's Web Application Firewall (WAF) is used to protect websites from a w
 
 By the end of this module, you will be able to:
 
-- Understand the different WAF components that Cloudflare offers
-- Understand the main features within each WAF offering
+* Understand the different WAF components that Cloudflare offers
+* Understand the main features within each WAF offering
diff --git a/src/content/docs/learning-paths/application-security/lists/configuration.mdx b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
index de13360e165d887..0a7cc2639adf13f 100644
--- a/src/content/docs/learning-paths/application-security/lists/configuration.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Both Custom and Managed Lists are located in the account settings. Refer to [Features by plan type](/learning-paths/application-security/lists/features/) for more information on plan eligibility.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/features.mdx b/src/content/docs/learning-paths/application-security/lists/features.mdx
index 4ea1c31ecbdd63e..96704045ef785d4 100644
--- a/src/content/docs/learning-paths/application-security/lists/features.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { FeatureTable, Render } from "~/components";
+import { FeatureTable, Render } from "~/components"
 
 List availability varies according to the list type and your Cloudflare plan and subscriptions.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/index.mdx b/src/content/docs/learning-paths/application-security/lists/index.mdx
index 852a5c8744856ab..5278a33aaa568ba 100644
--- a/src/content/docs/learning-paths/application-security/lists/index.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/index.mdx
@@ -14,12 +14,12 @@ products:
 
 Cloudflare Lists is a WAF feature that enables administrators to groups identifiers together, such as IPs, hostnames or ASNs, and reference the list by other Cloudflare products such as [Custom rules](/waf/custom-rules/). Cloudflare currently supports the following types of lists:
 
-- [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
-- [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
+* [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
+* [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Understand all the options Cloudflare's Lists products offer
-- Understand the advanced configurations provided to you with a paid offering
+* Understand all the options Cloudflare's Lists products offer
+* Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
index 9823a3c2fca778d..b14eddd109c6d34 100644
--- a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
index 21914e63f80aefc..ceee8008c0ec64e 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
@@ -14,14 +14,14 @@ products:
 
 Let's step through an example. If your `/create-account` page is being attacked, you will create a rule to limit the amount of requests, per `counting characteristic`, that you feel comfortable permitting through to your origin.
 
-The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, _after_ 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
+The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, *after* 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
 
----
+***
 
 ![rate-limiting-create-account-endpoint](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint.png)
 ![rate-limiting-create-account-endpoint-block](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint-block.png)
 
----
+***
 
 ## Advanced configuration
 
@@ -29,14 +29,14 @@ In the previous module, we reviewed the various configurations available per pla
 
 The rule below is being created on the `enterprise` plan, so we are no longer limited to default configurations.
 
-- The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
-- Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
-- Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
-- Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
+* The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
+* Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
+* Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
+* Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
 
 ![rate-limiting-advanced-config-1](~/assets/images/waf/rate-limiting-rules/rl-advanced-config.png)
 
----
+***
 
 ## Best practices
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
index 606b48b86302118..21aa7c300cdb961 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Rate limiting is composed of the following parameters:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
index 45270f5ec40f21e..75a9a0e25347d72 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
@@ -18,5 +18,5 @@ Rate Limiting mitigates excessive request rates for specific URLs or for an enti
 
 By the end of this module, you will be able to:
 
-- Understand all the options Cloudflare's Rate Limiting product offers
-- Understand the advanced configurations provided to you with a paid offering
+* Understand all the options Cloudflare's Rate Limiting product offers
+* Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
index 81787364edb5b8b..7eb7c2accedce4b 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
index 2533b2fabe4489e..06d7cf0e3aa85f1 100644
--- a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="brand-protection-definition" product="security-center" />
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/index.mdx b/src/content/docs/learning-paths/application-security/security-center/index.mdx
index 443cd3864fd9da6..3c114e0c0f9d8d6 100644
--- a/src/content/docs/learning-paths/application-security/security-center/index.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/index.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="security-center-definition" product="security-center" />
 
@@ -20,5 +20,5 @@ import { Render } from "~/components";
 
 By the end of this module, you will be able to:
 
-- Understand the primary Security Center features such as Security Insights and Brand Protection
-- Review and manage security risks at the account level, encompassing all of your domains in one unified view
+* Understand the primary Security Center features such as Security Insights and Brand Protection
+* Review and manage security risks at the account level, encompassing all of your domains in one unified view
diff --git a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
index 9ce422510bb4427..54e046c2db79eed 100644
--- a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
@@ -16,7 +16,7 @@ Now that you have [connected your private applications](/learning-paths/clientle
 
 By the end of this module, you will be able to:
 
-- Add your application to Cloudflare Access.
-- Create an Access policy.
-- Design reusable policies.
-- Design a domain structure for your applications.
+* Add your application to Cloudflare Access.
+* Create an Access policy.
+* Design reusable policies.
+* Design a domain structure for your applications.
diff --git a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
index 5450985227dcb8e..38a2051d7e24d98 100644
--- a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
@@ -16,7 +16,7 @@ Configure advanced Access policies to meet the specific requirements of your app
 
 By the end of this module, you will be able to:
 
-- Check identity-based attributes that are not directly supported by the Access policy builder.
-- Deliver sensitive web applications in an isolated browser.
-- Apply Gateway HTTP policies without a device client.
-- Connect to applications using their private hostnames without a device client.
+* Check identity-based attributes that are not directly supported by the Access policy builder.
+* Deliver sensitive web applications in an isolated browser.
+* Apply Gateway HTTP policies without a device client.
+* Connect to applications using their private hostnames without a device client.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
index ba3876cbb069c62..700dfb2c429be48 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
@@ -27,6 +27,6 @@ To configure Clientless Web Isolation to augment clientless access, refer to [th
 
 ## Best practices
 
-- For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
-- If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
-- You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
+* For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
+* If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
+* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
index 3d6978794492877..236369d2c8ea5d8 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
@@ -10,10 +10,10 @@ products:
   - cloudflare-one
 ---
 
-As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access. However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
+As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access.  However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Connect to private web applications using their private hostnames.
+* Connect to private web applications using their private hostnames.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
index 96467fa3ad74ab3..1c76266d3e00159 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
@@ -16,4 +16,4 @@ Review the concepts behind clientless access.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose and benefits of clientless access.
+- Understand the purpose and benefits of clientless access.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
index 9b3e4a2a40a5b80..446f1e1c72913e7 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
@@ -12,7 +12,7 @@ products:
 
 Clientless access is a deployment option of a [Zero Trust Network Access (ZTNA)](https://www.cloudflare.com/learning/access-management/what-is-ztna/) service that provides secure access to internal applications without requiring end users to install any software. Users access corporate resources like intranet web apps, SSH terminals, and Windows servers through RDP from their web browser. Clientless access is commonly used to provide internal, [least-privilege access](https://www.cloudflare.com/learning/access-management/principle-of-least-privilege/) to users on unmanaged devices. Users may include third-party contractors, suppliers, and partners, or employees using personal mobile phones as part of an organization's bring-your-own-device (BYOD) policy.
 
-IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as preventing uploads/downloads or copy/paste, or incorporating DLP policies.
+IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as  preventing uploads/downloads or copy/paste, or incorporating DLP policies.
 
 ## Alternatives to clientless access
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
index 7eb4c09d0ecbf01..7015fc5b6c802b5 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
@@ -20,9 +20,9 @@ For an additional point of availability, add a [`cloudflared` replica](/cloudfla
 
 To make your applications easier to manage, standardize the public hostnames that you publish your applications on. Here are a few examples of how customers manage their public hostnames:
 
-- Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
-- If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
-- Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
+* Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
+* If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
+* Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
 
 ## Disable TLS verification
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
index 9c6cbcd138686f2..3120d43f30efdce 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To enable clientless access to your applications, you will need to create a Cloudflare Tunnel that publishes applications to a domain on Cloudflare. A published application creates a public DNS record that routes traffic to a specific address, protocol, and port associated with a private application. For example, you can define a public hostname (`mywebapp.example.com`) to provide access to a web server running on `https://localhost:8080`. When a user goes to `mywebapp.example.com` in their browser, their request will first route to a Cloudflare data center where it is inspected against your configured security policies. Cloudflare will then forward validated requests down your tunnel to the web server.
 
@@ -32,8 +32,9 @@ All users on the Internet can now connect to this application via its public hos
 
 If the tunnel is disconnected:
 
-- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+
 
 :::
 
@@ -41,5 +42,5 @@ If the tunnel is disconnected:
 
 For more control over how traffic routes through your tunnel, refer to the following links:
 
-- [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
-- [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
+* [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
+* [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
index 4f9337b3961247c..fe443c8a8e5c306 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
@@ -16,5 +16,5 @@ Cloudflare Tunnel allows you to securely connect your applications to Cloudflare
 
 By the end of this module, you will be able to:
 
-- Create a Cloudflare Tunnel.
-- Publish your application via a public hostname.
+* Create a Cloudflare Tunnel.
+* Publish your application via a public hostname.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
index a14fda563a6432d..49e6a3bcf50f75b 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/app-launcher" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
index 3de4f9ba2ef5141..3f202ae036ff2e9 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/block-page" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
index 6a740a977e9de4c..23e9d4431ca5719 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/bookmarks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
index 01df3d80b023dd8..681cb50fbfb8882 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
@@ -16,7 +16,7 @@ Cloudflare Access offers several ways to customize the look and feel of the user
 
 By the end of this module, you will be able to:
 
-- Configure the App Launcher so that users can open all applications from single dashboard.
-- Add bookmarks to the App Launcher for applications that are not behind Access.
-- Customize the Access login page with your organization's branding.
-- Display custom block pages when a user is blocked by your Access policies.
+* Configure the App Launcher so that users can open all applications from single dashboard.
+* Add bookmarks to the App Launcher for applications that are not behind Access.
+* Customize the Access login page with your organization's branding.
+* Display custom block pages when a user is blocked by your Access policies.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
index b04f07439a4c9c8..0784ac3db460bb8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The Access login page is where users select their identity provider (IdP) or One-Time PIN prior to accessing the application. Customers who only use one IdP usually enable **Apply instant authentication** for their applications, which redirects end users directly to the SSO login page. If you are using multiple IdPs, we recommend customizing the Access login page to match your branding and minimize user confusion.
 
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
index 65bd38ce4da91e9..6b8b7f8ee3ace2f 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/tags" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
index 0348346f1053ba1..bf6be752e98fce7 100644
--- a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
@@ -18,7 +18,7 @@ If you need to deliver access to non-browser based applications, refer to our co
 
 By the end of this module, you will be able to:
 
-- Set up a Cloudflare account.
-- Add your domain to Cloudflare.
-- Create a Zero Trust organization to manage applications and policies.
-- Configure an identity provider (IdP) for user authentication.
+* Set up a Cloudflare account.
+* Add your domain to Cloudflare.
+* Create a Zero Trust organization to manage applications and policies.
+* Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
index f519cc3082b5669..238af10cab095cb 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
@@ -12,10 +12,10 @@ products:
 
 Most customers have a heterogeneous private application portfolio; some are home-built, some are internal managed services, some have SSO integrations available, and some rely on HTML or other forms of authentication. With that in mind, we recommend that you mix-and-match [onboarding solutions](/learning-paths/clientless-access/migrate-applications/integrated-sso/#potential-solutions) to fit the needs of each individual application. As shown in the table below, you can bucket applications into a series of stack-ranked categories that prioritize ease of implementation and total organizational impact.
 
-| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                         | Outcome                                                                                                                                                                                                                                                  |
-| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                 |
-| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                         |
-| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                 |
-| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.          | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
-| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                             | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                 |
+| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                             | Outcome                                                                                                                                                                                                                                                      |
+| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                     |
+| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                             |
+| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                     |
+| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.      | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
+| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                                                            | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                                                |
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
index 9221ff52404a5f0..87fd2e5aafa3f63 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
@@ -21,6 +21,6 @@ The remaining modules (Modules 6-9) discuss special considerations and setup opt
 
 By the end of this module, you will be able to:
 
-- Manage applications that are directly integrated with an identity provider.
-- Pass user information from Cloudflare Access to your application.
-- Review best practices for onboarding different types of internal applications.
+* Manage applications that are directly integrated with an identity provider.
+* Pass user information from Cloudflare Access to your application.
+* Review best practices for onboarding different types of internal applications.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
index 237820c4e1c9ca7..05491e91bbf7537 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
@@ -31,12 +31,12 @@ app.internal.com")
 
 If your applications use integrated SSO, there are a number of different paths you can take to onboard your applications to Cloudflare Access.
 
-| Solution                                                                                                                   | Steps required                                                                                                      | Pros                                                                                                                                                                        | Cons                                                                                                                     |
-| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                            | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                         | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
-| Present applications on existing internal domains with identical external domains delegated to Cloudflare                  | Add domains to Cloudflare that match internal domains                                                               | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
-| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li>  | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
-| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                   | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/) | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
+| Solution                                                                                                                       | Steps required                                                                                                     | Pros                                                                                                                                                                        | Cons                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                                | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                        | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
+| Present applications on existing internal domains with identical external domains delegated to Cloudflare                      | Add domains to Cloudflare that match internal domains                                                              | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
+| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li> | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
+| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                       | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/)           | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
 
 ## Recommended solution
 
diff --git a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
index 596225f3171052b..7412e5a55b1652c 100644
--- a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
@@ -16,4 +16,4 @@ Integrate Cloudflare Access into your private application development pipeline.
 
 By the end of this module, you will be able to:
 
-- Publish internal applications to Cloudflare using Terraform.
+* Publish internal applications to Cloudflare using Terraform.
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
index 1e092ce574856b2..69453ef2d875700 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
@@ -11,7 +11,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To set up a Zero Trust organization:
 
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
index c0853f8ed750a7f..721649155e70883 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
@@ -16,6 +16,6 @@ Get started by creating a Cloudflare account and initializing the Zero Trust and
 
 By the end of this module, you will have:
 
-- Created a Cloudflare account.
-- Initialized the Zero Trust dashboard.
-- Initialized the Area 1 dashboard.
+* Created a Cloudflare account.
+* Initialized the Zero Trust dashboard.
+* Initialized the Area 1 dashboard.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
index c6dc2bacee257d2..098f42bdf6a93f6 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
@@ -16,7 +16,7 @@ Learn the technical concepts behind Project Cybersafe Schools.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose of the Children’s Internet Protection Act (CIPA).
-- Describe the life of a DNS request.
-- Explain how DNS filtering works to control which websites users can access.
-- Understand the benefits of protecting your email inbox.
+* Understand the purpose of the Children’s Internet Protection Act (CIPA).
+* Describe the life of a DNS request.
+* Explain how DNS filtering works to control which websites users can access.
+* Understand the benefits of protecting your email inbox.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
index c7e8ff61a49fecf..af663840fbd1be0 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
@@ -16,9 +16,9 @@ DNS filtering is a technique to block access to websites or online content. DNS
 
 DNS filtering is commonly used to:
 
-- Protect school data from phishing, ransomware, and malware.
-- Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
-- Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
+* Protect school data from phishing, ransomware, and malware.
+* Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
+* Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
 
 ## How DNS filtering works
 
@@ -52,17 +52,17 @@ DNS filtering only applies to the hostname — `subdomain.domain.tld`. You canno
 
 Secure Web Gateways (SWGs) offer a greater set of capabilities, including:
 
-- [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
-- L4 firewalls to block ports and protocols
-- Antivirus scanning
-- [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
-- [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
+* [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
+* L4 firewalls to block ports and protocols
+* Antivirus scanning
+* [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
+* [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
 
 However, this can make SWGs more complex to deploy. Therefore, many organizations will start with DNS filtering as an initial layer of defense against Internet threats.
 
 ## Related resources
 
-- For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
+* For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
 
 ## Next steps
 
diff --git a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
index c3c1b8bad4a14a0..75e5801177a4b47 100644
--- a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
+++ b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
@@ -10,12 +10,8 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To verify that your DNS traffic is sent to Gateway:
 
-<Render
-	file="gateway/verify-connectivity"
-	product="cloudflare-one"
-	params={{ one: "DNS", two: "queries" }}
-/>
+<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
diff --git a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
index eb3666dd5133b61..b47b3a80514a788 100644
--- a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
@@ -11,4 +11,4 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="magic-transit/advertise-prefixes" product="networking-services" />
+<Render file="magic-transit/advertise-prefixes"	product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
index 49959caa851cad4..6d99098e5ffbd39 100644
--- a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
@@ -14,6 +14,6 @@ Learn core concepts about Magic Transit and its functionality, in order to prote
 ## Objectives
 
 By the end of this module you will be able to:
-
 - Understand what Magic Transit is
 - Why you should use it to protect your IP network
+
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
index a62c27d80ec53ce..96178b835574113 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare DDoS protection automatically detects and mitigates Distributed Denial of Service (DDoS) attacks using its Autonomous Edge. Magic Transit customers have access to additional features, such as:
 
@@ -26,10 +26,7 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/tcp-protection-intro" product="ddos-protection" />
 
-<Render
-	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
-	product="ddos-protection"
-/>
+<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
 
 #### Setup
 
@@ -39,11 +36,8 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/dns-protection-intro" product="ddos-protection" />
 
-<Render
-	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
-	product="ddos-protection"
-/>
+<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
 
 #### Setup
 
-<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
+<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
index 51c5f4f2f692123..482c2b215ae173f 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -19,16 +19,12 @@ import { Render } from "~/components";
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT:
-			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table",
+		routingTableName: "Magic Transit Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
index bd53e3d65b54e92..4c93f4789229aab 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
@@ -11,31 +11,22 @@ products:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
-	}}
-/>
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
index b98f8551ad40475..6f1888d2fbbff7e 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
@@ -14,6 +14,6 @@ In this unit you will learn how to set up tunnels and routes to steer traffic.
 ## Objectives
 
 By the end of this module you will be able to:
-
 - Create tunnels on both the Cloudflare side and your router side to connect to your infrastructure.
 - Configure static routes or dynamic routes with BGP peering to steer your traffic via next-hop from Cloudflare's global network to your connected networks.
+
diff --git a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
index 40adf54d7baae5f..1efb22a01b5feef 100644
--- a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
@@ -17,8 +17,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation:
-			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
@@ -33,4 +32,4 @@ Cloudflare also recommends that you enable the following account notifications f
 - (Optional) Advanced Layer 3/4 DDoS Attack Alert
 - (Optional) Cloudflare status - Maintenance Notification (in case you want to be alerted regarding maintenance in specific Cloudflare data centers).
 
-Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
+Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/get-started.mdx b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
index 16b63ff273ced89..58e23aba7e9451b 100644
--- a/src/content/docs/learning-paths/data-center-protection/get-started.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
@@ -9,10 +9,6 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/get-started"
-	product="networking-services"
-	params={{ magicWord: "Learning Path" }}
-/>
+<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Learning Path" }} />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
index 88f72d32072ad16..7d6e4bdd8b5ba93 100644
--- a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
@@ -10,7 +10,6 @@ products:
 ---
 
 After setting up your Magic Transit product, Cloudflare validates:
-
 - Tunnel connectivity
 - Tunnel and endpoint [health checks](/magic-transit/reference/tunnel-health-checks/#types-of-health-checks)
 - Letter of Agency (LOA)
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
index efe4d0f80aa7a93..4b7ab7651839800 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
@@ -14,7 +14,7 @@ Migrating your DNS from an on-premises BIND solution to a cloud-based provider l
 
 By the end of this module, you will be able to:
 
-- Plan and take inventory of your DNS migration.
-- Prepare for the migration with minimal downtime.
-- Learn how to make the actual switch to Cloudflare.
-- Verify and stabilize after your migration.
+* Plan and take inventory of your DNS migration.
+* Prepare for the migration with minimal downtime.
+* Learn how to make the actual switch to Cloudflare.
+* Verify and stabilize after your migration.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
index ac9f126e6cfb046..05eae75787849b0 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
@@ -12,55 +12,55 @@ Detailed planning is the cornerstone of a successful DNS migration.
 
 ## 1. Understand your current BIND setup
 
-1. Identify all DNS zones currently hosted on your BIND servers.
-2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.
-3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.
-   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.
+1. Identify all DNS zones currently hosted on your BIND servers.  
+2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.  
+3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.  
+   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.  
    - For policy-based internal DNS, consider Cloudflare Zero Trust features such as DNS policies and Internal DNS (Beta). For more details, refer to [Cloudflare DNS](/dns/) and [Internal DNS](/dns/internal-dns/).
-4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:
-   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.
-   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.
-   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:
-     - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)
-     - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)
+4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:  
+   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.  
+   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.  
+   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:  
+      - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)  
+      - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)  
 
-     These setups document how to restrict which IP addresses can perform zone transfers.
+      These setups document how to restrict which IP addresses can perform zone transfers.
 
-5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.
+5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.  
 
 ## 2. Define scope and objectives
 
-Clearly list all domain names to be migrated and define success criteria for the migration.
+Clearly list all domain names to be migrated and define success criteria for the migration.  
 
 ## 3. Cloudflare account and familiarization
 
-1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.
-2. Familiarize yourself with the Cloudflare DNS dashboard and its features.
+1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.  
+2. Familiarize yourself with the Cloudflare DNS dashboard and its features.  
 3. Consider the different [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) you can manage on Cloudflare and how they map from BIND.
 
 ## 4. DNSSEC strategy (critical)
 
-Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.
+Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.  
 
-Cloudflare supports two main migration approaches when DNSSEC is enabled:
+Cloudflare supports two main migration approaches when DNSSEC is enabled: 
 
-- Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.
-- Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+   - Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.  
+   - Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).  
 
-**Disable-and-re-enable approach (safer for most teams):**
+**Disable-and-re-enable approach (safer for most teams):**  
 
-1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.
-2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.
+1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.  
+2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.  
 
-\*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.
+*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.  
 
 For more information about DNSSEC on Cloudflare, refer to [DNSSEC](/dns/dnssec/).
 
 ## 5. Choose migration window
 
-Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.
+Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.  
 
 ## 6. Develop communication and rollback plan
 
-- Communication: Plan how to communicate with stakeholders before, during, and after the migration.
-- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
+- Communication: Plan how to communicate with stakeholders before, during, and after the migration.  
+- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
index b3b2d045d7021ec..f53af665ca87cfd 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
@@ -14,49 +14,49 @@ Careful preparation will minimize downtime and issues during the cutover.
 
 ## 1. Reduce DNS record TTLs (Time To Live)
 
-At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).
+At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).  
 
-This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.
+This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.  
 
-- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).
+- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).  
 
 ## 2. Export zone files from BIND
 
-Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.
+Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.  
 
 ## 3. Add domains to Cloudflare
 
-1. Log in to your Cloudflare dashboard.
+1. Log in to your Cloudflare dashboard.  
 
    <DashButton url="/?to=/:account/home" />
 
-2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.
+2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.  
 
 ## 4. Import DNS Records into Cloudflare
 
-Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.
-
-<DashButton url="/?to=/:account/home" />
+Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.  
+   
+   <DashButton url="/?to=/:account/home" />
 
-- Verification (Crucial):
-  - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.
-  - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.
-  - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).
-- Proxy status (orange vs grey cloud):
-  - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.
-  - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).
-  - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
+- Verification (Crucial): 
+   - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.  
+   - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.  
+   - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).  
+- Proxy status (orange vs grey cloud):  
+   - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.  
+   - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).  
+   - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
 
 ## 5. DNSSEC preparation (if currently enabled)
 
-Complete this step before you change your nameservers at the registrar.
+Complete this step before you change your nameservers at the registrar.  
 
 :::note
 
-For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy,  refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
 :::
 
-- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.
+- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.  
 - **Wait for DS TTL:** Wait at least the full DS record TTL published at the parent zone, and preferably up to 1.5 times that TTL, before you change nameservers. This ensures that validating resolvers stop expecting the old DNSSEC chain. The typical TTL duration for DS records is set to +24 hours (86,400 seconds).
-- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.
+- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.  
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
index 1decb20de5cda62..7307e676b28660a 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
@@ -12,29 +12,30 @@ Phase 3 is when you make the actual switch to Cloudflare.
 
 ## 1. Final verification
 
-Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.
+Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.  
 
 ## 2. Update nameservers at your registrar
 
-1.  Log in to your domain registrar's control panel for each domain.
-2.  Navigate to the section for managing nameservers.
-3.  Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.
-4.  Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).
-5.  Save the changes.
+   1. Log in to your domain registrar's control panel for each domain.  
+   2. Navigate to the section for managing nameservers.  
+   3. Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.  
+   4. Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).  
+   5. Save the changes.  
 
 ## 3. Monitor propagation
 
-- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).
-- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.
-  - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)
-  - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
-  - `whois yourdomain.com`
-  - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
-  You are looking for the Cloudflare nameservers to be reported consistently.
+- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).  
+- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.  
+   - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)  
+   - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
+   - `whois yourdomain.com`
+   - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
+   
+   You are looking for the Cloudflare nameservers to be reported consistently. 
 
 ## 4. Initial testing
 
 Once propagation appears to be widespread, perform basic resolution tests for critical records (for example, your website's `A` record and any `MX` records, if you had them set up).
 
-- `dig yourdomain.com A +short`
-- `dig yourdomain.com MX +short`
+- `dig yourdomain.com A +short`  
+- `dig yourdomain.com MX +short`
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
index e08e73b597e57b0..e1f0d1f96eb1bac 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
@@ -14,49 +14,47 @@ After the cutover, verify and stabilize.
 
 ## 1. Thorough testing and validation
 
-1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.
-2. Test from different networks and geographical locations if possible.
-3. Monitor application logs for any DNS-related errors.
+1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.  
+2. Test from different networks and geographical locations if possible.  
+3. Monitor application logs for any DNS-related errors.  
 
 ## 2. Enable DNSSEC in Cloudflare (if disabled earlier)
 
 Enable DNSSEC only after you are confident that DNS is resolving correctly through Cloudflare and that nameserver changes have fully propagated. In practice, plan for at least one full DS TTL after you add new DS records at the registrar.
 
-**Action in Cloudflare:**
+**Action in Cloudflare:**  
+   1. In the Cloudflare dashboard, go to your zone's **DNS Settings**.  
 
-1.  In the Cloudflare dashboard, go to your zone's **DNS Settings**.
+      <DashButton url="/?to=/:account/:zone/dns/settings" />
 
-    <DashButton url="/?to=/:account/:zone/dns/settings" />
-
-2.  Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details.
-
-**Action at registrar:**
-
-1.  Log in to your domain registrar.
-2.  Navigate to the DNSSEC management section for your domain.
-3.  Add the `DS` record details provided by Cloudflare.
+   2. Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details. 
+ 
+**Action at registrar:**  
+   1. Log in to your domain registrar.  
+   2. Navigate to the DNSSEC management section for your domain.  
+   3. Add the `DS` record details provided by Cloudflare.  
 
 After adding the `DS` record, allow time for propagation and then validate your configuration with tools such as [DNSViz](https://dnsviz.net) or [Verisign's DNSSEC debugger](https://dnssec-debugger.verisignlabs.com/). For more information, refer to [DNSSEC](/dns/dnssec/).
 
-:::note
-If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
-:::
+   :::note
+    If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
+   :::
 
 ## 3. Adjust TTLs in Cloudflare
 
-After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).
+After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).  
 
 Higher TTLs improve resolver cache efficiency and can reduce latency by allowing recursive resolvers to reuse cached answers for longer, at the cost of slower propagation when you make changes.
 
 ## 4. Review and enable Cloudflare proxy features
 
-If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.
+If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.  
 
 ## 5. Decommission On-Prem BIND servers
 
 Only after a significant stabilization period (for example, several days to a week after full propagation and successful testing) and when you are fully confident in the Cloudflare setup, decommission the on-premise BIND servers.
 
-Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.
+Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.   
 
 ## 6. Update internal documentation and monitoring
 
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
index 5d966db6e4f2e51..8e23617d11caed2 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
@@ -8,15 +8,15 @@ products:
   - dns
 ---
 
-- Plan meticulously: Do not rush the planning and preparation phases.
-- Communicate clearly: Keep stakeholders informed.
-- Lower TTLs in advance: This is crucial for a faster cutover.
-- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.
-- Verify, verify, verify: Double-check record imports and functionality at each stage.
-- Test thoroughly: From multiple locations and for all critical services.
-- Have a rollback plan: Know how to revert if necessary.
-- Migrate during low traffic: Minimize potential user impact.
-- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.
+- Plan meticulously: Do not rush the planning and preparation phases.  
+- Communicate clearly: Keep stakeholders informed.  
+- Lower TTLs in advance: This is crucial for a faster cutover.  
+- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.  
+- Verify, verify, verify: Double-check record imports and functionality at each stage.  
+- Test thoroughly: From multiple locations and for all critical services.  
+- Have a rollback plan: Know how to revert if necessary.  
+- Migrate during low traffic: Minimize potential user impact.  
+- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.  
 - Take advantage of Cloudflare features: Once stable, explore and implement Cloudflare's security and performance enhancements.
 
-By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
+By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
index a1bed2340a8f735..13c9e675861f17d 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
@@ -12,3 +12,4 @@ products:
   - dlp
   - casb
 ---
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
index 776126418ebd729..4f342e9997e31ea 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
@@ -20,3 +20,4 @@ The goal of this learning path is to provide Cloudflare One users with the strat
 - Monitor AI usage: Utilize Cloudflare One's tools, such as the Shadow IT dashboard and API CASB integrations, to gain visibility into both sanctioned and unsanctioned AI application usage.
 - Build security policies: Create granular security policies using Cloudflare Gateway to control AI usage, prevent data loss with DLP, and manage user behavior through actions like blocking or redirecting.
 - Secure sanctioned models: Apply Zero Trust principles to sanctioned AI models and internal services like Model Context Protocol (MCP) servers to ensure secure access and protect sensitive data from being exposed.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
index 29330ef6e90787c..c8811b8737b69c2 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
@@ -22,3 +22,4 @@ MCP uses a client-server architecture where an AI agent acts as the client and s
 ## What are the security concerns with MCP?
 
 MCP doesn't have native authentication, authorization, or encryption. Because it functions similarly to an API, many of the same security considerations apply. If developers do not proactively implement security measures like Transport Layer Security (TLS) and rate limiting, MCP servers can be vulnerable to attacks, data leaks, and unauthorized access. Organizations must ensure that they validate inputs and protect confidential data to secure their MCP implementations.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
index 97b3651ba7daa5d..1d18a0ebba41b16 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
@@ -18,3 +18,4 @@ Shadow AI is the use of any AI tool or application by employees without the form
 Since it may not be feasible to eliminate all instances of shadow AI, organizations can manage the risks by taking a balanced approach. First, it is essential to foster collaboration and open communication between IT and other departments to understand why employees are using these tools. Next, implement guardrails by developing a flexible governance framework with clear guidelines on which types of AI systems can be used and how sensitive information should be handled. Finally, monitor AI usage with network tools to track what is being used and educate employees on the risks of unauthorized AI.
 
 To combat the risks associated with shadow AI, Cloudflare's API-driven CASB integrates with SaaS applications and cloud environments to scan for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
index 2f4c30d5cb527a1..f98c47c842d9d81 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
@@ -16,4 +16,4 @@ To use the recommended AI security solutions in this learning path, you will nee
 
 :::note
 If you are new to securing your Internet traffic, refer to [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/) to get started and then return to this learning path to continue securing your organizations.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
index 7b68b9d51991f49..67b07408d9070cd 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
@@ -17,7 +17,6 @@ Before you can secure AI, you need to understand your organization's goals and c
 The level of risk you are willing to accept will determine how quickly you need to act and how deeply you need to implement security measures. Your specific concerns will then guide the exact security approaches you take to monitor and control AI usage.
 
 To begin, consider these questions to help shape your strategy:
-
 - Sanctioned versus shadow AI: Are your employees already using approved AI services, or are you primarily concerned with shadow AI — unapproved applications that may pose a risk? Note: Some approved vendors may offer embedded AI functionality. Consider whether those AI services are a risk, too.
 - Data sensitivity: What types of sensitive data do you currently monitor, classify, and protect? This will help you identify what you need to safeguard when employees interact with AI. If you have not determined this yet, refer to [Define your sensitive data](/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention/#define-your-sensitive-data) to learn more.
 - Encouraging user behavior: Do you want to encourage or limit user engagement with AI? How much do you expect your employees to use AI in a controlled, sanctioned way?
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
index d466618622bbdb9..b5caf20d92a283f 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
@@ -16,4 +16,4 @@ Businesses are eager to realize the potential boosts to productivity and efficie
 
 IT and security leaders are often asked to address risks and deal with increasing challenges like the use of shadow AI before they have an AI security strategy.
 
-Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively.
+Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively. 
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
index 5edae280f6bbf30..48c3654da15b283 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
@@ -17,3 +17,4 @@ Monitoring AI usage is one of the first steps in assessing holistic risk. Cloudf
 After you begin to understand your organization's AI usage, you should develop a balanced perspective on what constitutes sanctioned use of a tool. A good practice is to review applications in phases and then apply security policies based on those phases. For example, you can apply different security policies to applications that are considered approved, unapproved, unreviewed, or in review until they pass your corporate security standards and data privacy reviews.
 
 This section will detail options for assessing and understanding that risk by using inline (client) and out-of-band (API CASB) based methods.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
index 18a65bd00076557..38cfd98df28c2ac 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
@@ -13,11 +13,10 @@ products:
 ---
 
 When you enable [TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/#turn-on-tls-decryption), you can review the prompts and responses for supported AI applications. This allows you to understand three key things about AI application usage:
-
 - The sanctioned and unsanctioned AI tools your users are engaging with.
 - How they are interacting with them.
 - What information they are sharing.
 
 ![Log entry for a prompt detected using AI prompt protection.](~/assets/images/learning-paths/holistic-ai-security/gateway-prompt-log.png)
 
-You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
+You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
index aacf8456e79fe1c..c60e183df9211b9 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
@@ -20,6 +20,7 @@ To review how your organization uses AI apps, start with the Cloudflare [Shadow
 
 ![Shadow IT dashboard showing utilization of application statuses (Approved, Unapproved, In Review, Unreviewed).](~/assets/images/learning-paths/holistic-ai-security/shadowit-dashboard-ai-apps.png)
 
-This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as _Approved_. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
+This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as *Approved*. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
 
 ![The App Library filtered to show some of the supported Artificial Intelligence applications.](~/assets/images/learning-paths/holistic-ai-security/ai-app-type-app-library.png)
+
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
index da4bbe2960c586f..9d1796cbc8e77a5 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { GlossaryDefinition, Render } from "~/components";
+import { GlossaryDefinition, Render } from "~/components"
 
 There's more to a load balancer than just distributing traffic, however.
 
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
index 7369a7445edbd8d..2a58f062dc5eeeb 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
@@ -14,7 +14,7 @@ Learn the concepts behind load balancing, whether you are using Cloudflare or an
 
 By the end of this module, you will be able to:
 
-- Explain what load balancing is.
-- Describe the differences between load balancers, pools, and servers.
-- Explain what pool health is and how it affects load balancer traffic.
-- List the different ways your traffic can be routed.
+* Explain what load balancing is.
+* Describe the differences between load balancers, pools, and servers.
+* Explain what pool health is and how it affects load balancer traffic.
+* List the different ways your traffic can be routed.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
index e132195e0f7fb3a..7dd7ff6d269783a 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
@@ -8,13 +8,13 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 At it's most basic, load balancing is made up of three components:
 
-- **Pools**: Which contain one or more endpoints.
-- **Endpoints**: Which respond to individual requests.
-- **A load balancer**: Which decides which traffic goes to each pool.
+* **Pools**: Which contain one or more endpoints.
+* **Endpoints**: Which respond to individual requests.
+* **A load balancer**: Which decides which traffic goes to each pool.
 
 ## How it works
 
@@ -22,7 +22,7 @@ Normally, requests to your application would go to individual servers directly.
 
 With a load balancer, requests first go through the load balancer. Your load balancer then routes requests to specific pools.
 
-<Render file="load-balancing-diagram" product="load-balancing" /> <br />
+<Render file="load-balancing-diagram" product="load-balancing" /> <br/>
 
 Within each pool, requests then go to individual endpoints. And that endpoint is what responds to the request.
 
@@ -37,6 +37,6 @@ Within each pool, requests then go to individual endpoints. And that endpoint is
       end
 ```
 
-<br />
+<br/>
 
 This progression of load balancer --> pool --> endpoint is the core part of how a load balancer works.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
index d8019a91c1cf983..b5cf54d4113227f 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
@@ -8,11 +8,11 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Before, we covered how requests move from load balancers to pools and then from pools to individual servers.
 
-What we did not mention, however, was _how_ the load balancer and pools make those decisions.
+What we did not mention, however, was *how* the load balancer and pools make those decisions.
 
 This is a concept known as routing.
 
@@ -60,5 +60,5 @@ Often, load balancers have a special pool known as the **Fallback Pool**, which
 
 Finally, specific settings can also affect the ways a load balancer distributes traffic, such as:
 
-- Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
-- Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
+* Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
+* Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
index cc8e287532908ff..6337e5cf7172cd6 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="custom-rules-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/index.mdx b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
index 370f197fbab2a2d..eeee73027d3ca18 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
@@ -14,7 +14,7 @@ Explore the configuration choices available for your Cloudflare load balancer.
 
 By the end of this module, you will be able to:
 
-- Describe the difference between load balancing at different layers of the network stack.
-- Identify when a load balancer should utilize session affinity.
-- Describe the different policies for endpoint steering and traffic steering.
-- List the different options available to monitor server health.
+* Describe the difference between load balancing at different layers of the network stack.
+* Identify when a load balancer should utilize session affinity.
+* Describe the different policies for endpoint steering and traffic steering.
+* List the different options available to monitor server health.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
index 820f34fada45575..34aa1d6847c2ece 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
@@ -20,8 +20,10 @@ If you want to share a load balancing configuration across multiple hostnames, y
 
 :::note
 
+
 You could also achieve the same goal or create more advanced routing decisions by setting up DNS Overrides within [Origin Rules](/rules/origin-rules/) on each hostname that override the hostname to `lb.example.com`.
 
+
 :::
 
 ## Unique configurations
diff --git a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
index b430e5865cbd6a6..d03dbb9b4796bd1 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
@@ -8,17 +8,17 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="origin-steering-definition" product="load-balancing" />
 
----
+***
 
 ## Policies
 
 <Render file="origin-steering-policies" product="load-balancing" />
 
----
+***
 
 ## Weights
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
index 70a7b3e021585fc..dd99e87ee3c3d01 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="session-affinity-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
index 3b370b1ed392b31..9ced34523117fe9 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
@@ -8,8 +8,8 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
-<Render file="traffic-steering-definition" product="load-balancing" /> <br />
+<Render file="traffic-steering-definition" product="load-balancing" /> <br/>
 
 <DirectoryListing folder="load-balancing/understand-basics/traffic-steering/steering-policies" />
diff --git a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
index 1b2a9ce5c84006d..a1fbbb640bf00cb 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
@@ -8,15 +8,15 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 With Cloudflare, you can choose between three types of load balancers:
 
-- [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
-- [DNS-only](#dns-only-load-balancing)
-- [Layer 4 (TCP)](#layer-4-load-balancing)
+* [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
+* [DNS-only](#dns-only-load-balancing)
+* [Layer 4 (TCP)](#layer-4-load-balancing)
 
----
+***
 
 ## Layer 7 load balancing
 
@@ -26,7 +26,7 @@ With Cloudflare, you can choose between three types of load balancers:
 
 <Render file="layer-7-load-balancing-benefits" product="load-balancing" />
 
----
+***
 
 ## DNS-only load balancing
 
@@ -34,13 +34,13 @@ With Cloudflare, you can choose between three types of load balancers:
 
 ### Benefits
 
-<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br />
+<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br/>
 
 ### Limitations
 
 <Render file="dns-load-balancing-limitations" product="load-balancing" />
 
----
+***
 
 ## Layer 4 load balancing
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
index a34dcbf56c1a141..e44453449357179 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="confirm-pool-health" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
index 54cf2a41d9f5d89..f963bd4a1cc3aee 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
@@ -10,8 +10,8 @@ products:
 
 Before setting up anything related to your load balancer, make sure you test that production hostnames meet the following criteria:
 
-- Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
-- Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
+* Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
+* Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 
 After confirming each of these conditions are met, you can proceed with setting up your load balancer.
 
@@ -19,5 +19,5 @@ After confirming each of these conditions are met, you can proceed with setting
 
 Depending on your preferences and infrastructure, you might route traffic to your load balancer in different ways:
 
-- For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
-- However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
+* For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
+* However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/index.mdx b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
index 2f7ceb3e5cd7744..20b76253146a2fe 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
@@ -14,13 +14,13 @@ Create a load balancer that monitors endpoint health and intelligently routes tr
 
 By the end of this module, you will be able to:
 
-- Configure a monitor and health checks.
-- Create a pool.
-- Create a load balancer.
-- Analyze traffic patterns.
+* Configure a monitor and health checks.
+* Create a pool.
+* Create a load balancer.
+* Analyze traffic patterns.
 
 ## Prerequisites
 
-- Multiple endpoints, either physical or cloud-based.
-- Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
-- Two hostnames, one for test traffic and the other for production traffic.
+* Multiple endpoints, either physical or cloud-based.
+* Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
+* Two hostnames, one for test traffic and the other for production traffic.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
index 5cb5b8556548c35..7dea7a8b054a166 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Your load balancer should be receiving production traffic (and you can confirm this by reviewing the [analytics](/load-balancing/reference/load-balancing-analytics/)).
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
index 5f6e8812e2b018b..f2dda24cae894f0 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
@@ -8,6 +8,6 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="route-production-traffic" product="load-balancing" />
diff --git a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
index a9014dbe620e151..158ed1dbb6f5b89 100644
--- a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
+++ b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
@@ -20,10 +20,10 @@ Some common mTLS use cases are:
 
 There are two main ways to use mTLS at Cloudflare, either by using the Application Security offering (optionally including [API Shield](/api-shield/)) or [Cloudflare Access](/cloudflare-one/access-controls/policies/). Below is a non-exhaustive overview table of their differences:
 
-| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | Client Certificate Details                                            | Forwarded to the origin server via [Cloudflare API](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-api), [Cloudflare Workers](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-workers), and [Managed Transforms](/ssl/client-certificates/forward-a-client-certificate/#managed-transforms). | Forwarded to the origin server via [Cloudflare API](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-api), [Cloudflare Workers](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-workers), and [Managed Transforms](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#managed-transforms). Client Certificate headers and [Cf-Access-Jwt-Assertion](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/) JWT header can be forwarded to the origin server. |
-| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
index 4bc6231c21b5a96..93042dd1fa01f4d 100644
--- a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
+++ b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
@@ -26,4 +26,4 @@ mTLS user authentication is included with Cloudflare Access and depends on the n
 
 ## Option 3: mTLS Service Authentication
 
-The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
+The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
index c481f87de2d65a0..16c8ccf32ad86d5 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 Cloudflare provides analytics for [security events](/waf/analytics/security-events/), [traffic patterns](/analytics/account-and-zone-analytics/zone-analytics/), and more according to the level of your zone's plan.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
index 05f03d0f144275e..a4da185bc6f5065 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
@@ -15,7 +15,7 @@ Learn how to customize and augment Cloudflare’s DDoS protection.
 
 By the end of this module, you will be able to:
 
-- Audit DNS records to prevent accidental IP address exposures.
-- Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
-- Augment Cloudflare's default analytics to examine attacks in more detail.
-- Evaluate different ways to restrict external connections to your origin server.
+* Audit DNS records to prevent accidental IP address exposures.
+* Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
+* Augment Cloudflare's default analytics to examine attacks in more detail.
+* Evaluate different ways to restrict external connections to your origin server.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
index c2f9d500ff25ee7..c37bbf8ec26a7db 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
@@ -15,6 +15,6 @@ Get world-class DDoS protection with a few simple steps.
 
 By the end of this module, you will be able to:
 
-- List the built-in DDoS protection measures provided by Cloudflare.
-- Implement a few, simple customizations to improve DDoS protection.
-- Set up DDoS-related notifications.
+* List the built-in DDoS protection measures provided by Cloudflare.
+* Implement a few, simple customizations to improve DDoS protection.
+* Set up DDoS-related notifications.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
index 882b2ac86f7af63..d464cb2979e60be 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The first - and often easiest - step of DDoS protection is making sure your DNS records are [proxied](/dns/proxy-status/) through Cloudflare.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
index 504b661aeade97c..52946023a5865ab 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Another part of preparing for DDoS attacks is knowing when your application is being attacked.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
index 2dde4bb728e4cad..315ae18c24d496c 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
@@ -13,8 +13,8 @@ In some circumstances - specifically when an application allows client-initiated
 
 When you use an SSL/TLS certificate issued by Cloudflare[^1], you can reduce the impact of this vulnerability by:
 
-- Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
-- Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
+* Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
+* Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
 
 [^1]: Meaning either [Universal](/ssl/edge-certificates/universal-ssl/) or [Advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
index 5d276a7499bc51b..cfb31f718c1afba 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
@@ -15,5 +15,5 @@ Learn the concepts behind DDoS attacks and protection, whether you are using Clo
 
 By the end of this module, you will be able to:
 
-- Explain what a DDoS attack is and how it could affect your application.
-- List the common ways to prevent DDoS attacks.
+* Explain what a DDoS attack is and how it could affect your application.
+* List the common ways to prevent DDoS attacks.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
index 55992a486b4f980..bc327a66a03d394 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
@@ -18,7 +18,7 @@ With Cloudflare Zero Trust, you can apply granular security policies to all traf
 
 By the end of this module, you will be able to:
 
-- Create Zero Trust policies to secure access to your private network.
-- Enforce Cloudflare One Client session timeouts.
-- Display custom block messages.
-- Discover Shadow IT within your private network.
+* Create Zero Trust policies to secure access to your private network.
+* Enforce Cloudflare One Client session timeouts.
+* Display custom block messages.
+* Discover Shadow IT within your private network.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
index 78c93a432dea818..29387c50590e5a7 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
@@ -17,11 +17,11 @@ Most policy building for private network access happens within the Gateway DNS a
 
 Before building your policies, it is helpful to ask yourself a few questions:
 
-- Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
-- Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
-- Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
-- Do you have sources of truth for identity and device posture that will be used in policies?
-- Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
+* Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
+* Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
+* Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
+* Do you have sources of truth for identity and device posture that will be used in policies?
+* Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
 
 ## Prepare to build policies
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
index a78d1ef69ea07de..943c9627d37f792 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Most legacy VPNs have a global timeout setting that requires end users to log in every X hours or resets VPN profiles at a certain frequency. By doing continuous identity evaluation, a Zero Trust security model eliminates the need for most of the user-interrupting workflows triggered by session timeouts. However, there can still be valid reasons to want users to reauthenticate, either on a recurring basis or to access specific, highly-sensitive or regulated internal services.
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
index 43ea4220994ee40..10077edc657d785 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
@@ -43,13 +43,11 @@ Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build
 [Logs](/cloudflare-one/insights/logs/) provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment.
 
 To review traffic activity for applications protected by Access:
-
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **Access authentication logs**.
 3. Review the [per-request logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#per-request-logs) for your application.
 
 To review traffic activity in the [Gateway logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/):
-
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **HTTP request logs**, **Network logs**, or **DNS query logs** depending on your investigation scope.
 
@@ -100,8 +98,7 @@ To create a device connectivity anomaly notification:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
-
+    <DashButton url="/?to=/:account/notifications" />
 2. Select **Add**.
 3. Find **Product** DEX and **Alert type** Device connectivity anomaly, and choose **Select**.
 4. Name the notification.
@@ -119,4 +116,4 @@ Once your policies are live, you can use [DEX tests](/learning-paths/replace-vpn
 
 To learn how to use Logs, Analytics, and DEX together during real-world situations, like onboarding, daily monitoring, and troubleshooting, refer to [Insights](/cloudflare-one/insights/) for more example use cases.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
index e227e835a77f69b..f21582fa384073e 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
@@ -17,6 +17,6 @@ Concepts explain the basic ideas behind how Cloudflare Zero Trust works.
 
 By the end of this module, you will be able to:
 
-- Explain how Cloudflare works.
-- Describe the purpose of a VPN.
-- Understand the benefits of switching to a Zero Trust architecture.
+* Explain how Cloudflare works.
+* Describe the purpose of a VPN.
+* Understand the benefits of switching to a Zero Trust architecture.
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
index 92bfa07cbd99ff5..9d605a12bcca0b2 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
index 7a46245dacacf0c..62f98d74710996a 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
@@ -12,7 +12,7 @@ products:
   - gateway
 ---
 
-import { Render, Tabs, TabItem } from "~/components";
+import { Render, Tabs, TabItem } from "~/components"
 
 Cloudflare Tunnel is an outbound-only daemon service that can run on nearly any host machine and proxies local traffic once validated from the Cloudflare network. User traffic initiated from the Cloudflare One Client onramps to Cloudflare, passes down your Cloudflare Tunnel connections, and terminates automatically in your local network. Traffic reaching your internal applications or services will carry the local source IP address of the host machine running the `cloudflared` daemon.
 
@@ -73,16 +73,17 @@ All internal applications and services in this IP range are now connected to Clo
 
 If the tunnel is disconnected:
 
-- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+
 
 :::
 
 ## Best practices
 
-- Segregate production and staging traffic among different Cloudflare tunnels.
-- Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
-- Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
-- [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
-- [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
-- [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
+* Segregate production and staging traffic among different Cloudflare tunnels.
+* Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
+* Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
+* [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
+* [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
+* [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
index 9ff188f45e603dd..d36ecb80dd109d4 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
@@ -33,17 +33,17 @@ There are [multiple ways](/reference-architecture/architectures/sase/#connecting
 
 ## Comparison table
 
-|                       | Cloudflare Mesh                                                        | Cloudflare Tunnel                                                                                                                                                                                                                                   |
-| --------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bidirectional traffic | ✅                                                                     | ❌                                                                                                                                                                                                                                                  |
-| High availability     | ✅ (active-passive)                                                    | ✅ (active-active replicas)                                                                                                                                                                                                                         |
-| Source IP of request  | Virtual IP of requesting device                                        | `cloudflared` host machine                                                                                                                                                                                                                          |
-| Host machine          | Linux (amd64, arm64)                                                   | Linux, macOS, Windows                                                                                                                                                                                                                               |
-| IPv4                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
-| IPv6                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
-| OSI layer             | L3                                                                     | L7                                                                                                                                                                                                                                                  |
-| Protocol              | MASQUE                                                                 | QUIC or HTTP/2                                                                                                                                                                                                                                      |
-| Protocols proxied     | TCP, UDP, ICMP                                                         | HTTP/S, TCP, SSH, RDP, SMB                                                                                                                                                                                                                          |
+|                       | Cloudflare Mesh                 | Cloudflare Tunnel           |
+| --------------------- | ------------------------------- | --------------------------- |
+| Bidirectional traffic | ✅                              | ❌                          |
+| High availability     | ✅ (active-passive)             | ✅ (active-active replicas) |
+| Source IP of request  | Virtual IP of requesting device | `cloudflared` host machine  |
+| Host machine          | Linux (amd64, arm64)            | Linux, macOS, Windows       |
+| IPv4                  | ✅                              | ✅                          |
+| IPv6                  | ✅                              | ✅                          |
+| OSI layer             | L3                              | L7                          |
+| Protocol              | MASQUE                          | QUIC or HTTP/2              |
+| Protocols proxied     | TCP, UDP, ICMP                  | HTTP/S, TCP, SSH, RDP, SMB  |
 | Connection handling   | End-to-end — preserves long-lived TCP connections across the full path | Proxied — TCP connections are terminated and re-established at Cloudflare, which can interrupt long-lived sessions (for example, SAP transactions, database replication streams, or persistent RDP sessions may drop when `cloudflared` reconnects) |
 
 ## Recommendation
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
index 73d7ed1fcc063fd..8dfc2d8f3e258e1 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
@@ -17,6 +17,6 @@ This module covers how to connect your private network services and applications
 
 By the end of this module, you will be able to:
 
-- Create a Cloudflare Tunnel.
-- Configure private network routes for your tunnel.
-- Understand how to size and scale your tunnel.
+* Create a Cloudflare Tunnel.
+* Configure private network routes for your tunnel.
+* Understand how to size and scale your tunnel.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
index 536d489c6b31be9..c6b1493e5165c97 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
@@ -10,7 +10,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="tunnel/virtual-networks-intro" product="cloudflare-one" />
 
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
index 061277556b36313..91c1e173b09527c 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Now that you have a Cloudflare Tunnel up and running, evaluate whether `cloudflared` has enough system resources to handle the expected volume of requests from end users. <Render file="tunnel/availability/tunnel-capacity-intro" product="cloudflare-one" />
 If you have exhausted the ports on a single machine, you will need to add additional servers running `cloudflared`.
diff --git a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
index b7e1bbfc5ccef53..9add3ff07321ee9 100644
--- a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
@@ -13,7 +13,7 @@ products:
 
 To make the most of this learning path, make sure that you have the following:
 
-- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-- A private network with applications or services that are available locally or via a VPN.
-- A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
-- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
+* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+* A private network with applications or services that are available locally or via a VPN.
+* A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
+* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
index 1b88fb9f8b8b920..a516b09d3f257d6 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
@@ -19,7 +19,7 @@ Learn how to troubleshoot your ZTNA deployment.
 
 By the end of this module, you will be able to:
 
-- Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
-- Fix the most common causes of connectivity issues.
+* Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
+* Fix the most common causes of connectivity issues.
 
 <Render file="warp/troubleshooting-guide-reference" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
index 4a8c12e1c07aa82..e4c61751d31b4a3 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="tunnel/troubleshoot-private-networks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
index d83c0f50abab201..fa82b98809cbb10 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
@@ -18,6 +18,6 @@ DNS security is an important, wide-reaching, and early action in the lifecycle o
 
 By the end of this module, you will be able to:
 
-- Create your first Gateway DNS policy.
-- Build an allow or block list for use in firewall policies.
-- Onboard networks to Gateway to filter DNS queries.
+* Create your first Gateway DNS policy.
+* Build an allow or block list for use in firewall policies.
+* Onboard networks to Gateway to filter DNS queries.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
index 3264f26eb9ea844..3a42196c4090ecc 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
@@ -16,16 +16,18 @@ Now that you have created firewall policies to secure your organization, you can
 
 :::note
 
+
 The following module requires [egress policies](/cloudflare-one/traffic-policies/egress-policies/), a feature only available on Enterprise plans. If you are not an Enterprise user, you can skip ahead to [Secure SaaS applications](/learning-paths/secure-internet-traffic/secure-saas-applications/).
 
 For more information on egress policies, contact your account team.
 
+
 :::
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Understand when your organization may need source IP anchoring.
-- Create egress policies to make use of dedicated egress IPs.
-- Follow best practices for deploying egress IPs.
+* Understand when your organization may need source IP anchoring.
+* Create egress policies to make use of dedicated egress IPs.
+* Follow best practices for deploying egress IPs.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
index 486ba1b10c7e8c0..b67afebdb19655c 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
@@ -18,7 +18,7 @@ After securing your organization's DNS queries and network level traffic, you ca
 
 By the end of this module, you will be able to:
 
-- Understand how and when to use TLS inspection to decrypt HTTPS traffic.
-- Configure and enable Data Loss Prevention to protect your organization's sensitive data.
-- Protect user endpoints with Browser Isolation.
-- Add recommended HTTP security policies.
+* Understand how and when to use TLS inspection to decrypt HTTPS traffic.
+* Configure and enable Data Loss Prevention to protect your organization's sensitive data.
+* Protect user endpoints with Browser Isolation.
+* Add recommended HTTP security policies.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
index 8d4115bd0b7fde1..71711da35cc0387 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
@@ -18,5 +18,5 @@ Learn the core concepts of using Cloudflare Zero Trust functionality to provide
 
 By the end of this module, you will be able to:
 
-- Understand what products and features Cloudflare offers.
-- Describe how Cloudflare implements Internet traffic and SaaS app security.
+* Understand what products and features Cloudflare offers.
+* Describe how Cloudflare implements Internet traffic and SaaS app security.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
index a22224d4e229731..319216b4c04291b 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
@@ -36,12 +36,12 @@ Cloudflare supports filtering HTTP/S traffic sent via a PAC file on a user devic
 
 Cloudflare Browser Isolation runs a headless, Chromium-based browser for your users to accomplish their secure browsing needs. It can be activated via an Access application, a Gateway policy, or by using link-based isolation (reverse proxy). In this model, your users can connect from any device to a proxy website to browse the Internet while applying all your Gateway HTTP policies and inspection requirements.
 
-|                                                                                                 | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
-| ----------------------------------------------------------------------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
-| Supported OS                                                                                    | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
-| Configurable via MDM                                                                            | Yes                                  | Yes            | N/A                                   |
-| Gateway policy types supported                                                                  | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
-| Identity-based policies supported                                                               | Yes                                  | No             | Yes                                   |
+|                                   | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
+| --------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
+| Supported OS                      | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
+| Configurable via MDM              | Yes                                  | Yes            | N/A                                   |
+| Gateway policy types supported    | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
+| Identity-based policies supported | Yes                                  | No             | Yes                                   |
 | [Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Yes                                  | Yes            | Yes                                   |
 
 ## Network on-ramps
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
index 0317f717c9237be..14f947c033c85f7 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
@@ -14,5 +14,5 @@ products:
 
 To make the most of securing your Internet traffic and SaaS apps, make sure that you have the following:
 
-- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
+* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
index e67e85f67da54d6..1dcb52b2c614a63 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
@@ -18,6 +18,6 @@ Now that you have deployed dedicated egress IPs and created egress policies to a
 
 By the end of this module, you will be able to:
 
-- Secure your SaaS applications by integrating them with Cloudflare CASB.
-- Control access to your SSO front door.
-- Layer multiple security methods for protecting SaaS apps.
+* Secure your SaaS applications by integrating them with Cloudflare CASB.
+* Control access to your SSO front door.
+* Layer multiple security methods for protecting SaaS apps.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
index 92db03a4e2e98a1..52d73e8318fb87d 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
@@ -18,10 +18,10 @@ products:
 
 Access for SaaS integrates directly with your SaaS app using standard protocols (such as SAML) to become the primary enforcement point for user access. Access calls your identity provider (IdP) of choice and uses additional security signals about your users and devices to make policy decisions. Benefits of Access for SaaS include:
 
-- A streamlined experience for users on both managed and unmanaged devices.
-- Application of baseline policies requiring specific concepts such as device posture and endpoint control.
-- Distinct access methodology for contractors.
-- Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
+* A streamlined experience for users on both managed and unmanaged devices.
+* Application of baseline policies requiring specific concepts such as device posture and endpoint control.
+* Distinct access methodology for contractors.
+* Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
 
 ### SSO integrations
 
@@ -29,8 +29,10 @@ You can pair Access for SaaS with the [App Launcher](/cloudflare-one/access-cont
 
 :::note[SCIM provisioning limitation]
 
+
 Access for SaaS supports SCIM passthrough in an API-only closed beta. If you require SCIM passthrough, contact your account team.
 
+
 :::
 
 ## Configure your SSO provider
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
index 3e738d411947195..4028b6ad5e95765 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
@@ -22,6 +22,6 @@ This guide will provide you with a baseline of recommended policies to build and
 
 By the end of this module, you will be able to:
 
-- Understand the order Gateway enforces policies for filtering traffic.
-- Create reusable lists for Gateway policies.
-- Subscribe to indicator feeds for advanced threat intelligence.
+* Understand the order Gateway enforces policies for filtering traffic.
+* Create reusable lists for Gateway policies.
+* Subscribe to indicator feeds for advanced threat intelligence.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
index 288ad4bd4f9c714..d37b3443e21db00 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When building DNS, network, or HTTP policies to block malicious activity for your organization, you can use external indicator feeds supplied by Cloudflare and other third-party providers.
 
@@ -20,4 +20,4 @@ When building DNS, network, or HTTP policies to block malicious activity for you
 
 <Render file="indicator-feeds-overview" product="security-center" />
 
-To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
+To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
index 075efbb8570f006..4613217ef45c558 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Gateway follows a specific order of enforcement as traffic travels through the Cloudflare global network to the Internet:
 
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
index 779c314e0307099..094d430d9789447 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
@@ -16,4 +16,4 @@ By the end of this module, you will be able to:
 
 - Explain how Cloudflare works.
 - Describe what Email security is.
-- Understand how Cloudflare prevents email-based phishing attacks.
+- Understand how Cloudflare prevents email-based phishing attacks.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
index a81f77056268cbd..325d8d4fbe5e300 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
@@ -16,4 +16,4 @@ As organizations continue to adopt Microsoft 365 and Google Workspace to enhance
 
 Analysts agree that consolidating capabilities to minimize overlapping functionality is helping organizations reduce cost and complexity. However, they also advise organizations to carefully assess native features to ensure they satisfy all use cases. As Microsoft and Google continue to build out its essential email security features, the growing overlap with SEGs has given organizations an opportunity to streamline security operations by leveraging capabilities already included in their E3 or E5 license.
 
-This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
+This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
index 6810419da647886..606e29d7f67ce79 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="what-is-cloudflare" product="fundamentals" />
+<Render file="what-is-cloudflare" product="fundamentals" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
index e751db0ccb39b91..972a75f3e69fb82 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
@@ -10,4 +10,4 @@ products:
 
 Despite email's importance as a communication method, security and privacy were not built into the [The Simple Mail Transfer Protocol (SMTP) protocol](https://www.cloudflare.com/learning/email-security/what-is-smtp/). As a result, email is a major attack vector.
 
-Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
+Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
index 2476b73b8cb70b2..1134bd825289830 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
@@ -12,4 +12,4 @@ products:
 
 Phishing attackers disguise themselves as a reputable source. With an enticing or seemingly urgent request, an attacker lures the victim into providing information, just as a person uses bait while fishing.
 
-Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
+Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
index 09e0b06afb41ca9..a017783809f59cb 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
@@ -49,4 +49,4 @@ In addition, Email security allows you to:
 
 - [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry).
 - [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry).
-- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
+- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
index 8df6912430c831b..665a142ede96132 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
@@ -21,6 +21,7 @@ To enable audit logs:
 2. Select your storage destination.
 3. Select the three dots > **Edit**.
 4. Under **Configure logpush job**:
+
    - **Job name**: Enter the job name, if it is not already prepopulated.
    - **If logs match** > Select **Filtered logs**:
      - **Field**: Choose `ResourceType`.
@@ -29,4 +30,4 @@ To enable audit logs:
 
 5. Select **Submit**.
 
-You can now view logs via the Cloudflare dashboard.
+You can now view logs via the Cloudflare dashboard.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
index fbbb6474283ca81..0378058f8d87ec6 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
@@ -30,4 +30,4 @@ To add a user to the impersonation registry:
      - **Add users or groups**: Choose the users or groups you want to register.
 6. Select **Save**.
 
-For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
+For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
index 2e7a4d8bfb7cbe7..461cbd6dbd19774 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
@@ -10,4 +10,4 @@ products:
 
 With Email security, there is limited manual configuration and tuning. The Active Directory sync, allow policies, and additional detections are important to consider when you set up Email security.
 
-In this module, you will configure your email environment.
+In this module, you will configure your email environment.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
index ba4ad5c0c65ba4a..3cc5f8cd3fe2d8c 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
@@ -33,4 +33,4 @@ To set up PhishNet for Google Workspace:
 1. Log in to the Google Workspace Marketplace using an administrator account.
 2. Select **Admin install** to install Cloudflare PhishNet.
 
-Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
+Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
index 6efc9e48a5b5f2c..34c5572c1d9bd7f 100644
--- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
@@ -16,4 +16,4 @@ Ensure you have completed the previous modules before enabling auto-moves.
 
 Auto-move events are events where emails are automatically moved to different inboxes based on the disposition assigned to them by Email security.
 
-When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
+When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
index 20822f04cf3be59..a5209b5455fedb9 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
@@ -20,8 +20,8 @@ If you are a Google Workspace user, you can enable Email security via [BCC setup
 
 ![Google Workspace BCC deployment diagram](~/assets/email-security/Gmail_Deployment_BCC.png)
 
-With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection.
+With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection. 
 
 ![Microsoft 365 and Google Workspace MX/Inline](~/assets/email-security/Email_security_Deployment_Inline.png)
 
-Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
+Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
index ddf2e2a40c90def..16e8a6a9cc6b7f5 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
@@ -8,4 +8,4 @@ products:
   - email-security
 ---
 
-To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account.
+To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account. 
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
index 891d3080a754f62..a83c5051a08616c 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
@@ -16,4 +16,4 @@ The API deployment with Email security offers:
 - Agentless deployment for Microsoft 365.
 - Office 365 directory integration to retrieve user and group information and prevent user impersonation.
 
-![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
+![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
index 3743a5c02f2a30e..28bf9247f9c6975 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
@@ -11,4 +11,4 @@ products:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**.
-4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
+4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
index 1c65ac9d9434a5c..447dea2119c80ba 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
@@ -12,7 +12,7 @@ products:
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**.
 4. Enable **Microsoft Integration**:
-   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration.
+   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. 
    2. **Name integration**: Add your integration name, then select **Continue**.
    3. **Authorize integration**:
       - Select **Authorize**. Selecting **Authorize** will take you to the Microsoft Sign in page where you will have to enter your email address.
@@ -20,4 +20,4 @@ products:
       - After selecting **Next**, the system will show a dialog box with a list of requested permissions. Select **Accept** to authorize Email security. Upon authorization, you will be redirected to a page where you can review details and enroll integration.
    4. **Review details**: Review your integration details, then:
       - Select **Complete Email security set up** where you will be able to connect your domains and configure auto-moves.
-      - Select **Continue to Email security**.
+      - Select **Continue to Email security**.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
index 40565ed07e17558..e5a57972d2a82f0 100644
--- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
@@ -17,4 +17,4 @@ There are two different ways to [submit a phish](/cloudflare-one/email-security/
   - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you.
 - Admin submission:
   - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address.
-  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
+  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
index 47bf090845f40be..3432b43cd002658 100644
--- a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
@@ -20,15 +20,15 @@ To learn more about our service offerings, refer to [Customer Success offerings]
 
 For the security and protection of your account, be sure to register all account users.
 
-1. In the Cloudflare dashboard, go to the **Manage Account** > **Members** page.
+1. In the Cloudflare dashboard, go to the  **Manage Account** > **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Select more than one Super Administrator to ensure appropriate access when needed.
 
 :::note
 
-Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users.
+Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users. 
 
 :::
 
@@ -50,7 +50,7 @@ We strongly advise against credential-sharing which can jeopardize the trust and
   Certificates managed by Cloudflare are auto-renewed.
   :::
 - Review your Operational and Disaster recovery preparedness
-  - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
-  - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
+    - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
+    - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
 - Review and update your current users' access
-- Check your domain registry validity
+- Check your domain registry validity
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
index d58062e1f6e2e72..11fe9044b199b1c 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
@@ -14,14 +14,16 @@ products:
 
 Use the [Workers Analytics Engine](/analytics/analytics-engine/) to send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL.
 
+
 ## Account and zone analytics
 
 Use [Account and zone analytics](/analytics/account-and-zone-analytics/) to provide details about the requests and traffic related to your Cloudflare accounts and zones.
 
+
 ## Cloudflare Network Analytics
 
 Use [Cloudflare Network Analytics](/analytics/network-analytics/) to provide near real-time visibility into network and transport-layer traffic patterns and DDoS attacks.
 
 ## GraphQL Analytics API
 
-Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
+Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
index 7be8e912c96ed9a..d594e17850fe651 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
@@ -16,21 +16,26 @@ import { DashButton } from "~/components";
 
 By default, Cloudflare [caches static content](/cache/concepts/default-cache-behavior/) such as images, CSS, and JavaScript. However, you can extend Cloudflare caching to work with HTML by creating custom [Cache Rules](/cache/how-to/cache-rules/).
 
+
 ### Cache more requests
 
-1. In the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page.
+1. In  the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page. 
 
-   <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
 3. For When incoming requests match, enter either your entire website or a specific path on your application, based on the Hostname or URI Path. Refer to the [available fields](/cache/how-to/cache-rules/settings/#fields).
 4. For Cache eligibility, define how these requests should be cached and for how long. Refer to the available [cache eligibility settings](/cache/how-to/cache-rules/settings/#eligible-for-cache-settings).
 5. You can then monitor the effectiveness of your cache settings using [Cache Analytics](/cache/performance-review/cache-analytics/) and update your configuration according to our [Cache performance guide](/cache/performance-review/cache-performance/).
 
+
 ### Advanced cache optimizations
 
-- [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
-- [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
+
+
+* [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
+* [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
+
 
 ## Tiered Cache
 
@@ -40,6 +45,7 @@ It works by dividing Cloudflare's data centers into a hierarchy of lower-tiers a
 
 Refer to [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) to get started.
 
+
 ### Cache Reserve
 
 [Cache Reserve](/cache/advanced-configuration/cache-reserve/) is a large, persistent data store implemented on top of [R2](/r2/).
@@ -48,32 +54,38 @@ With a single click in the dashboard, your cacheable content will be written to
 
 This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
 
+
 ## Cloudflare Waiting Room
 
 [Cloudflare Waiting Room](/waiting-room/) allows you to route excess users of your website to a customized waiting room, helping preserve customer experience and protect origin servers from being overwhelmed with requests.
 
+
 ## Use Cloudflare IP addresses
 
 Take action to prevent attacks to your application during peak season by configuring your firewall to only accept traffic from Cloudflare IP addresses. By only allowing [Cloudflare IPs](https://www.cloudflare.com/ips), you can prevent attackers from bypassing Cloudflare and sending requests directly to your origin.
 
 Refer to [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) for more information.
 
+
 ## Monitor traffic
 
 You can use the Cloudflare dashboard to closely monitor the traffic on your domain and fine-tune your cache and security settings accordingly.
 
+
 ### Zone and Account analytics
 
 [Cloudflare zone analytics](/analytics/account-and-zone-analytics/zone-analytics/) gives you access to a wide range of metrics, collected at the website or domain level.
 
 [Cloudflare account analytics](/analytics/account-and-zone-analytics/account-analytics/) lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
+
 ### Security Analytics and Security Events
 
 [Security Analytics](/waf/analytics/security-analytics/) displays information about all incoming HTTP requests for your domain, including requests not handled by Cloudflare security products.
 
 You can also use the [Security Events](/waf/analytics/security-events/) to review mitigated requests and tailor your security configurations.
 
+
 ### Cache Analytics
 
-You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
+You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
index 2655eccdda8256f..63efb8a1e0f3aef 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
index 6434accda802398..46f719837ac8da1 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
@@ -14,14 +14,17 @@ products:
 
 Use [Logpush](/logs/logpush/) to push your request or event logs to your cloud service provider using Logpush, which can be configured via the Cloudflare dashboard or API.
 
+
 ## Instant Logs
 
 Use [Instant Logs](/logs/instant-logs/) to view HTTP request logs instantly in the Cloudflare dashboard or the CLI.
 
+
 ## Logs Engine
 
-Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.
+Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.  
+
 
 ## Log Explorer
 
-Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
+Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API. 
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
index 075b1e688bd6801..07a1c32748a4a4b 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
@@ -10,6 +10,7 @@ products:
   - ddos-protection
 ---
 
+
 [User Agent (UA) Blocking](/waf/tools/user-agent-blocking/) rules match against specific User-Agent request headers sent by the browser or application accessing your site. UA rules are applied against the entire domain, and after a rule is triggered, you can decide which action to take against the visitor.
 
 Actions:
diff --git a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
index c0d4fe2c9a50ebe..8a5b929f561880a 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Review the list below for guidance on securing your account.
 
-<DirectoryListing folder="fundamentals/account/account-security" />
+<DirectoryListing folder="fundamentals/account/account-security" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
index 8508360fa7d7ac7..9fb487a7190ccfd 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
@@ -14,10 +14,13 @@ products:
 
 IP Access Rules can be applied based on:
 
-- IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
-- IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
-- ASN
-- Country or the Tor network
+
+
+* IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
+* IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
+* ASN
+* Country or the Tor network
+
 
 :::note
 
@@ -31,3 +34,4 @@ Actions:
 - Non-Interactive Challenge: Visitors will be shown a non-interactive challenge before allowed access.
 - Interactive Challenge: Visitors will be shown an interactive challenge before allowed access.
 - Allowlist: Ensures that an IP address will never be blocked from accessing your site. This supersedes any Cloudflare security profile.
+
diff --git a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
index 2436739e7c61285..1c28bd66975b7dd 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
@@ -1,7 +1,7 @@
 ---
 title: What to do when under attack
 pcx_content_type: overview
-sidebar:
+sidebar: 
   order: 9
 description: Respond to active DDoS attacks.
 products:
@@ -16,12 +16,14 @@ If you are under attack and have this feature enabled during the attack, visitor
 
 Refer to [I'm Under Attack Mode](https://developers.cloudflare.com/fundamentals/reference/under-attack-mode/) for more information.
 
+
 ## Change Access Control List (ACL)
 
 An ACL refers to rules that are applied to port numbers or IP addresses that are available on a host permitting use of the service. When you only allow Cloudflare IPs, you eliminate threats attempting to attack your origin IP range.
 
 Refer to [Cloudflare IP Ranges](https://www.cloudflare.com/ips) for more information.
 
+
 ## Change Origin IPs and update Cloudflare DNS records
 
 If your origin is still being attacked, consider moving your Origin IPs and updating your Cloudflare DNS records.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/index.mdx b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
index 4e47eb5f69bf264..cd4191d21fbf2c9 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/support/index.mdx b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
index 289654ff24ecd81..38e3bfb1f22fb97 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
index 0ce3a91e3055cfd..1ae293e1c4a56e6 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
@@ -10,14 +10,15 @@ products:
   - ddos-protection
 ---
 
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
-| Support type                                      | Resource                                                                                     |
-| ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| Self-serve questions                              | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals          |
-| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team                                                     |
-| Non-critical production issues (reactive)         | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
-| Critical issues such as attacks (reactive)        | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)       |
+
+| Support type | Resource |
+| ------------ | -------- |
+| Self-serve questions | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals |
+| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team |
+| Non-critical production issues (reactive) | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
+| Critical issues such as attacks (reactive) | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)| 
 
 :::note
 For security reasons, Cloudflare Support only assists individuals whose email addresses are validated against the list of registered account contacts. Review and update all contacts accordingly in your Cloudflare Dashboard. For more information, refer to [Manage members](/fundamentals/manage-members/).
diff --git a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
index 898e3bb0f7ac8ed..2865a6b3e04b8af 100644
--- a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
@@ -24,13 +24,13 @@ If your application is built on Cloudflare, then Cloudflare would act as the ori
 
 An example tech stack for an application built on Cloudflare would look like:
 
-- [Domain Registrar](/registrar/) to buy a new your domain.
-- [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
-- [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
-- [Storage resources](/workers/platform/storage-options/) to persist different types of data.
-- [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
-- [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
-- [AI](/use-cases/ai/) to run machine learning models.
+* [Domain Registrar](/registrar/) to buy a new your domain.
+* [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
+* [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
+* [Storage resources](/workers/platform/storage-options/) to persist different types of data.
+* [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
+* [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
+* [AI](/use-cases/ai/) to run machine learning models.
 
 And more depending on your use case.
 
@@ -42,11 +42,11 @@ When you add your application to Cloudflare, Cloudflare's global network of serv
 
 After you add your application to [Cloudflare](/fundamentals/concepts/how-cloudflare-works/), you can:
 
-- Use Workers to augment the application by deploying code.
-- Add storage resources available on the Developer Platform.
-- Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
-- Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
-- Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
+* Use Workers to augment the application by deploying code.
+* Add storage resources available on the Developer Platform.
+* Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
+* Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
+* Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
 
 And more depending on your use case.
 
@@ -54,8 +54,8 @@ And more depending on your use case.
 
 By reading this page, you have:
 
-- Learned the scale of Cloudflare's global network.
-- Explored the product offering to know what Cloudflare can offer for users like you.
-- Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
+* Learned the scale of Cloudflare's global network.
+* Explored the product offering to know what Cloudflare can offer for users like you.
+* Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
 
 In the next section, you will be introduced to the fundamentals of serverless computing, the concept behind Cloudflare Workers.
diff --git a/src/content/docs/learning-paths/workers/concepts/index.mdx b/src/content/docs/learning-paths/workers/concepts/index.mdx
index 9837915441175e0..e293a2f1d9d87d7 100644
--- a/src/content/docs/learning-paths/workers/concepts/index.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/index.mdx
@@ -16,6 +16,6 @@ Learn the concepts behind what makes Cloudflare Workers reliable, scalable and f
 
 By the end of this module, you will learn:
 
-- What Cloudflare is.
-- The difference between serverless computing and cloud computing paradigms.
-- How Workers works.
+* What Cloudflare is.
+* The difference between serverless computing and cloud computing paradigms.
+* How Workers works.
diff --git a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
index c9f1788b07d3213..1fd5f921d05c1ed 100644
--- a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
@@ -40,8 +40,8 @@ Developers and organizations using serverless computing are billed on a usage mo
 
 By reading this page, you have:
 
-- Been introduced to the serverless computing concept that is behind Cloudflare Workers.
-- Reviewed the differences between legacy on-premise and cloud computing infrastructure.
-- Analyzed the key differences between the cloud computing and serverless computing paradigms.
+* Been introduced to the serverless computing concept that is behind Cloudflare Workers.
+* Reviewed the differences between legacy on-premise and cloud computing infrastructure.
+* Analyzed the key differences between the cloud computing and serverless computing paradigms.
 
 In the next section, you will learn about what makes Workers, a serverless computing platform that is part of the larger Cloudflare Developer Platform, unique in its architecture from other serverless computing providers.
diff --git a/src/content/docs/learning-paths/workers/devplat/index.mdx b/src/content/docs/learning-paths/workers/devplat/index.mdx
index 365fd4fa0f8d551..f792c7ba4cbfda3 100644
--- a/src/content/docs/learning-paths/workers/devplat/index.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/index.mdx
@@ -16,5 +16,5 @@ The Cloudflare Developer Platform allows you to build full-stack applications wi
 
 By the end of this module, you will learn:
 
-- Cloudflare Developer Platform's product offering.
-- What storage options are available to your Worker.
+* Cloudflare Developer Platform's product offering.
+* What storage options are available to your Worker.
diff --git a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
index 5a516cca6e30fc3..20e6536f1ef0349 100644
--- a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { Render, YouTube } from "~/components";
+import { Render, YouTube } from "~/components"
 
 The [Cloudflare Developer Platform](https://www.cloudflare.com/developer-platform/products/) offers various services to empower developers to build full-stack applications, including: [compute](https://www.cloudflare.com/developer-platform/products/#compute), [storage](https://www.cloudflare.com/developer-platform/products/#storage), [web development, image optimization, video streaming](https://www.cloudflare.com/developer-platform/products/#webdev) and [AI](https://ai.cloudflare.com/).
 
diff --git a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
index 491c0bb0dc6773c..4783f290410f89f 100644
--- a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
@@ -18,8 +18,8 @@ You can build and develop your Worker on the Cloudflare dashboard, without needi
 
 The Cloudflare Developer Platform ecosystem has two command-line interfaces (CLI):
 
-- C3: To create new projects.
-- Wrangler: To build and deploy your projects.
+* C3: To create new projects.
+* Wrangler: To build and deploy your projects.
 
 ## C3
 
@@ -45,7 +45,7 @@ Cloudflare recommends choosing and using one [source of truth](/workers/wrangler
 
 By reading this page, you have learned:
 
-- How to use C3 to create new Workers and Pages projects.
-- How to use Wrangler to develop, configure, and delete your projects.
+* How to use C3 to create new Workers and Pages projects.
+* How to use Wrangler to develop, configure, and delete your projects.
 
 In the next section, you will learn more about the Cloudflare dashboard before moving on to deploy your first Worker.
diff --git a/src/content/docs/learning-paths/workers/get-started/first-application.mdx b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
index 5797be4e53286d6..422ae8875a66d14 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-application.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
@@ -9,7 +9,6 @@ description: Build an AI application with Hono.
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 ## Build an AI application with Hono and Workers
@@ -18,21 +17,21 @@ If you have already created your first Worker and want to learn what more you ca
 
 In this course, you will:
 
-- Deploy your first Worker.
-- Develop your application locally.
-- Add the Hono framework to your project.
-- Integrate Workers AI into your project.
+* Deploy your first Worker.
+* Develop your application locally.
+* Add the Hono framework to your project.
+* Integrate Workers AI into your project.
 
 <div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
+    <iframe
+        src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
+        style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+        allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+        allowfullscreen="true">
+    </iframe>
 </div>
 
-<br />
+<br/>
 
 Find [the video on YouTube](https://youtu.be/H7Qe96fqg1M?si=GVkdGLrmb1faiHma) and explore other Cloudflare Workers tutorials.
 
diff --git a/src/content/docs/learning-paths/workers/get-started/index.mdx b/src/content/docs/learning-paths/workers/get-started/index.mdx
index a25e920d7e95452..39b04e54f6794eb 100644
--- a/src/content/docs/learning-paths/workers/get-started/index.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/index.mdx
@@ -14,6 +14,6 @@ Deploy your first Worker to the Cloudflare global network by
 
 By the end of this module, you will learn:
 
-- The difference between C3 (`create-cloudflare` CLI) and Wrangler.
-- How to use the Cloudflare dashboard to manage your Workers.
-- How to create and deploy your first Worker.
+* The difference between C3 (`create-cloudflare` CLI) and Wrangler.
+* How to use the Cloudflare dashboard to manage your Workers.
+* How to create and deploy your first Worker.
diff --git a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
index a01215316a0f040..cc182b7d7c81178 100644
--- a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
+++ b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
@@ -7,6 +7,7 @@ products:
 head:
   - tag: title
     content: Load balance additional DNS records
+
 ---
 
 In addition to load balancing between DNS records used for IP resolution — `A`, `AAAA`, and `CNAME` records — Enterprise customers can also load balance between **MX** and **SRV** records.
@@ -16,7 +17,7 @@ In addition to load balancing between DNS records used for IP resolution — `A`
 To load balance between multiple mail servers:
 
 1. Make sure you have the [required DNS records](/dns/manage-dns-records/how-to/email-records/#send-and-receive-email) for your mail servers.
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _SMTP_.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *SMTP*.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your mail servers and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. Since it will forward SMTP traffic, the load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
 
@@ -25,6 +26,6 @@ To load balance between multiple mail servers:
 To load balance between different **SRV** records, which contain significantly more information than many other DNS records:
 
 1. [Create your SRV records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records).
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _UDP-ICMP_ or _TCP_.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *UDP-ICMP* or *TCP*.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your various SRV records and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. This load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
diff --git a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
index 826228781b9546b..26703586383732d 100644
--- a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
+++ b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Route traffic through a Cloudflare Tunnel
+
 ---
 
 Cloudflare Tunnel (formerly Argo Tunnel) establishes a secure outbound connection which runs in your infrastructure to connect the applications and machines to Cloudflare.
diff --git a/src/content/docs/load-balancing/additional-options/index.mdx b/src/content/docs/load-balancing/additional-options/index.mdx
index 67bfe4b67c3ffd3..fa8021c02caae66 100644
--- a/src/content/docs/load-balancing/additional-options/index.mdx
+++ b/src/content/docs/load-balancing/additional-options/index.mdx
@@ -6,21 +6,22 @@ products:
 title: Additional configuration
 sidebar:
   order: 49
+
 ---
 
 Beyond [creating a simple load balancer](/load-balancing/load-balancers/create-load-balancer/), you may want to further customize how your load balancer routes traffic or integrate your load balancer with other Cloudflare products.
 
 ## Customize load balancer behavior
 
-- Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
-- Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
-- Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
+* Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
+* Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
+* Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
 
 ## Integrate with other Cloudflare products
 
-- Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
-- Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
+* Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
+* Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
 
 ## Integrate with 3rd parties
 
-- Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
+* Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
index e0591ff2cfa42ea..ce90921b4f41919 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Balancing with the China Network
 sidebar:
   order: 15
+
 ---
 
 ## Prerequisites
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
index ef52ac1aafb7236..3fa85bff4993517 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
@@ -9,15 +9,16 @@ sidebar:
 head:
   - tag: title
     content: Load Balancing expressions
+
 ---
 
 [Load Balancing rules](/load-balancing/additional-options/load-balancing-rules/) use two kinds of expressions:
 
-- [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (_equals_ or _less than_, for example).
+* [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (*equals* or *less than*, for example).
 
-- [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (_and_, _or_, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
+* [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (*and*, *or*, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
 
----
+***
 
 ## Simple expressions
 
@@ -43,11 +44,11 @@ In general, simple expressions use this pattern:
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
----
+***
 
 ## Compound expressions
 
-A compound expression uses a **logical operator** (_and_, _or_, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
+A compound expression uses a **logical operator** (*and*, *or*, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
 
 The example expression below returns true when both the HTTP request URI path contains `/content` and the query string contains `webserver`:
 
@@ -66,7 +67,7 @@ A compound expression can be an operand of a logical operator. This allows multi
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
----
+***
 
 ## Working with expressions
 
diff --git a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
index ec4cd87db9d1d86..135607380a8e453 100644
--- a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
+++ b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
@@ -6,16 +6,19 @@ products:
 title: Override HTTP Host headers
 sidebar:
   order: 16
+
 ---
 
 When your application needs specialized routing (`CNAME` setup or custom hosts like Heroku), you can customize the `Host` header used in health monitors on a per-endpoint or per-monitor level.
 
 :::caution[Important]
 
+
 If you set a header override on an individual endpoint, it will take precedence over a header override set on a monitor.
 
 Also, if you configure an [Origin Rule](/rules/origin-rules/) that overrides the hostname and set up a header override in your Load Balancer configuration, the Load Balancer configuration will take precedence over the Origin Rule hostname override.
 
+
 :::
 
 ## Per endpoint Host header override
@@ -24,13 +27,13 @@ To balance traffic across multiple hosts, add `Host` headers to individual endpo
 
 For example, you might have a pool with endpoints hosted in multiple AppEngine projects or Amazon S3 buckets. You also might want to set up specific failover endpoints within a pool.
 
-Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic _without_ a `Host` header override.
+Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic *without* a `Host` header override.
 
 If you need an endpoint `Host` header override, add it when [creating](/load-balancing/pools/create-pool/) or editing a pool. For security reasons, this header must meet one of the following criteria:
 
-- Is a subdomain of a zone associated with this account
-- Matches the endpoint address
-- Publicly resolves to the endpoint address
+* Is a subdomain of a zone associated with this account
+* Matches the endpoint address
+* Publicly resolves to the endpoint address
 
 ## Host header prioritization
 
@@ -38,16 +41,19 @@ If you set a header override on an individual endpoint, it will take precedence
 
 For example, you might have a load balancer for `www.example.com` with the following setup:
 
-- Pools:
-  - Pool 1:
-    - Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
-    - Endpoint 2
+* Pools:
+
+  * Pool 1:
+
+    * Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
+    * Endpoint 2
+
+  * Pool 2:
 
-  - Pool 2:
-    - Endpoint 3
-    - Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
+    * Endpoint 3
+    * Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
 
-- Monitor (`Host` header set to `www.example.com`)
+* Monitor (`Host` header set to `www.example.com`)
 
 In this scenario, health monitor requests for **Endpoint 1** would use `lb-app-a.example.com`, health monitor requests for **Endpoint 4** would use `lb-app-b.example.com`, and all other health monitor requests would default to `www.example.com`. For more information on updating your custom host configuration to be compatible with Cloudflare, see [Configure Cloudflare and Heroku over HTTPS](/support/third-party-software/others/configure-cloudflare-and-heroku-over-https/).
 
diff --git a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
index f9d25700c2ef3e6..800fefee9fab77d 100644
--- a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
+++ b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
@@ -6,6 +6,7 @@ products:
 title: Integrate with PagerDuty
 sidebar:
   order: 41
+
 ---
 
 To integrate Cloudflare health monitor notifications with PagerDuty, follow the steps outlined in PagerDuty’s [Email Integration Guide](https://www.pagerduty.com/docs/guides/email-integration-guide/). If you do not have a PagerDuty account, you will first need to set that up.
diff --git a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
index 934c8b9eaad2618..44d8e5917088c19 100644
--- a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
+++ b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
@@ -18,8 +18,10 @@ To direct traffic away from your endpoint immediately, [adjust settings on the p
 
 :::note
 
+
 If you want to divert traffic from an endpoint to prevent it from becoming unhealthy, use [Load Shedding](/load-balancing/additional-options/load-shedding/) instead.
 
+
 :::
 
 ## Before you begin
@@ -32,8 +34,10 @@ If a pool falls below its **Health Threshold**, it will be considered **Unhealth
 
 :::note
 
+
 Endpoint drain is only available for [proxied load balancers (orange-clouded)](/load-balancing/understand-basics/proxy-modes/).
 
+
 :::
 
 With [session-based load balancing](/load-balancing/understand-basics/session-affinity/), it is important to direct all requests from a particular end user to a specific endpoint. Otherwise, information about the user session — such as items in their shopping cart — may be lost and lead to negative business outcomes.
@@ -59,10 +63,10 @@ To remove an endpoint from rotation while still preserving session continuity, s
 To direct traffic away from an endpoint immediately:
 
 1. Do one of the following actions:
-   - On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
-   - On the pool, disable the endpoint.
-   - On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
+   * On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
+   * On the pool, disable the endpoint.
+   * On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
 2. Monitor [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) to make sure no requests are reaching the pool.
-   - If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
+   * If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
 3. Perform your required maintenance or upgrades.
 4. Undo the changes you made in **Step 1**.
diff --git a/src/content/docs/load-balancing/api-reference.mdx b/src/content/docs/load-balancing/api-reference.mdx
index 5fcef7600b948c2..beaae8039b92f86 100644
--- a/src/content/docs/load-balancing/api-reference.mdx
+++ b/src/content/docs/load-balancing/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/load_balancers/methods/get/
 sidebar:
   order: 152
+
 ---
diff --git a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
index 290ae83ee3bfbe9..2d257351a66f0cf 100644
--- a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
+++ b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
@@ -9,9 +9,10 @@ head:
   - tag: title
     content: Enable Load Balancing
 description: Learn how to enable load balancing.
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Load balancing is an add-on for your account, meaning your account needs a [billing profile](/billing/get-started/create-billing-profile/).
 
diff --git a/src/content/docs/load-balancing/get-started/index.mdx b/src/content/docs/load-balancing/get-started/index.mdx
index 42931ed740f8d8a..718f24899007689 100644
--- a/src/content/docs/load-balancing/get-started/index.mdx
+++ b/src/content/docs/load-balancing/get-started/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Get started
 sidebar:
   order: 1
+
 ---
 
 Get started with load balancing in one of two ways:
 
-- [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
-- [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
+* [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
+* [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
diff --git a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
index 9e97aeac3cc0923..47be390136f8260 100644
--- a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
+++ b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
@@ -6,6 +6,7 @@ products:
 title: Common configurations
 sidebar:
   order: 6
+
 ---
 
 Consider the following sections to understand how to achieve some commonly used load balancer configurations.
@@ -38,11 +39,13 @@ This setup speeds up overall requests, but is more vulnerable to planned or unpl
 
 To set up a load balancer with **active-active failover**, either:
 
-- Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
-- Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
+* Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
+* Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
 
 :::note
 
+
 For more background reading on server failover and common configurations, refer to [our Learning Center](https://www.cloudflare.com/learning/performance/what-is-server-failover/).
 
+
 :::
diff --git a/src/content/docs/load-balancing/monitors/index.mdx b/src/content/docs/load-balancing/monitors/index.mdx
index 1e9332fef2a2c18..4f3257567e10daf 100644
--- a/src/content/docs/load-balancing/monitors/index.mdx
+++ b/src/content/docs/load-balancing/monitors/index.mdx
@@ -86,6 +86,6 @@ The following table summarizes the different types of monitors available in Clou
 | ------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | HTTP/HTTPS   | Public and private | Used for HTTP and HTTPS endpoints with specific protocol attributes.                                                                                                                       | The probe is configured with settings and success criteria such as Method, Simulate Zone, Follow Redirects, Request Headers, and Response Body. The probe then evaluates the configured success criteria using the HTTP protocol. Throughout the configured timeout period, the TCP connection is kept active using [keep-alives](/fundamentals/reference/tcp-connections/#tcp-connections-and-keep-alives), even if no response is received. | Success is based on meeting the configured HTTP success criteria. No response within the configured timeout and retries is considered unhealthy.   |
 | TCP          | Public and private | Checks TCP connectivity by attempting to open a connection to the endpoint.                                                                                                                | The monitor sends a TCP SYN message to the specified port. A successful health check requires receiving a SYN/ACK message to establish the connection. The connection is closed by sending a FIN or RST packet, or by receiving a FIN packet from the endpoint.                                                                                                                                                                               | Failure to establish a TCP connection within the configured timeout and retries is considered unhealthy.                                           |
-| ICMP Ping    | Public and Tunnel  | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
-| UDP-ICMP     | Public and Tunnel  | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
+| ICMP Ping    | Public and Tunnel | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
+| UDP-ICMP     | Public and Tunnel | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
 | SMTP         | Public             | Verifies SMTP availability at the application layer.                                                                                                                                       | The monitor establishes a TCP connection and sends an SMTP HELO command. It expects a reply with code 250. The monitor then sends an SMTP QUIT command, expecting a reply with code 221. At the end of each interval, the TCP connection is closed by sending a TCP FIN packet.                                                                                                                                                               | The endpoint must respond with correct SMTP codes (250 for HELO, 221 for QUIT) within the configured timeout and retries to be considered healthy. |
diff --git a/src/content/docs/load-balancing/monitors/monitor-groups.mdx b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
index c9523c593355ecb..50904c9a7de3215 100644
--- a/src/content/docs/load-balancing/monitors/monitor-groups.mdx
+++ b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
@@ -6,6 +6,7 @@ products:
 title: Monitor Groups
 sidebar:
   order: 48
+
 ---
 
 Group multiple health monitors together to create sophisticated health checks for your applications, ensuring more intelligent and resilient traffic steering.
diff --git a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
index 3d3b8c26fad9827..db0595b89b0b6ef 100644
--- a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
+++ b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
@@ -33,10 +33,8 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to
 1. Go to **Load Balancing** at the account level and select **Create a Load Balancer**.
 2. Select **Private Load Balancer**.
 3. On the next step you can choose to associate this load balancer with either:
-
-- A CGNAT IP from the Cloudflare range or
-- A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
-
+ - A CGNAT IP from the Cloudflare range or
+ - A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
 4. Add a descriptive name to identify your Load Balancer.
 5. Proceed through the setup.
 
diff --git a/src/content/docs/load-balancing/reference-architecture-external-link.mdx b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
index 0183c3d39e2e8f3..09dbce736aec377 100644
--- a/src/content/docs/load-balancing/reference-architecture-external-link.mdx
+++ b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
@@ -7,4 +7,5 @@ title: Reference architecture
 external_link: /reference-architecture/architectures/load-balancing/
 sidebar:
   order: 150
+
 ---
diff --git a/src/content/docs/load-balancing/reference/index.mdx b/src/content/docs/load-balancing/reference/index.mdx
index e6f4d8d2d6c3b20..ec8770d1780404a 100644
--- a/src/content/docs/load-balancing/reference/index.mdx
+++ b/src/content/docs/load-balancing/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 50
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 See the following pages for more information about Cloudflare Load Balancing:
 
diff --git a/src/content/docs/load-balancing/reference/limitations.mdx b/src/content/docs/load-balancing/reference/limitations.mdx
index c46c0f6c8a12462..5bde030458bc22e 100644
--- a/src/content/docs/load-balancing/reference/limitations.mdx
+++ b/src/content/docs/load-balancing/reference/limitations.mdx
@@ -6,12 +6,13 @@ products:
 title: Limitations
 sidebar:
   order: 48
+
 ---
 
-| Name              | Non-Enterprise           | Enterprise               |
-| ----------------- | ------------------------ | ------------------------ |
-| Load balancers    | 20                       | custom                   |
-| Monitor intervals | 15s (min), 3600s (max)   | 10s (min), 3600s (max)   |
-| Monitors          | 1.5x the number of pools | 1.5x the number of pools |
-| Endpoints         | 20                       | custom                   |
-| Pools             | 20                       | custom                   |
+ Name | Non-Enterprise | Enterprise |
+ --- | --- | --- |
+ Load balancers | 20 | custom |
+ Monitor intervals | 15s (min), 3600s (max) | 10s (min), 3600s (max) |
+ Monitors | 1.5x the number of pools | 1.5x the number of pools |
+ Endpoints | 20 | custom |
+ Pools | 20 | custom |
diff --git a/src/content/docs/load-balancing/reference/migration-guides/index.mdx b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
index f1e1ae6e2a682da..aecc03630e37bc8 100644
--- a/src/content/docs/load-balancing/reference/migration-guides/index.mdx
+++ b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
index 9f0e7e87097a25c..ede4a1cdcb502e9 100644
--- a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
@@ -6,6 +6,7 @@ products:
 title: Common error codes
 sidebar:
   order: 51
+
 ---
 
 The Cloudflare Load Balancing API adds global health to each pool and endpoint. It also gives you a view into what our network sees at a wider level. Cloudflare uses a quorum system to determine pool and endpoint health status. The quorum is taken from PoPs responsible for running health monitor requests in a region, and the majority result is used.
@@ -22,7 +23,7 @@ If a health monitor request fails, the breakdown will include the reason.
 
 Common troubleshooting causes and solutions are listed below.
 
----
+***
 
 ## TCP connection failed
 
@@ -34,7 +35,7 @@ Our health monitor requests failed to establish a TCP connection to your endpoin
 
 This typically occurs when there is a network failure between Cloudflare and your endpoint, and/or a firewall refused to allow our connection. Ensure your network and firewall configurations are not interfering with load balancing traffic.
 
----
+***
 
 ## HTTP timeout occurred
 
@@ -46,7 +47,7 @@ The endpoint failed to return an HTTP response within the timeout configured. Th
 
 We recommend increasing the HTTP response timeout to allow the endpoint to respond.
 
----
+***
 
 ## Response code mismatch error
 
@@ -66,7 +67,7 @@ You may also see this issue if you have a monitor configured to use HTTP connect
 
 Either change your Cloudflare monitor configuration to use HTTPS, or set the value of `follow_redirect` to `true` so that we can resolve the correct status code.
 
----
+***
 
 ## Response body mismatch error
 
@@ -74,13 +75,13 @@ Either change your Cloudflare monitor configuration to use HTTPS, or set the val
 
 The response body returns from your endpoint and does not include the (case-insensitive) value of `expected_body` configured in your monitor.
 
-Note that we only read the first 10 KB of the response. If you return a larger response, and the expected_body is not in the first 10 KB, the health monitor request will fail.
+Note that we only read the first 10 KB of the response. If you return a larger response, and the expected\_body is not in the first 10 KB, the health monitor request will fail.
 
 ### Solution
 
-Ensure the expected_body is in the first 10 KB of the response body.
+Ensure the expected\_body is in the first 10 KB of the response body.
 
----
+***
 
 ## TLS untrusted certificate error
 
@@ -92,7 +93,7 @@ The certificate is not trusted by a public Certificate Authority (CA).
 
 If you're using a self-signed certificate, we recommend either using a publicly trusted certificate or setting the `allow_insecure` property on your monitor to `true`.
 
----
+***
 
 ## TLS name mismatch error
 
@@ -104,7 +105,7 @@ Our health monitor (client) was not able to match a name on the server certifica
 
 Use the List Monitors command to confirm that the `header` value set in the Cloudflare monitor is correct and the Update Monitors command to make any necessary changes.
 
----
+***
 
 ## TLS protocol error
 
@@ -116,7 +117,7 @@ This error can occur if you’re using an older version of TLS or your endpoint
 
 Ensure that your endpoint supports TLS 1.0 or greater and is configured for HTTPS.
 
----
+***
 
 ## TLS unrecognized name error
 
@@ -128,7 +129,7 @@ The server did not recognize the name provided by the client. When a host header
 
 Set the host header in your monitor object.
 
----
+***
 
 ## No route to host error
 
@@ -140,7 +141,7 @@ The IP address cannot be reached from our network. Common causes are ISP or host
 
 Make sure IP is accurate, and if it is check if there is an ISP or hosting provider network issue.
 
----
+***
 
 ## Exceeded quota error
 
@@ -154,10 +155,10 @@ If you're using the **Cloudflare API**, you will receive an error message.
 
 ### Solution
 
-- Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
-- Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
+* Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
+* Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
 
----
+***
 
 ## TCP Timeout
 
@@ -169,7 +170,7 @@ Data transmission was not acknowledged and retransmit of data did not succeed.
 
 Confirm whether the SYN-ACK for the handshake takes place at your endpoint and [contact Cloudflare Support](/support/contacting-cloudflare-support/).
 
----
+***
 
 ## TLS Handshake Failure
 
@@ -181,7 +182,7 @@ Indicates that the browser's connection to the web server is not secure.
 
 Change wifi networks, connect to a wired network, or verify the network connection is stable.
 
----
+***
 
 ## Network Unreachable
 
@@ -193,7 +194,7 @@ Cloudflare cannot connect to the endpoint due to network unavailability. This is
 
 Check either the IP entered for the endpoint in Cloudflare's Load Balancer configuration or the IP returned via DNS for the endpoint hostname.
 
----
+***
 
 ## HTTP Invalid Response
 
@@ -205,7 +206,7 @@ Usually caused by an HTTP 502 error or bad gateway.
 
 Ensure the endpoint responds to requests and that no applications have crashed or are under high load.
 
----
+***
 
 ## DNS Unknown Host
 
@@ -217,7 +218,7 @@ The endpoint hostname does not exist.
 
 Confirm the endpoint resolves to an IP address.
 
----
+***
 
 ## Connection Reset by Peer
 
@@ -229,7 +230,7 @@ A network error occurred while the client received data from the endpoint.
 
 Confirm whether the endpoint is experiencing a high amount of traffic or an error.
 
----
+***
 
 ## Monitor Config Error
 
@@ -241,7 +242,7 @@ There was a configuration error in the monitor and no checks are run against the
 
 Review your monitor configuration to ensure it matches an expected request to your endpoint.
 
----
+***
 
 ## DNS Internal
 
@@ -253,7 +254,7 @@ The endpoint's hostname resolves to an internal or orange-clouded IP address. No
 
 Cloudflare does not allow use of an endpoint hostname that is proxied by Cloudflare.
 
----
+***
 
 ## Load Balancing Not Enabled
 
@@ -265,7 +266,7 @@ Load Balancing is not enabled for your account or zone.
 
 For Enterprise customers, reach out to your Cloudflare Account Team. Free, Pro, and Business customers should [Enable Load Balancing](/load-balancing/get-started/enable-load-balancing/).
 
----
+***
 
 ## Validation failed error
 
@@ -277,7 +278,7 @@ You will receive an error if you try to set the host header value while configur
 
 Cloudflare now restricts configured [endpoint host headers](/load-balancing/additional-options/override-http-host-headers/) to fully qualified domain names (FQDNs) that are immediate subdomains of a zone associated with the account. For example, this host header would be the same zone as the load balancer itself, but pools may be used across multiple Load balancers.
 
----
+***
 
 ## Object referenced by other objects
 
@@ -289,7 +290,7 @@ You will receive this error when you attempt to delete a pool that is referenced
 
 Remove the pool from the load balancer's geo steering configuration. If your load balancer no longer uses geo steering, you will need to [re-enable geo steering](/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering/) and then remove the pool.
 
----
+***
 
 ## Other Failure
 
diff --git a/src/content/docs/load-balancing/troubleshooting/index.mdx b/src/content/docs/load-balancing/troubleshooting/index.mdx
index 2a9154394f0dda7..ab1582dd07df552 100644
--- a/src/content/docs/load-balancing/troubleshooting/index.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 151
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more guidance related to common issues with load balancers, refer to the following resources:
 
diff --git a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
index 49722335e1400f4..f9b35fca372872e 100644
--- a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
@@ -4,6 +4,7 @@ description: Answers to common Load Balancing questions.
 products:
   - load-balancing
 title: FAQs
+
 ---
 
 ## Overview
@@ -16,7 +17,7 @@ Are you trying to turn on Load Balancing? [Enable Load
 Balancing](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing).
 :::
 
----
+***
 
 ## Why is my origin receiving so many health monitor requests?
 
@@ -34,7 +35,7 @@ To reduce traffic, reduce the number of selected regions or choose an option bes
 
 If you have a low interval for your health monitor requests, you may increase the traffic sent to your endpoints.
 
----
+***
 
 ## Why is my endpoint or pool considered unhealthy?
 
@@ -42,15 +43,15 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 If you know that your endpoint is healthy but load balancing is reporting it as unhealthy, check the following settings on the [monitor](/load-balancing/monitors):
 
-- Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
-- Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
-- If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
-- If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
-- Try increasing the **Timeout** value.
-- Review the **Host Header** for the health monitor.
-- If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
+* Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
+* Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
+* If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
+* If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
+* Try increasing the **Timeout** value.
+* Review the **Host Header** for the health monitor.
+* If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
 
----
+***
 
 ## Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?
 
@@ -58,7 +59,7 @@ You occasionally might see traffic routed away from a pool if a health monitor r
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
----
+***
 
 ## What happens when a pool or endpoint becomes unhealthy?
 
@@ -76,7 +77,7 @@ To avoid these scenarios:
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
----
+***
 
 ## What is the difference between Load Balancing and Health Checks?
 
@@ -84,7 +85,7 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 [Cloudflare Health Checks](/health-checks/) are identical to monitors within a load balancer, but only meant for probing server health (and not distributing traffic).
 
----
+***
 
 ## Why do I see different numbers of requests in Load Balancing Analytics?
 
@@ -92,16 +93,16 @@ You may see different numbers of requests when reviewing [Load Balancing Analyti
 
 Load balancing **requests** are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds. This built-in caching is often the cause of an discrepancies.
 
----
+***
 
 ## I'm seeing a specific error code for my load balancer or monitor.
 
 For a list of specific error codes and next steps, refer to [Load Balancing Troubleshooting](/load-balancing/troubleshooting).
 
----
+***
 
 ## Related resources
 
-- [Endpoint and pool health](/load-balancing/understand-basics/health-details)
-- [Monitors](/load-balancing/monitors)
-- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
+* [Endpoint and pool health](/load-balancing/understand-basics/health-details)
+* [Monitors](/load-balancing/monitors)
+* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
diff --git a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
index 0d58152b129b64d..5932d2fa80bf195 100644
--- a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
+++ b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
@@ -6,9 +6,10 @@ products:
 title: Adaptive routing
 sidebar:
   order: 18
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Adaptive routing controls features that modify the routing of requests to pools and endpoints in response to dynamic conditions, such as during the interval between active health monitoring requests. <Render file="zero-downtime-failover-retry-on-error" product="fundamentals" />
 
diff --git a/src/content/docs/load-balancing/understand-basics/index.mdx b/src/content/docs/load-balancing/understand-basics/index.mdx
index 792addac1391985..c85c1403d1845cf 100644
--- a/src/content/docs/load-balancing/understand-basics/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts and components involved in Cloudflare Load Balancing.
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
index 923d4f04f8cf0f3..fdba031ab13f323 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
@@ -6,6 +6,7 @@ products:
 title: Traffic steering
 sidebar:
   order: 4
+
 ---
 
 When requests come to your load balancer, it distributes them across your pools and endpoints according to three factors:
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
index 4cdb38526cfe80e..0c4c24f3ea88b14 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Hash steering
+
 ---
 
 **Hash steering** guides Cloudflare to send requests to endpoints based on a combination of [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) and previous requests from that IP address. Ensures requests from the same IP address will hit the same endpoint, but actual traffic distribution may differ from endpoint weights.
@@ -22,3 +23,6 @@ When a request originates from a browser, it lacks an `x-forwarded-for` header,
 ### Workaround
 
 To ensure Hash Steering works correctly when using a Worker in front of a Load Balancer, manually set the `x-forwarded-for` header in the Worker to the client's original IP address. By manually setting `x-forwarded-for` to `CF-Connecting-IP`, Hash Steering will function as expected, ensuring traffic consistency for end users.
+
+
+
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
index 02a10b15022975c..c51194139beb164 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Endpoint-level steering
+
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to endpoints that currently have the lowest number of outstanding requests.
@@ -21,9 +22,9 @@ Least Outstanding Requests steering is best to use if your endpoints are easily
 
 ```json title="Pools"
 {
-	"origin_steering": {
-		"policy": "least_outstanding_requests"
-	}
+  "origin_steering": {
+    "policy": "least_outstanding_requests"
+  }
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
index 537f0a763c9de2a..80045c618e6408a 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Random steering
+
 ---
 
 **Random steering** sends requests to endpoints purely based on [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights). Distributes traffic more accurately, but may cause requests from the same IP to hit different endpoints.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
index f64ceb698d2ba17..666b471d0af1334 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Dynamic steering
+
 ---
 
 **Dynamic steering** uses health monitor data to identify the fastest pool for a given Cloudflare Region or data center.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
index 944941d3224b8ce..4ad16dc07656f19 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
@@ -20,7 +20,6 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components";
 ## EDNS Client Subnet (ECS) support
 
 <GlossaryTooltip term="EDNS Client Subnet (ECS)"> EDNS Client Subnet (ECS) </GlossaryTooltip> support provides customers with more control over location-based steering during
-
 gray-clouded DNS resolutions and can be used for proximity or geo (country) steering.
 
 Customers can configure their load balancer using the `location_strategy` parameter, which includes the properties `prefer_ecs` and `mode`.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
index b6cd01080f74721..a52ce97da3eb882 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Steering policies
+
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to pools that currently have the lowest number of outstanding requests.
@@ -21,7 +22,7 @@ Least Outstanding Requests steering is best to use if your pools are easily over
 
 ```json title="Load Balancers"
 {
-	"steering_policy": "least_outstanding_requests"
+  "steering_policy": "least_outstanding_requests"
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
index b5922711d2d91b3..2b5fbd7114d502e 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Proximity steering
+
 ---
 
 **Proximity steering** routes visitors or internal services to the closest physical data center.
@@ -17,19 +18,21 @@ To use proximity steering on a load balancer, you first need to add GPS coordina
 
 ## When to add proximity steering
 
-- For new pools, add GPS coordinates when you create a pool.
-- For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
+* For new pools, add GPS coordinates when you create a pool.
+* For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
 
 ## How to add proximity steering
 
 To add coordinates when creating or editing a pool:
 
-1. Click the _Configure coordinates for Proximity Steering_ dropdown.
+1. Click the *Configure coordinates for Proximity Steering* dropdown.
 2. Enter the latitude and longitude or drag a marker on the map.
 3. Select **Save**.
 
 :::caution[Warning:]
 
+
 For accurate proximity steering, add GPS coordinates to all pools within the same load balancer.
 
+
 :::
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
index 4cb1a555bf452a2..22d271801178c9b 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Standard traffic steering policies
+
 ---
 
 **Standard steering** policies include **Off - Failover** and **Random**.
diff --git a/src/content/docs/log-explorer/api.mdx b/src/content/docs/log-explorer/api.mdx
index 6bdcc752a5d4156..305c470002dd3d8 100644
--- a/src/content/docs/log-explorer/api.mdx
+++ b/src/content/docs/log-explorer/api.mdx
@@ -8,7 +8,7 @@ products:
   - log-explorer
 ---
 
-Configuration and Log searches are also available via a public API.
+Configuration and Log searches are also available via a public API. 
 
 ## Authentication
 
@@ -18,7 +18,7 @@ For detailed information on permissions required for each Log Explorer feature,
 
 ## Query data
 
-Log Explorer includes a SQL API for submitting queries.
+Log Explorer includes a SQL API for submitting queries. 
 
 For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
 
@@ -77,4 +77,4 @@ This command returns the following request details:
 	"errors": [],
 	"messages": []
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/log-explorer/changelog.mdx b/src/content/docs/log-explorer/changelog.mdx
index 707f755e2c52edd..2f97c532c5ac0e6 100644
--- a/src/content/docs/log-explorer/changelog.mdx
+++ b/src/content/docs/log-explorer/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="log-explorer" />
+<ProductChangelog product="log-explorer" />
\ No newline at end of file
diff --git a/src/content/docs/log-explorer/example-queries.mdx b/src/content/docs/log-explorer/example-queries.mdx
index 265a16759a71279..3d9b6d9cb490e20 100644
--- a/src/content/docs/log-explorer/example-queries.mdx
+++ b/src/content/docs/log-explorer/example-queries.mdx
@@ -131,5 +131,5 @@ FROM http_requests
 WHERE {{ timeFilter }}
 GROUP BY ClientRequestPath
 ORDER BY avg_ttfb DESC
-LIMIT 10
+LIMIT 10 
 ```
diff --git a/src/content/docs/log-explorer/index.mdx b/src/content/docs/log-explorer/index.mdx
index 8d7a69052b79578..89e85b9513fb688 100644
--- a/src/content/docs/log-explorer/index.mdx
+++ b/src/content/docs/log-explorer/index.mdx
@@ -8,16 +8,15 @@ products:
   - log-explorer
 ---
 
-import { Description, Feature, RelatedProduct } from "~/components";
+import { Description, Feature, RelatedProduct } from "~/components"
 
 <Description>
-	Store and explore your Cloudflare logs directly within the Cloudflare
-	dashboard or API.
+Store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
 </Description>
 
 Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third-party tools.
 
-Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include:
+Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include: 
 
 - **Reduced cost and complexity**: Drastically reduce the expense and operational overhead associated with forwarding, storing, and analyzing terabytes of log data in external tools.
 - **Faster detection and triage**: Access Cloudflare-native logs directly, eliminating cumbersome data pipelines and the ingest lags that delay critical security insights.
@@ -28,14 +27,14 @@ Contract customers can choose to store their logs in Log Explorer for up to two
 
 ## Permissions
 
-Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards.
-
-| Feature                     | Required Permission | Description                             |
-| --------------------------- | ------------------- | --------------------------------------- |
-| **Manage datasets**         | `Logs Edit`         | Add, enable, or disable datasets.       |
-| **Log Search**              | `Logs Read`         | Query logs in the dashboard or via API. |
-| **Log Search (save query)** | `Logs Write`        | Save log search queries.                |
-| **Custom dashboards**       | `Analytics Read`    | Create and view custom dashboards.      |
+Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards. 
+ 
+| Feature | Required Permission | Description |
+|----------|--------------------|--------------|
+| **Manage datasets** | `Logs Edit` | Add, enable, or disable datasets. |
+| **Log Search** | `Logs Read` | Query logs in the dashboard or via API. |
+| **Log Search (save query)** | `Logs Write` | Save log search queries. |
+| **Custom dashboards** | `Analytics Read` | Create and view custom dashboards. |
 
 These permissions apply across both the dashboard and the API, and must be granted at either the account or zone level depending on which datasets you need to access.
 
@@ -44,30 +43,27 @@ Authentication with the API can be done via an API token or API key with an emai
 ## Features
 
 <Feature header="Log Search" href="/log-explorer/log-search/">
-	Explore your Cloudflare logs directly within the Cloudflare dashboard or
-	[API](/log-explorer/api/).
+Explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
 </Feature>
 
 <Feature header="Custom dashboards" href="/log-explorer/custom-dashboards/">
-	Design customized views for tracking application security, performance, and
-	usage metrics.
+Design customized views for tracking application security, performance, and usage metrics.
 </Feature>
 
 <Feature header="Manage datasets" href="/log-explorer/manage-datasets/">
-	Manage the data you want to store within Log Explorer.
+Manage the data you want to store within Log Explorer. 
 </Feature>
 
-<Feature header="API" href="/log-explorer/api/">
-	Manage configuration and perform queries via the API.
+<Feature header="API" href= "/log-explorer/api/">
+Manage configuration and perform queries via the API.
 </Feature>
 
 ## Related products
 
 <RelatedProduct header="Logpush" href="/logs/" product="logs">
-	Forward Cloudflare logs to third-party tools for debugging, identifying
-	configuration adjustments, and creating analytics dashboards.
+Forward Cloudflare logs to third-party tools for debugging, identifying configuration adjustments, and creating analytics dashboards.
 </RelatedProduct>
 
 <RelatedProduct header="Analytics" href="/analytics/" product="analytics">
-	Visualize the metadata collected by our products in the Cloudflare dashboard.
-</RelatedProduct>
+Visualize the metadata collected by our products in the Cloudflare dashboard.
+</RelatedProduct>
\ No newline at end of file
diff --git a/src/content/docs/logs/auditlogs-mcp-server.mdx b/src/content/docs/logs/auditlogs-mcp-server.mdx
index 36c461b0633126a..c0a8f2dd81e60e2 100644
--- a/src/content/docs/logs/auditlogs-mcp-server.mdx
+++ b/src/content/docs/logs/auditlogs-mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the Audit Logs MCP server on GitHub.
 products:
   - logs
   - audit-logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/audit-logs.mdx b/src/content/docs/logs/changelog/audit-logs.mdx
index 2e97637e3f86291..146a75efedab424 100644
--- a/src/content/docs/logs/changelog/audit-logs.mdx
+++ b/src/content/docs/logs/changelog/audit-logs.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="audit-logs" />
+<ProductChangelog product="audit-logs" />
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/index.mdx b/src/content/docs/logs/changelog/index.mdx
index 771bbd8160cd93c..337ffa7afa5c1cb 100644
--- a/src/content/docs/logs/changelog/index.mdx
+++ b/src/content/docs/logs/changelog/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: View recent changes to Cloudflare Logs.
 products:
   - logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/logs.mdx b/src/content/docs/logs/changelog/logs.mdx
index 7f30b4e52b1ad87..69133c374ad154f 100644
--- a/src/content/docs/logs/changelog/logs.mdx
+++ b/src/content/docs/logs/changelog/logs.mdx
@@ -13,3 +13,5 @@ import { ProductChangelog } from "~/components";
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
 <ProductChangelog product="logs" />
+
+
diff --git a/src/content/docs/logs/faq/common-calculations.mdx b/src/content/docs/logs/faq/common-calculations.mdx
index 0252af63297f09c..97fe1a4a59bed1f 100644
--- a/src/content/docs/logs/faq/common-calculations.mdx
+++ b/src/content/docs/logs/faq/common-calculations.mdx
@@ -20,3 +20,5 @@ The best way to calculate bytes served by the origin is to use the `CacheRespons
 ### How do I calculate bandwidth usage for my zone?
 
 Bandwidth (or data transfer) can be calculated by adding the `EdgeResponseBytes` field in HTTP request logs. There are some types of requests that are not factored into bandwidth calculations. In order to only include relevant requests in calculations, add the filter `ClientRequestSource = 'eyeball'`.
+
+
diff --git a/src/content/docs/logs/faq/general-faq.mdx b/src/content/docs/logs/faq/general-faq.mdx
index 0be1d8058566c6f..dc0077117908e87 100644
--- a/src/content/docs/logs/faq/general-faq.mdx
+++ b/src/content/docs/logs/faq/general-faq.mdx
@@ -32,6 +32,7 @@ Yes. The time period for which you pull or receive logs is based on our processi
 
 Not at this time. Talk to your Cloudflare account team or [Cloudflare Support](/support/contacting-cloudflare-support/) if you are interested in other formats and we will consider them for the future.
 
+
 ### Is it possible to track cache purge requests in the logs?
 
 Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/audit-logs/).
@@ -40,3 +41,5 @@ Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/au
 
 Requests are logged only after they successfully reach our proxy.
 It means that requests failing during the TCP or TLS handshake between the client and the Cloudflare proxy will not be available in the logs.
+
+
diff --git a/src/content/docs/logs/faq/instant-logs.mdx b/src/content/docs/logs/faq/instant-logs.mdx
index 1ec7a24289b2ae0..b2c23c3ee7e6a1c 100644
--- a/src/content/docs/logs/faq/instant-logs.mdx
+++ b/src/content/docs/logs/faq/instant-logs.mdx
@@ -14,6 +14,7 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
+
 ### I am getting an HTTP 301 when attempting to connect to my WebSocket. What can I do?
 
 Make sure you are using the `wss://` protocol when connecting to your WebSocket.
@@ -33,3 +34,5 @@ Finally, make sure the destination is proxied through Cloudflare (also known as
 ### I am getting an error fetching my data. How can I solve this?
 
 Make sure you have the correct permissions. To use Instant Logs you need Super Administrator, Administrator, Log Share, or Log Share Reader permissions.
+
+
diff --git a/src/content/docs/logs/faq/logpull-api.mdx b/src/content/docs/logs/faq/logpull-api.mdx
index 04a52d4ae5aeb26..28623ba05c80d58 100644
--- a/src/content/docs/logs/faq/logpull-api.mdx
+++ b/src/content/docs/logs/faq/logpull-api.mdx
@@ -12,12 +12,17 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
+
 ### How long are logs retained?
 
 Cloudflare makes logs available for at least three days and up to seven days. If you need your logs for a longer time period, download and store them locally.
 
+
 ### I am asking for logs for the time window of 16:10-16:13. However, the timestamps in the logs show requests that are before this time period. Why does that happen?
 
+
 When you make a call for the time period of 16:10-16:13, you are actually asking for the logs that were received and processed by our system during that time (hence the endpoint name, `logs/received`). The received time is the time the logs are written to disk. There is some delay between the time the request hits the Cloudflare edge and the time it is received and processed. The **request time** is what you see in the log itself: **EdgeStartTimestamp** and **EdgeEndTimestamp** tell you when the edge started and stopped processing the request.
 
 The advantage of basing the responses on the **time received** rather than the request or edge time is not needing to worry about late-arriving logs. As long as you are calling our API for continuous time segments, you will always get all of your logs without making duplicate calls. If we based the response on request time, you could never be sure that all the logs for that request time had been processed.
+
+
diff --git a/src/content/docs/logs/faq/worker-subrequests.mdx b/src/content/docs/logs/faq/worker-subrequests.mdx
index d1652e3ff63fadd..3d51ed73a21100d 100644
--- a/src/content/docs/logs/faq/worker-subrequests.mdx
+++ b/src/content/docs/logs/faq/worker-subrequests.mdx
@@ -19,10 +19,10 @@ Because the initial log entry only covers the request from the client to the Wor
 
 ### What the two log entries represent
 
-| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                                      |
-| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------------------------- |
+| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                    |
+| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------- |
 | Initial request   | `eyeball`                           | End-user request to the Worker         | `OriginResponseStatus` is `0`, `OriginIP` is empty |
-| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                   |
+| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                    |
 
 Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for the full list of possible `ClientRequestSource` values.
 
@@ -30,10 +30,10 @@ Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for t
 
 Each log entry has its own `RayID`. The Worker subrequest also includes `ParentRayID`, which is the `RayID` of the request that triggered it — its immediate parent.
 
-| Field         | Initial request                            | Worker subrequest                        |
-| ------------- | ------------------------------------------ | ---------------------------------------- |
-| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest     |
-| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it |
+| Field         | Initial request                            | Worker subrequest                          |
+| ------------- | ------------------------------------------ | ------------------------------------------ |
+| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest       |
+| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it   |
 
 To correlate the two records:
 
diff --git a/src/content/docs/logs/glossary.mdx b/src/content/docs/logs/glossary.mdx
index 986f0dca8ab17e7..5996605fa39a008 100644
--- a/src/content/docs/logs/glossary.mdx
+++ b/src/content/docs/logs/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - logs
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Logs documentation.
 
diff --git a/src/content/docs/logs/logpull/index.mdx b/src/content/docs/logs/logpull/index.mdx
index 3629ad283b4166f..b22aea276e0eb94 100644
--- a/src/content/docs/logs/logpull/index.mdx
+++ b/src/content/docs/logs/logpull/index.mdx
@@ -8,14 +8,16 @@ products:
   - logs
 ---
 
-import { DirectoryListing, FeatureTable } from "~/components";
+import { DirectoryListing, FeatureTable } from "~/components"
 
 Cloudflare Logpull is a REST API for consuming request logs over HTTP. These logs contain data related to the connecting client, the request path through the Cloudflare network, and the response from the origin web server. This data is useful for enriching existing logs on an origin server. Logpull is available to customers on the Enterprise plan.
 
 :::caution
 
+
 Logpull is considered a legacy feature and we recommend using [Logpush](/logs/logpush/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
 
+
 :::
 
 Review the following content to learn more about Logpull.
diff --git a/src/content/docs/logs/logpull/requesting-logs.mdx b/src/content/docs/logs/logpull/requesting-logs.mdx
index 685501c9631c889..c7443bca08d6d5c 100644
--- a/src/content/docs/logs/logpull/requesting-logs.mdx
+++ b/src/content/docs/logs/logpull/requesting-logs.mdx
@@ -12,20 +12,20 @@ products:
 
 The three endpoints supported by the Logpull API are:
 
-- `GET /logs/received` - returns HTTP request log data based on the parameters specified
-- `GET /logs/received/fields` - returns the list of all available log fields
-- `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
+* `GET /logs/received` - returns HTTP request log data based on the parameters specified
+* `GET /logs/received/fields` - returns the list of all available log fields
+* `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
 
 ## Required authentication headers
 
 The following headers are required for all endpoint calls:
 
-- `X-Auth-Email` - the Cloudflare account email address associated with the domain
-- `X-Auth-Key` - the Cloudflare API key
+* `X-Auth-Email` - the Cloudflare account email address associated with the domain
+* `X-Auth-Key` - the Cloudflare API key
 
 Alternatively, API tokens with Logs Read permissions can also be used for authentication:
 
-- `Authorization: Bearer <API_TOKEN>`
+* `Authorization: Bearer <API_TOKEN>`
 
 ## Parameters
 
@@ -45,9 +45,11 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}?[&fiel
 
 The following table describes the parameters available:
 
+
+
 | Parameter      | Description                                                                                                                                                                                                                                                                                                                          | Applies to                                | Required |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | -------- |
-| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p> | /logs/received                            | Yes      |
+| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p>                                                                                                                                                 | /logs/received                            | Yes      |
 | end            | <p>- Exclusive</p> <p>- Same format as <em>start</em></p> <p>- Must be at least 1 minute earlier than now and later than <em>start</em></p>                                                                                                                                                                                          | /logs/received                            | Yes      |
 | count          | <p>- Return up to that many records</p> <p>- Do not include if returning all records</p> <p>- Results are not sorted; therefore, different data for repeated requests is likely</p> <p></p> <p>- Applies to number of total records returned, not number of sampled records</p>                                                      | /logs/received                            | No       |
 | sample         | <p>- Return only a sample of records</p> <p>- Do not include if returning all records</p> <p>- Value can range from `0.0` (exclusive) to `1.0` (inclusive)</p> <p>- `sample=0.1` means return 10% (1 in 10) of all records</p> <p>- Results are random; therefore, different numbers of results for repeated requests are likely</p> | /logs/received                            | No       |
@@ -55,14 +57,18 @@ The following table describes the parameters available:
 | timestamps     | <p>- Format in which timestamp fields will be returned</p> <p>- Value options are: `unixnano` (default), `unix`, `rfc3339`</p> <p>- Timestamps returned as integers for `unix` and `unixnano` and as strings for `rfc3339`</p>                                                                                                       | <p>/logs/received</p> <p>/logs/rayids</p> | No       |
 | CVE-2021-44228 | <p>- Optional redaction for [CVE-2021-44228](https://www.cve.org/CVERecord?id=CVE-2021-44228). This option will replace every occurrence of the string `${` with `x{`.</p> <p> For example: `CVE-2021-44228=true` </p>                                                                                                               | <p>/logs/received</p>                     | No       |
 
+
+
 :::note[Note]
 
+
 The maximum time range from **start** to **end** cannot exceed 1 hour. Because **start** is inclusive and **end** is exclusive, to get all the data for every minute, starting at 10AM, the proper values are:
 
 `start=2018-05-15T10:00:00Z&end=2018-05-15T10:01:00Z`, then `start=2018-05-15T10:01:00Z&end=2018-05-15T10:02:00Z` and so on.
 
 The overlap will be handled correctly.
 
+
 :::
 
 ## Example API requests using cURL
@@ -85,8 +91,10 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}}
 
 :::note[Note]
 
+
 The IATA code returned as part of the **RayID** does not need to included in the request. For example, if you have a **RayID** such as `49ddb3e70e665831-DFW`, only include `49ddb3e70e665831` in your request.
 
+
 :::
 
 ## Fields
diff --git a/src/content/docs/logs/logpull/understanding-the-basics.mdx b/src/content/docs/logs/logpull/understanding-the-basics.mdx
index bdd4d1622f13746..0464c6ff3cdf093 100644
--- a/src/content/docs/logs/logpull/understanding-the-basics.mdx
+++ b/src/content/docs/logs/logpull/understanding-the-basics.mdx
@@ -10,7 +10,7 @@ products:
 
 ## Access pattern
 
-The basic access pattern is _give me all the logs for zone Z for minute M_ where the minute _M_ refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
+The basic access pattern is *give me all the logs for zone Z for minute M* where the minute *M* refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
 
 To start, try running your query every minute. If responses are too small, go up to 5 minutes as this will be appropriate for most zones. If the responses are too large, try going down to 15 seconds.
 
@@ -24,7 +24,7 @@ Because our log processing system ingests data in batches, most zones with less
 
 The `logs/received` API endpoint exposes data by time received, which is the time the event was written to disk in the Cloudflare Logs aggregation system.
 
-Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from _rsyslog_ (albeit in chunks).
+Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from *rsyslog* (albeit in chunks).
 
 This means that to obtain logs for a given time range, you can issue one call for each consecutive minute (or other time range). Because log lines are batched by time received and made available, there is no late arriving data. A response for a given minute will never change. You do not have to repeatedly poll a given time range to receive logs as they converge on our aggregation system.
 
@@ -32,7 +32,7 @@ This means that to obtain logs for a given time range, you can issue one call fo
 
 The Logpull API returns data in NDJSON format, whereby each log line is a valid JSON object. Major analysis tools like Google BigQuery and AWS Kinesis require this format.
 
-To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into _jq_ using the _slurp_ (or simply _s_) flag:
+To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into *jq* using the *slurp* (or simply *s*) flag:
 
 `<API request data> | jq -s`
 
@@ -42,15 +42,15 @@ The following is a sample log with default fields:
 
 ```json
 {
-	"ClientIP": "89.163.242.206",
-	"ClientRequestHost": "www.theburritobot.com",
-	"ClientRequestMethod": "GET",
-	"ClientRequestURI": "/static/img/testimonial-hipster.png",
-	"EdgeEndTimestamp": 1506702504461999900,
-	"EdgeResponseBytes": 69045,
-	"EdgeResponseStatus": 200,
-	"EdgeStartTimestamp": 1506702504433000200,
-	"RayID": "3a6050bcbe121a87"
+  "ClientIP": "89.163.242.206",
+  "ClientRequestHost": "www.theburritobot.com",
+  "ClientRequestMethod": "GET",
+  "ClientRequestURI": "/static/img/testimonial-hipster.png",
+  "EdgeEndTimestamp": 1506702504461999900,
+  "EdgeResponseBytes": 69045,
+  "EdgeResponseStatus": 200,
+  "EdgeStartTimestamp": 1506702504433000200,
+  "RayID": "3a6050bcbe121a87"
 }
 ```
 
diff --git a/src/content/docs/logs/logpush-mcp-server.mdx b/src/content/docs/logs/logpush-mcp-server.mdx
index 66fb1c45f2e2f73..606c4e683714467 100644
--- a/src/content/docs/logs/logpush-mcp-server.mdx
+++ b/src/content/docs/logs/logpush-mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Access the Logpush MCP server on GitHub.
 products:
   - logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
index fd2d2d005e6d33d..4ab48625e439d06 100644
--- a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
+++ b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
@@ -12,8 +12,10 @@ You can manage your Cloudflare Logpush service using Python. In the script below
 
 :::note
 
+
 The examples below are for zone-scoped datasets. Account-scoped datasets should use `<ACCOUNT_ID>` instead of `<ZONE_ID>`.
 
+
 :::
 
 ```python
diff --git a/src/content/docs/logs/logpush/examples/index.mdx b/src/content/docs/logs/logpush/examples/index.mdx
index 17da91fca9f2307..d593b40a49fe8db 100644
--- a/src/content/docs/logs/logpush/examples/index.mdx
+++ b/src/content/docs/logs/logpush/examples/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/index.mdx b/src/content/docs/logs/logpush/index.mdx
index e93944723bd2eb9..c97ab2846f221ff 100644
--- a/src/content/docs/logs/logpush/index.mdx
+++ b/src/content/docs/logs/logpush/index.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { FeatureTable, LinkButton } from "~/components";
+import { FeatureTable, LinkButton } from "~/components"
 
 Logpush delivers logs in batches as quickly as possible, with no minimum batch size, potentially delivering files more than once per minute. This capability enables Cloudflare to provide information almost in real time, in smaller file sizes.
 
@@ -57,6 +57,8 @@ There is currently a max limit of **4 Logpush jobs per zone**. Trying to create
 
 :::note
 
+
 Users without an Enterprise plan can still access [Workers Trace Events Logpush](/workers/observability/logs/logpush/) by subscribing to the [Workers Paid](/workers/platform/pricing/) plan.
 
+
 :::
diff --git a/src/content/docs/logs/logpush/logpush-health.mdx b/src/content/docs/logs/logpush/logpush-health.mdx
index 9f31536d4532a8a..10604407f89dd20 100644
--- a/src/content/docs/logs/logpush/logpush-health.mdx
+++ b/src/content/docs/logs/logpush/logpush-health.mdx
@@ -20,17 +20,17 @@ Health notifications work alongside the Health Dashboard to provide both real-ti
 
 ## Access Health Dashboards
 
-1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.
-2. Go to the **Health** tab.
-3. Select the job you want to analyze.
-4. Specify the time range you want to review.
-5. _(Optional)_ From the **Jobs** tab, locate the job you want to analyze.
-6. Hover over the **Job Health (24h)** column for that job and select **View Health**.
+1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.  
+2. Go to the **Health** tab.  
+3. Select the job you want to analyze.  
+4. Specify the time range you want to review.  
+5. *(Optional)* From the **Jobs** tab, locate the job you want to analyze.  
+6. Hover over the **Job Health (24h)** column for that job and select **View Health**.  
 7. You will be redirected to the **Health** tab, where you can select the desired time range for analysis.
 
 ### Data availability and API access
 
-- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.
+- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.  
 - The raw health metrics can be queried via the `logpushHealthAdaptiveGroups` dataset in the GraphQL API.
 - You can explore or test queries using the [Cloudflare GraphQL Explorer](https://graphql.cloudflare.com/explorer).
 
@@ -62,7 +62,7 @@ Indicates that all upload attempts for a batch were exhausted without success. W
 
 ## Health dashboard flow
 
-The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.
+The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.  
 
 Each view highlights a different aspect of job performance — what was delivered and how reliably it was delivered.
 
@@ -72,23 +72,23 @@ Each view highlights a different aspect of job performance — what was delivere
 
 #### Charts and metrics
 
-- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.
-  - **Successful Uploads** - Total number of batches successfully uploaded.
-  - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
+- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.  
+    - **Successful Uploads** - Total number of batches successfully uploaded.  
+    - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
 
-- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.
-  - **Uploaded Log Lines** - Total number of log lines successfully delivered.
-  - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
+- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.  
+    - **Uploaded Log Lines** - Total number of log lines successfully delivered.  
+    - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
 
-- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.
-  - **Uncompressed Data (raw)** - Total size of log data before compression.
-  - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
+- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.  
+    - **Uncompressed Data (raw)** - Total size of log data before compression.  
+    - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
 
 #### When to use
 
 Start here to assess overall data delivery health:
 
-- High upload success and stable data volume indicate a healthy Logpush job.
+- High upload success and stable data volume indicate a healthy Logpush job.  
 - Drops, spikes, or failed uploads suggest delivery issues — proceed to **Upload Reliability** to investigate root causes.
 
 ### Upload Reliability
@@ -97,37 +97,37 @@ Upload Reliability helps you identify factors affecting reliability, stability,
 
 #### Charts and metrics
 
-- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.
-  - **Success Rate** - Percentage of batches successfully uploaded.
-  - **Successful Uploads** - Total number of batches successfully completed.
+- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.  
+    - **Success Rate** - Percentage of batches successfully uploaded.  
+    - **Successful Uploads** - Total number of batches successfully completed.
 
-- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.
-  - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.
-  - **Average Upload Duration** - Average time taken to upload logs after they are generated.
+- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.  
+    - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.  
+    - **Average Upload Duration** - Average time taken to upload logs after they are generated.
 
-- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.
-  - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
+- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.  
+    - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
 
 #### When to use
 
 Use this view to troubleshoot reliability issues:
 
-- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.
+- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.  
 - Combine with **Upload Health** metrics to correlate delivery success with underlying reliability patterns.
 
 ## Troubleshooting guide
 
 The Logpush Health Dashboards help you monitor the status, reliability, and performance of your Logpush jobs. Use this guide to interpret each chart, identify the root cause of anomalies, and take corrective action.
 
-| Chart name                                  | Symptom                                       | What it means                                                                                                                                 | Possible causes                                                                                                                                                                                                       | Recommended actions                                                                                                                                                                                                                           |
-| ------------------------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Batch Upload Success vs Failure**         | Failed uploads                                | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/> - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
-| **Log Lines Uploaded**                      | Dropped log lines or reduced delivery volume  | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches.                                                 | - Spike in failed uploads. <br/> - Destination ingestion limits or partial uploads.                                                                                                                                   | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/> - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes.                                               |
-| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume                | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches.                                       | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits.                                                                                                         | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries.                                                                                             |
-| **Uploaded Logs by Status Code**            | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries.                                                                                     | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination.                                                                                                   | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size.                                                                                         |
-| **Retry Attempts**                          | Frequent retry activity                       | Uploads are repeatedly failing and retried multiple times.                                                                                    | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination.                                                                                                    | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review.                                                             |
-| **Avg. Upload Duration**                    | Long upload times                             | Uploads are taking longer than expected, indicating latency or oversized batches.                                                             | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays.                                                                                                 | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings.                                                                                        |
-| **Destination Availability**                | Low or unstable availability                  | Cloudflare cannot consistently connect to your destination.                                                                                   | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare.                                                                                           | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings.                                                                             |
+| Chart name | Symptom | What it means | Possible causes | Recommended actions |
+|-----------------|-------------|-------------------|----------------------|--------------------------|
+| **Batch Upload Success vs Failure** | Failed uploads | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/>  - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
+| **Log Lines Uploaded** | Dropped log lines or reduced delivery volume | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches. | - Spike in failed uploads. <br/>  - Destination ingestion limits or partial uploads. | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/>  - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes. |
+| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches. | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits. | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries. |
+| **Uploaded Logs by Status Code** | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries. | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination. | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size. |
+| **Retry Attempts** | Frequent retry activity | Uploads are repeatedly failing and retried multiple times. | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination. | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review. |
+| **Avg. Upload Duration** | Long upload times | Uploads are taking longer than expected, indicating latency or oversized batches. | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays. | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings. |
+| **Destination Availability** | Low or unstable availability | Cloudflare cannot consistently connect to your destination. | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare. | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings. |
 
 ## Understanding retry behavior
 
diff --git a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
index d7b7dd78507d62e..6a98f17905433ca 100644
--- a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
@@ -18,19 +18,19 @@ You can locate `{zone_id}` and `{account_id}` arguments based on the [Find zone
 The `{job_id}` argument is numeric, like 123456.
 The `{dataset_id}` argument indicates the log category (such as `http_requests` or `audit_logs`).
 
-| Operation | Description                                 | API                                                                                            |
+| Operation | Description                                 | API                                                                                                                                                                                              |
 | --------- | ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                      |
-| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
-| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                        |
-| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
+| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                                             |
+| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)                                     |
+| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                                                 |
+| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)        |
 | `GET`     | Retrieve all available fields for a dataset | [Documentation](/api/resources/logpush/subresources/datasets/subresources/fields/methods/get/) |
-| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                      |
-| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                      |
-| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/)             |
-| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
-| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
-| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                  |
+| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                                      |
+| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                           |
+| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/) |
+| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                                      |
+| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                      |
+| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                           |
 
 For concrete examples, refer to the tutorials in [Logpush examples](/logs/logpush/examples/).
 
@@ -47,25 +47,25 @@ Before creating a new job, ownership of the destination must be proven.
 To issue an ownership challenge token to your destination:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/ownership"
-	method="POST"
-	json={{
-		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-	}}
+  path="/zones/{zone_id}/logpush/ownership"
+  method="POST"
+  json={{
+    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+  }}
 />
 
 A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path, if appropriate for your destination):
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"valid": true,
-		"message": "",
-		"filename": "<PATH_TO_CHALLENGE_FILE>.txt"
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "valid": true,
+    "message": "",
+    "filename": "<PATH_TO_CHALLENGE_FILE>.txt"
+  },
+  "success": true
 }
 ```
 
@@ -138,23 +138,23 @@ For more information on the value for your cloud storage provider, consult the f
 To check if a destination is already in use:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/validate/destination/exists"
-	method="POST"
-	json={{
-		destination_conf: "s3://foo",
-	}}
+  path="/zones/{zone_id}/logpush/validate/destination/exists"
+  method="POST"
+  json={{
+    destination_conf: "s3://foo",
+  }}
 />
 
 Response
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"exists": false
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "exists": false
+  },
+  "success": true
 }
 ```
 
@@ -173,28 +173,28 @@ The kind parameter cannot be used to update existing Logpush jobs. You can only
 :::
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/jobs"
-	method="POST"
-	json={{
-		name: "<DOMAIN_NAME>",
-		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-		dataset: "http_requests",
-		output_options: {
-			field_names: [
-				"ClientIP",
-				"ClientRequestHost",
-				"ClientRequestMethod",
-				" ClientRequestURI",
-				"EdgeEndTimestamp",
-				"EdgeResponseBytes",
-				"EdgeResponseStatus",
-				"EdgeStartTimestamp",
+  path="/zones/{zone_id}/logpush/jobs"
+  method="POST"
+  json={{
+    name: "<DOMAIN_NAME>",
+    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+    dataset: "http_requests",
+    output_options: {
+      field_names: [
+        "ClientIP",
+        "ClientRequestHost",
+        "ClientRequestMethod",
+        " ClientRequestURI",
+        "EdgeEndTimestamp",
+        "EdgeResponseBytes",
+        "EdgeResponseStatus",
+        "EdgeStartTimestamp",
 				"RayID",
-			],
+      ],
 			timestamp_format: "rfc3339",
-		},
+    },
 		kind: "edge",
-	}}
+  }}
 />
 
 ## Options
@@ -205,7 +205,7 @@ If you are still using logpull_options, here are the options that you can custom
 
 1. **Fields** (optional): Refer to [Datasets](/logs/logpush/logpush-job/datasets/) for the currently available fields. The list of fields is also accessible directly from the API: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields`. Default fields: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields/default`.
 2. **Timestamp format** (optional): The format in which timestamp fields will be returned. Value options: `unixnano` (nanoseconds unit - default), `unix` (seconds unit), `rfc3339` (seconds unit).
-3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`. To enable it, set `"CVE-2021-44228": true`.
+3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`.  To enable it, set `"CVE-2021-44228": true`.
 
 :::note[Note]
 
@@ -215,26 +215,26 @@ The **CVE-2021-44228** parameter can only be set through the API at this time. U
 To check if the selected **logpull_options** are valid:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/validate/origin"
-	method="POST"
-	json={{
+  path="/zones/{zone_id}/logpush/validate/origin"
+  method="POST"
+  json={{
 		logpull_options:
 			"fields=RayID,ClientIP,EdgeStartTimestamp&timestamps=rfc3339&CVE-2021-44228=true",
 		dataset: "http_requests",
-	}}
+  }}
 />
 
 Response
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"valid": true,
-		"message": ""
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "valid": true,
+    "message": ""
+  },
+  "success": true
 }
 ```
 
@@ -280,10 +280,10 @@ When customer-configured sampling is applied, the `SampleInterval` field value i
 
 These parameters control the size of each upload batch — not how quickly data is delivered. Use them to prevent overloading your destination with uploads that are too large or too small.
 
-| Parameter                     | Description                                                               | Default               |
-| ----------------------------- | ------------------------------------------------------------------------- | --------------------- |
-| `max_upload_bytes`            | Maximum uncompressed file size of a batch of logs.                        | Varies by destination |
-| `max_upload_records`          | Maximum number of log lines per batch.                                    | 100,000               |
+| Parameter | Description | Default |
+| --- | --- | --- |
+| `max_upload_bytes` | Maximum uncompressed file size of a batch of logs. | Varies by destination |
+| `max_upload_records` | Maximum number of log lines per batch. | 100,000 |
 | `max_upload_interval_seconds` | Maximum time-span of log data per batch (used during catch-up scenarios). | Varies by destination |
 
 :::note
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
index a9bd442099c837b..618a7f86d3a5d55 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
index 452263a6cac1017..2068e23086295d9 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
@@ -1,8 +1,8 @@
 ---
 pcx_content_type: reference
-title: CMB support by dataset
+title: CMB support by dataset 
 external_link: /data-localization/metadata-boundary/logpush-datasets/
 description: Learn about cmb support by dataset  in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
index d57a162728ea19b..64c4408ce21b874 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
@@ -12,25 +12,25 @@ products:
 
 The datasets below describe the fields available by log category:
 
-- [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
-- [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
+* [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
+* [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
 
 ## API
 
 The list of fields can also be accessed directly from the API using the following endpoints:
 
-- For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
+* For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
 
-- For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
+* For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
 
 The `<DATASET>` argument indicates the log category. For example, `http_requests`, `spectrum_events`, `firewall_events`, `nel_reports`, or `dns_logs`.
 
 ## Availability
 
-- The availability of Logpush dataset fields depends on your subscription plan.
-- Zone-scoped HTTP requests are available in both Logpush and Logpull.
-- [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
-- All other datasets are only available through Logpush.
+* The availability of Logpush dataset fields depends on your subscription plan.
+* Zone-scoped HTTP requests are available in both Logpush and Logpull.
+* [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
+* All other datasets are only available through Logpush.
 
 ## Deprecation
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
index 3916cd8f337d26e..f21b39be05e2657 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
@@ -49,7 +49,7 @@ Whether the response was cached or not.
 
 Type: `int`
 
-Integer value of response code. For more information refer to [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
+Integer value of response code. For more information refer to  [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
 
 ## SourceIP
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
index d9de685d205d4d0..b44ea90a6fa6a98 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
index 12b4d2e27bc5489..6b8090800495242 100644
--- a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
@@ -8,8 +8,9 @@ products:
   - logpush
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 Edge Log Delivery allows customers to send logs directly from Cloudflare’s edge to their destination of choice. You can configure the maximum interval for your log batches between 30 seconds and five minutes. However, you cannot specify a minimum interval for log batches, meaning that log files may be sent in shorter intervals than the maximum specified. Compared to Logpush, Edge Log Delivery sends logs with lower latency, more frequently, and in smaller batches.
 
 Edge Log Delivery is only available for HTTP request logs. Refer to the [API configuration](/logs/logpush/logpush-job/api-configuration/#kind) page for steps on how to configure a job to use Edge Log Delivery.
+
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
index e9823d82ca24e5c..65b671327acdea2 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
@@ -42,9 +42,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
index 437fe5b4f67cf0f..301c4bcbaf9e976 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
@@ -79,7 +79,6 @@ signedResourceTypes must be Object only (srt=o)
 ```
 
 To resolve this error, regenerate your SAS token using [Storage Explorer](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer) with the correct permissions:
-
 - Service: Blob-only (`ss=b`)
 - Resource type: Object-only (`srt=o`)
 - Permissions: Write-only
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
index bfc9e8b76c9f8f2..bde5e5a6cadf67d 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
@@ -40,23 +40,22 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 1. Register or use an existing zone for the dedicated egress IPs pool.
 2. Contact your account team to get the ID for your dedicated egress IPs pool.
 3. Make a `PATCH` request to the [Edit Zone Setting](/api/resources/zones/subresources/settings/methods/edit/) endpoint:
-
-- Specify `aegis` as the setting ID in the URL.
-- In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
+  - Specify `aegis` as the setting ID in the URL.
+  - In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
 
 <APIRequest
-	path="/zones/{zone_id}/settings/{setting_id}"
-	method="PATCH"
-	json={{
-		id: "aegis",
-		value: {
-			enabled: true,
-			pool_id: "<YOUR_EGRESS_POOL_ID>",
-		},
+  path="/zones/{zone_id}/settings/{setting_id}"
+  method="PATCH"
+  json={{
+		  "id": "aegis",
+			"value": {
+				"enabled": true,
+				"pool_id": "<YOUR_EGRESS_POOL_ID>",
+				},
 	}}
 	parameters={{
-		setting_id: "aegis",
-	}}
+    setting_id: "aegis",
+  }}
 />
 
 ## 3. Proxy zone setup
@@ -67,6 +66,7 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 
 2. If needed, configure [origin rules](/rules/origin-rules/) to specify a custom port. This is useful if your destination only accepts traffic on a non standard port, for example `12345`. You can configure `logpush.yourdestinationendpoint.com` (without specifying a port, as Cloudflare by default only proxies traffic on HTTP/HTTPS ports) to proxy to `yourdestinationendpoint.com:12345`.
 
+
 ## 4. Configure Logpush
 
 1. Create a Logpush job with the following details:
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
index 271f74a01e3f258..037278d7af513e7 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
@@ -11,20 +11,22 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Push your Cloudflare logs to Elastic for instant visibility and insights. Enabling this integration with Elastic comes with a predefined dashboard to view all of your Cloudflare observability and security data with ease.
 
 The Cloudflare Logpush integration can be used in three different modes to collect data:
 
-- **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
-- **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
-- **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
+* **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
+* **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
+* **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
 
 :::note[Note]
 
+
 Elastic recommends the AWS S3 SQS mode.
 
+
 :::
 
 ## Enable Logpush Job in Cloudflare
@@ -42,18 +44,17 @@ Add the same custom header along with its value on both sides for additional sec
 For example, while creating a job along with a header and value for a particular dataset:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/jobs"
-	method="POST"
-	json={{
-		name: "<PUBLIC_DOMAIN>",
-		destination_conf:
-			"https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
-		dataset: "http_requests",
-		output_options: {
-			field_names: ["RayID", "EdgeStartTimestamp"],
-			timestamp_format: "rfc3339",
-		},
-	}}
+  path="/zones/{zone_id}/logpush/jobs"
+  method="POST"
+  json={{
+    name: "<PUBLIC_DOMAIN>",
+    destination_conf: "https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
+    dataset: "http_requests",
+    output_options: {
+      field_names: ["RayID", "EdgeStartTimestamp"],
+      timestamp_format: "rfc3339"
+    }
+  }}
 />
 
 ## Enable the Integration in Elastic
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
index 79d92a490df72b5..559b432c8b43b4e 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
@@ -39,9 +39,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
index bc517b5783e0a01..54b030d14362706 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 To configure a QRadar/Cloudflare integration you have the option to use one of the following methods:
 
@@ -22,113 +22,57 @@ To send Cloudflare logs to QRadar you need to create a [Logpush job to HTTP endp
 ### Cloudflare Firewall events
 
 <APIRequest
-	method="POST"
-	path="/zones/{zone_id}/logpush/jobs"
-	json={{
-		name: "<NAME>",
-		output_options: {
-			field_names: [
-				"Action",
-				"ClientIP",
-				"ClientASN",
-				"ClientASNDescription",
-				"ClientCountry",
-				"ClientIPClass",
-				"ClientRefererHost",
-				"ClientRefererPath",
-				"ClientRefererQuery",
-				"ClientRefererScheme",
-				"ClientRequestHost",
-				"ClientRequestMethod",
-				"ClientRequestPath",
-				"ClientRequestProtocol",
-				"ClientRequestQuery",
-				"ClientRequestScheme",
-				"ClientRequestUserAgent",
-				"EdgeColoCode",
-				"EdgeResponseStatus",
-				"Kind",
-				"MatchIndex",
-				"Metadata",
-				"OriginResponseStatus",
-				"OriginatorRayID",
-				"RayID",
-				"RuleID",
-				"Source",
-				"Datetime",
-			],
-			timestamp_format: "rfc3339",
-		},
-		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-		max_upload_bytes: 5000000,
-		max_upload_records: 1000,
-		dataset: "firewall_events",
-		enabled: true,
-	}}
+  method="POST"
+  path="/zones/{zone_id}/logpush/jobs"
+  json={{
+    name: "<NAME>",
+    output_options: {
+      field_names: [
+        "Action", "ClientIP", "ClientASN", "ClientASNDescription", "ClientCountry", "ClientIPClass",
+        "ClientRefererHost", "ClientRefererPath", "ClientRefererQuery", "ClientRefererScheme",
+        "ClientRequestHost", "ClientRequestMethod", "ClientRequestPath", "ClientRequestProtocol",
+        "ClientRequestQuery", "ClientRequestScheme", "ClientRequestUserAgent", "EdgeColoCode",
+        "EdgeResponseStatus", "Kind", "MatchIndex", "Metadata", "OriginResponseStatus",
+        "OriginatorRayID", "RayID", "RuleID", "Source", "Datetime"
+      ],
+      timestamp_format: "rfc3339"
+    },
+    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+    max_upload_bytes: 5000000,
+    max_upload_records: 1000,
+    dataset: "firewall_events",
+    enabled: true
+  }}
 />
 
+
 ### Cloudflare HTTP events
 
 <APIRequest
-	method="POST"
-	path="/zones/{zone_id}/logpush/jobs"
-	json={{
-		name: "<NAME>",
-		output_options: {
-			field_names: [
-				"ClientRequestMethod",
-				"EdgeResponseStatus",
-				"ClientIP",
-				"ClientSrcPort",
-				"CacheCacheStatus",
-				"ClientCountry",
-				"ClientDeviceType",
-				"ClientIPClass",
-				"ClientMTLSAuthCertFingerprint",
-				"ClientMTLSAuthStatus",
-				"ClientRegionCode",
-				"ClientRequestBytes",
-				"ClientRequestHost",
-				"ClientRequestPath",
-				"ClientRequestProtocol",
-				"ClientRequestReferer",
-				"ClientRequestScheme",
-				"ClientRequestSource",
-				"ClientRequestURI",
-				"ClientRequestUserAgent",
-				"ClientSSLCipher",
-				"ClientSSLProtocol",
-				"ClientXRequestedWith",
-				"EdgeEndTimestamp",
-				"EdgeRequestHost",
-				"EdgeResponseBodyBytes",
-				"EdgeResponseBytes",
-				"EdgeServerIP",
-				"EdgeStartTimestamp",
-				"SecurityActions",
-				"SecurityRuleIDs",
-				"SecuritySources",
-				"OriginIP",
-				"OriginResponseStatus",
-				"OriginSSLProtocol",
-				"ParentRayID",
-				"RayID",
-				"SecurityAction",
-				"WAFAttackScore",
-				"SecurityRuleID",
-				"SecurityRuleDescription",
-				"WAFSQLiAttackScore",
-				"WAFXSSAttackScore",
-				"EdgeStartTimestamp",
-			],
-			timestamp_format: "rfc3339",
-		},
-		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-		max_upload_bytes: 5000000,
-		max_upload_records: 1000,
-		dataset: "http_requests",
-		enabled: true,
-	}}
+  method="POST"
+  path="/zones/{zone_id}/logpush/jobs"
+  json={{
+    name: "<NAME>",
+    output_options: {
+      field_names: [
+        "ClientRequestMethod", "EdgeResponseStatus", "ClientIP", "ClientSrcPort", "CacheCacheStatus",
+        "ClientCountry", "ClientDeviceType", "ClientIPClass", "ClientMTLSAuthCertFingerprint", "ClientMTLSAuthStatus",
+        "ClientRegionCode", "ClientRequestBytes", "ClientRequestHost", "ClientRequestPath", "ClientRequestProtocol",
+        "ClientRequestReferer", "ClientRequestScheme", "ClientRequestSource", "ClientRequestURI", "ClientRequestUserAgent",
+        "ClientSSLCipher", "ClientSSLProtocol", "ClientXRequestedWith", "EdgeEndTimestamp", "EdgeRequestHost",
+        "EdgeResponseBodyBytes", "EdgeResponseBytes", "EdgeServerIP", "EdgeStartTimestamp", "SecurityActions",
+        "SecurityRuleIDs", "SecuritySources", "OriginIP", "OriginResponseStatus", "OriginSSLProtocol", "ParentRayID",
+        "RayID", "SecurityAction", "WAFAttackScore", "SecurityRuleID", "SecurityRuleDescription", "WAFSQLiAttackScore",
+        "WAFXSSAttackScore", "EdgeStartTimestamp"
+      ],
+      timestamp_format: "rfc3339"
+    },
+    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+    max_upload_bytes: 5000000,
+    max_upload_records: 1000,
+    dataset: "http_requests",
+    enabled: true
+  }}
 />
 
 Cloudflare checks the accessibility of the IP address, port, and validates the certificate of the HTTP Receive log source. If all parameters are valid, a Logpush is created, and starts to send events to HTTP Receiver log source.
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
index e30073dde0691a1..c9e507400e4736f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
@@ -79,7 +79,7 @@ When configuring your Logpush job using IAM Access Keys, ensure that the IAM use
 kinesis://<STREAM_NAME>?region=<AWS_REGION>&access-key-id=<AWS_ACCESS_KEY_ID>&secret-access-key=<AWS_SECRET_ACCESS_KEY>
 ```
 
-### IAM Access Key example
+### IAM Access Key example 
 
 ```bash
 $ curl https://api.cloudflare.com/client/v4/zones/$ZONE_TAG/logpush/jobs \
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
index c8e74bd58ce5b1c..b5a8ad2efe5d08a 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about exabeam in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
index e035c9cab36b111..ebd93fd74f3fe4e 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about sekoia in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
index 9b27ff95df6e41f..33a79b6922e260b 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about taegis in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/filters.mdx b/src/content/docs/logs/logpush/logpush-job/filters.mdx
index 70fd97b0bc41bcc..e3d0dec59462d05 100644
--- a/src/content/docs/logs/logpush/logpush-job/filters.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/filters.mdx
@@ -100,11 +100,12 @@ Here is an example request using cURL via API:
 To set filters through the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
-
+ 
    For account: <DashButton url="/?to=/:account/logs" />
-
+ 
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
+
 2. Select the dataset you want to push to a storage service. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
 3. Below **Select data fields**, in the **Filter** section, you can set up your filters.
 4. You need to select a [dataset field](/logs/logpush/logpush-job/datasets/), an [Operator](/logs/logpush/logpush-job/filters/#logical-operators), and a **Value**.
diff --git a/src/content/docs/logs/logpush/logpush-job/index.mdx b/src/content/docs/logs/logpush/logpush-job/index.mdx
index 9f631a5d38edfd0..552977e3e38e2b6 100644
--- a/src/content/docs/logs/logpush/logpush-job/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: Configure and manage Logpush job settings.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
index 0c4922d8910409d..69caff8184b218b 100644
--- a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
@@ -70,17 +70,17 @@ Your bucket's IAM/access controls and Cloudflare account security are the primar
 
 ## Which destinations require an ownership challenge?
 
-| Destination           | Ownership challenge required       |
-| --------------------- | ---------------------------------- |
-| AWS S3                | Yes (or use access key/secret key) |
-| Google Cloud Storage  | Yes                                |
-| Azure Blob Storage    | Yes                                |
-| Sumo Logic            | Yes                                |
-| S3-compatible storage | No                                 |
-| HTTP endpoints        | No                                 |
-| Datadog               | No                                 |
-| Splunk                | No                                 |
-| New Relic             | No                                 |
+| Destination | Ownership challenge required |
+| --- | --- |
+| AWS S3 | Yes (or use access key/secret key) |
+| Google Cloud Storage | Yes |
+| Azure Blob Storage | Yes |
+| Sumo Logic | Yes |
+| S3-compatible storage | No |
+| HTTP endpoints | No |
+| Datadog | No |
+| Splunk | No |
+| New Relic | No |
 
 For destinations that do not require an ownership challenge, Cloudflare uses alternative authentication methods such as API keys or tokens.
 
diff --git a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
index b69e56fe07a33a4..090c84dab4fef92 100644
--- a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
+++ b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
@@ -9,12 +9,12 @@ products:
   - logs
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components";
+import { GlossaryTooltip, DashButton } from "~/components"
 
 Cloudflare will deploy some updates to security-related fields in Cloudflare Logs. These updates will affect the following datasets:
 
-- [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
-- [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
+* [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
+* [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
 
 ## Timeline
 
@@ -26,18 +26,18 @@ For the log fields being added, Cloudflare will gradually start adding them to l
 
 For the log fields being renamed, Cloudflare will:
 
-- **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
-- **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
+* **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
+* **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
 
 For the log fields being removed, Cloudflare is announcing them as deprecated. Their removal from logs datasets will occur on August 1, 2023.
 
 In addition to these Cloudflare Logs changes, Cloudflare will also add new security-related fields to the following [GraphQL datasets](/analytics/graphql-api/features/data-sets/):
 
-- `httpRequestsAdaptive `
-- `httpRequestsAdaptiveGroups`
-- `firewallEventsAdaptive`
-- `firewallEventsAdaptiveGroups`
-- `firewallEventsAdaptiveByTimeGroups`
+* `httpRequestsAdaptive `
+* `httpRequestsAdaptiveGroups`
+* `firewallEventsAdaptive`
+* `firewallEventsAdaptiveGroups`
+* `firewallEventsAdaptiveByTimeGroups`
 
 ### Phase 2 (August 1, 2023)
 
@@ -49,23 +49,27 @@ For the log fields being removed, Cloudflare will also remove them from the Clou
 
 The following concepts are used below in the reviewed field descriptions:
 
-- **Terminating action:** One of the following actions:
-  - `block`
-  - `js_challenge`
-  - `managed_challenge`
-  - `challenge` (_Interactive Challenge_)
+* **Terminating action:** One of the following actions:
+
+  * `block`
+  * `js_challenge`
+  * `managed_challenge`
+  * `challenge` (*Interactive Challenge*)
 
 For more information on these actions, refer to the [Actions](/ruleset-engine/rules-language/actions/) reference in the Rules language documentation.
 
-- **Security rule:** One of the following rule types:
-  - [WAF managed rule](/waf/managed-rules/)
-  - [WAF custom rule](/waf/custom-rules/)
-  - [WAF rate limiting rule](/waf/rate-limiting-rules/)
+* **Security rule:** One of the following rule types:
+
+  * [WAF managed rule](/waf/managed-rules/)
+  * [WAF custom rule](/waf/custom-rules/)
+  * [WAF rate limiting rule](/waf/rate-limiting-rules/)
 
 ## HTTP Requests dataset changes
 
 The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) dataset according to the two-phase strategy outlined in the [timeline](#timeline):
 
+
+
 | New field name            | Type         | Description                                                                        | Old field name<br/>(deprecated on Aug 1, 2023) |
 | ------------------------- | ------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------- |
 | `SecurityRuleID`          | String       | Rule ID of the security rule that triggered a terminating action, if any.          | `WAFRuleID`                                    |
@@ -75,8 +79,12 @@ The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpus
 | `SecurityActions`         | String Array | Array of actions that Cloudflare security products performed on the request.       | `FirewallMatchesActions`                       |
 | `SecuritySources`         | String Array | Array of Cloudflare security products that matched the request.                    | `FirewallMatchesSources`                       |
 
+
+
 The following fields are now deprecated and they will be removed from the HTTP Requests dataset on August 1, 2023:
 
+
+
 | Deprecated field name | Notes                                                                 |
 | --------------------- | --------------------------------------------------------------------- |
 | `WAFProfile`          | Used in the previous version of WAF managed rules (now deprecated).   |
@@ -84,30 +92,44 @@ The following fields are now deprecated and they will be removed from the HTTP R
 | `EdgeRateLimitID`     | Used in the previous version of rate limiting rules (now deprecated). |
 | `SecurityLevel`       | N/A                                                                   |
 
+
+
 ## Firewall Events dataset changes
 
 The following fields will be added to the [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/) dataset:
 
+
+
 | Field name    | Type   | Description                                                        |
 | ------------- | ------ | ------------------------------------------------------------------ |
 | `Description` | String | The description of the rule triggered by the request.              |
 | `Ref`         | String | The user-defined identifier for the rule triggered by the request. |
 
+
+
 ## Changes to GraphQL datasets
 
 Cloudflare will add the following fields to the `httpRequestsAdaptive `and `httpRequestsAdaptiveGroups `datasets:
 
+
+
 | Field name       | Type   | Description                                                              |
 | ---------------- | ------ | ------------------------------------------------------------------------ |
 | `securityAction` | String | Action of the security rule that triggered a terminating action, if any. |
 | `securitySource` | String | Source of the security rule that triggered a terminating action, if any. |
 
+
+
 Cloudflare will also add the following field to the `firewallEventsAdaptive`, `firewallEventsAdaptiveGroups`, and `firewallEventsAdaptiveByTimeGroups` datasets:
 
+
+
 | Field name    | Type   | Description                                           |
 | ------------- | ------ | ----------------------------------------------------- |
 | `description` | String | The description of the rule triggered by the request. |
 
+
+
 These new fields will become gradually available.
 
 For more information on the available datasets, refer to [GraphQL datasets](/analytics/graphql-api/features/data-sets/).
@@ -121,8 +143,8 @@ After updating Logpush jobs, you may need to update external filters or reports
 ### Update Logpush job in the dashboard
 
 1. In the Cloudflare dashboard, go to the **Logpush** page.
-
-   <DashButton url="/?to=/:account/:zone/analytics/logs" />
+ 
+    <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select **Edit** next to the Logpush job you wish to edit.
 3. Under **Select data fields**, update the fields in your job. The new security log fields are available under **General**.
@@ -130,7 +152,7 @@ After updating Logpush jobs, you may need to update external filters or reports
 
 ### Update Logpush job via API
 
-Follow the instructions in [Update output_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
+Follow the instructions in [Update output\_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
 
 ### Update Logpush job via Terraform
 
diff --git a/src/content/docs/logs/reference/change-notices/index.mdx b/src/content/docs/logs/reference/change-notices/index.mdx
index 9457944fa3b5f78..73f10f158563f08 100644
--- a/src/content/docs/logs/reference/change-notices/index.mdx
+++ b/src/content/docs/logs/reference/change-notices/index.mdx
@@ -11,6 +11,6 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/reference/clientrequestsource.mdx b/src/content/docs/logs/reference/clientrequestsource.mdx
index 13558a727481adb..142639187d95beb 100644
--- a/src/content/docs/logs/reference/clientrequestsource.mdx
+++ b/src/content/docs/logs/reference/clientrequestsource.mdx
@@ -11,6 +11,8 @@ products:
 
 The possible values for the `ClientRequestSource` field are the following:
 
+
+
 | Value | Request source     | Description                                                                                                                             |
 | ----- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
 | `0`   | unknown            | Should never happen.                                                                                                                    |
@@ -26,3 +28,4 @@ The possible values for the `ClientRequestSource` field are the following:
 | `10`  | sslDetector        | A request made by Cloudflare's [SSL Detector system](https://blog.cloudflare.com/ssl-tls-recommender/).                                 |
 | `11`  | earlyHintsCache    | An [Early Hint request](https://blog.cloudflare.com/early-hints/).                                                                      |
 | `12`  | inBrowserChallenge | An end user request caused by a Cloudflare security product (Challenges, JavaScript Detections). These requests never reach the origin. |
+
diff --git a/src/content/docs/logs/reference/index.mdx b/src/content/docs/logs/reference/index.mdx
index 31fafb51510ff9a..2dee7feaa4467ed 100644
--- a/src/content/docs/logs/reference/index.mdx
+++ b/src/content/docs/logs/reference/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 These reference resources are useful for gaining a more in-depth understanding of the terminology and status codes that are part of the Cloudflare Logs data. This information is especially important when integrating your data with third-party tools:
 
diff --git a/src/content/docs/logs/reference/security-fields.mdx b/src/content/docs/logs/reference/security-fields.mdx
index af844e299e4e427..c1dfac2c6154b28 100644
--- a/src/content/docs/logs/reference/security-fields.mdx
+++ b/src/content/docs/logs/reference/security-fields.mdx
@@ -13,6 +13,8 @@ The Security fields contain rules to block requests that contain specific types
 
 ## SecurityActions
 
+
+
 | Value                                  | Action         | Description                                                                                                                                                |
 | -------------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `unknown`                              | Unknown        | Take no other action.                                                                                                                                      |
@@ -25,15 +27,19 @@ The Security fields contain rules to block requests that contain specific types
 | `challengeSolved`                      | Allow          | Allow once interactive challenge solved.                                                                                                                   |
 | `challengeBypassed`                    | Allow          | Interactive challenge is not issued again because the visitor had previously passed an interactive challenge and a valid `cf_clearance` cookie is present. |
 | `jschallengeSolved`                    | Allow          | Allow once non-interactive challenge solved.                                                                                                               |
-| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                 |
+| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                  |
 | `bypass`                               | Allow          | Bypass all subsequent firewall rules.                                                                                                                      |
 | `managedChallenge`                     | Challenge Drop | Issue managed challenge.                                                                                                                                   |
 | `managedChallengeNonInteractiveSolved` | Allow          | Allow once the managed challenge is solved via non-interactive interstitial page.                                                                          |
 | `managedChallengeInteractiveSolved`    | Allow          | Allow once the managed challenged is solved via interactive interstitial page.                                                                             |
 | `managedChallengeBypassed`             | Allow          | Challenge was not presented because visitor had clearance from previous challenge.                                                                         |
 
+
+
 ## SecuritySources
 
+
+
 | Value             | Description                                                                                                      |
 | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
 | `unknown`         | Used if an event is received from a new source but the logging system has not been updated.                      |
diff --git a/src/content/docs/logs/reference/waf-fields.mdx b/src/content/docs/logs/reference/waf-fields.mdx
index e53ba194338c1b2..421f434955eb3f0 100644
--- a/src/content/docs/logs/reference/waf-fields.mdx
+++ b/src/content/docs/logs/reference/waf-fields.mdx
@@ -13,6 +13,8 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 
 ## WAF Action
 
+
+
 | Value                                      | Action          | Description                                  |
 | ------------------------------------------ | --------------- | -------------------------------------------- |
 | <span style="font-weight: 400;">`0`</span> | Unknown         | Take no other action.                        |
@@ -22,9 +24,11 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 | <span style="font-weight: 400;">`4`</span> | Challenge Drop  | Unused.                                      |
 | <span style="font-weight: 400;">`5`</span> | Log             | Take no action other than logging the event. |
 
+
+
 ## Deprecated fields for internal Cloudflare use
 
 The values of these fields are subject to change by Cloudflare at any time and are irrelevant for customer data analysis:
 
-- WAFFlags
-- WAFMatchedVar
+* WAFFlags
+* WAFMatchedVar
diff --git a/src/content/docs/magic-transit/about.mdx b/src/content/docs/magic-transit/about.mdx
index dc0086ba6a2fe2a..d24ff959ee90edf 100644
--- a/src/content/docs/magic-transit/about.mdx
+++ b/src/content/docs/magic-transit/about.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: About Magic Transit
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Magic Transit is a network security and performance solution that offers Distributed Denial of Service ([DDoS](/ddos-protection/)) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 
diff --git a/src/content/docs/magic-transit/alerts.mdx b/src/content/docs/magic-transit/alerts.mdx
index f8cadf60286d59c..c0c7de7a4836d78 100644
--- a/src/content/docs/magic-transit/alerts.mdx
+++ b/src/content/docs/magic-transit/alerts.mdx
@@ -6,9 +6,10 @@ products:
   - magic-transit
 sidebar:
   order: 14
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your network.
 
diff --git a/src/content/docs/magic-transit/analytics/index.mdx b/src/content/docs/magic-transit/analytics/index.mdx
index dfe4e5e0295bb7b..04ca8e61b7d11ce 100644
--- a/src/content/docs/magic-transit/analytics/index.mdx
+++ b/src/content/docs/magic-transit/analytics/index.mdx
@@ -13,14 +13,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
 		traceRoutes: "/magic-transit/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/",
-	}}
-/>
+		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
+		 }}
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/analytics/network-analytics.mdx b/src/content/docs/magic-transit/analytics/network-analytics.mdx
index c872539c3620160..14e7c6f5b8cbfd3 100644
--- a/src/content/docs/magic-transit/analytics/network-analytics.mdx
+++ b/src/content/docs/magic-transit/analytics/network-analytics.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit Network Analytics
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Magic Transit",
+		magicWord: "Magic Transit"
 	}}
 />
diff --git a/src/content/docs/magic-transit/analytics/packet-captures.mdx b/src/content/docs/magic-transit/analytics/packet-captures.mdx
index 8ef49043b64053d..0dd8a83c52fb2da 100644
--- a/src/content/docs/magic-transit/analytics/packet-captures.mdx
+++ b/src/content/docs/magic-transit/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
index 6f46709874eb1bc..e20b8573ade07d3 100644
--- a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
+++ b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
@@ -11,10 +11,9 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Magic Transit" }}
 />
diff --git a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
index 347e8ce8854d5cd..ec044cf25d36e9c 100644
--- a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
@@ -11,10 +11,8 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Magic Transit" }}
-/>
+	params={{ productName: "Magic Transit" }} />
diff --git a/src/content/docs/magic-transit/changelog.mdx b/src/content/docs/magic-transit/changelog.mdx
index f3d81cf0accb7be..df426867ae71afe 100644
--- a/src/content/docs/magic-transit/changelog.mdx
+++ b/src/content/docs/magic-transit/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/magic-transit/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="magic-transit"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="magic-transit" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/magic-transit/cloudflare-ips.mdx b/src/content/docs/magic-transit/cloudflare-ips.mdx
index 9812bcc56adb708..4ee1316b242c1ab 100644
--- a/src/content/docs/magic-transit/cloudflare-ips.mdx
+++ b/src/content/docs/magic-transit/cloudflare-ips.mdx
@@ -8,26 +8,23 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="magic-transit/cloudflare-ips"
 	product="networking-services"
 	params={{
 		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		mtLpStaticRoute:
-			"/magic-transit/how-to/configure-routes/#configure-static-routes",
-		mtLpBgpPeering:
-			"/magic-transit/how-to/configure-routes/#configure-bgp-routes",
-	}}
-/>
+		mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
+		mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
+		}} />
 
 ## Check your Cloudflare IPs
 
 <Render
-	file="check-leased-ips"
+  file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "Anycast IPs for Magic Transit",
+		product: "Anycast IPs for Magic Transit"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/get-started.mdx b/src/content/docs/magic-transit/get-started.mdx
index 8efc46ed319d06b..eec224e8dbadd55 100644
--- a/src/content/docs/magic-transit/get-started.mdx
+++ b/src/content/docs/magic-transit/get-started.mdx
@@ -10,10 +10,6 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/get-started"
-	product="networking-services"
-	params={{ magicWord: "Magic Transit" }}
-/>
+<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Magic Transit" }} />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/glossary.mdx b/src/content/docs/magic-transit/glossary.mdx
index 089812e9c6ecd3e..b14631d9375bd84 100644
--- a/src/content/docs/magic-transit/glossary.mdx
+++ b/src/content/docs/magic-transit/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Magic Transit documentation.
 products:
   - magic-transit
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Magic Transit documentation.
 
diff --git a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
index e8f018925c30330..ec7bc738458e71d 100644
--- a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
+++ b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
@@ -8,15 +8,7 @@ sidebar:
   order: 5
 ---
 
-import {
-	APIRequest,
-	DashButton,
-	Details,
-	GlossaryTooltip,
-	Render,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { APIRequest, DashButton, Details, GlossaryTooltip, Render, Tabs, TabItem } from "~/components"
 
 ## Onboard prefixes
 
@@ -75,11 +67,11 @@ You should only use one control method per prefix at any given time. Mixing mult
 Create a [POST request](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/create/) to add a BGP prefix. For example:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
-	method="POST"
-	json={{
-		cidr: "192.0.2.0/24",
-	}}
+  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
+  method="POST"
+  json={{
+    "cidr": "192.0.2.0/24"
+  }}
 />
 
 ### Advertise or withdraw a BGP prefix
@@ -125,7 +117,7 @@ Refer to [Safely withdraw a BYOIP prefix](#safely-withdraw-a-byoip-prefix) for m
 
 ### Delete an IP prefix
 
-You can only delete a prefix with an _Unapproved_ status. To delete prefixes with a different status, contact your administrator or account manager.
+You can only delete a prefix with an *Unapproved* status. To delete prefixes with a different status, contact your administrator or account manager.
 
 1. Go to the **Routes** page.
 
@@ -145,11 +137,11 @@ BGP has different mechanisms to control route priorities which are set by the pe
 Refer to the following example for how to prepend AS13335 three times to a BGP prefix:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-	method="PATCH"
-	json={{
-		asn_prepend_count: 3,
-	}}
+path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+method="PATCH"
+json={{
+	"asn_prepend_count": 3
+}}
 />
 
 AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once provides a smoother traffic migration and minimizes packet loss during a change of provider.
@@ -163,6 +155,8 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
 - **Introduce new provider**: You begin advertising the same prefix from your alternate provider with a standard (shorter) `AS_PATH`.
 - **Final state**: External networks now receive two advertisements: the prepended route through Cloudflare and the non-prepended route through your new provider. The external network will select a path based on its BGP policy rules.
 
+
+
 :::caution
 Cloudflare's internal network enforces local preference for traffic delivery to Magic Transit, even if a more specific or shorter path route is available on the public Internet. Withdraw the prefix from Cloudflare to avoid delivery of Cloudflare-sourced traffic over Magic Transit. This preference is local to our internal network and does not impact the route decision process of other networks.
 
@@ -171,32 +165,27 @@ For example, if you have a CDN zone with a Magic Transit-protected origin that i
 
 ## Safely withdraw a BYOIP prefix
 
-<Render
-	file="magic-transit/safely-withdraw-byoip-prefix"
-	product="networking-services"
-/>
+<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
 
 ## BGP control to Magic Transit Virtual Network routing table
 
 ### Automatically announce and withdraw anycast-based Magic BGP routes
 
 If you use CNI with Dataplane v2, GRE or IPsec tunnels, you can:
-
 - Automatically withdraw your prefixes from Cloudflare's global edge infrastructure when you withdraw all matching BGP learned prefixes from the Magic Transit Virtual Network routing table.
 - Automatically advertise your prefixes through Cloudflare's global edge infrastructure when you have at least one matching BGP learned prefix in the Magic Transit Virtual Network routing table.
 
 To enable automatic global announcement and withdrawal, enable this feature on the BGP prefix using the [Addressing API](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/edit/). For example:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-	method="PATCH"
-	json={{
-		auto_advertise_withdraw: true,
-	}}
+  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+  method="PATCH"
+  json={{
+    "auto_advertise_withdraw": true
+  }}
 />
 
 Once you configure this for a BGP prefix, Cloudflare applies the following logic:
-
 - If there are no BGP routes in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare withdraws the BGP prefix.
 - If there is at least one BGP route in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare announces the BGP prefix.
 
@@ -327,10 +316,7 @@ If you use CNI with Dataplane v2, GRE or IPsec tunnels to on-ramp your network t
 
 Magic Transit supports both static routing and BGP to steer traffic from Cloudflare's network to your configured off-ramps (GRE tunnels, IPsec tunnels, or CNI). Cloudflare does not currently support advertisement of routes for traffic engineering purposes. As a best practice to reduce last-hop latency, consider scoping your routes regionally.
 
-<Render
-	file="reference/traffic-steering-region-codes"
-	product="networking-services"
-/>
+<Render file="reference/traffic-steering-region-codes" product="networking-services" />
 
 The default setting for static route regions is **All Regions**. Configure scoping for your traffic in the **Region code** section when [adding](/magic-transit/how-to/configure-routes/#create-a-static-route) or [editing](/magic-transit/how-to/configure-routes/#edit-a-static-route) a static route.
 
diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx
index 0dfce207230821b..c3053044b8b28e3 100644
--- a/src/content/docs/magic-transit/how-to/configure-routes.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx
@@ -11,7 +11,7 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -21,16 +21,12 @@ import { Render } from "~/components";
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT:
-			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table",
+		routingTableName: "Magic Transit Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
index ab317378e353ddc..af1eee331945798 100644
--- a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
@@ -14,31 +14,23 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
index 7910debecdaac0e..ccf843678ccbee2 100644
--- a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
+++ b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
@@ -7,6 +7,6 @@ head: []
 description: You can determine which users have, or do not have, configuration edit access for Magic products.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="magic-user-role" product="networking-services" />
diff --git a/src/content/docs/magic-transit/how-to/index.mdx b/src/content/docs/magic-transit/how-to/index.mdx
index a80f260452a9bd5..962bded34f466cd 100644
--- a/src/content/docs/magic-transit/how-to/index.mdx
+++ b/src/content/docs/magic-transit/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
index 95d51e29e27e30d..b08bce6faedffc0 100644
--- a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
@@ -8,9 +8,6 @@ sidebar:
   order: 6
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/safely-withdraw-byoip-prefix"
-	product="networking-services"
-/>
+<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-flow.mdx b/src/content/docs/magic-transit/network-flow.mdx
index d77808bebde34fe..9af74ab7d1573b5 100644
--- a/src/content/docs/magic-transit/network-flow.mdx
+++ b/src/content/docs/magic-transit/network-flow.mdx
@@ -6,15 +6,16 @@ products:
   - magic-transit
 sidebar:
   order: 10
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
 	}}
 />
diff --git a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
index 7218ba148af08d2..99ee9ad379632a8 100644
--- a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
@@ -14,13 +14,11 @@ import { Render } from "~/components";
 	file="tunnel-health/check-tunnel-healthchecks-dash"
 	product="networking-services"
 	params={{
-		dashInfo:
-			"The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
+		dashInfo: "The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
 		graphQL: "/magic-transit/analytics/query-tunnel-health/",
-		notificationsPath:
-			"[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
+		notificationsPath: "[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/magic-transit/analytics/network-analytics/",
+		networkAnalytics: "/magic-transit/analytics/network-analytics/"
 	}}
 />
 
@@ -28,7 +26,7 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
 />
 
@@ -36,4 +34,4 @@ import { Render } from "~/components";
 
 If you received a tunnel health alert but are unsure whether it affects your traffic, refer to [Troubleshoot connectivity](/magic-transit/troubleshooting/connectivity/) to determine whether the alert is relevant.
 
-If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
+If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
index 32dcf34acba8937..d606ec4dcd288b1 100644
--- a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation:
-			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/index.mdx b/src/content/docs/magic-transit/network-health/index.mdx
index ac18e64e89dac4c..909456bebc21630 100644
--- a/src/content/docs/magic-transit/network-health/index.mdx
+++ b/src/content/docs/magic-transit/network-health/index.mdx
@@ -8,23 +8,23 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Magic Transit uses health check probes to determine the status of tunnels. Cloudflare uses this information to steer traffic through the best available route and warn you about potential issues with a tunnel. Service-level indicators (SLIs) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [How Cloudflare calculates tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/) for more information about SLIs and SLOs.
 
 There are two types of health checks available: endpoint and tunnel health checks.
 
-- Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
+ - Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
 
-  Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
+	Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
 
-  During onboarding, you specify IP addresses to configure endpoint health checks.
+	During onboarding, you specify IP addresses to configure endpoint health checks.
 
 - Tunnel health checks monitor the status of the tunnels that route traffic from Cloudflare to your origin network. Magic Transit relies on health checks to steer traffic to the best available routes.
 
-  During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
+	During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
 
-  You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
+	You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
 
 Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/) for a deep dive into the different types of health checks, what they do, and how they work.
 
@@ -32,10 +32,10 @@ Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/)
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
 />
 
 Refer to the following pages for details on how to use the various network health checks available.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
index 3fedb7f8c2cb1a3..b734e7357208bff 100644
--- a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
+++ b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
@@ -14,7 +14,7 @@ tags:
   - ICMP
 ---
 
-import { CURL, Render, DashButton } from "~/components";
+import { CURL, Render, DashButton } from '~/components';
 
 Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
 
@@ -43,35 +43,32 @@ Refer to the [API documentation](/api/resources/diagnostics/subresources/endpoin
 <Render file="account-id-api-key" product="networking-services" />
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-	method="POST"
-	json={{
-		check_type: "icmp",
-		endpoint: "8.31.160.1",
-		name: "Datacenter 1 - primary",
-	}}
+  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+  method="POST"
+  json={{
+    "check_type": "icmp",
+    "endpoint": "8.31.160.1",
+    "name": "Datacenter 1 - primary"
+  }}
 />
 
 ```json output
 {
-	"result": {
-		"id": "<HEALTH_CHECK_ID>",
-		"check_type": "icmp",
-		"endpoint": "8.31.160.1",
-		"name": "Datacenter 1 - primary"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+    "result": {
+        "id": "<HEALTH_CHECK_ID>",
+        "check_type": "icmp",
+        "endpoint": "8.31.160.1",
+        "name": "Datacenter 1 - primary"
+    },
+    "success": true,
+    "errors": [],
+    "messages": []
 }
 ```
 
 ## Query endpoint health checks with GraphQL
 
-<Render
-	file="graphql/query-magic-transit-endpoint-health-checks"
-	product="networking-services"
-/>
+<Render file="graphql/query-magic-transit-endpoint-health-checks" product="networking-services" />
 
 ## Configure alerts for endpoint health checks
 
@@ -80,23 +77,23 @@ You can set up alerts to be notified when the state of your endpoint's health is
 1. Make a `GET` request to get a list of IDs for all of the endpoint health checks configured:
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-	method="GET"
+  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<HEALTH_CHECK_ID>",
-			"check_type": "icmp",
-			"endpoint": "8.31.160.1",
-			"name": "Datacenter 1 - primary"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+    "result": [
+        {
+            "id": "<HEALTH_CHECK_ID>",
+            "check_type": "icmp",
+            "endpoint": "8.31.160.1",
+            "name": "Datacenter 1 - primary"
+        }
+    ],
+    "success": true,
+    "errors": [],
+    "messages": []
 }
 ```
 
@@ -106,13 +103,13 @@ You can set up alerts to be notified when the state of your endpoint's health is
 <DashButton url="/?to=/:account/notifications" />
 
 4. Select **Add**.
-5. From the drop-down menu, select _Magic Transit_.
+5. From the drop-down menu, select *Magic Transit*.
 6. Select **Magic Endpoint Health Check Alert**.
 7. Provide a name for your new notification and optionally provide a description.
-8. In the _Service Level Objective (SLO)_ drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
-   - **High** - 99%
-   - **Medium** - 98%
-   - **Low** - 97%
+8. In the *Service Level Objective (SLO)* drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
+	- **High** - 99%
+	- **Medium** - 98%
+	- **Low** - 97%
 9. In the drop-down menu below SLOs, select the `id` value that matches the `id` you got through the API in step 1. This `id` should match the endpoint health check you want to get notifications for.
 10. Select your preferred notification method (such as email or webhooks).
 11. Select **Save**.
diff --git a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
index cc01a8092fae660..5abf823c7864447 100644
--- a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
@@ -17,8 +17,7 @@ import { Render } from "~/components";
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",
-		addTunnelsPath:
-			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels"
 	}}
 />
 
@@ -26,6 +25,6 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-interconnect.mdx b/src/content/docs/magic-transit/network-interconnect.mdx
index d9cb97232b3510b..44619ba947f13ef 100644
--- a/src/content/docs/magic-transit/network-interconnect.mdx
+++ b/src/content/docs/magic-transit/network-interconnect.mdx
@@ -13,4 +13,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" />
+<Render file="magic-cni" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/on-demand.mdx b/src/content/docs/magic-transit/on-demand.mdx
index 75c387b34768ef6..019f50728fcda3c 100644
--- a/src/content/docs/magic-transit/on-demand.mdx
+++ b/src/content/docs/magic-transit/on-demand.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit on-demand
+
 ---
 
 If you have access to the Magic Transit on-demand option, you can [configure prefix advertisement](/byoip/concepts/dynamic-advertisement/best-practices/#configure-dynamic-advertisement) from the **IP Prefixes** page in your Cloudflare account home or through the [Cloudflare API](/api/resources/addressing/subresources/prefixes/subresources/advertisement_status/methods/edit/).
diff --git a/src/content/docs/magic-transit/partners/index.mdx b/src/content/docs/magic-transit/partners/index.mdx
index 6ee348692df331a..bfd05db0b774788 100644
--- a/src/content/docs/magic-transit/partners/index.mdx
+++ b/src/content/docs/magic-transit/partners/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 15
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
index 535769eb632525c..7bc128098d8f68c 100644
--- a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
+++ b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
@@ -18,8 +18,7 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
-		productPath:
-			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		productPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
index dc972d88c678590..6b1bfa5d9f79f7f 100644
--- a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
@@ -22,13 +22,12 @@ import { Render } from "~/components";
 		mssURL: "/magic-transit/get-started/#set-maximum-segment-size",
 		productURL: "/magic-transit/reference/anti-replay-protection/",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		magicWord: "Magic Transit",
+		magicWord: "Magic Transit"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/magic-transit/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index f9fbf42cffa7459..1fba89abfb6a2f8 100644
--- a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,12 +8,9 @@ sidebar:
   order: 9
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down",
-	}}
+	params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down" }}
 />
diff --git a/src/content/docs/magic-transit/reference/index.mdx b/src/content/docs/magic-transit/reference/index.mdx
index fe0a8581aa501bb..19ff0a30a962cbc 100644
--- a/src/content/docs/magic-transit/reference/index.mdx
+++ b/src/content/docs/magic-transit/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 16
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/reference/mtu-mss.mdx b/src/content/docs/magic-transit/reference/mtu-mss.mdx
index c35b312d04d675d..aea2b11b3a8ca3a 100644
--- a/src/content/docs/magic-transit/reference/mtu-mss.mdx
+++ b/src/content/docs/magic-transit/reference/mtu-mss.mdx
@@ -20,6 +20,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
-		productName: "Magic Transit",
-	}}
+		productName: "Magic Transit"
+		}}
 />
diff --git a/src/content/docs/magic-transit/reference/traffic-steering.mdx b/src/content/docs/magic-transit/reference/traffic-steering.mdx
index 3864fa3d06c3f68..6343ed66f6690f6 100644
--- a/src/content/docs/magic-transit/reference/traffic-steering.mdx
+++ b/src/content/docs/magic-transit/reference/traffic-steering.mdx
@@ -22,8 +22,7 @@ import { Render } from "~/components";
 		routingTableName: "Magic Transit Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
index 9f4b6435299ad5a..cc8c425a16b925c 100644
--- a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
@@ -20,12 +20,11 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		addTunnels: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		changeHealthCheckRate: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
 		staticRoutes: "/magic-transit/how-to/configure-routes/",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
index bc19d9e2ed3a087..ff5293328e0537b 100644
--- a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 		productName: "Magic Transit",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
 		routingBgpLink: "/magic-transit/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/index.mdx b/src/content/docs/magic-transit/troubleshooting/index.mdx
index 24dc284181dfdf0..6487eea738df77b 100644
--- a/src/content/docs/magic-transit/troubleshooting/index.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/index.mdx
@@ -12,6 +12,6 @@ tags:
   - Debugging
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
index 3ad6b0cbb6091ce..bacfef32c5f77a3 100644
--- a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
@@ -12,17 +12,15 @@ tags:
   - Logging
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		mtuMssLink: "/magic-transit/reference/mtu-mss/",
+		mtuMssLink: "/magic-transit/reference/mtu-mss/"
 	}}
 />
 
@@ -31,7 +29,6 @@ import { Render } from "~/components";
 Some customer routers cannot fully disable IPsec anti-replay protection, which is required for optimal Magic Transit operation (packet reordering at the Cloudflare edge can otherwise trigger false drops).
 
 **If your router does not support disabling anti-replay:**
-
 1. Check whether your router supports configuring a **replay window size**. Setting this to `0` is equivalent to disabling anti-replay protection.
 2. If neither disabling anti-replay nor setting the window size to `0` is supported, **the router cannot be used as a Magic Transit IPsec on-ramp**. Consider using a GRE tunnel or Cloudflare Network Interconnect (CNI) instead.
 
@@ -44,3 +41,4 @@ If your ISP is blocking these response packets, health checks will fail even whe
 **Symptom:** Health checks fail but application traffic flows normally through the tunnel.
 
 **Resolution:** Switch to bidirectional health checks, which send both the probe and the response through the tunnel. Bidirectional health checks require egress traffic to be turned on for your Magic Transit configuration. For more information, refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/).
+
diff --git a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
index 43b9bb867569e75..d207cbb1af0bab8 100644
--- a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
@@ -11,15 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "Magic Transit",
-		productName: "Magic Transit",
-		trafficSteeringLink:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink: "/magic-transit/how-to/configure-routes/",
-		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "Magic Transit",
+    productName: "Magic Transit",
+    trafficSteeringLink: "/magic-transit/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/magic-transit/how-to/configure-routes/",
+    tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
index 747fc6d131cd7b6..1f0887e6040a0f8 100644
--- a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
@@ -14,20 +14,17 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Magic Transit",
-		healthCheckDefault: "_Unidirectional_ (direct server return)",
-		tunnelsConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
-		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Magic Transit",
+    healthCheckDefault: "_Unidirectional_ (direct server return)",
+    tunnelsConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+    antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/moq/feature-matrix.mdx b/src/content/docs/moq/feature-matrix.mdx
index 92148c292bc4988..200715e6e3a4ba2 100644
--- a/src/content/docs/moq/feature-matrix.mdx
+++ b/src/content/docs/moq/feature-matrix.mdx
@@ -3,80 +3,81 @@ pcx_content_type: get-started
 title: MoQ Feature Matrix
 sidebar:
   order: 18
+
 ---
 
 ## Draft-14 Messages
 
 ### Supported
 
-| Message                            | Support | Relevant specification                                                                           |
-| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_CANCEL           | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_OK               | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_ERROR            | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_OK                         | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE                  | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_DONE             | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_DONE                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_OK                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_CANCEL | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ### Unsupported
 
-| Message                   | Support | Relevant specification                                                                           |
-| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| GOAWAY                    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| MAX_REQUEST_ID            | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| REQUESTS_BLOCKED          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_ERROR             | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH                     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_OK                  | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_ERROR               | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_ERROR        | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE       | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_OK    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_ERROR | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE_NAMESPACE     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| GOAWAY | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| MAX_REQUEST_ID | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| REQUESTS_BLOCKED | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_CANCEL | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ## Draft-07 Messages
 
 ### Supported
 
-| Message                            | Support | Relevant specification                                                                           |
-| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| ANNOUNCE_OK                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_ERROR                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_CANCEL                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS_REQUEST               | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE                           | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNANNOUNCE                         | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_DONE                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| MAX_SUBSCRIBE_ID                   | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| ANNOUNCE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_CANCEL | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS_REQUEST | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_DONE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| MAX_SUBSCRIBE_ID | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
 
 ### Unsupported
 
-| Message                   | Support | Relevant specification                                                                           |
-| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| GOAWAY                    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES       | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_OK    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_ERROR | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE_ANNOUNCES     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH                     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_OK                  | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_ERROR               | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| GOAWAY | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_CANCEL | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
diff --git a/src/content/docs/moq/index.mdx b/src/content/docs/moq/index.mdx
index d02f8400089cf48..838ca1c7516741e 100644
--- a/src/content/docs/moq/index.mdx
+++ b/src/content/docs/moq/index.mdx
@@ -22,7 +22,7 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Frequently Asked Questions
 
-- What about Safari?
+* What about Safari?
 
   Safari does not yet have fully functional WebTransport support. Apple never publicly commits to timelines for new features like this. However, Apple has indicated their [intent to support WebTransport](https://github.com/WebKit/standards-positions/issues/18#issuecomment-1495890122). An Apple employee is even a co-author of the [WebTransport over HTTP/3](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/) draft. Since Safari 18.4 (2025-03-31), an early (not yet fully functional) implementation of the WebTransport API has been available for testing behind a developer-mode / advanced settings feature flag (including on iOS).
 
@@ -30,12 +30,12 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Known Issues
 
-- Extra Subgroup header field
-
-  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits.
+* Extra Subgroup header field
 
+  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits. 
+  
   In section 7.3.1, `draft-ietf-moq-transport-07` [specifies](https://www.ietf.org/archive/id/draft-ietf-moq-transport-07.html#section-7.3.1):
-
+  
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Track Alias (i),
@@ -44,9 +44,8 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-
+  
   Whereas our implementation expects and produces:
-
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Subscribe ID (i),
@@ -56,5 +55,5 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-
+  
   This was erroroneously left over from a previous draft version and will be fixed in a future release. Thank you to [@yuki-uchida](https://github.com/yuki-uchida) for reporting.
diff --git a/src/content/docs/multi-cloud-networking/changelog.mdx b/src/content/docs/multi-cloud-networking/changelog.mdx
index 4bbf7ded14ca757..4374533a030deb1 100644
--- a/src/content/docs/multi-cloud-networking/changelog.mdx
+++ b/src/content/docs/multi-cloud-networking/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/multi-cloud-networking/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="multi-cloud-networking"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="multi-cloud-networking" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-11-21
 
diff --git a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
index d20a8425820479e..d388a38c069f08b 100644
--- a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
+++ b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
@@ -6,15 +6,12 @@ products:
 title: Cloud on-ramps
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="routing/mcn-cloudflare-wan-on-ramps"
+<Render file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
-	params={{
-		mwanAccount:
-			"Have a Cloudflare WAN account. Contact your account team to learn more.",
-	}}
+	params={{ mwanAccount: "Have a Cloudflare WAN account. Contact your account team to learn more." }}
 />
diff --git a/src/content/docs/multi-cloud-networking/get-started.mdx b/src/content/docs/multi-cloud-networking/get-started.mdx
index ef3448467003242..04c91b1108e2aa5 100644
--- a/src/content/docs/multi-cloud-networking/get-started.mdx
+++ b/src/content/docs/multi-cloud-networking/get-started.mdx
@@ -25,7 +25,7 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 1. Go to the **Cloud integrations (beta)** page.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **AWS integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -38,29 +38,29 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 ```json
 {
-	"Version": "2012-10-17",
-	"Statement": [
-		{
-			"Effect": "Allow",
-			"Action": [
-				"ec2:AcceptTransitGatewayPeeringAttachment",
-				"ec2:CreateTransitGatewayPeeringAttachment",
-				"ec2:DeleteTransitGatewayPeeringAttachment",
-				"ec2:DescribeRegions",
-				"ec2:DescribeTransitGatewayPeeringAttachments",
-				"ec2:RejectTransitGatewayPeeringAttachment",
-				"ec2:GetManagedPrefixListEntries",
-				"ec2:CreateManagedPrefixList",
-				"ec2:ModifyManagedPrefixList",
-				"ec2:DeleteManagedPrefixList",
-				"ec2:CreateTransitGatewayPrefixListReference",
-				"ec2:DeleteTransitGatewayPrefixListReference",
-				"ec2:GetTransitGatewayPrefixListReferences",
-				"ec2:ModifyTransitGatewayPrefixListReference"
-			],
-			"Resource": "*"
-		}
-	]
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "ec2:AcceptTransitGatewayPeeringAttachment",
+                "ec2:CreateTransitGatewayPeeringAttachment",
+                "ec2:DeleteTransitGatewayPeeringAttachment",
+                "ec2:DescribeRegions",
+                "ec2:DescribeTransitGatewayPeeringAttachments",
+                "ec2:RejectTransitGatewayPeeringAttachment",
+                "ec2:GetManagedPrefixListEntries",
+                "ec2:CreateManagedPrefixList",
+                "ec2:ModifyManagedPrefixList",
+                "ec2:DeleteManagedPrefixList",
+                "ec2:CreateTransitGatewayPrefixListReference",
+                "ec2:DeleteTransitGatewayPrefixListReference",
+                "ec2:GetTransitGatewayPrefixListReferences",
+                "ec2:ModifyTransitGatewayPrefixListReference"
+            ],
+            "Resource": "*"
+        }
+    ]
 }
 ```
 
@@ -69,15 +69,15 @@ Once Cloudflare has the credentials required to access your cloud environments,
 1. Create an [AWS role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html) with the following settings:
    - **Trusted entity type**: Select **Custom trust policy**, and paste the custom trust policy returned by the Cloudflare dashboard.
    - **Permissions**: Add the IAM policy you created in the previous step, along with these AWS-managed policies:
-     - `NetworkAdministrator`
-     - `AmazonEC2ReadOnlyAccess`
-     - `AmazonVPCReadOnlyAccess`
-     - `IAMReadOnlyAccess`
+      - `NetworkAdministrator`
+      - `AmazonEC2ReadOnlyAccess`
+      - `AmazonVPCReadOnlyAccess`
+      - `IAMReadOnlyAccess`
    - **ARN**: Copy the ARN for your newly created user.
 
    :::note
-   The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-   :::
+	 The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+	 :::
 
 2. Select **I authorize Cloudflare to access my AWS account.**
 3. Select **Authorize**.
@@ -92,7 +92,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Azure integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -115,8 +115,8 @@ Multi-Cloud Networking does not support personal Microsoft accounts. Sign in usi
 6. In **Verify account ownership**, [add the tags displayed in the Cloudflare dashboard](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources-portal).
 
    :::note
-   The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-   :::
+	 The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+	 :::
 
 7. Select **I authorize Cloudflare to access my Azure account.** If your account does not have administrator privileges, you may need to pass this link to an account that has administrator privileges.
 8. Select **Authorize**.
@@ -131,7 +131,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Google integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -142,8 +142,8 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. Create a new [GCP service account](https://cloud.google.com/iam/docs/service-accounts-create) in your **Google account** > **GCP Console** > **IAM & Admin** > **Service Accounts**.
 2. Grant the new service account these roles:
-   - `Compute Network Admin`
-   - `Compute Viewer`
+	- `Compute Network Admin`
+	- `Compute Viewer`
 3. Under **IAM & Admin** > **Service Accounts**, select the service account you just created, and navigate to the **Permissions** tab.
 4. Grant the **Service Account Token Creator** role to our bot account to allow it to impersonate this service account. Learn how to grant a specific role [in Google's documentation](https://cloud.google.com/iam/docs/manage-access-service-accounts#grant-single-role):
    - `mcn-integrations-bot-prod@mcn-gcp-01.iam.gserviceaccount.com`
@@ -163,4 +163,4 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 - [Set up Cloudflare WAN](/multi-cloud-networking/cloud-on-ramps/) as an on-ramp to your cloud.
 - [Manage resources](/multi-cloud-networking/manage-resources/) found by Multi-Cloud Networking.
-- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
+- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
\ No newline at end of file
diff --git a/src/content/docs/multi-cloud-networking/manage-resources.mdx b/src/content/docs/multi-cloud-networking/manage-resources.mdx
index b9eb3e0bc385769..4307d7b9da2de5c 100644
--- a/src/content/docs/multi-cloud-networking/manage-resources.mdx
+++ b/src/content/docs/multi-cloud-networking/manage-resources.mdx
@@ -6,6 +6,7 @@ products:
 title: Manage resources
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,7 +19,7 @@ To browse the resources in your catalog:
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select a resource to inspect its details.
@@ -29,7 +30,7 @@ You can change which cloud account the integration is linked to or delete the in
 
 1. Go to **Cloud integrations**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select your integration > **Edit**.
 3. In **Linked account details**, select **Link integration to a different cloud account**.
@@ -42,7 +43,7 @@ You can download a JSON file containing metadata and configuration for all your
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select **Download catalog**.
diff --git a/src/content/docs/multi-cloud-networking/reference.mdx b/src/content/docs/multi-cloud-networking/reference.mdx
index 16d0b78776c4c47..8c37c24b0eabb74 100644
--- a/src/content/docs/multi-cloud-networking/reference.mdx
+++ b/src/content/docs/multi-cloud-networking/reference.mdx
@@ -6,6 +6,7 @@ products:
 title: Reference
 sidebar:
   order: 5
+
 ---
 
 Refer to this page for details about how Cloudflare orchestrates VPN connectivity to your cloud networks.
diff --git a/src/content/docs/network-error-logging/get-started.mdx b/src/content/docs/network-error-logging/get-started.mdx
index 2b07fd6d29a8e84..e211ba22e5e901a 100644
--- a/src/content/docs/network-error-logging/get-started.mdx
+++ b/src/content/docs/network-error-logging/get-started.mdx
@@ -6,6 +6,7 @@ products:
   - network-error-logging
 tags:
   - Logging
+
 ---
 
 import { DashButton } from "~/components";
@@ -16,7 +17,7 @@ To enable Network Error Logging for Free and Pro zones:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **Network** and locate **Network Error Logging Monitoring**.
 3. Select the toggle to enable Network Error Logging.
diff --git a/src/content/docs/network-error-logging/how-to.mdx b/src/content/docs/network-error-logging/how-to.mdx
index 74f33f4e7eeadff..6aac695c1d00025 100644
--- a/src/content/docs/network-error-logging/how-to.mdx
+++ b/src/content/docs/network-error-logging/how-to.mdx
@@ -11,20 +11,21 @@ head:
 description: NEL reports show you why a request failed, the country a request
   failed from, and last mile network a request failed from, and the likely
   intended Cloudflare data center.
+
 ---
 
 import { DashButton } from "~/components";
 
 Use NEL reports to view information such as:
 
-- Why a request failed
-- The country a request failed from
-- The last mile network a request failed from
-- The Cloudflare data center the request was most likely meant for
+* Why a request failed
+* The country a request failed from
+* The last mile network a request failed from
+* The Cloudflare data center the request was most likely meant for
 
 1. Log in to your Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **Analytics & Logs** > **Edge Reachability**.
 
diff --git a/src/content/docs/network-error-logging/index.mdx b/src/content/docs/network-error-logging/index.mdx
index 9f1acd04e344ba5..b712cac7782fb54 100644
--- a/src/content/docs/network-error-logging/index.mdx
+++ b/src/content/docs/network-error-logging/index.mdx
@@ -34,21 +34,21 @@ A sample Network Error Report payload appears as follows:
 
 ```json
 {
-	"age": 20,
-	"type": "network-error",
-	"url": "https://example.com/previous-page",
-	"body": {
-		"elapsed_time": 18,
-		"method": "POST",
-		"phase": "dns",
-		"protocol": "http/1.1",
-		"referrer": "https://example.com/previous-page",
-		"sampling_fraction": 1,
-		"server_ip": "",
-		"status_code": 0,
-		"type": "dns.name_not_resolved",
-		"url": "https://example-host.com/"
-	}
+  "age": 20,
+  "type": "network-error",
+  "url": "https://example.com/previous-page",
+  "body": {
+    "elapsed_time": 18,
+    "method": "POST",
+    "phase": "dns",
+    "protocol": "http/1.1",
+    "referrer": "https://example.com/previous-page",
+    "sampling_fraction": 1,
+    "server_ip": "",
+    "status_code": 0,
+    "type": "dns.name_not_resolved",
+    "url": "https://example-host.com/"
+  }
 }
 ```
 
@@ -56,9 +56,9 @@ A sample Network Error Report payload appears as follows:
 
 Cloudflare uses geolocation lookups to extract the following information from every client IP in a NEL report:
 
-- Client ASN
-- Client country
-- Client metro area
+* Client ASN
+* Client country
+* Client metro area
 
 Cloudflare uses internal lookups to associate the above data with a customer domain and customer account.
 
@@ -67,10 +67,9 @@ Cloudflare does not store any PII or user-specific data, and any IP data is only
 The client IP address is only stored in volatile memory for the lifetime of the request to Cloudflare’s NEL endpoint (order of milliseconds) and is dropped immediately after the request completes. Cloudflare does not log the client IP address anywhere in the Network Error Logging pipeline.
 
 NEL reports contain information about the end user's network conditions, which could be considered sensitive. Cloudflare takes privacy seriously and has implemented the following safeguards:
-
-- Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
-- Reports do not contain personally identifiable information (PII).
-- Customers can opt out of having their end users consume the NEL headers using one of the following methods:
+* Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
+* Reports do not contain personally identifiable information (PII).
+* Customers can opt out of having their end users consume the NEL headers using one of the following methods:
   1. **Self-service (Zone setting)** — Use the dashboard toggle or API (`PATCH /zones/{zone_id}/settings/nel`) to disable NEL for your zone. This can be re-enabled by any zone administrator at any time.
   2. **Permanent opt-out via Support** — Contact Cloudflare support to have the `nel___enable` feature flag disabled at the product level. This prevents NEL from being enabled on your zone entirely and cannot be reversed by zone administrators.
-     For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
+For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
diff --git a/src/content/docs/network-flow/api.mdx b/src/content/docs/network-flow/api.mdx
index 86093e48a9529bf..abedf0335eb08a4 100644
--- a/src/content/docs/network-flow/api.mdx
+++ b/src/content/docs/network-flow/api.mdx
@@ -6,8 +6,9 @@ products:
   - network-flow
 sidebar:
   order: 9
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="mnm/api" product="networking-services" />
+<Render file="mnm/api" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/changelog.mdx b/src/content/docs/network-flow/changelog.mdx
index c0a384cb7ba3378..b94beaa04726a51 100644
--- a/src/content/docs/network-flow/changelog.mdx
+++ b/src/content/docs/network-flow/changelog.mdx
@@ -13,7 +13,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-flow/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="network-flow"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="network-flow" hideEntry="2024-06-16-cloudflare-one"/>
diff --git a/src/content/docs/network-flow/cloud-flow-logs.mdx b/src/content/docs/network-flow/cloud-flow-logs.mdx
index 1f7b9357b839a4c..b3b71aa0230d535 100644
--- a/src/content/docs/network-flow/cloud-flow-logs.mdx
+++ b/src/content/docs/network-flow/cloud-flow-logs.mdx
@@ -16,4 +16,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/cloud-flow-logs" product="networking-services" />
+<Render file="mnm/cloud-flow-logs" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/faq.mdx b/src/content/docs/network-flow/faq.mdx
index 7f18175619785c3..83e76018f873f71 100644
--- a/src/content/docs/network-flow/faq.mdx
+++ b/src/content/docs/network-flow/faq.mdx
@@ -11,6 +11,6 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="mnm/faqs" product="networking-services" />
+<Render file="mnm/faqs" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/get-started.mdx b/src/content/docs/network-flow/get-started.mdx
index 4c52c7365d5e149..8129f8e3bb7ce5a 100644
--- a/src/content/docs/network-flow/get-started.mdx
+++ b/src/content/docs/network-flow/get-started.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/get-started" product="networking-services" />
+<Render file="mnm/get-started" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/glossary.mdx b/src/content/docs/network-flow/glossary.mdx
index 3000aa1c392cf88..560fd3884273263 100644
--- a/src/content/docs/network-flow/glossary.mdx
+++ b/src/content/docs/network-flow/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - network-flow
 sidebar:
   order: 10
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Network Flow (formerly Magic Network Monitoring) documentation.
 
diff --git a/src/content/docs/network-flow/magic-transit-integration.mdx b/src/content/docs/network-flow/magic-transit-integration.mdx
index 0b4ac3859f62b97..8defa83ac2a41fc 100644
--- a/src/content/docs/network-flow/magic-transit-integration.mdx
+++ b/src/content/docs/network-flow/magic-transit-integration.mdx
@@ -8,15 +8,16 @@ tags:
   - Integration
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
 	}}
 />
diff --git a/src/content/docs/network-flow/network-flow-free.mdx b/src/content/docs/network-flow/network-flow-free.mdx
index 645bf56f6cb3a17..ca7198f7f03d8fe 100644
--- a/src/content/docs/network-flow/network-flow-free.mdx
+++ b/src/content/docs/network-flow/network-flow-free.mdx
@@ -11,6 +11,6 @@ head:
     content: Network Flow free version
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="mnm/network-flow-free" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/index.mdx b/src/content/docs/network-flow/routers/index.mdx
index 476c0017b240362..dc7bb414eb48ca9 100644
--- a/src/content/docs/network-flow/routers/index.mdx
+++ b/src/content/docs/network-flow/routers/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
index 58e65c53add4e60..3d1f2222d0b7878 100644
--- a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
+++ b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
@@ -11,8 +11,9 @@ sidebar:
 head: []
 description: A step-by-step configuration guide for exporting NetFlow or IPFIX
   data to Cloudflare's network.
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
+<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
index b8cd99b68ae977e..82158fe7ad97cf0 100644
--- a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
+++ b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
@@ -9,6 +9,7 @@ sidebar:
   order: 2
 head: []
 description: The best sampling rate recommendations for your network's traffic volume.
+
 ---
 
 import { Render } from "~/components";
@@ -16,4 +17,4 @@ import { Render } from "~/components";
 <Render
 	file="mnm/routers/recommended-sampling-rate"
 	product="networking-services"
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/sflow-config.mdx b/src/content/docs/network-flow/routers/sflow-config.mdx
index 5b7ba843d316df0..ee37c4c868a8ac4 100644
--- a/src/content/docs/network-flow/routers/sflow-config.mdx
+++ b/src/content/docs/network-flow/routers/sflow-config.mdx
@@ -14,4 +14,7 @@ description: A step-by-step configuration guide for exporting sFlow data to
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/sflow-config" product="networking-services" />
+<Render
+	file="mnm/routers/sflow-config"
+	product="networking-services"
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/supported-routers.mdx b/src/content/docs/network-flow/routers/supported-routers.mdx
index 410865594728185..45a57d81dc9d9a9 100644
--- a/src/content/docs/network-flow/routers/supported-routers.mdx
+++ b/src/content/docs/network-flow/routers/supported-routers.mdx
@@ -13,4 +13,7 @@ description: A list of open source, NetFlow, and sFlow routers.
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/supported-routers" product="networking-services" />
+<Render
+	file="mnm/routers/supported-routers"
+	product="networking-services"
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/index.mdx b/src/content/docs/network-flow/rules/index.mdx
index ff541e592e5802a..ef9d83a02553c40 100644
--- a/src/content/docs/network-flow/rules/index.mdx
+++ b/src/content/docs/network-flow/rules/index.mdx
@@ -14,3 +14,4 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="mnm/rules/overview" product="networking-services" />
+
diff --git a/src/content/docs/network-flow/rules/rule-notifications.mdx b/src/content/docs/network-flow/rules/rule-notifications.mdx
index cfc447c89cb41dd..0f85c34f0e1fd3d 100644
--- a/src/content/docs/network-flow/rules/rule-notifications.mdx
+++ b/src/content/docs/network-flow/rules/rule-notifications.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/rule-notifications" product="networking-services" />
+<Render file="mnm/rules/rule-notifications" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
index 34d38296b6570d4..9dfff3f061f5c5d 100644
--- a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
+++ b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
+<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/static-threshold.mdx b/src/content/docs/network-flow/rules/static-threshold.mdx
index fa5fca21e7cef6f..172ca611aa68db2 100644
--- a/src/content/docs/network-flow/rules/static-threshold.mdx
+++ b/src/content/docs/network-flow/rules/static-threshold.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/static-threshold" product="networking-services" />
+<Render file="mnm/rules/static-threshold" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
index d43167ed7936fd7..0b0bb68e1ebbc8d 100644
--- a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
+++ b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
@@ -15,4 +15,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
+<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
index 8b86d643dd5ade2..f7562708d10bd0d 100644
--- a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
+++ b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
@@ -19,7 +19,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/tutorials/encrypt-network-flow-data"
-	product="networking-services"
-/>
+<Render file="mnm/tutorials/encrypt-network-flow-data" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
index 26f062040cac4f3..00c00c094490f32 100644
--- a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
+++ b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
@@ -20,4 +20,4 @@ import { Render } from "~/components";
 
 <Render file="mnm/tutorials/graphql-analytics" product="networking-services" />
 
-<Render file="case-sensitivity-note" product="analytics" />
+<Render file="case-sensitivity-note" product="analytics" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/index.mdx b/src/content/docs/network-flow/tutorials/index.mdx
index a13ee6bc966bfd7..8fae75e32ca4f24 100644
--- a/src/content/docs/network-flow/tutorials/index.mdx
+++ b/src/content/docs/network-flow/tutorials/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/network-interconnect/changelog.mdx b/src/content/docs/network-interconnect/changelog.mdx
index 64c3877fd409947..5b15e2c668e23f3 100644
--- a/src/content/docs/network-interconnect/changelog.mdx
+++ b/src/content/docs/network-interconnect/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-interconnect/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="network-interconnect"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="network-interconnect" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx
index daba42777661fd5..16c0b376aa76fb9 100644
--- a/src/content/docs/network-interconnect/get-started.mdx
+++ b/src/content/docs/network-interconnect/get-started.mdx
@@ -11,7 +11,7 @@ tags:
   - GCP
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 :::note[BGP architecture and resiliency]
 CNI supports BGP peering with the Cloudflare Virtual Network routing table. BGP over CNI is in closed beta and is not currently available to new customers. If you are interested in BGP peering over CNI, contact your account team.
@@ -26,7 +26,7 @@ For detailed information about BGP architecture, Edge Resiliency Mode, and route
 Your Cloudflare account team determines CNI eligibility and port availability. Notably:
 
 - CNI ports are currently offered at no charge to Enterprise customers.
-  - Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
+	- Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
 - CNI is available at select Cloudflare data centers:
   - The type of Dataplane offered in that location will determine specifications of the supported connection, such as the MTU.
   - The diversity offered in the location will vary.
@@ -43,37 +43,36 @@ To peer with Cloudflare, advertise prefixes with a prefix length of `/24` or sho
 ## Technical specifications
 
 - **Supported port types**:
-  - **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
-  - **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
+	- **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
+	- **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
 - **Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection.
 - **IP addressing:** All CNI connections and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare.
 - **VLAN support:**
-  - **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
-  - **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
+	- **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
+	- **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
 - **MTU considerations:**
-  - **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
-  - **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
+	- **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
+	- **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
 - **Bidirectional Forwarding Detection (BFD):**
-  - **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
-  - **Dataplane v2**: Not yet supported.
+	- **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
+	- **Dataplane v2**: Not yet supported.
 - **Link Aggregation Control Protocol (LACP)**:
-  - **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
-  - **Dataplane v2**: Not yet supported. Use ECMP instead.
+	- **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
+	- **Dataplane v2**: Not yet supported. Use ECMP instead.
 
 ## Performance characteristics
 
 The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration.
 
-| Direction (use case)                            | 10G Circuit                                                                                     | 100G Circuit                                                                                    |
-| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| From Cloudflare to Customer (all use cases)     | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
-| From Customer to Cloudflare (peering use case)  | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
-| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection |
+| Direction (use case) | 10G Circuit | 100G Circuit |
+|----------------------|-------------|--------------|
+| From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection  |
 
 ## Service expectations
 
 Consider the following service levels when planning your deployment:
-
 - **No Formal SLA**:
   - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms).
   - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel.
@@ -99,8 +98,8 @@ The process of provisioning a CNI typically takes two to four weeks, depending o
 1. **Submit request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process.
 2. **Review configuration**: For the v1 Dataplane, the Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document. For the v2 Dataplane, this step is not necessary.
 3. **Order connection**:
-   - For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
-   - For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
+	- For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
+	- For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
 4. **Configure network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document.
 5. **Test and verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and, if applicable, verify that the BGP session can be established.
 6. Enable tunnel health checks for [Magic Transit](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) and/or [Cloudflare WAN](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels).
@@ -143,7 +142,7 @@ To connect to AWS Direct Connect:
 
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select **Create an interconnect**.
 3. Under **Cloud Interconnect**, select **Create new**.
@@ -163,5 +162,9 @@ You can now select **View interconnects** for a list of all interconnects on you
 
 After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect:
 
-- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP: - Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths. - Note that routes advertised by BGP from GCP Cloud Router will be ignored.
-- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router: - Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes). - Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
+- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP:
+		- Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths.
+		- Note that routes advertised by BGP from GCP Cloud Router will be ignored.
+- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router:
+		- Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes).
+		- Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
diff --git a/src/content/docs/network-interconnect/index.mdx b/src/content/docs/network-interconnect/index.mdx
index 9b63e926dc454eb..80bde6dd95d9bb1 100644
--- a/src/content/docs/network-interconnect/index.mdx
+++ b/src/content/docs/network-interconnect/index.mdx
@@ -11,10 +11,10 @@ head:
     content: Overview
 ---
 
-import { Description, Plan, RelatedProduct, Render } from "~/components";
+import { Description, Plan, RelatedProduct, Render } from "~/components"
 
 <Description>
-	Connect your network infrastructure directly to Cloudflare
+Connect your network infrastructure directly to Cloudflare
 </Description>
 
 <Plan type="enterprise" />
@@ -24,7 +24,6 @@ Cloudflare Network Interconnect (CNI) allows you to connect your network infrast
 ## Benefits
 
 Enterprises use CNI to achieve:
-
 - **Enhanced Performance**: Gain lower latency and more consistent network throughput.
 - **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet.
 
@@ -32,16 +31,15 @@ Enterprises use CNI to achieve:
 
 Choose the connection type for your infrastructure and operational needs.
 
-|                    | Direct Interconnect                                                                                                     | Partner Interconnect                                                                                       | Cloud Interconnect                                                                                                                              |
-| ------------------ | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Port type**      | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners.            | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare.             |
-| **Operations**     | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment.                    | Your partner manages the connection logistics, often through a software-defined networking portal.         | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
-| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability.                     | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services.                                    |
+| | Direct Interconnect | Partner Interconnect | Cloud Interconnect |
+| --- | --- | --- | --- |
+| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare. |
+| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
+| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. |
 
 ## Dataplane
 
 Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection:
-
 - **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports Generic Routing Encapsulation (GRE) tunnels for connecting with the Cloudflare Virtual Network, with optional GRE-less delivery for Magic Transit Direct Server Return.
 - **Dataplane v2**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte Maximum Transmission Unit (MTU) bidirectionally.
 
@@ -57,25 +55,15 @@ To protect against a single point of failure, it is critical to design your CNI
 
 Refer to [Service Expectations](/network-interconnect/get-started/#service-expectations) for more information.
 
----
+***
 
 ## Related products
 
-<RelatedProduct
-	header="Magic Transit"
-	href="/magic-transit/"
-	product="magic-transit"
->
-	Magic Transit is a network security and performance solution that offers
-	Distributed Denial of Service (DDoS) protection, traffic acceleration, and
-	more for on-premise, cloud-hosted, and hybrid networks.
+<RelatedProduct header="Magic Transit" href="/magic-transit/" product="magic-transit">
+Magic Transit is a network security and performance solution that offers Distributed Denial of Service (DDoS) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 </RelatedProduct>
 
-<RelatedProduct
-	header="Cloudflare WAN"
-	href="/cloudflare-wan/"
-	product="cloudflare-wan"
->
-	Improve security and performance for your entire corporate network, reducing
-	cost and operation complexity.
+<RelatedProduct header="Cloudflare WAN" href="/cloudflare-wan/" product="cloudflare-wan">
+Improve security and performance for your entire corporate network, reducing cost and operation complexity.
 </RelatedProduct>
+
diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
index 1b73b9485ee8d93..861b447fcad7132 100644
--- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
+++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 5
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 ## Monitoring
 
@@ -22,18 +22,17 @@ The Status column displays three statuses:
 - **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
 - **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The **Pending** status will disappear after the customer completes the cross-connect and status moves to **Active**.
 
+
 ## Alerts (v1 dataplane only)
 
 You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
 
 **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only.
-
 - You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections.
 - You will be notified if the details of a scheduled maintenance change or if it is canceled.
 - For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments.
 
 **Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network.
-
 - You will be warned about potentially disruptive maintenance at the PoP level.
 - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these.
 - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits.
@@ -44,7 +43,7 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
+	<DashButton url="/?to=/:account/notifications" />
 
 2. Select **Add**.
 3. From the product drop-down menu, select _Cloudflare Network Interconnect_.
@@ -56,10 +55,9 @@ You can configure notifications for upcoming CNI maintenance events using the No
 ### Enable Cloudflare Status Maintenance Notification
 
 First, identify the PoP code for your CNI circuit:
-
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select the CNI you want to enable notifications for.
 3. In the menu that appears, note the Data Center code (for example, `gru-b`).
diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx
index 2cf09f24173e915..a94aa4bae85717a 100644
--- a/src/content/docs/network-interconnect/operational-guidance.mdx
+++ b/src/content/docs/network-interconnect/operational-guidance.mdx
@@ -52,4 +52,4 @@ If no system-wide problems are reported, gather the following information before
 - **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
 - **Physical Layer**: Light levels of the CNI link (if applicable).
 - **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
-- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
+- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
\ No newline at end of file
diff --git a/src/content/docs/network/index.mdx b/src/content/docs/network/index.mdx
index e9f9e837d33f580..e6d3e05e3d5a401 100644
--- a/src/content/docs/network/index.mdx
+++ b/src/content/docs/network/index.mdx
@@ -11,48 +11,38 @@ products:
   - network
 ---
 
-import { Description, Feature, Plan, RelatedProduct } from "~/components";
+import { Description, Feature, Plan, RelatedProduct } from "~/components"
 
-<Description>Manage network settings for your website.</Description>
+<Description>
+Manage network settings for your website.
+</Description>
 
 <Plan type="all" />
 
----
+***
 
 ## Features
 
 <Feature header="IP Geolocation" href="/network/ip-geolocation/">
-	Include the country code of the visitor location with all requests to your
-	website.
+Include the country code of the visitor location with all requests to your website.
 </Feature>
 
 <Feature header="IPv6 Compatibility" href="/network/ipv6-compatibility/">
-	Enable IPv6 support and gateway.
+Enable IPv6 support and gateway.
 </Feature>
 
 <Feature header="WebSockets" href="/network/websockets/">
-	Allow WebSockets connections to your origin server.
+Allow WebSockets connections to your origin server.
 </Feature>
 
----
+***
 
 ## Related products
 
-<RelatedProduct
-	header="China Network"
-	href="/china-network/"
-	product="china-network"
->
-	The Cloudflare China Network is a package of selected Cloudflare’s performance
-	and security products running on data centers located in mainland China and
-	operated by Cloudflare’s partner JD Cloud.
+<RelatedProduct header="China Network" href="/china-network/" product="china-network">
+The Cloudflare China Network is a package of selected Cloudflare’s performance and security products running on data centers located in mainland China and operated by Cloudflare’s partner JD Cloud.
 </RelatedProduct>
 
-<RelatedProduct
-	header="Managed Transforms"
-	href="/rules/transform/managed-transforms/"
-	product="rules"
->
-	Managed Transforms allow you to perform common adjustments to HTTP request and
-	response headers with the click of a button.
+<RelatedProduct header="Managed Transforms" href="/rules/transform/managed-transforms/" product="rules">
+Managed Transforms allow you to perform common adjustments to HTTP request and response headers with the click of a button.
 </RelatedProduct>
diff --git a/src/content/docs/network/websockets.mdx b/src/content/docs/network/websockets.mdx
index dbb08884e375a08..77ff14da6b28963 100644
--- a/src/content/docs/network/websockets.mdx
+++ b/src/content/docs/network/websockets.mdx
@@ -89,3 +89,4 @@ Cloudflare will close a WebSocket connection when no data is transmitted in eith
 ### Session affinity for load-balanced WebSocket origins
 
 If your WebSocket origin is behind a Cloudflare Load Balancer, turn on **Session affinity** to ensure all requests from the same client are routed to the same origin server. Without session affinity, a WebSocket reconnect may land on a different origin that does not have the session state.
+
diff --git a/src/content/docs/notifications/get-started/configure-pagerduty.mdx b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
index a4e84b32aedd7cb..fef6662b17543be 100644
--- a/src/content/docs/notifications/get-started/configure-pagerduty.mdx
+++ b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
@@ -12,7 +12,7 @@ import { DashButton } from "~/components";
 
 :::note
 
-This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/).
+This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/). 
 :::
 
 Cloudflare’s Notification service supports routing notifications to PagerDuty. By sending notifications to PagerDuty you can leverage the same service definitions and escalation paths that you would for other third-party services that you connect to PagerDuty.
@@ -23,15 +23,14 @@ To use PagerDuty as a connected service, you must [sign up for a PagerDuty accou
 
 :::note
 
-According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner.
+According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner. 
 :::
 
 ## Connect PagerDuty to a Cloudflare account
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **Connect**.
 4. Log in to your [PagerDuty account](https://www.pagerduty.com/) to connect it to your Cloudflare account.
@@ -49,9 +48,8 @@ Disconnecting PagerDuty will disable any notifications being sent to PagerDuty w
 If other delivery destinations were selected, then those notifications will still be routed as configured.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **View** on the PagerDuty service you want to disconnect.
 4. Select **Disconnect** > **Confirm**.
diff --git a/src/content/docs/notifications/get-started/index.mdx b/src/content/docs/notifications/get-started/index.mdx
index 04bb4821e3116e6..4e0d0a3fba2ffc8 100644
--- a/src/content/docs/notifications/get-started/index.mdx
+++ b/src/content/docs/notifications/get-started/index.mdx
@@ -36,9 +36,8 @@ This guide will help you create, edit, test, or delete notifications using the C
 You can create a notification via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Select **Add**.
 3. On the notification you want to create, choose **Select**.
 4. Name the notification.
@@ -46,7 +45,7 @@ You can create a notification via the Cloudflare dashboard.
 
 :::note
 
-Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks.
+Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks. 
 :::
 
 6. (Optional) Specify any additional options for the notification, if required. For example, some notifications require that you select one or more domains or services.
@@ -59,9 +58,8 @@ The browser will navigate back to the list of notifications, where the new notif
 You can edit existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to modify, select **Edit**.
 3. Make your changes as needed and select **Save**.
 
@@ -72,9 +70,8 @@ The browser will navigate back to the list of notifications.
 You can delete or disable existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to disable, select the **Enabled** toggle. To delete it, select **Delete**.
 
 ### Mute a notification
@@ -82,9 +79,8 @@ You can delete or disable existing Notifications via the Cloudflare dashboard.
 You can temporarily mute a notification to stop receiving alerts for a set period of time. Muted notifications create a silence that automatically expires after the specified duration.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to mute, select **Mute**.
 3. Select a duration preset (**1h**, **12h**, or **24h**), or set a custom time range using the **Start Time** and **End Time** fields.
 4. Select **Save**.
@@ -99,9 +95,8 @@ While a notification is muted, alerts that would have triggered it are suppresse
 You can view, edit, or delete existing silences from the **Silences** tab.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Select the **Silences** tab.
 3. To create a new silence, select **Add**. To modify an existing silence, select **Edit**. To remove a silence before it expires, select **Delete**.
 
diff --git a/src/content/docs/notifications/index.mdx b/src/content/docs/notifications/index.mdx
index 829b5519eba15c2..a1d547bdecee617 100644
--- a/src/content/docs/notifications/index.mdx
+++ b/src/content/docs/notifications/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: overview
 title: Notifications
 sidebar:
@@ -8,7 +9,7 @@ products:
 description: Configure alerts for your Cloudflare account.
 ---
 
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
 <Plan type="all" />
 
@@ -28,4 +29,4 @@ The availability of delivery methods like PagerDuty and webhooks in Free or Prof
 
 - PagerDuty is available in zones on a Free/Professional plan if your Cloudflare account has at least one zone in a Business plan (or higher).
 - Webhooks are available in zones on a Free plan if your Cloudflare account has at least one zone in a Professional plan (or higher).
-  :::
+:::
diff --git a/src/content/docs/notifications/notification-available.mdx b/src/content/docs/notifications/notification-available.mdx
index b41697b971f7c3d..6712c3aee831957 100644
--- a/src/content/docs/notifications/notification-available.mdx
+++ b/src/content/docs/notifications/notification-available.mdx
@@ -8,7 +8,7 @@ products:
 description: Browse available notification types by product.
 ---
 
-import { AvailableNotifications } from "~/components";
+import { AvailableNotifications } from "~/components"
 
 Available Notifications depend on your Cloudflare plan. Cloudflare offers a variety of Notifications for our products and services, such as [Billing](/billing/), [Denial of Service protection](/ddos-protection/), [Magic Transit](/magic-transit/), and [SSL/TLS](/ssl/).
 
diff --git a/src/content/docs/notifications/notification-history.mdx b/src/content/docs/notifications/notification-history.mdx
index 4bbc04b274ecd9b..57b80f9b1bd7402 100644
--- a/src/content/docs/notifications/notification-history.mdx
+++ b/src/content/docs/notifications/notification-history.mdx
@@ -32,5 +32,5 @@ Notification History is available on all plans. The amount of history clients ha
 
 :::note
 
-Customers will not be able to access Notification History from before 2021-10-11.
+Customers will not be able to access Notification History from before 2021-10-11. 
 :::
diff --git a/src/content/docs/notifications/reference/index.mdx b/src/content/docs/notifications/reference/index.mdx
index 6d7a07ae02df9e1..38d8d2becb9beec 100644
--- a/src/content/docs/notifications/reference/index.mdx
+++ b/src/content/docs/notifications/reference/index.mdx
@@ -10,7 +10,7 @@ products:
 description: Reference information for Cloudflare Notifications.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Notifications:
 
diff --git a/src/content/docs/notifications/reference/traffic-alerts.mdx b/src/content/docs/notifications/reference/traffic-alerts.mdx
index 42527aee765f7ca..9741d0e2d2dcc30 100644
--- a/src/content/docs/notifications/reference/traffic-alerts.mdx
+++ b/src/content/docs/notifications/reference/traffic-alerts.mdx
@@ -28,7 +28,7 @@ This approach does not work as well for low traffic zones. If there are not many
 
 ### Service-level objective recommendations
 
-SLOs determine the sensitivity of an alert. For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
+SLOs determine the sensitivity of an alert.  For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
 
 Your traffic levels impact the accuracy of high sensitivity alerts. High sensitivity alerts are not recommended for zones with low traffic since the Error Rate alert will likely alert on every 5xx error. However, If you have a zone that has very high traffic (hundreds of millions of requests per day), High Sensitivity SLOs are recommended.
 
diff --git a/src/content/docs/pages/configuration/api.mdx b/src/content/docs/pages/configuration/api.mdx
index d813c97fe6c9adf..5f49f4fd6a70543 100644
--- a/src/content/docs/pages/configuration/api.mdx
+++ b/src/content/docs/pages/configuration/api.mdx
@@ -19,7 +19,6 @@ To create an API token:
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
-
 2. Select **Create Token**.
 3. You can go to **Edit Cloudflare Workers** template > **Use template** or go to **Create Custom Token** > **Get started**. If you create a custom token, you will need to make sure to add the **Cloudflare Pages** permission with **Edit** access.
 
diff --git a/src/content/docs/pages/configuration/build-caching.mdx b/src/content/docs/pages/configuration/build-caching.mdx
index 436cc3e60e5c6d3..3cd918887d0b276 100644
--- a/src/content/docs/pages/configuration/build-caching.mdx
+++ b/src/content/docs/pages/configuration/build-caching.mdx
@@ -37,15 +37,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                            |
-| ---------- | --------------------------------------------- |
-| Astro      | `node_modules/.astro`                         |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
-| Eleventy   | `.cache`                                      |
-| Gatsby     | `.cache`, `public`                            |
-| Next.js    | `.next/cache`                                 |
-| Nuxt       | `node_modules/.cache/nuxt`                    |
-| SvelteKit  | `node_modules/.cache/imagetools`              |
+| Framework  | Directories cached                                          |
+| ---------- | ----------------------------------------------------------- |
+| Astro      | `node_modules/.astro`                                       |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
+| Eleventy   | `.cache`                                                    |
+| Gatsby     | `.cache`, `public`                                          |
+| Next.js    | `.next/cache`                                               |
+| Nuxt       | `node_modules/.cache/nuxt`                                  |
+| SvelteKit  | `node_modules/.cache/imagetools`                            |
 
 ### Limits
 
diff --git a/src/content/docs/pages/configuration/build-image.mdx b/src/content/docs/pages/configuration/build-image.mdx
index e4596187251d055..d2c7006afebcc61 100644
--- a/src/content/docs/pages/configuration/build-image.mdx
+++ b/src/content/docs/pages/configuration/build-image.mdx
@@ -88,7 +88,6 @@ To migrate to this new version, configure your Pages project settings in the das
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Deployments** > **All deployments** > and select the latest version.
 
@@ -110,6 +109,7 @@ Cloudflare Pages builds are run in a [gVisor](https://gvisor.dev/docs/) containe
 
 <PagesBuildEnvironment />
 
+
 ## Build Image Policy
 
 ### Build Image Version Deprecation
@@ -131,7 +131,6 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
-
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -141,7 +140,6 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
-
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
 - **Plan for migration** when you receive update notices
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
\ No newline at end of file
diff --git a/src/content/docs/pages/configuration/deploy-hooks.mdx b/src/content/docs/pages/configuration/deploy-hooks.mdx
index b40eb6d48f435bb..66418eb9f810990 100644
--- a/src/content/docs/pages/configuration/deploy-hooks.mdx
+++ b/src/content/docs/pages/configuration/deploy-hooks.mdx
@@ -19,7 +19,6 @@ To create a Deploy Hook:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Builds** and select **Add deploy hook** to start configuration.
 
diff --git a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
index 46e064b4a0d8063..377ecb62654d209 100644
--- a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
+++ b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
@@ -68,7 +68,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Import from an existing Git repository**.
 3. Select your new GitHub repository.
 4. In the **Set up builds and deployments**, set `npm run build` as the **Build command**, and `dist` as the **Build output directory**.
diff --git a/src/content/docs/pages/functions/api-reference.mdx b/src/content/docs/pages/functions/api-reference.mdx
index 9a521a8c592d30b..e15d8a9a4aa0a15 100644
--- a/src/content/docs/pages/functions/api-reference.mdx
+++ b/src/content/docs/pages/functions/api-reference.mdx
@@ -18,27 +18,35 @@ The following methods can be used to configure your Pages Function.
 The `onRequest` method will be called unless a more specific `onRequestVerb` method is exported. For example, if both `onRequest` and `onRequestGet` are exported, only `onRequestGet` will be called for `GET` requests.
 
 - <code>onRequest(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all requests no matter what the request method is, as long as no specific request verb (like one of the methods below) is exported.
 
 - <code>onRequestGet(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `GET` requests.
 
 - <code>onRequestPost(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `POST` requests.
 
 - <code>onRequestPatch(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `PATCH` requests.
 
 - <code>onRequestPut(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `PUT` requests.
 
 - <code>onRequestDelete(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `DELETE` requests.
 
 - <code>onRequestHead(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `HEAD` requests.
 
 - <code>onRequestOptions(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `OPTIONS` requests.
 
 ### `env.ASSETS.fetch()`
diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx
index 4b1016b85d127f3..b6f53b59192f9eb 100644
--- a/src/content/docs/pages/functions/bindings.mdx
+++ b/src/content/docs/pages/functions/bindings.mdx
@@ -14,13 +14,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	TabItem,
-	Tabs,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, TabItem, Tabs, WranglerConfig, DashButton } from "~/components";
 
 A [binding](/workers/runtime-apis/bindings/) enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like [KV](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2](/r2/), and [D1](/d1/). You can set bindings for both production and preview environments.
 
@@ -43,7 +37,6 @@ To configure a KV namespace binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **KV namespace**.
 4. Give your binding a name under **Variable name**.
@@ -104,7 +97,6 @@ To configure a Durable Object binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Durable Object**.
 4. Give your binding a name under **Variable name**.
@@ -169,7 +161,6 @@ To configure a R2 bucket binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **R2 bucket**.
 4. Give your binding a name under **Variable name**.
@@ -242,7 +233,6 @@ To configure a D1 database binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add**> **D1 database bindings**.
 4. Give your binding a name under **Variable name**.
@@ -319,13 +309,12 @@ To configure a Vectorize index binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 3. Select your Pages project > **Settings**.
 4. Go to **Bindings** > **Add** > **Vectorize index**.
 5. Give your binding a name under **Variable name**.
 6. Under **Vectorize index**, select your desired Vectorize index.
-7. Redeploy your project for the binding to take effect.
+8. Redeploy your project for the binding to take effect.
 
 ### Use Vectorize index bindings
 
@@ -460,7 +449,6 @@ To configure a Workers AI binding via the Cloudflare dashboard:
 1. Go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings**.
 3. Select your Pages environment > **Bindings** > **Add** > **Workers AI**.
 4. Give your binding a name under **Variable name**.
@@ -534,7 +522,6 @@ To configure a Service binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Service binding**.
 4. Give your binding a name under **Variable name**.
@@ -599,7 +586,6 @@ To configure a queue producer binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Queue**.
 4. Give your binding a name under **Variable name**.
@@ -676,7 +662,6 @@ To configure a Hyperdrive binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Hyperdrive**.
 4. Give your binding a name under **Variable name**.
@@ -750,7 +735,6 @@ To configure an Analytics Engine binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Analytics engine**.
 4. Give your binding a name under **Variable name**.
@@ -812,7 +796,6 @@ To configure an environment variable via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add** .
 4. After setting a variable name and value, select **Save**.
@@ -871,7 +854,6 @@ To add secrets to your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add**.
 4. Set a variable name and value.
diff --git a/src/content/docs/pages/functions/examples/ab-testing.mdx b/src/content/docs/pages/functions/examples/ab-testing.mdx
index 125a99e100cd193..96d45b37cd3e0f8 100644
--- a/src/content/docs/pages/functions/examples/ab-testing.mdx
+++ b/src/content/docs/pages/functions/examples/ab-testing.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up an A/B test by controlling what page is served based on cookies.
   This version supports passing the request through to test and control on the
   origin.
diff --git a/src/content/docs/pages/functions/examples/cors-headers.mdx b/src/content/docs/pages/functions/examples/cors-headers.mdx
index 48c58ea881e153c..0011928013bbd10 100644
--- a/src/content/docs/pages/functions/examples/cors-headers.mdx
+++ b/src/content/docs/pages/functions/examples/cors-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: A Pages Functions for appending CORS headers.
 tags:
   - Headers
diff --git a/src/content/docs/pages/functions/examples/index.mdx b/src/content/docs/pages/functions/examples/index.mdx
index a7ae43643a007ce..26f22f52cf8ceca 100644
--- a/src/content/docs/pages/functions/examples/index.mdx
+++ b/src/content/docs/pages/functions/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: Examples
 description: Code examples for common Pages Functions use cases.
diff --git a/src/content/docs/pages/functions/metrics.mdx b/src/content/docs/pages/functions/metrics.mdx
index 802ad2e19dd4a42..12b285087c355a7 100644
--- a/src/content/docs/pages/functions/metrics.mdx
+++ b/src/content/docs/pages/functions/metrics.mdx
@@ -19,7 +19,6 @@ Functions metrics aggregate request data for an individual Pages project. To vie
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. In your Pages project, select **Functions Metrics**.
 
diff --git a/src/content/docs/pages/functions/plugins/community-plugins.mdx b/src/content/docs/pages/functions/plugins/community-plugins.mdx
index 69d5080b51c5b6f..164f24737e7be5c 100644
--- a/src/content/docs/pages/functions/plugins/community-plugins.mdx
+++ b/src/content/docs/pages/functions/plugins/community-plugins.mdx
@@ -17,6 +17,7 @@ The following are some of the community-maintained Pages Plugins. If you have cr
 - [proxyflare-for-pages](https://github.com/flaregun-net/proxyflare-for-pages)
 
   Move traffic around your Cloudflare Pages domain with ease. Proxyflare is a reverse-proxy that enables you to:
+
   - Port forward, redirect, and reroute HTTP and websocket traffic anywhere on the Internet.
   - Mount an entire website on a subpath (for example, `mysite.com/docs`) on your apex domain.
   - Serve static text (like `robots.txt` and other structured metadata) from any endpoint.
diff --git a/src/content/docs/pages/get-started/c3.mdx b/src/content/docs/pages/get-started/c3.mdx
index c88153d094feefa..68c5c783012edad 100644
--- a/src/content/docs/pages/get-started/c3.mdx
+++ b/src/content/docs/pages/get-started/c3.mdx
@@ -10,6 +10,7 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 products:
   - pages
+
 ---
 
 import {
@@ -84,24 +85,30 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
 />
 
 - `DIRECTORY` <Type text="string" /> <MetaInfo text="optional" />
+
   - The directory where the application should be created. The name of the application is taken from the directory name.
 
 - `NESTED ARGS..` <Type text="string[]" /> <MetaInfo text="optional" />
+
   - CLI arguments to pass to eventual third party CLIs C3 might invoke (in the case of full-stack applications).
 
 - `--category` <Type text="string" /> <MetaInfo text="optional" />
+
   - The kind of templates that should be created.
 
   - The possible values for this option are:
+
     - `hello-world`: Hello World example
     - `web-framework`: Framework Starter
     - `demo`: Application Starter
     - `remote-template`: Template from a GitHub repo
 
 - `--type` <Type text="string" /> <MetaInfo text="optional" />
+
   - The type of application that should be created.
 
   - The possible values for this option are:
+
     - `hello-world`: A basic "Hello World" Cloudflare Worker.
     - `hello-world-durable-object`: A [Durable Object](/durable-objects/) and a Worker to communicate with it.
     - `common`: A Cloudflare Worker which implements a common example of routing/proxying functionalities.
@@ -111,9 +118,11 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `pre-existing`: Fetch a Worker initialized from the Cloudflare dashboard.
 
 - `--framework` <Type text="string" /> <MetaInfo text="optional" />
+
   - The type of framework to use to create a web application (when using this option, `--type` is ignored).
 
   - The possible values for this option are:
+
     - `angular`
     - `astro`
     - `docusaurus`
@@ -130,9 +139,11 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `vue`
 
 - `--template` <Type text="string" /> <MetaInfo text="optional" />
+
   - Create a new project via an external template hosted in a git repository
 
   - The value for this option may be specified as any of the following:
+
     - `user/repo`
     - `git@github.com:user/repo`
     - `https://github.com/user/repo`
@@ -145,6 +156,7 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the `degit` [docs](https://github.com/Rich-Harris/degit) for more details.
 
     At a minimum, templates must contain the following:
+
     - `package.json`
     - [Wrangler configuration file](/pages/functions/wrangler-configuration/)
     - `src/` containing a worker script referenced from the Wrangler configuration file
@@ -152,40 +164,51 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the [templates folder](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare/templates) of this repo for more examples.
 
 - `--deploy` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Deploy your application after it has been created.
 
 - `--lang` <Type text="string" /> <MetaInfo text="(default: ts) optional" />
+
   - The programming language of the template.
 
   - The possible values for this option are:
+
     - `ts`
     - `js`
     - `python`
 
 - `--ts` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Use TypeScript in your application. Deprecated. Use `--lang=ts` instead.
 
 - `--git` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Initialize a local git repository for your application.
 
 - `--open` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Open with your browser the deployed application (this option is ignored if the application is not deployed).
 
 - `--existing-script` <Type text="string" /> <MetaInfo text="optional" />
+
   - The name of an existing Cloudflare Workers script to clone locally. When using this option, `--type` is coerced to `pre-existing`.
 
   - When `--existing-script` is specified, `deploy` will be ignored.
 
 - `-y`, `--accept-defaults` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Use all the default C3 options each can also be overridden by specifying it.
 
 - `--auto-update` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Automatically uses the latest version of C3.
 
 - `-v`, `--version` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Show version number.
 
 - `-h`, `--help` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Show a help message.
 
 :::note
diff --git a/src/content/docs/pages/get-started/direct-upload.mdx b/src/content/docs/pages/get-started/direct-upload.mdx
index f1f5228ef2053d0..9f7252898b5ddba 100644
--- a/src/content/docs/pages/get-started/direct-upload.mdx
+++ b/src/content/docs/pages/get-started/direct-upload.mdx
@@ -8,6 +8,7 @@ description: Upload your prebuilt assets to Pages and deploy them via the
   Wrangler CLI or the Cloudflare dashboard.
 products:
   - pages
+
 ---
 
 import { Render, DashButton } from "~/components";
@@ -127,7 +128,6 @@ To deploy with drag and drop:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Get started** > **Drag and drop your files**.
 3. Enter your project name in the provided field and drag and drop your assets.
 4. Select **Deploy site**.
diff --git a/src/content/docs/pages/get-started/git-integration.mdx b/src/content/docs/pages/get-started/git-integration.mdx
index 5ac8218965fb505..3b6cb58789596cb 100644
--- a/src/content/docs/pages/get-started/git-integration.mdx
+++ b/src/content/docs/pages/get-started/git-integration.mdx
@@ -7,6 +7,7 @@ head:
 description: Connect your Git provider to Pages.
 products:
   - pages
+
 ---
 
 import { Details, Render } from "~/components";
diff --git a/src/content/docs/pages/get-started/index.mdx b/src/content/docs/pages/get-started/index.mdx
index e76af4b0b86da8a..328bd28a8396d9c 100644
--- a/src/content/docs/pages/get-started/index.mdx
+++ b/src/content/docs/pages/get-started/index.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 2
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/add-custom-http-headers.mdx b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
index 7dedb62c0645ef1..3402e5e5a66d4e5 100644
--- a/src/content/docs/pages/how-to/add-custom-http-headers.mdx
+++ b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
@@ -5,6 +5,7 @@ description: Customize HTTP headers on Cloudflare Pages using a Workers function
 products:
   - pages
   - workers
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/docs/pages/how-to/build-commands-branches.mdx b/src/content/docs/pages/how-to/build-commands-branches.mdx
index d91423afb902d99..46ab3dfafb2d1a1 100644
--- a/src/content/docs/pages/how-to/build-commands-branches.mdx
+++ b/src/content/docs/pages/how-to/build-commands-branches.mdx
@@ -5,6 +5,7 @@ title: Set build commands per branch
 description: Run different build commands on specific branches in your Cloudflare Pages project.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -45,7 +46,6 @@ To put your changes into effect:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
 4. Update the **Build command** field value to `bash build.sh` and select **Save**.
diff --git a/src/content/docs/pages/how-to/custom-branch-aliases.mdx b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
index 818ca533a5bf852..a50f4c6b38fe0a3 100644
--- a/src/content/docs/pages/how-to/custom-branch-aliases.mdx
+++ b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
@@ -4,6 +4,7 @@ title: Add a custom domain to a branch
 description: Point a custom domain to a specific branch deployment of your Cloudflare Pages project.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -31,7 +32,6 @@ To do this:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Select **Custom domains** > **Setup a custom domain**.
 4. Input the domain you would like to use, such as `staging.example.com`
diff --git a/src/content/docs/pages/how-to/enable-zaraz.mdx b/src/content/docs/pages/how-to/enable-zaraz.mdx
index 20a3092b435873c..a421e08bb06a094 100644
--- a/src/content/docs/pages/how-to/enable-zaraz.mdx
+++ b/src/content/docs/pages/how-to/enable-zaraz.mdx
@@ -4,6 +4,7 @@ title: Enable Zaraz
 description: Set up Zaraz on your Cloudflare Pages project using a custom domain.
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/index.mdx b/src/content/docs/pages/how-to/index.mdx
index 3da369ff33b9913..d2707643d72ee16 100644
--- a/src/content/docs/pages/how-to/index.mdx
+++ b/src/content/docs/pages/how-to/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: How to
 description: Step-by-step guides for common Cloudflare Pages tasks and configurations.
@@ -8,6 +9,7 @@ sidebar:
     hideIndex: true
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/npm-private-registry.mdx b/src/content/docs/pages/how-to/npm-private-registry.mdx
index a03e59ef22f9dc3..95889b262b4dd84 100644
--- a/src/content/docs/pages/how-to/npm-private-registry.mdx
+++ b/src/content/docs/pages/how-to/npm-private-registry.mdx
@@ -4,6 +4,7 @@ title: Install private packages
 description: Use custom npm registries and private dependencies in your Cloudflare Pages builds.
 products:
   - pages
+
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
index 76183d80849d09f..8780a611c5c465c 100644
--- a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
+++ b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
@@ -5,6 +5,7 @@ description: Use Cloudflare Tunnel to share locally running Pages projects over
 products:
   - pages
   - tunnel
+
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) runs a lightweight daemon (`cloudflared`) in your infrastructure that establishes outbound connections (Tunnels) between your origin web server and the Cloudflare global network. In practical terms, you can use Cloudflare Tunnel to allow remote access to services running on your local machine. It is an alternative to popular tools like [Ngrok](https://ngrok.com), and provides free, long-running tunnels via the [TryCloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/trycloudflare/) service.
diff --git a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
index 4349352400a31e5..e70f762274f2772 100644
--- a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
+++ b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
@@ -6,6 +6,7 @@ sidebar:
   hidden: true
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
index 5526154ba6650bd..1770a4c1621da73 100644
--- a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
+++ b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
@@ -4,6 +4,7 @@ title: Use Direct Upload with continuous integration
 description: Deploy prebuilt assets to Cloudflare Pages using Wrangler in your CI/CD pipeline.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -28,7 +29,6 @@ To generate an API token:
 1. In the Cloudflare dashboard, go to the **API Tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
-
 2. Select **Create Token**.
 3. Under **Custom Token**, select **Get started**.
 4. Name your API Token in the **Token name** field.
@@ -43,7 +43,7 @@ Now that you have created your API token, you can use it to push your project fr
 
 To find your account ID, go to the **Zone Overview** page in the Cloudflare dashboard.
 
-<DashButton url="/?to=/:account/:zone/" />
+   <DashButton url="/?to=/:account/:zone/" />
 
 Find your account ID in the **API** section on the right-hand side menu.
 
diff --git a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
index 8e750ac70df0a77..2d7fb92626a856d 100644
--- a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
+++ b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
@@ -4,6 +4,7 @@ title: Use Pages Functions for A/B testing
 description: Implement A/B testing in Cloudflare Pages using Pages Functions and cookies.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -161,5 +162,4 @@ After you have deployed your application, review your middleware Function:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings** > **Functions** > **Configuration**.
diff --git a/src/content/docs/pages/how-to/web-analytics.mdx b/src/content/docs/pages/how-to/web-analytics.mdx
index 80cab7cc7a0ebda..723b5241d55c0e2 100644
--- a/src/content/docs/pages/how-to/web-analytics.mdx
+++ b/src/content/docs/pages/how-to/web-analytics.mdx
@@ -4,6 +4,7 @@ title: Enable Web Analytics
 description: Set up Cloudflare Web Analytics on your Pages project with one-click configuration.
 products:
   - pages
+
 ---
 
 import { Render, DashButton } from "~/components";
@@ -23,7 +24,6 @@ To view the metrics associated with your Pages project:
 1. In the Cloudflare dashboard, go to the **Web Analytics** page.
 
    <DashButton url="/?to=/:account/web-analytics" />
-
 2. Select the analytics associated with your Pages project.
 
 For more details about how to use Web Analytics, refer to the [Web Analytics documentation](/web-analytics/data-metrics/).
diff --git a/src/content/docs/pages/migrations/index.mdx b/src/content/docs/pages/migrations/index.mdx
index 462426a9667eb83..dfac1294f41d646 100644
--- a/src/content/docs/pages/migrations/index.mdx
+++ b/src/content/docs/pages/migrations/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: Migration guides
 description: Migrate your existing site from another platform to Cloudflare Pages.
@@ -7,6 +8,7 @@ sidebar:
   order: 4
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/index.mdx b/src/content/docs/pages/platform/index.mdx
index 925be7f4266e12b..1a133b13acfc655 100644
--- a/src/content/docs/pages/platform/index.mdx
+++ b/src/content/docs/pages/platform/index.mdx
@@ -8,6 +8,7 @@ sidebar:
     hideIndex: true
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/known-issues.mdx b/src/content/docs/pages/platform/known-issues.mdx
index 3a0b439ae2c0327..cd105ebacb7fa5e 100644
--- a/src/content/docs/pages/platform/known-issues.mdx
+++ b/src/content/docs/pages/platform/known-issues.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 4
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -39,6 +40,7 @@ Here are some known bugs and issues with Cloudflare Pages:
 ## Custom Domains
 
 - It is currently not possible to add a custom domain with
+
   - a wildcard, for example, `*.domain.com`.
   - a Worker already routed on that domain.
 
@@ -65,7 +67,6 @@ If you would like to enable [Cloudflare Access](https://www.cloudflare.com/teams
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Enable access policy**.
 4. Select **Manage** on the Access policy created for your preview deployments.
diff --git a/src/content/docs/pages/platform/limits.mdx b/src/content/docs/pages/platform/limits.mdx
index 372373843e2b19a..dd994f7de3cd191 100644
--- a/src/content/docs/pages/platform/limits.mdx
+++ b/src/content/docs/pages/platform/limits.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 1
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
@@ -17,10 +18,10 @@ Below are limits observed by the Cloudflare Free plan. For more details on remov
 ## Builds
 
 Each time you push new code to your Git repository, Pages will build and deploy your site. Build limits depend on your plan:
-| | Free | Pro | Business |
+|                  | Free              | Pro                 | Business             |
 | ---------------- | ----------------- | ------------------- | -------------------- |
-| Builds | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
-| Builds per month | 500 | 5,000 | 20,000 |
+| Builds           | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
+| Builds per month | 500               | 5,000               | 20,000               |
 
 Builds will timeout after 20 minutes. Concurrent builds are counted per account.
 
diff --git a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
index 499da32c9d96168..880fe3088aafd05 100644
--- a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
+++ b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
@@ -114,7 +114,7 @@ import ContactForm from "./ContactForm";
 Then insert the form into the page as a react component:
 
 ```jsx
-<ContactForm />;
+<ContactForm />
 ```
 
 For example, you can update your `src/App.js` file to add the form:
diff --git a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
index 413e037121afc72..d8a492d5d29124e 100644
--- a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
+++ b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
@@ -365,7 +365,6 @@ After you have pushed your project to GitHub, deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Import an existing Git repository**.
 3. Select the new GitHub repository that you created and select **Begin setup**.
 4. In the **Set up builds and deployments** section, under **Build settings** > **Framework preset**, choose _Nuxt_. Pages will set the correct fields for you automatically.
diff --git a/src/content/docs/pipelines/reference/wrangler-commands.mdx b/src/content/docs/pipelines/reference/wrangler-commands.mdx
index 154b40b6ccb4976..655d91f87e8a583 100644
--- a/src/content/docs/pipelines/reference/wrangler-commands.mdx
+++ b/src/content/docs/pipelines/reference/wrangler-commands.mdx
@@ -10,4 +10,5 @@ products:
 
 import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="pipelines" />
+<WranglerNamespace namespace="pipelines"/>
+
diff --git a/src/content/docs/pipelines/sinks/manage-sinks.mdx b/src/content/docs/pipelines/sinks/manage-sinks.mdx
index 5f4d14b28b01f0a..7623ca305f5c3e1 100644
--- a/src/content/docs/pipelines/sinks/manage-sinks.mdx
+++ b/src/content/docs/pipelines/sinks/manage-sinks.mdx
@@ -101,4 +101,4 @@ Deleting a sink stops all data writes to that destination.
 ## Limitations
 
 - Sinks cannot be modified after creation. To change sink configuration, you must delete and recreate the sink.
-- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
+- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
\ No newline at end of file
diff --git a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
index da91b792332d4d5..b47c9b02de9b990 100644
--- a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
+++ b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
@@ -521,6 +521,7 @@ uuid()
 Returns the string which is replaced by another string from the specified position and specified count length.
 For example, `overlay('Txxxxas' placing 'hom' from 2 for 4) → Thomas`
 
+
 ```
 overlay(str PLACING substr FROM pos [FOR count])
 ```
diff --git a/src/content/docs/privacy-gateway/get-started.mdx b/src/content/docs/privacy-gateway/get-started.mdx
index 05973978d5a98cd..41f956ba77f1276 100644
--- a/src/content/docs/privacy-gateway/get-started.mdx
+++ b/src/content/docs/privacy-gateway/get-started.mdx
@@ -14,13 +14,13 @@ Privacy Gateway implementation consists of three main parts:
 2. Client configuration (operated by you).
 3. Connection to a Privacy Gateway Relay Server (operated by Cloudflare).
 
----
+***
 
 ## Before you begin
 
 Privacy Gateway is currently in closed beta. If you are interested, [contact us](https://www.cloudflare.com/lp/privacy-edge/).
 
----
+***
 
 ## Step 1 - Configure your server
 
@@ -34,13 +34,13 @@ Applications can also implement this functionality themselves. Details about [pu
 
 Use the following resources for help with server configuration:
 
-- **Go**:
-  - [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
-  - [Gateway library](https://github.com/chris-wood/ohttp-go)
-- **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
-- **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
+* **Go**:
+  * [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
+  * [Gateway library](https://github.com/chris-wood/ohttp-go)
+* **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
+* **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
 
----
+***
 
 ## Step 2 - Configure your client
 
@@ -52,21 +52,21 @@ Additionally, app developers need to [configure the client](#resources-1) to fet
 
 Use the following resources for help with client configuration:
 
-- **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
-- **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
-- **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
+* **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
+* **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
+* **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
 
----
+***
 
 ## Step 3 - Review your application
 
 After you have configured your client and server, review your application to make sure you are only sending intended data to Cloudflare and the application backend. In particular, application data should not contain anything unique to an end-user, as this would invalidate the benefits that OHTTP provides.
 
-- Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
-- Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
-- Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
+* Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
+* Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
+* Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
 
----
+***
 
 ## Step 4 - Relay requests through Cloudflare
 
diff --git a/src/content/docs/privacy-gateway/reference/index.mdx b/src/content/docs/privacy-gateway/reference/index.mdx
index bdcb0f1f7729beb..50d23832e8505f7 100644
--- a/src/content/docs/privacy-gateway/reference/index.mdx
+++ b/src/content/docs/privacy-gateway/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - privacy-gateway
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/privacy-gateway/reference/legal.mdx b/src/content/docs/privacy-gateway/reference/legal.mdx
index 8f68db4684d0d76..22928aac224e0f6 100644
--- a/src/content/docs/privacy-gateway/reference/legal.mdx
+++ b/src/content/docs/privacy-gateway/reference/legal.mdx
@@ -24,5 +24,5 @@ Cloudflare retains the Privacy Gateway Logs information for the most recent quar
 
 ## What Privacy Gateway customers see
 
-- The application content of requests.
-- The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
+* The application content of requests.
+* The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
diff --git a/src/content/docs/privacy-gateway/reference/metrics.mdx b/src/content/docs/privacy-gateway/reference/metrics.mdx
index 6a0751366ca483b..f40cb4d6ffbc6ee 100644
--- a/src/content/docs/privacy-gateway/reference/metrics.mdx
+++ b/src/content/docs/privacy-gateway/reference/metrics.mdx
@@ -10,8 +10,8 @@ products:
 
 Privacy Gateway now supports enhanced monitoring through our GraphQL API, providing detailed insights into your gateway traffic and performance. To access these metrics, ensure you have:
 
-- A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
-- An API token with Analytics Read permissions.
+* A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
+* An API token with Analytics Read permissions.
   We offer two GraphQL nodes to retrieve metrics: `ohttpMetricsAdaptive` and `ohttpMetricsAdaptiveGroups`. The first node provides comprehensive request data, while the second facilitates grouped analytics.
 
 ## ohttpMetricsAdaptive
@@ -20,27 +20,33 @@ The `ohttpMetricsAdaptive` node is designed for detailed insights into individua
 
 ### Key Arguments
 
-- `filter` required
-  - Apply filters to narrow down your data set. `accountTag` is a required filter.
-- `limit` optional
-  - Specify the maximum number of records to return.
-- `orderBy` optional
-  - Choose how to sort your data, with options for various dimensions and metrics.
+
+
+* `filter` required
+  * Apply filters to narrow down your data set. `accountTag` is a required filter.
+* `limit`  optional
+  * Specify the maximum number of records to return.
+* `orderBy` optional
+  * Choose how to sort your data, with options for various dimensions and metrics.
+
 
 ### Available Fields
 
-- `bytesToClient` int optional
-  - The number of bytes returned to the client.
-- `bytesToGateway` int optional
-  - Total bytes received from the client.
-- `colo` string optional
-  - Airport code of the Cloudflare data center that served the request.
-- `datetime` Time optional
-  - The date and time when the event was recorded.
-- `gatewayStatusCode` int optional
-  - Status code returned by the gateway.
-- `relayStatusCode` int optional
-  - Status code returned by the relay.
+
+
+* `bytesToClient` int optional
+  * The number of bytes returned to the client.
+* `bytesToGateway` int optional
+  * Total bytes received from the client.
+* `colo` string optional
+  * Airport code of the Cloudflare data center that served the request.
+* `datetime` Time optional
+  * The date and time when the event was recorded.
+* `gatewayStatusCode` int optional
+  * Status code returned by the gateway.
+* `relayStatusCode` int optional
+  * Status code returned by the relay.
+
 
 This node is useful for a granular view of traffic, helping you identify patterns, performance issues, or anomalies in your data flow.
 
@@ -50,56 +56,66 @@ The `ohttpMetricsAdaptiveGroups` node allows for aggregated analysis of OHTTP re
 
 ### Key Arguments
 
-- `filter` required
-  - Apply filters to narrow down your data set. `accountTag` is a required filter.
-- `limit` optional
-  - Specify the maximum number of records to return.
-- `orderBy` optional
-  - Choose how to sort your data, with options for various dimensions and metrics.
+
+
+* `filter` required
+  * Apply filters to narrow down your data set. `accountTag` is a required filter.
+* `limit`  optional
+  * Specify the maximum number of records to return.
+* `orderBy` optional
+  * Choose how to sort your data, with options for various dimensions and metrics.
+
 
 ### Available Fields
 
-- `count` int optional
-  - The number of records that meet the criteria.
-- `dimensions` optional
-  - Specifies the grouping dimensions for your data.
-- `sum` optional
-  - Aggregated totals for various metrics, per dimension.
+
+
+* `count` int optional
+  * The number of records that meet the criteria.
+* `dimensions` optional
+  * Specifies the grouping dimensions for your data.
+* `sum` optional
+  * Aggregated totals for various metrics, per dimension.
+
 
 **Dimensions**
 
 You can group your metrics by various dimensions to get a more segmented view of your data:
 
-- `colo` string optional
-  - The airport code of the Cloudflare data center.
-- `date` Date optional
-  - The date of OHTTP request metrics.
-- `datetimeFifteenMinutes` Time optional
-  - Timestamp truncated to fifteen minutes.
-- `datetimeFiveMinutes` Time optional
-  - Timestamp truncated to five minutes.
-- `datetimeHour` Time optional
-  - Timestamp truncated to the hour.
-- `datetimeMinute` Time optional
-  - Timestamp truncated to the minute.
-- `endpoint` string optional
-  - The appId that generated traffic.
-- `gatewayStatusCode` int optional
-  - Status code returned by the gateway.
-- `relayStatusCode` int optional
-  - Status code returned by the relay.
+
+* `colo` string optional
+  * The airport code of the Cloudflare data center.
+* `date` Date optional
+  * The date of OHTTP request metrics.
+* `datetimeFifteenMinutes` Time optional
+  * Timestamp truncated to fifteen minutes.
+* `datetimeFiveMinutes` Time optional
+  * Timestamp truncated to five minutes.
+* `datetimeHour` Time optional
+  * Timestamp truncated to the hour.
+* `datetimeMinute` Time optional
+  * Timestamp truncated to the minute.
+* `endpoint` string optional
+  * The appId that generated traffic.
+* `gatewayStatusCode` int optional
+  * Status code returned by the gateway.
+* `relayStatusCode` int optional
+  * Status code returned by the relay.
+
 
 **Sum Fields**
 
 Sum fields offer a cumulative view of various metrics over your selected time period:
 
-- `bytesToClient` int optional
-  - Total bytes sent from the gateway to the client.
-- `bytesToGateway` int optional
-  - Total bytes from the client to the gateway.
-- `clientRequestErrors` int optional
-  - Total number of client request errors.
-- `gatewayResponseErrors` int optional
-  - Total number of gateway response errors.
+
+* `bytesToClient` int optional
+  * Total bytes sent from the gateway to the client.
+* `bytesToGateway` int optional
+  * Total bytes from the client to the gateway.
+* `clientRequestErrors` int optional
+  * Total number of client request errors.
+* `gatewayResponseErrors` int optional
+  * Total number of gateway response errors.
+
 
 Utilize the ohttpMetricsAdaptiveGroups node to gain comprehensive, aggregated insights into your traffic patterns, helping you optimize performance and user experience.
diff --git a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
index e319b9824e7ef2c..f6f435416d2e986 100644
--- a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
+++ b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
@@ -12,6 +12,6 @@ When [using Privacy Gateway](/privacy-gateway/get-started/), the majority of Clo
 
 However, the following products are not compatible:
 
-- [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
-- [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
-- [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
+* [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
+* [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
+* [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
diff --git a/src/content/docs/privacy-proxy/concepts/authentication.mdx b/src/content/docs/privacy-proxy/concepts/authentication.mdx
index 344ac01c3d65a39..5adead0bc45a818 100644
--- a/src/content/docs/privacy-proxy/concepts/authentication.mdx
+++ b/src/content/docs/privacy-proxy/concepts/authentication.mdx
@@ -14,11 +14,11 @@ Privacy Proxy requires clients to authenticate before proxying traffic. This pag
 
 Privacy Proxy supports three authentication methods:
 
-| Method               | Use case                  | Privacy level |
-| -------------------- | ------------------------- | ------------- |
-| Pre-shared key (PSK) | Proof of concept, testing | Lower         |
-| Privacy Pass tokens  | Client to server          | High          |
-| mTLS                 | Server to server          | Higher        |
+| Method | Use case | Privacy level |
+| -------- | ---------- | --------------- |
+| Pre-shared key (PSK) | Proof of concept, testing | Lower |
+| Privacy Pass tokens | Client to server | High |
+| mTLS | Server to server | Higher |
 
 ---
 
@@ -166,7 +166,7 @@ Proxy A (which you operate) authenticates users. Common methods include:
 - Privacy Pass tokens issued by your infrastructure
 - Client certificates (mTLS)
 
-### Proxy A to Proxy B
+### Proxy A to Proxy B 
 
 Proxy B authenticates itself to Proxy A using TLS. Depending on your configuration, this can use:
 
diff --git a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
index dfe5168ada7b9a2..72190396733d8b8 100644
--- a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
+++ b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
@@ -65,12 +65,12 @@ In a double-hop deployment, you operate the first proxy (Proxy A), and Cloudflar
 
 The double-hop architecture ensures:
 
-| Information        | Proxy A (you) | Proxy B (Cloudflare) |
-| ------------------ | ------------- | -------------------- |
-| Client IP address  | Yes           | No                   |
-| User account       | Yes           | No                   |
-| Destination server | Encrypted     | Yes                  |
-| Request content    | Encrypted     | Encrypted            |
+| Information | Proxy A (you) | Proxy B (Cloudflare) |
+| ------------- | --------------- | ---------------------- |
+| Client IP address | Yes | No |
+| User account | Yes | No |
+| Destination server | Encrypted | Yes |
+| Request content | Encrypted | Encrypted |
 
 Proxy A knows who the user is but cannot see where they are going (the destination is encrypted). Proxy B knows the destination but not who is making the request. Neither party has the complete picture.
 
@@ -90,13 +90,13 @@ Double-hop deployment works well when:
 
 ## Comparison
 
-| Aspect                 | Single-hop                        | Double-hop                 |
-| ---------------------- | --------------------------------- | -------------------------- |
-| Infrastructure         | Cloudflare only                   | You + Cloudflare           |
-| Privacy separation     | Proxy sees identity + destination | Split across two parties   |
-| Operational complexity | Lower                             | Higher                     |
-| Authentication         | Cloudflare-managed                | You manage first-hop auth  |
-| Use case               | Browser VPNs, simple privacy      | Maximum privacy separation |
+| Aspect | Single-hop | Double-hop |
+| -------- | ------------ | ------------ |
+| Infrastructure | Cloudflare only | You + Cloudflare |
+| Privacy separation | Proxy sees identity + destination | Split across two parties |
+| Operational complexity | Lower | Higher |
+| Authentication | Cloudflare-managed | You manage first-hop auth |
+| Use case | Browser VPNs, simple privacy | Maximum privacy separation |
 
 ---
 
diff --git a/src/content/docs/privacy-proxy/concepts/geolocation.mdx b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
index 2c60dc4cbde92c0..987c5e96e5514ab 100644
--- a/src/content/docs/privacy-proxy/concepts/geolocation.mdx
+++ b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
@@ -30,12 +30,12 @@ Privacy Proxy uses geohashes to preserve location without revealing precise coor
 A [geohash](https://en.wikipedia.org/wiki/Geohash) is a compact representation of latitude and longitude. Geohashes use a hierarchical encoding where longer strings represent more precise locations:
 
 | Geohash length | Approximate area |
-| -------------- | ---------------- |
-| 1 character    | ~5,000 km        |
-| 2 characters   | ~1,250 km        |
-| 3 characters   | ~150 km          |
-| 4 characters   | ~40 km           |
-| 5 characters   | ~5 km            |
+| ---------------- | ------------------ |
+| 1 character | ~5,000 km |
+| 2 characters | ~1,250 km |
+| 3 characters | ~150 km |
+| 4 characters | ~40 km |
+| 5 characters | ~5 km |
 
 Privacy Proxy uses reduced-precision geohashes (typically four to five characters) to locate users to a city or region without pinpointing their exact location.
 
diff --git a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
index 6d1b3146f38fc82..3c4634922f9757c 100644
--- a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
+++ b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
@@ -35,14 +35,15 @@ Privacy Proxy uses the MASQUE protocol suite to create encrypted tunnels between
 
 Throughout this process, the proxy learns the destination but not the content. The destination learns the egress IP address but not the client's real IP.
 
+
 ## MASQUE protocols
 
 [MASQUE](https://datatracker.ietf.org/wg/masque/about/) (Multiplexed Application Substrate over QUIC Encryption) defines methods for proxying traffic over HTTP. Privacy Proxy supports two MASQUE methods:
 
-| Method       | Transport | Use case                                   |
-| ------------ | --------- | ------------------------------------------ |
-| HTTP CONNECT | TCP       | Traditional HTTPS traffic                  |
-| CONNECT-UDP  | UDP       | QUIC-based traffic, real-time applications |
+| Method | Transport | Use case |
+| -------- | ----------- | ---------- |
+| HTTP CONNECT | TCP | Traditional HTTPS traffic |
+| CONNECT-UDP | UDP | QUIC-based traffic, real-time applications |
 
 Both methods create encrypted tunnels where the proxy forwards traffic without inspecting the content. The proxy sees only the destination hostname and port, not the actual requests, paths, or data exchanged.
 
@@ -54,11 +55,11 @@ For a technical deep dive into how these protocols work, refer to our [blog post
 
 Privacy Proxy creates a privacy boundary between user identity and user activity:
 
-| Information                         | Who knows it                                                  |
-| ----------------------------------- | ------------------------------------------------------------- |
+| Information | Who knows it |
+| ------------- | -------------- |
 | User identity (IP address, account) | Authentication service, first-hop proxy (if using double-hop) |
-| Destination server                  | Privacy Proxy, destination server                             |
-| Request content                     | Client, destination server only                               |
+| Destination server | Privacy Proxy, destination server |
+| Request content | Client, destination server only |
 
 The proxy authenticates users to verify they have permission to use the service, but authentication happens separately from proxying. Once authenticated, the proxy forwards traffic without linking individual requests to specific users.
 
diff --git a/src/content/docs/privacy-proxy/get-started.mdx b/src/content/docs/privacy-proxy/get-started.mdx
index 951b12a8ad7876e..f07aa967b04f5d0 100644
--- a/src/content/docs/privacy-proxy/get-started.mdx
+++ b/src/content/docs/privacy-proxy/get-started.mdx
@@ -37,7 +37,7 @@ curl -v \
   https://example.com
 ```
 
-### Use Chaussette
+### Use Chaussette 
 
 [Chaussette](/privacy-proxy/reference/client-libraries/#chaussette) is a local SOCKS5 proxy that handles authentication and forwards requests to Privacy Proxy.
 
diff --git a/src/content/docs/privacy-proxy/reference/http-headers.mdx b/src/content/docs/privacy-proxy/reference/http-headers.mdx
index da3750df07b72b9..39788fd3a51a37b 100644
--- a/src/content/docs/privacy-proxy/reference/http-headers.mdx
+++ b/src/content/docs/privacy-proxy/reference/http-headers.mdx
@@ -30,10 +30,10 @@ Privacy Pass token format:
 Proxy-Authorization: PrivateToken token=<base64-encoded-token>
 ```
 
-| Parameter                | Description                               |
-| ------------------------ | ----------------------------------------- |
-| `<key>`                  | The pre-shared key provided by Cloudflare |
-| `<base64-encoded-token>` | A base64-encoded Privacy Pass token       |
+| Parameter | Description |
+| ----------- | ------------- |
+| `<key>` | The pre-shared key provided by Cloudflare |
+| `<base64-encoded-token>` | A base64-encoded Privacy Pass token |
 
 ### GraphQL Analytics API request headers
 
@@ -47,10 +47,10 @@ Specifies the client's geographic location for egress IP selection. Optional but
 sec-ch-geohash: <geohash>-<country_code>
 ```
 
-| Parameter        | Description                                                                          |
-| ---------------- | ------------------------------------------------------------------------------------ |
-| `<geohash>`      | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
-| `<country_code>` | ISO 3166-1 alpha-2 country code                                                      |
+| Parameter | Description |
+| ----------- | ------------- |
+| `<geohash>` | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
+| `<country_code>` | ISO 3166-1 alpha-2 country code |
 
 ```http title="Example"
 sec-ch-geohash: u4pruydqqvj-GB
@@ -72,8 +72,8 @@ Provides timing information about proxy processing. This is part of the [OpenTel
 Server-Timing: proxy;dur=<milliseconds>
 ```
 
-| Parameter        | Description                                             |
-| ---------------- | ------------------------------------------------------- |
+| Parameter | Description |
+| ----------- | ------------- |
 | `<milliseconds>` | Processing time in milliseconds introduced by the proxy |
 
 ```http title="Example"
@@ -99,9 +99,9 @@ sec-ch-geohash: 9q8yy-US
 
 The proxy responds with a status code indicating success or failure:
 
-| Status                    | Meaning                          |
-| ------------------------- | -------------------------------- |
-| `200 OK`                  | Tunnel established successfully  |
-| `403 Forbidden`           | Authentication failed            |
-| `502 Bad Gateway`         | Could not connect to destination |
-| `503 Service Unavailable` | Proxy temporarily unavailable    |
+| Status | Meaning |
+| -------- | --------- |
+| `200 OK` | Tunnel established successfully |
+| `403 Forbidden` | Authentication failed |
+| `502 Bad Gateway` | Could not connect to destination |
+| `503 Service Unavailable` | Proxy temporarily unavailable |
diff --git a/src/content/docs/privacy-proxy/reference/proxy-status.mdx b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
index 3cd177c2306ccca..8a0a873a9b6ca6f 100644
--- a/src/content/docs/privacy-proxy/reference/proxy-status.mdx
+++ b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
@@ -16,29 +16,29 @@ The `proxyStatus` dimension provides proxy-level error classification. This fiel
 
 ## `proxyStatus` values
 
-| Value                       | Description                                                                                          |
-| --------------------------- | ---------------------------------------------------------------------------------------------------- |
-| `dns_error`                 | The proxy encountered a DNS error when resolving the next hop hostname.                              |
-| `dns_timeout`               | The proxy timed out while resolving the next hop hostname.                                           |
-| `destination_not_found`     | The proxy cannot determine the appropriate next hop for this request.                                |
-| `destination_unavailable`   | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
-| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address.                          |
-| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address.                                            |
-| `connection_refused`        | The proxy's connection to the next hop was refused.                                                  |
-| `connection_terminated`     | The proxy's connection to the next hop was closed before any response was received.                  |
-| `connection_timeout`        | The proxy's attempt to open a connection to the next hop timed out.                                  |
-| `connection_read_timeout`   | The proxy was expecting data on a connection but received none within the configured time limit.     |
-| `connection_write_timeout`  | The proxy was attempting to write data to a connection but was unable to.                            |
-| `connection_limit_reached`  | The proxy's configured connection limit to the next hop has been exceeded.                           |
-| `source_addr_in_use`        | The proxy cannot assign a source address when connecting to the next hop.                            |
-| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure).           |
-| `tls_protocol_error`        | The proxy encountered a TLS error when communicating with the next hop.                              |
-| `tls_certificate_error`     | The proxy encountered an error verifying the certificate presented by the next hop.                  |
-| `http_request_error`        | The proxy is generating a client (4xx) response on the origin's behalf.                              |
-| `http_upgrade_failed`       | The HTTP Upgrade between the proxy and the next hop failed.                                          |
-| `http_request_denied`       | The proxy rejected the HTTP request based on its configuration or policy.                            |
-| `proxy_internal_error`      | The proxy encountered an internal error unrelated to the origin.                                     |
-| `proxy_loop_detected`       | The proxy tried to forward the request to itself.                                                    |
-| `http_protocol_error`       | The proxy encountered an HTTP protocol error when communicating with the next hop.                   |
-| `http_response_incomplete`  | The proxy received an incomplete response from the next hop.                                         |
-| `rate_limited`              | The client has reached the maximum number of connections per second to a single origin.              |
+| Value | Description |
+| --- | --- |
+| `dns_error` | The proxy encountered a DNS error when resolving the next hop hostname. |
+| `dns_timeout` | The proxy timed out while resolving the next hop hostname. |
+| `destination_not_found` | The proxy cannot determine the appropriate next hop for this request. |
+| `destination_unavailable` | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
+| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address. |
+| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address. |
+| `connection_refused` | The proxy's connection to the next hop was refused. |
+| `connection_terminated` | The proxy's connection to the next hop was closed before any response was received. |
+| `connection_timeout` | The proxy's attempt to open a connection to the next hop timed out. |
+| `connection_read_timeout` | The proxy was expecting data on a connection but received none within the configured time limit. |
+| `connection_write_timeout` | The proxy was attempting to write data to a connection but was unable to. |
+| `connection_limit_reached` | The proxy's configured connection limit to the next hop has been exceeded. |
+| `source_addr_in_use` | The proxy cannot assign a source address when connecting to the next hop. |
+| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure). |
+| `tls_protocol_error` | The proxy encountered a TLS error when communicating with the next hop. |
+| `tls_certificate_error` | The proxy encountered an error verifying the certificate presented by the next hop. |
+| `http_request_error` | The proxy is generating a client (4xx) response on the origin's behalf. |
+| `http_upgrade_failed` | The HTTP Upgrade between the proxy and the next hop failed. |
+| `http_request_denied` | The proxy rejected the HTTP request based on its configuration or policy. |
+| `proxy_internal_error` | The proxy encountered an internal error unrelated to the origin. |
+| `proxy_loop_detected` | The proxy tried to forward the request to itself. |
+| `http_protocol_error` | The proxy encountered an HTTP protocol error when communicating with the next hop. |
+| `http_response_incomplete` | The proxy received an incomplete response from the next hop. |
+| `rate_limited` | The client has reached the maximum number of connections per second to a single origin. |
diff --git a/src/content/docs/pulumi/tutorial/index.mdx b/src/content/docs/pulumi/tutorial/index.mdx
index 2d5a00e48f838d0..a221bc981254072 100644
--- a/src/content/docs/pulumi/tutorial/index.mdx
+++ b/src/content/docs/pulumi/tutorial/index.mdx
@@ -12,16 +12,19 @@ products:
 Before you begin, make sure you [install Pulumi](/pulumi/installing/).
 
 1. [Add a Site](/pulumi/tutorial/add-site/)
+
    - Bring your existing site under Cloudflare with Pulumi IaC.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Zone and DNS records.
 
 2. [Manage secrets](/pulumi/tutorial/manage-secrets/)
+
    - Develop Workers securely with Pulumi ESC and Wrangler.
    - Introduction to the ESC CLI and the Wrangler CLI.
    - Manage Cloudflare credentials, Worker secrets, and `.dev.vars`.
 
 3. [Deploy a Worker](/pulumi/tutorial/hello-world/)
+
    - Brief introduction to deploying a Cloudflare Workers application with Pulumi.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Worker script, Worker route, and DNS record.
diff --git a/src/content/docs/queues/configuration/configure-queues.mdx b/src/content/docs/queues/configuration/configure-queues.mdx
index cec7b05be692f5a..67aaf22fcf32e57 100644
--- a/src/content/docs/queues/configuration/configure-queues.mdx
+++ b/src/content/docs/queues/configuration/configure-queues.mdx
@@ -15,33 +15,35 @@ import { WranglerConfig, Type } from "~/components";
 
 Cloudflare Queues can be configured using [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Cloudflare's Developer Platform, which includes [Workers](/workers/), [R2](/r2/), and other developer products.
 
+
 Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
 
 Use the options below to configure your queue.
 
 :::note
 
+
 Below are options for queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
 
+
 :::
 
 ## Queue configuration
-
 The following queue level settings can be configured using Wrangler:
 
 ```sh
 npx wrangler queues update <QUEUE-NAME> --delivery-delay-secs 60 --message-retention-period-secs 3000
 ```
 
-- `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
-  - How long a published message is delayed for, before it is delivered to consumers.
-  - Must be between 0 and 86400 (24 hours).
-  - Defaults to 0.
+* `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
+	* How long a published message is delayed for, before it is delivered to consumers.
+	* Must be between 0 and 86400 (24 hours).
+	* Defaults to 0.
 
-- `--message-retention-period-secs` <Type text="number" /> <Type text="optional" />
-  - How long messages are retained on the Queue.
-  - Defaults to 345600 (4 days).
-  - Must be between 60 and 1209600 (14 days)
+* `--message-retention-period-secs`  <Type text="number" /> <Type text="optional" />
+	* How long messages are retained on the Queue.
+	* Defaults to 345600 (4 days).
+	* Must be between 60 and 1209600 (14 days)
 
 ## Producer Worker configuration
 
@@ -66,16 +68,24 @@ To produce to a queue, set up a binding in your Wrangler file. These options sho
 
 </WranglerConfig>
 
-- <code>queue</code> <Type text="string" />
-  - The name of the queue.
 
-- <code>binding</code> <Type text="string" />
-  - The name of the binding, which is a JavaScript variable.
+
+* <code>queue</code> <Type text="string" />
+
+  * The name of the queue.
+
+* <code>binding</code> <Type text="string" />
+
+  * The name of the binding, which is a JavaScript variable.
+
+
 
 ## Consumer Worker Configuration
 
 To consume messages from one or more queues, set up a binding in your Wrangler file. These options should be used when a Worker wants to receive messages from a queue.
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -98,29 +108,39 @@ To consume messages from one or more queues, set up a binding in your Wrangler f
 
 Refer to [Limits](/queues/platform/limits) to review the maximum values for each of these options.
 
-- <code>queue</code> <Type text="string" />
-  - The name of the queue.
 
-- <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of messages allowed in each batch.
-  - Defaults to `10` messages.
 
-- <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of seconds to wait until a batch is full.
-  - Defaults to `5` seconds.
+* <code>queue</code> <Type text="string" />
+
+  * The name of the queue.
+
+* <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of messages allowed in each batch.
+  * Defaults to `10` messages.
+
+* <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of seconds to wait until a batch is full.
+  * Defaults to `5` seconds.
+
+* <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
+  * Defaults to `3` retries.
+
+* <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
+
+  * The name of another queue to send a message if it fails processing at least `max_retries` times.
+  * If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
+  * If there is no queue with the specified name, it will be created automatically.
+
+* <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
 
-- <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
-  - Defaults to `3` retries.
+  * The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
+  * Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
-- <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
-  - The name of another queue to send a message if it fails processing at least `max_retries` times.
-  - If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
-  - If there is no queue with the specified name, it will be created automatically.
 
-- <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
-  - Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
 ## Pull-based
 
diff --git a/src/content/docs/queues/configuration/consumer-concurrency.mdx b/src/content/docs/queues/configuration/consumer-concurrency.mdx
index 503b8d2fdba5fa2..072aa3381bd5001 100644
--- a/src/content/docs/queues/configuration/consumer-concurrency.mdx
+++ b/src/content/docs/queues/configuration/consumer-concurrency.mdx
@@ -71,7 +71,7 @@ To configure the concurrency settings for your consumer Worker from the dashboar
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select your queue > **Settings**.
 3. Select **Edit Consumer** under Consumer details.
diff --git a/src/content/docs/queues/configuration/index.mdx b/src/content/docs/queues/configuration/index.mdx
index bc7e0d0237bb4c5..fb230019e4a5916 100644
--- a/src/content/docs/queues/configuration/index.mdx
+++ b/src/content/docs/queues/configuration/index.mdx
@@ -8,6 +8,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/configuration/javascript-apis.mdx b/src/content/docs/queues/configuration/javascript-apis.mdx
index a948c75c6c39862..9a34dca675084e9 100644
--- a/src/content/docs/queues/configuration/javascript-apis.mdx
+++ b/src/content/docs/queues/configuration/javascript-apis.mdx
@@ -94,27 +94,30 @@ A binding that allows a producer to send messages to a Queue.
 
 ```ts
 interface Queue<Body = unknown> {
-	send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
-	sendBatch(
-		messages: Iterable<MessageSendRequest<Body>>,
-		options?: QueueSendBatchOptions,
-	): Promise<QueueSendResult>;
-	metrics(): Promise<QueueMetrics>;
+  send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
+  sendBatch(messages: Iterable<MessageSendRequest<Body>>, options?: QueueSendBatchOptions): Promise<QueueSendResult>;
+  metrics(): Promise<QueueMetrics>;
 }
 ```
 
-- `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
-  - Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-  - When the promise resolves, the message is confirmed to be written to disk.
-  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
 
-- `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
-  - Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
-  - The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
-  - When the promise resolves, the messages are confirmed to be written to disk.
 
-- `metrics()` <Type text="Promise<QueueMetrics>" />
-  - Returns realtime [QueueMetrics](#queuemetrics) for the queue.
+* `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
+
+  * Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+  * When the promise resolves, the message is confirmed to be written to disk.
+  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+
+* `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
+
+  * Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
+  * The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
+  * When the promise resolves, the messages are confirmed to be written to disk.
+
+* `metrics()` <Type text="Promise<QueueMetrics>" />
+
+  * Returns realtime [QueueMetrics](#queuemetrics) for the queue.
+
 
 ### `MessageSendRequest`
 
@@ -122,44 +125,54 @@ A wrapper type used for sending message batches.
 
 ```ts
 interface MessageSendRequest<Body = unknown> {
-	body: Body;
-	contentType?: QueueContentType;
-	delaySeconds?: number;
+  body: Body;
+  contentType?: QueueContentType;
+  delaySeconds?: number;
 }
 ```
 
-- <code>body</code> <Type text="unknown" />
-  - The body of the message.
-  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
-- <code>contentType</code> <Type text="QueueContentType" />
-  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be an integer between 0 and 86400 (24 hours).
+* <code>body</code> <Type text="unknown" />
+
+  * The body of the message.
+  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+
+* <code>contentType</code> <Type text="QueueContentType" />
+
+  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  * See [QueuesContentType](#queuescontenttype) for possible values.
+
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be an integer between 0 and 86400 (24 hours).
+
+
 
 ### `QueueSendOptions`
 
 Optional configuration that applies when sending a message to a queue.
 
-- <code>contentType</code> <Type text="QueuesContentType" />
-  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  - As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
-  - See [QueuesContentType](#queuescontenttype) for possible values.
+* <code>contentType</code> <Type text="QueuesContentType" />
+
+  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  * As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
+  * See [QueuesContentType](#queuescontenttype) for possible values.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
 
 ### `QueueSendBatchOptions`
 
 Optional configuration that applies when sending a batch of messages to a queue.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be a positive integer.
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be a positive integer.
 
 ### `QueuesContentType`
 
@@ -170,15 +183,17 @@ A union type containing valid message content types.
 type QueuesContentType = "text" | "bytes" | "json" | "v8";
 ```
 
-- Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
-- Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
-- Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
-- Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+* Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
+* Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
+* Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+* Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
 
 :::note
 
+
 The default content type for Queues changed to `json` (from `v8`) to improve compatibility with pull-based consumers for any Workers with a [compatibility date](/workers/configuration/compatibility-flags/#queues-send-messages-in-json-format) after `2024-03-18`.
 
+
 :::
 
 If you specify an invalid content type, or if your specified content type does not match the message content's type, the send operation will fail with an error.
@@ -195,11 +210,15 @@ interface QueueSendResult {
 }
 ```
 
-- <code>metadata</code> <Type text="object" />
-  - Contains metadata about the queue after the send operation.
 
-- <code>metadata.metrics</code> <Type text="QueueMetrics" />
-  - Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
+
+* <code>metadata</code> <Type text="object" />
+
+  * Contains metadata about the queue after the send operation.
+
+* <code>metadata.metrics</code> <Type text="QueueMetrics" />
+
+  * Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
 
 ### `QueueMetrics`
 
@@ -213,14 +232,19 @@ interface QueueMetrics {
 }
 ```
 
-- <code>backlogCount</code> <Type text="number" />
-  - The number of messages currently in the queue.
 
-- <code>backlogBytes</code> <Type text="number" />
-  - The total size of messages in the queue, in bytes.
 
-- <code>oldestMessageTimestamp</code> <Type text="number" />
-  - The timestamp (in milliseconds since epoch) of the oldest message in the queue.
+* <code>backlogCount</code> <Type text="number" />
+
+  * The number of messages currently in the queue.
+
+* <code>backlogBytes</code> <Type text="number" />
+
+  * The total size of messages in the queue, in bytes.
+
+* <code>oldestMessageTimestamp</code> <Type text="number" />
+
+  * The timestamp (in milliseconds since epoch) of the oldest message in the queue.
 
 ## Consumer
 
@@ -238,8 +262,10 @@ If the `queue()` function throws, or the promise returned by it or any of the pr
 
 :::note
 
+
 `waitUntil()` is the only supported method to run tasks (such as logging or metrics calls) that resolve after a queue handler has completed. Promises that have not resolved by the time the queue handler returns may not complete and will not block completion of execution.
 
+
 :::
 
 <Tabs syncKey="workersExamples">
@@ -278,19 +304,19 @@ You can type queue messages with `Queue<T>` on the producer and `ExportedHandler
 
 ```ts
 type MyMessage = {
-	id: string;
+  id: string;
 };
 
 interface Env {
-	MY_QUEUE: Queue<MyMessage>;
+  MY_QUEUE: Queue<MyMessage>;
 }
 
 export default {
-	async queue(batch) {
-		for (const message of batch.messages) {
-			console.log(message.body.id);
-		}
-	},
+  async queue(batch) {
+    for (const message of batch.messages) {
+      console.log(message.body.id);
+    }
+  },
 } satisfies ExportedHandler<Env, MyMessage>;
 ```
 
@@ -299,7 +325,7 @@ For primitive messages, use `Queue<number>` or `satisfies ExportedHandler<Env, n
 Or alternatively, a queue consumer can be written using the (deprecated) service worker syntax:
 
 ```js
-addEventListener("queue", (event) => {
+addEventListener('queue', (event) => {
 	event.waitUntil(handleMessages(event));
 });
 ```
@@ -308,8 +334,10 @@ In service worker syntax, `event` provides the same fields and methods as `Messa
 
 :::note
 
+
 When performing asynchronous tasks in your queue handler that iterates through messages, use an asynchronous version of iterating through your messages. For example, `for (const m of batch.messages)`or `await Promise.all(batch.messages.map(work))` allow for waiting for the results of asynchronous calls. `batch.messages.forEach()` does not.
 
+
 :::
 
 ### `MessageBatch`
@@ -318,25 +346,34 @@ A batch of messages that are sent to a consumer Worker.
 
 ```ts
 interface MessageBatch<Body = unknown> {
-	readonly queue: string;
-	readonly messages: readonly Message<Body>[];
-	ackAll(): void;
-	retryAll(options?: QueueRetryOptions): void;
+  readonly queue: string;
+  readonly messages: readonly Message<Body>[];
+  ackAll(): void;
+  retryAll(options?: QueueRetryOptions): void;
 }
 ```
 
-- <code>queue</code> <Type text="string" />
-  - The name of the Queue that belongs to this batch.
 
-- <code>messages</code> <Type text="Message[]" />
-  - An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
 
-- <code>ackAll()</code> <Type text="void" />
-  - Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+* <code>queue</code> <Type text="string" />
+
+  * The name of the Queue that belongs to this batch.
+
+* <code>messages</code> <Type text="Message[]" />
+
+  * An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
+
+* <code>ackAll()</code> <Type text="void" />
+
+
+  * Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+
+* <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
+
+  * Marks every message to be retried in the next batch.
+  * Supports an optional `options` object.
+
 
-- <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
-  - Marks every message to be retried in the next batch.
-  - Supports an optional `options` object.
 
 ### `Message`
 
@@ -344,34 +381,44 @@ A message that is sent to a consumer Worker.
 
 ```ts
 interface Message<Body = unknown> {
-	readonly id: string;
-	readonly timestamp: Date;
-	readonly body: Body;
+  readonly id: string;
+  readonly timestamp: Date;
+  readonly body: Body;
 	readonly attempts: number;
-	ack(): void;
-	retry(options?: QueueRetryOptions): void;
+  ack(): void;
+  retry(options?: QueueRetryOptions): void;
 }
 ```
 
-- <code>id</code> <Type text="string" />
-  - A unique, system-generated ID for the message.
 
-- <code>timestamp</code> <Type text="Date" />
-  - A timestamp when the message was sent.
 
-- <code>body</code> <Type text="unknown" />
-  - The body of the message.
-  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+* <code>id</code> <Type text="string" />
+
+  * A unique, system-generated ID for the message.
+
+* <code>timestamp</code> <Type text="Date" />
+
+  * A timestamp when the message was sent.
+
+* <code>body</code> <Type text="unknown" />
+
+  * The body of the message.
+  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+
+* <code>attempts</code> <Type text="number" />
+
+	* The number of times the consumer has attempted to process this message. Starts at 1.
+
+* <code>ack()</code> <Type text="void" />
+
+  * Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+
+* <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
 
-- <code>attempts</code> <Type text="number" />
-  - The number of times the consumer has attempted to process this message. Starts at 1.
+  * Marks a message to be retried in the next batch.
+  * Supports an optional `options` object.
 
-- <code>ack()</code> <Type text="void" />
-  - Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
-- <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
-  - Marks a message to be retried in the next batch.
-  - Supports an optional `options` object.
 
 ### `QueueRetryOptions`
 
@@ -379,13 +426,13 @@ Optional configuration when marking a message or a batch of messages for retry.
 
 ```ts
 interface QueueRetryOptions {
-	delaySeconds?: number;
+  delaySeconds?: number;
 }
 ```
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be a positive integer.
+* <code>delaySeconds</code> <Type text="number" />
 
-- When the promise resolves, the messages are written to disk.
-  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be a positive integer.
+* When the promise resolves, the messages are written to disk.
+  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
diff --git a/src/content/docs/queues/configuration/local-development.mdx b/src/content/docs/queues/configuration/local-development.mdx
index 557fb80e5c067c5..69ba57856a90286 100644
--- a/src/content/docs/queues/configuration/local-development.mdx
+++ b/src/content/docs/queues/configuration/local-development.mdx
@@ -23,7 +23,6 @@ To develop locally with Queues, you will need:
 ## Start a local development session
 
 Open your terminal and run the following commands to start a local development session:
-
 ```sh
 npx wrangler@latest dev
 ```
@@ -41,15 +40,13 @@ Local development sessions create a standalone, local-only environment that mirr
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/general/#dev) to learn more about how to configure a local development session.
 
 ## Separating producer & consumer Workers
-
 Wrangler supports running multiple Workers simultaneously with a single command. If your architecture separates the producer and consumer into distinct Workers, you can use this functionality to test the entire message flow locally.
 
 :::caution
 Support for running multiple Workers at once with one Wrangler command is experimental, and subject to change as we work on the experience. If you run into bugs or have any feedback, [open an issue on the workers-sdk repository](https://github.com/cloudflare/workers-sdk/issues/new)
 :::
 
-For example, if your project has the following directory structure:
-
+For example, if your project has the following directory structure: 
 ```
 producer-worker/
 ├── wrangler.jsonc
@@ -60,7 +57,6 @@ producer-worker/
 ```
 
 You can start development servers for both workers with the following command:
-
 ```sh
 npx wrangler@latest dev -c wrangler.jsonc -c consumer-worker/wrangler.jsonc --persist-to .wrangler/state
 ```
@@ -71,5 +67,4 @@ When the producer Worker sends messages to the queue, the consumer Worker will a
 :::
 
 ## Known Issues
-
 - Queues does not support Wrangler remote mode (`wrangler dev --remote`).
diff --git a/src/content/docs/queues/configuration/pause-purge.mdx b/src/content/docs/queues/configuration/pause-purge.mdx
index aa3e793a9a0dc2e..0ca72cdbb02b121 100644
--- a/src/content/docs/queues/configuration/pause-purge.mdx
+++ b/src/content/docs/queues/configuration/pause-purge.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - queues
 ---
-
 import { WranglerConfig, Type, MetaInfo } from "~/components";
 
 ## Pause Delivery
@@ -39,11 +38,9 @@ $ npx wrangler queues resume-delivery <QUEUE-NAME>
   - The name of the queue for which delivery should be resumed.
 
 ### What happens to HTTP Pull consumers with a paused queue?
-
 When a queue is paused, messages cannot be pulled by an [HTTP pull based consumer](/queues/configuration/pull-consumers). Requests to pull messages will receive a `409` response, along with an error message stating `queue_delivery_paused`.
 
 ## Purge queue
-
 Purging a queue permanently deletes any messages currently stored in the Queue. Purging is useful while developing a new application, especially to clear out any test data. It can also be useful in production to handle scenarios when a batch of bad messages have been sent to a Queue.
 
 Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the queue.
@@ -53,9 +50,7 @@ Purging a queue is an irreversible operation. Make sure to use this operation ca
 :::
 
 ### Purge queue using Wrangler
-
 The following command will purge messages from your queue. You will be prompted to enter the queue name to confirm the operation.
-
 ```sh
 $ npx wrangler queues purge <QUEUE-NAME>
 
@@ -63,5 +58,4 @@ This operation will permanently delete all the messages in Queue <QUEUE-NAME>. T
 ```
 
 ### Does purging a Queue affect my bill?
-
 Purging a queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.
diff --git a/src/content/docs/queues/event-subscriptions/index.mdx b/src/content/docs/queues/event-subscriptions/index.mdx
index 8d7a0aa847de518..7fea1b1b89a7a1d 100644
--- a/src/content/docs/queues/event-subscriptions/index.mdx
+++ b/src/content/docs/queues/event-subscriptions/index.mdx
@@ -12,7 +12,7 @@ products:
   - workers
 ---
 
-import { LinkCard } from "~/components";
+import { LinkCard } from "~/components"
 
 Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products (e.g., [KV](/kv/), [Workers AI](/workers-ai), [Workers](/workers)) can publish structured events to a queue, which you can then consume with Workers or [HTTP pull consumers](/queues/configuration/pull-consumers/) to build custom workflows, integrations, or logic.
 
@@ -34,4 +34,4 @@ An event is a structured record of something happening in your Cloudflare accoun
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event types and their corresponding data schemas."
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
index d7dc089f45b0751..aa2f5a7998b8f6d 100644
--- a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
+++ b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
@@ -8,7 +8,11 @@ sidebar:
   order: 1
 ---
 
-import { Steps, LinkCard, DashButton } from "~/components";
+import {
+	Steps,
+	LinkCard,
+	DashButton,
+} from "~/components";
 
 Learn how to:
 
@@ -98,4 +102,4 @@ npx wrangler queues subscription delete <queue-name> --id <subscription-id>
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event sources and types that you can subscribe to."
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
index 4875bc7d1174f24..58bc8f327afbbc5 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
@@ -22,6 +22,7 @@ This allows you to write to a Queue from any service or programming language tha
 - A [queue created](/queues/get-started/#3-create-a-queue) via the [Cloudflare dashboard](https://dash.cloudflare.com) or the [wrangler CLI](/workers/wrangler/install-and-update/).
 - A Cloudflare API token with the `Queues Edit` permission.
 
+
 ### 1. Send a test message
 
 To make sure you successfully authenticate and write a message to your queue, use `curl` on the command line:
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
index fb595d622adf56c..45926ceeb6e587d 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
@@ -66,10 +66,7 @@ export default {
 			messages = await req.json();
 		} catch {
 			// Return a HTTP 400 (Bad Request) if the payload isn't JSON
-			return Response.json(
-				{ error: "payload not valid JSON" },
-				{ status: 400 },
-			);
+			return Response.json({ error: "payload not valid JSON" }, { status: 400 });
 		}
 
 		// Publish to the Queue
diff --git a/src/content/docs/queues/examples/send-errors-to-r2.mdx b/src/content/docs/queues/examples/send-errors-to-r2.mdx
index 0ff30d559be40f2..ba6649a7b277a6a 100644
--- a/src/content/docs/queues/examples/send-errors-to-r2.mdx
+++ b/src/content/docs/queues/examples/send-errors-to-r2.mdx
@@ -63,33 +63,33 @@ interface Env {
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			return doRequest(req);
-		} catch (e) {
-			const error: ErrorMessage = {
-				message: e instanceof Error ? e.message : String(e),
-				stack: e instanceof Error ? e.stack : undefined,
-			};
-			await env.ERROR_QUEUE.send(error);
-			return new Response(error.message, { status: 500 });
-		}
-	},
-	async queue(batch, env, ctx): Promise<void> {
-		let file = "";
-		for (const message of batch.messages) {
-			const error = message.body;
-			file += error.stack ?? error.message;
-			file += "\r\n";
-		}
-		await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      return doRequest(req);
+    } catch (e) {
+      const error: ErrorMessage = {
+        message: e instanceof Error ? e.message : String(e),
+        stack: e instanceof Error ? e.stack : undefined,
+      };
+      await env.ERROR_QUEUE.send(error);
+      return new Response(error.message, { status: 500 });
+    }
+  },
+  async queue(batch, env, ctx): Promise<void> {
+    let file = "";
+    for (const message of batch.messages) {
+      const error = message.body;
+      file += error.stack ?? error.message;
+      file += "\r\n";
+    }
+    await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
+  },
 } satisfies ExportedHandler<Env, ErrorMessage>;
 
 function doRequest(request: Request): Response {
-	if (Math.random() > 0.5) {
-		return new Response("Success!");
-	}
-	throw new Error("Failed!");
+  if (Math.random() > 0.5) {
+    return new Response("Success!");
+  }
+  throw new Error("Failed!");
 }
 ```
diff --git a/src/content/docs/queues/examples/send-messages-from-dash.mdx b/src/content/docs/queues/examples/send-messages-from-dash.mdx
index 1a2b6cc2f1b7455..6d384b6b6bd668a 100644
--- a/src/content/docs/queues/examples/send-messages-from-dash.mdx
+++ b/src/content/docs/queues/examples/send-messages-from-dash.mdx
@@ -22,14 +22,14 @@ To send messages from the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select the queue to send a message to.
 3. Select the **Messages** tab.
 4. Select **Send**.
 5. Choose your message **Content Type**: _Text_ or _JSON_.
-6. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
-7. Select **Send**.
+5. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
+6. Select **Send**.
 
 Your message will be sent to the queue.
 
diff --git a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
index 4803ac4d16c217c..481b9a11fe9e225 100644
--- a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
+++ b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
@@ -73,45 +73,45 @@ Extending the `DurableObject` base class makes your `Env` available on `this.env
 import { DurableObject } from "cloudflare:workers";
 
 interface Env {
-	YOUR_QUEUE: Queue;
-	YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
+  YOUR_QUEUE: Queue;
+  YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		// Assume each Durable Object is mapped to a userId in a query parameter
-		// In a production application, this will be a userId defined by your application
-		// that you validate (and/or authenticate) first.
-		const url = new URL(req.url);
-		const userIdParam = url.searchParams.get("userId");
-
-		if (userIdParam) {
-			// Get a stub that allows you to call that Durable Object
-			const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
-
-			// Pass the request to that Durable Object and await the response
-			// This invokes the constructor once on your Durable Object class (defined further down)
-			// on the first initialization, and the fetch method on each request.
-			// We pass the original Request to the Durable Object's fetch method
-			const response = await durableObjectStub.fetch(req);
-
-			// This would return "wrote to queue", but you could return any response.
-			return response;
-		}
-		return new Response("userId must be provided", { status: 400 });
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    // Assume each Durable Object is mapped to a userId in a query parameter
+    // In a production application, this will be a userId defined by your application
+    // that you validate (and/or authenticate) first.
+    const url = new URL(req.url);
+    const userIdParam = url.searchParams.get("userId");
+
+    if (userIdParam) {
+      // Get a stub that allows you to call that Durable Object
+      const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
+
+      // Pass the request to that Durable Object and await the response
+      // This invokes the constructor once on your Durable Object class (defined further down)
+      // on the first initialization, and the fetch method on each request.
+      // We pass the original Request to the Durable Object's fetch method
+      const response = await durableObjectStub.fetch(req);
+
+      // This would return "wrote to queue", but you could return any response.
+      return response;
+    }
+    return new Response("userId must be provided", { status: 400 });
+  },
 } satisfies ExportedHandler<Env>;
 
 export class YourDurableObject extends DurableObject<Env> {
-	async fetch(req: Request): Promise<Response> {
-		// Error handling elided for brevity.
-		// Publish to your queue
-		await this.env.YOUR_QUEUE.send({
-			id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
-			// Write any other properties to your queue
-		});
-
-		return new Response("wrote to queue");
-	}
+  async fetch(req: Request): Promise<Response> {
+    // Error handling elided for brevity.
+    // Publish to your queue
+    await this.env.YOUR_QUEUE.send({
+      id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
+      // Write any other properties to your queue
+    });
+
+    return new Response("wrote to queue");
+  }
 }
 ```
diff --git a/src/content/docs/queues/glossary.mdx b/src/content/docs/queues/glossary.mdx
index 4bb72d0ab69bbf6..845aecc4bdd10b3 100644
--- a/src/content/docs/queues/glossary.mdx
+++ b/src/content/docs/queues/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - queues
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Queues documentation.
 
diff --git a/src/content/docs/queues/observability/index.mdx b/src/content/docs/queues/observability/index.mdx
index 7becde1ad32ae99..c9ebe21e8103fb1 100644
--- a/src/content/docs/queues/observability/index.mdx
+++ b/src/content/docs/queues/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/observability/metrics.mdx b/src/content/docs/queues/observability/metrics.mdx
index 39c918a48ff366b..e003fb8ca5507e5 100644
--- a/src/content/docs/queues/observability/metrics.mdx
+++ b/src/content/docs/queues/observability/metrics.mdx
@@ -74,10 +74,10 @@ The `queueMessageOperationsAdaptiveGroups` dataset provides the following dimens
 
 You can access realtime backlog metrics via the [Queues REST API](/api/resources/queues/) and [JavaScript API](/queues/configuration/javascript-apis/). These metrics provide point-in-time values rather than aggregated data.
 
-| Metric                   | Field Name                    | Description                                                    |
-| ------------------------ | ----------------------------- | -------------------------------------------------------------- |
-| Backlog count            | `backlog_count`               | Number of messages currently in the queue                      |
-| Backlog bytes            | `backlog_bytes`               | Total size of messages in the queue, in bytes                  |
+| Metric                   | Field Name                 | Description                                                    |
+| ------------------------ | -------------------------- | -------------------------------------------------------------- |
+| Backlog count            | `backlog_count`            | Number of messages currently in the queue                      |
+| Backlog bytes            | `backlog_bytes`            | Total size of messages in the queue, in bytes                  |
 | Oldest message timestamp | `oldest_message_timestamp_ms` | Timestamp (in milliseconds) of the oldest message in the queue |
 
 To retrieve these metrics via the REST API, use the metrics endpoint (`/accounts/{account_id}/queues/{queue_id}/metrics`).
diff --git a/src/content/docs/queues/platform/index.mdx b/src/content/docs/queues/platform/index.mdx
index db2ed89685726c9..a227085598b92e9 100644
--- a/src/content/docs/queues/platform/index.mdx
+++ b/src/content/docs/queues/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/platform/limits.mdx b/src/content/docs/queues/platform/limits.mdx
index 7da1292c246a72b..4ca7f09527545a6 100644
--- a/src/content/docs/queues/platform/limits.mdx
+++ b/src/content/docs/queues/platform/limits.mdx
@@ -8,49 +8,42 @@ products:
   - queues
 ---
 
-import { Render, WranglerConfig } from "~/components";
+import { Render, WranglerConfig } from "~/components"
 
 :::caution
 The following limits apply to both Workers Paid and Workers Free plans with the exception of **Message Retention**, which is non-configurable at 24 hours for the Workers Free plan.
 :::
 
-| Feature                                                 | Limit                                                                                             |
-| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| Queues                                                  | 10,000 per account                                                                                |
-| Message size                                            | 128 KB <sup>1</sup>                                                                               |
-| Message retries                                         | 100                                                                                               |
-| Maximum consumer batch size                             | 100 messages                                                                                      |
-| Maximum messages per `sendBatch` call                   | 100 (or 256KB in total)                                                                           |
-| Maximum Batch wait time                                 | 60 seconds                                                                                        |
-| Per-queue message throughput                            | 5,000 messages per second <sup>2</sup>                                                            |
-| Message retention period <sup>3</sup>                   | [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration).        |
-| Per-queue backlog size <sup>4</sup>                     | 25GB                                                                                              |
-| Concurrent consumer invocations                         | 250 <sup>push-based only</sup>                                                                    |
-| Consumer duration (wall clock time)                     | 15 minutes <sup>5</sup>                                                                           |
-| [Consumer CPU time](/workers/platform/limits/#cpu-time) | [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) |
-| `visibilityTimeout` (pull-based queues)                 | 12 hours                                                                                          |
-| `delaySeconds` (when sending or retrying)               | 24 hours                                                                                          |
-
-<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100
-bytes of internal metadata that counts towards total message limits.
-
-<sup>2</sup> Exceeding the maximum message throughput will cause the `send()`
-and `sendBatch()` methods to throw an exception with a `Too Many Requests` error
-until your producer falls below the limit.
-
-<sup>3</sup> Messages in a queue that reach the maximum message retention are
-deleted from the queue. Queues does not delete messages in the same queue that
-have not reached this limit.
-
-<sup>4</sup> Individual queues that reach this limit will receive a `Storage
-Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
+| Feature                                       									| Limit                                                         |
+| ----------------------------------------------------------------| ------------------------------------------------------------- |
+| Queues                                        									| 10,000 per account								                            |
+| Message size                                  									| 128 KB <sup>1</sup>                                           |
+| Message retries                               									| 100                                                           |
+| Maximum consumer batch size                   									| 100 messages 								                                  |
+| Maximum messages per `sendBatch` call         									| 100 (or 256KB in total)                                       |
+| Maximum Batch wait time                       									| 60 seconds                                                    |
+| Per-queue message throughput    																| 5,000 messages per second <sup>2</sup>                        |
+| Message retention period <sup>3</sup>         									| [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration). |
+| Per-queue backlog size <sup>4</sup>           									| 25GB                                                          |
+| Concurrent consumer invocations               									| 250 <sup>push-based only</sup>                                |
+| Consumer duration (wall clock time) 														| 15 minutes <sup>5</sup>                                       |
+| [Consumer CPU time](/workers/platform/limits/#cpu-time)| [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) 							|
+| `visibilityTimeout` (pull-based queues)       									| 12 hours                                                      |
+| `delaySeconds` (when sending or retrying)     									| 24 hours                                                      |
+
+<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100 bytes of internal metadata that counts towards total message limits.
+
+<sup>2</sup> Exceeding the maximum message throughput will cause the `send()` and `sendBatch()` methods to throw an exception with a `Too Many Requests` error until your producer falls below the limit.
+
+<sup>3</sup> Messages in a queue that reach the maximum message retention are deleted from the queue. Queues does not delete messages in the same queue that have not reached this limit.
+
+<sup>4</sup> Individual queues that reach this limit will receive a `Storage Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
 
 <sup>5</sup> Refer to [Workers limits](/workers/platform/limits/#cpu-time).
 
 <Render file="limits_increase" product="workers" />
 
 ### Increasing Queue Consumer Worker CPU Limits
-
 [Queue consumer Workers](/queues/reference/how-queues-works/#consumers) are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#account-plan-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O.
 
 By default, the maximum CPU time per consumer Worker invocation is set to 30 seconds, but can be increased by setting `limits.cpu_ms` in your Wrangler configuration:
diff --git a/src/content/docs/queues/platform/pricing.mdx b/src/content/docs/queues/platform/pricing.mdx
index 0a2d005b5559044..f8336c97f5b08a3 100644
--- a/src/content/docs/queues/platform/pricing.mdx
+++ b/src/content/docs/queues/platform/pricing.mdx
@@ -11,7 +11,7 @@ products:
   - queues
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="queues_pricing" product="workers" />
 
@@ -19,16 +19,23 @@ import { Render } from "~/components";
 
 If an application writes, reads and deletes (consumes) one million messages a day (in a 30 day month), and each message is less than 64 KB in size, the estimated bill for the month would be:
 
+
+
 |                     | Total Usage           | Free Usage | Billed Usage | Price      |
 | ------------------- | --------------------- | ---------- | ------------ | ---------- |
 | Standard operations | 3 \* 30 \* 1,000,000  | 1,000,000  | 89,000,000   | $35.60     |
 |                     | (write, read, delete) |            |              |            |
 | **TOTAL**           |                       |            |              | **$35.60** |
 
+
+
 An application that writes, reads and deletes (consumes) 100 million \~127 KB messages (each message counts as two 64 KB chunks) per month would have an estimated bill resembling the following:
 
+
+
 |                     | Total Usage                  | Free Usage | Billed Usage | Price       |
 | ------------------- | ---------------------------- | ---------- | ------------ | ----------- |
 | Standard operations | 2 \* 3 \* 100 \* 1,000,000   | 1,000,000  | 599,000,000  | $239.60     |
 |                     | (2x ops for > 64KB messages) |            |              |             |
 | **TOTAL**           |                              |            |              | **$239.60** |
+
diff --git a/src/content/docs/queues/reference/delivery-guarantees.mdx b/src/content/docs/queues/reference/delivery-guarantees.mdx
index bd589fd8317c267..1f78e3276a09305 100644
--- a/src/content/docs/queues/reference/delivery-guarantees.mdx
+++ b/src/content/docs/queues/reference/delivery-guarantees.mdx
@@ -12,8 +12,8 @@ Delivery guarantees define how strongly a messaging system enforces the delivery
 
 As you make stronger guarantees about message delivery, the system needs to perform more checks and acknowledgments to ensure that messages are delivered, or maintain state to ensure a message is only delivered the specified number of times. This increases the latency of the system and reduces the overall throughput of the system. Each message may require an additional internal acknowledgements, and an equivalent number of additional roundtrips, before it can be considered delivered.
 
-- **Queues provides _at least once_ delivery by default** in order to optimize for reliability.
-- This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
-- For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
+* **Queues provides *at least once* delivery by default** in order to optimize for reliability.
+* This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
+* For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
 
 In cases where processing the same message more than once would introduce unintended behaviour, generating a unique ID when writing the message to the queue and using that as the primary key on database inserts and/or as an idempotency key to de-duplicate the message after processing. For example, using this idempotency key as the ID in an upstream email API or payment API will allow those services to reject the duplicate on your behalf, without you having to carry additional state in your application.
diff --git a/src/content/docs/queues/reference/error-codes.mdx b/src/content/docs/queues/reference/error-codes.mdx
index 94d502fd00435b6..1a227b114e29bfe 100644
--- a/src/content/docs/queues/reference/error-codes.mdx
+++ b/src/content/docs/queues/reference/error-codes.mdx
@@ -17,7 +17,7 @@ For the [JavaScript APIs](/queues/configuration/javascript-apis/), Queues operat
 ```js
 try {
 	await env.MY_QUEUE.send("message", { delaySeconds: 999999 });
-	return new Response("Sent message to the queue");
+    return new Response("Sent message to the queue");
 } catch (error) {
 	console.error(error);
 	return new Response("Failed to send message to the queue", { status: 500 });
@@ -28,18 +28,20 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ```json
 {
-	"errors": [
-		{
-			"code": 7003,
-			"message": "No route for the URI",
-			"documentation_url": "documentation_url",
-			"source": {
-				"pointer": "pointer"
-			}
-		}
-	],
-	"messages": ["string"],
-	"success": true
+  "errors": [
+    {
+      "code": 7003,
+      "message": "No route for the URI",
+      "documentation_url": "documentation_url",
+      "source": {
+        "pointer": "pointer"
+      }
+    }
+  ],
+  "messages": [
+    "string"
+  ],
+  "success": true
 }
 ```
 
@@ -47,19 +49,19 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ### Client side errors
 
-| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                           |
-| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                           |
-| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                |
-| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                 |
-| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                           |
-| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                       |
+| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                                                                                       |
+| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                                                                                       |
+| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                                                                            |
+| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                                                                             |
+| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                                                                                       |
+| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                                                                                   |
 | 10203      | MessageMetadataInvalid   | Invalid message metadata (includes invalid content type and invalid delay) | Ensure `contentType` is one of `text`, `bytes`, `json`, or `v8`. Ensure the message delay does not exceed the [maximum of 24 hours](/queues/platform/limits/) |
-| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                               |
-| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                 |
-| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                          |
-| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                             |
-| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                    |
+| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                                                                                           |
+| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                                                                             |
+| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                                                                                      |
+| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                                                                                         |
+| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                                                                                                                         |
 
 ### 429 type errors
 
diff --git a/src/content/docs/queues/reference/how-queues-works.mdx b/src/content/docs/queues/reference/how-queues-works.mdx
index 807d34b52e91d6c..efc649900122fdd 100644
--- a/src/content/docs/queues/reference/how-queues-works.mdx
+++ b/src/content/docs/queues/reference/how-queues-works.mdx
@@ -29,9 +29,9 @@ Queues does not guarantee that messages will be delivered to a consumer in the s
 
 Developers can create multiple queues. Creating multiple queues can be useful to:
 
-- Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
-- Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
-- Configure different batching strategies for each consumer connected to a queue.
+* Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
+* Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
+* Configure different batching strategies for each consumer connected to a queue.
 
 For most applications, a single producer Worker per queue, with a single consumer Worker consuming messages from that queue allows you to logically separate the processing for each of your queues.
 
@@ -43,29 +43,31 @@ For example, if we bound a queue named `my-first-queue` to a binding of `MY_FIRS
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		const message = {
-			url: req.url,
-			method: req.method,
-			headers: Object.fromEntries(req.headers),
-		};
-
-		await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
-		return new Response("Sent!");
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    const message = {
+      url: req.url,
+      method: req.method,
+      headers: Object.fromEntries(req.headers),
+    };
+
+    await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
+    return new Response("Sent!");
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
 :::note
 
+
 You can also use [`context.waitUntil()`](/workers/runtime-apis/context/#waituntil) to send the message without blocking the response.
 
 Note that because `waitUntil()` is non-blocking, any errors raised from the `send()` or `sendBatch()` methods on a queue will be implicitly ignored.
 
+
 :::
 
 A queue can have multiple producer Workers. For example, you may have multiple producer Workers writing events or logs to a shared queue based on incoming HTTP requests from users. There is no limit to the total number of producer Workers that can write to a single queue.
@@ -80,25 +82,25 @@ To explicitly set the content type or specify an alternative content type, pass
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		const message = {
-			url: req.url,
-			method: req.method,
-			headers: Object.fromEntries(req.headers),
-		};
-		try {
-			await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
-			return new Response("Sent!");
-		} catch (e) {
-			// Catch cases where send fails, including due to a mismatched content type
-			const msg = e instanceof Error ? e.message : "Unknown error";
-			return Response.json({ error: msg }, { status: 500 });
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    const message = {
+      url: req.url,
+      method: req.method,
+      headers: Object.fromEntries(req.headers),
+    };
+    try {
+      await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
+      return new Response("Sent!");
+    } catch (e) {
+      // Catch cases where send fails, including due to a mismatched content type
+      const msg = e instanceof Error ? e.message : "Unknown error";
+      return Response.json({ error: msg }, { status: 500 });
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -106,21 +108,21 @@ To only accept simple strings when writing to a queue, set `{ contentType: "text
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			// This will throw an exception (error) if you pass a non-string to the queue,
-			// such as a native JavaScript object or ArrayBuffer.
-			await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
-			return new Response("Sent!");
-		} catch (e) {
-			const msg = e instanceof Error ? e.message : "Unknown error";
-			return Response.json({ error: msg }, { status: 500 });
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      // This will throw an exception (error) if you pass a non-string to the queue,
+      // such as a native JavaScript object or ArrayBuffer.
+      await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
+      return new Response("Sent!");
+    } catch (e) {
+      const msg = e instanceof Error ? e.message : "Unknown error";
+      return Response.json({ error: msg }, { status: 500 });
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -137,22 +139,22 @@ A queue can only have one type of consumer configured.
 
 ### Create a consumer Worker
 
-A consumer is the term for a client that is subscribing to or _consuming_ messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
+A consumer is the term for a client that is subscribing to or *consuming* messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
 
 ```ts
 interface Env {
-	// Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
+  // Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
 }
 
 export default {
-	async queue(batch, env, ctx): Promise<void> {
-		// Do something with messages in the batch
-		// i.e. write to R2 storage, D1 database, or POST to an external API
-		for (const msg of batch.messages) {
-			// Process each message
-			console.log(msg.body);
-		}
-	},
+  async queue(batch, env, ctx): Promise<void> {
+    // Do something with messages in the batch
+    // i.e. write to R2 storage, D1 database, or POST to an external API
+    for (const msg of batch.messages) {
+      // Process each message
+      console.log(msg.body);
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -180,40 +182,42 @@ Importantly, each queue can only have one active consumer. This allows Cloudflar
 
 :::note[Best practice]
 
+
 Configure a single consumer per queue. This both logically separates your queues, and ensures that errors (failures) in processing messages from one queue do not impact your other queues.
 
+
 :::
 
 Notably, you can use the same consumer with multiple queues. The queue handler that defines your consumer Worker will be invoked by the queues it is connected to.
 
-- The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
-- This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
+* The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
+* This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
 
 For example, a consumer configured to consume messages from multiple queues would resemble the following:
 
 ```ts
 interface Env {
-	// Add your bindings here
+  // Add your bindings here
 }
 
 export default {
-	async queue(batch, env, ctx): Promise<void> {
-		// MessageBatch has a `queue` property we can switch on
-		switch (batch.queue) {
-			case "log-queue":
-				// Write the batch to R2
-				break;
-			case "debug-queue":
-				// Write the message to the console or to another queue
-				break;
-			case "email-reset":
-				// Trigger a password reset email via an external API
-				break;
-			default:
-				// Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
-				break;
-		}
-	},
+  async queue(batch, env, ctx): Promise<void> {
+    // MessageBatch has a `queue` property we can switch on
+    switch (batch.queue) {
+      case "log-queue":
+        // Write the batch to R2
+        break;
+      case "debug-queue":
+        // Write the message to the console or to another queue
+        break;
+      case "email-reset":
+        // Trigger a password reset email via an external API
+        break;
+      default:
+        // Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
+        break;
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
diff --git a/src/content/docs/queues/reference/index.mdx b/src/content/docs/queues/reference/index.mdx
index a4b4b60c39f76b3..5470c10d9bcf385 100644
--- a/src/content/docs/queues/reference/index.mdx
+++ b/src/content/docs/queues/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
index 1f5af0257e338e5..ca3746a34a661dd 100644
--- a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
+++ b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
@@ -27,15 +27,15 @@ This page summarizes supported features, limitations, and best practices.
 | 173 scalar functions                                    | Yes       | Math, string, datetime, regex, crypto, array, map, struct, JSON              |
 | 33 aggregate functions                                  | Yes       | Basic, approximate, statistical, bitwise, boolean, positional                |
 | Approximate aggregates                                  | Yes       | `approx_distinct`, `approx_median`, `approx_percentile_cont`, `approx_top_k` |
-| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions              |
+| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions           |
 | CTEs (`WITH ... AS`)                                    | Yes       | Can reference different tables and include JOINs                             |
 | JOINs (INNER, LEFT, RIGHT, FULL OUTER, CROSS)           | Yes       | All standard join types                                                      |
-| Implicit joins (comma FROM)                             | Yes       |                                                                              |
-| Subqueries (`IN`, `NOT IN`)                             | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
-| Subqueries (`EXISTS`, `NOT EXISTS`)                     | Yes       | semi-join and anti-join patterns                                             |
-| Scalar subqueries                                       | Yes       | In SELECT, WHERE, HAVING                                                     |
-| Derived tables (FROM subqueries)                        | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
-| Self-joins                                              | Yes       | Same table with different aliases                                            |
+| Implicit joins (comma FROM)                              | Yes       |                                                                              |
+| Subqueries (`IN`, `NOT IN`)                              | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
+| Subqueries (`EXISTS`, `NOT EXISTS`)                      | Yes       | semi-join and anti-join patterns                                             |
+| Scalar subqueries                                        | Yes       | In SELECT, WHERE, HAVING                                                     |
+| Derived tables (FROM subqueries)                         | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
+| Self-joins                                               | Yes       | Same table with different aliases                                            |
 | Window functions (`OVER`)                               | No        |                                                                              |
 | `SELECT DISTINCT`                                       | No        | Use `approx_distinct`                                                        |
 | `OFFSET`                                                | No        |                                                                              |
@@ -49,44 +49,44 @@ For the full SQL syntax, refer to the [SQL reference](/r2-sql/sql-reference/).
 
 ## Unsupported SQL features
 
-| Feature                                                                       | Error                                                   |
-| :---------------------------------------------------------------------------- | :------------------------------------------------------ |
-| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported` |
-| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`   |
-| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                            |
-| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`   |
-| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                    |
-| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                    |
-| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                           |
-| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                           |
-| Nested (parenthesized) joins                                                  | Not supported                                           |
-| `LATERAL` derived tables                                                      | Not supported                                           |
-| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                           |
+| Feature                                                                       | Error                                                    |
+| :---------------------------------------------------------------------------- | :------------------------------------------------------- |
+| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported`  |
+| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`    |
+| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                             |
+| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`    |
+| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                     |
+| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                     |
+| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                            |
+| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                            |
+| Nested (parenthesized) joins                                                  | Not supported                                            |
+| `LATERAL` derived tables                                                      | Not supported                                            |
+| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                            |
 
 ---
 
 ## Unsupported expression patterns
 
-| Pattern                               | Alternative                                                                                       |
-| :------------------------------------ | :------------------------------------------------------------------------------------------------ |
-| `func(DISTINCT ...)` on any aggregate | Use `approx_distinct` for counting                                                                |
-| `PERCENTILE_CONT` / `PERCENTILE_DISC` | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
-| `MEDIAN`                              | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
-| `ARRAY_AGG`                           | No alternative (unsupported for memory safety)                                                    |
-| `STRING_AGG`                          | No alternative (unsupported for memory safety)                                                    |
-| `NOT IN` subquery on nullable columns | Use `NOT EXISTS` with a correlated subquery instead                                               |
+| Pattern                                                 | Alternative                                                                                       |
+| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------ |
+| `func(DISTINCT ...)` on any aggregate                   | Use `approx_distinct` for counting                                                                |
+| `PERCENTILE_CONT` / `PERCENTILE_DISC`                   | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
+| `MEDIAN`                                                | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
+| `ARRAY_AGG`                                             | No alternative (unsupported for memory safety)                                                    |
+| `STRING_AGG`                                            | No alternative (unsupported for memory safety)                                                    |
+| `NOT IN` subquery on nullable columns                   | Use `NOT EXISTS` with a correlated subquery instead                                               |
 
 ---
 
 ## Runtime constraints
 
-| Constraint                           | Details                                                                                                                                                                                    |
-| :----------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Constraint                           | Details                                                                                               |
+| :----------------------------------- | :---------------------------------------------------------------------------------------------------- |
 | Multi-table queries                  | JOINs, subqueries (IN, EXISTS, scalar, derived tables), and multi-table CTEs are supported. Performance depends on intermediate result size; use WHERE filters to manage join selectivity. |
-| Partitioned and unpartitioned tables | Both partitioned and unpartitioned Iceberg tables are supported.                                                                                                                           |
-| Parquet format only                  | No CSV, JSON, or other formats.                                                                                                                                                            |
-| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                                                                                                       |
-| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                                                                                                            |
+| Partitioned and unpartitioned tables  | Both partitioned and unpartitioned Iceberg tables are supported.                                       |
+| Parquet format only                  | No CSV, JSON, or other formats.                                                                       |
+| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                  |
+| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                       |
 
 ---
 
diff --git a/src/content/docs/r2-sql/reference/wrangler-commands.mdx b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
index f9765698d06f77d..26a591c683434f5 100644
--- a/src/content/docs/r2-sql/reference/wrangler-commands.mdx
+++ b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { Render, Type, MetaInfo } from "~/components";
 
-<Render file="wrangler-commands/r2-sql" product="workers" />
+<Render file="wrangler-commands/r2-sql" product="workers" />
\ No newline at end of file
diff --git a/src/content/docs/r2-sql/sql-reference/index.mdx b/src/content/docs/r2-sql/sql-reference/index.mdx
index 58ed3641062a224..70227b97d4db20a 100644
--- a/src/content/docs/r2-sql/sql-reference/index.mdx
+++ b/src/content/docs/r2-sql/sql-reference/index.mdx
@@ -194,14 +194,14 @@ R2 SQL supports joining multiple Iceberg tables in a single query. All join type
 
 ### Supported join types
 
-| Join type        | Syntax                            | Description                                                        |
-| :--------------- | :-------------------------------- | :----------------------------------------------------------------- |
-| Inner join       | `INNER JOIN ... ON`               | Returns rows that match in both tables                             |
-| Left outer join  | `LEFT JOIN ... ON`                | Returns all rows from the left table, NULLs for non-matching right |
-| Right outer join | `RIGHT JOIN ... ON`               | Returns all rows from the right table, NULLs for non-matching left |
-| Full outer join  | `FULL OUTER JOIN ... ON`          | Returns all rows from both tables, NULLs where no match            |
-| Cross join       | `CROSS JOIN`                      | Cartesian product of both tables                                   |
-| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id` | Comma-separated tables with join condition in `WHERE`              |
+| Join type        | Syntax                              | Description                                                        |
+| :--------------- | :---------------------------------- | :----------------------------------------------------------------- |
+| Inner join       | `INNER JOIN ... ON`                 | Returns rows that match in both tables                             |
+| Left outer join  | `LEFT JOIN ... ON`                  | Returns all rows from the left table, NULLs for non-matching right |
+| Right outer join | `RIGHT JOIN ... ON`                 | Returns all rows from the right table, NULLs for non-matching left |
+| Full outer join  | `FULL OUTER JOIN ... ON`            | Returns all rows from both tables, NULLs where no match            |
+| Cross join       | `CROSS JOIN`                        | Cartesian product of both tables                                   |
+| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id`  | Comma-separated tables with join condition in `WHERE`              |
 
 ### Syntax
 
@@ -264,7 +264,6 @@ SELECT * FROM (t1 JOIN t2 ON t1.id = t2.id) JOIN t3 ON t2.id = t3.id
 -- Supported
 SELECT * FROM t1 JOIN t2 ON t1.id = t2.id JOIN t3 ON t2.id = t3.id
 ```
-
 :::
 
 ### Best practices for joins
@@ -359,7 +358,6 @@ WHERE NOT EXISTS (
 )
 LIMIT 20
 ```
-
 :::
 
 ### `EXISTS` / `NOT EXISTS` subqueries
diff --git a/src/content/docs/r2/api/error-codes.mdx b/src/content/docs/r2/api/error-codes.mdx
index 27e9cbdf09979fb..49ec6f7e7bff0ec 100644
--- a/src/content/docs/r2/api/error-codes.mdx
+++ b/src/content/docs/r2/api/error-codes.mdx
@@ -16,10 +16,10 @@ For the **Workers API**, R2 operations throw exceptions that you can catch. The
 
 ```js
 try {
-	await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
+  await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
 } catch (error) {
-	console.error(error.message);
-	// "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
+  console.error(error.message);
+  // "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
 }
 ```
 
@@ -37,59 +37,59 @@ For the **S3-compatible API**, errors are returned as XML in the response body:
 
 ### Authentication and authorization errors
 
-| Error Code | S3 Code               | HTTP Status | Details                                                | Recommended Fix                                                                                         |
-| ---------- | --------------------- | ----------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
-| 10002      | Unauthorized          | 401         | Missing or invalid authentication credentials.         | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired.    |
-| 10003      | AccessDenied          | 403         | Insufficient permissions for the requested operation.  | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
-| 10018      | ExpiredRequest        | 400         | Presigned URL or request signature has expired.        | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature.                                |
-| 10035      | SignatureDoesNotMatch | 403         | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues.                            |
-| 10042      | NotEntitled           | 403         | Account not entitled to this feature.                  | Ensure your account has an [R2 subscription](/r2/pricing/).                                             |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10002 | Unauthorized | 401 | Missing or invalid authentication credentials. | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired. |
+| 10003 | AccessDenied | 403 | Insufficient permissions for the requested operation. | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
+| 10018 | ExpiredRequest | 400 | Presigned URL or request signature has expired. | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature. |
+| 10035 | SignatureDoesNotMatch | 403 | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues. |
+| 10042 | NotEntitled | 403 | Account not entitled to this feature. | Ensure your account has an [R2 subscription](/r2/pricing/). |
 
 ### Bucket errors
 
-| Error Code | S3 Code           | HTTP Status | Details                                                     | Recommended Fix                                                                                       |
-| ---------- | ----------------- | ----------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| 10005      | InvalidBucketName | 400         | Bucket name does not meet naming requirements.              | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric.     |
-| 10006      | NoSuchBucket      | 404         | The specified bucket does not exist.                        | Verify the bucket name is correct and the bucket exists in your account.                              |
-| 10008      | BucketNotEmpty    | 409         | Cannot delete bucket that contains objects.                 | Delete all objects in the bucket before deleting the bucket.                                          |
-| 10009      | TooManyBuckets    | 400         | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
-| 10073      | BucketConflict    | 409         | Bucket name already exists.                                 | Choose a different bucket name. Bucket names must be unique within your account.                      |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10005 | InvalidBucketName | 400 | Bucket name does not meet naming requirements. | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric. |
+| 10006 | NoSuchBucket | 404 | The specified bucket does not exist. | Verify the bucket name is correct and the bucket exists in your account. |
+| 10008 | BucketNotEmpty | 409 | Cannot delete bucket that contains objects. | Delete all objects in the bucket before deleting the bucket. |
+| 10009 | TooManyBuckets | 400 | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
+| 10073 | BucketConflict | 409 | Bucket name already exists. | Choose a different bucket name. Bucket names must be unique within your account. |
 
 ### Object errors
 
-| Error Code | S3 Code                    | HTTP Status | Details                                                                                                                                                         | Recommended Fix                                                                                                                   |
-| ---------- | -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| 10007      | NoSuchKey                  | 404         | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted.                                                             |
-| 10020      | InvalidObjectName          | 400         | Object key contains invalid characters or is too long.                                                                                                          | Use valid UTF-8 characters. Maximum key length is 1024 bytes.                                                                     |
-| 100100     | EntityTooLarge             | 400         | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart).                                                                                     | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
-| 10012      | MetadataTooLarge           | 400         | Custom metadata exceeds the 8,192 byte limit.                                                                                                                   | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata.                                                |
-| 10069      | ObjectLockedByBucketPolicy | 403         | Object is protected by a bucket lock rule and cannot be modified or deleted.                                                                                    | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/).                                      |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10007 | NoSuchKey | 404 | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted. |
+| 10020 | InvalidObjectName | 400 | Object key contains invalid characters or is too long. | Use valid UTF-8 characters. Maximum key length is 1024 bytes. |
+| 100100 | EntityTooLarge | 400 | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart). | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
+| 10012 | MetadataTooLarge | 400 | Custom metadata exceeds the 8,192 byte limit. | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata. |
+| 10069 | ObjectLockedByBucketPolicy | 403 | Object is protected by a bucket lock rule and cannot be modified or deleted. | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/). |
 
 ### Upload and request errors
 
-| Error Code | S3 Code              | HTTP Status | Details                                                                           | Recommended Fix                                                                                                                                                                     |
-| ---------- | -------------------- | ----------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10033      | MissingContentLength | 411         | `Content-Length` header required but missing.                                     | Include the `Content-Length` header in PUT/POST requests.                                                                                                                           |
-| 10013      | IncompleteBody       | 400         | Request body terminated before expected `Content-Length`.                         | Ensure the full request body is sent. Check for network interruptions or client timeouts.                                                                                           |
-| 10014      | InvalidDigest        | 400         | Checksum header format is malformed.                                              | Ensure checksums are properly encoded (base64 for SHA/CRC checksums).                                                                                                               |
-| 10037      | BadDigest            | 400         | Provided checksum does not match the uploaded content.                            | Verify data integrity and retry the upload.                                                                                                                                         |
-| 10039      | InvalidRange         | 416         | Requested byte range is not satisfiable.                                          | Ensure the range start is less than object size. Check `Range` header format.                                                                                                       |
-| 10031      | PreconditionFailed   | 412         | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10033 | MissingContentLength | 411 | `Content-Length` header required but missing. | Include the `Content-Length` header in PUT/POST requests. |
+| 10013 | IncompleteBody | 400 | Request body terminated before expected `Content-Length`. | Ensure the full request body is sent. Check for network interruptions or client timeouts. |
+| 10014 | InvalidDigest | 400 | Checksum header format is malformed. | Ensure checksums are properly encoded (base64 for SHA/CRC checksums). |
+| 10037 | BadDigest | 400 | Provided checksum does not match the uploaded content. | Verify data integrity and retry the upload. |
+| 10039 | InvalidRange | 416 | Requested byte range is not satisfiable. | Ensure the range start is less than object size. Check `Range` header format. |
+| 10031 | PreconditionFailed | 412 | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
 
 ### Multipart upload errors
 
-| Error Code | S3 Code        | HTTP Status | Details                                                                 | Recommended Fix                                                                                                                                               |
-| ---------- | -------------- | ----------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10011      | EntityTooSmall | 400         | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB.                                                                                                         |
-| 10024      | NoSuchUpload   | 404         | Multipart upload does not exist or was aborted.                         | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
-| 10025      | InvalidPart    | 400         | One or more parts could not be found when completing the upload.        | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`.                                                                 |
-| 10048      | InvalidPart    | 400         | All non-trailing parts must have the same size.                         | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads.                                                  |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10011 | EntityTooSmall | 400 | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB. |
+| 10024 | NoSuchUpload | 404 | Multipart upload does not exist or was aborted. | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
+| 10025 | InvalidPart | 400 | One or more parts could not be found when completing the upload. | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`. |
+| 10048 | InvalidPart | 400 | All non-trailing parts must have the same size. | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads. |
 
 ### Service errors
 
-| Error Code | S3 Code            | HTTP Status | Details                                                                                                                   | Recommended Fix                                                                                                   |
-| ---------- | ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| 10001      | InternalError      | 500         | An internal error occurred.                                                                                               | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
-| 10043      | ServiceUnavailable | 503         | Service is temporarily unavailable.                                                                                       | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com).                      |
-| 10054      | ClientDisconnect   | 400         | Client disconnected before request completed.                                                                             | Check network connectivity and retry.                                                                             |
-| 10058      | TooManyRequests    | 429         | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/).               |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10001 | InternalError | 500 | An internal error occurred. | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
+| 10043 | ServiceUnavailable | 503 | Service is temporarily unavailable. | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com). |
+| 10054 | ClientDisconnect | 400 | Client disconnected before request completed. | Check network connectivity and retry. |
+| 10058 | TooManyRequests | 429 | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/). |
diff --git a/src/content/docs/r2/api/index.mdx b/src/content/docs/r2/api/index.mdx
index c7113b1969a8c64..ea9d2d32f1163c9 100644
--- a/src/content/docs/r2/api/index.mdx
+++ b/src/content/docs/r2/api/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 R2 provides three API surfaces for interacting with your data:
 
diff --git a/src/content/docs/r2/api/s3/extensions.mdx b/src/content/docs/r2/api/s3/extensions.mdx
index 3d837887f7d5b66..79016396a6a9091 100644
--- a/src/content/docs/r2/api/s3/extensions.mdx
+++ b/src/content/docs/r2/api/s3/extensions.mdx
@@ -16,11 +16,13 @@ HTTP header names and values may only contain ASCII characters, which is a small
 
 :::caution[Metadata variance]
 
-Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted.
+Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted. 
 :::
 
 These headers map to the `httpMetadata` field in the [R2 bindings](/workers/runtime-apis/bindings/):
 
+
+
 | HTTP Header           | Property Name                     |
 | --------------------- | --------------------------------- |
 | `Content-Encoding`    | `httpMetadata.contentEncoding`    |
@@ -71,6 +73,8 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 `ListBuckets` supports all the same search parameters as `ListObjectsV2` in R2 because some customers may have more than 1,000 buckets. Because tooling, like existing S3 libraries, may not expose a way to set these search parameters, these values may also be sent in via headers. Values in headers take precedence over the search parameters.
 
+
+
 | Search parameter     | HTTP Header             | Meaning                                                           |
 | -------------------- | ----------------------- | ----------------------------------------------------------------- |
 | `prefix`             | `cf-prefix`             | Show buckets with this prefix only.                               |
@@ -81,6 +85,8 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 The XML response contains a `NextContinuationToken` and `IsTruncated` elements as appropriate. Since these may not be accessible from existing S3 APIs, these are also available in response headers:
 
+
+
 | XML Response Element    | HTTP Response Header         | Meaning                                                                                        |
 | ----------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------- |
 | `IsTruncated`           | `cf-is-truncated`            | This is set to `true` if the list of buckets returned is not all the buckets on the account.   |
@@ -95,15 +101,15 @@ The XML response contains a `NextContinuationToken` and `IsTruncated` elements a
 
 :::note
 
-This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81).
+This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81). 
 :::
 
 `CopyObject` already supports conditions that relate to the source object through the `x-amz-copy-source-if-...` headers as part of our compliance with the S3 API. In addition to this, R2 supports an R2 specific set of headers that allow the `CopyObject` operation to be conditional on the target object:
 
-- `cf-copy-destination-if-match`
-- `cf-copy-destination-if-none-match`
-- `cf-copy-destination-if-modified-since`
-- `cf-copy-destination-if-unmodified-since`
+* `cf-copy-destination-if-match`
+* `cf-copy-destination-if-none-match`
+* `cf-copy-destination-if-modified-since`
+* `cf-copy-destination-if-unmodified-since`
 
 These headers work akin to the similarly named conditional headers supported on `PutObject`. When the preceding state of the destination object to does not match the specified conditions the `CopyObject` operation will be rejected with a `412 PreconditionFailed` error code.
 
diff --git a/src/content/docs/r2/api/s3/presigned-urls.mdx b/src/content/docs/r2/api/s3/presigned-urls.mdx
index bda593cdc55a82e..4b4c1fc51449c91 100644
--- a/src/content/docs/r2/api/s3/presigned-urls.mdx
+++ b/src/content/docs/r2/api/s3/presigned-urls.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { Tabs, TabItem, LinkCard } from "~/components";
+import {Tabs, TabItem, LinkCard } from "~/components";
 
 Presigned URLs are an [S3 concept](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) for granting temporary access to objects without exposing your API credentials. A presigned URL includes signature parameters in the URL itself, authorizing anyone with the URL to perform a specific operation (like `GetObject` or `PutObject`) on a specific object until the URL expires.
 
@@ -24,10 +24,10 @@ Presigned URLs are generated client-side with no communication with R2, requirin
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern                                                    | Grants                                                                                                         | Good for                                                                                                                   |
-| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Presigned URLs (this page)                                 | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
-| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
+| Pattern | Grants | Good for |
+| --- | --- | --- |
+| Presigned URLs (this page) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
 
 ## Generate a presigned URL
 
@@ -136,7 +136,6 @@ aws s3 presign --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com \
 </Tabs>
 
 For complete examples and additional operations, refer to the SDK-specific documentation:
-
 - [AWS SDK for JavaScript](/r2/examples/aws/aws-sdk-js-v3/#generate-presigned-urls)
 - [AWS SDK for Python (Boto3)](/r2/examples/aws/boto3/#generate-presigned-urls)
 - [AWS CLI](/r2/examples/aws/aws-cli/#generate-presigned-urls)
diff --git a/src/content/docs/r2/api/s3/temporary-credentials.mdx b/src/content/docs/r2/api/s3/temporary-credentials.mdx
index 42a48a5428e8ec4..eabe88c5d475d9f 100644
--- a/src/content/docs/r2/api/s3/temporary-credentials.mdx
+++ b/src/content/docs/r2/api/s3/temporary-credentials.mdx
@@ -16,10 +16,10 @@ Use temporary credentials to delegate access without issuing a long-lived token.
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern                                      | Grants                                                                                                         | Good for                                                                                                                   |
-| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Temporary credentials (this page)            | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
-| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| Pattern | Grants | Good for |
+| --- | --- | --- |
+| Temporary credentials (this page) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
+| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
 
 ## Generate temporary credentials
 
@@ -108,11 +108,11 @@ For example, `actions: ["GetObject", "HeadObject"]` grants read of individual ob
 
 Valid actions:
 
-| Category  | Actions                                                                                                               |
-| --------- | --------------------------------------------------------------------------------------------------------------------- |
-| Read      | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
-| Write     | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject`                                                            |
-| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload`            |
+| Category | Actions |
+| --- | --- |
+| Read | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
+| Write | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject` |
+| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload` |
 
 ### Paths
 
@@ -122,8 +122,8 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-	"prefixes": ["uploads/user-123/"],
-	"objects": ["shared/manifest.json"],
+  "prefixes": ["uploads/user-123/"],
+  "objects": ["shared/manifest.json"]
 }
 ```
 
@@ -131,10 +131,10 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-	"paths": {
-		"prefixPaths": ["uploads/user-123/"],
-		"objectPaths": ["shared/manifest.json"],
-	},
+  "paths": {
+    "prefixPaths": ["uploads/user-123/"],
+    "objectPaths": ["shared/manifest.json"]
+  }
 }
 ```
 
@@ -205,25 +205,25 @@ Treat temporary credentials as bearer tokens. Anyone in possession of all three
 ## Related resources
 
 <LinkCard
-	title="Authenticate against R2 with temporary credentials"
-	href="/r2/examples/authenticate-r2-temp-credentials/"
-	description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
+  title="Authenticate against R2 with temporary credentials"
+  href="/r2/examples/authenticate-r2-temp-credentials/"
+  description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
 />
 
 <LinkCard
-	title="Presigned URLs"
-	href="/r2/api/s3/presigned-urls/"
-	description="Grant single-operation access to a specific object without issuing credentials."
+  title="Presigned URLs"
+  href="/r2/api/s3/presigned-urls/"
+  description="Grant single-operation access to a specific object without issuing credentials."
 />
 
 <LinkCard
-	title="R2 API tokens"
-	href="/r2/api/tokens/"
-	description="Create the parent token that temporary credentials derive from."
+  title="R2 API tokens"
+  href="/r2/api/tokens/"
+  description="Create the parent token that temporary credentials derive from."
 />
 
 <LinkCard
-	title="Error codes"
-	href="/r2/api/error-codes/"
-	description="Authentication and authorization error codes returned by R2."
+  title="Error codes"
+  href="/r2/api/error-codes/"
+  description="Authentication and authorization error codes returned by R2."
 />
diff --git a/src/content/docs/r2/api/workers/workers-api-reference.mdx b/src/content/docs/r2/api/workers/workers-api-reference.mdx
index d60ffa3b2d79709..b7489165a08ccee 100644
--- a/src/content/docs/r2/api/workers/workers-api-reference.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-reference.mdx
@@ -103,33 +103,40 @@ class Default(WorkerEntrypoint):
 </Tabs>
 
 - `head` <Type text="(key: string): Promise<R2Object | null>" />
+
   - Retrieves the `R2Object` for the given key containing only object metadata, if the key exists, and `null` if the key does not exist.
 
 - `get` <Type text="(key: string, options?: R2GetOptions): Promise<R2ObjectBody | R2Object | null>" />
+
   - Retrieves the `R2ObjectBody` for the given key containing object metadata and the object body as a <code>ReadableStream</code>, if the key exists, and `null` if the key does not exist.
   - In the event that a precondition specified in <code>options</code> fails, <code>get()</code> returns an <code>R2Object</code> with <code>body</code> undefined.
 
 - `put` <Type text="(key: string, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | null | Blob, options?: R2PutOptions): Promise<R2Object | null>" />
+
   - Stores the given <code>value</code> and metadata under the associated <code>key</code>. Once the write succeeds, returns an `R2Object` containing metadata about the stored Object.
   - In the event that a precondition specified in <code>options</code> fails, <code>put()</code> returns `null`, and the object will not be stored.
   - R2 writes are strongly consistent. Once the Promise resolves, all subsequent read operations will see this key value pair globally.
 
 - `delete` <Type text="(key: string | string[]): Promise<void>" />
+
   - Deletes the given <code>values</code> and metadata under the associated <code>keys</code>. Once the delete succeeds, returns <code>void</code>.
   - R2 deletes are strongly consistent. Once the Promise resolves, all subsequent read operations will no longer see the provided key value pairs globally.
   - Up to 1000 keys may be deleted per call.
 
 - `list` <Type text="(options?: R2ListOptions): Promise<R2Objects>" />
-  - Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
-  - The returned list of objects is ordered lexicographically.
-  - Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
-  - To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
+
+  * Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
+  * The returned list of objects is ordered lexicographically.
+  * Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
+  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
 
 * `createMultipartUpload` <Type text="(key: string, options?: R2MultipartOptions): Promise<R2MultipartUpload>" />
+
   - Creates a multipart upload.
   - Returns Promise which resolves to an `R2MultipartUpload` object representing the newly created multipart upload. Once the multipart upload has been created, the multipart upload can be immediately interacted with globally, either through the Workers API, or through the S3 API.
 
 - `resumeMultipartUpload` <Type text="(key: string, uploadId: string): R2MultipartUpload" />
+
   - Returns an object representing a multipart upload with the given key and uploadId.
   - The resumeMultipartUpload operation does not perform any checks to ensure the validity of the uploadId, nor does it verify the existence of a corresponding active multipart upload. This is done to minimize latency before being able to call subsequent operations on the `R2MultipartUpload` object.
 
@@ -138,12 +145,15 @@ class Default(WorkerEntrypoint):
 `R2Object` is created when you `PUT` an object into an R2 bucket. `R2Object` represents the metadata of an object based on the information provided by the uploader. Every object that you `PUT` into an R2 bucket will have an `R2Object` created.
 
 - `key` <Type text="string" />
+
   - The object's key.
 
 - `version` <Type text="string" />
+
   - Random unique string associated with a specific upload of a key.
 
 - `size` <Type text="number" />
+
   - Size of the object in bytes.
 
 - `etag` <Type text="string" />
@@ -156,30 +166,39 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 - The etag associated with the object upload.
 
 - `httpEtag` <Type text="string" />
+
   - The object's etag, in quotes so as to be returned as a header.
 
 - `uploaded` <Type text="Date" />
+
   - A Date object representing the time the object was uploaded.
 
 - `httpMetadata` <Type text="R2HTTPMetadata" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" />
+
   - A map of custom, user-defined metadata associated with the object.
 
 - `range` <Type text="R2Range" />
+
   - A `R2Range` object containing the returned range of the object.
 
 - `checksums` <Type text="R2Checksums" />
+
   - A `R2Checksums` object containing the stored checksums of the object. Refer to [checksums](#checksums).
 
 - `writeHttpMetadata` <Type text="(headers: Headers): void" />
+
   - Retrieves the `httpMetadata` from the `R2Object` and applies their corresponding HTTP headers to the `Headers` input object. Refer to [HTTP Metadata](#http-metadata).
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
+
   - The storage class associated with the object. Refer to [Storage Classes](#storage-class).
 
 - `ssecKeyMd5` <Type text="string" />
+
   - Hex-encoded MD5 hash of the [SSE-C](/r2/examples/ssec) key used for encryption (if one was provided). Hash can be used to identify which key is needed to decrypt object.
 
 ## `R2ObjectBody` definition
@@ -187,21 +206,27 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 `R2ObjectBody` represents an object's metadata combined with its body. It is returned when you `GET` an object from an R2 bucket. The full list of keys for `R2ObjectBody` includes the list below and all keys inherited from [`R2Object`](#r2object-definition).
 
 - `body` <Type text="ReadableStream" />
+
   - The object's value.
 
 - `bodyUsed` <Type text="boolean" />
+
   - Whether the object's value has been consumed or not.
 
 - `arrayBuffer` <Type text="(): Promise<ArrayBuffer>" />
+
   - Returns a Promise that resolves to an `ArrayBuffer` containing the object's value.
 
 - `text` <Type text="(): Promise<string>" />
+
   - Returns a Promise that resolves to an string containing the object's value.
 
 - `json` <Type text="<T>() : Promise<T>" />
+
   - Returns a Promise that resolves to the given object containing the object's value.
 
 - `blob` <Type text="(): Promise<Blob>" />
+
   - Returns a Promise that resolves to a binary Blob containing the object's value.
 
 ## `R2MultipartUpload` definition
@@ -219,19 +244,24 @@ A multipart upload can be completed or aborted at any time, either through the S
 :::
 
 - `key` <Type text="string" />
+
   - The `key` for the multipart upload.
 
 - `uploadId` <Type text="string" />
+
   - The `uploadId` for the multipart upload.
 
 - `uploadPart` <Type text="(partNumber: number, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | Blob, options?: R2MultipartOptions): Promise<R2UploadedPart>" />
+
   - Uploads a single part with the specified part number to this multipart upload. Each part must be uniform in size with an exception for the final part which can be smaller.
   - Returns an `R2UploadedPart` object containing the `etag` and `partNumber`. These `R2UploadedPart` objects are required when completing the multipart upload.
 
 - `abort` <Type text="(): Promise<void>" />
+
   - Aborts the multipart upload. Returns a Promise that resolves when the upload has been successfully aborted.
 
 - `complete` <Type text="(uploadedParts: R2UploadedPart[]): Promise<R2Object>" />
+
   - Completes the multipart upload with the given parts.
   - Returns a Promise that resolves when the complete operation has finished. Once this happens, the object is immediately accessible globally by any subsequent read operation.
 
@@ -240,12 +270,15 @@ A multipart upload can be completed or aborted at any time, either through the S
 ### R2GetOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
+
   - Specifies that the object should only be returned given satisfaction of certain conditions in the `R2Conditional` or in the conditional Headers. Refer to [Conditional operations](#conditional-operations).
 
 - `range` <Type text="R2Range" />
+
   - Specifies that only a specific length (from an optional offset) or suffix of bytes from the object should be returned. Refer to [Ranged reads](#ranged-reads).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 #### Ranged reads
@@ -259,23 +292,29 @@ There are 3 variations of arguments that can be used in a range:
 - A suffix.
 
 - `offset` <Type text="number" />
+
   - The byte to begin returning data from, inclusive.
 
 - `length` <Type text="number" />
+
   - The number of bytes to return. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 - `suffix` <Type text="number" />
+
   - The number of bytes to return from the end of the file, starting from the last byte. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 ### R2PutOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
+
   - Specifies that the object should only be stored given satisfaction of certain conditions in the `R2Conditional`. Refer to [Conditional operations](#conditional-operations).
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
+
   - A map of custom, user-defined metadata that will be stored with the object.
 
 :::note
@@ -285,57 +324,73 @@ Only a single hashing algorithm can be specified at once.
 :::
 
 - `md5` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A md5 hash to use to check the received object's integrity.
 
 - `sha1` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-1 hash to use to check the received object's integrity.
 
 - `sha256` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-256 hash to use to check the received object's integrity.
 
 - `sha384` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-384 hash to use to check the received object's integrity.
 
 - `sha512` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-512 hash to use to check the received object's integrity.
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
+
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2MultipartOptions
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
+
   - A map of custom, user-defined metadata that will be stored with the object.
 
 - `storageClass` <Type text="string" />
+
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2ListOptions
 
 - `limit` <Type text="number" /> <MetaInfo text="optional" />
+
   - The number of results to return. Defaults to `1000`, with a maximum of `1000`.
 
   - If `include` is set, you may receive fewer than `limit` results in your response to accommodate metadata.
 
 - `prefix` <Type text="string" /> <MetaInfo text="optional" />
+
   - The prefix to match keys against. Keys will only be returned if they start with given prefix.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
+
   - An opaque token that indicates where to continue listing objects from. A cursor can be retrieved from a previous list operation.
 
 - `delimiter` <Type text="string" /> <MetaInfo text="optional" />
+
   - The character to use when grouping keys.
 
 - `include` <Type text="Array<string>" /> <MetaInfo text="optional" />
+
   - Can include `httpMetadata` and/or `customMetadata`. If included, items returned by the list will include the specified metadata.
 
   - Note that there is a limit on the total amount of data that a single `list` operation can return. If you request data, you may receive fewer than `limit` results in your response to accommodate metadata.
@@ -380,15 +435,19 @@ while (truncated) {
 An object containing an `R2Object` array, returned by `BUCKET_BINDING.list()`.
 
 - `objects` <Type text="Array<R2Object>" />
+
   - An array of objects matching the `list` request.
 
 - `truncated` boolean
+
   - If true, indicates there are more results to be retrieved for the current `list` request.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
+
   - A token that can be passed to future `list` calls to resume listing from that point. Only present if truncated is true.
 
 - `delimitedPrefixes` <Type text="Array<string>" />
+
   - If a delimiter has been specified, contains all prefixes between the specified prefix and the next occurrence of the delimiter.
 
   - For example, if no prefix is provided and the delimiter is '/', `foo/bar/baz` would return `foo` as a delimited prefix. If `foo/` was passed as a prefix with the same structure and delimiter, `foo/bar` would be returned as a delimited prefix.
@@ -400,15 +459,19 @@ You can pass an `R2Conditional` object to `R2GetOptions` and `R2PutOptions`. If
 If the condition check for `put()` fails, `null` will be returned instead of the `R2Object`.
 
 - `etagMatches` <Type text="string" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object's etag matches the given string.
 
 - `etagDoesNotMatch` <Type text="string" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object's etag does not match the given string.
 
 - `uploadedBefore` <Type text="Date" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object was uploaded before the given date.
 
 - `uploadedAfter` <Type text="Date" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object was uploaded after the given date.
 
 Alternatively, you can pass a `Headers` object containing conditional headers to `R2GetOptions` and `R2PutOptions`. For information on these conditional headers, refer to [the MDN docs on conditional requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditional_requests#conditional_headers). All conditional headers aside from `If-Range` are supported.
@@ -436,18 +499,23 @@ Generally, these fields match the HTTP metadata passed when the object was creat
 If a checksum was provided when using the `put()` binding, it will be available on the returned object under the `checksums` property. The MD5 checksum will be included by default for non-multipart objects.
 
 - `md5` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The MD5 checksum of the object.
 
 - `sha1` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-1 checksum of the object.
 
 - `sha256` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-256 checksum of the object.
 
 - `sha384` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-384 checksum of the object.
 
 - `sha512` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-512 checksum of the object.
 
 ### `R2UploadedPart`
@@ -455,9 +523,11 @@ If a checksum was provided when using the `put()` binding, it will be available
 An `R2UploadedPart` object represents a part that has been uploaded. `R2UploadedPart` objects are returned from `uploadPart` operations and must be passed to `completeMultipartUpload` operations.
 
 - `partNumber` <Type text="number" />
+
   - The number of the part.
 
 - `etag` <Type text="string" />
+
   - The `etag` of the part.
 
 ### Storage Class
diff --git a/src/content/docs/r2/api/workers/workers-api-usage.mdx b/src/content/docs/r2/api/workers/workers-api-usage.mdx
index 3201040184b441e..6cfb3742ecf0dbe 100644
--- a/src/content/docs/r2/api/workers/workers-api-usage.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-usage.mdx
@@ -251,7 +251,6 @@ class Default(WorkerEntrypoint):
 ```
 </TabItem>
 </Tabs>
-
 <Render file="request-dot-clone-warning" product="workers" />
 
 ## 5. Bucket access and privacy
diff --git a/src/content/docs/r2/buckets/bucket-locks.mdx b/src/content/docs/r2/buckets/bucket-locks.mdx
index d7bcec562a81685..464a1623fef1b18 100644
--- a/src/content/docs/r2/buckets/bucket-locks.mdx
+++ b/src/content/docs/r2/buckets/bucket-locks.mdx
@@ -22,7 +22,6 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Select **Add rule** and enter the rule name, prefix, and retention period.
@@ -98,7 +97,6 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 
@@ -121,7 +119,6 @@ For more information on required parameters and examples of how to get bucket lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Locate the rule you want to remove, select the `...` icon next to it, and then select **Delete**.
diff --git a/src/content/docs/r2/buckets/cors.mdx b/src/content/docs/r2/buckets/cors.mdx
index e377d4c3587d41b..509574538198e4b 100644
--- a/src/content/docs/r2/buckets/cors.mdx
+++ b/src/content/docs/r2/buckets/cors.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) is a standardized method that prevents domain X from accessing the resources of domain Y. It does so by using special headers in HTTP responses from domain Y, that allow your browser to verify that domain Y permits domain X to access these resources.
 
@@ -56,13 +56,13 @@ The following example allows browser-based uploads from `https://example.com` wi
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -83,7 +83,6 @@ If you set a CORS policy on a bucket that is already serving traffic using a cus
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. Select **Settings**.
 4. Under **CORS Policy**, select **Add CORS policy**.
@@ -100,14 +99,14 @@ You can configure CORS rules using the [Wrangler CLI](/r2/reference/wrangler-com
 
 ```json title="cors.json"
 {
-	"rules": [
-		{
-			"allowed": {
-				"origins": ["https://example.com"],
-				"methods": ["GET"]
-			}
-		}
-	]
+  "rules": [
+    {
+      "allowed": {
+        "origins": ["https://example.com"],
+        "methods": ["GET"]
+      }
+    }
+  ]
 }
 ```
 
@@ -127,13 +126,13 @@ npx wrangler r2 bucket cors list <BUCKET_NAME>
 
 The following fields in an R2 CORS policy map to HTTP response headers. These response headers are only returned when the incoming HTTP request is a valid CORS request.
 
-| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                                     | Example                                                                                                                                                                                                                              |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                    | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
-| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                   | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
-| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                          | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
+| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                           | Example                                                                                                                                                                                                                              |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                          | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
+| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                         | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
+| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
 | `ExposeHeaders`  | Specifies the headers that can be exposed back, and accessed by, the JavaScript making the cross-origin request. If you need to access headers beyond the [safelisted response headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers#examples), such as `Content-Encoding` or `cf-cache-status`, you must specify it here. | `Content-Encoding`, `cf-cache-status`, `Date`                                                                                                                                                                                        |
-| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                                   | `3600`                                                                                                                                                                                                                               |
+| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                         | `3600`                                                                                                                                                                                                                               |
 
 ## Example
 
diff --git a/src/content/docs/r2/buckets/delete-buckets.mdx b/src/content/docs/r2/buckets/delete-buckets.mdx
index 71cdbc593f9c6e8..cae21c981e67944 100644
--- a/src/content/docs/r2/buckets/delete-buckets.mdx
+++ b/src/content/docs/r2/buckets/delete-buckets.mdx
@@ -27,7 +27,6 @@ The dashboard provides an **Empty Bucket** action that handles this for you, reg
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you want to empty.
 3. Go to the **Settings** tab.
 4. Scroll to the **Empty Bucket** section.
@@ -87,7 +86,6 @@ You can delete a bucket in various ways.
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you want to delete.
 3. Go to the **Settings** tab.
 4. Scroll to the **Delete Bucket** section. If the bucket is not empty, select **Empty Bucket** first to clear all objects.
@@ -131,25 +129,25 @@ curl -X DELETE "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/r2/bu
 ## Related resources
 
 <LinkCard
-	title="Delete objects"
-	href="/r2/objects/delete-objects/"
-	description="Delete individual objects or folders from an R2 bucket."
+  title="Delete objects"
+  href="/r2/objects/delete-objects/"
+  description="Delete individual objects or folders from an R2 bucket."
 />
 
 <LinkCard
-	title="Bucket locks"
-	href="/r2/buckets/bucket-locks/"
-	description="Prevent accidental deletion by setting retention policies on objects."
+  title="Bucket locks"
+  href="/r2/buckets/bucket-locks/"
+  description="Prevent accidental deletion by setting retention policies on objects."
 />
 
 <LinkCard
-	title="Object lifecycles"
-	href="/r2/buckets/object-lifecycles/"
-	description="Automatically expire objects after a specified period instead of emptying manually."
+  title="Object lifecycles"
+  href="/r2/buckets/object-lifecycles/"
+  description="Automatically expire objects after a specified period instead of emptying manually."
 />
 
 <LinkCard
-	title="Create buckets"
-	href="/r2/buckets/create-buckets/"
-	description="Create a new R2 bucket after deleting an existing one."
+  title="Create buckets"
+  href="/r2/buckets/create-buckets/"
+  description="Create a new R2 bucket after deleting an existing one."
 />
diff --git a/src/content/docs/r2/buckets/event-notifications.mdx b/src/content/docs/r2/buckets/event-notifications.mdx
index e910f9b896e6223..b0fe30eb775ad6f 100644
--- a/src/content/docs/r2/buckets/event-notifications.mdx
+++ b/src/content/docs/r2/buckets/event-notifications.mdx
@@ -26,7 +26,6 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you'd like to add an event notification rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Event notifications** card.
 4. Select **Add notification** and choose the queue you'd like to receive notifications and the [type of events](/r2/buckets/event-notifications/#event-types) that will trigger them.
@@ -67,10 +66,10 @@ Event notification rules determine the [event types](/r2/buckets/event-notificat
 
 ## Event types
 
-| Event type      | Description                                                                 | Trigger actions                                                                      |
-| --------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| Event type | Description | Trigger actions |
+|------------|-------------|----------------|
 | `object-create` | Triggered when new objects are created or existing objects are overwritten. | <ul><li>`PutObject`</li><li>`CopyObject`</li><li>`CompleteMultipartUpload`</li></ul> |
-| `object-delete` | Triggered when an object is explicitly removed from the bucket.             | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul>                         |
+| `object-delete` | Triggered when an object is explicitly removed from the bucket. | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul> |
 
 ## Message format
 
@@ -96,19 +95,19 @@ Queue consumers receive notifications as [Messages](/queues/configuration/javasc
 
 ### Properties
 
-| Property            | Type   | Description                                                                                                                                              |
-| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `account`           | String | The Cloudflare account ID that the event is associated with.                                                                                             |
-| `action`            | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
-| `bucket`            | String | The name of the bucket where the event occurred.                                                                                                         |
-| `object`            | Object | A nested object containing details about the object involved in the event.                                                                               |
-| `object.key`        | String | The key (or name) of the object within the bucket.                                                                                                       |
-| `object.size`       | Number | The size of the object in bytes. Note: not present for object-delete events.                                                                             |
-| `object.eTag`       | String | The entity tag (eTag) of the object. Note: not present for object-delete events.                                                                         |
-| `eventTime`         | String | The time when the action that triggered the event occurred.                                                                                              |
-| `copySource`        | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`.                         |
-| `copySource.bucket` | String | The bucket that contained the source object.                                                                                                             |
-| `copySource.object` | String | The name of the source object.                                                                                                                           |
+| Property | Type | Description |
+|----------|------|-------------|
+| `account` | String | The Cloudflare account ID that the event is associated with. |
+| `action` | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
+| `bucket` | String | The name of the bucket where the event occurred. |
+| `object` | Object | A nested object containing details about the object involved in the event. |
+| `object.key` | String | The key (or name) of the object within the bucket. |
+| `object.size` | Number | The size of the object in bytes. Note: not present for object-delete events. |
+| `object.eTag` | String | The entity tag (eTag) of the object. Note: not present for object-delete events. |
+| `eventTime` | String | The time when the action that triggered the event occurred. |
+| `copySource` | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`. |
+| `copySource.bucket` | String | The bucket that contained the source object. |
+| `copySource.object` | String | The name of the source object. |
 
 ## Notes
 
diff --git a/src/content/docs/r2/buckets/index.mdx b/src/content/docs/r2/buckets/index.mdx
index 56bda3ed5e0d4ce..6b32cf898b1518c 100644
--- a/src/content/docs/r2/buckets/index.mdx
+++ b/src/content/docs/r2/buckets/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 With object storage, all of your objects are stored in buckets. Buckets do not contain folders that group the individual files, but instead, buckets have a flat structure which simplifies the way you access and retrieve the objects in your bucket.
 
diff --git a/src/content/docs/r2/buckets/object-lifecycles.mdx b/src/content/docs/r2/buckets/object-lifecycles.mdx
index 0eaef01b4fefed0..8aa7719e17e7b1a 100644
--- a/src/content/docs/r2/buckets/object-lifecycles.mdx
+++ b/src/content/docs/r2/buckets/object-lifecycles.mdx
@@ -35,7 +35,6 @@ When you create an object lifecycle rule, you can specify which prefix you would
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object Lifecycle Rules**, select **Add rule**.
@@ -187,7 +186,6 @@ console.log(
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object lifecycle rules**, select the rules you would like to delete.
diff --git a/src/content/docs/r2/buckets/storage-classes.mdx b/src/content/docs/r2/buckets/storage-classes.mdx
index 329e212d619b99e..d26bd2b34d5a359 100644
--- a/src/content/docs/r2/buckets/storage-classes.mdx
+++ b/src/content/docs/r2/buckets/storage-classes.mdx
@@ -6,22 +6,22 @@ products:
   - r2
 ---
 
-import { Badge, Tabs, TabItem } from "~/components";
+import { Badge, Tabs, TabItem } from "~/components"
 
 Storage classes allow you to trade off between the cost of storage and the cost of accessing data. Every object stored in R2 has an associated storage class.
 
 All storage classes share the following characteristics:
 
-- Compatible with Workers API, S3 API, and public buckets.
-- 99.999999999% (eleven 9s) of annual durability.
-- No minimum object size.
+* Compatible with Workers API, S3 API, and public buckets.
+* 99.999999999% (eleven 9s) of annual durability.
+* No minimum object size.
 
 ## Available storage classes
 
-| Storage class     | Minimum storage duration | Data retrieval fees (processing) | Egress fees (data transfer to Internet) |
-| ----------------- | ------------------------ | -------------------------------- | --------------------------------------- |
-| Standard          | None                     | None                             | None                                    |
-| Infrequent Access | 30 days                  | Yes                              | None                                    |
+| Storage class                  | Minimum storage duration  | Data retrieval fees (processing) | Egress fees (data transfer to Internet)  |
+|--------------------------------|---------------------------|----------------------------------|------------------------------------------|
+| Standard                       | None                      | None                             | None                                     |
+| Infrequent Access              | 30 days                   | Yes                              | None                                     |
 
 For more information on how storage classes impact pricing, refer to [Pricing](/r2/pricing/).
 
@@ -31,11 +31,11 @@ Standard storage is designed for data that is accessed frequently. This is the d
 
 #### Example use cases
 
-- Website and application data
-- Media content (e.g., images, video)
-- Storing large datasets for analysis and processing
-- AI training data
-- Other workloads involving frequently accessed data
+* Website and application data
+* Media content (e.g., images, video)
+* Storing large datasets for analysis and processing
+* AI training data
+* Other workloads involving frequently accessed data
 
 ### Infrequent Access storage
 
@@ -47,9 +47,9 @@ For objects stored in Infrequent Access storage, you will be charged for the obj
 
 #### Example use cases
 
-- Long-term data archiving (for example, logs and historical records needed for compliance)
-- Data backup and disaster recovery
-- Long tail user-generated content
+* Long-term data archiving (for example, logs and historical records needed for compliance)
+* Data backup and disaster recovery
+* Long tail user-generated content
 
 ## Set default storage class for buckets
 
diff --git a/src/content/docs/r2/data-migration/index.mdx b/src/content/docs/r2/data-migration/index.mdx
index 1fc637f6979b11a..05a1dabde3c991d 100644
--- a/src/content/docs/r2/data-migration/index.mdx
+++ b/src/content/docs/r2/data-migration/index.mdx
@@ -58,4 +58,4 @@ Quickly and easily migrate data from other cloud providers to R2. Explore each o
 	</tbody>
 </table>
 
-For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
+For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
\ No newline at end of file
diff --git a/src/content/docs/r2/data-migration/migration-strategies.mdx b/src/content/docs/r2/data-migration/migration-strategies.mdx
index 484528cc3c1eabc..9771c0a5eb95eb3 100644
--- a/src/content/docs/r2/data-migration/migration-strategies.mdx
+++ b/src/content/docs/r2/data-migration/migration-strategies.mdx
@@ -60,4 +60,4 @@ You can create separate jobs with prefixes such as:
 - `/photos/2024` to migrate all 2024 files
 - `/photos/202` to migrate all files from 2023 and 2024
 
-Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
+Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
\ No newline at end of file
diff --git a/src/content/docs/r2/data-migration/sippy.mdx b/src/content/docs/r2/data-migration/sippy.mdx
index 5715798fe2b8a77..66ef2a76b92a898 100644
--- a/src/content/docs/r2/data-migration/sippy.mdx
+++ b/src/content/docs/r2/data-migration/sippy.mdx
@@ -85,10 +85,10 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 
 When enabled, Sippy exposes metrics that help you understand the progress of your ongoing migrations.
 
-| Metric                   | Description                                                                                                                                                    |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Metric | Description |
+|--------|-------------|
 | Requests served by Sippy | The percentage of overall requests served by R2 over a period of time. A higher percentage indicates that fewer requests need to be made to the source bucket. |
-| Data migrated by Sippy   | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes.                                                 |
+| Data migrated by Sippy | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes. |
 
 To view current and historical metrics:
 
@@ -138,12 +138,12 @@ Cloudflare currently supports copying data from the following cloud object stora
 
 When Sippy is enabled, it changes the behavior of certain actions on your R2 bucket across [Workers](/r2/api/workers/), [S3 API](/r2/api/s3/), and [public buckets](/r2/buckets/public-buckets/).
 
-| Action       | New behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| GetObject    | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
-| HeadObject   | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| PutObject    | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Action | New behavior |
+|--------|-------------|
+| GetObject | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
+| HeadObject | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket. |
+| PutObject | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket. |
+| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul> |
 
 Actions not listed above have no change in behavior. For more information, refer to [Workers API reference](/r2/api/workers/workers-api-reference/) or [S3 API compatibility](/r2/api/s3/api/).
 
diff --git a/src/content/docs/r2/data-migration/super-slurper.mdx b/src/content/docs/r2/data-migration/super-slurper.mdx
index 9788052b63d58ac..584c6edca51ca0f 100644
--- a/src/content/docs/r2/data-migration/super-slurper.mdx
+++ b/src/content/docs/r2/data-migration/super-slurper.mdx
@@ -32,7 +32,6 @@ For migration use cases that do not meet the above criteria, we recommend using
 1. In the Cloudflare dashboard, go to the **R2 data migration** page.
 
    <DashButton url="/?to=/:account/r2/slurper" />
-
 2. Select **Migrate files**.
 3. Select the source cloud storage provider that you will be migrating data from.
 4. Enter your source bucket name and associated credentials and select **Next**.
@@ -137,11 +136,7 @@ You can now use this JSON key file when enabling Super Slurper.
 
 ### ETags
 
-<Render
-	file="migrator-etag-caveat"
-	params={{ one: "Super Slurper" }}
-	product="r2"
-/>
+<Render file="migrator-etag-caveat" params={{ one: "Super Slurper" }} product="r2" />
 
 ### Archive storage classes
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
index d603be9a7e32e27..a4c2c23cbae798d 100644
--- a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
@@ -7,7 +7,7 @@ products:
   - r2
 ---
 
-import { PackageManagers, Tabs, TabItem } from "~/components";
+import { PackageManagers, Tabs, TabItem } from '~/components';
 
 The following example shows how to authenticate against R2 using the S3 API and an API token.
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
index 0d2a8e4861600f8..76b0c32d6744f0f 100644
--- a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
@@ -40,14 +40,14 @@ The response wraps the credentials in a `result` object:
 
 ```json
 {
-	"result": {
-		"accessKeyId": "<accessKeyId>",
-		"secretAccessKey": "<secretAccessKey>",
-		"sessionToken": "<sessionToken>"
-	},
-	"errors": [],
-	"messages": [],
-	"success": true
+  "result": {
+    "accessKeyId": "<accessKeyId>",
+    "secretAccessKey": "<secretAccessKey>",
+    "sessionToken": "<sessionToken>"
+  },
+  "errors": [],
+  "messages": [],
+  "success": true
 }
 ```
 
@@ -63,77 +63,77 @@ The following helper signs a JWT with your parent secret access key and derives
 import { SignJWT } from "jose";
 
 type R2Scope =
-	| "object-read-only"
-	| "object-read-write"
-	| "admin-read-only"
-	| "admin-read-write";
+  | "object-read-only"
+  | "object-read-write"
+  | "admin-read-only"
+  | "admin-read-write";
 
 export interface TempCredentialOptions {
-	scope: R2Scope;
-	// Optional: narrow the credential to specific S3 operations.
-	actions?: string[];
-	// Time-to-live in seconds. Defaults to 1 hour.
-	ttlSeconds?: number;
-	// Optional: restrict access to specific prefixes or objects.
-	paths?: { prefixPaths?: string[]; objectPaths?: string[] };
+  scope: R2Scope;
+  // Optional: narrow the credential to specific S3 operations.
+  actions?: string[];
+  // Time-to-live in seconds. Defaults to 1 hour.
+  ttlSeconds?: number;
+  // Optional: restrict access to specific prefixes or objects.
+  paths?: { prefixPaths?: string[]; objectPaths?: string[] };
 }
 
 export async function createTempCredentials(
-	endpoint: string,
-	accountId: string,
-	parentAccessKeyId: string,
-	parentSecretAccessKey: string,
-	bucket: string,
-	opts: TempCredentialOptions,
+  endpoint: string,
+  accountId: string,
+  parentAccessKeyId: string,
+  parentSecretAccessKey: string,
+  bucket: string,
+  opts: TempCredentialOptions,
 ): Promise<{
-	accessKeyId: string;
-	secretAccessKey: string;
-	sessionToken: string;
+  accessKeyId: string;
+  secretAccessKey: string;
+  sessionToken: string;
 }> {
-	const ttl = opts.ttlSeconds ?? 3600;
-
-	const claims: Record<string, unknown> = {
-		bucket,
-		scope: opts.scope,
-	};
-
-	if (opts.actions !== undefined && opts.actions.length > 0) {
-		claims.actions = opts.actions;
-	}
-
-	if (opts.paths !== undefined) {
-		claims.paths = {
-			prefixPaths: opts.paths.prefixPaths ?? [],
-			objectPaths: opts.paths.objectPaths ?? [],
-		};
-	}
-
-	// Sign the JWT with the parent secret access key. R2 validates this signature.
-	const jwt = await new SignJWT(claims)
-		.setProtectedHeader({ alg: "HS256", typ: "JWT" })
-		.setSubject(accountId)
-		.setIssuer(parentAccessKeyId)
-		.setAudience(new URL(endpoint).host)
-		.setIssuedAt()
-		.setExpirationTime(`${ttl}s`)
-		.sign(new TextEncoder().encode(parentSecretAccessKey));
-
-	// The temporary secret access key is the SHA-256 hex digest of the signed JWT.
-	const digest = await crypto.subtle.digest(
-		"SHA-256",
-		new TextEncoder().encode(jwt),
-	);
-	const secretAccessKey = Array.from(new Uint8Array(digest))
-		.map((b) => b.toString(16).padStart(2, "0"))
-		.join("");
-
-	return {
-		// Reuse the parent access key ID as the temporary access key ID.
-		accessKeyId: parentAccessKeyId,
-		secretAccessKey,
-		// The session token is base64("jwt/" + signed JWT).
-		sessionToken: btoa(`jwt/${jwt}`),
-	};
+  const ttl = opts.ttlSeconds ?? 3600;
+
+  const claims: Record<string, unknown> = {
+    bucket,
+    scope: opts.scope,
+  };
+
+  if (opts.actions !== undefined && opts.actions.length > 0) {
+    claims.actions = opts.actions;
+  }
+
+  if (opts.paths !== undefined) {
+    claims.paths = {
+      prefixPaths: opts.paths.prefixPaths ?? [],
+      objectPaths: opts.paths.objectPaths ?? [],
+    };
+  }
+
+  // Sign the JWT with the parent secret access key. R2 validates this signature.
+  const jwt = await new SignJWT(claims)
+    .setProtectedHeader({ alg: "HS256", typ: "JWT" })
+    .setSubject(accountId)
+    .setIssuer(parentAccessKeyId)
+    .setAudience(new URL(endpoint).host)
+    .setIssuedAt()
+    .setExpirationTime(`${ttl}s`)
+    .sign(new TextEncoder().encode(parentSecretAccessKey));
+
+  // The temporary secret access key is the SHA-256 hex digest of the signed JWT.
+  const digest = await crypto.subtle.digest(
+    "SHA-256",
+    new TextEncoder().encode(jwt),
+  );
+  const secretAccessKey = Array.from(new Uint8Array(digest))
+    .map((b) => b.toString(16).padStart(2, "0"))
+    .join("");
+
+  return {
+    // Reuse the parent access key ID as the temporary access key ID.
+    accessKeyId: parentAccessKeyId,
+    secretAccessKey,
+    // The session token is base64("jwt/" + signed JWT).
+    sessionToken: btoa(`jwt/${jwt}`),
+  };
 }
 ```
 
@@ -145,17 +145,17 @@ import { createTempCredentials } from "./temp-credentials";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const creds = await createTempCredentials(
-	R2_URL,
-	ACCOUNT_ID,
-	PARENT_ACCESS_KEY_ID,
-	PARENT_SECRET_ACCESS_KEY,
-	"my-bucket",
-	{
-		scope: "object-read-only",
-		actions: ["GetObject", "HeadObject"],
-		ttlSeconds: 900,
-		paths: { prefixPaths: ["data/"] },
-	},
+  R2_URL,
+  ACCOUNT_ID,
+  PARENT_ACCESS_KEY_ID,
+  PARENT_SECRET_ACCESS_KEY,
+  "my-bucket",
+  {
+    scope: "object-read-only",
+    actions: ["GetObject", "HeadObject"],
+    ttlSeconds: 900,
+    paths: { prefixPaths: ["data/"] },
+  },
 );
 ```
 
@@ -169,10 +169,10 @@ import { AwsClient } from "aws4fetch";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const client = new AwsClient({
-	accessKeyId: ACCESS_KEY_ID,
-	secretAccessKey: SECRET_ACCESS_KEY,
-	sessionToken: SESSION_TOKEN,
-	service: "s3",
+  accessKeyId: ACCESS_KEY_ID,
+  secretAccessKey: SECRET_ACCESS_KEY,
+  sessionToken: SESSION_TOKEN,
+  service: "s3",
 });
 
 // Allowed: object under the data/ prefix.
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
index 1fb6ee02263c766..8c7b8736c9498a9 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
@@ -58,7 +58,9 @@ console.log(await S3.send(new ListBucketsCommand({})));
 //     }
 // }
 
-console.log(await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })));
+console.log(
+	await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })),
+);
 // {
 //     '$metadata': {
 //       httpStatusCode: 200,
@@ -155,13 +157,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -180,6 +182,5 @@ const putUrl = await getSignedUrl(
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
index a7845d865d25f16..3143d3c15d33437 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
@@ -74,11 +74,11 @@ You can also generate presigned links that can be used to share public read or w
 ```ts
 // Use the expires property to determine how long the presigned link is valid.
 console.log(
-	await s3.getSignedUrlPromise("getObject", {
-		Bucket: "my-bucket",
-		Key: "dog.png",
-		Expires: 3600,
-	}),
+await s3.getSignedUrlPromise("getObject", {
+	Bucket: "my-bucket",
+	Key: "dog.png",
+	Expires: 3600,
+}),
 );
 // You can also create links for operations such as putObject to allow temporary write access to a specific key.
 // Specify ContentType to restrict uploads to a specific file type.
@@ -115,13 +115,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -137,6 +137,5 @@ const putUrl = await s3.getSignedUrlPromise("putObject", {
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
index ef0c34ebe76c4fc..e19b20b7d19fdd1 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
@@ -104,3 +104,4 @@ To download a file using the GET URL:
 ```bash
 curl -X GET "https://<your-presigned-get-url>" -o downloaded-file.txt
 ```
+
diff --git a/src/content/docs/r2/examples/aws/aws4fetch.mdx b/src/content/docs/r2/examples/aws/aws4fetch.mdx
index 51411a247aef736..6330b4a288944d3 100644
--- a/src/content/docs/r2/examples/aws/aws4fetch.mdx
+++ b/src/content/docs/r2/examples/aws/aws4fetch.mdx
@@ -144,13 +144,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -172,6 +172,5 @@ const putUrl = signedRequest.url.toString();
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/boto3.mdx b/src/content/docs/r2/examples/aws/boto3.mdx
index 9dce860b7a623d6..fe1fe466ad3d55c 100644
--- a/src/content/docs/r2/examples/aws/boto3.mdx
+++ b/src/content/docs/r2/examples/aws/boto3.mdx
@@ -118,13 +118,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -145,6 +145,5 @@ put_url = s3.generate_presigned_url(
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/custom-header.mdx b/src/content/docs/r2/examples/aws/custom-header.mdx
index 31c3e784bed5934..59695cb8019c958 100644
--- a/src/content/docs/r2/examples/aws/custom-header.mdx
+++ b/src/content/docs/r2/examples/aws/custom-header.mdx
@@ -45,32 +45,35 @@ print(response)
 `aws-sdk-js-v3` allows the customization of request behavior through the use of its [middleware stack](https://aws.amazon.com/blogs/developer/middleware-stack-modular-aws-sdk-js/). This example adds a middleware to the client which adds a header to every `PutObject` request being made.
 
 ```ts
-import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
+import {
+  PutObjectCommand,
+  S3Client,
+} from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-	region: "auto", // Required by SDK but not used by R2
-	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-	credentials: {
-		accessKeyId: ACCESS_KEY_ID,
-		secretAccessKey: SECRET_ACCESS_KEY,
-	},
+  region: "auto", // Required by SDK but not used by R2
+  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+  credentials: {
+    accessKeyId: ACCESS_KEY_ID,
+    secretAccessKey: SECRET_ACCESS_KEY,
+  },
 });
 
 client.middlewareStack.add(
-	(next, context) => async (args) => {
-		const r = args.request as RequestInit;
-		r.headers["cf-create-bucket-if-missing"] = "true";
+  (next, context) => async (args) => {
+      const r = args.request as RequestInit
+      r.headers["cf-create-bucket-if-missing"] = "true";
 
-		return await next(args);
-	},
-	{ step: "build", name: "customHeaders" },
-);
+      return await next(args)
+    },
+  { step: 'build', name: 'customHeaders' },
+)
 
 const command = new PutObjectCommand({
-	Bucket: "my_bucket",
-	Key: "my_key",
-	Body: "my_data",
+  Bucket: "my_bucket",
+  Key: "my_key",
+  Body: "my_data"
 });
 
 const response = await client.send(command);
@@ -124,40 +127,44 @@ print(response)
 Here we again configure the header we would like to set by creating a middleware, but this time we add the middleware to the request itself instead of to the whole client.
 
 ```ts
-import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
+import {
+  PutObjectCommand,
+  S3Client,
+} from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-	region: "auto", // Required by SDK but not used by R2
-	// Provide your Cloudflare account ID
-	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-	credentials: {
-		accessKeyId: ACCESS_KEY_ID,
-		secretAccessKey: SECRET_ACCESS_KEY,
-	},
+  region: "auto", // Required by SDK but not used by R2
+  // Provide your Cloudflare account ID
+  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+  credentials: {
+    accessKeyId: ACCESS_KEY_ID,
+    secretAccessKey: SECRET_ACCESS_KEY,
+  },
 });
 
 const command = new PutObjectCommand({
-	Bucket: "my_bucket",
-	Key: "my_key",
-	Body: "my_data",
+  Bucket: "my_bucket",
+  Key: "my_key",
+  Body: "my_data"
 });
 
-const headers = { "If-Match": '"29d911f495d1ba7cb3a4d7d15e63236a"' };
+const headers = { 'If-Match': '"29d911f495d1ba7cb3a4d7d15e63236a"' }
 command.middlewareStack.add(
-	(next) => (args) => {
-		const r = args.request as RequestInit;
-
-		Object.entries(headers).forEach(
-			([k, v]: [key: string, value: string]): void => {
-				r.headers[k] = v;
-			},
-		);
-
-		return next(args);
-	},
-	{ step: "build", name: "customHeaders" },
-);
+  (next) =>
+    (args) => {
+      const r = args.request as RequestInit
+
+      Object.entries(headers).forEach(
+        ([k, v]: [key: string, value: string]): void => {
+          r.headers[k] = v
+        },
+      )
+
+      return next(args)
+    },
+  { step: 'build', name: 'customHeaders' },
+)
 const response = await client.send(command);
 
 console.log(response);
diff --git a/src/content/docs/r2/examples/cache-api.mdx b/src/content/docs/r2/examples/cache-api.mdx
index c5b5a3f0b9d2437..8b5d8ebd9354ccc 100644
--- a/src/content/docs/r2/examples/cache-api.mdx
+++ b/src/content/docs/r2/examples/cache-api.mdx
@@ -11,64 +11,67 @@ Use the [Cache API](/workers/runtime-apis/cache/) to store R2 objects in Cloudfl
 
 :::note
 
+
 You will need to [connect a custom domain](/workers/configuration/routing/custom-domains/) or [route](/workers/configuration/routing/routes/) to your Worker in order to use the Cache API. Cache API operations in the Cloudflare Workers dashboard editor, Playground previews, and any `*.workers.dev` deployments will have no impact.
 
+
 :::
 
 ```js
+
 export default {
-	async fetch(request, env, context) {
-		try {
-			const url = new URL(request.url);
-
-			// Construct the cache key from the cache URL
-			const cacheKey = new Request(url.toString(), request);
-			const cache = caches.default;
-
-			// Check whether the value is already available in the cache
-			// if not, you will need to fetch it from R2, and store it in the cache
-			// for future access
-			let response = await cache.match(cacheKey);
-
-			if (response) {
-				console.log(`Cache hit for: ${request.url}.`);
-				return response;
-			}
-
-			console.log(
-				`Response for request url: ${request.url} not present in cache. Fetching and caching request.`,
-			);
-
-			// If not in cache, get it from R2
-			const objectKey = url.pathname.slice(1);
-			const object = await env.MY_BUCKET.get(objectKey);
-			if (object === null) {
-				return new Response("Object Not Found", { status: 404 });
-			}
-
-			// Set the appropriate object headers
-			const headers = new Headers();
-			object.writeHttpMetadata(headers);
-			headers.set("etag", object.httpEtag);
-
-			// Cache API respects Cache-Control headers. Setting s-max-age to 10
-			// will limit the response to be in cache for 10 seconds max
-			// Any changes made to the response here will be reflected in the cached value
-			headers.append("Cache-Control", "s-maxage=10");
-
-			response = new Response(object.body, {
-				headers,
-			});
-
-			// Store the fetched response as cacheKey
-			// Use waitUntil so you can return the response without blocking on
-			// writing to cache
-			context.waitUntil(cache.put(cacheKey, response.clone()));
-
-			return response;
-		} catch (e) {
-			return new Response("Error thrown " + e.message);
-		}
-	},
+  async fetch(request, env, context) {
+    try {
+      const url = new URL(request.url);
+
+      // Construct the cache key from the cache URL
+      const cacheKey = new Request(url.toString(), request);
+      const cache = caches.default;
+
+      // Check whether the value is already available in the cache
+      // if not, you will need to fetch it from R2, and store it in the cache
+      // for future access
+      let response = await cache.match(cacheKey);
+
+      if (response) {
+        console.log(`Cache hit for: ${request.url}.`);
+        return response;
+      }
+
+      console.log(
+        `Response for request url: ${request.url} not present in cache. Fetching and caching request.`
+      );
+
+      // If not in cache, get it from R2
+      const objectKey = url.pathname.slice(1);
+      const object = await env.MY_BUCKET.get(objectKey);
+      if (object === null) {
+        return new Response('Object Not Found', { status: 404 });
+      }
+
+      // Set the appropriate object headers
+      const headers = new Headers();
+      object.writeHttpMetadata(headers);
+      headers.set('etag', object.httpEtag);
+
+      // Cache API respects Cache-Control headers. Setting s-max-age to 10
+      // will limit the response to be in cache for 10 seconds max
+      // Any changes made to the response here will be reflected in the cached value
+      headers.append('Cache-Control', 's-maxage=10');
+
+      response = new Response(object.body, {
+        headers,
+      });
+
+      // Store the fetched response as cacheKey
+      // Use waitUntil so you can return the response without blocking on
+      // writing to cache
+      context.waitUntil(cache.put(cacheKey, response.clone()));
+
+      return response;
+    } catch (e) {
+      return new Response('Error thrown ' + e.message);
+    }
+  },
 };
 ```
diff --git a/src/content/docs/r2/examples/terraform.mdx b/src/content/docs/r2/examples/terraform.mdx
index 6298b67ad2b5e29..70ba59913732088 100644
--- a/src/content/docs/r2/examples/terraform.mdx
+++ b/src/content/docs/r2/examples/terraform.mdx
@@ -7,17 +7,18 @@ products:
   - r2
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="keys" product="r2" />
-<br />
+<Render file="keys" product="r2" /><br/>
 
 This example shows how to configure R2 with Terraform using the [Cloudflare provider](https://github.com/cloudflare/terraform-provider-cloudflare).
 
 :::note[Note for using AWS provider]
 
+
 When using the Cloudflare Terraform provider, you can only manage buckets. To configure items such as CORS and object lifecycles, you will need to use the [AWS Provider](/r2/examples/terraform-aws/).
 
+
 :::
 
 With [`terraform`](https://developer.hashicorp.com/terraform/downloads) installed, create `main.tf` and copy the content below replacing with your API Token.
diff --git a/src/content/docs/r2/get-started/cli.mdx b/src/content/docs/r2/get-started/cli.mdx
index 9d545d0ef4b0755..96eb679c9c1e3f1 100644
--- a/src/content/docs/r2/get-started/cli.mdx
+++ b/src/content/docs/r2/get-started/cli.mdx
@@ -8,14 +8,7 @@ products:
   - r2
 ---
 
-import {
-	PackageManagers,
-	LinkCard,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { PackageManagers, LinkCard, Render, Tabs, TabItem, Steps } from "~/components";
 
 Manage R2 buckets and objects directly from your terminal. Use CLI tools to automate tasks and manage objects.
 
diff --git a/src/content/docs/r2/get-started/index.mdx b/src/content/docs/r2/get-started/index.mdx
index dd498e4f6f5b795..f23578ee0cbb2f0 100644
--- a/src/content/docs/r2/get-started/index.mdx
+++ b/src/content/docs/r2/get-started/index.mdx
@@ -16,7 +16,6 @@ Cloudflare R2 Storage allows developers to store large amounts of unstructured d
 ## Before you begin
 
 You need a Cloudflare account with an R2 subscription. If you do not have one:
-
 1. Go to the [Cloudflare Dashboard](https://dash.cloudflare.com/).
 2. Select **Storage & databases > R2 > Overview**
 3. Complete the checkout flow to add an R2 subscription to your account.
diff --git a/src/content/docs/r2/get-started/s3.mdx b/src/content/docs/r2/get-started/s3.mdx
index 30f8f11008b2c09..d8f07cb88333887 100644
--- a/src/content/docs/r2/get-started/s3.mdx
+++ b/src/content/docs/r2/get-started/s3.mdx
@@ -8,14 +8,7 @@ products:
   - r2
 ---
 
-import {
-	LinkCard,
-	PackageManagers,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { LinkCard, PackageManagers, Render, Tabs, TabItem, Steps } from "~/components";
 
 R2 provides support for a [S3-compatible API](/r2/api/s3/api/), which means you can use any S3 SDK, library, or tool to interact with your buckets. If you have existing code that works with S3, you can use it with R2 by changing the endpoint URL.
 
diff --git a/src/content/docs/r2/get-started/workers-api.mdx b/src/content/docs/r2/get-started/workers-api.mdx
index 408785ea7255ff2..2fca2b0febc4696 100644
--- a/src/content/docs/r2/get-started/workers-api.mdx
+++ b/src/content/docs/r2/get-started/workers-api.mdx
@@ -15,7 +15,7 @@ import {
 	Render,
 	Tabs,
 	TabItem,
-	Steps,
+	Steps
 } from "~/components";
 
 [Workers](/workers/) let you run code at the edge. When you bind an R2 bucket to a Worker, you can read and write objects directly using the [Workers API](/r2/api/workers/workers-api-usage/).
diff --git a/src/content/docs/r2/objects/delete-objects.mdx b/src/content/docs/r2/objects/delete-objects.mdx
index 30dedcd5ba096ac..a890b14c861b46d 100644
--- a/src/content/docs/r2/objects/delete-objects.mdx
+++ b/src/content/docs/r2/objects/delete-objects.mdx
@@ -17,7 +17,6 @@ You can delete objects from R2 using the dashboard, Workers API, S3 API, or comm
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. (Optional) Select the **View prefixes as directories** checkbox to view prefixes grouped as [folders](/r2/objects/#prefixes-and-folders).
 4. Select the objects or folders you want to delete. You can select a mix of both in the same operation.
@@ -111,19 +110,19 @@ wrangler r2 object delete test-bucket/image.png
 ## Related resources
 
 <LinkCard
-	title="Delete buckets"
-	href="/r2/buckets/delete-buckets/"
-	description="Empty all objects from a bucket and permanently delete it."
+  title="Delete buckets"
+  href="/r2/buckets/delete-buckets/"
+  description="Empty all objects from a bucket and permanently delete it."
 />
 
 <LinkCard
-	title="Bucket locks"
-	href="/r2/buckets/bucket-locks/"
-	description="Protect objects from accidental deletion with retention policies."
+  title="Bucket locks"
+  href="/r2/buckets/bucket-locks/"
+  description="Protect objects from accidental deletion with retention policies."
 />
 
 <LinkCard
-	title="Object lifecycles"
-	href="/r2/buckets/object-lifecycles/"
-	description="Automatically expire objects after a specified period."
+  title="Object lifecycles"
+  href="/r2/buckets/object-lifecycles/"
+  description="Automatically expire objects after a specified period."
 />
diff --git a/src/content/docs/r2/objects/download-objects.mdx b/src/content/docs/r2/objects/download-objects.mdx
index 78ebe64fe9940ee..d060979a0b675d4 100644
--- a/src/content/docs/r2/objects/download-objects.mdx
+++ b/src/content/docs/r2/objects/download-objects.mdx
@@ -17,7 +17,6 @@ You can download objects from R2 using the dashboard, Workers API, S3 API, or co
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Locate the object you want to download.
 4. Select **...** for the object and click **Download**.
@@ -109,4 +108,4 @@ Use [Wrangler](/workers/wrangler/install-and-update/) to download objects. Run t
 wrangler r2 object get test-bucket/image.png
 ```
 
-The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
+The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
\ No newline at end of file
diff --git a/src/content/docs/r2/objects/index.mdx b/src/content/docs/r2/objects/index.mdx
index 147e55a78a576d7..7cee8cf9e982a0c 100644
--- a/src/content/docs/r2/objects/index.mdx
+++ b/src/content/docs/r2/objects/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Objects are individual files or data that you store in an R2 bucket. Each object is identified by its key, a string like `images/photo.png`.
 
@@ -22,4 +22,4 @@ The R2 dashboard groups objects that share a common prefix into folders when the
 
 <DirectoryListing />
 
-<Render file="link-to-workers-r2-api" product="r2" />
+<Render file="link-to-workers-r2-api" product="r2"/>
\ No newline at end of file
diff --git a/src/content/docs/r2/platform/audit-logs.mdx b/src/content/docs/r2/platform/audit-logs.mdx
index ca1e6d74b1b1059..56b604e8c1363a0 100644
--- a/src/content/docs/r2/platform/audit-logs.mdx
+++ b/src/content/docs/r2/platform/audit-logs.mdx
@@ -22,18 +22,18 @@ For more information on how to access and use audit logs, refer to [Review audit
 
 The following configuration actions are logged:
 
-| Operation                          | Description                                                          |
-| ---------------------------------- | -------------------------------------------------------------------- |
-| CreateBucket                       | Creation of a new bucket.                                            |
-| DeleteBucket                       | Deletion of an existing bucket.                                      |
-| AddCustomDomain                    | Addition of a custom domain to a bucket.                             |
-| RemoveCustomDomain                 | Removal of a custom domain from a bucket.                            |
-| ChangeBucketVisibility             | Change to the managed public access (`r2.dev`) settings of a bucket. |
-| PutBucketStorageClass              | Change to the default storage class of a bucket.                     |
-| PutBucketLifecycleConfiguration    | Change to the object lifecycle configuration of a bucket.            |
-| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket.         |
-| PutBucketCors                      | Change to the CORS configuration for a bucket.                       |
-| DeleteBucketCors                   | Deletion of the CORS configuration for a bucket.                     |
+| Operation | Description |
+|-----------|-------------|
+| CreateBucket | Creation of a new bucket. |
+| DeleteBucket | Deletion of an existing bucket. |
+| AddCustomDomain | Addition of a custom domain to a bucket. |
+| RemoveCustomDomain | Removal of a custom domain from a bucket. |
+| ChangeBucketVisibility | Change to the managed public access (`r2.dev`) settings of a bucket. |
+| PutBucketStorageClass | Change to the default storage class of a bucket. |
+| PutBucketLifecycleConfiguration | Change to the object lifecycle configuration of a bucket. |
+| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket. |
+| PutBucketCors | Change to the CORS configuration for a bucket. |
+| DeleteBucketCors | Deletion of the CORS configuration for a bucket. |
 
 :::note
 Logs for data access operations, such as `GetObject` and `PutObject`, are not included in audit logs. To log HTTP requests made to public R2 buckets, use the [HTTP requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) Logpush dataset.
@@ -45,22 +45,23 @@ Below is an example of an audit log entry showing the creation of a new bucket:
 
 ```json
 {
-	"action": { "info": "CreateBucket", "result": true, "type": "create" },
-	"actor": {
-		"email": "<ACTOR_EMAIL>",
-		"id": "3f7b730e625b975bc1231234cfbec091",
-		"ip": "fe32:43ed:12b5:526::1d2:13",
-		"type": "user"
-	},
-	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-	"interface": "API",
-	"metadata": { "zone_name": "r2.cloudflarestorage.com" },
-	"newValue": "",
-	"newValueJson": {},
-	"oldValue": "",
-	"oldValueJson": {},
-	"owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
-	"resource": { "id": "my-bucket", "type": "r2.bucket" },
-	"when": "2024-07-15T16:32:52.412Z"
+  "action": { "info": "CreateBucket", "result": true, "type": "create" },
+  "actor": {
+    "email": "<ACTOR_EMAIL>",
+    "id": "3f7b730e625b975bc1231234cfbec091",
+    "ip": "fe32:43ed:12b5:526::1d2:13",
+    "type": "user"
+  },
+  "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+  "interface": "API",
+  "metadata": { "zone_name": "r2.cloudflarestorage.com" },
+  "newValue": "",
+  "newValueJson": {},
+  "oldValue": "",
+  "oldValueJson": {},
+  "owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
+  "resource": { "id": "my-bucket", "type": "r2.bucket" },
+  "when": "2024-07-15T16:32:52.412Z"
 }
+
 ```
diff --git a/src/content/docs/r2/platform/metrics-analytics.mdx b/src/content/docs/r2/platform/metrics-analytics.mdx
index e28dc53a56af003..91288c6dcf21e47 100644
--- a/src/content/docs/r2/platform/metrics-analytics.mdx
+++ b/src/content/docs/r2/platform/metrics-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 R2 exposes analytics that allow you to inspect the requests and storage of the buckets in your account.
 
@@ -16,8 +16,8 @@ The metrics displayed for a bucket in the [Cloudflare dashboard](https://dash.cl
 
 R2 currently has two datasets:
 
-| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                                  |
-| --------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------- |
+| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                          |
+| --------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- |
 | Operations                              | `r2OperationsAdaptiveGroups`                         | This dataset consists of the operations taken on a bucket within an account. |
 | Storage                                 | `r2StorageAdaptiveGroups`                            | This dataset consists of the storage of a bucket within an account.          |
 
@@ -58,7 +58,6 @@ Per-bucket analytics for R2 are available in the Cloudflare dashboard. To view c
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/r2/platform/troubleshooting.mdx b/src/content/docs/r2/platform/troubleshooting.mdx
index 726ef97a385e92b..e42a38c8bff9748 100644
--- a/src/content/docs/r2/platform/troubleshooting.mdx
+++ b/src/content/docs/r2/platform/troubleshooting.mdx
@@ -21,7 +21,6 @@ If you do have a CORS issue, refer to [Resolving CORS issues](#if-it-is-actually
 1. Open developer tools on your browser.
 2. Go to the **Network** tab and find the failing request. You may need to reload the page, as requests are only logged after developer tools have been opened.
 3. Check the response headers for the following two headers:
-
 - `cf-cache-status`
 - `cf-mitigated`
 
@@ -65,7 +64,7 @@ If your users are directly uploading to the bucket (for example, using the S3 or
 
 ### Bucket sharding
 
-For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket. While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
+For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket.  While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
 
 ## Objects named `This object is unnamed`
 
@@ -85,4 +84,4 @@ For example, uploading an object named `example/` into an R2 bucket will be disp
 <FileTree>
 - example
   - `This object is unnamed`
-</FileTree>
+</FileTree>
\ No newline at end of file
diff --git a/src/content/docs/r2/pricing.mdx b/src/content/docs/r2/pricing.mdx
index 6d420e4740d8b39..7c3d3a55663af73 100644
--- a/src/content/docs/r2/pricing.mdx
+++ b/src/content/docs/r2/pricing.mdx
@@ -27,13 +27,13 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 ## R2 pricing
 
-|                                    | Standard storage         | Infrequent Access storage |
-| ---------------------------------- | ------------------------ | ------------------------- |
-| Storage                            | $0.015 / GB-month        | $0.01 / GB-month          |
-| Class A Operations                 | $4.50 / million requests | $9.00 / million requests  |
-| Class B Operations                 | $0.36 / million requests | $0.90 / million requests  |
-| Data Retrieval (processing)        | None                     | $0.01 / GB                |
-| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                 |
+|                                    | Standard storage         | Infrequent Access storage                               |
+| ---------------------------------- | ------------------------ | ------------------------------------------------------- |
+| Storage                            | $0.015 / GB-month        | $0.01 / GB-month                                        |
+| Class A Operations                 | $4.50 / million requests | $9.00 / million requests                                |
+| Class B Operations                 | $0.36 / million requests | $0.90 / million requests                                |
+| Data Retrieval (processing)        | None                     | $0.01 / GB                                              |
+| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                                               |
 
 :::caution[Billable unit rounding]
 Cloudflare rounds up your usage to the next billing unit.
@@ -43,7 +43,7 @@ For example:
 - If you have performed one million and one operations, you will be billed for two million operations.
 - If you have used 1.1 GB-month, you will be billed for 2 GB-month.
 - If you have retrieved data (for infrequent access storage) for 1.1 GB, you will be billed for 2 GB.
-  :::
+:::
 
 ### Free tier
 
@@ -92,10 +92,10 @@ Data retrieval fees apply when you access or retrieve data from the Infrequent A
 
 For objects stored in Infrequent Access storage, you will be charged for the object for the minimum storage duration even if the object was deleted, moved, or replaced before the specified duration.
 
-| Storage class             | Minimum storage duration |
-| ------------------------- | ------------------------ |
-| Standard storage          | None                     |
-| Infrequent Access storage | 30 days                  |
+| Storage class                                          | Minimum storage duration |
+| ------------------------------------------------------ | ------------------------ |
+| Standard storage                                       | None                     |
+| Infrequent Access storage                              | 30 days                  |
 
 ## R2 Data Catalog pricing
 
@@ -127,25 +127,25 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 If a user writes 1,000 objects in R2 **Standard storage** for 1 month with an average size of 1 GB and reads each object 1,000 times during the month, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price      |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ---------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85     |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00      |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00      |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | None              | $0.00      |
-| **TOTAL**                   |                                                               |              |                   | **$14.85** |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85      |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00       |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00       |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA         | None              | $0.00       |
+| **TOTAL**                   |                                                               |              |                   | **$14.85**  |
 
 ### Infrequent access example
 
 If a user writes 1,000 objects in R2 Infrequent Access storage with an average size of 1 GB, stores them for 5 days, and then deletes them (delete operations are free), and during those 5 days each object is read 1,000 times, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier | Billable Quantity | Price      |
-| --------------------------- | ------------------------------------------------------------- | --------- | ----------------- | ---------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA        | 1,000 GB-months   | $10.00     |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA        | 1,000             | $9.00      |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA        | 1 million         | $0.90      |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA        | 1,000 GB          | $10.00     |
-| **TOTAL**                   |                                                               |           |                   | **$29.90** |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA           | 1,000 GB-months   | $10.00      |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA           | 1,000             | $9.00       |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA           | 1 million         | $0.90       |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | 1,000 GB          | $10.00      |
+| **TOTAL**                   |                                                               |              |                   | **$29.90**  |
 
 Note that the minimal storage duration for infrequent access storage is 30 days, which means the billable quantity is 1,000 GB-months, rather than 167 GB-months.
 
diff --git a/src/content/docs/r2/r2-sql.mdx b/src/content/docs/r2/r2-sql.mdx
index 727a004053c732a..690e0b283548807 100644
--- a/src/content/docs/r2/r2-sql.mdx
+++ b/src/content/docs/r2/r2-sql.mdx
@@ -10,4 +10,4 @@ description: >-
   R2 SQL is a serverless SQL interface for Cloudflare R2, enabling querying and analyzing data.
 products:
   - r2
----
+---
\ No newline at end of file
diff --git a/src/content/docs/r2/reference/data-location.mdx b/src/content/docs/r2/reference/data-location.mdx
index a55ac28a3ebbc87..64607b3dbd621ac 100644
--- a/src/content/docs/r2/reference/data-location.mdx
+++ b/src/content/docs/r2/reference/data-location.mdx
@@ -29,7 +29,6 @@ You can choose to automatically create your bucket in the closest available regi
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, leave _None_ selected for automatic selection or choose a region from the list.
@@ -80,7 +79,6 @@ Use Jurisdictional Restrictions when you need to ensure data is stored and proce
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
diff --git a/src/content/docs/r2/reference/data-security.mdx b/src/content/docs/r2/reference/data-security.mdx
index 96c66a58a3eb8df..15c1260d9648ae3 100644
--- a/src/content/docs/r2/reference/data-security.mdx
+++ b/src/content/docs/r2/reference/data-security.mdx
@@ -26,8 +26,10 @@ Access over plaintext HTTP (without TLS/SSL) can be disabled by connecting a [cu
 
 :::note
 
+
 R2 custom domains use Cloudflare for SaaS certificates and cannot be customized. Even if you have [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/), the advanced certificate will not be used due to [certificate prioritization](/ssl/reference/certificate-and-hostname-priority/).
 
+
 :::
 
 ## Compliance
diff --git a/src/content/docs/r2/reference/durability.mdx b/src/content/docs/r2/reference/durability.mdx
index 5d15f76865bd036..177e6ed4bd08d13 100644
--- a/src/content/docs/r2/reference/durability.mdx
+++ b/src/content/docs/r2/reference/durability.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-R2 is designed to provide 99.999999999% (eleven 9s) of annual durability. This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
+R2 is designed to provide 99.999999999% (eleven 9s) of annual durability.  This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
 
 ## How R2 achieves eleven-nines durability
 
@@ -22,7 +22,7 @@ R2's durability is built on multiple layers of redundancy and data protection:
 
 ### Considerations
 
-- Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
-- R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
-- Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
-- Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
+* Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
+* R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
+* Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
+* Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
diff --git a/src/content/docs/r2/reference/unicode-interoperability.mdx b/src/content/docs/r2/reference/unicode-interoperability.mdx
index 77796a1f1294a90..1543c6629fa5744 100644
--- a/src/content/docs/r2/reference/unicode-interoperability.mdx
+++ b/src/content/docs/r2/reference/unicode-interoperability.mdx
@@ -16,8 +16,8 @@ R2 preserves the encoding for display though. When you list the objects, you wil
 
 There are still some platform-specific differences to consider:
 
-- Windows and macOS filenames are case-insensitive while R2 and Linux are not.
-- Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
-- Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
+* Windows and macOS filenames are case-insensitive while R2 and Linux are not.
+* Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
+* Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
 
 If it is important for you to be able to bypass the unicode equivalence and use byte-oriented key names, contact your Cloudflare account team.
diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx
index 1025cfea8f7c9bb..0c041c84fc44833 100644
--- a/src/content/docs/r2/tutorials/cloudflare-access.mdx
+++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx
@@ -49,7 +49,7 @@ To create an Access application for your R2 bucket:
    Ensure that your policies only allow the users within your organization that need access to this R2 bucket.
    :::
 
-5. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
+6. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
 
 ## 3. Connect a custom domain
 
diff --git a/src/content/docs/r2/tutorials/mastodon.mdx b/src/content/docs/r2/tutorials/mastodon.mdx
index dd7a6b339aace64..3a1bb7b0eae2ed8 100644
--- a/src/content/docs/r2/tutorials/mastodon.mdx
+++ b/src/content/docs/r2/tutorials/mastodon.mdx
@@ -23,8 +23,10 @@ Different from the default hostname of your Mastodon instance, object storage fo
 
 :::note
 
+
 If you move from R2 to another S3 compatible service later on, you can continue using the same hostname determined in this step. We do not recommend changing the hostname after the instance has been running to avoid breaking historical file references. In such a scenario, [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) can be used to instruct requests reaching the previous hostname to refer to the new hostname.
 
+
 :::
 
 ### 2. Create and set up an R2 bucket
@@ -32,7 +34,6 @@ If you move from R2 to another S3 compatible service later on, you can continue
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter your bucket name and then select **Create bucket**. This name is internal when setting up your Mastodon instance and is not publicly accessible.
 4. Once the bucket is created, navigate to the **Settings** tab of this bucket and copy the value of **S3 API**.
diff --git a/src/content/docs/r2/tutorials/postman.mdx b/src/content/docs/r2/tutorials/postman.mdx
index 4bec7f80443cc16..2c8fbc313867b2b 100644
--- a/src/content/docs/r2/tutorials/postman.mdx
+++ b/src/content/docs/r2/tutorials/postman.mdx
@@ -11,7 +11,7 @@ products:
 
 import { DashButton } from "~/components";
 
-Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290) includes a complete list of operations supported by the platform.
+Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290) includes a complete list of operations supported by the platform.
 
 ## 1. Purchase R2
 
@@ -19,11 +19,11 @@ This guide assumes that you have made a Cloudflare account and purchased R2.
 
 ## 2. Explore R2 in Postman
 
-Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
+Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
 
 ## 3. Configure your R2 credentials
 
-In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
+In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
 
 To execute basic operations, you must set the `account-id`, `r2-access-key-id`, and `r2-secret-access-key` variables in the Postman dashboard > **Variables**.
 
@@ -32,9 +32,8 @@ To do this:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. In **R2**, under **Manage R2 API Tokens** on the right side of the dashboard, copy your Cloudflare account ID.
-3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation).
+3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation).
 4. Set the **CURRENT VALUE** of `account-id` to your Cloudflare account ID and select **Save**.
 
 Next, generate an R2 API token:
@@ -42,7 +41,6 @@ Next, generate an R2 API token:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. On the right hand sidebar, select **Manage R2 API Tokens**.
 3. Select **Create API token**.
 4. Name your token **Postman** by selecting the pencil icon next to the API name and grant it the **Edit** permission.
@@ -51,7 +49,7 @@ Guard this token and the **Access Key ID** and **Secret Access Key** closely. Yo
 
 After you have created your API token in the Cloudflare dashboard:
 
-1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation) > **Variables**.
+1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation) > **Variables**.
 2. Copy `Access Key ID` value from the Cloudflare dashboard and paste it into Postman’s `r2-access-key-id` variable value and select **Save**.
 3. Copy the `Secret Access Key` value from the Cloudflare dashboard and paste it into Postman’s `r2-secret-access-key` variable value and select **Save**.
 
diff --git a/src/content/docs/r2/video-tutorials.mdx b/src/content/docs/r2/video-tutorials.mdx
index f92a3914495462c..67585e1469ac91a 100644
--- a/src/content/docs/r2/video-tutorials.mdx
+++ b/src/content/docs/r2/video-tutorials.mdx
@@ -12,9 +12,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Introduction to R2"
-		description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
-		href="/learning-paths/r2-intro/series/r2-1/"
-	/>
+    <LinkCard
+        title="Introduction to R2"
+        description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
+        href="/learning-paths/r2-intro/series/r2-1/"
+    />
 </CardGrid>
diff --git a/src/content/docs/radar/concepts/index.mdx b/src/content/docs/radar/concepts/index.mdx
index e439f4733f5f884..e8c3c876f284ebb 100644
--- a/src/content/docs/radar/concepts/index.mdx
+++ b/src/content/docs/radar/concepts/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/concepts/normalization.mdx b/src/content/docs/radar/concepts/normalization.mdx
index 3a2a09e5b4ebd78..dbf55dfbe42a9f7 100644
--- a/src/content/docs/radar/concepts/normalization.mdx
+++ b/src/content/docs/radar/concepts/normalization.mdx
@@ -19,7 +19,7 @@ Refer to the `result.meta.normalization` property in the response to check which
 | `PERCENTAGE`            | Values represent percentages.                                                                                                                                                    |
 | `PERCENTAGE_CHANGE`     | Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period.                                   |
 | `OVERLAPPED_PERCENTAGE` | Values represent percentages that exceed 100% due to overlap.                                                                                                                    |
-| `MIN_MAX`               | Values have been normalized using [min-max](<https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_(min-max_normalization)>).                                                  |
+| `MIN_MAX`               | Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)).                                                  |
 | `MIN0_MAX`              | Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
 | `RAW_VALUES`            | Values are raw and have not been changed.                                                                                                                                        |
 
diff --git a/src/content/docs/radar/get-started/configure-alerts.mdx b/src/content/docs/radar/get-started/configure-alerts.mdx
index 64ad4396db7c424..6e7641992176d98 100644
--- a/src/content/docs/radar/get-started/configure-alerts.mdx
+++ b/src/content/docs/radar/get-started/configure-alerts.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications when Radar detects changes impacting countries, regions, or autonomous systems.
 
diff --git a/src/content/docs/radar/get-started/embed.mdx b/src/content/docs/radar/get-started/embed.mdx
index bf036cde8f960ad..249eccb402d8918 100644
--- a/src/content/docs/radar/get-started/embed.mdx
+++ b/src/content/docs/radar/get-started/embed.mdx
@@ -25,8 +25,8 @@ Charts supporting this feature will have a share icon next to its description.
 
 1. Select the Share icon next to the description of the chart you wish to share.
 2. Select between Fixed Time and Real Time.
-   - Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
-   - Fixed Time will always display a chart with only the currently visible data points.
+   * Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
+   * Fixed Time will always display a chart with only the currently visible data points.
 3. Select Copy Code and paste the code into your web page.
 
 **Note**: Your current selections, such as date range, location, autonomous system (ASN), and visible series, will be reflected in the shared chart.
diff --git a/src/content/docs/radar/get-started/index.mdx b/src/content/docs/radar/get-started/index.mdx
index 809a736dd35ebc9..1ce36868a710f4f 100644
--- a/src/content/docs/radar/get-started/index.mdx
+++ b/src/content/docs/radar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/get-started/making-comparisons.mdx b/src/content/docs/radar/get-started/making-comparisons.mdx
index 984fcafb3a77490..9bffd560f9e690b 100644
--- a/src/content/docs/radar/get-started/making-comparisons.mdx
+++ b/src/content/docs/radar/get-started/making-comparisons.mdx
@@ -35,26 +35,26 @@ The response (shortened below for brevity) uses the provided `name` property to
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"us_data": {
-			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
-			"values": ["0.871752", "1"]
-		},
-		"pt_data": {
-			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
-			"values": ["0.020457", "0.012313"]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-10-26T17:00:00Z",
-				"endTime": "2022-11-02T17:00:00Z"
-			},
-			"aggInterval": "ONE_HOUR"
+  "success": true,
+  "errors": [],
+  "result": {
+    "us_data": {
+      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
+      "values": [ "0.871752", "1" ]
+    },
+    "pt_data": {
+      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
+      "values": [ "0.020457", "0.012313" ]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-10-26T17:00:00Z",
+        "endTime": "2022-11-02T17:00:00Z"
+      },
+      "aggInterval": "ONE_HOUR",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -81,24 +81,14 @@ Now, in the `result` property, you should get something like this:
 
 ```json
 {
-	"this_week": {
-		"timestamps": [
-			"2022-10-27T13:00:00Z",
-			"2022-10-27T14:00:00Z",
-			"...",
-			"2022-11-03T12:00:00Z"
-		],
-		"values": ["0.794321", "1", "...", "0.718433"]
-	},
-	"previous_week": {
-		"timestamps": [
-			"2022-10-20T13:00:00Z",
-			"2022-10-20T14:00:00Z",
-			"...",
-			"2022-10-27T12:00:00Z"
-		],
-		"values": ["0.774392", "0.835071", "...", "0.720181"]
-	}
+  "this_week": {
+    "timestamps": [ "2022-10-27T13:00:00Z", "2022-10-27T14:00:00Z", "...", "2022-11-03T12:00:00Z" ],
+    "values": [ "0.794321", "1", "...", "0.718433"]
+  },
+  "previous_week": {
+    "timestamps": [ "2022-10-20T13:00:00Z", "2022-10-20T14:00:00Z", "...", "2022-10-27T12:00:00Z" ],
+    "values": [ "0.774392", "0.835071", "...", "0.720181"]
+  }
 }
 ```
 
@@ -128,21 +118,11 @@ The `result` property should return a response like this:
 ```json
 {
 	"tonga": {
-		"timestamps": [
-			"2022-10-15T02:00:00Z",
-			"2022-10-15T03:00:00Z",
-			"2022-10-15T04:00:00Z",
-			"2022-10-15T05:00:00Z"
-		],
+		"timestamps": ["2022-10-15T02:00:00Z", "2022-10-15T03:00:00Z", "2022-10-15T04:00:00Z", "2022-10-15T05:00:00Z"],
 		"values": ["1.0", "0.832473", "0.820083", "0.79408"]
 	},
 	"tonga_outage": {
-		"timestamps": [
-			"2022-01-15T02:00:00Z",
-			"2022-01-15T03:00:00Z",
-			"2022-01-15T04:00:00Z",
-			"2022-01-15T05:00:00Z"
-		],
+		"timestamps": ["2022-01-15T02:00:00Z", "2022-01-15T03:00:00Z", "2022-01-15T04:00:00Z", "2022-01-15T05:00:00Z"],
 		"values": ["0.354105", "0.357287", "0.181811", "0.044198"]
 	}
 }
diff --git a/src/content/docs/radar/investigate/application-layer-attacks.mdx b/src/content/docs/radar/investigate/application-layer-attacks.mdx
index 62b6591ff068b45..bef19dc325ce63d 100644
--- a/src/content/docs/radar/investigate/application-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/application-layer-attacks.mdx
@@ -40,27 +40,27 @@ From the abbreviated response below, we can conclude that distributed denial-of-
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks": {
-			"timestamps": ["2022-11-05T11:00:00Z", ".."],
-			"ddos": ["53.824302", "54.305823", ".."],
-			"waf": ["39.760956", "39.31228", ".."],
-			"ip_reputation": ["5.623487", "5.485468", ".."],
-			"access_rules": ["0.648368", "0.676456", ".."],
-			"bot_management": ["0.139733", "0.217155", ".."],
-			"api_shield": ["0.003154", "0.002819", ".."],
-			"data_loss_prevention": ["0.0", "0.0", ".."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-05T11:00:00Z",
-				"endTime": "2022-11-06T11:00:00Z"
-			}
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks": {
+      "timestamps": ["2022-11-05T11:00:00Z", ".."],
+      "ddos": ["53.824302", "54.305823",  ".."],
+      "waf": ["39.760956", "39.31228",  ".."],
+      "ip_reputation": ["5.623487", "5.485468",  ".."],
+      "access_rules": ["0.648368", "0.676456",  ".."],
+      "bot_management": ["0.139733", "0.217155",  ".."],
+      "api_shield": ["0.003154", "0.002819",  ".."],
+      "data_loss_prevention": ["0.0", "0.0",  ".."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-05T11:00:00Z",
+        "endTime": "2022-11-06T11:00:00Z"
+      },
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -79,9 +79,9 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"attacks_gb": {
 			"waf": "75.012138",
 			"ddos": "18.539149",
@@ -90,10 +90,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 			"bot_management": "0.131998",
 			"api_shield": "0.003178",
 			"data_loss_prevention": "0.0"
-		},
+  	},
 		"meta": {
 			// ...
-		}
+    }
 	}
 }
 ```
@@ -115,10 +115,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks_target": [
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks_target": [
 			{
 				"targetCountryName": "Belgium",
 				"targetCountryAlpha2": "BE",
@@ -150,14 +150,14 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 				"rank": 5
 			}
 		],
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-05T12:00:00Z",
-				"endTime": "2022-11-06T12:00:00Z"
-			}
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-05T12:00:00Z",
+        "endTime": "2022-11-06T12:00:00Z"
+      },
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -178,9 +178,9 @@ A typical response will be similar to the following:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"originCountryName": "United States",
@@ -223,10 +223,10 @@ A typical response will be similar to the following:
 				"rank": 5
 			}
 		],
-		"meta": {
+    "meta": {
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/dns.mdx b/src/content/docs/radar/investigate/dns.mdx
index 837edba24ef5632..59db1f37eb09dbc 100644
--- a/src/content/docs/radar/investigate/dns.mdx
+++ b/src/content/docs/radar/investigate/dns.mdx
@@ -27,9 +27,9 @@ The response shows that most queries come from the United States and Brazil:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "US",
@@ -43,9 +43,9 @@ The response shows that most queries come from the United States and Brazil:
 			}
 		],
 		"meta": {
-			// ...
-		}
-	}
+      // ...
+    }
+  }
 }
 ```
 
@@ -60,9 +60,9 @@ Returns the following response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "RU",
@@ -76,9 +76,9 @@ Returns the following response:
 			}
 		],
 		"meta": {
-			// ...
-		}
-	}
+      // ...
+    }
+  }
 }
 ```
 
@@ -86,7 +86,7 @@ As expected, most queries come from Russia.
 
 :::note
 
-Note that these examples return the total number of DNS queries from a location to a hostname, _out_ of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
+Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
 :::
 
 You can also provide multiple hostnames. Refer to [Get DNS top locations](/api/resources/radar/subresources/dns/subresources/top/methods/locations/) for more information. This is useful when the application you want to explore uses several hostnames to serve its content (like a hostname for the main website, another hostname dedicated to its API, etc.).
diff --git a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
index 26d9f65fea55f7d..9c025150aa46f67 100644
--- a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
+++ b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
@@ -8,10 +8,10 @@ products:
   - radar
 ---
 
-Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/), Cloudflare's public DNS resolver. Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
+Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/),  Cloudflare's public DNS resolver.  Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
 
-- An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
-- An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
+* An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
+* An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
 
 ## List of endpoints
 
@@ -26,10 +26,10 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"top_0": [
+  "success": true,
+  "errors": [],
+  "result": {
+    "top_0": [
 			{
 				"rank": 1,
 				"domain": "google.com"
@@ -50,8 +50,8 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 				"rank": 5,
 				"domain": "apple.com"
 			}
-		]
-	},
+    ]
+  },
 	"meta": {
 		// ...
 	}
@@ -75,21 +75,24 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets?limit=10&datasetType=R
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"datasets": [
 			{
 				"id": 213,
 				"title": "Top 1000000 ranking domains",
 				"description": "Unordered top 1000000 from 2023-01-02 to 2023-01-09",
 				"type": "RANKING_BUCKET",
-				"tags": ["GLOBAL", "top_1000000"],
+				"tags": [
+					"GLOBAL",
+					"top_1000000"
+				],
 				"meta": {
 					"top": 1000000
 				},
 				"alias": "ranking_top_1000000"
-			}
+			},
 			// ...
 		]
 	}
@@ -111,9 +114,9 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets/download" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"dataset": {
 			"url": "https://example.com/download"
 		}
diff --git a/src/content/docs/radar/investigate/http-requests.mdx b/src/content/docs/radar/investigate/http-requests.mdx
index f850973ae9af912..8fcdba8ef35ed24 100644
--- a/src/content/docs/radar/investigate/http-requests.mdx
+++ b/src/content/docs/radar/investigate/http-requests.mdx
@@ -19,9 +19,9 @@ Most of the charts in the [Adoption and Usage](https://radar.cloudflare.com/adop
 
 These endpoints can be broadly split into:
 
-- `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
-- `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
-- `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
+* `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
+* `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
+* `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
 
 ## List of endpoints
 
@@ -40,29 +40,29 @@ Here is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"human": {
-			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-			"mobile": ["52.5532", "52.146628", ".."],
-			"desktop": ["47.394791", "47.800731", ".."],
-			"other": ["0.052009", "0.052642", ".."]
-		},
-		"bot": {
-			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-			"desktop": ["83.833892", "84.017711", ".."],
-			"mobile": ["16.156748", "15.969936", ".."],
-			"other": ["0.00936", "0.012353", ".."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-03T13:00:00Z",
-				"endTime": "2022-11-04T13:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
-		}
-	}
+  "success": true,
+  "errors": [],
+  "result": {
+    "human": {
+      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+      "mobile": ["52.5532", "52.146628", ".."],
+      "desktop": ["47.394791", "47.800731", ".."],
+      "other": ["0.052009", "0.052642", ".."]
+    },
+    "bot": {
+      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+      "desktop": ["83.833892", "84.017711", ".."],
+      "mobile": ["16.156748", "15.969936", ".."],
+      "other": ["0.00936", "0.012353", ".."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-03T13:00:00Z",
+        "endTime": "2022-11-04T13:00:00Z"
+      },
+      "normalization": "PERCENTAGE"
+    }
+  }
 }
 ```
 
@@ -90,9 +90,9 @@ Here is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"human": {
 			"mobile": "54.967243",
 			"desktop": "44.974006",
@@ -103,7 +103,7 @@ Here is the abbreviated response:
 			"mobile": "16.707455",
 			"other": "0.017093"
 		}
-	}
+  }
 }
 ```
 
@@ -122,9 +122,9 @@ This returns the following:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"human": {
 			"IPv4": "76.213647",
 			"IPv6": "23.786353"
@@ -133,7 +133,7 @@ This returns the following:
 			"IPv4": "91.492032",
 			"IPv6": "8.507968"
 		}
-	}
+  }
 }
 ```
 
@@ -156,9 +156,9 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"ipv6": [
 			{
 				"clientCountryAlpha2": "IN",
@@ -186,7 +186,7 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 				"value": "39.1514"
 			}
 		]
-	}
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/index.mdx b/src/content/docs/radar/investigate/index.mdx
index 5c1a9cd5a898a6c..c377e8628eba30c 100644
--- a/src/content/docs/radar/investigate/index.mdx
+++ b/src/content/docs/radar/investigate/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore the different types of data available in Cloudflare Radar, from NetFlows (what feeds the [Internet Traffic Change](https://radar.cloudflare.com/) chart in Radar) to HTTP requests and DNS queries.
 
diff --git a/src/content/docs/radar/investigate/netflows.mdx b/src/content/docs/radar/investigate/netflows.mdx
index 3971efa9cabc498..1d7c85ee2290995 100644
--- a/src/content/docs/radar/investigate/netflows.mdx
+++ b/src/content/docs/radar/investigate/netflows.mdx
@@ -36,9 +36,9 @@ This is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS3243_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.565885", "0.586434", "..."]
@@ -64,9 +64,9 @@ The abbreviated response is:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
@@ -92,9 +92,9 @@ which would lead to a response like this:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
diff --git a/src/content/docs/radar/investigate/network-layer-attacks.mdx b/src/content/docs/radar/investigate/network-layer-attacks.mdx
index 56394fa33270271..edd685c50ae34f8 100644
--- a/src/content/docs/radar/investigate/network-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/network-layer-attacks.mdx
@@ -35,36 +35,36 @@ If we inspect the abbreviated response below, we can conclude that globally, at
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"global": {
-			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-			"udp": ["50.784034", "51.055221", "..."],
-			"tcp": ["49.213944", "48.943769", "..."],
-			"icmp": ["0.002023", "0.001009", "..."],
-			"gre": ["0.0", "0.0", "0.0", "..."]
-		},
-		"singapore": {
-			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-			"tcp": ["79.605287", "83.943885", "..."],
-			"udp": ["20.394594", "16.056115", "..."],
-			"icmp": ["0.000119", "0.0", "..."],
-			"gre": ["0.0", "0.0", "..."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-06T13:00:00Z",
-				"endTime": "2022-11-07T13:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
+  "success": true,
+  "errors": [],
+  "result": {
+    "global": {
+      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+      "udp": ["50.784034", "51.055221", "..."],
+      "tcp": ["49.213944", "48.943769", "..."],
+      "icmp": ["0.002023", "0.001009", "..."],
+      "gre": ["0.0", "0.0", "0.0", "..."]
+    },
+    "singapore": {
+      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+      "tcp": ["79.605287", "83.943885", "..."],
+      "udp": ["20.394594", "16.056115", "..."],
+      "icmp": ["0.000119", "0.0", "..."],
+      "gre": ["0.0", "0.0", "..."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-06T13:00:00Z",
+        "endTime": "2022-11-07T13:00:00Z"
+      },
+      "normalization": "PERCENTAGE",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
-We can also conclude that the distribution of network layer attacks coming from Singapore — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
+We can also conclude that the distribution of network layer attacks coming from Singapore  — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
 
 For more information refer to the [API reference](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) for this endpoint.
 
@@ -81,24 +81,24 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer3/summary?location
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks_ru": {
-			"udp": "86.682356",
-			"tcp": "11.928664",
-			"gre": "1.381015",
-			"icmp": "0.007965"
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-06T15:00:00Z",
-				"endTime": "2022-11-07T15:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks_ru": {
+      "udp": "86.682356",
+      "tcp": "11.928664",
+      "gre": "1.381015",
+      "icmp": "0.007965"
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-06T15:00:00Z",
+        "endTime": "2022-11-07T15:00:00Z"
+      },
+      "normalization": "PERCENTAGE",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/outages.mdx b/src/content/docs/radar/investigate/outages.mdx
index 4627c42298d06d6..6d6f0d662f2a97e 100644
--- a/src/content/docs/radar/investigate/outages.mdx
+++ b/src/content/docs/radar/investigate/outages.mdx
@@ -12,13 +12,13 @@ products:
 
 Refer the [blog post](https://blog.cloudflare.com/announcing-cloudflare-radar-outage-center/) for more information but, in short, Radar provides the following information:
 
-- **Location**: Where was the outage?
-- **ASN**: What autonomous system experienced a disruption in connectivity?
-- **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
-- **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
-- **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
-- **Start time**: When did the outage start?
-- **End time**: When did the outage end?
+* **Location**: Where was the outage?
+* **ASN**: What autonomous system experienced a disruption in connectivity?
+* **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
+* **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
+* **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
+* **Start time**: When did the outage start?
+* **End time**: When did the outage end?
 
 ## List of endpoints
 
diff --git a/src/content/docs/radar/investigate/url-scanner.mdx b/src/content/docs/radar/investigate/url-scanner.mdx
index ab5ce64f3fd1662..ec99e52a8ef0c7b 100644
--- a/src/content/docs/radar/investigate/url-scanner.mdx
+++ b/src/content/docs/radar/investigate/url-scanner.mdx
@@ -14,7 +14,7 @@ To better understand Internet usage around the world, use Cloudflare's URL Scann
 
 ## Use the API
 
-To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with _Account_ > _URL Scanner_ in the **Permissions** group, and select _Edit_ as the access level.
+To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with *Account* > *URL Scanner* in the **Permissions** group, and select *Edit* as the access level.
 
 Once you have the token, and you know your `account_id`, you are ready to make your first request to the API at `https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/`.
 
@@ -37,11 +37,11 @@ A successful response will have a status code of `200` and be similar to the fol
 
 ```json
 {
-	"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-	"api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-	"visibility": "public",
-	"url": "https://www.example.com",
-	"message": "Submission successful"
+  "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+  "api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+  "visibility": "public",
+  "url": "https://www.example.com",
+  "message": "Submission successful"
 }
 ```
 
@@ -56,9 +56,11 @@ Here's an example request body with some custom configuration options:
 ```json
 {
 	"url": "https://example.com",
-	"screenshotsResolutions": ["desktop", "mobile", "tablet"],
-	"customagent": "XXX-my-user-agent",
-	"referer": "example",
+	"screenshotsResolutions": [
+		"desktop", "mobile", "tablet"
+	],
+  "customagent": "XXX-my-user-agent",
+  "referer": "example",
 	"customHeaders": {
 		"Authorization": "xxx-token"
 	},
@@ -66,7 +68,7 @@ Here's an example request body with some custom configuration options:
 }
 ```
 
-Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In effect, only users with knowledge of the scan ID will be able to access it.
+Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In  effect, only users with knowledge of the scan ID will be able to access it.
 
 There will also be three screenshots taken of the webpage, one per target device type. The [`User-Agent`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) will be set as "XXX-my-user-agent". Note that you can set any custom HTTP header, including [Authorization](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Authorization).
 
@@ -82,38 +84,38 @@ While the scan is in progress, the HTTP status code will be `404`; once it is fi
 
 The response will include, among others, the following top properties:
 
-- `task` - Information on the scan submission.
-- `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
-- `data.requests` - Request chains involved in the page load.
-- `data.cookies` - Cookies set by the page.
-- `data.globals` - Non-standard JavaScript global variables.
-- `data.console` - Console logs.
-- `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
-- `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
-- `lists.ips` - IPs contacted.
-- `lists.asns` - AS Numbers contacted.
-- `lists.domains` - Hostnames contacted, including `dns` record information.
-- `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
-- `lists.certificates` - TLS certificates of HTTP responses.
-- `verdicts` - Verdicts on malicious content.
+* `task` - Information on the scan submission.
+* `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
+* `data.requests` - Request chains involved in the page load.
+* `data.cookies` - Cookies set by the page.
+* `data.globals` - Non-standard JavaScript global variables.
+* `data.console` - Console logs.
+* `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
+* `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
+* `lists.ips` - IPs contacted.
+* `lists.asns` - AS Numbers contacted.
+* `lists.domains` - Hostnames contacted, including `dns` record information.
+* `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
+* `lists.certificates` - TLS certificates of HTTP responses.
+* `verdicts` - Verdicts on malicious content.
 
 Some examples of more specific properties include:
 
-- `task.uuid` - ID of the scan.
-- `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
-- `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
-- `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
-- `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
-- `meta.processors.phishing` - What kind of phishing, if any, was detected.
-- `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
-- `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
-- `page.url` - URL of the primary request, after all HTTP redirects.
-- `page.country` - Country name from geolocation data associated with the main IP address contacted.
-- `page.history` - Main page history, including any HTTP redirects.
-- `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
-- `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
-- `page.favicon.hash` - MD5 hash of the favicon.
-- `verdicts.overall.malicious` - Whether the website was considered malicious _at the time of the scan_. Please check the remaining properties for each subsystem(s) for specific threats detected.
+* `task.uuid` - ID of the scan.
+* `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
+* `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
+* `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
+* `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
+* `meta.processors.phishing` - What kind of phishing, if any, was detected.
+* `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
+* `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
+* `page.url` - URL of the primary request, after all HTTP redirects.
+* `page.country` - Country name from geolocation data associated with the main IP address contacted.
+* `page.history` - Main page history, including any HTTP redirects.
+* `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
+* `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
+* `page.favicon.hash` - MD5 hash of the favicon.
+* `verdicts.overall.malicious` - Whether the website was considered malicious *at the time of the scan*. Please check the remaining properties for each subsystem(s) for specific threats detected.
 
 The [Get URL Scan](/api/resources/url_scanner/subresources/scans/methods/get/) API endpoint documentation contains the full response schema.
 
@@ -130,6 +132,7 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/v2/s
 --header "Authorization: Bearer <API_TOKEN>"
 ```
 
+
 If, instead, you wanted to search for scans that made at least one request to the hostname `cdnjs.cloudflare.com`, for example sites that use a JavaScript library hosted at `cdnjs.cloudflare.com`, use the query parameter `hostname=cdnjs.cloudflare.com`:
 
 ```bash
@@ -150,13 +153,14 @@ Some other example queries:
 
 Go to [Search URL scans](/api/resources/url_scanner/subresources/scans/methods/list/) in the API documentation for the full list of available options.
 
+
 ### Security Center
 
 Alternatively, you can search in the Security Center:
 
 1. In the Cloudflare dashboard, go to the **Investigate** page.
 
-   <DashButton url="/?to=/:account/security-center/investigate" />
+	 <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your query and select **Search**.
 
@@ -172,7 +176,7 @@ To scan a URL based on your geographic location:
 2. Go to **Location** > Select which country to scan the URL from.
 3. Select **Scan now**.
 
-You can also use the [API](<https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20>) to scan a URL from a specific location.
+You can also use the [API](https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20) to scan a URL from a specific location.
 
 In Security Center, you can retrieve pre-filtered information by:
 
@@ -183,4 +187,4 @@ In Security Center, you can retrieve pre-filtered information by:
 - Identical ASN
 - Identical IP
 - Identical domain
-- Identical final URL (after all redirections)
+- Identical final URL (after all redirections)
\ No newline at end of file
diff --git a/src/content/docs/radar/mcp-server.mdx b/src/content/docs/radar/mcp-server.mdx
index 56303e7fd5ac8ad..ef902ec41e498a5 100644
--- a/src/content/docs/radar/mcp-server.mdx
+++ b/src/content/docs/radar/mcp-server.mdx
@@ -10,4 +10,4 @@ sidebar:
     variant: note
 products:
   - radar
----
+---
\ No newline at end of file
diff --git a/src/content/docs/radar/reference/index.mdx b/src/content/docs/radar/reference/index.mdx
index 1223e257fc2e24e..605b54567f61ed5 100644
--- a/src/content/docs/radar/reference/index.mdx
+++ b/src/content/docs/radar/reference/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review reference information related to Cloudflare Radar:
 
diff --git a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
index d08ecc4c77e6915..7b84e9fcb6eff4b 100644
--- a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
+++ b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
@@ -6,7 +6,7 @@ products:
   - radar
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Quarterly DDoS threat reports provide a comprehensive overview of <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attack</GlossaryTooltip> insights and trends over a three-month period.
 
@@ -14,7 +14,7 @@ Thanks to our vast network, Cloudflare provides insights on the evolving threat
 
 Find the latest quarterly DDoS threat reports in the [**Reports**](https://radar.cloudflare.com/reports) section of Cloudflare Radar.
 
----
+***
 
 ## Methodologies
 
@@ -58,7 +58,7 @@ To calculate the attack size, duration, attack vectors, and emerging threats, Cl
 
 However, in the **Network layer attack distribution** graph of the [**Security & Attacks**](https://radar.cloudflare.com/security-and-attacks) Radar page these trends are calculated by number of bytes instead. Since attacks may vary greatly in number of bytes from one another, this could lead to trends differing between the quarterly reports and the graph displayed in Cloudflare Radar.
 
----
+***
 
 ## Final remarks
 
diff --git a/src/content/docs/randomness-beacon/about/background.mdx b/src/content/docs/randomness-beacon/about/background.mdx
index 3985a768398b9d4..34ad6ab86602697 100644
--- a/src/content/docs/randomness-beacon/about/background.mdx
+++ b/src/content/docs/randomness-beacon/about/background.mdx
@@ -11,7 +11,7 @@ products:
 description: History and development of the drand project.
 ---
 
-Over the years, a generation of public randomness (often referred to as _common coins_) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
+Over the years, a generation of public randomness (often referred to as *common coins*) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
 
 Realizing this, [Ewa Syta](http://ewa.syta.us/) started a project on [Scalable Bias-Resistant Distributed Randomness](https://eprint.iacr.org/2016/1067) during her PhD studies under the supervision of [Michael J. Fischer](http://www.cs.yale.edu/homes/fischer/) and [Bryan Ford](https://bford.info/) at Yale University. After Bryan moved to EPFL in 2015, the new members of the DEDIS team at EPFL ([Nicolas Gailly](https://github.com/nikkolasg/), [Linus Gasser](https://people.epfl.ch/linus.gasser), [Philipp Jovanovic](https://jovanovic.io/), [Ismail Khoffi](https://ismailkhoffi.com/), [Eleftherios Kokoris Kogias](https://lefteriskk.github.io/)) joined the project and together published a research paper at the [2017 IEEE Symposium on Security and Privacy](https://ieeexplore.ieee.org/abstract/document/7958592).
 
diff --git a/src/content/docs/randomness-beacon/about/future.mdx b/src/content/docs/randomness-beacon/about/future.mdx
index 76c17926bf29159..486975f9356ffc8 100644
--- a/src/content/docs/randomness-beacon/about/future.mdx
+++ b/src/content/docs/randomness-beacon/about/future.mdx
@@ -15,10 +15,10 @@ As of spring 2020, the drand network is production-ready and can now be consider
 
 While the project has reached a mature state, we believe there are several ways for drand to continue to evolve.
 
-- We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
+* We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
 
-- We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
+* We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
 
-- We would like to consider standardization of the core drand protocol.
+* We would like to consider standardization of the core drand protocol.
 
 We are proud to be a part of these efforts and hope to see even more adoption of drand in third-party applications and systems.
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
index 0678464a6ad4525..59049a2b40a28d4 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
@@ -12,11 +12,11 @@ drand is an efficient randomness beacon daemon that utilizes pairing-based crypt
 
 This is an overview of the cryptographic building blocks drand uses to generate publicly-verifiable, unbiasable, and unpredictable randomness in a distributed manner.
 
-The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are _n_ participants, out of which at most _f\<n_ are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of _t-f+1_ nodes work together to successfully execute cryptographic operations.
+The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are *n* participants, out of which at most *f\<n* are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of *t-f+1* nodes work together to successfully execute cryptographic operations.
 
-Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where _t-of-n_ participants are required to sign a transaction using a threshold signature scheme.
+Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where *t-of-n* participants are required to sign a transaction using a threshold signature scheme.
 
 :::note[Note]
 
-This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts.
+This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts. 
 :::
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
index c39777be50f168c..b3c4780456fd4fd 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
@@ -16,11 +16,11 @@ First, we explain pairing-based cryptography (PBC), which has become quite popul
 
 Pairing-based cryptography is based on bilinear groups `(𝔾1,𝔾2,𝔾𝑡)`, where `𝔾1`, `𝔾2`, and `𝔾𝑡` are cyclic groups of prime order `𝑝` with generators `𝑔1`, `𝑔2`, and `𝑔𝑡`, respectively, and a pairing operation `𝑒:𝔾1×𝔾2→𝔾𝑡` with these properties:
 
-- **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
+* **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
 
-- **Non-degeneracy:** `𝑒≠1`
+* **Non-degeneracy:** `𝑒≠1`
 
-- **Computability:** There exists an efficient algorithm to compute `𝑒`.
+* **Computability:** There exists an efficient algorithm to compute `𝑒`.
   drand currently uses the Barreto-Lynn-Scott curve BLS12-381.
 
 ## BLS Signatures
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
index 27152a46a610de6..1931a7beb984bc1 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
@@ -8,7 +8,7 @@ products:
 description: Learn about the distributed key generation phase.
 ---
 
-In the drand setup phase, you create a collective private and public key pair shared among _𝑛_ participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
+In the drand setup phase, you create a collective private and public key pair shared among *𝑛* participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
 
 A DKG is performed in a fully distributed manner, avoiding any single points of failure. This is an overview of the different sub-components of the drand DKG implementation.
 
@@ -36,7 +36,7 @@ Note that you can use any subset of `𝑡-of-𝑛` shares to perform Lagrange in
 
 SSS scheme assumes that the dealer is honest, but this may not always hold in practice. A Verifiable Secret Sharing (VSS) scheme protects against malicious dealers by enabling participants to verify that their shares are consistent with those dealt to other nodes, ensuring that the shared secret can be correctly reconstructed later.
 
-drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A _cyclic group_ means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
+drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A *cyclic group* means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
 
 ### Share Distribution
 
diff --git a/src/content/docs/realtime/agents/index.mdx b/src/content/docs/realtime/agents/index.mdx
index 841ef041c51d3c4..251f1183eda51db 100644
--- a/src/content/docs/realtime/agents/index.mdx
+++ b/src/content/docs/realtime/agents/index.mdx
@@ -10,6 +10,6 @@ products:
   - realtime
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing/>
diff --git a/src/content/docs/realtime/realtimekit/ai/index.mdx b/src/content/docs/realtime/realtimekit/ai/index.mdx
index 0b4b56d2c3a2e40..69baea7896467dd 100644
--- a/src/content/docs/realtime/realtimekit/ai/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/index.mdx
@@ -17,7 +17,7 @@ RealtimeKit provides AI-powered features using Cloudflare's AI infrastructure to
 ## Available features
 
 | Feature                                                  | Description                                 |
-| -------------------------------------------------------- | ------------------------------------------- |
+| -------------------------------------------------------- | -----------------------------------------   |
 | [Transcription](/realtime/realtimekit/ai/transcription/) | Real-time and end-of-meeting speech-to-text |
 | [Summary](/realtime/realtimekit/ai/summary/)             | AI-generated meeting summaries              |
 
diff --git a/src/content/docs/realtime/realtimekit/ai/summary.mdx b/src/content/docs/realtime/realtimekit/ai/summary.mdx
index f541baa92f1c99c..47577ad2f26f95d 100644
--- a/src/content/docs/realtime/realtimekit/ai/summary.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/summary.mdx
@@ -20,44 +20,44 @@ Set `summarize_on_end: true` when [creating a meeting](/realtime/realtimekit/con
 
 ```json
 {
-	"title": "Product Review",
-	"ai_config": {
-		"transcription": {
-			"language": "en-US"
-		},
-		"summarization": {
-			"word_limit": 500,
-			"text_format": "markdown",
-			"summary_type": "team_meeting"
-		}
-	},
-	"summarize_on_end": true
+  "title": "Product Review",
+  "ai_config": {
+    "transcription": {
+      "language": "en-US"
+    },
+    "summarization": {
+      "word_limit": 500,
+      "text_format": "markdown",
+      "summary_type": "team_meeting"
+    }
+  },
+  "summarize_on_end": true
 }
 ```
 
 ## Configuration
 
-| Option         | Type   | Default      | Description                               |
-| -------------- | ------ | ------------ | ----------------------------------------- |
-| `word_limit`   | number | 300          | Summary length (150-1000 words)           |
-| `text_format`  | string | `plain_text` | Output format: `plain_text` or `markdown` |
-| `summary_type` | string | `general`    | Meeting context for tailored summaries    |
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `word_limit` | number | 300 | Summary length (150-1000 words) |
+| `text_format` | string | `plain_text` | Output format: `plain_text` or `markdown` |
+| `summary_type` | string | `general` | Meeting context for tailored summaries |
 
 ### Summary types
 
 Choose a type that matches your meeting for better results:
 
-| Type                 | Best for                     |
-| -------------------- | ---------------------------- |
-| `general`            | Any meeting (default)        |
-| `team_meeting`       | Regular team syncs           |
-| `daily_standup`      | Agile standups               |
-| `one_on_one_meeting` | 1:1 meetings                 |
-| `sales_call`         | Customer sales conversations |
-| `client_check_in`    | Client status updates        |
-| `interview`          | Job interviews               |
-| `lecture`            | Educational content          |
-| `code_review`        | Technical code reviews       |
+| Type | Best for |
+|------|----------|
+| `general` | Any meeting (default) |
+| `team_meeting` | Regular team syncs |
+| `daily_standup` | Agile standups |
+| `one_on_one_meeting` | 1:1 meetings |
+| `sales_call` | Customer sales conversations |
+| `client_check_in` | Client status updates |
+| `interview` | Job interviews |
+| `lecture` | Educational content |
+| `code_review` | Technical code reviews |
 
 ## Consume summaries
 
@@ -67,11 +67,11 @@ Configure `meeting.summary` event in [webhooks](/api/resources/realtime_kit/subr
 
 ```json
 {
-	"event": "meeting.summary",
-	"meetingId": "meeting-123",
-	"sessionId": "session-456",
-	"summaryDownloadUrl": "https://...",
-	"summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
+  "event": "meeting.summary",
+  "meetingId": "meeting-123",
+  "sessionId": "session-456",
+  "summaryDownloadUrl": "https://...",
+  "summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
 }
 ```
 
@@ -103,19 +103,16 @@ With `text_format: "markdown"` and `summary_type: "team_meeting"`:
 ## Meeting Summary
 
 ### Key Discussion Points
-
 - Reviewed Q4 roadmap priorities
 - Discussed deployment timeline for v2.0
 - Identified blockers for the auth migration
 
 ### Action Items
-
 - @alice: Update design specs by Friday
 - @bob: Schedule security review
 - @charlie: Create migration runbook
 
 ### Decisions Made
-
 - Approved moving forward with Kubernetes migration
 - Delayed analytics dashboard to next sprint
 ```
diff --git a/src/content/docs/realtime/realtimekit/ai/transcription.mdx b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
index 0c3a1720bf0478a..fbedd591aeb9eb5 100644
--- a/src/content/docs/realtime/realtimekit/ai/transcription.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 RealtimeKit provides two transcription modes powered by Cloudflare Workers AI:
 
 | Mode               | Model                                                                | Use Case                       |
-| ------------------ | -------------------------------------------------------------------- | ------------------------------ |
+| ----------------   | -------------------------------------------------------------------- | ------------------------------ |
 | **Real-time**      | [Deepgram Nova-3](/workers-ai/models/nova-3/)                        | Live captions during meeting   |
 | **End-of-meeting** | [Whisper Large v3 Turbo](/workers-ai/models/whisper-large-v3-turbo/) | Accurate offline transcription |
 
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
index f4de77a1ba6d15d..bfe857bd9ca8b92 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
@@ -12,50 +12,48 @@ This module consists of the `ai` object which is used to interface with product'
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
 
-- [RTKAi](#module_RTKAi)
-  - _instance_
-    - [.telemetry](#module_RTKAi+telemetry)
-    - [.onTranscript(transcript)](#module_RTKAi+onTranscript)
-  - _static_
-    - [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
-    - [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
+
+* [RTKAi](#module_RTKAi)
+    * _instance_
+        * [.telemetry](#module_RTKAi+telemetry)
+        * [.onTranscript(transcript)](#module_RTKAi+onTranscript)
+    * _static_
+        * [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
+        * [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
 
 <a name="module_RTKAi+telemetry"></a>
 
 ### meeting.ai.telemetry
-
 **Kind**: instance property of [<code>RTKAi</code>](#module_RTKAi)  
 <a name="module_RTKAi+onTranscript"></a>
 
 ### meeting.ai.onTranscript(transcript)
+**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)  
 
-**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)
-
-| Param      | Type                           | Description                                 |
-| ---------- | ------------------------------ | ------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | transcript | <code>TranscriptionData</code> | Transcript data received for a participant. |
 
 <a name="module_RTKAi.parseTranscript"></a>
 
 ### meeting.ai.parseTranscript(transcriptData, [isPartialTranscript])
-
 Parse a single line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param                 | Type                 | Default            | Description                       |
-| --------------------- | -------------------- | ------------------ | --------------------------------- |
-| transcriptData        | <code>string</code>  |                    | The transcript data to parse      |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| transcriptData | <code>string</code> |  | The transcript data to parse |
 | [isPartialTranscript] | <code>boolean</code> | <code>false</code> | Whether the transcript is partial |
 
 <a name="module_RTKAi.parseTranscripts"></a>
 
 ### meeting.ai.parseTranscripts(transcriptData)
-
 Parse a multi-line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param          | Type                | Description                  |
-| -------------- | ------------------- | ---------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | transcriptData | <code>string</code> | The transcript data to parse |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
index c5262c512d5524e..f0dc2d5d09f31ea 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
@@ -10,367 +10,340 @@ web_core_version: 1.2.4
 
 This is the chat module, which can be used to send and receive messages from the meeting.
 
-- [RTKChat](#module_RTKChat)
-  - [module.exports](#exp_module_RTKChat--module.exports) ⏏
-    - [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
-    - ~~[.messages](#module_RTKChat--module.exports+messages)~~
-    - [.telemetry](#module_RTKChat--module.exports+telemetry)
-    - [.pinned](#module_RTKChat--module.exports+pinned)
-    - [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
-    - [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
-    - [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
-    - [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
-    - [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
-    - [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
-    - [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
-    - [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
-    - [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
-    - [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
-    - [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
-    - [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
-    - [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
-    - [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
-    - [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
-    - [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
-    - ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
-    - ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
-    - [.pin(id)](#module_RTKChat--module.exports+pin)
-    - [.unpin(id)](#module_RTKChat--module.exports+unpin)
-    - [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
-    - [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
-    - [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
-    - ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
-    - ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
+
+* [RTKChat](#module_RTKChat)
+    * [module.exports](#exp_module_RTKChat--module.exports) ⏏
+        * [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
+        * ~~[.messages](#module_RTKChat--module.exports+messages)~~
+        * [.telemetry](#module_RTKChat--module.exports+telemetry)
+        * [.pinned](#module_RTKChat--module.exports+pinned)
+        * [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
+        * [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
+        * [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
+        * [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
+        * [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
+        * [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
+        * [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
+        * [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
+        * [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
+        * [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
+        * [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
+        * [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
+        * [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
+        * [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
+        * [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
+        * [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
+        * ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
+        * ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
+        * [.pin(id)](#module_RTKChat--module.exports+pin)
+        * [.unpin(id)](#module_RTKChat--module.exports+unpin)
+        * [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
+        * [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
+        * [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
+        * ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
+        * ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
 
 <a name="exp_module_RTKChat--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKChat--module.exports_new"></a>
 
 #### new module.exports(context, chatSocketHandler, self, participants)
 
-| Param             | Type                              |
-| ----------------- | --------------------------------- |
-| context           | <code>Context</code>              |
-| chatSocketHandler | <code>RTKChatSocketHandler</code> |
-| self              | <code>Self</code>                 |
-| participants      | <code>Participants</code>         |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| chatSocketHandler | <code>RTKChatSocketHandler</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
 
 <a name="module_RTKChat--module.exports+messages"></a>
 
 #### ~~module.exports.messages~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+pinned"></a>
 
 #### module.exports.pinned
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 **Deprecated.**: This property is deprecated. Please use `fetchPinnedMessages()` instead.
 Returns an array of pinned messages.  
 <a name="module_RTKChat--module.exports+setMaxTextLimit"></a>
 
 #### module.exports.setMaxTextLimit(limit)
-
 Set the max character limit of a text message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                             |
-| ----- | ------------------- | --------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | limit | <code>number</code> | Max character limit for a text message. |
 
 <a name="module_RTKChat--module.exports+sendMessageInternal"></a>
 
 #### module.exports.sendMessageInternal(message, [participantIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param            | Type                              | Description                             |
-| ---------------- | --------------------------------- | --------------------------------------- |
-| message          | <code>MessagePayload</code>       | Message payload to send.                |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>MessagePayload</code> | Message payload to send. |
 | [participantIds] | <code>Array.&lt;string&gt;</code> | Participant ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendTextMessageInternal"></a>
 
 #### module.exports.sendTextMessageInternal(message, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                              | Description                      |
-| --------- | --------------------------------- | -------------------------------- |
-| message   | <code>string</code>               | Text message to send.            |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>string</code> | Text message to send. |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessageInternal"></a>
 
 #### module.exports.sendImageMessageInternal(image, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send.              |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessageInternal"></a>
 
 #### module.exports.sendFileMessageInternal(file, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | File to send.                    |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | File to send. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKChat--module.exports+sendTextMessage"></a>
 
 #### module.exports.sendTextMessage(message, [peerIds])
-
 Sends a chat text message to the room.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                              | Description                                |
-| --------- | --------------------------------- | ------------------------------------------ |
-| message   | <code>string</code>               | The message that must be sent to the room. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to.           |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>string</code> | The message that must be sent to the room. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendCustomMessage"></a>
 
 #### module.exports.sendCustomMessage(message, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                              | Description                      |
-| --------- | --------------------------------- | -------------------------------- |
-| message   | <code>CustomMessagePayload</code> | Custom message payload.          |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>CustomMessagePayload</code> | Custom message payload. |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessage"></a>
 
 #### module.exports.sendImageMessage(image, [peerIds])
-
 Sends an image message to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent.    |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessage"></a>
 
 #### module.exports.sendFileMessage(file, [peerIds])
-
 Sends a file to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | A File object.                   |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | A File object. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendMessage"></a>
 
 #### module.exports.sendMessage(message, [participantIds])
-
 Sends a message to the meeting. This method can be used to send text, image,
 or file messages. The message type is determined by the key 'type' in `message`
 object.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param            | Type                              | Description                                              |
-| ---------------- | --------------------------------- | -------------------------------------------------------- |
-| message          | <code>MessagePayload</code>       | An object including the type and content of the message. |
-| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants.      |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>MessagePayload</code> | An object including the type and content of the message. |
+| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants. |
 
 <a name="module_RTKChat--module.exports+editTextMessage"></a>
 
 #### module.exports.editTextMessage(messageId, message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                | Description                |
-| --------- | ------------------- | -------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | messageId | <code>string</code> | Id of the message to edit. |
-| message   | <code>string</code> | Updated text message.      |
+| message | <code>string</code> | Updated text message. |
 
 <a name="module_RTKChat--module.exports+editImageMessage"></a>
 
 #### module.exports.editImageMessage(messageId, image)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                |
-| --------- | ------------------------------------------------- | -------------------------- |
-| messageId | <code>string</code>                               | Id of the message to edit. |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file.        |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file. |
 
 <a name="module_RTKChat--module.exports+editFileMessage"></a>
 
 #### module.exports.editFileMessage(messageId, file)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                |
-| --------- | ------------------------------------------------- | -------------------------- |
-| messageId | <code>string</code>                               | Id of the message to edit. |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | Updated file.              |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | Updated file. |
 
 <a name="module_RTKChat--module.exports+editMessage"></a>
 
 #### module.exports.editMessage(messageId, message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                        | Description                |
-| --------- | --------------------------- | -------------------------- |
-| messageId | <code>string</code>         | Id of the message to edit. |
-| message   | <code>MessagePayload</code> | Updated message payload.   |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| message | <code>MessagePayload</code> | Updated message payload. |
 
 <a name="module_RTKChat--module.exports+deleteMessage"></a>
 
 #### module.exports.deleteMessage(messageId)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                | Description                  |
-| --------- | ------------------- | ---------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | messageId | <code>string</code> | Id of the message to delete. |
 
 <a name="module_RTKChat--module.exports+getMessagesByUser"></a>
 
 #### ~~module.exports.getMessagesByUser(userId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param  | Type                | Description                                    |
-| ------ | ------------------- | ---------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | userId | <code>string</code> | The user id of the user that sent the message. |
 
 <a name="module_RTKChat--module.exports+getMessagesByType"></a>
 
 #### ~~module.exports.getMessagesByType(type)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                                                                                                                                                                 | Description                                   |
-| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
-| type  | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
+| Param | Type | Description |
+| --- | --- | --- |
+| type | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
 
 <a name="module_RTKChat--module.exports+pin"></a>
 
 #### module.exports.pin(id)
-
 Pins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                    |
-| ----- | ------------------- | ------------------------------ |
-| id    | <code>string</code> | ID of the message to be pinned |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | ID of the message to be pinned |
 
 <a name="module_RTKChat--module.exports+unpin"></a>
 
 #### module.exports.unpin(id)
-
 Unpins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                      |
-| ----- | ------------------- | -------------------------------- |
-| id    | <code>string</code> | ID of the message to be unpinned |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | ID of the message to be unpinned |
 
 <a name="module_RTKChat--module.exports+fetchPublicMessages"></a>
 
 #### module.exports.fetchPublicMessages(options)
-
 Fetches messages from the chat with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                             | Description                                                                                            |
-| ------- | -------------------------------- | ------------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching messages, including timestamp, limit, and direction for pagination. |
 
 <a name="module_RTKChat--module.exports+fetchPrivateMessages"></a>
 
 #### module.exports.fetchPrivateMessages(options)
-
 Fetches private messages between the current user and another participant with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                                     | Description                                                                                                                             |
-| ------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchPrivateMessagesOptions</code> | Configuration options for fetching private messages, including private RTKChat ID (User ID of the participant) and pagination settings. |
 
 <a name="module_RTKChat--module.exports+fetchPinnedMessages"></a>
 
 #### module.exports.fetchPinnedMessages(options)
-
 Fetches pinned messages with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                             | Description                                                                                    |
-| ------- | -------------------------------- | ---------------------------------------------------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching pinned messages, including timestamp, limit, and direction. |
 
 <a name="module_RTKChat--module.exports+getMessages"></a>
 
 #### ~~module.exports.getMessages(timeStamp, size, reversed, [offset])~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                 | Default        |
-| --------- | -------------------- | -------------- |
-| timeStamp | <code>number</code>  |                |
-| size      | <code>number</code>  |                |
-| reversed  | <code>boolean</code> |                |
-| [offset]  | <code>number</code>  | <code>0</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| timeStamp | <code>number</code> |  | 
+| size | <code>number</code> |  | 
+| reversed | <code>boolean</code> |  | 
+| [offset] | <code>number</code> | <code>0</code> | 
 
 <a name="module_RTKChat--module.exports+searchMessages"></a>
 
 #### ~~module.exports.searchMessages(query, [filters])~~
+***Deprecated***
 
-**_Deprecated_**
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+| Param | Type |
+| --- | --- |
+| query | <code>string</code> | 
+| [filters] | <code>SearchFilters</code> | 
 
-| Param     | Type                       |
-| --------- | -------------------------- |
-| query     | <code>string</code>        |
-| [filters] | <code>SearchFilters</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
index 05ce7315d3a789b..4f7519ff80810fe 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
@@ -10,96 +10,91 @@ web_core_version: 1.2.4
 
 This consists of the methods to facilitate connected meetings
 
-- [RTKConnectedMeetings](#module_RTKConnectedMeetings)
-  - [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
-    - [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
-    - [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
-    - [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
-    - [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
-    - [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
-    - [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
-    - [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
+
+* [RTKConnectedMeetings](#module_RTKConnectedMeetings)
+    * [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
+        * [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
+        * [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
+        * [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
+        * [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
+        * [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
+        * [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
+        * [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
 
 <a name="exp_module_RTKConnectedMeetings--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKConnectedMeetings--module.exports_new"></a>
 
 #### new module.exports(context)
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings"></a>
 
 #### module.exports.getRTKConnectedMeetings()
-
 get connected meeting state
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 <a name="module_RTKConnectedMeetings--module.exports+createMeetings"></a>
 
 #### module.exports.createMeetings(request)
-
 create connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param   | Type                                       |
-| ------- | ------------------------------------------ |
-| request | <code>Array.&lt;{title: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| request | <code>Array.&lt;{title: string}&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+updateMeetings"></a>
 
 #### module.exports.updateMeetings(request)
-
 update meeting title
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param   | Type                                                   |
-| ------- | ------------------------------------------------------ |
-| request | <code>Array.&lt;{id: string, title: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| request | <code>Array.&lt;{id: string, title: string}&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+deleteMeetings"></a>
 
 #### module.exports.deleteMeetings(meetingIds)
-
 delete connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param      | Type                              |
-| ---------- | --------------------------------- |
-| meetingIds | <code>Array.&lt;string&gt;</code> |
+| Param | Type |
+| --- | --- |
+| meetingIds | <code>Array.&lt;string&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipants"></a>
 
 #### module.exports.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)
-
 Trigger event to move participants
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param                | Type                              | Description                    |
-| -------------------- | --------------------------------- | ------------------------------ |
-| sourceMeetingId      | <code>string</code>               | id of source meeting           |
-| destinationMeetingId | <code>string</code>               | id of destination meeting      |
-| participantIds       | <code>Array.&lt;string&gt;</code> | list of id of the participants |
+| Param | Type | Description |
+| --- | --- | --- |
+| sourceMeetingId | <code>string</code> | id of source meeting |
+| destinationMeetingId | <code>string</code> | id of destination meeting |
+| participantIds | <code>Array.&lt;string&gt;</code> | list of id of the participants |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset"></a>
 
 #### module.exports.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)
-
 Trigger event to move participants with custom preset
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+
+| Param | Type | Description |
+| --- | --- | --- |
+| sourceMeetingId | <code>string</code> | id of source meeting |
+| destinationMeetingId | <code>string</code> | id of destination meeting |
+| participants | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |  |
 
-| Param                | Type                                                      | Description               |
-| -------------------- | --------------------------------------------------------- | ------------------------- |
-| sourceMeetingId      | <code>string</code>                                       | id of source meeting      |
-| destinationMeetingId | <code>string</code>                                       | id of destination meeting |
-| participants         | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |                           |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
index 2706403d75acd35..4d2d4d56bab5c91 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
@@ -11,59 +11,55 @@ web_core_version: 1.2.4
 The RTKLivestream module represents the state of the current livestream, and allows
 to start/stop live streams.
 
-- [RTKLivestream](#module_RTKLivestream)
-  - [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
-    - [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
-    - [.telemetry](#module_RTKLivestream--module.exports+telemetry)
-    - [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
-    - [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
-    - [.stop()](#module_RTKLivestream--module.exports+stop)
+
+* [RTKLivestream](#module_RTKLivestream)
+    * [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
+        * [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
+        * [.telemetry](#module_RTKLivestream--module.exports+telemetry)
+        * [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
+        * [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
+        * [.stop()](#module_RTKLivestream--module.exports+stop)
 
 <a name="exp_module_RTKLivestream--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKLivestream--module.exports_new"></a>
 
 #### new module.exports(context, self)
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
-| self    | <code>Self</code>    |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
 
 <a name="module_RTKLivestream--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 <a name="module_RTKLivestream--module.exports+setRTKLivestreamState"></a>
 
 #### module.exports.setRTKLivestreamState(livestreamState)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
-
-| Param           | Type                            |
-| --------------- | ------------------------------- |
-| livestreamState | <code>RTKLivestreamState</code> |
+| Param | Type |
+| --- | --- |
+| livestreamState | <code>RTKLivestreamState</code> | 
 
 <a name="module_RTKLivestream--module.exports+start"></a>
 
 #### module.exports.start([livestreamConfig])
-
 Starts livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-| Param              | Type                                  |
-| ------------------ | ------------------------------------- |
-| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> |
+| Param | Type |
+| --- | --- |
+| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> | 
 
 <a name="module_RTKLivestream--module.exports+stop"></a>
 
 #### module.exports.stop()
-
 Stops livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
index 9752ca8616beba0..8a3447521dfd9b2 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
@@ -10,54 +10,51 @@ web_core_version: 1.2.4
 
 This consists of the metadata of the meeting, such as the room name and the title.
 
-- [RTKMeta](#module_RTKMeta)
-  - [module.exports](#exp_module_RTKMeta--module.exports) ⏏
-    - [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
-    - [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
-    - [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
-    - [.viewType](#module_RTKMeta--module.exports+viewType)
-    - [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
-    - [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
-    - [.sessionId](#module_RTKMeta--module.exports+sessionId)
-    - [.meetingId](#module_RTKMeta--module.exports+meetingId)
-    - [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
-    - [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
+
+* [RTKMeta](#module_RTKMeta)
+    * [module.exports](#exp_module_RTKMeta--module.exports) ⏏
+        * [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
+        * [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
+        * [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
+        * [.viewType](#module_RTKMeta--module.exports+viewType)
+        * [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
+        * [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
+        * [.sessionId](#module_RTKMeta--module.exports+sessionId)
+        * [.meetingId](#module_RTKMeta--module.exports+meetingId)
+        * [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
+        * [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
 
 <a name="exp_module_RTKMeta--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKMeta--module.exports_new"></a>
 
 #### new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)
 
-| Param             | Type                           |
-| ----------------- | ------------------------------ |
-| context           | <code>Context</code>           |
-| self              | <code>Self</code>              |
-| viewType          | <code>string</code>            |
-| roomSocketHandler | <code>RoomSocketHandler</code> |
-| meetingTitle      | <code>string</code>            |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| viewType | <code>string</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| meetingTitle | <code>string</code> | 
 
 <a name="module_RTKMeta--module.exports+selfActiveTab"></a>
 
 #### module.exports.selfActiveTab
-
 Represents the current active tab
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+broadcastTabChanges"></a>
 
 #### module.exports.broadcastTabChanges
-
 Represents whether current user is spotlighted
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+viewType"></a>
 
 #### module.exports.viewType
-
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -65,52 +62,47 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKMeta--module.exports+meetingStartedTimestamp"></a>
 
 #### module.exports.meetingStartedTimestamp
-
 The timestamp of the time when the meeting started.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingTitle"></a>
 
 #### module.exports.meetingTitle
-
 The title of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+sessionId"></a>
 
 #### module.exports.sessionId
-
 (Experimental) The sessionId this meeting object is part of.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingId"></a>
 
 #### module.exports.meetingId
-
 The room name of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+setBroadcastTabChanges"></a>
 
 #### module.exports.setBroadcastTabChanges(broadcastTabChanges)
-
 Sets current user as broadcasting tab changes
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 
-| Param               | Type                 |
-| ------------------- | -------------------- |
-| broadcastTabChanges | <code>boolean</code> |
+| Param | Type |
+| --- | --- |
+| broadcastTabChanges | <code>boolean</code> | 
 
 <a name="module_RTKMeta--module.exports+setSelfActiveTab"></a>
 
 #### module.exports.setSelfActiveTab(spotlightTab, tabChangeSource)
-
 Sets current active tab for user
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| spotlightTab | <code>ActiveTab</code> | 
+| tabChangeSource | <code>TabChangeSource</code> | 
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| spotlightTab    | <code>ActiveTab</code>       |
-| tabChangeSource | <code>TabChangeSource</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
index 12a5b874df4f649..5ab88c872e965cd 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
@@ -11,72 +11,68 @@ web_core_version: 1.2.4
 This module represents a single participant in the meeting.
 The participant object can be accessed from one of the participant lists
 present in the `meeting.participants` object. For example,
-
 ```ts
 const participant1 = meeting.participants.active.get(participantId);
 const participant2 = meeting.participants.joined.get(participantId);
 const participant3 = meeting.participants.active.toArray()[0];
-const participant4 = meeting.participants.active
-	.toArray()
-	.filter((p) => p.name === "John");
+const participant4 = meeting.participants.active.toArray().filter((p) => p.name === 'John');
 ```
 
-- [RTKParticipant](#module_RTKParticipant)
-  - [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
-    - [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
-    - [.id](#module_RTKParticipant--module.exports+id)
-    - [.userId](#module_RTKParticipant--module.exports+userId)
-    - [.name](#module_RTKParticipant--module.exports+name)
-    - [.picture](#module_RTKParticipant--module.exports+picture)
-    - [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
-    - ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
-    - [.device](#module_RTKParticipant--module.exports+device)
-    - [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
-    - [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
-    - [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
-    - [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
-    - [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
-    - [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
-    - [.producers](#module_RTKParticipant--module.exports+producers)
-    - [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
-    - [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
-    - [.presetName](#module_RTKParticipant--module.exports+presetName)
-    - [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
-    - [.telemetry](#module_RTKParticipant--module.exports+telemetry)
-    - [.isPinned](#module_RTKParticipant--module.exports+isPinned)
-    - [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
-    - [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
-    - [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
-    - [.pin()](#module_RTKParticipant--module.exports+pin)
-    - [.unpin()](#module_RTKParticipant--module.exports+unpin)
-    - [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
-    - [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
-    - [.kick()](#module_RTKParticipant--module.exports+kick)
-    - [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
-    - [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
-    - [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
-    - [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
+
+* [RTKParticipant](#module_RTKParticipant)
+    * [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
+        * [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
+        * [.id](#module_RTKParticipant--module.exports+id)
+        * [.userId](#module_RTKParticipant--module.exports+userId)
+        * [.name](#module_RTKParticipant--module.exports+name)
+        * [.picture](#module_RTKParticipant--module.exports+picture)
+        * [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
+        * ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
+        * [.device](#module_RTKParticipant--module.exports+device)
+        * [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
+        * [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
+        * [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
+        * [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
+        * [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
+        * [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
+        * [.producers](#module_RTKParticipant--module.exports+producers)
+        * [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
+        * [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
+        * [.presetName](#module_RTKParticipant--module.exports+presetName)
+        * [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
+        * [.telemetry](#module_RTKParticipant--module.exports+telemetry)
+        * [.isPinned](#module_RTKParticipant--module.exports+isPinned)
+        * [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
+        * [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
+        * [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
+        * [.pin()](#module_RTKParticipant--module.exports+pin)
+        * [.unpin()](#module_RTKParticipant--module.exports+unpin)
+        * [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
+        * [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
+        * [.kick()](#module_RTKParticipant--module.exports+kick)
+        * [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
+        * [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
+        * [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
+        * [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
 
 <a name="exp_module_RTKParticipant--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipant--module.exports_new"></a>
 
 #### new module.exports(context, participant, self, roomSocket)
 
-| Param       | Type                           |
-| ----------- | ------------------------------ |
-| context     | <code>Context</code>           |
-| participant | <code>IRTKParticipant</code>   |
-| self        | <code>Self</code>              |
-| roomSocket  | <code>RoomSocketHandler</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| participant | <code>IRTKParticipant</code> | 
+| self | <code>Self</code> | 
+| roomSocket | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKParticipant--module.exports+id"></a>
 
 #### module.exports.id
-
 The peer ID of the participant.
 The participants are indexed by this ID in the participant map.
 
@@ -84,171 +80,148 @@ The participants are indexed by this ID in the participant map.
 <a name="module_RTKParticipant--module.exports+userId"></a>
 
 #### module.exports.userId
-
 The user ID of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+name"></a>
 
 #### module.exports.name
-
 The name of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+picture"></a>
 
 #### module.exports.picture
-
 The picture of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+customRTKParticipantId"></a>
 
 #### module.exports.customRTKParticipantId
-
 The custom id of the participant set during Add RTKParticipant REST API
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+clientSpecificId"></a>
 
 #### ~~module.exports.clientSpecificId~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+device"></a>
 
 #### module.exports.device
-
 The device configuration of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoTrack"></a>
 
 #### module.exports.videoTrack
-
 The participant's video track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioTrack"></a>
 
 #### module.exports.audioTrack
-
 The participant's audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareTracks"></a>
 
 #### module.exports.screenShareTracks
-
 The participant's screenshare video and audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoEnabled"></a>
 
 #### module.exports.videoEnabled
-
 This is true if the participant's video is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioEnabled"></a>
 
 #### module.exports.audioEnabled
-
 This is true if the participant's audio is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareEnabled"></a>
 
 #### module.exports.screenShareEnabled
-
 This is true if the participant is screensharing.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+producers"></a>
 
 #### module.exports.producers
-
 producers created by participant
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+manualProducerConfig"></a>
 
 #### module.exports.manualProducerConfig
-
 producer config passed during manual subscription
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+supportsRemoteControl"></a>
 
 #### module.exports.supportsRemoteControl
-
 This is true if the participant supports remote control.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+presetName"></a>
 
 #### module.exports.presetName
-
 The preset of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+stageStatus"></a>
 
 #### module.exports.stageStatus
-
 Denotes the participants's current stage status.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+isPinned"></a>
 
 #### module.exports.isPinned
-
 Returns true if the participant is pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+setVideoEnabled"></a>
 
 #### module.exports.setVideoEnabled(videoEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param        | Type                 | Default           |
-| ------------ | -------------------- | ----------------- |
-| videoEnabled | <code>boolean</code> |                   |
-| [emitEvent]  | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| videoEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+setAudioEnabled"></a>
 
 #### module.exports.setAudioEnabled(audioEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param        | Type                 | Default           |
-| ------------ | -------------------- | ----------------- |
-| audioEnabled | <code>boolean</code> |                   |
-| [emitEvent]  | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| audioEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+setScreenShareEnabled"></a>
 
 #### module.exports.setScreenShareEnabled(screenShareEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param              | Type                 | Default           |
-| ------------------ | -------------------- | ----------------- |
-| screenShareEnabled | <code>boolean</code> |                   |
-| [emitEvent]        | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| screenShareEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+pin"></a>
 
 #### module.exports.pin()
-
 Returns `participant.id` if user has permission
 to pin participants.
 
@@ -256,7 +229,6 @@ to pin participants.
 <a name="module_RTKParticipant--module.exports+unpin"></a>
 
 #### module.exports.unpin()
-
 Returns `participant.id` if user has permission
 to unpin participants.
 
@@ -264,18 +236,16 @@ to unpin participants.
 <a name="module_RTKParticipant--module.exports+setIsPinned"></a>
 
 #### module.exports.setIsPinned(isPinned, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param       | Type                 | Default           |
-| ----------- | -------------------- | ----------------- |
-| isPinned    | <code>boolean</code> |                   |
-| [emitEvent] | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| isPinned | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+disableAudio"></a>
 
 #### module.exports.disableAudio()
-
 Disables audio for this participant.
 Requires the permission to disable participant audio.
 
@@ -283,7 +253,6 @@ Requires the permission to disable participant audio.
 <a name="module_RTKParticipant--module.exports+kick"></a>
 
 #### module.exports.kick()
-
 Kicks this participant from the meeting.
 Requires the permission to kick a participant.
 
@@ -291,7 +260,6 @@ Requires the permission to kick a participant.
 <a name="module_RTKParticipant--module.exports+disableVideo"></a>
 
 #### module.exports.disableVideo()
-
 Disables video for this participant.
 Requires the permission to disable video for a participant.
 
@@ -299,31 +267,29 @@ Requires the permission to disable video for a participant.
 <a name="module_RTKParticipant--module.exports+registerVideoElement"></a>
 
 #### module.exports.registerVideoElement(videoElem)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param     | Type                          |
-| --------- | ----------------------------- |
-| videoElem | <code>HTMLVideoElement</code> |
+| Param | Type |
+| --- | --- |
+| videoElem | <code>HTMLVideoElement</code> | 
 
 <a name="module_RTKParticipant--module.exports+deregisterVideoElement"></a>
 
 #### module.exports.deregisterVideoElement([videoElem])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param       | Type                          |
-| ----------- | ----------------------------- |
-| [videoElem] | <code>HTMLVideoElement</code> |
+| Param | Type |
+| --- | --- |
+| [videoElem] | <code>HTMLVideoElement</code> | 
 
 <a name="module_RTKParticipant--module.exports+updateVideo"></a>
 
 #### module.exports.updateVideo(e)
-
 Internal method, do not use
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| e | <code>HTMLVideoElement</code> | 
 
-| Param | Type                          |
-| ----- | ----------------------------- |
-| e     | <code>HTMLVideoElement</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
index c894fa0a1e8958c..f10720836d026ca 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
@@ -14,57 +14,55 @@ For example, when a participant is added to this map, a `participantJoined` even
 emitted from the map. When a participant object emits an event `videoUpdate`, the map
 re-emits that event (provided the participant is present in the map).
 
-- [RTKParticipantMap](#module_RTKParticipantMap)
-  - [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
-    - [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
-    - [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
-    - [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
-    - [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
+
+* [RTKParticipantMap](#module_RTKParticipantMap)
+    * [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
+        * [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
+        * [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
+        * [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
+        * [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
 
 <a name="exp_module_RTKParticipantMap--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipantMap--module.exports_new"></a>
 
 #### new module.exports(logger, [options])
 
-| Param     | Type                   |
-| --------- | ---------------------- |
-| logger    | <code>Logger</code>    |
-| [options] | <code>MapEvents</code> |
+| Param | Type |
+| --- | --- |
+| logger | <code>Logger</code> | 
+| [options] | <code>MapEvents</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+add"></a>
 
 #### module.exports.add(participant, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
-
-| Param       | Type                 | Default           |
-| ----------- | -------------------- | ----------------- |
-| participant | <code>T</code>       |                   |
-| [emitEvent] | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| participant | <code>T</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+clear"></a>
 
 #### module.exports.clear([emitEvent], [removeListeners])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
-
-| Param             | Type                 | Default            |
-| ----------------- | -------------------- | ------------------ |
-| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
-| [removeListeners] | <code>boolean</code> | <code>false</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+| [removeListeners] | <code>boolean</code> | <code>false</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+delete"></a>
 
 #### module.exports.delete(participantId, [emitEvent], [removeListeners])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+| Param | Type | Default |
+| --- | --- | --- |
+| participantId | <code>string</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+| [removeListeners] | <code>boolean</code> | <code>false</code> | 
 
-| Param             | Type                 | Default            |
-| ----------------- | -------------------- | ------------------ |
-| participantId     | <code>string</code>  |                    |
-| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
-| [removeListeners] | <code>boolean</code> | <code>false</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
index 85f7c46ef94b31e..6cc9cfa343f6be8 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
@@ -10,114 +10,106 @@ web_core_version: 1.2.4
 
 This module represents all the participants in the meeting (except the local user).
 It consists of 4 maps:
-
 - `joined`: A map of all participants that have joined the meeting.
 - `waitlisted`: A map of all participants that have been added to the waitlist.
 - `active`: A map of active participants who should be displayed in the meeting grid.
 - `pinned`: A map of pinned participants.
 
+
 * [RTKParticipants](#module_RTKParticipants)
-  - [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
-    - [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
-    - [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
-    - [.joined](#module_RTKParticipants--module.exports+joined)
-    - ~~[.active](#module_RTKParticipants--module.exports+active)~~
-    - [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
-    - [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
-    - [.pinned](#module_RTKParticipants--module.exports+pinned)
-    - [.all](#module_RTKParticipants--module.exports+all)
-    - [.pip](#module_RTKParticipants--module.exports+pip)
-    - [.telemetry](#module_RTKParticipants--module.exports+telemetry)
-    - [.viewMode](#module_RTKParticipants--module.exports+viewMode)
-    - [.currentPage](#module_RTKParticipants--module.exports+currentPage)
-    - [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
-    - [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
-    - [.count](#module_RTKParticipants--module.exports+count)
-    - [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
-    - [.pageCount](#module_RTKParticipants--module.exports+pageCount)
-    - [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
-    - [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
-    - [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
-    - [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
-    - [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
-    - [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
-    - [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
-    - [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
-    - [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
-    - [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
-    - ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
-    - ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
-    - ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
-    - [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
-    - [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
-    - [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
-    - [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
+    * [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
+        * [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
+        * [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
+        * [.joined](#module_RTKParticipants--module.exports+joined)
+        * ~~[.active](#module_RTKParticipants--module.exports+active)~~
+        * [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
+        * [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
+        * [.pinned](#module_RTKParticipants--module.exports+pinned)
+        * [.all](#module_RTKParticipants--module.exports+all)
+        * [.pip](#module_RTKParticipants--module.exports+pip)
+        * [.telemetry](#module_RTKParticipants--module.exports+telemetry)
+        * [.viewMode](#module_RTKParticipants--module.exports+viewMode)
+        * [.currentPage](#module_RTKParticipants--module.exports+currentPage)
+        * [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
+        * [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
+        * [.count](#module_RTKParticipants--module.exports+count)
+        * [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
+        * [.pageCount](#module_RTKParticipants--module.exports+pageCount)
+        * [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
+        * [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
+        * [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
+        * [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
+        * [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
+        * [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
+        * [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
+        * [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
+        * [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
+        * [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
+        * ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
+        * ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
+        * ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
+        * [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
+        * [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
+        * [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
+        * [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
 
 <a name="exp_module_RTKParticipants--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipants--module.exports_new"></a>
 
 #### new module.exports(context, self, roomSocketHandler)
-
 This constructs a new Participant object and maintains
 the maps of active/joined/waitlisted/pinned/selectedPeers maps.
 self : Self
 
-| Param             | Type                           |
-| ----------------- | ------------------------------ |
-| context           | <code>Context</code>           |
-| self              | <code>Self</code>              |
-| roomSocketHandler | <code>RoomSocketHandler</code> |
+
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKParticipants--module.exports+waitlisted"></a>
 
 #### module.exports.waitlisted
-
 Returns a list of participants waiting to join the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+joined"></a>
 
 #### module.exports.joined
-
 Returns a list of all participants in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+active"></a>
 
 #### ~~module.exports.active~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+videoSubscribed"></a>
 
 #### module.exports.videoSubscribed
-
 Returns a list of participants whose video streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+audioSubscribed"></a>
 
 #### module.exports.audioSubscribed
-
 Returns a list of participants whose audio streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+pinned"></a>
 
 #### module.exports.pinned
-
 Returns a list of participants who have been pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+all"></a>
 
 #### module.exports.all
-
 Returns all added participants irrespective of whether they are currently
 in the meeting or not
 
@@ -125,19 +117,16 @@ in the meeting or not
 <a name="module_RTKParticipants--module.exports+pip"></a>
 
 #### module.exports.pip
-
 Return the controls for Picture-in-Picture
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+viewMode"></a>
 
 #### module.exports.viewMode
-
 Indicates whether the meeting is in 'ACTIVE_GRID' mode or 'PAGINATED' mode.
 
 In 'ACTIVE_GRID' mode, participants are populated in the participants.active map
@@ -152,7 +141,6 @@ changed by the user using setPage(page).
 <a name="module_RTKParticipants--module.exports+currentPage"></a>
 
 #### module.exports.currentPage
-
 This indicates the current page that has been set by the user in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -160,28 +148,24 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+lastActiveSpeaker"></a>
 
 #### module.exports.lastActiveSpeaker
-
 This stores the `participantId` of the last participant who spoke in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+selectedPeers"></a>
 
 #### module.exports.selectedPeers
-
 Keeps a list of all participants who have been present in the selected peers list.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+count"></a>
 
 #### module.exports.count
-
 Returns the number of participants who are joined in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount"></a>
 
 #### module.exports.maxActiveRTKParticipantsCount
-
 Returns the maximum number of participants that can be present in
 the active map.
 
@@ -189,7 +173,6 @@ the active map.
 <a name="module_RTKParticipants--module.exports+pageCount"></a>
 
 #### module.exports.pageCount
-
 Returns the number of pages that are available in the meeting in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -197,204 +180,187 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount"></a>
 
 #### module.exports.setMaxActiveRTKParticipantsCount(limit)
-
 Updates the maximum number of participants that are populated in
 the active map.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description       |
-| ----- | ------------------- | ----------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | limit | <code>number</code> | Updated max limit |
 
 <a name="module_RTKParticipants--module.exports+acceptWaitingRoomRequest"></a>
 
 #### module.exports.acceptWaitingRoomRequest(id)
-
 Accepts requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                                     |
-| ----- | ------------------- | ----------------------------------------------- |
-| id    | <code>string</code> | peerId or userId of the waitlisted participant. |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | peerId or userId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest"></a>
 
 #### module.exports.acceptAllWaitingRoomRequest(userIds)
-
 We need a new event for socket service events
 since if we send them all together, sequence of events
 can be unreliable
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param   | Type                              |
-| ------- | --------------------------------- |
-| userIds | <code>Array.&lt;string&gt;</code> |
+| Param | Type |
+| --- | --- |
+| userIds | <code>Array.&lt;string&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+rejectWaitingRoomRequest"></a>
 
 #### module.exports.rejectWaitingRoomRequest(id)
-
 Rejects requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                                  |
-| ----- | ------------------- | -------------------------------------------- |
-| id    | <code>string</code> | participantId of the waitlisted participant. |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | participantId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+setViewMode"></a>
 
 #### module.exports.setViewMode(viewMode)
-
 Sets the view mode of the meeting to either ACTIVE_GRID or PAGINATED.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param    | Type                  | Description                                          |
-| -------- | --------------------- | ---------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | viewMode | <code>ViewMode</code> | The mode in which the active map should be populated |
 
 <a name="module_RTKParticipants--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(peerIds, [kinds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
-
-| Param   | Type                                                                                                                          |
-| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
+| Param | Type |
+| --- | --- |
+| peerIds | <code>Array.&lt;string&gt;</code> | 
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(peerIds, [kinds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
-
-| Param   | Type                                                                                                                          |
-| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
+| Param | Type |
+| --- | --- |
+| peerIds | <code>Array.&lt;string&gt;</code> | 
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+setPage"></a>
 
 #### module.exports.setPage(page)
-
 Populates the active map with participants present in the page number
 indicated by the parameter `page` in PAGINATED mode.
 Does not do anything in ACTIVE_GRID mode.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                |
-| ----- | ------------------- | -------------------------- |
-| page  | <code>number</code> | The page number to be set. |
+| Param | Type | Description |
+| --- | --- | --- |
+| page | <code>number</code> | The page number to be set. |
 
 <a name="module_RTKParticipants--module.exports+disableAllAudio"></a>
 
 #### module.exports.disableAllAudio(allowUnmute)
-
 Disables audio for all participants in the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param       | Type                 | Description                                        |
-| ----------- | -------------------- | -------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | allowUnmute | <code>boolean</code> | Allow participants to unmute after they are muted. |
 
 <a name="module_RTKParticipants--module.exports+disableAllVideo"></a>
 
 #### module.exports.disableAllVideo()
-
 Disables video for all participants in the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+disableAudio"></a>
 
 #### ~~module.exports.disableAudio(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                    |
-| ------------- | ------------------- | ------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+disableVideo"></a>
 
 #### ~~module.exports.disableVideo(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                    |
-| ------------- | ------------------- | ------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+kick"></a>
 
 #### ~~module.exports.kick(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                     |
-| ------------- | ------------------- | ------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be kicked. |
 
 <a name="module_RTKParticipants--module.exports+kickAll"></a>
 
 #### module.exports.kickAll()
-
 Kicks all participants from the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+broadcastMessage"></a>
 
 #### module.exports.broadcastMessage(type, payload, target)
-
 Broadcasts the message to participants
 
 If no `target` is specified it is sent to all participants including `self`.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param   | Type                                 | Description                                                                                                                           |
-| ------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
-| type    | <code>string</code>                  |                                                                                                                                       |
-| payload | <code>BroadcastMessagePayload</code> |                                                                                                                                       |
-| target  | <code>BroadcastMessageTarget</code>  | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
+| Param | Type | Description |
+| --- | --- | --- |
+| type | <code>string</code> |  |
+| payload | <code>BroadcastMessagePayload</code> |  |
+| target | <code>BroadcastMessageTarget</code> | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
 
 <a name="module_RTKParticipants--module.exports+getAllJoinedPeers"></a>
 
 #### module.exports.getAllJoinedPeers(searchQuery, limit, offset)
-
 Returns all peers currently present in the room
 If you are in a group call, use `meeting.participants.joined`
 instead
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param       | Type                |
-| ----------- | ------------------- |
-| searchQuery | <code>string</code> |
-| limit       | <code>number</code> |
-| offset      | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| searchQuery | <code>string</code> | 
+| limit | <code>number</code> | 
+| offset | <code>number</code> | 
 
 <a name="module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin"></a>
 
 #### module.exports.getRTKParticipantsInMeetingPreJoin()
-
 Returns all peers currently in the room, is a non paginated call
 and should only be used if you are in a non room joined state,
 if in a joined group call, use `meeting.participants.joined`
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
index ac3f6c4b61d2b82..e8da972e0b7c931 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
@@ -10,52 +10,52 @@ web_core_version: 1.2.4
 
 The PermissionPreset class represents the meeting permissions for the current participant
 
-- [PermissionPreset](#module_PermissionPreset)
-  - _instance_
-    - [.stageEnabled](#module_PermissionPreset+stageEnabled)
-    - [.stageAccess](#module_PermissionPreset+stageAccess)
-    - [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
-    - [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
-    - [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
-    - [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
-    - [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
-    - [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
-    - [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
-    - [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
-    - [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
-    - [.kickParticipant](#module_PermissionPreset+kickParticipant)
-    - [.pinParticipant](#module_PermissionPreset+pinParticipant)
-    - [.canRecord](#module_PermissionPreset+canRecord)
-    - ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
-    - [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
-    - [.plugins](#module_PermissionPreset+plugins)
-    - [.polls](#module_PermissionPreset+polls)
-    - ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
-    - ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
-    - [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
-    - ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
-    - [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
-    - ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
-    - [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
-    - [.chatPublic](#module_PermissionPreset+chatPublic)
-    - [.chatPrivate](#module_PermissionPreset+chatPrivate)
-    - [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
-    - [.showParticipantList](#module_PermissionPreset+showParticipantList)
-    - ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
-    - [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
-    - ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
-    - ~~[.canPresent](#module_PermissionPreset+canPresent)~~
-    - ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
-    - ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
-    - [.canLivestream](#module_PermissionPreset+canLivestream)
-  - _static_
-    - [.fromResponse()](#module_PermissionPreset.fromResponse)
-    - [.default()](#module_PermissionPreset.default)
+
+* [PermissionPreset](#module_PermissionPreset)
+    * _instance_
+        * [.stageEnabled](#module_PermissionPreset+stageEnabled)
+        * [.stageAccess](#module_PermissionPreset+stageAccess)
+        * [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
+        * [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
+        * [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
+        * [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
+        * [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
+        * [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
+        * [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
+        * [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
+        * [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
+        * [.kickParticipant](#module_PermissionPreset+kickParticipant)
+        * [.pinParticipant](#module_PermissionPreset+pinParticipant)
+        * [.canRecord](#module_PermissionPreset+canRecord)
+        * ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
+        * [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
+        * [.plugins](#module_PermissionPreset+plugins)
+        * [.polls](#module_PermissionPreset+polls)
+        * ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
+        * ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
+        * [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
+        * ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
+        * [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
+        * ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
+        * [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
+        * [.chatPublic](#module_PermissionPreset+chatPublic)
+        * [.chatPrivate](#module_PermissionPreset+chatPrivate)
+        * [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
+        * [.showParticipantList](#module_PermissionPreset+showParticipantList)
+        * ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
+        * [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
+        * ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
+        * ~~[.canPresent](#module_PermissionPreset+canPresent)~~
+        * ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
+        * ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
+        * [.canLivestream](#module_PermissionPreset+canLivestream)
+    * _static_
+        * [.fromResponse()](#module_PermissionPreset.fromResponse)
+        * [.default()](#module_PermissionPreset.default)
 
 <a name="module_PermissionPreset+stageEnabled"></a>
 
 ### meeting.self.permissions.stageEnabled
-
 The `stageEnabled` property returns a boolean value.
 If `true`, stage management is available for the participant.
 
@@ -63,7 +63,6 @@ If `true`, stage management is available for the participant.
 <a name="module_PermissionPreset+stageAccess"></a>
 
 ### meeting.self.permissions.stageAccess
-
 The `stageAccess` property dictates how a user interacts with the stage.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 
@@ -71,7 +70,6 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 <a name="module_PermissionPreset+acceptWaitingRequests"></a>
 
 ### meeting.self.permissions.acceptWaitingRequests
-
 The `acceptWaitingRequests` returns boolean value.
 If `true`, participant can accept the request of waiting participant.
 
@@ -79,7 +77,6 @@ If `true`, participant can accept the request of waiting participant.
 <a name="module_PermissionPreset+requestProduceVideo"></a>
 
 ### meeting.self.permissions.requestProduceVideo
-
 The `requestProduceVideo` returns boolean value.
 If `true`, participant can send request to participants
 about producing video.
@@ -88,7 +85,6 @@ about producing video.
 <a name="module_PermissionPreset+requestProduceAudio"></a>
 
 ### meeting.self.permissions.requestProduceAudio
-
 The `requestProduceAudio` returns boolean value.
 If `true`, participant can send request to participants
 about producing audio.
@@ -97,7 +93,6 @@ about producing audio.
 <a name="module_PermissionPreset+requestProduceScreenshare"></a>
 
 ### meeting.self.permissions.requestProduceScreenshare
-
 The `requestProduceScreenshare` returns boolean value.
 If `true`, participant can send request to participants
 about sharing screen.
@@ -106,7 +101,6 @@ about sharing screen.
 <a name="module_PermissionPreset+canAllowParticipantAudio"></a>
 
 ### meeting.self.permissions.canAllowParticipantAudio
-
 The `canAllowParticipantAudio` returns boolean value.
 If `true`, participant can enable other participants` audio.
 
@@ -114,7 +108,6 @@ If `true`, participant can enable other participants` audio.
 <a name="module_PermissionPreset+canAllowParticipantScreensharing"></a>
 
 ### meeting.self.permissions.canAllowParticipantScreensharing
-
 The `canAllowParticipantScreensharing` returns boolean value.
 If `true`, participant can enable other participants` screen share.
 
@@ -122,7 +115,6 @@ If `true`, participant can enable other participants` screen share.
 <a name="module_PermissionPreset+canAllowParticipantVideo"></a>
 
 ### meeting.self.permissions.canAllowParticipantVideo
-
 The `canAllowParticipantVideo` returns boolean value.
 If `true`, participant can enable other participants` video.
 
@@ -130,21 +122,18 @@ If `true`, participant can enable other participants` video.
 <a name="module_PermissionPreset+canDisableParticipantAudio"></a>
 
 ### meeting.self.permissions.canDisableParticipantAudio
-
 If `true`, a participant can disable other participants` audio.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canDisableParticipantVideo"></a>
 
 ### meeting.self.permissions.canDisableParticipantVideo
-
 If `true`, a participant can disable other participants` video.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+kickParticipant"></a>
 
 ### meeting.self.permissions.kickParticipant
-
 The `kickParticipant` returns boolean value.
 If `true`, participant can remove other participants from the meeting.
 
@@ -152,7 +141,6 @@ If `true`, participant can remove other participants from the meeting.
 <a name="module_PermissionPreset+pinParticipant"></a>
 
 ### meeting.self.permissions.pinParticipant
-
 The `pinParticipant` returns boolean value.
 If `true`, participant can pin a participant in the meeting.
 
@@ -160,7 +148,6 @@ If `true`, participant can pin a participant in the meeting.
 <a name="module_PermissionPreset+canRecord"></a>
 
 ### meeting.self.permissions.canRecord
-
 The `canRecord` returns boolean value.
 If `true`, participant can record the meeting.
 
@@ -168,14 +155,12 @@ If `true`, participant can record the meeting.
 <a name="module_PermissionPreset+waitingRoomType"></a>
 
 ### ~~meeting.self.permissions.waitingRoomType~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+waitingRoomBehaviour"></a>
 
 ### meeting.self.permissions.waitingRoomBehaviour
-
 The `waitingRoomType` returns string value.
 type of waiting room behavior
 possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
@@ -184,7 +169,6 @@ possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
 <a name="module_PermissionPreset+plugins"></a>
 
 ### meeting.self.permissions.plugins
-
 The `plugins` tells if the participant can act on plugins
 there are 2 permissions with boolean values, `canStart` and `canClose`.
 
@@ -192,7 +176,6 @@ there are 2 permissions with boolean values, `canStart` and `canClose`.
 <a name="module_PermissionPreset+polls"></a>
 
 ### meeting.self.permissions.polls
-
 The `polls` tells if the participant can use polls.
 There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewResults`
 
@@ -200,21 +183,18 @@ There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewRes
 <a name="module_PermissionPreset+produceVideo"></a>
 
 ### ~~meeting.self.permissions.produceVideo~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+requestProduce"></a>
 
 ### ~~meeting.self.permissions.requestProduce~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceVideo"></a>
 
 ### meeting.self.permissions.canProduceVideo
-
 The `canProduceVideo` shows permissions for enabling video.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -222,14 +202,12 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceScreenshare"></a>
 
 ### ~~meeting.self.permissions.produceScreenshare~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceScreenshare"></a>
 
 ### meeting.self.permissions.canProduceScreenshare
-
 The `canProduceScreenshare` shows permissions for sharing screen.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -237,14 +215,12 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceAudio"></a>
 
 ### ~~meeting.self.permissions.produceAudio~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceAudio"></a>
 
 ### meeting.self.permissions.canProduceAudio
-
 The `canProduceAudio` shows permissions for enabling audio.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -252,7 +228,6 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+chatPublic"></a>
 
 ### meeting.self.permissions.chatPublic
-
 The `chatPublic` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send chat
@@ -263,7 +238,6 @@ there are 4 permissions
 <a name="module_PermissionPreset+chatPrivate"></a>
 
 ### meeting.self.permissions.chatPrivate
-
 The `chatPrivate` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send private chat
@@ -275,7 +249,6 @@ there are 4 permissions
 <a name="module_PermissionPreset+hiddenParticipant"></a>
 
 ### meeting.self.permissions.hiddenParticipant
-
 The `hiddenParticipant` returns boolean value.
 If `true`, participant is hidden.
 
@@ -283,7 +256,6 @@ If `true`, participant is hidden.
 <a name="module_PermissionPreset+showParticipantList"></a>
 
 ### meeting.self.permissions.showParticipantList
-
 The `showParticipantList` returns boolean value.
 If `true`, participant list can be shown to the participant.
 
@@ -291,14 +263,12 @@ If `true`, participant list can be shown to the participant.
 <a name="module_PermissionPreset+canChangeParticipantRole"></a>
 
 ### ~~meeting.self.permissions.canChangeParticipantRole~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canChangeParticipantPermissions"></a>
 
 ### meeting.self.permissions.canChangeParticipantPermissions
-
 The `canChangeParticipantPermissions` returns boolean value.
 If `true`, allow changing the participants' permissions.
 
@@ -306,47 +276,40 @@ If `true`, allow changing the participants' permissions.
 <a name="module_PermissionPreset+canChangeTheme"></a>
 
 ### ~~meeting.self.permissions.canChangeTheme~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canPresent"></a>
 
 ### ~~meeting.self.permissions.canPresent~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+acceptPresentRequests"></a>
 
 ### ~~meeting.self.permissions.acceptPresentRequests~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+maxScreenShareCount"></a>
 
 ### ~~meeting.self.permissions.maxScreenShareCount~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canLivestream"></a>
 
 ### meeting.self.permissions.canLivestream
-
 Livestream
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset.fromResponse"></a>
 
 ### meeting.self.permissions.fromResponse()
-
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 **Deprecated.**: Use init()  
 <a name="module_PermissionPreset.default"></a>
 
 ### meeting.self.permissions.default()
-
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
-**Deprecated.**: Use init()
+**Deprecated.**: Use init()  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
index 6cb2dd696a9ff5f..72747a12f6bdcac 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
@@ -46,76 +46,76 @@ Code from ui-kit. Same method used in the avatar component
 **Kind**: global function  
 <a name="_init"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
-| self    | <code>Self</code>    |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
 
 <a name="init"></a>
 
 Initialize PiP and prepare sources
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param            | Type                |
-| ---------------- | ------------------- |
-| [options]        | <code>Object</code> |
-| [options.height] | <code>number</code> |
-| [options.width]  | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| [options] | <code>Object</code> | 
+| [options.height] | <code>number</code> | 
+| [options.width] | <code>number</code> | 
 
 <a name="disableSource"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                |
-| ------ | ------------------- |
-| source | <code>string</code> |
+| Param | Type |
+| --- | --- |
+| source | <code>string</code> | 
 
 <a name="addSource"></a>
 
 Add a video source from the participant grid
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param         | Type                          | Description                            |
-| ------------- | ----------------------------- | -------------------------------------- |
-| id            | <code>string</code>           | id for the source (ex. participant id) |
-| element       | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source  |
-| enabled       | <code>boolean</code>          | if source is enabled                   |
-| [displayText] | <code>string</code>           | two character display text             |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | id for the source (ex. participant id) |
+| element | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source |
+| enabled | <code>boolean</code> | if source is enabled |
+| [displayText] | <code>string</code> | two character display text |
 
 <a name="updateSource"></a>
 
 Update a video source
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                |
-| ------ | ------------------- |
-| id     | <code>string</code> |
-| source | <code>any</code>    |
+| Param | Type |
+| --- | --- |
+| id | <code>string</code> | 
+| source | <code>any</code> | 
 
 <a name="removeSource"></a>
 
 Remove the video source for the participant
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param | Description                            |
-| ----- | -------------------------------------- |
-| id    | id for the source (ex. participant id) |
+| Param | Description |
+| --- | --- |
+| id | id for the source (ex. participant id) |
 
 <a name="removePinnedSource"></a>
 
 Remove the pinned source
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param | Description                            |
-| ----- | -------------------------------------- |
-| id    | id for the source (ex. participant id) |
+| Param | Description |
+| --- | --- |
+| id | id for the source (ex. participant id) |
 
 <a name="removeAllSources"></a>
 
@@ -126,4 +126,4 @@ Remove all sources
 
 Enable PiP
 
-**Kind**: global function
+**Kind**: global function  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
index 1dc5407b42362d4..68d9b48f76fb51b 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
@@ -11,159 +11,145 @@ web_core_version: 1.2.4
 The RTKPlugin module represents a single plugin in the meeting.
 A plugin can be obtained from one of the plugin arrays in `meeting.plugins`.
 For example,
-
 ```ts
 const plugin1 = meeting.plugins.active.get(pluginId);
 const plugin2 = meeting.plugins.all.get(pluginId);
 ```
 
-- [RTKPlugin](#module_RTKPlugin)
-  - [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
-    - [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
-    - [.telemetry](#module_RTKPlugin--module.exports+telemetry)
-    - [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
-    - [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
-    - [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
-    - [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
-    - [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
-    - [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
-    - [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
-    - [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
-    - ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
-    - ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
-    - [.activate()](#module_RTKPlugin--module.exports+activate)
-    - [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
+
+* [RTKPlugin](#module_RTKPlugin)
+    * [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
+        * [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
+        * [.telemetry](#module_RTKPlugin--module.exports+telemetry)
+        * [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
+        * [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
+        * [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
+        * [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
+        * [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
+        * [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
+        * [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
+        * [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
+        * ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
+        * ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
+        * [.activate()](#module_RTKPlugin--module.exports+activate)
+        * [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
 
 <a name="exp_module_RTKPlugin--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKPlugin--module.exports_new"></a>
 
 #### new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)
 
-| Param               | Type                                |
-| ------------------- | ----------------------------------- |
-| context             | <code>Context</code>                |
-| plugin              | <code>RTKPluginResponse</code>      |
-| pluginSocketHandler | <code>RTKPluginSocketHandler</code> |
-| self                | <code>Self</code>                   |
-| participants        | <code>Participants</code>           |
-| chat                | <code>Chat</code>                   |
-| meetingTitle        | <code>string</code>                 |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| plugin | <code>RTKPluginResponse</code> | 
+| pluginSocketHandler | <code>RTKPluginSocketHandler</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
+| chat | <code>Chat</code> | 
+| meetingTitle | <code>string</code> | 
 
 <a name="module_RTKPlugin--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+sendIframeEvent"></a>
 
 #### module.exports.sendIframeEvent(message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param   | Type                                | Description                              |
-| ------- | ----------------------------------- | ---------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | message | <code>RTKPluginIframeMessage</code> | Socket message forwarded to this plugin. |
 
 <a name="module_RTKPlugin--module.exports+handleIframeMessage"></a>
 
 #### module.exports.handleIframeMessage(iframeMessage)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param         | Type                                |
-| ------------- | ----------------------------------- |
-| iframeMessage | <code>RTKPluginIframeMessage</code> |
+| Param | Type |
+| --- | --- |
+| iframeMessage | <code>RTKPluginIframeMessage</code> | 
 
 <a name="module_RTKPlugin--module.exports+sendData"></a>
 
 #### module.exports.sendData(payload)
-
 This method is used to send arbitrary data to the plugin.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param             | Type                         | Description                                                            |
-| ----------------- | ---------------------------- | ---------------------------------------------------------------------- |
-| payload           | <code>SendDataOptions</code> | The payload that you want to send inside the plugin.                   |
-| payload.eventName | <code>string</code>          | Name of the event. This is used to listen for the event in plugin SDK. |
-| payload.data      | <code>any</code>             | Data you wish to emit. It can assume any data type.                    |
+| Param | Type | Description |
+| --- | --- | --- |
+| payload | <code>SendDataOptions</code> | The payload that you want to send inside the plugin. |
+| payload.eventName | <code>string</code> | Name of the event. This is used to listen for the event in plugin SDK. |
+| payload.data | <code>any</code> | Data you wish to emit. It can assume any data type. |
 
 <a name="module_RTKPlugin--module.exports+removeRTKPluginView"></a>
 
 #### module.exports.removeRTKPluginView(viewId)
-
 This method is used for cleaning up event listeners attached to an iframe. It must
 be used before the iframe is removed from the DOM.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param  | Type                | Default                          | Description                                                        |
-| ------ | ------------------- | -------------------------------- | ------------------------------------------------------------------ |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
 | viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+addRTKPluginView"></a>
 
 #### module.exports.addRTKPluginView(iframe, viewId)
-
 This method adds the communication layer between the plugin inside the iframe
 and the core application (meeting object) in the main window.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param  | Type                                                              | Default                          | Description                                                        |
-| ------ | ----------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------ |
-| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |                                  | Iframe element to display this plugin.                             |
-| viewId | <code>string</code>                                               | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |  | Iframe element to display this plugin. |
+| viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+setActive"></a>
 
 #### module.exports.setActive(active)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param  | Type                 |
-| ------ | -------------------- |
-| active | <code>boolean</code> |
+| Param | Type |
+| --- | --- |
+| active | <code>boolean</code> | 
 
 <a name="module_RTKPlugin--module.exports+activateForSelf"></a>
 
 #### module.exports.activateForSelf()
-
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivateForSelf"></a>
 
 #### module.exports.deactivateForSelf()
-
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+enable"></a>
 
 #### ~~module.exports.enable()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+disable"></a>
 
 #### ~~module.exports.disable()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+activate"></a>
 
 #### module.exports.activate()
-
 Activate this plugin for all participants.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivate"></a>
 
 #### module.exports.deactivate()
-
 Deactivate this plugin for all participants.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
index ff22e5a74589e76..8ea2b9486986701 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
@@ -9,40 +9,37 @@ web_core_version: 1.2.4
 <a name="module_RTKPlugins"></a>
 
 The RTKPlugins module consists of all the plugins in the meeting. It has 2 maps:
-
 - `all`: Consists of all the plugins in the meeting.
 - `active`: Consists of the plugins that are currently in use.
 
+
 * [RTKPlugins](#module_RTKPlugins)
-  - [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
-    - [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
-    - [.all](#module_RTKPlugins--module.exports+all)
-    - [.active](#module_RTKPlugins--module.exports+active)
+    * [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
+        * [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
+        * [.all](#module_RTKPlugins--module.exports+all)
+        * [.active](#module_RTKPlugins--module.exports+active)
 
 <a name="exp_module_RTKPlugins--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKPlugins--module.exports_new"></a>
 
 #### new module.exports(logger)
 
-| Param  | Type                |
-| ------ | ------------------- |
-| logger | <code>Logger</code> |
+| Param | Type |
+| --- | --- |
+| logger | <code>Logger</code> | 
 
 <a name="module_RTKPlugins--module.exports+all"></a>
 
 #### module.exports.all
-
 All plugins accessible by the current user.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
 <a name="module_RTKPlugins--module.exports+active"></a>
 
 #### module.exports.active
-
 All plugins that are currently enabled in the room.
 
-**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)
+**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
index 25d6abf2a17b0fe..95f20dbb49fe688 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
@@ -10,42 +10,41 @@ web_core_version: 1.2.4
 
 The RTKPolls module consists of the polls that have been created in the meeting.
 
-- [RTKPolls](#module_RTKPolls)
-  - [.items](#module_RTKPolls+items)
-  - [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
-  - [.vote(pollId, index)](#module_RTKPolls+vote)
+
+* [RTKPolls](#module_RTKPolls)
+    * [.items](#module_RTKPolls+items)
+    * [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
+    * [.vote(pollId, index)](#module_RTKPolls+vote)
 
 <a name="module_RTKPolls+items"></a>
 
 ### meeting.polls.items
-
 An array of poll items.
 
 **Kind**: instance property of [<code>RTKPolls</code>](#module_RTKPolls)  
 <a name="module_RTKPolls+create"></a>
 
 ### meeting.polls.create(question, options, anonymous, hideVotes)
-
 Creates a poll in the meeting.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
 
-| Param     | Default            | Description                                |
-| --------- | ------------------ | ------------------------------------------ |
-| question  |                    | The question that is to be voted for.      |
-| options   |                    | The options of the poll.                   |
-| anonymous | <code>false</code> | If true, the poll votes are anonymous.     |
+| Param | Default | Description |
+| --- | --- | --- |
+| question |  | The question that is to be voted for. |
+| options |  | The options of the poll. |
+| anonymous | <code>false</code> | If true, the poll votes are anonymous. |
 | hideVotes | <code>false</code> | If true, the votes on the poll are hidden. |
 
 <a name="module_RTKPolls+vote"></a>
 
 ### meeting.polls.vote(pollId, index)
-
 Casts a vote on an existing poll.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
 
-| Param  | Description                                |
-| ------ | ------------------------------------------ |
+| Param | Description |
+| --- | --- |
 | pollId | The ID of the poll that is to be voted on. |
-| index  | The index of the option.                   |
+| index | The index of the option. |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
index e63b1525fae136c..4b2dd3b6116b3dd 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
@@ -11,43 +11,39 @@ web_core_version: 1.2.4
 The RTKRecording module represents the state of the current recording, and allows
 to start/stop recordings and check if there's a recording in progress.
 
-- [RTKRecording](#module_RTKRecording)
-  - [.telemetry](#module_RTKRecording+telemetry)
-  - [.start()](#module_RTKRecording+start)
-  - [.stop()](#module_RTKRecording+stop)
-  - [.pause()](#module_RTKRecording+pause)
-  - [.resume()](#module_RTKRecording+resume)
+
+* [RTKRecording](#module_RTKRecording)
+    * [.telemetry](#module_RTKRecording+telemetry)
+    * [.start()](#module_RTKRecording+start)
+    * [.stop()](#module_RTKRecording+stop)
+    * [.pause()](#module_RTKRecording+pause)
+    * [.resume()](#module_RTKRecording+resume)
 
 <a name="module_RTKRecording+telemetry"></a>
 
 ### meeting.recording.telemetry
-
 **Kind**: instance property of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+start"></a>
 
 ### meeting.recording.start()
-
 Starts recording the meeting.
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+stop"></a>
 
 ### meeting.recording.stop()
-
 Stops all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+pause"></a>
 
 ### meeting.recording.pause()
-
 Pauses all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+resume"></a>
 
 ### meeting.recording.resume()
-
 Resumes all recording currently in 'PAUSED' state
 
-**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)
+**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
index 1ad8cd81f058059..aa4a71840eac6b8 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
@@ -12,43 +12,42 @@ The RTKSelf module represents the current user, and allows to modify the state
 of the user in the meeting. The audio and video streams of the user can be retrieved from
 this module.
 
-- [RTKSelf](#module_RTKSelf)
-  - [.telemetry](#module_RTKSelf+telemetry)
-  - [.peerId](#module_RTKSelf+peerId)
-  - [.roomState](#module_RTKSelf+roomState)
-  - [.permissions](#module_RTKSelf+permissions)
-  - [.config](#module_RTKSelf+config)
-  - [.roomJoined](#module_RTKSelf+roomJoined)
-  - [.isPinned](#module_RTKSelf+isPinned)
-  - [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
-  - [.setName(name)](#module_RTKSelf+setName)
-  - [.setupTracks(options)](#module_RTKSelf+setupTracks)
-  - [.enableAudio()](#module_RTKSelf+enableAudio)
-  - [.enableVideo()](#module_RTKSelf+enableVideo)
-  - [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
-  - [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
-  - [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
-  - [.disableAudio()](#module_RTKSelf+disableAudio)
-  - [.disableVideo()](#module_RTKSelf+disableVideo)
-  - [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
-  - [.getAllDevices()](#module_RTKSelf+getAllDevices)
-  - [.setIsPinned()](#module_RTKSelf+setIsPinned)
-  - [.pin()](#module_RTKSelf+pin)
-  - [.unpin()](#module_RTKSelf+unpin)
-  - [.hide()](#module_RTKSelf+hide)
-  - [.show()](#module_RTKSelf+show)
-  - [.setDevice(device)](#module_RTKSelf+setDevice)
-  - [.updateVideo()](#module_RTKSelf+updateVideo)
+
+* [RTKSelf](#module_RTKSelf)
+    * [.telemetry](#module_RTKSelf+telemetry)
+    * [.peerId](#module_RTKSelf+peerId)
+    * [.roomState](#module_RTKSelf+roomState)
+    * [.permissions](#module_RTKSelf+permissions)
+    * [.config](#module_RTKSelf+config)
+    * [.roomJoined](#module_RTKSelf+roomJoined)
+    * [.isPinned](#module_RTKSelf+isPinned)
+    * [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
+    * [.setName(name)](#module_RTKSelf+setName)
+    * [.setupTracks(options)](#module_RTKSelf+setupTracks)
+    * [.enableAudio()](#module_RTKSelf+enableAudio)
+    * [.enableVideo()](#module_RTKSelf+enableVideo)
+    * [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
+    * [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
+    * [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
+    * [.disableAudio()](#module_RTKSelf+disableAudio)
+    * [.disableVideo()](#module_RTKSelf+disableVideo)
+    * [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
+    * [.getAllDevices()](#module_RTKSelf+getAllDevices)
+    * [.setIsPinned()](#module_RTKSelf+setIsPinned)
+    * [.pin()](#module_RTKSelf+pin)
+    * [.unpin()](#module_RTKSelf+unpin)
+    * [.hide()](#module_RTKSelf+hide)
+    * [.show()](#module_RTKSelf+show)
+    * [.setDevice(device)](#module_RTKSelf+setDevice)
+    * [.updateVideo()](#module_RTKSelf+updateVideo)
 
 <a name="module_RTKSelf+telemetry"></a>
 
 ### meeting.self.telemetry
-
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+peerId"></a>
 
 ### meeting.self.peerId
-
 NOTE(ishita1805): Discussed with Ravindra, added a duplicate for consistency
 when using identifiers in Locker.
 We might want to look at deprecating the `id` sometime later.
@@ -57,7 +56,6 @@ We might want to look at deprecating the `id` sometime later.
 <a name="module_RTKSelf+roomState"></a>
 
 ### meeting.self.roomState
-
 Returns the current state of room
 init - Initial State
 joined - User is in the meeting
@@ -71,76 +69,67 @@ ended - The meeting was ended
 <a name="module_RTKSelf+permissions"></a>
 
 ### meeting.self.permissions
-
 Returns the current permission given to the user for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+config"></a>
 
 ### meeting.self.config
-
 Returns configuration for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+roomJoined"></a>
 
 ### meeting.self.roomJoined
-
 Returns true if the local participant has joined the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+isPinned"></a>
 
 ### meeting.self.isPinned
-
 Returns true if the current user is pinned.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+cleanupEvents"></a>
 
 ### meeting.self.cleanupEvents()
-
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setName"></a>
 
 ### meeting.self.setName(name)
-
 The name of the user can be set by calling this method.
 This will get reflected to other participants ONLY if
 this method is called before the room is joined.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param | Type                | Description       |
-| ----- | ------------------- | ----------------- |
-| name  | <code>string</code> | Name of the user. |
+| Param | Type | Description |
+| --- | --- | --- |
+| name | <code>string</code> | Name of the user. |
 
 <a name="module_RTKSelf+setupTracks"></a>
 
 ### meeting.self.setupTracks(options)
-
 Sets up the local media tracks.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param                | Type                 | Description                                       |
-| -------------------- | -------------------- | ------------------------------------------------- |
-| options              | <code>Object</code>  | The audio and video options.                      |
-| [options.video]      | <code>boolean</code> | If true, the video stream is fetched.             |
-| [options.audio]      | <code>boolean</code> | If true, the audio stream is fetched.             |
+| Param | Type | Description |
+| --- | --- | --- |
+| options | <code>Object</code> | The audio and video options. |
+| [options.video] | <code>boolean</code> | If true, the video stream is fetched. |
+| [options.audio] | <code>boolean</code> | If true, the audio stream is fetched. |
 | [options.forceReset] | <code>boolean</code> | If true, force resets tracks before re-acquiring. |
 
 <a name="module_RTKSelf+enableAudio"></a>
 
 ### meeting.self.enableAudio()
-
 This method is used to unmute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+enableVideo"></a>
 
 ### meeting.self.enableVideo()
-
 This method is used to start streaming the local participant's video
 to the meeting.
 
@@ -148,7 +137,6 @@ to the meeting.
 <a name="module_RTKSelf+updateVideoConstraints"></a>
 
 ### meeting.self.updateVideoConstraints()
-
 This method is used to apply constraints to the current video
 stream.
 
@@ -156,7 +144,6 @@ stream.
 <a name="module_RTKSelf+enableScreenShare"></a>
 
 ### meeting.self.enableScreenShare()
-
 This method is used to start sharing the local participant's screen
 to the meeting.
 
@@ -164,7 +151,6 @@ to the meeting.
 <a name="module_RTKSelf+updateScreenshareConstraints"></a>
 
 ### meeting.self.updateScreenshareConstraints()
-
 This method is used to apply constraints to the current screenshare
 stream.
 
@@ -172,40 +158,34 @@ stream.
 <a name="module_RTKSelf+disableAudio"></a>
 
 ### meeting.self.disableAudio()
-
 This method is used to mute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableVideo"></a>
 
 ### meeting.self.disableVideo()
-
 This participant is used to disable the local participant's video.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableScreenShare"></a>
 
 ### meeting.self.disableScreenShare()
-
 This method is used to stop sharing the local participant's screen.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+getAllDevices"></a>
 
 ### meeting.self.getAllDevices()
-
 Returns all media devices accessible by the local participant.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setIsPinned"></a>
 
 ### meeting.self.setIsPinned()
-
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+pin"></a>
 
 ### meeting.self.pin()
-
 Returns `self.id` if user has permission
 to pin participants.
 
@@ -213,7 +193,6 @@ to pin participants.
 <a name="module_RTKSelf+unpin"></a>
 
 ### meeting.self.unpin()
-
 Returns `self.id` if user has permission
 to unpin participants.
 
@@ -221,33 +200,29 @@ to unpin participants.
 <a name="module_RTKSelf+hide"></a>
 
 ### meeting.self.hide()
-
 Hide's user's tile in the UI (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+show"></a>
 
 ### meeting.self.show()
-
 Show's user's tile in the UI if hidden (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setDevice"></a>
 
 ### meeting.self.setDevice(device)
-
 Change the current media device that is being used by the local participant.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param  | Type                         | Description                                                                                      |
-| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
 
 <a name="module_RTKSelf+updateVideo"></a>
 
 ### meeting.self.updateVideo()
-
 Internal method, do not use
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
index be8f537561e76eb..9e2d6335663b878 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
@@ -147,16 +147,16 @@ Returns true if screen share is enabled.
 **Kind**: global variable  
 <a name="init"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param                 | Type                          | Default            |
-| --------------------- | ----------------------------- | ------------------ |
-| options               | <code>Object</code>           |                    |
-| [options.video]       | <code>boolean</code>          |                    |
-| [options.audio]       | <code>boolean</code>          |                    |
-| [options.constraints] | <code>MediaConstraints</code> |                    |
-| [skipAwaits]          | <code>boolean</code>          | <code>false</code> |
-| [context]             | <code>Context</code>          | <code></code>      |
+| Param | Type | Default |
+| --- | --- | --- |
+| options | <code>Object</code> |  | 
+| [options.video] | <code>boolean</code> |  | 
+| [options.audio] | <code>boolean</code> |  | 
+| [options.constraints] | <code>MediaConstraints</code> |  | 
+| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
+| [context] | <code>Context</code> | <code></code> | 
 
 <a name="addAudioMiddleware"></a>
 
@@ -165,21 +165,21 @@ If there are more than 1 audio middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| audioMiddleware | <code>AudioMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| audioMiddleware | <code>AudioMiddleware</code> | 
 
 <a name="removeAudioMiddleware"></a>
 
 Removes the audio middleware, if it is there.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| audioMiddleware | <code>AudioMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| audioMiddleware | <code>AudioMiddleware</code> | 
 
 <a name="removeAllAudioMiddlewares"></a>
 
@@ -193,32 +193,32 @@ If there are more than 1 video middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| videoMiddleware | <code>VideoMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| videoMiddleware | <code>VideoMiddleware</code> | 
 
 <a name="setVideoMiddlewareGlobalConfig"></a>
 
 Sets global config to be used by video middlewares.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param                                 | Type                                     | Description                                                                                                                                                                                                                                                                                               |
-| ------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| config                                | <code>VideoMiddlewareGlobalConfig</code> | config                                                                                                                                                                                                                                                                                                    |
-| config.disablePerFrameCanvasRendering | <code>boolean</code>                     | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas, it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
+| Param | Type | Description |
+| --- | --- | --- |
+| config | <code>VideoMiddlewareGlobalConfig</code> | config |
+| config.disablePerFrameCanvasRendering | <code>boolean</code> | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas,  it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
 
 <a name="removeVideoMiddleware"></a>
 
 Removes the video middleware, if it is there.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| videoMiddleware | <code>VideoMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| videoMiddleware | <code>VideoMiddleware</code> | 
 
 <a name="removeAllVideoMiddlewares"></a>
 
@@ -249,19 +249,20 @@ Returns the local participant's speaker devices.
 
 Returns the local participant's device, indexed by ID and kind.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param    | Type                                                                                                 | Description                                       |
-| -------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| deviceId | <code>string</code>                                                                                  | The ID of the device.                             |
-| kind     | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
+| Param | Type | Description |
+| --- | --- | --- |
+| deviceId | <code>string</code> | The ID of the device. |
+| kind | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
 
 <a name="setDevice"></a>
 
 Change the current media device that is being used by the local participant.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                         | Description                                                                                      |
-| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
index 35bd0dcc153011f..787b7778e4ea72e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
@@ -13,76 +13,70 @@ RTKStage refers to a virtual area, where participants stream are visible to othe
 When a participant is off stage, they are not producing media
 but only consuming media from participants who are on RTKStage
 
-- [RTKStage](#module_RTKStage)
-  - [module.exports](#exp_module_RTKStage--module.exports) ⏏
-    - [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
-    - [.telemetry](#module_RTKStage--module.exports+telemetry)
-    - [.peerId](#module_RTKStage--module.exports+peerId)
-    - [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
-    - [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
-    - [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
-    - [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
-    - [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
-    - [.join()](#module_RTKStage--module.exports+join)
-    - [.leave()](#module_RTKStage--module.exports+leave)
-    - [.kick(userIds)](#module_RTKStage--module.exports+kick)
+
+* [RTKStage](#module_RTKStage)
+    * [module.exports](#exp_module_RTKStage--module.exports) ⏏
+        * [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
+        * [.telemetry](#module_RTKStage--module.exports+telemetry)
+        * [.peerId](#module_RTKStage--module.exports+peerId)
+        * [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
+        * [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
+        * [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
+        * [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
+        * [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
+        * [.join()](#module_RTKStage--module.exports+join)
+        * [.leave()](#module_RTKStage--module.exports+leave)
+        * [.kick(userIds)](#module_RTKStage--module.exports+kick)
 
 <a name="exp_module_RTKStage--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKStage--module.exports_new"></a>
 
 #### new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)
 
-| Param              | Type                               |
-| ------------------ | ---------------------------------- |
-| context            | <code>Context</code>               |
-| self               | <code>Self</code>                  |
-| participants       | <code>Participants</code>          |
-| stageSocketHandler | <code>RTKStageSocketHandler</code> |
-| roomSocketHandler  | <code>RoomSocketHandler</code>     |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
+| stageSocketHandler | <code>RTKStageSocketHandler</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKStage--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+peerId"></a>
 
 #### module.exports.peerId
-
 Returns the peerId of the current user
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+getAccessRequests"></a>
 
 #### module.exports.getAccessRequests()
-
 Method to fetch all RTKStage access requests from viewers
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+requestAccess"></a>
 
 #### module.exports.requestAccess()
-
 Method to send a request to privileged users to join the stage
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+cancelRequestAccess"></a>
 
 #### module.exports.cancelRequestAccess()
-
 Method to cancel a previous RTKStage join request
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+grantAccess"></a>
 
 #### module.exports.grantAccess()
-
 Method to grant access to RTKStage.
-This can be in response to a RTKStage Join request but it can be called on other users as well
+	This can be in response to a RTKStage Join request but it can be called on other users as well
 
 `permissions.acceptRTKStageRequests` privilege required
 
@@ -90,7 +84,6 @@ This can be in response to a RTKStage Join request but it can be called on other
 <a name="module_RTKStage--module.exports+denyAccess"></a>
 
 #### module.exports.denyAccess()
-
 Method to deny access to RTKStage.
 This should be called in response to a RTKStage Join request
 
@@ -98,7 +91,6 @@ This should be called in response to a RTKStage Join request
 <a name="module_RTKStage--module.exports+join"></a>
 
 #### module.exports.join()
-
 Method to join the stage
 Users either need to have the permission in the preset or must be accepted by a privileged
 user to call this method
@@ -107,7 +99,6 @@ user to call this method
 <a name="module_RTKStage--module.exports+leave"></a>
 
 #### module.exports.leave()
-
 Method to leave the stage
 Users must either be on the stage already or be accepted to join the stage
 to call this method
@@ -116,13 +107,13 @@ to call this method
 <a name="module_RTKStage--module.exports+kick"></a>
 
 #### module.exports.kick(userIds)
-
 Method to kick a user off the stage
 
 `permissions.acceptRTKStageRequests` privilege required
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| userIds | <code>Array.&lt;string&gt;</code> | 
 
-| Param   | Type                              |
-| ------- | --------------------------------- |
-| userIds | <code>Array.&lt;string&gt;</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
index 51d98a4f1ebc2ea..c27dd5a9443bf19 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
@@ -12,136 +12,127 @@ This module represents a single global store.
 The store can be accessed from the `meeting.stores` module.
 
 **Returns**: An instance of RTKStore.  
-**Example**
-
+**Example**  
 ```js
-const handRaiseRTKStore = meeting.stores.stores.get("handRaise");
+const handRaiseRTKStore = meeting.stores.stores.get('handRaise');
 ```
 
-- [RTKStore](#module_RTKStore) ⇒
-  - [module.exports](#exp_module_RTKStore--module.exports) ⏏
-    - [new module.exports(args)](#new_module_RTKStore--module.exports_new)
-    - [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
-    - [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
-    - [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
-    - [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
-    - [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
-    - [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
-    - [.populate(data)](#module_RTKStore--module.exports+populate)
+* [RTKStore](#module_RTKStore) ⇒
+    * [module.exports](#exp_module_RTKStore--module.exports) ⏏
+        * [new module.exports(args)](#new_module_RTKStore--module.exports_new)
+        * [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
+        * [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
+        * [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
+        * [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
+        * [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
+        * [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
+        * [.populate(data)](#module_RTKStore--module.exports+populate)
 
 <a name="exp_module_RTKStore--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKStore--module.exports_new"></a>
 
 #### new module.exports(args)
 
-| Param              | Type                             |
-| ------------------ | -------------------------------- |
-| args               | <code>Object</code>              |
-| args.name          | <code>string</code>              |
-| args.socketHandler | <code>PluginSocketHandler</code> |
-| args.meetingId     | <code>string</code>              |
+| Param | Type |
+| --- | --- |
+| args | <code>Object</code> | 
+| args.name | <code>string</code> | 
+| args.socketHandler | <code>PluginSocketHandler</code> | 
+| args.meetingId | <code>string</code> | 
 
 <a name="module_RTKStore--module.exports+set"></a>
 
 #### module.exports.set(key, value, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Sets a value in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default            | Description                             |
-| ------ | -------------------- | ------------------ | --------------------------------------- |
-| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
-| value  | <code>any</code>     |                    | Data to be set.                         |
-| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| value | <code>any</code> |  | Data to be set. |
+| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
 
 <a name="module_RTKStore--module.exports+bulkSet"></a>
 
 #### module.exports.bulkSet(data) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Sets multiple values in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param | Type                                                   |
-| ----- | ------------------------------------------------------ |
-| data  | <code>Array.&lt;{key: string, payload: any}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| data | <code>Array.&lt;{key: string, payload: any}&gt;</code> | 
 
 <a name="module_RTKStore--module.exports+update"></a>
 
 #### module.exports.update(key, value, [sync]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Updates an already existing value in the store.
 If the value stored is `['a', 'b']`, the operation
 `store.update(key, ['c'])` will modify
 the value to `['a','b','c']`.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default           | Description                             |
-| ------ | -------------------- | ----------------- | --------------------------------------- |
-| key    | <code>string</code>  |                   | Unique identifier used to store value.  |
-| value  | <code>any</code>     |                   | Data to be updated.                     |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| value | <code>any</code> |  | Data to be updated. |
 | [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
 
 <a name="module_RTKStore--module.exports+delete"></a>
 
 #### module.exports.delete(key, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Deletes a key value pair form the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default            | Description                             |
-| ------ | -------------------- | ------------------ | --------------------------------------- |
-| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
-| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
 
 <a name="module_RTKStore--module.exports+bulkDelete"></a>
 
 #### module.exports.bulkDelete(data) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Deletes multiple values from the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param | Type                                     |
-| ----- | ---------------------------------------- |
-| data  | <code>Array.&lt;{key: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| data | <code>Array.&lt;{key: string}&gt;</code> | 
 
 <a name="module_RTKStore--module.exports+get"></a>
 
 #### module.exports.get(key) ⇒ <code>any</code>
-
 Returns value for the given key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>any</code> - Value for the given key.
+**Returns**: <code>any</code> - Value for the given key.  
 
-| Param | Type                | Description                            |
-| ----- | ------------------- | -------------------------------------- |
-| key   | <code>string</code> | Unique identifier used to store value. |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
 
 <a name="module_RTKStore--module.exports+getAll"></a>
 
 #### module.exports.getAll() ⇒ <code>RTKStoreData</code>
-
 Returns the entire store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
@@ -149,59 +140,55 @@ Returns the entire store.
 <a name="module_RTKStore--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKStore--module.exports+updateBulkRateLimits"></a>
 
 #### module.exports.updateBulkRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKStore--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(key, cb) ⇒ <code>void</code>
-
 Listens for data change on a store key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void
+**Returns**: <code>void</code> - void  
 
-| Param | Type                  | Description                                                     |
-| ----- | --------------------- | --------------------------------------------------------------- |
-| key   | <code>string</code>   | Unique identifier used to store value.                          |
-| cb    | <code>function</code> | The callback function that gets executed when data is modified. |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
+| cb | <code>function</code> | The callback function that gets executed when data is modified. |
 
 <a name="module_RTKStore--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(key, [cb]) ⇒ <code>void</code>
-
 Removes all listeners for a key on the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void
+**Returns**: <code>void</code> - void  
 
-| Param | Type                  | Description                            |
-| ----- | --------------------- | -------------------------------------- |
-| key   | <code>string</code>   | Unique identifier used to store value. |
-| [cb]  | <code>function</code> | Callback to be removed.                |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
+| [cb] | <code>function</code> | Callback to be removed. |
 
 <a name="module_RTKStore--module.exports+populate"></a>
 
 #### module.exports.populate(data)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+| Param | Type |
+| --- | --- |
+| data | <code>RTKStoreData</code> | 
 
-| Param | Type                      |
-| ----- | ------------------------- |
-| data  | <code>RTKStoreData</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
index e5a1e74b8e69bcf..88539296c8905b0 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
@@ -10,78 +10,72 @@ web_core_version: 1.2.4
 
 The RTKThemePreset class represents the meeting theme for the current participant
 
-- [RTKThemePreset](#module_RTKThemePreset)
-  - [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
-    - [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
-    - _instance_
-      - ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
-      - ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
-      - ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
-      - ~~[.header](#module_RTKThemePreset--module.exports+header)~~
-      - ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
-      - [.viewType](#module_RTKThemePreset--module.exports+viewType)
-      - [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
-      - [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
-      - [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
-      - ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
-      - [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
-    - _static_
-      - [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
-      - [.default()](#module_RTKThemePreset--module.exports.default)
-      - [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
+
+* [RTKThemePreset](#module_RTKThemePreset)
+    * [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
+        * [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
+        * _instance_
+            * ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
+            * ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
+            * ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
+            * ~~[.header](#module_RTKThemePreset--module.exports+header)~~
+            * ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
+            * [.viewType](#module_RTKThemePreset--module.exports+viewType)
+            * [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
+            * [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
+            * [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
+            * ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
+            * [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
+        * _static_
+            * [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
+            * [.default()](#module_RTKThemePreset--module.exports.default)
+            * [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
 
 <a name="exp_module_RTKThemePreset--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKThemePreset--module.exports_new"></a>
 
 #### new module.exports(preset)
 
-| Param  | Type                            |
-| ------ | ------------------------------- |
-| preset | <code>PresetV2CamelCased</code> |
+| Param | Type |
+| --- | --- |
+| preset | <code>PresetV2CamelCased</code> | 
 
 <a name="module_RTKThemePreset--module.exports+setupScreen"></a>
 
 #### ~~module.exports.setupScreen~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+waitingRoom"></a>
 
 #### ~~module.exports.waitingRoom~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+controlBar"></a>
 
 #### ~~module.exports.controlBar~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+header"></a>
 
 #### ~~module.exports.header~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+pipMode"></a>
 
 #### ~~module.exports.pipMode~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+viewType"></a>
 
 #### module.exports.viewType
-
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -89,7 +83,6 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKThemePreset--module.exports+livestreamViewerQualities"></a>
 
 #### module.exports.livestreamViewerQualities
-
 The `livestreamViewerQualities` specifies the allowed qualities of a stream,
 that can be viewed by a livestream viewer
 
@@ -97,7 +90,6 @@ that can be viewed by a livestream viewer
 <a name="module_RTKThemePreset--module.exports+maxVideoStreams"></a>
 
 #### module.exports.maxVideoStreams
-
 The `maxVideoStreams` contains the maximum video
 streams for mobile and desktop
 
@@ -105,7 +97,6 @@ streams for mobile and desktop
 <a name="module_RTKThemePreset--module.exports+maxScreenShareCount"></a>
 
 #### module.exports.maxScreenShareCount
-
 The `maxScreenShareCount` contains the maximum
 possible concurrent screen shares
 
@@ -113,41 +104,37 @@ possible concurrent screen shares
 <a name="module_RTKThemePreset--module.exports+plugins"></a>
 
 #### ~~module.exports.plugins~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+disabledPlugins"></a>
 
 #### module.exports.disabledPlugins
-
 The `disabledPlugins` property returns id of all disabled plugins
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports.fromResponse"></a>
 
 #### module.exports.fromResponse(preset)
-
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
-**Deprecated.**: Use init()
+**Deprecated.**: Use init()  
 
-| Param  | Type                            |
-| ------ | ------------------------------- |
-| preset | <code>PresetV2CamelCased</code> |
+| Param | Type |
+| --- | --- |
+| preset | <code>PresetV2CamelCased</code> | 
 
 <a name="module_RTKThemePreset--module.exports.default"></a>
 
 #### module.exports.default()
-
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 **Deprecated.**: Use init()  
 <a name="module_RTKThemePreset--module.exports.init"></a>
 
 #### module.exports.init([preset], [useDefault])
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)
+| Param | Type | Default |
+| --- | --- | --- |
+| [preset] | <code>PresetV2CamelCased</code> |  | 
+| [useDefault] | <code>boolean</code> | <code>true</code> | 
 
-| Param        | Type                            | Default           |
-| ------------ | ------------------------------- | ----------------- |
-| [preset]     | <code>PresetV2CamelCased</code> |                   |
-| [useDefault] | <code>boolean</code>            | <code>true</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
index 31f2a68764c9ee9..1afafcb4fd4b751 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
@@ -13,46 +13,45 @@ An object of the RealtimeKitClient class can be created using
 `await RealtimeKitClient.init({ ... })`. Typically, an object of `RealtimeKitClient` is
 named `meeting`.
 
-- [RealtimeKitClient](#module_RealtimeKitClient)
-  - [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
-    - [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
-    - _instance_
-      - [.participants](#module_RealtimeKitClient--module.exports+participants)
-      - [.self](#module_RealtimeKitClient--module.exports+self)
-      - [.meta](#module_RealtimeKitClient--module.exports+meta)
-      - [.ai](#module_RealtimeKitClient--module.exports+ai)
-      - [.plugins](#module_RealtimeKitClient--module.exports+plugins)
-      - [.chat](#module_RealtimeKitClient--module.exports+chat)
-      - [.polls](#module_RealtimeKitClient--module.exports+polls)
-      - [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
-      - [.**internals**](#module_RealtimeKitClient--module.exports+__internals__)
-      - [.join()](#module_RealtimeKitClient--module.exports+join)
-      - [.leave()](#module_RealtimeKitClient--module.exports+leave)
-      - ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
-      - ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
-    - _static_
-      - [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
-      - [.init(options)](#module_RealtimeKitClient--module.exports.init)
-      - [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
+
+* [RealtimeKitClient](#module_RealtimeKitClient)
+    * [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
+        * [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
+        * _instance_
+            * [.participants](#module_RealtimeKitClient--module.exports+participants)
+            * [.self](#module_RealtimeKitClient--module.exports+self)
+            * [.meta](#module_RealtimeKitClient--module.exports+meta)
+            * [.ai](#module_RealtimeKitClient--module.exports+ai)
+            * [.plugins](#module_RealtimeKitClient--module.exports+plugins)
+            * [.chat](#module_RealtimeKitClient--module.exports+chat)
+            * [.polls](#module_RealtimeKitClient--module.exports+polls)
+            * [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
+            * [.__internals__](#module_RealtimeKitClient--module.exports+__internals__)
+            * [.join()](#module_RealtimeKitClient--module.exports+join)
+            * [.leave()](#module_RealtimeKitClient--module.exports+leave)
+            * ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
+            * ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
+        * _static_
+            * [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
+            * [.init(options)](#module_RealtimeKitClient--module.exports.init)
+            * [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
 
 <a name="exp_module_RealtimeKitClient--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RealtimeKitClient--module.exports_new"></a>
 
 #### new module.exports(context, controller)
 
-| Param      | Type                    |
-| ---------- | ----------------------- |
-| context    | <code>IContext</code>   |
-| controller | <code>Controller</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>IContext</code> | 
+| controller | <code>Controller</code> | 
 
 <a name="module_RealtimeKitClient--module.exports+participants"></a>
 
 #### module.exports.participants
-
 The `participants` object consists of 4 maps of participants,
 `waitlisted`, `joined`, `active`, `pinned`. The maps are indexed by
 `peerId`s, and the values are the corresponding participant objects.
@@ -61,7 +60,6 @@ The `participants` object consists of 4 maps of participants,
 <a name="module_RealtimeKitClient--module.exports+self"></a>
 
 #### module.exports.self
-
 The `self` object can be used to manipulate audio and video settings,
 and other configurations for the local participant. This exposes methods
 to enable and disable media tracks, share the user's screen, etc.
@@ -70,7 +68,6 @@ to enable and disable media tracks, share the user's screen, etc.
 <a name="module_RealtimeKitClient--module.exports+meta"></a>
 
 #### module.exports.meta
-
 The `room` object stores information about the current meeting, such
 as chat messages, polls, room name, etc.
 
@@ -78,7 +75,6 @@ as chat messages, polls, room name, etc.
 <a name="module_RealtimeKitClient--module.exports+ai"></a>
 
 #### module.exports.ai
-
 The `ai` object is used to interface with AI features.
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
@@ -87,7 +83,6 @@ features such as summary, and agenda using this object.
 <a name="module_RealtimeKitClient--module.exports+plugins"></a>
 
 #### module.exports.plugins
-
 The `plugins` object stores information about the plugins available in
 the current meeting. It exposes methods to activate and deactivate them.
 
@@ -95,7 +90,6 @@ the current meeting. It exposes methods to activate and deactivate them.
 <a name="module_RealtimeKitClient--module.exports+chat"></a>
 
 #### module.exports.chat
-
 The chat object stores the chat messages that were sent in the meeting.
 This includes text messages, images, and files.
 
@@ -103,7 +97,6 @@ This includes text messages, images, and files.
 <a name="module_RealtimeKitClient--module.exports+polls"></a>
 
 #### module.exports.polls
-
 The polls object stores the polls that were initiated in the meeting.
 It exposes methods to create and vote on polls.
 
@@ -111,7 +104,6 @@ It exposes methods to create and vote on polls.
 <a name="module_RealtimeKitClient--module.exports+connectedMeetings"></a>
 
 #### module.exports.connectedMeetings
-
 The connectedMeetings object stores the connected meetings states.
 It exposes methods to create/read/update/delete methods for connected meetings.
 
@@ -119,17 +111,15 @@ It exposes methods to create/read/update/delete methods for connected meetings.
 <a name="module_RealtimeKitClient--module.exports+__internals__"></a>
 
 #### module.exports.\_\_internals\_\_
-
-The **internals** object exposes the internal tools & utilities such as features and logger
+The __internals__ object exposes the internal tools & utilities such as features and logger
 so that client can utilise the same to build their own feature based UI.
-Logger (**internals**.logger) can be used to send logs to servers
-to inform of issues, if any, proactively.
+Logger (__internals__.logger) can be used to send logs to servers
+	to inform  of issues, if any, proactively.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+join"></a>
 
 #### module.exports.join()
-
 The `join()` method can be used to join the meeting.
 A `roomJoined` event is emitted on `self` when the room
 is joined successfully.
@@ -138,70 +128,65 @@ is joined successfully.
 <a name="module_RealtimeKitClient--module.exports+leave"></a>
 
 #### module.exports.leave()
-
 The `leave()` method can be used to leave a meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+joinRoom"></a>
 
 #### ~~module.exports.joinRoom()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+leaveRoom"></a>
 
 #### ~~module.exports.leaveRoom([state])~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param   | Type                        |
-| ------- | --------------------------- |
-| [state] | <code>LeaveRoomState</code> |
+| Param | Type |
+| --- | --- |
+| [state] | <code>LeaveRoomState</code> | 
 
 <a name="module_RealtimeKitClient--module.exports.initMedia"></a>
 
 #### module.exports.initMedia([options], [skipAwaits], [cachedUserDetails])
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
-
-| Param                 | Type                           | Default            |
-| --------------------- | ------------------------------ | ------------------ |
-| [options]             | <code>Object</code>            |                    |
-| [options.video]       | <code>boolean</code>           |                    |
-| [options.audio]       | <code>boolean</code>           |                    |
-| [options.constraints] | <code>MediaConstraints</code>  |                    |
-| [skipAwaits]          | <code>boolean</code>           | <code>false</code> |
-| [cachedUserDetails]   | <code>CachedUserDetails</code> |                    |
+| Param | Type | Default |
+| --- | --- | --- |
+| [options] | <code>Object</code> |  | 
+| [options.video] | <code>boolean</code> |  | 
+| [options.audio] | <code>boolean</code> |  | 
+| [options.constraints] | <code>MediaConstraints</code> |  | 
+| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
+| [cachedUserDetails] | <code>CachedUserDetails</code> |  | 
 
 <a name="module_RealtimeKitClient--module.exports.init"></a>
 
 #### module.exports.init(options)
-
 The `init` method can be used to instantiate the RealtimeKitClient class.
 This returns an instance of RealtimeKitClient, which can be used to perform
 actions on the meeting.
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param             | Description                                     |
-| ----------------- | ----------------------------------------------- |
-| options           | The options object.                             |
+| Param | Description |
+| --- | --- |
+| options | The options object. |
 | options.authToken | The authorization token received using the API. |
-| options.baseURI   | The base URL of the API.                        |
-| options.defaults  | The default audio and video settings.           |
+| options.baseURI | The base URL of the API. |
+| options.defaults | The default audio and video settings. |
 
 <a name="module_RealtimeKitClient--module.exports.setupContext"></a>
 
 #### module.exports.setupContext(peerId, options, meetingId, args)
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+| Param | Type |
+| --- | --- |
+| peerId | <code>string</code> | 
+| options | <code>RealtimeKitClientOptions</code> | 
+| meetingId | <code>string</code> | 
+| args | <code>any</code> | 
 
-| Param     | Type                                  |
-| --------- | ------------------------------------- |
-| peerId    | <code>string</code>                   |
-| options   | <code>RealtimeKitClientOptions</code> |
-| meetingId | <code>string</code>                   |
-| args      | <code>any</code>                      |
diff --git a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
index d9e3105165b252d..b94947abd5d3245 100644
--- a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
+++ b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
@@ -23,7 +23,6 @@ The following SDKs are collectively referred to as Web SDKs:
 - [`@cloudflare/realtimekit-virtual-background`](https://www.npmjs.com/package/@cloudflare/realtimekit-virtual-background)
 
 Overview of licenses:
-
 - Apache-2.0 (3)
 - ISC (1)
 - MIT (16)
@@ -814,12 +813,10 @@ Apache License
 ## RealtimeKit Android SDKs
 
 The following SDKs are collectively referred to as Android SDKs:
-
 - [`com.cloudflare.realtimekit:core-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-android)
 - [`com.cloudflare.realtimekit:ui-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/ui-android)
 
 Overview of licenses:
-
 - Apache-2.0 (24)
 
 ### Apache-2.0 (15 packages)
@@ -1935,13 +1932,11 @@ Apache License
 ## RealtimeKit iOS SDKs
 
 The following SDKs are collectively referred to as iOS SDKs:
-
 - [`RealtimeKit`](https://github.com/dyte-in/RealtimeKitCoreiOS)
 - [`RealtimeKitUI`](https://github.com/dyte-in/RealtimeKitUI)
 - [`RealtimeKit KMM Core`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-iosarm64)
 
 Overview of licenses:
-
 - Apache-2.0 (8)
 
 ### Apache-2.0 (4 packages)
@@ -2817,12 +2812,10 @@ Apache License
 ## RealtimeKit Flutter SDKs
 
 The following SDKs are collectively referred to as Flutter SDKs:
-
 - [`realtimekit_core`](https://pub.dev/packages/realtimekit_core)
 - [`realtimekit_ui`](https://pub.dev/packages/realtimekit_ui)
 
 Overview of licenses:
-
 - Apache-2.0 (1)
 - BSD-3-Clause (55)
 - MIT (10)
@@ -2855,7 +2848,7 @@ Used by:
 [watcher](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2014, the Dart project authors.
+Copyright 2014, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -2899,7 +2892,7 @@ Used by:
 [typed_data](https://github.com/dart-lang/core)
 
 ```
-Copyright 2015, the Dart project authors.
+Copyright 2015, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3174,7 +3167,7 @@ Used by:
 [term_glyph](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2017, the Dart project authors.
+Copyright 2017, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3212,7 +3205,7 @@ Used by:
 [package_config](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2019, the Dart project authors.
+Copyright 2019, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3250,7 +3243,7 @@ Used by:
 [logging](https://github.com/dart-lang/core)
 
 ```
-Copyright 2013, the Dart project authors.
+Copyright 2013, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3288,7 +3281,7 @@ Used by:
 [test_core](https://github.com/dart-lang/test)
 
 ```
-Copyright 2018, the Dart project authors.
+Copyright 2018, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3758,11 +3751,11 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ```
 
-### BSD-3-Clause (\_fe_analyzer_shared)
+### BSD-3-Clause (_fe_analyzer_shared)
 
 Used by:
 
-[\_fe_analyzer_shared](https://github.com/dart-lang/sdk)
+[_fe_analyzer_shared](https://github.com/dart-lang/sdk)
 
 ```
 Copyright 2019, the Dart project authors.
@@ -3930,7 +3923,7 @@ Used by:
 [web_socket_channel](https://github.com/dart-lang/http)
 
 ```
-Copyright 2016, the Dart project authors.
+Copyright 2016, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4001,7 +3994,7 @@ Used by:
 [web_socket](https://github.com/dart-lang/http)
 
 ```
-Copyright 2024, the Dart project authors.
+Copyright 2024, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4037,7 +4030,7 @@ Used by:
 [frontend_server_client](https://github.com/dart-lang/webdev)
 
 ```
-Copyright 2020, the Dart project authors.
+Copyright 2020, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4617,12 +4610,10 @@ THE SOFTWARE.
 ## RealtimeKit React Native SDKs
 
 The following SDKs are collectively referred to as React Native SDKs:
-
 - [`@cloudflare/realtimekit-react-native`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native)
 - [`@cloudflare/realtimekit-react-native-ui`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native-ui)
 
 Overview of licenses:
-
 - Apache-2.0 (3)
 - BSD-2-Clause (10)
 - BSD-3-Clause (3)
@@ -6705,25 +6696,25 @@ The MIT License
 
 Copyright (c) 2013 Dominic Tarr
 
-Permission is hereby granted, free of charge,
-to any person obtaining a copy of this software and
-associated documentation files (the "Software"), to
-deal in the Software without restriction, including
-without limitation the rights to use, copy, modify,
-merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom
-the Software is furnished to do so,
+Permission is hereby granted, free of charge, 
+to any person obtaining a copy of this software and 
+associated documentation files (the "Software"), to 
+deal in the Software without restriction, including 
+without limitation the rights to use, copy, modify, 
+merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom 
+the Software is furnished to do so, 
 subject to the following conditions:
 
-The above copyright notice and this permission notice
+The above copyright notice and this permission notice 
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -7700,25 +7691,25 @@ The MIT License
 
 Copyright (c) 2015 John Hiesey
 
-Permission is hereby granted, free of charge,
-to any person obtaining a copy of this software and
-associated documentation files (the "Software"), to
-deal in the Software without restriction, including
-without limitation the rights to use, copy, modify,
-merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom
-the Software is furnished to do so,
+Permission is hereby granted, free of charge, 
+to any person obtaining a copy of this software and 
+associated documentation files (the "Software"), to 
+deal in the Software without restriction, including 
+without limitation the rights to use, copy, modify, 
+merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom 
+the Software is furnished to do so, 
 subject to the following conditions:
 
-The above copyright notice and this permission notice
+The above copyright notice and this permission notice 
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -8677,7 +8668,7 @@ Used by:
 ```
 The MIT License (MIT)
 
-Copyright (c) 2015
+Copyright (c) 2015 
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9206,7 +9197,7 @@ Used by:
 [convert-source-map](https://github.com/thlorenz/convert-source-map)
 
 ```
-Copyright 2013 Thorsten Lorenz.
+Copyright 2013 Thorsten Lorenz. 
 All rights reserved.
 
 Permission is hereby granted, free of charge, to any person
@@ -9556,7 +9547,7 @@ exhaustive, and do not form part of our licenses.
      such as asking that all changes be marked or described.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
-     for the public:
+     for the public: 
 	wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
@@ -10890,4 +10881,4 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
index 837b0108533d03f..3a3cdb4f8122af5 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
@@ -18,15 +18,15 @@ RealtimeKit's watermark feature enables you to include an image as a watermark i
 
 ```json
 {
-	"video_config": {
-		"watermark": {
-			"url": "https://test.io/images/client-logos-6.webp",
-			"position": "left top",
-			"size": {
-				"height": 20,
-				"width": 100
-			}
-		}
-	}
+  "video_config": {
+    "watermark": {
+      "url": "https://test.io/images/client-logos-6.webp",
+      "position": "left top",
+      "size": {
+        "height": 20,
+        "width": 100
+      }
+    }
+  }
 }
 ```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
index f6ff1aa7a6b2ed3..e79a05b4153957e 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
@@ -26,9 +26,9 @@ example:
 
 ```json
 {
-	"video_config": {
-		"codec": "H264"
-	}
+  "video_config": {
+    "codec": "H264"
+  }
 }
 ```
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
index 81744c2746450cb..67da5cc041affca 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
@@ -12,13 +12,13 @@ products:
 
 The recording of a meeting can have the following states:
 
-| Name      | Description                                                                                                                                                                                                                                                |
-| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                         |
-| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                             |
+| Name      | Description                                                                                                                                                                                                                                         |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                  |
+| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                      |
 | UPLOADING | The recording has been stopped and the file is being uploaded to the cloud storage. If you have not specified storage details, then the files will be uploaded only to RealtimeKit's server. Any RTMP and livestreaming link will also stop at this stage. |
-| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                            |
-| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                           |
+| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                     |
+| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                    |
 
 ## Fetching the state
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
index aa28566cf639ab0..50d601987d14693 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -8,16 +8,9 @@ products:
   - realtime
 ---
 
-Track recording lets you record participant audio as separate WebM files instead of one composite meeting recording. Use it when you need speaker-level control over what you store, process, or review.
+Track recording records each participant's audio as a separate WebM file in RealtimeKit's Cloudflare R2 bucket. Use track recording when you need isolated speaker tracks for post-processing, transcription, compliance workflows, or audio analysis.
 
-With track recording, you can record specific participant tracks by passing `user_ids`, which is useful for content-sensitive or regulated workflows where recording every participant is unnecessary. If you do not provide `user_ids`, RealtimeKit will record all participant audio tracks as separate WebM files by default.
-
-To pass `user_ids` for specific participant track recording, use the following minimum SDK versions:
-
-- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
-- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
-- Android Core or iOS Core: version `2.0.0` or later
-- Android UI Kit or iOS UI Kit: version `1.1.0` or later
+Composite recording creates one mixed meeting recording. Track recording creates one file per recorded participant peer.
 
 :::note
 
@@ -29,36 +22,19 @@ Track recording currently supports audio tracks only. Video track recording is i
 
 Track recording has the following requirements and limits:
 
-| Limit                 | Description                                                                  |
-| --------------------- | ---------------------------------------------------------------------------- |
-| Active meeting        | The meeting must have an active live session.                                |
-| Media kind            | Only `audio` layers are recorded.                                            |
-| Participant selection | Pass up to 100 values in `user_ids`.                                         |
-| Storage               | Files are uploaded to RealtimeKit's managed R2 bucket with zero-egress fees. |
-| File retention        | RealtimeKit bucket download URLs expire after seven days.                    |
+| Limit                 | Description                                           |
+| --------------------- | ----------------------------------------------------- |
+| Active meeting        | The meeting must have an active live session.         |
+| Media kind            | Only `audio` layers are recorded.                     |
+| Participant selection | Pass up to `100` values in `user_ids`.                |
+| Storage               | Files are uploaded to the RealtimeKit bucket.         |
+| File retention        | RealtimeKit bucket download URLs expire after seven days. |
 
 ## Start track recording
 
-### Record specific participants
-
-To record separate audio tracks for specific participants, call `POST /recordings/track` with the meeting ID and the participant `user_ids`.
-
-```bash
-curl --request POST \
-  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
-  --header 'Authorization: Bearer <api_token>' \
-  --header 'Content-Type: application/json' \
-  --data '{
-  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
-  "user_ids": ["user-123", "user-456"]
-}'
-```
-
-RealtimeKit records current and future participant peers whose `user_id` matches the allowlist. Participants whose `user_id` is not listed are not recorded.
+To start track recording, call `POST /recordings/track` with the meeting ID.
 
-### Record all participants as separate tracks
-
-Omit `user_ids` to record separate audio tracks for all participants in the live meeting. RealtimeKit creates one WebM file for each recorded participant peer.
+If you omit `layers`, RealtimeKit records all participant audio. You can pass an audio layer to set a file name prefix for generated files.
 
 ```bash
 curl --request POST \
@@ -87,9 +63,26 @@ The response includes a recording ID. Use this ID to stop or fetch the recording
 }
 ```
 
-## Customize file names with prefixes
+## Record selected participants
+
+Pass `user_ids` to record only specific participants. RealtimeKit records current and future participant peers whose `user_id` matches the allowlist.
+
+:::caution
+
+To use selective track recording with `user_ids`, contact your Cloudflare account team or RealtimeKit support.
+
+:::
+
+```json
+{
+	"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+	"user_ids": ["user-123", "user-456"]
+}
+```
+
+## Set file name prefix
 
-Use `layers.default.file_name_prefix` to prefix every generated track recording file.
+Use `file_name_prefix` to prefix every generated track recording file.
 
 ```json
 {
@@ -127,7 +120,7 @@ After track recording stops, RealtimeKit uploads the per-participant WebM files
 
 Track recording uses the same recording status lifecycle as composite recording. To monitor status, refer to [Monitor Recording Status](/realtime/realtimekit/recording-guide/monitor-status/).
 
-When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. For track recordings, `download_url` contains per-participant WebM file URLs grouped by layer.
+When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. The `download_url` field contains the recorded WebM files for participant peers.
 
 ```json
 {
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
index 740b8984d91accc..a530264178e2cd7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
index be354415f804c68..9022f7eef15914a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-ai-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,5 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-toggle [meeting]="meeting" size="md" variant="button"> </rtk-ai-toggle>
+<rtk-ai-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
+</rtk-ai-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
index 05bb2a1ea2666d2..36207327073578c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-ai-transcriptions component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,6 +26,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-transcriptions [initialTranscriptions]="[]" [meeting]="meeting">
+<rtk-ai-transcriptions
+ [initialTranscriptions]="[]"
+ [meeting]="meeting">
 </rtk-ai-transcriptions>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
index 8d64f23b0df3f0b..936d95be25b08c0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ai component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai [meeting]="meeting" size="md" [view]="aiview"> </rtk-ai>
+<rtk-ai
+ [meeting]="meeting"
+ size="md"
+ [view]="aiview">
+</rtk-ai>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
index 74fb58b92b23308..690fb5c0632fc17 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-grid component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-grid
-	[config]="defaultUiConfig"
-	[hideSelf]="true"
-	[meeting]="meeting"
->
+ [config]="defaultUiConfig"
+ [hideSelf]="true"
+ [meeting]="meeting">
 </rtk-audio-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
index 9fa0eff7807d9be..dbb17aafd24724b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-tile component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-tile
-	[config]="defaultUiConfig"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [config]="defaultUiConfig"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-audio-tile>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
index cc99527e230b702..1622d030b9255cf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-audio-visualizer component (Angular Library)
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ Commonly used inside `rtk-name-tag`.
 ```html
 <!-- component.html -->
 <rtk-audio-visualizer
-	[hideMuted]="true"
-	[isScreenShare]="true"
-	[participant]="participant"
->
+ [hideMuted]="true"
+ [isScreenShare]="true"
+ [participant]="participant">
 </rtk-audio-visualizer>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
index 6bd382f5ba1c7b1..ff5a9ab19b357c0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-avatar component (Angular Library)
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ Avatar component which renders a participant's image or their initials.
 
 ```html
 <!-- component.html -->
-<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
+<rtk-avatar
+ participant="example"
+ size="md"
+ variant="circular">
+</rtk-avatar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
index 942b66a929beefc..b310482b33cdfe8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-breakout-room-manager component (Angular Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-breakout-room-manager
-	[allowDelete]="true"
-	[assigningParticipants]="true"
-	[defaultExpanded]="true"
->
+ [allowDelete]="true"
+ [assigningParticipants]="true"
+ [defaultExpanded]="true">
 </rtk-breakout-room-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
index 8d2a38f304f03fd..2d1f1e58d56e53f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-breakout-room-participants component (Angular
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-breakout-room-participants
-	[meeting]="meeting"
-	participantIds="example"
-	selectedParticipantIds="example"
->
+ [meeting]="meeting"
+ participantIds="example"
+ selectedParticipantIds="example">
 </rtk-breakout-room-participants>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
index 6b60a42d4f64b07..bbe7a129471cfef 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-breakout-rooms-manager component (Angular Lib
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-breakout-rooms-manager [meeting]="meeting"> </rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager
+ [meeting]="meeting">
+</rtk-breakout-rooms-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
index e769d064ce27906..dab4a3a9ced6758 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-breakout-rooms-toggle component (Angular Libr
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ You need to pass the `meeting` object to it.
 ```html
 <!-- component.html -->
 <rtk-breakout-rooms-toggle
-	[iconPack]="defaultIconPack"
-	[meeting]="meeting"
-	size="md"
->
+ [iconPack]="defaultIconPack"
+ [meeting]="meeting"
+ size="md">
 </rtk-breakout-rooms-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
index a9399e40c4b7a2c..706f133335069c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-broadcast-message-modal component (Angular Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-broadcast-message-modal [meeting]="meeting"> </rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal
+ [meeting]="meeting">
+</rtk-broadcast-message-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
index 49d3ca7ffe6a357..ed08f480b320ab1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-button component (Angular Library)
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ A button that follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-button [disabled]="true" [kind]="buttonkind" [reverse]="true">
+<rtk-button
+ [disabled]="true"
+ [kind]="buttonkind"
+ [reverse]="true">
 </rtk-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
index 92270e3c97fe0e1..755404225238040 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-camera-selector component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -41,9 +39,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-camera-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-camera-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
index db38dc91c0aac70..00b9d2b1e4bdd06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-camera-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles your camera.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ A button which toggles your camera.
 
 ```html
 <!-- component.html -->
-<rtk-camera-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-camera-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-camera-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
index 5dc17611c79b114..66da419d1dea460 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-caption-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-caption-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-caption-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-caption-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
index b6ff46e4d62c8d9..ee2887a10f7e46a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat-composer-ui component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-composer-ui
-	[canSendFiles]="true"
-	[canSendTextMessage]="true"
-	size="md"
->
+ [canSendFiles]="true"
+ [canSendTextMessage]="true"
+ size="md">
 </rtk-chat-composer-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
index 3b98703d1ac78cb..407b10b43a4197f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-chat-composer-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,9 +37,9 @@ A component which renders a chat composer
 ```html
 <!-- component.html -->
 <rtk-chat-composer-view
-	[canSendFiles]="true"
-	[canSendTextMessage]="true"
-	inputTextPlaceholder="example"
->
+ [canSendFiles]="true"
+ [canSendTextMessage]="true"
+ inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
index 18489ada36fdf99..400bbe3d46a8aaa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
@@ -5,10 +5,9 @@ description: API reference for rtk-chat-header component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
@@ -18,3 +17,4 @@ _No properties available._
 <!-- component.html -->
 <rtk-chat-header></rtk-chat-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
index 98cb5beca666769..de48d16b7b4d731 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
@@ -5,30 +5,29 @@ description: API reference for rtk-chat-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -43,6 +42,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-message [alignRight]="true" [canDelete]="true" [canEdit]="true">
+<rtk-chat-message
+ [alignRight]="true"
+ [canDelete]="true"
+ [canEdit]="true">
 </rtk-chat-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
index b42f6dc5f8f79eb..ce18aa44fb427c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-chat-messages-ui-paginated component (Angular
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui-paginated
-	[meeting]="meeting"
-	[privateChatRecipient]="participant | null"
-	size="md"
->
+ [meeting]="meeting"
+ [privateChatRecipient]="participant | null"
+ size="md">
 </rtk-chat-messages-ui-paginated>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
index 5241b26b67f1ef7..30863c471104539 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-chat-messages-ui component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui
-	[canPinMessages]="true"
-	[messages]="[]"
-	selectedGroup="example"
->
+ [canPinMessages]="true"
+ [messages]="[]"
+ selectedGroup="example">
 </rtk-chat-messages-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
index 674604a158dad2c..c523cd074c0f8b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-search-results component (Angular Librar
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-search-results
-	channelId="example"
-	[meeting]="meeting"
-	query="example"
->
+ channelId="example"
+ [meeting]="meeting"
+ query="example">
 </rtk-chat-search-results>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
index 784cf425f1ad9a0..0ab9edbe1fcae7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-chat-selector-ui component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-selector-ui
-	[groups]="[]"
-	selectedGroupId="example"
-	selfUserId="example"
->
+ [groups]="[]"
+ selectedGroupId="example"
+ selfUserId="example">
 </rtk-chat-selector-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
index ef6a41c79405f4a..e7e5178d7c5072b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-selector component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-selector [meeting]="meeting" size="md"> </rtk-chat-selector>
+<rtk-chat-selector
+ [meeting]="meeting"
+ size="md">
+</rtk-chat-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
index 942cba2a0f25e3c..1973396bb8401c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
@@ -5,28 +5,23 @@ description: API reference for rtk-chat-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of chat.
-You need to pass the `meeting` object to it to see the unread messages count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "chat";
-}
-```
+ You need to pass the `meeting` object to it to see the unread messages count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'chat' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -41,6 +36,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-chat-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-chat-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-chat-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
index b968cfe975421fa..12504ff17633de3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat component (Angular Library)
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 
 ```html
 <!-- component.html -->
-<rtk-chat [meeting]="meeting" size="md"> </rtk-chat>
+<rtk-chat
+ [meeting]="meeting"
+ size="md">
+</rtk-chat>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
index eea055224c112f4..fe930adaf1f7baf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-clock component (Angular Library)
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ Shows the time elapsed in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-clock [meeting]="meeting" size="md"> </rtk-clock>
+<rtk-clock
+ [meeting]="meeting"
+ size="md">
+</rtk-clock>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
index cd3a2dc87b17a9f..9af1775bf822f6f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-confirmation-modal component (Angular Library
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,8 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-confirmation-modal [meeting]="meeting"> </rtk-confirmation-modal>
+<rtk-confirmation-modal
+ [meeting]="meeting">
+</rtk-confirmation-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
index 85344ab73bbbe9e..52a23c6c3a7c14b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-controlbar-button component (Angular Library)
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ A skeleton component used for composing custom controlbar buttons.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar-button [brandIcon]="true" [disabled]="true" icon="example">
+<rtk-controlbar-button
+ [brandIcon]="true"
+ [disabled]="true"
+ icon="example">
 </rtk-controlbar-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
index f06437464f138a2..e7d739a49130cb7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-controlbar component (Angular Library)
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,6 +33,10 @@ Controlbar component provides you with various designs as variants.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar [disableRender]="true" [meeting]="meeting" size="md">
+<rtk-controlbar
+ [disableRender]="true"
+ [meeting]="meeting"
+ size="md">
 </rtk-controlbar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
index 61d79e5a7230d1b..1dcbd9f1997daff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-counter component (Angular Library)
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A number picker with increment and decrement buttons.
 
 ```html
 <!-- component.html -->
-<rtk-counter minValue="42" size="md" value="42"> </rtk-counter>
+<rtk-counter
+ minValue="42"
+ size="md"
+ value="42">
+</rtk-counter>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
index b878475ad72fa65..958771b9756d2be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-audio component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-audio [meeting]="meeting" size="md"> </rtk-debugger-audio>
+<rtk-debugger-audio
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
index c78c0ff33fa40dd..d6002b9a6aecd84 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-screenshare component (Angular Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,6 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-screenshare [meeting]="meeting" size="md">
+<rtk-debugger-screenshare
+ [meeting]="meeting"
+ size="md">
 </rtk-debugger-screenshare>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
index ea1d6d90d2b938e..60e7d5bb6289f9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-system component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-system [meeting]="meeting" size="md"> </rtk-debugger-system>
+<rtk-debugger-system
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-system>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
index 3e69cb73fef0b73..6c7e30bd9fcf7f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-debugger-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-debugger-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-debugger-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
index 2a84fafef9eb27b..d5210d91dc9db4d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-video component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-video [meeting]="meeting" size="md"> </rtk-debugger-video>
+<rtk-debugger-video
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-video>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
index f73efac1fa88dbf..40b74b2e1ab8c69 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-debugger component (Angular Library)
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,9 @@ A troubleshooting component to identify and fix any issues in the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-debugger [meeting]="meeting" size="md"> </rtk-debugger>
+<rtk-debugger
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
index db0a49fdc7627bc..c1de127979df06a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
@@ -5,26 +5,24 @@ description: API reference for rtk-dialog-manager component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -39,5 +37,9 @@ A component which handles all dialog elements in a component such as:
 
 ```html
 <!-- component.html -->
-<rtk-dialog-manager [meeting]="meeting" size="md"> </rtk-dialog-manager>
+<rtk-dialog-manager
+ [meeting]="meeting"
+ size="md">
+</rtk-dialog-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
index 76e69151c16a283..9635ed56702713b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-dialog component (Angular Library)
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ A dialog component.
 ```html
 <!-- component.html -->
 <rtk-dialog
-	[disableEscapeKey]="true"
-	[hideCloseButton]="true"
-	[meeting]="meeting"
->
+ [disableEscapeKey]="true"
+ [hideCloseButton]="true"
+ [meeting]="meeting">
 </rtk-dialog>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
index 41ba93a5da182cd..a8934fc38c1e469 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-emoji-picker-button component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker-button [isActive]="true"> </rtk-emoji-picker-button>
+<rtk-emoji-picker-button
+ [isActive]="true">
+</rtk-emoji-picker-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
index 01b94d697105b34..4247ddbd5c1ce10 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-emoji-picker component (Angular Library)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A very simple emoji picker component.
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker [focusWhenOpened]="true"> </rtk-emoji-picker>
+<rtk-emoji-picker
+ [focusWhenOpened]="true">
+</rtk-emoji-picker>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
index b2ad7d8f8e7eea2..b354fa28a6845bf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-ended-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ A screen which shows a meeting has ended.
 
 ```html
 <!-- component.html -->
-<rtk-ended-screen [meeting]="meeting" size="md"> </rtk-ended-screen>
+<rtk-ended-screen
+ [meeting]="meeting"
+ size="md">
+</rtk-ended-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
index 57ffa8f9039d89a..8344ce746896053 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-file-dropzone component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-dropzone [hostEl]="htmlelement"> </rtk-file-dropzone>
+<rtk-file-dropzone
+ [hostEl]="htmlelement">
+</rtk-file-dropzone>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
index 858399c5abccaed..48e4cca9eee6790 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-file-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ A component which renders a file message.
 
 ```html
 <!-- component.html -->
-<rtk-file-message-view name="example" size="42" url="example">
+<rtk-file-message-view
+ name="example"
+ size="42"
+ url="example">
 </rtk-file-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
index d32dd9edc995033..a19ab17f5b413c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-file-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders a file message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-file-message [isContinued]="true" [message]="filemessage" [now]="date">
+<rtk-file-message
+ [isContinued]="true"
+ [message]="filemessage"
+ [now]="date">
 </rtk-file-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
index 2470555e83eff13..4bda6955ac1042e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-file-picker-button component (Angular Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-file-picker-button
-	filter="example"
-	[icon]="defaultIconPack"
-	label="example"
->
+ filter="example"
+ [icon]="defaultIconPack"
+ label="example">
 </rtk-file-picker-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
index 04544ab3ecc21c2..f1d002421e860d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-fullscreen-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles full screen mode for any
-existing `rtk-meeting` component in the DOM.
+ existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                  |
-| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
-| `size`          | `Size`              | ✅       | -                 | Size                         |
-| `states`        | `States`            | ✅       | -                 | States object                |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
-| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
-| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ existing `rtk-meeting` component in the DOM.
 
 ```html
 <!-- component.html -->
-<rtk-fullscreen-toggle size="md" [targetElement]="htmlelement" variant="button">
+<rtk-fullscreen-toggle
+ size="md"
+ [targetElement]="htmlelement"
+ variant="button">
 </rtk-fullscreen-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
index 04a546d6b3f89a5..535638be929e69a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-grid-pagination component (Angular Library)
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ of active participants list. This is reflected in the `rtk-grid` component.
 ```html
 <!-- component.html -->
 <rtk-grid-pagination
-	[meeting]="meeting"
-	size="md"
-	[variant]="gridpaginationvariants"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="gridpaginationvariants">
 </rtk-grid-pagination>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
index 0c97b4b23ee5ea2..bd36da17a99fc2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-grid component (Angular Library)
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,5 +36,10 @@ The main grid component which abstracts all the grid handling logic and renders
 
 ```html
 <!-- component.html -->
-<rtk-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-grid>
+<rtk-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
+</rtk-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
index c09018ff727582b..6308160dae44850 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-header component (Angular Library)
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,5 +33,10 @@ A component that houses all the header components.
 
 ```html
 <!-- component.html -->
-<rtk-header [disableRender]="true" [meeting]="meeting" size="md"> </rtk-header>
+<rtk-header
+ [disableRender]="true"
+ [meeting]="meeting"
+ size="md">
+</rtk-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
index fdb32d3739e666a..b78675a57bf3f47 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-icon component (Angular Library)
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
@@ -29,5 +28,10 @@ An icon component which accepts an svg string and renders it.
 
 ```html
 <!-- component.html -->
-<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
+<rtk-icon
+ icon="example"
+ size="md"
+ variant="primary">
+</rtk-icon>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
index a5a0b562a10c71e..98bd3fd010f365a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-idle-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ i.e; when you are waiting for data about the meeting, specifically the `meeting`
 
 ```html
 <!-- component.html -->
-<rtk-idle-screen [meeting]="meeting"> </rtk-idle-screen>
+<rtk-idle-screen
+ [meeting]="meeting">
+</rtk-idle-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
index b6624557f5b530d..ae4305bd0b859b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-image-message-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A component which renders an image message.
 
 ```html
 <!-- component.html -->
-<rtk-image-message-view url="example"> </rtk-image-message-view>
+<rtk-image-message-view
+ url="example">
+</rtk-image-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
index 57f711994dc6ea4..e61a9e43a995966 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-image-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders an image message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-message [isContinued]="true" [message]="imagemessage" [now]="date">
+<rtk-image-message
+ [isContinued]="true"
+ [message]="imagemessage"
+ [now]="date">
 </rtk-image-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
index a5c26ec0490046f..ce55f03e3a1012b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-image-viewer component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows an image sent via chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-viewer [image]="imagemessage" size="md"> </rtk-image-viewer>
+<rtk-image-viewer
+ [image]="imagemessage"
+ size="md">
+</rtk-image-viewer>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
index 4a0ff811c795716..87a5a453715b10c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
@@ -5,12 +5,11 @@ description: API reference for rtk-information-tooltip component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
@@ -25,6 +24,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-information-tooltip [iconPack]="defaultIconPack">
+<rtk-information-tooltip
+ [iconPack]="defaultIconPack">
 </rtk-information-tooltip>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
index 54215fd0fe361ad..877a7a5fef233c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-join-stage component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-join-stage [dataConfig]="modaldataconfig" [meeting]="meeting" size="md">
+<rtk-join-stage
+ [dataConfig]="modaldataconfig"
+ [meeting]="meeting"
+ size="md">
 </rtk-join-stage>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
index 57d4746414928cd..28820eb49fe7d0e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-leave-button component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description |
-| ---------- | ------------------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size`              | ✅       | -                 | Size        |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A button which toggles visilibility of the leave confirmation dialog.
 
 ```html
 <!-- component.html -->
-<rtk-leave-button size="md" variant="button"> </rtk-leave-button>
+<rtk-leave-button
+ size="md"
+ variant="button">
+</rtk-leave-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
index 97cb75f991a2535..46d14fe211c640f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-leave-meeting component (Angular Library)
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ end meeting for all, if you have the permission.
 
 ```html
 <!-- component.html -->
-<rtk-leave-meeting [meeting]="meeting"> </rtk-leave-meeting>
+<rtk-leave-meeting
+ [meeting]="meeting">
+</rtk-leave-meeting>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
index 5822982df0f5a65..04858c6a723e9f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-indicator component (Angular Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-indicator [meeting]="meeting" size="md">
+<rtk-livestream-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-livestream-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
index 4aedae8a958db06..35b411555cd3561 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-player component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-player [meeting]="meeting" size="md"> </rtk-livestream-player>
+<rtk-livestream-player
+ [meeting]="meeting"
+ size="md">
+</rtk-livestream-player>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
index 43e52a53ecca76d..b965a5d73aa5a9c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-livestream-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -29,6 +28,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-livestream-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-livestream-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
index 8a910a96dda8544..c7422b474f26bde 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-logo component (Angular Library)
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 
 ```html
 <!-- component.html -->
-<rtk-logo logoUrl="example" [meeting]="meeting"> </rtk-logo>
+<rtk-logo
+ logoUrl="example"
+ [meeting]="meeting">
+</rtk-logo>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
index b5b816456292b1a..a7f872c4122307b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
@@ -5,13 +5,12 @@ description: API reference for rtk-markdown-view component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
@@ -26,5 +25,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-markdown-view maxLength="42" text="example"> </rtk-markdown-view>
+<rtk-markdown-view
+ maxLength="42"
+ text="example">
+</rtk-markdown-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
index 6adbeb63b44a99a..31cbdb86d3736f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-meeting-title component (Angular Library)
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ Displays the title of the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-meeting-title [meeting]="meeting"> </rtk-meeting-title>
+<rtk-meeting-title
+ [meeting]="meeting">
+</rtk-meeting-title>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
index fb1306311adea67..f1727781860d6f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
@@ -5,28 +5,27 @@ description: API reference for rtk-meeting component (Angular Library)
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -42,9 +41,9 @@ dialogs and other smaller bits of managing the application.
 ```html
 <!-- component.html -->
 <rtk-meeting
-	[applyDesignSystem]="true"
-	[config]="defaultUiConfig"
-	[gridLayout]="gridlayout1"
->
+ [applyDesignSystem]="true"
+ [config]="defaultUiConfig"
+ [gridLayout]="gridlayout1">
 </rtk-meeting>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
index ec230b806744c2e..b640c6b002c812a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-menu-item component (Angular Library)
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,6 +29,9 @@ A menu item component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-item [menuVariant]="'primary' | 'secondary'" size="md">
+<rtk-menu-item
+ [menuVariant]="'primary' | 'secondary'"
+ size="md">
 </rtk-menu-item>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
index cc93e411c5ade5a..7637b0961658634 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-menu-list component (Angular Library)
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A menu list component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-list [menuVariant]="'primary' | 'secondary'"> </rtk-menu-list>
+<rtk-menu-list
+ [menuVariant]="'primary' | 'secondary'">
+</rtk-menu-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
index 75bea868f269ae2..166ba3bed89a7cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-menu component (Angular Library)
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A menu component.
 
 ```html
 <!-- component.html -->
-<rtk-menu offset="42" [placement]="placement" size="md"> </rtk-menu>
+<rtk-menu
+ offset="42"
+ [placement]="placement"
+ size="md">
+</rtk-menu>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
index c6e6a410829ecf7..3a2c6f64fdbcb64 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-message-list-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders list of messages.
 
 ## Properties
 
-| Property            | Type                                | Required | Default           | Description                                                                   |
-| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
-| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
-| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
-| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
-| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
-| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
-| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
+| `messages` | `Message[]` | ✅ | - | Messages to render |
+| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
+| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ A component which renders list of messages.
 ```html
 <!-- component.html -->
 <rtk-message-list-view
-	estimateItemSize="42"
-	[loadMore]="(lastmessage: message)"
-	[messages]="[]"
->
+ estimateItemSize="42"
+ [loadMore]="(lastmessage: message)"
+ [messages]="[]">
 </rtk-message-list-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
index cf2cd2949c924ba..b9ab493f273c95c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
@@ -5,25 +5,24 @@ description: API reference for rtk-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
@@ -38,6 +37,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-message-view [actions]="[]" authorName="example" avatarUrl="example">
+<rtk-message-view
+ [actions]="[]"
+ authorName="example"
+ avatarUrl="example">
 </rtk-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
index 2f9fa6aaf5f2e0e..a99b4422c32892b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-mic-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles your microphone.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ A button which toggles your microphone.
 
 ```html
 <!-- component.html -->
-<rtk-mic-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-mic-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-mic-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
index 1cd58cb2ab66302..e387ad7b10c0480 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-microphone-selector component (Angular Librar
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -41,9 +39,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-microphone-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-microphone-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
index bc1d583c35d077b..fce5f3ee1150759 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
@@ -5,27 +5,26 @@ description: API reference for rtk-mixed-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +39,10 @@ A grid component which handles screenshares, plugins and participants.
 
 ```html
 <!-- component.html -->
-<rtk-mixed-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-mixed-grid>
+<rtk-mixed-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
+</rtk-mixed-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
index b6d4f9cd6a2fb91..da82abf95847f76 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
@@ -5,24 +5,20 @@ description: API reference for rtk-more-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,5 +33,8 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-more-toggle size="md"> </rtk-more-toggle>
+<rtk-more-toggle
+ size="md">
+</rtk-more-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
index e1a63a750b62c5d..267acdbbab6197c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-mute-all-button component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -29,6 +28,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-button [meeting]="meeting" size="md" variant="button">
+<rtk-mute-all-button
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-mute-all-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
index 406a2e94c9b8462..fd686e57c8f8e71 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-mute-all-confirmation component (Angular Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-confirmation [meeting]="meeting"> </rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation
+ [meeting]="meeting">
+</rtk-mute-all-confirmation>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
index 4f21452d80b34f9..ab2fdfe0ef135b8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-name-tag component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ A component which shows a participant's name.
 ```html
 <!-- component.html -->
 <rtk-name-tag
-	[isScreenShare]="true"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [isScreenShare]="true"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-name-tag>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
index 2776b79be409e22..7a1feeae085082d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-network-indicator component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-network-indicator
-	[isScreenShare]="true"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [isScreenShare]="true"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-network-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
index 3125a0458248d60..4bb7b34755028e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-notification component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ You need to remove the element after you receive the
 
 ```html
 <!-- component.html -->
-<rtk-notification [notification]="notification" [paused]="true" size="md">
+<rtk-notification
+ [notification]="notification"
+ [paused]="true"
+ size="md">
 </rtk-notification>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
index 29874314310420f..7d3957e28575b5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-notifications component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -34,5 +33,9 @@ There are also certain limits which you can set as well.
 
 ```html
 <!-- component.html -->
-<rtk-notifications [meeting]="meeting" size="md"> </rtk-notifications>
+<rtk-notifications
+ [meeting]="meeting"
+ size="md">
+</rtk-notifications>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
index f7b0a744c973685..da6b60ff9959d29 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-overlay-modal component (Angular Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,8 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-overlay-modal [meeting]="meeting"> </rtk-overlay-modal>
+<rtk-overlay-modal
+ [meeting]="meeting">
+</rtk-overlay-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
index 3a22d1b7e3c7e6a..a37ab406bfe13c8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-paginated-list component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-paginated-list
-	[autoScroll]="true"
-	[createNodes]="[]"
-	emptyListLabel="example"
->
+ [autoScroll]="true"
+ [createNodes]="[]"
+ emptyListLabel="example">
 </rtk-paginated-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
index dc709547d180829..a77302d526005b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participant-count component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-participant-count [meeting]="meeting" size="md"> </rtk-participant-count>
+<rtk-participant-count
+ [meeting]="meeting"
+ size="md">
+</rtk-participant-count>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
index 354d7029075e454..fbdb48390bc0073 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-participant-setup component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,14 +33,14 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participant-setup
-	[isPreview]="true"
-	[nameTagPosition]="| 'bottom-left'
+ [isPreview]="true"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
     | 'top-center'"
-	[participant]="participant"
->
+ [participant]="participant">
 </rtk-participant-setup>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
index e4417402b7a4053..a87d31044667f2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-participant-tile component (Angular Library)
 products:
   - realtime
 ---
-
 A component which plays a participants video and allows for placement
-of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -38,14 +37,14 @@ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component
 ```html
 <!-- component.html -->
 <rtk-participant-tile
-	[isPreview]="true"
-	[meeting]="meeting"
-	[nameTagPosition]="| 'bottom-left'
+ [isPreview]="true"
+ [meeting]="meeting"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'"
->
+    | 'top-center'">
 </rtk-participant-tile>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
index 2cb75bb1541d4dc..1dda330a33b1b70 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-participant component (Angular Library)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ You can perform privileged actions on the participant too.
 ```html
 <!-- component.html -->
 <rtk-participant
-	[meeting]="meeting"
-	[participant]="participant"
-	[view]="participantviewmode"
->
+ [meeting]="meeting"
+ [participant]="participant"
+ [view]="participantviewmode">
 </rtk-participant>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
index f35effb4020a5a4..8d1dd8043548405 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-audio component (Angular Library
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,8 +30,8 @@ A component which plays all the audio from participants and screenshares.
 ```html
 <!-- component.html -->
 <rtk-participants-audio
-	[meeting]="meeting"
-	[preloadedAudioElem]="htmlaudioelement"
->
+ [meeting]="meeting"
+ [preloadedAudioElem]="htmlaudioelement">
 </rtk-participants-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
index a0ad0b85a8677ae..805eb1630f5565d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-participants-stage-list component (Angular Li
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -37,9 +36,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-participants-stage-list
-	[hideHeader]="true"
-	[meeting]="meeting"
-	search="example"
->
+ [hideHeader]="true"
+ [meeting]="meeting"
+ search="example">
 </rtk-participants-stage-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
index 883999ff9c3ed7f..0963dbb1699ef78 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-stage-queue component (Angular L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-stage-queue
-	[meeting]="meeting"
-	size="md"
-	[view]="participantsviewmode"
->
+ [meeting]="meeting"
+ size="md"
+ [view]="participantsviewmode">
 </rtk-participants-stage-queue>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
index bb5751a926de3b4..dea0f244da4a0d5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
@@ -5,27 +5,22 @@ description: API reference for rtk-participants-toggle component (Angular Librar
 products:
   - realtime
 ---
-
 A button which toggles visibility of participants.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "participants";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'participants' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -40,6 +35,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-participants-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-participants-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-participants-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
index db2b020c8b88ab8..4ae0ae15cc28d5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-participants-viewer-list component (Angular L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-viewer-list
-	[hideHeader]="true"
-	[meeting]="meeting"
-	search="example"
->
+ [hideHeader]="true"
+ [meeting]="meeting"
+ search="example">
 </rtk-participants-viewer-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
index f31d8a204b73fd3..073a3e467d62514 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-waiting-list component (Angular
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-waiting-list
-	[meeting]="meeting"
-	size="md"
-	[view]="participantsviewmode"
->
+ [meeting]="meeting"
+ size="md"
+ [view]="participantsviewmode">
 </rtk-participants-waiting-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
index b771206de02ce49..f1984d1798d8879 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-participants component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-participants
-	[defaultParticipantsTabId]="participantstabid"
-	[meeting]="meeting"
-	size="md"
->
+ [defaultParticipantsTabId]="participantstabid"
+ [meeting]="meeting"
+ size="md">
 </rtk-participants>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
index 683752123d4ac43..dec4a8e63bdaed2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-permissions-message component (Angular Librar
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ information.
 
 ```html
 <!-- component.html -->
-<rtk-permissions-message [meeting]="meeting"> </rtk-permissions-message>
+<rtk-permissions-message
+ [meeting]="meeting">
+</rtk-permissions-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
index 930b8fea7a6f96a..94aad79b50a76a9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-pinned-message-selector component (Angular Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pinned-message-selector [meeting]="meeting"> </rtk-pinned-message-selector>
+<rtk-pinned-message-selector
+ [meeting]="meeting">
+</rtk-pinned-message-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
index 3b85d1e48dc9a96..ff56f4f7c8fc58c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-pip-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pip-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-pip-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-pip-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
index 8bc1fdc55db3407..2adc29e0fe4d37f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-plugin-main component (Angular Library)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which loads a plugin.
 
 ```html
 <!-- component.html -->
-<rtk-plugin-main [meeting]="meeting" [plugin]="rtkplugin"> </rtk-plugin-main>
+<rtk-plugin-main
+ [meeting]="meeting"
+ [plugin]="rtkplugin">
+</rtk-plugin-main>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
index 78da2d41fbb440d..1e55dfd168ff802 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
@@ -5,27 +5,22 @@ description: API reference for rtk-plugins-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of plugins.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "plugins";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'plugins' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -40,6 +35,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-plugins-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-plugins-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-plugins-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
index 916242388b0671a..ef10daccef93a00 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-plugins component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ and ability to enable or disable plugins.
 
 ```html
 <!-- component.html -->
-<rtk-plugins [meeting]="meeting" size="md"> </rtk-plugins>
+<rtk-plugins
+ [meeting]="meeting"
+ size="md">
+</rtk-plugins>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
index 92e52060d4aa885..ed3e4b10df95868 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-poll-form component (Angular Library)
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,9 @@ A component that lets you create a poll.
 
 ```html
 <!-- component.html -->
-<rtk-poll-form [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-poll-form>
+<rtk-poll-form
+ [iconPack]="defaultIconPack"
+ [t]="rtki18n">
+</rtk-poll-form>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
index ef928546a835336..9c50bc3106f4e74 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-poll component (Angular Library)
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ Shows a poll where a user can vote.
 
 ```html
 <!-- component.html -->
-<rtk-poll [permissions]="rtkpermissionspreset" [poll]="poll" self="example">
+<rtk-poll
+ [permissions]="rtkpermissionspreset"
+ [poll]="poll"
+ self="example">
 </rtk-poll>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
index 4bc3fdff2d81dca..8ee05f66d6d0c1e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
@@ -5,28 +5,23 @@ description: API reference for rtk-polls-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of polls.
-You need to pass the `meeting` object to it to see the unread polls count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "polls";
-}
-```
+ You need to pass the `meeting` object to it to see the unread polls count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'polls' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -41,6 +36,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-polls-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-polls-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-polls-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
index 32b89fad2be1ffb..0ccd3069c42b635 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-polls component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ the ability to enable or disable them as per their permissions.
 
 ```html
 <!-- component.html -->
-<rtk-polls [meeting]="meeting" size="md"> </rtk-polls>
+<rtk-polls
+ [meeting]="meeting"
+ size="md">
+</rtk-polls>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
index 51f3ba8000a0d15..ad5090fddeb9402 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-recording-indicator component (Angular Librar
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,6 +30,9 @@ It will not render anything if no recording is taking place.
 
 ```html
 <!-- component.html -->
-<rtk-recording-indicator [meeting]="meeting" size="md">
+<rtk-recording-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-recording-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
index 47452de08e7ec1c..5bc2e14496eecf7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-recording-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ who don't have the permission to record a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-toggle [disabled]="true" [meeting]="meeting" size="md">
+<rtk-recording-toggle
+ [disabled]="true"
+ [meeting]="meeting"
+ size="md">
 </rtk-recording-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
index 00b6c6adc2aabc0..dec1ea51ccfddcc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-screen-share-toggle component (Angular Librar
 products:
   - realtime
 ---
-
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ A button which toggles your screenshare.
 
 ```html
 <!-- component.html -->
-<rtk-screen-share-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-screen-share-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-screen-share-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
index ab7da66afebf434..f678a4456bcdc0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-screenshare-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which plays a participant's screenshared video.
-It also allows for placement of other components similar to `rtk-participant-tile`.
-This component will not render anything if the participant hasn't start screensharing.
+ It also allows for placement of other components similar to `rtk-participant-tile`.
+ This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property               | Type                                                                                                                     | Required | Default           | Description             |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
-| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
-| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
-| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
-| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
-| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
-| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
-| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
-| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -37,14 +36,14 @@ This component will not render anything if the participant hasn't start screensh
 ```html
 <!-- component.html -->
 <rtk-screenshare-view
-	[hideFullScreenButton]="true"
-	[meeting]="meeting"
-	[nameTagPosition]="| 'bottom-left'
+ [hideFullScreenButton]="true"
+ [meeting]="meeting"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'"
->
+    | 'top-center'">
 </rtk-screenshare-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
index 066d024c27fab77..5818d8214fc8651 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-audio component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +38,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 
 ```html
 <!-- component.html -->
-<rtk-settings-audio [meeting]="meeting" size="md"> </rtk-settings-audio>
+<rtk-settings-audio
+ [meeting]="meeting"
+ size="md">
+</rtk-settings-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
index d003ef750b8f9f1..56af8d465416a8d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
@@ -5,25 +5,21 @@ description: API reference for rtk-settings-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of settings module.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSettings: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSettings: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description   |
-| ---------- | ------------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`              | ✅       | -                 | Size          |
-| `states`   | `States`            | ✅       | -                 | States object |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -38,5 +34,9 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-settings-toggle size="md" variant="button"> </rtk-settings-toggle>
+<rtk-settings-toggle
+ size="md"
+ variant="button">
+</rtk-settings-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
index 381c51a0e2cf855..19b1a2ff5f132a7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-video component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +38,9 @@ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
 
 ```html
 <!-- component.html -->
-<rtk-settings-video [meeting]="meeting" size="md"> </rtk-settings-video>
+<rtk-settings-video
+ [meeting]="meeting"
+ size="md">
+</rtk-settings-video>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
index 9789b422d1f2837..339be6009cf2424 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-settings component (Angular Library)
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ as well as see your connection quality.
 
 ```html
 <!-- component.html -->
-<rtk-settings [meeting]="meeting" size="md"> </rtk-settings>
+<rtk-settings
+ [meeting]="meeting"
+ size="md">
+</rtk-settings>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
index 1406ce5ff38d369..d142bf62459ec14 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-setup-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,5 +32,9 @@ and media settings.
 
 ```html
 <!-- component.html -->
-<rtk-setup-screen [meeting]="meeting" size="md"> </rtk-setup-screen>
+<rtk-setup-screen
+ [meeting]="meeting"
+ size="md">
+</rtk-setup-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
index 94db2e01d33f007..8126edad79c871c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-sidebar-ui component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-sidebar-ui
-	currentTab="example"
-	[focusCloseButton]="true"
-	[hideCloseAction]="true"
->
+ currentTab="example"
+ [focusCloseButton]="true"
+ [hideCloseAction]="true">
 </rtk-sidebar-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
index 71e210674395a9d..bfd8e5e11b5177c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-sidebar component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -37,9 +36,9 @@ you can customize which sections you want, and which section you want as the def
 ```html
 <!-- component.html -->
 <rtk-sidebar
-	[defaultSection]="rtksidebarsection"
-	[enabledSections]="[]"
-	[meeting]="meeting"
->
+ [defaultSection]="rtksidebarsection"
+ [enabledSections]="[]"
+ [meeting]="meeting">
 </rtk-sidebar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
index bf202dd85e47787..ea88ffe55f9f48e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-simple-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ A grid component which renders only the participants in a simple grid.
 
 ```html
 <!-- component.html -->
-<rtk-simple-grid aspectRatio="example" gap="42" [meeting]="meeting">
+<rtk-simple-grid
+ aspectRatio="example"
+ gap="42"
+ [meeting]="meeting">
 </rtk-simple-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
index 16628f891f7fa01..c19b21a731b3bcd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
@@ -5,28 +5,26 @@ description: API reference for rtk-speaker-selector component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -42,9 +40,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-speaker-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-speaker-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
index 47ea91cffa10d78..915451bf50a7527 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spinner component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ A component which shows an animating spinner.
 
 ```html
 <!-- component.html -->
-<rtk-spinner size="md"> </rtk-spinner>
+<rtk-spinner
+ size="md">
+</rtk-spinner>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
index c3e3916f6cc12bb..f88cc7f531eac2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
@@ -5,29 +5,27 @@ description: API reference for rtk-spotlight-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -42,6 +40,10 @@ You can customize the layout to a `column` view, by default is is `row`.
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-grid aspectRatio="example" gap="42" gridSize="md">
+<rtk-spotlight-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
 </rtk-spotlight-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
index ddb740d3af6b233..60b6debe69e9082 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spotlight-indicator component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-indicator [meeting]="meeting" size="md">
+<rtk-spotlight-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-spotlight-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
index 27bcf1579495dbe..8e92fdc9598d17a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-stage-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `states`   | `States1`           | ✅       | -                 | States         |
-| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-stage-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-stage-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-stage-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
index 0b94a4fd1566c92..ccffa6559353763 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-stage component (Angular Library)
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ the `grid` and `sidebar` components.
 
 ```html
 <!-- component.html -->
-<rtk-stage [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-stage>
+<rtk-stage
+ [iconPack]="defaultIconPack"
+ [t]="rtki18n">
+</rtk-stage>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
index 75c781fb19e4ce2..f8993d18641c090 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-switch component (Angular Library)
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A switch component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-switch [checked]="true" [disabled]="true" [readonly]="true"> </rtk-switch>
+<rtk-switch
+ [checked]="true"
+ [disabled]="true"
+ [readonly]="true">
+</rtk-switch>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
index 339bfe235fceedb..1c8cf7cad9f42ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-tab-bar component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-tab-bar [activeTab]="tab" [layout]="gridlayout1" [meeting]="meeting">
+<rtk-tab-bar
+ [activeTab]="tab"
+ [layout]="gridlayout1"
+ [meeting]="meeting">
 </rtk-tab-bar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
index b2a412cd7210059..cba219399b00342 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-text-composer-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders a text composer
 
 ## Properties
 
-| Property            | Type                              | Required | Default           | Description                                   |
-| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
-| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
-| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
-| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
-| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
-| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
-| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
-| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
-| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
-| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `placeholder` | `string` | ✅ | - | Placeholder text |
+| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
+| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `value` | `string` | ✅ | - | Default value for text input |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ A component which renders a text composer
 ```html
 <!-- component.html -->
 <rtk-text-composer-view
-	[disabled]="true"
-	[keyDownHandler]="(e: keyboardevent)"
-	maxLength="42"
->
+ [disabled]="true"
+ [keyDownHandler]="(e: keyboardevent)"
+ maxLength="42">
 </rtk-text-composer-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
index 45ba2ef88c72b20..1ccf18977b7aa7d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-text-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message-view [isMarkdown]="true" text="example">
+<rtk-text-message-view
+ [isMarkdown]="true"
+ text="example">
 </rtk-text-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
index 230e3211e03b994..5060b6599375a57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-text-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message [isContinued]="true" [message]="textmessage" [now]="date">
+<rtk-text-message
+ [isContinued]="true"
+ [message]="textmessage"
+ [now]="date">
 </rtk-text-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
index 371a6eec0e5bcf2..4e6f62691aef692 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-tooltip component (Angular Library)
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
@@ -34,5 +33,10 @@ Tooltip component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-tooltip delay="42" [disabled]="true" [kind]="tooltipkind"> </rtk-tooltip>
+<rtk-tooltip
+ delay="42"
+ [disabled]="true"
+ [kind]="tooltipkind">
+</rtk-tooltip>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
index 570133cd5d8d464..4f6fe2ff039b589 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-transcript component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ You need to remove the element after you receive the
 
 ```html
 <!-- component.html -->
-<rtk-transcript [t]="rtki18n" transcript="example"> </rtk-transcript>
+<rtk-transcript
+ [t]="rtki18n"
+ transcript="example">
+</rtk-transcript>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
index 578013baff0705a..4e6c1192fcba044 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-transcripts component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,8 @@ There are also certain limits which you can set as well.
 
 ```html
 <!-- component.html -->
-<rtk-transcripts [meeting]="meeting"> </rtk-transcripts>
+<rtk-transcripts
+ [meeting]="meeting">
+</rtk-transcripts>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
index 8602181f2eb682c..0bfe8c1b9050c14 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ui-provider component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-ui-provider
-	[config]="defaultUiConfig"
-	[mode]="meeting"
-	[showSetupScreen]="true"
->
+ [config]="defaultUiConfig"
+ [mode]="meeting"
+ [showSetupScreen]="true">
 </rtk-ui-provider>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
index f64a1ff20e41f82..bb61879c99d4f26 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-viewer-count component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-viewer-count [meeting]="meeting" variant="primary"> </rtk-viewer-count>
+<rtk-viewer-count
+ [meeting]="meeting"
+ variant="primary">
+</rtk-viewer-count>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
index 040843c9c08f95e..63be1a12b781fd2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-virtualized-participant-list component (Angul
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-virtualized-participant-list
-	bufferedItemsCount="42"
-	[emptyListElement]="htmlelement"
-	itemHeight="42"
->
+ bufferedItemsCount="42"
+ [emptyListElement]="htmlelement"
+ itemHeight="42">
 </rtk-virtualized-participant-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
index ed0bda90edc56eb..46061d522a85431 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-waiting-screen component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-waiting-screen [meeting]="meeting"> </rtk-waiting-screen>
+<rtk-waiting-screen
+ [meeting]="meeting">
+</rtk-waiting-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
index 8ef6d5dcdfadf48..7f6ea96d5eaefa0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
index 4a58db7ec3bb580..e270c77642b2c4a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-ai-transcriptions component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,14 +24,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai-transcriptions> </rtk-ai-transcriptions>
+<rtk-ai-transcriptions>
+</rtk-ai-transcriptions>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ai-transcriptions");
+  const el = document.querySelector("rtk-ai-transcriptions");
 
-	el.initialTranscriptions = [];
-	el.meeting = meeting;
+  el.initialTranscriptions= [];
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
index a55ac07cacbbec6..970e391d75c32bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ai component (Web Components (HTML) Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai size="md"> </rtk-ai>
+<rtk-ai
+ size="md">
+</rtk-ai>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ai");
+  const el = document.querySelector("rtk-ai");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
index ac1e4eef81b052e..2d9130e9d8e4121 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-grid> </rtk-audio-grid>
+<rtk-audio-grid>
+</rtk-audio-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-grid");
+  const el = document.querySelector("rtk-audio-grid");
 
-	el.config = defaultUiConfig;
-	el.hideSelf = true;
-	el.meeting = meeting;
+  el.config= defaultUiConfig
+  el.hideSelf= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
index 6b7d96a935dd7f4..8959b0dde236c5c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-tile component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-tile> </rtk-audio-tile>
+<rtk-audio-tile>
+</rtk-audio-tile>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-tile");
+  const el = document.querySelector("rtk-audio-tile");
 
-	el.config = defaultUiConfig;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.config= defaultUiConfig
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
index 8ff29c76cd061be..813eab6b421006a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-audio-visualizer component (Web Components (H
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,15 +31,17 @@ Commonly used inside `rtk-name-tag`.
 ### With Properties
 
 ```html
-<rtk-audio-visualizer> </rtk-audio-visualizer>
+<rtk-audio-visualizer>
+</rtk-audio-visualizer>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-visualizer");
+  const el = document.querySelector("rtk-audio-visualizer");
 
-	el.hideMuted = true;
-	el.isScreenShare = true;
-	el.participant = participant;
+  el.hideMuted= true;
+  el.isScreenShare= true;
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
index d3d2acf95812bd9..7f8b81f1043b96d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-avatar component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
@@ -29,13 +28,18 @@ Avatar component which renders a participant's image or their initials.
 ### With Properties
 
 ```html
-<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
+<rtk-avatar
+ participant="example"
+ size="md"
+ variant="circular">
+</rtk-avatar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-avatar");
+  const el = document.querySelector("rtk-avatar");
 
-	el.participant = {};
+  el.participant= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
index 08565892ad5d286..0ffde64de310896 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-breakout-room-manager component (Web Componen
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,15 +31,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-room-manager> </rtk-breakout-room-manager>
+<rtk-breakout-room-manager>
+</rtk-breakout-room-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-room-manager");
+  const el = document.querySelector("rtk-breakout-room-manager");
 
-	el.allowDelete = true;
-	el.assigningParticipants = true;
-	el.defaultExpanded = true;
+  el.allowDelete= true;
+  el.assigningParticipants= true;
+  el.defaultExpanded= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
index 90bf0a7a6599970..a27e85c3f7202e5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-breakout-room-participants component (Web Com
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,18 +30,18 @@ run privileged actions on each participant according to your permissions.
 
 ```html
 <rtk-breakout-room-participants
-	participantIds="example"
-	selectedParticipantIds="example"
->
+ participantIds="example"
+ selectedParticipantIds="example">
 </rtk-breakout-room-participants>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-room-participants");
+  const el = document.querySelector("rtk-breakout-room-participants");
 
-	el.meeting = meeting;
-	el.participantIds = [];
-	el.selectedParticipantIds = [];
+  el.meeting= meeting
+  el.participantIds= [];
+  el.selectedParticipantIds= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
index 8186a41e5b921c7..4d3fe5430be46fe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-breakout-rooms-manager component (Web Compone
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-manager> </rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager>
+</rtk-breakout-rooms-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-rooms-manager");
+  const el = document.querySelector("rtk-breakout-rooms-manager");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
index 330651ce2800cee..12e8adafccffa1d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-breakout-rooms-toggle component (Web Componen
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,14 +30,17 @@ You need to pass the `meeting` object to it.
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-toggle size="md"> </rtk-breakout-rooms-toggle>
+<rtk-breakout-rooms-toggle
+ size="md">
+</rtk-breakout-rooms-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-rooms-toggle");
+  const el = document.querySelector("rtk-breakout-rooms-toggle");
 
-	el.iconPack = defaultIconPack;
-	el.meeting = meeting;
+  el.iconPack= defaultIconPack
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
index 90a5bf9760e290c..c701b24f24c37b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-broadcast-message-modal component (Web Compon
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-broadcast-message-modal> </rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal>
+</rtk-broadcast-message-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-broadcast-message-modal");
+  const el = document.querySelector("rtk-broadcast-message-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
index 2257bd8dc185484..190ce0bd634cebf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-button component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
@@ -30,14 +29,16 @@ A button that follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-button> </rtk-button>
+<rtk-button>
+</rtk-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-button");
+  const el = document.querySelector("rtk-button");
 
-	el.disabled = true;
-	el.reverse = true;
+  el.disabled= true;
+  el.reverse= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
index 31e3f2482ecb54c..839aea969dea5f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-camera-selector component (Web Components (HT
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-camera-selector size="md"> </rtk-camera-selector>
+<rtk-camera-selector
+ size="md">
+</rtk-camera-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-camera-selector");
+  const el = document.querySelector("rtk-camera-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
index 7726ca148fdf888..6062945d8cda350 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat-composer-ui component (Web Components (H
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-composer-ui size="md"> </rtk-chat-composer-ui>
+<rtk-chat-composer-ui
+ size="md">
+</rtk-chat-composer-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-composer-ui");
+  const el = document.querySelector("rtk-chat-composer-ui");
 
-	el.canSendFiles = true;
-	el.canSendTextMessage = true;
+  el.canSendFiles= true;
+  el.canSendTextMessage= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
index 6f24d73d4050be8..4f0b587d7e57cda 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-chat-composer-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,15 +34,17 @@ A component which renders a chat composer
 ### With Properties
 
 ```html
-<rtk-chat-composer-view inputTextPlaceholder="example">
+<rtk-chat-composer-view
+ inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-composer-view");
+  const el = document.querySelector("rtk-chat-composer-view");
 
-	el.canSendFiles = true;
-	el.canSendTextMessage = true;
+  el.canSendFiles= true;
+  el.canSendTextMessage= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
index d53fa58a0768116..00331fb11033be4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
@@ -5,10 +5,9 @@ description: API reference for rtk-chat-header component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
@@ -17,3 +16,4 @@ _No properties available._
 ```html
 <rtk-chat-header></rtk-chat-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
index 67158b1da131121..b49edd649f06ee1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
@@ -5,30 +5,29 @@ description: API reference for rtk-chat-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -41,15 +40,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-message> </rtk-chat-message>
+<rtk-chat-message>
+</rtk-chat-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-message");
+  const el = document.querySelector("rtk-chat-message");
 
-	el.alignRight = true;
-	el.canDelete = true;
-	el.canEdit = true;
+  el.alignRight= true;
+  el.canDelete= true;
+  el.canEdit= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
index 9b334cb50256afd..1a1f8d1bb2a313f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-chat-messages-ui-paginated component (Web Com
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui-paginated size="md"> </rtk-chat-messages-ui-paginated>
+<rtk-chat-messages-ui-paginated
+ size="md">
+</rtk-chat-messages-ui-paginated>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-messages-ui-paginated");
+  const el = document.querySelector("rtk-chat-messages-ui-paginated");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
index 91b79ea94878ffb..4315ce89d3ea880 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-chat-messages-ui component (Web Components (H
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,14 +30,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui selectedGroup="example"> </rtk-chat-messages-ui>
+<rtk-chat-messages-ui
+ selectedGroup="example">
+</rtk-chat-messages-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-messages-ui");
+  const el = document.querySelector("rtk-chat-messages-ui");
 
-	el.canPinMessages = true;
-	el.messages = [];
+  el.canPinMessages= true;
+  el.messages= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
index fd7ba927fca8daa..12510bac6bda05a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-search-results component (Web Components
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,14 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-search-results channelId="example" query="example">
+<rtk-chat-search-results
+ channelId="example"
+ query="example">
 </rtk-chat-search-results>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-search-results");
+  const el = document.querySelector("rtk-chat-search-results");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
index 713fb73bd989f34..88fd33ff9a1e098 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-chat-selector-ui component (Web Components (H
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
@@ -28,14 +27,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector-ui selectedGroupId="example" selfUserId="example">
+<rtk-chat-selector-ui
+ selectedGroupId="example"
+ selfUserId="example">
 </rtk-chat-selector-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-selector-ui");
+  const el = document.querySelector("rtk-chat-selector-ui");
 
-	el.groups = [];
+  el.groups= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
index f41ed748ffb2bcf..35043d7c0f2796e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-selector component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector size="md"> </rtk-chat-selector>
+<rtk-chat-selector
+ size="md">
+</rtk-chat-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-selector");
+  const el = document.querySelector("rtk-chat-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
index d296e1f85861da7..f1f46fa4254dfc0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 ### With Properties
 
 ```html
-<rtk-chat size="md"> </rtk-chat>
+<rtk-chat
+ size="md">
+</rtk-chat>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat");
+  const el = document.querySelector("rtk-chat");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
index f29acbd05520f7c..f4befa6dbda7af6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-clock component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ Shows the time elapsed in a meeting.
 ### With Properties
 
 ```html
-<rtk-clock size="md"> </rtk-clock>
+<rtk-clock
+ size="md">
+</rtk-clock>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-clock");
+  const el = document.querySelector("rtk-clock");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
index 54bd7f2399df487..59a36b5e16679da 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-confirmation-modal component (Web Components
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-confirmation-modal> </rtk-confirmation-modal>
+<rtk-confirmation-modal>
+</rtk-confirmation-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-confirmation-modal");
+  const el = document.querySelector("rtk-confirmation-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
index b63c726196d6d84..59c9be5f52f7987 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-controlbar-button component (Web Components (
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ A skeleton component used for composing custom controlbar buttons.
 ### With Properties
 
 ```html
-<rtk-controlbar-button icon="example"> </rtk-controlbar-button>
+<rtk-controlbar-button
+ icon="example">
+</rtk-controlbar-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-controlbar-button");
+  const el = document.querySelector("rtk-controlbar-button");
 
-	el.brandIcon = true;
-	el.disabled = true;
+  el.brandIcon= true;
+  el.disabled= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
index 326a72bac0165d4..c303a5102cb22ac 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-controlbar component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ Controlbar component provides you with various designs as variants.
 ### With Properties
 
 ```html
-<rtk-controlbar size="md"> </rtk-controlbar>
+<rtk-controlbar
+ size="md">
+</rtk-controlbar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-controlbar");
+  const el = document.querySelector("rtk-controlbar");
 
-	el.disableRender = true;
-	el.meeting = meeting;
+  el.disableRender= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
index 762c4d9d8d1cfc9..59bbbbf35837964 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-counter component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
@@ -29,14 +28,17 @@ A number picker with increment and decrement buttons.
 ### With Properties
 
 ```html
-<rtk-counter size="md"> </rtk-counter>
+<rtk-counter
+ size="md">
+</rtk-counter>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-counter");
+  const el = document.querySelector("rtk-counter");
 
-	el.minValue = 42;
-	el.value = 42;
+  el.minValue= 42;
+  el.value= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
index 22f1b026cd01b82..8733f92d520e775 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-audio component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-audio size="md"> </rtk-debugger-audio>
+<rtk-debugger-audio
+ size="md">
+</rtk-debugger-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-audio");
+  const el = document.querySelector("rtk-debugger-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
index 9435b3bec0238c6..f7f80fd287b5ef1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-screenshare component (Web Component
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-screenshare size="md"> </rtk-debugger-screenshare>
+<rtk-debugger-screenshare
+ size="md">
+</rtk-debugger-screenshare>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-screenshare");
+  const el = document.querySelector("rtk-debugger-screenshare");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
index a80a0f3c3252295..a7cc1725cc28364 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-system component (Web Components (HT
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-system size="md"> </rtk-debugger-system>
+<rtk-debugger-system
+ size="md">
+</rtk-debugger-system>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-system");
+  const el = document.querySelector("rtk-debugger-system");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
index 9deac224fdf1a02..84a90649d07675a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-video component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-video size="md"> </rtk-debugger-video>
+<rtk-debugger-video
+ size="md">
+</rtk-debugger-video>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-video");
+  const el = document.querySelector("rtk-debugger-video");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
index 7d345ee443ecde8..a8141d499177b06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-debugger component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ A troubleshooting component to identify and fix any issues in the meeting.
 ### With Properties
 
 ```html
-<rtk-debugger size="md"> </rtk-debugger>
+<rtk-debugger
+ size="md">
+</rtk-debugger>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger");
+  const el = document.querySelector("rtk-debugger");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
index 3709d9d501cd38e..ba7f8b4cd15bf85 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
@@ -5,26 +5,24 @@ description: API reference for rtk-dialog-manager component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,13 +35,16 @@ A component which handles all dialog elements in a component such as:
 ### With Properties
 
 ```html
-<rtk-dialog-manager size="md"> </rtk-dialog-manager>
+<rtk-dialog-manager
+ size="md">
+</rtk-dialog-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-dialog-manager");
+  const el = document.querySelector("rtk-dialog-manager");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
index d361f6b14ccdb8b..170ade6492a1274 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-dialog component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,15 +32,17 @@ A dialog component.
 ### With Properties
 
 ```html
-<rtk-dialog> </rtk-dialog>
+<rtk-dialog>
+</rtk-dialog>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-dialog");
+  const el = document.querySelector("rtk-dialog");
 
-	el.disableEscapeKey = true;
-	el.hideCloseButton = true;
-	el.meeting = meeting;
+  el.disableEscapeKey= true;
+  el.hideCloseButton= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
index 7060d45d649d00a..f21db9738750267 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-draft-attachment-view component (Web Componen
 products:
   - realtime
 ---
-
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property     | Type                                                 | Required | Default           | Description           |
-| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
-| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
-| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ A component which renders the draft attachment to send
 ### With Properties
 
 ```html
-<rtk-draft-attachment-view> </rtk-draft-attachment-view>
+<rtk-draft-attachment-view>
+</rtk-draft-attachment-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-draft-attachment-view");
+  const el = document.querySelector("rtk-draft-attachment-view");
 
-	el.attachment = {};
+  el.attachment= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
index be00c3a6e33ad46..f67d8a0f096c864 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-emoji-picker-button component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,13 +24,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-emoji-picker-button> </rtk-emoji-picker-button>
+<rtk-emoji-picker-button>
+</rtk-emoji-picker-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-emoji-picker-button");
+  const el = document.querySelector("rtk-emoji-picker-button");
 
-	el.isActive = true;
+  el.isActive= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
index 69aabd63c26f21f..a0876babb985962 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-emoji-picker component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ A very simple emoji picker component.
 ### With Properties
 
 ```html
-<rtk-emoji-picker> </rtk-emoji-picker>
+<rtk-emoji-picker>
+</rtk-emoji-picker>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-emoji-picker");
+  const el = document.querySelector("rtk-emoji-picker");
 
-	el.focusWhenOpened = true;
+  el.focusWhenOpened= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
index e5388b1585fd982..6aa6297284ea709 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-ended-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ A screen which shows a meeting has ended.
 ### With Properties
 
 ```html
-<rtk-ended-screen size="md"> </rtk-ended-screen>
+<rtk-ended-screen
+ size="md">
+</rtk-ended-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ended-screen");
+  const el = document.querySelector("rtk-ended-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
index fdf7e9e77e382ba..a9528f31a65a0cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-file-dropzone component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,11 +24,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-dropzone> </rtk-file-dropzone>
+<rtk-file-dropzone>
+</rtk-file-dropzone>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-dropzone");
+  const el = document.querySelector("rtk-file-dropzone");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
index 083396274de8c83..1764939b1ca0276 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-file-message-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
@@ -28,13 +27,17 @@ A component which renders a file message.
 ### With Properties
 
 ```html
-<rtk-file-message-view name="example" url="example"> </rtk-file-message-view>
+<rtk-file-message-view
+ name="example"
+ url="example">
+</rtk-file-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-message-view");
+  const el = document.querySelector("rtk-file-message-view");
 
-	el.size = 42;
+  el.size= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
index 936feef21b37fa9..811a6cce1a3b65e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-file-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders a file message from chat.
 ### With Properties
 
 ```html
-<rtk-file-message> </rtk-file-message>
+<rtk-file-message>
+</rtk-file-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-message");
+  const el = document.querySelector("rtk-file-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
index 851138e1627613b..54b3d5dd21d7da8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-file-picker-button component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,14 +26,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-picker-button filter="example" label="example">
+<rtk-file-picker-button
+ filter="example"
+ label="example">
 </rtk-file-picker-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-picker-button");
+  const el = document.querySelector("rtk-file-picker-button");
 
-	el.icon = defaultIconPack;
+  el.icon= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
index d663d791207416c..f3865d72720b943 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-grid-pagination component (Web Components (HT
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ of active participants list. This is reflected in the `rtk-grid` component.
 ### With Properties
 
 ```html
-<rtk-grid-pagination size="md"> </rtk-grid-pagination>
+<rtk-grid-pagination
+ size="md">
+</rtk-grid-pagination>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-grid-pagination");
+  const el = document.querySelector("rtk-grid-pagination");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
index 31eef43afae392f..cf79955eff09681 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-grid component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,13 +34,17 @@ The main grid component which abstracts all the grid handling logic and renders
 ### With Properties
 
 ```html
-<rtk-grid aspectRatio="example" gridSize="md"> </rtk-grid>
+<rtk-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-grid");
+  const el = document.querySelector("rtk-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
index a89c57e5b374cc4..1fb6ec7f5c5a1b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-header component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ A component that houses all the header components.
 ### With Properties
 
 ```html
-<rtk-header size="md"> </rtk-header>
+<rtk-header
+ size="md">
+</rtk-header>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-header");
+  const el = document.querySelector("rtk-header");
 
-	el.disableRender = true;
-	el.meeting = meeting;
+  el.disableRender= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
index 225e4d075df1fad..581f5e42555059a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-icon component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
@@ -27,11 +26,17 @@ An icon component which accepts an svg string and renders it.
 ### With Properties
 
 ```html
-<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
+<rtk-icon
+ icon="example"
+ size="md"
+ variant="primary">
+</rtk-icon>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-icon");
+  const el = document.querySelector("rtk-icon");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
index 54a72fdf6f17b5b..a2e6c178b6c1e82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-idle-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ i.e; when you are waiting for data about the meeting, specifically the `meeting`
 ### With Properties
 
 ```html
-<rtk-idle-screen> </rtk-idle-screen>
+<rtk-idle-screen>
+</rtk-idle-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-idle-screen");
+  const el = document.querySelector("rtk-idle-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
index 4faebe0ab376143..707341e71c859f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-image-message-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
@@ -27,11 +26,15 @@ A component which renders an image message.
 ### With Properties
 
 ```html
-<rtk-image-message-view url="example"> </rtk-image-message-view>
+<rtk-image-message-view
+ url="example">
+</rtk-image-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-message-view");
+  const el = document.querySelector("rtk-image-message-view");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
index cb324944fd49d2c..76c23bbf2dfca99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-image-message component (Web Components (HTML
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders an image message from chat.
 ### With Properties
 
 ```html
-<rtk-image-message> </rtk-image-message>
+<rtk-image-message>
+</rtk-image-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-message");
+  const el = document.querySelector("rtk-image-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
index b7e74691417c0f1..da7064e9253ab13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-image-viewer component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,11 +27,15 @@ A component which shows an image sent via chat.
 ### With Properties
 
 ```html
-<rtk-image-viewer size="md"> </rtk-image-viewer>
+<rtk-image-viewer
+ size="md">
+</rtk-image-viewer>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-viewer");
+  const el = document.querySelector("rtk-image-viewer");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
index f638b70c50e83d4..7950fc7f2bc101a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
@@ -5,12 +5,11 @@ description: API reference for rtk-information-tooltip component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
@@ -23,13 +22,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-information-tooltip> </rtk-information-tooltip>
+<rtk-information-tooltip>
+</rtk-information-tooltip>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-information-tooltip");
+  const el = document.querySelector("rtk-information-tooltip");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
index 7cbac34216b6b9a..36d7fcfd41612fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-join-stage component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-join-stage size="md"> </rtk-join-stage>
+<rtk-join-stage
+ size="md">
+</rtk-join-stage>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-join-stage");
+  const el = document.querySelector("rtk-join-stage");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
index 7953645ed11d440..60d83d6896b419b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-leave-meeting component (Web Components (HTML
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ end meeting for all, if you have the permission.
 ### With Properties
 
 ```html
-<rtk-leave-meeting> </rtk-leave-meeting>
+<rtk-leave-meeting>
+</rtk-leave-meeting>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-leave-meeting");
+  const el = document.querySelector("rtk-leave-meeting");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
index 7089f2c65e4c3b4..67707911b550145 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-indicator component (Web Component
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-indicator size="md"> </rtk-livestream-indicator>
+<rtk-livestream-indicator
+ size="md">
+</rtk-livestream-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-livestream-indicator");
+  const el = document.querySelector("rtk-livestream-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
index 4d35b373ccbafc2..5e6da815b9a6c32 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-player component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-player size="md"> </rtk-livestream-player>
+<rtk-livestream-player
+ size="md">
+</rtk-livestream-player>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-livestream-player");
+  const el = document.querySelector("rtk-livestream-player");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
index cb8ff8473cd8a3e..f6713bd26d22ab2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-logo component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 ### With Properties
 
 ```html
-<rtk-logo logoUrl="example"> </rtk-logo>
+<rtk-logo
+ logoUrl="example">
+</rtk-logo>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-logo");
+  const el = document.querySelector("rtk-logo");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
index 811851e7e12e984..d1381ac73ca5828 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
@@ -5,13 +5,12 @@ description: API reference for rtk-markdown-view component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
@@ -24,13 +23,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-markdown-view text="example"> </rtk-markdown-view>
+<rtk-markdown-view
+ text="example">
+</rtk-markdown-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-markdown-view");
+  const el = document.querySelector("rtk-markdown-view");
 
-	el.maxLength = 42;
+  el.maxLength= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
index 55697cb504158d1..ba9885092147cbb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-meeting-title component (Web Components (HTML
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ Displays the title of the meeting.
 ### With Properties
 
 ```html
-<rtk-meeting-title> </rtk-meeting-title>
+<rtk-meeting-title>
+</rtk-meeting-title>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-meeting-title");
+  const el = document.querySelector("rtk-meeting-title");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
index 753af9e783bf586..0a6abda1bfb826a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
@@ -5,28 +5,27 @@ description: API reference for rtk-meeting component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -39,14 +38,16 @@ dialogs and other smaller bits of managing the application.
 ### With Properties
 
 ```html
-<rtk-meeting> </rtk-meeting>
+<rtk-meeting>
+</rtk-meeting>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-meeting");
+  const el = document.querySelector("rtk-meeting");
 
-	el.applyDesignSystem = true;
-	el.config = defaultUiConfig;
+  el.applyDesignSystem= true;
+  el.config= defaultUiConfig
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
index c9fd4b7ff50b042..169675ff5a4498c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-menu-item component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,11 +27,15 @@ A menu item component.
 ### With Properties
 
 ```html
-<rtk-menu-item size="md"> </rtk-menu-item>
+<rtk-menu-item
+ size="md">
+</rtk-menu-item>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu-item");
+  const el = document.querySelector("rtk-menu-item");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
index 6735e67c1b647e8..88b9d8538638163 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-menu-list component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,11 +26,14 @@ A menu list component.
 ### With Properties
 
 ```html
-<rtk-menu-list> </rtk-menu-list>
+<rtk-menu-list>
+</rtk-menu-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu-list");
+  const el = document.querySelector("rtk-menu-list");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
index bb093d6585896ca..12ad508b8b32180 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-menu component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ A menu component.
 ### With Properties
 
 ```html
-<rtk-menu size="md"> </rtk-menu>
+<rtk-menu
+ size="md">
+</rtk-menu>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu");
+  const el = document.querySelector("rtk-menu");
 
-	el.offset = 42;
+  el.offset= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
index f409f90de250597..cdb30bac0e60ed4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-message-list-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders list of messages.
 
 ## Properties
 
-| Property            | Type                                | Required | Default           | Description                                                                   |
-| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
-| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
-| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
-| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
-| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
-| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
-| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
+| `messages` | `Message[]` | ✅ | - | Messages to render |
+| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
+| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
 
 ## Usage Examples
 
@@ -30,14 +29,16 @@ A component which renders list of messages.
 ### With Properties
 
 ```html
-<rtk-message-list-view> </rtk-message-list-view>
+<rtk-message-list-view>
+</rtk-message-list-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-message-list-view");
+  const el = document.querySelector("rtk-message-list-view");
 
-	el.estimateItemSize = 42;
-	el.messages = [];
+  el.estimateItemSize= 42;
+  el.messages= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
index 09def76b8fce5db..728e84fc9321401 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
@@ -5,25 +5,24 @@ description: API reference for rtk-message-view component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
@@ -36,13 +35,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-message-view authorName="example" avatarUrl="example"> </rtk-message-view>
+<rtk-message-view
+ authorName="example"
+ avatarUrl="example">
+</rtk-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-message-view");
+  const el = document.querySelector("rtk-message-view");
 
-	el.actions = [];
+  el.actions= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
index 0e2adb948d754a3..1565dc06501cfad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-microphone-selector component (Web Components
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-microphone-selector size="md"> </rtk-microphone-selector>
+<rtk-microphone-selector
+ size="md">
+</rtk-microphone-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-microphone-selector");
+  const el = document.querySelector("rtk-microphone-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
index 79ad17a23ebacab..d399d66944cd6fc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
@@ -5,27 +5,26 @@ description: API reference for rtk-mixed-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +37,17 @@ A grid component which handles screenshares, plugins and participants.
 ### With Properties
 
 ```html
-<rtk-mixed-grid aspectRatio="example" gridSize="md"> </rtk-mixed-grid>
+<rtk-mixed-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-mixed-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-mixed-grid");
+  const el = document.querySelector("rtk-mixed-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
index 83ee618b019e4c1..43e569451c44e9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
@@ -5,24 +5,20 @@ description: API reference for rtk-more-toggle component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,11 +31,15 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 ### With Properties
 
 ```html
-<rtk-more-toggle size="md"> </rtk-more-toggle>
+<rtk-more-toggle
+ size="md">
+</rtk-more-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-more-toggle");
+  const el = document.querySelector("rtk-more-toggle");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
index 6bb1b8bdce29e58..8100fe45db00611 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-mute-all-confirmation component (Web Componen
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-mute-all-confirmation> </rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation>
+</rtk-mute-all-confirmation>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-mute-all-confirmation");
+  const el = document.querySelector("rtk-mute-all-confirmation");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
index 14082b5393b2820..f6cee72609ed898 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-name-tag component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
@@ -31,15 +30,17 @@ A component which shows a participant's name.
 ### With Properties
 
 ```html
-<rtk-name-tag> </rtk-name-tag>
+<rtk-name-tag>
+</rtk-name-tag>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-name-tag");
+  const el = document.querySelector("rtk-name-tag");
 
-	el.isScreenShare = true;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.isScreenShare= true;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
index b5241b2075c51f8..a87b7aea196b1a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-network-indicator component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,15 +26,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-network-indicator> </rtk-network-indicator>
+<rtk-network-indicator>
+</rtk-network-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-network-indicator");
+  const el = document.querySelector("rtk-network-indicator");
 
-	el.isScreenShare = true;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.isScreenShare= true;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
index 4573caf03b498f0..e175a377ba80f6e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-notification component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ You need to remove the element after you receive the
 ### With Properties
 
 ```html
-<rtk-notification size="md"> </rtk-notification>
+<rtk-notification
+ size="md">
+</rtk-notification>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-notification");
+  const el = document.querySelector("rtk-notification");
 
-	el.paused = true;
+  el.paused= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
index c914a13e3c8be1a..1854740c5dd7087 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-notifications component (Web Components (HTML
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,13 +31,16 @@ There are also certain limits which you can set as well.
 ### With Properties
 
 ```html
-<rtk-notifications size="md"> </rtk-notifications>
+<rtk-notifications
+ size="md">
+</rtk-notifications>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-notifications");
+  const el = document.querySelector("rtk-notifications");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
index 9364cd4626d354c..0cb6286a078603e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-overlay-modal component (Web Components (HTML
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-overlay-modal> </rtk-overlay-modal>
+<rtk-overlay-modal>
+</rtk-overlay-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-overlay-modal");
+  const el = document.querySelector("rtk-overlay-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
index 4cde117f427306e..ef79cf0de81f3f7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-paginated-list component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-paginated-list emptyListLabel="example"> </rtk-paginated-list>
+<rtk-paginated-list
+ emptyListLabel="example">
+</rtk-paginated-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-paginated-list");
+  const el = document.querySelector("rtk-paginated-list");
 
-	el.autoScroll = true;
-	el.createNodes = [];
+  el.autoScroll= true;
+  el.createNodes= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
index 7719882d3fb4be7..d62e21d5129aa82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participant-count component (Web Components (
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-participant-count size="md"> </rtk-participant-count>
+<rtk-participant-count
+ size="md">
+</rtk-participant-count>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-count");
+  const el = document.querySelector("rtk-participant-count");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
index f6bd84e42574673..caf9dc47c1b7c3f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-participant-setup component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,14 +30,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participant-setup> </rtk-participant-setup>
+<rtk-participant-setup>
+</rtk-participant-setup>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-setup");
+  const el = document.querySelector("rtk-participant-setup");
 
-	el.isPreview = true;
-	el.participant = participant;
+  el.isPreview= true;
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
index 9a88d9c0a727ee0..4cab2f0eb1eca60 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-participant-tile component (Web Components (H
 products:
   - realtime
 ---
-
 A component which plays a participants video and allows for placement
-of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,14 +34,16 @@ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component
 ### With Properties
 
 ```html
-<rtk-participant-tile> </rtk-participant-tile>
+<rtk-participant-tile>
+</rtk-participant-tile>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-tile");
+  const el = document.querySelector("rtk-participant-tile");
 
-	el.isPreview = true;
-	el.meeting = meeting;
+  el.isPreview= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
index b353795e7b1d39f..bb8ac1dd6367703 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-participant component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
@@ -33,14 +32,16 @@ You can perform privileged actions on the participant too.
 ### With Properties
 
 ```html
-<rtk-participant> </rtk-participant>
+<rtk-participant>
+</rtk-participant>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant");
+  const el = document.querySelector("rtk-participant");
 
-	el.meeting = meeting;
-	el.participant = participant;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
index 60421301e0a2c48..1f8797c35adb77e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-audio component (Web Components
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A component which plays all the audio from participants and screenshares.
 ### With Properties
 
 ```html
-<rtk-participants-audio> </rtk-participants-audio>
+<rtk-participants-audio>
+</rtk-participants-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-audio");
+  const el = document.querySelector("rtk-participants-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
index fd655a61d22ef33..01d0f27f271ce7e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-participants-stage-list component (Web Compon
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -34,14 +33,17 @@ run privileged actions on each participant according to your permissions.
 ### With Properties
 
 ```html
-<rtk-participants-stage-list search="example"> </rtk-participants-stage-list>
+<rtk-participants-stage-list
+ search="example">
+</rtk-participants-stage-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-stage-list");
+  const el = document.querySelector("rtk-participants-stage-list");
 
-	el.hideHeader = true;
-	el.meeting = meeting;
+  el.hideHeader= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
index 7032a7bf6eae0d8..963520bc7e53b54 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-stage-queue component (Web Compo
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-stage-queue size="md"> </rtk-participants-stage-queue>
+<rtk-participants-stage-queue
+ size="md">
+</rtk-participants-stage-queue>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-stage-queue");
+  const el = document.querySelector("rtk-participants-stage-queue");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
index a9ac8f17b8c789a..bb79d669d9e7c10 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-participants-viewer-list component (Web Compo
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-viewer-list search="example"> </rtk-participants-viewer-list>
+<rtk-participants-viewer-list
+ search="example">
+</rtk-participants-viewer-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-viewer-list");
+  const el = document.querySelector("rtk-participants-viewer-list");
 
-	el.hideHeader = true;
-	el.meeting = meeting;
+  el.hideHeader= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
index f2090258605a509..bb42583235f5ab8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-waiting-list component (Web Comp
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-waiting-list size="md"> </rtk-participants-waiting-list>
+<rtk-participants-waiting-list
+ size="md">
+</rtk-participants-waiting-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-waiting-list");
+  const el = document.querySelector("rtk-participants-waiting-list");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
index 746ec51d0d8660b..1ba0901c553c486 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-participants component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,13 +31,16 @@ run privileged actions on each participant according to your permissions.
 ### With Properties
 
 ```html
-<rtk-participants size="md"> </rtk-participants>
+<rtk-participants
+ size="md">
+</rtk-participants>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants");
+  const el = document.querySelector("rtk-participants");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
index 150b3a750c1b030..57a566accadd160 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-permissions-message component (Web Components
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ information.
 ### With Properties
 
 ```html
-<rtk-permissions-message> </rtk-permissions-message>
+<rtk-permissions-message>
+</rtk-permissions-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-permissions-message");
+  const el = document.querySelector("rtk-permissions-message");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
index 5d603b6e59daf8b..a125dffe72ae892 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-pinned-message-selector component (Web Compon
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,13 +24,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-pinned-message-selector> </rtk-pinned-message-selector>
+<rtk-pinned-message-selector>
+</rtk-pinned-message-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-pinned-message-selector");
+  const el = document.querySelector("rtk-pinned-message-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
index 2d619085455442a..35331c64a8d6e7d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-plugin-main component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A component which loads a plugin.
 ### With Properties
 
 ```html
-<rtk-plugin-main> </rtk-plugin-main>
+<rtk-plugin-main>
+</rtk-plugin-main>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-plugin-main");
+  const el = document.querySelector("rtk-plugin-main");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
index 6461be9451e19f9..162f337bb6592f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-plugins component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ and ability to enable or disable plugins.
 ### With Properties
 
 ```html
-<rtk-plugins size="md"> </rtk-plugins>
+<rtk-plugins
+ size="md">
+</rtk-plugins>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-plugins");
+  const el = document.querySelector("rtk-plugins");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
index 3e1e182ae6b3e03..0272f65d9b3b48e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-poll-form component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ A component that lets you create a poll.
 ### With Properties
 
 ```html
-<rtk-poll-form> </rtk-poll-form>
+<rtk-poll-form>
+</rtk-poll-form>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-poll-form");
+  const el = document.querySelector("rtk-poll-form");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
index 74d94c512226da3..c7c9985644e098f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-poll component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,11 +29,15 @@ Shows a poll where a user can vote.
 ### With Properties
 
 ```html
-<rtk-poll self="example"> </rtk-poll>
+<rtk-poll
+ self="example">
+</rtk-poll>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-poll");
+  const el = document.querySelector("rtk-poll");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
index 98f0ca7892e6576..bef8f30b7725c38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-polls component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ the ability to enable or disable them as per their permissions.
 ### With Properties
 
 ```html
-<rtk-polls size="md"> </rtk-polls>
+<rtk-polls
+ size="md">
+</rtk-polls>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-polls");
+  const el = document.querySelector("rtk-polls");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
index 4d369e04d632069..d30318ecc55e3a5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-recording-indicator component (Web Components
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ It will not render anything if no recording is taking place.
 ### With Properties
 
 ```html
-<rtk-recording-indicator size="md"> </rtk-recording-indicator>
+<rtk-recording-indicator
+ size="md">
+</rtk-recording-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-recording-indicator");
+  const el = document.querySelector("rtk-recording-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
index a98b211032c1cbb..ec59e9f219e9f7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-recording-toggle component (Web Components (H
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ who don't have the permission to record a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-toggle size="md"> </rtk-recording-toggle>
+<rtk-recording-toggle
+ size="md">
+</rtk-recording-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-recording-toggle");
+  const el = document.querySelector("rtk-recording-toggle");
 
-	el.disabled = true;
-	el.meeting = meeting;
+  el.disabled= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
index 1f9320fd4015e72..a90c136dff9c22a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-screenshare-view component (Web Components (H
 products:
   - realtime
 ---
-
 A component which plays a participant's screenshared video.
-It also allows for placement of other components similar to `rtk-participant-tile`.
-This component will not render anything if the participant hasn't start screensharing.
+ It also allows for placement of other components similar to `rtk-participant-tile`.
+ This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property               | Type                                                                                                                     | Required | Default           | Description             |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
-| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
-| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
-| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
-| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
-| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
-| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
-| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
-| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,14 +33,16 @@ This component will not render anything if the participant hasn't start screensh
 ### With Properties
 
 ```html
-<rtk-screenshare-view> </rtk-screenshare-view>
+<rtk-screenshare-view>
+</rtk-screenshare-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-screenshare-view");
+  const el = document.querySelector("rtk-screenshare-view");
 
-	el.hideFullScreenButton = true;
-	el.meeting = meeting;
+  el.hideFullScreenButton= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
index eb030d8fd7c3939..be7787328820925 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-audio component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-settings-audio size="md"> </rtk-settings-audio>
+<rtk-settings-audio
+ size="md">
+</rtk-settings-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings-audio");
+  const el = document.querySelector("rtk-settings-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
index 90b1ddf72d04d58..523484ecbd3ff73 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-video component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
 ### With Properties
 
 ```html
-<rtk-settings-video size="md"> </rtk-settings-video>
+<rtk-settings-video
+ size="md">
+</rtk-settings-video>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings-video");
+  const el = document.querySelector("rtk-settings-video");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
index 5dd39a1a89173b9..4dd3286895b7a97 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-settings component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ as well as see your connection quality.
 ### With Properties
 
 ```html
-<rtk-settings size="md"> </rtk-settings>
+<rtk-settings
+ size="md">
+</rtk-settings>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings");
+  const el = document.querySelector("rtk-settings");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
index 2f276604dd912f8..622524c4fd4f8c8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-setup-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ and media settings.
 ### With Properties
 
 ```html
-<rtk-setup-screen size="md"> </rtk-setup-screen>
+<rtk-setup-screen
+ size="md">
+</rtk-setup-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-setup-screen");
+  const el = document.querySelector("rtk-setup-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
index 8902143e96624a4..f7ebcc96c331885 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-sidebar-ui component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-sidebar-ui currentTab="example"> </rtk-sidebar-ui>
+<rtk-sidebar-ui
+ currentTab="example">
+</rtk-sidebar-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-sidebar-ui");
+  const el = document.querySelector("rtk-sidebar-ui");
 
-	el.focusCloseButton = true;
-	el.hideCloseAction = true;
+  el.focusCloseButton= true;
+  el.hideCloseAction= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
index a22797273800cff..d03131c5d572243 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-sidebar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -34,14 +33,16 @@ you can customize which sections you want, and which section you want as the def
 ### With Properties
 
 ```html
-<rtk-sidebar> </rtk-sidebar>
+<rtk-sidebar>
+</rtk-sidebar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-sidebar");
+  const el = document.querySelector("rtk-sidebar");
 
-	el.enabledSections = [];
-	el.meeting = meeting;
+  el.enabledSections= [];
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
index 1614ba1605368b3..222b8ffafe1e97e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-simple-grid component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ A grid component which renders only the participants in a simple grid.
 ### With Properties
 
 ```html
-<rtk-simple-grid aspectRatio="example"> </rtk-simple-grid>
+<rtk-simple-grid
+ aspectRatio="example">
+</rtk-simple-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-simple-grid");
+  const el = document.querySelector("rtk-simple-grid");
 
-	el.gap = 42;
-	el.meeting = meeting;
+  el.gap= 42;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
index ee3244f04afe45c..1c3c4ff1ad54559 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
@@ -5,28 +5,26 @@ description: API reference for rtk-speaker-selector component (Web Components (H
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -39,13 +37,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-speaker-selector size="md"> </rtk-speaker-selector>
+<rtk-speaker-selector
+ size="md">
+</rtk-speaker-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-speaker-selector");
+  const el = document.querySelector("rtk-speaker-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
index 729aa072d8e8358..1b2a10a9aa431a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spinner component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -26,11 +25,15 @@ A component which shows an animating spinner.
 ### With Properties
 
 ```html
-<rtk-spinner size="md"> </rtk-spinner>
+<rtk-spinner
+ size="md">
+</rtk-spinner>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spinner");
+  const el = document.querySelector("rtk-spinner");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
index 0aba1ad132414cc..feaee337d8349f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
@@ -5,29 +5,27 @@ description: API reference for rtk-spotlight-grid component (Web Components (HTM
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,13 +38,17 @@ You can customize the layout to a `column` view, by default is is `row`.
 ### With Properties
 
 ```html
-<rtk-spotlight-grid aspectRatio="example" gridSize="md"> </rtk-spotlight-grid>
+<rtk-spotlight-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-spotlight-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spotlight-grid");
+  const el = document.querySelector("rtk-spotlight-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
index db3971dcecc6fba..fb0fcf76dbe0835 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spotlight-indicator component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-spotlight-indicator size="md"> </rtk-spotlight-indicator>
+<rtk-spotlight-indicator
+ size="md">
+</rtk-spotlight-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spotlight-indicator");
+  const el = document.querySelector("rtk-spotlight-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
index 99bc88ba74ef425..0f37d1d696ab3f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-stage component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ the `grid` and `sidebar` components.
 ### With Properties
 
 ```html
-<rtk-stage> </rtk-stage>
+<rtk-stage>
+</rtk-stage>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-stage");
+  const el = document.querySelector("rtk-stage");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
index cd5071fb1a445d1..899e19c8037f8c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-switch component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ A switch component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-switch> </rtk-switch>
+<rtk-switch>
+</rtk-switch>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-switch");
+  const el = document.querySelector("rtk-switch");
 
-	el.checked = true;
-	el.disabled = true;
-	el.readonly = true;
+  el.checked= true;
+  el.disabled= true;
+  el.readonly= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
index 0eb2929868dce57..37b7c05e987b351 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-tab-bar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-tab-bar> </rtk-tab-bar>
+<rtk-tab-bar>
+</rtk-tab-bar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-tab-bar");
+  const el = document.querySelector("rtk-tab-bar");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
index 22603bbe1ca64f7..47adf5034bc93ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-text-composer-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders a text composer
 
 ## Properties
 
-| Property            | Type                              | Required | Default           | Description                                   |
-| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
-| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
-| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
-| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
-| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
-| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
-| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
-| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
-| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
-| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `placeholder` | `string` | ✅ | - | Placeholder text |
+| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
+| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `value` | `string` | ✅ | - | Default value for text input |
 
 ## Usage Examples
 
@@ -33,14 +32,16 @@ A component which renders a text composer
 ### With Properties
 
 ```html
-<rtk-text-composer-view> </rtk-text-composer-view>
+<rtk-text-composer-view>
+</rtk-text-composer-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-composer-view");
+  const el = document.querySelector("rtk-text-composer-view");
 
-	el.disabled = true;
-	el.maxLength = 42;
+  el.disabled= true;
+  el.maxLength= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
index c7802ea87ac4cbc..4e15cd5f1fcdb7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-text-message-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message-view text="example"> </rtk-text-message-view>
+<rtk-text-message-view
+ text="example">
+</rtk-text-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-message-view");
+  const el = document.querySelector("rtk-text-message-view");
 
-	el.isMarkdown = true;
+  el.isMarkdown= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
index db080a025087bed..6163072c5b51c71 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-text-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message> </rtk-text-message>
+<rtk-text-message>
+</rtk-text-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-message");
+  const el = document.querySelector("rtk-text-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
index ff346f3104717b1..6e38e8bb3887731 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-tooltip component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
@@ -32,14 +31,16 @@ Tooltip component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-tooltip> </rtk-tooltip>
+<rtk-tooltip>
+</rtk-tooltip>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-tooltip");
+  const el = document.querySelector("rtk-tooltip");
 
-	el.delay = 42;
-	el.disabled = true;
+  el.delay= 42;
+  el.disabled= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
index 5ed0883121e7db1..f0631ca86b905bd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-transcript component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ You need to remove the element after you receive the
 ### With Properties
 
 ```html
-<rtk-transcript transcript="example"> </rtk-transcript>
+<rtk-transcript
+ transcript="example">
+</rtk-transcript>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-transcript");
+  const el = document.querySelector("rtk-transcript");
 
-	el.transcript = {};
+  el.transcript= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
index c734652bd0fbcd1..f75a986f1cfd9de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-transcripts component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,15 @@ There are also certain limits which you can set as well.
 ### With Properties
 
 ```html
-<rtk-transcripts> </rtk-transcripts>
+<rtk-transcripts>
+</rtk-transcripts>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-transcripts");
+  const el = document.querySelector("rtk-transcripts");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
index 3387ed120b39d4e..041148907fcb623 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ui-provider component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-ui-provider> </rtk-ui-provider>
+<rtk-ui-provider>
+</rtk-ui-provider>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ui-provider");
+  const el = document.querySelector("rtk-ui-provider");
 
-	el.config = defaultUiConfig;
-	el.mode = meeting;
-	el.showSetupScreen = true;
+  el.config= defaultUiConfig
+  el.mode= meeting
+  el.showSetupScreen= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
index 42c4225721997e0..4d041852272b5c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-viewer-count component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-viewer-count variant="primary"> </rtk-viewer-count>
+<rtk-viewer-count
+ variant="primary">
+</rtk-viewer-count>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-viewer-count");
+  const el = document.querySelector("rtk-viewer-count");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
index d551b47a44c6b52..9856cd393b4f8d3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-virtualized-participant-list component (Web C
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
@@ -27,14 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-virtualized-participant-list> </rtk-virtualized-participant-list>
+<rtk-virtualized-participant-list>
+</rtk-virtualized-participant-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-virtualized-participant-list");
+  const el = document.querySelector("rtk-virtualized-participant-list");
 
-	el.bufferedItemsCount = 42;
-	el.itemHeight = 42;
+  el.bufferedItemsCount= 42;
+  el.itemHeight= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
index f65c231d33c3ab5..5486f52a36737c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-waiting-screen component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-waiting-screen> </rtk-waiting-screen>
+<rtk-waiting-screen>
+</rtk-waiting-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-waiting-screen");
+  const el = document.querySelector("rtk-waiting-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
index 248a49136afe991..301d8b7d3bff009 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
@@ -10,11 +10,11 @@ A pressable menu item within a menu.
 
 ## Properties
 
-| Property   | Type                           | Required | Default | Description            |
-| ---------- | ------------------------------ | -------- | ------- | ---------------------- |
-| `children` | `ReactNode`                    | ✅       | -       | Menu item content      |
-| `onClick`  | `(ev) => {}`                   | ❌       | -       | Press handler callback |
-| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'` | ❌       | -       | Size variant           |
+| Property   | Type                                  | Required | Default | Description            |
+| ---------- | ------------------------------------- | -------- | ------- | ---------------------- |
+| `children` | `ReactNode`                           | ✅       | -       | Menu item content      |
+| `onClick`  | `(ev) => {}` | ❌       | -       | Press handler callback |
+| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'`        | ❌       | -       | Size variant           |
 
 ## Usage Examples
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
index 422840190bc663c..0ec727fad6c4379 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkAi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAi } from "@cloudflare/realtimekit-react-ui";
+import { RtkAi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAi />;
+  return <RtkAi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAi } from "@cloudflare/realtimekit-react-ui";
+import { RtkAi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAi meeting={meeting} size="md" view={aiview} />;
+  return (
+    <RtkAi
+      meeting={meeting}
+      size="md"
+      view={aiview}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
index 396561410fcfa72..8545071a098a60f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkAiToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiToggle />;
+  return <RtkAiToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkAiToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
index 676a14f2675ae81..ef4f69f64146916 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
@@ -5,33 +5,38 @@ description: API reference for RtkAiTranscriptions component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiTranscriptions />;
+  return <RtkAiTranscriptions />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiTranscriptions initialTranscriptions={[]} meeting={meeting} />;
+  return (
+    <RtkAiTranscriptions
+      initialTranscriptions={[]}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
index 75ece5db8d70097..5a8f8fedf34406a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
@@ -5,39 +5,43 @@ description: API reference for RtkAudioGrid component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioGrid />;
+  return <RtkAudioGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioGrid config={defaultUiConfig} hideSelf={true} meeting={meeting} />
-	);
+  return (
+    <RtkAudioGrid
+      config={defaultUiConfig}
+      hideSelf={true}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
index 5c8a03c08f715b6..71a65e966b788a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkAudioTile component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioTile />;
+  return <RtkAudioTile />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioTile
-			config={defaultUiConfig}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkAudioTile
+      config={defaultUiConfig}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
index 33a40cf994b8247..9f5b3941640b98a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkAudioVisualizer component (React Library)
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioVisualizer />;
+  return <RtkAudioVisualizer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioVisualizer
-			hideMuted={true}
-			isScreenShare={true}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkAudioVisualizer
+      hideMuted={true}
+      isScreenShare={true}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
index b48ab891f56912c..0e6ffdb430de443 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkAvatar component (React Library)
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
+import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAvatar />;
+  return <RtkAvatar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
+import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAvatar participant="example" size="md" variant="circular" />;
+  return (
+    <RtkAvatar
+      participant="example"
+      size="md"
+      variant="circular"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
index a8884efc78197e3..487dc6287788cc7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkBreakoutRoomManager component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomManager />;
+  return <RtkBreakoutRoomManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomManager
-			allowDelete={true}
-			assigningParticipants={true}
-			defaultExpanded={true}
-		/>
-	);
+  return (
+    <RtkBreakoutRoomManager
+      allowDelete={true}
+      assigningParticipants={true}
+      defaultExpanded={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
index 2004a147afe14a6..fb2341581602302 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkBreakoutRoomParticipants component (React Libr
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomParticipants />;
+  return <RtkBreakoutRoomParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomParticipants
-			meeting={meeting}
-			participantIds="example"
-			selectedParticipantIds="example"
-		/>
-	);
+  return (
+    <RtkBreakoutRoomParticipants
+      meeting={meeting}
+      participantIds="example"
+      selectedParticipantIds="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
index dcbcea2d4770056..50f3260dcf7a651 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkBreakoutRoomsManager component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsManager />;
+  return <RtkBreakoutRoomsManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsManager meeting={meeting} />;
+  return (
+    <RtkBreakoutRoomsManager
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
index 437ddd1710ebf57..380c96f9f1541ef 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkBreakoutRoomsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsToggle />;
+  return <RtkBreakoutRoomsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomsToggle
-			iconPack={defaultIconPack}
-			meeting={meeting}
-			size="md"
-		/>
-	);
+  return (
+    <RtkBreakoutRoomsToggle
+      iconPack={defaultIconPack}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
index 2117f12536528dd..856b11cff1b3d13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkBroadcastMessageModal component (React Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBroadcastMessageModal />;
+  return <RtkBroadcastMessageModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBroadcastMessageModal meeting={meeting} />;
+  return (
+    <RtkBroadcastMessageModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
index 4662a4cb4703613..5be7a8515fbc268 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
@@ -5,38 +5,44 @@ description: API reference for RtkButton component (React Library)
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkButton />;
+  return <RtkButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkButton disabled={true} kind={buttonkind} reverse={true} />;
+  return (
+    <RtkButton
+      disabled={true}
+      kind={buttonkind}
+      reverse={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
index 5bd7f5725ed45f5..5964ca5795dff5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
@@ -5,52 +5,51 @@ description: API reference for RtkCameraSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraSelector />;
+  return <RtkCameraSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkCameraSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkCameraSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
index ef0f7be9cbd784b..f32d538b0d242cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCameraToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your camera.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraToggle />;
+  return <RtkCameraToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkCameraToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
index ccb44bea4849232..4e5a7b0e9ae81e2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCaptionToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCaptionToggle />;
+  return <RtkCaptionToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCaptionToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkCaptionToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
index 88044716a737a05..08109cd1a6900d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkChat component (React Library)
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChat } from "@cloudflare/realtimekit-react-ui";
+import { RtkChat } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChat />;
+  return <RtkChat />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChat } from "@cloudflare/realtimekit-react-ui";
+import { RtkChat } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChat meeting={meeting} size="md" />;
+  return (
+    <RtkChat
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
index f71eb84400228a3..3c8a6961bebc260 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkChatComposerUi component (React Library)
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatComposerUi />;
+  return <RtkChatComposerUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatComposerUi
-			canSendFiles={true}
-			canSendTextMessage={true}
-			size="md"
-		/>
-	);
+  return (
+    <RtkChatComposerUi
+      canSendFiles={true}
+      canSendTextMessage={true}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
index 3f5eabaf3bbce7c..2ebfa2b0d2a24e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
@@ -5,49 +5,49 @@ description: API reference for RtkChatComposerView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatComposerView />;
+  return <RtkChatComposerView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatComposerView
-			canSendFiles={true}
-			canSendTextMessage={true}
-			inputTextPlaceholder="example"
-		/>
-	);
+  return (
+    <RtkChatComposerView
+      canSendFiles={true}
+      canSendTextMessage={true}
+      inputTextPlaceholder="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
index 172ac6463eae729..b8d221aa00d5d75 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
@@ -5,19 +5,19 @@ description: API reference for RtkChatHeader component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatHeader />;
+  return <RtkChatHeader />;
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
index 06b7622778baee0..62095db66fa56ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
@@ -5,49 +5,55 @@ description: API reference for RtkChatMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessage />;
+  return <RtkChatMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessage alignRight={true} canDelete={true} canEdit={true} />;
+  return (
+    <RtkChatMessage
+      alignRight={true}
+      canDelete={true}
+      canEdit={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
index 24dfa75d1e264c5..39be829497f47dc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkChatMessagesUi component (React Library)
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessagesUi />;
+  return <RtkChatMessagesUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatMessagesUi
-			canPinMessages={true}
-			messages={[]}
-			selectedGroup="example"
-		/>
-	);
+  return (
+    <RtkChatMessagesUi
+      canPinMessages={true}
+      messages={[]}
+      selectedGroup="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
index 5891af64b276945..2050ab5a26bc247 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkChatMessagesUiPaginated component (React Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessagesUiPaginated />;
+  return <RtkChatMessagesUiPaginated />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatMessagesUiPaginated
-			meeting={meeting}
-			privateChatRecipient={participant | null}
-			size="md"
-		/>
-	);
+  return (
+    <RtkChatMessagesUiPaginated
+      meeting={meeting}
+      privateChatRecipient={participant | null}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
index 7b498cd1db28fe1..8218e3a1de98dcc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkChatSearchResults component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSearchResults />;
+  return <RtkChatSearchResults />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatSearchResults
-			channelId="example"
-			meeting={meeting}
-			query="example"
-		/>
-	);
+  return (
+    <RtkChatSearchResults
+      channelId="example"
+      meeting={meeting}
+      query="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
index 377f279bef2cd5e..d57247e25b7d5f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkChatSelector component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelector />;
+  return <RtkChatSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelector meeting={meeting} size="md" />;
+  return (
+    <RtkChatSelector
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
index 883fee41a51d0de..780c0f8d5ddc863 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkChatSelectorUi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelectorUi />;
+  return <RtkChatSelectorUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatSelectorUi
-			groups={[]}
-			selectedGroupId="example"
-			selfUserId="example"
-		/>
-	);
+  return (
+    <RtkChatSelectorUi
+      groups={[]}
+      selectedGroupId="example"
+      selfUserId="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
index 23fa8dea93d070a..93bb6e482beaa63 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
@@ -5,47 +5,49 @@ description: API reference for RtkChatToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of chat.
-You need to pass the `meeting` object to it to see the unread messages count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "chat";
-}
-```
+ You need to pass the `meeting` object to it to see the unread messages count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'chat' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatToggle />;
+  return <RtkChatToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkChatToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
index 6671c8edffa9090..5b51f5833c33a3f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkClock component (React Library)
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkClock } from "@cloudflare/realtimekit-react-ui";
+import { RtkClock } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkClock />;
+  return <RtkClock />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkClock } from "@cloudflare/realtimekit-react-ui";
+import { RtkClock } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkClock meeting={meeting} size="md" />;
+  return (
+    <RtkClock
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
index 31eb8135db4c518..03354726cb31f89 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
@@ -5,36 +5,40 @@ description: API reference for RtkConfirmationModal component (React Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkConfirmationModal />;
+  return <RtkConfirmationModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkConfirmationModal meeting={meeting} />;
+  return (
+    <RtkConfirmationModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
index 70878abe0db3e5a..23812e3db206ab2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkControlbar component (React Library)
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbar />;
+  return <RtkControlbar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbar disableRender={true} meeting={meeting} size="md" />;
+  return (
+    <RtkControlbar
+      disableRender={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
index d9027e6aa0875b4..d0e6e508caf9480 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
@@ -5,43 +5,47 @@ description: API reference for RtkControlbarButton component (React Library)
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbarButton />;
+  return <RtkControlbarButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkControlbarButton brandIcon={true} disabled={true} icon="example" />
-	);
+  return (
+    <RtkControlbarButton
+      brandIcon={true}
+      disabled={true}
+      icon="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
index 2f691f8771858ee..7b619a1539d261f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCounter component (React Library)
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
+import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCounter />;
+  return <RtkCounter />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
+import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCounter minValue={42} size="md" value={42} />;
+  return (
+    <RtkCounter
+      minValue={42}
+      size="md"
+      value={42}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
index e50a8ecb11348d8..f053eb720bed15d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkDebugger component (React Library)
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebugger />;
+  return <RtkDebugger />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebugger meeting={meeting} size="md" />;
+  return (
+    <RtkDebugger
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
index e3b258be377ed38..7dc5d08497e8bd7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerAudio component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerAudio />;
+  return <RtkDebuggerAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerAudio meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerAudio
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
index 62053832f219996..84e96a1f71fb63a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerScreenshare component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerScreenshare />;
+  return <RtkDebuggerScreenshare />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerScreenshare meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerScreenshare
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
index fa2fc78d58a6309..351882399cc12df 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerSystem component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerSystem />;
+  return <RtkDebuggerSystem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerSystem meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerSystem
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
index 5e693f7e36fb65e..a31dd78c42d4145 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkDebuggerToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerToggle />;
+  return <RtkDebuggerToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkDebuggerToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
index f5819d9caac23ff..c74f2cb9062572f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerVideo component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerVideo />;
+  return <RtkDebuggerVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerVideo meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerVideo
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
index 46fbf93818f24f8..fe104ba37211c2a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkDialog component (React Library)
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialog />;
+  return <RtkDialog />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkDialog
-			disableEscapeKey={true}
-			hideCloseButton={true}
-			meeting={meeting}
-		/>
-	);
+  return (
+    <RtkDialog
+      disableEscapeKey={true}
+      hideCloseButton={true}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
index 736b239555dd6c7..61ee80cd7643468 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
@@ -5,45 +5,49 @@ description: API reference for RtkDialogManager component (React Library)
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialogManager />;
+  return <RtkDialogManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialogManager meeting={meeting} size="md" />;
+  return (
+    <RtkDialogManager
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
index 90c0d95b4208a0a..a5285022bbe30c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkDraftAttachmentView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property     | Type                                                 | Required | Default           | Description           |
-| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
-| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
-| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
+import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDraftAttachmentView />;
+  return <RtkDraftAttachmentView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
+import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDraftAttachmentView attachment={{}} />;
+  return (
+    <RtkDraftAttachmentView
+      attachment={{}}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
index 8a0e1b654ee40a0..c43046ea84826be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkEmojiPicker component (React Library)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPicker />;
+  return <RtkEmojiPicker />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPicker focusWhenOpened={true} />;
+  return (
+    <RtkEmojiPicker
+      focusWhenOpened={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
index dd15556f86ad2a2..fb41c2305bae5b8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkEmojiPickerButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPickerButton />;
+  return <RtkEmojiPickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPickerButton isActive={true} />;
+  return (
+    <RtkEmojiPickerButton
+      isActive={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
index 9e06d6de13b10ac..f5d34bcb49b8d47 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkEndedScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEndedScreen />;
+  return <RtkEndedScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEndedScreen meeting={meeting} size="md" />;
+  return (
+    <RtkEndedScreen
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
index d000f71a09a18c4..249558fdf892cff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkFileDropzone component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileDropzone />;
+  return <RtkFileDropzone />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileDropzone hostEl={htmlelement} />;
+  return (
+    <RtkFileDropzone
+      hostEl={htmlelement}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
index 0d763747bc4f21b..160e6d45a1c3e0d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkFileMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessage />;
+  return <RtkFileMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessage isContinued={true} message={filemessage} now={date} />;
+  return (
+    <RtkFileMessage
+      isContinued={true}
+      message={filemessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
index 64098e714003e5e..baf330586b09a46 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkFileMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessageView />;
+  return <RtkFileMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessageView name="example" size={42} url="example" />;
+  return (
+    <RtkFileMessageView
+      name="example"
+      size={42}
+      url="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
index f495c13464a820e..7695557d4ce9b2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkFilePickerButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFilePickerButton />;
+  return <RtkFilePickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkFilePickerButton
-			filter="example"
-			icon={defaultIconPack}
-			label="example"
-		/>
-	);
+  return (
+    <RtkFilePickerButton
+      filter="example"
+      icon={defaultIconPack}
+      label="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
index 0abc92d640e427b..4dfd50432f2e792 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkFullscreenToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles full screen mode for any
-existing `rtk-meeting` component in the DOM.
+ existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                  |
-| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
-| `size`          | `Size`              | ✅       | -                 | Size                         |
-| `states`        | `States`            | ✅       | -                 | States object                |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
-| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
-| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFullscreenToggle />;
+  return <RtkFullscreenToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkFullscreenToggle
-			size="md"
-			targetElement={htmlelement}
-			variant="button"
-		/>
-	);
+  return (
+    <RtkFullscreenToggle
+      size="md"
+      targetElement={htmlelement}
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
index f927f0f83579df1..ba09d23bb59421f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
@@ -5,43 +5,49 @@ description: API reference for RtkGrid component (React Library)
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGrid />;
+  return <RtkGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
index 2ec869ec68a635d..5f237bf642f2544 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkGridPagination component (React Library)
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
+import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGridPagination />;
+  return <RtkGridPagination />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
+import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkGridPagination
-			meeting={meeting}
-			size="md"
-			variant={gridpaginationvariants}
-		/>
-	);
+  return (
+    <RtkGridPagination
+      meeting={meeting}
+      size="md"
+      variant={gridpaginationvariants}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
index ae22b18378bd4c7..10ccda38fa97f7e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkHeader component (React Library)
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkHeader />;
+  return <RtkHeader />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkHeader disableRender={true} meeting={meeting} size="md" />;
+  return (
+    <RtkHeader
+      disableRender={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
index 16a092f54b2dbce..f7283d6288d99a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkIcon component (React Library)
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
+import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIcon />;
+  return <RtkIcon />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
+import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIcon icon="example" size="md" variant="primary" />;
+  return (
+    <RtkIcon
+      icon="example"
+      size="md"
+      variant="primary"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
index c1bb80f2c5f6df1..673fc18b193b110 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkIdleScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIdleScreen />;
+  return <RtkIdleScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIdleScreen meeting={meeting} />;
+  return (
+    <RtkIdleScreen
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
index 55513c0267caef0..8c0288f2c73bdea 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
@@ -5,41 +5,45 @@ description: API reference for RtkImageMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessage />;
+  return <RtkImageMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkImageMessage isContinued={true} message={imagemessage} now={date} />
-	);
+  return (
+    <RtkImageMessage
+      isContinued={true}
+      message={imagemessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
index 7bbc3cd4d39a23a..c780f5404911db6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkImageMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessageView />;
+  return <RtkImageMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessageView url="example" />;
+  return (
+    <RtkImageMessageView
+      url="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
index 9df4c2bb772122b..91083a36a5cc7cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkImageViewer component (React Library)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageViewer />;
+  return <RtkImageViewer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageViewer image={imagemessage} size="md" />;
+  return (
+    <RtkImageViewer
+      image={imagemessage}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
index 59bb5a4a42279d0..0fbe8b295b4e90a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
@@ -5,31 +5,35 @@ description: API reference for RtkInformationTooltip component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkInformationTooltip />;
+  return <RtkInformationTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkInformationTooltip iconPack={defaultIconPack} />;
+  return (
+    <RtkInformationTooltip
+      iconPack={defaultIconPack}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
index cb2514eb8f698d8..980d877c6c2be1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
@@ -5,39 +5,43 @@ description: API reference for RtkJoinStage component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkJoinStage />;
+  return <RtkJoinStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkJoinStage dataConfig={modaldataconfig} meeting={meeting} size="md" />
-	);
+  return (
+    <RtkJoinStage
+      dataConfig={modaldataconfig}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
index bd0118ecce5e460..cbadd40c668ffb5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkLeaveButton component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description |
-| ---------- | ------------------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size`              | ✅       | -                 | Size        |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveButton />;
+  return <RtkLeaveButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveButton size="md" variant="button" />;
+  return (
+    <RtkLeaveButton
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
index caaa57aa9b7489a..381df4d5a32d9a8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkLeaveMeeting component (React Library)
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveMeeting />;
+  return <RtkLeaveMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveMeeting meeting={meeting} />;
+  return (
+    <RtkLeaveMeeting
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
index f32e008ce30ba45..c460afe367c3aba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkLivestreamIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamIndicator />;
+  return <RtkLivestreamIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkLivestreamIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
index 76bcbcc4f131e9b..f2825122178db2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkLivestreamPlayer component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamPlayer />;
+  return <RtkLivestreamPlayer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamPlayer meeting={meeting} size="md" />;
+  return (
+    <RtkLivestreamPlayer
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
index bbc41afc7185d64..5a02a6110c65ab6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkLivestreamToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamToggle />;
+  return <RtkLivestreamToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkLivestreamToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
index 9477a16d30710b5..eb4e53ce7220d26 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkLogo component (React Library)
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
+import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLogo />;
+  return <RtkLogo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
+import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLogo logoUrl="example" meeting={meeting} />;
+  return (
+    <RtkLogo
+      logoUrl="example"
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
index 55fbf4dd7de4c88..b4a60b36bb5affb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
@@ -5,32 +5,37 @@ description: API reference for RtkMarkdownView component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMarkdownView />;
+  return <RtkMarkdownView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMarkdownView maxLength={42} text="example" />;
+  return (
+    <RtkMarkdownView
+      maxLength={42}
+      text="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
index fc2ab8e84fcd5de..46f187b5651c348 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
@@ -5,53 +5,53 @@ description: API reference for RtkMeeting component (React Library)
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeeting />;
+  return <RtkMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMeeting
-			applyDesignSystem={true}
-			config={defaultUiConfig}
-			gridLayout={gridlayout1}
-		/>
-	);
+  return (
+    <RtkMeeting
+      applyDesignSystem={true}
+      config={defaultUiConfig}
+      gridLayout={gridlayout1}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
index 8e26823a9775b15..390e091d34851d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkMeetingTitle component (React Library)
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeetingTitle />;
+  return <RtkMeetingTitle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeetingTitle meeting={meeting} />;
+  return (
+    <RtkMeetingTitle
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
index 9ee83f7cee4ea0a..5f5db9ac9f51c5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkMenu component (React Library)
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenu />;
+  return <RtkMenu />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenu offset={42} placement={placement} size="md" />;
+  return (
+    <RtkMenu
+      offset={42}
+      placement={placement}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
index e3ed88af47b32ff..07d2090f6869fa5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkMenuItem component (React Library)
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuItem />;
+  return <RtkMenuItem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuItem menuVariant={"primary" | "secondary"} size="md" />;
+  return (
+    <RtkMenuItem
+      menuVariant={'primary' | 'secondary'}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
index c8535a1fd33ef85..3abcdf3681cf82c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkMenuList component (React Library)
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuList />;
+  return <RtkMenuList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuList menuVariant={"primary" | "secondary"} />;
+  return (
+    <RtkMenuList
+      menuVariant={'primary' | 'secondary'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
index 80a9a91264a8c83..a821d60dd934f37 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkMessageView component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMessageView />;
+  return <RtkMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMessageView actions={[]} authorName="example" avatarUrl="example" />
-	);
+  return (
+    <RtkMessageView
+      actions={[]}
+      authorName="example"
+      avatarUrl="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
index cc03a1979681184..8a828fa1df70a57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkMicToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your microphone.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicToggle />;
+  return <RtkMicToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkMicToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
index bddd6410870b69d..7635bf3bc850417 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
@@ -5,52 +5,51 @@ description: API reference for RtkMicrophoneSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicrophoneSelector />;
+  return <RtkMicrophoneSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMicrophoneSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkMicrophoneSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
index 2a84e600445f8a4..9797cef0997f626 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
@@ -5,46 +5,52 @@ description: API reference for RtkMixedGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMixedGrid />;
+  return <RtkMixedGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMixedGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkMixedGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
index ec75917e7d6794f..2c8f9d6008454df 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
@@ -5,43 +5,44 @@ description: API reference for RtkMoreToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMoreToggle />;
+  return <RtkMoreToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMoreToggle size="md" />;
+  return (
+    <RtkMoreToggle
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
index 9ff1d6062e97f3a..0a61a27b14d57cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkMuteAllButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllButton />;
+  return <RtkMuteAllButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllButton meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkMuteAllButton
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
index de60763a8da782a..6964b04a06fce07 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkMuteAllConfirmation component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllConfirmation />;
+  return <RtkMuteAllConfirmation />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllConfirmation meeting={meeting} />;
+  return (
+    <RtkMuteAllConfirmation
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
index b24255b2688e80e..653d3e71c13c219 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkNameTag component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
+import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNameTag />;
+  return <RtkNameTag />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
+import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNameTag
-			isScreenShare={true}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkNameTag
+      isScreenShare={true}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
index badca357da7d298..cdc9b9d26f6014c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkNetworkIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNetworkIndicator />;
+  return <RtkNetworkIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNetworkIndicator
-			isScreenShare={true}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkNetworkIndicator
+      isScreenShare={true}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
index 5aecde35407d99b..011b505c0f96d15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
@@ -5,41 +5,45 @@ description: API reference for RtkNotification component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotification />;
+  return <RtkNotification />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNotification notification={notification} paused={true} size="md" />
-	);
+  return (
+    <RtkNotification
+      notification={notification}
+      paused={true}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
index b4cf3563bdaf55e..a6479a63c2b3dc3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
@@ -5,40 +5,45 @@ description: API reference for RtkNotifications component (React Library)
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotifications />;
+  return <RtkNotifications />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotifications meeting={meeting} size="md" />;
+  return (
+    <RtkNotifications
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
index f4a1c236a9e1ff3..075d2ad41e4e7f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
@@ -5,36 +5,40 @@ description: API reference for RtkOverlayModal component (React Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkOverlayModal />;
+  return <RtkOverlayModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkOverlayModal meeting={meeting} />;
+  return (
+    <RtkOverlayModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
index 4efdfe198d33ae2..9c2aa7dd5fa68fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkPaginatedList component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
+import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPaginatedList />;
+  return <RtkPaginatedList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
+import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkPaginatedList
-			autoScroll={true}
-			createNodes={[]}
-			emptyListLabel="example"
-		/>
-	);
+  return (
+    <RtkPaginatedList
+      autoScroll={true}
+      createNodes={[]}
+      emptyListLabel="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
index 516579dd9a334b1..ccc8cb4e191bc51 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkParticipant component (React Library)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipant />;
+  return <RtkParticipant />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipant
-			meeting={meeting}
-			participant={participant}
-			view={participantviewmode}
-		/>
-	);
+  return (
+    <RtkParticipant
+      meeting={meeting}
+      participant={participant}
+      view={participantviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
index 328f0c14986aba0..e8cd175555dcd38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkParticipantCount component (React Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantCount />;
+  return <RtkParticipantCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantCount meeting={meeting} size="md" />;
+  return (
+    <RtkParticipantCount
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
index 91ef45fb563d602..7606fca272f529b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkParticipants component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipants />;
+  return <RtkParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipants
-			defaultParticipantsTabId={participantstabid}
-			meeting={meeting}
-			size="md"
-		/>
-	);
+  return (
+    <RtkParticipants
+      defaultParticipantsTabId={participantstabid}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
index b758d16591fc32d..8ef488005d52a27 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkParticipantsAudio component (React Library)
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsAudio />;
+  return <RtkParticipantsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsAudio
-			meeting={meeting}
-			preloadedAudioElem={htmlaudioelement}
-		/>
-	);
+  return (
+    <RtkParticipantsAudio
+      meeting={meeting}
+      preloadedAudioElem={htmlaudioelement}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
index 135d60ff19db841..b00d785b2acf701 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkParticipantsStageList component (React Library
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsStageList />;
+  return <RtkParticipantsStageList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsStageList
-			hideHeader={true}
-			meeting={meeting}
-			search="example"
-		/>
-	);
+  return (
+    <RtkParticipantsStageList
+      hideHeader={true}
+      meeting={meeting}
+      search="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
index 8528f80bb052dd6..4e41381ce80f30a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsStageQueue component (React Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsStageQueue />;
+  return <RtkParticipantsStageQueue />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsStageQueue
-			meeting={meeting}
-			size="md"
-			view={participantsviewmode}
-		/>
-	);
+  return (
+    <RtkParticipantsStageQueue
+      meeting={meeting}
+      size="md"
+      view={participantsviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
index 0301d934942ee7a..9c8fdaf5ece9fe4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
@@ -5,46 +5,48 @@ description: API reference for RtkParticipantsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of participants.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "participants";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'participants' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsToggle />;
+  return <RtkParticipantsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkParticipantsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
index a8153f7ffc87a99..2122d23e95a3666 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkParticipantsViewerList component (React Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsViewerList />;
+  return <RtkParticipantsViewerList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsViewerList
-			hideHeader={true}
-			meeting={meeting}
-			search="example"
-		/>
-	);
+  return (
+    <RtkParticipantsViewerList
+      hideHeader={true}
+      meeting={meeting}
+      search="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
index 4649b0bfc0e82fd..3a889887010026a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsWaitingList component (React Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsWaitingList />;
+  return <RtkParticipantsWaitingList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsWaitingList
-			meeting={meeting}
-			size="md"
-			view={participantsviewmode}
-		/>
-	);
+  return (
+    <RtkParticipantsWaitingList
+      meeting={meeting}
+      size="md"
+      view={participantsviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
index d775d0fe83a22f1..3772370f932a5c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkPermissionsMessage component (React Library)
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPermissionsMessage />;
+  return <RtkPermissionsMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPermissionsMessage meeting={meeting} />;
+  return (
+    <RtkPermissionsMessage
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
index 3204dca64827f0c..6ec7ca9cc8718b2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkPinnedMessageSelector component (React Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPinnedMessageSelector />;
+  return <RtkPinnedMessageSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPinnedMessageSelector meeting={meeting} />;
+  return (
+    <RtkPinnedMessageSelector
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
index 7fa13266f256c40..2c97be980f7bfe7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkPipToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPipToggle />;
+  return <RtkPipToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPipToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPipToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
index c3e69d48c2363ad..558894132225b7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkPluginMain component (React Library)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginMain />;
+  return <RtkPluginMain />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginMain meeting={meeting} plugin={rtkplugin} />;
+  return (
+    <RtkPluginMain
+      meeting={meeting}
+      plugin={rtkplugin}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
index d965a8cd11d84f3..6deb86e4607c003 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkPlugins component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
+import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPlugins />;
+  return <RtkPlugins />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
+import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPlugins meeting={meeting} size="md" />;
+  return (
+    <RtkPlugins
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
index ea36e607b88f055..68b70c406caf1cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
@@ -5,46 +5,48 @@ description: API reference for RtkPluginsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of plugins.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "plugins";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'plugins' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginsToggle />;
+  return <RtkPluginsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPluginsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
index 3005624ec80b0f9..aa4fe6fd115a016 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
@@ -5,40 +5,44 @@ description: API reference for RtkPoll component (React Library)
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
+import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPoll />;
+  return <RtkPoll />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
+import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkPoll permissions={rtkpermissionspreset} poll={poll} self="example" />
-	);
+  return (
+    <RtkPoll
+      permissions={rtkpermissionspreset}
+      poll={poll}
+      self="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
index e875461eed40218..83cc1ae5190f3c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkPollForm component (React Library)
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollForm />;
+  return <RtkPollForm />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollForm iconPack={defaultIconPack} t={rtki18n} />;
+  return (
+    <RtkPollForm
+      iconPack={defaultIconPack}
+      t={rtki18n}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
index d6c56afb6b26cca..4277a2b47bfdace 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkPolls component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
+import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPolls />;
+  return <RtkPolls />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
+import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPolls meeting={meeting} size="md" />;
+  return (
+    <RtkPolls
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
index ce797b91301661d..f50a1cdaceb586b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
@@ -5,47 +5,49 @@ description: API reference for RtkPollsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of polls.
-You need to pass the `meeting` object to it to see the unread polls count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "polls";
-}
-```
+ You need to pass the `meeting` object to it to see the unread polls count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'polls' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollsToggle />;
+  return <RtkPollsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPollsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
index 80fd74b508c85d2..5c2762db23494d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkRecordingIndicator component (React Library)
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingIndicator />;
+  return <RtkRecordingIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkRecordingIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
index 37ff40da4c4e3e2..0f80e38da1040bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
@@ -5,41 +5,47 @@ description: API reference for RtkRecordingToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingToggle />;
+  return <RtkRecordingToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingToggle disabled={true} meeting={meeting} size="md" />;
+  return (
+    <RtkRecordingToggle
+      disabled={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
index f2af8f3196dc19e..52908befd7de5b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
@@ -5,38 +5,44 @@ description: API reference for RtkScreenShareToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkScreenShareToggle />;
+  return <RtkScreenShareToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkScreenShareToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkScreenShareToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
index 71105173b22229f..2b52d0ae178ce6d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkSettings component (React Library)
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettings />;
+  return <RtkSettings />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettings meeting={meeting} size="md" />;
+  return (
+    <RtkSettings
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
index 3519e84e54fc498..81dfd8b2b09dd43 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkSettingsAudio component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsAudio />;
+  return <RtkSettingsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsAudio meeting={meeting} size="md" />;
+  return (
+    <RtkSettingsAudio
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
index d3a027941137787..be09e3aaa6d7c96 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
@@ -5,44 +5,46 @@ description: API reference for RtkSettingsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of settings module.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSettings: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSettings: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description   |
-| ---------- | ------------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`              | ✅       | -                 | Size          |
-| `states`   | `States`            | ✅       | -                 | States object |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsToggle />;
+  return <RtkSettingsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsToggle size="md" variant="button" />;
+  return (
+    <RtkSettingsToggle
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
index 004752677fc71bb..e8ecedcb858f5f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkSettingsVideo component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsVideo />;
+  return <RtkSettingsVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsVideo meeting={meeting} size="md" />;
+  return (
+    <RtkSettingsVideo
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
index 9425271184560e0..b7d2b949edf7209 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
@@ -5,39 +5,44 @@ description: API reference for RtkSetupScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSetupScreen />;
+  return <RtkSetupScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSetupScreen meeting={meeting} size="md" />;
+  return (
+    <RtkSetupScreen
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
index a911ce5c3815222..1304726dd69f9a7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkSidebar component (React Library)
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSidebar />;
+  return <RtkSidebar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSidebar
-			defaultSection={rtksidebarsection}
-			enabledSections={[]}
-			meeting={meeting}
-		/>
-	);
+  return (
+    <RtkSidebar
+      defaultSection={rtksidebarsection}
+      enabledSections={[]}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
index 476c5b291b984ca..01b17c6dd9ffc5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkSidebarUi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSidebarUi />;
+  return <RtkSidebarUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSidebarUi
-			currentTab="example"
-			focusCloseButton={true}
-			hideCloseAction={true}
-		/>
-	);
+  return (
+    <RtkSidebarUi
+      currentTab="example"
+      focusCloseButton={true}
+      hideCloseAction={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
index 000057d63bf902c..1a39406c2ae6fc3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
@@ -5,41 +5,47 @@ description: API reference for RtkSimpleGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSimpleGrid />;
+  return <RtkSimpleGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSimpleGrid aspectRatio="example" gap={42} meeting={meeting} />;
+  return (
+    <RtkSimpleGrid
+      aspectRatio="example"
+      gap={42}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
index 04e2e6cc9985238..ef6967aefdd7575 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
@@ -5,53 +5,52 @@ description: API reference for RtkSpeakerSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpeakerSelector />;
+  return <RtkSpeakerSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSpeakerSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkSpeakerSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
index 28454314a99f114..f465d60658ede2a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkSpinner component (React Library)
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpinner />;
+  return <RtkSpinner />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpinner size="md" />;
+  return (
+    <RtkSpinner
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
index 78418e203326306..0bf9ca54bc892c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
@@ -5,48 +5,53 @@ description: API reference for RtkSpotlightGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightGrid />;
+  return <RtkSpotlightGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkSpotlightGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
index 4777d387761bd9c..6b3cf9e708c5b27 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkSpotlightIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightIndicator />;
+  return <RtkSpotlightIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkSpotlightIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
index 317f51dde0bca13..2d45d987a733a92 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkStage component (React Library)
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStage />;
+  return <RtkStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStage iconPack={defaultIconPack} t={rtki18n} />;
+  return (
+    <RtkStage
+      iconPack={defaultIconPack}
+      t={rtki18n}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
index 348c55faae4ad7a..cb4ca66a237f1fe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkStageToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `states`   | `States1`           | ✅       | -                 | States         |
-| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStageToggle />;
+  return <RtkStageToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStageToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkStageToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
index d70d8ba438e9132..45b7bebc4f42df5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkSwitch component (React Library)
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
+import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSwitch />;
+  return <RtkSwitch />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
+import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSwitch checked={true} disabled={true} readonly={true} />;
+  return (
+    <RtkSwitch
+      checked={true}
+      disabled={true}
+      readonly={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
index d425e9836824989..4b92e54781696ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkTabBar component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
+import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTabBar />;
+  return <RtkTabBar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
+import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTabBar activeTab={tab} layout={gridlayout1} meeting={meeting} />;
+  return (
+    <RtkTabBar
+      activeTab={tab}
+      layout={gridlayout1}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
index 275064c3a0e30cf..b13d5561c20349b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkTextMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessage />;
+  return <RtkTextMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessage isContinued={true} message={textmessage} now={date} />;
+  return (
+    <RtkTextMessage
+      isContinued={true}
+      message={textmessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
index 05911d805ffcb0f..181ebc339cd53d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkTextMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessageView />;
+  return <RtkTextMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessageView isMarkdown={true} text="example" />;
+  return (
+    <RtkTextMessageView
+      isMarkdown={true}
+      text="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
index c1621ec9cec5946..d2bfb5b64eb3958 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkTooltip component (React Library)
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTooltip />;
+  return <RtkTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTooltip delay={42} disabled={true} kind={tooltipkind} />;
+  return (
+    <RtkTooltip
+      delay={42}
+      disabled={true}
+      kind={tooltipkind}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
index bbcf034ad560898..de37a7083168217 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkTranscript component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscript />;
+  return <RtkTranscript />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscript t={rtki18n} transcript="example" />;
+  return (
+    <RtkTranscript
+      t={rtki18n}
+      transcript="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
index 42bf35aa1892a1c..f0c0d8559cc445a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
@@ -5,38 +5,42 @@ description: API reference for RtkTranscripts component (React Library)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscripts />;
+  return <RtkTranscripts />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscripts meeting={meeting} />;
+  return (
+    <RtkTranscripts
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
index 539123ffabfd8ae..ae022070d0bc868 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkUiProvider component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
+import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkUiProvider />;
+  return <RtkUiProvider />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
+import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkUiProvider
-			config={defaultUiConfig}
-			mode={meeting}
-			showSetupScreen={true}
-		/>
-	);
+  return (
+    <RtkUiProvider
+      config={defaultUiConfig}
+      mode={meeting}
+      showSetupScreen={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
index 1ba972a480e5bf9..6cd926ddcacf256 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkViewerCount component (React Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkViewerCount />;
+  return <RtkViewerCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkViewerCount meeting={meeting} variant="primary" />;
+  return (
+    <RtkViewerCount
+      meeting={meeting}
+      variant="primary"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
index a0e877a59bc623a..5357ad00b4bb2f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkVirtualizedParticipantList component (React Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
+import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkVirtualizedParticipantList />;
+  return <RtkVirtualizedParticipantList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
+import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkVirtualizedParticipantList
-			bufferedItemsCount={42}
-			emptyListElement={htmlelement}
-			itemHeight={42}
-		/>
-	);
+  return (
+    <RtkVirtualizedParticipantList
+      bufferedItemsCount={42}
+      emptyListElement={htmlelement}
+      itemHeight={42}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
index 80ab41447906b03..7a88d11a1ddcc8e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkWaitingScreen component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkWaitingScreen />;
+  return <RtkWaitingScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkWaitingScreen meeting={meeting} />;
+  return (
+    <RtkWaitingScreen
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
index 484d77e089e0389..e278b3204222b09 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
index 97583e8bcbbb2dc..167875d1b34c213 100644
--- a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
+++ b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-import { Aside } from "~/components";
+import { Aside } from "~/components"
 
 ## Cloudflare Realtime vs. Traditional SFUs
 
@@ -31,10 +31,7 @@ Cloudflare Realtime addresses these limitations by leveraging Cloudflare's globa
 - **Decentralized Architecture:** There are no dedicated servers for Realtime. Every server within Cloudflare's network contributes to handling Realtime, ensuring scalability and reliability. This approach mirrors the distributed nature of Cloudflare's products such as 1.1.1.1 DNS or Cloudflare's CDN.
 
 <Aside type="tip">
-	**See it in action:** Explore our [interactive Global SFU
-	visualization](https://realtime-sfu.dev-demos.workers.dev) to see how
-	participants connect to their nearest Cloudflare datacenter and how media
-	flows across the global backbone.
+**See it in action:** Explore our [interactive Global SFU visualization](https://realtime-sfu.dev-demos.workers.dev) to see how participants connect to their nearest Cloudflare datacenter and how media flows across the global backbone.
 </Aside>
 
 ## How Cloudflare Realtime Works
diff --git a/src/content/docs/realtime/sfu/changelog.mdx b/src/content/docs/realtime/sfu/changelog.mdx
index 1c9d09e442ea9d3..e41f539ea385e1c 100644
--- a/src/content/docs/realtime/sfu/changelog.mdx
+++ b/src/content/docs/realtime/sfu/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/realtime.yaml. --> */}
 
-<ProductReleaseNotes />
+<ProductReleaseNotes />
\ No newline at end of file
diff --git a/src/content/docs/realtime/sfu/datachannels.mdx b/src/content/docs/realtime/sfu/datachannels.mdx
index f60c593ca262bb6..fb486465f76084c 100644
--- a/src/content/docs/realtime/sfu/datachannels.mdx
+++ b/src/content/docs/realtime/sfu/datachannels.mdx
@@ -22,7 +22,7 @@ DataChannels on Cloudflare Realtime can scale up to many subscribers per publish
 
 ### How to use DataChannels
 
-1. Create two Realtime sessions, one for the publisher and one for the subscribers.
+1. Create  two Realtime sessions, one for the publisher and one for the subscribers.
 2. Create a DataChannel by calling /datachannels/new with the location set to "local" and the dataChannelName set to the name of the DataChannel.
 3. Create a DataChannel by calling /datachannels/new with the location set to "remote" and the sessionId set to the sessionId of the publisher.
 4. Use the DataChannel to send data from the publisher to the subscribers.
diff --git a/src/content/docs/realtime/sfu/get-started.mdx b/src/content/docs/realtime/sfu/get-started.mdx
index 43ee74f34fe8975..c629ade1a9f321c 100644
--- a/src/content/docs/realtime/sfu/get-started.mdx
+++ b/src/content/docs/realtime/sfu/get-started.mdx
@@ -10,8 +10,10 @@ products:
 
 :::note[Before you get started:]
 
+
 You must first [create a Cloudflare account](/fundamentals/account/create-account/).
 
+
 :::
 
 ## Create your first app
@@ -19,7 +21,7 @@ You must first [create a Cloudflare account](/fundamentals/account/create-accoun
 Every Realtime App is a separate environment, so you can make one for development, staging and production versions for your product.
 Either using [Dashboard](https://dash.cloudflare.com/?to=/:account/realtime/sfu), or the [API](/api/resources/calls/subresources/sfu/methods/create/) create a Realtime App. When you create a Realtime App, you will get:
 
-- App ID
-- App Secret
+* App ID
+* App Secret
 
 These two combined will allow you to make API Realtime from your backend server to Realtime.
diff --git a/src/content/docs/realtime/sfu/limits.mdx b/src/content/docs/realtime/sfu/limits.mdx
index df32c721be0f051..b68859142236802 100644
--- a/src/content/docs/realtime/sfu/limits.mdx
+++ b/src/content/docs/realtime/sfu/limits.mdx
@@ -12,28 +12,28 @@ Understanding the limits and timeouts of Cloudflare Realtime is crucial for opti
 
 ## Free
 
-- Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
-- Data transfer from your client to Cloudflare is always free of charge.
+* Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
+* Data transfer from your client to Cloudflare is always free of charge.
 
 ## Limits
 
-- **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
+* **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
 
-- **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
+* **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
 
-- **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
+* **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
 
 ## Inactivity Timeout
 
-- **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
+* **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
 
 ## PeerConnection Requirements
 
-- **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
+* **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
 
 ## Handling Connectivity Issues
 
-- **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
+* **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
 
 Adhering to these limits and understanding the timeout behaviors will help ensure that your applications remain responsive and stable while providing a seamless user experience.
 
@@ -43,18 +43,19 @@ Cloudflare Realtime supports the following codecs:
 
 ### Supported video codecs
 
-- **H264**
-- **H265**
-- **VP8**
-- **VP9**
-- **AV1**
+* **H264**
+* **H265**
+* **VP8**
+* **VP9**
+* **AV1**
 
 ### Supported audio codecs
 
-- **Opus**
-- **G.711 PCM (A-law)**
-- **G.711 PCM (µ-law)**
+* **Opus**
+* **G.711 PCM (A-law)**
+* **G.711 PCM (µ-law)**
 
 :::note
 For external 48kHz PCM support refer to the [WebSocket adapter](/realtime/sfu/media-transport-adapters/websocket-adapter/)
 :::
+
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
index 2edd1740c70cb39..a9a0f3df0ddbf5b 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
@@ -47,7 +47,6 @@ graph LR
 **Adapter instance**: Each connection creates a unique instance with an `adapterId` to manage its lifecycle.
 
 **Location types**:
-
 - `local` (Ingest): Receives media from external endpoints to create new WebRTC tracks
 - `remote` (Stream): Sends media from existing WebRTC tracks to external endpoints
 
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
index 818a1d69f4a3779..ea922e873043cc4 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
@@ -206,11 +206,11 @@ POST /v1/apps/{appId}/adapters/websocket/close
 
 ```json
 {
-	"tracks": [
-		{
-			"adapterId": "string"
-		}
-	]
+  "tracks": [
+    {
+      "adapterId": "string"
+    }
+  ]
 }
 ```
 
@@ -242,7 +242,6 @@ message Packet {
 **Ingest mode (buffer)**: Only the `payload` field is used, containing chunks of audio data.
 
 **Stream mode (egress)**:
-
 - For audio frames:
   - `sequenceNumber`: Incremental packet counter
   - `timestamp`: Timestamp for synchronization
@@ -268,14 +267,12 @@ Connects to your WebSocket endpoint:
 ### Message format
 
 #### Buffer mode (ingest)
-
 - **Binary messages**: PCM audio data in chunks
 - **Maximum message size**: 32 KB per WebSocket message
 - **Important**: Account for serialization overhead when chunking audio buffers
 - Send audio in small, frequent chunks rather than large batches
 
-#### Stream mode (egress)
-
+#### Stream mode (egress)  
 - **Binary messages**: Individual frames with metadata (audio or video)
 - Audio frames include:
   - Timestamp information
@@ -333,11 +330,11 @@ Usage counts towards your Cloudflare Realtime free tier of 1,000 GB.
 
 ## Error handling
 
-| Error Code | Description                              |
-| ---------- | ---------------------------------------- |
-| `400`      | Invalid request parameters               |
-| `404`      | Session or track not found               |
-| `503`      | Adapter not found (for close operations) |
+| Error Code | Description |
+|------------|-------------|
+| `400` | Invalid request parameters |
+| `404` | Session or track not found |
+| `503` | Adapter not found (for close operations) |
 
 ## Reference implementations
 
diff --git a/src/content/docs/realtime/sfu/sessions-tracks.mdx b/src/content/docs/realtime/sfu/sessions-tracks.mdx
index 8f88a1a807fd435..0acfcba0d460671 100644
--- a/src/content/docs/realtime/sfu/sessions-tracks.mdx
+++ b/src/content/docs/realtime/sfu/sessions-tracks.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**, **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
+Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**,  **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
 
 ## Application
 
@@ -18,17 +18,17 @@ A Realtime Application is an environment within different Sessions and Tracks ca
 
 A **Session** in Cloudflare Realtime correlates directly to a WebRTC PeerConnection. It represents the establishment of a communication channel between a client and the nearest Cloudflare data center, as determined by Cloudflare's anycast routing. Typically, a client will maintain a single Session, encompassing all communications between the client and Cloudflare.
 
-- **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
-- **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
-- **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
+* **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
+* **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
+* **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
 
 ## Tracks
 
 Within a Session, there can be one or more **Tracks**.
 
-- **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
-- **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
-- **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
+* **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
+* **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
+* **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
 
 ## Realtime as a Programmable "Switchboard"
 
@@ -38,9 +38,9 @@ The analogy of a switchboard is apt for understanding Realtime. Historically, sw
 
 While many SFUs utilize concepts like "rooms" to manage media streams among users, this approach has scalability and flexibility limitations. Cloudflare Realtime opts for a more granular and flexible model with Sessions and Tracks, enabling a wide range of use cases:
 
-- Large-scale remote events, like 'fireside chats' with thousands of participants.
-- Interactive conversations with the ability to bring audience members "on stage."
-- Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
+* Large-scale remote events, like 'fireside chats' with thousands of participants.
+* Interactive conversations with the ability to bring audience members "on stage."
+* Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
 
 ### Presence Protocol vs. Media Flow
 
diff --git a/src/content/docs/realtime/turn/custom-domains.mdx b/src/content/docs/realtime/turn/custom-domains.mdx
index 16baeeb56029ffa..9103a2e08eaf8a9 100644
--- a/src/content/docs/realtime/turn/custom-domains.mdx
+++ b/src/content/docs/realtime/turn/custom-domains.mdx
@@ -12,9 +12,9 @@ Cloudflare Realtime TURN service supports using custom domains for UDP, and TCP
 
 | Protocol      | Custom domains | Primary port | Alternate port |
 | ------------- | -------------- | ------------ | -------------- |
-| STUN over UDP | ✅             | 3478/udp     | 53/udp         |
-| TURN over UDP | ✅             | 3478/udp     | 53 udp         |
-| TURN over TCP | ✅             | 3478/tcp     | 80/tcp         |
+| STUN over UDP | ✅              | 3478/udp     | 53/udp         |
+| TURN over UDP | ✅              | 3478/udp     | 53 udp         |
+| TURN over TCP | ✅              | 3478/tcp     | 80/tcp         |
 | TURN over TLS | No             | 5349/tcp     | 443/tcp        |
 
 ## Setting up a CNAME record
@@ -23,16 +23,20 @@ To use custom domains for TURN, you must create a CNAME DNS record pointing to `
 
 :::caution
 
+
 Do not resolve the address of `turn.cloudflare.com` or `stun.cloudflare.com` or use an IP address as the value you input to your DNS record. Only CNAME records are supported.
 
+
 :::
 
 Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for custom domains.
 
 :::note
 
+
 If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
+
 :::
 
 There is no additional charge to using a custom hostname with Cloudflare Realtime TURN.
diff --git a/src/content/docs/realtime/turn/generate-credentials.mdx b/src/content/docs/realtime/turn/generate-credentials.mdx
index 3f1c3bf4bf971ac..bbb75c2c0e043bf 100644
--- a/src/content/docs/realtime/turn/generate-credentials.mdx
+++ b/src/content/docs/realtime/turn/generate-credentials.mdx
@@ -18,8 +18,8 @@ You should keep your TURN key on the server side (don't share it with the browse
 
 With a TURN key you can:
 
-- Generate TURN credentials that expire
-- Revoke previously issued TURN credentials
+* Generate TURN credentials that expire
+* Revoke previously issued TURN credentials
 
 ## Create credentials
 
@@ -36,9 +36,12 @@ The **201 (Created)** response below can then be passed on to your front-end app
 
 ```json
 {
-	"iceServers": [
+  "iceServers": [
 		{
-			"urls": ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"]
+			"urls": [
+				"stun:stun.cloudflare.com:3478",
+				"stun:stun.cloudflare.com:53"
+			]
 		},
 		{
 			"urls": [
@@ -64,9 +67,12 @@ Use `iceServers` as follows when instantiating the `RTCPeerConnection`:
 
 ```js
 const myPeerConnection = new RTCPeerConnection({
-	iceServers: [
-		{
-			urls: ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"],
+  iceServers: [
+    {
+      urls: [
+				"stun:stun.cloudflare.com:3478",
+				"stun:stun.cloudflare.com:53"
+			]
 		},
 		{
 			urls: [
@@ -75,15 +81,14 @@ const myPeerConnection = new RTCPeerConnection({
 				"turn:turn.cloudflare.com:3478?transport=tcp",
 				"turn:turn.cloudflare.com:80?transport=tcp",
 				"turns:turn.cloudflare.com:5349?transport=tcp",
-				"turns:turn.cloudflare.com:443?transport=tcp",
-			],
-			username:
-				"bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
-			credential:
-				"ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0",
-		},
-	],
+				"turns:turn.cloudflare.com:443?transport=tcp"
+      ],
+			"username": "bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
+			"credential": "ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0"
+    },
+  ],
 });
+
 ```
 
 The `ttl` value can be adjusted to expire the short lived key in a certain amount of time. This value should be larger than the time you'd expect the users to use the TURN service. For example, if you're using TURN for a video conferencing app, the value should be set to the longest video call you'd expect to happen in the app.
diff --git a/src/content/docs/realtime/turn/replacing-existing.mdx b/src/content/docs/realtime/turn/replacing-existing.mdx
index 7fdfd0d0da1642f..2ed8f3af74ea916 100644
--- a/src/content/docs/realtime/turn/replacing-existing.mdx
+++ b/src/content/docs/realtime/turn/replacing-existing.mdx
@@ -14,12 +14,12 @@ If you are a existing TURN provider but would like to switch to providing Cloudf
 
 Cloudflare Realtime TURN service can reduce tangible and untangible costs associated with TURN servers:
 
-- Server costs (AWS EC2 etc)
-- Bandwidth costs (Egress, load balancing etc)
-- Time and effort to set up a TURN process and maintenance of server
-- Scaling the servers up and down
-- Maintain the TURN server with security and feature updates
-- Maintain high availability
+* Server costs (AWS EC2 etc)
+* Bandwidth costs (Egress, load balancing etc)
+* Time and effort to set up a TURN process and maintenance of server
+* Scaling the servers up and down
+* Maintain the TURN server with security and feature updates
+* Maintain high availability
 
 ## Recommendations
 
@@ -56,8 +56,8 @@ When billing for TURN usage in your application, it's crucial to understand and
 
 The sampling process in TURN analytics works on two levels:
 
-- At data collection: Usage data points may be sampled if they are generated too quickly.
-- At query time: Additional sampling may occur if the query is too complex or covers a large time range.
+* At data collection: Usage data points may be sampled if they are generated too quickly.
+* At query time: Additional sampling may occur if the query is too complex or covers a large time range.
 
 To ensure accurate billing, write a single query that sums TURN usage per customer per time period, returning a single value. Avoid using queries that list usage for multiple customers simultaneously.
 
@@ -65,16 +65,20 @@ By following these guidelines and understanding how TURN analytics handles sampl
 
 :::note
 
+
 Cloudflare Realtime only bills for traffic from Cloudflare's servers to your client, called `egressBytes`.
 
+
 :::
 
 ### Example queries
 
 :::caution[Incorrect approach example]
 
+
 Querying TURN usage for multiple customers in a single query can lead to inaccurate results. This is because the usage pattern of one customer could affect the sampling rate applied to another customer's data, potentially skewing the results.
 
+
 :::
 
 ```
diff --git a/src/content/docs/realtime/turn/rfc-matrix.mdx b/src/content/docs/realtime/turn/rfc-matrix.mdx
index b2a69b56b7450d0..88bffe6390fe56f 100644
--- a/src/content/docs/realtime/turn/rfc-matrix.mdx
+++ b/src/content/docs/realtime/turn/rfc-matrix.mdx
@@ -12,23 +12,23 @@ products:
 
 | Protocol | Support | Relevant specification                                                                                    |
 | -------- | ------- | --------------------------------------------------------------------------------------------------------- |
-| UDP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TCP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TLS      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| UDP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TCP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TLS      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
 | DTLS     | No      | [draft-petithuguenin-tram-turn-dtls-00](http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00) |
 
 ## TURN client to TURN server protocols
 
-| Protocol                                        | Support                                                                                                                               | Relevant specification                                                                                               |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| TURN (base RFC)                                 | ✅                                                                                                                                    | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
+| Protocol                                        | Support                                                                                                                        | Relevant specification                                                                                               |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
+| TURN (base RFC)                                 | ✅                                                                                                                              | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
 | TURN REST API                                   | ✅ (See [FAQ](/realtime/turn/faq/#does-cloudflare-realtime-turn-support-the-expired-ietf-rfc-draft-draft-uberti-behave-turn-rest-00)) | [draft-uberti-behave-turn-rest-00](http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)                      |
-| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                                    | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
-| ALPN support for STUN & TURN                    | ✅                                                                                                                                    | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
-| TURN Bandwidth draft specs                      | No                                                                                                                                    | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
-| TURN-bis (with dual allocation) draft specs     | No                                                                                                                                    | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
-| TCP relaying TURN extension                     | No                                                                                                                                    | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
-| IPv6 extension for TURN                         | No                                                                                                                                    | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
-| oAuth third-party TURN/STUN authorization       | No                                                                                                                                    | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
-| DTLS support (for TURN)                         | No                                                                                                                                    | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
-| Mobile ICE (MICE) support                       | No                                                                                                                                    | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
+| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                              | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
+| ALPN support for STUN & TURN                    | ✅                                                                                                                              | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
+| TURN Bandwidth draft specs                      | No                                                                                                                             | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
+| TURN-bis (with dual allocation) draft specs     | No                                                                                                                             | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
+| TCP relaying TURN extension                     | No                                                                                                                             | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
+| IPv6 extension for TURN                         | No                                                                                                                             | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
+| oAuth third-party TURN/STUN authorization       | No                                                                                                                             | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
+| DTLS support (for TURN)                         | No                                                                                                                             | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
+| Mobile ICE (MICE) support                       | No                                                                                                                             | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx
index 22b77e10e9ae65d..737fee4c2b7c58b 100644
--- a/src/content/docs/reference-architecture/architectures/sase.mdx
+++ b/src/content/docs/reference-architecture/architectures/sase.mdx
@@ -318,13 +318,13 @@ Organizations may also connect their network locations directly to the Cloudflar
 
 The following table summarizes the different methods of connecting networks to Cloudflare:
 
-| **Use case**                                                                                                                                           | **Recommended**                            | **Alternative solution**                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------- |
-| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)** | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment   |
-| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                         | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
-| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                         | **N/A**                                                                               |
-| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh**                        | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required      |
-| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh**                        | **N/A**                                                                               |
+| **Use case**                                                                                                                                           | **Recommended**                             | **Alternative solution**                                                                                      |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)**  | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment                           |
+| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                          | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
+| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                          | **N/A**                                                                                                       |
+| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh** | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required                              |
+| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh** | **N/A**                                                                                                       |
 
 Each of these methods of connecting and routing traffic can be deployed concurrently from any location. The following diagram highlights how different connectivity methods can be used in a single architecture.
 
@@ -343,8 +343,8 @@ Note the following traffic flows:
 _Note: Labels in this image may reflect a previous product name._
 
 <sub>
-	*Note: All of the endpoints connected via Cloudflare Mesh or device agent are
-	automatically assigned IP addresses from the 100.96.0.0/12 address range,
+	*Note: All of the endpoints connected via Cloudflare Mesh or device agent
+	are automatically assigned IP addresses from the 100.96.0.0/12 address range,
 	while endpoints connected to Cloudflare WAN retain their assigned RFC1918
 	private IP addresses. `cloudflared` can be deployed in any of the locations by
 	an application owner to provide hostname-based connectivity to the
diff --git a/src/content/docs/reference-architecture/architectures/security.mdx b/src/content/docs/reference-architecture/architectures/security.mdx
index f773fce4c276399..3d627ba4e4372c4 100644
--- a/src/content/docs/reference-architecture/architectures/security.mdx
+++ b/src/content/docs/reference-architecture/architectures/security.mdx
@@ -527,7 +527,7 @@ Existing private infrastructure can be complex. Cloudflare provides a variety of
 | [Cloudflare WAN](/cloudflare-wan/)                                                                            | IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                                   | Connecting existing network routers to Cloudflare. Allowing all traffic into and out of the network to go through Cloudflare.                                                       |
 | [Cloudflare One Appliance](/cloudflare-wan/configuration/appliance/)                                          | Appliance-based IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                   | Uses the same technology as Cloudflare WAN; however, instead of using existing networking devices, a dedicated appliance or virtual machine is used — the Cloudflare One Appliance. |
 | [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/)                                         | Software agent deployed on servers or alongside services like Kubernetes for creating a tunnel for incoming connections to private applications or networks. | IT admins or application owners can easily install this tunnel software to expose their application to the Cloudflare network.                                                      |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                                       | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)           | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
 | [WARP Desktop Agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                       | Software agent deployed on user devices, creating a tunnel for traffic to and from private applications and networks.                                        | Connecting end user devices like phones and laptops to be part of the Cloudflare network.                                                                                           |
 | [Cloudflare Network Interconnect](https://www.cloudflare.com/network-services/products/network-interconnect/) | Direct connection between your physical networks and Cloudflare.                                                                                             | When your applications live in the same data centers we operate in, we can connect those networks directly to Cloudflare.                                                           |
 
diff --git a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
index fb6d969b7413b35..7365c6406dda2f5 100644
--- a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
+++ b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
@@ -485,15 +485,15 @@ Now, you will learn how to secure RDP access as a private IP application:
 
 As mentioned before, private IP applications work because Cloudflare proxies the IP range across its network. The nature of this application necessitates the use of the device client, as unless the user is connected to Cloudflare (and more specifically, unless they can take advantage of the Client-to-Tunnel connectivity), they will not be able to reach non-local RFC 1918 addresses.
 
-| Traffic                                            |                                                                 |
-| :------------------------------------------------- | :-------------------------------------------------------------- |
-| Destination IP                                     | 169.254.255.254                                                 |
-| Destination Port                                   | 3389                                                            |
-| **Identity**                                       |                                                                 |
-| User Group Names                                   | Server Admins                                                   |
-| **Device Posture**                                 |                                                                 |
-| Passed Device Posture Checks                       | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
-| **Action**                                         | Allow                                                           |
+| Traffic                                  |                                                                 |
+| :--------------------------------------- | :-------------------------------------------------------------- |
+| Destination IP                           | 169.254.255.254                                                 |
+| Destination Port                         | 3389                                                            |
+| **Identity**                             |                                                                 |
+| User Group Names                         | Server Admins                                                   |
+| **Device Posture**                       |                                                                 |
+| Passed Device Posture Checks             | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
+| **Action**                               | Allow                                                           |
 | **Enforce Cloudflare One Client session duration** | 60m0s                                                           |
 
 Defining the application here is simple, as Cloudflare automatically fills in the IP range, and you need to limit the detected protocol to RDP. However, the rules for private IP applications are slightly different. You will notice they appear as network policies under the Cloudflare Gateway menu, despite managing them in Access. Certain options, such as checking for MFA and external evaluation, do not appear here. However, these attributes can be verified when the user activates their device client and authenticates to their organization.
diff --git a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
index 6b66d65a74db8d4..dc60c3bd546f404 100644
--- a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
+++ b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
@@ -33,15 +33,15 @@ This solution supports subdomains under your own zone while also allowing your c
 
 Before looking at how Cloudflare can be configured to protect your SaaS application through your custom hostnames, it's worth reviewing the benefits of taking this approach.
 
-| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                   |
-| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                           |
-| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                |
-| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                           |
-| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                |
+| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                                                       |
+| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                                                               |
+| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                                                    |
+| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                                                               |
+| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                                                    |
 | O2O                      | For end-customers who already proxy traffic through Cloudflare, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) may be required. Generally, it's recommended for those end-customers to [not proxy](/dns/proxy-status/#dns-only-records) the hostnames used by the SaaS provider. If O2O functionality is required, please review the [product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/). |
-| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                            |
+| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                                                                |
 
 ## Products included in this guide
 
diff --git a/src/content/docs/reference-architecture/diagrams/ai/index.mdx b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
index 31b853acdc50598..a86575102d8dcfa 100644
--- a/src/content/docs/reference-architecture/diagrams/ai/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
@@ -12,6 +12,6 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
index b78ee67b330dcc6..65249beeb1e0af4 100644
--- a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
@@ -12,6 +12,6 @@ products:
   - cache
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
index 52648681f876333..0e82981e3eafb7b 100644
--- a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
+++ b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
@@ -1,20 +1,7 @@
 ---
 title: Optimizing and securing connected transportation systems
 pcx_content_type: reference-architecture-diagram
-products:
-  [
-    argo-smart-routing,
-    api-shield,
-    cache,
-    ddos-protection,
-    dns-firewall,
-    load-balancing,
-    r2,
-    workers,
-    ssl,
-    waf,
-    workers-ai,
-  ]
+products: [argo-smart-routing, api-shield, cache, ddos-protection, dns-firewall, load-balancing, r2, workers, ssl, waf, workers-ai]
 sidebar:
   order: 1
   label: Connected transportation systems
@@ -42,6 +29,7 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
 2. **Cloudflare anycast network**: Cloudflare uses [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) networking and is one of the world's most connected and geographically distributed networks. Traffic is routed to the nearest Cloudflare data center, which reduces the number of network hops, dynamically adapts to changing network conditions, and ensures data takes the shortest path to its destination, minimizing latency and maximizing reliability.
 
 3. **Security services**:
+
    1. **API Shield**: Cloudflare's [API Shield](/api-shield/get-started/) protects critical APIs from unauthorized access and abuse, ensuring secure data exchange between connected systems.
    2. **Web Application Firewall (WAF)**: Cloudflare's [WAF](/waf/) helps block malicious traffic and prevent application or API vulnerabilities from being exploited, safeguarding your network, devices and applications.
    3. **DDoS Protection**: Cloudflare's [DDoS protection](/ddos-protection/about/attack-coverage/), covering the network, transport and application layer, prevents volumetric attacks that could compromise the availability of connected systems. By providing multi-layered protection, Cloudflare is able to mitigate a wide variety of DDoS threats. At lower layers, Cloudflare defends against high-volume attacks such as SYN floods, UDP floods, and other types of protocol-based disruptions that can overwhelm network resources. At the application layer, more sophisticated attacks targeting the application itself, such as HTTP floods \- which aim to exhaust server resources and disrupt user-facing services \- are blocked even in the face of [large-scale DDoS attempts](https://blog.cloudflare.com/tag/ddos-reports/).
@@ -49,6 +37,7 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
    5. **TLS encryption**: [TLS encryption](/ssl/edge-certificates/) ensures that data exchanged across the network is protected from interception, maintaining data integrity and privacy.
 
 4. **Performance and reliability services**:
+
    1. **Content Delivery Network (CDN)**: [Distribute content](https://www.cloudflare.com/en-gb/learning/cdn/what-is-a-cdn/) efficiently across the network, reducing latency for end users by caching data closer to them.
    2. **Load balancing**: [Distribute incoming traffic](/load-balancing/get-started/quickstart/) across multiple servers or data centers, ensuring optimal resource utilization, preventing single points of failure, and improving the performance of connected systems.
    3. **Cloudflare Workers**: Our serverless compute platform, [Cloudflare Workers](/workers/), allows data processing at the edge, reducing the need for data to travel long distances and significantly reducing latency. Combined with related services like [Workers KV](/kv/get-started/) and [D1](https://www.cloudflare.com/en-gb/developer-platform/products/d1/), Cloudflare's edge-based storage solutions enable efficient data management close to the user. Workers KV allows for quick, read-heavy data access, perfect for caching configurations and frequently used data, while D1 provides a serverless SQL database for more robust storage needs. Additionally, Cloudflare's [Durable Objects](https://blog.cloudflare.com/sqlite-in-durable-objects/) help manage stateful interactions at the edge, facilitating real-time data consistency. These tools together allow for seamless data processing, storage and lazy updates to core services, minimizing back-and-forth to centralized servers and ensuring faster, more efficient performance.
diff --git a/src/content/docs/reference-architecture/diagrams/network/index.mdx b/src/content/docs/reference-architecture/diagrams/network/index.mdx
index 8d297fcb542d684..dab7f9b29c2ac8b 100644
--- a/src/content/docs/reference-architecture/diagrams/network/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/network/index.mdx
@@ -12,6 +12,6 @@ products:
   - magic-transit
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/sase/index.mdx b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
index 5a5bcdc66e7f753..952f8cbb7035014 100644
--- a/src/content/docs/reference-architecture/diagrams/sase/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
@@ -12,6 +12,6 @@ products:
   - cloudflare-one
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/security/index.mdx b/src/content/docs/reference-architecture/diagrams/security/index.mdx
index b6a5e7116f9b9ab..6e7f959a2bf1894 100644
--- a/src/content/docs/reference-architecture/diagrams/security/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/security/index.mdx
@@ -12,6 +12,6 @@ products:
   - waf
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
index 80a5daa8d28537b..be169cd2360397e 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
@@ -1,32 +1,7 @@
 ---
 title: Fullstack applications
 pcx_content_type: reference-architecture-diagram
-products:
-  [
-    ai-gateway,
-    agents,
-    api-shield,
-    bots,
-    containers,
-    d1,
-    ddos-protection,
-    durable-objects,
-    images,
-    kv,
-    logs,
-    pages,
-    pipelines,
-    queues,
-    r2,
-    realtime,
-    ssl,
-    stream,
-    vectorize,
-    waf,
-    workflows,
-    workers,
-    workers-ai,
-  ]
+products: [ai-gateway, agents, api-shield, bots, containers, d1, ddos-protection, durable-objects, images, kv, logs, pages, pipelines, queues, r2, realtime, ssl, stream, vectorize, waf, workflows, workers, workers-ai]
 sidebar:
   order: 1
   label: Fullstack applications
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
index ec24b3e2d1e0920..fd828080d0d13a7 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
@@ -11,6 +11,6 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
index 37a97208f955c57..59502f5c65c9030 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
@@ -94,6 +94,7 @@ Data observability and control is crucial for security. [Outbound Workers](/clou
 1. **Management Interface**: Interact with the platform through GUI, API, or CLI interfaces.
 
 2. **Platform Processing**: Process these interactions to:
+
    - Transform and bundle code
    - Perform security checks
    - Apply configuration
diff --git a/src/content/docs/reference-architecture/diagrams/storage/index.mdx b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
index c1a8deb1e885b1a..bed6aa10ef8f5ae 100644
--- a/src/content/docs/reference-architecture/diagrams/storage/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
@@ -11,6 +11,6 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/implementation-guides/index.mdx b/src/content/docs/reference-architecture/implementation-guides/index.mdx
index 050e352a4e30355..2904c70b1df0a79 100644
--- a/src/content/docs/reference-architecture/implementation-guides/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/index.mdx
@@ -23,4 +23,4 @@ Implementation guides provide [step-by-step instructions](/reference-architectur
 
 ## Application Security
 
-- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
+- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
\ No newline at end of file
diff --git a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
index 2fdb4a789da4092..5c5f919b63c0538 100644
--- a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
@@ -19,4 +19,4 @@ Zero Trust implementation guides walk you through the steps to deploy a Zero Tru
 - [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/)
 - [Replace your VPN](/learning-paths/replace-vpn/concepts/)
 - [Deploy Zero Trust Web Access](/learning-paths/clientless-access/concepts/)
-- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
+- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
\ No newline at end of file
diff --git a/src/content/docs/registrar/account-options/domain-contact-updates.mdx b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
index 33cc9a043acdbdd..c68e021cdb34a52 100644
--- a/src/content/docs/registrar/account-options/domain-contact-updates.mdx
+++ b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
@@ -12,18 +12,18 @@ It is important that you keep your contact details accurate and up-to-date. [ICA
 
 The contact information you can update includes:
 
-- First name
-- Last name
-- Email
-- Organization
-- Phone
-- Address including City, State/Province, Postal code & Country
+* First name
+* Last name
+* Email
+* Organization
+* Phone
+* Address including City, State/Province, Postal code & Country
 
 To update your registrant contacts:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find **Default contact** and select **Edit**.
 3. Update the relevant information, and select **Save**.
@@ -32,10 +32,10 @@ To update your registrant contacts:
 
 If you change any of the following fields, Cloudflare Registrar will require a Change of Registrant approval before the changes are finalized:
 
-- First name
-- Last name
-- Organization
-- Email address
+* First name
+* Last name
+* Organization
+* Email address
 
 If you update any of the fields mentioned above, Cloudflare Registrar will send an approval email to the current registrant's email address. The approval email contains a link to a web page where the requested change may be viewed and approved or rejected. If the pending change is not approved or rejected within seven days, the request will automatically be canceled.
 
@@ -43,9 +43,11 @@ If you do not update these fields, your contact information is updated immediate
 
 :::caution[Important]
 
+
 After selecting the link in the approval email Cloudflare sends you, you have the option to accept or reject the contact changes. If you select the **Accept** button, your domain will be transfer-locked for 60 days.
 
-If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox _before_ selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
+If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox *before* selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
+
 
 :::
 
diff --git a/src/content/docs/registrar/account-options/domain-management.mdx b/src/content/docs/registrar/account-options/domain-management.mdx
index 436f7461a485b3f..b00b69c71cdde48 100644
--- a/src/content/docs/registrar/account-options/domain-management.mdx
+++ b/src/content/docs/registrar/account-options/domain-management.mdx
@@ -6,7 +6,7 @@ products:
 description: Manage your registered domains in the dashboard.
 ---
 
-import { DashButton, LinkButton } from "~/components";
+import { DashButton, LinkButton } from "~/components"
 
 ## Domain status
 
@@ -14,9 +14,9 @@ When your domain is registered with Cloudflare, you can review your domain statu
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date.
+2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date. 
 3. Select **Manage domain** to review the Auto-Renew status for your domain.
 
 ## Billing information
@@ -25,7 +25,7 @@ Domain registrations will not appear in the **Active Subscriptions** section of
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to check and select **Manage**.
 3. Refer to **Registration** for information regarding your domain fees. From here, you can also opt to [renew or extend](/registrar/account-options/renew-domains/) your domain registration.
@@ -36,7 +36,7 @@ Cloudflare redacts WHOIS information from your domain by default. However, we do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to edit and select **Manage** > **Contacts**.
 3. Select **Edit** in any of the contacts you previously set up. This allows you to update the contact information for the selected domain only. It will not update the contact information for other domains within the account.
@@ -62,10 +62,10 @@ There may be instances where users may wish to delete a domain prior to expirati
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
-3. If the domain is deletable the button will be active. The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
-4. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
+3. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
+4. If the domain is deletable the button will be active.  The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
+5. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
 
 Once all steps are completed, the domain will then be scheduled for deletion. To understand more about the timelines and potential reasons why a domain cannot be deleted, refer to the Registrar [FAQ](/registrar/faq/#domain-deletions).
diff --git a/src/content/docs/registrar/account-options/icloud-domains.mdx b/src/content/docs/registrar/account-options/icloud-domains.mdx
index 51ea04635dec389..7cd576b2342f223 100644
--- a/src/content/docs/registrar/account-options/icloud-domains.mdx
+++ b/src/content/docs/registrar/account-options/icloud-domains.mdx
@@ -17,7 +17,7 @@ You will need an active iCloud+ subscription to add a custom email domain.
 
 If you want to buy a custom email domain, go to your [iCloud](https://www.icloud.com/settings/) settings and scroll down to **Custom Email Domain**.
 
----
+***
 
 ## Log in to Cloudflare
 
@@ -31,7 +31,7 @@ If you had signed up with Apple, signing into Cloudflare is as easy as clicking
 
 If you had signed up with Cloudflare, signing into Cloudflare can be done with your email and password.
 
----
+***
 
 ## Billing information
 
@@ -39,9 +39,9 @@ If you had signed up with Cloudflare, signing into Cloudflare can be done with y
 
 For domain registration, Cloudflare supports the following payment methods:
 
-- Credit Card
-- PayPal
-- Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
+* Credit Card
+* PayPal
+* Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
 
 For domain renewals, Apple Pay does not currently support recurring payments. You can either add another payment method (Credit Card or PayPal) for automatic renewals or log into [your account](#log-in-to-cloudflare) near the renewal date and use Apple Pay.
 
@@ -51,7 +51,7 @@ Users may see a price estimate in both U.S. Dollars and a local currency. This i
 
 The final payment will be charged in US dollars.
 
----
+***
 
 ## Email issues
 
@@ -67,7 +67,7 @@ If you are not receiving emails intended for your new email address, review your
 
 If your domain has records similar to those listed above and you are still experiencing problems with your new email address, contact [Apple Support](https://support.apple.com/).
 
----
+***
 
 ## Domain website
 
@@ -80,7 +80,7 @@ If you want your domain to be a fully functioning website, you will need to:
 1. **Build your website**: Either using [Cloudflare Pages](/pages/), a website builder, or files hosted on a server.
 2. **Update your Cloudflare DNS**: To direct visitors looking for your domain name to the actual content on your website ([detailed guide](/dns/manage-dns-records/how-to/create-zone-apex/)).
 
----
+***
 
 ## Landing Page
 
@@ -92,16 +92,18 @@ If you do not want to have Landing Page enabled:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
-3. Scroll to Landing Page and select **Disable**.
+3. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
+4. Scroll to Landing Page and select **Disable**.
 
 You now have Landing Page disabled. The page can also be re-enabled through the same process.
 
 :::note
 
+
 Customers must disable the landing page before they can add DNS records
 to point to a new website.
 
+
 :::
diff --git a/src/content/docs/registrar/account-options/index.mdx b/src/content/docs/registrar/account-options/index.mdx
index 0ad0fed63956d72..c28da7b171d3437 100644
--- a/src/content/docs/registrar/account-options/index.mdx
+++ b/src/content/docs/registrar/account-options/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Explore Cloudflare Registrar account options.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/account-options/inter-account-transfer.mdx b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
index 8089af6ebb59ebd..9ec8ed6c910675e 100644
--- a/src/content/docs/registrar/account-options/inter-account-transfer.mdx
+++ b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
@@ -15,29 +15,28 @@ This process only applies to domains which are registered with Cloudflare Regist
 
 Before proceeding, please be aware of the following:
 
-- WHOIS contact information will be moved as is.
-- No other configuration will be moved.
-- After successful move, the registration will be transfer-locked for 30 days.
-- The target account will become responsible for domain renewals going forward.
+* WHOIS contact information will be moved as is.
+* No other configuration will be moved.
+* After successful move, the registration will be transfer-locked for 30 days.
+* The target account will become responsible for domain renewals going forward.
 
 ## 1. Prepare for the move
 
 Before you request the move, you will need to do the following:
 
-- Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
-- Add the domain as a website to the new account and select a plan.
-- [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
+* Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
+* Add the domain as a website to the new account and select a plan.
+* [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
 
 The following pre-conditions must be met before the domain can be moved:
-
-- The domain must have been registered more than 10 days ago.
-- The domain must be added to the new account as a website and a plan must be selected.
-- The domain must not be administratively locked, such as being locked due to a dispute or court order.
-- The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
-- The registrant email address must be verified.
-- A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
-- DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
-- If the current zone is locked, the lock must be released.
+* The domain must have been registered more than 10 days ago.
+* The domain must be added to the new account as a website and a plan must be selected.
+* The domain must not be administratively locked, such as being locked due to a dispute or court order.
+* The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
+* The registrant email address must be verified.
+* A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
+* DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
+* If the current zone is locked, the lock must be released.
 
 ## 2. Submit the move request
 
diff --git a/src/content/docs/registrar/account-options/renew-domains.mdx b/src/content/docs/registrar/account-options/renew-domains.mdx
index 285bff694c78d57..dda7c66958054bd 100644
--- a/src/content/docs/registrar/account-options/renew-domains.mdx
+++ b/src/content/docs/registrar/account-options/renew-domains.mdx
@@ -21,8 +21,10 @@ If you decide you no longer need the domain, [disable auto-renew for your domain
 
 :::note[Note]
 
+
 The first auto-renew attempt will occur approximately 30 days prior to expiration. If you wish to disable auto-renew, do so at least 30 days prior to the expiration date.
 
+
 :::
 
 You can continue to keep your domain registered with Cloudflare for the time remaining until the expiration date. If you decide you want to keep the domain, enable auto-renew at any time prior to expiration.
@@ -33,7 +35,7 @@ If you want your domains to renew automatically, keep the default settings for y
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to automatically renew, and make sure the **Auto-renew** toggle is enabled.
 
@@ -45,8 +47,10 @@ If the renewal fails, you will receive an email notification and Cloudflare will
 
 :::note
 
+
 If you want to delete your domain from Cloudflare, **disable** Auto-Renew first.
 
+
 :::
 
 ## Renew a domain manually
@@ -55,7 +59,7 @@ You can renew a domain at any time. To renew a domain registered with Cloudflare
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to renew and select **Manage**.
 3. In **Registration** select **Renew/Extend Domain**.
@@ -68,22 +72,24 @@ Once Cloudflare validates your payment, the status of your domain changes to **R
 
 Once a domain is registered, Registrar sends the following expiration notices to the Super Admin of the domain:
 
-- A monthly email listing all domains set to renew automatically within the next 45 days.
-- A monthly email listing all domains expiring in the next 60-90 days.
+* A monthly email listing all domains set to renew automatically within the next 45 days.
+* A monthly email listing all domains expiring in the next 60-90 days.
 
 In addition to the Super Admin, the following expiration notices are sent to the WHOIS Registrant contact associated with the domain:
 
-- A weekly email listing all domains expiring within the next month.
-- A daily email listing all domains expiring in seven days.
-- An email one day after a domain expires.
-- An email 20 days after the expiration date.
+* A weekly email listing all domains expiring within the next month.
+* A daily email listing all domains expiring in seven days.
+* An email one day after a domain expires.
+* An email 20 days after the expiration date.
 
 :::note
 
+
 If you do not renew your domain before the expiration date, your domain will enter a Redemption Grace Period (RGP) for 30 days. These domains are not deleted and you can restore them to your account, but restoration may require an additional fee. You cannot transfer domains during the RGP.
 
 All renewals are final and Cloudflare will not issue refunds.
 
 When renewing a domain, additional years are always added to the current expiration date regardless of when the renewal takes place.
 
+
 :::
diff --git a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
index 9c7bbb499016c44..b699b2181413945 100644
--- a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
+++ b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
@@ -13,9 +13,9 @@ import { DashButton } from "~/components";
 
 Cloudflare Registrar makes it easy to transfer your domain to another registrar. Be aware that ICANN rules prohibit a domain from being transferred if:
 
-- The domain has been transferred within the last 60 days;
-- The domain was registered within the last 60 days;
-- If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
+* The domain has been transferred within the last 60 days;
+* The domain was registered within the last 60 days;
+* If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
 
 Follow the instructions below to transfer your domain out from Cloudflare.
 
@@ -28,7 +28,7 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to transfer, and select **Manage**.
 3. Select **Configuration** > **Unlock**.
@@ -37,8 +37,8 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 If you lose your authentication code, you can get a new one by:
 
-- Selecting the **Regenerate** button;
-- Locking the domain and repeating steps 1-6.
+* Selecting the **Regenerate** button;
+* Locking the domain and repeating steps 1-6.
 
 ## 2. Transfer to a new registrar
 
diff --git a/src/content/docs/registrar/account-options/whois-redaction.mdx b/src/content/docs/registrar/account-options/whois-redaction.mdx
index ae936db97b56984..54f84e462053f44 100644
--- a/src/content/docs/registrar/account-options/whois-redaction.mdx
+++ b/src/content/docs/registrar/account-options/whois-redaction.mdx
@@ -20,8 +20,8 @@ Cloudflare’s WHOIS service can be found at [https://rdap.cloudflare.com/](http
 
 WHOIS redaction removes most contact information categorized as personal data (such as registrant name, email address, postal address) from the published WHOIS record for a domain. These fields will read `Data Redacted`. The nameserver, domain lock information, and date records for a domain are still available publicly. The following fields will continue to show in WHOIS, due to ICANN policy:
 
-- Registrant state/province
-- Registrant country
+* Registrant state/province
+* Registrant country
 
 Cloudflare still maintains the authoritative, unredacted, record of your WHOIS data. You can modify this information at any time. Refer to [Registrant contact updates](/registrar/account-options/domain-contact-updates) for more information.
 
diff --git a/src/content/docs/registrar/custom-domain-protection.mdx b/src/content/docs/registrar/custom-domain-protection.mdx
index 7c230831d9ec50c..5175f44c6cba05f 100644
--- a/src/content/docs/registrar/custom-domain-protection.mdx
+++ b/src/content/docs/registrar/custom-domain-protection.mdx
@@ -12,8 +12,8 @@ Cloudflare offers [Custom Domain Protection](https://www.cloudflare.com/products
 
 Custom Domain Protection offers additional safeguard features for registered domains, including:
 
-- **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
-- **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
-- **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
+* **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
+* **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
+* **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
 
 Contact your account team if you are interested in Cloudflare's Custom Domain Protection.
diff --git a/src/content/docs/registrar/get-started/index.mdx b/src/content/docs/registrar/get-started/index.mdx
index adddbd0c163091c..0337c455830ed00 100644
--- a/src/content/docs/registrar/get-started/index.mdx
+++ b/src/content/docs/registrar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Set up Client IP Geolocation for your network.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/get-started/register-domain.mdx b/src/content/docs/registrar/get-started/register-domain.mdx
index 7f46b29e462ccda..b3d8c632b668672 100644
--- a/src/content/docs/registrar/get-started/register-domain.mdx
+++ b/src/content/docs/registrar/get-started/register-domain.mdx
@@ -10,14 +10,15 @@ description: Register a new domain with Cloudflare.
 
 import { DashButton, Render } from "~/components";
 
+
 ## Prerequisites and restrictions
 
 :::note[Cloudflare nameservers]
 All domains acquired via Cloudflare Registrar use Cloudflare nameservers, automatically [protecting and speeding up](/fundamentals/concepts/how-cloudflare-works/) your content or services. You will not be able to change to another DNS provider's nameservers while using Cloudflare Registrar.
 :::
 
-- Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
-- You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
+* Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
+* You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
 
 <Render file="icann-unverified-email" product="registrar" />
 
@@ -29,14 +30,16 @@ If you are registering a `.us` domain, refer to the [Additional requirements for
 
 1. In the Cloudflare dashboard, go to the **Register domains** page.
 
-   <DashButton url="/?to=/:account/registrar/register" />
+    <DashButton url="/?to=/:account/registrar/register" />
 
 2. In the search box, enter the domain name you wish to register, and select **Search**. You may also enter one or more keywords. The search results will contain a list of suggested domains. If the domain you entered does not appear in the list, this means it is not available for registration.
 
 :::caution[Important]
 
+
 Cloudflare Registrar currently does not support internationalized domain names (IDNs), also known as unicode. For that reason, you cannot search for words with special characters, such as `à`, `ü`, `ç`, among others.
 
+
 :::
 
 3. Select **Purchase** on the domain you wish to register. In rare instances, a domain that is not available for registration may appear in the search results. After selecting **Purchase**, a definitive availability check will be performed to confirm that the domain is actually available for registration.
@@ -49,10 +52,12 @@ Cloudflare Registrar currently does not support internationalized domain names (
 
 :::note
 
+
 If you have previously registered or transferred a domain name, the form will be filled in advance with the information from your default contact. If not, you will need to fill out the form.
 
 It is important that you provide complete and accurate contact information. If you do not follow this recommendation, the domain registration may be suspended and/or canceled.
 
+
 :::
 
 6. In **Payment**, select which type of payment you want to use. If you already have a billing profile, Cloudflare uses this information to automatically fill the form. If there is no billing profile, you need to enter your payment information.
@@ -67,6 +72,8 @@ The registration process may take up to 30 seconds to complete. Once the registr
 
 At this time, you can only use ASCII characters for contact data. If the default contact has non-ASCII characters, you will need to update the domain contact details before proceeding. Cloudflare recommends that you update your default contact information to include ASCII characters only.
 
+
+
 | Field        | Required? | Restrictions                                                                                                                   |
 | ------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
 | First Name   | Yes       | Minimum of two letters.                                                                                                        |
@@ -82,6 +89,8 @@ At this time, you can only use ASCII characters for contact data. If the default
 | Country      | Yes       | You must select one from the drop-down options.                                                                                |
 | Postal Code  | Yes       | Must be a properly formatted postal code.                                                                                      |
 
+
+
 When you register a domain with Cloudflare, your personal information is redacted when permitted by the registry. Refer to [WHOIS redaction](/registrar/account-options/whois-redaction/) for more information.
 
 ## Next steps
diff --git a/src/content/docs/registrar/top-level-domains/uk-domains.mdx b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
index 4ec5d8a00c26f8f..33034fbe090ae38 100644
--- a/src/content/docs/registrar/top-level-domains/uk-domains.mdx
+++ b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
@@ -22,16 +22,22 @@ Cloudflare currently supports the transfer of `.uk`, `co.uk`, `org.uk`, and `me.
 
 1. In the Cloudflare dashboard, go to the **Transfer domains** page.
 
-   <DashButton url="/?to=/:account/registrar/transfer" />
+    <DashButton url="/?to=/:account/registrar/transfer" />
 
-Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain. 2. Select the domains you wish to transfer. 3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process. 4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days. 5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
+Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain.
+2. Select the domains you wish to transfer.
+3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process.
+4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days.
+5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
 
 :::caution[Warning]
 
+
 If you request your current registrar to update the IPS tag before completing the checkout process, the transfer request will be automatically rejected. You must complete the checkout process before requesting the IPS tag update.
 
 For security reasons, domains transferred to Cloudflare Registrar are locked for 60 days before they can be transferred out to another Registrar.
 
+
 :::
 
 ## Transfer a .UK domain to another registrar
@@ -46,6 +52,8 @@ Your new registrar is responsible for accepting the transfer. Cloudflare has no
 
 :::note
 
+
 If you do not know the IPS tag, contact your new registrar for instructions. Your new registrar may require you to follow some additional steps before starting the transfer process.
 
+
 :::
diff --git a/src/content/docs/registrar/whoisrequests.mdx b/src/content/docs/registrar/whoisrequests.mdx
index 95317e78416dd66..445ca659095fc8e 100644
--- a/src/content/docs/registrar/whoisrequests.mdx
+++ b/src/content/docs/registrar/whoisrequests.mdx
@@ -10,7 +10,7 @@ description: Submit WHOIS disclosure requests to Cloudflare.
 
 This page describes the mechanism and process for submitting a disclosure request to Cloudflare for WHOIS data under Section 10 of the Internet Corporation for Assigned Names and Number's ("ICANN") [Registration Data Policy](https://www.icann.org/en/contracted-parties/consensus-policies/registration-data-policy).
 
-Please read the following instructions carefully.
+Please read the following instructions carefully.  
 
 ## 1. Prepare your request
 
@@ -18,7 +18,7 @@ Your request must include the following elements:
 
 - Your name
 - The requestor's name, mailing address, and email
-- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity. If the latter, identify whether the requestor is an individual, corporation, or government
+- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity.  If the latter, identify whether the requestor is an individual, corporation, or government
 - Any power of Attorney statements or similar statements evidencing authorization to act on the requestor's behalf, where applicable and relevant
 - A list of data element values requested by the requestor
 - Information about the legal rights of the requestor and specific rationale and basis for the request
diff --git a/src/content/docs/resource-tagging/get-started.mdx b/src/content/docs/resource-tagging/get-started.mdx
index b9bc956239e99a5..5a8aa68ee493d82 100644
--- a/src/content/docs/resource-tagging/get-started.mdx
+++ b/src/content/docs/resource-tagging/get-started.mdx
@@ -26,13 +26,13 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys
 
 ### Interpreting the response
 
-| Response                                             | Meaning                                                            | Action                                                                                                                                                        |
-| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step.                                                                                                                                     |
-| **403** mentioning "permission" or "role"            | The caller lacks required permissions.                             | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope.                    |
-| **403** mentioning "feature" or "gate"               | Tagging is not enabled for this account.                           | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance.                                                                         |
-| **401 Unauthorized**                                 | Authentication failed.                                             | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header.                                                        |
-| Any other response                                   | Unexpected error.                                                  | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
+| Response | Meaning | Action |
+| --- | --- | --- |
+| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step. |
+| **403** mentioning "permission" or "role" | The caller lacks required permissions. | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope. |
+| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance. |
+| **401 Unauthorized** | Authentication failed. | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header. |
+| Any other response | Unexpected error. | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
 
 ## 2. Create your first tags
 
diff --git a/src/content/docs/resource-tagging/how-to/index.mdx b/src/content/docs/resource-tagging/how-to/index.mdx
index daacb0f1c1aa2d4..8c39e93b47e1641 100644
--- a/src/content/docs/resource-tagging/how-to/index.mdx
+++ b/src/content/docs/resource-tagging/how-to/index.mdx
@@ -7,6 +7,6 @@ head:
     content: How-to guides
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/how-to/manage-tags.mdx b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
index 9625cc22be99763..813ad1a57752b9b 100644
--- a/src/content/docs/resource-tagging/how-to/manage-tags.mdx
+++ b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
@@ -75,9 +75,9 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags?reso
 
 ```json
 {
-	"environment": "production",
-	"team": "platform",
-	"cost-center": "engineering"
+  "environment": "production",
+  "team": "platform",
+  "cost-center": "engineering"
 }
 ```
 
diff --git a/src/content/docs/resource-tagging/reference/error-codes.mdx b/src/content/docs/resource-tagging/reference/error-codes.mdx
index 026f122644541f7..7f1cd73a0d758bf 100644
--- a/src/content/docs/resource-tagging/reference/error-codes.mdx
+++ b/src/content/docs/resource-tagging/reference/error-codes.mdx
@@ -8,19 +8,19 @@ description: Tagging API error codes, causes, and resolutions.
 
 ## Error code reference
 
-| Code   | HTTP status | Message                                        | Likely cause                                           | Resolution                                                                    |
-| ------ | ----------- | ---------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------- |
-| `1002` | 400         | Invalid set payload                            | Request body is malformed or missing required fields   | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
-| `1003` | 400         | `resource_type` and `resource_id` are required | Missing query parameters                               | Include both `resource_type` and `resource_id` in the query string            |
-| `1006` | 400         | Invalid resource type                          | Unsupported resource type                              | Use a [supported resource type](/resource-tagging/reference/resource-types/)  |
-| `1007` | 400         | tag parameter must be in format...             | Tag filter syntax is incorrect                         | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/)   |
-| `1009` | 400         | `tag_key` is required                          | Missing `tag_key` parameter                            | Include the `tag_key` path parameter                                          |
-| `1010` | 400         | too many tag filters (maximum 20)              | More than 20 `tag` query parameters                    | Reduce filters to 20 or fewer, or split across multiple requests              |
-| `1011` | 400         | tag key too long (maximum 256 characters)      | Tag key exceeds 256 characters                         | Shorten the tag key                                                           |
-| `1012` | 400         | tag value too long (maximum 1024 characters)   | Tag value exceeds 1,024 characters                     | Shorten the tag value                                                         |
-| `1013` | 400         | too many OR values in tag filter (maximum 10)  | More than 10 comma-separated values in a single filter | Split into multiple filters                                                   |
-| `1014` | 400         | Invalid tag key                                | Key contains invalid characters                        | Use only letters, digits, `_`, `.`, `-`                                       |
-| `1015` | 400         | Invalid delete payload                         | Delete request body is malformed                       | Verify the body includes `resource_type` and `resource_id`                    |
+| Code | HTTP status | Message | Likely cause | Resolution |
+| --- | --- | --- | --- | --- |
+| `1002` | 400 | Invalid set payload | Request body is malformed or missing required fields | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
+| `1003` | 400 | `resource_type` and `resource_id` are required | Missing query parameters | Include both `resource_type` and `resource_id` in the query string |
+| `1006` | 400 | Invalid resource type | Unsupported resource type | Use a [supported resource type](/resource-tagging/reference/resource-types/) |
+| `1007` | 400 | tag parameter must be in format... | Tag filter syntax is incorrect | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/) |
+| `1009` | 400 | `tag_key` is required | Missing `tag_key` parameter | Include the `tag_key` path parameter |
+| `1010` | 400 | too many tag filters (maximum 20) | More than 20 `tag` query parameters | Reduce filters to 20 or fewer, or split across multiple requests |
+| `1011` | 400 | tag key too long (maximum 256 characters) | Tag key exceeds 256 characters | Shorten the tag key |
+| `1012` | 400 | tag value too long (maximum 1024 characters) | Tag value exceeds 1,024 characters | Shorten the tag value |
+| `1013` | 400 | too many OR values in tag filter (maximum 10) | More than 10 comma-separated values in a single filter | Split into multiple filters |
+| `1014` | 400 | Invalid tag key | Key contains invalid characters | Use only letters, digits, `_`, `.`, `-` |
+| `1015` | 400 | Invalid delete payload | Delete request body is malformed | Verify the body includes `resource_type` and `resource_id` |
 
 :::note[Error 1007 note]
 The error message text references `:` as the tag filter separator (for example, `key:value`), but the API implementation uses `=` in query parameters (for example, `tag=key=value`). The error message is outdated — always use `=` when constructing tag filters.
diff --git a/src/content/docs/resource-tagging/reference/index.mdx b/src/content/docs/resource-tagging/reference/index.mdx
index 9361dd2c4b8a0cd..6de666492e69204 100644
--- a/src/content/docs/resource-tagging/reference/index.mdx
+++ b/src/content/docs/resource-tagging/reference/index.mdx
@@ -7,6 +7,6 @@ head:
     content: Reference
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/reference/limits.mdx b/src/content/docs/resource-tagging/reference/limits.mdx
index 85a5ee4696d5f45..350cb2973f6183a 100644
--- a/src/content/docs/resource-tagging/reference/limits.mdx
+++ b/src/content/docs/resource-tagging/reference/limits.mdx
@@ -8,14 +8,14 @@ description: API limits, tag key validation rules, and pagination behavior.
 
 ## API limits
 
-| Limit                         | Value            | Error code |
-| ----------------------------- | ---------------- | ---------- |
-| Maximum tags per account      | 10,000 (beta)    | N/A        |
-| Maximum tag key length        | 256 characters   | `1011`     |
-| Maximum tag value length      | 1,024 characters | `1012`     |
-| Maximum tag filters per query | 20               | `1010`     |
-| Maximum OR values per filter  | 10               | `1013`     |
-| Results per page              | 100 (fixed)      | N/A        |
+| Limit | Value | Error code |
+| --- | --- | --- |
+| Maximum tags per account | 10,000 (beta) | N/A |
+| Maximum tag key length | 256 characters | `1011` |
+| Maximum tag value length | 1,024 characters | `1012` |
+| Maximum tag filters per query | 20 | `1010` |
+| Maximum OR values per filter | 10 | `1013` |
+| Results per page | 100 (fixed) | N/A |
 
 When a limit is exceeded, the API returns `400 Bad Request` with the corresponding error code.
 
@@ -45,16 +45,16 @@ Tag keys must follow these character rules:
 
 ### Examples
 
-| Key           | Valid  | Reason                |
-| ------------- | ------ | --------------------- |
-| `environment` | Yes    | Letters only          |
-| `team_name`   | Yes    | Underscore            |
-| `cost-center` | Yes    | Hyphen                |
-| `owner.email` | Yes    | Period                |
-| `env123`      | Yes    | Letters and digits    |
-| `env name`    | **No** | Contains space        |
-| `team@work`   | **No** | Special character `@` |
-| (empty)       | **No** | Empty string          |
+| Key | Valid | Reason |
+| --- | --- | --- |
+| `environment` | Yes | Letters only |
+| `team_name` | Yes | Underscore |
+| `cost-center` | Yes | Hyphen |
+| `owner.email` | Yes | Period |
+| `env123` | Yes | Letters and digits |
+| `env name` | **No** | Contains space |
+| `team@work` | **No** | Special character `@` |
+| (empty) | **No** | Empty string |
 
 Invalid tag keys return `400 Bad Request` with error code `1014`.
 
@@ -63,7 +63,6 @@ Invalid tag keys return `400 Bad Request` with error code `1014`.
 List endpoints use cursor-based pagination with a fixed page size of 100. The page size is not configurable.
 
 Paginated endpoints:
-
 - `GET /accounts/{account_id}/tags/keys`
 - `GET /accounts/{account_id}/tags/resources`
 - `GET /accounts/{account_id}/tags/values/{tag_key}`
diff --git a/src/content/docs/resource-tagging/reference/resource-types.mdx b/src/content/docs/resource-tagging/reference/resource-types.mdx
index 0d2bab2a3ec669c..65c23a2da688ce7 100644
--- a/src/content/docs/resource-tagging/reference/resource-types.mdx
+++ b/src/content/docs/resource-tagging/reference/resource-types.mdx
@@ -12,51 +12,51 @@ The Tagging API supports the following resource types across account-level and z
 
 Use `/accounts/{account_id}/tags` endpoints for these resource types.
 
-| Resource type              | Required extra fields | Description                      |
-| -------------------------- | --------------------- | -------------------------------- |
-| `account`                  | None                  | The Cloudflare account itself    |
-| `access_application`       | None                  | Access application               |
-| `access_group`             | None                  | Access group                     |
-| `account_ruleset`          | None                  | Account-level ruleset            |
-| `ai_gateway`               | None                  | AI Gateway                       |
-| `alerting_policy`          | None                  | Notification policy              |
-| `alerting_webhook`         | None                  | Notification webhook destination |
-| `cloudflared_tunnel`       | None                  | Cloudflare Tunnel                |
-| `d1_database`              | None                  | D1 database                      |
-| `durable_object_namespace` | None                  | Durable Objects namespace        |
-| `gateway_list`             | None                  | Gateway list                     |
-| `gateway_rule`             | None                  | Gateway rule                     |
-| `image`                    | None                  | Cloudflare Image                 |
-| `kv_namespace`             | None                  | Workers KV namespace             |
-| `load_balancer_monitor`    | None                  | Load Balancer monitor            |
-| `load_balancer_pool`       | None                  | Load Balancer pool               |
-| `pages_project`            | None                  | Pages project                    |
-| `queue`                    | None                  | Queue                            |
-| `r2_bucket`                | None                  | R2 bucket                        |
-| `resource_share`           | None                  | Resource share                   |
-| `stream_live_input`        | None                  | Stream live input                |
-| `stream_video`             | None                  | Stream video                     |
-| `vectorize_index`          | None                  | Vectorize index                  |
-| `worker`                   | None                  | Workers script                   |
-| `worker_version`           | `worker_id`           | Specific version of a Worker     |
+| Resource type | Required extra fields | Description |
+| --- | --- | --- |
+| `account` | None | The Cloudflare account itself |
+| `access_application` | None | Access application |
+| `access_group` | None | Access group |
+| `account_ruleset` | None | Account-level ruleset |
+| `ai_gateway` | None | AI Gateway |
+| `alerting_policy` | None | Notification policy |
+| `alerting_webhook` | None | Notification webhook destination |
+| `cloudflared_tunnel` | None | Cloudflare Tunnel |
+| `d1_database` | None | D1 database |
+| `durable_object_namespace` | None | Durable Objects namespace |
+| `gateway_list` | None | Gateway list |
+| `gateway_rule` | None | Gateway rule |
+| `image` | None | Cloudflare Image |
+| `kv_namespace` | None | Workers KV namespace |
+| `load_balancer_monitor` | None | Load Balancer monitor |
+| `load_balancer_pool` | None | Load Balancer pool |
+| `pages_project` | None | Pages project |
+| `queue` | None | Queue |
+| `r2_bucket` | None | R2 bucket |
+| `resource_share` | None | Resource share |
+| `stream_live_input` | None | Stream live input |
+| `stream_video` | None | Stream video |
+| `vectorize_index` | None | Vectorize index |
+| `worker` | None | Workers script |
+| `worker_version` | `worker_id` | Specific version of a Worker |
 
 ## Zone-level resources
 
 Use `/zones/{zone_id}/tags` endpoints for these resource types.
 
-| Resource type                | Required extra fields   | Description                       |
-| ---------------------------- | ----------------------- | --------------------------------- |
-| `access_application_policy`  | `access_application_id` | Access application policy         |
-| `api_gateway_operation`      | None                    | API Gateway operation             |
-| `custom_certificate`         | None                    | Custom SSL certificate            |
-| `custom_hostname`            | None                    | Custom hostname (SSL for SaaS)    |
-| `dns_record`                 | None                    | DNS record                        |
-| `healthcheck`                | None                    | Health check                      |
-| `load_balancer`              | None                    | Load Balancer                     |
-| `managed_client_certificate` | None                    | Managed client certificate (mTLS) |
-| `worker_route`               | None                    | Worker route                      |
-| `zone`                       | None                    | DNS zone                          |
-| `zone_ruleset`               | None                    | Zone-level ruleset                |
+| Resource type | Required extra fields | Description |
+| --- | --- | --- |
+| `access_application_policy` | `access_application_id` | Access application policy |
+| `api_gateway_operation` | None | API Gateway operation |
+| `custom_certificate` | None | Custom SSL certificate |
+| `custom_hostname` | None | Custom hostname (SSL for SaaS) |
+| `dns_record` | None | DNS record |
+| `healthcheck` | None | Health check |
+| `load_balancer` | None | Load Balancer |
+| `managed_client_certificate` | None | Managed client certificate (mTLS) |
+| `worker_route` | None | Worker route |
+| `zone` | None | DNS zone |
+| `zone_ruleset` | None | Zone-level ruleset |
 
 ## Extra fields
 
diff --git a/src/content/docs/rules/normalization/settings.mdx b/src/content/docs/rules/normalization/settings.mdx
index 7243dde493afff1..5caa0fb2aa550f7 100644
--- a/src/content/docs/rules/normalization/settings.mdx
+++ b/src/content/docs/rules/normalization/settings.mdx
@@ -35,8 +35,8 @@ Default value: _Off_
 
 Configures URLs sent to the origin:
 
-- When enabled, requests sent to the origin are normalized.
-- When disabled, requests sent to the origin are not modified.
+  - When enabled, requests sent to the origin are normalized.
+  - When disabled, requests sent to the origin are not modified.
 
 You can only view and enable this option when **Normalize incoming URLs** is enabled.
 
diff --git a/src/content/docs/rules/snippets/when-to-use.mdx b/src/content/docs/rules/snippets/when-to-use.mdx
index 37954e262869ef1..e86e4a0e07433ec 100644
--- a/src/content/docs/rules/snippets/when-to-use.mdx
+++ b/src/content/docs/rules/snippets/when-to-use.mdx
@@ -86,7 +86,7 @@ Snippets are ideal for fast, cost-free request and response modifications at the
 | Route traffic dynamically between [origin servers](/rules/snippets/examples/serve-different-origin/)                                                                                                          |    ✅    |   ✅    |
 | [Authenticate](/rules/snippets/examples/auth-with-headers/) requests, [pre-sign](/cache/interaction-cloudflare-products/waf-snippets/) URLs, run [A/B testing](/rules/snippets/examples/ab-testing-same-url/) |    ✅    |   ✅    |
 | Define logic using [JavaScript and Web APIs](/workers/languages/javascript/)                                                                                                                                  |    ✅    |   ✅    |
-| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                           |    ❌    |   ✅    |
+| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                                       |    ❌    |   ✅    |
 | Store persistent data (for example, [KV](/kv/), [Durable Objects](/durable-objects/), and [D1](/d1/))                                                                                                         |    ❌    |   ✅    |
 | Build [APIs](/d1/tutorials/build-a-comments-api/) and [full-stack applications](/pages/framework-guides/deploy-an-astro-site/#video-tutorial)                                                                 |    ❌    |   ✅    |
 | Use TypeScript, Python, Rust, or other programming [languages](/workers/languages/)                                                                                                                           |    ❌    |   ✅    |
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
index d28441888bab606..7167193080e4368 100644
--- a/src/content/docs/rules/transform/managed-transforms/reference.mdx
+++ b/src/content/docs/rules/transform/managed-transforms/reference.mdx
@@ -87,6 +87,7 @@ Turning on [IP geolocation](/network/ip-geolocation/) will send a `cf-ipcountry`
 
 Cloudflare always converts non-ASCII characters to UTF-8 in HTTP request and response header values. This applies to location headers added by the **Add visitor location headers** managed transform.
 
+
 ### Add "True-Client-IP" header
 
 :::note
diff --git a/src/content/docs/ruleset-engine/about/index.mdx b/src/content/docs/ruleset-engine/about/index.mdx
index b2b96116594e34b..4627da09be58e13 100644
--- a/src/content/docs/ruleset-engine/about/index.mdx
+++ b/src/content/docs/ruleset-engine/about/index.mdx
@@ -9,17 +9,18 @@ sidebar:
 head:
   - tag: title
     content: About Ruleset Engine
+
 ---
 
 The Cloudflare Ruleset Engine allows you to create and deploy rules and rulesets. The engine syntax, inspired by the Wireshark Display Filter language, is defined by the [Rules language](/ruleset-engine/rules-language/). Cloudflare uses the Ruleset Engine in different products, allowing you to configure several products using the same basic syntax.
 
 There are several elements involved in the configuration and use of the Ruleset Engine. These elements are:
 
-- [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
-- [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
-- [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
+* [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
+* [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
+* [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
 
----
+***
 
 ## Get started
 
diff --git a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
index 4ead3afce0027eb..195f92316c007d2 100644
--- a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
+++ b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
@@ -7,4 +7,5 @@ title: Adjust an L3/4 DDoS rule
 external_link: /ddos-protection/managed-rulesets/network/network-overrides/configure-api/#configure-an-override-for-the-network-layer-ddos-attack-protection-managed-ruleset
 sidebar:
   order: 7
+
 ---
diff --git a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
index 5e0d01303a761d5..4e1b9c1603ab0bf 100644
--- a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
+++ b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
@@ -34,12 +34,14 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 :::note
 
+
 The Rulesets API endpoints require a value for `{account_id}` or `{zone_id}`.
 
 To retrieve a list of accounts you have access to, use the [List Accounts](/api/resources/accounts/methods/list/) operation. Note the IDs of the accounts you want to manage.
 
 To retrieve a list of zones you have access to, use the [List Zones](/api/resources/zones/methods/list/) operation. Note the IDs of the zones you want to manage.
 
+
 :::
 
 The Cloudflare Rulesets API supports the operations outlined below. Visit the associated links for API endpoints and examples.
@@ -47,235 +49,206 @@ The Cloudflare Rulesets API supports the operations outlined below. Visit the as
 ## List and view rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Method</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">
-					List existing rulesets
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the list of existing rulesets at the account level or at the
-					zone level.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">
-					View a specific ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the properties of the most recent version of a specific
-					ruleset.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
-					List all versions of a ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>Returns a list of all the versions of a ruleset.</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
-					View a specific version of a ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the configuration of a specific version of a ruleset,
-					including its rules.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
-					List rules in a managed ruleset with a specific tag
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns a list of all the rules in a managed ruleset with a specific
-					tag.
-				</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Method</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">List existing rulesets</a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the list of existing rulesets at the account level or at the zone level.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">View a specific ruleset</a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the properties of the most recent version of a specific ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
+          List all versions of a ruleset
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns a list of all the versions of a ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
+          View a specific version of a ruleset
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the configuration of a specific version of a ruleset, including its rules.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
+          List rules in a managed ruleset with a specific tag
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns a list of all the rules in a managed ruleset with a specific tag.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Create rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
-			</td>
-			<td>
-				<code>POST</code>
-			</td>
-			<td>
-				<p>Creates a new ruleset or a new phase entry point.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
+      </td>
+      <td>
+        <code>POST</code>
+      </td>
+      <td>
+        <p>Creates a new ruleset or a new phase entry point.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Update and deploy rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/update/">
-					Update or deploy a ruleset
-				</a>
-			</td>
-			<td>
-				<code>PUT</code>
-			</td>
-			<td>
-				<p>
-					Updates the basic properties of a ruleset and the list of rules in the
-					ruleset.
-					<br />
-					Allows you to configure the execution of managed rulesets.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/add-rule/">
-					Add a rule to a ruleset
-				</a>
-			</td>
-			<td>
-				<code>POST</code>
-			</td>
-			<td>
-				<p>
-					Adds a single rule to an existing ruleset.
-					<br />
-					Allows you to add a single rule without having to include all the
-					existing ruleset rules in the request.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/update-rule/">
-					Update a rule in a ruleset
-				</a>
-			</td>
-			<td>
-				<code>PATCH</code>
-			</td>
-			<td>
-				<p>
-					Updates the definition of a single rule within a ruleset.
-					<br />
-					Allows you to change the order of a rule in a ruleset.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete-rule/">
-					Delete a rule in a ruleset
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes a single rule in a ruleset.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/update/">Update or deploy a ruleset</a>
+      </td>
+      <td>
+        <code>PUT</code>
+      </td>
+      <td>
+        <p>
+          Updates the basic properties of a ruleset and the list of rules in the ruleset.
+          <br />
+          Allows you to configure the execution of managed rulesets.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/add-rule/">Add a rule to a ruleset</a>
+      </td>
+      <td>
+        <code>POST</code>
+      </td>
+      <td>
+        <p>
+          Adds a single rule to an existing ruleset.
+          <br />
+          Allows you to add a single rule without having to include all the existing ruleset rules
+          in the request.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/update-rule/">Update a rule in a ruleset</a>
+      </td>
+      <td>
+        <code>PATCH</code>
+      </td>
+      <td>
+        <p>
+          Updates the definition of a single rule within a ruleset.
+          <br />
+          Allows you to change the order of a rule in a ruleset.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete-rule/">Delete a rule in a ruleset</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes a single rule in a ruleset.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Delete rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">
-					Delete a ruleset
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes all the versions of a ruleset.</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">
-					Delete a ruleset version
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes a specific version of a ruleset.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">Delete a ruleset</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes all the versions of a ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">Delete a ruleset version</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes a specific version of a ruleset.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/docs/sandbox/bridge/http-api.mdx b/src/content/docs/sandbox/bridge/http-api.mdx
index ba425ec0d9cf393..8454191fa57021e 100644
--- a/src/content/docs/sandbox/bridge/http-api.mdx
+++ b/src/content/docs/sandbox/bridge/http-api.mdx
@@ -28,10 +28,10 @@ When `SANDBOX_API_KEY` is not configured, authentication is skipped for local de
 
 The bridge serves its own API documentation:
 
-| Method | Route              | Description                          |
-| ------ | ------------------ | ------------------------------------ |
-| `GET`  | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
-| `GET`  | `/v1/openapi`      | Interactive HTML documentation.      |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
+| `GET` | `/v1/openapi` | Interactive HTML documentation. |
 
 Both routes accept authentication via Bearer header or `?token=` query parameter.
 
@@ -39,25 +39,25 @@ When running locally with `npm run dev`, open `http://localhost:8787/v1/openapi`
 
 ## Sandbox lifecycle
 
-| Method   | Route                     | Description                                                   |
-| -------- | ------------------------- | ------------------------------------------------------------- |
-| `POST`   | `/v1/sandbox`             | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`.       |
-| `DELETE` | `/v1/sandbox/:id`         | Destroy the sandbox container. Returns `204`.                 |
-| `GET`    | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox` | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id` | Destroy the sandbox container. Returns `204`. |
+| `GET` | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
 
 ## Command execution
 
-| Method | Route                  | Description                                           |
-| ------ | ---------------------- | ----------------------------------------------------- |
+| Method | Route | Description |
+|---|---|---|
 | `POST` | `/v1/sandbox/:id/exec` | Run a command. Response is an SSE stream (see below). |
 
 The `/exec` endpoint accepts a JSON body:
 
 ```json
 {
-	"argv": ["sh", "-lc", "echo hello"],
-	"timeout_ms": 10000,
-	"cwd": "/workspace"
+  "argv": ["sh", "-lc", "echo hello"],
+  "timeout_ms": 10000,
+  "cwd": "/workspace"
 }
 ```
 
@@ -69,27 +69,27 @@ Each element of the `argv` array is escaped using ANSI-C `$'...'` quoting before
 
 The response is a `text/event-stream` with the following event types:
 
-| Event    | Data                          | Description                        |
-| -------- | ----------------------------- | ---------------------------------- |
-| `stdout` | Base64-encoded chunk          | Standard output from the command.  |
-| `stderr` | Base64-encoded chunk          | Standard error from the command.   |
-| `exit`   | `{"exit_code": N}`            | Command completed. Terminal event. |
-| `error`  | `{"error": "…", "code": "…"}` | Command failed. Terminal event.    |
+| Event | Data | Description |
+|---|---|---|
+| `stdout` | Base64-encoded chunk | Standard output from the command. |
+| `stderr` | Base64-encoded chunk | Standard error from the command. |
+| `exit` | `{"exit_code": N}` | Command completed. Terminal event. |
+| `error` | `{"error": "…", "code": "…"}` | Command failed. Terminal event. |
 
 ## File operations
 
-| Method | Route                    | Description                                                                  |
-| ------ | ------------------------ | ---------------------------------------------------------------------------- |
-| `GET`  | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`).                 |
-| `PUT`  | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`). |
+| `PUT` | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
 
 The file path is encoded in the URL after `/file/`. All paths must resolve within `/workspace`. Path traversal attempts (for example, `../../etc/passwd`) are rejected.
 
 ## Workspace persistence
 
-| Method | Route                     | Description                                                        |
-| ------ | ------------------------- | ------------------------------------------------------------------ |
-| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes.    |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes. |
 | `POST` | `/v1/sandbox/:id/hydrate` | Populate `/workspace` from a tar archive sent as the request body. |
 
 The `/persist` endpoint accepts an optional `excludes` query parameter — a comma-separated list of relative paths to exclude from the archive.
@@ -98,10 +98,10 @@ The `/hydrate` endpoint accepts a raw tar payload up to 32 MiB.
 
 ## Bucket mounts
 
-| Method | Route                     | Description                                         |
-| ------ | ------------------------- | --------------------------------------------------- |
-| `POST` | `/v1/sandbox/:id/mount`   | Mount an S3-compatible bucket as a local directory. |
-| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket.                |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/mount` | Mount an S3-compatible bucket as a local directory. |
+| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket. |
 
 The `/mount` endpoint accepts a JSON body. Two flows are supported:
 
@@ -111,12 +111,12 @@ Omit `endpoint` and pass the Worker R2 binding name in `bucket`:
 
 ```json
 {
-	"bucket": "MY_BUCKET",
-	"mountPath": "/mnt/data",
-	"options": {
-		"readOnly": false,
-		"prefix": "/subdir"
-	}
+  "bucket": "MY_BUCKET",
+  "mountPath": "/mnt/data",
+  "options": {
+    "readOnly": false,
+    "prefix": "/subdir"
+  }
 }
 ```
 
@@ -126,17 +126,17 @@ For an explicit S3-compatible endpoint mount, include `endpoint` and optionally
 
 ```json
 {
-	"bucket": "my-r2-bucket",
-	"mountPath": "/mnt/data",
-	"options": {
-		"endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
-		"readOnly": false,
-		"prefix": "/subdir",
-		"credentials": {
-			"accessKeyId": "...",
-			"secretAccessKey": "..."
-		}
-	}
+  "bucket": "my-r2-bucket",
+  "mountPath": "/mnt/data",
+  "options": {
+    "endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
+    "readOnly": false,
+    "prefix": "/subdir",
+    "credentials": {
+      "accessKeyId": "...",
+      "secretAccessKey": "..."
+    }
+  }
 }
 ```
 
@@ -144,10 +144,10 @@ When `endpoint` is provided, `bucket` means the remote bucket name. Credentials
 
 ## Sessions
 
-| Method   | Route                          | Description                                         |
-| -------- | ------------------------------ | --------------------------------------------------- |
-| `POST`   | `/v1/sandbox/:id/session`      | Create a session. Returns `{"id": "<session-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`.                    |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/session` | Create a session. Returns `{"id": "<session-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`. |
 
 Sessions isolate working directory, environment variables, and command execution state within a sandbox. Pass the `Session-Id` header on `/exec`, `/file/*`, and `/pty` requests to scope them to a session.
 
@@ -155,35 +155,35 @@ When no `Session-Id` header is provided, requests use the sandbox default sessio
 
 ## Terminal (PTY)
 
-| Method | Route                 | Description                         |
-| ------ | --------------------- | ----------------------------------- |
-| `GET`  | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
 
 Query parameters:
 
-| Parameter | Type   | Default | Description                              |
-| --------- | ------ | ------- | ---------------------------------------- |
-| `cols`    | number | `80`    | Terminal width in columns.               |
-| `rows`    | number | `24`    | Terminal height in rows.                 |
-| `shell`   | string | —       | Shell binary (for example, `/bin/bash`). |
-| `session` | string | —       | Session ID for session-scoped PTY.       |
+| Parameter | Type | Default | Description |
+|---|---|---|---|
+| `cols` | number | `80` | Terminal width in columns. |
+| `rows` | number | `24` | Terminal height in rows. |
+| `shell` | string | — | Shell binary (for example, `/bin/bash`). |
+| `session` | string | — | Session ID for session-scoped PTY. |
 
 The WebSocket carries binary frames for terminal I/O and JSON text frames for control messages:
 
-| Direction        | Frame type  | Content                                                                        |
-| ---------------- | ----------- | ------------------------------------------------------------------------------ |
-| Client to server | Binary      | UTF-8 encoded keystrokes.                                                      |
-| Server to client | Binary      | Terminal output including ANSI escape sequences.                               |
+| Direction | Frame type | Content |
+|---|---|---|
+| Client to server | Binary | UTF-8 encoded keystrokes. |
+| Server to client | Binary | Terminal output including ANSI escape sequences. |
 | Client to server | Text (JSON) | Control messages (for example, `{"type": "resize", "cols": 120, "rows": 30}`). |
-| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`).                                    |
+| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`). |
 
 ## Warm pool
 
-| Method | Route                         | Description                     |
-| ------ | ----------------------------- | ------------------------------- |
-| `GET`  | `/v1/pool/stats`              | Current pool statistics.        |
-| `POST` | `/v1/pool/prime`              | Start the warm pool alarm loop. |
-| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers.  |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/pool/stats` | Current pool statistics. |
+| `POST` | `/v1/pool/prime` | Start the warm pool alarm loop. |
+| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers. |
 
 The warm pool pre-starts sandbox containers so new sessions boot instantly. Configure it with environment variables in `wrangler.jsonc`:
 
@@ -201,9 +201,9 @@ A cron trigger (`* * * * *`) primes the pool automatically after deployment. Set
 
 ## Health check
 
-| Method | Route     | Description                                             |
-| ------ | --------- | ------------------------------------------------------- |
-| `GET`  | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
 
 ## Related resources
 
diff --git a/src/content/docs/sandbox/concepts/containers.mdx b/src/content/docs/sandbox/concepts/containers.mdx
index e1a711233feb34b..dd9a725669a262e 100644
--- a/src/content/docs/sandbox/concepts/containers.mdx
+++ b/src/content/docs/sandbox/concepts/containers.mdx
@@ -30,18 +30,16 @@ apt-get update && apt-get install -y redis-server
 The container provides a standard Linux filesystem. You can read and write anywhere you have permissions.
 
 **Standard directories**:
-
 - `/workspace` - Default working directory for user code
 - `/tmp` - Temporary files
 - `/home` - User home directory
 - `/usr/bin`, `/usr/local/bin` - Executable binaries
 
 **Example**:
-
 ```typescript
-await sandbox.writeFile("/workspace/app.py", 'print("Hello")');
-await sandbox.writeFile("/tmp/cache.json", "{}");
-await sandbox.exec("ls -la /workspace");
+await sandbox.writeFile('/workspace/app.py', 'print("Hello")');
+await sandbox.writeFile('/tmp/cache.json', '{}');
+await sandbox.exec('ls -la /workspace');
 ```
 
 ## Process management
@@ -49,23 +47,20 @@ await sandbox.exec("ls -la /workspace");
 Processes run as you'd expect in a regular Linux environment.
 
 **Foreground processes** (`exec()`):
-
 ```typescript
-const result = await sandbox.exec("npm test");
+const result = await sandbox.exec('npm test');
 // Waits for completion, returns output
 ```
 
 **Background processes** (`startProcess()`):
-
 ```typescript
-const process = await sandbox.startProcess("node server.js");
+const process = await sandbox.startProcess('node server.js');
 // Returns immediately, process runs in background
 ```
 
 ## Network capabilities
 
 **Outbound connections** work:
-
 ```bash
 curl https://api.example.com/data
 pip install requests
@@ -73,10 +68,9 @@ npm install express
 ```
 
 **Inbound connections** require port exposure:
-
 ```typescript
 const { hostname } = new URL(request.url);
-await sandbox.startProcess("python -m http.server 8000");
+await sandbox.startProcess('python -m http.server 8000');
 const exposed = await sandbox.exposePort(8000, { hostname });
 console.log(exposed.url); // Public URL
 ```
@@ -86,7 +80,6 @@ When using `wrangler dev`, you must add `EXPOSE` directives to your Dockerfile f
 :::
 
 **Localhost** works within sandbox:
-
 ```bash
 redis-server &      # Start server
 redis-cli ping      # Connect locally
@@ -95,18 +88,15 @@ redis-cli ping      # Connect locally
 ## Security
 
 **Between sandboxes** (isolated):
-
 - Each sandbox is a separate container
 - Filesystem, memory and network are all isolated
 
 **Within sandbox** (shared):
-
 - All processes see the same files
 - Processes can communicate with each other
 - Environment variables are session-scoped
 
 To run untrusted code, use separate sandboxes per user:
-
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
@@ -114,7 +104,6 @@ const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ## Limitations
 
 **Cannot**:
-
 - Load kernel modules or access host hardware
 
 ## Related resources
diff --git a/src/content/docs/sandbox/concepts/preview-urls.mdx b/src/content/docs/sandbox/concepts/preview-urls.mdx
index 43eecbf9c151321..7fdf50c71ce90b4 100644
--- a/src/content/docs/sandbox/concepts/preview-urls.mdx
+++ b/src/content/docs/sandbox/concepts/preview-urls.mdx
@@ -24,9 +24,9 @@ const req = await fetch(`${tunnel.url}/api/users`); // => GET http://localhost:8
 
 Cloudflare Tunnel support currently has the following limitations:
 
-- No control over generated URL.
-- No authentication mechanism beyond randomly generated URL.
-- Each URL uses an additional `cloudflared` process on the sandbox.
+ - No control over generated URL.
+ - No authentication mechanism beyond randomly generated URL.
+ - Each URL uses an additional `cloudflared` process on the sandbox.
 
 :::note[Production requires custom domain]
 We are working on production deployments, custom hostnames and authentication for Cloudflare Tunnel support. In the mean time we recommend using `exposePort()` and `proxyToSandbox()` documented below under [Production usage, stable URLs and custom domains](#).
diff --git a/src/content/docs/sandbox/concepts/sandboxes.mdx b/src/content/docs/sandbox/concepts/sandboxes.mdx
index cd86f4ac0b8f21d..e0828106d246dbd 100644
--- a/src/content/docs/sandbox/concepts/sandboxes.mdx
+++ b/src/content/docs/sandbox/concepts/sandboxes.mdx
@@ -126,8 +126,8 @@ try {
 Containers with [`keepAlive: true`](/sandbox/configuration/sandbox-options/#keepalive) require explicit management since they do not timeout automatically:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, "persistent-task", {
-	keepAlive: true,
+const sandbox = getSandbox(env.Sandbox, 'persistent-task', {
+  keepAlive: true
 });
 
 // Later, when done with long-running work
diff --git a/src/content/docs/sandbox/concepts/security.mdx b/src/content/docs/sandbox/concepts/security.mdx
index 9954cb9833e9732..5c15d8d4295ba00 100644
--- a/src/content/docs/sandbox/concepts/security.mdx
+++ b/src/content/docs/sandbox/concepts/security.mdx
@@ -36,7 +36,7 @@ For complete isolation, use separate sandboxes per user:
 const userSandbox = getSandbox(env.Sandbox, `user-${userId}`);
 
 // Bad - Users sharing one sandbox
-const shared = getSandbox(env.Sandbox, "shared");
+const shared = getSandbox(env.Sandbox, 'shared');
 // Users can read each other's files!
 ```
 
@@ -53,12 +53,12 @@ await sandbox.exec(`cat ${filename}`);
 // User could input: "file.txt; rm -rf /"
 
 // Safe - validate input
-const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, "");
+const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, '');
 await sandbox.exec(`cat ${filename}`);
 
 // Better - use file API
-await sandbox.writeFile("/tmp/input", userInput);
-await sandbox.exec("cat /tmp/input");
+await sandbox.writeFile('/tmp/input', userInput);
+await sandbox.exec('cat /tmp/input');
 ```
 
 ## Authentication
@@ -69,16 +69,16 @@ Sandbox IDs provide basic access control but aren't cryptographically secure. Ad
 
 ```typescript
 export default {
-	async fetch(request: Request, env: Env): Promise<Response> {
-		const userId = await authenticate(request);
-		if (!userId) {
-			return new Response("Unauthorized", { status: 401 });
-		}
-
-		// User can only access their sandbox
-		const sandbox = getSandbox(env.Sandbox, userId);
-		return Response.json({ authorized: true });
-	},
+  async fetch(request: Request, env: Env): Promise<Response> {
+    const userId = await authenticate(request);
+    if (!userId) {
+      return new Response('Unauthorized', { status: 401 });
+    }
+
+    // User can only access their sandbox
+    const sandbox = getSandbox(env.Sandbox, userId);
+    return Response.json({ authorized: true });
+  }
 };
 ```
 
@@ -125,18 +125,15 @@ Use environment variables, not hardcoded secrets:
 
 ```typescript
 // Bad - hardcoded in file
-await sandbox.writeFile(
-	"/workspace/config.js",
-	`
+await sandbox.writeFile('/workspace/config.js', `
   const API_KEY = 'sk_live_abc123';
-`,
-);
+`);
 
 // Good - use environment variables
-await sandbox.startProcess("node app.js", {
-	env: {
-		API_KEY: env.API_KEY, // From Worker environment binding
-	},
+await sandbox.startProcess('node app.js', {
+  env: {
+    API_KEY: env.API_KEY,  // From Worker environment binding
+  }
 });
 ```
 
@@ -144,10 +141,10 @@ Clean up temporary sensitive data:
 
 ```typescript
 try {
-	await sandbox.writeFile("/tmp/sensitive.txt", secretData);
-	await sandbox.exec("python process.py /tmp/sensitive.txt");
+  await sandbox.writeFile('/tmp/sensitive.txt', secretData);
+  await sandbox.exec('python process.py /tmp/sensitive.txt');
 } finally {
-	await sandbox.deleteFile("/tmp/sensitive.txt");
+  await sandbox.deleteFile('/tmp/sensitive.txt');
 }
 ```
 
@@ -181,34 +178,30 @@ This pattern is useful when accessing GitHub for private repository operations,
 ## Best practices
 
 **Use separate sandboxes for isolation**:
-
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
 
 **Validate all inputs**:
-
 ```typescript
-const safe = input.replace(/[^a-zA-Z0-9._-]/g, "");
+const safe = input.replace(/[^a-zA-Z0-9._-]/g, '');
 await sandbox.exec(`command ${safe}`);
 ```
 
 **Use environment variables for secrets**:
-
 ```typescript
-await sandbox.startProcess("node app.js", {
-	env: { API_KEY: env.API_KEY },
+await sandbox.startProcess('node app.js', {
+  env: { API_KEY: env.API_KEY }
 });
 ```
 
 **Clean up temporary resources**:
-
 ```typescript
 try {
-	const sandbox = getSandbox(env.Sandbox, sessionId);
-	await sandbox.exec("npm test");
+  const sandbox = getSandbox(env.Sandbox, sessionId);
+  await sandbox.exec('npm test');
 } finally {
-	await sandbox.destroy();
+  await sandbox.destroy();
 }
 ```
 
diff --git a/src/content/docs/sandbox/concepts/sessions.mdx b/src/content/docs/sandbox/concepts/sessions.mdx
index dd054b3036ce8f7..1697cf6e8795d7f 100644
--- a/src/content/docs/sandbox/concepts/sessions.mdx
+++ b/src/content/docs/sandbox/concepts/sessions.mdx
@@ -18,14 +18,14 @@ Sessions are bash shell execution contexts within a sandbox. Think of them like
 Every sandbox has a default session that maintains shell state between commands while the container is active:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, "my-sandbox");
+const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
 
 // These commands run in the default session
 await sandbox.exec("cd /app");
-await sandbox.exec("pwd"); // Output: /app
+await sandbox.exec("pwd");  // Output: /app
 
 await sandbox.exec("export MY_VAR=hello");
-await sandbox.exec("echo $MY_VAR"); // Output: hello
+await sandbox.exec("echo $MY_VAR");  // Output: hello
 ```
 
 Working directory, environment variables, and exported variables carry over between commands. This state resets if the container restarts due to inactivity.
@@ -36,7 +36,7 @@ The container automatically creates sessions on first use. If you reference a no
 
 ```typescript
 // This session doesn't exist yet
-const result = await sandbox.exec("echo hello", { sessionId: "new-session" });
+const result = await sandbox.exec('echo hello', { sessionId: 'new-session' });
 // Container automatically creates 'new-session' with defaults:
 // - cwd: '/workspace'
 // - env: {} (empty)
@@ -47,15 +47,15 @@ This behavior is particularly relevant after deleting a session:
 ```typescript
 // Create and configure a session
 const session = await sandbox.createSession({
-	id: "temp",
-	env: { MY_VAR: "value" },
+  id: 'temp',
+  env: { MY_VAR: 'value' }
 });
 
 // Delete the session
-await sandbox.deleteSession("temp");
+await sandbox.deleteSession('temp');
 
 // Using the same session ID again works - auto-created with defaults
-const result = await sandbox.exec("echo $MY_VAR", { sessionId: "temp" });
+const result = await sandbox.exec('echo $MY_VAR', { sessionId: 'temp' });
 // Output: (empty) - MY_VAR is not set in the freshly created session
 ```
 
@@ -67,15 +67,15 @@ Create additional sessions for isolated shell contexts:
 
 ```typescript
 const buildSession = await sandbox.createSession({
-	id: "build",
-	env: { NODE_ENV: "production" },
-	cwd: "/build",
+  id: "build",
+  env: { NODE_ENV: "production" },
+  cwd: "/build"
 });
 
 const testSession = await sandbox.createSession({
-	id: "test",
-	env: { NODE_ENV: "test" },
-	cwd: "/test",
+  id: "test",
+  env: { NODE_ENV: "test" },
+  cwd: "/test"
 });
 
 // Different shell contexts
@@ -87,8 +87,8 @@ You can also set a default command timeout for all commands in a session:
 
 ```typescript
 const session = await sandbox.createSession({
-	id: "ci",
-	commandTimeoutMs: 30000, // 30s timeout for all commands
+  id: "ci",
+  commandTimeoutMs: 30000 // 30s timeout for all commands
 });
 
 await session.exec("npm test"); // Times out after 30s if still running
@@ -101,27 +101,24 @@ Individual commands can override the session timeout with the `timeout` option o
 Each session has its own:
 
 **Shell environment**:
-
 ```typescript
 await session1.exec("export MY_VAR=hello");
-await session2.exec("echo $MY_VAR"); // Empty - different shell
+await session2.exec("echo $MY_VAR");  // Empty - different shell
 ```
 
 **Working directory**:
-
 ```typescript
 await session1.exec("cd /workspace/project1");
-await session2.exec("pwd"); // Different working directory
+await session2.exec("pwd");  // Different working directory
 ```
 
 **Environment variables** (set via `createSession` options):
-
 ```typescript
 const session1 = await sandbox.createSession({
-	env: { API_KEY: "key-1" },
+  env: { API_KEY: 'key-1' }
 });
 const session2 = await sandbox.createSession({
-	env: { API_KEY: "key-2" },
+  env: { API_KEY: 'key-2' }
 });
 ```
 
@@ -130,47 +127,42 @@ const session2 = await sandbox.createSession({
 All sessions in a sandbox share:
 
 **Filesystem**:
-
 ```typescript
-await session1.writeFile("/workspace/file.txt", "data");
-await session2.readFile("/workspace/file.txt"); // Can read it
+await session1.writeFile('/workspace/file.txt', 'data');
+await session2.readFile('/workspace/file.txt');  // Can read it
 ```
 
 **Processes**:
-
 ```typescript
-await session1.startProcess("node server.js");
-await session2.listProcesses(); // Sees the server
+await session1.startProcess('node server.js');
+await session2.listProcesses();  // Sees the server
 ```
 
 ## When to use sessions
 
 **Use sessions when**:
-
 - You need isolated shell state for different tasks
 - Running parallel operations with different environments
 - Keeping AI agent credentials separate from app runtime
 
 **Example - separate dev and runtime environments**:
-
 ```typescript
 // Phase 1: AI agent writes code (with API keys)
 const devSession = await sandbox.createSession({
-	id: "dev",
-	env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY },
+  id: "dev",
+  env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY }
 });
 await devSession.exec('ai-tool "build a web server"');
 
 // Phase 2: Run the code (without API keys)
 const appSession = await sandbox.createSession({
-	id: "app",
-	env: { PORT: "3000" },
+  id: "app",
+  env: { PORT: "3000" }
 });
 await appSession.exec("node server.js");
 ```
 
 **Use separate sandboxes when**:
-
 - You need complete isolation (untrusted code)
 - Different users require fully separated environments
 - Independent resource allocation is needed
@@ -180,31 +172,28 @@ await appSession.exec("node server.js");
 ### Session cleanup
 
 **Clean up temporary sessions** to free resources while keeping the sandbox running:
-
 ```typescript
 try {
-	const session = await sandbox.createSession({ id: "temp" });
-	await session.exec("command");
+  const session = await sandbox.createSession({ id: 'temp' });
+  await session.exec('command');
 } finally {
-	await sandbox.deleteSession("temp");
+  await sandbox.deleteSession('temp');
 }
 ```
 
 **Default session cannot be deleted**:
-
 ```typescript
 // This throws an error
-await sandbox.deleteSession("default");
+await sandbox.deleteSession('default');
 // Error: Cannot delete default session. Use sandbox.destroy() instead.
 ```
 
 ### Filesystem isolation
 
 **Sessions share filesystem** - file operations affect all sessions:
-
 ```typescript
 // Bad - affects all sessions
-await session.exec("rm -rf /workspace/*");
+await session.exec('rm -rf /workspace/*');
 
 // For untrusted code isolation, use separate sandboxes
 const userSandbox = getSandbox(env.Sandbox, userId);
diff --git a/src/content/docs/sandbox/configuration/environment-variables.mdx b/src/content/docs/sandbox/configuration/environment-variables.mdx
index 2bd802277756cba..522821f21e1c931 100644
--- a/src/content/docs/sandbox/configuration/environment-variables.mdx
+++ b/src/content/docs/sandbox/configuration/environment-variables.mdx
@@ -18,10 +18,10 @@ These environment variables configure how the Sandbox SDK behaves. Set these as
 
 ### SANDBOX_TRANSPORT
 
-|             |                           |
-| ----------- | ------------------------- |
-| **Type**    | `"http"` \| `"websocket"` |
-| **Default** | `"http"`                  |
+| | |
+|---|---|
+| **Type** | `"http"` \| `"websocket"` |
+| **Default** | `"http"` |
 
 Controls the transport protocol for SDK-to-container communication. WebSocket transport multiplexes all operations over a single persistent connection, avoiding [subrequest limits](/workers/platform/limits/#subrequests) when performing many SDK operations per request.
 
@@ -39,10 +39,10 @@ See [Transport modes](/sandbox/configuration/transport/) for a complete guide in
 
 ### COMMAND_TIMEOUT_MS
 
-|             |                         |
-| ----------- | ----------------------- |
-| **Type**    | `number` (milliseconds) |
-| **Default** | None (no timeout)       |
+| | |
+|---|---|
+| **Type** | `number` (milliseconds) |
+| **Default** | None (no timeout) |
 
 Sets a global default timeout for every `exec()` call. When set, any command that exceeds this duration raises an error on the caller side and closes the connection.
 
@@ -95,9 +95,9 @@ await sandbox.setEnvVars({
 
 ```typescript
 await sandbox.setEnvVars({
-	API_KEY: "new-key", // Sets API_KEY
-	OLD_SECRET: undefined, // Unsets OLD_SECRET
-	DEBUG_MODE: null, // Unsets DEBUG_MODE
+	API_KEY: 'new-key',     // Sets API_KEY
+	OLD_SECRET: undefined,  // Unsets OLD_SECRET
+	DEBUG_MODE: null        // Unsets DEBUG_MODE
 });
 ```
 
@@ -153,12 +153,12 @@ The Sandbox SDK supports unsetting environment variables by passing `undefined`
 ```typescript
 await sandbox.setEnvVars({
 	// Set new values
-	API_KEY: "new-key",
+	API_KEY: 'new-key',
 	DATABASE_URL: env.DATABASE_URL,
 
 	// Unset variables (removes them from the environment)
 	OLD_API_KEY: undefined,
-	TEMP_TOKEN: null,
+	TEMP_TOKEN: null
 });
 ```
 
@@ -172,7 +172,7 @@ await sandbox.setEnvVars({
 
 ```typescript
 // Use a temporary token
-await sandbox.setEnvVars({ TEMP_TOKEN: "abc123" });
+await sandbox.setEnvVars({ TEMP_TOKEN: 'abc123' });
 await sandbox.exec('curl -H "Authorization: $TEMP_TOKEN" api.example.com');
 
 // Clean up the token
@@ -184,8 +184,8 @@ await sandbox.setEnvVars({ TEMP_TOKEN: undefined });
 ```typescript
 await sandbox.setEnvVars({
 	API_KEY: env.API_KEY,
-	DEBUG_MODE: env.NODE_ENV === "development" ? "true" : undefined,
-	PROFILING: env.ENABLE_PROFILING ? "true" : undefined,
+	DEBUG_MODE: env.NODE_ENV === 'development' ? 'true' : undefined,
+	PROFILING: env.ENABLE_PROFILING ? 'true' : undefined
 });
 ```
 
diff --git a/src/content/docs/sandbox/configuration/transport.mdx b/src/content/docs/sandbox/configuration/transport.mdx
index 18e5f33fc1b515d..dce27bacce1ff87 100644
--- a/src/content/docs/sandbox/configuration/transport.mdx
+++ b/src/content/docs/sandbox/configuration/transport.mdx
@@ -22,6 +22,7 @@ The Sandbox SDK supports three transport modes for communication between the Dur
 - **NEW: RPC transport** - All SDK operations are multiplexed over a single persistent WebSocket connection. Will replace HTTP as the default transport in future. Available since 0.9.1.
 - **Deprecated: WebSocket transport** - All SDK operations are multiplexed over a single persistent WebSocket. Superseded by RPC transport which uses an improved protocol.
 
+
 ## When to use RPC transport
 
 Use the RPC transport when your Worker or Durable Object makes many SDK operations per request. This avoids hitting [subrequest limits](/workers/platform/limits/#subrequests).
@@ -111,13 +112,11 @@ No application code changes are needed. The SDK automatically uses the configure
 ### Connection lifecycle
 
 **HTTP transport:**
-
 - Creates a new HTTP request for each SDK operation
 - No persistent connection
 - Each request is independent and stateless
 
 **RPC transport:**
-
 - Establishes a WebSocket connection on the first SDK operation
 - Maintains the persistent connection for all subsequent operations
 - Connection is closed when the sandbox sleeps or is evicted
@@ -137,7 +136,6 @@ Your code remains identical regardless of transport mode.
 All transports provide identical error handling behavior. The SDK automatically retries on transient errors (like 503 responses) with exponential backoff.
 
 WebSocket-specific behavior:
-
 - Connection failures trigger automatic reconnection
 - The SDK transparently handles WebSocket disconnections
 - In-flight operations are not lost during reconnection
@@ -156,6 +154,7 @@ Switching between transports requires no code changes.
 Using the `rpc` transport requires version 0.9.1 or newer. If you are using an older version of the Sandbox SDK upgrade and deploy your application with the newer `@cloudflare/sandbox` and image first. Otherwise there will be issues with newer SDK clients attempting to connect to older sandboxes that do not support the new transport.
 :::
 
+
 Add `SANDBOX_TRANSPORT` to your `wrangler.jsonc`:
 
 <WranglerConfig>
diff --git a/src/content/docs/sandbox/guides/production-deployment.mdx b/src/content/docs/sandbox/guides/production-deployment.mdx
index c0f0ed75abf6508..27c08a0c143f74a 100644
--- a/src/content/docs/sandbox/guides/production-deployment.mdx
+++ b/src/content/docs/sandbox/guides/production-deployment.mdx
@@ -24,11 +24,10 @@ The `.workers.dev` domain does not support wildcard subdomains, so production de
 If your worker runs on a subdomain (for example, `sandbox.yourdomain.com`), preview URLs become second-level wildcards like `*.sandbox.yourdomain.com`. Cloudflare's Universal SSL only covers first-level wildcards (`*.yourdomain.com`), so you need a certificate covering `*.sandbox.yourdomain.com`. Without it, preview URLs will fail with TLS handshake errors.
 
 You have three options:
-
 - **Deploy on the apex domain** (`yourdomain.com`) so preview URLs stay at the first level (`*.yourdomain.com`), which Universal SSL covers automatically. This is the simplest option.
 - **Use [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/)** ($10/month) to provision a certificate for `*.sandbox.yourdomain.com` through the Cloudflare dashboard.
 - **Upload a custom certificate** from a provider like [Let's Encrypt](https://letsencrypt.org/) (free). Generate a wildcard certificate for `*.sandbox.yourdomain.com` using the DNS-01 challenge, then upload it via the Cloudflare dashboard under **SSL/TLS > Edge Certificates > [Custom Certificates](/ssl/edge-certificates/custom-certificates/)**. You will need to renew it before expiry.
-  :::
+:::
 
 ## Prerequisites
 
@@ -43,7 +42,7 @@ You have three options:
 In the Cloudflare dashboard, go to your domain and create an A record:
 
 - **Type**: A
-- **Name**: \* (wildcard)
+- **Name**: * (wildcard)
 - **IPv4 address**: 192.0.2.0
 - **Proxy status**: Proxied (orange cloud)
 
@@ -88,8 +87,8 @@ Test that preview URLs work:
 // Extract hostname from request
 const { hostname } = new URL(request.url);
 
-const sandbox = getSandbox(env.Sandbox, "test-sandbox");
-await sandbox.startProcess("python -m http.server 8080");
+const sandbox = getSandbox(env.Sandbox, 'test-sandbox');
+await sandbox.startProcess('python -m http.server 8080');
 const exposed = await sandbox.exposePort(8080, { hostname });
 
 console.log(exposed.url);
diff --git a/src/content/docs/sandbox/platform/pricing.mdx b/src/content/docs/sandbox/platform/pricing.mdx
index cf39a5eba58829c..cc9fe5632a5b833 100644
--- a/src/content/docs/sandbox/platform/pricing.mdx
+++ b/src/content/docs/sandbox/platform/pricing.mdx
@@ -13,7 +13,6 @@ Sandbox SDK pricing is determined by the underlying [Containers](/containers/) p
 ## Containers Pricing
 
 Refer to [Containers pricing](/containers/pricing/) for complete details on:
-
 - vCPU, memory, and disk usage rates
 - Network egress pricing
 - Instance types and their costs
@@ -21,7 +20,6 @@ Refer to [Containers pricing](/containers/pricing/) for complete details on:
 ## Related Pricing
 
 When using Sandbox, you'll also be billed for:
-
 - [Workers](/workers/platform/pricing/) - Handles incoming requests to your sandbox
 - [Durable Objects](/durable-objects/platform/pricing/) - Powers each sandbox instance
 - [Workers Logs](/workers/observability/logs/workers-logs/#pricing) - Optional observability (if enabled)
diff --git a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
index 5e0e4d91dfa660e..992afa80321cc03 100644
--- a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
+++ b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
@@ -25,7 +25,6 @@ An API that accepts questions like "What's the 100th Fibonacci number?", uses Cl
 <Render file="prereqs" product="workers" />
 
 You'll also need:
-
 - An [Anthropic API key](https://console.anthropic.com/) for Claude
 - [Docker](https://www.docker.com/) running locally
 
@@ -53,11 +52,11 @@ Install the Anthropic SDK:
 
 Replace the contents of `src/index.ts`:
 
-````typescript
-import { getSandbox, type Sandbox } from "@cloudflare/sandbox";
-import Anthropic from "@anthropic-ai/sdk";
+```typescript
+import { getSandbox, type Sandbox } from '@cloudflare/sandbox';
+import Anthropic from '@anthropic-ai/sdk';
 
-export { Sandbox } from "@cloudflare/sandbox";
+export { Sandbox } from '@cloudflare/sandbox';
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -66,10 +65,7 @@ interface Env {
 
 export default {
 	async fetch(request: Request, env: Env): Promise<Response> {
-		if (
-			request.method !== "POST" ||
-			new URL(request.url).pathname !== "/execute"
-		) {
+		if (request.method !== 'POST' || new URL(request.url).pathname !== '/execute') {
 			return new Response('POST /execute with { "question": "your question" }');
 		}
 
@@ -77,74 +73,65 @@ export default {
 			const { question } = await request.json();
 
 			if (!question) {
-				return Response.json(
-					{ error: "Question is required" },
-					{ status: 400 },
-				);
+				return Response.json({ error: 'Question is required' }, { status: 400 });
 			}
 
 			// Use Claude to generate Python code
 			const anthropic = new Anthropic({ apiKey: env.ANTHROPIC_API_KEY });
 			const codeGeneration = await anthropic.messages.create({
-				model: "claude-sonnet-4-5",
+				model: 'claude-sonnet-4-5',
 				max_tokens: 1024,
-				messages: [
-					{
-						role: "user",
-						content: `Generate Python code to answer: "${question}"
+				messages: [{
+					role: 'user',
+					content: `Generate Python code to answer: "${question}"
 
 Requirements:
 - Use only Python standard library
 - Print the result using print()
 - Keep code simple and safe
 
-Return ONLY the code, no explanations.`,
-					},
-				],
+Return ONLY the code, no explanations.`
+				}],
 			});
 
-			const generatedCode =
-				codeGeneration.content[0]?.type === "text"
-					? codeGeneration.content[0].text
-					: "";
+			const generatedCode = codeGeneration.content[0]?.type === 'text'
+				? codeGeneration.content[0].text
+				: '';
 
 			if (!generatedCode) {
-				return Response.json(
-					{ error: "Failed to generate code" },
-					{ status: 500 },
-				);
+				return Response.json({ error: 'Failed to generate code' }, { status: 500 });
 			}
 
 			// Strip markdown code fences if present
 			const cleanCode = generatedCode
-				.replace(/^```python?\n?/, "")
-				.replace(/\n?```\s*$/, "")
+				.replace(/^```python?\n?/, '')
+				.replace(/\n?```\s*$/, '')
 				.trim();
 
 			// Execute the code in a sandbox
-			const sandbox = getSandbox(env.Sandbox, "demo-user");
-			await sandbox.writeFile("/tmp/code.py", cleanCode);
-			const result = await sandbox.exec("python /tmp/code.py");
+			const sandbox = getSandbox(env.Sandbox, 'demo-user');
+			await sandbox.writeFile('/tmp/code.py', cleanCode);
+			const result = await sandbox.exec('python /tmp/code.py');
 
 			return Response.json({
 				success: result.success,
 				question,
 				code: generatedCode,
 				output: result.stdout,
-				error: result.stderr,
+				error: result.stderr
 			});
+
 		} catch (error: any) {
 			return Response.json(
-				{ error: "Internal server error", message: error.message },
-				{ status: 500 },
+				{ error: 'Internal server error', message: error.message },
+				{ status: 500 }
 			);
 		}
 	},
 };
-````
+```
 
 **How it works:**
-
 1. Receives a question via POST to `/execute`
 2. Uses Claude to generate Python code
 3. Writes code to `/tmp/code.py` in the sandbox
@@ -189,11 +176,11 @@ Response:
 
 ```json
 {
-	"success": true,
-	"question": "What is the 10th Fibonacci number?",
-	"code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
-	"output": "55\n",
-	"error": ""
+  "success": true,
+  "question": "What is the 10th Fibonacci number?",
+  "code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
+  "output": "55\n",
+  "error": ""
 }
 ```
 
@@ -241,7 +228,6 @@ curl -X POST https://ai-code-executor.YOUR_SUBDOMAIN.workers.dev/execute \
 ## What you built
 
 You created an AI code execution system that:
-
 - Accepts natural language questions
 - Generates Python code with Claude
 - Executes code securely in isolated sandboxes
diff --git a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
index 13784a7bf7fb634..5497b602e6f0f38 100644
--- a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
+++ b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
@@ -119,27 +119,24 @@ export default {
 			}
 
 			async function streamToBase64(stream) {
-				const blob = await new Response(stream).blob();
-				const buffer = await blob.arrayBuffer();
-				const bytes = new Uint8Array(buffer);
-
-				// Convert to base64
-				let binary = "";
-				for (let i = 0; i < bytes.length; i++) {
-					binary += String.fromCharCode(bytes[i]);
-				}
-				return btoa(binary);
+			  const blob = await new Response(stream).blob();
+			  const buffer = await blob.arrayBuffer();
+			  const bytes = new Uint8Array(buffer);
+
+			  // Convert to base64
+			  let binary = '';
+			  for (let i = 0; i < bytes.length; i++) {
+			    binary += String.fromCharCode(bytes[i]);
+			  }
+			  return btoa(binary);
 			}
 
 			// Check for generated chart
 			let chart = null;
 			try {
-				const { content, mimeType } = await sandbox.readFile(
-					"/workspace/chart.png",
-					{
-						encoding: "none",
-					},
-				);
+				const { content, mimeType } = await sandbox.readFile("/workspace/chart.png", {
+					encoding: "none"
+				});
 				chart = `data:${mimeType};base64,${await streamToBase64(content)}`;
 			} catch {
 				// No chart generated
diff --git a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
index cc84853855df6ca..1a964dfdb7b13da 100644
--- a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
+++ b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
@@ -39,15 +39,9 @@ cd test-pipeline
 Replace `src/index.ts`:
 
 ```typescript
-import {
-	getSandbox,
-	proxyToSandbox,
-	parseSSEStream,
-	type Sandbox,
-	type ExecEvent,
-} from "@cloudflare/sandbox";
+import { getSandbox, proxyToSandbox, parseSSEStream, type Sandbox, type ExecEvent } from '@cloudflare/sandbox';
 
-export { Sandbox } from "@cloudflare/sandbox";
+export { Sandbox } from '@cloudflare/sandbox';
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -59,39 +53,34 @@ export default {
 		const proxyResponse = await proxyToSandbox(request, env);
 		if (proxyResponse) return proxyResponse;
 
-		if (request.method !== "POST") {
-			return new Response(
-				'POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }',
-			);
+		if (request.method !== 'POST') {
+			return new Response('POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }');
 		}
 
 		try {
 			const { repoUrl, branch } = await request.json();
 
 			if (!repoUrl) {
-				return Response.json({ error: "repoUrl required" }, { status: 400 });
+				return Response.json({ error: 'repoUrl required' }, { status: 400 });
 			}
 
 			const sandbox = getSandbox(env.Sandbox, `test-${Date.now()}`);
 
 			try {
 				// Clone repository
-				console.log("Cloning repository...");
+				console.log('Cloning repository...');
 				let cloneUrl = repoUrl;
-
-				if (env.GITHUB_TOKEN && cloneUrl.includes("github.com")) {
-					cloneUrl = cloneUrl.replace(
-						"https://",
-						`https://${env.GITHUB_TOKEN}@`,
-					);
+				
+				if (env.GITHUB_TOKEN && cloneUrl.includes('github.com')) {
+					cloneUrl = cloneUrl.replace('https://', `https://${env.GITHUB_TOKEN}@`);
 				}
 
 				await sandbox.gitCheckout(cloneUrl, {
 					...(branch && { branch }),
 					depth: 1,
-					targetDir: "repo",
+					targetDir: 'repo'
 				});
-				console.log("Repository cloned");
+				console.log('Repository cloned');
 
 				// Detect project type
 				const projectType = await detectProjectType(sandbox);
@@ -100,42 +89,38 @@ export default {
 				// Install dependencies
 				const installCmd = getInstallCommand(projectType);
 				if (installCmd) {
-					console.log("Installing dependencies...");
-					const installStream = await sandbox.execStream(
-						`cd /workspace/repo && ${installCmd}`,
-					);
-
+					console.log('Installing dependencies...');
+					const installStream = await sandbox.execStream(`cd /workspace/repo && ${installCmd}`);
+					
 					let installExitCode = 0;
 					for await (const event of parseSSEStream<ExecEvent>(installStream)) {
-						if (event.type === "stdout" || event.type === "stderr") {
+						if (event.type === 'stdout' || event.type === 'stderr') {
 							console.log(event.data);
-						} else if (event.type === "complete") {
+						} else if (event.type === 'complete') {
 							installExitCode = event.exitCode;
 						}
 					}
-
+					
 					if (installExitCode !== 0) {
 						return Response.json({
 							success: false,
-							error: "Install failed",
-							exitCode: installExitCode,
+							error: 'Install failed',
+							exitCode: installExitCode
 						});
 					}
-					console.log("Dependencies installed");
+					console.log('Dependencies installed');
 				}
 
 				// Run tests
-				console.log("Running tests...");
+				console.log('Running tests...');
 				const testCmd = getTestCommand(projectType);
-				const testStream = await sandbox.execStream(
-					`cd /workspace/repo && ${testCmd}`,
-				);
-
+				const testStream = await sandbox.execStream(`cd /workspace/repo && ${testCmd}`);
+				
 				let testExitCode = 0;
 				for await (const event of parseSSEStream<ExecEvent>(testStream)) {
-					if (event.type === "stdout" || event.type === "stderr") {
+					if (event.type === 'stdout' || event.type === 'stderr') {
 						console.log(event.data);
-					} else if (event.type === "complete") {
+					} else if (event.type === 'complete') {
 						testExitCode = event.exitCode;
 					}
 				}
@@ -145,11 +130,13 @@ export default {
 					success: testExitCode === 0,
 					exitCode: testExitCode,
 					projectType,
-					message: testExitCode === 0 ? "All tests passed" : "Tests failed",
+					message: testExitCode === 0 ? 'All tests passed' : 'Tests failed'
 				});
+
 			} finally {
 				await sandbox.destroy();
 			}
+
 		} catch (error: any) {
 			return Response.json({ error: error.message }, { status: 500 });
 		}
@@ -158,46 +145,38 @@ export default {
 
 async function detectProjectType(sandbox: any): Promise<string> {
 	try {
-		await sandbox.readFile("/workspace/repo/package.json");
-		return "nodejs";
+		await sandbox.readFile('/workspace/repo/package.json');
+		return 'nodejs';
 	} catch {}
 
 	try {
-		await sandbox.readFile("/workspace/repo/requirements.txt");
-		return "python";
+		await sandbox.readFile('/workspace/repo/requirements.txt');
+		return 'python';
 	} catch {}
 
 	try {
-		await sandbox.readFile("/workspace/repo/go.mod");
-		return "go";
+		await sandbox.readFile('/workspace/repo/go.mod');
+		return 'go';
 	} catch {}
 
-	return "unknown";
+	return 'unknown';
 }
 
 function getInstallCommand(projectType: string): string {
 	switch (projectType) {
-		case "nodejs":
-			return "npm install";
-		case "python":
-			return "pip install -r requirements.txt || pip install -e .";
-		case "go":
-			return "go mod download";
-		default:
-			return "";
+		case 'nodejs': return 'npm install';
+		case 'python': return 'pip install -r requirements.txt || pip install -e .';
+		case 'go': return 'go mod download';
+		default: return '';
 	}
 }
 
 function getTestCommand(projectType: string): string {
 	switch (projectType) {
-		case "nodejs":
-			return "npm test";
-		case "python":
-			return "python -m pytest || python -m unittest discover";
-		case "go":
-			return "go test ./...";
-		default:
-			return 'echo "Unknown project type"';
+		case 'nodejs': return 'npm test';
+		case 'python': return 'python -m pytest || python -m unittest discover';
+		case 'go': return 'go test ./...';
+		default: return 'echo "Unknown project type"';
 	}
 }
 ```
@@ -224,10 +203,10 @@ You will see progress logs in the wrangler console, and receive a JSON response:
 
 ```json
 {
-	"success": true,
-	"exitCode": 0,
-	"projectType": "nodejs",
-	"message": "All tests passed"
+  "success": true,
+  "exitCode": 0,
+  "projectType": "nodejs",
+  "message": "All tests passed"
 }
 ```
 
@@ -246,7 +225,6 @@ npx wrangler secret put GITHUB_TOKEN
 ## What you built
 
 An automated testing pipeline that:
-
 - Clones Git repositories
 - Detects project type (Node.js, Python, Go)
 - Installs dependencies automatically
diff --git a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
index fc519d4cc81608a..022b3803088764b 100644
--- a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
+++ b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
@@ -19,10 +19,7 @@ Cloudflare provides a self-managed environment for [Claude Managed Agents](https
 
 This integration ships as an open-source deployment template. Fork the repo, deploy it to your Cloudflare account, and customize it as needed.
 
-<LinkButton
-	variant="secondary"
-	href="https://github.com/cloudflare/claude-managed-agents"
->
+<LinkButton variant="secondary" href="https://github.com/cloudflare/claude-managed-agents">
 	Get Started
 </LinkButton>
 
@@ -69,15 +66,15 @@ You need a Workers Paid plan or Enterprise account. [Containers](/containers/) (
 
 The repository includes detailed documentation on each capability:
 
-| Topic                                                                                                                                    | What it covers                                                                                                                                                   |
-| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md)   | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings                                                                             |
-| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md)               | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing                               |
-| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md)           | Pick the best agent execution environment                                                                                                                        |
-| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md)                                         | Give agents their own email addresses and sending abilities                                                                                                      |
-| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md)                 | Observable agent browser interactions with Browser Run                                                                                                           |
-| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md)                         | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
-| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md)                     | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend                                                                                            |
-| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types                                                                                                                      |
-| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md)                                       | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses                               |
-| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md)                                 | Secure access to the CMA control plane                                                                                                                           |
+| Topic | What it covers |
+| --- | --- |
+| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md) | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings |
+| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md) | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing |
+| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md) | Pick the best agent execution environment |
+| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md) | Give agents their own email addresses and sending abilities |
+| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md) | Observable agent browser interactions with Browser Run |
+| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md) | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
+| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md) | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend |
+| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types |
+| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md) | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses |
+| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md) | Secure access to the CMA control plane |
diff --git a/src/content/docs/sandbox/tutorials/code-review-bot.mdx b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
index 98052e0f745d6e9..daeeff910905556 100644
--- a/src/content/docs/sandbox/tutorials/code-review-bot.mdx
+++ b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
@@ -108,7 +108,9 @@ export default {
 			) {
 				console.log(`Starting review for PR #${payload.pull_request.number}`);
 				// Use waitUntil to ensure the review completes even after response is sent
-				ctx.waitUntil(reviewPullRequest(payload, env).catch(console.error));
+				ctx.waitUntil(
+					reviewPullRequest(payload, env).catch(console.error),
+				);
 				return Response.json({ message: "Review started" });
 			}
 
diff --git a/src/content/docs/secrets-store/audit-logs.mdx b/src/content/docs/secrets-store/audit-logs.mdx
index 90f826135f55949..144a24543be86f5 100644
--- a/src/content/docs/secrets-store/audit-logs.mdx
+++ b/src/content/docs/secrets-store/audit-logs.mdx
@@ -17,4 +17,4 @@ sidebar:
   - A boolean `"value_modified": true` is presented when the secret value is edited.
 - Delete
 
-For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
+For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/index.mdx b/src/content/docs/secrets-store/index.mdx
index e2ed5d0af9f4441..4d1e230e37ff9e9 100644
--- a/src/content/docs/secrets-store/index.mdx
+++ b/src/content/docs/secrets-store/index.mdx
@@ -16,8 +16,7 @@ head:
 import { Description, Plan } from "~/components";
 
 <Description>
-	Encrypt and store sensitive information as secrets that are securely reusable
-	across your account.
+Encrypt and store sensitive information as secrets that are securely reusable across your account.
 </Description>
 
 <Plan id="secrets_store.properties.availability.summary" />
diff --git a/src/content/docs/secrets-store/integrations/ai-gateway.mdx b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
index af789df84d1a0c0..918c8bcfa39217c 100644
--- a/src/content/docs/secrets-store/integrations/ai-gateway.mdx
+++ b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
@@ -8,4 +8,4 @@ external_link: /ai-gateway/configuration/bring-your-own-keys/
 sidebar:
   order: 3
   label: AI Gateway
----
+---
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/integrations/index.mdx b/src/content/docs/secrets-store/integrations/index.mdx
index a5ce8b0cbe2a887..64d5175c5fd2e82 100644
--- a/src/content/docs/secrets-store/integrations/index.mdx
+++ b/src/content/docs/secrets-store/integrations/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/manage-secrets/how-to.mdx b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
index cb9d42efdc308d9..2fd99158d2495e9 100644
--- a/src/content/docs/secrets-store/manage-secrets/how-to.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
@@ -155,4 +155,4 @@ Refer to [Secrets Store API](/api/resources/secrets_store/) for the full API doc
 	method="DELETE"
 />
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/manage-secrets/index.mdx b/src/content/docs/secrets-store/manage-secrets/index.mdx
index e9a5f2e3ffdfc0c..17a01164f12187d 100644
--- a/src/content/docs/secrets-store/manage-secrets/index.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/index.mdx
@@ -28,4 +28,4 @@ If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler)
 - [Create a secret](/secrets-store/manage-secrets/how-to/#create-a-secret)
 - [Duplicate a secret](/secrets-store/manage-secrets/how-to/#duplicate-a-secret)
 - [Edit a secret](/secrets-store/manage-secrets/how-to/#edit-a-secret)
-- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
+- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
\ No newline at end of file
diff --git a/src/content/docs/security-center/brand-protection.mdx b/src/content/docs/security-center/brand-protection.mdx
index 064f17815b2cfeb..3a021e91ce70f25 100644
--- a/src/content/docs/security-center/brand-protection.mdx
+++ b/src/content/docs/security-center/brand-protection.mdx
@@ -54,7 +54,7 @@ To start searching for new domains that might be trying to impersonate your bran
 
 5. To export all matches from a saved query, select your **Query name** > select the three dots > **Export matches**.
 
-In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the **Show dismissed matches** toggle in the Cloudflare dashboard.
+In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the  **Show dismissed matches** toggle in the Cloudflare dashboard.
 
 ### Logo search (AI-powered)
 
diff --git a/src/content/docs/security-center/changelog.mdx b/src/content/docs/security-center/changelog.mdx
index 889cbe1b2ec6c7b..1c92506953963cf 100644
--- a/src/content/docs/security-center/changelog.mdx
+++ b/src/content/docs/security-center/changelog.mdx
@@ -16,20 +16,20 @@ import { ProductChangelog } from "~/components";
 
 ## 2025-02-03
 
-- Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
+* Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
 
 ## 2025-01-20
 
-- On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
+* On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
 
 ## 2024-09-23
 
-- Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
+* Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
 
 ## 2024-09-19
 
-- Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
+* Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
 
 ## 2024-07-22
 
-- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
+* Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
diff --git a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
index e90c084b944a737..6749f8a8b7ee551 100644
--- a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
+++ b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
@@ -7,4 +7,5 @@ products:
 external_link: https://www.cloudflare.com/threat-intelligence/
 sidebar:
   order: 10
+
 ---
diff --git a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
index 33bd1dd3898a1bd..55fbf7081e51889 100644
--- a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
+++ b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
@@ -10,7 +10,9 @@ sidebar:
     text: Beta
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
+
+
 
 Open Port Scanning allows [Magic Transit](/magic-transit/) and [Bring your Own IPs](/byoip/) users to efficiently monitor IP ranges for security vulnerabilities. This API enables users to scan their designated IP ranges, detect any open ports, and receive daily notifications regarding newly opened ports.
 
@@ -19,24 +21,24 @@ You can access this feature via the [API](/api/resources/cloudforce_one/subresou
 ## Prerequisites
 
 - Cloudforce One Administrator, Administrator and Super Administrator roles.
-- Account token: **Custom API Token** > **Cloudforce One:Edit**.
+- Account token: **Custom API Token** >  **Cloudforce One:Edit**. 
 
 To create a custom API token:
 
 1. From the [Cloudflare dashboard](https://dash.cloudflare.com/profile/api-tokens/), go to **My Profile** > **API Tokens** for user tokens. Go to **Create Custom Token** > **Get started**.
 2. Enter a **Token name**, for example, `Open Port Scanning`.
 3. In **Permissions**:
-   - Choose **Account**.
-   - Select **Cloudforce One** as the account.
-   - Choose **Edit** access.
+    - Choose **Account**.
+    - Select **Cloudforce One** as the account.
+    - Choose **Edit** access.
 4. In Client IP Address Filtering:
-   - In **Operator**, select `is in`.
-   - In **Value**, enter a valid IP address.
+    - In **Operator**, select `is in`.
+    - In **Value**, enter a valid IP address.
 5. Select **Continue to summary**.
 6. Review the token, then select **Create Token**.
 
 :::note
-The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules.
+The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules. 
 :::
 
 ## Configure Open Port Scanning
@@ -44,56 +46,150 @@ The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce O
 To configure Open Port Scanning, follow these steps:
 
 1. **Create a new scan config**:
-   - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
-   - **Frequency**: Enter the scan frequency in days.
-   - **Ports**: Select the ports to scan. Choose among:
-     - All
-     - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
-     - List of specific ports
+    - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
+    - **Frequency**: Enter the scan frequency in days.
+    - **Ports**: Select the ports to scan. Choose among:
+        - All
+        - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
+        - List of specific ports
 2. **Scan IPs**: Initiate the scanning process. The system will analyze the specified IP ranges to identify any open ports.
 3. **Generate list of open ports**: Once the scan is complete, the API will generate a list of detected open ports for review and action.
-4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude any ports that do not require immediate attention.
+4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude  any ports that do not require immediate attention.
 5. **View differences from previous scan**: The API will highlight any changes in open ports since the last scan, allowing you to quickly assess new vulnerabilities.
-6. **Stop scanning**: If necessary, you can stop the scanning process at any time.
-7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open.
+6. **Stop scanning**: If necessary, you can stop  the scanning process at any time.
+7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open. 
 
 :::note[Beta feature notice]
 Open Port Scanning feature is currently in closed beta. The Cloudforce One team appreciates your feedback as the team works to enhance its functionality and user experience.
-If you want to subscribe to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
+If you want to subscribe  to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
 :::
 
 ## Default ports
 
 <Details header="List of default ports">
-	- `80` - `631` - `161` - `137` - `123` - `138` - `1434` - `445` - `135` - `67`
-	- `23` - `53` - `443` - `21` - `139` - `22` - `500` - `68` - `520` - `1900` -
-	`25` - `4500` - `514` - `49152` - `162` - `69` - `5353` - `111` - `49154` -
-	`3389` - `110` - `1701` - `998` - `996` - `997` - `999` - `3283` - `49153` -
-	`445` - `1812` - `136` - `139` - `143` - `53` - `2222` - `135` - `3306` -
-	`2049` - `32768` - `5060` - `8080` - `1025` - `1433` - `3456` - `80` - `1723`
-	- `111` - `995` - `993` - `20031` - `1026` - `7` - `5900` - `1646` - `1645` -
-	`593` - `1025` - `518` - `2048` - `626` - `1027` - `587` - `177` - `1719` -
-	`427` - `497` - `8888` - `4444` - `1023` - `65024` - `199` - `19` - `9` -
-	`49193` - `1029` - `1720` - `49` - `465` - `88` - `1028` - `17185` - `1718` -
-	`49186` - `548` - `113` - `81` - `6001` - `2000` - `10000` - `31337`
+- `80`
+- `631`
+- `161`
+- `137`
+- `123`
+- `138`
+- `1434`
+- `445`
+- `135`
+- `67`
+- `23`
+- `53`
+- `443`
+- `21`
+- `139`
+- `22`
+- `500`
+- `68`
+- `520`
+- `1900`
+- `25`
+- `4500`
+- `514`
+- `49152`
+- `162`
+- `69`
+- `5353`
+- `111`
+- `49154`
+- `3389`
+- `110`
+- `1701`
+- `998`
+- `996`
+- `997`
+- `999`
+- `3283`
+- `49153`
+- `445`
+- `1812`
+- `136`
+- `139`
+- `143`
+- `53`
+- `2222`
+- `135`
+- `3306`
+- `2049`
+- `32768`
+- `5060`
+- `8080`
+- `1025`
+- `1433`
+- `3456`
+- `80`
+- `1723`
+- `111`
+- `995`
+- `993`
+- `20031`
+- `1026`
+- `7`
+- `5900`
+- `1646`
+- `1645`
+- `593`
+- `1025`
+- `518`
+- `2048`
+- `626`
+- `1027`
+- `587`
+- `177`
+- `1719`
+- `427`
+- `497`
+- `8888`
+- `4444`
+- `1023`
+- `65024`
+- `199`
+- `19`
+- `9`
+- `49193`
+- `1029`
+- `1720`
+- `49`
+- `465`
+- `88`
+- `1028`
+- `17185`
+- `1718`
+- `49186`
+- `548`
+- `113`
+- `81`
+- `6001`
+- `2000`
+- `10000`
+- `31337`
 </Details>
 
 ## Frequently Asked Questions
 
 1. What IPs will the scan come from?
-   - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
-   - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
-   - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241`
+
+    - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
+    - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
+    - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241` 
 
 2. Can the Port Scanner bypass other security rules configured?
-   - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
+
+    - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
 
 3. How long do scans take?
-   - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
+
+    - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
 
 4. Can I stop automatic scanning?
-   - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
+
+    - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
 
 5. What are the limitations for the scans?
-   - Scans are limited to ranges of up to 5,000 IPs.
-   - The API scans both IPv4 and IPv6 IP addresses.
+
+    - Scans are limited to ranges of up to 5,000 IPs.
+    - The API scans both IPv4 and IPv6 IP addresses.
\ No newline at end of file
diff --git a/src/content/docs/security-center/investigate/change-categorization.mdx b/src/content/docs/security-center/investigate/change-categorization.mdx
index bc56bde0cf28d7a..c2efde74687cbbf 100644
--- a/src/content/docs/security-center/investigate/change-categorization.mdx
+++ b/src/content/docs/security-center/investigate/change-categorization.mdx
@@ -6,6 +6,7 @@ products:
   - security-center
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/docs/security-center/investigate/index.mdx b/src/content/docs/security-center/investigate/index.mdx
index 6a3e0202c62c662..f63c519b1be248a 100644
--- a/src/content/docs/security-center/investigate/index.mdx
+++ b/src/content/docs/security-center/investigate/index.mdx
@@ -6,6 +6,7 @@ products:
   - security-center
 sidebar:
   order: 6
+
 ---
 
 :::note[User permission]
diff --git a/src/content/docs/security-center/investigate/investigate-threats.mdx b/src/content/docs/security-center/investigate/investigate-threats.mdx
index 8056b226555f5c8..48ce56a091e23fd 100644
--- a/src/content/docs/security-center/investigate/investigate-threats.mdx
+++ b/src/content/docs/security-center/investigate/investigate-threats.mdx
@@ -6,9 +6,10 @@ products:
   - security-center
 sidebar:
   order: 3
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Users can investigate the details of an IP address, domain name, URL, or Autonomous System Number (ASN). You can find the Investigate feature in your Cloudflare account's Security Center and in [Cloudflare Radar](https://radar.cloudflare.com/scan).
 
@@ -105,4 +106,4 @@ To download a report:
    <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your domain and select **Search**.
-3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
+3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
\ No newline at end of file
diff --git a/src/content/docs/security-center/investigate/scan-limits.mdx b/src/content/docs/security-center/investigate/scan-limits.mdx
index 00c9e0921faf0d5..4a87a3ad19d63d5 100644
--- a/src/content/docs/security-center/investigate/scan-limits.mdx
+++ b/src/content/docs/security-center/investigate/scan-limits.mdx
@@ -5,13 +5,17 @@ products:
   - security-center
 head: []
 description: Limits
+
 ---
 
 URL scans are limited by search history, Public and Unlisted visibility, and requests per second across different Cloudflare plans.
 
+
+
 | Cloudflare Plan    | Search history | Public scans (per month) | Unlisted scans (per month) | Rate limit       |
 | ------------------ | -------------- | ------------------------ | -------------------------- | ---------------- |
 | **Free / Radar**   | last 50 scans  | 5,000                    | none                       | 1 per 10 seconds |
 | **Self serve**     | 30 days        | 5,000                    | 500                        | 1 per 10 seconds |
 | **Enterprise**     | 12 months      | 10,000                   | 5,000                      | 12 per second    |
 | **Cloudforce One** | Unlimited      | 75,000                   | 20,000                     | 12 per second    |
+
diff --git a/src/content/docs/security/overview.mdx b/src/content/docs/security/overview.mdx
index 91001dcbbfba6db..544b227b7e54dfc 100644
--- a/src/content/docs/security/overview.mdx
+++ b/src/content/docs/security/overview.mdx
@@ -24,11 +24,10 @@ The Security overview page displays:
 
 ## Security action items
 
-**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity.
-
-- **Action item types**:
-  - Suspicious activity
-  - Security insight
+**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity. 
+  - **Action item types**:
+    - Suspicious activity
+    - Security insight
 - **Criticality**: Your action items are ranked by the highest criticality, showing critical first, moderate, and low respectively.
 - **Filters**: You can filter your action items by Criticality, Insight Type, and Security Category.
   - Criticality:
@@ -36,20 +35,20 @@ The Security overview page displays:
     - Moderate
     - Critical
   - Insight Types:
-    - Suspicious activity
-    - Exposed infrastructure
-    - Insecure configuration
+    - Suspicious activity 
+    - Exposed infrastructure 
+    - Insecure configuration 
     - Configuration suggestion
     - Compliance Violation
     - Email Security
     - Weak Authentication
-  - Security Category:
+  - Security Category: 
     - Web application exploits
     - AI exploits
-    - DDoS attacks
-    - Bot traffic
-    - API abuse
-    - Client-side abuse
+    - DDoS attacks 
+    - Bot traffic 
+    - API abuse 
+    - Client-side abuse 
     - Fraud
 - **Review**: Review your security action items for more detailed information and recommended actions to resolve.
 - **Load more**: View the full list of security action items.
@@ -72,14 +71,14 @@ Archiving a detected suspicious activity will only archive that item from the se
 
 To view when an action item’s status was changed and the rationale provided for that change, use the following API commands to retrieve audit logs:
 
-| Method | Path                                                                      | Description                                      |
-| ------ | ------------------------------------------------------------------------- | ------------------------------------------------ |
-| `GET`  | `/api/accounts/{accountID}/insights/audit-log`                            | List all audit logs for an account               |
-| `GET`  | `/api/accounts/{accountID}/insights/{insightID}/audit-log`                | List audit logs for a specific issue             |
-| `GET`  | `/api/accounts/{accountID}/issues/audit-log`                              | List all audit logs for account issues           |
-| `GET`  | `/api/accounts/{accountID}/issues/{insightID}/audit-log`                  | List all audit logs for a specific issue         |
-| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log`             | List all audit logs for a domain                 |
-| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
+| Method | Path | Description |
+| ------ | ---- | ----------- |
+| `GET` | `/api/accounts/{accountID}/insights/audit-log` | List all audit logs for an account |
+| `GET` | `/api/accounts/{accountID}/insights/{insightID}/audit-log` | List audit logs for a specific issue |
+| `GET` | `/api/accounts/{accountID}/issues/audit-log` | List all audit logs for account issues |
+| `GET` | `/api/accounts/{accountID}/issues/{insightID}/audit-log` | List all audit logs for a specific issue |
+| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log` | List all audit logs for a domain |
+| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
 
 Refer to our [Security Center API documentation](/api/resources/security_center) to review the action item audit logs by account, domain, or a specific `issue_id`.
 
@@ -94,4 +93,4 @@ View the patterns and highlights from your domain's traffic in the past 30 days.
 The Cloudflare dashboard displays:
 
 - **Monthly requests**: View the monthly requests and traffic that has been mitigated by Cloudflare.
-- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
+- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/concepts/index.mdx b/src/content/docs/smart-shield/concepts/index.mdx
index 12403e47aa9a979..1120c7c003aa4c3 100644
--- a/src/content/docs/smart-shield/concepts/index.mdx
+++ b/src/content/docs/smart-shield/concepts/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/concepts/network-diagram.mdx b/src/content/docs/smart-shield/concepts/network-diagram.mdx
index 307591a0ae523f1..3eec884e62a0d79 100644
--- a/src/content/docs/smart-shield/concepts/network-diagram.mdx
+++ b/src/content/docs/smart-shield/concepts/network-diagram.mdx
@@ -16,4 +16,4 @@ Requests from visitors first reach a nearby lower-tier data center. For static (
 
 For dynamic (non-cacheable) requests, [Argo Smart Routing](/smart-shield/configuration/argo/) finds the fastest network path to your origin. Between Cloudflare's upper-tier data centers and your origin, [connection reuse](/smart-shield/concepts/connection-reuse/) packages multiple requests into a single connection, reducing the total number of connections your origin handles.
 
-[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
+[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/argo.mdx b/src/content/docs/smart-shield/configuration/argo.mdx
index 0d1fcae78001d37..16a4fce8d7e97be 100644
--- a/src/content/docs/smart-shield/configuration/argo.mdx
+++ b/src/content/docs/smart-shield/configuration/argo.mdx
@@ -18,4 +18,4 @@ Available with Smart Shield + Argo and Smart Shield Advanced.
 
 Cloudflare provides analytics to show the performance benefits of Argo Smart Routing.
 
-<Render file="argo-analytics" product="smart-shield" />
+<Render file="argo-analytics" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
index 3e14a1542d4343a..14f71bac0cc40fc 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
@@ -14,9 +14,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="cache-reserve-analytics"
-	product="cache"
+  file="cache-reserve-analytics"
+  product="cache"
 	params={{
 		conditional: "smart-shield-tile",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
index 9c1e9769086a7e3..8eeb03f8661c785 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
@@ -40,4 +40,4 @@ You can remove all data stored in Cache Reserve. In most cases, deletion takes a
 
 :::note
 If you want to purge your cache instead, refer to [cache configurations](/cache/how-to/purge-cache/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
index 40b660890f6f6f9..5d0b8457ad806be 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
@@ -13,4 +13,7 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cache-reserve-operations" product="cache" />
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
index 4af2a88245d5455..6b011755c7d6d69 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
@@ -38,7 +38,7 @@ flowchart LR
 
 If the server does not have access to an applicable IP, the following options are checked and the first that is possible will take place:
 
-- Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
+* Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
 
 ```mermaid
 flowchart LR
@@ -55,7 +55,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-- Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
+* Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
 
 ```mermaid
 flowchart LR
@@ -77,7 +77,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-- Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
+* Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
 
 ```mermaid
 flowchart LR
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
index 44ef7eec5859bde..c7f7d638be9549d 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Refer to the pages below to understand how Dedicated CDN Egress IPs work.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
index 2275ff704685684..4ed679361eb9526 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
@@ -24,9 +24,9 @@ Dedicated CDN Egress IPs was formerly known as Cloudflare Aegis ([release blog p
 
 With Dedicated CDN Egress IPs, you can:
 
-- Lock down your network firewall to only allow traffic from your dedicated IPs.
-- Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
-- Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
+* Lock down your network firewall to only allow traffic from your dedicated IPs.
+* Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
+* Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
 
 ## Scope
 
@@ -40,4 +40,4 @@ Dedicated CDN Egress IPs are included within [BGP advertisement over CNI](/netwo
 
 <DirectoryListing />
 
-[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
+[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
index 7e7eb7f4fe8699d..bf1bd852f10c57a 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
@@ -16,7 +16,7 @@ Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data and monitor
 
 <Render file="concurrent-connections-explainer" product="smart-shield" />
 
-Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the [example](#example) below for a quickstart.
+Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the  [example](#example) below for a quickstart.
 
 ## GraphQL schema
 
@@ -25,19 +25,19 @@ The specific schema to get Dedicated CDN Egress IPs data is called `aegisIpUtili
 You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions:
 
 - `datetimeFiveMinutes` <Type text="time" />
-  - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
+    - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
 
 - `popName` <Type text="string" />
-  - The Cloudflare point of presence (PoP). For example, `sjc`.
+    - The Cloudflare point of presence (PoP). For example, `sjc`.
 
 - `egressIp` <Type text="string" />
-  - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
+    - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
 
 - `origin` <Type text="string" />
-  - Origin IP and port. For example, `203.0.113.150:443`.
+    - Origin IP and port. For example, `203.0.113.150:443`.
 
 - `popUtilizationKey` <Type text="string" />
-  - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
+    - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
 
 ## Example
 
@@ -47,100 +47,100 @@ You can also select the button at the bottom to use this query for your account
 
 ```graphql graphql-api-explorer "popName: "<CLOUDFLARE_POP>"" "egressIp: "<YOUR_EGRESS_IP>"" "origin: "<ORIGIN_IP_AND_PORT>""
 query AegisIpUtilizationQuery(
-	$accountTag: string
-	$datetimeStart: string
-	$datetimeEnd: string
+  $accountTag: string
+  $datetimeStart: string
+  $datetimeEnd: string
 ) {
-	viewer {
-		utilization: accounts(filter: { accountTag: $accountTag }) {
-			avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				avg {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					popName: "<CLOUDFLARE_POP>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					egressIp: "<YOUR_EGRESS_IP>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					origin: "<ORIGIN_IP_AND_PORT>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-		}
-	}
+  viewer {
+    utilization: accounts(filter: { accountTag: $accountTag }) {
+      avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        avg {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          popName: "<CLOUDFLARE_POP>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          egressIp: "<YOUR_EGRESS_IP>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          origin: "<ORIGIN_IP_AND_PORT>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+    }
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
index da17ba92284032c..f36cbde97e071bb 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
@@ -63,4 +63,4 @@ Workers subrequests — requests from one Worker to another — are expected to
 
 For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
 
-[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
+[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
index 2ff26322bf71a01..121427dcf85f924 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
@@ -15,4 +15,7 @@ import { Render } from "~/components";
 
 Use Health Checks analytics to debug possible origin issues.
 
-<Render file="health-checks-analytics" product="smart-shield" />
+<Render
+  file="health-checks-analytics"
+	product="smart-shield"
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/index.mdx b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
index 0f3fdf5c2c0f9a7..ca2d659d7d5eb14 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/index.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
@@ -24,4 +24,4 @@ Available for Pro, Business, and Enterprise customers in all Smart Shield packag
 
 ## Further reading
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
index 07cacf201721425..292d644b16b754d 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
@@ -20,8 +20,8 @@ Refer to the section below to learn how to manage your Smart Shield health check
 3. For Health Checks, select **Manage**.
 4. Select **Create** or find an existing health check and select **Edit**.
 5. Fill out the form or edit existing values, paying special attention to:
-   - The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
-   - **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
+   * The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
+   * **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
 6. Select **Save and Deploy**.
 
 ## Configure alerts
diff --git a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
index e269a8febaf8111..5a42572ca2e935b 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
@@ -15,4 +15,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
+<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/index.mdx b/src/content/docs/smart-shield/configuration/index.mdx
index 6244ba2195424e8..9a1b637e55751a5 100644
--- a/src/content/docs/smart-shield/configuration/index.mdx
+++ b/src/content/docs/smart-shield/configuration/index.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
index 49cf513c617947e..9073a8017865420 100644
--- a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
@@ -16,4 +16,4 @@ import { Render } from "~/components";
 Available with Smart Shield Advanced.
 :::
 
-<Render file="regional-tiered-cache" product="cache" />
+<Render file="regional-tiered-cache" product="cache" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
index 9b9c6760721cd54..f7fafaa47aea6a9 100644
--- a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
@@ -18,4 +18,4 @@ Available in all Smart Shield packages.
 
 With data centers around the world, Cloudflare caches content very close to end users. However, if a piece of content is not in cache, the Cloudflare data centers must contact the origin server to receive the cacheable content. Tiered cache works by dividing Cloudflare's data centers into a hierarchy of lower-tiers and upper-tiers, where only upper-tiers can ask your origin for content.
 
-<Render file="smart-tiered-cache" product="cache" />
+<Render file="smart-tiered-cache" product="cache" />
\ No newline at end of file
diff --git a/src/content/docs/spectrum/about/byoip.mdx b/src/content/docs/spectrum/about/byoip.mdx
index 3e3fb82322e59aa..b574fc12e5048f2 100644
--- a/src/content/docs/spectrum/about/byoip.mdx
+++ b/src/content/docs/spectrum/about/byoip.mdx
@@ -5,18 +5,22 @@ description: Use your own IP addresses with Spectrum applications.
 products:
   - spectrum
 weight: 0
+
 ---
 
-import { APIRequest, Render } from "~/components";
+import { APIRequest, Render } from "~/components"
 
 When creating a Spectrum application, Cloudflare normally assigns an arbitrary IP from Cloudflare’s IP pool to your application. If you want to be explicit in your network setup or use your own IP addresses, BYOIP with Spectrum allows you to do just that.
 
 BYOIP stands for [Bring Your Own IP](/byoip/). If you own an IP prefix you can migrate it to Cloudflare. After migration, Cloudflare broadcasts your IP prefix and traffic is routed to the global Cloudflare network. However, without configuration, Cloudflare will not know how to handle this traffic. The last step is to add Spectrum applications for all applications that you wish to protect with the IP addresses you want associated with them.
 
+
 :::caution
 
+
 When switching from non-BYOIP to BYOIP, if you are already using a Spectrum application, you need to delete your configurations and recreate new ones.
 
+
 :::
 
 The smallest prefixes that Cloudflare currently supports is /24 for IPv4 and /48 for IPv6.
@@ -31,22 +35,22 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 
 ```json
 {
-	"id": "4590376cf2994d72cee36828ec4eff19",
-	"protocol": "tcp/22",
-	"dns": {
-		"type": "ADDRESS",
-		"name": "ssh.example.com"
-	},
-	"origin_direct": ["tcp://192.0.2.1:22"],
-	"ip_firewall": true,
-	"proxy_protocol": false,
-	"spp": false,
-	"tls": "off",
-	"traffic_type": "direct",
-	"edge_ips": {
-		"type": "static",
-		"ips": ["198.51.100.10", "2001:DB8::1"]
-	}
+  "id": "4590376cf2994d72cee36828ec4eff19",
+  "protocol": "tcp/22",
+  "dns": {
+    "type": "ADDRESS",
+    "name": "ssh.example.com"
+  },
+  "origin_direct": ["tcp://192.0.2.1:22"],
+  "ip_firewall": true,
+  "proxy_protocol": false,
+  "spp": false,
+  "tls": "off",
+  "traffic_type": "direct",
+  "edge_ips": {
+    "type": "static",
+    "ips": ["198.51.100.10", "2001:DB8::1"]
+  }
 }
 ```
 
@@ -55,20 +59,25 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 In the example below, the application routes traffic through Cloudflare’s HTTP pipeline, including WAF, Workers and CDN functionality.
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		protocol: "tcp/80",
-		dns: {
-			type: "ADDRESS",
-			name: "www.example.com",
-		},
-		origin_direct: ["tcp://192.0.2.1:80"],
-		tls: "off",
-		traffic_type: "http",
-		edge_ips: {
-			type: "static",
-			ips: ["198.51.100.10", "2001:DB8::1"],
-		},
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    protocol: "tcp/80",
+    dns: {
+      type: "ADDRESS",
+      name: "www.example.com"
+    },
+    origin_direct: [
+      "tcp://192.0.2.1:80"
+    ],
+    tls: "off",
+    traffic_type: "http",
+    edge_ips: {
+      type: "static",
+      ips: [
+        "198.51.100.10",
+        "2001:DB8::1"
+      ]
+    }
+  }}
 />
diff --git a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
index 30cfcf85e672028..21f55d4cd8281c7 100644
--- a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
+++ b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
@@ -5,6 +5,7 @@ description: Layer 3 and 4 DDoS protection for TCP and UDP Spectrum applications
 products:
   - spectrum
 weight: 0
+
 ---
 
 Spectrum provides DDoS Protection at layers 3-4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/), that is against TCP and UDP based DDoS attacks.
diff --git a/src/content/docs/spectrum/about/ftp.mdx b/src/content/docs/spectrum/about/ftp.mdx
index 68f7e8ff116275c..1d666adace4bcc4 100644
--- a/src/content/docs/spectrum/about/ftp.mdx
+++ b/src/content/docs/spectrum/about/ftp.mdx
@@ -13,15 +13,17 @@ Enabling Spectrum for FTP is not straightforward due to the implementation of th
 
 :::note
 
+
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
+
 :::
 
 ## How FTP Operates
 
 FTP leverages two different sockets, one for issuing commands and the other for actual data transfer. The control socket takes care of users logging in and sending commands, and the data socket is where directory listings and files actually get transferred.
 
-There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects _back_ to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
+There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects *back* to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
 
 In passive mode, the FTP server communicates a port that the client should connect to, which is done on the control socket via a PASV command. By default, the FTP server responds with the IP address that it is listening on. This scenario is fine for servers running directly on a public-facing IP but creates issues when a server is behind an NAT, firewall, or Cloudflare Spectrum.
 
@@ -29,7 +31,7 @@ Alternatively, more modern FTP server software supports [FTP extensions](https:/
 
 ## What Does and Does Not Work
 
-Spectrum is able to protect servers serving FTP traffic in _passive mode only_. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
+Spectrum is able to protect servers serving FTP traffic in *passive mode only*. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
 
 Passive mode in combination with EPSV works out of the box with no origin-side configuration required. Note that the client must also support EPSV for this to work. Traditional passive mode with PASV is possible with minimal origin-side configuration (see below, Protecting an FTP server with Spectrum)
 
@@ -69,14 +71,14 @@ Example configuration for [vsftpd](https://security.appspot.com/vsftpd.html):
 
 To use Spectrum TCP to proxy and protect FTPS, specifically ProFTPD, the following example configuration is recommended:
 
-- **Control Port**: Port 21
-- **Data Ports**: Port ranges 50000-50500
+* **Control Port**: Port 21
+* **Data Ports**: Port ranges 50000-50500
 
 On the ProFTPD server side use the following example configuration:
 
-- `MasqueradeAddress`: `www.example.com`
-- `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
-- `PassivePorts`: `50000-50500`
+* `MasqueradeAddress`: `www.example.com`
+* `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
+* `PassivePorts`: `50000-50500`
 
 For more details, refer to the [ProFTPD documentation](http://www.proftpd.org/docs/modules/mod_core.html).
 
diff --git a/src/content/docs/spectrum/about/index.mdx b/src/content/docs/spectrum/about/index.mdx
index 79bf764731996bb..a45de1bbf3080f6 100644
--- a/src/content/docs/spectrum/about/index.mdx
+++ b/src/content/docs/spectrum/about/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information about concepts related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/about/static-ip.mdx b/src/content/docs/spectrum/about/static-ip.mdx
index 9ad484844461329..f075127c3337700 100644
--- a/src/content/docs/spectrum/about/static-ip.mdx
+++ b/src/content/docs/spectrum/about/static-ip.mdx
@@ -5,9 +5,10 @@ description: Assign persistent IP addresses to your Spectrum applications.
 products:
   - spectrum
 weight: 0
+
 ---
 
-import { APIRequest, Render } from "~/components";
+import { APIRequest, Render } from "~/components"
 
 When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.
 
@@ -28,30 +29,35 @@ Once you get your static IP from Cloudflare, you can use it via API, just like [
 When creating a Spectrum application through the API, specify the static IPs that you have been provided. See, for instance, the API example below that creates an application routing traffic through Cloudflare’s HTTP pipeline.
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		protocol: "tcp/80",
-		dns: {
-			type: "ADDRESS",
-			name: "www.example.com",
-		},
-		origin_direct: ["tcp://192.0.2.1:80"],
-		tls: "off",
-		traffic_type: "http",
-		edge_ips: {
-			type: "static",
-			ips: ["198.51.100.10", "2001:DB8::1"],
-		},
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    protocol: "tcp/80",
+    dns: {
+      type: "ADDRESS",
+      name: "www.example.com"
+    },
+    origin_direct: [
+      "tcp://192.0.2.1:80"
+    ],
+    tls: "off",
+    traffic_type: "http",
+    edge_ips: {
+      type: "static",
+      ips: [
+        "198.51.100.10",
+        "2001:DB8::1"
+      ]
+    }
+  }}
 />
 
 ## Check your static IPs
 
 <Render
-	file="check-leased-ips"
+  file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "static IPs for Spectrum",
+		product: "static IPs for Spectrum"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/spectrum/glossary.mdx b/src/content/docs/spectrum/glossary.mdx
index e858503baad6ca3..5dfed742cc6ccb5 100644
--- a/src/content/docs/spectrum/glossary.mdx
+++ b/src/content/docs/spectrum/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - spectrum
 sidebar:
   order: 7
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Spectrum documentation.
 
diff --git a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
index bed4a42932be361..3961a4766160937 100644
--- a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
+++ b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
@@ -5,6 +5,7 @@ description: Pass client IP information to your origin using Proxy protocol v1 o
 products:
   - spectrum
 weight: 0
+
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +16,10 @@ Some services you run may require knowledge of the true client IP. In those case
 
 :::note
 
+
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
+
 :::
 
 ## Enable Proxy Protocol v1 for TCP
diff --git a/src/content/docs/spectrum/how-to/index.mdx b/src/content/docs/spectrum/how-to/index.mdx
index 8edbdf1ca9239c5..9f660cc61eee6f5 100644
--- a/src/content/docs/spectrum/how-to/index.mdx
+++ b/src/content/docs/spectrum/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information on completing Spectrum related tasks, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/protocols-per-plan.mdx b/src/content/docs/spectrum/protocols-per-plan.mdx
index b82fd38bf63e579..6ae364f5a9f92e8 100644
--- a/src/content/docs/spectrum/protocols-per-plan.mdx
+++ b/src/content/docs/spectrum/protocols-per-plan.mdx
@@ -6,9 +6,10 @@ products:
   - spectrum
 sidebar:
   order: 2
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 On this table, you have information about which protocols are available per plan.
 
diff --git a/src/content/docs/spectrum/reference/analytics.mdx b/src/content/docs/spectrum/reference/analytics.mdx
index 3f021a4dd31e9fb..8ad2a392de6915f 100644
--- a/src/content/docs/spectrum/reference/analytics.mdx
+++ b/src/content/docs/spectrum/reference/analytics.mdx
@@ -9,10 +9,12 @@ tags:
   - Analytics
 ---
 
-import { Render, APIRequest } from "~/components";
+import { Render, APIRequest } from "~/components"
 
 Cloudflare measures the following metrics for every connection.
 
+
+
 | Metric         | Name                                | Example | Unit                 |
 | -------------- | ----------------------------------- | ------- | -------------------- |
 | count          | Count of total events               | `1000`  | Count                |
@@ -23,10 +25,14 @@ Cloudflare measures the following metrics for every connection.
 | duration90th   | 90th percentile connection duration | `1.0`   | Time in milliseconds |
 | duration99th   | 99th percentile connection duration | `1.0`   | Time in milliseconds |
 
+
+
 ## Additional dimensions
 
 You can divide your analytics further by the following dimensions.
 
+
+
 | Dimension | Name                          | Example                                                              |
 | --------- | ----------------------------- | -------------------------------------------------------------------- |
 | event     | Connection Event              | `connect`, `progress`, `disconnect`, `originError`, `clientFiltered` |
@@ -34,10 +40,14 @@ You can divide your analytics further by the following dimensions.
 | coloName  | Colo Name                     | `SFO`                                                                |
 | ipVersion | IP version used by the client | `4`, `6`                                                             |
 
+
+
 ## Operators for filtering
 
 Use the operators below to filter data.
 
+
+
 | Operator | Name                     | URL Encoded |
 | -------- | ------------------------ | ----------- |
 | `==`     | Equals                   | `%3D%3D`    |
@@ -47,6 +57,8 @@ Use the operators below to filter data.
 | `>=`     | Greater than or equal to | `%3E%3D`    |
 | `<=`     | Less than or equal to    | `%3C%3D`    |
 
+
+
 <Render file="api-combine-filters" product="fundamentals" />
 
 ## Analytics request structure
@@ -56,26 +68,26 @@ Use the operators below to filter data.
 /api/v4/zones/{zone_id}/spectrum/analytics/events/bytime?metrics=METRICS&dimensions=DIMENSIONS&filters=FILTERS&since=FROM_TS&sort=SORT&until=TO_TS&limit=LIMIT
 ```
 
-- METRICS is one or more metrics (such as count) to compute
-- DIMENSIONS can be used to break down the data by given attributes
-- FILTERS used to filter rows by one or more dimensions (see Filters section below)
-- SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
-- TO_TS is that end of time interval to query, defaults to current time
-- FROM_TS is that start of time interval to query, defaults to TO_TS - 6 hours
-- STEP is used to select time series resolution when using endpoint:
-- auto or omitted - selects time step most appropriate to time interval
-  - year
-  - quarter
-  - month
-  - week
-  - day
-  - hour
+* METRICS is one or more metrics (such as count) to compute
+* DIMENSIONS can be used to break down the data by given attributes
+* FILTERS used to filter rows by one or more dimensions (see Filters section below)
+* SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
+* TO\_TS is that end of time interval to query, defaults to current time
+* FROM\_TS is that start of time interval to query, defaults to TO\_TS - 6 hours
+* STEP is used to select time series resolution when using endpoint:
+* auto or omitted - selects time step most appropriate to time interval
+  * year
+  * quarter
+  * month
+  * week
+  * day
+  * hour
 
 ## Analytics query example
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/analytics/events/summary"
-	method="GET"
+  path="/zones/{zone_id}/spectrum/analytics/events/summary"
+  method="GET"
 />
 
 Refer to the [Spectrum API documentation](/api/resources/spectrum/subresources/analytics/subresources/aggregates/subresources/currents/methods/get/) for more examples of API requests.
diff --git a/src/content/docs/spectrum/reference/index.mdx b/src/content/docs/spectrum/reference/index.mdx
index 2f5495921b7c522..1cb17fdcb764a75 100644
--- a/src/content/docs/spectrum/reference/index.mdx
+++ b/src/content/docs/spectrum/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/reference/layer-7-analytics.mdx b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
index ed2b0717d749251..ac15ed1aa946651 100644
--- a/src/content/docs/spectrum/reference/layer-7-analytics.mdx
+++ b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - spectrum
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Even when you have Spectrum enabled to handle Layer 4 traffic (for example, TCP/UDP connections), you may still notice traffic in your Layer 7 (L7) analytics dashboard. This is due to the way Cloudflare's Layer 7 <GlossaryTooltip term="content delivery network (CDN)">CDN</GlossaryTooltip>
  and Spectrum handle customer identity differently.
@@ -42,4 +42,4 @@ This means traffic for this hostname undergoes the standard Layer 7 CDN products
 
 If you want to prevent traffic for Layer-4-only Spectrum hostnames from being proxied through Layer 7 to your origin (including unwanted scans or requests), we recommend implementing a Layer 7 WAF (Web Application Firewall) rule. This rule can block traffic directed at specific hostnames or ports, ensuring that only legitimate traffic reaches your Spectrum service.
 
-For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
+For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
\ No newline at end of file
diff --git a/src/content/docs/spectrum/reference/logs.mdx b/src/content/docs/spectrum/reference/logs.mdx
index e5c27ce81e5be5e..0ee954278aec0d5 100644
--- a/src/content/docs/spectrum/reference/logs.mdx
+++ b/src/content/docs/spectrum/reference/logs.mdx
@@ -19,6 +19,8 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 
 ## Status Codes
 
+
+
 | Code | Description                                                                                        |
 | ---- | -------------------------------------------------------------------------------------------------- |
 | 0    | Connection was opened successfully.                                                                |
@@ -50,3 +52,4 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 | 533  | Internal error while resolving origin to an IP.                                                    |
 | 540  | The client/edge TLS handshake failed due to an invalid configuration.                              |
 | 999  | Unknown connection error.                                                                          |
+
diff --git a/src/content/docs/spectrum/reference/settings-by-plan.mdx b/src/content/docs/spectrum/reference/settings-by-plan.mdx
index 9865188065dbb98..c243f1c03952069 100644
--- a/src/content/docs/spectrum/reference/settings-by-plan.mdx
+++ b/src/content/docs/spectrum/reference/settings-by-plan.mdx
@@ -5,12 +5,19 @@ description: Spectrum API fields and settings available by Cloudflare plan.
 products:
   - spectrum
 weight: 0
+
 ---
 
+
+
 Certain fields in Spectrum request and response bodies require an Enterprise plan. To upgrade your plan, contact your account team.
 
 Spectrum properties requiring an Enterprise plan:
 
+
+
+
+
 | Name                 | Type    | Description                                                                                                                                                                                                                                                                                                              | Example                                                    |
 | -------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
 | `origin_dns`         | object  | Method and parameters used to discover the origin server address via DNS. Valid record types are `A`, `AAAA`, `SRV` and empty (both `A` and `AAA`).<br />A request must contain either an `origin_dns` parameter or an `origin_direct` parameter. When both are specified the service returns an `HTTP 400 Bad Request`. | `origin_dns: {type: A, name: mqtt.example.com, ttl: 1200}` |
@@ -18,6 +25,11 @@ Spectrum properties requiring an Enterprise plan:
 | `proxy_protocol`     | string  | Enables Proxy Protocol to the origin. Spectrum supports `v1`, `v2`, and `simple` proxy protocols. Refer to [Proxy Protocol](/spectrum/how-to/enable-proxy-protocol/) for more details.                                                                                                                                   | `off`                                                      |
 | `ip_firewall`        | boolean | Enables IP Access rules for this application.                                                                                                                                                                                                                                                                            | `true`                                                     |
 | `tls`                | string  | Type of TLS termination for the application. Options are `off` (default, also known as Passthrough), `flexible`, `full`, and `strict`. Refer to [Configuration Options](/spectrum/reference/configuration-options/) for descriptions of each.                                                                            | `full`                                                     |
-| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic_type set to `direct`.                                                                                                                                                                                   | `true`                                                     |
+| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic\_type set to `direct`.                                                                                                                                                                                  | `true`                                                     |
+
+
+
+
 
 Review the [Spectrum API documentation](/api/resources/spectrum/subresources/apps/methods/list/) for example API requests.
+
diff --git a/src/content/docs/speed/aim.mdx b/src/content/docs/speed/aim.mdx
index 95fc9acbd18a0d7..c8139eed9a0013a 100644
--- a/src/content/docs/speed/aim.mdx
+++ b/src/content/docs/speed/aim.mdx
@@ -4,6 +4,7 @@ description: Measure real-world internet quality metrics for your visitors.
 products:
   - speed
 title: Aggregated Internet Measurement
+
 ---
 
 Aggregated Internet Measurement (AIM) helps you understand your Internet quality to identify scenarios that your Internet connection is good or bad for. Typically, an Internet speed test provides you with upload and download speeds, which may not always provide a holistic view of your Internet quality.
@@ -14,28 +15,28 @@ AIM uses a scoring rubric that assigns point values based on speed tests to help
 
 AIM analyzes the following metrics to generate your score:
 
-- Latency
-- Packet Loss
-- Download
-- Upload
-- Loaded Latency
-- Jitter
+* Latency
+* Packet Loss
+* Download
+* Upload
+* Loaded Latency
+* Jitter
 
-After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC. These scores will indicate how good your Internet is in each of these scenarios.
+After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC.  These scores will indicate how good your Internet is in each of these scenarios.
 
 The possible network scores are:
 
-- Bad
-- Poor
-- Average
-- Good
-- Great
+* Bad
+* Poor
+* Average
+* Good
+* Great
 
 ## Improve your network score
 
 You have a few options to help improve network scores.
 
-- **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
-- **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
-- **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
-- **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
+* **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
+* **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
+* **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
+* **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
diff --git a/src/content/docs/speed/glossary.mdx b/src/content/docs/speed/glossary.mdx
index 2fb9f99dba9493c..fc3634a28e51568 100644
--- a/src/content/docs/speed/glossary.mdx
+++ b/src/content/docs/speed/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Speed documentation.
 products:
   - speed
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Speed documentation.
 
diff --git a/src/content/docs/speed/observatory/dashboard.mdx b/src/content/docs/speed/observatory/dashboard.mdx
index 6a18975aceb0150..1017a25218c61a5 100644
--- a/src/content/docs/speed/observatory/dashboard.mdx
+++ b/src/content/docs/speed/observatory/dashboard.mdx
@@ -40,10 +40,11 @@ The **Network Performance** section shows timing data that can help pinpoint whe
 
 - **Time to First Byte (TTFB)**: Measures the time between the initial request and the first byte of the response.
 - **Time to Last Byte (TTLB) Breakdown**: Provides a breakdown of response phases:
-  - DNS resolution time
-  - TCP connection time
-  - Request processing time at the server
-  - Response transfer time
+
+    - DNS resolution time
+    - TCP connection time
+    - Request processing time at the server
+    - Response transfer time
 
 This breakdown helps identify whether delays are caused by DNS, connection setup, server processing, or response delivery.
 
@@ -76,4 +77,4 @@ Use the Speed Overview dashboard to:
 - Track **Core Web Vitals** to ensure a good user experience.
 - Analyze **Network Performance** to identify latency bottlenecks.
 - Diagnose errors with **HTTP Traffic** insights.
-- Confirm site reliability using **Synthetic Monitoring** results.
+- Confirm site reliability using **Synthetic Monitoring** results.
\ No newline at end of file
diff --git a/src/content/docs/speed/observatory/rum-beacon.mdx b/src/content/docs/speed/observatory/rum-beacon.mdx
index 8e343c58ee410d5..66c0e8035856ce1 100644
--- a/src/content/docs/speed/observatory/rum-beacon.mdx
+++ b/src/content/docs/speed/observatory/rum-beacon.mdx
@@ -8,6 +8,7 @@ tags:
   - Privacy
 sidebar:
   order: 4
+ 
 ---
 
 The RUM beacon is a JavaScript snippet that runs when a Cloudflare customer enables RUM through [Web Analytics](/web-analytics/) or [Observatory](/speed/observatory/). This script runs in users' browsers when they visit the customer's site, and its purpose is to collect performance-related data, for example, page load time, and send it to Cloudflare's systems for processing. This [data](/web-analytics/data-metrics/) is then presented to the customer, providing valuable insights into the website's performance and usage.
@@ -16,7 +17,7 @@ The RUM beacon script can be enabled into a webpage in two ways:
 
 - **One-click setup**: For [sites proxied through Cloudflare](/web-analytics/get-started/#sites-proxied-through-cloudflare) that have Web Analytics enabled, the snippet can be _automatically_ injected into pages as the HTML response passes through Cloudflare's edge network to the browser by simply enabling the automatic injection option.
 
-- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML.
+- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML. 
 
 ## Data collection
 
@@ -24,36 +25,36 @@ Once downloaded to the browser, the RUM beacon script runs as JavaScript in the
 
 The data collected from the browser is summarized in the table below:
 
-| Field                  | Example                                                                                                              | Description                                  | How it is collected                                                                                                                                                                                                                                                                                       |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pageloadId`           | 0c698922-8d60-40bf-85ac-7982b5f8034d                                                                                 | The unique ID for the page.                  | Generated in the browser code.                                                                                                                                                                                                                                                                            |
-| `referrer`             | https://cfrumtest.com/                                                                                               | The referring page URL.                      | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
-| `startTime`            | 1693488419352                                                                                                        | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                                                                                                                                                                         |
-| `memory`               | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }`                               | Measures memory heap size.                   | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                                                                                                                                                                                    |
-| `timings`              | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming)                    | Timing data.                                 | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)                                                                                                                                                           |
-| `timingV2`             | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data.                      | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
-| `resources`            | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)     | Resource timing data.                        | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                                                                                                                                                                    |
-| `firstPaint`           | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)           | Paint timing data.                           | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)                                                                                                                                                                                          |
-| `firstContentfulPaint` | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `FCP`                  | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `LCP`                  | 209                                                                                                                  | Largest Contentful Paint metric.             | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `CLS`                  | 0.001                                                                                                                | Cumulative Layout Shift metric.              | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-|  |
-| `TTFB`                 | 0.03                                                                                                                 | Time to First Byte metric.                   | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `INP`                  | 1.23                                                                                                                 | Interaction to Next Paint metric.            | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `landingPath`          | https://cfrumtest.com/                                                                                               | The landing page URL.                        | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
+| Field      | Example  | Description  | How it is collected    |
+|------------|----------|--------------|------------------------|
+| `pageloadId`  | 0c698922-8d60-40bf-85ac-7982b5f8034d  | The unique ID for the page. | Generated in the browser code.  |
+| `referrer`    | https://cfrumtest.com/ | The referring page URL. | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
+| `startTime`  | 1693488419352  | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                        |
+| `memory` | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }` | Measures memory heap size. | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                              |
+| `timings` | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming) | Timing data. | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)     |
+| `timingV2` | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                   |
+| `resources`  | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | Resource timing data.  | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                     |
+| `firstPaint` | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | Paint timing data. | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) |
+| `firstContentfulPaint` | 209  | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1] |
+| `FCP`        | 209 | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `LCP`        | 209 | Largest Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `CLS`        | 0.001 | Cumulative Layout Shift metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+                                                           |
+| `TTFB`       | 0.03 | Time to First Byte metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `INP`        | 1.23 | Interaction to Next Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `landingPath`| https://cfrumtest.com/  | The landing page URL. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | 
 
 ## Data processing
 
 RUM data is generally processed at the nearest Cloudflare data center based on how the incoming request is routed. This is determined by a number of factors including [Anycast](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) and [Unimog](https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/). Since RUM data does not use location services, it may be processed in a different country or region from where it originated. Although the RUM service receives the client/source IP address from the beacon as part of normal HTTP request handling process, it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs.
 
-## Privacy information
+## Privacy information 
 
 The RUM beacon script does not store any data in the browser or access any storage data, such as [cookies](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie), [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage), [sessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage), IP address, or [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB). The data we collect is performance data from the browser performance [APIs](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API). This performance data is ephemeral and only relates to the current webpage that is being viewed. If the user refreshes their browser, all the previous performance data is gone and new performance data starts being available. This data is not stored or accessed from anywhere on the device, it is only available as in-memory data.
 
 ## RUM excluding EEA/EU
 
-Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.
+Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.   
 
 Free customers have RUM enabled automatically, with EU traffic excluded, and can switch it off if they prefer. Customers on other plans may enable RUM as needed.
 
@@ -63,4 +64,5 @@ Free customers have RUM enabled automatically, with EU traffic excluded, and can
 
     </div>
 
-[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
+
+[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
\ No newline at end of file
diff --git a/src/content/docs/speed/observatory/run-speed-test.mdx b/src/content/docs/speed/observatory/run-speed-test.mdx
index 5ae182cbf4eb09c..b86b5c58655a186 100644
--- a/src/content/docs/speed/observatory/run-speed-test.mdx
+++ b/src/content/docs/speed/observatory/run-speed-test.mdx
@@ -50,19 +50,20 @@ RUM uses a lightweight JavaScript beacon to collect the information Observatory
 Quota limits for the number of tests you can run per month are currently the following:
 
 | Plan       | One-off tests | Recurring tests | Frequency of recurring tests |
-| ---------- | ------------- | --------------- | ---------------------------- |
+|------------|---------------|-----------------|------------------------------|
 | Pro        | 50            | 5               | Daily                        |
 | Business   | 100           | 10              | Daily                        |
 | Enterprise | 150           | 15              | Daily                        |
 
 **Available Regions (all plans):**
 
-| Region              | Region                 | Region                  |
-| ------------------- | ---------------------- | ----------------------- |
-| Iowa, USA           | Hamina, Finland        | Changhua County, Taiwan |
-| South Carolina, USA | Madrid, Spain          | Tokyo, Japan            |
-| North Virginia, USA | St. Ghislain, Belgium  | Osaka, Japan            |
-| Dallas, USA         | Eemshaven, Netherlands | Jurong West, Singapore  |
-| Oregon, USA         | Milan, Italy           | Sydney, Australia       |
-| London, England     | Paris, France          | Mumbai, India           |
-| Frankfurt, Germany  | Tel Aviv, Israel       | São Paulo, Brazil       |
+| Region                | Region              | Region             |
+|------------------------|---------------------|--------------------|
+| Iowa, USA             | Hamina, Finland     | Changhua County, Taiwan |
+| South Carolina, USA   | Madrid, Spain       | Tokyo, Japan       |
+| North Virginia, USA   | St. Ghislain, Belgium | Osaka, Japan      |
+| Dallas, USA           | Eemshaven, Netherlands | Jurong West, Singapore |
+| Oregon, USA           | Milan, Italy        | Sydney, Australia  |
+| London, England       | Paris, France       | Mumbai, India      |
+| Frankfurt, Germany    | Tel Aviv, Israel    | São Paulo, Brazil  |
+
diff --git a/src/content/docs/speed/observatory/test-results.mdx b/src/content/docs/speed/observatory/test-results.mdx
index c6bf699af5e19a6..a9b42c82085bb1a 100644
--- a/src/content/docs/speed/observatory/test-results.mdx
+++ b/src/content/docs/speed/observatory/test-results.mdx
@@ -6,6 +6,7 @@ products:
 title: Understand test results
 sidebar:
   order: 3
+
 ---
 
 The test result page shows you how your website performed regarding several key industry metrics. Some of these metrics are presented for synthetic tests and the real user monitoring, and others only apply to synthetic tests or only to real user monitoring.
@@ -35,19 +36,19 @@ These metrics result from the synthetic tests.
 
 These metrics are collected as part of the real user data, as they require real user interaction with a page.
 
-| Metric                                                  | Definition                                                                                                                 |
-| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page. |
+| Metric                                                  | Definition                                                                                                                                                                       |
+| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page.                                                       |
 
 Refer to [Data and metrics](/web-analytics/data-metrics/) for more information about the metrics you can find in the Real User Monitoring dashboard. You can find details about [Core Web Vitals](/web-analytics/data-metrics/core-web-vitals/), the debug view and the data collected.
 
 ## Network monitoring metrics
 
-| Metric                                                     | Definition                                                                                                        |
-| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Wait Time                                                  | Measures the time spent waiting for the server to send back the first byte of a response after a request is made. |
-| Load Time                                                  | Measures the total time it takes for a web page to fully load in a user’s browser from the network.               |
-| Time to First Byte ([TTFB](https://web.dev/articles/ttfb)) | Measures the duration between initiating a web page request and receiving the first byte from the server.         |
-| Server Response Time                                       | Measures the time it takes for a server to respond to a request from a user's browser.                            |
-| Connect Time                                               | Measures the time taken to establish a connection between the user's browser and the web server.                  |
-| TLS Time                                                   | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.       |
+| Metric                                            | Definition                                                                                                          |
+| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| Wait Time | Measures the time spent waiting for the server to send back the first byte of a response after a request is made.                                           |
+| Load Time | Measures the total time it takes for a web page to fully load in a user’s browser from the network.                                                         |
+| Time to First Byte ([TTFB](https://web.dev/articles/ttfb))  | Measures the duration between initiating a web page request and receiving the first byte from the server. |
+| Server Response Time | Measures the time it takes for a server to respond to a request from a user's browser.                                                           |
+| Connect Time | Measures the time taken to establish a connection between the user's browser and the web server.                                                         | 
+| TLS Time | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.                                                  | 
\ No newline at end of file
diff --git a/src/content/docs/speed/optimization/content/apo.mdx b/src/content/docs/speed/optimization/content/apo.mdx
index f706bab097e8e8c..bf378bf7685846b 100644
--- a/src/content/docs/speed/optimization/content/apo.mdx
+++ b/src/content/docs/speed/optimization/content/apo.mdx
@@ -7,4 +7,5 @@ title: Automatic Platform Optimization
 external_link: /automatic-platform-optimization/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/content/compression.mdx b/src/content/docs/speed/optimization/content/compression.mdx
index e021ae803ef2b55..93ad3418e9054de 100644
--- a/src/content/docs/speed/optimization/content/compression.mdx
+++ b/src/content/docs/speed/optimization/content/compression.mdx
@@ -22,9 +22,9 @@ Cloudflare compresses content in two ways: between Cloudflare and your website v
 In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.
 
 <Stream
-	id="9103750883217fcb9274666fd57ebac1"
-	title="Content compression"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
+  id="9103750883217fcb9274666fd57ebac1"
+  title="Content compression"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
 />
 
 :::note
diff --git a/src/content/docs/speed/optimization/content/early-hints.mdx b/src/content/docs/speed/optimization/content/early-hints.mdx
index f40d05197e0f6de..3263897899e5f21 100644
--- a/src/content/docs/speed/optimization/content/early-hints.mdx
+++ b/src/content/docs/speed/optimization/content/early-hints.mdx
@@ -7,4 +7,5 @@ title: Early Hints
 external_link: /cache/advanced-configuration/early-hints/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
index 778b154ef43acac..b5627175aec2342 100644
--- a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
+++ b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
@@ -28,10 +28,7 @@ To test that the Fonts feature is working correctly, follow these steps:
 For the feature to work, the response HTML (when the feature is disabled) must include a link tag with `href` pointing to `fonts.googleapis.com`. You can check this on the browser by viewing the source code of the webpage. As an example of what to look for, the following link tag is for the Roboto Google Font:
 
 ```html
-<link
-	href="https://fonts.googleapis.com/css2?family=Roboto&display=swap"
-	rel="stylesheet"
-/>
+<link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">
 ```
 
 If the tag does not exist in the HTML, but you are still sure that your page is using Google Fonts, it might be that your hosting provider is optimizing your Google Fonts on the server. This can prevent Cloudflare Fonts from working properly.
diff --git a/src/content/docs/speed/optimization/content/index.mdx b/src/content/docs/speed/optimization/content/index.mdx
index e1a5decf41e6b26..a778f875d6059cc 100644
--- a/src/content/docs/speed/optimization/content/index.mdx
+++ b/src/content/docs/speed/optimization/content/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
index 115046f10c28f12..148e6cc5d93b485 100644
--- a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
+++ b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
@@ -23,13 +23,15 @@ Rocket Loader will still optimize the loading of all other scripts on the page.
 
 :::note
 
+
 If Rocket Loader is only impacting a specific page, use a [Configuration Rule](/rules/configuration-rules/) to exclude that page by URL.
 
+
 :::
 
 ## Limitations
 
-- Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
-- If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
-- The `data-cfasync` attribute must be added before the `src` attribute.
-- Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
+* Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
+* If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
+* The `data-cfasync` attribute must be added before the `src` attribute.
+* Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
diff --git a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
index e17a32a6e8a3b82..8b56ec1c37765c8 100644
--- a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
+++ b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
@@ -43,11 +43,11 @@ Shared dictionaries work when all of the following are true:
 
 The protocol uses two new request and response headers and two new content encodings:
 
-| Header                           | Direction        | Purpose                                                                                             |
-| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- |
+| Header                           | Direction        | Purpose                                                                                            |
+| -------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
 | `Use-As-Dictionary`              | Origin → browser | Marks a response as usable as a dictionary for future requests matching the supplied `match` value. |
-| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.            |
-| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).      |
+| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.           |
+| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).     |
 
 The first response for a versioned asset includes `Use-As-Dictionary`, and the browser stores the response. On subsequent requests for assets matching the pattern, the browser sends `Available-Dictionary: :<sha256>:` and adds `dcb, dcz` to `Accept-Encoding`. Your origin compresses the new asset against the dictionary and returns it with `Content-Encoding: dcb` or `dcz`. The browser uses its stored copy to reconstruct the full response.
 
diff --git a/src/content/docs/speed/optimization/content/smart-hints.mdx b/src/content/docs/speed/optimization/content/smart-hints.mdx
index 9df2f2740a81901..74a30be29625c81 100644
--- a/src/content/docs/speed/optimization/content/smart-hints.mdx
+++ b/src/content/docs/speed/optimization/content/smart-hints.mdx
@@ -7,4 +7,5 @@ title: Smart Hints
 external_link: https://blog.cloudflare.com/smart-hints/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/speed/optimization/content/speed-brain.mdx b/src/content/docs/speed/optimization/content/speed-brain.mdx
index 979f0002e29fc50..e0de7cbfe69f617 100644
--- a/src/content/docs/speed/optimization/content/speed-brain.mdx
+++ b/src/content/docs/speed/optimization/content/speed-brain.mdx
@@ -10,13 +10,7 @@ sidebar:
 description: Learn how Speed Brain enhances web performance by prefetching likely next pages, improving metrics like LCP and TTFB.
 ---
 
-import {
-	FeatureTable,
-	TabItem,
-	Tabs,
-	APIRequest,
-	DashButton,
-} from "~/components";
+import { FeatureTable, TabItem, Tabs, APIRequest, DashButton } from "~/components";
 
 Speed Brain is a tool for improving web page performance by prefetching the most likely next navigation.
 
@@ -117,6 +111,7 @@ You can also configure Speed Brain using Terraform. For more details, refer to t
 ## Caveats
 
 - Since prefetch responses are not guaranteed to be rendered by the browser, Speed Brain includes two safeguards to minimize the risk of [unsafe prefetching](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#unsafe_prefetching):
+
   - Speed Brain will not prefetch on routes that run Workers. Without this safeguard, prefetch requests could inadvertently run Worker logic that assumes the incoming request is a normal (that is, not a prefetch) request. An example of this could be an incrementing page view counter running in a Worker. A page view counter should not increment if the page is not actually rendered in the browser.
 
   - Prefetch requests will never reach origin servers. Prefetch requests only serve content that is stored in Cloudflare’s Cache. If the content is not in Cache, the prefetch request will not continue to origin servers. Without this safeguard, origin server state could be modified despite the prefetch response not being rendered in the browser. An example of this could be a prefetch `GET` request to a sign-out URL inadvertently triggering a sign-out action on the server.
diff --git a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
index e125fcbbe0254bf..274ba87dc345bae 100644
--- a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Optimization issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/image-resizing.mdx b/src/content/docs/speed/optimization/images/image-resizing.mdx
index 6594df5754962d0..5e5c8613ef540aa 100644
--- a/src/content/docs/speed/optimization/images/image-resizing.mdx
+++ b/src/content/docs/speed/optimization/images/image-resizing.mdx
@@ -7,4 +7,5 @@ title: Image Resizing
 external_link: /images/optimization/transformations/overview/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/images/index.mdx b/src/content/docs/speed/optimization/images/index.mdx
index c079cac0a17b480..d027767b2a3faf5 100644
--- a/src/content/docs/speed/optimization/images/index.mdx
+++ b/src/content/docs/speed/optimization/images/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/polish.mdx b/src/content/docs/speed/optimization/images/polish.mdx
index 631c4cbe263d8c9..c529447865e7b61 100644
--- a/src/content/docs/speed/optimization/images/polish.mdx
+++ b/src/content/docs/speed/optimization/images/polish.mdx
@@ -7,4 +7,5 @@ title: Polish
 external_link: /images/polish/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
index cb64aa9539c46b7..1f8d029c7d93ae9 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Image issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
index fb72840fc7b149a..9ac31a532e60906 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
@@ -5,6 +5,7 @@ products:
   - speed
 source: https://support.cloudflare.com/hc/en-us/articles/200168046-Will-Cloudflare-s-image-optimization-features-help-if-I-m-already-optimizing-images-
 title: Image optimization on optimized images
+
 ---
 
 Cloudflare's [image optimization features](/speed/optimization/images/) will likely not help much if you are already optimizing your images in some way (Smush.it, etc.).
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
index ce279de1efcba70..26bdaff52e6866e 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
@@ -6,4 +6,5 @@ products:
 title: Polish statuses
 external_link: /images/polish/cf-polished-statuses/
 weight: 0
+
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
index 12268c9dc18cddc..ed4e61afdf15934 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
@@ -15,9 +15,9 @@ If images are missing from your website, other Cloudflare features may be interf
 To troubleshoot:
 
 1. Perform one of the following actions:
-   - [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
-   - [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
-   - Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 
+   * [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
+   * [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
+   * Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 2. Retest the image load in a private browser tab.
 3. If the issue is not fixed, try another of the actions suggested in Step 1.
diff --git a/src/content/docs/speed/optimization/index.mdx b/src/content/docs/speed/optimization/index.mdx
index 83b3fba317047d6..bd80c971ba9878a 100644
--- a/src/content/docs/speed/optimization/index.mdx
+++ b/src/content/docs/speed/optimization/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The Optimization section will show you a list of Cloudflare products that are recommended for enhancing your website's performance.
 
diff --git a/src/content/docs/speed/optimization/measurement.mdx b/src/content/docs/speed/optimization/measurement.mdx
index 89a7f989f4b71dc..016533a4dd1986e 100644
--- a/src/content/docs/speed/optimization/measurement.mdx
+++ b/src/content/docs/speed/optimization/measurement.mdx
@@ -6,6 +6,7 @@ products:
 title: Measurement
 sidebar:
   order: 2
+
 ---
 
 Enable measurement to track your traffic in a privacy-first manner, optimizing your site's speed tools. To access this feature, you need to enable [Web Analytics](/web-analytics/) on your website. This analytics tool leverages [Real User Measurement](/speed/observatory/run-speed-test/#enable-real-user-monitoring-rum) (RUM) data, providing insights based on actual user interactions to enhance site performance effectively.
diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx
index 13e54b4c22eaedd..74d4e0a9ae7f530 100644
--- a/src/content/docs/speed/optimization/protocol/http2.mdx
+++ b/src/content/docs/speed/optimization/protocol/http2.mdx
@@ -56,10 +56,10 @@ The origin web server may be sending improperly formatted HTTP response headers.
 
 #### Resolution
 
-Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements:
+Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements: 
 
 - [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5)
-- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1)
+- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) 
 - [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1)
 
 ### Compression issues
diff --git a/src/content/docs/speed/optimization/protocol/index.mdx b/src/content/docs/speed/optimization/protocol/index.mdx
index 094dadd43d13cf2..fdfe4aa14eb11b1 100644
--- a/src/content/docs/speed/optimization/protocol/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
index 957822a95ff61cf..45783c25f400853 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
@@ -4,6 +4,7 @@ description: Fix Enhanced HTTP/2 Prioritization issues on iOS and Safari.
 products:
   - speed
 title: Enhanced HTTP/2 Prioritization negatively affects iOS/Safari devices
+
 ---
 
 Occasionally, [Enhanced HTTP/2 Prioritization](/speed/optimization/protocol/enhanced-http2-prioritization/) can negatively affect the experience of visitors using Safari on macOS or any browser on iOS.
@@ -16,8 +17,10 @@ If visitors using using Safari on macOS or any browser on iOS are experiencing i
 
 :::note
 
+
 Sometimes, [HTTP/2](/speed/optimization/protocol/http2/) will cause **Enhanced HTTP/2 Prioritization** to be re-enabled automatically.
 
 If you notice this happening, also disable **HTTP/2**.
 
+
 :::
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
index 804f216d9cf3f8c..0d6974f96123177 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Protocol optimization issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/recommendations.mdx b/src/content/docs/speed/optimization/recommendations.mdx
index aac4598f71a5531..1367d8efb7789e2 100644
--- a/src/content/docs/speed/optimization/recommendations.mdx
+++ b/src/content/docs/speed/optimization/recommendations.mdx
@@ -6,6 +6,7 @@ products:
 title: Recommendations
 sidebar:
   order: 1
+
 ---
 
 In the **Recommendations** tab, with one click you can enable all the recommended settings available for your plan. You can enable all the recommended settings at once or you can also just enable the ones you want.
diff --git a/src/content/docs/speed/smart-shield.mdx b/src/content/docs/speed/smart-shield.mdx
index 9fc997ea18add10..76f0af22755c9f7 100644
--- a/src/content/docs/speed/smart-shield.mdx
+++ b/src/content/docs/speed/smart-shield.mdx
@@ -7,4 +7,5 @@ title: Smart Shield
 sidebar:
   order: 4
 external_link: /smart-shield/
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/speed/troubleshooting.mdx b/src/content/docs/speed/troubleshooting.mdx
index 6f7d78e7f34c259..1a73653e90dc280 100644
--- a/src/content/docs/speed/troubleshooting.mdx
+++ b/src/content/docs/speed/troubleshooting.mdx
@@ -7,15 +7,12 @@ title: Troubleshooting
 hideChildren: true
 sidebar:
   order: 20
+
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 The following topics are useful for troubleshooting Speed issues.
 
-<ResourcesBySelector
-	directory="speed"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="speed" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+
diff --git a/src/content/docs/ssl/changelog.mdx b/src/content/docs/ssl/changelog.mdx
index 96577c758525512..c96ac0914a9da7c 100644
--- a/src/content/docs/ssl/changelog.mdx
+++ b/src/content/docs/ssl/changelog.mdx
@@ -16,7 +16,7 @@ import { ProductChangelog } from "~/components";
 
 ## 2024-10-18
 
-**New cloudflare_branding flag allows hostnames with over 64 characters for all CAs**
+**New cloudflare\_branding flag allows hostnames with over 64 characters for all CAs**
 
 To order certificates for hostnames longer than 64 characters, customers can now use the `cloudflare_branding` flag when ordering a certificate via [API](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/create/). Setting `cloudflare_branding` to `true` will cause `sni.cloudflaressl.com` to be used as the common name, while the long hostname is added as part of the subject alternative name (SAN).
 
@@ -24,4 +24,4 @@ To order certificates for hostnames longer than 64 characters, customers can now
 
 **SSL.com available with ACM and SSL for SaaS**
 
-SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
+SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
\ No newline at end of file
diff --git a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
index 129b0ea9d7b037b..fda3782b24250c6 100644
--- a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
@@ -15,4 +15,4 @@ import { Render } from "~/components";
 
 <Render file="add-client-certificate-rfc9440" product="ssl" />
 
-<Render file="forward-client-certificate" product="ssl" />
+<Render file="forward-client-certificate" product="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
index c362c3ea0cbfc69..20bc4a82a73822d 100644
--- a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
@@ -6,6 +6,7 @@ products:
 title: Revoke a client certificate
 sidebar:
   order: 8
+
 ---
 
 import { DashButton } from "~/components";
@@ -25,8 +26,10 @@ It is not possible to permanently delete client certificates generated with the
 
 :::caution[Important]
 
+
 After revoking a certificate, you must update any mTLS rules that check for the presence of a client certificate so that they block all requests that include a revoked certificate.
 
 For more information, refer to [Check for revoked certificates](/api-shield/security/mtls/configure/#check-for-revoked-certificates).
 
+
 :::
diff --git a/src/content/docs/ssl/concepts.mdx b/src/content/docs/ssl/concepts.mdx
index 074f33eaa264a9e..2f0333d5ec7c728 100644
--- a/src/content/docs/ssl/concepts.mdx
+++ b/src/content/docs/ssl/concepts.mdx
@@ -25,9 +25,9 @@ Since [Cloudflare's global network](https://www.cloudflare.com/network/) is at t
 The [edge certificates](/ssl/edge-certificates/) are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the [Cloudflare Dashboard](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
 
 <Stream
-	id="fe9344af4ab476bf81f4447000f36db66"
-	title="SSL/TLS concepts"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
+  id="fe9344af4ab476bf81f4447000f36db66"
+  title="SSL/TLS concepts"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
 />
 
 ### Origin certificate
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
index c4d44c211b0ec09..18550b308521f31 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
@@ -30,9 +30,9 @@ If you are a SaaS provider looking to restrict cipher suites for connections to
 
 Custom cipher suites is a hostname-level setting, which implies that:
 
-- When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
-- The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
-- If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
+* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
+* The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
+* If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
 
 ## Scope
 
@@ -50,4 +50,4 @@ This documentation only refers to connections [between clients and the Cloudflar
 
 Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hostname-priority/) to determine which setting to apply.
 
-ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
+ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
index c8b458d6184c218..7aae1bb58f1bbd9 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
@@ -16,31 +16,31 @@ tags:
 
 Cloudflare supports the following cipher suites by default. If needed, you can [restrict your website or application](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) to only use specific cipher suites.
 
-| Cipher name                      | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name                                     |
-| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------- |
-| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02b]    | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256       |
-| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca9]    | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 |
-| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02f]    | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256         |
-| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca8]    | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   |
-| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc023]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256       |
-| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                                              | \[0xc009]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA          |
-| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc027]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256         |
-| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc013]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA            |
-| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                                              | \[0x9c]      | TLS_RSA_WITH_AES_128_GCM_SHA256               |
-| AES128-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3c]      | TLS_RSA_WITH_AES_128_CBC_SHA256               |
-| AES128-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x2f]      | TLS_RSA_WITH_AES_128_CBC_SHA                  |
-| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02c]    | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384       |
-| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc024]    | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384       |
-| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc030]    | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384         |
-| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc028]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384         |
-| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc014]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA            |
-| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                                              | \[0x9d]      | TLS_RSA_WITH_AES_256_GCM_SHA384               |
-| AES256-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3d]      | TLS_RSA_WITH_AES_256_CBC_SHA256               |
-| AES256-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x35]      | TLS_RSA_WITH_AES_256_CBC_SHA                  |
-| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                                              | \[0x0a]      | TLS_RSA_WITH_3DES_EDE_CBC_SHA                 |
-| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x01} | TLS_AES_128_GCM_SHA256                        |
-| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x02} | TLS_AES_256_GCM_SHA384                        |
-| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x03} | TLS_CHACHA20_POLY1305_SHA256                  |
+| Cipher name | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name |
+| -------------------------------- | ---------------- | ------------------------------------------------------------------------ | ------------ | --------------------------------------------------- |
+| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02b]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256      |
+| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca9]    | TLS\_ECDHE\_ECDSA\_WITH\_CHACHA20\_POLY1305\_SHA256 |
+| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02f]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256        |
+| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca8]    | TLS\_ECDHE\_RSA\_WITH\_CHACHA20\_POLY1305\_SHA256   |
+| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc023]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256      |
+| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                   | \[0xc009]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA         |
+| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc027]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256        |
+| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc013]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA           |
+| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                   | \[0x9c]      | TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256               |
+| AES128-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3c]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256               |
+| AES128-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x2f]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA                  |
+| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02c]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384      |
+| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc024]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384      |
+| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc030]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384        |
+| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc028]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384        |
+| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc014]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA           |
+| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                   | \[0x9d]      | TLS\_RSA\_WITH\_AES\_256\_GCM\_SHA384               |
+| AES256-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3d]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256               |
+| AES256-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x35]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA                  |
+| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                   | \[0x0a]      | TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA                 |
+| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x01}  | TLS\_AES\_128\_GCM\_SHA256                          |
+| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x02}  | TLS\_AES\_256\_GCM\_SHA384                          |
+| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x03}  | TLS\_CHACHA20\_POLY1305\_SHA256                     |
 
 :::note[* TLS 1.3 minimum protocol]
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
index 186ef035f3bc82f..33d50ea3a037245 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Once you set up SSL/TLS on your application, you can adjust the following settings on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page:
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
index c5f7c351636e7ea..cb0cd6575e94980 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
@@ -8,14 +8,7 @@ sidebar:
   order: 13
 ---
 
-import {
-	FeatureTable,
-	TabItem,
-	Tabs,
-	APIRequest,
-	Render,
-	DashButton,
-} from "~/components";
+import { FeatureTable, TabItem, Tabs, APIRequest, Render, DashButton } from "~/components";
 
 Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer.
 
@@ -93,13 +86,13 @@ Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hos
 In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and authentication placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
 <APIRequest
-	path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
-	method="PUT"
-	json={{
-		value: "1.2",
+  path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
+  method="PUT"
+  json={{
+		"value": "1.2"
 	}}
 	parameters={{
-		setting_id: "min_tls_version",
+		setting_id: "min_tls_version"
 	}}
 />
 
@@ -107,6 +100,7 @@ In the following example, the minimum TLS version for a specific hostname will b
 
 If you are a SaaS provider looking to configure minimum TLS version for your custom hostnames, refer to the Cloudflare for SaaS [TLS management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version).
 
+
 ## Test supported TLS versions
 
-<Render file="test-tls-version" product="ssl" />
+<Render file="test-tls-version" product="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
index f302408667237f8..0e4362cf11468cb 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
@@ -10,14 +10,7 @@ tags:
   - TLS
 ---
 
-import {
-	Details,
-	FeatureTable,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { Details, FeatureTable, Render, TabItem, Tabs, DashButton } from "~/components";
 
 TLS 1.3 enables the latest version of the TLS protocol (when supported) for improved security and performance.
 
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
index 9de3f9a1b2d4d87..4a643427148e0dc 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
@@ -6,15 +6,19 @@ products:
 title: API commands
 sidebar:
   order: 5
+
 ---
 
 Use the following API commands to manage advanced certificates. If you are using our API for the first time, review our [API documentation](/fundamentals/api/).
 
-| Command                                                                                                                                                        | Method   | Endpoint                                             | Additional notes                                                                            |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                                                | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
-| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                                                              | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                  |
-| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                                                   | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
+
+
+| Command                                                                                                                                                 | Method   | Endpoint                                             | Additional notes                                                                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                     | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
+| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                                                                             |
+| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                       | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
 | [List certificate packs in a zone](/api/resources/ssl/subresources/certificate_packs/methods/list/)                                                            | `GET`    | `zones/<<ZONE_ID>>/ssl/certificate_packs?status=all` | This API call returns all certificate packs for a domain (Universal, Custom, and Advanced). |
 | List Cipher Suite settings: [Get zone setting](/api/resources/zones/subresources/settings/methods/get/) with `ciphers` as the setting name in the URI path     | `GET`    | `zones/<<ZONE_ID>>/settings/ciphers`                 |                                                                                             |
 | Change Cipher Suite settings: [Edit zone setting](/api/resources/zones/subresources/settings/methods/edit/) with `ciphers` as the setting name in the URI path | `PATCH`  | `zones/<<ZONE_ID>>/settings/ciphers`                 | To restore default settings, send a blank array in the `value` parameter.                   |
+
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
index 6261626f47813e8..8bb9170bb3e5e55 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
@@ -10,13 +10,7 @@ description: Learn how to create, delete and perform other operations to manage
   your Cloudflare Advanced SSL certificates.
 ---
 
-import {
-	AvailableNotifications,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { AvailableNotifications, Render, TabItem, Tabs, DashButton } from "~/components";
 
 ## Create a certificate
 
diff --git a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
index 9612b1b4e300149..cd1a9df4c9a9acd 100644
--- a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
@@ -6,9 +6,10 @@ products:
 title: Backup certificates
 sidebar:
   order: 9
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 If Cloudflare is providing [authoritative DNS](/dns/zone-setups/full-setup/) for your domain, Cloudflare will issue a backup [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for every standard Universal certificate issued.
 
diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx
index d8baa4eef05cff2..81472be5e1532d4 100644
--- a/src/content/docs/ssl/edge-certificates/caa-records.mdx
+++ b/src/content/docs/ssl/edge-certificates/caa-records.mdx
@@ -77,3 +77,4 @@ Check CAA at all levels of your CNAME chain:
 dig yourdomain.com CAA +short
 dig cname-target.com CAA +short
 ```
+
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
index 96fb56d94da1db3..cc1c3b4df79dbed 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
@@ -6,6 +6,7 @@ products:
 title: Bundle methodologies
 sidebar:
   order: 4
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -42,4 +43,4 @@ The related value for the `bundle_method` parameter when using the [API](/api/re
 
 User-defined allows you to paste your own certificate chain and present that bundle to clients. If you are using a self-signed certificate (not recommended), you must use this mode.
 
-The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
+The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
index 450b178703c442c..b6e2aa56fcc596a 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
@@ -8,9 +8,10 @@ sidebar:
 head: []
 description: Learn how renewal and expiration work when using Cloudflare Custom
   SSL certificates.
+
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components";
+import { GlossaryTooltip, DashButton } from "~/components"
 
 ## Renew custom certificates
 
diff --git a/src/content/docs/ssl/edge-certificates/ech.mdx b/src/content/docs/ssl/edge-certificates/ech.mdx
index f41c594d329fe41..0fbfdfc7d498d82 100644
--- a/src/content/docs/ssl/edge-certificates/ech.mdx
+++ b/src/content/docs/ssl/edge-certificates/ech.mdx
@@ -35,7 +35,7 @@ In practice, this means that any intermediary that is looking at your traffic wi
 
 In the example below, a user is visiting `example.com`. Without ECH, any intermediate networks will be able to detect the website being accessed by the user. With ECH, the visible information will be limited to `cloudflare-ech.com` instead.
 
-<br />
+<br/>
 
 ```mermaid
 flowchart LR
@@ -46,7 +46,7 @@ A(User visits <code>example.com</code>)
     A -- Without ECH  --> D(intermediaries see <code>example.com</code>)-->B(Cloudflare)
 ```
 
-<br />
+<br/>
 
 For more details about ECH protocol technology, refer to our [introductory blog](https://blog.cloudflare.com/encrypted-client-hello/).
 
diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
index 01b85e22786233d..1f5ef82895c17f4 100644
--- a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
+++ b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
@@ -31,7 +31,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 | WEUR        | Western Europe        |
 | WNAM        | Western North America |
 
----
+***
 
 ## Available countries
 
@@ -39,7 +39,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 
 Examples of supported countries are Japan, Canada, India, and Australia.
 
----
+***
 
 ## Highest security data centers
 
diff --git a/src/content/docs/ssl/edge-certificates/index.mdx b/src/content/docs/ssl/edge-certificates/index.mdx
index e7cf9b2a13c1a4d..ffb763f9a56da56 100644
--- a/src/content/docs/ssl/edge-certificates/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/index.mdx
@@ -22,7 +22,7 @@ This behavior occurs when all of the following conditions are true:
 
 - The zone is on a [subdomain setup](/dns/zone-setups/subdomain-setup/).
 - The certificate has a subject or SAN that is a wildcard for the zone's parent domain.
-  :::
+:::
 
 ## Use cases
 
diff --git a/src/content/docs/ssl/edge-certificates/staging-environment.mdx b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
index 19eb3fbbdf32035..339031829e8da8c 100644
--- a/src/content/docs/ssl/edge-certificates/staging-environment.mdx
+++ b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
@@ -8,21 +8,22 @@ sidebar:
   order: 8
   badge:
     text: Beta
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Use your certificate staging environment to test new custom (modern) certificates before pushing them to your production environment. This process helps you solve potential certificate problems **before** there's an incident, such as when:
 
-- You make a mistake when uploading a new custom certificate.
-- You misunderstand the order of your certificates.
-- Clients have previously pinned your custom certificate, causing a TLS termination error.
+* You make a mistake when uploading a new custom certificate.
+* You misunderstand the order of your certificates.
+* Clients have previously pinned your custom certificate, causing a TLS termination error.
 
 ## Availability
 
 <FeatureTable id="ssl.staging_environment" />
 
----
+***
 
 ## Use your staging environment
 
@@ -48,9 +49,9 @@ curl --resolve <HOSTNAME>:<PORT>:<STAGING_IP> https://<HOSTNAME> -iv
 
 You should confirm whether:
 
-- TLS termination is successful.
-- The right certificate is being served at the edge.
-- Any clients are pinning the old certificate.
+* TLS termination is successful.
+* The right certificate is being served at the edge.
+* Any clients are pinning the old certificate.
 
 ### 3. Push certificate to production
 
@@ -77,7 +78,7 @@ If you roll out a custom (modern) certificate to production and encounter issues
 3. Select **Deactivate**.
 4. Select **Push to Staging**.
 
----
+***
 
 ## Limitations
 
@@ -89,5 +90,5 @@ Currently, staging environments are only available to Enterprise customers parti
 
 At the moment, staging environments have limited functionality:
 
-- Only custom (modern) certificates
-- Only accessed via the dashboard
+* Only custom (modern) certificates
+* Only accessed via the dashboard
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
index 70ebac7297e8244..3104afffd410349 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
@@ -9,15 +9,13 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Universal SSL
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your certificates.
 
-<AvailableNotifications
-	product="SSL/TLS"
-	notificationFilter="Universal SSL Alert"
-/>
+<AvailableNotifications product="SSL/TLS" notificationFilter="Universal SSL Alert" />
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
index 818182201a137ed..b594fc5113be2e0 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
@@ -25,11 +25,13 @@ To avoid errors with your domain, either [upload a custom certificate](/ssl/edge
 If you disable Universal SSL, you may experience errors with the following scenarios:
 
 - **Enabled features**:
+
   - [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/)
   - [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/)
   - [Opportunistic Encryption](/ssl/edge-certificates/additional-options/opportunistic-encryption/)
 
 - **Other setups**:
+
   - [Page Rules](/rules/page-rules/) that redirect traffic to HTTPS
   - HTTP to HTTPS redirects at your origin web server
 
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
index e18e34ce743050c..9caba32b58ee4c2 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
@@ -17,10 +17,10 @@ If a certificate issuance times out, Cloudflare tells you where in the chain of
 
 To resolve timeout issues, try one or more of the following options:
 
-- Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
-- [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
-- Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
-- Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
+* Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
+* [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
+* Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
+* Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
 
 ## Delete certificates
 
diff --git a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
index 08f0a67ed984db2..f525157d8b998f3 100644
--- a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with Keyless SSL
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The way you set up Keyless SSL depends on how you route traffic to your keyless server.
 
diff --git a/src/content/docs/ssl/keyless-ssl/glossary.mdx b/src/content/docs/ssl/keyless-ssl/glossary.mdx
index ac939b4a2946953..e64a45f3d972083 100644
--- a/src/content/docs/ssl/keyless-ssl/glossary.mdx
+++ b/src/content/docs/ssl/keyless-ssl/glossary.mdx
@@ -9,6 +9,7 @@ head:
   - tag: title
     content: Glossary | Keyless SSL
 description: Learn more about the common terms related to Keyless SSL.
+
 ---
 
 ## Cloudflare Keyless SSL key server (“key server”)
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
index 3804977bcd01432..0ca6a0fe976beb8 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
@@ -69,6 +69,7 @@ brew install azure-cli
    ```
 
 4. If the key server is running in an Azure VM in the same account, use **Managed services** for authorization:
+
    1. Enable managed services on the VM in the UI.
    2. Give your service user (associated with your VM) HSM sign permissions
 
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
index 18a3cbbad52b8b7..df9caf0b486ccaf 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
@@ -14,4 +14,4 @@ You can use Cloudflare Keyless SSL with [Fortanix Data Security Manager (DSM)](h
 
 You must have a [Data Security Manager Enterprise Tier](https://www.fortanix.com/start-your-free-trial) and set up a group and an application assigned to the group.
 
-For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
+For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
\ No newline at end of file
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
index a28200144687ee8..fd448a9791cb833 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
@@ -6,11 +6,12 @@ products:
 title: Hardware security modules
 sidebar:
   order: 2
+
 ---
 
 In addition to private keys stored on disk, Keyless SSL supports keys stored in a Hardware Security Module (HSM) via the PKCS#11 standard. Keyless uses PKCS#11 for signing and decrypting payloads without having direct access to the private keys.
 
----
+***
 
 ## Why use Keyless SSL with an HSM?
 
@@ -18,7 +19,7 @@ Hardware Security Modules (HSMs) facilitate a higher level of protection for you
 
 Moreover, many HSMs are also capable of generating keys and producing cryptographically secure randomness. Some are purpose-built to perform cryptographic computations more efficiently.
 
----
+***
 
 ## Communicating using PKCS#11
 
@@ -44,4 +45,4 @@ Also, the following cloud HSM offerings have been tested with Keyless SSL:
 - [Azure Managed HSM](/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm/)
 - [Fortanix DSM](/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm/)
 - [IBM Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/ibm-cloud-hsm/)
-- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
+- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
\ No newline at end of file
diff --git a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
index f2176ee72e743cd..459196f2dd78e7d 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
@@ -6,6 +6,7 @@ products:
 title: High availability
 sidebar:
   order: 3
+
 ---
 
 The Cloudflare Keyless SSL server runs as a single binary with minimal dependencies and is designed to be robust and reliable. However, the network between your key server and Cloudflare may not be, which could prevent new TLS connections.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/index.mdx b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
index 78c6fba61f6ed5e..4c22ae751c29b2c 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Reference — Keyless SSL
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information on Keyless SSL, refer to the following resources:
 
diff --git a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
index b0c023f66fe907a..08105e84ad0afe6 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
@@ -8,6 +8,7 @@ tags:
   - TLS
 sidebar:
   order: 7
+
 ---
 
 Keyless Delegation is Cloudflare's implementation of the emerging delegated credentials standard ([RFC 9345](https://www.rfc-editor.org/rfc/rfc9345.html)). When you upload a certificate for use with Keyless that has the special extension permitting the use of delegated credentials, Cloudflare will automatically produce a delegated credential and use it at the edge with clients that support this feature. The handshakes will complete without the extra latency induced by reaching back to the Keyless Server, and there are [additional advantages to flexibility in algorithm choice](https://blog.cloudflare.com/keyless-delegation/).
diff --git a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
index 292a3c66bcec5c5..0e9d1a59aa73910 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
@@ -6,10 +6,13 @@ products:
 title: Key server metrics
 sidebar:
   order: 5
+
 ---
 
 The gokeyless key server exposes a [Prometheus](https://prometheus.io/) metrics endpoint that you can use to monitor signing performance, error rates, connection health, and certificate expiry. This endpoint can also be scraped by the OpenTelemetry Collector Prometheus receiver, making the metrics available to any OpenTelemetry-compatible backend.
 
+
+
 ## Metrics endpoint
 
 By default, metrics are served at:
@@ -28,24 +31,24 @@ The endpoint serves only `/metrics`. There are no additional HTTP endpoints such
 
 All histogram metrics share the same bucket configuration: 15 exponential buckets starting at 100 microseconds, doubling each step up to approximately 1.64 seconds, plus a final `+Inf` bucket.
 
-| Bucket | Upper bound            |
-| ------ | ---------------------- |
-| 1      | 100 µs                 |
-| 2      | 200 µs                 |
-| 3      | 400 µs                 |
-| 4      | 800 µs                 |
-| 5      | 1.6 ms                 |
-| 6      | 3.2 ms                 |
-| 7      | 6.4 ms                 |
-| 8      | 12.8 ms                |
-| 9      | 25.6 ms                |
-| 10     | 51.2 ms                |
-| 11     | 102 ms                 |
-| 12     | 205 ms                 |
-| 13     | 410 ms                 |
-| 14     | 819 ms                 |
-| 15     | ~1.64 s                |
-| +Inf   | Anything above ~1.64 s |
+| Bucket | Upper bound |
+| --- | --- |
+| 1 | 100 µs |
+| 2 | 200 µs |
+| 3 | 400 µs |
+| 4 | 800 µs |
+| 5 | 1.6 ms |
+| 6 | 3.2 ms |
+| 7 | 6.4 ms |
+| 8 | 12.8 ms |
+| 9 | 25.6 ms |
+| 10 | 51.2 ms |
+| 11 | 102 ms |
+| 12 | 205 ms |
+| 13 | 410 ms |
+| 14 | 819 ms |
+| 15 | ~1.64 s |
+| +Inf | Anything above ~1.64 s |
 
 :::note
 When using a hardware security module (HSM) with a PKCS#11 session pool, the pool wait timeout is hardcoded at 10 seconds. A pool exhaustion event will therefore always appear in the `+Inf` bucket. Spikes in `+Inf` observations on signing operations with `error="cryptography error"` are a direct indicator of PKCS#11 session pool saturation.
@@ -66,45 +69,45 @@ The `opcode` label uses the full constant name from the gokeyless protocol.
 
 #### RSA operations
 
-| `opcode` label       | Wire value | Description                                                                   |
-| -------------------- | ---------- | ----------------------------------------------------------------------------- |
-| `OpRSADecrypt`       | `0x01`     | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3)     |
-| `OpRSASignMD5SHA1`   | `0x02`     | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
-| `OpRSASignSHA1`      | `0x03`     | RSA PKCS#1 v1.5 signature over SHA1                                           |
-| `OpRSASignSHA224`    | `0x04`     | RSA PKCS#1 v1.5 signature over SHA224                                         |
-| `OpRSASignSHA256`    | `0x05`     | RSA PKCS#1 v1.5 signature over SHA256                                         |
-| `OpRSASignSHA384`    | `0x06`     | RSA PKCS#1 v1.5 signature over SHA384                                         |
-| `OpRSASignSHA512`    | `0x07`     | RSA PKCS#1 v1.5 signature over SHA512                                         |
-| `OpRSAPSSSignSHA256` | `0x35`     | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3           |
-| `OpRSAPSSSignSHA384` | `0x36`     | RSASSA-PSS signature over SHA384                                              |
-| `OpRSAPSSSignSHA512` | `0x37`     | RSASSA-PSS signature over SHA512                                              |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpRSADecrypt` | `0x01` | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3) |
+| `OpRSASignMD5SHA1` | `0x02` | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
+| `OpRSASignSHA1` | `0x03` | RSA PKCS#1 v1.5 signature over SHA1 |
+| `OpRSASignSHA224` | `0x04` | RSA PKCS#1 v1.5 signature over SHA224 |
+| `OpRSASignSHA256` | `0x05` | RSA PKCS#1 v1.5 signature over SHA256 |
+| `OpRSASignSHA384` | `0x06` | RSA PKCS#1 v1.5 signature over SHA384 |
+| `OpRSASignSHA512` | `0x07` | RSA PKCS#1 v1.5 signature over SHA512 |
+| `OpRSAPSSSignSHA256` | `0x35` | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3 |
+| `OpRSAPSSSignSHA384` | `0x36` | RSASSA-PSS signature over SHA384 |
+| `OpRSAPSSSignSHA512` | `0x37` | RSASSA-PSS signature over SHA512 |
 
 #### ECDSA operations
 
-| `opcode` label       | Wire value | Description                                                      |
-| -------------------- | ---------- | ---------------------------------------------------------------- |
-| `OpECDSASignMD5SHA1` | `0x12`     | ECDSA signature over MD5+SHA1 combined hash                      |
-| `OpECDSASignSHA1`    | `0x13`     | ECDSA signature over SHA1                                        |
-| `OpECDSASignSHA224`  | `0x14`     | ECDSA signature over SHA224                                      |
-| `OpECDSASignSHA256`  | `0x15`     | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
-| `OpECDSASignSHA384`  | `0x16`     | ECDSA signature over SHA384                                      |
-| `OpECDSASignSHA512`  | `0x17`     | ECDSA signature over SHA512                                      |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpECDSASignMD5SHA1` | `0x12` | ECDSA signature over MD5+SHA1 combined hash |
+| `OpECDSASignSHA1` | `0x13` | ECDSA signature over SHA1 |
+| `OpECDSASignSHA224` | `0x14` | ECDSA signature over SHA224 |
+| `OpECDSASignSHA256` | `0x15` | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
+| `OpECDSASignSHA384` | `0x16` | ECDSA signature over SHA384 |
+| `OpECDSASignSHA512` | `0x17` | ECDSA signature over SHA512 |
 
 #### Other signing
 
-| `opcode` label  | Wire value | Description                                                                  |
-| --------------- | ---------- | ---------------------------------------------------------------------------- |
-| `OpEd25519Sign` | `0x18`     | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpEd25519Sign` | `0x18` | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
 
 #### Sealing and infrastructure operations
 
-| `opcode` label | Wire value | Description                                                                                           |
-| -------------- | ---------- | ----------------------------------------------------------------------------------------------------- |
-| `OpSeal`       | `0x21`     | Encrypt a blob using the server's sealing key — used for TLS session tickets                          |
-| `OpUnseal`     | `0x22`     | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated  |
-| `OpRPC`        | `0x23`     | Execute a named function registered on the server. Available to all connection types                  |
-| `OpCustom`     | `0x24`     | Execute a custom function set in the server configuration. Available to unrestricted connections only |
-| `OpPing`       | `0xF1`     | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved      |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpSeal` | `0x21` | Encrypt a blob using the server's sealing key — used for TLS session tickets |
+| `OpUnseal` | `0x22` | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated |
+| `OpRPC` | `0x23` | Execute a named function registered on the server. Available to all connection types |
+| `OpCustom` | `0x24` | Execute a custom function set in the server configuration. Available to unrestricted connections only |
+| `OpPing` | `0xF1` | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved |
 
 ---
 
@@ -121,15 +124,15 @@ This metric does not include time a request spends waiting for a connection sema
 
 Opcodes are grouped into coarser categories for this label:
 
-| `type` label | Opcodes included                                                  |
-| ------------ | ----------------------------------------------------------------- |
-| `rsa`        | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*`             |
-| `ecdsa`      | All `OpECDSASign*`                                                |
-| `ed25519`    | `OpEd25519Sign`                                                   |
-| `rpc`        | `OpRPC`                                                           |
-| `custom`     | `OpCustom`                                                        |
-| `other`      | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
-| `unknown`    | Any unrecognised opcode byte                                      |
+| `type` label | Opcodes included |
+| --- | --- |
+| `rsa` | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*` |
+| `ecdsa` | All `OpECDSASign*` |
+| `ed25519` | `OpEd25519Sign` |
+| `rpc` | `OpRPC` |
+| `custom` | `OpCustom` |
+| `other` | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
+| `unknown` | Any unrecognised opcode byte |
 
 :::note
 `OpPing` is grouped into `other` alongside `OpSeal` and `OpUnseal`. Ping round-trip latency cannot be separated from seal and unseal operation latency in this metric.
@@ -139,20 +142,20 @@ Opcodes are grouped into coarser categories for this label:
 
 For successful requests the value is `no error`. All other values indicate a failed operation.
 
-| `error` label                                       | Description                             | Common cause                                                                                          |
-| --------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| `no error`                                          | Operation completed successfully        | —                                                                                                     |
-| `cryptography error`                                | HSM or signing operation failed         | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
-| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result           | Key not loaded in keystore, incorrect SKI in request                                                  |
-| `read failure`                                      | I/O read error during the operation     | Disk error reading key file                                                                           |
-| `version mismatch`                                  | Protocol version not supported          | Client and server version skew                                                                        |
-| `bad opcode`                                        | Unknown opcode received                 | `OpCustom` sent with no custom handler configured                                                     |
-| `unexpected opcode`                                 | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request                                         |
-| `malformed message`                                 | TLV parse failure                       | Corrupt or truncated packet                                                                           |
-| `internal error`                                    | Non-cryptographic server-side failure   | Sealer is nil, RPC dispatch error                                                                     |
-| `certificate not found`                             | Certificate lookup failed               | Certificate not loaded                                                                                |
-| `sealing key expired`                               | `OpUnseal` blob is too old to decrypt   | TLS session ticket key rotation — blob sealed with a key that has since been retired                  |
-| `remote configuration error`                        | Remote key server is misconfigured      | Key points to an unreachable or misconfigured remote key server                                       |
+| `error` label | Description | Common cause |
+| --- | --- | --- |
+| `no error` | Operation completed successfully | — |
+| `cryptography error` | HSM or signing operation failed | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
+| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result | Key not loaded in keystore, incorrect SKI in request |
+| `read failure` | I/O read error during the operation | Disk error reading key file |
+| `version mismatch` | Protocol version not supported | Client and server version skew |
+| `bad opcode` | Unknown opcode received | `OpCustom` sent with no custom handler configured |
+| `unexpected opcode` | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request |
+| `malformed message` | TLV parse failure | Corrupt or truncated packet |
+| `internal error` | Non-cryptographic server-side failure | Sealer is nil, RPC dispatch error |
+| `certificate not found` | Certificate lookup failed | Certificate not loaded |
+| `sealing key expired` | `OpUnseal` blob is too old to decrypt | TLS session ticket key rotation — blob sealed with a key that has since been retired |
+| `remote configuration error` | Remote key server is misconfigured | Key points to an unreachable or misconfigured remote key server |
 
 ---
 
@@ -194,16 +197,16 @@ It is **not** recorded for `OpPing`, `OpSeal`, `OpUnseal`, `OpRPC`, or `OpCustom
 
 Counts connection-level transport failures. This metric reflects problems at the network or TLS layer — it does not count signing errors or key lookup failures, which are reported in the `error` label of the duration histograms.
 
-| Scenario                                             | Counted? |
-| ---------------------------------------------------- | -------- |
-| TLS handshake failure                                | No       |
-| Client disconnected before TLS handshake (EOF)       | No       |
-| Failure determining connection trust level after TLS | Yes      |
-| Non-EOF read error on an established connection      | Yes      |
-| Write error when delivering a response               | Yes      |
-| Read timeout — graceful connection drain             | No       |
-| Signing error, including PKCS#11 pool timeout        | No       |
-| Key not found                                        | No       |
+| Scenario | Counted? |
+| --- | --- |
+| TLS handshake failure | No |
+| Client disconnected before TLS handshake (EOF) | No |
+| Failure determining connection trust level after TLS | Yes |
+| Non-EOF read error on an established connection | Yes |
+| Write error when delivering a response | Yes |
+| Read timeout — graceful connection drain | No |
+| Signing error, including PKCS#11 pool timeout | No |
+| Key not found | No |
 
 ---
 
@@ -215,19 +218,18 @@ Counts connection-level transport failures. This metric reflects problems at the
 Reports the expiration time (`NotAfter`) of each certificate loaded by the key server as a Unix timestamp. One time series is emitted per certificate.
 
 This metric is updated:
-
 - At startup, for the server authentication certificate (`auth_cert`) and the Cloudflare CA certificate (`cloudflare_ca_cert`).
 - On each successful inbound TLS connection, for the peer certificates presented by the connecting client.
 
-| Label       | Description                                                                              |
-| ----------- | ---------------------------------------------------------------------------------------- |
-| `source`    | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
-| `serial_no` | Certificate serial number                                                                |
-| `cn`        | Subject Common Name                                                                      |
-| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names                            |
-| `ca`        | `1` if the certificate is a CA certificate, `0` otherwise                                |
-| `server`    | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise                   |
-| `client`    | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise                   |
+| Label | Description |
+| --- | --- |
+| `source` | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
+| `serial_no` | Certificate serial number |
+| `cn` | Subject Common Name |
+| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names |
+| `ca` | `1` if the certificate is a CA certificate, `0` otherwise |
+| `server` | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise |
+| `client` | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise |
 
 :::note
 `server_utilization` is a registered `GaugeVec` metric that is never written to by the key server. Because no label values are ever set, it emits no time series in the `/metrics` output at all. Do not use it.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
index 4edb4db09bab546..22b7833a2be107e 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
@@ -6,6 +6,7 @@ products:
 title: Scaling and benchmarking
 sidebar:
   order: 4
+
 ---
 
 Cloudflare's Keyless SSL technology was designed to scale to accommodate any sized workload using vertical and horizontal scaling, and pre-computation techniques wherever possible, such as ECDSA. The goals of the architectural design of the key server are to minimize latency while maximizing signing operations per second.
@@ -14,7 +15,7 @@ Each key server uses a worker pool model, with incoming client connections handl
 
 Where needed, multiple key servers can be deployed and balanced between using your preferred ingress load balancing configuration. For full high availability, make sure to deploy sufficient key servers to handle twice the expected workload.
 
----
+***
 
 ## Key type
 
@@ -24,7 +25,7 @@ ECDSA signing can be broken down into two steps. Since the first step — genera
 
 Additional details can be found in the [gokeyless server readme file](https://github.com/cloudflare/gokeyless#readme) file.
 
----
+***
 
 ## Benchmarks
 
diff --git a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
index 725673be1dbd8c2..4f8047f3f0bc964 100644
--- a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
+++ b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
@@ -6,6 +6,7 @@ products:
 title: Upgrade your key server
 sidebar:
   order: 4
+
 ---
 
 Periodically, you may need to update your key server when using Cloudflare's Keyless SSL.
@@ -24,6 +25,8 @@ To upgrade your key server:
 
 :::caution
 
+
 If you are running a [high availability configuration](/ssl/keyless-ssl/reference/high-availability/), upgrade one server at a time as new TLS connections will fail to terminate at Cloudflare's global network without a functioning key server.
 
+
 :::
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
index bda18f6939d8966..c8ca40f070b5e2a 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
@@ -24,9 +24,10 @@ Global, [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/
 - Make sure your zone is using an [SSL/TLS encryption mode](/ssl/origin-configuration/ssl-modes/) of **Full** or higher.
 
 - Consider your security and certificate needs:
-  - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
 
-  - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
+   - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
+
+   - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
 
 ## 1. Download the Cloudflare certificate
 
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
index 5ab7622aa6b0069..d2d6befaa600c0d 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Set up Authenticated Origin Pulls
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
index 8a042656568dd34..051fcf061c534ca 100644
--- a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
+++ b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
@@ -28,19 +28,19 @@ The list order is based on how the cipher suites appear in the [ClientHello](htt
 
 | Cipher name                        | TLS 1.0 | TLS 1.1 | TLS 1.2 | TLS 1.3 |
 | ---------------------------------- | ------- | ------- | ------- | ------- |
-| AEAD-AES128-GCM-SHA256 [^1]        | ❌      | ❌      | ❌      | ✅      |
-| AEAD-AES256-GCM-SHA384 [^1]        | ❌      | ❌      | ❌      | ✅      |
-| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌      | ❌      | ❌      | ✅      |
-| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES128-GCM-SHA256        | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES128-SHA               | ✅      | ✅      | ✅      | ❌      |
-| AES128-GCM-SHA256                  | ❌      | ❌      | ✅      | ❌      |
-| AES128-SHA                         | ✅      | ✅      | ✅      | ❌      |
-| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES256-GCM-SHA384        | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES256-SHA384            | ❌      | ❌      | ✅      | ❌      |
-| AES256-SHA                         | ✅      | ✅      | ✅      | ❌      |
-| DES-CBC3-SHA                       | ✅      | ❌      | ❌      | ❌      |
+| AEAD-AES128-GCM-SHA256 [^1]        | ❌       | ❌       | ❌       | ✅       |
+| AEAD-AES256-GCM-SHA384 [^1]        | ❌       | ❌       | ❌       | ✅       |
+| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌       | ❌       | ❌       | ✅       |
+| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES128-GCM-SHA256        | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES128-SHA               | ✅       | ✅       | ✅       | ❌       |
+| AES128-GCM-SHA256                  | ❌       | ❌       | ✅       | ❌       |
+| AES128-SHA                         | ✅       | ✅       | ✅       | ❌       |
+| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES256-GCM-SHA384        | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES256-SHA384            | ❌       | ❌       | ✅       | ❌       |
+| AES256-SHA                         | ✅       | ✅       | ✅       | ❌       |
+| DES-CBC3-SHA                       | ✅       | ❌       | ❌       | ❌       |
 
 ### TLS 1.3 cipher suites
 
@@ -67,4 +67,4 @@ ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RS
 ssl_prefer_server_ciphers on;
 ```
 
-[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
+[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
\ No newline at end of file
diff --git a/src/content/docs/ssl/origin-configuration/index.mdx b/src/content/docs/ssl/origin-configuration/index.mdx
index ca68ac364da293b..aac15f2f4132e15 100644
--- a/src/content/docs/ssl/origin-configuration/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn more about SSL/TLS protection options for your origin servers:
 
diff --git a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
index 6669b3202cadc81..b417523729d50b6 100644
--- a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
+++ b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
@@ -64,7 +64,7 @@ If the user does not have **API Access**, this error is returned.
 
 Make sure that the user creating the certificate has access to the API. You can check in the account **Members** page.
 
-<DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 - The default setting for the account is specified in the card **Enable API Access**.
 - Specific user API Access (which can override the default setting) is presented after selecting the user in the list of members.
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
index c19aaa19e4e96d1..087e14efa75240d 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
@@ -16,9 +16,9 @@ import { Stream, Render, TabItem, Tabs } from "~/components";
 When you set your encryption mode to **Full**, Cloudflare allows HTTPS connections between your visitor and Cloudflare and makes connections to the origin using the scheme requested by the visitor. If your visitor uses `http`, then Cloudflare connects to the origin using plaintext HTTP and vice versa.
 
 <Stream
-	id="a1e79096a2b042e0525a8543c232279a"
-	title="Configure Full encryption mode"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
+  id="a1e79096a2b042e0525a8543c232279a"
+  title="Configure Full encryption mode"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
 />
 
 ## Use when
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
index ffbf39cb4685b3c..d914207fd292d04 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
@@ -45,7 +45,7 @@ Automatic SSL/TLS leverages advanced methods developed by the SSL/TLS Recommende
 Automatic SSL/TLS will not change your setting to a less secure encryption mode. For example, if your origin certificate expires, the encryption mode will not change from **Full (strict)** to **Full**. You must ensure the validity of your origin SSL/TLS configuration at all times.
 :::
 
-Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode. If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
+Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode.  If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
 
 Flexible → Full/Strict transitions are handled with extra caution since the origin scheme change (HTTP → HTTPS) alters cache keys. In this case, the ramp-up may proceed more slowly to allow cache warm-up before resuming standard increments.
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
index 44f4f531ad50fd4..60489481ea636f2 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
@@ -23,11 +23,12 @@ When you set your encryption mode to **Strict (SSL-Only Origin Pull)**, connecti
 The certificate presented by the origin will be validated the same as with [Full (strict) mode](/ssl/origin-configuration/ssl-modes/full-strict/).
 
 <Stream
-	id="f407072cb5b4837c8c3a58a69cde90b5"
-	title="Configure Strict encryption mode"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
+  id="f407072cb5b4837c8c3a58a69cde90b5"
+  title="Configure Strict encryption mode"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
 />
 
+
 ## Use when
 
 You want the most secure configuration available for your origin, you are an Enterprise customer, and you meet the requirements for [**Full (strict)** mode](/ssl/origin-configuration/ssl-modes/full-strict/).
diff --git a/src/content/docs/ssl/reference/all-features.mdx b/src/content/docs/ssl/reference/all-features.mdx
index e4526a1b070534c..83243c2d35356e9 100644
--- a/src/content/docs/ssl/reference/all-features.mdx
+++ b/src/content/docs/ssl/reference/all-features.mdx
@@ -7,12 +7,13 @@ sidebar:
   order: 9
 head: []
 description: Review information on all Cloudflare SSL/TLS features and their availability.
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="ssl" />
+<ProductFeatures id="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/browser-compatibility.mdx b/src/content/docs/ssl/reference/browser-compatibility.mdx
index 964b497ae00d5c6..a7af16592d73bd7 100644
--- a/src/content/docs/ssl/reference/browser-compatibility.mdx
+++ b/src/content/docs/ssl/reference/browser-compatibility.mdx
@@ -8,6 +8,7 @@ sidebar:
 head: []
 description: Review information about browser compatibility for the different
   Cloudflare SSL/TLS offerings.
+
 ---
 
 Cloudflare attempts to provide compatibility for as wide a range of user agents (browsers, API clients, etc.) as possible. However, the specific set of supported clients can vary depending on the different SSL/TLS certificate types, your visitor's [browser version](#non-sni-support), and the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that issues the certificate.
@@ -30,13 +31,13 @@ Although [SNI extensions](https://www.cloudflare.com/learning/ssl/what-is-sni/)
 
 To support non-SNI requests, you can:
 
-- [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
+* [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
 
   Note that `Legacy` custom certificates are not compatible with [BYOIP](/byoip/) and that, unlike [Universal SSL](/ssl/edge-certificates/universal-ssl/) or [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/), Cloudflare does not manage issuance and renewal for [custom certificates](/ssl/edge-certificates/custom-certificates/).
 
-- (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
+* (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
 
-- (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
+* (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
 
 ## HTTPS records
 
@@ -54,4 +55,4 @@ If you need HTTPS records without Universal SSL, you can manually add them, but
 
 Cloudflare's OCSP implementation uses HTTP/1.1 by default for plain HTTP connections.
 
-For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
+For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
index 455857836c90c94..2c27bca6871ec0e 100644
--- a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
+++ b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
@@ -7,13 +7,14 @@ sidebar:
   order: 4
 head: []
 description: Learn about how Cloudflare decides which certificate and associated SSL/TLS settings to apply to individual hostnames.
+
 ---
 
 import { GlossaryTooltip } from "~/components";
 
 When a new certificate is created, Cloudflare first deploys the certificate and then serves it.
 
----
+***
 
 ## Certificate deployment
 
@@ -41,17 +42,17 @@ For any given hostname, Cloudflare uses the following order to determine which c
 In this case, when the certificate with the closest expiration date is renewed, it will then become the one with the latest expiration date and get presented.
 :::
 
----
+***
 
 ## Certificate presentation
 
 Cloudflare uses the following order to determine the certificate and settings used during a TLS handshake:
 
-1. **SNI match**: Certificates and settings that match the SNI hostname _exactly_ take precedence.
+1. **SNI match**: Certificates and settings that match the SNI hostname *exactly* take precedence.
 2. **SNI wildcard match**: If there is not an exact match between the hostname and SNI hostname, Cloudflare uses certificates and settings that match an SNI wildcard.
 3. **IP address**: If no SNI is presented, Cloudflare uses certificate based on the IP address (the hostname can support TLS handshakes made without SNI).
 
----
+***
 
 ## Hostname priority
 
@@ -60,11 +61,13 @@ When multiple <GlossaryTooltip term="proxy status">proxied DNS records</Glossary
 Cloudflare determines this priority in the following order, assuming each record exists and is proxied (orange-clouded):
 
 1. **Exact hostname match**:
+
    1. [New custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) (belonging to a SaaS provider)
    2. [Legacy custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning/) (belonging to a SaaS provider)
    3. [DNS](/dns/proxy-status/) (belonging to the logical DNS zone)
 
 2. **Wildcard hostname match**:
+
    1. DNS (belonging to the logical DNS zone)
    2. New custom hostname (belonging to a SaaS provider)
 
@@ -76,9 +79,9 @@ If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudf
 
 Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`. Customer2 is a SaaS provider that creates and successfully [verifies the new custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/) `shop.example.com`. Afterward, traffic starts routing over Customer2's zone:
 
-- If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
-- If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
-- If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
+* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
+* If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
+* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
 
 #### Scenario 2
 
diff --git a/src/content/docs/ssl/reference/certificate-authorities.mdx b/src/content/docs/ssl/reference/certificate-authorities.mdx
index 07206f1e5b03d00..0acd5bbcd68336c 100644
--- a/src/content/docs/ssl/reference/certificate-authorities.mdx
+++ b/src/content/docs/ssl/reference/certificate-authorities.mdx
@@ -137,4 +137,4 @@ The following table lists the CAA record content for each CA:
 | SSL.com               | `ssl.com`                            |
 | Sectigo               | `sectigo.com`                        |
 
-[^1]: A payment gateway used with some ecommerce plugins.
+[^1]: A payment gateway used with some ecommerce plugins.
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/certificate-pinning.mdx b/src/content/docs/ssl/reference/certificate-pinning.mdx
index 0c8cf4aa06ead76..ab7622846e0f1d2 100644
--- a/src/content/docs/ssl/reference/certificate-pinning.mdx
+++ b/src/content/docs/ssl/reference/certificate-pinning.mdx
@@ -7,6 +7,7 @@ sidebar:
   order: 8
 head: []
 description: Learn why Cloudflare does not support HTTP public key pinning (HPKP) and consider an alternative solution to prevent certificate misissuance.
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
index 0886b9f6b8540b5..bf7f12feedcf976 100644
--- a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
+++ b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
@@ -5,6 +5,7 @@ products:
   - ssl
 source: https://support.cloudflare.com/hc/en-us/articles/4422920018317-Cloudflare-and-CVE-2019-1559
 title: Cloudflare and CVE-2019-1559
+
 ---
 
 The [GOLDENDOODLE and Zombie POODLE attacks](https://www.tripwire.com/state-of-security/vulnerability-management/zombie-poodle-goldendoodle/) affect applications that use certain cipher suites associated with TLS 1.2.
@@ -19,6 +20,6 @@ Even though your application is not vulnerable to CVE-2019-1559, some security s
 
 To remove these warnings, refer to [Customize cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) and exclude the following ciphers:
 
-- `ECDHE-ECDSA-AES256-SHA384`
-- `ECDHE-ECDSA-AES128-SHA256`
-- `ECDHE-RSA-AES256-SHA384`
+* `ECDHE-ECDSA-AES256-SHA384`
+* `ECDHE-ECDSA-AES128-SHA256`
+* `ECDHE-RSA-AES256-SHA384`
diff --git a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
index d90f31506bc85cd..c2b34ec0ba65fc4 100644
--- a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
+++ b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
@@ -34,31 +34,31 @@ Refer to [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum
 
 There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:
 
-- Header compression in TLS
-- Header compression in SPDY 3.1
-- RC4
-- SSL 3.0
-- Renegotiation with clients
-- DHE ciphersuites
-- Export-grade ciphers
+* Header compression in TLS
+* Header compression in SPDY 3.1
+* RC4
+* SSL 3.0
+* Renegotiation with clients
+* DHE ciphersuites
+* Export-grade ciphers
 
 Cloudflare mitigations protect against several attacks:
 
-- CRIME
-- BREACH
-- POODLE
-- RC4 Cryptographic Weaknesses
-- SSL Renegotiation Attack
-- Protocol Downgrade Attacks
-- FREAK
-- LogJam
-- 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
+* CRIME
+* BREACH
+* POODLE
+* RC4 Cryptographic Weaknesses
+* SSL Renegotiation Attack
+* Protocol Downgrade Attacks
+* FREAK
+* LogJam
+* 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
 
 Cloudflare provides additional mitigations for:
 
-- Heartbleed
-- Lucky Thirteen
-- CCS injection vulnerability
+* Heartbleed
+* Lucky Thirteen
+* CCS injection vulnerability
 
 Cloudflare has patched all servers against these vulnerabilities. Also, the [Cloudflare Web Application Firewall](/waf/) has managed rules that mitigate several of these vulnerabilities including Heartbleed and ShellShock.
 
@@ -70,5 +70,5 @@ Security scans that note the presence of ROBOT while on Cloudflare are a false p
 
 A vulnerability in the use of the Triple DES (3DES) encryption algorithm in the Transport Layer Security (TLS) protocol. Sweet32 is currently a proof of concept attack, there are no known examples of this in the wild. Cloudflare has manually mitigated the vulnerability for TLS 1.0 in the following manner:
 
-- The attacker must collect 32GB of data from a single TLS session.
-- Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
+* The attacker must collect 32GB of data from a single TLS session.
+* Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
diff --git a/src/content/docs/ssl/reference/index.mdx b/src/content/docs/ssl/reference/index.mdx
index 09459738c3be6af..cdb3e27983cc833 100644
--- a/src/content/docs/ssl/reference/index.mdx
+++ b/src/content/docs/ssl/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more on Cloudflare SSL/TLS, refer to these articles:
 
diff --git a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
index dac25cb8479e6f3..99bfb37d1c5d06d 100644
--- a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
@@ -34,13 +34,14 @@ This means that Entrust certificates will be issued using SSL.com roots.
 
 Since Cloudflare also [partners with SSL.com](/ssl/reference/certificate-authorities/), you can switch from uploading custom certificates to using Cloudflare-managed certificates. This change brings the following advantages:
 
-- Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
-- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
-- Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
-- If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
+* Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
+* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
+* Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
+* If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
 
 ## More resources
 
-- [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
-- [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
-- [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
+* [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
+* [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
+* [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
+
diff --git a/src/content/docs/ssl/reference/migration-guides/index.mdx b/src/content/docs/ssl/reference/migration-guides/index.mdx
index a2d9c7e09c8f5eb..c7d41fe832e31ba 100644
--- a/src/content/docs/ssl/reference/migration-guides/index.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 These guides walk you through the migration processes associated with various changes in Cloudflare's SSL/TLS infrastructure.
 
diff --git a/src/content/docs/ssl/reference/protocols.mdx b/src/content/docs/ssl/reference/protocols.mdx
index 5fc1e33f6ac60f0..4431c3f94d47833 100644
--- a/src/content/docs/ssl/reference/protocols.mdx
+++ b/src/content/docs/ssl/reference/protocols.mdx
@@ -13,10 +13,10 @@ tags:
 
 Cloudflare supports the following TLS protocols:
 
-- TLS 1.0
-- TLS 1.1
-- TLS 1.2
-- TLS 1.3
+* TLS 1.0
+* TLS 1.1
+* TLS 1.2
+* TLS 1.3
 
 TLS 1.0 is the [version that Cloudflare sets by default](/ssl/edge-certificates/additional-options/minimum-tls/) for all customers using certificate-based encryption.
 
@@ -42,12 +42,12 @@ TLS 1.3 has become widely adopted. As a general rule, Cloudflare recommends sett
 
 However, not all browser versions support TLS 1.2 and above. Depending on your particular business situation, this may present some limitations in using stronger encryption standards:
 
-- Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
+* Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
 
-- For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
+* For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
 
 ## Related resources
 
-- [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
-- [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
-- [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
+* [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
+* [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
+* [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
diff --git a/src/content/docs/ssl/saas.mdx b/src/content/docs/ssl/saas.mdx
index fcce7104fc2969a..3e85a7dff75970e 100644
--- a/src/content/docs/ssl/saas.mdx
+++ b/src/content/docs/ssl/saas.mdx
@@ -7,4 +7,5 @@ title: Cloudflare for SaaS
 external_link: /cloudflare-for-platforms/cloudflare-for-saas/
 sidebar:
   order: 7
+
 ---
diff --git a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
index 3061e3715c16c1c..e7e9028c7ed7c8e 100644
--- a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
@@ -171,4 +171,4 @@ When clicking `Approve Certificate` on a Certificate Approval renewal email, you
 
 ### Resolution
 
-Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
+Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
\ No newline at end of file
diff --git a/src/content/docs/ssl/troubleshooting/index.mdx b/src/content/docs/ssl/troubleshooting/index.mdx
index d6196df82ab4540..098ba6ffb1eb8d0 100644
--- a/src/content/docs/ssl/troubleshooting/index.mdx
+++ b/src/content/docs/ssl/troubleshooting/index.mdx
@@ -10,15 +10,11 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting
+
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 For FAQs and other troubleshooting information, refer to the following resources:
 
-<ResourcesBySelector
-	directory="ssl"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="ssl" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
diff --git a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
index 8499af2e2c86769..5b2b86f88806a9d 100644
--- a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
@@ -10,6 +10,7 @@ sidebar:
 learning_center:
   title: What is mixed content?
   link: https://www.cloudflare.com/learning/ssl/what-is-mixed-content/
+
 ---
 
 Domains added to Cloudflare receive SSL certificates and can serve traffic over HTTPS. However, after starting to use Cloudflare, some customers notice missing content or page rendering issues when they first serve HTTPS traffic.
@@ -20,7 +21,7 @@ Normally, if your website loads all resources securely over HTTPS, visitors obse
 
 This indicates your site has a working SSL certificate and all resources loaded by the site are loaded over HTTPS. The green lock assures visitors that their connection is safe. One of the [symptoms of mixed content](#symptoms-of-mixed-content-occurrence) is that different icons appear instead of the green lock icon.
 
----
+***
 
 ## Symptoms of mixed content occurrence
 
@@ -30,8 +31,8 @@ Most modern browsers block HTTP requests on secure HTTPS pages. Blocked content
 
 Each web browser uses different methods to warn visitors about mixed content on a website, potentially including:
 
-- A yellow triangle or information symbol beside the URL bar
-- Messages mentioning "secure content"
+* A yellow triangle or information symbol beside the URL bar
+* Messages mentioning "secure content"
 
 ### **Console logs**
 
@@ -45,7 +46,7 @@ For mixed content errors, the browser refuses to load the resources over an inse
 
 Information on using the browser’s debug tools to locate these issues are found in the documentation for [Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content) and [Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content). Alternatively, you can view your page source and find specific references of *http\://* for paths to other resources.
 
----
+***
 
 ## Resolution
 
@@ -59,12 +60,12 @@ There are two methods to resolve mixed content errors.
 
 ### WordPress users
 
-Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the _Automatic HTTPS rewrites_ option within the plugin.
+Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the *Automatic HTTPS rewrites* option within the plugin.
 
----
+***
 
 ## Related resources
 
-- [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
-- [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
-- [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
+* [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
+* [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
+* [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
diff --git a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
index 759b5d1a646ae8d..3ffbddefe30f522 100644
--- a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
+++ b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
@@ -14,11 +14,7 @@ description: Learn how to troubleshoot ERR_SSL_VERSION_OR_CIPHER_MISMATCH when
 
 import { Stream, Render } from "~/components";
 
-<Stream
-	id="03e51d8a6f9a15e16969b8cc117d9225"
-	title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public"
-/>
+<Stream id="03e51d8a6f9a15e16969b8cc117d9225" title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public" />
 
 After you [add a new domain](/fundamentals/manage-domains/add-site/) to Cloudflare, your visitors' browsers might display one of the following errors:
 
diff --git a/src/content/docs/stream/edit-videos/adding-captions.mdx b/src/content/docs/stream/edit-videos/adding-captions.mdx
index 1cadfef74b3cd32..a5d5afcbca787ae 100644
--- a/src/content/docs/stream/edit-videos/adding-captions.mdx
+++ b/src/content/docs/stream/edit-videos/adding-captions.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 5
 products:
   - stream
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -148,15 +149,15 @@ Example response:
 
 ```json
 {
-	"result": {
-		"language": "en",
-		"label": "English (auto-generated)",
-		"generated": true,
-		"status": "inprogress"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "language": "en",
+    "label": "English (auto-generated)",
+    "generated": true,
+    "status": "inprogress"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -252,15 +253,15 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-	"result": {
-		"language": "en",
-		"label": "English",
-		"generated": false,
-		"status": "ready"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "language": "en",
+    "label": "English",
+    "generated": false,
+    "status": "ready"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -338,23 +339,23 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-	"result": [
-		{
-			"language": "en",
-			"label": "English (auto-generated)",
-			"generated": true,
-			"status": "inprogress"
-		},
-		{
-			"language": "de",
-			"label": "Deutsch",
-			"generated": false,
-			"status": "ready"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "language": "en",
+      "label": "English (auto-generated)",
+      "generated": true,
+      "status": "inprogress"
+    },
+    {
+      "language": "de",
+      "label": "Deutsch",
+      "generated": false,
+      "status": "ready"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -370,7 +371,7 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/<VIDEO_UID>/ca
 
 ### Example response to get the caption file for a video
 
-```text
+``` text
 WEBVTT
 
 1
@@ -457,25 +458,25 @@ deleted.
 
 ```json
 {
-	"result": "",
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": "",
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 ## Limitations
 
-- A video must be uploaded before a caption can be attached to it. In the following
+* A video must be uploaded before a caption can be attached to it. In the following
   example URLs, the video's ID is referenced as `media_id`.
-- Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
+* Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
   formatted caption files. If you have a differently formatted caption file,
   use [a tool to convert your file to WebVTT](https://subtitletools.com/convert-to-vtt-online)
   prior to uploading it.
-- Videos may include several language captions, but each language must be unique.
+* Videos may include several language captions, but each language must be unique.
   For example, a video may have English, French, and German captions associated
   with it, but it cannot have two French captions.
-- Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
+* Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
   if you need to upload a larger file.
 
 ## Most common language codes
@@ -504,4 +505,4 @@ deleted.
 | pl            | Polish           |
 | uk            | Ukrainian        |
 | my            | Burmese          |
-| th            | Thai             |
+| th            | Thai             |
\ No newline at end of file
diff --git a/src/content/docs/stream/edit-videos/player-enhancements.mdx b/src/content/docs/stream/edit-videos/player-enhancements.mdx
index 17a4d16c0a03c04..c439bce5564db4f 100644
--- a/src/content/docs/stream/edit-videos/player-enhancements.mdx
+++ b/src/content/docs/stream/edit-videos/player-enhancements.mdx
@@ -4,8 +4,8 @@ title: Add player enhancements
 description: Customize the Cloudflare Stream player with branding, logos, and share links.
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 With player enhancements, you can modify your video player to incorporate elements of your branding such as your logo, and customize additional options to present to your viewers.
@@ -14,10 +14,10 @@ The player enhancements are automatically applied to videos using the Stream Pla
 
 ## Properties
 
-- `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
-- `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
-- `channel_link`: The URL users will be directed to when selecting the logo from the video player.
-- `logo`: A valid HTTPS URL for the image of your logo.
+* `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
+* `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
+* `channel_link`: The URL users will be directed to when selecting the logo from the video player.
+* `logo`: A valid HTTPS URL for the image of your logo.
 
 ## Customize your own player
 
@@ -61,6 +61,6 @@ You can also pull the JSON by using the endpoint below.
    <DashButton url="/?to=/:account/stream/videos" />
 
 2. Select a video from the list to edit it.
-3. Select the **Public Details** tab.
-4. From **Public Details**, enter information in the text fields for the properties you want to set.
-5. When you are done, select **Save**.
+4. Select the **Public Details** tab.
+5. From **Public Details**, enter information in the text fields for the properties you want to set.
+6. When you are done, select **Save**.
diff --git a/src/content/docs/stream/examples/dash-js.mdx b/src/content/docs/stream/examples/dash-js.mdx
index 734287e03dbb82d..08404220937a1dd 100644
--- a/src/content/docs/stream/examples/dash-js.mdx
+++ b/src/content/docs/stream/examples/dash-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and the DASH reference
   player (dash.js)
 tags:
diff --git a/src/content/docs/stream/examples/hls-js.mdx b/src/content/docs/stream/examples/hls-js.mdx
index db446e6987ec0c9..aeb76104307a2ce 100644
--- a/src/content/docs/stream/examples/hls-js.mdx
+++ b/src/content/docs/stream/examples/hls-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and the HLS reference
   player (hls.js)
 tags:
@@ -24,12 +25,12 @@ products:
 		<video id="video"></video>
 		<script>
 			if (Hls.isSupported()) {
-				const video = document.getElementById("video");
+				const video = document.getElementById('video');
 				const hls = new Hls();
 				hls.attachMedia(video);
 				hls.on(Hls.Events.MEDIA_ATTACHED, () => {
 					hls.loadSource(
-						"https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+						'https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8'
 					);
 				});
 			}
diff --git a/src/content/docs/stream/examples/index.mdx b/src/content/docs/stream/examples/index.mdx
index 53469dcc7069b34..8fb98577e0d6f90 100644
--- a/src/content/docs/stream/examples/index.mdx
+++ b/src/content/docs/stream/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: true
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/stream/examples/obs-from-scratch/index.mdx b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
index 6eab955a0b28cfb..ca8948b5ccc2a81 100644
--- a/src/content/docs/stream/examples/obs-from-scratch/index.mdx
+++ b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up and start your first Live Stream using OBS (Open Broadcaster
   Software) Studio
 pcx_content_type: example
diff --git a/src/content/docs/stream/examples/rtmps_playback.mdx b/src/content/docs/stream/examples/rtmps_playback.mdx
index c614726f2680f0a..206b7ad224a4c78 100644
--- a/src/content/docs/stream/examples/rtmps_playback.mdx
+++ b/src/content/docs/stream/examples/rtmps_playback.mdx
@@ -17,10 +17,9 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the RTMPS _playback_ key for your live input from either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/srt_playback.mdx b/src/content/docs/stream/examples/srt_playback.mdx
index 3b5100f826b36a3..86ff42d0f0555d5 100644
--- a/src/content/docs/stream/examples/srt_playback.mdx
+++ b/src/content/docs/stream/examples/srt_playback.mdx
@@ -17,10 +17,9 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the SRT Playback URL for your live input from either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/stream-player.mdx b/src/content/docs/stream/examples/stream-player.mdx
index a948e755d04215e..b542eeb0bb0f3c4 100644
--- a/src/content/docs/stream/examples/stream-player.mdx
+++ b/src/content/docs/stream/examples/stream-player.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with the Cloudflare Stream Player
 tags:
   - Playback
@@ -18,12 +19,12 @@ products:
 	<head> </head>
 	<body>
 		<div style="position: relative; padding-top: 56.25%;">
-			<iframe
-				src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-				style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-				allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-				allowfullscreen="true"
-			></iframe>
+		<iframe
+			src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+			style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+			allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+			allowfullscreen="true"
+		></iframe>
 		</div>
 	</body>
 </html>
diff --git a/src/content/docs/stream/examples/video-js.mdx b/src/content/docs/stream/examples/video-js.mdx
index e6a2aad84dcfd9f..e8fbb571e4df8ae 100644
--- a/src/content/docs/stream/examples/video-js.mdx
+++ b/src/content/docs/stream/examples/video-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and Video.js
 tags:
   - Playback
@@ -31,7 +32,7 @@ products:
 		</video-js>
 
 		<script>
-			const vid = document.getElementById("vid1");
+			const vid = document.getElementById('vid1');
 			const player = videojs(vid);
 		</script>
 	</body>
diff --git a/src/content/docs/stream/examples/vidstack.mdx b/src/content/docs/stream/examples/vidstack.mdx
index fee573dfe355731..50ee3a7e270f9f3 100644
--- a/src/content/docs/stream/examples/vidstack.mdx
+++ b/src/content/docs/stream/examples/vidstack.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and Vidstack
 tags:
   - Playback
@@ -18,13 +19,13 @@ products:
 There's a few options to choose from when getting started with Vidstack, follow any of the links
 below to get setup. You can replace the player `src` with `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8` to test Cloudflare Stream.
 
-- [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
-- [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
-- [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
-- [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
-- [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
-- [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
-- [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
+* [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
+* [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
+* [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
+* [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
+* [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
+* [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
+* [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
 
 ## Examples
 
diff --git a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
index 84765138fc82658..67fd72638c29427 100644
--- a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
+++ b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - stream
 ---
-
 import { DashButton } from "~/components";
 
 Stream provides analytics about both live video and video uploaded to Stream, via the GraphQL API described below, as well as on the Stream **Analytics** page of the Cloudflare dashboard.
diff --git a/src/content/docs/stream/getting-analytics/index.mdx b/src/content/docs/stream/getting-analytics/index.mdx
index ddc5d2b46f2d12e..0b87d38fd44efbc 100644
--- a/src/content/docs/stream/getting-analytics/index.mdx
+++ b/src/content/docs/stream/getting-analytics/index.mdx
@@ -6,21 +6,20 @@ sidebar:
   order: 8
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 Stream provides server-side analytics that can be used to:
 
-- Identify most viewed video content in your app or platform.
-- Identify where content is viewed from and when it is viewed.
-- Understand which creators on your platform are publishing the most viewed content, and analyze trends.
+* Identify most viewed video content in your app or platform.
+* Identify where content is viewed from and when it is viewed.
+* Understand which creators on your platform are publishing the most viewed content, and analyze trends.
 
 You can access data on either:
-
 - The Stream **Analytics** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/analytics" />
+   <DashButton url="/?to=/:account/stream/analytics" />
 
 - The [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics).
 
diff --git a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
index 2f19eae42ea7fc3..b4650f2f9bc28c2 100644
--- a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
+++ b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 2
 products:
   - stream
+
 ---
 
 The Stream player has full support for live viewer counts by default. To get the viewer count for live videos for use with third party players, make a `GET` request to the `/views` endpoint.
diff --git a/src/content/docs/stream/manage-video-library/index.mdx b/src/content/docs/stream/manage-video-library/index.mdx
index b4ece17f01bbf40..f1c87b325b33406 100644
--- a/src/content/docs/stream/manage-video-library/index.mdx
+++ b/src/content/docs/stream/manage-video-library/index.mdx
@@ -9,3 +9,4 @@ sidebar:
 products:
   - stream
 ---
+
diff --git a/src/content/docs/stream/manage-video-library/searching.mdx b/src/content/docs/stream/manage-video-library/searching.mdx
index 78979f3e8fe99a6..385d98f5df957d0 100644
--- a/src/content/docs/stream/manage-video-library/searching.mdx
+++ b/src/content/docs/stream/manage-video-library/searching.mdx
@@ -4,6 +4,7 @@ title: Search for videos
 description: Search your Cloudflare Stream video library by name using the Stream API.
 products:
   - stream
+
 ---
 
 You can search for videos by name through the Stream API by adding a `search` query parameter to the [list media files](/api/resources/stream/methods/list/) endpoint.
diff --git a/src/content/docs/stream/stream-api.mdx b/src/content/docs/stream/stream-api.mdx
index 3cb2866bfef54bb..14a6a735991b555 100644
--- a/src/content/docs/stream/stream-api.mdx
+++ b/src/content/docs/stream/stream-api.mdx
@@ -7,4 +7,5 @@ sidebar:
   order: 11
 products:
   - stream
+
 ---
diff --git a/src/content/docs/stream/stream-live/custom-domains.mdx b/src/content/docs/stream/stream-live/custom-domains.mdx
index 9d386faca81de66..cbea1246aae4f56 100644
--- a/src/content/docs/stream/stream-live/custom-domains.mdx
+++ b/src/content/docs/stream/stream-live/custom-domains.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 3
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 With custom ingest domains, you can configure your RTMPS feeds to use an ingest URL that you specify instead of using `live.cloudflare.com.`
@@ -21,6 +21,7 @@ Custom Ingest Domains cannot be configured for domains with [zone holds](/fundam
 
 :::
 
+
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
 
    <DashButton url="/?to=/:account/stream/inputs" />
diff --git a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
index 6cc5f62c4cb10f5..de3dd780bfe12a4 100644
--- a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
+++ b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
@@ -9,16 +9,18 @@ sidebar:
   order: 4
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 You can enable downloads for live stream videos from the Cloudflare dashboard. Videos are available for download after they enter the **Ready** state.
 
 :::note
 
+
 Downloadable MP4s are only available for live recordings under four hours. Live recordings exceeding four hours can be played at a later time but cannot be downloaded as an MP4.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
diff --git a/src/content/docs/stream/stream-live/dvr-for-live.mdx b/src/content/docs/stream/stream-live/dvr-for-live.mdx
index 3bcb1c067f39da8..47ae2985c0d2fce 100644
--- a/src/content/docs/stream/stream-live/dvr-for-live.mdx
+++ b/src/content/docs/stream/stream-live/dvr-for-live.mdx
@@ -13,14 +13,14 @@ manifest URL.
 
 ## Stream Player
 
-```html title="Stream Player embed format"
+``` html title="Stream Player embed format"
 <div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
+  <iframe
+    src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
+    style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+    allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+    allowfullscreen="true"
+  ></iframe>
 </div>
 ```
 
@@ -37,7 +37,7 @@ When DVR mode is enabled the Stream Player will:
 
 ## HLS manifest for custom players
 
-```text title="HLS manifest URL format"
+``` text title="HLS manifest URL format"
 https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/manifest/video.m3u8?dvrEnabled=true
 ```
 
diff --git a/src/content/docs/stream/stream-live/index.mdx b/src/content/docs/stream/stream-live/index.mdx
index 7baf513e8a40a50..3234ba97f8bbef7 100644
--- a/src/content/docs/stream/stream-live/index.mdx
+++ b/src/content/docs/stream/stream-live/index.mdx
@@ -9,6 +9,7 @@ sidebar:
   order: 4
 products:
   - stream
+
 ---
 
 Cloudflare Stream lets you or your users [stream live video](https://www.cloudflare.com/learning/video/what-is-live-streaming/), and play live video in your website or app, without managing and configuring any of your own infrastructure.
@@ -36,7 +37,7 @@ With ABR, client video players need to be provided with estimates of how much ba
 
 ### How it works
 
-If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution. This ensures that as many viewers as possible view the highest quality level.
+If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution.  This ensures that as many viewers as possible view the highest quality level.
 
 Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the manifest will be higher — a stream like this has a high bitrate and requires more bandwidth. This ensures that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
 
@@ -58,7 +59,7 @@ After the live stream ends, you can [replay live stream recordings](/stream/stre
 
 Stream Live is billed identically to the rest of Cloudflare Stream.
 
-- You pay $5 per 1000 minutes of recorded video.
-- You pay $1 per 1000 minutes of delivered video.
+* You pay $5 per 1000 minutes of recorded video.
+* You pay $1 per 1000 minutes of delivered video.
 
 All Stream Live videos are automatically recorded. There is no additional cost for encoding and packaging live videos.
diff --git a/src/content/docs/stream/stream-live/live-instant-clipping.mdx b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
index 7c329e9302fd291..900ea4ee817bc3f 100644
--- a/src/content/docs/stream/stream-live/live-instant-clipping.mdx
+++ b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
@@ -10,8 +10,10 @@ Stream supports generating clips of live streams and recordings so creators and
 
 :::note[Note:]
 
+
 Clipping works differently for uploaded / on-demand videos. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
 
+
 :::
 
 ## Prerequisites
@@ -30,12 +32,18 @@ To help users replay and seek recent content, request a preview manifest by addi
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID||INPUT_ID>/manifest/video.m3u8?duration=5m
 ```
 
-- `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
+
+
+* `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
+
 
 When the preview manifest is delivered, inspect the headers for two properties:
 
-- `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the _broadcast_ start time, not the _preview_ start time.
-- `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an _input_ ID because the clip URL should reference the _video_ ID.
+
+
+* `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the *broadcast* start time, not the *preview* start time.
+* `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an *input* ID because the clip URL should reference the *video* ID.
+
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -51,44 +59,38 @@ let currentPreviewVideoID;
 
 // Override the pLoader (playlist loader) to read the manifest headers:
 class pLoader extends Hls.DefaultConfig.loader {
-	constructor(config) {
-		super(config);
-		var load = this.load.bind(this);
-		this.load = function (context, config, callbacks) {
-			if (context.type == "manifest") {
-				var onSuccess = callbacks.onSuccess;
-				// copy the existing onSuccess handler to fire it later.
-
-				callbacks.onSuccess = function (
-					response,
-					stats,
-					context,
-					networkDetails,
-				) {
-					// The fourth argument here is undocumented in HLS.js but contains
-					// the response object for the manifest fetch, which gives us headers:
-
-					currentPreviewStart = parseFloat(
-						networkDetails.getResponseHeader("preview-start-seconds"),
-					);
-					// Save the start time of the preview manifest
-
-					currentPreviewVideoID =
-						networkDetails.getResponseHeader("stream-media-id");
-					// Save the video ID in case the preview was loaded with an input ID
-
-					onSuccess(response, stats, context);
-					// And fire the existing success handler.
-				};
-			}
-			load(context, config, callbacks);
-		};
-	}
+  constructor(config) {
+    super(config);
+    var load = this.load.bind(this);
+    this.load = function (context, config, callbacks) {
+      if (context.type == 'manifest') {
+        var onSuccess = callbacks.onSuccess;
+        // copy the existing onSuccess handler to fire it later.
+
+        callbacks.onSuccess = function (response, stats, context, networkDetails) {
+          // The fourth argument here is undocumented in HLS.js but contains
+          // the response object for the manifest fetch, which gives us headers:
+
+          currentPreviewStart =
+            parseFloat(networkDetails.getResponseHeader('preview-start-seconds'));
+          // Save the start time of the preview manifest
+
+          currentPreviewVideoID =
+            networkDetails.getResponseHeader('stream-media-id');
+          // Save the video ID in case the preview was loaded with an input ID
+
+          onSuccess(response, stats, context);
+          // And fire the existing success handler.
+        };
+      }
+      load(context, config, callbacks);
+    };
+  }
 }
 
 // Specify the new loader class when setting up HLS
 const hls = new Hls({
-	pLoader: pLoader,
+  pLoader: pLoader,
 });
 ```
 
@@ -100,8 +102,11 @@ To play a clip of a live stream or recording, request a clip manifest with a dur
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/manifest/clip.m3u8?time=600s&duration=30s
 ```
 
-- `time` string start time of the clip in seconds, from the start of the live stream or recording
-- `duration` string duration of the clip in seconds, up to 60 seconds max
+
+
+* `time` string start time of the clip in seconds, from the start of the live stream or recording
+* `duration` string duration of the clip in seconds, up to 60 seconds max
+
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -113,6 +118,8 @@ An MP4 of the clip can also be generated dynamically to be saved and shared on o
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/clip.mp4?time=600s&duration=30s&filename=clip.mp4
 ```
 
-- `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
-- `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
-- `filename` string _(optional)_ a filename for the clip
+
+
+* `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
+* `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
+* `filename` string *(optional)* a filename for the clip
diff --git a/src/content/docs/stream/stream-live/simulcasting.mdx b/src/content/docs/stream/stream-live/simulcasting.mdx
index 0f88a8a94fd31ff..e5f03f9003c3432 100644
--- a/src/content/docs/stream/stream-live/simulcasting.mdx
+++ b/src/content/docs/stream/stream-live/simulcasting.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 5
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 Simulcasting lets you forward your live stream to third-party platforms such as Twitch, YouTube, Facebook, Twitter, and more. You can simulcast to up to 50 concurrent destinations from each live input. To begin simulcasting, select an input and add one or more Outputs.
@@ -28,32 +28,30 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/live_inputs/<I
 
 ```json title="Response"
 {
-	"result": {
-		"uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
-		"url": "rtmp://a.rtmp.youtube.com/live2",
-		"streamKey": "<redacted>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
+    "url": "rtmp://a.rtmp.youtube.com/live2",
+    "streamKey": "<redacted>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 ## Control when you start and stop simulcasting
 
 You can enable and disable individual live outputs with either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
-
+   <DashButton url="/?to=/:account/stream/inputs" />
 - [The API](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/update/)
 
 This allows you to:
 
-- Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
-- Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
-- Give your own users manual control over when they go live to specific simulcasting destinations.
+* Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
+* Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
+* Give your own users manual control over when they go live to specific simulcasting destinations.
 
 When a live output is disabled, video is not simulcast to the live output, even when actively streaming to the corresponding live input.
 
@@ -70,11 +68,11 @@ By default, all live outputs are enabled.
 
 ## Manage outputs
 
-| Command                                                                                                                                      | Method   | Endpoint                                                                                        |
-| -------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------- |
-| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)                                                                 | `GET`    | `accounts/:account_identifier/stream/live_inputs`                                               |
-| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/)                                                             | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier`                        |
-| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET`    | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs`                     |
-| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/)                                      | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
+| Command                                                                  | Method   | Endpoint                                                                 |
+| ------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------ |
+| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)      | `GET`    | `accounts/:account_identifier/stream/live_inputs`                        |
+| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/) | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier` |
+| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs` |
+| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/) | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
 
 If the associated live input is already retransmitting to this output when you make the `DELETE` request, that output will be disconnected within 30 seconds.
diff --git a/src/content/docs/stream/stream-live/start-stream-live.mdx b/src/content/docs/stream/stream-live/start-stream-live.mdx
index 7c32e2b8b669da8..0f114459ebb8755 100644
--- a/src/content/docs/stream/stream-live/start-stream-live.mdx
+++ b/src/content/docs/stream/stream-live/start-stream-live.mdx
@@ -22,7 +22,6 @@ After you subscribe to Stream, you can create Live Inputs in Dash or via the API
 ## Use the dashboard
 
 **Step 1:** In the Cloudflare dashboard, go to the **Live inputs** page and create a live input.
-
 <DashButton url="/?to=/:account/stream/inputs" />
 
 ![Create live input field from dashboard](~/assets/images/stream/create-live-input-from-stream-dashboard.png)
diff --git a/src/content/docs/stream/stream-live/troubleshooting.mdx b/src/content/docs/stream/stream-live/troubleshooting.mdx
index 48973fe852b3b32..d82985f4c5dfeff 100644
--- a/src/content/docs/stream/stream-live/troubleshooting.mdx
+++ b/src/content/docs/stream/stream-live/troubleshooting.mdx
@@ -7,8 +7,7 @@ sidebar:
 products:
   - stream
 ---
-
-import { Details, DashButton } from "~/components";
+import {Details, DashButton } from "~/components"
 
 In addition to following the live stream troubleshooting steps in this guide, make sure that your video settings align with [Cloudflare live stream recommendations](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If you use OBS, you can also check these [OBS-specific recommendations](/stream/examples/obs-from-scratch/#6-optional-optimize-settings).
 
@@ -24,37 +23,29 @@ If your live stream is buffering, freezing, experiencing latency issues, or havi
 
 3. Look at your **Keyframe Interval** chart.
 
-   It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform. \* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
-   - If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
+	It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform.
+			* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
+
+	  	* If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
 
-   <Details header="What is a keyframe interval?">
-   	The keyframe interval (also called GOP size) is a measurement of how often
-   	keyframes are sent to Stream. A shorter keyframe interval requires more
-   	Internet bandwidth on the broadcast side, but can reduce glass-to-glass
-   	latency. A longer keyframe requires less Internet bandwidth and can reduce
-   	buffering and freezing, but can increase glass-to-glass latency.
-   </Details>
+	<Details header="What is a keyframe interval?">
+	The keyframe interval (also called GOP size) is a measurement of how often keyframes are sent to Stream. A shorter keyframe interval requires more Internet bandwidth on the broadcast side, but can reduce glass-to-glass latency. A longer keyframe requires less Internet bandwidth and can reduce buffering and freezing, but can increase glass-to-glass latency.
+	</Details>
 
-4. Look at your **Upload-to-Duration Ratio** chart.
+3. Look at your **Upload-to-Duration Ratio** chart.
 
-   It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
-   - [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
+	It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
+    * [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
 
-   - Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
-     - If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
-     - If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
+    * Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
+	   * If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
+	   * If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
 
-   - Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
+    * Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
 
-   <Details header="What is the upload-to-duration ratio?">
-   	The upload-to-duration ratio is a measurement of how long it takes to
-   	upload a part of the stream compared to how long that part would take to
-   	play. A ratio of less than 100% means that the stream is uploading at least
-   	as fast as it would take to play, so most users should not experience
-   	buffering or freezing. A ratio of 100% or more means that your video is
-   	uploading slower than it would take to play, so it is likely that most
-   	users will experience buffering and freezing.
-   </Details>
+	<Details header="What is the upload-to-duration ratio?">
+	The upload-to-duration ratio is a measurement of how long it takes to upload a part of the stream compared to how long that part would take to play. A ratio of less than 100% means that the stream is uploading at least as fast as it would take to play, so most users should not experience buffering or freezing. A ratio of 100% or more means that your video is uploading slower than it would take to play, so it is likely that most users will experience buffering and freezing.
+	</Details>
 
 ## Encoder failing to connect or keeps disconnecting
 
@@ -64,22 +55,22 @@ If your encoder shows a connection error such as "Failed to connect to server" o
 
 - Verify that the live input is enabled. A live input that is _disabled_ will reject all incoming connections. You can enable or disable a live input from the **Live inputs** page in the Dashboard or via the API using the `enabled` property.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
-  ```bash
-  curl -X GET \
-  --header "Authorization: Bearer <API_TOKEN>" \
-  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
-  ```
+   ```bash
+   curl -X GET \
+   --header "Authorization: Bearer <API_TOKEN>" \
+   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
+   ```
 
-  If `enabled` is `false` in the response, update the live input to enable it:
+   If `enabled` is `false` in the response, update the live input to enable it:
 
-  ```bash
-  curl --request PUT \
-  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
-  --header "Authorization: Bearer <API_TOKEN>" \
-  --data '{"enabled": true}'
-  ```
+   ```bash
+   curl --request PUT \
+   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
+   --header "Authorization: Bearer <API_TOKEN>" \
+   --data '{"enabled": true}'
+   ```
 
 - If you use [Live Webhooks](/stream/stream-live/webhooks/), check for a `live_input.errored` event. The webhook payload includes an [error code](/stream/stream-live/webhooks/#error-codes) that can help you troubleshoot the specific cause.
 
@@ -93,4 +84,4 @@ If your encoder is connected and the dashboard shows a green **Connected** statu
 
 - Verify that your encoder is sending [AAC audio](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If it is not, set your encoder's settings to AAC explicitly.
 
-- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to _variable_ or _automatic_, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
+- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to *variable* or *automatic*, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
\ No newline at end of file
diff --git a/src/content/docs/stream/stream-live/webhooks.mdx b/src/content/docs/stream/stream-live/webhooks.mdx
index 2f298bf7ca81d9d..b80693318e6d6cb 100644
--- a/src/content/docs/stream/stream-live/webhooks.mdx
+++ b/src/content/docs/stream/stream-live/webhooks.mdx
@@ -8,7 +8,7 @@ products:
   - stream
 ---
 
-import { AvailableNotifications, DashButton } from "~/components";
+import { AvailableNotifications,DashButton } from "~/components"
 
 Stream Live offers webhooks to notify your service when an Input connects, disconnects, or encounters an error with Stream Live.
 
@@ -40,15 +40,15 @@ Webhooks works differently for uploaded / on-demand videos. For more information
 
 ```json title="Example webhook payload"
 {
-	"name": "Live Webhook Test",
-	"text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
-	"data": {
-		"notification_name": "Stream Live Input",
-		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-		"event_type": "live_input.disconnected",
-		"updated_at": "2022-01-13T11:43:41.855717910Z"
-	},
-	"ts": 1642074233
+  "name": "Live Webhook Test",
+  "text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
+  "data": {
+    "notification_name": "Stream Live Input",
+    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+    "event_type": "live_input.disconnected",
+    "updated_at": "2022-01-13T11:43:41.855717910Z"
+  },
+  "ts": 1642074233
 }
 ```
 
@@ -58,30 +58,30 @@ If there are issues detected with the input, the `event_type` will be `live_inpu
 
 ## Error codes
 
-- `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
-- `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
-- `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
-- `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
-- `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
+* `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
+* `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
+* `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
+* `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
+* `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
 
 ```json title="Example live_input.errored webhook payload"
 {
-	"name": "Live Webhook Test",
-	"text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
-	"data": {
-		"notification_name": "Stream Live Input",
-		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-		"event_type": "live_input.errored",
-		"updated_at": "2024-07-09T18:07:51.077371662Z",
-		"live_input_errored": {
-			"error": {
-				"code": "ERR_GOP_OUT_OF_RANGE",
-				"message": "Input GOP size or keyframe interval is out of range."
-			},
-			"video_codec": "",
-			"audio_codec": ""
-		}
-	},
-	"ts": 1720548474
+  "name": "Live Webhook Test",
+  "text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
+  "data": {
+    "notification_name": "Stream Live Input",
+    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+    "event_type": "live_input.errored",
+    "updated_at": "2024-07-09T18:07:51.077371662Z",
+    "live_input_errored": {
+      "error": {
+        "code": "ERR_GOP_OUT_OF_RANGE",
+        "message": "Input GOP size or keyframe interval is out of range."
+      },
+      "video_codec": "",
+      "audio_codec": ""
+    }
+  },
+  "ts": 1720548474,
 }
 ```
diff --git a/src/content/docs/stream/transform-videos/bindings.mdx b/src/content/docs/stream/transform-videos/bindings.mdx
index 8d5cd162e0df120..5e17fac1f2f59de 100644
--- a/src/content/docs/stream/transform-videos/bindings.mdx
+++ b/src/content/docs/stream/transform-videos/bindings.mdx
@@ -13,6 +13,7 @@ products:
 
 import { WranglerConfig, InlineBadge } from "~/components";
 
+
 A [binding](/workers/runtime-apis/bindings/) connects your [Worker](/workers/) to external resources on the Developer Platform, like [Media Transformations](/stream/transform-videos/), [R2 buckets](/r2/buckets/), or [KV namespaces](/kv/concepts/kv-namespaces/).
 
 You can bind the Media Transformations API to your Worker to transform, resize, and extract content from videos without requiring them to be accessible through a URL.
@@ -154,8 +155,8 @@ export default {
 		const frame = await env.MEDIA.input(video.body)
 			.transform({ width: 720 })
 			.output({
-				mode: "frame",
-				time: "3s",
+				mode: 'frame',
+				time: '3s',
 			})
 			.response();
 
@@ -165,10 +166,13 @@ export default {
 			prompt: "Generate a caption for this image",
 			max_tokens: 512,
 		};
-		const response = await env.AI.run("@cf/unum/uform-gen2-qwen-500m", payload);
+		const response = await env.AI.run(
+			"@cf/unum/uform-gen2-qwen-500m",
+			payload
+		);
 		return new Response(JSON.stringify(response));
-	},
-};
+	}
+}
 ```
 
 ### Extract audio
@@ -210,22 +214,28 @@ export default {
 		const audio = await env.MEDIA.input(video.body)
 			.transform()
 			.output({
-				mode: "audio",
-			})
+				mode: 'audio',
+				})
 			.response();
 
 		// Prepare and run Workers AI inference
 		const payload = {
 			audio: [...new Uint8Array(await audio.arrayBuffer())],
 		};
-		const response = await env.AI.run("@cf/openai/whisper", payload);
+		const response = await env.AI.run(
+			"@cf/openai/whisper",
+			payload
+		);
 
 		// response will have props {text, word_count, vtt, words}
-		return new Response(JSON.stringify(response, null, 2), {
-			headers: { "Content-Type": "application/json" },
-		});
-	},
-};
+		return new Response(
+			JSON.stringify(response, null, 2),
+			{
+				headers: {'Content-Type': 'application/json'}
+			}
+		);
+	}
+}
 ```
 
 ### Store transformed output in R2
diff --git a/src/content/docs/stream/transform-videos/index.mdx b/src/content/docs/stream/transform-videos/index.mdx
index 1d9dfe55c0bc0b1..cd79ead8f896bd9 100644
--- a/src/content/docs/stream/transform-videos/index.mdx
+++ b/src/content/docs/stream/transform-videos/index.mdx
@@ -7,15 +7,17 @@ sidebar:
 products:
   - stream
 ---
-
 import { DashButton } from "~/components";
 
 :::note[Media Transformations is now GA:]
 
+
 Billing for Media Transformations began on November 1st, 2025.
 
+
 :::
 
+
 You can optimize and manipulate videos stored _outside_ of Cloudflare Stream with Media Transformations. Transformed videos and images are served from one of your zones on Cloudflare.
 
 To transform a video or image, you must [enable transformations](/stream/transform-videos/#getting-started) for your zone. If your zone already has Image Transformations enabled, you can also optimize videos with Media Transformations.
diff --git a/src/content/docs/stream/uploading-videos/index.mdx b/src/content/docs/stream/uploading-videos/index.mdx
index 8d01549e5d26ccf..1e357b50c36f54c 100644
--- a/src/content/docs/stream/uploading-videos/index.mdx
+++ b/src/content/docs/stream/uploading-videos/index.mdx
@@ -12,15 +12,17 @@ Before you upload your video, review the options for uploading a video, supporte
 
 ## Upload options
 
-| Upload method                                                              | When to use                                                                             |
-| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
-| [Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)       | Upload videos from the Stream Dashboard without writing any code.                       |
-| [Upload with a link](/stream/uploading-videos/upload-via-link/)            | Upload videos using a link, such as an S3 bucket or content management system.          |
-| [Upload video file](/stream/uploading-videos/upload-video-file/)           | Upload videos stored on a computer.                                                     |
-| [Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/) | Allows end users of your website or app to upload videos directly to Cloudflare Stream. |
+| Upload method	| When to use |
+|---------------|-------------|
+|[Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)| Upload videos from the Stream Dashboard without writing any code.
+|[Upload with a link](/stream/uploading-videos/upload-via-link/)| Upload videos using a link, such as an S3 bucket or content management system.
+|[Upload video file](/stream/uploading-videos/upload-video-file/)| Upload videos stored on a computer.
+|[Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/)| Allows end users of your website or app to upload videos directly to Cloudflare Stream.
+
 
 ## Supported video formats
 
+
 :::note
 Files must be less than 30 GB, and content should be encoded and uploaded in the same frame rate it was recorded.
 :::
diff --git a/src/content/docs/stream/uploading-videos/player-api.mdx b/src/content/docs/stream/uploading-videos/player-api.mdx
index afe17603c50c36e..ba0c652f2710a62 100644
--- a/src/content/docs/stream/uploading-videos/player-api.mdx
+++ b/src/content/docs/stream/uploading-videos/player-api.mdx
@@ -22,82 +22,103 @@ Multiple attributes can be used together, added one after each other like this:
 
 ## Supported attributes
 
-- `autoplay` boolean
-  - Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
+* `autoplay` boolean
+
+  * Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
 
   :::note
   To disable video autoplay, the `autoplay` attribute needs to be removed altogether as this attribute. Setting `autoplay="false"` will not work; the video will autoplay if the attribute is there in the `<stream>` tag.
 
 In addition, some browsers now prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, see [new video policies for iOS](https://webkit.org/blog/6784/new-video-policies-for-ios/).
-:::
+  :::
+
+* `controls` boolean
+
+  * Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
+
+* `height` integer
+
+  * The height of the video's display area, in CSS pixels.
 
-- `controls` boolean
-  - Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
+* `loop` boolean
 
-- `height` integer
-  - The height of the video's display area, in CSS pixels.
+  * A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
 
-- `loop` boolean
-  - A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
+* `muted` boolean
 
-- `muted` boolean
-  - A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
+  * A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
 
-- `preload` string | null
-  - This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
+* `preload` string | null
+
+  * This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
 
   :::note
   The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
   :::
 
-- `poster` string
-  - A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
+* `poster` string
+
+  * A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
+
+* `src` string
 
-- `src` string
-  - The video id from the video you've uploaded to Cloudflare Stream should be included here.
+  * The video id from the video you've uploaded to Cloudflare Stream should be included here.
 
-- `width` integer
-  - The width of the video's display area, in CSS pixels.
+* `width` integer
+
+  * The width of the video's display area, in CSS pixels.
 
 ## Methods
 
-- `play()` Promise
-  - Start video playback.
+* `play()` Promise
+
+  * Start video playback.
+
+* `pause()` null
 
-- `pause()` null
-  - Pause video playback.
+  * Pause video playback.
 
 ## Properties
 
-- `autoplay`
-  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+* `autoplay`
 
-- `controls`
-  - Sets or returns whether the video should display controls (like play/pause etc.)
+  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
-- `currentTime`
-  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+* `controls`
 
-- `duration` readonly
-  - Returns the duration of the video in seconds.
+  * Sets or returns whether the video should display controls (like play/pause etc.)
 
-- `ended` readonly
-  - Returns whether the video has ended.
+* `currentTime`
 
-- `loop`
-  - Sets or returns whether the video should start over when it reaches the end
+  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-- `muted`
-  - Sets or returns whether the audio should be played with the video
+* `duration` readonly
 
-- `paused` readonly
-  - Returns whether the video is paused
+  * Returns the duration of the video in seconds.
 
-- `preload`
-  - Sets or returns whether the video should be preloaded upon element load.
+* `ended` readonly
 
-- `volume`
-  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+  * Returns whether the video has ended.
+
+* `loop`
+
+  * Sets or returns whether the video should start over when it reaches the end
+
+* `muted`
+
+  * Sets or returns whether the audio should be played with the video
+
+* `paused` readonly
+
+  * Returns whether the video is paused
+
+* `preload`
+
+  * Sets or returns whether the video should be preloaded upon element load.
+
+* `volume`
+
+  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -105,78 +126,102 @@ In addition, some browsers now prevent videos with audio from playing automatica
 
 Stream supports most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-- `abort`
-  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+* `abort`
+
+  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `canplay`
-  - Sent when enough data is available that the media can be played, at least for a couple of frames.
+* `canplay`
 
-- `canplaythrough`
-  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+  * Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `durationchange`
-  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+* `canplaythrough`
 
-- `ended`
-  - Sent when playback completes.
+  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-- `error`
-  - Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+* `durationchange`
 
-- `loadeddata`
-  - The first frame of the media has finished loading.
+  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-- `loadedmetadata`
-  - The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
+* `ended`
 
-- `loadstart`
-  - Sent when loading of the media begins.
+  * Sent when playback completes.
 
-- `pause`
-  - Sent when the playback state is changed to paused (paused property is true).
+* `error`
 
-- `play`
-  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+  * Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-- `playing`
-  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+* `loadeddata`
 
-- `progress`
-  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+  * The first frame of the media has finished loading.
 
-- `ratechange`
-  - Sent when the playback speed changes.
+* `loadedmetadata`
 
-- `seeked`
-  - Sent when a seek operation completes.
+   * The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
 
-- `seeking`
-  - Sent when a seek operation begins.
+* `loadstart`
 
-- `stalled`
-  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+  * Sent when loading of the media begins.
 
-- `suspend`
-  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+* `pause`
 
-- `timeupdate`
-  - The time indicated by the element's currentTime attribute has changed.
+  * Sent when the playback state is changed to paused (paused property is true).
 
-- `volumechange`
-  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+* `play`
 
-- `waiting`
-  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+
+* `playing`
+
+  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+
+* `progress`
+
+  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+
+* `ratechange`
+
+  * Sent when the playback speed changes.
+
+* `seeked`
+
+  * Sent when a seek operation completes.
+
+* `seeking`
+
+  * Sent when a seek operation begins.
+
+* `stalled`
+
+  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+
+* `suspend`
+
+  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+
+* `timeupdate`
+
+  * The time indicated by the element's currentTime attribute has changed.
+
+* `volumechange`
+
+  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+
+* `waiting`
+
+  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-- `stream-adstart`
-  - Fires when `ad-url` attribute is present and the ad begins playback
+* `stream-adstart`
+
+  * Fires when `ad-url` attribute is present and the ad begins playback
+
+* `stream-adend`
+
+  * Fires when `ad-url` attribute is present and the ad finishes playback
 
-- `stream-adend`
-  - Fires when `ad-url` attribute is present and the ad finishes playback
+* `stream-adtimeout`
 
-- `stream-adtimeout`
-  - Fires when `ad-url` attribute is present and the ad took too long to load.
+  * Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
index 44e7fb9660de859..aff3f05547c7c42 100644
--- a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
+++ b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
@@ -176,21 +176,27 @@ The tus protocol allows you to add optional parameters in the [`Upload-Metadata`
 Setting arbitrary metadata values in the `Upload-Metadata` header sets values in the [meta key in Stream API](/api/resources/stream/methods/list/).
 
 - `name`
+
   - Setting this key will set `meta.name` in the API and display the value as the name of the video in the dashboard.
 
 - `requiresignedurls`
+
   - If this key is present, the video playback for this video will be required to use signed URLs after upload.
 
 - `scheduleddeletion`
+
   - Specifies a date and time when a video will be deleted. After a video is deleted, it is no longer viewable and no longer counts towards storage for billing. The specified date and time cannot be earlier than 30 days or later than 1,096 days from the video's created timestamp.
 
 - `allowedorigins`
+
   - An array of strings listing origins allowed to display the video. This will set the [allowed origins setting](/stream/viewing-videos/securing-your-stream/#security-considerations) for the video.
 
 - `thumbnailtimestamppct`
+
   - Specify the default thumbnail [timestamp percentage](/stream/viewing-videos/displaying-thumbnails/). Note that percentage is a floating point value between 0.0 and 1.0.
 
 - `watermark`
+
   - The watermark profile UID.
 
 ## Set creator property
diff --git a/src/content/docs/stream/uploading-videos/upload-via-link.mdx b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
index 2b140c2dc1d2686..1d7071ca08fb038 100644
--- a/src/content/docs/stream/uploading-videos/upload-via-link.mdx
+++ b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
@@ -8,7 +8,11 @@ products:
   - stream
 ---
 
-import { Tabs, TabItem, LinkButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	LinkButton,
+} from "~/components"
 
 If you have videos stored in a cloud storage bucket, you can pass a HTTP link for the file, and Stream will fetch the file on your behalf.
 
@@ -104,45 +108,45 @@ You can optionally use [webhooks](/stream/manage-video-library/using-webhooks/)
 
 ```json {3,6}
 {
-	"result": {
-		"uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
-		"thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
-		"thumbnailTimestampPct": 0,
-		"readyToStream": false,
-		"status": {
-			"state": "downloading"
-		},
-		"meta": {
-			"downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
-			"name": "My First Stream Video"
-		},
-		"created": "2020-10-16T20:20:17.872170843Z",
-		"modified": "2020-10-16T20:20:17.872170843Z",
-		"size": 9032701,
-		"preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
-		"allowedOrigins": [],
-		"requireSignedURLs": false,
-		"uploaded": "2020-10-16T20:20:17.872170843Z",
-		"uploadExpiry": null,
-		"maxSizeBytes": 0,
-		"maxDurationSeconds": 0,
-		"duration": -1,
-		"input": {
-			"width": -1,
-			"height": -1
-		},
-		"playback": {
-			"hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
-			"dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
-		},
-		"watermark": null
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
+    "thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
+    "thumbnailTimestampPct": 0,
+    "readyToStream": false,
+    "status": {
+      "state": "downloading"
+    },
+    "meta": {
+      "downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
+      "name": "My First Stream Video"
+    },
+    "created": "2020-10-16T20:20:17.872170843Z",
+    "modified": "2020-10-16T20:20:17.872170843Z",
+    "size": 9032701,
+    "preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
+    "allowedOrigins": [],
+    "requireSignedURLs": false,
+    "uploaded": "2020-10-16T20:20:17.872170843Z",
+    "uploadExpiry": null,
+    "maxSizeBytes": 0,
+    "maxDurationSeconds": 0,
+    "duration": -1,
+    "input": {
+      "width": -1,
+      "height": -1
+    },
+    "playback": {
+      "hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+      "dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
+    },
+    "watermark": null
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 After the video is uploaded, you can use the video `uid` shown in the example response above to play the video using the [Stream video player](/stream/viewing-videos/using-the-stream-player/).
 
-If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
+If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
\ No newline at end of file
diff --git a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
index 1aa988048c1fe40..cc8a1491f78e4b0 100644
--- a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
+++ b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
@@ -10,8 +10,10 @@ products:
 
 :::note
 
+
 Stream thumbnails are not supported for videos with non-square pixels.
 
+
 :::
 
 ## Use Case 1: Generating a thumbnail on-the-fly
@@ -20,32 +22,29 @@ A thumbnail from your video can be generated using a special link where you spec
 
 `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270`
 
-<img
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270"
-	alt="Example of thumbnail image generated from example video"
-/>
+<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270" alt="Example of thumbnail image generated from example video" />
 
 Using the `poster` query parameter in the embed URL, you can set a thumbnail to any time in your video. If [signed URLs](/stream/viewing-videos/securing-your-stream/) are required, you must use a signed URL instead of video UIDs.
 
 ```html
 <iframe
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-	style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-	allowfullscreen="true"
+  src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+  style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+  allowfullscreen="true"
 ></iframe>
 ```
 
 Supported URL attributes are:
 
-- **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
-- **`height`** (default `640`)
-- **`width`** (default `640`)
-- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  - **`crop`** cut parts of the video that doesn't fit in the given size
-  - **`clip`** preserve the entire frame and decrease the size of the image within given size
-  - **`scale`** distort the image to fit the given size
-  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+* **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
+* **`height`** (default `640`)
+* **`width`** (default `640`)
+* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  * **`crop`** cut parts of the video that doesn't fit in the given size
+  * **`clip`** preserve the entire frame and decrease the size of the image within given size
+  * **`scale`** distort the image to fit the given size
+  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
 
 ## Use Case 2: Set the default thumbnail timestamp using the API
 
@@ -68,20 +67,17 @@ Stream supports animated GIFs as thumbnails. Viewing animated thumbnails does no
 
 ` https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s`
 
-<img
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s"
-	alt="Animated gif example, generated on-demand from Cloudflare Stream"
-/>
+<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s" alt="Animated gif example, generated on-demand from Cloudflare Stream" />
 
 Supported URL attributes for animated thumbnails are:
 
-- **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
-- **`height`** (default `640`)
-- **`width`** (default `640`)
-- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  - **`crop`** cut parts of the video that doesn't fit in the given size
-  - **`clip`** preserve the entire frame and decrease the size of the image within given size
-  - **`scale`** distort the image to fit the given size
-  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
-- **`duration`** (default `5s`)
-- **`fps`** (default `8`)
+* **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
+* **`height`** (default `640`)
+* **`width`** (default `640`)
+* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  * **`crop`** cut parts of the video that doesn't fit in the given size
+  * **`clip`** preserve the entire frame and decrease the size of the image within given size
+  * **`scale`** distort the image to fit the given size
+  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+* **`duration`** (default `5s`)
+* **`fps`** (default `8`)
diff --git a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
index 979b5f8d99e2f35..0ae5a7967717599 100644
--- a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
+++ b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
@@ -15,103 +15,134 @@ To use this SDK, add an additional `<script>` tag to your website:
 ```html
 <!-- You can use styles and CSS on this iframe element where the video player will appear -->
 <iframe
-	src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
-	style="border: none"
-	height="720"
-	width="1280"
-	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-	allowfullscreen="true"
-	id="stream-player"
+  src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
+  style="border: none"
+  height="720"
+  width="1280"
+  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+  allowfullscreen="true"
+  id="stream-player"
 ></iframe>
 
 <script src="https://embed.cloudflarestream.com/embed/sdk.latest.js"></script>
 
 <!-- Your JavaScript code below-->
 <script>
-	const player = Stream(document.getElementById("stream-player"));
-	player.addEventListener("play", () => {
-		console.log("playing!");
-	});
-	player.play().catch(() => {
-		console.log("playback failed, muting to try again");
-		player.muted = true;
-		player.play();
-	});
+  const player = Stream(document.getElementById('stream-player'));
+  player.addEventListener('play', () => {
+    console.log('playing!');
+  });
+  player.play().catch(() => {
+    console.log('playback failed, muting to try again');
+    player.muted = true;
+    player.play();
+  });
 </script>
 ```
 
 ## Methods
 
-- `play()` Promise
-  - Start video playback.
 
-- `pause()` null
-  - Pause video playback.
+
+* `play()` Promise
+
+  * Start video playback.
+
+* `pause()` null
+
+  * Pause video playback.
+
+
 
 ## Properties
 
-- `autoplay` boolean
-  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+
+
+* `autoplay` boolean
+
+  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
 :::note
 
+
 Some browsers prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, review the [iOS video policies](https://webkit.org/blog/6784/new-video-policies-for-ios/).
 
+
 :::
 
-- `buffered` TimeRanges readonly
-  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+* `buffered` TimeRanges readonly
+
+  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-- `controls` boolean
-  - Sets or returns whether the video should display controls (like play/pause etc.)
+* `controls` boolean
 
-- `currentTime` integer
-  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+  * Sets or returns whether the video should display controls (like play/pause etc.)
 
-- `defaultTextTrack`
-  - Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
+* `currentTime` integer
+
+  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+
+* `defaultTextTrack`
+
+  * Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
 
 :::note
 
-This will _only_ work once during initialization. Beyond that point the user has full control over their text track settings.
+
+This will *only* work once during initialization. Beyond that point the user has full control over their text track settings.
+
 
 :::
 
-- `duration` integer readonly
-  - Returns the duration of the video in seconds.
+* `duration` integer readonly
+
+  * Returns the duration of the video in seconds.
+
+* `ended` boolean readonly
+
+  * Returns whether the video has ended.
+
+* `letterboxColor` string
+
+  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
+
+* `loop` boolean
+
+  * Sets or returns whether the video should start over when it reaches the end
 
-- `ended` boolean readonly
-  - Returns whether the video has ended.
+* `muted` boolean
 
-- `letterboxColor` string
-  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
+  * Sets or returns whether the audio should be played with the video
 
-- `loop` boolean
-  - Sets or returns whether the video should start over when it reaches the end
+* `paused` boolean readonly
 
-- `muted` boolean
-  - Sets or returns whether the audio should be played with the video
+  * Returns whether the video is paused
 
-- `paused` boolean readonly
-  - Returns whether the video is paused
+* `played` TimeRanges readonly
 
-- `played` TimeRanges readonly
-  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-- `preload` boolean
-  - Sets or returns whether the video should be preloaded upon element load.
+* `preload` boolean
+
+  * Sets or returns whether the video should be preloaded upon element load.
 
 :::note
 
+
 The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
 
+
 :::
 
-- `primaryColor` string
-  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
+* `primaryColor` string
+
+  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
+
+* `volume` float
+
+  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+
 
-- `volume` float
-  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -119,78 +150,109 @@ The `<video>` element does not force the browser to follow the value of this att
 
 We support most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-- `abort`
-  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `canplay`
-  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `canplaythrough`
-  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+* `abort`
 
-- `durationchange`
-  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `ended`
-  - Sent when playback completes.
+* `canplay`
 
-- `error`
-  - Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+  * Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `loadeddata`
-  - The first frame of the media has finished loading.
+* `canplaythrough`
 
-- `loadedmetadata`
-  - The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
+  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-- `loadstart`
-  - Sent when loading of the media begins.
+* `durationchange`
 
-- `pause`
-  - Sent when the playback state is changed to paused (paused property is true).
+  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-- `play`
-  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+* `ended`
 
-- `playing`
-  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+  * Sent when playback completes.
 
-- `progress`
-  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+* `error`
 
-- `ratechange`
-  - Sent when the playback speed changes.
+  * Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-- `seeked`
-  - Sent when a seek operation completes.
+* `loadeddata`
 
-- `seeking`
-  - Sent when a seek operation begins.
+  * The first frame of the media has finished loading.
 
-- `stalled`
-  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+* `loadedmetadata`
 
-- `suspend`
-  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+  * The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
 
-- `timeupdate`
-  - The time indicated by the element's currentTime attribute has changed.
+* `loadstart`
+
+  * Sent when loading of the media begins.
+
+* `pause`
+
+  * Sent when the playback state is changed to paused (paused property is true).
+
+* `play`
+
+  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+
+* `playing`
+
+  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+
+* `progress`
+
+  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+
+* `ratechange`
+
+  * Sent when the playback speed changes.
+
+* `seeked`
+
+  * Sent when a seek operation completes.
+
+* `seeking`
+
+  * Sent when a seek operation begins.
+
+* `stalled`
+
+  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+
+* `suspend`
+
+  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+
+* `timeupdate`
+
+  * The time indicated by the element's currentTime attribute has changed.
+
+* `volumechange`
+
+  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+
+* `waiting`
+
+  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
-- `volumechange`
-  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
-- `waiting`
-  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard Events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-- `stream-adstart`
-  - Fires when `ad-url` attribute is present and the ad begins playback
 
-- `stream-adend`
-  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-- `stream-adtimeout`
-  - Fires when `ad-url` attribute is present and the ad took too long to load.
+* `stream-adstart`
+
+  * Fires when `ad-url` attribute is present and the ad begins playback
+
+* `stream-adend`
+
+  * Fires when `ad-url` attribute is present and the ad finishes playback
+
+* `stream-adtimeout`
+
+  * Fires when `ad-url` attribute is present and the ad took too long to load.
+
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
index e65a1289cbbf95e..4d5dded596a44eb 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
@@ -14,7 +14,7 @@ The purpose of Deprecated API content is to communicate that Cloudflare no longe
 
 instructional, straightforward
 
-## content_type
+## content\_type
 
 `reference`
 
@@ -24,7 +24,7 @@ instructional, straightforward
 
 **Deprecated endpoint name**: Must match what existed in the non-deprecated [Endpoint](/style-guide/api-content-strategy/api-content-types/endpoints/).
 
-**Context**: Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
+**Context**:  Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
 
 **Replacement**: A description of and/or link to the alternative endpoint OR an explanation as to why Cloudflare is removing the capability of that endpoint.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
index 6529edfc70b1ed6..f73e8c33466bbfe 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
@@ -18,19 +18,21 @@ An endpoint is used to make HTTPS requests, and the `GET`, `POST`, `PUT`, `PATCH
 
 :::note
 
+
 The required components apply to newly created endpoints. Existing endpoints will **not** be modified.
 
+
 :::
 
 **Title**: Title of the endpoint using sentence casing (first word capitalized). The titles do not use punctuation marks at the end of the title. Simple cases usually take one of the following forms:
 
 Endpoints that act on/return a single item: verb + indefinite article + singular resource name.
 
-- Example: Get a list item
+* Example: Get a list item
 
 Endpoints that act on/return a collection of items: verb + plural resource name.
 
-- Example: Get list items
+* Example: Get list items
 
 **Description**: Describes what the endpoint does or how it should be used. Use punctuation at the end of the description.
 
@@ -52,11 +54,11 @@ When writing the titles and descriptions, keep our voice and tone in mind. Be co
 
 Below are some examples of endpoint titles and descriptions for reference:
 
-- **Get domain**: Fetches a single domain.
-- **List workers**: Fetches a list of uploaded workers.
-- **List pools**: Lists configured pools.
-- **Create waiting room**: Creates a new waiting room.
-- **Update health check**: Updates configured health checks.
+* **Get domain**: Fetches a single domain.
+* **List workers**: Fetches a list of uploaded workers.
+* **List pools**: Lists configured pools.
+* **Create waiting room**: Creates a new waiting room.
+* **Update health check**: Updates configured health checks.
 
 ## Example
 
@@ -68,4 +70,4 @@ Below are some examples of endpoint titles and descriptions for reference:
 
 **Method**: `GET`
 
-**Endpoint**: user/audit_logs
+**Endpoint**: user/audit\_logs
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
index 59e3387e3c346d0..5b998bffe2e51f0 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
index aebb7c2e49d8230..a31e895ce8f45c1 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
@@ -46,7 +46,7 @@ Below are some examples of parameter descriptions for reference:
 
 **version**: The Cloudflare One Client version.
 
-**per_page**: Sets the maximum number of requested results.
+**per\_page**: Sets the maximum number of requested results.
 
 **enabled**: Enables or disable a load balancer.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
index c24e2857250568e..26a17b8a4f34fc5 100644
--- a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
@@ -21,9 +21,9 @@ To automatically incorporate our conventions into your examples, use:
 
 Use long parameter names for clarity:
 
-- `--header` (instead of `-H`)
-- `--request` (when needed, instead of `-X`)
-- `--data` (instead of `-d`)
+* `--header` (instead of `-H`)
+* `--request` (when needed, instead of `-X`)
+* `--data` (instead of `-d`)
 
 You do not need to use the `--url` parameter since it is the main cURL parameter. Also, the URL does not need to be enclosed in double quotes (`""`), except if it contains a `?` character (that is, when it includes a query string).
 
@@ -45,9 +45,9 @@ If you must suggest the use of this tool, you can add a link to the [Make API ca
 
 ### Preliminary notes
 
-- Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
-- Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
-- Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
+* Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
+* Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
+* Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
 
 The same placeholder name should correspond to the same value – use different placeholder names for different ID values. You can use the same request placeholders in the response, if they should match the values in the request.
 
@@ -149,7 +149,7 @@ Enclose the JSON payload ( the `--data` command-line argument) in single quotes
 
 The recommended way of escaping a single quote inside the body is the following (assuming the user will run the command in a bash-like terminal):
 
-- Replace the single quote `'` with `'\''`
+* Replace the single quote `'` with `'\''`
 
 Which means "close string, add escaped single quote, begin string again".
 
@@ -203,28 +203,28 @@ A response starts either with an object (`{ ... }`) or a list (`[ ... ]`). The i
 (}|])
 ```
 
-- If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
-- Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
+* If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
+* Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
 
 ### Full response example
 
 ```json
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"paused": false,
-		"description": "do not challenge login from office",
-		"action": "allow",
-		"priority": null,
-		"filter": {
-			"id": "<FILTER_ID>",
-			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-			"paused": false,
-			"description": "Login from office"
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "paused": false,
+    "description": "do not challenge login from office",
+    "action": "allow",
+    "priority": null,
+    "filter": {
+      "id": "<FILTER_ID>",
+      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+      "paused": false,
+      "description": "Login from office"
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/style-guide/components/anchor-heading.mdx b/src/content/docs/style-guide/components/anchor-heading.mdx
index 3a3195eb29ef0a3..22d6bd5d8b60e19 100644
--- a/src/content/docs/style-guide/components/anchor-heading.mdx
+++ b/src/content/docs/style-guide/components/anchor-heading.mdx
@@ -17,11 +17,7 @@ The `AnchorHeading` component defines headings. Specifically, `AnchorHeading` pe
 ```mdx live
 import { AnchorHeading } from "~/components";
 
-<AnchorHeading
-	title="How to use AnchorHeading"
-	slug="use-anchorheading"
-	depth={2}
-/>
+<AnchorHeading title="How to use AnchorHeading" slug="use-anchorheading" depth={2} />
 ```
 
 Markdown files (including partials) have this behavior by default, applied via rehype plugins. Therefore, the `AnchorHeading` component is usually only required when writing headings yourself inside components, or when working on non-markdown files.
@@ -29,8 +25,7 @@ Markdown files (including partials) have this behavior by default, applied via r
 To override the ID given to a heading within Markdown, add an MDX comment at the end of the line:
 
 ```mdx live
-## foo {/* bar */}
-
+## foo {/*bar*/}
 {/* HTML: <h2 id="bar">foo</h2> */}
 ```
 
@@ -38,4 +33,4 @@ To override the ID given to a heading within Markdown, add an MDX comment at the
 
 The `AnchorHeading` component emulates the behavior of the [`rehype-slug`](https://github.com/rehypejs/rehype-slug) and the [`rehype-autolink-headings`](https://github.com/rehypejs/rehype-autolink-headings). It adds an `id` based on the output of [`github-slugger`](https://github.com/Flet/github-slugger/) to the heading, as well as adding a button to copy a link to that particular heading.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/available-notifications.mdx b/src/content/docs/style-guide/components/available-notifications.mdx
index ef0ad606272bc27..52d9d0e9f2ec6d7 100644
--- a/src/content/docs/style-guide/components/available-notifications.mdx
+++ b/src/content/docs/style-guide/components/available-notifications.mdx
@@ -14,19 +14,14 @@ import { AvailableNotifications } from "~/components";
 
 <AvailableNotifications product="Traffic Monitoring" />
 <AvailableNotifications
-	product="dns"
-	notificationFilter="Secondary DNS all Primaries Failing"
+    product="dns"
+    notificationFilter="Secondary DNS all Primaries Failing"
 />
 ```
 
 ## Notifications
 
-import { Code } from "~/components";
-import glossary from "~/content/notifications/index.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/notifications/index.yaml?raw"
 
-<Code
-	title="/src/content/notifications/index.yaml"
-	code={glossary}
-	lang="yaml"
-	wrap={true}
-/>
+<Code title="/src/content/notifications/index.yaml" code={glossary} lang="yaml" wrap={true} />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/description.mdx b/src/content/docs/style-guide/components/description.mdx
index 75456e07bf8c711..4d91bb6f10f8f27 100644
--- a/src/content/docs/style-guide/components/description.mdx
+++ b/src/content/docs/style-guide/components/description.mdx
@@ -8,7 +8,9 @@ products:
 ---
 
 ```mdx live
-import { Description } from "~/components";
+import { Description } from "~/components"
 
-<Description>Hello, world!</Description>
-```
+<Description>
+    Hello, world!
+</Description>
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/example.mdx b/src/content/docs/style-guide/components/example.mdx
index 2d3de76617e19e9..eb0ba2069a80284 100644
--- a/src/content/docs/style-guide/components/example.mdx
+++ b/src/content/docs/style-guide/components/example.mdx
@@ -10,13 +10,17 @@ products:
 Use the `<Example>` component to add a box around some content. This can be useful when you want to demonstrate or showcase something without it being confused by the surrounding text.
 
 ```mdx live
-import { Example } from "~/components";
+import { Example } from "~/components"
 
-<Example>Hello, world!</Example>
+<Example>
+    Hello, world!
+</Example>
 
-{/_
-`title` is an optional string which customizes the title of your example card
-_/}
+{/*
+    `title` is an optional string which customizes the title of your example card
+*/}
 
-<Example title="Hello world">Hello, world!</Example>
-```
+<Example title="Hello world">
+    Hello, world!
+</Example>
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/feature-table.mdx b/src/content/docs/style-guide/components/feature-table.mdx
index c839be1febca17e..7018dd906b70056 100644
--- a/src/content/docs/style-guide/components/feature-table.mdx
+++ b/src/content/docs/style-guide/components/feature-table.mdx
@@ -14,7 +14,7 @@ If the feature information includes an `Availability` row and you would like to
 This component pulls information from the `index.json` file in `src/content/plans/`.
 
 ```mdx live
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 <FeatureTable id="analytics.logpush" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/feature.mdx b/src/content/docs/style-guide/components/feature.mdx
index 1b795ccb977fbf1..ce6073fbff74c41 100644
--- a/src/content/docs/style-guide/components/feature.mdx
+++ b/src/content/docs/style-guide/components/feature.mdx
@@ -12,15 +12,15 @@ The `<Feature>` component lists features available in the product and provides a
 The header parameter supplies the feature name and the href parameter supplies the link to the feature. Text wrapped in the component supplies the description.
 
 ```mdx
-import { Feature } from "~/components";
+import { Feature } from "~/components"
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-	Hello, world!
+   Hello, world!
 </Feature>
 ```
 
-import { Feature } from "~/components";
+import { Feature } from "~/components"
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-	Hello, world!
+   Hello, world!
 </Feature>
diff --git a/src/content/docs/style-guide/components/glossary-definition.mdx b/src/content/docs/style-guide/components/glossary-definition.mdx
index 7a95c0d7c2a7584..379a96198932f4f 100644
--- a/src/content/docs/style-guide/components/glossary-definition.mdx
+++ b/src/content/docs/style-guide/components/glossary-definition.mdx
@@ -12,18 +12,14 @@ Use the this component to add extra information to an existing glossary entry. `
 ## Component
 
 ```mdx live
-import { GlossaryDefinition } from "~/components";
+import { GlossaryDefinition } from "~/components"
 
 <GlossaryDefinition term="example" prepend="The definition for example is: " />
 ```
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
 
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/glossary-tooltip.mdx b/src/content/docs/style-guide/components/glossary-tooltip.mdx
index 8f0e06da3c09d3d..0efadd82370ed12 100644
--- a/src/content/docs/style-guide/components/glossary-tooltip.mdx
+++ b/src/content/docs/style-guide/components/glossary-tooltip.mdx
@@ -22,11 +22,7 @@ import { GlossaryTooltip } from "~/components"
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
-
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
+
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/glossary.mdx b/src/content/docs/style-guide/components/glossary.mdx
index df05ad6c06dab82..1bf06744eadfba7 100644
--- a/src/content/docs/style-guide/components/glossary.mdx
+++ b/src/content/docs/style-guide/components/glossary.mdx
@@ -14,18 +14,14 @@ Create the glossary entries in a file dedicated to your product. These YAML file
 ## Component
 
 ```mdx live
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 <Glossary />
 ```
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
 
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/inline-badge.mdx b/src/content/docs/style-guide/components/inline-badge.mdx
index 6e49dc901618e2c..b0c325af0bf4068 100644
--- a/src/content/docs/style-guide/components/inline-badge.mdx
+++ b/src/content/docs/style-guide/components/inline-badge.mdx
@@ -12,18 +12,17 @@ products:
 Our current recommendation is to avoid inline badges, since they may hurt readability.
 
 Guidelines:
-
 - Mention beta/alpha/early access in the feature's main documentation page (use the [`<Badge>`](/style-guide/components/badges/) component for this purpose).
 - If an additional reference is needed in the middle of the text, use "(beta)", with no special formatting, after the feature name.
 - For instructions related to the feature (such as instructions on turning the feature on or off), you may mention again it's in beta, and also include "(beta)" in the side nav.
-  :::
+:::
 
 ## Component
 
 To adopt this styling in a React component, apply the `sl-badge` class to a `span` element.
 
 ```mdx live
-import { InlineBadge } from "~/components";
+import { InlineBadge } from '~/components';
 
 ### Alpha <InlineBadge preset="alpha" />
 
@@ -45,24 +44,24 @@ Either `preset` or `text` and `variant` must be specified.
 ### Presets
 
 - `alpha`
-  - **Text**: `Alpha`
-  - **Variant** `success`
+    - **Text**: `Alpha`
+    - **Variant** `success`
 
 - `beta`
-  - **Text**: `Beta`
-  - **Variant** `caution`
+    - **Text**: `Beta`
+    - **Variant** `caution`
 
 - `deprecated`
-  - **Text**: `Deprecated`
-  - **Variant** `danger`
+    - **Text**: `Deprecated`
+    - **Variant** `danger`
 
 - `early-access`
-  - **Text**: `Early Access`
-  - **Variant** `note`
+    - **Text**: `Early Access`
+    - **Variant** `note`
 
 - `legacy`
-  - **Text**: `Legacy`
-  - **Variant** `danger`
+    - **Text**: `Legacy`
+    - **Variant** `danger`
 
 ### Text
 
@@ -71,16 +70,16 @@ Any string.
 ### Variant
 
 - `note`
-  - **Color**: Blue
+    - **Color**: Blue
 
 - `tip`
-  - **Color**: Purple
+    - **Color**: Purple
 
 - `danger`
-  - **Color**: Red
+    - **Color**: Red
 
 - `caution`
-  - **Color**: Orange
+    - **Color**: Orange
 
 - `success`
-  - **Color**: Green
+    - **Color**: Green
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/link-cards.mdx b/src/content/docs/style-guide/components/link-cards.mdx
index 0adc8e6059e72d6..da6aaeafc9831a0 100644
--- a/src/content/docs/style-guide/components/link-cards.mdx
+++ b/src/content/docs/style-guide/components/link-cards.mdx
@@ -8,21 +8,21 @@ products:
 ---
 
 ```mdx live wrap
-import { CardGrid, LinkCard } from "~/components";
+import { CardGrid, LinkCard } from "~/components"
 
 <LinkCard
-	title="foo"
-	description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-	href="/style-guide/components/link-cards/"
+    title="foo"
+    description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+    href="/style-guide/components/link-cards/"
 />
 
 <CardGrid>
-	{[...Array(4).keys()].map(() => (
-		<LinkCard
-			title="foo"
-			description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-			href="/style-guide/components/link-cards/"
-		/>
-	))}
+{[...Array(4).keys()].map(() => (
+    <LinkCard
+        title="foo"
+        description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+        href="/style-guide/components/link-cards/"
+    />
+))}
 </CardGrid>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/list-tutorials.mdx b/src/content/docs/style-guide/components/list-tutorials.mdx
index c67b80ab5057fa1..c225a6b23e4a78c 100644
--- a/src/content/docs/style-guide/components/list-tutorials.mdx
+++ b/src/content/docs/style-guide/components/list-tutorials.mdx
@@ -15,4 +15,4 @@ import { ListTutorials } from "~/components";
 
 ## Associated content types
 
-- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
+- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/package-managers.mdx b/src/content/docs/style-guide/components/package-managers.mdx
index 4c5f8298b9152d9..7b9c3137bd4b3b3 100644
--- a/src/content/docs/style-guide/components/package-managers.mdx
+++ b/src/content/docs/style-guide/components/package-managers.mdx
@@ -10,7 +10,7 @@ products:
 This component is provided by the [`starlight-package-managers` package.](https://github.com/HiDeoo/starlight-package-managers)
 
 ```mdx live
-import { PackageManagers } from "~/components";
+import { PackageManagers } from "~/components"
 
 <PackageManagers pkg="wrangler" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/pages-build-preset.mdx b/src/content/docs/style-guide/components/pages-build-preset.mdx
index 3480c8339307db2..976dc1433f725e5 100644
--- a/src/content/docs/style-guide/components/pages-build-preset.mdx
+++ b/src/content/docs/style-guide/components/pages-build-preset.mdx
@@ -8,8 +8,8 @@ products:
 ---
 
 ```mdx live
-import { PagesBuildPreset } from "~/components";
+import { PagesBuildPreset } from "~/components"
 
 <PagesBuildPreset framework="gatsby" />
 <PagesBuildPreset framework="next-js" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/plan.mdx b/src/content/docs/style-guide/components/plan.mdx
index 1b1457fa37ceb98..07b591b1274a686 100644
--- a/src/content/docs/style-guide/components/plan.mdx
+++ b/src/content/docs/style-guide/components/plan.mdx
@@ -14,8 +14,9 @@ To specify a special feature use `<Plan id="<FIRST_PRODUCT>.<SECOND-PRODUCT>.pro
 
 Refer to the examples below for more information.
 
+
 ```mdx live
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
 <Plan type="all" />
 <Plan type="paid" />
@@ -26,4 +27,4 @@ import { Plan } from "~/components";
 <Plan type="workers-all" />
 <Plan type="workers-paid" />
 <Plan id="web3.ethereum.properties.availability.summary" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/product-availability-text.mdx b/src/content/docs/style-guide/components/product-availability-text.mdx
index 77e2bca0cf78b1d..83689f8bbba4207 100644
--- a/src/content/docs/style-guide/components/product-availability-text.mdx
+++ b/src/content/docs/style-guide/components/product-availability-text.mdx
@@ -19,10 +19,10 @@ Cloud Connector <ProductAvailabilityText product="cloud-connector" /> allows you
 
 ## Props
 
-| Prop          | Type     | Required | Default  | Description                                                                                                |
-| ------------- | -------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------- |
-| `product`     | `string` | Yes      | —        | Product slug matching a file in `src/content/directory/`.                                                  |
-| `parentheses` | `string` | No       | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `product` | `string` | Yes | — | Product slug matching a file in `src/content/directory/`. |
+| `parentheses` | `string` | No | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
 
 ## Behavior
 
diff --git a/src/content/docs/style-guide/components/product-features.mdx b/src/content/docs/style-guide/components/product-features.mdx
index bea56b72ab74c5e..199e0ded2498a76 100644
--- a/src/content/docs/style-guide/components/product-features.mdx
+++ b/src/content/docs/style-guide/components/product-features.mdx
@@ -10,7 +10,6 @@ products:
 Use when you need to list all available features within a product grouping inside of the `index.json` file in `src/content/plans/`. For the id property, specify the product object you want to use.
 
 ```mdx live
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
-<ProductFeatures id="dns" />
-```
+<ProductFeatures id="dns" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/related-product.mdx b/src/content/docs/style-guide/components/related-product.mdx
index 99c45329075a2a1..8de8d8c11cdca07 100644
--- a/src/content/docs/style-guide/components/related-product.mdx
+++ b/src/content/docs/style-guide/components/related-product.mdx
@@ -17,11 +17,10 @@ Use in Overview pages.
 import { RelatedProduct } from "~/components";
 
 <RelatedProduct header="R2" href="/r2/" product="r2">
-	Store large amounts of unstructured data without the costly egress bandwidth
-	fees associated with typical cloud storage services.
+    Store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.
 </RelatedProduct>
 
 <RelatedProduct header="Images" href="/images/" product="images">
-	A suite of products tailored to your image-processing needs.
+    A suite of products tailored to your image-processing needs.
 </RelatedProduct>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/rule-id.mdx b/src/content/docs/style-guide/components/rule-id.mdx
index f5b213de131b2bc..d2a33c41ef0ebd7 100644
--- a/src/content/docs/style-guide/components/rule-id.mdx
+++ b/src/content/docs/style-guide/components/rule-id.mdx
@@ -8,7 +8,7 @@ products:
 ---
 
 ```mdx live
-import { RuleID } from "~/components";
+import { RuleID } from "~/components"
 
 <RuleID id="abcdefghijklmnopqrstuvwxyz" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/steps.mdx b/src/content/docs/style-guide/components/steps.mdx
index a8ad45e2b122573..26b09c984dee440 100644
--- a/src/content/docs/style-guide/components/steps.mdx
+++ b/src/content/docs/style-guide/components/steps.mdx
@@ -15,4 +15,4 @@ import { Steps } from "~/components"
 2. Wrap your numbered list in the `Steps` components
 3. Done!
 </Steps>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
index 7208cf19466a58c..824d45bb57c3001 100644
--- a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
+++ b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
@@ -40,7 +40,7 @@ An optional object containing `base` (`string`) and `subtract` (`string[]`) prop
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
 	}}
 />
 
@@ -51,7 +51,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
 	}}
 />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/type-highlighting.mdx b/src/content/docs/style-guide/components/type-highlighting.mdx
index 26f7c06002aa2bb..a95852acfc7dc55 100644
--- a/src/content/docs/style-guide/components/type-highlighting.mdx
+++ b/src/content/docs/style-guide/components/type-highlighting.mdx
@@ -32,4 +32,4 @@ import { Type, MetaInfo } from "~/components";
   - The name of your service.
 - `local` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
   - If the service should run locally or not.
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/usage.mdx b/src/content/docs/style-guide/components/usage.mdx
index b1548e52b571c45..337c49995287617 100644
--- a/src/content/docs/style-guide/components/usage.mdx
+++ b/src/content/docs/style-guide/components/usage.mdx
@@ -11,4 +11,4 @@ import { ComponentsUsage } from "~/components";
 
 This page contains a breakdown of each component and the pages where they are used.
 
-<ComponentsUsage />
+<ComponentsUsage />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/wrangler-namespace.mdx b/src/content/docs/style-guide/components/wrangler-namespace.mdx
index 6ebac49e56a3019..fab2bbf305de528 100644
--- a/src/content/docs/style-guide/components/wrangler-namespace.mdx
+++ b/src/content/docs/style-guide/components/wrangler-namespace.mdx
@@ -32,4 +32,4 @@ import { WranglerNamespace } from "~/components";
 - `namespace` <Type text="string" /> <MetaInfo text="required" />
   - The namespace to pull the related commands from (`d1`, `hyperdrive`).
 - `headingLevel` <Type text="boolean" /> <MetaInfo text="(default: 2) optional" />
-  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
+  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/youtube.mdx b/src/content/docs/style-guide/components/youtube.mdx
index b7dd62471b86ad2..8b24f0d71780445 100644
--- a/src/content/docs/style-guide/components/youtube.mdx
+++ b/src/content/docs/style-guide/components/youtube.mdx
@@ -7,12 +7,12 @@ products:
   - style-guide
 ---
 
-import { YouTube } from "~/components";
+import { YouTube } from "~/components"
 
 <YouTube id="XHvmX3FhTwU" />
 
 ```mdx
-import { YouTube } from "~/components";
+import { YouTube } from "~/components"
 
 <YouTube id="XHvmX3FhTwU" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/contributions.mdx b/src/content/docs/style-guide/contributions.mdx
index 26f56188f64db34..5921a50b9de6eba 100644
--- a/src/content/docs/style-guide/contributions.mdx
+++ b/src/content/docs/style-guide/contributions.mdx
@@ -2,27 +2,23 @@
 title: Contributions
 description: Learn how to contribute to the Cloudflare Docs.
 sidebar:
-  order: 1
+    order: 1
 products:
   - style-guide
 ---
-
 import { Details } from "~/components";
 
 The [Cloudflare Docs](https://developers.cloudflare.com/) are open source and hosted on the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs) on GitHub. This means that anyone, including those who are not part of the Cloudflare organization, can contribute to them. We welcome all suggestions that help keep our docs high quality and up to date.
 
 To contribute to our docs, you will need to [create an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) (if you do not have one already) and log in. Then you have three options:
-
-- [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
-- [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
-- [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
+* [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
+* [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
+* [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
 
 In addition to using the [Cloudflare Style Guide](/style-guide/) for guidance on grammar and style, we recommend browsing our [components](/style-guide/components/) to add additional formatting such as buttons, tabs, and collapsible sections.
 
 ## Create a GitHub issue
-
 To create a GitHub issue:
-
 1. [Log in to GitHub](https://github.com/login) and go to the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs).
 2. Select **Issues** and then **New issue**.
 3. Select the issue type, fill out the form, and select **Create**.
@@ -30,63 +26,53 @@ To create a GitHub issue:
 [Learn more about creating GitHub issues.](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue)
 
 ## Quick edit
-
 To quickly create a pull request using the edit button:
-
 1. [Log in to GitHub](https://github.com/login).
 2. Go to the page you want to edit in the [Cloudflare Docs](https://developers.cloudflare.com/)
 3. Select <Details header="**Edit** or **Edit page**">Every page in the Cloudflare Docs (including this one) has an **Edit** button on the right sidebar and an **Edit page** button on the very bottom of the page.
-   ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
-   The page's Markdown opens.
-   :::note
-   The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
-   :::
+ ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
+The page's Markdown opens.
+	:::note
+	The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
+	:::
 4. Make your edits and select **Commit changes**.
 5. In the form, update the **Commit message** with the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 6. Update the **Extended description** with more details about what you changed and why. The more details, the better.
 7. Select **Propose changes** > **Create pull request** > **Create pull request** again.
 
 ## Full development
-
 To edit and create a pull request with the [full development workflow](https://docs.github.com/en/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace):
-
 1. [Log in to GitHub](https://github.com/login) and [fork the cloudflare-docs repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
 2. If you are editing in your web browser (with [Codespaces](https://docs.github.com/en/codespaces)), move on to step 3.
-   <br />
-   If you are editing on your local machine (with [Visual Studio
-   Code](https://code.visualstudio.com/)): * (Required) Install
-   [Node.js](https://nodejs.org/en) (version 24 or later). * (Recommended, but
-   not required) Install [Volta](https://volta.sh/) for easier package
-   management. * (Required) [Clone the fork to your local
-   machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
+<br/>If you are editing on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)):
+	* (Required) Install [Node.js](https://nodejs.org/en) (version 24 or later).
+	* (Recommended, but not required) Install [Volta](https://volta.sh/) for easier package management.
+	* (Required) [Clone the fork to your local machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
 3. Create a branch from your fork (or from your clone).
-4. Make your edits.
-   :::note[Preview your edits]
-   To preview your edits, you need to install `pnpm`.
-
-```bash
-pnpm install
-```
-
+3. Make your edits.
+:::note[Preview your edits]
+To preview your edits, you need to install `pnpm`.
+ ```bash
+ pnpm install
+ ```
 Then, run `pnpm run dev`.
-
-```bash
-pnpm run dev
-```
-
+ ```bash
+ pnpm run dev
+ ```
 A link will appear in the terminal, `https://localhost:1111/`, where you can preview your edits. This link automatically updates with any new edits you make.
-::: 5. Commit your changes. 6. Push your commits to your branch and then back to your fork. 7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
+:::
+5. Commit your changes.
+6. Push your commits to your branch and then back to your fork.
+7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 
 ## After you create an issue or PR
-
 After you create an issue or PR, a member of the Cloudflare organization will review your suggestion. Here is what to expect:
-
-- A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
-- If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
-- If your changes are approved:
-  - For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
-  - For GitHub PRs, the Cloudflare member will merge your PR.
-- If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
+* A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
+* If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
+* If your changes are approved:
+	* For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
+	* For GitHub PRs, the Cloudflare member will merge your PR.
+* If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
 
 Thank you for contributing to our open-source ecosystem and being a part of the Cloudflare community.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
index 38e5c2fa935864f..899c473a810e03e 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
@@ -18,9 +18,9 @@ When at all possible, Cloudflare seeks to avoid creating static representations
 
 Potential examples include:
 
-- Exhaustive listing of fields
-- Replicating API content in developer docs
-- Maintaining lists of potential options in the UI (i.e., Alert types)
-- Verified Bots
+* Exhaustive listing of fields
+* Replicating API content in developer docs
+* Maintaining lists of potential options in the UI (i.e., Alert types)
+* Verified Bots
 
 The preferred approach would be speak more generally to the categories or specific, high-value fields.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
index f02e3493fdef2c0..335031ce0afc95f 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
@@ -12,12 +12,14 @@ A code sample or line of text that shows the specific structure of a request/res
 
 :::note
 
+
 If you are unsure about when to categorize something as an example or tutorial, remember:
 
 Examples are a component attribute and are typically a snippet of code a user might copy and paste to run a task. Examples should not have multiple steps. A tutorial might contain an example, but an example will not contain a tutorial.
 
 Tutorials are a content type, typically longer form, and contain multiple steps to help users connect products to real-world scenarios.
 
+
 :::
 
 ## Used in
@@ -34,9 +36,9 @@ Explain what the code sample does in a short sentence.
 
 These could include:
 
-- Example requests and responses
-- Example inputs and outputs
-- Field values for UI and/or API
+* Example requests and responses
+* Example inputs and outputs
+* Field values for UI and/or API
 
 ## Additional information
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
index d2ac5552b440a7c..eb6cc09d35a217d 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
@@ -56,16 +56,21 @@ entries:
 Relevant values include the following:
 
 - `productName` string required
+
   - Core product associated with this file. Should always match the same formatting / styling used in `associated_products`.
 
 - `entries` object required
+
   - `term` string required
+
     - The glossary term itself.
 
   - `general_definition` string required
+
     - Definition of the term. Should be general enough to apply to multiple products. Should also start with a lowercase letter unless starting with a proper noun.
 
   - `associated_products` array optional
+
     - If the term is associated with other products. Any names used should correspond to the `productName` of that associated file.
 
 ### Usage
@@ -104,9 +109,11 @@ Is a quoted definition that comes from:
 Properties are:
 
 - `term` string required
+
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
+
   - Text to add before a definition.
 
 #### Glossary tooltip
@@ -122,12 +129,15 @@ Here's a <GlossaryTooltip term="active zone">tooltip</GlossaryTooltip> example.
 Properties are:
 
 - `term` string required
+
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
+
   - Text to add before a definition.
 
 - `link` string optional
+
   - Wraps the inner text in a markdown link, similar to normal markdown formatting.
 
 Because of space limitations, the tooltip will always default to the short definition of a term, meaning the definition text before the first line break.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
index 6027b8e869f159d..0e75f19c6dc5e99 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
index c412e4ff4c12769..017decd9096ef80 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
@@ -28,15 +28,15 @@ This reference architecture is designed for IT or security professionals with so
 
 To build a stronger baseline understanding of Cloudflare, we recommend the following resources:
 
-- What is Cloudflare? | Website (5 minute read) or video (2 minutes)
-- Solution Brief: Cloudflare One (3 minute read)
-- Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
-- Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
+* What is Cloudflare? | Website (5 minute read) or video (2 minutes)
+* Solution Brief: Cloudflare One (3 minute read)
+* Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
+* Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
 
 Those who read this reference architecture will learn:
 
-- How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
-- How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
-- How to plan for deploying Cloudflare One
+* How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
+* How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
+* How to plan for deploying Cloudflare One
 
 While this document examines Cloudflare One at a technical level, it does not offer fine detail about every product in the platform. Instead, it looks at how all the services in Cloudflare One enable networking and network security to be consolidated on one architecture. Visit the developer documentation for further information specific to a product area or use case.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
index aa2c818fd681979..5935c28d4a85d09 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
@@ -44,15 +44,15 @@ Cross-links between related pages create a navigable knowledge graph. When an AI
 
 Every page with a `pcx_content_type` should include links to related pages in its **Related resources** section. Use the following table to determine which content types to link to from each page.
 
-| Content type    | Must link to                                                                 |
-| --------------- | ---------------------------------------------------------------------------- |
-| Concept         | Related how-to or get-started page; related reference page                   |
-| How-to          | Prerequisite concept page; relevant configuration page; troubleshooting page |
-| Get started     | Next-level how-to pages; product overview page                               |
-| Troubleshooting | Related how-to page; relevant configuration page                             |
-| Configuration   | Parent how-to or get-started page; relevant concept page                     |
-| Reference       | Related concept page; how-to pages that use the reference                    |
-| Tutorial        | Related product overview; prerequisite get-started page                      |
+| Content type | Must link to |
+| --- | --- |
+| Concept | Related how-to or get-started page; related reference page |
+| How-to | Prerequisite concept page; relevant configuration page; troubleshooting page |
+| Get started | Next-level how-to pages; product overview page |
+| Troubleshooting | Related how-to page; relevant configuration page |
+| Configuration | Parent how-to or get-started page; relevant concept page |
+| Reference | Related concept page; how-to pages that use the reference |
+| Tutorial | Related product overview; prerequisite get-started page |
 
 Links should be bidirectional. If a concept page links to a how-to, the how-to should link back to the concept page. This ensures that users (and AI systems) can traverse between pages in either direction.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
index 6bd0cb8c746ca6e..7971b04fd461597 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
@@ -20,7 +20,7 @@ If an operation occurs inside of a code block, use the formatting associated wit
 
 ## Example
 
-| Correct             | Incorrect         |
-| ------------------- | ----------------- |
-| 25 / 30             | 25/30             |
+| Correct                       | Incorrect         |
+| ----------------------------- | ----------------- |
+| 25 / 30                       | 25/30             |
 | `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏` | e(aP,bQ)=e(P,Q)ab |
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
index 365813c38ea3809..dd344888b67b5bd 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
@@ -20,9 +20,9 @@ One to two sentences
 
 It should answer:
 
-- What happens now?
-- What was the end result of the procedure?
-- What do users do next?
+* What happens now?
+* What was the end result of the procedure?
+* What do users do next?
 
 ## Cross-linking
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
index 59f4a527a66fde9..f17397285f578bf 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
@@ -52,7 +52,7 @@ Use a warning to alert a reader to behavior that could impact the security of a
 
 ## Recommendations
 
-- **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
-- **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
-- **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
-- **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
+* **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
+* **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
+* **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
+* **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
index f696235502bd1f7..b0d981549ac0adf 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
@@ -14,10 +14,10 @@ The information architecture (IA) of the Cloudflare developer documentation foll
 
 At launch, Cloudflare Developer Platform products are recommended to include the following high-level sections. The following is a recommended guideline based on standard user journey flow (Learn, Get started, Configure, Test, Deploy, Asses, Maintain, etc.) and is intended to serve as a helpful reference to the documentation writer and collaborators. Depending on the product and as products mature, the IA may grow out of this structure or differ from this structure based on what you can do with the product. For an example of a more mature product that differs from this IA, refer to the [Cloudflare Stream documentation](/stream/).
 
-- [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
-- [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
-- [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
-- Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
-- [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
-- [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
-- Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
+* [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
+* [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
+* [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
+* Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
+* [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
+* [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
+* Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
diff --git a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
index 5ec373d9988218e..1b38177313b1f44 100644
--- a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
+++ b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
@@ -80,9 +80,9 @@ In nested menus, use bold for the word not the symbol.
 
 Example: **Dashboard** > **This** > **That**
 
-## _Italics_
+## *Italics*
 
-Use _italics_ when referring to an option that customers can select from, like in dropdown menus.
+Use *italics* when referring to an option that customers can select from, like in dropdown menus.
 
 Do not use italics when referring to the state of a toggle - for example, enabled/disabled should not be italicized.
 
@@ -94,32 +94,32 @@ Text in this font denotes text or characters that you should enter from the keyb
 
 ### Examples of elements we monospace
 
-| Element                                                    | Example                                                                                                                                                                                      |
-| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                                                                                                         |
-| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                                                                                                                |
-| API commands                                               | The endpoint supports `GET` for JSON format.                                                                                                                                                 |
-| Terminal commands                                          | Run the command `wrangler login`.                                                                                                                                                            |
-| Attribute names and values                                 | `type`, `name`                                                                                                                                                                               |
-| Class names                                                | `button-primary`                                                                                                                                                                             |
-| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                                                                                                     |
-| Data types                                                 | (`string`, `number`, `int64`)                                                                                                                                                                |
-| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                                                                                                           |
-| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink. |
-| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                                                                                                    |
-| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                                                                                                           |
-| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                                                                                                       |
-| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                                                                                                            |
-| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                                                                                                              |
-| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                                                                                                        |
-| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx.                                                                                   |
-| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                                                                                                         |
-| HTTP header names                                          | `Content-Length`                                                                                                                                                                             |
-| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                                                                                                                 |
-| IAM role names                                             | `roles/storage.admin`                                                                                                                                                                        |
-| Language keywords                                          | `in`, `await`                                                                                                                                                                                |
-| Method and function names                                  | `handleRequest`                                                                                                                                                                              |
-| Namespace aliases                                          | `numpy`                                                                                                                                                                                      |
-| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                                                                                                           |
-| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                                                                                                       |
-| Text input                                                 | `"Hello Worker"`                                                                                                                                                                             |
+| Element                                                    | Example                                                                                                    |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                       |
+| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                              |
+| API commands                                               | The endpoint supports `GET` for JSON format.                                                               |
+| Terminal commands                                          | Run the command `wrangler login`.                                                                          |
+| Attribute names and values                                 | `type`, `name`                                                                                             |
+| Class names                                                | `button-primary`                                                                                           |
+| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                   |
+| Data types                                                 | (`string`, `number`, `int64`)                                                                              |
+| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                         |
+| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink.  |
+| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                  |
+| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                         |
+| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                     |
+| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                        |
+| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                            |
+| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                      |
+| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx. |
+| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                       |
+| HTTP header names                                          | `Content-Length`                                                                                           |
+| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                               |
+| IAM role names                                             | `roles/storage.admin`                                                                                      |
+| Language keywords                                          | `in`, `await`                                                                                              |
+| Method and function names                                  | `handleRequest`                                                                                            |
+| Namespace aliases                                          | `numpy`                                                                                                    |
+| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                         |
+| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                     |
+| Text input                                                 | `"Hello Worker"`                                                                                           |
diff --git a/src/content/docs/style-guide/formatting/dates-and-times.mdx b/src/content/docs/style-guide/formatting/dates-and-times.mdx
index 70172f50376d6b5..ab9f427759fec31 100644
--- a/src/content/docs/style-guide/formatting/dates-and-times.mdx
+++ b/src/content/docs/style-guide/formatting/dates-and-times.mdx
@@ -10,9 +10,9 @@ products:
 
 To account for internationalization and inclusivity of all locales, use the ISO-8601 (YYYY-MM-DD hh:mm:ss) standard when writing dates and times as much as possible.
 
-In general, documentation should strive to represent universal truth, not
-something time-bound. This is why semgrep may flag uses of explicit dates
-or month names or years because often become out-of-date and not be
+In general, documentation should strive to represent universal truth, not 
+something time-bound. This is why semgrep may flag uses of explicit dates 
+or month names or years because often become out-of-date and not be 
 revised later.
 
 ## Blogs
diff --git a/src/content/docs/style-guide/formatting/external-references.mdx b/src/content/docs/style-guide/formatting/external-references.mdx
index 49120127e781b06..19253920fd68de6 100644
--- a/src/content/docs/style-guide/formatting/external-references.mdx
+++ b/src/content/docs/style-guide/formatting/external-references.mdx
@@ -11,9 +11,9 @@ When referencing external resources, ensure that you are linking to a trustworth
 
 For general websites, consider the following recommendations about the link text:
 
-- Use the website name if you are linking to the home page.
-- Use the page name if you are linking to a specific page.
-- Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
+* Use the website name if you are linking to the home page.
+* Use the page name if you are linking to a specific page.
+* Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
 When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
diff --git a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
index 7ef14947ec6845d..316c3540dcbba9d 100644
--- a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
+++ b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
@@ -8,8 +8,8 @@ products:
 
 You can refer both to file types and file extensions in documentation:
 
-- File types: Accepted file formats are JSON and YAML.
-- File extensions: Upload the `.txt` file to the dashboard.
+* File types: Accepted file formats are JSON and YAML.
+* File extensions: Upload the `.txt` file to the dashboard.
 
 When referring to a specific file type, always use regular text formatting, write the file type in uppercase, and avoid the initial dot (you are referring to the file type, not the file extension).
 
@@ -17,7 +17,7 @@ When referring to a specific extension, always monospace the file, include a dot
 
 Additional examples:
 
-- The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
-- Additionally, this plist can be wrapped in a `.mobileconfig` file.
-- If you would like to test how this feature works, here is a sample `.csv` file.
-- Concatenate the string to a text-based `.pem` file.
+* The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
+* Additionally, this plist can be wrapped in a `.mobileconfig` file.
+* If you would like to test how this feature works, here is a sample `.csv` file.
+* Concatenate the string to a text-based `.pem` file.
diff --git a/src/content/docs/style-guide/formatting/index.mdx b/src/content/docs/style-guide/formatting/index.mdx
index 7ec4a59dacb722c..8c1d56e0c307810 100644
--- a/src/content/docs/style-guide/formatting/index.mdx
+++ b/src/content/docs/style-guide/formatting/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/keyboard-keys.mdx b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
index 9dad67aca460e95..d9faeed37a3cd77 100644
--- a/src/content/docs/style-guide/formatting/keyboard-keys.mdx
+++ b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
@@ -14,20 +14,16 @@ products:
 ## Formatting keyboard shortcuts
 
 When telling readers what keyboard shortcuts to use to achieve a result:
-
 - Place the keyboard shortcut in between backticks (monospace formatting)
 - Use uppercase letters with the abbreviated version of the key (`CTRL` instead of `CONTROL`, `CMD` instead of `COMMAND`for example)
 - Wrap the complete keyboard shortcut in between backticks, including the plus sign:
-  - **Do**:
-
-  ```mdx
-  `CTRL + C`
-  ```
-
-  - **Don't**:
-
-  ```mdx
-  `CTRL` + `C`
-  ```
-
-- Do not use the old `<kbd></kbd>` component
+	- **Do**:
+	```mdx
+	`CTRL + C`
+	```
+
+	- **Don't**:
+	```mdx
+	`CTRL` + `C`
+	```
+- Do not use the old `<kbd></kbd>` component
\ No newline at end of file
diff --git a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
index 02c81845f3a290b..382bab58c8d7d78 100644
--- a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
+++ b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
@@ -9,7 +9,6 @@ products:
 When adding a note to a page, always use this special note formatting. There are three types of formatted notes: `note`, `caution`, and `tip`.
 
 Here is some additional information about notes:
-
 - The color of the note depends on the type of note: `note` is blue, `caution` is yellow, and `tip` is purple.
 - For every note type, the header text is optional.
 - All note types can contain text and additional formatting like lists, code blocks, and images.
diff --git a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
index 96a4801c772e1e3..5085765a1f2090b 100644
--- a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
+++ b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
@@ -10,26 +10,26 @@ products:
 
 In body text, spell out whole numbers from zero through nine.
 
-- Example: We have added three more servers.
+* Example: We have added three more servers.
 
 For numbers greater than or equal to 10, use digits.
 
-- Example: The message is 32 bytes long, \[...]
+* Example: The message is 32 bytes long, \[...]
 
 For analytics, display metrics with numerals.
 Use commas for numbers with more than 3 digits (no spaces). Note the differences in numerical punctuation for translation.
 
-- 300
-- 1,000
-- 7,465
+* 300
+* 1,000
+* 7,465
 
 ## Using k to indicate thousands
 
 Do not put a space between the number and k.
 
-Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for _kilobytes_.
+Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for *kilobytes*.
 
-- Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
+* Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
 
 ## Units of measurement
 
@@ -45,14 +45,14 @@ Many CPU architectures either do not allow execution of the machine code, which
 
 In general, only abbreviate units of measurements when they modify specific quantities/numbers. When you need to abbreviate them:
 
-| ✅    | ❌     | Rationale                                              |
+| ✅     | ❌      | Rationale                                              |
 | ----- | ------ | ------------------------------------------------------ |
 | 10 m  | 10m    | Always include a space between the number and the unit |
 | 10 cm | 10 cms | Unit symbols should unaltered in the plural.           |
 
 **Always include a space between a numerical value and the corresponding unit of measurement.** Although both formats are widely used, the metric system standardized the use of a space before a unit of measurement and should be used as a guideline to keep content consistent and clear.
 
-| ✅                                               | ❌                                          | Rationale                                                                                                   |
+| ✅                                                | ❌                                           | Rationale                                                                                                   |
 | ------------------------------------------------ | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
 | 128 GB                                           | 128 gb, 128gb, 128GB                        | Units of measurement should always be capitalized and spaced out from their corresponding numerical values. |
 | This network has a capacity of over **30 Tbps.** | This network has a capacity of over 30Tbps. | Adding a space between ‘30’ and ‘Tbps’ makes this sentence easier to read.                                  |
diff --git a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
index 25c6ca97daeed00..e44f43ed36fdc50 100644
--- a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
+++ b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
@@ -10,5 +10,5 @@ Product names should follow a noun-verb agreement such that the verb is singular
 
 Examples:
 
-- Cloudflare Pages enables/allows.
-- Cloudflare Workers executes/propagates.
+* Cloudflare Pages enables/allows.
+* Cloudflare Workers executes/propagates.
diff --git a/src/content/docs/style-guide/formatting/structure/index.mdx b/src/content/docs/style-guide/formatting/structure/index.mdx
index 3498fa8f873c716..e2f981f9d22a682 100644
--- a/src/content/docs/style-guide/formatting/structure/index.mdx
+++ b/src/content/docs/style-guide/formatting/structure/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/structure/lists.mdx b/src/content/docs/style-guide/formatting/structure/lists.mdx
index 35a60f4a49b706c..94571bd31ee8c27 100644
--- a/src/content/docs/style-guide/formatting/structure/lists.mdx
+++ b/src/content/docs/style-guide/formatting/structure/lists.mdx
@@ -8,15 +8,15 @@ products:
 
 There are three types of lists:
 
-- Bulleted lists for unordered items
-- Numbered lists for ordered items
-- Embedded lists for items within a sentence
+* Bulleted lists for unordered items
+* Numbered lists for ordered items
+* Embedded lists for items within a sentence
 
 Here are some tips when creating lists:
 
-- Keep list items parallel
-- Start numbered lists with a command (imperative verb)
-- Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
+* Keep list items parallel
+* Start numbered lists with a command (imperative verb)
+* Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
 
 ## Bullet points
 
@@ -25,37 +25,26 @@ Bullet points help the reader's eye focus on a list of important elements.
 However, as with any other aspect of writing, they should be used mindfully. Below is a list of when you should and should not resort to bullet points.
 
 <table>
-	<thead>
-		<tr>
-			<th>❌ Do not use bullet points</th>
-			<th>✅ Use bullet points</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>
-				To outline <b>processes</b> (prefer numbered lists)
-			</td>
-			<td>
-				To list <b>facts</b>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				To explain your reasoning (it is a blog post, not a list of system
-				requirements)
-			</td>
-			<td>
-				To list <b>data</b>
-			</td>
-		</tr>
-		<tr>
-			<td>-</td>
-			<td>
-				To list <b>options</b>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+        <th>❌ Do not use bullet points</th>
+        <th>✅ Use bullet points</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+        <td>To outline <b>processes</b> (prefer numbered lists)</td>
+        <td>To list <b>facts</b></td>
+    </tr>
+    <tr>
+        <td>To explain your reasoning (it is a blog post, not a list of system requirements)</td>
+        <td>To list <b>data</b></td>
+    </tr>
+    <tr>
+        <td>-</td>
+        <td>To list <b>options</b></td>
+    </tr>
+    </tbody>
 </table>
 
 ## Bulleted lists
@@ -66,8 +55,8 @@ Do not punctuate bullet points unless each item is a full sentence.
 
 If bullet point items are followed by a description, use a colon after the heading and capitalize the description. For example,
 
-- **Item 1**: Description 1
-- **Item 2**: Description 2
+* **Item 1**: Description 1
+* **Item 2**: Description 2
 
 For bullet points, try to stick to the "six-pack" rule: no more than six bullets, each made up of six words or less.
 
@@ -78,14 +67,14 @@ Refer to [The best way to use bullet points](https://thewritinghabit.blog/2016/0
 When you find yourself creating a list of bullet points, go through this checklist:
 
 1. Do all bullet points belong together?
-   - Check that all the elements in the list are logically connected.
+   * Check that all the elements in the list are logically connected.
 2. Do I have more three or more bullet points, but less than six?
-   - Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
+   * Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
 3. Are all bullet points shorter than three lines of text?
-   - Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
+   * Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
 4. Is punctuation consistent?
-   - End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
+   * End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
 5. Do all bullet points start with the most important word we want the reader to remember?
-   - Make sure the "head" of your bullet point is not hiding after a long circumlocution.
+   * Make sure the "head" of your bullet point is not hiding after a long circumlocution.
 6. Do all bullet points start with the same part of speech?
-   - If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
+   * If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
diff --git a/src/content/docs/style-guide/formatting/structure/tables.mdx b/src/content/docs/style-guide/formatting/structure/tables.mdx
index 7a79ef760d68e39..d43a5fa3787672b 100644
--- a/src/content/docs/style-guide/formatting/structure/tables.mdx
+++ b/src/content/docs/style-guide/formatting/structure/tables.mdx
@@ -12,14 +12,14 @@ Using tables to simplify content and data provides a comprehensive way to arrang
 
 Here are some tips when creating tables:
 
-- Label column headers.
-- Label row headers if appropriate.
-- Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
-- Avoid too much text.
-- Aim for parallelism within the column.
-- Keep tables as simple and as small as possible.
-- Sort rows in a logical order. If no logical order exists, use alphabetical order.
-- <Render file="table-guidelines" product="style-guide" />
+* Label column headers.
+* Label row headers if appropriate.
+* Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
+* Avoid too much text.
+* Aim for parallelism within the column.
+* Keep tables as simple and as small as possible.
+* Sort rows in a logical order. If no logical order exists, use alphabetical order.
+* <Render file="table-guidelines" product="style-guide" />
 
 ## Introductory sentences
 
@@ -29,25 +29,25 @@ When referring to a table, use a phrase like "the following table" or "the prece
 
 ## Column headings
 
-- Use sentence case.
-- Write concise headings that clearly describe the column content.
-- Do not end column headings with punctuation, including periods, ellipses, or colons.
-- Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
+* Use sentence case.
+* Write concise headings that clearly describe the column content.
+* Do not end column headings with punctuation, including periods, ellipses, or colons.
+* Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
 
 ```html
 <thead>
-	<tr>
-		<th scope="col">Name</th>
-		<th scope="col">Description</th>
-	</tr>
+  <tr>
+    <th scope="col">Name</th>
+    <th scope="col">Description</th>
+  </tr>
 </thead>
 ```
 
 ## Table placement
 
-- Place each table directly after the sentence that introduces it.
-- Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
-- If a table has footnotes, place them immediately after the table.
+* Place each table directly after the sentence that introduces it.
+* Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
+* If a table has footnotes, place them immediately after the table.
 
 ## Table captions
 
@@ -62,9 +62,9 @@ In Markdown, place the caption as a bold line immediately before the table:
 ```markdown
 **Table 1.** Supported DNS record types
 
-| Type | Description                      |
-| ---- | -------------------------------- |
-| A    | Maps a domain to an IPv4 address |
+| Type | Description |
+| --- | --- |
+| A | Maps a domain to an IPv4 address |
 | AAAA | Maps a domain to an IPv6 address |
 ```
 
@@ -72,22 +72,19 @@ In HTML, use the `caption` element as the first child of the `table` element:
 
 ```html
 <table>
-	<caption>
-		<b>Table 1.</b>
-		Supported DNS record types
-	</caption>
-	<thead>
-		<tr>
-			<th scope="col">Type</th>
-			<th scope="col">Description</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>A</td>
-			<td>Maps a domain to an IPv4 address</td>
-		</tr>
-	</tbody>
+  <caption><b>Table 1.</b> Supported DNS record types</caption>
+  <thead>
+    <tr>
+      <th scope="col">Type</th>
+      <th scope="col">Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A</td>
+      <td>Maps a domain to an IPv4 address</td>
+    </tr>
+  </tbody>
 </table>
 ```
 
@@ -97,8 +94,8 @@ Tables display pieces of information that have some sort of relationship.
 
 Example:
 
-- Dates and descriptions, like a changelog
-- A list of products with attributes
+* Dates and descriptions, like a changelog
+* A list of products with attributes
 
 ## When not to use tables
 
@@ -142,7 +139,7 @@ The rendered output looks like this:
 | Syntax    | Description |    Test Text |
 | :-------- | :---------: | -----------: |
 | Header    |    Title    | Here is this |
-| Paragraph |    Text     |     And more |
+| Paragraph |     Text    |     And more |
 
 ## Formatting text in tables
 
diff --git a/src/content/docs/style-guide/frontmatter/sidebar.mdx b/src/content/docs/style-guide/frontmatter/sidebar.mdx
index b28d8a5f1d52ccb..ec8a552cab6f221 100644
--- a/src/content/docs/style-guide/frontmatter/sidebar.mdx
+++ b/src/content/docs/style-guide/frontmatter/sidebar.mdx
@@ -215,5 +215,5 @@ sidebar:
 
 ### Automatic "Beta" badges
 
-A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status.
-This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`.
+A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status. 
+This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`. 
diff --git a/src/content/docs/style-guide/grammar/index.mdx b/src/content/docs/style-guide/grammar/index.mdx
index c7d3f0ea3544cd9..d70d2ce818eea88 100644
--- a/src/content/docs/style-guide/grammar/index.mdx
+++ b/src/content/docs/style-guide/grammar/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
index bffb664c1bd3269..3241618b639da6b 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
@@ -6,7 +6,7 @@ products:
   - style-guide
 ---
 
-Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word _acronym_ to refer to both).
+Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word *acronym* to refer to both).
 
 ## Long and short versions of a word
 
@@ -16,7 +16,7 @@ The short versions of the words are not abbreviations, and if you use them, you
 
 If you are not sure whether a word is an abbreviation or just a short version of a longer word, here is a list of [common abbreviations](https://abbreviations.yourdictionary.com/articles/list-of-commonly-used-abbreviations.html). If that does not settle the issue, use the speaking test: if you speak the short version as a word ("This is a demo version of the product"), you can usually treat it as a word and not an abbreviation.
 
-If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer _applications_ on Cloudflare for Teams are not shortened to _apps_. Depending on the use case, application might be the preferred term, especially due to translation.
+If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer *applications* on Cloudflare for Teams are not shortened to *apps*. Depending on the use case, application might be the preferred term, especially due to translation.
 
 ## When to spell out a term
 
@@ -24,28 +24,28 @@ In general, when an abbreviation is likely to be unfamiliar to the audience, spe
 
 If the first mention of a term occurs in a heading or title, you can use the abbreviation and then spell out the abbreviation in the first paragraph that follows the heading or title.
 
-When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out _application programming interface_. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
+When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out *application programming interface*. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
 
-In some cases, spelling out a term does not help the reader understand the term. For example, writing out _portable document format_ does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
+In some cases, spelling out a term does not help the reader understand the term. For example, writing out *portable document format* does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
 
 The following abbreviations rarely need to be spelled out:
 
-- API
-- DVD
-- File formats such as PDF or XML
-- HTML
-- PC
-- RAM
-- REST
-- Units of measure such as MB or GB
-- URL
-- USB
+* API
+* DVD
+* File formats such as PDF or XML
+* HTML
+* PC
+* RAM
+* REST
+* Units of measure such as MB or GB
+* URL
+* USB
 
 ## Abbreviations not to use
 
 Prefer English terms over Latin abbreviations. Do not use i.e. or e.g. Instead, use **that is** or **for example**, respectively.
 
-One exception: avoid both _etc._ and _and so on_ wherever possible, but if you really need to use one, use _etc._ Always include the period, even if a comma follows immediately after.
+One exception: avoid both *etc.* and *and so on* wherever possible, but if you really need to use one, use *etc.* Always include the period, even if a comma follows immediately after.
 
 Do not use Internet slang abbreviations such as tl;dr, IMO, FYI, or others.
 
@@ -55,16 +55,16 @@ Use the most common form of a word. If the full spelled-out word is common and e
 
 Follow these guidelines:
 
-- Do not use periods with acronyms or initialisms.
-- Put a period at the end of a shortened word, except for date and time abbreviations.
-- If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
-- Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
+* Do not use periods with acronyms or initialisms.
+* Put a period at the end of a shortened word, except for date and time abbreviations.
+* If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
+* Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
 
 ## i.e. vs e.g.
 
 While similar, these two Latin abbreviations carry very different meanings.
 
-- **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
-  - The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
-- **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
-  - Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
+* **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
+  * The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
+* **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
+  * Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
index 3d4836341a01f1b..1b9979cc0ba573e 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
@@ -6,10 +6,10 @@ products:
   - style-guide
 ---
 
-**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
+**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some  terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
 
-- If the term already exists, link to a good existing explanation.
+* If the term already exists, link to a good existing explanation.
 
-- If your document is introducing the term, define the term.
+* If your document is introducing the term, define the term.
 
-- **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
+* **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods  between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word  — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
index ca1c548ad846c7e..fbbcad12c379e14 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
@@ -10,7 +10,7 @@ products:
 
 Each product, service, and feature should be properly spelled and capitalized when used in any content, both to ensure consistency across all channels and to differentiate common performance and security technologies (for example: load balancing, bot management, and web application firewalls) from specific Cloudflare solutions (for example: Cloudflare Load Balancing, Cloudflare Bot Management, and Cloudflare Web Application Firewall).
 
-| ✅                                                                                                                                                          | ❌                                                                                                                                               | Rationale                                                                                                                                   |
+| ✅                                                                                                                                                           | ❌                                                                                                                                                | Rationale                                                                                                                                   |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | This interactive demo provides three different scenarios on how to utilize **Cloudflare Rate Limiting** to protect your endpoints from suspicious requests. | This interactive demo provides three different scenarios on how to utilize **rate limiting** to protect your endpoints from suspicious requests. | This demo is specific to a Cloudflare product (Cloudflare Rate Limiting), not a tutorial on utilizing generic rate limiting.                |
 | The **Cloudflare Web Application Firewall (WAF)** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.       | Our **web application firewall** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.             | Cloudflare Web Application Firewall (WAF) is a specific product we offer and should be capitalized and identified with the Cloudflare name. |
@@ -19,109 +19,75 @@ Each product, service, and feature should be properly spelled and capitalized wh
 
 **When to use Waiting Room capitalized and singular:**
 
-- Naming the product: _Waiting Room keeps wait times low by dynamically managing traffic._
-- Page title: _Access Waiting Room_
-- Preceded by “Cloudflare”: _Cloudflare Waiting Room allows organizations to…_
-- Preceding a feature name: _Waiting Room Event Scheduling_
+* Naming the product: *Waiting Room keeps wait times low by dynamically managing traffic.*
+* Page title: *Access Waiting Room*
+* Preceded by “Cloudflare”: *Cloudflare Waiting Room allows organizations to…*
+* Preceding a feature name: *Waiting Room Event Scheduling*
 
 **When to waiting room(s) lower-case and in singular or plural:**
 
-- Used as an object: _Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room._
-- Capitalize only the first word when at the beginning of a sentence: _Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated._
-- Capitalize only the first word when it is the title of a subsection: _### Waiting room template_
+* Used as an object: *Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room.*
+* Capitalize only the first word when at the beginning of a sentence:  *Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated.*
+* Capitalize only the first word when it is the title of a subsection: *### Waiting room template*
 
 ## Common capitalization conventions
 
 <table>
-	<tr>
-		<th style="width:20%">✅</th>
-		<th style="width:20%">❌</th>
-		<th>Rationale</th>
-	</tr>
-	<tr>
-		<td>CAPTCHA, reCAPTCHA</td>
-		<td>Captcha, captcha, recaptcha, Recaptcha</td>
-		<td>
-			A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are
-			not bots.
-		</td>
-	</tr>
-	<tr>
-		<td>cloud</td>
-		<td>Cloud, "cloud"</td>
-		<td>
-			The <b>cloud</b> is a network of remote servers used to store and maintain
-			data.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>DDoS</td>
-		<td>ddos, DDOS</td>
-		<td>
-			A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a
-			targeted server.
-		</td>
-	</tr>
-	<tr>
-		<td>denial-of-service (DoS)</td>
-		<td>
-			denial of service, Denial-of-Service, Denial-Of-Service, Denial of
-			Service, dos, Dos, DOS
-		</td>
-		<td>
-			DDoS is a type of <b>DoS</b> attack.
-		</td>
-	</tr>
-	<tr>
-		<td>Enterprise, enterprise</td>
-		<td>ent, ENT</td>
-		<td>
-			Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or
-			a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise
-			customers are enterprise companies, but not all enterprises are Enterprise
-			customers.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>Internet</td>
-		<td>internet</td>
-		<td>
-			Disabling this option may cause all devices to lose <b>Internet</b>{" "}
-			connectivity.
-		</td>
-	</tr>
-	<tr>
-		<td>SSL</td>
-		<td>ssl</td>
-		<td>
-			<b>SSL</b> is an encryption-based Internet security protocol.
-		</td>
-	</tr>
-	<tr>
-		<td>TLS</td>
-		<td>tls</td>
-		<td>
-			<b>TLS</b> is a security protocol designed to facilitate privacy and data
-			security for communications over the Internet..
-		</td>
-	</tr>
-	<tr>
-		<td>WAF</td>
-		<td>waf</td>
-		<td>
-			<b>WAF</b> is a security system that helps protect web applications by
-			filtering and monitoring HTTP traffic between a web application and the
-			Internet.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>Zero Trust</td>
-		<td>zero trust</td>
-		<td>
-			<b>Cloudflare</b> Access is a Zero Trust solution that secures inbound
-			connections to your protected applications.
-		</td>
-	</tr>
+  <tr>
+    <th style="width:20%">✅</th>
+    <th style="width:20%">❌</th>
+    <th>Rationale</th>
+  </tr>
+  <tr>
+    <td>CAPTCHA, reCAPTCHA</td>
+    <td>Captcha, captcha, recaptcha, Recaptcha</td>
+    <td>A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are not bots.</td>
+  </tr>
+  <tr>
+    <td>cloud</td>
+    <td>Cloud, "cloud"</td>
+    <td>The <b>cloud</b> is a network of remote servers used to store and maintain data. </td>
+  </tr>
+  <tr>
+    <td>DDoS</td>
+    <td>ddos, DDOS</td>
+    <td>A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a targeted server.</td>
+  </tr>
+  <tr>
+    <td>denial-of-service (DoS)</td>
+    <td>denial of service, Denial-of-Service, Denial-Of-Service, Denial of Service, dos, Dos, DOS</td>
+    <td>DDoS is a type of <b>DoS</b> attack.</td>
+  </tr>
+  <tr>
+    <td>Enterprise, enterprise</td>
+    <td>ent, ENT</td>
+    <td>Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise customers are enterprise companies, but not all enterprises are Enterprise customers. </td>
+  </tr>
+  <tr>
+    <td>Internet</td>
+    <td>internet</td>
+    <td>Disabling this option may cause all devices to lose <b>Internet</b> connectivity.</td>
+  </tr>
+  <tr>
+    <td>SSL</td>
+    <td>ssl</td>
+    <td><b>SSL</b> is an encryption-based Internet security protocol.</td>
+  </tr>
+  <tr>
+    <td>TLS</td>
+    <td>tls</td>
+    <td><b>TLS</b> is a security protocol designed to facilitate privacy and data security for communications over the Internet..</td>
+  </tr>
+  <tr>
+    <td>WAF</td>
+    <td>waf</td>
+    <td><b>WAF</b> is a security system that helps protect web applications by filtering and monitoring HTTP traffic between a web application and the Internet. </td>
+  </tr>
+  <tr>
+    <td>Zero Trust</td>
+    <td>zero trust</td>
+    <td><b>Cloudflare</b> Access is a Zero Trust solution that secures inbound connections to your protected applications.</td>
+  </tr>
 </table>
 
 ## Headings
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
index e7f8868af4430c8..1e61e8bfdd8ecf5 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
@@ -11,34 +11,31 @@ products:
 Whitespace is used in our blog posts and product content. For the sake of consistency, follow these conventions when using them:
 
 <table>
-	<tr>
-		<th style="width:20%">✅</th>
-		<th style="width:20%">❌</th>
-		<th>Example</th>
-	</tr>
-	<tr>
-		<td>nameserver</td>
-		<td>name servers</td>
-		<td>Change your nameservers to Cloudflare's.</td>
-	</tr>
-	<tr>
-		<td>hostname</td>
-		<td>host name</td>
-		<td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
-	</tr>
-	<tr>
-		<td>data center</td>
-		<td>datacenter</td>
-		<td>
-			Cloudflare updates the new setting across all of our data centers around
-			the world.
-		</td>
-	</tr>
-	<tr>
-		<td>checkbox</td>
-		<td>check box</td>
-		<td>Select the Transfer lock checkbox before continuing the setup.</td>
-	</tr>
+  <tr>
+    <th style="width:20%">✅</th>
+    <th style="width:20%">❌</th>
+    <th>Example</th>
+  </tr>
+  <tr>
+    <td>nameserver</td>
+    <td>name servers</td>
+    <td>Change your nameservers to Cloudflare's.</td>
+  </tr>
+  <tr>
+    <td>hostname</td>
+    <td>host name</td>
+    <td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
+  </tr>
+  <tr>
+    <td>data center</td>
+    <td>datacenter</td>
+    <td>Cloudflare updates the new setting across all of our data centers around the world.</td>
+  </tr>
+  <tr>
+    <td>checkbox</td>
+    <td>check box</td>
+    <td>Select the Transfer lock checkbox before continuing the setup.</td>
+  </tr>
 </table>
 
 When using compound words that have a preposition in them (think log in, or set up), they should be written as two separate words when they are verbs, and as one word when they are nouns.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
index 72a9ab7762531bd..fdb9214b95f5fc2 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
@@ -6,4 +6,4 @@ products:
   - style-guide
 ---
 
-Avoid using contractions such as _don't_, _won't_, and _can't_.
+Avoid using contractions such as *don't*, *won't*, and *can't*.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
index 72d3c0deacba961..dd8d05d847d9506 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
index 76a0418aeb4ab62..deb7014e128ee54 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
@@ -14,7 +14,7 @@ Make sure it is clear who or what pronouns are in reference to. Pronouns act as
 
 Substitute "we" or "I" with "Cloudflare" if you need to represent Cloudflare. You do not need to use "we" constantly. However, use it when it is the best choice grammatically.
 
-| ✅                                                          | ❌                                                                |
+| ✅                                                           | ❌                                                                 |
 | ----------------------------------------------------------- | ----------------------------------------------------------------- |
 | Cloudflare recommends you submit image or plain text files. | We recommend closing your files before you restart your computer. |
 
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
index 5f490a47e38f572..187e021787a2e58 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
@@ -8,4 +8,4 @@ products:
 
 In general, avoid the 's construction to show possession by an inanimate object as doing so personifies the object.
 
-Example: _the device's address_.
+Example: *the device's address*.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
index 8e3704dfdac8622..10c8af546776d4a 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
@@ -8,6 +8,6 @@ products:
 
 You can put a preposition at the end of a sentence, but do not do it often. Your sentences can sound stilted if you try to avoid putting the preposition at the end.
 
-| ✅                                                    | ❌                                                         |
+| ✅                                                     | ❌                                                          |
 | ----------------------------------------------------- | ---------------------------------------------------------- |
 | Open the application you are submitting an image for. | Open the application for which you are submitting an icon. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
index 39a5939c88506d9..415d78fa7023e8f 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
@@ -18,6 +18,6 @@ Example: After you open the file, save it to your desktop with a different name.
 
 Use the Oxford comma. The Oxford comma should break up lists of three or more items in a sentence.
 
-Example: Stream for Free, Pro, and Business plans
+Example:  Stream for Free, Pro, and Business plans
 
 Without the Oxford comma, readers might misunderstand this header as free streaming for Pro and Business plans.
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
index 6e37346b1c896c4..2773cd5a9e97ed4 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
@@ -14,9 +14,9 @@ Dashes look like hyphens, but are wider. An em dash is the widest type of dash.
 
 Examples:
 
-- The most up-to-date software can be found here.
+* The most up-to-date software can be found here.
 
-- It takes 24-48 hours for the data to upload.
+* It takes 24-48 hours for the data to upload.
 
 :::note
 
@@ -26,7 +26,7 @@ Never include whitespaces around a hyphen.
 
 Additional examples:
 
-| ✅                                                                                                                   | ❌                                                                                                                   | Rationale                                                                                                                                                                                 |
+| ✅                                                                                                                    | ❌                                                                                                                    | Rationale                                                                                                                                                                                 |
 | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Protect your Internet property from common vulnerabilities with our enterprise-class Web Application Firewall (WAF). | Protect your Internet property from common vulnerabilities with our enterprise class Web Application Firewall (WAF). | ‘Enterprise-class’ refers to the ability of something to scale with and handle the needs of large enterprises. A hyphen is necessary because the compound modifier comes before the noun. |
 | Our WAF is enterprise class.                                                                                         | Our WAF is enterprise-class.                                                                                         | ‘Enterprise class’ modifies ‘WAF.’ A hyphen is not necessary because the compound modifier comes after the noun.                                                                          |
@@ -35,17 +35,17 @@ Additional examples:
 
 **Use em dashes to break up thoughts within a single sentence.** Em dashes (—) or double dashes (--) with spaces around them may be used to break up thoughts within a sentence. Single dashes (-), or hyphens, are commonly used to write compound words/modifiers and should never be used to break up thoughts in this way.
 
-- Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
+* Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
 
-- Shortcut for PC users: Hold down the Alt key and type 0151
+* Shortcut for PC users: Hold down the Alt key and type 0151
 
 Dashes are used in pairs (in place of parenthesis) or alone (in place of a semicolon or colon).
 
 Examples:
 
-- Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
+* Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
 
-- Embed yourself in the team — the best results will come when trust is built.
+* Embed yourself in the team — the best results will come when trust is built.
 
 :::note
 
@@ -54,7 +54,7 @@ Following AP style guides, and to improve readability, we include whitespaces be
 
 Additional examples:
 
-| ✅                                                                                                                                                 | ❌                                                                                                                                               | Rationale                                                                                                                                                      |
+| ✅                                                                                                                                                  | ❌                                                                                                                                                | Rationale                                                                                                                                                      |
 | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | The app has made security and privacy core to the company’s mission — and that is why it chose Cloudflare to provide an extra layer of protection. | The app has made security and privacy core to the company’s mission—and that is why it chose Cloudflare to provide an extra layer of protection. | An em dash with spaces on both sides is the appropriate way to distinguish the offset phrase at the end of this sentence.                                      |
 | ACME has always looked deeply into two sources of traffic -- organic and direct traffic.                                                           | ACME has always looked deeply into two sources of traffic - organic and direct traffic.                                                          | A double dash is the appropriate way to clarify different types of traffic at the end of this sentence. A hyphen should not be used in place of a double dash. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
index 6c7364bfdbb410d..d73f721061e8356 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/how-we-docs/our-site.mdx b/src/content/docs/style-guide/how-we-docs/our-site.mdx
index 22522e9cde5ff47..99ca2d006472130 100644
--- a/src/content/docs/style-guide/how-we-docs/our-site.mdx
+++ b/src/content/docs/style-guide/how-we-docs/our-site.mdx
@@ -28,6 +28,7 @@ We use [Starlight](https://starlight.astro.build/) for our docs, which is a free
 
 Astro's [component overrides](https://starlight.astro.build/guides/overriding-components/) and [plugins](https://starlight.astro.build/resources/plugins/) system were a big part of us [choosing this framework](https://blog.cloudflare.com/open-source-all-the-way-down-upgrading-our-developer-documentation/) and have exponentially increased our [site's capabilities](/style-guide/components/) (without much extra work).
 
+
 ## Builds
 
 We use [GitHub Actions](https://github.com/features/actions) to build our site, which is then [hosted](#hosting) on Cloudflare.
diff --git a/src/content/docs/style-guide/how-we-docs/reviews.mdx b/src/content/docs/style-guide/how-we-docs/reviews.mdx
index 26cc6567c416368..da23b24233aa04c 100644
--- a/src/content/docs/style-guide/how-we-docs/reviews.mdx
+++ b/src/content/docs/style-guide/how-we-docs/reviews.mdx
@@ -25,14 +25,14 @@ For pull requests, we use a specific [GitHub action](https://github.com/cloudfla
 - [Label products](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-products/): We add labels for the top-level product folder, which helps writers scan incoming pull requests and see which are relevant to them.
 - [Label size](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-size/): We add labels for the size of the pull request, which helps writers see the relative size of the difference. It's not a perfect measure, but we use the lines changed to estimate the size of the pull request:
 
-  <GitHubCode
-  	repo="cloudflare/cloudflare-docs"
-  	file=".github/actions/label-size/index.ts"
-  	commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
-  	lines="20-36"
-  	lang="ts"
-  	code={{ title: "label-size.ts" }}
-  />
+	<GitHubCode
+		repo="cloudflare/cloudflare-docs"
+		file=".github/actions/label-size/index.ts"
+		commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
+		lines="20-36"
+		lang="ts"
+		code={{ title: "label-size.ts" }}
+	/>
 
 - [Assign codeowners](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/assign-pr): We use our [CODEOWNERS](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/CODEOWNERS) file to automatically assign people to pull requests based on the files changed. This assignment helps writers scan and filter to see which pull requests are relevant to them.
 
@@ -42,6 +42,7 @@ For issues, we use a similar [GitHub action](https://github.com/cloudflare/cloud
 
 Our [script](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/issue-label-assign) treats issues because usually they contain links to our site instead of files within the repository. We grab the associated links in the issue description fields and then use those to assign writers (again based on `CODEOWNERS`) and add product labels.
 
+
 ## Streamline reviews
 
 To streamline reviews, we use several automations to help solve common reviewer issues.
@@ -67,7 +68,7 @@ We have a specific part of [CI](https://github.com/cloudflare/cloudflare-docs/bl
 
 ### What changed?
 
-We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub).
+We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub). 
 
 We are in the process of migrating to [Workers Builds](/workers/ci-cd/builds/git-integration/github-integration/), which provides that functionality natively.
 
@@ -103,4 +104,4 @@ This workflow - we hope - balances the needs our of team with a healthy respect
 
 We intentionally avoid the [`stale` workflow](https://github.com/github/docs/blob/main/.github/workflows/stale.yml) that closes pull requests or issues that have been inactive for a specific period of time.
 
-In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
+In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
\ No newline at end of file
diff --git a/src/content/docs/support/contacting-cloudflare-support.mdx b/src/content/docs/support/contacting-cloudflare-support.mdx
index 657813bb6f05df5..ac84963b72ae9f0 100644
--- a/src/content/docs/support/contacting-cloudflare-support.mdx
+++ b/src/content/docs/support/contacting-cloudflare-support.mdx
@@ -39,7 +39,7 @@ As a Cloudflare customer, you can contact Cloudflare for support via the communi
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------- | ----------- | ----------- |
 | [Community](https://community.cloudflare.com/)<br/>Join the community to ask basic troubleshooting questions and to view the latest resources (such as tips for resolving common issues and configuration guidance). | Yes        | Yes      | Recommended | Recommended |
 | [Discord](https://discord.cloudflare.com/)<br/>Join the Discord community to ask basic troubleshooting questions (mainly focused on the Developer Platform).                                                         | Yes        | Yes      | Recommended | Recommended |
-| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]      |
+| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]        |
 | **Chat**<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                                                      | Yes        | Yes      | No          | No          |
 | **Emergency Phone** <br/>Use phone support to reach out during emergencies such as site outages or DDoS attacks.                                                                                                     | Yes        | No       | No          | No          |
 
@@ -83,12 +83,7 @@ In both cases, you will also need your **Unique Customer ID** (refer to [Finding
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton
-	href="https://dash.cloudflare.com/?to=/:account/support"
-	icon="external"
->
-	Go to Support
-</LinkButton>
+<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -102,12 +97,7 @@ Your Unique Customer ID is required when calling the emergency phone line, regar
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton
-	href="https://dash.cloudflare.com/?to=/:account/support"
-	icon="external"
->
-	Go to Support
-</LinkButton>
+<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -141,21 +131,21 @@ To submit a support case, follow these steps:
 5. Enter a detailed summary of the issue you’re experiencing.
 
 6. Complete the case submission fields as completely as possible with the following information. _(**Please note** that missing information will increase the time it takes to resolve your issue and our team may not be able to investigate without enough information. Please review [Gathering information for troubleshooting sites](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) and make sure you include all needed information.)_
-   \- A detailed description of the issue with the following information:
-   - Timestamp (UTC)
-   - ZoneName/ZoneID
-   - Problem frequency
-   - Steps to reproduce the issue, with actual results vs expected results
-     \- Any necessary information for a technical investigation
-   - A description of the actual results vs expected results
-   - Steps to reproduce the issue, with example URLs 
-   - Exact error messages
-   - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
-   - Screenshots
-   - Relevant logs from the origin web server
-   - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
-     \- Priority level, impact to service / production
-     \- Any collaborators whom you wish to be cc'd on the case
+    \- A detailed description of the issue with the following information:
+    - Timestamp (UTC)
+    - ZoneName/ZoneID
+    - Problem frequency
+    - Steps to reproduce the issue, with actual results vs expected results
+      \- Any necessary information for a technical investigation
+    - A description of the actual results vs expected results
+    - Steps to reproduce the issue, with example URLs 
+    - Exact error messages
+    - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
+    - Screenshots
+    - Relevant logs from the origin web server
+    - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
+      \- Priority level, impact to service / production
+      \- Any collaborators whom you wish to be cc'd on the case
 
 7. Click **Submit Case**.
 
diff --git a/src/content/docs/support/index.mdx b/src/content/docs/support/index.mdx
index 113e68d713a7601..d6fc7fa654994ef 100644
--- a/src/content/docs/support/index.mdx
+++ b/src/content/docs/support/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
index 318aef05f182daf..f4dcbec1ff8594c 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
@@ -15,14 +15,14 @@ When you switch a theme or customise a theme within the WordPress admin panel, t
 
 Automatic Cache Management uses native hooks built into WordPress. The Cloudflare WordPress plugin purges the following cache URLs:
 
-- deleted_post
-- edit_post
-- delete_attachment
-- autoptimize_action_cachepurged (for compatibility with the Autoptimize WordPress plugin)
-- switch_theme
-- customize_save_after
-
----
+* deleted\_post
+* edit\_post
+* delete\_attachment
+* autoptimize\_action\_cachepurged (for compatibility with the Autoptimize WordPress plugin)
+* switch\_theme
+* customize\_save\_after
+
+***
 
 ## Enable Automatic Cache Management
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
index 0993a2e99b86ad7..9a95b6b8ff0e658 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
@@ -9,7 +9,7 @@ products:
 
 HTTP/2 Server Push allows a website to push content to a browser, without having to wait for the HTML of one page to render first. In conjunction with the concurrency support built into HTTP/2, Server Push is able to dramatically reduce the amount of requests needed to load your website.
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733367/http2-server-push-2.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733367/http2-server-push-2.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-http2_server_push_2.png)
 
@@ -23,12 +23,12 @@ define('CLOUDFLARE_HTTP2_SERVER_PUSH_ACTIVE', true);
 
 You should insert this line above where it says *"/\* That's all, stop editing! Happy blogging. \*/*", like follows:|
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733547/Screen_Shot_2017-02-09_at_16.09.31.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733547/Screen\_Shot\_2017-02-09\_at\_16.09.31.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2017_02_09_at_16_09_31.png)
 
 You should then start to see requests coming in which are initiated through Server Push, for example, in the Network tab of Chrome Development Tools you should see some assets have "Push" as the initiator:
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2016_04_26_at_15_08_59.png)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
index bd0724c70711abf..2f68ed6b392d2da 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
@@ -11,7 +11,7 @@ Content Management Systems make it easy to create, update, and manage content. H
 
 There are many Cloudflare features that can be used for preventing such attacks, but they can also disrupt normal administrative processes such as logging in or uploading images. With proper configuration, you can protect your site from attacks without losing important functionality.
 
----
+***
 
 ## Stage One: Improve Site Security
 
@@ -29,13 +29,13 @@ The [WAF Managed Rulesets](/waf/managed-rules/) are pre-configured rulesets that
 
 While the feature to customize these managed rulesets required a paid plan, the [Free Cloudflare Managed Ruleset](https://blog.cloudflare.com/waf-for-everyone/#the-free-cloudflare-managed-ruleset) is automatically deployed on any new Cloudflare zone. This ruleset is specially designed to reduce false positives to a minimum across a very broad range of traffic types. As of today, the ruleset contains the following rules:
 
-- Log4J rules matching payloads in the URI and HTTP headers;
-- Shellshock rules;
-- Rules matching very common WordPress exploits;
+* Log4J rules matching payloads in the URI and HTTP headers;
+* Shellshock rules;
+* Rules matching very common WordPress exploits;
 
 Additionally, you can configure many aspects of the [OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/), including the anomaly threshold, paranoia level, and individual rules. One good practice is to ensure any rules related to XSS and SQL injection are enabled.
 
----
+***
 
 ## Stage Two: Restore Administrative Functions
 
@@ -56,12 +56,12 @@ Next, you can use this information to create a Skip Rule that excludes only the
 
 It is recommended to make this rule as tightly defined as possible, particularly without the additional protections listed below. While the exact content will be site-specific, some possible fields to use are:
 
-- IP Source Address
-- AS Num
-- Cookie
-- User Agent
+* IP Source Address
+* AS Num
+* Cookie
+* User Agent
 
-Make sure to apply the rule _only_ to the admin portion of your CMS. With WordPress for example, you can set a condition like '_URI Path contains /wp-admin/_'.
+Make sure to apply the rule *only* to the admin portion of your CMS. With WordPress for example, you can set a condition like '*URI Path contains /wp-admin/*'.
 
 Any of these fields can be spoofed, so this is not a security measure on its own. The purpose is to restore administrative functions only to conditions that may need them, while using other tools and features (including strong passwords on your CMS logins!) to secure access.
 
@@ -77,7 +77,7 @@ After this is complete, you will want to create a similar rule for any rulesets
 
 Make sure to set your Skip rules to be at a higher priority than the Execute rules.
 
----
+***
 
 ## Stage Three: Restrict Access
 
@@ -102,7 +102,7 @@ Do the following:
 3. [Enable mTLS](/ssl/client-certificates/enable-mtls/) by adding the correct host.
 4. In **SSL/TLS** > **Client Certificates**, select **Create mTLS Rule**.
 5. Under **When incoming requests match**, enter a value for the **URI Path** field to narrow the rule scope to the admin section, otherwise you will block your visitors from accessing the public content.
-6. Set the rule to _Block_ any requests made to your admin panel if the client certificate is not verified.
+6. Set the rule to *Block* any requests made to your admin panel if the client certificate is not verified.
 7. Select **Deploy**. This creates a WAF custom rule that checks all requests to the admin section for a valid client certificate.
 
 **Note:** If you have issues getting your certificate to verify, try accessing the page in a private window. If it works, the previous successful TLS state may be cached in your browser.
@@ -113,13 +113,13 @@ Rate limiting rules can help protect your login page from an attacker trying to
 
 Rate Limiting Rules are now available unmetered, on all plans. For more information, refer to the [developer documentation](/waf/rate-limiting-rules/).
 
----
+***
 
 ## Resources
 
-- [WAF Managed Rules](/waf/managed-rules/)
-- [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
-- [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
-- [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
-- [Client certificates](/ssl/client-certificates/)
-- [Rate limiting rules](/waf/rate-limiting-rules/)
+* [WAF Managed Rules](/waf/managed-rules/)
+* [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
+* [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
+* [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
+* [Client certificates](/ssl/client-certificates/)
+* [Rate limiting rules](/waf/rate-limiting-rules/)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
index a520969018400e2..7f619ce81d0c809 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Content Management System (CMS) support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
index b1a0aaaa794a451..72cf2b3808b2ec2 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
@@ -14,16 +14,16 @@ If you are using [Cloudflare's WordPress plugin](/automatic-platform-optimizatio
 
 ![Cloudflare's one-click configuration WordPress plugin.](~/assets/images/support/dash-optimize_wordpress.png)
 
-| **Setting**                 | **Value**                          |
-| --------------------------- | ---------------------------------- |
-| Caching level               | Standard                           |
-| Browser Cache TTL           | 4 hours                            |
-| Always Online               | On                                 |
-| Development Mode            | Disabled                           |
-| IPV6 Compatibility          | On                                 |
-| WebSockets                  | On                                 |
-| IP Geolocation              | On                                 |
-| Email Address Obfuscation   | On                                 |
-| Hotlink Protection          | Off                                |
-| Image optimization (Polish) | Off (unless on Pro or higher plan) |
-| Rocket Loader               | Off                                |
+| **Setting**                            | **Value**                          |
+| -------------------------------------- | ---------------------------------- |
+| Caching level                          | Standard                           |
+| Browser Cache TTL                      | 4 hours                            |
+| Always Online                          | On                                 |
+| Development Mode                       | Disabled                           |
+| IPV6 Compatibility                     | On                                 |
+| WebSockets                             | On                                 |
+| IP Geolocation                         | On                                 |
+| Email Address Obfuscation              | On                                 |
+| Hotlink Protection                     | Off                                |
+| Image optimization (Polish)            | Off (unless on Pro or higher plan) |
+| Rocket Loader                          | Off                                |
diff --git a/src/content/docs/support/third-party-software/forum-software/index.mdx b/src/content/docs/support/third-party-software/forum-software/index.mdx
index a3bd9f78a0ca9a2..6b8e3da66053d73 100644
--- a/src/content/docs/support/third-party-software/forum-software/index.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Forum Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
index 0669bac8222e466..1b3e0496d4d3820 100644
--- a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
@@ -13,14 +13,14 @@ Many widely used forum platforms are compatible with Cloudflare.
 
 These include:
 
-- [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
-- vBulletin
-- Xenforo
-- MyBB
+* [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
+* vBulletin
+* Xenforo
+* MyBB
 
 If you have a forum using these platforms, you can increase its speed and safety by adding Cloudflare.
 
----
+***
 
 ## Steps
 
diff --git a/src/content/docs/support/third-party-software/index.mdx b/src/content/docs/support/third-party-software/index.mdx
index 64ef43df834abe9..b79e7fe82f69cfc 100644
--- a/src/content/docs/support/third-party-software/index.mdx
+++ b/src/content/docs/support/third-party-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Third-Party Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/index.mdx b/src/content/docs/support/third-party-software/others/index.mdx
index d253e19c2efccb6..70b8ce2974da5f2 100644
--- a/src/content/docs/support/third-party-software/others/index.mdx
+++ b/src/content/docs/support/third-party-software/others/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Others support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
index a32fb2d6902eb8f..4cbb158f3f19295 100644
--- a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
+++ b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
@@ -13,7 +13,7 @@ Cloudflare launched Bandwidth Alliance in 2018 – a group of forward-looking cl
 
 Cloudflare customers using Azure can lower their egress bills between Cloudflare and Azure via [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/virtual-network/routing-preference-overview).
 
----
+***
 
 ## How to
 
@@ -31,9 +31,9 @@ To lower your data transfer costs from Azure and Cloudflare: 
 
 For additional details, refer to [Configure network routing preference for Azure Storage](https://docs.microsoft.com/en-us/azure/storage/common/configure-network-routing-preference?tabs=azure-portal) and [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/storage/common/network-routing-preference).
 
----
+***
 
 ## Related resources
 
-- [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
-- [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
+* [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
+* [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
index f5af757c7bdc872..3a30b097d7d9ced 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
@@ -26,7 +26,7 @@ This process will allow us to link your account inside our new support system.
 
 If you are a free account customer, you do not have access to this feature, but you can get assistance in many other ways:
 
-- By joining the conversation in our [Community forums](https://community.cloudflare.com/).
-- By joining our [Discord server](https://discord.cloudflare.com/).
-- By checking out our [Documentation](/).
-- By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
+* By joining the conversation in our [Community forums](https://community.cloudflare.com/).
+* By joining our [Discord server](https://discord.cloudflare.com/).
+* By checking out our [Documentation](/).
+* By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
index 2a8ae8a1e746734..a1ec1b9e2b99753 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
@@ -23,18 +23,18 @@ customers due to security and liability concerns.
 
 Use this table to quickly identify which troubleshooting method to use based on your issue:
 
-| Issue Type                     | Recommended Tool                                                                    | When to Use                                               |
-| ------------------------------ | ----------------------------------------------------------------------------------- | --------------------------------------------------------- |
-| Page not loading correctly     | [HAR file](#generate-a-har-file)                                                    | Visual issues, broken elements, slow page loads           |
-| JavaScript errors              | [Console log](#export-console-log)                                                  | CORS errors, scripts failing, browser-side errors         |
-| Protocol errors (QUIC/HTTP2)   | [NetLog dump](#capture-a-netlog-dump)                                               | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR`     |
-| Slow response times            | [curl (performance)](#performance)                                                  | Measuring latency, TLS handshake times                    |
-| HTTP errors (5xx, 4xx)         | [curl (HTTP errors)](#http-errors)                                                  | Determining if errors originate from Cloudflare or origin |
-| Caching issues                 | [curl (caching)](#caching)                                                          | Cache misses, stale content, cache headers                |
-| SSL/TLS certificate issues     | [curl (SSL/TLS)](#ssltls-certificates)                                              | Certificate errors, TLS version issues                    |
-| Connection timeouts/drops      | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr)                         | Network path issues, latency between hops                 |
-| Packet loss, connection resets | [Packet capture](#run-packet-captures)                                              | Layer 3/4 issues, SSL handshake failures                  |
-| Identifying serving location   | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests        |
+| Issue Type | Recommended Tool | When to Use |
+|------------|------------------|-------------|
+| Page not loading correctly | [HAR file](#generate-a-har-file) | Visual issues, broken elements, slow page loads |
+| JavaScript errors | [Console log](#export-console-log) | CORS errors, scripts failing, browser-side errors |
+| Protocol errors (QUIC/HTTP2) | [NetLog dump](#capture-a-netlog-dump) | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR` |
+| Slow response times | [curl (performance)](#performance) | Measuring latency, TLS handshake times |
+| HTTP errors (5xx, 4xx) | [curl (HTTP errors)](#http-errors) | Determining if errors originate from Cloudflare or origin |
+| Caching issues | [curl (caching)](#caching) | Cache misses, stale content, cache headers |
+| SSL/TLS certificate issues | [curl (SSL/TLS)](#ssltls-certificates) | Certificate errors, TLS version issues |
+| Connection timeouts/drops | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr) | Network path issues, latency between hops |
+| Packet loss, connection resets | [Packet capture](#run-packet-captures) | Layer 3/4 issues, SSL handshake failures |
+| Identifying serving location | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests |
 
 ---
 
@@ -53,7 +53,7 @@ A HTTP Archive (HAR) records all web browser requests including the request and
 :::caution
 
 A HAR file can include sensitive details such as passwords, payment
-information, and private keys.
+information, and private keys. 
 
 Remove sensitive information using a [HAR Sanitizer](https://har-sanitizer.pages.dev/).
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
index 75fdc9854918fee..2d097e0a9229ebd 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
@@ -6,6 +6,6 @@ products:
   - support
 ---
 
-Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability.
+Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability. 
 
 In instances where performance and reliability are in conflict, our systems are designed to prioritize a stable connection over a local one.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
index 256522df2decdc4..058aa4d051dd35b 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for General Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
index 738bb5db1983575..acc27ba05615fa5 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
@@ -8,18 +8,18 @@ products:
 
 This article may help if you are unable to receive transactional emails from Cloudflare. These types of email include:
 
-- email verification
-- forgot / reset password
-- any other type of automated notification generated by the Cloudflare dashboard
+* email verification
+* forgot / reset password
+* any other type of automated notification generated by the Cloudflare dashboard
 
 If you are expecting but not receiving these emails from Cloudflare, review the following.
 
 ## Causes
 
-- Your email address is incorrect or mistyped in the Cloudflare dashboard
-- Your email server or mailbox is not working
-- Your mail server or software is filtering or blocking messages from Cloudflare
-- Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
+* Your email address is incorrect or mistyped in the Cloudflare dashboard
+* Your email server or mailbox is not working
+* Your mail server or software is filtering or blocking messages from Cloudflare
+* Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
 
 ## Solution
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
index d7bbd6cd5dbd72d..3a81d5514edb8f9 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
@@ -6,17 +6,17 @@ products:
   - support
 ---
 
-Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare.
+Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare. 
 
 This appears to restrict data transfer to approximately 16 KB per connection, which renders most websites, including those of our customers, inaccessible or unusable for visitors from Russia.
 
 What to expect with your website:
 
-- This is not due to a misconfiguration of your Cloudflare settings.
+- This is not due to a misconfiguration of your Cloudflare settings. 
 - You will likely see a significant drop in traffic from users in Russia in your Cloudflare Analytics.
 - Your visitors in Russia may experience connection failures or sites that do not load properly.
-- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users.
+- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users. 
 
 If you are a Cloudflare enterprise customer, contact your account team for further assistance.
 
-For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/).
+For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/). 
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
index eeef01c3bebc4e4..37ece0e92f767e7 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
@@ -30,15 +30,15 @@ F5 session cookies can have arbitrary names but typically follow a specific form
 
 - Without encryption (trivially decoded to show origin server IP and port):
 
-  ```txt
-  BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
-  ```
+   ```txt
+   BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
+   ```
 
 - With encryption:
 
-  ```txt
-  BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
-  ```
+   ```txt
+   BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
+   ```
 
 #### 2. Test for the issue
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
index e47931dd17c1429..78c13a35999c2b2 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
@@ -9,46 +9,46 @@ products:
 
 Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
 
----
+***
 
 ## Disable Anti-bot modules
 
 Search engine crawlers' requests, when proxied through Cloudflare, can be blocked by anti-bot modules installed on your origin server. Try disabling any anti-bot modules to prevent your origin from blocking these requests.
 
----
+***
 
 ## Adjust Google and Bing crawl rates
 
 To optimize CDN performance, Google and Bing assign special crawl rates to websites that use CDN services in order. Special crawl rates do not negatively affect Search Engine Optimization (SEO) and Search Engine Results Pages (SERPs). To change your crawl rates for Bing and Google, follow the guides below:
 
-- Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
-- Change your Bing crawl rate via guidance from Bing’s documentation:
-  - [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
-  - [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
+* Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
+* Change your Bing crawl rate via guidance from Bing’s documentation:
+  * [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
+  * [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
 
----
+***
 
 ## Prevent crawl errors
 
 Review the following recommendations to prevent crawler errors:
 
-- Monitor the performance and availability of your website using a third-party tool:
-  - [StatusCake](http://www.statuscake.com/)
-  - [Pingdom](http://www.pingdom.com/)
-  - [Monitor.Us](http://www.monitor.us/)
-  - [Updown](https://updown.io/)
+* Monitor the performance and availability of your website using a third-party tool:
+  * [StatusCake](http://www.statuscake.com/)
+  * [Pingdom](http://www.pingdom.com/)
+  * [Monitor.Us](http://www.monitor.us/)
+  * [Updown](https://updown.io/)
 
-- Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
+* Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
 
   Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
 
-- Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
+* Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
 
-- Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
+* Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
 
 Google uses a [variety of User-Agents](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers) to crawl your website. You can [test your `robots.txt` via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
 
-- Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
+* Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
 
 `Disallow: /cdn-cgi/`
 
@@ -57,10 +57,10 @@ Google uses a [variety of User-Agents](https://developers.google.com/search/docs
 Errors for `cdn-cgi` do not impact site rankings.
 :::
 
-- Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943).
-- [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
+* Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
+* [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
 
----
+***
 
 ## Troubleshoot crawl errors
 
@@ -107,7 +107,7 @@ If the above troubleshooting steps do not resolve your crawl errors, follow the
 3. Click **Download** to export the list of errors as a `.csv` file.
 4. Provide the downloaded `.csv` file to Cloudflare support.
 
----
+***
 
 ## Related resources
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
index fd1f90255a9adde..f5f8373a02c6fde 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
@@ -15,7 +15,7 @@ For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
 
 ### Common use cases
 
-A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing.
+A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. 
 For example:
 
 - If the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
index b62f398bfdbf194..6f67fbca6e007e6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
@@ -21,4 +21,4 @@ If the client resends the request with the same credentials and the challenge re
 
 ### Cloudflare-specific information
 
-When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
+When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
index 5ab48647ac86db3..dc315ae8a719b89 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
@@ -19,4 +19,4 @@ For example, if a client requests content in a specific language or character se
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
+Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
index dd4f38c4aa51099..8083045fa4bc840 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
@@ -18,4 +18,4 @@ This error typically occurs in environments where a proxy server is used as an i
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
+Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
index f2e5da4a9064ce3..5b3115cc744996f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
@@ -21,4 +21,4 @@ This error typically occurs when a client fails to send a complete request withi
 
 If a `408` error occurs on a Cloudflare-powered site, it is most often being proxied from the origin. In these cases, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly.
 
-Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
+Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
index c0098ba91b387b4..87e414554c0bf55 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
@@ -22,4 +22,4 @@ This error typically happens with a `PUT` request when multiple clients are atte
 
 ### Cloudflare-specific information
 
-Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
+Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
index 17e6ee5ff4d269a..efdb6f72bdc5fe1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
@@ -23,4 +23,4 @@ This status is commonly applied to deprecated content, such as outdated pages or
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
+Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
index 47fe8d6954c39bd..2bbf1fafa9e5767 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
@@ -19,4 +19,4 @@ This status code can occur in various scenarios, such as when a client sends an
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
+Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
index 11efe2add1f92d6..6c46a3195a74a9e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
@@ -19,4 +19,4 @@ One common use case for the `412 Precondition Failed` status code is version con
 
 ### Cloudflare-specific information
 
-Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
+Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
index effc3539c4d9e6a..df0769a0b4bfd44 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
@@ -27,4 +27,4 @@ The upload limit for the Cloudflare API depends on your plan. If you exceed this
 
 Keep in mind, customers can reduce the **Maximum Upload Size** from the zone's **Network** page which can cause a `413`.
 
-If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
+If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
index c6b7876ce046cf3..d27ba07b657f86b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
@@ -19,4 +19,4 @@ For example, if a client is attempting a `GET` request with an unusually long UR
 
 ### Cloudflare-specific information
 
-Cloudflare will generate a `414` response if the URI length exceeds 32KB.
+Cloudflare will generate a `414` response if the URI length exceeds 32KB.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
index bf00d11dff44238..62c07d24e2e5251 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
@@ -19,4 +19,4 @@ This error can happen when a client requests a byte range outside the bounds of
 
 ### Cloudflare-specific information
 
-Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
+Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
index 711500dca7e9bae..5ad66dd00072ced 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
@@ -19,4 +19,4 @@ Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify
 
 ### Cloudflare-specific information
 
-Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
+Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
index 7d4d40af9d2bd76..995be774a343c75 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
@@ -32,3 +32,4 @@ Cloudflare applies rate limiting to requests for R2 managed public buckets acces
 #### Website end users
 
 Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
index 7a3792b883d662c..4d7d15261e11b47 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
@@ -19,4 +19,4 @@ This occurs when access to a resource is blocked due to court orders, copyright
 
 ### Cloudflare-specific information
 
-Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
+Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
index c2a6601666766b7..d9e3fe99f491207 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
@@ -15,7 +15,7 @@ products:
 
 ## Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), which can be useful to investigate HTTP Errors.
 
@@ -27,6 +27,7 @@ For a complete description of this error refer to the [Error 400](/support/troub
 
 For a complete description of this error refer to the [Error 401](/support/troubleshooting/http-status-codes/4xx-client-error/error-401/) page.
 
+
 ## 402 Payment Required
 
 The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231).
@@ -35,6 +36,7 @@ The `402 Payment Required` status code is reserved for future use and is not yet
 
 For a complete description of this error refer to the [Error 403](/support/troubleshooting/http-status-codes/4xx-client-error/error-403/) page.
 
+
 ## 404 Not Found
 
 For a complete description of this error refer to the [Error 404](/support/troubleshooting/http-status-codes/4xx-client-error/error-404/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
index 18167b8092b1b9b..36deca809c49e5c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
@@ -20,4 +20,4 @@ This error occurs when there are duplicate list items in a single operation to a
 
 ### Resolution
 
-You need to remove the duplicate item and try again.
+You need to remove the duplicate item and try again.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
index 107785e0dccf2ec..ec68460a428d719 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
@@ -20,4 +20,4 @@ This error occurs when the source URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the source URL.
+You need to use a shorter URL as the source URL.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
index c5307d8789975fb..687c3022a1391f4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
@@ -20,4 +20,4 @@ This error occurs when the target URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the target URL.
+You need to use a shorter URL as the target URL.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
index e061d57515adeb3..16221ebbff83170 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
index 16897ff09f53dfb..263401952d5dc31 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
+You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
index 1bc04c5dadad755..ba1cd6d9d14c953 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
@@ -17,4 +17,4 @@ This error occurs when you specify a URL redirect status code that is not suppor
 
 ### Resolution
 
-Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
+Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
index a68813f6502ebc5..5d066ea9c0d5f2c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve path suffix** option in a redir
 
 ### Resolution
 
-Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
+Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
index 085dc2ea7f596d2..343a60e375b1269 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect has an invalid scheme, w
 
 ### Resolution
 
-Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
index 172b34e6b076576..e037df5b8d6fdca 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a user info com
 
 ### Resolution
 
-You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
index a7ea0e0f82e50c6..e4399c78df33671 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect does not include an auth
 
 ### Resolution
 
-Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
+Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
index 371faef69c84269..36d65f8b2d2d541 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a port (for exa
 
 ### Resolution
 
-Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
index c0c9c3440aa4398..4cacdc75502b532 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve query string** option of a URL
 
 ### Resolution
 
-To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
+To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
index 1198b1552a6e89e..d6b879890b89165 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
@@ -20,4 +20,4 @@ This error occurs when different types of list items (such as IP addresses, host
 Remove the list items that do not apply to the list type. This means:
 
 - Removing IP addresses from a request to add items to a Bulk Redirect List.
-- Removing URL redirects from a request to add items to an IP list.
+- Removing URL redirects from a request to add items to an IP list.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
index 6c39cf94fee9dc4..158e45e84a4d659 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
@@ -21,4 +21,4 @@ Make sure you are adding the items to the correct list:
 
 - Custom lists with IP addresses (IP lists) can only contain IP addresses as list items.
 - Custom lists with hostnames can only contain hostnames as list items.
-- Bulk Redirect Lists can only contain URL redirects as list items.
+- Bulk Redirect Lists can only contain URL redirects as list items.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
index 7d137ba67522622..37a293ffd69b91e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
@@ -17,4 +17,4 @@ This error occurs when you have more than the maximum number of URL redirects wi
 
 ### Resolution
 
-Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
+Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
index 617ad8ff0c6f421..eb841ff74628814 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL of a URL redirect does not include a schem
 
 ### Resolution
 
-Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
+Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
index 1b97c64adc8da93..c47d1c3dccc0286 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
@@ -76,4 +76,4 @@ For a complete description of this error refer to the [Error 10059](/support/tro
 
 ## Error 10060: Missing scheme in redirect target URL
 
-For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
+For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
index 23d789e3acc15d7..ed56fe2d03d4b5c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
@@ -27,4 +27,4 @@ Cloudflare halted the request for one of the following reasons:
 
 - If an A record within your Cloudflare DNS app points to a [Cloudflare IP address](https://www.cloudflare.com/ips/), update the IP address to your origin web server IP address. Reach out to your hosting provider if you need help obtaining the origin IP address.
 - There is a reverse-proxy at your origin that sends the request back through the Cloudflare proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.
-- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
+- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
index 2c3f226dc6e792c..ccc795620204019 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
@@ -1,13 +1,13 @@
 ---
 pcx_content_type: troubleshooting
-title: Error 1002
+title: Error 1002 
 source: null
 description: Troubleshoot Cloudflare 1002 error code.
 products:
   - support
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 ## Error 1002: DNS points to Prohibited IP
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
index 23dc25e82509737..e1345953169f933 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
@@ -19,3 +19,4 @@ This error indicates that the host is not configured to serve web traffic.
 ### Resolution
 
 If the issue persists beyond five minutes, [contact Cloudflare Support](/support/contacting-cloudflare-support/).
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
index 3f1e6d6819b72b2..0927129b5cce7e1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
@@ -19,3 +19,4 @@ The owner of the website (for example, `example.com`) has banned the country or
 
 - If you are a site visitor, contact the site owner and ask them to allow your IP address.
 - If you are the site owner, ensure that the reported IP address is allowed under the [IP Access rules](/waf/tools/ip-access-rules/) security feature.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
index 8c178fd7a6ca6f1..1f107b8f72b7f05 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
@@ -22,5 +22,6 @@ Another common cause is connecting a custom domain to an R2 bucket, where the do
 - To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/).
 - To allow connecting to a R2 bucket with a custom domain, disable the [zone hold](/fundamentals/account/account-security/zone-holds/) feature on the custom domain target zone to resolve the 1014 error.
 - To allow connections to an R2 bucket whose zone is banned:
+
   - First, check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one).
   - Second, make sure that you have no unpaid invoice(s), as you will not be able to enable any new services until [any outstanding balance](/billing/manage/pay-invoices-overdue-balances/) is addressed. If this does not resolve the issue, contact your account team.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
index 27a7f8ca892a5ae..9b401eee437c5d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
@@ -27,4 +27,4 @@ For example, the following URI path rewrite expression is not valid:
 
 To fix the expression above, add a `/` prefix:
 
-`concat("/", lower(ip.src.country), http.request.uri.path)`
+`concat("/", lower(ip.src.country), http.request.uri.path)`
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
index a07128b006e1a78..8ca43a2009913cf 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
@@ -18,3 +18,4 @@ You are trying to modify an HTTP header that Request Header Transform Rules cann
 ### Resolution
 
 Make sure you are not trying to modify one of the [reserved HTTP request headers](/rules/transform/request-header-modification/#important-remarks).
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
index ca8eb720fb9b8ca..1468ee4c28b0408 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
@@ -57,3 +57,4 @@ To avoid exceeding memory limits:
 
 - [Error 1101](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1101/) - Workers JavaScript runtime exception
 - [Error 503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503/) - Service temporarily unavailable (can be caused by Workers CPU or memory limits)
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
index 064d799dd10135c..a31eb60f8fa2f99 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
@@ -32,6 +32,7 @@ For a complete description of this error refer to the [Error 1000](/support/trou
 
 For a complete description of this error refer to the [Error 1001](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/) page.
 
+
 ## Error 1002: DNS points to Prohibited IP
 
 For a complete description of this error refer to the [Error 1002: DNS points to Prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002/#error-1002-dns-points-to-prohibited-ip) page.
@@ -84,10 +85,12 @@ For a complete description of this error refer to the [Error 1014](/support/trou
 
 For a complete description of this error refer to the [Error 1015](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1015/) page.
 
+
 ## Error 1016: Origin DNS error
 
 For a complete description of this error refer to the [Error 1016](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016/) page.
 
+
 ## Error 1018: Could not find host
 
 For a complete description of this error refer to the [Error 1018](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1018/) page.
@@ -151,3 +154,4 @@ For a complete description of this error refer to the [Error 1104](/support/trou
 ## Error 1200: Cache connection limit
 
 For a complete description of this error refer to the [Error 1200](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1200/) page.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
index aa184c991eb318f..137fd47bdd00bcb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
@@ -18,4 +18,4 @@ Cloudflare Workers returns a `501` error when a request uses an HTTP method that
 
 ### Resolution
 
-- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
+- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
index 4f5ba4cb59b6c1d..f03079632ed610b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
@@ -52,10 +52,10 @@ If you are using Workers, check the Workers dashboard for error logs and resourc
 
 Use the error page content to determine whether a 503 was generated by Cloudflare or your origin server:
 
-| Signal                                                              | Interpretation                                                                                                                     |
-| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| Error page HTML contains `cloudflare` or `cloudflare-nginx`         | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
-| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly                                                                                             |
+| Signal | Interpretation |
+|--------|---------------|
+| Error page HTML contains `cloudflare` or `cloudflare-nginx` | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
+| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly |
 
 ### Cloudflare-generated 503
 
@@ -64,3 +64,4 @@ A Cloudflare-generated 503 indicates a connectivity issue in a Cloudflare data c
 ### Origin-generated 503
 
 If your origin generated a 503, check origin server logs for signs of overload: CPU/memory saturation, exhausted connection pool, or application-level maintenance mode.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
index c5e17a3afac58f5..1ce4d0ddda9a4a1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
@@ -68,3 +68,4 @@ To distinguish between the two, check the `CacheStatus` field in the same log re
 Do not conclude your origin returned a 5xx error solely because `OriginResponseStatus = 0`. Always check `CacheStatus` first to determine whether Cloudflare contacted the origin at all.
 
 :::
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
index a49d78dbb7cbe12..1759ae0d321392e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
@@ -21,6 +21,7 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 ### Resolution
 
 - Contact your hosting provider and share the [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist in troubleshooting these common causes:
+
   - [Cloudflare IP addresses](https://www.cloudflare.com/ips/) are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider allows **all Cloudflare IP ranges** (most common cause). You can use a [Cloudflare WAF Custom Rule](/waf/custom-rules/use-cases/block-by-geographical-location/) if you need to restrict traffic from geographical locations.
   - An overloaded or offline origin web server drops incoming requests.
   - [Keepalives](http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html) are disabled at the origin web server.
@@ -31,8 +32,9 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 
 - If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a `522` error. Consider using a [Route](/workers/configuration/routing/), targeting another hostname, or enabling the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) instead.
 
-- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`.
+- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`. 
 
 - If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before [contacting Cloudflare support](/support/contacting-cloudflare-support/):
+
   - An [MTR or traceroute](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#perform-a-traceroute) from your origin web server to a [Cloudflare IP address](http://www.cloudflare.com/ips) that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
   - Details from the hosting provider's investigation, such as pertinent logs or conversations with the hosting provider.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
index b075caaba321bfa..b67257eb3168ed7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
@@ -18,6 +18,7 @@ The error `524` occurs if the origin web server acknowledges (ACK) the resource
 
 Error `524` can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/) (or 6.5 seconds in the case of [Cloudflare Images](/images/)). This timeout cannot be adjusted.
 
+
 ### Resolution at your origin
 
 Here are the options we suggest to work around this issue:
@@ -30,7 +31,7 @@ Here are the options we suggest to work around this issue:
 
 :::note
 
-Logging request response time at your origin web server may help identify the cause of resource slowness.
+Logging request response time at your origin web server may help identify the cause of resource slowness. 
 Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as [Apache](http://httpd.apache.org/docs/current/mod/mod_log_config.html) or [Nginx](http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format).
 :::
 
@@ -41,7 +42,7 @@ Here are some other actions you can take on the Cloudflare side:
 - If you regularly run HTTP requests that take over 120 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
 - Enterprise customers can increase the `524` timeout up to 6,000 seconds:
   - If your content can be cached, you can create a [Cache Rule](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only) with the `Proxy Read Timeout` setting. The content needs to be cacheable for the rule to be triggered, but does not need to be cached.
-  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/).
+  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/). 
 
 :::note
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
index 1e57ec517869150..5278dcbd17ebc5f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
@@ -43,4 +43,4 @@ If `525` errors occur intermittently, review the origin web server error logs to
 
 - [Review the cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/) used by your server to ensure they are compatible with Cloudflare.
 
-- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
+- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
index 1bd602ef3df5764..d438cc1893edcbb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
@@ -46,7 +46,7 @@ To view Error Analytics:
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific Ray ID, which can be useful to investigate HTTP Errors.
 
@@ -72,6 +72,7 @@ For a complete description of this error refer to the [Error 503](/support/troub
 
 For a complete description of this error refer to the [Error 520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) page.
 
+
 ## Error 521: web server is down
 
 For a complete description of this error refer to the [Error 521](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) page.
@@ -84,14 +85,17 @@ For a complete description of this error refer to the [Error 522](/support/troub
 
 For a complete description of this error refer to the [Error 523](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) page.
 
+
 ## Error 524: a timeout occurred
 
 For a complete description of this error refer to the [Error 524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) page.
 
+
 ## Error 525: SSL handshake failed
 
 For a complete description of this error refer to the [Error 525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/) page.
 
+
 ## Error 526: invalid SSL certificate
 
 For a complete description of this error refer to the [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
index ec947473bacdc11..f0c29b1fb117d8a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
@@ -28,8 +28,9 @@ Reproduce the error and inspect response headers using one of:
 
 ## Using cf-error-type for diagnosis
 
-| `cf-error-type` prefix | Origin              | Next step                                              |
-| ---------------------- | ------------------- | ------------------------------------------------------ |
-| `1xxx`                 | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
-| `1101` / `1102`        | Workers runtime     | Check `wrangler tail` for the exception                |
-| `52x`                  | Origin connectivity | Check origin server is up and reachable                |
+| `cf-error-type` prefix | Origin | Next step |
+|---|---|---|
+| `1xxx` | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
+| `1101` / `1102` | Workers runtime | Check `wrangler tail` for the exception |
+| `52x` | Origin connectivity | Check origin server is up and reachable |
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
index 6c1c9d2be8a69d7..01c72d0bc87c34f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for HTTP Status Codes support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/index.mdx
index 03006375415d51d..d81e4565fde34b9 100644
--- a/src/content/docs/support/troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
index 09b614cc99e93e2..3594cec54c60318 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Restoring Visitor IPs support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
index e1a34f3e2f2c079..dd9d3148e61c91c 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
@@ -216,7 +216,7 @@ Use the [`ngx_http_realip_module` Nginx module](http://nginx.org/en/docs/http/ng
 
 ```
 #example IP address
-set_real_ip_from 192.0.2.1;
+set_real_ip_from 192.0.2.1; 
 
 #use any of the following two
 
@@ -463,7 +463,6 @@ For more details, refer to [Custom header original IP detection extension](https
 If you are running an application behind [Caddy](https://caddyserver.com/) that relies on the `X-Forwarded-For` header, you can configure Caddy to override the header with Cloudflare's [CF-Connecting-IP header](/fundamentals/reference/http-headers/#cf-connecting-ip).
 
 It is advised that you also only accept traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/); otherwise, the header could be spoofed. That's why, in the second example, we handle this as part of the Caddy configuration. Alternatively, you can handle this at the firewall level, which is usually easier to automate. If you already have a firewall or other measure in place to ensure this, your Caddyfile could look like this:
-
 ```txt title="Caddyfile"
 https://example.com {
     reverse_proxy localhost:8080 {
@@ -474,7 +473,6 @@ https://example.com {
 ```
 
 If you want Caddy to handle only accepting traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/), you can use a configuration like this one:
-
 ```txt title="Caddyfile"
 https://example.com {
     # Restrict access to Cloudflare IPs (https://www.cloudflare.com/ips/)
@@ -496,7 +494,6 @@ https://example.com {
     }
 }
 ```
-
 ---
 
 ## Related Resources
diff --git a/src/content/docs/tenant/how-to/index.mdx b/src/content/docs/tenant/how-to/index.mdx
index 5b478d437d47b4b..036aa6d32db9c09 100644
--- a/src/content/docs/tenant/how-to/index.mdx
+++ b/src/content/docs/tenant/how-to/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/tenant/index.mdx b/src/content/docs/tenant/index.mdx
index a9bea30e67a18fc..f669fc53278a372 100644
--- a/src/content/docs/tenant/index.mdx
+++ b/src/content/docs/tenant/index.mdx
@@ -19,7 +19,7 @@ These APIs are built into our Client v4 API library to provide a streamlined onb
 
 As you dive into the Tenant API, take advantage of the following resources:
 
-- [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
-- [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
-- [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
-- [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
+* [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
+* [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
+* [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
+* [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
diff --git a/src/content/docs/tenant/reference/index.mdx b/src/content/docs/tenant/reference/index.mdx
index cc579a35dcc72f4..ed9d4e28bbe4895 100644
--- a/src/content/docs/tenant/reference/index.mdx
+++ b/src/content/docs/tenant/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/terraform/advanced-topics/best-practices.mdx b/src/content/docs/terraform/advanced-topics/best-practices.mdx
index 8bc08838c5a7125..e3dd89c7e78f2e0 100644
--- a/src/content/docs/terraform/advanced-topics/best-practices.mdx
+++ b/src/content/docs/terraform/advanced-topics/best-practices.mdx
@@ -189,8 +189,10 @@ Using modules also increases the difficulty of debugging or reproducing issues a
 
 :::caution
 
+
 This advice also applies to [Terraform dynamic blocks](https://www.terraform.io/language/expressions/dynamic-blocks) that allow you to do logic in your HCL. Since these dynamic blocks are always evaluated, you can get yourself into situations where you have logic bugs in your configuration (and making the end result unreproducible).
 
+
 :::
 
 ## Migrate resources into Terraform
diff --git a/src/content/docs/terraform/how-to/create-partial-zone.mdx b/src/content/docs/terraform/how-to/create-partial-zone.mdx
index b6532b8ca83d6a4..7ddc5bbf8335cb9 100644
--- a/src/content/docs/terraform/how-to/create-partial-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-partial-zone.mdx
@@ -39,7 +39,6 @@ resource "cloudflare_zone" "subdomain_example_com" {
 ```
 
 Then, in a new Terraform plan and apply cycle, upgrade the zone to a Business plan or higher:
-
 ```hcl
 resource "cloudflare_zone_subscription" "example_zone_subscription" {
   zone_id = cloudflare_zone.subdomain_example_com.id
@@ -73,4 +72,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Partial zone setup](/dns/zone-setups/partial-setup/)
 - [Convert a full zone to partial](/dns/zone-setups/conversions/convert-full-to-partial/)
-- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
+- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
\ No newline at end of file
diff --git a/src/content/docs/terraform/how-to/create-secondary-zone.mdx b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
index ab90c9a7bf683c7..df90ad68810ec8a 100644
--- a/src/content/docs/terraform/how-to/create-secondary-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
@@ -13,9 +13,7 @@ products:
 ---
 
 A [subdomain zone](/dns/zone-setups/subdomain-setup/) lets you manage a subdomain in a separate Cloudflare zone from the parent domain. This is useful for access control and team management. This guide shows how to automate the setup using the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs). It is only available for Enterprise accounts
-
 > NOTE: subdomain setup is only available for Enterprise accounts
-
 ## Prerequisites
 
 - Terraform installed. Refer to [Get started](/terraform/installing/).
@@ -45,4 +43,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Subdomain setup](/dns/zone-setups/subdomain-setup/)
 - [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
-- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
+- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
\ No newline at end of file
diff --git a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
index 4fe8686bb0585da..2ab6af754503c16 100644
--- a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
+++ b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
@@ -24,4 +24,4 @@ Use this:
 
 ```txt "zones[0]"
 zone_id = data.cloudflare_zones.example_com.zones[0].id`
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/terraform/tutorial/index.mdx b/src/content/docs/terraform/tutorial/index.mdx
index 0a16482753a93c7..9eb9b90d3aaf527 100644
--- a/src/content/docs/terraform/tutorial/index.mdx
+++ b/src/content/docs/terraform/tutorial/index.mdx
@@ -10,41 +10,41 @@ products:
 
 Before you begin, [install Terraform](/terraform/installing/). Each tutorial builds on the previous, so you should complete the tutorials in the order shown below.
 
-:::note
+:::note 
 If you are upgrading from v4, review the [migration guide](https://github.com/cloudflare/terraform-provider-cloudflare/blob/main/docs/guides/version-5-upgrade.md) for breaking changes.
 :::
 
 ## [1 – Initialize Terraform](/terraform/tutorial/initialize-terraform/)
 
-- Brief introduction.
-- Introduction of `terraform init`, `plan`, `apply`, and `show`.
-- Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
+* Brief introduction.
+* Introduction of `terraform init`, `plan`, `apply`, and `show`.
+* Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
 
 ## [2 – Track your history](/terraform/tutorial/track-history/)
 
-- Store Cloudflare configuration in source control.
+* Store Cloudflare configuration in source control.
 
 ## [3 – Configure HTTPS settings](/terraform/tutorial/configure-https-settings/)
 
-- Modify zone settings.
-- Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
+* Modify zone settings.
+* Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
 
 ## [4 – Improve performance and reliability](/terraform/tutorial/use-load-balancing/)
 
-- Add load balancing rules.
-- Resources covered:
-  - [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
-  - [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
-  - [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
+* Add load balancing rules.
+* Resources covered:
+  * [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
+  * [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
+  * [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
 
 ## [5 – Add exceptions with page rules](/terraform/tutorial/add-page-rules/)
 
-- Add page rule.
-- Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
-- Increase security level for a specific URL: `/expensive-db-call`.
-- Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
+* Add page rule.
+* Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
+* Increase security level for a specific URL: `/expensive-db-call`.
+* Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
 
 ## [6 – Revert configuration](/terraform/tutorial/revert-configuration/)
 
-- Review change history.
-- Roll back changes.
+* Review change history.
+* Roll back changes.
diff --git a/src/content/docs/time-services/index.mdx b/src/content/docs/time-services/index.mdx
index e0533cac714f018..28cf018d1d9c55a 100644
--- a/src/content/docs/time-services/index.mdx
+++ b/src/content/docs/time-services/index.mdx
@@ -12,7 +12,7 @@ products:
 description: Synchronize time with Cloudflare NTP, NTS, and Roughtime.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn more about Cloudflare’s suite of time services.
 
diff --git a/src/content/docs/time-services/roughtime/index.mdx b/src/content/docs/time-services/roughtime/index.mdx
index fa744d4dd0b4954..c63fcd5c61e6ed3 100644
--- a/src/content/docs/time-services/roughtime/index.mdx
+++ b/src/content/docs/time-services/roughtime/index.mdx
@@ -16,7 +16,7 @@ Endpoints on the Internet often synchronize their clocks using the [Network Time
 
 As a result, a man-in-the-middle attacker can easily influence a victim’s clock. By moving them back in time, the attacker can, for example, force a victim to accept an expired (and possibly compromised) TLS certificate or session ticket.
 
-For many applications, _precise_ network time is not essential. It is sufficient to have _accurate_ time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
+For many applications, *precise* network time is not essential. It is sufficient to have *accurate* time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
 
 ## Next steps
 
diff --git a/src/content/docs/time-services/roughtime/recipes.mdx b/src/content/docs/time-services/roughtime/recipes.mdx
index c7873f7d93f6904..47cfdd6f2bd8e21 100644
--- a/src/content/docs/time-services/roughtime/recipes.mdx
+++ b/src/content/docs/time-services/roughtime/recipes.mdx
@@ -21,28 +21,28 @@ formatted as a JSON object. For example:
 
 ```json
 {
-	"servers": [
-		{
-			"name": "Cloudflare-Roughtime-2",
-			"publicKeyType": "ed25519",
-			"publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
-			"addresses": [
-				{
-					"protocol": "udp",
-					"address": "roughtime.cloudflare.com:2003"
-				}
-			]
-		}
-	]
+  "servers": [
+    {
+      "name": "Cloudflare-Roughtime-2",
+      "publicKeyType": "ed25519",
+      "publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
+      "addresses": [
+        {
+          "protocol": "udp",
+          "address": "roughtime.cloudflare.com:2003"
+        }
+      ]
+    }
+  ]
 }
 ```
 
-It includes each server's _root public key_. When the server starts, it
-generates an _online_ public/secret key pair. The root secret key is used to create a _delegation_ for the online public key and the online secret key is used to sign the response.
+It includes each server's *root public key*. When the server starts, it
+generates an *online* public/secret key pair. The root secret key is used to create a *delegation* for the online public key and the online secret key is used to sign the response.
 
 The delegation serves the same function as a traditional [X.509 certificate](https://en.wikipedia.org/wiki/X.509) on the web. The client first uses the root public key to verify the delegation, then uses the online public key to verify the response.
 
-Because the response is _auditable_, the protocol makes each client accountable to provide accurate time.
+Because the response is *auditable*, the protocol makes each client accountable to provide accurate time.
 
 The configuration also encodes the type of signature algorithm used by the
 server (currently only [Ed25519](https://en.wikipedia.org/wiki/EdDSA) is supported). Lastly, the configuration contains a list of addresses where the service can be reached and which transport protocol to use to reach them (currently only UDP is supported).
diff --git a/src/content/docs/time-services/tos.mdx b/src/content/docs/time-services/tos.mdx
index 3045d87449c98de..919e1a6c1d5e131 100644
--- a/src/content/docs/time-services/tos.mdx
+++ b/src/content/docs/time-services/tos.mdx
@@ -8,4 +8,4 @@ products:
 description: Cloudflare Time Services terms of use.
 ---
 
-By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
+By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
\ No newline at end of file
diff --git a/src/content/docs/tunnel/advanced/origin-parameters.mdx b/src/content/docs/tunnel/advanced/origin-parameters.mdx
index 8b0a1173bb017e7..765569e743882e5 100644
--- a/src/content/docs/tunnel/advanced/origin-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/origin-parameters.mdx
@@ -13,13 +13,11 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/origin-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/tunnel/advanced/local-management/configuration-file/",
-		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-		validatingJwtURL:
-			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
-	}}
+  file="tunnel/origin-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
+    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
+  }}
 />
diff --git a/src/content/docs/tunnel/advanced/run-parameters.mdx b/src/content/docs/tunnel/advanced/run-parameters.mdx
index 61f30d9abf493ba..3024141c055de62 100644
--- a/src/content/docs/tunnel/advanced/run-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/run-parameters.mdx
@@ -13,17 +13,15 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/run-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/tunnel/advanced/local-management/configuration-file/",
-		metricsURL: "/tunnel/monitoring/#metrics",
-		usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
-		tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
-		tunnelPermissionsURL:
-			"/tunnel/advanced/local-management/tunnel-permissions/",
-		createRemoteTunnelURL: "/tunnel/get-started/",
-		faqURL: "/tunnel/troubleshooting/",
-	}}
+  file="tunnel/run-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
+    metricsURL: "/tunnel/monitoring/#metrics",
+    usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
+    tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
+    tunnelPermissionsURL: "/tunnel/advanced/local-management/tunnel-permissions/",
+    createRemoteTunnelURL: "/tunnel/get-started/",
+    faqURL: "/tunnel/troubleshooting/"
+  }}
 />
diff --git a/src/content/docs/tunnel/changelog.mdx b/src/content/docs/tunnel/changelog.mdx
index dd0771082a7b9ac..9a0b8f86b225617 100644
--- a/src/content/docs/tunnel/changelog.mdx
+++ b/src/content/docs/tunnel/changelog.mdx
@@ -12,4 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
+<ProductChangelog
+	product="tunnel"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
\ No newline at end of file
diff --git a/src/content/docs/tunnel/deployment-guides/terraform.mdx b/src/content/docs/tunnel/deployment-guides/terraform.mdx
index cc28a315060b536..13890c8c111c1c4 100644
--- a/src/content/docs/tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/tunnel/deployment-guides/terraform.mdx
@@ -80,6 +80,7 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
+
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/tunnel/downloads/system-requirements.mdx b/src/content/docs/tunnel/downloads/system-requirements.mdx
index df9a49384ea6c6e..252a3704e2bda8c 100644
--- a/src/content/docs/tunnel/downloads/system-requirements.mdx
+++ b/src/content/docs/tunnel/downloads/system-requirements.mdx
@@ -17,11 +17,7 @@ import { Render, TunnelCalculator } from "~/components";
 Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availability) on two dedicated hosts per location with a minimum of 4 GB RAM and 4 CPU cores. Allocate 50,000 ports per host.
 
 ## Port configuration
-
-<Render
-	file="tunnel/availability/port-configuration"
-	product="cloudflare-one"
-/>
+<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
 
 ## ulimits (Linux and macOS)
 
@@ -30,7 +26,6 @@ Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availabil
 ## Capacity calculator
 
 To estimate tunnel capacity requirements for your deployment:
-
 1. Use the [metrics endpoint](/tunnel/monitoring/#cloudflared-metrics) to measure `cloudflared_tcp_total_sessions` and `cloudflared_udp_total_sessions`.
 2. Compute the average **TCP requests per second** by dividing `cloudflared_tcp_total_sessions` by total time.
 3. Compute the average **Non-DNS UDP requests per second** by dividing `cloudflared_udp_total_sessions` by total time.
diff --git a/src/content/docs/tunnel/troubleshooting.mdx b/src/content/docs/tunnel/troubleshooting.mdx
index 06fba9a65a218a4..0c02d1a8ecf4b9a 100644
--- a/src/content/docs/tunnel/troubleshooting.mdx
+++ b/src/content/docs/tunnel/troubleshooting.mdx
@@ -121,7 +121,6 @@ As a quick test, run:
 ```sh
 curl -v https://region1.v2.argotunnel.com:7844
 ```
-
 If the connection hangs, traffic is being dropped between your host and Cloudflare.
 
 To test if `cloudflared` can connect on port `7844`, run:
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
index b2a3eaa4e14958f..51b265f76e5f1f0 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
@@ -7,6 +7,7 @@ products:
 sidebar:
   order: 4
   label: Any Hostname
+
 ---
 
 The Any Hostname feature removes the requirement to specify hostnames during widget creation, allowing widgets to function on any domain.
@@ -23,37 +24,31 @@ When using the Any Hostname feature, it is essential to implement additional val
 
 ```js title="Example response"
 async function validateTurnstileWithHostname(token, expectedHostnames = []) {
-	const response = await fetch(
-		"https://challenges.cloudflare.com/turnstile/v0/siteverify",
-		{
-			method: "POST",
-			headers: { "Content-Type": "application/json" },
-			body: JSON.stringify({
-				secret: process.env.TURNSTILE_SECRET,
-				response: token,
-			}),
-		},
-	);
-
-	const result = await response.json();
-
-	if (!result.success) {
-		return { valid: false, error: "Token validation failed" };
-	}
-
-	// Additional hostname validation when using Any Hostname
-	if (
-		expectedHostnames.length > 0 &&
-		!expectedHostnames.includes(result.hostname)
-	) {
-		return {
-			valid: false,
-			error: "Hostname not in allowed list",
-			hostname: result.hostname,
-		};
-	}
-
-	return { valid: true, data: result };
+  const response = await fetch('https://challenges.cloudflare.com/turnstile/v0/siteverify', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      secret: process.env.TURNSTILE_SECRET,
+      response: token
+    })
+  });
+
+  const result = await response.json();
+
+  if (!result.success) {
+    return { valid: false, error: 'Token validation failed' };
+  }
+
+  // Additional hostname validation when using Any Hostname
+  if (expectedHostnames.length > 0 && !expectedHostnames.includes(result.hostname)) {
+    return { 
+      valid: false, 
+      error: 'Hostname not in allowed list',
+      hostname: result.hostname 
+    };
+  }
+
+  return { valid: true, data: result };
 }
 ```
 
@@ -63,12 +58,10 @@ Use `action` and `cData` parameters to track widget usage sources.
 
 ```html
 <!-- Widget with tracking information -->
-<div
-	class="cf-turnstile"
-	data-sitekey="your-site-key"
-	data-action="customer-portal"
-	data-cdata="tenant-123"
-></div>
+<div class="cf-turnstile" 
+     data-sitekey="your-site-key"
+     data-action="customer-portal"
+     data-cdata="tenant-123"></div>
 ```
 
 ---
@@ -80,4 +73,4 @@ The Any Hostname feature is particularly valuable for customers with:
 - Large domain portfolios with many domains to manage individually.
 - Dynamic subdomain creation and frequently create subdomains or customer-specific domains.
 - Multi-tenant applications such as SaaS platforms serving multiple customer domains.
-- Development environments that test across various staging and development domains.
+- Development environments that test across various staging and development domains.
\ No newline at end of file
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
index a54d5062f8d33e7..2ec95bf7163dc6f 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
@@ -6,9 +6,10 @@ products:
   - turnstile
 sidebar:
   order: 2
+
 ---
 
-import { DashButton, Steps, Tabs, TabItem, Details } from "~/components";
+import { DashButton, Steps, Tabs, TabItem, Details } from "~/components"
 
 Hostname management controls where your Turnstile widgets can be used by specifying which domains are authorized to load and execute your widgets. This security measure prevents unauthorized use of your widgets on domains that you do not control.
 
@@ -35,7 +36,7 @@ The following formats are not valid and will not be accepted:
 - Schemes such as `http://example.com` or `https://example.com`
 - Ports such as `example.com:443` or `subdomain.example.com:8080`
 - Paths such as `example.com/path` or `subdomain.example.com/login`
-  :::
+:::
 
 ### Subdomain behavior
 
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
index c8b59dade309ca5..eaa623056629f2a 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
@@ -8,6 +8,7 @@ tags:
   - Cookies
 sidebar:
   order: 3
+
 ---
 
 [Pre-clearance](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) allows Turnstile to issue clearance cookies that can be used across your Cloudflare-protected domains. This feature requires specific hostname configuration for proper functionality.
@@ -16,18 +17,18 @@ sidebar:
 
 For pre-clearance to work correctly, you must:
 
-1. Use a registered Cloudflare zone.
-
-   The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones.
-
-2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance.
+1. Use a registered Cloudflare zone. 
 
-   The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile.
+    The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones. 
 
-   For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`.
+2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance. 
+    
+    The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile. 
+    
+    For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`. 
 
 ## Validation
 
 The clearance cookie `cf_clearance` will only be accepted on domains that match the widget's configured hostnames, are registered as zones in your Cloudflare account, and have challenges enabled through Cloudflare's security settings.
 
-If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
+If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
\ No newline at end of file
diff --git a/src/content/docs/turnstile/additional-configuration/index.mdx b/src/content/docs/turnstile/additional-configuration/index.mdx
index c1dd255c43c229e..fa53423d1ca145e 100644
--- a/src/content/docs/turnstile/additional-configuration/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile's additional configurations:
 
diff --git a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
index ff23f12fc0c683d..f4882feb0c77f50 100644
--- a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
+++ b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile
 sidebar:
   order: 3
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/turnstile/concepts/challenges.mdx b/src/content/docs/turnstile/concepts/challenges.mdx
index 2049cf0d9334a17..fa67c9f121a081a 100644
--- a/src/content/docs/turnstile/concepts/challenges.mdx
+++ b/src/content/docs/turnstile/concepts/challenges.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /cloudflare-challenges/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/turnstile/concepts/index.mdx b/src/content/docs/turnstile/concepts/index.mdx
index f8bdd001acb61db..4545231c8047916 100644
--- a/src/content/docs/turnstile/concepts/index.mdx
+++ b/src/content/docs/turnstile/concepts/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile's concepts:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/extensions/google-firebase.mdx b/src/content/docs/turnstile/extensions/google-firebase.mdx
index 7ecd2d24ede91af..2456c9d7c189b62 100644
--- a/src/content/docs/turnstile/extensions/google-firebase.mdx
+++ b/src/content/docs/turnstile/extensions/google-firebase.mdx
@@ -10,9 +10,10 @@ tags:
 sidebar:
   order: 2
   label: Google Firebase
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 Turnstile is [available as an extension](https://extensions.dev/extensions/cloudflare/cloudflare-turnstile-app-check-provider) with [Google's Firebase](https://firebase.google.com/) platform as an [App Check](https://firebase.google.com/docs/app-check) provider. You can leverage Cloudflare Turnstile's bot detection and challenge capabilities to ensure that requests to your Firebase backend services are verified and only authentic human visitors can interact with your application.
 
@@ -118,25 +119,25 @@ const expressApp = express();
 const firebaseApp = initializeApp();
 
 const appCheckVerification = async (req, res, next) => {
-	const appCheckToken = req.header("X-Firebase-AppCheck");
+    const appCheckToken = req.header("X-Firebase-AppCheck");
 
-	if (!appCheckToken) {
-		res.status(401);
-		return next("Unauthorized");
-	}
+    if (!appCheckToken) {
+        res.status(401);
+        return next("Unauthorized");
+    }
 
-	try {
-		const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
+    try {
+        const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
 
-		// If verifyToken() succeeds, continue with the next middleware function in the stack.
-		return next();
-	} catch (err) {
-		res.status(401);
-		return next("Unauthorized");
-	}
-};
+        // If verifyToken() succeeds, continue with the next middleware function in the stack.
+        return next();
+    } catch (err) {
+        res.status(401);
+        return next("Unauthorized");
+    }
+}
 
 expressApp.get("/yourApiEndpoint", [appCheckVerification], (req, res) => {
-	// Handle request.
+    // Handle request.
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/extensions/index.mdx b/src/content/docs/turnstile/extensions/index.mdx
index e7d4e7afeae3a2f..2649807908e1165 100644
--- a/src/content/docs/turnstile/extensions/index.mdx
+++ b/src/content/docs/turnstile/extensions/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile extensions:
 
diff --git a/src/content/docs/turnstile/extensions/pages-plugin.mdx b/src/content/docs/turnstile/extensions/pages-plugin.mdx
index 963a6bb4dee2004..e3a41748a59f3ca 100644
--- a/src/content/docs/turnstile/extensions/pages-plugin.mdx
+++ b/src/content/docs/turnstile/extensions/pages-plugin.mdx
@@ -7,4 +7,5 @@ title: Pages Plugin
 external_link: /pages/functions/plugins/turnstile/
 sidebar:
   order: 1
+
 ---
diff --git a/src/content/docs/turnstile/extensions/waiting-room.mdx b/src/content/docs/turnstile/extensions/waiting-room.mdx
index 1153676741e4dc1..474416b1df638c3 100644
--- a/src/content/docs/turnstile/extensions/waiting-room.mdx
+++ b/src/content/docs/turnstile/extensions/waiting-room.mdx
@@ -7,4 +7,5 @@ title: Waiting Room Analytics
 external_link: /waiting-room/waiting-room-analytics/#turnstile-widget-traffic
 sidebar:
   order: 3
+
 ---
diff --git a/src/content/docs/turnstile/get-started/widget-management/api.mdx b/src/content/docs/turnstile/get-started/widget-management/api.mdx
index 9c0738b7d0d5cda..4342df29d7ee58e 100644
--- a/src/content/docs/turnstile/get-started/widget-management/api.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/api.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - REST API
 sidebar:
-  order: 2
-  label: API
+    order: 2
+    label: API
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Use the [Cloudflare API](/api/resources/turnstile/) for programmatic widget management and automation.
 
@@ -25,44 +25,47 @@ Before you begin, you must have:
 ### Create a widget via the API
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets"
-	method="POST"
-	json={{
-		domains: ["example.com"],
-		mode: "managed",
-		name: "My Example Turnstile Widget",
-	}}
+  path="/accounts/{account_id}/challenges/widgets"
+  method="POST"
+  json={{
+    domains: ["example.com"],
+    mode: "managed",
+    name: "My Example Turnstile Widget",
+  }}
 />
 
 ### Manage widgets via the API
 
-<APIRequest path="/accounts/{account_id}/challenges/widgets" method="GET" />
-
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="GET"
+  path="/accounts/{account_id}/challenges/widgets"
+  method="GET"
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="PUT"
-	json={{
-		domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
-		mode: "invisible",
-		name: "blog.cloudflare.com login form",
-		clearance_level: "interactive",
-	}}
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="GET"
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
-	method="POST"
-	json={{
-		invalidate_immediately: false,
-	}}
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="PUT"
+  json={{
+    domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
+    mode: "invisible",
+    name: "blog.cloudflare.com login form",
+    clearance_level: "interactive",
+  }}
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="DELETE"
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
+  method="POST"
+  json={{
+    invalidate_immediately: false,
+  }}
 />
+
+<APIRequest
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="DELETE"
+/>
\ No newline at end of file
diff --git a/src/content/docs/turnstile/get-started/widget-management/index.mdx b/src/content/docs/turnstile/get-started/widget-management/index.mdx
index 70a4816c948455b..bcb9b3c62a9e45f 100644
--- a/src/content/docs/turnstile/get-started/widget-management/index.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about managing Turnstile widgets:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
index 22a01e0fa0389de..d39317f90ca363c 100644
--- a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - Terraform
 sidebar:
-  order: 3
-  label: Terraform
+    order: 3
+    label: Terraform
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Manage Turnstile widgets as code using Terraform for version control and automated deployments.
 
@@ -153,7 +153,7 @@ locals {
 
 resource "cloudflare_turnstile_widget" "app_widget" {
   for_each = local.environments
-
+  
   account_id = var.account_id
   name       = "App Widget - ${each.key}"
   domains    = each.value.domains
@@ -195,4 +195,4 @@ cf-terraforming generate \
 ```shell title="Import existing widget"
 terraform import cloudflare_turnstile_widget.existing_widget \
   $ACCOUNT_ID/$WIDGET_SITEKEY
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/migration/hcaptcha.mdx b/src/content/docs/turnstile/migration/hcaptcha.mdx
index bbe32fd8f917c8d..87ff8fe69db29c4 100644
--- a/src/content/docs/turnstile/migration/hcaptcha.mdx
+++ b/src/content/docs/turnstile/migration/hcaptcha.mdx
@@ -46,7 +46,7 @@ Turnstile supports:
 
 - the `render()` call
 - hCaptcha invisible mode with the `execute()` call
-  :::
+:::
 
 ## Server-side integration
 
diff --git a/src/content/docs/turnstile/reference/index.mdx b/src/content/docs/turnstile/reference/index.mdx
index 0f952082dda1ea1..ed8c7d7668f0cc2 100644
--- a/src/content/docs/turnstile/reference/index.mdx
+++ b/src/content/docs/turnstile/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile:
 
diff --git a/src/content/docs/turnstile/reference/supported-browsers.mdx b/src/content/docs/turnstile/reference/supported-browsers.mdx
index 837dbda385d3c26..28bdb4eb396bfad 100644
--- a/src/content/docs/turnstile/reference/supported-browsers.mdx
+++ b/src/content/docs/turnstile/reference/supported-browsers.mdx
@@ -7,4 +7,5 @@ title: Supported browsers
 external_link: /cloudflare-challenges/reference/supported-browsers/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/turnstile/reference/supported-languages.mdx b/src/content/docs/turnstile/reference/supported-languages.mdx
index 8263d260812b2fd..f0338658d106a98 100644
--- a/src/content/docs/turnstile/reference/supported-languages.mdx
+++ b/src/content/docs/turnstile/reference/supported-languages.mdx
@@ -8,6 +8,7 @@ tags:
   - Localization
 sidebar:
   order: 3
+
 ---
 
 Turnstile supports `auto` (default), which uses the visitor's browser language if it is supported. You can also explicitly set the widget's language using the [client-side configuration attribute](/turnstile/get-started/client-side-rendering/#configurations) to one listed on the table below:
diff --git a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
index 8b37a576667565e..12e1785bd51cc86 100644
--- a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
+++ b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
@@ -7,4 +7,5 @@ title: Turnstile Privacy Addendum
 external_link: https://www.cloudflare.com/turnstile-privacy-policy/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
index b38f8de49356b2c..6a51837058ce17d 100644
--- a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
@@ -7,4 +7,5 @@ title: Challenge solve issues
 external_link: /cloudflare-challenges/troubleshooting/challenge-solve-issues/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
index e0c9bc9938840cc..fd6c9090b063095 100644
--- a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
@@ -9,21 +9,22 @@ tags:
   - JavaScript
 sidebar:
   order: 3
+
 ---
 
 import { Tabs, TabItem } from "~/components";
 
-There are instances where Turnstile may encounter problems, invoking the `error-callback`.
+There are instances where Turnstile may encounter problems, invoking the `error-callback`. 
 
-These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures.
+These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures. 
 
-When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues.
+When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues. 
 
 Refer to the [Error codes](/turnstile/troubleshooting/client-side-errors/error-codes/) for troubleshooting guidance to address specific error conditions.
 
 ## Error handling
 
-The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur.
+The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur. 
 
 This callback mechanism gives you complete control over how errors are presented to visitors and allows you to implement custom recovery strategies tailored to your application's needs.
 
@@ -57,30 +58,28 @@ An error callback will retrieve an error code as its first parameter. This error
 
 ```js wrap
 function handleTurnstileError(errorCode) {
-	const errorFamily = Math.floor(errorCode / 1000);
-
-	switch (errorFamily) {
-		case 100:
-			showMessage("Please refresh the page and try again.");
-			break;
-		case 110:
-			showMessage("Configuration error. Please contact support.");
-			break;
-		case 300:
-		case 600:
-			showMessage(
-				"Security check failed. Please try refreshing or using a different browser.",
-			);
-			break;
-		default:
-			showMessage("An unexpected error occurred. Please try again.");
-	}
+  const errorFamily = Math.floor(errorCode / 1000);
+  
+  switch(errorFamily) {
+    case 100:
+      showMessage('Please refresh the page and try again.');
+      break;
+    case 110:
+      showMessage('Configuration error. Please contact support.');
+      break;
+    case 300:
+    case 600:
+      showMessage('Security check failed. Please try refreshing or using a different browser.');
+      break;
+    default:
+      showMessage('An unexpected error occurred. Please try again.');
+  }
 }
 ```
 
 ## Retry
 
-By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention.
+By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention. 
 
 This automatic retry mechanism is useful for [mobile visitors](/turnstile/get-started/mobile-implementation/) who may experience intermittent connectivity or visitors on networks with occasional stability issues.
 
@@ -89,34 +88,34 @@ When subsequent failures due to retries are observed, the error callback can be
 ```js wrap
 let retryCount = 0;
 
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	"error-callback": function (errorCode) {
-		retryCount++;
-
-		if (retryCount <= 2) {
-			console.log(`Turnstile retry attempt ${retryCount}`);
-			return false; // Let Turnstile handle the retry
-		} else {
-			showPersistentErrorMessage(errorCode);
-			return true; // We'll handle it from here
-		}
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  'error-callback': function(errorCode) {
+    retryCount++;
+    
+    if (retryCount <= 2) {
+      console.log(`Turnstile retry attempt ${retryCount}`);
+      return false; // Let Turnstile handle the retry
+    } else {
+      showPersistentErrorMessage(errorCode);
+      return true; // We'll handle it from here
+    }
+  }
 });
 ```
 
 You can adjust the retry behavior by setting the retry value to `never` instead of the default `auto`. This will result in Turnstile not automatically retrying, giving you control over when and how recovery attempts are made. If there is any issue or error verifying the visitor, the widget will not retry and will remain in the respective failure state until you take manual action.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	retry: "never",
-	"error-callback": function (errorCode) {
-		// You control all retry logic
-		setTimeout(() => {
-			turnstile.reset("#my-widget");
-		}, 3000);
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  retry: 'never',
+  'error-callback': function(errorCode) {
+    // You control all retry logic
+    setTimeout(() => {
+      turnstile.reset('#my-widget');
+    }, 3000);
+  }
 });
 ```
 
@@ -125,11 +124,11 @@ You may call `turnstile.reset()` in the corresponding `error-callback` to manual
 The interval between retries for Turnstile can be configured by the `retry-interval` option, allowing you to optimize retry timing for your visitors’ typical network conditions. A longer interval may be more appropriate for visitors on slower or less reliable connections, while shorter intervals work well in environments with typically stable connectivity.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	retry: "auto",
-	"retry-interval": 8000, // Wait 8 seconds between retries
-	"error-callback": handleError,
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  retry: 'auto',
+  'retry-interval': 8000, // Wait 8 seconds between retries
+  'error-callback': handleError
 });
 ```
 
@@ -142,23 +141,23 @@ For instance, in a scenario where the Turnstile widget is implemented within a f
 In such instances, the `timeout-callback` of the widget is activated, enabling the widget to reset itself as needed and provide appropriate guidance. This callback allows you to implement user-friendly timeout handling, such as highlighting the Turnstile widget, displaying a notification, or automatically refreshing the challenge.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	callback: function (token) {
-		console.log("Challenge completed successfully");
-	},
-	"timeout-callback": function () {
-		console.log("Challenge timed out - user action required");
-		document.getElementById("challenge-notice").textContent =
-			"Please complete the security check above to continue.";
-
-		// Optionally highlight the widget
-		document.getElementById("my-widget").style.border = "2px solid orange";
-	},
-	"expired-callback": function () {
-		console.log("Token expired - challenge needs refresh");
-		document.getElementById("challenge-notice").textContent =
-			"Security check expired. Please try again.";
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  callback: function(token) {
+    console.log('Challenge completed successfully');
+  },
+  'timeout-callback': function() {
+    console.log('Challenge timed out - user action required');
+    document.getElementById('challenge-notice').textContent = 
+      'Please complete the security check above to continue.';
+    
+    // Optionally highlight the widget
+    document.getElementById('my-widget').style.border = '2px solid orange';
+  },
+  'expired-callback': function() {
+    console.log('Token expired - challenge needs refresh');
+    document.getElementById('challenge-notice').textContent = 
+      'Security check expired. Please try again.';
+  }
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/troubleshooting/index.mdx b/src/content/docs/turnstile/troubleshooting/index.mdx
index 62155e4b61f1542..9732a59701eb192 100644
--- a/src/content/docs/turnstile/troubleshooting/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 8
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about troubleshooting Turnstile:
 
diff --git a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
index ce67d78a5431377..50d1cebeb5a11e6 100644
--- a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
+++ b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
@@ -6,9 +6,10 @@ products:
   - turnstile
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip, DashButton, Steps } from "~/components";
+import { GlossaryTooltip, DashButton, Steps } from "~/components"
 
 You can rotate the <GlossaryTooltip term="secret key">secret key</GlossaryTooltip> using the following steps:
 
diff --git a/src/content/docs/turnstile/troubleshooting/testing.mdx b/src/content/docs/turnstile/troubleshooting/testing.mdx
index 41f98655c15fd16..32e507a1005bb68 100644
--- a/src/content/docs/turnstile/troubleshooting/testing.mdx
+++ b/src/content/docs/turnstile/troubleshooting/testing.mdx
@@ -9,9 +9,10 @@ tags:
 sidebar:
   order: 1
   label: Testing
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Use dummy sitekeys and secret keys to test your Turnstile implementation without triggering real challenges that would interfere with automated testing suites.
 
@@ -26,23 +27,23 @@ Dummy keys solve this by providing predictable, controlled responses that work w
 
 ## Test sitekeys
 
-| Sitekey                    | Behavior                     | Widget Type | Use case                             |
-| -------------------------- | ---------------------------- | ----------- | ------------------------------------ |
-| `1x00000000000000000000AA` | Always passes                | Visible     | Test successful form submissions     |
-| `2x00000000000000000000AB` | Always fails                 | Visible     | Test error handling and retry logic  |
-| `1x00000000000000000000BB` | Always passes                | Invisible   | Test invisible widget success flows  |
-| `2x00000000000000000000BB` | Always fails                 | Invisible   | Test invisible widget error handling |
-| `3x00000000000000000000FF` | Forces interactive challenge | Visible     | Test user interaction scenarios      |
+| Sitekey | Behavior | Widget Type | Use case |
+| ------- | -------- | ----------- | -------- |
+| `1x00000000000000000000AA` | Always passes | Visible | Test successful form submissions |
+| `2x00000000000000000000AB` | Always fails | Visible | Test error handling and retry logic |
+| `1x00000000000000000000BB` | Always passes | Invisible | Test invisible widget success flows |
+| `2x00000000000000000000BB` | Always fails | Invisible | Test invisible widget error handling |
+| `3x00000000000000000000FF` | Forces interactive challenge | Visible | Test user interaction scenarios |
 
 ## Test secret keys
 
 Use these secret keys for server-side validation testing:
 
-| Secret key                            | Behavior                            | Use case                         |
-| ------------------------------------- | ----------------------------------- | -------------------------------- |
-| `1x0000000000000000000000000000000AA` | Always passes validation            | Test successful token validation |
-| `2x0000000000000000000000000000000AA` | Always fails validation             | Test validation error handling   |
-| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling    |
+| Secret key | Behavior | Use case |
+| ---------- | -------- | -------- |
+| `1x0000000000000000000000000000000AA` | Always passes validation | Test successful token validation |
+| `2x0000000000000000000000000000000AA` | Always fails validation | Test validation error handling |
+| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling |
 
 ---
 
@@ -77,10 +78,9 @@ Replace your production secret key with a test secret key.
 
 ```js
 // Environment-based configuration
-const SECRET_KEY =
-	process.env.NODE_ENV === "production"
-		? process.env.TURNSTILE_SECRET_KEY
-		: "1x0000000000000000000000000000000AA";
+const SECRET_KEY = process.env.NODE_ENV === 'production' 
+  ? process.env.TURNSTILE_SECRET_KEY 
+  : '1x0000000000000000000000000000000AA';
 
 // Use in validation
 const validation = await validateTurnstile(token, SECRET_KEY);
@@ -96,7 +96,7 @@ Set up different keys for different environments.
 TURNSTILE_SITEKEY=1x00000000000000000000AA
 TURNSTILE_SECRET_KEY=1x0000000000000000000000000000000AA
 
-# .env.test
+# .env.test  
 TURNSTILE_SITEKEY=2x00000000000000000000AB
 TURNSTILE_SECRET_KEY=2x0000000000000000000000000000000AA
 
@@ -126,26 +126,27 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ```json title="Success response"
 {
-	"success": true,
-	"challenge_ts": "2022-02-28T15:14:30.096Z",
-	"hostname": "localhost",
-	"error-codes": [],
-	"action": "test",
-	"cdata": "test-data"
+  "success": true,
+  "challenge_ts": "2022-02-28T15:14:30.096Z",
+  "hostname": "localhost",
+  "error-codes": [],
+  "action": "test",
+  "cdata": "test-data"
 }
 ```
 
 ```json title="Failure response"
 {
-	"success": false,
-	"error-codes": ["invalid-input-response"]
+  "success": false,
+  "error-codes": ["invalid-input-response"]
 }
+
 ```
 
 ```json title="Token already redeemed"
 {
-	"success": false,
-	"error-codes": ["timeout-or-duplicate"]
+  "success": false,
+  "error-codes": ["timeout-or-duplicate"]
 }
 ```
 
@@ -153,8 +154,8 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ## Testing scenarios
 
-| Test sitekey               | Test secret key                       | <div style="width:200px">Test case</div>                             |
-| -------------------------- | ------------------------------------- | -------------------------------------------------------------------- |
-| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation.        |
-| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail.                                   |
-| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
+| Test sitekey | Test secret key | <div style="width:200px">Test case</div> |
+| ------------ | --------------- | --------- |
+| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation. |
+| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail. |
+| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
\ No newline at end of file
diff --git a/src/content/docs/turnstile/turnstile-analytics/index.mdx b/src/content/docs/turnstile/turnstile-analytics/index.mdx
index 1ad2a0c6a7bcde0..b580a70e9a92a88 100644
--- a/src/content/docs/turnstile/turnstile-analytics/index.mdx
+++ b/src/content/docs/turnstile/turnstile-analytics/index.mdx
@@ -9,9 +9,10 @@ sidebar:
   order: 5
 description: Use Turnstile Analytics to view the number of challenges issued,
   the challenge solve rate, and the metrics of issued challenges.
+
 ---
 
-import { Render, DirectoryListing, DashButton } from "~/components";
+import { Render, DirectoryListing, DashButton } from "~/components"
 
 Turnstile Analytics shows widget statistics across traffic dimensions like hostname, country, browser, and IP address. Use these metrics to identify where challenge activity is highest and whether specific sources are failing or bypassing challenges.
 
@@ -37,4 +38,4 @@ The metrics show changes in the solve rate, widget traffic, and top actions for
 
 Refer to the pages below for more information about Turnstile Analytics:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
index a4a5ca21b6e199c..6a6c10bc60370a8 100644
--- a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
+++ b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
@@ -28,11 +28,10 @@ For more details, refer to the [testing documentation](/turnstile/troubleshootin
 :::caution
 
 Never use test credentials in production. Always ensure:
-
 - Test credentials are only used in test environments.
 - Production credentials are properly protected.
 - Your deployment process prevents test credentials from reaching production.
-  :::
+:::
 
 ## Implementation
 
@@ -41,27 +40,26 @@ The key to implementing test-environment detection is identifying test requests
 ```typescript
 // Detect test environments using IP addresses or headers
 function isTestEnvironment(request) {
-	const testIPs = ["127.0.0.1", "::1"];
-	const isTestIP = testIPs.includes(request.ip);
-	const hasTestHeader =
-		request.headers["x-test-environment"] === "secret-token";
+  const testIPs = ['127.0.0.1', '::1'];
+  const isTestIP = testIPs.includes(request.ip);
+  const hasTestHeader = request.headers['x-test-environment'] === 'secret-token';
 
-	return isTestIP || hasTestHeader;
+  return isTestIP || hasTestHeader;
 }
 
 // Use the appropriate credentials based on the environment
 function getTurnstileCredentials(request) {
-	if (isTestEnvironment(request)) {
-		return {
-			sitekey: "1x00000000000000000000AA",
-			secretKey: "1x0000000000000000000000000000000AA",
-		};
-	}
-
-	return {
-		sitekey: process.env.TURNSTILE_SITE_KEY,
-		secretKey: process.env.TURNSTILE_SECRET_KEY,
-	};
+  if (isTestEnvironment(request)) {
+    return {
+      sitekey: '1x00000000000000000000AA',
+      secretKey: '1x0000000000000000000000000000000AA'
+    };
+  }
+
+  return {
+    sitekey: process.env.TURNSTILE_SITE_KEY,
+    secretKey: process.env.TURNSTILE_SECRET_KEY
+  };
 }
 ```
 
@@ -70,9 +68,9 @@ function getTurnstileCredentials(request) {
 When rendering your page, inject the appropriate sitekey based on the environment:
 
 ```typescript
-app.get("/your-form", (req, res) => {
-	const { sitekey } = getTurnstileCredentials(req);
-	res.render("form", { sitekey });
+app.get('/your-form', (req, res) => {
+  const { sitekey } = getTurnstileCredentials(req);
+  res.render('form', { sitekey });
 });
 ```
 
@@ -114,16 +112,16 @@ For Cypress or similar E2E testing frameworks:
 ```typescript
 // Set test header for all test requests
 beforeEach(() => {
-	cy.intercept("*", (req) => {
-		req.headers["x-test-environment"] = "secret-token";
-	});
+  cy.intercept('*', (req) => {
+    req.headers['x-test-environment'] = 'secret-token';
+  });
 });
 
 // Your test can now interact with the form normally
-it("submits form successfully", () => {
-	cy.visit("/your-form");
-	cy.get("form").submit();
-	// Turnstile will automatically pass verification
+it('submits form successfully', () => {
+  cy.visit('/your-form');
+  cy.get('form').submit();
+  // Turnstile will automatically pass verification
 });
 ```
 
diff --git a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
index 865dade6b1b9bde..cd516941cbdc5e1 100644
--- a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
+++ b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
@@ -27,7 +27,7 @@ Traditional IP-based detection fails because each request appears to come from a
 - You must have basic familiarity with Turnstile integration. Refer to [Get started with Turnstile](/turnstile/get-started/) for more information.
 
 :::caution[Ephemeral IDs are not guaranteed to be unique]
-Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID.
+Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID. 
 
 Use Ephemeral IDs to detect high-volume abuse patterns, not to uniquely identify individual devices. Always set detection thresholds high enough to avoid false positives.
 :::
@@ -241,4 +241,4 @@ Ephemeral IDs are privacy-preserving. They are scoped to your account, short-liv
 
 - [Ephemeral IDs](/turnstile/additional-configuration/ephemeral-id/)
 - [Server-side validation](/turnstile/get-started/server-side-validation/)
-- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
+- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
\ No newline at end of file
diff --git a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
index ebc66f19cfe4972..c7a73ce8527faa1 100644
--- a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
+++ b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
@@ -85,13 +85,7 @@ Add the Turnstile widget to your existing login form:
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input
-		type="password"
-		id="password"
-		placeholder="Password"
-		autocomplete="off"
-		required
-	/>
+	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
diff --git a/src/content/docs/use-cases/e-commerce/performance.mdx b/src/content/docs/use-cases/e-commerce/performance.mdx
index 82a7e010f0ab221..7c7d4fc51d1f3db 100644
--- a/src/content/docs/use-cases/e-commerce/performance.mdx
+++ b/src/content/docs/use-cases/e-commerce/performance.mdx
@@ -51,4 +51,4 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 2. [Set up Cloudflare Images](/images/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
 4. [Configure Zaraz](/zaraz/get-started/)
-5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
+5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
diff --git a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
index a073c15a2066185..9a2ebfe22516874 100644
--- a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
+++ b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
@@ -11,29 +11,21 @@ sidebar:
 
 import { DashButton, Render, Steps, TabItem, Tabs } from "~/components";
 
-HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages:
+HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages: 
 
 1. Configure your SSL/TLS encryption mode.
 2. Redirect all HTTP requests to HTTPS.
 3. Harden your HTTPS setup with minimum TLS versions and HSTS.
 4. Monitor third-party scripts on your pages.
-5. Verify your configuration.
+5. Verify your configuration. 
 
 The core workflow is available on Free, Pro, and Business plans.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Client-Side Security is the exception: it is configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Client-Side Security is the exception: it is configured at the account level." }} />
 
 ## Configure your SSL/TLS encryption mode
 
 Your SSL/TLS encryption mode controls how Cloudflare connects to your origin server. For end-to-end encryption, use **Full (strict)** — it encrypts both connections and verifies your origin certificate. For a detailed comparison of all available modes, refer to [Encryption modes](/ssl/origin-configuration/ssl-modes/).
-
 ### Check your current mode
 
 <Steps>
@@ -83,7 +75,6 @@ If your origin already has a valid certificate from a publicly trusted certifica
 9. Select **OK**.
 
 </Steps>
-
 :::note
 For details about working with certificates programmatically, refer to [API calls](/ssl/origin-configuration/origin-ca/#api-calls).
 :::
@@ -101,7 +92,6 @@ For details about working with certificates programmatically, refer to [API call
 4. Enable SSL and port `443` at your origin web server.
 
 </Steps>
-
 :::note
 If you do not see your server listed, search the [DigiCert documentation](https://www.digicert.com/search-results) or contact your hosting provider.
 :::
@@ -119,15 +109,13 @@ After installing a valid certificate on your origin server, set the encryption m
 <Render file="change-encryption-mode-api" product="ssl" />
 
 </TabItem> </Tabs>
-
 :::caution
 If your site shows a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) after changing the encryption mode, your origin certificate may not meet the requirements for Full (strict). The certificate must be unexpired, issued by a trusted CA or Cloudflare Origin CA, and contain a Common Name (CN) or Subject Alternative Name (SAN) that matches your hostname. For redirect loop issues, refer to [ERR_TOO_MANY_REDIRECTS](/ssl/troubleshooting/too-many-redirects/).
 :::
 
 ## Redirect all HTTP requests to HTTPS
 
-Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this:
-
+Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this: 
 1. Always Use HTTPS redirects HTTP requests to HTTPS
 2. Automatic HTTPS Rewrites fixes mixed content references in your page HTML
 
@@ -166,7 +154,6 @@ If only some parts of your application can support HTTPS traffic, do not turn on
 </Steps>
 
 </TabItem> </Tabs>
-
 ### Turn on Automatic HTTPS Rewrites
 
 Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resource URLs in your page HTML to HTTPS. This is useful for sites where you do not control all asset URLs, such as CMS-hosted content or embedded third-party resources.
@@ -188,7 +175,6 @@ Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resourc
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `automatic_https_rewrites` as the setting name in the URI path, and the `value` parameter set to `"on"`.
 
 </TabItem> </Tabs>
-
 :::note
 Automatic HTTPS Rewrites does not rewrite all HTTP URLs. Some passive content (such as images) may not be rewritten, which can still cause mixed content warnings. For details on how rewrites work and troubleshooting, refer to [Automatic HTTPS Rewrites](/ssl/edge-certificates/additional-options/automatic-https-rewrites/) and [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/).
 :::
@@ -218,7 +204,6 @@ TLS 1.0 and 1.1 have known vulnerabilities and are no longer considered secure.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `min_tls_version` as the setting name in the URI path, and the `value` parameter set to `"1.2"`.
 
 </TabItem> </Tabs>
-
 :::note[Per-hostname minimum TLS version requires Advanced Certificate Manager]
 To set minimum TLS versions for individual hostnames instead of the entire zone, refer to [Per-hostname setup](/ssl/edge-certificates/additional-options/minimum-tls/#per-hostname). This requires an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription.
 :::
@@ -244,7 +229,6 @@ TLS 1.3 provides faster handshakes and improved security over TLS 1.2.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `tls_1_3` as the setting name in the URI path, and the `value` parameter set to `"on"`. To also turn on 0-RTT (Zero Round Trip Time Resumption), set the value to `"zrt"`.
 
 </TabItem> </Tabs>
-
 ### Turn on HSTS
 
 HTTP Strict Transport Security (HSTS) adds a response header that tells browsers to connect to your site over HTTPS only, even if a link or redirect tries to send them over HTTP. HSTS protects against protocol downgrade attacks.
@@ -288,7 +272,6 @@ Before turning on HSTS, confirm these prerequisites:
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `security_header` as the setting name in the URI path, and specify the `value` object that includes your HSTS settings.
 
 </TabItem> </Tabs>
-
 ### Review your cipher suites
 
 Cloudflare's default cipher suites provide strong encryption for most sites. You do not need to change them unless a security audit or compliance requirement specifies particular cipher configurations.
@@ -316,7 +299,6 @@ HTTPS encrypts data in transit, but third-party scripts loaded by your pages can
 3. Turn on **Continuous script monitoring**.
 
 </Steps>
-
 ### Review detected resources
 
 After turning on monitoring, it may take some time for Cloudflare to generate a list of detected scripts on your domain.
@@ -332,7 +314,6 @@ After turning on monitoring, it may take some time for Cloudflare to generate a
 3. Review the list of detected scripts. Check for unknown or unexpected scripts from domains you do not recognize.
 
 </Steps>
-
 Depending on your Cloudflare plan, you may also be able to review connections made by scripts and check them for malicious activity. For setup details, refer to [Get started with client-side security](/client-side-security/get-started/).
 
 :::note[Content security rules require Client-Side Security Advanced]
diff --git a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
index 0e5abbc0284d7c9..4cfed58dfe9b42a 100644
--- a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
+++ b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
@@ -15,14 +15,7 @@ import { Render, Steps, DashButton } from "~/components";
 
 Contact, registration, and checkout forms are common targets for automated abuse. This guide covers form protection: verifying that visitors are human, limiting repeated submissions, and blocking known attack patterns. The core workflow uses features available on all plans. Pro and Business plan features are included as callouts.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Add Turnstile to your forms
 
@@ -42,18 +35,14 @@ Add the Turnstile script and widget `div` element to each form you want to prote
 
 ```html
 <form id="contact-form" action="/submit" method="POST">
-	<input type="text" name="name" placeholder="Name" required />
-	<input type="email" name="email" placeholder="Email" required />
-	<textarea name="message" placeholder="Message" required></textarea>
-	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
-	<button type="submit">Submit</button>
+  <input type="text" name="name" placeholder="Name" required />
+  <input type="email" name="email" placeholder="Email" required />
+  <textarea name="message" placeholder="Message" required></textarea>
+  <div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
+  <button type="submit">Submit</button>
 </form>
 
-<script
-	src="https://challenges.cloudflare.com/turnstile/v0/api.js"
-	async
-	defer
-></script>
+<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
 ```
 
 The widget renders in the form and generates a token when the visitor passes verification. The token is included in the form submission as the `cf-turnstile-response` field.
@@ -68,26 +57,26 @@ Call the Siteverify API before processing any form submission:
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
 async function validateTurnstile(token, remoteip) {
-	try {
-		const response = await fetch(
-			"https://challenges.cloudflare.com/turnstile/v0/siteverify",
-			{
-				method: "POST",
-				headers: { "Content-Type": "application/json" },
-				body: JSON.stringify({
-					secret: SECRET_KEY,
-					response: token,
-					remoteip: remoteip,
-				}),
-			},
-		);
-
-		const result = await response.json();
-		return result;
-	} catch (error) {
-		console.error("Turnstile validation error:", error);
-		return { success: false, "error-codes": ["internal-error"] };
-	}
+  try {
+    const response = await fetch(
+      "https://challenges.cloudflare.com/turnstile/v0/siteverify",
+      {
+        method: "POST",
+        headers: { "Content-Type": "application/json" },
+        body: JSON.stringify({
+          secret: SECRET_KEY,
+          response: token,
+          remoteip: remoteip,
+        }),
+      },
+    );
+
+    const result = await response.json();
+    return result;
+  } catch (error) {
+    console.error("Turnstile validation error:", error);
+    return { success: false, "error-codes": ["internal-error"] };
+  }
 }
 ```
 
@@ -127,17 +116,7 @@ The **Request rate analysis** tab in Security Analytics displays request rate di
 
 Create a rule that limits how many times a single IP address can submit to your form endpoint within a given period. Adjust the path, threshold, and period for your site.
 
-<Render
-	file="create-rate-limiting-rule"
-	product="waf"
-	params={{
-		ruleName: "Rate limit contact form submissions",
-		expression:
-			'(http.request.uri.path eq "/contact" and http.request.method eq "POST")',
-		expressionHelp: 'Replace "/contact" with your form endpoint path.',
-		threshold: "5",
-	}}
-/>
+<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit contact form submissions", expression: '(http.request.uri.path eq "/contact" and http.request.method eq "POST")', expressionHelp: 'Replace "/contact" with your form endpoint path.', threshold: "5" }} />
 
 :::note
 Rate limiting rule parameters (counting characteristics, periods, number of rules) vary by plan. For the full availability matrix, refer to [Rate limiting rules](/waf/rate-limiting-rules/#availability).
diff --git a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
index e1db4f92ef75e8b..cfa61e65fe47d61 100644
--- a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
+++ b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
@@ -11,18 +11,16 @@ sidebar:
   label: Stop account takeover
 ---
 
-import { Steps, DashButton, GlossaryTooltip, Render } from "~/components";
+import {
+  Steps,
+  DashButton,
+  GlossaryTooltip,
+  Render,
+} from "~/components";
 
 When your site has login pages, you need to decide how to verify that visitors are human, how aggressively to limit failed attempts, and which request patterns to block. This guide covers five stages: enforce HTTPS, turn on bot protection, add [Turnstile](/turnstile/) to your login form, create Application Security [rate limiting rules](/waf/rate-limiting-rules/) and [custom rules](/waf/custom-rules/) for suspicious patterns, and monitor for ongoing attacks using [SSL/TLS](/ssl/) transport security and [Cloudflare bot solutions](/bots/). The core workflow covers features available on Free, Pro, and Business plans. Enterprise features such as leaked credentials custom detection locations and Bot Management custom rules are included as callouts.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Enforce HTTPS to protect credentials in transit
 
@@ -100,17 +98,10 @@ You need both the sitekey and secret key in the following steps.
 #### 2. Add the client-side snippet
 
 Add the Turnstile script and widget container to your login form. Replace `<YOUR-SITE-KEY>` with the sitekey from the previous step.
-
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input
-		type="password"
-		id="password"
-		placeholder="Password"
-		autocomplete="off"
-		required
-	/>
+	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
@@ -127,7 +118,6 @@ The widget renders inside the `div` and produces a token when the visitor passes
 #### 3. Validate the token on your server
 
 Before processing the form submission, send the token to the Turnstile siteverify endpoint to confirm the visitor passed the challenge.
-
 ```js title="server.js"
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
@@ -166,7 +156,6 @@ For the complete response format, error codes, and examples in other languages,
 #### Test your implementation
 
 Turnstile provides test site keys that return predictable results without contacting the Siteverify API.
-
 - **Always passes**: Use site key `1x00000000000000000000AA` and secret key `1x0000000000000000000000000000000AA` to simulate a successful challenge.
 - **Always blocks**: Use site key `2x00000000000000000000AB` and secret key `2x0000000000000000000000000000000AA` to simulate a failed challenge.
 - **Forces interactive challenge**: Use site key `3x00000000000000000000FF` to test the interactive challenge flow.
@@ -183,18 +172,7 @@ The following example creates a rate limiting rule that issues a Managed Challen
 Managed Challenge and other [challenge types](/cloudflare-challenges/challenge-types/challenge-pages/) require an HTML response to render. They do not work for non-HTML responses such as AJAX/XHR requests, which are common on login endpoints that use single-page applications (SPAs) or API-based authentication. If your login flow uses AJAX, consider using [Turnstile Pre-Clearance](/turnstile/additional-configuration/pre-clearance-support/) instead.
 :::
 
-<Render
-	file="create-rate-limiting-rule"
-	product="waf"
-	params={{
-		ruleName: "Rate limit login endpoint",
-		expression:
-			'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"',
-		expressionHelp:
-			"Replace `example.com` with your domain and `/login` with your login endpoint path.",
-		threshold: "5",
-	}}
-/>
+<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit login endpoint", expression: 'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"', expressionHelp: 'Replace `example.com` with your domain and `/login` with your login endpoint path.', threshold: "5" }} />
 
 :::note
 (Optional) To count only failed login attempts instead of all matching requests, Business plan and above users can add a separate counting expression under **Increment counter when**:
@@ -342,7 +320,7 @@ Enterprise customers with Bot Management get additional tools for login protecti
 - **Custom rules with bot scores**: combine `cf.bot_management.score` with login path matching for precise control. Refer to [Custom rules for bot protection](/bots/additional-configurations/custom-rules/).
 - **Account takeover detections**: monitor suspicious login volume and failure rates using detection IDs in custom rules and rate limiting rules. Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/).
 - **Account Abuse Protection** (Early Access): detect account fraud patterns beyond credential stuffing. Refer to [Account Abuse Protection](/bots/account-abuse-protection/).
-  :::
+:::
 
 ## Monitor for ongoing compromise attempts
 
diff --git a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
index 82e2fbcd9c90854..df0cbabb8f7a2aa 100644
--- a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
+++ b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
@@ -14,14 +14,7 @@ import { Tabs, TabItem, Steps, Render, DashButton } from "~/components";
 
 The right defense against malicious bot traffic depends on the traffic patterns on your site and your plan. This guide covers a layered approach using [Cloudflare Bots](/bots/), [Cloudflare Application Security](/waf/) (also known as Web Application Firewall or WAF), and [Turnstile](/turnstile/), from baseline protection to targeted custom rules. The core workflow uses features on Free, Pro, and Business plans, with callouts for Enterprise options.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Review your bot traffic
 
diff --git a/src/content/docs/use-cases/web-apps/performance.mdx b/src/content/docs/use-cases/web-apps/performance.mdx
index 8fa2bc53968700d..f3ac9b09881123e 100644
--- a/src/content/docs/use-cases/web-apps/performance.mdx
+++ b/src/content/docs/use-cases/web-apps/performance.mdx
@@ -39,9 +39,10 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 
 - **Edge logic** - Run custom performance optimizations at the edge, such as HTML rewriting and dynamic content assembly, without round-trips to your origin
 
+
 ## Get started
 
 1. [Configure Cache Rules](/cache/how-to/cache-rules/)
 2. [Enable Argo Smart Routing](/argo-smart-routing/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
-4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
+4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
diff --git a/src/content/docs/vectorize/best-practices/index.mdx b/src/content/docs/vectorize/best-practices/index.mdx
index b5663efc9edfdd9..de610d3a68aed70 100644
--- a/src/content/docs/vectorize/best-practices/index.mdx
+++ b/src/content/docs/vectorize/best-practices/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/best-practices/list-vectors.mdx b/src/content/docs/vectorize/best-practices/list-vectors.mdx
index 0c5754e5d12cfb3..d623e334eb65385 100644
--- a/src/content/docs/vectorize/best-practices/list-vectors.mdx
+++ b/src/content/docs/vectorize/best-practices/list-vectors.mdx
@@ -43,7 +43,6 @@ To see recently added or removed vectors, you must start a new list-vectors requ
 ### Response structure
 
 Each response includes:
-
 - `count`: Number of vectors returned in this response
 - `totalCount`: Total number of vectors in the index
 - `isTruncated`: Whether there are more vectors available
@@ -71,4 +70,4 @@ wrangler vectorize list-vectors my-index --count=1000
 wrangler vectorize list-vectors my-index --count=1000 --cursor="<cursor-from-response>"
 
 # Repeat until no more results
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/vectorize/demos.mdx b/src/content/docs/vectorize/demos.mdx
index f98a71856f7f16a..d908b0b5883751d 100644
--- a/src/content/docs/vectorize/demos.mdx
+++ b/src/content/docs/vectorize/demos.mdx
@@ -8,7 +8,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, ResourcesBySelector } from "~/components";
+import { GlossaryTooltip, ResourcesBySelector } from "~/components"
 
 Learn how you can use Vectorize within your existing architecture.
 
@@ -16,11 +16,4 @@ Learn how you can use Vectorize within your existing architecture.
 
 Explore the following <GlossaryTooltip term="reference architecture">reference architectures</GlossaryTooltip> that use Vectorize:
 
-<ResourcesBySelector
-	types={[
-		"reference-architecture",
-		"design-guide",
-		"reference-architecture-diagram",
-	]}
-	products={["vectorize"]}
-/>
+<ResourcesBySelector types={["reference-architecture","design-guide","reference-architecture-diagram"]} products={["vectorize"]} />
diff --git a/src/content/docs/vectorize/examples/agents.mdx b/src/content/docs/vectorize/examples/agents.mdx
index e9bd2deab309881..c7eb3790d39040b 100644
--- a/src/content/docs/vectorize/examples/agents.mdx
+++ b/src/content/docs/vectorize/examples/agents.mdx
@@ -9,4 +9,4 @@ description: Build AI-powered Agents on Cloudflare
 products:
   - vectorize
   - agents
----
+---
\ No newline at end of file
diff --git a/src/content/docs/vectorize/examples/index.mdx b/src/content/docs/vectorize/examples/index.mdx
index f5b3b57929be9d3..b7aaf4f768acdcd 100644
--- a/src/content/docs/vectorize/examples/index.mdx
+++ b/src/content/docs/vectorize/examples/index.mdx
@@ -11,7 +11,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, DirectoryListing } from "~/components";
+import { GlossaryTooltip, DirectoryListing } from "~/components"
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Vectorize.
 
diff --git a/src/content/docs/vectorize/get-started/index.mdx b/src/content/docs/vectorize/get-started/index.mdx
index 44c0cdc6b7ec9e3..2ea3f1ce7462b31 100644
--- a/src/content/docs/vectorize/get-started/index.mdx
+++ b/src/content/docs/vectorize/get-started/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/platform/index.mdx b/src/content/docs/vectorize/platform/index.mdx
index 0dde65d6a58df96..1be91e4d2f5aaf8 100644
--- a/src/content/docs/vectorize/platform/index.mdx
+++ b/src/content/docs/vectorize/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/reference/index.mdx b/src/content/docs/vectorize/reference/index.mdx
index 8f496dea995d462..f297e13f34d84b6 100644
--- a/src/content/docs/vectorize/reference/index.mdx
+++ b/src/content/docs/vectorize/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/about.mdx b/src/content/docs/version-management/about.mdx
index 1587b66c14e88d6..6c6e429bda9459d 100644
--- a/src/content/docs/version-management/about.mdx
+++ b/src/content/docs/version-management/about.mdx
@@ -9,7 +9,7 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Version Management works through a combination of **environments** and **versions**.
 
@@ -47,7 +47,7 @@ stateDiagram-v2
 
 ## Environments
 
-<Render file="environment-definition" product="version-management" /> <br />
+<Render file="environment-definition" product="version-management" /> <br/>
 
 After you [enable](/version-management/how-to/enable/) version management, you will have the ability to create default environments:
 
@@ -59,7 +59,7 @@ To send traffic to specific environments, send requests to that environment that
 
 ## Versions
 
-<Render file="version-definition" product="version-management" /> <br />
+<Render file="version-definition" product="version-management" /> <br/>
 
 <Render file="enable-default-creation" product="version-management" />
 
diff --git a/src/content/docs/version-management/how-to/compare-versions.mdx b/src/content/docs/version-management/how-to/compare-versions.mdx
index 1b6ec4ea51148f4..587f8e9dea1faed 100644
--- a/src/content/docs/version-management/how-to/compare-versions.mdx
+++ b/src/content/docs/version-management/how-to/compare-versions.mdx
@@ -19,7 +19,7 @@ To compare versions:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management** > **Comparisons**.
diff --git a/src/content/docs/version-management/how-to/environments.mdx b/src/content/docs/version-management/how-to/environments.mdx
index 9c26342241ce248..7b1de502b4273a7 100644
--- a/src/content/docs/version-management/how-to/environments.mdx
+++ b/src/content/docs/version-management/how-to/environments.mdx
@@ -9,43 +9,44 @@ products:
   - version-management
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
 
 <Render file="environment-definition" product="version-management" />
 
----
+***
 
 ## Create environment
 
 <Render file="enable-default-creation" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" />
-<br />
+<Render file="create-environment-situation" product="version-management" /> <br/>
 
 To create a new environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Go to **Environments**.
 4. Select **Create Environment**.
 5. Provide the following information:
 
-- **Environment Name**: A unique, descriptive name for the environment.
-- [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
-- **Initial position**: Controls where this environment should be in your testing process.
+* **Environment Name**: A unique, descriptive name for the environment.
+* [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
+* **Initial position**: Controls where this environment should be in your testing process.
 
 6. Select **Create**.
 
 :::note
 
+
 You can only adjust the [**Read-only Environment**](/version-management/reference/read-only-environments/) configuration after an environment has been created.
 
+
 :::
 
----
+***
 
 ## Edit environment
 
@@ -53,7 +54,7 @@ To edit an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -61,7 +62,7 @@ To edit an environment:
 5. Make any required changes.
 6. Select **Save**.
 
----
+***
 
 ## Change environment version
 
@@ -73,7 +74,7 @@ For more details on the flow of versions and environments, refer to [How it work
 
 Promotion moves a version from a lower-ranked environment to the next highest one.
 
-<Render file="promote-version" product="version-management" /> <br />
+<Render file="promote-version" product="version-management" /> <br/>
 
 ### Roll back a version
 
@@ -83,13 +84,13 @@ To roll back a version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
 4. On a specific environment, select **Roll back**.
 
----
+***
 
 ## Delete environment
 
@@ -97,7 +98,7 @@ To delete an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -106,6 +107,8 @@ To delete an environment:
 
 :::note
 
+
 You cannot delete your **Production** environment.
 
+
 :::
diff --git a/src/content/docs/version-management/how-to/index.mdx b/src/content/docs/version-management/how-to/index.mdx
index 688bebd5f8faf4c..94f85edeb05a853 100644
--- a/src/content/docs/version-management/how-to/index.mdx
+++ b/src/content/docs/version-management/how-to/index.mdx
@@ -3,7 +3,7 @@ title: How to
 pcx_content_type: navigation
 sidebar:
   order: 4
-  group:
+  group: 
     hideIndex: true
 
 description: Guides for managing versions and environments.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/how-to/versions.mdx b/src/content/docs/version-management/how-to/versions.mdx
index df497bbd391bd24..2bacb859b39b82d 100644
--- a/src/content/docs/version-management/how-to/versions.mdx
+++ b/src/content/docs/version-management/how-to/versions.mdx
@@ -25,7 +25,7 @@ To create a new version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **Clone**. This will copy over all configurations from that version.
@@ -78,7 +78,7 @@ To view metrics:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **View Metrics**.
diff --git a/src/content/docs/version-management/reference/available-configurations.mdx b/src/content/docs/version-management/reference/available-configurations.mdx
index bf748224eda2e08..d9d33c1d24d8f15 100644
--- a/src/content/docs/version-management/reference/available-configurations.mdx
+++ b/src/content/docs/version-management/reference/available-configurations.mdx
@@ -9,22 +9,24 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When you use Version Management, you can edit various configurations, such as [WAF custom rules](/waf/custom-rules/) and [Cache](/cache/).
 
 Generally, you are allowed to edit all zone-level configurations except for the following:
 
-- [DNS](/dns/)
-- [Spectrum](/spectrum/)
-- Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
-- [Zero Trust](/cloudflare-one/) and Access policies
-- [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
+* [DNS](/dns/)
+* [Spectrum](/spectrum/)
+* Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
+* [Zero Trust](/cloudflare-one/) and Access policies
+* [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
 
 :::note
 
+
 For the most up-to-date list of these configurations, start [editing configurations within a version](/version-management/how-to/versions/#change-configurations-in-a-version) in the Cloudflare dashboard.
 
+
 :::
 
 ## Limitations
diff --git a/src/content/docs/version-management/reference/index.mdx b/src/content/docs/version-management/reference/index.mdx
index 042d6149a274f5b..38759a3843efde4 100644
--- a/src/content/docs/version-management/reference/index.mdx
+++ b/src/content/docs/version-management/reference/index.mdx
@@ -3,7 +3,7 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 5
-  group:
+  group: 
     hideIndex: true
 
 description: Reference information for AI Crawl Control.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/reference/read-only-environments.mdx b/src/content/docs/version-management/reference/read-only-environments.mdx
index 36c12fc21a35a82..b6e45386b17cec4 100644
--- a/src/content/docs/version-management/reference/read-only-environments.mdx
+++ b/src/content/docs/version-management/reference/read-only-environments.mdx
@@ -9,15 +9,14 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When an environment is read-only, versions deployed to this environment will permanently become read-only. This configuration protects sensitive environments from accidental changes.
 
 **Version Zero** is an exception to this rule and is always editable.
 
-<Render file="production-read-only-default" product="version-management" />
-<br />
+<Render file="production-read-only-default" product="version-management" /> <br/>
 
-For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** _after_ your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
+For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** *after* your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
 
 To change the read-only status of an environment, [edit the environment](/version-management/how-to/environments/#edit-environment).
diff --git a/src/content/docs/waf/custom-rules/create-dashboard.mdx b/src/content/docs/waf/custom-rules/create-dashboard.mdx
index a48edb1f3026c30..5e974d601239c71 100644
--- a/src/content/docs/waf/custom-rules/create-dashboard.mdx
+++ b/src/content/docs/waf/custom-rules/create-dashboard.mdx
@@ -15,6 +15,7 @@ head:
 
 import { Render, Tabs, TabItem, Steps, DashButton } from "~/components";
 
+
 <Tabs syncKey="dashNewNav"> <TabItem label="New dashboard" icon="rocket">
 
 <Steps>
diff --git a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
index 6775abcaf7788d7..749a72275225954 100644
--- a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
+++ b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
@@ -10,4 +10,4 @@ import { Render } from "~/components";
 
 You can build an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
 
-<Render file="sequence-custom-rules" product="api-shield" />
+<Render file="sequence-custom-rules" product="api-shield" />
\ No newline at end of file
diff --git a/src/content/docs/waf/glossary.mdx b/src/content/docs/waf/glossary.mdx
index f7ce048d441c2e7..e777165a6bf1999 100644
--- a/src/content/docs/waf/glossary.mdx
+++ b/src/content/docs/waf/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - waf
 sidebar:
   order: 17
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's WAF documentation.
 
diff --git a/src/content/docs/waf/managed-rules/index.mdx b/src/content/docs/waf/managed-rules/index.mdx
index dcdce6b4f353b4b..d24fec1853393e0 100644
--- a/src/content/docs/waf/managed-rules/index.mdx
+++ b/src/content/docs/waf/managed-rules/index.mdx
@@ -81,3 +81,4 @@ This means a rule with a terminal action (such as Block or Managed Challenge) in
 ### WAF exceptions
 
 WAF exceptions (skip rules) are rules with a `skip` action deployed to the `http_request_firewall_managed` phase entry-point ruleset. They are evaluated in list order within the entry-point ruleset — a skip rule only bypasses `execute` rules listed after it. Place exceptions before the managed ruleset execute rules they are intended to skip. For more information, refer to [WAF exceptions](/waf/managed-rules/waf-exceptions/).
+
diff --git a/src/content/docs/waf/tools/index.mdx b/src/content/docs/waf/tools/index.mdx
index 93bf5ec8fba60f0..2547f0abc231788 100644
--- a/src/content/docs/waf/tools/index.mdx
+++ b/src/content/docs/waf/tools/index.mdx
@@ -12,6 +12,7 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
+
 The Cloudflare WAF offers the following additional tools:
 
 <DirectoryListing />
diff --git a/src/content/docs/waf/tools/privacy-pass.mdx b/src/content/docs/waf/tools/privacy-pass.mdx
index 253f4e8bd646159..dce774674951b17 100644
--- a/src/content/docs/waf/tools/privacy-pass.mdx
+++ b/src/content/docs/waf/tools/privacy-pass.mdx
@@ -7,6 +7,7 @@ source: https://support.cloudflare.com/hc/en-us/articles/115001992652-Using-Priv
 title: Privacy Pass
 tags:
   - Privacy
+
 ---
 
 [Privacy Pass](https://datatracker.ietf.org/wg/privacypass/about/) specifies an extensible protocol for creating and redeeming anonymous and transferable tokens. Its specification is maintained by the IETF.
@@ -14,7 +15,7 @@ Cloudflare provides "Silk - Privacy Pass Client". This is a Chrome and Firefox b
 
 For instance, a visitor IP address with poor reputation may receive a Cloudflare challenge page before gaining access to a Cloudflare-protected website. Privacy Pass allows the visitor to solve a challenge with or without interaction, depending on the device. Solving this challenge is coordinated with a third party attester in such a way that Cloudflare does not see the attestation method or the interaction, preserving visitors' privacy while maintaining a high level of security.
 
----
+***
 
 ## Set up Privacy Pass
 
@@ -22,12 +23,12 @@ For instance, a visitor IP address with poor reputation may receive a Cloudflare
 
 Your end users should download the Privacy Pass extension for either Google Chrome or Firefox:
 
-- [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
-- [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
+* [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
+* [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
 
 The Privacy Pass code is [available on GitHub](https://github.com/cloudflare/pp-browser-extension). You can report any issues in this repository.
 
----
+***
 
 ## Support for Privacy Pass v1 (legacy)
 
diff --git a/src/content/docs/waf/troubleshooting/faq.mdx b/src/content/docs/waf/troubleshooting/faq.mdx
index a3a09ba5996df45..d7e6a3b09ec4447 100644
--- a/src/content/docs/waf/troubleshooting/faq.mdx
+++ b/src/content/docs/waf/troubleshooting/faq.mdx
@@ -34,7 +34,6 @@ If you are using a regular expression, it is recommended that you test it with a
 If you have [SSL/TLS certificates](/ssl/) managed by Cloudflare, every time a certificate is issued or renewed, a [domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/dcv-flow/) must happen. When a certificate is in `pending_validation` state and there are valid DCV tokens in place, some Cloudflare security features such as [custom rules](/waf/custom-rules/) and [Managed Rules](/waf/managed-rules/) will be automatically disabled on specific DCV paths (for example, `/.well-known/pki-validation/` and `/.well-known/acme-challenge/`).
 
 These automatic bypasses do not appear in [Trace](/rules/trace-request/) results.
-
 ### Why have I been blocked?
 
 Cloudflare may block requests when it detects activity that could be unsafe. Common reasons include:
diff --git a/src/content/docs/waiting-room/about.mdx b/src/content/docs/waiting-room/about.mdx
index 85b25d1bb61107e..ae5c646b790822d 100644
--- a/src/content/docs/waiting-room/about.mdx
+++ b/src/content/docs/waiting-room/about.mdx
@@ -6,9 +6,10 @@ products:
   - waiting-room
 sidebar:
   order: 2
+
 ---
 
-import { LinkButton, Render } from "~/components";
+import { LinkButton, Render } from "~/components"
 
 Waiting Room queues visitors when your traffic approaches a previously defined threshold that might otherwise bring an application down.
 
@@ -20,6 +21,7 @@ Once you have [created and activated a waiting room](/waiting-room/get-started/)
 
 - If a page is not experiencing heavy traffic, a visitor accesses the page directly.
 - If page traffic approaches a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
+
   - Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
   - While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
   - When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
@@ -45,4 +47,4 @@ The other factor is the Waiting Room state, which is maintained at the local dat
 
 The Waiting Room state is updated with global information every few seconds. We have a pipeline set up in Cloudflare [Durable Objects](/durable-objects/) that ensures changes in traffic get propagated around the world. This architecture ensures that we do not introduce additional latency, as well as that we are making decisions with as near-time accuracy as possible.
 
-For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
+For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
\ No newline at end of file
diff --git a/src/content/docs/waiting-room/additional-options/create-events.mdx b/src/content/docs/waiting-room/additional-options/create-events.mdx
index 6fba618cbc22dd8..123834ddd12dbc3 100644
--- a/src/content/docs/waiting-room/additional-options/create-events.mdx
+++ b/src/content/docs/waiting-room/additional-options/create-events.mdx
@@ -6,6 +6,7 @@ products:
 title: Create scheduled events
 sidebar:
   order: 4
+
 ---
 
 When you want to customize the behavior of a waiting room for a specific period of time — such as changing the queueing method or increasing the total active users — set up a **scheduled event**. You can do this from the dashboard or via the API.
@@ -20,7 +21,7 @@ Only some customers can support scheduled events with their waiting rooms. For m
 
 1. Within your application, go to **Traffic** > **Waiting Room**.
 
-2. Expand a waiting room and select **Schedule event**.
+2. Expand a waiting room  and select **Schedule event**.
 
 3. Customize the details for your event: name the event, add a description (optional), and select a Start Date Time and an End Date Time.
 
@@ -64,21 +65,23 @@ If you are using a [custom template](/waiting-room/how-to/customize-waiting-room
 
 :::note
 
+
 If you need to create overlapping events, use different waiting rooms.
 
+
 :::
 
 ### Parameters
 
 Though most parameters are identical to those in a regular waiting room, there are a few unique to creating an event. For a complete list of event settings, please refer to [Create an Event](/api/resources/waiting_rooms/subresources/events/methods/create/).
 
-- `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
-- `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
-- `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
-- `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
-- `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
-- `description`: A text description providing more detail about the event.
-- `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
+* `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
+* `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
+* `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
+* `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
+* `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
+* `description`: A text description providing more detail about the event.
+* `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
 
 ### Queueing methods
 
@@ -96,8 +99,8 @@ Users who reach your application **during the prequeue period** are [randomly as
 
 To set up a "lottery", include the [following parameters](#parameters) in your API request:
 
-- `prequeue_start_time`
-- `shuffle_at_event_start`
+* `prequeue_start_time`
+* `shuffle_at_event_start`
 
 ## Preview an event configuration
 
@@ -122,12 +125,12 @@ Follow these steps if you would like to deploy a scheduled maintenance page, wit
 1. [Create a waiting room](/waiting-room/how-to/create-waiting-room/) with [Passthrough](/waiting-room/reference/queueing-methods/#passthrough) queueing method enabled.
 2. Create a waiting room event for this room with [Reject](/waiting-room/reference/queueing-methods/#reject) queueing method enabled.
 
-After the scheduled event has ended, users will have access to your site. You can end the maintenance window before the scheduled event is over by setting the event to disabled.
+After the scheduled event has ended, users will have access to your site.  You can end the maintenance window before the scheduled event is over by setting the event to disabled.
 
 ## Other API commands
 
-| Function                                                                                | Command  |
-| --------------------------------------------------------------------------------------- | -------- |
-| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)      | `GET`    |
+| Function                                                          | Command  |
+| ----------------------------------------------------------------- | -------- |
+| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)   | `GET`    |
 | [List scheduled events](/api/resources/waiting_rooms/subresources/events/methods/list/) | `GET`    |
-| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)        | `DELETE` |
+| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)         | `DELETE` |
diff --git a/src/content/docs/waiting-room/additional-options/index.mdx b/src/content/docs/waiting-room/additional-options/index.mdx
index bd77dc9b14cc6ad..92470e9cc3b208c 100644
--- a/src/content/docs/waiting-room/additional-options/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Beyond [creating a waiting room](/waiting-room/get-started/), you may want to further customize how your waiting room functions.
 
diff --git a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
index 8eac756e51d27f1..bd9c6161eebc229 100644
--- a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
+++ b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
@@ -6,6 +6,7 @@ products:
 title: Combine with Cloudflare for SaaS
 sidebar:
   order: 7
+
 ---
 
 If your application is using a custom hostname — meaning your SaaS provider is using [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) — your application can support a waiting room.
diff --git a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
index c39b032cfdb8839..0f15a5bf0d091f7 100644
--- a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Waiting Room Rules
 sidebar:
   order: 10
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In this section, we will list the Waiting Room rules available.
 
diff --git a/src/content/docs/waiting-room/api-reference.mdx b/src/content/docs/waiting-room/api-reference.mdx
index 893bc601dbd2942..b91d98532f5c31c 100644
--- a/src/content/docs/waiting-room/api-reference.mdx
+++ b/src/content/docs/waiting-room/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/waiting_rooms/methods/list/
 sidebar:
   order: 10
+
 ---
diff --git a/src/content/docs/waiting-room/glossary.mdx b/src/content/docs/waiting-room/glossary.mdx
index aa5be06af954401..5e0ec50ac37db3d 100644
--- a/src/content/docs/waiting-room/glossary.mdx
+++ b/src/content/docs/waiting-room/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Waiting Room documentation.
 products:
   - waiting-room
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Waiting Room documentation.
 
diff --git a/src/content/docs/waiting-room/how-to/control-user-session.mdx b/src/content/docs/waiting-room/how-to/control-user-session.mdx
index 9f585b420804aa8..a8981dcd2100717 100644
--- a/src/content/docs/waiting-room/how-to/control-user-session.mdx
+++ b/src/content/docs/waiting-room/how-to/control-user-session.mdx
@@ -8,13 +8,13 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Adjust these settings to control how long a user can hold their place on your site after leaving the waiting room.
 
 ## Session duration
 
-Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes. Each new request restarts a user’s time to stay active equal to **session duration**.
+Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes.  Each new request restarts a user’s time to stay active equal to **session duration**. 
 
 ## Disable session renewal to limit browsing time
 
@@ -24,9 +24,9 @@ You can limit each user’s time on your site to only one session duration by ch
 
 To terminate a user's session when they perform a specific action, you can send a command to the waiting room using an HTTP header on the response from your origin. This command tells the waiting room to revoke the session of the user associated with the current response. This allows spots to open up more dynamically and may increase throughput from your queue.
 
-To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard.
+To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard. 
 To enable this feature through the [Cloudflare API](/api/resources/waiting_rooms/methods/update/), update the `enabled_origin_commands` property to include the value `”revoke”` in the list of enabled origin commands.
-
+ 
 Then, to return a revocation origin command and revoke the user's session associated with the current request, add the `Cf-Waiting-Room-Command: revoke` HTTP header to the response from your origin.
 
 To get the number of sessions revoked, you can query `sessionsRevoked` metrics from your [Waiting Room analytics](/waiting-room/waiting-room-analytics/#graphql-analytics) data via GraphQL API.
diff --git a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
index f826cb8f5c312f5..ea279a612cbaf63 100644
--- a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
 title: Edit and delete waiting rooms
 sidebar:
   order: 5
+
 ---
 
 import { APIRequest } from "~/components";
@@ -40,36 +41,36 @@ For details about updating an active waiting room, refer to [Best practices](/wa
 [Replace](https://api.cloudflare.com#waiting-room-update-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="PUT"
-	json={{
-		name: "webshop-waiting-room",
-		host: "example.com",
-		new_users_per_minute: 200,
-		total_active_users: 300,
-	}}
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="PUT"
+  json={{
+    name: "webshop-waiting-room",
+    host: "example.com",
+    new_users_per_minute: 200,
+    total_active_users: 300
+  }}
 />
 
 [Update](https://api.cloudflare.com#waiting-room-patch-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="PATCH"
-	json={{
-		name: "webshop-waiting-room",
-		host: "example.com",
-		new_users_per_minute: 200,
-		total_active_users: 300,
-	}}
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="PATCH"
+  json={{
+    name: "webshop-waiting-room",
+    host: "example.com",
+    new_users_per_minute: 200,
+    total_active_users: 300
+  }}
 />
 
-You only need to include the fields you want to update in the payload of the PATCH request.
 
+You only need to include the fields you want to update in the payload of the PATCH request.
 ### Delete a waiting room
 
 Delete a waiting room by appending the following endpoint in the [Waiting Room API](https://api.cloudflare.com#waiting-room-delete-waiting-room) to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="DELETE"
-/>
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="DELETE"
+/>
\ No newline at end of file
diff --git a/src/content/docs/waiting-room/how-to/index.mdx b/src/content/docs/waiting-room/how-to/index.mdx
index 38bb6f03248845f..be1f971a0c6909b 100644
--- a/src/content/docs/waiting-room/how-to/index.mdx
+++ b/src/content/docs/waiting-room/how-to/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Common tasks
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 When working with Cloudflare Waiting Room, you will commonly perform the following tasks:
 
diff --git a/src/content/docs/waiting-room/how-to/json-response.mdx b/src/content/docs/waiting-room/how-to/json-response.mdx
index 71bc059dc58e13a..4851e4a1a5bc96a 100644
--- a/src/content/docs/waiting-room/how-to/json-response.mdx
+++ b/src/content/docs/waiting-room/how-to/json-response.mdx
@@ -65,11 +65,13 @@ In a browser environment, the page automatically refreshes every `refreshInterva
 These are some of the places where the JSON-friendly response can be consumed (this list is not exhaustive):
 
 1. In a mobile app traffic
+
    - **Integrate Waiting Room variables** – Create a new template in your mobile app to receive the JSON response. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Allow cookies** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your mobile app will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Consume JSON data** - Make a request to the Waiting Room endpoint with the `Accept: application/json` header.
 
 2. Inside Cloudflare Workers (or in your own backend service)
+
    - **Integrate Waiting Room variables** – Expect a JSON response in your backend API. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Include cookies in the request header** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your backend API will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Enable JSON response** - Via the dashboard or via the API.
diff --git a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
index 00fa24999781e3f..f17f0406cc79484 100644
--- a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
 title: Monitor waiting room status
 sidebar:
   order: 3
+
 ---
 
 import { APIRequest } from "~/components";
@@ -22,37 +23,37 @@ Open the **Waiting Room** dashboard to view the list of your waiting rooms.
 
 The **Status** column displays the current state of the waiting room:
 
-- **Not queueing**:
-  - Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
-  - Shows estimated number of users in the application.
-- **Queueing**:
-  - Waiting room enabled and sending visitors to waiting room.
-  - Shows estimated number of users in the queue.
-  - On hover, shows maximum wait time expected for users.
-- **Disabled**: The waiting room is suspended.
-- **Queue-all**:
-  - Forces all traffic to queue in the waiting room.
-  - On hover, shows estimated number of users in the queue.
+* **Not queueing**:
+  * Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
+  * Shows estimated number of users in the application.
+* **Queueing**:
+  * Waiting room enabled and sending visitors to waiting room.
+  * Shows estimated number of users in the queue.
+  * On hover, shows maximum wait time expected for users.
+* **Disabled**: The waiting room is suspended.
+* **Queue-all**:
+  * Forces all traffic to queue in the waiting room.
+  * On hover, shows estimated number of users in the queue.
 
 ## Status in the API
 
 [Check whether traffic is queueing in a configured waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) by appending the following endpoint to the Cloudflare API base URL:
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
-	method="GET"
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
+  method="GET"
 />
 
 The response is:
 
-- `queueing` if visitors are currently queueing in the waiting room.
-- `not_queueing` if the room is empty or if the waiting room is suspended.
+* `queueing` if visitors are currently queueing in the waiting room.
+* `not_queueing` if the room is empty or if the waiting room is suspended.
 
 To check whether a configured waiting room is suspended or whether the traffic is force-queued to the waiting room, append the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="GET"
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="GET"
 />
 
 The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/get/) for a configured waiting room:
@@ -87,13 +88,13 @@ The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/g
 
 The value of `suspended` indicates whether a waiting room is activated or suspended:
 
-- `false`: The waiting room is activated.
-- `true`: The waiting room is suspended.
+* `false`: The waiting room is activated.
+* `true`: The waiting room is suspended.
 
 The value of `queue_all` indicates whether all traffic is forced to queue in the waiting room:
 
-- `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
-- `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
+* `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
+* `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
 
 ## Queueing activation
 
@@ -107,5 +108,5 @@ To help prevent a waiting room from active queueing, increase the values for `ne
 
 :::note
 
-Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products.
+Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products. 
 :::
diff --git a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
index 3f4ca5fb6eafa52..d8e1e831c020a7e 100644
--- a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
   - waiting-room
 sidebar:
   order: 2
+
 ---
 
 When [configuring a waiting room](/waiting-room/how-to/create-waiting-room/), you need to indicate which pages the waiting room will cover.
@@ -20,8 +21,8 @@ You cannot add any hostname and path combinations already configured for another
 
 A single waiting room can be applied to multiple custom hostnames as long as the following is true:
 
-- The apex domain is the same between the custom hostnames
-- Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
+* The apex domain is the same between the custom hostnames
+* Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
 
 ## Custom hostnames
 
diff --git a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
index 5039172c35fa4e8..3876ca31bccde46 100644
--- a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
+++ b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
@@ -6,6 +6,7 @@ products:
 title: Access Waiting Room
 sidebar:
   order: 1
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,6 @@ Use Cloudflare Waiting Room to create a holding area where users can queue to ac
 
 To access Waiting Room on the Cloudflare dashboard, go to the **Waiting Room** page.
 
-<DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
+   <DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
 
 Use the dashboard to [create, edit, update, and delete](/waiting-room/how-to/) waiting rooms.
diff --git a/src/content/docs/waiting-room/plans.mdx b/src/content/docs/waiting-room/plans.mdx
index a4041473cdfc940..29189c6fe19e6d5 100644
--- a/src/content/docs/waiting-room/plans.mdx
+++ b/src/content/docs/waiting-room/plans.mdx
@@ -10,9 +10,10 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
+
 ---
 
-import { FeatureTable, Render } from "~/components";
+import { FeatureTable, Render } from "~/components"
 
 The features available for a waiting room depend on your plan type. You can only have **one plan** per zone.
 
diff --git a/src/content/docs/waiting-room/reference/configuration-settings.mdx b/src/content/docs/waiting-room/reference/configuration-settings.mdx
index 0d6c313160fc12b..20481e7adaee0c6 100644
--- a/src/content/docs/waiting-room/reference/configuration-settings.mdx
+++ b/src/content/docs/waiting-room/reference/configuration-settings.mdx
@@ -7,18 +7,15 @@ products:
 title: Configuration settings
 sidebar:
   order: 2
+
 ---
 
-import { Description, LinkButton } from "~/components";
+import { Description, LinkButton } from "~/components"
 
 You can customize a variety of options for your waiting rooms.
 
-<LinkButton variant="primary" href="#dashboard-settings">
-	Dashboard settings
-</LinkButton>
-<LinkButton variant="secondary" href="#additional-details">
-	Additional details
-</LinkButton>
+ <LinkButton variant="primary" href="#dashboard-settings">Dashboard settings</LinkButton> <LinkButton variant="secondary" href="#additional-details">Additional details</LinkButton>
+
 
 ## Dashboard settings
 
diff --git a/src/content/docs/waiting-room/reference/index.mdx b/src/content/docs/waiting-room/reference/index.mdx
index 386e738762a9e82..4567f07d6834f80 100644
--- a/src/content/docs/waiting-room/reference/index.mdx
+++ b/src/content/docs/waiting-room/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use the following reference information when setting up and deploying your waiting rooms:
 
diff --git a/src/content/docs/waiting-room/reference/waiting-room-api.mdx b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
index 9d57a00c62e2a34..cd9d3e20bb3a293 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-api.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
@@ -4,6 +4,7 @@ description: API commands for managing waiting rooms.
 products:
   - waiting-room
 title: API commands
+
 ---
 
 Cloudflare Waiting Room redirect visitors to virtual waiting rooms when they are trying to access web pages that have high volumes of traffic.
@@ -24,17 +25,17 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 ## Manage your waiting room
 
-| Operation                                                           | Method + URL stub                                             | Notes                              |
-| ------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
-| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)    | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
-| [Create waiting room](/api/resources/waiting_rooms/methods/create/) | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
-| [Waiting room details](/api/resources/waiting_rooms/methods/get/)   | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
-| [Update waiting room](/api/resources/waiting_rooms/methods/update/) | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
-| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/) | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
-| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)    | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
+| Operation                                                                 | Method + URL stub                                             | Notes                              |
+| ------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
+| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)     | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
+| [Create waiting room](/api/resources/waiting_rooms/methods/create/)   | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
+| [Waiting room details](/api/resources/waiting_rooms/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
+| [Update waiting room](/api/resources/waiting_rooms/methods/update/)   | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
+| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/)   | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
+| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)     | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
 
 ## Fetch the current status of a waiting room
 
-| Operation                                                                                                   | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
-| ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation                                                                                        | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [Get the current status of a waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}/status` | <ul><li>Returns <code>queueing</code> if the queue is activated (clients are put in the waiting room).</li><li>Returns <code>not\_queueing</code> if the queue is not activated or if the waiting room is suspended.</li></ul> |
diff --git a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
index 999050767f022fd..fc575945d64c011 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
@@ -12,22 +12,24 @@ A waiting room only uses the `__cfwaitingroom` cookie when a visitor requests ac
 
 :::caution[Important:]
 
+
 Cloudflare Waiting Room requires the `__cfwaitingroom` cookie. When a waiting room is actively queueing, users cannot visit that host and path combination without enabling cookies.
 
+
 :::
 
 ## Cookie function
 
 The `__cfwaitingroom` cookie is used to:
 
-- Track a user's position in the waiting room queue and serve them in the correct order.
-- Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
-- To allow re-entry for a period of time (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
+* Track a user's position in the waiting room queue and serve them in the correct order.
+* Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
+* To allow re-entry for a period of time (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
 
 ## Cookie expiration time
 
-- While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
-- When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)).
+* While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
+* When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)).
 
 ## Customize cookie name
 
diff --git a/src/content/docs/waiting-room/troubleshooting.mdx b/src/content/docs/waiting-room/troubleshooting.mdx
index 0ff28fdedd01e62..79df5d5298f08bd 100644
--- a/src/content/docs/waiting-room/troubleshooting.mdx
+++ b/src/content/docs/waiting-room/troubleshooting.mdx
@@ -7,16 +7,17 @@ title: FAQ
 structured_data: true
 sidebar:
   order: 11
+
 ---
 
 Below you will find answers to our most commonly asked questions about the Waiting Room.
 
-- [Configuration](#configuration)
-- [Features and products](#features-and-products)
-- [User behavior](#user-behavior)
-- [Monitor your waiting room](#monitor-your-waiting-room)
+* [Configuration](#configuration)
+* [Features and products](#features-and-products)
+* [User behavior](#user-behavior)
+* [Monitor your waiting room](#monitor-your-waiting-room)
 
----
+***
 
 ## Configuration
 
@@ -24,6 +25,7 @@ Below you will find answers to our most commonly asked questions about the Waiti
 
 Yes. For more details, refer to [Customize a waiting room](/waiting-room/how-to/customize-waiting-room/).
 
+
 ### Why does my waiting room look different than how I designed it?
 
 If you have [customized your waiting room template](/waiting-room/how-to/customize-waiting-room):
@@ -33,8 +35,10 @@ If you have [customized your waiting room template](/waiting-room/how-to/customi
 
 :::note[Note]
 
+
 Only Enterprise customers can customize the appearance of their waiting room.
 
+
 :::
 
 ### What can I update when my waiting room is actively queueing?
@@ -43,51 +47,69 @@ You can update a [waiting room's template](/waiting-room/how-to/customize-waitin
 
 You can also update the [configuration settings](/waiting-room/reference/configuration-settings) of a waiting room, but only make these changes when necessary. These changes may impact the estimated wait time shown to end users and cause unnecessary confusion.
 
+
+
+
 ## Features and products
 
 ### Which features are included in my Waiting Room plan?
 
 To check which features are available to different plan types, refer to [Plans](/waiting-room/plans/).
 
+
+
 ### How does Waiting Room interact with other Cloudflare products?
 
 Some Cloudflare products run before a waiting room acts on traffic:
 
-- DDoS Mitigation
-- Web Application Firewall (WAF)
-- Bot Management
-- Page Rules
+* DDoS Mitigation
+* Web Application Firewall (WAF)
+* Bot Management
+* Page Rules
 
 Other Cloudflare products run after a waiting room acts on traffic:
 
-- Workers
+* Workers
+
+
+
 
 ## User behavior
 
+
 ### What happens if a user refreshes their tab when in a waiting room?
 
 A manual tab refresh has no effect on a user's position in your waiting room.
 
 However, if they close their tab and then try to access the application again during active queueing, they will lose their spot and have to go to the back of the queue.
 
+
 ### What happens if a queued user leaves the queue?
 
 When a user joins the queue, they are placed into a bucket which is their general position in line. When a user leaves the queue (closes the browser or tab), their place in line is held for five minutes after the last refresh. This grace period allows users to keep their position in line if they experience a brief disconnection. After five minutes, the grace period expires and they are no longer counted as waiting in the queue.
 
+
+
 ## Monitor your waiting room
 
+
 ### Why do I observe a few users being queued in the dashboard?
 
+
 Some users might be queued before your waiting room reaches is limit due to architectural designs. For more details on the behavior and how to fix it, refer to [​​Queueing activation](/waiting-room/how-to/monitor-waiting-room#queueing-activation).
 
+
+
 ### Why are some users not being queued in my waiting room?
 
+
 If you notice users not being queued to your waiting room, make sure the path you defined exactly matches the path of your website.
 
 The path is case-sensitive, so if you have a waiting room set up for `/Black-Friday-Sale` and users go to `/black-friday-sale`, they will bypass your waiting room.
 
 For more details, refer to [Best practices](/waiting-room/reference/best-practices).
 
+
 ### Why are users being blocked from entering my waiting room?
 
 If you have Rate Limiting, check your [rate limiting rules](/waf/rate-limiting-rules/).
@@ -96,15 +118,17 @@ The Waiting Room queue page refreshes every 20 seconds by populating the refresh
 
 Your user also might not have [cookies](/waiting-room/reference/waiting-room-cookie) enabled. If they do not enable cookies and your waiting room is actively queueing traffic, they will not reach your endpoint until the queueing stops.
 
+
 ### Why is the estimated wait time increasing for some users?
 
 Estimated wait times may increase if the rate of users leaving your site decreases. The estimated wait time is updated upon each page refresh based on the most recently available information about the rate of slots opening up on your site and the number of users ahead of the user in line. To make this increase less likely, you could limit the amount of time users are allowed to spend on your site by disabling session renewal. Be aware that, if you change your traffic settings, estimated wait times will change as well.
 
+
 ### Why is `new users per minute` low when there is capacity available?
 
 The `new users per minute` metric tracks how many users were accepted to the origin in the last minute. It is only incremented when a queued user refreshes and is accepted to the origin. If the waiting room queueing method is set to `fifo`, we will wait until all queued users in a minute-based bucket are accepted before moving to the next bucket. If many of the users in a bucket have abandoned the queue, then the waiting room must wait until their place in line expires before moving on to the next bucket. This can cause `new users per minute` to be low when only a small percentage of queued users are actually still waiting.
 
-This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting them in an infinite queue.
+This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting  them in an infinite queue.
 
 ### Why are my Waiting Room analytics and Google analytics not matching?
 
@@ -118,8 +142,8 @@ Another key difference is that Waiting Room runs on requests made to the origin,
 
 ### Why did my traffic exceed the New Users Per Minute threshold?
 
-Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally.
+Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally. 
 
 In the case of a rapid spike — rising to several thousand users within a minute — the global state propagation process takes approximately two minutes, resulting in a delay before all data centers become aware of the spike. If this information is not disseminated quickly enough to other locations, temporary overshooting may occur, particularly when lower limits are in place.
 
-This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
+This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
\ No newline at end of file
diff --git a/src/content/docs/warp-client/get-started/linux.mdx b/src/content/docs/warp-client/get-started/linux.mdx
index 5d816a7dfe1846d..8aaf86985cb9983 100644
--- a/src/content/docs/warp-client/get-started/linux.mdx
+++ b/src/content/docs/warp-client/get-started/linux.mdx
@@ -78,20 +78,19 @@ To enable [WARP+ Unlimited](/warp-client/warp-modes/#warp-unlimited) on Linux, y
 2. Go to **Settings** > **Account** and copy the **Key** value.
 3. On your Linux device, run the following command:
 
-   ```sh
-   warp-cli registration license <KEY>
-   ```
-
+	```sh
+	warp-cli registration license <KEY>
+	```
 4. Verify the new registration:
 
-   ```sh
-   warp-cli registration show
-   ```
+	```sh
+	warp-cli registration show
+	```
 
-   ```sh output
-   Account type: Unlimited
-   ...
-   ```
+	```sh output
+	Account type: Unlimited
+	...
+	```
 
 Your WARP+ Unlimited subscription is now active on this device.
 
diff --git a/src/content/docs/warp-client/known-issues-and-faq.mdx b/src/content/docs/warp-client/known-issues-and-faq.mdx
index 3f43023c46ff622..b4e0b7837fc2175 100644
--- a/src/content/docs/warp-client/known-issues-and-faq.mdx
+++ b/src/content/docs/warp-client/known-issues-and-faq.mdx
@@ -7,6 +7,7 @@ products:
 structured_data: true
 sidebar:
   order: 5
+
 ---
 
 Below you will find answers to our most commonly asked questions regarding the WARP client. If you cannot find the answer you are looking for, refer to the [community page](https://community.cloudflare.com/) to explore more resources.
@@ -15,9 +16,9 @@ Below you will find answers to our most commonly asked questions regarding the W
 
 As our [Network Map](https://www.cloudflare.com/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the server you are connecting to is not necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-- We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
-- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
-- Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
+* We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
+* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+* Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
 
 ## Does WARP reveal my IP address to websites I visit?
 
@@ -35,6 +36,7 @@ Cloudflare WARP is in part powered by [1.1.1.1](/1.1.1.1/), the world's fastest
 
 Cloudflare WARP and the 1.1.1.1 with WARP applications go through performance testing that includes battery, network and CPU on a regular basis. In addition, both applications are used by millions of users worldwide that help us stay on top of issues across a wide variety of devices, networks, sites and applications.
 
+
 ## What is the version of .NET Framework required for the Windows client?
 
 The WARP client for Windows requires .NET Framework version 4.7.2 or later to be installed on your computer.
diff --git a/src/content/docs/warp-client/legal/3rdparty.mdx b/src/content/docs/warp-client/legal/3rdparty.mdx
index 26189309784c944..10a5097703b90b5 100644
--- a/src/content/docs/warp-client/legal/3rdparty.mdx
+++ b/src/content/docs/warp-client/legal/3rdparty.mdx
@@ -5,13 +5,14 @@ pcx_content_type: reference
 description: Third-party licenses used in the WARP client.
 products:
   - warp-client
+
 ---
 
 Following is the third party license information for our desktop applications. License information for our iOS and Android clients can be found in-app.
 
 ## Windows
 
-- ### NetSparkle
+* ### NetSparkle
 
 Copyright (c) 2020 Deadpikle
 
@@ -19,7 +20,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### Reactive Extensions
+* ### Reactive Extensions
 
 Copyright (c) .NET Foundation and Contributors
 
@@ -27,7 +28,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### NLog
+* ### NLog
 
 Copyright (c) 2016, NLog
 
@@ -39,7 +40,7 @@ Redistribution and use in source and binary forms, with or without modification,
 
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### Visual Studio App Center SDK for .NET
+* ### Visual Studio App Center SDK for .NET
 
 Copyright (c) Microsoft Corporation
 
@@ -49,9 +50,9 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### Font-Awesome-WPF
+* ### Font-Awesome-WPF
 
 Copyright (c) 2014-2016 charri
 
@@ -61,7 +62,7 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### WpfScreenHelper
+* ### WpfScreenHelper
 
 Copyright (c) 2014 Michael Denny
 
@@ -73,7 +74,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ## Mac
 
-- ### Sparkle
+* ### Sparkle
 
 Copyright (c) 2006-2013 Andy Matuschak.
 Copyright (c) 2009-2013 Elgato Systems GmbH.
@@ -88,7 +89,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### ITSwitch
+* ### ITSwitch
 
 Copyright 2014 Ilija Tovilo
 
@@ -98,7 +99,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-- ### Visual Studio App Center SDK for Apple platforms
+* ### Visual Studio App Center SDK for Apple platforms
 
 Copyright (c) Microsoft Corporation
 
@@ -108,7 +109,7 @@ MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ## Rust
 
@@ -118,21 +119,22 @@ This section lists the licenses of the projects used in cargo-about.
 
 Overview of licenses:
 
-- [MIT](#mit-license) (54)
-- [Apache](#apache-license-20) (41)
-- [BSD](#bsd-3-clause-new-or-revised-license) (8)
-- [BSD](#bsd-2-clause-simplified-license) (3)
-- [ISC](#isc-license) (3)
-- [BSD](#bsd-zero-clause-license) (2)
-- [Mozilla](#mozilla-public-license-20) (2)
-- [OpenSSL](#openssl-license) (1)
+* [MIT](#mit-license) (54)
+* [Apache](#apache-license-20) (41)
+* [BSD](#bsd-3-clause-new-or-revised-license) (8)
+* [BSD](#bsd-2-clause-simplified-license) (3)
+* [ISC](#isc-license) (3)
+* [BSD](#bsd-zero-clause-license) (2)
+* [Mozilla](#mozilla-public-license-20) (2)
+* [OpenSSL](#openssl-license) (1)
 
 All license text:
 
-- ### BSD Zero Clause License
+* ### BSD Zero Clause License
 
   #### Used by:
-  - [managed](https://github.com/m-labs/rust-managed.git)
+
+  * [managed](https://github.com/m-labs/rust-managed.git)
 
   Copyright (C) 2017 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -147,10 +149,11 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### BSD Zero Clause License
+* ### BSD Zero Clause License
 
   #### Used by:
-  - [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
+
+  * [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
 
   Copyright (C) 2016 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -165,135 +168,136 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [addr](https://github.com/addr-rs/addr)
-  - [addr2line](https://github.com/gimli-rs/addr2line)
-  - [anyhow](https://github.com/dtolnay/anyhow)
-  - [arc-swap](https://github.com/vorner/arc-swap)
-  - [async-trait](https://github.com/dtolnay/async-trait)
-  - [autocfg](https://github.com/cuviper/autocfg)
-  - [backoff](https://github.com/ihrwein/backoff)
-  - [backtrace](https://github.com/rust-lang/backtrace-rs)
-  - [base64](https://github.com/marshallpierce/rust-base64)
-  - [bitflags](https://github.com/bitflags/bitflags)
-  - [bumpalo](https://github.com/fitzgen/bumpalo)
-  - [bzip2](https://github.com/alexcrichton/bzip2-rs)
-  - [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
-  - [cache-padded](https://github.com/stjepang/cache-padded)
-  - [cc](https://github.com/alexcrichton/cc-rs)
-  - [cfg-if](https://github.com/alexcrichton/cfg-if)
-  - [concurrent-queue](https://github.com/stjepang/concurrent-queue)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
-  - [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
-  - [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
-  - [ct-logs](https://github.com/ctz/ct-logs)
-  - [either](https://github.com/bluss/either)
-  - [errno](https://github.com/lambda-fairy/rust-errno)
-  - [error-chain](https://github.com/rust-lang-nursery/error-chain)
-  - [event-listener](https://github.com/stjepang/event-listener)
-  - [flate2](https://github.com/rust-lang/flate2-rs)
-  - [fnv](https://github.com/servo/rust-fnv)
-  - [form_urlencoded](https://github.com/servo/rust-url)
-  - [gcc](https://github.com/alexcrichton/gcc-rs)
-  - [getopts](https://github.com/rust-lang/getopts)
-  - [gimli](https://github.com/gimli-rs/gimli)
-  - [hashbrown](https://github.com/rust-lang/hashbrown)
-  - [heck](https://github.com/withoutboats/heck)
-  - [hermit-abi](https://github.com/hermitcore/libhermit-rs)
-  - [httparse](https://github.com/seanmonstar/httparse)
-  - [hyper-rustls](https://github.com/ctz/hyper-rustls)
-  - [idna](https://github.com/servo/rust-url/)
-  - [indexmap](https://github.com/bluss/indexmap)
-  - [itoa](https://github.com/dtolnay/itoa)
-  - [jni](https://github.com/jni-rs/jni-rs)
-  - [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
-  - [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs)
-  - [libc](https://github.com/rust-lang/libc)
-  - [lock_api](https://github.com/Amanieu/parking_lot)
-  - [match_cfg](https://github.com/gnzlbg/match_cfg)
-  - [mime](https://github.com/hyperium/mime)
-  - [miow](https://github.com/yoshuawuyts/miow)
-  - [num](https://github.com/rust-num/num)
-  - [num](https://github.com/rust-num/num)
-  - [num-bigint](https://github.com/rust-num/num-bigint)
-  - [num-complex](https://github.com/rust-num/num-complex)
-  - [num-complex](https://github.com/rust-num/num-complex)
-  - [num-integer](https://github.com/rust-num/num-integer)
-  - [num-iter](https://github.com/rust-num/num-iter)
-  - [num-rational](https://github.com/rust-num/num-rational)
-  - [num-rational](https://github.com/rust-num/num-rational)
-  - [num-traits](https://github.com/rust-num/num-traits)
-  - [num_cpus](https://github.com/seanmonstar/num_cpus)
-  - [object](https://github.com/gimli-rs/object)
-  - [once_cell](https://github.com/matklad/once_cell)
-  - [openssl-probe](https://github.com/alexcrichton/openssl-probe)
-  - [parking_lot](https://github.com/Amanieu/parking_lot)
-  - [parking_lot_core](https://github.com/Amanieu/parking_lot)
-  - [paste](https://github.com/dtolnay/paste)
-  - [percent-encoding](https://github.com/servo/rust-url/)
-  - [pfctl](https://github.com/mullvad/pfctl-rs)
-  - [pkg-config](https://github.com/rust-lang/pkg-config-rs)
-  - [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
-  - [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
-  - [proc-macro2](https://github.com/alexcrichton/proc-macro2)
-  - [quote](https://github.com/dtolnay/quote)
-  - [regex](https://github.com/rust-lang/regex)
-  - [regex-syntax](https://github.com/rust-lang/regex)
-  - [reqwest](https://github.com/seanmonstar/reqwest)
-  - [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
-  - [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
-  - [rustversion](https://github.com/dtolnay/rustversion)
-  - [scopeguard](https://github.com/bluss/scopeguard)
-  - [sct](https://github.com/ctz/sct.rs)
-  - [secret-service](https://github.com/hwchen/secret-service-rs.git)
-  - [semver](https://github.com/dtolnay/semver)
-  - [serde](https://github.com/serde-rs/serde)
-  - [serde_derive](https://github.com/serde-rs/serde)
-  - [serde_json](https://github.com/serde-rs/json)
-  - [serde_repr](https://github.com/dtolnay/serde-repr)
-  - [signal-hook-registry](https://github.com/vorner/signal-hook)
-  - [size_format](https://github.com/aticu/size_format)
-  - [slog](https://github.com/slog-rs/slog)
-  - [slog-async](https://github.com/slog-rs/async)
-  - [slog-scope](https://github.com/slog-rs/scope)
-  - [slog-stdlog](https://github.com/slog-rs/stdlog)
-  - [slog-term](https://github.com/slog-rs/term)
-  - [smallvec](https://github.com/servo/rust-smallvec)
-  - [socket2](https://github.com/alexcrichton/socket2-rs)
-  - [socket2](https://github.com/rust-lang/socket2)
-  - [syn](https://github.com/dtolnay/syn)
-  - [tempfile](https://github.com/Stebalien/tempfile)
-  - [term](https://github.com/Stebalien/term)
-  - [thiserror](https://github.com/dtolnay/thiserror)
-  - [thiserror-impl](https://github.com/dtolnay/thiserror)
-  - [thread_local](https://github.com/Amanieu/thread_local-rs)
-  - [time](https://github.com/time-rs/time)
-  - [toml](https://github.com/alexcrichton/toml-rs)
-  - [tungstenite](https://github.com/snapview/tungstenite-rs)
-  - [unicode-bidi](https://github.com/servo/unicode-bidi)
-  - [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
-  - [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
-  - [unicode-width](https://github.com/unicode-rs/unicode-width)
-  - [unicode-xid](https://github.com/unicode-rs/unicode-xid)
-  - [url](https://github.com/servo/rust-url)
-  - [version_check](https://github.com/SergioBenitez/version_check)
-  - [wasi](https://github.com/bytecodealliance/wasi)
-  - [wasi](https://github.com/bytecodealliance/wasi)
-  - [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
-  - [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
-  - [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
-  - [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
-  - [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
-  - [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
-  - [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
+
+  * [addr](https://github.com/addr-rs/addr)
+  * [addr2line](https://github.com/gimli-rs/addr2line)
+  * [anyhow](https://github.com/dtolnay/anyhow)
+  * [arc-swap](https://github.com/vorner/arc-swap)
+  * [async-trait](https://github.com/dtolnay/async-trait)
+  * [autocfg](https://github.com/cuviper/autocfg)
+  * [backoff](https://github.com/ihrwein/backoff)
+  * [backtrace](https://github.com/rust-lang/backtrace-rs)
+  * [base64](https://github.com/marshallpierce/rust-base64)
+  * [bitflags](https://github.com/bitflags/bitflags)
+  * [bumpalo](https://github.com/fitzgen/bumpalo)
+  * [bzip2](https://github.com/alexcrichton/bzip2-rs)
+  * [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
+  * [cache-padded](https://github.com/stjepang/cache-padded)
+  * [cc](https://github.com/alexcrichton/cc-rs)
+  * [cfg-if](https://github.com/alexcrichton/cfg-if)
+  * [concurrent-queue](https://github.com/stjepang/concurrent-queue)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
+  * [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
+  * [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
+  * [ct-logs](https://github.com/ctz/ct-logs)
+  * [either](https://github.com/bluss/either)
+  * [errno](https://github.com/lambda-fairy/rust-errno)
+  * [error-chain](https://github.com/rust-lang-nursery/error-chain)
+  * [event-listener](https://github.com/stjepang/event-listener)
+  * [flate2](https://github.com/rust-lang/flate2-rs)
+  * [fnv](https://github.com/servo/rust-fnv)
+  * [form\_urlencoded](https://github.com/servo/rust-url)
+  * [gcc](https://github.com/alexcrichton/gcc-rs)
+  * [getopts](https://github.com/rust-lang/getopts)
+  * [gimli](https://github.com/gimli-rs/gimli)
+  * [hashbrown](https://github.com/rust-lang/hashbrown)
+  * [heck](https://github.com/withoutboats/heck)
+  * [hermit-abi](https://github.com/hermitcore/libhermit-rs)
+  * [httparse](https://github.com/seanmonstar/httparse)
+  * [hyper-rustls](https://github.com/ctz/hyper-rustls)
+  * [idna](https://github.com/servo/rust-url/)
+  * [indexmap](https://github.com/bluss/indexmap)
+  * [itoa](https://github.com/dtolnay/itoa)
+  * [jni](https://github.com/jni-rs/jni-rs)
+  * [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
+  * [lazy\_static](https://github.com/rust-lang-nursery/lazy-static.rs)
+  * [libc](https://github.com/rust-lang/libc)
+  * [lock\_api](https://github.com/Amanieu/parking_lot)
+  * [match\_cfg](https://github.com/gnzlbg/match_cfg)
+  * [mime](https://github.com/hyperium/mime)
+  * [miow](https://github.com/yoshuawuyts/miow)
+  * [num](https://github.com/rust-num/num)
+  * [num](https://github.com/rust-num/num)
+  * [num-bigint](https://github.com/rust-num/num-bigint)
+  * [num-complex](https://github.com/rust-num/num-complex)
+  * [num-complex](https://github.com/rust-num/num-complex)
+  * [num-integer](https://github.com/rust-num/num-integer)
+  * [num-iter](https://github.com/rust-num/num-iter)
+  * [num-rational](https://github.com/rust-num/num-rational)
+  * [num-rational](https://github.com/rust-num/num-rational)
+  * [num-traits](https://github.com/rust-num/num-traits)
+  * [num\_cpus](https://github.com/seanmonstar/num_cpus)
+  * [object](https://github.com/gimli-rs/object)
+  * [once\_cell](https://github.com/matklad/once_cell)
+  * [openssl-probe](https://github.com/alexcrichton/openssl-probe)
+  * [parking\_lot](https://github.com/Amanieu/parking_lot)
+  * [parking\_lot\_core](https://github.com/Amanieu/parking_lot)
+  * [paste](https://github.com/dtolnay/paste)
+  * [percent-encoding](https://github.com/servo/rust-url/)
+  * [pfctl](https://github.com/mullvad/pfctl-rs)
+  * [pkg-config](https://github.com/rust-lang/pkg-config-rs)
+  * [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
+  * [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
+  * [proc-macro2](https://github.com/alexcrichton/proc-macro2)
+  * [quote](https://github.com/dtolnay/quote)
+  * [regex](https://github.com/rust-lang/regex)
+  * [regex-syntax](https://github.com/rust-lang/regex)
+  * [reqwest](https://github.com/seanmonstar/reqwest)
+  * [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
+  * [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
+  * [rustversion](https://github.com/dtolnay/rustversion)
+  * [scopeguard](https://github.com/bluss/scopeguard)
+  * [sct](https://github.com/ctz/sct.rs)
+  * [secret-service](https://github.com/hwchen/secret-service-rs.git)
+  * [semver](https://github.com/dtolnay/semver)
+  * [serde](https://github.com/serde-rs/serde)
+  * [serde\_derive](https://github.com/serde-rs/serde)
+  * [serde\_json](https://github.com/serde-rs/json)
+  * [serde\_repr](https://github.com/dtolnay/serde-repr)
+  * [signal-hook-registry](https://github.com/vorner/signal-hook)
+  * [size\_format](https://github.com/aticu/size_format)
+  * [slog](https://github.com/slog-rs/slog)
+  * [slog-async](https://github.com/slog-rs/async)
+  * [slog-scope](https://github.com/slog-rs/scope)
+  * [slog-stdlog](https://github.com/slog-rs/stdlog)
+  * [slog-term](https://github.com/slog-rs/term)
+  * [smallvec](https://github.com/servo/rust-smallvec)
+  * [socket2](https://github.com/alexcrichton/socket2-rs)
+  * [socket2](https://github.com/rust-lang/socket2)
+  * [syn](https://github.com/dtolnay/syn)
+  * [tempfile](https://github.com/Stebalien/tempfile)
+  * [term](https://github.com/Stebalien/term)
+  * [thiserror](https://github.com/dtolnay/thiserror)
+  * [thiserror-impl](https://github.com/dtolnay/thiserror)
+  * [thread\_local](https://github.com/Amanieu/thread_local-rs)
+  * [time](https://github.com/time-rs/time)
+  * [toml](https://github.com/alexcrichton/toml-rs)
+  * [tungstenite](https://github.com/snapview/tungstenite-rs)
+  * [unicode-bidi](https://github.com/servo/unicode-bidi)
+  * [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
+  * [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
+  * [unicode-width](https://github.com/unicode-rs/unicode-width)
+  * [unicode-xid](https://github.com/unicode-rs/unicode-xid)
+  * [url](https://github.com/servo/rust-url)
+  * [version\_check](https://github.com/SergioBenitez/version_check)
+  * [wasi](https://github.com/bytecodealliance/wasi)
+  * [wasi](https://github.com/bytecodealliance/wasi)
+  * [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
+  * [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
+  * [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
+  * [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
+  * [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
+  * [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
+  * [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
 
     ```
                           Apache License
@@ -302,6 +306,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -500,10 +505,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [adler](https://github.com/jonas-schievink/adler.git)
+
+  * [adler](https://github.com/jonas-schievink/adler.git)
 
     ```
                           Apache License
@@ -512,6 +518,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -710,32 +717,33 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [aes](https://github.com/RustCrypto/block-ciphers)
-  - [aes-soft](https://github.com/RustCrypto/block-ciphers)
-  - [aesni](https://github.com/RustCrypto/block-ciphers)
-  - [block-buffer](https://github.com/RustCrypto/utils)
-  - [block-buffer](https://github.com/RustCrypto/utils)
-  - [block-modes](https://github.com/RustCrypto/block-ciphers)
-  - [block-padding](https://github.com/RustCrypto/utils)
-  - [block-padding](https://github.com/RustCrypto/utils)
-  - [byte-tools](https://github.com/RustCrypto/utils)
-  - [cipher](https://github.com/RustCrypto/traits)
-  - [cpufeatures](https://github.com/RustCrypto/utils)
-  - [crypto-mac](https://github.com/RustCrypto/traits)
-  - [crypto-mac](https://github.com/RustCrypto/traits)
-  - [digest](https://github.com/RustCrypto/traits)
-  - [digest](https://github.com/RustCrypto/traits)
-  - [fake-simd](https://github.com/RustCrypto/utils)
-  - [hmac](https://github.com/RustCrypto/MACs)
-  - [hmac](https://github.com/RustCrypto/MACs)
-  - [opaque-debug](https://github.com/RustCrypto/utils)
-  - [opaque-debug](https://github.com/RustCrypto/utils)
-  - [sha-1](https://github.com/RustCrypto/hashes)
-  - [sha2](https://github.com/RustCrypto/hashes)
-  - [sha2](https://github.com/RustCrypto/hashes)
+
+  * [aes](https://github.com/RustCrypto/block-ciphers)
+  * [aes-soft](https://github.com/RustCrypto/block-ciphers)
+  * [aesni](https://github.com/RustCrypto/block-ciphers)
+  * [block-buffer](https://github.com/RustCrypto/utils)
+  * [block-buffer](https://github.com/RustCrypto/utils)
+  * [block-modes](https://github.com/RustCrypto/block-ciphers)
+  * [block-padding](https://github.com/RustCrypto/utils)
+  * [block-padding](https://github.com/RustCrypto/utils)
+  * [byte-tools](https://github.com/RustCrypto/utils)
+  * [cipher](https://github.com/RustCrypto/traits)
+  * [cpufeatures](https://github.com/RustCrypto/utils)
+  * [crypto-mac](https://github.com/RustCrypto/traits)
+  * [crypto-mac](https://github.com/RustCrypto/traits)
+  * [digest](https://github.com/RustCrypto/traits)
+  * [digest](https://github.com/RustCrypto/traits)
+  * [fake-simd](https://github.com/RustCrypto/utils)
+  * [hmac](https://github.com/RustCrypto/MACs)
+  * [hmac](https://github.com/RustCrypto/MACs)
+  * [opaque-debug](https://github.com/RustCrypto/utils)
+  * [opaque-debug](https://github.com/RustCrypto/utils)
+  * [sha-1](https://github.com/RustCrypto/hashes)
+  * [sha2](https://github.com/RustCrypto/hashes)
+  * [sha2](https://github.com/RustCrypto/hashes)
 
     ```
                           Apache License
@@ -744,6 +752,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -940,16 +949,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ascii](https://github.com/tomprogrammer/rust-ascii)
+
+  * [ascii](https://github.com/tomprogrammer/rust-ascii)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1150,14 +1161,15 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [async-channel](https://github.com/smol-rs/async-channel)
-  - [ipconfig](https://github.com/liranringel/ipconfig)
-  - [log](https://github.com/rust-lang/log)
-  - [safemem](https://github.com/abonander/safemem)
-  - [uuid](https://github.com/uuid-rs/uuid)
+
+  * [async-channel](https://github.com/smol-rs/async-channel)
+  * [ipconfig](https://github.com/liranringel/ipconfig)
+  * [log](https://github.com/rust-lang/log)
+  * [safemem](https://github.com/abonander/safemem)
+  * [uuid](https://github.com/uuid-rs/uuid)
 
     ```
                           Apache License
@@ -1166,6 +1178,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1364,30 +1377,32 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [cesu8](https://github.com/emk/cesu8-rs)
-  - [ident_case](https://github.com/TedDriggs/ident_case)
-  - [ioctl-sys](https://github.com/jmesmon/ioctl)
-  - [psl](https://github.com/addr-rs/psl)
-  - [psl-types](https://github.com/addr-rs/psl-types)
-  - [rustls](https://github.com/ctz/rustls)
-  - [security-framework](https://github.com/kornelski/rust-security-framework)
-  - [security-framework](https://github.com/kornelski/rust-security-framework)
-  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  - [system-configuration](https://github.com/mullvad/system-configuration-rs)
-  - [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
-  - [tinyvec_macros](https://github.com/Soveu/tinyvec_macros)
-  - [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
-  - [winapi-x86_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+
+  * [cesu8](https://github.com/emk/cesu8-rs)
+  * [ident\_case](https://github.com/TedDriggs/ident_case)
+  * [ioctl-sys](https://github.com/jmesmon/ioctl)
+  * [psl](https://github.com/addr-rs/psl)
+  * [psl-types](https://github.com/addr-rs/psl-types)
+  * [rustls](https://github.com/ctz/rustls)
+  * [security-framework](https://github.com/kornelski/rust-security-framework)
+  * [security-framework](https://github.com/kornelski/rust-security-framework)
+  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  * [system-configuration](https://github.com/mullvad/system-configuration-rs)
+  * [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
+  * [tinyvec\_macros](https://github.com/Soveu/tinyvec_macros)
+  * [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  * [winapi-x86\_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
@@ -1409,6 +1424,7 @@ All license text:
   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
 
   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
   2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
 
   3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
@@ -1455,10 +1471,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [chrono](https://github.com/chronotope/chrono)
+
+  * [chrono](https://github.com/chronotope/chrono)
 
   Rust-chrono is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2]. Copyright (c) 2014--2017, Kang Seonghoon and
@@ -1698,23 +1715,24 @@ All license text:
   limitations under the License.
   ```
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [crc32fast](https://github.com/srijs/rust-crc32fast)
-  - [derive_builder](https://github.com/colin-kiegel/rust-derive-builder)
-  - [derive_builder_core](https://github.com/colin-kiegel/rust-derive-builder)
-  - [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
-  - [hex](https://github.com/KokaKiwi/rust-hex)
-  - [jni-sys](https://github.com/sfackler/rust-jni-sys)
-  - [log-panics](https://github.com/sfackler/rust-log-panics)
-  - [quick-error](http://github.com/tailhook/quick-error)
-  - [resolv-conf](http://github.com/tailhook/resolv-conf)
-  - [trust-dns-https](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
-  - [unreachable](https://github.com/reem/rust-unreachable.git)
+
+  * [crc32fast](https://github.com/srijs/rust-crc32fast)
+  * [derive\_builder](https://github.com/colin-kiegel/rust-derive-builder)
+  * [derive\_builder\_core](https://github.com/colin-kiegel/rust-derive-builder)
+  * [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
+  * [hex](https://github.com/KokaKiwi/rust-hex)
+  * [jni-sys](https://github.com/sfackler/rust-jni-sys)
+  * [log-panics](https://github.com/sfackler/rust-log-panics)
+  * [quick-error](http://github.com/tailhook/quick-error)
+  * [resolv-conf](http://github.com/tailhook/resolv-conf)
+  * [trust-dns-https](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
+  * [unreachable](https://github.com/reem/rust-unreachable.git)
 
     ```
                              Apache License
@@ -1723,6 +1741,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1923,16 +1942,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dbus](https://github.com/diwic/dbus-rs)
+
+  * [dbus](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2133,17 +2154,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dbus](https://github.com/diwic/dbus-rs)
-  - [libdbus-sys](https://github.com/diwic/dbus-rs)
+
+  * [dbus](https://github.com/diwic/dbus-rs)
+  * [libdbus-sys](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2344,10 +2367,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [deadqueue](https://github.com/bikeshedder/deadqueue)
+
+  * [deadqueue](https://github.com/bikeshedder/deadqueue)
 
     ```
                              Apache License
@@ -2356,6 +2380,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2556,12 +2581,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [diff](https://github.com/utkarshkukreti/diff.rs)
-  - [ipnetwork](https://github.com/achanda/ipnetwork)
-  - [winapi](https://github.com/retep998/winapi-rs)
+
+  * [diff](https://github.com/utkarshkukreti/diff.rs)
+  * [ipnetwork](https://github.com/achanda/ipnetwork)
+  * [winapi](https://github.com/retep998/winapi-rs)
 
     ```
                              Apache License
@@ -2570,6 +2596,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2770,13 +2797,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dirs](https://github.com/soc/dirs-rs)
-  - [dirs-next](https://github.com/xdg-rs/dirs)
-  - [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
-  - [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
+
+  * [dirs](https://github.com/soc/dirs-rs)
+  * [dirs-next](https://github.com/xdg-rs/dirs)
+  * [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
+  * [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
 
     ```
                           Apache License
@@ -2785,6 +2813,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2954,11 +2983,12 @@ All license text:
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [encoding_rs](https://github.com/hsivonen/encoding_rs)
-  - [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
+
+  * [encoding\_rs](https://github.com/hsivonen/encoding_rs)
+  * [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
 
     ```
                              Apache License
@@ -2967,6 +2997,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3167,10 +3198,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [err-derive](https://gitlab.com/torkleyy/err-derive)
+
+  * [err-derive](https://gitlab.com/torkleyy/err-derive)
 
     ```
                              Apache License
@@ -3179,6 +3211,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3379,18 +3412,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [futures](https://github.com/rust-lang/futures-rs)
-  - [futures-channel](https://github.com/rust-lang/futures-rs)
-  - [futures-core](https://github.com/rust-lang/futures-rs)
-  - [futures-executor](https://github.com/rust-lang/futures-rs)
-  - [futures-io](https://github.com/rust-lang/futures-rs)
-  - [futures-macro](https://github.com/rust-lang/futures-rs)
-  - [futures-sink](https://github.com/rust-lang/futures-rs)
-  - [futures-task](https://github.com/rust-lang/futures-rs)
-  - [futures-util](https://github.com/rust-lang/futures-rs)
+
+  * [futures](https://github.com/rust-lang/futures-rs)
+  * [futures-channel](https://github.com/rust-lang/futures-rs)
+  * [futures-core](https://github.com/rust-lang/futures-rs)
+  * [futures-executor](https://github.com/rust-lang/futures-rs)
+  * [futures-io](https://github.com/rust-lang/futures-rs)
+  * [futures-macro](https://github.com/rust-lang/futures-rs)
+  * [futures-sink](https://github.com/rust-lang/futures-rs)
+  * [futures-task](https://github.com/rust-lang/futures-rs)
+  * [futures-util](https://github.com/rust-lang/futures-rs)
 
     ```
                           Apache License
@@ -3399,6 +3433,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3598,19 +3633,20 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [getrandom](https://github.com/rust-random/getrandom)
-  - [getrandom](https://github.com/rust-random/getrandom)
-  - [rand](https://github.com/rust-random/rand)
-  - [rand](https://github.com/rust-random/rand)
-  - [rand_chacha](https://github.com/rust-random/rand)
-  - [rand_chacha](https://github.com/rust-random/rand)
-  - [rand_core](https://github.com/rust-random/rand)
-  - [rand_core](https://github.com/rust-random/rand)
-  - [rand_hc](https://github.com/rust-random/rand)
-  - [rand_hc](https://github.com/rust-random/rand)
+
+  * [getrandom](https://github.com/rust-random/getrandom)
+  * [getrandom](https://github.com/rust-random/getrandom)
+  * [rand](https://github.com/rust-random/rand)
+  * [rand](https://github.com/rust-random/rand)
+  * [rand\_chacha](https://github.com/rust-random/rand)
+  * [rand\_chacha](https://github.com/rust-random/rand)
+  * [rand\_core](https://github.com/rust-random/rand)
+  * [rand\_core](https://github.com/rust-random/rand)
+  * [rand\_hc](https://github.com/rust-random/rand)
+  * [rand\_hc](https://github.com/rust-random/rand)
 
     ```
                           Apache License
@@ -3619,6 +3655,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3817,10 +3854,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [hkdf](https://github.com/RustCrypto/KDFs/)
+
+  * [hkdf](https://github.com/RustCrypto/KDFs/)
 
     ```
                           Apache License
@@ -3829,6 +3867,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4025,10 +4064,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [http](https://github.com/hyperium/http)
+
+  * [http](https://github.com/hyperium/http)
 
     ```
                           Apache License
@@ -4037,6 +4077,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4235,16 +4276,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [httpdate](https://github.com/pyfisch/httpdate)
+
+  * [httpdate](https://github.com/pyfisch/httpdate)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction,
@@ -4303,6 +4346,7 @@ All license text:
   "Contributor" shall mean Licensor and any individual or Legal Entity
   on behalf of whom a Contribution has been received by Licensor and
   subsequently incorporated within the Work.
+
   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
@@ -4366,6 +4410,7 @@ All license text:
   for any such Derivative Works as a whole, provided Your use,
   reproduction, and distribution of the Work otherwise complies with
   the conditions stated in this License.
+
   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
@@ -4439,10 +4484,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
+
+  * [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
 
     ```
                              Apache License
@@ -4451,6 +4497,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4652,10 +4699,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ipnet](https://github.com/krisprice/ipnet)
+
+  * [ipnet](https://github.com/krisprice/ipnet)
 
     ```
                              Apache License
@@ -4664,6 +4712,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4864,10 +4913,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [keyring](https://github.com/hwchen/keyring-rs.git)
+
+  * [keyring](https://github.com/hwchen/keyring-rs.git)
 
     ```
                           Apache License
@@ -4876,6 +4926,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5074,13 +5125,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
-  - [lru-cache](https://github.com/contain-rs/lru-cache)
-  - [process_path](https://github.com/wesleywiser/process_path)
-  - [vec_map](https://github.com/contain-rs/vec-map)
+
+  * [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
+  * [lru-cache](https://github.com/contain-rs/lru-cache)
+  * [process\_path](https://github.com/wesleywiser/process_path)
+  * [vec\_map](https://github.com/contain-rs/vec-map)
 
     ```
                           Apache License
@@ -5089,6 +5141,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5287,13 +5340,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [miniz_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
-  - [pin-project](https://github.com/taiki-e/pin-project)
-  - [pin-project-internal](https://github.com/taiki-e/pin-project)
-  - [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
+
+  * [miniz\_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
+  * [pin-project](https://github.com/taiki-e/pin-project)
+  * [pin-project-internal](https://github.com/taiki-e/pin-project)
+  * [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
 
     ```
                              Apache License
@@ -5302,6 +5356,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5473,10 +5528,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ntapi](https://github.com/MSxDOS/ntapi)
+
+  * [ntapi](https://github.com/MSxDOS/ntapi)
 
     ```
                              Apache License
@@ -5485,6 +5541,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5685,10 +5742,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
+
+  * [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
 
     ```
                           Apache License
@@ -5697,6 +5755,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5895,10 +5954,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
+
+  * [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
 
     ```
                           Apache License
@@ -5907,6 +5967,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6103,10 +6164,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
+
+  * [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6115,6 +6177,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6313,10 +6376,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
+
+  * [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6325,6 +6389,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6523,10 +6588,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [remove_dir_all](https://github.com/XAMPPRocky/remove_dir_all.git)
+
+  * [remove\_dir\_all](https://github.com/XAMPPRocky/remove_dir_all.git)
 
     ```
                           Apache License
@@ -6535,6 +6601,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6722,10 +6789,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [rolling-file](https://github.com/Axcient/rolling-file-rs)
+
+  * [rolling-file](https://github.com/Axcient/rolling-file-rs)
 
   rolling-file is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2].
@@ -6966,10 +7034,11 @@ All license text:
   limitations under the License.
   ```
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ryu](https://github.com/dtolnay/ryu)
+
+  * [ryu](https://github.com/dtolnay/ryu)
 
     ```
                              Apache License
@@ -6978,6 +7047,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7178,11 +7248,12 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [serde_urlencoded](https://github.com/nox/serde_urlencoded)
-  - [utf-8](https://github.com/SimonSapin/rust-utf8)
+
+  * [serde\_urlencoded](https://github.com/nox/serde_urlencoded)
+  * [utf-8](https://github.com/SimonSapin/rust-utf8)
 
     ```
                           Apache License
@@ -7191,6 +7262,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7362,10 +7434,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [tinyvec](https://github.com/Lokathor/tinyvec)
+
+  * [tinyvec](https://github.com/Lokathor/tinyvec)
 
     ```
                              Apache License
@@ -7374,6 +7447,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7574,10 +7648,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [tokio-rustls](https://github.com/tokio-rs/tls)
+
+  * [tokio-rustls](https://github.com/tokio-rs/tls)
 
     ```
                           Apache License
@@ -7586,6 +7661,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7784,10 +7860,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [typenum](https://github.com/paholg/typenum)
+
+  * [typenum](https://github.com/paholg/typenum)
 
     ```
                           Apache License
@@ -7796,6 +7873,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7994,10 +8072,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [webbrowser](https://github.com/amodm/webbrowser-rs)
+
+  * [webbrowser](https://github.com/amodm/webbrowser-rs)
 
   Copyright (c) 2015 Amod Malviya
 
@@ -8024,6 +8103,7 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8195,10 +8275,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [widestring](https://github.com/starkat99/widestring-rs.git)
+
+  * [widestring](https://github.com/starkat99/widestring-rs.git)
 
     ```
                           Apache License
@@ -8207,6 +8288,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8405,10 +8487,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [windows-service](https://github.com/mullvad/windows-service-rs)
+
+  * [windows-service](https://github.com/mullvad/windows-service-rs)
 
     ```
                           Apache License
@@ -8417,6 +8500,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8615,14 +8699,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [winlog](https://gitlab.com/arbitrix/winlog)
+
+  * [winlog](https://gitlab.com/arbitrix/winlog)
 
   This software is licensed under either of
-  - Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
-  - MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
+
+  * Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+  * MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
 
   at your option.
 
@@ -8633,6 +8719,7 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8855,15 +8942,17 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [ip_network](https://github.com/JakubOnderka/ip_network)
+
+  * [ip\_network](https://github.com/JakubOnderka/ip_network)
 
   Copyright (c) 2017, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8881,15 +8970,17 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [ip_network_table](https://github.com/JakubOnderka/ip_network_table)
+
+  * [ip\_network\_table](https://github.com/JakubOnderka/ip_network_table)
 
   Copyright (c) 2018, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8907,17 +8998,19 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [mach](https://github.com/fitzgen/mach)
-  - [mach](https://github.com/fitzgen/mach)
+
+  * [mach](https://github.com/fitzgen/mach)
+  * [mach](https://github.com/fitzgen/mach)
 
   Copyright (c) 2015, Nick Fitzgerald
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -8936,11 +9029,12 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [app-center](https://github.com/vkrasnov/appcenter-rs)
-  - [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
+
+  * [app-center](https://github.com/vkrasnov/appcenter-rs)
+  * [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
 
   BSD 3-Clause License
 
@@ -8949,6 +9043,7 @@ All license text:
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -8971,10 +9066,11 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [boringtun](https://github.com/cloudflare/boringtun)
+
+  * [boringtun](https://github.com/cloudflare/boringtun)
 
   Copyright (c) 2019 Cloudflare, Inc. All rights reserved.
 
@@ -8988,10 +9084,11 @@ All license text:
 
   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [etherparse](https://github.com/JulianSchmid/etherparse)
+
+  * [etherparse](https://github.com/JulianSchmid/etherparse)
 
   BSD 3-Clause License
 
@@ -9023,16 +9120,18 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [instant](https://github.com/sebcrozet/instant)
+
+  * [instant](https://github.com/sebcrozet/instant)
 
   Copyright (c) 2019, Sébastien Crozet
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9055,15 +9154,17 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [nel](https://crates.io/crates/nel/0.1.4)
+
+  * [nel](https://crates.io/crates/nel/0.1.4)
 
   Copyright 2021 Cloudflare, Inc. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9086,16 +9187,18 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [subtle](https://github.com/dalek-cryptography/subtle)
+
+  * [subtle](https://github.com/dalek-cryptography/subtle)
 
   Copyright (c) 2016-2017 Isis Agora Lovecruft, Henry de Valence. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
+
   1. Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
 
@@ -9119,10 +9222,11 @@ All license text:
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [webpki](https://github.com/briansmith/webpki)
+
+  * [webpki](https://github.com/briansmith/webpki)
 
   // Copyright 2015 The Chromium Authors. All rights reserved.
   //
@@ -9152,10 +9256,11 @@ All license text:
   // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   // Copyright 2017 Brian Smith.
   //
@@ -9171,7 +9276,7 @@ All license text:
   // OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
   // CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-  \#\[macro_use]
+  \#\[macro\_use]
   pub mod constant;
 
   \#\[cfg(feature = "alloc")]
@@ -9179,10 +9284,11 @@ All license text:
 
   pub mod montgomery;
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [untrusted](https://github.com/briansmith/untrusted)
+
+  * [untrusted](https://github.com/briansmith/untrusted)
 
   // Copyright 2015-2016 Brian Smith.
   //
@@ -9198,10 +9304,11 @@ All license text:
   // ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
   // OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [webpki](https://github.com/briansmith/webpki)
+
+  * [webpki](https://github.com/briansmith/webpki)
 
   Except as otherwise noted, this project is licensed under the following
   (ISC-style) terms:
@@ -9223,14 +9330,15 @@ All license text:
   The files under third-party/chromium are licensed as described in
   third-party/chromium/LICENSE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [aho-corasick](https://github.com/BurntSushi/aho-corasick)
-  - [byteorder](https://github.com/BurntSushi/byteorder)
-  - [memchr](https://github.com/BurntSushi/memchr)
-  - [regex-automata](https://github.com/BurntSushi/regex-automata)
-  - [walkdir](https://github.com/BurntSushi/walkdir)
+
+  * [aho-corasick](https://github.com/BurntSushi/aho-corasick)
+  * [byteorder](https://github.com/BurntSushi/byteorder)
+  * [memchr](https://github.com/BurntSushi/memchr)
+  * [regex-automata](https://github.com/BurntSushi/regex-automata)
+  * [walkdir](https://github.com/BurntSushi/walkdir)
 
   The MIT License (MIT)
 
@@ -9254,10 +9362,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ansi_term](https://crates.io/crates/ansi_term)
+
+  * [ansi\_term](https://crates.io/crates/ansi_term)
 
   The MIT License (MIT)
 
@@ -9281,10 +9390,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ansi_term](https://github.com/ogham/rust-ansi-term)
+
+  * [ansi\_term](https://github.com/ogham/rust-ansi-term)
 
   The MIT License (MIT)
 
@@ -9308,10 +9418,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [atty](https://github.com/softprops/atty)
+
+  * [atty](https://github.com/softprops/atty)
 
   Copyright (c) 2015-2019 Doug Tangren
 
@@ -9334,10 +9445,11 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [bytes](https://github.com/tokio-rs/bytes)
+
+  * [bytes](https://github.com/tokio-rs/bytes)
 
   Copyright (c) 2018 Carl Lerche
 
@@ -9365,10 +9477,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [clap](https://github.com/clap-rs/clap)
+
+  * [clap](https://github.com/clap-rs/clap)
 
   The MIT License (MIT)
 
@@ -9392,10 +9505,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [combine](https://github.com/Marwes/combine)
+
+  * [combine](https://github.com/Marwes/combine)
 
   The MIT License (MIT)
 
@@ -9419,12 +9533,13 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [darling](https://github.com/TedDriggs/darling)
-  - [darling_core](https://github.com/TedDriggs/darling)
-  - [darling_macro](https://github.com/TedDriggs/darling)
+
+  * [darling](https://github.com/TedDriggs/darling)
+  * [darling\_core](https://github.com/TedDriggs/darling)
+  * [darling\_macro](https://github.com/TedDriggs/darling)
 
   MIT License
 
@@ -9448,10 +9563,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [data-encoding](https://github.com/ia0/data-encoding)
+
+  * [data-encoding](https://github.com/ia0/data-encoding)
 
   The MIT License (MIT)
 
@@ -9476,16 +9592,17 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [dispatch](http://github.com/SSheldon/rust-dispatch)
-  - [netlink-packet-core](https://github.com/little-dude/netlink)
-  - [netlink-packet-route](https://github.com/little-dude/netlink)
-  - [netlink-packet-utils](https://github.com/little-dude/netlink)
-  - [netlink-sys](https://github.com/little-dude/netlink)
-  - [tokio-macros](https://github.com/tokio-rs/tokio)
-  - [void](https://github.com/reem/rust-void.git)
+
+  * [dispatch](http://github.com/SSheldon/rust-dispatch)
+  * [netlink-packet-core](https://github.com/little-dude/netlink)
+  * [netlink-packet-route](https://github.com/little-dude/netlink)
+  * [netlink-packet-utils](https://github.com/little-dude/netlink)
+  * [netlink-sys](https://github.com/little-dude/netlink)
+  * [tokio-macros](https://github.com/tokio-rs/tokio)
+  * [void](https://github.com/reem/rust-void.git)
 
   MIT License
 
@@ -9495,10 +9612,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
+
+  * [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
 
   MIT License
 
@@ -9522,10 +9640,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
+
+  * [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
 
   MIT License
 
@@ -9549,10 +9668,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [generic-array](https://github.com/fizyk20/generic-array.git)
+
+  * [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9576,10 +9696,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [generic-array](https://github.com/fizyk20/generic-array.git)
+
+  * [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9603,10 +9724,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [h2](https://github.com/hyperium/h2)
+
+  * [h2](https://github.com/hyperium/h2)
 
   Copyright (c) 2017 h2 authors
 
@@ -9634,10 +9756,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [hostname](https://github.com/svartalf/hostname)
+
+  * [hostname](https://github.com/svartalf/hostname)
 
   MIT License
 
@@ -9662,10 +9785,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [http-body](https://github.com/hyperium/http-body)
+
+  * [http-body](https://github.com/hyperium/http-body)
 
   Copyright (c) 2019 Hyper Contributors
 
@@ -9693,10 +9817,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [hyper](https://github.com/hyperium/hyper)
+
+  * [hyper](https://github.com/hyperium/hyper)
 
   Copyright (c) 2014-2021 Sean McArthur
 
@@ -9718,10 +9843,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ip_network_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
+
+  * [ip\_network\_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
 
   Copyright (c) 2016 Hroi Sigurdsson
 
@@ -9749,10 +9875,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [iprange](https://github.com/sticnarf/iprange-rs)
+
+  * [iprange](https://github.com/sticnarf/iprange-rs)
 
   MIT License
 
@@ -9776,10 +9903,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
+
+  * [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
 
   The MIT License
 
@@ -9802,10 +9930,11 @@ All license text:
   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [matchers](https://github.com/hawkw/matchers)
+
+  * [matchers](https://github.com/hawkw/matchers)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -9827,10 +9956,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [matches](https://github.com/SimonSapin/rust-std-candidates)
+
+  * [matches](https://github.com/SimonSapin/rust-std-candidates)
 
   Copyright (c) 2014-2016 Simon Sapin
 
@@ -9858,10 +9988,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [memoffset](https://github.com/Gilnaa/memoffset)
+
+  * [memoffset](https://github.com/Gilnaa/memoffset)
 
   Copyright (c) 2017 Gilad Naaman
 
@@ -9883,10 +10014,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [mio](https://github.com/tokio-rs/mio)
+
+  * [mio](https://github.com/tokio-rs/mio)
 
   Copyright (c) 2014 Carl Lerche and other MIO contributors
 
@@ -9908,10 +10040,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [nix](https://github.com/nix-rust/nix)
+
+  * [nix](https://github.com/nix-rust/nix)
 
   The MIT License (MIT)
 
@@ -9935,10 +10068,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [plist](https://github.com/ebarnard/rust-plist/)
+
+  * [plist](https://github.com/ebarnard/rust-plist/)
 
   Copyright (c) 2015 Edward Barnard
 
@@ -9960,10 +10094,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [powershell_script](https://github.com/cfsamson/powershell-script)
+
+  * [powershell\_script](https://github.com/cfsamson/powershell-script)
 
   The MIT License (MIT)
 
@@ -9975,10 +10110,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [redox_syscall](https://gitlab.redox-os.org/redox-os/syscall)
+
+  * [redox\_syscall](https://gitlab.redox-os.org/redox-os/syscall)
 
   Copyright (c) 2017 Redox OS Developers
 
@@ -10003,10 +10139,11 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [redox_users](https://gitlab.redox-os.org/redox-os/users)
+
+  * [redox\_users](https://gitlab.redox-os.org/redox-os/users)
 
   The MIT License (MIT)
 
@@ -10030,10 +10167,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   The MIT License (MIT)
 
@@ -10058,11 +10196,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [same-file](https://github.com/BurntSushi/same-file)
-  - [winapi-util](https://github.com/BurntSushi/winapi-util)
+
+  * [same-file](https://github.com/BurntSushi/same-file)
+  * [winapi-util](https://github.com/BurntSushi/winapi-util)
 
   The MIT License (MIT)
 
@@ -10086,10 +10225,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [schannel](https://github.com/steffengy/schannel-rs)
+
+  * [schannel](https://github.com/steffengy/schannel-rs)
 
   Copyright (c) 2015 steffengy
 
@@ -10099,10 +10239,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
+
+  * [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
 
   MIT License
 
@@ -10126,10 +10267,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sharded-slab](https://github.com/hawkw/sharded-slab)
+
+  * [sharded-slab](https://github.com/hawkw/sharded-slab)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -10151,10 +10293,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [slab](https://github.com/tokio-rs/slab)
+
+  * [slab](https://github.com/tokio-rs/slab)
 
   Copyright (c) 2019 Carl Lerche
 
@@ -10182,10 +10325,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [smbios-lib](https://github.com/jrgerber/smbios-lib)
+
+  * [smbios-lib](https://github.com/jrgerber/smbios-lib)
 
   MIT License
 
@@ -10209,11 +10353,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [spin](https://github.com/mvdnes/spin-rs.git)
-  - [zip](https://github.com/zip-rs/zip.git)
+
+  * [spin](https://github.com/mvdnes/spin-rs.git)
+  * [zip](https://github.com/zip-rs/zip.git)
 
   The MIT License (MIT)
 
@@ -10237,11 +10382,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [strsim](https://github.com/dguo/strsim-rs)
-  - [strsim](https://github.com/dguo/strsim-rs)
+
+  * [strsim](https://github.com/dguo/strsim-rs)
+  * [strsim](https://github.com/dguo/strsim-rs)
 
   The MIT License (MIT)
 
@@ -10266,10 +10412,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [synstructure](https://github.com/mystor/synstructure)
+
+  * [synstructure](https://github.com/mystor/synstructure)
 
   Copyright 2016 Nika Layzell
 
@@ -10279,10 +10426,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sys-info](https://github.com/FillZpp/sys-info-rs)
+
+  * [sys-info](https://github.com/FillZpp/sys-info-rs)
 
   The MIT License (MIT)
 
@@ -10306,10 +10454,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
+
+  * [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
 
   The MIT License (MIT)
 
@@ -10333,10 +10482,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [take_mut](https://github.com/Sgeo/take_mut)
+
+  * [take\_mut](https://github.com/Sgeo/take_mut)
 
   The MIT License (MIT)
 
@@ -10360,10 +10510,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [textwrap](https://github.com/mgeisler/textwrap)
+
+  * [textwrap](https://github.com/mgeisler/textwrap)
 
   MIT License
 
@@ -10387,11 +10538,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tokio](https://github.com/tokio-rs/tokio)
-  - [tokio-util](https://github.com/tokio-rs/tokio)
+
+  * [tokio](https://github.com/tokio-rs/tokio)
+  * [tokio-util](https://github.com/tokio-rs/tokio)
 
   Copyright (c) 2021 Tokio Contributors
 
@@ -10419,10 +10571,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
+
+  * [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
 
   Copyright (c) 2017 Daniel Abramov
   Copyright (c) 2017 Alexey Galakhov
@@ -10445,10 +10598,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [totp-lite](https://github.com/fosskers/totp-lite)
+
+  * [totp-lite](https://github.com/fosskers/totp-lite)
 
   MIT License
 
@@ -10472,10 +10626,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tower-service](https://github.com/tower-rs/tower)
+
+  * [tower-service](https://github.com/tower-rs/tower)
 
   Copyright (c) 2019 Tower Contributors
 
@@ -10503,16 +10658,17 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tracing](https://github.com/tokio-rs/tracing)
-  - [tracing-appender](https://github.com/tokio-rs/tracing)
-  - [tracing-attributes](https://github.com/tokio-rs/tracing)
-  - [tracing-core](https://github.com/tokio-rs/tracing)
-  - [tracing-log](https://github.com/tokio-rs/tracing)
-  - [tracing-serde](https://github.com/tokio-rs/tracing)
-  - [tracing-subscriber](https://github.com/tokio-rs/tracing)
+
+  * [tracing](https://github.com/tokio-rs/tracing)
+  * [tracing-appender](https://github.com/tokio-rs/tracing)
+  * [tracing-attributes](https://github.com/tokio-rs/tracing)
+  * [tracing-core](https://github.com/tokio-rs/tracing)
+  * [tracing-log](https://github.com/tokio-rs/tracing)
+  * [tracing-serde](https://github.com/tokio-rs/tracing)
+  * [tracing-subscriber](https://github.com/tokio-rs/tracing)
 
   Copyright (c) 2019 Tokio Contributors
 
@@ -10540,10 +10696,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [try-lock](https://github.com/seanmonstar/try-lock)
+
+  * [try-lock](https://github.com/seanmonstar/try-lock)
 
   Copyright (c) 2018 Sean McArthur
   Copyright (c) 2016 Alex Crichton
@@ -10566,10 +10723,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [want](https://github.com/seanmonstar/want)
+
+  * [want](https://github.com/seanmonstar/want)
 
   Copyright (c) 2018-2019 Sean McArthur
 
@@ -10591,12 +10749,13 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [winreg](https://github.com/gentoo90/winreg-rs)
-  - [winreg](https://github.com/gentoo90/winreg-rs)
-  - [winreg](https://github.com/gentoo90/winreg-rs)
+
+  * [winreg](https://github.com/gentoo90/winreg-rs)
+  * [winreg](https://github.com/gentoo90/winreg-rs)
+  * [winreg](https://github.com/gentoo90/winreg-rs)
 
   Copyright (c) 2015 Igor Shaula
 
@@ -10618,10 +10777,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [winres](https://github.com/mxre/winres)
+
+  * [winres](https://github.com/mxre/winres)
 
   Copyright 2016 Max Resch
 
@@ -10649,10 +10809,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [xml-rs](https://github.com/netvl/xml-rs)
+
+  * [xml-rs](https://github.com/netvl/xml-rs)
 
   The MIT License (MIT)
 
@@ -10676,10 +10837,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### Mozilla Public License 2.0
+* ### Mozilla Public License 2.0
 
   #### Used by:
-  - [cbindgen](https://github.com/eqrion/cbindgen/)
+
+  * [cbindgen](https://github.com/eqrion/cbindgen/)
+
   1. Definitions
 
   ***
@@ -10766,6 +10929,7 @@ All license text:
   whether by contract or otherwise, or (b) ownership of more than
   fifty percent (50%) of the outstanding shares or beneficial
   ownership of such entity.
+
   2. License Grants and Conditions
 
   ***
@@ -10837,6 +11001,7 @@ All license text:
 
   Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
   in Section 2.1.
+
   3. Responsibilities
 
   ***
@@ -10899,6 +11064,7 @@ All license text:
   indemnity or liability terms You offer. You may include additional
   disclaimers of warranty and limitations of liability specific to any
   jurisdiction.
+
   4. Inability to Comply Due to Statute or Regulation
 
   ***
@@ -10912,6 +11078,7 @@ All license text:
   Software under this License. Except to the extent prohibited by statute
   or regulation, such description must be sufficiently detailed for a
   recipient of ordinary skill to be able to understand it.
+
   5. Termination
 
   ***
@@ -10947,6 +11114,7 @@ All license text:
 
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \* \* \* 7. Limitation of Liability \* \* -------------------------- \* \* \* \* Under no circumstances and under no legal theory, whether tort \* \* (including negligence), contract, or otherwise, shall any \* \* Contributor, or anyone who distributes Covered Software as \* \* permitted above, be liable to You for any direct, indirect, \* \* special, incidental, or consequential damages of any character \* \* including, without limitation, damages for lost profits, loss of \* \* goodwill, work stoppage, computer failure or malfunction, or any \* \* and all other commercial damages or losses, even if such party \* \* shall have been informed of the possibility of such damages. This \* \* limitation of liability shall not apply to liability for death or \* \* personal injury resulting from such party's negligence to the \* \* extent applicable law prohibits such limitation. Some \* \* jurisdictions do not allow the exclusion or limitation of \* \* incidental or consequential damages, so this exclusion and \* \* limitation may not apply to You. \* \* \*
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
+
   8. Litigation
 
   ***
@@ -10957,6 +11125,7 @@ All license text:
   jurisdiction, without reference to its conflict-of-law provisions.
   Nothing in this Section shall prevent a party's ability to bring
   cross-claims or counter-claims.
+
   9. Miscellaneous
 
   ***
@@ -10967,6 +11136,7 @@ All license text:
   necessary to make it enforceable. Any law or regulation which provides
   that the language of a contract shall be construed against the drafter
   shall not be used to construe this License against a Contributor.
+
   10. Versions of the License
 
   ***
@@ -11018,12 +11188,14 @@ All license text:
   This Source Code Form is "Incompatible With Secondary Licenses", as
   defined by the Mozilla Public License, v. 2.0.
 
-- ### Mozilla Public License 2.0
+* ### Mozilla Public License 2.0
 
   #### Used by:
-  - [webpki-roots](https://github.com/ctz/webpki-roots)
+
+  * [webpki-roots](https://github.com/ctz/webpki-roots)
 
   Mozilla Public License Version 2.0
+
   1. Definitions
 
      1.1. "Contributor" means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.
@@ -11181,10 +11353,11 @@ All license text:
    This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0.
   ```
 
-- ### OpenSSL License
+* ### OpenSSL License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   /\* Copyright (C) 1995-1998 Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)) \* All rights reserved. \* \* This package is an SSL implementation written \* by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)). \* The implementation was written so as to conform with Netscapes SSL. \* \* This library is free for commercial and non-commercial use as long as \* the following conditions are aheared to. The following conditions \* apply to all code found in this distribution, be it the RC4, RSA, \* lhash, DES, etc., code; not just the SSL code. The SSL documentation \* included with this distribution is covered by the same copyright terms \* except that the holder is Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com)). \* \* Copyright remains Eric Young's, and as such any Copyright notices in \* the code are not to be removed. \* If this package is used in a product, Eric Young should be given attribution \* as the author of the parts of the library used. \* This can be in the form of a textual message at program startup or \* in documentation (online or textual) provided with the package. \* \* Redistribution and use in source and binary forms, with or without \* modification, are permitted provided that the following conditions \* are met: \* 1. Redistributions of source code must retain the copyright \* notice, this list of conditions and the following disclaimer. \* 2. Redistributions in binary form must reproduce the above copyright \* notice, this list of conditions and the following disclaimer in the \* documentation and/or other materials provided with the distribution. \* 3. All advertising materials mentioning features or use of this software \* must display the following acknowledgement: \* "This product includes cryptographic software written by \* Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com))" \* The word 'cryptographic' can be left out if the rouines from the library \* being used are not cryptographic related :-). \* 4. If you include any Windows specific code (or a derivative thereof) from \* the apps directory (application code) you must include an acknowledgement: \* "This product includes software written by Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com))" \* \* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND \* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE \* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE \* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE \* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL \* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS \* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) \* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT \* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY \* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF \* SUCH DAMAGE. \* \* The licence and distribution terms for any publically available version or \* derivative of this code cannot be changed. i.e. this code cannot simply be \* copied and put under another distribution licence \* \[including the GNU Public Licence.]
   \*/
diff --git a/src/content/docs/warp-client/legal/index.mdx b/src/content/docs/warp-client/legal/index.mdx
index 2a3706602febaf7..eda71adda87c679 100644
--- a/src/content/docs/warp-client/legal/index.mdx
+++ b/src/content/docs/warp-client/legal/index.mdx
@@ -7,8 +7,9 @@ title: Legal
 hideChildren: true
 sidebar:
   order: 6
+
 ---
 
-- [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
-- [Application Terms of Service](https://www.cloudflare.com/application/terms/)
-- [Third party licenses](/warp-client/legal/3rdparty/)
+* [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
+* [Application Terms of Service](https://www.cloudflare.com/application/terms/)
+* [Third party licenses](/warp-client/legal/3rdparty/)
diff --git a/src/content/docs/warp-client/privacy.mdx b/src/content/docs/warp-client/privacy.mdx
index b9d5bb1a7061d21..92288d9c01bb7c0 100644
--- a/src/content/docs/warp-client/privacy.mdx
+++ b/src/content/docs/warp-client/privacy.mdx
@@ -8,6 +8,7 @@ tags:
   - Privacy
 sidebar:
   order: 4
+
 ---
 
 The WARP Client application uses a VPN profile and/or service that enables us to intercept and secure your DNS queries and to transmit data from your device through the Cloudflare network, depending on the services you have enabled. We only collect limited DNS query and traffic data (excluding payload) that is sent to our network when you have the app enabled on your device. All information is handled in accordance with our [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/).
diff --git a/src/content/docs/web-analytics/configuration-options/filters.mdx b/src/content/docs/web-analytics/configuration-options/filters.mdx
index 8ad627a79b2582d..27174f2f041e941 100644
--- a/src/content/docs/web-analytics/configuration-options/filters.mdx
+++ b/src/content/docs/web-analytics/configuration-options/filters.mdx
@@ -5,6 +5,7 @@ products:
 title: Filters
 head: []
 description: Learn how to use filters in Cloudflare Web Analytics.
+
 ---
 
 import { DashButton } from "~/components";
@@ -24,4 +25,4 @@ To filter the data shown on Web Analytics:
 
 - By default, Web Analytics shows data for the previous 24 hours. Adjust the time range using the dropdown menu above the graph.
 - Select and drag the cursor on the graph to choose a custom time period.
-- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
+- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
\ No newline at end of file
diff --git a/src/content/docs/web-analytics/configuration-options/index.mdx b/src/content/docs/web-analytics/configuration-options/index.mdx
index 4a728a05e606d7f..390e5e32d1c7476 100644
--- a/src/content/docs/web-analytics/configuration-options/index.mdx
+++ b/src/content/docs/web-analytics/configuration-options/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Configuration options
 sidebar:
   order: 4
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Customize your Web Analytics views by using filters and rules.
 
diff --git a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
index 4766dc07ffc8926..0b5369d3af5186b 100644
--- a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
+++ b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
@@ -6,6 +6,7 @@ products:
 title: Core Web Vitals
 sidebar:
   order: 3
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,8 +15,10 @@ import { DashButton } from "~/components";
 
 :::note
 
+
 Core Web Vitals is currently only supported in Chromium browsers, with Safari and Firefox coming soon.
 
+
 :::
 
 ## Access Core Web Vitals
@@ -29,7 +32,7 @@ To access Core Web Vitals:
 
 2. Select your website and select **Core Web Vitals**.
 
-### Core Web Vitals metrics
+###  Core Web Vitals metrics
 
 Core Web Vitals is divided into three main sections, each one with information about a specific feature that affects user experience:
 
diff --git a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
index 407d22e05366193..503d9caaf70f22e 100644
--- a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
+++ b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
@@ -11,7 +11,7 @@ tags:
   - Privacy
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Web Analytics relies on the `performance.getEntriesByType('navigation')` object to collect metrics about page load performance. If Navigation Timing Level 2 is not supported, then [`performance.timing` (Level 1)](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) is used.
 
diff --git a/src/content/docs/web-analytics/data-metrics/dimensions.mdx b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
index 2f8158417df0f8f..3caceecb45f0a80 100644
--- a/src/content/docs/web-analytics/data-metrics/dimensions.mdx
+++ b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
@@ -6,6 +6,7 @@ products:
 title: Dimensions
 sidebar:
   order: 4
+
 ---
 
 Dimensions are the labels used to describe different types of metrics or data. For example, **Referer** is the data collected from external links referring visits to a page, while **Browser** shows which browsers accessed your website.
@@ -27,14 +28,14 @@ Below you can find a list of the different dimensions you can use to filter Web
 
 ## Navigation types
 
-| Type                    | Cache hit? | Explanation                                                                                                                                                                                                                                                                                                                                                |
-| ----------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                              |
-| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                  |
-| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                    |
-| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document.                                                                                                                                                                                                     |
-| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                                               |
-| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                                   |
+| Type                    | Cache hit? | Explanation |
+| ----------------------- | ---------- | ----------- |
+| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
+| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document. |
+| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document. |
+| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
+| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
 | Back-forward            | ❌         | The visitor used the back/forward buttons/gestures in their browser but the previously-loaded document either not found or stale in the browsers HTTP cache OR a feature was used which prevents using the cache (refer to the explanation in [Back/forward cache](https://web.dev/articles/bfcache)), so a network request was made to load the document. |
-| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                             |
-| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity.                                                                                                                                                                                                                                                       |
+| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity. |
diff --git a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
index d3db219922bbfb9..65577424b5e1480 100644
--- a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
+++ b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
@@ -6,13 +6,14 @@ products:
 title: High-level metrics
 sidebar:
   order: 1
+
 ---
 
 Understanding the key metrics in web analytics is essential for optimizing your website’s performance and user experience. Here are the high-level metrics tracked by Cloudflare Web Analytics:
 
-- **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
-- **Page views** - A successful HTTP response with a content-type of HTML.
-- **Page load time** - The total amount of time required to load the page.
-- **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
+* **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
+* **Page views** - A successful HTTP response with a content-type of HTML.
+* **Page load time** - The total amount of time required to load the page.
+* **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
 
 ![Web Analytics overview page](~/assets/images/web-analytics/dash-web_analytics-overview.png)
diff --git a/src/content/docs/web-analytics/data-metrics/index.mdx b/src/content/docs/web-analytics/data-metrics/index.mdx
index 7295662b2a7dd44..701245c37266099 100644
--- a/src/content/docs/web-analytics/data-metrics/index.mdx
+++ b/src/content/docs/web-analytics/data-metrics/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Data and metrics
 sidebar:
   order: 5
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In this section, you can find information about the data and metrics available in Web Analytics.
 
diff --git a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
index 17d8640e8fe0887..ed4e1dedbe02b6b 100644
--- a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
+++ b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
@@ -6,6 +6,7 @@ products:
 title: Page load time
 sidebar:
   order: 2
+
 ---
 
 Page load time summary gives you an overview of how long your web page takes to load, broken down by area. To access Page load time:
diff --git a/src/content/docs/web-analytics/faq.mdx b/src/content/docs/web-analytics/faq.mdx
index 50db67fa11ae9e8..57b722a62fab5d6 100644
--- a/src/content/docs/web-analytics/faq.mdx
+++ b/src/content/docs/web-analytics/faq.mdx
@@ -123,11 +123,11 @@ For manual embedding, this script instead connects to `cloudflareinsights.com`,
 connect-src [...existing values...] cloudflareinsights.com
 ```
 
-### How can I enforce Subresource Integrity (SRI) with the JS beacon?
+### How can I enforce Subresource Integrity (SRI) with the JS beacon? 
 
 If you're using the automated injection (i.e. not the manually-embedded script approach mentioned above), Cloudflare automatically includes an `integrity` attribute in the `<script>`. This ensures the script will only execute if a local hash of its downloaded contents match the integrity hash supplied in the HTML.
 
-Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure
+Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure 
 
 ### Can I use the same JS Snippet for a different domain?
 
@@ -159,11 +159,11 @@ When aggregating metrics in the Cloudflare Dashboard or querying the GraphQL API
 
 Note: the GraphQL API exposes a `sampleInterval` field to indicate which level of sampling has been applied to the query.
 
-- The beacon script will fire on every pageview.
-- The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
-- We store the unsampled data for 7 days.
-- We also aggregate it down so it's around 10% of the original volume for long-term storage.
-- Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
+* The beacon script will fire on every pageview.
+* The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
+* We store the unsampled data for 7 days.
+* We also aggregate it down so it's around 10% of the original volume for long-term storage.
+* Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
 
 ### Can I see server-side analytics by URL?
 
diff --git a/src/content/docs/web-analytics/get-started/rum-beacon.mdx b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
index 675f6808ea47e52..11ec40779ef5cee 100644
--- a/src/content/docs/web-analytics/get-started/rum-beacon.mdx
+++ b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
@@ -5,4 +5,5 @@ products:
   - web-analytics
 title: RUM beacon for Web Analytics
 external_link: /speed/observatory/rum-beacon/
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
index 9ae208a6c8ea4c5..6b3368cab792483 100644
--- a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
+++ b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
@@ -21,9 +21,9 @@ If you want to disable the automatic tracking for SPAs, you can do so by adding
 
 ```html
 <script
-	defer
-	src="https://static.cloudflareinsights.com/beacon.min.js"
-	data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
+  defer
+  src="https://static.cloudflareinsights.com/beacon.min.js"
+  data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
 ></script>
 ```
 
@@ -33,7 +33,7 @@ If you are using Google Tag Manager (GTM), you can disable SPA tracking by passi
 
 ```html
 <script
-	defer
-	src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
+  defer
+  src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
 ></script>
 ```
diff --git a/src/content/docs/web-analytics/limits.mdx b/src/content/docs/web-analytics/limits.mdx
index 8a2772d9e9f328e..cc30789f0796155 100644
--- a/src/content/docs/web-analytics/limits.mdx
+++ b/src/content/docs/web-analytics/limits.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Web Analytics - Limits
+
 ---
 
 Cloudflare limits the number of sites for which you can track web analytics, as well as the number of rules allowed for each plan type. Refer to the following tables for more information.
diff --git a/src/content/docs/web3/about.mdx b/src/content/docs/web3/about.mdx
index 12c2faf886781b6..e71d0319dd669a7 100644
--- a/src/content/docs/web3/about.mdx
+++ b/src/content/docs/web3/about.mdx
@@ -29,4 +29,4 @@ Only available for gateways to EVM-based chains, such as [Ethereum](/web3/how-to
 
 Write operations submit new data to the network. For example, sending a transaction or deploying a smart contract. The gateway forwards your request to one of Cloudflare's Ethereum nodes, which places the transaction in its mempool (a queue of pending transactions waiting to be included in a block).
 
-From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
+From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
\ No newline at end of file
diff --git a/src/content/docs/web3/api-reference.mdx b/src/content/docs/web3/api-reference.mdx
index 6580ba64f458124..a71630e4616b775 100644
--- a/src/content/docs/web3/api-reference.mdx
+++ b/src/content/docs/web3/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/web3/subresources/hostnames/methods/list/
 sidebar:
   order: 6
+
 ---
diff --git a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
index 8fa017a894a1131..e8c6ae241ad289f 100644
--- a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Concepts - Ethereum Gateways
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 As you get started with Cloudflare's Ethereum Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ethereum-gateway/reference/index.mdx b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
index 2bb1163debfdf53..0ac05bf3f8fd5a3 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - Ethereum
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
index ae20777dcb9b048..424052aeb898254 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
@@ -6,6 +6,7 @@ products:
 title: Kill Switches
 sidebar:
   order: 6
+
 ---
 
 When writing contracts, be especially careful to write secure code and include a
@@ -15,7 +16,7 @@ the smart contract that can be exploited, this can lead to the theft of
 resources from the smart contract or from other individuals.
 
 This was brought into sharp focus during the [infamous DAO
-incident](<https://en.wikipedia.org/wiki/The_DAO_(organization)>). The DAO smart
+incident](https://en.wikipedia.org/wiki/The_DAO_\(organization\)). The DAO smart
 contract acted as a complex, decentralized venture capital fund and held Ether
 worth $250 million at its peak collected from a group of investors. Hackers
 exploited vulnerabilities in the smart contract, stealing $50 million worth of
@@ -23,7 +24,7 @@ Ether.
 
 Because there is no way to undo transactions in Ether, there was a highly
 controversial “hard fork," where the majority of the community agreed to accept
-a block that contained an _irregular state change_ that essentially drained all
+a block that contained an *irregular state change* that essentially drained all
 DAO funds into a special “WithdrawDAO” recovery contract. By convincing enough
 miners to accept this irregular block as valid, the DAO was able to return
 investors funds. However, not everyone agreed with the chain, with those who
@@ -58,7 +59,7 @@ trustworthiness.
 The trust placed in consensus-based algorithms is based on the assumption that
 most people are honest, or more accurately that no sufficiently large subset of
 people can be made to collude to produce a malicious outcome. This is the
-_democratisation of trust_. In the DAO attack, a majority of nodes agreed to
+*democratisation of trust*. In the DAO attack, a majority of nodes agreed to
 accept an irregular state transition. This effectively undid the damage of the
 attack, and shows how, at least in the world of blockchain, perception is
 reality. Because most people “believed" -- accepted this irregular block, it
diff --git a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
index a786977025d3db2..fe72e9e11b576ae 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
@@ -8,6 +8,7 @@ tags:
   - Migration
 sidebar:
   order: 5
+
 ---
 
 Though Cloudflare's Ethereum Gateway launched with support for the Rinkeby testnet, Rinkeby did not run through [The Merge](https://ethereum.org/en/upgrades/merge/) and - as a result - will no longer be a reliable staging environment for mainnet.
@@ -35,20 +36,20 @@ curl https://web3-trial.cloudflare-eth.com/v1/rinkeby \
 
 ```js title="Previous JS Fetch API" {2}
 await fetch(
-	new Request("https://web3-trial.cloudflare-eth.com/v1/rinkeby", {
-		method: "POST",
-		body: JSON.stringify({
-			jsonrpc: "2.0",
-			method: "eth_getBlockByNumber",
-			params: ["0x2244", true],
-			id: 1,
-		}),
-		headers: {
-			"Content-Type": "application/json",
-		},
-	}),
-).then((resp) => {
-	return resp.json();
+  new Request('https://web3-trial.cloudflare-eth.com/v1/rinkeby', {
+    method: 'POST',
+    body: JSON.stringify({
+      jsonrpc: '2.0',
+      method: 'eth_getBlockByNumber',
+      params: ['0x2244', true],
+      id: 1,
+    }),
+    headers: {
+      'Content-Type': 'application/json',
+    },
+  })
+).then(resp => {
+  return resp.json();
 });
 ```
 
@@ -67,19 +68,19 @@ curl https://web3-trial.cloudflare-eth.com/v1/sepolia \
 
 ```js title="New JS Fetch API" {2}
 await fetch(
-	new Request("https://web3-trial.cloudflare-eth.com/v1/sepolia", {
-		method: "POST",
-		body: JSON.stringify({
-			jsonrpc: "2.0",
-			method: "eth_getBlockByNumber",
-			params: ["0x2244", true],
-			id: 1,
-		}),
-		headers: {
-			"Content-Type": "application/json",
-		},
-	}),
-).then((resp) => {
-	return resp.json();
+  new Request('https://web3-trial.cloudflare-eth.com/v1/sepolia', {
+    method: 'POST',
+    body: JSON.stringify({
+      jsonrpc: '2.0',
+      method: 'eth_getBlockByNumber',
+      params: ['0x2244', true],
+      id: 1,
+    }),
+    headers: {
+      'Content-Type': 'application/json',
+    },
+  })
+).then(resp => {
+  return resp.json();
 });
 ```
diff --git a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
index dbc5a494061f6e0..b4932918c9e909b 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Supported networks - Ethereum Gateway
+
 ---
 
 Currently, Cloudflare Ethereum gateways support [interacting with](/web3/how-to/use-ethereum-gateway/) the following networks.
diff --git a/src/content/docs/web3/how-to/index.mdx b/src/content/docs/web3/how-to/index.mdx
index f6ebb1af9d9b691..09b45998630efc4 100644
--- a/src/content/docs/web3/how-to/index.mdx
+++ b/src/content/docs/web3/how-to/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Web3 - How to
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
index d15b08583b61f0b..3987b7170bde027 100644
--- a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
+++ b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
@@ -6,6 +6,7 @@ products:
 title: Use IPFS gateway
 sidebar:
   order: 2
+
 ---
 
 Once you have an IPFS gateway — meaning that you [create a new gateway](/web3/how-to/manage-gateways/#create-a-gateway) with a `target` of **IPFS** — you can get data from the IPFS network by using a URL.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
index f4449ce98f8c009..46ac314920cbb5a 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
@@ -8,6 +8,7 @@ tags:
   - DNS
 sidebar:
   order: 4
+
 ---
 
 When you set up a gateway with a DNSLink record, that gateway is restricted to a particular piece of content — either a specific Content Identifier (CID) or an Interplanetary Name Service (IPNS) hostname. This is called a restricted gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
index 77d6c15618f0cde..1f800c90518ab08 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Concepts - IPFS Gateway
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 As you get started with Cloudflare's IPFS Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
index 754e32b96952c90..b47002eb8b4134b 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
@@ -6,12 +6,13 @@ products:
 title: Automated deployments
 sidebar:
   order: 6
+
 ---
 
 Static sites are easy to deploy automatically. The code of the site is usually kept in a Git repository and deployed by pushing the latest commit to a repository that's connected to a Continuous Integration service like [Travis CI](https://travis-ci.org/), or by pushing to a repository directly on the server and activating a post-receive hook. Either way, the production version of the site is built and then copied into the serving path of an Apache or NGINX instance.
 
 IPFS usually fits into these systems: instead of copying the production version of a website into the serving path of an HTTP server, you would upload the same files to an IPFS node and update your DNS records with the new hash. There are several tools that help with different parts of this:
 
-- [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
-- [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
-- [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
+* [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
+* [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
+* [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/reference/index.mdx b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
index 10c80255fdf7a98..c69067dd176b415 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - IPFS
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
index 81ab323e9cf901a..574f2ebad732b96 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
@@ -6,6 +6,7 @@ products:
 title: Peering
 sidebar:
   order: 5
+
 ---
 
 If you are running an IPFS node that serves many requests - like a public HTTP gateway - you may be able to speed up queries by maintaining long-lived connections to nodes that provide a large volume of data.
@@ -14,57 +15,81 @@ This process is known as **Peering** and you can tell IPFS to prioritize Cloudfl
 
 ```json
 {
-	"Peering": {
-		"Peers": [
-			{
-				"ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
-				"Addrs": ["/dnsaddr/node-1.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
-				"Addrs": ["/dnsaddr/node-2.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
-				"Addrs": ["/dnsaddr/node-3.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
-				"Addrs": ["/dnsaddr/node-4.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
-				"Addrs": ["/dnsaddr/node-5.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
-				"Addrs": ["/dnsaddr/node-6.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
-				"Addrs": ["/dnsaddr/node-7.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
-				"Addrs": ["/dnsaddr/node-8.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
-				"Addrs": ["/dnsaddr/node-9.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
-				"Addrs": ["/dnsaddr/node-10.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
-				"Addrs": ["/dnsaddr/node-11.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
-				"Addrs": ["/dnsaddr/node-12.ingress.cloudflare-ipfs.com"]
-			}
-		]
-	}
+  "Peering": {
+    "Peers": [
+      {
+        "ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
+        "Addrs": [
+          "/dnsaddr/node-1.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
+        "Addrs": [
+          "/dnsaddr/node-2.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
+        "Addrs": [
+          "/dnsaddr/node-3.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
+        "Addrs": [
+          "/dnsaddr/node-4.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
+        "Addrs": [
+          "/dnsaddr/node-5.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
+        "Addrs": [
+          "/dnsaddr/node-6.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
+        "Addrs": [
+          "/dnsaddr/node-7.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
+        "Addrs": [
+          "/dnsaddr/node-8.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
+        "Addrs": [
+          "/dnsaddr/node-9.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
+        "Addrs": [
+          "/dnsaddr/node-10.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
+        "Addrs": [
+          "/dnsaddr/node-11.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
+        "Addrs": [
+          "/dnsaddr/node-12.ingress.cloudflare-ipfs.com"
+        ]
+      }
+    ]
+  }
 }
 ```
diff --git a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
index 9ae156f2b234174..f66712b07d379ed 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
@@ -6,13 +6,14 @@ products:
 title: Using IPFS with your website
 sidebar:
   order: 5
+
 ---
 
 Though it is not required, it is strongly recommended that websites hosted on IPFS use only relative links, unless linking to a different domain. This is because data can be accessed in many different (but ultimately equivalent) ways:
 
-- From your custom domain: `https://ipfs.tech/index.html`
-- From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
-- By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
+* From your custom domain: `https://ipfs.tech/index.html`
+* From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
+* By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
 
 Using only relative links within a web application supports all of these at once, and gives the most flexibility to the user. The exact method for switching to relative links, if you do not use them already, depends on the framework you use.
 
diff --git a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
index 658a32e0017e5e9..b76805532e21a27 100644
--- a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
+++ b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
@@ -8,6 +8,7 @@ tags:
   - Debugging
 sidebar:
   order: 11
+
 ---
 
 ## Cloudflare-specific
diff --git a/src/content/docs/web3/reference/gateway-dns-records.mdx b/src/content/docs/web3/reference/gateway-dns-records.mdx
index 44ce03c721e9985..c7ca135a158f53d 100644
--- a/src/content/docs/web3/reference/gateway-dns-records.mdx
+++ b/src/content/docs/web3/reference/gateway-dns-records.mdx
@@ -8,12 +8,13 @@ tags:
   - DNS
 sidebar:
   order: 1
+
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), Cloudflare automatically creates and adds records to your Cloudflare DNS so your gateway can receive and route traffic appropriately:
 
-- **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
-- **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
+* **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
+* **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
 
 These records cannot be edited within Cloudflare DNS. To make edits, you will have to [edit the gateway configuration](/web3/how-to/manage-gateways/#edit-a-gateway) itself.
 
diff --git a/src/content/docs/web3/reference/gateway-status.mdx b/src/content/docs/web3/reference/gateway-status.mdx
index b8f41477bb010ac..f48cc0df30a6a4e 100644
--- a/src/content/docs/web3/reference/gateway-status.mdx
+++ b/src/content/docs/web3/reference/gateway-status.mdx
@@ -6,6 +6,7 @@ products:
 title: Gateway status
 sidebar:
   order: 2
+
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), it can have one of several statuses.
diff --git a/src/content/docs/web3/reference/index.mdx b/src/content/docs/web3/reference/index.mdx
index d5e84b5cb473800..000a9dc1764b37c 100644
--- a/src/content/docs/web3/reference/index.mdx
+++ b/src/content/docs/web3/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - Web3 Gateways
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/reference/migration-guide.mdx b/src/content/docs/web3/reference/migration-guide.mdx
index aa20fe71fbcb5ac..438c79c9d19f639 100644
--- a/src/content/docs/web3/reference/migration-guide.mdx
+++ b/src/content/docs/web3/reference/migration-guide.mdx
@@ -8,13 +8,14 @@ tags:
   - Migration
 sidebar:
   order: 4
+
 ---
 
 As announced in [our blog post](https://blog.cloudflare.com/ea-web3-gateways/), Cloudflare is deprecating legacy hostnames that point to our public gateway endpoints at `cloudflare-eth.com` and `cloudflare-ipfs.com`.
 
 If you created a hostname pointing to these gateways during the [private beta](https://blog.cloudflare.com/announcing-web3-gateways/), you should migrate to use our new Web3 gateways to avoid a disruption in service.
 
----
+***
 
 ## Migration guide
 
diff --git a/src/content/docs/workers-ai/agents.mdx b/src/content/docs/workers-ai/agents.mdx
index b54052a2ddfb2a5..6987307dd6a54f5 100644
--- a/src/content/docs/workers-ai/agents.mdx
+++ b/src/content/docs/workers-ai/agents.mdx
@@ -9,12 +9,9 @@ sidebar:
   order: 7
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
-<div style={{ textAlign: "center", marginBottom: "2rem" }}>
-	<p>
-		Build AI assistants that can perform complex tasks on behalf of your users
-		using Cloudflare Workers AI and Agents.
-	</p>
-	<LinkButton href="/agents/">Go to Agents documentation</LinkButton>
-</div>
+<div style={{ textAlign: 'center', marginBottom: '2rem' }}>
+  <p>Build AI assistants that can perform complex tasks on behalf of your users using Cloudflare Workers AI and Agents.</p>
+  <LinkButton href="/agents/">Go to Agents documentation</LinkButton>
+</div>
\ No newline at end of file
diff --git a/src/content/docs/workers-ai/api-reference.mdx b/src/content/docs/workers-ai/api-reference.mdx
index d4399b2cedbf0b1..62cc80dfcec7e8a 100644
--- a/src/content/docs/workers-ai/api-reference.mdx
+++ b/src/content/docs/workers-ai/api-reference.mdx
@@ -7,4 +7,5 @@ products:
   - workers-ai
 sidebar:
   order: 9
+
 ---
diff --git a/src/content/docs/workers-ai/configuration/bindings.mdx b/src/content/docs/workers-ai/configuration/bindings.mdx
index 679ad1f230931bf..51750be8e394b68 100644
--- a/src/content/docs/workers-ai/configuration/bindings.mdx
+++ b/src/content/docs/workers-ai/configuration/bindings.mdx
@@ -43,27 +43,33 @@ To configure a Workers AI binding in your Pages Function, you must use the Cloud
 `async env.AI.run()` runs a model. Takes a model as the first parameter, and an object as the second parameter.
 
 ```javascript
-const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
-	prompt: "What is the origin of the phrase 'Hello, World'",
+const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
+    prompt: "What is the origin of the phrase 'Hello, World'"
 });
 ```
 
 **Parameters**
 
-- `model` <Type text="string" /> <MetaInfo text="required" />
-  - The model to run.
+
+
+* `model` <Type text="string" /> <MetaInfo text="required" />
+
+  * The model to run.
 
   **Supported options**
-  - `stream` <Type text="boolean" /> <MetaInfo text="optional" />
-    - Returns a stream of results as they are available.
+
+  * `stream` <Type text="boolean" /> <MetaInfo text="optional" />
+    * Returns a stream of results as they are available.
+
+
 
 ```javascript
-const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
-	prompt: "What is the origin of the phrase 'Hello, World'",
-	stream: true,
+const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
+    prompt: "What is the origin of the phrase 'Hello, World'",
+    stream: true
 });
 
 return new Response(answer, {
-	headers: { "content-type": "text/event-stream" },
+    headers: { "content-type": "text/event-stream" }
 });
 ```
diff --git a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
index 9daadf9eb13e568..fe7d83c834c46c7 100644
--- a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
+++ b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
@@ -14,9 +14,9 @@ Use Workers AI with [Chat UI](https://github.com/huggingface/chat-ui?tab=readme-
 
 You will need the following:
 
-- A [Cloudflare account](https://dash.cloudflare.com)
-- Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
-- An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
+* A [Cloudflare account](https://dash.cloudflare.com)
+* Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
+* An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
 
 ## Setup
 
@@ -28,20 +28,20 @@ When setting up your models, specify the `cloudflare` endpoint.
 
 ```json
 {
-	"name": "nousresearch/hermes-2-pro-mistral-7b",
-	"tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
-	"parameters": {
-		"stop": ["<|im_end|>"]
-	},
-	"endpoints": [
-		{
-			"type": "cloudflare",
-			// optionally specify these if not included in .env.local
-			"accountId": "your-account-id",
-			"apiToken": "your-api-token"
-			//
-		}
-	]
+  "name" : "nousresearch/hermes-2-pro-mistral-7b",
+  "tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
+  "parameters": {
+    "stop": ["<|im_end|>"]
+  },
+  "endpoints" : [
+    {
+      "type": "cloudflare",
+      // optionally specify these if not included in .env.local
+      "accountId": "your-account-id",
+      "apiToken": "your-api-token"
+      //
+    }
+  ]
 }
 ```
 
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
index defd31249419534..1f531e7b4d8115a 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
@@ -20,7 +20,7 @@ To do so a `getWeather` function is defined that is passed to the LLM as tool.
 The `getWeather`function extracts the user's location from the request and calls the external weather API via the Workers' [`Fetch API`](/workers/runtime-apis/fetch/) and returns the result.
 
 ```ts title="Embedded function calling example with fetch()"
-import { runWithTools } from "@cloudflare/ai-utils";
+import { runWithTools } from '@cloudflare/ai-utils';
 
 type Env = {
 	AI: Ai;
@@ -31,14 +31,14 @@ export default {
 		// Define function
 		const getWeather = async (args: { numDays: number }) => {
 			const { numDays } = args;
-			// Location is extracted from request based on
-			// https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
-			const lat = request.cf?.latitude;
-			const long = request.cf?.longitude;
+      // Location is extracted from request based on
+      // https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
+      const lat = request.cf?.latitude
+      const long = request.cf?.longitude
 
-			// Interpolate values for external API call
+      // Interpolate values for external API call
 			const response = await fetch(
-				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`,
+				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`
 			);
 			return response.text();
 		};
@@ -46,37 +46,35 @@ export default {
 		const response = await runWithTools(
 			env.AI,
 			// Model with function calling support
-			"@hf/nousresearch/hermes-2-pro-mistral-7b",
+			'@hf/nousresearch/hermes-2-pro-mistral-7b',
 			{
 				// Messages
 				messages: [
 					{
-						role: "user",
-						content: "What the weather like the next 5 days? Respond as text",
+						role: 'user',
+						content: 'What the weather like the next 5 days? Respond as text',
 					},
 				],
 				// Definition of available tools the AI model can leverage
 				tools: [
 					{
-						name: "getWeather",
-						description: "Get the weather for the next [numDays] days",
+						name: 'getWeather',
+						description: 'Get the weather for the next [numDays] days',
 						parameters: {
-							type: "object",
+							type: 'object',
 							properties: {
-								numDays: {
-									type: "numDays",
-									description: "number of days for the weather forecast",
-								},
+								numDays: { type: 'numDays', description: 'number of days for the weather forecast' },
 							},
-							required: ["numDays"],
+							required: ['numDays'],
 						},
 						// reference to previously defined function
 						function: getWeather,
 					},
 				],
-			},
+			}
 		);
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
+
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
index 1f3842dcb258da4..f70be9e51f5b064 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
@@ -12,7 +12,6 @@ description: Learn how to use Cloudflare Workers AI to interact with KV storage,
 Interact with persistent storage to retrieve or store information enables for powerful use cases.
 
 In this example we show how embedded function calling can interact with other resources on the Cloudflare Developer Platform with a few lines of code.
-
 ## Pre-Requisites
 
 For this example to work, you need to provision a [KV](/kv/) namespace first. To do so, follow the [KV - Get started ](/kv/get-started/) guide.
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
index 0d5b64aae3a9a86..99f3b4077c79279 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
@@ -15,54 +15,54 @@ Oftentimes APIs are defined and documented via [OpenAPI specification](https://s
 In this example the LLM will describe the a Github user, based Github's API and its OpenAPI spec.
 
 ```ts title="Embedded function calling example from OpenAPI Spec"
-import { createToolsFromOpenAPISpec, runWithTools } from "@cloudflare/ai-utils";
+import { createToolsFromOpenAPISpec, runWithTools } from '@cloudflare/ai-utils';
 
 type Env = {
 	AI: Ai;
 };
 
-const APP_NAME = "cf-fn-calling-example-app";
+const APP_NAME = 'cf-fn-calling-example-app';
 
 export default {
 	async fetch(request, env, ctx) {
 		const toolsFromOpenAPISpec = [
 			// You can pass the OpenAPI spec link or contents directly
 			...(await createToolsFromOpenAPISpec(
-				"https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json",
+				'https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json',
 				{
 					overrides: [
 						{
 							matcher: ({ url }) => {
-								return url.hostname === "api.github.com";
+								return url.hostname === 'api.github.com';
 							},
 							// for all requests on *.github.com, we'll need to add a User-Agent.
 							values: {
 								headers: {
-									"User-Agent": APP_NAME,
+									'User-Agent': APP_NAME,
 								},
 							},
 						},
 					],
-				},
+				}
 			)),
 		];
 
 		const response = await runWithTools(
 			env.AI,
-			"@hf/nousresearch/hermes-2-pro-mistral-7b",
+			'@hf/nousresearch/hermes-2-pro-mistral-7b',
 			{
 				messages: [
 					{
-						role: "user",
-						content:
-							"Who is cloudflare on Github and how many repos does the organization have?",
+						role: 'user',
+						content: 'Who is cloudflare on Github and how many repos does the organization have?',
 					},
 				],
 				tools: toolsFromOpenAPISpec,
-			},
+			}
 		);
 
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
+
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
index c246533acd9ad9b..559cf113e209a3a 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare has a unique [embedded function calling](https://blog.cloudflare.com/embedded-function-calling) feature that allows you to execute function code alongside your tool call inference. Our npm package [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) is the developer toolkit to get started.
 
@@ -21,8 +21,10 @@ Embedded function calling can be used to easily make complex agents that interac
 
 :::caution[REST API support]
 
+
 Embedded function calling depends on features native to the Workers platform. This means that embedded function calling is only supported via [Cloudflare Workers](/workers-ai/get-started/workers-wrangler/), not via the [REST API](/workers-ai/get-started/rest-api/).
 
+
 :::
 
 ## Resources
diff --git a/src/content/docs/workers-ai/get-started/dashboard.mdx b/src/content/docs/workers-ai/get-started/dashboard.mdx
index e22a698bbeddce6..2ba3fce6dbc68cc 100644
--- a/src/content/docs/workers-ai/get-started/dashboard.mdx
+++ b/src/content/docs/workers-ai/get-started/dashboard.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Follow this guide to create a Workers AI application using the Cloudflare dashboard.
 
@@ -26,12 +26,11 @@ To create a Workers AI application:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Under **Select a template**, select **LLM Chat App**.
 4. Select **Deploy**.
 5. Name your Worker, then select **Create and deploy**.
-6. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
+5. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
 
 ## Development
 
diff --git a/src/content/docs/workers-ai/get-started/index.mdx b/src/content/docs/workers-ai/get-started/index.mdx
index a6eeb86d18d02ef..707509ca784b6a0 100644
--- a/src/content/docs/workers-ai/get-started/index.mdx
+++ b/src/content/docs/workers-ai/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 There are several options to build your Workers AI projects on Cloudflare. To get started, choose your preferred method:
 
@@ -16,6 +16,8 @@ There are several options to build your Workers AI projects on Cloudflare. To ge
 
 :::note
 
+
 These examples are geared towards creating new Workers AI projects. For help adding Workers AI to an existing Worker, refer to [Workers Bindings](/workers-ai/configuration/bindings/).
 
+
 :::
diff --git a/src/content/docs/workers-ai/get-started/rest-api.mdx b/src/content/docs/workers-ai/get-started/rest-api.mdx
index bd2a6f0630db0aa..e25c56fa87f355a 100644
--- a/src/content/docs/workers-ai/get-started/rest-api.mdx
+++ b/src/content/docs/workers-ai/get-started/rest-api.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 This guide will instruct you through setting up and deploying your first Workers AI project. You will use the Workers AI REST API to experiment with a large language model (LLM).
 
@@ -28,7 +28,6 @@ To get these values:
 1. In the Cloudflare dashboard, go to the **Workers AI** page.
 
    <DashButton url="/?to=/:account/ai/workers-ai" />
-
 2. Select **Use REST API**.
 3. Get your API token:
    1. Select **Create a Workers AI API Token**.
diff --git a/src/content/docs/workers-ai/guides/agents.mdx b/src/content/docs/workers-ai/guides/agents.mdx
index 86751d6187c1375..1e57ab991facb86 100644
--- a/src/content/docs/workers-ai/guides/agents.mdx
+++ b/src/content/docs/workers-ai/guides/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workers-ai
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
index 3b27b14dfda0ebb..bc3a24a9954b382 100644
--- a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
@@ -14,7 +14,9 @@ products:
   - workers-ai
 ---
 
-import { YouTube } from "~/components";
+
+
+import { YouTube } from "~/components"
 
 A handy way to explore all of the models available on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -24,7 +26,7 @@ You can [download the DeepSeek Coder notebook](/workers-ai/static/documentation/
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
----
+***
 
 ## Exploring Code Generation Using DeepSeek Coder
 
@@ -227,8 +229,8 @@ if __name__ == '__main__':
 
 In this test case, we have two tests:
 
-- `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
-- `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
+* `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
+* `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
 
 If all these tests pass, it means that the `full_name` method is working as expected. If any of these tests fail, it
 
@@ -344,9 +346,9 @@ display(Markdown(f"""
 
 ```json
 {
-	"firstName": "Craig",
-	"lastName": "Dennis",
-	"numKids": 2,
-	"interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
+  "firstName": "Craig",
+  "lastName": "Dennis",
+  "numKids": 2,
+  "interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
 }
 ```
diff --git a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
index bb75cb0837843ae..3ca61769775d494 100644
--- a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
@@ -17,7 +17,9 @@ products:
   - workers-ai
 ---
 
-import { YouTube } from "~/components";
+
+
+import { YouTube } from "~/components"
 
 A great way to explore the models that are available to you on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -27,7 +29,7 @@ You can [download the Workers AI Text Generation Exploration notebook](/workers-
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
----
+***
 
 ## How to Choose The Right Text Generation Model
 
@@ -146,7 +148,7 @@ questions = [
 speed_date(models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -170,9 +172,9 @@ speed_date(models, questions)
 
 *Generated in *3.63* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -192,9 +194,9 @@ speed_date(models, questions)
 
 *Generated in *4.33* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -214,9 +216,9 @@ speed_date(models, questions)
 
 *Generated in *3.15* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -240,9 +242,9 @@ Remember, these are just a few examples, and your use cases may vary depending o
 
 *Generated in *2.92* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -270,7 +272,7 @@ That's me in a nutshell! I'm ready to help with a wide range of tasks, so feel f
 
 *Generated in *10.28* seconds*
 
----
+***
 
 ### Language Translation
 
@@ -297,7 +299,7 @@ questions = [f"""Translate "{phrase}" from "English" to "{language}" """
 speed_date(proud_translator_models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -387,9 +389,9 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *3.44* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -465,7 +467,7 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *1.51* seconds*
 
----
+***
 
 ### Information Retrieval and Summarization
 
@@ -491,7 +493,7 @@ questions = [f"""Summarize the book "{book}" into a few sentences. Ensure to inc
 speed_date(proud_summarizers, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -519,9 +521,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *8.34* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -543,9 +545,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.04* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -567,7 +569,7 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.66* seconds*
 
----
+***
 
 ### Content Creation
 
@@ -589,7 +591,7 @@ questions = [
 speed_date(proud_content_creator_models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -625,9 +627,9 @@ I hope these suggestions help! Let me know if you have any other questions or if
 
 *Generated in *1.13* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -657,9 +659,9 @@ Tagline: "Say goodbye to cable chaos and hello to a clutter-free workspace with
 
 *Generated in *1.33* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -700,15 +702,15 @@ Sure, here's a headline for a blog on why you should use me specifically over ot
 
 Here's a brief summary of why I stand out from other models:
 
-- Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
-- Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
-- Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
+* Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
+* Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
+* Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
 
 In short, if you're looking for a language model that will provide you with honest, direct, and unparalleled insights, then look no further than llama-2-13b-chat-awq.
 
 *Generated in *10.24* seconds*
 
----
+***
 
 ### Text Classification
 
@@ -739,7 +741,7 @@ sentiment_questions = [sentiment_prompt_template.format(text=comment) for commen
 speed_date(proud_classifiers, sentiment_questions)
 ```
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -785,9 +787,9 @@ The sentiment of the text is positive.
 
 *Generated in *0.89* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -831,4 +833,4 @@ The sentiment of the text is positive.
 
 *Generated in *1.93* seconds*
 
----
+***
diff --git a/src/content/docs/workers-ai/platform/data-usage.mdx b/src/content/docs/workers-ai/platform/data-usage.mdx
index bab6821ff99f590..9b29840f9db5768 100644
--- a/src/content/docs/workers-ai/platform/data-usage.mdx
+++ b/src/content/docs/workers-ai/platform/data-usage.mdx
@@ -19,7 +19,7 @@ Your inputs (e.g., text prompts, image submissions, audio files, etc.), outputs
 
 For Workers AI:
 
-- You own, and are responsible for, all of your Customer Content.
-- Cloudflare does not make your Customer Content available to any other Cloudflare customer.
-- Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
-- Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
+* You own, and are responsible for, all of your Customer Content.
+* Cloudflare does not make your Customer Content available to any other Cloudflare customer.
+* Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
+* Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
diff --git a/src/content/docs/workers-ai/platform/pricing.mdx b/src/content/docs/workers-ai/platform/pricing.mdx
index 474edbfe1bdd8fb..fd38831c6ee17fc 100644
--- a/src/content/docs/workers-ai/platform/pricing.mdx
+++ b/src/content/docs/workers-ai/platform/pricing.mdx
@@ -35,38 +35,38 @@ The Price in Tokens column is equivalent to the Price in Neurons column - the di
 
 ## LLM model pricing
 
-| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                        |
-| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
-| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
-| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
-| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                               |
-| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                                |
-| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
-| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
-| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
-| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                               |
-| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                 |
-| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                                |
-| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                                |
-| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
-| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
-| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
-| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                                |
-| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
-| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
-| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                 |
-| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                 |
-| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                               |
-| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens  |
+| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                       |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                |
+| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                |
+| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
+| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
+| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                              |
+| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                               |
+| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
+| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
+| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
+| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                              |
+| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                |
+| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                               |
+| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                               |
+| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
+| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
+| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
+| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                               |
+| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                               |
+| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
+| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                |
+| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                |
+| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                              |
+| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens |
 | @cf/moonshotai/kimi-k2.6                     | $0.950 per M input tokens <br/> $0.160 per M cached input tokens <br/> $4.000 per M output tokens | 86364 neurons per M input tokens <br/> 14545 neurons per M cached input tokens <br/> 363636 neurons per M output tokens |
-| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                 |
+| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
 
 ## Embeddings model pricing
 
diff --git a/src/content/docs/workers-vpc/configuration/index.mdx b/src/content/docs/workers-vpc/configuration/index.mdx
index e669ed279505b79..aee79d0d23cdc78 100644
--- a/src/content/docs/workers-vpc/configuration/index.mdx
+++ b/src/content/docs/workers-vpc/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
index da1a8323544eed5..e5d02896289509c 100644
--- a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
+++ b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
@@ -128,7 +128,6 @@ resource "cloudflare_connectivity_directory_service" "my_database" {
 ```
 
 Valid values for `cert_verification_mode` are:
-
 - `verify_full` (default)
 - `verify_ca`
 - `disabled`
diff --git a/src/content/docs/workers-vpc/examples/private-api.mdx b/src/content/docs/workers-vpc/examples/private-api.mdx
index 09e90435cc172fe..48bc4d0013d7733 100644
--- a/src/content/docs/workers-vpc/examples/private-api.mdx
+++ b/src/content/docs/workers-vpc/examples/private-api.mdx
@@ -87,9 +87,7 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch data from internal API and process it before returning
-			const response = await env.INTERNAL_API.fetch(
-				"http://10.0.1.50:8080/api/data",
-			);
+			const response = await env.INTERNAL_API.fetch("http://10.0.1.50:8080/api/data");
 
 			// Use the response of the private API to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
index 3312f993bec679d..12fb5230fee07fe 100644
--- a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
+++ b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
@@ -125,9 +125,7 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch a file from the private S3 bucket via VPC endpoint
-			const response = await env.S3_STORAGE.fetch(
-				"https://s3.us-west-2.amazonaws.com/my-bucket/data.json",
-			);
+			const response = await env.S3_STORAGE.fetch("https://s3.us-west-2.amazonaws.com/my-bucket/data.json");
 
 			// Use the response from S3 to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
index 60995de99ab8b3c..6bc0349de2f2609 100644
--- a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
+++ b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
@@ -72,19 +72,15 @@ export default {
 		const url = new URL(request.url);
 
 		// Route to internal services
-		if (url.pathname.startsWith("/api/users")) {
-			const response = await env.USER_SERVICE.fetch(
-				"https://user-api.internal.example.com" + url.pathname,
-			);
+		if (url.pathname.startsWith('/api/users')) {
+			const response = await env.USER_SERVICE.fetch("https://user-api.internal.example.com" + url.pathname);
 			return response;
-		} else if (url.pathname.startsWith("/api/orders")) {
-			const response = await env.ORDER_SERVICE.fetch(
-				"https://orders-api.internal.example.com" + url.pathname,
-			);
+		} else if (url.pathname.startsWith('/api/orders')) {
+			const response = await env.ORDER_SERVICE.fetch("https://orders-api.internal.example.com" + url.pathname);
 			return response;
 		}
 
-		return new Response("Not Found", { status: 404 });
+		return new Response('Not Found', { status: 404 });
 	},
 };
 ```
@@ -111,3 +107,4 @@ curl https://api-gateway.workers.dev/api/orders
 - Implement [rate limiting](/durable-objects/api/)
 - Set up [monitoring and alerting](/analytics/analytics-engine/)
 - Explore [other examples](/workers-vpc/examples/)
+
diff --git a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
index 42c63e8209e1e50..570cd2dcec2d850 100644
--- a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
+++ b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
@@ -53,7 +53,6 @@ When you merge the PR, Workers Builds will update your build and deploy commands
 If Workers Builds detects a mismatch between your Worker name in the Cloudflare dashboard and the `name` field in your Wrangler configuration file, it will create a pull request to fix the conflict.
 
 This can happen when:
-
 - You rename your Worker in the dashboard but not in your config file
 - You connect a repository that was previously used with a different Worker
 - The `name` field in your config does not match the connected Worker
diff --git a/src/content/docs/workers/ci-cd/builds/build-caching.mdx b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
index 603f75d3db137a1..83e4dd1c9c17496 100644
--- a/src/content/docs/workers/ci-cd/builds/build-caching.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
@@ -35,15 +35,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                            |
-| ---------- | --------------------------------------------- |
-| Astro      | `node_modules/.astro`                         |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
-| Eleventy   | `.cache`                                      |
-| Gatsby     | `.cache`, `public`                            |
-| Next.js    | `.next/cache`                                 |
-| Nuxt       | `node_modules/.cache/nuxt`                    |
-| SvelteKit  | `node_modules/.cache/imagetools`              |
+| Framework  | Directories cached                                          |
+| ---------- | ----------------------------------------------------------- |
+| Astro      | `node_modules/.astro`                                       |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
+| Eleventy   | `.cache`                                                    |
+| Gatsby     | `.cache`, `public`                                          |
+| Next.js    | `.next/cache`                                               |
+| Nuxt       | `node_modules/.cache/nuxt`                                  |
+| SvelteKit  | `node_modules/.cache/imagetools`                            |
 
 :::note
 [Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers.
diff --git a/src/content/docs/workers/ci-cd/builds/build-image.mdx b/src/content/docs/workers/ci-cd/builds/build-image.mdx
index 0daab950f2f9c35..828b464902269e7 100644
--- a/src/content/docs/workers/ci-cd/builds/build-image.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-image.mdx
@@ -91,6 +91,7 @@ Workers Builds are run in the following environment:
 | **Build Environment** | Ubuntu 24.04 |
 | **Architecture**      | x86_64       |
 
+
 ## Build Image Policy
 
 ### Preinstalled Software Updates
@@ -101,7 +102,6 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
-
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -111,6 +111,5 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
-
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
index 6d533ab9b2cede9..032d023592e4d4f 100644
--- a/src/content/docs/workers/ci-cd/builds/configuration.mdx
+++ b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -8,13 +8,7 @@ products:
   - workers
 ---
 
-import {
-	DirectoryListing,
-	Render,
-	Tabs,
-	TabItem,
-	DashButton,
-} from "~/components";
+import { DirectoryListing, Render, Tabs, TabItem, DashButton } from "~/components";
 
 When connecting your Git repository to your Worker, you can customize the configurations needed to build and deploy your Worker.
 
@@ -41,7 +35,7 @@ Note that when you update and save build settings, the updated settings will be
 | **Git repository**                                                                                                    | Choose the Git repository you would like to connect your Worker to.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | **Git branch**                                                                                                        | Select the branch you would like Cloudflare to listen to for new commits. This will be defaulted to `main`.                                                                                                                                                                                                                                                                                                                                                                            |
 | **Build command** _(Optional)_                                                                                        | Set a build command if your project requires a build step (e.g. `npm run build`). This is necessary, for example, when using a [front-end framework](/workers/ci-cd/builds/configuration/#framework-support) such as Next.js or Remix.                                                                                                                                                                                                                                                 |
-| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                         |
+| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                                 |
 | **[Non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command)** | Set a command to run when executing [a build for commit on a non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds). This will default to `npx wrangler versions upload` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                    |
 | **Root directory** _(Optional)_                                                                                       | Specify the path to your project. The root directory defines where the build command will be run and can be helpful in [monorepos](/workers/ci-cd/builds/advanced-setups/#monorepos) to isolate a specific project within the repository for builds.                                                                                                                                                                                                                                   |
 | **[API token](/workers/ci-cd/builds/configuration/#api-token)** _(Optional)_                                          | The API token is used to authenticate your build request and authorize the upload and deployment of your Worker to Cloudflare. By default, Cloudflare will automatically generate an API token for your account when using Workers Builds, and continue to use this API token for all subsequent builds. Alternatively, you can [create your own API token](/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication/#generate-tokens), or select one that you already own. |
@@ -134,4 +128,4 @@ The following system environment variables are injected by default (but can be o
 | `WORKERS_CI`            | `1`                             | Changing build behaviour when run on Workers Builds versus locally                      |
 | `WORKERS_CI_BUILD_UUID` | `<build-uuid-of-current-build>` | Passing the Build UUID along to custom workflows                                        |
 | `WORKERS_CI_COMMIT_SHA` | `<sha1-hash-of-current-commit>` | Passing current commit ID to error reporting, for example, Sentry                       |
-| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
+| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
index 6438ba7c4ac10cf..19c36e00c988216 100644
--- a/src/content/docs/workers/ci-cd/builds/index.mdx
+++ b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets you connect a new or existing Worker to a GitHub or GitLab repository, enabling automated builds and deployments for your Worker on push.
@@ -17,7 +16,6 @@ The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets yo
 ### Connect a new Worker
 
 To create a new Worker and connect it to a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -32,7 +30,6 @@ To create a new Worker and connect it to a GitHub or GitLab repository:
 ### Connect an existing Worker
 
 To connect an existing Worker to a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -74,15 +71,14 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 ## Disconnecting builds
 
 To disconnect a Worker from a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select the Worker you want to disconnect from a repository.
-3. Select **Settings** and then **Builds**.
-4. Select **Disconnect**.
+4. Select **Settings** and then **Builds**.
+5. Select **Disconnect**.
 
 If you want to switch to a different repository for your Worker, you must first disable builds, then reconnect to select the new repository.
 
-To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
+To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
index b5fe2e420f07c48..12161e725454792 100644
--- a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
+++ b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
@@ -8,19 +8,19 @@ products:
   - workers
 ---
 
-Workers Builds has the following limits.
+Workers Builds has the following limits. 
 
-| Metric                            | Free plan                              | Paid plans                                 |
-| --------------------------------- | -------------------------------------- | ------------------------------------------ |
-| **Build minutes**                 | 3,000 per month                        | 6,000 per month (then, +$0.005 per minute) |
-| **Concurrent builds**             | 1                                      | 6                                          |
-| **Build timeout**                 | 20 minutes                             | 20 minutes                                 |
-| **Deploy Hooks**                  | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account     |
-| **CPU**                           | 2 vCPU                                 | 4 vCPU                                     |
-| **Memory**                        | 8 GB                                   | 8 GB                                       |
-| **Disk space**                    | 20 GB                                  | 20 GB                                      |
-| **Environment variables**         | 64                                     | 64                                         |
-| **Size per environment variable** | 5 KB                                   | 5 KB                                       |
+| Metric                | Free plan       | Paid plans                                 |
+| --------------------- | --------------- | ------------------------------------------ |
+| **Build minutes**     | 3,000 per month | 6,000 per month (then, +$0.005 per minute) |
+| **Concurrent builds** | 1               | 6                                          |
+| **Build timeout**     | 20 minutes      | 20 minutes                                 |
+| **Deploy Hooks**      | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account |
+| **CPU**               | 2 vCPU          | 4 vCPU                                     |
+| **Memory**            | 8 GB            | 8 GB                                       |
+| **Disk space**        | 20 GB           | 20 GB                                      |
+| **Environment variables**  | 64              | 64                                        |
+| **Size per environment variable**  | 5 KB            | 5 KB                                       |
 
 ## Definitions
 
diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
index 34a4b8f9fba5a10..19e65105b5e0d03 100644
--- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
+++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
@@ -35,7 +35,6 @@ On Wrangler v3 and up, Workers Builds automatically matches the name of the conn
 `✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. wrangler deploy path/to/script) or the main config field.`
 
 If you see this error, a Wrangler configuration file is likely missing from the root directory. Navigate to **Settings** > **Build** > **Build Configuration** to update the root directory, or add a [Wrangler configuration file](/workers/wrangler/configuration/) to the specified directory.
-
 ### Incorrect account_id
 
 `Could not route to /client/v4/accounts/<Account ID>/workers/services/<Worker name>, perhaps your object identifier is invalid? [code: 7003]`
diff --git a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
index f67f5ae1685a419..2eae230b3612062 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
@@ -5,7 +5,6 @@ description: Integrate Workers development into your existing GitHub Actions wor
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitHub Actions](https://github.com/marketplace/actions/deploy-to-cloudflare-workers-with-wrangler). Here is how you can set up your GitHub Actions workflow.
@@ -21,7 +20,6 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
 ### API token
 
 To create an API token to authenticate Wrangler in your CI job:
-
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
diff --git a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
index 713a4dfc47d7707..ad35eea9bad7ff5 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
@@ -5,7 +5,6 @@ description: Integrate Workers development into your existing GitLab Pipelines w
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitLab CI/CD](https://docs.gitlab.com/ee/ci/pipelines/index.html). Here is how you can set up your Gitlab CI/CD pipeline.
diff --git a/src/content/docs/workers/configuration/integrations/index.mdx b/src/content/docs/workers/configuration/integrations/index.mdx
index e9f73b20e932138..23a188bf0e4e94c 100644
--- a/src/content/docs/workers/configuration/integrations/index.mdx
+++ b/src/content/docs/workers/configuration/integrations/index.mdx
@@ -14,24 +14,24 @@ One of the key features of Cloudflare Workers is the ability to integrate with o
 
 Cloudflare Workers offers several types of integrations, including:
 
-- [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
-- [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
-- [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
+* [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
+* [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
+* [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
 
 ## How to use integrations
 
 To use any of the available integrations:
 
-- Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
-- In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
-- Use the provided APIs and functions to connect to the integration and access its data or functionality.
-- Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
+* Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
+* In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
+* Use the provided APIs and functions to connect to the integration and access its data or functionality.
+* Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
 
 ## Tips and best practices
 
 To help you get the most out of using integrations with Cloudflare Workers:
 
-- Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
-- Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
-- Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
-- Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
+* Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
+* Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
+* Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
+* Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
diff --git a/src/content/docs/workers/configuration/routing/custom-domains.mdx b/src/content/docs/workers/configuration/routing/custom-domains.mdx
index dccd631d43e8638..be78f27efb57efa 100644
--- a/src/content/docs/workers/configuration/routing/custom-domains.mdx
+++ b/src/content/docs/workers/configuration/routing/custom-domains.mdx
@@ -14,7 +14,7 @@ Custom Domains allow you to connect your Worker to a domain or subdomain, withou
 
 Custom Domains are routes to a domain or subdomain (such as `example.com` or `shop.example.com`) within a Cloudflare zone where the Worker is the origin.
 
-Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with. If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
+Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with.  If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
 
 Custom Domains can stack on top of each other. For example, if you have Worker A attached to `app.example.com` and Worker B attached to `api.example.com`, Worker A can call `fetch()` on `api.example.com` and invoke Worker B.
 
@@ -33,8 +33,10 @@ Custom Domains can be attached to your Worker via the Cloudflare dashboard, [Wra
 
 :::caution
 
+
 You cannot create a Custom Domain on a hostname with an existing CNAME DNS record or on a zone you do not own.
 
+
 :::
 
 ### Set up a Custom Domain in the dashboard
@@ -75,6 +77,8 @@ To configure a Custom Domain in your [Wrangler configuration file](/workers/wran
 
 To configure multiple Custom Domains:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -102,8 +106,8 @@ On the same zone, if a Worker is attempting to communicate with a target Worker
 
 For example, consider the following scenario, where both Workers are running on the `example.com` Cloudflare zone:
 
-- `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
-- `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
+* `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
+* `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
 
 If `worker-a` sends a fetch request to `worker-b`, the request will fail, because of the limitation on same-zone fetch requests. `worker-a` must have a service binding to `worker-b` for this request to resolve.
 
@@ -111,9 +115,9 @@ If `worker-a` sends a fetch request to `worker-b`, the request will fail, becaus
 export default {
 	fetch(request) {
 		// This will fail
-		return fetch("https://shop.example.com");
-	},
-};
+		return fetch("https://shop.example.com")
+	}
+}
 ```
 
 However, if `worker-b` was instead set up to run on the Custom Domain `shop.example.com`, the fetch request would succeed.
@@ -138,15 +142,15 @@ For example, consider the following workflow:
 ```js title="auth-worker" {8}
 export default {
 	fetch(request) {
-		const url = new URL(request.url);
-		if (url.searchParams.get("auth") !== "SECRET_TOKEN") {
-			return new Response(null, { status: 401 });
+		const url = new URL(request.url)
+		if(url.searchParams.get("auth") !== "SECRET_TOKEN") {
+			return new Response(null, { status: 401 })
 		} else {
 			// This will invoke `api-worker`
-			return fetch(request);
+			return fetch(request)
 		}
-	},
-};
+	}
+}
 ```
 
 ## Certificates
@@ -162,10 +166,10 @@ Because Custom Domains require an exact hostname match, a Worker attached to `ex
 - [Redirect from www to root](/rules/url-forwarding/examples/redirect-www-to-root/)
 - [Redirect from root to www](/rules/url-forwarding/examples/redirect-root-to-www/)
 
-You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting _from_, so that Cloudflare can apply the redirect rule.
+You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting *from*, so that Cloudflare can apply the redirect rule.
 
-- For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
-- For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+  - For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+  - For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
 
 :::note
 `192.0.2.0` (A record) and `100::` (AAAA record) are [reserved placeholder addresses](/dns/manage-dns-records/how-to/create-dns-records/#originless-setups) for originless setups. Because the DNS record is proxied, requests never reach this address — Cloudflare intercepts them and applies your redirect rule.
@@ -220,4 +224,4 @@ To migrate the route `example.com/*` in your [Wrangler configuration file](/work
    </WranglerConfig>
 
 4. Run `npx  wrangler deploy` to create the Custom Domain your Worker will run on.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/workers/configuration/routing/routes.mdx b/src/content/docs/workers/configuration/routing/routes.mdx
index 977bc4da059df0f..867c38239a1de4e 100644
--- a/src/content/docs/workers/configuration/routing/routes.mdx
+++ b/src/content/docs/workers/configuration/routing/routes.mdx
@@ -95,6 +95,8 @@ Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `z
 
 To add multiple routes:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -192,12 +194,12 @@ Because `*` matches zero or more of **any character** (not just subdomains), `*e
 
 The following examples illustrate the difference between `*example.com/*` and `*.example.com/*`:
 
-| Request URL                    | `*example.com/*` | `*.example.com/*` |
-| ------------------------------ | ---------------- | ----------------- |
-| `https://example.com/`         | Matches          | Does not match    |
-| `https://www.example.com/path` | Matches          | Matches           |
-| `https://myexample.com/`       | Matches          | Does not match    |
-| `https://not-example.com/`     | Does not match   | Does not match    |
+| Request URL | `*example.com/*` | `*.example.com/*` |
+|---|---|---|
+| `https://example.com/` | Matches | Does not match |
+| `https://www.example.com/path` | Matches | Matches |
+| `https://myexample.com/` | Matches | Does not match |
+| `https://not-example.com/` | Does not match | Does not match |
 
 #### Paths may optionally end with `*`
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-existing.mdx b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
index 005eac692d1bd1f..5ec6aea9c3faf4a 100644
--- a/src/content/docs/workers/configuration/sites/start-from-existing.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
@@ -40,16 +40,16 @@ To deploy a pre-existing static site project, start with a pre-generated site. W
 2. Add your site's build/output directory to the Wrangler file:
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "site": {
-          "bucket": "./public" // <-- Add your build directory name here.
-        }
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "site": {
+       "bucket": "./public" // <-- Add your build directory name here.
+     }
+   }
+   ```
+
+   </WranglerConfig>
 
    The default directories for the most popular static site generators are listed below:
    - Hugo: `public`
@@ -138,14 +138,14 @@ async function handleEvent(event) {
 6. Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone. Add a `route` property to the Wrangler file.
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "route": "https://example.com/*"
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "route": "https://example.com/*"
+   }
+   ```
+
+   </WranglerConfig>
 
    :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
index 4406df19ce0437c..8dd326cda0b305d 100644
--- a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
@@ -55,39 +55,39 @@ The template project contains the following files and directories:
 - Change the `name` property to the name of your project:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "$schema": "./node_modules/wrangler/config-schema.json",
-      "name": "my-site"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "$schema": "./node_modules/wrangler/config-schema.json",
+    "name": "my-site"
+  }
+  ```
+
+  </WranglerConfig>
 
 - Consider updating`compatibility_date` to today's date to get access to the most recent Workers features:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "compatibility_date": "yyyy-mm-dd"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "compatibility_date": "yyyy-mm-dd"
+  }
+  ```
+
+  </WranglerConfig>
 
 - Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "route": "https://example.com/*"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "route": "https://example.com/*"
+  }
+  ```
+
+  </WranglerConfig>
 
   :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-worker.mdx b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
index 78314e60913a490..55e9d74a41f69f7 100644
--- a/src/content/docs/workers/configuration/sites/start-from-worker.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
@@ -24,16 +24,16 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st
 2. Add configuration to your Wrangler file to point to it.
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "site": {
-          "bucket": "./public" // Add the directory with your static assets!
-        }
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "site": {
+       "bucket": "./public" // Add the directory with your static assets!
+     }
+   }
+   ```
+
+   </WranglerConfig>
 
 3. Install the `@cloudflare/kv-asset-handler` package in your project:
 
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
index c5f131c4787fd9c..c32f452efe28734 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
@@ -6,7 +6,6 @@ description: Upload versions of Workers and create deployments to release new ve
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 Versions track changes to your Worker. Deployments configure how those changes are deployed to your traffic.
@@ -108,3 +107,4 @@ Refer to [Migrate from Service Workers to ES modules](/workers/reference/migrate
 ### Durable Object migrations
 
 Uploading a version with [Durable Object migrations](/durable-objects/reference/durable-objects-migrations/) is not supported. Use [`wrangler deploy`](/workers/wrangler/commands/workers/#deploy) if you are applying a [Durable Object migration](/durable-objects/reference/durable-objects-migrations/).
+
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
index 49bb0247b41f32f..6e0adad52574968 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
@@ -65,9 +65,9 @@ If you forward the original request object, the override header carries through
 ```js
 // The override header from the inbound request is forwarded to the downstream Worker.
 export default {
-	async fetch(request, env) {
-		return env.MY_SERVICE.fetch(request);
-	},
+  async fetch(request, env) {
+    return env.MY_SERVICE.fetch(request);
+  },
 };
 ```
 
@@ -76,15 +76,15 @@ Alternatively, you can set an override header explicitly:
 ```js
 // Replace the version ID with the target version from `wrangler versions list`.
 export default {
-	async fetch(request, env) {
-		const response = await env.MY_SERVICE.fetch("https://example.com/", {
-			headers: {
-				"Cloudflare-Workers-Version-Overrides":
-					'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
-			},
-		});
-		return response;
-	},
+  async fetch(request, env) {
+    const response = await env.MY_SERVICE.fetch("https://example.com/", {
+      headers: {
+        "Cloudflare-Workers-Version-Overrides":
+          'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
+      },
+    });
+    return response;
+  },
 };
 ```
 
diff --git a/src/content/docs/workers/configuration/workers-with-page-rules.mdx b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
index b50db0cc22a9f9c..f165f162646c204 100644
--- a/src/content/docs/workers/configuration/workers-with-page-rules.mdx
+++ b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
@@ -32,39 +32,43 @@ If you are experiencing Page Rule errors when running Workers, contact your Clou
 
 The following Page Rules may not work as expected when an incoming request is matched to a Worker route:
 
-- Always Online
-- [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
-- [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
-- [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
-- [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
-- [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
-- [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
-- Disable Apps
-- [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
-- [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
-- [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
-- [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
-- Host Header Override
-- [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
-- [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
-- [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
-- [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
-- [SSL](/workers/configuration/workers-with-page-rules/#ssl)
+* Always Online
+* [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
+* [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
+* [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
+* [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
+* [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
+* [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
+* Disable Apps
+* [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
+* [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
+* [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
+* [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
+* Host Header Override
+* [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
+* [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
+* [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
+* [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
+* [SSL](/workers/configuration/workers-with-page-rules/#ssl)
 
 This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.
 
 :::caution[Testing]
 
+
 Due to ongoing changes to the Workers runtime, detailed documentation on how these rules will be affected are updated following testing.
 
+
 :::
 
 To learn what these Page Rules do, refer to [Page Rules](/rules/page-rules/).
 
 :::note[Same zone versus other zone]
 
+
 A same zone subrequest is a request the Worker makes to an orange-clouded hostname in the same zone the Worker runs on. Depending on your DNS configuration, any request that falls outside that definition may be considered an other zone request by the Cloudflare network.
 
+
 :::
 
 ### Always Use HTTPS
@@ -133,11 +137,11 @@ A same zone subrequest is a request the Worker makes to an orange-clouded hostna
 
 ### Email Obfuscation
 
-| Source | Target     | Behavior       |
-| ------ | ---------- | -------------- |
-| Client | Worker     | Rule Ignored   |
-| Worker | Same Zone  | Rule Respected |
-| Worker | Other Zone | Rule Ignored   |
+| Source     | Target     | Behavior       |
+| -------------------------|------------|------------|
+| Client     | Worker     | Rule Ignored   |
+| Worker     | Same Zone  | Rule Respected |
+| Worker     | Other Zone | Rule Ignored   |
 
 ### Forwarding URL
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
index 39d7ac436e98f44..ddd98b108387e07 100644
--- a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
@@ -12,9 +12,9 @@ import { Render, PackageManagers, Tabs, TabItem } from "~/components";
 
 :::note
 
-The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client.
+The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client. 
 
-If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/).
+If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/). 
 
 :::
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/turso.mdx b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
index a144bb3ba616abd..8467e1c8801cf6a 100644
--- a/src/content/docs/workers/databases/third-party-integrations/turso.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
@@ -92,7 +92,7 @@ To set up an integration with Turso:
    ```sh
    # Get your database URL
    turso db show my-db --url
-
+   
    # Create an authentication token
    turso db tokens create my-db
    ```
@@ -103,8 +103,8 @@ To set up an integration with Turso:
    # Add the database URL as a secret
    npx wrangler secret put TURSO_URL
    # When prompted, paste your database URL
-
-   # Add the authentication token as a secret
+   
+   # Add the authentication token as a secret  
    npx wrangler secret put TURSO_AUTH_TOKEN
    # When prompted, paste your authentication token
    ```
diff --git a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
index e34c59345e8275b..ebdc513a162cfd2 100644
--- a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
@@ -17,6 +17,7 @@ To set up an integration with Upstash:
 1. You need an existing Upstash database to connect to. [Create an Upstash database](https://docs.upstash.com/redis#create-a-database) or [load data from an existing database to Upstash](https://docs.upstash.com/redis/howto/connectclient).
 
 2. Insert some data to your Upstash database. You can add data to your Upstash database in two ways:
+
    - Use the CLI directly from your Upstash console.
    - Alternatively, install [redis-cli](https://redis.io/docs/getting-started/installation/) locally and run the following commands.
 
@@ -52,7 +53,7 @@ To set up an integration with Upstash:
    # Add the Upstash Redis URL as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_URL
    # When prompted, paste your Upstash Redis REST URL
-
+   
    # Add the Upstash Redis token as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_TOKEN
    # When prompted, paste your Upstash Redis REST token
diff --git a/src/content/docs/workers/databases/third-party-integrations/xata.mdx b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
index a7bcec8e02894d4..31cf393a9843646 100644
--- a/src/content/docs/workers/databases/third-party-integrations/xata.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
@@ -10,6 +10,7 @@ import { Render, TabItem, Tabs } from "~/components";
 
 [Xata](https://xata.io) is a PostgreSQL database platform designed to help developers operate and scale databases with enhanced productivity and performance. Xata provides features like instant copy-on-write database branches, zero-downtime schema changes, data anonymization, AI-powered performance monitoring, and BYOC.
 
+
 :::note
 
 You can connect to Xata using [Hyperdrive](/hyperdrive), which provides connection pooling and reduces the amount of round trips required to create a secure connection from Workers to your database.
diff --git a/src/content/docs/workers/development-testing/multi-workers.mdx b/src/content/docs/workers/development-testing/multi-workers.mdx
index c90270083c2c91e..42e37c1197aff58 100644
--- a/src/content/docs/workers/development-testing/multi-workers.mdx
+++ b/src/content/docs/workers/development-testing/multi-workers.mdx
@@ -22,11 +22,11 @@ We recommend this approach as the default for most development workflows as it e
 You can run multiple Workers in a single dev command by passing multiple configuration files to your dev server:
 
 **Using Wrangler**
-
+   
 <PackageManagers
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
 />
 
 The first config (`./app/wrangler.jsonc`) is treated as the primary Worker, exposed at `http://localhost:8787`. Additional configs (e.g. `./api/wrangler.jsonc`) run as auxiliary Workers, available via service bindings or tail consumers from the primary Worker.
@@ -40,16 +40,16 @@ import { defineConfig } from "vite";
 import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
-	plugins: [
-		cloudflare({
-			configPath: "./app/wrangler.jsonc",
-			auxiliaryWorkers: [
-				{
-					configPath: "./api/wrangler.jsonc",
-				},
-			],
-		}),
-	],
+  plugins: [
+    cloudflare({
+      configPath: "./app/wrangler.jsonc",
+      auxiliaryWorkers: [
+        {
+          configPath: "./api/wrangler.jsonc",
+        },
+      ],
+    }),
+  ],
 });
 ```
 
@@ -68,17 +68,17 @@ Then run:
 You can also run each Worker in separate dev commands, each with its own terminal and configuration.
 
 <PackageManagers
-	comment="Terminal 1"
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./app/wrangler.jsonc"
+  comment="Terminal 1"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./app/wrangler.jsonc"
 />
 
 <PackageManagers
-	comment="Terminal 2"
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./api/wrangler.jsonc"
+  comment="Terminal 2"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./api/wrangler.jsonc"
 />
 
 These Workers run in different dev commands but can still communicate with each other via service bindings or tail consumers **regardless of whether they are started with `wrangler dev` or `vite dev`**.
diff --git a/src/content/docs/workers/development-testing/testing.mdx b/src/content/docs/workers/development-testing/testing.mdx
index c5a0a61aa1c1e8c..d085cb4f503f58c 100644
--- a/src/content/docs/workers/development-testing/testing.mdx
+++ b/src/content/docs/workers/development-testing/testing.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 7
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/development-testing/vite-plugin.mdx b/src/content/docs/workers/development-testing/vite-plugin.mdx
index 60632a1db291f01..f11a1758026f45d 100644
--- a/src/content/docs/workers/development-testing/vite-plugin.mdx
+++ b/src/content/docs/workers/development-testing/vite-plugin.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 1
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx
index e61fa08d45b3e14..1a033e8825cce5d 100644
--- a/src/content/docs/workers/examples/103-early-hints.mdx
+++ b/src/content/docs/workers/examples/103-early-hints.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Allow a client to request static assets while waiting for the HTML response.
 tags:
   - Middleware
@@ -15,7 +16,6 @@ reviewed: 2022-08-12
 products:
   - workers
 ---
-
 import { DashButton, Steps, TabItem, Tabs } from "~/components";
 
 If you want to get started quickly, click on the button below.
diff --git a/src/content/docs/workers/examples/ab-testing.mdx b/src/content/docs/workers/examples/ab-testing.mdx
index bf57cc1256414cd..28b72e57b042734 100644
--- a/src/content/docs/workers/examples/ab-testing.mdx
+++ b/src/content/docs/workers/examples/ab-testing.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up an A/B test by controlling what response is served based on
   cookies. This version supports passing the request through to test and control
   on the origin, bypassing random assignment.
diff --git a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
index 79830e09a3e34f0..3947c1f80350fb6 100644
--- a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
+++ b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Access custom Cloudflare properties and control how Cloudflare features
   are applied to every request.
 tags:
diff --git a/src/content/docs/workers/examples/aggregate-requests.mdx b/src/content/docs/workers/examples/aggregate-requests.mdx
index 05f04def29f8b17..4666d5fd1baf002 100644
--- a/src/content/docs/workers/examples/aggregate-requests.mdx
+++ b/src/content/docs/workers/examples/aggregate-requests.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send two GET request to two urls and aggregates the responses into one
   response.
 tags:
diff --git a/src/content/docs/workers/examples/alter-headers.mdx b/src/content/docs/workers/examples/alter-headers.mdx
index 129e244ab485ac0..cec4c62a5d08212 100644
--- a/src/content/docs/workers/examples/alter-headers.mdx
+++ b/src/content/docs/workers/examples/alter-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of how to add, change, or delete headers sent in a request or
   returned in a response.
 tags:
diff --git a/src/content/docs/workers/examples/auth-with-headers.mdx b/src/content/docs/workers/examples/auth-with-headers.mdx
index cf1ff87eee06ec7..4903f1f12598379 100644
--- a/src/content/docs/workers/examples/auth-with-headers.mdx
+++ b/src/content/docs/workers/examples/auth-with-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Allow or deny a request based on a known pre-shared key in a header.
   This is not meant to replace the WebCrypto API.
 tags:
diff --git a/src/content/docs/workers/examples/basic-auth.mdx b/src/content/docs/workers/examples/basic-auth.mdx
index c4dbb71353b6c7f..84e8be086b49095 100644
--- a/src/content/docs/workers/examples/basic-auth.mdx
+++ b/src/content/docs/workers/examples/basic-auth.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Shows how to restrict access using the HTTP Basic schema.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/block-on-tls.mdx b/src/content/docs/workers/examples/block-on-tls.mdx
index c6edd048d5fafdc..43831741eb75193 100644
--- a/src/content/docs/workers/examples/block-on-tls.mdx
+++ b/src/content/docs/workers/examples/block-on-tls.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Inspects the incoming request's TLS version and blocks if under TLSv1.2.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/bulk-origin-proxy.mdx b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
index 943e7b6c4e8fea0..6760d74eafdc8fb 100644
--- a/src/content/docs/workers/examples/bulk-origin-proxy.mdx
+++ b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Resolve requests to your domain to a set of proxy third-party origin URLs.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/bulk-redirects.mdx b/src/content/docs/workers/examples/bulk-redirects.mdx
index f6c5d881a4b4ef6..623d39afaf43402 100644
--- a/src/content/docs/workers/examples/bulk-redirects.mdx
+++ b/src/content/docs/workers/examples/bulk-redirects.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Redirect requests to certain URLs based on a mapped object to the
   request's URL.
 tags:
diff --git a/src/content/docs/workers/examples/cache-api.mdx b/src/content/docs/workers/examples/cache-api.mdx
index 34e592721b3174c..3bb0c1b6578703f 100644
--- a/src/content/docs/workers/examples/cache-api.mdx
+++ b/src/content/docs/workers/examples/cache-api.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the Cache API to store responses in Cloudflare's cache.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-post-request.mdx b/src/content/docs/workers/examples/cache-post-request.mdx
index 3c7f7548bf22aef..2fb05d6f62ead04 100644
--- a/src/content/docs/workers/examples/cache-post-request.mdx
+++ b/src/content/docs/workers/examples/cache-post-request.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Cache POST requests using the Cache API.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-tags.mdx b/src/content/docs/workers/examples/cache-tags.mdx
index 248effca15f46bc..0a85395341521d5 100644
--- a/src/content/docs/workers/examples/cache-tags.mdx
+++ b/src/content/docs/workers/examples/cache-tags.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send Additional Cache Tags using Workers
 tags:
   - Caching
diff --git a/src/content/docs/workers/examples/cache-using-fetch.mdx b/src/content/docs/workers/examples/cache-using-fetch.mdx
index b3f9f1cd60b870c..2270d27f236d16a 100644
--- a/src/content/docs/workers/examples/cache-using-fetch.mdx
+++ b/src/content/docs/workers/examples/cache-using-fetch.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Determine how to cache a resource by setting TTLs, custom cache keys,
   and cache headers in a fetch request.
 tags:
@@ -563,6 +564,6 @@ When `no-cache` is supplied the cache is forced to revalidate the currently cach
 origin.
 
 ```js
-fetch(request, { cache: "no-store" });
-fetch(request, { cache: "no-cache" });
+fetch(request, { cache: 'no-store'});
+fetch(request, { cache: 'no-cache'});
 ```
diff --git a/src/content/docs/workers/examples/conditional-response.mdx b/src/content/docs/workers/examples/conditional-response.mdx
index 0772d216c56f507..f6b109c19de1a2f 100644
--- a/src/content/docs/workers/examples/conditional-response.mdx
+++ b/src/content/docs/workers/examples/conditional-response.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Return a response based on the incoming request's URL, HTTP method,
   User Agent, IP address, ASN or device type.
 tags:
diff --git a/src/content/docs/workers/examples/cors-header-proxy.mdx b/src/content/docs/workers/examples/cors-header-proxy.mdx
index c6eacdd133464f7..8335f92850f2e62 100644
--- a/src/content/docs/workers/examples/cors-header-proxy.mdx
+++ b/src/content/docs/workers/examples/cors-header-proxy.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Add the necessary CORS headers to a third party API response.
 tags:
   - Security
@@ -715,3 +716,4 @@ return response.json()
 }
 ```
 </TabItem> </Tabs>
+
diff --git a/src/content/docs/workers/examples/country-code-redirect.mdx b/src/content/docs/workers/examples/country-code-redirect.mdx
index 19a10589a4fb622..ca3af654f791168 100644
--- a/src/content/docs/workers/examples/country-code-redirect.mdx
+++ b/src/content/docs/workers/examples/country-code-redirect.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Redirect a response based on the country code in the header of a visitor.
 tags:
   - Redirects
diff --git a/src/content/docs/workers/examples/data-loss-prevention.mdx b/src/content/docs/workers/examples/data-loss-prevention.mdx
index ce5c655a6d71251..8483ccab86121e9 100644
--- a/src/content/docs/workers/examples/data-loss-prevention.mdx
+++ b/src/content/docs/workers/examples/data-loss-prevention.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Protect sensitive data to prevent data loss, and send alerts to a
   webhooks server in the event of a data breach.
 tags:
diff --git a/src/content/docs/workers/examples/debugging-logs.mdx b/src/content/docs/workers/examples/debugging-logs.mdx
index 33128a13520e036..ac22a6f78f37918 100644
--- a/src/content/docs/workers/examples/debugging-logs.mdx
+++ b/src/content/docs/workers/examples/debugging-logs.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send debugging information in an errored response to a logging service.
 tags:
   - Debugging
diff --git a/src/content/docs/workers/examples/extract-cookie-value.mdx b/src/content/docs/workers/examples/extract-cookie-value.mdx
index 2d1e1e7afa6b59d..26eeba1adfb4182 100644
--- a/src/content/docs/workers/examples/extract-cookie-value.mdx
+++ b/src/content/docs/workers/examples/extract-cookie-value.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Given the cookie name, get the value of a cookie. You can also use
   cookies for A/B testing.
 tags:
diff --git a/src/content/docs/workers/examples/fetch-json.mdx b/src/content/docs/workers/examples/fetch-json.mdx
index ea574ed80ffa5a5..e803fee74e049cb 100644
--- a/src/content/docs/workers/examples/fetch-json.mdx
+++ b/src/content/docs/workers/examples/fetch-json.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send a GET request and read in JSON from the response. Use to fetch
   external data.
 pcx_content_type: example
diff --git a/src/content/docs/workers/examples/geolocation-app-weather.mdx b/src/content/docs/workers/examples/geolocation-app-weather.mdx
index 903b1906ea7da65..da915f46349f806 100644
--- a/src/content/docs/workers/examples/geolocation-app-weather.mdx
+++ b/src/content/docs/workers/examples/geolocation-app-weather.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Fetch weather data from an API using the user's geolocation data.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-custom-styling.mdx b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
index 9010b98d7034c34..9e5888fbd2a51de 100644
--- a/src/content/docs/workers/examples/geolocation-custom-styling.mdx
+++ b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Personalize website styling based on localized user time.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-hello-world.mdx b/src/content/docs/workers/examples/geolocation-hello-world.mdx
index 9e9f01f835ea0c3..ca32cc280b07052 100644
--- a/src/content/docs/workers/examples/geolocation-hello-world.mdx
+++ b/src/content/docs/workers/examples/geolocation-hello-world.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Get all geolocation data fields and display them in HTML.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/hot-link-protection.mdx b/src/content/docs/workers/examples/hot-link-protection.mdx
index b0773924fca66d4..4a7d1a997e16191 100644
--- a/src/content/docs/workers/examples/hot-link-protection.mdx
+++ b/src/content/docs/workers/examples/hot-link-protection.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Block other websites from linking to your content. This is useful for
   protecting images.
 tags:
diff --git a/src/content/docs/workers/examples/modify-request-property.mdx b/src/content/docs/workers/examples/modify-request-property.mdx
index fe5199d30781dab..7b0dff4cea7b789 100644
--- a/src/content/docs/workers/examples/modify-request-property.mdx
+++ b/src/content/docs/workers/examples/modify-request-property.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Create a modified request with edited properties based off of an
   incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/modify-response.mdx b/src/content/docs/workers/examples/modify-response.mdx
index 75b8731aae95371..6638180c480b268 100644
--- a/src/content/docs/workers/examples/modify-response.mdx
+++ b/src/content/docs/workers/examples/modify-response.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Fetch and modify response properties which are immutable by creating a
   copy first.
 tags:
diff --git a/src/content/docs/workers/examples/multiple-cron-triggers.mdx b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
index 70ffa53d857fde0..52d717075365808 100644
--- a/src/content/docs/workers/examples/multiple-cron-triggers.mdx
+++ b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set multiple Cron Triggers on three different schedules.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/openai-sdk-streaming.mdx b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
index 4a56649266440a9..20dc1d448fe2b7e 100644
--- a/src/content/docs/workers/examples/openai-sdk-streaming.mdx
+++ b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the OpenAI v4 SDK to stream responses from OpenAI.
 tags:
   - AI
diff --git a/src/content/docs/workers/examples/post-json.mdx b/src/content/docs/workers/examples/post-json.mdx
index c14f7e3a5c83c6a..6b01ab31537684d 100644
--- a/src/content/docs/workers/examples/post-json.mdx
+++ b/src/content/docs/workers/examples/post-json.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send a POST request with JSON data. Use to share data with external servers.
 tags:
   - JSON
diff --git a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
index 0204a2732ca6e07..c18930609c886b2 100644
--- a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
+++ b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Protect against timing attacks by safely comparing values using
   `timingSafeEqual`.
 tags:
diff --git a/src/content/docs/workers/examples/read-post.mdx b/src/content/docs/workers/examples/read-post.mdx
index 6ec581eff46a60c..c805138d150cb88 100644
--- a/src/content/docs/workers/examples/read-post.mdx
+++ b/src/content/docs/workers/examples/read-post.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Serve an HTML form, then read POST requests. Use also to read JSON or
   POST data from an incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/return-html.mdx b/src/content/docs/workers/examples/return-html.mdx
index 065b623759cdcc6..3cd587b30a97fae 100644
--- a/src/content/docs/workers/examples/return-html.mdx
+++ b/src/content/docs/workers/examples/return-html.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Deliver an HTML page from an HTML string directly inside the Worker script.
 demo: https://returning-html.workers-sites-examples.workers.dev
 tags:
diff --git a/src/content/docs/workers/examples/rewrite-links.mdx b/src/content/docs/workers/examples/rewrite-links.mdx
index e20265b28ed4a5b..cd10efbb5239087 100644
--- a/src/content/docs/workers/examples/rewrite-links.mdx
+++ b/src/content/docs/workers/examples/rewrite-links.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Rewrite URL links in HTML using the HTMLRewriter. This is useful for
   JAMstack websites.
 tags:
diff --git a/src/content/docs/workers/examples/signing-requests.mdx b/src/content/docs/workers/examples/signing-requests.mdx
index 7d98b2922d35a5f..f1e685251d8fc52 100644
--- a/src/content/docs/workers/examples/signing-requests.mdx
+++ b/src/content/docs/workers/examples/signing-requests.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Verify a signed request using the HMAC and SHA-256 algorithms or return a 403.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
index 6f97419c267b833..d20ca8a4a5aa54b 100644
--- a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
+++ b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Inject [Turnstile](/turnstile/) implicitly into HTML elements using the
   HTMLRewriter runtime API.
 tags:
diff --git a/src/content/docs/workers/examples/websockets.mdx b/src/content/docs/workers/examples/websockets.mdx
index 84e5dc0f892523c..cd919a2ecbdd2e4 100644
--- a/src/content/docs/workers/examples/websockets.mdx
+++ b/src/content/docs/workers/examples/websockets.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the WebSockets API to communicate in real time with your Cloudflare Workers.
 tags:
   - WebSockets
@@ -81,9 +82,9 @@ async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<worker::Res
 ```
 
 </TabItem> </Tabs>
-
 After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
+
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
@@ -135,6 +136,7 @@ The `WebSocketPair` constructor returns an Object, with the `0` and `1` keys eac
 
 In order to begin communicating with the `client` WebSocket in your Worker, call `accept` on the `server` WebSocket. This will tell the Workers runtime that it should listen for WebSocket data and keep the connection open with your `client` WebSocket:
 
+
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
diff --git a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
index bf7151b9c2d494c..8311463a2303071 100644
--- a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
+++ b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
@@ -10,14 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers with AI & agent
-	frameworks.
+Create full-stack applications deployed to Cloudflare Workers with AI & agent frameworks.
 </Description>
 
-<DirectoryListing
-	folder="workers/framework-guides/ai-and-agents"
-	maxDepth={2}
-/>
+<DirectoryListing folder="workers/framework-guides/ai-and-agents" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/apis/index.mdx b/src/content/docs/workers/framework-guides/apis/index.mdx
index e3e0997d8023893..7c65dfc89d5ab12 100644
--- a/src/content/docs/workers/framework-guides/apis/index.mdx
+++ b/src/content/docs/workers/framework-guides/apis/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers using APIs.
+Create full-stack applications deployed to Cloudflare Workers using APIs.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/index.mdx b/src/content/docs/workers/framework-guides/index.mdx
index 7c7d795d9e3aa13..e7fd39e00a6aecf 100644
--- a/src/content/docs/workers/framework-guides/index.mdx
+++ b/src/content/docs/workers/framework-guides/index.mdx
@@ -11,10 +11,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers.
+Create full-stack applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides" maxDepth={4} />
+<DirectoryListing folder="workers/framework-guides" maxDepth={4}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
index f7fc7a59d1511ee..03a98d1fc26641a 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
@@ -5,4 +5,4 @@ pcx_content_type: navigation
 external_link: https://docs.expo.dev/eas/hosting/reference/worker-runtime/
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
index be6cede9f5c8287..6cc8183f77ec8c3 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack mobile applications deployed to Cloudflare Workers.
+Create full-stack mobile applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/astro.mdx b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
index b90f2936598dcff..a1e4aaf3e9ea768 100644
--- a/src/content/docs/workers/framework-guides/web-apps/astro.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
@@ -87,27 +87,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Astro"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: "dist/_worker.js/index.js",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: ./dist, binding: ASSETS",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: "dist/_worker.js/index.js" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: ./dist, binding: ASSETS" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{
-			label: "adapter",
-			file: "astro.config.mjs",
-			value: "@astrojs/cloudflare",
-		},
+		{ label: "adapter", file: "astro.config.mjs", value: "@astrojs/cloudflare" },
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/index.mdx b/src/content/docs/workers/framework-guides/web-apps/index.mdx
index 87009d6003a290e..cb372caec51f847 100644
--- a/src/content/docs/workers/framework-guides/web-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack web applications deployed to Cloudflare Workers.
+Create full-stack web applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
index 0cd619c91b471d7..db924f15079e094 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
@@ -24,21 +24,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Analog"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
index c12d9db29798dfc..8dbf8a2eccef565 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
@@ -29,11 +29,7 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Angular"
 	configs={[
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/browser",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/browser" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
index b098122622c408a..6f0ab43afa2d870 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
@@ -75,6 +75,7 @@ Docusaurus is designed to be easy to use and customizable, making it a popular c
 
 If your Docusaurus project is entirely pre-rendered (which it usually is), follow these steps:
 
+
 <Steps>
 1.  **Add a Wrangler configuration file.**
 
@@ -115,3 +116,4 @@ If your Docusaurus project is entirely pre-rendered (which it usually is), follo
 Bindings are a way to connect your Docusaurus project to other Cloudflare services, enabling you to store and retrieve data within your application.
 
 <Render file="frameworks-bindings" product="workers" />
+
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
index 8373da96cbbdb96..5b69a489c1fe3d0 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
@@ -33,6 +33,8 @@ import {
 
 [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create/deploy-to-workers&repository=https://github.com/cloudflare/templates/tree/main/vite-react-template)
 
+
+
 ## What is Hono?
 
 [Hono](https://hono.dev/) is an ultra-fast, lightweight framework for building web applications, and works fantastically with Cloudflare Workers.
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
index 2c8eb7ea43bc8ed..eb6f1cd2cdff605 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
@@ -8,4 +8,4 @@ sidebar:
     hideIndex: true
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
index bf3f6b53620a121..775117671401c50 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
@@ -29,21 +29,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Nuxt"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "preset", file: "nuxt.config.ts", value: "cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
index 0b4849166b7c4fc..520223f8048b1ce 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
@@ -33,21 +33,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Solid Start"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
index 6d8e6bedc97a74c..11a06ef6dfe2634 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
@@ -30,16 +30,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Waku"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/worker.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -97,4 +89,4 @@ You can serve static assets in your Waku application by adding them to the `./pu
 
 During the build process, Waku copies `.js`, `.css`, `.html`, and `.txt` files from this directory into the final assets output. `.txt` files are used for storing data used by Server Components that are rendered at build time.
 
-<Render file="workers-assets-routing-summary" product="workers" />
+<Render file="workers-assets-routing-summary" product="workers" />
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
index 59f1211f42978e5..7218158dad2f5ea 100644
--- a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
@@ -29,6 +29,8 @@ import {
 
 This is a simple getting started guide. For detailed documentation on how to use the Cloudflare OpenNext adapter, visit the [OpenNext website](https://opennext.js.org/cloudflare).
 
+
+
 ## What is Next.js?
 
 [Next.js](https://nextjs.org/) is a [React](https://react.dev/) framework for building full stack applications.
@@ -41,23 +43,23 @@ You can deploy your Next.js app to Cloudflare Workers using the OpenNext adapter
 
 Most Next.js features are supported by the Cloudflare OpenNext adapter:
 
-| Feature                               | Cloudflare adapter   | Notes                                                       |
-| ------------------------------------- | -------------------- | ----------------------------------------------------------- |
-| App Router                            | 🟢 supported         |                                                             |
-| Pages Router                          | 🟢 supported         |                                                             |
-| Route Handlers                        | 🟢 supported         |                                                             |
-| React Server Components               | 🟢 supported         |                                                             |
-| Static Site Generation (SSG)          | 🟢 supported         |                                                             |
-| Server-Side Rendering (SSR)           | 🟢 supported         |                                                             |
-| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                             |
-| Server Actions                        | 🟢 supported         |                                                             |
-| Response streaming                    | 🟢 supported         |                                                             |
-| asynchronous work with `next/after`   | 🟢 supported         |                                                             |
-| Middleware                            | 🟢 supported         |                                                             |
-| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/)                 |
-| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                              |
-| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js               |
-| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported |
+| Feature                               | Cloudflare adapter   | Notes                                                                        |
+| ------------------------------------- | -------------------- | ---------------------------------------------------------------------------- |
+| App Router                            | 🟢 supported         |                                                                              |
+| Pages Router                          | 🟢 supported         |                                                                              |
+| Route Handlers                        | 🟢 supported         |                                                                              |
+| React Server Components               | 🟢 supported         |                                                                              |
+| Static Site Generation (SSG)          | 🟢 supported         |                                                                              |
+| Server-Side Rendering (SSR)           | 🟢 supported         |                                                                              |
+| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                                              |
+| Server Actions                        | 🟢 supported         |                                                                              |
+| Response streaming                    | 🟢 supported         |                                                                              |
+| asynchronous work with `next/after`   | 🟢 supported         |                                                                              |
+| Middleware                            | 🟢 supported         |                                                                              |
+| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/) |
+| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                                               |
+| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js                                |
+| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported                  |
 
 ## Deploy a new Next.js project on Workers
 
@@ -131,16 +133,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Next.js"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: ".open-next/worker.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .open-next/assets",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .open-next/assets" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "adapter", file: "package.json", value: "@opennextjs/cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
index a69d19964c7156c..226dd6d9fc4c19e 100644
--- a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
@@ -96,4 +96,4 @@ RedwoodSDK is a framework for building server-side web applications on Cloudflar
 
 	The first time you run the command it might fail and ask you to create a workers.dev subdomain. Go to the dashboard and open the Workers menu. Opening the Workers landing page for the first time will create a workers.dev subdomain automatically.
 
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
index 0c4e1f8d44d8645..16233bdaac9a5ea 100644
--- a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
@@ -31,27 +31,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="SvelteKit"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".svelte-kit/cloudflare/_worker.js",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .svelte-kit/cloudflare",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".svelte-kit/cloudflare/_worker.js" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .svelte-kit/cloudflare" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{
-			label: "adapter",
-			file: "svelte.config.js",
-			value: "@sveltejs/adapter-cloudflare",
-		},
+		{ label: "adapter", file: "svelte.config.js", value: "@sveltejs/adapter-cloudflare" },
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vike.mdx b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
index 6218d56b5d4a81a..27dd268608448ee 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vike.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
@@ -10,12 +10,13 @@ products:
 ---
 
 import { AutoconfigDiagram, Steps, PackageManagers } from "~/components";
-import { Tabs, TabItem } from "@astrojs/starlight/components";
+import { Tabs, TabItem } from '@astrojs/starlight/components';
 
 You can deploy your [Vike](https://vike.dev) app to Cloudflare using the Vike extension [`vike-photon`](https://vike.dev/vike-photon).
 
 All app types (SSR/SPA/SSG) are supported.
 
+
 :::tip[Already have a Vike project?]
 Run `wrangler deploy` in a project without a Wrangler configuration file and Wrangler will automatically detect Vike, generate the necessary configuration, and deploy your project.
 
@@ -28,16 +29,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Vike"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/server/index.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/client",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/client" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -50,6 +43,7 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 
 Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `vike-photon` with `@photonjs/cloudflare`.
 
+
 ## Add to existing app
 
 <Steps>
@@ -98,29 +92,31 @@ Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `v
 To access Cloudflare APIs (such as [D1](/d1/) and [KV](/kv/)), use [bindings](/workers/runtime-apis/bindings/) which are available via the `env` object [imported from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global).
 
 ```ts
-import { env } from "cloudflare:workers";
+import { env } from 'cloudflare:workers'
 // Key-value store
-env.KV.get("my-key");
+env.KV.get('my-key')
 // Environment variable
-env.LOG_LEVEL;
+env.LOG_LEVEL
 // ...
 ```
 
 > Example of using Cloudflare D1:
->
 > <PackageManagers
 > 	type="create"
 > 	pkg="vike@latest"
 > 	args="--react --hono --drizzle --cloudflare"
 > />
-> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an
-> ORM.
+> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an ORM.
 
 ## TypeScript
 
 If you use TypeScript, run [`wrangler types`](/workers/wrangler/commands/general/#types) whenever you change your Cloudflare configuration to update the `worker-configuration.d.ts` file.
 
-<PackageManagers type="exec" pkg="wrangler" args="types" />
+<PackageManagers
+	type="exec"
+	pkg="wrangler"
+	args="types"
+/>
 
 Then commit:
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vue.mdx b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
index 155e8df3c77be19..e3f18d090e9e901 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vue.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
@@ -34,9 +34,9 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
 	args="my-vue-app --framework=vue"
 />
 
-		 <Details header="How is this project set up?">
-    			Below is a simplified file tree of the project.
-    			<FileTree>
+    		 <Details header="How is this project set up?">
+        			Below is a simplified file tree of the project.
+        			<FileTree>
     						- my-vue-app
     							- src/
     									- App.vue
@@ -47,17 +47,17 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
     							- wrangler.jsonc
         			</FileTree>
 
-    			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
-    			In this file:
-    					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
-    					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
-    					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
+        			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
+        			In this file:
+        					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
+        					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
+        					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
+    						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
-						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
-    		</Details>
+    						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
+    						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
+        		</Details>
 
 ## 2. Develop locally with the [Cloudflare Vite plugin](/workers/vite-plugin/)
 
diff --git a/src/content/docs/workers/get-started/dashboard.mdx b/src/content/docs/workers/get-started/dashboard.mdx
index 93f5ddc844d62d9..927871405d844f0 100644
--- a/src/content/docs/workers/get-started/dashboard.mdx
+++ b/src/content/docs/workers/get-started/dashboard.mdx
@@ -29,15 +29,14 @@ To get started with a new Workers application:
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
-2. Select **Create application**. From here, you can:
-   - Select from the gallery of production-ready templates
-   - Import an existing Git repository on your own account
-   - Let Cloudflare clone and bootstrap a public repository containing a Workers application.
+3. Select **Create application**. From here, you can:
+    * Select from the gallery of production-ready templates
+    * Import an existing Git repository on your own account
+    * Let Cloudflare clone and bootstrap a public repository containing a Workers application.
 3. Once you have connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and select **Deploy**.
 4. Cloudflare will kick off a new build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain.
 
 ## Continue development
-
 Applications started in the dashboard are set up with Git to help kickstart your development workflow. To continue developing on your repository, you can run:
 
 ```bash
@@ -61,8 +60,8 @@ git commit -m "your message"
 git push origin main
 ```
 
-To do more:
 
+To do more:
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.
diff --git a/src/content/docs/workers/get-started/quickstarts.mdx b/src/content/docs/workers/get-started/quickstarts.mdx
index 5b4c0d7dd74919f..c4c9aaa383a02c3 100644
--- a/src/content/docs/workers/get-started/quickstarts.mdx
+++ b/src/content/docs/workers/get-started/quickstarts.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: get-started
 title: Templates
 sidebar:
diff --git a/src/content/docs/workers/languages/javascript/index.mdx b/src/content/docs/workers/languages/javascript/index.mdx
index ad25a7a59321ff9..a2697d4edad3d26 100644
--- a/src/content/docs/workers/languages/javascript/index.mdx
+++ b/src/content/docs/workers/languages/javascript/index.mdx
@@ -8,15 +8,16 @@ products:
   - workers
 ---
 
+
 The Workers platform is designed to be [JavaScript standards compliant](https://ecma-international.org/publications-and-standards/standards/ecma-262/) and web-interoperable, and supports JavaScript standards, as defined by [TC39](https://tc39.es/) (ECMAScript). Wherever possible, it uses web platform APIs, so that code can be reused across client and server, as well as across [WinterCG](https://wintercg.org/) JavaScript runtimes.
 
 Refer to [Runtime APIs](/workers/runtime-apis/) for more information on specific JavaScript APIs available in Workers.
 
 ### Resources
 
-- [Getting Started](/workers/get-started/guide/)
-- [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
-- [TypeScript type definitions](https://github.com/cloudflare/workers-types)
-- [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
-- [Tutorials](/workers/tutorials/)
-- [Examples](/workers/examples/?languages=JavaScript)
+* [Getting Started](/workers/get-started/guide/)
+* [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
+* [TypeScript type definitions](https://github.com/cloudflare/workers-types)
+* [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
+* [Tutorials](/workers/tutorials/)
+* [Examples](/workers/examples/?languages=JavaScript)
diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx
index 57b1c75a4621975..d45ef218a482019 100644
--- a/src/content/docs/workers/observability/errors.mdx
+++ b/src/content/docs/workers/observability/errors.mdx
@@ -15,21 +15,22 @@ Review Workers errors and exceptions.
 
 When a Worker running in production has an error that prevents it from returning a response, the client will receive an error page with an error code, defined as follows:
 
-| Error code | Meaning                                                                                                                                                                                                                                                             |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `1101`     | Worker threw a JavaScript exception.                                                                                                                                                                                                                                |
-| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                                                                                                                                               |
-| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                                                                                                                                             |
-| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                                                                                                                                               |
-| `1021`     | Worker has requested a host it cannot access.                                                                                                                                                                                                                       |
-| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                                                                                                                                           |
-| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                                                                                                                                                   |
-| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                                                                                                                                          |
+| Error code | Meaning                                                                                                                                         |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `1101`     | Worker threw a JavaScript exception.                                                                                                            |
+| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                           |
+| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                         |
+| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                           |
+| `1021`     | Worker has requested a host it cannot access.                                                                                                   |
+| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                       |
+| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                               |
+| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                       |
 | `1042`     | Worker tried to fetch from another Worker on the same zone, which is only [supported](/workers/runtime-apis/fetch/) when the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) is used. |
-| `10162`    | Module has an unsupported Content-Type.                                                                                                                                                                                                                             |
+| `10162`    | Module has an unsupported Content-Type.                                                                                                         |
 
 Other `11xx` errors generally indicate a problem with the Workers runtime itself. Refer to the [status page](https://www.cloudflarestatus.com) if you are experiencing an error.
 
+
 ### Loop limit
 
 A Worker cannot call itself or another Worker more than 16 times. In order to prevent infinite loops between Workers, the [`CF-EW-Via`](/fundamentals/reference/http-headers/#cf-ew-via) header's value is an integer that indicates how many invocations are left. Every time a Worker is invoked, the integer will decrement by 1. If the count reaches zero, a [`1019`](#error-pages-generated-by-workers) error is returned.
@@ -190,23 +191,23 @@ If you need to share state across requests, consider using [Durable Objects](/du
 
 These errors occur when a Worker is uploaded or modified.
 
-| Error code | Meaning                                                                                                                     |
-| ---------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `10006`    | Could not parse your Worker's code.                                                                                         |
-| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                   |
-| `10015`    | Account is not entitled to use Workers.                                                                                     |
-| `10016`    | Invalid Worker name.                                                                                                        |
-| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.         |
-| `10026`    | Could not parse request body.                                                                                               |
-| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size).                               |
-| `10035`    | Multiple attempts to modify a resource at the same time                                                                     |
-| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                       |
-| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                    |
-| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                 |
-| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables). |
-| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                       |
-| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                    |
-| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.          |
+| Error code | Meaning                                                                                                                         |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `10006`    | Could not parse your Worker's code.                                                                                             |
+| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                       |
+| `10015`    | Account is not entitled to use Workers.                                                                                         |
+| `10016`    | Invalid Worker name.                                                                                                            |
+| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.             |
+| `10026`    | Could not parse request body.                                                                                                   |
+| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size). |
+| `10035`    | Multiple attempts to modify a resource at the same time                                                                         |
+| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                           |
+| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                        |
+| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                     |
+| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables).     |
+| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                           |
+| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                        |
+| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.              |
 
 ### Validation Errors (10021)
 
@@ -235,7 +236,6 @@ Runtime errors will occur within the runtime, do not throw up an error page, and
 ## Identify errors: Workers Metrics
 
 To review whether your application is experiencing any downtime or returning any errors:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
index 105fea21b7e83dc..586b51c9eed17af 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
@@ -8,11 +8,10 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Axiom is a serverless log analytics platform that helps you store, search, and analyze massive amounts of data. By exporting your Cloudflare Workers application telemetry to Axiom, you can:
-
-- Store and query logs and traces at scale
+- Store and query logs and traces at scale 
 - Create dashboards and alerts to monitor your Workers
 
 ![Trace view with timing information displayed on a timeline](~/assets/images/workers-observability/axiom-example.png)
@@ -30,7 +29,6 @@ Before you begin, ensure you have:
 ## Step 1: Create a dataset
 
 If you don't already have a dataset to send data to:
-
 1. Log in to your [Axiom account](https://app.axiom.co/)
 2. Navigate to **Datasets** in the left sidebar
 3. Click **New Dataset**
@@ -58,7 +56,6 @@ Now you'll create destinations in the Cloudflare dashboard that point to Axiom.
 ### Axiom OTLP endpoints
 
 Axiom provides separate OTLP endpoints for traces and logs:
-
 - **Traces**: `https://api.axiom.co/v1/traces`
 - **Logs**: `https://api.axiom.co/v1/logs`
 
@@ -70,13 +67,13 @@ Axiom provides separate OTLP endpoints for traces and logs:
    - **Destination Name**: `axiom-traces` (or any descriptive name)
    - **Destination Type**: Select **Traces**
    - **OTLP Endpoint**: `https://api.axiom.co/v1/traces` (or `/v1/logs`)
-   - **Custom Headers**: Add two required headers:
-     - Authentication header
-       - Header name: `Authorization`
-       - Header value: `Bearer <your-api-token>`
-     - Dataset header:
+   - **Custom Headers**: Add two required headers: 
+     -  Authentication header 
+        - Header name: `Authorization`
+        - Header value: `Bearer <your-api-token>` 
+     - Dataset header: 
        - Header name: `X-Axiom-Dataset`
-       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`)
+       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`) 
 4. Click **Save**
 
 ## Step 3: Configure your Worker
@@ -107,5 +104,6 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Axiom.
+It may take a few minutes after deployment for data to appear in Axiom. 
 :::
+
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
index 996992e42bfb4d6..8592f3ba188c813 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
@@ -7,11 +7,9 @@ sidebar:
 products:
   - workers
 ---
-
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Grafana Cloud is a fully managed observability platform that provides visualization, alerting, and analytics for your telemetry data. By exporting your Cloudflare Workers telemetry to Grafana Cloud, you can:
-
 - Visualize distributed traces in **Grafana Tempo** to understand request flows and performance bottlenecks
 - Query and analyze logs in **Grafana Loki** alongside your traces
 
@@ -32,25 +30,24 @@ Before you begin, ensure you have:
 2. From your organization's home page, navigate to **Connections** → **Add new connection**
 3. Search for "OpenTelemetry" and select **OpenTelemetry (OTLP)**
 4. Select **Quickstart** then select **JavaScript**
-5. Click **Create a new token**
-6. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
-7. Click on **Close** without copying the token
-8. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
+6. Click **Create a new token**
+7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
+8. Click on **Close** without copying the token
+9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
 
-## Step 2: Set up destination
 
+## Step 2: Set up destination 
 1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
 2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
-3. From Grafana, copy your Otel endpoint, auth header, and auth value
-
-- Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs)
-- Your custom header should include:
-  - Your auth header name `Authorization`
-  - Your auth header value `Basic MTMxxx...`
+3. From Grafana, copy your Otel endpoint, auth header, and auth value 
+  * Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs) 
+  * Your custom header should include: 
+      * Your auth header name `Authorization`
+      * Your auth header value `Basic MTMxxx...`
 
 ## Step 3: Configure your Worker
 
-With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
+With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export. 
 
 <WranglerConfig>
 
@@ -73,8 +70,8 @@ With your destination created in the Cloudflare dashboard, update your Worker's
 
 </WranglerConfig>
 
-After updating your configuration, deploy your Worker for the changes to take effect.
+After updating your configuration, deploy your Worker for the changes to take effect. 
 
 :::note
-It may take a few minutes after deployment for data to appear in Grafana Cloud.
+It may take a few minutes after deployment for data to appear in Grafana Cloud. 
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
index 9b00d57e583249b..847f103352c625f 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
@@ -8,10 +8,9 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Honeycomb is an observability platform built for high-cardinality data that helps you understand and debug your applications. By exporting your Cloudflare Workers application telemetry to Honeycomb, you can:
-
 - Visualize traces to understand request flows and identify performance bottlenecks
 - Query and analyze logs with unlimited dimensionality across any attribute
 - Create custom queries and dashboards to monitor your Workers
@@ -45,12 +44,11 @@ The API key will look something like: `hcaik_01hq...`
 
 ## Step 2: Configure Cloudflare destinations
 
-Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb.
+Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb. 
 
 ### Honeycomb OTLP endpoints
 
 Honeycomb provides separate OTLP endpoints for traces and logs:
-
 - **Traces**: `https://api.honeycomb.io/v1/traces`
 - **Logs**: `https://api.honeycomb.io/v1/logs`
 
@@ -109,5 +107,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Honeycomb.
+It may take a few minutes after deployment for data to appear in Honeycomb. 
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
index fbafabca9cdfc0f..fd45dd3b86981fd 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
@@ -25,18 +25,18 @@ You can export the following types of telemetry data:
 
 Below are common OTLP endpoint formats for popular observability providers. Refer to your provider's documentation for specific details and authentication requirements.
 
-| Provider                                                                                          | Traces Endpoint                                              | Logs Endpoint                                                |
-| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)                   | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
-| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/)           | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
-| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)                        | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
-| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                           | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
-| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)                         | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
-| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)                       | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
-| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)                        | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
-| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/)  | `https://otlp.nr-data.net/v1/traces`                         | `https://otlp.nr-data.net/v1/logs`                           |
-| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp`          | N/A                                                          |
-| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp)                          | `http://splunk.internal:4318/v1/traces`                      | `http://splunk.internal:4318/v1/logs`                        |
+| Provider                                                                                | Traces Endpoint                                              | Logs Endpoint                                                |
+| --------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)         | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
+| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
+| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)              | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
+| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                 | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
+| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)               | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
+| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)             | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
+| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)              | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
+| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/) | `https://otlp.nr-data.net/v1/traces` | `https://otlp.nr-data.net/v1/logs` |
+| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp` | N/A |
+| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp) | `http://splunk.internal:4318/v1/traces` | `http://splunk.internal:4318/v1/logs` |
 
 :::note[Authentication]
 Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.
@@ -109,11 +109,11 @@ After creating a destination, you can monitor its health and delivery status in
 
 ### Status indicators
 
-| Status                  | Description                                                             | Troubleshooting                                                                                                |
-| ----------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
-| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                                |
+| Status                  | Description                                                             | Troubleshooting                                                                                               |
+| ----------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                               |
 | **Never run**           | No data has been delivered to this destination.                         | •Check if your Worker is receiving traffic <br /> • Review sampling rates (low rates generate less data)<br /> |
-| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                      |
+| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                     |
 
 ## Limits and pricing
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
index 69002849ba8e0f1..0f42b67c6bb7168 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 PostHog is a product analytics platform that helps you understand user behavior and debug issues. By exporting your Cloudflare Workers application telemetry to PostHog, you can:
 
@@ -41,10 +41,10 @@ The API key should look something like: `phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 PostHog has different endpoints depending on your data region:
 
-| Region           | Logs Endpoint                        |
-| ---------------- | ------------------------------------ |
+| Region | Logs Endpoint |
+| ------ | ------------- |
 | **US** (default) | `https://us.i.posthog.com/i/v1/logs` |
-| **EU**           | `https://eu.i.posthog.com/i/v1/logs` |
+| **EU** | `https://eu.i.posthog.com/i/v1/logs` |
 
 You can find your region in your PostHog project settings or by checking the URL when logged into PostHog (either `us.posthog.com` or `eu.posthog.com`).
 
@@ -104,7 +104,6 @@ Once your Worker is deployed and receiving traffic:
 3. Your Worker logs will appear with severity levels, timestamps, and attributes
 
 You can filter logs by:
-
 - **Severity level** (trace, debug, info, warn, error, fatal)
 - **Time range**
 - **Custom attributes** added to your log entries
@@ -116,25 +115,25 @@ You can add custom attributes to your logs using standard `console` methods with
 
 ```javascript
 export default {
-	async fetch(request, env) {
-		// Basic logging
-		console.log("Processing request");
-
-		// Logs with additional context
-		console.info("User action", {
-			userId: "user_123",
-			action: "api_call",
-			path: new URL(request.url).pathname,
-		});
-
-		// Error logging with details
-		console.error("Request failed", {
-			error: "Connection timeout",
-			retryCount: 3,
-		});
-
-		return new Response("OK");
-	},
+  async fetch(request, env) {
+    // Basic logging
+    console.log("Processing request");
+
+    // Logs with additional context
+    console.info("User action", {
+      userId: "user_123",
+      action: "api_call",
+      path: new URL(request.url).pathname
+    });
+
+    // Error logging with details
+    console.error("Request failed", {
+      error: "Connection timeout",
+      retryCount: 3
+    });
+
+    return new Response("OK");
+  }
 };
 ```
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
index 1c602ea7225b551..57d0992698f5e67 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
@@ -8,10 +8,9 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Sentry is a software monitoring tool that helps developers identify and debug performance issues and errors. From end-to-end distributed tracing to performance monitoring, Sentry provides code-level observability that makes it easy to diagnose issues and learn continuously about your application code health across systems and services. By exporting your Cloudflare Workers application telemetry to Sentry, you can:
-
 - Query logs and traces in Sentry
 - Create custom alerts and dashboards to monitor your Workers
 
@@ -38,7 +37,6 @@ If you don't already have a Sentry project to send data to, you'll need to creat
 ## Step 2: Get your Sentry OTLP endpoints
 
 Sentry provides separate OTLP endpoints for traces and logs which you can use to send your telemetry data to Sentry.
-
 - **Traces**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`
 - **Logs**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`
 
@@ -59,24 +57,23 @@ To set up a destination in the Cloudflare dashboard, navigate to your Cloudflare
 ### Traces Destination
 
 To configure your traces destination, click **Add destination** and configure the following:
-
-- **Destination Name**: `sentry-traces` (or any descriptive name)
-- **Destination Type**: Select **Traces**
-- **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
-- **Custom Headers**: Add the Sentry authentication header:
-  - Header name: `x-sentry-auth`
-  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
+   - **Destination Name**: `sentry-traces` (or any descriptive name)
+   - **Destination Type**: Select **Traces**
+   - **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
+   - **Custom Headers**: Add the Sentry authentication header:
+     - Header name: `x-sentry-auth`
+     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ### Logs destination
 
 To configure your logs destination, click **Add destination** and configure the following:
+   - **Destination Name**: `sentry-logs` (or any descriptive name)
+   - **Destination Type**: Select **Logs**
+   - **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
+   - **Custom Headers**: Add the Sentry authentication header:
+     - Header name: `x-sentry-auth`
+     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
-- **Destination Name**: `sentry-logs` (or any descriptive name)
-- **Destination Type**: Select **Logs**
-- **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
-- **Custom Headers**: Add the Sentry authentication header:
-  - Header name: `x-sentry-auth`
-  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ## Step 4: Configure your Worker
 
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 2b21d8e285a2a6b..72b1c12297f3d02 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -17,8 +17,10 @@ import { WranglerConfig, DashButton } from "~/components";
 
 :::caution
 
+
 Workers Trace Events Logpush is not available for zones on the [Cloudflare China Network](/china-network/).
 
+
 :::
 
 ## Verify your Logpush access
@@ -28,7 +30,6 @@ Minimum required Wrangler version: 2.2.0. Check your version by running `wrangle
 :::
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
-
 1. In the Cloudflare dashboard, go to the **Members** page.
 
    <DashButton url="/?to=/:account/members" />
@@ -42,7 +43,6 @@ Alternatively, create a new [API token](/fundamentals/api/get-started/create-tok
 ### Via the Cloudflare dashboard
 
 To create a Logpush job in the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Logpush** page.
 
    <DashButton url="/?to=/:account/logs" />
@@ -117,7 +117,6 @@ curl --request PUT \
 ### Dashboard
 
 To enable Logpush logging via the dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -148,30 +147,30 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-	"Exceptions": [
-		{
-			"Name": "SampleError",
-			"Message": "something went wrong",
-			"TimestampMs": 0
-		},
-		{
-			"Name": "AuthError",
-			"Message": "unable to process request authentication from client",
-			"TimestampMs": 1
-		}
-	],
-	"Logs": [
-		{
-			"Level": "log",
-			"Message": ["Hello "],
-			"TimestampMs": 0
-		},
-		{
-			"Level": "log",
-			"Message": ["World!"],
-			"TimestampMs": 0
-		}
-	]
+  "Exceptions": [
+    {
+      "Name": "SampleError",
+      "Message": "something went wrong",
+      "TimestampMs": 0
+    },
+    {
+      "Name": "AuthError",
+      "Message": "unable to process request authentication from client",
+      "TimestampMs": 1
+    },
+  ],
+  "Logs": [
+    {
+      "Level": "log",
+      "Message": ["Hello "],
+      "TimestampMs": 0
+    },
+    {
+      "Level": "log",
+      "Message": ["World!"],
+      "TimestampMs": 0
+    }
+  ]
 }
 ```
 
@@ -179,24 +178,24 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-	"Exceptions": [
-		{
-			"name": "SampleError",
-			"message": "something went wrong",
-			"TimestampMs": 0
-		},
-		{
-			"name": "AuthError",
-			"message": "unable to <<<Logpush: exception messages truncated>>>",
-			"TimestampMs": 1
-		}
-	],
-	"Logs": [
-		{
-			"Level": "log",
-			"Message": ["<<<Logpush: messages truncated>>>"],
-			"TimestampMs": 0
-		}
-	]
+  "Exceptions": [
+    {
+      "name": "SampleError",
+      "message": "something went wrong",
+      "TimestampMs": 0
+    },
+    {
+      "name": "AuthError",
+      "message": "unable to <<<Logpush: exception messages truncated>>>",
+      "TimestampMs": 1
+    },
+  ],
+  "Logs": [
+    {
+      "Level": "log",
+      "Message": ["<<<Logpush: messages truncated>>>"],
+      "TimestampMs": 0
+    }
+  ]
 }
 ```
diff --git a/src/content/docs/workers/observability/logs/real-time-logs.mdx b/src/content/docs/workers/observability/logs/real-time-logs.mdx
index 32ea43c6b2fedf7..65b48530222963a 100644
--- a/src/content/docs/workers/observability/logs/real-time-logs.mdx
+++ b/src/content/docs/workers/observability/logs/real-time-logs.mdx
@@ -25,7 +25,6 @@ Real-time logs are not available for zones on the [Cloudflare China Network](/ch
 ## View logs from the dashboard
 
 To view real-time logs associated with any deployed Worker using the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
index 88e00843194056a..1f162b257fc1d15 100644
--- a/src/content/docs/workers/observability/logs/workers-logs.mdx
+++ b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -53,7 +53,7 @@ You must add the observability setting for your Worker to write logs to Workers
 
 [Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for an environment named `staging`: 1. Add the following configuration below `[env.staging]`
 
-<WranglerConfig>
+    <WranglerConfig>
 
     ```jsonc
     {
@@ -70,8 +70,8 @@ You must add the observability setting for your Worker to write logs to Workers
 
     </WranglerConfig>
 
-2. Deploy your Worker with `npx wrangler deploy -e staging`
-3. Repeat step 1 and 2 for each environment.
+    2. Deploy your Worker with `npx wrangler deploy -e staging`
+    3. Repeat step 1 and 2 for each environment.
 
 ## View logs from the dashboard
 
diff --git a/src/content/docs/workers/observability/metrics-and-analytics.mdx b/src/content/docs/workers/observability/metrics-and-analytics.mdx
index 3f270c3f47959fb..ef28c321eb02f2a 100644
--- a/src/content/docs/workers/observability/metrics-and-analytics.mdx
+++ b/src/content/docs/workers/observability/metrics-and-analytics.mdx
@@ -54,7 +54,6 @@ Subrequests are requests triggered by calling `fetch` from within a Worker. A su
 ### Wall time per execution
 
 <GlossaryTooltip term="wall-clock time">Wall time</GlossaryTooltip> represents
-
 the elapsed time in milliseconds between the start of a Worker invocation, and
 when the Workers runtime determines that no more JavaScript needs to run.
 Specifically, wall time per execution chart measures the wall time that the
diff --git a/src/content/docs/workers/observability/source-maps.mdx b/src/content/docs/workers/observability/source-maps.mdx
index 20d213c75c986ae..2872e097f8f75a0 100644
--- a/src/content/docs/workers/observability/source-maps.mdx
+++ b/src/content/docs/workers/observability/source-maps.mdx
@@ -45,8 +45,10 @@ You can then view the stack trace when streaming [real-time logs](/workers/obser
 
 :::note
 
+
 The source map is retrieved after your Worker invocation completes — it's an asynchronous process that does not impact your Worker's CPU utilization or performance. Source maps are not accessible inside the Worker at runtime, if you `console.log()` the [stack property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/stack) within a Worker, you will not get a deobfuscated stack trace.
 
+
 :::
 
 When Cloudflare attempts to remap a stack trace to the Worker's source map, it does so line-by-line, remapping as much as possible. If a line of the stack trace cannot be remapped for any reason, Cloudflare will leave that line of the stack trace unchanged, and continue to the next line of the stack trace.
@@ -57,9 +59,10 @@ When Cloudflare attempts to remap a stack trace to the Worker's source map, it d
 Minimum required Wrangler version for source maps: 3.46.0. Check your version by running `wrangler --version`.
 :::
 
-| Description             | Limit         |
-| ----------------------- | ------------- |
-| Maximum Source Map Size | 15 MB gzipped |
+
+| Description                    | Limit         |
+| ------------------------------ | ------------- |
+| Maximum Source Map Size        | 15 MB gzipped |
 
 ## Example
 
@@ -85,6 +88,6 @@ With **source maps uploaded**: all methods reference the correct files and line
 
 ## Related resources
 
-- [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
-- [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
-- [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
+* [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
+* [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
+* [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
diff --git a/src/content/docs/workers/platform/betas.mdx b/src/content/docs/workers/platform/betas.mdx
index e151ed5f512fd42..99cebde932f6ce9 100644
--- a/src/content/docs/workers/platform/betas.mdx
+++ b/src/content/docs/workers/platform/betas.mdx
@@ -12,11 +12,11 @@ products:
 
 These are the current alphas and betas relevant to the Cloudflare Workers platform.
 
-- **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
-- Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
+* **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
+* Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
 
 | Product                                           | Private Beta | Public Beta | More Info                                                                   |
 | ------------------------------------------------- | ------------ | ----------- | --------------------------------------------------------------------------- |
-| Email Workers                                     |              | ✅          | [Docs](/email-routing/email-workers/)                                       |
-| Green Compute                                     |              | ✅          | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
-| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅          | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
+| Email Workers                                     |              | ✅           | [Docs](/email-routing/email-workers/)                                       |
+| Green Compute                                     |              | ✅           | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
+| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅           | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
diff --git a/src/content/docs/workers/platform/built-with-cloudflare.mdx b/src/content/docs/workers/platform/built-with-cloudflare.mdx
index 42aafcb95946784..b9ae5fb6977f6da 100644
--- a/src/content/docs/workers/platform/built-with-cloudflare.mdx
+++ b/src/content/docs/workers/platform/built-with-cloudflare.mdx
@@ -45,4 +45,4 @@ The Built with Cloudflare button is an SVG and can be embedded anywhere. Use the
 https://workers.cloudflare.com/built-with-cloudflare.svg
 ```
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/docs/workers/platform/changelog/historical-changelog.mdx b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
index 6ecdf4d3609fbdb..0b2cbd209519aa6 100644
--- a/src/content/docs/workers/platform/changelog/historical-changelog.mdx
+++ b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
@@ -16,374 +16,374 @@ This page tracks changes made to Cloudflare Workers before 2023. For a view of m
 
 ## 2022-12-16
 
-- Conditional `PUT` requests have been fixed in the R2 bindings API.
+* Conditional `PUT` requests have been fixed in the R2 bindings API.
 
 ## 2022-12-02
 
-- Queues no longer support calling `send()` with an undefined JavaScript value as the message.
+* Queues no longer support calling `send()` with an undefined JavaScript value as the message.
 
 ## 2022-11-30
 
-- The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
-- Extended the R2 binding API to include support for multipart uploads.
+* The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
+* Extended the R2 binding API to include support for multipart uploads.
 
 ## 2022-11-17
 
-- V8 update: 10.6 → 10.8
+* V8 update: 10.6 → 10.8
 
 ## 2022-11-02
 
-- Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
+* Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
 
 ## 2022-10-21
 
-- The alarm retry limit will no longer apply to errors that are our fault.
-- Compatibility dates have been added for multiple flags including the new streams implementation.
-- `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
+* The alarm retry limit will no longer apply to errors that are our fault.
+* Compatibility dates have been added for multiple flags including the new streams implementation.
+* `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
 
 ## 2022-10-10
 
-- Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
-- `console.log` now prints more information about certain objects, for example Promises.
-- The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
+* Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
+* `console.log` now prints more information about certain objects, for example Promises.
+* The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
 
 ## 2022-09-16
 
-- R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
-- Allow deleting multiple keys at once in R2 bindings.
-- Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
-- User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
-- Updated V8 to 10.6.
+* R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
+* Allow deleting multiple keys at once in R2 bindings.
+* Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
+* User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
+* Updated V8 to 10.6.
 
 ## 2022-08-12
 
-- A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
-- When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
-- Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
-- Validation errors during Worker upload for module scripts now include correct line and column numbers.
-- Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
+* A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
+* When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
+* Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
+* Validation errors during Worker upload for module scripts now include correct line and column numbers.
+* Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
 
 ## 2022-07-08
 
-- Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
+* Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
 
 ## 2022-06-24
 
-- `wrangler dev` in global network preview mode now supports scheduling alarms.
-- R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
-- Some Web Cryptography API error messages include more information now.
-- Updated V8 from 10.2 to 10.3.
+* `wrangler dev` in global network preview mode now supports scheduling alarms.
+* R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
+* Some Web Cryptography API error messages include more information now.
+* Updated V8 from 10.2 to 10.3.
 
 ## 2022-06-18
 
-- Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
-- The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
+* Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
+* The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
 
 ## 2022-06-09
 
-- No externally-visible changes.
+* No externally-visible changes.
 
 ## 2022-06-03
 
-- It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
-- Preview in Quick Edit now correctly uses the correct R2 bindings.
-- Updated V8 from 10.1 to 10.2.
+* It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
+* Preview in Quick Edit now correctly uses the correct R2 bindings.
+* Updated V8 from 10.1 to 10.2.
 
 ## 2022-05-26
 
-- The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
-- R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
+* The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
+* R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
 
 ## 2022-05-19
 
-- R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
-- ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
-- Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
-- R2: Better runtime support for additional ranges.
-- R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
+* R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
+* ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
+* Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
+* R2: Better runtime support for additional ranges.
+* R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
 
 ## 2022-05-12
 
-- Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
-- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-- Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
-- R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
-- R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
-- Added `startAfter` option to the `list()` method in the Durable Object storage API.
+* Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
+* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+* Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+* R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
+* R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
+* Added `startAfter` option to the `list()` method in the Durable Object storage API.
 
 ## 2022-05-05
 
-- `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
-- Fix generated types for Date.
-- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-- Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+* `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
+* Fix generated types for Date.
+* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+* Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
 
 ## 2022-04-29
 
-- Minor V8 update: 10.0 → 10.1.
-- R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
+* Minor V8 update: 10.0 → 10.1.
+* R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
 
 ## 2022-04-22
 
-- Major V8 update: 9.9 → 10.0.
+* Major V8 update: 9.9 → 10.0.
 
 ## 2022-04-14
 
-- Performance and stability improvements.
+* Performance and stability improvements.
 
 ## 2022-04-08
 
-- The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
-- R2 error responses now include better details.
+* The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
+* R2 error responses now include better details.
 
 ## 2022-03-24
 
-- A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
-- When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
-- The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
+* A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
+* When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
+* The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
 
 ## 2022-03-17
 
-- The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
-- When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
-- Fix R2 publish date rendering.
-- Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
-- When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
+* The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
+* When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
+* Fix R2 publish date rendering.
+* Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
+* When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
 
 ## 2022-03-11
 
-- Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
-- Implementations of `CompressionStream` and `DecompressionStream` are now available.
+* Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
+* Implementations of `CompressionStream` and `DecompressionStream` are now available.
 
 ## 2022-03-04
 
-- Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
-- With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
-- A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
-- The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
-- An implementation of `URLPattern` is now available.
+* Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
+* With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
+* A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
+* The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
+* An implementation of `URLPattern` is now available.
 
 ## 2022-02-25
 
-- The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
-- Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
-- Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
+* The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
+* Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
+* Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
 
 ## 2022-02-18
 
-- `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
+* `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
 
 ## 2022-02-11
 
-- WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
+* WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
 
 ## 2022-02-05
 
-- Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
-- `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
-- A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
+* Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
+* `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
+* A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
 
 ## 2022-01-28
 
-- No user-visible changes.
+* No user-visible changes.
 
 ## 2022-01-20
 
-- Updated V8: 9.7 → 9.8.
+* Updated V8: 9.7 → 9.8.
 
 ## 2022-01-17
 
-- `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
-- Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
+* `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
+* Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
 
 ## 2022-01-07
 
-- The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
+* The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
 
 ## 2021-12-22
 
-- Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
+* Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
 
 ## 2021-12-10
 
-- Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
-- `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
-- Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
-- `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
-- Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
-- Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
+* Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
+* `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
+* Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
+* `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
+* Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
+* Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
 
 ## 2021-12-02
 
-- The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
-- Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
+* The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
+* Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
 
 ## 2021-11-19
 
-- Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
-- Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
-- [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
+* Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
+* Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
+* [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
 
 ## 2021-11-12
 
-- The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
-- Unhandled rejection warnings will be printed to the inspector console.
+* The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
+* Unhandled rejection warnings will be printed to the inspector console.
 
 ## 2021-11-05
 
-- Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
-- Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams_byob_reader_detaches_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
+* Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
+* Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams\_byob\_reader\_detaches\_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
 
 ## 2021-10-21
 
-- Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
-- The `unhandledrejection` and `rejectionhandled` events are now supported.
-- The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
-- Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
-- The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
+* Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
+* The `unhandledrejection` and `rejectionhandled` events are now supported.
+* The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
+* Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
+* The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
 
 ## 2021-10-14
 
-- `request.signal` will always return an `AbortSignal`.
-- Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
-- Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
+* `request.signal` will always return an `AbortSignal`.
+* Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
+* Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
 
 ## 2021-09-24
 
-- The `AbortController` and `AbortSignal` objects are now available.
-- The Web Platform `queueMicrotask` API is now available.
-- It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
-- The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
-- Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
-- The `Event` object now supports most standard methods and properties.
-- V8 updated from 9.3 to 9.4.
+* The `AbortController` and `AbortSignal` objects are now available.
+* The Web Platform `queueMicrotask` API is now available.
+* It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
+* The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
+* Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
+* The `Event` object now supports most standard methods and properties.
+* V8 updated from 9.3 to 9.4.
 
 ## 2021-09-03
 
-- The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
-- Durable Objects are now scheduled more evenly around a colocation (colo).
+* The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
+* Durable Objects are now scheduled more evenly around a colocation (colo).
 
 ## 2021-08-05
 
-- No user-facing changes. Just bug fixes & internal maintenance.
+* No user-facing changes. Just bug fixes & internal maintenance.
 
 ## 2021-07-30
 
-- Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
-- Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
+* Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
+* Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
 
 ## 2021-07-23
 
-- Performance and stability improvements.
+* Performance and stability improvements.
 
 ## 2021-07-16
 
-- Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
-- Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
-- Durable Object constructors may now initiate I/O, such as `fetch()` calls.
-- Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
-- In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
+* Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
+* Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
+* Durable Object constructors may now initiate I/O, such as `fetch()` calls.
+* Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
+* In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
 
 ## 2021-07-13
 
-- The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
+* The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
 
 ## 2021-07-01
 
-- Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
-- Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
+* Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
+* Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
 
 ## 2021-06-27
 
-- WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
+* WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
 
 ## 2021-06-17
 
 Changes this week:
 
-- Updated V8 from 9.1 to 9.2.
-- `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
+* Updated V8 from 9.1 to 9.2.
+* `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
 
 ## 2021-06-11
 
 Changes this week:
 
-- Turn on V8 Sparkplug compiler.
-- Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
+* Turn on V8 Sparkplug compiler.
+* Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
 
 ## 2021-06-04
 
 Changes this week:
 
-- WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
-- `request.cf` is no longer missing when writing Workers using modules syntax.
+* WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
+* `request.cf` is no longer missing when writing Workers using modules syntax.
 
 ## 2021-05-14
 
 Changes this week:
 
-- Improve error messages coming from the WebCrypto API.
-- Updated V8: 9.0 → 9.1
+* Improve error messages coming from the WebCrypto API.
+* Updated V8: 9.0 → 9.1
 
 Changes in an earlier release:
 
-- WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
-- WebCrypto: Add support for RSA-OAEP
-- WebCrypto: HKDF implemented.
-- Fix recently-introduced backwards clock jumps in Durable Objects.
-- `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
+* WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
+* WebCrypto: Add support for RSA-OAEP
+* WebCrypto: HKDF implemented.
+* Fix recently-introduced backwards clock jumps in Durable Objects.
+* `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1\_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
 
 ## 2021-04-29
 
 Changes this week:
 
-- WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
-- The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
+* WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
+* The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
 
 ## 2021-04-23
 
 Changes this week:
 
-- In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
-- For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
-- When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
-- Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
-- When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
-- When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-- When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-- `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
+* In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
+* For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
+* When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
+* Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
+* When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
+* When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+* When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+* `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
 
 ## 2021-04-19
 
 Changes since the last post on 3/26:
 
-- Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
-- Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
-- Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
-- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-- Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
-- WebCrypto: Key derivation for ECDH.
-- WebCrypto: Support ECDH key generation & import.
-- WebCrypto: Support ECDSA key generation.
-- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-- Improved exception messages thrown by the WebCrypto API somewhat.
-- `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
-- `passThroughOnException` is now available under the ctx argument to module handlers
-- Reliability improvements for Durable Objects
-- Reliability improvements for Durable Objects persistent storage API
-- `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
+* Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
+* Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
+* Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
+* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+* Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
+* WebCrypto: Key derivation for ECDH.
+* WebCrypto: Support ECDH key generation & import.
+* WebCrypto: Support ECDSA key generation.
+* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+* Improved exception messages thrown by the WebCrypto API somewhat.
+* `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
+* `passThroughOnException` is now available under the ctx argument to module handlers
+* Reliability improvements for Durable Objects
+* Reliability improvements for Durable Objects persistent storage API
+* `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
 
 ## 2021-03-26
 
 Changes this week:
 
-- Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
+* Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
 
 ## 2021-03-11
 
 New this week:
 
-- When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
+* When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
 
 (It looks like no release notes were posted the last few weeks, but there were no new user-visible changes to report.)
 
@@ -391,56 +391,56 @@ New this week:
 
 Changes this week:
 
-- In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
-- A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
+* In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
+* A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
 
 ## 2021-02-05
 
 New this week:
 
-- V8 has been updated from 8.8 to 8.9.
-- During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
+* V8 has been updated from 8.8 to 8.9.
+* During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
 
 New last week (forgot to post):
 
-- Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
+* Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
 
 ## 2021-01-22
 
 New in the past week:
 
-- Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
+* Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
 
 ## 2021-01-14
 
 Changes this week:
 
-- Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
+* Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
 
 ## 2021-01-07
 
 Changes this week:
 
-- No user-visible changes.
+* No user-visible changes.
 
 Changes in the prior release:
 
-- Fixed delivery of WebSocket “error” events.
-- Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
+* Fixed delivery of WebSocket “error” events.
+* Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
 
 ## 2020-12-10
 
 Changes this week:
 
-- Major V8 update: 8.7.220.29 -> 8.8.278.8
+* Major V8 update: 8.7.220.29 -> 8.8.278.8
 
 ## 2019-09-19
 
 Changes this week:
 
-- Unannounced new feature. (Stay tuned.)
-- Enforced new limit on concurrent subrequests (see below).
-- Stability improvements.
+* Unannounced new feature. (Stay tuned.)
+* Enforced new limit on concurrent subrequests (see below).
+* Stability improvements.
 
 **Concurrent Subrequest Limit**
 
@@ -472,129 +472,129 @@ We chose the limit of 6 concurrent connections based on the fact that Chrome enf
 
 Changes this week:
 
-- Durable Objects storage API now supports listing keys by prefix.
-- Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
-- `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
-- Fixed off-by-one line numbers in Worker exceptions.
-- Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
-- Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
+* Durable Objects storage API now supports listing keys by prefix.
+* Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
+* `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
+* Fixed off-by-one line numbers in Worker exceptions.
+* Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
+* Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
 
 ## 2020-11-13
 
 Changes over the past week:
 
-- `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
-- Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
+* `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
+* Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
 
 ## 2020-11-05
 
 Changes this week:
 
-- Major V8 update: 8.6 -> 8.7
-- Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
+* Major V8 update: 8.6 -> 8.7
+* Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
 
 ## 2020-10-05
 
 We had our usual weekly release last week, but:
 
-- No user-visible changes.
+* No user-visible changes.
 
 ## 2020-09-24
 
 Changes this week:
 
-- Internal changes to support upcoming features.
+* Internal changes to support upcoming features.
 
 Also, a change from the 2020-09-08 release that it seems we forgot to post:
 
-- V8 major update: 8.5 -> 8.6
+* V8 major update: 8.5 -> 8.6
 
 ## 2020-08-03
 
 Changes last week:
 
-- Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
-- Upgraded V8 from 8.4 to 8.5.
+* Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
+* Upgraded V8 from 8.4 to 8.5.
 
 ## 2020-07-09
 
 Changes this week:
 
-- Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
-- Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
+* Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
+* Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
 
 Changes last week (… forgot to post):
 
-- `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
+* `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
 
 Changes the week before last (… also… forgot to post… we really need to code up a bot for this):
 
-- The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
+* The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
 
 ## 2020-05-15
 
 Changes this week:
 
-- Implemented API for yet-to-be-announced new feature.
+* Implemented API for yet-to-be-announced new feature.
 
 ## 2020-04-20
 
 Looks like we forgot to post release notes for a couple weeks. Releases still are happening weekly as always, but the “post to the community” step is insufficiently automated…
 4/2 release:
 
-- Fixed a source of long garbage collection paused in memory limit enforcement.
+* Fixed a source of long garbage collection paused in memory limit enforcement.
 
 4/9 release:
 
-- No publicly-visible changes.
+* No publicly-visible changes.
 
 4/16 release:
 
-- In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
+* In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
 
 ## 2020-03-26
 
 New this week:
 
-- Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
+* Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
 
 ## 2020-02-28
 
 New from the past two weeks:
 
-- Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
-- Major V8 update: 8.0 -> 8.1
-- Minor bug fixes.
+* Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
+* Major V8 update: 8.0 -> 8.1
+* Minor bug fixes.
 
 ## 2020-02-13
 
 Changes over the last couple weeks:
 
-- Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
-- Performance and stability improvements.
+* Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
+* Performance and stability improvements.
 
 ## 2020-01-24
 
 It has been a while since we posted release notes, partly due to the holidays. Here is what is new over the past month:
 
-- Performance and stability improvements.
-- A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
-- Updated V8 7.9 -> 8.0.
+* Performance and stability improvements.
+* A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
+* Updated V8 7.9 -> 8.0.
 
 ## 2019-12-12
 
 New this week:
 
-- We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
-- Fixed a significant source of daemonDown (1105) errors.
+* We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
+* Fixed a significant source of daemonDown (1105) errors.
 
 ## 2019-12-06
 
 Runtime release notes covering the past few weeks:
 
-- Increased total per-request `Cache.put()` limit to 5GiB.
-- Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
-- Added a helpful error message explaining AES decryption failures.
-- Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
-- More “internal errors” were converted to useful user-facing errors.
-- Stability improvements and bug fixes.
+* Increased total per-request `Cache.put()` limit to 5GiB.
+* Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
+* Added a helpful error message explaining AES decryption failures.
+* Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
+* More “internal errors” were converted to useful user-facing errors.
+* Stability improvements and bug fixes.
diff --git a/src/content/docs/workers/platform/changelog/index.mdx b/src/content/docs/workers/platform/changelog/index.mdx
index dd80529874c454a..c4945fcbdae6f6c 100644
--- a/src/content/docs/workers/platform/changelog/index.mdx
+++ b/src/content/docs/workers/platform/changelog/index.mdx
@@ -17,7 +17,7 @@ import { ProductReleaseNotes } from "~/components";
 
 This changelog details meaningful changes made to Workers across the Cloudflare dashboard, Wrangler, the API, and the workerd runtime. These changes are not configurable.
 
-This is _different_ from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
+This is *different* from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
 
 {/* <!-- Actual content lives in /src/content/release-notes/workers.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx
index 38a84a62e234adb..7e4e69499728faa 100644
--- a/src/content/docs/workers/platform/known-issues.mdx
+++ b/src/content/docs/workers/platform/known-issues.mdx
@@ -14,7 +14,7 @@ Below are some known bugs and issues to be aware of when using Cloudflare Worker
 
 ## Route specificity
 
-- When defining route specificity, a trailing `/*` in your pattern may not act as expected.
+* When defining route specificity, a trailing `/*` in your pattern may not act as expected.
 
 Consider two different Workers, each deployed to the same zone. Worker A is assigned the `example.com/images/*` route and Worker B is given the `example.com/images*` route pattern. With these in place, here are how the following URLs will be resolved:
 
@@ -44,11 +44,11 @@ When adding a wildcard on a subdomain, here are how the following URLs will be r
 
 ## wrangler dev
 
-- When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
+* When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
 
 ```js
 const request = new Request(url, incomingRequest);
-request.headers.delete("cf-workers-preview-token");
+request.headers.delete('cf-workers-preview-token');
 return await fetch(request);
 ```
 
@@ -90,11 +90,11 @@ For Workers subrequests, requests can only be made to URLs, not to IP addresses
 For example, in the zone `example.com` create a record of type `A` with the name `server` and value `192.0.2.1`, and then use:
 
 ```js
-await fetch("http://server.example.com");
+await fetch('http://server.example.com')
 ```
 
 Do not use:
 
 ```js
-await fetch("http://192.0.2.1");
+await fetch('http://192.0.2.1')
 ```
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
index 929570df6454101..d306aaec2558390 100644
--- a/src/content/docs/workers/platform/pricing.mdx
+++ b/src/content/docs/workers/platform/pricing.mdx
@@ -27,9 +27,9 @@ All [Pages Functions](/pages/functions/) are billed as Workers. All pricing and
 
 Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, contact your Account Manager.
 
-|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                      |
+|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                |
 | **Standard** | 10 million included per month <br /> +$0.30 per additional million | No charge or limit for duration | 30 million CPU milliseconds included per month<br /> +$0.02 per additional million CPU milliseconds<br /><br/> Max of [5 minutes of CPU time](/workers/platform/limits/#account-plan-limits) per invocation (default: 30 seconds)<br /> Max of 15 minutes of CPU time per [Cron Trigger](/workers/configuration/cron-triggers/) or [Queue Consumer](/queues/configuration/javascript-apis/#consumer) invocation |
 
 <sup>1</sup> Inbound requests to your Worker. Cloudflare does not bill for
diff --git a/src/content/docs/workers/reference/how-the-cache-works.mdx b/src/content/docs/workers/reference/how-the-cache-works.mdx
index fb3c5d8662710f6..53aad4dd28b3f81 100644
--- a/src/content/docs/workers/reference/how-the-cache-works.mdx
+++ b/src/content/docs/workers/reference/how-the-cache-works.mdx
@@ -17,9 +17,11 @@ Cloudflare Workers run before the cache but can also be utilized to modify asset
 Conceptually, there are two ways to interact with Cloudflare’s Cache using a Worker:
 
 - Call to [`fetch()`](/workers/runtime-apis/fetch/) in a Workers script. Requests proxied through Cloudflare are cached even without Workers according to a zone’s default or configured behavior (for example, static assets like files ending in `.jpg` are cached by default). Workers can further customize this behavior by:
+
   - Setting Cloudflare cache rules (that is, operating on the `cf` object of a [request](/workers/runtime-apis/request/)).
 
 - Store responses using the [Cache API](/workers/runtime-apis/cache/) from a Workers script. This allows caching responses that did not come from an origin and also provides finer control by:
+
   - Customizing cache behavior of any asset by setting headers such as `Cache-Control` on the response passed to `cache.put()`.
 
   - Caching responses generated by the Worker itself through `cache.put()`.
@@ -60,9 +62,11 @@ A("You have a Worker script that runs on <code>https://</code><code>example.com/
 Assets stored in the cache through [Cache API](/workers/runtime-apis/cache/) operations can be purged in a couple of ways:
 
 - Call `cache.delete` within a Worker to invalidate the cache for the asset with a matching request variable.
+
   - Assets purged in this way are only purged locally to the data center the Worker runtime was executed.
 
 - To purge an asset globally, use the standard [cache purge options](/cache/how-to/purge-cache/). Based on cache API implementation, not all cache purge endpoints function for purging assets stored by the Cache API.
+
   - All assets on a zone can be purged by using the [Purge Everything](/cache/how-to/purge-cache/purge-everything/) cache operation. This purge will remove all assets associated with a Cloudflare zone from cache in all data centers regardless of the method set.
 
   - [Cache Tags](/cache/how-to/purge-cache/purge-by-tags/#add-cache-tag-http-response-headers) can be added to requests dynamically in a Worker by calling `response.headers.append()` and appending `Cache-Tag` values dynamically to that request. Once set, those tags can be used to selectively purge assets from cache without invalidating all cached assets on a zone.
diff --git a/src/content/docs/workers/reference/how-workers-works.mdx b/src/content/docs/workers/reference/how-workers-works.mdx
index 8d93ed5dfa09491..4a44795d4bf2054 100644
--- a/src/content/docs/workers/reference/how-workers-works.mdx
+++ b/src/content/docs/workers/reference/how-workers-works.mdx
@@ -9,7 +9,7 @@ products:
   - workers
 ---
 
-import { Render, WorkersIsolateDiagram } from "~/components";
+import { Render, WorkersIsolateDiagram } from "~/components"
 
 Though Cloudflare Workers behave similarly to [JavaScript](https://www.cloudflare.com/learning/serverless/serverless-javascript/) in the browser or in Node.js, there are a few differences in how you have to think about your code. Under the hood, the Workers runtime uses the [V8 engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/) — the same engine used by Chromium and Node.js. The Workers runtime also implements many of the standard [APIs](/workers/runtime-apis/) available in most modern browsers.
 
@@ -27,13 +27,13 @@ The three largest differences are: Isolates, Compute per Request, and Distribute
 
 <Render file="isolate-description" product="workers" />
 
-<WorkersIsolateDiagram />
+<WorkersIsolateDiagram/>
 
 A given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons:
 
-- Resource limitations on the machine.
-- A suspicious script - anything seen as trying to break out of the isolate sandbox.
-- Individual [resource limits](/workers/platform/limits/).
+* Resource limitations on the machine.
+* A suspicious script - anything seen as trying to break out of the isolate sandbox.
+* Individual [resource limits](/workers/platform/limits/).
 
 Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingency.
 
@@ -52,6 +52,6 @@ Because there is no guarantee that any two user requests will be routed to the s
 
 ## Related resources
 
-- [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
-- [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
-- [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
+* [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
+* [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
+* [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
diff --git a/src/content/docs/workers/reference/protocols.mdx b/src/content/docs/workers/reference/protocols.mdx
index bd089af6329ec22..fe7f15baf21e464 100644
--- a/src/content/docs/workers/reference/protocols.mdx
+++ b/src/content/docs/workers/reference/protocols.mdx
@@ -10,10 +10,10 @@ products:
 
 Cloudflare Workers support the following protocols and interfaces:
 
-| Protocol               | Inbound                                                                                                                                                                                                                                                                                                         | Outbound                                                                                        |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                              | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                   |
-| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                            | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/) |
-| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                                                                                                            |                                                                                                 |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                 |
-| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                 | [Email Workers](/email-routing/email-workers/)                                                  |
+| Protocol               | Inbound                                                                                                                                                                                                                                                                                                          | Outbound                                                                                                     |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                               | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                                |
+| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
+| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                           |                                     |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
+| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |
diff --git a/src/content/docs/workers/reference/security-model.mdx b/src/content/docs/workers/reference/security-model.mdx
index d79f5a740d88d0d..f45407e36b6b093 100644
--- a/src/content/docs/workers/reference/security-model.mdx
+++ b/src/content/docs/workers/reference/security-model.mdx
@@ -7,7 +7,7 @@ products:
   - workers
 ---
 
-import { WorkersArchitectureDiagram } from "~/components";
+import { WorkersArchitectureDiagram } from "~/components"
 
 This article includes an overview of Cloudflare security architecture, and then addresses two frequently asked about issues: V8 bugs and Spectre.
 
@@ -25,7 +25,7 @@ For more details, refer to [this talk](https://www.infoq.com/presentations/cloud
 
 Beginning with a quick overview of the Workers runtime architecture:
 
-<WorkersArchitectureDiagram />
+<WorkersArchitectureDiagram/>
 
 There are two fundamental parts of designing a code sandbox: secure isolation and API design.
 
@@ -172,7 +172,7 @@ In Workers, you can get the current time using the JavaScript Date API by callin
 ```js
 let start = Date.now();
 for (let i = 0; i < 1e6; i++) {
-	doSpectreAttack();
+  doSpectreAttack();
 }
 let end = Date.now();
 ```
diff --git a/src/content/docs/workers/runtime-apis/bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/index.mdx
index c395b7d9593aa09..a1b72465e91fb65 100644
--- a/src/content/docs/workers/runtime-apis/bindings/index.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/index.mdx
@@ -121,37 +121,38 @@ Bindings are located on the `env` object, which can be accessed in several ways:
   [DurableObject](/durable-objects/), and [Workflow](/workflows/):
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-    ```js
-    export class MyDurableObject extends DurableObject {
-    	async sayHello() {
-    		return `Hi, ${this.env.NAME}!`;
-    	}
-    }
-    ```
-    </TabItem> <TabItem label="Python" icon="seti:python">
-    ```python
-    from workers import WorkerEntrypoint, Response
-  
-    class Default(WorkerEntrypoint):
-    	async def fetch(self, request):
-    		return Response(f"Hi {self.env.NAME}")
-    ```
-    </TabItem></Tabs>
+  ```js
+  export class MyDurableObject extends DurableObject {
+  	async sayHello() {
+  		return `Hi, ${this.env.NAME}!`;
+  	}
+  }
+  ```
+  </TabItem> <TabItem label="Python" icon="seti:python">
+  ```python
+  from workers import WorkerEntrypoint, Response
+
+  class Default(WorkerEntrypoint):
+  	async def fetch(self, request):
+  		return Response(f"Hi {self.env.NAME}")
+  ```
+  </TabItem></Tabs>
+
 
 * It can be imported from `cloudflare:workers`:
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-    ```js
-    import { env } from "cloudflare:workers";
-    console.log(`Hi, ${env.Name}`);
-    ```
-    </TabItem> <TabItem label="Python" icon="seti:python">
-    ```python
-    from workers import import_from_javascript
-    env = import_from_javascript("cloudflare:workers").env
-    print(f"Hi, {env.NAME}")
-    ```
-    </TabItem></Tabs>
+  ```js
+  import { env } from "cloudflare:workers";
+  console.log(`Hi, ${env.Name}`);
+  ```
+  </TabItem> <TabItem label="Python" icon="seti:python">
+  ```python
+  from workers import import_from_javascript
+  env = import_from_javascript("cloudflare:workers").env
+  print(f"Hi, {env.NAME}")
+  ```
+  </TabItem></Tabs>
 
 ### Importing `env` as a global
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
index 6354459443f42ff..90cbad356d0ff57 100644
--- a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
@@ -6,16 +6,16 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components";
+import { TabItem, Tabs, WranglerConfig } from "~/components"
 
 The Rate Limiting API lets you define rate limits and write code around them in your Worker.
 
 You can use it to enforce:
 
-- Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
-- Different rate limits for different types of customers or users (ex: free vs. paid)
-- Resource-specific or path-specific limits (ex: limit per API route)
-- Any combination of the above
+* Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
+* Different rate limits for different types of customers or users (ex: free vs. paid)
+* Resource-specific or path-specific limits (ex: limit per API route)
+* Any combination of the above
 
 The Rate Limiting API is backed by the same infrastructure that serves [rate limiting rules](/waf/rate-limiting-rules/).
 
@@ -96,13 +96,15 @@ export default {
 
 The `limit()` API accepts a single argument — a configuration object with the `key` field.
 
-- The key you provide can be any `string` value.
-- A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
+* The key you provide can be any `string` value.
+* A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
 
 You can define and configure multiple rate limiting configurations per Worker, which allows you to define different limits against incoming request and/or user parameters as needed to protect your application or upstream APIs.
 
 For example, here is how you can define two rate limiting configurations for free and paid tier users:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -137,12 +139,12 @@ For example, here is how you can define two rate limiting configurations for fre
 
 A rate limiting binding has the following settings:
 
-| Setting         | Type     | Description                                                                                                                                                                                                                                     |
-| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `namespace_id`  | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
-| `simple`        | `object` | The rate limit configuration. `simple` is the only supported type.                                                                                                                                                                              |
-| `simple.limit`  | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`.                                                                                                                                                               |
-| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`.                                                                                                                                                                 |
+| Setting | Type | Description |
+| --- | --- | --- |
+| `namespace_id` | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
+| `simple` | `object` | The rate limit configuration. `simple` is the only supported type. |
+| `simple.limit` | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`. |
+| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`. |
 
 :::note
 Two rate limiting bindings that share the same `namespace_id` — even across different Workers on the same account — share the same rate limit counters for a given key. This is intentional and allows you to enforce a single rate limit across multiple Workers.
@@ -176,19 +178,19 @@ For example, to apply a rate limit of 1500 requests per minute, you would define
 
 The `key` passed to the `limit` function, that determines what to rate limit on, should represent a unique characteristic of a user or class of user that you wish to rate limit.
 
-- Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
-- It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
+* Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
+* It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
 
 ```ts
 // Recommended: use a key that represents a specific user or class of user
-const url = new URL(req.url);
-const userId = url.searchParams.get("userId") || "";
-const { success } = await env.MY_RATE_LIMITER.limit({ key: userId });
+const url = new URL(req.url)
+const userId = url.searchParams.get("userId") || ""
+const { success } = await env.MY_RATE_LIMITER.limit({ key: userId })
 
 // Not recommended:  many users may share a single IP, especially on mobile networks
 // or when using privacy-enabling proxies
-const ipAddress = req.headers.get("cf-connecting-ip") || "";
-const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress });
+const ipAddress = req.headers.get("cf-connecting-ip") || ""
+const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })
 ```
 
 ## Locality
@@ -206,7 +208,7 @@ The underlying counters are cached on the same machine that your Worker runs in,
 This means that while in your code you `await` a call to the `limit()` method:
 
 ```javascript
-const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId });
+const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId })
 ```
 
 You are not waiting on a network request. You can use the Rate Limiting API without introducing any meaningful latency to your Worker.
@@ -221,11 +223,11 @@ For example, if many requests come in to your Worker in a single Cloudflare loca
 
 Rate limiting bindings are not currently visible in the Cloudflare dashboard. To monitor rate-limited requests from your Worker:
 
-- **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
-- **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
+* **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
+* **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
 
 ## Examples
 
-- [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
-- [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
-- [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
+* [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
+* [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
+* [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
index 153b3d20f4de2f8..a30129269dd55d9 100644
--- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
@@ -30,14 +30,16 @@ For example, consider the following Worker that implements a [`fetch()` handler]
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
-	},
-};
+  async fetch(request, env, ctx) {
+    return new Response("Hello World!");
+  }
+}
 ```
 
 The following Worker declares a binding to the Worker above:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -72,12 +74,12 @@ If you construct a new request manually, rather than forwarding an existing one,
 
 ```js
 export default {
-	async fetch(request, env) {
-		// provide a valid URL
-		let newRequest = new Request("https://valid-url.com", { method: "GET" });
-		let response = await env.WORKER_B.fetch(newRequest);
-		return response;
-	},
+  async fetch(request, env) {
+    // provide a valid URL
+    let newRequest = new Request("https://valid-url.com", { method: "GET" });
+    let response = await env.WORKER_B.fetch(newRequest);
+    return response;
+  }
 };
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/stream.mdx b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
index f07806aa6308be8..8614dfafc2d517e 100644
--- a/src/content/docs/workers/runtime-apis/bindings/stream.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
@@ -4,4 +4,5 @@ title: Stream
 external_link: /stream/manage-video-library/bindings/
 head: []
 description: Upload, manage, and deliver video with Cloudflare Stream.
+
 ---
diff --git a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
index f6647c550ce60aa..53634f635526565 100644
--- a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
@@ -15,7 +15,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components";
+import { TabItem, Tabs, WranglerConfig } from "~/components"
 
 The version metadata binding can be used to access metadata associated with a [version](/workers/configuration/versions-and-deployments/#versions) from inside the Workers runtime.
 
diff --git a/src/content/docs/workers/runtime-apis/cache.mdx b/src/content/docs/workers/runtime-apis/cache.mdx
index 6347b07bd87cc61..cc26647ff0a0df2 100644
--- a/src/content/docs/workers/runtime-apis/cache.mdx
+++ b/src/content/docs/workers/runtime-apis/cache.mdx
@@ -30,7 +30,7 @@ This individualized zone cache object differs from Cloudflare’s Global CDN. Fo
 
 :::
 
----
+***
 
 ## Accessing Cache
 
@@ -44,7 +44,7 @@ await cache.match(request);
 You may create and manage additional Cache instances via the [`caches.open`](https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage/open) method.
 
 ```js
-let myCache = await caches.open("custom:cache");
+let myCache = await caches.open('custom:cache');
 await myCache.match(request);
 ```
 
@@ -56,28 +56,28 @@ When using the cache API, avoid overriding the hostname in cache requests, as th
 // recommended approach: use your Worker hostname to ensure efficient caching
 request.url = "https://your-Worker-hostname.com/";
 
-let myCache = await caches.open("custom:cache");
+let myCache = await caches.open('custom:cache');
 let response = await myCache.match(request);
 ```
 
 :::
 
----
+***
 
 ## Headers
 
 Our implementation of the Cache API respects the following HTTP headers on the response passed to `put()`:
 
-- `Cache-Control`
-  - Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
-- `Cache-Tag`
-  - Allows resource purging by tag(s) later.
-- `ETag`
-  - Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
-- `Expires` string
-  - A string that specifies when the resource becomes invalid.
-- `Last-Modified`
-  - Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
+* `Cache-Control`
+  * Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
+* `Cache-Tag`
+  * Allows resource purging by tag(s) later.
+* `ETag`
+  * Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
+* `Expires` string
+  * A string that specifies when the resource becomes invalid.
+* `Last-Modified`
+  * Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
 
 This differs from the web browser Cache API as they do not honor any headers on the request or response.
 
@@ -89,7 +89,7 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 
 :::
 
----
+***
 
 ## Methods
 
@@ -99,8 +99,9 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 cache.put(request, response);
 ```
 
-- <code>put(request, response)</code> : Promise
-  - Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
+* <code>put(request, response)</code> : Promise
+
+  * Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
 
 :::note
 
@@ -110,19 +111,20 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 
 #### Parameters
 
-- `request` string | Request
-  - Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
+* `request` string | Request
 
-- `response` Response
-  - A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
+  * Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
+
+* `response` Response
+  * A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
 
 #### Invalid parameters
 
 `cache.put` will throw an error if:
 
-- The `request` passed is a method other than `GET`.
-- The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
-- The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
+* The `request` passed is a method other than `GET`.
+* The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
+* The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
 
 #### Errors
 
@@ -134,34 +136,40 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 cache.match(request, options);
 ```
 
-- <code>match(request, options)</code> : Promise`<Response | undefined>`
-  - Returns a promise wrapping the response object keyed to that request.
+* <code>match(request, options)</code> : Promise`<Response | undefined>`
+
+  * Returns a promise wrapping the response object keyed to that request.
 
 :::note
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
 :::
 
+
 #### Parameters
 
-- `request` string | Request
-  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+* `request` string | Request
 
-- `options`
-  - Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
+  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+
+* `options`
+  * Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
 
 Unlike the browser Cache API, Cloudflare Workers do not support the `ignoreSearch` or `ignoreVary` options on `match()`. You can accomplish this behavior by removing query strings or HTTP headers at `put()` time.
 
 Our implementation of the Cache API respects the following HTTP headers on the request passed to `match()`:
 
-- `Range`
-  - Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
+* `Range`
+
+  * Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
+
+* `If-Modified-Since`
 
-- `If-Modified-Since`
-  - Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
+  * Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
 
-- `If-None-Match`
-  - Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
+* `If-None-Match`
+
+  * Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
 
 :::note
 
@@ -180,12 +188,12 @@ If you use Cloudflare Logs, you may see these `504` responses with the `RequestS
 cache.delete(request, options);
 ```
 
-- <code>delete(request, options)</code> : Promise`<boolean>`
+* <code>delete(request, options)</code> : Promise`<boolean>`
 
 Deletes the `Response` object from the cache and returns a `Promise` for a Boolean response:
 
-- `true`: The response was cached but is now deleted
-- `false`: The response was not in the cache at the time of deletion.
+* `true`: The response was cached but is now deleted
+* `false`: The response was not in the cache at the time of deletion.
 
 :::caution[Global purges]
 
@@ -195,17 +203,18 @@ The `cache.delete` method only purges content of the cache in the data center th
 
 #### Parameters
 
-- `request` string | Request
-  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+* `request` string | Request
 
-- `options` object
-  - Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
----
+* `options` object
+  * Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+
+***
 
 ## Related resources
 
-- [How the cache works](/workers/reference/how-the-cache-works/)
-- [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
-- [Example: using the Cache API](/workers/examples/cache-api/)
-- [Example: caching POST requests](/workers/examples/cache-post-request/)
+* [How the cache works](/workers/reference/how-the-cache-works/)
+* [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
+* [Example: using the Cache API](/workers/examples/cache-api/)
+* [Example: caching POST requests](/workers/examples/cache-post-request/)
diff --git a/src/content/docs/workers/runtime-apis/console.mdx b/src/content/docs/workers/runtime-apis/console.mdx
index f1861458031b416..6ed3997531c52a7 100644
--- a/src/content/docs/workers/runtime-apis/console.mdx
+++ b/src/content/docs/workers/runtime-apis/console.mdx
@@ -18,39 +18,39 @@ The table below enumerates each method, and the extent to which it is supported
 
 All methods noted as "✅ supported" have the following behavior:
 
-- They will be written to the console in local dev (`npx wrangler@latest dev`)
-- They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
-- They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
+* They will be written to the console in local dev (`npx wrangler@latest dev`)
+* They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
+* They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
 
 All methods noted as "🟡 partial support" have the following behavior:
 
-- In both production and local development the method can be safely called, but will do nothing (no op)
-- In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
+* In both production and local development the method can be safely called, but will do nothing (no op)
+* In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
 
 Refer to [Log from Workers](https://developers.cloudflare.com/workers/observability/log-from-workers/) for more on debugging and adding logs to Workers.
 
 | Method                                                                                                         | Behavior                                                                                           |
 | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                       |
-| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                       |
-| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                       |
-| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                       |
-| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                       |
+| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                        |
+| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                        |
+| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                        |
+| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                        |
+| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                        |
 | [`console.clear()`](https://developer.mozilla.org/en-US/docs/Web/API/console/clear_static)                     | 🟡 partial support                                                                                 |
 | [`console.count()`](https://developer.mozilla.org/en-US/docs/Web/API/console/count_static)                     | 🟡 partial support                                                                                 |
 | [`console.group()`](https://developer.mozilla.org/en-US/docs/Web/API/console/group_static)                     | 🟡 partial support                                                                                 |
 | [`console.table()`](https://developer.mozilla.org/en-US/docs/Web/API/console/table_static)                     | 🟡 partial support                                                                                 |
 | [`console.trace()`](https://developer.mozilla.org/en-US/docs/Web/API/console/trace_static)                     | 🟡 partial support                                                                                 |
-| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                           |
-| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                           |
-| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                           |
-| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                           |
-| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                           |
-| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                           |
-| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                           |
-| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                           |
-| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                           |
-| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                           |
-| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                           |
-| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                           |
+| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                            |
+| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                            |
+| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                            |
+| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                            |
+| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                            |
+| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                            |
+| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                            |
+| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                            |
+| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                            |
+| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                            |
+| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                            |
+| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                            |
 | [`console.createTask()`](https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces) | 🔴 Will throw an exception in production, but works in local dev, Quick Editor, and remote preview |
diff --git a/src/content/docs/workers/runtime-apis/encoding.mdx b/src/content/docs/workers/runtime-apis/encoding.mdx
index 1c2d6dd741d8730..7f2f363e0232ea5 100644
--- a/src/content/docs/workers/runtime-apis/encoding.mdx
+++ b/src/content/docs/workers/runtime-apis/encoding.mdx
@@ -24,15 +24,24 @@ let encoder = new TextEncoder();
 
 ### Properties
 
-- `encoder.encoding` DOMString read-only
-  - The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
+
+
+* `encoder.encoding` DOMString read-only
+  * The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
+
+
 
 ### Methods
 
-- <code>encode(inputUSVString)</code> : Uint8Array
-  - Encodes a string input.
 
----
+
+* <code>encode(inputUSVString)</code> : Uint8Array
+
+  * Encodes a string input.
+
+
+
+***
 
 ## TextDecoder
 
@@ -50,16 +59,25 @@ let decoder = new TextDecoder();
 
 ### Properties
 
-- `decoder.encoding` DOMString read-only
-  - The name of the decoder that describes the method the `TextDecoder` uses.
 
-- `decoder.fatal` boolean read-only
-  - Indicates if the error mode is fatal.
 
-- `decoder.ignoreBOM` boolean read-only
-  - Indicates if the byte-order marker is ignored.
+* `decoder.encoding` DOMString read-only
+
+  * The name of the decoder that describes the method the `TextDecoder` uses.
+
+* `decoder.fatal` boolean read-only
+
+  * Indicates if the error mode is fatal.
+
+* `decoder.ignoreBOM` boolean read-only
+  * Indicates if the byte-order marker is ignored.
+
+
 
 ### Methods
 
-- `decode()` : DOMString
-  - Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
+
+
+* `decode()` : DOMString
+  * Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
+
diff --git a/src/content/docs/workers/runtime-apis/eventsource.mdx b/src/content/docs/workers/runtime-apis/eventsource.mdx
index e8678e44d07dd79..789989011083673 100644
--- a/src/content/docs/workers/runtime-apis/eventsource.mdx
+++ b/src/content/docs/workers/runtime-apis/eventsource.mdx
@@ -19,8 +19,12 @@ The [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource
 let eventSource = new EventSource(url, options);
 ```
 
-- `url` USVString - The URL to which to connect.
-- `options` EventSourceInit - An optional dictionary containing any optional settings.
+
+
+* `url` USVString - The URL to which to connect.
+* `options` EventSourceInit - An optional dictionary containing any optional settings.
+
+
 
 By default, the `EventSource` will use the global `fetch()` function under the
 covers to make requests. If you need to use a different fetch implementation as
@@ -28,10 +32,10 @@ provided by a Cloudflare Workers binding, you can pass the `fetcher` option:
 
 ```js
 export default {
-	async fetch(req, env) {
-		let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
-		// ...
-	},
+  async fetch(req, env) {
+    let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
+    // ...
+  }
 };
 ```
 
@@ -39,34 +43,49 @@ Note that the `fetcher` option is a Cloudflare Workers specific extension.
 
 ### Properties
 
-- `eventSource.url` USVString read-only
-  - The URL of the event source.
-- `eventSource.readyState` USVString read-only
-  - The state of the connection.
-- `eventSource.withCredentials` Boolean read-only
-  - A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
+
+
+* `eventSource.url` USVString read-only
+  * The URL of the event source.
+* `eventSource.readyState` USVString read-only
+  * The state of the connection.
+* `eventSource.withCredentials` Boolean read-only
+  * A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
+
+
 
 ### Methods
 
-- `eventSource.close()`
-  - Closes the connection.
-- `eventSource.onopen`
-  - An event handler called when a connection is opened.
-- `eventSource.onmessage`
-  - An event handler called when a message is received.
-- `eventSource.onerror`
-  - An event handler called when an error occurs.
+
+
+* `eventSource.close()`
+  * Closes the connection.
+* `eventSource.onopen`
+  * An event handler called when a connection is opened.
+* `eventSource.onmessage`
+  * An event handler called when a message is received.
+* `eventSource.onerror`
+  * An event handler called when an error occurs.
+
+
 
 ### Events
 
-- `message`
-  - Fired when a message is received.
-- `open`
-  - Fired when the connection is opened.
-- `error`
-  - Fired when an error occurs.
+
+
+* `message`
+  * Fired when a message is received.
+* `open`
+  * Fired when the connection is opened.
+* `error`
+  * Fired when an error occurs.
+
+
 
 ### Class Methods
 
-- <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
-  - This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
+
+
+* <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
+  * This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
+
diff --git a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
index 17256889d32d9bb..afee782db35b496 100644
--- a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
@@ -13,27 +13,36 @@ Incoming HTTP requests to a Worker are passed to the `fetch()` handler as a [`Re
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
+		return new Response('Hello World!');
 	},
 };
 ```
 
 :::note
 
+
 The Workers runtime does not support `XMLHttpRequest` (XHR). Learn the difference between `XMLHttpRequest` and `fetch()` in the [MDN](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) documentation.
 
+
 :::
 
 ### Parameters
 
-- `request` Request
-  - The incoming HTTP request.
 
-- `env` object
-  - The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
 
-- <code>ctx.waitUntil(promisePromise)</code> : void
-  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
+* `request` Request
+
+  * The incoming HTTP request.
+
+* `env` object
+
+  * The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
+
+* <code>ctx.waitUntil(promisePromise)</code> : void
+
+  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
+
+* <code>ctx.passThroughOnException()</code> : void
+
+  * Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
 
-- <code>ctx.passThroughOnException()</code> : void
-  - Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
diff --git a/src/content/docs/workers/runtime-apis/handlers/index.mdx b/src/content/docs/workers/runtime-apis/handlers/index.mdx
index 0ce1d48c75d798b..f62e15838d7d289 100644
--- a/src/content/docs/workers/runtime-apis/handlers/index.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/index.mdx
@@ -9,14 +9,14 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Handlers are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker. For example, the `fetch()` handler receives an HTTP request, and can return a response:
 
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
+		return new Response('Hello World!');
 	},
 };
 ```
diff --git a/src/content/docs/workers/runtime-apis/handlers/tail.mdx b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
index b95fc4c33d0ffea..7c6fbbaa19a19ad 100644
--- a/src/content/docs/workers/runtime-apis/handlers/tail.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
@@ -18,124 +18,170 @@ To configure a Tail Worker, refer to [Tail Workers documentation](/workers/obser
 
 ```js
 export default {
-	async tail(events, env, ctx) {
-		fetch("<YOUR_ENDPOINT>", {
-			method: "POST",
-			body: JSON.stringify(events),
-		});
-	},
-};
+  async tail(events, env, ctx) {
+    fetch("<YOUR_ENDPOINT>", {
+      method: "POST",
+      body: JSON.stringify(events),
+    })
+  }
+}
 ```
 
 ### Parameters
 
-- `events` array
-  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
 
-- `env` object
-  - An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
 
-- `ctx` object
-  - An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
+* `events` array
+
+  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
+
+* `env` object
+
+  * An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
+
+* `ctx` object
+  * An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
+
+
 
 ### Properties
 
-- `event.type` string
-  - The type of event. This will always return `"tail"`.
 
-- `event.traces` array
-  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
 
-- <code>event.waitUntil(promisePromise)</code> : void
-  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
+* `event.type` string
+
+  * The type of event. This will always return `"tail"`.
+
+* `event.traces` array
+
+  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
+
+* <code>event.waitUntil(promisePromise)</code> : void
+
+  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
+
+
 
 ### `TailItems`
 
 #### Properties
 
-- `scriptName` string
-  - The name of the producer script.
-
-- `event` object
-  - Contains information about the Worker’s triggering event.
-    - For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
-    - For other event types: `null`, currently.
-
-- `eventTimestamp` number
-  - Measured in epoch time.
-
-- `logs` array
-  - An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
-
-- `exceptions` array
-  - An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
-
-- `outcome` string
-  - The outcome of the Worker invocation, one of:
-    - `unknown`: outcome status was not set.
-    - `ok`: The worker invocation succeeded.
-    - `exception`: An unhandled exception was thrown. This can happen for many reasons, including:
-      - An uncaught JavaScript exception.
-      - A fetch handler that does not result in a Response.
-      - An internal error.
-    - `exceededCpu`: The Worker invocation exceeded either its CPU limits.
-    - `exceededMemory`: The Worker invocation exceeded memory limits.
-    - `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
-    - `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
-    - `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
+
+
+* `scriptName` string
+
+  * The name of the producer script.
+
+* `event` object
+
+  * Contains information about the Worker’s triggering event.
+    * For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
+    * For other event types: `null`, currently.
+
+* `eventTimestamp` number
+
+  * Measured in epoch time.
+
+* `logs` array
+
+  * An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
+
+* `exceptions` array
+
+  * An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
+
+* `outcome` string
+
+  * The outcome of the Worker invocation, one of:
+    * `unknown`: outcome status was not set.
+    * `ok`: The worker invocation succeeded.
+    * `exception`: An unhandled exception was thrown.  This can happen for many reasons, including:
+      * An uncaught JavaScript exception.
+      * A fetch handler that does not result in a Response.
+      * An internal error.
+    * `exceededCpu`: The Worker invocation exceeded either its CPU limits.
+    * `exceededMemory`: The Worker invocation exceeded memory limits.
+    * `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
+    * `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
+    * `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
+
+
 
 :::note[Outcome is not the same as HTTP status.]
 
 Outcome is equivalent to the exit status of a script and an indicator of whether it has fully run to completion. A Worker outcome may differ from a response code if, for example:
 
-- a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
-- a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
+* a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
+* a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
   :::
 
 ### `FetchEventInfo`
 
 #### Properties
 
-- `request` object
-  - A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
 
-- `response` object
-  - A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
+
+* `request` object
+
+  * A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
+
+* `response` object
+
+  * A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
+
 
 ### `TailRequest`
 
 #### Properties
 
-- `cf` object
-  - Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
 
-- `headers` object
-  - Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
 
-- `method` string
-  - The HTTP request method.
+* `cf` object
+
+  * Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
+
+* `headers` object
+
+  * Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
+
+* `method` string
+
+  * The HTTP request method.
+
+* `url` string
+
+  * The HTTP request URL (redacted by default).
+
 
-- `url` string
-  - The HTTP request URL (redacted by default).
 
 #### Methods
 
-- `getUnredacted()` object
-  - Returns a TailRequest object with unredacted properties
+
+
+* `getUnredacted()` object
+
+  * Returns a TailRequest object with unredacted properties
+
+
 
 Some of the properties of `TailRequest` are redacted by default to make it harder to accidentally record sensitive information, like user credentials or API tokens. The redactions use heuristic rules, so they are subject to false positives and negatives. Clients can call `getUnredacted()` to bypass redaction, but they should always be careful about what information is retained, whether using the redaction or not.
 
-- Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
-- URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
-- Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
-- Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
+* Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
+* URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
+* Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
+* Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
 
 ### `TailResponse`
 
 #### Properties
 
-- `status` number
-  - The HTTP status code.
+
+
+* `status` number
+
+  * The HTTP status code.
+
+
 
 ### `TailLog`
 
@@ -143,14 +189,20 @@ Records information sent to console functions.
 
 #### Properties
 
-- `timestamp` number
-  - Measured in epoch time.
 
-- `level` string
-  - A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
 
-- `message` object
-  - The array of parameters passed to the console function.
+* `timestamp` number
+
+  * Measured in epoch time.
+
+* `level` string
+
+  * A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
+
+* `message` object
+
+  * The array of parameters passed to the console function.
+
 
 ### `TailException`
 
@@ -158,15 +210,22 @@ Records an unhandled exception that occurred during the Worker invocation.
 
 #### Properties
 
-- `timestamp` number
-  - Measured in epoch time.
 
-- `name` string
-  - The error type (For example,`Error`, `TypeError`, etc.).
 
-- `message` object
-  - The error description (For example, `"x" is not a function`).
+* `timestamp` number
+
+  * Measured in epoch time.
+
+* `name` string
+
+  * The error type (For example,`Error`, `TypeError`, etc.).
+
+* `message` object
+
+  * The error description (For example, `"x" is not a function`).
+
+
 
 ## Related resources
 
-- [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
+* [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
diff --git a/src/content/docs/workers/runtime-apis/headers.mdx b/src/content/docs/workers/runtime-apis/headers.mdx
index f7a50f6ec116fc8..5fd387aafea782c 100644
--- a/src/content/docs/workers/runtime-apis/headers.mdx
+++ b/src/content/docs/workers/runtime-apis/headers.mdx
@@ -17,16 +17,16 @@ When a header name possesses multiple values, those values will be concatenated
 ```js
 let headers = new Headers();
 
-headers.get("x-foo"); //=> null
+headers.get('x-foo'); //=> null
 
-headers.set("x-foo", "123");
-headers.get("x-foo"); //=> "123"
+headers.set('x-foo', '123');
+headers.get('x-foo'); //=> "123"
 
-headers.set("x-foo", "hello");
-headers.get("x-foo"); //=> "hello"
+headers.set('x-foo', 'hello');
+headers.get('x-foo'); //=> "hello"
 
-headers.append("x-foo", "world");
-headers.get("x-foo"); //=> "hello, world"
+headers.append('x-foo', 'world');
+headers.get('x-foo'); //=> "hello, world"
 ```
 
 ## Differences
@@ -61,6 +61,7 @@ console.log(headers.getAll("Set-Cookie"));
 
 In Cloudflare Workers, the `Headers.get` method returns a [`USVString`](https://mdn2.netlify.app/en-us/docs/web/api/usvstring/) instead of a [`ByteString`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String), which is specified by the web standard. For most scenarios, this should have no noticeable effect. To compare the differences between these two string classes, refer to this [Playground example](https://workers.cloudflare.com/playground#LYVwNgLglgDghgJwgegGYHsHALQBM4RwDcABAEbogB2+CAngLzbMutvvsCMALAJx-cAzAHZeANkG8AHAAZOU7t2EBWAEy9eqsXNWdOALg5HjbHv34jxk2fMUr1m7Z12cAsACgAwuioQApr7YACJQAM4w6KFQ0D76JBhYeATEJFRwwH4MAERQNH4AHgB0AFahWaSoUGAB6Zk5eUWlWR7evgEQ2AAqdDB+cXAwMGBQAMYEUD7IxXAAbnChIwiwEADUwOi44H4eHgURSCS4fqhw4BAkAN7uAJDzdFQj8X4QIwAWABQIfgCOIH6hEAAlJcbtdqucxucGCQsoBeDcAXHtZUHgkggCCoKSeAgkaFUPwAdxInQKEAAog8Nn4EO9AYUAiNKe9IYDkc8SPTKbgsVCSABlCBLKgAc0KqAQ6GAnleiG8R3ehQVaIx3JZoIZVFC6GqhTA6CF7yynVeYRIJrgJAAqryAGr8wVCkj46KvEjmyH6LIAGhIzLVPk12t1+sNxtCprD5oAQnR-Hbcg6nRAXW7sT5LZ0AGLYKQe70co5cgiq67XZDIEgACT8cCOCAjXxIoRAg0iflwJAg6EdmAA1iQfGA6I7nSRo7GBfHQt6yGj+yAEKCy6bgEM-BlfOM0yBQv9LTa48LQoUiaHUiSSMM8cOwGASDBBec4Ivy-jEFR466KLOk2FCqzzq81a1mGuIEpWQFUqE7wXDC+ZttgkJZHEcGFucAC+xbXF8EDzlQZ6EgASv8EQan4BpSn4Ix9pQ5xJn4JAAAatAGfgMa6NAdoBJBEeE-r0YBNaQR2XY7vRdFzhAMCzgyK6IGE-qFF6lwkAJwEkBhNxoe4aEeCYelGGYAiWBI0hyAoShqBoWg6HoLQ+P4gQhLxUQxFQcQJDg+CEKQaQZNkGSEF5cDlPEVQ1H5WRkLqZDNF49ntF0PR9K6gzDJCExUFMmpUDs7gXFkwBwLkAD66ybNUSH1EcjRlDp7j6Q1rCGRYogmTY5n2FZTguMwHhAA).
 
+
 ## Cloudflare headers
 
 Cloudflare sets a number of its own custom headers on incoming requests and outgoing responses. While some may be used for its own tracking and bookkeeping, many of these can be useful to your own applications – or Workers – too.
@@ -69,5 +70,5 @@ For a list of documented Cloudflare request headers, refer to [Cloudflare HTTP h
 
 ## Related resources
 
-- [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
-- [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
+* [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
+* [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
\ No newline at end of file
diff --git a/src/content/docs/workers/runtime-apis/messagechannel.mdx b/src/content/docs/workers/runtime-apis/messagechannel.mdx
index dc8e4475fe3ec30..34a69e18a8ca1ac 100644
--- a/src/content/docs/workers/runtime-apis/messagechannel.mdx
+++ b/src/content/docs/workers/runtime-apis/messagechannel.mdx
@@ -19,10 +19,10 @@ currently limited to uses with a single Worker instance. This means that you can
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log("Received message:", event.data);
+	console.log('Received message:', event.data);
 };
 
-port2.postMessage("Hello from port2!");
+port2.postMessage('Hello from port2!');
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -31,13 +31,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-- Transfer lists are currently not supported. This means that you will not be able to transfer
+* Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-  are errors serializing or deserializing the message data. Instead, the error will be thrown when
-  the `postMessage` method is called on the sending port.
-- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+	are errors serializing or deserializing the message data. Instead, the error will be thrown when
+	the `postMessage` method is called on the sending port.
+* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/docs/workers/runtime-apis/nodejs/util.mdx b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
index 7a797483bdc8683..2e7372f4d555bc0 100644
--- a/src/content/docs/workers/runtime-apis/nodejs/util.mdx
+++ b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
@@ -35,16 +35,16 @@ await promisifiedFoo(args);
 Similarly to `promisify`, `callbackify` converts a Promise-returning async function into a Node.js-style callback function:
 
 ```js
-import { callbackify } from "node:util";
+import { callbackify } from 'node:util';
 
 async function foo(args) {
-	throw new Error("boom");
+  throw new Error('boom');
 }
 
 const callbackifiedFoo = callbackify(foo);
 
 callbackifiedFoo(args, (err, value) => {
-	if (err) throw err;
+  if (err) throw err;
 });
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/performance.mdx b/src/content/docs/workers/runtime-apis/performance.mdx
index f8c14e1b3cc76b2..0465b6db640c78a 100644
--- a/src/content/docs/workers/runtime-apis/performance.mdx
+++ b/src/content/docs/workers/runtime-apis/performance.mdx
@@ -21,7 +21,7 @@ When Workers are deployed to Cloudflare, as a security measure to [mitigate agai
 ```typescript title="Time is frozen — start will have the exact same value as end."
 const start = performance.now();
 for (let i = 0; i < 1e6; i++) {
-	// do expensive work
+  // do expensive work
 }
 const end = performance.now();
 const timing = end - start; // 0
diff --git a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
index acf48ac5f2c6e48..a0677b887aebf4c 100644
--- a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
@@ -18,9 +18,9 @@ An exception thrown by an RPC method implementation will propagate to the caller
 
 ### Unsupported error types
 
-- If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
-- The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
-- Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
+* If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
+* The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
+* Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
 
 ## Additional properties
 
diff --git a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
index 5bb6019d5d24910..2a80b67db3d88e2 100644
--- a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
@@ -16,7 +16,7 @@ Some method names are reserved or have special semantics.
 
 ## Special Methods
 
-For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does _not_ apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
+For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does *not* apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
 
 ### `fetch()`
 
@@ -36,12 +36,12 @@ The `connect()` method of the `WorkerEntrypoint` class is reserved for opening a
 
 The following method (or property) names may not be used as RPC methods on any RPC type (including `WorkerEntrypoint`, `DurableObject`, and `RpcTarget`):
 
-- `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
-- `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
+* `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
+* `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
 
 The following methods are disallowed only on `WorkerEntrypoint` and `DurableObject`, but allowed on `RpcTarget`. These methods have historically had special meaning to Durable Objects, where they are used to handle certain system-generated events.
 
-- `alarm`
-- `webSocketMessage`
-- `webSocketClose`
-- `webSocketError`
+* `alarm`
+* `webSocketMessage`
+* `webSocketClose`
+* `webSocketError`
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
index 8ec8b621e64213b..72512cc6f9f0f85 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
@@ -13,33 +13,47 @@ A `ReadableStream` is returned by the `readable` property inside [`TransformStre
 
 ## Properties
 
-- `locked` boolean
-  - A Boolean value that indicates if the readable stream is locked to a reader.
+
+
+* `locked` boolean
+  * A Boolean value that indicates if the readable stream is locked to a reader.
+
+
 
 ## Methods
 
-- <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
-  - Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
 
-- <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
-  - Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
+
+* <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
+
+  * Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
+
+* <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
+
+  * Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
 
 ```js
-let reader = readable.getReader({ mode: "byob" });
+let reader = readable.getReader({ mode: 'byob' });
 ```
 
+
+
 ### `PipeToOptions`
 
-- `preventClose` bool
-  - When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
 
-- `preventAbort` bool
-  - When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
 
----
+* `preventClose` bool
+
+  * When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
+
+* `preventAbort` bool
+
+  * When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
-- [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
+* [Streams](/workers/runtime-apis/streams/)
+* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+* [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
index c8a67b7ecf18fec..cff8e9257521f97 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
@@ -24,41 +24,50 @@ A `ReadableStreamBYOBReader` is not instantiated via its constructor. Rather, it
 
 ```js
 const { readable, writable } = new TransformStream();
-const reader = readable.getReader({ mode: "byob" });
+const reader = readable.getReader({ mode: 'byob' });
 ```
 
----
+***
 
 ## Methods
 
-- <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-  - Returns a promise with the next available chunk of data read into a passed-in buffer.
 
-- <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-  - Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read. The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
-    - If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
-    - If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
-    - If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
-    - If the stream errors, the promise rejects.
-    - `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
 
----
+* <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+
+  * Returns a promise with the next available chunk of data read into a passed-in buffer.
+
+* <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+
+  * Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read.  The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
+
+    * If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
+    * If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
+    * If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
+    * If the stream errors, the promise rejects.
+    * `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
+
+
+
+***
 
 ## Common issues
 
 :::caution[Warning]
 
+
 `read` provides no control over the minimum number of bytes that should be read into the buffer. Even if you allocate a 1 MiB buffer, the kernel is perfectly within its rights to fulfill this read with a single byte, whether or not an EOF immediately follows.
 
 In practice, the Workers team has found that `read` typically fills only 1% of the provided buffer.
 
 `readAtLeast` is a non-standard extension to the Streams API which allows users to specify that at least `minElements` elements must be read into the buffer before resolving the read. For a `Uint8Array` (the most common case), each element is one byte, so `minElements` is effectively a byte count. If the stream ends before `minElements` elements are available, the partial data that was read is still returned rather than throwing an error — refer to the [`readAtLeast` method documentation above](#methods) for the full details.
 
+
 :::
 
----
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
+* [Streams](/workers/runtime-apis/streams/)
+* [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
index 41d4eaf45b54a02..72a05a4edd97f20 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
@@ -23,32 +23,44 @@ const { readable, writable } = new TransformStream();
 const reader = readable.getReader();
 ```
 
----
+***
 
 ## Properties
 
-- `reader.closed` : Promise
-  - A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
+
+
+* `reader.closed` : Promise
+
+  * A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
+
+
 
 ## Methods
 
-- `read()` : Promise
-  - A promise that returns the next available chunk of data being passed through the reader queue.
 
-- <code>cancel(reasonstringoptional)</code> : void
-  - Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
+
+* `read()` : Promise
+
+  * A promise that returns the next available chunk of data being passed through the reader queue.
+
+* <code>cancel(reasonstringoptional)</code> : void
+
+  * Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet read is lost.
   :::
 
-- `releaseLock()` : void
-  - Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+* `releaseLock()` : void
 
----
+  * Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
index 46c9e41542ea8b0..029a878e9e847be 100644
--- a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
@@ -13,7 +13,7 @@ A transform stream consists of a pair of streams: a writable stream, known as it
 
 Workers currently only implements an identity transform stream, a type of transform stream which forwards all chunks written to its writable side to its readable side, without any changes.
 
----
+***
 
 ## Constructor
 
@@ -21,17 +21,26 @@ Workers currently only implements an identity transform stream, a type of transf
 let { readable, writable } = new TransformStream();
 ```
 
-- `TransformStream()` TransformStream
-  - Returns a new identity transform stream.
+
+
+* `TransformStream()` TransformStream
+
+  * Returns a new identity transform stream.
+
+
 
 ## Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## `IdentityTransformStream`
 
@@ -45,17 +54,26 @@ The `IdentityTransformStream` readable side supports [bring your own buffer (BYO
 let { readable, writable } = new IdentityTransformStream();
 ```
 
-- `IdentityTransformStream()` IdentityTransformStream
-  - Returns a new identity transform stream.
+
+
+* `IdentityTransformStream()` IdentityTransformStream
+
+  * Returns a new identity transform stream.
+
+
 
 ### Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## `FixedLengthStream`
 
@@ -67,20 +85,29 @@ The `FixedLengthStream` is a specialization of `IdentityTransformStream` that li
 let { readable, writable } = new FixedLengthStream(1000);
 ```
 
-- `FixedLengthStream(length)` FixedLengthStream
-  - Returns a new identity transform stream.
-  - `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
+
+
+* `FixedLengthStream(length)` FixedLengthStream
+
+  * Returns a new identity transform stream.
+  * `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
+
+
 
 ### Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
+* [Streams](/workers/runtime-apis/streams/)
+* [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
index 1040f59de92975c..799ddf11156ada5 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
@@ -15,9 +15,9 @@ A typical way to write to a `WritableStream` is to pipe a [`ReadableStream`](/wo
 
 ```js
 readableStream
-	.pipeTo(writableStream)
-	.then(() => console.log("All data successfully written!"))
-	.catch((e) => console.error("Something went wrong!", e));
+  .pipeTo(writableStream)
+  .then(() => console.log('All data successfully written!'))
+  .catch(e => console.error('Something went wrong!', e));
 ```
 
 To write to a `WritableStream` directly, you must use its writer.
@@ -31,25 +31,36 @@ Refer to the [WritableStreamDefaultWriter](/workers/runtime-apis/streams/writabl
 
 ## Properties
 
-- `locked` boolean
-  - A Boolean value to indicate if the writable stream is locked to a writer.
+
+
+* `locked` boolean
+
+  * A Boolean value to indicate if the writable stream is locked to a writer.
+
+
 
 ## Methods
 
-- <code>abort(reasonstringoptional)</code> : Promise\<void>
-  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+
+
+* <code>abort(reasonstringoptional)</code> : Promise\<void>
+
+  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-- `getWriter()` : WritableStreamDefaultWriter
-  - Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+* `getWriter()` : WritableStreamDefaultWriter
 
----
+  * Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
index fda65a4afb87bbd..9778261db7f5088 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
@@ -18,57 +18,71 @@ A writer is used when you want to write directly to a [`WritableStream`](/worker
 
 ```js
 function writeArrayToStream(array, writableStream) {
-	const writer = writableStream.getWriter();
-	array.forEach((chunk) => writer.write(chunk).catch(() => {}));
+  const writer = writableStream.getWriter();
+  array.forEach(chunk => writer.write(chunk).catch(() => {}));
 
-	return writer.close();
+  return writer.close();
 }
 
 writeArrayToStream([1, 2, 3, 4, 5], writableStream)
-	.then(() => console.log("All done!"))
-	.catch((e) => console.error("Error with the stream: " + e));
+  .then(() => console.log('All done!'))
+  .catch(e => console.error('Error with the stream: ' + e));
 ```
 
 ## Properties
 
-- `writer.desiredSize` int
-  - The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
 
-- `writer.closed` Promise\<void>
-  - A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
+
+* `writer.desiredSize` int
+
+  * The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
+
+* `writer.closed` Promise\<void>
+
+  * A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
+
+
 
 ## Methods
 
-- <code>abort(reasonstringoptional)</code> : Promise\<void>
-  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+
+
+* <code>abort(reasonstringoptional)</code> : Promise\<void>
+
+  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-- `close()` : Promise\<void>
-  - Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
+* `close()` : Promise\<void>
+
+  * Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
 
-- `releaseLock()` : void
-  - Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
+* `releaseLock()` : void
+
+  * Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
 
 ```js
 let writer = writable.getWriter();
 // Write a preamble.
-writer.write(new TextEncoder().encode("foo bar"));
+writer.write(new TextEncoder().encode('foo bar'));
 // While that’s still writing, pipe the rest of the body from somewhere else.
 writer.releaseLock();
 await someResponse.body.pipeTo(writable);
 ```
 
-- <code>write(chunkany)</code> : Promise\<void>
-  - Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
-  - The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+* <code>write(chunkany)</code> : Promise\<void>
 
----
+  * Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
+  * The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
index ef899b752b54415..be6e3593489cb39 100644
--- a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
+++ b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
@@ -29,132 +29,143 @@ The `connect()` function returns a TCP socket, with both a [readable](/workers/r
 `connect()` is provided as a [Runtime API](/workers/runtime-apis/), and is accessed by importing the `connect` function from `cloudflare:sockets`. This process is similar to how one imports built-in modules in Node.js. Refer to the following codeblock for an example of creating a TCP socket, writing to it, and returning the readable side of the socket as a response:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from 'cloudflare:sockets';
 
 export default {
-	async fetch(req): Promise<Response> {
-		const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
-		const url = new URL(req.url);
-
-		try {
-			const socket = connect(gopherAddr);
-
-			const writer = socket.writable.getWriter();
-			const encoder = new TextEncoder();
-			const encoded = encoder.encode(url.pathname + "\r\n");
-			await writer.write(encoded);
-			await writer.close();
-
-			return new Response(socket.readable, {
-				headers: { "Content-Type": "text/plain" },
-			});
-		} catch (error) {
-			return new Response("Socket connection failed: " + error, {
-				status: 500,
-			});
-		}
-	},
+  async fetch(req): Promise<Response> {
+    const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
+    const url = new URL(req.url);
+
+    try {
+      const socket = connect(gopherAddr);
+
+      const writer = socket.writable.getWriter()
+      const encoder = new TextEncoder();
+      const encoded = encoder.encode(url.pathname + "\r\n");
+      await writer.write(encoded);
+      await writer.close();
+
+      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
+    } catch (error) {
+      return new Response("Socket connection failed: " + error, { status: 500 });
+    }
+  }
 } satisfies ExportedHandler;
 ```
 
-- <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
-  - `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
+
+
+* <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
+  * `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
+
 
 ### `SocketAddress`
 
-- `hostname` string
-  - The hostname to connect to. Example: `cloudflare.com`.
 
-- `port` number
-  - The port number to connect to. Example: `5432`.
+
+* `hostname` string
+  * The hostname to connect to. Example: `cloudflare.com`.
+
+* `port` number
+  * The port number to connect to. Example: `5432`.
+
+
 
 ### `SocketOptions`
 
-- `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
-  - Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
-  - `off` — Do not use TLS.
-  - `on` — Use TLS.
-  - `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
 
-- `allowHalfOpen` boolean — Defaults to `false`
-  - Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
-  - This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
+
+* `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
+  * Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
+  * `off` — Do not use TLS.
+  * `on` — Use TLS.
+  * `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
+
+* `allowHalfOpen` boolean — Defaults to `false`
+  * Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
+  * This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
+
+
 
 ### `SocketInfo`
 
-- `remoteAddress` string | null
-  - The address of the remote peer the socket is connected to. May not always be set.
 
-- `localAddress` string | null
-  - The address of the local network endpoint for this socket. May not always be set.
+
+* `remoteAddress` string | null
+  * The address of the remote peer the socket is connected to. May not always be set.
+
+* `localAddress` string | null
+  * The address of the local network endpoint for this socket. May not always be set.
+
+
 
 ### `Socket`
 
-- <code>readable</code> : ReadableStream
-  - Returns the readable side of the TCP socket.
 
-- <code>writable</code> : WritableStream
-  - Returns the writable side of the TCP socket.
-  - The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
 
-- `opened` `Promise<SocketInfo>`
-  - This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
+* <code>readable</code> : ReadableStream
+  * Returns the readable side of the TCP socket.
+
+* <code>writable</code> : WritableStream
+  * Returns the writable side of the TCP socket.
+  * The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
+
+* `opened` `Promise<SocketInfo>`
+  * This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
+
+* `closed` `Promise<void>`
+  * This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
+
+* `close()` `Promise<void>`
+  * Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
-- `closed` `Promise<void>`
-  - This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
+* <code>startTls()</code> : Socket
+  * Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
-- `close()` `Promise<void>`
-  - Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
-- <code>startTls()</code> : Socket
-  - Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
 ## Opportunistic TLS (StartTLS)
 
 Many TCP-based systems, including databases and email servers, require that clients use opportunistic TLS (otherwise known as [StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS)) when connecting. In this pattern, the client first creates an insecure TCP socket, without TLS, and then upgrades it to a secure TCP socket, that uses TLS. The `connect()` API simplifies this by providing a method, `startTls()`, which returns a new `Socket` instance that uses TLS:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from "cloudflare:sockets"
 
 const address = {
-	hostname: "example-postgres-db.com",
-	port: 5432,
+  hostname: "example-postgres-db.com",
+  port: 5432
 };
 const socket = connect(address, { secureTransport: "starttls" });
 const secureSocket = socket.startTls();
 ```
 
-- `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
-- Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
-- `startTls()` should only be called once on an existing socket.
+* `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
+* Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
+* `startTls()` should only be called once on an existing socket.
 
 ## Handle errors
 
 To handle errors when creating a new TCP socket, reading from a socket, or writing to a socket, wrap these calls inside [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) statement blocks. The following example opens a connection to Google.com, initiates a HTTP request, and returns the response. If this fails and throws an exception, it returns a [`500`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-500/) response:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from 'cloudflare:sockets';
 const connectionUrl = { hostname: "google.com", port: 80 };
-export interface Env {}
+export interface Env { }
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			const socket = connect(connectionUrl);
-			const writer = socket.writable.getWriter();
-			const encoder = new TextEncoder();
-			const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
-			await writer.write(encoded);
-			await writer.close();
-
-			return new Response(socket.readable, {
-				headers: { "Content-Type": "text/plain" },
-			});
-		} catch (error) {
-			return new Response(`Socket connection failed: ${error}`, {
-				status: 500,
-			});
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      const socket = connect(connectionUrl);
+      const writer = socket.writable.getWriter();
+      const encoder = new TextEncoder();
+      const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
+      await writer.write(encoded);
+      await writer.close();
+
+      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
+    } catch (error) {
+      return new Response(`Socket connection failed: ${error}`, { status: 500 });
+    }
+  }
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -163,7 +174,7 @@ export default {
 You can close a TCP connection by calling `close()` on the socket. This will close both the readable and writable sides of the socket.
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from "cloudflare:sockets"
 
 const socket = connect({ hostname: "my-url.com", port: 70 });
 const reader = socket.readable.getReader();
@@ -175,11 +186,11 @@ const reader = socket.readable.getReader(); // This fails
 
 ## Considerations
 
-- Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
-- TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
-- Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
-- By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
-- Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
+* Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
+* TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
+* Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
+* By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
+* Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
 
 ## Troubleshooting
 
diff --git a/src/content/docs/workers/runtime-apis/web-crypto.mdx b/src/content/docs/workers/runtime-apis/web-crypto.mdx
index 5bb7cee5fad993b..9e3a0f0faaaf9f3 100644
--- a/src/content/docs/workers/runtime-apis/web-crypto.mdx
+++ b/src/content/docs/workers/runtime-apis/web-crypto.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 ## Background
 
@@ -19,13 +19,13 @@ Performing cryptographic operations using the Web Crypto API is significantly fa
 The Web Crypto API is implemented through the `SubtleCrypto` interface, accessible via the global `crypto.subtle` binding. A simple example of calculating a digest (also known as a hash) is:
 
 ```js
-const myText = new TextEncoder().encode("Hello world!");
+const myText = new TextEncoder().encode('Hello world!');
 
 const myDigest = await crypto.subtle.digest(
-	{
-		name: "SHA-256",
-	},
-	myText, // The data you want to hash as an ArrayBuffer
+  {
+    name: 'SHA-256',
+  },
+  myText // The data you want to hash as an ArrayBuffer
 );
 
 console.log(new Uint8Array(myDigest));
@@ -38,17 +38,27 @@ Some common uses include [signing requests](/workers/examples/signing-requests/)
 The Web Crypto API differs significantly from the [Node.js Crypto API](/workers/runtime-apis/nodejs/crypto/). If you are working with code that relies on the Node.js Crypto API, you can use it by enabling the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/).
 :::
 
----
+***
 
 ## Constructors
 
-- <code>crypto.DigestStream(algorithm)</code> DigestStream
-  - A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
+
+
+* <code>crypto.DigestStream(algorithm)</code> DigestStream
+
+  * A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
+
+
 
 ### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+
 
 ### Usage
 
@@ -112,16 +122,27 @@ export default {
 
 ## Methods
 
-- <code>crypto.randomUUID()</code> : string
-  - Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
 
-- <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
-  - Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
+
+* <code>crypto.randomUUID()</code> : string
+
+  * Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
+
+* <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
+
+  * Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
+
+
 
 ### Parameters
 
-- <code>buffer</code>ArrayBufferView
-  - Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
+
+
+* <code>buffer</code>ArrayBufferView
+
+  * Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
+
+
 
 ## SubtleCrypto Methods
 
@@ -129,219 +150,358 @@ These methods are all accessed via [`crypto.subtle`](https://developer.mozilla.o
 
 ### encrypt
 
-- <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
+
+
+* <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>BufferSource
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>BufferSource
+
+
 
 ### decrypt
 
-- <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
+
+
+* <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>BufferSource
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>BufferSource
+
+
 
 ### sign
 
-- <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
+
+
+* <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>ArrayBuffer
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>ArrayBuffer
+
+
 
 ### verify
 
-- <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
-  - Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
+
+
+* <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
+
+  * Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>signature</code>ArrayBuffer
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>signature</code>ArrayBuffer
+
+* <code>data</code>ArrayBuffer
+
 
-- <code>data</code>ArrayBuffer
 
 ### digest
 
-- <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
+
+
+* <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
-- <code>data</code>ArrayBuffer
+
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+* <code>data</code>ArrayBuffer
+
+
 
 ### generateKey
 
-- <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
-  - Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
+
+
+* <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
+
+  * Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
 
   ```js
   let keyPair = await crypto.subtle.generateKey(
-  	{
-  		name: "AES-GCM",
-  		length: 256,
-  	},
-  	true,
-  	["encrypt", "decrypt"],
+    {
+      name: 'AES-GCM',
+      length: 256,
+    },
+    true,
+    ['encrypt', 'decrypt']
   );
   ```
 
+
+
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+
+
 
 ### deriveKey
 
-- <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
+
+
+* <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
-- <code>baseKeyCryptoKey</code>
 
-- <code>derivedKeyAlgorithmobject</code>
-  - Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+
+* <code>baseKeyCryptoKey</code>
+
+* <code>derivedKeyAlgorithmobject</code>
+
+  * Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+
+* <code>extractablebool</code>
+
+* <code>keyUsagesArray</code>
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
-- <code>extractablebool</code>
 
-- <code>keyUsagesArray</code>
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
 ### deriveBits
 
-- <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
+
+
+* <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
 
-- <code>baseKey</code>CryptoKey
 
-- <code>length</code>int
-  - Length of the bit string to derive.
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
+
+* <code>baseKey</code>CryptoKey
+
+* <code>length</code>int
+
+  * Length of the bit string to derive.
+
+
 
 ### importKey
 
-- <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
+
+
+* <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
-- <code>keyData</code>ArrayBuffer
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+* <code>format</code>string
+
+  * Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+
+* <code>keyData</code>ArrayBuffer
+
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
 ### exportKey
 
-- <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
-  - Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
+
+
+* <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
+
+  * Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
 
-- <code>key</code>CryptoKey
+
+* <code>format</code>string
+
+  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
+
+* <code>key</code>CryptoKey
+
+
 
 ### wrapKey
 
-- <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
-  - Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
+
+
+* <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
+
+  * Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
 
-- <code>key</code>CryptoKey
 
-- <code>wrappingKey</code>CryptoKey
+* <code>format</code>string
+
+  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
+
+* <code>key</code>CryptoKey
+
+* <code>wrappingKey</code>CryptoKey
+
+* <code>wrapAlgo</code>object
+
+  * Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
+
 
-- <code>wrapAlgo</code>object
-  - Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
 
 ### unwrapKey
 
-- <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
+
+
+* <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>unwrappingKey</code>CryptoKey
+* <code>format</code>string
+
+  * Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>unwrappingKey</code>CryptoKey
 
-- <code>unwrapAlgo</code>object
-  - Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+* <code>unwrapAlgo</code>object
 
-- <code>unwrappedKeyAlgo</code>object
-  - Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+  * Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>unwrappedKeyAlgo</code>object
+
+  * Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
 ### timingSafeEqual
 
-- <code>timingSafeEqual(a, b)</code> : bool
-  - Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
+
+
+* <code>timingSafeEqual(a, b)</code> : bool
+
+  * Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
+
+
 
 #### Parameters
 
-- <code>a</code>ArrayBuffer | TypedArray
 
-- <code>b</code>ArrayBuffer | TypedArray
+
+* <code>a</code>ArrayBuffer | TypedArray
+
+* <code>b</code>ArrayBuffer | TypedArray
+
+
 
 ### Supported algorithms
 
@@ -351,6 +511,8 @@ A checkmark (✓) indicates that this feature is believed to be fully supported
 An x (✘) indicates that this feature is part of the specification but not implemented.<br/>
 If a feature only implements the operation partially, details are listed.
 
+
+
 | Algorithm                                          | sign()<br/>verify() | encrypt()<br/>decrypt() | digest() | deriveBits()<br/>deriveKey() | generateKey() | wrapKey()<br/>unwrapKey() | exportKey() | importKey() |
 | :------------------------------------------------- | :------------------ | :---------------------- | :------- | :--------------------------- | :------------ | :------------------------ | :---------- | :---------- |
 | RSASSA PKCS1 v1.5                                  | ✓                   |                         |          |                              | ✓             |                           | ✓           | ✓           |
@@ -374,27 +536,24 @@ If a feature only implements the operation partially, details are listed.
 | HKDF                                               |                     |                         |          | ✓                            |               |                           |             | ✓           |
 | PBKDF2                                             |                     |                         |          | ✓                            |               |                           |             | ✓           |
 
+
+
 **Footnotes:**
 
-1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves
-   API](https://wicg.github.io/webcrypto-secure-curves).
+1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves API](https://wicg.github.io/webcrypto-secure-curves).
 
-2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the
-   Ed25519 curve in addition to the Secure Curves version. Since this algorithm
-   is non-standard, note the following while using it:
-   - Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
-   - Unlike NodeJS, Cloudflare will not support raw import of private keys.
-   - The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
+2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the Ed25519 curve in addition to the Secure Curves version. Since this algorithm is non-standard, note the following while using it:
 
-3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is
-   supported in Cloudflare Workers for interacting with legacy systems that
-   require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for
-   security.
+   * Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
+   * Unlike NodeJS, Cloudflare will not support raw import of private keys.
+   * The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
 
----
+3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is supported in Cloudflare Workers for interacting with legacy systems that require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for security.
+
+***
 
 ## Related resources
 
-- [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
-- [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
-- [Example: signing requests](/workers/examples/signing-requests/)
+* [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
+* [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
+* [Example: signing requests](/workers/examples/signing-requests/)
diff --git a/src/content/docs/workers/runtime-apis/webassembly/index.mdx b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
index 492c0ae788ec4ea..d4a1cb8a2d546a5 100644
--- a/src/content/docs/workers/runtime-apis/webassembly/index.mdx
+++ b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
@@ -9,18 +9,18 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 [WebAssembly](https://webassembly.org/) (abbreviated Wasm) allows you to compile languages like [Rust](/workers/languages/rust/), Go, or C to a binary format that can run in a wide variety of environments, including [web browsers](https://developer.mozilla.org/en-US/docs/WebAssembly#browser_compatibility), Cloudflare Workers, and other WebAssembly runtimes.
 
 You can use WebAssembly to:
 
-- Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
-  :::note
-  `WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
-  :::
+* Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
+	:::note
+		`WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
+	:::
 
-- Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
+* Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
 
 Most programming languages can be compiled to Wasm, although support varies across languages and compilers. Guides are available for the following languages:
 
@@ -50,5 +50,5 @@ WASI is an earlier and more rapidly evolving set of standards than Wasm. WASI su
 
 ### Resources on WebAssembly
 
-- [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
-- [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
+* [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
+* [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
diff --git a/src/content/docs/workers/runtime-apis/websockets.mdx b/src/content/docs/workers/runtime-apis/websockets.mdx
index bf31fea43cc174c..6178ac08aa6b4b7 100644
--- a/src/content/docs/workers/runtime-apis/websockets.mdx
+++ b/src/content/docs/workers/runtime-apis/websockets.mdx
@@ -14,8 +14,10 @@ WebSockets allow you to communicate in real time with your Cloudflare Workers se
 
 :::note
 
+
 If your application needs to coordinate among multiple WebSocket connections, such as a chat room or game match, you will need clients to send messages to a single-point-of-coordination. Durable Objects provide a single-point-of-coordination for Cloudflare Workers, and are often used in parallel with WebSockets to persist state over multiple clients and connections. In this case, refer to [Durable Objects](/durable-objects/) to get started, and prefer using the Durable Objects' extended [WebSockets API](/durable-objects/best-practices/websockets/).
 
+
 :::
 
 ## Constructor
@@ -37,97 +39,148 @@ let [client, server] = Object.values(new WebSocketPair());
 
 ### accept
 
-- <code>accept(options?)</code>
-  - Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
+
+
+* <code>accept(options?)</code>
+
+  * Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
 
 #### Parameters
 
-- `options` object optional
-  - An optional configuration object with the following properties:
-    - `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
+
+
+* `options` object optional
+
+  * An optional configuration object with the following properties:
+
+    * `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
+
+
 
 ### addEventListener
 
-- <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
-  - Add callback functions to be executed when an event has occurred on the WebSocket.
+
+
+* <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
+
+  * Add callback functions to be executed when an event has occurred on the WebSocket.
+
+
 
 #### Parameters
 
-- `event` WebSocketEvent
-  - The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
 
-- <code>callbackFunction(messageMessage)</code> Function
-  - A function to be called when the WebSocket responds to a specific event.
+
+* `event` WebSocketEvent
+
+  * The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
+
+* <code>callbackFunction(messageMessage)</code> Function
+
+  * A function to be called when the WebSocket responds to a specific event.
+
+
 
 ### close
 
-- <code>close(codenumber, reasonstring)</code>
-  - Close the WebSocket connection.
+
+
+* <code>close(codenumber, reasonstring)</code>
+
+  * Close the WebSocket connection.
+
+
 
 #### Parameters
 
-- <code>codeinteger</code> optional
-  - An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
 
-- <code>reasonstring</code> optional
-  - A human-readable string indicating why the WebSocket connection was closed.
+
+* <code>codeinteger</code> optional
+
+  * An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
+
+* <code>reasonstring</code> optional
+
+  * A human-readable string indicating why the WebSocket connection was closed.
+
+
 
 ### send
 
-- <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
-  - Send a message to the other WebSocket in this WebSocket pair.
+
+
+* <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
+
+  * Send a message to the other WebSocket in this WebSocket pair.
+
+
 
 #### Parameters
 
-- <code>messagestring</code>
-  - The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
 
----
+
+* <code>messagestring</code>
+
+  * The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
+
+
+
+***
 
 ## Properties
 
 ### readyState
 
-- `readyState` number
-  - Returns the current state of the WebSocket connection. Possible values:
+* `readyState` number
 
-    | Constant               | Value | Description                                      |
-    | ---------------------- | ----- | ------------------------------------------------ |
-    | `WebSocket.CONNECTING` | `0`   | The connection is not yet open.                  |
-    | `WebSocket.OPEN`       | `1`   | The connection is open and ready to communicate. |
-    | `WebSocket.CLOSING`    | `2`   | The connection is in the process of closing.     |
-    | `WebSocket.CLOSED`     | `3`   | The connection is closed.                        |
+  * Returns the current state of the WebSocket connection. Possible values:
+
+    | Constant | Value | Description |
+    | --- | --- | --- |
+    | `WebSocket.CONNECTING` | `0` | The connection is not yet open. |
+    | `WebSocket.OPEN` | `1` | The connection is open and ready to communicate. |
+    | `WebSocket.CLOSING` | `2` | The connection is in the process of closing. |
+    | `WebSocket.CLOSED` | `3` | The connection is closed. |
 
 ### binaryType
 
-- `binaryType` string
-  - Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+* `binaryType` string
 
----
+  * Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+
+***
 
 ## Events
 
-- <code>close</code>* An event indicating the WebSocket has closed. The
-  `CloseEvent` includes `code` (number), `reason` (string), and `wasClean`
-  (boolean) properties.
 
-- <code>error</code>* An event indicating there was an error with the WebSocket.
 
-- <code>message</code>
-  - An event indicating a new message received from the client, including the data passed by the client.
+* <code>close</code>
+  * An event indicating the WebSocket has closed. The `CloseEvent` includes `code` (number), `reason` (string), and `wasClean` (boolean) properties.
+
+* <code>error</code>
+  * An event indicating there was an error with the WebSocket.
+
+* <code>message</code>
+  * An event indicating a new message received from the client, including the data passed by the client.
+
+
 
 :::note
-WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes). If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
+WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes).  If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
 :::
 
 ## Types
 
 ### Message
 
-- `data` any - The data passed back from the other WebSocket in your pair.
-- `type` string - Defaults to `message`.
 
----
+
+* `data` any - The data passed back from the other WebSocket in your pair.
+* `type` string - Defaults to `message`.
+
+
+
+***
 
 ## Close behavior
 
@@ -137,10 +190,10 @@ If you still call `close()` inside the `close` event handler, the call is silent
 
 ```js
 server.addEventListener("close", (event) => {
-	// readyState is already CLOSED — no need to call server.close().
-	console.log(server.readyState); // WebSocket.CLOSED
-	console.log(event.code); // 1000
-	console.log(event.wasClean); // true
+  // readyState is already CLOSED — no need to call server.close().
+  console.log(server.readyState); // WebSocket.CLOSED
+  console.log(event.code);        // 1000
+  console.log(event.wasClean);    // true
 });
 ```
 
@@ -152,12 +205,12 @@ The automatic close behavior can interfere with WebSocket proxying, where a Work
 server.accept({ allowHalfOpen: true });
 
 server.addEventListener("close", (event) => {
-	// readyState is still CLOSING here, giving you time
-	// to coordinate the close on the other side.
-	console.log(server.readyState); // WebSocket.CLOSING
+  // readyState is still CLOSING here, giving you time
+  // to coordinate the close on the other side.
+  console.log(server.readyState); // WebSocket.CLOSING
 
-	// Manually close when ready.
-	server.close(event.code, "done");
+  // Manually close when ready.
+  server.close(event.code, "done");
 });
 ```
 
@@ -171,7 +224,7 @@ WebSockets created with `new WebSocket(url)` always auto-reply to Close frames a
 
 On compatibility dates before `2026-04-07` (or with the `web_socket_manual_reply_to_close` flag), receiving a Close frame leaves the WebSocket in `CLOSING` state, and your code must call `close()` to complete the handshake. Failing to do so can result in `1006` abnormal closure errors on the client.
 
----
+***
 
 ## Binary messages
 
@@ -183,7 +236,7 @@ The `binaryType` property itself is always available. To opt back into `ArrayBuf
 
 ```js
 const resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -192,11 +245,11 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-	if (typeof event.data === "string") {
-		// Text frame.
-	} else {
-		// event.data is an ArrayBuffer because we set binaryType above.
-	}
+  if (typeof event.data === "string") {
+    // Text frame.
+  } else {
+    // event.data is an ArrayBuffer because we set binaryType above.
+  }
 });
 ```
 
@@ -223,9 +276,9 @@ This flag has no effect on the Durable Object hibernatable WebSocket [`webSocket
 
 :::
 
----
+***
 
 ## Related resources
 
-- [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
-- [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
+* [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
+* [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
diff --git a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
index 0ba52cb42d3e81a..31e081797dd1ada 100644
--- a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
+++ b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
@@ -14,7 +14,10 @@ Full-stack applications are web applications which are span both the client and
 
 The following full-stack frameworks are natively supported by Workers:
 
-<DirectoryListing folder="workers/framework-guides/web-apps" tag="full-stack" />
+<DirectoryListing
+	folder="workers/framework-guides/web-apps"
+	tag="full-stack"
+/>
 <DirectoryListing
 	folder="workers/framework-guides/web-apps/more-web-frameworks"
 	tag="full-stack"
diff --git a/src/content/docs/workers/testing/miniflare/storage/cache.md b/src/content/docs/workers/testing/miniflare/storage/cache.md
index c7c385b4cbe8025..78aac412fb542af 100644
--- a/src/content/docs/workers/testing/miniflare/storage/cache.md
+++ b/src/content/docs/workers/testing/miniflare/storage/cache.md
@@ -86,9 +86,7 @@ console.log(await res.text()); // 2
 You can programmatically purge all entries from a cache using the `purgeCache` method on the `Miniflare` instance. This is useful during development when cached assets need to be cleared without restarting the instance:
 
 ```js
-const mf = new Miniflare({
-	/* options */
-});
+const mf = new Miniflare({ /* options */ });
 
 // Purge the default cache and get the number of entries purged
 const count = await mf.purgeCache();
diff --git a/src/content/docs/workers/testing/vitest-integration/recipes.mdx b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
index d125b33d9e53931..79fb21b23ea73f1 100644
--- a/src/content/docs/workers/testing/vitest-integration/recipes.mdx
+++ b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
@@ -30,4 +30,4 @@ Recipes are examples that help demonstrate how to write unit tests and integrati
 - [Resolving modules with Vite Dependency Pre-Bundling](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/module-resolution)
 - [Mocking Workers AI and Vectorize bindings in unit tests](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/ai-vectorize)
 - [Tests using the Images binding](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/images)
-- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
+- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
\ No newline at end of file
diff --git a/src/content/docs/workers/vite-plugin/tutorial.mdx b/src/content/docs/workers/vite-plugin/tutorial.mdx
index ef7f05b8c086add..c5b6e9446a92aa4 100644
--- a/src/content/docs/workers/vite-plugin/tutorial.mdx
+++ b/src/content/docs/workers/vite-plugin/tutorial.mdx
@@ -205,7 +205,6 @@ This opts out of interpreting the `Sec-Fetch-Mode` header.
 ```
 
 </WranglerConfig>
-
 :::
 
 ### Call the API from the client
diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx
index ccabcb8262755a1..8b28f295cdc13b8 100644
--- a/src/content/docs/workers/wrangler/api.mdx
+++ b/src/content/docs/workers/wrangler/api.mdx
@@ -50,7 +50,9 @@ const result = await experimental_generateTypes(options);
 ### Parameters
 
 - `options` <Type text="object" /> <MetaInfo text="optional" />
+
   - Optional options object mirroring the `wrangler types` CLI flags:
+
     - `config` `string | string[]`
 
       Path to the Wrangler configuration file to use. Can be an array for multi-config type resolution.
@@ -88,15 +90,19 @@ const result = await experimental_generateTypes(options);
 `experimental_generateTypes()` returns a `Promise` resolving to an object containing the following fields:
 
 - `content` `string`
+
   - Combined formatted output containing all generated sections, including headers and both env and runtime types.
 
 - `env` `string | null`
+
   - Generated environment and bindings types, or `null` when env types are excluded.
 
 - `path` `string`
+
   - Target declaration file path associated with this generation run.
 
 - `runtime` `string | null`
+
   - Generated runtime types, or `null` when runtime types are excluded.
 
 ### Usage
@@ -500,22 +506,22 @@ The bindings supported by `getPlatformProxy` are:
     For example, you might have the following binding in a Wrangler configuration file read by `getPlatformProxy`.
 
     <WranglerConfig>
-                
-                    ```jsonc
-                    {
-                      "durable_objects": {
-                        "bindings": [
-                          {
-                            "name": "MyDurableObject",
-                            "class_name": "MyDurableObject",
-                            "script_name": "external-do-worker"
-                          }
-                        ]
+            
+                ```jsonc
+                {
+                  "durable_objects": {
+                    "bindings": [
+                      {
+                        "name": "MyDurableObject",
+                        "class_name": "MyDurableObject",
+                        "script_name": "external-do-worker"
                       }
-                    }
-                    ```
-                
-                    </WranglerConfig>
+                    ]
+                  }
+                }
+                ```
+            
+                </WranglerConfig>
 
     You will need to declare your Durable Object `"MyDurableObject"` in another Worker, called `external-do-worker` in this example.
 
@@ -535,14 +541,14 @@ The bindings supported by `getPlatformProxy` are:
     That Worker also needs a Wrangler configuration file that looks like this:
 
     <WranglerConfig>
-                        ```json
-                        {
-                        	"name": "external-do-worker",
-                        	"main": "src/index.ts",
-                        	"compatibility_date": "XXXX-XX-XX"
-                        }
-                        ```
-                        </WranglerConfig>
+                    ```json
+                    {
+                    	"name": "external-do-worker",
+                    	"main": "src/index.ts",
+                    	"compatibility_date": "XXXX-XX-XX"
+                    }
+                    ```
+                    </WranglerConfig>
 
     If you are not using RPC with your Durable Object, you can run a separate Wrangler dev session alongside your framework development server.
 
diff --git a/src/content/docs/workers/wrangler/commands/r2.mdx b/src/content/docs/workers/wrangler/commands/r2.mdx
index fb437a18a9717a9..60266e3b8e29b81 100644
--- a/src/content/docs/workers/wrangler/commands/r2.mdx
+++ b/src/content/docs/workers/wrangler/commands/r2.mdx
@@ -10,6 +10,7 @@ import { Render } from "~/components";
 
 Manage your [R2](/r2/) configurations using Wrangler.
 
+
 <Render file="wrangler-commands/r2" product="workers" />
 
 ## R2 SQL
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
index d19eda7c7872fca..f32639e194e9391 100644
--- a/src/content/docs/workers/wrangler/configuration.mdx
+++ b/src/content/docs/workers/wrangler/configuration.mdx
@@ -1839,26 +1839,26 @@ A common example of using a redirected configuration is where a custom build too
 - First, the user writes code that uses Cloudflare Workers resources, configured via a user's Wrangler configuration file like the following:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-    	"$schema": "./node_modules/wrangler/config-schema.json",
-    	"name": "my-worker",
-    	"main": "src/index.ts",
-    	"vars": {
-    		"MY_VARIABLE": "production variable",
-    	},
-    	"env": {
-    		"staging": {
-    			"vars": {
-    				"MY_VARIABLE": "staging variable",
-    			},
-    		},
-    	},
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+  	"$schema": "./node_modules/wrangler/config-schema.json",
+  	"name": "my-worker",
+  	"main": "src/index.ts",
+  	"vars": {
+  		"MY_VARIABLE": "production variable",
+  	},
+  	"env": {
+  		"staging": {
+  			"vars": {
+  				"MY_VARIABLE": "staging variable",
+  			},
+  		},
+  	},
+  }
+  ```
+
+  </WranglerConfig>
 
   This configuration points `main` at the user's code entry-point and defines the `MY_VARIABLE` variable in two different environments.
 
@@ -1872,8 +1872,8 @@ A common example of using a redirected configuration is where a custom build too
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>
-    	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
-    </FileTree>
+  	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
+  </FileTree>
 
 The generated `dist/wrangler.jsonc` might contain:
 
@@ -1896,4 +1896,4 @@ And the `.wrangler/deploy/config.json` contains the path to the generated config
 {
 	"configPath": "../../dist/wrangler.jsonc"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/workers/wrangler/custom-builds.mdx b/src/content/docs/workers/wrangler/custom-builds.mdx
index e22e4bc6c269534..0b63ae3bd2a8037 100644
--- a/src/content/docs/workers/wrangler/custom-builds.mdx
+++ b/src/content/docs/workers/wrangler/custom-builds.mdx
@@ -21,12 +21,15 @@ Wrangler runs [esbuild](https://esbuild.github.io/) by default as part of the `d
 Custom builds are configured by adding a `[build]` section in your [Wrangler configuration file](/workers/wrangler/configuration/), and using the following options for configuring your custom build.
 
 - `command` <Type text="string" /> <MetaInfo text="optional" />
+
   - The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used. This command will be run as part of `wrangler dev` and `npx wrangler deploy`.
 
 - `cwd` <Type text="string" /> <MetaInfo text="optional" />
+
   - The directory in which the command is executed.
 
 - `watch_dir` <Type text="string | string\[]" /> <MetaInfo text="optional" />
+
   - The directory to watch for changes while using `wrangler dev`. Defaults to the current working directory.
 
 Example:
@@ -51,12 +54,12 @@ When Wrangler runs your custom build command, it sets the `WRANGLER_COMMAND` env
 
 The possible values are:
 
-| Value             | Wrangler command triggered |
-| ----------------- | -------------------------- |
-| `dev`             | `wrangler dev`             |
-| `deploy`          | `wrangler deploy`          |
-| `versions upload` | `wrangler versions upload` |
-| `types`           | `wrangler types`           |
+| Value              | Wrangler command triggered               |
+| ------------------ | ---------------------------------------- |
+| `dev`              | `wrangler dev`                           |
+| `deploy`           | `wrangler deploy`                        |
+| `versions upload`  | `wrangler versions upload`               |
+| `types`            | `wrangler types`                         |
 
 For example, you can use this to apply different build settings for development and production:
 
diff --git a/src/content/docs/workers/wrangler/deprecations.mdx b/src/content/docs/workers/wrangler/deprecations.mdx
index ab606324004172b..3b4d23ccc8c99eb 100644
--- a/src/content/docs/workers/wrangler/deprecations.mdx
+++ b/src/content/docs/workers/wrangler/deprecations.mdx
@@ -83,89 +83,82 @@ This no longer has any effect, after the [rollout of Workers Standard Pricing](h
 
 Wrangler v2 introduces new fields for configuration and new features for developing and deploying a Worker, while deprecating some redundant fields.
 
-- `wrangler.toml` is no longer mandatory.
-- `dev` and `publish` accept CLI arguments.
-- `tail` can be run on arbitrary Worker names.
-- `init` creates a project boilerplate.
-- JSON bindings for `vars`.
-- Local mode for `wrangler dev`.
-- Module system (for both modules and service worker format Workers).
-- DevTools.
-- TypeScript support.
-- Sharing development environment on the Internet.
-- Wider platform compatibility.
-- Developer hotkeys.
-- Better configuration validation.
+* `wrangler.toml` is no longer mandatory.
+* `dev` and `publish` accept CLI arguments.
+* `tail` can be run on arbitrary Worker names.
+* `init` creates a project boilerplate.
+* JSON bindings for `vars`.
+* Local mode for `wrangler dev`.
+* Module system (for both modules and service worker format Workers).
+* DevTools.
+* TypeScript support.
+* Sharing development environment on the Internet.
+* Wider platform compatibility.
+* Developer hotkeys.
+* Better configuration validation.
 
 The following video describes some of the major changes in Wrangler v2, and shows you how Wrangler v2 can help speed up your workflow.
 
-<div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
-</div>
+<div style="position: relative; padding-top: 56.25%;"><iframe src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600" style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;" allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;" allowfullscreen="true"></iframe></div>
 
 ### Common deprecations
 
 Refer to the following list for common fields that are no longer required.
 
-- `type` is no longer required. Wrangler will infer the correct project type automatically.
-- `zone_id` is no longer required. It can be deduced from the routes directly.
-- `build.upload.format` is no longer used. The format is now inferred automatically from the code.
-- `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
-- `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
-- `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
+* `type` is no longer required. Wrangler will infer the correct project type automatically.
+* `zone_id` is no longer required. It can be deduced from the routes directly.
+* `build.upload.format` is no longer used. The format is now inferred automatically from the code.
+* `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
+* `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
+* `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
   Here are the Wrangler v1 commands that are no longer supported:
-- `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
-- `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
-- `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
-- `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
-- `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
+* `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
+* `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
+* `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
+* `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
+* `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
 
 #### New fields
 
 These are new fields that can be added to your [Wrangler configuration file](/workers/wrangler/configuration/).
 
-- **`main`**: `string`, optional
+* **`main`**: `string`, optional
 
   The `main` field is used to specify an entry point to the Worker. It may be in the established service worker format, or the newer, preferred modules format. An entry point is now explicitly required, and can be configured either via the `main` field, or passed directly as a command line, for example, `wrangler dev index.js`. This field replaces the legacy `build.upload.main` field (which only applied to modules format Workers).
 
-- **`rules`**: `array`, optional
+* **`rules`**: `array`, optional
 
   The `rules` field is an array of mappings between module types and file patterns. It instructs Wrangler to interpret specific files differently than JavaScript. For example, this is useful for reading text-like content as text files, or compiled WASM as ready to instantiate and execute. These rules can apply to Workers of both the established service worker format, and the newer modules format. This field replaces the legacy `build.upload.rules` field (which only applied to modules format Workers).
 
-{/\* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
+{/* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
 
-The `legacy_env` field toggles how environments are handled by `wrangler`.
+  The `legacy_env` field toggles how environments are handled by `wrangler`.
 
-- When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
-- When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
-  Read more at (ref:)[] --> \*/}
+  - When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
+  - When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
+    Read more at (ref:)[] --> */}
 
-{/\* <!-- - **`services`**: TODO
+{/* <!-- - **`services`**: TODO
 
 - **`node-compat`**: TODO
 
-- **`public`**: TODO --> \*/}
+- **`public`**: TODO --> */}
 
 #### Non-mandatory fields
 
 A few configuration fields which were previously required, are now optional in particular situations. They can either be inferred, or added as an optimization. No fields are required anymore when starting with Wrangler v2, and you can gradually add configuration as the need arises.
 
-- **`name`**: `string`
+* **`name`**: `string`
 
   The `name` configuration field is now not required for `wrangler dev`, or any of the `wrangler kv:*` commands. Further, it can also be passed as a command line argument as `--name <name>`. It is still required for `wrangler deploy`.
 
-- **`account_id`**: `string`
+* **`account_id`**: `string`
 
   The `account_id` field is not required for any of the commands. Any relevant commands will check if you are logged in, and if not, will prompt you to log in. Once logged in, it will use your account ID and will not prompt you again until your login session expires. If you have multiple account IDs, you will be presented with a list of accounts to choose from.
 
   You can still configure `account_id` in your Wrangler file, or as an environment variable `CLOUDFLARE_ACCOUNT_ID`. This makes startup faster and bypasses the list of choices if you have multiple IDs. The `CLOUDFLARE_API_TOKEN` environment variable is also useful for situations where it is not possible to login interactively. To learn more, visit [Running in CI/CD](/workers/ci-cd/external-cicd/).
 
-- **`workers_dev`** `boolean`, default: `true` when no routes are present
+* **`workers_dev`** `boolean`, default: `true` when no routes are present
 
   The `workers_dev` field is used to indicate that the Worker should be published to a `*.workers.dev` subdomain. For example, for a Worker named `my-worker` and a previously configured `*.workers.dev` subdomain `username`, the Worker will get published to `my-worker.username.workers.dev.com`. This field is not mandatory, and defaults to `true` when `route` or `routes` are not configured. When routes are present, it defaults to `false`. If you want to neither publish it to a `*.workers.dev` subdomain nor any routes, set `workers_dev` to `false`. This useful when you are publishing a Worker as a standalone service that can only be accessed from another Worker with (`services`).
 
@@ -173,26 +166,27 @@ A few configuration fields which were previously required, are now optional in p
 
 A few configuration fields are deprecated, but their presence is not a breaking change yet. It is recommended to read the warning messages and follow the instructions to migrate to the new configuration. They will be removed and stop working in a future version.
 
-- **`zone_id`**: `string`, deprecated
+* **`zone_id`**: `string`, deprecated
 
   The `zone_id` field is deprecated and will be removed in a future release. It is now inferred from `route`/`routes`, and optionally from `dev.host` when using `wrangler dev`. This also makes it simpler to deploy a single Worker to multiple domains.
 
-- **`build.upload`**: `object`, deprecated
+* **`build.upload`**: `object`, deprecated
 
   The `build.upload` field is deprecated and will be removed in a future release. Its usage results in a warning with suggestions on rewriting the configuration file to remove the warnings.
-  - `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
-  - `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
-  - `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
+
+  * `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
+  * `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
+  * `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
 
 #### Deprecated fields (breaking)
 
 A few configuration fields are deprecated and will not work as expected anymore. It is recommended to read the error messages and follow the instructions to migrate to the new configuration.
 
-- **`site.entry-point`**: `string`, deprecated
+* **`site.entry-point`**: `string`, deprecated
 
   The `site.entry-point` configuration was used to specify an entry point for Workers with a `[site]` configuration. This has been replaced by the top-level `main` field.
 
-- **`type`**: `rust` | `javascript` | `webpack`, deprecated
+* **`type`**: `rust` | `javascript` | `webpack`, deprecated
 
   The `type` configuration was used to specify the type of Worker. It has since been made redundant and is now inferred from usage. If you were using `type = "webpack"` (and the optional `webpack_config` field), you should read the [webpack migration guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to modify your project and use a custom build instead.
 
@@ -232,11 +226,11 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 ### Other deprecated behavior
 
-- Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
+* Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
 
-- Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
+* Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
 
-- Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
+* Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
 
   ```
   project
@@ -250,7 +244,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
   import SomeDependency from "some-dependency.js";
 
   addEventListener("fetch", (event) => {
-  	// ...
+    // ...
   });
   ```
 
@@ -265,8 +259,8 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Commands
 
-| Command     | v1  | v2  | Notes                                          |
-| ----------- | --- | --- | ---------------------------------------------- |
+| Command     | v1 | v2 | Notes                                          |
+| ----------- | -- | -- | ---------------------------------------------- |
 | `publish`   | ✅  | ✅  |                                                |
 | `dev`       | ✅  | ✅  |                                                |
 | `preview`   | ✅  | ❌  | Removed, use `dev` instead.                    |
@@ -277,7 +271,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 | `route`     | ✅  | ❌  | Removed, use `publish` instead.                |
 | `tail`      | ✅  | ✅  |                                                |
 | `kv`        | ✅  | ✅  |                                                |
-| `r2`        | 🚧  | ✅  | Introduced in Wrangler v1.19.8.                |
+| `r2`        | 🚧 | ✅  | Introduced in Wrangler v1.19.8.                |
 | `pages`     | ❌  | ✅  |                                                |
 | `config`    | ✅  | ❓  |                                                |
 | `login`     | ✅  | ✅  |                                                |
@@ -288,15 +282,15 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Configuration
 
-| Property              | v1  | v2  | Notes                                                                                           |
-| --------------------- | --- | --- | ----------------------------------------------------------------------------------------------- |
+| Property              | v1 | v2 | Notes                                                                                                                                            |
+| --------------------- | -- | -- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `type = "webpack"`    | ✅  | ❌  | Removed, refer to [this guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to migrate. |
-| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                  |
-| `type = "javascript"` | ✅  | 🚧  | No longer required, can be omitted.                                                             |
+| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                                                                   |
+| `type = "javascript"` | ✅  | 🚧 | No longer required, can be omitted.                                                                                                              |
 
 #### Features
 
-| Feature    | v1  | v2  | Notes                                                                                                                                                                                                 |
-| ---------- | --- | --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Feature    | v1 | v2 | Notes                                                                                                                                                                                                 |
+| ---------- | -- | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | TypeScript | ❌  | ✅  | You can give wrangler a TypeScript file, and it will automatically transpile it to JavaScript using [`esbuild`](https://github.com/evanw/esbuild) under-the-hood.                                     |
 | Local mode | ❌  | ✅  | `wrangler dev --local` will run your Worker on your local machine instead of on our network. This is powered by [Miniflare](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare/). |
diff --git a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
index 6f633bb98248e76..8092bb1422993dd 100644
--- a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
+++ b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
@@ -12,8 +12,10 @@ There are no special instructions for migrating from Wrangler v2 to v3. You shou
 
 :::caution
 
+
 If you tried to update to Wrangler v3 prior to v3.3, you may have experienced some compatibility issues with older operating systems. Please try again with the latest v3 where those have been resolved.
 
+
 :::
 
 ## Deprecations
diff --git a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
index a700b3c6cef0bbc..5c0712ab06b89e5 100644
--- a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
+++ b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
@@ -12,13 +12,7 @@ products:
   - workers
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 <Render file="wrangler-v1-deprecation" product="workers" />
 
diff --git a/src/content/docs/workflows/build/index.mdx b/src/content/docs/workflows/build/index.mdx
index d37b306c71a2e1e..317e4c6fd68d3d8 100644
--- a/src/content/docs/workflows/build/index.mdx
+++ b/src/content/docs/workflows/build/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/build/test-workflows.mdx b/src/content/docs/workflows/build/test-workflows.mdx
index 8752df04fd942ab..bf533e4a14be140 100644
--- a/src/content/docs/workflows/build/test-workflows.mdx
+++ b/src/content/docs/workflows/build/test-workflows.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 11
 products:
   - workflows
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workflows/examples/agents.mdx b/src/content/docs/workflows/examples/agents.mdx
index dabdf0389fd185b..4395885fbb20f1b 100644
--- a/src/content/docs/workflows/examples/agents.mdx
+++ b/src/content/docs/workflows/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workflows
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workflows/examples/backup-d1.mdx b/src/content/docs/workflows/examples/backup-d1.mdx
index 1ef6fc225a7cfea..a22c45b46fda50d 100644
--- a/src/content/docs/workflows/examples/backup-d1.mdx
+++ b/src/content/docs/workflows/examples/backup-d1.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Export a D1 database into R2 storage with Workflows
 products: [d1, r2]
 tags:
diff --git a/src/content/docs/workflows/examples/send-invoices.mdx b/src/content/docs/workflows/examples/send-invoices.mdx
index 88c4d7c81871595..290cf8159582787 100644
--- a/src/content/docs/workflows/examples/send-invoices.mdx
+++ b/src/content/docs/workflows/examples/send-invoices.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send invoice when shopping cart is checked out and paid for
 products: [d1, email-routing]
 tags:
diff --git a/src/content/docs/workflows/examples/twilio.mdx b/src/content/docs/workflows/examples/twilio.mdx
index 08df323ebf3258d..f9a9331974d6ad1 100644
--- a/src/content/docs/workflows/examples/twilio.mdx
+++ b/src/content/docs/workflows/examples/twilio.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Integrate Workflows with Twilio. Learn how to receive and send text messages and phone calls via APIs and Webhooks.
 products: [workers]
 pcx_content_type: example
diff --git a/src/content/docs/workflows/examples/wait-for-event.mdx b/src/content/docs/workflows/examples/wait-for-event.mdx
index 0e46962c459c1ab..95cc28394e9e6ec 100644
--- a/src/content/docs/workflows/examples/wait-for-event.mdx
+++ b/src/content/docs/workflows/examples/wait-for-event.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Implement a Cloudflare Workflow that processes user-uploaded images, awaits human approval, and performs AI-based image tagging upon approval.
 tags:
   - Typescript
@@ -12,7 +13,7 @@ products:
   - workflows
 ---
 
-import { GitHubCode, WranglerConfig } from "~/components";
+import {  GitHubCode, WranglerConfig } from "~/components"
 
 This example demonstrates how to use the `waitForEvent()` API in Cloudflare Workflows to introduce a human-in-the-loop step. The Workflow is triggered by an image upload, during which metadata is stored in a D1 database. The Workflow then waits for user approval, and upon approval, it uses Workers AI to generate image tags, which are stored in the database. An accompanying Next.js frontend application facilitates the image upload and approval process.
 
@@ -44,12 +45,12 @@ The `index.ts` file defines the core logic of the Cloudflare Workflow responsibl
 For the complete implementation of the `index.ts` file, please refer to the [GitHub repository](https://github.com/cloudflare/docs-examples/blob/main/workflows/waitForEvent/workflow/src/index.ts).
 
 <GitHubCode
-	repo="cloudflare/docs-examples"
-	file="workflows/waitForEvent/workflow/src/index.ts"
-	commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
-	lang="ts"
+  repo="cloudflare/docs-examples"
+  file="workflows/waitForEvent/workflow/src/index.ts"
+  commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
+  lang="ts"
 	lines="17-57"
-	useTypeScriptExample={true}
+  useTypeScriptExample={true}
 />
 
 ## Workflow wrangler.jsonc
diff --git a/src/content/docs/workflows/observability/index.mdx b/src/content/docs/workflows/observability/index.mdx
index 8a5a7d7938f5dfc..9fb63d677e9caec 100644
--- a/src/content/docs/workflows/observability/index.mdx
+++ b/src/content/docs/workflows/observability/index.mdx
@@ -5,11 +5,11 @@ pcx_content_type: navigation
 sidebar:
   order: 5
   group:
-    hideIndex: true
+   hideIndex: true
 products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/python/bindings.mdx b/src/content/docs/workflows/python/bindings.mdx
index a861b88223cc0f3..ea31fe2f488a996 100644
--- a/src/content/docs/workflows/python/bindings.mdx
+++ b/src/content/docs/workflows/python/bindings.mdx
@@ -153,7 +153,7 @@ class Default(WorkerEntrypoint):
 Send an event to a workflow instance.
 
 - <code>send_event(options)</code>* `type` - the type of event to send to the
-  workflow instance. \* `payload` - the payload to send to the workflow instance.
+  workflow instance. * `payload` - the payload to send to the workflow instance.
 
 ```python
 from pyodide.ffi import to_js
diff --git a/src/content/docs/workflows/reference/changelog.mdx b/src/content/docs/workflows/reference/changelog.mdx
index 00df519b89f7276..beba6e99cb7a9fe 100644
--- a/src/content/docs/workflows/reference/changelog.mdx
+++ b/src/content/docs/workflows/reference/changelog.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: changelog
-title: Release notes
+title: Release notes 
 description: Latest release notes and changes for Cloudflare Workflows.
 release_notes_file_name:
   - workflows
@@ -10,7 +10,7 @@ products:
   - workflows
 ---
 
-import { ProductReleaseNotes } from "~/components";
+import { ProductReleaseNotes } from "~/components"
 
 {/* <!-- Actual content lives in /data/changelogs/workflows.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workflows/reference/glossary.mdx b/src/content/docs/workflows/reference/glossary.mdx
index c6bc3d0908b0a9d..e19733552053c95 100644
--- a/src/content/docs/workflows/reference/glossary.mdx
+++ b/src/content/docs/workflows/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Workflows documentation.
 
diff --git a/src/content/docs/workflows/reference/index.mdx b/src/content/docs/workflows/reference/index.mdx
index 6df95f6daddcdc4..89abc260ef45793 100644
--- a/src/content/docs/workflows/reference/index.mdx
+++ b/src/content/docs/workflows/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/reference/pricing.mdx b/src/content/docs/workflows/reference/pricing.mdx
index 283b87cdbd8653d..db0a2a5aa7c5f2e 100644
--- a/src/content/docs/workflows/reference/pricing.mdx
+++ b/src/content/docs/workflows/reference/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 :::note
 
@@ -18,19 +18,19 @@ Workflows is included in both the Free and Paid [Workers plans](/workers/platfor
 
 Workflows pricing is identical to [Workers Standard pricing](/workers/platform/pricing/#workers) and are billed on three dimensions:
 
-- **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
-- **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
-- **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
+* **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
+* **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
+* **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
 
 A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle, does not incur CPU time.
 
 ### Workflows Pricing
 
-| Unit                | Workers Free                                                                        | Workers Paid                                                                                   |
-| ------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers) | 10 million included per month + $0.30 per additional million                                   |
-| CPU time (ms)       | 10 milliseconds of CPU time per invocation                                          | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
-| Storage (GB-mo)     | 1GB                                                                                 | 1GB included per month + $0.20/ GB-month                                                       |
+| Unit | Workers Free | Workers Paid |
+|------|--------------|--------------|
+| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers)| 10 million included per month + $0.30 per additional million	|
+| CPU time (ms) | 10 milliseconds of CPU time per invocation | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
+| Storage (GB-mo) | 1GB | 1GB included per month + $0.20/ GB-month |
 
 :::note[CPU limits]
 
@@ -48,10 +48,10 @@ Storage billing for Workflows will go live on September 15th, 2025.
 
 Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to [Durable Objects SQL storage](/durable-objects/platform/pricing/#sqlite-storage-backend). A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).
 
-- Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
-- By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
-- When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
-- Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
+* Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
+* By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
+* When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
+* Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
 
 An instance that attempts to store state when your have reached the storage limit on the Free plan will cause an error to be thrown.
 
diff --git a/src/content/docs/workflows/reference/wrangler-commands.mdx b/src/content/docs/workflows/reference/wrangler-commands.mdx
index 2ad49f1ed36f4a1..b80050771f16411 100644
--- a/src/content/docs/workflows/reference/wrangler-commands.mdx
+++ b/src/content/docs/workflows/reference/wrangler-commands.mdx
@@ -8,6 +8,6 @@ products:
   - workflows
 ---
 
-import { WranglerNamespace } from "~/components";
+import {WranglerNamespace} from "~/components";
 
-<WranglerNamespace namespace="workflows" />
+<WranglerNamespace namespace="workflows"/>
diff --git a/src/content/docs/workflows/videos.mdx b/src/content/docs/workflows/videos.mdx
index 8d5a6926d7c97fa..0b45561d7cdf80d 100644
--- a/src/content/docs/workflows/videos.mdx
+++ b/src/content/docs/workflows/videos.mdx
@@ -11,9 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Build an application using Cloudflare Workflows"
-		description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
-		href="/learning-paths/workflows-course/series/workflows-1/"
-	/>
+    <LinkCard
+        title="Build an application using Cloudflare Workflows"
+        description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
+        href="/learning-paths/workflows-course/series/workflows-1/"
+    />
 </CardGrid>
diff --git a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
index e537c733bce84dd..07719d8b84e7244 100644
--- a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
+++ b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
@@ -6,6 +6,7 @@ products:
 title: Data layer compatibility mode
 sidebar:
   order: 3
+
 ---
 
 Cloudflare Zaraz offers backwards compatibility with the `dataLayer` function found in tag management software, used to track events and other parameters. This way you can keep your current implementation and Cloudflare Zaraz will automatically collect your events.
@@ -27,10 +28,10 @@ Events will only be sent to Zaraz if your pushed object includes an `event` key.
 
 ```js
 dataLayer.push({
-	event: "purchase",
-	price: "24",
-	currency: "USD",
-	transactionID: "12345678",
+  event: 'purchase',
+  price: '24',
+  currency: 'USD',
+  transactionID: '12345678',
 });
 ```
 
@@ -40,6 +41,6 @@ Because Zaraz converts the `dataLayer.push()` call to `zaraz.track()`, creating
 
 | Rule type    | Variable name | Match operation | Match string |
 | ------------ | ------------- | --------------- | ------------ |
-| _Match rule_ | _Event Name_  | _Equals_        | `purchase`   |
+| *Match rule* | *Event Name*  | *Equals*        | `purchase`   |
 
 We do not recommend using `dataLayer`. However, as many websites employ it, Cloudflare Zaraz has this automatic translation layer that converts it to `zaraz.track()`.
diff --git a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
index 359716b4e8520a1..571d8120641dd8c 100644
--- a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
+++ b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Use Zaraz on domains not proxied by Cloudflare
+
 ---
 
 You can load Zaraz on domains that are not proxied through Cloudflare. However, you will need to create a separate domain, or subdomain, proxied by Cloudflare (also [known as orange-clouded](https://community.cloudflare.com/t/step-3-enabling-the-orange-cloud/52715) domains), and load the script from it:
diff --git a/src/content/docs/zaraz/advanced/google-consent-mode.mdx b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
index 730a6cf363a3bba..32b7951c7c0b104 100644
--- a/src/content/docs/zaraz/advanced/google-consent-mode.mdx
+++ b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
@@ -6,6 +6,7 @@ products:
 title: Google Consent Mode
 sidebar:
   order: 4
+
 ---
 
 ## Background
@@ -14,7 +15,7 @@ sidebar:
 
 You can also use Google Analytics and Google Ads without cookies by selecting **Permissions** and disabling **Access client key-value store**.
 
----
+***
 
 ## Consent Mode v2
 
@@ -27,12 +28,12 @@ Often websites will want to set a default consent status that denies all categor
 If that is not what your website needs, and instead you want to set the default consent status in a more granular way, use the reserved `google_consent_default` property:
 
 ```js
-zaraz.set("google_consent_default", {
-	ad_storage: "denied",
-	ad_user_data: "denied",
-	ad_personalization: "denied",
-	analytics_storage: "denied",
-});
+zaraz.set("google_consent_default",  {
+  'ad_storage': 'denied',
+  'ad_user_data': 'denied',
+  'ad_personalization': 'denied',
+  'analytics_storage': 'denied'
+})
 ```
 
 After the above code is executed, the consent status will be saved to `localStorage` and will be included with every subsequent Zaraz event.
@@ -44,12 +45,12 @@ Note that the code should be included as part of your website HTML code, usually
 After the user has provided their consent preferences you can set the new status using the reserved `google_consent_update` property. If you are using the Zaraz Consent Management Platform, you can use the [Consent Choices Updated event](/zaraz/consent-management/api/#consent-choices-updated) to know when to update the Google Consent status.
 
 ```js
-zaraz.set("google_consent_update", {
-	ad_storage: "granted",
-	ad_user_data: "denied",
-	ad_personalization: "granted",
-	analytics_storage: "denied",
-});
+zaraz.set("google_consent_update",  {
+  'ad_storage': 'granted',
+  'ad_user_data': 'denied',
+  'ad_personalization': 'granted',
+  'analytics_storage': 'denied'
+})
 ```
 
 All subsequent events will include the information about both the default and the updated consent status.
diff --git a/src/content/docs/zaraz/advanced/import-export.mdx b/src/content/docs/zaraz/advanced/import-export.mdx
index 578d82719d2e9dc..450eddcbc977e9a 100644
--- a/src/content/docs/zaraz/advanced/import-export.mdx
+++ b/src/content/docs/zaraz/advanced/import-export.mdx
@@ -6,6 +6,7 @@ products:
 title: Configuration Import & Export
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To export your Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Advanced**.
 3. Click "Export" to download your configuration.
 
@@ -27,15 +27,16 @@ To export your Zaraz configuration:
 
 :::caution
 
+
 Importing a Zaraz configuration replaces your existing configuration, meaning that any information you did not back up could be lost. Consider exporting your existing configuration before importing a new one.
 
+
 :::
 
 To import a Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Advanced**.
 3. Click **Browse** to select your configuration file, and **Import** to import it.
diff --git a/src/content/docs/zaraz/advanced/index.mdx b/src/content/docs/zaraz/advanced/index.mdx
index 1b0c3fd82039d96..9b8a538527e1ac3 100644
--- a/src/content/docs/zaraz/advanced/index.mdx
+++ b/src/content/docs/zaraz/advanced/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Advanced options
 sidebar:
   order: 7
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
index 568da28f0043abf..7e825c97731546d 100644
--- a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
+++ b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
@@ -60,8 +60,7 @@ As with regular tools, it is recommended that you [create the triggers](/zaraz/c
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > [**Third-party tools**](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/tools-config/tools/catalog).
 3. Select **Add new tool** and choose **Custom Managed Component** from the tools library page. Select **Continue** to confirm your selection.
 4. In **Select Custom MC**, choose a Custom Managed Component that you have deployed to your account, such as `custom-mc-my-new-counter-mc`. Select **Continue**.
diff --git a/src/content/docs/zaraz/advanced/load-selectively.mdx b/src/content/docs/zaraz/advanced/load-selectively.mdx
index 1d02673007eda4d..f9384c91755a2cc 100644
--- a/src/content/docs/zaraz/advanced/load-selectively.mdx
+++ b/src/content/docs/zaraz/advanced/load-selectively.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Zaraz selectively
 sidebar:
   order: 1
+
 ---
 
 You can use [Configuration Rules](/rules/configuration-rules/) to load Zaraz selectively on specific URLs or subdomains. Configuration Rules can also be used to block Zaraz from loading based on cookies, IP addresses or anything else related to a request.
@@ -14,6 +15,8 @@ Refer to [Configuration Rules](/rules/configuration-rules/) documentation to lea
 
 :::note
 
+
 If you need to block one or more actions from firing in a tool, Cloudflare recommends you use [Blocking Triggers](/zaraz/advanced/blocking-triggers/) instead of Configuration Rules.
 
+
 :::
diff --git a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
index ce72a802d046457..d8ca835447f24d1 100644
--- a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
+++ b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Zaraz manually
 sidebar:
   order: 5
+
 ---
 
 By default, if your domain is proxied by Cloudflare, Zaraz will automatically inject itself to HTML pages in your site. This makes it easier to get up and running quickly. However, you might want to load Zaraz manually, for example to test Zaraz on specific pages first.
@@ -20,13 +21,13 @@ With the script, your page HTML should be similar to the following:
 
 ```html
 <html>
-	<head>
-		….
-		<script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
-	</head>
-	<body>
-		…
-	</body>
+  <head>
+    ….
+    <script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
+  </head>
+  <body>
+    …
+  </body>
 </html>
 ```
 
diff --git a/src/content/docs/zaraz/advanced/using-jsonata.mdx b/src/content/docs/zaraz/advanced/using-jsonata.mdx
index 82292524bfe52e4..925c0718866321c 100644
--- a/src/content/docs/zaraz/advanced/using-jsonata.mdx
+++ b/src/content/docs/zaraz/advanced/using-jsonata.mdx
@@ -6,6 +6,7 @@ products:
 title: Using JSONata
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To use JSONata inside Zaraz, follow these steps:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Tools configuration** > **Tools**.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -38,22 +38,23 @@ Converting a string to lowercase is useful if you want to compare it to somethin
 Assuming you are using `zaraz.ecommerce()` to send the cart content like this:
 
 ```js
-zaraz.track("Product List Viewed", {
-	products: [
-		{
-			sku: "2671033",
-			name: "V-neck T-shirt",
-			price: 14.99,
-			quantity: 3,
-		},
-		{
-			sku: "2671034",
-			name: "T-shirt",
-			price: 10.99,
-			quantity: 2,
-		},
-	],
-});
+zaraz.track('Product List Viewed',
+  {  products:
+    [
+    {
+      sku: '2671033',
+      name: 'V-neck T-shirt',
+      price: 14.99,
+      quantity: 3
+    },{
+      sku: '2671034',
+      name: 'T-shirt',
+      price: 10.99,
+      quantity: 2
+    },
+    ],
+  }
+);
 ```
 
 If the field in which you want to show the sum, you will enter `{{ $sum(client.products.(price * quantity)) }}`. This will multiply the price of each product by its quantity, and then sum up the total.
diff --git a/src/content/docs/zaraz/consent-management/api.mdx b/src/content/docs/zaraz/consent-management/api.mdx
index cfbaa929889d835..b6feadf8eef42a1 100644
--- a/src/content/docs/zaraz/consent-management/api.mdx
+++ b/src/content/docs/zaraz/consent-management/api.mdx
@@ -6,6 +6,7 @@ products:
 title: Consent API
 sidebar:
   order: 3
+
 ---
 
 ## Background
@@ -14,7 +15,7 @@ The Consent API allows you to programmatically control all aspects of the Consen
 
 Using the Consent API, you can integrate Zaraz Consent preferences with an external Consent Management Platform, customize your consent modal, or restrict consent management to users in specific regions.
 
----
+***
 
 ## Events
 
@@ -24,8 +25,9 @@ It can be useful to know when the Consent API is fully loaded on the page so tha
 
 ```js
 document.addEventListener("zarazConsentAPIReady", () => {
-	// do things with the Consent API
+  // do things with the Consent API
 });
+
 ```
 
 ### `Consent Choices Updated`
@@ -34,26 +36,34 @@ This event is fired every time the user makes changes to their consent preferenc
 
 ```js
 document.addEventListener("zarazConsentChoicesUpdated", () => {
-	// read the new consent preferences using `zaraz.consent.getAll();` and do things with it
+  // read the new consent preferences using `zaraz.consent.getAll();` and do things with it
 });
+
 ```
 
----
+***
 
 ## Properties
 
 The following are properties of the `zaraz.consent` object.
 
-- `modal` boolean
-  - Get or set the current visibility status of the consent modal dialog.
 
-- `purposes` object read-only
-  - An object containing all configured purposes, with their ID, name, description, and order.
 
-- `APIReady` boolean read-only
-  - Indicates whether the Consent API is currently available on the page.
+* `modal` boolean
 
----
+  * Get or set the current visibility status of the consent modal dialog.
+
+* `purposes` object read-only
+
+  * An object containing all configured purposes, with their ID, name, description, and order.
+
+* `APIReady` boolean read-only
+
+  * Indicates whether the Consent API is currently available on the page.
+
+
+
+***
 
 ## Methods
 
@@ -63,18 +73,27 @@ The following are properties of the `zaraz.consent` object.
 zaraz.consent.get(purposeId);
 ```
 
-- <code>get(purposeId)</code> : `boolean | undefined`
+
+
+* <code>get(purposeId)</code> : `boolean | undefined`
+
+
 
 Get the current consent status for a purpose using the purpose ID.
 
-- `true`: The consent was granted.
-- `false`: The consent was not granted.
-- `undefined`: The purpose does not exist.
+* `true`: The consent was granted.
+* `false`: The consent was not granted.
+* `undefined`: The purpose does not exist.
 
 #### Parameters
 
-- `purposeId` string
-  - The ID representing the Purpose.
+
+
+* `purposeId` string
+
+  * The ID representing the Purpose.
+
+
 
 ### `Set`
 
@@ -82,14 +101,23 @@ Get the current consent status for a purpose using the purpose ID.
 zaraz.consent.set(consentPreferences);
 ```
 
-- <code>set(consentPreferences)</code> : `undefined`
+
+
+* <code>set(consentPreferences)</code> : `undefined`
+
+
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-- `consentPreferences` object
-  - a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
+
+
+* `consentPreferences` object
+
+  * a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
+
+
 
 ### `Get All`
 
@@ -97,7 +125,11 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.getAll();
 ```
 
-- <code>getAll()</code> : `{ purposeId: boolean }`
+
+
+* <code>getAll()</code> : `{ purposeId: boolean }`
+
+
 
 Returns an object with the consent status of all purposes.
 
@@ -107,14 +139,23 @@ Returns an object with the consent status of all purposes.
 zaraz.consent.setAll(consentStatus);
 ```
 
-- <code>setAll(consentStatus)</code> : `undefined`
+
+
+* <code>setAll(consentStatus)</code> : `undefined`
+
+
 
 Set the consent status for all purposes at once.
 
 #### Parameters
 
-- `consentStatus` boolean
-  - Indicates whether the consent was granted or not.
+
+
+* `consentStatus` boolean
+
+  * Indicates whether the consent was granted or not.
+
+
 
 ### `Get All Checkboxes`
 
@@ -122,7 +163,11 @@ Set the consent status for all purposes at once.
 zaraz.consent.getAllCheckboxes();
 ```
 
-- <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
+
+
+* <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
+
+
 
 Returns an object with the checkbox status of all purposes.
 
@@ -132,14 +177,23 @@ Returns an object with the checkbox status of all purposes.
 zaraz.consent.setCheckboxes(checkboxesStatus);
 ```
 
-- <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
+
+
+* <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
+
+
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-- `checkboxesStatus` object
-  - a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
+
+
+* `checkboxesStatus` object
+
+  * a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
+
+
 
 ### `Set All Checkboxes`
 
@@ -147,14 +201,23 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.setAllCheckboxes(checkboxStatus);
 ```
 
-- <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
+
+
+* <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
+
+
 
 Set the `checkboxStatus` status for all purposes in the consent modal at once.
 
 #### Parameters
 
-- `checkboxStatus` boolean
-  - Indicates whether the purposes should be marked as checked or not.
+
+
+* `checkboxStatus` boolean
+
+  * Indicates whether the purposes should be marked as checked or not.
+
+
 
 ### `Send queued events`
 
@@ -162,7 +225,11 @@ Set the `checkboxStatus` status for all purposes in the consent modal at once.
 zaraz.consent.sendQueuedEvents();
 ```
 
-- <code>sendQueuedEvents()</code> : `undefined`
+
+
+* <code>sendQueuedEvents()</code> : `undefined`
+
+
 
 If some Pageview-based events were not sent due to a lack of consent, they can be sent using this method after consent was granted.
 
@@ -174,35 +241,32 @@ You can combine multiple features of Zaraz to effectively disable Consent Manage
 
 ```html
 <script>
-	function getCookie(name) {
-		const value = `; ${document.cookie}`;
-		return value?.split(`; ${name}=`)[1]?.split(";")[0];
-	}
-
-	function handleZarazConsentAPIReady() {
-		const consent_cookie = getCookie("cf_consent");
-		const isEUCountry = "{{system.device.location.isEUCountry}}" === "1";
-		if (!consent_cookie) {
-			if (isEUCountry) {
-				zaraz.consent.modal = true;
-			} else {
-				zaraz.consent.setAll(true);
-				zaraz.consent.sendQueuedEvents();
-			}
-		}
-	}
-
-	if (zaraz.consent?.APIReady) {
-		handleZarazConsentAPIReady();
-	} else {
-		document.addEventListener(
-			"zarazConsentAPIReady",
-			handleZarazConsentAPIReady,
-		);
-	}
+function getCookie(name) {
+  const value = `; ${document.cookie}`
+  return value?.split(`; ${name}=`)[1]?.split(";")[0]
+}
+
+function handleZarazConsentAPIReady() {
+  const consent_cookie = getCookie("cf_consent")
+  const isEUCountry = "{{system.device.location.isEUCountry}}" === "1"
+  if (!consent_cookie) {
+    if (isEUCountry) {
+      zaraz.consent.modal = true
+    } else {
+      zaraz.consent.setAll(true)
+      zaraz.consent.sendQueuedEvents()
+    }
+  }
+}
+
+if (zaraz.consent?.APIReady) {
+  handleZarazConsentAPIReady()
+} else {
+  document.addEventListener("zarazConsentAPIReady", handleZarazConsentAPIReady)
+}
 </script>
 ```
 
-Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf_consent" in the snippet above.
+Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf\_consent"  in the snippet above.
 
 By letting this Custom HTML tool to run without consent requirements, the modal will appear to all EU visitors, while for other visitors consent will be automatically granted. The `{{ system.device.location.isEUCountry }}` property will be `1` if the visitor is from an EU country and `0` otherwise. You can use any other property or variable to customize the Consent Management behavior in a similar manner, such as `{{ system.device.location.country }}` to restrict consent checks based on country code.
diff --git a/src/content/docs/zaraz/consent-management/custom-css.mdx b/src/content/docs/zaraz/consent-management/custom-css.mdx
index 7827dbae8fb4745..719f2839cf27872 100644
--- a/src/content/docs/zaraz/consent-management/custom-css.mdx
+++ b/src/content/docs/zaraz/consent-management/custom-css.mdx
@@ -6,6 +6,7 @@ products:
 title: Custom CSS
 sidebar:
   order: 2
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,5 @@ You can add custom CSS to the Zaraz Consent Management Platform, to make the con
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Find the **Custom CSS** section, and add your custom CSS code as you would on any other HTML editor.
diff --git a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
index 1a442cb85828653..39e50481db06ef5 100644
--- a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
+++ b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable the Consent Management platform (CMP)
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Turn on **Enable Consent Management**.
 3. In **Consent modal text** fill in any legal information required in your country. Use HTML code to format your information as you would in any other HTML editor.
 4. Under **Purposes**, select **Add new Purpose**. Give your new purpose a name and a description. Purposes are the reasons for using third-party tools in your website.
@@ -31,8 +31,7 @@ In your Zaraz consent settings, you can add your consent modal text and purposes
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Select a default language of your choice. The default setting is English.
 3. In **Consent modal text** and **Purposes**, you can select different languages and add translations.
 
@@ -45,7 +44,7 @@ Below is an example that forces the language shown to be American English.
 
 ```html
 <script>
-	zaraz.set("__zarazConsentLanguage", "en-US");
+  zaraz.set('__zarazConsentLanguage', 'en-US')
 </script>
 ```
 
diff --git a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
index 57e58eba4bb79c1..0ab62c99c732fa1 100644
--- a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
+++ b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: IAB Transparency & Consent Framework Compliance
+
 ---
 
 import { DashButton } from "~/components";
@@ -21,8 +22,7 @@ Using the Zaraz Consent Management Platform in IAB TCF Compliance Mode is is opt
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Check the **Use IAB TCF compliant modal** option.
 3. Under the **Assign purposes to tools** section, add vendor details to every tool that was not automatically assigned.
 4. Press **Save**.
diff --git a/src/content/docs/zaraz/consent-management/index.mdx b/src/content/docs/zaraz/consent-management/index.mdx
index 577214eacbb7f26..57e7e5e3a28277f 100644
--- a/src/content/docs/zaraz/consent-management/index.mdx
+++ b/src/content/docs/zaraz/consent-management/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Zaraz Consent Management platform
+
 ---
 
-Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
+Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219\&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
 
 The consent modal added to your website is concise and gives your users an easy way to opt-in to any purposes of data processing your tools need.
 
@@ -21,12 +22,12 @@ The consent modal added to your website is concise and gives your users an easy
 
 The Zaraz Consent Management platform (CMP) has a **Purposes** section. This is where you will have to create purposes for the third-party tools your website uses. To better understand the terms involved in dealing with personal data, refer to these definitions:
 
-- **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
-- **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
+* **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
+* **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
 
 :::note
 
-All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in.
+All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in. 
 :::
 
 ## Purposes and tools
@@ -35,19 +36,19 @@ When you add a new tool to your website, Zaraz does not assign any purpose to it
 
 The user’s consent preferences are stored within a first-party cookie. This cookie is a JSON file that maps the purposes’ ID to a `true`/`false`/missing value:
 
-- `true` value: The user gave consent.
-- `false`value: The user refused consent.
-- Missing value: The user has not made a choice yet.
+* `true` value: The user gave consent.
+* `false`value: The user refused consent.
+* Missing value: The user has not made a choice yet.
 
 :::caution[Important]
 
-Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR.
+Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR. 
 :::
 
 ## Important things to note
 
-- Purposes that have no tools assigned will not show up in the CMP modal.
-- If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
-- Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
-- If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
-- On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
+* Purposes that have no tools assigned will not show up in the CMP modal.
+* If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
+* Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
+* If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
+* On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
diff --git a/src/content/docs/zaraz/custom-actions/additional-fields.mdx b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
index f0bf936140a3a71..76436e214d13c6c 100644
--- a/src/content/docs/zaraz/custom-actions/additional-fields.mdx
+++ b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
@@ -6,6 +6,7 @@ products:
 title: Additional fields
 sidebar:
   order: 5
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ Adding an additional field to an action will attach it to this action only, and
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool with the action you want to add the additional field to, and select **Edit**.
 4. Select the action you wish to modify.
@@ -36,8 +36,7 @@ Adding an additional field to the tool sets it as a default field for all of the
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool where you want to add the field, and select **Edit**.
 4. Select **Settings** > **Add Field**.
diff --git a/src/content/docs/zaraz/custom-actions/create-action.mdx b/src/content/docs/zaraz/custom-actions/create-action.mdx
index fbb05627895c834..7d01b943b05425e 100644
--- a/src/content/docs/zaraz/custom-actions/create-action.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-action.mdx
@@ -16,8 +16,7 @@ To create an action, first [add a third-party tool](/zaraz/get-started/). If you
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate the tool you want to configure an action for, and select **Edit**.
 4. Under Custom actions select **Create action**.
diff --git a/src/content/docs/zaraz/custom-actions/create-trigger.mdx b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
index 200485ee7f7263e..7d7d8c141b3ade7 100644
--- a/src/content/docs/zaraz/custom-actions/create-trigger.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
@@ -14,8 +14,7 @@ Triggers define the conditions under which a tool will start an action. Since a
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Select the **Triggers** tab.
 4. Select **Create trigger**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
index 8e83ceeaf6c5a71..38a7dae5ee8f9a5 100644
--- a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
@@ -6,14 +6,14 @@ products:
 title: Edit tools and actions
 sidebar:
   order: 6
----
 
+---
 import { DashButton } from "~/components";
 
-1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
+1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools**.
 3. Under **Third-party tools**, locate your tool and select **Edit**.
 
@@ -23,8 +23,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select the **Enabled** toggle.
 
@@ -32,8 +31,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate the tool you wan to edit and select **Edit**.
 4. Find the action you want to change state, and enable or disable it with the toggle.
@@ -42,7 +40,6 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select **Delete**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
index 23abf7eee383799..2e9e13f08691d48 100644
--- a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a trigger
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Edit**.
 
@@ -26,7 +26,6 @@ You can edit every field related to the trigger, as well as add new trigger rule
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Delete**.
diff --git a/src/content/docs/zaraz/embeds.mdx b/src/content/docs/zaraz/embeds.mdx
index 72ce24521d03833..d2a6e58612bd5d4 100644
--- a/src/content/docs/zaraz/embeds.mdx
+++ b/src/content/docs/zaraz/embeds.mdx
@@ -6,6 +6,7 @@ products:
 title: Embeds
 sidebar:
   order: 6
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To add an Embed to Your Website:
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Click "add new tool" and activate the desired tools on your Cloudflare Zaraz dashboard.
 4. Add a placeholder in your HTML, specifying the necessary attributes. For a generic embed, the snippet looks like this:
@@ -43,10 +43,7 @@ Replace `tweet-id` with the actual tweet ID for the content you wish to embed.
 ### Instagram embed
 
 ```html
-<instagram-post
-	post-url="https://www.instagram.com/p/ABC/"
-	captions="true"
-></instagram-post>
+<instagram-post post-url="https://www.instagram.com/p/ABC/" captions="true"></instagram-post>
 ```
 
 Replace `post-url` with the actual URL for the content you wish to embed. To include posts captions set captions attribute to `true`.
diff --git a/src/content/docs/zaraz/get-started.mdx b/src/content/docs/zaraz/get-started.mdx
index 69973cb72ac66dc..682f7f02cc686a6 100644
--- a/src/content/docs/zaraz/get-started.mdx
+++ b/src/content/docs/zaraz/get-started.mdx
@@ -18,8 +18,7 @@ You can add new third-party tools and load them into your website through the Cl
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. If you have already added a tool before, select **Third-party tools** and click on **Add new tool**.
 3. Choose a tool from the tools catalog. Select **Continue** to confirm your selection.
 4. In **Set up**, configure the settings for your new tool. The information you need to enter will depend on the tool you choose. If you want to use any dynamic properties or variables, select the `+` sign in the drop-down menu next to the relevant field.
diff --git a/src/content/docs/zaraz/history/index.mdx b/src/content/docs/zaraz/history/index.mdx
index 98f0e09c733046c..a86038b87af35fc 100644
--- a/src/content/docs/zaraz/history/index.mdx
+++ b/src/content/docs/zaraz/history/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Versions & History
 sidebar:
   order: 8
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Zaraz can work in real-time. In this mode, every change you make is instantly published. You can also enable [Preview & Publish mode](/zaraz/history/preview-mode/), which allows you to test your changes before you commit to them.
 
diff --git a/src/content/docs/zaraz/history/versions.mdx b/src/content/docs/zaraz/history/versions.mdx
index d5c71f8201e3f9d..0ee58afc9464854 100644
--- a/src/content/docs/zaraz/history/versions.mdx
+++ b/src/content/docs/zaraz/history/versions.mdx
@@ -6,10 +6,12 @@ products:
 title: Versions
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
 
+
 Version History enables you to keep track of all the Zaraz configuration changes made in your website. With Version History you can also revert changes to previous settings should there be a problem.
 
 To access Version History you need to enable [Preview & Publish mode](/zaraz/history/preview-mode/) first. Then, you can access Version History under **Zaraz** > **History**.
@@ -18,12 +20,11 @@ To access Version History you need to enable [Preview & Publish mode](/zaraz/his
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-   <DashButton url="/?to=/:account/tag-management/history" />
-
-2. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
-   - Date of change
-   - User who made the change
-   - Description of the change
+	<DashButton url="/?to=/:account/tag-management/history" />
+3. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
+   * Date of change
+   * User who made the change
+   * Description of the change
 
 ## Revert changes
 
@@ -31,8 +32,7 @@ Version History enables you to revert any changes made to your Zaraz settings.
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-   <DashButton url="/?to=/:account/tag-management/history" />
-
+	<DashButton url="/?to=/:account/tag-management/history" />
 2. Find the changes you want to revert, and select **Restore**.
 3. Confirm you want to revert your changes.
 4. Select **Publish** to publish your changes.
diff --git a/src/content/docs/zaraz/http-events-api.mdx b/src/content/docs/zaraz/http-events-api.mdx
index a4e94957e49f0cd..657a00899b82342 100644
--- a/src/content/docs/zaraz/http-events-api.mdx
+++ b/src/content/docs/zaraz/http-events-api.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: HTTP Events API
+
 ---
 
 import { DashButton } from "~/components";
@@ -23,8 +24,7 @@ To enable the API endpoint:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Under **Endpoints** > **HTTP Events API**, set your desired path. Remember the path is relative to your domain, and it must start with a `/`.
 
 :::caution[Important]
@@ -37,25 +37,25 @@ The endpoint you have configured for the API will receive `POST` requests with a
 
 ```json
 {
-	"events": [
-		{
-			"client": {
-				"__zarazTrack": "transaction successful",
-				"value": "200"
-			}
-		}
-	]
+  "events": [
+    {
+      "client": {
+        "__zarazTrack": "transaction successful",
+        "value": "200"
+      }
+    }
+  ]
 }
 ```
 
 The payload must contain an `events` array. Each Event Object in this array corresponds to one event you want Zaraz to process. The above example is similar to calling `zaraz.track('transaction successful', { value: "200" })` using the Web API.
 
-The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a _Track Property_ in the Zaraz dashboard.
+The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a *Track Property* in the Zaraz dashboard.
 
 There are two reserved keys:
 
-- `__zarazTrack`: The value of this key will be available as _Event Name_. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
-- `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
+* `__zarazTrack`: The value of this key will be available as *Event Name*. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
+* `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
 
 ### The `system` key
 
@@ -65,41 +65,41 @@ The same payload from before will resemble the following example, when we add th
 
 ```json
 {
-	"events": [
-		{
-			"client": {
-				"__zarazTrack": "transaction successful",
-				"value": "200"
-			},
-			"system": {
-				"page": {
-					"url": "https://example.com",
-					"title": "My website"
-				},
-				"device": {
-					"language": "en-US",
-					"ip": "192.168.0.1"
-				}
-			}
-		}
-	]
+  "events": [
+    {
+      "client": {
+        "__zarazTrack": "transaction successful",
+        "value": "200"
+      },
+      "system": {
+        "page": {
+          "url": "https://example.com",
+          "title": "My website"
+        },
+        "device": {
+          "language": "en-US",
+          "ip": "192.168.0.1"
+        }
+      }
+    }
+  ]
 }
 ```
 
 For all available system keys, refer to the table below:
 
-| Property                   | Type   | Description                                                                                |
-| -------------------------- | ------ | ------------------------------------------------------------------------------------------ |
-| `system.cookies`           | Object | A key-value object holding cookies from the device associated with the event.              |
-| `system.device.ip`         | String | The IP address of the device associated with the event.                                    |
-| `system.device.resolution` | String | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
-| `system.device.viewport`   | String | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
-| `system.device.language`   | String | The language code used by the device associated with the event.                            |
-| `system.device.user-agent` | String | The `User-Agent` string of the device associated with the event.                           |
-| `system.page.title`        | String | The title of the page associated with the event.                                           |
-| `system.page.url`          | String | The URL of the page associated with the event.                                             |
-| `system.page.referrer`     | String | The URL of the referrer page in the time the event took place.                             |
-| `system.page.encoding`     | String | The encoding of the page associated with the event.                                        |
+| Property                   | Type  | Description                                                                                |
+| -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------ |
+| `system.cookies`           | Object                         | A key-value object holding cookies from the device associated with the event.              |
+| `system.device.ip`         | String                         | The IP address of the device associated with the event.                                    |
+| `system.device.resolution` | String                         | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
+| `system.device.viewport`   | String                         | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
+| `system.device.language`   | String                         | The language code used by the device associated with the event.                            |
+| `system.device.user-agent` | String                         | The `User-Agent` string of the device associated with the event.                           |
+| `system.page.title`        | String                         | The title of the page associated with the event.                                           |
+| `system.page.url`          | String                         | The URL of the page associated with the event.                                             |
+| `system.page.referrer`     | String                         | The URL of the referrer page in the time the event took place.                             |
+| `system.page.encoding`     | String                         | The encoding of the page associated with the event.                                        |
 
 :::note
 
@@ -112,11 +112,11 @@ For each Event Object in your payload, Zaraz will respond with a Result Object.
 
 Depending on what tools you are loading using Zaraz, the body of the response coming from the API might include information you will want to process. This is because some tools do not have a complete server-side implementation and still depend on cookies, client-side JavaScript or similar mechanisms. Each Result Object can include the following information:
 
-| Result key | Description                                                     |
-| ---------- | --------------------------------------------------------------- |
-| `fetch`    | Fetch requests that tools want to send from the user browser.   |
-| `execute`  | JavaScript code that tools want to execute in the user browser. |
-| `return`   | Information that tools return.                                  |
-| `cookies`  | Cookies that tools want to set for the user.                    |
+| Result key | Description |
+| --- | --- |
+| `fetch` | Fetch requests that tools want to send from the user browser. |
+| `execute` | JavaScript code that tools want to execute in the user browser. |
+| `return` | Information that tools return. |
+| `cookies` | Cookies that tools want to set for the user. |
 
 You do not have to process the information above, but some tools might depend on this to work properly. You can start using the HTTP Events API without processing the information in the table above, and adjust accordingly later.
diff --git a/src/content/docs/zaraz/monitoring/index.mdx b/src/content/docs/zaraz/monitoring/index.mdx
index 89a3c69828ab590..7d60ca7c1291ea9 100644
--- a/src/content/docs/zaraz/monitoring/index.mdx
+++ b/src/content/docs/zaraz/monitoring/index.mdx
@@ -18,9 +18,8 @@ To use Zaraz Monitoring:
 
 1. In the Cloudflare dashboard, go to the **Monitoring** page.
 
-   <DashButton url="/?to=/:account/tag-management/monitoring" />
-
-2. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
+	<DashButton url="/?to=/:account/tag-management/monitoring" />
+3. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
 
 ## Zaraz Monitoring options
 
diff --git a/src/content/docs/zaraz/pricing-info.mdx b/src/content/docs/zaraz/pricing-info.mdx
index 1ca41a948098035..dca9b6076413d78 100644
--- a/src/content/docs/zaraz/pricing-info.mdx
+++ b/src/content/docs/zaraz/pricing-info.mdx
@@ -6,6 +6,7 @@ products:
 title: Pricing
 sidebar:
   order: 15
+
 ---
 
 import { DashButton } from "~/components";
@@ -17,15 +18,13 @@ All Zaraz features and tools are always available on all accounts. Learn more ab
 ## The Zaraz Event unit
 
 One Zaraz Event is an event you are sending to Zaraz, whether that is a page view, a `zaraz.track` event, or similar. You can easily see the total number of Zaraz Events you are currently using on the **Monitoring** page of the Cloudflare dashboard:
-
-<DashButton url="/?to=/:account/tag-management/monitoring" />
+   <DashButton url="/?to=/:account/tag-management/monitoring" />
 
 ## Enabling Zaraz Paid
 
 1. In the Cloudflare dashboard, go to the **Zaraz plans** page.
 
-   <DashButton url="/?to=/:account/tag-management/plans" />
-
+	<DashButton url="/?to=/:account/tag-management/plans" />
 2. Click the **Enable Zaraz usage billing** button and follow the instructions.
 
 ## Using Zaraz Free
diff --git a/src/content/docs/zaraz/reference/context.mdx b/src/content/docs/zaraz/reference/context.mdx
index 6f7df19926f9b1a..bda539074da4906 100644
--- a/src/content/docs/zaraz/reference/context.mdx
+++ b/src/content/docs/zaraz/reference/context.mdx
@@ -6,6 +6,7 @@ products:
 title: Zaraz Context
 sidebar:
   order: 10
+
 ---
 
 The Zaraz Context is a versatile object that provides a set of configurable properties for Zaraz, a web analytics tool for tracking user behavior on websites. These properties can be accessed and utilized across various components, including [Worker Variables](/zaraz/variables/worker-variables/) and [JSONata expressions](/zaraz/advanced/using-jsonata/).
@@ -16,6 +17,8 @@ System properties, which are automatically collected by Zaraz, provide insights
 
 ### Page information
 
+
+
 | Property               | Type   | Description                                                                                                     |
 | ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------- |
 | `system.page.query`    | Object | Key-Value object containing all query parameters in the current URL.                                            |
@@ -35,6 +38,8 @@ The keys inside the `system.cookies` are the cookies name. The property `system.
 
 ### Device information
 
+
+
 | Property                                   | Type   | Description                                                                                                              |
 | ------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------ |
 | `system.device.ip`                         | String | Visitor incoming IP address.                                                                                             |
@@ -71,6 +76,8 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ### Miscellaneous
 
+
+
 | Property                            | Type   | Description                           |
 | ----------------------------------- | ------ | ------------------------------------- |
 | `system.misc.random`                | Number | Random number unique to each request. |
@@ -80,6 +87,8 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ## Event properties
 
+
+
 | Property              | Type   | Description                                                                                                                                                                                                                                                          |
 | --------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `client.__zarazTrack` | String | Returns the name of the event sent using the Track method of the Web API. Refer to [Zaraz Track](/zaraz/web-api/track/) for more information.                                                                                                                        |
diff --git a/src/content/docs/zaraz/reference/index.mdx b/src/content/docs/zaraz/reference/index.mdx
index 11447093e6b50dc..3b3f9005d879c9c 100644
--- a/src/content/docs/zaraz/reference/index.mdx
+++ b/src/content/docs/zaraz/reference/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Reference
 sidebar:
   order: 9
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/reference/properties-reference.mdx b/src/content/docs/zaraz/reference/properties-reference.mdx
index abecfe520bf0280..a6ac0acf199d0b1 100644
--- a/src/content/docs/zaraz/reference/properties-reference.mdx
+++ b/src/content/docs/zaraz/reference/properties-reference.mdx
@@ -4,8 +4,8 @@ description: Built-in properties available in Zaraz events.
 products:
   - zaraz
 title: Properties reference
----
 
+---
 import { DashButton } from "~/components";
 
 Cloudflare Zaraz offers properties that you can use when configuring the product. They are helpful to send data to a third-party tool or to create triggers as they have context about a specific user's browser session and the actions they take on the website. Below is a list of the properties you can access from the Cloudflare dashboard and their values.
@@ -14,69 +14,69 @@ Cloudflare Zaraz offers properties that you can use when configuring the product
 
 | Property               | Description                                                                                                                                                                                                                                          |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| _Event Name_           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
-| _Track Property name:_ | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
+| *Event Name*           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
+| *Track Property name:* | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
 
 ## Page Properties
 
 | Property                  | Description                                                                                                            |
 | ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| _Page character encoding_ | Returns the document character encoding from `document.characterSet`.                                                  |
-| _Page referrer_           | Returns the page referrer from `document.referrer`.                                                                    |
-| _Page title_              | Returns the page title.                                                                                                |
-| _Query param name:_       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
-| _URL_                     | Returns a string containing the entire URL.                                                                            |
-| _URL base domain_         | Returns the base domain part of the URL, without any subdomains.                                                       |
-| _URL host_                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
-| _URL hostname_            | Returns the domain of the URL.                                                                                         |
-| _URL origin_              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
-| _URL password_            | Returns the password specified before the domain name.                                                                 |
-| _URL pathname_            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
-| _URL port_                | Returns the port number of the URL.                                                                                    |
-| _URL protocol scheme_     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
-| _URL query parameters_    | Returns query parameters provided, beginning with the leading `?` character.                                           |
-| _URL username_            | Returns the username specified before the domain name.                                                                 |
+| *Page character encoding* | Returns the document character encoding from `document.characterSet`.                                                  |
+| *Page referrer*           | Returns the page referrer from `document.referrer`.                                                                    |
+| *Page title*              | Returns the page title.                                                                                                |
+| *Query param name:*       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
+| *URL*                     | Returns a string containing the entire URL.                                                                            |
+| *URL base domain*         | Returns the base domain part of the URL, without any subdomains.                                                       |
+| *URL host*                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
+| *URL hostname*            | Returns the domain of the URL.                                                                                         |
+| *URL origin*              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
+| *URL password*            | Returns the password specified before the domain name.                                                                 |
+| *URL pathname*            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
+| *URL port*                | Returns the port number of the URL.                                                                                    |
+| *URL protocol scheme*     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
+| *URL query parameters*    | Returns query parameters provided, beginning with the leading `?` character.                                           |
+| *URL username*            | Returns the username specified before the domain name.                                                                 |
 
 ## Cookies
 
 | Property       | Description                                           |
 | -------------- | ----------------------------------------------------- |
-| _Cookie name:_ | Returns cookies obtained from the browser `document`. |
+| *Cookie name:* | Returns cookies obtained from the browser `document`. |
 
 ## Device properties
 
 | Property                   | Description                                                 |
 | -------------------------- | ----------------------------------------------------------- |
-| _Browser engine_           | Returns the type of browser engine (for example, `WebKit`). |
-| _Browser engine version_   | Returns the version of the browser’s engine.                |
-| _Browser name_             | Returns the browser’s name.                                 |
-| _Browser version_          | Returns the browser’s version.                              |
-| _Device CPU_               | Returns the device’s CPU.                                   |
-| _Device IP address_        | Returns the incoming IP address.                            |
-| _Device language_          | Returns the language used.                                  |
-| _Device screen resolution_ | Returns the screen resolution of the device.                |
-| _Device type_              | Returns the type of device used (for example, `iPhone`).    |
-| _Device viewport_          | Returns the visible web page area in user’s device.         |
-| _Operating system name_    | Returns the operating system.                               |
-| _Operating system version_ | Returns the version of the operating system.                |
-| _User-agent string_        | Returns the browser’s user agent.                           |
+| *Browser engine*           | Returns the type of browser engine (for example, `WebKit`). |
+| *Browser engine version*   | Returns the version of the browser’s engine.                |
+| *Browser name*             | Returns the browser’s name.                                 |
+| *Browser version*          | Returns the browser’s version.                              |
+| *Device CPU*               | Returns the device’s CPU.                                   |
+| *Device IP address*        | Returns the incoming IP address.                            |
+| *Device language*          | Returns the language used.                                  |
+| *Device screen resolution* | Returns the screen resolution of the device.                |
+| *Device type*              | Returns the type of device used (for example, `iPhone`).    |
+| *Device viewport*          | Returns the visible web page area in user’s device.         |
+| *Operating system name*    | Returns the operating system.                               |
+| *Operating system version* | Returns the version of the operating system.                |
+| *User-agent string*        | Returns the browser’s user agent.                           |
 
 ## Device location
 
 | Property       | Description                                                                                                                                                                       |
 | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| _City_         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
-| _Continent_    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
-| _Country_ code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
-| _EU_ country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
-| _Region_       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
-| _Region_ code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
-| _Timezone_     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
+| *City*         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
+| *Continent*    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
+| *Country* code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
+| *EU* country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
+| *Region*       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
+| *Region* code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
+| *Timezone*     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
 
 ## Miscellaneous
 
 | Property                   | Description                                     |
 | -------------------------- | ----------------------------------------------- |
-| _Random number_            | Returns a random number unique to each request. |
-| _Timestamp (milliseconds)_ | Returns the Unix time in milliseconds.          |
-| _Timestamp (seconds)_      | Returns the Unix time in seconds.               |
+| *Random number*            | Returns a random number unique to each request. |
+| *Timestamp (milliseconds)* | Returns the Unix time in milliseconds.          |
+| *Timestamp (seconds)*      | Returns the Unix time in seconds.               |
diff --git a/src/content/docs/zaraz/reference/settings.mdx b/src/content/docs/zaraz/reference/settings.mdx
index 40f857c4d333de9..886095c024fe466 100644
--- a/src/content/docs/zaraz/reference/settings.mdx
+++ b/src/content/docs/zaraz/reference/settings.mdx
@@ -13,7 +13,7 @@ import { Plan, DashButton } from "~/components";
 
 To configure Zaraz's general settings, go to the **Settings** page in the Cloudflare dashboard:
 
-<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
 
 Make sure you save your changes, by selecting the **Save** button after making them.
 
@@ -45,15 +45,15 @@ When you toggle Single Page Application support off, the `pageview` trigger will
 
 Zaraz offers privacy settings you can configure, such as:
 
-- **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
+* **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
 
-- **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
+* **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
 
-- **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
+* **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
 
-- **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
+* **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
 
-- **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
+* **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
 
 ## Injection
 
@@ -93,9 +93,9 @@ Choose whether to prevent Zaraz from loading on suspected bot-initiated requests
 
 The options are:
 
-- **Block none**: Load Zaraz for all requests, even if those come from bots.
-- **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
-- **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
+* **Block none**: Load Zaraz for all requests, even if those come from bots.
+* **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
+* **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
 
 ### Context Enricher
 
diff --git a/src/content/docs/zaraz/reference/supported-tools.mdx b/src/content/docs/zaraz/reference/supported-tools.mdx
index e20ce7495b724b0..1b388c261cd4ea2 100644
--- a/src/content/docs/zaraz/reference/supported-tools.mdx
+++ b/src/content/docs/zaraz/reference/supported-tools.mdx
@@ -7,6 +7,7 @@ title: Third-party tools
 head:
   - tag: title
     content: Supported tools
+
 ---
 
 Cloudflare Zaraz supports the following third-party tools:
diff --git a/src/content/docs/zaraz/variables/create-variables.mdx b/src/content/docs/zaraz/variables/create-variables.mdx
index cfce350ba75324b..7e4f9894f49c848 100644
--- a/src/content/docs/zaraz/variables/create-variables.mdx
+++ b/src/content/docs/zaraz/variables/create-variables.mdx
@@ -20,8 +20,7 @@ For example, instead of typing a specific user ID in multiple fields, you can cr
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Variables**.
 3. Select **Create variable**, and give it a name.
 4. In **Variable type** select between `String`, `Masked variable` or `Worker` from the drop-down menu. Use `Masked variable` when you have a private value that you do not want to share, such as an API token.
diff --git a/src/content/docs/zaraz/variables/edit-variables.mdx b/src/content/docs/zaraz/variables/edit-variables.mdx
index 0c30678d2adc6e5..2225f830ff4de41 100644
--- a/src/content/docs/zaraz/variables/edit-variables.mdx
+++ b/src/content/docs/zaraz/variables/edit-variables.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a variable
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Variables**.
 3. Locate the variable you want to edit, and select **Edit** to make your changes.
 4. Select **Save** to save your edits.
@@ -29,8 +29,7 @@ You cannot delete a variable being used in tools or triggers.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate any tools using the variable, and delete the variable from those tools.
 4. Select **Zaraz** > **Tools Configuration** > **Triggers**.
diff --git a/src/content/docs/zaraz/variables/index.mdx b/src/content/docs/zaraz/variables/index.mdx
index 98febbeb0a587f0..2201ce391be6a3a 100644
--- a/src/content/docs/zaraz/variables/index.mdx
+++ b/src/content/docs/zaraz/variables/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Variables
 sidebar:
   order: 6
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/variables/worker-variables.mdx b/src/content/docs/zaraz/variables/worker-variables.mdx
index 57b8bfa416f7617..3b80fe43170c522 100644
--- a/src/content/docs/zaraz/variables/worker-variables.mdx
+++ b/src/content/docs/zaraz/variables/worker-variables.mdx
@@ -6,6 +6,7 @@ products:
 title: Worker Variables
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -24,8 +25,7 @@ To create a new Worker in the Cloudflare dashboard:
 
 1. In the Cloudflare dashboard, go to the **Workers and Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
-
+	<DashButton url="/?to=/:account/workers-and-pages" />
 2. Select **Create application**.
 3. Give a name to your Worker and select **Deploy**.
 4. Select **Edit code**.
@@ -35,17 +35,17 @@ You have now created a basic Worker that responds with "Hello world." If you use
 Zaraz forwards the Zaraz Context object to your Worker as a JSON payload with a POST request. You can access any property like this:
 
 ```js
-const { system, client } = await request.json();
+const { system, client } = await request.json()
 
 /* System parameters */
-system.page.url.href; // URL of the current page
-system.page.query.gclid; // Value of the gclid query parameter
-system.device.resolution; // Device screen resolution
-system.device.language; // Browser preferred language
+system.page.url.href // URL of the current page
+system.page.query.gclid // Value of the gclid query parameter
+system.device.resolution // Device screen resolution
+system.device.language // Browser preferred language
 
 /* Zaraz Track values */
-client.value; // value from `zaraz.track("foo", {value: "bar"})`
-client.products[0].name; // name of the first product in an ecommerce call
+client.value // value from `zaraz.track("foo", {value: "bar"})`
+client.products[0].name // name of the first product in an ecommerce call
 ```
 
 Keep reading for more complete examples of different use cases or refer to [Zaraz Context](/zaraz/reference/context/).
@@ -56,8 +56,7 @@ Once your Worker is published, configuring a Worker Variable is easy.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select the domain for which you want to configure variables.
 3. Select the **Variables** tab.
 4. Select **Create variable**.
@@ -72,8 +71,7 @@ To use your Worker Variable:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select the domain for which you want to configure variables.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -88,11 +86,11 @@ Assuming we are sending a list of products in a cart, like this:
 
 ```js
 zaraz.ecommerce("Cart Viewed", {
-	products: [
-		{ name: "shirt", price: "50" },
-		{ name: "jacket", price: "20" },
-		{ name: "hat", price: "30" },
-	],
+  products: [
+    { name: "shirt", price: "50" },
+    { name: "jacket", price: "20" },
+    { name: "hat", price: "30" },
+  ],
 });
 ```
 
@@ -100,18 +98,18 @@ Calculating the sum can be done like this:
 
 ```js
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		// Get an array of all prices
-		const productsPrices = client.products.map((p) => p.price);
+    // Get an array of all prices
+    const productsPrices = client.products.map((p) => p.price);
 
-		// Calculate the sum
-		const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
+    // Calculate the sum
+    const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
 
-		return new Response(sum);
-	},
+    return new Response(sum);
+  },
 };
 ```
 
@@ -121,20 +119,20 @@ Zaraz exposes all cookies automatically under the `system.cookies` object, so th
 
 ```js
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		// Get the value of the cookie "login-cookie"
-		const cookieValue = system.cookies["login-cookie"];
+    // Get the value of the cookie "login-cookie"
+    const cookieValue = system.cookies["login-cookie"];
 
-		const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
-			method: POST,
-			body: cookieValue,
-		});
+    const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
+      method: POST,
+      body: cookieValue,
+    });
 
-		return new Response(userId);
-	},
+    return new Response(userId);
+  },
 };
 ```
 
@@ -150,23 +148,23 @@ You can access this property and hash it like this:
 
 ```js
 async function digestMessage(message) {
-	const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
-	const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
-	const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
-	const hashHex = hashArray
-		.map((b) => b.toString(16).padStart(2, "0"))
-		.join(""); // convert bytes to hex string
-	return hashHex;
+  const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
+  const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
+  const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
+  const hashHex = hashArray
+    .map((b) => b.toString(16).padStart(2, "0"))
+    .join(""); // convert bytes to hex string
+  return hashHex;
 }
 
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		const { email } = client;
+    const { email } = client;
 
-		return new Response(await digestMessage(email));
-	},
+    return new Response(await digestMessage(email));
+  },
 };
 ```
diff --git a/src/content/docs/zaraz/web-api/debug-mode.mdx b/src/content/docs/zaraz/web-api/debug-mode.mdx
index 3e17a55399dfbf2..a2110d8626e7f2c 100644
--- a/src/content/docs/zaraz/web-api/debug-mode.mdx
+++ b/src/content/docs/zaraz/web-api/debug-mode.mdx
@@ -6,6 +6,7 @@ products:
 title: Debug mode
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
@@ -15,14 +16,13 @@ You can set this cookie manually or via the `zaraz.debug` helper function availa
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Copy your **Debug Key**.
 3. Open a web browser and access its Developer Tools. For example, to access Developer Tools in Google Chrome, select **View** > **Developer** > **Developer Tools**.
 4. Select the **Console** pane and enter the following command to create a debug cookie:
 
    ```js
-   zaraz.debug("YOUR_DEBUG_KEY");
+   zaraz.debug("YOUR_DEBUG_KEY")
    ```
 
 Zaraz’s debug mode is now enabled. A pop-up window will show up with the debugger information. To exit debug mode, remove the cookie by typing `zaraz.debug()` in the console pane of the browser.
diff --git a/src/content/docs/zaraz/web-api/ecommerce.mdx b/src/content/docs/zaraz/web-api/ecommerce.mdx
index 94708e09a23b5eb..47b9b8b44b53c60 100644
--- a/src/content/docs/zaraz/web-api/ecommerce.mdx
+++ b/src/content/docs/zaraz/web-api/ecommerce.mdx
@@ -31,8 +31,7 @@ You do not need to map e-commerce events to triggers. Zaraz automatically forwar
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Enable **E-commerce tracking**.
 3. Select **Save**.
 4. Go to **Zaraz** > **Tools Configuration** > **Third-party tools**.
diff --git a/src/content/docs/zaraz/web-api/index.mdx b/src/content/docs/zaraz/web-api/index.mdx
index be94552a3782c97..15b544bb65b4744 100644
--- a/src/content/docs/zaraz/web-api/index.mdx
+++ b/src/content/docs/zaraz/web-api/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Web API
 sidebar:
   order: 3
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Zaraz provides a client-side web API that you can use anywhere inside the `<body>` tag of a page.
 
diff --git a/src/content/docs/zaraz/web-api/set.mdx b/src/content/docs/zaraz/web-api/set.mdx
index 447578481222c7a..0d9f29ac5943204 100644
--- a/src/content/docs/zaraz/web-api/set.mdx
+++ b/src/content/docs/zaraz/web-api/set.mdx
@@ -9,26 +9,27 @@ sidebar:
 head:
   - tag: title
     content: zaraz.set
+
 ---
 
 You can use `zaraz.set()` anywhere inside the `<body>` tag of a page:
 
 ```js
-zaraz.set(key, value, [options]);
+zaraz.set(key, value, [options])
 ```
 
 Set is useful if you want to make a variable available in all your events without manually setting it every time you are using `zaraz.track()`. For the purpose of this example, assume users in your system have a unique identifier that you want to send to your tools. You might have many `zaraz.track()` calls all sharing this one parameter:
 
 ```js
-zaraz.track("form completed", { userId: "ABC-123" });
+zaraz.track("form completed", {userId: "ABC-123"})
 ```
 
 ```js
-zaraz.track("button clicked", { userId: "ABC-123", value: 200 });
+zaraz.track("button clicked", {userId: "ABC-123", value: 200})
 ```
 
 ```js
-zaraz.track("cart viewed", { items: 3, userId: "ABC-123" });
+zaraz.track("cart viewed", {items: 3, userId: "ABC-123"})
 ```
 
 Here, all the events are collecting the `userId` key, and the code for setting that key repeats itself. With `zaraz.set()` you can avoid repetition by setting the key once when the page loads. Zaraz will then attach this key to all future `zaraz.track()` calls.
@@ -38,23 +39,23 @@ Using the above data as the example, if you use `zaraz.set("userId", "ABC-123")`
 Another example:
 
 ```js
-zaraz.set("product_name", "t-shirt", { scope: "page" });
+zaraz.set('product_name', 't-shirt', {scope: 'page'})
 ```
 
-Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable _Track Property name:_, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
+Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable *Track Property name:*, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
 
 ![Example of how to create a variable with the Set method, tracking t-shirts](~/assets/images/zaraz/set.png)
 
 The `[options]` argument is an optional object and can include a `scope` property that has a string value. This property determines the lifetime of this key, meaning for how long Zaraz should keep attaching it to `zaraz.track()` calls. Allowed values are:
 
-- `page`: To set the key for the context of the current page only.
-- `session`: To make the key last the whole session.
-- `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
+* `page`: To set the key for the context of the current page only.
+* `session`: To make the key last the whole session.
+* `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
 
 In the previous example, `{scope: 'page'}` makes the `product_name` property available to all `zaraz.track()` calls in the current page, but will not affect calls after visitors navigate to other pages.
 
 To unset a variable, set it to `undefined`. The variable will then be removed from all scopes it was included in, and will not be automatically sent with future `zaraz.track` calls. For example:
 
 ```js
-zaraz.set("product_name", undefined);
+zaraz.set('product_name', undefined)
 ```
diff --git a/src/content/partials/1.1.1.1/captive-portals.mdx b/src/content/partials/1.1.1.1/captive-portals.mdx
index 7d4223b076a5f3f..9a22c3361ba00f0 100644
--- a/src/content/partials/1.1.1.1/captive-portals.mdx
+++ b/src/content/partials/1.1.1.1/captive-portals.mdx
@@ -12,4 +12,4 @@ If you are experiencing connectivity issues related to captive portals:
 2. Connect to the Wi-Fi network.
 3. Once the connection has been established, re-add the static IP addresses or enable the 1.1.1.1 app.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/agents/unique-agents.mdx b/src/content/partials/agents/unique-agents.mdx
index bd157735e3ad07f..d3f96c7f9fa15e9 100644
--- a/src/content/partials/agents/unique-agents.mdx
+++ b/src/content/partials/agents/unique-agents.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
@@ -10,4 +11,4 @@ This allows you to avoid synchronizing state across requests: if an Agent instan
 
 If the client disconnects, you can always route the client back to the exact same Agent and pick up where they left off.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ai-crawl-control/plan-comparison.mdx b/src/content/partials/ai-crawl-control/plan-comparison.mdx
index a03e263b7030fed..f56f51d865fe7c5 100644
--- a/src/content/partials/ai-crawl-control/plan-comparison.mdx
+++ b/src/content/partials/ai-crawl-control/plan-comparison.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                               |
-| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)                   |
-| Maximum 24-hour analytics window                                                                                              | Configurable analytics timeframes                                                                                                                  |
-| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
+| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                       |
+| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)           |
+| Maximum 24-hour analytics window                                                                                              |  Configurable analytics timeframes                                                                                                      |
+| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
\ No newline at end of file
diff --git a/src/content/partials/ai-gateway/analytics-dashboard.mdx b/src/content/partials/ai-gateway/analytics-dashboard.mdx
index 5dbb03ea869ad8b..9c812ba529cb5bb 100644
--- a/src/content/partials/ai-gateway/analytics-dashboard.mdx
+++ b/src/content/partials/ai-gateway/analytics-dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To view analytics in the dashboard:
diff --git a/src/content/partials/ai-gateway/logging.mdx b/src/content/partials/ai-gateway/logging.mdx
index 9522593e0222102..ae7983b75652584 100644
--- a/src/content/partials/ai-gateway/logging.mdx
+++ b/src/content/partials/ai-gateway/logging.mdx
@@ -1,7 +1,6 @@
 ---
 {}
 ---
-
 import { DashButton } from "~/components";
 
 To change the default log configuration in the dashboard:
diff --git a/src/content/partials/ai-gateway/universal-gateway-example.mdx b/src/content/partials/ai-gateway/universal-gateway-example.mdx
index 6950494e7677012..c0bbda990100faa 100644
--- a/src/content/partials/ai-gateway/universal-gateway-example.mdx
+++ b/src/content/partials/ai-gateway/universal-gateway-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```bash title="Request"
diff --git a/src/content/partials/ai-search/rest-api-auth.mdx b/src/content/partials/ai-search/rest-api-auth.mdx
index afc3a5199d0f9b0..84c53bc88b43199 100644
--- a/src/content/partials/ai-search/rest-api-auth.mdx
+++ b/src/content/partials/ai-search/rest-api-auth.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 All requests require an API token with **AI Search:Edit** and **AI Search:Run** permissions.
 
diff --git a/src/content/partials/analytics/customer_metadata_boundary_error.mdx b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
index 892e43f082a7c02..aa5a25eabdfe090 100644
--- a/src/content/partials/analytics/customer_metadata_boundary_error.mdx
+++ b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 If you encounter a message on the dashboard indicating that your data is unavailable due to your account's Metadata Boundary configuration, this is because you are trying to access data that is not stored in your region (that is, you are in the US and trying to access data that is only stored in the EU, or vice versa). If you receive this error message while being in the region where your data is stored, there are two potential reasons why you might get this message:
 
-- Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
+* Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
 
-- If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
+* If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
diff --git a/src/content/partials/analytics/network-analytics-requirements.mdx b/src/content/partials/analytics/network-analytics-requirements.mdx
index 509b51ff43b0ffd..972d6cea688b524 100644
--- a/src/content/partials/analytics/network-analytics-requirements.mdx
+++ b/src/content/partials/analytics/network-analytics-requirements.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 :::note[Requirements]
 
 Network Analytics requires the following:
 
-- A Cloudflare Enterprise plan.
-- Cloudflare Magic Transit or Spectrum.
-- Cloudflare WAN.
+* A Cloudflare Enterprise plan.
+* Cloudflare Magic Transit or Spectrum.
+* Cloudflare WAN.
   :::
diff --git a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
index bc1a23a14f531b7..d2dfe96892e93b6 100644
--- a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
+++ b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Network Analytics v1 (NAv1) is now deprecated.** For more information on Network Analytics v2 (NAv2), refer to [Cloudflare Network Analytics](/analytics/network-analytics/).
diff --git a/src/content/partials/api-shield/label-methodology.mdx b/src/content/partials/api-shield/label-methodology.mdx
index 96af54686fabef0..72400e85c006187 100644
--- a/src/content/partials/api-shield/label-methodology.mdx
+++ b/src/content/partials/api-shield/label-methodology.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-| 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. |
+| 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. |
diff --git a/src/content/partials/api-shield/mtls-api-shield-support.mdx b/src/content/partials/api-shield/mtls-api-shield-support.mdx
index 1588524b353a3c5..0224d99943797f8 100644
--- a/src/content/partials/api-shield/mtls-api-shield-support.mdx
+++ b/src/content/partials/api-shield/mtls-api-shield-support.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/api-shield/mtls-create-rule.mdx b/src/content/partials/api-shield/mtls-create-rule.mdx
index 8385e54de0b19d4..ac25847bffa79f2 100644
--- a/src/content/partials/api-shield/mtls-create-rule.mdx
+++ b/src/content/partials/api-shield/mtls-create-rule.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 <Steps>
 1. In the Cloudflare dashboard, go to **Client Certificates** page.
@@ -15,4 +16,4 @@ import { Steps, DashButton } from "~/components";
 6. Select **Deploy** to make the rule active.
 </Steps>
 
-Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
+Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
\ No newline at end of file
diff --git a/src/content/partials/api-shield/rate-limit-user.mdx b/src/content/partials/api-shield/rate-limit-user.mdx
index d47e2e46b45069e..9cdc3591641dfcf 100644
--- a/src/content/partials/api-shield/rate-limit-user.mdx
+++ b/src/content/partials/api-shield/rate-limit-user.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ### Rate limit by user (JWT claim)
diff --git a/src/content/partials/api-shield/required-session-identifiers.mdx b/src/content/partials/api-shield/required-session-identifiers.mdx
index 59e54427d1d871b..a1f6276e094c00c 100644
--- a/src/content/partials/api-shield/required-session-identifiers.mdx
+++ b/src/content/partials/api-shield/required-session-identifiers.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You must have specific entitlements to configure session identifiers or cookies as a form of identifiers, such as an Enterprise subscription, for features such as [API Discovery](/api-shield/security/api-discovery/), [Sequence Mitigation](/api-shield/security/sequence-mitigation/) or [rate limiting recommendations](/api-shield/security/volumetric-abuse-detection/), and to see results in [Sequence Analytics](/api-shield/security/sequence-analytics/) and [Authentication Posture](/api-shield/security/authentication-posture/).
diff --git a/src/content/partials/api-shield/sequence-mitigation-availability.mdx b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
index 94c7f150023934f..38bbe706bb998a3 100644
--- a/src/content/partials/api-shield/sequence-mitigation-availability.mdx
+++ b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
+Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
\ No newline at end of file
diff --git a/src/content/partials/api-shield/session-identifiers.mdx b/src/content/partials/api-shield/session-identifiers.mdx
index ef978913a8fe1cf..4e517b779b2b3a9 100644
--- a/src/content/partials/api-shield/session-identifiers.mdx
+++ b/src/content/partials/api-shield/session-identifiers.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 While not strictly required, it is recommended that you configure your <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> when getting started with API Shield. When Cloudflare inspects your API traffic for individual sessions, we can offer more tools for visibility, management, and control.
 
@@ -10,4 +11,4 @@ If you are unsure of the session identifiers that your API uses, consult with yo
 
 Session identifiers should uniquely identify API clients. A common session identifier for API traffic is the `Authorization` header. When a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) is used by the API for client authentication, its value may change over time. You can use a claim value inside the JWT such as `sub` or `email` as a session ID to uniquely identify the session over time.
 
-If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
+If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
\ No newline at end of file
diff --git a/src/content/partials/billing/two-payment-methods.mdx b/src/content/partials/billing/two-payment-methods.mdx
index 9db0c042394f0a1..fcd2e4ffca05097 100644
--- a/src/content/partials/billing/two-payment-methods.mdx
+++ b/src/content/partials/billing/two-payment-methods.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/bots/about-plan-considerations.mdx b/src/content/partials/bots/about-plan-considerations.mdx
index dbee048b258ff34..13c3ff7327eaed5 100644
--- a/src/content/partials/bots/about-plan-considerations.mdx
+++ b/src/content/partials/bots/about-plan-considerations.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 Bot Fight Mode and Super Bot Fight Mode use the same underlying technology that powers our [Bot Management](https://www.cloudflare.com/products/bot-management/) product. Specifically, these products:
 
-- Protect entire domains without endpoint restrictions
-- Cannot be customized, adjusted, or reconfigured via WAF custom rules
+* Protect entire domains without endpoint restrictions
+* Cannot be customized, adjusted, or reconfigured via WAF custom rules
 
 Although these products are designed to fight malicious actors on the Internet, they may challenge API or mobile app traffic. For more granular control, upgrade to [Bot Management for Enterprise](/bots/plans/bm-subscription/).
diff --git a/src/content/partials/bots/analytics-features.mdx b/src/content/partials/bots/analytics-features.mdx
index 5c8c8cc61b1b641..8b21959f185efd0 100644
--- a/src/content/partials/bots/analytics-features.mdx
+++ b/src/content/partials/bots/analytics-features.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare uses adaptive bitrate technology to show sampled data — most customers will see a 1-10% sample depending on how much information they are trying to view. Tooltips on the page will display the current sample rate.
diff --git a/src/content/partials/bots/bfm-change-notice.mdx b/src/content/partials/bots/bfm-change-notice.mdx
index e4fb1dd54926f1a..d7474bab9acd502 100644
--- a/src/content/partials/bots/bfm-change-notice.mdx
+++ b/src/content/partials/bots/bfm-change-notice.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Change notice for Super Bot Fight Mode rulesets]
diff --git a/src/content/partials/bots/bm-analytics-features.mdx b/src/content/partials/bots/bm-analytics-features.mdx
index 9af38b36aca085c..7dc1163ab88af8d 100644
--- a/src/content/partials/bots/bm-analytics-features.mdx
+++ b/src/content/partials/bots/bm-analytics-features.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 For a full tour of Bot Analytics, see [our blog post](https://blog.cloudflare.com/introducing-bot-analytics/). At a high level, the tool includes:
 
-- **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on _automated_ and _likely automated_ traffic.
-- **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
-- **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
-- **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
+* **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on *automated* and *likely automated* traffic.
+* **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
+* **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
+* **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
 
 Bot Analytics shows up to one week of data at a time and can display data up to 30 days old. Bot Analytics displays data in real time in most cases.
diff --git a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
index 4a7b8ba166882b8..792c3896e90dbdb 100644
--- a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
+++ b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
@@ -6,13 +6,13 @@
 
 The following features are handled automatically in **Security Settings** and do not require custom rules:
 
-| Feature                                         | Handled by bot settings | Requires custom rules                                    |
-| ----------------------------------------------- | ----------------------- | -------------------------------------------------------- |
-| Block or challenge definitely automated traffic | Yes                     | Only for path-specific or threshold-tuned rules          |
-| Block or challenge likely automated traffic     | Not available on Pro    | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
-| Allow or block verified bots                    | Yes                     | No                                                       |
-| Block AI crawlers                               | Yes                     | Only to target individual AI crawlers                    |
-| Protect static resources                        | Yes                     | No                                                       |
-| Optimize for WordPress                          | Yes                     | No                                                       |
+| Feature | Handled by bot settings | Requires custom rules |
+| --- | --- | --- |
+| Block or challenge definitely automated traffic | Yes | Only for path-specific or threshold-tuned rules |
+| Block or challenge likely automated traffic | Not available on Pro | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
+| Allow or block verified bots | Yes | No |
+| Block AI crawlers | Yes | Only to target individual AI crawlers |
+| Protect static resources | Yes | No |
+| Optimize for WordPress | Yes | No |
 
-For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
+For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
\ No newline at end of file
diff --git a/src/content/partials/bots/bots-ad.mdx b/src/content/partials/bots/bots-ad.mdx
index f690a31c6f51ec3..da728dfe8e0016d 100644
--- a/src/content/partials/bots/bots-ad.mdx
+++ b/src/content/partials/bots/bots-ad.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Deprecation notice]
diff --git a/src/content/partials/bots/bots-cookie.mdx b/src/content/partials/bots/bots-cookie.mdx
index 62c2872d9a483c0..43bda678f796566 100644
--- a/src/content/partials/bots/bots-cookie.mdx
+++ b/src/content/partials/bots/bots-cookie.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare uses the `__cf_bm` cookie to smooth out the <GlossaryTooltip term="bot score">bot score</GlossaryTooltip> and reduce false positives for actual user sessions.
 
diff --git a/src/content/partials/bots/bots-heuristics.mdx b/src/content/partials/bots/bots-heuristics.mdx
index be4df17066ad18c..4cd143b9744bd18 100644
--- a/src/content/partials/bots/bots-heuristics.mdx
+++ b/src/content/partials/bots/bots-heuristics.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
+The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
\ No newline at end of file
diff --git a/src/content/partials/bots/bots-jsd.mdx b/src/content/partials/bots/bots-jsd.mdx
index 7256269923ab642..0db49de66e6f82f 100644
--- a/src/content/partials/bots/bots-jsd.mdx
+++ b/src/content/partials/bots/bots-jsd.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The [**JavaScript Detections (JSD)**](/bots/additional-configurations/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines.
diff --git a/src/content/partials/bots/bots-ml.mdx b/src/content/partials/bots/bots-ml.mdx
index a14e20442d1ecca..df1136f568be04c 100644
--- a/src/content/partials/bots/bots-ml.mdx
+++ b/src/content/partials/bots/bots-ml.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
 The **Machine Learning (ML)** engine accounts for the majority of all detections, distinguishing between human and bot traffic. This approach leverages our global network, which proxies billions of requests daily, to identify both automated and human traffic.
 
-The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99).
+The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99). 
 
 The core model relies on the following process:
 
 - Input Variables (X): Various request features (headers, session characteristics, and browser signals) collected from traffic across the Cloudflare network.
 - Output Variable (Y): The predicted probability that a client is human (such as the probability of successfully solving a Challenge). This probability is mapped to the final 1–99 Bot Score.
 
-We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
+We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
\ No newline at end of file
diff --git a/src/content/partials/bots/buttons-plan-pages.mdx b/src/content/partials/bots/buttons-plan-pages.mdx
index fcacd4331504ccc..f4bb5390173d743 100644
--- a/src/content/partials/bots/buttons-plan-pages.mdx
+++ b/src/content/partials/bots/buttons-plan-pages.mdx
@@ -1,18 +1,8 @@
 ---
 {}
+
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
-<LinkButton variant="primary" href="/bots/plans/free/">
-	Free
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/pro/">
-	Pro
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/biz-and-ent/">
-	Business
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/bm-subscription/">
-	Bot Management for Enterprise
-</LinkButton>
+ <LinkButton variant="primary" href="/bots/plans/free/">Free</LinkButton> <LinkButton variant="primary" href="/bots/plans/pro/">Pro</LinkButton> <LinkButton variant="primary" href="/bots/plans/biz-and-ent/">Business</LinkButton> <LinkButton variant="primary" href="/bots/plans/bm-subscription/">Bot Management for Enterprise</LinkButton>
diff --git a/src/content/partials/bots/content-security-policy-limitation.mdx b/src/content/partials/bots/content-security-policy-limitation.mdx
index e42c9647319100a..f62345793fe5368 100644
--- a/src/content/partials/bots/content-security-policy-limitation.mdx
+++ b/src/content/partials/bots/content-security-policy-limitation.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from '~/components';
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip>, you need to take additional steps to implement JavaScript Detections:
 
@@ -15,4 +16,4 @@ If you have a <GlossaryTooltip term="content security policy (CSP)">Content Secu
 :::caution[Warning]
 
 JavaScript Detections is not supported with `nonce` set via `<meta>` tags.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/bots/disable-cf-bm-cookie.mdx b/src/content/partials/bots/disable-cf-bm-cookie.mdx
index 3e1a4f6255413c8..a19d23bd96c3778 100644
--- a/src/content/partials/bots/disable-cf-bm-cookie.mdx
+++ b/src/content/partials/bots/disable-cf-bm-cookie.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can disable the `__cf_bm` cookie using the `bm_cookie_enabled` field [via the API](/api/resources/bot_management/methods/update/).
diff --git a/src/content/partials/bots/endpoint-label-warning.mdx b/src/content/partials/bots/endpoint-label-warning.mdx
index 1d94ff8d3590322..3e0748847f1cfbc 100644
--- a/src/content/partials/bots/endpoint-label-warning.mdx
+++ b/src/content/partials/bots/endpoint-label-warning.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: endpoint
+
 ---
 
 :::caution[Login {props.one} endpoints]
-Not all login {props.one} endpoints are automatically detected.
+Not all login {props.one} endpoints are automatically detected. 
 
-Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized.
+Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized. 
 
 For example, if you have a non-traditional login endpoint, you should label it with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/). Once you have applied the `cf-log-in` label, Cloudflare will use the labeled endpoint for account takeover detection decisions.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/bots/execution-order.mdx b/src/content/partials/bots/execution-order.mdx
index 4d3aa8ec0155216..458ad91c88f6909 100644
--- a/src/content/partials/bots/execution-order.mdx
+++ b/src/content/partials/bots/execution-order.mdx
@@ -7,4 +7,4 @@ flowchart LR
 accTitle: Super Bot Fight Mode and custom rules execution order diagram
 accDescr: This diagram details the execution order of custom rules before Super Bot Fight Mode managed rules.
 A[Custom rules] --> B[Block AI bots<br>managed rule] --> C[Other SBFM managed rules]
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/bots/flexible-sbfm.mdx b/src/content/partials/bots/flexible-sbfm.mdx
index d5c7abc133997b6..207bbda9d1f29ee 100644
--- a/src/content/partials/bots/flexible-sbfm.mdx
+++ b/src/content/partials/bots/flexible-sbfm.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-In parts of your site where you want bot traffic, you can use the [_Skip_ action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
+In parts of your site where you want bot traffic, you can use the [*Skip* action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
 
 You can use the [Rules language](/ruleset-engine/rules-language/) and its [operators](/ruleset-engine/rules-language/operators/) and [fields](/ruleset-engine/rules-language/fields/) in custom rules to configure a scoped rule for approved automated traffic in Super Bot Fight Mode.
diff --git a/src/content/partials/bots/ja3-ja4-null.mdx b/src/content/partials/bots/ja3-ja4-null.mdx
index e8829ace2150293..68bc0569df18296 100644
--- a/src/content/partials/bots/ja3-ja4-null.mdx
+++ b/src/content/partials/bots/ja3-ja4-null.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or empty in logs under specific circumstances:
@@ -8,4 +9,4 @@ The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or emp
 - The field may be empty when a [Worker](/workers/) sends a request to a zone that is either internal to Cloudflare's network (O2O traffic that is not proxied) or to a third-party origin, or when a Worker is routing traffic to the target zone.
 - The fingerprints may be absent when Bot Management itself is skipped for a request, as the feature is responsible for calculating and populating these values.
 
-Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
+Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
\ No newline at end of file
diff --git a/src/content/partials/bots/jsd-availability.mdx b/src/content/partials/bots/jsd-availability.mdx
index 3306814fd548d25..57c501ca55fd5a0 100644
--- a/src/content/partials/bots/jsd-availability.mdx
+++ b/src/content/partials/bots/jsd-availability.mdx
@@ -1,5 +1,6 @@
 ---
 inputParameters: planType;;enablement
+
 ---
 
-For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
+For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
\ No newline at end of file
diff --git a/src/content/partials/bots/plan-get-started.mdx b/src/content/partials/bots/plan-get-started.mdx
index 3e26918905eccd4..ab81f675f77e822 100644
--- a/src/content/partials/bots/plan-get-started.mdx
+++ b/src/content/partials/bots/plan-get-started.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To get started, review our [setup guides](/bots/get-started/). If you have any questions, visit the [community](https://community.cloudflare.com/) to engage with other Cloudflare users.
diff --git a/src/content/partials/bots/plan-intro.mdx b/src/content/partials/bots/plan-intro.mdx
index 0b5da491920a683..e2f77067f05bc6d 100644
--- a/src/content/partials/bots/plan-intro.mdx
+++ b/src/content/partials/bots/plan-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To learn more about features and functionality, select a plan.
diff --git a/src/content/partials/bots/sequence-rules.mdx b/src/content/partials/bots/sequence-rules.mdx
index f1469b3b97b7941..5a37ee6b8ddf181 100644
--- a/src/content/partials/bots/sequence-rules.mdx
+++ b/src/content/partials/bots/sequence-rules.mdx
@@ -1,9 +1,6 @@
 ---
 inputParameters: addLink;;Link
+
 ---
 
-<a href={props.two}>{props.one}</a> uses cookies to track the order of requests
-a user has made and the time between requests and makes them available via
-[Cloudflare Rules](/rules/). This allows you to write rules that match valid or
-invalid sequences. The specific cookies used to validate sequences are called
-sequence cookies.
+<a href={props.two}>{props.one}</a> uses cookies to track the order of requests a user has made and the time between requests and makes them available via [Cloudflare Rules](/rules/). This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
diff --git a/src/content/partials/bots/signals-intelligence-and-ja4.mdx b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
index 5f9750c2e03b2f8..d4985540fd03195 100644
--- a/src/content/partials/bots/signals-intelligence-and-ja4.mdx
+++ b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 If you want to use JA4 fingerprints and Signals Intelligence, your Workers script must be able to handle the absence of any field in the array, including:
 
-- The possibility that the JA4 fingerprint could be missing.
-- The possibility that the `ja4Signals` array could be missing.
-- Results with `NaN` or `Infinity` values will be excluded from the array.
+* The possibility that the JA4 fingerprint could be missing.
+* The possibility that the `ja4Signals` array could be missing.
+* Results with `NaN` or `Infinity` values will be excluded from the array.
diff --git a/src/content/partials/bots/verified-bots.mdx b/src/content/partials/bots/verified-bots.mdx
index 641b00e41848448..643ff4708ca88c8 100644
--- a/src/content/partials/bots/verified-bots.mdx
+++ b/src/content/partials/bots/verified-bots.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare maintains an internal directory of [verified bot](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/) that are associated with search engine optimization (SEO), website monitoring, and more.
diff --git a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
index 6674b5b0b076f4f..d6d1aa6348cc9ab 100644
--- a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
+++ b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
@@ -3,14 +3,13 @@
 If you set a large viewport width and height, your screenshot may appear blurry or pixelated. This can happen if your browser's default `deviceScaleFactor` (which defaults to 1) is not high enough for the viewport.
 
 To fix this, increase the value of the `deviceScaleFactor`.
-
 ```json
 {
-	"url": "https://cloudflare.com/",
-	"viewport": {
-		"width": 3600,
-		"height": 2400,
-		"deviceScaleFactor": 2
-	}
+  "url": "https://cloudflare.com/",
+  "viewport": {
+    "width": 3600,
+    "height": 2400,
+    "deviceScaleFactor": 2
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/byoip/cloudflare-asn-callout.mdx b/src/content/partials/byoip/cloudflare-asn-callout.mdx
index c2e64662ef201ba..c4c4f51e5e3f276 100644
--- a/src/content/partials/byoip/cloudflare-asn-callout.mdx
+++ b/src/content/partials/byoip/cloudflare-asn-callout.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Use Cloudflare's ASN]
 The process described on this page only supports using Cloudflare's ASN (AS13335). If you must announce the prefixes under your own ASN, contact your account team.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/byoip/loa.mdx b/src/content/partials/byoip/loa.mdx
index 6f4223cd8341462..c4320799ddc0c7b 100644
--- a/src/content/partials/byoip/loa.mdx
+++ b/src/content/partials/byoip/loa.mdx
@@ -35,4 +35,4 @@ Regards,
 [COMPANY NAME]
 [COMPANY ADDRESS]
 [COMPANY STAMP]
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/byoip/validate-prefix-endpoint.mdx b/src/content/partials/byoip/validate-prefix-endpoint.mdx
index 3d0fbbd3b42c0d2..096f54fc687f97e 100644
--- a/src/content/partials/byoip/validate-prefix-endpoint.mdx
+++ b/src/content/partials/byoip/validate-prefix-endpoint.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
diff --git a/src/content/partials/cache/cache-reserve-billing-note.mdx b/src/content/partials/cache/cache-reserve-billing-note.mdx
index 6f0fbe8ec743390..1d60713a3590fee 100644
--- a/src/content/partials/cache/cache-reserve-billing-note.mdx
+++ b/src/content/partials/cache/cache-reserve-billing-note.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 The billable quantity is rounded up to the nearest million.
 
+
 :::
diff --git a/src/content/partials/cache/cache-reserve-eligibility.mdx b/src/content/partials/cache/cache-reserve-eligibility.mdx
index 426e01aee0d369e..4222abac1e72533 100644
--- a/src/content/partials/cache/cache-reserve-eligibility.mdx
+++ b/src/content/partials/cache/cache-reserve-eligibility.mdx
@@ -7,4 +7,4 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 - Be cacheable, according to Cloudflare's standard [cacheability factors](/cache/).
 - Have a freshness time-to-live (TTL) of at least 10 hours (set by any means such as Cache-Control / [CDN-Cache-Control](/cache/concepts/cache-control/) origin response headers, [Edge Cache TTL](/cache/how-to/edge-browser-cache-ttl/#edge-cache-ttl), [Cache TTL By Status](/cache/how-to/configure-cache-status-code/), or [Cache Rules](/cache/how-to/cache-rules/)),
 - Have a Content-Length response header.
-- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
+- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-intro.mdx b/src/content/partials/cache/cache-reserve-intro.mdx
index d4dd113880b158a..e2f420e60a81457 100644
--- a/src/content/partials/cache/cache-reserve-intro.mdx
+++ b/src/content/partials/cache/cache-reserve-intro.mdx
@@ -4,4 +4,4 @@
 
 Cache Reserve is a large, persistent data store [implemented on top of R2](/r2/). By pushing a single button in the dashboard, your website's cacheable content will be written to Cache Reserve.
 
-In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
+In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-limits.mdx b/src/content/partials/cache/cache-reserve-limits.mdx
index a8fa9e8ea8c5d44..e98031a3e1fb9ba 100644
--- a/src/content/partials/cache/cache-reserve-limits.mdx
+++ b/src/content/partials/cache/cache-reserve-limits.mdx
@@ -7,4 +7,4 @@
 - [Vary for images](/cache/advanced-configuration/vary-for-images/) is currently not compatible with Cache Reserve.
 - Requests to [R2 public buckets linked to a zone's domain](/r2/buckets/public-buckets/) will not use Cache Reserve. Enabling Cache Reserve for the connected zone will use Cache Reserve only for requests not destined for the R2 bucket.
 - Cache Reserve makes requests for uncompressed content directly from the origin. Unlike the standard Cloudflare CDN, Cache Reserve does not include the `Accept-Encoding: gzip` header when sending requests to the origin.
-- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
+- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-operations.mdx b/src/content/partials/cache/cache-reserve-operations.mdx
index ebbfac04358fb8a..7d9ec8cabea8443 100644
--- a/src/content/partials/cache/cache-reserve-operations.mdx
+++ b/src/content/partials/cache/cache-reserve-operations.mdx
@@ -22,4 +22,4 @@ Other purge methods, such as purge by tag, host, prefix, or purge everything wil
 
 :::note
 Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cache/edge-ttl.mdx b/src/content/partials/cache/edge-ttl.mdx
index 02f8bc5af24dabe..1a84b61e6d0f948 100644
--- a/src/content/partials/cache/edge-ttl.mdx
+++ b/src/content/partials/cache/edge-ttl.mdx
@@ -12,4 +12,4 @@ By default, Cloudflare caches certain HTTP response codes with the following Ed
 | 302, 303         | 20m         |
 | 404, 410         | 3m          |
 
-All other status codes are not cached by default.
+All other status codes are not cached by default.
\ No newline at end of file
diff --git a/src/content/partials/cache/regional-tiered-cache.mdx b/src/content/partials/cache/regional-tiered-cache.mdx
index 84f6ff7440bd316..2da23da74a44c6f 100644
--- a/src/content/partials/cache/regional-tiered-cache.mdx
+++ b/src/content/partials/cache/regional-tiered-cache.mdx
@@ -4,4 +4,4 @@
 
 Regional Tiered Cache provides an additional layer of caching for customers who have a global traffic footprint and want to serve content faster by avoiding network latency when there is a cache `MISS` in a lower-tier, resulting in an upper-tier fetch in a data center located far away.
 
-Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
+Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
\ No newline at end of file
diff --git a/src/content/partials/cache/smart-tiered-cache.mdx b/src/content/partials/cache/smart-tiered-cache.mdx
index 4cadd0acc82f9d2..f7feae4ba341a37 100644
--- a/src/content/partials/cache/smart-tiered-cache.mdx
+++ b/src/content/partials/cache/smart-tiered-cache.mdx
@@ -14,4 +14,4 @@ While Smart Tiered Cache selects one Upper Tier per origin, when using Load Bala
 
 #### Caveats
 
-You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
+You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
index 38bc50594dca1b0..d395290564350e8 100644
--- a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
+++ b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
@@ -7,4 +8,4 @@
 [JavaScript detections](/bots/additional-configurations/javascript-detections/) are stored in the `cf_clearance` cookie.
 
 The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
index 3e1cf935e85c7fd..a4d3b6a8833f777 100644
--- a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
+++ b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/).
+You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/). 
 
-Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/).
+Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/). 
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
index 6b6ee7d8e7a6954..ecd1e00cd105b61 100644
--- a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With [apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/), SaaS customers need to create an `A` record for their hostname that points to the IP prefix allocated to the SaaS provider's account.
@@ -10,6 +11,8 @@ example.com.  60  IN  A   192.0.2.1
 
 :::note
 
+
 For [BYOIP](/byoip/) customers, Cloudflare automatically enables the Apex Proxy Access feature on your BYOIP block, which allows Custom Hostnames to be activated via [Apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) when Authoritative DNS for a customer's hostname targets any IP addresses in your BYOIP block.
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
index e442ded8479e150..cc1caa4a35ce4a3 100644
--- a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Most customers will have a `CNAME` target, which requires their customers to create a `CNAME` record similar to:
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
index b778c86451909e7..c72ac1bf7f7c156 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
@@ -1,10 +1,12 @@
 ---
 {}
+
 ---
 
 1. To create a custom hostname using the API, use the [Create Custom Hostname](/api/resources/custom_hostnames/methods/create/) endpoint.
-   - You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
 
-2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`. It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
+   * You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
+
+2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`.  It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
 
 The response contains the complete definition of the new custom hostname.
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
index 6c4d2491a949000..e70192ef25ae6e5 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
@@ -1,12 +1,15 @@
 ---
 {}
+
 ---
 
 :::note[Default behavior]
 
+
 When you create a custom hostname:
 
-- If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
-- If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
+* If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
+* If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
+
 
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
index 0e5a5aff297fbc1..5734dd54f9b5277 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,10 +11,10 @@ import { DashButton } from "~/components";
 
 2. Select **Add Custom Hostname**.
 3. Add your customer's hostname `app.customer.com` and set the relevant options, including:
-   - The [minimum TLS version](/ssl/reference/protocols/).
-   - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
-   - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
-   - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
-   - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
-   - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
+    - The [minimum TLS version](/ssl/reference/protocols/).
+    - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
+    - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
+    - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+    - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
+    - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
 4. Select **Add Custom Hostname**.
diff --git a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
index 2d204cd4201372c..8d09df2ede8e363 100644
--- a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 A **custom origin server** lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback, such as:
 
-- `soap.stores.com` goes to `origin1.com`
-- `towel.stores.com` goes to `origin2.com`
+* `soap.stores.com` goes to `origin1.com`
+* `towel.stores.com` goes to `origin2.com`
diff --git a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
index de24df450fd2452..dd9e0a9dbf02a89 100644
--- a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
+++ b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
index b93ff80e6e1c8a8..f75a9b302889462 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you first [enable](/cloudflare-for-platforms/cloudflare-for-saas/start/enable/) Cloudflare for SaaS, you need to perform a few steps prior to creating any custom hostnames.
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
index cfac6c51968d0bb..d0487c9804e2705 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs } from "~/components"
 
 You need to perform the following steps for each custom hostname.
 
@@ -49,6 +50,8 @@ To create a custom hostname:
 
 :::note
 
+
 <Render file="issue-certs-preamble" product="cloudflare-for-platforms" />
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
index 76408b768cb0721..e69030364c61734 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: planReqs
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 ## Before you begin
 
@@ -13,5 +14,5 @@ Before you start creating custom hostnames:
 3. Review the [Hostname prioritization guidelines](/ssl/reference/certificate-and-hostname-priority/#hostname-priority). Wildcard custom hostnames behave differently than an exact hostname match.
 4. (optional) Review the following documentation:
 
-- [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
-- [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+* [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
+* [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
index 35edd6886fe0424..82d0fca0621c733 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your customer is also using Cloudflare for their domain, they should keep their DNS record pointing to your SaaS provider in place for as long as they want to use your service.
diff --git a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
index ea5860cd4a1012d..93a809da7f02598 100644
--- a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 Specific (non-wildcard) custom hostnames can use [HTTP based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/http/) for certificate renewals, as long as:
 
-- The hostname is pointing to the SaaS provider.
-- The hostname's traffic is proxying through the Cloudflare network.
+* The hostname is pointing to the SaaS provider.
+* The hostname's traffic is proxying through the Cloudflare network.
 
 If your custom hostnames do not meet these requirements, use another validation method.
diff --git a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
index 7f9762bab2589d4..3bb70a1297de1a6 100644
--- a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For each custom hostname, Cloudflare issues two certificates bundled in chains that maximize browser compatibility (unless you [upload custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/)).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
index 1e684db0ea49bf0..1d723d8f9826ad2 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
 
-- [Caching](/cache/)
-- [Workers](/workers/)
-- [Rules](/rules/)
+* [Caching](/cache/)
+* [Workers](/workers/)
+* [Rules](/rules/)
 
 For a full list of compatible products and potential limitations, refer to [Product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
index 1e0fb535dd18bf6..343e065d9148425 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
@@ -9,4 +9,4 @@ If your own Cloudflare zone is on the Enterprise plan, you have access to the [z
 
 To successfully activate the custom hostname on {props.providerName}, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to {props.providerName}, only the subfeature titled **Also prevent Subdomains** needs to be temporarily disabled.
 
-Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
+Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/regional-services.mdx b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
index c636d4b3c92b405..ee7ffcc908b6aac 100644
--- a/src/content/partials/cloudflare-for-platforms/regional-services.mdx
+++ b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you have [regional services](/data-localization/regional-services/) set up for your custom hostnames, Cloudflare always uses the processing region associated with your DNS target record (instead of the processing region of any [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/)).
diff --git a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
index 092651f810975a3..b4bb3909a232e68 100644
--- a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
+++ b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your SaaS domain is also a [domain using Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/), you can use your Cloudflare DNS to remove your domain from your SaaS provider.
diff --git a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
index 22b6eab5814cf27..d99a28f10dcf5ed 100644
--- a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
+++ b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
+Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
index f92949ab320cc09..b78a7aab90c363e 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you [create a new hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/issue-certificates/) and choose this validation method, you will see the following values after a few seconds:
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
index 0d895b1350d6147..7c01800301e8819 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare's network to your customers via their own custom or vanity domains.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
index cc44b4ab26564b0..44c1c73202134c3 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Only certain customers have access to this feature. For more details, see the [Plans page](/cloudflare-for-platforms/cloudflare-for-saas/plans/).
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
index 6d0ccd57fab6aec..86394cc77e6b615 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you would like to request an immediate recheck, [rather than wait for the next retry](/ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/), send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) with the same values as your initial `POST` request.
diff --git a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
index 04ae68397c36d17..39515e01e4e3b0a 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Wildcard custom hostnames require TXT-based validation. As the SaaS provider, you have two options for wildcard custom hostname certificate renewals:
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
index 50ebce2cda146e9..37093f6529689dd 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can access these tokens using the API with the [`GET` custom hostnames endpoint](/api/resources/custom_hostnames/methods/list/).
@@ -8,46 +9,46 @@ For example, here are two tokens highlighted in the API response for a **wildcar
 
 ```json title="Response" {11,12,13,14,15,16,17,18,19,20,21,22}
 {
-	"result": [
-		{
-			"id": "<HOSTNAME_ID>",
-			"hostname": "<HOSTNAME>",
-			"ssl": {
-				"id": "<CERTIFICATE_ID>",
-				"type": "dv",
-				"method": "txt",
-				"status": "pending_validation",
-				"validation_records": [
-					{
-						"status": "pending",
-						"txt_name": "_acme-challenge.<HOSTNAME>",
-						"txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
-					},
-					{
-						"status": "pending",
-						"txt_name": "_acme-challenge.<HOSTNAME>",
-						"txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
-					}
-				],
-				"settings": {
-					"min_tls_version": "1.0"
-				},
-				"bundle_method": "ubiquitous",
-				"wildcard": true,
-				"certificate_authority": "google"
-			},
-			"status": "pending",
-			"ownership_verification": {
-				"type": "txt",
-				"name": "_cf-custom-hostname.<HOSTNAME>",
-				"value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-			},
-			"ownership_verification_http": {
-				"http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
-				"http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-			},
-			"created_at": "2022-10-06T19:35:33.143257Z"
-		}
-	]
+  "result": [
+    {
+      "id": "<HOSTNAME_ID>",
+      "hostname": "<HOSTNAME>",
+      "ssl": {
+        "id": "<CERTIFICATE_ID>",
+        "type": "dv",
+        "method": "txt",
+        "status": "pending_validation",
+        "validation_records": [
+          {
+            "status": "pending",
+            "txt_name": "_acme-challenge.<HOSTNAME>",
+            "txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
+          },
+          {
+            "status": "pending",
+            "txt_name": "_acme-challenge.<HOSTNAME>",
+            "txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
+          }
+        ],
+        "settings": {
+          "min_tls_version": "1.0"
+        },
+        "bundle_method": "ubiquitous",
+        "wildcard": true,
+        "certificate_authority": "google"
+      },
+      "status": "pending",
+      "ownership_verification": {
+        "type": "txt",
+        "name": "_cf-custom-hostname.<HOSTNAME>",
+        "value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+      },
+      "ownership_verification_http": {
+        "http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
+        "http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+      },
+      "created_at": "2022-10-06T19:35:33.143257Z"
+    }
+  ]
 }
 ```
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
index b813a3302da20ca..1b2e4694b7a24a3 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
index 88015281280b9e2..45dff2d23eddc00 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 Your customers should place these at their authoritative DNS provider under the `"_acme-challenge"` DNS label. Once these TXT records are in place, validation and certificate issuance will automatically complete.
 
 :::note
 
+
 These tokens are different than the hostname validation tokens.
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
index b28cac12e8c8a6e..ff44799c97955f9 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 These tokens can be fetched through the API or the dashboard when the certificates are in a [pending validation](/ssl/reference/certificate-statuses/#new-certificates) state during custom hostname creation or during certificate renewals.
diff --git a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
index df573c1be7cd67a..62c3d6a6525d69f 100644
--- a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
+++ b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your hostname is using another validation method, you will need to [update](/api/resources/custom_hostnames/methods/edit/) the `"method"` field in the SSL object to be `"txt"`.
diff --git a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
index a7d0a8eb53a6049..e0c4b7896a69330 100644
--- a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To validate a certificate on a wildcard custom hostname, you should either set up [Delegated DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv/) or [TXT-based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/).
diff --git a/src/content/partials/cloudflare-one/access/access-block-page.mdx b/src/content/partials/cloudflare-one/access/access-block-page.mdx
index 42cdfd762ed89a7..0330f3335eae871 100644
--- a/src/content/partials/cloudflare-one/access/access-block-page.mdx
+++ b/src/content/partials/cloudflare-one/access/access-block-page.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 **Custom block pages**: Choose what users will see when they are denied access to the application.
 
-- **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
-- **Redirect URL**: Redirect to the specified website.
-- **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
+* **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
+* **Redirect URL**: Redirect to the specified website.
+* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
diff --git a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
index ed3f8e126327b44..8c24f29e8151dc8 100644
--- a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
+++ b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
@@ -11,15 +11,14 @@ params:
 
 4. In **Certificate content**, paste the contents of your root CA.
 
-   If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
+	If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
+	```txt
+	-----BEGIN CERTIFICATE-----
+	<intermediate.pem>
+	-----END CERTIFICATE-----
+	-----BEGIN CERTIFICATE-----
+	<rootCA.pem>
+	-----END CERTIFICATE-----
+	```
 
-   ```txt
-   -----BEGIN CERTIFICATE-----
-   <intermediate.pem>
-   -----END CERTIFICATE-----
-   -----BEGIN CERTIFICATE-----
-   <rootCA.pem>
-   -----END CERTIFICATE-----
-   ```
-
-   { props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
+	{ props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/add-target.mdx b/src/content/partials/cloudflare-one/access/add-target.mdx
index e96d8060689cd6f..744e5212117cbde 100644
--- a/src/content/partials/cloudflare-one/access/add-target.mdx
+++ b/src/content/partials/cloudflare-one/access/add-target.mdx
@@ -3,22 +3,15 @@ params:
   - protocol
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	Details,
-	APIRequest,
-	GlossaryTooltip,
-} from "~/components";
+import { Tabs, TabItem, Render, Details, APIRequest, GlossaryTooltip } from "~/components";
 
 A target represents a single resource in your infrastructure (such as a server, Kubernetes cluster, database, or container) that users will connect to through Cloudflare.
 
 {
-props.protocol === "rdp" ? (
-<p> Create a target for each Windows machine that requires RDP access.
+  props.protocol === "rdp" ? (
+		<p> Create a target for each Windows machine that requires RDP access.
 To create a new target:</p>) :
-(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
+	(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
 }
 
 <Tabs syncKey="dashPlusAPI">
@@ -93,4 +86,4 @@ The following example requires Cloudflare provider version `>=4.45.0`.
 </TabItem>
 </Tabs>
 
-Next, create an Access application to secure the target.
+Next, create an Access application to secure the target.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/app-launcher.mdx b/src/content/partials/cloudflare-one/access/app-launcher.mdx
index b4f2bad751637b9..7e555517f94da72 100644
--- a/src/content/partials/cloudflare-one/access/app-launcher.mdx
+++ b/src/content/partials/cloudflare-one/access/app-launcher.mdx
@@ -54,8 +54,8 @@ To show an Access application in the App Launcher:
 
 6.  In **Application domains**, choose a domain to use for the App Launcher link.
 
-7.  (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
+7. (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
 
 ## Customize App Launcher appearance
 
-To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
+To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx
index f34af47cbd7d9e0..5090f69c89745fd 100644
--- a/src/content/partials/cloudflare-one/access/bookmarks.mdx
+++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With Cloudflare One, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
@@ -55,4 +56,4 @@ If you attempt to assign a policy that uses an unsupported feature, the dashboar
 
 :::tip[Device posture policies]
 To show bookmarks only to users on managed devices, assign a policy that requires device posture checks (such as [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)). The bookmark will only appear in the App Launcher for users whose devices satisfy the posture requirements.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/create-service-token.mdx b/src/content/partials/cloudflare-one/access/create-service-token.mdx
index 1fa69e143298c53..048dfc0204abc20 100644
--- a/src/content/partials/cloudflare-one/access/create-service-token.mdx
+++ b/src/content/partials/cloudflare-one/access/create-service-token.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Tabs, TabItem, Details, APIRequest } from "~/components";
+import { Tabs, TabItem, Details, APIRequest } from '~/components';
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
index 5eafbf7d586642f..ad31a3a9469c5c2 100644
--- a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
@@ -4,7 +4,7 @@ params:
   - supportgroups?
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Identity providers**.
 
@@ -14,12 +14,12 @@ import { Markdown } from "~/components";
 
 4. (Optional) Configure the following settings:
 
-- **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
-- **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
-- **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
-  - _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
-  - _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
-  - _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
+* **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
+* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
+* **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
+	- _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
+	- _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
+	- _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
 
 5. Select **Regenerate Secret**. Copy the **SCIM Endpoint** and **SCIM Secret**. You will need to enter these values into {props.idp}.
 
diff --git a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
index 4b7ad4e06edeccf..7c3cd7116b2f389 100644
--- a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
+++ b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
@@ -2,6 +2,7 @@
 {}
 ---
 
+
 ```tf
 resource "cloudflare_zero_trust_access_identity_provider" "microsoft_entra_id" {
 	account_id = var.cloudflare_account_id
diff --git a/src/content/partials/cloudflare-one/access/idp-integration.mdx b/src/content/partials/cloudflare-one/access/idp-integration.mdx
index 183354135c18212..d72214326c20f10 100644
--- a/src/content/partials/cloudflare-one/access/idp-integration.mdx
+++ b/src/content/partials/cloudflare-one/access/idp-integration.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, Tabs, TabItem } from "~/components";
+import {Render, Tabs, TabItem} from "~/components"
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -33,4 +33,4 @@ import { Render, Tabs, TabItem } from "~/components";
 
 		<Render file="access/idp-integration-note" product="cloudflare-one" params={{verb: "use" }} />
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
index d87a8bf152d7198..1963b122d60ac7e 100644
--- a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
+++ b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Your browser must [allow third-party cookies](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#allow-third-party-cookies-in-the-browser) on the application domain.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
index 6383efe24af3bc3..0c88cd0f401e32d 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
@@ -1,12 +1,13 @@
 ---
 inputParameters: uiLocation;;stepIntro
+
 ---
 
 1. In Miro, select your profile picture > **Settings** > <strong>{props.one}</strong>.
 2. Turn on **SSO/SAML**.
 3. Fill in the following fields:
-   - **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
-   - **Key x509 Certificate**: Public key from application configuration in Cloudflare One
+   * **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
+   * **Key x509 Certificate**: Public key from application configuration in Cloudflare One
 4. In **Domain**, enter the domain you want to configure SSO for and select **Enter**.
 5. {props.two} an email address from that domain and select **send verification**.
 6. Once you receive a verification email, select the link in the email, then select **Save**. When the domain is successfully configured, the **VERIFY EMAIL** label next to the domain in the SSO/SAML configuration page will disappear.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
index ef59bdce1e4d853..ae78bb666c48d5b 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
@@ -4,4 +4,4 @@ params:
   - token
 ---
 
-{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
+{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
index 8d954a610155794..4c14a8d7ee82fc2 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Enable Cloudflare Access as an identity provider on your Salesforce domain:
diff --git a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
index 9ef968d9aade80a..0aaa9e7f0ecc8c3 100644
--- a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
+++ b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
@@ -4,4 +4,4 @@
 
 :::note
 New users must first [register the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/) or authenticate to an Access application before SCIM provisioning can begin.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
index eab1fcef7940eb3..3407640eddab5ff 100644
--- a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
+++ b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To secure your origin, you must validate the [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/) issued by Cloudflare Access. Token validation ensures that any requests which bypass Cloudflare Access (for example, due to a network misconfiguration) are rejected.
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
index 58d1b77d29be1f9..759ae3cd92c090e 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - [**Cross-Origin Resource Sharing (CORS) settings**](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors/)
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
index 4e0f540d68c6438..abb27fd686a9a68 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::note
 Ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
index 6ff71b18c02ad6d..c7820c683885328 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
@@ -12,29 +13,21 @@ import { Render } from "~/components";
 
 4. Select **Add public hostname**.
 
-5. <Render
-   	file="access/self-hosted-app/choose-domain"
-   	product="cloudflare-one"
-   />
+5. <Render file="access/self-hosted-app/choose-domain" product="cloudflare-one" />
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-7. <Render
-   	file="access/access-choose-idps"
-   	product="cloudflare-one"
-   	params={{ appType: "public" }}
-   />
+7. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "public" }}/>
 
 8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
 9. <Render file="access/session-duration" product="cloudflare-one" />
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-    - <Render file="access/access-block-page" product="cloudflare-one" />
-      <Render
-      	file="access/self-hosted-app/advanced-settings"
-      	product="cloudflare-one"
-      />
+
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	- <Render file="access/access-block-page" product="cloudflare-one" />
+	<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
 
 11. Select **Create**.
+
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
index 427717a9cdab7ee..9c4a7b36eb13bf2 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
@@ -1,14 +1,14 @@
 ---
 {}
----
 
+---
 When using Access self-hosted applications, the majority of Cloudflare products will be compatible with your application.
 
 However, the following products are not supported:
 
-- [Automatic Platform Optimization](/automatic-platform-optimization)
-- [Zaraz](/zaraz)
-- [Google tag gateway for advertisers](/google-tag-gateway)
+* [Automatic Platform Optimization](/automatic-platform-optimization)
+* [Zaraz](/zaraz)
+* [Google tag gateway for advertisers](/google-tag-gateway)
 
 You can disable Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain.
 
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
index af5476bb1880972..1f73a0a13cfd29a 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
+Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/session-duration.mdx b/src/content/partials/cloudflare-one/access/session-duration.mdx
index 77ec2d4a99238d0..ac75de0b9aa9cfa 100644
--- a/src/content/partials/cloudflare-one/access/session-duration.mdx
+++ b/src/content/partials/cloudflare-one/access/session-duration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 In **Session Duration**, choose how often the user's [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token/) should expire.
diff --git a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
index 21858eabcee3e1e..c53f9130b03a46d 100644
--- a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
+++ b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
@@ -3,6 +3,6 @@ params:
   - intro
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
+{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/tags.mdx b/src/content/partials/cloudflare-one/access/tags.mdx
index 77a811446a51a56..0afe99bdc346ec1 100644
--- a/src/content/partials/cloudflare-one/access/tags.mdx
+++ b/src/content/partials/cloudflare-one/access/tags.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can label an Access application with up to 25 custom tags. End users can then filter the applications in their [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) by their tags.
diff --git a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
index bfb96fb10ada920..90d56df296e1cc3 100644
--- a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
+++ b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
@@ -6,4 +6,4 @@ import { Render } from "~/components";
 
 To check if user identities were updated in Cloudflare One, view your [SCIM provisioning logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/).
 
-<Render file="access/scim-requires-login" product="cloudflare-one" />
+<Render file="access/scim-requires-login" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/aws-resolver.mdx b/src/content/partials/cloudflare-one/aws-resolver.mdx
index 9c47b138f5d989e..9a9d914decd40c5 100644
--- a/src/content/partials/cloudflare-one/aws-resolver.mdx
+++ b/src/content/partials/cloudflare-one/aws-resolver.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 Avoid configuring your [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) or [Resolver Policy](/cloudflare-one/traffic-policies/resolver-policies/) to direct all `*.amazonaws.com` DNS resolution via AWS Route 53 Resolver.
 
 Some AWS endpoints (such as `ssm.us-east-1.amazonaws.com`) are public AWS endpoints that are not resolvable via internal VPC resolution. This can break AWS Console features for users on the Cloudflare One Client.
 
-Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
+Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
index ddceb27b9e24102..e908569bbffc1cf 100644
--- a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
+++ b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
@@ -12,3 +12,4 @@
 - [Microsoft 365 Copilot](/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot/)
 - [OpenAI](/cloudflare-one/integrations/cloud-and-saas/openai/)
 - [Anthropic](/cloudflare-one/integrations/cloud-and-saas/anthropic/)
+
diff --git a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
index e478a5a5da68b5d..aada7498182b020 100644
--- a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
+++ b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
@@ -8,4 +8,4 @@ Detect DLP matches in content used and shared within Microsoft's artificial inte
 | --------------------------------------------------------- | -------------------------------------- | -------- |
 | Microsoft: Copilot Referenced File with DLP Profile match | `fa7b06bd-cf63-41fc-9afa-a20598f7a52d` | High     |
 | Microsoft: Copilot AI Response with DLP Profile match     | `176b9299-0cee-4bbb-9c59-b18611228454` | High     |
-| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
+| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/choose-team-name.mdx b/src/content/partials/cloudflare-one/choose-team-name.mdx
index 4d29a981f28db0a..a8d57921a2efb06 100644
--- a/src/content/partials/cloudflare-one/choose-team-name.mdx
+++ b/src/content/partials/cloudflare-one/choose-team-name.mdx
@@ -2,6 +2,7 @@ import { GlossaryTooltip } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
 
+
 2. On the onboarding screen, choose a <GlossaryTooltip term="team name">team name</GlossaryTooltip>. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry.
 
    You can find your team name in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Settings**.
diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
index 65c136e3d2c2438..fe7557d47652954 100644
--- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**.
-2. Turn on **Allow users to open a remote browser without the device client**.
+2. Turn on **Allow users to open a remote browser without the device client**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
index 69056d8ee6f20d8..7323f05d09189c0 100644
--- a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
+++ b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
@@ -1 +1 @@
-Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
+Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
index 8305079a6f89537..65a8f00486b5bc1 100644
--- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
+++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
@@ -16,7 +16,7 @@ To capture data from a remote device:
      :::note
      **Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test.
      :::
-     {props.bestPractice}
+		 {props.bestPractice}
 4. Select **Run diagnostics**.
 
 DEX will now send capture requests to the configured devices. If the Cloudflare One Client is disconnected, the capture will time out after 10 minutes.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
index fea35b13ae26ba6..83843ecfc58460f 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -21,8 +22,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -32,4 +34,4 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 
 12. Review your settings and select **Submit**.
 
-13. Select **Done**.
+13. Select **Done**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
index d4376f9c0f71649..ca5f0f65140cc17 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -21,8 +22,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -41,8 +43,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
-    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
+    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 18. Select **Next**.
 
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
index b2310b379b92a16..a2bfdd54a9efbbb 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To configure quarantine notifications:
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
index 01fe2f78cef538f..8e7f70186f96377 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
+Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
index d49c114294cdce6..3ff7a31c494d759 100644
--- a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
+++ b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
@@ -1,10 +1,10 @@
 - **Malicious**: Traffic associated with active threat campaigns. Malicious messages invoked multiple phishing verdict triggers and met thresholds for bad behavior.
-  - **Recommendation**: Block.
+    - **Recommendation**: Block.
 - **Spam**: Traffic associated with non-malicious, commercial campaigns.
-  - **Recommendation**: Route to existing Spam quarantine folder.
+    - **Recommendation**: Route to existing Spam quarantine folder.
 - **Bulk**: Traffic often associated with newsletters or marketing campaigns. Refer to [Graymail](https://en.wikipedia.org/wiki/Graymail_%28email%29) for more details.
-  - **Recommendation**: Monitor or tag.
+    - **Recommendation**: Monitor or tag.
 - **Suspicious**: Traffic associated with phishing campaigns (and is under further analysis by our automated systems).
-  - **Recommendation**: Research these messages internally to evaluate legitimacy.
+    - **Recommendation**: Research these messages internally to evaluate legitimacy.
 - **Spoof**: Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) or has mismatching `Envelope From` and `Header From` values.
-  - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
+    - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
index 2edeb49998378d2..23143351441d03b 100644
--- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx
+++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
@@ -2,17 +2,17 @@ When you configure your domain, the Cloudflare dashboard will display you the fo
 
 - **Domain**: Domain name. Refer to [Manage domains](/cloudflare-one/email-security/setup/manage-domains/) to learn how to add, filter, and delete domains.
 - **Configured method**: The deployment method you used to configure your domain. Depending on how you decided to configure Email security, the dashboard will display:
-  - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
-  - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
-  - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
-- **Status**: Status indicates the state of the configuration.
-  - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
-  - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
+    - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
+    - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
+    - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
+- **Status**: Status indicates the state of the configuration. 
+    - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
+    - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
 - **Service address**: This is the email address you will use to send a copy of your email.
 - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**.
 - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration:
-  1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
-  2. Locate your integration, select **Configure**, then select **Edit**.
-  3. Rename your integration, then select **Save**.
+    1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
+    2. Locate your integration, select **Configure**, then select **Edit**.
+    3. Rename your integration, then select **Save**. 
 - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured.
-- **Date added**: Date when the domain was added.
+- **Date added**: Date when the domain was added.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
index 5ea5ae3a83f02f1..33c6c6c71c6243a 100644
--- a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
+++ b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
+[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
index 40c2ac71b068bec..49cd1e994f8a9f8 100644
--- a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
+++ b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up)
 - A [Zero Trust organization](/cloudflare-one/setup/#2-create-a-zero-trust-organization)
-- A domain to protect
+- A domain to protect
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
index b06118fd3a052a0..9a1bdd00693b775 100644
--- a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
+++ b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can include an external logo image to display on your custom block page. The block page resizes all images to 146x146 pixels. The URL must be valid and no longer than 2048 characters. Accepted file types include SVG, PNG, JPEG, and GIF.
diff --git a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
index bbbfc69bd059ecb..eec835ed93e198e 100644
--- a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
+++ b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies**.
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
index 046196f5fdbf1e2..ea9c95d04ff8dfe 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
 - **IPv4**: `100.80.0.0/16`
-- **IPv6**: `2606:4700:0cf1:4000::/64`
+- **IPv6**: `2606:4700:0cf1:4000::/64`
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
index 30af62814f0f3df..7aafd3c92aef6de 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
@@ -4,13 +4,13 @@
 
 import { Render, Details, GlossaryTooltip } from "~/components";
 
-| On-ramp method                                                                             | Compatibility |
-| ------------------------------------------------------------------------------------------ | ------------- |
-| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) | ✅            |
-| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)               | ✅            |
-| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                             | ✅            |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                    | ✅            |
-| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                           | 🚧[^1]        |
+| On-ramp method                                                                                      | Compatibility |
+| --------------------------------------------------------------------------------------------------- | ------------- |
+| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                                            | ✅            |
+| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)                        | ✅            |
+| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                                      | ✅            |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) | ✅            |
+| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                                              | 🚧[^1]        |
 
 [^1]: Not compatible with [ECMP routing](/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing). For hostname-based routing to work, DNS queries and the resulting network traffic must reach Cloudflare over the same IPsec/GRE tunnel. <br/>
 
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
index d1f4b0b967db2ba..a639506c0b67a66 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip } from "~/components"
 
 In your WARP [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel.  Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode):
 
 - **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
 - **Include mode**: Add Split Tunnel entries for the following IP addresses:
-  <Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
+	 	<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
index 0dbf6f82fe6cd31..07c7d64a068b757 100644
--- a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
+++ b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
@@ -28,4 +28,4 @@ import { TabItem, Tabs } from "~/components";
 	}
 	```
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
index 91940427f366679..1615bd27d784c47 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 | Selector    | Operator | Value            | Action         |
 | ----------- | -------- | ---------------- | -------------- |
-| Application | in       | _Do Not Inspect_ | Do Not Inspect |
+| Application | in       | *Do Not Inspect* | Do Not Inspect |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
index 24521accd2be220..a55001b8df4ac2c 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | Policy name                 | Selector       | Operator | Value            | Egress method                   |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
index 7584fb41e2afe19..4e453523e39abb5 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
@@ -2,7 +2,7 @@
 inputParameters: selector;;value
 ---
 
-| Selector         | Operator      | Value                      | Logic | Action |
-| ---------------- | ------------- | -------------------------- | ----- | ------ |
-| {props.selector} | in            | <code>{props.value}</code> | And   | Allow  |
-| User Email       | matches regex | `.*@example.com`           |       |        |
+| Selector       | Operator      | Value            | Logic | Action |
+| -------------- | ------------- | ---------------- | ----- | ------ |
+| {props.selector} | in          | <code>{props.value}</code>   | And   | Allow  |
+| User Email     | matches regex | `.*@example.com` |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
index 77ace8200c34cdf..3b9f11e6ef1ca2b 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
@@ -4,4 +4,4 @@
 
 | Selector       | Operator | Value        | Action |
 | -------------- | -------- | ------------ | ------ |
-| Destination IP | in       | `10.0.0.0/8` | Block  |
+| Destination IP | in       | `10.0.0.0/8` | Block  |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
index 1ed03e7aa407058..293b0d23be0ff03 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-| Selector   | Operator      | Value                 | Logic | Action |
-| ---------- | ------------- | --------------------- | ----- | ------ |
-| Host       | in            | `wiki.internal.local` | And   | Allow  |
-| User Email | matches regex | `.*@example.com`      |       |        |
+| Selector       | Operator      | Value            | Logic | Action |
+| -------------- | ------------- | ---------------- | ----- | ------ |
+| Host           | in            | `wiki.internal.local`   | And   | Allow  |
+| User Email     | matches regex | `.*@example.com` |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
index a7c16e3c1d91ed9..b23ff64f7475ed7 100644
--- a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
+++ b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Resolver policies](/cloudflare-one/traffic-policies/resolver-policies/) provide similar functionality to Local Domain Fallback but occur in Cloudflare Gateway rather than on the local device. This option is recommended if you want more granular control over private DNS resolution. For example, you can ensure that all users in a specific geography use the private DNS server closest to them, ensure that specific conditions are met before resolving private DNS traffic, and apply [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) to private DNS traffic.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
index 5a6e380d089015d..64bfa9b16dc161a 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When using an Allow or Block action, you can optionally [block IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category) or [filter categories for `CNAME` records](/cloudflare-one/traffic-policies/domain-categories/#ignore-cname-domain-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
index a9531e7748ee785..9fb4a6872e220df 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 The country that the request is destined for. Geolocation is determined from the target IP address. To specify a country, enter its [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                            | API example                                  |
-| ---------------------------------- | -------------------------------------------- |
+| UI name                            | API example              |
+| ---------------------------------- | ------------------------ |
 | Destination Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
index 335ee3ee0daeeca..00723a3e876eb59 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With the Device Posture selector, admins can use signals from end-user devices to secure access to their internal and external resources. For example, a security admin can choose to limit all access to internal applications based on whether specific software is installed on a device and/or if the device or software are configured in a particular way.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
index 76e61efb71ed111..843d9ab425e324b 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to DNS queries that arrived to your Gateway Resolver IP address aligned with a registered DNS location. For most Gateway customers, this is an IPv4 anycast address and policies created using this IPv4 address will apply to all DNS locations. However, each DNS location has a dedicated IPv6 address and some Gateway customers have been supplied with a dedicated IPv4 address — these both can be used to apply policies to specific registered DNS locations.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
index 526e97d2d3911fd..272bcfbd3b2eb4f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to match against DNS queries that arrive via DNS-over-HTTPS (DoH) destined for the DoH endpoint configured for each DNS location. For example, you can use a DNS location with a DoH endpoint of `abcdefg.cloudflare-gateway.com` by choosing the DoH Subdomain selector and inputting a value of `abcdefg`.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
index 4f8461929b76d11..05b18f7f521327c 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-| UI name     | API example                                                    |
-| ----------- | -------------------------------------------------------------- |
+| UI name     | API example                                     |
+| ----------- | ----------------------------------------------- |
 | OIDC Claims | `any(identity.oidc_claims[*] == "\"department=engineering\"")` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
index 588a6399b52dfb6..e61b2a18a69b641 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The protocol used to send the packet.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
index 21ddf4a78052f03..8c09fe7735b8ada 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to choose the DNS resource record type that you would like to apply policies against. For example, you can match `A` records for a domain but not `MX` records.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
index aa08d0cb5aaa69a..16aa0c58ae0be8d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to match domains (and optionally, [IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category)) belonging to specific [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
index cfc4e49bf7dcc14..f770cd8258d370f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  | Evaluation phase      |
-| ----------------------------- | -------------------------------------------- | --------------------- |
+| UI name                       | API example              | Evaluation phase      |
+| ----------------------------- | ------------------------ | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
index 18542f3726a8e3e..bea70cb9423860e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  |
-| ----------------------------- | -------------------------------------------- |
+| UI name                       | API example              |
+| ----------------------------- | ------------------------ |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
index cfc4e49bf7dcc14..f770cd8258d370f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  | Evaluation phase      |
-| ----------------------------- | -------------------------------------------- | --------------------- |
+| UI name                       | API example              | Evaluation phase      |
+| ----------------------------- | ------------------------ | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
index 2d8b06452ef3050..135f98ad365bdf1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
index 2d8b06452ef3050..135f98ad365bdf1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
index 593bd93476a3680..fee81be8110d5cb 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example value                           |
-| -------------- | ------------------------------------------- |
+| UI name    | API example value                           |
+| ---------- | ------------------------------------------- |
 | {props.UIname} | `identity.email == "user-name@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
index 7d9c06487f8bece..f1b4aa99de07338 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                                          |
-| -------------- | ---------------------------------------------------- |
-| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
index 458d7606be62bb1..719a72bec8720a8 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                                    |
-| -------------- | ---------------------------------------------- |
-| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
index 7d5f097e94c6fa9..35fe7cc1e898bed 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                             |
-| -------------- | --------------------------------------- |
-| {props.UIname} | `identity.groups.name == "\"finance\""` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.name == "\"finance\""` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
index 444ae920411c5ae..209566937c34f20 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                    |
-| -------------- | ------------------------------ |
-| {props.UIname} | `identity.name == "user-name"` |
+| UI name   | API example                    |
+| --------- | ------------------------------ |
+| {props.UIname}  | `identity.name == "user-name"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
index 253f211beb4c83e..bd7de5ffe296634 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name           | API example                                                                                                    | Evaluation phase      |
-| ----------------- | -------------------------------------------------------------------------------------------------------------- | --------------------- |
-| User Email        | `identity.email == "user@example.com"`                                                                         | Before DNS resolution |
-| User Name         | `identity.name == "Test User"`                                                                                 | Before DNS resolution |
-| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   | Before DNS resolution |
-| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               | Before DNS resolution |
-| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       | Before DNS resolution |
-| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
+| UI name         | API example                                                                                | Evaluation phase      |
+| --------------- | ------------------------------------------------------------------------------------------ | --------------------- |
+| User Email      | `identity.email == "user@example.com"`                                                     | Before DNS resolution |
+| User Name       | `identity.name == "Test User"`                                                             | Before DNS resolution |
+| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               | Before DNS resolution |
+| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           | Before DNS resolution |
+| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  | Before DNS resolution |
+| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
index e18e640ce352a0d..e963ab12286d3ee 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name           | API example                                                                                                    |
-| ----------------- | -------------------------------------------------------------------------------------------------------------- |
-| User Email        | `identity.email == "user@example.com"`                                                                         |
-| User Name         | `identity.name == "Test User"`                                                                                 |
-| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   |
-| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               |
-| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       |
-| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
+| UI name         | API example                                                                                |
+| --------------- | ------------------------------------------------------------------------------------------ |
+| User Email      | `identity.email == "user@example.com"`                                                     |
+| User Name       | `identity.name == "Test User"`                                                             |
+| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               |
+| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           |
+| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  |
+| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
index 8e62f876db500b1..ce7d5d89de6d711 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
 Identity-based selectors include:
 
-- **SAML Attributes**
-- **User Email**
-- **User Group Emails**
-- **User Group IDs**
-- **User Group Names**
-- **User Name**
+* **SAML Attributes**
+* **User Email**
+* **User Group Emails**
+* **User Group IDs**
+* **User Group Names**
+* **User Name**
 
 To use identity-based selectors, enable **Traffic and DNS mode** in the Cloudflare One Client and enroll your user in your organization. For more information, refer to [Identity-based policies](/cloudflare-one/traffic-policies/identity-selectors/).
diff --git a/src/content/partials/cloudflare-one/gateway/value.mdx b/src/content/partials/cloudflare-one/gateway/value.mdx
index 8ba2eb6529409da..a438bb02fbddee1 100644
--- a/src/content/partials/cloudflare-one/gateway/value.mdx
+++ b/src/content/partials/cloudflare-one/gateway/value.mdx
@@ -17,8 +17,8 @@ Regular expressions are evaluated using Rust. The Rust implementation is slightl
 
 If you want to match multiple values, you can use the pipe symbol (`|`) as an OR operator. You do not need to use an escape character (`\`) before the pipe symbol. For example, the following expression evaluates to true when the {props.selectordescription} matches either <code>{props.valueOne}</code> or <code>{props.valueTwo}</code>:
 
-| Selector         | Operator         | Value                                               |
-| ---------------- | ---------------- | --------------------------------------------------- |
+| Selector    | Operator        | Value          |
+| ----------- | --------------- | -------------- |
 | {props.selector} | {props.operator} | <code>{props.valueOne}&#124;{props.valueTwo}</code> |
 
 In addition to regular expressions, you can use [logical operators](#logical-operators) to match multiple values.
diff --git a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
index c8d77f235da0dee..d14d28f9b8b9303 100644
--- a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
+++ b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Posture checks** > **Service provider checks**.
 2. Select **Add a check**.
diff --git a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
index 251164d2d766ee4..38dd06ceea2f117 100644
--- a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
+++ b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
@@ -1,5 +1,6 @@
 ---
 inputParameters: param1
+
 ---
 
 Cloudflare One Client is [deployed](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) on the device. For a list of supported modes and operating systems, refer to <a href={props.link}>{props.name}</a>.
diff --git a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
index 5927c815e59262a..41541ce5b9dac6d 100644
--- a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
+++ b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
@@ -4,8 +4,8 @@
 
 To decrypt the log, follow the instructions in the [SSH Logging CLI repository](https://github.com/cloudflare/ssh-log-cli/). In the following example, `sshkey` is the private key that matches the public key uploaded to Cloudflare.
 
-```sh
-./ssh-log-cli decrypt -i sshlog -k sshkey
-```
+   ```sh
+   ./ssh-log-cli decrypt -i sshlog -k sshkey
+   ```
 
-This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
+   This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
diff --git a/src/content/partials/cloudflare-one/ssh/public-key.mdx b/src/content/partials/cloudflare-one/ssh/public-key.mdx
index 67338a0b2b7b927..6cdb18030f52db0 100644
--- a/src/content/partials/cloudflare-one/ssh/public-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/public-key.mdx
@@ -16,9 +16,9 @@
 
 3. In the `ca.pub` file, paste the public key without any modifications.
 
-   ```txt title="ca.pub"
-   ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
-   ```
+	```txt title="ca.pub"
+	ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
+	```
 
    The `ca.pub` file can hold multiple keys, listed one per line. Empty lines and comments starting with `#` are also allowed.
 
diff --git a/src/content/partials/cloudflare-one/ssh/restart-server.mdx b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
index ea942613d292e20..4e91c37de63e2e5 100644
--- a/src/content/partials/cloudflare-one/ssh/restart-server.mdx
+++ b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Tabs, TabItem, Render } from "~/components";
+import { Tabs, TabItem, Render } from "~/components"
 
 Once you have modified your `sshd` configuration, reload the SSH service on the remote machine for the changes to take effect.
 
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
index edd0dc07d1ee8a5..5117c9c548cc54c 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 :::note
 
 Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
index 667604bc9b6a4ef..15141e1a16ba29f 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
@@ -43,4 +43,4 @@ import { Render, Details, APIRequest, Tabs, TabItem } from "~/components";
 4. Copy the `public_key` value returned in the response.
 
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
index fbcdf62609e8975..35834d8c2063b23 100644
--- a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
@@ -3,7 +3,7 @@ params:
   - note
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 To log SSH commands, you will need to generate an HPKE key pair and upload the public key to Cloudflare.
 
diff --git a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
index be9833c0d225c55..2492eb7979d2109 100644
--- a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
@@ -14,161 +14,161 @@ The following configuration will modify settings in your Cloudflare account.
 
 2.  Add the following resources to `Cloudflare-config.tf`:
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            ```tf
-    
-            # Creates a new remotely-managed tunnel for the GCP VM.
-            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-            	account_id    = var.cloudflare_account_id
-            	name          = "Terraform GCP tunnel"
-            	config_src    = "cloudflare"
-            }
-    
-            # Reads the token used to run the tunnel on the server.
-            data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
-            	account_id 	= var.cloudflare_account_id
-            	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            }
-    
-            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-            resource "cloudflare_dns_record" "http_app" {
-            	zone_id = var.cloudflare_zone_id
-            	name    = "http_app"
-            	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
-            	type    = "CNAME"
-            	ttl     = 1
-            	proxied = true
-            }
-    
-            # Configures tunnel with a published application for clientless access.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-            	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            	account_id = var.cloudflare_account_id
-            	config     = {
-            		ingress 	= [
-            			{
-            				hostname = "http_app.${var.cloudflare_zone}"
-            				service  = "http://httpbin:80"
-            			},
-            			{
-            				service  = "http_status:404"
-            			}
-            		]
-            	}
-            }
-    
-            # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
-            account_id         = var.cloudflare_account_id
-            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            network            = google_compute_instance.http_server.network_interface.0.network_ip
-            comment            = "Example tunnel route"
-            }
-    
-            # Creates a reusable Access policy.
-            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-            	account_id   = var.cloudflare_account_id
-            	name         = "Allow email addresses"
-            	decision     = "allow"
-            	include      = [
-            		{
-            			email = {
-            				email = var.cloudflare_email
-            			}
-            		},
-            		{
-            			email_domain = {
-            				domain = "@example.com"
-            			}
-            		}
-            	]
-            }
-    
-            # Creates an Access application to control who can connect to the public hostname.
-            resource "cloudflare_zero_trust_access_application" "http_app" {
-            	account_id       = var.cloudflare_account_id
-            	type             = "self_hosted"
-            	name             = "Access application for http_app.${var.cloudflare_zone}"
-            	domain           = "http_app.${var.cloudflare_zone}"
-            	policies = [
-            		{
-            			id = cloudflare_zero_trust_access_policy.allow_emails.id
-            			precedence = 1
-            		}
-            	]
-            }
-            ```
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            # Generates a 32-byte secret for the tunnel.
-            resource "random_bytes" "tunnel_secret" {
-            	byte_length = 32
-            }
-    
-            # Creates a new remotely-managed tunnel for the GCP VM.
-            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-            	account_id = var.cloudflare_account_id
-            	name       = "Terraform GCP tunnel"
-            	secret     = random_bytes.tunnel_secret.base64
-            }
-    
-            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-            resource "cloudflare_record" "http_app" {
-            	zone_id = var.cloudflare_zone_id
-            	name    = "http_app"
-            	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
-            	type    = "CNAME"
-            	proxied = true
-            }
-    
-            # Configures tunnel with a published application for clientless access.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-            	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            	account_id = var.cloudflare_account_id
-            	config {
-            		ingress_rule {
-            			hostname = "${cloudflare_record.http_app.hostname}"
-            			service  = "http://httpbin:80"
-            		}
-            		ingress_rule {
-            			service  = "http_status:404"
-            		}
-            	}
-            }
-    
-            # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
-            resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
-            account_id         = var.cloudflare_account_id
-            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            network            = google_compute_instance.http_server.network_interface.0.network_ip
-            comment            = "Example tunnel route"
-            }
-    
-            # Creates an Access application to control who can connect to the public hostname.
-            resource "cloudflare_zero_trust_access_application" "http_app" {
-            	account_id          = var.cloudflare_account_id
-            	name             = "Access application for http_app.${var.cloudflare_zone}"
-            	domain           = "http_app.${var.cloudflare_zone}"
-            }
-    
-            # Creates a (legacy) Access policy for the Access application.
-            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-            	application_id = cloudflare_zero_trust_access_application.http_app.id
-            	account_id        = var.cloudflare_account_id
-            	name           = "Example policy for http_app.${var.cloudflare_zone}"
-            	precedence     = "1"
-            	decision       = "allow"
-            	include {
-            		email = [var.cloudflare_email]
-            	}
-            }
-            ```
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        ```tf
+
+        # Creates a new remotely-managed tunnel for the GCP VM.
+        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+        	account_id    = var.cloudflare_account_id
+        	name          = "Terraform GCP tunnel"
+        	config_src    = "cloudflare"
+        }
+
+        # Reads the token used to run the tunnel on the server.
+        data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
+        	account_id 	= var.cloudflare_account_id
+        	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        }
+
+        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+        resource "cloudflare_dns_record" "http_app" {
+        	zone_id = var.cloudflare_zone_id
+        	name    = "http_app"
+        	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
+        	type    = "CNAME"
+        	ttl     = 1
+        	proxied = true
+        }
+
+        # Configures tunnel with a published application for clientless access.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+        	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        	account_id = var.cloudflare_account_id
+        	config     = {
+        		ingress 	= [
+        			{
+        				hostname = "http_app.${var.cloudflare_zone}"
+        				service  = "http://httpbin:80"
+        			},
+        			{
+        				service  = "http_status:404"
+        			}
+        		]
+        	}
+        }
+
+        # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
+        account_id         = var.cloudflare_account_id
+        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        network            = google_compute_instance.http_server.network_interface.0.network_ip
+        comment            = "Example tunnel route"
+        }
+
+        # Creates a reusable Access policy.
+        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+        	account_id   = var.cloudflare_account_id
+        	name         = "Allow email addresses"
+        	decision     = "allow"
+        	include      = [
+        		{
+        			email = {
+        				email = var.cloudflare_email
+        			}
+        		},
+        		{
+        			email_domain = {
+        				domain = "@example.com"
+        			}
+        		}
+        	]
+        }
+
+        # Creates an Access application to control who can connect to the public hostname.
+        resource "cloudflare_zero_trust_access_application" "http_app" {
+        	account_id       = var.cloudflare_account_id
+        	type             = "self_hosted"
+        	name             = "Access application for http_app.${var.cloudflare_zone}"
+        	domain           = "http_app.${var.cloudflare_zone}"
+        	policies = [
+        		{
+        			id = cloudflare_zero_trust_access_policy.allow_emails.id
+        			precedence = 1
+        		}
+        	]
+        }
+        ```
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        # Generates a 32-byte secret for the tunnel.
+        resource "random_bytes" "tunnel_secret" {
+        	byte_length = 32
+        }
+
+        # Creates a new remotely-managed tunnel for the GCP VM.
+        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+        	account_id = var.cloudflare_account_id
+        	name       = "Terraform GCP tunnel"
+        	secret     = random_bytes.tunnel_secret.base64
+        }
+
+        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+        resource "cloudflare_record" "http_app" {
+        	zone_id = var.cloudflare_zone_id
+        	name    = "http_app"
+        	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
+        	type    = "CNAME"
+        	proxied = true
+        }
+
+        # Configures tunnel with a published application for clientless access.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+        	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        	account_id = var.cloudflare_account_id
+        	config {
+        		ingress_rule {
+        			hostname = "${cloudflare_record.http_app.hostname}"
+        			service  = "http://httpbin:80"
+        		}
+        		ingress_rule {
+        			service  = "http_status:404"
+        		}
+        	}
+        }
+
+        # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
+        resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
+        account_id         = var.cloudflare_account_id
+        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        network            = google_compute_instance.http_server.network_interface.0.network_ip
+        comment            = "Example tunnel route"
+        }
+
+        # Creates an Access application to control who can connect to the public hostname.
+        resource "cloudflare_zero_trust_access_application" "http_app" {
+        	account_id          = var.cloudflare_account_id
+        	name             = "Access application for http_app.${var.cloudflare_zone}"
+        	domain           = "http_app.${var.cloudflare_zone}"
+        }
+
+        # Creates a (legacy) Access policy for the Access application.
+        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+        	application_id = cloudflare_zero_trust_access_application.http_app.id
+        	account_id        = var.cloudflare_account_id
+        	name           = "Example policy for http_app.${var.cloudflare_zone}"
+        	precedence     = "1"
+        	decision       = "allow"
+        	include {
+        		email = [var.cloudflare_email]
+        	}
+        }
+        ```
+        </TabItem>
+        </Tabs>
 
 To learn more about these resources, refer to the [Cloudflare provider documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
diff --git a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
index e21650fa17456a6..4eca7f0c1b7957c 100644
--- a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
@@ -14,88 +14,88 @@ The following configuration defines the specifications for the GCP virtual machi
 
 2.  Add the following content to `GCP-config.tf`:
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            ```tf
-            # OS the server will use
-            data "google_compute_image" "image" {
-            	family  = "ubuntu-2204-lts"
-            	project = "ubuntu-os-cloud"
-            }
-    
-            # GCP Instance resource
-            resource "google_compute_instance" "http_server" {
-            	name         = "test"
-            	machine_type = var.machine_type
-            	zone         = var.zone
-            	tags         = []
-            	boot_disk {
-            		initialize_params {
-            			image = data.google_compute_image.image.self_link
-            		}
-            	}
-    
-            	network_interface {
-            		network = "default"
-            		access_config {
-            			//Ephemeral IP
-            		}
-            	}
-            	// Optional config to make instance ephemeral
-            /*  scheduling {
-            		preemptible       = true
-            		automatic_restart = false
-            	} */
-    
-            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-            		{
-            			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
-            		})
-            }
-            ```
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            # OS the server will use
-            data "google_compute_image" "image" {
-            	family  = "ubuntu-2204-lts"
-            	project = "ubuntu-os-cloud"
-            }
-    
-            # GCP Instance resource
-            resource "google_compute_instance" "http_server" {
-            	name         = "test"
-            	machine_type = var.machine_type
-            	zone         = var.zone
-            	tags         = []
-            	boot_disk {
-            		initialize_params {
-            			image = data.google_compute_image.image.self_link
-            		}
-            	}
-    
-            	network_interface {
-            		network = "default"
-            		access_config {
-            			//Ephemeral IP
-            		}
-            	}
-            	// Optional config to make instance ephemeral
-            /*  scheduling {
-            		preemptible       = true
-            		automatic_restart = false
-            	} */
-    
-            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-            		{
-            			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
-            		})
-            }
-            ```
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        ```tf
+        # OS the server will use
+        data "google_compute_image" "image" {
+        	family  = "ubuntu-2204-lts"
+        	project = "ubuntu-os-cloud"
+        }
+
+        # GCP Instance resource
+        resource "google_compute_instance" "http_server" {
+        	name         = "test"
+        	machine_type = var.machine_type
+        	zone         = var.zone
+        	tags         = []
+        	boot_disk {
+        		initialize_params {
+        			image = data.google_compute_image.image.self_link
+        		}
+        	}
+
+        	network_interface {
+        		network = "default"
+        		access_config {
+        			//Ephemeral IP
+        		}
+        	}
+        	// Optional config to make instance ephemeral
+        /*  scheduling {
+        		preemptible       = true
+        		automatic_restart = false
+        	} */
+
+        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+        		{
+        			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
+        		})
+        }
+        ```
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        # OS the server will use
+        data "google_compute_image" "image" {
+        	family  = "ubuntu-2204-lts"
+        	project = "ubuntu-os-cloud"
+        }
+
+        # GCP Instance resource
+        resource "google_compute_instance" "http_server" {
+        	name         = "test"
+        	machine_type = var.machine_type
+        	zone         = var.zone
+        	tags         = []
+        	boot_disk {
+        		initialize_params {
+        			image = data.google_compute_image.image.self_link
+        		}
+        	}
+
+        	network_interface {
+        		network = "default"
+        		access_config {
+        			//Ephemeral IP
+        		}
+        	}
+        	// Optional config to make instance ephemeral
+        /*  scheduling {
+        		preemptible       = true
+        		automatic_restart = false
+        	} */
+
+        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+        		{
+        			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
+        		})
+        }
+        ```
+        </TabItem>
+        </Tabs>
diff --git a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
index 5afae47ec52d2f1..cda294b702f2e15 100644
--- a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
@@ -25,4 +25,4 @@ provider "google" {
 }
 provider "random" {
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/terraform/providers.mdx b/src/content/partials/cloudflare-one/terraform/providers.mdx
index 962ef714f4ec1c3..113455091a647e1 100644
--- a/src/content/partials/cloudflare-one/terraform/providers.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers.mdx
@@ -14,41 +14,41 @@ You will need to declare the [providers](https://registry.terraform.io/browse/pr
 
 2.  Add the following providers to `providers.tf`. The `random` provider is used to generate a tunnel secret.
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            <Render file="terraform/providers-v5" product="cloudflare-one" />
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            terraform {
-            	required_providers {
-            		cloudflare = {
-            			source = "cloudflare/cloudflare"
-            			version = ">= 4.40.0, < 5.0.0"
-            		}
-            		google = {
-            			source = "hashicorp/google"
-            		}
-            		random = {
-            			source = "hashicorp/random"
-            		}
-            	}
-            	required_version = ">= 1.2"
-            }
-    
-            # Providers
-            provider "cloudflare" {
-            	api_token    = var.cloudflare_token
-            }
-            provider "google" {
-            	project    = var.gcp_project_id
-            }
-            provider "random" {
-            }
-            ```
-    
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        <Render file="terraform/providers-v5" product="cloudflare-one" />
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        terraform {
+        	required_providers {
+        		cloudflare = {
+        			source = "cloudflare/cloudflare"
+        			version = ">= 4.40.0, < 5.0.0"
+        		}
+        		google = {
+        			source = "hashicorp/google"
+        		}
+        		random = {
+        			source = "hashicorp/random"
+        		}
+        	}
+        	required_version = ">= 1.2"
+        }
+
+        # Providers
+        provider "cloudflare" {
+        	api_token    = var.cloudflare_token
+        }
+        provider "google" {
+        	project    = var.gcp_project_id
+        }
+        provider "random" {
+        }
+        ```
+
+        </TabItem>
+        </Tabs>
diff --git a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
index 6abc149ee79e338..a68729e1c588fba 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -3,37 +3,31 @@ Review common troubleshooting scenarios for Cloudflare Browser Isolation.
 ## Connectivity and sessions
 
 ### No Browsers Available
-
 If you encounter a `No Browsers Available` alert, please file feedback via the Cloudflare One Client. This error typically indicates a temporary capacity issue in the data center or a connectivity problem between your client and the remote browser.
 
 ### Maximum Sessions Reached
-
 This alert appears if your device attempts to establish more than two concurrent remote browser instances. A browser isolation session is shared across all tabs and windows within the same browser (for example, all Chrome tabs share one session). You can use two different browsers (such as Chrome and Firefox) concurrently, but opening a third will trigger this alert. To release a session, close all tabs and windows in one of your local browsers.
 
 ## Rendering and performance
 
 ### WebGL Rendering Error
-
 Cloudflare Browser Isolation uses Network Vector Rendering (NVR), which does not support WebGL (Web Graphics Library) in all environments. If a website requires WebGL and your device lacks the necessary hardware resources in the virtualized environment, you may see a rendering error.
 
 To resolve this, try enabling software rasterization in your browser:
-
 1. Go to `chrome://flags/#override-software-rendering-list`.
-2. Set **Override software rendering list** to _Enabled_.
+2. Set **Override software rendering list** to *Enabled*.
 3. Select **Relaunch**.
 
 ### Blank screen on Windows
-
 On Windows devices, Clientless Web Isolation may load with a blank screen if there is a conflict between browser mDNS settings and Windows IGMP configuration.
 
-| IGMPLevel    | WebRTC Anonymization | Result          |
-| ------------ | -------------------- | --------------- |
-| 0 (disabled) | Enabled / Default    | ❌ Blank screen |
-| 0 (disabled) | Disabled             | ✅ Works        |
-| 2 (enabled)  | Enabled / Default    | ✅ Works        |
+| IGMPLevel | WebRTC Anonymization | Result |
+| --------- | -------------------- | ------ |
+| 0 (disabled) | Enabled / Default | ❌ Blank screen |
+| 0 (disabled) | Disabled | ✅ Works |
+| 2 (enabled) | Enabled / Default | ✅ Works |
 
 To fix this, either disable **Anonymize local IPs exposed by WebRTC** in your browser flags or ensure `IGMPLevel` is enabled (set to `2`) in your Windows network settings.
 
 ### Rendering issues (CSS/Images)
-
 If a website displays incorrectly (for example, broken CSS or missing images), it may indicate that the remote browser is unable to fetch specific resources from the origin server. Check your [Gateway HTTP logs](/cloudflare-one/traffic-policies/troubleshooting/) for any blocked subresources that might be required by the page.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
index ea6662dd6b23a61..812e31a9e577986 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
@@ -3,17 +3,13 @@ Use this guide to troubleshoot common issues with Cloud Access Security Broker (
 ## Security findings
 
 ### Findings not appearing
-
 If you do not see findings for an integrated application:
-
 - **Wait for scan**: Initial scans can take up to 24 hours depending on the size of the application.
 - **Permissions**: Ensure the account used to integrate the application has the necessary administrative permissions.
 - **Enabled status**: Verify that the integration is enabled in the Zero Trust dashboard.
 
 ### False positives
-
 If CASB flags a configuration that is intended for your organization:
-
 1. Go to **CASB** &gt; **Findings**.
 2. Select the finding and choose **Dismiss**.
 3. Provide a reason for dismissal to help refine future scans.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
index b0b9af1de6363da..d9f76c11a762d23 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
@@ -3,7 +3,6 @@ Review common troubleshooting scenarios for Digital Experience Monitoring (DEX).
 ## Data visibility
 
 ### No data displayed for certain users
-
 If you do not see DEX data for specific users in your organization, verify the following:
 
 - **Client version**: Ensure the users are running a version of the Cloudflare One Client that supports DEX.
@@ -11,13 +10,11 @@ If you do not see DEX data for specific users in your organization, verify the f
 - **Traffic routing**: DEX requires that traffic to Cloudflare's orchestration API is not blocked by local firewalls or SSL-inspecting proxies.
 
 ### Fleet status not updating
-
 The Fleet status dashboard can take several minutes to reflect changes in device connectivity. If a device remains in an incorrect state, try disconnecting and reconnecting the Cloudflare One Client to force a status update.
 
 ## Remote captures
 
 ### Remote capture fails to start
-
 Remote captures require the Cloudflare One Client to be connected and able to communicate with the Cloudflare control plane. If a capture fails to start:
 
 - Verify the device status in the Zero Trust dashboard.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
index 500c1dc89b9f0c0..77aac5be079b8ae 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
@@ -4,51 +4,44 @@ Review common troubleshooting scenarios for Cloudflare Email Security.
 
 Email Security identifies threats using detections that result in a final disposition. You can inspect email headers to understand why a specific disposition was applied.
 
-| Attribute           | Description                                                                                                                                 |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list.                                                                                          |
-| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain.                                                                                          |
-| `NEW_DOMAIN_LINK`   | The email contains links to a newly registered domain.                                                                                      |
-| `ENCRYPTED`         | The email message is encrypted.                                                                                                             |
-| `BEC`               | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
+| Attribute | Description |
+| --------- | ----------- |
+| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list. |
+| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain. |
+| `NEW_DOMAIN_LINK` | The email contains links to a newly registered domain. |
+| `ENCRYPTED` | The email message is encrypted. |
+| `BEC` | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
 
 ## Detections and reclassification
 
 ### Handle a false positive
-
-A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam.
+A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam. 
 
 **Solution**:
-
 1. In the Email Security dashboard, go to **Investigation**.
 2. Find the email and select **Submit for reclassification**.
 3. Choose the correct disposition (for example, `Clean`).
 4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) list.
 
 ### Handle a false negative
-
 A false negative occurs when a malicious email is not detected by Email Security.
 
 **Solution**:
-
 1. Ensure the email actually passed through Email Security by checking for the `X-CFEmailSecurity-Disposition` header.
 2. Submit the email for reclassification in the dashboard. This is the preferred method for reporting missed detections.
 
 ## Authentication errors
 
 ### DMARC failures
-
 Email Security may mark an email as **SPAM** if it fails DMARC authentication and the sending domain has a `p=reject` or `p=quarantine` policy.
 
 **Solution**:
-
 - Ask the sender to fix their DMARC/SPF/DKIM records.
 - Configure an [Acceptable Sender](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) entry to suppress the failure for that specific sender.
 
 ## Delivery issues
 
 ### Emails are delayed or not arriving
-
 If emails are not being delivered or are arriving with significant latency:
 
 1. **Check MX records**: Ensure your [MX records](/cloudflare-one/email-security/setup/) are correctly configured and pointing to Cloudflare.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
index 9aa7ada94a6a62d..a5dd284025e9f77 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
@@ -3,11 +3,9 @@ This guide helps you troubleshoot common issues with Cloudflare Gateway policies
 ## Blocked websites and connectivity
 
 ### A website is blocked incorrectly
-
 If you believe a domain has been incorrectly blocked by Gateway's security categories or threat intelligence, you can use the [Cloudflare Radar categorization feedback form](https://radar.cloudflare.com/categorization-feedback/) to request a review.
 
 ### Error 526: Invalid SSL certificate
-
 Gateway presents a **526** error page when it cannot establish a secure connection to the origin. This typically occurs in two cases:
 
 - **Untrusted origin certificate**: The certificate presented by the origin server is expired, revoked, or issued by an unknown authority.
@@ -16,17 +14,14 @@ Gateway presents a **526** error page when it cannot establish a secure connecti
 For more information, refer to [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ### Error 502: Bad Gateway
-
 This issue can occur when communicating with an origin that partially supports HTTP/2. If the origin requests a downgrade to HTTP/1.1 (for example, via a `RST_STREAM` frame with `HTTP_1_1_REQUIRED`), Gateway will not automatically reissue the request over HTTP/1.1 and will instead return a `502 Bad Gateway`. To resolve this, disable HTTP/2 at the origin server.
 
 ### Untrusted certificate warnings
-
 If users see certificate warnings for every page, ensure that the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) is installed and trusted on their devices. This is required for Gateway to inspect HTTPS traffic.
 
 ## Dashboard and analytics
 
 ### Gateway analytics not displayed
-
 If you do not see analytics on the Gateway Overview page:
 
 - **Verify DNS traffic**: Ensure your devices are actually sending queries to Gateway. Check your [DNS locations](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) and verify the source IPv4 address.
@@ -131,8 +126,8 @@ To resolve this issue:
 
 You have configured Gateway to resolve internal hostnames, but users are unable to access them. For example, a user connected to the Cloudflare One Client tries to access an internal service like `jira.mycompany.local`, but the DNS query fails.
 
-| Common causes                              | Solution                                                                                                                                                                                                                                       |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                                               |
+| Common causes                              | Solution                                                                                                                                                                                                                  |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                             |
 | Split Tunnel excludes the private IP range | If your internal resources are in a private IP range (such as `10.0.0.0/8`), that range must be included in the tunnel. If it is in the Exclude list of your Split Tunnel configuration, the Cloudflare One Client will not proxy the traffic. |
-| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                                           |
+| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                      |
diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
index 0a544adaa854c9b..bec8b880edeb7cc 100644
--- a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Render } from "~/components";
@@ -8,4 +9,4 @@ A `1033` error indicates your tunnel is not connected to Cloudflare's network be
 
 First, review whether your tunnel is listed as `Active` in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status:
 
-<Render file="tunnel/tunnel-status" product="cloudflare-one" />
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
index b4d07916659c2d7..cf11d2740614eac 100644
--- a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
@@ -1,12 +1,11 @@
 ---
 {}
+
 ---
 
 Minimum permissions needed to create, delete, and configure tunnels for an account:
-
 - [Cloudflare Access](/cloudflare-one/roles-permissions/)
 
 Additional permissions needed to [route traffic to a public hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) and to be able to perform `cloudflared login`:
-
 - [DNS](/fundamentals/manage-members/roles/)
-- [Load Balancer](/fundamentals/manage-members/roles/)
+- [Load Balancer](/fundamentals/manage-members/roles/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
index 49599f43b544a2f..7df9b2e5a62c416 100644
--- a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To add a published application when creating a new tunnel:
@@ -7,16 +8,16 @@ To add a published application when creating a new tunnel:
 1. Go to the **Published applications** tab.
 
 2. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
+	:::note
+	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+	:::
 
 3. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example,
-   - **Type**: _HTTP_
-   - **URL**: `localhost:8000`
+	- **Type**: _HTTP_
+	- **URL**: `localhost:8000`
 
 4. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
    ![Example of a published application route in the Cloudflare One dashboard](~/assets/images/cloudflare-one/connections/connect-apps/published-app.png)
 
-5. Select **Save**.
+5. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
index 10f16e4d43c7afe..b070a82d446402e 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
index ceda180a2994ca9..00915193311f7b7 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
@@ -5,9 +5,10 @@ params:
 
 TCP monitors are not supported for tunnel endpoints. Instead, create a health check endpoint on the `cloudflared` host and use an HTTPS monitor. For example, you can use `cloudflared` to return a fixed HTTP status response:
 
-1. <a href={props.publishedAppRouteURL}>Add a published application route</a>
-   for the health check: - **Hostname**: `health-check.example.com` - **Service
-   Type**: _HTTP_STATUS_ - **HTTP Status Code**: `200`
+1. <a href={props.publishedAppRouteURL}>Add a published application route</a> for the health check:
+   - **Hostname**: `health-check.example.com`
+   - **Service Type**: _HTTP_STATUS_
+   - **HTTP Status Code**: `200`
 2. [Create a monitor](/load-balancing/monitors/create-monitor/) with these settings:
    - **Type**: _HTTPS_
    - **Path**: `/`
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
index a96ead9f4e833cc..f61bde5fb1a3556 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
-- Size each host with minimum 4GB of RAM and 4 CPU cores.
-- Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
+* Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
+* Size each host with minimum 4GB of RAM and 4 CPU cores.
+* Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
 
 This setup is usually sufficient to handle traffic from 8,000 users (4,000 per host).
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
index 399600466878e2a..e38f3ea59068e4a 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Unlike legacy VPNs where throughput is determined by the server's memory, CPU and other hardware specifications, Cloudflare Tunnel throughput is primarily limited by the number of ports configured in system software. Therefore, when sizing your `cloudflared` server, the most important element is sizing the available ports on the machine to reflect the expected throughput of TCP and UDP traffic.
diff --git a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
index d3d57f5ddd564cf..c4aa95aa270a7b2 100644
--- a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
@@ -3,3 +3,4 @@
 ---
 
 To prevent Cloudflare One Client users from accessing your entire private network, we recommend creating a [catch-all Gateway block policy](/learning-paths/replace-vpn/build-policies/create-policy/#catch-all-policy) for your private IP space. You can then layer on higher priority Allow policies (in either Access or Gateway) which grant users access to specific applications or IPs.
+
diff --git a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
index 836d5c4e7335fae..32bad08d6a11538 100644
--- a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
@@ -1,4 +1,5 @@
 ---
+
 ---
 
 In your device profile, configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) goes through the WARP tunnel. Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode). For example, if your devices use the default `100.96.0.0/12` range:
diff --git a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
index c90519fd3fb9a8e..6c082731f7502d1 100644
--- a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
@@ -18,4 +19,4 @@
 
    ![Connector appearing in the UI after cloudflared has run](~/assets/images/cloudflare-one/connections/connect-apps/connector.png)
 
-8. Select **Next**.
+8. Select **Next**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
index 4836708c394928a..0f7caefc4aa0c56 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Create a Cloudflare Tunnel in Cloudflare One and run the tunnel on the {props.one}.
 
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
index 061651ac15df2a8..2f6208021fb86bc 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
@@ -11,17 +11,17 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 2.  In the **CIDR** tab, enter the **Private IP address** of your {props.resourceName} (for example, <code>{props.exampleIp}</code>). You can expand the IP range later if necessary.
 3.  In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through the Cloudflare One Client. For example, if you are using Split Tunnels in **Exclude** mode, delete <code>{props.splitTunnelCidr}</code>. We recommend re-adding the IPs that are not explicitly used by your {props.resourceName}.
 
-    To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
-    
-    <SubtractIPCalculator
-    	client:load
-    	defaults={{
-    		base: props.splitTunnelCidr,
-    		subtract: props.calcExclude
-    	}}
-    />
-    
-    Add the results back to your Split Tunnel Exclude mode list.
+        To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
+
+        <SubtractIPCalculator
+        	client:load
+        	defaults={{
+        		base: props.splitTunnelCidr,
+        		subtract: props.calcExclude
+        	}}
+        />
+
+        Add the results back to your Split Tunnel Exclude mode list.
 
 4.  To test on a user device:
     1. [Log in to the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/).
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
index 170049a7ac5f7c8..9e70a1198bb9fb7 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Published applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) allow anyone on the Internet to connect to HTTP resources hosted on your virtual private cloud (VPC). To add a published application for your Cloudflare Tunnel:
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
index 6980de61dec14cf..4f15318c29c1162 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
@@ -24,30 +24,15 @@ params:
 
    ```json
    {
-   	"tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
-   	"connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
-   	"connections": [
-   		{ "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167" },
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.200.113",
-   			"index": 1
-   		},
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.192.47",
-   			"index": 2
-   		},
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.200.73",
-   			"index": 3
-   		}
-   	],
-   	"icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
+     "tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
+     "connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
+     "connections": [
+       { "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167"},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.113", "index": 1},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.47", "index": 2},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.73", "index": 3}
+     ],
+     "icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
    }
    ```
 
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
index af11a9afb297c8f..35a23d38040988e 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
@@ -8,18 +8,18 @@ params:
 
 The `cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.
 
-| File name                | Description                                                                              | Instance  |
-| ------------------------ | ---------------------------------------------------------------------------------------- | --------- |
+| File name                | Description                                                                                                                                                  | Instance  |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
 | `cli-configuration.json` | <a href={props.runParametersURL}>Tunnel run parameters</a> used when starting the tunnel | diagnosee |
-| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                          | diagnosee |
-| `configuration.json`     | Tunnel configuration parameters                                                          | diagnosee |
-| `goroutine.pprof`        | goroutine profile made available by `pprof`                                              | diagnosee |
-| `heap.pprof`             | heap profile made available by `pprof`                                                   | diagnosee |
-| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis       | diagnosee |
-| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                      | diagnoser |
-| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                       | diagnoser |
-| `systeminformation.json` | Operating system information and resource usage                                          | diagnosee |
-| `task-result.json`       | Result of each diagnostic task                                                           | diagnoser |
-| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                              | diagnosee |
+| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                                                    | diagnosee |
+| `configuration.json`     | Tunnel configuration parameters                                                                                                                              | diagnosee |
+| `goroutine.pprof`        | goroutine profile made available by `pprof`                                                                                                                  | diagnosee |
+| `heap.pprof`             | heap profile made available by `pprof`                                                                                                                       | diagnosee |
+| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis               | diagnosee |
+| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                          | diagnoser |
+| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                           | diagnoser |
+| `systeminformation.json` | Operating system information and resource usage                                                                                                              | diagnosee |
+| `task-result.json`       | Result of each diagnostic task                                                                                                                               | diagnoser |
+| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                                                                                                  | diagnosee |
 
 [^1]: If the log file is blank, you may need to <a href={props.loglevelURL}>set `--loglevel` to `debug`</a> when you start the tunnel. The `--loglevel` parameter is only required if you ran the tunnel from the CLI using a `cloudflared tunnel run` command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes.
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
index e8c007b9d69d74c..2f2327ca51fb9e4 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Published applications inherit the Cloudflare settings for their hostname, including [cache rules](/cache/how-to/cache-rules/), [WAF rules](/waf/), and other [Rules](/rules/) configurations. You can change these settings for each hostname in the [Cloudflare dashboard](https://dash.cloudflare.com/).
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
index 6e023ea0564f577..f3c26351bc152ee 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you create a tunnel, Cloudflare generates a subdomain at `<UUID>.cfargotunnel.com`. You point a CNAME record at this subdomain to route traffic from your hostname to the tunnel.
diff --git a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
index 5fb221e26749de9..ad172f22cfae0ee 100644
--- a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Tunnel supports gRPC traffic via [private subnet routing](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/). Public hostname deployments are not currently supported.
diff --git a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
index 91d158683723dd9..da5faccbdab0cc8 100644
--- a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
@@ -5,16 +5,13 @@
 import { Details } from "~/components";
 
 <Details header="Hostname format restrictions">
-	- **Character limit:** Must be less than 255 characters. - **Supported
-	wildcards:** A single wildcard (`*`) is allowed, and it must represent a full
-	DNS label. Example: `*.internal.local` - **Unsupported wildcards:** The
-	following wildcard formats are not supported: - Partial wildcards such as
-	`*-dev.internal.local` or `dev-*.internal.local`. - Wildcards in the middle,
-	such as `foo*bar.internal.local` or `foo.*.internal.local`. - Multiple
-	wildcards in the hostname, such as `*.*.internal.local`. - **Wildcard
-	trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`)
-	is assumed. For example, `*.internal.local` is saved as `internal.local` but
-	will match all subdomains at the wildcard level (covers `foo.internal.local`
-	but not `foo.bar.internal.local`). - **Dot trimming:** Leading and ending dots
-	(`.`) are allowed but trimmed off.
+- **Character limit:** Must be less than 255 characters.
+- **Supported wildcards:** A single wildcard (`*`) is allowed, and it must represent a full DNS label.
+			Example: `*.internal.local`
+- **Unsupported wildcards:** The following wildcard formats are not supported:
+		- Partial wildcards such as `*-dev.internal.local` or `dev-*.internal.local`.
+		- Wildcards in the middle, such as `foo*bar.internal.local` or `foo.*.internal.local`.
+		- Multiple wildcards in the hostname, such as `*.*.internal.local`.
+- **Wildcard trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`) is assumed. For example, `*.internal.local` is saved as `internal.local` but will match all subdomains at the wildcard level (covers `foo.internal.local` but not `foo.bar.internal.local`).
+- **Dot trimming:** Leading and ending dots (`.`) are allowed but trimmed off.
 </Details>
diff --git a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
index 660cd5d5f759ab9..221f41fda76b716 100644
--- a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -46,4 +47,4 @@ import { Tabs, TabItem } from "~/components";
         	docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <TUNNEL_TOKEN>
         	```
 
-</TabItem>  </Tabs>
+</TabItem>  </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
index 4fdc32d904e2241..3e1b6567d49585d 100644
--- a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
@@ -12,16 +12,16 @@ Tunnel permissions determine who can run and manage a Cloudflare Tunnel. Two fil
 
 Refer to the table below for a comparison between the two files and the purposes for which they are intended.
 
-|                         | Account certificate                                                                                        | Tunnel credential                                         |
-| ----------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
-| **File name**           | `cert.pem`                                                                                                 | `<TUNNEL-UUID>.json`                                      |
-| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account                               | Authenticates the tunnel it is associated with            |
-| **Scope**               | Account-wide                                                                                               | Tunnel-specific                                           |
-| **File type**           | `.pem`                                                                                                     | `.json`                                                   |
-| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                                                  | <a href={props.defaultDirectoryURL}>Default directory</a> |
-| **Issued when running** | `cloudflared tunnel login`                                                                                 | `cloudflared tunnel create <NAME>`                        |
-| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate) | Does not expire                                           |
-| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)                                       | Run a tunnel. Create a config file.                       |
+|                         | Account certificate                                                          | Tunnel credential                                         |
+| ----------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------- |
+| **File name**           | `cert.pem`                                                                   | `<TUNNEL-UUID>.json`                                      |
+| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account | Authenticates the tunnel it is associated with            |
+| **Scope**               | Account-wide                                                                 | Tunnel-specific                                           |
+| **File type**           | `.pem`                                                                       | `.json`                                                   |
+| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                    | <a href={props.defaultDirectoryURL}>Default directory</a> |
+| **Issued when running** | `cloudflared tunnel login`                                                   | `cloudflared tunnel create <NAME>`                        |
+| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate)  | Does not expire                                           |
+| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)         | Run a tunnel. Create a config file.                       |
 
 ## Tunnel ownership
 
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
index c3f3293198255e7..6c50a4d38d46d4a 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
@@ -9,8 +9,8 @@ You can filter logs by event type (`--event`), event level (`--level`), or sampl
 cloudflared tail --level debug <UUID>
 ```
 
-| Flag         | Description                                                                                                                         | Allowed values                            | Default value |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
-| `--event`    | Filter by the type of event / request.                                                                                              | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
+| Flag         | Description                                                                                                                                                                                           | Allowed values                            | Default value |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
+| `--event`    | Filter by the type of event / request.                                                                                                                                                                | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
 | `--level`    | Return logs at this level and above. Works independently of the <a href={props.loglevelURL}>`--loglevel`</a> setting on the server. | `debug`, `info`, `warn`, `error`, `fatal` | `debug`       |
-| `--sampling` | Sample a fraction of the total logs.                                                                                                | Number from `0.0` to `1.0`                | `1.0`         |
+| `--sampling` | Sample a fraction of the total logs.                                                                                                                                                                  | Number from `0.0` to `1.0`                | `1.0`         |
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
index 7e5b276368ef811..9199c7ed894a76f 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
@@ -3,6 +3,7 @@
 
 import { GlossaryTooltip } from "~/components";
 
+
 Dashboard log streams are only available for <GlossaryTooltip term="remotely-managed tunnel">remotely-managed tunnels</GlossaryTooltip>. To stream tunnel logs from the dashboard:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
index c5d8a1638544701..323c86b55d57992 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
@@ -12,3 +12,4 @@ To enable logs, <a href={props.runParametersURL}>run the tunnel</a> using the `-
 ```sh
 cloudflared tunnel --loglevel info --logfile cloudflared.log run <UUID>
 ```
+
diff --git a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
index bdc546346c31fc1..4e0fc2c84e7e66e 100644
--- a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
@@ -19,7 +19,7 @@
 | `cloudflared_tunnel_tunnel_authenticate_success`    | Number of successful tunnel authentication events.                                                         | COUNTER |                                            |
 | `cloudflared_tunnel_tunnel_register_success`        | Number of successful tunnel registrations.                                                                 | COUNTER | `rpcName`                                  |
 | `cloudflared_udp_active_sessions`                   | Concurrent number of UDP sessions that are being proxied to any origin.                                    | GAUGE   |                                            |
-| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER |                                            |
+| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER   |                                            |
 | `coredns_panics_total`                              | Number of panics.                                                                                          | COUNTER |                                            |
 | `quic_client_closed_connections`                    | Number of connections that have been closed.                                                               | COUNTER |                                            |
 | `quic_client_latest_rtt`                            | Latest round-trip time (RTT) measured on a connection.                                                     | GAUGE   | `conn_index`                               |
diff --git a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
index 1b6b39f6f1a5fda..000cf30ab14fdcb 100644
--- a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
@@ -132,8 +132,8 @@ When `true`, Happy Eyeballs is disabled.
 `cloudflared` starts a proxy server to translate HTTP traffic into TCP when proxying, for example, SSH or RDP.
 This configures what type of proxy will be started. Valid options are:
 
-- `""` for the regular proxy
-- `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
+* `""` for the regular proxy
+* `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
 
 ### proxyAddress
 
diff --git a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
index 53e2484f9439265..2fd27a10bd6f00a 100644
--- a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
+You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
index b0e9a72f30f6267..9bed10dd3b8e8ea 100644
--- a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
@@ -6,19 +6,19 @@ params:
 
 The table below lists the service types you can route to a public hostname. Non-HTTP services require [installing `cloudflared` on the client](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/) for end users to connect.
 
-| Service type | Description                                                                                                                                                                                                                                                                                                                                                    | Example `service` value               |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
-| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP.                                                                                                                                                                                                                                                                                           | `http://localhost:8000`               |
-| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates.                                                                                                                                                                               | `https://localhost:8000`              |
-| UNIX         | Same as HTTP, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                          | `unix:/home/production/echo.sock`     |
-| UNIX + TLS   | Same as HTTPS, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                         | `unix+tls:/home/production/echo.sock` |
-| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead.                     | `tcp://localhost:2222`                |
-| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22`                  |
-| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/).                                                                                                                                    | `rdp://localhost:3389`                |
-| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access).                                                                                                                     | `smb://localhost:445`                 |
-| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code.                                                                                                                                                                                                                                                                                                        | `http_status:404`                     |
-| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address.                                                                                                                                                                                                                                                                             | `bastion`                             |
-| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only).                                                                                                                                                                                                                  | `hello_world`                         |
+| Service type | Description | Example `service` value |
+| ------------ | ----------- | ----------------------- |
+| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP. | `http://localhost:8000` |
+| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates. | `https://localhost:8000` |
+| UNIX         | Same as HTTP, but uses a Unix socket. | `unix:/home/production/echo.sock` |
+| UNIX + TLS   | Same as HTTPS, but uses a Unix socket. | `unix+tls:/home/production/echo.sock` |
+| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead. | `tcp://localhost:2222` |
+| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22` |
+| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/). | `rdp://localhost:3389` |
+| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access). | `smb://localhost:445` |
+| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code. | `http_status:404` |
+| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address. | `bastion` |
+| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only). | `hello_world` |
 
 ## IPv6 service addresses
 
diff --git a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
index effd28c88ed8811..05449ecd0346b32 100644
--- a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
@@ -171,9 +171,9 @@ Specifies the path to a <a href={props.configurationFileURL}>configuration file<
 Requires `cloudflared` version 2025.7.0 or later.
 :::
 
-| Syntax                                                                 | Environment Variable        |
-| ---------------------------------------------------------------------- | --------------------------- |
-| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>` | `TUNNEL_DNS_RESOLVER_ADDRS` |
+| Syntax                                                                    | Environment Variable        |
+| ------------------------------------------------------------------------- | --------------------------- |
+| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>`    | `TUNNEL_DNS_RESOLVER_ADDRS` |
 
 Specifies custom DNS resolver addresses for `cloudflared` to use instead of the host machine's default resolvers. Each address must be in `ip:port` format — providing an IP address without a port will cause `cloudflared` to fail to start. You can specify multiple resolvers by repeating the flag. For example,
 
diff --git a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
index a0e19ac3f17e0f6..0a7bafc56310b6d 100644
--- a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
@@ -2,9 +2,9 @@
 {}
 ---
 
-| Status       | Meaning                                                                                                                                                                                                                                                                                                                                | Recommended Action                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Healthy**  | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                                                                                                                                                                                                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **Inactive** | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                                                                                                                                                                                                   | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel). |
-| **Down**     | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                                                                                                                                                                                                       | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                                                                                           |
-| **Degraded** | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic. | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                                            |
+| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
+| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel).                           |
+| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
+| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
index a868e4cec7f75c4..a8aee795acbec88 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
@@ -16,4 +16,4 @@ warp-cli target list
 ├──────────────────────────────────────┼──────────┼───────┼───────────────────────┼──────────────────────┼────────────┤
 │ 01943cff-6130-7989-8bff-cbc02b59a2b1 │ SSH      │ 80    │ hostname: az-target   │ 172.16.0.0 (b1net)   │ alice, bob │
 ╰──────────────────────────────────────┴──────────┴───────┴───────────────────────┴──────────────────────┴────────────╯
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
index 9fd296c4c4257a5..612d5ce51183c58 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
@@ -3,42 +3,42 @@ params:
   - one
 ---
 
-import { Markdown, Details, Tabs, TabItem } from "~/components";
+import { Markdown, Details, Tabs, TabItem} from "~/components";
 import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 
 By default, WARP excludes traffic bound for [RFC 1918 space](https://datatracker.ietf.org/doc/html/rfc1918), which are IP addresses typically used in private networks and not reachable from the Internet. In order for the Cloudflare One Client to send traffic to your <Markdown text={props.one}/>, you must configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that the IP/CIDR of your <Markdown text={props.one}/> routes through the Cloudflare One Client.
 
 1. First, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include** mode.
 2. Edit your Split Tunnel routes depending on the mode:
-   <Tabs> <TabItem label="Exclude IPs and domains">
-   
-   		If you are using **Exclude** mode:
-   
-   		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
-   
-   		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
-   
-   		You can use the following calculator to determine which IP addresses to re-add:
-   
-   			<SubtractIPCalculator
-   				client:load
-   				defaults={{
-   					base: "172.16.0.0/12",
-   					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
-   				}}
-   			/>
-   		<Details header="Calculator instructions" open = {true}>
-   		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
-   		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
-   		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
-   		</Details>
-   
-   		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
-   
-   
-      </TabItem> <TabItem label="Include IPs and domains">
-   		If you are using **Include** mode:
-   		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
-   		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
-   
-      </TabItem> </Tabs>
+  	<Tabs> <TabItem label="Exclude IPs and domains">
+
+		If you are using **Exclude** mode:
+
+		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
+
+		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
+
+		You can use the following calculator to determine which IP addresses to re-add:
+
+			<SubtractIPCalculator
+				client:load
+				defaults={{
+					base: "172.16.0.0/12",
+					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
+				}}
+			/>
+		<Details header="Calculator instructions" open = {true}>
+		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
+		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
+		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
+		</Details>
+
+		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
+
+
+   </TabItem> <TabItem label="Include IPs and domains">
+		If you are using **Include** mode:
+		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
+		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
+
+   </TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
index aed1dc57c84005a..88879da57d19361 100644
--- a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-It may take up to 10 minutes for newly updated settings to propagate to devices.
+It may take up to 10 minutes for newly updated settings to propagate to devices.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
index cc4a288a0d916a4..885e29755b6d368 100644
--- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105`
diff --git a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
index dfc8ccca98273c3..0f9cabfed41c022 100644
--- a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
+++ b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components";
+import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components"
 
 <Details header="Certificate requirements">
-	<Render file="byo-ca-mtls-cert-requirements" product="ssl" />
+   <Render file="byo-ca-mtls-cert-requirements" product="ssl" />
 </Details>
 
 To check for an mTLS certificate:
@@ -80,4 +81,4 @@ To check for an mTLS certificate:
 
 5. On your device, add the client certificate to the [system keychain](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#test-in-the-browser).
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
index 4c9ebbf7bef15c0..565425c2df7ac87 100644
--- a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
+++ b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 1. [Download](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and install the Cloudflare One Agent app.
 2. Launch the Cloudflare One Agent app.
diff --git a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
index 18e8ab3a2beb429..0c7940a4582c545 100644
--- a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
+++ b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
@@ -8,4 +8,4 @@ import { GlossaryTooltip } from "~/components";
 
 If your DNS server can be configured to connect to a Cloudflare <GlossaryTooltip term="on-ramp">on-ramp</GlossaryTooltip>, Cloudflare recommends using Gateway Resolver policies rather than Local Domain Fallback. Gateway Resolver policies provide more visibility by allowing you to log and review DNS traffic.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
index cb7f6b23c978461..65cc25e27b64395 100644
--- a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
+++ b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
@@ -12,4 +12,4 @@ The output will look something like:
 
 ```txt
 SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8662
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
index b54554c4a3ae864..77582cb8d22f063 100644
--- a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
+++ b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
@@ -6,4 +6,4 @@ To manually refresh your Cloudflare Access session and update your group informa
 
 `https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/refresh-identity`
 
-Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
+Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
index 81e72731b5d5abf..9df1996bb09d5b3 100644
--- a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
+++ b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
@@ -1,16 +1,13 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Refer to our [managed deployment instructions](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/) and create a `.plist`, `mdm.xml`, or `.msi` policy file based on your organization's software management tool.
 
-<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we
-recommend that your policy file only contain the organization name and
-potentially the onboarding flag, [relying on the
-dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/)
-to configure the remaining device settings.
+<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we recommend that your policy file only contain the organization name and potentially the onboarding flag, [relying on the dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/) to configure the remaining device settings.
 
 ```xml
 <dict>
diff --git a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
index 324b01831d1d350..40d23df27682b3c 100644
--- a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
+++ b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::note
 
 The OS version must be specified as a valid [Semver](https://semver.org/). For example, if your device is running OS version `1.2`, you must enter `1.2.0`.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
index 591e817aebaf97a..e7611c019caec78 100644
--- a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
+++ b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
@@ -22,4 +22,4 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
 
 <Render file="warp/managed-networks-sha-256" product="cloudflare-one"/>
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
index bee309cd06764e9..84e14c59cd4278e 100644
--- a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
+++ b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
@@ -115,9 +115,9 @@ Avoid vague descriptions and include scenario, timestamps, and steps taken to tr
   <>
     <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p>
 
-<p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
+    <p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
 
-<p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
+    <p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
 
   </>
 ) : props.tunnelMode ? (
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
index 3a4377564d2f4ff..d2177c9f8dc51ca 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
-|                            |                                                                                                               |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| **OS version**             | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
-| **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                                                             |
-| **HD space**               | 75 MB                                                                                                         |
-| **Memory**                 | 35 MB                                                                                                         |
-| **Network interface type** | Wi-Fi or LAN                                                                                                  |
-| **MTU**                    | 1381 bytes recommended [^2]                                                                                   |
+|                       |                                                                               |
+| --------------------- | ----------------------------------------------------------------------------- |
+| **OS version**        | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
+| **Processor**         | AMD64 / x86-64 or ARM64 / AArch64                                   |
+| **HD space**          | 75 MB                                                                         |
+| **Memory**            | 35 MB                                                                         |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^2] |
 
 [^1]: On RHEL 9 and later, enable the [Extra Packages for Enterprise Linux (EPEL)](https://docs.fedoraproject.org/en-US/epel/) repository (`sudo dnf install epel-release`) before installing `cloudflare-warp`. EPEL provides dependencies required by the client UI.
 
-[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
index 8742afdde17d699..48053016ac259ca 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-|                            |                                                                    |
-| -------------------------- | ------------------------------------------------------------------ |
-| **OS version**             | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+ |
-| **Processor**              | Intel or M series                                                  |
-| **HD space**               | 75 MB                                                              |
-| **Memory**                 | 35 MB                                                              |
-| **Network interface type** | Wi-Fi or LAN                                                       |
-| **MTU**                    | 1381 bytes recommended [^1]                                        |
+|                       |                                                   |
+| --------------------- | ------------------------------------------------- |
+| **OS version**        | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+                                 |
+| **Processor**         | Intel or M series   |
+| **HD space**          | 75 MB                                             |
+| **Memory**            | 35 MB                                             |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^1] |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
index 8c0f46bf3c6c5ae..7f1dfe65c468ba2 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
-|                            |                                                                      |
-| -------------------------- | -------------------------------------------------------------------- |
-| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11 |
+|                            |                                                   |
+| -------------------------- | ------------------------------------------------- |
+| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11                           |
 | **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                    |
-| **.NET Framework version** | 4.7.2 or later                                                       |
-| **HD space**               | 184 MB                                                               |
-| **Memory**                 | 3 MB                                                                 |
-| **Network interface type** | Wi-Fi or LAN                                                         |
-| **MTU**                    | 1381 bytes recommended [^1]                                          |
+| **.NET Framework version** | 4.7.2 or later                                    |
+| **HD space**               | 184 MB                                            |
+| **Memory**                 | 3 MB                                              |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^1] |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
index f13c7f8da379164..168c80b4c6089fd 100644
--- a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
+++ b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
@@ -1,17 +1,19 @@
 ---
 {}
+
 ---
 
 Perform these steps in the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Team & Resources** > **Devices** > **Device profiles** > **General profiles**.
 
 1. Set your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) to **Exclude IPs and domains**.
 2. [Add the following entries](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to your Split Tunnel Exclude list:
-   - Private IP address range exposed by your third-party VPN client. For example,
+
+   * Private IP address range exposed by your third-party VPN client. For example,
      | Selector | Value |
      | -------- | ----- |
-     | IP Address | `172.16.0.0/12` |
+     | IP Address   | `172.16.0.0/12` |
      |
-   - Server that your third-party VPN client connects to. For example,
+   * Server that your third-party VPN client connects to. For example,
      | Selector | Value |
      | -------- | ----- |
-     | Domain | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
+     | Domain   | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
diff --git a/src/content/partials/cloudflare-one/warp/warp-modes.mdx b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
index fe4dbbfb81edeea..ed493a08759ce6b 100644
--- a/src/content/partials/cloudflare-one/warp/warp-modes.mdx
+++ b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
@@ -4,8 +4,8 @@
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                          | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                   | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/partials/containers/instance-types.mdx b/src/content/partials/containers/instance-types.mdx
index 0c7e58181689b5f..705a0f3c5970555 100644
--- a/src/content/partials/containers/instance-types.mdx
+++ b/src/content/partials/containers/instance-types.mdx
@@ -1,8 +1,8 @@
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------- | ----- |
+| ------------- | ---- | ------  | ----  |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
 | standard-2    | 1    | 6 GiB   | 12 GB |
 | standard-3    | 2    | 8 GiB   | 16 GB |
-| standard-4    | 4    | 12 GiB  | 20 GB |
+| standard-4    | 4    | 12 GiB  | 20 GB |
\ No newline at end of file
diff --git a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
index b0f0987a817dc7c..ea530442f741999 100644
--- a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
+++ b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
@@ -1,6 +1,6 @@
 ---
 params:
-  - product
+- product
 ---
 
 {props.product} a subset of SQLite extensions for added functionality, including:
@@ -9,4 +9,4 @@ params:
 - [JSON extension](https://www.sqlite.org/json1.html) for JSON functions and operators.
 - [Math functions](https://sqlite.org/lang_mathfunc.html).
 
-Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
+Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
\ No newline at end of file
diff --git a/src/content/partials/d1/generate-d1-api-token.mdx b/src/content/partials/d1/generate-d1-api-token.mdx
index 2c13c1ba8b60e3d..700bee2bfb563e9 100644
--- a/src/content/partials/d1/generate-d1-api-token.mdx
+++ b/src/content/partials/d1/generate-d1-api-token.mdx
@@ -21,4 +21,4 @@ import { Steps, DashButton } from "~/components";
 </Steps>
 
 - Refer to [Create API token](/fundamentals/api/get-started/create-token/) for more information on creating API tokens through the Cloudflare dashboard.
-- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
+- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
index 18b1bdc17d3c358..5c559f1e70ee53e 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
+Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
index 2cba0a9f642281c..9a44876d0af0d32 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
+[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
index 54dbbb22ddac8c5..1393b132f8df703 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
@@ -6,4 +6,4 @@
 Advanced TCP and DNS Protection systems are automatically enabled in `Monitor` mode with the default thresholds for new Magic Transit customers and their [authorized prefixes](/magic-transit/how-to/advertise-prefixes/).
 
 Magic Transit customers can also enable the Advanced DDoS systems when the prefixes are ready, change the sensitivity level, or adjust the thresholds by contacting their account team.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
index bd07b8b43cb7890..3b2d7e3139d2b5a 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
+Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
index e6d886f65e51b05..2c4124f1e232eee 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
+[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
index 4a2843a4d9281c2..a66db33424c00e8 100644
--- a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
+++ b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DDoS reports and DDoS alerts are independent: DDoS reports will include information about any attacks for which you received DDoS alerts.
diff --git a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
index e752ea9ae03f6d5..b98f5547923a93c 100644
--- a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
+++ b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 :::caution[Important]
 
+
 Prefixes in the allowlist will be vulnerable to <GlossaryTooltip term="IP spoofing">IP spoofing</GlossaryTooltip> attacks. If an attacker can guess the source IP addresses you have allowlisted, their packets will be allowlisted.
 
+
 :::
diff --git a/src/content/partials/ddos-protection/atp-filter-definition.mdx b/src/content/partials/ddos-protection/atp-filter-definition.mdx
index 523d17768055849..12d6e288ceadf95 100644
--- a/src/content/partials/ddos-protection/atp-filter-definition.mdx
+++ b/src/content/partials/ddos-protection/atp-filter-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
+A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
index a961f5d75580c97..856694a96d0c99c 100644
--- a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
+++ b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/ddos-protection/create-notification.mdx b/src/content/partials/ddos-protection/create-notification.mdx
index 8a4ea2addd089cb..d198471ab167dd0 100644
--- a/src/content/partials/ddos-protection/create-notification.mdx
+++ b/src/content/partials/ddos-protection/create-notification.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
index b78cd219dfc2f48..6b49ed03060ba7f 100644
--- a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
+++ b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
-| OSI Layer   | Ruleset / Feature                                                                                        | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| ----------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| L3/4        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                       | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
-| L3/4        | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1] | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| L7 (DNS)    | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1] | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| L7 (HTTP/S) | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                   | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| OSI Layer       | Ruleset / Feature                                                                                                      | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| --------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| L3/4            | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                                     | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
+| L3/4            | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1]               | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| L7 (DNS)        | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1]               | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| L7 (HTTP/S)     | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                                 | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                  |
 
 [^1]: Available to Magic Transit customers.
diff --git a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
index ebb6dc3d1dbdf51..6bd97998baead60 100644
--- a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
+++ b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
+Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
index a85897a7a575038..ffcd4438247f2b1 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details, Render, Steps, DashButton } from "~/components";
+import { Details, Render, Steps, DashButton } from "~/components"
 
 <Steps>
   1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
@@ -35,4 +35,4 @@ import { Details, Render, Steps, DashButton } from "~/components";
       - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
       :::
   8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
index 03910e37301db8a..b32f56a8b16d56e 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Create multiple rules in the `ddos_l7` phase entry point ruleset to define different overrides for different sets of incoming requests. Set each rule expression according to the traffic whose HTTP DDoS protection you wish to customize.
 
-Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
+Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
index 9b1cf47c23bbb2e..21e80e11b8adc25 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Highly targeted rules for mitigating DDoS attacks with a high confidence rate. These rules are read-only — you cannot override their sensitivity level or action.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
index fcc5ea826e263dc..3168c30b815a38a 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The managed ruleset includes some read-only rules that you cannot override.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
index 0c3e48d1a2ab57c..6f4476224899bd4 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 API property name: `"sensitivity_level"`.
@@ -10,15 +11,15 @@ The available sensitivity levels are:
 
 | UI value          | API value   |
 | ----------------- | ----------- |
-| _High_            | `"default"` |
-| _Medium_          | `"medium"`  |
-| _Low_             | `"low"`     |
-| _Essentially Off_ | `"eoff"`    |
+| *High*            | `"default"` |
+| *Medium*          | `"medium"`  |
+| *Low*             | `"low"`     |
+| *Essentially Off* | `"eoff"`    |
 
-The default sensitivity level is _High_.
+The default sensitivity level is *High*.
 
-In most cases, when you select the _Essentially Off_ sensitivity level the rule will not trigger for any of the selected actions, including _Log_. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
+In most cases, when you select the *Essentially Off* sensitivity level the rule will not trigger for any of the selected actions, including *Log*. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
 
-_Essentially Off_ means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+*Essentially Off* means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
 
-**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
index 2b38abe2e55abcf..72d2abd12cf1632 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Rules used for testing the detection, mitigation, and alerting capabilities of Cloudflare's DDoS protection products.
diff --git a/src/content/partials/ddos-protection/override-example.mdx b/src/content/partials/ddos-protection/override-example.mdx
index c25df1b5a153d19..4e8d68a92360f5f 100644
--- a/src/content/partials/ddos-protection/override-example.mdx
+++ b/src/content/partials/ddos-protection/override-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Example
@@ -13,33 +14,33 @@ A DDoS managed ruleset contains the following managed rules:
 The following ruleset overrides have been configured:
 
 - **Ruleset override A**
-  - **Managed rule 1** is set to `block`
+   - **Managed rule 1** is set to `block`
 - **Ruleset override B**
-  - The action of the entire ruleset (or _all managed rules_) is set to `Managed Challenge`
-  - **Managed rule 1** is set to `log`
-  - **Managed rule 2** is set to `log`
+   - The action of the entire ruleset (or *all managed rules*) is set to `Managed Challenge`
+   - **Managed rule 1** is set to `log`
+   - **Managed rule 2** is set to `log`
 - **Ruleset override C**
-  - **Managed rule 3** is set to `log`
+   - **Managed rule 3** is set to `log`
 
-### Use case
+### Use case 
 
 A DDoS attack was detected on **managed rules 1**, **2**, and **3**, and has generated a mitigation rule.
 
-- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules.
+- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules. 
 
 - **Managed rule 2** does not match **ruleset override A**, so Cloudflare proceeds to **ruleset override B**. <br /> **Ruleset override B** matches both all managed rules and **managed rule 2**, but specificity takes precedence. It does not `challenge` and instead proceeds with `log` since it matches the most specific managed rule.
 
-- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets _all managed rules_ to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
+- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets *all managed rules* to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
 
 An additional dimension to take into account is Cloudflare’s DDoS systems will apply a given rule override only if its conditions are met — which includes the Sensitivity level. So, while it needs to match and modify the correct managed rule (or everything in the case of all managed rules above), it also has to meet the specified Sensitivity level of the rule.
 
 - **Rule override A**
-  - _All managed rules_ are set to `challenge` at low sensitivity
+   - *All managed rules* are set to `challenge` at low sensitivity
 
 - **Rule override B**
-  - **Managed rule 1** is set to `log` at default sensitivity
+   - **Managed rule 1** is set to `log` at default sensitivity
 
 You receive a small attack below the threshold for low sensitivity, but above the threshold for high sensitivity on **managed rule 1**.
 
-- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate.
-- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
+- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate. 
+- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/override-logic.mdx b/src/content/partials/ddos-protection/override-logic.mdx
index a4cde6e1c07ac0b..b9ff54257029827 100644
--- a/src/content/partials/ddos-protection/override-logic.mdx
+++ b/src/content/partials/ddos-protection/override-logic.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 When Cloudflare's DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection managed ruleset. Each mitigation rule is generated from a single managed rule.
 
-All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches.
+All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches. 
 
-You can create only one ruleset override that can contain one or multiple rule overrides.
+You can create only one ruleset override that can contain one or multiple rule overrides. 
 
 :::note
 Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) add-on can create up to 10 ruleset overrides.
@@ -14,4 +15,4 @@ Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanc
 
 A rule override instructs the DDoS system on the action it should take against the attack according to its matching managed rule.
 
-However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override.
+However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override. 
\ No newline at end of file
diff --git a/src/content/partials/dmarc-management/domain-spoofing.mdx b/src/content/partials/dmarc-management/domain-spoofing.mdx
index 789d26bbd41acbb..f67efe27497fedf 100644
--- a/src/content/partials/dmarc-management/domain-spoofing.mdx
+++ b/src/content/partials/dmarc-management/domain-spoofing.mdx
@@ -10,6 +10,8 @@ Without email authentication records, anyone can send email that appears to come
 
 :::note
 
+
 For additional background on email security records, refer to the [introductory blog post](https://blog.cloudflare.com/tackling-email-spoofing/).
 
+
 :::
diff --git a/src/content/partials/dns/a-aaaa-definition.mdx b/src/content/partials/dns/a-aaaa-definition.mdx
index 7871b0c522c087c..382543d232d0715 100644
--- a/src/content/partials/dns/a-aaaa-definition.mdx
+++ b/src/content/partials/dns/a-aaaa-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [A and AAAA records](https://www.cloudflare.com/learning/dns/dns-records/dns-a-record/) map a domain name to one or multiple IPv4 or IPv6 address(es).
diff --git a/src/content/partials/dns/acns-tcns-byoip.mdx b/src/content/partials/dns/acns-tcns-byoip.mdx
index d54a916972d3a46..0184972c95cb464 100644
--- a/src/content/partials/dns/acns-tcns-byoip.mdx
+++ b/src/content/partials/dns/acns-tcns-byoip.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::note
 
diff --git a/src/content/partials/dns/acns-tcns-conditions.mdx b/src/content/partials/dns/acns-tcns-conditions.mdx
index 8ffad8ef38a32d5..910dee1af8bb028 100644
--- a/src/content/partials/dns/acns-tcns-conditions.mdx
+++ b/src/content/partials/dns/acns-tcns-conditions.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2;;param3
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-- {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
-- [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
+* {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
+* [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
diff --git a/src/content/partials/dns/acns-tcns-intro.mdx b/src/content/partials/dns/acns-tcns-intro.mdx
index 4089262cc29499c..d75bd29c06d9035 100644
--- a/src/content/partials/dns/acns-tcns-intro.mdx
+++ b/src/content/partials/dns/acns-tcns-intro.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2;;param3;;param4;;param5
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 {props.one} custom nameservers ({props.two}CNS) allow you to define {props.three}-level custom nameservers and use them for different {props.four} within a Cloudflare {props.five}.
 
diff --git a/src/content/partials/dns/aname-alias-callout.mdx b/src/content/partials/dns/aname-alias-callout.mdx
index e958df71d713e10..6751169d5c78778 100644
--- a/src/content/partials/dns/aname-alias-callout.mdx
+++ b/src/content/partials/dns/aname-alias-callout.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's [CNAME flattening](/dns/cname-flattening/)[^1] allows you to create CNAME records at your [zone apex](/dns/concepts/#zone-apex), removing the need for those other record types.
 
-[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
+[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
\ No newline at end of file
diff --git a/src/content/partials/dns/api-field-definitions.mdx b/src/content/partials/dns/api-field-definitions.mdx
index 2629350da26de28..af7ea90d28101b2 100644
--- a/src/content/partials/dns/api-field-definitions.mdx
+++ b/src/content/partials/dns/api-field-definitions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For field definitions, refer to the [API documentation](/api/resources/dns/subresources/records/methods/create/) (visible once you select the record type under the request body specification).
diff --git a/src/content/partials/dns/cname-definition.mdx b/src/content/partials/dns/cname-definition.mdx
index 324c92c3d9865a3..ac977bc79ea7fe9 100644
--- a/src/content/partials/dns/cname-definition.mdx
+++ b/src/content/partials/dns/cname-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [CNAME records](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/) map a domain name to another (canonical) domain name. They can be used to resolve other record types present on the target domain name.
diff --git a/src/content/partials/dns/cname-flattening-callout.mdx b/src/content/partials/dns/cname-flattening-callout.mdx
index 000688fb842401b..030fec534c89c49 100644
--- a/src/content/partials/dns/cname-flattening-callout.mdx
+++ b/src/content/partials/dns/cname-flattening-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If a CNAME target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the CNAME record itself will not be returned directly.
diff --git a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
index 6c9b25d037c6bfd..2d6ccf3c0e1d1b4 100644
--- a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
+++ b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::caution[Subdomain setup]
 If you also use subdomain setup[^1], consider the [available combinations](/dns/zone-setups/subdomain-setup/setup/#available-setups) and whether your zone conversion could have any implications.
 :::
 
-[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
+[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
\ No newline at end of file
diff --git a/src/content/partials/dns/dns-errors-ts-action.mdx b/src/content/partials/dns/dns-errors-ts-action.mdx
index 4d2f0fe2811d7d4..9dfa15e76d1dfa6 100644
--- a/src/content/partials/dns/dns-errors-ts-action.mdx
+++ b/src/content/partials/dns/dns-errors-ts-action.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: errorName
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 If you experience <code>{props.one}</code> errors with a newly activated domain, review your DNS settings in the Cloudflare dashboard.
 
diff --git a/src/content/partials/dns/dns-errors-ts-intro.mdx b/src/content/partials/dns/dns-errors-ts-intro.mdx
index d1d1d3950aaa5fa..cb332968acfcf3d 100644
--- a/src/content/partials/dns/dns-errors-ts-intro.mdx
+++ b/src/content/partials/dns/dns-errors-ts-intro.mdx
@@ -1,13 +1,16 @@
 ---
 inputParameters: errorName
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 If you or your visitors experience <code>{props.one}</code> errors after you [activate your domain on Cloudflare](/dns/zone-setups/full-setup/setup/), review your DNS records in Cloudflare.
 
 :::note
 
+
 If your domain is added to Cloudflare by a hosting partner, manage your DNS records via the hosting partner.
 
+
 :::
diff --git a/src/content/partials/dns/dns-nxdomain-warning.mdx b/src/content/partials/dns/dns-nxdomain-warning.mdx
index a0aa3e538b03546..d9b592cdc25513c 100644
--- a/src/content/partials/dns/dns-nxdomain-warning.mdx
+++ b/src/content/partials/dns/dns-nxdomain-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
-If you activate your domain on Cloudflare _without_ setting up the correct DNS records for your domain, your visitors may experience [DNS_PROBE_FINISHED_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
+
+If you activate your domain on Cloudflare *without* setting up the correct DNS records for your domain, your visitors may experience [DNS\_PROBE\_FINISHED\_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
+
 
 :::
diff --git a/src/content/partials/dns/dns-record-steps.mdx b/src/content/partials/dns/dns-record-steps.mdx
index 8ab4783d7d17bee..058a0bf5c7cacfd 100644
--- a/src/content/partials/dns/dns-record-steps.mdx
+++ b/src/content/partials/dns/dns-record-steps.mdx
@@ -4,13 +4,7 @@ params:
   - example
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
@@ -33,4 +27,4 @@ Use the [Create DNS Record API endpoint](/api/resources/dns/subresources/records
     - To point to an IPv6 address, select **AAAA Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the IPv6 address for the field `content`.
     - To point to a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (such as `your-site.host.example.com`), select **CNAME Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the fully qualified domain name for the field `content`.
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/dns/dns-scan-intro.mdx b/src/content/partials/dns/dns-scan-intro.mdx
index e54726a33bab66b..8901df100607fa7 100644
--- a/src/content/partials/dns/dns-scan-intro.mdx
+++ b/src/content/partials/dns/dns-scan-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/dns-scan-note.mdx b/src/content/partials/dns/dns-scan-note.mdx
index eff151ba8112ac8..636218d0b27de88 100644
--- a/src/content/partials/dns/dns-scan-note.mdx
+++ b/src/content/partials/dns/dns-scan-note.mdx
@@ -1,5 +1,5 @@
 ---
 {}
----
 
+---
 If you add a zone via the [API](/api/resources/zones/methods/create/), you can manually invoke the quick scan with the [Trigger DNS Records Scan endpoint](/api/resources/dns/subresources/records/methods/scan_trigger/).
diff --git a/src/content/partials/dns/dnssec-auto-add.mdx b/src/content/partials/dns/dnssec-auto-add.mdx
index 692574c3903a3ce..c59ce7dadf53c5d 100644
--- a/src/content/partials/dns/dnssec-auto-add.mdx
+++ b/src/content/partials/dns/dnssec-auto-add.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Note:]
 
+
 Cloudflare automatically adds **DS** records for domains using Cloudflare Registrar or those using `.ch` and `.cz` top-level domains.
 
+
 :::
diff --git a/src/content/partials/dns/dnssec-cloudflare-steps.mdx b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
index 97e0be8c4a00e2d..d066c3e5a606e96 100644
--- a/src/content/partials/dns/dnssec-cloudflare-steps.mdx
+++ b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/dns/dnssec-definition.mdx b/src/content/partials/dns/dnssec-definition.mdx
index e286d2e3f82b1ed..8e4f721549a3dcd 100644
--- a/src/content/partials/dns/dnssec-definition.mdx
+++ b/src/content/partials/dns/dnssec-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS Security Extensions (DNSSEC) adds an extra layer of authentication to DNS, ensuring requests are not routed to a spoofed domain.
diff --git a/src/content/partials/dns/dnssec-enabled-migration.mdx b/src/content/partials/dns/dnssec-enabled-migration.mdx
index 34be4c281d852e9..2baa9a405746770 100644
--- a/src/content/partials/dns/dnssec-enabled-migration.mdx
+++ b/src/content/partials/dns/dnssec-enabled-migration.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If your previous provider allows you to add DNSKEY records on the zone apex and use these records in responses to DNS queries, refer to this [migration tutorial](/dns/dnssec/dnssec-active-migration/) to learn how to migrate a zone with DNSSEC enabled.
 
+
 :::
diff --git a/src/content/partials/dns/dnssec-registrar-steps.mdx b/src/content/partials/dns/dnssec-registrar-steps.mdx
index bb870033de61d09..60a42cb75248c8b 100644
--- a/src/content/partials/dns/dnssec-registrar-steps.mdx
+++ b/src/content/partials/dns/dnssec-registrar-steps.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called _ECDSA Curve P-256 with SHA-256_.
+Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called *ECDSA Curve P-256 with SHA-256*.
 
 <Render file="dnssec-providers" product="dns" />
diff --git a/src/content/partials/dns/export-dns-records.mdx b/src/content/partials/dns/export-dns-records.mdx
index 1c63cb825b5f494..1f8697f19614b35 100644
--- a/src/content/partials/dns/export-dns-records.mdx
+++ b/src/content/partials/dns/export-dns-records.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
diff --git a/src/content/partials/dns/internal-dns-beta-note.mdx b/src/content/partials/dns/internal-dns-beta-note.mdx
index 5f59566c426a379..5d69d57445eafa7 100644
--- a/src/content/partials/dns/internal-dns-beta-note.mdx
+++ b/src/content/partials/dns/internal-dns-beta-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/internal-dns-view-conditions.mdx b/src/content/partials/dns/internal-dns-view-conditions.mdx
index 864542fca83a966..b28ccc739a2b0fc 100644
--- a/src/content/partials/dns/internal-dns-view-conditions.mdx
+++ b/src/content/partials/dns/internal-dns-view-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - DNS views can be empty, with no [internal zones](/dns/internal-dns/internal-zones/) linked to them.
@@ -7,5 +8,4 @@
 - Each internal DNS zone name must be unique within a given DNS view.
 - Each DNS view name must be unique within a given Cloudflare account.
 
-<sup>1</sup> DNS zones that contain public DNS records and are accessible by
-public resolvers.
+<sup>1</sup> DNS zones that contain public DNS records and are accessible by public resolvers.
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-reference-zone-api.mdx b/src/content/partials/dns/internal-reference-zone-api.mdx
index 830c568f97e562c..05e1180d9227406 100644
--- a/src/content/partials/dns/internal-reference-zone-api.mdx
+++ b/src/content/partials/dns/internal-reference-zone-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -9,12 +10,14 @@ In the following example, internal zone A (ID `8a904aeb565c42cfa207d98f6edea2f3`
 <APIRequest
 	path="/zones/{zone_id}/dns_settings"
 	method="PATCH"
-	json={{
-		internal_dns: {
-			reference_zone_id: "8e64c6fb4b514f3faf64de81efc11e51",
-		},
-	}}
+	json={
+		{
+    "internal_dns": {
+        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51"
+    }
+		}
+	}
 	parameters={{
 		zone_id: "8a904aeb565c42cfa207d98f6edea2f3",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-reference-zone-intro.mdx b/src/content/partials/dns/internal-reference-zone-intro.mdx
index 94e58c8e201d0d8..71d7c7621b8fda4 100644
--- a/src/content/partials/dns/internal-reference-zone-intro.mdx
+++ b/src/content/partials/dns/internal-reference-zone-intro.mdx
@@ -5,9 +5,10 @@ params:
 
 During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain.
 
+
 { props.conditional === "get-started-link" && (
-<p>
-For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
-</p>
-)
-}
+	<p>
+	For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
+	</p>
+	)
+}
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-zones-conditions.mdx b/src/content/partials/dns/internal-zones-conditions.mdx
index 33e00fe187436c9..64201918a6fb264 100644
--- a/src/content/partials/dns/internal-zones-conditions.mdx
+++ b/src/content/partials/dns/internal-zones-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
@@ -8,5 +9,4 @@
 - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
 - Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`).
 
-<sup>1</sup> Logical groupings of internal DNS zones that are referenced by
-Gateway resolver policies to define how a specific query should be resolved.
+<sup>1</sup> Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved.
\ No newline at end of file
diff --git a/src/content/partials/dns/linked-peers-limit.mdx b/src/content/partials/dns/linked-peers-limit.mdx
index c18d3fb2b701548..07cf4abcd9e4cc3 100644
--- a/src/content/partials/dns/linked-peers-limit.mdx
+++ b/src/content/partials/dns/linked-peers-limit.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The maximum number of linked peers per zone is 30.
diff --git a/src/content/partials/dns/minimize-downtime-tip.mdx b/src/content/partials/dns/minimize-downtime-tip.mdx
index ca7fae767a4d48c..b13c26fb8eaa702 100644
--- a/src/content/partials/dns/minimize-downtime-tip.mdx
+++ b/src/content/partials/dns/minimize-downtime-tip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
+If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
\ No newline at end of file
diff --git a/src/content/partials/dns/mix-proxied-and-unproxied.mdx b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
index c028f99ad6ccb3b..8b12a1d041c6e54 100644
--- a/src/content/partials/dns/mix-proxied-and-unproxied.mdx
+++ b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If you have multiple `A/AAAA` records on the same name and at least one of them is proxied, Cloudflare will treat all `A/AAAA` records on this name as being proxied.
 
+
 :::
diff --git a/src/content/partials/dns/nameserver-preamble.mdx b/src/content/partials/dns/nameserver-preamble.mdx
index 5b17906420c1020..96bf1107d118e88 100644
--- a/src/content/partials/dns/nameserver-preamble.mdx
+++ b/src/content/partials/dns/nameserver-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/nameservers-registrar-callout.mdx b/src/content/partials/dns/nameservers-registrar-callout.mdx
index afcec9106f1f765..efdd668bfb70fc7 100644
--- a/src/content/partials/dns/nameservers-registrar-callout.mdx
+++ b/src/content/partials/dns/nameservers-registrar-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Cloudflare Registrar]
diff --git a/src/content/partials/dns/ns-advanced-vs-custom.mdx b/src/content/partials/dns/ns-advanced-vs-custom.mdx
index 42e1cfe62cc3fb3..085c0ab10e67144 100644
--- a/src/content/partials/dns/ns-advanced-vs-custom.mdx
+++ b/src/content/partials/dns/ns-advanced-vs-custom.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The advantages that come with Foundation DNS [advanced nameservers](/dns/foundation-dns/advanced-nameservers/) are currently not available for [custom nameservers](/dns/nameservers/custom-nameservers/). Make sure you only use one at a time.
diff --git a/src/content/partials/dns/ns-set-omission-callout.mdx b/src/content/partials/dns/ns-set-omission-callout.mdx
index aceb7ef494144c3..4255ed43dcb62dd 100644
--- a/src/content/partials/dns/ns-set-omission-callout.mdx
+++ b/src/content/partials/dns/ns-set-omission-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/ns-static-ips.mdx b/src/content/partials/dns/ns-static-ips.mdx
index f7cb24564edd03d..33542f81098b4ae 100644
--- a/src/content/partials/dns/ns-static-ips.mdx
+++ b/src/content/partials/dns/ns-static-ips.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The IPs assigned to each nameserver are static, meaning they will not change without notification.
+The IPs assigned to each nameserver are static, meaning they will not change without notification.
\ No newline at end of file
diff --git a/src/content/partials/dns/ns-update-providers.mdx b/src/content/partials/dns/ns-update-providers.mdx
index 207b9774b87ee74..4619e0f648cd65c 100644
--- a/src/content/partials/dns/ns-update-providers.mdx
+++ b/src/content/partials/dns/ns-update-providers.mdx
@@ -1,41 +1,42 @@
 ---
 {}
+
 ---
 
 This is not an exhaustive list of provider-specific instructions, but the following links may be helpful:
 
-- [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
-- [101Domain](https://help.101domain.com/kb/managing-name-server-records)
-- [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
-- [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
-- [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
-- [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
-- [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
-- [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
-- [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
-- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
-- [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
-- [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
-- [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
-- [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
-- [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
-- [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
-- [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
-- [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
-- [HostMonster](https://my.hostmonster.com/cgi/help/222)
-- [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
-- [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
-- [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
-- [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
-- [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
-- [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
-- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
-- [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
-- [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
-- [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
-- [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
-- [Register](https://www.register.com/knowledge)
-- [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
-- [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
-- [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
-- [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
+* [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
+* [101Domain](https://help.101domain.com/kb/managing-name-server-records)
+* [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
+* [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
+* [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
+* [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
+* [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
+* [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
+* [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
+* [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
+* [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
+* [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
+* [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
+* [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
+* [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
+* [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
+* [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
+* [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
+* [HostMonster](https://my.hostmonster.com/cgi/help/222)
+* [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
+* [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
+* [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
+* [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
+* [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
+* [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
+* [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
+* [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
+* [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
+* [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
+* [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
+* [Register](https://www.register.com/knowledge)
+* [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
+* [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
+* [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
+* [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
diff --git a/src/content/partials/dns/onboard-warning.mdx b/src/content/partials/dns/onboard-warning.mdx
index 883289d67398e5e..cd609c994c7516f 100644
--- a/src/content/partials/dns/onboard-warning.mdx
+++ b/src/content/partials/dns/onboard-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you [add a domain](/fundamentals/manage-domains/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
diff --git a/src/content/partials/dns/partial-setup-definition.mdx b/src/content/partials/dns/partial-setup-definition.mdx
index d429d6c760396ab..d4a185c7c288b4c 100644
--- a/src/content/partials/dns/partial-setup-definition.mdx
+++ b/src/content/partials/dns/partial-setup-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 A CNAME setup (also known as partial setup) allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
 
diff --git a/src/content/partials/dns/random-prefix-attack-definition.mdx b/src/content/partials/dns/random-prefix-attack-definition.mdx
index 3a4378c97f94a4e..421e48350e97627 100644
--- a/src/content/partials/dns/random-prefix-attack-definition.mdx
+++ b/src/content/partials/dns/random-prefix-attack-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Random prefix attacks are when someone sends a lot of traffic to subdomains that are highly unlikely to exist (`12345.example.com`, `abcdefg.example.com`), but are still associated with your main domain (`example.com`).
diff --git a/src/content/partials/dns/records-name-field.mdx b/src/content/partials/dns/records-name-field.mdx
index ed19a6fb9b2d987..ed33e8cf7fea2e3 100644
--- a/src/content/partials/dns/records-name-field.mdx
+++ b/src/content/partials/dns/records-name-field.mdx
@@ -3,7 +3,7 @@
 ---
 
 - **Name**: A subdomain or the zone apex (`@`).
-  - The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
-  - DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
-  - There is no requirement to start with a letter or end with a letter or digit.
-  - Underscores are valid in DNS and commonly used for service records.
+	- The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
+	- DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
+	- There is no requirement to start with a letter or end with a letter or digit.
+	- Underscores are valid in DNS and commonly used for service records.
diff --git a/src/content/partials/dns/recover-deleted-domain.mdx b/src/content/partials/dns/recover-deleted-domain.mdx
index dd9da29b1c18d12..04ea32052b4199c 100644
--- a/src/content/partials/dns/recover-deleted-domain.mdx
+++ b/src/content/partials/dns/recover-deleted-domain.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/manage-domains/add-site/) just like you would for a new domain.
diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx
index 8a76949a59dd2f5..3addd6a512c230f 100644
--- a/src/content/partials/dns/secondary-conversion-unlink.mdx
+++ b/src/content/partials/dns/secondary-conversion-unlink.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -11,4 +12,4 @@ import { DashButton } from "~/components";
 2. Under **DNS Zone Transfers**, and select **Manage linked peers**.
 3. Unlink the peer and select **Save**.
 
-At this point, your zone will be read-only.
+At this point, your zone will be read-only.
\ No newline at end of file
diff --git a/src/content/partials/dns/secondary-dns-override.mdx b/src/content/partials/dns/secondary-dns-override.mdx
index e85867604e92094..3479cba6efadd24 100644
--- a/src/content/partials/dns/secondary-dns-override.mdx
+++ b/src/content/partials/dns/secondary-dns-override.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Normal incoming zone transfers only provide DNS resolution. If you also want your traffic to benefit from Cloudflare's performance and security features, you need to [set up Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/).
diff --git a/src/content/partials/dns/ssltls-subdomains.mdx b/src/content/partials/dns/ssltls-subdomains.mdx
index 65f7bae8f4f3cc0..7509364e5359f30 100644
--- a/src/content/partials/dns/ssltls-subdomains.mdx
+++ b/src/content/partials/dns/ssltls-subdomains.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your main domain is using Cloudflare's [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/), that certificate also covers all first-level subdomains (`blog.example.com`).
diff --git a/src/content/partials/dns/subdomain-customization.mdx b/src/content/partials/dns/subdomain-customization.mdx
index ca49fdca438e461..b3d2fc5d81bd5a3 100644
--- a/src/content/partials/dns/subdomain-customization.mdx
+++ b/src/content/partials/dns/subdomain-customization.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to customize Cloudflare settings for individual subdomains, your approach will vary depending on your plan.
diff --git a/src/content/partials/dns/third-party-caveat.mdx b/src/content/partials/dns/third-party-caveat.mdx
index aa50c4ed3da9acf..32f0740937afdaf 100644
--- a/src/content/partials/dns/third-party-caveat.mdx
+++ b/src/content/partials/dns/third-party-caveat.mdx
@@ -1,11 +1,14 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::note
 
+
 When you [add records to Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/), those records should be [DNS-only (unproxied)](/dns/proxy-status/#dns-only-records) until {props.one} verifies your domain. Then, you can switch your DNS records to **Proxied**.
 
+
 :::
diff --git a/src/content/partials/dns/tsig-create-api.mdx b/src/content/partials/dns/tsig-create-api.mdx
index 240a4ecc1800410..0ca5c0a9ba3903e 100644
--- a/src/content/partials/dns/tsig-create-api.mdx
+++ b/src/content/partials/dns/tsig-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create a TSIG using the API, send a [POST](/api/resources/dns/subresources/zone_transfers/subresources/tsigs/methods/create/) request.
diff --git a/src/content/partials/dns/tsig-create-dash.mdx b/src/content/partials/dns/tsig-create-dash.mdx
index df306405d917d0e..b93345590415a34 100644
--- a/src/content/partials/dns/tsig-create-dash.mdx
+++ b/src/content/partials/dns/tsig-create-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -13,7 +14,7 @@ To create a TSIG using the dashboard:
 2. Go to **DNS Settings**.
 3. Under **DNS Zone Transfers**, for **TSIG**, select **Create**.
 4. Enter the following information:
-   - **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
-   - **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
-   - **Algorithm**: Choose a TSIG signing algorithm.
+   * **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
+   * **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
+   * **Algorithm**: Choose a TSIG signing algorithm.
 5. Select **Create**.
diff --git a/src/content/partials/dns/tsig-definition.mdx b/src/content/partials/dns/tsig-definition.mdx
index be7c2d62be93667..74fe88b3a4ddd3a 100644
--- a/src/content/partials/dns/tsig-definition.mdx
+++ b/src/content/partials/dns/tsig-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 A Transaction Signature (TSIG) authenticates communication between a primary and secondary DNS server.
 
diff --git a/src/content/partials/dns/tsig-name-match.mdx b/src/content/partials/dns/tsig-name-match.mdx
index dffb08898eb97bf..ffaa6bc70ebfc62 100644
--- a/src/content/partials/dns/tsig-name-match.mdx
+++ b/src/content/partials/dns/tsig-name-match.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/why-disable-dnssec.mdx b/src/content/partials/dns/why-disable-dnssec.mdx
index 2b37d7c7fa26608..57db63f976fd9d8 100644
--- a/src/content/partials/dns/why-disable-dnssec.mdx
+++ b/src/content/partials/dns/why-disable-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When your domain has [DNSSEC enabled](https://www.cloudflare.com/learning/dns/dns-security/#what-is-dnssec), your DNS provider digitally signs all your DNS records. This action prevents anyone else from issuing false DNS records on your behalf and redirecting traffic intended for your domain.
diff --git a/src/content/partials/dns/zone-defaults-exceptions.mdx b/src/content/partials/dns/zone-defaults-exceptions.mdx
index 1e74b26d026a49a..5005703713f7f89 100644
--- a/src/content/partials/dns/zone-defaults-exceptions.mdx
+++ b/src/content/partials/dns/zone-defaults-exceptions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones, nor zones that existed previously and are being revived.
diff --git a/src/content/partials/dns/zone-file-size-limit.mdx b/src/content/partials/dns/zone-file-size-limit.mdx
index 71afea606b6bc17..4873764d6189ff0 100644
--- a/src/content/partials/dns/zone-file-size-limit.mdx
+++ b/src/content/partials/dns/zone-file-size-limit.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The zone file size limit is 256 KiB (262144 bytes).
diff --git a/src/content/partials/durable-objects/api-async-kv-legacy.mdx b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
index a2698461e2eebcd..1ef05ec94c61a03 100644
--- a/src/content/partials/durable-objects/api-async-kv-legacy.mdx
+++ b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Type, MetaInfo, AnchorHeading } from "~/components";
+import {Type, MetaInfo, AnchorHeading} from "~/components";
 
 <AnchorHeading title="get" slug="do-kv-async-get" depth={3} />
 
@@ -107,4 +107,4 @@ The `put()` method returns a `Promise`, but most applications can discard this p
   - Same as the option to [`get()`](#do-kv-async-get), above.
 
 - `noCache` <Type text ='boolean' />
-  - Same as the option to [`get()`](#do-kv-async-get), above.
+  - Same as the option to [`get()`](#do-kv-async-get), above.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-storage-alarms.mdx b/src/content/partials/durable-objects/api-storage-alarms.mdx
index 1014b07d6080c01..8deccef0d3d08f2 100644
--- a/src/content/partials/durable-objects/api-storage-alarms.mdx
+++ b/src/content/partials/durable-objects/api-storage-alarms.mdx
@@ -27,4 +27,4 @@ import { Type, MetaInfo, Render } from "~/components";
 
 #### Supported options
 
-- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
+- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-storage-other-methods.mdx b/src/content/partials/durable-objects/api-storage-other-methods.mdx
index 50cc1584f88f26d..05bf6d643f93346 100644
--- a/src/content/partials/durable-objects/api-storage-other-methods.mdx
+++ b/src/content/partials/durable-objects/api-storage-other-methods.mdx
@@ -39,4 +39,4 @@ import { Type, MetaInfo } from "~/components";
 - `sync()`: <Type text='Promise' />
   - Synchronizes any pending writes to disk.
 
-  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
+  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-sync-kv.mdx b/src/content/partials/durable-objects/api-sync-kv.mdx
index 84a39a044b3d293..816f231f927d279 100644
--- a/src/content/partials/durable-objects/api-sync-kv.mdx
+++ b/src/content/partials/durable-objects/api-sync-kv.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Type, MetaInfo } from "~/components";
+import {Type, MetaInfo} from "~/components";
 
 ### `get`
 
diff --git a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
index c869d21821c71a3..ea25a405ba4567b 100644
--- a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
+++ b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
@@ -2,8 +2,8 @@
 {}
 ---
 
-import { GlossaryTooltip, WranglerConfig } from "~/components";
+import {GlossaryTooltip, WranglerConfig} from "~/components";
 
 ### How can I identify which Durable Object instance generated a log entry?
 
-You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
+You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/do-plans-note.mdx b/src/content/partials/durable-objects/do-plans-note.mdx
index 3c7cb86f3649773..36771fa0ccba055 100644
--- a/src/content/partials/durable-objects/do-plans-note.mdx
+++ b/src/content/partials/durable-objects/do-plans-note.mdx
@@ -9,4 +9,4 @@ Durable Objects are available both on Workers Free and Workers Paid plans.
 - **Workers Paid plan**: Durable Objects with either SQLite storage backend or [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) are available.
 
 If you wish to downgrade from a Workers Paid plan to a Workers Free plan, you must first ensure that you have deleted all Durable Object namespaces with the key-value storage backend.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/durable-objects-sql.mdx b/src/content/partials/durable-objects/durable-objects-sql.mdx
index b13e5deb71af0d6..43eb7777f652040 100644
--- a/src/content/partials/durable-objects/durable-objects-sql.mdx
+++ b/src/content/partials/durable-objects/durable-objects-sql.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
 [SQL API](/durable-objects/api/sqlite-storage-api/#exec) examples below use the following SQL schema:
 
@@ -10,114 +10,102 @@ import { Details } from "~/components";
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-	sql: SqlStorage;
-	constructor(ctx: DurableObjectState, env: Env) {
-		super(ctx, env);
-		this.sql = ctx.storage.sql;
+  sql: SqlStorage
+  constructor(ctx: DurableObjectState, env: Env) {
+    super(ctx, env);
+    this.sql = ctx.storage.sql;
 
-		this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
+    this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
       artistid    INTEGER PRIMARY KEY,
       artistname  TEXT
     );INSERT INTO artist (artistid, artistname) VALUES
       (123, 'Alice'),
       (456, 'Bob'),
-      (789, 'Charlie');`);
-	}
+      (789, 'Charlie');`
+    );
+  }
 }
 ```
 
 Iterate over query results as row objects:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist;");
+  let cursor = this.sql.exec("SELECT * FROM artist;");
 
-for (let row of cursor) {
-	// Iterate over row object and do something
-}
+  for (let row of cursor) {
+    // Iterate over row object and do something
+  }
 ```
 
 Convert query results to an array of row objects:
-
 ```ts
-// Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
-let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
-// OR
-let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
-// OR
-let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
+  // Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
+  let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
+  // OR
+  let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
+  // OR
+  let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
 ```
 
 Convert query results to an array of row values arrays:
-
 ```ts
-// Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
-let cursor = this.sql.exec("SELECT * FROM artist;");
-let resultsArray = cursor.raw().toArray();
-
-// Returns ["artistid","artistname"]
-let columnNameArray = this.sql
-	.exec("SELECT * FROM artist;")
-	.columnNames.toArray();
+  // Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
+  let cursor = this.sql.exec("SELECT * FROM artist;");
+  let resultsArray = cursor.raw().toArray();
+
+  // Returns ["artistid","artistname"]
+  let columnNameArray = this.sql.exec("SELECT * FROM artist;").columnNames.toArray();
 ```
 
 Get first row object of query results:
-
 ```ts
-// Returns {"artistid":123,"artistname":"Alice"}
-let firstRow = this.sql
-	.exec("SELECT * FROM artist ORDER BY artistname DESC;")
-	.toArray()[0];
+  // Returns {"artistid":123,"artistname":"Alice"}
+  let firstRow = this.sql.exec("SELECT * FROM artist ORDER BY artistname DESC;").toArray()[0];
 ```
 
 Check if query results have exactly one row:
-
 ```ts
-// returns error
-this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
+  // returns error
+  this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
 
-// returns { artistid: 123, artistname: 'Alice' }
-let oneRow = this.sql
-	.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice")
-	.one();
+  // returns { artistid: 123, artistname: 'Alice' }
+  let oneRow = this.sql.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice").one()
 ```
 
 Returned cursor behavior:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-let result = cursor.next();
-if (!result.done) {
-	console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
-} else {
-	// query returned zero results
-}
-
-let remainingRows = cursor.toArray();
-console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+  let result = cursor.next();
+  if (!result.done) {
+    console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
+  } else {
+    // query returned zero results
+  }
+
+  let remainingRows = cursor.toArray();
+  console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 Returned cursor and `raw()` iterator iterate over the same query results:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-let result = cursor.raw().next();
+  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+  let result = cursor.raw().next();
 
-if (!result.done) {
-	console.log(result.value); // prints [ 123, 'Alice' ]
-} else {
-	// query returned zero results
-}
+  if (!result.done) {
+    console.log(result.value); // prints [ 123, 'Alice' ]
+  } else {
+    // query returned zero results
+  }
 
-console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+  console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 `sql.exec().rowsRead()`:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist;");
-cursor.next();
-console.log(cursor.rowsRead); // prints 1
+  let cursor = this.sql.exec("SELECT * FROM artist;");
+  cursor.next()
+  console.log(cursor.rowsRead); // prints 1
 
-cursor.toArray(); // consumes remaining cursor
-console.log(cursor.rowsRead); // prints 3
+  cursor.toArray(); // consumes remaining cursor
+  console.log(cursor.rowsRead); // prints 3
 ```
+
diff --git a/src/content/partials/durable-objects/recommend-sqlite-do.mdx b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
index 0d406290b88226e..dea8504982d30c4 100644
--- a/src/content/partials/durable-objects/recommend-sqlite-do.mdx
+++ b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
@@ -8,4 +8,4 @@ Cloudflare recommends all new Durable Object namespaces use the [SQLite storage
 Additionally, SQLite-backed Durable Objects allow you to store more types of data (such as tables), and offer Point In Time Recovery API which can restore a Durable Object's embedded SQLite database contents (both SQL data and key-value data) to any point in the past 30 days.
 
 The [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) remains for backwards compatibility, and a migration path from KV storage backend to SQLite storage backend for existing Durable Object namespaces will be available in the future.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/what-are-durable-objects.mdx b/src/content/partials/durable-objects/what-are-durable-objects.mdx
index 82e992b0b2297d9..15b96c85f0f37a6 100644
--- a/src/content/partials/durable-objects/what-are-durable-objects.mdx
+++ b/src/content/partials/durable-objects/what-are-durable-objects.mdx
@@ -7,4 +7,4 @@ A Durable Object is a special kind of [Cloudflare Worker](/workers/) which uniqu
 - Each Durable Object has a **globally-unique name**, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together.
 - Each Durable Object has some **durable storage** attached. Since this storage lives together with the object, it is strongly consistent yet fast to access.
 
-Therefore, Durable Objects enable **stateful** serverless applications.
+Therefore, Durable Objects enable **stateful** serverless applications.
\ No newline at end of file
diff --git a/src/content/partials/email-routing/email-routing-definition.mdx b/src/content/partials/email-routing/email-routing-definition.mdx
index 6359302158f6bd7..b3fc4db641ed951 100644
--- a/src/content/partials/email-routing/email-routing-definition.mdx
+++ b/src/content/partials/email-routing/email-routing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Email Routing is designed to simplify the way you create and manage email addresses, without needing to keep an eye on additional mailboxes. With Email Routing, you can create any number of custom email addresses to use in situations where you do not want to share your primary email address, such as when you subscribe to a new service or newsletter. Emails are then routed to your preferred email inbox, without you ever having to expose your primary email address.
diff --git a/src/content/partials/email-routing/enable-create-worker.mdx b/src/content/partials/email-routing/enable-create-worker.mdx
index 0d37ad3ba5aaa03..240b23f507f76ab 100644
--- a/src/content/partials/email-routing/enable-create-worker.mdx
+++ b/src/content/partials/email-routing/enable-create-worker.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 4. (Optional) Enter a descriptive Email Worker name in **Create a worker name**.
diff --git a/src/content/partials/email-routing/send-emails-workers-intro.mdx b/src/content/partials/email-routing/send-emails-workers-intro.mdx
index e71d08e38f239f7..0e3bcc4027b1122 100644
--- a/src/content/partials/email-routing/send-emails-workers-intro.mdx
+++ b/src/content/partials/email-routing/send-emails-workers-intro.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: lastSentence
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 You can send an email about your Worker's activity from your Worker to an email address verified on [Email Routing](/email-routing/setup/email-routing-addresses/#destination-addresses). This is useful for when you want to know about certain types of events being triggered, for example.
 
diff --git a/src/content/partials/email-routing/types-bindings.mdx b/src/content/partials/email-routing/types-bindings.mdx
index 5d33d135b31a988..a15b5284b492f9d 100644
--- a/src/content/partials/email-routing/types-bindings.mdx
+++ b/src/content/partials/email-routing/types-bindings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/email-security/add-user.mdx b/src/content/partials/email-security/add-user.mdx
index 274d07c1c67b2ae..b36f104c9f96b1f 100644
--- a/src/content/partials/email-security/add-user.mdx
+++ b/src/content/partials/email-security/add-user.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: childParentInfo
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. Log in to the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/) {props.one}.
 2. Go to **Settings** (the gear icon).
diff --git a/src/content/partials/email-security/auto-retraction.mdx b/src/content/partials/email-security/auto-retraction.mdx
index aba4b1ad99db360..bbaf21ca8a016d6 100644
--- a/src/content/partials/email-security/auto-retraction.mdx
+++ b/src/content/partials/email-security/auto-retraction.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: hardRetract
+
 ---
 
-import { GlossaryTooltip, Markdown } from "~/components";
+import { GlossaryTooltip, Markdown } from "~/components"
 
 You can set up auto-retraction to automatically move messages matching certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to specific folders within a user's mailbox.
 
@@ -17,11 +18,12 @@ To set up automatic retraction:
 4. Select **Edit**.
 
 5. For each disposition, choose which folder the message should be sent to:
-   - **No Action**: Do not move the message.
-   - **Junk Email**: Sends the message to the junk or spam email folder.
-   - **Trash**: Sends the message to the trash or deleted items email folder.
-   - **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
-   - **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
+
+   * **No Action**: Do not move the message.
+   * **Junk Email**: Sends the message to the junk or spam email folder.
+   * **Trash**: Sends the message to the trash or deleted items email folder.
+   * **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
+   * **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
 
 6. Select **Update Auto-retract Settings**.
 
@@ -31,5 +33,5 @@ Email Security (formerly Area 1) is continuously gathering new information about
 
 You can enable two options:
 
-- **Post Delivery Response**: Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
-- **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
+* **Post Delivery Response**:  Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
+* **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
\ No newline at end of file
diff --git a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
index 5c8fd8d25359499..06080642f1da59c 100644
--- a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Now that Email Security (formerly Area 1) has been authorized to access and retrieve directory information, you will need to configure the Business Email Compromise list.
diff --git a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
index 423c5edd0ddce5b..d13f48b4b6e1ecd 100644
--- a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When the Business Email Compromise list is configured, Email Security (formerly Area 1) will enforce the proper match of the sender’s display name and email address. Any variation from this strict requirement will raise a detection event. The reason of detection will be `Protected Name <NAME> should not appear as <non-configured email address>`.
diff --git a/src/content/partials/email-security/contact-support.mdx b/src/content/partials/email-security/contact-support.mdx
index b4a2c7c68ef7575..5378b3ab6111c21 100644
--- a/src/content/partials/email-security/contact-support.mdx
+++ b/src/content/partials/email-security/contact-support.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::caution[Access to Area 1]
 Beginning October 1, 2025, access and support for Email Security (formerly Area 1) will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
index fb9b79de16a89ea..5d3c830d646535b 100644
--- a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
 Select from the following BCC addresses to process email in the correct geographic location.
 
-| Host                                                                   | Location                | Note                                                                                                               |
+| Host                                        | Location                | Note                                                                                                               |
 | ---------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `<customer_name>@journaling.mxrecord.io`                               | US                      | Best option to ensure all email traffic processing happens US data centers.                                        |
-| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
-| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.        |
+| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.           |
+| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.      |
 | `<customer_name>@journaling.mailstream-bom.mxrecord.mx`                | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
-| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
+| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                            |
+| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.                                                            |
 | `<customer_name>@journaling.mailstream-syd.area1.cloudflare.net`       | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
 | `<customer_name>@journaling.mailstream-australia.area1.cloudflare.net` | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/mx-deployment-values.mdx b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
index 6c51818a2f48130..7159d1c82e5849e 100644
--- a/src/content/partials/email-security/deployment/mx-deployment-values.mdx
+++ b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | MX Priority | Host                             |
diff --git a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
index 0486462814a3d07..c4e31a82c6cc983 100644
--- a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
@@ -1,17 +1,18 @@
 ---
 {}
+
 ---
 
 When configuring the Email Security (formerly Area 1) MX records, it is important to configure hosts with the correct MX priority. This will allow mail flows to the preferred hosts and fail over as needed.
 
 Choose from the following Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
 
-| Host                                                                                                                             | Location                | Note                                                                                                               |
-| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                              |
-| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
-| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
-| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
-| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
-| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
+| Host                                                                                                                             | Location                | Note                                                                                                                                                                                  |
+| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                                                                                                 |
+| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.                                                                              |
+| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.
+| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                                                                                               |
+| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.
+| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                                                                                          |
+| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup.                                                                    |
diff --git a/src/content/partials/email-security/deployment/o365-gcc.mdx b/src/content/partials/email-security/deployment/o365-gcc.mdx
index 452dc5782964883..94afd5f4a9ae9d6 100644
--- a/src/content/partials/email-security/deployment/o365-gcc.mdx
+++ b/src/content/partials/email-security/deployment/o365-gcc.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
index 7e6a508dd4c5951..2de2cfae20b80ed 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create quarantine policies:
@@ -19,8 +20,9 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
index e797688ae2d418e..ffd9e7b6f9ee7a9 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create quarantine policies:
@@ -19,8 +20,9 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-allow-message-release.png)
 
@@ -41,8 +43,9 @@ To create quarantine policies:
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
-    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
+    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
     ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
index 8acc6ea1e36ac83..075e0dfe8e17426 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: quarantinePolicy
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 You first need to configure the domains you are onboarding on the Email Security (formerly Area 1) dashboard. To configure your domains:
 
@@ -11,9 +12,9 @@ You first need to configure the domains you are onboarding on the Email Security
 3. Go to **Email configuration** > **Domains & Routing** > **Domains**.
 4. Make sure each domain you are onboarding has been added.
 5. For each domain you are configuring, select **...** > **Edit**, and set the following options:
-   - **Domain** - `<YOUR_DOMAIN>`.
-   - **Configured as** - `MX Records`.
-   - **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
-   - **IP Restrictions** - Leave this field empty.
-   - **Outbound TLS** - `Forward all messages over TLS`.
-   - **Quarantine Policy** - {props.one}
+   * **Domain** - `<YOUR_DOMAIN>`.
+   * **Configured as** - `MX Records`.
+   * **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
+   * **IP Restrictions** - Leave this field empty.
+   * **Outbound TLS** - `Forward all messages over TLS`.
+   * **Quarantine Policy** - {props.one}
diff --git a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
index 5ecfa3d112baa85..0f3c8996e8dba65 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
@@ -1,9 +1,10 @@
 ---
 inputParameters: ruleName;;ruleWords;;doFollowing;;img;;ruleName2;;ruleWords2;;doFollowing2;;img2
+
 ---
 
-import { Image } from "astro:assets";
-import { GlossaryTooltip, Markdown } from "~/components";
+import { Image } from 'astro:assets';
+import { GlossaryTooltip, Markdown } from "~/components"
 
 To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Email Security:
 
@@ -14,15 +15,16 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 3. Select **Add a Rule** > **Create a new rule**.
 
 4. Set the following rule conditions:
-   - **Name**: _{props.one}_.
-   - **Apply this rule if**: _The message headers_ > _includes any of these words_.
-     - **Enter text**: `X-Area1Security-Disposition` > **Save**.
-     - **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
-   - **Apply this rule if**: Select **+** to add a second condition.
-   - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-   - **Do the following** - _{props.three}_.
 
-{/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
+   * **Name**: *{props.one}*.
+   * **Apply this rule if**: *The message headers* > *includes any of these words*.
+     * **Enter text**: `X-Area1Security-Disposition` > **Save**.
+     * **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
+   * **Apply this rule if**: Select **+** to add a second condition.
+   * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+   * **Do the following** - *{props.three}*.
+
+ {/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
 
 5. Select **Next**.
 
@@ -35,15 +37,16 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 9. Select **Add a Rule** > **Create a new rule**.
 
 10. Set the following rule conditions:
-    - **Name**: _{props.five}_.
-    - **Apply this rule if**: _The message headers_ > _includes any of these words_.
-      - **Enter text**: `X-Area1Security-Disposition` > **Save**.
-      - **Enter words**: _{props.six}_ > **Add** > **Save**.
-    - **Apply this rule if**: Select **+** to add a second condition.
-    - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-    - **Do the following**: _{props.seven}_.
 
-{/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
+    * **Name**: *{props.five}*.
+    * **Apply this rule if**: *The message headers* > *includes any of these words*.
+      * **Enter text**: `X-Area1Security-Disposition` > **Save**.
+      * **Enter words**: *{props.six}* > **Add** > **Save**.
+    * **Apply this rule if**: Select **+** to add a second condition.
+    * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+    * **Do the following**: *{props.seven}*.
+
+ {/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
 
 11. Select **Next**.
 
@@ -51,4 +54,4 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 
 13. Review your settings and select **Finish** > **Done**.
 
-14. Select the rule _{props.five}_ you have just created, and select **Enable**.
+14. Select the rule *{props.five}* you have just created, and select **Enable**.
diff --git a/src/content/partials/email-security/deployment/setup-api-overview.mdx b/src/content/partials/email-security/deployment/setup-api-overview.mdx
index 749c98c3bfc1b4a..42cb0c0bf4e1c36 100644
--- a/src/content/partials/email-security/deployment/setup-api-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-api-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Email Security after they have already reached a user's inbox.
@@ -12,18 +13,18 @@ Then, through on integrations with your email provider, Email Security can [retr
 
 When you choose API deployment, you get the following benefits:
 
-- Easy protection for complex email architectures, without requiring any change to mailflow operations.
-- Agentless deployment for Microsoft 365 and Gmail.
-- The initial email protection measures offered by your current email provider.
+* Easy protection for complex email architectures, without requiring any change to mailflow operations.
+* Agentless deployment for Microsoft 365 and Gmail.
+* The initial email protection measures offered by your current email provider.
 
 ## Limitations
 
 However, API deployment also has the following disadvantages:
 
-- Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
-- Email Security requires read and write access to mailboxes.
-- Requires API support from your email provider (does not typically support on-premise providers).
-- Your email provider may throttle API requests from Email Security.
-- Detection rates may be lower if multiple solutions exist.
-- Messages cannot be modified or quarantined.
-- Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
+* Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
+* Email Security requires read and write access to mailboxes.
+* Requires API support from your email provider (does not typically support on-premise providers).
+* Your email provider may throttle API requests from Email Security.
+* Detection rates may be lower if multiple solutions exist.
+* Messages cannot be modified or quarantined.
+* Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
diff --git a/src/content/partials/email-security/deployment/setup-inline-overview.mdx b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
index 70fac3460c076fb..a7473c6318abaea 100644
--- a/src/content/partials/email-security/deployment/setup-inline-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 With an **Inline deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), Email Security evaluates email messages before they reach a user's inbox.
 
@@ -14,11 +15,11 @@ More technically, Email Security becomes a hop in the <GlossaryTooltip term="SMT
 
 When you choose an inline deployment, you get the following benefits:
 
-- Messages are processed and physically blocked before delivery to a user's mailbox.
-- Your deployment is simpler, because any complex processing can happen downstream and without modification.
-- Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
-- Email Security can offer high availability and adaptive message pooling.
-- You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
+* Messages are processed and physically blocked before delivery to a user's mailbox.
+* Your deployment is simpler, because any complex processing can happen downstream and without modification.
+* Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
+* Email Security can offer high availability and adaptive message pooling.
+* You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
 
 ## Limitations
 
diff --git a/src/content/partials/email-security/deployment/setup-overview.mdx b/src/content/partials/email-security/deployment/setup-overview.mdx
index 272608e20f764f3..d8963b1ca171ef2 100644
--- a/src/content/partials/email-security/deployment/setup-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you configure Email Security (formerly Area 1) Email Security to protect your organization, you can choose between two main setup architectures: Inline and API.
diff --git a/src/content/partials/email-security/email-security-description.mdx b/src/content/partials/email-security/email-security-description.mdx
index a613aab3d39121a..f65277d146ce070 100644
--- a/src/content/partials/email-security/email-security-description.mdx
+++ b/src/content/partials/email-security/email-security-description.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 <GlossaryTooltip term="phishing">Phishing</GlossaryTooltip> is the root cause of upwards of 90% of breaches that lead to financial loss and brand damage. Email Security (formerly Area 1) is a cloud-native service that stops phishing attacks across all threat vectors either at the [edge](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/) or in the cloud.
 
diff --git a/src/content/partials/email-security/outbound-email.mdx b/src/content/partials/email-security/outbound-email.mdx
index b7cc2413e883e96..1ed881d40a0dd1b 100644
--- a/src/content/partials/email-security/outbound-email.mdx
+++ b/src/content/partials/email-security/outbound-email.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/email-security/rename-area1-to-ces.mdx b/src/content/partials/email-security/rename-area1-to-ces.mdx
index ab1890e42fc4e97..4e5b20b1df6b4ea 100644
--- a/src/content/partials/email-security/rename-area1-to-ces.mdx
+++ b/src/content/partials/email-security/rename-area1-to-ces.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Area 1 has been renamed]
diff --git a/src/content/partials/email-security/search.mdx b/src/content/partials/email-security/search.mdx
index 6e314af0ce256bd..2a9c170e7e24c0e 100644
--- a/src/content/partials/email-security/search.mdx
+++ b/src/content/partials/email-security/search.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 1. **Detections only** is enabled by default. This means that the system will only search through and display emails that Email Security (formerly Area 1) has marked with a detection <GlossaryTooltip term="disposition" link="/email-security/reference/dispositions-and-attributes/">disposition</GlossaryTooltip>. If you prefer to search through and view all emails that have been processed by Email Security, whether they are marked with a detection disposition or not, disable this option.
 2. The **All detections** drop-down menu allows you to refine your search by detection disposition. This menu will be disabled if **Detections only** is not selected.
 3. By default, the search results are limited to the previous 30 days. Select **Last 30 days** to change this setting.
 4. (Optional) You can download the results from your search in CSV format. The CSV file is capped at 1,000 rows.
 5. The system returns a list of emails that fit your search criteria, and will inform you if there are emails similar to the ones found. If Email Security finds emails similar to the ones returned by your query, select **Show** to display them. Otherwise, select **View** on the email you are interested in. This will show you more information about that particular email, such as:
-   - Disposition (if any)
-   - Email status (for example `Quarantined`)
-   - Sender details (for example, IP address)
+   * Disposition (if any)
+   * Email status (for example `Quarantined`)
+   * Sender details (for example, IP address)
diff --git a/src/content/partials/email-security/service-addresses.mdx b/src/content/partials/email-security/service-addresses.mdx
index 5440ee7231acb79..6e22907a82f13d1 100644
--- a/src/content/partials/email-security/service-addresses.mdx
+++ b/src/content/partials/email-security/service-addresses.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/email-security/sso-enforcement.mdx b/src/content/partials/email-security/sso-enforcement.mdx
index 8ff51749311a532..bf094a37f8a0fc8 100644
--- a/src/content/partials/email-security/sso-enforcement.mdx
+++ b/src/content/partials/email-security/sso-enforcement.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
-- **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
-- **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
-- **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
+* **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
+* **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
+* **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
diff --git a/src/content/partials/fundamentals/account-audit-logs-definition.mdx b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
index 524d5179caa2fed..f8c6c30b76e700a 100644
--- a/src/content/partials/fundamentals/account-audit-logs-definition.mdx
+++ b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Audit logs summarize the history of changes made within your Cloudflare account. Audit logs include account level actions like login, as well as zone configuration changes.
@@ -8,6 +9,8 @@ Audit Logs are available on all plan types and are captured for both individual
 
 :::note
 
+
 Most beta features will not appear in audit logs until they are out of beta.
 
+
 :::
diff --git a/src/content/partials/fundamentals/account-manage-active-sessions.mdx b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
index 68aba8bba607b09..4be15fc6addf57f 100644
--- a/src/content/partials/fundamentals/account-manage-active-sessions.mdx
+++ b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 In the Cloudflare dashboard, you can view a list of active sessions associated with your email address.
@@ -10,8 +11,10 @@ If you notice any suspicious activity, you can also revoke any active sessions.
 
 :::note
 
+
 By default, the session timeout for the Cloudflare dashboard is 72 hours without any activity.
 
 Some customers can also enforce single-sign on (SSO) by [adding a Dashboard SSO application](/fundamentals/manage-members/dashboard-sso/).
 
+
 :::
diff --git a/src/content/partials/fundamentals/account-member-manage-limitation.mdx b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
index 67c9f962a22856f..9d7535b542de061 100644
--- a/src/content/partials/fundamentals/account-member-manage-limitation.mdx
+++ b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/).
diff --git a/src/content/partials/fundamentals/api-change-api-key.mdx b/src/content/partials/fundamentals/api-change-api-key.mdx
index 06ec545d2f3cd2a..215b04ead3be1e3 100644
--- a/src/content/partials/fundamentals/api-change-api-key.mdx
+++ b/src/content/partials/fundamentals/api-change-api-key.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ If your API key might be compromised, change your API key:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **API Tokens**.
 3. In the **API Keys** section, find your key.
diff --git a/src/content/partials/fundamentals/api-combine-filters.mdx b/src/content/partials/fundamentals/api-combine-filters.mdx
index 01c8e615b939694..6e4a1b16a8df9cf 100644
--- a/src/content/partials/fundamentals/api-combine-filters.mdx
+++ b/src/content/partials/fundamentals/api-combine-filters.mdx
@@ -1,15 +1,18 @@
 ---
 {}
+
 ---
 
 Combine filters using `OR` and `AND` boolean logic:
 
-- `AND` takes precedence over `OR` in all expressions.
-- The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
-- The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
+* `AND` takes precedence over `OR` in all expressions.
+* The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
+* The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
 
   :::note
 
+
   Note that the semicolon is a reserved character in URLs ([RFC 1738](https://www.rfc-editor.org/rfc/rfc1738)) and should be percent-encoded as `%3B`.
 
+
   :::
diff --git a/src/content/partials/fundamentals/api-filter-operators.mdx b/src/content/partials/fundamentals/api-filter-operators.mdx
index 57f6d12acfe8282..fd3a372b4041816 100644
--- a/src/content/partials/fundamentals/api-filter-operators.mdx
+++ b/src/content/partials/fundamentals/api-filter-operators.mdx
@@ -1,14 +1,18 @@
 ---
 inputParameters: param1;;param2;;param3;;param4
+
 ---
 
-import { Markdown } from "~/components";
 
-| Operator | Name                     | Example                                  | Description                                                                                  | URL Encoded |
-| -------- | ------------------------ | ---------------------------------------- | -------------------------------------------------------------------------------------------- | ----------- |
-| `==`     | Equals                   | <code>{props.one}=={props.two}</code>    | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.           | `%3D%3D`    |
-| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code> | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>. | `!%3D`      |
-| `>`      | Greater than             | `dimension>1000`                         | Return results where a dimension is greater than `1000`.                                     | `%3E`       |
-| `<`      | Less than                | `dimension<1000`                         | Return results where a dimension is less than `1000`.                                        | `%3C`       |
-| `>=`     | Greater than or equal to | `dimension>=1000`                        | Return results where a dimension is greater than or equal to `1000`.                         | `%3E%3D`    |
-| `<=`     | Less than or equal to    | `dimension<=1000`                        | Return results where a dimension is less than or equal to `1000`.                            | `%3C%3D`    |
+
+import { Markdown } from "~/components"
+
+| Operator | Name                     | Example           | Description                                                          | URL Encoded |
+| -------- | ------------------------ | ----------------- | -------------------------------------------------------------------- | ----------- |
+| `==`     | Equals                   | <code>{props.one}=={props.two}</code>          | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.                           | `%3D%3D`    |
+| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code>         | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>.                    | `!%3D`      |
+| `>`      | Greater than             | `dimension>1000`  | Return results where a dimension is greater than `1000`.             | `%3E`       |
+| `<`      | Less than                | `dimension<1000`  | Return results where a dimension is less than `1000`.                | `%3C`       |
+| `>=`     | Greater than or equal to | `dimension>=1000` | Return results where a dimension is greater than or equal to `1000`. | `%3E%3D`    |
+| `<=`     | Less than or equal to    | `dimension<=1000` | Return results where a dimension is less than or equal to `1000`.    | `%3C%3D`    |
+
diff --git a/src/content/partials/fundamentals/api-rate-limits.mdx b/src/content/partials/fundamentals/api-rate-limits.mdx
index 37822f640908916..09202c8b7845f04 100644
--- a/src/content/partials/fundamentals/api-rate-limits.mdx
+++ b/src/content/partials/fundamentals/api-rate-limits.mdx
@@ -6,16 +6,16 @@ params:
 import { AnchorHeading } from "~/components";
 
 {props.showHeading && (
-<AnchorHeading title="API token limits" depth={2} />
+	<AnchorHeading title="API token limits" depth={2} />
 )}
 
-| Type                              | Limit                               |
-| --------------------------------- | ----------------------------------- |
-| Client API per user/account token | 1200/5 minutes                      |
-| Client API per IP                 | 200/second                          |
-| GraphQL                           | Varies by query cost. Max 320/5 min |
-| User API token quota              | 50                                  |
-| Account API token quota           | 500                                 |
+| Type                    | Limit                               |
+| ----------------------- | ----------------------------------- |
+| Client API per user/account token     | 1200/5 minutes        |
+| Client API per IP       | 200/second                          |
+| GraphQL                 | Varies by query cost. Max 320/5 min |
+| User API token quota    | 50                                  |
+| Account API token quota | 500                                 |
 
 :::note
 The global rate limit for the Cloudflare API is 1,200 requests per five minute period per user, and applies cumulatively regardless of whether the request is made via the dashboard, API key, or API token.
diff --git a/src/content/partials/fundamentals/api-using-api.mdx b/src/content/partials/fundamentals/api-using-api.mdx
index e5ae32ba9e53c09..b1ca2470c79d58c 100644
--- a/src/content/partials/fundamentals/api-using-api.mdx
+++ b/src/content/partials/fundamentals/api-using-api.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 Using the Cloudflare API requires authentication so that Cloudflare knows who is making requests and what permissions you have. [Create an API token](/fundamentals/api/get-started/create-token/) to grant access to the API to perform actions.
 
 :::note
 
+
 You can also authenticate with [API keys](/fundamentals/api/get-started/keys/), but these keys have [several limitations](/fundamentals/api/get-started/keys/#limitations) that make them less secure than API tokens. Whenever possible, use API tokens to interact with the Cloudflare API.
 
+
 :::
diff --git a/src/content/partials/fundamentals/audit-log-api.mdx b/src/content/partials/fundamentals/audit-log-api.mdx
index 6d53ba9530aa6e7..ce209127d72ff3f 100644
--- a/src/content/partials/fundamentals/audit-log-api.mdx
+++ b/src/content/partials/fundamentals/audit-log-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To get audit logs from the Cloudflare API, send a [GET request](/api/resources/audit_logs/methods/list/).
diff --git a/src/content/partials/fundamentals/create-account-best-practices.mdx b/src/content/partials/fundamentals/create-account-best-practices.mdx
index efc376dfbf7bcdb..8a878be2c868221 100644
--- a/src/content/partials/fundamentals/create-account-best-practices.mdx
+++ b/src/content/partials/fundamentals/create-account-best-practices.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you are creating an account for your team or a business, we recommend choosing an email alias or distribution list for your **Email**, such as `cloudflare@example.com`.
diff --git a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
index 24617a79253e1c1..5c9104ac3a59f7b 100644
--- a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
+++ b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
@@ -1,35 +1,36 @@
 ---
 {}
+
 ---
 
 Cloudflare’s recommended CIPA rule blocks the following content subcategories:
 
-- Adult Themes
-- Alcohol
-- Anonymizer
-- Brand Embedding
-- Child Abuse
-- Command and Control & Botnet
-- Cryptomining
-- DGA Domains
-- DNS Tunneling
-- Drugs
-- Gambling
-- Hacking
-- Malware
-- Militancy, Hate & Extremism
-- Nudity
-- P2P
-- Phishing
-- Pornography
-- Private IP Address
-- Profanity
-- Questionable Activities
-- School Cheating
-- Spam
-- Spyware
-- Tobacco
-- Violence
-- Weapons
+* Adult Themes
+* Alcohol
+* Anonymizer
+* Brand Embedding
+* Child Abuse
+* Command and Control & Botnet
+* Cryptomining
+* DGA Domains
+* DNS Tunneling
+* Drugs
+* Gambling
+* Hacking
+* Malware
+* Militancy, Hate & Extremism
+* Nudity
+* P2P
+* Phishing
+* Pornography
+* Private IP Address
+* Profanity
+* Questionable Activities
+* School Cheating
+* Spam
+* Spyware
+* Tobacco
+* Violence
+* Weapons
 
 Review the [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for more information.
diff --git a/src/content/partials/fundamentals/cybersafe-configuration.mdx b/src/content/partials/fundamentals/cybersafe-configuration.mdx
index 97c5c85cf1bc3fe..e8654c6c41b1e83 100644
--- a/src/content/partials/fundamentals/cybersafe-configuration.mdx
+++ b/src/content/partials/fundamentals/cybersafe-configuration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To facilitate compliance with CIPA requirements, administrators can [enable a single filtering policy option](/cloudflare-one/traffic-policies/dns-policies/common-policies/#turn-on-cipa-filter). This includes applying the required filter categories to block access to unwanted or harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-description.mdx b/src/content/partials/fundamentals/cybersafe-description.mdx
index a3f8e1c475bbb46..431d708d46e714b 100644
--- a/src/content/partials/fundamentals/cybersafe-description.mdx
+++ b/src/content/partials/fundamentals/cybersafe-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/sites/default/files/childrens_internet_protection_act_cipa.pdf) is a federal law enacted by the United States Congress to address concerns about children's access to inappropriate or harmful content over the Internet. CIPA requires K-12 schools and libraries that receive certain federal funding to implement Internet safety measures to protect minors from harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-requirements.mdx b/src/content/partials/fundamentals/cybersafe-requirements.mdx
index e6be7dae9a66a9c..833e37f87f33941 100644
--- a/src/content/partials/fundamentals/cybersafe-requirements.mdx
+++ b/src/content/partials/fundamentals/cybersafe-requirements.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 CIPA mandates that K-12 schools and libraries adopt Internet safety policies that include measures to block or filter access to specific categories of content. These categories encompass a wide range of topics that could be harmful or inappropriate for minors. Compliance with these requirements helps ensure that students' online experiences are safer and more secure.
diff --git a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
index 9973f9748eda869..2e2f41f8016c234 100644
--- a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
+++ b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 This program is only available to eligible school districts. To be eligible, Project Cybersafe School participants must be:
 
-- K-12 public school districts located in the United States.
-- Up to 2,500 students in the district.
+* K-12 public school districts located in the United States.
+* Up to 2,500 students in the district.
diff --git a/src/content/partials/fundamentals/idp-group-deprecation.mdx b/src/content/partials/fundamentals/idp-group-deprecation.mdx
index baaae6c04591975..05821b931796237 100644
--- a/src/content/partials/fundamentals/idp-group-deprecation.mdx
+++ b/src/content/partials/fundamentals/idp-group-deprecation.mdx
@@ -1,7 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 **Important Update:** Cloudflare now supports native User Groups for enhanced access control. This new feature replaces the previous method of directly assigning Cloudflare roles based on IdP group mappings (identified by the pattern `CF-<accountID> - <Role Name>`), which is deprecated as of June 2nd, 2025. SCIM Virtual Groups will reach end-of-life on December 2, 2025. Update your SCIM configurations using the instructions below to utilize User Groups for seamless provisioning.
 :::
+
+
+
+
diff --git a/src/content/partials/fundamentals/lists-import-notes.mdx b/src/content/partials/fundamentals/lists-import-notes.mdx
index 1325dd37dc9b03c..7b084592eb99561 100644
--- a/src/content/partials/fundamentals/lists-import-notes.mdx
+++ b/src/content/partials/fundamentals/lists-import-notes.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 Cloudflare will apply the following rules when you add items to an existing list (either manually or via CSV file):
 
-- Do not remove any existing list items before updating/adding items.
-- Update items that were already in the list.
-- Add items that were not present in the list.
+* Do not remove any existing list items before updating/adding items.
+* Update items that were already in the list.
+* Add items that were not present in the list.
diff --git a/src/content/partials/fundamentals/new-token-warning.mdx b/src/content/partials/fundamentals/new-token-warning.mdx
index 794191bf0e51bba..ebba0665c1f6103 100644
--- a/src/content/partials/fundamentals/new-token-warning.mdx
+++ b/src/content/partials/fundamentals/new-token-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Warning]
 
+
 The token secret is **only shown once**. Do not store the secret in plaintext where others can access it. Anyone with this token can perform the authorized actions against the resources that the token has access to.
 
+
 :::
diff --git a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
index 707af55fc2d4d48..8339d260cd8f0fd 100644
--- a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
+++ b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If **Pseudo IPv4** is set to `Overwrite Headers` - Cloudflare overwrites the existing `Cf-Connecting-IP` and `X-Forwarded-For` headers with a pseudo IPv4 address while preserving the real IPv6 address in `CF-Connecting-IPv6` header.
diff --git a/src/content/partials/fundamentals/revoke-active-sessions.mdx b/src/content/partials/fundamentals/revoke-active-sessions.mdx
index fc8a9e0c4c296c9..07d956a61afdf20 100644
--- a/src/content/partials/fundamentals/revoke-active-sessions.mdx
+++ b/src/content/partials/fundamentals/revoke-active-sessions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,7 +11,7 @@ To revoke a session:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 3. On a specific section, click **Revoke**.
diff --git a/src/content/partials/fundamentals/ubb-recommendation.mdx b/src/content/partials/fundamentals/ubb-recommendation.mdx
index d05b58438eb70b2..ec055f77df645ca 100644
--- a/src/content/partials/fundamentals/ubb-recommendation.mdx
+++ b/src/content/partials/fundamentals/ubb-recommendation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,15 +11,16 @@ To set up those notifications:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
+      <DashButton url="/?to=/:account/notifications" />
 
 2. On **Alert Type** of **Usage Based Billing**, click **Select**.
 
 3. Fill out the following information:
-   - **Name**
-   - **Product**
-   - **Notification limit** (exact metric will vary based on product)
-   - **Notification email**
+
+   * **Name**
+   * **Product**
+   * **Notification limit** (exact metric will vary based on product)
+   * **Notification email**
 
    :::note
    Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/).
diff --git a/src/content/partials/fundamentals/user-permissions-table.mdx b/src/content/partials/fundamentals/user-permissions-table.mdx
index 0a4067fc83f026d..5bcacf794820b2f 100644
--- a/src/content/partials/fundamentals/user-permissions-table.mdx
+++ b/src/content/partials/fundamentals/user-permissions-table.mdx
@@ -1,14 +1,15 @@
 ---
 inputParameters: editWord
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-| Name                     | Description                                                                                  |
-| ------------------------ | -------------------------------------------------------------------------------------------- |
-| API Tokens Read          | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).         |
-| API Tokens {props.one}   | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).        |
-| Memberships Read         | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
-| Memberships {props.one}  | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
-| User Details Read        | Grants read access to user details.                                                          |
-| User Details {props.one} | Grants write access to user details.                                                         |
+| Name              | Description                                                                                        |
+| ----------------- | -------------------------------------------------------------------------------------------------- |
+| API Tokens Read   | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).               |
+| API Tokens {props.one}     | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).              |
+| Memberships Read  | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
+| Memberships {props.one}    | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
+| User Details Read | Grants read access to user details.                                                                |
+| User Details {props.one}   | Grants write access to user details.                                                               |
diff --git a/src/content/partials/fundamentals/user-profiles.mdx b/src/content/partials/fundamentals/user-profiles.mdx
index 5f074fa4484f104..95d7406967bb114 100644
--- a/src/content/partials/fundamentals/user-profiles.mdx
+++ b/src/content/partials/fundamentals/user-profiles.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/user-profiles/customize-account/#notifications) and [Language preferences](/fundamentals/user-profiles/customize-account/#language).
 
-To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
+To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
\ No newline at end of file
diff --git a/src/content/partials/fundamentals/view-audit-log.mdx b/src/content/partials/fundamentals/view-audit-log.mdx
index ea0694e788fe9fc..34f479029436066 100644
--- a/src/content/partials/fundamentals/view-audit-log.mdx
+++ b/src/content/partials/fundamentals/view-audit-log.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,8 @@ You can search these audit logs by user email or domain and filter by date range
 
 :::note
 
+
 Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Logpush](/logs/logpush/) to make sure Audit Logs are always available and stored externally.
 
+
 :::
diff --git a/src/content/partials/fundamentals/what-is-cloudflare.mdx b/src/content/partials/fundamentals/what-is-cloudflare.mdx
index 7321651a4cf4000..6db16b67782d1fc 100644
--- a/src/content/partials/fundamentals/what-is-cloudflare.mdx
+++ b/src/content/partials/fundamentals/what-is-cloudflare.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Stream } from "~/components";
+import { Stream } from "~/components"
 
 Cloudflare is one of the world's largest [connectivity cloud networks](https://blog.cloudflare.com/welcome-to-connectivity-cloud). Today, anyone with an Internet presence can have faster and more secure websites and applications thanks to Cloudflare. This includes bloggers, businesses, and even non-profits.
 
diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
index 7f8df8ff66b23e8..17b0e04547941b8 100644
--- a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
+++ b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) is occurring. No other error codes will trigger a zero-downtime failover operation.
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
index 94ebfc3d69ff887..a0936f417ad77a4 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
@@ -29,7 +30,9 @@ Specifically:
 - The binding must be [a valid JavaScript variable name](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#variables). For example, `binding = "hyperdrive"` or `binding = "productionDB"` would both be valid names for the binding.
 - Your binding is available in your Worker at `env.<BINDING_NAME>`.
 
-If you wish to use a local database during development, you can add a `localConnectionString` to your Hyperdrive configuration with the connection string of your database:
+
+If you wish to use a local database during development, you can add a `localConnectionString` to your  Hyperdrive configuration with the connection string of your database:
+
 
 <WranglerConfig>
 
@@ -51,4 +54,4 @@ If you wish to use a local database during development, you can add a `localConn
 
 Learn more about setting up [Hyperdrive for local development](/hyperdrive/configuration/local-development/).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
index 55f58eb3fdaebda..2bccc59303de979 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
@@ -2,14 +2,7 @@
 {}
 ---
 
-import {
-	DashButton,
-	WranglerConfig,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { DashButton, WranglerConfig, Render, Tabs, TabItem, Steps } from "~/components";
 
 To configure Hyperdrive, you will need:
 
diff --git a/src/content/partials/hyperdrive/pooling-mode.mdx b/src/content/partials/hyperdrive/pooling-mode.mdx
index ca988038c32fd15..a06f46f412dcfe7 100644
--- a/src/content/partials/hyperdrive/pooling-mode.mdx
+++ b/src/content/partials/hyperdrive/pooling-mode.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool.
diff --git a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
index f4895b5eecb79bb..b1275de22aeb7e2 100644
--- a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
+++ b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
@@ -37,7 +37,7 @@ export default {
 			// If you are not using array types in your Postgres schema, disable `fetch_types` to avoid an additional round-trip (unnecessary latency)
 			fetch_types: false,
 
-			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.
+			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.  
 			prepare: true,
 		});
 
diff --git a/src/content/partials/learning-paths/cache-basic-diagram.mdx b/src/content/partials/learning-paths/cache-basic-diagram.mdx
index c44a888cabcaa1e..6555ff5ad8fcf75 100644
--- a/src/content/partials/learning-paths/cache-basic-diagram.mdx
+++ b/src/content/partials/learning-paths/cache-basic-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/learning-paths/cache-optimization.mdx b/src/content/partials/learning-paths/cache-optimization.mdx
index 48c74235eb911f9..890676e0f865216 100644
--- a/src/content/partials/learning-paths/cache-optimization.mdx
+++ b/src/content/partials/learning-paths/cache-optimization.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 A few ways to optimize Cloudflare caching include:
 
-- Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
-- Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
-- Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
+* Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
+* Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
+* Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
diff --git a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
index 6dba0749cadcf88..f15999e994d4aec 100644
--- a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Related content**
@@ -9,4 +10,4 @@ For additional resources on the China Network, refer to the following resources:
     - [Cloudflare China Network](/china-network/)
     - [CDN Global Acceleration (formerly China Express)](/china-network/concepts/global-acceleration/)
     - [Internet Content Provider (ICP)](/china-network/concepts/icp/)
-    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
+    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/china-network-overview-navigation.mdx b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
index 6e6fee7c6c5dfbd..5e5f0c651602e6f 100644
--- a/src/content/partials/learning-paths/china-network-overview-navigation.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
@@ -1,19 +1,20 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: How to speed up your web traffic inside mainland China"
-		description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
-		href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
-		description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
-		href="/learning-paths/china-network-overview/series/china-express-overview-2/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: How to speed up your web traffic inside mainland China"
+          description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
+          href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
+          description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
+          href="/learning-paths/china-network-overview/series/china-express-overview-2/"
+        />              
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
index b825a923b79a986..80b90de36b0e2f6 100644
--- a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
+++ b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address, by creating an outbound-only connections to Cloudflare’s global network.
 
-- **Security**: Very secure.
-- **Availability**: All customers.
-- **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
+* **Security**: Very secure.
+* **Availability**: All customers.
+* **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
diff --git a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
index 95cf4f8cf529595..7b1ca7fcfce93d8 100644
--- a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
+++ b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A distributed denial-of-service (DDoS) attack is where a large number of computers or devices, usually controlled by a single attacker, attempt to access a website or online service all at once. This flood of traffic can overwhelm the website's origin servers, causing the site to slow down or even crash.
@@ -17,4 +18,4 @@ sequenceDiagram;
     Origin Server-->>User: Unable to respond to user requests
 ```
 
-<br />
+<br/>
diff --git a/src/content/partials/learning-paths/email-record-origin-ip.mdx b/src/content/partials/learning-paths/email-record-origin-ip.mdx
index 5b5f2c45e1b9e18..94b82b3791865f7 100644
--- a/src/content/partials/learning-paths/email-record-origin-ip.mdx
+++ b/src/content/partials/learning-paths/email-record-origin-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If possible, do not host a mail service on the same server as the web resource you want to protect, since emails sent to non-existent addresses get bounced back to the attacker and reveal the mail server IP address.
diff --git a/src/content/partials/learning-paths/r2-series-navigation.mdx b/src/content/partials/learning-paths/r2-series-navigation.mdx
index 612ab4b973072ca..fdf03a46c5a8df9 100644
--- a/src/content/partials/learning-paths/r2-series-navigation.mdx
+++ b/src/content/partials/learning-paths/r2-series-navigation.mdx
@@ -1,33 +1,34 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Getting started with R2"
-		description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
-		href="/learning-paths/r2-intro/series/r2-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: Public buckets"
-		description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
-		href="/learning-paths/r2-intro/series/r2-2/"
-	/>
-	<LinkCard
-		title="Watch Episode 3: S3 API compatibility"
-		description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
-		href="/learning-paths/r2-intro/series/r2-3/"
-	/>
-	<LinkCard
-		title="Watch Episode 4: Migrating your bucket data"
-		description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
-		href="/learning-paths/r2-intro/series/r2-4/"
-	/>
-	<LinkCard
-		title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
-		description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
-		href="/learning-paths/r2-intro/series/r2-5/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Getting started with R2"
+          description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
+          href="/learning-paths/r2-intro/series/r2-1/"
+        />          
+      <LinkCard
+          title="Watch Episode 2: Public buckets"
+          description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
+          href="/learning-paths/r2-intro/series/r2-2/"
+        />    
+      <LinkCard
+          title="Watch Episode 3: S3 API compatibility"
+          description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
+          href="/learning-paths/r2-intro/series/r2-3/"
+        />    
+      <LinkCard
+          title="Watch Episode 4: Migrating your bucket data"
+          description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
+          href="/learning-paths/r2-intro/series/r2-4/"
+        />    
+      <LinkCard
+          title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
+          description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
+          href="/learning-paths/r2-intro/series/r2-5/"
+        />                                    
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/sase-series-navigation.mdx b/src/content/partials/learning-paths/sase-series-navigation.mdx
index 67412cf58413313..c9ac5dace4ee296 100644
--- a/src/content/partials/learning-paths/sase-series-navigation.mdx
+++ b/src/content/partials/learning-paths/sase-series-navigation.mdx
@@ -1,38 +1,40 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: The evolution of corporate networks"
-		description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
-		href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 2: Stop hosting your own VPN service"
-		description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
-		href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 3: Secure remote access to your critical infrastructure"
-		description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
-		href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 4: Connect and secure from any network to anywhere"
-		description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: The evolution of corporate networks"
+          description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
+          href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 2: Stop hosting your own VPN service"
+          description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
+          href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 3: Secure remote access to your critical infrastructure"
+          description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
+          href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 4: Connect and secure from any network to anywhere"
+          description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
   "
-		href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 5: Protect your users from Internet risks"
-		description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
-		href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
-	/>
-</CardGrid>
+          href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 5: Protect your users from Internet risks"
+          description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
+          href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
+      />                           
+        
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/warp-series-navigation.mdx b/src/content/partials/learning-paths/warp-series-navigation.mdx
index af1eed7e2a23691..30d3c3c2090ec52 100644
--- a/src/content/partials/learning-paths/warp-series-navigation.mdx
+++ b/src/content/partials/learning-paths/warp-series-navigation.mdx
@@ -1,18 +1,19 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
-		description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
-		href="/learning-paths/warp-overview-course/series/warp-basics-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: WARP diagnostic logs"
-		description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
-		href="/learning-paths/warp-overview-course/series/warp-basics-2/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
+          description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
+          href="/learning-paths/warp-overview-course/series/warp-basics-1/"
+        />              
+      <LinkCard
+          title="Watch Episode 2: WARP diagnostic logs"
+          description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
+          href="/learning-paths/warp-overview-course/series/warp-basics-2/"
+        />                   
+    </CardGrid>
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/workflows-series-navigation.mdx b/src/content/partials/learning-paths/workflows-series-navigation.mdx
index f037d68638048ed..3aef6a36002ba88 100644
--- a/src/content/partials/learning-paths/workflows-series-navigation.mdx
+++ b/src/content/partials/learning-paths/workflows-series-navigation.mdx
@@ -1,23 +1,24 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Understand Cloudflare Workflows"
-		description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
-		href="/learning-paths/workflows-course/series/workflows-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: Monitor and batch your website data"
-		description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
-		href="/learning-paths/workflows-course/series/workflows-2/"
-	/>
-	<LinkCard
-		title="Watch Episode 3: Use cron triggers to develop time-aware applications"
-		description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
-		href="/learning-paths/workflows-course/series/workflows-3/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Understand Cloudflare Workflows"
+          description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
+          href="/learning-paths/workflows-course/series/workflows-1/"
+        />          
+      <LinkCard
+          title="Watch Episode 2: Monitor and batch your website data"
+          description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
+          href="/learning-paths/workflows-course/series/workflows-2/"
+        />    
+      <LinkCard
+          title="Watch Episode 3: Use cron triggers to develop time-aware applications"
+          description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
+          href="/learning-paths/workflows-course/series/workflows-3/"
+        />                          
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
index 1432141f867394c..634c2666bff6d5b 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Restrict access for users included in an <GlossaryTooltip term="identity provider">identity provider (IdP)</GlossaryTooltip> user group for risky users. This policy ensures your security team can restrict traffic for users of whom malicious or suspicious activity was detected.
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
index 39d1803880c83b2..060cde6c1160533 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Block [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories), such as **Command and Control & Botnet** and **Malware**, based on Cloudflare's threat intelligence.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
index 0a419a55b8b121b..b9a22f0fb157e40 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The Cloudflare One Client (known as the Cloudflare One Agent in mobile app stores) encrypts designated traffic from a user's device to Cloudflare's global network. In this learning path, we will first define all of your parameters and deployment rules, and then we will install and connect the client. If you prefer to start the client download now, refer to [Download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/).
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
index 01f20205751345a..087954988839621 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-- Define which users can connect devices to your Zero Trust instance.
-- Configure global and device-specific settings for the Cloudflare One Client.
-- Route user traffic through Cloudflare Gateway.
-- Route domains to a private DNS server, if required.
+* Define which users can connect devices to your Zero Trust instance.
+* Configure global and device-specific settings for the Cloudflare One Client.
+* Route user traffic through Cloudflare Gateway.
+* Route domains to a private DNS server, if required.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
index f358209dc42676a..21e92853d18e27b 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render} from "~/components"
 
 An <GlossaryTooltip term="identity provider" link="https://www.cloudflare.com/learning/access-management/what-is-an-identity-provider/">identity provider (IdP)</GlossaryTooltip> stores and manages users' digital identities. You can integrate your existing identity provider with Cloudflare Zero Trust in order to manage user access to your private network. This requires configuration both in Cloudflare and with the identity provider itself.
 
diff --git a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
index 5317428531592d0..6af7493ea8d2e78 100644
--- a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Manually deploy the Cloudflare One Client on a test device.
-- Create an automated script to use with your organization's managed deployment tool.
-- View user traffic in Zero Trust.
+* Manually deploy the Cloudflare One Client on a test device.
+* Create an automated script to use with your organization's managed deployment tool.
+* View user traffic in Zero Trust.
diff --git a/src/content/partials/learning-paths/zero-trust/create-list.mdx b/src/content/partials/learning-paths/zero-trust/create-list.mdx
index db39846de4a243f..f5cc8a1e77768f5 100644
--- a/src/content/partials/learning-paths/zero-trust/create-list.mdx
+++ b/src/content/partials/learning-paths/zero-trust/create-list.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Gateway supports creating [lists](/cloudflare-one/reusable-components/lists/) of IPs, hostnames, or other entries to reference in your policies.
 
diff --git a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
index d1c2be740c04bb1..5f2f956a234b5a0 100644
--- a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Device enrollment permissions determine which users can connect new devices to your organization's Cloudflare Zero Trust instance. Once the user registers their device, the Cloudflare One Client will store their identity token and use it to authenticate to services in your private network.
 
diff --git a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
index af96e5d35431904..d7a5d2a680983d6 100644
--- a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
-| Disposition | Description                                                                                                                                                                                                                                                                                                                                                                                                                             | Recommendation                                                             |     |
-| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --- |
-| MALICIOUS   | Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                                                                                                                                                                                                                                                                                           | Block                                                                      |     |
-| SUSPICIOUS  | Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                                                                                                                                                                                                                                                                                                                    | Research these messages internally to evaluate legitimacy.                 |     |
-| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |     |
-| SPAM        | Traffic associated with non-malicious, commercial campaigns.                                                                                                                                                                                                                                                                                                                                                                            | Route to existing Spam quarantine folder.                                  |     |
-| BULK        | Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.                                                                                                                                                                                                              | Monitor or tag                                                             |     |
+| Disposition | Description                                                                                                                                                                                  | Recommendation                                                             |   |
+|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---|
+| MALICIOUS   |                                 Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                |                                    Block                                   |   |
+| SUSPICIOUS  |                                             Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                             |         Research these messages internally to evaluate legitimacy.         |   |
+| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |   |
+| SPAM        |                                                                 Traffic associated with non-malicious, commercial campaigns.                                                                 |                  Route to existing Spam quarantine folder.                 |   |
+| BULK        |       Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.       |                               Monitor or tag                               |   |
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
index 8a8dcfab6f7c924..e6800e57f7aafd3 100644
--- a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
+++ b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With Cloudflare Gateway, you can log and filter DNS, network, and HTTP traffic from devices running the Cloudflare One Client. This includes traffic to the public Internet and traffic directed to your private network. DNS filtering is enabled by default since the Cloudflare One Client sends DNS queries to Cloudflare's public DNS resolver, [1.1.1.1](/1.1.1.1/). To enable network and HTTP filtering, you will need to allow Cloudflare Gateway to proxy that traffic.
diff --git a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
index 4c1e0192bd1e400..fd8de62a9baadd6 100644
--- a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Set up a Cloudflare account.
-- Create a Zero Trust organization to manage your devices and policies.
-- Configure an identity provider (IdP) for user authentication.
+* Set up a Cloudflare account.
+* Create a Zero Trust organization to manage your devices and policies.
+* Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/partials/learning-paths/zero-trust/install-agent.mdx b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
index c0b8798b2485485..50221f53efc84d9 100644
--- a/src/content/partials/learning-paths/zero-trust/install-agent.mdx
+++ b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
@@ -1,32 +1,32 @@
 ---
 inputParameters: WARPsuccess
+
 ---
 
-import { Details, Markdown, Render } from "~/components";
+import { Details, Markdown, Render } from "~/components"
 
 Most admins test by manually downloading the Cloudflare One Client and enrolling in your organization's Cloudflare Zero Trust instance.
 
 ## Install the Cloudflare One Client
 
-1.  First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
-2.  If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
-
-    <Render file="warp/client-orchestration-ips" product="cloudflare-one" />
+1. First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
+2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
+  	<Render file="warp/client-orchestration-ips" product="cloudflare-one" />
 
-    For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
+	For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 
-3.  Manually install the Cloudflare One Client on the device.
+3. Manually install the Cloudflare One Client on the device.
 
-        <Details header="Window, macOS, and Linux">
+		<Details header="Window, macOS, and Linux">
 
-        <Render file="warp/enroll-desktop" product="cloudflare-one" />
+		<Render file="warp/enroll-desktop" product="cloudflare-one" />
 
-        </Details>
+		</Details>
 
-        <Details header="iOS, Android, and ChromeOS">
+		<Details header="iOS, Android, and ChromeOS">
 
-        <Render file="warp/enroll-ios-android" product="cloudflare-one" />
+		<Render file="warp/enroll-ios-android" product="cloudflare-one" />
 
-        </Details>
+		</Details>
 
 The Cloudflare One Client should show as **Connected**. {props.one}
diff --git a/src/content/partials/learning-paths/zero-trust/mdm.mdx b/src/content/partials/learning-paths/zero-trust/mdm.mdx
index 042067aab0fd199..d928a456aa181ac 100644
--- a/src/content/partials/learning-paths/zero-trust/mdm.mdx
+++ b/src/content/partials/learning-paths/zero-trust/mdm.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="warp/mdm-intro" product="cloudflare-one" />
 
diff --git a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
index d3ea3aaab5d3ff0..eb80c75bd1fbfa8 100644
--- a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
+++ b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render} from "~/components"
 
 Split tunnel settings determine which traffic the Cloudflare One Client does and does not proxy.
 
 The Cloudflare One Client offers two different split tunnel modes:
 
-- If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
-- If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
+* If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
+* If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
 
 ## Update Split Tunnels mode
 
diff --git a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
index 21f27878f44c392..5e3a0df5f6c077b 100644
--- a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
+++ b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
@@ -1,13 +1,10 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To validate that Cloudflare is receiving traffic from a user device:
 
-<Render
-	file="gateway/verify-connectivity"
-	product="cloudflare-one"
-	params={{ one: "DNS", two: "queries" }}
-/>
+<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
diff --git a/src/content/partials/load-balancing/components-knowledge-callout.mdx b/src/content/partials/load-balancing/components-knowledge-callout.mdx
index b8493c88bd03af8..75cdfecec22253a 100644
--- a/src/content/partials/load-balancing/components-knowledge-callout.mdx
+++ b/src/content/partials/load-balancing/components-knowledge-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This guide assumes you are familiar with the Cloudflare [Load Balancing components](/load-balancing/understand-basics/load-balancing-components/).
diff --git a/src/content/partials/load-balancing/custom-rules-definition.mdx b/src/content/partials/load-balancing/custom-rules-definition.mdx
index 49889fc8bc61ee2..87c37f08ebba3d4 100644
--- a/src/content/partials/load-balancing/custom-rules-definition.mdx
+++ b/src/content/partials/load-balancing/custom-rules-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom load balancing rules let you customize the behavior of your load balancer based on the characteristics of a request.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
index b05bdc170e119f5..2a826379296653d 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your load balancer is attached to a hostname used for an [`MX` or `SRV` record](/load-balancing/additional-options/additional-dns-records/) — and not an `A`, `AAAA`, or `CNAME` record — its proxy mode should be **DNS-only**.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
index 07047a05eddeed8..85d6c2a3775c9cf 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS-only load balancers route traffic by returning specific IP addresses in response to a client's DNS query.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
index ebcffa45dd9ce22..bc03d3b58635b6d 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 In comparison to proxied, layer 7 load balancing, DNS-only load balancing:
 
-- Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
-- Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
-- Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
-- Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
-- Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
-- Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
-- Does not support [Private Network Load Balancing](/load-balancing/private-network/).
+* Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
+* Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
+* Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
+* Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
+* Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
+* Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
+* Does not support [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
index b5888a2b8e97651..5a380e226cc7c4b 100644
--- a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
+++ b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Since load balancing targets are not limited to origin web servers, the term `endpoints` has been introduced. Refer to [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-other-terms/) for its use in the context of Cloudflare offerings, and to [load balancing concepts](/load-balancing/understand-basics/load-balancing-components/) or [Reference Architecture](/reference-architecture/architectures/load-balancing/) for use case examples.
diff --git a/src/content/partials/load-balancing/fallback-pools.mdx b/src/content/partials/load-balancing/fallback-pools.mdx
index bac40469f252c71..49f0595e95dc999 100644
--- a/src/content/partials/load-balancing/fallback-pools.mdx
+++ b/src/content/partials/load-balancing/fallback-pools.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This pool is meant to be the pool of last resort, meaning that its health is not taken into account when directing traffic.
diff --git a/src/content/partials/load-balancing/health-check-diagram.mdx b/src/content/partials/load-balancing/health-check-diagram.mdx
index 6b2bfb5560e0f49..568033512858810 100644
--- a/src/content/partials/load-balancing/health-check-diagram.mdx
+++ b/src/content/partials/load-balancing/health-check-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/health-check-regions.mdx b/src/content/partials/load-balancing/health-check-regions.mdx
index 85b94acbc34ab57..cb98a0bc269813a 100644
--- a/src/content/partials/load-balancing/health-check-regions.mdx
+++ b/src/content/partials/load-balancing/health-check-regions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For each option selected in a pool's **Health Monitor Regions**, Cloudflare sends health monitor requests from three separate data centers in that region.
diff --git a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
index aa5e650fec2b99b..e1379917600272c 100644
--- a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Layer 4 load balancers route traffic by forwarding traffic to certain ports or IP addresses.
@@ -8,6 +9,8 @@ Cloudflare currently only supports layer 4 load balancing as part of [Cloudflare
 
 :::note
 
+
 Since Spectrum operates at the TCP level, it does not have the information to support features like [session affinity](/load-balancing/understand-basics/session-affinity/), [custom rules](/load-balancing/additional-options/load-balancing-rules/), or caching.
 
+
 :::
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
index 5d6045bd0ac9477..9dfc53ccb56e590 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 In comparison to DNS-only load balancing, layer 7 load balancing:
 
-- Protects endpoints from DDoS attacks by hiding their IP addresses.
-- Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
-- Integrates with other Cloudflare features such as caching, Workers, and the WAF.
-- Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
-- Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
-- More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
-- Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
+* Protects endpoints from DDoS attacks by hiding their IP addresses.
+* Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
+* Integrates with other Cloudflare features such as caching, Workers, and the WAF.
+* Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
+* Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
+* More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
+* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
index 78f4d9da0758f11..120a77b9f1486a4 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Layer 7 load balancers direct traffic to specific endpoints based on information present in each HTTP/HTTPS request (HTTP headers, URI, cookies, type of data, etc.).
diff --git a/src/content/partials/load-balancing/load-balancer-create-api.mdx b/src/content/partials/load-balancing/load-balancer-create-api.mdx
index 9110fc3325a87d9..8dbe3ed3d7b8337 100644
--- a/src/content/partials/load-balancing/load-balancer-create-api.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -8,89 +9,91 @@ For a full list of properties, refer to [Create Load Balancer](/api/resources/lo
 
 :::note
 
+
 Since load balancers only exist on a zone — and not an account — you may need to get the zone `id` with the [List Zones](/api/resources/zones/methods/list/) command.
 
+
 :::
 
 <APIRequest
-	path="/zones/{zone_id}/load_balancers"
-	method="POST"
-	json={{
-		description: "Load Balancer for lb.example.com",
-		name: "lb.example.com",
-		enabled: true,
-		ttl: 30,
-		fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
-		default_pools: [
-			"17b5962d775c646f3f9725cbc7a53df4",
-			"9290f38c5d07c2e2f4df57b1f61d4196",
-			"00920f38ce07c2e2f4df50b1f61d4194",
-		],
-		proxied: true,
-		steering_policy: "random_steering",
-		session_affinity: "cookie",
-		session_affinity_attributes: {
-			samesite: "Auto",
-			secure: "Auto",
-			drain_duration: 100,
-			zero_downtime_failover: "sticky",
-		},
-		session_affinity_ttl: 5000,
-		adaptive_routing: {
-			failover_across_pools: true,
-		},
-		location_strategy: {
-			prefer_ecs: "always",
-			mode: "resolver_ip",
-		},
-		random_steering: {
-			pool_weights: {
-				de90f38ced07c2e2f4df50b1f61d4194: 0.3,
-				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5,
-			},
-			default_weight: 0.2,
-		},
-	}}
+  path="/zones/{zone_id}/load_balancers"
+  method="POST"
+  json={{
+    description: "Load Balancer for lb.example.com",
+    name: "lb.example.com",
+    enabled: true,
+    ttl: 30,
+    fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
+    default_pools: [
+      "17b5962d775c646f3f9725cbc7a53df4",
+      "9290f38c5d07c2e2f4df57b1f61d4196",
+      "00920f38ce07c2e2f4df50b1f61d4194"
+    ],
+    proxied: true,
+    steering_policy: "random_steering",
+    session_affinity: "cookie",
+    session_affinity_attributes: {
+      samesite: "Auto",
+      secure: "Auto",
+      drain_duration: 100,
+      zero_downtime_failover: "sticky"
+    },
+    session_affinity_ttl: 5000,
+    adaptive_routing: {
+      failover_across_pools: true
+    },
+    location_strategy: {
+      prefer_ecs: "always",
+      mode: "resolver_ip"
+    },
+    random_steering: {
+      pool_weights: {
+        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+      },
+      default_weight: 0.2
+    }
+  }}
 />
 
 The response contains the complete definition of the new load balancer.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "699d98642c564d2e855e9661899b7252",
-		"created_on": "2021-01-01T05:20:00.12345Z",
-		"modified_on": "2021-01-01T05:20:00.12345Z",
-		"description": "Load Balancer for lb.example.com",
-		"name": "lb.example.com",
-		"enabled": true,
-		"ttl": 30,
-		"fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
-		"default_pools": [
-			"17b5962d775c646f3f9725cbc7a53df4",
-			"9290f38c5d07c2e2f4df57b1f61d4196",
-			"00920f38ce07c2e2f4df50b1f61d4194"
-		],
-		"proxied": true,
-		"steering_policy": "random_steering",
-		"session_affinity": "cookie",
-		"session_affinity_attributes": {
-			"samesite": "Auto",
-			"secure": "Auto",
-			"drain_duration": 100,
-			"zero_downtime_failover": "sticky"
-		},
-		"session_affinity_ttl": 5000,
-		"random_steering": {
-			"pool_weights": {
-				"de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-			},
-			"default_weight": 0.2
-		}
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "699d98642c564d2e855e9661899b7252",
+    "created_on": "2021-01-01T05:20:00.12345Z",
+    "modified_on": "2021-01-01T05:20:00.12345Z",
+    "description": "Load Balancer for lb.example.com",
+    "name": "lb.example.com",
+    "enabled": true,
+    "ttl": 30,
+    "fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
+    "default_pools": [
+      "17b5962d775c646f3f9725cbc7a53df4",
+      "9290f38c5d07c2e2f4df57b1f61d4196",
+      "00920f38ce07c2e2f4df50b1f61d4194"
+    ],
+    "proxied": true,
+    "steering_policy": "random_steering",
+    "session_affinity": "cookie",
+    "session_affinity_attributes": {
+      "samesite": "Auto",
+      "secure": "Auto",
+      "drain_duration": 100,
+      "zero_downtime_failover": "sticky"
+    },
+    "session_affinity_ttl": 5000,
+    "random_steering": {
+      "pool_weights": {
+        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+      },
+      "default_weight": 0.2
+    }
+  }
 }
 ```
diff --git a/src/content/partials/load-balancing/load-balancer-create.mdx b/src/content/partials/load-balancing/load-balancer-create.mdx
index d0b76484eaea2e6..0eddd6c4f2e92bb 100644
--- a/src/content/partials/load-balancing/load-balancer-create.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create a Public or a Private load balancer in the dashboard:
@@ -8,31 +9,31 @@ To create a Public or a Private load balancer in the dashboard:
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Public load balancer**
+2. On the **Load Balancer Setup**, select **Public load balancer** 
 
-3. Choose the website to which you want to add this load balancer.
+3. Choose the website to which you want to add this load balancer. 
 
 4. On the **Hostname** page:
-   - Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
-   - From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
-   - Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
-   - Add a description for your load balancer.
-   - If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
-   - If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
+   * Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
+   * From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
+   * Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
+   * Add a description for your load balancer. 
+   * If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
+   * If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
 
 5. Select **Next**.
 
 6. On the **Add a Pool** page:
-   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 7. Select **Next**.
 
 8. On the **Monitors** page:
-   - Review the monitors attached to your pools.
-   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   * Review the monitors attached to your pools.
+   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 9. Select **Next**.
 
@@ -43,28 +44,28 @@ To create a Public or a Private load balancer in the dashboard:
 12. Select **Next**.
 
 13. On the **Review** page:
-    - Review your configuration and make any changes.
-    - Choose whether to **Save as Draft** or **Save and Deploy**.
+    * Review your configuration and make any changes.
+    * Choose whether to **Save as Draft** or **Save and Deploy**.
 
-### Create a Private load balancer
+### Create a Private load balancer 
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Private load balancer**
+2. On the **Load Balancer Setup**, select **Private load balancer** 
 
 3. Associate your load balancer with either a Cloudflare private IP or a specified IP address and create a description for your load balancer.
 
 4. On the **Add a Pool** page:
-   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 5. Select **Next**.
 
 6. On the **Monitors** page:
-   - Review the monitors attached to your pools.
-   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   * Review the monitors attached to your pools.
+   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 7. Select **Next**.
 
@@ -73,5 +74,5 @@ To create a Public or a Private load balancer in the dashboard:
 9. Select **Next**.
 
 10. On the **Review** page:
-    - Review your configuration and make any changes.
-    - Choose whether to **Save as Draft** or **Save and Deploy**.
+    * Review your configuration and make any changes.
+    * Choose whether to **Save as Draft** or **Save and Deploy**.
diff --git a/src/content/partials/load-balancing/load-balancer-definition.mdx b/src/content/partials/load-balancing/load-balancer-definition.mdx
index e955489d0848da8..7c7f1e2775cb3b6 100644
--- a/src/content/partials/load-balancing/load-balancer-definition.mdx
+++ b/src/content/partials/load-balancing/load-balancer-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.) or IP address.
diff --git a/src/content/partials/load-balancing/load-balancing-diagram.mdx b/src/content/partials/load-balancing/load-balancing-diagram.mdx
index bc43dd9c4d9b564..8f66f37a89cdc36 100644
--- a/src/content/partials/load-balancing/load-balancing-diagram.mdx
+++ b/src/content/partials/load-balancing/load-balancing-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/monitor-create-api.mdx b/src/content/partials/load-balancing/monitor-create-api.mdx
index cc778566aa44003..d1d69939d9bd159 100644
--- a/src/content/partials/load-balancing/monitor-create-api.mdx
+++ b/src/content/partials/load-balancing/monitor-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -7,61 +8,65 @@ import { APIRequest } from "~/components";
 For a full list of monitor properties, refer to [Create Monitor](/api/resources/load_balancers/subresources/monitors/methods/create/). If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
 <APIRequest
-	path="/accounts/{account_id}/load_balancers/monitors"
-	method="POST"
-	json={{
-		type: "https",
-		description: "Login page monitor",
-		method: "GET",
-		path: "/health",
-		header: {
-			Host: ["example.com"],
-			"X-App-ID": ["abc123"],
-		},
-		port: 8080,
-		timeout: 3,
-		retries: 0,
-		interval: 90,
-		expected_body: "alive",
-		expected_codes: "2xx",
-		follow_redirects: true,
-		allow_insecure: true,
-		consecutive_up: 3,
-		consecutive_down: 2,
-		probe_zone: "example.com",
-	}}
+  path="/accounts/{account_id}/load_balancers/monitors"
+  method="POST"
+  json={{
+    type: "https",
+    description: "Login page monitor",
+    method: "GET",
+    path: "/health",
+    header: {
+      Host: ["example.com"],
+      "X-App-ID": ["abc123"]
+    },
+    port: 8080,
+    timeout: 3,
+    retries: 0,
+    interval: 90,
+    expected_body: "alive",
+    expected_codes: "2xx",
+    follow_redirects: true,
+    allow_insecure: true,
+    consecutive_up: 3,
+    consecutive_down: 2,
+    probe_zone: "example.com"
+  }}
 />
 
 The response contains the complete definition of the new monitor.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": ":monitor-id",
-		"created_on": "2021-01-01T05:20:00.12345Z",
-		"modified_on": "2021-01-01T05:20:00.12345Z",
-		"type": "https",
-		"description": "Login page monitor",
-		"method": "GET",
-		"path": "/health",
-		"header": {
-			"Host": ["example.com"],
-			"X-App-ID": ["abc123"]
-		},
-		"port": 8080,
-		"timeout": 3,
-		"retries": 0,
-		"interval": 90,
-		"expected_body": "alive",
-		"expected_codes": "2xx",
-		"follow_redirects": true,
-		"allow_insecure": true,
-		"consecutive_up": 3,
-		"consecutive_down": 2,
-		"probe_zone": "example.com"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": ":monitor-id",
+    "created_on": "2021-01-01T05:20:00.12345Z",
+    "modified_on": "2021-01-01T05:20:00.12345Z",
+    "type": "https",
+    "description": "Login page monitor",
+    "method": "GET",
+    "path": "/health",
+    "header": {
+      "Host": [
+        "example.com"
+      ],
+      "X-App-ID": [
+        "abc123"
+      ]
+    },
+    "port": 8080,
+    "timeout": 3,
+    "retries": 0,
+    "interval": 90,
+    "expected_body": "alive",
+    "expected_codes": "2xx",
+    "follow_redirects": true,
+    "allow_insecure": true,
+    "consecutive_up": 3,
+    "consecutive_down": 2,
+    "probe_zone": "example.com"
+  }
 }
 ```
diff --git a/src/content/partials/load-balancing/monitor-create.mdx b/src/content/partials/load-balancing/monitor-create.mdx
index cba41c6a75cd948..e886aac579f8934 100644
--- a/src/content/partials/load-balancing/monitor-create.mdx
+++ b/src/content/partials/load-balancing/monitor-create.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can create a monitor within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Monitors** tab:
 
diff --git a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
index 000c0980eda9bc6..203ada096f2b360 100644
--- a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
+++ b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **All Data Centers (Enterprise only)**
@@ -16,8 +17,10 @@ Three health monitor probes are sent from each specified region within the pool
 
 :::caution
 
+
 Because of how Cloudflare checks health from [multiple regions](#health-monitor-regions), adding multiple regions — or choosing to check health from **All Data Centers** — can send a lot of traffic to your endpoint.
 
 The same problem can occur when setting low values for a monitor's **Interval**.
 
-:::
+
+:::
\ No newline at end of file
diff --git a/src/content/partials/load-balancing/monitor-prepare-server.mdx b/src/content/partials/load-balancing/monitor-prepare-server.mdx
index 40b7618385d0835..cac096756d634a6 100644
--- a/src/content/partials/load-balancing/monitor-prepare-server.mdx
+++ b/src/content/partials/load-balancing/monitor-prepare-server.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with [Cloudflare IP addresses](https://www.cloudflare.com/ips).
@@ -8,6 +9,8 @@ Each health monitor has the HTTP user-agent of `"Mozilla/5.0 (compatible; Cloudf
 
 :::caution
 
+
 If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our [Monitor troubleshooting guide](/load-balancing/troubleshooting/load-balancing-faq/#why-is-my-endpoint-or-pool-considered-unhealthy).
 
+
 :::
diff --git a/src/content/partials/load-balancing/monitor-settings-basic.mdx b/src/content/partials/load-balancing/monitor-settings-basic.mdx
index 48d2f9414f6707b..61c55dcb0698619 100644
--- a/src/content/partials/load-balancing/monitor-settings-basic.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-basic.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- **Type**: The protocol to use for health monitors
-  - _Non-enterprise customers_: Choose **HTTP**, **HTTPS**, or **TCP**.
-  - _Enterprise customers_: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
-- **Path**: The endpoint path to run health monitor requests against
-- **Port**: The destination port for health monitors
+* **Type**: The protocol to use for health monitors
+  * *Non-enterprise customers*: Choose **HTTP**, **HTTPS**, or **TCP**.
+  * *Enterprise customers*: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
+* **Path**: The endpoint path to run health monitor requests against
+* **Port**: The destination port for health monitors
diff --git a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
index d6ca1888d5c5948..5ea1696866dbf6b 100644
--- a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 :::note[Note]
 
+
 To increase confidence in pool status, you can also increase the `consecutive_up` and `consecutive_down` fields when [creating a monitor with the API](/api/resources/load_balancers/subresources/monitors/methods/create/).
 
 To become healthy or unhealthy, monitored endpoints must pass this health monitor request the consecutive number of times specified in these parameters.
 
+
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-definition.mdx b/src/content/partials/load-balancing/origin-steering-definition.mdx
index 41f06c64c7d903e..ff95cda09a041f0 100644
--- a/src/content/partials/load-balancing/origin-steering-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-definition.mdx
@@ -1,16 +1,19 @@
 ---
 {}
+
 ---
 
 Endpoint steering customizes how each [pool](/load-balancing/pools/) distributes requests to its associated endpoints.
 
 These distributions are a combination of two properties:
 
-- The endpoint steering [policy](#policies) chosen for your pool.
-- The [weights](#weights) assigned to each endpoint.
+* The endpoint steering [policy](#policies) chosen for your pool.
+* The [weights](#weights) assigned to each endpoint.
 
 :::note
 
+
 If an endpoint [becomes unhealthy](/load-balancing/understand-basics/health-details/), your pool will also re-balance traffic according to its endpoint steering policy.
 
+
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-policies.mdx b/src/content/partials/load-balancing/origin-steering-policies.mdx
index 3588f6aa482ccc6..f1231eacca1c19e 100644
--- a/src/content/partials/load-balancing/origin-steering-policies.mdx
+++ b/src/content/partials/load-balancing/origin-steering-policies.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you [create a pool](/load-balancing/pools/create-pool/), you have to choose an option for **Endpoint Steering**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
index 04b243f9c170afd..02f56f65d616a1b 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The weight assigned to an endpoint controls the percentage of pool traffic sent to that endpoint. By default, all endpoints within a pool have a weight of **1**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
index 55e5f89bf7d1d0a..003b326d282ef75 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you choose **Hash** for your **Endpoint Steering** or enable [session affinity](/load-balancing/understand-basics/session-affinity/), these options can affect traffic distribution.
diff --git a/src/content/partials/load-balancing/pool-create.mdx b/src/content/partials/load-balancing/pool-create.mdx
index 198bbcd758d3fd7..c6b72f1a6076a14 100644
--- a/src/content/partials/load-balancing/pool-create.mdx
+++ b/src/content/partials/load-balancing/pool-create.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can create a pool within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Pools** tab:
 
@@ -11,22 +12,24 @@ You can create a pool within the [load balancer workflow](/load-balancing/load-b
 2. Select the **Pools** tab and then **Create pool**.
 
 3. For your pool, enter the following information:
-   - A name (must be unique)
-   - A description to provide more detail on the name
-   - A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
+   * A name (must be unique)
+   * A description to provide more detail on the name
+   * A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
 
 4. For each endpoint, enter the following information:
-   - A name (must be unique)
-   - The endpoint address or associated hostname
-   - (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
-   - A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
-   - (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
-   - (Optional) The destination port to which the traffic will be served.
+   * A name (must be unique)
+   * The endpoint address or associated hostname
+   * (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
+   * A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
+   * (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
+   * (Optional) The destination port to which the traffic will be served.
 
 :::note[Note]
 
+
 If your endpoint is a website or application hosted on [Cloudflare Pages](/pages/), you will need to fill in the host header field with the project domain for it to resolve correctly.
 
+
 :::
 
 5. Repeat this process for additional endpoints in the pool.
@@ -34,9 +37,9 @@ If your endpoint is a website or application hosted on [Cloudflare Pages](/pages
 6. (Optional) Set up coordinates for [Proximity Steering](/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering/) on the pool.
 
 7. On the pool, update the following information:
-   - **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
-   - **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
-   - **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
-   - **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
+   * **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
+   * **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
+   * **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
+   * **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
 
 8. When finished, select **Save**.
diff --git a/src/content/partials/load-balancing/pool-health-threshold.mdx b/src/content/partials/load-balancing/pool-health-threshold.mdx
index ef2bac2c25ed613..825e481e8f68a55 100644
--- a/src/content/partials/load-balancing/pool-health-threshold.mdx
+++ b/src/content/partials/load-balancing/pool-health-threshold.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered _Healthy_ and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
+The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered *Healthy* and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
diff --git a/src/content/partials/load-balancing/region-mapping.mdx b/src/content/partials/load-balancing/region-mapping.mdx
index 1bd65acff2b56cc..128fad39ca78170 100644
--- a/src/content/partials/load-balancing/region-mapping.mdx
+++ b/src/content/partials/load-balancing/region-mapping.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | Region code | Region name            |
diff --git a/src/content/partials/load-balancing/route-production-traffic.mdx b/src/content/partials/load-balancing/route-production-traffic.mdx
index 5da9c7169712872..3e1b688df82eeb7 100644
--- a/src/content/partials/load-balancing/route-production-traffic.mdx
+++ b/src/content/partials/load-balancing/route-production-traffic.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Now that you have set up your load balancer and verified everything is working correctly, you can put the load balancer on a live domain or subdomain:
@@ -7,11 +8,13 @@ Now that you have set up your load balancer and verified everything is working c
 1. If you update your pools and monitors, review the pool health again to make sure everything is working as expected.
 2. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 3. Configure your load balancer to receive production traffic, which could involve either:
-   - Editing the **Hostname** of your existing load balancer.
-   - Updating the `CNAME` record sending traffic to your load balancer.
+   * Editing the **Hostname** of your existing load balancer.
+   * Updating the `CNAME` record sending traffic to your load balancer.
 
 :::note
 
+
 If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [origin rule](/rules/origin-rules/features/#dns-record).
 
+
 :::
diff --git a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
index 8c0d3b883dc0ee3..b6398dd605663ec 100644
--- a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
+++ b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Session affinity automatically directs requests from the same client to the same endpoint:
@@ -24,8 +25,8 @@ Session affinity automatically directs requests from the same client to the same
      end
 ```
 
-<br />
+<br/>
 
-All cookie-based sessions default to 23 hours unless you set a custom session _Time to live_ (TTL).
+All cookie-based sessions default to 23 hours unless you set a custom session *Time to live* (TTL).
 
 The session cookie is secure when [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) is enabled. Additionally, HttpOnly is always enabled for the cookie to prevent cross-site scripting attacks.
diff --git a/src/content/partials/load-balancing/session-affinity-definition.mdx b/src/content/partials/load-balancing/session-affinity-definition.mdx
index 5b2531052f2e4ae..457703c7c032ae8 100644
--- a/src/content/partials/load-balancing/session-affinity-definition.mdx
+++ b/src/content/partials/load-balancing/session-affinity-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you enable session affinity, your load balancer directs all requests from a particular end user to a specific endpoint. This continuity preserves information about the user session — such as items in their shopping cart — that might otherwise be lost if requests were spread out among multiple servers.
diff --git a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
index 4daefe6d4a289dd..dfe52808eb3b9c0 100644
--- a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
+++ b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
+* Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
 
-- UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
+* UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
diff --git a/src/content/partials/load-balancing/test-domain-setup.mdx b/src/content/partials/load-balancing/test-domain-setup.mdx
index 88b53616839ade6..8a7c754c580a135 100644
--- a/src/content/partials/load-balancing/test-domain-setup.mdx
+++ b/src/content/partials/load-balancing/test-domain-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Instead of starting on your production domain, you likely should create a load balancer on a test or staging domain. This may involve temporary changes to your monitors and pools, depending on your infrastructure setup.
diff --git a/src/content/partials/load-balancing/traffic-steering-definition.mdx b/src/content/partials/load-balancing/traffic-steering-definition.mdx
index 84b6a196eba9451..471d03f63fbe154 100644
--- a/src/content/partials/load-balancing/traffic-steering-definition.mdx
+++ b/src/content/partials/load-balancing/traffic-steering-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Global traffic steering policies decide how a load balancer routes traffic to attached and healthy pools.
diff --git a/src/content/partials/load-balancing/unexpected-health-statuses.mdx b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
index 9bd3a6cad5b730a..cc03b813fa18383 100644
--- a/src/content/partials/load-balancing/unexpected-health-statuses.mdx
+++ b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 If you notice that healthy pools are being marked unhealthy:
 
-- Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
-- Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
+* Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
+* Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
diff --git a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
index d0ec34fe725e179..8e1a71d8ff5616f 100644
--- a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
+++ b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
@@ -1,11 +1,13 @@
 ---
 {}
+
 ---
 
 When a pool reaches **Critical** health, your load balancer will begin diverting traffic according to its [Traffic steering policy](/load-balancing/understand-basics/traffic-steering/steering-policies/):
 
-- **Off**:
-  - If the active pool becomes unhealthy, traffic goes to the next pool in order.
-  - If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
+* **Off**:
+
+  * If the active pool becomes unhealthy, traffic goes to the next pool in order.
+  * If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
 
-- **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
+* **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
diff --git a/src/content/partials/logs/check-log-retention.mdx b/src/content/partials/logs/check-log-retention.mdx
index 13b4c54b32aacc3..6a5b9c2e8254154 100644
--- a/src/content/partials/logs/check-log-retention.mdx
+++ b/src/content/partials/logs/check-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/disable-log-retention.mdx b/src/content/partials/logs/disable-log-retention.mdx
index f13215928cc87a1..3a89db7ac7c39e0 100644
--- a/src/content/partials/logs/disable-log-retention.mdx
+++ b/src/content/partials/logs/disable-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-log-retention.mdx b/src/content/partials/logs/enable-log-retention.mdx
index 46ea7dc9617f844..7d9a9ac4a7a3e7c 100644
--- a/src/content/partials/logs/enable-log-retention.mdx
+++ b/src/content/partials/logs/enable-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-logpush-job.mdx b/src/content/partials/logs/enable-logpush-job.mdx
index f571da2cfbdba5a..9c86c3c83faa49b 100644
--- a/src/content/partials/logs/enable-logpush-job.mdx
+++ b/src/content/partials/logs/enable-logpush-job.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
-
+ 
    For account: <DashButton url="/?to=/:account/logs" />
-
+ 
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
diff --git a/src/content/partials/logs/enable-read-permissions.mdx b/src/content/partials/logs/enable-read-permissions.mdx
index 0782c628cb0ea41..b2b55619a3f5903 100644
--- a/src/content/partials/logs/enable-read-permissions.mdx
+++ b/src/content/partials/logs/enable-read-permissions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Ensure **Log Share** permissions are enabled, before attempting to read or configure a Logpush job. For more information refer to the [Roles section](/logs/logpush/permissions/#roles).
diff --git a/src/content/partials/logs/filtering-limitations.mdx b/src/content/partials/logs/filtering-limitations.mdx
index 1f28334e5fc8c7b..2d32cc7f88aa921 100644
--- a/src/content/partials/logs/filtering-limitations.mdx
+++ b/src/content/partials/logs/filtering-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/networking-services/account-id-api-key.mdx b/src/content/partials/networking-services/account-id-api-key.mdx
index ae09eb187dd2510..c2532c7e6b0a36c 100644
--- a/src/content/partials/networking-services/account-id-api-key.mdx
+++ b/src/content/partials/networking-services/account-id-api-key.mdx
@@ -1,18 +1,16 @@
 ---
 {}
+
 ---
 
 import { Markdown } from "~/components";
 
-{/\*
-Conditional rendering based on showSiteId prop:
-
-- When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
-- When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
+{/* 
+  Conditional rendering based on showSiteId prop:
+  - When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
+  - When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
   The ternaries only render the differing prefix and suffix to avoid content duplication.
-  \*/}
-  :::note
-  <Markdown
-  	text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`}
-  />
-  :::
+*/}
+:::note
+<Markdown text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`} />
+:::
diff --git a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
index e7f64d2d3b9bca3..665ea039cad5541 100644
--- a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
+++ b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
@@ -9,4 +9,4 @@ When you set up an alert for your site, you will be notified when there is an is
 To set up health alerts:
 
 1. Configure <a href={props.magicTunnelHcsURL}>Tunnel health alerts</a> across all of the tunnels associated with each {props.productName} site.
-2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
+2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/analytics/site-analytics.mdx b/src/content/partials/networking-services/analytics/site-analytics.mdx
index 03a99eb68bf605b..5f9269dba906210 100644
--- a/src/content/partials/networking-services/analytics/site-analytics.mdx
+++ b/src/content/partials/networking-services/analytics/site-analytics.mdx
@@ -7,45 +7,51 @@ params:
   - setGeoCoordinatesURL
 ---
 
-import { Details, Markdown, DashButton } from "~/components";
+
+
+import { Details, Markdown, DashButton } from "~/components"
 
 After adding your sites, the {props.networkOverviewPageName} section of the dashboard provides a summary of the connectivity status and traffic analytics for all your sites. This is a great place to start if you receive a Cloudflare WAN alert, need to begin the troubleshooting process, or are performing routine monitoring. <Markdown text={props.instructions} />
 
 {props.networkOverviewPageName} has the following data types available:
 
 <Details header="Geographic map summary">
-	- [Aggregate Cloudflare WAN site health](#site-health) - [Cloudflare WAN
-	availability status for sites](#no-status-available) - [Cloudflare WAN site
-	geographic location](#no-location-set)
+	- [Aggregate Cloudflare WAN site health](#site-health)
+	- [Cloudflare WAN availability status for sites](#no-status-available)
+	- [Cloudflare WAN site geographic location](#no-location-set)
 </Details>
 
 <Details header="Cloudflare WAN site data table">
-	- Site Name - Site Health - Site Tunnel Names - Site Tunnel Statuses - Site
-	Traffic Sent - Site Traffic Received
+	- Site Name
+	- Site Health
+	- Site Tunnel Names
+	- Site Tunnel Statuses
+	- Site Traffic Sent
+	- Site Traffic Received
 </Details>
 
 <Details header="Cloudflare WAN site data">
-	- Traffic Sent by Tunnel - Traffic Received by Tunnel
+	- Traffic Sent by Tunnel
+	- Traffic Received by Tunnel
 </Details>
 
 To start using network overview:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **${props.networkOverviewPageName}**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    <DashButton url="/?to=/:account/networking-insights/health" />
-    </>
+	<>
 
+	<DashButton url="/?to=/:account/networking-insights/health" />
+	</>
 )
 }
 
@@ -77,6 +83,7 @@ The status of a site refers to its health. If your sites show a **No status avai
 
 The dashboard displays the number of sites with no location set, meaning sites for which you did not set up a geographic location. To add a location to a site, find the site you want to add location to, and select **no location set** to edit its location settings. Refer to <a href={props.setGeoCoordinatesURL}>Set geographic coordinates</a> for more information.
 
+
 ### Traffic overview
 
 Traffic overview aggregates all Cloudflare WAN sites configured in your account. Here, you can check summary information about each site like:
@@ -84,4 +91,4 @@ Traffic overview aggregates all Cloudflare WAN sites configured in your account.
 - Site status
 - Traffic sent and received
 
-Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
+Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
index 9388b0a604a3311..fb6b8b613c66bea 100644
--- a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
+++ b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
@@ -30,7 +30,7 @@ The following table provides a high-level comparison of all connectivity options
 | [Cloudflare Tunnel](#cloudflare-tunnel) | HTTP/2, QUIC | Off-ramp only | Software daemon (`cloudflared`) on server | Exposing private applications without a public IP |
 | [Cloudflare One Client](#cloudflare-one-client) | MASQUE (default), WireGuard | Bidirectional | Client software on end-user devices | Securing remote workforce devices |
 | [Cloudflare Mesh](#cloudflare-mesh) | MASQUE | Bidirectional | Software client on Linux host | Connecting sites with IoT or VoIP devices |
-| [DNS locations](#dns-locations) | DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration | Filtering DNS traffic without device agents |
+| [DNS locations](#dns-locations) |  DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration  | Filtering DNS traffic without device agents |
 | [Proxy endpoints](#proxy-endpoints) | HTTP/HTTPS | On-ramp only | Browser PAC file configuration | Filtering web traffic without device agents |
 | [Clientless Web Isolation](#clientless-web-isolation) | HTTP/HTTPS | On-ramp only | Prefixed URL with Access authentication | Secure web access for unmanaged devices |
 | [GRE tunnels](#gre-tunnels) | GRE | Bidirectional | Network tunnel from router or firewall | Connecting sites with existing network hardware |
@@ -97,9 +97,9 @@ DNS locations allow you to filter DNS traffic from networks without deploying th
 
 DNS locations support multiple endpoint types:
 
-- **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
-- **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
-- **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
+* **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
+* **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
+* **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
 
 Use DNS locations when you need to filter DNS traffic for an entire office or network, per device without installing agents on devices, or integrate with existing network infrastructure.
 
@@ -119,8 +119,8 @@ Proxy endpoints allow you to apply Cloudflare Gateway HTTP policies without inst
 
 Cloudflare One supports two types of proxy endpoints:
 
-- **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
-- **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
+* **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
+* **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
 
 Use proxy endpoints when you need to filter web traffic without device agents, integrate with existing proxy infrastructure, or deploy Gateway alongside other security tools.
 
@@ -283,7 +283,7 @@ The connectivity options on this page connect your private infrastructure, sites
 
 - **Non-HTTP traffic** (TCP/UDP protocols such as gaming, email, or custom services) — refer to [Spectrum](/spectrum/).
 - **Network-level DDoS protection** (for on-premises, cloud-hosted, and hybrid networks) — refer to [Magic Transit](/magic-transit/).
-  :::
+:::
 
 ### Cloudflare One recommendations by team
 
@@ -301,14 +301,14 @@ The team driving your Cloudflare One connectivity project influences which optio
 
 Cloudflare Mesh and Cloudflare One Appliance both provide site-level connectivity, but serve different deployment scenarios.
 
-| Aspect                | Cloudflare Mesh                                                                                                         | Cloudflare One Appliance                                                           |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
-| **Protocol**          | MASQUE                                                                                                                  | IPsec                                                                              |
-| **Deployment model**  | Software on Linux host (can run alongside other workloads)                                                              | Dedicated hardware appliance or virtual machine                                    |
-| **Best for**          | Cloud VPCs, development environments, smaller deployments with an available Linux host                                  | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
-| **Platform support**  | Linux only (x86_64, ARM64). Currently in beta.                                                                          | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox)                |
-| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site                                     |
-| **Management**        | Configured as a device in the Cloudflare One Client settings                                                            | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning      |
+| Aspect | Cloudflare Mesh | Cloudflare One Appliance |
+| ---- | ---- | ---- |
+| **Protocol** | MASQUE | IPsec |
+| **Deployment model** | Software on Linux host (can run alongside other workloads) | Dedicated hardware appliance or virtual machine |
+| **Best for** | Cloud VPCs, development environments, smaller deployments with an available Linux host | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
+| **Platform support** | Linux only (x86_64, ARM64). Currently in beta. | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox) |
+| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site |
+| **Management** | Configured as a device in the Cloudflare One Client settings | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning |
 
 Use Cloudflare Mesh when you need lightweight, software-only connectivity for cloud workloads or sites where a Linux host is available. Use Cloudflare One Appliance when you need enterprise-grade throughput, high availability, or integration with existing network infrastructure.
 
@@ -457,8 +457,7 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)
 - [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)
 - [Cloudflare WAN](/cloudflare-wan/)
-- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of
-  supported on-ramps
+- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of supported on-ramps
 - [Multi-Cloud Networking](/multi-cloud-networking/) - Automate cloud VPC connectivity
 - [Magic Transit](/magic-transit/)
 - <a href={props.connectorURL}>Cloudflare One Appliance</a>
@@ -468,4 +467,4 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) - Filter web traffic using PAC files
 - [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) - Secure web access without device agents
 
-For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/).
+For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/). 
diff --git a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
index d436a168d8d8c4c..18c9671ea9ce7f4 100644
--- a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
@@ -15,11 +15,10 @@ VeloCloud has a high availability mechanism that allows customers to specify one
 Cloudflare WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for `<account_id>`, `<tunnel_id>`, and the FQDN wildcard before running the API call.
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
-	method="PATCH"
-	json={{
-		custom_remote_identities: {
-			fqdn_id: "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com",
-		},
-	}}
+  url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
+  method="PATCH"
+  json={{
+    "custom_remote_identities":
+			{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
+  }}
 />
diff --git a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
index ae7c5d5a52b3fa7..c7cfca556c7a735 100644
--- a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
@@ -64,17 +64,11 @@ The list of prerequisites below is only for customers planning to connect manual
 
 ##### GRE tunnels as off-ramp
 
-<Render
-	file="cloudflare-wan/mtu-mss/mss-clamping-gre"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/mtu-mss/mss-clamping-gre" product="networking-services" />
 
 ##### IPsec tunnels
 
-<Render
-	file="cloudflare-wan/mtu-mss/mss-clamping-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/mtu-mss/mss-clamping-ipsec" product="networking-services"/>
 
 :::caution[Important]
 Refer to your device documentation to check if it sets IPsec MSS clamping automatically. If that is not the case and you are using IPsec inside GRE, you have to set MSS clamp manually.
@@ -87,4 +81,4 @@ Refer to <a href={props.mtuReferenceURL}>Maximum transmission unit and maximum s
 <Render
 	file="prerequisites/router-vendor-guidelines-mss-settings-origin"
 	product="networking-services"
-/>
+/>
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
index 027327c70df8bf4..fc3cadd24324184 100644
--- a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
@@ -6,4 +6,4 @@ If your network has multiple paths to the same destination — for example, redu
 
 Cloudflare WAN (formerly Magic WAN) uses Private Network Load Balancing, which balances traffic across your private network endpoints. It supports both on-ramping (traffic entering Cloudflare's network) and off-ramping (traffic exiting to your sites).
 
-Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
+Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
index 031870b0e53efd0..361286f6db723bf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
@@ -24,41 +24,41 @@ params:
   - oracleUrl
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) is compatible with any device that supports <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> with the <a href={props.supportedConfigurationParametersUrl}>supported configuration parameters</a> or supports <GlossaryTooltip term="GRE tunnel">GRE</GlossaryTooltip>.
 
 The matrix below includes example devices and links to the integration guides.
 
-| Appliance                                                                   | GRE tunnel                    | IPsec tunnel                  |
-| --------------------------------------------------------------------------- | ----------------------------- | ----------------------------- |
-| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a>                   | ✅                            | ✅                            |
-| Cisco ASA                                                                   | Compatibility on roadmap      | Specifications compatible[^1] |
-| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a>                              | ✅                            | ✅                            |
-| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a>   | -                             | ✅                            |
-| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>                              | ✅                            | ✅                            |
-| <a href={props.fortinetUrl}>Fortinet</a>                                    | Specifications compatible[^1] | ✅                            |
-| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a>                  | -                             | ✅                            |
-| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a>  | Specifications compatible[^1] | ✅                            |
-| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅                            |
-| <a href={props.pfsenseUrl}>pfSense</a>                                      | ✅                            | ✅                            |
-| Prisma SD-WAN (Palo Alto)                                                   | Specifications compatible[^1] | Specifications compatible[^1] |
-| Riverbed                                                                    | Specifications compatible[^1] | Specifications compatible[^1] |
-| <a href={props.sonicwallUrl}>SonicWall</a>                                  | -                             | ✅                            |
-| <a href={props.sophosFirewallUrl}>Sophos Firewall</a>                       | ✅                            | ✅                            |
-| <a href={props.strongswanUrl}>strongSwan</a>                                | -                             | ✅                            |
-| <a href={props.ubiquitiUrl}>Ubiquiti</a>                                    | -                             | ✅                            |
-| <a href={props.velocloudUrl}>Velocloud</a>                                  | -                             | ✅                            |
-| Versa                                                                       | Specifications compatible[^1] | Compatibility on roadmap      |
-| <a href={props.vyosUrl}>VyOS</a>                                            | ✅                            | ✅                            |
-| <a href={props.yamahaUrl}>Yamaha RTX Router</a>                             | -                             | ✅                            |
+| Appliance | GRE tunnel | IPsec tunnel |
+| --- | --- | --- |
+| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a> |✅ | ✅ |
+| Cisco ASA | Compatibility on roadmap | Specifications compatible[^1] |
+| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a> | ✅ | ✅ |
+| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a> | - | ✅ |
+| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>  | ✅ | ✅ |
+| <a href={props.fortinetUrl}>Fortinet</a>| Specifications compatible[^1] | ✅ |
+| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a> | - | ✅ |
+| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a> | Specifications compatible[^1] | ✅ |
+| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅ |
+| <a href={props.pfsenseUrl}>pfSense</a>| ✅ | ✅ |
+| Prisma SD-WAN (Palo Alto) | Specifications compatible[^1] | Specifications compatible[^1] |
+| Riverbed  | Specifications compatible[^1] | Specifications compatible[^1] |
+| <a href={props.sonicwallUrl}>SonicWall</a>| - | ✅ |
+| <a href={props.sophosFirewallUrl}>Sophos Firewall</a> | ✅ | ✅ |
+| <a href={props.strongswanUrl}>strongSwan</a> | - | ✅ |
+| <a href={props.ubiquitiUrl}>Ubiquiti</a> | - | ✅ |
+| <a href={props.velocloudUrl}>Velocloud</a> | - | ✅ |
+| Versa  | Specifications compatible[^1] | Compatibility on roadmap |
+| <a href={props.vyosUrl}>VyOS</a>| ✅ | ✅ |
+| <a href={props.yamahaUrl}>Yamaha RTX Router</a> | - | ✅ |
 
-| VPN                                                           | GRE tunnel | IPsec tunnel |
-| ------------------------------------------------------------- | ---------- | ------------ |
-| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | -          | ✅           |
-| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>         | -          | ✅           |
-| <a href={props.azureUrl}>Azure VPN Gateway</a>                | -          | ✅           |
-| <a href={props.googleUrl}>GCP Cloud VPN</a>                   | -          | ✅           |
-| <a href={props.oracleUrl}>Oracle Cloud</a>                    | -          | ✅           |
+| VPN | GRE tunnel | IPsec tunnel |
+| --- | --- | --- |
+| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | - | ✅ |
+| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>          | - | ✅ |
+| <a href={props.azureUrl}>Azure VPN Gateway</a>                 | - | ✅ |
+| <a href={props.googleUrl}>GCP Cloud VPN</a>                    | - | ✅ |
+| <a href={props.oracleUrl}>Oracle Cloud</a> 										| - | ✅ |
 
 [^1]: Specifications compatible per vendor documentation
diff --git a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
index 2b8dae020681cee..2c7ce55ec60f37e 100644
--- a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
@@ -7,4 +7,4 @@ Once your traffic flows through Cloudflare's network, you can apply security pol
 
 **[Cloudflare Network Firewall](/cloudflare-network-firewall/)** filters traffic at layers 3 and 4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/) — the network and transport layers. You can allow or block traffic based on packet characteristics such as source and destination IP addresses, ports, protocols, and packet length. All Cloudflare WAN customers have <a href="/cloudflare-network-firewall/plans/">automatic access to Cloudflare Network Firewall</a>.
 
-**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
+**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
index d4b5c75a6d6e558..51ffc512d5a6a49 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
@@ -37,7 +37,7 @@ Additionally, you also need to configure the necessary route table entries for t
 
 5. Take note of the **IP address** you chose, as this corresponds to the customer endpoint IP that you will need to configure on the Cloudflare side of the IPsec tunnel.
 
-6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**. You will need it to create the IPsec tunnel on Cloudflare's side.
+6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**.  You will need it to create the IPsec tunnel on Cloudflare's side.
 
 7. In **Inside IPv4 CIDR**, AWS enforces that only a `/30` block within the `169.254.0.0/16` range can be used. To accommodate this, Cloudflare supports a subset of this IP block. Namely, Cloudflare supports `169.254.240.0/20` to be assigned as the IPsec tunnel's (internal) interface IPs. This example will use `169.254.244.0/30` as the CIDR block for the IPsec tunnel: `169.254.244.1` for the AWS side of the tunnel, and `169.254.244.2` for the Cloudflare side of the tunnel.
 
@@ -84,7 +84,7 @@ After configuring the AWS transit gateway VPN connection and the tunnel as menti
 
 ### Static routes
 
-The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of `192.168.192.0/26`, you should use it as the prefix for your static route.
+The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of  `192.168.192.0/26`, you should use it as the prefix for your static route.
 
 To create a static route:
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
index 58bcc4e8130ad91..2683c003c5db069 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
@@ -36,7 +36,7 @@ Using traditional hub and spoke terminology, a Virtual WAN Hub deployed within a
 4. Select **Create**. Note that the deployment time for the vWAN Hub and VPN Gateway may take 30 minutes or more.
 5. After the VPN Gateway has finished provisioning, go to **Virtual WAN** > **Hubs** > **Your vHub** > **Connectivity** > **VPN (Site to site)**.
 6. In the **Essentials** dropdown select the VPN Gateway listed.
-7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
+7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and  `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
 
 ### 3. Create a VPN site
 
@@ -128,17 +128,17 @@ To create a **VPN Gateway Connection**:
 Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the <a href={props.cloudflareDocumentationUrl}>Cloudflare documentation</a>.
 
 1. **PSK**: Provide the PSK generated by Cloudflare for your IPsec tunnels.
-2. **Protocol**: _IKEv2_
-3. **IPsec**: _Custom_
+2. **Protocol**: *IKEv2*
+3. **IPsec**: *Custom*
    1. **IPsec SA lifetime in seconds**: 28800
    2. **IKE Phase 1**
-      1. **Encryption**: _AES256_
-      2. **Integrity/PRF**: _SHA256_
-      3. **DH Group**: _ECP384_
+      1. **Encryption**: *AES256*
+      2. **Integrity/PRF**: *SHA256*
+      3. **DH Group**: *ECP384*
    3. **IKE Phase 2(IPsec)**
-      1. **IPsec Encryption**: _AES256_
-      2. **IPsec Integrity**: _SHA256_
-      3. **PFS Group**: _ECP384_
+      1. **IPsec Encryption**: *AES256*
+      2. **IPsec Integrity**: *SHA256*
+      3. **PFS Group**: *ECP384*
    4. **Propagate Default Route:** **Disable**
    5. **Use policy based traffic selector**: **Disable**
    6. **Connection mode**: **Initiator Only**
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
index 07fb95463263fea..9a13c91be0214a0 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
@@ -201,6 +201,7 @@ Use the CLI to configure these settings:
 ip route 192.168.1.0 255.255.255.0 tunnel 2
 ```
 
+
 ## Connection test
 
 ### IPsec status
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
index 64e945e0798b80d..b19e899b9966bbf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
@@ -42,10 +42,12 @@ By default, the static routes are defined with the priority set to `100`. Cloudf
 
 1. Follow the <a href={props.configureStaticRoutesUrl}>Configure static routes</a> instructions to create a static route.
 2. For the first route, ensure the following settings are defined:
+
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).
 
 3. For the second route, ensure the following settings are defined:
+
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the second IPsec tunnel defined in the previous section.
    - **Tunnel/Next hop**: Select your second tunnel (Tunnel 02 of 02).
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
index c9dfa4d0c897b6d..74c35ae14467fa1 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ## Test Environment
 
-| **Field**   | **Value**              |
-| ----------- | ---------------------- |
-| Vendor      | HPE Juniper Networking |
-| Model       | SRX 320                |
-| Release     | JUNOS 23.4R2-S3.9      |
-| Date Tested | March 2026             |
+| **Field**                          | **Value**                                      |
+| ---------------------------------- | ---------------------------------------------- |
+| Vendor                             | HPE Juniper Networking                         |
+| Model                              | SRX 320                                        |
+| Release                            | JUNOS 23.4R2-S3.9                              |
+| Date Tested                        | March 2026                                     |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**       |
-| ---------------------------------- | --------------- |
-| Traffic Selection Criteria         | Route-Based VPN |
-| Routing                            | Static          |
-| Redundant Tunnels                  | Yes             |
-| Tunnel Load Balancing              | Active/Active   |
-| IKE Version                        | IKEv2           |
-| Authentication                     | Pre-Shared Key  |
-| Anti-Replay Protection             | Disabled        |
-| NAT Traversal (NAT-T)              | Not Tested      |
-| NAT-T Port                         | Not Applicable  |
-| Phase 1 - DH-Group                 | Group 20        |
-| Phase 1 - Encryption               | AES-256-CBC     |
-| Phase 1 - Authentication/Integrity | SHA-256         |
-| Phase 2 - DH-Group                 | Group 20        |
-| Phase 2 - Transport                | ESP             |
-| Phase 2 - Encryption               | AES-256-CBC     |
+| **Field**                          | **Value**                                      |
+| ---------------------------------- | ---------------------------------------------- |
+| Traffic Selection Criteria         | Route-Based VPN                                |
+| Routing                            | Static                                         |
+| Redundant Tunnels                  | Yes                                            |
+| Tunnel Load Balancing              | Active/Active                                  |
+| IKE Version                        | IKEv2                                          |
+| Authentication                     | Pre-Shared Key                                 |
+| Anti-Replay Protection             | Disabled                                       |
+| NAT Traversal (NAT-T)              | Not Tested                                     |
+| NAT-T Port                         | Not Applicable                                 |
+| Phase 1 - DH-Group                 | Group 20                                       |
+| Phase 1 - Encryption               | AES-256-CBC                                    |
+| Phase 1 - Authentication/Integrity | SHA-256                                        |
+| Phase 2 - DH-Group                 | Group 20                                       |
+| Phase 2 - Transport                | ESP                                            |
+| Phase 2 - Encryption               | AES-256-CBC                                    |
 
 ## Cloudflare WAN and HPE Juniper Networking SRX Series Firewalls - Configuration Settings
 
@@ -46,92 +46,92 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_01     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.0/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 162.159.135.1     |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_01                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 162.159.135.1                                  |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`      |
+| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_02     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.2/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 172.64.135.1      |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_02                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 172.64.135.1                                   |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`      |
+| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
 
 ## Customer Premise Equipment - HPE Juniper Networking
 
-| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| WAN Interface     | ge-0/0/0.0          | ge-0/0/0.0          |
-| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
-| Security Zone     | untrust             | untrust             |
+| **WAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| WAN Interface                       | ge-0/0/0.0            | ge-0/0/0.0            |
+| IP Address                          | 203.0.113.100/24      | 203.0.113.100/24      |
+| Security Zone                       | untrust               | untrust               |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ---------------------------------- | ------------------- | ------------------- |
-| Tunnel interface                   | st0.1               | st0.2               |
-| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
-| Security Zone                      | cloudflare          | cloudflare          |
+| **Virtual Tunnel Interface (VTI)**  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| Tunnel interface                    | st0.1                 | st0.2                 |
+| IP Address                          | 169.254.250.1/31      | 169.254.250.3/31      |
+| Security Zone                       | cloudflare            | cloudflare            |
 
-| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| LAN Interface     | ge-0/0/1.0          | ge-0/0/1.0          |
-| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
-| Security Zone     | trust               | trust               |
+| **LAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| LAN Interface                       | ge-0/0/1.0            | ge-0/0/1.0            |
+| IP Address                          | 192.168.125.1/24      | 192.168.125.1/24      |
+| Security Zone                       | trust                 | trust                 |
 
 ### HPE Juniper Networking SRX Object Names
 
-| **Element**                        | **Object Hierarchy**             | **Name**                        |
-| ---------------------------------- | -------------------------------- | ------------------------------- |
-| Security Zone - Trust              | [ security zones security-zone ] | trust                           |
-| Security Zone - Untrust            | [ security zones security-zone ] | untrust                         |
-| Security Zone - Cloudflare WAN     | [ security zones security-zone ] | cloudflare                      |
-| IKE Proposal (only one required)   | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
-| IKE Policy - Tunnel 1              | [ security ike policy ]          | cf-wan-ike-pol-01               |
-| IKE Policy - Tunnel 2              | [ security ike policy ]          | cf-wan-ike-pol-02               |
-| IKE Gateway - Tunnel 1             | [ security ike gateway ]         | cf-wan-ike-gw-01                |
-| IKE Gateway - Tunnel 2             | [ security ike gateway ]         | cf-wan-ike-gw-02                |
-| IPsec Proposal (only one required) | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
-| IPsec Policy (only one required)   | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
-| IPsec Tunnel - Tunnel 1            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
-| IPsec Tunnel - Tunnel 2            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
+| **Element**                          | **Object Hierarchy**             | **Name**                        |
+| ------------------------------------ | -------------------------------- | ------------------------------- |
+| Security Zone - Trust                | [ security zones security-zone ] | trust                           |
+| Security Zone - Untrust              | [ security zones security-zone ] | untrust                         |
+| Security Zone - Cloudflare WAN       | [ security zones security-zone ] | cloudflare                      |
+| IKE Proposal (only one required)     | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
+| IKE Policy - Tunnel 1                | [ security ike policy ]          | cf-wan-ike-pol-01               |
+| IKE Policy - Tunnel 2                | [ security ike policy ]          | cf-wan-ike-pol-02               |
+| IKE Gateway - Tunnel 1               | [ security ike gateway ]         | cf-wan-ike-gw-01                |
+| IKE Gateway - Tunnel 2               | [ security ike gateway ]         | cf-wan-ike-gw-02                |
+| IPsec Proposal (only one required)   | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
+| IPsec Policy (only one required)     | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
+| IPsec Tunnel - Tunnel 1              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
+| IPsec Tunnel - Tunnel 2              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
 
 ## Assumptions
 
@@ -216,7 +216,7 @@ Configure the following:
 Define an IKE Proposal with the following settings:
 
 | **Attribute**            | **Value**       |
-| ------------------------ | --------------- |
+| ------------------------ | ----------------|
 | authentication-method    | pre-shared-keys |
 | dh-group                 | group20         |
 | authentication-algorithm | sha256          |
@@ -356,13 +356,13 @@ _Perform in Configuration Mode_
 
 The following example allows all source & destination IPs, ports, and protocols/services between `cloudflare` and `trust` as well as between `trust` and `cloudflare`.
 
-| **Attribute**       | **Value**     |
-| ------------------- | ------------- |
-| source-address      | any           |
-| destination-address | any           |
-| application         | any           |
-| action              | permit        |
-| log                 | session-close |
+| **Attribute**            | **Value**     |
+| ------------------------ | ------------- |
+| source-address           | any           |
+| destination-address      | any           |
+| application              | any           |
+| action                   | permit        |
+| log                      | session-close |
 
 ```txt
 set security policies from-zone cloudflare to-zone trust policy cloudflare-to-trust-permit match source-address any
@@ -389,18 +389,18 @@ This example assumes traffic originating from 192.168.125.0/24 (ingress interfac
 Implementing Filter-Based Forwarding (FBF) requires four steps:
 
 1. Create a Forwarding Routing Instance
-   - Think of the Routing Instance as a "bucket" containing an alternate routing table
-   - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
+    - Think of the Routing Instance as a "bucket" containing an alternate routing table
+    - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
 2. Create a Firewall Filter
-   - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
-   - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
+    - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
+    - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
 3. Configure the RIB Group and Bind Routes
-   - Think of this as the "bridge" that copies interface routes to the "bucket"
-   - The Routing Instance is not part of the default routing table.
-   - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
+    - Think of this as the "bridge" that copies interface routes to the "bucket"
+    - The Routing Instance is not part of the default routing table.
+    - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
 4. Apply the Firewall Filter to the ingress traffic interface(s)
-   - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
-   - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
+    - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
+    - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
 
 #### Define a Routing Instance
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
index e64b5b02cda5941..51757cc2dd241e8 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
@@ -11,16 +11,15 @@ This tutorial shows how to configure IPsec (Internet Protocol Security) between
 You need a pre-shared key to establish the IPsec tunnel. You can use the following code to create a random key:
 
 ```js
-const a = new Uint8Array(48);
-crypto.getRandomValues(a);
-let base64String = btoa(String.fromCharCode.apply(null, a));
+		const a = new Uint8Array(48);
+		crypto.getRandomValues(a);
+		let base64String = btoa(String.fromCharCode.apply(null, a));
 
-base64String = base64String
-	.replace(/\+/g, "")
-	.replace(/\//g, "")
-	.replace(/=/g, "");
+		base64String = base64String.replace(/\+/g, '')
+								   .replace(/\//g, '')
+								   .replace(/=/g, '');
 
-console.log(base64String.substring(0, 32));
+		console.log(base64String.substring(0, 32));
 ```
 
 :::caution
@@ -59,28 +58,28 @@ You can try this code in the [Workers playground](https://workers.cloudflare.com
    - **Dynamic routing gateways (DRG)**: Select the DRG you created in step 2.
    - **Routes to your on-premises network**: Enter a CIDR (Classless Inter-Domain Routing) range you want to route to Cloudflare WAN.
    - **Tunnel 1**
-     - **Name**: Enter a name.
-     - Select **Provide custom shared secret**.
-     - Enter the **pre-shared key** you created in the Prerequisites section.
-     - **IKE (Internet Key Exchange) version**: **IKEv2**
-     - **Routing type**: **Static routing**
-     - **IPv4 inside tunnel interface - CPE**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
-     - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
-       1. Select **Show advanced options**
-       2. Select **Phase one (ISAKMP) configuration**
-          - Select **Set custom configurations**
-          - **Custom encryption algorithm**: **AES_256_CBC**
-          - **Custom authentication algorithm**: **SHA2_256**
-          - **Custom Diffie-Hellman group**: **GROUP20**
-          - **IKE session key lifetime in seconds**: **86400**
-       3. Select **Phase two (IPsec) configuration**
-          - Select **Set custom configurations**
-          - **Custom encryption algorithm**: **AES_256_CBC**
-          - **HMAC (Hash-based Message Authentication Code)\_SHA2_256_128**: **HMAC_SHA2_256_128**
-          - **IPsec session key lifetime in seconds**: **28800**
-          - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
-   - **Tunnel 2**
-     - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
+      - **Name**: Enter a name.
+      - Select **Provide custom shared secret**.
+      - Enter the **pre-shared key** you created in the Prerequisites section.
+      - **IKE (Internet Key Exchange) version**: **IKEv2**
+      - **Routing type**: **Static routing**
+      - **IPv4 inside tunnel interface - CPE**:  Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
+      - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
+         1. Select **Show advanced options**
+         2. Select **Phase one (ISAKMP) configuration**
+            - Select **Set custom configurations**
+            - **Custom encryption algorithm**: **AES_256_CBC**
+            - **Custom authentication algorithm**: **SHA2_256**
+            - **Custom Diffie-Hellman group**: **GROUP20**
+            - **IKE session key lifetime in seconds**: **86400**
+         3. Select **Phase two (IPsec) configuration**
+            - Select **Set custom configurations**
+            - **Custom encryption algorithm**: **AES_256_CBC**
+            - **HMAC (Hash-based Message Authentication Code)_SHA2_256_128**: **HMAC_SHA2_256_128**
+            - **IPsec session key lifetime in seconds**: **28800**
+            - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
+    - **Tunnel 2**
+      - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
 4. Select **Create IPsec connection**
 
 ## Cloudflare WAN
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
index 81fe83217616d1d..34b5e4bec7deae3 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ## Test Environment
 
-| **Field**   | **Value**          |
-| ----------- | ------------------ |
-| Vendor      | Palo Alto Networks |
-| Model       | PA-440             |
-| Release     | PAN-OS 11.2.8      |
-| Date Tested | March 2026         |
+| **Field**                          | **Value**                                  |
+| ---------------------------------- | ------------------------------------------ |
+| Vendor                             | Palo Alto Networks                         |
+| Model                              | PA-440                                     |
+| Release                            | PAN-OS 11.2.8                              |
+| Date Tested                        | March 2026                                 |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**       |
-| ---------------------------------- | --------------- |
-| Traffic Selection Criteria         | Route-Based VPN |
-| Routing                            | Static          |
-| Redundant Tunnels                  | Yes             |
-| Tunnel Load Balancing              | Active/Active   |
-| IKE Version                        | IKEv2           |
-| Authentication                     | Pre-Shared Key  |
-| Anti-Replay Protection             | Disabled        |
-| NAT Traversal (NAT-T)              | Not Tested      |
-| NAT-T Port                         | Not Applicable  |
-| Phase 1 - DH-Group                 | Group 20        |
-| Phase 1 - Encryption               | AES-256-CBC     |
-| Phase 1 - Authentication/Integrity | SHA-256         |
-| Phase 2 - DH-Group                 | Group 20        |
-| Phase 2 - Transport                | ESP             |
-| Phase 2 - Encryption               | AES-256-CBC     |
+| **Field**                          | **Value**                                  |
+| ---------------------------------- | ------------------------------------------ |
+| Traffic Selection Criteria         | Route-Based VPN                            |
+| Routing                            | Static                                     |
+| Redundant Tunnels                  | Yes                                        |
+| Tunnel Load Balancing              | Active/Active                              |
+| IKE Version                        | IKEv2                                      |
+| Authentication                     | Pre-Shared Key                             |
+| Anti-Replay Protection             | Disabled                                   |
+| NAT Traversal (NAT-T)              | Not Tested                                 |
+| NAT-T Port                         | Not Applicable                             |
+| Phase 1 - DH-Group                 | Group 20                                   |
+| Phase 1 - Encryption               | AES-256-CBC                                |
+| Phase 1 - Authentication/Integrity | SHA-256                                    |
+| Phase 2 - DH-Group                 | Group 20                                   |
+| Phase 2 - Transport                | ESP                                        |
+| Phase 2 - Encryption               | AES-256-CBC                                |
 
 ## Cloudflare WAN and Palo Alto Networks NGFW - Configuration Settings
 
@@ -46,85 +46,85 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_01     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.0/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 162.159.135.1     |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_01                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 162.159.135.1                                  |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`    |
+| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_02     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.2/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 172.64.135.1      |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_02                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 172.64.135.1                                   |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`    |
+| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
 
 ## Customer Premise Equipment - Palo Alto Networks
 
-| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| WAN Interface     | ethernet1/1         | ethernet1/1         |
-| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
-| Security Zone     | untrust             | untrust             |
+| **WAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| WAN Interface                      | ethernet1/1           | ethernet1/1           |
+| IP Address                         | 203.0.113.100/24      | 203.0.113.100/24      |
+| Security Zone                      | untrust               | untrust               |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ---------------------------------- | ------------------- | ------------------- |
-| Tunnel interface                   | tunnel.1            | tunnel.2            |
-| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
-| Security Zone                      | cloudflare          | cloudflare          |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| Tunnel interface                   | tunnel.1              | tunnel.2              |
+| IP Address                         | 169.254.250.1/31      | 169.254.250.3/31      |
+| Security Zone                      | cloudflare            | cloudflare            |
 
-| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| LAN Interface     | ethernet1/2         | ethernet1/2         |
-| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
-| Security Zone     | trust               | trust               |
+| **LAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| LAN Interface                      | ethernet1/2           | ethernet1/2           |
+| IP Address                         | 192.168.125.1/24      | 192.168.125.1/24      |
+| Security Zone                      | trust                 | trust                 |
 
 ### Palo Alto Networks NGFW Object Names
 
-| **Role**                           | **Label/Name**       | **Address**                 |
-| ---------------------------------- | -------------------- | --------------------------- |
-| CPE Security Zone - Trust          | Zone                 | trust                       |
-| CPE Security Zone - Untrust        | Zone                 | untrust                     |
-| CPE Security Zone - Cloudflare WAN | Zone                 | cloudflare                  |
-| CPE IKE Crypto Profile Name        | IKE Crypto Profile   | ike-aes256cbc-sha256-dh20   |
-| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile | ipsec-aes256cbc-sha256-dh20 |
+| **Role**                           | **Label/Name**            | **Address**                 |
+| ---------------------------------- | ------------------------- | --------------------------- |
+| CPE Security Zone - Trust          | Zone                      | trust                       |
+| CPE Security Zone - Untrust        | Zone                      | untrust                     |
+| CPE Security Zone - Cloudflare WAN | Zone                      | cloudflare                  |
+| CPE IKE Crypto Profile Name        | IKE Crypto Profile        | ike-aes256cbc-sha256-dh20   |
+| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile      | ipsec-aes256cbc-sha256-dh20 |
 
 ## Assumptions
 
@@ -271,12 +271,12 @@ Repeat steps for tunnel 2
 
 Define an IKE Crypto Profile with the following settings:
 
-| **Attribute**  | **Value**   |
-| -------------- | ----------- |
-| hash           | sha256      |
-| dh-group       | group20     |
-| encryption     | aes-256-cbc |
-| lifetime hours | 8           |
+| **Attribute**   | **Value**   |
+| --------------- | ----------- |
+| hash            | sha256      |
+| dh-group        | group20     |
+| encryption      | aes-256-cbc |
+| lifetime hours  | 8           |
 
 ###### CLI
 
@@ -639,10 +639,10 @@ Gateway ID      Peer-Address       Gateway Name       Role SN    Algorithm
 
 ```txt
 IKEv2 IPSec Child SAs
-Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST
-------------                   ----     ------                     --       ------   ---- -------  -------- -----    --
-cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature
-cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature
+Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST              
+------------                   ----     ------                     --       ------   ---- -------  -------- -----    --              
+cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature           
+cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature           
 
 Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 ```
@@ -652,7 +652,7 @@ Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 Use [test](https://docs.paloaltonetworks.com/network-security/ipsec-vpn/administration/troubleshooting/troubleshooting-site-to-site-vpn-issues-using-cli) commands to force Phase 1 and Phase 2 security associations:
 
 ```txt
-admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01
+admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01 
 
 Start time: Mar.30 21:23:23
 Initiate 1 IKE SA.
@@ -664,7 +664,7 @@ Initiate 1 IKE SA.
 ```
 
 ```txt
-admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01
+admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01 
 
 Start time: Mar.30 21:26:50
 Initiate 1 IPSec SA for tunnel cf-wan-ipsec-tun-01.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
index 20b793688afdc79..7aff703eec495a2 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
@@ -11,6 +11,7 @@ import { Render } from "~/components";
 This tutorial shows you how to use Cloudflare WAN (formerly Magic WAN) with the following versions of the Sophos Firewall:
 
 - **Sophos form factor tested:**
+
   - Sophos Firewall XGS and XG series hardware
   - Sophos Firewall virtual appliance on VMware
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
index 29458f09ea57950..4a09ab7e89822a7 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
@@ -195,7 +195,7 @@ Once the Edge device is added, you should land on the **Device** tab.
 
 #### User Defined WAN Link
 
-Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result, the WAN Link must be specified.
+Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result,  the WAN Link must be specified.
 
 ![Note the indicator next to GE3.](~/assets/images/cloudflare-wan/third-party/velocloud/image2.png)
 
@@ -215,7 +215,7 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 5. Select the **Network Service** defined earlier. For example, `Magic_WAN_vc-edge-03`.
 6. In the **Action** column, select the **+** button, and configure the following options:
    1. **Public WAN Link**: Choose the Public WAN Link (refer to User-Defined WAN Link)
-   2. **Local Identification Type**: _FQDN_
+   2. **Local Identification Type**: *FQDN*
    3. **Local Identification**: Enter the FQDN specified when configuring Cloudflare WAN IPsec tunnels through the Custom FQDN IKE ID API endpoint.
    4. **PSK**: Enter the Pre-Shared Key. Ensure you use the same PSK for both Cloudflare WAN IPsec tunnels.
    5. **Destination Primary Public IP**: Pre-populated from the Network Service defined earlier.
@@ -227,8 +227,8 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 
 Configure the **Site Subnets** to facilitate:
 
-- Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
-- Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
+* Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
+* Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
 
 1. Go to **Configure** > **Network Services**.
 2. Expand the **Non SD-WAN Destinations through Edge** section.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
index 948613cef1331b1..fae8475cf53be20 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
@@ -37,32 +37,32 @@ To create a Secure Internet Gateway (SIG) using vManage:
 1. From **Cisco vManage** under **Configuration**, select **Generic** and **Add Tunnel**.
 2. The table below shows the setting fields and their options.
 
-| Setting             | Type/Detail                           |
-| ------------------- | ------------------------------------- |
+| Setting             | Type/Detail                               |
+| ------------------- | ----------------------------------------- |
 | **Global Template** | Factory_Default_Global_CISCO_Template |
-| **Cisco Banner**    | Factory_Default_Retail_Banner         |
-| **Policy**          | Branch-Local-Policy                   |
+| **Cisco Banner**    | Factory_Default_Retail_Banner          |
+| **Policy**          | Branch-Local-Policy                       |
 
 **Transport & Management VPN settings**
 
-| Setting                           | Type/Detail                     |
-| --------------------------------- | ------------------------------- |
-| **Cisco VPN 0**                   | GCP-Branch-VPN0                 |
-| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template         |
-| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC |
-| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface              |
-| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01  |
+| Setting                           | Type/Detail                         |
+| --------------------------------- | ----------------------------------- |
+| **Cisco VPN 0**                   | GCP-Branch-VPN0                     |
+| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template             |
+| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC     |
+| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface                  |
+| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01 |
 
 **Basic Information settings**
 
-| Setting            | Type/Detail                             |
-| ------------------ | --------------------------------------- |
+| Setting            | Type/Detail                                 |
+| ------------------ | ------------------------------------------- |
 | **Cisco System**   | Default_BootStrap_Cisco_System_Template |
-| **Cisco Logging**  | Default_Logging_Cisco_V01               |
-| **Cisco AAA**      | AWS-Branch-AAA-Template                 |
-| **Cisco BFD**      | Default_BFD_Cisco-V01                   |
-| **Cisco OMP**      | Default*AWS_TGW_CSR_OMP_IPv46*...       |
-| **Cisco Security** | Default_Security_Cisco_V01              |
+| **Cisco Logging**  | Default_Logging_Cisco_V01                |
+| **Cisco AAA**      | AWS-Branch-AAA-Template                     |
+| **Cisco BFD**      | Default_BFD_Cisco-V01                     |
+| **Cisco OMP**      | Default_AWS_TGW_CSR_OMP_IPv46_...     |
+| **Cisco Security** | Default_Security_Cisco_V01               |
 
 When creating the Feature Template, you can choose values that apply globally or that are device specific. For example, the **Tunnel Source IP Address**, **Interface Name** and fields from **Update Tunnel** are device specific and should be chosen accordingly.
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
index 82717dcc274bcdf..017633fb496566a 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
@@ -22,19 +22,19 @@ Before proceeding, ensure that you have the anycast IPs assigned to your account
 ### IPsec tunnels
 
 1. Follow the <a href={props.addTunnelsUrl}>Add tunnels</a> instructions to create the required IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
-   - **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
-   - **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
-   - **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
-   - **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
-   - **Health check rate**: _Medium_.
-   - **Health check type**: _Request_.
-   - **Health check direction**: _Bidirectional_.
-   - **Health check target**: _Default_.
-   - **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
-   - **Replay protection**: Do not check the box, to keep this disabled.
+	- **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
+	- **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
+	- **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
+	- **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
+	- **Health check rate**: _Medium_.
+	- **Health check type**: _Request_.
+	- **Health check direction**: _Bidirectional_.
+	- **Health check target**: _Default_.
+	- **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
+	- **Replay protection**: Do not check the box, to keep this disabled.
 
 2. After you create your tunnel, the Cloudflare dashboard will load a list of tunnels set up for your account. Select the IPsec tunnel you have just created, and check the following setting:
-   - **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
+	- **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
 
 ### Static routes
 
@@ -214,4 +214,4 @@ IKE keepalive:
 [Status]: OK
 
 [Next send]: 1 sec after
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
index e49fb208f2bd10f..7639f10f685149d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
@@ -36,13 +36,13 @@ On-premises network and security appliances require manual firmware updates, pat
 
 ## Compare WAN approaches
 
-|                 | Traditional WAN (MPLS)                                                                                | SD-WAN                                                                                             | Cloudflare One                                                                                                   |
-| --------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing.   | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling.  |
-| **Cost model**  | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment.            | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model.                    |
-| **Agility**     | Weeks to months to provision new circuits. Rigid topology changes.                                    | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection.                              |
-| **Security**    | Security applied at central data center or per-site firewalls.                                        | Varies by vendor. Some offer integrated security, others require separate appliances.              | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
-| **Management**  | Separate management for WAN circuits, routers, and security appliances.                               | Single console for WAN, but security often managed separately.                                     | Single dashboard for network connectivity, routing, firewall rules, and security policies.                       |
+| | Traditional WAN (MPLS) | SD-WAN | Cloudflare One |
+|---|---|---|---|
+| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing. | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling. |
+| **Cost model** | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment. | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model. |
+| **Agility** | Weeks to months to provision new circuits. Rigid topology changes. | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection. |
+| **Security** | Security applied at central data center or per-site firewalls. | Varies by vendor. Some offer integrated security, others require separate appliances. | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
+| **Management** | Separate management for WAN circuits, routers, and security appliances. | Single console for WAN, but security often managed separately. | Single dashboard for network connectivity, routing, firewall rules, and security policies. |
 
 ## Plan your migration
 
@@ -78,11 +78,7 @@ Organizations that start with Cloudflare WAN for site-to-site connectivity and p
 
 ## Next steps
 
-- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the
-  Cloudflare One Appliance or a third-party device.
-- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all
-  Cloudflare One connectivity options and choose the right combination for your
-  deployment.
-- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported
-  on-ramps for connecting your networks.
+- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the Cloudflare One Appliance or a third-party device.
+- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all Cloudflare One connectivity options and choose the right combination for your deployment.
+- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported on-ramps for connecting your networks.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the architecture of Cloudflare One as a SASE platform.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
index 67d32f2a51ebbf2..233eb735ada557b 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
@@ -21,9 +21,7 @@ params:
 
 import { Render } from "~/components";
 
-<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web
-Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress
-traffic.
+<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress traffic.
 
 You can apply network and HTTP Gateway policies alongside <a href="/cloudflare-network-firewall/">Cloudflare Network Firewall</a> policies (for L3/4 traffic filtering) to Internet-bound traffic or private traffic entering the Cloudflare network through Cloudflare WAN (formerly Magic WAN). Additionally, you can configure Gateway to [resolve DNS queries](#dns-filtering) from Cloudflare WAN.
 
@@ -130,9 +128,9 @@ Source ports are fixed to `1024`-`65535` and cannot be overridden.
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
 
 ## Test Gateway integration
 
@@ -143,7 +141,6 @@ If you are still testing Gateway and Cloudflare is not your default route, confi
 Confirm there is an entry for the test in <a href={props.gatewayLogsURL}>HTTP Gateway Activity Logs</a>.
 
 Verify the following details:
-
 - **Destination IP**: Should be the public IP address of `ifconfig.me`.
 - **Source IP**: Should be the private (WAN) address of the host with the browser.
 - **Outbound connection**: Should be sourced from a Cloudflare WAN IP address, not any public IP address that Cloudflare might be advertising on your behalf.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
index 05ee41c0b931606..ca49d64696b2380 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
@@ -1,8 +1,8 @@
 ---
-{}
+ {}
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) provides site-to-site connectivity and packet-level security through [Cloudflare Network Firewall](/cloudflare-network-firewall/). The Cloudflare One integrations below extend that foundation with identity-aware security — user-level access policies through [Cloudflare Access](/cloudflare-one/access-controls/), secure Internet egress through [Cloudflare Gateway](/cloudflare-one/traffic-policies/), and device-level routing through the [Cloudflare One Client (formerly WARP)](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/).
 
@@ -10,4 +10,4 @@ Review the tutorials to learn how to use Cloudflare WAN with these Cloudflare On
 
 <DirectoryListing />
 
-If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
+If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
index f80c67cfd5709c5..00c200fe13cb9b3 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
@@ -19,9 +19,7 @@ Cloudflare WAN carries three types of traffic, and different security services a
 
 ### Cloudflare Network Firewall
 
-<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides
-packet-level filtering at layers 3 and 4. You define allow or block rules based
-on IP addresses, ports, and protocols.
+<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides packet-level filtering at layers 3 and 4. You define allow or block rules based on IP addresses, ports, and protocols.
 
 - **Applies to**: inbound, outbound, and east-west traffic
 - **Included with**: Cloudflare WAN by default for [standard features](/cloudflare-network-firewall/plans/)
@@ -76,16 +74,16 @@ AI visibility is not a separate inline security service. It is an analytics feat
 
 ## Use-case mapping
 
-| Traffic scenario                                     | Recommended services                                          |
-| ---------------------------------------------------- | ------------------------------------------------------------- |
-| Block traffic between sites by IP, port, or protocol | Network Firewall                                              |
-| Filter DNS queries from branch offices               | Gateway DNS policies                                          |
-| Block malware downloads from branch offices          | Gateway HTTP policies                                         |
-| Prevent sensitive data uploads to the Internet       | DLP (via Gateway HTTP policies)                               |
-| Isolate risky web browsing from branch users         | Browser Isolation (via Gateway HTTP policies)                 |
-| Detect and block unsanctioned SaaS applications      | CASB + Gateway HTTP policies                                  |
-| Monitor employee AI tool usage                       | AI Security Report (via Gateway)                              |
-| Protect against DDoS on customer-owned IPs           | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
+| Traffic scenario | Recommended services |
+|---|---|
+| Block traffic between sites by IP, port, or protocol | Network Firewall |
+| Filter DNS queries from branch offices | Gateway DNS policies |
+| Block malware downloads from branch offices | Gateway HTTP policies |
+| Prevent sensitive data uploads to the Internet | DLP (via Gateway HTTP policies) |
+| Isolate risky web browsing from branch users | Browser Isolation (via Gateway HTTP policies) |
+| Detect and block unsanctioned SaaS applications | CASB + Gateway HTTP policies |
+| Monitor employee AI tool usage | AI Security Report (via Gateway) |
+| Protect against DDoS on customer-owned IPs | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
 
 ## How services compose
 
@@ -101,12 +99,7 @@ This means you can layer multiple security services on the same traffic flow wit
 
 ## Next steps
 
-- <a href={props.gatewaySetupURL}>
-  	Connect to Cloudflare Gateway with Cloudflare WAN
-  </a>
-  : Detailed setup guide for Gateway integration with WAN traffic.
-- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure
-  packet-level filtering rules.
+- <a href={props.gatewaySetupURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a>: Detailed setup guide for Gateway integration with WAN traffic.
+- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure packet-level filtering rules.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the full architecture of Cloudflare One as a SASE platform.
-- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your
-  migration from traditional WAN to Cloudflare.
+- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your migration from traditional WAN to Cloudflare.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
index ef33bc683575a8e..41ddc29de0c6c15 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
@@ -8,7 +8,7 @@ params:
   - arrURL
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) can work together with <a href="/cloudflare-one/networks/connectors/cloudflare-tunnel/">Cloudflare Tunnel</a> to provide easy access between your networks and applications.
 
@@ -30,12 +30,12 @@ To route the same prefix to different destinations, use separate [virtual networ
 
 Cloudflare reserves the following IP ranges for Zero Trust services:
 
-| IP range         | Purpose                                                                                              |
-| ---------------- | ---------------------------------------------------------------------------------------------------- |
-| `100.64.0.0/12`  | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/)       |
-| `100.96.0.0/12`  | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
-| `100.80.0.0/16`  | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/)             |
-| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/)                                           |
+| IP range | Purpose |
+| --- | --- |
+| `100.64.0.0/12` | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/) |
+| `100.96.0.0/12` | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
+| `100.80.0.0/16` | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/) |
+| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/) |
 
 Do not configure routes that overlap with these reserved ranges.
 
@@ -51,8 +51,7 @@ Longest-prefix-match routing is the default route selection method. Other mechan
 
 ### Automatic Return Routing (ARR)
 
-<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for
-return traffic.
+<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for return traffic.
 
 When ARR is enabled:
 
@@ -89,6 +88,7 @@ To verify that a `cloudflared` tunnel works correctly with your Cloudflare WAN c
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
+
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
index 425405bded13584..02de971802f7fa9 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
@@ -73,9 +73,9 @@ You must log out and log back in with at least one device to ensure the configur
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
 
 ## Double encapsulation
 
@@ -91,8 +91,7 @@ To learn which IP addresses and UDP ports you should exclude to accomplish this,
 	file="mconn/network-options/app-aware-policies/warp-traffic"
 	product="networking-services"
 	params={{
-		warpFirewallURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/",
+		warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 	}}
 />
 
diff --git a/src/content/partials/networking-services/cni-product-use-cases.mdx b/src/content/partials/networking-services/cni-product-use-cases.mdx
index 5d902dd611989d8..1e1079f2de90aec 100644
--- a/src/content/partials/networking-services/cni-product-use-cases.mdx
+++ b/src/content/partials/networking-services/cni-product-use-cases.mdx
@@ -4,12 +4,13 @@
 
 CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications.
 
-|                                                                                                                                                                                                         | Dataplane v1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Dataplane v2                                                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Supported.                                                                                                                                                                |
-| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare.                                              | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
-| **Cloudflare WAN and Zero Trust** <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds.                      | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
-| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence).                                                                                                             | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP.                                                                                                                                                                                                                                                                              | Not supported.                                                                                                                                                            |
-| **Application Security and Performance** <br /> Improve the performance and security of your web applications                                                                                           | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
+
+|  | Dataplane v1 | Dataplane v2 |
+| ---- | ---- | ---- |
+| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Cloudflare WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. |
+| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
 
 For more details refer to the [prerequisites section](/network-interconnect/get-started/#prerequisites).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
index 3776c9a7c06a1bd..4b05caa926f685e 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
@@ -104,5 +104,4 @@ curl https://api.cloudflare.com/client/v4/graphql \
 ```
 
 [^1]: For details, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
-
-[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
+[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
index 40149b5bcec5005..0471540ec9e7cb8 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
@@ -17,13 +17,13 @@ You need the following to query endpoint health check data:
 
 The following parameters are some of the most common ones in the `filter` object:
 
-| Parameter      | Description                                                                                                                                                                                                                                             |
-| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `date_geq`     | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
-| `date_leq`     | _(Optional)_ End date for the query. Uses the same format as `date_geq`.                                                                                                                                                                                |
-| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions.                                                                                                  |
-| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format.                                                                                                                                                                                                          |
-| `limit`        | Maximum number of result groups to return.                                                                                                                                                                                                              |
+| Parameter | Description |
+| :---- | :---- |
+| `date_geq` | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
+| `date_leq` | _(Optional)_ End date for the query. Uses the same format as `date_geq`. |
+| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions. |
+| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format. |
+| `limit` | Maximum number of result groups to return. |
 
 You can also filter on any dimension listed in the [Available dimensions](#available-dimensions) table. Append an operator suffix to the dimension name to create a filter — for example, `endpoint_in` to filter by a list of endpoints, or `checkType_neq` to exclude a specific check type. Using a dimension name without a suffix filters for equality. For the full list of supported operators, refer to [Filtering](/analytics/graphql-api/features/filtering/).
 
@@ -31,28 +31,28 @@ You can also filter on any dimension listed in the [Available dimensions](#avail
 
 You can query the following dimensions in the `dimensions` field:
 
-| Dimension                | Description                                                                      |
-| :----------------------- | :------------------------------------------------------------------------------- |
-| `checkId`                | The unique ID of the configured health check.                                    |
-| `checkType`              | The type of health check (for example, `icmp`).                                  |
-| `endpoint`               | The IP address of the endpoint being checked.                                    |
-| `name`                   | The name assigned to the health check when configured (may be empty if not set). |
-| `date`                   | Event timestamp truncated to the day.                                            |
-| `datetime`               | Full event timestamp.                                                            |
-| `datetimeMinute`         | Event timestamp truncated to the minute.                                         |
-| `datetimeFiveMinutes`    | Event timestamp truncated to five-minute intervals.                              |
-| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals.                                |
-| `datetimeHalfOfHour`     | Event timestamp truncated to 30-minute intervals.                                |
-| `datetimeHour`           | Event timestamp truncated to the hour.                                           |
+| Dimension | Description |
+| :---- | :---- |
+| `checkId` | The unique ID of the configured health check. |
+| `checkType` | The type of health check (for example, `icmp`). |
+| `endpoint` | The IP address of the endpoint being checked. |
+| `name` | The name assigned to the health check when configured (may be empty if not set). |
+| `date` | Event timestamp truncated to the day. |
+| `datetime` | Full event timestamp. |
+| `datetimeMinute` | Event timestamp truncated to the minute. |
+| `datetimeFiveMinutes` | Event timestamp truncated to five-minute intervals. |
+| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals. |
+| `datetimeHalfOfHour` | Event timestamp truncated to 30-minute intervals. |
+| `datetimeHour` | Event timestamp truncated to the hour. |
 
 ### Available metrics
 
-| Metric               | Description                                       |
-| :------------------- | :------------------------------------------------ |
-| `count`              | Total number of health check events in the group. |
-| `sum.total`          | Total number of health check probes sent.         |
-| `sum.failures`       | Number of failed health check probes.             |
-| `avg.lossPercentage` | Average calculated loss percentage (0-100).       |
+| Metric | Description |
+| :---- | :---- |
+| `count` | Total number of health check events in the group. |
+| `sum.total` | Total number of health check probes sent. |
+| `sum.failures` | Number of failed health check probes. |
+| `avg.lossPercentage` | Average calculated loss percentage (0-100). |
 
 ### API call
 
@@ -111,43 +111,43 @@ https://api.cloudflare.com/client/v4/graphql \
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"accounts": [
-				{
-					"magicEndpointHealthCheckAdaptiveGroups": [
-						{
-							"count": 288,
-							"dimensions": {
-								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-								"checkType": "icmp",
-								"datetimeFiveMinutes": "2026-01-21T12:00:00Z",
-								"endpoint": "103.21.244.100"
-							},
-							"sum": {
-								"failures": 0,
-								"total": 288
-							}
-						},
-						{
-							"count": 288,
-							"dimensions": {
-								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-								"checkType": "icmp",
-								"datetimeFiveMinutes": "2026-01-21T12:05:00Z",
-								"endpoint": "103.21.244.100"
-							},
-							"sum": {
-								"failures": 2,
-								"total": 288
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "accounts": [
+        {
+          "magicEndpointHealthCheckAdaptiveGroups": [
+            {
+              "count": 288,
+              "dimensions": {
+                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+                "checkType": "icmp",
+                "datetimeFiveMinutes": "2026-01-21T12:00:00Z",
+                "endpoint": "103.21.244.100"
+              },
+              "sum": {
+                "failures": 0,
+                "total": 288
+              }
+            },
+            {
+              "count": 288,
+              "dimensions": {
+                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+                "checkType": "icmp",
+                "datetimeFiveMinutes": "2026-01-21T12:05:00Z",
+                "endpoint": "103.21.244.100"
+              },
+              "sum": {
+                "failures": 2,
+                "total": 288
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
index f9f5e61e69a7e7b..f224c2ab01efe75 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
@@ -97,4 +97,4 @@ https://api.cloudflare.com/client/v4/graphql \
 #=> }
 ```
 
-[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
+[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
index 630b17ac37eb812..1240490c155138a 100644
--- a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
+++ b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
@@ -40,7 +40,7 @@ Authentication failures in Phase 1 indicate a PSK mismatch. To resolve:
 
 1. Go to **Connectors** and select your tunnel.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select **Generate new PSK**.
 3. Copy the new PSK exactly — do not add extra spaces or characters.
@@ -72,9 +72,9 @@ Disable anti-replay protection on your tunnel endpoint, or set the replay window
 
 #### Health check type incompatible with stateful firewall
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default _Reply_ health check packets because no matching ICMP request exists in their session table.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default *Reply* health check packets because no matching ICMP request exists in their session table.
 
-Change the health check type from _Reply_ to _Request_. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
+Change the health check type from *Reply* to *Request*. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
 
 #### ISP blocking health check return path
 
@@ -128,7 +128,7 @@ Use IPsec logs to monitor tunnel activity during the key-exchange phase of the I
 
 1. Go to the **Logpush** page.
 
-   <DashButton url="/?to=/:account/logs" />
+	<DashButton url="/?to=/:account/logs" />
 
 2. Select **Create a Logpush job**.
 3. Select **IPsec logs** as your dataset.
diff --git a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
index 57fe9ec9026d18b..01689291e53b1c2 100644
--- a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
+++ b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
@@ -12,9 +12,8 @@ If you are using a Cloudflare IP, you do not need to advertise your prefixes.
 You must [put the appropriate MSS clamps](#set-maximum-segment-size) in place before [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) changes are made. Failure to apply an MSS clamp can result in dropped packets and hard-to-debug connectivity issues.
 
 Also, when using [Cloudflare Network Interconnect](/magic-transit/network-interconnect/) with Magic Transit you must set the following MSS clamp sizes to accommodate additional overhead:
-
 - GRE tunnels over CNI with Dataplane v1: 1476 bytes
 - CNI with Dataplane v2 / CNI with Dataplane v1 with a maximum transmission unit (MTU) size of 1500 bytes handoff does not require an MSS clamp.
 
 MSS clamps are used to backhaul data from the data center where traffic is ingested (close to the end user) to the facility with the CNI link.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
index 2eab7b7b67f803a..c10384b93e929ca 100644
--- a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
+++ b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
@@ -3,19 +3,19 @@ params:
   - mtLpCreateTunnel
   - mtLpStaticRoute
   - mtLpBgpPeering
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To use Magic Transit, you need to own a publicly routable IP address block with a minimum size of `/24`. If you do not own a `/24` address block, you can use Magic Transit with a Cloudflare-owned IP address. This option is helpful if you do not meet the `/24` prefix length requirements or want to protect a smaller network.
 
 To protect your network with a Cloudflare IP address, contact your account manager. After you receive your IP address:
 
 - <a href={props.mtLpCreateTunnel}>Create a tunnel</a>.
-- <a href={props.mtLpStaticRoute}>Set up static routes</a> or
-  <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
+- <a href={props.mtLpStaticRoute}>Set up static routes</a> or <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
 - [Configure health checks](/magic-transit/network-health/run-endpoint-health-checks/).
 - Confirm you properly configured [tunnel](/magic-transit/network-health/update-tunnel-health-checks-frequency/) and endpoint health checks.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.
 
-When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
+When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
index df51d0077eac1b3..312b1d8e17bf88c 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
@@ -5,9 +5,11 @@
 The MSS value depends on how your network is set up.
 
 - **Magic Transit ingress-only traffic (DSR):**
+
   - **On your edge router transit ports**: Set a TCP MSS clamp to a maximum of 1,436 bytes.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: Apply the MSS clamp on the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce the current value by 24 bytes.
 
 - **For Magic Transit ingress + egress traffic:**
+
   - **On the Magic Transit GRE tunnel internal interface**: Meaning where the Magic Transit egress traffic will traverse. Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 24 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
index 9724b74d99a9784..ca0dc864b8bd976 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
@@ -5,9 +5,11 @@
 For IPsec tunnels, the value you need to specify depends on how your network is set up. The MSS clamping value is lower than for GRE tunnels because the physical interface sees IPsec-encrypted [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/), not TCP packets, and MSS clamping does not apply to those.
 
 - **Magic Transit ingress-only traffic (DSR):**
+
   - **On your edge router transit ports**: Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 140 bytes.
 
 - **Magic Transit ingress + egress traffic:**
+
   - **On your edge router**: Apply this on your Magic Transit IPsec tunnel internal interface (that is, where the Magic Transit egress traffic will traverse). Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,360 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the IPsec-terminating device in your premises) to reduce its current value by 140 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
index 5768c1e380eceba..b760409416dfd6f 100644
--- a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
@@ -18,8 +18,8 @@ The following steps outline the recommended multi-step draining process to achie
 2. **Wait for global BGP convergence**: Allow a period of time (typically five to ten minutes) for the new native advertisement to propagate fully across the global routing table, and for routes to converge. This passive waiting period ensures that the majority of traffic has shifted to your local network before the next step.
 3. **Signal BGP withdrawal from the Cloudflare edge**: Once you have verified that traffic has successfully drained, use one of the BGP control methods to stop the advertisement of the prefix from the Cloudflare edge.
 
-   :::caution[ISP route refresh delays may impact traffic]
-   Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
-   :::
+	:::caution[ISP route refresh delays may impact traffic]
+	Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
+	:::
 
-4. The draining process is complete.
+4. The draining process is complete.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-user-role.mdx b/src/content/partials/networking-services/magic-user-role.mdx
index 72715ce73e544d4..5f688524a5b726f 100644
--- a/src/content/partials/networking-services/magic-user-role.mdx
+++ b/src/content/partials/networking-services/magic-user-role.mdx
@@ -12,7 +12,7 @@ For example, if multiple teams manage different Cloudflare products on the same
 
 1. Go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+	 <DashButton url="/?to=/:account/members" />
 
 2. Under **Members**, enter an existing user's name and select **Search**.
 3. Expand the menu at the end of the user row.
diff --git a/src/content/partials/networking-services/mconn/device-metrics.mdx b/src/content/partials/networking-services/mconn/device-metrics.mdx
index 278ab4d0b610b62..a2fad49b670b4f3 100644
--- a/src/content/partials/networking-services/mconn/device-metrics.mdx
+++ b/src/content/partials/networking-services/mconn/device-metrics.mdx
@@ -13,59 +13,59 @@ For example:
 
 ```graphql graphql-api-explorer
 query telemetry(
-	$accountTag: string
-	$snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
-	$snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
-	$snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
-	$limit: int64!
+  $accountTag: string
+  $snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
+  $snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
+  $snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
+  $limit: int64!
 ) {
-	viewer {
-		accounts(filter: { accountTag: $accountTag }) {
-			snapshots: mconnTelemetrySnapshots(
-				filter: $snapshotsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC]
-			) {
-				max {
-					cpuCount
-					loadAverage1m
-					memoryFreeBytes
-					memoryTotalBytes
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-			snapshotMounts: mconnTelemetrySnapshotMounts(
-				filter: $snapshotMountsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC]
-			) {
-				max {
-					availableBytes
-					totalBytes
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-			snapshotThermals: mconnTelemetrySnapshotThermals(
-				filter: $snapshotThermalsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
-			) {
-				max {
-					currentCelsius
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-		}
-	}
+  viewer {
+    accounts(filter: { accountTag: $accountTag }) {
+      snapshots: mconnTelemetrySnapshots(
+        filter: $snapshotsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC]
+      ) {
+        max {
+          cpuCount
+          loadAverage1m
+          memoryFreeBytes
+          memoryTotalBytes
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+      snapshotMounts: mconnTelemetrySnapshotMounts(
+        filter: $snapshotMountsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC]
+      ) {
+        max {
+          availableBytes
+          totalBytes
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+      snapshotThermals: mconnTelemetrySnapshotThermals(
+        filter: $snapshotThermalsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
+      ) {
+        max {
+          currentCelsius
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+    }
+  }
 }
 ```
 
@@ -75,4 +75,4 @@ The metric `average CPU load` is unique and distinctly different from `CPU utili
 
 CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the Cloudflare One Appliance CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
 
-Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
+Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/licence-keys.mdx b/src/content/partials/networking-services/mconn/licence-keys.mdx
index 19fc13fb15ac9ea..762bbc9168a849d 100644
--- a/src/content/partials/networking-services/mconn/licence-keys.mdx
+++ b/src/content/partials/networking-services/mconn/licence-keys.mdx
@@ -3,6 +3,8 @@ params:
   - virtualConnectorName
 ---
 
+
+
 :::note
 You cannot use the same license key twice, or reuse a key once the virtual machine has been registered with Cloudflare. You need a new key from your account team for every new {props.virtualConnectorName}.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
index 5ed0d70f3420a55..720da967d7f0d34 100644
--- a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
@@ -7,4 +7,4 @@ params:
 Before you can activate your Cloudflare One Appliance (formerly Magic WAN Connector), you need to follow Cloudflare's instructions regarding DHCP. For instructions, refer to:
 
 - The <a href={props.hardwareConnectorURL}>hardware version of Cloudflare One Appliance</a>
-- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
+- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
index 69bcf5dfd06bb9d..abb2c35e51bfd08 100644
--- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -3,38 +3,38 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
-    `}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
+	`}
+	inline={false}
+	/>
+	</>
 )
-} 4. In **Status**, select _Deactivated_ from the drop-down menu. 5. Select **Update**.
+}
+4. In **Status**, select _Deactivated_ from the drop-down menu.
+5. Select **Update**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index e2cb63fb178ba6b..0946f2695192a8a 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -12,4 +12,4 @@ The default password for Cloudflare One Appliance is the serial number (also kno
 
 The default password for Virtual Appliance is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
 
-For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
+For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
index 20bffc12db414cc..b11277c02a77557 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -8,33 +8,34 @@ import { DashButton, Markdown } from "~/components";
 In **Basic information**, you can change the name and description of your Cloudflare One Appliance (formerly Magic WAN Connector).
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**. 4. In **Basic information** make the necessary changes. 5. Select **Save**.
+}
+3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. In **Basic information** make the necessary changes.
+5. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
index 16e6075ed0b533e..f71c11c0de55a12 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -6,32 +6,36 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Connectors** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**. 5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**. 6. Make the necessary changes. 7. Select **Save**.
+}
+3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**.
+5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**.
+6. Make the necessary changes.
+7. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
index e0c56079072bb08..7a5e68df4e8f5b2 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
@@ -6,35 +6,35 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a> > **Insights**.
 		2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on.
 		3. Select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-<Markdown
-text={`
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/networking-insights/health" />
+				<Markdown
+	text={`
 		3. Find the site you want to make changes on > select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 		`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
index 79373537351ff1d..267156ca7a1e2d3 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -8,33 +8,35 @@ import { DashButton, Markdown } from "~/components";
 You can only add or remove applications to Breakout traffic and Prioritized traffic. To add or remove applications:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**. 5. Select **Add** to add a new application. 6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
+}
+3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**.
+5. Select **Add** to add a new application.
+6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
index 6a9d81008d379c6..c8f54f97a753b77 100644
--- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -3,7 +3,7 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 Cloudflare One Appliance (formerly Magic WAN Connector) communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
@@ -18,34 +18,33 @@ There are three symbols for the heartbeat signal that allow you to quickly check
 ### Access Cloudflare One Appliance's heartbeat
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Connectors** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
-    `}
-    inline={false}
-    />
-    </>
-
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
+
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
+	`}
+	inline={false}
+	/>
+	</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
index e0ac8962997b44f..b94efb16efe2c31 100644
--- a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
@@ -3,43 +3,42 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 The Interrupt window defines when Cloudflare One Appliance (formerly Magic WAN Connector) can update its systems. When Cloudflare One Appliance is updating, this may result in an interruption to existing connections. Set up a time window that minimizes disruption to your sites.
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks** > **Connectors**.
 		2. In **Appliances** > **Appliances**, select the Cloudflare One Appliance for which you want to set up the update window > **Edit**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
+	<>
 
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
-    `}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
+	`}
+	inline={false}
+	/>
+	</>
 )
-} 3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
-
-- **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
-- **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
-- **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
+}
+3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
+   - **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
+   - **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
+   - **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
index 622bec3086c2415..ad72dcbe7fe8d77 100644
--- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
@@ -9,27 +9,30 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag
 
 {/* Dashboard steps for CF1 Cloudflare WAN (Cloudflare One dashboard) */}
 { props.dashName === "CF1 Cloudflare WAN" && (
-<>
-<ol>
-<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
-<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
-</ol>
-</>
+	<>
+	<ol>
+		<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
+		<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
+	</ol>
+	</>
 )
 }
 
 {/* Dashboard steps for Cloudflare WAN (standalone dashboard) */}
 { props.dashName !== "CF1 Cloudflare WAN" && (
-<>
-<ol>
-<li>Go to the <strong>Connectors</strong> page.
-<br />
-<DashButton url="/?to=/:account/magic-networks/connections" />
-</li>
-<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
-</ol>
-</>
+	<>
+	<ol>
+		<li>Go to the <strong>Connectors</strong> page.
+			<br />
+			<DashButton url="/?to=/:account/magic-networks/connections" />
+		</li>
+		<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
+	</ol>
+	</>
 )
-} 3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard. 4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account. 5. Select **Register appliance**.
+}
+3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard.
+4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account.
+5. Select **Register appliance**.
 
-Your device is now registered with your account.
+Your device is now registered with your account.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
index b9ba61db220dfb4..fa154fec8acde27 100644
--- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
@@ -6,7 +6,6 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 When adding or removing Cloudflare One Appliances (formerly Magic WAN Connectors), you need to be aware of the difference between the physical device and its profile.
-
 - The physical device is the hardware at your site.
 - The profile contains the configuration that allows the device to connect to Cloudflare, including your WANs, LANs, traffic steering, and LAN policies.
 
@@ -15,69 +14,67 @@ You can have more than one Cloudflare One Appliance in one profile if you initia
 ## Remove a profile
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to **Appliances** > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to **Appliances** > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
+}
+3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
 
 ## Remove a physical device
 
 To remove a Cloudflare One Appliance from your account:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
+}
+3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 58394a01819ac0d..5dc4a5441cd0fde 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -16,7 +16,7 @@ params:
   - networkSegmentationURL
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 The Cloudflare One Appliance (formerly Magic WAN Connector) software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
 
@@ -91,14 +91,11 @@ When a failover occurs, traffic is moved to the new active node. It could take u
 
 This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
 
-<Render
-	file="mconn/wan-two-tunnels"
-	product="networking-services"
-	params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }}
-/>
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }} />
 
 When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in Cloudflare One Appliance routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 
+
 Creating several WAN connections also means Cloudflare One Appliance can failover between circuits according to their health.
 
 ### High-capacity use cases
@@ -111,7 +108,7 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ### WAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
 - **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. For details on how Cloudflare calculates priorities, refer to <a href={props.trafficSteeringURL}>Traffic steering</a>.
 - **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. For details, refer to <a href={props.hcFrequencyURL}>Update tunnel health checks frequency</a>.
@@ -119,9 +116,9 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ## LAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
-- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
+- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable  DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
 - **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
 - **Routed subnets:** Configures additional subnets behind a layer 3 router. For details, refer to <a href={props.routedSubnetsURL}>Routed subnets</a>.
 
@@ -129,4 +126,4 @@ If you do not have more than one anycast IP configured in your account, and you
 
 Depending on your use case, you can define policies in your Cloudflare One Appliance to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
-For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
+For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index d64025ffaf32777..7eb868cf827fa41 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -7,64 +7,53 @@ params:
   - dashName
 ---
 
-import {
-	APIRequest,
-	Aside,
-	AnchorHeading,
-	CURL,
-	DashButton,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-} from "~/components";
+import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
 
 { props.magicWord === "breakout" && (
-<>
-<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
-<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-</>
-)
+	<>
+		<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
+		<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+	</>
+	)
 }
 
 { props.magicWord === "prioritized" && (
-<>
-<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
-<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
-<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-</>
-)
+	<>
+		<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
+		<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
+		<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+	</>
+	)
 }
 
 { props.magicWord === "breakout" && (
-<>
-<pre class="mermaid">
-{`
-flowchart LR
-accTitle: Breakout traffic flow
-accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
-a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
-
-    		a-- Breakout traffic ---d(Application1) & e(Application2) --> c
-
-    		classDef orange fill:#f48120,color: black
-    		class a,b orange
-    		`}
-    	</pre>
-    	<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
-    	<Aside type="note" title="A note on security">
-    	<Markdown
-    	text={`
-    	We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
+	<>
+		<pre class="mermaid">
+			{`
+			flowchart LR
+			accTitle: Breakout traffic flow
+			accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
+			a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
+
+			a-- Breakout traffic ---d(Application1) & e(Application2) --> c
+
+			classDef orange fill:#f48120,color: black
+			class a,b orange
+			`}
+		</pre>
+		<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
+		<Aside type="note" title="A note on security">
+		<Markdown
+		text={`
+		We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
 
     For details on how Cloudflare routes traffic, refer to <a href="${props.trafficSteeringURL}">Traffic steering</a>.
-    	`}
-    	inline={false}
-    	/>
-    	</Aside>
-    </>
-    )
-
+		`}
+		inline={false}
+		/>
+		</Aside>
+	</>
+	)
 }
 
 ## Add an application to your account
@@ -75,28 +64,28 @@ To add applications to your account:
 
 Send a `POST` request to add new apps to your account.
 
-    <APIRequest
-    path="/accounts/{account_id}/magic/apps"
-    method="POST"
-    json={{
+	<APIRequest
+	path="/accounts/{account_id}/magic/apps"
+	method="POST"
+	json={{
     "managed_app_id": "<APP_ID>",
     "name": "<APP_NAME>",
     "type": "<APP_TYPE>",
-    }}
-    />
-
-    ```json output
-    {
-    	"result": {
-    		"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
-    		"name": "<APP_NAME>",
-    		"type": "<APP_TYPE>",
-    	},
-    	"success": true,
-    	"errors": [],
-    	"messages": []
-    }
-    ```
+	}}
+	/>
+
+	```json output
+	{
+		"result": {
+			"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
+			"name": "<APP_NAME>",
+			"type": "<APP_TYPE>",
+		},
+		"success": true,
+		"errors": [],
+		"messages": []
+	}
+	```
 
 You can now add this new app to the {props.featureName} list in your Cloudflare One Appliance.
 
@@ -326,88 +315,87 @@ You need to delete {props.featureName} applications for each of your existing si
 </TabItem> </Tabs>
 
 { props.magicWord === "breakout" && (
-<>
-<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
-
-    	<Markdown
-    	text={`
+	<>
+		<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
 
+		<Markdown
+		text={`
 You can pin applications to a specific WAN port in Cloudflare One Appliance when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, Cloudflare One Appliance automatically fails over to a standard configured WAN port priority.
 
 With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
 
 To pin applications to a WAN port:
-`}
-inline={false}
-/>
-
-    	{ props.dashName === "CF1 Cloudflare WAN" ? (
-    		<>
-    			<Markdown
-    		text={`
-    			1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
-    			2. Go to **Connectors** > **Appliances** > **Profiles**.
-    			3. Select the Cloudflare One Appliance you want to configure > **Edit**.
-    		`}
-    		inline={false}
-    		/>
-    		</>
-    	) : (
-    		<>
-    		<Markdown
-    			text={`
-    				1. Go to the **Connectors** page.
-    				`}
-    			inline={false}
-    			/>
-    				<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    				<Markdown
-    			text={`
-    				2. Go to the **Appliances** tab > **Profiles**.
-    				`}
-    			inline={false}
-    			/>
-    			<Markdown
-    		text={`
-    			3. Select your Appliance > **Edit**.
-    		`}
-    		inline={false}
-    		/>
-    		</>
-    	)
-    	}
-    	<Markdown
-    	text={`
-    	4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
-    	5. Select the three dots next to it > **Edit application traffic**.
-    	6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
-    	7. Select **Save**.
-    	`}
-    	inline={false}
-    	/>
-    </>
-
+		`}
+		inline={false}
+		/>
+
+		{ props.dashName === "CF1 Cloudflare WAN" ? (
+			<>
+				<Markdown
+			text={`
+				1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
+				2. Go to **Connectors** > **Appliances** > **Profiles**.
+				3. Select the Cloudflare One Appliance you want to configure > **Edit**.
+			`}
+			inline={false}
+			/>
+			</>
+		) : (
+			<>
+			<Markdown
+				text={`
+					1. Go to the **Connectors** page.
+					`}
+				inline={false}
+				/>
+					<DashButton url="/?to=/:account/magic-networks/connections" />
+
+					<Markdown
+				text={`
+					2. Go to the **Appliances** tab > **Profiles**.
+					`}
+				inline={false}
+				/>
+				<Markdown
+			text={`
+				3. Select your Appliance > **Edit**.
+			`}
+			inline={false}
+			/>
+			</>
+		)
+		}
+		<Markdown
+		text={`
+		4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
+		5. Select the three dots next to it > **Edit application traffic**.
+		6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
+		7. Select **Save**.
+		`}
+		inline={false}
+		/>
+	</>
 )
 }
 
+
 {props.magicWord === "breakout" && (
-<>
-<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
-</>
-)
+	<>
+		<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
+	</>
+	)
 }
 
 { props.magicWord === "breakout" && (
-<>
-<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
-<Render
-file="mconn/network-options/app-aware-policies/warp-traffic"
-product="networking-services"
-params={{
+	<>
+	<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
+		<Render
+			file="mconn/network-options/app-aware-policies/warp-traffic"
+			product="networking-services"
+			params={{
 				warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 			}}
-/>
-</>
-)
-}
+			/>
+	</>
+	)
+}
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
index 126ebd7f08071e4..70f81778279f769 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
@@ -14,11 +14,7 @@ The Cloudflare One Appliance uses NetFlow v9 to export flow data for breakout tr
 
 ### Enable NetFlow exports
 
-<Render
-	file="account-id-api-key"
-	product="networking-services"
-	params={{ showSiteId: true }}
-/>
+<Render file="account-id-api-key" product="networking-services" params={{ showSiteId: true }} />
 
 1. Send a `PUT` request to the Netflow configuration endpoint for your site.
 2. In the JSON body request, you must include the `collector_ip` parameter. To export traffic statistics to Network Flow, use the IP address `162.159.65.1`. This is the only field required to enable the feature.
@@ -29,12 +25,11 @@ Minimal configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		collector_ip: "162.159.65.1",
+		"collector_ip": "162.159.65.1"
 	}}
 />
 
 3. You can customize the configuration by adding optional fields to the JSON payload. These fields include:
-
 - `collector_port`: The UDP port for the collector. The default is `2055`.
 - `sampling_rate`: The rate at which packets are sampled.
 - `active_timeout`: The timeout for active flows in seconds.
@@ -46,11 +41,11 @@ Full configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		collector_ip: "162.159.65.1",
-		collector_port: 2055,
-		sampling_rate: 100,
-		active_timeout: 60,
-		inactive_timeout: 30,
+		"collector_ip": "162.159.65.1",
+		"collector_port": 2055,
+		"sampling_rate": 100,
+		"active_timeout": 60,
+		"inactive_timeout": 30
 	}}
 />
 
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
index f3203bf58619f2c..1d2567a03ec9803 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
@@ -4,7 +4,7 @@ params:
   - appTypesGatewayURL
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Standard traffic policies match on network-layer attributes like IP addresses and port ranges. Application-aware policies go further — they identify traffic by the application generating it, so you can make routing and security decisions based on what the traffic is, not just where it is going.
 
@@ -19,4 +19,5 @@ With application-aware policies, you can:
 
 For details, refer to the following pages:
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
index 4ef40f59c1c2bc9..a00df21396023ca 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -5,14 +5,7 @@ params:
   - cfVsCoreDashNamingMwanCni
 ---
 
-import {
-	APIRequest,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
 
 DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, Cloudflare One Appliance (formerly Magic WAN Connector) forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
index 3a9c1d021abc578..94056a78a61e391 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
@@ -3,14 +3,7 @@ params:
   - dashName
 ---
 
-import {
-	APIRequest,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
 
 When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN Connector) can also act as a DHCP server in your network. To enable this feature:
 
diff --git a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
index dfd266a24e6682a..000cfd917c0229e 100644
--- a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
@@ -63,3 +63,4 @@ For step-by-step instructions to configure a LAN and supply a static NAT prefix,
 
 - <a href={props.hardConnectorURL}>Configure hardware Appliance</a>
 - <a href={props.virtualConnectorURL}>Configure Virtual Appliance</a>
+
diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
index 079bcbe7f92895c..6243e2b3a08d8e5 100644
--- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -5,14 +5,7 @@ params:
   - virtualConnectorURL
 ---
 
-import {
-	APIRequest,
-	DashButton,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-} from "~/components";
+import { APIRequest, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
 
 You can define policies in your Cloudflare One Appliance (formerly Magic WAN Connector) to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
index 22273d0546df33d..9509f4c9fe5a7d6 100644
--- a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
@@ -44,7 +44,7 @@ Blue represents directly-attached subnets, and red represents routed subnets.
 	`}
 </pre>
 
-<br />
+<br/>
 
 To add a routed subnet to your LAN, you need:
 
diff --git a/src/content/partials/networking-services/mconn/overview.mdx b/src/content/partials/networking-services/mconn/overview.mdx
index 0aaac9276dd0f51..7ac69fc4e47b806 100644
--- a/src/content/partials/networking-services/mconn/overview.mdx
+++ b/src/content/partials/networking-services/mconn/overview.mdx
@@ -19,4 +19,4 @@ Either option ensures the best possible connectivity to the closest Cloudflare n
 
 Review this section to learn how to configure and deploy {props.hardwareProductName}.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
index 3c1e9c89c2d55cc..1680225d6dfcefe 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
@@ -19,11 +19,7 @@ Cloudflare customers can inspect metrics for a specific Cloudflare One Appliance
 
 To find the information above and start troubleshooting your Cloudflare One Appliance:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 
 ### Performance analytics
 
@@ -37,11 +33,7 @@ In Performance analytics you can review your Cloudflare One Appliance's performa
 
 To access performance analytics:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **Performance analytics**.
 
 ### Port analytics
@@ -53,11 +45,7 @@ Port analytics gives you access to information related to the packets sent and r
 
 The dashboard provides this information for all active ports in your Cloudflare One Appliance. To access port analytics:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **Port analytics**.
 
 ### Event logs
@@ -83,22 +71,15 @@ Use Event logs to identify general patterns and changes over time. This is usefu
 
 To access event logs:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
-4. Select **Events**. 5. You can filter results by specific events, and by time.
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+4. Select **Events**.
+5. You can filter results by specific events, and by time.
 
 ### DHCP leasing
 
 The DHCP leasing section identifies DHCP assigned leases and their expiration dates. To access DHCP leasing:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **DHCP leasing**.
 
 ## Troubleshooting tips
diff --git a/src/content/partials/networking-services/mconn/vlan-tagging.mdx b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
index 787946548bcc7a4..d13dfd1e5a4f2a6 100644
--- a/src/content/partials/networking-services/mconn/vlan-tagging.mdx
+++ b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
@@ -17,4 +17,4 @@ Use VLAN ID <code>0</code> when:
 You can also configure subinterfaces on the {props.virtualConnectorName} by associating the network interface with a Port Group or Distributed Port Group trunk and specifying a VLAN ID in addition to the port associated with the network interface (VLAN ID <code>1</code>-<code>4094</code>).
 
 Refer to <Markdown text={props.url} /> for more information.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
index bce930a2152d57d..304d1616c387e6a 100644
--- a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
+++ b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
@@ -4,4 +4,4 @@ params:
   - dashName
 ---
 
-When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
+When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
index 5419d89b875b933..3bf575d2cf83e7d 100644
--- a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
+++ b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
@@ -11,4 +11,4 @@ You will receive the status of the advertisement for each prefix with the follow
 - **Delayed**: The prefix cannot currently be advertised but will attempt advertisement. After the prefix can be advertised, a new notification is sent with the updated status.
 - **Locked**: The prefix is locked and cannot be advertised.
 - **Could not Advertise**: Cloudflare was unable to advertise the prefix. This status can occur for multiple reasons, but usually occurs when you are not allowed to advertise a prefix.
-- **Error**: A general error occurred during prefix advertisement.
+- **Error**: A general error occurred during prefix advertisement.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
index 7b58e1a58a4bed2..0090ebe938488ea 100644
--- a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
+++ b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
@@ -17,19 +17,15 @@ After Magic Transit activates and your traffic flows through Cloudflare, Cloudfl
 The following diagrams illustrate this process:
 
 <Width size="large">
-	![The diagram shows the flow of traffic when you send flow data from your
-	network to Cloudflare for
-	analysis.](~/assets/images/network-flow/1-flowdata.png)
+	![The diagram shows the flow of traffic when you send flow data from your network to Cloudflare for analysis.](~/assets/images/network-flow/1-flowdata.png)
 </Width>
 
 <Width size="large">
-	![Cloudflare automatically notifies you when Cloudflare detects an attack
-	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
+	![Cloudflare automatically notifies you when Cloudflare detects an attack	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
 </Width>
 
 <Width size="large">
-	![You can create rules to activate Magic Transit automatically, to protect
-	your IP addresses from a DDoS
+	![You can create rules to activate Magic Transit automatically, to protect your IP addresses from a DDoS
 	attack.](~/assets/images/network-flow/3-flowdata.png)
 </Width>
 
diff --git a/src/content/partials/networking-services/mnm/faqs.mdx b/src/content/partials/networking-services/mnm/faqs.mdx
index b0208fe02c88cf2..b4a27eb520e6d6c 100644
--- a/src/content/partials/networking-services/mnm/faqs.mdx
+++ b/src/content/partials/networking-services/mnm/faqs.mdx
@@ -6,7 +6,7 @@ If you cannot find your answer here, refer to the [community page](https://commu
 
 ## I am getting an "Invalid account settings request body: account name format contains illegal characters or is not supported" error when trying to create a rule.
 
-This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
+This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 
diff --git a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
index 46c472367567090..cd765351f8a8f43 100644
--- a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
+++ b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Configure your router to export <GlossaryTooltip term="sFlow">sFlow</GlossaryTooltip> data to Cloudflare's network for analysis in Network Flow (formerly Magic Network Monitoring). sFlow is a network monitoring protocol that samples network traffic to provide visibility into your network's performance and traffic patterns.
 
diff --git a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
index c117433d7d663dc..4cbd7f7fa55f513 100644
--- a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
@@ -8,14 +8,14 @@ To use dynamic threshold rules, you must send NetFlow or sFlow data to Cloudflar
 
 ## Rule configuration fields
 
-| Field                  | Description                                                                                                                                                                                                                                                                                                                                              |
-| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                               |
-| **Rule type**          | zscore                                                                                                                                                                                                                                                                                                                                                   |
-| **Target**             | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                                          |
-| **Sensitivity**        | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic.                                                                                                                                                                             |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | zscore |
+| **Target** | Can be defined in either bits per second or packets per second. |
+| **Sensitivity** | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic. |
 | **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. Network Flow supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section.                                                                      |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section. |
 
 ## API documentation
 
@@ -33,4 +33,4 @@ Z = (X - μ) / σ
 
 - `X` = Current traffic value.
 - `μ` = Mean traffic value over the long window.
-- `σ` = Standard deviation over the long window.
+- `σ` = Standard deviation over the long window.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/overview.mdx b/src/content/partials/networking-services/mnm/rules/overview.mdx
index f604442b91f7228..64c496cc2672375 100644
--- a/src/content/partials/networking-services/mnm/rules/overview.mdx
+++ b/src/content/partials/networking-services/mnm/rules/overview.mdx
@@ -25,7 +25,7 @@ If you get the following error when trying to create a rule:
 
 `Invalid account settings request body: account name format contains illegal characters or is not supported`
 
-Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
+Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 :::
diff --git a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
index 2a6ee954fa33c84..cc8a9232c23298e 100644
--- a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
+++ b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Network Flow (formerly Magic Network Monitoring) can notify you by email, webhook, or PagerDuty when a rule is triggered. When a rule detects a traffic anomaly, notifications alert your team so you can respond — or, if you use Magic Transit with auto-advertisement, Cloudflare can begin mitigating the attack automatically.
 
@@ -16,19 +16,16 @@ For more information on the notification platform, refer to [Notifications docum
 
 ## Notification configuration fields
 
-| Field                      | Description                                                       |
-| :------------------------- | :---------------------------------------------------------------- |
-| **Notification name**      | A label to identify this notification in your notifications list. |
-| **Description (optional)** | The description of the notification.                              |
-| **Webhooks**               | One or more webhooks to deliver the notification to.              |
-| **Notification email**     | One or more email addresses to deliver the notification to.       |
+| Field | Description |
+| :---- | :---- |
+| **Notification name** | A label to identify this notification in your notifications list. |
+| **Description (optional)** | The description of the notification. |
+| **Webhooks** | One or more webhooks to deliver the notification to. |
+| **Notification email** | One or more email addresses to deliver the notification to. |
 
 ## Rule Auto-Advertisement notifications
 
-<Render
-	file="mnm-auto-advertisement-notifications"
-	product="networking-services"
-/>
+<Render file="mnm-auto-advertisement-notifications" product="networking-services" />
 
 ## Configure rule notifications
 
@@ -44,4 +41,4 @@ To configure notifications for Network Flow rules:
    - **Network Flow: Volumetric Attack** - for static threshold and dynamic threshold notifications
    - **Network Flow: DDoS Attack** - for sFlow DDoS attack notifications
 5. Fill in the notification configuration details.
-6. Select **Save**.
+6. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
index bec5f1386000a0d..b3e8a3d3bc9f6f8 100644
--- a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
+++ b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
@@ -12,13 +12,13 @@ To send sFlow data to Cloudflare, your router must support sFlow exports. Refer
 
 ## Rule configuration fields
 
-| Field                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                                                                                                                                                                                                              |
-| **Rule type**          | advanced_ddos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| **Prefix Match**       | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
-| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement).                                                                                                                                                                                                                                                  |
-| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes).                                                                                                                                                                                                                                                                    |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | advanced_ddos |
+| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
+| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement). |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes). |
 
 ## API documentation
 
@@ -26,4 +26,4 @@ Refer to the [Rules API documentation](/api/resources/magic_network_monitoring/s
 
 ## Tune the sFlow DDoS alert thresholds
 
-You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
+You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
index 6f3111db0f8feab..8f00ec41f108d69 100644
--- a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
@@ -10,15 +10,15 @@ To use static threshold rules, you must send NetFlow or sFlow data to Cloudflare
 
 ## Rule configuration fields
 
-| Field                   | Description                                                                                                                                                                                                                                                                                                                    |
-| :---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**           | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                     |
-| **Rule type**           | threshold                                                                                                                                                                                                                                                                                                                      |
-| **Rule threshold type** | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                |
-| **Rule threshold**      | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum.                                                                                                                                       |
-| **Rule duration**       | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes.                                                                                                                                         |
-| **Auto-advertisement**  | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
-| **Rule IP prefix**      | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes).                                                                                                          |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | threshold |
+| **Rule threshold type** | Can be defined in either bits per second or packets per second. |
+| **Rule threshold** | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum. |
+| **Rule duration** | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes. |
+| **Auto-advertisement** | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes). |
 
 ## API documentation
 
@@ -45,9 +45,9 @@ When you first configure Network Flow, you may not know the typical traffic patt
 This lets you collect baseline traffic data without receiving alerts. After configuring your initial rules, monitor for alerts and review traffic in Network Flow Analytics. Over time, update each rule's threshold based on historical traffic data.
 
 | Threshold type | Recommended rule threshold to collect initial data |
-| :------------- | :------------------------------------------------- |
-| Bits           | 10 Gbps (10,000,000,000 bits per second)           |
-| Packets        | 10 Mpps (10,000,000 packets per second)            |
+| :---- 				 | :---- 																						  |
+| Bits 					 | 10 Gbps (10,000,000,000 bits per second) 					|
+| Packets 			 | 10 Mpps (10,000,000 packets per second) 						|
 
 #### Setting the appropriate threshold
 
@@ -64,9 +64,9 @@ To find the maximum non-attack traffic for a one minute time interval over the p
 2. Select **Add filter**.
 3. In **New filter**, use the drop-down menus to create the following filter:
 
-| Field             | Operator | Rule name     |
-| :---------------- | :------- | :------------ |
-| _Monitoring Rule_ | _equals_ | `<RULE_NAME>` |
+| Field 						| Operator | Rule name 			|
+| :---- 						| :---- 	 | :---- 		 			|
+| _Monitoring Rule_ | _equals_ | `<RULE_NAME>`  |
 
 Once the rule filter is selected in Network Flow Analytics, you can check the historical traffic volume data for the rule over the selected time period. Cloudflare recommends reviewing historical data in seven-day increments, since that is the largest window that shows one-hour time intervals. To select a custom seven-day range, go to the top right corner of Network Flow analytics, open the time window drop-down menu, and select **Custom range**.
 
@@ -80,4 +80,4 @@ Your IP prefixes may experience inconsistent spikes across one-minute intervals.
 
 ### Adjusting rules over time
 
-After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
+After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
index 87ca7eb4eb1d41c..db70332705ae2dc 100644
--- a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
+++ b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
@@ -2,6 +2,7 @@
 {}
 ---
 
+
 import { GlossaryTooltip, DashButton } from "~/components";
 
 Use the GraphQL Analytics API to retrieve Network Flow (formerly Magic Network Monitoring) <GlossaryTooltip term="flow data">flow data</GlossaryTooltip>.
diff --git a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
index 2849ce921c3e6a5..1afc04ea7741587 100644
--- a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
+++ b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
@@ -6,7 +6,7 @@ Instructions to adjust MSS by applying MSS clamps vary depending on the vendor o
 
 The following table lists several commonly used router vendors with links to MSS clamping instructions:
 
-| Router device | URL                                                                                                                                                                                    |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Router device | URL |
+| ---					  | --- |
 | Cisco         | [TCP IP Adjust MSS](https://www.cisco.com/en/US/docs/ios-xml/ios/ipapp/command/ip_tcp_adjust-mss_through_ip_wccp_web-cache_accelerated.html#GUID-68044D35-A53E-42C1-A7AB-9236333DA8C4) |
-| Juniper       | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html)                                           |
+| Juniper | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html) |
diff --git a/src/content/partials/networking-services/reference/longest-prefix-match.mdx b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
index 98fb9a953cd67de..562deeae9654317 100644
--- a/src/content/partials/networking-services/reference/longest-prefix-match.mdx
+++ b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
+Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
index 660c84eea51122e..4b89061153d1dcb 100644
--- a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
+++ b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
@@ -4,14 +4,14 @@
 
 Cloudflare has nine geographic regions:
 
-| Region code | Region                |
-| ----------- | --------------------- |
-| `AFR`       | Africa                |
-| `APAC`      | Asia Pacific          |
-| `EEUR`      | Eastern Europe        |
-| `ENAM`      | Eastern North America |
-| `ME`        | Middle East           |
-| `OC`        | Oceania               |
-| `SAM`       | South America         |
-| `WEUR`      | Western Europe        |
-| `WNAM`      | Western North America |
+| Region code | Region |
+| ----- | ----- |
+| `AFR` | Africa |
+| `APAC` | Asia Pacific |
+| `EEUR` | Eastern Europe |
+| `ENAM` | Eastern North America |
+| `ME` | Middle East |
+| `OC` | Oceania |
+| `SAM` | South America |
+| `WEUR` | Western Europe |
+| `WNAM` | Western North America |
diff --git a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
index 666d6fb81f454a0..4dddd911617f979 100644
--- a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
+++ b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
@@ -21,8 +21,7 @@ A tunnel health check probe travels from Cloudflare to the tunnel origin, then r
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName:
-			props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN",
+		productName: props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN"
 	}}
 />
 
@@ -114,12 +113,12 @@ To avoid control plane policies enforced by the origin network, you can set tunn
 
 ### Summary table with tunnel health check probe types
 
-|      Attribute      |     Type      |        Unidirectional health checks        |                  Bidirectional health checks                  |
-| :-----------------: | :-----------: | :----------------------------------------: | :-----------------------------------------------------------: |
-|   Source Address    | Request Style |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
-| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-|   Source Address    |  Reply Style  | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-| Destination Address |  Reply Style  |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
+| Attribute 					| Type 					| Unidirectional health checks | Bidirectional health checks |
+| :---: 							| :---: 				| :---: 											 | :---: 											 |
+| Source Address 			| Request Style | Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
+| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) |Origin Interface Address (Privately Routable) / Custom Target |
+| Source Address 			| Reply Style		| Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+| Destination Address | Reply Style 	| Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
 
 ### Graphics summarizing health check types
 
@@ -224,10 +223,9 @@ accDescr: Shows the flow of a unidirectional echo reply health check from Cloudf
 	product="networking-services"
 	params={{
 		mFirewallName: "Cloudflare Network Firewall rules",
-		mFirewallURL:
-			"/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks",
+		mFirewallURL: "/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks"
 	}}
-/>
+	/>
 
 Every Cloudflare data center configured to process your traffic sends tunnel health check probes. The rate at which Cloudflare sends these probes varies based on tunnel and location. You can tune this rate on a per-tunnel basis by modifying the `health_check` rate with the <a href={props.changeHealthCheckRate}>API or the dashboard</a>. You can set the rate as _low_, _mid_, or _high_, with _mid_ being the default.
 
@@ -235,6 +233,7 @@ The actual rate formula considers the number of servers in a Cloudflare data cen
 
 When a probe attempt fails for a <a href={props.probeHealth}>healthy tunnel</a>, each server detecting the failure quickly probes up to two more times to obtain an accurate result. Cloudflare does the same if a tunnel has been down and probes start returning success. Because Cloudflare global network servers send probes up to every second, your network will receive several hundred health check packets per second. Each Cloudflare data center sends only one health check packet as part of a probe, representing a relatively trivial amount of traffic.
 
+
 ## Health state and prioritization
 
 There are three tunnel health states: healthy, degraded, and down.
@@ -306,4 +305,4 @@ Suppose the connectivity issue that set Tunnel 1 health to down becomes resolved
 
 When all three probes return successfully, {props.productName} transitions the tunnel from down to degraded. As part of this transition, Cloudflare reduces the priority penalty for that route so that its priority becomes `500,100`. Because Tunnel 2 has a priority of `200`, traffic continues to flow over Tunnel 2.
 
-Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
+Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/routing/anycast-warning.mdx b/src/content/partials/networking-services/routing/anycast-warning.mdx
index 581fa4d4006258c..4a70b0d9c18b322 100644
--- a/src/content/partials/networking-services/routing/anycast-warning.mdx
+++ b/src/content/partials/networking-services/routing/anycast-warning.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Anycast routing]
 Cloudflare uses anycast to route traffic. Anycast is a network addressing and routing method that routes incoming requests to different locations. Traffic can arrive at a different geographic location than expected. Not all requests go to the closest data center because Internet routing and peering relationships are complex, and Cloudflare optimizes for performance and reliability.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/routing/bgp-config-steps.mdx b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
index 49bffd5bd2831f1..ddf3fa73d94cc70 100644
--- a/src/content/partials/networking-services/routing/bgp-config-steps.mdx
+++ b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
@@ -10,16 +10,16 @@ import { Aside, Markdown } from "~/components";
 5. <Markdown text={props.locateText} />
 6. In **Customer device ASN**, enter the ASN for your network.
 
-   { props.magicWord !== "Magic Transit" && (
-   <>
-   <Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
-   </>
-   )
-   }
+	{ props.magicWord !== "Magic Transit" && (
+		<>
+		<Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
+		</>
+		)
+	}
 
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations and is not a security mechanism.
 8. (Optional) In **Additional Advertised prefix list**, input any additional prefixes you want to advertise alongside your existing routes. Leave this blank if you do not want to advertise extra routes. Typical prefixes to configure here include:
-   - A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
-   - A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
-     { props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
+	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
+	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
+	{ props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
 9. Select **Save**.
diff --git a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
index b45261be84bfb8e..2c65310f9047a4a 100644
--- a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
+++ b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
@@ -7,7 +7,6 @@ params:
 import { APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 You can configure the source IP address range used by Cloudflare whenever a Cloudflare service, such as Cloudflare Load Balancing, sends traffic to a Cloudflare One private network. This address range is referred to as the Cloudflare Source IP Prefix (or `cloudflare_source` subnet type in the API).
-
 - IPv4 traffic is sourced from `100.64.0.0/12`. This range is configurable.
 - IPv6 traffic is sourced from `2606:4700:cf1:5000::/64`. This range is not configurable.
 
@@ -26,7 +25,6 @@ You must configure routes in your network so that response traffic for these sou
 ## Prerequisites
 
 Before you begin, ensure that:
-
 - You have Cloudflare One <a href={props.unifiedRoutingLink}>Unified Routing (beta)</a>. If your account is not yet on Unified Routing, contact your account team to discuss migration and availability.
 - You have [Cloudflare One Networks Write](/fundamentals/api/reference/permissions/) permission.
 - Your desired new network range meets the following requirements:
diff --git a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
index d22d6e489c92663..17e4497d25e28e8 100644
--- a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
+++ b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
@@ -37,7 +37,7 @@ Choose this option if you have a single VPC in your cloud to connect to Cloudfla
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -74,7 +74,7 @@ When you configure a hub on-ramp, Cloudflare always manages the VPN tunnel betwe
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -105,7 +105,7 @@ You have successfully created your Cloudflare WAN on-ramp. However, on-ramp crea
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -156,7 +156,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, select **Add new on-ramp** and begin the **Create a Cloudflare WAN cloud on-ramp** workflow following the standard steps.
@@ -169,7 +169,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the on-ramp you want to download > select the three dots > **Download as Terraform**.
@@ -186,7 +186,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to edit.
@@ -203,7 +203,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to delete.
@@ -227,7 +227,7 @@ To override the defaults with custom prefixes:
 
 1. Go to the **Routes** page.
 
-   <DashButton url="/?to=/:account/magic-networks/routes" />
+	<DashButton url="/?to=/:account/magic-networks/routes" />
 
 2. Select **WAN configuration**.
 3. Scroll to **Propagated routes to cloud networks**.
@@ -244,7 +244,7 @@ You can view estimated costs associated with your cloud resources in the Cloudfl
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the cloud on-ramp for which you want to check the estimated costs > select the three dots > **Associated Resources**.
diff --git a/src/content/partials/networking-services/sites/sites-brief.mdx b/src/content/partials/networking-services/sites/sites-brief.mdx
index cea114893c8546c..b562aa89e9a4045 100644
--- a/src/content/partials/networking-services/sites/sites-brief.mdx
+++ b/src/content/partials/networking-services/sites/sites-brief.mdx
@@ -5,4 +5,4 @@ params:
 
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that Cloudflare notifies you when there are issues with the site's on-ramps.
 
-Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
+Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx
index ab902ad3cbb22b4..e49acf781ff2f8d 100644
--- a/src/content/partials/networking-services/sites/sites.mdx
+++ b/src/content/partials/networking-services/sites/sites.mdx
@@ -13,7 +13,6 @@ import { Markdown, Render, DashButton } from "~/components";
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to quickly check the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
 
 To use a site, start by setting up your on-ramps. On-ramps can be:
-
 - <a href={props.greIpsecTunnelsURL}>GRE or IPsec tunnels</a>
 - <a href={props.connectorURL}>{props.connectorName}</a>
 - Direct <a href={props.cniURL}>CNI link</a>
@@ -23,9 +22,9 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 ## Add a site
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview**, select **Add site**.
@@ -39,36 +38,35 @@ text={`
 		11. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
 		12. Select **Complete setup** to finish setting up your site.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-
-    	<Markdown
-    	text={`
-    	2. In **Network overview**, select **Add a site**.
-    	3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
-    	4. Select **Create and continue**.
-    	5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
-    	6. Select **Continue**.
-    	7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
-    	8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
-    	9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-    	10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
-    	11. Select **Complete setup** to finish setting up your site.
-    	`}
-    	inline={false}
-    />
-    </>
-
+		inline={false}
+	/>
+	<DashButton url="/?to=/:account/networking-insights/health" />
+
+		<Markdown
+		text={`
+		2. In **Network overview**, select **Add a site**.
+		3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
+		4. Select **Create and continue**.
+		5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
+		6. Select **Continue**.
+		7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
+		8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
+		9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
+		10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
+		11. Select **Complete setup** to finish setting up your site.
+		`}
+		inline={false}
+	/>
+	</>
 )
 }
 
@@ -84,13 +82,10 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 	params={{
 		instructions: "",
 		magicWord: props.magicWord,
-		networkOverviewPageName:
-			props.magicWord === "CF1 Cloudflare WAN"
-				? "Network visibility"
-				: "Network overview",
+		networkOverviewPageName: props.magicWord === "CF1 Cloudflare WAN" ? "Network visibility" : "Network overview",
 		magicTunnelHcsURL: props.magicTunnelHcsURL,
-		setGeoCoordinatesURL: "#set-geographic-coordinates",
-	}}
+		setGeoCoordinatesURL: "#set-geographic-coordinates"
+		}}
 />
 
 ---
@@ -100,9 +95,9 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 ### Add or remove on-ramps
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
@@ -110,32 +105,31 @@ text={`
 		5. Select **Add** to add a new on-ramp.
 		6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-
-    <DashButton url="/?to=/:account/networking-insights/health" />
+		inline={false}
+	/>
 
-    <Markdown
-    	text={`
-    	2. Go to **Network overview** > **Traffic overview**.
-    	3. Find your site > select the three dots in front of it > **Edit**.
-    	3. Select **On-ramps**.
-    	4. Select **Add** to add a new on-ramp.
-    	5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
-    	`}
-    	inline={false}
-    />
-    </>
+	<DashButton url="/?to=/:account/networking-insights/health" />
 
+	<Markdown
+		text={`
+		2. Go to **Network overview** > **Traffic overview**.
+		3. Find your site > select the three dots in front of it > **Edit**.
+		3. Select **On-ramps**.
+		4. Select **Add** to add a new on-ramp.
+		5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
+		`}
+		inline={false}
+	/>
+	</>
 )
 }
 
@@ -144,34 +138,36 @@ inline={false}
 If you add geographic coordinates to your site, it will appear in the Network map. To set up or edit geographic coordinates to an existing site:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to **Insights** > **Network visibility**.
 		2. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-<Markdown
-text={`
+		inline={false}
+	/>
+	<DashButton url="/?to=/:account/networking-insights/health" />
+		<Markdown
+		text={`
 		2. Go to **Network overview** > **Traffic overview**.
 		3. Find your site > select the three dots in front of it > **Edit**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 )
-} 3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates. 4. Select **Save**.
+}
+3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
+4. Select **Save**.
 
 ### Set thresholds for site health
 
@@ -180,6 +176,6 @@ inline={false}
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: props.magicTunnelHcsURL,
+		magicTunnelHcsURL: props.magicTunnelHcsURL
 	}}
 />
diff --git a/src/content/partials/networking-services/troubleshoot-connectivity.mdx b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
index 3c84b2a29e2bedd..9a288f95f8861fd 100644
--- a/src/content/partials/networking-services/troubleshoot-connectivity.mdx
+++ b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
@@ -74,7 +74,7 @@ You can identify which data centers handle your traffic by using **Network Analy
 
 1. Go to the **Network Analytics** page.
 
-   <DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
+	<DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
 
 2. Select **Add filter** and filter traffic by your source IP addresses to isolate your traffic.
 3. Under **Packets summary**, select the **Source data center** tab. If the tab is not visible, select the three-dot menu (`...`) to reveal additional view options and select **Source data center**.
@@ -112,13 +112,8 @@ If you have worked through this guide and cannot resolve the issue, gather the f
 
 ## Related resources
 
-- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve
-  common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
-- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose
-  routing and BGP issues that affect traffic delivery.
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
-  Monitor tunnel status per data center.
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
-  details on how health checks work.
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic
-  patterns over time.
+- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
+- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose routing and BGP issues that affect traffic delivery.
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Monitor tunnel status per data center.
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on how health checks work.
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic patterns over time.
diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
index f91d7cf6d89d54e..33f16ff7be38ee7 100644
--- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
+++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
@@ -8,13 +8,7 @@ params:
   - magicWord?
 ---
 
-import {
-	Aside,
-	AnchorHeading,
-	DashButton,
-	GlossaryTooltip,
-	Markdown,
-} from "~/components";
+import { Aside, AnchorHeading, DashButton, GlossaryTooltip, Markdown } from "~/components";
 
 The Cloudflare dashboard monitors the health of all <GlossaryTooltip term="anycast">anycast</GlossaryTooltip> tunnels on your account that route traffic from Cloudflare to your origin network.
 
@@ -29,9 +23,9 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 ## Check tunnel health
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
@@ -40,34 +34,33 @@ text={`
 			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
 		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    	<Markdown
-    		text={`
-    		1. Go to the **Network health** page.
-    			`}
-    		inline={false}
-    	/>
-
-    	<DashButton url="/?to=/:account/networking-insights/health" />
-
-    	<Markdown
-    		text={`
-    		2. Select the **Connector health** tab.
-    		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
-    		4. Find the tunnel you want to inspect, select the three dots next to it, and select:
-    			- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
-    			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
-    		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
-    		`}
-    		inline={false}
-    	/>
-    </>
-
+	<>
+
+		<Markdown
+			text={`
+			1. Go to the **Network health** page.
+				`}
+			inline={false}
+		/>
+
+		<DashButton url="/?to=/:account/networking-insights/health" />
+
+		<Markdown
+			text={`
+			2. Select the **Connector health** tab.
+			3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+			4. Find the tunnel you want to inspect, select the three dots next to it, and select:
+				- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
+				- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
+			5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
+			`}
+			inline={false}
+		/>
+	</>
 )
 }
 
@@ -76,50 +69,48 @@ inline={false}
 You can drill down into a specific tunnel to check its health status and other information.
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    <Markdown
-    		text={`
-    		1. Go to the **Network health** page.
-    			`}
-    		inline={false}
-    	/>
+	<>
 
-    <DashButton url="/?to=/:account/networking-insights/health" />
+	<Markdown
+			text={`
+			1. Go to the **Network health** page.
+				`}
+			inline={false}
+		/>
 
-    <Markdown
-    		text={`
+	<DashButton url="/?to=/:account/networking-insights/health" />
 
+	<Markdown
+			text={`
 2. Select the **Connector health** tab.
-   `}
-   inline={false}
-   />
-   </>
-   )
-   }
+			`}
+			inline={false}
+		/>
+	</>
+)
+}
+
 
 3. Find and select the tunnel you want to inspect.
 
 The next view displays detailed information about the tunnel, including:
-
 - Status information
-  - Up: More than 80% of health checks pass.
-  - Degraded: More than 40% of health checks pass.
-  - Down: Less than 40% of health checks pass.
+	- Up: More than 80% of health checks pass.
+	- Degraded: More than 40% of health checks pass.
+	- Down: Less than 40% of health checks pass.
 - Health checks passed in the last hour
 - Traffic volume in the last hour
 
 If you select the three dots in front of the tunnel you want to inspect, you have access to the following tools:
-
 - Packet captures: Collect <a href={props.packetCaptures}>packet level data for your traffic</a>
 - Network Analytics: Leverage real-time insights into <a href={props.networkAnalytics}>network analytics</a>.
diff --git a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
index 40f78d258f68ce4..7b2222fb7119eaf 100644
--- a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
+++ b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
@@ -5,4 +5,4 @@ params:
 
 :::note
 {props.productName} customers with [Customer Metadata Boundary](/data-localization/metadata-boundary/) enabled for the European Union can access GRE, IPsec, and CNI (Cloudflare Network Interconnect) health check and traffic volume data in the Cloudflare dashboard and through the API. This ensures that customers who need to be General Data Protection Regulation (GDPR) compliant can access all {props.productName} features.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
index a4314a796e274e0..d9eecdf681026ce 100644
--- a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
+++ b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
@@ -8,14 +8,14 @@ params:
 ---
 
 import {
-	APIRequest,
-	Code,
-	Details,
-	GlossaryTooltip,
-	Render,
-	Tabs,
-	TabItem,
-	DashButton,
+  APIRequest,
+  Code,
+  Details,
+  GlossaryTooltip,
+  Render,
+  Tabs,
+  TabItem,
+  DashButton,
 } from "~/components";
 
 You can configure Tunnel Health Alerts (formerly Magic Tunnel health alerts) to receive email, webhook, and PagerDuty notifications when the percentage of successful <GlossaryTooltip term="tunnel health-check">health checks</GlossaryTooltip> for an IPsec/GRE tunnel drops below the selected <a href={props.magicTunnelHealthCheckCalculation}>service-level objective (SLO)</a>.
@@ -42,14 +42,14 @@ Currently, there are seven SLO threshold values that you can configure through t
 The SLO threshold for Tunnel health alerts is the percentage of successful health checks for each IPsec/GRE tunnel in the alert:
 
 | Alert Sensitivity Level | SLO threshold |
-| ----------------------- | ------------- |
-| Minimum                 | 95.0          |
-| Very low                | 96.0          |
-| Low                     | 97.0          |
-| Medium                  | 98.0          |
-| High                    | 99.0          |
-| Very high               | 99.5          |
-| Maximum                 | 99.9          |
+| --- 										| --- 					|
+| Minimum 								| 95.0 					|
+| Very low 								| 96.0					|
+| Low 										| 97.0 					|
+| Medium 									| 98.0 					|
+| High 										| 99.0 					|
+| Very high 							| 99.5					|
+| Maximum 								| 99.9					|
 
 The time it takes to receive alerts depends on the sensitivity level you configure for your SLO thresholds. Higher sensitivity levels notify you faster when a tunnel's health degrades, but they may also trigger alerts for brief or minor disruptions. Lower sensitivity levels reduce the chance of false alarms but may delay notifications for less severe issues.
 
@@ -57,6 +57,7 @@ While the underlying detection timing remains consistent across sensitivity leve
 
 For details, refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Tunnel health alerts</a>.
 
+
 ## Set up Tunnel Health Alerts
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
index be3e95d154d505a..87ae557ab8ac1a5 100644
--- a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
@@ -5,4 +5,4 @@ params:
 
 Cloudflare One Appliance (formerly Magic WAN Connector) also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare through HTTPS and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
-Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
+Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
index a3df68499495d50..83373e4b20668f6 100644
--- a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
@@ -19,15 +19,15 @@ This guide helps you diagnose and resolve common tunnel health issues with {prop
 
 Use the following table to match your symptom to the most likely cause and first action:
 
-| Symptom                                           | Most likely cause                                         | First action                                                                                                                                        |
-| :------------------------------------------------ | :-------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Tunnel shows Down, never becomes healthy          | Configuration mismatch or firewall blocking IKE           | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures).                    |
-| Dashboard shows "100% degraded" for some colos    | Normal — this is a state indicator, not packet loss       | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard).              |
-| Tunnel flaps between healthy and unhealthy        | Anti-replay protection or rekey disruption                | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops).                      |
-| Health checks fail but traffic flows normally     | Stateful firewall dropping health check probes            | Change health check type from _Reply_ to _Request_. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
-| Health checks fail on policy-based VPN tunnels    | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
-| All tunnels degraded or down in a specific region | Network path issue between that region and your network   | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare.                                                          |
-| All tunnels degraded or down globally             | Issue at your network edge                                | Check your tunnel endpoint router and upstream connectivity.                                                                                        |
+| Symptom | Most likely cause | First action |
+| :------ | :---------------- | :----------- |
+| Tunnel shows Down, never becomes healthy | Configuration mismatch or firewall blocking IKE | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures). |
+| Dashboard shows "100% degraded" for some colos | Normal — this is a state indicator, not packet loss | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard). |
+| Tunnel flaps between healthy and unhealthy | Anti-replay protection or rekey disruption | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops). |
+| Health checks fail but traffic flows normally | Stateful firewall dropping health check probes | Change health check type from *Reply* to *Request*. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
+| Health checks fail on policy-based VPN tunnels | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
+| All tunnels degraded or down in a specific region | Network path issue between that region and your network | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare. |
+| All tunnels degraded or down globally | Issue at your network edge | Check your tunnel endpoint router and upstream connectivity. |
 
 ### What you can check
 
@@ -46,7 +46,7 @@ Use the following table to match your symptom to the most likely cause and first
 
 If you are experiencing tunnel health issues, check these items first:
 
-1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from _Reply_ to _Request_.
+1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from *Reply* to *Request*.
 2. **Anti-replay protection**: Disable anti-replay protection on your router, or set the replay window to `0`.
 3. **MTU settings**: Verify MTU is set correctly (typically `1476` for GRE, `1400`-`1450` for IPsec).
 4. **IPsec parameters**: Confirm your cryptographic parameters match <a href={props.tunnelsConfigLink}>Cloudflare's supported configuration</a>.
@@ -59,11 +59,11 @@ If you are experiencing tunnel health issues, check these items first:
 
 The [Network health](https://dash.cloudflare.com/?to=/:account/networking-insights/health) page in the Cloudflare dashboard displays three tunnel health states:
 
-| State        | Dashboard display                         | Technical threshold                                                |
-| :----------- | :---------------------------------------- | :----------------------------------------------------------------- |
-| **Healthy**  | More than 80% of health checks pass       | Less than 0.1% failure rate                                        |
+| State | Dashboard display | Technical threshold |
+| :---- | :---- | :---- |
+| **Healthy** | More than 80% of health checks pass | Less than 0.1% failure rate |
 | **Degraded** | Between 40% and 80% of health checks pass | At least 0.1% failures in last five minutes (minimum two failures) |
-| **Down**     | Less than 40% of health checks pass       | All health checks failed (at least three samples in last second)   |
+| **Down** | Less than 40% of health checks pass | All health checks failed (at least three samples in last second) |
 
 The dashboard shows tunnel health as measured from each Cloudflare data center where your traffic lands. It is normal to see some locations reporting degraded status due to Internet path issues. Focus on locations that show traffic in the **Traffic volume (1h)** column.
 
@@ -122,16 +122,16 @@ For instructions on monitoring tunnel status, refer to <a href={props.checkHealt
 
 **Health check type:**
 
-| Type                | Behavior                              | When to use                                                         |
-| :------------------ | :------------------------------------ | :------------------------------------------------------------------ |
-| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls                          |
-| **Request**         | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
+| Type | Behavior | When to use |
+| :---- | :---- | :---- |
+| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls |
+| **Request** | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
 
 **Health check direction:**
 
-| Direction          | Behavior                                              | Default for                          |
-| :----------------- | :---------------------------------------------------- | :----------------------------------- |
-| **Bidirectional**  | Probe and response both traverse the tunnel           | Cloudflare WAN (formerly Magic WAN)  |
+| Direction | Behavior | Default for |
+| :---- | :---- | :--- |
+| **Bidirectional** | Probe and response both traverse the tunnel | Cloudflare WAN (formerly Magic WAN) |
 | **Unidirectional** | Probe traverses tunnel; response returns via Internet | Magic Transit (direct server return) |
 
 :::note
@@ -152,23 +152,23 @@ Unidirectional health checks can be unreliable because intermediate network devi
 
 #### Cause
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP _Reply_ packets as health check probes.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP *Reply* packets as health check probes.
 
-Stateful firewalls inspect these packets and look for a matching ICMP _Request_ in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
+Stateful firewalls inspect these packets and look for a matching ICMP *Request* in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
 
 #### Solution
 
-Change the health check type from _Reply_ to _Request_:
+Change the health check type from *Reply* to *Request*:
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on the affected tunnel.
-3. Under **Health check type**, change from _Reply_ to _Request_.
+3. Under **Health check type**, change from *Reply* to *Request*.
 4. Select **Update tunnel**.
 
-When you use _Request_ style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
+When you use *Request* style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
 
 :::note
 If your firewall drops ICMP request packets as well, verify that your firewall policy permits ICMP traffic on the tunnel interface.
@@ -190,21 +190,21 @@ Cloudflare Network Firewall processes all traffic, including Cloudflare's health
 
 #### Solution
 
-Add an allow rule for ICMP traffic from Cloudflare IP addresses _before_ any block rules:
+Add an allow rule for ICMP traffic from Cloudflare IP addresses *before* any block rules:
 
 1. Go to the **Firewall policies** page.
 
-   <DashButton url="/?to=/:account/network-security/magic_firewall" />
+	<DashButton url="/?to=/:account/network-security/magic_firewall" />
 
 2. Create a new policy with the following parameters:
 
-| Field        | Value                                               |
-| :----------- | :-------------------------------------------------- |
-| **Action**   | Allow                                               |
-| **Protocol** | ICMP                                                |
-| **Source**   | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
+| Field | Value |
+| :---- | :---- |
+| **Action** | Allow |
+| **Protocol** | ICMP |
+| **Source** | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
 
-3. Position this rule _before_ any rules that block ICMP traffic.
+3. Position this rule *before* any rules that block ICMP traffic.
 
 For more information, refer to [Cloudflare Network Firewall rules and endpoint health checks](/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks).
 
@@ -246,7 +246,7 @@ Enable replay protection in the Cloudflare dashboard. This routes all tunnel tra
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on your IPsec tunnel.
 3. Enable **Replay protection**.
@@ -294,11 +294,13 @@ This behavior is expected and the tunnel will automatically recover. To minimize
 2. **Increase rekey intervals**: Configure longer SA lifetimes on your tunnel endpoint to reduce rekey frequency. Common values are 8-24 hours for IKE SA and 1-8 hours for IPsec SA.
 
 3. **Adjust health check sensitivity**: If brief degradation during rekeys triggers alerts, consider lowering the health check rate:
+
    1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
+
    2. In **IPsec/GRE tunnels**, select **Edit** on the tunnel.
-   3. Change **Health check rate** to _Low_.
+   3. Change **Health check rate** to *Low*.
 
 4. **Stagger rekey times**: If you have multiple tunnels, configure different SA lifetimes so they do not rekey simultaneously.
 
@@ -350,12 +352,12 @@ For detailed information on how bidirectional health checks work, refer to <a hr
 
 IPsec tunnel establishment can fail due to several configuration mismatches:
 
-| Issue                         | Symptom                                         |
-| :---------------------------- | :---------------------------------------------- |
+| Issue | Symptom |
+| :---- | :---- |
 | **Crypto parameter mismatch** | IKE negotiation fails with "no proposal chosen" |
-| **Incorrect PSK**             | Authentication failures in Phase 1              |
-| **Wrong IKE ID format**       | Authentication failures despite correct PSK     |
-| **Firewall blocking IKE**     | No IKE traffic reaches Cloudflare               |
+| **Incorrect PSK** | Authentication failures in Phase 1 |
+| **Wrong IKE ID format** | Authentication failures despite correct PSK |
+| **Firewall blocking IKE** | No IKE traffic reaches Cloudflare |
 
 #### Solution
 
@@ -363,22 +365,24 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 
    **Phase 1 (IKE)**
 
-| Parameter      | Supported values            |
-| :------------- | :-------------------------- |
-| IKE version    | IKEv2 only                  |
-| Encryption     | AES-GCM-16, AES-CBC-256     |
-| Authentication | SHA-256, SHA-384, SHA-512   |
-| DH Group       | DH group 14, 15, 16, 19, 20 |
 
-**Phase 2 (IPsec)**
+| Parameter | Supported values |
+| :---- | :---- |
+| IKE version | IKEv2 only |
+| Encryption | AES-GCM-16, AES-CBC-256 |
+| Authentication | SHA-256, SHA-384, SHA-512 |
+| DH Group | DH group 14, 15, 16, 19, 20 |
+
+   **Phase 2 (IPsec)**
 
-| Parameter      | Supported values            |
-| :------------- | :-------------------------- |
-| Encryption     | AES-GCM-16, AES-CBC-256     |
-| Authentication | SHA-256, SHA-512            |
-| PFS Group      | DH group 14, 15, 16, 19, 20 |
+| Parameter | Supported values |
+| :---- | :---- |
+| Encryption | AES-GCM-16, AES-CBC-256 |
+| Authentication | SHA-256, SHA-512 |
+| PFS Group | DH group 14, 15, 16, 19, 20 |
 
 2. **Verify the Pre-Shared Key (PSK):**
+
    - Regenerate the PSK in the Cloudflare dashboard
    - Copy the new PSK exactly (no extra spaces or characters)
    - Update your router with the new PSK
@@ -386,6 +390,7 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 3. **Check the IKE ID format:** Cloudflare uses FQDN format for the IKE ID. Ensure your router is configured to accept an FQDN peer identity. The FQDN is displayed in the tunnel details in the Cloudflare dashboard.
 
 4. **Verify firewall rules:** Ensure your edge firewall permits:
+
    - UDP port `500` (IKE)
    - UDP port `4500` (IKE NAT-T)
    - IP protocol `50` (ESP)
@@ -410,7 +415,7 @@ Additionally, some firewalls (such as Check Point) may flag Reply-style health c
 
 #### Solution
 
-1. Change the health check type from _Reply_ to _Request_.
+1. Change the health check type from *Reply* to *Request*.
 2. Configure a loopback address on your tunnel endpoint as the health check target. The target must be:
    - Routable from the tunnel endpoint
    - Covered by the tunnel's traffic selectors (encryption domain)
@@ -426,13 +431,13 @@ Policy-based tunnels use a separate Child SA for each set of traffic selectors.
 
 ### Common vendor-specific issues
 
-| Vendor                 | Common issue                             | Solution                                                   |
-| :--------------------- | :--------------------------------------- | :--------------------------------------------------------- |
-| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to _Request_; disable anti-replay |
-| **Cisco Meraki**       | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **AWS VPN Gateway**    | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **VeloCloud**          | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **Check Point**        | Out-of-state packet drops                | Change health check type to _Request_                      |
+| Vendor | Common issue | Solution |
+| :---- | :---- | :---- |
+| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to *Request*; disable anti-replay |
+| **Cisco Meraki** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **AWS VPN Gateway** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **VeloCloud** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **Check Point** | Out-of-state packet drops | Change health check type to *Request* |
 
 ---
 
@@ -479,13 +484,8 @@ Collect output from these commands (syntax varies by vendor):
 
 ## Resources
 
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
-  details on health check behavior
-- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay
-  must be disabled
-- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel
-  setup instructions
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
-  Dashboard navigation guide
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis
-  tools
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on health check behavior
+- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay must be disabled
+- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel setup instructions
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Dashboard navigation guide
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis tools
\ No newline at end of file
diff --git a/src/content/partials/networking-services/virtual-networks-concept.mdx b/src/content/partials/networking-services/virtual-networks-concept.mdx
index 5f791ebd1962872..bec7de23f758195 100644
--- a/src/content/partials/networking-services/virtual-networks-concept.mdx
+++ b/src/content/partials/networking-services/virtual-networks-concept.mdx
@@ -84,21 +84,18 @@ The same CIDR (`10.0.0.0/8`) can exist in each virtual network because they are
 
 Each virtual network maintains its own routing table. Routes added to one virtual network do not appear in another virtual network routing table. However, if traffic does not match a route in the selected virtual network, Cloudflare may fall back to the default virtual network routing table for WAN routes.
 
-<Markdown
-	text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`}
-	inline={false}
-/>
+<Markdown text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`} inline={false} />
 
 ## Virtual networks across Cloudflare
 
 Virtual network support varies by product:
 
-| Product               | Virtual network support   | Details                                                              |
-| --------------------- | ------------------------- | -------------------------------------------------------------------- |
-| Cloudflare Tunnel     | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
-| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection  |
-| Cloudflare Mesh       | Not currently supported   | —                                                                    |
-| Cloudflare WAN        | Default only              | All IPsec, GRE, and CNI connections use the default virtual network  |
+| Product | Virtual network support | Details |
+| --- | --- | --- |
+| Cloudflare Tunnel | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
+| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection |
+| Cloudflare Mesh | Not currently supported | — |
+| Cloudflare WAN | Default only | All IPsec, GRE, and CNI connections use the default virtual network |
 
 ## The default virtual network
 
@@ -123,26 +120,14 @@ If you are familiar with cloud networking concepts, a virtual network is analogo
 
 ## Create and manage virtual networks
 
-<Markdown
-	text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`}
-	inline={false}
-/>
+<Markdown text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`} inline={false} />
 
-<Markdown
-	text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`}
-	inline={false}
-/>
+<Markdown text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`} inline={false} />
 
-<Markdown
-	text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`}
-	inline={false}
-/>
+<Markdown text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`} inline={false} />
 
 ## Related resources
 
-<Markdown
-	text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
+<Markdown text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
 - [Routes](${props.routesURL}) — Define IP and hostname routes through your connectors
-- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`}
-	inline={false}
-/>
+- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`} inline={false} />
diff --git a/src/content/partials/notifications/get-started.mdx b/src/content/partials/notifications/get-started.mdx
index 829b54d50c6d7ad..00b7b4ec3a8f058 100644
--- a/src/content/partials/notifications/get-started.mdx
+++ b/src/content/partials/notifications/get-started.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Refer to [Cloudflare Notifications](/notifications/get-started/) for more information on how to set up an alert.
diff --git a/src/content/partials/pages/c3-adapter.mdx b/src/content/partials/pages/c3-adapter.mdx
index 32d2a3499fce337..a38fe66ad454db8 100644
--- a/src/content/partials/pages/c3-adapter.mdx
+++ b/src/content/partials/pages/c3-adapter.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If using [`create-cloudflare` (C3)](https://www.npmjs.com/package/create-cloudflare), you can bypass adding an adapter as C3 automatically installs any necessary adapters and configures them when creating your project.
 
+
 :::
diff --git a/src/content/partials/pages/c3-run-command-no-directory.mdx b/src/content/partials/pages/c3-run-command-no-directory.mdx
index 193d0bcd558150b..a64961aff54a926 100644
--- a/src/content/partials/pages/c3-run-command-no-directory.mdx
+++ b/src/content/partials/pages/c3-run-command-no-directory.mdx
@@ -4,8 +4,5 @@
 
 import { PackageManagers } from "~/components";
 
-<PackageManagers
-	type="create"
-	pkg="cloudflare@latest"
-	args="--platform=pages"
-/>
+<PackageManagers type="create" pkg="cloudflare@latest" args="--platform=pages"/>
+
diff --git a/src/content/partials/pages/cli-precedence-over-file.mdx b/src/content/partials/pages/cli-precedence-over-file.mdx
index b2bc3188eee261f..11a0cb2f0ebfdd4 100644
--- a/src/content/partials/pages/cli-precedence-over-file.mdx
+++ b/src/content/partials/pages/cli-precedence-over-file.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If a binding is specified in a [Wrangler configuration file](/workers/wrangler/configuration/) and via a command-line argument, the command-line argument takes precedence.
 
+
 :::
diff --git a/src/content/partials/pages/custom-domain-steps.mdx b/src/content/partials/pages/custom-domain-steps.mdx
index 20c18cb6fc838aa..fee5e4c0dbb152c 100644
--- a/src/content/partials/pages/custom-domain-steps.mdx
+++ b/src/content/partials/pages/custom-domain-steps.mdx
@@ -9,7 +9,6 @@ To add a custom domain:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Custom domains**.
 3. Select **Set up a domain**.
 4. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
index 953960ee01038c9..62859ea9b7e533e 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
@@ -9,7 +9,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
index b8561649554de9d..f70be8044a5cf71 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
@@ -10,7 +10,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/do-note.mdx b/src/content/partials/pages/do-note.mdx
index 6490baa6181c199..44f90d7ff7a4785 100644
--- a/src/content/partials/pages/do-note.mdx
+++ b/src/content/partials/pages/do-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You must create a Durable Object Worker and bind it to your Pages project using the Cloudflare dashboard or your Pages project's [Wrangler configuration file](/pages/functions/wrangler-configuration/). You cannot create and deploy a Durable Object within a Pages project.
diff --git a/src/content/partials/pages/framework-guides/create-gh-repo.mdx b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
index 8e6a0ec2e677e3a..7d4f7ac729dd198 100644
--- a/src/content/partials/pages/framework-guides/create-gh-repo.mdx
+++ b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Create a new GitHub repository by visiting [repo.new](https://repo.new). After creating a new repository, go to your newly created project directory to prepare and push your local application to GitHub by running the following commands in your terminal:
diff --git a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
index 9f8e802cee2e978..46eb8a378cb57e1 100644
--- a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
+++ b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Create a GitHub repository
diff --git a/src/content/partials/pages/framework-guides/git-integration.mdx b/src/content/partials/pages/framework-guides/git-integration.mdx
index ce38fa80e780d15..b904fe727721313 100644
--- a/src/content/partials/pages/framework-guides/git-integration.mdx
+++ b/src/content/partials/pages/framework-guides/git-integration.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Git integration
 
diff --git a/src/content/partials/pages/framework-guides/learn-more.mdx b/src/content/partials/pages/framework-guides/learn-more.mdx
index 875e06f11937b9d..412a7475b5f45d7 100644
--- a/src/content/partials/pages/framework-guides/learn-more.mdx
+++ b/src/content/partials/pages/framework-guides/learn-more.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: deployedTarget
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 ## Learn more
 
diff --git a/src/content/partials/pages/get-started-git-connect-pages.mdx b/src/content/partials/pages/get-started-git-connect-pages.mdx
index e2b68a6f9b7f3cc..9f0e08f89c4e2e7 100644
--- a/src/content/partials/pages/get-started-git-connect-pages.mdx
+++ b/src/content/partials/pages/get-started-git-connect-pages.mdx
@@ -9,17 +9,18 @@ Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitl
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Connect to Git**.
 
 You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/).
 
 :::note
 
+
 Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages.
 
 If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages.
 
+
 :::
 
 ### Select your GitHub repository
@@ -28,4 +29,4 @@ You can select a GitHub project from your personal account or an organization yo
 
 ### Select your GitLab repository
 
-If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
+If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
\ No newline at end of file
diff --git a/src/content/partials/pages/get-started-git-manage-site.mdx b/src/content/partials/pages/get-started-git-manage-site.mdx
index 6be5dbe386c0e10..0aa235c6ce61425 100644
--- a/src/content/partials/pages/get-started-git-manage-site.mdx
+++ b/src/content/partials/pages/get-started-git-manage-site.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments.
 
@@ -15,15 +15,16 @@ To delete your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings** > **Delete project**.
 
 :::caution
 
+
 For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions.
 
 For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings.
 
+
 :::
 
 ## Advanced project settings
@@ -32,6 +33,6 @@ In the **Settings** section, you can configure advanced settings, such as changi
 
 ## Related resources
 
-- Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
-- Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
-- Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
+* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
+* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
+* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
\ No newline at end of file
diff --git a/src/content/partials/pages/git-integration-warning.mdx b/src/content/partials/pages/git-integration-warning.mdx
index 29972cbf983d1e4..fe22fd4c858b9dd 100644
--- a/src/content/partials/pages/git-integration-warning.mdx
+++ b/src/content/partials/pages/git-integration-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Git integration]
 
+
 Currently, you cannot add Git integration to existing Pages applications. If you have already deployed your application, you need to create a new Pages application in order to add Git integration to it.
 
+
 :::
diff --git a/src/content/partials/pages/prod-branch-update.mdx b/src/content/partials/pages/prod-branch-update.mdx
index cc5195454fc9ea4..09fee36fe5dc103 100644
--- a/src/content/partials/pages/prod-branch-update.mdx
+++ b/src/content/partials/pages/prod-branch-update.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your project is a [Direct Upload](/pages/get-started/direct-upload/) project, you will not have the option to configure production branch controls. To update your production branch, you will need to manually call the [Update Project](/api/resources/pages/subresources/projects/methods/edit/) endpoint in the API.
diff --git a/src/content/partials/pages/tutorials-before-you-start.mdx b/src/content/partials/pages/tutorials-before-you-start.mdx
index 828e29a27d7e760..054f3014bbb4e20 100644
--- a/src/content/partials/pages/tutorials-before-you-start.mdx
+++ b/src/content/partials/pages/tutorials-before-you-start.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Before you continue
diff --git a/src/content/partials/pages/web-analytics-setup.mdx b/src/content/partials/pages/web-analytics-setup.mdx
index 5b7a79ede654b56..0c4d814773e0860 100644
--- a/src/content/partials/pages/web-analytics-setup.mdx
+++ b/src/content/partials/pages/web-analytics-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -7,7 +8,6 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Metrics** and select **Enable** under Web Analytics.
 
diff --git a/src/content/partials/queues/enable-queues.mdx b/src/content/partials/queues/enable-queues.mdx
index 2abc709865461de..5d055261c9dc78a 100644
--- a/src/content/partials/queues/enable-queues.mdx
+++ b/src/content/partials/queues/enable-queues.mdx
@@ -12,6 +12,6 @@ To enable Queues:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select **Enable Queues**.
diff --git a/src/content/partials/queues/event-subscriptions/access-events.mdx b/src/content/partials/queues/event-subscriptions/access-events.mdx
index 9f74f1279bcec9a..fc76184e339a0ed 100644
--- a/src/content/partials/queues/event-subscriptions/access-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/access-events.mdx
@@ -6,20 +6,20 @@ Triggered when an application is created.
 
 ```json
 {
-	"type": "cf.access.application.created",
-	"source": {
-		"type": "access"
-	},
-	"payload": {
-		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "My Application"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.access.application.created",
+  "source": {
+    "type": "access"
+  },
+  "payload": {
+    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "My Application"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when an application is deleted.
 
 ```json
 {
-	"type": "cf.access.application.deleted",
-	"source": {
-		"type": "access"
-	},
-	"payload": {
-		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "My Application"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.access.application.deleted",
+  "source": {
+    "type": "access"
+  },
+  "payload": {
+    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "My Application"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
index e25f2024c3d7d08..520d32a2d17b86f 100644
--- a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
@@ -8,27 +8,27 @@ Triggered when a repository is created.
 
 ```json
 {
-	"type": "cf.artifacts.repo.created",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "0tvugavnogssnwzk",
-		"defaultBranch": "main",
-		"description": "My Artifacts repository",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:46.833Z",
-		"updatedAt": "2026-05-18T15:53:46.833Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:48.187Z"
-	}
+  "type": "cf.artifacts.repo.created",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "0tvugavnogssnwzk",
+    "defaultBranch": "main",
+    "description": "My Artifacts repository",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:46.833Z",
+    "updatedAt": "2026-05-18T15:53:46.833Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:48.187Z"
+  }
 }
 ```
 
@@ -40,27 +40,27 @@ Triggered when a repository is deleted.
 
 ```json
 {
-	"type": "cf.artifacts.repo.deleted",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "0tvugavnogssnwzk",
-		"defaultBranch": "main",
-		"description": "My Artifacts repository",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:46.833Z",
-		"updatedAt": "2026-05-18T15:53:46.833Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:59.914Z"
-	}
+  "type": "cf.artifacts.repo.deleted",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "0tvugavnogssnwzk",
+    "defaultBranch": "main",
+    "description": "My Artifacts repository",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:46.833Z",
+    "updatedAt": "2026-05-18T15:53:46.833Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:59.914Z"
+  }
 }
 ```
 
@@ -72,29 +72,29 @@ Triggered when a repository is forked.
 
 ```json
 {
-	"type": "cf.artifacts.repo.forked",
-	"source": {
-		"type": "artifacts",
-		"namespace": "source-namespace",
-		"repoName": "source-repo"
-	},
-	"payload": {
-		"namespace": "target-namespace",
-		"repoName": "target-repo",
-		"repoId": "5ankv1vhl4xnw7wq",
-		"defaultBranch": "main",
-		"description": "Fork of source-repo",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:52.384Z",
-		"updatedAt": "2026-05-18T15:53:54.579Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:54.641Z"
-	}
+  "type": "cf.artifacts.repo.forked",
+  "source": {
+    "type": "artifacts",
+    "namespace": "source-namespace",
+    "repoName": "source-repo"
+  },
+  "payload": {
+    "namespace": "target-namespace",
+    "repoName": "target-repo",
+    "repoId": "5ankv1vhl4xnw7wq",
+    "defaultBranch": "main",
+    "description": "Fork of source-repo",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:52.384Z",
+    "updatedAt": "2026-05-18T15:53:54.579Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:54.641Z"
+  }
 }
 ```
 
@@ -106,29 +106,29 @@ Triggered when a repository is imported from an external Git remote.
 
 ```json
 {
-	"type": "cf.artifacts.repo.imported",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "d7nd72k964cv9kub",
-		"defaultBranch": "main",
-		"description": null,
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:54.864Z",
-		"updatedAt": "2026-05-18T15:53:57.737Z",
-		"lastPushAt": null,
-		"sourceUrl": "https://github.com/example/repo.git",
-		"branch": "main"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:58.195Z"
-	}
+  "type": "cf.artifacts.repo.imported",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "d7nd72k964cv9kub",
+    "defaultBranch": "main",
+    "description": null,
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:54.864Z",
+    "updatedAt": "2026-05-18T15:53:57.737Z",
+    "lastPushAt": null,
+    "sourceUrl": "https://github.com/example/repo.git",
+    "branch": "main"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:58.195Z"
+  }
 }
 ```
 
@@ -142,42 +142,44 @@ Triggered when commits are pushed to a repository.
 
 ```json
 {
-	"type": "cf.artifacts.repo.pushed",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"ref": "refs/heads/main",
-		"before": "abc123def456abc123def456abc123def456abc1",
-		"after": "def789ghi012def789ghi012def789ghi012def7",
-		"commits": [
-			{
-				"id": "def789ghi012def789ghi012def789ghi012def7",
-				"message": "Fix bug in authentication",
-				"messageTruncated": false,
-				"timestamp": "2025-05-01T02:48:57.000Z",
-				"author": {
-					"name": "Developer Name",
-					"email": "developer@example.com"
-				},
-				"committer": {
-					"name": "Developer Name",
-					"email": "developer@example.com"
-				},
-				"parents": ["abc123def456abc123def456abc123def456abc1"]
-			}
-		],
-		"totalCommitsCount": 1,
-		"commitsTruncated": false
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.artifacts.repo.pushed",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "ref": "refs/heads/main",
+    "before": "abc123def456abc123def456abc123def456abc1",
+    "after": "def789ghi012def789ghi012def789ghi012def7",
+    "commits": [
+      {
+        "id": "def789ghi012def789ghi012def789ghi012def7",
+        "message": "Fix bug in authentication",
+        "messageTruncated": false,
+        "timestamp": "2025-05-01T02:48:57.000Z",
+        "author": {
+          "name": "Developer Name",
+          "email": "developer@example.com"
+        },
+        "committer": {
+          "name": "Developer Name",
+          "email": "developer@example.com"
+        },
+        "parents": [
+          "abc123def456abc123def456abc123def456abc1"
+        ]
+      }
+    ],
+    "totalCommitsCount": 1,
+    "commitsTruncated": false
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -189,19 +191,19 @@ Triggered when a repository is cloned.
 
 ```json
 {
-	"type": "cf.artifacts.repo.cloned",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:51.358Z"
-	}
+  "type": "cf.artifacts.repo.cloned",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {},
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:51.358Z"
+  }
 }
 ```
 
@@ -213,19 +215,19 @@ Triggered when updates are fetched from a repository.
 
 ```json
 {
-	"type": "cf.artifacts.repo.fetched",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:51.358Z"
-	}
+  "type": "cf.artifacts.repo.fetched",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {},
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:51.358Z"
+  }
 }
 ```
 
@@ -237,23 +239,23 @@ Triggered when a repo-scoped token is created. Includes the token ID, scope, and
 
 ```json
 {
-	"type": "cf.artifacts.repo.token.created",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "default",
-		"repoName": "token-evt-repo"
-	},
-	"payload": {
-		"tokenId": "7ngdf3ww3u84t33x",
-		"scope": "read",
-		"expiresAt": "2026-05-20T16:58:14.548Z"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-20T16:58:14.548Z"
-	}
+  "type": "cf.artifacts.repo.token.created",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "default",
+    "repoName": "token-evt-repo"
+  },
+  "payload": {
+    "tokenId": "7ngdf3ww3u84t33x",
+    "scope": "read",
+    "expiresAt": "2026-05-20T16:58:14.548Z"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-20T16:58:14.548Z"
+  }
 }
 ```
 
@@ -265,20 +267,20 @@ Triggered when a repo-scoped token is revoked. Includes the token ID.
 
 ```json
 {
-	"type": "cf.artifacts.repo.token.revoked",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "default",
-		"repoName": "token-evt-repo"
-	},
-	"payload": {
-		"tokenId": "7ngdf3ww3u84t33x"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-20T16:58:14.548Z"
-	}
+  "type": "cf.artifacts.repo.token.revoked",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "default",
+    "repoName": "token-evt-repo"
+  },
+  "payload": {
+    "tokenId": "7ngdf3ww3u84t33x"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-20T16:58:14.548Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/kv-events.mdx b/src/content/partials/queues/event-subscriptions/kv-events.mdx
index e824a2a4d79909a..41f5c1399c2dda4 100644
--- a/src/content/partials/queues/event-subscriptions/kv-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/kv-events.mdx
@@ -6,20 +6,20 @@ Triggered when a namespace is created.
 
 ```json
 {
-	"type": "cf.kv.namespace.created",
-	"source": {
-		"type": "kv"
-	},
-	"payload": {
-		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "my-kv-namespace"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.kv.namespace.created",
+  "source": {
+    "type": "kv"
+  },
+  "payload": {
+    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "my-kv-namespace"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when a namespace is deleted.
 
 ```json
 {
-	"type": "cf.kv.namespace.deleted",
-	"source": {
-		"type": "kv"
-	},
-	"payload": {
-		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "my-kv-namespace"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.kv.namespace.deleted",
+  "source": {
+    "type": "kv"
+  },
+  "payload": {
+    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "my-kv-namespace"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/r2-events.mdx b/src/content/partials/queues/event-subscriptions/r2-events.mdx
index 30261e144e2610c..b50d8c3a1c19d49 100644
--- a/src/content/partials/queues/event-subscriptions/r2-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/r2-events.mdx
@@ -6,22 +6,22 @@ Triggered when a bucket is created.
 
 ```json
 {
-	"type": "cf.r2.bucket.created",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"jurisdiction": "default",
-		"location": "WNAM",
-		"storageClass": "Standard"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.r2.bucket.created",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "jurisdiction": "default",
+    "location": "WNAM",
+    "storageClass": "Standard"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -33,19 +33,19 @@ Triggered when a bucket is deleted.
 
 ```json
 {
-	"type": "cf.r2.bucket.deleted",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"jurisdiction": "default"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.r2.bucket.deleted",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "jurisdiction": "default"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
index 0cb885462b37f7b..4cae246e7055fa3 100644
--- a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
@@ -6,33 +6,33 @@ Triggered when a migration job starts.
 
 ```json
 {
-	"type": "cf.superSlurper.job.started",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"overwrite": true,
-		"pathPrefix": "migrations/",
-		"source": {
-			"provider": "s3",
-			"bucket": "source-bucket",
-			"region": "us-east-1",
-			"endpoint": "s3.amazonaws.com"
-		},
-		"destination": {
-			"provider": "r2",
-			"bucket": "destination-bucket",
-			"jurisdiction": "default"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.started",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "overwrite": true,
+    "pathPrefix": "migrations/",
+    "source": {
+      "provider": "s3",
+      "bucket": "source-bucket",
+      "region": "us-east-1",
+      "endpoint": "s3.amazonaws.com"
+    },
+    "destination": {
+      "provider": "r2",
+      "bucket": "destination-bucket",
+      "jurisdiction": "default"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -44,19 +44,19 @@ Triggered when a migration job pauses.
 
 ```json
 {
-	"type": "cf.superSlurper.job.paused",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.paused",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -68,19 +68,19 @@ Triggered when a migration job resumes.
 
 ```json
 {
-	"type": "cf.superSlurper.job.resumed",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.resumed",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -92,23 +92,23 @@ Triggered when a migration job finishes.
 
 ```json
 {
-	"type": "cf.superSlurper.job.completed",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"totalObjectsCount": 1000,
-		"skippedObjectsCount": 10,
-		"migratedObjectsCount": 980,
-		"failedObjectsCount": 10
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.completed",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "totalObjectsCount": 1000,
+    "skippedObjectsCount": 10,
+    "migratedObjectsCount": 980,
+    "failedObjectsCount": 10
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -120,23 +120,23 @@ Triggered when a migration job is manually aborted.
 
 ```json
 {
-	"type": "cf.superSlurper.job.aborted",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"totalObjectsCount": 1000,
-		"skippedObjectsCount": 100,
-		"migratedObjectsCount": 500,
-		"failedObjectsCount": 50
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.aborted",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "totalObjectsCount": 1000,
+    "skippedObjectsCount": 100,
+    "migratedObjectsCount": 500,
+    "failedObjectsCount": 50
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -148,19 +148,19 @@ Triggered when an object is migrated.
 
 ```json
 {
-	"type": "cf.superSlurper.job.object.migrated",
-	"source": {
-		"type": "superSlurper.job",
-		"jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"payload": {
-		"key": "migrations/file.txt"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.object.migrated",
+  "source": {
+    "type": "superSlurper.job",
+    "jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "payload": {
+    "key": "migrations/file.txt"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
index e9422149256d246..fbdfca03358751d 100644
--- a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
@@ -6,24 +6,24 @@ Triggered when an index is created.
 
 ```json
 {
-	"type": "cf.vectorize.index.created",
-	"source": {
-		"type": "vectorize"
-	},
-	"payload": {
-		"name": "my-vector-index",
-		"description": "Index for embeddings",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"modifiedAt": "2025-05-01T02:48:57.132Z",
-		"dimensions": 1536,
-		"metric": "cosine"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.vectorize.index.created",
+  "source": {
+    "type": "vectorize"
+  },
+  "payload": {
+    "name": "my-vector-index",
+    "description": "Index for embeddings",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "modifiedAt": "2025-05-01T02:48:57.132Z",
+    "dimensions": 1536,
+    "metric": "cosine"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -35,18 +35,18 @@ Triggered when an index is deleted.
 
 ```json
 {
-	"type": "cf.vectorize.index.deleted",
-	"source": {
-		"type": "vectorize"
-	},
-	"payload": {
-		"name": "my-vector-index"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.vectorize.index.deleted",
+  "source": {
+    "type": "vectorize"
+  },
+  "payload": {
+    "name": "my-vector-index"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
index c28ded25de74231..0353629c8d35492 100644
--- a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
@@ -6,20 +6,20 @@ Triggered when a batch request is queued.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.queued",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.queued",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,20 +31,20 @@ Triggered when a batch request has completed.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.succeeded",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.succeeded",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -56,22 +56,22 @@ Triggered when a batch request has failed.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.failed",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
-		"message": "Model execution failed",
-		"internalCode": 5001,
-		"httpCode": 500
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.failed",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
+    "message": "Model execution failed",
+    "internalCode": 5001,
+    "httpCode": 500
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
index c0f0508d1e6468e..5a30ffa88665135 100644
--- a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
@@ -6,39 +6,39 @@ Triggered when a build starts.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.started",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "running",
-		"buildOutcome": null,
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": null,
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.started",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "running",
+    "buildOutcome": null,
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": null,
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -50,39 +50,39 @@ Triggered when a build fails.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.failed",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "failed",
-		"buildOutcome": "failure",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:50:00.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.failed",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "failed",
+    "buildOutcome": "failure",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:50:00.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -94,39 +94,39 @@ Triggered when a build is canceled.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.canceled",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "canceled",
-		"buildOutcome": "canceled",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:49:30.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.canceled",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "canceled",
+    "buildOutcome": "canceled",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:49:30.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -138,38 +138,38 @@ Triggered when a build succeeds.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.succeeded",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "success",
-		"buildOutcome": "success",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:50:15.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.succeeded",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "success",
+    "buildOutcome": "success",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:50:15.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workflows-events.mdx b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
index 6c814481a6dbed4..3df38e1c77de3c5 100644
--- a/src/content/partials/queues/event-subscriptions/workflows-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
@@ -6,21 +6,21 @@ Triggered when an instance was created and is awaiting execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.queued",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.queued",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -32,21 +32,21 @@ Triggered when an instance starts or resumes execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.started",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.started",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -58,21 +58,21 @@ Triggered when an instance pauses execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.paused",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.paused",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -84,21 +84,21 @@ Triggered when an instance step throws an error.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.errored",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.errored",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -110,21 +110,21 @@ Triggered when an instance is manually terminated.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.terminated",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.terminated",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -136,20 +136,20 @@ Triggered when an instance finishes execution successfully.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.completed",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.completed",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/r2/custom-domain-steps.mdx b/src/content/partials/r2/custom-domain-steps.mdx
index 1b858090ebc584b..f5c65596995f046 100644
--- a/src/content/partials/r2/custom-domain-steps.mdx
+++ b/src/content/partials/r2/custom-domain-steps.mdx
@@ -7,7 +7,6 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Select **Settings**.
 4. Under **Custom Domains**, select **Add**.
diff --git a/src/content/partials/r2/link-to-workers-r2-api.mdx b/src/content/partials/r2/link-to-workers-r2-api.mdx
index 22e4c599d0521ab..c18ac02fda8ef0a 100644
--- a/src/content/partials/r2/link-to-workers-r2-api.mdx
+++ b/src/content/partials/r2/link-to-workers-r2-api.mdx
@@ -4,4 +4,4 @@
 
 ## Other resources
 
-For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
+For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
\ No newline at end of file
diff --git a/src/content/partials/r2/migrator-etag-caveat.mdx b/src/content/partials/r2/migrator-etag-caveat.mdx
index 134d0b7745e8eea..5b40fec510b86ec 100644
--- a/src/content/partials/r2/migrator-etag-caveat.mdx
+++ b/src/content/partials/r2/migrator-etag-caveat.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 While R2's ETag generation is compatible with S3's during the regular course of operations, ETags are not guaranteed to be equal when an object is migrated using {props.one}.
 {props.one} makes autonomous decisions about the operations it uses when migrating objects to optimize for performance and network usage. It may choose to migrate an object in multiple parts, which affects [ETag calculation](/r2/objects/upload-objects/#etags).
diff --git a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
index 1bdda7b3e476265..3767632424c95a7 100644
--- a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
@@ -1,13 +1,12 @@
 ---
 {}
----
 
+---
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
-
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/create-your-own-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/create-your-own-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
index f74bb9079e70dd4..c50d7c9cec90a22 100644
--- a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
@@ -1,13 +1,12 @@
 ---
 {}
----
 
+---
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
-
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/default-meeting-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/default-meeting-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
index 87e72e9cc2d11a8..59cb825253d7aa7 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
@@ -1,22 +1,21 @@
 ---
 {}
----
 
+---
 ```js
 await meeting.connectedMeetings.deleteMeetings([
-	"MEETING_ID_TO_CLOSE_1",
-	"MEETING_ID_TO_CLOSE_2",
+  "MEETING_ID_TO_CLOSE_1",
+  "MEETING_ID_TO_CLOSE_2",
 ]);
 ```
-
 This would also trigger `stateUpdate` event updating the list of breakout rooms & participants.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
-	console.log("stateUpdate", { meetings, parentMeeting });
+meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
+  console.log("stateUpdate", {meetings, parentMeeting});
 });
 
 // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
 console.log("Meetings List", meeting.connectedMeetings.meetings);
 console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
index 7c577d42c671773..f4af17e0a5883c0 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
@@ -1,20 +1,15 @@
 ---
 {}
----
 
+---
 ```js
 const breakoutRooms = await meeting.connectedMeetings.createMeetings([
-	{ title: "Breakout Room 1" },
-	{ title: "Breakout Room 2" },
-	{ title: "Breakout Room 3" },
+  { title: "Breakout Room 1" },
+  { title: "Breakout Room 2" },
+  { title: "Breakout Room 3" },
 ]);
 
-console.log(
-	"Created Breakout Rooms: ",
-	breakoutRooms
-		.map((room) => "Id:: " + room.id + " --- Title:: " + room.title)
-		.join("\n"),
-);
+console.log("Created Breakout Rooms: ", breakoutRooms.map((room) => "Id:: " + room.id + " --- Title:: " + room.title).join("\n"));
 ```
 
-`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
+`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
index 3047851f75d834f..dfde78c93ff676c 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
@@ -1,10 +1,10 @@
 ---
 {}
+
 ---
 
 ```js
-const breakoutRoomsInfo =
-	await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
 ```
 
 `breakoutRoomsInfo` is an object containing the list of breakout rooms and their participants, along with details of the parent meeting.
@@ -14,11 +14,11 @@ This data can be used to display the list of breakout rooms & participants in th
 You can also listen to `stateUpdate` event to get the latest list of breakout rooms & participants, as they are updated in real-time.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
-	console.log("stateUpdate", { meetings, parentMeeting });
+meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
+  console.log("stateUpdate", {meetings, parentMeeting});
 
-	// Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
-	console.log("Meetings List", meeting.connectedMeetings.meetings);
-	console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
+  // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
+  console.log("Meetings List", meeting.connectedMeetings.meetings);
+  console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
 });
 ```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
index f77df15d7e5faa7..e10a85c8c58bf11 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
@@ -1,16 +1,13 @@
 ---
 {}
+
 ---
 
 ```js
 // Listen to changingMeeting event to show a custom UI to indicate that a meeting switch is happening
 meeting.connectedMeetings.on("changingMeeting", (meetingId) => {
-	console.log(
-		"Switching to breakout room or main meeting with id: " + meetingId,
-	);
-	console.log(
-		"Show a Custom UI to indicate that a meeting switch is happening",
-	);
+	console.log("Switching to breakout room or main meeting with id: " + meetingId);
+	console.log("Show a Custom UI to indicate that a meeting switch is happening");
 });
 
 // Listen to meetingChanged event to update the meeting object reference
@@ -18,4 +15,4 @@ meeting.connectedMeetings.on("meetingChanged", (newMeeting) => {
 	console.log("Switched to breakout room or main meeting");
 	console.log("Every action now should be performed on this meeting");
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
index fbd4d918d2faf36..be50df93029763f 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
@@ -1,21 +1,20 @@
 ---
 {}
----
 
+---
 ```js
 // Retrieve list of breakout rooms & participants
-const breakoutRoomsInfo =
-	await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
 
 /*
- * You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
- * Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
- */
+* You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
+* Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
+*/
 
 // Move participants to breakout rooms
 const response = await meeting.connectedMeetings.moveParticipants(
-	"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-	"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-	["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
+  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+  ["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
 );
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
index 66e13a506f735ec..1491da6d62c305b 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
@@ -1,12 +1,11 @@
 ---
 {}
----
 
+---
 ```js
-const response =
-	await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
-		"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-		"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-		[{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
-	);
-```
+const response = await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
+  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+  [{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
+);
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
index 796eed925700f90..40805bd8dd7ae50 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
@@ -1,24 +1,20 @@
 ---
 {}
----
 
+---
 ```js
 // Check if breakout rooms are supported
-const areBreakoutRoomsSupported =
-	meeting.connectedMeetings.supportsConnectedMeetings;
+const areBreakoutRoomsSupported = meeting.connectedMeetings.supportsConnectedMeetings;
 
 // Check if any breakout rooms are already created
 const areBreakoutRoomsActive = meeting.connectedMeetings.isActive;
 
 // Check if the current participant has permission to create breakout rooms
-const hasPermissionToCreateBreakoutRooms =
-	meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
+const hasPermissionToCreateBreakoutRooms = meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
 
 // Check if the current participant has permission to switch to parent meeting
-const hasPermissionToSwitchToParentMeeting =
-	meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
+const hasPermissionToSwitchToParentMeeting = meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
 
 // Check if the current participant has permission to switch to connected meeting
-const hasPermissionToSwitchToConnectedMeeting =
-	meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
-```
+const hasPermissionToSwitchToConnectedMeeting = meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
index e3f7d0532664f23..7ecbc3317f46d23 100644
--- a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
+++ b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
@@ -1,417 +1,417 @@
 ---
 {}
----
 
+---
 ```json
 {
-	"about_call": "About Call",
-	"screen": "Screen",
-	"camera": "Camera",
-	"leave": "Leave",
-	"dismiss": "Dismiss",
-	"logo": "Logo",
-	"page": "Page",
-	"more": "More",
-	"page.prev": "Previous Page",
-	"page.next": "Next Page",
-	"layout": "Layout",
-	"layout.auto": "Auto Layout",
-	"settings": "Settings",
-	"file": "File",
-	"image": "Image",
-	"connection": "Connection",
-	"leave_confirmation": "Are you sure you want to leave the call?",
-	"cancel": "Cancel",
-	"yes": "Yes",
-	"(you)": "(you)",
-	"you": "You",
-	"everyone": "Everyone",
-	"to": "To",
-	"mute": "Mute",
-	"kick": "Kick",
-	"pin": "Pin",
-	"pinned": "Pinned",
-	"accept": "Accept",
-	"unpin": "Unpin",
-	"pip_on": "Show PiP",
-	"pip_off": "Hide PiP",
-	"viewers": "Viewers",
-	"join": "Join",
-	"joined": "Joined",
-	"create": "Create",
-	"close": "Close",
-	"ask": "Ask",
-	"type": "Type",
-	"activate": "Activate",
-	"requests": "Requests",
-	"mic_off": "Mic Off",
-	"disable_mic": "Disable Mic",
-	"mic_on": "Mic On",
-	"enable_mic": "Enable Mic",
-	"audio": "Audio",
-	"test": "Test",
-	"minimize": "Hide Tile",
-	"maximize": "Show Tile",
-	"mute_all": "Mute all",
-	"mute_all.description": "Everyone else in the meeting will be muted.",
-	"mute_all.header": "Are you sure?",
-	"mute_all.allow_unmute": "Allow others to unmute",
-	"video_off": "Video Off",
-	"disable_video": "Disable Video",
-	"video_on": "Video On",
-	"enable_video": "Enable Video",
-	"video": "Video",
-	"offline": "You're offline",
-	"offline.description": "Please ensure that you are connected to the internet.",
-	"disconnected": "You haven't joined the meeting.",
-	"failed": "You've been disconnected",
-	"failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
-	"disconnected.description": "Please join the meeting in order to see and interact with other participants.",
-	"participants": "Participants",
-	"participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
-	"participants.empty_list": "It looks like nobody is here.",
-	"participants.no_pending_requests": "There are no pending requests.",
-	"participants.turn_off_video": "Turn off video",
-	"polls": "Polls",
-	"polls.by": "Poll by",
-	"polls.question": "Poll Question",
-	"polls.question.placeholder": "What is your poll for?",
-	"polls.answers": "Answers",
-	"polls.option": "Add an option.",
-	"polls.option.placeholder": "Enter an option",
-	"polls.results.anon": "Anonymous",
-	"polls.results.hide": "Hide results before voting",
-	"polls.create": "Create Poll",
-	"polls.cancel": "Cancel Poll Creation",
-	"polls.empty": "No polls available",
-	"polls.errors.question_required": "Question is required.",
-	"polls.errors.empty_option": "Empty options not allowed.",
-	"screenshare": "Screen Share",
-	"screenshare.min_preview": "Minimize Preview",
-	"screenshare.max_preview": "Expand Preview",
-	"screenshare.shared": "Your screen is being shared.",
-	"screenshare.start": "Share Screen",
-	"screenshare.stop": "Stop Sharing",
-	"screenshare.error.unknown": "An error occurred while starting screenshare.",
-	"screenshare.error.max_count": "Maximum screen share limit reached.",
-	"plugins": "Plugins",
-	"perm_denied": "Permission denied by browser.",
-	"perm_denied.audio": "Mic Permission denied by browser",
-	"perm_denied.video": "Camera Permission denied by browser",
-	"perm_denied.screenshare": "Screenshare Permission denied by browser",
-	"perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
-	"perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
-	"perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
-	"perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
-	"perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
-	"perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
-	"perm_sys_denied": "Permission denied by system",
-	"perm_sys_denied.audio": "Mic permission denied by system",
-	"perm_sys_denied.video": "Camera permission denied by system",
-	"perm_sys_denied.screenshare": "Screenshare permission denied by system",
-	"perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
-	"perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
-	"perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
-	"perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
-	"perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
-	"perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
-	"perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
-	"perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
-	"perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
-	"perm_could_not_start": "Could not capture device.",
-	"perm_could_not_start.audio": "Unable to start your Microphone",
-	"perm_could_not_start.video": "Unable to start your Camera",
-	"perm_could_not_start.screenshare": "Unable to start your Screenshare",
-	"perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
-	"perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
-	"perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
-	"full_screen": "Full Screen",
-	"full_screen.exit": "Exit Full Screen",
-	"waitlist.header_title": "Waiting",
-	"waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
-	"waitlist.deny_request": "Deny request",
-	"waitlist.accept_request": "Accept request",
-	"waitlist.accept_all": "Accept all",
-	"stage_request.header_title": "Join Stage Requests",
-	"stage_request.deny_request": "Deny request",
-	"stage_request.accept_request": "Accept request",
-	"stage_request.accept_all": "Accept all",
-	"stage_request.deny_all": "Deny all",
-	"stage_request.approval_pending": "Pending",
-	"stage_request.denied": "Denied",
-	"stage_request.request": "Join stage",
-	"stage_request.requested": "Requested",
-	"stage_request.cancel_request": "Cancel request",
-	"stage_request.leave_stage": "Leave stage",
-	"stage_request.request_tip": "Request to join the discussion",
-	"stage_request.leave_tip": "Leave the stage",
-	"stage_request.pending_tip": "Request pending",
-	"stage_request.denied_tip": "Rejected request",
-	"stage.empty_host": "The stage is empty",
-	"stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
-	"stage.empty_viewer": "There is no one on stage",
-	"stage.remove_from_stage": "Remove from stage",
-	"stage.invited_notification": "has been invited to join stage.",
-	"stage.add_to_stage": "Invite to stage",
-	"stage.join_title": "Join Stage",
-	"stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
-	"stage.join_cancel": "Cancel",
-	"stage.join_confirm": "Join",
-	"setup_screen.join_in_as": "Joining as",
-	"setup_screen.your_name": "Your name",
-	"stage.reconnecting": "Reconnecting...",
-	"recording.label": "REC",
-	"recording.indicator": "This meeting is being recorded.",
-	"recording.started": "This meeting is being recorded.",
-	"recording.stopped": "Recording for this meeting has been stopped.",
-	"recording.paused": "Recording for this meeting has been paused.",
-	"recording.error.start": "Error while starting recording.",
-	"recording.error.stop": "Error while stopping recording",
-	"recording.error.resume": "Error while resuming recording",
-	"recording.start": "Start Recording",
-	"recording.stop": "Stop Recording",
-	"recording.resume": "Resume Recording",
-	"recording.starting": "Starting",
-	"recording.stopping": "Stopping",
-	"recording.loading": "Loading",
-	"recording.idle": "Record",
-	"audio_playback": "Play Audio",
-	"audio_playback.title": "Allow Audio Playback",
-	"audio_playback.description": "In order to play audio properly on your device, click the button below.",
-	"breakout_rooms": "Breakout Rooms",
-	"breakout_rooms.room_config_header": "Create Breakout",
-	"breakout_rooms.join_breakout_header": "Join Breakout",
-	"breakout_rooms.empty": "Nobody here yet.",
-	"breakout_rooms.delete": "Delete Room",
-	"breakout_rooms.switch": "Switch",
-	"breakout_rooms.main_room": "Main Room",
-	"breakout_rooms.shuffle_participants": "Shuffle Participants",
-	"breakout_rooms.deselect": "Deselect",
-	"breakout_rooms.selected": "selected",
-	"breakout_rooms.num_of_rooms": "No. of Rooms",
-	"breakout_rooms.approx": "Approx.",
-	"breakout_rooms.participants_per_room": "participants/room",
-	"breakout_rooms.division_text": "when equally divided.",
-	"breakout_rooms.start_breakout": "Start Breakout",
-	"breakout_rooms.close_breakout": "Close Breakout",
-	"breakout_rooms.update_breakout": "Update Breakout",
-	"breakout_rooms.discard_changes": "Discard Changes",
-	"breakout_rooms.room": "Room",
-	"breakout_rooms.rooms": "Rooms",
-	"breakout_rooms.room_name": "Room Name",
-	"breakout_rooms.edit_room_name": "Edit Room Name",
-	"breakout_rooms.save_room_name": "Save Room Name",
-	"breakout_rooms.add_room": "Add",
-	"breakout_rooms.add_room_brief": "Add Room",
-	"breakout_rooms.select_all": "Select all",
-	"breakout_rooms.unassign_all": "Unassign all",
-	"breakout_rooms.assign": "Assign",
-	"breakout_rooms.assign_participants": "Assign Participants",
-	"breakout_rooms.none_assigned": "No participants assigned yet",
-	"breakout_rooms.drag_drop_participants": "Drag and drop participants",
-	"breakout_rooms.click_drop_participants": "Click here to assign",
-	"breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
-	"breakout_rooms.status.select_room": "Select a room to assign",
-	"breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
-	"breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
-	"breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
-	"breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
-	"breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
-	"breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
-	"breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
-	"breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
-	"breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
-	"breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
-	"breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
-	"breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
-	"breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
-	"breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
-	"breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
-	"breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
-	"breakout_rooms.all_assigned": "All participants have been assigned",
-	"breakout_rooms.empty_main_room": "No more participants in the main room.",
-	"breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
-	"breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
-	"ai": "AI",
-	"ai.meeting_ai": "MeetingAI",
-	"ai.home": "Home",
-	"ai.transcriptions": "Transcriptions",
-	"ai.personal": "Personal",
-	"ai.caption_view": "Caption View",
-	"ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
-	"ai.chat.summarise": "Hey AI, summarise this call",
-	"ai.chat.agenda": "Hey AI, what is today's agenda?",
-	"search": "Search",
-	"search.could_not_find": "Couldn't find a participant with the specified name or ID.",
-	"search.empty": "It looks like nobody is here.",
-	"end": "End Meeting",
-	"end.all": "End meeting for all",
-	"ended": "The meeting ended.",
-	"ended.rejected": "Your request to join the meeting was denied.",
-	"ended.left": "You left the meeting.",
-	"ended.kicked": "You were removed from the meeting.",
-	"ended.disconnected": "The call ended because the connection was lost.",
-	"ended.network": "Please check your internet connection and try again.",
-	"ended.unauthorized": "You are not authorized to join this meeting.",
-	"network": "Network",
-	"network.reconnecting": "Connection lost. Trying to reconnect.",
-	"network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
-	"network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
-	"network.leaving": "Automatically leaving the meeting in 10 seconds.",
-	"network.restored": "Connection restored",
-	"network.delay": "Taking too long to reconnect.",
-	"network.lost": "Connection lost",
-	"network.lost_extended": "Connection lost. Please check your network connection.",
-	"livestream": "Livestream",
-	"livestream.indicator": "This meeting is being livestreamed.",
-	"livestream.skip": "Skip to Live",
-	"livestream.idle": "Waiting to go live.",
-	"livestream.starting": "Livestream is starting...",
-	"livestream.stopping": "Livestream is stopping...",
-	"livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
-	"livestream.error.not_supported": "Player not supported.",
-	"livestream.error.not_found": "Playback URL not found.",
-	"livestream.error.unknown": "An unknown error occurred.",
-	"livestream.error.sync": "Could not sync livestream please try again later.",
-	"livestream.error.start": "Error while starting livestream.",
-	"livestream.error.stop": "Error while stopping livestream.",
-	"livestream.go_live": "Go Live",
-	"livestream.end_live": "End Live",
-	"livestream.error": "Error",
-	"cta.help": "Need help on how to do this?",
-	"cta.continue": "Ignore",
-	"cta.reload": "Reload",
-	"cta.confirmation": "Are you sure?",
-	"cta.system_settings": "Open Settings",
-	"remote_access.empty": "There are no remote requests, yet.",
-	"remote_access.requests": "The following people have requested remote control to your screen share.",
-	"remote_access.allow": "Please select whom you want to give access to.",
-	"remote_access.grant": "Grant access",
-	"remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
-	"chat": "Chat",
-	"chat.new": "New",
-	"chat.max_limit_warning": "Max Character Limit",
-	"chat.rate_limit_error": "Please wait before you can send another message",
-	"chat.new_channel": "Create new channel",
-	"chat.channel_name": "Enter channel name",
-	"chat.member_name": "Enter member name",
-	"chat.add_members": "Add members",
-	"chat.delete_msg": "Delete",
-	"chat.edit_msg": "Edit",
-	"chat.send_msg": "Send message",
-	"chat.send_attachment": "Drop files/images to send",
-	"chat.send_img": "Send an image",
-	"chat.send_file": "Send a file",
-	"chat.send_emoji": "Send an emoji",
-	"chat.update_msg": "Update message",
-	"chat.channel_members": "Channel Members",
-	"chat.img.loading": "Loading image",
-	"chat.error.img_not_found": "Image not found",
-	"chat.error.empty_results": "Couldn't find a member with the specified name.",
-	"chat.img.shared_by": "Shared by",
-	"chat.reply": "Reply",
-	"chat.message_placeholder": "Message..",
-	"chat.click_to_send": "Click to send as message",
-	"chat.search_msgs": "Search messages",
-	"chat.search_conversations": "Search conversations",
-	"chat.start_conversation": "Start a conversation..",
-	"chat.empty_search": "No messages found",
-	"chat.empty_channel": "Send a message to get started",
-	"chat.cancel_upload": "Cancel upload",
-	"chat.view_chats": "View chats",
-	"chat.everyone": "everyone",
-	"chat.pinned_msgs": "Pinned messages",
-	"chat.toggle_pinned_msgs": "Toggle pinned messages",
-	"date.today": "Today",
-	"date.yesterday": "Yesterday",
-	"date.sunday": "Sunday",
-	"date.monday": "Monday",
-	"date.tuesday": "Tuesday",
-	"date.wednesday": "Wednesday",
-	"date.thursday": "Thursday",
-	"date.friday": "Friday",
-	"date.saturday": "Saturday",
-	"list.empty": "No items found",
-	"grid.listening": "Listening",
-	"transcript.off": "Turn off Transcripts",
-	"transcript.on": "Turn on Transcripts",
-	"settings.notification_sound": "Notification sound",
-	"settings.microphone_input": "Microphone",
-	"settings.speaker_output": "Speaker",
-	"settings.mirror_video": "Mirror my Video",
-	"settings.camera_off": "Camera is off",
-	"dialog.close": "Close dialog",
-	"notifications.joined": "just joined",
-	"notifications.left": "left",
-	"notifications.requesting_to_join_meeting": "is requesting to join the meeting",
-	"notifications.requested_to_join_stage": "has requested to join stage",
-	"notifications.joined_stage": "has joined stage",
-	"notifications.request_to_join_accepted": "Request to join accepted",
-	"notifications.request_to_join_rejected": "Request to join rejected",
-	"notifications.accept": "Accept",
-	"notifications.new_poll_created_by": "New poll created by",
-	"notifications.connected_to": "Connected to",
-	"notifications.plugin_switched_to": "Plugin switched to",
-	"notifications.remote_control_requested": "has requested for remote control",
-	"notifications.remote_control_request_sent": "Sent remote control request to",
-	"notifications.remote_control_request_accepted": "has granted remote control",
-	"notifications.remote_control_granted": "Granted remote control to",
-	"notifications.remote_control_terminated": "Existing remote control has been terminated",
-	"debugger.troubleshooting.label": "Troubleshooting",
-	"debugger.quality.good": "Good",
-	"debugger.quality.average": "Average",
-	"debugger.quality.poor": "Poor",
-	"debugger.stats.bitrate.label": "Bitrate",
-	"debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
-	"debugger.stats.packet_loss.label": "Packet Loss",
-	"debugger.stats.packet_loss.description": "Amount of data lost during transfer",
-	"debugger.stats.jitter.label": "Jitter",
-	"debugger.stats.jitter.description": "Variance or fluctuation in latency",
-	"debugger.stats.cpu_limitations.label": "CPU Limitations",
-	"debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
-	"debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
-	"debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
-	"debugger.audio.label": "Audio",
-	"debugger.audio.troubleshooting.label": "Audio Troubleshooting",
-	"debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.audio.messages.enable_media": "Please enable mic to see the report.",
-	"debugger.audio.sections.network_media": "Network & Media",
-	"debugger.video.label": "Video",
-	"debugger.video.troubleshooting.label": "Video Troubleshooting",
-	"debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.video.messages.enable_media": "Please enable camera to see the report.",
-	"debugger.video.sections.network_media": "Network & Media",
-	"debugger.screenshare.label": "Screenshare",
-	"debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
-	"debugger.screenshare.sections.network_media": "Network & Media",
-	"debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
-	"debugger.system.label": "System",
-	"debugger.system.troubleshooting.label": "System Troubleshooting",
-	"debugger.system.sections.battery": "Battery",
-	"debugger.system.battery.level.label": "Battery Level",
-	"debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
-	"debugger.system.battery.charging.label": "Battery Charging Status",
-	"debugger.system.battery.charging.description": "A device running on power performs optimally.",
-	"debugger.system.battery.charging.is_charging": "Charging",
-	"debugger.system.battery.charging.is_not_charging": "Not charging"
+  "about_call": "About Call",
+  "screen": "Screen",
+  "camera": "Camera",
+  "leave": "Leave",
+  "dismiss": "Dismiss",
+  "logo": "Logo",
+  "page": "Page",
+  "more": "More",
+  "page.prev": "Previous Page",
+  "page.next": "Next Page",
+  "layout": "Layout",
+  "layout.auto": "Auto Layout",
+  "settings": "Settings",
+  "file": "File",
+  "image": "Image",
+  "connection": "Connection",
+  "leave_confirmation": "Are you sure you want to leave the call?",
+  "cancel": "Cancel",
+  "yes": "Yes",
+  "(you)": "(you)",
+  "you": "You",
+  "everyone": "Everyone",
+  "to": "To",
+  "mute": "Mute",
+  "kick": "Kick",
+  "pin": "Pin",
+  "pinned": "Pinned",
+  "accept": "Accept",
+  "unpin": "Unpin",
+  "pip_on": "Show PiP",
+  "pip_off": "Hide PiP",
+  "viewers": "Viewers",
+  "join": "Join",
+  "joined": "Joined",
+  "create": "Create",
+  "close": "Close",
+  "ask": "Ask",
+  "type": "Type",
+  "activate": "Activate",
+  "requests": "Requests",
+  "mic_off": "Mic Off",
+  "disable_mic": "Disable Mic",
+  "mic_on": "Mic On",
+  "enable_mic": "Enable Mic",
+  "audio": "Audio",
+  "test": "Test",
+  "minimize": "Hide Tile",
+  "maximize": "Show Tile",
+  "mute_all": "Mute all",
+  "mute_all.description": "Everyone else in the meeting will be muted.",
+  "mute_all.header": "Are you sure?",
+  "mute_all.allow_unmute": "Allow others to unmute",
+  "video_off": "Video Off",
+  "disable_video": "Disable Video",
+  "video_on": "Video On",
+  "enable_video": "Enable Video",
+  "video": "Video",
+  "offline": "You're offline",
+  "offline.description": "Please ensure that you are connected to the internet.",
+  "disconnected": "You haven't joined the meeting.",
+  "failed": "You've been disconnected",
+  "failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
+  "disconnected.description": "Please join the meeting in order to see and interact with other participants.",
+  "participants": "Participants",
+  "participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
+  "participants.empty_list": "It looks like nobody is here.",
+  "participants.no_pending_requests": "There are no pending requests.",
+  "participants.turn_off_video": "Turn off video",
+  "polls": "Polls",
+  "polls.by": "Poll by",
+  "polls.question": "Poll Question",
+  "polls.question.placeholder": "What is your poll for?",
+  "polls.answers": "Answers",
+  "polls.option": "Add an option.",
+  "polls.option.placeholder": "Enter an option",
+  "polls.results.anon": "Anonymous",
+  "polls.results.hide": "Hide results before voting",
+  "polls.create": "Create Poll",
+  "polls.cancel": "Cancel Poll Creation",
+  "polls.empty": "No polls available",
+  "polls.errors.question_required": "Question is required.",
+  "polls.errors.empty_option": "Empty options not allowed.",
+  "screenshare": "Screen Share",
+  "screenshare.min_preview": "Minimize Preview",
+  "screenshare.max_preview": "Expand Preview",
+  "screenshare.shared": "Your screen is being shared.",
+  "screenshare.start": "Share Screen",
+  "screenshare.stop": "Stop Sharing",
+  "screenshare.error.unknown": "An error occurred while starting screenshare.",
+  "screenshare.error.max_count": "Maximum screen share limit reached.",
+  "plugins": "Plugins",
+  "perm_denied": "Permission denied by browser.",
+  "perm_denied.audio": "Mic Permission denied by browser",
+  "perm_denied.video": "Camera Permission denied by browser",
+  "perm_denied.screenshare": "Screenshare Permission denied by browser",
+  "perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
+  "perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
+  "perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
+  "perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
+  "perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
+  "perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
+  "perm_sys_denied": "Permission denied by system",
+  "perm_sys_denied.audio": "Mic permission denied by system",
+  "perm_sys_denied.video": "Camera permission denied by system",
+  "perm_sys_denied.screenshare": "Screenshare permission denied by system",
+  "perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
+  "perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
+  "perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
+  "perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
+  "perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
+  "perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
+  "perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
+  "perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
+  "perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
+  "perm_could_not_start": "Could not capture device.",
+  "perm_could_not_start.audio": "Unable to start your Microphone",
+  "perm_could_not_start.video": "Unable to start your Camera",
+  "perm_could_not_start.screenshare": "Unable to start your Screenshare",
+  "perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
+  "perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
+  "perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
+  "full_screen": "Full Screen",
+  "full_screen.exit": "Exit Full Screen",
+  "waitlist.header_title": "Waiting",
+  "waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
+  "waitlist.deny_request": "Deny request",
+  "waitlist.accept_request": "Accept request",
+  "waitlist.accept_all": "Accept all",
+  "stage_request.header_title": "Join Stage Requests",
+  "stage_request.deny_request": "Deny request",
+  "stage_request.accept_request": "Accept request",
+  "stage_request.accept_all": "Accept all",
+  "stage_request.deny_all": "Deny all",
+  "stage_request.approval_pending": "Pending",
+  "stage_request.denied": "Denied",
+  "stage_request.request": "Join stage",
+  "stage_request.requested": "Requested",
+  "stage_request.cancel_request": "Cancel request",
+  "stage_request.leave_stage": "Leave stage",
+  "stage_request.request_tip": "Request to join the discussion",
+  "stage_request.leave_tip": "Leave the stage",
+  "stage_request.pending_tip": "Request pending",
+  "stage_request.denied_tip": "Rejected request",
+  "stage.empty_host": "The stage is empty",
+  "stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
+  "stage.empty_viewer": "There is no one on stage",
+  "stage.remove_from_stage": "Remove from stage",
+  "stage.invited_notification": "has been invited to join stage.",
+  "stage.add_to_stage": "Invite to stage",
+  "stage.join_title": "Join Stage",
+  "stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
+  "stage.join_cancel": "Cancel",
+  "stage.join_confirm": "Join",
+  "setup_screen.join_in_as": "Joining as",
+  "setup_screen.your_name": "Your name",
+  "stage.reconnecting": "Reconnecting...",
+  "recording.label": "REC",
+  "recording.indicator": "This meeting is being recorded.",
+  "recording.started": "This meeting is being recorded.",
+  "recording.stopped": "Recording for this meeting has been stopped.",
+  "recording.paused": "Recording for this meeting has been paused.",
+  "recording.error.start": "Error while starting recording.",
+  "recording.error.stop": "Error while stopping recording",
+  "recording.error.resume": "Error while resuming recording",
+  "recording.start": "Start Recording",
+  "recording.stop": "Stop Recording",
+  "recording.resume": "Resume Recording",
+  "recording.starting": "Starting",
+  "recording.stopping": "Stopping",
+  "recording.loading": "Loading",
+  "recording.idle": "Record",
+  "audio_playback": "Play Audio",
+  "audio_playback.title": "Allow Audio Playback",
+  "audio_playback.description": "In order to play audio properly on your device, click the button below.",
+  "breakout_rooms": "Breakout Rooms",
+  "breakout_rooms.room_config_header": "Create Breakout",
+  "breakout_rooms.join_breakout_header": "Join Breakout",
+  "breakout_rooms.empty": "Nobody here yet.",
+  "breakout_rooms.delete": "Delete Room",
+  "breakout_rooms.switch": "Switch",
+  "breakout_rooms.main_room": "Main Room",
+  "breakout_rooms.shuffle_participants": "Shuffle Participants",
+  "breakout_rooms.deselect": "Deselect",
+  "breakout_rooms.selected": "selected",
+  "breakout_rooms.num_of_rooms": "No. of Rooms",
+  "breakout_rooms.approx": "Approx.",
+  "breakout_rooms.participants_per_room": "participants/room",
+  "breakout_rooms.division_text": "when equally divided.",
+  "breakout_rooms.start_breakout": "Start Breakout",
+  "breakout_rooms.close_breakout": "Close Breakout",
+  "breakout_rooms.update_breakout": "Update Breakout",
+  "breakout_rooms.discard_changes": "Discard Changes",
+  "breakout_rooms.room": "Room",
+  "breakout_rooms.rooms": "Rooms",
+  "breakout_rooms.room_name": "Room Name",
+  "breakout_rooms.edit_room_name": "Edit Room Name",
+  "breakout_rooms.save_room_name": "Save Room Name",
+  "breakout_rooms.add_room": "Add",
+  "breakout_rooms.add_room_brief": "Add Room",
+  "breakout_rooms.select_all": "Select all",
+  "breakout_rooms.unassign_all": "Unassign all",
+  "breakout_rooms.assign": "Assign",
+  "breakout_rooms.assign_participants": "Assign Participants",
+  "breakout_rooms.none_assigned": "No participants assigned yet",
+  "breakout_rooms.drag_drop_participants": "Drag and drop participants",
+  "breakout_rooms.click_drop_participants": "Click here to assign",
+  "breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
+  "breakout_rooms.status.select_room": "Select a room to assign",
+  "breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
+  "breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
+  "breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
+  "breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
+  "breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
+  "breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
+  "breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
+  "breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
+  "breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
+  "breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
+  "breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
+  "breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
+  "breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
+  "breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
+  "breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
+  "breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
+  "breakout_rooms.all_assigned": "All participants have been assigned",
+  "breakout_rooms.empty_main_room": "No more participants in the main room.",
+  "breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
+  "breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
+  "ai": "AI",
+  "ai.meeting_ai": "MeetingAI",
+  "ai.home": "Home",
+  "ai.transcriptions": "Transcriptions",
+  "ai.personal": "Personal",
+  "ai.caption_view": "Caption View",
+  "ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
+  "ai.chat.summarise": "Hey AI, summarise this call",
+  "ai.chat.agenda": "Hey AI, what is today's agenda?",
+  "search": "Search",
+  "search.could_not_find": "Couldn't find a participant with the specified name or ID.",
+  "search.empty": "It looks like nobody is here.",
+  "end": "End Meeting",
+  "end.all": "End meeting for all",
+  "ended": "The meeting ended.",
+  "ended.rejected": "Your request to join the meeting was denied.",
+  "ended.left": "You left the meeting.",
+  "ended.kicked": "You were removed from the meeting.",
+  "ended.disconnected": "The call ended because the connection was lost.",
+  "ended.network": "Please check your internet connection and try again.",
+  "ended.unauthorized": "You are not authorized to join this meeting.",
+  "network": "Network",
+  "network.reconnecting": "Connection lost. Trying to reconnect.",
+  "network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
+  "network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
+  "network.leaving": "Automatically leaving the meeting in 10 seconds.",
+  "network.restored": "Connection restored",
+  "network.delay": "Taking too long to reconnect.",
+  "network.lost": "Connection lost",
+  "network.lost_extended": "Connection lost. Please check your network connection.",
+  "livestream": "Livestream",
+  "livestream.indicator": "This meeting is being livestreamed.",
+  "livestream.skip": "Skip to Live",
+  "livestream.idle": "Waiting to go live.",
+  "livestream.starting": "Livestream is starting...",
+  "livestream.stopping": "Livestream is stopping...",
+  "livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
+  "livestream.error.not_supported": "Player not supported.",
+  "livestream.error.not_found": "Playback URL not found.",
+  "livestream.error.unknown": "An unknown error occurred.",
+  "livestream.error.sync": "Could not sync livestream please try again later.",
+  "livestream.error.start": "Error while starting livestream.",
+  "livestream.error.stop": "Error while stopping livestream.",
+  "livestream.go_live": "Go Live",
+  "livestream.end_live": "End Live",
+  "livestream.error": "Error",
+  "cta.help": "Need help on how to do this?",
+  "cta.continue": "Ignore",
+  "cta.reload": "Reload",
+  "cta.confirmation": "Are you sure?",
+  "cta.system_settings": "Open Settings",
+  "remote_access.empty": "There are no remote requests, yet.",
+  "remote_access.requests": "The following people have requested remote control to your screen share.",
+  "remote_access.allow": "Please select whom you want to give access to.",
+  "remote_access.grant": "Grant access",
+  "remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
+  "chat": "Chat",
+  "chat.new": "New",
+  "chat.max_limit_warning": "Max Character Limit",
+  "chat.rate_limit_error": "Please wait before you can send another message",
+  "chat.new_channel": "Create new channel",
+  "chat.channel_name": "Enter channel name",
+  "chat.member_name": "Enter member name",
+  "chat.add_members": "Add members",
+  "chat.delete_msg": "Delete",
+  "chat.edit_msg": "Edit",
+  "chat.send_msg": "Send message",
+  "chat.send_attachment": "Drop files/images to send",
+  "chat.send_img": "Send an image",
+  "chat.send_file": "Send a file",
+  "chat.send_emoji": "Send an emoji",
+  "chat.update_msg": "Update message",
+  "chat.channel_members": "Channel Members",
+  "chat.img.loading": "Loading image",
+  "chat.error.img_not_found": "Image not found",
+  "chat.error.empty_results": "Couldn't find a member with the specified name.",
+  "chat.img.shared_by": "Shared by",
+  "chat.reply": "Reply",
+  "chat.message_placeholder": "Message..",
+  "chat.click_to_send": "Click to send as message",
+  "chat.search_msgs": "Search messages",
+  "chat.search_conversations": "Search conversations",
+  "chat.start_conversation": "Start a conversation..",
+  "chat.empty_search": "No messages found",
+  "chat.empty_channel": "Send a message to get started",
+  "chat.cancel_upload": "Cancel upload",
+  "chat.view_chats": "View chats",
+  "chat.everyone": "everyone",
+  "chat.pinned_msgs": "Pinned messages",
+  "chat.toggle_pinned_msgs": "Toggle pinned messages",
+  "date.today": "Today",
+  "date.yesterday": "Yesterday",
+  "date.sunday": "Sunday",
+  "date.monday": "Monday",
+  "date.tuesday": "Tuesday",
+  "date.wednesday": "Wednesday",
+  "date.thursday": "Thursday",
+  "date.friday": "Friday",
+  "date.saturday": "Saturday",
+  "list.empty": "No items found",
+  "grid.listening": "Listening",
+  "transcript.off": "Turn off Transcripts",
+  "transcript.on": "Turn on Transcripts",
+  "settings.notification_sound": "Notification sound",
+  "settings.microphone_input": "Microphone",
+  "settings.speaker_output": "Speaker",
+  "settings.mirror_video": "Mirror my Video",
+  "settings.camera_off": "Camera is off",
+  "dialog.close": "Close dialog",
+  "notifications.joined": "just joined",
+  "notifications.left": "left",
+  "notifications.requesting_to_join_meeting": "is requesting to join the meeting",
+  "notifications.requested_to_join_stage": "has requested to join stage",
+  "notifications.joined_stage": "has joined stage",
+  "notifications.request_to_join_accepted": "Request to join accepted",
+  "notifications.request_to_join_rejected": "Request to join rejected",
+  "notifications.accept": "Accept",
+  "notifications.new_poll_created_by": "New poll created by",
+  "notifications.connected_to": "Connected to",
+  "notifications.plugin_switched_to": "Plugin switched to",
+  "notifications.remote_control_requested": "has requested for remote control",
+  "notifications.remote_control_request_sent": "Sent remote control request to",
+  "notifications.remote_control_request_accepted": "has granted remote control",
+  "notifications.remote_control_granted": "Granted remote control to",
+  "notifications.remote_control_terminated": "Existing remote control has been terminated",
+  "debugger.troubleshooting.label": "Troubleshooting",
+  "debugger.quality.good": "Good",
+  "debugger.quality.average": "Average",
+  "debugger.quality.poor": "Poor",
+  "debugger.stats.bitrate.label": "Bitrate",
+  "debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
+  "debugger.stats.packet_loss.label": "Packet Loss",
+  "debugger.stats.packet_loss.description": "Amount of data lost during transfer",
+  "debugger.stats.jitter.label": "Jitter",
+  "debugger.stats.jitter.description": "Variance or fluctuation in latency",
+  "debugger.stats.cpu_limitations.label": "CPU Limitations",
+  "debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
+  "debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
+  "debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
+  "debugger.audio.label": "Audio",
+  "debugger.audio.troubleshooting.label": "Audio Troubleshooting",
+  "debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.audio.messages.enable_media": "Please enable mic to see the report.",
+  "debugger.audio.sections.network_media": "Network & Media",
+  "debugger.video.label": "Video",
+  "debugger.video.troubleshooting.label": "Video Troubleshooting",
+  "debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.video.messages.enable_media": "Please enable camera to see the report.",
+  "debugger.video.sections.network_media": "Network & Media",
+  "debugger.screenshare.label": "Screenshare",
+  "debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
+  "debugger.screenshare.sections.network_media": "Network & Media",
+  "debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
+  "debugger.system.label": "System",
+  "debugger.system.troubleshooting.label": "System Troubleshooting",
+  "debugger.system.sections.battery": "Battery",
+  "debugger.system.battery.level.label": "Battery Level",
+  "debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
+  "debugger.system.battery.charging.label": "Battery Charging Status",
+  "debugger.system.battery.charging.description": "A device running on power performs optimally.",
+  "debugger.system.battery.charging.is_charging": "Charging",
+  "debugger.system.battery.charging.is_not_charging": "Not charging"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/reference-architecture/description-of-design-guides.mdx b/src/content/partials/reference-architecture/description-of-design-guides.mdx
index cedea82e2560037..ebf33568632639f 100644
--- a/src/content/partials/reference-architecture/description-of-design-guides.mdx
+++ b/src/content/partials/reference-architecture/description-of-design-guides.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Design guides take your knowledge from a reference architecture and walk through the conceptual decisions and directions you should take to implement a specific solution. They do not replace our product documentation, but instead provide guidance on the decisions you should make given a certain solution you are trying to deploy.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
index 8756e82c2b9cbe2..6a2206f3b86ff23 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
index 8756e82c2b9cbe2..6a2206f3b86ff23 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
index 24ca75fa6ed1a30..a5d6d6bb9b81e53 100644
--- a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
+++ b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-- What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
+* What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
diff --git a/src/content/partials/registrar/email-verification.mdx b/src/content/partials/registrar/email-verification.mdx
index 2b72b0b433a4f42..4dd91c56e47bc07 100644
--- a/src/content/partials/registrar/email-verification.mdx
+++ b/src/content/partials/registrar/email-verification.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If you have an [unverified account email address](/fundamentals/user-profiles/verify-email-address/), you will not be able to transfer or register domains. Verify your account email address before proceeding.
 
+
 :::
diff --git a/src/content/partials/registrar/enable-dnssec.mdx b/src/content/partials/registrar/enable-dnssec.mdx
index 83ac4c6b7219453..237935a506b128b 100644
--- a/src/content/partials/registrar/enable-dnssec.mdx
+++ b/src/content/partials/registrar/enable-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ Cloudflare Registrar offers one-click DNSSEC activation for free to all customer
 
 1. In Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain that you want to activate DNSSEC and select **Manage**.
 3. Select **Configuration** > **Enable DNSSEC**. If DNSSEC was previously activated, select **Disable DNSSEC** to disable it.
diff --git a/src/content/partials/registrar/icann-unverified-email.mdx b/src/content/partials/registrar/icann-unverified-email.mdx
index 296e965a96cf9c5..665b423fb7c437c 100644
--- a/src/content/partials/registrar/icann-unverified-email.mdx
+++ b/src/content/partials/registrar/icann-unverified-email.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::note
 
 If you purchased your domain through Cloudflare Registrar, [ICANN](https://www.icann.org/) requires you to verify your registrant email address. If your email is unverified or if the verification has expired, ICANN places a hold on the domain and replaces your nameservers with parking server nameservers (NS). Once you complete verification, your nameservers are automatically restored.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/registrar/requirements.mdx b/src/content/partials/registrar/requirements.mdx
index 1178776bde7f938..23d333ecb86aba7 100644
--- a/src/content/partials/registrar/requirements.mdx
+++ b/src/content/partials/registrar/requirements.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Requirements
diff --git a/src/content/partials/registrar/restrictions.mdx b/src/content/partials/registrar/restrictions.mdx
index b34956aeb7039bd..57a9452a3ab5a69 100644
--- a/src/content/partials/registrar/restrictions.mdx
+++ b/src/content/partials/registrar/restrictions.mdx
@@ -1,20 +1,20 @@
 ---
 {}
+
 ---
 
 ## Restrictions
 
 To transfer your domain, it must meet the following requirements:
 
-- ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
-- Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
+* ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
+* Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
   :::caution
 
   The transfer of an expired domain may result in an additional year NOT being added during the transfer.
   :::
-
-- Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
-- Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
-- Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
+* Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
+* Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
+* Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
 
 If your domain is listed as available for transfer in the Cloudflare dashboard, these restrictions have already been checked.
diff --git a/src/content/partials/registrar/verify-dnssec.mdx b/src/content/partials/registrar/verify-dnssec.mdx
index f5182b94b5a1559..cc9f05e4a7120d0 100644
--- a/src/content/partials/registrar/verify-dnssec.mdx
+++ b/src/content/partials/registrar/verify-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When DNSSEC has been successfully applied to your domain, Cloudflare shows you a confirmed status. Go to [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) in the Cloudflare dashboard, and scroll down to **DNSSEC**.
diff --git a/src/content/partials/rules/configuration-rule-link-to-examples.mdx b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
index 037eaeef781404b..1ff0517f5389e04 100644
--- a/src/content/partials/rules/configuration-rule-link-to-examples.mdx
+++ b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Refer to [Create a configuration rule via API](/rules/configuration-rules/create-api/#example-requests) for complete API examples.
diff --git a/src/content/partials/rules/configuration-rule-promotion.mdx b/src/content/partials/rules/configuration-rule-promotion.mdx
index 6519187465e5160..3ae68e3cf154e68 100644
--- a/src/content/partials/rules/configuration-rule-promotion.mdx
+++ b/src/content/partials/rules/configuration-rule-promotion.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 To use this feature on specific hostnames - instead of across your entire zone - use a [configuration rule](/rules/configuration-rules/).
 
+
 :::
diff --git a/src/content/partials/rules/error-pages-list.mdx b/src/content/partials/rules/error-pages-list.mdx
index 7ab22e20464a19f..e3245503608f21c 100644
--- a/src/content/partials/rules/error-pages-list.mdx
+++ b/src/content/partials/rules/error-pages-list.mdx
@@ -11,3 +11,4 @@ import { Details } from "~/components";
 - 1000 class errors
 - Managed challenge / I'm Under Attack Mode
 - Rate limiting block
+
diff --git a/src/content/partials/rules/page-rules-migration.mdx b/src/content/partials/rules/page-rules-migration.mdx
index 88530db810e2ac1..49184a9b7fddd3a 100644
--- a/src/content/partials/rules/page-rules-migration.mdx
+++ b/src/content/partials/rules/page-rules-migration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/rules/rules-creation-workflow.mdx b/src/content/partials/rules/rules-creation-workflow.mdx
index 457e137376878ed..c5c10393f7fe7b5 100644
--- a/src/content/partials/rules/rules-creation-workflow.mdx
+++ b/src/content/partials/rules/rules-creation-workflow.mdx
@@ -11,6 +11,7 @@ Follow this workflow to create {props.ruleName} for a given zone via API:
 1. Use the [List zone rulesets](/api/resources/rulesets/methods/list/) operation to check if there is already a ruleset for the <code>{props.phaseName}</code> phase at the zone level.
 
 2. If the phase ruleset does not exist, create it using the [Create a zone ruleset](/api/resources/rulesets/methods/create/) operation. In the new ruleset properties, set the following values:
+
    - **kind**: `zone`
    - **phase**: <code>{props.phaseName}</code>
 
diff --git a/src/content/partials/rules/rules-templates.mdx b/src/content/partials/rules/rules-templates.mdx
index 327ddbb7e03e964..15707947ed21c52 100644
--- a/src/content/partials/rules/rules-templates.mdx
+++ b/src/content/partials/rules/rules-templates.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
-Cloudflare provides you with rules templates for common use cases.
+Cloudflare provides you with rules templates for common use cases. 
 
 1. In the Cloudflare dashboard, go to the Rules **Overview** page.
 
    <DashButton url="/?to=/:account/:zone/rules/overview" />
 
-2. Select **Templates**, and then select one of the available templates.
+2. Select **Templates**, and then select one of the available templates. 
 
 You can also refer to the [Examples gallery](/rules/examples/) in the developer docs.
diff --git a/src/content/partials/rules/terraform-additional-resources.mdx b/src/content/partials/rules/terraform-additional-resources.mdx
index 38d3d167a3b1839..d12cb288e5d11d2 100644
--- a/src/content/partials/rules/terraform-additional-resources.mdx
+++ b/src/content/partials/rules/terraform-additional-resources.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 ## Additional resources
 
 For additional guidance on using Terraform with Cloudflare, refer to the following resources:
 
-- [Terraform documentation](/terraform/)
-- [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
+* [Terraform documentation](/terraform/)
+* [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
diff --git a/src/content/partials/rules/transform/header-valid-names.mdx b/src/content/partials/rules/transform/header-valid-names.mdx
index 0e72fbaa66dee00..f286e2ab339e6cc 100644
--- a/src/content/partials/rules/transform/header-valid-names.mdx
+++ b/src/content/partials/rules/transform/header-valid-names.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
-- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-- The following special characters: `-` and `_`
+* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+* The following special characters: `-` and `_`
diff --git a/src/content/partials/rules/transform/header-valid-values.mdx b/src/content/partials/rules/transform/header-valid-values.mdx
index 9daf4a9a76a4e18..540ff31d7a51c22 100644
--- a/src/content/partials/rules/transform/header-valid-values.mdx
+++ b/src/content/partials/rules/transform/header-valid-values.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
-- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-- The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
+* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+* The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
diff --git a/src/content/partials/ruleset-engine/max-expression-length.mdx b/src/content/partials/ruleset-engine/max-expression-length.mdx
index 59d99f613473f9c..e8881c097a0cb0c 100644
--- a/src/content/partials/ruleset-engine/max-expression-length.mdx
+++ b/src/content/partials/ruleset-engine/max-expression-length.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The maximum length of a rule expression is 4,096 characters.
diff --git a/src/content/partials/ruleset-engine/rule-position-values.mdx b/src/content/partials/ruleset-engine/rule-position-values.mdx
index c83ff42bfcf11a3..aed905dee8894cd 100644
--- a/src/content/partials/ruleset-engine/rule-position-values.mdx
+++ b/src/content/partials/ruleset-engine/rule-position-values.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
-- `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
+* `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
 
-- `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
+* `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
 
-- `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
+* `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
 
 :::caution[Important]
 
diff --git a/src/content/partials/security-center/brand-protection-alerts.mdx b/src/content/partials/security-center/brand-protection-alerts.mdx
index 30a6ad5713d7bad..71e7f9d688bd180 100644
--- a/src/content/partials/security-center/brand-protection-alerts.mdx
+++ b/src/content/partials/security-center/brand-protection-alerts.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Brand Protection integrates with Cloudflare's ANS (Alerts Notification Service) to provide configurable alerts when new domains are detected.
diff --git a/src/content/partials/security-center/brand-protection-definition.mdx b/src/content/partials/security-center/brand-protection-definition.mdx
index 6707a12034c0016..be50db0bf8b3b06 100644
--- a/src/content/partials/security-center/brand-protection-definition.mdx
+++ b/src/content/partials/security-center/brand-protection-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Brand Protection allows you to proactively identify and mitigate domain impersonation and phishing attacks. By monitoring newly registered domains and visual assets across the Internet, Cloudflare helps protect your brand's reputation and prevents your customers or employees from submitting sensitive information to fraudulent sites.
@@ -8,4 +9,4 @@ Common threats include:
 
 - [Typosquatting](https://en.wikipedia.org/wiki/Typosquatting): For example, typing `cloudfalre.com` instead of `cloudflare.com`.
 - Concatenation of services (`cloudflare-service.com`) often registered by attackers to trick unsuspecting victims into submitting private information such as passwords.
-- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
+- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
\ No newline at end of file
diff --git a/src/content/partials/security-center/scan-frequency.mdx b/src/content/partials/security-center/scan-frequency.mdx
index d5d4a4b4bfe5c98..78e170a9f3c6a81 100644
--- a/src/content/partials/security-center/scan-frequency.mdx
+++ b/src/content/partials/security-center/scan-frequency.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you enable Security Insights, Cloudflare performs scans automatically. Paying customers (as defined in the table below) are re-scanned daily and can trigger a scan manually:
@@ -7,4 +8,4 @@ Once you enable Security Insights, Cloudflare performs scans automatically. Payi
 | Plan                                      | Scan Frequency | On-Demand |
 | ----------------------------------------- | -------------- | --------- |
 | Accounts on a Free, Pro, or Business plan | Every 7 days   | Yes       |
-| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
+| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
\ No newline at end of file
diff --git a/src/content/partials/security-center/scan-properties.mdx b/src/content/partials/security-center/scan-properties.mdx
index cb96cf4aa2a437c..aa07143a1e7c4f7 100644
--- a/src/content/partials/security-center/scan-properties.mdx
+++ b/src/content/partials/security-center/scan-properties.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-- **Severity**: The security risk of the insight. The severity values are: _Moderate_, _High_, and _Critical_. The higher the severity level, the higher the risk of threat to your environment.
-- **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
-- **Risk**: A description of the risk associated with not addressing the issue.
-- **Type**: The insight category.
+* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment.
+* **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
+* **Risk**: A description of the risk associated with not addressing the issue.
+* **Type**: The insight category.
diff --git a/src/content/partials/security-center/security-insights-definition.mdx b/src/content/partials/security-center/security-insights-definition.mdx
index b41a47d43774aa0..caeb5d26174c035 100644
--- a/src/content/partials/security-center/security-insights-definition.mdx
+++ b/src/content/partials/security-center/security-insights-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Security Insights provides you with a list of insights, covering different areas of your Cloudflare environment, such as: Cloudflare account settings, DNS record configurations, SSL/TLS certificates configurations, Cloudflare Access configurations and Cloudflare WAF configurations.
diff --git a/src/content/partials/smart-shield/argo-analytics.mdx b/src/content/partials/smart-shield/argo-analytics.mdx
index de75df8e6e26cee..32f48959a9305a7 100644
--- a/src/content/partials/smart-shield/argo-analytics.mdx
+++ b/src/content/partials/smart-shield/argo-analytics.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
+Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/argo-intro.mdx b/src/content/partials/smart-shield/argo-intro.mdx
index 32ea358182d40ac..268b8495d8fe135 100644
--- a/src/content/partials/smart-shield/argo-intro.mdx
+++ b/src/content/partials/smart-shield/argo-intro.mdx
@@ -6,5 +6,5 @@ params:
 Argo Smart Routing detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
 
 { props.conditional === "dedicated-argo-tile" && (
-<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
+	<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
 )}
diff --git a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
index 3d8aa0a11fe62e8..9fa952b07643f85 100644
--- a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
+++ b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
+Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/dcei-pool-requirements.mdx b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
index ac278f7e6a42db8..7cafa55a6d95d3e 100644
--- a/src/content/partials/smart-shield/dcei-pool-requirements.mdx
+++ b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
+Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-analytics.mdx b/src/content/partials/smart-shield/health-checks-analytics.mdx
index 6a9a9c84165553c..2983c5deb95bc9f 100644
--- a/src/content/partials/smart-shield/health-checks-analytics.mdx
+++ b/src/content/partials/smart-shield/health-checks-analytics.mdx
@@ -194,4 +194,4 @@ If the failure cannot be classified as any other type of failure mentioned above
 
 #### Solution
 
-Contact [Cloudflare support](/support/contacting-cloudflare-support/).
+Contact [Cloudflare support](/support/contacting-cloudflare-support/).
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-intro.mdx b/src/content/partials/smart-shield/health-checks-intro.mdx
index 5d9ab876a0af7ce..ed843ebdf208147 100644
--- a/src/content/partials/smart-shield/health-checks-intro.mdx
+++ b/src/content/partials/smart-shield/health-checks-intro.mdx
@@ -4,4 +4,4 @@
 
 A health check is a service that runs on Cloudflare's edge network to monitor whether an origin server is online. This allows you to view the health of your origin servers even if there is only one origin or you do not yet need to balance traffic across your infrastructure.
 
-Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
+Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-regions.mdx b/src/content/partials/smart-shield/health-checks-regions.mdx
index 4c0e494eaeec2e9..bbbbdb12d2c0ec9 100644
--- a/src/content/partials/smart-shield/health-checks-regions.mdx
+++ b/src/content/partials/smart-shield/health-checks-regions.mdx
@@ -12,8 +12,8 @@ The Internet is not the same everywhere around the world and your users may not
 
 Analytics are presented at two levels:
 
-- Regional Aggregates: Combined results from the three data centers within a specific region.
-- Global Aggregates: Total results across all configured regions and data centers.
+* Regional Aggregates: Combined results from the three data centers within a specific region.
+* Global Aggregates: Total results across all configured regions and data centers.
 
 In the event log, entries are labeled by region or as **Global**. We do not provide granular data for individual data centers.
 
diff --git a/src/content/partials/smart-shield/smart-shield-callout.mdx b/src/content/partials/smart-shield/smart-shield-callout.mdx
index 706d52242176099..15c3e70be832e5a 100644
--- a/src/content/partials/smart-shield/smart-shield-callout.mdx
+++ b/src/content/partials/smart-shield/smart-shield-callout.mdx
@@ -4,4 +4,4 @@
 
 :::note[Smart Shield]
 This functionality is now offered as part of Cloudflare's origin server safeguard, Smart Shield. [Learn more](/smart-shield/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/zone-lockdown.mdx b/src/content/partials/smart-shield/zone-lockdown.mdx
index 5181bf0878bc7b3..77215453e523f54 100644
--- a/src/content/partials/smart-shield/zone-lockdown.mdx
+++ b/src/content/partials/smart-shield/zone-lockdown.mdx
@@ -18,7 +18,7 @@ To bypass zone lockdown using a WAF custom rule:
 
    To allow a specific Health Check, verify if the user agent contains the first 16 characters of the Health Check ID.
 
-3. Set the action to _Skip_ and the corresponding feature to **Zone Lockdown** under **More components to skip**.
+3. Set the action to *Skip* and the corresponding feature to **Zone Lockdown** under **More components to skip**.
 
 ### Via the API
 
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
index a743f57b374347a..d19bdad602512e2 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
@@ -1,49 +1,50 @@
 ---
 {}
+
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Below is a curl example and the associated data being posted to the API.
 
 **API example:**
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		dns: {
-			type: "CNAME",
-			name: "spectrum-cname.example.com",
-		},
-		ip_firewall: false,
-		protocol: "tcp/22",
-		proxy_protocol: "off",
-		tls: "off",
-		origin_dns: {
-			name: "cname-to-origin.example.com",
-			ttl: 1200,
-		},
-		origin_port: 22,
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    dns: {
+      type: "CNAME",
+      name: "spectrum-cname.example.com"
+    },
+    ip_firewall: false,
+    protocol: "tcp/22",
+    proxy_protocol: "off",
+    tls: "off",
+    origin_dns: {
+      name: "cname-to-origin.example.com",
+      ttl: 1200
+    },
+    origin_port: 22
+  }}
 />
 
 **Example data:**
 
 ```json
 {
-	"dns": {
-		"type": "CNAME",
-		"name": "spectrum-cname.example.com"
-	},
-	"ip_firewall": false,
-	"protocol": "tcp/22",
-	"proxy_protocol": "off",
-	"tls": "off",
-	"origin_dns": {
-		"name": "cname-to-origin.example.com",
-		"ttl": 1200
-	},
-	"origin_port": 22
+  "dns": {
+    "type": "CNAME",
+    "name": "spectrum-cname.example.com"
+  },
+  "ip_firewall": false,
+  "protocol": "tcp/22",
+  "proxy_protocol": "off",
+  "tls": "off",
+  "origin_dns": {
+    "name": "cname-to-origin.example.com",
+    "ttl": 1200
+  },
+  "origin_port": 22
 }
 ```
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
index 2e354499765aa68..7bca9b160ea79e7 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 1. In the Cloudflare dashboard, go to the **Spectrum** page.
 
diff --git a/src/content/partials/speed/rocket-loader-csp.mdx b/src/content/partials/speed/rocket-loader-csp.mdx
index 415fe7be153ccd2..5f9b9948eb37a16 100644
--- a/src/content/partials/speed/rocket-loader-csp.mdx
+++ b/src/content/partials/speed/rocket-loader-csp.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> in place for your domain, you will need to [update your headers](/fundamentals/reference/policies-compliances/content-security-policies/#product-requirements) to support Rocket Loader.
diff --git a/src/content/partials/speed/user-agents.mdx b/src/content/partials/speed/user-agents.mdx
index f5ce8588ee1bd80..c0837b69232398f 100644
--- a/src/content/partials/speed/user-agents.mdx
+++ b/src/content/partials/speed/user-agents.mdx
@@ -1,17 +1,19 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 For **IPv6** Cloudflare Observatory tests originate from **ASN 15169** or **ASN 132892** and are generated with the following user agents:
 
-- Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
-- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
+* Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
+* Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
 
 For **IPv4** Cloudflare Observatory tests originate from **ASN 396982** and are generated with the following user agents:
 
-- Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
-- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
+* Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
+* Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
 
 :::
diff --git a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
index 684249cf2e95c7c..f31818fcb7c6970 100644
--- a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
+++ b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The available options for **Validation method** and **Certificate Validity Period** may vary depending on the certificate authority you choose and the hostnames that you include in your Advanced certificate order.
diff --git a/src/content/partials/ssl/acm-definition.mdx b/src/content/partials/ssl/acm-definition.mdx
index b7e35411b9f6074..dd03df9af1b9a04 100644
--- a/src/content/partials/ssl/acm-definition.mdx
+++ b/src/content/partials/ssl/acm-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use advanced certificates when you want something more customizable than [Universal SSL](/ssl/edge-certificates/universal-ssl/) but still want the convenience of SSL certificate issuance and renewal.
diff --git a/src/content/partials/ssl/acm-validate-cert.mdx b/src/content/partials/ssl/acm-validate-cert.mdx
index 9927c34e5e8158d..28d8bc6f0d5532f 100644
--- a/src/content/partials/ssl/acm-validate-cert.mdx
+++ b/src/content/partials/ssl/acm-validate-cert.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 To check whether your certificates have been validated and reissued:
 
-- **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
-- **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
+* **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
+* **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
diff --git a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
index dff294bdc66047e..1d472785e89e8e2 100644
--- a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
+++ b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```bash
@@ -23,4 +24,4 @@ curl --silent \
 --header "X-Auth-Email: $MYAUTHEMAIL" \
 --header "X-Auth-Key: $MYAUTHKEY" \
 --data "$request_body"
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/ssl/caa-records-added-by-cf.mdx b/src/content/partials/ssl/caa-records-added-by-cf.mdx
index 5ff6ca31c6bf4b5..1a4489c3befb910 100644
--- a/src/content/partials/ssl/caa-records-added-by-cf.mdx
+++ b/src/content/partials/ssl/caa-records-added-by-cf.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare adds CAA records automatically in the following situations:
@@ -10,7 +11,7 @@ Cloudflare adds CAA records automatically in the following situations:
 These records make sure Cloudflare can still issue Universal certificates on your behalf.
 
 :::note[Subdomain zones caveat]
-CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) - with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
+CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) -  with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
 :::
 
 If Cloudflare has automatically added CAA records on your behalf, these records will not appear in the Cloudflare dashboard. However, if you run a command line query using `dig`, you can see any existing CAA records, including those added by Cloudflare (replacing `example.com` with your own domain on Cloudflare):
diff --git a/src/content/partials/ssl/caa-records-definition.mdx b/src/content/partials/ssl/caa-records-definition.mdx
index fd0343ee0ae9acb..0154a3d0a0fc6b4 100644
--- a/src/content/partials/ssl/caa-records-definition.mdx
+++ b/src/content/partials/ssl/caa-records-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A Certificate Authority Authorization (CAA) DNS record specifies which certificate authorities (CAs) are allowed to issue certificates for a domain. This record reduces the chance of unauthorized certificate issuance and promotes standardization across your organization.
diff --git a/src/content/partials/ssl/change-encryption-mode-api.mdx b/src/content/partials/ssl/change-encryption-mode-api.mdx
index c9c759459aa123f..56ae28c0a1ced82 100644
--- a/src/content/partials/ssl/change-encryption-mode-api.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To adjust your encryption mode with the API, send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `ssl` as the setting name in the URI path, and the `value` parameter set to your desired setting (`off`, `flexible`, `full`, `strict`, or `origin_pull`).
diff --git a/src/content/partials/ssl/change-encryption-mode-dash.mdx b/src/content/partials/ssl/change-encryption-mode-dash.mdx
index a831eabba8bed79..e7e6afa2c5c9740 100644
--- a/src/content/partials/ssl/change-encryption-mode-dash.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/cipher-suites-api-linkout.mdx b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
index 630e79915c01b64..ceda6f3443c4a1f 100644
--- a/src/content/partials/ssl/cipher-suites-api-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
+If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
\ No newline at end of file
diff --git a/src/content/partials/ssl/cipher-suites-definition.mdx b/src/content/partials/ssl/cipher-suites-definition.mdx
index 659728684c4e279..eea7fc621379f4f 100644
--- a/src/content/partials/ssl/cipher-suites-definition.mdx
+++ b/src/content/partials/ssl/cipher-suites-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cipher suites are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/) (and therefore separate from the [SSL/TLS protocol](/ssl/reference/protocols/)).
diff --git a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
index 308d5f6b820a7d9..8d202297dd8d513 100644
--- a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
+For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
\ No newline at end of file
diff --git a/src/content/partials/ssl/ciphers-api-general-notes.mdx b/src/content/partials/ssl/ciphers-api-general-notes.mdx
index 3461784c3991163..431555f3a04bc82 100644
--- a/src/content/partials/ssl/ciphers-api-general-notes.mdx
+++ b/src/content/partials/ssl/ciphers-api-general-notes.mdx
@@ -1,7 +1,7 @@
 ---
 {}
----
 
+---
 To configure cipher suites per hostname, replace the first two lines by the following:
 
 ```bash
diff --git a/src/content/partials/ssl/cname-cert-verification.mdx b/src/content/partials/ssl/cname-cert-verification.mdx
index 1af431ba8e62f82..6803cb1241595a9 100644
--- a/src/content/partials/ssl/cname-cert-verification.mdx
+++ b/src/content/partials/ssl/cname-cert-verification.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare contacts one of our certificate authority (CA) providers and asks them to issue certificates for the specified hostname. The CA will then inform Cloudflare that we need to demonstrate control of this hostname by returning a `$DCV_TOKEN` at a specified `$DCV_FILENAME`; both the token and the filename are randomly generated by the CA and not known to Cloudflare ahead of time.
diff --git a/src/content/partials/ssl/csr-definition.mdx b/src/content/partials/ssl/csr-definition.mdx
index a77784b8eeb8a0f..c3f8ebb7fdbce8c 100644
--- a/src/content/partials/ssl/csr-definition.mdx
+++ b/src/content/partials/ssl/csr-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Generate a Certificate Signing Request (CSR) to get a custom certificate from the Certificate Authority (CA) of your choice while maintaining control of the private key on Cloudflare. The private key associated with the CSR will be generated by Cloudflare and will never leave our network.
diff --git a/src/content/partials/ssl/custom-cert-ciphers.mdx b/src/content/partials/ssl/custom-cert-ciphers.mdx
index bba82764fc568eb..3f3a5f7954778d6 100644
--- a/src/content/partials/ssl/custom-cert-ciphers.mdx
+++ b/src/content/partials/ssl/custom-cert-ciphers.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before deploying custom certificates to Cloudflare's global network, Cloudflare automatically groups the certificates into certificate packs.
@@ -8,6 +9,6 @@ A certificate pack is a group of certificates that share the same set of hostnam
 
 Each pack can include up to three certificates, one from each of the following signature algorithms:
 
-- `SHA-2/RSA`
-- `SHA-2/ECDSA`
-- `SHA-1/RSA`
+* `SHA-2/RSA`
+* `SHA-2/ECDSA`
+* `SHA-1/RSA`
diff --git a/src/content/partials/ssl/custom-cert-openssl-commands.mdx b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
index 7bcbf7ba02b6ffc..547be3cbf37680a 100644
--- a/src/content/partials/ssl/custom-cert-openssl-commands.mdx
+++ b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. Run the following command to generate a 4096-bit RSA private key, using AES-256 encryption. Enter a passphrase when prompted.
diff --git a/src/content/partials/ssl/custom-certificates-definition.mdx b/src/content/partials/ssl/custom-certificates-definition.mdx
index 8b65b18a079f395..64d10e717e0b1ed 100644
--- a/src/content/partials/ssl/custom-certificates-definition.mdx
+++ b/src/content/partials/ssl/custom-certificates-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom certificates are meant for Business and Enterprise customers who want to use their own SSL certificates.
diff --git a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
index fd1a1fad0352eb7..7cf70fd8b8e6960 100644
--- a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
+++ b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom Origin Trust Store allows you to upload certificate authorities (CAs) that Cloudflare will use to authenticate connections to your origin server. Use this feature to override the default trust store with your preferred CA or CAs.
diff --git a/src/content/partials/ssl/dcv-certificate-renewal.mdx b/src/content/partials/ssl/dcv-certificate-renewal.mdx
index 77fff64fa5de773..966d6f3d11cb207 100644
--- a/src/content/partials/ssl/dcv-certificate-renewal.mdx
+++ b/src/content/partials/ssl/dcv-certificate-renewal.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
 Even if you manually handle DCV when issuing certificates in a [partial DNS setup](/dns/zone-setups/partial-setup/), at certificate renewal, Cloudflare will attempt to automatically perform DCV via HTTP.
 
 If all of the following conditions are confirmed at the first attempt, the renewal happens automatically via [HTTP](/ssl/edge-certificates/changing-dcv-method/methods/http/).
 
-- Hostnames are proxied.
-- Hostnames on the certificate resolve to the IPs assigned to the zone.
-- The certificate does not contain wildcards.
+* Hostnames are proxied.
+* Hostnames on the certificate resolve to the IPs assigned to the zone.
+* The certificate does not contain wildcards.
 
 :::note
 To automatically renew certificates that do not meet the referred criteria, consider using [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/dcv-conflicting-records.mdx b/src/content/partials/ssl/dcv-conflicting-records.mdx
index e932ebc41dd7175..c6a89d7d1f55c86 100644
--- a/src/content/partials/ssl/dcv-conflicting-records.mdx
+++ b/src/content/partials/ssl/dcv-conflicting-records.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Remove previous TXT records]
@@ -10,4 +11,4 @@ Existing TXT records for `_acme-challenge` will conflict with the delegated DCV
 _acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
 ```
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/dcv-definition.mdx b/src/content/partials/ssl/dcv-definition.mdx
index c5748e6902bfec1..88a6cd79a67b650 100644
--- a/src/content/partials/ssl/dcv-definition.mdx
+++ b/src/content/partials/ssl/dcv-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before a certificate authority (CA) will issue a certificate for a domain, the requester must prove they have control over that domain. This process is known as domain control validation (DCV).
diff --git a/src/content/partials/ssl/dcv-invalid-token-situations.mdx b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
index 785d89543fd4097..d705eaac712405c 100644
--- a/src/content/partials/ssl/dcv-invalid-token-situations.mdx
+++ b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Tokens may also become invalid upon validation failure. For more details, refer to [Domain control validation flow](/ssl/edge-certificates/changing-dcv-method/dcv-flow/#dcv-tokens).
diff --git a/src/content/partials/ssl/dcv-path-security.mdx b/src/content/partials/ssl/dcv-path-security.mdx
index eb4a9601201193b..5501d6eb5a3f734 100644
--- a/src/content/partials/ssl/dcv-path-security.mdx
+++ b/src/content/partials/ssl/dcv-path-security.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When your certificate is in `pending_validation` and valid tokens are in place, some security features targeting your zone's path for `/.well-known/*` can be automatically bypassed.
diff --git a/src/content/partials/ssl/dcv-renewal-fallback.mdx b/src/content/partials/ssl/dcv-renewal-fallback.mdx
index 662ad6b134f61e1..fd0e39d48edac6e 100644
--- a/src/content/partials/ssl/dcv-renewal-fallback.mdx
+++ b/src/content/partials/ssl/dcv-renewal-fallback.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If any one of the conditions is not met, the certificate renewal falls back to your chosen method and you will need to [repeat the DCV process](/ssl/edge-certificates/changing-dcv-method/methods/txt/#get-dcv-values) manually.
diff --git a/src/content/partials/ssl/dcv-validate-patch.mdx b/src/content/partials/ssl/dcv-validate-patch.mdx
index 173f9e888cce376..26c6cda69d9927a 100644
--- a/src/content/partials/ssl/dcv-validate-patch.mdx
+++ b/src/content/partials/ssl/dcv-validate-patch.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To request an immediate recheck, send another [PATCH request](/api/resources/ssl/subresources/verification/methods/edit/) with the same `validation_method` as your current validation method.
diff --git a/src/content/partials/ssl/encryption-mode-definition.mdx b/src/content/partials/ssl/encryption-mode-definition.mdx
index 22d2c160d68d3b2..145f8a9e7617a8f 100644
--- a/src/content/partials/ssl/encryption-mode-definition.mdx
+++ b/src/content/partials/ssl/encryption-mode-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Your zone's **SSL/TLS Encryption Mode** controls how Cloudflare manages two connections: one between your visitors and Cloudflare, and the other between Cloudflare and your origin server.
diff --git a/src/content/partials/ssl/enforce-https-recommendation.mdx b/src/content/partials/ssl/enforce-https-recommendation.mdx
index 3bedac422468cc2..9c7faf843ba079a 100644
--- a/src/content/partials/ssl/enforce-https-recommendation.mdx
+++ b/src/content/partials/ssl/enforce-https-recommendation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Even if your application has an active edge certificate, visitors can still access resources over unsecured HTTP connections.
diff --git a/src/content/partials/ssl/error-rate-limiting.mdx b/src/content/partials/ssl/error-rate-limiting.mdx
index 239593e80b8d7b9..ba85796a11af004 100644
--- a/src/content/partials/ssl/error-rate-limiting.mdx
+++ b/src/content/partials/ssl/error-rate-limiting.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 As mentioned in [Certificate authorities](/ssl/reference/certificate-authorities/), specific CAs may have their own limitations. If you use Let’s Encrypt and receive the error below, it means you hit the [duplicate certificate limit](https://letsencrypt.org/docs/duplicate-certificate-limit/) imposed by Let's Encrypt.
diff --git a/src/content/partials/ssl/generic-validation-process.mdx b/src/content/partials/ssl/generic-validation-process.mdx
index e67dc0bfa07e1cb..0b3edf72e02fea2 100644
--- a/src/content/partials/ssl/generic-validation-process.mdx
+++ b/src/content/partials/ssl/generic-validation-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/geokey-manager-v1.mdx b/src/content/partials/ssl/geokey-manager-v1.mdx
index c2a97612cff66a7..38388aa647932b8 100644
--- a/src/content/partials/ssl/geokey-manager-v1.mdx
+++ b/src/content/partials/ssl/geokey-manager-v1.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The first version of Geo Key Manager supports 3 regions: U.S., E.U., and a set of High Security Data Centers. If you would like to restrict your private key to another country or region, [apply for the closed beta](https://www.cloudflare.com/lp/geo-key-manager/) of the new version.
diff --git a/src/content/partials/ssl/get-started-additional-features.mdx b/src/content/partials/ssl/get-started-additional-features.mdx
index e975392ac50b3c9..9e7f8fdb53fbfc6 100644
--- a/src/content/partials/ssl/get-started-additional-features.mdx
+++ b/src/content/partials/ssl/get-started-additional-features.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 After you have chosen your encryption mode and enforced HTTPS connections, evaluate the following settings:
 
-- [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
-- [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
-- [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
+* [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
+* [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
+* [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
diff --git a/src/content/partials/ssl/http-cname-validation-process.mdx b/src/content/partials/ssl/http-cname-validation-process.mdx
index 33d5cd00e2c0499..f5e56eee7eb0688 100644
--- a/src/content/partials/ssl/http-cname-validation-process.mdx
+++ b/src/content/partials/ssl/http-cname-validation-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/http-to-txt-schedule.mdx b/src/content/partials/ssl/http-to-txt-schedule.mdx
index 94368fb7c494aae..7081625d6110114 100644
--- a/src/content/partials/ssl/http-to-txt-schedule.mdx
+++ b/src/content/partials/ssl/http-to-txt-schedule.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 - 90-days certificates: after failing for 15 days
 - 30-days certificates: after failing for 7 days
-- 14-days certificates: after failing for 3 days
+- 14-days certificates: after failing for 3 days
\ No newline at end of file
diff --git a/src/content/partials/ssl/keyless-ssl-definition.mdx b/src/content/partials/ssl/keyless-ssl-definition.mdx
index 7199cc1bbca9e0a..12b1d3ad53d80e7 100644
--- a/src/content/partials/ssl/keyless-ssl-definition.mdx
+++ b/src/content/partials/ssl/keyless-ssl-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Keyless SSL allows security-conscious clients to upload their own custom certificates and benefit from Cloudflare, but without exposing their TLS private keys.
diff --git a/src/content/partials/ssl/keyless-tunnel-setup.mdx b/src/content/partials/ssl/keyless-tunnel-setup.mdx
index fc296217a5ba2fd..ff09dc073729618 100644
--- a/src/content/partials/ssl/keyless-tunnel-setup.mdx
+++ b/src/content/partials/ssl/keyless-tunnel-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This process differs depending on whether you are using the [command line](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/create-local-tunnel/) or the [Cloudflare dashboard](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/).
diff --git a/src/content/partials/ssl/keyless-upload-preamble.mdx b/src/content/partials/ssl/keyless-upload-preamble.mdx
index ae8cfa436a5f20f..1c57296ce980ad0 100644
--- a/src/content/partials/ssl/keyless-upload-preamble.mdx
+++ b/src/content/partials/ssl/keyless-upload-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before your key servers can be configured, you must next upload the corresponding SSL certificates to Cloudflare’s edge. During TLS termination, Cloudflare will present these certificates to connecting browsers and then (for non-resumed sessions) communicate with the specified key server to complete the handshake.
diff --git a/src/content/partials/ssl/origin-ca-pause-error.mdx b/src/content/partials/ssl/origin-ca-pause-error.mdx
index 282af35186d78e9..a3d2919fcdfbca3 100644
--- a/src/content/partials/ssl/origin-ca-pause-error.mdx
+++ b/src/content/partials/ssl/origin-ca-pause-error.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
 
-Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
+Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
\ No newline at end of file
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
index ee3c0a0ba7c5962..5ce503fae04a18f 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -10,9 +11,10 @@ This applies to customers using [Universal](/ssl/edge-certificates/universal-ssl
 
 If one of the hostnames on the certificate is not proxying traffic through Cloudflare, certificate issuance and renewal will vary based on the type of certificate you are using:
 
-- **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
-- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+* **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
+* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+
 
 :::tip
 If all hostnames are proxied and non-wildcard but you are using [TXT](/ssl/edge-certificates/changing-dcv-method/methods/txt/) as DCV method for advanced certificates, also consider [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to simplify the process.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
index 59e04d484d2bc13..c506b1aaf0cbe6b 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 For wildcard hostname certificates, certificate issuance and renewal varies based on the type of certificate you are using:
 
-- **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
-- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+* **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
+* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 If you cannot use Delegated DCV, you need to use [TXT based DCV](/ssl/edge-certificates/changing-dcv-method/methods/txt/) for certificate issuance and renewal. This means you will need to place one TXT DCV token for every hostname on the certificate. If one or more of the hostnames on the certificate fails to validate, the certificate will not be issued or renewed.
 
diff --git a/src/content/partials/ssl/ssl-mode-errors.mdx b/src/content/partials/ssl/ssl-mode-errors.mdx
index 2182e11414cdb4f..6c4766d72ecd2c2 100644
--- a/src/content/partials/ssl/ssl-mode-errors.mdx
+++ b/src/content/partials/ssl/ssl-mode-errors.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Depending on your origin configuration, you may have to adjust settings to avoid [Mixed Content errors](/ssl/troubleshooting/mixed-content-errors/) or [redirect loops](/ssl/troubleshooting/too-many-redirects/).
diff --git a/src/content/partials/ssl/ssl-mode-no-aop.mdx b/src/content/partials/ssl/ssl-mode-no-aop.mdx
index de73f0f75904e95..4818962513eef71 100644
--- a/src/content/partials/ssl/ssl-mode-no-aop.mdx
+++ b/src/content/partials/ssl/ssl-mode-no-aop.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Authenticated Origin Pull](/ssl/origin-configuration/authenticated-origin-pull/) does not work when your [**SSL/TLS encryption mode**](/ssl/origin-configuration/ssl-modes/) is set to **Off** or **Flexible**.
diff --git a/src/content/partials/ssl/ssl-recommender-post-setup.mdx b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
index c20c95e8c8d9494..f742c710a2e813c 100644
--- a/src/content/partials/ssl/ssl-recommender-post-setup.mdx
+++ b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 Once enabled, the SSL/TLS Recommender runs an origin scan using the user agent `Cloudflare-SSLDetector` and ignores your `robots.txt` file (except for rules explicitly targeting the user agent).
 
 Based on this initial scan, the Recommender may decide that you could use a stronger [SSL encryption mode](/ssl/origin-configuration/ssl-modes/). It will never recommend a weaker option than what is currently configured.
 
-If so, it will send the application owner an email with the recommended option and add a _Recommended by Cloudflare_ tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
+If so, it will send the application owner an email with the recommended option and add a *Recommended by Cloudflare* tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
 
 If you do not receive an email, keep your current **SSL encryption mode**.
diff --git a/src/content/partials/ssl/ssl-recommender-prereqs.mdx b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
index 54a2fb9f09c8532..5a469237108799e 100644
--- a/src/content/partials/ssl/ssl-recommender-prereqs.mdx
+++ b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 To make sure you do not inadvertently block the **SSL/TLS Recommender**, review your settings to make sure your domain:
 
-- Is accessible.
-- Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
-- Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
+* Is accessible.
+* Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
+* Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
diff --git a/src/content/partials/ssl/test-tls-version.mdx b/src/content/partials/ssl/test-tls-version.mdx
index 7795c23bee8e13c..610dd99b691b6f9 100644
--- a/src/content/partials/ssl/test-tls-version.mdx
+++ b/src/content/partials/ssl/test-tls-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To test supported TLS versions, attempt a request to your website or application while specifying a TLS version.
@@ -16,4 +17,4 @@ If the TLS version you are testing is blocked by Cloudflare, the TLS handshake i
 
 :::note
 Local VPN or a device security client may prevent insecure connections using legacy protocols like TLS 1.0. Make sure to disable such network or security client before running the test on your device.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
index 39ab2370be87926..40fff440b9fdfbe 100644
--- a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
+++ b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You cannot set specific TLS 1.3 ciphers. Instead, you can enable [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) for your entire zone and Cloudflare will use [all applicable TLS 1.3 cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites/). In combination with this, you can still [disable weak cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) for TLS 1.0-1.2.
diff --git a/src/content/partials/ssl/total-tls-character-limitation.mdx b/src/content/partials/ssl/total-tls-character-limitation.mdx
index 958bf51b7fa1f6c..2f4bd6c578be433 100644
--- a/src/content/partials/ssl/total-tls-character-limitation.mdx
+++ b/src/content/partials/ssl/total-tls-character-limitation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
+Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
\ No newline at end of file
diff --git a/src/content/partials/ssl/txt-validation-api.mdx b/src/content/partials/ssl/txt-validation-api.mdx
index 26ae11200ce4d88..cdf1f38f24b2fcc 100644
--- a/src/content/partials/ssl/txt-validation-api.mdx
+++ b/src/content/partials/ssl/txt-validation-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can access these tokens using the API with the [`GET` request](/api/resources/ssl/subresources/certificate_packs/methods/get/) and including `status=pending_validation` as a request parameter.
@@ -8,31 +9,31 @@ For example, here are two tokens highlighted in the API response for a wildcard
 
 ```json title="Response" {13,14,15,16,17,18,19,20,21,22,23,24}
 {
-	"result": [
-		{
-			"id": "<CERTIFICATE_ID>",
-			"type": "advanced",
-			"hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
-			"primary_certificate": "0",
-			"status": "pending_validation",
-			"certificates": [],
-			"created_on": "2022-10-12T21:46:21.979150Z",
-			"validity_days": 90,
-			"validation_method": "txt",
-			"validation_records": [
-				{
-					"status": "pending",
-					"txt_name": "_acme-challenge.<DOMAIN>.com",
-					"txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
-				},
-				{
-					"status": "pending",
-					"txt_name": "_acme-challenge.<DOMAIN>.com",
-					"txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
-				}
-			],
-			"certificate_authority": "google"
-		}
-	]
+  "result": [
+    {
+      "id": "<CERTIFICATE_ID>",
+      "type": "advanced",
+      "hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
+      "primary_certificate": "0",
+      "status": "pending_validation",
+      "certificates": [],
+      "created_on": "2022-10-12T21:46:21.979150Z",
+      "validity_days": 90,
+      "validation_method": "txt",
+      "validation_records": [
+        {
+          "status": "pending",
+          "txt_name": "_acme-challenge.<DOMAIN>.com",
+          "txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
+        },
+        {
+          "status": "pending",
+          "txt_name": "_acme-challenge.<DOMAIN>.com",
+          "txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
+        }
+      ],
+      "certificate_authority": "google"
+    }
+  ]
 }
 ```
diff --git a/src/content/partials/ssl/txt-validation-dashboard.mdx b/src/content/partials/ssl/txt-validation-dashboard.mdx
index af46b2c550b4575..e32eed0b158c9b1 100644
--- a/src/content/partials/ssl/txt-validation-dashboard.mdx
+++ b/src/content/partials/ssl/txt-validation-dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/txt-validation-definition.mdx b/src/content/partials/ssl/txt-validation-definition.mdx
index adb5d6e522dfef2..01de109728d2ed3 100644
--- a/src/content/partials/ssl/txt-validation-definition.mdx
+++ b/src/content/partials/ssl/txt-validation-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 TXT record validation requires the creation of a TXT record in the hostname's authoritative DNS.
diff --git a/src/content/partials/ssl/txt-validation-preamble.mdx b/src/content/partials/ssl/txt-validation-preamble.mdx
index f373dcb972851f5..93faafe1adf5447 100644
--- a/src/content/partials/ssl/txt-validation-preamble.mdx
+++ b/src/content/partials/ssl/txt-validation-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you [create a new certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) and choose the validation method of **TXT**, your tokens will be ready after a few seconds.
diff --git a/src/content/partials/ssl/universal-ssl-enable-full.mdx b/src/content/partials/ssl/universal-ssl-enable-full.mdx
index 4eae263d68c1083..ccc7dd4e0694511 100644
--- a/src/content/partials/ssl/universal-ssl-enable-full.mdx
+++ b/src/content/partials/ssl/universal-ssl-enable-full.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For domains on a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], your domain should **automatically** receive its Universal SSL certificate within **15 minutes to 24 hours** of domain activation[^2].
diff --git a/src/content/partials/ssl/universal-ssl-validity.mdx b/src/content/partials/ssl/universal-ssl-validity.mdx
index 10512702dea5b86..ab44a9287adf96f 100644
--- a/src/content/partials/ssl/universal-ssl-validity.mdx
+++ b/src/content/partials/ssl/universal-ssl-validity.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For Universal certificates, Cloudflare controls the validity periods and certificate authorities (CAs), making sure that renewal always occur.
@@ -8,4 +9,4 @@ For Universal certificates, Cloudflare controls the validity periods and certifi
 If you are on a [CNAME setup (partial)](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup), make sure [Domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/) is configured correctly. Refer to [Troubleshooting DCV](/ssl/edge-certificates/changing-dcv-method/troubleshooting/) for further help.
 :::
 
-Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
+Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
\ No newline at end of file
diff --git a/src/content/partials/ssl/ussl-limitations-solutions.mdx b/src/content/partials/ssl/ussl-limitations-solutions.mdx
index 3fdeeda79faea70..ee503a418a8aacd 100644
--- a/src/content/partials/ssl/ussl-limitations-solutions.mdx
+++ b/src/content/partials/ssl/ussl-limitations-solutions.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 To prevent insecure connections on a multi-level subdomain, do one of the following:
 
-- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
-- Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
-- Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
+* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
+* Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
+* Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
 
 If none of these solutions work, you could also remove the multi-level subdomain.
diff --git a/src/content/partials/ssl/ussl-limitations-table.mdx b/src/content/partials/ssl/ussl-limitations-table.mdx
index 7d391d48177e70e..f2f932a5a2b1a7e 100644
--- a/src/content/partials/ssl/ussl-limitations-table.mdx
+++ b/src/content/partials/ssl/ussl-limitations-table.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 By default, Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) only cover your apex domain and one level of subdomain.
diff --git a/src/content/partials/ssl/validation-level-note.mdx b/src/content/partials/ssl/validation-level-note.mdx
index 2eb371ceb102413..03bd8c76025c290 100644
--- a/src/content/partials/ssl/validation-level-note.mdx
+++ b/src/content/partials/ssl/validation-level-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Certificates issued through Cloudflare - [Universal](/ssl/edge-certificates/universal-ssl/), [Advanced](/ssl/edge-certificates/advanced-certificate-manager/), and [Custom Hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) certificates - are Domain Validated (DV). You can [upload a custom certificate](/ssl/edge-certificates/custom-certificates/) if your organization needs OV or EV certificates.
diff --git a/src/content/partials/stream/android_playback_code_snippet.mdx b/src/content/partials/stream/android_playback_code_snippet.mdx
index e60e829108231a9..6962729cc8a9fce 100644
--- a/src/content/partials/stream/android_playback_code_snippet.mdx
+++ b/src/content/partials/stream/android_playback_code_snippet.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```kotlin
diff --git a/src/content/partials/stream/chromecast_limitations.mdx b/src/content/partials/stream/chromecast_limitations.mdx
index e7a4b69eed6c016..0aa204b3ebbd6bb 100644
--- a/src/content/partials/stream/chromecast_limitations.mdx
+++ b/src/content/partials/stream/chromecast_limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/stream/ios_playback_code_snippet.mdx b/src/content/partials/stream/ios_playback_code_snippet.mdx
index f9d23f1f2ea17d1..5b446692c4df2da 100644
--- a/src/content/partials/stream/ios_playback_code_snippet.mdx
+++ b/src/content/partials/stream/ios_playback_code_snippet.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```swift
diff --git a/src/content/partials/stream/prereqs.mdx b/src/content/partials/stream/prereqs.mdx
index abc70769ba595b1..3c8c70289c8042a 100644
--- a/src/content/partials/stream/prereqs.mdx
+++ b/src/content/partials/stream/prereqs.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Before you can play videos, you must first [upload a video to Cloudflare Stream](/stream/uploading-videos/) or be [actively streaming to a live input](/stream/stream-live)
 
+
 :::
diff --git a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
index 4359b8da3c410e2..aa189ea437225d8 100644
--- a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
+++ b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Before you can play live video, you must first be [actively streaming to a live input](/stream/stream-live/start-stream-live).
 
+
 :::
diff --git a/src/content/partials/stream/srt-supported-modes.mdx b/src/content/partials/stream/srt-supported-modes.mdx
index 2355744270cb533..e265ce9ecd07404 100644
--- a/src/content/partials/stream/srt-supported-modes.mdx
+++ b/src/content/partials/stream/srt-supported-modes.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Stream only supports the SRT caller mode, which is responsible for broadcasting a live stream after a connection is established.
 
+
 :::
diff --git a/src/content/partials/style-guide/directory-listing-definition.mdx b/src/content/partials/style-guide/directory-listing-definition.mdx
index 3fe2c759e1c53cc..e301ae54c2538d0 100644
--- a/src/content/partials/style-guide/directory-listing-definition.mdx
+++ b/src/content/partials/style-guide/directory-listing-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
+Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/icons.mdx b/src/content/partials/style-guide/icons.mdx
index e7565605607107d..0ff4d9b2bdff1b2 100644
--- a/src/content/partials/style-guide/icons.mdx
+++ b/src/content/partials/style-guide/icons.mdx
@@ -3,4 +3,4 @@ params:
   - component
 ---
 
-Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
+Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/public-stats-definition.mdx b/src/content/partials/style-guide/public-stats-definition.mdx
index 5c337b32e6019f3..0feedc632bbe330 100644
--- a/src/content/partials/style-guide/public-stats-definition.mdx
+++ b/src/content/partials/style-guide/public-stats-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
+The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/tab-guidance.mdx b/src/content/partials/style-guide/tab-guidance.mdx
index 0c4938e1fd9a2ce..bbabd5ac6d12ff3 100644
--- a/src/content/partials/style-guide/tab-guidance.mdx
+++ b/src/content/partials/style-guide/tab-guidance.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section.
+The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section. 
 
-Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
+Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/table-guidelines.mdx b/src/content/partials/style-guide/table-guidelines.mdx
index 5095d31cef3b176..add12c6f1f8fea9 100644
--- a/src/content/partials/style-guide/table-guidelines.mdx
+++ b/src/content/partials/style-guide/table-guidelines.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
+Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
\ No newline at end of file
diff --git a/src/content/partials/support/2fa-enable.mdx b/src/content/partials/support/2fa-enable.mdx
index dcde0ef633ea1f1..f93e4811432751f 100644
--- a/src/content/partials/support/2fa-enable.mdx
+++ b/src/content/partials/support/2fa-enable.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 We recommend that all Cloudflare user account holders enable two-factor authentication (2FA) to keep your accounts secure. 
diff --git a/src/content/partials/support/2fa-overview.mdx b/src/content/partials/support/2fa-overview.mdx
index ef795a849728569..566f562331ebb06 100644
--- a/src/content/partials/support/2fa-overview.mdx
+++ b/src/content/partials/support/2fa-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Two-factor authentication (2FA) allows user account owners to add an additional layer of login security to Cloudflare accounts. This additional authentication step requires you to provide both something you know, such as a Cloudflare password, and something you have, such as an authentication code from a mobile device.
diff --git a/src/content/partials/tenant/account-definition.mdx b/src/content/partials/tenant/account-definition.mdx
index 9ad1c4090b9bb5a..02febfffaee6f3b 100644
--- a/src/content/partials/tenant/account-definition.mdx
+++ b/src/content/partials/tenant/account-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An entity that contains various settings, users, and resources (zones, Zero Trust applications, Workers).
diff --git a/src/content/partials/tenant/account-details-preamble.mdx b/src/content/partials/tenant/account-details-preamble.mdx
index f43626e1f450432..67723262e1208c1 100644
--- a/src/content/partials/tenant/account-details-preamble.mdx
+++ b/src/content/partials/tenant/account-details-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An [**Account**](/tenant/glossary/#account) will contain various settings, resources, and subscriptions to products for users. Each Tenant can have multiple associated accounts.
diff --git a/src/content/partials/tenant/account-details.mdx b/src/content/partials/tenant/account-details.mdx
index beac7c19ba854a0..0fe39346e3d974f 100644
--- a/src/content/partials/tenant/account-details.mdx
+++ b/src/content/partials/tenant/account-details.mdx
@@ -1,20 +1,27 @@
 ---
 {}
+
 ---
 
+
+
 To retrieve a list of accounts associated with a Tenant details, send a `GET` request to the `/tenants/{tenant_id}/accounts` endpoint. You can find the Tenant tag and all Tenants associated with the user with the [**Tenant Details**](/tenant/how-to/get-tenant-details/) API. The Tenant Accounts API also requires pagination passed as query parameters:
 
-- `page` number
-  - Page number of accounts list response, indexed from 1
+* `page` number
+
+  * Page number of accounts list response, indexed from 1
+
+* `per_page` number
+
+  * Number of accounts to display per page
+
+* `order` string
+  * (optional) Order by a specific column, has to be a valid top-level key from the response
 
-- `per_page` number
-  - Number of accounts to display per page
+  * `direction` number
+    * (optional) 0 for ascending or 1 for descending, is 0 by default
 
-- `order` string
-  - (optional) Order by a specific column, has to be a valid top-level key from the response
 
-  - `direction` number
-    - (optional) 0 for ascending or 1 for descending, is 0 by default
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/tenants/{tenant_id}/accounts?page=1&per_page=10" \
diff --git a/src/content/partials/tenant/account-preamble.mdx b/src/content/partials/tenant/account-preamble.mdx
index e1243d170a99457..f8b3baf7f3775a0 100644
--- a/src/content/partials/tenant/account-preamble.mdx
+++ b/src/content/partials/tenant/account-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Each customer or team that uses Cloudflare should have their own account. This ensures proper security and access of resources. Each account acts as a container of zones and other resources. Depending on your needs, you may even provision multiple accounts for a single customer or team.
diff --git a/src/content/partials/tenant/create-account-api.mdx b/src/content/partials/tenant/create-account-api.mdx
index 0783c47157f77f3..7c40a5a7b6cd770 100644
--- a/src/content/partials/tenant/create-account-api.mdx
+++ b/src/content/partials/tenant/create-account-api.mdx
@@ -1,39 +1,51 @@
 ---
 {}
+
 ---
 
+
+
 To create an account using the API, make a `POST` request to the `/accounts` endpoint and include the following values:
 
-- `name` string
-  - The name of the account that is displayed in the Cloudflare dashboard.
+* `name` string
 
-- `type` enum
-  - Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
+  * The name of the account that is displayed in the Cloudflare dashboard.
 
-- `unit` object
-  - Information related to the tenant unit.
+* `type` enum
 
-  - `id` string
-    - (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
+  * Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
+
+* `unit` object
+  * Information related to the tenant unit.
+
+  * `id` string
+    * (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
 
 ### Know-Your-Customer (optional)
 
 All KYC parameters are text fields, have a 120 character limit, and are optional unless enforced by the Tenant.
 
-- `business_name` string
-  - (optional) The name of the business associated with this account.
+* `business_name` string
+
+  * (optional) The name of the business associated with this account.
+
+* `business_address` string
+
+  * (optional) The address of the business associated with this account.
+
+* `business_email` string
+
+  * (optional) The email of the business associated with this account.
+
+* `business_phone` string
+
+  * (optional) The phone number of the business associated with this account.
 
-- `business_address` string
-  - (optional) The address of the business associated with this account.
+* `external_metadata` string
 
-- `business_email` string
-  - (optional) The email of the business associated with this account.
+  * (optional) External metadata for this account.
 
-- `business_phone` string
-  - (optional) The phone number of the business associated with this account.
 
-- `external_metadata` string
-  - (optional) External metadata for this account.
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/accounts" \
@@ -50,17 +62,17 @@ A successful request will return an HTTP status of `200` and the following respo
 
 ```json title="Response"
 {
-	"result": {
-		"id": "2bab6ace8c72ed3f09b9eca6db1396bb",
-		"name": "<ACCOUNT_NAME>",
-		"type": "standard",
-		"settings": {
-			"enforce_twofactor": false
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "2bab6ace8c72ed3f09b9eca6db1396bb",
+    "name": "<ACCOUNT_NAME>",
+    "type": "standard",
+    "settings": {
+      "enforce_twofactor": false
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
diff --git a/src/content/partials/tenant/create-account-dash.mdx b/src/content/partials/tenant/create-account-dash.mdx
index b419db913d27be1..5ac799f25ff0d84 100644
--- a/src/content/partials/tenant/create-account-dash.mdx
+++ b/src/content/partials/tenant/create-account-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create an account under your tenant using the dashboard:
diff --git a/src/content/partials/tenant/create-account-subscription.mdx b/src/content/partials/tenant/create-account-subscription.mdx
index 5de32a989695839..3079c476a2951ff 100644
--- a/src/content/partials/tenant/create-account-subscription.mdx
+++ b/src/content/partials/tenant/create-account-subscription.mdx
@@ -1,17 +1,25 @@
 ---
 {}
+
 ---
 
+
+
 To create an account subscription, send a [POST](/api/resources/accounts/subresources/subscriptions/methods/create/) request to the `/accounts/{account_id}/subscriptions` endpoint and include the following values:
 
-- `rate_plan` object
-  - Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
+* `rate_plan` object
+
+  * Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
+
+* `component_values` array
+
+  * Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
+
+* `frequency` string
+
+  * How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-- `component_values` array
-  - Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
 
-- `frequency` string
-  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
 ```bash title="Request"
 curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/subscriptions' \
diff --git a/src/content/partials/tenant/create-zone-subscription.mdx b/src/content/partials/tenant/create-zone-subscription.mdx
index bf71f6c38a3b69f..4535e906db668f5 100644
--- a/src/content/partials/tenant/create-zone-subscription.mdx
+++ b/src/content/partials/tenant/create-zone-subscription.mdx
@@ -1,19 +1,27 @@
 ---
 {}
+
 ---
 
+
+
 To create a zone subscription, typically used to upgrade a zone's plan from `PARTNERS_FREE` to a paid [Zone plan](/tenant/reference/subscriptions/#zone-plans), send a [POST](/api/resources/zones/subresources/subscriptions/methods/create/) request to the `/zones/{zone_id}/subscription` endpoint and include the following values:
 
-- `rate_plan` object
-  - Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
+* `rate_plan` object
+
+  * Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
+
+* `component_values` array
+
+  * Additional services depending on your reseller agreement, such as additional `page_rules`.
+
+* `frequency` string
+
+  * How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-- `component_values` array
-  - Additional services depending on your reseller agreement, such as additional `page_rules`.
 
-- `frequency` string
-  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-```bash title="Request (without `component_values`)"
+```bash title="Request (without &#x60;component_values&#x60;)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
@@ -25,7 +33,7 @@ curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 }'
 ```
 
-```bash title="Request (with `component_values`)"
+```bash title="Request (with &#x60;component_values&#x60;)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
diff --git a/src/content/partials/tenant/resource-definition.mdx b/src/content/partials/tenant/resource-definition.mdx
index ccd4f6b5cf492d4..e8eb77e0f94146a 100644
--- a/src/content/partials/tenant/resource-definition.mdx
+++ b/src/content/partials/tenant/resource-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A resource is an entity owned by an account, which could be a zone/domain, a Workers instance, or a Zero Trust application.
diff --git a/src/content/partials/tenant/tenant-admin-definition.mdx b/src/content/partials/tenant/tenant-admin-definition.mdx
index 93e8c088ed8bd38..fad90445024fac8 100644
--- a/src/content/partials/tenant/tenant-admin-definition.mdx
+++ b/src/content/partials/tenant/tenant-admin-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you sign a partner agreement with Cloudflare, we create a special Tenant account and then add your user to that account as a **Tenant admin**. Cloudflare can add multiple users as Tenant admins upon request.
diff --git a/src/content/partials/tenant/tenant-definition.mdx b/src/content/partials/tenant/tenant-definition.mdx
index c3f7cca0a2e8b7d..750a5387fbdb3c1 100644
--- a/src/content/partials/tenant/tenant-definition.mdx
+++ b/src/content/partials/tenant/tenant-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A **Tenant** is a special type of Cloudflare account that contains other accounts and resources.
diff --git a/src/content/partials/tenant/tenant-details-preamble.mdx b/src/content/partials/tenant/tenant-details-preamble.mdx
index a54abfd6e57347a..d1b84c3b3cbac7c 100644
--- a/src/content/partials/tenant/tenant-details-preamble.mdx
+++ b/src/content/partials/tenant/tenant-details-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A [**Tenant Admin**](/tenant/glossary/#tenant-admin)'s unit and membership details will be used for access of resources and all Tenant operations on the API. The unit ID (`unit_tag`), for example, can be used to create an account on a specific unit.
diff --git a/src/content/partials/tenant/tenant-details.mdx b/src/content/partials/tenant/tenant-details.mdx
index 9ee665e4b7dff30..131ba5be5b9e779 100644
--- a/src/content/partials/tenant/tenant-details.mdx
+++ b/src/content/partials/tenant/tenant-details.mdx
@@ -1,9 +1,14 @@
 ---
 {}
+
 ---
 
+
+
 To retrieve tenant details, send a `GET` request to the `/user/tenants` endpoint:
 
+
+
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/user/tenants" \
 --header "X-Auth-Email: <EMAIL>" \
diff --git a/src/content/partials/tenant/user-definition.mdx b/src/content/partials/tenant/user-definition.mdx
index a7bb17ad18df033..6b17b01a9d90808 100644
--- a/src/content/partials/tenant/user-definition.mdx
+++ b/src/content/partials/tenant/user-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A member of a Cloudflare account with their own user profile and [an associated role](/fundamentals/manage-members/roles/) that specifies their privileges within that account.
diff --git a/src/content/partials/terraform/create-r2-buckets.mdx b/src/content/partials/terraform/create-r2-buckets.mdx
index 3e04904347b494d..13c5a4d7689c5d6 100644
--- a/src/content/partials/terraform/create-r2-buckets.mdx
+++ b/src/content/partials/terraform/create-r2-buckets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs } from "~/components";
diff --git a/src/content/partials/terraform/find-ids-managed-rulesets.mdx b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
index f096359f08c52fb..e93b48bff9fb814 100644
--- a/src/content/partials/terraform/find-ids-managed-rulesets.mdx
+++ b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy the managed rulesets.
 
-- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
 
 The deployment of managed rulesets via Terraform requires that you use the ruleset IDs. To find the IDs of managed rulesets, use the [List account rulesets](/api/resources/rulesets/methods/list/) operation. The response will include the description and IDs of existing managed rulesets.
diff --git a/src/content/partials/terraform/find-ids.mdx b/src/content/partials/terraform/find-ids.mdx
index 989917bed7dc690..25181bac1db4ec9 100644
--- a/src/content/partials/terraform/find-ids.mdx
+++ b/src/content/partials/terraform/find-ids.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy rulesets.
 
-- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
diff --git a/src/content/partials/terraform/import-delete-existing-rulesets.mdx b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
index b31987c47c68650..3b1d669425223b3 100644
--- a/src/content/partials/terraform/import-delete-existing-rulesets.mdx
+++ b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 Terraform assumes that it has complete control over account and zone rulesets. If you already have rulesets configured in your account or zone, do one of the following:
 
-- [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
-- Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
+* [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
+* Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
diff --git a/src/content/partials/terraform/v4-code-snippets.mdx b/src/content/partials/terraform/v4-code-snippets.mdx
index 485490e7bf66300..99de18e73442fe3 100644
--- a/src/content/partials/terraform/v4-code-snippets.mdx
+++ b/src/content/partials/terraform/v4-code-snippets.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::note
 Terraform code snippets below refer to the v4 SDK only.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/terraform/v5-code-snippets.mdx b/src/content/partials/terraform/v5-code-snippets.mdx
index 65ddb58c386e133..4bd83b42ff17813 100644
--- a/src/content/partials/terraform/v5-code-snippets.mdx
+++ b/src/content/partials/terraform/v5-code-snippets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/time-services/ntp-definition.mdx b/src/content/partials/time-services/ntp-definition.mdx
index df9e63e8a5ab83d..76dc31d5a57dd6a 100644
--- a/src/content/partials/time-services/ntp-definition.mdx
+++ b/src/content/partials/time-services/ntp-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Network Time Protocol](https://tools.ietf.org/html/rfc1305) (NTP) is an Internet protocol designed to synchronize time between computer systems communicating over unreliable and variable-latency network paths. Cloudflare offers its version of NTP for free so you can use our [global anycast network](https://www.cloudflare.com/network/) to synchronize time from our closest server.
diff --git a/src/content/partials/turnstile/challenge-behavior.mdx b/src/content/partials/turnstile/challenge-behavior.mdx
index ff0bebf920921ee..f60a738f5071a3e 100644
--- a/src/content/partials/turnstile/challenge-behavior.mdx
+++ b/src/content/partials/turnstile/challenge-behavior.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare issues challenges through the [Challenge Platform](/cloudflare-challenges/), which is the same underlying technology powering [Turnstile](/turnstile/).
diff --git a/src/content/partials/turnstile/privacy-policy.mdx b/src/content/partials/turnstile/privacy-policy.mdx
index 061f021d37cc27a..cc7c482ea104785 100644
--- a/src/content/partials/turnstile/privacy-policy.mdx
+++ b/src/content/partials/turnstile/privacy-policy.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
+As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/proxied-hostnames.mdx b/src/content/partials/turnstile/proxied-hostnames.mdx
index e9d1fd903e735be..e8beeab649b6d39 100644
--- a/src/content/partials/turnstile/proxied-hostnames.mdx
+++ b/src/content/partials/turnstile/proxied-hostnames.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your hostname is proxied through Cloudflare, visitors may experience challenges on your webpages.
diff --git a/src/content/partials/turnstile/security-requirements.mdx b/src/content/partials/turnstile/security-requirements.mdx
index 2569ee7839e2ca3..7a31837435e6e89 100644
--- a/src/content/partials/turnstile/security-requirements.mdx
+++ b/src/content/partials/turnstile/security-requirements.mdx
@@ -1,7 +1,9 @@
 ---
 {}
+
 ---
 
+
 - Server-side validation is mandatory. It is critical to enforce Turnstile tokens with the Siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. You must call Siteverify to complete your Turnstile configuration. Otherwise, it is incomplete and will result in zeroes for token validation when viewing your metrics in [Turnstile Analytics](/turnstile/turnstile-analytics/).
 
 - Tokens expire after 300 seconds (5 minutes). Each token can only be validated once. Expired or used tokens must be replaced with fresh challenges.
diff --git a/src/content/partials/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/siteverify-warning.mdx
index 979c06c7a94acd4..4e5b0a232868dfd 100644
--- a/src/content/partials/turnstile/siteverify-warning.mdx
+++ b/src/content/partials/turnstile/siteverify-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Warning]
diff --git a/src/content/partials/turnstile/siteverify.mdx b/src/content/partials/turnstile/siteverify.mdx
index 775e57ebf87175b..59ba0e6f92f190a 100644
--- a/src/content/partials/turnstile/siteverify.mdx
+++ b/src/content/partials/turnstile/siteverify.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 It is important to [call the Siteverify API](/turnstile/get-started/server-side-validation/). Without calling Siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
 
 - Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
 - Tokens expire after five minutes. Validation must occur within this window to be effective.
-- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
+- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/test-secret-key.mdx b/src/content/partials/turnstile/test-secret-key.mdx
index 142da6b947bd3e3..67d4fb5139a1840 100644
--- a/src/content/partials/turnstile/test-secret-key.mdx
+++ b/src/content/partials/turnstile/test-secret-key.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 You can test the dummy token generated with testing sitekey via Siteverify API with the testing secret key. Your production secret keys will reject dummy tokens.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/test-sitekey.mdx b/src/content/partials/turnstile/test-sitekey.mdx
index 5bb6f0697d38eaf..5ecb3a3c4062605 100644
--- a/src/content/partials/turnstile/test-sitekey.mdx
+++ b/src/content/partials/turnstile/test-sitekey.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 You can test your Turnstile widget on your webpage without triggering an actual Cloudflare Challenge by using a testing sitekey.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/troubleshooting-steps.mdx b/src/content/partials/turnstile/troubleshooting-steps.mdx
index 471234502a31d07..8e9ff7625e051fb 100644
--- a/src/content/partials/turnstile/troubleshooting-steps.mdx
+++ b/src/content/partials/turnstile/troubleshooting-steps.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 1. Verify your browser compatibility.
-   - Turnstile supports all major browsers, except Internet Explorer.
-   - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
-   - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
+    - Turnstile supports all major browsers, except Internet Explorer.
+    - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
+    - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
 2. Disable your browser extensions.
-   - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
-   - Temporarily disable all extensions and reload the page.
+    - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
+    - Temporarily disable all extensions and reload the page.
 3. Enable JavaScript.
-   - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
+    - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
 4. Try Incognito or Private mode.
-   - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
+    - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
 5. Test another browser or device.
-   - Switch to a different browser or device to see if the issue is specific to your current setup.
+    - Switch to a different browser or device to see if the issue is specific to your current setup.
 6. Avoid VPNs or proxies.
-   - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
+    - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
 7. Switch to a different network.
-   - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
+    - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
diff --git a/src/content/partials/turnstile/widget-components.mdx b/src/content/partials/turnstile/widget-components.mdx
index a72f62cd2d99b6f..36da69ec11fc53f 100644
--- a/src/content/partials/turnstile/widget-components.mdx
+++ b/src/content/partials/turnstile/widget-components.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 Each widget gets its own unique sitekey and secret key pair, and options for configurations.
 
-| Component      | Description                                                  |
-| -------------- | ------------------------------------------------------------ |
-| Sitekey        | Public key used to invoke the Turnstile widget on your site. |
-| Secret key     | Private key used for server-side token validation.           |
-| Configurations | Mode, hostnames, appearance settings, and other options.     |
+| Component | Description |
+| --- | --- |
+| Sitekey | Public key used to invoke the Turnstile widget on your site. |
+| Secret key | Private key used for server-side token validation. |
+| Configurations | Mode, hostnames, appearance settings, and other options. |
diff --git a/src/content/partials/vectorize/vectorize-ga.mdx b/src/content/partials/vectorize/vectorize-ga.mdx
index 78ba16f7ac1273b..efd48735d4aac5d 100644
--- a/src/content/partials/vectorize/vectorize-ga.mdx
+++ b/src/content/partials/vectorize/vectorize-ga.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Vectorize is now Generally Available]
 
+
 To report bugs or give feedback, go to the [#vectorize Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
+
 :::
diff --git a/src/content/partials/vectorize/vectorize-pricing.mdx b/src/content/partials/vectorize/vectorize-pricing.mdx
index 8ff2bf6036a4c2c..9281365f50e95ed 100644
--- a/src/content/partials/vectorize/vectorize-pricing.mdx
+++ b/src/content/partials/vectorize/vectorize-pricing.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-|                                     | [Workers Free](/workers/platform/pricing/#workers) | [Workers Paid](/workers/platform/pricing/#workers)                              |
-| ----------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------- |
-| **Total queried vector dimensions** | 30 million queried vector dimensions / month       | First 50 million queried vector dimensions / month included + $0.01 per million |
-| **Total stored vector dimensions**  | 5 million stored vector dimensions                 | First 10 million stored vector dimensions + $0.05 per 100 million               |
+|                                     | [Workers Free](/workers/platform/pricing/#workers)       | [Workers Paid](/workers/platform/pricing/#workers)                              |
+| ----------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------- |
+| **Total queried vector dimensions** | 30 million queried vector dimensions / month             | First 50 million queried vector dimensions / month included + $0.01 per million |
+| **Total stored vector dimensions**  | 5 million stored vector dimensions                       | First 10 million stored vector dimensions + $0.05 per 100 million               |
 
 ### Calculating vector dimensions
 
diff --git a/src/content/partials/version-management/create-environment-situation.mdx b/src/content/partials/version-management/create-environment-situation.mdx
index f6971602bd7ee8d..63f1307158b6f24 100644
--- a/src/content/partials/version-management/create-environment-situation.mdx
+++ b/src/content/partials/version-management/create-environment-situation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Based on your organization's needs, you may need to create additional environments to test and roll out changes.
diff --git a/src/content/partials/version-management/edit-version.mdx b/src/content/partials/version-management/edit-version.mdx
index 39944dba67d8e50..385307cecb41c36 100644
--- a/src/content/partials/version-management/edit-version.mdx
+++ b/src/content/partials/version-management/edit-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,12 +11,12 @@ To change between different versions of your zone:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and a domain that has version management. The Global Configuration of your domain will load.
 3. Go to the product or feature you wish to modify.
-   - **If the product or feature is available for versioning**: The last version you were working on will load.
-   - **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
+   * **If the product or feature is available for versioning**: The last version you were working on will load.
+   * **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
 4. Ensure that the configuration or version displayed in the domain summary bar is the one you would like to work on. If not, select the version in the domain summary bar to open the version switcher.
 
 :::note
diff --git a/src/content/partials/version-management/enable-default-creation.mdx b/src/content/partials/version-management/enable-default-creation.mdx
index 8e98769c2ae8675..e4ea2ec7726c964 100644
--- a/src/content/partials/version-management/enable-default-creation.mdx
+++ b/src/content/partials/version-management/enable-default-creation.mdx
@@ -1,16 +1,19 @@
 ---
 {}
+
 ---
 
 Once you [enable](/version-management/how-to/enable/) Version Management, Cloudflare will automatically create:
 
-- **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
-- **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
+* **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
+* **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
 
 :::caution[Important]
 
+
 Any changes made to the **Global Configuration** will immediately apply to your zone and all versions of your zone, affecting live traffic.
 
+
 :::
 
 On the Environments page, you can create default environments for **Production**, **Staging**, and **Development**.
diff --git a/src/content/partials/version-management/enable-versioning.mdx b/src/content/partials/version-management/enable-versioning.mdx
index 12ef04c2c918b0e..0602c8e8c03f543 100644
--- a/src/content/partials/version-management/enable-versioning.mdx
+++ b/src/content/partials/version-management/enable-versioning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,7 +11,7 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
@@ -18,6 +19,8 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 :::note
 
+
 If you cannot enable Version Management, make sure your zone, account, and user meet the [requirements](/version-management/#requirements).
 
+
 :::
diff --git a/src/content/partials/version-management/environment-defaults.mdx b/src/content/partials/version-management/environment-defaults.mdx
index 572b0f7b00346e2..896a639507362a4 100644
--- a/src/content/partials/version-management/environment-defaults.mdx
+++ b/src/content/partials/version-management/environment-defaults.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
-- **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
-- **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
+* **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
+* **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
+* **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
diff --git a/src/content/partials/version-management/environment-definition.mdx b/src/content/partials/version-management/environment-definition.mdx
index 378169d4dcb3cba..8219f760421603b 100644
--- a/src/content/partials/version-management/environment-definition.mdx
+++ b/src/content/partials/version-management/environment-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An environment is a place to test different versions of your zone configurations.
diff --git a/src/content/partials/version-management/production-read-only-default.mdx b/src/content/partials/version-management/production-read-only-default.mdx
index 9f1294d9a8e859c..309f5eee6b6b858 100644
--- a/src/content/partials/version-management/production-read-only-default.mdx
+++ b/src/content/partials/version-management/production-read-only-default.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Production** is a read-only environment by default. This means that any version associated with **Production** also becomes read-only. This configuration prevents another member of your account from accidentally editing the version associated with your live traffic. You can change this configuration by editing the environment.
diff --git a/src/content/partials/version-management/promote-version.mdx b/src/content/partials/version-management/promote-version.mdx
index 953f69ab8ea0963..9fa55abd7e19289 100644
--- a/src/content/partials/version-management/promote-version.mdx
+++ b/src/content/partials/version-management/promote-version.mdx
@@ -1,14 +1,16 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
 
+
 To promote a version:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/test-version.mdx b/src/content/partials/version-management/test-version.mdx
index 26ffc6023ca8be6..30f9c66058586c5 100644
--- a/src/content/partials/version-management/test-version.mdx
+++ b/src/content/partials/version-management/test-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ Once you have made changes to a version, apply that version to your lowest-ranke
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/version-definition.mdx b/src/content/partials/version-management/version-definition.mdx
index 23ed20a7ece8e28..32f24171ac0cc3f 100644
--- a/src/content/partials/version-management/version-definition.mdx
+++ b/src/content/partials/version-management/version-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A version is a collection of configurations related to your zone, such as WAF custom rules and [other optimization configurations](/version-management/reference/available-configurations/).
diff --git a/src/content/partials/waf/api-create-ruleset-with-rule.mdx b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
index 18ec3b89654dcc2..04b31a71d329c75 100644
--- a/src/content/partials/waf/api-create-ruleset-with-rule.mdx
+++ b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To define a specific position for the new rule, include a `position` object in the request body according to the guidelines in [Change the order of a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/#change-the-order-of-a-rule-in-a-ruleset).
diff --git a/src/content/partials/waf/list-advantages.mdx b/src/content/partials/waf/list-advantages.mdx
index d6d8663d04e3c6e..d5fed7a8acd3fbc 100644
--- a/src/content/partials/waf/list-advantages.mdx
+++ b/src/content/partials/waf/list-advantages.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
-- When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
-- When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
-- Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
+* When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
+* When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
+* Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
 
 When you update the content of a list, any rules that use the list are automatically updated, so you can make a single change to your list rather than modify rules individually.
 
diff --git a/src/content/partials/waf/managed-lists.mdx b/src/content/partials/waf/managed-lists.mdx
index aebc0ae400a11c4..8b6a68a42f9fb86 100644
--- a/src/content/partials/waf/managed-lists.mdx
+++ b/src/content/partials/waf/managed-lists.mdx
@@ -6,8 +6,8 @@
 | ----------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
 | Cloudflare Open Proxies                         | `cf.open_proxies`   | IP addresses of known open HTTP and SOCKS proxy endpoints, which are frequently used to launch attacks and hide attackers identity. |
 | Cloudflare Anonymizers                          | `cf.anonymizer`     | IP addresses of known anonymizers (Open SOCKS Proxies, VPNs, and TOR nodes).                                                        |
-| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers.                                                                                                  |
+| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers. |
 | Cloudflare Malware                              | `cf.malware`        | IP addresses of known sources of malware.                                                                                           |
 | Cloudflare Botnets, Command and Control Servers | `cf.botnetcc`       | IP addresses of known botnet command-and-control servers.                                                                           |
 
-<br />
+<br />
\ No newline at end of file
diff --git a/src/content/partials/waf/open-ports-blocked-traffic.mdx b/src/content/partials/waf/open-ports-blocked-traffic.mdx
index e360487eafc6582..98358a33d289ffd 100644
--- a/src/content/partials/waf/open-ports-blocked-traffic.mdx
+++ b/src/content/partials/waf/open-ports-blocked-traffic.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Due to the nature of Cloudflare's anycast network, ports other than `80` and `443` will be open so that Cloudflare can serve traffic for other customers on these ports. In general, Cloudflare makes available several different products on [Cloudflare IPs](https://www.cloudflare.com/ips), so you can expect tools like Netcat and security scanners to report these non-standard ports as open in specific conditions. If you have questions on security compliance, review [Cloudflare's certifications and compliance resources](https://www.cloudflare.com/en-gb/trust-hub/compliance-resources/) and contact your Cloudflare enterprise account manager for more information.
diff --git a/src/content/partials/waf/rate-limiting-best-practices.mdx b/src/content/partials/waf/rate-limiting-best-practices.mdx
index 0ef94060427faa0..5f059b73120f923 100644
--- a/src/content/partials/waf/rate-limiting-best-practices.mdx
+++ b/src/content/partials/waf/rate-limiting-best-practices.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
-- [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
-- [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
-- [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
-- [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
+* [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
+* [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
+* [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
+* [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
+* [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
diff --git a/src/content/partials/waf/rate-limiting-rule-parameters.mdx b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
index ecbeba6002d94e2..00a4d92d21e6462 100644
--- a/src/content/partials/waf/rate-limiting-rule-parameters.mdx
+++ b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-- An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
-- An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
+* An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
+* An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
 
 Besides these two parameters, rate limiting rules require the following additional parameters:
 
-- **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
-- **Period**: The period of time to consider (in seconds) when evaluating the rate.
-- **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
-- **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
-- **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
+* **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
+* **Period**: The period of time to consider (in seconds) when evaluating the rate.
+* **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
+* **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
+* **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
diff --git a/src/content/partials/waf/rules-next-steps-table.mdx b/src/content/partials/waf/rules-next-steps-table.mdx
index b2513ef838112da..8f12446af3318fa 100644
--- a/src/content/partials/waf/rules-next-steps-table.mdx
+++ b/src/content/partials/waf/rules-next-steps-table.mdx
@@ -6,9 +6,9 @@ params:
 
 import { Markdown } from "~/components";
 
-| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                       |
+| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                     |
 | Update a rule             | <p>Use the [Update a zone ruleset rule](/api/resources/rulesets/methods/update/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Update a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/).</p> |
 | Delete a rule             | <p>Use the [Delete a zone ruleset rule](/api/resources/rulesets/methods/delete/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Delete a rule in a ruleset](/ruleset-engine/rulesets-api/delete-rule/).</p> |
 
diff --git a/src/content/partials/waiting-room/change-queueing-method.mdx b/src/content/partials/waiting-room/change-queueing-method.mdx
index 3a7226abca98756..3ff0fa35e97cda9 100644
--- a/src/content/partials/waiting-room/change-queueing-method.mdx
+++ b/src/content/partials/waiting-room/change-queueing-method.mdx
@@ -1,14 +1,17 @@
 ---
 {}
+
 ---
 
 Though you can change your [queueing method](/waiting-room/reference/queueing-methods/), it may affect users if your waiting room is actively queueing:
 
-- **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
-- **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
+* **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
+* **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
 
 :::note
 
+
 If you change the queueing method from FIFO > Random > FIFO, users will be ordered by their original entry time.
 
+
 :::
diff --git a/src/content/partials/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/queue-all.mdx
index fe401b22131a2d6..f8625465ac3beeb 100644
--- a/src/content/partials/waiting-room/queue-all.mdx
+++ b/src/content/partials/waiting-room/queue-all.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To queue all visitors prior to a time-based offering, set up a pre-queue as part of a [waiting room event](/waiting-room/additional-options/create-events/#create-an-event-from-the-dashboard).
diff --git a/src/content/partials/waiting-room/queue-some.mdx b/src/content/partials/waiting-room/queue-some.mdx
index 373a1bf37d6b081..a2ae7dd6d08055a 100644
--- a/src/content/partials/waiting-room/queue-some.mdx
+++ b/src/content/partials/waiting-room/queue-some.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To queue visitors only when necessary:
diff --git a/src/content/partials/warp-client/modes-options.mdx b/src/content/partials/warp-client/modes-options.mdx
index 2965f0ed7c28f20..9582cee987393f3 100644
--- a/src/content/partials/warp-client/modes-options.mdx
+++ b/src/content/partials/warp-client/modes-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## WARP modes
@@ -22,11 +23,11 @@ Beyond the two modes of operation, the WARP app lets you configure additional op
 
 The following is a list of options you can configure in the **Connection** tab:
 
-- **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
-- **DNS Protocol**: The available options depend on the WARP mode you have enabled:
-  - **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
-  - **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
-  - **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
-- **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
+* **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
+* **DNS Protocol**: The available options depend on the WARP mode you have enabled:
+  * **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
+  * **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
+  * **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
+* **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
 
 For the **Advanced** options, refer to [Exclude or include network traffic with WARP](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/) for more information.
diff --git a/src/content/partials/web-analytics/web-analytics-definition.mdx b/src/content/partials/web-analytics/web-analytics-definition.mdx
index 1b6186550086a2c..1e5015687b288cc 100644
--- a/src/content/partials/web-analytics/web-analytics-definition.mdx
+++ b/src/content/partials/web-analytics/web-analytics-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Web Analytics provides free, privacy-first analytics for your website without changing your DNS or using Cloudflare’s proxy. Cloudflare Web Analytics helps you understand the performance of your web pages as experienced by your site visitors.
diff --git a/src/content/partials/web-analytics/web-analytics-notifications.mdx b/src/content/partials/web-analytics/web-analytics-notifications.mdx
index b0d9f16da41095b..6c43aff254d6a41 100644
--- a/src/content/partials/web-analytics/web-analytics-notifications.mdx
+++ b/src/content/partials/web-analytics/web-analytics-notifications.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Web Analytics uses Cloudflare's Notification service. When enabled, Web Analytics sends you a weekly report with aggregate visits, page views and median page load time for all your sites, so you can monitor their performance.
diff --git a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
index 859414aab8041e6..083546fd2a119b7 100644
--- a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
+++ b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
index f57d62227d76b86..e713539e0af17a5 100644
--- a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
+++ b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For Cloudflare to automatically add the JavaScript snippet, your pages need to have valid HTML.
@@ -19,7 +20,9 @@ For Web Analytics to correctly insert the JavaScript snippet, you would need val
 		<title>Title</title>
 	</head>
 	<body>
+
 		<p>Hello world.</p>
+
 	</body>
 </html>
 ```
diff --git a/src/content/partials/web3/cloudflare-settings.mdx b/src/content/partials/web3/cloudflare-settings.mdx
index c557eb6be68904f..652075c6ca43719 100644
--- a/src/content/partials/web3/cloudflare-settings.mdx
+++ b/src/content/partials/web3/cloudflare-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once your gateway becomes [active](/web3/reference/gateway-status/), you can customize the Cloudflare settings associated with your hostname.
diff --git a/src/content/partials/web3/create-gateway-api.mdx b/src/content/partials/web3/create-gateway-api.mdx
index 8b00c7b740ad9b5..e1952e8378a32e6 100644
--- a/src/content/partials/web3/create-gateway-api.mdx
+++ b/src/content/partials/web3/create-gateway-api.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 To create a gateway using the API, send a [`POST`](/api/resources/web3/subresources/hostnames/methods/create/) request that includes the following parameters:
 
-- `name`: The hostname that will point to the target gateway via a `CNAME` record.
-- `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
+* `name`: The hostname that will point to the target gateway via a `CNAME` record.
+* `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
 
 If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
@@ -26,18 +27,18 @@ The response contains the complete definition of the new gateway.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "<WEB3_GATEWAY_ID>",
-		"name": "gateway.example.com",
-		"description": "This is my IPFS gateway.",
-		"status": "active",
-		"target": "ipfs",
-		"dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
-		"created_on": "<CREATED_ON_DATE>",
-		"modified_on": "<MODIFIED_ON_DATE>"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "<WEB3_GATEWAY_ID>",
+    "name": "gateway.example.com",
+    "description": "This is my IPFS gateway.",
+    "status": "active",
+    "target": "ipfs",
+    "dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
+    "created_on": "<CREATED_ON_DATE>",
+    "modified_on": "<MODIFIED_ON_DATE>"
+  }
 }
 ```
diff --git a/src/content/partials/web3/pricing-page-reference.mdx b/src/content/partials/web3/pricing-page-reference.mdx
index 80deb4fcdfdd040..28fa234c7caadd1 100644
--- a/src/content/partials/web3/pricing-page-reference.mdx
+++ b/src/content/partials/web3/pricing-page-reference.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 For more pricing details, refer to the [Web3 product page](https://www.cloudflare.com/application-services/products/web3/).
 
+
 :::
diff --git a/src/content/partials/workers-ai/custom_requirements.mdx b/src/content/partials/workers-ai/custom_requirements.mdx
index dfdd8c4a50439f7..8a34dddf8cb8d82 100644
--- a/src/content/partials/workers-ai/custom_requirements.mdx
+++ b/src/content/partials/workers-ai/custom_requirements.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Custom requirements]
 
+
 If you have custom requirements like private custom models or higher limits, complete the [Custom Requirements Form](https://forms.gle/axnnpGDb6xrmR31T6). Cloudflare will contact you with next steps.
 
+
 :::
diff --git a/src/content/partials/workers-ai/file_issues.mdx b/src/content/partials/workers-ai/file_issues.mdx
index 0e250e4dcc7c3b7..3f30780c51c35ed 100644
--- a/src/content/partials/workers-ai/file_issues.mdx
+++ b/src/content/partials/workers-ai/file_issues.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Workers AI is now Generally Available]
 
+
 To report bugs or give feedback, go to the [#workers-ai Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
+
 :::
diff --git a/src/content/partials/workers-ai/openai-compatibility.mdx b/src/content/partials/workers-ai/openai-compatibility.mdx
index e245b363ffe1571..64bc69da90146c0 100644
--- a/src/content/partials/workers-ai/openai-compatibility.mdx
+++ b/src/content/partials/workers-ai/openai-compatibility.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Workers AI supports OpenAI compatible endpoints for [text generation](/workers-ai/models/) (`/v1/chat/completions`) and [text embedding models](/workers-ai/models/) (`/v1/embeddings`). This allows you to use the same code as you would for your OpenAI commands, but swap in Workers AI easily.
diff --git a/src/content/partials/workers-vpc/create-tunnel-steps.mdx b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
index 4ec8b8731f765c2..9c0aef59ee08b46 100644
--- a/src/content/partials/workers-vpc/create-tunnel-steps.mdx
+++ b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
@@ -1,7 +1,7 @@
 ---
 {}
----
 
+---
 import { Steps } from "~/components";
 
 <Steps>
diff --git a/src/content/partials/workers-vpc/required-roles.mdx b/src/content/partials/workers-vpc/required-roles.mdx
index be0cad6ee37c062..0af2217c4362e96 100644
--- a/src/content/partials/workers-vpc/required-roles.mdx
+++ b/src/content/partials/workers-vpc/required-roles.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Workers VPC uses the following account roles:
diff --git a/src/content/partials/workers/ai-local-usage-charges.mdx b/src/content/partials/workers/ai-local-usage-charges.mdx
index 392a77552fc2ac9..0747f627b173468 100644
--- a/src/content/partials/workers/ai-local-usage-charges.mdx
+++ b/src/content/partials/workers/ai-local-usage-charges.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Workers AI local development usage charges]
 
+
 Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
 
+
 :::
diff --git a/src/content/partials/workers/c3-definition.mdx b/src/content/partials/workers/c3-definition.mdx
index 06920a6667d56af..5cad05a047d4f02 100644
--- a/src/content/partials/workers/c3-definition.mdx
+++ b/src/content/partials/workers/c3-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [C3 (create-cloudflare-cli)](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare) is a command-line tool designed to help you set up and deploy new applications to Cloudflare. In addition to speed, it leverages officially developed templates for Workers and framework-specific setup guides to ensure each new application that you set up follows Cloudflare and any third-party best practices for deployment on the Cloudflare network.
diff --git a/src/content/partials/workers/compute-per-request.mdx b/src/content/partials/workers/compute-per-request.mdx
index 3114c34331ad0a5..78671c444b721be 100644
--- a/src/content/partials/workers/compute-per-request.mdx
+++ b/src/content/partials/workers/compute-per-request.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 Most Workers are a variation on the default Workers flow:
 
diff --git a/src/content/partials/workers/content_and_contentoptions.mdx b/src/content/partials/workers/content_and_contentoptions.mdx
index d033ded8e7aef53..0cd4835706f96a9 100644
--- a/src/content/partials/workers/content_and_contentoptions.mdx
+++ b/src/content/partials/workers/content_and_contentoptions.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Content and ContentOptions]
 
+
 Refer to [Global types](/workers/runtime-apis/html-rewriter/#global-types) for more information on `Content` and `ContentOptions`.
 
+
 :::
diff --git a/src/content/partials/workers/dash-creation-next-steps.mdx b/src/content/partials/workers/dash-creation-next-steps.mdx
index 7e62d21c0a45c4d..3a4659d03dc4f7e 100644
--- a/src/content/partials/workers/dash-creation-next-steps.mdx
+++ b/src/content/partials/workers/dash-creation-next-steps.mdx
@@ -13,7 +13,6 @@ Once you have created your Worker script, you can edit and deploy your Worker us
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your application.
 3. Select **Edit Code**.
 
diff --git a/src/content/partials/workers/env_and_secrets.mdx b/src/content/partials/workers/env_and_secrets.mdx
index 60002bb1713e2d1..7efe87d33bc8f1b 100644
--- a/src/content/partials/workers/env_and_secrets.mdx
+++ b/src/content/partials/workers/env_and_secrets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Compare secrets and environment variables
diff --git a/src/content/partials/workers/envvar-example.mdx b/src/content/partials/workers/envvar-example.mdx
index 1a778eee6e6cefa..a3680630114446c 100644
--- a/src/content/partials/workers/envvar-example.mdx
+++ b/src/content/partials/workers/envvar-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/workers/fetch-html-example-js.mdx b/src/content/partials/workers/fetch-html-example-js.mdx
index 132f5b1a1063882..4e19efbae720a72 100644
--- a/src/content/partials/workers/fetch-html-example-js.mdx
+++ b/src/content/partials/workers/fetch-html-example-js.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		/**
-		 * Replace `remote` with the host you wish to send requests to
-		 */
-		const remote = "https://example.com";
+  async fetch(request) {
+    /**
+     * Replace `remote` with the host you wish to send requests to
+     */
+    const remote = "https://example.com";
 
-		return await fetch(remote, request);
-	},
+    return await fetch(remote, request);
+  },
 };
 ```
diff --git a/src/content/partials/workers/get-started-dash.mdx b/src/content/partials/workers/get-started-dash.mdx
index c04cc67a0123925..63f3c464720f5e4 100644
--- a/src/content/partials/workers/get-started-dash.mdx
+++ b/src/content/partials/workers/get-started-dash.mdx
@@ -1,11 +1,10 @@
 ---
 {}
----
 
+---
 import { DashButton } from "~/components";
 
 To create your first Worker using the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/partials/workers/isolate-cpu-flexibility.mdx b/src/content/partials/workers/isolate-cpu-flexibility.mdx
index e8cd1b510fbfbe6..2b2c293912bb364 100644
--- a/src/content/partials/workers/isolate-cpu-flexibility.mdx
+++ b/src/content/partials/workers/isolate-cpu-flexibility.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Each [isolate](/workers/reference/how-workers-works/#isolates) has some built-in flexibility to allow for cases where your Worker infrequently runs over the configured limit. If your Worker starts hitting the limit consistently, its execution will be terminated according to the limit configured.
diff --git a/src/content/partials/workers/isolate-description.mdx b/src/content/partials/workers/isolate-description.mdx
index a70b5337ab358ab..48b5a2edfba0141 100644
--- a/src/content/partials/workers/isolate-description.mdx
+++ b/src/content/partials/workers/isolate-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A single instance of the runtime can run hundreds or thousands of isolates, seamlessly switching between them. Each isolate's memory is completely isolated, so each piece of code is protected from other untrusted or user-written code on the runtime. Isolates are also designed to start very quickly. Instead of creating a virtual machine for each function, an isolate is created within an existing environment. This model eliminates the cold starts of the virtual machine model.
diff --git a/src/content/partials/workers/limits_increase.mdx b/src/content/partials/workers/limits_increase.mdx
index fd226c8f5cbf150..e5fa0351f7a8510 100644
--- a/src/content/partials/workers/limits_increase.mdx
+++ b/src/content/partials/workers/limits_increase.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Need a higher limit?]
 
+
 To request an adjustment to a limit, complete the [Limit Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). If the limit can be increased, Cloudflare will contact you with next steps.
 
+
 :::
diff --git a/src/content/partials/workers/nodejs-compat-howto.mdx b/src/content/partials/workers/nodejs-compat-howto.mdx
index 40e11bbb98811e6..2dee652a3cb15d3 100644
--- a/src/content/partials/workers/nodejs-compat-howto.mdx
+++ b/src/content/partials/workers/nodejs-compat-howto.mdx
@@ -1,9 +1,11 @@
 ---
 {}
+
 ---
 
 :::note
 
 To enable built-in Node.js APIs and polyfills, add the nodejs_compat compatibility flag to your [Wrangler configuration file](/workers/wrangler/configuration/). This also enables nodejs_compat_v2 as long as your compatibility date is 2024-09-23 or later. [Learn more about the Node.js compatibility flag and v2](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
 
+
 :::
diff --git a/src/content/partials/workers/playground-callout.mdx b/src/content/partials/workers/playground-callout.mdx
index c854466893a08ef..571ac3076e049f8 100644
--- a/src/content/partials/workers/playground-callout.mdx
+++ b/src/content/partials/workers/playground-callout.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Try the Playground]
 
+
 The quickest way to experiment with Cloudflare Workers is in the [Playground](https://workers.cloudflare.com/playground). The Playground does not require any setup. It is an instant way to preview and test a Worker directly in the browser.
 
+
 :::
diff --git a/src/content/partials/workers/prereqs.mdx b/src/content/partials/workers/prereqs.mdx
index 3d041a42f4203a5..70c0d166cb8f710 100644
--- a/src/content/partials/workers/prereqs.mdx
+++ b/src/content/partials/workers/prereqs.mdx
@@ -1,15 +1,13 @@
 ---
 {}
+
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
 1. Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up/workers-and-pages).
 2. Install [`Node.js`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
 
 <Details header="Node.js version manager">
-	Use a Node version manager like [Volta](https://volta.sh/) or
-	[nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change
-	Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed
-	later in this guide, requires a Node version of `16.17.0` or later.
+Use a Node version manager like [Volta](https://volta.sh/) or [nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed later in this guide, requires a Node version of `16.17.0` or later.
 </Details>
diff --git a/src/content/partials/workers/redirect-example-js.mdx b/src/content/partials/workers/redirect-example-js.mdx
index 9b764fa66e236ce..b5b219d970896c9 100644
--- a/src/content/partials/workers/redirect-example-js.mdx
+++ b/src/content/partials/workers/redirect-example-js.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const destinationURL = "https://example.com";
-		const statusCode = 301;
-		return Response.redirect(destinationURL, statusCode);
-	},
+  async fetch(request) {
+    const destinationURL = "https://example.com";
+    const statusCode = 301;
+    return Response.redirect(destinationURL, statusCode);
+  },
 };
 ```
diff --git a/src/content/partials/workers/remote-binding-note.mdx b/src/content/partials/workers/remote-binding-note.mdx
index 14a8b741425af69..f05321bd7cd36e3 100644
--- a/src/content/partials/workers/remote-binding-note.mdx
+++ b/src/content/partials/workers/remote-binding-note.mdx
@@ -6,4 +6,4 @@
 
 To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. Learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/workers/request-dot-clone-warning.mdx b/src/content/partials/workers/request-dot-clone-warning.mdx
index 5371525c77f704e..5e9640d3f34d8d2 100644
--- a/src/content/partials/workers/request-dot-clone-warning.mdx
+++ b/src/content/partials/workers/request-dot-clone-warning.mdx
@@ -9,4 +9,4 @@ The body of a [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request
 To avoid errors, create a clone of the Request object with `request.clone()` for each subsequent attempt to access a Request's body.
 Keep in mind that Workers have a [memory limit of 128 MB per Worker](/workers/platform/limits/#memory) and loading particularly large files into a Worker's memory multiple times may reach this limit. To ensure memory usage does not reach this limit, consider using [Streams](/workers/runtime-apis/streams/).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/workers/respond-another-site-example-js.mdx b/src/content/partials/workers/respond-another-site-example-js.mdx
index 1e55c7a658919ba..05c6f264b81aa7f 100644
--- a/src/content/partials/workers/respond-another-site-example-js.mdx
+++ b/src/content/partials/workers/respond-another-site-example-js.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		function MethodNotAllowed(request) {
-			return new Response(`Method ${request.method} not allowed.`, {
-				status: 405,
-				headers: {
-					Allow: "GET",
-				},
-			});
-		}
-		// Only GET requests work with this proxy.
-		if (request.method !== "GET") return MethodNotAllowed(request);
-		return fetch(`https://example.com`);
-	},
+  async fetch(request) {
+    function MethodNotAllowed(request) {
+      return new Response(`Method ${request.method} not allowed.`, {
+        status: 405,
+        headers: {
+          Allow: "GET",
+        },
+      });
+    }
+    // Only GET requests work with this proxy.
+    if (request.method !== "GET") return MethodNotAllowed(request);
+    return fetch(`https://example.com`);
+  },
 };
 ```
diff --git a/src/content/partials/workers/return-html-example-js.mdx b/src/content/partials/workers/return-html-example-js.mdx
index 41b5a8db682bcdc..24bed7993c20042 100644
--- a/src/content/partials/workers/return-html-example-js.mdx
+++ b/src/content/partials/workers/return-html-example-js.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const html = `<!DOCTYPE html>
+  async fetch(request) {
+    const html = `<!DOCTYPE html>
 		<body>
 		  <h1>Hello World</h1>
 		  <p>This markup was generated by a Cloudflare Worker.</p>
 		</body>`;
 
-		return new Response(html, {
-			headers: {
-				"content-type": "text/html;charset=UTF-8",
-			},
-		});
-	},
+    return new Response(html, {
+      headers: {
+        "content-type": "text/html;charset=UTF-8",
+      },
+    });
+  },
 };
 ```
diff --git a/src/content/partials/workers/return-json-example-js.mdx b/src/content/partials/workers/return-json-example-js.mdx
index e81939c499570ad..5222c0a889a5073 100644
--- a/src/content/partials/workers/return-json-example-js.mdx
+++ b/src/content/partials/workers/return-json-example-js.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const data = {
-			hello: "world",
-		};
+  async fetch(request) {
+    const data = {
+      hello: "world",
+    };
 
-		return Response.json(data);
-	},
+    return Response.json(data);
+  },
 };
 ```
diff --git a/src/content/partials/workers/service-binding-rpc-example.mdx b/src/content/partials/workers/service-binding-rpc-example.mdx
index 0e2f10a6dad4f77..1f67ca0636f4dea 100644
--- a/src/content/partials/workers/service-binding-rpc-example.mdx
+++ b/src/content/partials/workers/service-binding-rpc-example.mdx
@@ -77,6 +77,7 @@ Worker A can declare a [binding](/workers/runtime-apis/bindings) to Worker B:
 
 Making it possible for Worker A to call the `add()` method from Worker B:
 
+
 <Tabs syncKey="workersExamples">
 
 <TypeScriptExample omitTabs={true}>
diff --git a/src/content/partials/workers/storage-products-table.mdx b/src/content/partials/workers/storage-products-table.mdx
index 47d0a3281d70912..9b832c39da70b20 100644
--- a/src/content/partials/workers/storage-products-table.mdx
+++ b/src/content/partials/workers/storage-products-table.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-| Use-case                                  | Product                                          | Ideal for                                                                                                                                              |
-| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Key-value storage                         | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                                                            |
-| Object storage / blob storage             | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.                                        |
-| Accelerate a Postgres or MySQL database   | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                               |
-| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage. |
-| Lightweight SQL database                  | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                                                           |
-| Task processing, batching and messaging   | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks.                                                          |
-| Vector search & embeddings queries        | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.                           |
-| Streaming ingestion                       | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying                         |
-| Time-series metrics                       | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL.                                |
+| Use-case | Product                                          | Ideal for                                                                                                               |
+| ------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
+| Key-value storage | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                             |
+| Object storage / blob storage | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.         |
+| Accelerate a Postgres or MySQL database | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                                            |
+| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage.  |
+| Lightweight SQL database | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                            |
+| Task processing, batching and messaging | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks. |
+| Vector search & embeddings queries | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.  |
+| Streaming ingestion | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying |
+| Time-series metrics | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL. |
\ No newline at end of file
diff --git a/src/content/partials/workers/testing-pages-functions.mdx b/src/content/partials/workers/testing-pages-functions.mdx
index 2d921130e88652f..568cbc85bd23a01 100644
--- a/src/content/partials/workers/testing-pages-functions.mdx
+++ b/src/content/partials/workers/testing-pages-functions.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Pages Functions]
 
+
 The content described on this page is also applicable to [Pages Functions](/pages/functions/). Pages Functions are Cloudflare Workers and can be thought of synonymously with Workers in this context.
 
+
 :::
diff --git a/src/content/partials/workers/tutorials-before-you-start.mdx b/src/content/partials/workers/tutorials-before-you-start.mdx
index bb2f002bb183c96..b33c0af2815ddef 100644
--- a/src/content/partials/workers/tutorials-before-you-start.mdx
+++ b/src/content/partials/workers/tutorials-before-you-start.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Before you start
diff --git a/src/content/partials/workers/workers_logs_pricing.mdx b/src/content/partials/workers/workers_logs_pricing.mdx
index 7e8c152265137aa..8772eec1debdf90 100644
--- a/src/content/partials/workers/workers_logs_pricing.mdx
+++ b/src/content/partials/workers/workers_logs_pricing.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Workers Logs is included in both the Free and Paid [Workers plans](/workers/platform/pricing/).
 
-|                  | Log Events Written                                                 | Retention |
-| ---------------- | ------------------------------------------------------------------ | --------- |
-| **Workers Free** | 200,000 per day                                                    | 3 Days    |
-| **Workers Paid** | 20 million included per month <br /> +$0.60 per additional million | 7 Days    |
+|                    | Log Events Written                                                 | Retention  |
+| ------------------ | ------------------------------------------------------------------ | ---------- |
+| **Workers Free**   | 200,000 per day                                                    | 3 Days     |
+| **Workers Paid**   | 20 million included per month <br /> +$0.60 per additional million | 7 Days     |
diff --git a/src/content/partials/workers/wrangler-commands/containers.mdx b/src/content/partials/workers/wrangler-commands/containers.mdx
index aa5f7677a4557ba..e04e280d72c1783 100644
--- a/src/content/partials/workers/wrangler-commands/containers.mdx
+++ b/src/content/partials/workers/wrangler-commands/containers.mdx
@@ -202,14 +202,14 @@ wrangler containers instances 12345678-abcd-1234-abcd-123456789abc --json
 
 ```json output
 [
-	{
-		"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
-		"name": "worker-12",
-		"state": "running",
-		"location": "sfo06",
-		"version": 3,
-		"created": "2025-06-01T12:00:00Z"
-	}
+  {
+    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+    "name": "worker-12",
+    "state": "running",
+    "location": "sfo06",
+    "version": 3,
+    "created": "2025-06-01T12:00:00Z"
+  }
 ]
 ```
 
diff --git a/src/content/partials/workers/wrangler-commands/r2-sql.mdx b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
index 5c20b7b51c03454..17cd10b4c69f8c1 100644
--- a/src/content/partials/workers/wrangler-commands/r2-sql.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
@@ -2,14 +2,7 @@
 {}
 ---
 
-import {
-	Render,
-	AnchorHeading,
-	Type,
-	MetaInfo,
-	WranglerCommand,
-	WranglerNamespace,
-} from "~/components";
+import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand, WranglerNamespace } from "~/components";
 
 :::note
 
@@ -17,4 +10,4 @@ R2 SQL is currently in open beta. Report R2 SQL bugs in [GitHub](https://github.
 
 :::
 
-<WranglerCommand command="r2 sql query" headingLevel={3} />
+<WranglerCommand command="r2 sql query" headingLevel={3} />
\ No newline at end of file
diff --git a/src/content/partials/workers/wrangler-commands/r2.mdx b/src/content/partials/workers/wrangler-commands/r2.mdx
index 692fb87d223e3e1..3046ac2f72125bb 100644
--- a/src/content/partials/workers/wrangler-commands/r2.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2.mdx
@@ -2,13 +2,7 @@
 {}
 ---
 
-import {
-	Render,
-	AnchorHeading,
-	Type,
-	MetaInfo,
-	WranglerCommand,
-} from "~/components";
+import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand } from "~/components";
 
 ## `r2 bucket`
 
@@ -19,24 +13,21 @@ Interact with buckets in an R2 store.
 The `r2 bucket` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 bucket create" headingLevel={3} />
+<WranglerCommand command="r2 bucket create" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket info" headingLevel={3} />
+<WranglerCommand command="r2 bucket info" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket list" headingLevel={3} />
+<WranglerCommand command="r2 bucket list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog get" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog get" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog compaction enable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog compaction enable" headingLevel={3}/>
 
 Examples:
 
@@ -48,10 +39,7 @@ npx wrangler r2 bucket catalog compaction enable my-bucket --token <TOKEN>
 npx wrangler r2 bucket catalog compaction enable my-bucket my-namespace my-table --target-size 256
 ```
 
-<WranglerCommand
-	command="r2 bucket catalog compaction disable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog compaction disable" headingLevel={3}/>
 
 Examples:
 
@@ -62,66 +50,60 @@ npx wrangler r2 bucket catalog compaction disable my-bucket
 # Disable table-level compaction
 npx wrangler r2 bucket catalog compaction disable my-bucket my-namespace my-table
 ```
+<WranglerCommand command="r2 bucket catalog snapshot-expiration enable" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog snapshot-expiration enable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog snapshot-expiration disable" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog snapshot-expiration disable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket cors set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors set" headingLevel={3} />
+<WranglerCommand command="r2 bucket cors delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket cors list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors list" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url get" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain add" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain update" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain update" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain get" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock add" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock set" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification create" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification create" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification list" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy get" headingLevel={3} />
 
 ## `r2 object`
 
@@ -132,8 +114,8 @@ Interact with R2 objects.
 The `r2 object` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 object get" headingLevel={3} />
+<WranglerCommand command="r2 object get" headingLevel={3}/>
 
-<WranglerCommand command="r2 object put" headingLevel={3} />
+<WranglerCommand command="r2 object put" headingLevel={3}/>
 
-<WranglerCommand command="r2 object delete" headingLevel={3} />
+<WranglerCommand command="r2 object delete" headingLevel={3}/>
\ No newline at end of file
diff --git a/src/content/partials/workflows/workflows-type-parameters.mdx b/src/content/partials/workflows/workflows-type-parameters.mdx
index 37e0134270468b8..0ad91e5f88a4fcf 100644
--- a/src/content/partials/workflows/workflows-type-parameters.mdx
+++ b/src/content/partials/workflows/workflows-type-parameters.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::caution
 
diff --git a/src/content/partials/zaraz/zaraz-definition.mdx b/src/content/partials/zaraz/zaraz-definition.mdx
index 2b5e8f884cd31f7..b17ee4fa2792f6f 100644
--- a/src/content/partials/zaraz/zaraz-definition.mdx
+++ b/src/content/partials/zaraz/zaraz-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Zaraz gives you complete control over third-party tools and services for your website, and allows you to offload them to Cloudflare's edge, improving the speed and security of your website. With Cloudflare Zaraz you can load tools such as analytics tools, advertising pixels and scripts, chatbots, marketing automation tools, and more, in the most optimized way.
diff --git a/src/pages/agent-setup/index.astro b/src/pages/agent-setup/index.astro
index e5e4a7adc39235c..9c6aa0f8bc91720 100644
--- a/src/pages/agent-setup/index.astro
+++ b/src/pages/agent-setup/index.astro
@@ -24,59 +24,29 @@ const props = {
 
 <StarlightPage {...props}>
 	<p class="agent-setup-lede">
-		Install an agent of your choice, connect Cloudflare <a
-			href="https://github.com/cloudflare/skills"
-			target="_blank"
-			rel="noopener noreferrer">Skills &nearr;</a
-		> and <a
-			href="https://blog.cloudflare.com/code-mode-mcp/"
-			target="_blank"
-			rel="noopener noreferrer">Code Mode API &nearr;</a
-		> and <a
-			href="https://github.com/cloudflare/mcp-server-cloudflare"
-			target="_blank"
-			rel="noopener noreferrer">domain-specific &nearr;</a
-		> MCP servers, and start deploying to Cloudflare from your editor or terminal.
+		Install an agent of your choice, connect Cloudflare <a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">Skills &nearr;</a> and <a href="https://blog.cloudflare.com/code-mode-mcp/" target="_blank" rel="noopener noreferrer">Code Mode API &nearr;</a> and <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific &nearr;</a> MCP servers, and start deploying to Cloudflare from your editor or terminal.
 	</p>
 
 	<div class="agent-setup-paths not-content">
 		<!-- Left: quick path -->
-		<div
-			class="agent-setup-path agent-setup-path--quick"
-			style="flex-basis: 60%;"
-		>
+		<div class="agent-setup-path agent-setup-path--quick" style="flex-basis: 60%;">
 			<p class="agent-setup-path-eyebrow">Quick setup</p>
 			<p class="agent-setup-path-title">Already have an agent?</p>
-			<p class="agent-setup-path-desc">
-				Paste this into any AI coding agent to install Cloudflare agent tooling
-				in one step.
-			</p>
-			<PromptCopyBlock
-				text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md"
-				hideLabel
-			/>
+			<p class="agent-setup-path-desc">Paste this into any AI coding agent to install Cloudflare agent tooling in one step.</p>
+			<PromptCopyBlock text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md" hideLabel />
 		</div>
 		<!-- Right: manual path -->
 		<div class="agent-setup-path agent-setup-path--manual">
 			<p class="agent-setup-path-eyebrow">Manual setup</p>
 			<p class="agent-setup-path-title">New to AI agents?</p>
-			<p class="agent-setup-path-desc">
-				Pick an agent, follow step-by-step setup instructions, compare
-				capabilities, and learn about the Cloudflare tools available to you.
-			</p>
-			<a href="#pick-your-agent" class="agent-setup-path-cta"
-				>Browse agents &darr;</a
-			>
+			<p class="agent-setup-path-desc">Pick an agent, follow step-by-step setup instructions, compare capabilities, and learn about the Cloudflare tools available to you.</p>
+			<a href="#pick-your-agent" class="agent-setup-path-cta">Browse agents &darr;</a>
 		</div>
 	</div>
 
 	<hr />
 
-	<div
-		class="agent-setup-section-header"
-		style="margin-top: 3.25rem;"
-		id="pick-your-agent"
-	>
+	<div class="agent-setup-section-header" style="margin-top: 3.25rem;" id="pick-your-agent">
 		<h2>Pick your agent</h2>
 		<p>Select an agent to get step-by-step setup instructions.</p>
 	</div>
@@ -138,6 +108,10 @@ const props = {
 		border-color: var(--color-cl1-gray-2);
 	}
 
+
+
+
+
 	.agent-setup-path-eyebrow {
 		font-size: 0.75rem;
 		font-weight: 700;
@@ -178,4 +152,5 @@ const props = {
 		text-decoration: underline;
 		text-underline-offset: 2px;
 	}
+
 </style>
diff --git a/src/pages/plans.astro b/src/pages/plans.astro
index e46fb3945ae4d16..38f964ff6dac9d9 100644
--- a/src/pages/plans.astro
+++ b/src/pages/plans.astro
@@ -120,8 +120,8 @@ import { ProductFeatures } from "~/components";
 			<strong>Developer products</strong>: Refer to the <a
 				href="https://www.cloudflare.com/plans/developer-platform/"
 				>Developer Platform pricing page</a
-			> or individual <a href="/directory/">product docs</a> to learn more about plans
-			and pricing.
+			> or individual <a href="/directory/">product docs</a> to learn more about
+			plans and pricing.
 		</li>
 		<li>
 			<strong>Zero Trust products</strong>: Refer to the <a

From 3c3f2f9a7d496cb2ad108f550835b835d25db44b Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 06:33:33 +0000
Subject: [PATCH 5/8] [RealtimeKit] Apply korinne's track recording edits

---
 ...2026-05-28-realtimekit-track-recording.mdx | 34 +++++++++
 .../recording-guide/track-recording.mdx       | 71 +++++++++++--------
 2 files changed, 74 insertions(+), 31 deletions(-)
 create mode 100644 src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx

diff --git a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
new file mode 100644
index 000000000000000..e4633c13a0546e5
--- /dev/null
+++ b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
@@ -0,0 +1,34 @@
+---
+title: RealtimeKit now supports track recording for per-participant audio
+description: You can now record specific participant audio tracks in RealtimeKit with the new track recording feature.
+products:
+  - realtime
+date: 2026-05-28
+---
+
+You can now record specific participant audio tracks in RealtimeKit with the new [track recording feature](/realtime/realtimekit/recording-guide/track-recording/). Track recording creates separate WebM files for each participant instead of a single composite recording, which is useful for post-processing, transcription, and regulated or content-sensitive workflows.
+
+To record specific participants, pass `user_ids` when starting a track recording:
+
+```bash
+curl --request POST \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+  "user_ids": ["user-123", "user-456"]
+}'
+```
+
+To pass `user_ids` for selective track recording, use the following minimum SDK versions:
+
+- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
+- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
+- Android Core or iOS Core: version `2.0.0` or later
+- Android UI Kit or iOS UI Kit: version `1.1.0` or later
+
+[RealtimeKit](/realtime/realtimekit/) provides SDKs and UI components so that you can build your own meeting experience on Cloudflare's global WebRTC infrastructure. Teams today build products ranging from telehealth to education on RealtimeKit for global audiences. You can get started today with our [Quickstart](/realtime/realtimekit/quickstart/) or take a look at our [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
+
+- [Track recording docs](/realtime/realtimekit/recording-guide/track-recording/)
+- [RealtimeKit Quickstart](/realtime/realtimekit/quickstart/)
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
index 50d601987d14693..d7b1839d295968b 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -8,9 +8,18 @@ products:
   - realtime
 ---
 
-Track recording records each participant's audio as a separate WebM file in RealtimeKit's Cloudflare R2 bucket. Use track recording when you need isolated speaker tracks for post-processing, transcription, compliance workflows, or audio analysis.
+Track recording lets you record participant audio as separate WebM files instead of one composite meeting recording. Use it when you need speaker-level control over what you store, process, or review.
 
-Composite recording creates one mixed meeting recording. Track recording creates one file per recorded participant peer.
+With track recording, you can record specific participant tracks by passing `user_ids`, which is useful for content-sensitive or regulated workflows where recording every participant is unnecessary. If you do not provide `user_ids`, RealtimeKit will record all participant audio tracks as separate WebM files by default.
+
+To pass `user_ids` for specific participant track recording, use the following minimum SDK versions:
+
+- Web Core: `@cloudflare/realtimekit` version `1.4.0` or later
+- Web UI Kit: `@cloudflare/realtimekit-ui`, `@cloudflare/realtimekit-react-ui`, or `@cloudflare/realtimekit-angular-ui` version `1.1.2` or later
+- Android Core or iOS Core: version `2.0.0` or later
+- Android UI Kit or iOS UI Kit: version `1.1.0` or later
+
+Track recording creates one file per recorded participant.
 
 :::note
 
@@ -22,19 +31,36 @@ Track recording currently supports audio tracks only. Video track recording is i
 
 Track recording has the following requirements and limits:
 
-| Limit                 | Description                                           |
-| --------------------- | ----------------------------------------------------- |
-| Active meeting        | The meeting must have an active live session.         |
-| Media kind            | Only `audio` layers are recorded.                     |
-| Participant selection | Pass up to `100` values in `user_ids`.                |
-| Storage               | Files are uploaded to the RealtimeKit bucket.         |
-| File retention        | RealtimeKit bucket download URLs expire after seven days. |
+| Limit | Description |
+| --- | --- |
+| Active meeting | The meeting must have an active live session. |
+| Media kind | Only `audio` layers are recorded. |
+| Participant selection | Pass up to 100 values in `user_ids`. |
+| Storage | Files are uploaded to RealtimeKit's managed R2 bucket with zero-egress fees. |
+| File retention | RealtimeKit bucket download URLs expire after seven days. |
 
 ## Start track recording
 
-To start track recording, call `POST /recordings/track` with the meeting ID.
+### Record specific participants
 
-If you omit `layers`, RealtimeKit records all participant audio. You can pass an audio layer to set a file name prefix for generated files.
+To record separate audio tracks for specific participants, call [`POST /recordings/track`](/api/resources/realtime_kit/subresources/recordings/methods/start_track_recording/) with the meeting ID and the participant `user_ids`.
+
+```bash
+curl --request POST \
+  --url https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/kit/<app_id>/recordings/track \
+  --header 'Authorization: Bearer <api_token>' \
+  --header 'Content-Type: application/json' \
+  --data '{
+  "meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
+  "user_ids": ["user-123", "user-456"]
+}'
+```
+
+RealtimeKit records current and future participant peers whose user_id matches the allowlist. Participants whose user_id is not listed are not recorded.
+
+### Record all participants as separate tracks
+
+Omit `user_ids` to record separate audio tracks for all participants in the live meeting. RealtimeKit creates one WebM file for each recorded participant peer.
 
 ```bash
 curl --request POST \
@@ -63,26 +89,9 @@ The response includes a recording ID. Use this ID to stop or fetch the recording
 }
 ```
 
-## Record selected participants
-
-Pass `user_ids` to record only specific participants. RealtimeKit records current and future participant peers whose `user_id` matches the allowlist.
-
-:::caution
-
-To use selective track recording with `user_ids`, contact your Cloudflare account team or RealtimeKit support.
-
-:::
-
-```json
-{
-	"meeting_id": "97440c6a-140b-40a9-9499-b23fd7a3868a",
-	"user_ids": ["user-123", "user-456"]
-}
-```
-
-## Set file name prefix
+## Customize file names with prefixes
 
-Use `file_name_prefix` to prefix every generated track recording file.
+Use `layers.default.file_name_prefix` to prefix every generated track recording file.
 
 ```json
 {
@@ -120,7 +129,7 @@ After track recording stops, RealtimeKit uploads the per-participant WebM files
 
 Track recording uses the same recording status lifecycle as composite recording. To monitor status, refer to [Monitor Recording Status](/realtime/realtimekit/recording-guide/monitor-status/).
 
-When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. The `download_url` field contains the recorded WebM files for participant peers.
+When the recording reaches `UPLOADED`, fetch the recording details or listen for the `recording.statusUpdate` webhook. For track recordings, `download_url` contains per-participant WebM file URLs grouped by layer.
 
 ```json
 {

From ea37dec262cd8b556dd40a04d8b56b33b8284aec Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 07:23:39 +0000
Subject: [PATCH 6/8] Applied review fixes, all checks pass.

Co-authored-by: korinne <korinne@users.noreply.github.com>
---
 .../realtimekit/recording-guide/index.mdx     |  2 +-
 .../recording-guide/track-recording.mdx       | 20 +++++++++----------
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
index 0818278555efc44..dd3305069dadec9 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
@@ -19,7 +19,7 @@ Visit the following pages to learn more about recording meetings:
 
 RealtimeKit can record the audio and video of multiple users in a meeting, as well as interactions with RealtimeKit plugins, in a single file using composite recording mode. RealtimeKit can also record separate participant audio tracks using track recording.
 
-## How does composite recording work?
+## How does composite recording work
 
 Composite recordings are powered by anonymous virtual bot users who join your
 meeting, record it, and then upload it to RealtimeKit's Cloudflare R2 bucket. For video files,
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
index d7b1839d295968b..29a017d6fe7a8de 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/track-recording.mdx
@@ -31,13 +31,13 @@ Track recording currently supports audio tracks only. Video track recording is i
 
 Track recording has the following requirements and limits:
 
-| Limit | Description |
-| --- | --- |
-| Active meeting | The meeting must have an active live session. |
-| Media kind | Only `audio` layers are recorded. |
-| Participant selection | Pass up to 100 values in `user_ids`. |
-| Storage | Files are uploaded to RealtimeKit's managed R2 bucket with zero-egress fees. |
-| File retention | RealtimeKit bucket download URLs expire after seven days. |
+| Limit                 | Description                                                                  |
+| --------------------- | ---------------------------------------------------------------------------- |
+| Active meeting        | The meeting must have an active live session.                                |
+| Media kind            | Only `audio` layers are recorded.                                            |
+| Participant selection | Pass up to 100 values in `user_ids`.                                         |
+| Storage               | Files are uploaded to RealtimeKit's managed R2 bucket with zero-egress fees. |
+| File retention        | RealtimeKit bucket download URLs expire after seven days.                    |
 
 ## Start track recording
 
@@ -56,11 +56,11 @@ curl --request POST \
 }'
 ```
 
-RealtimeKit records current and future participant peers whose user_id matches the allowlist. Participants whose user_id is not listed are not recorded.
+RealtimeKit records current and future participants whose `user_id` matches the allowlist. Participants whose `user_id` is not listed are not recorded.
 
 ### Record all participants as separate tracks
 
-Omit `user_ids` to record separate audio tracks for all participants in the live meeting. RealtimeKit creates one WebM file for each recorded participant peer.
+Omit `user_ids` to record separate audio tracks for all participants in the live meeting. RealtimeKit creates one WebM file for each recorded participant.
 
 ```bash
 curl --request POST \
@@ -109,7 +109,7 @@ If you omit `layers`, RealtimeKit uses `default` as the file name prefix.
 
 ## Stop track recording
 
-Use the recording update endpoint to stop a track recording.
+Use the [recording update endpoint](/api/resources/realtime_kit/subresources/recordings/methods/pause_resume_stop_recording/) to stop a track recording.
 
 ```bash
 curl --request PUT \

From 4917098ab861cdf63a3777c6867b73cfce3f0b2e Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 07:56:20 +0000
Subject: [PATCH 7/8] Fixed PR #31077: title, links, heading.

Co-authored-by: korinne <korinne@users.noreply.github.com>
---
 .agents/references/procedures.md              |   20 +-
 .agents/skills/dependabot-review/SKILL.md     |   18 +-
 .agents/skills/docs-review/SKILL.md           |   26 +-
 .agents/skills/eli5/SKILL.md                  |   45 +-
 .../internal-dns/index.eli5.mdx               |    1 +
 .../eli5/references/EXAMPLES_REFERENCE.md     |  517 ++++----
 .../eli5/references/content-type-guide.md     |  105 +-
 .../skills/eli5/references/pattern-library.md |  202 +--
 .github/review-template.md                    |    3 +-
 .opencode/command/styleguide.md               |    1 +
 .windsurf/rules/general-rules.md              |    2 +-
 CONTRIBUTING.md                               |    3 +-
 MIGRATION.md                                  |    4 +-
 src/components/AutoconfigDiagram.astro        |  157 ++-
 src/components/ComponentUsage.astro           |    3 +-
 src/components/FeatureTable.astro             |   44 +-
 src/components/LayerCard.astro                |    8 +-
 src/components/LlmsTxtDirective.astro         |    6 +-
 src/components/PagesBuildPresetsTable.astro   |   15 +-
 src/components/ProductReleaseNotes.astro      |    7 +-
 src/components/R2LocalUploadsdiagram.astro    |  404 ++++--
 src/components/WranglerCommand.astro          |    2 +-
 src/components/WranglerConfig.astro           |    4 +-
 src/components/WranglerNamespace.astro        |    2 +-
 .../agent-setup/AgentComparison.astro         |   12 +-
 src/components/agent-setup/AgentHeader.astro  |    4 +-
 src/components/agent-setup/AgentPrimer.astro  |    6 +-
 .../agent-setup/BuildAgentsCallout.astro      |    4 +-
 .../agent-setup/CloudflareToolsBanner.astro   |   35 +-
 .../agent-setup/PlatformAccessSection.astro   |    7 +-
 src/components/ai-gateway/code-examples.astro |  329 +++--
 src/components/changelog/Pagination.astro     |    7 +-
 src/components/models/CopyableCode.astro      |   11 +-
 src/components/models/ModelDetailPage.astro   |  220 +++-
 src/components/models/SchemaDisplay.astro     |   16 +-
 src/components/models/code/DeepgramFlux.astro |   15 +-
 .../OpenAIResponsesTextGenerationCode.astro   |    4 +-
 src/components/overrides/Page.astro           |    6 +-
 ...ss-Supports-Customer-Metadata-Boundary.mdx |    4 +-
 .../access/2025-08-26-mcp-server-portals.mdx  |    1 -
 ...-17-clientless-access-for-private-apps.mdx |    4 +-
 .../2025-12-22-agents-sdk-ai-sdk-v6.mdx       |   40 +-
 .../2026-04-15-agentlee-writeops-genui.mdx    |   14 +-
 .../ai-search/2025-09-19-autorag-metrics.mdx  |    2 +-
 .../2025-09-25-ai-search-more-models.mdx      |   31 +-
 ...add-extra-headers-for-website-crawling.mdx |    7 +-
 ...2026-04-16-ai-search-namespace-binding.mdx |    4 +-
 .../2025-10-01-confidence-intervals.mdx       |    8 +-
 .../2026-02-18-cfworker-server-timing.mdx     |    8 +-
 .../2026-03-09-vulnerability-scanner.mdx      |    4 +-
 .../2026-05-19-event-subscriptions.mdx        |   10 +-
 .../2024-09-05-cache-rules-templates.mdx      |    1 -
 .../2024-11-07-shard-cache-by-cache-key.mdx   |   16 +-
 ...-11-07-cache-keys-for-cloudflare-trace.mdx |   26 +-
 ...1-25-audit-logs-for-cache-purge-events.mdx |   44 +-
 .../cache/2026-03-24-cache-response-rules.mdx |    2 +-
 .../changelog/casb/2025-10-28-casb-roles.mdx  |    4 +-
 .../2025-08-29-warp-AI-diag-analyzer.mdx      |    1 -
 ...nabled-search-for-zero-trust-dashboard.mdx |    4 +-
 ...for-supported-cloudflare-one-resources.mdx |   10 +-
 .../cloudflare-one/new-applications-71825.mdx |    2 +-
 ...-01-27-configure-cloudflare-source-ips.mdx |    2 +-
 ...025-10-01-new-container-instance-types.mdx |    2 +-
 .../containers/2025-11-21-new-cpu-pricing.mdx |    6 +-
 ...02-25-higher-container-resource-limits.mdx |    2 +-
 .../2026-03-24-docker-hub-images.mdx          |    2 +-
 .../2026-04-05-regional-placement.mdx         |    8 +-
 ...4-13-sandbox-outbound-workers-tls-auth.mdx |    2 +-
 .../2026-05-12-ssh-enabled-by-default.mdx     |    2 +-
 .../dex/2025-11-12-dex-logpush-jobs.mdx       |    4 +-
 .../dex/2026-02-19-dex-supports-cmb-eu.mdx    |    1 -
 ...04-28-dex-internet-outage-notification.mdx |    2 +-
 .../dex/2026-04-28-dex-speed-test.mdx         |    3 +-
 .../dex/2026-04-29-dex-tests-to-auth.mdx      |    3 +-
 .../2025-04-14-account-level-dlp-settings.mdx |    1 +
 .../dlp/2025-07-17-document-matching.mdx      |    5 +-
 .../dlp/2025-08-25-ai-prompt-protection.mdx   |   12 +-
 ...25-har-file-detection-and-sanitization.mdx |    2 +-
 ...-04-14-cloudflare-api-token-detections.mdx |   16 +-
 .../dlp/2026-04-28-pii-record-profile.mdx     |    2 +-
 .../dns/2026-03-31-internal-dns-open-beta.mdx |    1 +
 .../dns/2026-04-28-enforce-dns-only.mdx       |    1 +
 ...2025-08-21-durable-objects-get-by-name.mdx |    8 +-
 ...2025-10-16-durable-objects-data-studio.mdx |    2 +-
 ...durable-objects-sqlite-storage-billing.mdx |    3 +-
 .../2026-03-15-durable-object-id-name.mdx     |   18 +-
 .../2025-07-21-subaddressing.mdx              |    2 +-
 .../2024-12-19-escalate-user-submissions.mdx  |    2 +-
 .../2025-10-16-on-demand-security-report.mdx  |    1 -
 ...adjustment-to-final-disposition-column.mdx |    3 +-
 ...25-12-03-submission-terminology-update.mdx |   11 +-
 ...anced-visibility-post-delivery-actions.mdx |    9 +-
 ...ed-accessibility-search-for-monitoring.mdx |   26 +-
 ...6-03-15-infinite-paging-investigations.mdx |   12 +-
 ...2026-04-06-dane-support-mx-deployments.mdx |   12 +-
 .../2026-04-07-triage-status-tracking.mdx     |    2 +
 ...5-06-cloudy-summaries-in-phishnet_o365.mdx |    1 +
 .../2025-06-23-user-groups-ga.mdx             |    4 +-
 .../2025-09-03-rate-limiting-improvement.mdx  |   21 +-
 ...two-factor-authentication-backup-codes.mdx |    3 +-
 .../2025-09-25-sign-in-with-github.mdx        |    3 +-
 .../fundamentals/2025-10-01-md-returned.mdx   |    2 +-
 .../2025-10-14-sso-self-service-ux.mdx        |    1 -
 .../fundamentals/2025-10-30-email-2FA.mdx     |    6 +-
 ...5-10-30-member-management-improvements.mdx |   14 +-
 .../2026-01-23-New-2FA-Experience.mdx         |    9 +-
 .../2026-02-12-markdown-for-agents.mdx        |    3 +-
 ...02-16-markdown-for-agents-improvements.mdx |    2 +-
 ...json-rfc9457-responses-for-1xxx-errors.mdx |    1 +
 ...-12-retry-after-header-for-1xxx-errors.mdx |   19 +-
 .../2026-03-17-scim-authentik-support.mdx     |    2 +-
 .../2026-03-18-scim-audit-logging.mdx         |    4 +-
 .../2026-04-06-organizations-public-beta.mdx  |    2 +-
 .../2026-04-10-secret-scanning-support.mdx    |    2 +-
 .../2026-04-14-oauth-consent-and-revoke.mdx   |   22 +-
 ...27-structured-responses-for-5xx-errors.mdx |    1 +
 .../2026-05-04-keyboard-shortcuts.mdx         |   54 +-
 ...025-07-24-HTTP-Inspection-on-all-ports.mdx |    4 +-
 ...-07-28-Spam-domain-category-introduced.mdx |   12 +-
 ...08-15-gemini-application-replaces-bard.mdx |    3 +-
 .../2025-10-10-new-domain-categories.mdx      |   10 +-
 ...-11-06-Applications-recategorised-plan.mdx |    6 +-
 ...02-27-new-protocol-detection-protocols.mdx |   14 +-
 .../Gateway-application-categories-added.mdx  |    4 +-
 ...4-hyperdrive-remote-database-local-dev.mdx |   14 +-
 src/content/changelog/images/heic-support.mdx |    1 +
 ...2025-08-22-kv-performance-improvements.mdx |    2 -
 .../2025-06-04-account-load-balancing-ui.mdx  |    3 +-
 .../2025-07-09-usage-tracking.mdx             |    2 +-
 .../2025-08-15-extended-retention.mdx         |    2 +-
 .../2025-09-03-log-headers-and-cookies.mdx    |    2 -
 .../2025-09-11-contextual-pivots.mdx          |    4 +-
 .../2025-09-11-new-results-table-view.mdx     |    4 +-
 .../2025-11-04-query-cancellation.mdx         |    2 +-
 .../2025-11-11-resize-sql-window.mdx          |    2 +-
 .../2025-11-13-fixed-custom-date.mdx          |    2 +-
 .../log-explorer/2025-11-13-new-datasets.mdx  |    5 +-
 .../2026-03-11-ingest-field-selection.mdx     |   20 +-
 .../logs/2024-10-08-new-gateway-fields.mdx    |    2 +-
 .../logs/2026-03-09-log-fields-updated.mdx    |    1 -
 ...26-04-20-pipelines-logpush-destination.mdx |    2 +-
 ...2026-04-21-logpush-subrequests-merging.mdx |    4 +-
 ...-03-24-interconnects-navigation-update.mdx |    2 +-
 .../pages/2025-05-30-pages-build-image-v3.mdx |    2 +-
 .../queues/2025-03-25-pause-purge-queues.mdx  |    8 +-
 .../2025-04-17-pull-consumer-limits.mdx       |    3 +
 .../2025-05-09-publish-to-queues-via-http.mdx |    2 +-
 .../queues/2025-08-19-event-subscriptions.mdx |   26 +-
 ...2025-09-25-announcing-r2-sql-open-beta.mdx |    2 +-
 ...ql-functions-expressions-complex-types.mdx |    1 -
 ...0-r2-sql-json-functions-explain-format.mdx |    2 +
 .../radar/2025-08-04-radar-ct-insights.mdx    |    2 +-
 .../radar/2025-09-29-radar-regional-data.mdx  |    2 +-
 .../radar/2026-02-25-radar-aspa-insights.mdx  |    2 +-
 .../2026-04-01-radar-routing-section.mdx      |    2 +-
 ...2026-05-28-realtimekit-track-recording.mdx |    8 +-
 .../2026-1-15-crowdstrike-score.mdx           |    1 +
 .../2025-10-30-tcp-rtt-and-tcp-fields.mdx     |    8 +-
 .../rules/2026-01-12-dma-metro-code-field.mdx |    4 +-
 .../rules/2026-01-20-array-map-functions.mdx  |   12 +-
 .../2026-01-27-body-buffering-settings.mdx    |   26 +-
 .../rules/2026-03-18-worker-timing-field.mdx  |    4 +-
 .../rules/2026-03-25-rfc9440-mtls-fields.mdx  |    2 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   12 +-
 ...20-cloudflare-typescript-v6.0.0-beta.1.mdx |   70 +-
 ...-02-13-cloudflare-python-v5.0.0-beta.1.mdx |   13 +-
 .../2025-07-18-brand-protection-api.mdx       |   14 +-
 .../2025-10-27-RFI-Tokens-in-Dash.mdx         |    2 +-
 ...protection-logo-dashboard-report-abuse.mdx |    4 +-
 ...Threat-Events-now-show-events-insights.mdx |    6 +-
 ...-01-14-Download-URL-Scanner-Report-PDF.mdx |    8 +-
 .../2026-02-19-threat-events-graphs.mdx       |    1 +
 ...026-02-23-Saved-views-in-threat-events.mdx |    5 +-
 .../2026-04-08-threat-events-notification.mdx |   20 +-
 .../2026-05-07-CSV-export-for-RFIs.mdx        |    1 +
 ...-12-URL-scanner-report-agent-readiness.mdx |   17 +-
 ...archive-and-audit-security-action-items.md |    5 +-
 .../2025-08-25-secrets-store-ai-gateway.mdx   |   20 +-
 ...07-22-media-transformations-audio-mode.mdx |    2 +-
 .../2026-04-06-redesigned-support-portal.mdx  |    1 +
 .../2026-04-28-direct-support-navigation.mdx  |    4 +-
 .../2025-02-03-terraform-v5-provider.mdx      |    6 +-
 .../2025-05-19-terraform-v5.5.0-provider.mdx  |   13 +-
 .../2025-06-17-terraform-v5.6.0-provider.mdx  |    3 +-
 .../2025-07-11-terraform-v5.7.0-provider.mdx  |    3 +-
 .../2025-08-01-terraform-v5.8.2-provider.mdx  |    6 +-
 .../2025-08-15-terraform-v5.8.4-provider.mdx  |    6 +-
 .../2025-08-29-terrform-v5.9-provider.mdx     |    3 +-
 .../2025-11-20-terraform-v5.13.0-provider.mdx |   63 +-
 .../2025-12-05-terraform-v5.14.0-provider.mdx |   22 +-
 .../2025-12-19-terraform-v5.15.0-provider.mdx |   36 +-
 .../2026-01-20-terraform-v5.16.0-provider.mdx |   55 +-
 .../2026-02-12-terraform-v5.17.0-provider.mdx |   91 +-
 .../2026-04-24-terraform-v5.19.0-provider.mdx |    1 +
 .../2026-04-24-tf-migrate-tool-released.mdx   |    6 +-
 .../tunnel/2025-07-15-udp-improvements.mdx    |    3 +-
 ...el-networks-list-endpoints-new-default.mdx |   28 +-
 .../2025-09-18-tunnel-hostname-routing.mdx    |    3 +-
 ...2026-01-15-warp-connector-ping-support.mdx |    2 +-
 .../changelog/waf/2025-07-14-waf-release.mdx  |    1 -
 .../changelog/waf/2025-07-21-emergency.mdx    |   30 +-
 .../changelog/waf/2025-07-28-waf-release.mdx  |   11 +-
 .../changelog/waf/2025-08-04-waf-release.mdx  |  207 +--
 .../waf/2025-08-07-emergency-waf-release.mdx  |   75 +-
 .../changelog/waf/2025-08-11-waf-release.mdx  |  460 ++++---
 .../changelog/waf/2025-08-18-waf-release.mdx  |  275 ++--
 .../changelog/waf/2025-08-25-waf-release.mdx  |   98 +-
 .../waf/2025-08-29-emergency-waf-release.mdx  |   72 +-
 .../changelog/waf/2025-09-01-waf-release.mdx  |   78 +-
 .../waf/2025-09-04-emergency-waf-release.mdx  |   95 +-
 .../changelog/waf/2025-09-08-waf-release.mdx  |  250 ++--
 .../changelog/waf/2025-09-15-waf-release.mdx  |  100 +-
 .../changelog/waf/2025-09-22-waf-release.mdx  |  221 ++--
 .../waf/2025-09-24-emergency-waf-release.mdx  |   52 +-
 .../changelog/waf/2025-09-26-waf-release.mdx  |  268 ++--
 .../waf/2025-09-28-emergency-waf-release.mdx  |   80 +-
 .../changelog/waf/2025-09-29-waf-release.mdx  |  135 +-
 .../changelog/waf/2025-10-03-waf-release.mdx  |  488 +++----
 .../changelog/waf/2025-10-06-waf-release.mdx  |  220 ++--
 .../waf/2025-10-07-emergency-waf-release.mdx  |   55 +-
 .../waf/2025-10-17-emergency-waf-release.mdx  |   82 +-
 .../changelog/waf/2025-10-20-waf-release.mdx  |   16 +-
 .../waf/2025-10-23-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-24-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-30-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-11-05-emergency-waf-release.mdx  |   50 +-
 .../changelog/waf/2025-11-10-waf-release.mdx  |    4 +-
 .../changelog/waf/2025-11-17-waf-release.mdx  |    2 +-
 .../waf/2025-11-21-emergency-waf-release.mdx  |    2 +-
 .../changelog/waf/2025-11-24-waf-release.mdx  |   16 +-
 .../changelog/waf/2025-12-01-waf-release.mdx  |    9 +-
 .../waf/2025-12-02-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-03-emergency-waf-release.mdx  |    3 +-
 .../waf/2025-12-10-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-11-emergency-waf-release.mdx  |   14 +-
 .../changelog/waf/2025-12-18-waf-release.mdx  |  225 ++--
 .../changelog/waf/2026-01-12-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-15-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-20-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-26-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-02-02-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-03-02-waf-release.mdx  |    7 +-
 .../waf/2026-03-12-emergency-waf-release.mdx  |    6 +-
 .../changelog/waf/2026-03-23-waf-release.mdx  |  104 +-
 .../changelog/waf/2026-03-30-waf-release.mdx  |  116 +-
 .../changelog/waf/2026-04-15-waf-release.mdx  |  144 ++-
 .../changelog/waf/2026-04-21-waf-release.mdx  |  339 +++--
 .../changelog/waf/2026-04-27-waf-release.mdx  |  343 ++---
 .../waf/2026-05-07-emergency-waf-release.mdx  |   12 +-
 .../changelog/waf/2026-05-11-waf-release.mdx  |    9 +-
 .../waf/2026-05-15-emergency-waf-release.mdx  |   16 +-
 .../changelog/waf/2026-05-20-waf-release.mdx  |   12 +-
 .../2026-04-30-rum-navigation-types.mdx       |    4 +-
 .../2025-08-05-openai-open-models.mdx         |    5 +-
 .../workers-ai/2025-08-27-partner-models.mdx  |    3 +-
 .../workers-ai/2025-09-05-embeddinggemma.mdx  |    3 +-
 .../workers-vpc/2025-09-25-workers-vpc.mdx    |    4 +-
 ...-07-new-ways-to-get-started-on-workers.mdx |   12 +-
 .../workers/2025-03-25-higher-cpu-limits.mdx  |    2 +-
 ...2025-04-08-deploy-to-cloudflare-button.mdx |   18 +-
 .../workers/2025-04-09-qb-workers-logs-ga.mdx |    4 +-
 ...2025-04-22-python-worker-cron-triggers.mdx |    2 +-
 ...025-05-14-python-worker-durable-object.mdx |    2 +-
 .../workers/2025-06-05-open-next-size.mdx     |    2 +-
 .../2025-07-23-workers-preview-urls.mdx       |   12 +-
 .../2025-08-04-builds-increased-disk-size.mdx |    8 +-
 ...08-08-add-waituntil-cloudflare-workers.mdx |    2 +-
 ...port-long-branch-names-preview-aliases.mdx |    4 +-
 .../workers/2025-08-11-messagechannel.mdx     |   16 +-
 .../2025-08-14-new-python-handlers.mdx        |    2 +-
 ...workers-terraform-and-sdk-improvements.mdx |   39 +-
 .../2025-08-15-static-assets-redirect-url.mdx |    6 +-
 ...5-08-19-improved-wrangler-error-screen.mdx |    4 +-
 .../workers/2025-09-03-new-workers-api.mdx    |   86 +-
 .../2025-09-07-builds-increased-cpu-paid.mdx  |   17 +-
 ...2025-09-09-interactive-wrangler-assets.mdx |    5 +-
 ...025-09-10-built-with-cloudflare-button.mdx |    2 +-
 ...09-11-increased-version-rollback-limit.mdx |    9 +-
 .../2025-09-17-update-preview-url-setting.mdx |    6 +-
 .../2025-09-19-ratelimit-workers-ga.mdx       |    4 +-
 ...dev-multi-config-cross-command-support.mdx |   19 +-
 ...9-26-analytics-engine-sql-enhancements.mdx |   21 +-
 .../workers/2025-09-26-ctx-exports.md         |   16 +-
 .../workers/2025-10-09-assets-terraform.mdx   |   10 +-
 .../2025-10-09-workflows-terraform.mdx        |    8 +-
 ...025-10-23-preview-url-default-behavior.mdx |    7 +-
 ...-10-24-automatic-resource-provisioning.mdx |    2 +-
 .../workers/2025-10-30-builds-preview.mdx     |    8 +-
 .../2025-11-09-cloudflare-env-variable.mdx    |    1 +
 ...lytics-engine-further-sql-enhancements.mdx |   12 +-
 ...25-12-01-build-image-policies-dev-plat.mdx |    2 +-
 ...5-12-08-python-cold-start-improvements.mdx |   10 +-
 .../workers/2025-12-08-python-pywrangler.mdx  |    1 -
 .../2025-12-08-vite-optional-config.mdx       |    2 +-
 .../2025-12-08-vite-programmatic-config.mdx   |    2 +-
 .../2025-12-16-vitest-ctx-exports-support.mdx |   10 +-
 ...2025-12-19-tanstack-start-prerendering.mdx |   20 +-
 .../2026-02-15-workers-best-practices.mdx     |    1 +
 .../2026-03-27-rfc9440-mtls-fields.mdx        |   45 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   34 +-
 ...026-05-06-react-nextjs-vulnerabilities.mdx |    2 +-
 .../2025-01-15-workflows-more-steps.mdx       |    6 +-
 .../workflows/2025-10-28-raising-limits.mdx   |    6 +-
 .../2026-03-23-local-dev-instance-methods.mdx |    2 +-
 .../2026-05-01-dynamic-workflows.mdx          |    6 +-
 .../compatibility-flags/allow-custom-ports.md |    1 +
 .../enable-nodejs-http-modules.md             |    8 +-
 .../enable-nodejs-http-server-modules.md      |    8 +-
 .../fetcher-no-get-put-delete.md              |    1 -
 .../compatibility-flags/js-weak-refs.md       |    3 +-
 .../new-url-parser-implementation.md          |    8 +-
 .../compatibility-flags/nodejs-compat.md      |   12 +-
 .../queue-consumer-no-wait-waituntil.md       |   29 +-
 .../queues-json-messages.md                   |    2 +-
 .../compatibility-flags/request-signal.md     |    2 +-
 .../streams-byob-reader-detaches-buffer.md    |   12 +-
 .../compatibility-flags/strict-crypto.md      |    1 +
 .../throw-on-unrecognized-import-assertion.md |    1 -
 .../compatibility-flags/to-string-tag.md      |    2 +-
 .../urlsearchparams-deletehasvalue.md         |    6 +-
 .../web-socket-auto-reply-to-close.md         |   38 +-
 .../web-socket-compression.md                 |    2 +-
 .../websocket-standard-binary-type.md         |    4 +-
 ...ws-preserve-non-retryable-error-message.md |   14 +-
 .../mpp/charge-for-http-content.mdx           |   10 +-
 .../agents/agentic-payments/x402/index.mdx    |    4 +-
 .../ai-crawl-control-with-bots.mdx            |    2 +-
 .../ai-crawl-control-with-waf.mdx             |   10 +-
 .../features/analyze-ai-traffic.mdx           |   22 +-
 .../features/manage-ai-crawlers.mdx           |   24 +-
 .../set-up-cloudflare-account.mdx             |    2 +-
 .../features/track-robots-txt.mdx             |   10 +-
 .../reference/redirects-for-ai-training.mdx   |   16 +-
 .../configuration/authentication.mdx          |    2 +-
 .../configuration/custom-providers.mdx        |   69 +-
 .../evaluations/add-human-feedback.mdx        |    1 +
 .../docs/ai-gateway/features/dlp/index.mdx    |   10 +-
 .../features/dynamic-routing/usage.mdx        |    3 +-
 .../integrations/aig-workers-ai-binding.mdx   |    2 +-
 src/content/docs/ai-gateway/mcp-server.mdx    |    2 +-
 .../observability/logging/index.mdx           |    6 +-
 .../docs/ai-gateway/reference/audit-logs.mdx  |   71 +-
 .../docs/ai-gateway/reference/limits.mdx      |   13 +-
 .../ai-gateway/tutorials/pruna-p-video.mdx    |   14 +-
 .../docs/ai-gateway/usage/chat-completion.mdx |    6 +-
 .../ai-gateway/usage/providers/anthropic.mdx  |   17 +-
 .../usage/providers/azureopenai.mdx           |   12 +-
 .../ai-gateway/usage/providers/baseten.mdx    |   40 +-
 .../ai-gateway/usage/providers/bedrock.mdx    |   10 +-
 .../docs/ai-gateway/usage/providers/fal.mdx   |   26 +-
 .../usage/providers/google-ai-studio.mdx      |   15 +-
 .../ai-gateway/usage/providers/ideogram.mdx   |   20 +-
 .../docs/ai-gateway/usage/rest-api.mdx        |   70 +-
 .../usage/websockets-api/non-realtime-api.mdx |    2 +-
 .../usage/websockets-api/realtime-api.mdx     |    2 +-
 .../docs/ai-search/api/instances/rest-api.mdx |    4 +-
 .../docs/ai-search/api/items/rest-api.mdx     |    4 +-
 .../ai-search/configuration/models/index.mdx  |    2 -
 src/content/docs/ai-search/how-to/nlweb.mdx   |   34 +-
 .../docs/ai-search/wrangler-commands.mdx      |    2 +-
 .../docs/ai/related-products/ai-gateway.mdx   |    2 +-
 .../account-analytics.mdx                     |   28 +-
 .../analytics-with-workers.mdx                |   10 +-
 .../account-and-zone-analytics/index.mdx      |    2 +-
 .../analytics/analytics-engine/grafana.mdx    |   12 +-
 .../docs/analytics/analytics-engine/index.mdx |   14 +-
 .../analytics/analytics-engine/limits.mdx     |    8 +-
 .../analytics/analytics-engine/pricing.mdx    |    2 +-
 .../analytics-engine/recipes/index.mdx        |    2 +-
 .../analytics/analytics-engine/sampling.mdx   |   62 +-
 .../analytics/analytics-engine/sql-api.mdx    |   10 +-
 .../sql-reference/aggregate-functions.mdx     |    2 +-
 .../sql-reference/bit-functions.mdx           |    2 +-
 .../sql-reference/date-time-functions.mdx     |    2 +-
 .../sql-reference/encoding-functions.mdx      |    2 +-
 .../analytics-engine/sql-reference/index.mdx  |    2 +-
 .../sql-reference/mathematical-functions.mdx  |    2 +-
 .../sql-reference/string-functions.mdx        |    2 +-
 .../type-conversion-functions.mdx             |    2 +-
 .../analytics-engine/worker-querying.mdx      |    1 -
 .../analytics-integrations/datadog.mdx        |    1 -
 .../analytics-integrations/index.mdx          |    2 +-
 .../analytics-integrations/prometheus.mdx     |   75 +-
 .../docs/analytics/custom-dashboards.mdx      |   38 +-
 .../docs/analytics/faq/about-analytics.mdx    |   16 +-
 src/content/docs/analytics/faq/index.mdx      |    2 +-
 src/content/docs/analytics/faq/other-faqs.mdx |   12 +-
 src/content/docs/analytics/faq/wae-faqs.mdx   |    9 +-
 .../docs/analytics/graphql-api/errors.mdx     |   64 +-
 .../features/confidence-intervals.mdx         |  102 +-
 .../graphql-api/features/discovery/index.mdx  |    1 -
 .../analytics/graphql-api/features/index.mdx  |    2 +-
 .../authentication/graphql-client-headers.mdx |    6 +-
 .../getting-started/authentication/index.mdx  |   52 +-
 .../getting-started/compose-graphql-query.mdx |   15 -
 .../getting-started/execute-graphql-query.mdx |    4 +-
 .../explore-graphql-schema.mdx                |   17 +-
 .../graphql-api/getting-started/index.mdx     |   20 +-
 .../docs/analytics/graphql-api/limits.mdx     |   18 +-
 .../docs/analytics/graphql-api/mcp-server.mdx |    2 +-
 .../graphql-api/migration-guides/index.mdx    |    4 +-
 .../network-analytics-v2/schema-map.mdx       |    1 -
 .../docs/analytics/graphql-api/sampling.mdx   |    4 -
 .../tutorials/end-customer-analytics.mdx      |  218 ++--
 .../analytics/graphql-api/tutorials/index.mdx |    2 +-
 .../querying-access-login-events.mdx          |   72 +-
 .../tutorials/querying-email-routing.mdx      |  352 ++---
 ...c-transit-endpoint-healthcheck-results.mdx |    5 +-
 ...gic-transit-tunnel-bandwidth-analytics.mdx |    8 +-
 ...gic-transit-tunnel-healthcheck-results.mdx |    5 +-
 src/content/docs/analytics/index.mdx          |   36 +-
 .../network-analytics/configure/index.mdx     |    2 +-
 .../configure/share-export.mdx                |    2 +-
 .../configure/time-range.mdx                  |    2 +-
 .../analytics/network-analytics/index.mdx     |   12 +-
 .../network-analytics/reference/index.mdx     |    2 +-
 .../network-analytics/understand/index.mdx    |    2 +-
 src/content/docs/analytics/sampling.mdx       |   23 +-
 .../docs/analytics/types-of-analytics.mdx     |   27 +-
 src/content/docs/api-shield/api-gateway.mdx   |    1 -
 src/content/docs/api-shield/glossary.mdx      |    3 +-
 src/content/docs/api-shield/index.mdx         |   30 +-
 .../management-and-monitoring/index.mdx       |    5 +-
 .../session-identifiers.mdx                   |    4 +-
 src/content/docs/api-shield/plans.mdx         |   15 +-
 .../reference/classic-schema-validation.mdx   |   14 +-
 .../docs/api-shield/reference/index.mdx       |    5 +-
 .../docs/api-shield/reference/terraform.mdx   |   11 +-
 .../security/graphql-protection/index.mdx     |    1 -
 .../docs/api-shield/security/index.mdx        |   45 +-
 .../security/jwt-validation/jwt-worker.mdx    |    2 +-
 .../jwt-validation/transform-rules.mdx        |    4 +-
 .../docs/api-shield/security/mtls/byo-ca.mdx  |    1 -
 .../docs/api-shield/security/mtls/index.mdx   |    1 -
 .../security/sequence-analytics.mdx           |    3 +-
 .../security/sequence-mitigation/api.mdx      |   23 +-
 .../sequence-mitigation/custom-rules.mdx      |   21 +-
 .../security/sequence-mitigation/index.mdx    |    8 +-
 .../security/volumetric-abuse-detection.mdx   |   11 +-
 .../docs/argo-smart-routing/analytics.mdx     |    9 +-
 .../argo-smart-routing/argo-for-packets.mdx   |    1 -
 src/content/docs/artifacts/api/errors.mdx     |   28 +-
 .../docs/artifacts/api/git-protocol.mdx       |    6 +-
 .../docs/artifacts/concepts/repositories.mdx  |   10 +-
 .../docs/artifacts/examples/git-client.mdx    |    5 +-
 .../docs/artifacts/guides/authentication.mdx  |   18 +-
 .../artifacts/guides/event-subscriptions.mdx  |    1 +
 .../docs/artifacts/platform/limits.mdx        |    4 +-
 .../docs/artifacts/platform/pricing.mdx       |    8 +-
 .../about/index.mdx                           |    1 -
 .../about/plugin-compatibility.mdx            |   50 +-
 .../about/test-current-speed.mdx              |    1 -
 .../get-started/change-nameservers.mdx        |    2 -
 .../get-started/index.mdx                     |    3 +-
 .../reference/cache-device-type.mdx           |    8 +-
 .../reference/index.mdx                       |    3 +-
 .../reference/page-rule-integration.mdx       |   17 +-
 .../reference/query-parameters.mdx            |   80 +-
 .../reference/subdomain-subdirectories.mdx    |    6 +-
 .../troubleshooting/index.mdx                 |   15 +-
 .../get-started/create-billing-profile.mdx    |    4 +-
 .../get-started/update-billing-info.mdx       |   22 +-
 .../docs/billing/manage/billable-usage.mdx    |   15 +-
 .../docs/billing/manage/budget-alerts.mdx     |   22 +-
 .../billing/manage/cancel-subscription.mdx    |    6 +-
 src/content/docs/billing/manage/invoices.mdx  |   26 +-
 .../docs/billing/manage/optimize-costs.mdx    |   48 +-
 .../manage/pay-invoices-overdue-balances.mdx  |    7 +-
 .../instant-bank-payments-link.mdx            |    6 +-
 .../docs/billing/threshold-billing.mdx        |    8 +-
 .../billing/troubleshoot/error-reference.mdx  |   24 +-
 .../resolve-cannot-remove-payment-method.mdx  |   37 +-
 ...ve-you-cannot-modify-this-subscription.mdx |   12 +-
 .../troubleshoot/troubleshoot-invoices.mdx    |    2 +-
 .../understand/billing-permissions.mdx        |   26 +-
 .../billing/understand/billing-policy.mdx     |   18 +-
 .../billing/understand/how-charges-accrue.mdx |   72 +-
 .../billing/understand/preview-services.mdx   |    2 +-
 .../understand/usage-based-billing.mdx        |   36 +-
 .../docs/bots/account-abuse-protection.mdx    |   75 +-
 .../block-ai-bots.mdx                         |    4 +-
 .../custom-rules.mdx                          |   22 +-
 .../detection-ids/additional-detections.mdx   |    7 +-
 .../bots/additional-configurations/index.mdx  |    5 +-
 .../ja3-ja4-fingerprint/index.mdx             |   81 +-
 .../signals-intelligence.mdx                  |    2 +-
 .../javascript-detections.mdx                 |    2 +-
 src/content/docs/bots/concepts/bot-tags.mdx   |    3 +-
 src/content/docs/bots/concepts/bot/index.mdx  |    2 +-
 .../bots/concepts/bot/signed-agents/index.mdx |    3 +-
 .../concepts/bot/signed-agents/policy.mdx     |    7 +-
 .../concepts/bot/verified-bots/policy.mdx     |    7 +-
 src/content/docs/bots/concepts/index.mdx      |    3 +-
 src/content/docs/bots/get-started/index.mdx   |    3 +-
 src/content/docs/bots/glossary.mdx            |    3 +-
 .../docs/bots/plans/bm-subscription.mdx       |   22 +-
 src/content/docs/bots/reference/alerts.mdx    |    9 +-
 .../reference/bot-management-variables.mdx    |   12 +-
 .../bots/reference/bot-verification/index.mdx |    5 +-
 .../bot-verification/ip-validation.mdx        |    9 +-
 src/content/docs/bots/reference/index.mdx     |    3 +-
 .../reference/machine-learning-models.mdx     |    5 +-
 .../docs/bots/reference/sample-terms.mdx      |    6 +-
 .../troubleshooting/bot-management-skips.mdx  |    3 +-
 .../bots/troubleshooting/false-positives.mdx  |    3 +-
 .../docs/bots/troubleshooting/index.mdx       |    4 +-
 .../docs/bots/workers-templates/index.mdx     |    3 +-
 .../docs/browser-run/features/index.mdx       |    2 +-
 .../docs/browser-run/how-to/deploy-worker.mdx |    2 +-
 src/content/docs/browser-run/mcp-server.mdx   |    2 +-
 .../quick-actions/api-reference.mdx           |    2 +-
 .../reference/browser-close-reasons.mdx       |   54 +-
 src/content/docs/byoip/address-maps/setup.mdx |   26 +-
 src/content/docs/byoip/changelog.mdx          |    2 +-
 src/content/docs/byoip/concepts/index.mdx     |    2 +-
 .../byoip/concepts/prefix-delegations.mdx     |    1 -
 src/content/docs/byoip/glossary.mdx           |    2 +-
 .../docs/byoip/route-leak-detection.mdx       |    3 +-
 .../docs/byoip/service-bindings/index.mdx     |    3 +-
 .../docs/byoip/troubleshooting/index.mdx      |    9 +-
 .../advanced-configuration/cache-reserve.mdx  |    9 +-
 .../advanced-configuration/crawler-hints.mdx  |    9 +-
 .../advanced-configuration/early-hints.mdx    |   21 +-
 .../cache/advanced-configuration/index.mdx    |    3 +-
 .../query-string-sort.mdx                     |   32 +-
 .../serve-tailored-content.mdx                |  158 +--
 .../vary-for-images.mdx                       |   74 +-
 .../cache-security/avoid-web-poisoning.mdx    |   18 +-
 .../cache-security/cache-deception-armor.mdx  |    6 +-
 .../docs/cache/cache-security/cors.mdx        |   11 +-
 .../docs/cache/cache-security/index.mdx       |    3 +-
 .../docs/cache/concepts/cache-behavior.mdx    |   10 +-
 .../docs/cache/concepts/cache-responses.mdx   |    9 +-
 .../docs/cache/concepts/cdn-cache-control.mdx |  178 +--
 .../docs/cache/concepts/customize-cache.mdx   |   13 +-
 .../cache/concepts/default-cache-behavior.mdx |   44 +-
 src/content/docs/cache/concepts/index.mdx     |    3 +-
 .../cache/concepts/retention-vs-freshness.mdx |    5 +-
 .../docs/cache/concepts/revalidation.mdx      |    1 -
 src/content/docs/cache/get-started.mdx        |   58 +-
 src/content/docs/cache/glossary.mdx           |    3 +-
 .../docs/cache/how-to/always-online.mdx       |    5 +-
 src/content/docs/cache/how-to/cache-keys.mdx  |   72 +-
 .../cache-response-rules/create-dashboard.mdx |    4 +-
 .../how-to/cache-rules/examples/index.mdx     |    4 +-
 .../docs/cache/how-to/cache-rules/order.mdx   |    3 +-
 .../cache-rules/page-rules-migration.mdx      |    4 +-
 .../how-to/configure-cache-status-code.mdx    |   14 +-
 .../how-to/edge-browser-cache-ttl/index.mdx   |   14 +-
 .../set-browser-ttl.mdx                       |    7 +-
 src/content/docs/cache/how-to/index.mdx       |    3 +-
 .../how-to/purge-cache/purge-by-hostname.mdx  |    9 +-
 .../purge-cache/purge-by-single-file.mdx      |    2 +-
 .../how-to/purge-cache/purge-by-tags.mdx      |   26 +-
 .../how-to/purge-cache/purge-cache-key.mdx    |   72 +-
 .../how-to/purge-cache/purge-everything.mdx   |    3 +-
 .../purge-cache/purge-varied-images.mdx       |    1 -
 .../purge-cache/purge-zone-versions.mdx       |   81 +-
 .../how-to/purge-cache/purge_by_prefix.mdx    |   39 +-
 .../docs/cache/how-to/set-caching-levels.mdx  |    9 +-
 .../interaction-cloudflare-products/index.mdx |    5 +-
 .../interaction-cloudflare-products/r2.mdx    |    1 -
 .../waf-snippets.mdx                          |    2 +-
 .../workers-cache-rules.mdx                   |    9 +-
 .../workers.mdx                               |    3 +-
 .../performance-review/cache-analytics.mdx    |    5 +-
 .../performance-review/cache-performance.mdx  |    5 +-
 .../docs/cache/performance-review/index.mdx   |    3 +-
 src/content/docs/cache/plans.mdx              |    5 +-
 .../reference/cdn-reference-architecture.mdx  |    1 -
 .../docs/cache/reference/development-mode.mdx |    5 +-
 src/content/docs/cache/reference/index.mdx    |    3 +-
 .../cache/troubleshooting/always-online.mdx   |    3 -
 .../docs/cache/troubleshooting/index.mdx      |    3 +-
 .../concepts/global-acceleration.mdx          |   14 +-
 .../reference/available-products.mdx          |    2 +-
 .../client-ip-geolocation/about/index.mdx     |    4 +-
 .../docs/client-ip-geolocation/faq/index.mdx  |    2 -
 .../client-ip-geolocation/get-started.mdx     |   16 +-
 .../docs/client-ip-geolocation/index.mdx      |   14 +-
 .../additional-configuration.mdx              |    2 +-
 .../challenge-pages/detect-response.mdx       |    2 +-
 .../challenge-types/challenge-pages/index.mdx |    2 +-
 .../challenge-pages/resolve-challenge.mdx     |    2 +-
 .../challenge-types/index.mdx                 |    6 +-
 .../challenge-types/turnstile.mdx             |   12 +-
 .../cloudflare-challenges/concepts/index.mdx  |    4 +-
 .../docs/cloudflare-challenges/index.mdx      |    3 +-
 .../cloudflare-challenges/reference/index.mdx |    6 +-
 .../reference/supported-browsers.mdx          |   38 +-
 .../reference/supported-languages.mdx         |   44 +-
 .../challenge-solve-issues.mdx                |    5 +-
 .../hostname-validation/backoff-schedule.mdx  |    5 +-
 .../hostname-validation/error-codes.mdx       |    1 -
 .../hostname-validation/pre-validation.mdx    |   59 +-
 .../migrating-custom-hostnames.mdx            |    2 +-
 .../hostname-analytics.mdx                    |   16 +-
 .../performance/argo-for-saas.mdx             |    1 -
 .../performance/cache-for-saas.mdx            |    1 -
 .../performance/early-hints-for-saas.mdx      |   66 +-
 .../cloudflare-for-saas/performance/index.mdx |    9 +-
 .../reference/certificate-authorities.mdx     |    1 -
 .../reference/certificate-statuses.mdx        |    1 -
 .../reference/dcv-validation-backoff.mdx      |    1 -
 .../reference/hostname-priority.mdx           |    1 -
 .../reference/status-codes/custom-csrs.mdx    |   59 +-
 .../status-codes/custom-hostnames.mdx         |  123 +-
 .../reference/token-validity-periods.mdx      |    8 +-
 .../reference/versioning.mdx                  |   24 +-
 .../saas-customers/index.mdx                  |    3 +-
 .../saas-customers/product-compatibility.mdx  |    4 +-
 .../provider-guides/webflow.mdx               |    6 +-
 .../certificate-statuses.mdx                  |    1 -
 .../uploading-certificates.mdx                |    5 +-
 .../validate-certificates/delegated-dcv.mdx   |    5 +-
 .../validate-certificates/troubleshooting.mdx |   19 +-
 .../webhook-definitions.mdx                   |  755 +++++------
 .../cloudflare-for-saas/security/index.mdx    |   11 +-
 .../security/waf-for-saas/index.mdx           |   48 +-
 .../regional-services-for-saas.mdx            |    1 -
 .../advanced-settings/worker-as-origin.mdx    |    6 +-
 .../configuration/bindings.mdx                |    5 +
 .../configuration/observability.mdx           |    2 +-
 .../reference/limits.mdx                      |    2 +-
 .../reference/platform-examples.mdx           |    2 +-
 .../reference/worker-isolation.mdx            |   21 +-
 .../best-practices/minimal-ruleset.mdx        |   23 +-
 .../cloudflare-network-firewall/index.mdx     |    4 +-
 .../packet-captures/collect-pcaps.mdx         |    2 +-
 .../packet-captures/pcaps-bucket-setup.mdx    |    4 +-
 .../diagnose-traffic-decisions.mdx            |    8 +-
 .../access-controls/access-settings/index.mdx |    1 -
 .../require-access-protection.mdx             |   10 +-
 .../access-settings/session-management.mdx    |    1 +
 .../access-controls/ai-controls/index.mdx     |    1 -
 .../ai-controls/mcp-portals.mdx               |   16 +-
 .../application-token.mdx                     |   78 +-
 .../http-apps/authorization-cookie/cors.mdx   |    7 +-
 .../applications/http-apps/managed-oauth.mdx  |   14 +-
 .../http-apps/saas-apps/generic-oidc-saas.mdx |   11 +-
 .../saas-apps/grafana-cloud-saas-oidc.mdx     |    2 +-
 .../http-apps/saas-apps/grafana-saas-oidc.mdx |    2 +-
 .../http-apps/saas-apps/index.mdx             |    3 +-
 .../non-http/browser-rendering.mdx            |    9 +-
 .../arbitrary-tcp.mdx                         |    4 +-
 .../automatic-cloudflared-authentication.mdx  |    2 +-
 .../non-http/legacy-private-network-app.mdx   |    5 +-
 .../non-http/self-hosted-private-app.mdx      |   76 +-
 .../access-controls/event-subscriptions.mdx   |    2 +-
 .../access-controls/policies/app-paths.mdx    |   17 +-
 .../access-controls/policies/index.mdx        |   46 +-
 .../policies/policy-management.mdx            |   29 +-
 .../require-purpose-justification.mdx         |    1 -
 .../policies/temporary-auth.mdx               |    8 +-
 .../service-credentials/index.mdx             |    1 -
 .../service-credentials/service-tokens.mdx    |    4 +-
 .../docs/cloudflare-one/account-limits.mdx    |   19 +-
 .../docs/cloudflare-one/changelog/tunnel.mdx  |    5 +-
 .../data-classification/index.mdx             |   12 +-
 .../configure-detection-entries.mdx           |   20 +-
 .../predefined-detection-entries.mdx          |  296 ++---
 .../dlp-profiles/predefined-profiles.mdx      |   15 +-
 .../email-security/investigation/index.mdx    |    4 +-
 .../investigation/search-email.mdx            |    4 +-
 .../email-security/reference/index.mdx        |    4 +-
 .../reference/regional-processing.mdx         |    2 +-
 .../email-security/settings/auto-moves.mdx    |    4 +-
 .../detection-settings/best-practices.mdx     |    6 +-
 .../settings/detection-settings/index.mdx     |    4 +-
 .../settings/domain-management/domain.mdx     |    2 +-
 .../settings/domain-management/index.mdx      |    4 +-
 .../email-security/settings/index.mdx         |    4 +-
 .../phish-submissions/phishnet-365.mdx        |    2 +-
 .../phishnet-google-workspace.mdx             |    2 +-
 .../submission-addresses.mdx                  |    2 +-
 .../email-security/setup/index.mdx            |   18 +-
 .../email-security/setup/manage-domains.mdx   |    2 +-
 .../bcc-setup/gmail-bcc-setup/index.mdx       |    5 +-
 .../bcc-journaling/bcc-setup/index.mdx        |    5 +-
 .../bcc-journaling/index.mdx                  |    2 +-
 .../bcc-journaling/journaling-setup/index.mdx |    5 +-
 .../journaling-setup/m365-journaling.mdx      |    3 +-
 .../journaling-setup/manual-add.mdx           |    1 -
 .../setup/post-delivery-deployment/index.mdx  |    4 +-
 .../pre-delivery-deployment/egress-ips.mdx    |    2 +-
 .../setup/pre-delivery-deployment/index.mdx   |    6 +-
 .../partner-domain-tls.mdx                    |    2 +-
 .../prerequisites/index.mdx                   |    6 +-
 .../use-cases/index.mdx                       |    5 +-
 .../email-security/submissions/index.mdx      |    2 +-
 .../submissions/invalid-submissions.mdx       |    2 +-
 .../docs/cloudflare-one/faq/devices-faq.mdx   |   11 +-
 .../insights/analytics-overview.mdx           |    2 +-
 .../insights/analytics/ai-security.mdx        |   26 +-
 .../insights/analytics/application-access.mdx |   36 +-
 .../insights/dex/mcp-server.mdx               |    3 +-
 .../insights/dex/monitoring.mdx               |   10 +-
 .../cloudflare-one/insights/dex/rules.mdx     |    2 +-
 .../insights/dex/tests/index.mdx              |    6 +-
 .../docs/cloudflare-one/insights/index.mdx    |   18 +-
 .../dashboard-logs/admin-activity-logs.mdx    |   24 +-
 .../dashboard-logs/gateway-logs/index.mdx     |   63 +-
 .../insights/logs/dashboard-logs/index.mdx    |    2 +-
 .../logs/dashboard-logs/posture-logs.mdx      |    2 +-
 .../insights/logs/logpush/index.mdx           |   32 +-
 .../diagnostics/buckets.mdx                   |    4 +-
 .../network-visibility/diagnostics/index.mdx  |    5 +-
 .../integrations/cloud-and-saas/anthropic.mdx |   22 +-
 .../microsoft-365/m365-copilot-fedramp.mdx    |    2 +-
 .../microsoft-365/m365-copilot.mdx            |    2 +-
 .../identity-providers/aws-saml.mdx           |    2 +-
 .../identity-providers/cloudflare.mdx         |    4 +-
 .../identity-providers/facebook-login.mdx     |    8 +-
 .../identity-providers/github.mdx             |    4 +-
 .../integrations/identity-providers/index.mdx |    1 -
 .../integrations/identity-providers/okta.mdx  |    4 +-
 .../identity-providers/pingone-saml.mdx       |    1 -
 .../identity-providers/signed_authn.mdx       |    2 -
 .../integrations/service-providers/index.mdx  |    4 +-
 .../networks/connectivity-options.mdx         |   22 +-
 .../connectors/cloudflare-mesh/routes.mdx     |    1 +
 .../configure-tunnels/cipher-suites.mdx       |   10 +-
 .../configure-tunnels/index.mdx               |    2 +-
 .../configure-tunnels/origin-parameters.mdx   |   16 +-
 .../remote-tunnel-permissions.mdx             |  126 +-
 .../configure-tunnels/run-parameters.mdx      |   28 +-
 .../system-requirements.mdx                   |    5 +-
 .../tunnel-with-firewall.mdx                  |   19 +-
 .../deployment-guides/index.mdx               |    2 +-
 .../deployment-guides/terraform.mdx           |    1 -
 .../tunnel-useful-commands.mdx                |   14 +-
 .../downloads/copyrights.mdx                  |   57 +-
 .../cloudflare-tunnel/downloads/license.mdx   |    1 -
 .../get-started/create-remote-tunnel-api.mdx  |  117 +-
 .../get-started/create-remote-tunnel.mdx      |    6 +-
 .../cloudflare-tunnel/get-started/index.mdx   |    3 +-
 .../connectors/cloudflare-tunnel/index.mdx    |    4 +-
 .../monitor-tunnels/index.mdx                 |    3 +-
 .../monitor-tunnels/notifications.mdx         |    3 +-
 .../private-net/cloudflared/connect-cidr.mdx  |   14 +-
 .../private-net/cloudflared/index.mdx         |    3 +-
 .../private-net/cloudflared/private-dns.mdx   |   23 +-
 .../routing-to-tunnel/dns.mdx                 |   13 +-
 .../routing-to-tunnel/protocols.mdx           |   14 +-
 .../public-load-balancers.mdx                 |   41 +-
 .../troubleshoot-tunnels/common-errors.mdx    |    1 -
 .../troubleshoot-tunnels/diag-logs.mdx        |   59 +-
 .../troubleshoot-tunnels/index.mdx            |    2 +-
 .../cloudflare-tunnel/use-cases/index.mdx     |    9 +-
 .../cloudflare-tunnel/use-cases/rdp/index.mdx |    2 +-
 .../use-cases/rdp/rdp-device-client.mdx       |    2 +-
 .../use-cases/vnc-browser-rendering.mdx       |  214 ++--
 .../cloudflare-wan/analytics/index.mdx        |   23 +-
 .../analytics/netflow-analytics.mdx           |    9 +-
 .../analytics/network-analytics.mdx           |    5 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 .../analytics/site-analytics.mdx              |   16 +-
 .../configure-hardware-appliance/index.mdx    |   84 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/configure-virtual-appliance.mdx |   80 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |   11 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../maintenance/deactivate-appliance.mdx      |    1 -
 .../appliance/maintenance/heartbeat.mdx       |    1 -
 .../appliance/maintenance/index.mdx           |    3 +-
 .../maintenance/interrupt-service-window.mdx  |    1 -
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   18 +-
 .../application-based-policies/index.mdx      |   14 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    5 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   14 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../configuration/appliance/reference.mdx     |   33 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../check-tunnel-health-dashboard.mdx         |   11 +-
 .../configure-tunnel-health-alerts.mdx        |    6 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |   12 +-
 .../update-tunnel-health-checks-frequency.mdx |    3 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   34 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   45 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |   11 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../third-party/alibaba-cloud.mdx             |   19 +-
 .../third-party/aruba-edgeconnect.mdx         |   15 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   22 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   22 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    5 +-
 .../third-party/cisco-meraki-static.mdx       |   30 +-
 .../configuration/third-party/fitelnet.mdx    |   19 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   16 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   19 +-
 .../configuration/third-party/oracle.mdx      |   16 +-
 .../configuration/third-party/palo-alto.mdx   |   19 +-
 .../configuration/third-party/pfsense.mdx     |   19 +-
 .../configuration/third-party/sonicwall.mdx   |   22 +-
 .../third-party/sophos-firewall.mdx           |   22 +-
 .../configuration/third-party/strongswan.mdx  |   13 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   13 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../connectors/cloudflare-wan/get-started.mdx |   21 +-
 .../connectors/cloudflare-wan/index.mdx       |   20 +-
 .../cloudflare-wan/legal/3rdparty.mdx         |    1 -
 .../connectors/cloudflare-wan/legal/index.mdx |    3 +-
 .../cloudflare-wan/network-interconnect.mdx   |   17 +-
 .../connectors/cloudflare-wan/on-ramps.mdx    |   20 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    3 +-
 .../reference/device-compatibility.mdx        |   76 +-
 .../reference/gre-ipsec-tunnels.mdx           |   10 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |   10 +-
 .../cloudflare-wan/reference/index.mdx        |    3 +-
 .../cloudflare-wan/reference/mtu-mss.mdx      |    2 +-
 .../reference/traffic-steering.mdx            |   28 +-
 .../reference/tunnel-health-checks.mdx        |   12 +-
 .../connectors/cloudflare-wan/security.mdx    |    9 +-
 .../troubleshooting/connectivity.mdx          |   15 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   17 +-
 .../troubleshooting/routing-and-bgp.mdx       |   24 +-
 .../troubleshooting/tunnel-health.mdx         |   33 +-
 .../cloudflare-wan/wan-transformation.mdx     |   12 +-
 .../zero-trust/cloudflare-gateway.mdx         |   45 +-
 .../zero-trust/cloudflare-one-client.mdx      |   24 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   15 +-
 .../cloudflare-wan/zero-trust/index.mdx       |    1 -
 .../zero-trust/security-services.mdx          |    9 +-
 .../connectors/granular-permissions.mdx       |    2 +-
 .../networks/connectors/index.mdx             |    3 +-
 .../networks/routes/add-routes.mdx            |   20 +-
 .../networks/routes/reserved-ips.mdx          |    4 +-
 .../networks/virtual-networks.mdx             |   12 +-
 .../accessibility.mdx                         |    2 +-
 .../remote-browser-isolation/index.mdx        |    2 -
 .../known-limitations.mdx                     |    5 +-
 .../network-dependencies.mdx                  |    4 +-
 .../remote-browser-isolation/setup/index.mdx  |   14 +-
 .../custom-pages/gateway-block-page.mdx       |    2 +-
 .../custom-pages/index.mdx                    |    2 +-
 .../client-checks/antivirus.mdx               |   31 +-
 .../client-checks/application-check.mdx       |    4 +-
 .../client-checks/file-check.mdx              |    3 +-
 .../posture-checks/client-checks/firewall.mdx |   11 +-
 .../posture-checks/client-checks/index.mdx    |   41 +-
 .../client-checks/os-version.mdx              |    3 +-
 .../client-checks/require-warp.mdx            |    2 +-
 .../reusable-components/tags.mdx              |    1 -
 .../configure/modes/index.mdx                 |    4 +-
 .../troubleshooting/common-issues.mdx         |   15 +
 .../troubleshooting/connectivity-status.mdx   |   36 +-
 .../troubleshooting/diagnostic-logs.mdx       |  184 +--
 .../devices/device-registration.mdx           |   35 +-
 .../devices/user-side-certificates/index.mdx  |   10 +-
 .../manual-deployment.mdx                     |  218 ++--
 .../team-and-resources/users/risk-score.mdx   |   19 +-
 .../team-and-resources/users/scim.mdx         |    3 +-
 .../team-and-resources/users/users.mdx        |   10 +-
 .../traffic-policies/global-policies.mdx      |   18 +-
 .../network-policies/protocol-detection.mdx   |   18 +-
 .../best-practices/magic-transit-egress.mdx   |    6 +-
 .../tiered-policies/index.mdx                 |   12 +-
 .../tiered-policies/tenant-api.mdx            |    1 -
 .../cloudflare-one/troubleshooting/access.mdx |    2 +-
 .../troubleshooting/browser-isolation.mdx     |    2 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    2 +-
 .../troubleshooting/contact-support.mdx       |    4 +
 .../cloudflare-one/troubleshooting/dex.mdx    |    2 +-
 .../troubleshooting/email-security.mdx        |    2 +-
 .../troubleshooting/gateway.mdx               |    2 +-
 .../cloudflare-one/troubleshooting/tunnel.mdx |   33 +-
 .../troubleshooting/wan/connectivity.mdx      |   17 +-
 .../troubleshooting/wan/index.mdx             |    2 +-
 .../troubleshooting/wan/ipsec.mdx             |   19 +-
 .../troubleshooting/wan/routing-bgp.mdx       |   26 +-
 .../troubleshooting/wan/tunnel-health.mdx     |   35 +-
 .../troubleshooting/warp-client.mdx           |    2 +-
 .../tutorials/entra-id-risky-users.mdx        |   40 +-
 .../docs/cloudflare-wan/analytics/index.mdx   |    7 +-
 .../analytics/netflow-analytics.mdx           |    5 +-
 .../analytics/network-analytics.mdx           |    7 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    6 +-
 .../analytics/query-tunnel-health.mdx         |    9 +-
 .../analytics/site-analytics.mdx              |   19 +-
 src/content/docs/cloudflare-wan/changelog.mdx |    7 +-
 .../configure-hardware-appliance/index.mdx    |   79 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |    9 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../appliance/maintenance/index.mdx           |    5 +-
 .../maintenance/register-appliance.mdx        |    2 +-
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   27 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-options.mdx     |   42 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    7 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   11 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |    8 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   25 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   32 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |    7 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../configuration/multi-cloud-networking.mdx  |    3 +-
 .../third-party/alibaba-cloud.mdx             |   20 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   21 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   21 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    6 +-
 .../third-party/cisco-meraki-static.mdx       |   21 +-
 .../configuration/third-party/fitelnet.mdx    |   20 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   17 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   18 +-
 .../configuration/third-party/oracle.mdx      |   17 +-
 .../configuration/third-party/palo-alto.mdx   |   18 +-
 .../configuration/third-party/pfsense.mdx     |   20 +-
 .../configuration/third-party/sonicwall.mdx   |   23 +-
 .../third-party/sophos-firewall.mdx           |   23 +-
 .../configuration/third-party/strongswan.mdx  |   14 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   14 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../docs/cloudflare-wan/get-started.mdx       |   11 +-
 src/content/docs/cloudflare-wan/glossary.mdx  |    3 +-
 src/content/docs/cloudflare-wan/index.mdx     |    5 +-
 .../docs/cloudflare-wan/legal/3rdparty.mdx    |    3 +-
 .../docs/cloudflare-wan/legal/index.mdx       |    5 +-
 .../cloudflare-wan/network-interconnect.mdx   |   16 +-
 src/content/docs/cloudflare-wan/on-ramps.mdx  |    4 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    4 +-
 .../reference/device-compatibility.mdx        |   58 +-
 .../reference/gre-ipsec-tunnels.mdx           |    4 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/cloudflare-wan/reference/index.mdx   |    5 +-
 .../docs/cloudflare-wan/reference/mtu-mss.mdx |    6 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    9 +-
 .../reference/virtual-networks.mdx            |    9 +-
 src/content/docs/cloudflare-wan/security.mdx  |    8 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   10 +-
 .../troubleshooting/routing-and-bgp.mdx       |   22 +-
 .../troubleshooting/tunnel-health.mdx         |   30 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   12 +-
 .../zero-trust/connectivity-options.mdx       |   19 +-
 .../docs/cloudflare-wan/zero-trust/index.mdx  |    4 +-
 .../docs/constellation/platform/index.mdx     |    2 +-
 src/content/docs/containers/examples/cron.mdx |   41 +-
 .../examples/durable-object-interface.mdx     |    1 -
 .../docs/containers/examples/index.mdx        |    1 -
 .../containers/platform-details/placement.mdx |    8 +-
 src/content/docs/containers/pricing.mdx       |    2 +-
 src/content/docs/containers/ssh.mdx           |    2 +-
 .../d1/best-practices/local-development.mdx   |    2 -
 .../docs/d1/best-practices/query-d1.mdx       |   50 +-
 .../d1/best-practices/remote-development.mdx  |   15 +-
 .../docs/d1/best-practices/retry-queries.mdx  |   26 +-
 .../d1/best-practices/use-d1-from-pages.mdx   |    2 +-
 .../docs/d1/best-practices/use-indexes.mdx    |   26 +-
 .../docs/d1/configuration/environments.mdx    |   60 +-
 src/content/docs/d1/get-started.mdx           |   12 +-
 src/content/docs/d1/observability/billing.mdx |    4 +-
 src/content/docs/d1/platform/limits.mdx       |   34 +-
 .../docs/d1/reference/community-projects.mdx  |   40 +-
 .../docs/d1/reference/data-security.mdx       |    6 +-
 src/content/docs/d1/reference/faq.mdx         |    4 +-
 .../docs/d1/reference/generated-columns.mdx   |   24 +-
 src/content/docs/d1/reference/glossary.mdx    |    2 +-
 src/content/docs/d1/reference/migrations.mdx  |    6 +-
 src/content/docs/d1/sql-api/foreign-keys.mdx  |   28 +-
 src/content/docs/d1/sql-api/query-json.mdx    |   82 +-
 .../tutorials/build-an-api-to-access-d1.mdx   |    8 +-
 .../docs/d1/tutorials/d1-and-prisma-orm.mdx   |    2 +-
 .../docs/data-localization/compatibility.mdx  |   68 +-
 .../data-localization/geo-key-manager.mdx     |    5 +-
 .../docs/ddos-protection/about/components.mdx |    3 +-
 .../about/how-ddos-protection-works.mdx       |   17 +-
 .../docs/ddos-protection/about/index.mdx      |    5 +-
 .../api/dns-protection/index.mdx              |   17 +-
 .../api/dns-protection/json-objects.mdx       |   21 +-
 .../advanced-ddos-systems/api/index.mdx       |    3 +-
 .../programmable-flow-protection/examples.mdx |  209 ++-
 .../programmable-flow-protection/index.mdx    |   37 +-
 .../json-objects.mdx                          |   61 +-
 .../api/tcp-protection/examples.mdx           |  217 ++--
 .../api/tcp-protection/index.mdx              |  103 +-
 .../api/tcp-protection/json-objects.mdx       |   51 +-
 .../how-to/add-prefix.mdx                     |    6 +-
 .../how-to/exclude-prefix.mdx                 |    5 +-
 .../advanced-ddos-systems/how-to/index.mdx    |    5 +-
 .../advanced-ddos-systems/index.mdx           |    4 +-
 .../advanced-ddos-systems/overview/index.mdx  |   16 +-
 .../overview/programmable-flow-protection.mdx |   92 +-
 .../advanced-ddos-systems/troubleshooting.mdx |   13 +-
 .../ddos-protection/best-practices/index.mdx  |    3 +-
 .../best-practices/proactive-defense.mdx      |    4 +-
 .../best-practices/third-party.mdx            |    2 +-
 .../ddos-protection/botnet-threat-feed.mdx    |   58 +-
 .../docs/ddos-protection/get-started.mdx      |    3 +-
 .../managed-rulesets/http/index.mdx           |    2 +-
 .../managed-rulesets/index.mdx                |    1 -
 .../managed-rulesets/network/index.mdx        |    2 +-
 .../network-overrides/override-examples.mdx   |   12 +-
 .../docs/ddos-protection/reference/alerts.mdx |    2 +-
 .../docs/ddos-protection/reference/index.mdx  |    3 +-
 .../docs/ddos-protection/reference/logs.mdx   |    3 +-
 .../reference/simulate-ddos-attack.mdx        |    3 +-
 src/content/docs/dmarc-management/enable.mdx  |    3 +-
 .../dmarc-management/security-records.mdx     |    2 +-
 .../docs/dmarc-management/statistics.mdx      |    1 -
 .../docs/dns/additional-options/index.mdx     |    2 +-
 src/content/docs/dns/changelog.mdx            |    8 +-
 .../docs/dns/cname-flattening/index.mdx       |    2 +-
 .../set-up-cname-flattening.mdx               |    8 +-
 .../random-prefix-attacks/setup.mdx           |   11 +-
 src/content/docs/dns/dnssec/dnssec-states.mdx |   13 +-
 src/content/docs/dns/dnssec/enable-nsec3.mdx  |    4 +-
 src/content/docs/dns/dnssec/index.mdx         |   19 +-
 .../dns/dnssec/multi-signer-dnssec/about.mdx  |    4 +-
 .../dns/dnssec/multi-signer-dnssec/setup.mdx  |    2 +-
 .../dnssec/validation-and-key-management.mdx  |    8 +-
 .../docs/dns/foundation-dns/dnssec-keys.mdx   |    3 +-
 src/content/docs/dns/foundation-dns/index.mdx |   23 +-
 src/content/docs/dns/glossary.mdx             |    2 +-
 .../docs/dns/internal-dns/analytics.mdx       |    2 +-
 .../how-to/create-subdomain.mdx               |    3 +-
 .../how-to/email-records.mdx                  |   15 +-
 .../dns/manage-dns-records/how-to/index.mdx   |    3 +-
 .../how-to/managing-dynamic-ip-addresses.mdx  |    3 +-
 .../how-to/round-robin-dns.mdx                |    1 -
 .../how-to/subdomains-outside-cloudflare.mdx  |   17 +-
 .../manage-dns-records/reference/index.mdx    |    3 +-
 .../reference/record-attributes.mdx           |   17 +-
 .../dns/manage-dns-records/reference/ttl.mdx  |    3 +-
 .../troubleshooting/exposed-ip-address.mdx    |    3 +-
 .../troubleshooting/index.mdx                 |    5 +-
 .../dns/nameservers/advanced-nameservers.mdx  |    1 -
 .../zone-custom-nameservers.mdx               |    1 +
 .../docs/dns/private-origins/index.mdx        |    3 +-
 .../docs/dns/reference/all-features.mdx       |    3 +-
 .../dns/reference/analytics-mcp-server.mdx    |    3 +-
 .../docs/dns/reference/best-practices.mdx     |    3 +-
 .../docs/dns/reference/domain-connect.mdx     |   18 +-
 src/content/docs/dns/reference/index.mdx      |    2 +-
 .../recommended-third-party-tools.mdx         |    9 +-
 .../docs/dns/troubleshooting/email-issues.mdx |   12 +-
 .../docs/dns/troubleshooting/index.mdx        |    9 +-
 .../conversions/convert-full-to-secondary.mdx |   34 +-
 .../conversions/convert-partial-to-full.mdx   |    2 +-
 .../dns/zone-setups/conversions/index.mdx     |    2 +-
 .../docs/dns/zone-setups/full-setup/index.mdx |    2 +-
 .../partial-setup/dns-resolution.mdx          |    7 +-
 .../dns/zone-setups/partial-setup/setup.mdx   |   11 +-
 .../zone-setups/reference/domain-status.mdx   |   10 +-
 .../docs/dns/zone-setups/reference/index.mdx  |    3 +-
 .../subdomain-setup/move-to-new-account.mdx   |    1 -
 .../zone-setups/subdomain-setup/rollback.mdx  |    5 +-
 .../subdomain-setup/setup/parent-on-full.mdx  |    3 -
 .../setup/parent-on-partial.mdx               |    3 +-
 .../dns/zone-setups/troubleshooting/index.mdx |    3 +-
 .../cloudflare-as-primary/index.mdx           |    2 +-
 .../transfer-criteria.mdx                     |    3 +-
 .../cloudflare-as-secondary/alerts.mdx        |    3 +-
 .../cloudflare-as-secondary/index.mdx         |    4 +-
 .../cloudflare-as-secondary/proxy-traffic.mdx |    2 +-
 .../docs/durable-objects/api/alarms.mdx       |   77 +-
 .../api/legacy-kv-storage-api.mdx             |   13 +-
 .../api/sqlite-storage-api.mdx                |   24 +-
 .../access-durable-objects-storage.mdx        |    3 +
 .../concepts/durable-object-lifecycle.mdx     |    2 +-
 .../docs/durable-objects/examples/agents.mdx  |    2 +-
 .../docs/durable-objects/examples/index.mdx   |    5 +-
 .../examples/websocket-server.mdx             |    8 +-
 .../observability/data-studio.mdx             |    2 +-
 .../durable-objects/platform/known-issues.mdx |    2 +-
 .../docs/durable-objects/platform/limits.mdx  |    1 -
 .../reference/data-location.mdx               |   16 +-
 .../reference/data-security.mdx               |    6 +-
 .../reference/environments.mdx                |    7 +-
 .../docs/durable-objects/reference/faq.mdx    |    6 +-
 .../durable-objects/reference/glossary.mdx    |    2 +-
 .../reference/in-memory-state.mdx             |   30 +-
 .../docs/durable-objects/video-tutorials.mdx  |   12 +-
 .../docs/dynamic-workers/usage/bindings.mdx   |  140 +-
 .../email-workers/local-development.mdx       |   95 +-
 .../email-workers/reply-email-workers.mdx     |   60 +-
 .../email-routing/get-started/audit-logs.mdx  |    8 +-
 .../docs/email-routing/get-started/index.mdx  |    2 +-
 .../docs/email-routing/graphql-example.mdx    |    2 +-
 src/content/docs/email-routing/limits.mdx     |    2 +-
 src/content/docs/email-routing/postmaster.mdx |    3 +-
 .../setup/email-routing-dns-records.mdx       |    8 +-
 .../docs/email-routing/setup/index.mdx        |    2 +-
 .../email-routing/troubleshooting/index.mdx   |    2 +-
 .../email-security/account-setup/index.mdx    |    2 +-
 .../gsuite-bcc-setup/create-project-gcp.mdx   |    4 +-
 .../deployment/inline/reference/index.mdx     |    2 +-
 .../deployment/inline/setup/index.mdx         |    2 +-
 .../domains-and-routing/alert-webhooks.mdx    |   10 +-
 .../domains-and-routing/index.mdx             |    2 +-
 .../email-policies/index.mdx                  |    2 +-
 .../enhanced-detections/index.mdx             |    2 +-
 .../email-configuration/lists/index.mdx       |    2 +-
 .../migrate-to-email-security.mdx             |   26 +-
 .../docs/email-security/reference/index.mdx   |    2 +-
 src/content/docs/email-service/api/index.mdx  |    2 +-
 .../api/route-emails/email-handler.mdx        |    2 +-
 .../email-service/api/route-emails/index.mdx  |    2 +-
 .../api/send-emails/rest-api.mdx              |   52 +-
 .../api/send-emails/workers-api.mdx           |   40 +-
 .../docs/email-service/concepts/index.mdx     |    2 +-
 .../email-service/configuration/index.mdx     |    2 +-
 .../email-routing/hard-bounce-handling.mdx    |  241 ++--
 .../examples/email-routing/spam-filtering.mdx |   33 +-
 .../email-service/get-started/send-emails.mdx |   34 +-
 .../email-service/local-development/index.mdx |    2 +-
 .../local-development/routing.mdx             |   44 +-
 .../docs/email-service/platform/index.mdx     |    2 +-
 .../docs/email-service/platform/pricing.mdx   |    8 +-
 .../docs/email-service/reference/index.mdx    |    5 +-
 .../email-service/reference/postmaster.mdx    |    1 -
 .../docs/firewall/api/cf-filters/delete.mdx   |   38 +-
 .../docs/firewall/api/cf-filters/get.mdx      |  100 +-
 .../docs/firewall/api/cf-filters/post.mdx     |   68 +-
 .../docs/firewall/api/cf-filters/put.mdx      |   52 +-
 .../firewall/api/cf-filters/validation.mdx    |   34 +-
 .../api/cf-filters/what-is-a-filter.mdx       |   10 +-
 .../firewall/api/cf-firewall-rules/get.mdx    |  160 +--
 .../firewall/api/cf-firewall-rules/post.mdx   |  116 +-
 .../cf-firewall-rules/order-priority.mdx      |    1 -
 .../account-security/cloudflare-access.mdx    |    4 +-
 .../account/account-security/index.mdx        |    2 +-
 .../leaked-password-notifications.mdx         |    2 -
 .../manage-active-sessions.mdx                |    2 +-
 .../account/account-security/zone-holds.mdx   |    4 +-
 .../fundamentals/account/create-account.mdx   |   11 +-
 .../account/find-account-and-zone-ids.mdx     |   12 +-
 .../docs/fundamentals/account/index.mdx       |    2 +-
 .../api/how-to/control-api-access.mdx         |    6 +-
 .../api/how-to/create-via-api.mdx             |   32 +-
 .../api/how-to/restrict-tokens.mdx            |    7 +-
 src/content/docs/fundamentals/api/index.mdx   |    2 +-
 .../docs/fundamentals/api/reference/index.mdx |    2 +-
 .../fundamentals/api/reference/limits.mdx     |    6 +-
 .../docs/fundamentals/api/troubleshooting.mdx |   18 +-
 .../concepts/how-cloudflare-works.mdx         |    8 +-
 .../docs/fundamentals/concepts/index.mdx      |    2 +-
 .../concepts/traffic-flow-cloudflare.mdx      |   22 +-
 src/content/docs/fundamentals/index.mdx       |    4 +-
 .../fundamentals/manage-domains/add-site.mdx  |   11 +-
 .../manage-domains/domain-version.mdx         |   12 +-
 .../manage-domains/move-domain.mdx            |    2 -
 .../manage-domains/pause-cloudflare.mdx       |    4 +-
 .../fundamentals/manage-members/index.mdx     |    2 +-
 .../fundamentals/manage-members/policies.mdx  |    5 +-
 .../fundamentals/manage-members/roles.mdx     |    2 +-
 .../fundamentals/manage-members/scope.mdx     |   52 +-
 .../manage-members/user-groups.mdx            |   23 +-
 .../docs/fundamentals/new-features/index.mdx  |    4 +-
 .../organizations/limitations.mdx             |    4 +-
 .../docs/fundamentals/organizations/setup.mdx |   16 +-
 .../fundamentals/performance/improve-seo.mdx  |   16 +-
 .../docs/fundamentals/performance/index.mdx   |    2 +-
 .../fundamentals/performance/test-speed.mdx   |   16 +-
 .../fundamentals/reference/best-practices.mdx |    6 +-
 .../reference/cdn-cgi-endpoint.mdx            |   12 +-
 .../reference/cloudflare-ray-id.mdx           |    3 +-
 .../reference/connection-limits.mdx           |   22 +-
 .../reference/cryptographic-personhood.mdx    |   44 +-
 .../docs/fundamentals/reference/glossary.mdx  |    2 +-
 .../reference/google-analytics.mdx            |    4 -
 .../docs/fundamentals/reference/index.mdx     |    2 +-
 .../scim-virtual-groups-migration.mdx         |   17 +-
 .../docs/fundamentals/reference/partners.mdx  |    2 +-
 .../delivering-videos-with-cloudflare.mdx     |   18 +-
 .../reference/policies-compliances/index.mdx  |    2 +-
 .../docs/fundamentals/reference/redirects.mdx |    2 +-
 .../report-abuse/abuse-report-obligations.mdx |    6 +-
 .../report-abuse/complaint-types.mdx          |   26 +-
 .../reference/report-abuse/index.mdx          |    8 +-
 .../reference/report-abuse/submit-report.mdx  |   12 +-
 .../sdk-ecosystem-support-policy.mdx          |   14 +-
 .../reference/tcp-connections.mdx             |    4 +-
 .../reference/troubleshooting.mdx             |   44 +-
 .../docs/fundamentals/security/index.mdx      |    2 +-
 .../docs/fundamentals/security/pci-scans.mdx  |    6 +-
 .../security/under-ddos-attack.mdx            |    8 +-
 .../docs/fundamentals/user-profiles/2fa.mdx   |   34 +-
 .../user-profiles/account-recovery.mdx        |   10 +-
 .../change-password-or-email.mdx              |    2 +-
 .../user-profiles/customize-account.mdx       |    6 +-
 .../user-profiles/delete-account.mdx          |    5 +-
 .../docs/fundamentals/user-profiles/login.mdx |    7 +-
 .../multi-factor-email-authentication.mdx     |    6 +-
 .../user-profiles/verify-email-address.mdx    |    6 +-
 src/content/docs/google-tag-gateway/index.mdx |    6 +-
 .../concepts/health-checks-regions.mdx        |    1 -
 .../docs/health-checks/concepts/index.mdx     |    3 +-
 .../health-checks/health-checks-analytics.mdx |    3 +-
 .../how-to/health-checks-notifications.mdx    |    5 +-
 .../docs/health-checks/how-to/index.mdx       |    3 +-
 .../health-checks/how-to/zone-lockdown.mdx    |    3 +-
 .../drizzle-orm.mdx                           |    4 +-
 .../prisma-postgres.mdx                       |   15 +-
 .../postgres-database-providers/supabase.mdx  |    2 +-
 .../observability/troubleshooting.mdx         |   78 +-
 .../docs/hyperdrive/platform/limits.mdx       |   28 +-
 .../hyperdrive/platform/storage-options.mdx   |    2 +-
 .../reference/wrangler-commands.mdx           |    2 +-
 .../docs/hyperdrive/tutorials/index.mdx       |    2 +-
 ...rverless-timeseries-api-with-timescale.mdx |    2 +-
 .../optimization/make-responsive-images.mdx   |   17 +-
 .../optimization/transformations/flows.mdx    |   19 +-
 .../optimization/transformations/overview.mdx |    3 +-
 .../docs/key-transparency/api/epochs.mdx      |    2 +-
 .../docs/key-transparency/api/index.mdx       |    4 +-
 .../docs/key-transparency/api/namespaces.mdx  |    8 +-
 .../docs/kv/api/delete-key-value-pairs.mdx    |   37 +-
 src/content/docs/kv/concepts/kv-bindings.mdx  |   32 +-
 .../docs/kv/concepts/kv-namespaces.mdx        |   17 +-
 src/content/docs/kv/get-started.mdx           |   15 +-
 src/content/docs/kv/glossary.mdx              |    2 +-
 src/content/docs/kv/observability/index.mdx   |    2 +-
 .../kv/observability/metrics-analytics.mdx    |    1 +
 src/content/docs/kv/platform/pricing.mdx      |    2 +-
 .../docs/kv/reference/data-security.mdx       |    6 +-
 .../docs/kv/reference/environments.mdx        |    2 -
 src/content/docs/kv/reference/kv-commands.mdx |    4 +-
 .../account-security/audit-logs.mdx           |    2 +-
 .../account-security/index.mdx                |    6 +-
 .../review-active-sessions.mdx                |    2 +-
 .../account-security/review-audit-logs.mdx    |    2 +-
 .../account-security/set-up-2fa.mdx           |    4 +-
 .../browser-integrity.mdx                     |    2 +-
 .../default-traffic-security/ddos.mdx         |    4 +-
 .../default-traffic-security/dnssec.mdx       |    2 +-
 .../default-traffic-security/index.mdx        |    2 +-
 .../default-traffic-security/mtls.mdx         |    2 +-
 .../application-security/firewall/index.mdx   |    4 +-
 .../lists/configuration.mdx                   |    2 +-
 .../application-security/lists/features.mdx   |    2 +-
 .../application-security/lists/index.mdx      |    8 +-
 .../application-security/lists/use-cases.mdx  |    2 +-
 .../rate-limiting/configurations.mdx          |   16 +-
 .../rate-limiting/features.mdx                |    2 +-
 .../rate-limiting/index.mdx                   |    4 +-
 .../rate-limiting/use-cases.mdx               |    2 +-
 .../security-center/brand-protection.mdx      |    2 +-
 .../security-center/index.mdx                 |    6 +-
 .../access-application/index.mdx              |    8 +-
 .../advanced-workflows/index.mdx              |    8 +-
 .../alternative-onramps/clientless-rbi.mdx    |    6 +-
 .../alternative-onramps/index.mdx             |    4 +-
 .../clientless-access/concepts/index.mdx      |    2 +-
 .../concepts/what-is-clientless-access.mdx    |    2 +-
 .../best-practices.mdx                        |    6 +-
 .../create-tunnel.mdx                         |   11 +-
 .../connect-private-applications/index.mdx    |    4 +-
 .../customize-ux/app-launcher.mdx             |    2 +-
 .../customize-ux/block-page.mdx               |    2 +-
 .../customize-ux/bookmarks.mdx                |    2 +-
 .../clientless-access/customize-ux/index.mdx  |    8 +-
 .../customize-ux/login-page.mdx               |    2 +-
 .../clientless-access/customize-ux/tags.mdx   |    2 +-
 .../clientless-access/initial-setup/index.mdx |    8 +-
 .../migrate-applications/best-practices.mdx   |   14 +-
 .../migrate-applications/index.mdx            |    6 +-
 .../migrate-applications/integrated-sso.mdx   |   12 +-
 .../clientless-access/terraform/index.mdx     |    2 +-
 .../create-zero-trust-org.mdx                 |    2 +-
 .../cybersafe/account-creation/index.mdx      |    6 +-
 .../cybersafe/concepts/index.mdx              |    8 +-
 .../concepts/what-is-dns-filtering.mdx        |   18 +-
 .../gateway-verify-local-connectivity.mdx     |    8 +-
 .../advertise-prefixes.mdx                    |    2 +-
 .../data-center-protection/concepts/index.mdx |    2 +-
 .../data-center-protection/configure-ddos.mdx |   14 +-
 .../configure-routes.mdx                      |   18 +-
 .../configure-tunnels.mdx                     |   29 +-
 .../configure-tunnels-routes/index.mdx        |    2 +-
 .../enable-notifications.mdx                  |    5 +-
 .../data-center-protection/get-started.mdx    |    8 +-
 .../run-pre-flight-checks.mdx                 |    1 +
 .../dns-best-practices/concepts/index.mdx     |    8 +-
 .../dns-best-practices/concepts/phase-1.mdx   |   52 +-
 .../dns-best-practices/concepts/phase-2.mdx   |   42 +-
 .../dns-best-practices/concepts/phase-3.mdx   |   31 +-
 .../dns-best-practices/concepts/phase-4.mdx   |   38 +-
 .../concepts/summary-considerations.mdx       |   20 +-
 .../holistic-ai-security/appendix/index.mdx   |    1 -
 .../holistic-ai-security/concepts/index.mdx   |    1 -
 .../holistic-ai-security/concepts/mcp.mdx     |    1 -
 .../concepts/shadow-ai.mdx                    |    1 -
 .../get-started/additional-setup.mdx          |    2 +-
 .../get-started/define-ai-risk-tolerance.mdx  |    1 +
 .../get-started/index.mdx                     |    2 +-
 .../monitor-ai-use/index.mdx                  |    1 -
 .../monitor-prompts-responses.mdx             |    3 +-
 .../monitor-ai-use/review-inline-ai-use.mdx   |    3 +-
 .../load-balancing/concepts/health-checks.mdx |    2 +-
 .../load-balancing/concepts/index.mdx         |    8 +-
 .../concepts/load-balancer-components.mdx     |   12 +-
 .../load-balancing/concepts/routing.mdx       |    8 +-
 .../load-balancing/planning/custom-rules.mdx  |    2 +-
 .../load-balancing/planning/index.mdx         |    8 +-
 .../planning/multiple-zones.mdx               |    2 -
 .../planning/origin-steering-policies.mdx     |    6 +-
 .../planning/session-affinity.mdx             |    2 +-
 .../planning/traffic-steering.mdx             |    4 +-
 .../planning/types-load-balancers.mdx         |   16 +-
 .../setup/check-pool-health.mdx               |    2 +-
 .../setup/hostname-preparation.mdx            |    8 +-
 .../load-balancing/setup/index.mdx            |   14 +-
 .../load-balancing/setup/next-steps.mdx       |    2 +-
 .../setup/production-traffic.mdx              |    2 +-
 .../mtls/concepts/mtls-cloudflare.mdx         |   12 +-
 .../mtls/mtls-implementation/index.mdx        |    2 +-
 .../advanced/improve-analytics.mdx            |    2 +-
 .../prevent-ddos-attacks/advanced/index.mdx   |    8 +-
 .../prevent-ddos-attacks/baseline/index.mdx   |    6 +-
 .../baseline/proxy-dns-records.mdx            |    2 +-
 .../baseline/set-up-alerts.mdx                |    2 +-
 .../baseline/tls-versions.mdx                 |    4 +-
 .../prevent-ddos-attacks/concepts/index.mdx   |    4 +-
 .../replace-vpn/build-policies/index.mdx      |    8 +-
 .../build-policies/policy-design.mdx          |   10 +-
 .../build-policies/session-timeouts.mdx       |    2 +-
 .../test-your-first-application.mdx           |    7 +-
 .../replace-vpn/concepts/index.mdx            |    6 +-
 .../concepts/what-is-cloudflare.mdx           |    2 +-
 .../connect-private-network/cloudflared.mdx   |   19 +-
 .../connection-methods.mdx                    |   22 +-
 .../connect-private-network/index.mdx         |    6 +-
 .../overlapping-ips.mdx                       |    2 +-
 .../tunnel-capacity.mdx                       |    2 +-
 .../replace-vpn/get-started/prerequisites.mdx |    8 +-
 .../replace-vpn/troubleshooting/index.mdx     |    4 +-
 .../troubleshoot-private-networks.mdx         |    2 +-
 .../build-dns-policies/index.mdx              |    6 +-
 .../build-egress-policies/index.mdx           |    8 +-
 .../build-http-policies/index.mdx             |    8 +-
 .../concepts/index.mdx                        |    4 +-
 .../choose-on-ramp.mdx                        |   12 +-
 .../initial-setup/prerequisites.mdx           |    4 +-
 .../secure-saas-applications/index.mdx        |    6 +-
 .../sso-front-door.mdx                        |   10 +-
 .../understand-policies/index.mdx             |    6 +-
 .../understand-policies/indicator-feeds.mdx   |    4 +-
 .../order-of-enforcement.mdx                  |    2 +-
 .../secure-your-email/concepts/index.mdx      |    2 +-
 .../protect-from-phishing-attacks.mdx         |    2 +-
 .../concepts/what-is-cloudflare.mdx           |    4 +-
 .../concepts/what-is-email-security.mdx       |    2 +-
 .../concepts/what-is-phishing-attack.mdx      |    2 +-
 .../active-directory-sync.mdx                 |    2 +-
 .../configure-email-security/audit-logs.mdx   |    3 +-
 .../impersonation-registry.mdx                |    2 +-
 .../configure-email-security/index.mdx        |    2 +-
 .../configure-email-security/report-phish.mdx |    2 +-
 .../enable-auto-moves/index.mdx               |    2 +-
 .../get-started/deployment-models.mdx         |    4 +-
 .../get-started/prerequisites.mdx             |    2 +-
 .../recommended-deployment-model.mdx          |    2 +-
 .../get-started/setup-google-workspace.mdx    |    2 +-
 .../get-started/setup-ms-graph-api.mdx        |    4 +-
 .../monitor-your-inbox/phish-submissions.mdx  |    2 +-
 .../surge-readiness/concepts/index.mdx        |   12 +-
 .../surge-readiness/performance/analytics.mdx |    4 +-
 .../surge-readiness/performance/caching.mdx   |   22 +-
 .../surge-readiness/performance/index.mdx     |    2 +-
 .../surge-readiness/performance/logs.mdx      |    7 +-
 .../security/block-agents-lock-zones.mdx      |    1 -
 .../security/confirm-account-security.mdx     |    2 +-
 .../security/control-domain-access.mdx        |   12 +-
 .../surge-readiness/security/enable-iaum.mdx  |    4 +-
 .../surge-readiness/security/index.mdx        |    2 +-
 .../surge-readiness/support/index.mdx         |    2 +-
 .../surge-readiness/support/resources.mdx     |   15 +-
 .../workers/concepts/cloudflare-intro.mdx     |   30 +-
 .../learning-paths/workers/concepts/index.mdx |    6 +-
 .../workers/concepts/serverless-computing.mdx |    6 +-
 .../learning-paths/workers/devplat/index.mdx  |    4 +-
 .../workers/devplat/intro-to-devplat.mdx      |    2 +-
 .../workers/get-started/c3-and-wrangler.mdx   |    8 +-
 .../workers/get-started/first-application.mdx |   23 +-
 .../workers/get-started/index.mdx             |    6 +-
 .../additional-dns-records.mdx                |    5 +-
 .../additional-options/cloudflare-tunnel.mdx  |    1 -
 .../additional-options/index.mdx              |   13 +-
 .../load-balancing-china.mdx                  |    1 -
 .../load-balancing-rules/expressions.mdx      |   13 +-
 .../override-http-host-headers.mdx            |   30 +-
 .../pagerduty-integration.mdx                 |    1 -
 .../planned-maintenance.mdx                   |   12 +-
 .../docs/load-balancing/api-reference.mdx     |    1 -
 .../get-started/enable-load-balancing.mdx     |    3 +-
 .../docs/load-balancing/get-started/index.mdx |    5 +-
 .../load-balancers/common-configurations.mdx  |    7 +-
 .../docs/load-balancing/monitors/index.mdx    |    4 +-
 .../monitors/monitor-groups.mdx               |    1 -
 .../private-network/cloudflare-wan.mdx        |    6 +-
 .../reference-architecture-external-link.mdx  |    1 -
 .../docs/load-balancing/reference/index.mdx   |    3 +-
 .../load-balancing/reference/limitations.mdx  |   15 +-
 .../reference/migration-guides/index.mdx      |    3 +-
 .../troubleshooting/common-error-codes.mdx    |   53 +-
 .../load-balancing/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/load-balancing-faq.mdx    |   37 +-
 .../understand-basics/adaptive-routing.mdx    |    3 +-
 .../understand-basics/index.mdx               |    3 +-
 .../traffic-steering/index.mdx                |    1 -
 .../hash-origin-steering.mdx                  |    4 -
 .../least-outstanding-requests-pools.mdx      |    7 +-
 .../random-origin-steering.mdx                |    1 -
 .../steering-policies/dynamic-steering.mdx    |    1 -
 .../steering-policies/index.mdx               |    1 +
 .../least-outstanding-requests.mdx            |    3 +-
 .../steering-policies/proximity-steering.mdx  |    9 +-
 .../steering-policies/standard-options.mdx    |    1 -
 src/content/docs/log-explorer/api.mdx         |    6 +-
 src/content/docs/log-explorer/changelog.mdx   |    2 +-
 .../docs/log-explorer/example-queries.mdx     |    2 +-
 src/content/docs/log-explorer/index.mdx       |   42 +-
 .../docs/logs/auditlogs-mcp-server.mdx        |    2 +-
 .../docs/logs/changelog/audit-logs.mdx        |    2 +-
 src/content/docs/logs/changelog/index.mdx     |    2 +-
 src/content/docs/logs/changelog/logs.mdx      |    2 -
 .../docs/logs/faq/common-calculations.mdx     |    2 -
 src/content/docs/logs/faq/general-faq.mdx     |    3 -
 src/content/docs/logs/faq/instant-logs.mdx    |    3 -
 src/content/docs/logs/faq/logpull-api.mdx     |    5 -
 .../docs/logs/faq/worker-subrequests.mdx      |   14 +-
 src/content/docs/logs/glossary.mdx            |    2 +-
 src/content/docs/logs/logpull/index.mdx       |    4 +-
 .../docs/logs/logpull/requesting-logs.mdx     |   22 +-
 .../logs/logpull/understanding-the-basics.mdx |   24 +-
 src/content/docs/logs/logpush-mcp-server.mdx  |    2 +-
 .../examples/example-logpush-python.mdx       |    2 -
 .../docs/logs/logpush/examples/index.mdx      |    2 +-
 src/content/docs/logs/logpush/index.mdx       |    4 +-
 .../docs/logs/logpush/logpush-health.mdx      |   72 +-
 .../logpush/logpush-job/api-configuration.mdx |  140 +-
 .../logpush-job/datasets/account/index.mdx    |    2 +-
 .../logs/logpush/logpush-job/datasets/cmb.mdx |    4 +-
 .../logpush/logpush-job/datasets/index.mdx    |   16 +-
 .../logpush-job/datasets/zone/dns_logs.md     |    2 +-
 .../logpush-job/datasets/zone/index.mdx       |    2 +-
 .../logpush/logpush-job/edge-log-delivery.mdx |    3 +-
 .../enable-destinations/aws-s3.mdx            |    6 +-
 .../logpush-job/enable-destinations/azure.mdx |    1 +
 .../enable-destinations/egress-ip.mdx         |   26 +-
 .../enable-destinations/elastic.mdx           |   33 +-
 .../google-cloud-storage.mdx                  |    6 +-
 .../enable-destinations/ibm-qradar.mdx        |  150 ++-
 .../enable-destinations/kinesis.mdx           |    2 +-
 .../third-party/exabeam.mdx                   |    2 +-
 .../third-party/sekoia.mdx                    |    2 +-
 .../third-party/taegis.mdx                    |    2 +-
 .../docs/logs/logpush/logpush-job/filters.mdx |    5 +-
 .../docs/logs/logpush/logpush-job/index.mdx   |    2 +-
 .../logpush-ownership-challenge.mdx           |   22 +-
 .../2023-02-01-security-fields-updates.mdx    |   66 +-
 .../logs/reference/change-notices/index.mdx   |    2 +-
 .../logs/reference/clientrequestsource.mdx    |    3 -
 src/content/docs/logs/reference/index.mdx     |    2 +-
 .../docs/logs/reference/security-fields.mdx   |    8 +-
 .../docs/logs/reference/waf-fields.mdx        |    8 +-
 src/content/docs/magic-transit/about.mdx      |    3 +-
 src/content/docs/magic-transit/alerts.mdx     |    3 +-
 .../docs/magic-transit/analytics/index.mdx    |    9 +-
 .../analytics/network-analytics.mdx           |    6 +-
 .../analytics/packet-captures.mdx             |    1 -
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 src/content/docs/magic-transit/changelog.mdx  |    5 +-
 .../docs/magic-transit/cloudflare-ips.mdx     |   17 +-
 .../docs/magic-transit/get-started.mdx        |    8 +-
 src/content/docs/magic-transit/glossary.mdx   |    3 +-
 .../how-to/advertise-prefixes.mdx             |   56 +-
 .../magic-transit/how-to/configure-routes.mdx |   18 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   28 +-
 .../how-to/enable-magic-roles.mdx             |    2 +-
 .../docs/magic-transit/how-to/index.mdx       |    5 +-
 .../how-to/safely-withdraw-byoip-prefix.mdx   |    7 +-
 .../docs/magic-transit/network-flow.mdx       |    5 +-
 .../check-tunnel-health-dashboard.mdx         |   12 +-
 .../configure-tunnel-health-alerts.mdx        |    5 +-
 .../magic-transit/network-health/index.mdx    |   16 +-
 .../run-endpoint-health-checks.mdx            |   75 +-
 .../update-tunnel-health-checks-frequency.mdx |    7 +-
 .../magic-transit/network-interconnect.mdx    |    2 +-
 src/content/docs/magic-transit/on-demand.mdx  |    1 -
 .../docs/magic-transit/partners/index.mdx     |    5 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/gre-ipsec-tunnels.mdx           |    3 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/magic-transit/reference/index.mdx    |    5 +-
 .../docs/magic-transit/reference/mtu-mss.mdx  |    4 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    5 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../magic-transit/troubleshooting/index.mdx   |    2 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   12 +-
 .../troubleshooting/routing-and-bgp.mdx       |   21 +-
 .../troubleshooting/tunnel-health.mdx         |   29 +-
 src/content/docs/moq/feature-matrix.mdx       |  121 +-
 src/content/docs/moq/index.mdx                |   15 +-
 .../docs/multi-cloud-networking/changelog.mdx |    5 +-
 .../multi-cloud-networking/cloud-on-ramps.mdx |   11 +-
 .../multi-cloud-networking/get-started.mdx    |   74 +-
 .../manage-resources.mdx                      |    7 +-
 .../docs/multi-cloud-networking/reference.mdx |    1 -
 .../network-error-logging/get-started.mdx     |    3 +-
 .../docs/network-error-logging/how-to.mdx     |   11 +-
 .../docs/network-error-logging/index.mdx      |   45 +-
 src/content/docs/network-flow/api.mdx         |    5 +-
 src/content/docs/network-flow/changelog.mdx   |    5 +-
 .../docs/network-flow/cloud-flow-logs.mdx     |    2 +-
 src/content/docs/network-flow/faq.mdx         |    4 +-
 src/content/docs/network-flow/get-started.mdx |    2 +-
 src/content/docs/network-flow/glossary.mdx    |    3 +-
 .../magic-transit-integration.mdx             |    5 +-
 .../docs/network-flow/network-flow-free.mdx   |    2 +-
 .../docs/network-flow/routers/index.mdx       |    5 +-
 .../routers/netflow-ipfix-config.mdx          |    3 +-
 .../routers/recommended-sampling-rate.mdx     |    3 +-
 .../network-flow/routers/sflow-config.mdx     |    5 +-
 .../routers/supported-routers.mdx             |    5 +-
 src/content/docs/network-flow/rules/index.mdx |    1 -
 .../network-flow/rules/rule-notifications.mdx |    2 +-
 .../network-flow/rules/s-flow-ddos-attack.mdx |    2 +-
 .../network-flow/rules/static-threshold.mdx   |    2 +-
 .../tutorials/ddos-testing-guide.mdx          |    2 +-
 .../tutorials/encrypt-network-flow-data.mdx   |    5 +-
 .../tutorials/graphql-analytics.mdx           |    2 +-
 .../docs/network-flow/tutorials/index.mdx     |    5 +-
 .../docs/network-interconnect/changelog.mdx   |    5 +-
 .../docs/network-interconnect/get-started.mdx |   49 +-
 .../docs/network-interconnect/index.mdx       |   38 +-
 .../monitoring-and-alerts.mdx                 |   10 +-
 .../operational-guidance.mdx                  |    2 +-
 src/content/docs/network/index.mdx            |   36 +-
 src/content/docs/network/websockets.mdx       |    1 -
 .../get-started/configure-pagerduty.mdx       |   14 +-
 .../docs/notifications/get-started/index.mdx  |   27 +-
 src/content/docs/notifications/index.mdx      |    5 +-
 .../notifications/notification-available.mdx  |    2 +-
 .../notifications/notification-history.mdx    |    2 +-
 .../docs/notifications/reference/index.mdx    |    2 +-
 .../reference/traffic-alerts.mdx              |    2 +-
 src/content/docs/pages/configuration/api.mdx  |    1 +
 .../pages/configuration/build-caching.mdx     |   18 +-
 .../docs/pages/configuration/build-image.mdx  |    6 +-
 .../docs/pages/configuration/deploy-hooks.mdx |    1 +
 .../deploy-a-vite3-project.mdx                |    1 +
 .../docs/pages/functions/api-reference.mdx    |    8 -
 src/content/docs/pages/functions/bindings.mdx |   22 +-
 .../pages/functions/examples/ab-testing.mdx   |    1 -
 .../pages/functions/examples/cors-headers.mdx |    1 -
 .../docs/pages/functions/examples/index.mdx   |    1 -
 src/content/docs/pages/functions/metrics.mdx  |    1 +
 .../functions/plugins/community-plugins.mdx   |    1 -
 src/content/docs/pages/get-started/c3.mdx     |   23 -
 .../docs/pages/get-started/direct-upload.mdx  |    2 +-
 .../pages/get-started/git-integration.mdx     |    1 -
 src/content/docs/pages/get-started/index.mdx  |    1 -
 .../pages/how-to/add-custom-http-headers.mdx  |    1 -
 .../pages/how-to/build-commands-branches.mdx  |    2 +-
 .../pages/how-to/custom-branch-aliases.mdx    |    2 +-
 .../docs/pages/how-to/enable-zaraz.mdx        |    1 -
 src/content/docs/pages/how-to/index.mdx       |    2 -
 .../pages/how-to/npm-private-registry.mdx     |    1 -
 .../how-to/preview-with-cloudflare-tunnel.mdx |    1 -
 .../refactor-a-worker-to-pages-functions.mdx  |    1 -
 ...ect-upload-with-continuous-integration.mdx |    4 +-
 .../use-worker-for-ab-testing-in-pages.mdx    |    2 +-
 .../docs/pages/how-to/web-analytics.mdx       |    2 +-
 src/content/docs/pages/migrations/index.mdx   |    2 -
 src/content/docs/pages/platform/index.mdx     |    1 -
 .../docs/pages/platform/known-issues.mdx      |    3 +-
 src/content/docs/pages/platform/limits.mdx    |    7 +-
 .../add-a-react-form-with-formspree.mdx       |    2 +-
 .../build-a-blog-using-nuxt-and-sanity.mdx    |    1 +
 .../pipelines/reference/wrangler-commands.mdx |    3 +-
 .../docs/pipelines/sinks/manage-sinks.mdx     |    2 +-
 .../sql-reference/scalar-functions/string.mdx |    1 -
 .../docs/privacy-gateway/get-started.mdx      |   32 +-
 .../docs/privacy-gateway/reference/index.mdx  |    2 +-
 .../docs/privacy-gateway/reference/legal.mdx  |    4 +-
 .../privacy-gateway/reference/metrics.mdx     |  132 +-
 .../reference/product-compatibility.mdx       |    6 +-
 .../privacy-proxy/concepts/authentication.mdx |   12 +-
 .../concepts/deployment-models.mdx            |   26 +-
 .../privacy-proxy/concepts/geolocation.mdx    |   12 +-
 .../privacy-proxy/concepts/how-it-works.mdx   |   17 +-
 .../docs/privacy-proxy/get-started.mdx        |    2 +-
 .../privacy-proxy/reference/http-headers.mdx  |   32 +-
 .../privacy-proxy/reference/proxy-status.mdx  |   52 +-
 src/content/docs/pulumi/tutorial/index.mdx    |    3 -
 .../queues/configuration/configure-queues.mdx |   82 +-
 .../configuration/consumer-concurrency.mdx    |    2 +-
 .../docs/queues/configuration/index.mdx       |    2 +-
 .../queues/configuration/javascript-apis.mdx  |  243 ++--
 .../configuration/local-development.mdx       |    7 +-
 .../docs/queues/configuration/pause-purge.mdx |    6 +
 .../docs/queues/event-subscriptions/index.mdx |    4 +-
 .../manage-event-subscriptions.mdx            |    8 +-
 .../examples/publish-to-a-queue-via-http.mdx  |    1 -
 .../publish-to-a-queue-via-workers.mdx        |    5 +-
 .../queues/examples/send-errors-to-r2.mdx     |   50 +-
 .../examples/send-messages-from-dash.mdx      |    6 +-
 .../use-queues-with-durable-objects.mdx       |   68 +-
 src/content/docs/queues/glossary.mdx          |    2 +-
 .../docs/queues/observability/index.mdx       |    2 +-
 .../docs/queues/observability/metrics.mdx     |    8 +-
 src/content/docs/queues/platform/index.mdx    |    2 +-
 src/content/docs/queues/platform/limits.mdx   |   57 +-
 src/content/docs/queues/platform/pricing.mdx  |    9 +-
 .../queues/reference/delivery-guarantees.mdx  |    6 +-
 .../docs/queues/reference/error-codes.mdx     |   52 +-
 .../queues/reference/how-queues-works.mdx     |  148 ++-
 src/content/docs/queues/reference/index.mdx   |    2 +-
 .../reference/limitations-best-practices.mdx  |   68 +-
 .../r2-sql/reference/wrangler-commands.mdx    |    2 +-
 .../docs/r2-sql/sql-reference/index.mdx       |   18 +-
 src/content/docs/r2/api/error-codes.mdx       |   88 +-
 src/content/docs/r2/api/index.mdx             |    2 +-
 src/content/docs/r2/api/s3/extensions.mdx     |   18 +-
 src/content/docs/r2/api/s3/presigned-urls.mdx |   11 +-
 .../docs/r2/api/s3/temporary-credentials.mdx  |   54 +-
 .../r2/api/workers/workers-api-reference.mdx  |   78 +-
 .../docs/r2/api/workers/workers-api-usage.mdx |    1 +
 src/content/docs/r2/buckets/bucket-locks.mdx  |    3 +
 src/content/docs/r2/buckets/cors.mdx          |   45 +-
 .../docs/r2/buckets/delete-buckets.mdx        |   26 +-
 .../docs/r2/buckets/event-notifications.mdx   |   33 +-
 src/content/docs/r2/buckets/index.mdx         |    2 +-
 .../docs/r2/buckets/object-lifecycles.mdx     |    2 +
 .../docs/r2/buckets/storage-classes.mdx       |   32 +-
 src/content/docs/r2/data-migration/index.mdx  |    2 +-
 .../data-migration/migration-strategies.mdx   |    2 +-
 src/content/docs/r2/data-migration/sippy.mdx  |   18 +-
 .../docs/r2/data-migration/super-slurper.mdx  |    7 +-
 .../examples/authenticate-r2-auth-tokens.mdx  |    2 +-
 .../authenticate-r2-temp-credentials.mdx      |  174 +--
 .../docs/r2/examples/aws/aws-sdk-js-v3.mdx    |   19 +-
 .../docs/r2/examples/aws/aws-sdk-js.mdx       |   25 +-
 .../docs/r2/examples/aws/aws-sdk-kotlin.mdx   |    1 -
 .../docs/r2/examples/aws/aws4fetch.mdx        |   15 +-
 src/content/docs/r2/examples/aws/boto3.mdx    |   15 +-
 .../docs/r2/examples/aws/custom-header.mdx    |   95 +-
 src/content/docs/r2/examples/cache-api.mdx    |  109 +-
 src/content/docs/r2/examples/terraform.mdx    |    7 +-
 src/content/docs/r2/get-started/cli.mdx       |    9 +-
 src/content/docs/r2/get-started/index.mdx     |    1 +
 src/content/docs/r2/get-started/s3.mdx        |    9 +-
 .../docs/r2/get-started/workers-api.mdx       |    2 +-
 .../docs/r2/objects/delete-objects.mdx        |   19 +-
 .../docs/r2/objects/download-objects.mdx      |    3 +-
 src/content/docs/r2/objects/index.mdx         |    4 +-
 src/content/docs/r2/platform/audit-logs.mdx   |   59 +-
 .../docs/r2/platform/metrics-analytics.mdx    |    7 +-
 .../docs/r2/platform/troubleshooting.mdx      |    5 +-
 src/content/docs/r2/pricing.mdx               |   52 +-
 src/content/docs/r2/r2-sql.mdx                |    2 +-
 .../docs/r2/reference/data-location.mdx       |    2 +
 .../docs/r2/reference/data-security.mdx       |    2 -
 src/content/docs/r2/reference/durability.mdx  |   10 +-
 .../r2/reference/unicode-interoperability.mdx |    6 +-
 .../docs/r2/tutorials/cloudflare-access.mdx   |    2 +-
 src/content/docs/r2/tutorials/mastodon.mdx    |    3 +-
 src/content/docs/r2/tutorials/postman.mdx     |   12 +-
 src/content/docs/r2/video-tutorials.mdx       |   10 +-
 src/content/docs/radar/concepts/index.mdx     |    2 +-
 .../docs/radar/concepts/normalization.mdx     |    2 +-
 .../radar/get-started/configure-alerts.mdx    |    2 +-
 src/content/docs/radar/get-started/embed.mdx  |    4 +-
 src/content/docs/radar/get-started/index.mdx  |    2 +-
 .../radar/get-started/making-comparisons.mdx  |   78 +-
 .../investigate/application-layer-attacks.mdx |   84 +-
 src/content/docs/radar/investigate/dns.mdx    |   26 +-
 .../investigate/domain-ranking-datasets.mdx   |   37 +-
 .../docs/radar/investigate/http-requests.mdx  |   76 +-
 src/content/docs/radar/investigate/index.mdx  |    2 +-
 .../docs/radar/investigate/netflows.mdx       |   18 +-
 .../investigate/network-layer-attacks.mdx     |   86 +-
 .../docs/radar/investigate/outages.mdx        |   14 +-
 .../docs/radar/investigate/url-scanner.mdx    |   88 +-
 src/content/docs/radar/mcp-server.mdx         |    2 +-
 src/content/docs/radar/reference/index.mdx    |    2 +-
 .../reference/quarterly-ddos-reports.mdx      |    6 +-
 .../randomness-beacon/about/background.mdx    |    2 +-
 .../docs/randomness-beacon/about/future.mdx   |    6 +-
 .../cryptographic-background/index.mdx        |    6 +-
 .../randomness-generation.mdx                 |    6 +-
 .../cryptographic-background/setup-phase.mdx  |    4 +-
 src/content/docs/realtime/agents/index.mdx    |    4 +-
 .../docs/realtime/realtimekit/ai/index.mdx    |    2 +-
 .../docs/realtime/realtimekit/ai/summary.mdx  |   69 +-
 .../realtime/realtimekit/ai/transcription.mdx |    2 +-
 .../realtimekit/core/api-reference/RTKAi.md   |   40 +-
 .../realtimekit/core/api-reference/RTKChat.md |  329 ++---
 .../api-reference/RTKConnectedMeetings.md     |   81 +-
 .../core/api-reference/RTKLivestream.md       |   46 +-
 .../realtimekit/core/api-reference/RTKMeta.md |   68 +-
 .../core/api-reference/RTKParticipant.md      |  188 +--
 .../core/api-reference/RTKParticipantMap.md   |   56 +-
 .../core/api-reference/RTKParticipants.md     |  240 ++--
 .../api-reference/RTKPermissionsPreset.md     |  143 ++-
 .../realtimekit/core/api-reference/RTKPip.md  |   72 +-
 .../core/api-reference/RTKPlugin.md           |  122 +-
 .../core/api-reference/RTKPlugins.md          |   21 +-
 .../core/api-reference/RTKPolls.md            |   33 +-
 .../core/api-reference/RTKRecording.md        |   20 +-
 .../realtimekit/core/api-reference/RTKSelf.md |  109 +-
 .../core/api-reference/RTKSelfMedia.md        |   77 +-
 .../core/api-reference/RTKStage.md            |   63 +-
 .../core/api-reference/RTKStore.md            |  167 +--
 .../core/api-reference/RTKThemePreset.md      |   89 +-
 .../core/api-reference/RealtimeKitClient.md   |  129 +-
 .../realtime/realtimekit/legal/3rdparty.mdx   |   99 +-
 .../recording-guide/add-watermark.mdx         |   20 +-
 .../recording-guide/configure-codecs.mdx      |    6 +-
 .../realtimekit/recording-guide/index.mdx     |    4 +-
 .../recording-guide/monitor-status.mdx        |   12 +-
 .../ui-kit/api-reference/angular/index.mdx    |    2 +-
 .../api-reference/angular/rtk-ai-toggle.mdx   |   24 +-
 .../angular/rtk-ai-transcriptions.mdx         |   16 +-
 .../ui-kit/api-reference/angular/rtk-ai.mdx   |   26 +-
 .../api-reference/angular/rtk-audio-grid.mdx  |   27 +-
 .../api-reference/angular/rtk-audio-tile.mdx  |   27 +-
 .../angular/rtk-audio-visualizer.mdx          |   29 +-
 .../api-reference/angular/rtk-avatar.mdx      |   22 +-
 .../angular/rtk-breakout-room-manager.mdx     |   33 +-
 .../rtk-breakout-room-participants.mdx        |   25 +-
 .../angular/rtk-breakout-rooms-manager.mdx    |   18 +-
 .../angular/rtk-breakout-rooms-toggle.mdx     |   27 +-
 .../angular/rtk-broadcast-message-modal.mdx   |   18 +-
 .../api-reference/angular/rtk-button.mdx      |   23 +-
 .../angular/rtk-camera-selector.mdx           |   40 +-
 .../angular/rtk-camera-toggle.mdx             |   21 +-
 .../angular/rtk-caption-toggle.mdx            |   25 +-
 .../angular/rtk-chat-composer-ui.mdx          |   25 +-
 .../angular/rtk-chat-composer-view.mdx        |   35 +-
 .../api-reference/angular/rtk-chat-header.mdx |    4 +-
 .../angular/rtk-chat-message.mdx              |   45 +-
 .../rtk-chat-messages-ui-paginated.mdx        |   23 +-
 .../angular/rtk-chat-messages-ui.mdx          |   27 +-
 .../angular/rtk-chat-search-results.mdx       |   23 +-
 .../angular/rtk-chat-selector-ui.mdx          |   25 +-
 .../angular/rtk-chat-selector.mdx             |   25 +-
 .../api-reference/angular/rtk-chat-toggle.mdx |   37 +-
 .../ui-kit/api-reference/angular/rtk-chat.mdx |   23 +-
 .../api-reference/angular/rtk-clock.mdx       |   17 +-
 .../angular/rtk-confirmation-modal.mdx        |   18 +-
 .../angular/rtk-controlbar-button.mdx         |   29 +-
 .../api-reference/angular/rtk-controlbar.mdx  |   27 +-
 .../api-reference/angular/rtk-counter.mdx     |   22 +-
 .../angular/rtk-debugger-audio.mdx            |   21 +-
 .../angular/rtk-debugger-screenshare.mdx      |   20 +-
 .../angular/rtk-debugger-system.mdx           |   21 +-
 .../angular/rtk-debugger-toggle.mdx           |   23 +-
 .../angular/rtk-debugger-video.mdx            |   21 +-
 .../api-reference/angular/rtk-debugger.mdx    |   21 +-
 .../angular/rtk-dialog-manager.mdx            |   36 +-
 .../api-reference/angular/rtk-dialog.mdx      |   31 +-
 .../angular/rtk-emoji-picker-button.mdx       |   16 +-
 .../angular/rtk-emoji-picker.mdx              |   16 +-
 .../angular/rtk-ended-screen.mdx              |   23 +-
 .../angular/rtk-file-dropzone.mdx             |   16 +-
 .../angular/rtk-file-message-view.mdx         |   19 +-
 .../angular/rtk-file-message.mdx              |   25 +-
 .../angular/rtk-file-picker-button.mdx        |   23 +-
 .../angular/rtk-fullscreen-toggle.mdx         |   25 +-
 .../angular/rtk-grid-pagination.mdx           |   27 +-
 .../ui-kit/api-reference/angular/rtk-grid.mdx |   34 +-
 .../api-reference/angular/rtk-header.mdx      |   28 +-
 .../ui-kit/api-reference/angular/rtk-icon.mdx |   18 +-
 .../api-reference/angular/rtk-idle-screen.mdx |   20 +-
 .../angular/rtk-image-message-view.mdx        |   16 +-
 .../angular/rtk-image-message.mdx             |   25 +-
 .../angular/rtk-image-viewer.mdx              |   19 +-
 .../angular/rtk-information-tooltip.mdx       |   11 +-
 .../api-reference/angular/rtk-join-stage.mdx  |   25 +-
 .../angular/rtk-leave-button.mdx              |   19 +-
 .../angular/rtk-leave-meeting.mdx             |   20 +-
 .../angular/rtk-livestream-indicator.mdx      |   18 +-
 .../angular/rtk-livestream-player.mdx         |   19 +-
 .../angular/rtk-livestream-toggle.mdx         |   21 +-
 .../ui-kit/api-reference/angular/rtk-logo.mdx |   19 +-
 .../angular/rtk-markdown-view.mdx             |   15 +-
 .../angular/rtk-meeting-title.mdx             |   16 +-
 .../api-reference/angular/rtk-meeting.mdx     |   43 +-
 .../api-reference/angular/rtk-menu-item.mdx   |   18 +-
 .../api-reference/angular/rtk-menu-list.mdx   |   16 +-
 .../ui-kit/api-reference/angular/rtk-menu.mdx |   22 +-
 .../angular/rtk-message-list-view.mdx         |   25 +-
 .../angular/rtk-message-view.mdx              |   39 +-
 .../api-reference/angular/rtk-mic-toggle.mdx  |   21 +-
 .../angular/rtk-microphone-selector.mdx       |   40 +-
 .../api-reference/angular/rtk-mixed-grid.mdx  |   40 +-
 .../api-reference/angular/rtk-more-toggle.mdx |   29 +-
 .../angular/rtk-mute-all-button.mdx           |   21 +-
 .../angular/rtk-mute-all-confirmation.mdx     |   18 +-
 .../api-reference/angular/rtk-name-tag.mdx    |   27 +-
 .../angular/rtk-network-indicator.mdx         |   23 +-
 .../angular/rtk-notification.mdx              |   25 +-
 .../angular/rtk-notifications.mdx             |   27 +-
 .../angular/rtk-overlay-modal.mdx             |   18 +-
 .../angular/rtk-paginated-list.mdx            |   33 +-
 .../angular/rtk-participant-count.mdx         |   19 +-
 .../angular/rtk-participant-setup.mdx         |   31 +-
 .../angular/rtk-participant-tile.mdx          |   37 +-
 .../api-reference/angular/rtk-participant.mdx |   31 +-
 .../angular/rtk-participants-audio.mdx        |   19 +-
 .../angular/rtk-participants-stage-list.mdx   |   33 +-
 .../angular/rtk-participants-stage-queue.mdx  |   25 +-
 .../angular/rtk-participants-toggle.mdx       |   35 +-
 .../angular/rtk-participants-viewer-list.mdx  |   29 +-
 .../angular/rtk-participants-waiting-list.mdx |   25 +-
 .../angular/rtk-participants.mdx              |   29 +-
 .../angular/rtk-permissions-message.mdx       |   20 +-
 .../angular/rtk-pinned-message-selector.mdx   |   16 +-
 .../api-reference/angular/rtk-pip-toggle.mdx  |   25 +-
 .../api-reference/angular/rtk-plugin-main.mdx |   19 +-
 .../angular/rtk-plugins-toggle.mdx            |   35 +-
 .../api-reference/angular/rtk-plugins.mdx     |   23 +-
 .../api-reference/angular/rtk-poll-form.mdx   |   15 +-
 .../ui-kit/api-reference/angular/rtk-poll.mdx |   23 +-
 .../angular/rtk-polls-toggle.mdx              |   37 +-
 .../api-reference/angular/rtk-polls.mdx       |   23 +-
 .../angular/rtk-recording-indicator.mdx       |   20 +-
 .../angular/rtk-recording-toggle.mdx          |   29 +-
 .../angular/rtk-screen-share-toggle.mdx       |   23 +-
 .../angular/rtk-screenshare-view.mdx          |   35 +-
 .../angular/rtk-settings-audio.mdx            |   38 +-
 .../angular/rtk-settings-toggle.mdx           |   32 +-
 .../angular/rtk-settings-video.mdx            |   38 +-
 .../api-reference/angular/rtk-settings.mdx    |   23 +-
 .../angular/rtk-setup-screen.mdx              |   25 +-
 .../api-reference/angular/rtk-sidebar-ui.mdx  |   29 +-
 .../api-reference/angular/rtk-sidebar.mdx     |   33 +-
 .../api-reference/angular/rtk-simple-grid.mdx |   29 +-
 .../angular/rtk-speaker-selector.mdx          |   42 +-
 .../api-reference/angular/rtk-spinner.mdx     |   14 +-
 .../angular/rtk-spotlight-grid.mdx            |   42 +-
 .../angular/rtk-spotlight-indicator.mdx       |   18 +-
 .../angular/rtk-stage-toggle.mdx              |   23 +-
 .../api-reference/angular/rtk-stage.mdx       |   17 +-
 .../api-reference/angular/rtk-switch.mdx      |   22 +-
 .../api-reference/angular/rtk-tab-bar.mdx     |   29 +-
 .../angular/rtk-text-composer-view.mdx        |   31 +-
 .../angular/rtk-text-message-view.mdx         |   14 +-
 .../angular/rtk-text-message.mdx              |   25 +-
 .../api-reference/angular/rtk-tooltip.mdx     |   28 +-
 .../api-reference/angular/rtk-transcript.mdx  |   19 +-
 .../api-reference/angular/rtk-transcripts.mdx |   22 +-
 .../api-reference/angular/rtk-ui-provider.mdx |   27 +-
 .../angular/rtk-viewer-count.mdx              |   19 +-
 .../rtk-virtualized-participant-list.mdx      |   23 +-
 .../angular/rtk-waiting-screen.mdx            |   18 +-
 .../ui-kit/api-reference/core/index.mdx       |    2 +-
 .../core/rtk-ai-transcriptions.mdx            |   21 +-
 .../ui-kit/api-reference/core/rtk-ai.mdx      |   28 +-
 .../api-reference/core/rtk-audio-grid.mdx     |   31 +-
 .../api-reference/core/rtk-audio-tile.mdx     |   31 +-
 .../core/rtk-audio-visualizer.mdx             |   33 +-
 .../ui-kit/api-reference/core/rtk-avatar.mdx  |   26 +-
 .../core/rtk-breakout-room-manager.mdx        |   37 +-
 .../core/rtk-breakout-room-participants.mdx   |   31 +-
 .../core/rtk-breakout-rooms-manager.mdx       |   21 +-
 .../core/rtk-breakout-rooms-toggle.mdx        |   30 +-
 .../core/rtk-broadcast-message-modal.mdx      |   21 +-
 .../ui-kit/api-reference/core/rtk-button.mdx  |   27 +-
 .../core/rtk-camera-selector.mdx              |   41 +-
 .../core/rtk-chat-composer-ui.mdx             |   28 +-
 .../core/rtk-chat-composer-view.mdx           |   37 +-
 .../api-reference/core/rtk-chat-header.mdx    |    4 +-
 .../api-reference/core/rtk-chat-message.mdx   |   51 +-
 .../core/rtk-chat-messages-ui-paginated.mdx   |   24 +-
 .../core/rtk-chat-messages-ui.mdx             |   30 +-
 .../core/rtk-chat-search-results.mdx          |   24 +-
 .../core/rtk-chat-selector-ui.mdx             |   26 +-
 .../api-reference/core/rtk-chat-selector.mdx  |   28 +-
 .../ui-kit/api-reference/core/rtk-chat.mdx    |   26 +-
 .../ui-kit/api-reference/core/rtk-clock.mdx   |   20 +-
 .../core/rtk-confirmation-modal.mdx           |   21 +-
 .../core/rtk-controlbar-button.mdx            |   34 +-
 .../api-reference/core/rtk-controlbar.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-counter.mdx |   26 +-
 .../api-reference/core/rtk-debugger-audio.mdx |   24 +-
 .../core/rtk-debugger-screenshare.mdx         |   24 +-
 .../core/rtk-debugger-system.mdx              |   24 +-
 .../api-reference/core/rtk-debugger-video.mdx |   24 +-
 .../api-reference/core/rtk-debugger.mdx       |   24 +-
 .../api-reference/core/rtk-dialog-manager.mdx |   39 +-
 .../ui-kit/api-reference/core/rtk-dialog.mdx  |   35 +-
 .../core/rtk-draft-attachment-view.mdx        |   19 +-
 .../core/rtk-emoji-picker-button.mdx          |   19 +-
 .../api-reference/core/rtk-emoji-picker.mdx   |   19 +-
 .../api-reference/core/rtk-ended-screen.mdx   |   26 +-
 .../api-reference/core/rtk-file-dropzone.mdx  |   18 +-
 .../core/rtk-file-message-view.mdx            |   23 +-
 .../api-reference/core/rtk-file-message.mdx   |   27 +-
 .../core/rtk-file-picker-button.mdx           |   24 +-
 .../core/rtk-grid-pagination.mdx              |   28 +-
 .../ui-kit/api-reference/core/rtk-grid.mdx    |   37 +-
 .../ui-kit/api-reference/core/rtk-header.mdx  |   32 +-
 .../ui-kit/api-reference/core/rtk-icon.mdx    |   21 +-
 .../api-reference/core/rtk-idle-screen.mdx    |   23 +-
 .../core/rtk-image-message-view.mdx           |   19 +-
 .../api-reference/core/rtk-image-message.mdx  |   27 +-
 .../api-reference/core/rtk-image-viewer.mdx   |   21 +-
 .../core/rtk-information-tooltip.mdx          |   15 +-
 .../api-reference/core/rtk-join-stage.mdx     |   28 +-
 .../api-reference/core/rtk-leave-meeting.mdx  |   23 +-
 .../core/rtk-livestream-indicator.mdx         |   22 +-
 .../core/rtk-livestream-player.mdx            |   22 +-
 .../ui-kit/api-reference/core/rtk-logo.mdx    |   22 +-
 .../api-reference/core/rtk-markdown-view.mdx  |   18 +-
 .../api-reference/core/rtk-meeting-title.mdx  |   19 +-
 .../ui-kit/api-reference/core/rtk-meeting.mdx |   45 +-
 .../api-reference/core/rtk-menu-item.mdx      |   21 +-
 .../api-reference/core/rtk-menu-list.mdx      |   18 +-
 .../ui-kit/api-reference/core/rtk-menu.mdx    |   24 +-
 .../core/rtk-message-list-view.mdx            |   27 +-
 .../api-reference/core/rtk-message-view.mdx   |   43 +-
 .../core/rtk-microphone-selector.mdx          |   41 +-
 .../api-reference/core/rtk-mixed-grid.mdx     |   43 +-
 .../api-reference/core/rtk-more-toggle.mdx    |   32 +-
 .../core/rtk-mute-all-confirmation.mdx        |   21 +-
 .../api-reference/core/rtk-name-tag.mdx       |   31 +-
 .../core/rtk-network-indicator.mdx            |   27 +-
 .../api-reference/core/rtk-notification.mdx   |   28 +-
 .../api-reference/core/rtk-notifications.mdx  |   30 +-
 .../api-reference/core/rtk-overlay-modal.mdx  |   21 +-
 .../api-reference/core/rtk-paginated-list.mdx |   36 +-
 .../core/rtk-participant-count.mdx            |   22 +-
 .../core/rtk-participant-setup.mdx            |   33 +-
 .../core/rtk-participant-tile.mdx             |   37 +-
 .../api-reference/core/rtk-participant.mdx    |   33 +-
 .../core/rtk-participants-audio.mdx           |   21 +-
 .../core/rtk-participants-stage-list.mdx      |   36 +-
 .../core/rtk-participants-stage-queue.mdx     |   26 +-
 .../core/rtk-participants-viewer-list.mdx     |   32 +-
 .../core/rtk-participants-waiting-list.mdx    |   26 +-
 .../api-reference/core/rtk-participants.mdx   |   30 +-
 .../core/rtk-permissions-message.mdx          |   23 +-
 .../core/rtk-pinned-message-selector.mdx      |   19 +-
 .../api-reference/core/rtk-plugin-main.mdx    |   21 +-
 .../ui-kit/api-reference/core/rtk-plugins.mdx |   26 +-
 .../api-reference/core/rtk-poll-form.mdx      |   17 +-
 .../ui-kit/api-reference/core/rtk-poll.mdx    |   25 +-
 .../ui-kit/api-reference/core/rtk-polls.mdx   |   26 +-
 .../core/rtk-recording-indicator.mdx          |   24 +-
 .../core/rtk-recording-toggle.mdx             |   34 +-
 .../core/rtk-screenshare-view.mdx             |   35 +-
 .../api-reference/core/rtk-settings-audio.mdx |   41 +-
 .../api-reference/core/rtk-settings-video.mdx |   41 +-
 .../api-reference/core/rtk-settings.mdx       |   26 +-
 .../api-reference/core/rtk-setup-screen.mdx   |   28 +-
 .../api-reference/core/rtk-sidebar-ui.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-sidebar.mdx |   35 +-
 .../api-reference/core/rtk-simple-grid.mdx    |   34 +-
 .../core/rtk-speaker-selector.mdx             |   43 +-
 .../ui-kit/api-reference/core/rtk-spinner.mdx |   17 +-
 .../api-reference/core/rtk-spotlight-grid.mdx |   46 +-
 .../core/rtk-spotlight-indicator.mdx          |   22 +-
 .../ui-kit/api-reference/core/rtk-stage.mdx   |   19 +-
 .../ui-kit/api-reference/core/rtk-switch.mdx  |   27 +-
 .../ui-kit/api-reference/core/rtk-tab-bar.mdx |   31 +-
 .../core/rtk-text-composer-view.mdx           |   33 +-
 .../core/rtk-text-message-view.mdx            |   18 +-
 .../api-reference/core/rtk-text-message.mdx   |   27 +-
 .../ui-kit/api-reference/core/rtk-tooltip.mdx |   31 +-
 .../api-reference/core/rtk-transcript.mdx     |   22 +-
 .../api-reference/core/rtk-transcripts.mdx    |   25 +-
 .../api-reference/core/rtk-ui-provider.mdx    |   31 +-
 .../api-reference/core/rtk-viewer-count.mdx   |   22 +-
 .../core/rtk-virtualized-participant-list.mdx |   25 +-
 .../api-reference/core/rtk-waiting-screen.mdx |   21 +-
 .../react-native/RtkMenuItem.mdx              |   10 +-
 .../ui-kit/api-reference/react/RtkAi.mdx      |   34 +-
 .../api-reference/react/RtkAiToggle.mdx       |   32 +-
 .../react/RtkAiTranscriptions.mdx             |   25 +-
 .../api-reference/react/RtkAudioGrid.mdx      |   36 +-
 .../api-reference/react/RtkAudioTile.mdx      |   40 +-
 .../react/RtkAudioVisualizer.mdx              |   42 +-
 .../ui-kit/api-reference/react/RtkAvatar.mdx  |   30 +-
 .../react/RtkBreakoutRoomManager.mdx          |   46 +-
 .../react/RtkBreakoutRoomParticipants.mdx     |   38 +-
 .../react/RtkBreakoutRoomsManager.mdx         |   26 +-
 .../react/RtkBreakoutRoomsToggle.mdx          |   40 +-
 .../react/RtkBroadcastMessageModal.mdx        |   26 +-
 .../ui-kit/api-reference/react/RtkButton.mdx  |   32 +-
 .../api-reference/react/RtkCameraSelector.mdx |   53 +-
 .../api-reference/react/RtkCameraToggle.mdx   |   30 +-
 .../api-reference/react/RtkCaptionToggle.mdx  |   34 +-
 .../ui-kit/api-reference/react/RtkChat.mdx    |   31 +-
 .../api-reference/react/RtkChatComposerUi.mdx |   38 +-
 .../react/RtkChatComposerView.mdx             |   48 +-
 .../api-reference/react/RtkChatHeader.mdx     |    8 +-
 .../api-reference/react/RtkChatMessage.mdx    |   54 +-
 .../api-reference/react/RtkChatMessagesUi.mdx |   40 +-
 .../react/RtkChatMessagesUiPaginated.mdx      |   36 +-
 .../react/RtkChatSearchResults.mdx            |   36 +-
 .../api-reference/react/RtkChatSelector.mdx   |   33 +-
 .../api-reference/react/RtkChatSelectorUi.mdx |   38 +-
 .../api-reference/react/RtkChatToggle.mdx     |   46 +-
 .../ui-kit/api-reference/react/RtkClock.mdx   |   25 +-
 .../react/RtkConfirmationModal.mdx            |   26 +-
 .../api-reference/react/RtkControlbar.mdx     |   36 +-
 .../react/RtkControlbarButton.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkCounter.mdx |   30 +-
 .../api-reference/react/RtkDebugger.mdx       |   29 +-
 .../api-reference/react/RtkDebuggerAudio.mdx  |   29 +-
 .../react/RtkDebuggerScreenshare.mdx          |   29 +-
 .../api-reference/react/RtkDebuggerSystem.mdx |   29 +-
 .../api-reference/react/RtkDebuggerToggle.mdx |   32 +-
 .../api-reference/react/RtkDebuggerVideo.mdx  |   29 +-
 .../ui-kit/api-reference/react/RtkDialog.mdx  |   44 +-
 .../api-reference/react/RtkDialogManager.mdx  |   44 +-
 .../react/RtkDraftAttachmentView.mdx          |   24 +-
 .../api-reference/react/RtkEmojiPicker.mdx    |   24 +-
 .../react/RtkEmojiPickerButton.mdx            |   24 +-
 .../api-reference/react/RtkEndedScreen.mdx    |   31 +-
 .../api-reference/react/RtkFileDropzone.mdx   |   24 +-
 .../api-reference/react/RtkFileMessage.mdx    |   34 +-
 .../react/RtkFileMessageView.mdx              |   28 +-
 .../react/RtkFilePickerButton.mdx             |   36 +-
 .../react/RtkFullscreenToggle.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkGrid.mdx    |   42 +-
 .../api-reference/react/RtkGridPagination.mdx |   40 +-
 .../ui-kit/api-reference/react/RtkHeader.mdx  |   36 +-
 .../ui-kit/api-reference/react/RtkIcon.mdx    |   26 +-
 .../api-reference/react/RtkIdleScreen.mdx     |   28 +-
 .../api-reference/react/RtkImageMessage.mdx   |   36 +-
 .../react/RtkImageMessageView.mdx             |   24 +-
 .../api-reference/react/RtkImageViewer.mdx    |   27 +-
 .../react/RtkInformationTooltip.mdx           |   20 +-
 .../api-reference/react/RtkJoinStage.mdx      |   36 +-
 .../api-reference/react/RtkLeaveButton.mdx    |   27 +-
 .../api-reference/react/RtkLeaveMeeting.mdx   |   28 +-
 .../react/RtkLivestreamIndicator.mdx          |   27 +-
 .../react/RtkLivestreamPlayer.mdx             |   27 +-
 .../react/RtkLivestreamToggle.mdx             |   30 +-
 .../ui-kit/api-reference/react/RtkLogo.mdx    |   27 +-
 .../api-reference/react/RtkMarkdownView.mdx   |   23 +-
 .../ui-kit/api-reference/react/RtkMeeting.mdx |   56 +-
 .../api-reference/react/RtkMeetingTitle.mdx   |   24 +-
 .../ui-kit/api-reference/react/RtkMenu.mdx    |   30 +-
 .../api-reference/react/RtkMenuItem.mdx       |   27 +-
 .../api-reference/react/RtkMenuList.mdx       |   24 +-
 .../api-reference/react/RtkMessageView.mdx    |   50 +-
 .../api-reference/react/RtkMicToggle.mdx      |   30 +-
 .../react/RtkMicrophoneSelector.mdx           |   53 +-
 .../api-reference/react/RtkMixedGrid.mdx      |   48 +-
 .../api-reference/react/RtkMoreToggle.mdx     |   37 +-
 .../api-reference/react/RtkMuteAllButton.mdx  |   30 +-
 .../react/RtkMuteAllConfirmation.mdx          |   26 +-
 .../ui-kit/api-reference/react/RtkNameTag.mdx |   40 +-
 .../react/RtkNetworkIndicator.mdx             |   36 +-
 .../api-reference/react/RtkNotification.mdx   |   36 +-
 .../api-reference/react/RtkNotifications.mdx  |   35 +-
 .../api-reference/react/RtkOverlayModal.mdx   |   26 +-
 .../api-reference/react/RtkPaginatedList.mdx  |   46 +-
 .../api-reference/react/RtkParticipant.mdx    |   44 +-
 .../react/RtkParticipantCount.mdx             |   27 +-
 .../api-reference/react/RtkParticipants.mdx   |   42 +-
 .../react/RtkParticipantsAudio.mdx            |   32 +-
 .../react/RtkParticipantsStageList.mdx        |   46 +-
 .../react/RtkParticipantsStageQueue.mdx       |   38 +-
 .../react/RtkParticipantsToggle.mdx           |   44 +-
 .../react/RtkParticipantsViewerList.mdx       |   42 +-
 .../react/RtkParticipantsWaitingList.mdx      |   38 +-
 .../react/RtkPermissionsMessage.mdx           |   28 +-
 .../react/RtkPinnedMessageSelector.mdx        |   24 +-
 .../api-reference/react/RtkPipToggle.mdx      |   34 +-
 .../api-reference/react/RtkPluginMain.mdx     |   27 +-
 .../ui-kit/api-reference/react/RtkPlugins.mdx |   31 +-
 .../api-reference/react/RtkPluginsToggle.mdx  |   44 +-
 .../ui-kit/api-reference/react/RtkPoll.mdx    |   34 +-
 .../api-reference/react/RtkPollForm.mdx       |   23 +-
 .../ui-kit/api-reference/react/RtkPolls.mdx   |   31 +-
 .../api-reference/react/RtkPollsToggle.mdx    |   46 +-
 .../react/RtkRecordingIndicator.mdx           |   29 +-
 .../react/RtkRecordingToggle.mdx              |   38 +-
 .../react/RtkScreenShareToggle.mdx            |   32 +-
 .../api-reference/react/RtkSettings.mdx       |   31 +-
 .../api-reference/react/RtkSettingsAudio.mdx  |   46 +-
 .../api-reference/react/RtkSettingsToggle.mdx |   40 +-
 .../api-reference/react/RtkSettingsVideo.mdx  |   46 +-
 .../api-reference/react/RtkSetupScreen.mdx    |   33 +-
 .../ui-kit/api-reference/react/RtkSidebar.mdx |   46 +-
 .../api-reference/react/RtkSidebarUi.mdx      |   42 +-
 .../api-reference/react/RtkSimpleGrid.mdx     |   38 +-
 .../react/RtkSpeakerSelector.mdx              |   55 +-
 .../ui-kit/api-reference/react/RtkSpinner.mdx |   22 +-
 .../api-reference/react/RtkSpotlightGrid.mdx  |   51 +-
 .../react/RtkSpotlightIndicator.mdx           |   27 +-
 .../ui-kit/api-reference/react/RtkStage.mdx   |   25 +-
 .../api-reference/react/RtkStageToggle.mdx    |   32 +-
 .../ui-kit/api-reference/react/RtkSwitch.mdx  |   30 +-
 .../ui-kit/api-reference/react/RtkTabBar.mdx  |   38 +-
 .../api-reference/react/RtkTextMessage.mdx    |   34 +-
 .../react/RtkTextMessageView.mdx              |   23 +-
 .../ui-kit/api-reference/react/RtkTooltip.mdx |   36 +-
 .../api-reference/react/RtkTranscript.mdx     |   27 +-
 .../api-reference/react/RtkTranscripts.mdx    |   30 +-
 .../api-reference/react/RtkUiProvider.mdx     |   40 +-
 .../api-reference/react/RtkViewerCount.mdx    |   27 +-
 .../react/RtkVirtualizedParticipantList.mdx   |   36 +-
 .../api-reference/react/RtkWaitingScreen.mdx  |   26 +-
 .../ui-kit/api-reference/react/index.mdx      |    2 +-
 .../docs/realtime/sfu/calls-vs-sfus.mdx       |    7 +-
 src/content/docs/realtime/sfu/changelog.mdx   |    2 +-
 .../docs/realtime/sfu/datachannels.mdx        |    2 +-
 src/content/docs/realtime/sfu/get-started.mdx |    6 +-
 src/content/docs/realtime/sfu/limits.mdx      |   33 +-
 .../sfu/media-transport-adapters/index.mdx    |    1 +
 .../websocket-adapter.mdx                     |   25 +-
 .../docs/realtime/sfu/sessions-tracks.mdx     |   20 +-
 .../docs/realtime/turn/custom-domains.mdx     |   10 +-
 .../realtime/turn/generate-credentials.mdx    |   35 +-
 .../docs/realtime/turn/replacing-existing.mdx |   20 +-
 src/content/docs/realtime/turn/rfc-matrix.mdx |   30 +-
 .../architectures/sase.mdx                    |   18 +-
 .../architectures/security.mdx                |    2 +-
 .../designing-ztna-access-policies.mdx        |   18 +-
 ...nefits-to-saas-providers-end-customers.mdx |   16 +-
 .../diagrams/ai/index.mdx                     |    2 +-
 .../diagrams/content-delivery/index.mdx       |    2 +-
 ...uring-connected-transportation-systems.mdx |   17 +-
 .../diagrams/network/index.mdx                |    2 +-
 .../diagrams/sase/index.mdx                   |    2 +-
 .../diagrams/security/index.mdx               |    2 +-
 .../serverless/fullstack-application.mdx      |   27 +-
 .../diagrams/serverless/index.mdx             |    2 +-
 .../serverless/programmable-platforms.mdx     |    1 -
 .../diagrams/storage/index.mdx                |    2 +-
 .../implementation-guides/index.mdx           |    2 +-
 .../zero-trust/index.mdx                      |    2 +-
 .../domain-contact-updates.mdx                |   26 +-
 .../account-options/domain-management.mdx     |   18 +-
 .../account-options/icloud-domains.mdx        |   24 +-
 .../docs/registrar/account-options/index.mdx  |    2 +-
 .../inter-account-transfer.mdx                |   31 +-
 .../account-options/renew-domains.mdx         |   22 +-
 .../transfer-out-from-cloudflare.mdx          |   12 +-
 .../account-options/whois-redaction.mdx       |    4 +-
 .../registrar/custom-domain-protection.mdx    |    6 +-
 .../docs/registrar/get-started/index.mdx      |    2 +-
 .../registrar/get-started/register-domain.mdx |   15 +-
 .../top-level-domains/uk-domains.mdx          |   12 +-
 src/content/docs/registrar/whoisrequests.mdx  |    4 +-
 .../docs/resource-tagging/get-started.mdx     |   14 +-
 .../docs/resource-tagging/how-to/index.mdx    |    2 +-
 .../resource-tagging/how-to/manage-tags.mdx   |    6 +-
 .../reference/error-codes.mdx                 |   26 +-
 .../docs/resource-tagging/reference/index.mdx |    2 +-
 .../resource-tagging/reference/limits.mdx     |   37 +-
 .../reference/resource-types.mdx              |   80 +-
 .../docs/rules/normalization/settings.mdx     |    4 +-
 .../docs/rules/snippets/when-to-use.mdx       |    2 +-
 .../managed-transforms/reference.mdx          |    1 -
 .../docs/ruleset-engine/about/index.mdx       |    9 +-
 ...ink-override-ddos-l34-rule-sensitivity.mdx |    1 -
 .../ruleset-engine/rulesets-api/endpoints.mdx |  405 +++---
 src/content/docs/sandbox/bridge/http-api.mdx  |  148 +--
 .../docs/sandbox/concepts/containers.mdx      |   23 +-
 .../docs/sandbox/concepts/preview-urls.mdx    |    6 +-
 .../docs/sandbox/concepts/sandboxes.mdx       |    4 +-
 .../docs/sandbox/concepts/security.mdx        |   65 +-
 .../docs/sandbox/concepts/sessions.mdx        |   77 +-
 .../configuration/environment-variables.mdx   |   32 +-
 .../docs/sandbox/configuration/transport.mdx  |    5 +-
 .../sandbox/guides/production-deployment.mdx  |    9 +-
 src/content/docs/sandbox/platform/pricing.mdx |    2 +
 .../sandbox/tutorials/ai-code-executor.mdx    |   76 +-
 .../tutorials/analyze-data-with-ai.mdx        |   29 +-
 .../tutorials/automated-testing-pipeline.mdx  |  116 +-
 .../tutorials/claude-managed-agents.mdx       |   29 +-
 .../sandbox/tutorials/code-review-bot.mdx     |    4 +-
 src/content/docs/secrets-store/audit-logs.mdx |    2 +-
 src/content/docs/secrets-store/index.mdx      |    3 +-
 .../secrets-store/integrations/ai-gateway.mdx |    2 +-
 .../docs/secrets-store/integrations/index.mdx |    2 +-
 .../secrets-store/manage-secrets/how-to.mdx   |    2 +-
 .../secrets-store/manage-secrets/index.mdx    |    2 +-
 .../docs/security-center/brand-protection.mdx |    2 +-
 .../docs/security-center/changelog.mdx        |   10 +-
 .../cloudforce-one/cloudforce-one.mdx         |    1 -
 .../cloudforce-one/open-port-scanning.mdx     |  170 +--
 .../investigate/change-categorization.mdx     |    1 -
 .../security-center/investigate/index.mdx     |    1 -
 .../investigate/investigate-threats.mdx       |    5 +-
 .../investigate/scan-limits.mdx               |    4 -
 src/content/docs/security/overview.mdx        |   43 +-
 .../docs/smart-shield/concepts/index.mdx      |    2 +-
 .../smart-shield/concepts/network-diagram.mdx |    2 +-
 .../docs/smart-shield/configuration/argo.mdx  |    2 +-
 .../configuration/cache-reserve/analytics.mdx |    6 +-
 .../configuration/cache-reserve/index.mdx     |    2 +-
 .../cache-reserve/operations.mdx              |    5 +-
 .../how-it-works/connection-forwarding.mdx    |    6 +-
 .../how-it-works/index.mdx                    |    2 +-
 .../dedicated-egress-ips/index.mdx            |    8 +-
 .../dedicated-egress-ips/ips-utilization.mdx  |  202 +--
 .../dedicated-egress-ips/other-products.mdx   |    2 +-
 .../configuration/health-checks/analytics.mdx |    5 +-
 .../configuration/health-checks/index.mdx     |    2 +-
 .../configuration/health-checks/setup.mdx     |    4 +-
 .../health-checks/zone-lockdown.mdx           |    2 +-
 .../docs/smart-shield/configuration/index.mdx |    2 +-
 .../configuration/regional-tiered-cache.mdx   |    2 +-
 .../configuration/smart-tiered-cache.mdx      |    2 +-
 src/content/docs/spectrum/about/byoip.mdx     |   75 +-
 .../docs/spectrum/about/ddos-for-spectrum.mdx |    1 -
 src/content/docs/spectrum/about/ftp.mdx       |   16 +-
 src/content/docs/spectrum/about/index.mdx     |    3 +-
 src/content/docs/spectrum/about/static-ip.mdx |   46 +-
 src/content/docs/spectrum/glossary.mdx        |    3 +-
 .../spectrum/how-to/enable-proxy-protocol.mdx |    3 -
 src/content/docs/spectrum/how-to/index.mdx    |    3 +-
 .../docs/spectrum/protocols-per-plan.mdx      |    3 +-
 .../docs/spectrum/reference/analytics.mdx     |   46 +-
 src/content/docs/spectrum/reference/index.mdx |    3 +-
 .../spectrum/reference/layer-7-analytics.mdx  |    4 +-
 src/content/docs/spectrum/reference/logs.mdx  |    3 -
 .../spectrum/reference/settings-by-plan.mdx   |   14 +-
 src/content/docs/speed/aim.mdx                |   33 +-
 src/content/docs/speed/glossary.mdx           |    3 +-
 .../docs/speed/observatory/dashboard.mdx      |   11 +-
 .../docs/speed/observatory/rum-beacon.mdx     |   46 +-
 .../docs/speed/observatory/run-speed-test.mdx |   21 +-
 .../docs/speed/observatory/test-results.mdx   |   23 +-
 .../docs/speed/optimization/content/apo.mdx   |    1 -
 .../optimization/content/compression.mdx      |    6 +-
 .../optimization/content/early-hints.mdx      |    1 -
 .../content/fonts/troubleshooting.mdx         |    5 +-
 .../docs/speed/optimization/content/index.mdx |    3 +-
 .../rocket-loader/ignore-javascripts.mdx      |   10 +-
 .../content/shared-dictionaries.mdx           |    8 +-
 .../optimization/content/smart-hints.mdx      |    1 -
 .../optimization/content/speed-brain.mdx      |    9 +-
 .../content/troubleshooting/index.mdx         |    3 +-
 .../optimization/images/image-resizing.mdx    |    1 -
 .../docs/speed/optimization/images/index.mdx  |    3 +-
 .../docs/speed/optimization/images/polish.mdx |    1 -
 .../images/troubleshooting/index.mdx          |    3 +-
 .../multiple-optimizations.mdx                |    1 -
 .../images/troubleshooting/polish.mdx         |    1 -
 .../troubleshooting-missing-images.mdx        |    6 +-
 src/content/docs/speed/optimization/index.mdx |    3 +-
 .../docs/speed/optimization/measurement.mdx   |    1 -
 .../speed/optimization/protocol/http2.mdx     |    4 +-
 .../speed/optimization/protocol/index.mdx     |    3 +-
 ...hanced-http2-prioritization-ios-safari.mdx |    3 -
 .../protocol/troubleshooting/index.mdx        |    3 +-
 .../speed/optimization/recommendations.mdx    |    1 -
 src/content/docs/speed/smart-shield.mdx       |    3 +-
 src/content/docs/speed/troubleshooting.mdx    |   11 +-
 src/content/docs/ssl/changelog.mdx            |    4 +-
 .../forward-a-client-certificate.mdx          |    2 +-
 .../revoke-client-certificate.mdx             |    3 -
 src/content/docs/ssl/concepts.mdx             |    6 +-
 .../customize-cipher-suites/index.mdx         |    8 +-
 .../cipher-suites/supported-cipher-suites.mdx |   50 +-
 .../additional-options/index.mdx              |    3 +-
 .../additional-options/minimum-tls.mdx        |   22 +-
 .../additional-options/tls-13.mdx             |    9 +-
 .../api-commands.mdx                          |   14 +-
 .../manage-certificates.mdx                   |    8 +-
 .../edge-certificates/backup-certificates.mdx |    3 +-
 .../ssl/edge-certificates/caa-records.mdx     |    1 -
 .../bundling-methodologies.mdx                |    3 +-
 .../custom-certificates/renewing.mdx          |    3 +-
 .../docs/ssl/edge-certificates/ech.mdx        |    4 +-
 .../geokey-manager/supported-options.mdx      |    4 +-
 .../docs/ssl/edge-certificates/index.mdx      |    2 +-
 .../edge-certificates/staging-environment.mdx |   23 +-
 .../universal-ssl/alerts.mdx                  |    8 +-
 .../universal-ssl/disable-universal-ssl.mdx   |    2 -
 .../universal-ssl/troubleshooting.mdx         |    8 +-
 .../ssl/keyless-ssl/configuration/index.mdx   |    3 +-
 src/content/docs/ssl/keyless-ssl/glossary.mdx |    1 -
 .../azure-managed-hsm.mdx                     |    1 -
 .../fortanix-dsm.mdx                          |    2 +-
 .../hardware-security-modules/index.mdx       |    7 +-
 .../reference/high-availability.mdx           |    1 -
 .../docs/ssl/keyless-ssl/reference/index.mdx  |    3 +-
 .../reference/keyless-delegation.mdx          |    1 -
 .../ssl/keyless-ssl/reference/metrics.mdx     |  184 ++-
 .../reference/scaling-and-benchmarking.mdx    |    5 +-
 .../keyless-ssl/upgrading-your-key-server.mdx |    3 -
 .../set-up/global.mdx                         |    5 +-
 .../set-up/index.mdx                          |    5 +-
 .../origin-configuration/cipher-suites.mdx    |   28 +-
 .../docs/ssl/origin-configuration/index.mdx   |    3 +-
 .../origin-ca/troubleshooting.mdx             |    2 +-
 .../origin-configuration/ssl-modes/full.mdx   |    6 +-
 .../origin-configuration/ssl-modes/index.mdx  |    2 +-
 .../ssl-modes/ssl-only-origin-pull.mdx        |    7 +-
 .../docs/ssl/reference/all-features.mdx       |    5 +-
 .../ssl/reference/browser-compatibility.mdx   |    9 +-
 .../certificate-and-hostname-priority.mdx     |   17 +-
 .../ssl/reference/certificate-authorities.mdx |    2 +-
 .../ssl/reference/certificate-pinning.mdx     |    1 -
 .../cloudflare-and-cve-2019-1559.mdx          |    7 +-
 .../compliance-and-vulnerabilities.mdx        |   42 +-
 src/content/docs/ssl/reference/index.mdx      |    3 +-
 .../migration-guides/entrust-distrust.mdx     |   15 +-
 .../ssl/reference/migration-guides/index.mdx  |    3 +-
 src/content/docs/ssl/reference/protocols.mdx  |   18 +-
 src/content/docs/ssl/saas.mdx                 |    1 -
 .../troubleshooting/general-ssl-errors.mdx    |    2 +-
 .../docs/ssl/troubleshooting/index.mdx        |   10 +-
 .../troubleshooting/mixed-content-errors.mdx  |   19 +-
 .../version-cipher-mismatch.mdx               |    6 +-
 .../stream/edit-videos/adding-captions.mdx    |   91 +-
 .../edit-videos/player-enhancements.mdx       |   16 +-
 src/content/docs/stream/examples/dash-js.mdx  |    1 -
 src/content/docs/stream/examples/hls-js.mdx   |    5 +-
 src/content/docs/stream/examples/index.mdx    |    1 -
 .../examples/obs-from-scratch/index.mdx       |    1 -
 .../docs/stream/examples/rtmps_playback.mdx   |    3 +-
 .../docs/stream/examples/srt_playback.mdx     |    3 +-
 .../docs/stream/examples/stream-player.mdx    |   13 +-
 src/content/docs/stream/examples/video-js.mdx |    3 +-
 src/content/docs/stream/examples/vidstack.mdx |   15 +-
 .../fetching-bulk-analytics.mdx               |    1 +
 .../docs/stream/getting-analytics/index.mdx   |   11 +-
 .../getting-analytics/live-viewer-count.mdx   |    1 -
 .../stream/manage-video-library/index.mdx     |    1 -
 .../stream/manage-video-library/searching.mdx |    1 -
 src/content/docs/stream/stream-api.mdx        |    1 -
 .../stream/stream-live/custom-domains.mdx     |    3 +-
 .../download-stream-live-videos.mdx           |    4 +-
 .../docs/stream/stream-live/dvr-for-live.mdx  |   16 +-
 src/content/docs/stream/stream-live/index.mdx |    7 +-
 .../stream-live/live-instant-clipping.mdx     |   91 +-
 .../docs/stream/stream-live/simulcasting.mdx  |   40 +-
 .../stream/stream-live/start-stream-live.mdx  |    1 +
 .../stream/stream-live/troubleshooting.mdx    |   73 +-
 .../docs/stream/stream-live/webhooks.mdx      |   64 +-
 .../docs/stream/transform-videos/bindings.mdx |   36 +-
 .../docs/stream/transform-videos/index.mdx    |    4 +-
 .../docs/stream/uploading-videos/index.mdx    |   14 +-
 .../stream/uploading-videos/player-api.mdx    |  227 ++--
 .../uploading-videos/resumable-uploads.mdx    |    6 -
 .../uploading-videos/upload-via-link.mdx      |   80 +-
 .../viewing-videos/displaying-thumbnails.mdx  |   56 +-
 .../using-the-player-api.mdx                  |  260 ++--
 .../api-content-types/deprecated-apis.mdx     |    4 +-
 .../api-content-types/endpoints.mdx           |   18 +-
 .../api-content-types/index.mdx               |    2 +-
 .../api-content-types/parameters.mdx          |    2 +-
 .../guidelines-for-curl-commands.mdx          |   50 +-
 .../style-guide/components/anchor-heading.mdx |   11 +-
 .../components/available-notifications.mdx    |   15 +-
 .../style-guide/components/description.mdx    |    8 +-
 .../docs/style-guide/components/example.mdx   |   18 +-
 .../style-guide/components/feature-table.mdx  |    4 +-
 .../docs/style-guide/components/feature.mdx   |    8 +-
 .../components/glossary-definition.mdx        |   12 +-
 .../components/glossary-tooltip.mdx           |   12 +-
 .../docs/style-guide/components/glossary.mdx  |   12 +-
 .../style-guide/components/inline-badge.mdx   |   35 +-
 .../style-guide/components/link-cards.mdx     |   24 +-
 .../style-guide/components/list-tutorials.mdx |    2 +-
 .../components/package-managers.mdx           |    4 +-
 .../components/pages-build-preset.mdx         |    4 +-
 .../docs/style-guide/components/plan.mdx      |    5 +-
 .../components/product-availability-text.mdx  |    8 +-
 .../components/product-features.mdx           |    5 +-
 .../components/related-product.mdx            |    7 +-
 .../docs/style-guide/components/rule-id.mdx   |    4 +-
 .../docs/style-guide/components/steps.mdx     |    2 +-
 .../components/subtract-ip-calculator.mdx     |    6 +-
 .../components/type-highlighting.mdx          |    2 +-
 .../docs/style-guide/components/usage.mdx     |    2 +-
 .../components/wrangler-namespace.mdx         |    2 +-
 .../docs/style-guide/components/youtube.mdx   |    6 +-
 .../docs/style-guide/contributions.mdx        |   78 +-
 .../component-attributes/dynamic-lists.mdx    |    8 +-
 .../component-attributes/examples.mdx         |    8 +-
 .../component-attributes/glossary-entry.mdx   |   10 -
 .../component-attributes/index.mdx            |    2 +-
 .../intended-audience.mdx                     |   14 +-
 .../component-attributes/links.mdx            |   18 +-
 .../mathematical-operations.mdx               |    6 +-
 .../component-attributes/next-steps.mdx       |    6 +-
 .../notes-tips-warnings.mdx                   |    8 +-
 .../information-architecture.mdx              |   14 +-
 .../code-conventions-and-format.mdx           |   62 +-
 .../formatting/dates-and-times.mdx            |    6 +-
 .../formatting/external-references.mdx        |    6 +-
 .../formatting/file-types-and-extensions.mdx  |   12 +-
 .../docs/style-guide/formatting/index.mdx     |    2 +-
 .../style-guide/formatting/keyboard-keys.mdx  |   24 +-
 .../notes-and-other-notation-types.mdx        |    1 +
 .../numbers-and-units-of-measurement.mdx      |   18 +-
 .../product-name-and-pluralization.mdx        |    4 +-
 .../formatting/structure/index.mdx            |    2 +-
 .../formatting/structure/lists.mdx            |   79 +-
 .../formatting/structure/tables.mdx           |   79 +-
 .../docs/style-guide/frontmatter/sidebar.mdx  |    4 +-
 .../docs/style-guide/grammar/index.mdx        |    2 +-
 .../grammar/parts-of-speech/abbreviations.mdx |   46 +-
 .../grammar/parts-of-speech/acronyms.mdx      |    8 +-
 .../parts-of-speech/capitalization.mdx        |  160 ++-
 .../parts-of-speech/compound-words.mdx        |   53 +-
 .../grammar/parts-of-speech/contractions.mdx  |    2 +-
 .../grammar/parts-of-speech/index.mdx         |    2 +-
 .../parts-of-speech/nouns-and-pronouns.mdx    |    2 +-
 .../grammar/parts-of-speech/possessives.mdx   |    2 +-
 .../grammar/parts-of-speech/prepositions.mdx  |    2 +-
 .../punctuation-marks-and-symbols/commas.mdx  |    2 +-
 .../punctuation-marks-and-symbols/dashes.mdx  |   16 +-
 .../punctuation-marks-and-symbols/index.mdx   |    2 +-
 .../docs/style-guide/how-we-docs/our-site.mdx |    1 -
 .../docs/style-guide/how-we-docs/reviews.mdx  |   21 +-
 .../support/contacting-cloudflare-support.mdx |   46 +-
 src/content/docs/support/index.mdx            |    2 +-
 ...ress-plugin-automatic-cache-management.mdx |   16 +-
 ...-enable-http2-server-push-in-wordpress.mdx |    6 +-
 ...tent-management-systems-like-wordpress.mdx |   38 +-
 .../content-management-system-cms/index.mdx   |    2 +-
 ...dpress-in-cloudflares-wordpress-plugin.mdx |   26 +-
 .../forum-software/index.mdx                  |    2 +-
 ...-various-forums-vbulletin-xenforo-mybb.mdx |   10 +-
 .../support/third-party-software/index.mdx    |    2 +-
 .../third-party-software/others/index.mdx     |    2 +-
 ...ess-costs-between-azure-and-cloudflare.mdx |    8 +-
 .../cannot-locate-dashboard-account.mdx       |    8 +-
 ...-information-for-troubleshooting-sites.mdx |   26 +-
 .../geographic-traffic-routing.mdx            |    2 +-
 .../general-troubleshooting/index.mdx         |    2 +-
 .../not-receiving-cloudflare-emails.mdx       |   14 +-
 .../service-disruption.mdx                    |    8 +-
 .../third-party-load-balancers.mdx            |   12 +-
 .../troubleshooting-crawl-errors.mdx          |   40 +-
 .../4xx-client-error/error-400.mdx            |    2 +-
 .../4xx-client-error/error-401.mdx            |    2 +-
 .../4xx-client-error/error-406.mdx            |    2 +-
 .../4xx-client-error/error-407.mdx            |    2 +-
 .../4xx-client-error/error-408.mdx            |    2 +-
 .../4xx-client-error/error-409.mdx            |    2 +-
 .../4xx-client-error/error-410.mdx            |    2 +-
 .../4xx-client-error/error-411.mdx            |    2 +-
 .../4xx-client-error/error-412.mdx            |    2 +-
 .../4xx-client-error/error-413.mdx            |    2 +-
 .../4xx-client-error/error-414.mdx            |    2 +-
 .../4xx-client-error/error-416.mdx            |    2 +-
 .../4xx-client-error/error-417.mdx            |    2 +-
 .../4xx-client-error/error-429.mdx            |    1 -
 .../4xx-client-error/error-451.mdx            |    2 +-
 .../4xx-client-error/index.mdx                |    4 +-
 .../cloudflare-10xxx-errors/error-10028.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10043.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10044.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10045.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10046.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10047.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10048.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10049.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10050.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10051.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10052.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10055.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10056.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10058.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10059.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10060.mdx   |    2 +-
 .../cloudflare-10xxx-errors/index.md          |    2 +-
 .../cloudflare-1xxx-errors/error-1000.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1002.mdx     |    4 +-
 .../cloudflare-1xxx-errors/error-1004.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1009.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1014.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1035.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1040.mdx     |    1 -
 .../cloudflare-1xxx-errors/error-1102.mdx     |    1 -
 .../cloudflare-1xxx-errors/index.mdx          |    4 -
 .../cloudflare-5xx-errors/error-501.mdx       |    2 +-
 .../cloudflare-5xx-errors/error-503.mdx       |    9 +-
 .../cloudflare-5xx-errors/error-520.mdx       |    1 -
 .../cloudflare-5xx-errors/error-522.mdx       |    4 +-
 .../cloudflare-5xx-errors/error-524.mdx       |    5 +-
 .../cloudflare-5xx-errors/error-525.mdx       |    2 +-
 .../cloudflare-5xx-errors/index.mdx           |    6 +-
 .../cloudflare-error-headers.mdx              |   11 +-
 .../http-status-codes/index.mdx               |    2 +-
 .../docs/support/troubleshooting/index.mdx    |    2 +-
 .../restoring-visitor-ips/index.mdx           |    2 +-
 .../restoring-original-visitor-ips.mdx        |    5 +-
 src/content/docs/tenant/how-to/index.mdx      |    2 +-
 src/content/docs/tenant/index.mdx             |    8 +-
 src/content/docs/tenant/reference/index.mdx   |    2 +-
 .../advanced-topics/best-practices.mdx        |    2 -
 .../terraform/how-to/create-partial-zone.mdx  |    3 +-
 .../how-to/create-secondary-zone.mdx          |    4 +-
 .../authentication-error-dns-records.mdx      |    2 +-
 src/content/docs/terraform/tutorial/index.mdx |   36 +-
 src/content/docs/time-services/index.mdx      |    2 +-
 .../docs/time-services/roughtime/index.mdx    |    2 +-
 .../docs/time-services/roughtime/recipes.mdx  |   32 +-
 src/content/docs/time-services/tos.mdx        |    2 +-
 .../tunnel/advanced/origin-parameters.mdx     |   16 +-
 .../docs/tunnel/advanced/run-parameters.mdx   |   24 +-
 src/content/docs/tunnel/changelog.mdx         |    5 +-
 .../tunnel/deployment-guides/terraform.mdx    |    1 -
 .../tunnel/downloads/system-requirements.mdx  |    7 +-
 src/content/docs/tunnel/troubleshooting.mdx   |    1 +
 .../hostname-management/any-hostname.mdx      |   69 +-
 .../hostname-management/index.mdx             |    5 +-
 .../hostname-management/pre-clearance.mdx     |   17 +-
 .../additional-configuration/index.mdx        |    3 +-
 .../pre-clearance-support.mdx                 |    3 +-
 .../docs/turnstile/concepts/challenges.mdx    |    1 -
 src/content/docs/turnstile/concepts/index.mdx |    5 +-
 .../turnstile/extensions/google-firebase.mdx  |   35 +-
 .../docs/turnstile/extensions/index.mdx       |    3 +-
 .../turnstile/extensions/pages-plugin.mdx     |    1 -
 .../turnstile/extensions/waiting-room.mdx     |    1 -
 .../get-started/widget-management/api.mdx     |   61 +-
 .../get-started/widget-management/index.mdx   |    4 +-
 .../widget-management/terraform.mdx           |   10 +-
 .../docs/turnstile/migration/hcaptcha.mdx     |    2 +-
 .../docs/turnstile/reference/index.mdx        |    3 +-
 .../reference/supported-browsers.mdx          |    1 -
 .../reference/supported-languages.mdx         |    1 -
 .../reference/turnstile-privacy-addendum.mdx  |    1 -
 .../challenge-solve-issues.mdx                |    1 -
 .../client-side-errors/index.mdx              |  137 +-
 .../docs/turnstile/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/rotate-secret-key.mdx     |    3 +-
 .../turnstile/troubleshooting/testing.mdx     |   67 +-
 .../turnstile/turnstile-analytics/index.mdx   |    5 +-
 .../excluding-turnstile-from-e2e-tests.mdx    |   54 +-
 .../fraud-detection-with-ephemeral-ids.mdx    |    4 +-
 ...ating-turnstile-waf-and-bot-management.mdx |    8 +-
 .../docs/use-cases/e-commerce/performance.mdx |    2 +-
 .../encrypt-all-keep-site-secure.mdx          |   27 +-
 .../protect-sensitive-forms-fraud-abuse.mdx   |   77 +-
 .../stop-account-takeover-attacks.mdx         |   42 +-
 .../solutions/stop-malicious-bots.mdx         |    9 +-
 .../docs/use-cases/web-apps/performance.mdx   |    3 +-
 .../docs/vectorize/best-practices/index.mdx   |    2 +-
 .../vectorize/best-practices/list-vectors.mdx |    3 +-
 src/content/docs/vectorize/demos.mdx          |   11 +-
 .../docs/vectorize/examples/agents.mdx        |    2 +-
 src/content/docs/vectorize/examples/index.mdx |    2 +-
 .../docs/vectorize/get-started/index.mdx      |    2 +-
 src/content/docs/vectorize/platform/index.mdx |    2 +-
 .../docs/vectorize/reference/index.mdx        |    2 +-
 src/content/docs/version-management/about.mdx |    6 +-
 .../how-to/compare-versions.mdx               |    2 +-
 .../how-to/environments.mdx                   |   33 +-
 .../docs/version-management/how-to/index.mdx  |    4 +-
 .../version-management/how-to/versions.mdx    |    4 +-
 .../reference/available-configurations.mdx    |   14 +-
 .../version-management/reference/index.mdx    |    4 +-
 .../reference/read-only-environments.mdx      |    7 +-
 .../waf/custom-rules/create-dashboard.mdx     |    1 -
 .../use-cases/sequence-custom-rules.mdx       |    2 +-
 src/content/docs/waf/glossary.mdx             |    3 +-
 src/content/docs/waf/managed-rules/index.mdx  |    1 -
 src/content/docs/waf/tools/index.mdx          |    1 -
 src/content/docs/waf/tools/privacy-pass.mdx   |    9 +-
 src/content/docs/waf/troubleshooting/faq.mdx  |    1 +
 src/content/docs/waiting-room/about.mdx       |    6 +-
 .../additional-options/create-events.mdx      |   33 +-
 .../waiting-room/additional-options/index.mdx |    3 +-
 .../additional-options/ssl-for-saas.mdx       |    1 -
 .../waiting-room-rules/index.mdx              |    3 +-
 .../docs/waiting-room/api-reference.mdx       |    1 -
 src/content/docs/waiting-room/glossary.mdx    |    3 +-
 .../how-to/control-user-session.mdx           |    8 +-
 .../how-to/edit-delete-waiting-room.mdx       |   41 +-
 .../docs/waiting-room/how-to/index.mdx        |    3 +-
 .../waiting-room/how-to/json-response.mdx     |    2 -
 .../how-to/monitor-waiting-room.mdx           |   45 +-
 .../how-to/place-waiting-room.mdx             |    5 +-
 .../how-to/waiting-room-dashboard.mdx         |    3 +-
 src/content/docs/waiting-room/plans.mdx       |    3 +-
 .../reference/configuration-settings.mdx      |   11 +-
 .../docs/waiting-room/reference/index.mdx     |    3 +-
 .../reference/waiting-room-api.mdx            |   21 +-
 .../reference/waiting-room-cookie.mdx         |   12 +-
 .../docs/waiting-room/troubleshooting.mdx     |   50 +-
 .../docs/warp-client/get-started/linux.mdx    |   21 +-
 .../docs/warp-client/known-issues-and-faq.mdx |    8 +-
 .../docs/warp-client/legal/3rdparty.mdx       | 1139 +++++++----------
 src/content/docs/warp-client/legal/index.mdx  |    7 +-
 src/content/docs/warp-client/privacy.mdx      |    1 -
 .../configuration-options/filters.mdx         |    3 +-
 .../configuration-options/index.mdx           |    3 +-
 .../data-metrics/core-web-vitals.mdx          |    5 +-
 .../data-origin-and-collection.mdx            |    2 +-
 .../web-analytics/data-metrics/dimensions.mdx |   21 +-
 .../data-metrics/high-level-metrics.mdx       |    9 +-
 .../docs/web-analytics/data-metrics/index.mdx |    3 +-
 .../data-metrics/page-load-time-summary.mdx   |    1 -
 src/content/docs/web-analytics/faq.mdx        |   14 +-
 .../web-analytics/get-started/rum-beacon.mdx  |    3 +-
 .../get-started/web-analytics-spa.mdx         |   10 +-
 src/content/docs/web-analytics/limits.mdx     |    1 -
 src/content/docs/web3/about.mdx               |    2 +-
 src/content/docs/web3/api-reference.mdx       |    1 -
 .../web3/ethereum-gateway/concepts/index.mdx  |    3 +-
 .../web3/ethereum-gateway/reference/index.mdx |    3 +-
 .../reference/kill-switches.mdx               |    7 +-
 .../reference/rinkeby-deprecation.mdx         |   57 +-
 .../reference/supported-networks.mdx          |    1 -
 src/content/docs/web3/how-to/index.mdx        |    3 +-
 .../docs/web3/how-to/use-ipfs-gateway.mdx     |    1 -
 .../web3/ipfs-gateway/concepts/dnslink.mdx    |    1 -
 .../docs/web3/ipfs-gateway/concepts/index.mdx |    3 +-
 .../reference/automated-deployment.mdx        |    7 +-
 .../web3/ipfs-gateway/reference/index.mdx     |    3 +-
 .../peering-with-content-providers.mdx        |  129 +-
 .../reference/updating-for-ipfs.mdx           |    7 +-
 .../web3/ipfs-gateway/troubleshooting.mdx     |    1 -
 .../web3/reference/gateway-dns-records.mdx    |    5 +-
 .../docs/web3/reference/gateway-status.mdx    |    1 -
 src/content/docs/web3/reference/index.mdx     |    3 +-
 .../docs/web3/reference/migration-guide.mdx   |    3 +-
 src/content/docs/workers-ai/agents.mdx        |   13 +-
 src/content/docs/workers-ai/api-reference.mdx |    1 -
 .../workers-ai/configuration/bindings.mdx     |   26 +-
 .../configuration/hugging-face-chat-ui.mdx    |   34 +-
 .../embedded/examples/fetch.mdx               |   36 +-
 .../function-calling/embedded/examples/kv.mdx |    1 +
 .../embedded/examples/openapi.mdx             |   22 +-
 .../function-calling/embedded/index.mdx       |    4 +-
 .../docs/workers-ai/get-started/dashboard.mdx |    5 +-
 .../docs/workers-ai/get-started/index.mdx     |    4 +-
 .../docs/workers-ai/get-started/rest-api.mdx  |    3 +-
 src/content/docs/workers-ai/guides/agents.mdx |    2 +-
 ...generation-using-deepseek-coder-models.mdx |   18 +-
 ...choose-the-right-text-generation-model.mdx |   72 +-
 .../docs/workers-ai/platform/data-usage.mdx   |    8 +-
 .../docs/workers-ai/platform/pricing.mdx      |   62 +-
 .../docs/workers-vpc/configuration/index.mdx  |    2 +-
 .../configuration/vpc-services/terraform.mdx  |    1 +
 .../docs/workers-vpc/examples/private-api.mdx |    4 +-
 .../examples/private-s3-bucket.mdx            |    4 +-
 .../route-across-private-services.mdx         |   15 +-
 .../workers/ci-cd/builds/automatic-prs.mdx    |    1 +
 .../workers/ci-cd/builds/build-caching.mdx    |   18 +-
 .../docs/workers/ci-cd/builds/build-image.mdx |    5 +-
 .../workers/ci-cd/builds/configuration.mdx    |   12 +-
 .../docs/workers/ci-cd/builds/index.mdx       |   10 +-
 .../ci-cd/builds/limits-and-pricing.mdx       |   24 +-
 .../workers/ci-cd/builds/troubleshoot.mdx     |    1 +
 .../ci-cd/external-cicd/github-actions.mdx    |    2 +
 .../ci-cd/external-cicd/gitlab-cicd.mdx       |    1 +
 .../configuration/integrations/index.mdx      |   22 +-
 .../configuration/routing/custom-domains.mdx  |   36 +-
 .../workers/configuration/routing/routes.mdx  |   14 +-
 .../sites/start-from-existing.mdx             |   36 +-
 .../sites/start-from-scratch.mdx              |   50 +-
 .../configuration/sites/start-from-worker.mdx |   20 +-
 .../versions-and-deployments/index.mdx        |    2 +-
 .../version-overrides.mdx                     |   24 +-
 .../configuration/workers-with-page-rules.mdx |   50 +-
 .../third-party-integrations/supabase.mdx     |    4 +-
 .../third-party-integrations/turso.mdx        |    6 +-
 .../third-party-integrations/upstash.mdx      |    3 +-
 .../third-party-integrations/xata.mdx         |    1 -
 .../development-testing/multi-workers.mdx     |   44 +-
 .../workers/development-testing/testing.mdx   |    2 +-
 .../development-testing/vite-plugin.mdx       |    2 +-
 .../docs/workers/examples/103-early-hints.mdx |    2 +-
 .../docs/workers/examples/ab-testing.mdx      |    1 -
 .../accessing-the-cloudflare-object.mdx       |    1 -
 .../workers/examples/aggregate-requests.mdx   |    1 -
 .../docs/workers/examples/alter-headers.mdx   |    1 -
 .../workers/examples/auth-with-headers.mdx    |    1 -
 .../docs/workers/examples/basic-auth.mdx      |    1 -
 .../docs/workers/examples/block-on-tls.mdx    |    1 -
 .../workers/examples/bulk-origin-proxy.mdx    |    1 -
 .../docs/workers/examples/bulk-redirects.mdx  |    1 -
 .../docs/workers/examples/cache-api.mdx       |    1 -
 .../workers/examples/cache-post-request.mdx   |    1 -
 .../docs/workers/examples/cache-tags.mdx      |    1 -
 .../workers/examples/cache-using-fetch.mdx    |    5 +-
 .../workers/examples/conditional-response.mdx |    1 -
 .../workers/examples/cors-header-proxy.mdx    |    2 -
 .../examples/country-code-redirect.mdx        |    1 -
 .../workers/examples/data-loss-prevention.mdx |    1 -
 .../docs/workers/examples/debugging-logs.mdx  |    1 -
 .../workers/examples/extract-cookie-value.mdx |    1 -
 .../docs/workers/examples/fetch-json.mdx      |    1 -
 .../examples/geolocation-app-weather.mdx      |    1 -
 .../examples/geolocation-custom-styling.mdx   |    1 -
 .../examples/geolocation-hello-world.mdx      |    1 -
 .../workers/examples/hot-link-protection.mdx  |    1 -
 .../examples/modify-request-property.mdx      |    1 -
 .../docs/workers/examples/modify-response.mdx |    1 -
 .../examples/multiple-cron-triggers.mdx       |    1 -
 .../workers/examples/openai-sdk-streaming.mdx |    1 -
 .../docs/workers/examples/post-json.mdx       |    1 -
 .../protect-against-timing-attacks.mdx        |    1 -
 .../docs/workers/examples/read-post.mdx       |    1 -
 .../docs/workers/examples/return-html.mdx     |    1 -
 .../docs/workers/examples/rewrite-links.mdx   |    1 -
 .../workers/examples/signing-requests.mdx     |    1 -
 .../examples/turnstile-html-rewriter.mdx      |    1 -
 .../docs/workers/examples/websockets.mdx      |    4 +-
 .../framework-guides/ai-and-agents/index.mdx  |   13 +-
 .../workers/framework-guides/apis/index.mdx   |    9 +-
 .../docs/workers/framework-guides/index.mdx   |    9 +-
 .../framework-guides/mobile-apps/expo.mdx     |    2 +-
 .../framework-guides/mobile-apps/index.mdx    |    9 +-
 .../framework-guides/web-apps/astro.mdx       |   24 +-
 .../framework-guides/web-apps/index.mdx       |    9 +-
 .../web-apps/more-web-frameworks/analog.mdx   |   18 +-
 .../web-apps/more-web-frameworks/angular.mdx  |    6 +-
 .../more-web-frameworks/docusaurus.mdx        |    2 -
 .../web-apps/more-web-frameworks/hono.mdx     |    2 -
 .../web-apps/more-web-frameworks/index.mdx    |    2 +-
 .../web-apps/more-web-frameworks/nuxt.mdx     |   18 +-
 .../web-apps/more-web-frameworks/solid.mdx    |   18 +-
 .../web-apps/more-web-frameworks/waku.mdx     |   14 +-
 .../framework-guides/web-apps/nextjs.mdx      |   48 +-
 .../framework-guides/web-apps/redwoodsdk.mdx  |    2 +-
 .../framework-guides/web-apps/sveltekit.mdx   |   24 +-
 .../framework-guides/web-apps/vike.mdx        |   32 +-
 .../workers/framework-guides/web-apps/vue.mdx |   24 +-
 .../docs/workers/get-started/dashboard.mdx    |   11 +-
 .../docs/workers/get-started/quickstarts.mdx  |    1 -
 .../workers/languages/javascript/index.mdx    |   13 +-
 .../docs/workers/observability/errors.mdx     |   58 +-
 .../exporting-opentelemetry-data/axiom.mdx    |   22 +-
 .../grafana-cloud.mdx                         |   31 +-
 .../honeycomb.mdx                             |    8 +-
 .../exporting-opentelemetry-data/index.mdx    |   32 +-
 .../exporting-opentelemetry-data/posthog.mdx  |   47 +-
 .../exporting-opentelemetry-data/sentry.mdx   |   29 +-
 .../workers/observability/logs/logpush.mdx    |   91 +-
 .../observability/logs/real-time-logs.mdx     |    1 +
 .../observability/logs/workers-logs.mdx       |    6 +-
 .../observability/metrics-and-analytics.mdx   |    1 +
 .../workers/observability/source-maps.mdx     |   15 +-
 src/content/docs/workers/platform/betas.mdx   |   10 +-
 .../platform/built-with-cloudflare.mdx        |    2 +-
 .../changelog/historical-changelog.mdx        |  448 +++----
 .../docs/workers/platform/changelog/index.mdx |    2 +-
 .../docs/workers/platform/known-issues.mdx    |   10 +-
 src/content/docs/workers/platform/pricing.mdx |    6 +-
 .../workers/reference/how-the-cache-works.mdx |    4 -
 .../workers/reference/how-workers-works.mdx   |   16 +-
 .../docs/workers/reference/protocols.mdx      |   14 +-
 .../docs/workers/reference/security-model.mdx |    6 +-
 .../workers/runtime-apis/bindings/index.mdx   |   55 +-
 .../runtime-apis/bindings/rate-limit.mdx      |   54 +-
 .../bindings/service-bindings/http.mdx        |   22 +-
 .../workers/runtime-apis/bindings/stream.mdx  |    1 -
 .../bindings/version-metadata.mdx             |    2 +-
 .../docs/workers/runtime-apis/cache.mdx       |  105 +-
 .../docs/workers/runtime-apis/console.mdx     |   44 +-
 .../docs/workers/runtime-apis/encoding.mdx    |   44 +-
 .../docs/workers/runtime-apis/eventsource.mdx |   75 +-
 .../workers/runtime-apis/handlers/fetch.mdx   |   27 +-
 .../workers/runtime-apis/handlers/index.mdx   |    4 +-
 .../workers/runtime-apis/handlers/tail.mdx    |  227 ++--
 .../docs/workers/runtime-apis/headers.mdx     |   19 +-
 .../workers/runtime-apis/messagechannel.mdx   |   16 +-
 .../docs/workers/runtime-apis/nodejs/util.mdx |    6 +-
 .../docs/workers/runtime-apis/performance.mdx |    2 +-
 .../runtime-apis/rpc/error-handling.mdx       |    6 +-
 .../runtime-apis/rpc/reserved-methods.mdx     |   14 +-
 .../runtime-apis/streams/readablestream.mdx   |   44 +-
 .../streams/readablestreambyobreader.mdx      |   39 +-
 .../streams/readablestreamdefaultreader.mdx   |   36 +-
 .../runtime-apis/streams/transformstream.mdx  |   77 +-
 .../runtime-apis/streams/writablestream.mdx   |   35 +-
 .../streams/writablestreamdefaultwriter.mdx   |   58 +-
 .../docs/workers/runtime-apis/tcp-sockets.mdx |  183 ++-
 .../docs/workers/runtime-apis/web-crypto.mdx  |  425 ++----
 .../runtime-apis/webassembly/index.mdx        |   16 +-
 .../docs/workers/runtime-apis/websockets.mdx  |  177 +--
 .../routing/full-stack-application.mdx        |    5 +-
 .../testing/miniflare/storage/cache.md        |    4 +-
 .../testing/vitest-integration/recipes.mdx    |    2 +-
 .../docs/workers/vite-plugin/tutorial.mdx     |    1 +
 src/content/docs/workers/wrangler/api.mdx     |   52 +-
 .../docs/workers/wrangler/commands/r2.mdx     |    1 -
 .../docs/workers/wrangler/configuration.mdx   |   46 +-
 .../docs/workers/wrangler/custom-builds.mdx   |   15 +-
 .../docs/workers/wrangler/deprecations.mdx    |  122 +-
 .../wrangler/migration/update-v2-to-v3.mdx    |    2 -
 .../v1-to-v2/wrangler-legacy/commands.mdx     |    8 +-
 src/content/docs/workflows/build/index.mdx    |    2 +-
 .../docs/workflows/build/test-workflows.mdx   |    2 +-
 .../docs/workflows/examples/agents.mdx        |    2 +-
 .../docs/workflows/examples/backup-d1.mdx     |    1 -
 .../docs/workflows/examples/send-invoices.mdx |    1 -
 .../docs/workflows/examples/twilio.mdx        |    1 -
 .../workflows/examples/wait-for-event.mdx     |   13 +-
 .../docs/workflows/observability/index.mdx    |    4 +-
 .../docs/workflows/python/bindings.mdx        |    2 +-
 .../docs/workflows/reference/changelog.mdx    |    4 +-
 .../docs/workflows/reference/glossary.mdx     |    2 +-
 .../docs/workflows/reference/index.mdx        |    2 +-
 .../docs/workflows/reference/pricing.mdx      |   26 +-
 .../workflows/reference/wrangler-commands.mdx |    4 +-
 src/content/docs/workflows/videos.mdx         |   10 +-
 .../advanced/datalayer-compatibility.mdx      |   11 +-
 .../zaraz/advanced/domains-not-proxied.mdx    |    1 -
 .../zaraz/advanced/google-consent-mode.mdx    |   27 +-
 .../docs/zaraz/advanced/import-export.mdx     |    9 +-
 src/content/docs/zaraz/advanced/index.mdx     |    3 +-
 .../load-custom-managed-component.mdx         |    3 +-
 .../docs/zaraz/advanced/load-selectively.mdx  |    3 -
 .../zaraz/advanced/load-zaraz-manually.mdx    |   15 +-
 .../docs/zaraz/advanced/using-jsonata.mdx     |   37 +-
 .../docs/zaraz/consent-management/api.mdx     |  182 +--
 .../zaraz/consent-management/custom-css.mdx   |    4 +-
 .../enable-consent-management.mdx             |    9 +-
 .../consent-management/iab-tcf-compliance.mdx |    4 +-
 .../docs/zaraz/consent-management/index.mdx   |   27 +-
 .../custom-actions/additional-fields.mdx      |    7 +-
 .../zaraz/custom-actions/create-action.mdx    |    3 +-
 .../zaraz/custom-actions/create-trigger.mdx   |    3 +-
 .../custom-actions/edit-tools-and-actions.mdx |   15 +-
 .../zaraz/custom-actions/edit-triggers.mdx    |    7 +-
 src/content/docs/zaraz/embeds.mdx             |    9 +-
 src/content/docs/zaraz/get-started.mdx        |    3 +-
 src/content/docs/zaraz/history/index.mdx      |    3 +-
 src/content/docs/zaraz/history/versions.mdx   |   16 +-
 src/content/docs/zaraz/http-events-api.mdx    |   98 +-
 src/content/docs/zaraz/monitoring/index.mdx   |    5 +-
 src/content/docs/zaraz/pricing-info.mdx       |    7 +-
 src/content/docs/zaraz/reference/context.mdx  |    9 -
 src/content/docs/zaraz/reference/index.mdx    |    3 +-
 .../zaraz/reference/properties-reference.mdx  |   84 +-
 src/content/docs/zaraz/reference/settings.mdx |   18 +-
 .../docs/zaraz/reference/supported-tools.mdx  |    1 -
 .../docs/zaraz/variables/create-variables.mdx |    3 +-
 .../docs/zaraz/variables/edit-variables.mdx   |    7 +-
 src/content/docs/zaraz/variables/index.mdx    |    3 +-
 .../docs/zaraz/variables/worker-variables.mdx |  100 +-
 src/content/docs/zaraz/web-api/debug-mode.mdx |    6 +-
 src/content/docs/zaraz/web-api/ecommerce.mdx  |    3 +-
 src/content/docs/zaraz/web-api/index.mdx      |    3 +-
 src/content/docs/zaraz/web-api/set.mdx        |   21 +-
 .../partials/1.1.1.1/captive-portals.mdx      |    2 +-
 src/content/partials/agents/unique-agents.mdx |    3 +-
 .../ai-crawl-control/plan-comparison.mdx      |   11 +-
 .../ai-gateway/analytics-dashboard.mdx        |    1 -
 src/content/partials/ai-gateway/logging.mdx   |    1 +
 .../ai-gateway/universal-gateway-example.mdx  |    1 -
 .../partials/ai-search/rest-api-auth.mdx      |    2 +-
 .../customer_metadata_boundary_error.mdx      |    5 +-
 .../network-analytics-requirements.mdx        |    7 +-
 .../network-analytics-v1-deprecation.mdx      |    1 -
 .../partials/api-shield/label-methodology.mdx |    9 +-
 .../api-shield/mtls-api-shield-support.mdx    |    1 -
 .../partials/api-shield/mtls-create-rule.mdx  |    5 +-
 .../partials/api-shield/rate-limit-user.mdx   |    1 -
 .../required-session-identifiers.mdx          |    1 -
 .../sequence-mitigation-availability.mdx      |    3 +-
 .../api-shield/session-identifiers.mdx        |    5 +-
 .../partials/billing/two-payment-methods.mdx  |    1 -
 .../bots/about-plan-considerations.mdx        |    5 +-
 .../partials/bots/analytics-features.mdx      |    1 -
 .../partials/bots/bfm-change-notice.mdx       |    1 -
 .../partials/bots/bm-analytics-features.mdx   |    9 +-
 .../bots/bot-settings-vs-custom-rules.mdx     |   18 +-
 src/content/partials/bots/bots-ad.mdx         |    1 -
 src/content/partials/bots/bots-cookie.mdx     |    3 +-
 src/content/partials/bots/bots-heuristics.mdx |    3 +-
 src/content/partials/bots/bots-jsd.mdx        |    1 -
 src/content/partials/bots/bots-ml.mdx         |    5 +-
 .../partials/bots/buttons-plan-pages.mdx      |   16 +-
 .../content-security-policy-limitation.mdx    |    5 +-
 .../partials/bots/disable-cf-bm-cookie.mdx    |    1 -
 .../partials/bots/endpoint-label-warning.mdx  |    7 +-
 src/content/partials/bots/execution-order.mdx |    2 +-
 src/content/partials/bots/flexible-sbfm.mdx   |    3 +-
 src/content/partials/bots/ja3-ja4-null.mdx    |    3 +-
 .../partials/bots/jsd-availability.mdx        |    3 +-
 .../partials/bots/plan-get-started.mdx        |    1 -
 src/content/partials/bots/plan-intro.mdx      |    1 -
 src/content/partials/bots/sequence-rules.mdx  |    7 +-
 .../bots/signals-intelligence-and-ja4.mdx     |    7 +-
 src/content/partials/bots/verified-bots.mdx   |    1 -
 .../improve-blurry-screenshot-resolution.mdx  |   15 +-
 .../partials/byoip/cloudflare-asn-callout.mdx |    2 +-
 src/content/partials/byoip/loa.mdx            |    2 +-
 .../byoip/validate-prefix-endpoint.mdx        |    1 -
 .../cache/cache-reserve-billing-note.mdx      |    3 -
 .../cache/cache-reserve-eligibility.mdx       |    2 +-
 .../partials/cache/cache-reserve-intro.mdx    |    2 +-
 .../partials/cache/cache-reserve-limits.mdx   |    2 +-
 .../cache/cache-reserve-operations.mdx        |    2 +-
 src/content/partials/cache/edge-ttl.mdx       |    2 +-
 .../partials/cache/regional-tiered-cache.mdx  |    2 +-
 .../partials/cache/smart-tiered-cache.mdx     |    2 +-
 .../cf-clearance-cookie.mdx                   |    3 +-
 .../create-challenge-page.mdx                 |    5 +-
 .../apex-proxying-process.mdx                 |    3 -
 .../cname-target-process.mdx                  |    1 -
 .../create-custom-hostname-api.mdx            |    6 +-
 .../create-custom-hostname-limitations.mdx    |    7 +-
 .../create-custom-hostname.mdx                |   13 +-
 .../custom-origin-server-definition.mdx       |    5 +-
 .../delete-custom-hostname-dash.mdx           |    1 -
 .../get-started-initial-setup-preamble.mdx    |    1 -
 .../get-started-per-hostname.mdx              |    5 +-
 .../get-started-prereqs.mdx                   |    7 +-
 .../get-started-service-continuation.mdx      |    1 -
 .../http-dcv-situation.mdx                    |    5 +-
 .../issue-certs-preamble.mdx                  |    1 -
 .../provider-guide-compatibility.mdx          |    7 +-
 .../provider-guide-zone-hold.mdx              |    2 +-
 .../regional-services.mdx                     |    1 -
 .../saas-customer-churn.mdx                   |    1 -
 .../same-name-as-zone.mdx                     |    3 +-
 .../ssl-for-saas-create-hostname.mdx          |    1 -
 .../ssl-for-saas-definition.mdx               |    1 -
 .../ssl-for-saas-plan-limitation.mdx          |    3 -
 .../ssl-for-saas-validate-patch.mdx           |    1 -
 .../txt-dcv-situation.mdx                     |    1 -
 .../txt-validation_api.mdx                    |   83 +-
 .../txt-validation_dashboard.mdx              |    1 -
 .../txt-validation_post.mdx                   |    3 -
 .../txt-validation_preamble.mdx               |    1 -
 .../update-dcv-method.mdx                     |    1 -
 .../wildcard-hostname-reqs.mdx                |    1 -
 .../access/access-block-page.mdx              |    7 +-
 .../cloudflare-one/access/add-mtls-cert.mdx   |   21 +-
 .../cloudflare-one/access/add-target.mdx      |   17 +-
 .../cloudflare-one/access/app-launcher.mdx    |    4 +-
 .../cloudflare-one/access/bookmarks.mdx       |    3 +-
 .../access/create-service-token.mdx           |    3 +-
 .../access/enable-scim-on-dashboard.mdx       |   14 +-
 .../access/entra-id-terraform.mdx             |    1 -
 .../cloudflare-one/access/idp-integration.mdx |    4 +-
 .../access/isolation-prereqs.mdx              |    1 -
 .../access/saas-apps/miro-sso.mdx             |    5 +-
 .../access/saas-apps/saas-sessions.mdx        |    2 +-
 .../access/saas-apps/salesforce-sso.mdx       |    1 -
 .../access/scim-requires-login.mdx            |    2 +-
 .../access/secure-tunnel-with-access.mdx      |    1 -
 .../self-hosted-app/advanced-settings.mdx     |    1 -
 .../browser-rendering-policies.mdx            |    3 +-
 .../self-hosted-app/generic-public-app.mdx    |   25 +-
 .../self-hosted-app/product-compatibility.mdx |    8 +-
 .../access/self-hosted-app/ssh-sessions.mdx   |    2 +-
 .../access/session-duration.mdx               |    1 -
 .../access/short-lived-certs-intro.mdx        |    4 +-
 .../partials/cloudflare-one/access/tags.mdx   |    1 -
 .../access/verify-scim-provisioning.mdx       |    2 +-
 .../partials/cloudflare-one/aws-resolver.mdx  |    3 +-
 .../casb/casb-dlp-integrations.mdx            |    1 -
 .../casb/microsoft/m365-copilot-findings.mdx  |    2 +-
 .../cloudflare-one/choose-team-name.mdx       |    1 -
 .../clientless-browser-isolation.mdx          |    3 +-
 .../dex/notifications-intro.mdx               |    2 +-
 .../partials/cloudflare-one/dex/pcaps-run.mdx |    2 +-
 ...-use-case-1-3-create-quarantine-policy.mdx |    8 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 ...ase-configure-quarantine-notifications.mdx |    1 -
 .../deployment/set-up-mx-inline-step.mdx      |    3 +-
 .../dispositions-and-attributes.mdx           |   10 +-
 .../email-security/domain-information.mdx     |   20 +-
 .../email-security/enable-logs.mdx            |    3 +-
 .../onboarding-prerequisites.mdx              |    3 +-
 .../cloudflare-one/gateway/add-logo-image.mdx |    1 -
 .../gateway/debugging-policies.mdx            |    1 -
 .../gateway/egress-selector-cgnat-ips.mdx     |    3 +-
 .../gateway/egress-selector-onramps.mdx       |   14 +-
 .../gateway/egress-selector-split-tunnels.mdx |    4 +-
 .../gateway/enable-tls-decryption.mdx         |    2 +-
 .../policies/do-not-inspect-applications.mdx  |    3 +-
 .../policies/egress-destination-ip.mdx        |    1 -
 ...trict-access-to-private-networks-allow.mdx |    8 +-
 ...trict-access-to-private-networks-block.mdx |    2 +-
 ...estrict-access-to-private-networks-dns.mdx |    8 +-
 .../gateway/resolver-policies-intro.mdx       |    1 -
 .../gateway/selectors/category-options.mdx    |    1 -
 .../gateway/selectors/destination-country.mdx |    7 +-
 .../gateway/selectors/device-posture.mdx      |    1 -
 .../gateway/selectors/dns-resolver-ip.mdx     |    1 -
 .../gateway/selectors/doh-subdomain.mdx       |    1 -
 .../gateway/selectors/oidc-claims.mdx         |    4 +-
 .../gateway/selectors/protocol.mdx            |    1 -
 .../gateway/selectors/query-record-type.mdx   |    1 -
 .../gateway/selectors/security-categories.mdx |    1 -
 .../gateway/selectors/source-country-dns.mdx  |    7 +-
 .../gateway/selectors/source-country-http.mdx |    7 +-
 .../gateway/selectors/source-country.mdx      |    7 +-
 .../gateway/selectors/source-ip-dns.mdx       |    1 -
 .../gateway/selectors/source-ip-resolver.mdx  |    1 -
 .../gateway/selectors/user-email.mdx          |    4 +-
 .../gateway/selectors/user-group-email.mdx    |    6 +-
 .../gateway/selectors/user-group-ids.mdx      |    6 +-
 .../gateway/selectors/user-group-names.mdx    |    6 +-
 .../gateway/selectors/user-name.mdx           |    6 +-
 .../gateway/selectors/users-dns.mdx           |   16 +-
 .../gateway/selectors/users-http.mdx          |   16 +-
 .../gateway/selectors/users.mdx               |   13 +-
 .../partials/cloudflare-one/gateway/value.mdx |    4 +-
 .../posture/configure-posture-check.mdx       |    3 +-
 .../posture/prereqs-warp-is-deployed.mdx      |    1 -
 .../cloudflare-one/ssh/decrypt-ssh-log.mdx    |    8 +-
 .../cloudflare-one/ssh/public-key.mdx         |    6 +-
 .../cloudflare-one/ssh/restart-server.mdx     |    2 +-
 .../cloudflare-one/ssh/ssh-proxy-ca-note.mdx  |    3 +-
 .../cloudflare-one/ssh/ssh-proxy-ca.mdx       |    2 +-
 .../cloudflare-one/ssh/upload-ssh-key.mdx     |    2 +-
 .../terraform/cloudflare-resources.mdx        |  312 ++---
 .../terraform/gcp-resources.mdx               |  170 +--
 .../cloudflare-one/terraform/providers-v5.mdx |    2 +-
 .../cloudflare-one/terraform/providers.mdx    |   76 +-
 .../troubleshooting/browser-isolation.mdx     |   18 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    4 +
 .../cloudflare-one/troubleshooting/dex.mdx    |    3 +
 .../troubleshooting/email-security.mdx        |   23 +-
 .../troubleshooting/gateway.mdx               |   13 +-
 .../cloudflare-one/tunnel/1033-error.mdx      |    3 +-
 .../tunnel/account-scoped-roles.mdx           |    5 +-
 .../tunnel/add-published-application.mdx      |   13 +-
 .../cloudflared-replicas-diagram.mdx          |    1 -
 .../load-balancer-tcp-monitors.mdx            |    7 +-
 .../availability/tunnel-capacity-baseline.mdx |    7 +-
 .../availability/tunnel-capacity-intro.mdx    |    1 -
 .../tunnel/catch-all-policy.mdx               |    1 -
 .../tunnel/cgnat-split-tunnels.mdx            |    1 -
 .../cloudflare-one/tunnel/create-tunnel.mdx   |    3 +-
 .../deployment-guides/cloud-create-tunnel.mdx |    3 +-
 .../deployment-guides/cloud-private-ip.mdx    |   22 +-
 .../cloud-public-hostname.mdx                 |    1 -
 .../tunnel/diagnostics/docker.mdx             |   33 +-
 .../tunnel/diagnostics/tunnel-diag-file.mdx   |   24 +-
 .../tunnel/dns-cloudflare-settings.mdx        |    1 -
 .../tunnel/dns-records-intro.mdx              |    1 -
 .../cloudflare-one/tunnel/grpc-support.mdx    |    1 -
 .../tunnel/hostname-format-restrictions.mdx   |   21 +-
 .../tunnel/install-and-run-tunnel.mdx         |    3 +-
 .../locally-managed/tunnel-permissions.mdx    |   20 +-
 .../tunnel/logs/filter-logs.mdx               |    8 +-
 .../tunnel/logs/view-logs-dashboard.mdx       |    1 -
 .../tunnel/logs/view-logs-on-server.mdx       |    1 -
 .../tunnel/metrics/cloudflared.mdx            |    2 +-
 .../tunnel/origin-parameters.mdx              |    4 +-
 .../cloudflare-one/tunnel/package-manager.mdx |    3 +-
 .../cloudflare-one/tunnel/protocols-table.mdx |   26 +-
 .../cloudflare-one/tunnel/run-parameters.mdx  |    6 +-
 .../cloudflare-one/tunnel/tunnel-status.mdx   |   12 +-
 .../tunnel/warp-cli-target-list.mdx           |    2 +-
 .../tunnel/warp-to-tunnel-route-ips.mdx       |   66 +-
 .../warp/client-notification-lag.mdx          |    3 +-
 .../warp/client-orchestration-ips.mdx         |    1 -
 .../warp/device-enrollment-mtls.mdx           |    7 +-
 .../warp/enroll-ios-android.mdx               |    3 +-
 .../cloudflare-one/warp/ldf-best-practice.mdx |    2 +-
 .../warp/managed-networks-sha-256.mdx         |    2 +-
 .../cloudflare-one/warp/manually-reauth.mdx   |    2 +-
 .../cloudflare-one/warp/mdm-policy-file.mdx   |    9 +-
 .../cloudflare-one/warp/os-version-semver.mdx |    3 +-
 .../warp/sha-256-fingerprint.mdx              |    2 +-
 .../warp/support-ticket-best-practices.mdx    |    4 +-
 .../warp/system-requirements/linux.mdx        |   19 +-
 .../warp/system-requirements/macOS.mdx        |   19 +-
 .../warp/system-requirements/windows.mdx      |   19 +-
 .../cloudflare-one/warp/vpn-ip-traffic.mdx    |   10 +-
 .../cloudflare-one/warp/warp-modes.mdx        |    4 +-
 .../partials/containers/instance-types.mdx    |    4 +-
 .../d1/d1-do-supported-sqlite-extensions.mdx  |    4 +-
 .../partials/d1/generate-d1-api-token.mdx     |    2 +-
 .../advanced-ddos/dns-protection-intro.mdx    |    2 +-
 .../advanced-ddos/dns-setup.mdx               |    2 +-
 .../mt-advanced-ddos-systems-onboarding.mdx   |    2 +-
 .../advanced-ddos/tcp-protection-intro.mdx    |    2 +-
 .../advanced-ddos/tcp-setup.mdx               |    2 +-
 .../alerts-and-reports-independent.mdx        |    1 -
 .../ddos-protection/allowlist-ip-spoofing.mdx |    5 +-
 .../ddos-protection/atp-filter-definition.mdx |    3 +-
 .../atp-filters-rules-precedence.mdx          |    1 -
 .../ddos-protection/create-notification.mdx   |    1 -
 .../ddos-protection/ddos-attack-coverage.mdx  |   15 +-
 .../log-and-monitor-behavior-link.mdx         |    2 +-
 .../managed-rulesets/create-override.mdx      |    4 +-
 .../managed-rulesets/evaluation-behavior.mdx  |    5 +-
 .../read-only-rules-description.mdx           |    1 -
 .../managed-rulesets/read-only-rules-note.mdx |    1 -
 .../sensitivity-level-reference.mdx           |   17 +-
 .../test-rules-description.mdx                |    1 -
 .../ddos-protection/override-example.mdx      |   25 +-
 .../ddos-protection/override-logic.mdx        |    7 +-
 .../dmarc-management/domain-spoofing.mdx      |    2 -
 .../partials/dns/a-aaaa-definition.mdx        |    1 -
 src/content/partials/dns/acns-tcns-byoip.mdx  |    3 +-
 .../partials/dns/acns-tcns-conditions.mdx     |    7 +-
 src/content/partials/dns/acns-tcns-intro.mdx  |    3 +-
 .../partials/dns/aname-alias-callout.mdx      |    3 +-
 .../partials/dns/api-field-definitions.mdx    |    1 -
 src/content/partials/dns/cname-definition.mdx |    1 -
 .../partials/dns/cname-flattening-callout.mdx |    1 -
 .../conversion-subdomain-setup-callout.mdx    |    3 +-
 .../partials/dns/dns-errors-ts-action.mdx     |    3 +-
 .../partials/dns/dns-errors-ts-intro.mdx      |    5 +-
 .../partials/dns/dns-nxdomain-warning.mdx     |    5 +-
 src/content/partials/dns/dns-record-steps.mdx |   10 +-
 src/content/partials/dns/dns-scan-intro.mdx   |    1 -
 src/content/partials/dns/dns-scan-note.mdx    |    2 +-
 src/content/partials/dns/dnssec-auto-add.mdx  |    3 -
 .../partials/dns/dnssec-cloudflare-steps.mdx  |    1 -
 .../partials/dns/dnssec-definition.mdx        |    1 -
 .../partials/dns/dnssec-enabled-migration.mdx |    3 -
 .../partials/dns/dnssec-registrar-steps.mdx   |    5 +-
 .../partials/dns/export-dns-records.mdx       |    1 -
 .../partials/dns/internal-dns-beta-note.mdx   |    1 -
 .../dns/internal-dns-view-conditions.mdx      |    4 +-
 .../dns/internal-reference-zone-api.mdx       |   15 +-
 .../dns/internal-reference-zone-intro.mdx     |   11 +-
 .../dns/internal-zones-conditions.mdx         |    4 +-
 .../partials/dns/linked-peers-limit.mdx       |    1 -
 .../partials/dns/minimize-downtime-tip.mdx    |    3 +-
 .../dns/mix-proxied-and-unproxied.mdx         |    3 -
 .../partials/dns/nameserver-preamble.mdx      |    1 -
 .../dns/nameservers-registrar-callout.mdx     |    1 -
 .../partials/dns/ns-advanced-vs-custom.mdx    |    1 -
 .../partials/dns/ns-set-omission-callout.mdx  |    1 -
 src/content/partials/dns/ns-static-ips.mdx    |    3 +-
 .../partials/dns/ns-update-providers.mdx      |   71 +-
 src/content/partials/dns/onboard-warning.mdx  |    1 -
 .../partials/dns/partial-setup-definition.mdx |    3 +-
 .../dns/random-prefix-attack-definition.mdx   |    1 -
 .../partials/dns/records-name-field.mdx       |    8 +-
 .../partials/dns/recover-deleted-domain.mdx   |    1 -
 .../dns/secondary-conversion-unlink.mdx       |    3 +-
 .../partials/dns/secondary-dns-override.mdx   |    1 -
 .../partials/dns/ssltls-subdomains.mdx        |    1 -
 .../partials/dns/subdomain-customization.mdx  |    1 -
 .../partials/dns/third-party-caveat.mdx       |    5 +-
 src/content/partials/dns/tsig-create-api.mdx  |    1 -
 src/content/partials/dns/tsig-create-dash.mdx |    7 +-
 src/content/partials/dns/tsig-definition.mdx  |    3 +-
 src/content/partials/dns/tsig-name-match.mdx  |    1 -
 .../partials/dns/why-disable-dnssec.mdx       |    1 -
 .../partials/dns/zone-defaults-exceptions.mdx |    1 -
 .../partials/dns/zone-file-size-limit.mdx     |    1 -
 .../durable-objects/api-async-kv-legacy.mdx   |    4 +-
 .../durable-objects/api-storage-alarms.mdx    |    2 +-
 .../api-storage-other-methods.mdx             |    2 +-
 .../partials/durable-objects/api-sync-kv.mdx  |    2 +-
 .../do-faq-metrics-and-analytics.mdx          |    4 +-
 .../durable-objects/do-plans-note.mdx         |    2 +-
 .../durable-objects/durable-objects-sql.mdx   |  122 +-
 .../durable-objects/recommend-sqlite-do.mdx   |    2 +-
 .../what-are-durable-objects.mdx              |    2 +-
 .../email-routing-definition.mdx              |    1 -
 .../email-routing/enable-create-worker.mdx    |    1 -
 .../send-emails-workers-intro.mdx             |    3 +-
 .../partials/email-routing/types-bindings.mdx |    1 -
 .../partials/email-security/add-user.mdx      |    3 +-
 .../email-security/auto-retraction.mdx        |   18 +-
 .../bec-directory-guide-compromise-list.mdx   |    1 -
 .../bec-directory-guide-secondary-email.mdx   |    1 -
 .../email-security/contact-support.mdx        |    3 +-
 .../bcc-table-geographic-locations.mdx        |   11 +-
 .../deployment/mx-deployment-values.mdx       |    1 -
 .../deployment/mx-geographic-locations.mdx    |   19 +-
 .../email-security/deployment/o365-gcc.mdx    |    1 -
 ...-use-case-1-3-create-quarantine-policy.mdx |    6 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 .../o365-use-case-configure-domain.mdx        |   15 +-
 .../o365-use-case-transport-rules.mdx         |   41 +-
 .../deployment/setup-api-overview.mdx         |   21 +-
 .../deployment/setup-inline-overview.mdx      |   13 +-
 .../deployment/setup-overview.mdx             |    1 -
 .../email-security-description.mdx            |    3 +-
 .../email-security/outbound-email.mdx         |    1 -
 .../email-security/rename-area1-to-ces.mdx    |    1 -
 .../partials/email-security/search.mdx        |    9 +-
 .../email-security/service-addresses.mdx      |    1 -
 .../email-security/sso-enforcement.mdx        |    9 +-
 .../account-audit-logs-definition.mdx         |    3 -
 .../account-manage-active-sessions.mdx        |    3 -
 .../account-member-manage-limitation.mdx      |    1 -
 .../fundamentals/api-change-api-key.mdx       |    3 +-
 .../fundamentals/api-combine-filters.mdx      |    9 +-
 .../fundamentals/api-filter-operators.mdx     |   22 +-
 .../partials/fundamentals/api-rate-limits.mdx |   16 +-
 .../partials/fundamentals/api-using-api.mdx   |    3 -
 .../partials/fundamentals/audit-log-api.mdx   |    1 -
 .../create-account-best-practices.mdx         |    1 -
 .../cybersafe-cipa-subcategories.mdx          |   55 +-
 .../fundamentals/cybersafe-configuration.mdx  |    1 -
 .../fundamentals/cybersafe-description.mdx    |    1 -
 .../fundamentals/cybersafe-requirements.mdx   |    1 -
 .../cybersafe-school-eligibility.mdx          |    5 +-
 .../fundamentals/idp-group-deprecation.mdx    |    5 -
 .../fundamentals/lists-import-notes.mdx       |    7 +-
 .../fundamentals/new-token-warning.mdx        |    3 -
 .../fundamentals/pseudo-ipv4-warning.mdx      |    1 -
 .../fundamentals/revoke-active-sessions.mdx   |    3 +-
 .../fundamentals/ubb-recommendation.mdx       |   12 +-
 .../fundamentals/user-permissions-table.mdx   |   19 +-
 .../partials/fundamentals/user-profiles.mdx   |    3 +-
 .../partials/fundamentals/view-audit-log.mdx  |    3 -
 .../fundamentals/what-is-cloudflare.mdx       |    3 +-
 .../zero-downtime-failover-retry-on-error.mdx |    1 -
 .../hyperdrive/create-hyperdrive-binding.mdx  |    7 +-
 .../hyperdrive/create-hyperdrive-config.mdx   |    9 +-
 .../partials/hyperdrive/pooling-mode.mdx      |    1 -
 .../use-postgres-js-to-make-query.mdx         |    2 +-
 .../learning-paths/cache-basic-diagram.mdx    |    1 -
 .../learning-paths/cache-optimization.mdx     |    7 +-
 ...-network-overview-additional-resources.mdx |    3 +-
 .../china-network-overview-navigation.mdx     |   27 +-
 .../cloudflare-tunnels-origin-description.mdx |    7 +-
 .../ddos-definition-and-diagram.mdx           |    3 +-
 .../learning-paths/email-record-origin-ip.mdx |    1 -
 .../learning-paths/r2-series-navigation.mdx   |   55 +-
 .../learning-paths/sase-series-navigation.mdx |   64 +-
 .../learning-paths/warp-series-navigation.mdx |   25 +-
 .../workflows-series-navigation.mdx           |   35 +-
 .../zero-trust/blocklist-restricted-users.mdx |    3 +-
 .../blocklist-security-categories.mdx         |    1 -
 .../configure-device-agent-description.mdx    |    1 -
 .../configure-device-agent-objectives.mdx     |    9 +-
 .../zero-trust/configure-idp.mdx              |    3 +-
 .../zero-trust/connect-devices-objectives.mdx |    7 +-
 .../learning-paths/zero-trust/create-list.mdx |    3 +-
 .../device-enrollment-permissions.mdx         |    3 +-
 .../zero-trust/email-dispositions.mdx         |   15 +-
 .../zero-trust/enable-proxy-intro.mdx         |    1 -
 .../zero-trust/initial-setup-objectives.mdx   |    7 +-
 .../zero-trust/install-agent.mdx              |   26 +-
 .../learning-paths/zero-trust/mdm.mdx         |    3 +-
 .../zero-trust/split-tunnel-settings.mdx      |    7 +-
 .../validate-traffic-in-gateway.mdx           |    9 +-
 .../components-knowledge-callout.mdx          |    1 -
 .../custom-rules-definition.mdx               |    1 -
 .../dns-load-balancing-benefits.mdx           |    1 -
 .../dns-load-balancing-definition.mdx         |    1 -
 .../dns-load-balancing-limitations.mdx        |   15 +-
 .../endpoints-introduction-callout.mdx        |    1 -
 .../load-balancing/fallback-pools.mdx         |    1 -
 .../load-balancing/health-check-diagram.mdx   |    1 -
 .../load-balancing/health-check-regions.mdx   |    1 -
 .../layer-4-load-balancing-definition.mdx     |    3 -
 .../layer-7-load-balancing-benefits.mdx       |   15 +-
 .../layer-7-load-balancing-definition.mdx     |    1 -
 .../load-balancer-create-api.mdx              |  149 ++-
 .../load-balancing/load-balancer-create.mdx   |   53 +-
 .../load-balancer-definition.mdx              |    1 -
 .../load-balancing/load-balancing-diagram.mdx |    1 -
 .../load-balancing/monitor-create-api.mdx     |  105 +-
 .../load-balancing/monitor-create.mdx         |    3 +-
 .../monitor-health-check-regions-options.mdx  |    5 +-
 .../load-balancing/monitor-prepare-server.mdx |    3 -
 .../load-balancing/monitor-settings-basic.mdx |   11 +-
 .../monitor-settings-consecutive.mdx          |    3 -
 .../origin-steering-definition.mdx            |    7 +-
 .../origin-steering-policies.mdx              |    1 -
 .../origin-steering-weights-definition.mdx    |    1 -
 .../origin-steering-weights-limitations.mdx   |    1 -
 .../partials/load-balancing/pool-create.mdx   |   31 +-
 .../load-balancing/pool-health-threshold.mdx  |    3 +-
 .../load-balancing/region-mapping.mdx         |    1 -
 .../route-production-traffic.mdx              |    7 +-
 .../session-affinity-by-cookie-process.mdx    |    5 +-
 .../session-affinity-definition.mdx           |    1 -
 .../spectrum-lb-limitations.mdx               |    5 +-
 .../load-balancing/test-domain-setup.mdx      |    1 -
 .../traffic-steering-definition.mdx           |    1 -
 .../unexpected-health-statuses.mdx            |    5 +-
 .../unhealthy-pool-traffic-distribution.mdx   |   10 +-
 .../partials/logs/check-log-retention.mdx     |    1 -
 .../partials/logs/disable-log-retention.mdx   |    1 -
 .../partials/logs/enable-log-retention.mdx    |    1 -
 .../partials/logs/enable-logpush-job.mdx      |    5 +-
 .../partials/logs/enable-read-permissions.mdx |    1 -
 .../partials/logs/filtering-limitations.mdx   |    1 -
 .../account-id-api-key.mdx                    |   20 +-
 .../analytics/set-thresholds-site-health.mdx  |    2 +-
 .../analytics/site-analytics.mdx              |   43 +-
 .../cloudflare-one-connectivity-options.mdx   |   35 +-
 .../cloudflare-wan/custom-ike-id-ipsec.mdx    |   13 +-
 .../cloudflare-wan/get-started.mdx            |   12 +-
 .../cloudflare-wan/load-balancing.mdx         |    2 +-
 .../reference/device-compatibility.mdx        |   60 +-
 .../cloudflare-wan/security-filters.mdx       |    2 +-
 .../cloudflare-wan/third-party/aws.mdx        |    4 +-
 .../third-party/azure-virtual-wan.mdx         |   18 +-
 .../cloudflare-wan/third-party/fitelnet.mdx   |    1 -
 .../cloudflare-wan/third-party/fortinet.mdx   |    2 -
 .../cloudflare-wan/third-party/juniper.mdx    |  218 ++--
 .../cloudflare-wan/third-party/oracle.mdx     |   59 +-
 .../cloudflare-wan/third-party/palo-alto.mdx  |  194 +--
 .../third-party/sophos-firewall.mdx           |    1 -
 .../cloudflare-wan/third-party/velocloud.mdx  |    8 +-
 .../cloudflare-wan/third-party/viptela.mdx    |   36 +-
 .../cloudflare-wan/third-party/yamaha.mdx     |   24 +-
 .../cloudflare-wan/wan-transformation.mdx     |   24 +-
 .../cloudflare-wan/zero-trust/gateway.mdx     |   11 +-
 .../cloudflare-wan/zero-trust/overview.mdx    |    6 +-
 .../zero-trust/security-services.mdx          |   35 +-
 .../cloudflare-wan/zero-trust/tunnel.mdx      |   24 +-
 .../cloudflare-wan/zero-trust/warp.mdx        |    9 +-
 .../cni-product-use-cases.mdx                 |   15 +-
 .../query-magic-transit-bandwidth-graphql.mdx |    3 +-
 ...y-magic-transit-endpoint-health-checks.mdx |  126 +-
 .../query-magic-transit-health-checks.mdx     |    2 +-
 .../ipsec-logs-troubleshooting.mdx            |    8 +-
 .../magic-transit/advertise-prefixes.mdx      |    3 +-
 .../magic-transit/cloudflare-ips.mdx          |    8 +-
 .../mtu-mss/mss-clamping-gre.mdx              |    2 -
 .../mtu-mss/mss-clamping-ipsec.mdx            |    2 -
 .../safely-withdraw-byoip-prefix.mdx          |    8 +-
 .../networking-services/magic-user-role.mdx   |    2 +-
 .../mconn/device-metrics.mdx                  |  106 +-
 .../mconn/licence-keys.mdx                    |    4 +-
 .../mconn/maintenance/activate-connectors.mdx |    2 +-
 .../maintenance/deactivate-connector.mdx      |   42 +-
 .../mconn/maintenance/default-password.mdx    |    2 +-
 .../mconn/maintenance/edit-basic-info.mdx     |   39 +-
 .../maintenance/edit-network-settings.mdx     |   46 +-
 .../mconn/maintenance/edit-sites.mdx          |   34 +-
 .../maintenance/edit-traffic-steering.mdx     |   40 +-
 .../mconn/maintenance/heartbeat.mdx           |   45 +-
 .../maintenance/interrupt-service-window.mdx  |   47 +-
 .../register-hardware-appliance.mdx           |   37 +-
 .../mconn/maintenance/remove-connectors.mdx   |   75 +-
 .../mconn/mconn-reference.mdx                 |   17 +-
 .../breakout-prioritized.mdx                  |  262 ++--
 .../app-aware-policies/netflow.mdx            |   19 +-
 .../app-aware-policies/overview.mdx           |    5 +-
 .../mconn/network-options/dhcp/dhcp-relay.mdx |    9 +-
 .../network-options/dhcp/dhcp-server.mdx      |    9 +-
 .../mconn/network-options/nat-subnet.mdx      |    1 -
 .../network-options/network-segmentation.mdx  |    9 +-
 .../mconn/network-options/routed-subnets.mdx  |    2 +-
 .../networking-services/mconn/overview.mdx    |    2 +-
 .../mconn/troubleshooting/troubleshooting.mdx |   33 +-
 .../mconn/vlan-tagging.mdx                    |    2 +-
 .../mconn/wan-two-tunnels.mdx                 |    2 +-
 .../mnm-auto-advertisement-notifications.mdx  |    2 +-
 .../mnm-magic-transit-integration.mdx         |   10 +-
 .../partials/networking-services/mnm/faqs.mdx |    2 +-
 .../mnm/routers/sflow-config.mdx              |    2 +-
 .../mnm/rules/dynamic-threshold.mdx           |   16 +-
 .../mnm/rules/overview.mdx                    |    2 +-
 .../mnm/rules/rule-notifications.mdx          |   21 +-
 .../mnm/rules/s-flow-ddos-attack.mdx          |   16 +-
 .../mnm/rules/static-threshold.mdx            |   32 +-
 .../mnm/tutorials/graphql-analytics.mdx       |    1 -
 ...-vendor-guidelines-mss-settings-origin.mdx |    6 +-
 .../reference/longest-prefix-match.mdx        |    2 +-
 .../traffic-steering-region-codes.mdx         |   22 +-
 .../reference/tunnel-health-checks.mdx        |   23 +-
 .../routing/anycast-warning.mdx               |    2 +-
 .../routing/bgp-config-steps.mdx              |   18 +-
 .../configure-cloudflare-source-ips.mdx       |    2 +
 .../routing/mcn-cloudflare-wan-on-ramps.mdx   |   18 +-
 .../networking-services/sites/sites-brief.mdx |    2 +-
 .../networking-services/sites/sites.mdx       |  156 +--
 .../troubleshoot-connectivity.mdx             |   17 +-
 .../check-tunnel-healthchecks-dash.mdx        |  121 +-
 .../health-checks-compatible-cmb-eu.mdx       |    2 +-
 .../magic-tunnel-health-alerts.mdx            |   33 +-
 .../tunnel-health/mconn-heartbeat-health.mdx  |    2 +-
 .../troubleshoot-tunnel-health.mdx            |  146 +--
 .../virtual-networks-concept.mdx              |   39 +-
 .../partials/notifications/get-started.mdx    |    1 -
 src/content/partials/pages/c3-adapter.mdx     |    3 -
 .../pages/c3-run-command-no-directory.mdx     |    7 +-
 .../pages/cli-precedence-over-file.mdx        |    3 -
 .../partials/pages/custom-domain-steps.mdx    |    1 +
 .../pages/deploy-to-pages-steps-no-preset.mdx |    1 +
 .../deploy-to-pages-steps-with-preset.mdx     |    1 +
 src/content/partials/pages/do-note.mdx        |    1 -
 .../pages/framework-guides/create-gh-repo.mdx |    1 -
 .../create-github-repository-prefix.mdx       |    1 -
 .../framework-guides/git-integration.mdx      |    3 +-
 .../pages/framework-guides/learn-more.mdx     |    3 +-
 .../pages/get-started-git-connect-pages.mdx   |    5 +-
 .../pages/get-started-git-manage-site.mdx     |   11 +-
 .../pages/git-integration-warning.mdx         |    3 -
 .../partials/pages/prod-branch-update.mdx     |    1 -
 .../pages/tutorials-before-you-start.mdx      |    1 -
 .../partials/pages/web-analytics-setup.mdx    |    2 +-
 src/content/partials/queues/enable-queues.mdx |    2 +-
 .../event-subscriptions/access-events.mdx     |   58 +-
 .../event-subscriptions/artifacts-events.mdx  |  366 +++---
 .../queues/event-subscriptions/kv-events.mdx  |   56 +-
 .../queues/event-subscriptions/r2-events.mdx  |   60 +-
 .../super-slurper-events.mdx                  |  202 +--
 .../event-subscriptions/vectorize-events.mdx  |   62 +-
 .../event-subscriptions/workers-ai-events.mdx |   90 +-
 .../workers-builds-events.mdx                 |  264 ++--
 .../event-subscriptions/workflows-events.mdx  |  180 +--
 .../partials/r2/custom-domain-steps.mdx       |    1 +
 .../partials/r2/link-to-workers-r2-api.mdx    |    2 +-
 .../partials/r2/migrator-etag-caveat.mdx      |    3 +-
 .../common/create-your-own-ui-examples.mdx    |    5 +-
 .../common/default-meeting-examples.mdx       |    5 +-
 .../web/breakout-room-close-breakout.mdx      |   13 +-
 .../web/breakout-room-creation-sdk-api.mdx    |   17 +-
 .../breakout-room-fetch-meetings-sdk-api.mdx  |   14 +-
 .../breakout-room-handle-breakout-events.mdx  |   11 +-
 ...breakout-room-move-participant-sdk-api.mdx |   19 +-
 ...t-room-move-preset-participant-sdk-api.mdx |   15 +-
 .../web/breakout-room-permission-check.mdx    |   16 +-
 .../realtimekit/web/language-pack-json.mdx    |  822 ++++++------
 .../description-of-design-guides.mdx          |    1 -
 ...scription-of-ref-architecture-diagrams.mdx |    1 -
 .../description-of-ref-architectures.mdx      |    1 -
 .../what-is-cloudflare-link.mdx               |    3 +-
 .../partials/registrar/email-verification.mdx |    3 -
 .../partials/registrar/enable-dnssec.mdx      |    3 +-
 .../registrar/icann-unverified-email.mdx      |    3 +-
 .../partials/registrar/requirements.mdx       |    1 -
 .../partials/registrar/restrictions.mdx       |   12 +-
 .../partials/registrar/verify-dnssec.mdx      |    1 -
 .../configuration-rule-link-to-examples.mdx   |    1 -
 .../rules/configuration-rule-promotion.mdx    |    3 -
 .../partials/rules/error-pages-list.mdx       |    1 -
 .../partials/rules/page-rules-migration.mdx   |    1 -
 .../rules/rules-creation-workflow.mdx         |    1 -
 .../partials/rules/rules-templates.mdx        |    6 +-
 .../rules/terraform-additional-resources.mdx  |    5 +-
 .../rules/transform/header-valid-names.mdx    |    5 +-
 .../rules/transform/header-valid-values.mdx   |    5 +-
 .../ruleset-engine/max-expression-length.mdx  |    1 -
 .../ruleset-engine/rule-position-values.mdx   |    7 +-
 .../brand-protection-alerts.mdx               |    1 -
 .../brand-protection-definition.mdx           |    3 +-
 .../security-center/scan-frequency.mdx        |    3 +-
 .../security-center/scan-properties.mdx       |    9 +-
 .../security-insights-definition.mdx          |    1 -
 .../partials/smart-shield/argo-analytics.mdx  |    2 +-
 .../partials/smart-shield/argo-intro.mdx      |    2 +-
 .../concurrent-connections-explainer.mdx      |    2 +-
 .../smart-shield/dcei-pool-requirements.mdx   |    2 +-
 .../smart-shield/health-checks-analytics.mdx  |    2 +-
 .../smart-shield/health-checks-intro.mdx      |    2 +-
 .../smart-shield/health-checks-regions.mdx    |    4 +-
 .../smart-shield/smart-shield-callout.mdx     |    2 +-
 .../partials/smart-shield/zone-lockdown.mdx   |    2 +-
 .../spectrum-with-load-balancer-api.mdx       |   63 +-
 .../spectrum-with-load-balancer-dash.mdx      |    3 +-
 .../partials/speed/rocket-loader-csp.mdx      |    3 +-
 src/content/partials/speed/user-agents.mdx    |   10 +-
 .../ssl/acm-ca-hostnames-conditions.mdx       |    1 -
 src/content/partials/ssl/acm-definition.mdx   |    1 -
 .../partials/ssl/acm-validate-cert.mdx        |    5 +-
 .../ssl/aop-per-hostname-upload-cert.mdx      |    3 +-
 .../partials/ssl/caa-records-added-by-cf.mdx  |    3 +-
 .../partials/ssl/caa-records-definition.mdx   |    1 -
 .../ssl/change-encryption-mode-api.mdx        |    1 -
 .../ssl/change-encryption-mode-dash.mdx       |    1 -
 .../ssl/cipher-suites-api-linkout.mdx         |    3 +-
 .../partials/ssl/cipher-suites-definition.mdx |    1 -
 .../ssl/cipher-suites-saas-linkout.mdx        |    3 +-
 .../ssl/ciphers-api-general-notes.mdx         |    2 +-
 .../partials/ssl/cname-cert-verification.mdx  |    1 -
 src/content/partials/ssl/csr-definition.mdx   |    1 -
 .../partials/ssl/custom-cert-ciphers.mdx      |    7 +-
 .../ssl/custom-cert-openssl-commands.mdx      |    1 -
 .../ssl/custom-certificates-definition.mdx    |    1 -
 .../custom-origin-trust-store-definition.mdx  |    1 -
 .../partials/ssl/dcv-certificate-renewal.mdx  |    9 +-
 .../partials/ssl/dcv-conflicting-records.mdx  |    3 +-
 src/content/partials/ssl/dcv-definition.mdx   |    1 -
 .../ssl/dcv-invalid-token-situations.mdx      |    1 -
 .../partials/ssl/dcv-path-security.mdx        |    1 -
 .../partials/ssl/dcv-renewal-fallback.mdx     |    1 -
 .../partials/ssl/dcv-validate-patch.mdx       |    1 -
 .../ssl/encryption-mode-definition.mdx        |    1 -
 .../ssl/enforce-https-recommendation.mdx      |    1 -
 .../partials/ssl/error-rate-limiting.mdx      |    1 -
 .../ssl/generic-validation-process.mdx        |    1 -
 .../partials/ssl/geokey-manager-v1.mdx        |    1 -
 .../ssl/get-started-additional-features.mdx   |    7 +-
 .../ssl/http-cname-validation-process.mdx     |    1 -
 .../partials/ssl/http-to-txt-schedule.mdx     |    3 +-
 .../partials/ssl/keyless-ssl-definition.mdx   |    1 -
 .../partials/ssl/keyless-tunnel-setup.mdx     |    1 -
 .../partials/ssl/keyless-upload-preamble.mdx  |    1 -
 .../partials/ssl/origin-ca-pause-error.mdx    |    3 +-
 .../ssl/partial-zone-acm-dcv-nonwildcard.mdx  |    8 +-
 .../ssl/partial-zone-acm-dcv-wildcard.mdx     |    5 +-
 src/content/partials/ssl/ssl-mode-errors.mdx  |    1 -
 src/content/partials/ssl/ssl-mode-no-aop.mdx  |    1 -
 .../ssl/ssl-recommender-post-setup.mdx        |    3 +-
 .../partials/ssl/ssl-recommender-prereqs.mdx  |    7 +-
 src/content/partials/ssl/test-tls-version.mdx |    3 +-
 .../ssl/tls-1.3-cipher-limitations.mdx        |    1 -
 .../ssl/total-tls-character-limitation.mdx    |    3 +-
 .../partials/ssl/txt-validation-api.mdx       |   53 +-
 .../partials/ssl/txt-validation-dashboard.mdx |    1 -
 .../ssl/txt-validation-definition.mdx         |    1 -
 .../partials/ssl/txt-validation-preamble.mdx  |    1 -
 .../ssl/universal-ssl-enable-full.mdx         |    1 -
 .../partials/ssl/universal-ssl-validity.mdx   |    3 +-
 .../ssl/ussl-limitations-solutions.mdx        |    7 +-
 .../partials/ssl/ussl-limitations-table.mdx   |    1 -
 .../partials/ssl/validation-level-note.mdx    |    1 -
 .../stream/android_playback_code_snippet.mdx  |    1 -
 .../stream/chromecast_limitations.mdx         |    1 -
 .../stream/ios_playback_code_snippet.mdx      |    1 -
 src/content/partials/stream/prereqs.mdx       |    3 -
 .../prereqs_first_start_live_streaming.mdx    |    3 -
 .../partials/stream/srt-supported-modes.mdx   |    3 -
 .../directory-listing-definition.mdx          |    2 +-
 src/content/partials/style-guide/icons.mdx    |    2 +-
 .../style-guide/public-stats-definition.mdx   |    2 +-
 .../partials/style-guide/tab-guidance.mdx     |    4 +-
 .../partials/style-guide/table-guidelines.mdx |    2 +-
 src/content/partials/support/2fa-enable.mdx   |    1 -
 src/content/partials/support/2fa-overview.mdx |    1 -
 .../partials/tenant/account-definition.mdx    |    1 -
 .../tenant/account-details-preamble.mdx       |    1 -
 .../partials/tenant/account-details.mdx       |   23 +-
 .../partials/tenant/account-preamble.mdx      |    1 -
 .../partials/tenant/create-account-api.mdx    |   70 +-
 .../partials/tenant/create-account-dash.mdx   |    1 -
 .../tenant/create-account-subscription.mdx    |   20 +-
 .../tenant/create-zone-subscription.mdx       |   24 +-
 .../partials/tenant/resource-definition.mdx   |    1 -
 .../tenant/tenant-admin-definition.mdx        |    1 -
 .../partials/tenant/tenant-definition.mdx     |    1 -
 .../tenant/tenant-details-preamble.mdx        |    1 -
 .../partials/tenant/tenant-details.mdx        |    5 -
 .../partials/tenant/user-definition.mdx       |    1 -
 .../partials/terraform/create-r2-buckets.mdx  |    1 -
 .../terraform/find-ids-managed-rulesets.mdx   |    5 +-
 src/content/partials/terraform/find-ids.mdx   |    5 +-
 .../import-delete-existing-rulesets.mdx       |    5 +-
 .../partials/terraform/v4-code-snippets.mdx   |    3 +-
 .../partials/terraform/v5-code-snippets.mdx   |    1 -
 .../partials/time-services/ntp-definition.mdx |    1 -
 .../partials/turnstile/challenge-behavior.mdx |    1 -
 .../partials/turnstile/privacy-policy.mdx     |    2 +-
 .../partials/turnstile/proxied-hostnames.mdx  |    1 -
 .../turnstile/security-requirements.mdx       |    2 -
 .../partials/turnstile/siteverify-warning.mdx |    1 -
 src/content/partials/turnstile/siteverify.mdx |    3 +-
 .../partials/turnstile/test-secret-key.mdx    |    3 +-
 .../partials/turnstile/test-sitekey.mdx       |    3 +-
 .../turnstile/troubleshooting-steps.mdx       |   21 +-
 .../partials/turnstile/widget-components.mdx  |   11 +-
 .../partials/vectorize/vectorize-ga.mdx       |    3 -
 .../partials/vectorize/vectorize-pricing.mdx  |    8 +-
 .../create-environment-situation.mdx          |    1 -
 .../version-management/edit-version.mdx       |    7 +-
 .../enable-default-creation.mdx               |    7 +-
 .../version-management/enable-versioning.mdx  |    5 +-
 .../environment-defaults.mdx                  |    7 +-
 .../environment-definition.mdx                |    1 -
 .../production-read-only-default.mdx          |    1 -
 .../version-management/promote-version.mdx    |    4 +-
 .../version-management/test-version.mdx       |    3 +-
 .../version-management/version-definition.mdx |    1 -
 .../waf/api-create-ruleset-with-rule.mdx      |    1 -
 src/content/partials/waf/list-advantages.mdx  |    7 +-
 src/content/partials/waf/managed-lists.mdx    |    4 +-
 .../waf/open-ports-blocked-traffic.mdx        |    1 -
 .../waf/rate-limiting-best-practices.mdx      |   11 +-
 .../waf/rate-limiting-rule-parameters.mdx     |   15 +-
 .../partials/waf/rules-next-steps-table.mdx   |    6 +-
 .../waiting-room/change-queueing-method.mdx   |    7 +-
 .../partials/waiting-room/queue-all.mdx       |    1 -
 .../partials/waiting-room/queue-some.mdx      |    1 -
 .../partials/warp-client/modes-options.mdx    |   13 +-
 .../web-analytics-definition.mdx              |    1 -
 .../web-analytics-notifications.mdx           |    1 -
 .../web-analytics-proxied-setup.mdx           |    1 -
 .../web-analytics-troubleshooting.mdx         |    3 -
 .../partials/web3/cloudflare-settings.mdx     |    1 -
 .../partials/web3/create-gateway-api.mdx      |   31 +-
 .../partials/web3/pricing-page-reference.mdx  |    3 -
 .../workers-ai/custom_requirements.mdx        |    3 -
 .../partials/workers-ai/file_issues.mdx       |    3 -
 .../workers-ai/openai-compatibility.mdx       |    1 -
 .../workers-vpc/create-tunnel-steps.mdx       |    2 +-
 .../partials/workers-vpc/required-roles.mdx   |    1 -
 .../workers/ai-local-usage-charges.mdx        |    3 -
 .../partials/workers/c3-definition.mdx        |    1 -
 .../partials/workers/compute-per-request.mdx  |    3 +-
 .../workers/content_and_contentoptions.mdx    |    3 -
 .../workers/dash-creation-next-steps.mdx      |    1 +
 .../partials/workers/env_and_secrets.mdx      |    1 -
 .../partials/workers/envvar-example.mdx       |    1 -
 .../workers/fetch-html-example-js.mdx         |   15 +-
 .../partials/workers/get-started-dash.mdx     |    3 +-
 .../workers/isolate-cpu-flexibility.mdx       |    1 -
 .../partials/workers/isolate-description.mdx  |    1 -
 .../partials/workers/limits_increase.mdx      |    3 -
 .../partials/workers/nodejs-compat-howto.mdx  |    2 -
 .../partials/workers/playground-callout.mdx   |    3 -
 src/content/partials/workers/prereqs.mdx      |    8 +-
 .../partials/workers/redirect-example-js.mdx  |   11 +-
 .../partials/workers/remote-binding-note.mdx  |    2 +-
 .../workers/request-dot-clone-warning.mdx     |    2 +-
 .../respond-another-site-example-js.mdx       |   27 +-
 .../workers/return-html-example-js.mdx        |   17 +-
 .../workers/return-json-example-js.mdx        |   13 +-
 .../workers/service-binding-rpc-example.mdx   |    1 -
 .../workers/storage-products-table.mdx        |   22 +-
 .../workers/testing-pages-functions.mdx       |    3 -
 .../workers/tutorials-before-you-start.mdx    |    1 -
 .../partials/workers/workers_logs_pricing.mdx |   11 +-
 .../workers/wrangler-commands/containers.mdx  |   16 +-
 .../workers/wrangler-commands/r2-sql.mdx      |   11 +-
 .../partials/workers/wrangler-commands/r2.mdx |   98 +-
 .../workflows/workflows-type-parameters.mdx   |    3 +-
 .../partials/zaraz/zaraz-definition.mdx       |    1 -
 src/pages/agent-setup/index.astro             |   49 +-
 src/pages/plans.astro                         |    4 +-
 3654 files changed, 33816 insertions(+), 34089 deletions(-)

diff --git a/.agents/references/procedures.md b/.agents/references/procedures.md
index b335d124dc55fb0..04454ac541394b5 100644
--- a/.agents/references/procedures.md
+++ b/.agents/references/procedures.md
@@ -11,10 +11,7 @@ Wrap all multi-step procedures in the `Steps` component:
 ```mdx
 import { Steps } from "~/components";
 
-<Steps>
-1. Step one
-2. Step two
-</Steps>
+<Steps>1. Step one 2. Step two</Steps>
 ```
 
 Single-step procedures: fold the step into the introductory sentence rather than making a one-item list.
@@ -26,14 +23,17 @@ Sub-steps use lowercase letters (a, b, c). Sub-sub-steps use lowercase Roman num
 ## Writing rules
 
 **Order**: state location before action, purpose before action.
+
 - "In the **DNS** section, select **Add record**." (location → action)
 - "To delete the rule, select **Delete**." (purpose → action)
 
 **First step**: consolidate login and navigation. Do not make "Log in" its own step if the next step is navigating somewhere.
+
 - "Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **DNS** > **Records**."
 - Write "log in to" (three words), not "log into".
 
 **Optional steps**: prefix with `(Optional)` as the first word.
+
 - "(Optional) Enter a description for the rule."
 
 **Enter key**: if the user must press **Enter** after a step, include it in that step.
@@ -62,10 +62,10 @@ Provide a screenshot when the UI element is genuinely hard to locate without one
 
 ## Terminology in procedures
 
-| Use | Not |
-| --- | --- |
-| select | click |
-| go to | navigate to |
+| Use                | Not              |
+| ------------------ | ---------------- |
+| select             | click            |
+| go to              | navigate to      |
 | turn on / turn off | enable / disable |
-| log in to | log into |
-| (Optional) | Optional: |
+| log in to          | log into         |
+| (Optional)         | Optional:        |
diff --git a/.agents/skills/dependabot-review/SKILL.md b/.agents/skills/dependabot-review/SKILL.md
index 9ad186440519dd9..1b684c642fe06e3 100644
--- a/.agents/skills/dependabot-review/SKILL.md
+++ b/.agents/skills/dependabot-review/SKILL.md
@@ -62,7 +62,7 @@ grep -r "require(['\"]<package>['\"]" src/ worker/ bin/ -l
 grep '"<package>"' package.json
 
 # If transitive, who pulls it in?
-node -e "const lock = require('./pnpm-lock.yaml'); ..." 
+node -e "const lock = require('./pnpm-lock.yaml'); ..."
 # or just:
 grep -A2 '"<package>"' pnpm-lock.yaml | grep -v "^--$" | head -20
 ```
@@ -79,6 +79,7 @@ grep -r "<method_name>\|<export_name>" src/ worker/ bin/ --include="*.ts" --incl
 ```
 
 For Astro/MDX source files under `src/content/docs/`, map them to their route:
+
 - `src/content/docs/workers/get-started/index.mdx` → `/workers/get-started/`
 - `src/content/docs/pages/platform/limits.mdx` → `/pages/platform/limits/`
 
@@ -88,13 +89,13 @@ If more than ~5 files use the changed API, list a representative sample (pick th
 
 Rate the probability that this bump causes a **visible change to the docs site**:
 
-| Rating | Meaning |
-|--------|---------|
-| **None** | Package not used directly; transitive only; or only internal/type changes |
-| **Very Low** | Direct dependency, but changed APIs are not called in this repo |
-| **Low** | Changed APIs are called, but only in build tooling (not runtime or content rendering) |
-| **Medium** | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
-| **High** | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior |
+| Rating       | Meaning                                                                                       |
+| ------------ | --------------------------------------------------------------------------------------------- |
+| **None**     | Package not used directly; transitive only; or only internal/type changes                     |
+| **Very Low** | Direct dependency, but changed APIs are not called in this repo                               |
+| **Low**      | Changed APIs are called, but only in build tooling (not runtime or content rendering)         |
+| **Medium**   | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
+| **High**     | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior       |
 
 For **security fixes**: note what the vulnerability affects and whether our usage is in the vulnerable code path.
 
@@ -142,5 +143,6 @@ For grouped PRs (non-major group), the PR body lists each package separately. Pr
 ### Packages with no public changelog
 
 If a package has no changelog and the upstream repo is private or unavailable:
+
 1. Check npm for version diff: `npm diff <package>@<old> <package>@<new>`
 2. If that also fails, note it explicitly and rate impact conservatively based on usage alone.
diff --git a/.agents/skills/docs-review/SKILL.md b/.agents/skills/docs-review/SKILL.md
index 4f37fbdb5b612a6..7ba37ceae99136b 100644
--- a/.agents/skills/docs-review/SKILL.md
+++ b/.agents/skills/docs-review/SKILL.md
@@ -150,19 +150,19 @@ Read full files for context — code that looks wrong in a diff may be correct i
 
 See `.agents/references/style-guide.md` for the full rules. Quick reference:
 
-| Rule                     | Detail                                                                                               |
-| ------------------------ | ---------------------------------------------------------------------------------------------------- |
-| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                          |
-| Component imports        | Every component used must be imported from `~/components`                                            |
-| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                              |
-| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                     |
-| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                     |
-| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                          |
-| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs    |
-| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                         |
-| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc.    |
-| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                     |
-| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover    |
+| Rule                     | Detail                                                                                            |
+| ------------------------ | ------------------------------------------------------------------------------------------------- |
+| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                       |
+| Component imports        | Every component used must be imported from `~/components`                                         |
+| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                           |
+| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                  |
+| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                  |
+| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                       |
+| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs |
+| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                      |
+| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc. |
+| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                  |
+| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover |
 
 ### 3. Assess What to Flag
 
diff --git a/.agents/skills/eli5/SKILL.md b/.agents/skills/eli5/SKILL.md
index 47c5f5e78f0cc91..3158464814dc939 100644
--- a/.agents/skills/eli5/SKILL.md
+++ b/.agents/skills/eli5/SKILL.md
@@ -67,7 +67,7 @@ Use this skill for content that targets a broad or mixed audience — not every
 
 - **Developer-focused API and SDK references** (e.g. Workers, D1, R2, Durable Objects, KV) — the audience is developers who are expected to know programming concepts, database terminology, and API conventions
 - **Code-heavy tutorials targeting developers** — readers self-select into these and already have the prerequisite knowledge
-- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon *is* the content
+- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon _is_ the content
 
 **Use your judgment for everything else.** Ask: "Would a reasonable reader of this page already know these terms?" If yes, this skill adds little value. On the other hand, if the following are true, this skill could provide significant value.
 
@@ -105,13 +105,13 @@ I read the file, detect sections, analyze organization, and identify the content
 
 After detection, I ask you to confirm the content type. Different types require different strategies:
 
-| Type | Strategy |
-|------|----------|
-| Overview | Problem → Solution → Benefit |
-| Concept | Analogy → Plain explanation → Technical details |
-| How To | Context → Multi-path steps (Dashboard + API) |
+| Type      | Strategy                                         |
+| --------- | ------------------------------------------------ |
+| Overview  | Problem → Solution → Benefit                     |
+| Concept   | Analogy → Plain explanation → Technical details  |
+| How To    | Context → Multi-path steps (Dashboard + API)     |
 | Reference | Use-case organization with two-tier descriptions |
-| Tutorial | Progressive complexity with code explanations |
+| Tutorial  | Progressive complexity with code explanations    |
 
 **3. Apply Enhancement Constraints**
 
@@ -225,7 +225,7 @@ These are the highest-risk categories when documentation has been simplified. Pr
 
 1. **Simplified mechanism descriptions** — Any "how it works" explanation added during simplification that was not in the original. These carry the highest risk: a plausible-sounding explanation that describes the wrong mechanism is worse than the original jargon. Verify the actual mechanism against the source docs in this repository.
 
-2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies *where* crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
+2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies _where_ crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
 
 3. **Net-new claims** — Any explanation, context, or framing added during simplification that was not present in the original document. Every piece of new information requires a citation. If the original said "zones pair with resolver policies" and the simplification adds "based on source IP, user identity, or domain," verify that all three of those selectors are actually supported.
 
@@ -249,12 +249,12 @@ These are the highest-risk categories when documentation has been simplified. Pr
    - **low** — Claim is minor or widely accepted common knowledge.
 5. **Report** — Present findings in this format:
 
-| # | Claim (exact text) | Source | Status |
-|---|---|---|---|
-| 1 | "Workers KV supports keys up to 512 bytes" | `src/content/docs/kv/api/write-key-value-pairs.mdx` | ✅ sourced |
-| 2 | "Latency is under 50 ms globally" | — | ❌ unsourced (high) |
-| 3 | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
-| 4 | "zones pair with resolver policies" | present in original — `path/to/file.mdx:34` | ✅ sourced (original) |
+| #   | Claim (exact text)                                  | Source                                                                                          | Status                   |
+| --- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------ |
+| 1   | "Workers KV supports keys up to 512 bytes"          | `src/content/docs/kv/api/write-key-value-pairs.mdx`                                             | ✅ sourced               |
+| 2   | "Latency is under 50 ms globally"                   | —                                                                                               | ❌ unsourced (high)      |
+| 3   | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
+| 4   | "zones pair with resolver policies"                 | present in original — `path/to/file.mdx:34`                                                     | ✅ sourced (original)    |
 
 ### Rules
 
@@ -397,10 +397,12 @@ Produce output following this template exactly. All sections are required.
 ## Simplification Overview
 
 **What was confusing:**
+
 - [Issue pattern 1]
 - [Issue pattern 2]
 
 **Approach taken:**
+
 - [Strategy 1]
 - [Strategy 2]
 
@@ -409,14 +411,17 @@ Produce output following this template exactly. All sections are required.
 ## Section: [Original Heading]
 
 ### Original Content
+
 [Exact text from source, preserved]
 
 ### Issues Identified
+
 **Jargon:** [terms and why problematic]
 **Assumptions:** [unstated prerequisites]
 **Unclear Logic:** [structural issues]
 
 ### Simplified Version
+
 **In Plain Language:** [One-sentence distillation]
 **What It Is:** [2-3 paragraphs building from basics]
 **Why It Matters:** [Benefits and value]
@@ -434,9 +439,9 @@ Produce output following this template exactly. All sections are required.
 
 ## Terminology Index
 
-| Term | Line | Defined? | Suggested Action |
-| ---- | ---- | -------- | ---------------- |
-| [term] | [line number] | Yes/No | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
+| Term   | Line          | Defined? | Suggested Action                                                        |
+| ------ | ------------- | -------- | ----------------------------------------------------------------------- |
+| [term] | [line number] | Yes/No   | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
 
 ---
 
@@ -449,9 +454,9 @@ Produce output following this template exactly. All sections are required.
 
 Line-numbered recommendations for further improvements:
 
-| Line(s) | Current Approach | Suggested Enhancement | Why | Priority |
-| ------- | ---------------- | --------------------- | --- | -------- |
-| [lines] | [what exists] | [what to change] | [why it improves accessibility] | High/Medium/Low |
+| Line(s) | Current Approach | Suggested Enhancement | Why                             | Priority        |
+| ------- | ---------------- | --------------------- | ------------------------------- | --------------- |
+| [lines] | [what exists]    | [what to change]      | [why it improves accessibility] | High/Medium/Low |
 ```
 
 ## References
diff --git a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
index 6d9e9f57671e88a..a81b5834b7aae6c 100644
--- a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
+++ b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
@@ -193,6 +193,7 @@ For detailed step-by-step setup instructions, see the [Get started guide](/dns/i
 This overview was enhanced with inline context explaining when you'd use Internal DNS, step-by-step query flow showing how views work, and three detailed use case examples with real-world scenarios. Added explanations of key concepts (views, zone referencing, privacy model) and a "Getting started" checklist.
 
 **What was added:**
+
 - Opening context: When to use Internal DNS with concrete example (lines 34-36)
 - Architecture explanations: On-ramp options, why zones are private (lines 42-44, 48-50)
 - Views explanation: Why views matter and how they enable customization (lines 73-75)
diff --git a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
index 742a86dc6ee14df..4d1539a961ee745 100644
--- a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
+++ b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
@@ -26,6 +26,7 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Purpose:** Help users quickly understand what a product/feature is and decide if they need it.
 
 **Required Elements:**
+
 - Opening benefit statement (what problem this solves)
 - Problem/Solution/Benefit structure
 - "Perfect for" self-identification section
@@ -33,6 +34,7 @@ Once content type is detected and validated, I apply type-specific simplificatio
 - Technical architecture separated to bottom
 
 **Analysis Focus:**
+
 - Does opening paragraph answer "what" and "why"?
 - Are features explained with benefits, not just descriptions?
 - Is there a clear call-to-action?
@@ -49,32 +51,36 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Pattern Example:**
 
 ❌ **Before (Technical-first):**
+
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 
-isolates for serverless code execution with sub-millisecond cold 
+Product X is a distributed edge computing platform utilizing V8
+isolates for serverless code execution with sub-millisecond cold
 start performance.
 
 Features:
+
 - Global anycast network deployment
 - Automatic scaling and load distribution
 - Pay-per-request pricing model
 ```
 
 ✅ **After (Benefit-first):**
+
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, 
+Run code worldwide without managing servers. Deploy in seconds,
 scale automatically, pay only for what you use.
 
 **What problem it solves:**
-Maintaining global infrastructure is expensive and complex. Product X 
-runs your code in 300+ cities automatically, handling all the 
+Maintaining global infrastructure is expensive and complex. Product X
+runs your code in 300+ cities automatically, handling all the
 infrastructure for you.
 
 **Perfect for:**
+
 - Applications needing fast global performance
 - Teams wanting to skip server management
 - Projects with variable traffic (scale from zero to millions)
@@ -83,7 +89,7 @@ infrastructure for you.
 
 ---
 
-**For technical users:** Built on V8 isolates with global anycast 
+**For technical users:** Built on V8 isolates with global anycast
 deployment. [Architecture details →]
 ```
 
@@ -94,6 +100,7 @@ deployment. [Architecture details →]
 **Purpose:** Build understanding of WHY something works the way it does.
 
 **Required Elements:**
+
 - Opening analogy or visual (accessible to all)
 - Plain language definition
 - "Why it matters" business value
@@ -102,6 +109,7 @@ deployment. [Architecture details →]
 - Technical details for advanced users (separated)
 
 **Analysis Focus:**
+
 - Is there an analogy early in the content?
 - Does it explain WHY before HOW?
 - Are use cases concrete and realistic?
@@ -118,47 +126,51 @@ deployment. [Architecture details →]
 **Pattern Example:**
 
 ❌ **Before (Technical-only):**
+
 ```markdown
 ## Rate Limiting
 
-Rate limiting implements token bucket algorithms to control request 
-throughput based on configurable parameters including burst size and 
+Rate limiting implements token bucket algorithms to control request
+throughput based on configurable parameters including burst size and
 refill rate. Requests exceeding limits receive 429 status codes.
 ```
 
 ✅ **After (Layered explanation):**
+
 ```markdown
 ## Rate Limiting
 
-**Think of it like:** A nightclub with maximum capacity. Even if 
-1,000 people want to enter at once, you only let a controlled number 
+**Think of it like:** A nightclub with maximum capacity. Even if
+1,000 people want to enter at once, you only let a controlled number
 in at a time to keep things manageable.
 
 **What it is:**
-Rate limiting controls how many requests can hit your website in a 
-given time period. Without it, a sudden spike—whether from real 
+Rate limiting controls how many requests can hit your website in a
+given time period. Without it, a sudden spike—whether from real
 users or attackers—could overwhelm your server.
 
 **Why you need it:**
+
 - Prevents DDoS attacks from taking your site down
 - Stops bots from scraping your content
 - Ensures fair usage across all users
 - Keeps infrastructure costs predictable
 
 **How it works:**
-You set a rule like "100 requests per minute per IP address." When 
-someone exceeds this limit, we block additional requests until the 
+You set a rule like "100 requests per minute per IP address." When
+someone exceeds this limit, we block additional requests until the
 time window resets.
 
 **Real scenarios:**
+
 - E-commerce site during Black Friday preventing bot purchases
 - API preventing scraping of product catalog
 - Forum preventing spam post flooding
 
 ---
 
-**For technical users:** Implements token bucket algorithm with 
-configurable burst size and refill rates. Returns 429 status with 
+**For technical users:** Implements token bucket algorithm with
+configurable burst size and refill rates. Returns 429 status with
 Retry-After header. [Implementation details →]
 ```
 
@@ -169,6 +181,7 @@ Retry-After header. [Implementation details →]
 **Purpose:** Help users successfully accomplish specific tasks.
 
 **Required Elements:**
+
 - Context (what this accomplishes, why you'd do it)
 - Prerequisites listed upfront
 - Expected outcome stated
@@ -179,6 +192,7 @@ Retry-After header. [Implementation details →]
 - Common issues and troubleshooting
 
 **Analysis Focus:**
+
 - Is context provided before steps?
 - Are prerequisites clearly stated?
 - Is there both a Dashboard and API path?
@@ -197,6 +211,7 @@ Retry-After header. [Implementation details →]
 **Pattern Example:**
 
 ❌ **Before (Steps-only):**
+
 ```markdown
 ## Enable Feature
 
@@ -207,16 +222,17 @@ Retry-After header. [Implementation details →]
 ```
 
 ✅ **After (Contextual multi-path):**
-```markdown
+
+````markdown
 ## Enable Feature
 
-**What this does:** Protects your site from [specific threat] by 
+**What this does:** Protects your site from [specific threat] by
 [specific mechanism].
 
 **Time required:** ~2 minutes  
 **Prerequisites:** Admin access to your account
 
-**What happens:** After enabling, all incoming requests will be 
+**What happens:** After enabling, all incoming requests will be
 [specific behavior]. You'll see results in Analytics within 5 minutes.
 
 ### Via Dashboard
@@ -227,7 +243,7 @@ Retry-After header. [Implementation details →]
 4. Find **Feature Name** and toggle it **On**
 5. Click **Save Changes**
 
-💡 **Note:** Changes take effect immediately, but analytics may take 
+💡 **Note:** Changes take effect immediately, but analytics may take
 5 minutes to update.
 
 ### Via API
@@ -240,15 +256,17 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_enabled": true}'
 ```
+````
 
 **Response:**
+
 ```json
 {
-  "success": true,
-  "result": {
-    "feature_enabled": true,
-    "updated_at": "2026-02-09T10:30:00Z"
-  }
+	"success": true,
+	"result": {
+		"feature_enabled": true,
+		"updated_at": "2026-02-09T10:30:00Z"
+	}
 }
 ```
 
@@ -266,9 +284,10 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 ## Troubleshooting
 
 **Problem:** Feature doesn't seem to be active  
-**Solution:** Clear your browser cache and wait 5 minutes for 
+**Solution:** Clear your browser cache and wait 5 minutes for
 propagation. Still not working? Check that [prerequisite].
-```
+
+````
 
 ---
 
@@ -304,19 +323,20 @@ propagation. Still not working? Check that [prerequisite].
 ```markdown
 ## Cache Headers
 
-**Cache-Control:** Controls caching. Values: public, private, 
+**Cache-Control:** Controls caching. Values: public, private,
 no-cache, max-age=seconds
 
 **Expires:** HTTP date for expiration
 
 **Pragma:** Legacy directive. Value: no-cache
-```
+````
 
 ✅ **After (Use-case organized with examples):**
-```markdown
+
+````markdown
 ## Cache Headers Reference
 
-**When to use:** Control how long content stays cached and who can 
+**When to use:** Control how long content stays cached and who can
 cache it.
 
 ### Common Scenarios
@@ -335,17 +355,19 @@ cache it.
 
 **What it does:** Caches content for 1 year before checking for updates
 
-**When to use:** Files that never change, like `logo-v2.png` or 
+**When to use:** Files that never change, like `logo-v2.png` or
 `style.abc123.css` with version hash in filename
 
 **Technical spec:** Integer, seconds. Range: 0-31536000 (1 year max)
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
+````
 
-**Result:** First visitor downloads the file. For the next year, all 
+**Result:** First visitor downloads the file. For the next year, all
 visitors get the cached version with zero origin requests.
 
 ---
@@ -354,17 +376,18 @@ visitors get the cached version with zero origin requests.
 
 **What it does:** Tells browsers this file will literally never change
 
-**When to use:** Combine with `max-age` for versioned assets 
+**When to use:** Combine with `max-age` for versioned assets
 (filename includes hash/version number)
 
 **Technical spec:** No value. Presence activates directive.
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
 
-**Result:** Browsers won't revalidate even on refresh. Perfect for 
+**Result:** Browsers won't revalidate even on refresh. Perfect for
 `style.abc123.css` where hash changes when content changes.
 
 ---
@@ -375,17 +398,18 @@ Cache-Control: public, max-age=31536000, immutable
 
 **What it does:** Caches content for 1 hour
 
-**When to use:** Content that updates occasionally but doesn't need 
+**When to use:** Content that updates occasionally but doesn't need
 to be real-time, like blog posts or product pages
 
 **Technical spec:** Integer, seconds
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=3600
 ```
 
-**Result:** Content stays cached for 1 hour. After expiration, next 
+**Result:** Content stays cached for 1 hour. After expiration, next
 request checks origin for updates.
 
 ---
@@ -394,17 +418,18 @@ request checks origin for updates.
 
 **What it does:** Always check with origin before using cached version
 
-**When to use:** Content that changes frequently but can still be 
+**When to use:** Content that changes frequently but can still be
 cached briefly (shopping cart, personalized pages)
 
 **Technical spec:** No value. Presence activates.
 
 **Example:**
+
 ```http
 Cache-Control: no-cache
 ```
 
-**Result:** Every request checks origin via If-Modified-Since or 
+**Result:** Every request checks origin via If-Modified-Since or
 ETag. If nothing changed, serves cached version (304 response).
 
 ---
@@ -415,19 +440,21 @@ ETag. If nothing changed, serves cached version (304 response).
 
 **What it does:** Prevents any caching
 
-**When to use:** Sensitive data (account info, payment details) or 
+**When to use:** Sensitive data (account info, payment details) or
 highly dynamic content (real-time scores, live chat)
 
 **Technical spec:** Combine both directives
 
 **Example:**
+
 ```http
 Cache-Control: private, no-store
 ```
 
-**Result:** Every request fetches fresh from origin. Nothing cached 
+**Result:** Every request fetches fresh from origin. Nothing cached
 anywhere.
-```
+
+````
 
 ---
 
@@ -473,8 +500,9 @@ const handler = async (req) => {
   return new Response('Hello')
 }
 addEventListener('fetch', e => e.respondWith(handler(e.request)))
-```
-```
+````
+
+````
 
 ✅ **After (Explained progression):**
 ```markdown
@@ -482,14 +510,14 @@ addEventListener('fetch', e => e.respondWith(handler(e.request)))
 
 ### What You'll Build
 
-A working URL shortener that redirects short links to long URLs, 
+A working URL shortener that redirects short links to long URLs,
 stores mappings, and tracks click analytics.
 
 **Live example:** `short.example.com/github` → `github.com/cloudflare`
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience with 
+Developers comfortable with JavaScript. No prior experience with
 Workers needed, but you should understand:
 - HTTP requests and responses
 - JSON data format
@@ -510,7 +538,7 @@ Workers needed, but you should understand:
 
 ## Step 1: Create Your First Worker
 
-Let's start with the absolute minimum—a Worker that responds to 
+Let's start with the absolute minimum—a Worker that responds to
 requests:
 
 ```javascript
@@ -526,7 +554,7 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-```
+````
 
 **What this code does:**
 
@@ -550,15 +578,15 @@ Now let's make it recognize short codes in the URL:
 
 ```javascript
 async function handleRequest(request) {
-  // Extract the pathname from the URL
-  // Example: https://short.example.com/github → "/github"
-  const url = new URL(request.url)
-  const shortCode = url.pathname.slice(1) // Remove leading "/"
-  
-  // For now, just echo back the short code
-  return new Response(`You requested: ${shortCode}`, {
-    headers: { 'content-type': 'text/plain' }
-  })
+	// Extract the pathname from the URL
+	// Example: https://short.example.com/github → "/github"
+	const url = new URL(request.url);
+	const shortCode = url.pathname.slice(1); // Remove leading "/"
+
+	// For now, just echo back the short code
+	return new Response(`You requested: ${shortCode}`, {
+		headers: { "content-type": "text/plain" },
+	});
 }
 ```
 
@@ -590,15 +618,15 @@ Now we can detect what short code someone's requesting...
 
 **Cause:** Your Worker is doing too much computation in a single request
 
-**Solution:** Workers have a 50ms CPU time limit. Move heavy processing 
+**Solution:** Workers have a 50ms CPU time limit. Move heavy processing
 to background tasks or use Durable Objects for longer operations.
 
 **Problem:** "KV data not updating"
 
-**Cause:** KV is eventually consistent and may take 60 seconds to 
+**Cause:** KV is eventually consistent and may take 60 seconds to
 propagate globally
 
-**Solution:** For testing, add a cache-busting parameter (`?v=2`) or 
+**Solution:** For testing, add a cache-busting parameter (`?v=2`) or
 wait 60 seconds between writes and reads.
 
 ---
@@ -608,20 +636,24 @@ wait 60 seconds between writes and reads.
 Want to take this further? Here are some ideas:
 
 **Add Click Analytics** (Medium difficulty)
+
 - Store click count in KV
 - Increment on each redirect
 - Create stats endpoint
 
 **Custom Short Codes** (Easy)
+
 - Let users choose their short code
 - Check if code is already taken
 - Return error if unavailable
 
 **Expiring Links** (Medium)
+
 - Store expiration timestamp
 - Check before redirecting
 - Return 404 if expired
-```
+
+````
 
 ---
 
@@ -642,7 +674,7 @@ Want to take this further? Here are some ideas:
 - Not: "Webhooks, which are HTTP callbacks, send notifications containing event data to your specified endpoint when certain events occur on the platform."
 
 ✅ **Active voice** over passive
-- "The system sends a notification" 
+- "The system sends a notification"
 - Not: "A notification is sent by the system"
 
 ✅ **Concrete nouns** over abstract
@@ -663,11 +695,12 @@ Want to take this further? Here are some ideas:
 
 **Always define on first use:**
 ```markdown
-An API (Application Programming Interface) defines how programs 
+An API (Application Programming Interface) defines how programs
 can request and exchange data...
-```
+````
 
 **Expand acronyms:**
+
 ```markdown
 CDN (Content Delivery Network)
 CI/CD (Continuous Integration/Continuous Deployment)
@@ -675,9 +708,10 @@ HMAC (Hash-based Message Authentication Code)
 ```
 
 **Provide context for technical terms:**
+
 ```markdown
 Not: "Configure the webhook endpoint."
-But: "A webhook endpoint is the URL where we'll send notifications. 
+But: "A webhook endpoint is the URL where we'll send notifications.
 Configure it to point to your server."
 ```
 
@@ -696,16 +730,16 @@ Configure it to point to your server."
 
 ```markdown
 **Think of It Like:**
-An API is like a restaurant menu. The menu shows you what dishes 
-are available (endpoints), what customizations you can request 
-(parameters like "no onions" or "extra spicy"), and what you'll 
-receive (the response - your meal). You don't need to know how the 
-kitchen operates or what cooking techniques they use. You just order 
+An API is like a restaurant menu. The menu shows you what dishes
+are available (endpoints), what customizations you can request
+(parameters like "no onions" or "extra spicy"), and what you'll
+receive (the response - your meal). You don't need to know how the
+kitchen operates or what cooking techniques they use. You just order
 from the menu, and the kitchen handles the rest.
 
 **Where this breaks down:**
-Unlike a restaurant where you wait for your food, API responses are 
-usually near-instantaneous. Also, APIs can fail (kitchen is out of 
+Unlike a restaurant where you wait for your food, API responses are
+usually near-instantaneous. Also, APIs can fail (kitchen is out of
 ingredients), requiring error handling.
 ```
 
@@ -713,15 +747,15 @@ ingredients), requiring error handling.
 
 ```markdown
 **Think of It Like:**
-Caching is like a library's reserve desk. Popular books are kept at 
-the front desk for quick access instead of requiring a trip to the 
-stacks. The first person requesting a book triggers the librarian to 
-fetch it from the stacks, but then it stays at the reserve desk so 
+Caching is like a library's reserve desk. Popular books are kept at
+the front desk for quick access instead of requiring a trip to the
+stacks. The first person requesting a book triggers the librarian to
+fetch it from the stacks, but then it stays at the reserve desk so
 subsequent readers can grab it immediately.
 
 **Where this breaks down:**
-Caches expire (books eventually return to the stacks), and cache 
-invalidation (deciding when to return books) is more complex than 
+Caches expire (books eventually return to the stacks), and cache
+invalidation (deciding when to return books) is more complex than
 the metaphor suggests.
 ```
 
@@ -729,15 +763,15 @@ the metaphor suggests.
 
 ```markdown
 **Think of It Like:**
-Load balancing is like grocery store checkout lanes. Instead of 
-everyone lining up at a single register (which would create a huge 
-wait), customers are distributed across multiple lanes. If one lane 
-gets too long or a register breaks down, the store can redirect 
+Load balancing is like grocery store checkout lanes. Instead of
+everyone lining up at a single register (which would create a huge
+wait), customers are distributed across multiple lanes. If one lane
+gets too long or a register breaks down, the store can redirect
 people to other lanes.
 
 **Where this breaks down:**
-Load balancers are more intelligent than checkout lane selection—they 
-know which servers are healthy, how busy they are, and can route 
+Load balancers are more intelligent than checkout lane selection—they
+know which servers are healthy, how busy they are, and can route
 based on sophisticated algorithms.
 ```
 
@@ -745,14 +779,14 @@ based on sophisticated algorithms.
 
 ```markdown
 **Think of It Like:**
-A webhook is like a doorbell notification. Instead of constantly 
-checking your front door to see if someone arrived (polling), the 
-doorbell alerts you the moment someone presses it (push notification). 
+A webhook is like a doorbell notification. Instead of constantly
+checking your front door to see if someone arrived (polling), the
+doorbell alerts you the moment someone presses it (push notification).
 You only respond when there's actually something to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have some latency due to 
-network transmission. Also, webhooks can fail if your server is down 
+Doorbells are instantaneous, while webhooks have some latency due to
+network transmission. Also, webhooks can fail if your server is down
 (like a broken doorbell).
 ```
 
@@ -760,15 +794,15 @@ network transmission. Also, webhooks can fail if your server is down
 
 ```markdown
 **Think of It Like:**
-Authentication is like a building security badge system. You present 
-your badge (credentials) when entering. The system verifies you are 
-who you claim to be (authentication), then checks what floors you're 
-allowed to access (authorization). Different badges have different 
+Authentication is like a building security badge system. You present
+your badge (credentials) when entering. The system verifies you are
+who you claim to be (authentication), then checks what floors you're
+allowed to access (authorization). Different badges have different
 access levels.
 
 **Where this breaks down:**
-Digital authentication often uses time-limited tokens (like a badge 
-that expires), and can verify identity through multiple methods 
+Digital authentication often uses time-limited tokens (like a badge
+that expires), and can verify identity through multiple methods
 (password + fingerprint), which isn't common with physical badges.
 ```
 
@@ -776,15 +810,15 @@ that expires), and can verify identity through multiple methods
 
 ```markdown
 **Think of It Like:**
-Rate limiting is like freeway on-ramp metering lights. Instead of 
-letting everyone merge at once (causing congestion), the lights 
-control how many cars enter per minute. This keeps traffic flowing 
-smoothly on the main freeway. If you arrive too fast, you wait at 
+Rate limiting is like freeway on-ramp metering lights. Instead of
+letting everyone merge at once (causing congestion), the lights
+control how many cars enter per minute. This keeps traffic flowing
+smoothly on the main freeway. If you arrive too fast, you wait at
 the red light.
 
 **Where this breaks down:**
-Rate limits are often user-specific (you get your own limit), not 
-shared like a metering light. Also, rate limits reset on schedules 
+Rate limits are often user-specific (you get your own limit), not
+shared like a metering light. Also, rate limits reset on schedules
 (every hour, every day), unlike continuous traffic flow.
 ```
 
@@ -792,14 +826,14 @@ shared like a metering light. Also, rate limits reset on schedules
 
 ```markdown
 **Think of It Like:**
-A database index is like the index at the back of a textbook. Instead 
-of reading every page to find mentions of "webhooks," you check the 
-index, which tells you exactly which pages to look at. The index 
+A database index is like the index at the back of a textbook. Instead
+of reading every page to find mentions of "webhooks," you check the
+index, which tells you exactly which pages to look at. The index
 takes up extra space, but makes searching dramatically faster.
 
 **Where this breaks down:**
-Database indexes need updating when data changes (like keeping a 
-book index current as you add pages), and choosing which fields to 
+Database indexes need updating when data changes (like keeping a
+book index current as you add pages), and choosing which fields to
 index involves tradeoffs between search speed and write speed.
 ```
 
@@ -807,16 +841,16 @@ index involves tradeoffs between search speed and write speed.
 
 ```markdown
 **Think of It Like:**
-A CDN (Content Delivery Network) is like having local warehouses 
-instead of shipping everything from one central warehouse. When 
-someone in California orders a product, it ships from the California 
-warehouse (faster delivery). When someone in New York orders, it 
+A CDN (Content Delivery Network) is like having local warehouses
+instead of shipping everything from one central warehouse. When
+someone in California orders a product, it ships from the California
+warehouse (faster delivery). When someone in New York orders, it
 ships from New York. Same product, closer source.
 
 **Where this breaks down:**
-Unlike physical warehouses with unique inventory, CDNs store copies 
-of the same content in many locations. Updates need to propagate to 
-all locations (cache invalidation), which has no physical warehouse 
+Unlike physical warehouses with unique inventory, CDNs store copies
+of the same content in many locations. Updates need to propagate to
+all locations (cache invalidation), which has no physical warehouse
 equivalent.
 ```
 
@@ -824,17 +858,17 @@ equivalent.
 
 ```markdown
 **Think of It Like:**
-Software containers are like shipping containers. Before shipping 
-containers existed, moving goods required different methods for 
-different types of cargo. Shipping containers standardized this—put 
-anything inside a standard container, and it can go on any ship, 
-truck, or train. Software containers work the same way: package your 
+Software containers are like shipping containers. Before shipping
+containers existed, moving goods required different methods for
+different types of cargo. Shipping containers standardized this—put
+anything inside a standard container, and it can go on any ship,
+truck, or train. Software containers work the same way: package your
 application and its dependencies, and it runs anywhere.
 
 **Where this breaks down:**
-Shipping containers physically isolate cargo, while software 
-containers share the same operating system kernel. Also, you can run 
-thousands of software containers on one machine, unlike physical 
+Shipping containers physically isolate cargo, while software
+containers share the same operating system kernel. Also, you can run
+thousands of software containers on one machine, unlike physical
 containers.
 ```
 
@@ -843,15 +877,15 @@ containers.
 ```markdown
 **Think of It Like:**
 Environment variables are like your application's settings panel—
-configuration values that change behavior without modifying code. 
-Just like you might set your phone to dark mode or adjust notification 
-preferences, environment variables let you configure database URLs, 
+configuration values that change behavior without modifying code.
+Just like you might set your phone to dark mode or adjust notification
+preferences, environment variables let you configure database URLs,
 API keys, or feature flags without rewriting your application.
 
 **Where this breaks down:**
-Environment variables are usually set before the application starts 
-(not changed while running), and they're text-based rather than UI 
-toggles. They're also specific to each deployment environment (dev, 
+Environment variables are usually set before the application starts
+(not changed while running), and they're text-based rather than UI
+toggles. They're also specific to each deployment environment (dev,
 staging, production).
 ```
 
@@ -870,22 +904,26 @@ When you encounter a concept not in this library, create a new metaphor by:
 **Always structure content in this order:**
 
 **1. The Problem (Why)**
+
 ```markdown
-When building applications, you often need to know when something 
-happens on another platform—like when a payment completes, a file 
-finishes uploading, or a deployment succeeds. Constantly checking 
+When building applications, you often need to know when something
+happens on another platform—like when a payment completes, a file
+finishes uploading, or a deployment succeeds. Constantly checking
 for updates (polling) wastes resources and creates delays.
 ```
 
 **2. The Solution (What)**
+
 ```markdown
-Webhooks solve this by pushing notifications to you. When an event 
+Webhooks solve this by pushing notifications to you. When an event
 happens, we immediately send a message to your server with the details.
 ```
 
 **3. The Value (Why It Matters)**
+
 ```markdown
 This means:
+
 - Your application responds in real-time instead of polling
 - You save resources (no constant checking)
 - Users get faster updates
@@ -893,8 +931,10 @@ This means:
 ```
 
 **4. The Use Cases (When)**
+
 ```markdown
 Common scenarios:
+
 - Triggering workflows when deployments complete
 - Updating your database when content changes
 - Sending notifications when payments are processed
@@ -902,8 +942,10 @@ Common scenarios:
 ```
 
 **5. The Implementation (How)**
+
 ```markdown
 To set up a webhook:
+
 1. Create an endpoint URL where we'll send notifications
 2. Configure which events you want to receive
 3. Verify requests are from us (using signatures)
@@ -945,7 +987,7 @@ Focus on outcomes, when to involve technical help, business impact
 
 **Example in Practice:**
 
-```markdown
+````markdown
 ## Webhook Signature Verification
 
 ---
@@ -970,11 +1012,13 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## 📋 Simplification Overview
 
 **What was confusing:**
+
 - [Pattern 1 - e.g., Heavy acronym use without expansion]
 - [Pattern 2 - e.g., Assumed understanding of HTTP protocols]
 - [Pattern 3 - e.g., Jumped to implementation without explaining purpose]
 
 **Approach taken:**
+
 - [Strategy 1 - e.g., Added one-sentence summaries for each concept]
 - [Strategy 2 - e.g., Expanded all acronyms on first use]
 - [Strategy 3 - e.g., Added "Why this matters" to each section]
@@ -985,9 +1029,11 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## Section: [Original Heading]
 
 ### 📄 Original Content
-
 ```
+````
+
 [Exact text from source, formatting preserved]
+
 ```
 
 ### ⚠️ Issues Identified
@@ -1006,21 +1052,21 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 
 ### ✨ Simplified Version
 
-**In Plain Language:**  
+**In Plain Language:**
 [One crisp sentence capturing the essence without jargon]
 
-**What It Is:**  
-[2-3 paragraphs building understanding from basics. Define terms. 
+**What It Is:**
+[2-3 paragraphs building understanding from basics. Define terms.
 Explain concepts. Build progressively. No jargon assumed.]
 
-**Why It Matters:**  
+**Why It Matters:**
 [Value proposition and concrete benefits]
 
 - **Benefit 1:** [Specific, concrete impact]
 - **Benefit 2:** [Specific, concrete impact]
 - **Benefit 3:** [Specific, concrete impact]
 
-**When You'd Use This:**  
+**When You'd Use This:**
 
 - **Scenario 1:** [Realistic use case with context]
   - Example: "When building a chat application that needs real-time message delivery..."
@@ -1031,23 +1077,23 @@ Explain concepts. Build progressively. No jargon assumed.]
 - **Scenario 3:** [Realistic use case with context]
   - Example: "When triggering post-deployment tasks like cache clearing..."
 
-**Think of It Like:**  
+**Think of It Like:**
 [Tech-adjacent metaphor with detailed explanation]
 
 [Full metaphor explanation, making connections explicit]
 
-**Where this metaphor breaks down:**  
+**Where this metaphor breaks down:**
 [Acknowledge limitations honestly]
 
-**Common Pitfalls:**  
+**Common Pitfalls:**
 
-- **Pitfall:** [What people commonly misunderstand]  
+- **Pitfall:** [What people commonly misunderstand]
   **Reality:** [Correction with explanation]
 
-- **Pitfall:** [Common mistake]  
+- **Pitfall:** [Common mistake]
   **Reality:** [How it actually works]
 
-**Related Concepts:**  
+**Related Concepts:**
 [Connections to things readers might already know]
 
 - "If you've used [familiar concept], this works similarly..."
@@ -1124,6 +1170,7 @@ After the main simplification and summary, I include a **"Suggestions for Enhanc
 **Format:**
 
 Each suggestion includes:
+
 - **Line reference:** Specific location in the original document
 - **Section name:** What part of the doc this applies to
 - **Current approach:** What's there now
@@ -1133,11 +1180,9 @@ Each suggestion includes:
 
 **Example:**
 
-```markdown
+````markdown
 ---
-
 ## 📝 Suggestions for Enhancement
-
 ---
 
 ## 4. Suggestions for Enhancement
@@ -1154,11 +1199,13 @@ These suggestions show where additional patterns could improve accessibility:
 **Suggested enhancement:** Add API path for technical users who prefer code
 
 **Why this helps:**
+
 - Serves both UI users and developers with their preferred method
 - Technical users can automate the process via API
 - Provides complete coverage for mixed audiences
 
 **Implementation:**
+
 ```markdown
 ### Via API
 
@@ -1167,18 +1214,18 @@ These suggestions show where additional patterns could improve accessibility:
 
 \`\`\`bash
 curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/always_use_https" \\
-  -H "Authorization: Bearer {token}" \\
-  -d '{"value":"on"}'
+-H "Authorization: Bearer {token}" \\
+-d '{"value":"on"}'
 \`\`\`
 
 **Response:**
 \`\`\`json
 {
-  "success": true,
-  "result": {
-    "id": "always_use_https",
-    "value": "on"
-  }
+"success": true,
+"result": {
+"id": "always_use_https",
+"value": "on"
+}
 }
 \`\`\`
 
@@ -1195,6 +1242,7 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 **Suggested enhancement:** Move advanced technical details to collapsible section
 
 **Why this helps:**
+
 - Beginners get the simple explanation without being overwhelmed
 - Experts can expand for full technical depth
 - Maintains clear progressive disclosure
@@ -1202,15 +1250,17 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 
 **Implementation:**
 \`\`\`markdown
+
 ## How TLS Encryption Works
 
-Your connection is encrypted using industry-standard TLS 1.3 protocol, 
+Your connection is encrypted using industry-standard TLS 1.3 protocol,
 ensuring no one can intercept your data in transit.
 
 <details>
 <summary>For technical users: Cipher suite details</summary>
 
 We support TLS 1.3 with modern AEAD cipher suites including:
+
 - TLS_AES_128_GCM_SHA256
 - TLS_AES_256_GCM_SHA384
 - TLS_CHACHA20_POLY1305_SHA256
@@ -1230,6 +1280,7 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 **Suggested enhancement:** Call out recommended default for most users
 
 **Why this helps:**
+
 - Reduces decision paralysis for uncertain users
 - Provides a safe starting point
 - Guides users toward best security practices
@@ -1237,22 +1288,23 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 
 **Implementation:**
 \`\`\`markdown
+
 ### Encryption Modes
 
 **Recommended for most sites:** Full (Strict)
 
-Provides maximum security by validating your origin server's 
-certificate. This is the best option if your server has a valid SSL 
+Provides maximum security by validating your origin server's
+certificate. This is the best option if your server has a valid SSL
 certificate installed.
 
 #### Other Options
 
 - **Off:** No encryption (Not recommended - only use for testing)
-- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your 
+- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your
   server doesn't have SSL)
 - **Full:** Encrypts entire path but doesn't validate certificate
 - **Full (Strict):** Maximum security with certificate validation ✅
-\`\`\`
+  \`\`\`
 
 ---
 
@@ -1264,6 +1316,7 @@ certificate installed.
 **Suggested enhancement:** Add realistic use case showing feature in action
 
 **Why this helps:**
+
 - Makes abstract benefits concrete and relatable
 - Helps users visualize how they'd use this
 - Provides "aha moment" of recognition
@@ -1275,19 +1328,21 @@ certificate installed.
 Prevents attackers from overwhelming your site with fake traffic.
 
 **Real scenario:**
-An e-commerce site during Black Friday gets hit by bots trying to 
-buy limited inventory. DDoS protection automatically filters out 
-the bot traffic, letting real customers complete their purchases 
+An e-commerce site during Black Friday gets hit by bots trying to
+buy limited inventory. DDoS protection automatically filters out
+the bot traffic, letting real customers complete their purchases
 while the attack is absorbed across Cloudflare's network.
 
-Without protection, the site would crash within minutes, losing 
+Without protection, the site would crash within minutes, losing
 thousands in sales.
 \`\`\`
 ```
+````
 
 **When to include suggestions:**
 
 Include this section when:
+
 - Multi-path opportunities exist (Dashboard + API)
 - Technical details could be collapsed
 - Missing recommended defaults
@@ -1298,6 +1353,7 @@ Include this section when:
 **Placement:**
 
 The Suggestions section appears:
+
 - After the "Summary & Recommendations" section
 - Before the "Next Steps" section
 - Clearly separated with heading and explanation
@@ -1335,7 +1391,7 @@ Before finalizing any simplified content, verify:
 ❌ "Clearly, this requires..."  
 ❌ "As everyone knows..."  
 ❌ "It's easy to..."  
-❌ "All you have to do is..."  
+❌ "All you have to do is..."
 
 **Use these respectful alternatives:**
 
@@ -1344,34 +1400,38 @@ Before finalizing any simplified content, verify:
 ✅ "This requires..."  
 ✅ "Here's how this works..."  
 ✅ "This involves..."  
-✅ "The process is..."  
+✅ "The process is..."
 
 ### Accuracy Is Non-Negotiable
 
 **Good simplification:**
+
 ```markdown
-Webhooks send HTTP POST requests to your endpoint URL whenever 
-specified events occur. Think of it as a notification system where 
+Webhooks send HTTP POST requests to your endpoint URL whenever
+specified events occur. Think of it as a notification system where
 we call your server instead of you constantly checking ours.
 ```
-*Accurate, clear, uses metaphor effectively*
+
+_Accurate, clear, uses metaphor effectively_
 
 **Bad simplification:**
+
 ```markdown
 Webhooks let programs talk to each other.
 ```
-*Too vague, loses important details, not actually helpful*
+
+_Too vague, loses important details, not actually helpful_
 
 **When complex accuracy is needed:**
 
 Use progressive disclosure:
 
 ```markdown
-**Simplified:** Rate limiting controls how many requests you can 
+**Simplified:** Rate limiting controls how many requests you can
 make in a time period, like 100 requests per minute.
 
-**More precisely:** Rate limits apply per API key and reset on a 
-sliding window. If you hit the limit, you'll receive a 429 status 
+**More precisely:** Rate limits apply per API key and reset on a
+sliding window. If you hit the limit, you'll receive a 429 status
 code with a Retry-After header indicating when you can try again.
 ```
 
@@ -1380,6 +1440,7 @@ code with a Retry-After header indicating when you can try again.
 #### API Documentation
 
 Focus on:
+
 - What the endpoint does (purpose)
 - When you'd use it (scenarios)
 - What you send (parameters explained)
@@ -1388,6 +1449,7 @@ Focus on:
 - Error handling (what can go wrong)
 
 **Add value through:**
+
 - Explaining parameter purposes, not just types
 - Showing realistic request/response examples
 - Clarifying common misunderstandings
@@ -1396,6 +1458,7 @@ Focus on:
 #### Architecture Documentation
 
 Focus on:
+
 - Problem being solved
 - Why this approach was chosen
 - Tradeoffs made (what was gained/lost)
@@ -1403,6 +1466,7 @@ Focus on:
 - Alternatives considered
 
 **Add value through:**
+
 - Explaining decision rationale
 - Making tradeoffs explicit
 - Providing context for choices
@@ -1411,12 +1475,14 @@ Focus on:
 #### Code Documentation
 
 Focus on:
+
 - What the code accomplishes
 - Why it's structured this way
 - Key concepts or patterns used
 - What to watch out for
 
 **Add value through:**
+
 - Plain-language "reading guides"
 - Explaining non-obvious choices
 - Clarifying complex logic
@@ -1454,22 +1520,25 @@ Focus on:
 ## 📋 Simplification Overview
 
 **What was done well:**
+
 - Clear section headings with logical flow
 - Terms defined on first use
 - Good use of examples
 - "Why" explained before "how"
 
 **Minor improvements suggested:**
+
 - Could add a tech-adjacent metaphor for [concept]
 - Section 3 could benefit from a concrete use case
 - Consider adding "common pitfalls" to section 5
 
 **Overall assessment:**
-This documentation is already quite accessible. The suggestions above 
+This documentation is already quite accessible. The suggestions above
 are minor enhancements rather than necessary corrections.
 ```
 
 **Avoid:**
+
 - Adding unnecessary verbosity
 - Creating problems that don't exist
 - Over-explaining clear content
@@ -1485,6 +1554,7 @@ are minor enhancements rather than necessary corrections.
    - Preserve necessary complexity
 
 2. **Layer explanations**
+
    ```markdown
    **High-level:** [What it accomplishes]
    **How it works:** [Simplified mechanism]
@@ -1511,7 +1581,8 @@ are minor enhancements rather than necessary corrections.
    - Preserve technical correctness
 
 2. **Add explanatory context**
-   ```markdown
+
+   ````markdown
    **What this code does:**
    [Plain-language explanation]
 
@@ -1519,12 +1590,17 @@ are minor enhancements rather than necessary corrections.
    [Architectural rationale]
 
    **Key points to understand:**
+
    - [Important concept 1]
    - [Important concept 2]
 
    ```python
    [Original code, unchanged]
    ```
+   ````
+
+   ```
+
    ```
 
 3. **Create "reading guides"**
@@ -1541,9 +1617,10 @@ are minor enhancements rather than necessary corrections.
    - Leave component code unchanged
 
 2. **Explain component purpose**
+
    ```markdown
    **What this component does:**
-   The <CodeBlock> component displays syntax-highlighted code with 
+   The <CodeBlock> component displays syntax-highlighted code with
    copy functionality, making it easier for readers to use the examples.
    ```
 
@@ -1554,7 +1631,7 @@ are minor enhancements rather than necessary corrections.
 
 ## Future Enhancements
 
-*Documented for future implementation*
+_Documented for future implementation_
 
 ### Planned Features
 
@@ -1567,19 +1644,21 @@ Support for code files with inline documentation:
 def process_webhook(payload, signature):
     """
     Processes incoming webhook notifications.
-    
+
     Verifies signature, parses payload, triggers handlers.
     """
     # Implementation...
 ```
 
 **Planned behavior:**
+
 - Extract docstrings and comments
 - Simplify technical language in comments
 - Add explanatory prose for complex logic
 - Generate "code walkthrough" guides
 
 **Supported formats:**
+
 - `.js`, `.ts`, `.tsx` (JavaScript/TypeScript)
 - `.py` (Python)
 - `.go` (Go)
@@ -1605,6 +1684,7 @@ Quantitative analysis:
 - **Context gap analysis** - Identify missing "why" and "when" statements
 
 **Auto-prioritization:**
+
 - Sort sections by complexity
 - Focus on highest-value simplifications
 - Generate complexity reports
@@ -1646,63 +1726,65 @@ Returns a `webhook` object.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-Set up automatic notifications that we'll send to your server whenever 
+Set up automatic notifications that we'll send to your server whenever
 specific events occur.
 
 **What It Is:**
-A webhook subscription tells our system to notify your application 
-when certain events happen (like a deployment completing or content 
-being published). Instead of your application constantly checking for 
+A webhook subscription tells our system to notify your application
+when certain events happen (like a deployment completing or content
+being published). Instead of your application constantly checking for
 updates (polling), we push notifications to you the moment events occur.
 
 **Why It Matters:**
+
 - **Real-time updates** - Your application responds immediately
 - **Resource efficiency** - No wasted API calls checking for changes
 - **Reliability** - You never miss an event
 - **Automation** - Trigger workflows automatically
 
 **When You'd Use This:**
+
 - **Deployment notifications:** Trigger post-deployment tasks when builds complete
 - **Content synchronization:** Update your CMS when content changes
 - **Monitoring:** Alert your team when errors occur
 - **Integration:** Connect multiple systems to respond to events
 
 **Think of It Like:**
-A webhook is like setting up a doorbell notification on your phone. 
-Instead of constantly checking your front door camera to see if someone 
-arrived (polling), the doorbell alerts you the moment someone presses 
-it (push notification). You only respond when there's actually something 
+A webhook is like setting up a doorbell notification on your phone.
+Instead of constantly checking your front door camera to see if someone
+arrived (polling), the doorbell alerts you the moment someone presses
+it (push notification). You only respond when there's actually something
 to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have small delays due to 
-network transmission. Also, webhooks can fail if your server is down 
+Doorbells are instantaneous, while webhooks have small delays due to
+network transmission. Also, webhooks can fail if your server is down
 (like a broken doorbell), so you need retry logic.
 
 **Parameters Explained:**
 
-- **`endpoint`** - The URL where we'll send notifications (your server's 
+- **`endpoint`** - The URL where we'll send notifications (your server's
   address that listens for webhook events). Must use HTTPS for security.
 
-- **`events`** - Which events you want to receive (like `deployment.succeeded` 
+- **`events`** - Which events you want to receive (like `deployment.succeeded`
   or `content.published`). You choose only the events you care about.
 
-- **`secret`** - Optional security key for verifying notifications actually 
+- **`secret`** - Optional security key for verifying notifications actually
   come from us. We use this to create a signature you can verify.
 
 **Common Pitfalls:**
 
 - **Pitfall:** Thinking webhooks are 100% reliable  
-  **Reality:** Network issues or server downtime can cause missed notifications. 
+  **Reality:** Network issues or server downtime can cause missed notifications.
   Implement retry logic and consider periodic polling as a backup.
 
 - **Pitfall:** Not verifying signatures  
-  **Reality:** Without signature verification, attackers could send fake 
+  **Reality:** Without signature verification, attackers could send fake
   webhooks to trigger unauthorized actions.
 
 **Related Concepts:**
-If you've used RSS feeds, webhooks work similarly—both push updates to 
-you. The difference is webhooks are programmable and work with any type 
+If you've used RSS feeds, webhooks work similarly—both push updates to
+you. The difference is webhooks are programmable and work with any type
 of event, not just content updates.
 ```
 
@@ -1713,8 +1795,8 @@ of event, not just content updates.
 ```markdown
 ## Edge Deployment Architecture
 
-We've implemented a globally distributed edge architecture utilizing 
-V8 isolates for multi-tenant execution with microsecond cold starts 
+We've implemented a globally distributed edge architecture utilizing
+V8 isolates for multi-tenant execution with microsecond cold starts
 and automatic geographic distribution.
 ```
 
@@ -1724,40 +1806,42 @@ and automatic geographic distribution.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-We run your code on servers located around the world, close to your 
+We run your code on servers located around the world, close to your
 users, making responses nearly instant regardless of where users are.
 
 **What It Is:**
-Traditional servers run in specific data centers—if your server is in 
-Virginia and your user is in Singapore, every request travels across 
-the world and back (adding hundreds of milliseconds). Our edge 
-architecture runs your code on servers in hundreds of cities worldwide, 
+Traditional servers run in specific data centers—if your server is in
+Virginia and your user is in Singapore, every request travels across
+the world and back (adding hundreds of milliseconds). Our edge
+architecture runs your code on servers in hundreds of cities worldwide,
 so requests are handled by the nearest server.
 
 **Why It Matters:**
+
 - **Speed:** Users get responses in 10-50ms instead of 200-500ms
 - **Reliability:** If one location fails, others continue serving traffic
 - **Scale:** Handles traffic spikes automatically across all locations
 - **Simplicity:** You deploy once; we handle global distribution
 
 **When You'd Use This:**
+
 - **Global applications:** Users are distributed worldwide
 - **API endpoints:** Need fast response times everywhere
 - **Dynamic content:** Content that can't be cached must still be fast
 - **High availability:** Can't afford regional outages
 
 **Think of It Like:**
-Instead of one central warehouse shipping products nationwide (slow 
-delivery to distant customers), you have local warehouses in every major 
-city. When someone orders, it ships from their nearest warehouse. Same 
+Instead of one central warehouse shipping products nationwide (slow
+delivery to distant customers), you have local warehouses in every major
+city. When someone orders, it ships from their nearest warehouse. Same
 product, faster delivery, handled automatically.
 
 **The Technical Approach:**
 
-We use "V8 isolates"—lightweight execution environments that start in 
-microseconds (thousandths of a millisecond). Traditional "serverless" 
-functions use containers that take 50-500ms to start. Isolates are 
-fast enough that we don't need to keep them warm; they start on-demand 
+We use "V8 isolates"—lightweight execution environments that start in
+microseconds (thousandths of a millisecond). Traditional "serverless"
+functions use containers that take 50-500ms to start. Isolates are
+fast enough that we don't need to keep them warm; they start on-demand
 for each request.
 
 **Why this architecture:**
@@ -1768,11 +1852,12 @@ We evaluated three approaches:
 3. **Isolate-based edge:** Global + fast (our choice)
 
 **Tradeoff made:**
-Isolates have some limitations compared to full containers (no arbitrary 
-system libraries, limited execution time). We accepted these constraints 
+Isolates have some limitations compared to full containers (no arbitrary
+system libraries, limited execution time). We accepted these constraints
 for the massive speed improvement.
 
 **Common Pitfalls:**
+
 - **Pitfall:** Assuming it works like traditional servers  
   **Reality:** Stateless execution—no persistent local storage, no background jobs
 
@@ -1780,20 +1865,22 @@ for the massive speed improvement.
   **Reality:** Implements web standards, not full Node.js APIs
 
 **Related Concepts:**
-If you've used CDNs (Content Delivery Networks), this is similar but 
-for code execution, not just static files. Like a CDN distributes 
+If you've used CDNs (Content Delivery Networks), this is similar but
+for code execution, not just static files. Like a CDN distributes
 content globally, we distribute code execution globally.
 ```
 
 ## Remember
 
 **Your mission:**
+
 - Make technical concepts accessible
 - Maintain technical accuracy
 - Respect reader intelligence
 - Focus on understanding
 
 **Always include:**
+
 - One-sentence plain language summary
 - Clear "why" and "when" explanations
 - Tech-adjacent metaphor with limitations
@@ -1801,25 +1888,28 @@ content globally, we distribute code execution globally.
 - Use cases grounding abstract concepts
 
 **Quality standards:**
+
 - Technical accuracy is non-negotiable
 - Metaphors must clarify, not confuse
 - Tone must be professional and respectful
 - No condescending language ever
 
 **Process:**
+
 1. Ask which sections to focus on
 2. Identify specific issues (jargon, assumptions, logic, context)
 3. Generate complete before/after comparison
 4. Prompt for next steps
 
 **Output:**
+
 - Create `.eli5.md` file in same directory
 - Include all required elements per section
 - Provide actionable recommendations
 - Offer clear next-step options
 
 **Philosophy:**
-Technical expertise should never be a barrier to understanding. Every 
+Technical expertise should never be a barrier to understanding. Every
 person deserves clear, accurate, respectful documentation.
 
 ---
@@ -1831,4 +1921,3 @@ person deserves clear, accurate, respectful documentation.
 **License:** MIT  
 **Version:** 1.0  
 **Last Updated:** February 2026
-
diff --git a/.agents/skills/eli5/references/content-type-guide.md b/.agents/skills/eli5/references/content-type-guide.md
index 85d544a7c071296..1454cfea7242833 100644
--- a/.agents/skills/eli5/references/content-type-guide.md
+++ b/.agents/skills/eli5/references/content-type-guide.md
@@ -7,6 +7,7 @@ Operational guide for detecting and simplifying different documentation types.
 ## Purpose
 
 This guide provides:
+
 - **Detection criteria** for identifying content types
 - **Required elements** checklist for each type
 - **Simplification patterns** specific to each type
@@ -21,6 +22,7 @@ This guide provides:
 For each content type below, the enhancement patterns are designed to ADD MINIMAL CONTEXT AND EXAMPLES, not restructure or massively expand.
 
 **Universal constraints:**
+
 - Maximum 1-2 examples per major concept
 - Each example: 5-15 lines
 - Inline "why" explanations: 1-2 sentences
@@ -31,6 +33,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Minimal testing guidance (3-5 commands for tutorials)
 
 **When patterns below suggest "Add [section]":**
+
 - Interpret as "enhance inline" not "create separate major section"
 - Keep additions brief and integrated
 - Target 1.5-2x expansion, not 5-10x
@@ -39,13 +42,13 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 ## Content Type Overview
 
-| Type | Purpose | Key Pattern | Example |
-|------|---------|-------------|---------|
-| **Overview** | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages |
-| **Concept** | Build understanding of "why" | Analogy → Plain → Technical | "What is rate limiting?" |
-| **How To** | Enable task completion | Context → Multi-path steps | "Enable HTTPS" |
-| **Reference** | Provide comprehensive specs | Use-case organization | API parameters, headers |
-| **Tutorial** | Teach through application | Build → Enhance → Polish | "Build a URL shortener" |
+| Type          | Purpose                             | Key Pattern                  | Example                  |
+| ------------- | ----------------------------------- | ---------------------------- | ------------------------ |
+| **Overview**  | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages    |
+| **Concept**   | Build understanding of "why"        | Analogy → Plain → Technical  | "What is rate limiting?" |
+| **How To**    | Enable task completion              | Context → Multi-path steps   | "Enable HTTPS"           |
+| **Reference** | Provide comprehensive specs         | Use-case organization        | API parameters, headers  |
+| **Tutorial**  | Teach through application           | Build → Enhance → Polish     | "Build a URL shortener"  |
 
 ---
 
@@ -54,6 +57,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 ### Detection Criteria
 
 **Look for:**
+
 - Product/feature name in title or H1
 - Feature lists or capability descriptions
 - "What is [Product]" sections
@@ -62,6 +66,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Lack of step-by-step instructions
 
 **Confidence signals:**
+
 - Multiple features described briefly
 - High-level product description
 - Links to detailed documentation
@@ -69,6 +74,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Pricing or plan information
 
 **Example titles:**
+
 - "Cloudflare Workers"
 - "Introduction to Gateway"
 - "What is Workers KV?"
@@ -77,7 +83,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 - [ ] Opening benefit statement (what problem solved)
 - [ ] Problem/Solution/Benefit structure
-- [ ] "Perfect for" self-identification section  
+- [ ] "Perfect for" self-identification section
 - [ ] Clear call-to-action ("Get started" link)
 - [ ] Feature descriptions with benefits (not just specs)
 - [ ] Technical architecture separated/collapsed
@@ -87,12 +93,14 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Target: 1.5-2x original length**
 
 **Minimal additions:**
+
 1. **Add 2-4 sentence problem statement** (if completely missing) at document start
 2. **Add 1-2 use case examples inline** (5-10 lines each) showing who benefits
 3. **Add inline "why"** (1 sentence) when introducing features
 4. **Define jargon on first use** (brief inline definition)
 
 **Structure to preserve:**
+
 - Keep original opening and headings
 - Don't reorganize sections
 - Don't move architecture (just add brief intro if it leads)
@@ -100,41 +108,46 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Example enhancement:**
 
 Original (8 lines):
+
 ```markdown
 # Internal DNS
 
 Manage DNS records for your private network.
 
-Internal DNS zones pair with Gateway resolver policies to control 
+Internal DNS zones pair with Gateway resolver policies to control
 DNS query responses.
 
 ## Features
+
 - Create internal zones
 - Configure views
 - Link to Gateway
 ```
 
 Enhanced (15 lines - 1.9x):
+
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS 
+Manage DNS records for your private network without running your own DNS
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS query 
+Internal DNS zones pair with Gateway resolver policies to control DNS query
 responses based on context (source IP, user identity, domain).
 
-**Example use case:** A multi-region company creates separate views for London 
-and SF offices. Users query the same hostname (api.company.internal) but get 
+**Example use case:** A multi-region company creates separate views for London
+and SF offices. Users query the same hostname (api.company.internal) but get
 different IP addresses based on location.
 
 ## Features
+
 - Create internal zones - Private namespaces accessible only via Gateway
 - Configure views - Logical groupings that route different users to different resources
 - Link to Gateway - Resolver policies determine which view to use
 ```
 
 What was added:
+
 - 1 sentence "why" (without running own servers)
 - Brief context for zones (source IP, user identity)
 - 1 example (3 lines)
@@ -156,6 +169,7 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
+
 - "What is..." or "Understanding..." titles
 - Explanatory content (not procedural)
 - "How it works" sections
@@ -164,6 +178,7 @@ What was added:
 - Analogies or metaphors (sometimes)
 
 **Confidence signals:**
+
 - Explains mechanisms, not steps
 - Educational tone
 - Links to related concepts
@@ -171,6 +186,7 @@ What was added:
 - Multiple explanation approaches
 
 **Example titles:**
+
 - "Understanding Rate Limiting"
 - "How Caching Works"
 - "What is Edge Computing?"
@@ -188,6 +204,7 @@ What was added:
 ### Simplification Pattern
 
 **Structure:**
+
 ```markdown
 # [Concept Name]
 
@@ -196,6 +213,7 @@ What was added:
 **What it is:** [Plain English definition without jargon]
 
 **Why you need it:**
+
 - [Benefit 1]
 - [Benefit 2]
 - [Benefit 3]
@@ -203,6 +221,7 @@ What was added:
 **How it works:** [Simplified technical explanation]
 
 **Real scenarios:**
+
 - [Use case 1 with context]
 - [Use case 2 with context]
 - [Use case 3 with context]
@@ -228,6 +247,7 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
+
 - Action verbs in titles (Configure, Enable, Create, Set up)
 - Numbered steps or procedures
 - "Prerequisites" sections
@@ -236,6 +256,7 @@ What was added:
 - Command examples or code blocks
 
 **Confidence signals:**
+
 - Clear sequential structure
 - Specific actionable steps
 - Tool/UI references
@@ -243,6 +264,7 @@ What was added:
 - Troubleshooting sections
 
 **Example titles:**
+
 - "Enable Always Use HTTPS"
 - "Configure DNS Settings"
 - "Create a Worker"
@@ -265,6 +287,7 @@ What was added:
 **For how-to guides, preserve existing steps and add minimal context:**
 
 **Minimal additions:**
+
 1. **Add 1-2 sentence "what this accomplishes"** at top (if missing)
 2. **Add inline "why"** (1 sentence) for non-obvious steps
 3. **Add 1 example** showing when you'd use this (3-5 lines)
@@ -272,6 +295,7 @@ What was added:
 5. **Add 1-2 troubleshooting notes** for critical failures only
 
 **Preserve:**
+
 - Original step numbering and flow
 - Existing Dashboard/API paths (don't create new ones)
 - All screenshots and UI elements
@@ -280,6 +304,7 @@ What was added:
 **Example enhancement:**
 
 Original (12 lines):
+
 ```markdown
 # Create a DNS View
 
@@ -297,10 +322,11 @@ Use the create view endpoint with zone IDs.
 ```
 
 Enhanced (20 lines - 1.67x):
+
 ```markdown
 # Create a DNS View
 
-Create a logical grouping of zones that determines which DNS records users see. 
+Create a logical grouping of zones that determines which DNS records users see.
 Useful for multi-region setups or environment separation.
 
 **Example:** Create "London View" and "SF View" to route users to nearest datacenter.
@@ -327,6 +353,7 @@ curl -X POST /api/views -d '{"name": "London View", "zone_ids": ["id1", "id2"]}'
 ```
 
 What was added:
+
 - 2-sentence purpose statement (2 lines)
 - 1 example (1 line)
 - Inline context for 2 steps (2 lines)
@@ -336,11 +363,13 @@ What was added:
 - Total: 8 lines added to 12 original = 20 lines (1.67x) ✅
 
 **What was NOT added:**
+
 - Comprehensive troubleshooting section
 - Multiple examples
 - Separate "Understanding Views" section
 - Extensive testing procedures
-```
+
+````
 
 ### Common Issues to Fix
 
@@ -414,7 +443,7 @@ What was added:
 **Example:**
 ```[language]
 [Realistic usage example]
-```
+````
 
 **Result:** [What happens when this is used]
 
@@ -423,7 +452,8 @@ What was added:
 ### [Next Option]
 
 [Same structure...]
-```
+
+````
 
 ### Common Issues to Fix
 
@@ -513,24 +543,25 @@ Add records to the zone.
 curl -X POST https://api.cloudflare.com/zones/ID/dns_records \\
   -d '{"type": "A", "name": "app", "content": "192.168.1.100"}'
 \`\`\`
-```
+````
 
 Enhanced (35 lines - 1.75x):
+
 ```markdown
 ## Step 1: Create the zone
 
-Create an internal zone that will contain your DNS records. This zone is only 
+Create an internal zone that will contain your DNS records. This zone is only
 accessible via Gateway (not public DNS).
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones \\
-  -d '{
-    "name": "company.internal",  # Your internal domain
-    "type": "internal"             # Marks as internal-only
-  }'
+-d '{
+"name": "company.internal", # Your internal domain
+"type": "internal" # Marks as internal-only
+}'
 \`\`\`
 
-**Example use:** A company creates company.internal for all internal apps 
+**Example use:** A company creates company.internal for all internal apps
 (app.company.internal, api.company.internal, db.company.internal).
 
 ## Step 2: Add DNS records
@@ -539,24 +570,27 @@ Add records mapping hostnames to private IPs.
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones/ZONE_ID/dns_records \\
-  -d '{
-    "type": "A",                           # Address record
-    "name": "app.company.internal",        # Full hostname
-    "content": "192.168.1.100"             # Private IP
-  }'
+-d '{
+"type": "A", # Address record
+"name": "app.company.internal", # Full hostname
+"content": "192.168.1.100" # Private IP
+}'
 \`\`\`
 
-**Test:** 
+**Test:**
 \`\`\`bash
 nslookup app.company.internal
+
 # Expected: Returns 192.168.1.100
+
 \`\`\`
 
-**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP 
+**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP
 connection or DNS settings.
 ```
 
 What was added:
+
 - Brief "why" for each step (1 sentence)
 - Inline code comments (3-4 comments)
 - 1 example showing usage (2 lines)
@@ -565,6 +599,7 @@ What was added:
 - Total: 15 lines added to 20 original = 35 lines (1.75x) ✅
 
 **What was NOT added:**
+
 - Separate "What you'll build" section
 - Multiple examples
 - Comprehensive troubleshooting section
@@ -614,16 +649,19 @@ What was added:
 Sometimes documentation combines types:
 
 ### Overview + How To
+
 **Pattern:** Product intro followed by quick start steps  
 **Approach:** Treat first section as Overview, steps as How To  
 **Example:** "Workers Overview" with "Deploy Your First Worker" steps
 
 ### Concept + Reference
+
 **Pattern:** Conceptual explanation followed by parameter reference  
 **Approach:** Layer explanation first, reference at bottom  
 **Example:** "Understanding Caching" + "Cache Headers Reference"
 
 ### Tutorial + Reference
+
 **Pattern:** Build project + API reference at end  
 **Approach:** Keep tutorial progressive, move reference to appendix  
 **Example:** "Build URL Shortener" + "Workers API Reference"
@@ -635,6 +673,7 @@ Sometimes documentation combines types:
 ## Quick Reference Cards
 
 ### Overview Page Card
+
 ```
 ✓ Opens with benefit statement
 ✓ Problem/Solution structure
@@ -644,6 +683,7 @@ Sometimes documentation combines types:
 ```
 
 ### Concept Page Card
+
 ```
 ✓ Analogy in first paragraph
 ✓ Plain definition
@@ -653,6 +693,7 @@ Sometimes documentation combines types:
 ```
 
 ### How To Page Card
+
 ```
 ✓ Context before steps
 ✓ Prerequisites listed
@@ -662,6 +703,7 @@ Sometimes documentation combines types:
 ```
 
 ### Reference Page Card
+
 ```
 ✓ Opening context
 ✓ Use-case organized
@@ -671,6 +713,7 @@ Sometimes documentation combines types:
 ```
 
 ### Tutorial Page Card
+
 ```
 ✓ "What you'll build"
 ✓ Prerequisites + time
diff --git a/.agents/skills/eli5/references/pattern-library.md b/.agents/skills/eli5/references/pattern-library.md
index 3d7b91b310a8918..f7ebb468915de2c 100644
--- a/.agents/skills/eli5/references/pattern-library.md
+++ b/.agents/skills/eli5/references/pattern-library.md
@@ -7,6 +7,7 @@ A reference collection of reusable before/after patterns for simplifying technic
 ## Purpose
 
 This library provides:
+
 - **Reusable patterns** for common simplification scenarios
 - **Jargon → Plain English** translations
 - **Before/after examples** demonstrating transformations
@@ -19,6 +20,7 @@ This library provides:
 **All patterns below demonstrate minimal, integrated enhancements (1.5-2x growth)**
 
 When applying these patterns:
+
 - ✅ Add inline, not as separate major sections
 - ✅ Integrate with existing content flow
 - ✅ Keep examples brief (5-15 lines each, max 1-2 examples)
@@ -32,6 +34,7 @@ When applying these patterns:
 When a pattern shows "Add [section]" → Interpret as "add brief inline content" not "create major new section"
 
 **Example:**
+
 - Pattern says: "Add use case example"
 - **Correct:** Add 5-10 line example inline with concept
 - **Incorrect:** Create separate "Use Case Examples" section with 4 detailed scenarios
@@ -44,23 +47,23 @@ When a pattern shows "Add [section]" → Interpret as "add brief inline content"
 
 Common technical terms and their accessible alternatives:
 
-| Technical Term | Plain English | Context Example |
-|----------------|---------------|-----------------|
-| **Implement** | Set up, turn on, use | "Set up two-factor authentication" not "Implement 2FA" |
-| **Utilize** | Use | "Use the API" not "Utilize the API" |
-| **Leverage** | Use, take advantage of | "Take advantage of caching" not "Leverage caching capabilities" |
-| **Execute** | Run | "Run the command" not "Execute the command" |
-| **Instantiate** | Create | "Create a new Worker" not "Instantiate a Worker" |
-| **Terminate** | Stop, end | "Stop the process" not "Terminate the process" |
-| **Subsequently** | Then, next | "Then, configure the settings" not "Subsequently, configure" |
-| **Optimal** | Best | "Best performance" not "Optimal performance" |
-| **Facilitate** | Help, enable | "This helps you deploy faster" not "Facilitates rapid deployment" |
-| **Invoke** | Call, trigger | "Call the function" not "Invoke the function" |
-| **Provision** | Set up, create | "Set up your server" not "Provision infrastructure" |
-| **Egress** | Outgoing data | "Data leaving your network" not "Egress traffic" |
-| **Ingress** | Incoming data | "Data entering your network" not "Ingress traffic" |
-| **Anycast** | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
-| **Propagation** | Spreading, updating | "Changes spread globally" not "Configuration propagates" |
+| Technical Term   | Plain English             | Context Example                                                      |
+| ---------------- | ------------------------- | -------------------------------------------------------------------- |
+| **Implement**    | Set up, turn on, use      | "Set up two-factor authentication" not "Implement 2FA"               |
+| **Utilize**      | Use                       | "Use the API" not "Utilize the API"                                  |
+| **Leverage**     | Use, take advantage of    | "Take advantage of caching" not "Leverage caching capabilities"      |
+| **Execute**      | Run                       | "Run the command" not "Execute the command"                          |
+| **Instantiate**  | Create                    | "Create a new Worker" not "Instantiate a Worker"                     |
+| **Terminate**    | Stop, end                 | "Stop the process" not "Terminate the process"                       |
+| **Subsequently** | Then, next                | "Then, configure the settings" not "Subsequently, configure"         |
+| **Optimal**      | Best                      | "Best performance" not "Optimal performance"                         |
+| **Facilitate**   | Help, enable              | "This helps you deploy faster" not "Facilitates rapid deployment"    |
+| **Invoke**       | Call, trigger             | "Call the function" not "Invoke the function"                        |
+| **Provision**    | Set up, create            | "Set up your server" not "Provision infrastructure"                  |
+| **Egress**       | Outgoing data             | "Data leaving your network" not "Egress traffic"                     |
+| **Ingress**      | Incoming data             | "Data entering your network" not "Ingress traffic"                   |
+| **Anycast**      | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
+| **Propagation**  | Spreading, updating       | "Changes spread globally" not "Configuration propagates"             |
 
 ---
 
@@ -71,6 +74,7 @@ Common technical terms and their accessible alternatives:
 ### Example: Internal DNS Documentation
 
 **Before (Original - 15 lines):**
+
 ```markdown
 # Internal DNS
 
@@ -83,6 +87,7 @@ Internal DNS zones pair with Gateway resolver policies.
 Use the dashboard or API to create an internal zone.
 
 ### Dashboard
+
 1. Navigate to Internal DNS
 2. Click Create Zone
 3. Enter zone name
@@ -90,25 +95,27 @@ Use the dashboard or API to create an internal zone.
 ```
 
 **After (Enhanced - 26 lines, 1.73x growth):**
+
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS 
+Manage DNS records for your private network without running your own DNS
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS 
+Internal DNS zones pair with Gateway resolver policies to control DNS
 responses based on source IP, user identity, or domain.
 
-**Example use case:** A multi-region company creates views for London and SF. 
-Users query api.company.internal but get different IPs based on location 
+**Example use case:** A multi-region company creates views for London and SF.
+Users query api.company.internal but get different IPs based on location
 (London users → 10.0.1.100, SF users → 10.0.2.100).
 
 ## Create a Zone
 
-Create an internal zone that will contain your DNS records. Zones are only 
+Create an internal zone that will contain your DNS records. Zones are only
 accessible via Gateway (not public DNS).
 
 ### Dashboard
+
 1. Navigate to Internal DNS → Zones
 2. Click **Create Zone**
 3. Enter zone name (e.g., company.internal)
@@ -118,8 +125,9 @@ accessible via Gateway (not public DNS).
 ```
 
 **What was added:**
+
 - 1 sentence explaining "why" (without running own servers) - 1 line
-- Brief context for resolver policies (source IP, user identity) - 1 line  
+- Brief context for resolver policies (source IP, user identity) - 1 line
 - 1 concrete example (3 lines)
 - Brief zone explanation (2 lines)
 - Inline step context (1 line each for 2 steps) - 2 lines
@@ -127,6 +135,7 @@ accessible via Gateway (not public DNS).
 - **Total added: 11 lines to 15 original = 26 lines (1.73x)** ✅
 
 **What was NOT added:**
+
 - No "What Problem Does Internal DNS Solve?" section
 - No "How It Works (Conceptual)" section before content
 - No diagram annotations
@@ -136,6 +145,7 @@ accessible via Gateway (not public DNS).
 - No separate "Understanding Zones" section
 
 **Why this works:**
+
 - Preserves original structure completely
 - Adds context inline where readers need it
 - Provides 1 concrete example for grounding
@@ -151,33 +161,37 @@ accessible via Gateway (not public DNS).
 ### Overview Pages
 
 **Before (Technical-first):**
+
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 isolates 
-for low-latency serverless code execution with sub-millisecond cold start 
+Product X is a distributed edge computing platform utilizing V8 isolates
+for low-latency serverless code execution with sub-millisecond cold start
 performance and global anycast deployment.
 ```
 
 **After (Benefit-first):**
+
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, scale 
+Run code worldwide without managing servers. Deploy in seconds, scale
 automatically, and pay only for what you use.
 
-**What problem it solves:** Maintaining global infrastructure is expensive 
+**What problem it solves:** Maintaining global infrastructure is expensive
 and complex. Product X runs your code in 300+ cities automatically.
 
 **Perfect for:**
+
 - Applications needing fast global performance
-- Teams wanting to skip server management  
+- Teams wanting to skip server management
 - Projects with variable traffic
 
 [Get started →]
 ```
 
 **Why this works:**
+
 - Opens with clear user value
 - Problem framing creates relevance
 - "Perfect for" helps self-identification
@@ -190,35 +204,39 @@ and complex. Product X runs your code in 300+ cities automatically.
 ### Concept Pages
 
 **Before (Abstract):**
+
 ```markdown
 ## Caching
 
-Caching stores frequently accessed data in high-speed storage layers to 
-reduce origin server load and improve response times through data locality 
+Caching stores frequently accessed data in high-speed storage layers to
+reduce origin server load and improve response times through data locality
 optimization.
 ```
 
 **After (Concrete):**
+
 ```markdown
 ## Caching
 
-**Think of it like:** A library's reserve desk. Popular books stay at the 
+**Think of it like:** A library's reserve desk. Popular books stay at the
 front desk for quick access instead of requiring trips to the distant stacks.
 
-**What it is:** Caching keeps copies of your frequently accessed files 
-(images, CSS, JavaScript) close to users, so they load instantly instead of 
+**What it is:** Caching keeps copies of your frequently accessed files
+(images, CSS, JavaScript) close to users, so they load instantly instead of
 being fetched from your origin server every time.
 
 **Why it matters:**
+
 - Pages load 10x faster (50ms vs 500ms)
 - Reduces server costs (fewer origin requests)
 - Handles traffic spikes (serves from cache, not origin)
 
-**When to use:** Any content that doesn't change constantly—images, stylesheets, 
+**When to use:** Any content that doesn't change constantly—images, stylesheets,
 blog posts, product pages.
 ```
 
 **Why this works:**
+
 - Analogy creates immediate mental model
 - Plain language explanation builds understanding
 - Benefits are concrete and measurable
@@ -231,6 +249,7 @@ blog posts, product pages.
 ### How To Pages
 
 **Before (Steps-only):**
+
 ```markdown
 ## Enable Feature X
 
@@ -241,7 +260,8 @@ blog posts, product pages.
 ```
 
 **After (Contextual multi-path):**
-```markdown
+
+````markdown
 ## Enable Feature X
 
 **What this does:** Protects your site from [specific threat] by [mechanism].
@@ -257,7 +277,7 @@ blog posts, product pages.
 4. Find **Feature X** and toggle it **On**
 5. Click **Save Changes** at the bottom
 
-💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes 
+💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes
 to see it working.
 
 ### Via API
@@ -270,12 +290,14 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_x_enabled": true}'
 ```
+````
 
 **Response:**
+
 ```json
 {
-  "success": true,
-  "result": {"feature_x_enabled": true}
+	"success": true,
+	"result": { "feature_x_enabled": true }
 }
 ```
 
@@ -287,7 +309,8 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 2. Check browser DevTools → Network tab
 3. Look for [specific indicator]
 4. You should see [expected result]
-```
+
+````
 
 **Why this works:**
 - Context explains purpose before steps
@@ -310,15 +333,16 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 **Content-Type:** MIME type. Examples: text/html, application/json
 
 **Expires:** Cache expiration date. Format: HTTP-date
-```
+````
 
 **After (Use-case organized):**
-```markdown
+
+````markdown
 ## Headers by Purpose
 
 ### Controlling Cache Behavior
 
-**When to use:** Make your site faster by controlling what gets cached and 
+**When to use:** Make your site faster by controlling what gets cached and
 for how long.
 
 #### Long-Term Caching (Static Assets)
@@ -327,15 +351,17 @@ for how long.
 
 **What it does:** Caches content for 1 year
 
-**When to use:** Files that never change, like `logo-v2.png` or 
+**When to use:** Files that never change, like `logo-v2.png` or
 `style.abc123.css` with version hash in filename
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
+````
 
-**Result:** First visitor downloads. Next year, everyone gets the cached 
+**Result:** First visitor downloads. Next year, everyone gets the cached
 version instantly.
 
 ---
@@ -349,6 +375,7 @@ version instantly.
 **When to use:** Content that updates occasionally—blog posts, product pages
 
 **Example:**
+
 ```http
 Cache-Control: public, max-age=3600
 ```
@@ -362,7 +389,8 @@ Cache-Control: public, max-age=3600
 **When to use:** Tell browsers what type of content they're receiving.
 
 [Continue pattern...]
-```
+
+````
 
 **Why this works:**
 - Organized by task, not alphabet
@@ -389,8 +417,9 @@ async function handleRequest(request) {
   const url = new URL(request.url)
   return new Response('Hello')
 }
-```
-```
+````
+
+````
 
 **After (Explained progression):**
 ```markdown
@@ -404,7 +433,7 @@ A working [specific thing] that [specific capability].
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience needed with 
+Developers comfortable with JavaScript. No prior experience needed with
 [platform], but you should understand HTTP requests and JSON.
 
 ### Time: 30 minutes
@@ -428,14 +457,16 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-```
+````
 
 **What this code does:**
+
 - **Line 2:** Listens for HTTP requests to your Worker
-- **Line 4:** Calls `handleRequest` to process each request  
+- **Line 4:** Calls `handleRequest` to process each request
 - **Line 8-12:** Returns a simple text response
 
 **Test it:**
+
 1. Deploy this code
 2. Visit your Worker's URL
 3. You should see: "Hello! It works!"
@@ -445,7 +476,8 @@ Great! Your Worker is running. Now let's add real functionality...
 ## Step 2: Parse URLs
 
 [Continue building progressively with explanations...]
-```
+
+````
 
 **Why this works:**
 - Sets clear expectations upfront
@@ -465,11 +497,13 @@ Features:
 - Global anycast network
 - Automatic scaling
 - Pay-per-request pricing
-```
+````
 
 **After:**
+
 ```markdown
 **What you get:**
+
 - **Fast everywhere:** Code runs in 300+ cities, close to every user
 - **Auto-scaling:** Handles 10 requests or 10 million without configuration
 - **Cost-efficient:** Pay only when code runs, not for idle servers
@@ -478,27 +512,29 @@ Features:
 ### Transform 2: Jargon Explanation → Layered Understanding
 
 **Before:**
+
 ```markdown
-DDoS mitigation employs anycast architecture to distribute volumetric attacks 
-across our edge network, utilizing L3/L4 packet inspection and L7 behavioral 
+DDoS mitigation employs anycast architecture to distribute volumetric attacks
+across our edge network, utilizing L3/L4 packet inspection and L7 behavioral
 analysis.
 ```
 
 **After:**
+
 ```markdown
 **In plain language:** Stops attackers from overwhelming your site with fake traffic.
 
-**How it protects you:** We have 300+ data centers. When an attack hits, we 
-spread it across all locations—like opening thousands of doors instead of one. 
+**How it protects you:** We have 300+ data centers. When an attack hits, we
+spread it across all locations—like opening thousands of doors instead of one.
 We also identify and block fake visitors before they reach your site.
 
-**What happens:** Your real visitors get through normally while attack traffic 
+**What happens:** Your real visitors get through normally while attack traffic
 is filtered out automatically.
 
 <details>
 <summary>For technical users</summary>
 
-Anycast distributes L3/L4 volumetric attacks across the network. L7 protection 
+Anycast distributes L3/L4 volumetric attacks across the network. L7 protection
 uses JS challenges and behavioral fingerprinting. [Architecture details →]
 
 </details>
@@ -507,21 +543,24 @@ uses JS challenges and behavioral fingerprinting. [Architecture details →]
 ### Transform 3: Assumed Knowledge → Explicit Prerequisites
 
 **Before:**
+
 ```markdown
 Configure your A record to point to the anycast IP.
 ```
 
 **After:**
+
 ```markdown
 Update your DNS A record to point to Cloudflare's IP address.
 
-**What's an A record?** It's the DNS entry that tells the internet where your 
+**What's an A record?** It's the DNS entry that tells the internet where your
 website lives (like an address in a phone book).
 
-**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap, 
+**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap,
 etc.). Look for "DNS Management" or "DNS Settings."
 
-**What to enter:** 
+**What to enter:**
+
 - Type: A
 - Name: @ (means your root domain)
 - Value: 192.0.2.1 (our IP address)
@@ -532,10 +571,12 @@ etc.). Look for "DNS Management" or "DNS Settings."
 ## Metaphor Templates
 
 ### Template: API Explanation
+
 ```markdown
 **Think of it like:** [Familiar interface concept]
 
 An API is like a restaurant menu. It shows you:
+
 - What's available to order (endpoints)
 - What details you need to provide (parameters: "no onions, extra cheese")
 - What you'll get back (response: your meal)
@@ -543,11 +584,12 @@ An API is like a restaurant menu. It shows you:
 
 You don't need to know how the kitchen works. Just order from the menu.
 
-**Where this breaks down:** Unlike restaurants where you wait, API responses 
+**Where this breaks down:** Unlike restaurants where you wait, API responses
 are usually instant. Also, APIs can return errors if your "order" is invalid.
 ```
 
 ### Template: Security Feature Explanation
+
 ```markdown
 **The threat:** [What attackers do]
 
@@ -559,22 +601,26 @@ Think of it like [security analogy]:
 [Concrete comparison that shows the protection model]
 
 **What happens automatically:**
+
 - [Protection 1]
 - [Protection 2]
 
 **What you control:**
+
 - [Setting 1]
 - [Setting 2]
 ```
 
 ### Template: Infrastructure Concept
+
 ```markdown
 **What it is:** [One-sentence plain English definition]
 
-**Real-world comparison:** 
+**Real-world comparison:**
 [Physical/familiar tech analog that maps 1:1 to key concepts]
 
 **Why it matters:**
+
 - [Benefit 1 with measurable impact]
 - [Benefit 2 with measurable impact]
 
@@ -590,24 +636,25 @@ Think of it like [security analogy]:
 
 ### When You See → Do This
 
-| **Original** | **Transform To** |
-|--------------|------------------|
-| Technical architecture first | Problem → Solution → Benefit |
-| Abstract concept | Analogy → Plain explanation → Technical |
-| Steps without context | Context → Prerequisites → Multi-path steps |
-| Alphabetical reference | Use-case groups → Two-tier descriptions |
-| Unexplained code | What you'll build → Progressive steps → Explained blocks |
-| Feature list | Problem/solution pairs with benefits |
-| Jargon without definition | Define inline or use plain alternative |
-| Missing "why" | Add value proposition upfront |
-| No use cases | Add 3-5 realistic scenarios |
-| Assumes knowledge | State prerequisites explicitly |
+| **Original**                 | **Transform To**                                         |
+| ---------------------------- | -------------------------------------------------------- |
+| Technical architecture first | Problem → Solution → Benefit                             |
+| Abstract concept             | Analogy → Plain explanation → Technical                  |
+| Steps without context        | Context → Prerequisites → Multi-path steps               |
+| Alphabetical reference       | Use-case groups → Two-tier descriptions                  |
+| Unexplained code             | What you'll build → Progressive steps → Explained blocks |
+| Feature list                 | Problem/solution pairs with benefits                     |
+| Jargon without definition    | Define inline or use plain alternative                   |
+| Missing "why"                | Add value proposition upfront                            |
+| No use cases                 | Add 3-5 realistic scenarios                              |
+| Assumes knowledge            | State prerequisites explicitly                           |
 
 ---
 
 ## Best Practices Summary
 
 ### Do:
+
 ✅ Lead with benefits and problems solved  
 ✅ Use tech-adjacent metaphors with stated limitations  
 ✅ Provide both Dashboard and API paths  
@@ -615,9 +662,10 @@ Think of it like [security analogy]:
 ✅ Explain every code block  
 ✅ State prerequisites before steps  
 ✅ Include verification/testing sections  
-✅ Add "For technical users" collapsible sections  
+✅ Add "For technical users" collapsible sections
 
 ### Don't:
+
 ❌ Start with technical architecture  
 ❌ Use condescending language ("simply," "just," "obviously")  
 ❌ Assume prior knowledge without stating it  
@@ -625,7 +673,7 @@ Think of it like [security analogy]:
 ❌ Organize specs alphabetically without context  
 ❌ Drop code without explanation  
 ❌ Skip the "why" to get to "how" faster  
-❌ Sacrifice accuracy for brevity  
+❌ Sacrifice accuracy for brevity
 
 ---
 
diff --git a/.github/review-template.md b/.github/review-template.md
index 0e56cc03451cac7..4aee0df6e1cf7ed 100644
--- a/.github/review-template.md
+++ b/.github/review-template.md
@@ -1,8 +1,9 @@
 ## Author self-review
 
 I've reviewed my PR for the following:
+
 - [ ] Metadata in the frontmatter, including `pcx_content_type` and - for tutorials - `updated: YYYY-MM-DD`.
 - [ ] PCX content strategy overall.
 - [ ] PCX style guidelines (product names, capitalization, etc.).
 - [ ] Needed redirects (if deleting any existing pages).
-- [ ] Code blocks && other formatting issues (bolding, italics, lists).
\ No newline at end of file
+- [ ] Code blocks && other formatting issues (bolding, italics, lists).
diff --git a/.opencode/command/styleguide.md b/.opencode/command/styleguide.md
index 085e070750f199c..fbacc3b8e40c886 100644
--- a/.opencode/command/styleguide.md
+++ b/.opencode/command/styleguide.md
@@ -49,6 +49,7 @@ Look at all the unstaged changes to markdown (.md, .mdx) files, pull out the lin
 ## Output Format
 
 For each issue found, report:
+
 - The problematic text (quote it)
 - Which rule it violates
 - A suggested fix
diff --git a/.windsurf/rules/general-rules.md b/.windsurf/rules/general-rules.md
index e563c09c965c3cf..7efe2f90487c8d4 100644
--- a/.windsurf/rules/general-rules.md
+++ b/.windsurf/rules/general-rules.md
@@ -61,4 +61,4 @@ This code would only be rendered if the page has a magicWord variable set to "ha
 - Replace `sh` blocks using `npm commands` with our [`PackageManagers` component](https://developers.cloudflare.com/style-guide/components/package-managers/).
 - Replace in-text mentions of Cloudflare's number of data centers, network capacity, or network peers with our [`PublicStats` component](https://developers.cloudflare.com/style-guide/components/public-stats/).
 - Replace `toml` or `json` code blocks with [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/#sample-wrangler-configuration) information with our [`WranglerConfig` component](https://developers.cloudflare.com/style-guide/components/wrangler-config/).
-- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
\ No newline at end of file
+- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7d3e71c75126c9f..198fa9cdc3bf951 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,9 +1,10 @@
 # Contributing to Cloudflare's developer documentation
 
 Everyone, including those who are not part of the Cloudflare organization, are encouraged to contribute.
+
 - If you are not a Cloudflare employee, learn how to contribute in the [contribution page](https://developers.cloudflare.com/style-guide/contributions/) of the Cloudflare Style Guide.
 - If you are a Cloudflare employee, reach out via our Developer Docs space in Google chat.
 
 Consult the [Cloudflare Style Guide](https://developers.cloudflare.com/style-guide/) on everything from grammar, to formatting, to frontmatter requirements. Browse our [components](/style-guide/components/) to add additional formatting.
 
-Thank you for helping us to maintain quality documentation.
\ No newline at end of file
+Thank you for helping us to maintain quality documentation.
diff --git a/MIGRATION.md b/MIGRATION.md
index 622c020aee16f4d..4ac50851fe0e52b 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -18,7 +18,7 @@
 ## High-risk items and unknowns
 
 | Item                                                  | Risk   | Status                                                        |
-|-------------------------------------------------------|--------|---------------------------------------------------------------|
+| ----------------------------------------------------- | ------ | ------------------------------------------------------------- |
 | **`Page.astro` Vite alias**                           | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`patch-package` hunks against Starlight internals** | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`starlight-links-validator` Zod 4 incompatibility** | HIGH   | Confirmed broken upstream                                     |
@@ -42,7 +42,7 @@ Targets are determined by [withastro/docs#13230].
 That is the north star.
 
 | Package                        | Current  | Target                                                 |
-| ------------------------------ | -------- |--------------------------------------------------------|
+| ------------------------------ | -------- | ------------------------------------------------------ |
 | `astro`                        | `5.13.7` | `6.0.0-beta.8`                                         |
 | `@astrojs/starlight`           | `0.36.0` | `https://pkg.pr.new/@astrojs/starlight@3644`           |
 | `@astrojs/starlight-docsearch` | `0.6.0`  | `https://pkg.pr.new/@astrojs/starlight-docsearch@3644` |
diff --git a/src/components/AutoconfigDiagram.astro b/src/components/AutoconfigDiagram.astro
index dafb15f5e6c8c24..bc843cdd921273a 100644
--- a/src/components/AutoconfigDiagram.astro
+++ b/src/components/AutoconfigDiagram.astro
@@ -21,10 +21,15 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon">
 						<slot name="icon">
-							<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								viewBox="0 0 24 24"
+								fill="none"
+								stroke="currentColor"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</slot>
 					</div>
@@ -43,15 +48,17 @@ const { framework, configs } = Astro.props;
 				<div class="config-box">
 					<span class="config-title">Generated configuration</span>
 					<div class="config-items">
-						{configs.map((config, i) => (
-							<div class="config-item" data-config-index={i}>
-								<div class="config-file">{config.file}</div>
-								<div class="config-detail">
-									<span class="config-label">{config.label}:</span>
-									<span class="config-value">{config.value}</span>
+						{
+							configs.map((config, i) => (
+								<div class="config-item" data-config-index={i}>
+									<div class="config-file">{config.file}</div>
+									<div class="config-detail">
+										<span class="config-label">{config.label}:</span>
+										<span class="config-value">{config.value}</span>
+									</div>
 								</div>
-							</div>
-						))}
+							))
+						}
 					</div>
 				</div>
 			</div>
@@ -64,8 +71,12 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon workers-icon">
 						<svg viewBox="0 0 24 24" fill="none">
-							<path d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z" fill="#F6821F"/>
-							<path d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z" fill="#FBAD41"/>
+							<path
+								d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z"
+								fill="#F6821F"></path>
+							<path
+								d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z"
+								fill="#FBAD41"></path>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -79,7 +90,9 @@ const { framework, configs } = Astro.props;
 		<!-- Status indicator -->
 		<div class="status-indicator">
 			<div class="status-dot"></div>
-			<span class="status-text">Wrangler handles configuration automatically</span>
+			<span class="status-text"
+				>Wrangler handles configuration automatically</span
+			>
 		</div>
 	</div>
 </autoconfig-diagram>
@@ -131,7 +144,9 @@ const { framework, configs } = Astro.props;
 		padding: 0.75rem 1rem;
 		border: 1px solid rgb(229 229 229);
 		min-width: 120px;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -323,7 +338,8 @@ const { framework, configs } = Astro.props;
 
 	.config-file {
 		font-size: 0.625rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		color: rgb(115 115 115);
 		margin-bottom: 0.125rem;
 	}
@@ -334,7 +350,8 @@ const { framework, configs } = Astro.props;
 
 	.config-detail {
 		font-size: 0.6875rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 	}
 
 	.config-label {
@@ -393,8 +410,13 @@ const { framework, configs } = Astro.props;
 	}
 
 	@keyframes pulse {
-		0%, 100% { opacity: 1; }
-		50% { opacity: 0.5; }
+		0%,
+		100% {
+			opacity: 1;
+		}
+		50% {
+			opacity: 0.5;
+		}
 	}
 
 	.status-text {
@@ -415,10 +437,10 @@ const { framework, configs } = Astro.props;
 <script>
 	class AutoconfigDiagram extends HTMLElement {
 		private isRunning = false;
-		private framework = '';
+		private framework = "";
 
 		connectedCallback() {
-			this.framework = this.dataset.framework || '';
+			this.framework = this.dataset.framework || "";
 			// Auto-start after a short delay
 			setTimeout(() => this.run(), 500);
 		}
@@ -427,87 +449,90 @@ const { framework, configs } = Astro.props;
 			if (this.isRunning) return;
 			this.isRunning = true;
 
-			const statusIndicator = this.querySelector('.status-indicator');
-			const statusText = this.querySelector('.status-text');
+			const statusIndicator = this.querySelector(".status-indicator");
+			const statusText = this.querySelector(".status-text");
 
 			// Reset state
 			this.resetState();
 
 			// Update status
-			statusIndicator?.classList.add('running');
-			if (statusText) statusText.textContent = `Detecting ${this.framework} project...`;
+			statusIndicator?.classList.add("running");
+			if (statusText)
+				statusText.textContent = `Detecting ${this.framework} project...`;
 
 			await this.delay(900);
 
 			// Step 1: Framework detected
-			const frameworkNode = this.querySelector('.framework-node');
-			frameworkNode?.classList.add('active');
+			const frameworkNode = this.querySelector(".framework-node");
+			frameworkNode?.classList.add("active");
 			if (statusText) statusText.textContent = `${this.framework} detected`;
 
 			await this.delay(1200);
 
 			// Step 2: First connector
-			const connectors = this.querySelectorAll('.connector');
-			connectors[0]?.classList.add('active');
+			const connectors = this.querySelectorAll(".connector");
+			connectors[0]?.classList.add("active");
 
 			await this.delay(600);
 
 			// Step 3: Config section
-			const configSection = this.querySelector('.config-section');
-			configSection?.classList.add('active');
-			if (statusText) statusText.textContent = 'Generating configuration...';
+			const configSection = this.querySelector(".config-section");
+			configSection?.classList.add("active");
+			if (statusText) statusText.textContent = "Generating configuration...";
 
 			await this.delay(600);
 
 			// Show config items one by one
-			const configItems = this.querySelectorAll('.config-item');
+			const configItems = this.querySelectorAll(".config-item");
 			for (let i = 0; i < configItems.length; i++) {
 				const item = configItems[i];
-				item.classList.add('visible', 'active');
-				
+				item.classList.add("visible", "active");
+
 				// Get the config value for status
-				const valueEl = item.querySelector('.config-value');
-				const labelEl = item.querySelector('.config-label');
+				const valueEl = item.querySelector(".config-value");
+				const labelEl = item.querySelector(".config-label");
 				if (valueEl && labelEl) {
-					const label = labelEl.textContent?.replace(':', '') || '';
-					const value = valueEl.textContent || '';
-					if (statusText) statusText.textContent = `Setting ${label} → ${value}`;
+					const label = labelEl.textContent?.replace(":", "") || "";
+					const value = valueEl.textContent || "";
+					if (statusText)
+						statusText.textContent = `Setting ${label} → ${value}`;
 				}
 
 				await this.delay(1400);
-				item.classList.remove('active');
+				item.classList.remove("active");
 			}
 
 			await this.delay(500);
 
 			// Step 4: Second connector
-			connectors[1]?.classList.add('active');
-			if (statusText) statusText.textContent = 'Deploying to Workers...';
+			connectors[1]?.classList.add("active");
+			if (statusText) statusText.textContent = "Deploying to Workers...";
 
 			await this.delay(900);
 
 			// Step 5: Workers node
-			const workersNode = this.querySelector('.workers-node');
-			workersNode?.classList.add('active');
+			const workersNode = this.querySelector(".workers-node");
+			workersNode?.classList.add("active");
 
 			await this.delay(600);
 
 			// Complete - keep orange theme
-			frameworkNode?.classList.remove('active');
-			frameworkNode?.classList.add('connected');
-			configSection?.classList.remove('active');
-			configSection?.classList.add('connected');
-			connectors.forEach(c => {
-				c.classList.remove('active');
-				c.classList.add('connected');
+			frameworkNode?.classList.remove("active");
+			frameworkNode?.classList.add("connected");
+			configSection?.classList.remove("active");
+			configSection?.classList.add("connected");
+			connectors.forEach((c) => {
+				c.classList.remove("active");
+				c.classList.add("connected");
 			});
-			configItems.forEach(item => item.classList.add('visible'));
-			workersNode?.classList.remove('active');
-			workersNode?.classList.add('connected');
+			configItems.forEach((item) => item.classList.add("visible"));
+			workersNode?.classList.remove("active");
+			workersNode?.classList.add("connected");
 
-			statusIndicator?.classList.remove('running');
-			statusIndicator?.classList.add('complete');
-			if (statusText) statusText.textContent = 'Deployed to Cloudflare Workers!';
+			statusIndicator?.classList.remove("running");
+			statusIndicator?.classList.add("complete");
+			if (statusText)
+				statusText.textContent = "Deployed to Cloudflare Workers!";
 
 			this.isRunning = false;
 
@@ -518,18 +543,18 @@ const { framework, configs } = Astro.props;
 
 		private resetState() {
 			// Remove all state classes
-			this.querySelectorAll('.active, .connected, .visible').forEach(el => {
-				el.classList.remove('active', 'connected', 'visible');
+			this.querySelectorAll(".active, .connected, .visible").forEach((el) => {
+				el.classList.remove("active", "connected", "visible");
 			});
-			
-			const statusIndicator = this.querySelector('.status-indicator');
-			statusIndicator?.classList.remove('running', 'complete');
+
+			const statusIndicator = this.querySelector(".status-indicator");
+			statusIndicator?.classList.remove("running", "complete");
 		}
 
 		private delay(ms: number): Promise<void> {
-			return new Promise(resolve => setTimeout(resolve, ms));
+			return new Promise((resolve) => setTimeout(resolve, ms));
 		}
 	}
 
-	customElements.define('autoconfig-diagram', AutoconfigDiagram);
+	customElements.define("autoconfig-diagram", AutoconfigDiagram);
 </script>
diff --git a/src/components/ComponentUsage.astro b/src/components/ComponentUsage.astro
index 4a3bf2d7677a098..66ee88e6d14b810 100644
--- a/src/components/ComponentUsage.astro
+++ b/src/components/ComponentUsage.astro
@@ -18,7 +18,8 @@ const usage = await getComponentsUsage(component);
 
 <>
 	<p>
-		The <code>{component}</code> component is used <code>{usage.count}</code> times on{" "}
+		The <code>{component}</code> component is used <code>{usage.count}</code> times
+		on{" "}
 		<code>{usage.pages.size}</code> pages.
 	</p>
 	<Details header={`See all examples of pages that use ${component}`}>
diff --git a/src/components/FeatureTable.astro b/src/components/FeatureTable.astro
index 8af0f2ee817b163..e9dd6c485730d49 100644
--- a/src/components/FeatureTable.astro
+++ b/src/components/FeatureTable.astro
@@ -34,12 +34,44 @@ const markdown = (content: any) => {
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"></th>
-			{hasFree && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Free</th>}
-			{hasPro && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Pro</th>}
-			{hasBiz && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Business</th>}
-			{hasEnt && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Enterprise</th>}
-			{hasEntPlus && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">{plan.ent_plus}</th>}
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+			></th>
+			{
+				hasFree && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Free
+					</th>
+				)
+			}
+			{
+				hasPro && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Pro
+					</th>
+				)
+			}
+			{
+				hasBiz && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Business
+					</th>
+				)
+			}
+			{
+				hasEnt && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						Enterprise
+					</th>
+				)
+			}
+			{
+				hasEntPlus && (
+					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
+						{plan.ent_plus}
+					</th>
+				)
+			}
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/LayerCard.astro b/src/components/LayerCard.astro
index f809ad95620577b..52528db54e544c5 100644
--- a/src/components/LayerCard.astro
+++ b/src/components/LayerCard.astro
@@ -8,17 +8,17 @@ const { header = "Next Steps", href } = Astro.props;
 ---
 
 <div
-	class="flex w-full flex-col overflow-hidden rounded-lg bg-cl1-gray-9 text-base ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1"
+	class="bg-cl1-gray-9 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1 flex w-full flex-col overflow-hidden rounded-lg text-base ring-1"
 >
 	<div
-		class="-my-2 flex items-center justify-between gap-2 bg-cl1-gray-9 p-4 text-base font-medium text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7"
+		class="bg-cl1-gray-9 text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7 -my-2 flex items-center justify-between gap-2 p-4 text-base font-medium"
 	>
 		<div>{header}</div>
 		{
 			href && (
 				<a
 					href={href}
-					class="flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent text-cl1-gray-0 no-underline hover:bg-cl1-gray-8 focus-visible:outline focus-visible:outline-1 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3"
+					class="text-cl1-gray-0 hover:bg-cl1-gray-8 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3 flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent no-underline focus-visible:outline focus-visible:outline-1"
 					aria-label={`Go to ${header.toLowerCase()}`}
 				>
 					<svg
@@ -35,7 +35,7 @@ const { header = "Next Steps", href } = Astro.props;
 		}
 	</div>
 	<div
-		class="relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg bg-cl1-white p-4 pr-3 ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2"
+		class="bg-cl1-white ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2 relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg p-4 pr-3 ring-1"
 	>
 		<slot />
 	</div>
diff --git a/src/components/LlmsTxtDirective.astro b/src/components/LlmsTxtDirective.astro
index f9ea644e578be8b..87d72771289a198 100644
--- a/src/components/LlmsTxtDirective.astro
+++ b/src/components/LlmsTxtDirective.astro
@@ -11,9 +11,9 @@ const llmsTxt = productPrefix
 ---
 
 <blockquote class="llms-txt-directive" aria-hidden="true">
-Documentation Index<br/>
-Fetch the complete documentation index at: {llmsTxt}<br/>
-Use this file to discover all available pages before exploring further.
+	Documentation Index<br />
+	Fetch the complete documentation index at: {llmsTxt}<br />
+	Use this file to discover all available pages before exploring further.
 </blockquote>
 
 <style>
diff --git a/src/components/PagesBuildPresetsTable.astro b/src/components/PagesBuildPresetsTable.astro
index 93b77d7c42a275a..6383eeb9e7e6adc 100644
--- a/src/components/PagesBuildPresetsTable.astro
+++ b/src/components/PagesBuildPresetsTable.astro
@@ -14,9 +14,18 @@ const entries = Object.values(presets);
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Framework/tool</th>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build command</th>
-			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build directory</th>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Framework/tool</th
+			>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Build command</th
+			>
+			<th
+				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
+				>Build directory</th
+			>
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/ProductReleaseNotes.astro b/src/components/ProductReleaseNotes.astro
index df5a3cc1ee2cd47..5cf7314aeee4f17 100644
--- a/src/components/ProductReleaseNotes.astro
+++ b/src/components/ProductReleaseNotes.astro
@@ -15,9 +15,7 @@ if (!page) {
 	);
 }
 
-if (
-	!page.data.release_notes_file_name
-) {
+if (!page.data.release_notes_file_name) {
 	throw new Error(
 		`[ProductReleaseNotes] ${Astro.params.slug} does not have a 'release_notes_file_name' frontmatter property.`,
 	);
@@ -32,8 +30,7 @@ if (
 	);
 }
 
-const name =
-	page.data.release_notes_file_name?.[0];
+const name = page.data.release_notes_file_name?.[0];
 
 let releaseNotes;
 
diff --git a/src/components/R2LocalUploadsdiagram.astro b/src/components/R2LocalUploadsdiagram.astro
index 6d717c9406d70af..067f6f1892e41e6 100644
--- a/src/components/R2LocalUploadsdiagram.astro
+++ b/src/components/R2LocalUploadsdiagram.astro
@@ -1,32 +1,49 @@
 ---
 interface Props {
-	mode?: 'without' | 'with' | 'comparison';
+	mode?: "without" | "with" | "comparison";
 	autoPlay?: boolean;
 	loop?: boolean;
 }
 
-const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
+const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 ---
 
-<r2-local-uploads-diagram data-mode={mode} data-autoplay={autoPlay} data-loop={loop}>
+<r2-local-uploads-diagram
+	data-mode={mode}
+	data-autoplay={autoPlay}
+	data-loop={loop}
+>
 	<div class="diagram-wrapper">
-		{mode === 'comparison' && (
-			<div class="toggle-container">
-				<span class="toggle-label" id="local-uploads-label">Local uploads</span>
-				<label class="toggle-switch" aria-labelledby="local-uploads-label">
-					<input type="checkbox" class="toggle-input" aria-labelledby="local-uploads-label" />
-					<span class="toggle-slider"></span>
-				</label>
-			</div>
-		)}
+		{
+			mode === "comparison" && (
+				<div class="toggle-container">
+					<span class="toggle-label" id="local-uploads-label">
+						Local uploads
+					</span>
+					<label class="toggle-switch" aria-labelledby="local-uploads-label">
+						<input
+							type="checkbox"
+							class="toggle-input"
+							aria-labelledby="local-uploads-label"
+						/>
+						<span class="toggle-slider" />
+					</label>
+				</div>
+			)
+		}
 		<div class="diagram-container">
 			<!-- Client node -->
 			<div class="flow-node" data-step="1">
 				<div class="node-card">
 					<div class="node-badge">
-						<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-							<rect x="3" y="4" width="18" height="12" rx="2"/>
-							<path d="M7 20h10M12 16v4"/>
+						<svg
+							fill="none"
+							stroke="currentColor"
+							viewBox="0 0 24 24"
+							stroke-width="2"
+						>
+							<rect x="3" y="4" width="18" height="12" rx="2"></rect>
+							<path d="M7 20h10M12 16v4"></path>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -46,10 +63,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				<div class="group-content edge-single">
 					<div class="bucket-component gateway-node-without">
 						<div class="component-icon gateway">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -61,21 +83,74 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			<div class="split-area without-local-uploads" data-connector="2-bucket">
 				<svg class="split-svg" viewBox="0 0 320 100" preserveAspectRatio="none">
 					<!-- Stem from node above -->
-					<line class="split-line stem data-path" x1="160" y1="0" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line stem data-path"
+						x1="160"
+						y1="0"
+						x2="160"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Horizontal bar - left half (metadata) -->
-					<line class="split-line horizontal-left metadata-path" x1="85" y1="20" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line horizontal-left metadata-path"
+						x1="85"
+						y1="20"
+						x2="160"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Horizontal bar - right half (object data) -->
-					<line class="split-line horizontal-right data-path" x1="160" y1="20" x2="235" y2="20" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line horizontal-right data-path"
+						x1="160"
+						y1="20"
+						x2="235"
+						y2="20"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Left branch (metadata) -->
-					<line class="split-line left-branch-top metadata-path" x1="85" y1="20" x2="85" y2="50" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line left-branch-top metadata-path"
+						x1="85"
+						y1="20"
+						x2="85"
+						y2="50"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Right branch (object data) -->
-					<line class="split-line right-branch-top data-path" x1="235" y1="20" x2="235" y2="50" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line right-branch-top data-path"
+						x1="235"
+						y1="20"
+						x2="235"
+						y2="50"
+						stroke="currentColor"
+						stroke-width="2"></line>
 					<!-- Labels positioned on the lines -->
-					<text x="85" y="67" text-anchor="middle" class="svg-label">Object metadata</text>
-					<text x="235" y="67" text-anchor="middle" class="svg-label">Object data</text>
+					<text x="85" y="67" text-anchor="middle" class="svg-label"
+						>Object metadata</text
+					>
+					<text x="235" y="67" text-anchor="middle" class="svg-label"
+						>Object data</text
+					>
 					<!-- Continue lines to bucket -->
-					<line class="split-line left-branch-bottom metadata-path" x1="85" y1="72" x2="85" y2="100" stroke="currentColor" stroke-width="2"/>
-					<line class="split-line right-branch-bottom data-path" x1="235" y1="72" x2="235" y2="100" stroke="currentColor" stroke-width="2"/>
+					<line
+						class="split-line left-branch-bottom metadata-path"
+						x1="85"
+						y1="72"
+						x2="85"
+						y2="100"
+						stroke="currentColor"
+						stroke-width="2"></line>
+					<line
+						class="split-line right-branch-bottom data-path"
+						x1="235"
+						y1="72"
+						x2="235"
+						y2="100"
+						stroke="currentColor"
+						stroke-width="2"></line>
 				</svg>
 			</div>
 
@@ -87,10 +162,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<!-- R2 Gateway Worker -->
 					<div class="bucket-component gateway-node-local">
 						<div class="component-icon gateway">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
-								<path d="M2 17l10 5 10-5"/>
-								<path d="M2 12l10 5 10-5"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
+								<path d="M2 17l10 5 10-5"></path>
+								<path d="M2 12l10 5 10-5"></path>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -100,10 +180,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<!-- Local Object Data Infra -->
 					<div class="bucket-component local-storage-node">
 						<div class="component-icon storage">
-							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-								<ellipse cx="12" cy="6" rx="8" ry="3"/>
-								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
-								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
+							<svg
+								fill="none"
+								stroke="currentColor"
+								viewBox="0 0 24 24"
+								stroke-width="2"
+							>
+								<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
+								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
+								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
 							</svg>
 						</div>
 						<span class="component-name">Object Data Infra</span>
@@ -112,7 +197,10 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			</div>
 
 			<!-- WITH local uploads: Two lines down to bucket -->
-			<div class="local-split-columns with-local-uploads hidden" data-connector="local-split">
+			<div
+				class="local-split-columns with-local-uploads hidden"
+				data-connector="local-split"
+			>
 				<div class="split-col left-col">
 					<div class="v-connector meta-line"></div>
 					<div class="split-label-row">
@@ -124,8 +212,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<div class="v-connector replication-line"></div>
 					<div class="split-label-row">
 						<svg class="progress-ring" viewBox="0 0 20 20">
-							<circle class="progress-ring-bg" cx="10" cy="10" r="8" />
-							<circle class="progress-ring-fill" cx="10" cy="10" r="8" />
+							<circle class="progress-ring-bg" cx="10" cy="10" r="8"></circle>
+							<circle class="progress-ring-fill" cx="10" cy="10" r="8"></circle>
 						</svg>
 						<span class="split-col-label replication">Object data</span>
 					</div>
@@ -141,19 +229,31 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 					<div class="group-content">
 						<div class="bucket-component" data-component="metadata">
 							<div class="component-icon">
-								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-									<circle cx="12" cy="12" r="10"/>
-									<path d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"/>
+								<svg
+									fill="none"
+									stroke="currentColor"
+									viewBox="0 0 24 24"
+									stroke-width="2"
+								>
+									<circle cx="12" cy="12" r="10"></circle>
+									<path
+										d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"
+									></path>
 								</svg>
 							</div>
 							<span class="component-name">Metadata Service</span>
 						</div>
 						<div class="bucket-component" data-component="object-data">
 							<div class="component-icon">
-								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
-									<ellipse cx="12" cy="6" rx="8" ry="3"/>
-									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
-									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
+								<svg
+									fill="none"
+									stroke="currentColor"
+									viewBox="0 0 24 24"
+									stroke-width="2"
+								>
+									<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
+									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
+									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
 								</svg>
 							</div>
 							<span class="component-name">Object Data Infra</span>
@@ -164,9 +264,15 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		</div>
 		<!-- Status indicator -->
 		<div class="status-indicator">
-			<svg class="status-check" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.5">
-				<circle cx="12" cy="12" r="10" class="status-circle" />
-				<path d="M8 12l3 3 5-5" class="status-checkmark" />
+			<svg
+				class="status-check"
+				viewBox="0 0 24 24"
+				fill="none"
+				stroke="currentColor"
+				stroke-width="2.5"
+			>
+				<circle cx="12" cy="12" r="10" class="status-circle"></circle>
+				<path d="M8 12l3 3 5-5" class="status-checkmark"></path>
 			</svg>
 			<span class="status-text">Data is uploaded and accessible</span>
 		</div>
@@ -270,8 +376,6 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		width: 100%;
 	}
 
-
-
 	/* Vertical connector line between nodes */
 	.connector {
 		width: 2px;
@@ -303,7 +407,9 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		border: 1px solid rgb(229 229 229);
 		width: 220px;
 		margin: 0 !important;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -366,7 +472,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 
 	.node-name {
 		font-size: 0.8125rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 	}
@@ -535,7 +642,9 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		padding: 0.5rem;
 		margin: 0 !important;
 		box-sizing: border-box;
-		transition: border-color 0.3s ease, box-shadow 0.3s ease;
+		transition:
+			border-color 0.3s ease,
+			box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .bucket-component {
@@ -571,7 +680,8 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 
 	.component-name {
 		font-size: 0.625rem;
-		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family:
+			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 		text-align: center;
@@ -654,8 +764,6 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		color: rgb(249 115 22);
 	}
 
-
-
 	/* Note text under component name */
 	.component-note {
 		font-size: 0.5rem;
@@ -883,42 +991,50 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 		private playTimeout: number | null = null;
 
 		connectedCallback() {
-			this.loop = this.dataset.loop === 'true';
-			
-			const toggleInput = this.querySelector('.toggle-input') as HTMLInputElement;
+			this.loop = this.dataset.loop === "true";
+
+			const toggleInput = this.querySelector(
+				".toggle-input",
+			) as HTMLInputElement;
 			if (toggleInput) {
-				toggleInput.addEventListener('change', () => {
+				toggleInput.addEventListener("change", () => {
 					this.localUploadsEnabled = toggleInput.checked;
-					this.setMode(toggleInput.checked ? 'with' : 'without');
+					this.setMode(toggleInput.checked ? "with" : "without");
 					this.resetAnimation();
-					if (this.dataset.autoplay === 'true') {
-						this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
+					if (this.dataset.autoplay === "true") {
+						this.playTimeout = setTimeout(
+							() => this.play(),
+							500,
+						) as unknown as number;
 					}
 				});
 			}
 
-			if (this.dataset.autoplay === 'true') {
-				this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
+			if (this.dataset.autoplay === "true") {
+				this.playTimeout = setTimeout(
+					() => this.play(),
+					500,
+				) as unknown as number;
 			}
 		}
 
-		private setMode(mode: 'without' | 'with') {
-			const withoutElements = this.querySelectorAll('.without-local-uploads');
-			const withElements = this.querySelectorAll('.with-local-uploads');
+		private setMode(mode: "without" | "with") {
+			const withoutElements = this.querySelectorAll(".without-local-uploads");
+			const withElements = this.querySelectorAll(".with-local-uploads");
 
-			if (mode === 'without') {
-				withoutElements.forEach(el => el.classList.remove('hidden'));
-				withElements.forEach(el => el.classList.add('hidden'));
+			if (mode === "without") {
+				withoutElements.forEach((el) => el.classList.remove("hidden"));
+				withElements.forEach((el) => el.classList.add("hidden"));
 			} else {
-				withoutElements.forEach(el => el.classList.add('hidden'));
-				withElements.forEach(el => el.classList.remove('hidden'));
+				withoutElements.forEach((el) => el.classList.add("hidden"));
+				withElements.forEach((el) => el.classList.remove("hidden"));
 			}
 		}
 
 		private resetAnimation() {
 			this.currentStep = 0;
 			this.isPlaying = false;
-			
+
 			// Clear any pending timeouts
 			if (this.stepTimeout !== null) {
 				clearTimeout(this.stepTimeout);
@@ -928,12 +1044,20 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				clearTimeout(this.playTimeout);
 				this.playTimeout = null;
 			}
-			
+
 			// Remove all active and animating states
-			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
-			this.querySelectorAll('.animating').forEach(el => el.classList.remove('animating'));
-			this.querySelectorAll('.data-animating').forEach(el => el.classList.remove('data-animating'));
-			this.querySelectorAll('.metadata-active').forEach(el => el.classList.remove('metadata-active'));
+			this.querySelectorAll(".active").forEach((el) =>
+				el.classList.remove("active"),
+			);
+			this.querySelectorAll(".animating").forEach((el) =>
+				el.classList.remove("animating"),
+			);
+			this.querySelectorAll(".data-animating").forEach((el) =>
+				el.classList.remove("data-animating"),
+			);
+			this.querySelectorAll(".metadata-active").forEach((el) =>
+				el.classList.remove("metadata-active"),
+			);
 		}
 
 		private play() {
@@ -953,7 +1077,10 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 				if (this.loop) {
 					// Reset and restart
 					this.resetAnimation();
-					this.playTimeout = setTimeout(() => this.play(), 1000) as unknown as number;
+					this.playTimeout = setTimeout(
+						() => this.play(),
+						1000,
+					) as unknown as number;
 				} else {
 					this.isPlaying = false;
 				}
@@ -961,7 +1088,7 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			}
 
 			this.updateDiagram();
-			
+
 			// Duration for each step
 			let duration = 1200;
 			if (!this.localUploadsEnabled && this.currentStep === 4) {
@@ -973,12 +1100,17 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			} else if (this.localUploadsEnabled && this.currentStep === 9) {
 				duration = 2500; // Linger on final step with status indicator
 			}
-			this.stepTimeout = setTimeout(() => this.advanceStep(), duration) as unknown as number;
+			this.stepTimeout = setTimeout(
+				() => this.advanceStep(),
+				duration,
+			) as unknown as number;
 		}
 
 		private updateDiagram() {
 			// Remove all active states first
-			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
+			this.querySelectorAll(".active").forEach((el) =>
+				el.classList.remove("active"),
+			);
 
 			if (this.localUploadsEnabled) {
 				this.updateWithLocalUploads();
@@ -991,49 +1123,53 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client node lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add('active');
+				clientNode?.classList.add("active");
 			}
 
 			// Step 2: Connector from client to EDGE lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add('active');
+				connector1?.classList.add("active");
 			}
 
 			// Step 3: EDGE box border + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector('.region-box.without-local-uploads');
-				const gatewayNode = this.querySelector('.gateway-node-without');
-				edgeBox?.classList.add('active');
-				gatewayNode?.classList.add('active');
+				const edgeBox = this.querySelector(".region-box.without-local-uploads");
+				const gatewayNode = this.querySelector(".gateway-node-without");
+				edgeBox?.classList.add("active");
+				gatewayNode?.classList.add("active");
 			}
 
 			// Step 4: Object data line starts animating
 			if (this.currentStep >= 4) {
-				const splitArea = this.querySelector('.split-area');
-				splitArea?.classList.add('data-animating');
+				const splitArea = this.querySelector(".split-area");
+				splitArea?.classList.add("data-animating");
 			}
 
 			// Step 5: Object Data Infra lights up
 			if (this.currentStep >= 5) {
-				const objectDataComponent = this.querySelector('[data-component="object-data"]');
-				objectDataComponent?.classList.add('active');
+				const objectDataComponent = this.querySelector(
+					'[data-component="object-data"]',
+				);
+				objectDataComponent?.classList.add("active");
 			}
 
 			// Step 6: Object metadata line lights up
 			if (this.currentStep >= 6) {
-				const splitArea = this.querySelector('.split-area');
-				splitArea?.classList.add('metadata-active');
+				const splitArea = this.querySelector(".split-area");
+				splitArea?.classList.add("metadata-active");
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector('.bucket-group');
-				const metadataComponent = this.querySelector('[data-component="metadata"]');
-				const statusIndicator = this.querySelector('.status-indicator');
-				bucketGroup?.classList.add('active');
-				metadataComponent?.classList.add('active');
-				statusIndicator?.classList.add('active');
+				const bucketGroup = this.querySelector(".bucket-group");
+				const metadataComponent = this.querySelector(
+					'[data-component="metadata"]',
+				);
+				const statusIndicator = this.querySelector(".status-indicator");
+				bucketGroup?.classList.add("active");
+				metadataComponent?.classList.add("active");
+				statusIndicator?.classList.add("active");
 			}
 		}
 
@@ -1041,75 +1177,83 @@ const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add('active');
+				clientNode?.classList.add("active");
 			}
 
 			// Step 2: Connector (client -> edge) lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add('active');
+				connector1?.classList.add("active");
 			}
 
 			// Step 3: EDGE box + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector('.region-box.with-local-uploads');
-				const gatewayNode = this.querySelector('.gateway-node-local');
-				edgeBox?.classList.add('active');
-				gatewayNode?.classList.add('active');
+				const edgeBox = this.querySelector(".region-box.with-local-uploads");
+				const gatewayNode = this.querySelector(".gateway-node-local");
+				edgeBox?.classList.add("active");
+				gatewayNode?.classList.add("active");
 			}
 
 			// Step 4: Line from Gateway to Object Data Infra (edge)
 			if (this.currentStep >= 4) {
-				const regionLine = this.querySelector('.region-line');
-				regionLine?.classList.add('active');
+				const regionLine = this.querySelector(".region-line");
+				regionLine?.classList.add("active");
 			}
 
 			// Step 5: Object Data Infra (edge) lights up
 			if (this.currentStep >= 5) {
-				const localStorageNode = this.querySelector('.local-storage-node');
-				localStorageNode?.classList.add('active');
+				const localStorageNode = this.querySelector(".local-storage-node");
+				localStorageNode?.classList.add("active");
 			}
 
 			// Step 6: Line from Gateway to Metadata Service
 			if (this.currentStep >= 6) {
-				const metadataLines = this.querySelectorAll('.left-col .v-connector.meta-line');
-				metadataLines.forEach(el => el.classList.add('active'));
+				const metadataLines = this.querySelectorAll(
+					".left-col .v-connector.meta-line",
+				);
+				metadataLines.forEach((el) => el.classList.add("active"));
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator lights up
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector('.bucket-group');
-				const metadataComponent = this.querySelector('[data-component="metadata"]');
-				const statusIndicator = this.querySelector('.status-indicator');
-				bucketGroup?.classList.add('active');
-				metadataComponent?.classList.add('active');
-				statusIndicator?.classList.add('active');
+				const bucketGroup = this.querySelector(".bucket-group");
+				const metadataComponent = this.querySelector(
+					'[data-component="metadata"]',
+				);
+				const statusIndicator = this.querySelector(".status-indicator");
+				bucketGroup?.classList.add("active");
+				metadataComponent?.classList.add("active");
+				statusIndicator?.classList.add("active");
 			}
 
 			// Step 8: Purple replication line animates downward + progress ring fills
 			if (this.currentStep >= 8) {
-				const replicationLines = this.querySelectorAll('.right-col .v-connector.replication-line');
-				const progressRing = this.querySelector('.progress-ring');
+				const replicationLines = this.querySelectorAll(
+					".right-col .v-connector.replication-line",
+				);
+				const progressRing = this.querySelector(".progress-ring");
 				// Force animation restart by removing class, triggering reflow, then adding class
-				replicationLines.forEach(el => {
-					el.classList.remove('animating');
+				replicationLines.forEach((el) => {
+					el.classList.remove("animating");
 					void (el as HTMLElement).offsetWidth; // Trigger reflow
-					el.classList.add('animating');
+					el.classList.add("animating");
 				});
 				if (progressRing) {
-					progressRing.classList.remove('animating');
+					progressRing.classList.remove("animating");
 					void (progressRing as HTMLElement).offsetWidth; // Trigger reflow
-					progressRing.classList.add('animating');
+					progressRing.classList.add("animating");
 				}
 			}
 
 			// Step 9: Object Data Infra (bucket) lights up
 			if (this.currentStep >= 9) {
-				const objectDataComponent = this.querySelector('[data-component="object-data"]');
-				objectDataComponent?.classList.add('active');
+				const objectDataComponent = this.querySelector(
+					'[data-component="object-data"]',
+				);
+				objectDataComponent?.classList.add("active");
 			}
 		}
 	}
 
-	customElements.define('r2-local-uploads-diagram', R2LocalUploadsDiagram);
+	customElements.define("r2-local-uploads-diagram", R2LocalUploadsDiagram);
 </script>
diff --git a/src/components/WranglerCommand.astro b/src/components/WranglerCommand.astro
index 560f0f0a3b9fc1d..9effdfbbbc05806 100644
--- a/src/components/WranglerCommand.astro
+++ b/src/components/WranglerCommand.astro
@@ -29,7 +29,7 @@ const experimental = definition.metadata.status === "experimental";
 // CED-191 some commands are present but marked as "hidden" and shouldn't be shown
 if (definition.metadata.hidden) {
 	throw new Error(
-		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`
+		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`,
 	);
 }
 
diff --git a/src/components/WranglerConfig.astro b/src/components/WranglerConfig.astro
index cf7cdd0bca5b008..6635f78fddc1700 100644
--- a/src/components/WranglerConfig.astro
+++ b/src/components/WranglerConfig.astro
@@ -19,7 +19,7 @@ const copy = html.querySelector("div.copy > button");
 
 if (!copy) {
 	throw new Error(
-		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`
+		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`,
 	);
 }
 
@@ -27,7 +27,7 @@ let code = copy.attributes["data-code"];
 
 if (!code) {
 	throw new Error(
-		`[WranglerConfig] Unable to find data-code attribute on copy button.`
+		`[WranglerConfig] Unable to find data-code attribute on copy button.`,
 	);
 }
 
diff --git a/src/components/WranglerNamespace.astro b/src/components/WranglerNamespace.astro
index 26f4136c098904f..52fc4b766b79934 100644
--- a/src/components/WranglerNamespace.astro
+++ b/src/components/WranglerNamespace.astro
@@ -41,7 +41,7 @@ flattenSubtree(node.subtree);
 	definitions.map((definition) => {
 		if (definition.type !== "command") {
 			throw new Error(
-				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`
+				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`,
 			);
 		}
 		return (
diff --git a/src/components/agent-setup/AgentComparison.astro b/src/components/agent-setup/AgentComparison.astro
index 5d6382aa20f657f..58cd4d4ce361218 100644
--- a/src/components/agent-setup/AgentComparison.astro
+++ b/src/components/agent-setup/AgentComparison.astro
@@ -122,7 +122,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.pricing_model ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.pricing_model.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.pricing_model] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.pricing_model] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.pricing_model as keyof typeof capabilityLabels
@@ -136,7 +138,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.model_flexibility ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.model_flexibility.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.model_flexibility] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.model_flexibility] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.model_flexibility as keyof typeof capabilityLabels
@@ -150,7 +154,9 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.context_approach ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.context_approach.replace("_", "-")}`}
-										data-agent-tooltip={capabilityTooltips[agent.context_approach] ?? ""}
+										data-agent-tooltip={
+											capabilityTooltips[agent.context_approach] ?? ""
+										}
 									>
 										{capabilityLabels[
 											agent.context_approach as keyof typeof capabilityLabels
diff --git a/src/components/agent-setup/AgentHeader.astro b/src/components/agent-setup/AgentHeader.astro
index 65d087ccb59bd27..71bf483f8e9d0e3 100644
--- a/src/components/agent-setup/AgentHeader.astro
+++ b/src/components/agent-setup/AgentHeader.astro
@@ -20,9 +20,7 @@ const { slug } = Astro.props;
 const agent = AGENTS.find((a) => a.slug === slug);
 
 if (!agent) {
-	throw new Error(
-		`[AgentHeader] No agent found for slug="${slug}"`,
-	);
+	throw new Error(`[AgentHeader] No agent found for slug="${slug}"`);
 }
 
 const externalLinks = [
diff --git a/src/components/agent-setup/AgentPrimer.astro b/src/components/agent-setup/AgentPrimer.astro
index 35186f18fb15f25..ebcdc78adfe7adf 100644
--- a/src/components/agent-setup/AgentPrimer.astro
+++ b/src/components/agent-setup/AgentPrimer.astro
@@ -179,8 +179,10 @@
 				</div>
 				<p>
 					Which foundation models you can use. <strong>Locked</strong>
-					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your Own Key) lets you bring
-					your own API key. <strong>Multi-provider</strong>
+					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your
+					Own Key) lets you bring your own API key. <strong
+						>Multi-provider</strong
+					>
 					supports several providers out of the box.
 				</p>
 			</div>
diff --git a/src/components/agent-setup/BuildAgentsCallout.astro b/src/components/agent-setup/BuildAgentsCallout.astro
index 94869f042602215..6b69a6fa5d1d523 100644
--- a/src/components/agent-setup/BuildAgentsCallout.astro
+++ b/src/components/agent-setup/BuildAgentsCallout.astro
@@ -8,8 +8,8 @@
 	<div class="agent-build-callout-header">
 		<span class="agent-build-callout-eyebrow">Also worth knowing</span>
 		<p class="agent-build-callout-lede">
-			Cloudflare is not just a deploy target for agents, it is a full
-			stack for building your own.
+			Cloudflare is not just a deploy target for agents, it is a full stack for
+			building your own.
 		</p>
 	</div>
 
diff --git a/src/components/agent-setup/CloudflareToolsBanner.astro b/src/components/agent-setup/CloudflareToolsBanner.astro
index 5ed10cc064b9b55..0545d11317e00e4 100644
--- a/src/components/agent-setup/CloudflareToolsBanner.astro
+++ b/src/components/agent-setup/CloudflareToolsBanner.astro
@@ -5,27 +5,48 @@
 
 <div class="cf-banner not-content">
 	<div class="cf-banner-items">
-
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">Skills</p>
-			<p class="cf-banner-item-desc">Reusable prompt packages that teach agents about Cloudflare products and APIs.</p>
+			<p class="cf-banner-item-desc">
+				Reusable prompt packages that teach agents about Cloudflare products and
+				APIs.
+			</p>
 			<div class="cf-banner-item-links">
-				<a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">cloudflare/skills &nearr;</a>
+				<a
+					href="https://github.com/cloudflare/skills"
+					target="_blank"
+					rel="noopener noreferrer">cloudflare/skills &nearr;</a
+				>
 			</div>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">MCP</p>
-			<p class="cf-banner-item-desc">Connect agents to your Cloudflare account. Two flavors: <a href="https://github.com/cloudflare/mcp" target="_blank" rel="noopener noreferrer">Code Mode &nearr;</a> for broad API coverage across all products, or <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific servers &nearr;</a> for purpose-built tools within one product area.</p>
+			<p class="cf-banner-item-desc">
+				Connect agents to your Cloudflare account. Two flavors: <a
+					href="https://github.com/cloudflare/mcp"
+					target="_blank"
+					rel="noopener noreferrer">Code Mode &nearr;</a
+				> for broad API coverage across all products, or <a
+					href="https://github.com/cloudflare/mcp-server-cloudflare"
+					target="_blank"
+					rel="noopener noreferrer">domain-specific servers &nearr;</a
+				> for purpose-built tools within one product area.
+			</p>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">CLI</p>
 			<p class="cf-banner-item-desc">
-				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers, KV, D1, R2, and more.
-				<a href="https://blog.cloudflare.com/cf-cli-local-explorer/" target="_blank" rel="noopener noreferrer">cf CLI &nearr;</a> is a next-generation CLI covering every Cloudflare product — in technical preview.
+				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers,
+				KV, D1, R2, and more.
+				<a
+					href="https://blog.cloudflare.com/cf-cli-local-explorer/"
+					target="_blank"
+					rel="noopener noreferrer">cf CLI &nearr;</a
+				> is a next-generation CLI covering every Cloudflare product — in technical
+				preview.
 			</p>
 		</div>
-
 	</div>
 </div>
diff --git a/src/components/agent-setup/PlatformAccessSection.astro b/src/components/agent-setup/PlatformAccessSection.astro
index ca1c8625b1bbfae..a913296e1aae07b 100644
--- a/src/components/agent-setup/PlatformAccessSection.astro
+++ b/src/components/agent-setup/PlatformAccessSection.astro
@@ -32,9 +32,10 @@ import SkillsList from "./SkillsList.astro";
 		</p>
 		<p>
 			MCP servers provide typed tools to call into Cloudflare at runtime. There
-			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/">Code Mode</a> —
-			a single server that covers the entire Cloudflare API (2,500+ endpoints in
-			~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
+			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/"
+				>Code Mode</a
+			> — a single server that covers the entire Cloudflare API (2,500+ endpoints
+			in ~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
 				" "
 			}
 			<a
diff --git a/src/components/ai-gateway/code-examples.astro b/src/components/ai-gateway/code-examples.astro
index 5d48bb635cfa819..91687d405b07449 100644
--- a/src/components/ai-gateway/code-examples.astro
+++ b/src/components/ai-gateway/code-examples.astro
@@ -1,112 +1,245 @@
 ---
-import { CodeExample, CodeSelector, modelOptions, code, aiSDKUnifiedCode, aiSDKNativeCode, curlCode } from "./code-example-selector";
+import {
+	CodeExample,
+	CodeSelector,
+	modelOptions,
+	code,
+	aiSDKUnifiedCode,
+	aiSDKNativeCode,
+	curlCode,
+} from "./code-example-selector";
 import { Code } from "~/components";
 import { z } from "astro/zod";
 
-
 const props = z.object({
 	forceClient: z.string().optional(),
-    forceAPI: z.string().optional(),
+	forceAPI: z.string().optional(),
 });
 
 const { forceClient, forceAPI } = props.parse(Astro.props);
 ---
+
 <style>
-    .aig-code-example-container {
-        background-color: var(--color-gray-200);
-        border-color: var(--color-neutral-300);
-        border-radius: 0.675rem;
-        border-bottom-left-radius: 0.85rem;
-        border-bottom-right-radius: 0.85rem;
-        --selector-bg-color: var(--color-white);
-        --selector-border-color: var(--color-neutral-300);
-        --selector-text-color: var(--color-gray-900);
-        --ec-brdRad: 0.675rem;
-        --ec-brdCol: var(--color-neutral-300);
-        &:where([data-theme=dark], [data-theme=dark] *) {
-            background-color: var(--color-neutral-900);
-            border-color: var(--color-neutral-700);
-            --selector-bg-color: var(--color-neutral-700);
-            --selector-border-color: var(--color-neutral-800);
-            --selector-text-color: var(--color-gray-100);
-            --ec-brdCol: var(--color-neutral-700);
-        }
-    }
+	.aig-code-example-container {
+		background-color: var(--color-gray-200);
+		border-color: var(--color-neutral-300);
+		border-radius: 0.675rem;
+		border-bottom-left-radius: 0.85rem;
+		border-bottom-right-radius: 0.85rem;
+		--selector-bg-color: var(--color-white);
+		--selector-border-color: var(--color-neutral-300);
+		--selector-text-color: var(--color-gray-900);
+		--ec-brdRad: 0.675rem;
+		--ec-brdCol: var(--color-neutral-300);
+		&:where([data-theme="dark"], [data-theme="dark"] *) {
+			background-color: var(--color-neutral-900);
+			border-color: var(--color-neutral-700);
+			--selector-bg-color: var(--color-neutral-700);
+			--selector-border-color: var(--color-neutral-800);
+			--selector-text-color: var(--color-gray-100);
+			--ec-brdCol: var(--color-neutral-700);
+		}
+	}
 </style>
-<div class="border aig-code-example-container">
-<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
-{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript" title="" code={code
-        .replace("{provider}", option.provider)
-        .replace("{model}", option.model)
-        .replace("    {headerauth}\n","")}
-         />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript" title="" code={code
-        .replace("{provider}", option.provider)
-        .replace("{model}", option.model)
-        .replace("{cf_api_token}", "{" + option.provider + "_api_token}")
-        .replace("    {headerauth}\n","  defaultHeaders: {\n      // if gateway is authenticated\n      \"cf-aig-authorization\": `Bearer {cf_api_token}`, \n  },\n")}
-         />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
-            .replaceAll("{provider}", option.provider)
-            .replaceAll("{apikey}", "")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
-            .replaceAll("{provider}", option.provider)
-            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
+<div class="aig-code-example-container border">
+	<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
+	{
+		(!forceClient || forceClient === "openai-js") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="openai-js"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={code
+							.replace("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("    {headerauth}\n", "")}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "openai-js") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="openai-js"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={code
+							.replace("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("{cf_api_token}", "{" + option.provider + "_api_token}")
+							.replace(
+								"    {headerauth}\n",
+								'  defaultHeaders: {\n      // if gateway is authenticated\n      "cf-aig-authorization": `Bearer {cf_api_token}`, \n  },\n',
+							)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKUnifiedCode
+							.replaceAll("{provider}", option.provider)
+							.replaceAll("{apikey}", "")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKUnifiedCode
+							.replaceAll("{provider}", option.provider)
+							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
 
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKNativeCode
-            .replaceAll("{provider}", option.aiSDK.provider)
-            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-            .replaceAll("{apikey}", "")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code lang="javascript"  title="" code={aiSDKNativeCode
-            .replaceAll("{provider}", option.aiSDK.provider)
-            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-            .replace("{model}", option.model)} />
-    </CodeExample>
-))}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="stored"
+					apiType="native"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKNativeCode
+							.replaceAll("{provider}", option.aiSDK.provider)
+							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+							.replaceAll("{apikey}", "")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "aisdk") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="aisdk"
+					keyType="in-request"
+					apiType="native"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						lang="javascript"
+						title=""
+						code={aiSDKNativeCode
+							.replaceAll("{provider}", option.aiSDK.provider)
+							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+							.replace("{model}", option.model)}
+					/>
+				</CodeExample>
+			))
+	}
 
-{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="curl" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code title="" lang="curl" code={curlCode
-            .replaceAll("{provider}", option.provider)
-            .replace("{model}", option.model)
-            .replace("{headerauth}\n","")}
-             />
-    </CodeExample>
-))}
-{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
-    <CodeExample client:load provider={option.provider} clientType="curl" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
-        <Code title="" lang="curl" code={curlCode
-            .replaceAll("{provider}", option.provider)
-            .replace("{model}", option.model)
-            .replace("{headerauth}\n","  --header 'Authorization: Bearer {" + option.provider + "_api_token}' \\\n")} />
-    </CodeExample>
-))}
-</div>
\ No newline at end of file
+	{
+		(!forceClient || forceClient === "curl") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="curl"
+					keyType="stored"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						title=""
+						lang="curl"
+						code={curlCode
+							.replaceAll("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace("{headerauth}\n", "")}
+					/>
+				</CodeExample>
+			))
+	}
+	{
+		(!forceClient || forceClient === "curl") &&
+			modelOptions.map((option) => (
+				<CodeExample
+					client:load
+					provider={option.provider}
+					clientType="curl"
+					keyType="in-request"
+					apiType="unified"
+					forceClientType={forceClient}
+					forceApiType={forceAPI}
+				>
+					<Code
+						title=""
+						lang="curl"
+						code={curlCode
+							.replaceAll("{provider}", option.provider)
+							.replace("{model}", option.model)
+							.replace(
+								"{headerauth}\n",
+								"  --header 'Authorization: Bearer {" +
+									option.provider +
+									"_api_token}' \\\n",
+							)}
+					/>
+				</CodeExample>
+			))
+	}
+</div>
diff --git a/src/components/changelog/Pagination.astro b/src/components/changelog/Pagination.astro
index 33e8d73fe0001bd..633f1407b109d74 100644
--- a/src/components/changelog/Pagination.astro
+++ b/src/components/changelog/Pagination.astro
@@ -52,7 +52,10 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 
 {
 	lastPage > 1 && (
-		<nav class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2" aria-label="Pagination">
+		<nav
+			class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2"
+			aria-label="Pagination"
+		>
 			{prevUrl ? (
 				<a href={prevUrl} class="pagination-btn no-underline">
 					← Prev
@@ -64,7 +67,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 			<div class="pagination-pages flex items-center gap-1">
 				{items.map((item) =>
 					item === null ? (
-						<span class="flex h-9 items-center justify-center px-2 text-sm text-sl-color-gray-3">
+						<span class="text-sl-color-gray-3 flex h-9 items-center justify-center px-2 text-sm">
 							…
 						</span>
 					) : item === currentPage ? (
diff --git a/src/components/models/CopyableCode.astro b/src/components/models/CopyableCode.astro
index cf13027f562709e..0b17ed3299291d7 100644
--- a/src/components/models/CopyableCode.astro
+++ b/src/components/models/CopyableCode.astro
@@ -8,12 +8,7 @@ const { text, label = "Copy" } = Astro.props;
 ---
 
 <copyable-code data-text={text}>
-	<button
-		type="button"
-		title={label}
-		aria-label={label}
-		class="copy-button"
-	>
+	<button type="button" title={label} aria-label={label} class="copy-button">
 		<code>{text}</code>
 		<svg
 			xmlns="http://www.w3.org/2000/svg"
@@ -43,7 +38,9 @@ const { text, label = "Copy" } = Astro.props;
 		border: 1px solid var(--sl-color-gray-5);
 		background: transparent;
 		cursor: pointer;
-		transition: border-color 0.15s, background-color 0.15s;
+		transition:
+			border-color 0.15s,
+			background-color 0.15s;
 	}
 
 	.copy-button:hover {
diff --git a/src/components/models/ModelDetailPage.astro b/src/components/models/ModelDetailPage.astro
index f24f3a3540c7658..1019e2aa09c5ec0 100644
--- a/src/components/models/ModelDetailPage.astro
+++ b/src/components/models/ModelDetailPage.astro
@@ -188,7 +188,9 @@ const starlightPageProps = {
 			? { depth: 2, slug: "Examples", text: "Examples" }
 			: false,
 		hasSchema ? { depth: 2, slug: "Parameters", text: "Parameters" } : false,
-		hasSchema ? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" } : false,
+		hasSchema
+			? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" }
+			: false,
 	].filter((v) => Boolean(v)) as MarkdownHeading[],
 	hideTitle: true,
 } as StarlightPageProps;
@@ -424,22 +426,114 @@ const starlightPageProps = {
 					{model.apiModes.flatMap((mode) => [
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">
+									{mode.name}
+								</span>
 								<span class="ml-2 text-gray-500 dark:text-gray-400">Input</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/${mode.id}-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/${mode.id}-input.json`} download={`${mode.id}-input.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-input.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+										<polyline points="15 3 21 3 21 9" />
+										<line x1="10" y1="14" x2="21" y2="3" />
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-input.json`}
+									download={`${mode.id}-input.json`}
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+										<polyline points="7 10 12 15 17 10" />
+										<line x1="12" y1="15" x2="12" y2="3" />
+									</svg>
+								</a>
 							</span>
 						</div>,
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
-								<span class="ml-2 text-gray-500 dark:text-gray-400">Output</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">
+									{mode.name}
+								</span>
+								<span class="ml-2 text-gray-500 dark:text-gray-400">
+									Output
+								</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/${mode.id}-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/${mode.id}-output.json`} download={`${mode.id}-output.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-output.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+										<polyline points="15 3 21 3 21 9" />
+										<line x1="10" y1="14" x2="21" y2="3" />
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/${mode.id}-output.json`}
+									download={`${mode.id}-output.json`}
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+										<polyline points="7 10 12 15 17 10" />
+										<line x1="12" y1="15" x2="12" y2="3" />
+									</svg>
+								</a>
 							</span>
 						</div>,
 					])}
@@ -483,17 +577,115 @@ const starlightPageProps = {
 					<h2 id="API-Schemas">API Schemas (Raw)</h2>
 					<div class="not-content grid grid-cols-1 gap-2 sm:grid-cols-2">
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Input</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
+								Input
+							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/schema-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/schema-input.json`} download="schema-input.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/schema-input.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+											<polyline points="15 3 21 3 21 9" />
+											<line x1="10" y1="14" x2="21" y2="3" />
+										</>
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/schema-input.json`}
+									download="schema-input.json"
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+											<polyline points="7 10 12 15 17 10" />
+											<line x1="12" y1="15" x2="12" y2="3" />
+										</>
+									</svg>
+								</a>
 							</span>
 						</div>
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Output</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
+								Output
+							</span>
 							<span class="flex items-center gap-1">
-								<a href={`${schemaBasePath}/schema-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
-								<a href={`${schemaBasePath}/schema-output.json`} download="schema-output.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
+								<a
+									href={`${schemaBasePath}/schema-output.json`}
+									target="_blank"
+									rel="noopener noreferrer"
+									title="Open"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
+											<polyline points="15 3 21 3 21 9" />
+											<line x1="10" y1="14" x2="21" y2="3" />
+										</>
+									</svg>
+								</a>
+								<a
+									href={`${schemaBasePath}/schema-output.json`}
+									download="schema-output.json"
+									title="Download"
+									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
+								>
+									<svg
+										xmlns="http://www.w3.org/2000/svg"
+										width="14"
+										height="14"
+										viewBox="0 0 24 24"
+										fill="none"
+										stroke="currentColor"
+										stroke-width="2"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+									>
+										<>
+											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
+											<polyline points="7 10 12 15 17 10" />
+											<line x1="12" y1="15" x2="12" y2="3" />
+										</>
+									</svg>
+								</a>
 							</span>
 						</div>
 					</div>
diff --git a/src/components/models/SchemaDisplay.astro b/src/components/models/SchemaDisplay.astro
index 6dcb17aa8c69d0f..e87bb767e12aced 100644
--- a/src/components/models/SchemaDisplay.astro
+++ b/src/components/models/SchemaDisplay.astro
@@ -196,11 +196,10 @@ function collectRows(
 			(reg.annotations?.description as string | undefined) ??
 			nullableChildDescription;
 		// Check both validations and fragment for enum (different schema parsers put it in different places)
-		const enumValues =
-			((reg.validations?.enum as unknown[]) ??
-				((reg.fragment as Record<string, unknown>)?.enum as unknown[]))?.map(
-				String,
-			);
+		const enumValues = (
+			(reg.validations?.enum as unknown[]) ??
+			((reg.fragment as Record<string, unknown>)?.enum as unknown[])
+		)?.map(String);
 
 		// Collect all metadata from fragment and validations
 		const metadata: Record<string, string | number | boolean> = {};
@@ -429,7 +428,12 @@ const variantRows =
 				No parameters defined.
 			</p>
 		) : (
-			<SchemaTreeView rows={rows} schemaId={schemaId} hideRequired={hideRequired} client:visible />
+			<SchemaTreeView
+				rows={rows}
+				schemaId={schemaId}
+				hideRequired={hideRequired}
+				client:visible
+			/>
 		)
 	}
 </div>
diff --git a/src/components/models/code/DeepgramFlux.astro b/src/components/models/code/DeepgramFlux.astro
index c5c957d047b01e8..119317163ac8ede 100644
--- a/src/components/models/code/DeepgramFlux.astro
+++ b/src/components/models/code/DeepgramFlux.astro
@@ -73,11 +73,13 @@ function generateRandomAudio() {
   return buffer;
 }
 `;
-
 ---
 
 <>
-	<Details header="Step 1: Create a Worker that establishes a WebSocket connection" open>
+	<Details
+		header="Step 1: Create a Worker that establishes a WebSocket connection"
+		open
+	>
 		<Code code={worker} lang="ts" />
 	</Details>
 
@@ -85,7 +87,10 @@ function generateRandomAudio() {
 		<Code code={deployWorker} lang="sh" />
 	</Details>
 
-  <Details header="Step 3: Write a client script to connect to your Worker and send audio" open>
-    <Code code={clientScript} lang="js" />
-  </Details>
+	<Details
+		header="Step 3: Write a client script to connect to your Worker and send audio"
+		open
+	>
+		<Code code={clientScript} lang="js" />
+	</Details>
 </>
diff --git a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
index e1f4ce5d0ae4e09..ac2d801c62fdeb2 100644
--- a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
+++ b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
@@ -76,8 +76,8 @@ curl https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/v1/
 		</li>
 		<li>
 			<strong>Workers AI Run</strong> (<code>/ai/run</code>) - Dynamic format
-			detection, accepts Chat Completions (<code>messages</code>), legacy Completions
-			(<code>prompt</code>), or Responses API (<code>input</code>)
+			detection, accepts Chat Completions (<code>messages</code>), legacy
+			Completions (<code>prompt</code>), or Responses API (<code>input</code>)
 		</li>
 		<li>
 			<strong>Chat Completions</strong> (<code>/v1/chat/completions</code>) -
diff --git a/src/components/overrides/Page.astro b/src/components/overrides/Page.astro
index 193c0458f2d2a57..e0ba5423f7dfb20 100644
--- a/src/components/overrides/Page.astro
+++ b/src/components/overrides/Page.astro
@@ -12,9 +12,11 @@ const html = await Astro.slots.render("default");
 // Agent-setup pages use `template: splash` (to avoid sidebar group lookup) but
 // still need a right-hand ToC. Splash pages have props.toc === undefined, so we
 // bootstrap the object here before calling generateTableOfContents.
-const isAgentSetup = props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
+const isAgentSetup =
+	props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
 if (isAgentSetup) {
-	if (!props.toc) props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
+	if (!props.toc)
+		props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
 	props.hideBreadcrumbs = true;
 	props.hideTitle = true;
 }
diff --git a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
index c7f5ea93bac1254..d03cecd7bab8754 100644
--- a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
+++ b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
@@ -1,12 +1,12 @@
 ---
 title: Cloudflare Access Logging supports the Customer Metadata Boundary (CMB)
-description: Access logs will now respect the CMB. 
+description: Access logs will now respect the CMB.
 date: 2025-08-14
 products:
   - access
 ---
 
-Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration. 
+Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration.
 
 :::note
 For EU CMB customers, the logs will not be stored by Access and will appear as empty in the dashboard. EU CMB customers should utilize [Logpush](/logs/logpush/) to retain their Access logging, if desired.
diff --git a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
index a82bbcbeee550b8..cd95cf8fdd1edba 100644
--- a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
+++ b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
@@ -15,4 +15,3 @@ An [MCP server portal](/cloudflare-one/access-controls/ai-controls/mcp-portals/)
 - **Observability**: Once the user's AI agent is connected to the portal, Cloudflare Access logs the individual requests made using the tools in the portal.
 
 This is available in an open beta for all customers across all plans! For more information check out our [blog](https://blog.cloudflare.com/zero-trust-mcp-server-portals/) for this release.
-
diff --git a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
index 675b9236a2b9f3d..91a89f79924c5c2 100644
--- a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
+++ b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
@@ -12,6 +12,4 @@ A new **Allow clientless access** setting makes it easier to connect users witho
 
 Previously, to provide clientless access to a private hostname or IP without a [published application](/cloudflare-one/networks/routes/add-routes/#add-a-published-application-route), you had to create a separate [bookmark application](/cloudflare-one/access-controls/applications/bookmarks/) pointing to a prefixed [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) URL (for example, `https://<your-teamname>.cloudflareaccess.com/browser/https://10.0.0.1/`). This bookmark was visible to all users in the App Launcher, regardless of whether they had access to the underlying application.
 
-Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When  **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
-
-
+Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
diff --git a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
index e3dde55074d43c6..8524d2348de427d 100644
--- a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
+++ b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
@@ -33,13 +33,13 @@ const tools = {
 	getWeather: tool({
 		description: "Get weather for a city",
 		inputSchema: z.object({ city: z.string() }),
-		execute: async ({ city }) => fetchWeather(city)
+		execute: async ({ city }) => fetchWeather(city),
 	}),
 
 	// Client-executed tool (no execute = client handles via onToolCall)
 	getLocation: tool({
 		description: "Get user location from browser",
-		inputSchema: z.object({})
+		inputSchema: z.object({}),
 		// No execute function
 	}),
 
@@ -48,8 +48,8 @@ const tools = {
 		description: "Process a payment",
 		inputSchema: z.object({ amount: z.number() }),
 		needsApproval: async ({ amount }) => amount > 100,
-		execute: async ({ amount }) => charge(amount)
-	})
+		execute: async ({ amount }) => charge(amount),
+	}),
 };
 ```
 
@@ -70,11 +70,11 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 				toolCallId: toolCall.toolCallId,
 				output: {
 					lat: position.coords.latitude,
-					lng: position.coords.longitude
-				}
+					lng: position.coords.longitude,
+				},
 			});
 		}
-	}
+	},
 });
 ```
 
@@ -97,9 +97,9 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 		// Handle client-side tool execution
 		await addToolOutput({
 			toolCallId: toolCall.toolCallId,
-			output: { result: "success" }
+			output: { result: "success" },
 		});
-	}
+	},
 });
 ```
 
@@ -112,12 +112,12 @@ const paymentTool = tool({
 	description: "Process a payment",
 	inputSchema: z.object({
 		amount: z.number(),
-		recipient: z.string()
+		recipient: z.string(),
 	}),
 	needsApproval: async ({ amount }) => amount > 1000,
 	execute: async ({ amount, recipient }) => {
 		return await processPayment(amount, recipient);
-	}
+	},
 });
 ```
 
@@ -138,7 +138,7 @@ const pendingToolCallConfirmation = messages.some((m) =>
 if (pendingToolCallConfirmation) {
 	await addToolOutput({
 		toolCallId: part.toolCallId,
-		output: "User approved the action"
+		output: "User approved the action",
 	});
 }
 ```
@@ -158,7 +158,7 @@ import { convertToModelMessages } from "ai";
 
 const result = streamText({
 	messages: await convertToModelMessages(this.messages),
-	model: openai("gpt-4o")
+	model: openai("gpt-4o"),
 });
 ```
 
@@ -182,14 +182,14 @@ const result = await generateObject({
 	mode: "json",
 	model,
 	schema,
-	prompt
+	prompt,
 });
 
 // After (v6)
 const result = await generateObject({
 	model,
 	schema,
-	prompt
+	prompt,
 });
 ```
 
@@ -203,10 +203,10 @@ import { generateText, Output, stepCountIs } from "ai";
 const { output } = await generateText({
 	model: openai("gpt-4"),
 	output: Output.object({
-		schema: z.object({ name: z.string() })
+		schema: z.object({ name: z.string() }),
 	}),
 	stopWhen: stepCountIs(2),
-	prompt: "Generate a name"
+	prompt: "Generate a name",
 });
 ```
 
@@ -282,11 +282,11 @@ import { createAIGateway } from "ai-gateway-provider";
 const model = createAIGateway({
 	gatewayUrl: "https://gateway.ai.cloudflare.com/v1/your-account-id/gateway",
 	headers: {
-		"Authorization": `Bearer ${env.AI_GATEWAY_TOKEN}`
-	}
+		Authorization: `Bearer ${env.AI_GATEWAY_TOKEN}`,
+	},
 })({
 	provider: "openai",
-	model: "gpt-4o"
+	model: "gpt-4o",
 });
 ```
 
diff --git a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
index c47df65f32e38d4..af9c6cd51586110 100644
--- a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
+++ b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
@@ -10,25 +10,25 @@ We are excited to announce two major capability upgrades for **Agent Lee**, the
 
 ### Take action with Write Operations
 
-Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. 
+Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.
 
 To ensure security and accuracy, every write operation requires **explicit user approval**. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select **Confirm**, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.
 
 **Example requests:**
-* *"Add an A record for blog.example.com pointing to 192.0.2.10."*
-* *"Enable Always Use HTTPS on my zone."*
-* *"Set the SSL mode for example.com to Full (strict)."*
 
+- _"Add an A record for blog.example.com pointing to 192.0.2.10."_
+- _"Enable Always Use HTTPS on my zone."_
+- _"Set the SSL mode for example.com to Full (strict)."_
 
 ### Visualize data with Generative UI
 
 Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features **Generative UI**, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry.
 
 **Example requests:**
-* *"Show me a chart of my traffic over the last 7 days."*
-* *"What does my error rate look like for the past 24 hours?"*
-* *"Graph my cache hit rate for example.com this week."*
 
+- _"Show me a chart of my traffic over the last 7 days."_
+- _"What does my error rate look like for the past 24 hours?"_
+- _"Graph my cache hit rate for example.com this week."_
 
 ---
 
diff --git a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
index 70d67fd32103d74..6142d6dbab74b1a 100644
--- a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
+++ b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
@@ -16,4 +16,4 @@ You can find these metrics within each AutoRAG instance:
 - Search breakdown: Compare usage between `ai-search` and `search` endpoints.
 - Top file retrievals: Identify which files are most frequently retrieved in a given period.
 
-Try it today in [AutoRAG](/ai-search/get-started/).
\ No newline at end of file
+Try it today in [AutoRAG](/ai-search/get-started/).
diff --git a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
index 1eff4229721c7bd..37bf0f628f7a6a7 100644
--- a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
+++ b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
@@ -13,9 +13,9 @@ With AI Search you can now use models from different providers like OpenAI and A
 To use AI Search with other [model providers](/ai-search/configuration/models/):
 
 1. **Add provider keys to AI Gateway**
-    1. Go to AI > AI Gateway in the dashboard.
-    2. Select or create an AI gateway.
-    3. In Provider Keys, choose your provider, click Add, and enter the key.
+   1. Go to AI > AI Gateway in the dashboard.
+   2. Select or create an AI gateway.
+   3. In Provider Keys, choose your provider, click Add, and enter the key.
 2. **Connect a gateway to AI Search**: When creating a new AI Search, select the AI Gateway with your provider keys. For an existing AI Search, go to Settings and switch to a gateway that has your keys under Resources.
 3. **Select models**: Embedding models are only available to be changed when creating a new AI Search. Generation model can be selected when creating a new AI Search and can be changed at any time in Settings.
 
@@ -23,19 +23,18 @@ Once configured, your AI Search instance will be able to reference models availa
 
 ```javascript
 export default {
-  async fetch(request, env) {
-    
-    // Query your AI Search instance with a natural language question to an OpenAI model
-    const result = await env.AI.autorag("my-ai-search").aiSearch({
-      query: "What's new for Cloudflare Birthday Week?",
-      model: "openai/gpt-5"
-    });
-
-    // Return only the generated answer as plain text
-    return new Response(result.response, {
-      headers: { "Content-Type": "text/plain" },
-    });
-  },
+	async fetch(request, env) {
+		// Query your AI Search instance with a natural language question to an OpenAI model
+		const result = await env.AI.autorag("my-ai-search").aiSearch({
+			query: "What's new for Cloudflare Birthday Week?",
+			model: "openai/gpt-5",
+		});
+
+		// Return only the generated answer as plain text
+		return new Response(result.response, {
+			headers: { "Content-Type": "text/plain" },
+		});
+	},
 };
 ```
 
diff --git a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
index 5a9abdb9296fae3..561919395ce174d 100644
--- a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
+++ b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
@@ -10,7 +10,8 @@ date: 2025-11-19
 
 Previously, AI Search could only crawl publicly accessible pages, leaving knowledge bases, documentation, and other protected content out of your search results. With custom headers support, you can now include authentication credentials that allow the crawler to access this protected content.
 
-This is particularly useful for indexing content like: 
+This is particularly useful for indexing content like:
+
 - **Internal documentation** behind corporate login systems
 - **Premium content** that requires users to provide access to unlock
 - **Sites protected by Cloudflare Access** using service tokens
@@ -26,6 +27,6 @@ CF-Access-Client-Id: your-token-id.access
 CF-Access-Client-Secret: your-token-secret
 ```
 
-The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked. 
+The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked.
 
-Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
\ No newline at end of file
+Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
diff --git a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
index a54b6cddfff6e9a..105ae21f43fe4fd 100644
--- a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
+++ b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
@@ -7,13 +7,13 @@ date: 2026-04-16T12:00:00Z
 publish_future_dated_entry: true
 ---
 
-New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away. 
+New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away.
 
 Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call.
 
 ## Built-in storage and vector index
 
-All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first. 
+All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first.
 
 ```ts
 const instance = env.AI_SEARCH.get("my-instance");
diff --git a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
index e8c0c6621a0467f..420f30e5265e339 100644
--- a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
+++ b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
@@ -3,12 +3,12 @@ title: New Confidence Intervals in GraphQL Analytics API
 description: Confidence intervals are now supported in the GraphQL Analytics API to show statistical ranges for sampled data results
 date: 2025-10-01
 ---
- 
-The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty. 
+
+The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty.
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`). 
+- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`).
 - **Default**: If no confidence level is specified, no intervals are returned.
 
-For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/). 
+For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/).
diff --git a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
index 6194d159eaef0a2..91c0a2dc9d56063 100644
--- a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
+++ b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
@@ -8,10 +8,10 @@ The Server-Timing header now includes a new `cfWorker` metric that measures time
 
 Previously, Worker execution time was included in the `edge` metric, making it harder to identify true edge performance. The new `cfWorker` metric provides this visibility:
 
-| Metric | Description |
-| --- | --- |
-| `edge` | Total time spent on the Cloudflare edge, including Worker execution |
-| `origin` | Time spent fetching from the origin server |
+| Metric     | Description                                                                           |
+| ---------- | ------------------------------------------------------------------------------------- |
+| `edge`     | Total time spent on the Cloudflare edge, including Worker execution                   |
+| `origin`   | Time spent fetching from the origin server                                            |
 | `cfWorker` | Time spent in Worker execution, including subrequests but excluding origin fetch time |
 
 ### Example response
diff --git a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
index 1b6ce51e1eb4bfd..32a3c52bdfbfc7f 100644
--- a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
+++ b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
@@ -10,8 +10,8 @@ Cloudflare is launching the [Open Beta of the **Web and API Vulnerability Scanne
 
 The initial release focuses on detecting Broken Object Level Authorization (BOLA) vulnerabilities by building API call graphs to simulate attacker and owner contexts, then testing these contexts by sending real HTTP requests to your APIs.
 
-The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release. 
+The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release.
 
 **Access**: This feature is only available to API Shield subscribers via the Cloudflare API. We hope you will use the API for programmatic integration into your CI/CD pipelines and security dashboards.
 
-**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
\ No newline at end of file
+**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
diff --git a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
index 968d7e9e61a7325..8f0e0c75c5a3682 100644
--- a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
+++ b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
@@ -12,13 +12,13 @@ You can now receive [event notifications](/queues/event-subscriptions/) for [Art
 
 This allows you to:
 
-* Run custom workflows when a repository is created or imported
-* Kick off a build and deploy a change when an agent pushes to a repo
-* Trigger a review agent on every push
+- Run custom workflows when a repository is created or imported
+- Kick off a build and deploy a change when an agent pushes to a repo
+- Trigger a review agent on every push
 
 Available events include:
 
-* **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
-* **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
+- **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
+- **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
 
 To learn more, refer to [Artifacts documentation](/artifacts/guides/event-subscriptions/).
diff --git a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
index d613bad87530e49..18f7b35d1cbd348 100644
--- a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
+++ b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
@@ -27,4 +27,3 @@ You can now create optimized cache rules instantly with **one-click templates**,
 ## Get started
 
 To get started, go to [**Rules > Templates**](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) in the dashboard. For more information, refer to the [Cache Rules documentation](/cache/how-to/cache-rules/).
-
diff --git a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
index 13727aa33125d77..803a3785a4f7930 100644
--- a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
+++ b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
@@ -26,14 +26,14 @@ When configuring [custom cache keys](/cache/how-to/cache-keys/), you can now inc
 
 ```json
 {
-  "cache_key": {
-    "custom_key": {
-      "header": {
-        "include": ["accept-language", "user-agent"],
-        "check_presence": ["referer"]
-      }
-    }
-  }
+	"cache_key": {
+		"custom_key": {
+			"header": {
+				"include": ["accept-language", "user-agent"],
+				"check_presence": ["referer"]
+			}
+		}
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
index 3f346c5807413c8..a9d29c3c2cfc2b5 100644
--- a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
+++ b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
@@ -20,19 +20,19 @@ The Trace response includes the cache key in the `cache` object:
 
 ```json
 {
-  "step_name": "request",
-  "type": "cache",
-  "matched": true,
-  "public_name": "Cache Parameters",
-  "cache": {
-    "key": {
-      "zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
-      "scheme": "https",
-      "host": "example.com",
-      "uri": "/images/hero.jpg"
-    },
-    "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
-  }
+	"step_name": "request",
+	"type": "cache",
+	"matched": true,
+	"public_name": "Cache Parameters",
+	"cache": {
+		"key": {
+			"zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
+			"scheme": "https",
+			"host": "example.com",
+			"uri": "/images/hero.jpg"
+		},
+		"key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
index 814ebc40610e652..3f7c005146bb17a 100644
--- a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
+++ b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
@@ -20,28 +20,28 @@ The detailed audit payload is visible within the Cloudflare Dashboard (under **M
 
 ```json
 {
-  "action": {
-    "result": "success",
-    "type": "create"
-  },
-  "actor": {
-    "id": "1234567890abcdef",
-    "email": "user@example.com",
-    "type": "user"
-  },
-  "resource": {
-    "product": "purge_cache",
-    "request": {
-      "files": [
-        "https://example.com/images/logo.png",
-        "https://example.com/css/styles.css"
-      ]
-    }
-  },
-  "zone": {
-    "id": "023e105f4ecef8ad9ca31a8372d0c353",
-    "name": "example.com"
-  }
+	"action": {
+		"result": "success",
+		"type": "create"
+	},
+	"actor": {
+		"id": "1234567890abcdef",
+		"email": "user@example.com",
+		"type": "user"
+	},
+	"resource": {
+		"product": "purge_cache",
+		"request": {
+			"files": [
+				"https://example.com/images/logo.png",
+				"https://example.com/css/styles.css"
+			]
+		}
+	},
+	"zone": {
+		"id": "023e105f4ecef8ad9ca31a8372d0c353",
+		"name": "example.com"
+	}
 }
 ```
 
diff --git a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
index f8b1270d926561c..220ad070c02db00 100644
--- a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
+++ b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-24
 ---
 
-You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses *before* they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
+You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses _before_ they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
 
 ## What changed
 
diff --git a/src/content/changelog/casb/2025-10-28-casb-roles.mdx b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
index 0eba434bfd0c136..45bf12202502ff5 100644
--- a/src/content/changelog/casb/2025-10-28-casb-roles.mdx
+++ b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
@@ -8,8 +8,8 @@ date: 2025-10-28
 
 Cloudflare CASB (Cloud Access Security Broker) now supports two new granular roles to provide more precise access control for your security teams:
 
-* **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
-* **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
+- **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
+- **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
 
 These new roles help you better enforce the principle of least privilege. You can now grant specific members access to CASB security findings without assigning them broader permissions, such as the **Super Administrator** or **Administrator** roles.
 
diff --git a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
index 06fb9e1526fa249..8293deadac922ee 100644
--- a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
+++ b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
@@ -5,4 +5,3 @@ date: 2025-08-29
 ---
 
 We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client.
-
diff --git a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
index ae69ba66324f32d..40a2ecfb6928699 100644
--- a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
+++ b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
@@ -9,9 +9,9 @@ products:
 Zero Trust Dashboard has a brand new, AI-powered search functionality. You can search your account by resources (applications, policies, device profiles, settings, etc.), pages, products, and more.
 
 ![Example search results in the Zero Trust dashboard](~/assets/images/changelog/cloudflare-one/searchexample.png)
-  
+
 **Ask Cloudy** — You can also ask Cloudy, our AI agent, questions about Cloudflare Zero Trust. Cloudy is trained on our developer documentation and implementation guides, so it can tell you how to configure functionality, best practices, and can make recommendations.
 
 Cloudy can then stay open with you as you move between pages to build configuration or answer more questions.
 
-**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
\ No newline at end of file
+**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
diff --git a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
index d4b4b3081b4aa3a..b0f6e01371820c0 100644
--- a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
+++ b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
@@ -8,10 +8,10 @@ products:
 
 You can now duplicate specific Cloudflare One resources with a single click from the dashboard.
 
-
 Initially supported resources:
-* Access Applications
-* Access Policies
-* Gateway Policies
 
-To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
\ No newline at end of file
+- Access Applications
+- Access Policies
+- Gateway Policies
+
+To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
index 3732caa81147c83..1cbf0a71d44db2b 100644
--- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx
+++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
@@ -7,7 +7,7 @@ product: Gateway
 
 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications.
 
-33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. 
+33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security.
 
 To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**.
 
diff --git a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
index 03fb76c0a537bc1..9be106dafc193cc 100644
--- a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
+++ b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
@@ -23,4 +23,4 @@ Key details:
 
 Configuring Cloudflare source IPs requires Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
 
-For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
\ No newline at end of file
+For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
diff --git a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
index 32af30f28627705..a42523b426c282c 100644
--- a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
+++ b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
@@ -9,7 +9,7 @@ date: 2025-10-01
 New instance types provide up to 4 vCPU, 12 GiB of memory, and 20 GB of disk per container instance.
 
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------  | ----  |
+| ------------- | ---- | ------- | ----- |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
diff --git a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
index 3a6f1aa9ae491fc..1d4d4ea196130e1 100644
--- a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
+++ b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
@@ -15,15 +15,15 @@ This means that you now pay less for Containers and Sandboxes.
 Imagine running the `standard-2` instance type for one hour, which can use up to 1 vCPU,
 but on average you use only 20% of your CPU capacity.
 
-CPU-time is priced at *$0.00002 per vCPU-second*.
+CPU-time is priced at _$0.00002 per vCPU-second_.
 
 Previously, you would be charged for the CPU allocated to the instance multiplied by the time it was active, in this case 1 hour.
 
-CPU cost would have been: **$0.072** — 1 vCPU * 3600 seconds * $0.00002
+CPU cost would have been: **$0.072** — 1 vCPU _ 3600 seconds _ $0.00002
 
 Now, since you are only using 20% of your CPU capacity, your CPU cost is cut to 20% of the previous amount.
 
-CPU cost is now: **$0.0144** — 1 vCPU * 3600 seconds * $0.00002 * 20% utilization
+CPU cost is now: **$0.0144** — 1 vCPU _ 3600 seconds _ $0.00002 \* 20% utilization
 
 This can significantly reduce costs for Containers and Sandboxes.
 
diff --git a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
index 242d66f2e0cf6e2..baf0295247c3495 100644
--- a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
+++ b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
@@ -16,4 +16,4 @@ You can now run more [Containers](/containers/) concurrently with significantly
 
 This 15x increase enables larger-scale workloads on Containers. You can now run 15,000 instances of the `lite` instance type, 6,000 instances of `basic`, over 1,500 instances of `standard-1`, or over 1,000 instances of `standard-2` concurrently.
 
-Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
\ No newline at end of file
+Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
diff --git a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
index cb2468f841ffe89..d9a25a5bf08676f 100644
--- a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
+++ b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
@@ -27,4 +27,4 @@ Containers now support [Docker Hub](https://hub.docker.com/) images. You can use
 
 Containers also support private Docker Hub images. To configure credentials, refer to [Use private Docker Hub images](/containers/platform-details/image-management/#use-private-docker-hub-images).
 
-For more information, refer to [Image management](/containers/platform-details/image-management/).
\ No newline at end of file
+For more information, refer to [Image management](/containers/platform-details/image-management/).
diff --git a/src/content/changelog/containers/2026-04-05-regional-placement.mdx b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
index 2871fa894eff6a3..bb35775f82b0c78 100644
--- a/src/content/changelog/containers/2026-04-05-regional-placement.mdx
+++ b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
@@ -8,10 +8,10 @@ date: 2026-04-05
 
 You can now specify placement constraints to control where your [Containers](/containers/) run.
 
-| Constraint     | Values                                  | Use case                          |
-| -------------- | --------------------------------------- | --------------------------------- |
-| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR`          | Geographic placement              |
-| `jurisdiction` | `eu`, `fedramp`                         | Compliance boundaries             |
+| Constraint     | Values                         | Use case              |
+| -------------- | ------------------------------ | --------------------- |
+| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR` | Geographic placement  |
+| `jurisdiction` | `eu`, `fedramp`                | Compliance boundaries |
 
 Use `regions` to limit placement to specific geographic areas. Use `jurisdiction` to restrict containers to compliance boundaries — `eu` maps to European regions (EEUR, WEUR) and `fedramp` maps to North American regions (ENAM, WNAM).
 
diff --git a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
index 4b8f807edcebfbe..169bb898b975965 100644
--- a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
+++ b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
@@ -74,7 +74,7 @@ Define named outbound handlers then apply or remove them at runtime using `setOu
 export class MySandbox extends Sandbox {}
 
 MySandbox.outboundHandlers = {
-	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext ) => {
+	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext) => {
 		const url = new URL(req.url);
 		if (ctx.params.allowedHostnames.includes(url.hostname)) {
 			return fetch(req);
diff --git a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
index 797ef3ce255a866..9b7229b637259e4 100644
--- a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
+++ b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
@@ -51,4 +51,4 @@ To disable SSH, set `ssh.enabled` to `false` in your Container configuration:
 
 </WranglerConfig>
 
-For more information, refer to the [SSH documentation](/containers/ssh/).
\ No newline at end of file
+For more information, refer to the [SSH documentation](/containers/ssh/).
diff --git a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
index 7a8ddd2b404d6c1..076405a6f32954f 100644
--- a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
+++ b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
@@ -6,7 +6,7 @@ date: 2025-11-12
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into WARP device metrics, connectivity, and network performance across your Cloudflare SASE deployment.
 
-We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience. 
+We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience.
 
 1. [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)
 2. [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)
@@ -15,4 +15,4 @@ We've released four new WARP and DEX device data sets that can be exported via [
 
 To create a new DEX or WARP Logpush job, customers can go to the account level of the Cloudflare dashboard > Analytics & Logs > Logpush to get started.
 
-![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
\ No newline at end of file
+![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
diff --git a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
index 25a72ef1269d528..eaa2318c8339332 100644
--- a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
+++ b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
@@ -2,7 +2,6 @@
 title: DEX Supports EU Customer Metadata Boundary
 description: Digital Experience Monitoring now fully supports the EU Customer Metadata Boundary
 date: 2026-02-19
-
 ---
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into [WARP](/warp-client/) device connectivity and performance to any internal or external application.
diff --git a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
index df5d41b9f6f8634..5dabd4aeb835f4e 100644
--- a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
@@ -9,4 +9,4 @@ date: 2026-04-28
 This Internet outage and traffic anomaly data is pulled from [Cloudflare Radar](https://radar.cloudflare.com/). All Internet outage and traffic anomaly observations can be viewed in the [Radar Outage Center](https://radar.cloudflare.com/outage-center).
 
 ![Digital Experience Monitoring dashboard notification for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_ux_notification.png)
-![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
\ No newline at end of file
+![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
diff --git a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
index 37b7e2b2737abdf..a85263a713f6a1e 100644
--- a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
@@ -4,9 +4,10 @@ description: Customers can run speed tests from the Cloudflare One Client to Clo
 date: 2026-04-28
 ---
 
-IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge. 
+IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge.
 
 Each speed test includes the following metrics:
+
 - Internet speed: download and upload throughput
 - Latency: download, upload, unloaded latency, and jitter
 - Network quality score: video streaming, webchat/real-time communication (RTC)
diff --git a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
index abfb872fa28d368..6af9120fe4e08ee 100644
--- a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
+++ b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
@@ -4,9 +4,10 @@ description: Digital experience now supports testing applications with authentic
 date: 2026-04-29
 ---
 
-[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/). 
+[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/).
 
 Digital experience tests also have enhanced configuration options including:
+
 - New HTTP methods (DELETE, PATCH, POST, PUT)
 - Secret Store headers, custom plain text headers, and custom request bodies
 - Advanced settings: follow redirects, response bodies, response headers, and allow untrusted certificates
diff --git a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
index 73705ab18a430b6..608405c5701e920 100644
--- a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
+++ b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
@@ -9,6 +9,7 @@ date: 2026-04-14T12:00:00Z
 **Account-level DLP settings are now available** in Cloudflare One. You can now configure advanced DLP settings at the account level, including OCR, AI context analysis, and payload masking. This provides consistent enforcement across all DLP profiles and simplifies configuration management.
 
 Key changes:
+
 - **Consistent enforcement**: Settings configured at the account level apply to all DLP profiles
 - **Simplified migration**: Settings enabled on any profile are automatically migrated to account level
 - **Deprecation notice**: Profile-level advanced settings will be deprecated in a future release
diff --git a/src/content/changelog/dlp/2025-07-17-document-matching.mdx b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
index 7d3ef70acea78af..16c90b0f67b6ee1 100644
--- a/src/content/changelog/dlp/2025-07-17-document-matching.mdx
+++ b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
@@ -15,10 +15,9 @@ You can now create [document-based](/cloudflare-one/data-loss-prevention/detecti
 - **Granular control with similarity percentage:** Define a minimum similarity percentage (0-100%) that a document must meet to trigger a detection, reducing false positives.
 
 - **Comprehensive coverage:** Apply these document-based detection entries in:
+  - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
 
-    - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
-
-    - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
+  - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
 
 - **Identify sensitive data:** This new detection entry type is ideal for identifying sensitive data within completed forms, templates, or even small snippets of a larger document, helping you prevent data exfiltration and ensure compliance.
 
diff --git a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
index 21f93780d77fd28..17cdc9544eb17e9 100644
--- a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
+++ b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
@@ -24,14 +24,14 @@ To help you apply these topics quickly, we have also released five new predefine
 
 3. **Granular Guardrails**
 
-    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
+   You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
 
-    ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
+   ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
 
- 4. **Full Prompt Logging**
-   
-    To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by ```conversation_id```, allowing you to reconstruct the full context of an interaction that led to a policy violation.
+4. **Full Prompt Logging**
 
-    ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
+   To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by `conversation_id`, allowing you to reconstruct the full context of an interaction that led to a policy violation.
+
+   ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
 
 AI prompt protection is now available in open beta. To learn more about it, read the [blog](https://blog.cloudflare.com/ai-prompt-protection/#closing-the-loop-logging) or refer to [AI prompt topics](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics).
diff --git a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
index 5c12da589a2636c..d8e05425862ab77 100644
--- a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
+++ b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
@@ -11,7 +11,7 @@ Gateway now includes a predefined DLP profile called **Unsanitized HAR** that de
 
 ## How to configure a HAR file policy
 
-In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to  **Zero Trust** >  **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
+In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
 
 | Selector    | Operator | Value             | Action |
 | ----------- | -------- | ----------------- | ------ |
diff --git a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
index 7326522ab2e356e..649f291806b1ee8 100644
--- a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
+++ b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
@@ -7,11 +7,11 @@ products: [dlp]
 
 The **Credentials and Secrets** DLP profile now includes three new predefined entries for detecting Cloudflare API credentials:
 
-| Entry name | Token prefix | Detects |
-| --- | --- | --- |
-| Cloudflare User API Key | `cfk_` | User-scoped API keys |
-| Cloudflare User API Token | `cfut_` | User-scoped API tokens |
-| Cloudflare Account Owned API Token | `cfat_` | Account-scoped API tokens |
+| Entry name                         | Token prefix | Detects                   |
+| ---------------------------------- | ------------ | ------------------------- |
+| Cloudflare User API Key            | `cfk_`       | User-scoped API keys      |
+| Cloudflare User API Token          | `cfut_`      | User-scoped API tokens    |
+| Cloudflare Account Owned API Token | `cfat_`      | Account-scoped API tokens |
 
 These detections target the new [Cloudflare API credential format](/fundamentals/api/get-started/token-formats/), which uses a structured prefix and a CRC32 checksum suffix. The identifiable prefix makes it possible to detect leaked credentials with high confidence and low false positive rates — no surrounding context such as `Authorization: Bearer` headers is required.
 
@@ -26,9 +26,9 @@ Credentials generated before this format change will not be matched by these ent
 
 Example policy:
 
-| Selector | Operator | Value | Action |
-| --- | --- | --- | --- |
-| DLP Profile | in | _Credentials and Secrets_ | Block |
+| Selector    | Operator | Value                     | Action |
+| ----------- | -------- | ------------------------- | ------ |
+| DLP Profile | in       | _Credentials and Secrets_ | Block  |
 
 You can also enable individual entries to scope detection to specific credential types — for example, enabling **Account Owned API Token** detection without enabling **User API Key** detection.
 
diff --git a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
index a4a744c06468c98..64134f5ef20859c 100644
--- a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
+++ b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
@@ -2,7 +2,7 @@
 title: Detect PII records with a new predefined DLP profile
 description: A new predefined DLP profile detects records that contain multiple types of personal data, reducing false positives from isolated matches.
 date: 2026-04-28
-products: 
+products:
   - dlp
 ---
 
diff --git a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
index 483aed6201b6f66..fda8a201e4ce67f 100644
--- a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
+++ b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
@@ -7,6 +7,7 @@ date: 2026-03-31
 Internal DNS is now in open beta.
 
 ## Who can use it?
+
 Internal DNS is bundled as a part of Cloudflare Gateway and is now available to every Enterprise customer with one of the following subscriptions:
 
 - Cloudflare Zero Trust Enterprise
diff --git a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
index ada68f5dc86c767..e9117eeb36fbf71 100644
--- a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
+++ b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
@@ -3,6 +3,7 @@ title: Account-level enforce DNS-only
 description: Bypass Cloudflare's reverse proxy for all zones in your account with a single API call.
 date: 2026-04-28
 ---
+
 import { DashButton } from "~/components";
 
 You can now disable Cloudflare's reverse proxy across all zones in your account simultaneously using the new `enforce_dns_only` setting. When enabled, Cloudflare responds to DNS queries for all proxied records with your origin IP addresses instead of Cloudflare's anycast IPs.
diff --git a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
index e03702fa3be2931..eb2897fd7f98f7b 100644
--- a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
+++ b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
@@ -10,11 +10,11 @@ date: 2025-08-21
 You can now create a client (a [Durable Object stub](/durable-objects/api/stub/)) to a Durable Object with the new `getByName` method, removing the need to convert Durable Object names to IDs and then create a stub.
 
 ```js
-// Before: (1) translate name to ID then (2) get a client 
+// Before: (1) translate name to ID then (2) get a client
 const objectId = env.MY_DURABLE_OBJECT.idFromName("foo"); // or .newUniqueId()
-const stub = env.MY_DURABLE_OBJECT.get(objectId); 
+const stub = env.MY_DURABLE_OBJECT.get(objectId);
 
-// Now: retrieve client to Durable Object directly via its name 
+// Now: retrieve client to Durable Object directly via its name
 const stub = env.MY_DURABLE_OBJECT.getByName("foo");
 
 // Use client to send request to the remote Durable Object
@@ -23,4 +23,4 @@ const rpcResponse = await stub.sayHello();
 
 Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together. You can have billions of Durable Objects, providing isolation between application tenants.
 
-To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
\ No newline at end of file
+To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
diff --git a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
index 10b3c5b7270cdbe..b0b6b6b70c779bb 100644
--- a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
+++ b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
 
 ![Screenshot of Durable Objects Data Studio](~/assets/images/workers/changelog/do-data-studio.png)
 
-You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.  
+You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.
 
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
diff --git a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
index 7d4b1c1963247eb..ab0bc29c8091916 100644
--- a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
+++ b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
@@ -9,9 +9,10 @@ date: 2025-12-12
 
 import { DashButton } from "~/components";
 
-Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). 
+Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier).
 
 To view your SQLite storage usage, go to the **Durable Objects** page
+
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
 If you do not want to incur costs, please take action such as optimizing queries or deleting unnecessary stored data in order to reduce your SQLite storage usage ahead of the January 7th target. Only usage on and after the billing target date will incur charges.
diff --git a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
index c3a7dd97977d0d4..01b6f70aebb1c1f 100644
--- a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
+++ b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
@@ -15,19 +15,19 @@ This is especially useful for [alarms](/durable-objects/api/alarms/), where ther
 import { DurableObject } from "cloudflare:workers";
 
 export class ChatRoom extends DurableObject {
-  async getRoomName() {
-    // ctx.id.name returns the name passed to getByName() or idFromName()
-    return this.ctx.id.name;
-  }
+	async getRoomName() {
+		// ctx.id.name returns the name passed to getByName() or idFromName()
+		return this.ctx.id.name;
+	}
 }
 
 // Worker
 export default {
-  async fetch(request, env) {
-    const stub = env.CHAT_ROOM.getByName("general");
-    const roomName = await stub.getRoomName();
-    return new Response(`Welcome to ${roomName}!`);
-  },
+	async fetch(request, env) {
+		const stub = env.CHAT_ROOM.getByName("general");
+		const roomName = await stub.getRoomName();
+		return new Response(`Welcome to ${roomName}!`);
+	},
 };
 ```
 
diff --git a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
index d4933092b676b0e..7bbf5100d38aea3 100644
--- a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
+++ b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
@@ -12,4 +12,4 @@ Customers can use this feature to dynamically add context to their emails, such
 
 ![Subaddressing](~/assets/images/changelog/email-routing/subaddressing.png)
 
-Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
\ No newline at end of file
+Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
diff --git a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
index 2a643465f298e14..7ac05e0429ad659 100644
--- a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
+++ b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
@@ -16,4 +16,4 @@ This feature is available across these Email security packages:
 
 - **Advantage**
 - **Enterprise**
-- **Enterprise + PhishGuard**
\ No newline at end of file
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
index 7e74cf7136cb225..24afb396ce499bc 100644
--- a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
+++ b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
@@ -13,7 +13,6 @@ These reports offer several key benefits:
 - **Configuration Transparency:** Gain a clear view of your policy, submission, and domain configurations to ensure optimal setup.
 - **Account Takeover Risks:** Get a snapshot of your M365 risky users (requires a Microsoft Entra ID P2 license and [M365 SaaS integration](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/microsoft-365/)).
 
-
 To get started, refer to [Download a security report](/cloudflare-one/email-security/monitoring/download-report/#download-a-security-report).
 ![Report](~/assets/images/changelog/email-security/report.png)
 
diff --git a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
index 47d73e8920e5d3c..cbb47a69c0949ea 100644
--- a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
+++ b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
@@ -6,8 +6,7 @@ date: 2025-11-18
 
 # Adjustment to Final Disposition column
 
-The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
----
+## The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
 
 ### What's Changing
 
diff --git a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
index b8d67579c27c156..92b39dac688afa0 100644
--- a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
+++ b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
@@ -1,6 +1,6 @@
 ---
 title: Reclassifications to Submissions
-description: Submission terminology update to reflect outcomes 
+description: Submission terminology update to reflect outcomes
 date: 2025-12-03T21:11:33Z
 ---
 
@@ -10,7 +10,8 @@ Submissions are leveraged to tune future variants of campaigns. To respect data
 
 ![nav_example](~/assets/images/changelog/email-security/reclassification-submission.png)
 
-This applies to all Email Security packages: 
--   **Advantage** 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
index b38737ac382f6db..e12c5cc1bef0386 100644
--- a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
+++ b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
@@ -4,7 +4,7 @@ description: Additional post delivery action log details for failures
 date: 2026-01-12T11:15:33Z
 ---
 
-The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field. 
+The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field.
 
 :::note
 Error messages will vary depending on whether you are using Google Workspace or Microsoft 365.
@@ -14,6 +14,7 @@ Error messages will vary depending on whether you are using Google Workspace or
 
 This update allows you to see the full lifecycle of a failed action. For instance, if an administrator tries to move an email that has already been deleted or moved manually, the log will now show the multiple retry attempts and the specific destination error.
 
-This applies to all Email Security packages: 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
index 2b9c5533289c542..fdf3bbd3fac9920 100644
--- a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
+++ b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
@@ -6,17 +6,17 @@ date: 2026-02-02T11:05:33Z
 
 We have updated the Monitoring page to provide a more streamlined and insightful experience for administrators, improving both data visualization and dashboard accessibility.
 
-* **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis. 
-![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
-* **Improved Accessibility & Usability**: 
-    * **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation. 
-    * **Actionable UI**: All available actions are now accessible via dedicated buttons. 
-    * **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions. 
-![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
-* **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
-![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
+- **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis.
+  ![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
+- **Improved Accessibility & Usability**:
+  _ **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation.
+  _ **Actionable UI**: All available actions are now accessible via dedicated buttons. \* **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions.
+  ![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
+- **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
+  ![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
 
-This applies to all Email Security packages: 
--   **Advantage** 
--   **Enterprise** 
--   **Enterprise + PhishGuard** 
+This applies to all Email Security packages:
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
index 6d9695bd7a66d3e..40ee34a930aa4d0 100644
--- a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
+++ b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
@@ -10,12 +10,12 @@ In the dashboard, infinite paging is now supported in the Investigations view. T
 
 For high-volume use cases, we recommend:
 
--   **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
--   **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
--   **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
+- **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
+- **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
+- **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
 
 This applies to all Email Security packages:
 
--   **Advantage**
--   **Enterprise**
--   **Enterprise + PhishGuard**
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
index a69648a508bacbf..cf4ab36e568d60c 100644
--- a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
@@ -3,12 +3,14 @@ title: DANE Support for MX Deployments
 description: DNSSEC-backed TLSA records now available on regional MX hostnames for verified encrypted email delivery
 date: 2026-04-06T09:00:00Z
 ---
+
 Cloudflare Email Security now supports DANE (DNS-based Authentication of Named Entities) for MX deployments. This enhancement strengthens email transport security by enabling DNSSEC-backed certificate verification for our regional MX records.
 
-* Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
-* DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
+- Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
+- DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
 
 This applies to all Email Security packages:
--   **Advantage**
--   **Enterprise**
--   **Enterprise + PhishGuard**
+
+- **Advantage**
+- **Enterprise**
+- **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
index 3019f6e986513d4..eab1731927d760e 100644
--- a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
@@ -5,12 +5,14 @@ date: 2026-04-07 09:00:00 UTC
 ---
 
 Cloudflare Email security now supports **Triage Status Tracking for User Submissions**. This enhancement gives SOC teams a streamlined way to track, manage, and prioritize user-submitted emails directly within the Cloudflare One dashboard.
+
 - The User Submissions table now includes a **Status** column with three states: **Unreviewed** (new submissions awaiting triage), **Reviewed** (submissions assessed by the SOC team), and **Escalated** (submissions escalated to team submissions for further investigation). Analysts can quickly update statuses and filter the table to focus on what needs attention.
 - SOC teams can now organize their triage workflows, avoid duplicate reviews, and make sure critical threats get escalated for deeper investigation—bringing order to the chaos of high-volume submission management.
 
 Triage Status Tracking is **automatically available** for all Email security customers using the user submissions feature. No additional configuration is required; customers just need to make sure user submissions are being sent to their user submission aliases.
 
 This applies to all Email security packages:
+
 - **Advantage**
 - **Enterprise**
 - **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
index 558c35e1449d8c7..8447a0ad8b9c7aa 100644
--- a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
+++ b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
@@ -3,6 +3,7 @@ title: Cloudy Summaries in PhishNet O365
 description: Cloudy email summaries are now available in PhishNet for Office 365 environments.
 date: 2026-05-06T18:15:13Z
 ---
+
 PhishNet users can now access **Cloudy summaries** directly within the email investigation experience. When reviewing a message in PhishNet, users will see an AI-generated summary that provides additional context and key details about the email.
 
 These summaries help users quickly understand the nature of a message without needing to manually parse through headers, body content, and detection signals. Cloudy surfaces the most relevant information so users can make faster, more informed decisions about suspicious emails.
diff --git a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
index a5377b7e567f220..55a9de27459f439 100644
--- a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
+++ b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
@@ -14,11 +14,11 @@ We're announcing the GA of **User Groups for Cloudflare Dashboard** and **System
 
 **SCIM User Groups [GA]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.
 
-**Stability & Scale**: 
+**Stability & Scale**:
 These features have undergone extensive testing during the Public Beta period and are now ready for production use across enterprises of all sizes.
 
 :::note
-SCIM Virtual Groups  (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
+SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
 :::
 
 For more info:
diff --git a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
index 78ffc7cb93ea799..3bf99528e750d6f 100644
--- a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
+++ b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
@@ -1,31 +1,38 @@
 ---
 title: Introducing new headers for rate limiting on Cloudflare's API
-description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code. 
+description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code.
 products:
   - fundamentals
 date: 2025-09-03
 ---
-Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available. 
 
-Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this. 
+Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available.
 
-As always, if you need any help with rate limits, please contact Support. 
+Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this.
+
+As always, if you need any help with rate limits, please contact Support.
 
 ### Changes
+
 #### New Headers
 
 **Headers that are always returned:**
+
 - `Ratelimit`: List of service limit items, composed of the limit name, the remaining quota (`r`) and the time next window resets (`t`). For example: `"default";r=50;t=30`
 - `Ratelimit-Policy`: List of quota policy items, composed of the policy name, the total quota (`q`) and the time window the quota applies to (`w`). For example: `"burst";q=100;w=60`
 
 **Returned only when a rate limit has been reached (error code: 429):**
+
 - Retry-After: Number of Seconds until more capacity is available, rounded up
 
 #### SDK Back offs
-- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached. 
+
+- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached.
 
 ### GraphQL and Edge APIs
-These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL. 
+
+These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL.
 
 ### For more information
-* [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
+
+- [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
diff --git a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
index f3c21ce51683451..2d4cd4c94696926 100644
--- a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
+++ b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
@@ -6,7 +6,8 @@ products:
 date: 2025-09-08
 ---
 
-Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future. 
+Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future.
 
 ## For more information
+
 - [Two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
index 7cdd79523b47438..7132df4e0c21e5a 100644
--- a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
+++ b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
@@ -6,7 +6,8 @@ products:
 date: 2025-09-25
 ---
 
-Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address. 
+Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address.
 
 ## For more information
+
 - [Log in to Cloudflare](/fundamentals/user-profiles/login/)
diff --git a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
index ef6b79ccba485df..a55ff67b07c1c01 100644
--- a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
+++ b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
@@ -12,4 +12,4 @@ Users can now specify that they want to retrieve Cloudflare documentation as mar
 curl https://developers.cloudflare.com/workers/ -H 'Accept: text/markdown'  -v
 ```
 
-If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
\ No newline at end of file
+If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
diff --git a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
index c9763acda83fa9f..4d7ebf5cd529a99 100644
--- a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
+++ b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
@@ -15,4 +15,3 @@ Today, we are launching a new user experience which allows users to manage their
 ## For more information
 
 - [Cloudflare dashboard SSO](/fundamentals/manage-members/dashboard-sso/)
-
diff --git a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
index 206794e93f44faa..07fdea6b5a065fe 100644
--- a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
@@ -4,15 +4,15 @@ description: Cloudflare now offers email two-factor authentication to protect yo
 date: 2025-10-30
 ---
 
-Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support. 
+Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support.
 
-Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already. 
+Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already.
 
 You can now enable email 2FA on the Cloudflare dashboard:
 
 1. Go to **Profile** at the top right corner.
 2. Select **Authentication**.
-3. Under **Two-Factor Authentication**, select **Set up**.  
+3. Under **Two-Factor Authentication**, select **Set up**.
 
 ## Sign-in security best practices
 
diff --git a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
index b8e0027220e35a2..612e193af27fb2f 100644
--- a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
@@ -1,5 +1,5 @@
 ---
-title: Revamped Member Management UI 
+title: Revamped Member Management UI
 description: Simplifying the management of users, groups, and permissions within Cloudflare.
 products:
   - fundamentals
@@ -8,7 +8,6 @@ date: 2025-10-30
 
 As Cloudflare's platform has grown, so has the need for precise, role-based access control. We’ve redesigned the Member Management experience in the Dashboard to help administrators more easily discover, assign, and refine permissions for specific principals.
 
-
 ### What's New
 
 **Refreshed member invite flow**
@@ -17,10 +16,10 @@ We overhauled the Invite Members UI to simplify inviting users and assigning per
 
 ![Updated Invite Flow UX](~/assets/images/changelog/fundamentals/2025-10-30-invite-experience.gif)
 
-
 **Refreshed Members Overview Page**
- 
+
 We've updated the Members Overview Page to clearly display:
+
 - Member 2FA status
 - Which members hold Super Admin privileges
 - API access settings per member
@@ -30,12 +29,11 @@ We've updated the Members Overview Page to clearly display:
 
 **New Member Permission Policies Details View**
 
-We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have. 
+We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have.
 
 ![Updated Permission Policies Details Screen](~/assets/images/changelog/fundamentals/2025-10-30-permission-policies-screen.gif)
 
-
-**Improved Member Permission Workflow** 
+**Improved Member Permission Workflow**
 
 We redesigned the permission management experience to make it faster and easier for administrators to review roles and grant access.
 
@@ -43,4 +41,4 @@ We redesigned the permission management experience to make it faster and easier
 
 **Account-scoped Policies Restrictions Relaxed**
 
-Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions. 
\ No newline at end of file
+Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions.
diff --git a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
index 4809af309b7fae0..c83d90c5c82e0db 100644
--- a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
+++ b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
@@ -6,9 +6,10 @@ date: 2026-01-23
 
 ![Screenshot of new 2FA enrollment experience](~/assets/images/changelog/fundamentals/2026-01-23-2fa-interstitial.png)
 
-In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers. 
+In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers.
 
-We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works. 
+We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works.
 
-## For more information 
-* [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
+## For more information
+
+- [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
diff --git a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
index e00305d994595e1..0bd7606af0188e8 100644
--- a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
+++ b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
@@ -8,7 +8,6 @@ date: 2026-02-12
 
 Cloudflare's network now supports real-time content conversion at the source, for enabled zones using [content negotiation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation) headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for `text/markdown` in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
 
-
 Here is a curl example with the `Accept` negotiation header requesting this page from our developer documentation:
 
 ```bash
@@ -39,4 +38,4 @@ ultimately resulting in better results while minimizing token waste.
 ...
 ```
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
\ No newline at end of file
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
diff --git a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
index 33a3ae22e6230f3..69a7003183ac4a6 100644
--- a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
+++ b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
@@ -16,4 +16,4 @@ This release adds the following improvements:
 
 If you haven’t enabled automatic Markdown conversion yet, visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section of the Cloudflare dashboard and enable **Markdown for Agents**.
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
\ No newline at end of file
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
diff --git a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
index e6ad76ed4ec43a0..5ba8aed4decf5c8 100644
--- a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
@@ -57,5 +57,6 @@ curl -s --compressed -H "Accept: application/problem+json" -A "TestAgent/1.0" -H
 ```
 
 References:
+
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
index aa790c1bc84902b..7635eb13215cd99 100644
--- a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
@@ -12,15 +12,15 @@ Cloudflare-generated 1xxx error responses now include a standard `Retry-After` H
 
 Seven retryable error codes now emit `Retry-After`:
 
-| Error code | Retry-After (seconds) | Error name |
-|---|---|---|
-| 1004 | 120 | DNS resolution error |
-| 1005 | 120 | Banned zone |
-| 1015 | 30 | Rate limited |
-| 1033 | 120 | Argo Tunnel error |
-| 1038 | 60 | HTTP headers limit exceeded |
-| 1200 | 60 | Cache connection limit |
-| 1205 | 5 | Too many redirects |
+| Error code | Retry-After (seconds) | Error name                  |
+| ---------- | --------------------- | --------------------------- |
+| 1004       | 120                   | DNS resolution error        |
+| 1005       | 120                   | Banned zone                 |
+| 1015       | 30                    | Rate limited                |
+| 1033       | 120                   | Argo Tunnel error           |
+| 1038       | 60                    | HTTP headers limit exceeded |
+| 1200       | 60                    | Cache connection limit      |
+| 1205       | 5                     | Too many redirects          |
 
 The header value matches the existing `retry_after` body field in JSON and Markdown responses.
 
@@ -39,5 +39,6 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
+
 - [RFC 9110 section 10.2.3 - Retry-After](https://www.rfc-editor.org/rfc/rfc9110#section-10.2.3)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
index 92f5a45e27a8c57..c0c1a7659fedd48 100644
--- a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
+++ b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-18
 ---
 
-Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers. 
+Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers.
 
 Customers can now sync users and group information from Authentik to Cloudflare, apply Permission Policies to those groups, and manage the lifecycle of users & groups directly from your Authentik Identity Provider.
 
diff --git a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
index 115c15516aecbda..48fa5bd55c357ee 100644
--- a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
+++ b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
@@ -17,9 +17,9 @@ Cloudflare dashboard SCIM provisioning operations are now captured in [Audit Log
 | Create SCIM User  | User provisioned from IdP               |
 | Replace SCIM User | User fully replaced (PUT)               |
 | Update SCIM User  | User attributes modified (PATCH)        |
-| Delete SCIM User  | Member deprovisioned                      |
+| Delete SCIM User  | Member deprovisioned                    |
 | Create SCIM Group | Group provisioned from IdP              |
 | Update SCIM Group | Group membership or attributes modified |
-| Delete SCIM Group | Group deprovisioned                           |
+| Delete SCIM Group | Group deprovisioned                     |
 
 For more details, refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/).
diff --git a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
index 66f075b8044732c..99e5c7faac36b0e 100644
--- a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
+++ b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
@@ -18,7 +18,7 @@ We're announcing the public beta of **Organizations** for enterprise customers,
 
 **Centralized Account Management**: At launch, every Organization member has the Organization Super Admin role. Organization Super Admins can invite other users and manage any child account under the Organization implicitly.
 **Shared policies**: Share [WAF](/waf/custom-rules/) or [Gateway](/cloudflare-one/traffic-policies/tiered-policies/organizations/) policies across multiple accounts within your Organization to simplify centralized policy management.
-**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year. 
+**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year.
 
 **Unified analytics**: View, filter, and download aggregate HTTP analytics across all Organization child accounts from a single dashboard for centralized visibility into traffic patterns and security events.
 
diff --git a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
index 4fb052b1583582b..6df437b0b5fe8f2 100644
--- a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
+++ b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
@@ -1,6 +1,6 @@
 ---
 title: API tokens now detectable by secret scanning tools
-description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code. 
+description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code.
 date: 2026-04-10
 ---
 
diff --git a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
index ea662602678945a..b21e3e867f40139 100644
--- a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
+++ b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
@@ -5,29 +5,45 @@ products:
   - fundamentals
 date: 2026-04-14
 ---
+
 OAuth allows third-party applications to access your Cloudflare account on your behalf — like when Wrangler deploys Workers or when monitoring tools read your analytics. You now have **granular control** over which accounts these applications can access, plus the ability to revoke access anytime.
+
 ## What's new
+
 ### Choose which accounts to authorize
+
 When authorizing an OAuth application, you can now **select specific accounts** instead of granting access to all your accounts:
+
 - **Account-by-account selection** — Choose exactly which accounts the application can access
 - **"All accounts" option** — Still available for trusted tools like Wrangler
-This gives you precise control who can access your data.
+  This gives you precise control who can access your data.
+
 ### Clear consent screens
+
 The OAuth consent screen now shows:
+
 - **What the application can access** — Explicit list of permissions being requested
-- **Who created the application** — Application owner and contact information  
+- **Who created the application** — Application owner and contact information
 - **Which accounts you're authorizing** — Checkboxes for account selection
+
 ### Revoke access anytime
+
 Manage authorized OAuth applications from your profile:
+
 - **See all connected apps** — View every OAuth application with access to your accounts
 - **Review permissions and scope** — Check what each application can do and which accounts it can access
 - **Revoke instantly** — Remove access with one click when you no longer need it
-To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
+  To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
+
 ## Why this matters
+
 These updates give you:
+
 - **Granular control** — Authorize apps per-account instead of all-or-nothing
 - **Transparency** — Know exactly what you're authorizing before you consent
 - **Security** — Limit blast radius by restricting access to only necessary accounts
 - **Easy cleanup** — Revoke access when applications are no longer needed
+
 ## Learn more
+
 Read more about these improvements in our blog post: [Improving the OAuth consent experience](https://blog.cloudflare.com/improved-developer-security/#improving-the-oauth-consent-experience).
diff --git a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
index 0bd7547904452c2..02073d22df3580c 100644
--- a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
@@ -50,5 +50,6 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
+
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 5xx error documentation](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
index 521711f9c22d54b..2babbbfb86081cd 100644
--- a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
+++ b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
@@ -11,34 +11,34 @@ You can now navigate, switch context, and take common actions in the Cloudflare
 
 ## Navigate
 
-| Shortcut | Action |
-| --- | --- |
-| `g h` | Go to Home |
-| `g a` | Go to account overview |
-| `g z` | Go to zone overview |
-| `g p` | Go to your profile |
-| `g w` | Go to Workers & Pages |
-| `g o` | Go to Zero Trust |
-| `g b` | Go to billing |
+| Shortcut      | Action                                                 |
+| ------------- | ------------------------------------------------------ |
+| `g h`         | Go to Home                                             |
+| `g a`         | Go to account overview                                 |
+| `g z`         | Go to zone overview                                    |
+| `g p`         | Go to your profile                                     |
+| `g w`         | Go to Workers & Pages                                  |
+| `g o`         | Go to Zero Trust                                       |
+| `g b`         | Go to billing                                          |
 | `g 1` – `g 5` | Go to a recent or pinned item (by position in sidebar) |
-| `t →` | Move to the next tab |
-| `t ←` | Move to the previous tab |
-| `p →` | Move to the next page of a table |
-| `p ←` | Move to the previous page of a table |
+| `t →`         | Move to the next tab                                   |
+| `t ←`         | Move to the previous tab                               |
+| `p →`         | Move to the next page of a table                       |
+| `p ←`         | Move to the previous page of a table                   |
 
 ## Take action
 
-| Shortcut | Action |
-| --- | --- |
-| `/` | Open quick search |
-| `?` | Show keyboard shortcuts |
-| `s a` | Switch account |
-| `s z` | Switch zone |
-| `s .` | Star or unstar the current zone |
-| `p .` | Pin or unpin the current page |
-| `t s` | Toggle the sidebar open or closed |
-| `t m` | Expand or collapse all sidebar menus |
-| `t a` | Toggle Ask AI sidebar |
-| `d .` | Toggle dark mode |
-| `c u` | Copy the current URL |
-| `c d` | Copy a deep link URL |
+| Shortcut | Action                               |
+| -------- | ------------------------------------ |
+| `/`      | Open quick search                    |
+| `?`      | Show keyboard shortcuts              |
+| `s a`    | Switch account                       |
+| `s z`    | Switch zone                          |
+| `s .`    | Star or unstar the current zone      |
+| `p .`    | Pin or unpin the current page        |
+| `t s`    | Toggle the sidebar open or closed    |
+| `t m`    | Expand or collapse all sidebar menus |
+| `t a`    | Toggle Ask AI sidebar                |
+| `d .`    | Toggle dark mode                     |
+| `c u`    | Copy the current URL                 |
+| `c d`    | Copy a deep link URL                 |
diff --git a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
index 6d777cba0965f65..ae01229a4717c46 100644
--- a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
+++ b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
@@ -7,9 +7,9 @@ hidden: false
 date: 2025-07-24
 ---
 
-[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more. 
+[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more.
 
-You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing  _Inspect on all ports_.
+You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing _Inspect on all ports_.
 
 ![HTTP Inspection on all ports setting](~/assets/images/gateway/Gateway-Inspection-all-ports.png)
 
diff --git a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
index 99deeee7c9cf019..85d54d9085242a7 100644
--- a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
+++ b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
@@ -3,15 +3,13 @@ title: Scam domain category introduced under Security Threats
 description: You can now create policies specifically targeting the Scam content
 date: 2025-07-28
 ---
- 
-We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
- 
-**New category added**
 
+We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
 
-| Parent ID | Parent Name           | Category ID | Category Name                 |
-| --------- | --------------------- | ----------- | ----------------------------- |
-| 21        | Security Threats      | 191          | Scam                |
+**New category added**
 
+| Parent ID | Parent Name      | Category ID | Category Name |
+| --------- | ---------------- | ----------- | ------------- |
+| 21        | Security Threats | 191         | Scam          |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
index 295f092f251e8cc..e4f36b80ddf1cbf 100644
--- a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
+++ b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
@@ -3,8 +3,9 @@ title: Google Bard Application replaced by Gemini
 description: The Google Bard application has been fully replaced with Gemini
 date: 2025-07-22
 ---
+
 The **Google Bard** application (ID: 1198) has been deprecated and fully removed from the system. It has been replaced by the **Gemini** application (ID: 1340).
-Any existing Gateway policies that reference the old Google Bard application will no longer function. 
+Any existing Gateway policies that reference the old Google Bard application will no longer function.
 To ensure your policies continue to work as intended, you should update them to use the new Gemini application.
 We recommend replacing all instances of the deprecated Bard application with the new Gemini application in your Gateway policies.
 For more information about application policies, please see the [Cloudflare Gateway documentation](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
index 0583881ed95d8cb..450c765b4b0e122 100644
--- a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
+++ b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
@@ -8,10 +8,10 @@ We have added three new domain categories under the Technology parent category,
 
 **New categories added**
 
-| Parent ID | Parent Name           | Category ID | Category Name                 |
-| --------- | --------------------- | ----------- | ----------------------------- |
-| 26        | Technology            | 194         | Keep Awake Software           |
-| 26        | Technology            | 192         | Remote Access                 |
-| 26        | Technology            | 193         | Shareware/Freeware            |
+| Parent ID | Parent Name | Category ID | Category Name       |
+| --------- | ----------- | ----------- | ------------------- |
+| 26        | Technology  | 194         | Keep Awake Software |
+| 26        | Technology  | 192         | Remote Access       |
+| 26        | Technology  | 193         | Shareware/Freeware  |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
index 6ae683bd7093044..0d4496f7a95d1af 100644
--- a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
+++ b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
@@ -4,14 +4,15 @@ description: We are preparing to remap some existing applications to better refl
 date: 2025-11-06
 ---
 
-We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28). 
+We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28).
 While the new categories are live now, we want to ensure you have ample time to review and adjust any existing rules you have configured against old categories.
 The remapping of existing applications into these new categories will be completed by January 30, 2026.
 This timeline allows you a dedicated period to:
+
 - Review the new category structure.
 - Identify any policies you have that target the older categories.
 - Adjust your rules to reference the new, more precise categories before the old mappings change.
-Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
+  Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
 
 **Applications being remappedd**
 | Application Name | Existing Category | New Category |
@@ -76,5 +77,4 @@ Once the applications have been fully remapped by January 30, 2026, you might ob
 | DHL Express | Shopping | Business |
 | UPS | Shopping | Business |
 
-
 For more information on creating HTTP policies, refer to [Applications and app types](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
index f20f7a3b16f224a..25d0dbe1436d1fa 100644
--- a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
+++ b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
@@ -10,13 +10,13 @@ Gateway [Protocol Detection](/cloudflare-one/traffic-policies/network-policies/p
 
 | Protocol     | Notes                                              |
 | ------------ | -------------------------------------------------- |
-| IMAP         | Internet Message Access Protocol — email retrieval  |
-| POP3         | Post Office Protocol v3 — email retrieval           |
-| SMTP         | Simple Mail Transfer Protocol — email sending       |
-| MYSQL        | MySQL database wire protocol                        |
-| RSYNC-DAEMON | rsync daemon protocol                               |
-| LDAP         | Lightweight Directory Access Protocol               |
-| NTP          | Network Time Protocol                               |
+| IMAP         | Internet Message Access Protocol — email retrieval |
+| POP3         | Post Office Protocol v3 — email retrieval          |
+| SMTP         | Simple Mail Transfer Protocol — email sending      |
+| MYSQL        | MySQL database wire protocol                       |
+| RSYNC-DAEMON | rsync daemon protocol                              |
+| LDAP         | Lightweight Directory Access Protocol              |
+| NTP          | Network Time Protocol                              |
 
 These protocols join the existing set of detected protocols (HTTP, HTTP2, SSH, TLS, DCERPC, MQTT, and TPKT) and can be used with the _Detected Protocol_ selector in [Network policies](/cloudflare-one/traffic-policies/network-policies/) to identify and filter traffic based on the application-layer protocol, without relying on port-based identification.
 
diff --git a/src/content/changelog/gateway/Gateway-application-categories-added.mdx b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
index ec9c5e87eb92aa4..2f049a7fb324a63 100644
--- a/src/content/changelog/gateway/Gateway-application-categories-added.mdx
+++ b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
@@ -4,7 +4,7 @@ description: Manage outbound traffic with more granular application categories
 date: 2025-10-28
 ---
 
-To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product. 
+To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product.
 
 We have added the following categories to provide more precise organization and allow for finer-grained policy creation, designed around how users interact with different types of applications:
 
@@ -18,7 +18,7 @@ We have added the following categories to provide more precise organization and
 - Photography & Graphic Design
 - Travel
 
-The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories. 
+The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories.
 
 The full remapping will be completed by January 30, 2026.
 
diff --git a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
index 3266a97d34dcdcb..05c67dbc7fb82e7 100644
--- a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
+++ b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
@@ -13,13 +13,13 @@ The `localConnectionString` field and `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_ST
 
 ```jsonc
 {
-  "hyperdrive": [
-    {
-      "binding": "HYPERDRIVE",
-      "id": "your-hyperdrive-id",
-      "localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require"
-    }
-  ]
+	"hyperdrive": [
+		{
+			"binding": "HYPERDRIVE",
+			"id": "your-hyperdrive-id",
+			"localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require",
+		},
+	],
 }
 ```
 
diff --git a/src/content/changelog/images/heic-support.mdx b/src/content/changelog/images/heic-support.mdx
index 8e5f655340c4c12..3baf6ce9372089c 100644
--- a/src/content/changelog/images/heic-support.mdx
+++ b/src/content/changelog/images/heic-support.mdx
@@ -3,6 +3,7 @@ title: HEIC support in Cloudflare Images
 description: You can use Images to ingest HEIC images
 date: 2025-07-08
 ---
+
 You can use Images to ingest HEIC images and serve them in supported output formats like AVIF, WebP, JPEG, and PNG.
 
 When inputting a HEIC image, dimension and sizing limits may still apply. Refer to our documentation to see limits for [uploading to Images](/images/storage/upload-images/methods/) or [transforming a remote image](/images/optimization/transformations/overview/).
diff --git a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
index 8124fd2d6475783..6cf9d6cc44b1683 100644
--- a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
+++ b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
@@ -16,5 +16,3 @@ The new hybrid architecture delivers substantial latency reductions throughout E
 
 - **p95 latency**: Reduced from ~150ms to ~50ms (67% decrease)
 - **p99 latency**: Reduced from ~350ms to ~250ms (29% decrease)
-
-
diff --git a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
index 41b68f6e7a4c23d..d1a8fedd27fa065 100644
--- a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
+++ b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
@@ -5,6 +5,7 @@ date: 2025-06-04
 ---
 
 We've made two large changes to load balancing:
+
 - Redesigned the user interface, now centralized at the **account level**.
 - Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot.
 
@@ -15,13 +16,11 @@ This update streamlines how you manage load balancers across multiple zones and
 **Key Enhancements:**
 
 - **Account-Level UI Consolidation:**
-
   - **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level.
 
   - **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution.
 
 - **Private Network Load Balancing:**
-
   - **Secure Internal Application Access:** Create [**Private Load Balancers**](/load-balancing/private-network/) to distribute traffic to applications hosted within your private network, ensuring they are not exposed to the public Internet.
 
   - **WARP & Magic WAN Integration:** Effortlessly direct internal traffic from users connected via Cloudflare WARP or through your Magic WAN infrastructure to the appropriate internal endpoint pools.
diff --git a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
index 3a0234e53c4e96e..62de99fae3dc892 100644
--- a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
+++ b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
@@ -6,4 +6,4 @@ date: 2025-07-09
 
 [Log Explorer](/log-explorer/) customers can now monitor their data ingestion volume to keep track of their billing. Monthly usage is displayed at the top of the [Log Search](/log-explorer/log-search/) and [Manage Datasets](/log-explorer/manage-datasets/) screens in Log Explorer.
 
-![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
\ No newline at end of file
+![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
diff --git a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
index 02585abcdaa5285..c384730c331df3f 100644
--- a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
+++ b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
@@ -6,4 +6,4 @@ date: 2025-08-15
 
 Customers can now rely on Log Explorer to meet their log retention compliance requirements.
 
-Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
\ No newline at end of file
+Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
diff --git a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
index c1d5c1454d91cdf..bd9895c6bf2de02 100644
--- a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
+++ b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
@@ -11,5 +11,3 @@ Create a custom field to log desired header or cookie values into the `http_requ
 ![Edit Custom fields](src/assets/images/changelog/log-explorer/edit-custom-fields.png)
 
 For more details, refer to [Headers and cookies](/log-explorer/log-search/#headers-and-cookies).
-
-
diff --git a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
index 794a2ac99ef2c6c..a75aa1ccc71be40 100644
--- a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
@@ -4,7 +4,7 @@ description: Log Search now lets you pivot directly to related Cloudflare tools
 date: 2025-09-11
 ---
 
-Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation. 
+Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation.
 
 From the `http_requests` or `fw_events` dataset results, right click on an IP Address or JA3 Fingerprint to pivot to the Investigate portal to lookup the reputation of an IP address or JA3 fingerprint.
 
@@ -14,6 +14,6 @@ Easily learn about error codes by linking directly to our documentation from the
 
 ![View documentation](src/assets/images/changelog/log-explorer/view-documentation.png)
 
-From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy. 
+From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy.
 
 ![View policy](src/assets/images/changelog/log-explorer/policyid.png)
diff --git a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
index 915ab5b7a8c0a8a..9747dcb5ea70714 100644
--- a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
@@ -9,6 +9,6 @@ The results table view of **Log Search** has been updated with additional functi
 - Remove/add columns.
 - Resize columns.
 - Sort columns.
-- Copy values from any field. 
+- Copy values from any field.
 
-![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
\ No newline at end of file
+![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
diff --git a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
index 8a5f4b9954eb85f..7fc5df7c52c3f95 100644
--- a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
+++ b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
@@ -6,4 +6,4 @@ date: 2025-11-04
 
 We're excited to announce that Log Explorer users can now cancel queries that are currently running.
 
-This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
\ No newline at end of file
+This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
diff --git a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
index 6808c2b7ad9372e..4abf8c6cf36fdee 100644
--- a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
+++ b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
@@ -8,4 +8,4 @@ We're excited to announce a quality-of-life improvement for Log Explorer users.
 
 Previously, if you were writing a long custom SQL query, the fixed-size window required excessive scrolling to view the full query. This update allows you to easily drag the bottom edge of the query window to make it taller. This means you can view your entire custom query at once, improving the efficiency and experience of writing and debugging complex queries.
 
-To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
\ No newline at end of file
+To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
diff --git a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
index 012bc9566a75154..20d9cb72a336e55 100644
--- a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
@@ -6,4 +6,4 @@ date: 2025-11-13
 
 We've resolved a bug in Log Explorer that caused inconsistencies between the custom SQL date field filters and the date picker dropdown. Previously, users attempting to filter logs based on a custom date field via a SQL query sometimes encountered unexpected results or mismatching dates when using the interactive date picker.
 
-This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
\ No newline at end of file
+This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
diff --git a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
index eaa4f6d50ecf078..b3d870198ed0514 100644
--- a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
@@ -18,7 +18,6 @@ The newly supported datasets include:
 - `Spectrum_events`
 - `Zaraz_events`
 
-
 ## Account Level
 
 - `Audit Logs`
@@ -31,9 +30,8 @@ The newly supported datasets include:
 - `Sinkhole HTTP`
 - `ipsec_logs`
 
-
 :::note
-`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying. 
+`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying.
 
 The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` role for querying.
 :::
@@ -43,4 +41,3 @@ The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` ro
 You can now use Log Explorer to query and filter with each of these datasets. For example, you can identify an IP address exhibiting suspicious behavior in the `FW_event` logs, and then instantly pivot to the `Network Analytics` logs or `Access` logs to see its network-level traffic profile or if it bypassed a corporate policy.
 
 To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/) and the [Cloudflare Logs documentation](/logs/).
-
diff --git a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
index 305f5dc7bb195af..866a7fd1ae4efd5 100644
--- a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
+++ b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
@@ -21,16 +21,16 @@ When configuring a dataset via the dashboard or API, you can define a specific s
 
 ```json
 {
-  "dataset": "firewall_events",
-  "enabled": true,
-  "fields": [
-    "Timestamp",
-    "ClientRequestHost",
-    "ClientIP",
-    "Action",
-    "EdgeResponseStatus",
-    "OriginResponseStatus"
-  ]
+	"dataset": "firewall_events",
+	"enabled": true,
+	"fields": [
+		"Timestamp",
+		"ClientRequestHost",
+		"ClientIP",
+		"Action",
+		"EdgeResponseStatus",
+		"OriginResponseStatus"
+	]
 }
 ```
 
diff --git a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
index 5c89e845304dd52..67a64c6fcf983b4 100644
--- a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
+++ b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
@@ -8,4 +8,4 @@ Cloudflare has introduced new fields to two Gateway-related datasets in Cloudfla
 
 - **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
 
-- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
\ No newline at end of file
+- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
diff --git a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
index 05e75fb1d124a1b..e21ad4b2e7c9787 100644
--- a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
+++ b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
@@ -24,4 +24,3 @@ Cloudflare has added new fields across multiple [Logpush datasets](/logs/logpush
 - **Zero Trust Network Session Logs**: `SNI`.
 
 For the complete field definitions for each dataset, refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/).
-
diff --git a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
index 0bcd5c49fa1c601..f5a502289149705 100644
--- a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
+++ b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
@@ -31,4 +31,4 @@ Pipelines SQL supports string functions, regex, hashing, JSON extraction, timest
 
 ## Get started
 
-To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
\ No newline at end of file
+To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
diff --git a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
index 451556a3ef70408..322bbb2f1f6d38d 100644
--- a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
+++ b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
@@ -7,13 +7,15 @@ date: 2026-04-21
 When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request. With subrequest merging enabled, subrequest data is embedded as a nested array field on the parent log record instead.
 
 ### What's new
+
 - New subrequest_merging field on Logpush jobs — Set "merge_subrequests": true when creating or updating an http_requests Logpush job to enable the feature.
 - New Subrequests log field — When subrequest merging is enabled, a Subrequests field (`array\<object\>`) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.
 
 ### Limitations
+
 - Applies to the http_requests (zone-scoped) dataset only.
 - A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.
 - Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.
 - Subrequests that do not qualify appear as separate log entries — no data is lost.
 - Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.
-- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
\ No newline at end of file
+- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
diff --git a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
index 7513b6b2b18466c..3e32c36dcd09c10 100644
--- a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
+++ b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
@@ -6,4 +6,4 @@ date: 2026-03-24
 
 The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** > **Interconnects**.
 
-Your existing configurations and functionality remain the same.
\ No newline at end of file
+Your existing configurations and functionality remain the same.
diff --git a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
index e11320f25ae558b..5bbd423dd5f10bf 100644
--- a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
+++ b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
@@ -12,4 +12,4 @@ If you are creating a new Pages project, the new V3 build image that includes No
 
 Note that you can always specify a particular version of Node.js or other built-in dependencies by [setting an environment variable](/pages/configuration/build-image/#override-default-versions).
 
-For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
\ No newline at end of file
+For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
diff --git a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
index 21d1fa8ffb558fc..c3385ca2e92c7dd 100644
--- a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
+++ b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
@@ -8,11 +8,12 @@ date: 2025-03-27 12:00:00 UTC
 
 [Queues](/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:
 
-* Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
-* You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
-* Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
+- Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
+- You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
+- Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
 
 To pause a queue using [Wrangler](/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.
+
 ```bash title="Pause and resume a queue"
 $ wrangler queues pause-delivery my-queue
 Pausing message delivery for queue my-queue.
@@ -24,6 +25,7 @@ Resumed message delivery for queue my-queue.
 ```
 
 Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:
+
 ```bash title="Purge a queue"
 $ wrangler queues purge my-queue
 ✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue
diff --git a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
index f8a980ffedaf040..f3d5e6d4def673d 100644
--- a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
+++ b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
@@ -11,13 +11,16 @@ date: 2025-04-17 12:00:00 UTC
 Pull consumers allow you to consume messages over HTTP from any environment—including outside of [Cloudflare Workers](/workers). They’re also useful when you need fine-grained control over how quickly messages are consumed.
 
 To setup a new queue with a pull based consumer using [Wrangler](/workers/wrangler/), run:
+
 ```sh title="Create a queue with a pull based consumer"
 npx wrangler queues create my-queue
 npx wrangler queues consumer http add my-queue
 ```
+
 You can also configure a pull consumer using the [REST API](/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.
 
 Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:
+
 ```bash title="Pull messages from a queue"
 curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" \
 --header "Authorization: Bearer ${API_TOKEN}" \
diff --git a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
index c7afb7767b23bb4..7cec3511f215302 100644
--- a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
+++ b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
@@ -19,4 +19,4 @@ curl "https://api.cloudflare.com/client/v4/accounts/<account_id>/queues/<queue_i
 
 You can also use our [SDKs](/fundamentals/api/reference/sdks/) for TypeScript, Python, and Go.
 
-To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
\ No newline at end of file
+To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
diff --git a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
index cd3df4c25c12a32..2ad33c340181762 100644
--- a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
+++ b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
@@ -22,21 +22,21 @@ An event is a structured record of something happening in your Cloudflare accoun
 
 ```json title="Example R2 bucket created event"
 {
-  "type": "cf.r2.bucket.created",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "location": "WNAM"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventTimestamp": "2025-07-28T10:30:00Z"
-  }
+	"type": "cf.r2.bucket.created",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"location": "WNAM"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventTimestamp": "2025-07-28T10:30:00Z"
+	}
 }
 ```
 
 Current [event sources](/queues/event-subscriptions/events-schemas/) include [R2](/r2/), [Workers KV](/kv/), [Workers AI](/workers-ai/), [Workers Builds](/workers/ci-cd/builds/), [Vectorize](/vectorize/), [Super Slurper](/r2/data-migration/super-slurper/), and [Workflows](/workflows/). More sources and events are on the way.
 
-For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
\ No newline at end of file
+For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
diff --git a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
index 4e3338c452ffb31..965d8f2e1ebbc40 100644
--- a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
+++ b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
@@ -7,7 +7,7 @@ products:
 hidden: false
 ---
 
-import { LinkCard} from "~/components";
+import { LinkCard } from "~/components";
 
 Today, we're launching the **open beta** for [R2 SQL](/r2-sql/): A serverless, distributed query engine that can efficiently analyze petabytes of data in [Apache Iceberg](https://iceberg.apache.org/) tables managed by [R2 Data Catalog](/r2/data-catalog).
 
diff --git a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
index 6ebf2f9f66bcf2e..55b2b18066b5d26 100644
--- a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
+++ b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
@@ -8,7 +8,6 @@ date: 2026-03-23
 
 [R2 SQL](/r2-sql/) now supports an expanded SQL grammar so you can write richer analytical queries without exporting data. This release adds CASE expressions, column aliases, arithmetic in clauses, 163 scalar functions, 33 aggregate functions, EXPLAIN, Common Table Expressions (CTEs),and full struct/array/map access. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying [Apache Iceberg](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](/r2/data-catalog/). This page documents the supported SQL syntax.
 
-
 ## Highlights
 
 - **Column aliases** — `SELECT col AS alias` now works in all clauses
diff --git a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
index f6fc972ca48a3f5..8be0bd3a266e62c 100644
--- a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
+++ b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
@@ -20,6 +20,7 @@ SELECT
 FROM my_namespace.sales_data
 WHERE json_contains(doc, 'email')
 ```
+
 For a full list of available functions, refer to [JSON functions](/r2-sql/sql-reference/scalar-functions/#json-functions).
 
 `EXPLAIN FORMAT JSON` returns query execution plans as structured JSON for programmatic analysis and observability integrations:
@@ -66,6 +67,7 @@ npx wrangler r2 sql query "${WAREHOUSE}" "EXPLAIN FORMAT JSON SELECT * FROM logp
 │ }                                    │
 └──────────────────────────────────────┘
 ```
+
 For more details, refer to [EXPLAIN](/r2-sql/sql-reference/#explain).
 
 Unpartitioned Iceberg tables can now be queried directly, which is useful for smaller datasets or data without natural time dimensions. For tables with more than 1000 files, partitioning is still recommended for better performance.
diff --git a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
index 3a0934b0df07041..73516e563584422 100644
--- a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
+++ b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
@@ -35,4 +35,4 @@ For the `summary` and `timeseries_groups` endpoints, the following dimensions ar
 - `tld`: Top-level domain for DNS names found in certificates SANs
 - `validation_level`: [Validation level](https://www.cloudflare.com/learning/ssl/types-of-ssl-certificates/)
 
-Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
\ No newline at end of file
+Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
diff --git a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
index 2204d6097ae38bf..702f6495af2db32 100644
--- a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
+++ b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
@@ -18,4 +18,4 @@ All `summary` and `timeseries_groups` endpoints in [`HTTP`](/api/resources/radar
 
 A new filter `geoId` was also added to all endpoints in [`HTTP`](/api/resources/radar/subresources/http/) and [`NetFlows`](/api/resources/radar/subresources/netflows/), allowing filtering by a specific administrative division.
 
-Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
\ No newline at end of file
+Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
diff --git a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
index 3058add7fdc87a1..1da325fa4aeeaef 100644
--- a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
+++ b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
@@ -34,4 +34,4 @@ On AS routing pages, the connectivity table now includes checkmarks for ASPA-ver
 
 ![Screenshot of the ASPA changes timeline on an AS routing page](~/assets/images/radar/aspa-asn-timeline.png)
 
-Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
\ No newline at end of file
+Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
diff --git a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
index b2c0e9bbf120e31..190b32137ec4b34 100644
--- a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
+++ b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
@@ -34,4 +34,4 @@ The [IP address space](https://radar.cloudflare.com/routing) chart now displays
 
 ![Screenshot of the IPv4 and IPv6 combined IP space chart](~/assets/images/radar/combined-ipv4-ipv6-space.png)
 
-Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
\ No newline at end of file
+Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
diff --git a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
index e4633c13a0546e5..9ab71e94e48955a 100644
--- a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
+++ b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
@@ -1,12 +1,12 @@
 ---
-title: RealtimeKit now supports track recording for per-participant audio
-description: You can now record specific participant audio tracks in RealtimeKit with the new track recording feature.
+title: Record specific participant audio tracks in RealtimeKit
+description: You can now record specific participant audio tracks in RealtimeKit with track recording.
 products:
   - realtime
 date: 2026-05-28
 ---
 
-You can now record specific participant audio tracks in RealtimeKit with the new [track recording feature](/realtime/realtimekit/recording-guide/track-recording/). Track recording creates separate WebM files for each participant instead of a single composite recording, which is useful for post-processing, transcription, and regulated or content-sensitive workflows.
+You can now record specific participant audio tracks in RealtimeKit with [track recording](/realtime/realtimekit/recording-guide/track-recording/). Track recording creates separate WebM files for each participant instead of a single composite recording, which is useful for post-processing, transcription, and regulated or content-sensitive workflows.
 
 To record specific participants, pass `user_ids` when starting a track recording:
 
@@ -28,7 +28,7 @@ To pass `user_ids` for selective track recording, use the following minimum SDK
 - Android Core or iOS Core: version `2.0.0` or later
 - Android UI Kit or iOS UI Kit: version `1.1.0` or later
 
-[RealtimeKit](/realtime/realtimekit/) provides SDKs and UI components so that you can build your own meeting experience on Cloudflare's global WebRTC infrastructure. Teams today build products ranging from telehealth to education on RealtimeKit for global audiences. You can get started today with our [Quickstart](/realtime/realtimekit/quickstart/) or take a look at our [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
+[RealtimeKit](/realtime/realtimekit/) provides SDKs and UI components so that you can build your own meeting experience on Cloudflare's [global WebRTC infrastructure](https://toxicitymax-rtk-track-recording.preview.developers.cloudflare.com/realtime/#realtime-sfu). Teams today build products ranging from telehealth to education on RealtimeKit for global audiences. You can get started today with our [Quickstart](/realtime/realtimekit/quickstart/) or take a look at our [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
 
 - [Track recording docs](/realtime/realtimekit/recording-guide/track-recording/)
 - [RealtimeKit Quickstart](/realtime/realtimekit/quickstart/)
diff --git a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
index a57aa1f4b10d63e..4bdd9ba554b4731 100644
--- a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
+++ b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
@@ -10,6 +10,7 @@ Administrators can now automatically escalate the risk score of a user if their
 
 New risk behaviors
 The following risk scoring behaviors are now available:
+
 - CrowdStrike low device score: Automatically increases a user's risk score when the connected device reports a "Low" score from CrowdStrike.
 - CrowdStrike medium device score: Automatically increases a user's risk score when the connected device reports a "Medium" score from CrowdStrike.
 
diff --git a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
index 629804f5f46a6f4..1ade4db9cf454f6 100644
--- a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
+++ b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
@@ -12,10 +12,10 @@ Cloudflare now provides two new request fields in the Ruleset engine that let yo
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
-| `cf.edge.client_tcp` | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC. |
-| `cf.timings.client_tcp_rtt_msec` | Number | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
+| Field                            | Type    | Description                                                                                                                                                          |
+| -------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.edge.client_tcp`             | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC.                                                        |
+| `cf.timings.client_tcp_rtt_msec` | Number  | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
 
 Example filter expression:
 
diff --git a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
index 97bc5ce82abd556..21cdd6b6e931809 100644
--- a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
+++ b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
@@ -10,8 +10,8 @@ You can use this field to build rules that target traffic based on geographic ma
 
 ### Field details
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field               | Type           | Description                                                                                                                   |
+| ------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | `ip.src.metro_code` | String \| null | The metro code (DMA) of the incoming request's IP address. Returns the designated market area code for the client's location. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
index 9fa9ac345fef774..598cf65b45365a7 100644
--- a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
+++ b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
@@ -12,12 +12,12 @@ Cloudflare Rulesets now include new functions that enable advanced expression lo
 
 ### New functions
 
-| Function | Description |
-| --- | --- |
-| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter. |
-| `join(array, delimiter)` | Joins an array of strings into a single string using the specified delimiter. |
-| `has_key(map, key)` | Returns `true` if the specified key exists in the map. |
-| `has_value(map, value)` | Returns `true` if the specified value exists in the map. |
+| Function                   | Description                                                                   |
+| -------------------------- | ----------------------------------------------------------------------------- |
+| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter.       |
+| `join(array, delimiter)`   | Joins an array of strings into a single string using the specified delimiter. |
+| `has_key(map, key)`        | Returns `true` if the specified key exists in the map.                        |
+| `has_value(map, value)`    | Returns `true` if the specified value exists in the map.                      |
 
 ---
 
diff --git a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
index 9e980cd5968d3b0..5dcd031a6e4ba0b 100644
--- a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
+++ b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
@@ -10,20 +10,20 @@ You can now control how Cloudflare buffers HTTP request and response bodies usin
 
 Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:
 
-| Mode | Behavior |
-| --- | --- |
+| Mode                   | Behavior                                                                                                      |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------- |
 | **Standard** (default) | Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management. |
-| **Full** | Buffers the entire request body before sending to origin. |
-| **None** | No buffering — the request body streams directly to origin without inspection. |
+| **Full**               | Buffers the entire request body before sending to origin.                                                     |
+| **None**               | No buffering — the request body streams directly to origin without inspection.                                |
 
 ### Response body buffering
 
 Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:
 
-| Mode | Behavior |
-| --- | --- |
-| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality. |
-| **None** | No buffering — the response body streams directly to the client without inspection. |
+| Mode                   | Behavior                                                                            |
+| ---------------------- | ----------------------------------------------------------------------------------- |
+| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality.     |
+| **None**               | No buffering — the response body streams directly to the client without inspection. |
 
 :::caution
 Setting body buffering to **None** may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.
@@ -33,11 +33,11 @@ Setting body buffering to **None** may break security functionality that require
 
 ```json
 {
-  "action": "set_config",
-  "action_parameters": {
-    "request_body_buffering": "standard",
-    "response_body_buffering": "none"
-  }
+	"action": "set_config",
+	"action_parameters": {
+		"request_body_buffering": "standard",
+		"response_body_buffering": "none"
+	}
 }
 ```
 
diff --git a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
index 52e81f07114dcef..04fd03621cb1999 100644
--- a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
+++ b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
@@ -10,8 +10,8 @@ You can use this field to identify slow Worker executions, detect performance re
 
 ### Field details
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field                    | Type    | Description                                                                                         |
+| ------------------------ | ------- | --------------------------------------------------------------------------------------------------- |
 | `cf.timings.worker_msec` | Integer | The time spent executing a Cloudflare Worker in milliseconds. Returns `0` if no Worker was invoked. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
index f2a0c12b6257543..c2584a81e336dae 100644
--- a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
@@ -43,6 +43,6 @@ You should ensure that `Client-Cert` and `Client-Cert-Chain` headers received by
 
 - **If you use WAF custom rules to block requests with invalid mTLS connections:** The transform rule is sufficient. For all requests that reach your origin server, the rule will overwrite any existing `Client-Cert` and `Client-Cert-Chain` headers.
 - **If you do not enforce mTLS at the WAF:** Add another transform rule that removes any incoming `Client-Cert` and `Client-Cert-Chain` headers from all requests (use expression `true`), ordered before the rule above. This ensures your origin server cannot receive client-supplied values for these HTTP headers.
-:::
+  :::
 
 For more information, refer to [Mutual TLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/), [Request Header Transform Rules](/rules/transform/request-header-modification/), and the [fields reference](/ruleset-engine/rules-language/fields/reference/).
diff --git a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
index 2954caaf3ad34d3..92228ab4dd7a5fd 100644
--- a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,10 +10,10 @@ Previously, QUIC RTT and delivery rate data was only available via the `Server-T
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
+| Field                             | Type    | Description                                                                                                                                                               |
+| --------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cf.timings.client_quic_rtt_msec` | Integer | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only populated for QUIC (HTTP/3) connections. Returns `0` for TCP connections. |
-| `cf.edge.l4.delivery_rate` | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request. |
+| `cf.edge.l4.delivery_rate`        | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request.             |
 
 ### Example: Route slow connections to a lightweight origin
 
@@ -27,9 +27,9 @@ cf.timings.client_tcp_rtt_msec > 200 or cf.timings.client_quic_rtt_msec > 200
 
 **Header modifications:**
 
-| Operation | Header name | Value |
-| --- | --- | --- |
-| Set | `X-High-Latency` | `true` |
+| Operation | Header name      | Value  |
+| --------- | ---------------- | ------ |
+| Set       | `X-High-Latency` | `true` |
 
 ### Example: Match low-bandwidth connections
 
diff --git a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
index 9ee69fcc0ccb9c9..89121e503ad9af2 100644
--- a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
@@ -21,6 +21,7 @@ Please ensure you read through the list of changes below before moving to this v
 ### Breaking Changes
 
 #### Addressing - Parameter Requirements Changed
+
 - `BGPPrefixCreateParams.cidr`: optional → **required**
 - `PrefixCreateParams.asn`: `number | null` → `number`
 - `PrefixCreateParams.loa_document_id`: required → **optional**
@@ -28,21 +29,26 @@ Please ensure you read through the list of changes below before moving to this v
 - `ServiceBindingCreateParams.service_id`: optional → **required**
 
 #### API Gateway
+
 - `ConfigurationUpdateResponse` removed
 - `PublicSchema` → `OldPublicSchema`
 - `SchemaUpload` → `UserSchemaCreateResponse`
 - `ConfigurationUpdateParams.properties` removed; use `normalize`
 
 #### CloudforceOne - Response Type Changes
+
 - `ThreatEventBulkCreateResponse`: `number` → complex object with counts and errors
 
 #### D1 Database - Query Parameters
+
 - `DatabaseQueryParams`: simple interface → union type (`D1SingleQuery | MultipleQueries`)
 - `DatabaseRawParams`: same change
 - Supports batch queries via `batch` array
 
 #### DNS Records - Type Renames (21 types)
+
 All record type interfaces renamed from `*Record` to short names:
+
 - `RecordResponse.ARecord` → `RecordResponse.A`
 - `RecordResponse.AAAARecord` → `RecordResponse.AAAA`
 - `RecordResponse.CNAMERecord` → `RecordResponse.CNAME`
@@ -66,52 +72,64 @@ All record type interfaces renamed from `*Record` to short names:
 - `RecordResponse.OpenpgpkeyRecord` → `RecordResponse.Openpgpkey`
 
 #### IAM Resource Groups
+
 - `ResourceGroupCreateResponse.scope`: optional single → **required array**
 - `ResourceGroupCreateResponse.id`: optional → **required**
 
 #### Origin CA Certificates - Parameter Requirements Changed
+
 - `OriginCACertificateCreateParams.csr`: optional → **required**
 - `OriginCACertificateCreateParams.hostnames`: optional → **required**
 - `OriginCACertificateCreateParams.request_type`: optional → **required**
 
 #### Pages
+
 - Renamed: `DeploymentsSinglePage` → `DeploymentListResponsesV4PagePaginationArray`
 - Domain response fields: many optional → **required**
 
 #### Pipelines - v0 to v1 Migration
+
 - Entire v0 API deprecated; use v1 methods (`createV1`, `listV1`, etc.)
 - New sub-resources: `Sinks`, `Streams`
 
 #### R2
+
 - `EventNotificationUpdateParams.rules`: optional → **required**
 - Super Slurper: `bucket`, `secret` now required in source params
 
 #### Radar
+
 - `dataSource`: `string` → typed enum (23 values)
 - `eventType`: `string` → typed enum (6 values)
 - V2 methods require `dimension` parameter (breaking signature change)
 
 #### Resource Sharing
+
 - Removed: `status_message` field from all recipient response types
 
 #### Schema Validation
+
 - Consolidated `SchemaCreateResponse`, `SchemaListResponse`, `SchemaEditResponse`, `SchemaGetResponse` → `PublicSchema`
 - Renamed: `SchemaListResponsesV4PagePaginationArray` → `PublicSchemasV4PagePaginationArray`
 
 #### Spectrum
+
 - Renamed union members: `AppListResponse.UnionMember0` → `SpectrumConfigAppConfig`
 - Renamed union members: `AppListResponse.UnionMember1` → `SpectrumConfigPaygoAppConfig`
 
 #### Workers
+
 - Removed: `WorkersBindingKindTailConsumer` type (all occurrences)
 - Renamed: `ScriptsSinglePage` → `ScriptListResponsesSinglePage`
 - Removed: `DeploymentsSinglePage`
 
 #### Zero-Trust DLP
+
 - `datasets.create()`, `update()`, `get()` return types changed
 - `PredefinedGetResponse` union members renamed to `UnionMember0-5`
 
 #### Zero-Trust Tunnels
+
 - Removed: `CloudflaredCreateResponse`, `CloudflaredListResponse`, `CloudflaredDeleteResponse`, `CloudflaredEditResponse`, `CloudflaredGetResponse`
 - Removed: `CloudflaredListResponsesV4PagePaginationArray`
 
@@ -120,25 +138,30 @@ All record type interfaces renamed from `*Record` to short names:
 ### Features
 
 #### Abuse Reports (`client.abuseReports`)
+
 - **Reports**: `create`, `list`, `get`
 - **Mitigations**: sub-resource for abuse mitigations
 
 #### AI Search (`client.aisearch`)
+
 - **Instances**: `create`, `update`, `list`, `delete`, `read`, `stats`
 - **Items**: `list`, `get`
 - **Jobs**: `create`, `list`, `get`, `logs`
 - **Tokens**: `create`, `update`, `list`, `delete`, `read`
 
 #### Connectivity (`client.connectivity`)
+
 - **Directory Services**: `create`, `update`, `list`, `delete`, `get`
 - Supports IPv4, IPv6, dual-stack, and hostname configurations
 
 #### Organizations (`client.organizations`)
+
 - **Organizations**: `create`, `update`, `list`, `delete`, `get`
 - **OrganizationProfile**: `update`, `get`
 - Hierarchical organization support with parent/child relationships
 
 #### R2 Data Catalog (`client.r2DataCatalog`)
+
 - **Catalog**: `list`, `enable`, `disable`, `get`
 - **Credentials**: `create`
 - **MaintenanceConfigs**: `update`, `get`
@@ -147,6 +170,7 @@ All record type interfaces renamed from `*Record` to short names:
 - Apache Iceberg integration
 
 #### Realtime Kit (`client.realtimeKit`)
+
 - **Apps**: `get`, `post`
 - **Meetings**: `create`, `get`, participant management
 - **Livestreams**: 10+ methods for streaming
@@ -157,52 +181,66 @@ All record type interfaces renamed from `*Record` to short names:
 - **Analytics**: organization analytics
 
 #### Token Validation (`client.tokenValidation`)
+
 - **Configuration**: `create`, `list`, `delete`, `edit`, `get`
 - **Credentials**: `update`
 - **Rules**: `create`, `list`, `delete`, `bulkCreate`, `bulkEdit`, `edit`, `get`
 - JWT validation with RS256/384/512, PS256/384/512, ES256, ES384
 
 #### Alerting Silences (`client.alerting.silences`)
+
 - `create`, `update`, `list`, `delete`, `get`
 
 #### IAM SSO (`client.iam.sso`)
+
 - `create`, `update`, `list`, `delete`, `get`, `beginVerification`
 
 #### Pipelines v1 (`client.pipelines`)
+
 - **Sinks**: `create`, `list`, `delete`, `get`
 - **Streams**: `create`, `update`, `list`, `delete`, `get`
 
 #### Zero-Trust AI Controls / MCP (`client.zeroTrust.access.aiControls.mcp`)
+
 - **Portals**: `create`, `update`, `list`, `delete`, `read`
 - **Servers**: `create`, `update`, `list`, `delete`, `read`, `sync`
 
 #### Accounts
+
 - `managed_by` field with `parent_org_id`, `parent_org_name`
 
 #### Addressing LOA Documents
+
 - `auto_generated` field on `LOADocumentCreateResponse`
 
 #### Addressing Prefixes
+
 - `delegate_loa_creation`, `irr_validation_state`, `ownership_validation_state`, `ownership_validation_token`, `rpki_validation_state`
 
 #### AI
+
 - Added `toMarkdown.supported()` method to get all supported conversion formats
 
 #### AI Gateway
+
 - `zdr` field added to all responses and params
 
 #### Alerting
+
 - New alert type: `abuse_report_alert`
 - `type` field added to PolicyFilter
 
 #### Browser Rendering
+
 - `ContentCreateParams`: refined to discriminated union (`Variant0 | Variant1`)
 - Split into URL-based and HTML-based parameter variants for better type safety
 
 #### Client Certificates
+
 - `reactivate` parameter in edit
 
 #### CloudforceOne
+
 - `ThreatEventCreateParams.indicatorType`: required → optional
 - `hasChildren` field added to all threat event response types
 - `datasetIds` query parameter on `AttackerListParams`, `CategoryListParams`, `TargetIndustryListParams`
@@ -213,56 +251,69 @@ All record type interfaces renamed from `*Record` to short names:
 - `createdAt`, `datasetId` fields on `ThreatEventEditParams`
 
 #### Content Scanning
+
 - Added `create()`, `update()`, `get()` methods
 
 #### Custom Pages
+
 - New page types: `basic_challenge`, `under_attack`, `waf_challenge`
 
 #### D1
+
 - `served_by_colo` - colo that handled query
 - `jurisdiction` - `'eu' | 'fedramp'`
 - **Time Travel** (`client.d1.database.timeTravel`): `getBookmark()`, `restore()` - point-in-time recovery
 
 #### Email Security
+
 - New fields on `InvestigateListResponse`/`InvestigateGetResponse`: `envelope_from`, `envelope_to`, `postfix_id_outbound`, `replyto`
 - New detection classification: `'outbound_ndr'`
 - Enhanced `Finding` interface with `attachment`, `detection`, `field`, `portion`, `reason`, `score`
 - Added `cursor` query parameter to `InvestigateListParams`
 
 #### Gateway Lists
+
 - New list types: `CATEGORY`, `LOCATION`, `DEVICE`
 
 #### Intel
+
 - New issue type: `'configuration_suggestion'`
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Leaked Credential Checks
+
 - Added `detections.get()` method
 
 #### Logpush
+
 - New datasets: `dex_application_tests`, `dex_device_state_events`, `ipsec_logs`, `warp_config_changes`, `warp_toggle_changes`
 
 #### Load Balancers
+
 - `Monitor.port`: `number` → `number | null`
 - `Pool.load_shedding`: `LoadShedding` → `LoadShedding | null`
 - `Pool.origin_steering`: `OriginSteering` → `OriginSteering | null`
 
 #### Magic Transit
+
 - `license_key` field on connectors
 - `provision_license` parameter for auto-provisioning
 - IPSec: `custom_remote_identities` with FQDN support
 - Snapshots: Bond interface, `probed_mtu` field
 
 #### Pages
+
 - New response types: `ProjectCreateResponse`, `ProjectListResponse`, `ProjectEditResponse`, `ProjectGetResponse`
 - Deployment methods return specific response types instead of generic `Deployment`
 
 #### Queues
+
 - Added `subscriptions.get()` method
 - Enhanced `SubscriptionGetResponse` with typed event source interfaces
 - New event source types: Images, KV, R2, Vectorize, Workers AI, Workers Builds, Workflows
 
 #### R2
+
 - Sippy: new provider `s3` (S3-compatible endpoints)
 - Sippy: `bucketUrl` field for S3-compatible sources
 - Super Slurper: `keys` field on source response schemas (specify specific keys to migrate)
@@ -270,32 +321,41 @@ All record type interfaces renamed from `*Record` to short names:
 - Super Slurper: `region` field on S3 source params
 
 #### Radar
+
 - Added `geolocations.list()`, `geolocations.get()` methods
 - Added V2 dimension-based methods (`summaryV2`, `timeseriesGroupsV2`) to radar sub-resources
 
 #### Resource Sharing
+
 - Added `terminal` boolean field to Resource Error interfaces
 
 #### Rules
+
 - Added `id` field to `ItemDeleteParams.Item`
 
 #### Rulesets
+
 - New buffering fields on `SetConfigRule`: `request_body_buffering`, `response_body_buffering`
 
 #### Secrets Store
+
 - New scopes: `'dex'`, `'access'` (in addition to `'workers'`, `'ai_gateway'`)
 
 #### SSL Certificate Packs
+
 - Response types now proper interfaces (was `unknown`)
 - Fields now required: `id`, `certificates`, `hosts`, `status`, `type`
 
 #### Security Center
+
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Shared Types
+
 - Added: `CloudflareTunnelsV4PagePaginationArray` pagination class
 
 #### Workers
+
 - Added `subdomains.delete()` method
 - `Worker.references` - track external dependencies (domains, Durable Objects, queues)
 - `Worker.startup_time_ms` - startup timing
@@ -306,36 +366,44 @@ All record type interfaces renamed from `*Record` to short names:
 - Telemetry: `traces` field, `$containers` event info, `durableObjectId`, `transactionName`, `abr_level` fields
 
 #### Workers for Platforms
+
 - `ScriptUpdateResponse`: new fields `entry_point`, `observability`, `tag`, `tags`
 - `placement` field now union of 4 variants (smart mode, region, hostname, host)
 - `tags`, `tail_consumers` now nullable
 - `TagUpdateParams.body` now accepts `null`
 
 #### Workflows
+
 - `instance_retention`: `unknown` → typed `InstanceRetention` interface with `error_retention`, `success_retention`
 - New status option: `'restart'` added to `StatusEditParams.status`
 
 #### Zero-Trust Devices
+
 - External emergency disconnect settings (4 new fields)
 - `antivirus` device posture check type
 - `os_version_extra` documentation improvements
 
 #### Zones
+
 - New response types: `SubscriptionCreateResponse`, `SubscriptionUpdateResponse`, `SubscriptionGetResponse`
 
 #### Zero-Trust Access Applications
+
 - New `ApplicationType` values: `'mcp'`, `'mcp_portal'`, `'proxy_endpoint'`
 - New destination type: `ViaMcpServerPortalDestination` for MCP server access
 
 #### Zero-Trust Gateway
+
 - Added `rules.listTenant()` method
 
 #### Zero-Trust Gateway - Proxy Endpoints
+
 - `ProxyEndpoint`: interface → discriminated union (`ZeroTrustGatewayProxyEndpointIP | ZeroTrustGatewayProxyEndpointIdentity`)
 - `ProxyEndpointCreateParams`: interface → union type
 - Added `kind` field: `'ip' | 'identity'`
 
 #### Zero-Trust Tunnels
+
 - `WARPConnector*Response`: union type → interface
 
 ---
@@ -371,4 +439,4 @@ All record type interfaces renamed from `*Record` to short names:
 - Added deprecation notices with migration paths
 - **api_gateway:** deprecate API Shield Schema Validation resources ([8a4b20f](https://github.com/cloudflare/cloudflare-typescript/commit/8a4b20f7a572422f74179fbdb4f1c4fb555e3e40))
 - Improved JSDoc examples across all resources
-- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
\ No newline at end of file
+- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
diff --git a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
index 4637fe2ecd6fe2e..7b6922947ee7f2c 100644
--- a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
@@ -98,46 +98,57 @@ will help you understand any down or upstream issues it may cause to your enviro
 ### New Endpoints (Existing Resources)
 
 #### `acm.totaltls`
+
 - `edit()`
 - `update()`
 
 #### `cloudforceone.threatevents`
+
 - `list()`
 
 #### `contentscanning`
+
 - `create()`
 - `get()`
 - `update()`
 
 #### `dns.records`
+
 - `scan_list()`
 - `scan_review()`
 - `scan_trigger()`
 
 #### `intel.indicatorfeeds`
+
 - `create()`
 - `delete()`
 - `list()`
 
 #### `leakedcredentialchecks.detections`
+
 - `get()`
 
 #### `queues.consumers`
+
 - `list()`
 
 #### `radar.ai`
+
 - `summary()`
 - `timeseries()`
 - `timeseries_groups()`
 
 #### `radar.bgp`
+
 - `changes()`
 - `snapshot()`
 
 #### `workers.subdomains`
+
 - `delete()`
 
 #### `zerotrust.networks`
+
 - `create()`
 - `delete()`
 - `edit()`
@@ -164,4 +175,4 @@ will help you understand any down or upstream issues it may cause to your enviro
 - **Discriminated unions**: Correctly handle nested discriminated unions in response parsing
 - **Extra field types**: Parse extra field types correctly
 - **Empty metadata**: Ignore empty metadata fields during parsing
-- **Singularization rules**: Update resource name singularization rules for better consistency
\ No newline at end of file
+- **Singularization rules**: Update resource name singularization rules for better consistency
diff --git a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
index 80b92a2e38719b4..01d745a7853300f 100644
--- a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
+++ b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
@@ -1,16 +1,16 @@
-
 ---
 title: New APIs for Brand Protection setup
 description: You can now use the Brand Protection API endpoints to manage your Brand Protection queries
 date: 2025-07-18
 ---
- 
+
 The Brand Protection API is now available, allowing users to create new queries and delete existing ones, fetch matches and more!
- 
+
 What you can do:
-- **create new string or logo query** 
-- **delete string or logo queries** 
-- **download matches for both logo and string queries** 
-- **read matches for both logo and string queries** 
+
+- **create new string or logo query**
+- **delete string or logo queries**
+- **download matches for both logo and string queries**
+- **read matches for both logo and string queries**
 
 Ready to start? Check out the [Brand Protection API](/api/resources/brand_protection/) in our documentation.
diff --git a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
index a8da24443aa2244..58288565e961039 100644
--- a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
+++ b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
@@ -4,7 +4,7 @@ description: The Requests for Information (RFI) dashboard now shows the number o
 date: 2025-10-27
 ---
 
-The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted. 
+The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted.
 
 ![Cloudforce One RFI tokens](~/assets/images/changelog/security-center/2025-10-24RFITokens.png)
 
diff --git a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
index 5c14e85f93430d3..07257c943d54312 100644
--- a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
+++ b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
@@ -1,9 +1,9 @@
 ---
 title: Report logo misuse to Cloudflare directly from the Brand Protection dashboard
-description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network 
+description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network
 date: 2025-10-31
 ---
 
 The Brand Protection logo query dashboard now allows you to use the **Report to Cloudflare** button to submit an Abuse report directly from the Brand Protection logo queries dashboard. While you could previously report new domains that were impersonating your brand before, now you can do the same for websites found to be using your logo without your permission. The abuse reports will be prefilled and you will only need to validate a few fields before you can click the submit button, after which our team process your request.
 
-Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/). 
+Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/).
diff --git a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
index 9f9d5dd72cde73f..fcd53972aec849f 100644
--- a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
+++ b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
@@ -4,7 +4,7 @@ description: Threat events users can now access threat insights curated by our t
 date: 2025-11-21
 ---
 
-The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity. 
-Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.  
+The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity.
+Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.
 
-For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events). 
+For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events).
diff --git a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
index 1dad1d621eb3f74..f6b64dc1ba68722 100644
--- a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
+++ b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
@@ -9,13 +9,13 @@ This update streamlines how security analysts can share findings with stakeholde
 
 **Key Benefits:**
 
-* Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
-* Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
+- Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
+- Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
 
 **What’s new:**
 
-* **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
-* **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
+- **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
+- **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
 
 To get started with the URL Scanner and explore our reporting capabilities, visit the [URL Scanner API documentation](https://developers.cloudflare.com/api/resources/url_scanner/).
 
diff --git a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
index e0dd22e2c84e189..eff63f778930ece 100644
--- a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
+++ b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
@@ -3,6 +3,7 @@ title: Cloudforce One Threat events graphs are now visible in the dashboard
 description: Trace attack flows with Sankey diagrams and analyze dataset distribution over time
 date: 2026-02-19
 ---
+
 We have introduced dynamic visualizations to the Threat Events dashboard to help you better understand the threat landscape and identify emerging patterns at a glance.
 
 What's new:
diff --git a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
index 5260cc6ad7bf605..4a28f773e0eeeac 100644
--- a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
+++ b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
@@ -9,7 +9,8 @@ date: 2026-02-23
 ## Why this matters
 
 Threat intelligence is most effective when it is personalized. Previously, analysts had to manually re-apply complex filters (like combining specific industry datasets with geographic origins) every time they logged in. This update provides material value by:
-* Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
-* Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
+
+- Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
+- Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
 
 Cloudforce One subscribers can start saving their custom views now in [Application Security > Threat Intelligence > Threat Events](https://dash.cloudflare.com/?to=/:account/security-center/threat-intelligence/threat-events).
diff --git a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
index 14417dfa3c757dd..14c2ac824145ccc 100644
--- a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
+++ b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
@@ -3,25 +3,25 @@ title: Real-time alerts and daily digests for Threat Events
 description: You can now subscribe to automated notifications for your saved views in Threat Events
 date: 2026-04-08
 ---
- 
+
 You can now automate your threat monitoring by setting up custom alerts in your saved views. Instead of manually checking the dashboard for updates, you can subscribe to notifications that trigger whenever new data matches your specific filter sets, like new activity associated to a particular threat actor or spikes in activity within your industry.
- 
+
 ### Stay ahead of emerging threats
- 
+
 By linking your saved views to the Cloudflare Notifications Center, you can ensure the right information reaches your team at the right time.
- 
+
 - **Immediate Alerts**: receive real-time notifications the moment a critical event is detected that matches your saved criteria. This is essential for high-priority monitoring, such as tracking active campaigns from specific APT groups.
- 
+
 - **Daily Digests**: opt for a summarized report delivered once a day. This is ideal for maintaining situational awareness of broader trends, like regional activity shifts or industry-wide threat landscapes, without cluttering your inbox.
- 
+
 ![Threat Events notifications](~/assets/images/changelog/security-center/threat-events-notifications.png)
- 
+
 ### How to get started
- 
+
 To set up an alert, go to **Application Security** > **Threat Intelligence** > **Threat Events**. From there:
- 
+
 1. Choose your datasets and apply your desired filters and select **Save View** (or select an existing one).
 2. Open the **Manage Saved Views** menu.
 3. Select **Add Alert** next to your chosen view to configure your notification preferences in the Cloudflare dashboard.
- 
+
 For more technical details on configuring notifications, refer to the [Threat Events documentation](/security-center/cloudforce-one/).
diff --git a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
index 6ab0a8267691e14..51425d471206a97 100644
--- a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
+++ b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
@@ -7,6 +7,7 @@ date: 2026-05-07
 You can now export your Requests for Information (RFI) history to a **CSV document** and customize your dashboard view by choosing how many RFI records to load per page.
 
 ### Why this matters
+
 These quality-of-life updates focus on data portability and dashboard performance, allowing power users to manage high volumes of requests more efficiently:
 
 - The new **CSV export** allows you to move RFI data into external tools for custom reporting, internal auditing, or cross-referencing with other security projects without manual data entry
diff --git a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
index 7728d2033ec5df9..3045c86a164b8bf 100644
--- a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
+++ b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
@@ -9,18 +9,19 @@ We’ve added a new **Agent Readiness** tab to URL Scanner reports accessible vi
 The Internet is shifting from a human-read web to a machine-read web. AI agents now browse, interact with, and even perform transactions on websites. If a site isn't "agent-ready," these bots may consume excessive bandwidth, fail to find critical information, or be unable to navigate your services efficiently.
 
 This update provides material value by breaking down readiness into six actionable categories:
-- **Basic Web Presence** 
+
+- **Basic Web Presence**
 - **Discoverability**
-- **Content Accessibility** 
-- **Bot Access Control** 
-- **Protocol Discovery** 
-- **Commerce** 
+- **Content Accessibility**
+- **Bot Access Control**
+- **Protocol Discovery**
+- **Commerce**
 
 ## Accessing the report
 
-You can view these scores for any scanned URL directly in the dashboard or via our API. 
+You can view these scores for any scanned URL directly in the dashboard or via our API.
 
-* **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
-* **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
+- **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
+- **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
 
 To learn more about the methodology behind these scores, refer to the [blogpost](https://blog.cloudflare.com/agent-readiness/).
diff --git a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
index f32ba78cbd7337b..632429a872e1c7c 100644
--- a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
+++ b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
@@ -12,7 +12,7 @@ Introducing enhanced archiving capabilities for security action items within the
 
 ### Why this matters
 
-Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored. 
+Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored.
 
 With these new archiving options—**False Positive**, **Accept Risk**, and **Other**—you can now suppress items indefinitely with required rationale text for risk-based decisions. This ensures that your team remains focused on critical, actionable vulnerabilities while preserving institutional knowledge for audits.
 
@@ -36,4 +36,5 @@ To review the history and rationale of a specific archived issue at the account
 ```bash
 curl "[https://api.cloudflare.com/client/v4/accounts/](https://api.cloudflare.com/client/v4/accounts/){account_id}/insights/{insight_id}/audit-log" \
      -H "Authorization: Bearer <API_TOKEN>" \
-     -H "Content-Type: application/json"
\ No newline at end of file
+     -H "Content-Type: application/json"
+```
diff --git a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
index d1f9b23ef4c3974..52e1ce7305a8c77 100644
--- a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
+++ b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
@@ -7,7 +7,7 @@ description: Cloudflare Secrets Store is now integrated with AI Gateway, allowin
 date: 2025-08-25T11:00:00Z
 ---
 
-import { Card, Render, Details } from "~/components"
+import { Card, Render, Details } from "~/components";
 
 Cloudflare Secrets Store is now integrated with AI Gateway, allowing you to store, manage, and deploy your AI provider keys in a secure and seamless configuration through [Bring Your Own Key](https://developers.cloudflare.com/ai-gateway/configuration/bring-your-own-keys/). Instead of passing your AI provider keys directly in every request header, you can centrally manage each key with Secrets Store and deploy in your gateway configuration using only a reference, rather than passing the value in plain text.
 
@@ -25,24 +25,24 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthro
  --header 'anthropic-version: 2023-06-01' \
  --header 'Content-Type: application/json' \
  --data  '{"model": "claude-3-opus-20240229", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}'
- ```
+```
 
- Or, using Javascript:
+Or, using Javascript:
 
- ```
- import Anthropic from '@anthropic-ai/sdk';
+```
+import Anthropic from '@anthropic-ai/sdk';
 
 
 const anthropic = new Anthropic({
-  apiKey: "ANTHROPIC_KEY_1",
-  baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
+ apiKey: "ANTHROPIC_KEY_1",
+ baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
 });
 
 
 const message = await anthropic.messages.create({
-  model: 'claude-3-opus-20240229',
-  messages: [{role: "user", content: "What is Cloudflare?"}],
-  max_tokens: 1024
+ model: 'claude-3-opus-20240229',
+ messages: [{role: "user", content: "What is Cloudflare?"}],
+ max_tokens: 1024
 });
 ```
 
diff --git a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
index c7b16b6e1a681b2..d6f34e72b9e8ed7 100644
--- a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
+++ b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
@@ -10,7 +10,7 @@ an M4A file to use in downstream workflows like [AI inference](/workers-ai/), co
 
 For example,
 
-``` text title="Example URL"
+```text title="Example URL"
 https://example.com/cdn-cgi/media/<OPTIONS>/<SOURCE-VIDEO>
 https://example.com/cdn-cgi/media/mode=audio,time=3s,duration=60s/<input video with diction>
 ```
diff --git a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
index a2a4201f278c795..817c2e0c7c81e19 100644
--- a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
+++ b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
@@ -3,6 +3,7 @@ title: Redesigned Support Portal for faster, personalized help
 description: A streamlined Support Portal featuring AI-driven ticket routing and a simplified interface for all Cloudflare customers.
 date: 2026-04-07
 ---
+
 ## Redesigned "Get Help" Portal for faster, personalized help
 
 Cloudflare has officially launched a redesigned "Get Help" Support Portal to eliminate friction and get you to a resolution faster. Previously, navigating support meant clicking through multiple tiles, categorizing your own technical issues across 50+ conditional fields, and translating your problem into Cloudflare's internal taxonomy.
diff --git a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
index 0fe7d0c34250fb2..906dc74af3ffc2b 100644
--- a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
+++ b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
@@ -12,7 +12,7 @@ This change ensures that when you need help, you spend less time navigating the
 
 ### What changed?
 
-* **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
-* **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
+- **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
+- **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
 
 To learn more about the resources available to you, refer to the [Cloudflare Support documentation](https://developers.cloudflare.com/support/contacting-cloudflare-support/).
diff --git a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
index d128e3253f5acb2..70650f4bcd04ef7 100644
--- a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
+++ b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
@@ -5,6 +5,7 @@ products:
   - fundamentals
 date: 2025-02-03
 ---
+
 ![Screenshot of Terraform defining a Zone](~/assets/images/changelog/2024-02-03-terraform-v5-screenshot.png)
 
 Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure.
@@ -12,5 +13,6 @@ Cloudflare's v5 Terraform Provider is now generally available. With this release
 The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach.
 
 For more info
-* [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-* [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
+
+- [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
+- [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
index d8df928767923fd..692eda375b40aaa 100644
--- a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
@@ -11,12 +11,12 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 ### Changes
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
-	- `cloudflare_zero_trust_gateway_policy`
-	- `cloudflare_zero_trust_access_application`
-	- `cloudflare_zero_trust_tunnel_cloudflared_route`
-	- `cloudflare_zone_setting`
-	- `cloudflare_ruleset`
-	- `cloudflare_page_rule`
+  - `cloudflare_zero_trust_gateway_policy`
+  - `cloudflare_zero_trust_access_application`
+  - `cloudflare_zero_trust_tunnel_cloudflared_route`
+  - `cloudflare_zone_setting`
+  - `cloudflare_ruleset`
+  - `cloudflare_page_rule`
 - Zone settings can be re-applied without client errors
 - Page rules conversion errors are fixed
 - Failure to apply changes to `cloudflare_zero_trust_tunnel_cloudflared_route`
@@ -25,6 +25,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.5.0) in GitHub.
 
 ### Issues Closed
+
 - [#5304: Importing cloudflare_zero_trust_gateway_policy invalid attribute filter value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5304)
 - [#5303: cloudflare_page_rule import does not set values for all of the fields in terraform state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5303)
 - [#5178: cloudflare_page_rule Page rule creation with redirect fails](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5178)
diff --git a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
index 88d70bea95929e7..ce7ec83f1e68809 100644
--- a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
@@ -17,7 +17,7 @@ eye on this changelog for more information about upcoming releases.
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
   - `cloudflare_zero_trust_access_identity_provider`
-	- `cloudflare_zone`
+  - `cloudflare_zone`
 - `cloudflare_page_rules` runtime panic when setting `cache_level` to `cache_ttl_by_status`
 - Failure to serialize requests in `cloudflare_zero_trust_tunnel_cloudflared_config`
 - Undocumented field 'priority' on `zone_lockdown` resource
@@ -33,6 +33,7 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.6.0) in GitHub.
 
 ### Issues Closed
+
 - [#5098: 500 Server Error on updating 'zero_trust_tunnel_cloudflared_virtual_network' Terraform resource](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5098)
 - [#5148: cloudflare_user_agent_blocking_rule doesn’t actually support user agents](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5148)
 - [#5472: cloudflare_zone showing changes in plan after following upgrade steps](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5472)
diff --git a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
index aaabc9c53996ef2..e637557cb1938b2 100644
--- a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
@@ -11,6 +11,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases.
 
 ### Changes
+
 - Addressed permanent diff bug on Cloudflare Tunnel config
 - State is now saved correctly for Zero Trust Access applications
 - Exact match is now working as expected within `data.cloudflare_zero_trust_access_applications`
@@ -24,6 +25,7 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.7.0) in GitHub.
 
 ### Issues Closed
+
 - [#5563: cloudflare_logpull_retention is missing import](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5563)
 - [#5608: cloudflare_zero_trust_access_policy in 5.5.0 provider gives error upon apply unexpected new value: .app_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1)](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5608)
 - [#5612: data.cloudflare_zero_trust_access_applications does not exact match](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5612)
@@ -32,7 +34,6 @@ For a more detailed look at all of the changes, see the
 - [#5565: Running Terraform with the cloudflare_zero_trust_access_policy resource results in updates on every apply, even when no changes are made - breaks idempotency](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5565)
 - [#5529: cloudflare_zero_trust_access_application: self hosted applications with private ips require public domain ](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5529)
 
-
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
index 280ce29c2aebb63..ce5660cdb8f4833 100644
--- a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
@@ -11,6 +11,7 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_custom_pages`
   - `cloudflare_page_rule`
@@ -18,13 +19,14 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
   - `cloudflare_argo_tiered_caching`
 - Addressed chronic drift issues in `cloudflare_logpush_job`, `cloudflare_zero_trust_dns_location`, `cloudflare_ruleset` & `cloudflare_api_token`
 - `cloudflare_zone_subscription` returns expected values `rate_plan.id` from former versions
-- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate 
-- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy` 
+- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate
+- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy`
 - Other bug fixes
 
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.2) in GitHub.
 
 ### Issues Closed
+
 - [#5666: cloudflare_ruleset example lists id which is a read-only field](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5666)
 - [#5578: cloudflare_logpush_job plan always suggests changes](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5578)
 - [#5552: 5.4.0: Since provider update, existing cloudflare_list_item would be recreated "created" state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5552)
diff --git a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
index 32201f4ca38d484..62ed2ed4b454317 100644
--- a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
@@ -6,13 +6,14 @@ products:
 date: 2025-08-15
 ---
 
-Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. 
+Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability.
 
-One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests. 
+One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests.
 
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_argo_smart_routing`
   - `cloudflare_bot_management`
@@ -40,6 +41,7 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 For a more detailed look at all of the changes, refer to the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.4) in GitHub.
 
 ### Issues Closed
+
 - [#5017: 'Uncaught Error: No such module' using cloudflare_snippets](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5017)
 - [#5701: cloudflare_workers_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5701)
 - [#5640: cloudflare_argo_smart_routing importing doesn't read the actual value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5640)
diff --git a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
index f25c1bc414c9f19..e89ea7fd1f359cd 100644
--- a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
@@ -13,6 +13,7 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 This release includes a new resource, `cloudflare_snippet`, which replaces `cloudflare_snippets`. `cloudflare_snippet` is now considered deprecated but can still be used. Please utilize `cloudflare_snippet` as soon as possible.
 
 ### Changes
+
 - Resources stabilized:
   - `cloudflare_zone_setting`
   - `cloudflare_worker_script`
@@ -28,6 +29,7 @@ For a more detailed look at all of the changes, refer to the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.9.0) in GitHub.
 
 ### Issues Closed
+
 - [#5921: In cloudflare_ruleset removing an existing rule causes recreation of later rules](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5921)
 - [#5904: cloudflare_zero_trust_access_application is not idempotent](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5904)
 - [#5898: (cloudflare_workers_script) Durable Object migrations not applied](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5898)
@@ -47,7 +49,6 @@ For a more detailed look at all of the changes, refer to the
 - [#5727: cloudflare_ruleset http_request_cache_settings bypass mismatch between dashboard and terraform](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5727)
 - [#5700: cloudflare_account_member invalid type 'string' for field 'roles'](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5700)
 
-
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new issue if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
index 3886135203e9e03..ac788bb9e06272c 100644
--- a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
@@ -6,55 +6,56 @@ products:
 date: 2025-11-20
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
-This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more. 
+This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more.
 
 ### Breaking Change
+
 Please be aware that there are breaking changes for the `cloudflare_api_token` and `cloudflare_account_token` resources. These changes eliminate configuration drift caused by policy ordering differences in the Cloudflare API.
 
 For more specific information about the changes or the actions required, please see the [detailed Repository changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.13.0).
 
-
 ### Features
 
-* **New resources and data sources added** 
-	* cloudflare_connectivity_directory
-	* cloudflare_sso_connector
-	* cloudflare_universal_ssl_setting
-* **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
-* **docs:** make docs explicit when a resource does not have import support 
-* **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
-* **worker_version:** add content_base64 support
-* **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
-* **workers_script_subdomains:** add import support  ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
-* **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
-* **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
-
+- **New resources and data sources added**
+  - cloudflare_connectivity_directory
+  - cloudflare_sso_connector
+  - cloudflare_universal_ssl_setting
+- **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
+- **docs:** make docs explicit when a resource does not have import support
+- **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
+- **worker_version:** add content_base64 support
+- **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
+- **workers_script_subdomains:** add import support ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
+- **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
+- **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
 
 ### Bug Fixes
 
-* **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
-* allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
-* **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
-* **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
-* **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
-* **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
-* **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181)) 
-* **workers_kv:** multipart request  ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
-* **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386)) 
-* **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383)) 
-* **workers_script:** allow config.run_worker_first to accept list input 
-* **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
-* **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
-* **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
-* **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
+- **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
+- allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
+- **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
+- **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
+- **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
+- **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
+- **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181))
+- **workers_kv:** multipart request ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
+- **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386))
+- **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383))
+- **workers_script:** allow config.run_worker_first to accept list input
+- **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
+- **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
+- **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
+- **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
 
 ### Upgrading
+
 We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized. We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more info
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
index a33c746b8592808..9cff570347406b9 100644
--- a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
@@ -6,7 +6,7 @@ products:
 date: 2025-12-05
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
@@ -14,7 +14,7 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Deprecation notice
 
-Resource affected: `api_shield_discovery_operation` 
+Resource affected: `api_shield_discovery_operation`
 
 Cloudflare continuously discovers and updates API endpoints and web assets of your web applications. To improve the maintainability of these dynamic resources, we are working on reducing the need to actively engage with discovered operations.
 
@@ -26,21 +26,23 @@ The corresponding public API endpoint of [discovered operations](https://develop
 
 ### Bug fixes
 
-- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488)) 
+- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488))
 - **pages_project**: Ensures non empty refresh plans ([#6515](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6515))
-- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512)) 
-- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521)) 
-- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489)) 
-- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504)) 
-- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503)) 
+- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512))
+- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521))
+- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489))
+- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504))
+- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503))
 - **zero_trust_dlp_custom_profile**: Adds sweepers for `dlp_custom_profile`
 - **zone_subscription|account_subscription**: Adds `partners_ent` as valid enum for `rate_plan.id` ([#6505](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6505))
-- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487)) 
-- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510)) 
+- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487))
+- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510))
 
 ### Upgrade to newer version
+
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
index 017d74955cda99c..6c0f1f7bf13a718 100644
--- a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
@@ -14,29 +14,31 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-* **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
-* **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
-* **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
-* **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-* **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
-* **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+- **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
+- **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
+- **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
+- **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+- **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+- **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
 
 ### Bug fixes
 
-* **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
-* **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
-* **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
-* **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
-* **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
-* **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
-* **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
+- **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
+- **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
+- **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
+- **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
+- **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
+- **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
+- **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
 
 ### Upgrade to newer version
+
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](/terraform/)
\ No newline at end of file
+- [Documentation on using Terraform with Cloudflare](/terraform/)
diff --git a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
index 00374611ed967d8..fc887b15fcfba63 100644
--- a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
@@ -16,41 +16,42 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-* **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
-* **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
-* **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
-* **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
-* **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
-* **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
-* **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
-* **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
-* **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
-* **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
-* **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
-* **ruleset:** add request body buffering support
-* **ruleset:** enhance ruleset data source with additional configuration options
-* **workers_script:** add observability logs attributes to list data source model
-* **workers_script:** enhance list data source schema with additional configuration options
+- **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
+- **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
+- **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
+- **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
+- **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
+- **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
+- **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
+- **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
+- **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
+- **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
+- **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
+- **ruleset:** add request body buffering support
+- **ruleset:** enhance ruleset data source with additional configuration options
+- **workers_script:** add observability logs attributes to list data source model
+- **workers_script:** enhance list data source schema with additional configuration options
 
 ### Bug Fixes
 
-* **account_member**: fix resource importability issues
-* **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
-* **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
-* **workers_kv:** handle special characters correctly in URL encoding
+- **account_member**: fix resource importability issues
+- **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
+- **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
+- **workers_kv:** handle special characters correctly in URL encoding
 
 ### Documentation
 
-* **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
-* **api_shield:** add resource-level description for API Shield management of auth ID characteristics
-* **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
-* **api_shield:** specify JSONPath expression format for JWT claim locations
-* **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
-* **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
-* **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
-* **hyperdrive_config:** update port description to clarify defaults for different database types
+- **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
+- **api_shield:** add resource-level description for API Shield management of auth ID characteristics
+- **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
+- **api_shield:** specify JSONPath expression format for JWT claim locations
+- **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
+- **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
+- **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
+- **hyperdrive_config:** update port description to clarify defaults for different database types
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
index d8dedb4bea9275a..76242fbae5f2ce1 100644
--- a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
@@ -28,60 +28,61 @@ help us build products that reflect your needs.
 
 ### Features
 
-* **ai_search_instance:** add data source for querying AI Search instances
-* **ai_search_token:** add data source for querying AI Search tokens
-* **account:** add support for tenant unit management with new `unit` field
-* **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
-* **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
-* **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
-* **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
-* **workers_kv:** add `value` field to data source to retrieve KV values directly
-* **workers_script:** add `script` field to data source to retrieve script content
-* **workers_script:** add support for `simple` rate limit binding
-* **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
-* **workers_script:** add `placement_mode` and `placement_status` computed fields
-* **zero_trust_dex_test:** add data source with filter support for finding specific tests
-* **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
+- **ai_search_instance:** add data source for querying AI Search instances
+- **ai_search_token:** add data source for querying AI Search tokens
+- **account:** add support for tenant unit management with new `unit` field
+- **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
+- **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
+- **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
+- **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
+- **workers_kv:** add `value` field to data source to retrieve KV values directly
+- **workers_script:** add `script` field to data source to retrieve script content
+- **workers_script:** add support for `simple` rate limit binding
+- **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
+- **workers_script:** add `placement_mode` and `placement_status` computed fields
+- **zero_trust_dex_test:** add data source with filter support for finding specific tests
+- **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
 
 ### Bug Fixes
 
-* **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
-* **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
-* **authenticated_origin_pulls:** handle array response and implement full lifecycle
-* **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
-* **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
-* **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
-* **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
-* **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
-* **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
-* **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
-* **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
-* **mtls_certificates:** fix resource and test
-* **pages_project:** revert build_config to computed optional
-* **stream_key:** use correct `account_id` field instead of `id` in API calls
-* **total_tls:** use upsert pattern for singleton zone setting
-* **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
-* **workers_script:** add support for placement mode/status
-* **zero_trust_access_application:** update v4 version on migration tests
-* **zero_trust_device_posture_rule:** update tests to match API
-* **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
-* **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
-* **zero_trust_organization:** fix plan issues
+- **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
+- **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
+- **authenticated_origin_pulls:** handle array response and implement full lifecycle
+- **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
+- **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
+- **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
+- **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
+- **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
+- **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
+- **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
+- **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
+- **mtls_certificates:** fix resource and test
+- **pages_project:** revert build_config to computed optional
+- **stream_key:** use correct `account_id` field instead of `id` in API calls
+- **total_tls:** use upsert pattern for singleton zone setting
+- **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
+- **workers_script:** add support for placement mode/status
+- **zero_trust_access_application:** update v4 version on migration tests
+- **zero_trust_device_posture_rule:** update tests to match API
+- **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
+- **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
+- **zero_trust_organization:** fix plan issues
 
 ### Chores
 
-* add state upgraders to 95+ resources to lay the foundation for replacing Grit
+- add state upgraders to 95+ resources to lay the foundation for replacing Grit
   (still under active development)
-* **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
-* **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
-* **dns_record:** add state migration handler for SDKv2 to Framework conversion
-* **leaked_credential_check:** add import functionality and tests
-* **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
-* **pages_project:** add state migration handlers
-* **tiered_cache:** add state migration handlers
-* **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
+- **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
+- **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
+- **dns_record:** add state migration handler for SDKv2 to Framework conversion
+- **leaked_credential_check:** add import functionality and tests
+- **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
+- **pages_project:** add state migration handlers
+- **tiered_cache:** add state migration handlers
+- **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
 
 ### For more information
+
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
index 6681382c7d1ae98..c9633450d6adb47 100644
--- a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
@@ -32,6 +32,7 @@ Terraform Provider v5.19.0 introduces 14 new resources spanning AI Gateway, Pipe
 ### V4 to V5 Migration State Upgraders
 
 State upgraders added for seamless migration from v4 to v5 for the following resources:
+
 - account
 - account_member
 - account_token
diff --git a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
index 4aa693f7bd56a44..1acd6e85a6a432f 100644
--- a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
+++ b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
@@ -6,11 +6,11 @@ products:
   - terraform
 ---
 
-We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5. 
+We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5.
 
 ## v5 is stable and ready for production
 
-**Terraform Provider v5 is stable and actively receiving updates.**  We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
+**Terraform Provider v5 is stable and actively receiving updates.** We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
 
 Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool we're providing to the community — ensuring the best possible migration experience.
 
@@ -24,7 +24,7 @@ Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool w
 - **Cross-file reference updates** – Automatically finds and updates all references to renamed resources across your entire configuration
 - **Dry-run mode** – Preview all changes before applying them to ensure safety
 
-Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest. 
+Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest.
 
 ## Supported resources
 
diff --git a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
index d669da557298f32..968781b659c1aca 100644
--- a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
+++ b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
@@ -14,7 +14,8 @@ Your real-time applications running over [Cloudflare Tunnel](/cloudflare-one/net
 This is a foundational improvement to Cloudflare Tunnel, delivered automatically to all customers. There are no settings to configure — your UDP traffic is already flowing faster and more reliably.
 
 **What’s new:**
+
 - **Faster UDP performance**: We've significantly reduced the latency for establishing new UDP sessions, making applications like private DNS much more responsive.
 - **Greater reliability for mixed traffic**: UDP packets are no longer affected by heavy TCP traffic, preventing timeouts and connection drops for your real-time services.
 
-Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
\ No newline at end of file
+Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
diff --git a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
index 4ed43b589b89d2e..e857486e0668872 100644
--- a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
+++ b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
@@ -13,22 +13,22 @@ Starting **December 1, 2025**, list endpoints for the [Cloudflare Tunnel API](/a
 No action is required if you already explicitly set `is_deleted=false` or if you only need to list active resources.
 
 This change affects the following API endpoints:
-* List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
-* List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
-* List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
-* List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
-* List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
-* List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
+
+- List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
+- List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
+- List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
+- List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
+- List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
+- List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
 
 ## What is changing?
 
 The default behavior of the `is_deleted` query parameter will be updated.
 
-| Scenario | Previous behavior (before December 1, 2025) | New behavior (from December 1, 2025) |
-| :--- | :--- | :--- |
+| Scenario                          | Previous behavior (before December 1, 2025)                                | New behavior (from December 1, 2025)                                  |
+| :-------------------------------- | :------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
 | `is_deleted` parameter is omitted | Returns **active & deleted** tunnels, routes, subnets and virtual networks | Returns **only active** tunnels, routes, subnets and virtual networks |
 
-
 ## Action required
 
 If you need to retrieve deleted (or all) resources, please update your API calls to explicitly include the `is_deleted` parameter before **December 1, 2025**.
@@ -48,9 +48,11 @@ curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/virtual_
 Following this change, retrieving a complete list of both active and deleted resources will require two separate API calls: one to get active items (by omitting the parameter or using `is_deleted=false`) and one to get deleted items (`is_deleted=true`).
 
 ## Why we’re making this change
+
 This update is based on user feedback and aims to:
-* **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
-* **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
-* **Improve performance:** For most users, the default query result will now be smaller and more relevant.
 
-To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
\ No newline at end of file
+- **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
+- **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
+- **Improve performance:** For most users, the default query result will now be smaller and more relevant.
+
+To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
diff --git a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
index 947de730982905f..bc751a65e2b32ff 100644
--- a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
+++ b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
@@ -16,6 +16,7 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 ![Hostname-based routing in Cloudflare Tunnel](~/assets/images/changelog/cloudflare-one/tunnel-hostname-routing.webp)
 
 **What’s new:**
+
 - **Hostname & Domain Routing**: Create routes for individual hostnames (e.g., `payroll.acme.local`) or entire domains (e.g., `*.acme.local`) and direct their traffic to a specific Tunnel.
 - **Simplified Zero Trust Policies**: Build resilient policies in Cloudflare Access and Gateway using stable hostnames, making it dramatically easier to apply per-resource authorization for your private applications.
 - **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
@@ -23,4 +24,4 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 
 Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) or [public hostname](/cloudflare-one/traffic-policies/egress-policies/egress-cloudflared/) route.
 
-Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
\ No newline at end of file
+Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
diff --git a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
index b4bdbe1014ee162..35c45b7766d212a 100644
--- a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
+++ b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
@@ -13,4 +13,4 @@ You can now `ping` the WARP Connector host directly on its LAN IP address immedi
 
 Starting with [version 2025.10.186.0](/changelog/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability.
 
-Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
\ No newline at end of file
+Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
diff --git a/src/content/changelog/waf/2025-07-14-waf-release.mdx b/src/content/changelog/waf/2025-07-14-waf-release.mdx
index 27ee5690579c07e..3657b790de4b853 100644
--- a/src/content/changelog/waf/2025-07-14-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-14-waf-release.mdx
@@ -13,7 +13,6 @@ This week’s vulnerability analysis highlights emerging web application threats
 - XSS – Attribute Overloading: A novel cross-site scripting technique where attackers abuse custom or non-standard HTML attributes to smuggle payloads into the DOM. These payloads evade traditional sanitization logic, especially in frameworks that loosely validate attributes or trust unknown tokens.
 - XSS – onToggle Event Abuse: Exploits the lesser-used onToggle event (triggered by elements like `<details>`) to execute arbitrary JavaScript when users interact with UI elements. This vector is often overlooked by static analyzers and can be embedded in seemingly benign components.
 
-
 **Impact**
 
 These vulnerabilities target both user-facing components and back-end databases, introducing potential vectors for credential theft, session hijacking, or full data exfiltration. The XSS variants bypass conventional filters through overlooked HTML behaviors, while the obfuscated SQLi enables attackers to stealthily probe back-end logic, making them especially difficult to detect and block.
diff --git a/src/content/changelog/waf/2025-07-21-emergency.mdx b/src/content/changelog/waf/2025-07-21-emergency.mdx
index ce9154530bc73e3..190744a1169aa10 100644
--- a/src/content/changelog/waf/2025-07-21-emergency.mdx
+++ b/src/content/changelog/waf/2025-07-21-emergency.mdx
@@ -29,30 +29,30 @@ Together, these vulnerabilities significantly weaken the security posture of on-
 			<th>Comments</th>
 		</tr>
 	</thead>
-       <tbody>
- 		<tr>
+	<tbody>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
-					<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
+				<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
 			</td>
 			<td>100817</td>
 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53770</td>
 			<td>N/A</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
- 		</tr>
- 		<tr>
+		</tr>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
- 			<td>
- 					<RuleID id="d21f327516a145bc9d1b05678de656c4" />
- 			</td>
- 			<td>100818</td>
- 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
- 			<td>N/A</td>
- 			<td>Block</td>
- 			<td>This is a New Detection</td>
+			<td>
+				<RuleID id="d21f327516a145bc9d1b05678de656c4" />
+			</td>
+			<td>100818</td>
+			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
 		</tr>
-  </tbody>
+	</tbody>
 </table>
 
-For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
\ No newline at end of file
+For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
diff --git a/src/content/changelog/waf/2025-07-28-waf-release.mdx b/src/content/changelog/waf/2025-07-28-waf-release.mdx
index 3374f46caf0c044..c04a253ad3d3a3e 100644
--- a/src/content/changelog/waf/2025-07-28-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-28-waf-release.mdx
@@ -8,7 +8,6 @@ import { RuleID } from "~/components";
 
 This week’s update spotlights several vulnerabilities across Apache Tomcat, MongoDB, and Fortinet FortiWeb. Several flaws related with a memory leak in Apache Tomcat can lead to a denial-of-service attack. Additionally, a code injection flaw in MongoDB's Mongoose library allows attackers to bypass security controls to access restricted data.
 
-
 **Key Findings**
 
 - Fortinet FortiWeb (CVE-2025-25257): An improper neutralization of special elements used in a SQL command vulnerability in Fortinet FortiWeb versions allows an unauthenticated attacker to execute unauthorized SQL code or commands.
@@ -73,7 +72,9 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="f9e01e28c5d6499cac66364b4b6a5bb1" />
 			</td>
 			<td>100815</td>
-			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
+			<td>
+				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -84,10 +85,12 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="700d4fcc7b1f481a80cbeee5688f8e79" />
 			</td>
 			<td>100816</td>
-			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
+			<td>
+				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-08-04-waf-release.mdx b/src/content/changelog/waf/2025-08-04-waf-release.mdx
index f8f5bc852842740..b0e648fc90a3a62 100644
--- a/src/content/changelog/waf/2025-08-04-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-04-waf-release.mdx
@@ -35,105 +35,110 @@ The Grafana cross-site scripting (XSS) flaw can be used to hijack authenticated
 Meanwhile, the information disclosure flaw in WordPress core provides attackers with valid user emails, fueling targeted phishing campaigns that aim to secure the same account access achievable through the other exploits.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b8ab4644f8044f3485441ee052f30a13" />
-      </td>
-      <td>100535A</td>
-      <td>Sitecore - Dangerous File Upload - CVE:CVE-2025-34510, CVE:CVE-2025-34511</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
-      </td>
-      <td>100535</td>
-      <td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
-      </td>
-      <td>100543</td>
-      <td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
-      </td>
-      <td>100545</td>
-      <td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="28108d25f1cf470c8e7648938f634977" />
-      </td>
-      <td>100820</td>
-      <td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
-      </td>
-      <td>100821</td>
-      <td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
-      </td>
-      <td>100822</td>
-      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="69d43d704b0641898141a4300bf1b661" />
-      </td>
-      <td>100823</td>
-      <td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b8ab4644f8044f3485441ee052f30a13" />
+			</td>
+			<td>100535A</td>
+			<td>
+				Sitecore - Dangerous File Upload - CVE:CVE-2025-34510,
+				CVE:CVE-2025-34511
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
+			</td>
+			<td>100535</td>
+			<td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
+			</td>
+			<td>100543</td>
+			<td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
+			</td>
+			<td>100545</td>
+			<td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="28108d25f1cf470c8e7648938f634977" />
+			</td>
+			<td>100820</td>
+			<td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
+			</td>
+			<td>100821</td>
+			<td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
+			</td>
+			<td>100822</td>
+			<td>
+				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="69d43d704b0641898141a4300bf1b661" />
+			</td>
+			<td>100823</td>
+			<td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
index e7e5dad628ec2f1..e9deb9cfadebeca 100644
--- a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
@@ -23,39 +23,42 @@ Adobe AEM’s remote code execution vulnerability enables attackers to run arbit
 These findings reinforce the urgency of updating to the patched versions — Squid 6.4 and Adobe AEM 6.5.24 or later — and reviewing configurations to prevent exploitation.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
-      </td>
-      <td>100844</td>
-      <td>Adobe Experience Manager Forms - Remote Code Execution - CVE:CVE-2025-54253</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
-      </td>
-      <td>100840</td>
-      <td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
+			</td>
+			<td>100844</td>
+			<td>
+				Adobe Experience Manager Forms - Remote Code Execution -
+				CVE:CVE-2025-54253
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
+			</td>
+			<td>100840</td>
+			<td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-11-waf-release.mdx b/src/content/changelog/waf/2025-08-11-waf-release.mdx
index 62764e4b09840a6..74a303e3d74c2fb 100644
--- a/src/content/changelog/waf/2025-08-11-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-11-waf-release.mdx
@@ -8,26 +8,21 @@ import { RuleID } from "~/components";
 
 This week's update focuses on a wide range of enterprise software, from network infrastructure and security platforms to content management systems and development frameworks. Flaws include unsafe deserialization, OS command injection, SSRF, authentication bypass, and arbitrary file upload — many of which allow unauthenticated remote code execution. Notable risks include Cisco Identity Services Engine and Ivanti EPMM, where successful exploitation could grant attackers full administrative control of core network infrastructure and popular web services such as WordPress, SharePoint, and Ingress-Nginx, where security bypasses and arbitrary file uploads could lead to complete site or server compromise.
 
-
 **Key Findings**
 
 - Cisco Identity Services Engine (CVE-2025-20281): Insufficient input validation in a specific API of Cisco Identity Services Engine (ISE) and ISE-PIC allows an unauthenticated, remote attacker to execute arbitrary code with root privileges on an affected device.
 
 - Wazuh Server (CVE-2025-24016): An unsafe deserialization vulnerability in Wazuh Server (versions 4.4.0 to 4.9.0) allows for remote code execution and privilege escalation. By injecting unsanitized data, an attacker can trigger an exception to execute arbitrary code on the server.
 
-
 - CrushFTP (CVE-2025-54309): A flaw in AS2 validation within CrushFTP allows remote attackers to gain administrative access via HTTPS on systems not using the DMZ proxy feature. This flaw can lead to unauthorized file access and potential system compromise.
 
-
 - Kentico Xperience CMS (CVE-2025-2747, CVE-2025-2748): Vulnerabilities in Kentico Xperience CMS could enable cross-site scripting (XSS), allowing attackers to inject malicious scripts into web pages. Additionally, a flaw could allow unauthenticated attackers to bypass the Staging Sync Server's authentication, potentially leading to administrative control over the CMS.
 
-
 - Node.js (CVE-2025-27210): An incomplete fix for a previous vulnerability (CVE-2025-23084) in Node.js affects the `path.join()` API method on Windows systems. The vulnerability can be triggered using reserved Windows device names such as `CON`, `PRN`, or `AUX`.
 
-- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847): 
-This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
-(Note: CVE-2025-34085 has been rejected as a duplicate.)
-
+- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847):
+  This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
+  (Note: CVE-2025-34085 has been rejected as a duplicate.)
 
 - GeoServer (CVE-2024-29198): A Server-Side Request Forgery (SSRF) vulnerability exists in GeoServer's Demo request endpoint, which can be exploited where the Proxy Base URL has not been configured.
 
@@ -37,240 +32,239 @@ This vulnerability in the Simple File List plugin for WordPress allows an unauth
 
 - Manager-IO (CVE-2025-54122): A critical unauthenticated full read Server-Side Request Forgery (SSRF) vulnerability is present in the proxy handler of both Manager Desktop and Server editions up to version 25.7.18.2519. This allows an unauthenticated attacker to bypass network isolation and access internal services.
 
-- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. 
+- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller.
 
 - PaperCut NG/MF (CVE-2023-2533): A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PaperCut NG/MF. Under specific conditions, an attacker could exploit this to alter security settings or execute arbitrary code if they can deceive an administrator with an active login session into clicking a malicious link.
 
 - SonicWall SMA (CVE-2025-40598): This vulnerability could allow an unauthenticated attacker to bypass security controls. This allows a remote, unauthenticated attacker to potentially execute arbitrary JavaScript code.
 
-- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress  is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
-
+- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
 
 **Impact**
 
 These vulnerabilities span a broad range of enterprise technologies, including network access control systems, monitoring platforms, web servers, CMS platforms, cloud services, and collaboration tools. Exploitation techniques range from remote code execution and command injection to authentication bypass, SQL injection, path traversal, and configuration weaknesses.
 
-A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers. 
+A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ec6480c81253494b947d891e51bc8df1" />
-      </td>
-      <td>100538</td>
-      <td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
-      </td>
-      <td>100548</td>
-      <td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
-      </td>
-      <td>100550</td>
-      <td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e1369c5d629f4f10a14141381dca5738" />
-      </td>
-      <td>100562</td>
-      <td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
-      </td>
-      <td>100565</td>
-      <td>
-        Cisco Identity Services Engine - Remote Code Execution -
-        CVE:CVE-2025-20281
-      </td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed759f7e44184fa398ef71785d8102e1" />
-      </td>
-      <td>100567</td>
-      <td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="71b8e7b646f94d79873213cd99105c43" />
-      </td>
-      <td>100569</td>
-      <td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
-      </td>
-      <td>100571</td>
-      <td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
-      </td>
-      <td>100573</td>
-      <td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
-      </td>   
-      <td>100806</td>      
-      <td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
-      </td>
-      <td>100824</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3638baed75924604987b86d874920ace" />
-      </td>
-      <td>100824A</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
-      </td>
-      <td>100825</td>
-      <td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
-      <td>Log</td>
-      <td>Block</td> 
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
-      </td>
-      <td>100826</td>
-      <td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
-      </td>
-      <td>100827</td>
-      <td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="54dd826f578c483196ce852b6f1c2d12" />
-      </td>
-      <td>100828</td>
-      <td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a2867f7456c14213a94509a40341fccc" />
-      </td>
-      <td>100829</td>
-      <td>
-        WordPress:Plugin:Simple File List - Remote Code Execution -
-        CVE:CVE-2025-34085
-      </td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4cdb0e792d1a428a897526624cefeeda" />
-      </td>
-      <td>100829A</td>
-      <td>
-        WordPress:Plugin:Simple File List - Remote Code Execution -
-        CVE:CVE-2025-34085 - 2
-      </td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ec6480c81253494b947d891e51bc8df1" />
+			</td>
+			<td>100538</td>
+			<td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
+			</td>
+			<td>100548</td>
+			<td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
+			</td>
+			<td>100550</td>
+			<td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e1369c5d629f4f10a14141381dca5738" />
+			</td>
+			<td>100562</td>
+			<td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
+			</td>
+			<td>100565</td>
+			<td>
+				Cisco Identity Services Engine - Remote Code Execution -
+				CVE:CVE-2025-20281
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed759f7e44184fa398ef71785d8102e1" />
+			</td>
+			<td>100567</td>
+			<td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="71b8e7b646f94d79873213cd99105c43" />
+			</td>
+			<td>100569</td>
+			<td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
+			</td>
+			<td>100571</td>
+			<td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
+			</td>
+			<td>100573</td>
+			<td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
+			</td>
+			<td>100806</td>
+			<td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
+			</td>
+			<td>100824</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3638baed75924604987b86d874920ace" />
+			</td>
+			<td>100824A</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
+			</td>
+			<td>100825</td>
+			<td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
+			</td>
+			<td>100826</td>
+			<td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
+			</td>
+			<td>100827</td>
+			<td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="54dd826f578c483196ce852b6f1c2d12" />
+			</td>
+			<td>100828</td>
+			<td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a2867f7456c14213a94509a40341fccc" />
+			</td>
+			<td>100829</td>
+			<td>
+				WordPress:Plugin:Simple File List - Remote Code Execution -
+				CVE:CVE-2025-34085
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4cdb0e792d1a428a897526624cefeeda" />
+			</td>
+			<td>100829A</td>
+			<td>
+				WordPress:Plugin:Simple File List - Remote Code Execution -
+				CVE:CVE-2025-34085 - 2
+			</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-18-waf-release.mdx b/src/content/changelog/waf/2025-08-18-waf-release.mdx
index 78b79350ea882e6..8f05b2eb924b63f 100644
--- a/src/content/changelog/waf/2025-08-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-18-waf-release.mdx
@@ -31,138 +31,143 @@ This week, a series of critical vulnerabilities were discovered impacting core e
 These vulnerabilities affect core infrastructure, from network security appliances like SonicWall to data platforms such as Apache Druid and ML frameworks like BentoML. The code execution and deserialization flaws are particularly severe, offering deep system access that allows attackers to steal data, disrupt services, and establish a foothold for broader intrusions. Simultaneously, SSRF and XXE vulnerabilities undermine network boundaries, exposing sensitive internal data and creating pathways for lateral movement. Beyond data-centric threats, flaws in edge devices like the Tenda router introduce the tangible risk of operational disruption, highlighting a multi-faceted threat to the security and stability of key enterprise systems.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
-      </td>
-      <td>100574</td>
-      <td>SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819, CVE:CVE-2025-32820, CVE:CVE-2025-32821</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
-      </td>
-      <td>100576</td>
-      <td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d62935357ff846d9adefb58108ac45b3" />
-      </td>
-      <td>100585</td>
-      <td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
-      </td>
-      <td>100834</td>
-      <td>Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="1474121b01ba40629f8246f8022ab542" />
-      </td>
-      <td>100835</td>
-      <td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
-      </td>
-      <td>100837</td>
-      <td>SQLi - OOB</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
-      </td>
-      <td>100841</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="40fd793035c947c5ac75add1739180d2" />
-      </td>
-      <td>100841A</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
-      </td>
-      <td>100841B</td>
-      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
-      </td>
-      <td>100845</td>
-      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
-      </td>
-      <td>100845A</td>
-      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
+			</td>
+			<td>100574</td>
+			<td>
+				SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819,
+				CVE:CVE-2025-32820, CVE:CVE-2025-32821
+			</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
+			</td>
+			<td>100576</td>
+			<td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d62935357ff846d9adefb58108ac45b3" />
+			</td>
+			<td>100585</td>
+			<td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
+			</td>
+			<td>100834</td>
+			<td>
+				Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="1474121b01ba40629f8246f8022ab542" />
+			</td>
+			<td>100835</td>
+			<td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
+			</td>
+			<td>100837</td>
+			<td>SQLi - OOB</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
+			</td>
+			<td>100841</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="40fd793035c947c5ac75add1739180d2" />
+			</td>
+			<td>100841A</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
+			</td>
+			<td>100841B</td>
+			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
+			</td>
+			<td>100845</td>
+			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
+			</td>
+			<td>100845A</td>
+			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-08-25-waf-release.mdx b/src/content/changelog/waf/2025-08-25-waf-release.mdx
index f78810c3fd8e64b..42c73f310668c3c 100644
--- a/src/content/changelog/waf/2025-08-25-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-25-waf-release.mdx
@@ -21,50 +21,56 @@ This week, critical vulnerabilities were disclosed that impact widely used open-
 These vulnerabilities pose severe risks to enterprise environments and open-source ecosystems. Remote code execution enables attackers to gain deep system access, steal data, disrupt services, and establish persistent footholds for broader intrusions. Given the widespread deployment of Apache HTTP Server and Laravel in production systems, timely patching and mitigation are critical.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c550282a0f7343ca887bdab528050359" />
-      </td>
-      <td>100822_BETA</td>
-      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This was merged in to the original rule "WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058" (ID: <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
-      </td>
-      <td>100831</td>
-      <td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
-      </td>
-      <td>100846</td>
-      <td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c550282a0f7343ca887bdab528050359" />
+			</td>
+			<td>100822_BETA</td>
+			<td>
+				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>
+				This was merged in to the original rule "WordPress:Plugin:WPBookit -
+				Remote Code Execution - CVE:CVE-2025-6058" (ID:{" "}
+				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
+			</td>
+			<td>100831</td>
+			<td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
+			</td>
+			<td>100846</td>
+			<td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
index e11552cfbac77e9..0d6fc5ee3b10133 100644
--- a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
@@ -21,39 +21,39 @@ This week, new critical vulnerabilities were disclosed in Next.js’s image opti
 Exploitation could expose sensitive files, leak user or backend data, and undermine application trust. Given Next.js’s wide use, immediate patching and cache hardening are strongly advised.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
-      </td>
-      <td>100613</td>
-      <td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
-      </td>
-      <td>100616</td>
-      <td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
+			</td>
+			<td>100613</td>
+			<td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
+			</td>
+			<td>100616</td>
+			<td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-01-waf-release.mdx b/src/content/changelog/waf/2025-09-01-waf-release.mdx
index 5470b675623f1e5..88aa80a7543ddf4 100644
--- a/src/content/changelog/waf/2025-09-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-01-waf-release.mdx
@@ -10,50 +10,48 @@ import { RuleID } from "~/components";
 
 This week, a critical vulnerability was disclosed in Fortinet FortiWeb (versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and versions 7.0.10 and below), linked to improper parameter handling that could allow unauthorized access.
 
-
 **Key Findings**
 
-* Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
+- Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
 
 **Impact**
 
-Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended. 
-
+Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="636b145a49a84946b990d4fac49b7cf8" />
-      </td>
-      <td>100586</td>
-      <td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
-      </td>
-      <td>100136C</td>
-      <td>XSS - JavaScript - Headers and Body</td>
-      <td>N/A</td>
-      <td>N/A</td>
-      <td>Rule metadata description refined. Detection unchanged.</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="636b145a49a84946b990d4fac49b7cf8" />
+			</td>
+			<td>100586</td>
+			<td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
+			</td>
+			<td>100136C</td>
+			<td>XSS - JavaScript - Headers and Body</td>
+			<td>N/A</td>
+			<td>N/A</td>
+			<td>Rule metadata description refined. Detection unchanged.</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
index 385a50fe802115e..5855b853f30db8a 100644
--- a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
@@ -12,6 +12,7 @@ This week, new critical vulnerabilities were disclosed in Sitecore’s Sitecore
 These flaws are caused by unsafe data deserialization and code reflection, leaving affected systems at high risk of exploitation.
 
 **Key Findings**
+
 - CVE-2025-53690: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53691: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53693: HTML Cache Poisoning through Unsafe Reflections
@@ -21,50 +22,50 @@ These flaws are caused by unsafe data deserialization and code reflection, leavi
 Exploitation could allow attackers to execute arbitrary code remotely on the affected system and conduct cache poisoning attacks, potentially leading to further compromise. Applying the latest vendor-released solution without delay is strongly recommended.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
-      </td>
-      <td>100878</td>
-      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-      </td>
-      <td>100631</td>
-      <td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed94c7ce5301411a94a21a096c410240" />
-      </td>
-      <td>100879</td>
-      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
+			</td>
+			<td>100878</td>
+			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+			</td>
+			<td>100631</td>
+			<td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed94c7ce5301411a94a21a096c410240" />
+			</td>
+			<td>100879</td>
+			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-08-waf-release.mdx b/src/content/changelog/waf/2025-09-08-waf-release.mdx
index 1784243e8d5d2af..ccc94cccb99a6c9 100644
--- a/src/content/changelog/waf/2025-09-08-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-08-waf-release.mdx
@@ -6,21 +6,21 @@ date: 2025-09-08
 
 import { RuleID } from "~/components";
 
-**This week's update** 
+**This week's update**
 
 This week’s focus highlights newly disclosed vulnerabilities in web frameworks, enterprise applications, and widely deployed CMS plugins. The vulnerabilities include SSRF, authentication bypass, arbitrary file upload, and remote code execution (RCE), exposing organizations to high-impact risks such as unauthorized access, system compromise, and potential data exposure. In addition, security rule enhancements have been deployed to cover general command injection and server-side injection attacks, further strengthening protections.
 
 **Key Findings**
 
-* Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
+- Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
 
-* ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
+- ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
 
-* Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
+- Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
 
-* Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
+- Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
 
-* WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
+- WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
 
 **Impact**
 
@@ -29,116 +29,128 @@ These vulnerabilities could allow attackers to gain unauthorized access, execute
 Administrators are strongly advised to apply vendor patches immediately, remove unsupported software, and review authentication and access controls to mitigate these risks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
-      </td>
-      <td>100007D</td>
-      <td>Command Injection - Common Attack Commands Args</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "Command Injection - Common Attack Commands" (ID: <RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers only.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cd528243d6824f7ab56182988230a75b" />
-      </td>      
-      <td>100617</td>
-      <td>Next.js - SSRF - CVE:CVE-2025-57822</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
-      </td>
-      <td>100659_BETA</td>
-      <td>Common Payloads for Server-Side Template Injection - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "Common Payloads for Server-Side Template Injection" (ID: <RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)</td>
-    </tr>    
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
-      </td>
-      <td>100824B</td>
-      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>    
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
-      </td>
-      <td>100848</td>
-      <td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
-      </td>
-      <td>100849</td>
-      <td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e7464139fd3e44938b56716bef971afd" />
-      </td>
-      <td>100872</td>
-      <td>WordPress:Plugin:InfiniteWP Client - Missing Authorization - CVE:CVE-2020-8772</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
-      </td>
-      <td>100873</td>
-      <td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
-      </td>
-      <td>100875</td>
-      <td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>    
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
+			</td>
+			<td>100007D</td>
+			<td>Command Injection - Common Attack Commands Args</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "Command Injection -
+				Common Attack Commands" (ID:{" "}
+				<RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers
+				only.
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cd528243d6824f7ab56182988230a75b" />
+			</td>
+			<td>100617</td>
+			<td>Next.js - SSRF - CVE:CVE-2025-57822</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
+			</td>
+			<td>100659_BETA</td>
+			<td>Common Payloads for Server-Side Template Injection - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "Common Payloads for
+				Server-Side Template Injection" (ID:{" "}
+				<RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
+			</td>
+			<td>100824B</td>
+			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
+			</td>
+			<td>100848</td>
+			<td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
+			</td>
+			<td>100849</td>
+			<td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e7464139fd3e44938b56716bef971afd" />
+			</td>
+			<td>100872</td>
+			<td>
+				WordPress:Plugin:InfiniteWP Client - Missing Authorization -
+				CVE:CVE-2020-8772
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
+			</td>
+			<td>100873</td>
+			<td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
+			</td>
+			<td>100875</td>
+			<td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-15-waf-release.mdx b/src/content/changelog/waf/2025-09-15-waf-release.mdx
index d6bb571fc9be330..56e8dbc6e1051d7 100644
--- a/src/content/changelog/waf/2025-09-15-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-15-waf-release.mdx
@@ -12,11 +12,11 @@ This week's focus highlights newly disclosed vulnerabilities in DevOps tooling,
 
 **Key Findings**
 
-* Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
+- Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
 
-* DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
+- DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
 
-* Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
+- Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
 
 **Impact**
 
@@ -25,50 +25,50 @@ These vulnerabilities expose organizations to serious risks, including credentia
 Administrators are strongly advised to apply vendor patches immediately, rotate exposed credentials, and review access controls to mitigate these risks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
-      </td>
-      <td>100646</td>
-      <td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
-      </td>
-      <td>100874</td>
-      <td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
-      </td>
-      <td>100880</td>
-      <td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
+			</td>
+			<td>100646</td>
+			<td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
+			</td>
+			<td>100874</td>
+			<td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
+			</td>
+			<td>100880</td>
+			<td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-22-waf-release.mdx b/src/content/changelog/waf/2025-09-22-waf-release.mdx
index fd3fff204e42727..054a8348718a766 100644
--- a/src/content/changelog/waf/2025-09-22-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-22-waf-release.mdx
@@ -10,124 +10,125 @@ This week emphasizes two critical vendor-specific vulnerabilities: a full elevat
 
 **Key Findings**
 
+- Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges.
 
-* Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges. 
+- Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind).
 
-* Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind). 
-
-* Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
+- Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
 
 **Impact**
 
 These vulnerabilities allow attackers to escalate privileges or execute code under conditions where previously they could not:
 
-* Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components. 
-
-* Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components. 
+- Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components.
 
-* The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
+- Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components.
 
+- The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
-      </td>
-      <td>100146</td>
-      <td>SSRF - Host - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
-      </td>
-      <td>100146B</td>
-      <td>SSRF - Local - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
-      </td>
-      <td>100146C</td>
-      <td>SSRF - Cloud - 2</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="78c856218f2d40f4b5988c8c956c1961" />
-      </td>
-      <td>100714</td>
-      <td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
-      </td>
-      <td>100758</td>
-      <td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
-      </td>
-      <td>100773</td>
-      <td>Next.js - SSRF</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
-      </td>
-      <td>100774</td>
-      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
-      </td>
-      <td>100800_BETA</td>
-      <td>SQLi - Obfuscated Boolean - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule (ID: <RuleID id="7663ea44178441a0b3205c145563445f" />)</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
+			</td>
+			<td>100146</td>
+			<td>SSRF - Host - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
+			</td>
+			<td>100146B</td>
+			<td>SSRF - Local - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
+			</td>
+			<td>100146C</td>
+			<td>SSRF - Cloud - 2</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="78c856218f2d40f4b5988c8c956c1961" />
+			</td>
+			<td>100714</td>
+			<td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
+			</td>
+			<td>100758</td>
+			<td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
+			</td>
+			<td>100773</td>
+			<td>Next.js - SSRF</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
+			</td>
+			<td>100774</td>
+			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
+			</td>
+			<td>100800_BETA</td>
+			<td>SQLi - Obfuscated Boolean - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule (ID:{" "}
+				<RuleID id="7663ea44178441a0b3205c145563445f" />)
+			</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
index 2a09bf015de4913..05259d94a3946ba 100644
--- a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
@@ -10,35 +10,35 @@ This week highlights a critical vendor-specific vulnerability: a deserialization
 
 **Key Findings**
 
-* GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
+- GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
 
 **Impact**
 
 GoAnywhere MFT (CVE-2025-10035): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
-      </td>
-      <td>100787</td>
-      <td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
+			</td>
+			<td>100787</td>
+			<td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-26-waf-release.mdx b/src/content/changelog/waf/2025-09-26-waf-release.mdx
index b7e0125e8fa0a1a..aeb564538854fe1 100644
--- a/src/content/changelog/waf/2025-09-26-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-26-waf-release.mdx
@@ -11,138 +11,138 @@ import { RuleID } from "~/components";
 This update introduces 11 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
-      </td>
-      <td>100859A</td>
-      <td>SQLi - UNION - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
-      </td>
-      <td>100889</td>
-      <td>Command Injection - Generic 9</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c15ca8e8290f485287037665f2be3ddf" />
-      </td>
-      <td>100890</td>
-      <td>Information Disclosure - Common Files - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="56669615f2984c2cac8c608980a252a8" />
-      </td>
-      <td>100891</td>
-      <td>Anomaly:URL - Relative Paths</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c41789fb6370431d809567d17e7d3865" />
-      </td>
-      <td>100894</td>
-      <td>XSS - Inline Function</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
-      </td>
-      <td>100895</td>
-      <td>XSS - DOM</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab8277e3f432400bbd9403dd42978e38" />
-      </td>
-      <td>100896</td>
-      <td>SQLi - MSSQL Length Enumeration</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-      </td>
-      <td>100897</td>
-      <td>Generic Rules - Code Injection - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4375dc90c7af4c55908f6b95c1686741" />
-      </td>
-      <td>100898</td>
-      <td>SQLi - Evasion</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="945c5aa9f45141dd872d7ec920999be0" />
-      </td>
-      <td>100899</td>
-      <td>SQLi - Probing 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2c20b5e8684043f48620ff77b4026c88" />
-      </td>
-      <td>100900</td>
-      <td>SQLi - Probing</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
+			</td>
+			<td>100859A</td>
+			<td>SQLi - UNION - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
+			</td>
+			<td>100889</td>
+			<td>Command Injection - Generic 9</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c15ca8e8290f485287037665f2be3ddf" />
+			</td>
+			<td>100890</td>
+			<td>Information Disclosure - Common Files - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="56669615f2984c2cac8c608980a252a8" />
+			</td>
+			<td>100891</td>
+			<td>Anomaly:URL - Relative Paths</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c41789fb6370431d809567d17e7d3865" />
+			</td>
+			<td>100894</td>
+			<td>XSS - Inline Function</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
+			</td>
+			<td>100895</td>
+			<td>XSS - DOM</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab8277e3f432400bbd9403dd42978e38" />
+			</td>
+			<td>100896</td>
+			<td>SQLi - MSSQL Length Enumeration</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+			</td>
+			<td>100897</td>
+			<td>Generic Rules - Code Injection - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4375dc90c7af4c55908f6b95c1686741" />
+			</td>
+			<td>100898</td>
+			<td>SQLi - Evasion</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
+			</td>
+			<td>100899</td>
+			<td>SQLi - Probing 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2c20b5e8684043f48620ff77b4026c88" />
+			</td>
+			<td>100900</td>
+			<td>SQLi - Probing</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
index 93fe72102454c07..73bca3b78f919ec 100644
--- a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
@@ -10,46 +10,52 @@ This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CV
 
 **Key Findings**
 
-* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
 Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
-      </td>
-      <td>100788</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="51de6ce6596a40eb8200452ad30f768e" />
-      </td>
-      <td>100788A</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
+			</td>
+			<td>100788</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="51de6ce6596a40eb8200452ad30f768e" />
+			</td>
+			<td>100788A</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-09-29-waf-release.mdx b/src/content/changelog/waf/2025-09-29-waf-release.mdx
index b48fadd2caabecb..e4a7094b34030a4 100644
--- a/src/content/changelog/waf/2025-09-29-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-29-waf-release.mdx
@@ -10,82 +10,85 @@ This week highlights four important vendor- and component-specific issues: an au
 
 **Key Findings**
 
-* SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
+- SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
 
-* Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
+- Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
 
-* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
+- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
 
-* Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
+- Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
 
 **Impact**
 
 These vulnerabilities allow attackers to gain access, escalate privileges, or execute actions that were previously unavailable:
 
-* SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
+- SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
 
-* Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
+- Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
 
-* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
+- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
 
-* Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
+- Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6fe90532af50427484a5275c8c2e30fb" />
-      </td>
-      <td>100717</td>
-      <td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged to 100717 in legacy WAF and <RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
-      </td>
-      <td>100775</td>
-      <td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
-      </td>
-      <td>100881</td>
-      <td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
-      </td>
-      <td>100887</td>
-      <td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6fe90532af50427484a5275c8c2e30fb" />
+			</td>
+			<td>100717</td>
+			<td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged to 100717 in legacy WAF and{" "}
+				<RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
+			</td>
+			<td>100775</td>
+			<td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
+			</td>
+			<td>100881</td>
+			<td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
+			</td>
+			<td>100887</td>
+			<td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-10-03-waf-release.mdx b/src/content/changelog/waf/2025-10-03-waf-release.mdx
index c01420c6f44b5c8..f868e1edd121f98 100644
--- a/src/content/changelog/waf/2025-10-03-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-03-waf-release.mdx
@@ -11,248 +11,248 @@ import { RuleID } from "~/components";
 This update introduces 21 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
-      </td>
-      <td>100902</td>
-      <td>Generic Rules - Command Execution - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c3079865ce9a41368657026b514aeeb8" />
-      </td>
-      <td>100908</td>
-      <td>Generic Rules - Command Execution - 3</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
-      </td>
-      <td>100910</td>
-      <td>Generic Rules - Command Execution - 4</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
-      </td>
-      <td>100915</td>
-      <td>Generic Rules - Command Execution - 5</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
-      </td>
-      <td>100899</td>
-      <td>Generic Rules - Content-Type Abuse</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="233364f656ff42b8acc41dcd7996012f" />
-      </td>
-      <td>100914</td>
-      <td>Generic Rules - Content-Type Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="1aa695281c954513be3d003b93209312" />
-      </td>
-      <td>100911</td>
-      <td>Generic Rules - Cookie Header Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
-      </td>
-      <td>100905</td>
-      <td>Generic Rules - NoSQL Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
-      </td>
-      <td>100913</td>
-      <td>Generic Rules - NoSQL Injection - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
-      </td>
-      <td>100907</td>
-      <td>Generic Rules - Parameter Pollution</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
-      </td>
-      <td>100906</td>
-      <td>Generic Rules - PHP Object Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ed5190bfbe1b45a6a645126334c88168" />
-      </td>
-      <td>100904</td>
-      <td>Generic Rules - Prototype Pollution</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-      </td>
-      <td>100897</td>
-      <td>Generic Rules - Prototype Pollution 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
-      </td>
-      <td>100903</td>
-      <td>Generic Rules - Reverse Shell</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
-      </td>
-      <td>100909</td>
-      <td>Generic Rules - Reverse Shell - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="475d090baead467c88dfabbb565c78b0" />
-      </td>
-      <td>100898</td>
-      <td>Generic Rules - SSJI NoSQL</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="f4c7f98934264c9c937eec1212b837a0" />
-      </td>
-      <td>100896</td>
-      <td>Generic Rules - SSRF</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="efd01b814d144e90b36522b311c4fb00" />
-      </td>
-      <td>100895</td>
-      <td>Generic Rules - Template Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="00a9a0d663da4add95b863abd3ed0123" />
-      </td>
-      <td>100895A</td>
-      <td>Generic Rules - Template Injection - 2</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
-      </td>
-      <td>100912</td>
-      <td>Generic Rules - XXE</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
-      </td>
-      <td>100900</td>
-      <td>Relative Paths - Anomaly Headers</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
+			</td>
+			<td>100902</td>
+			<td>Generic Rules - Command Execution - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c3079865ce9a41368657026b514aeeb8" />
+			</td>
+			<td>100908</td>
+			<td>Generic Rules - Command Execution - 3</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
+			</td>
+			<td>100910</td>
+			<td>Generic Rules - Command Execution - 4</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
+			</td>
+			<td>100915</td>
+			<td>Generic Rules - Command Execution - 5</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
+			</td>
+			<td>100899</td>
+			<td>Generic Rules - Content-Type Abuse</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="233364f656ff42b8acc41dcd7996012f" />
+			</td>
+			<td>100914</td>
+			<td>Generic Rules - Content-Type Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="1aa695281c954513be3d003b93209312" />
+			</td>
+			<td>100911</td>
+			<td>Generic Rules - Cookie Header Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
+			</td>
+			<td>100905</td>
+			<td>Generic Rules - NoSQL Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
+			</td>
+			<td>100913</td>
+			<td>Generic Rules - NoSQL Injection - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
+			</td>
+			<td>100907</td>
+			<td>Generic Rules - Parameter Pollution</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
+			</td>
+			<td>100906</td>
+			<td>Generic Rules - PHP Object Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ed5190bfbe1b45a6a645126334c88168" />
+			</td>
+			<td>100904</td>
+			<td>Generic Rules - Prototype Pollution</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+			</td>
+			<td>100897</td>
+			<td>Generic Rules - Prototype Pollution 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
+			</td>
+			<td>100903</td>
+			<td>Generic Rules - Reverse Shell</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
+			</td>
+			<td>100909</td>
+			<td>Generic Rules - Reverse Shell - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="475d090baead467c88dfabbb565c78b0" />
+			</td>
+			<td>100898</td>
+			<td>Generic Rules - SSJI NoSQL</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="f4c7f98934264c9c937eec1212b837a0" />
+			</td>
+			<td>100896</td>
+			<td>Generic Rules - SSRF</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="efd01b814d144e90b36522b311c4fb00" />
+			</td>
+			<td>100895</td>
+			<td>Generic Rules - Template Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="00a9a0d663da4add95b863abd3ed0123" />
+			</td>
+			<td>100895A</td>
+			<td>Generic Rules - Template Injection - 2</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
+			</td>
+			<td>100912</td>
+			<td>Generic Rules - XXE</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
+			</td>
+			<td>100900</td>
+			<td>Relative Paths - Anomaly Headers</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-06-waf-release.mdx b/src/content/changelog/waf/2025-10-06-waf-release.mdx
index d4f1efa95c7512e..89c8ea1bc8db134 100644
--- a/src/content/changelog/waf/2025-10-06-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-06-waf-release.mdx
@@ -10,122 +10,124 @@ This week’s highlights prioritise an emergency Oracle E-Business Suite RCE rul
 
 **Key Findings**
 
-* New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
+- New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
 
-* Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
+- Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
 
-* Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
+- Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
 
-* Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
+- Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
 
 **Impact**
 
-* CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced. 
+- CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced.
 
-* CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
+- CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
 
-* CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
+- CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
-      </td>
-      <td>100882</td>
-      <td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
-      </td>
-      <td>100883</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a2591ba5befa4815a6861aefef859a04" />
-      </td>
-      <td>100884</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
-      </td>
-      <td>100886</td>
-      <td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="90514c7810694b188f56979826a4074c" />
-      </td>
-      <td>100888</td>
-      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
-      </td>
-      <td>100916</td>
-      <td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="badc687a3ba3420a844220b129aa43c3" />
-      </td>
-      <td>100917</td>
-      <td>Generic Rules - SQLi - Inline Comment Injection</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="28fa27511f29428899ceb5a273c10b6f" />
-      </td>
-      <td>100918</td>
-      <td>Generic Rules - SQLi - Information Disclosure</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a New Detection</td>
-    </tr>                    
-  </tbody>
-</table>
\ No newline at end of file
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
+			</td>
+			<td>100882</td>
+			<td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
+			</td>
+			<td>100883</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a2591ba5befa4815a6861aefef859a04" />
+			</td>
+			<td>100884</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
+			</td>
+			<td>100886</td>
+			<td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="90514c7810694b188f56979826a4074c" />
+			</td>
+			<td>100888</td>
+			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
+			</td>
+			<td>100916</td>
+			<td>
+				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="badc687a3ba3420a844220b129aa43c3" />
+			</td>
+			<td>100917</td>
+			<td>Generic Rules - SQLi - Inline Comment Injection</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="28fa27511f29428899ceb5a273c10b6f" />
+			</td>
+			<td>100918</td>
+			<td>Generic Rules - SQLi - Information Disclosure</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
+</table>
diff --git a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
index fa9d65c7613c3e3..724fe2ad9d9bcae 100644
--- a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
@@ -7,9 +7,9 @@ date: 2025-10-07
 import { RuleID } from "~/components";
 
 This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CVE-2025-20333, CVE-2025-20362). This flaw stems from improper input validation in HTTP(S) requests. An authenticated VPN user could send crafted requests to execute code as root, potentially compromising the device.
-The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection. 
+The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection.
 
-* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
@@ -17,28 +17,31 @@ Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables att
 Administrators are strongly advised to apply vendor updates immediately.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
-      </td>
-      <td>100788B</td>
-      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
+			</td>
+			<td>100788B</td>
+			<td>
+				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
+				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
+			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
index 3001df61385c0d0..fc5674015901639 100644
--- a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
@@ -47,7 +47,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="72f0ff933fb0492eb71cda50589f2a1d" /></td>
+			<td>
+				<RuleID id="72f0ff933fb0492eb71cda50589f2a1d" />
+			</td>
 			<td>N/A</td>
 			<td>Anomaly:Header - name - CR, LF</td>
 			<td>N/A</td>
@@ -56,7 +58,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="5d0377e4435f467488614170132fab7e" /></td>
+			<td>
+				<RuleID id="5d0377e4435f467488614170132fab7e" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Body</td>
 			<td>N/A</td>
@@ -65,7 +69,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="54e32f7f802c4a699182e8921a027008" /></td>
+			<td>
+				<RuleID id="54e32f7f802c4a699182e8921a027008" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Header</td>
 			<td>N/A</td>
@@ -74,7 +80,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" /></td>
+			<td>
+				<RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - URI</td>
 			<td>N/A</td>
@@ -83,7 +91,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="b9f3420674cf481da32333dc8e0cf7ad" /></td>
+			<td>
+				<RuleID id="b9f3420674cf481da32333dc8e0cf7ad" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - XXE - Body</td>
 			<td>N/A</td>
@@ -92,7 +102,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="ad55483512f0440b81426acdbf8aab5e" /></td>
+			<td>
+				<RuleID id="ad55483512f0440b81426acdbf8aab5e" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Common Patterns - Header URI</td>
 			<td>N/A</td>
@@ -101,7 +113,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="849c0618d1674f1c92ba6f9b2e466337" /></td>
+			<td>
+				<RuleID id="849c0618d1674f1c92ba6f9b2e466337" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Sleep Function - Header URI</td>
 			<td>N/A</td>
@@ -110,7 +124,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" /></td>
+			<td>
+				<RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - String Function - Header URI</td>
 			<td>N/A</td>
@@ -119,7 +135,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="fa2055b84af94ba4b925f834b0633709" /></td>
+			<td>
+				<RuleID id="fa2055b84af94ba4b925f834b0633709" />
+			</td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - WaitFor Function - Header URI</td>
 			<td>N/A</td>
@@ -128,7 +146,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="158177dec2504acdba1f2da201a076eb" /></td>
+			<td>
+				<RuleID id="158177dec2504acdba1f2da201a076eb" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Local - Beta</td>
 			<td>N/A</td>
@@ -137,7 +157,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" /></td>
+			<td>
+				<RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Local - 2 - Beta</td>
 			<td>N/A</td>
@@ -146,7 +168,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" /></td>
+			<td>
+				<RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - Beta</td>
 			<td>N/A</td>
@@ -155,7 +179,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" /></td>
+			<td>
+				<RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" />
+			</td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - 2 - Beta</td>
 			<td>N/A</td>
@@ -164,7 +190,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="c16f4e133c4541f293142d02e6e8dc5b" /></td>
+			<td>
+				<RuleID id="c16f4e133c4541f293142d02e6e8dc5b" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - URI</td>
 			<td>N/A</td>
@@ -173,7 +201,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="f4fd9904e7624666b8c49cd62550d794" /></td>
+			<td>
+				<RuleID id="f4fd9904e7624666b8c49cd62550d794" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Header</td>
 			<td>N/A</td>
@@ -182,7 +212,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="5c0875604f774c36a4f9b69c659d12a6" /></td>
+			<td>
+				<RuleID id="5c0875604f774c36a4f9b69c659d12a6" />
+			</td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Body</td>
 			<td>N/A</td>
@@ -191,7 +223,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="fae6fa37ae9249d58628e54b1a3e521e" /></td>
+			<td>
+				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />
+			</td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -200,7 +234,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="9c02e585db34440da620eb668f76bd74" /></td>
+			<td>
+				<RuleID id="9c02e585db34440da620eb668f76bd74" />
+			</td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -209,7 +245,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="cb67fe56a84747b8b64277dc091e296d" /></td>
+			<td>
+				<RuleID id="cb67fe56a84747b8b64277dc091e296d" />
+			</td>
 			<td>N/A</td>
 			<td>HTTP parameter pollution</td>
 			<td>N/A</td>
@@ -218,7 +256,9 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td><RuleID id="443b54d984944cd69043805ee34214ef" /></td>
+			<td>
+				<RuleID id="443b54d984944cd69043805ee34214ef" />
+			</td>
 			<td>N/A</td>
 			<td>Prototype Pollution - Common Payloads - Beta</td>
 			<td>N/A</td>
@@ -226,4 +266,4 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-10-20-waf-release.mdx b/src/content/changelog/waf/2025-10-20-waf-release.mdx
index b566732da2e8dad..3768829710eb921 100644
--- a/src/content/changelog/waf/2025-10-20-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-20-waf-release.mdx
@@ -10,7 +10,7 @@ This week’s update introduces an enhanced rule that expands detection coverage
 
 **Key Findings**
 
-New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
+New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
 
 **Impact**
 
@@ -38,15 +38,21 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  una
 			<td>Remote Code Execution - Common Bash Bypass - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "Remote Code Execution - Common Bash Bypass" (ID: <RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)</td>
-		</tr>         
+			<td>
+				This rule is merged into the original rule "Remote Code Execution -
+				Common Bash Bypass" (ID:{" "}
+				<RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)
+			</td>
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="185b5df42d1e44e0aeb8f8b8a1118614" />
 			</td>
 			<td>100916A</td>
-			<td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2</td>
+			<td>
+				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -63,4 +69,4 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  una
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
index 968037a9f6bf67c..eff22509bb0f005 100644
--- a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ This vulnerability allows unauthenticated attackers to take over customer accoun
 Adobe Commerce (CVE-2025-54236): Exploitation may allow attackers to hijack sessions, execute arbitrary commands, steal data, and disrupt storefronts, resulting in confidentiality and integrity risks for merchants. Administrators are strongly encouraged to apply vendor patches without delay.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
-      </td>
-      <td>N/A</td>
-      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
+			</td>
+			<td>N/A</td>
+			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
index 4deb26e943c3254..ffa6cd0f4a1e7e6 100644
--- a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The vulnerability allows unauthenticated attackers to potentially achieve remote
 Successful exploitation of CVE-2025-59287 could enable attackers to hijack sessions, execute arbitrary commands, exfiltrate sensitive data, and disrupt storefront operations. These actions pose significant confidentiality and integrity risks to affected environments. Administrators should apply vendor patches immediately to mitigate exposure.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
-      </td>
-      <td>N/A</td>
-      <td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
+			</td>
+			<td>N/A</td>
+			<td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
index 48b39ac6c7cfe22..a3359450691e99c 100644
--- a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The flaw is easily exploitable and allows an unauthenticated attacker with netwo
 Successful exploitation of CVE-2025-61884 may result in unauthorized access to critical business data or full exposure of information accessible through Oracle Configurator. Administrators are strongly advised to apply vendor's patches and recommended mitigations to reduce this exposure.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
-      </td>
-      <td>N/A</td>
-      <td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
+			</td>
+			<td>N/A</td>
+			<td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
index c9584fd1902891f..65a2c278f87407e 100644
--- a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
@@ -14,31 +14,31 @@ The Metro Development Server exposes an HTTP endpoint that is vulnerable to OS c
 
 **Impact**
 
-Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk. 
+Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk.
 
 <table style="width: 100%">
-  <thead>
-    <tr>
-      <th>Ruleset</th>
-      <th>Rule ID</th>
-      <th>Legacy Rule ID</th>
-      <th>Description</th>
-      <th>Previous Action</th>
-      <th>New Action</th>
-      <th>Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
-      </td>
-      <td>N/A</td>
-      <td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a New Detection</td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Ruleset</th>
+			<th>Rule ID</th>
+			<th>Legacy Rule ID</th>
+			<th>Description</th>
+			<th>Previous Action</th>
+			<th>New Action</th>
+			<th>Comments</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
+			</td>
+			<td>N/A</td>
+			<td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a New Detection</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-10-waf-release.mdx b/src/content/changelog/waf/2025-11-10-waf-release.mdx
index c442f86894866c0..6f0e60f36daadeb 100644
--- a/src/content/changelog/waf/2025-11-10-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-10-waf-release.mdx
@@ -39,7 +39,7 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>    
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -61,6 +61,6 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>        
+		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-17-waf-release.mdx b/src/content/changelog/waf/2025-11-17-waf-release.mdx
index 38a33ac01a0985b..f34a07d31022e1b 100644
--- a/src/content/changelog/waf/2025-11-17-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-17-waf-release.mdx
@@ -63,4 +63,4 @@ This vulnerability allows unauthenticated attackers to gain privileged access to
 			<td>Rule metadata description refined. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
index 668d5120066318a..92ca15cf695904c 100644
--- a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
@@ -41,4 +41,4 @@ Oracle Identity Manager (CVE-2025-61757): Exploitation could allow an unauthenti
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-11-24-waf-release.mdx b/src/content/changelog/waf/2025-11-24-waf-release.mdx
index 40fe7147867f34d..b7949e4310a105d 100644
--- a/src/content/changelog/waf/2025-11-24-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-24-waf-release.mdx
@@ -35,7 +35,9 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 				<RuleID id="b957ace6e9844bf29244401c4e2e1a2e" />
 			</td>
 			<td>N/A</td>
-			<td>FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446</td>
+			<td>
+				FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
@@ -49,7 +51,11 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - Body - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>This rule has been merged into the original rule "PHP Wrapper Injection - Body" (ID:<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)</td>
+			<td>
+				This rule has been merged into the original rule "PHP Wrapper Injection
+				- Body" (ID:
+				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -60,7 +66,11 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - URI - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>This rule has been merged into the original rule "PHP Wrapper Injection - URI" (ID:<RuleID id="9c02e585db34440da620eb668f76bd74" />)</td>
+			<td>
+				This rule has been merged into the original rule "PHP Wrapper Injection
+				- URI" (ID:
+				<RuleID id="9c02e585db34440da620eb668f76bd74" />)
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-01-waf-release.mdx b/src/content/changelog/waf/2025-12-01-waf-release.mdx
index 5c9725909eb48b5..bb91b0b857039b3 100644
--- a/src/content/changelog/waf/2025-12-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-01-waf-release.mdx
@@ -39,7 +39,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
-		</tr>    
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -49,7 +49,10 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>XSS - JS Context Escape - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "XSS - JS Context Escape" (ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)</td>
-		</tr>  
+			<td>
+				This rule is merged into the original rule "XSS - JS Context Escape"
+				(ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)
+			</td>
+		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
index 1cdc563f6d10a45..ff06da00aab5c68 100644
--- a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
@@ -52,4 +52,4 @@ New WAF rule deployed for RCE Generic Framework to block malicious POST requests
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
index 317f93bc2050154..e22e9674a2f7a29 100644
--- a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
@@ -15,6 +15,7 @@ Rule description updated to reference React – RCE – CVE-2025-55182 while ret
 **Impact**
 
 Improved classification and traceability with no change to coverage against remote code execution attempts.
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -51,4 +52,4 @@ Improved classification and traceability with no change to coverage against remo
 			<td>Rule metadata description changed. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
index 3c6833f7416480d..25b82374c113154 100644
--- a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
@@ -85,4 +85,4 @@ These updates strengthen protection against React RCE exploitation attempts and
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
index 18c75f46429d216..35ce57a85250982 100644
--- a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
@@ -38,7 +38,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
+			<td>
+				This was labeled as Generic - Server Function Source Code Exposure.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Free Ruleset</td>
@@ -49,7 +51,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
+			<td>
+				This was labeled as Generic - Server Function Source Code Exposure.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -60,7 +64,9 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - DoS - CVE:CVE-2025-55184</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>This was labeled as Generic – Server Function Resource Exhaustion.</td>
+			<td>
+				This was labeled as Generic – Server Function Resource Exhaustion.
+			</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2025-12-18-waf-release.mdx b/src/content/changelog/waf/2025-12-18-waf-release.mdx
index 161f57af1c49b1b..1e89c7251d32210 100644
--- a/src/content/changelog/waf/2025-12-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-18-waf-release.mdx
@@ -12,10 +12,6 @@ This week's release focuses on improvements to existing detections to enhance co
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
-
-
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -28,105 +24,124 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
-      </td>
-      <td>N/A</td>
-      <td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "Atlassian Confluence - Code Injection - CVE:CVE-2021-26084" (ID: <RuleID id="e8c550810618437c953cf3a969e0b97a" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="9108ddb347b3497e9f9351640d9206e3" />
-      </td>
-      <td>N/A</td>
-      <td>PostgreSQL - SQLi - Copy - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "PostgreSQL - SQLi - COPY" (ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - Body</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - Header</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="6df040f716194070a242967cfd181fb3" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Command Execution - URI</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Tautology - URI - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Tautology - URI" (ID: <RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - WaitFor Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - WaitFor Function" (ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="80690005fef342e0ad6bc9af596c741e" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Equation 2 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Equation" (ID: <RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)</td>
-    </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
+			</td>
+			<td>N/A</td>
+			<td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "Atlassian Confluence - Code
+				Injection - CVE:CVE-2021-26084" (ID:{" "}
+				<RuleID id="e8c550810618437c953cf3a969e0b97a" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="9108ddb347b3497e9f9351640d9206e3" />
+			</td>
+			<td>N/A</td>
+			<td>PostgreSQL - SQLi - Copy - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "PostgreSQL - SQLi - COPY"
+				(ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - Body</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - Header</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6df040f716194070a242967cfd181fb3" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Command Execution - URI</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Tautology - URI - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Tautology - URI" (ID:{" "}
+				<RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - WaitFor Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - WaitFor Function"
+				(ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="80690005fef342e0ad6bc9af596c741e" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - AND/OR Digit Operator
+				Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Equation 2 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Equation" (ID:{" "}
+				<RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-12-waf-release.mdx b/src/content/changelog/waf/2026-01-12-waf-release.mdx
index f98c0a337960ed6..4c5e3ce6f9668d0 100644
--- a/src/content/changelog/waf/2026-01-12-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-12-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-12
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="72963b917ef74697b5bde02f48a1841a" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT" (ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Benchmark Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Benchmark Function" (ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="72963b917ef74697b5bde02f48a1841a" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT"
+				(ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Benchmark Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Benchmark Function"
+				(ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-15-waf-release.mdx b/src/content/changelog/waf/2026-01-15-waf-release.mdx
index 63c93358717c0b5..884dea72d886e11 100644
--- a/src/content/changelog/waf/2026-01-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-15-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-15
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - String Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - String Function" (ID: <RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Sub Query - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Sub Query" (ID: <RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Function - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - String Function" (ID:{" "}
+				<RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Sub Query - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Sub Query" (ID:{" "}
+				<RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-20-waf-release.mdx b/src/content/changelog/waf/2026-01-20-waf-release.mdx
index 0da1e57c513f3ef..1b7ca4114286eb1 100644
--- a/src/content/changelog/waf/2026-01-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-20-waf-release.mdx
@@ -6,13 +6,12 @@ date: 2026-01-20
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage. 
+This week's release focuses on improvements to existing detections to enhance coverage.
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL injection.
 
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -25,28 +24,34 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Comment - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule is merged into the original rule "SQLi - Comment" (ID: <RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
-      </td>
-      <td>N/A</td>
-      <td>SQLi - Comparison - Beta</td>
-      <td>Log</td>
-      <td>Block</td>      
-      <td>This rule is merged into the original rule "SQLi - Comparison" (ID: <RuleID id="8166da327a614849bfa29317e7907480" />)</td>
-   </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comment - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Comment" (ID:{" "}
+				<RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule is merged into the original rule "SQLi - Comparison" (ID:{" "}
+				<RuleID id="8166da327a614849bfa29317e7907480" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-01-26-waf-release.mdx b/src/content/changelog/waf/2026-01-26-waf-release.mdx
index cfb420d9e2809ad..030699a9d584923 100644
--- a/src/content/changelog/waf/2026-01-26-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-26-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for denial-of-service attempts t
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="aaede80b4d414dc89c443cea61680354" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="930020d567684f19b05fb35b349edbc6" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
-      <td>N/A</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-  </tbody>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="aaede80b4d414dc89c443cea61680354" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="930020d567684f19b05fb35b349edbc6" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-02-02-waf-release.mdx b/src/content/changelog/waf/2026-02-02-waf-release.mdx
index 00ed3826f072eeb..cb989e8324478d9 100644
--- a/src/content/changelog/waf/2026-02-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-02-02-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for CVE-2025-64459 and CVE-2025-
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7a47683eacce4abd870ab2c630698ff3" />
-      </td>
-      <td>N/A</td>
-      <td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
-      </td>
-      <td>N/A</td>
-      <td>Django SQLI - CVE:CVE-2025-64459</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-  </tr>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="8f0d5c98bd24460a9305a1558d667511" />
-      </td>
-      <td>N/A</td>
-      <td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
-      <td>Block</td>
-      <td>Block</td>
-      <td>Rule metadata description refined. Detection unchanged.</td>
-  </tr>
-  </tbody>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7a47683eacce4abd870ab2c630698ff3" />
+			</td>
+			<td>N/A</td>
+			<td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
+			</td>
+			<td>N/A</td>
+			<td>Django SQLI - CVE:CVE-2025-64459</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="8f0d5c98bd24460a9305a1558d667511" />
+			</td>
+			<td>N/A</td>
+			<td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
+			<td>Block</td>
+			<td>Block</td>
+			<td>Rule metadata description refined. Detection unchanged.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-02-waf-release.mdx b/src/content/changelog/waf/2026-03-02-waf-release.mdx
index 5e417a5421f9c40..34e9cc77d392db9 100644
--- a/src/content/changelog/waf/2026-03-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-02-waf-release.mdx
@@ -8,7 +8,6 @@ import { RuleID } from "~/components";
 
 This week's release introduces new detections for vulnerabilities in SmarterTools SmarterMail (CVE-2025-52691 and CVE-2026-23760), alongside improvements to an existing Command Injection (nslookup) detection to enhance coverage.
 
-
 **Key Findings**
 
 - CVE-2025-52691: SmarterTools SmarterMail mail server is vulnerable to Arbitrary File Upload, allowing an unauthenticated attacker to upload files to any location on the mail server, potentially enabling remote code execution.
@@ -62,8 +61,10 @@ Successful exploitation of these SmarterMail vulnerabilities could lead to full
 			<td>Command Injection - Nslookup - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>This rule is merged into the original rule "Command Injection - Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)</td>
+			<td>
+				This rule is merged into the original rule "Command Injection -
+				Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)
+			</td>
 		</tr>
-          
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
index 37ee704eb668c95..82b11cdd62ca859 100644
--- a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
@@ -36,11 +36,13 @@ Successful exploitation of Ivanti EPMM vulnerability allows unauthenticated remo
 				<RuleID id="5ae86a9bda0c41dbb905132f796ea2f6" />
 			</td>
 			<td>N/A</td>
-			<td>Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340</td>
+			<td>
+				Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340
+			</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr> 
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
diff --git a/src/content/changelog/waf/2026-03-23-waf-release.mdx b/src/content/changelog/waf/2026-03-23-waf-release.mdx
index 4b55ee8e500a59b..ca8664ddf6e1b0f 100644
--- a/src/content/changelog/waf/2026-03-23-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-23-waf-release.mdx
@@ -12,10 +12,6 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
-
-
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -28,50 +24,58 @@ This week's release focuses on new improvements to enhance coverage.
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - URI Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - Header Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="155bb67d1061479e995a38510677175f" />
-      </td>
-      <td>N/A</td>
-      <td>Command Injection - Generic 9 - Body Vector</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
-      </td>
-      <td>N/A</td>
-      <td>PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132" (ID: <RuleID id="0f2da91cec674eb58006929e824b817c" />)</td>
-    </tr>
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - URI Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - Header Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="155bb67d1061479e995a38510677175f" />
+			</td>
+			<td>N/A</td>
+			<td>Command Injection - Generic 9 - Body Vector</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
+			</td>
+			<td>N/A</td>
+			<td>
+				PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File
+				Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "PHP, vBulletin, jQuery
+				File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206,
+				CVE:CVE-2019-17132" (ID:{" "}
+				<RuleID id="0f2da91cec674eb58006929e824b817c" />)
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-30-waf-release.mdx b/src/content/changelog/waf/2026-03-30-waf-release.mdx
index 1bf0c23738bd886..7bb86d5b78461dc 100644
--- a/src/content/changelog/waf/2026-03-30-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-30-waf-release.mdx
@@ -30,61 +30,63 @@ Successful exploitation of the Fortinet and Magento vulnerabilities could allow
 			<th>Comments</th>
 		</tr>
 	</thead>
-    <tbody>
-	<tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="4f7d513cea424c2a853881982f7f95e9" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - Body</td>
-      <td>Log</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-   </tr>
-   <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="60d023f3be414d379428add3319731a4" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - Header - Form</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-   </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
-      </td>
-      <td>N/A</td>
-      <td>Generic Rules - Parameter Pollution - URI</td>
-      <td>Log</td>
-      <td>Disabled</td>      
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="ab8a96ed13034d56a81a79e570a36147" />
-      </td>
-      <td>N/A</td>
-      <td>Magento 2 - Unrestricted file upload</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
-      </td>
-      <td>N/A</td>
-      <td>Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>    
-  </tbody>    
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="4f7d513cea424c2a853881982f7f95e9" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - Body</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="60d023f3be414d379428add3319731a4" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - Header - Form</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
+			</td>
+			<td>N/A</td>
+			<td>Generic Rules - Parameter Pollution - URI</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="ab8a96ed13034d56a81a79e570a36147" />
+			</td>
+			<td>N/A</td>
+			<td>Magento 2 - Unrestricted file upload</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-15-waf-release.mdx b/src/content/changelog/waf/2026-04-15-waf-release.mdx
index 48b63b279a71a7e..8027bd3284ff60d 100644
--- a/src/content/changelog/waf/2026-04-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-15-waf-release.mdx
@@ -21,7 +21,7 @@ This week's release introduces a new detection for a critical Remote Code Execut
 Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code, gain administrative control over network management infrastructure, or trigger server-side resource exhaustion. Administrators are strongly encouraged to apply official vendor updates.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -31,73 +31,81 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
-      </td>
-      <td>N/A</td>
-      <td>Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
-      </td>
-      <td>N/A</td>
-      <td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>   
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
-      </td>
-      <td>N/A</td>
-      <td>Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection.</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
-      </td>
-      <td>N/A</td>
-      <td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This rule has been merged into the original rule "React Server - DOS - CVE:CVE-2026-23864 - 1" (ID: <RuleID id="aaede80b4d414dc89c443cea61680354" />)</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
-      </td>
-      <td>N/A</td>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
+			</td>
+			<td>N/A</td>
+			<td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
+			</td>
+			<td>N/A</td>
+			<td>
+				Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057
+			</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
+			</td>
+			<td>N/A</td>
+			<td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This rule has been merged into the original rule "React Server - DOS -
+				CVE:CVE-2026-23864 - 1" (ID:{" "}
+				<RuleID id="aaede80b4d414dc89c443cea61680354" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
+			</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI (beta)</td>
-      <td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
-      <td>
-        <RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
-      </td>
-      <td>N/A</td>
-      <td>XSS, HTML Injection - Embed Tag  - URI (beta)</td>
 			<td>N/A</td>
-      <td>Disabled</td>
-      <td>This is a new detection.</td>
-    </tr>
-</tbody>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
+			</td>
+			<td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag - URI (beta)</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-21-waf-release.mdx b/src/content/changelog/waf/2026-04-21-waf-release.mdx
index d31b75ad221a27b..5a538a69976bfd7 100644
--- a/src/content/changelog/waf/2026-04-21-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-21-waf-release.mdx
@@ -23,7 +23,7 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -33,285 +33,266 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+	</thead>
+	<tbody>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="ff8df24181aa4573a81be531ee159e2e" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Command Injection - Generic 8 - uri</td>
-      <td>Log</td>
-      <td>Block</td>
-      <td>This is a new detection. Previous description was "Command Injection - Generic 8 - uri - Beta"</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. Previous description was "Command Injection -
+				Generic 8 - uri - Beta"
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9429b63c137247faadeb8a29a15308cf" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Command Injection - Generic 8 - body - Beta</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Command Injection - Generic 8 - body" (ID:{" "}
-				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />). The rule previously known as "Command Injection - Generic 8" is now renamed to "Command Injection - Generic 8 - body".
+				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />
+				). The rule previously known as "Command Injection - Generic 8" is now
+				renamed to "Command Injection - Generic 8 - body".
 			</td>
-    </tr>		
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="85aaf5db9e0c4237b87e837e958047ed" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
+			<td>Log</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"MySQL - SQLi - Executable Comment - Body" (ID:{" "}
-				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL - SQLi - Executable Comment - Body".
+				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously
+				known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL -
+				SQLi - Executable Comment - Body".
 			</td>
-    </tr>
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d19cd574c4644952881a6f3a582cc559" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="407f9ec8a17348dfba3b9450a16639d3" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - URI</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d07e6dbf15664b99b37b0d2544f24211" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Magento 2 - Unrestricted file upload - 2</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>     
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="26ef21cb197b44fc8a98b7cebf170a17" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>Apache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr> 
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7f7bc3d28a8e43bf97bd15d68c2ac1a7" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - Beta</td>
-      <td>Log</td>
-      <td>Block</td>
+			<td>Log</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Sleep Function" (ID:{" "}
 				<RuleID id="2c333735f7b24566b17cb64ef77e8d54" />)
 			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3872e5638bdf4bf0943a80394dacaeb8" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>   
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="bebce8fadfa94ccab09eb74fed4c9ece" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Sleep Function - URI</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7a40eed5a8654a50a2598a821dfa64df" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - uri</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="15c6b2ce033949b2a1a9f9454c62e2e7" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - header</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="fc9d800b7a724181af8d5650aab28ea1" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing - body</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Probing" (ID: <RuleID id="2c20b5e8684043f48620ff77b4026c88" />)
 			</td>
-    </tr>  
-    <tr>
-      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - Probing 2 </td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This rule had duplicate detection logic and has been deprecated.
-			</td>
-    </tr> 
-    <tr>
-	      <td>Cloudflare Managed Ruleset</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This rule had duplicate detection logic and has been deprecated.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="f1771273700342758e73cf16d7aa0008" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - UNION in MSSQL - Body</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
 			<td>
-				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL" (ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains updated rule logic.
+				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL"
+				(ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains
+				updated rule logic.
 			</td>
-    </tr> 
-    <tr> 
-	      <td>Cloudflare Managed Ruleset</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - UNION - 3</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This rule had duplicate detection logic and has been deprecated.
-			</td>
-    </tr> 
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This rule had duplicate detection logic and has been deprecated.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
 			</td>
-      <td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag  - URI</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag - URI</td>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2635275641bf44d4bad6a2e170282f38" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Embed Tag - Headers</td>
-      <td>Log</td>
-      <td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="b3d033ea9f364574b0a2ec4223f4d718" />
 			</td>
-      <td>N/A</td>
-			<td>XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers</td>
-      <td>Log</td>
-      <td>Disabled</td>
+			<td>N/A</td>
 			<td>
-				This is a new detection. 
+				XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers
 			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="76c37816ef5c4997ab2080a36978def1" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - Headers</td>
-      <td>Log</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>  
-      <tr>
-      <td>Cloudflare Managed Ruleset</td>
+			<td>Log</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
 			</td>
-      <td>N/A</td>
+			<td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI</td>
-      <td>Disabled</td>
-      <td>Disabled</td>
-			<td>
-				This is a new detection. 
-			</td>
-    </tr>           
-</tbody>
+			<td>Disabled</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-27-waf-release.mdx b/src/content/changelog/waf/2026-04-27-waf-release.mdx
index 0693afdefc19da2..cff93d4886276d7 100644
--- a/src/content/changelog/waf/2026-04-27-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-27-waf-release.mdx
@@ -12,14 +12,12 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
-
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -29,7 +27,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -39,188 +37,198 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
-				This is a new detection.  This rule is merged into the original rule
+				This is a new detection. This rule is merged into the original rule
 				"PostgreSQL - SQLi - COPY - Body (ID:{" "}
-				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />). The rule previously known as "PostgreSQL - SQLi - COPY" is now renamed to "PostgreSQL - SQLi - COPY - Body".
+				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />
+				). The rule previously known as "PostgreSQL - SQLi - COPY" is now
+				renamed to "PostgreSQL - SQLi - COPY - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="71d133c374d94559aa9fdf042903de89" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9f1b1b7fd28a401b9d5c172d1036cfa6" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>  
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="8e40416659334b8ba789365755ff389e" />
 			</td>
-   			<td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR MAKE_SET/ELT - Body" (ID:{" "}
-				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
+				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />
+				). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now
+				renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="1e0d4372ee1e41b9804b2d5c346487f9" />
 			</td>
-   			<td>N/A</td>
+			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d2c961a164a64cf6b871c9511ac6ceca" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="4dacc0e6f32d4c5da3c2293edd471337" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Common Patterns - Body" (ID:{" "}
-				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />). The rule previously known as "SQLi - Common Patterns" is now renamed to "SQLi - Common Patterns - Body".
+				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />
+				). The rule previously known as "SQLi - Common Patterns" is now renamed
+				to "SQLi - Common Patterns - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="53a374379f2e41e9934791c1975c07b7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9efedebfc371443f9fe7308605b1b06b" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d53a791496d64700870334f4dd0ba3c7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Equation - Body" (ID:{" "}
-				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />). The rule previously known as "SQLi - Equation" is now renamed to "SQLi - Equation - Body".
+				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />
+				). The rule previously known as "SQLi - Equation" is now renamed to
+				"SQLi - Equation - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46efbd3496e64c3f902ad33d3d1c2384" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46b937649a424b7ead90f6d0e1149ea6" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="04d9182545f54ba8a4fa29fe205adbb0" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR Digit Operator Digit - Body" (ID:{" "}
-				<RuleID id="762dd334ed0b4273816e3ff13893c564" />). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
+				<RuleID id="762dd334ed0b4273816e3ff13893c564" />
+				). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is
+				now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="a24e7c15503948bc8766481aad2abbaa" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - AND/OR Digit Operator Digit - Headers</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-        </tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="a24e7c15503948bc8766481aad2abbaa" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - AND/OR Digit Operator Digit - Headers</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="0c55eb362df64f92a85aa46753acbc0d" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="18c9879b7e184c559d23c1652b45a97d" />
-            </td>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="18c9879b7e184c559d23c1652b45a97d" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Beta</td>
 			<td>Log</td>
@@ -228,22 +236,24 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Benchmark Function - Body" (ID:{" "}
-				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />). The rule previously known as "SQLi - Benchmark Function" is now renamed to "SQLi - Benchmark Function - Body".
+				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />
+				). The rule previously known as "SQLi - Benchmark Function" is now
+				renamed to "SQLi - Benchmark Function - Body".
 			</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2adbc36c52324efcb4681b829889aadc" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>		
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="69564af3bc54406080deed72491b28e9" />
 			</td>
@@ -254,7 +264,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="94b1646f0b0b46ec9b96f7742aa649de" />
 			</td>
@@ -265,151 +275,166 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Comparison - Body" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />). The rule previously known as "SQLi - Comparison" is now renamed to "SQLi - Comparison - Body".
-			</td>
-		</tr>
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="455ce87681bd4200bf53456c39e3e013" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - Comparison - Headers</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-		</tr>	
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="8152816062ed47f69be0f907f4bdb492" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - Comparison - URI</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection.</td>
-		</tr>
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - String Concatenation - Body - Beta</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection. This rule is merged into the original rule "SQLi - String Concatenation - Headers" (ID:{" "}
-				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />).The rule previously known as "SQLi - String Concatenation - Headers" is now renamed to "SQLi - String Concatenation - Body". </td>
-		</tr>	
-        <tr>
+				<RuleID id="8166da327a614849bfa29317e7907480" />
+				). The rule previously known as "SQLi - Comparison" is now renamed to
+				"SQLi - Comparison - Body".
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="455ce87681bd4200bf53456c39e3e013" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - Headers</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
-            </td>
-            <td>N/A</td>
+			<td>
+				<RuleID id="8152816062ed47f69be0f907f4bdb492" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - Comparison - URI</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Concatenation - Body - Beta</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. This rule is merged into the original rule
+				"SQLi - String Concatenation - Headers" (ID:{" "}
+				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />
+				).The rule previously known as "SQLi - String Concatenation - Headers"
+				is now renamed to "SQLi - String Concatenation - Body".{" "}
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
+			</td>
+			<td>N/A</td>
 			<td>SQLi - String Concatenation - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
-			<td>This is a new detection.(Former Id was{" "}
-				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)</td>
-		</tr>		
-		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
-            </td>
-            <td>N/A</td>
-            <td>SQLi - String Concatenation - URI</td>
-            <td>Log</td>
-            <td>Block</td>
-            <td>This is a new detection. (Former Id was{" "}
-				<RuleID id="bd19397228404b85aa3797238fae8c84" />)</td>
-		</tr>	
+			<td>Block</td>
+			<td>
+				This is a new detection.(Former Id was{" "}
+				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)
+			</td>
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
-            </td>
-            <td>N/A</td>
+			<td>
+				<RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
+			</td>
+			<td>N/A</td>
+			<td>SQLi - String Concatenation - URI</td>
+			<td>Log</td>
+			<td>Block</td>
+			<td>
+				This is a new detection. (Former Id was{" "}
+				<RuleID id="bd19397228404b85aa3797238fae8c84" />)
+			</td>
+		</tr>
+		<tr>
+			<td>Cloudflare Managed Ruleset</td>
+			<td>
+				<RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
+			</td>
+			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - SELECT Expression - Body" (ID:{" "}
-				<RuleID id="00da180570d34b5bae2121acd0023a36" />). The rule previously known as "SQLi - SELECT Expression" is now renamed to "SQLi - SELECT Expression - Body".
+				<RuleID id="00da180570d34b5bae2121acd0023a36" />
+				). The rule previously known as "SQLi - SELECT Expression" is now
+				renamed to "SQLi - SELECT Expression - Body".
 			</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="4073f7b575ff45dfb7621b43630bb223" />
-            </td>
+			<td>
+				<RuleID id="4073f7b575ff45dfb7621b43630bb223" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
-            </td>
+			<td>
+				<RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
-            </td>
+			<td>
+				<RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Beta</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - ORD and ASCII- Body" (ID:{" "}
-				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />). The rule previously known as "SQLi - ORD and ASCII" is now renamed to "SQLi - ORD and ASCII- Body".
+				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />
+				). The rule previously known as "SQLi - ORD and ASCII" is now renamed to
+				"SQLi - ORD and ASCII- Body".
 			</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
-            </td>
+			<td>
+				<RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - URI</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-            <td>
-                <RuleID id="60704f5c5513425c94cf77031d0906b6" />
-            </td>
+			<td>
+				<RuleID id="60704f5c5513425c94cf77031d0906b6" />
+			</td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Headers</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>	
+		</tr>
 		<tr>
-        	<td>Cloudflare Managed Ruleset</td>
+			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="700613b191d3479ea2782b4e9fe4eff5" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Destructive Operations</td>
 			<td>Log</td>
-            <td>Block</td>
+			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>					
+		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
index 8e8330ad016a2e7..a13aa934882650b 100644
--- a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows unauthenticated attackers to bypass middleware or
 We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 				<RuleID id="1de95bf6d6374e1099854278e77e4a53" />
 			</td>
 			<td>N/A</td>
-			<td>Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575</td>
-			<td>N/A</td>
-			<td>Disabled</td>
 			<td>
-				This is a new detection.
+				Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575
 			</td>
+			<td>N/A</td>
+			<td>Disabled</td>
+			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-11-waf-release.mdx b/src/content/changelog/waf/2026-05-11-waf-release.mdx
index 043c71508d1a2ef..ab5ae2ac0485b0a 100644
--- a/src/content/changelog/waf/2026-05-11-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-11-waf-release.mdx
@@ -10,14 +10,12 @@ import { RuleID } from "~/components";
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
-
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
-
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -41,7 +39,8 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Remote Code Execution - Java Deserialization" (ID:{" "}
-				<RuleID id="36b0532eb3c941449afed2d3744305c4" />).
+				<RuleID id="36b0532eb3c941449afed2d3744305c4" />
+				).
 			</td>
 		</tr>
 	</tbody>
diff --git a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
index 6699189c3e6941d..044ad5768701d6e 100644
--- a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows remote attackers to trigger a heap buffer overflo
 We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, avoid `rewrite` directives with `?` in the replacement string followed by `set` or `if` referencing capture groups.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 				<RuleID id="2013e3e58efe4b79a26e214f7e52be73" />
 			</td>
 			<td>N/A</td>
-			<td>nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945</td>
-			<td>N/A</td>
-			<td>Block</td>
 			<td>
-				This is a new detection.
+				nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945
 			</td>
+			<td>N/A</td>
+			<td>Block</td>
+			<td>This is a new detection.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -51,9 +51,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<td>nginx - Remote Code Execution - Heap Spray - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This is a new detection.
-			</td>
+			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-20-waf-release.mdx b/src/content/changelog/waf/2026-05-20-waf-release.mdx
index f6bd07a5a23d740..e26381409165dae 100644
--- a/src/content/changelog/waf/2026-05-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-20-waf-release.mdx
@@ -15,7 +15,7 @@ import { RuleID } from "~/components";
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-  <thead>
+	<thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-  </thead>
+	</thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,9 +37,11 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>Block</td>
 			<td>
-				This rule is merged into the original rule "Sitecore - Cache Poisoning - CVE:CVE-2025-53693" (ID:{" "}
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />).
+				This rule is merged into the original rule "Sitecore - Cache Poisoning -
+				CVE:CVE-2025-53693" (ID:{" "}
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+				).
 			</td>
 		</tr>
 	</tbody>
-</table>
\ No newline at end of file
+</table>
diff --git a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
index c086c1b5689e944..e6847cc885baddb 100644
--- a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
+++ b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
@@ -22,8 +22,8 @@ For more information, refer to [Navigation Types](/web-analytics/data-metrics/di
 
 ### Key benefits
 
-* **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
-* **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
+- **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
+- **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
 
 ### Analyze navigation types in the Cloudflare dashboard
 
diff --git a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
index 1dbfdc154f12e70..023c0a2b71c0c0c 100644
--- a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
@@ -13,13 +13,14 @@ Get started with the new models at `@cf/openai/gpt-oss-120b` and `@cf/openai/gpt
 Check out the [blog](https://blog.cloudflare.com/openai-gpt-oss-on-workers-ai) for more details about the new models, and the [`gpt-oss-120b`](/workers-ai/models/gpt-oss-120b) and [`gpt-oss-20b`](/workers-ai/models/gpt-oss-20b) model pages for more information about pricing and context windows.
 
 ## Responses API
+
 If you call the model through:
+
 - Workers Binding, it will accept/return Responses API – `env.AI.run(“@cf/openai/gpt-oss-120b”)`
 - REST API on `/run` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/run/@cf/openai/gpt-oss-120b`
 - REST API on new `/responses` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses`
 - REST API for OpenAI Compatible endpoint, it will return Chat Completions (coming soon) – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/chat/completions`
 
-
 ```
 curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses \
   -H "Content-Type: application/json" \
@@ -39,7 +40,9 @@ curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses
 ```
 
 ## Code Interpreter
+
 The model is natively trained to support stateful code execution, and we've implemented support for this feature using our [Sandbox SDK](https://github.com/cloudflare/sandbox-sdk) and [Containers](https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/). Cloudflare's Developer Platform is uniquely positioned to support this feature, so we're very excited to bring our products together to support this new use case.
 
 ## Web Search (coming soon)
+
 We are working to implement Web Search for the model, where users can bring their own Exa API Key so the model can browse the Internet.
diff --git a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
index 21359bd2975b689..4a63321c26bcb30 100644
--- a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
@@ -11,6 +11,7 @@ New state-of-the-art models have landed on Workers AI! This time, we're introduc
 As well, we're introuding a new turn detection model that enables you to detect when someone is done speaking — useful for building voice agents!
 
 Read the [blog](https://blog.cloudflare.com/workers-ai-partner-models) for more details and check out some of the new models on our platform:
+
 - [`@cf/deepgram/aura-1`](/workers-ai/models/aura-1) is a text-to-speech model that allows you to input text and have it come to life in a customizable voice
 - [`@cf/deepgram/nova-3`](/workers-ai/models/nova-3) is speech-to-text model that transcribes multilingual audio at a blazingly fast speed
 - [`@cf/pipecat-ai/smart-turn-v2`](/workers-ai/models/smart-turn-v2) helps you detect when someone is done speaking
@@ -54,4 +55,4 @@ async def text_to_speech():
 
 if __name__ == "__main__":
     asyncio.run(text_to_speech())
-```
\ No newline at end of file
+```
diff --git a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
index 27cdbf6ba1773e1..f19b116401280e9 100644
--- a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
+++ b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
@@ -12,9 +12,10 @@ We're excited to be a launch partner alongside [Google](https://developers.googl
 Now you can leverage EmbeddingGemma directly through AI Search for your RAG pipelines. EmbeddingGemma's multilingual capabilities make it perfect for global applications that need to understand and retrieve content across different languages with exceptional accuracy.
 
 To use EmbeddingGemma for your AI Search projects:
+
 1. Go to **Create** in the [AI Search dashboard](https://dash.cloudflare.com/?to=/:account/ai/ai-search)
 2. Follow the setup flow for your new RAG instance
 3. In the **Generate Index** step, open up **More embedding models** and select `@cf/google/embeddinggemma-300m` as your embedding model
 4. Complete the setup to create an AI Search
 
-Try it out and let us know what you think!
\ No newline at end of file
+Try it out and let us know what you think!
diff --git a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
index 479a67c4a458f78..0f6f06d216ab8ea 100644
--- a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
+++ b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
@@ -17,7 +17,9 @@ export default {
 		// Perform application logic in Workers here
 
 		// Sample call to an internal API running on ECS in AWS using the binding
-		const response = await env.AWS_VPC_ECS_API.fetch("https://internal-host.example.com");
+		const response = await env.AWS_VPC_ECS_API.fetch(
+			"https://internal-host.example.com",
+		);
 
 		// Additional application logic in Workers
 		return new Response();
diff --git a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
index ad672d1184483df..cd1650bd65edb75 100644
--- a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
+++ b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
@@ -8,13 +8,13 @@ date: 2025-02-07 00:00:00 UTC
 
 ![Import repo or choose template](~/assets/images/workers/choose-template-import-repo.png)
 
-You can now create a Worker by: 
-* **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker. 
-* **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker. 
+You can now create a Worker by:
 
-With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker. 
+- **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker.
+- **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker.
 
-To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
+With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker.
 
-These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9). 
+To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
 
+These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9).
diff --git a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
index f651164ee14bfd0..5b44d0f80ee3d23 100644
--- a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
+++ b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
@@ -47,4 +47,4 @@ CPU time was limited.
 For more information on the updates limits, see the documentation on [Wrangler configuration for `cpu_ms`](/workers/wrangler/configuration/#limits)
 and on [Workers CPU time limits](/workers/platform/limits/#cpu-time).
 
-For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
\ No newline at end of file
+For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
diff --git a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
index d24d77883df382f..2b8b4d848965a55 100644
--- a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
@@ -1,28 +1,28 @@
 ---
 title: Deploy a Workers application in seconds with one-click
-description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project. 
+description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project.
 products:
   - workers
 date: 2025-04-08 00:00:00 UTC
 ---
-You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project! 
+
+You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project!
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/saas-admin-template)
 
+The Deploy to Cloudflare button:
 
-The Deploy to Cloudflare button: 
-1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
-2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
+1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing.
+2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment.
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 
-
-To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL: 
+To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL:
 
 ```md
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=<YOUR_GIT_REPO_URL>)
 ```
 
-Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers. 
+Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers.
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
index b0b15c17427b454..a03418408567548 100644
--- a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
+++ b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -7,7 +7,7 @@ date: 2025-04-09
 hidden: false
 ---
 
-import { WranglerConfig } from "~/components"
+import { WranglerConfig } from "~/components";
 
 The [Workers Observability dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](/workers/observability/logs/workers-logs).
 
@@ -16,6 +16,7 @@ The **Overview** tab shows logs from all your Workers in one place. The **Invoca
 ![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png)
 
 The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:
+
 - Which paths are experiencing the most 5XX errors?
 - What is the wall time distribution by status code for my Worker?
 - What are the slowest requests, and where are they coming from?
@@ -30,6 +31,7 @@ The Query Builder can use any field that you store in your logs as a key to visu
 [Workers Logs](/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.
 
 We've introduced a number of changes during our beta period, including:
+
 - Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
 - Performance improvements to ensure no adverse impact
 - Public [API endpoints](https://developers.cloudflare.com/api/resources/workers/subresources/observability/) for broader consumption
diff --git a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
index 9361cb8dd0b783c..b452371c6b814cf 100644
--- a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
+++ b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
@@ -52,4 +52,4 @@ npx wrangler dev --test-scheduled
 curl "http://localhost:8787/cdn-cgi/handler/scheduled?cron=*+*+*+*+*"
 ```
 
-Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
\ No newline at end of file
+Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
diff --git a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
index 1adf754ef15b998..66b3abe85c67f76 100644
--- a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
+++ b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
@@ -84,4 +84,4 @@ Then test your new Durable Object locally by running `wrangler dev`:
 npx wrangler dev
 ```
 
-Consult the [Durable Objects documentation](/durable-objects/) for more details.
\ No newline at end of file
+Consult the [Durable Objects documentation](/durable-objects/) for more details.
diff --git a/src/content/changelog/workers/2025-06-05-open-next-size.mdx b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
index dc09195d36386df..f812ab669e4ae81 100644
--- a/src/content/changelog/workers/2025-06-05-open-next-size.mdx
+++ b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
@@ -15,4 +15,4 @@ This means that users will now see a decrease from 14 to 8MiB (2.3 to 1.6MiB gzi
 Users only need to update to the latest version of `@opennextjs/cloudflare` to automatically benefit from these improvements.
 
 Note that we published [CVE-2005-6087](https://github.com/opennextjs/opennextjs-cloudflare/security/advisories/GHSA-rvpw-p7vw-wj3m) for a SSRF vulnerability in the `@opennextjs/cloudflare` package.
-The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one. 
+The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one.
diff --git a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
index cdfb5847ef6dfaf..09e28a32e4a37af 100644
--- a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
+++ b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
@@ -17,8 +17,8 @@ These preview URLs are named after your branch and are posted as a comment to ea
 
 Each comment includes **two preview URLs** as shown above:
 
-* **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
-* **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
+- **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
+- **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
 
 ## How it works
 
@@ -39,7 +39,7 @@ wrangler versions upload --preview-alias staging
 
 ## Limitations while in beta
 
-* Only available on the **workers.dev** subdomain (custom domains not yet supported)
-* Requires **Wrangler v4.21.0+**
-* Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
-* Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
+- Only available on the **workers.dev** subdomain (custom domains not yet supported)
+- Requires **Wrangler v4.21.0+**
+- Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
+- Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
diff --git a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
index 69b92f1517e3f97..62563705d8ffbf1 100644
--- a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
+++ b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
@@ -1,15 +1,17 @@
 ---
 title: Increased disk space for Workers Builds
-description: Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
+description:
+  Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
   - workers
 date: 2025-08-04T01:00:00Z
 ---
-As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans. 
+
+As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans.
 
 This provides more space for larger projects, dependencies, and build artifacts while improving overall build reliability.
 
 | Metric     | Free Plan | Paid Plans |
-|------------|-----------|------------|
+| ---------- | --------- | ---------- |
 | Disk Space | 20 GB     | 20 GB      |
 
 All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including CPU, memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
index ec55122dca6b4e3..38902472bf8ef79 100644
--- a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
+++ b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
@@ -40,7 +40,7 @@ export default {
 		// Background task that should complete even after response is sent
 		cleanupTempData(env.KV_NAMESPACE);
 		return new Response("Hello, World!");
-	}
+	},
 };
 
 function cleanupTempData(kvNamespace) {
diff --git a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
index 4b869cc6a72861c..ac79e16b37b4196 100644
--- a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
+++ b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
@@ -19,7 +19,7 @@ Now, Cloudflare automatically truncates long branch names and appends a unique h
 - **Hash generation**: The hash is derived from the full branch name to ensure uniqueness
 - **Stable URLs**: The same branch always generates the same hash across all commits
 
-## Requirements and compatibility 
+## Requirements and compatibility
 
 - **Wrangler 4.30.0 or later**: This feature requires updating to wrangler@4.30.0+
-- **No configuration needed**: Works automatically with existing preview URL setups
\ No newline at end of file
+- **No configuration needed**: Works automatically with existing preview URL setups
diff --git a/src/content/changelog/workers/2025-08-11-messagechannel.mdx b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
index b73740d15413afb..c6fc102f02133c4 100644
--- a/src/content/changelog/workers/2025-08-11-messagechannel.mdx
+++ b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
@@ -17,10 +17,10 @@ using the `no_expose_global_message_channel` compatibility flag.
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log('Received message:', event.data);
+	console.log("Received message:", event.data);
 };
 
-port2.postMessage('Hello from port2!');
+port2.postMessage("Hello from port2!");
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -29,13 +29,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-* Transfer lists are currently not supported. This means that you will not be able to transfer
+- Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-	are errors serializing or deserializing the message data. Instead, the error will be thrown when
-	the `postMessage` method is called on the sending port.
-* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+  are errors serializing or deserializing the message data. Instead, the error will be thrown when
+  the `postMessage` method is called on the sending port.
+- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
index c3da28c859aaa68..63d4feab2b544fb 100644
--- a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
+++ b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
@@ -34,4 +34,4 @@ To keep using the old-style handlers, you can specify the `disable_python_no_glo
 
 </WranglerConfig>
 
-Consult the [Python Workers documentation](/workers/languages/python/) for more details.
\ No newline at end of file
+Consult the [Python Workers documentation](/workers/languages/python/) for more details.
diff --git a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
index 71100f87446e32c..0665a23c274b592 100644
--- a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
+++ b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
@@ -90,20 +90,16 @@ const scriptContent = `
   };
 `;
 
-client.workers.scripts.versions.create('my-worker', {
-  account_id: '123456789',
-  metadata: {
-    main_module: 'my-worker.mjs',
-  },
-  files: [
-    await toFile(
-      Buffer.from(scriptContent),
-      'my-worker.mjs',
-      {
-        type: "application/javascript+module",
-      }
-    )
-  ]
+client.workers.scripts.versions.create("my-worker", {
+	account_id: "123456789",
+	metadata: {
+		main_module: "my-worker.mjs",
+	},
+	files: [
+		await toFile(Buffer.from(scriptContent), "my-worker.mjs", {
+			type: "application/javascript+module",
+		}),
+	],
 });
 ```
 
@@ -115,19 +111,20 @@ Previously when creating a KV value like this:
 
 ```js
 await cf.kv.namespaces.values.update("my-kv-namespace", "key1", {
-  account_id: "123456789",
-  metadata: "my metadata",
-  value: JSON.stringify({
-    hello: "world"
-  })
+	account_id: "123456789",
+	metadata: "my metadata",
+	value: JSON.stringify({
+		hello: "world",
+	}),
 });
 ```
 
 ...and recalling it in your Worker like this:
+
 ```ts
-const value = await c.env.KV.get<{hello: string}>("key1", "json");
+const value = await c.env.KV.get<{ hello: string }>("key1", "json");
 ```
 
-You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}` 
+You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}`
 
 This is fixed in cloudflare-typescript 4.5.0 and will be fixed in cloudflare-python 4.4.0.
diff --git a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
index 26a69c93645b1c1..edafaed88b57a69 100644
--- a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
+++ b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
@@ -1,9 +1,9 @@
 ---
-title: 'Workers Static Assets: Corrected handling of double slashes in redirect rule paths'
+title: "Workers Static Assets: Corrected handling of double slashes in redirect rule paths"
 description: Corrected handling of double slashes in redirect rule paths
 date: 2025-08-15
 ---
- 
-[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed. 
+
+[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed.
 
 If you're serving Static Assets with a `_redirects` file containing a rule like `/ja/* /:splat`, paths with double slashes were previously misinterpreted as external URLs. For example, visiting `/ja//example.com` would incorrectly redirect to `https://example.com` instead of `/example.com` on your domain. This has been fixed and double slashes now correctly resolve as local paths. Note: [Cloudflare Pages](/pages/) was not affected by this issue.
diff --git a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
index 607ca9dbee7a667..bf358c54fd5a98d 100644
--- a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
+++ b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
@@ -10,8 +10,8 @@ Wrangler's error screen has received several improvements to enhance your debugg
 
 The error screen now features a refreshed design thanks to [youch](https://www.npmjs.com/package/youch), with support for both light and dark themes, improved source map resolution logic that handles missing source files more reliably, and better error cause display.
 
-| Before | After (Light) | After (Dark) |
-|--------|---------------|--------------|
+| Before                                                                             | After (Light)                                                                                        | After (Dark)                                                                                       |
+| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
 | ![Old error screen](../../../assets/images/workers/changelog/old-error-screen.png) | ![New light theme error screen](../../../assets/images/workers/changelog/new-error-screen-light.png) | ![New dark theme error screen](../../../assets/images/workers/changelog/new-error-screen-dark.png) |
 
 Try it out now with `npx wrangler@latest dev` in your Workers project.
diff --git a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
index d5f72b78d505a8f..383e128922da73e 100644
--- a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
+++ b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
@@ -3,21 +3,22 @@ title: A new, simpler REST API for Cloudflare Workers (Beta)
 description: Simpler Workers API, SDK methods, and Terraform resources for directly managing Workers, Versions, and Deployments
 date: 2025-09-04
 ---
-You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
+
+You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
 
 This new API is supported in the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) and the [Cloudflare Typescript SDK](https://github.com/cloudflare/cloudflare-typescript), allowing platform teams to manage a Worker's infrastructure in Terraform, while development teams handle code deployments from a separate repository or workflow. We also designed this API with AI agents in mind, as a clear, predictable structure is essential for them to reliably build, test, and deploy applications.
 
 ### Try it out
+
 - [**New beta API endpoints**](/api/resources/workers/subresources/beta/)
 - [**Cloudflare TypeScript SDK v5.0.0**](https://github.com/cloudflare/cloudflare-typescript)
 - [**Cloudflare Go SDK v6.0.0**](https://github.com/cloudflare/cloudflare-go)
 - [**Terraform provider v5.9.0**](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs): [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) , [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version), and [`cloudflare_workers_deployments`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_deployment) resources.
 - See full examples in our [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 
-
 ## Before: Eight+ endpoints with mixed responsibilities
-![**Before**](~/assets/images/workers/platform/api-before.png)
 
+![**Before**](~/assets/images/workers/platform/api-before.png)
 
 The existing API was originally designed for simple, one-shot script uploads:
 
@@ -40,15 +41,17 @@ This API worked for creating a basic Worker, uploading all of its code, and depl
 
 - **Several endpoints implicitly created deployments**: Simple updates like adding a secret or changing a script's content would implicitly create a new version and immediately deploy it.
 
-- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities.  This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
+- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities. This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
 
 - **Scripts used names as primary identifiers**: This meant simple renames could turn into a risky migration, requiring you to create a brand new Worker and update every reference. If you were using Terraform, this could inadvertently destroy your Worker altogether.
 
 ## After: Three resources with clear boundaries
+
 ![**After**](~/assets/images/workers/platform/api-after.png)
-The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
+The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
 
 All endpoints now use simple JSON payloads, with script content embedded as `base64`-encoded strings -- a more consistent and reliable approach than the previous `multipart/form-data` format.
+
 - **Worker**: The parent resource representing your application. It has a stable UUID and holds persistent settings like `name`, `tags`, and `logpush`. You can now create a Worker to establish its identity and settings **before** any code is uploaded.
 
 - **Version**: An immutable snapshot of your code and its specific configuration, like bindings and `compatibility_date`. Creating a new version is a safe action that doesn't affect live traffic.
@@ -66,44 +69,52 @@ All endpoints now use simple JSON payloads, with script content embedded as `bas
 Workers are now standalone resources that can be created and configured without any code. Platform teams can provision Workers with the right settings, then hand them off to development teams for implementation.
 
 #### Example: Typescript SDK
+
 ```ts
 // Step 1: Platform team creates the Worker resource (no code needed)
 const worker = await client.workers.beta.workers.create({
-  name: "payment-service",
-  account_id: "...",
-  observability: {
-    enabled: true,
-  },
+	name: "payment-service",
+	account_id: "...",
+	observability: {
+		enabled: true,
+	},
 });
 
 // Step 2: Development team adds code and creates a version later
 const version = await client.workers.beta.workers.versions.create(worker.id, {
-  account_id: "...",
-  main_module: "worker.js",
-  compatibility_date: "$today",
-  bindings: [ /*...*/ ],
-  modules: [
-    {
-      name: "worker.js",
-      content_type: "application/javascript+module",
-      content_base64: Buffer.from(scriptContent).toString("base64"),
-    },
-  ],
+	account_id: "...",
+	main_module: "worker.js",
+	compatibility_date: "$today",
+	bindings: [
+		/*...*/
+	],
+	modules: [
+		{
+			name: "worker.js",
+			content_type: "application/javascript+module",
+			content_base64: Buffer.from(scriptContent).toString("base64"),
+		},
+	],
 });
 
 // Step 3: Deploy explicitly when ready
-const deployment = await client.workers.scripts.deployments.create(worker.name, {
-  account_id: "...",
-  strategy: "percentage",
-  versions: [
-    {
-      percentage: 100,
-      version_id: version.id,
-    },
-  ],
-});
-````
+const deployment = await client.workers.scripts.deployments.create(
+	worker.name,
+	{
+		account_id: "...",
+		strategy: "percentage",
+		versions: [
+			{
+				percentage: 100,
+				version_id: version.id,
+			},
+		],
+	},
+);
+```
+
 #### Example: Terraform
+
 If you use Terraform, you can now declare the Worker in your Terraform configuration and manage configuration outside of Terraform in your Worker's [`wrangler.jsonc` file](/workers/wrangler/configuration/) and deploy code changes using [Wrangler](/workers/wrangler/).
 
 ```tf
@@ -149,6 +160,7 @@ POST /workers/scripts/{script_name}/deployments
 ```
 
 ### Settings are clearly organized by scope
+
 Configuration is now logically divided: [**Worker settings**](/api/resources/workers/subresources/beta/subresources/workers/) (like `name` and `tags`) persist across all versions, while [**Version settings**](/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) (like `bindings` and `compatibility_date`) are specific to each code snapshot.
 
 ```sh
@@ -180,13 +192,15 @@ The `/workers/workers/` path now supports addressing a Worker by both its immuta
 GET /workers/workers/29494978e03748669e8effb243cf2515  # UUID (stable for automation)
 GET /workers/workers/payment-service                  # Name (convenient for humans)
 ```
+
 This dual approach means:
-  - Developers can use readable names for debugging.
-  - Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
-  - Terraform can rename Workers without destroying and recreating them.
 
+- Developers can use readable names for debugging.
+- Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
+- Terraform can rename Workers without destroying and recreating them.
 
 ## Learn more
+
 - [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 - [API documentation](/api/resources/workers/subresources/beta/)
 - [Versions and Deployments overview](/workers/configuration/versions-and-deployments/)
@@ -195,4 +209,4 @@ This dual approach means:
 
 - The pre-existing Workers REST API remains fully supported. Once the new API exits beta, we'll provide a migration timeline with ample notice and comprehensive migration guides.
 - Existing Terraform resources and SDK methods will continue to be fully supported through the current major version.
-- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
\ No newline at end of file
+- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
diff --git a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
index 8226df15cb8f922..08db5550e9f1847 100644
--- a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
+++ b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
@@ -1,19 +1,22 @@
 ---
 title: Increased vCPU for Workers Builds on paid plans
-description: Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
+description:
+  Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
   - workers
 date: 2025-09-18
 ---
-We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.  
+
+We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.
 
 These changes continue our focus on making [Workers Builds](/workers/ci-cd/builds/) faster and more reliable.
 
-| Metric     | Free Plan | Paid Plans |
-|------------|-----------|------------|
-| CPU |  2 vCPU  |  **4 vCPU**  |
+| Metric | Free Plan | Paid Plans |
+| ------ | --------- | ---------- |
+| CPU    | 2 vCPU    | **4 vCPU** |
 
 ## Performance Improvements
-- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs 
+
+- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs
 - **2x faster multi-threaded builds**: Tools like [esbuild](https://esbuild.github.io/) and [webpack](https://webpack.js.org/) can now utilize additional cores, delivering near-linear performance scaling
 
-All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
\ No newline at end of file
+All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
index ca46348805446ca..52947b26e2a263c 100644
--- a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
+++ b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
@@ -11,11 +11,13 @@ Deploying static site to Workers is now easier. When you run `wrangler deploy [d
 ## Before and after
 
 **Before:** Required remembering multiple flags and parameters
+
 ```bash
 wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project
 ```
 
 **After:** Simple directory deployment with guided setup
+
 ```bash
 wrangler deploy dist
 # Interactive prompts handle the rest as shown in the example flow below
@@ -24,12 +26,14 @@ wrangler deploy dist
 ## What's new
 
 **Interactive prompts for missing configuration:**
+
 - Wrangler detects when you're trying to deploy a directory of static assets
 - Prompts you to confirm the deployment type
 - Asks for a project name (with smart defaults)
 - Automatically sets the compatibility date to today
 
 **Automatic configuration generation:**
+
 - Creates a `wrangler.jsonc` file with your deployment settings
 - Stores your choices for future deployments
 - Eliminates the need to remember complex command-line flags
@@ -60,4 +64,3 @@ wrangler deploy
 ## Requirements
 
 - You must use Wrangler version 4.24.4 or later in order to use this feature
-
diff --git a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
index 50813da8dd6bb74..8dc771049e2038d 100644
--- a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
@@ -10,4 +10,4 @@ We've updated our "Built with Cloudflare" button to make it easier to share that
 
 ![Built with Cloudflare](https://workers.cloudflare.com/built-with-cloudflare.svg)
 
-Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
\ No newline at end of file
+Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
diff --git a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
index ad92d184dcdbf29..b36f8560a42c020 100644
--- a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
+++ b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
@@ -5,14 +5,15 @@ products:
   - workers
 date: 2025-09-11
 ---
+
 The number of recent versions available for a Worker rollback has been increased from 10 to 100.
 
-This allows you to: 
+This allows you to:
 
-* Promote any of the 100 most recent versions to be the active deployment. 
+- Promote any of the 100 most recent versions to be the active deployment.
 
-* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+- Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
 
 You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/general/#rollback)
 
-Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 
+Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/).
diff --git a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
index b43c774dfedb8db..36d8857e5b5101a 100644
--- a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
+++ b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
@@ -1,13 +1,15 @@
 ---
 title: Preview URLs now default to opt-in
-description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in. 
+description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in.
 date: 2025-09-17
 ---
+
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers.
 
 ## One-Time Update for Workers with workers.dev Disabled
+
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
 
 Because preview URLs were historically enabled by default, users who had intentionally disabled their workers.dev route may not have realized their Worker was still accessible at a separate preview URL. This update was performed to ensure that using a preview URL is always an intentional, opt-in choice.
diff --git a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
index f4d8ebd421fb775..2e03e6d00a562e1 100644
--- a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
+++ b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
@@ -5,8 +5,8 @@ products:
   - workers
 date: 2025-09-19
 ---
- 
-[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA). 
+
+[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA).
 
 The `ratelimit` binding is now stable and recommended for all production workloads. Existing deployments using the unsafe binding will continue to function to allow for a smooth transition.
 
diff --git a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
index 0af736a78a816cc..ae4a4020187a762 100644
--- a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
+++ b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
@@ -13,7 +13,6 @@ wrangler dev --config ./web/wrangler.jsonc --config ./api/wrangler.jsonc
 ```
 
 Previously, if you ran the command above and then also ran wrangler dev for a different Worker, the Workers running in separate wrangler dev sessions could not communicate with each other. This prevented you from being able to use [Service Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) and [Tail Workers](https://developers.cloudflare.com/workers/observability/logs/tail-workers/) in local development, when running separate wrangler dev sessions.
-	
 Now, the following works as expected:
 
 ```sh
@@ -28,17 +27,17 @@ These Workers can now communicate with each other across separate dev commands,
 
 ```js title="./api/src/index.ts"
 export default {
-  async fetch(request, env) {
-    // This service binding call now works across dev commands
-    const authorized = await env.AUTH.isAuthorized(request);
+	async fetch(request, env) {
+		// This service binding call now works across dev commands
+		const authorized = await env.AUTH.isAuthorized(request);
 
-    if (!authorized) {
-      return new Response('Unauthorized', { status: 401 });
-    }
+		if (!authorized) {
+			return new Response("Unauthorized", { status: 401 });
+		}
 
-    return new Response('Hello from API Worker!', { status: 200 });
-  },
+		return new Response("Hello from API Worker!", { status: 200 });
+	},
 };
 ```
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
\ No newline at end of file
+Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
diff --git a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
index 811b7c54cb413df..efbdbc961f780a8 100644
--- a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
@@ -1,17 +1,19 @@
 ---
 title: Workers Analytics Engine adds supports for new SQL functions
-description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions! 
+description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions!
 date: 2025-10-02
 products:
   - workers-analytics-engine
 ---
+
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
+
 - `argMin()` - Returns the value associated with the minimum in a group
 - `argMax()` - Returns the value associated with the maximum in a group
 - `topK()` - Returns an array of the most frequent values in a group
@@ -20,6 +22,7 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `last_value()` - Returns the last value in an ordered set of values within a partition
 
 [**New bit functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/bit-functions/)
+
 - `bitAnd()` - Returns the bitwise AND of two expressions
 - `bitCount()` - Returns the number of bits set to one in the binary representation of a number
 - `bitHammingDistance()` - Returns the number of bits that differ between two numbers
@@ -33,24 +36,28 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `bitXor()` - Returns the bitwise exclusive-or of two expressions
 
 [**New mathematical functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/mathematical-functions/)
+
 - `abs()` - Returns the absolute value of a number
 - `log()` - Computes the natural logarithm of a number
-- `round()` - Rounds a number to a specified number of decimal places  
+- `round()` - Rounds a number to a specified number of decimal places
 - `ceil()` - Rounds a number up to the nearest integer
 - `floor()` - Rounds a number down to the nearest integer
 - `pow()` - Returns a number raised to the power of another number
 
 [**New string functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/string-functions/)
+
 - `lowerUTF8()` - Converts a string to lowercase using UTF-8 encoding
 - `upperUTF8()` - Converts a string to uppercase using UTF-8 encoding
 
 [**New encoding functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/encoding-functions/)
+
 - `hex()` - Converts a number to its hexadecimal representation
-- `bin()` - Converts a string to its binary representation 
+- `bin()` - Converts a string to its binary representation
 
 [**New type conversion functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/type-conversion-functions/)
+
 - `toUInt8()` - Converts any numeric expression, or expression resulting in a string representation of a decimal, into an unsigned 8 bit integer
 
+## Ready to get started?
 
-## Ready to get started? 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
diff --git a/src/content/changelog/workers/2025-09-26-ctx-exports.md b/src/content/changelog/workers/2025-09-26-ctx-exports.md
index ca40c83e6442e7d..19bcc4be7d98ad5 100644
--- a/src/content/changelog/workers/2025-09-26-ctx-exports.md
+++ b/src/content/changelog/workers/2025-09-26-ctx-exports.md
@@ -12,17 +12,17 @@ Example:
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class Greeter extends WorkerEntrypoint {
-  greet(name) {
-    return `Hello, ${name}!`;
-  }
+	greet(name) {
+		return `Hello, ${name}!`;
+	}
 }
 
 export default {
-  async fetch(request, env, ctx) {
-    let greeting = await ctx.exports.Greeter.greet("World")
-    return new Response(greeting);
-  }
-}
+	async fetch(request, env, ctx) {
+		let greeting = await ctx.exports.Greeter.greet("World");
+		return new Response(greeting);
+	},
+};
 ```
 
 At present, you must use [the `enable_ctx_exports` compatibility flag](/workers/configuration/compatibility-flags#enable-ctxexports) to enable this API, though it will be on by default in the future.
diff --git a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
index 374f4f9426567ed..7ae62260c3c8ae4 100644
--- a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
@@ -5,7 +5,8 @@ products:
   - workers
 date: 2025-10-09
 ---
-import { Code } from 'astro-expressive-code/components';
+
+import { Code } from "astro-expressive-code/components";
 
 You can now upload Workers with [static assets](/workers/static-assets/) (like HTML, CSS, JavaScript, images) with the [Cloudflare Terraform provider v5.11.0](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), making it even easier to deploy and manage full-stack apps with IaC.
 
@@ -15,14 +16,12 @@ You can now upload Workers with [static assets](/workers/static-assets/) (like H
 
 You can get started today with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), using either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), or the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
-
 ## Examples
 
 #### With `cloudflare_workers_script`
 
 Here's how you can use the existing [`cloudflare_workers_script`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_script) resource to upload your Worker code and assets in one shot.
 
-
 ```hcl
 resource "cloudflare_workers_script" "my_app" {
   account_id  = var.account_id
@@ -82,10 +81,11 @@ resource "cloudflare_workers_deployment" "my_app_deployment" {
 ```
 
 ## What's changed
-Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for *only* those changed files.
 
+Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for _only_ those changed files.
 
 ## Try it out
--  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
+
+- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
 - You can use either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script) to upload your Worker code and assets in one resource.
 - Or you can use the new beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version) (along with the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment)) resources to more granularly control the lifecycle of each Worker resource.
diff --git a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
index a48ee31b4bd8245..8305f662b5ae806 100644
--- a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
@@ -20,8 +20,8 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 # Examples
-Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
 #### With `cloudflare_workflow` and `cloudflare_workers_script`
 
@@ -44,10 +44,9 @@ resource "cloudflare_workflow" "workflow" {
 
 ```
 
-
 #### With `cloudflare_workflow`, and the new beta resources
-You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
+You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
 ```hcl
 
@@ -89,4 +88,5 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 ## Try it out
--  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
\ No newline at end of file
+
+- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
diff --git a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
index 7e4144ec5e29a50..60b2deb83ab1bbe 100644
--- a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
+++ b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
@@ -3,20 +3,23 @@ title: Workers Preview URL default behavior now matches your workers.dev setting
 description: If a Workers Preview URL setting is not explicitly configured, its default behavior will now match the setting of the workers.dev subdomain.
 date: 2025-10-23
 ---
+
 We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/configuration/previews/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
 
 This change is intended to provide a more intuitive and secure experience by aligning your preview URL's default state with your `workers.dev` configuration to prevent cases where a preview URL might remain public even after you disabled your `workers.dev` route.
 
 **What this means for you:**
+
 - **If neither setting is configured:** both the workers.dev route and the preview URL will default to enabled
 - **If your workers.dev route is enabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to enabled
 - **If your workers.dev route is disabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to disabled
 
-You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file). 
+You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file).
 
 **Wrangler Version Behavior**
 
 The default behavior depends on the version of Wrangler you are using. This new logic applies to the latest version. Here is a summary of the behavior across different versions:
+
 - **Before v4.34.0:** Preview URLs defaulted to enabled, regardless of the workers.dev setting.
 - **v4.34.0 up to (but not including) v4.44.0:** Preview URLs defaulted to disabled, regardless of the workers.dev setting.
 - **v4.44.0 or later:** Preview URLs now default to matching your workers.dev setting.
@@ -27,7 +30,7 @@ In July, [we introduced preview URLs to Workers](/changelog/2025-07-23-workers-p
 
 To address this, we made a [one-time update](/changelog/2025-09-17-update-preview-url-setting/) to disable preview URLs on existing Workers that had their workers.dev route disabled and changed the default behavior to be disabled for all new deployments where a preview URL setting was not explicitly configured.
 
-While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience. 
+While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience.
 
 **Securing access to `workers.dev` and preview URL endpoints**
 
diff --git a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
index 8d5b16c36bd1a5c..a4a42cacd6469f1 100644
--- a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
+++ b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
 
 Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
 
-Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag. 
+Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
 
 To use this feature, update to wrangler@4.45.0 and add bindings to your config file _without_ resource IDs e.g.:
 
diff --git a/src/content/changelog/workers/2025-10-30-builds-preview.mdx b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
index 6d384a223acd212..b18b3bf98b7469f 100644
--- a/src/content/changelog/workers/2025-10-30-builds-preview.mdx
+++ b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
@@ -10,8 +10,8 @@ You can now access [preview URLs](/workers/configuration/previews/) directly fro
 
 ![preview button](src/assets/images/changelog/workers/builds-preview-button.png)
 
-
 **What's new**
-* A **Preview** button now appears in the top-right corner of the build details page for successful builds
-* Click it to instantly open the latest preview URL
-* Matches the same experience you're familiar with from Pages
+
+- A **Preview** button now appears in the top-right corner of the build details page for successful builds
+- Click it to instantly open the latest preview URL
+- Matches the same experience you're familiar with from Pages
diff --git a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
index f405d7512be43a7..3d8cbe449a7111e 100644
--- a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
+++ b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
@@ -11,6 +11,7 @@ Wrangler now supports using the `CLOUDFLARE_ENV` [environment variable](/workers
 ## What's new
 
 **Environment selection via environment variable:**
+
 - Set `CLOUDFLARE_ENV` to specify which environment to use for Wrangler commands
 - Works with all Wrangler commands that support the `--env` flag
 - The `--env` command line argument takes precedence over the `CLOUDFLARE_ENV` environment variable
diff --git a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
index aa66f983da252d7..cbf3d01a00ba625 100644
--- a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
@@ -5,18 +5,21 @@ date: 2025-11-12
 products:
   - workers-analytics-engine
 ---
+
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
+
 - `countIf()` - count the number of rows which satisfy a provided condition
 - `sumIf()` - calculate a sum from rows which satisfy a provided condition
 - `avgIf()` - calculate an average from rows which satisfy a provided condition
 
 [**New date and time functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/date-time-functions/)
+
 - `toYear()`
 - `toMonth()`
 - `toDayOfMonth()`
@@ -36,5 +39,6 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `today()`
 - `toYYYYMM()`
 
-## Ready to get started? 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
+## Ready to get started?
+
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
diff --git a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
index 1151c4807768e2e..8a813cefea8b895 100644
--- a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
+++ b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
@@ -12,4 +12,4 @@ We've published build image policies for [Workers Builds](/workers/ci-cd/builds/
 - **Major version updates**: Before preinstalled software reaches end-of-life, we update to the next stable LTS version with 3 months’ notice.
 - **Build image version deprecation (Pages only)**: We provide 6 months’ notice before deprecation. Projects on v1 or v2 will be automatically moved to v3 on their specified deprecation dates.
 
-To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
\ No newline at end of file
+To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
diff --git a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
index 073712734586f32..f8224767a58f981 100644
--- a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
@@ -17,11 +17,11 @@ We set up a benchmark that imports common packages ([httpx](https://www.python-h
 [fastapi](https://fastapi.tiangolo.com/) and [pydantic](https://docs.pydantic.dev/latest/))
 to see how Python Workers stack up against other platforms:
 
-| Platform | Mean Cold Start (ms) |
-|----------|----------------------|
-| Cloudflare Python Workers | 1027 |
-| AWS Lambda | 2502 |
-| Google Cloud Run | 3069 |
+| Platform                  | Mean Cold Start (ms) |
+| ------------------------- | -------------------- |
+| Cloudflare Python Workers | 1027                 |
+| AWS Lambda                | 2502                 |
+| Google Cloud Run          | 3069                 |
 
 These benchmarks run continuously. You can view the results and the methodology on our [benchmark page](https://cold.edgeworker.net).
 
diff --git a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
index 47424c741ce45c1..6889ac1e31e515b 100644
--- a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
@@ -37,5 +37,4 @@ uv run pywrangler deploy
 
 Pywrangler automatically downloads and vendors the necessary packages for your Worker, and these packages are bundled with the Worker when you deploy.
 
-
 Consult the [Python packages documentation](/workers/languages/python/packages/) for full details on Pywrangler and Python package management in Workers.
diff --git a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
index 2890f89b49db4ef..46b90006bdbbd44 100644
--- a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
@@ -8,4 +8,4 @@ date: 2025-12-08
 
 When using the [Cloudflare Vite plugin](/workers/vite-plugin/) to build and deploy Workers, a Wrangler configuration file is now optional for assets-only (static) sites. If no `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` file is found, the plugin generates sensible defaults for an assets-only site. The `name` is based on the `package.json` or the project directory name, and the `compatibility_date` uses the latest date supported by your installed Miniflare version.
 
-This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
\ No newline at end of file
+This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
diff --git a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
index b18355b4e98ed59..7be9426da4e23de 100644
--- a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
@@ -103,4 +103,4 @@ export default defineConfig({
 });
 ```
 
-For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
\ No newline at end of file
+For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
diff --git a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
index 64b1e78e3c965cc..c171a822bbc5fa6 100644
--- a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
+++ b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
@@ -15,9 +15,9 @@ import { createExecutionContext } from "cloudflare:test";
 import { it, expect } from "vitest";
 
 it("can access ctx.exports", async () => {
-  const ctx = createExecutionContext();
-  const result = await ctx.exports.MyEntryPoint.myMethod();
-  expect(result).toBe("expected value");
+	const ctx = createExecutionContext();
+	const result = await ctx.exports.MyEntryPoint.myMethod();
+	expect(result).toBe("expected value");
 });
 ```
 
@@ -28,8 +28,8 @@ import { exports } from "cloudflare:workers";
 import { it, expect } from "vitest";
 
 it("can access imported exports", async () => {
-  const result = await exports.MyEntryPoint.myMethod();
-  expect(result).toBe("expected value");
+	const result = await exports.MyEntryPoint.myMethod();
+	expect(result).toBe("expected value");
 });
 ```
 
diff --git a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
index 2a6b5bff0742249..7f91b0a340dd8fd 100644
--- a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
+++ b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
@@ -6,8 +6,8 @@ products:
 date: 2025-12-19
 ---
 
-[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables 
-and bindings,  and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
+[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables
+and bindings, and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
 
 ```ts title="vite.config.ts"
 import { defineConfig } from "vite";
@@ -15,14 +15,14 @@ import { cloudflare } from "@cloudflare/vite-plugin";
 import { tanstackStart } from "@tanstack/react-start/plugin/vite";
 
 export default defineConfig({
-  plugins: [
-    cloudflare({ viteEnvironment: { name: "ssr" } }),
-    tanstackStart({
-      prerender: {
-        enabled: true,
-      },
-    }),
-  ],
+	plugins: [
+		cloudflare({ viteEnvironment: { name: "ssr" } }),
+		tanstackStart({
+			prerender: {
+				enabled: true,
+			},
+		}),
+	],
 });
 ```
 
diff --git a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
index c28886f2273eb0a..f027c8fd04d6f0d 100644
--- a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
+++ b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
@@ -26,6 +26,7 @@ Key guidance includes:
 ```
 
 </WranglerConfig>
+
 - **Generate binding types with `wrangler types`** — Never hand-write your `Env` interface. Let Wrangler generate it from your actual configuration to catch mismatches at compile time.
 - **Stream request and response bodies** — Avoid buffering large payloads in memory. Use `TransformStream` and `pipeTo` to stay within the 128 MB memory limit and improve time-to-first-byte.
 - **Use bindings, not REST APIs** — Bindings to KV, R2, D1, Queues, and other Cloudflare services are direct, in-process references with no network hop and no authentication overhead.
diff --git a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
index c153f96598e79c4..7e14d709a1a753e 100644
--- a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
@@ -8,31 +8,36 @@ Four new fields are now available on `request.cf.tlsClientAuth` in Workers for r
 
 ### New fields
 
-| Field | Type | Description |
-| --- | --- | --- |
-| `certRFC9440` | String | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented. |
-| `certRFC9440TooLarge` | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`. |
-| `certChainRFC9440` | String | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
-| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`. |
+| Field                      | Type    | Description                                                                                                                                          |
+| -------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `certRFC9440`              | String  | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented.                                       |
+| `certRFC9440TooLarge`      | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`.                                                                    |
+| `certChainRFC9440`         | String  | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
+| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`.                                                             |
 
 ### Example: forwarding client certificate headers to your origin
 
 ```js
 export default {
-  async fetch(request) {
-    const tls = request.cf.tlsClientAuth;
-
-    // Only forward if cert was verified and chain is complete
-    if (!tls || !tls.certVerified || tls.certRevoked || tls.certChainRFC9440TooLarge) {
-      return new Response("Unauthorized", { status: 401 });
-    }
-
-    const headers = new Headers(request.headers);
-    headers.set("Client-Cert", tls.certRFC9440);
-    headers.set("Client-Cert-Chain", tls.certChainRFC9440);
-
-    return fetch(new Request(request, { headers }));
-  },
+	async fetch(request) {
+		const tls = request.cf.tlsClientAuth;
+
+		// Only forward if cert was verified and chain is complete
+		if (
+			!tls ||
+			!tls.certVerified ||
+			tls.certRevoked ||
+			tls.certChainRFC9440TooLarge
+		) {
+			return new Response("Unauthorized", { status: 401 });
+		}
+
+		const headers = new Headers(request.headers);
+		headers.set("Client-Cert", tls.certRFC9440);
+		headers.set("Client-Cert-Chain", tls.certChainRFC9440);
+
+		return fetch(new Request(request, { headers }));
+	},
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
index 1a9e3164168578c..c311cbdd393dadd 100644
--- a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,31 +10,33 @@ Previously, this telemetry was only available via the `Server-Timing: cfL4` resp
 
 ### New properties
 
-| Property | Type | Description |
-| --- | --- | --- |
-| `clientTcpRtt` | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`. |
-| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`. |
-| `edgeL4` | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
+| Property        | Type                | Description                                                                                                                                                                  |
+| --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `clientTcpRtt`  | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`.              |
+| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`.                    |
+| `edgeL4`        | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
 
 ### Example: Log connection quality metrics
 
 ```js
 export default {
-  async fetch(request) {
-    const cf = request.cf;
+	async fetch(request) {
+		const cf = request.cf;
 
-    const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
-    const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
-    const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
+		const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
+		const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
+		const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
 
-    console.log(`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`);
+		console.log(
+			`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`,
+		);
 
-    const headers = new Headers(request.headers);
-    headers.set("X-Client-RTT", String(rtt));
-    headers.set("X-Delivery-Rate", String(deliveryRate));
+		const headers = new Headers(request.headers);
+		headers.set("X-Client-RTT", String(rtt));
+		headers.set("X-Delivery-Rate", String(deliveryRate));
 
-    return fetch(new Request(request, { headers }));
-  },
+		return fetch(new Request(request, { headers }));
+	},
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
index 47a711a702b2fba..ffd136835ae4bc4 100644
--- a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
+++ b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
@@ -9,7 +9,7 @@ date: 2026-05-07 12:00:00 UTC
 
 Multiple security vulnerabilities were disclosed by the React team and Vercel affecting React Server Components and Next.js. These include denial of service, middleware and proxy bypass, server-side request forgery, cross-site scripting, and cache poisoning issues across a range of severity levels.
 
-**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`). 
+**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`).
 
 ## WAF protections
 
diff --git a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
index 48963056126296d..7f215858ca21722 100644
--- a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
+++ b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
@@ -10,8 +10,8 @@ date: 2025-01-15
 
 We've also added:
 
-* `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
-* Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
-* Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
+- `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
+- Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
+- Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
 
 We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks.
diff --git a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
index dbd052de60e2fc7..4f047f473ce8ee4 100644
--- a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
+++ b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
@@ -9,9 +9,9 @@ date: 2025-10-31
 
 We've raised the [Cloudflare Workflows](/workflows/) account-level limits for all accounts on the [Workers paid plan](/workers/platform/pricing/):
 
-* **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
-* **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
+- **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
+- **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
 
-These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/). 
+These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/).
 
 If your application requires a higher limit, fill out the [Limit Increase Request Form](/workers/platform/limits/) or contact your account team. Please refer to [Workflows pricing](/workflows/reference/pricing/) for more information.
diff --git a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
index 90eef81c9251ce0..e29d175b6b83ba6 100644
--- a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
+++ b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
@@ -20,4 +20,4 @@ await instance.pause(); // pauses a running workflow instance
 await instance.resume(); // resumes a paused instance
 await instance.restart(); // restarts the instance from the beginning
 await instance.terminate(); // terminates the instance immediately
-```
\ No newline at end of file
+```
diff --git a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
index 4afac919aa7d970..93eb46096142460 100644
--- a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
+++ b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
@@ -7,15 +7,15 @@ products:
 date: 2026-05-01
 ---
 
-You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime. 
+You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime.
 
 The Worker Loader loads Dynamic Workers on demand, which previously made durability challenging. Even within a Dynamic Worker, a Workflow might sleep for hours or days between steps, and by the time it resumes, the original Dynamic Worker code would no longer be in memory.
 
-The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens. 
+The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens.
 
 Because Dynamic Workers are created on-demand, you do not have to register each Workflow up front or manage them individually. Load the Workflow code in the Dynamic Worker when it is needed, and the Workflows engine handles persistence and retries behind the scenes. Your Workflow code itself is unaffected by the routing and behaves as normal.
 
-This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with: 
+This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with:
 
 - **SaaS platforms** where each tenant defines their own automation, such as onboarding sequences, approval chains, or billing retry logic.
 - **AI agent frameworks** where agents generate and execute multi-step plans at runtime, surviving restarts and waiting for human approval between tool calls.
diff --git a/src/content/compatibility-flags/allow-custom-ports.md b/src/content/compatibility-flags/allow-custom-ports.md
index 4a9cf4a9b5f6932..537127433070005 100644
--- a/src/content/compatibility-flags/allow-custom-ports.md
+++ b/src/content/compatibility-flags/allow-custom-ports.md
@@ -22,6 +22,7 @@ For example:
 ```js
 const response = await fetch("https://example.com:8000");
 ```
+
 With allow_custom_ports the above example would fetch `https://example.com:8000` rather than
 `https://example.com:443`.
 
diff --git a/src/content/compatibility-flags/enable-nodejs-http-modules.md b/src/content/compatibility-flags/enable-nodejs-http-modules.md
index b28f784408c15f9..2bfccf48ee0d939 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-modules.md
@@ -21,10 +21,10 @@ This enables compatibility with Node.js libraries and existing code that
 use the standard node:http and node:https APIs for making HTTP requests.
 The available functionality includes:
 
-* `http.request()` and `https.request()` for making HTTP/HTTPS requests
-* `http.get()` and `https.get()` for making GET requests
-* Request and response objects with standard Node.js APIs
-* Support for standard HTTP methods, headers, and options
+- `http.request()` and `https.request()` for making HTTP/HTTPS requests
+- `http.get()` and `https.get()` for making GET requests
+- Request and response objects with standard Node.js APIs
+- Support for standard HTTP methods, headers, and options
 
 See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html)
 for more details about the Node.js APIs.
diff --git a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
index 1e31b6a8b5508a4..b4b92da33a8f73b 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
@@ -20,9 +20,9 @@ server modules.
 This enables compatibility with Node.js libraries and existing code that
 use the standard Node.js HTTP server APIs. The available functionality includes:
 
-* `http.createServer()` for creating HTTP servers
-* `http.Server` class for server instances
-* `http.ServerResponse` for handling server responses
+- `http.createServer()` for creating HTTP servers
+- `http.Server` class for server instances
+- `http.ServerResponse` for handling server responses
 
 This flag must be used in combination with the `enable_nodejs_http_modules` flag
 to enable full features of `node:http`.
@@ -30,4 +30,4 @@ to enable full features of `node:http`.
 This flag is automatically enabled for Workers using
 a compatibility date of 2025-09-01 or later when `nodejs_compat` is enabled.
 
-See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
\ No newline at end of file
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
diff --git a/src/content/compatibility-flags/fetcher-no-get-put-delete.md b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
index d38f2d504089ae8..dcf2a945b94649b 100644
--- a/src/content/compatibility-flags/fetcher-no-get-put-delete.md
+++ b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
@@ -18,4 +18,3 @@ Historically, API objects that had such a `fetch()` method also had methods `get
 These methods were a very early idea from many years ago, but were never actually documented, and therefore rarely (if ever) used. Enabling the `fetcher_no_get_put_delete`, or setting a compatibility date on or after `2024-03-26` disables these methods for your Worker.
 
 This change paves a future path for you to be able to define your own custom methods using these names. Without this change, you would be unable to define your own `get`, `put`, and `delete` methods, since they would conflict with these built-in helper methods.
-
diff --git a/src/content/compatibility-flags/js-weak-refs.md b/src/content/compatibility-flags/js-weak-refs.md
index 718f8818a545c01..061ea4e608cd187 100644
--- a/src/content/compatibility-flags/js-weak-refs.md
+++ b/src/content/compatibility-flags/js-weak-refs.md
@@ -12,6 +12,7 @@ disable_flag: "disable_weak_ref"
 ---
 
 Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry) and [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef) built-ins.
+
 - `FinalizationRegistry` allows you to register a cleanup callback that runs after an object has been garbage-collected.
 - `WeakRef` creates a weak reference to an object, allowing it to be garbage-collected if no other strong references exist.
 
@@ -21,4 +22,4 @@ Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/
 
 :::caution
 These APIs are fundamentally non-deterministic. The timing and execution of garbage collection are unpredictable, and you **should not rely on them for essential program logic**. Additionally, cleanup callbacks registered with `FinalizationRegistry` may **never be executed**, including but not limited to cases where garbage collection is not triggered, or your Worker gets evicted.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/compatibility-flags/new-url-parser-implementation.md b/src/content/compatibility-flags/new-url-parser-implementation.md
index 55b21a5be67018c..9ec8017e42ea670 100644
--- a/src/content/compatibility-flags/new-url-parser-implementation.md
+++ b/src/content/compatibility-flags/new-url-parser-implementation.md
@@ -13,17 +13,17 @@ disable_flag: "url_original"
 
 The original implementation of the [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) API in Workers was not fully compliant with the [WHATWG URL Standard](https://url.spec.whatwg.org/), differing in several ways, including:
 
-* The original implementation collapsed sequences of multiple slashes into a single slash:
+- The original implementation collapsed sequences of multiple slashes into a single slash:
 
   `new URL("https://example.com/a//b").toString() === "https://example.com/a/b"`
 
-* The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
+- The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
 
-* The original implementation would percent-encode or percent-decode certain content differently:
+- The original implementation would percent-encode or percent-decode certain content differently:
 
   `new URL("https://example.com/a%40b?c d%20e?f").toString() === "https://example.com/a@b?c+d+e%3Ff"`
 
-* The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
+- The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
 
 Set the compatibility date of your Worker to a date after `2022-10-31` or enable the `url_standard` compatibility flag to opt-in the fully spec compliant `URL` API implementation.
 
diff --git a/src/content/compatibility-flags/nodejs-compat.md b/src/content/compatibility-flags/nodejs-compat.md
index 80bfc4fec1b0734..6eb72d18070e7de 100644
--- a/src/content/compatibility-flags/nodejs-compat.md
+++ b/src/content/compatibility-flags/nodejs-compat.md
@@ -14,12 +14,12 @@ Enables [Node.js APIs](/workers/runtime-apis/nodejs/) in the Workers Runtime.
 
 Note that some Node.js APIs are only enabled if your Worker's compatibility date is set to on or after the following dates:
 
-| Node.js API | Enabled after  |
-|---|---|
-| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)  | `2025-09-01`  |
-| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules)  | `2025-08-15`  |
-| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)  | `2025-04-01`  |
-| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)  | `2024-12-02`  |
+| Node.js API                                                                                                                    | Enabled after |
+| ------------------------------------------------------------------------------------------------------------------------------ | ------------- |
+| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)                                 | `2025-09-01`  |
+| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules) | `2025-08-15`  |
+| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)                                 | `2025-04-01`  |
+| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)       | `2024-12-02`  |
 
 When enabling `nodejs_compat`, we recommend using the latest version of [Wrangler CLI](/workers/wrangler/), and the latest compatiblity date, in order to maximize compatibility. Some older versions of Wrangler inject additional polyfills that are no longer neccessary, as they are provided by the Workers runtime, if your Worker is using a more recent compatibility date.
 
diff --git a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
index 82a917d18ac5162..458d6f154b4f789 100644
--- a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
+++ b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
@@ -13,26 +13,29 @@ enable_flag: "queue_consumer_no_wait_for_wait_until"
 By default, [Queues](/queues/) Consumer Workers acknowledge messages only after promises passed to [`ctx.waitUntil()`](/workers/runtime-apis/context) have resolved. This behavior can cause queue consumers which utilize `ctx.waitUntil()` to process messages slowly. The default behavior is documented in the [Queues Consumer Configuration Guide](/queues/configuration/javascript-apis#consumer).
 
 This Consumer Worker is an example of a Worker which utilizes `ctx.waitUntil()`. Under the default behavior, this consumer Worker will only acknowledge a batch of messages after the sleep function has resolved.
+
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    // omitted
-  },
-
-  async queue(batch, env, ctx) {
-    console.log(`received batch of ${batch.messages.length} messages to queue ${batch.queue}`);
-    for (let i = 0; i < batch.messages.length; ++i) {
-      console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
-    }
-    ctx.waitUntil(sleep(30 * 1000));
-  }
+	async fetch(request, env, ctx) {
+		// omitted
+	},
+
+	async queue(batch, env, ctx) {
+		console.log(
+			`received batch of ${batch.messages.length} messages to queue ${batch.queue}`,
+		);
+		for (let i = 0; i < batch.messages.length; ++i) {
+			console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
+		}
+		ctx.waitUntil(sleep(30 * 1000));
+	},
 };
 
 function sleep(ms) {
-  return new Promise(resolve => setTimeout(resolve, ms));
+	return new Promise((resolve) => setTimeout(resolve, ms));
 }
 ```
 
 If the `queue_consumer_no_wait_for_wait_until` flag is enabled, Queues consumers will no longer wait for promises passed to `ctx.waitUntil()` to resolve before acknowledging messages. This can improve the performance of queue consumers which utilize `ctx.waitUntil()`. With the flag enabled, in the above example, the consumer Worker will acknowledge the batch without waiting for the sleep function to resolve.
 
-Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
\ No newline at end of file
+Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
diff --git a/src/content/compatibility-flags/queues-json-messages.md b/src/content/compatibility-flags/queues-json-messages.md
index ed871f0ed83b10b..468e5bc0c452ce5 100644
--- a/src/content/compatibility-flags/queues-json-messages.md
+++ b/src/content/compatibility-flags/queues-json-messages.md
@@ -11,4 +11,4 @@ enable_flag: "queues_json_messages"
 disable_flag: "no_queues_json_messages"
 ---
 
-With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
\ No newline at end of file
+With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
diff --git a/src/content/compatibility-flags/request-signal.md b/src/content/compatibility-flags/request-signal.md
index e60e43e66403e2f..75a494da250906c 100644
--- a/src/content/compatibility-flags/request-signal.md
+++ b/src/content/compatibility-flags/request-signal.md
@@ -5,4 +5,4 @@ enable_flag: "enable_request_signal"
 disable_flag: "disable_request_signal"
 ---
 
-When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
\ No newline at end of file
+When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
diff --git a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
index 994a6a724e2f465..3cdf43761777395 100644
--- a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
+++ b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
@@ -20,12 +20,12 @@ User code should never try to reuse an `ArrayBuffer` that has been passed into a
 let reader = readable.getReader({ mode: "byob" });
 let arrayBufferView = new Uint8Array(4096);
 while (true) {
-  let result = await reader.read(arrayBufferView);
-  if (result.done) break;
-  // Optionally something with `result` here.
-  // Re-use the same memory for the next `read()` by creating
-  // a new Uint8Array backed by the result's ArrayBuffer.
-  arrayBufferView = new Uint8Array(result.value.buffer);
+	let result = await reader.read(arrayBufferView);
+	if (result.done) break;
+	// Optionally something with `result` here.
+	// Re-use the same memory for the next `read()` by creating
+	// a new Uint8Array backed by the result's ArrayBuffer.
+	arrayBufferView = new Uint8Array(result.value.buffer);
 }
 ```
 
diff --git a/src/content/compatibility-flags/strict-crypto.md b/src/content/compatibility-flags/strict-crypto.md
index 91a77815dd82fde..17274d7e485ef60 100644
--- a/src/content/compatibility-flags/strict-crypto.md
+++ b/src/content/compatibility-flags/strict-crypto.md
@@ -14,6 +14,7 @@ disable_flag: "no_strict_crypto_checks"
 ---
 
 Perform additional error checking in the Web Crypto API to conform with the specification and reject possibly unsafe key parameters:
+
 - For RSA key generation, key sizes are required to be multiples of 128 bits as boringssl may otherwise truncate the key.
 - The size of imported RSA keys must be at least 256 bits and at most 16384 bits, as with newly generated keys.
 - The public exponent for imported RSA keys is restricted to the commonly used values `[3, 17, 37, 65537]`.
diff --git a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
index 15ea7891dc4fcad..3b380e857412453 100644
--- a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
+++ b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
@@ -19,4 +19,3 @@ attribute is encountered that is not recognized.
 
 When the `ignore_unrecognized_import_assertion` flag is set, Workers will
 ignore unrecognized import attributes.
-
diff --git a/src/content/compatibility-flags/to-string-tag.md b/src/content/compatibility-flags/to-string-tag.md
index 1de8e533db3f8bb..6fc298a87c182de 100644
--- a/src/content/compatibility-flags/to-string-tag.md
+++ b/src/content/compatibility-flags/to-string-tag.md
@@ -13,5 +13,5 @@ disable_flag: "do_not_set_tostring_tag"
 
 A change was made to set the Symbol.toStringTag on all Workers API objects
 in order to fix several spec compliance bugs. Unfortunately,
-this change was more breaking than anticipated. The `do_not_set_tostring_tag`  compat
+this change was more breaking than anticipated. The `do_not_set_tostring_tag` compat
 flag restores the original behavior with compatibility dates of 2024-09-26 or earlier.
diff --git a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
index ff6e300d56a8451..b94637375b11410 100644
--- a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
+++ b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
@@ -21,7 +21,7 @@ For an example of how this change could break existing code, consider code that
 ```js
 const usp = new URLSearchParams();
 // ...
-['abc', 'xyz'].forEach(usp.delete.bind(usp));
+["abc", "xyz"].forEach(usp.delete.bind(usp));
 ```
 
 The `forEach()` automatically passes multiple parameters to the function that is passed in. Prior to the addition of the new standard parameters, these extra arguments would have been ignored.
@@ -31,5 +31,5 @@ Now, however, the additional arguments have meaning and change the behavior of t
 ```js
 const usp = new URLSearchParams();
 // ...
-['abc', 'xyz'].forEach((key) => usp.delete(key));
-```
\ No newline at end of file
+["abc", "xyz"].forEach((key) => usp.delete(key));
+```
diff --git a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
index be603aaba1a62ba..5a0f4a50358133e 100644
--- a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
+++ b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
@@ -19,12 +19,16 @@ Previously, receiving a server-initiated Close frame left the WebSocket in `CLOS
 const [client, server] = Object.values(new WebSocketPair());
 server.accept();
 
-server.addEventListener("close", (event) => {
-  // readyState is already CLOSED — no need to call server.close().
-  console.log(server.readyState); // WebSocket.CLOSED
-  console.log(event.code); // 1000
-  console.log(event.wasClean); // true
-}, { once: true });
+server.addEventListener(
+	"close",
+	(event) => {
+		// readyState is already CLOSED — no need to call server.close().
+		console.log(server.readyState); // WebSocket.CLOSED
+		console.log(event.code); // 1000
+		console.log(event.wasClean); // true
+	},
+	{ once: true },
+);
 ```
 
 If you do still call `close()` inside the handler, the call is silently ignored. This means existing code that manually replies to Close frames will not break when you update your compatibility date.
@@ -37,14 +41,18 @@ const [client, server] = Object.values(new WebSocketPair());
 // Opt into half-open mode for proxying
 server.accept({ allowHalfOpen: true });
 
-server.addEventListener("close", (event) => {
-  // With allowHalfOpen true, readyState is still CLOSING here,
-  // giving you time to coordinate the close on the other side.
-  console.log(server.readyState); // WebSocket.CLOSING
+server.addEventListener(
+	"close",
+	(event) => {
+		// With allowHalfOpen true, readyState is still CLOSING here,
+		// giving you time to coordinate the close on the other side.
+		console.log(server.readyState); // WebSocket.CLOSING
 
-  // Manually close when ready.
-  server.close(1000, "done");
-}, { once: true });
+		// Manually close when ready.
+		server.close(1000, "done");
+	},
+	{ once: true },
+);
 ```
 
 Note that there is no corresponding option to the `WebSocket` constructor. WebSockets constructed with `new WebSocket` will always auto-reply to closes after this flag takes effect. WebSockets constructed this way are automatically "accepted", so there is no opportunity to pass the option to `accept()`. If you are creating a WebSocket with `new WebSocket`, but you need half-open behavior, you will need to switch to using `fetch()` instead.
@@ -55,10 +63,10 @@ let ws = new WebSocket("wss://example.com");
 
 // But you can do this instead:
 let resp = await fetch("https://example.com", {
-  headers: { "Upgrade": "websocket" }
+	headers: { Upgrade: "websocket" },
 });
 if (!resp.webSocket) {
-  throw new Error("WebSocket handshake not accepted");
+	throw new Error("WebSocket handshake not accepted");
 }
 let ws = resp.webSocket;
 ws.accept({ allowHalfOpen: true });
diff --git a/src/content/compatibility-flags/web-socket-compression.md b/src/content/compatibility-flags/web-socket-compression.md
index c73d329ee01a83e..9949b65656e428f 100644
--- a/src/content/compatibility-flags/web-socket-compression.md
+++ b/src/content/compatibility-flags/web-socket-compression.md
@@ -15,4 +15,4 @@ The Workers runtime did not support WebSocket compression when the initial WebSo
 
 If the flag is present, the Workers runtime is capable of using WebSocket Compression on both inbound and outbound WebSocket connections.
 
-Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
\ No newline at end of file
+Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
diff --git a/src/content/compatibility-flags/websocket-standard-binary-type.md b/src/content/compatibility-flags/websocket-standard-binary-type.md
index 81e8b8883ea49f5..6e389dad36862eb 100644
--- a/src/content/compatibility-flags/websocket-standard-binary-type.md
+++ b/src/content/compatibility-flags/websocket-standard-binary-type.md
@@ -17,7 +17,7 @@ The `binaryType` property itself is available on every `WebSocket` regardless of
 
 ```js
 const resp = await fetch("https://example.com", {
-  headers: { Upgrade: "websocket" },
+	headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -26,7 +26,7 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-  // event.data is an ArrayBuffer for binary frames.
+	// event.data is an ArrayBuffer for binary frames.
 });
 ```
 
diff --git a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
index 9d993472b94bcb7..e0b79d3a85a05ed 100644
--- a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
+++ b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
@@ -19,13 +19,13 @@ Previously, throwing a `NonRetryableError` with a custom message would result in
 import { WorkflowEntrypoint, NonRetryableError } from "cloudflare:workers";
 
 export class MyWorkflow extends WorkflowEntrypoint {
-  async run(event, step) {
-    await step.do("my-step", async () => {
-      throw new NonRetryableError("custom error message");
-      // Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
-      // With this flag: error.message === "custom error message"
-    });
-  }
+	async run(event, step) {
+		await step.do("my-step", async () => {
+			throw new NonRetryableError("custom error message");
+			// Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
+			// With this flag: error.message === "custom error message"
+		});
+	}
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
index 17806e9fea110e3..39b0c719c6a6edd 100644
--- a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
+++ b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
@@ -34,10 +34,10 @@ Define protected routes in `wrangler.jsonc`:
 			{
 				"pattern": "/premium/*",
 				"amount": "0.01",
-				"description": "Access to premium content for 1 hour"
-			}
-		]
-	}
+				"description": "Access to premium content for 1 hour",
+			},
+		],
+	},
 }
 ```
 
@@ -55,7 +55,7 @@ With [Bot Management](/bots/), the proxy can charge crawlers while keeping the s
 	"amount": "0.25",
 	"description": "Content access for 1 hour",
 	"bot_score_threshold": 30,
-	"except_detection_ids": [120623194, 117479730]
+	"except_detection_ids": [120623194, 117479730],
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/x402/index.mdx b/src/content/docs/agents/agentic-payments/x402/index.mdx
index 4ae0cb18581f35d..bc12467db9b9995 100644
--- a/src/content/docs/agents/agentic-payments/x402/index.mdx
+++ b/src/content/docs/agents/agentic-payments/x402/index.mdx
@@ -45,8 +45,8 @@ The facilitator does not hold funds. It verifies and broadcasts the client's pre
 
 x402 uses payment **schemes** to define how a payment is constructed and settled on a given network.
 
-| Scheme                                                                                    | Networks                                 | Description                                                                                                                       |
-| ----------------------------------------------------------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Scheme                                                                                           | Networks                                 | Description                                                                                                                       |
+| ------------------------------------------------------------------------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | [`exact`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact.md) | EVM, Solana, Aptos, Stellar, Hedera, Sui | Transfers a fixed token amount — typically [ERC-20](https://eips.ethereum.org/EIPS/eip-20) USDC on EVM — to the merchant address. |
 | [`upto`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/upto/scheme_upto.md)    | EVM                                      | Authorizes a maximum amount; the actual charge is determined at settlement time based on resource consumption.                    |
 
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
index 25135f65b7f3f89..a766be9a51e7892 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
@@ -38,4 +38,4 @@ You may have both of the following enabled:
 - A selection of AI crawlers to be charged through AI Crawl Control's pay per crawl
 - Bot configuration option to [Block AI Bots](/bots/get-started/bot-fight-mode/#block-ai-bots).
 
-Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
\ No newline at end of file
+Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
index 8e8f5e9661c32ef..57d1c103c3178a0 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
@@ -9,7 +9,14 @@ products:
   - ai-crawl-control
 ---
 
-import { GlossaryTooltip, Example, Steps, Tabs, TabItem, DashButton } from "~/components";
+import {
+	GlossaryTooltip,
+	Example,
+	Steps,
+	Tabs,
+	TabItem,
+	DashButton,
+} from "~/components";
 
 AI Crawl Control works alongside other Cloudflare products, such as Cloudflare [Web Application Firewall (WAF)](/waf/). WAF checks incoming web and API requests, and filters undesired traffic based on rules. [WAF custom rules](/waf/custom-rules/) allow you to perform certain actions such as enforcing <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip>.
 
@@ -132,4 +139,3 @@ Any additions you make are preserved when you subsequently update crawler action
 :::caution
 Changes made directly to the WAF rule are not reflected back in the AI Crawl Control dashboard. Use the **Crawlers** tab as your primary interface, and reserve direct WAF edits for cases where the dashboard does not cover your requirements.
 :::
-
diff --git a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
index 62af2e2d1d983dc..8ed8a785d4df4d8 100644
--- a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
+++ b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
@@ -65,12 +65,12 @@ Visualize crawler activity patterns over the selected time period. Use the view
 
 You can group the data by different dimensions:
 
-| Dimension    | Description                                                                              |
-| ------------ | ---------------------------------------------------------------------------------------- |
-| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).      |
-| **Category** | Analyze crawlers by their purpose or type.                                               |
-| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site.  |
-| **Host**     | Break down activity across multiple subdomains.                                          |
+| Dimension    | Description                                                                             |
+| ------------ | --------------------------------------------------------------------------------------- |
+| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).     |
+| **Category** | Analyze crawlers by their purpose or type.                                              |
+| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site. |
+| **Host**     | Break down activity across multiple subdomains.                                         |
 
 :::note
 The Data transfer view shows `edgeResponseBytes`. Some crawlers may show higher data transfer per request than others, depending on the content they request.
@@ -93,11 +93,11 @@ The **Content Format** chart shows what content types AI systems request versus
 
 The chart includes three views:
 
-| View          | Description                                                                 |
-| ------------- | --------------------------------------------------------------------------- |
-| **Comparison** | A grouped bar chart comparing requested content types versus served content types |
-| **Request Type** | Breakdown of requests by Accept header                                      |
-| **Response Type** | Breakdown of responses by Content-Type header                              |
+| View              | Description                                                                       |
+| ----------------- | --------------------------------------------------------------------------------- |
+| **Comparison**    | A grouped bar chart comparing requested content types versus served content types |
+| **Request Type**  | Breakdown of requests by Accept header                                            |
+| **Response Type** | Breakdown of responses by Content-Type header                                     |
 
 ### Top referrers
 
diff --git a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
index 37400acba85f698..2892e1f8c9c5aa7 100644
--- a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
+++ b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
@@ -8,7 +8,15 @@ products:
   - ai-crawl-control
 ---
 
-import { Steps, GlossaryTooltip, Tabs, TabItem, Example, Plan, DashButton } from "~/components";
+import {
+	Steps,
+	GlossaryTooltip,
+	Tabs,
+	TabItem,
+	Example,
+	Plan,
+	DashButton,
+} from "~/components";
 
 AI Crawl Control enables you to take specific action for each AI crawler.
 
@@ -25,13 +33,13 @@ To manage AI crawlers:
 
 The **Crawlers** tab displays a table of AI crawlers that are requesting access to your content, and how they interact with your pages. The table provides the following information.
 
-| Column                | Details                                                                                                                                                                                    |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                                  |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                          |
-| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control.    |
-| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                               |
-| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).                |
+| Column                | Details                                                                                                                                                                                 |
+| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                               |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                       |
+| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control. |
+| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                            |
+| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).             |
 
 :::note[Quality of AI crawler detection]
 On the free plan, AI Crawl Control identifies AI crawlers based on their [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent). This enables AI Crawl Control to detect well-known, self-identifying AI crawlers.
diff --git a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
index 8fbf42ce0120ba3..175f3072a93187a 100644
--- a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
+++ b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
@@ -29,4 +29,4 @@ Pay per crawl is currently in closed beta.
 To find out how to join the beta program, reach out to us at [Pay per crawl signup](http://www.cloudflare.com/paypercrawl-signup/), or contact your account executive if you are an existing Enterprise customer.
 
 To learn more about pay per crawl, refer to Cloudflare blog: [Introducing pay per crawl: enabling content owners to charge AI crawlers for access](https://blog.cloudflare.com/introducing-pay-per-crawl/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
index f406e702ce30ed6..6673c210889beae 100644
--- a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
+++ b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
@@ -42,12 +42,12 @@ The values in all tables and metrics will update according to your filters.
 
 The **Robots.txt availability** table shows the historical request frequency and health status of `robots.txt` files across your hostnames over the selected time frame.
 
-| Column          | Description                                                                                                                                                                                                                    |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                      |
+| Column          | Description                                                                                                                                                                                                                       |
+| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                 |
 | Requests        | The total number of requests made to this path. Requests are broken down into:<br/>- **Successful:** HTTP status codes below 400 (including **200 OK** and redirects).<br/>- **Unsuccessful:** HTTP status codes of 400 or above. |
-| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                       |
-| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                          |
+| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                          |
+| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                             |
 
 From this table, you can take the following actions:
 
diff --git a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
index 1122f0a6d7d639e..d285d0714cd426d 100644
--- a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
+++ b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
@@ -156,12 +156,12 @@ The feature parses the `<link rel="canonical">` tag from the `<head>` section of
 ```html
 <!DOCTYPE html>
 <html>
-<head>
-  <link rel="canonical" href="https://example.com/current-version">
-</head>
-<body>
-  <!-- Page content -->
-</body>
+	<head>
+		<link rel="canonical" href="https://example.com/current-version" />
+	</head>
+	<body>
+		<!-- Page content -->
+	</body>
 </html>
 ```
 
@@ -169,10 +169,10 @@ Both absolute and relative URLs are supported:
 
 ```html
 <!-- Absolute URL -->
-<link rel="canonical" href="https://example.com/page">
+<link rel="canonical" href="https://example.com/page" />
 
 <!-- Relative URL (resolved against request URL) -->
-<link rel="canonical" href="/current-page">
+<link rel="canonical" href="/current-page" />
 ```
 
 ### Interaction with other redirect features
diff --git a/src/content/docs/ai-gateway/configuration/authentication.mdx b/src/content/docs/ai-gateway/configuration/authentication.mdx
index 780ade1a3e222cc..e848745b780263d 100644
--- a/src/content/docs/ai-gateway/configuration/authentication.mdx
+++ b/src/content/docs/ai-gateway/configuration/authentication.mdx
@@ -66,7 +66,7 @@ const openai = createOpenAI({
 
 :::note
 When an AI Gateway is accessed from a Cloudflare Worker using a **binding**, the `cf-aig-authorization` header does not need to be manually included.  
-Requests made through bindings are **pre-authenticated** within the associated Cloudflare account. 
+Requests made through bindings are **pre-authenticated** within the associated Cloudflare account.
 :::
 
 The following table outlines gateway behavior based on the authentication settings and header status:
diff --git a/src/content/docs/ai-gateway/configuration/custom-providers.mdx b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
index 6da29fa5366081a..0bc6f1543a3b8fe 100644
--- a/src/content/docs/ai-gateway/configuration/custom-providers.mdx
+++ b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
@@ -373,12 +373,12 @@ Everything after `custom-{slug}/` in your request URL is appended directly to th
 
 ### Choosing between Unified API and provider-specific endpoint
 
-| | Unified API (`/compat`) | Provider-specific endpoint |
-|---|---|---|
-| **Best for** | Providers with OpenAI-compatible APIs | Providers with any API structure |
-| **Request format** | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
-| **Path control** | Fixed to `/compat/chat/completions` | Full control over the upstream path |
-| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}` | URL path: `/custom-{slug}/{path}` |
+|                                 | Unified API (`/compat`)                           | Provider-specific endpoint                |
+| ------------------------------- | ------------------------------------------------- | ----------------------------------------- |
+| **Best for**                    | Providers with OpenAI-compatible APIs             | Providers with any API structure          |
+| **Request format**              | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
+| **Path control**                | Fixed to `/compat/chat/completions`               | Full control over the upstream path       |
+| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}`       | URL path: `/custom-{slug}/{path}`         |
 
 Use the **Unified API** when your custom provider accepts the OpenAI-compatible `/chat/completions` request format. This is the simplest option and works well with OpenAI SDKs.
 
@@ -425,10 +425,12 @@ The following examples show how to configure `base_url` and construct request UR
 Many providers follow the OpenAI convention of hosting their API at `{domain}/v1/chat/completions`.
 
 **Configuration:**
+
 - `slug`: `my-openai-compat`
 - `base_url`: `https://api.example-provider.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-openai-compat/v1/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -448,6 +450,7 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-op
 | Upstream URL | `https://api.example-provider.com/v1/chat/completions` |
 
 Since this provider is OpenAI-compatible, you could also use the Unified API:
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -463,10 +466,12 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/
 Some providers use API paths that don't follow the `/v1/` convention. For example, a provider whose chat endpoint is at `https://api.custom-ai.com/api/coding/paas/v4/chat/completions`.
 
 **Configuration:**
+
 - `slug`: `custom-ai`
 - `base_url`: `https://api.custom-ai.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-custom-ai/api/coding/paas/v4/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -494,10 +499,12 @@ For providers with non-standard paths, you must use the provider-specific endpoi
 If you host your own model behind a reverse proxy or on a platform that adds a path prefix, include only the fixed prefix portion in `base_url` if all your endpoints share it. Otherwise, keep `base_url` as just the domain.
 
 **Configuration (domain-only `base_url`):**
+
 - `slug`: `internal-llm`
 - `base_url`: `https://ml.internal.example.com`
 
 **Provider-specific endpoint:**
+
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-internal-llm/serving/models/my-model:predict \
   -H "Authorization: Bearer $INTERNAL_API_KEY" \
@@ -520,10 +527,12 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-inter
 When using the OpenAI SDK to connect to a custom provider through AI Gateway, set the SDK's `base_url` to the gateway's provider-specific endpoint path (up to and including the API version prefix that your provider expects).
 
 **Configuration:**
+
 - `slug`: `alt-provider`
 - `base_url`: `https://api.alt-provider.com`
 
 **Python (OpenAI SDK):**
+
 ```python title="Using OpenAI SDK with a custom provider"
 from openai import OpenAI
 
@@ -559,14 +568,14 @@ response = client.chat.completions.create(
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1003,
-      "message": "A custom provider with this slug already exists",
-      "path": ["body", "slug"]
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1003,
+			"message": "A custom provider with this slug already exists",
+			"path": ["body", "slug"]
+		}
+	]
 }
 ```
 
@@ -576,13 +585,13 @@ Each custom provider slug must be unique within your account. Choose a different
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1004,
-      "message": "Custom Provider not found"
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1004,
+			"message": "Custom Provider not found"
+		}
+	]
 }
 ```
 
@@ -592,14 +601,14 @@ The specified provider ID does not exist or you don't have access to it. Verify
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 1002,
-      "message": "base_url must be a valid HTTPS URL starting with https://",
-      "path": ["body", "base_url"]
-    }
-  ]
+	"success": false,
+	"errors": [
+		{
+			"code": 1002,
+			"message": "base_url must be a valid HTTPS URL starting with https://",
+			"path": ["body", "base_url"]
+		}
+	]
 }
 ```
 
@@ -636,4 +645,4 @@ If you receive a 404 from the upstream provider, the most common cause is an inc
 - [BYOK (Store Keys)](/ai-gateway/configuration/bring-your-own-keys/)
 - [Dynamic routing](/ai-gateway/features/dynamic-routing/)
 - [Caching](/ai-gateway/features/caching/)
-- [Rate limiting](/ai-gateway/features/rate-limiting/)
\ No newline at end of file
+- [Rate limiting](/ai-gateway/features/rate-limiting/)
diff --git a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
index 1583cae3d3cb063..591a2b78db5305d 100644
--- a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
+++ b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
@@ -8,6 +8,7 @@ sidebar:
 products:
   - ai-gateway
 ---
+
 import { DashButton } from "~/components";
 
 Human feedback is a valuable metric to assess the performance of your AI models. By incorporating human feedback, you can gain deeper insights into how the model's responses are perceived and how well it performs from a user-centric perspective. This feedback can then be used in evaluations to calculate performance metrics, driving optimization and ultimately enhancing the reliability, accuracy, and efficiency of your AI application.
diff --git a/src/content/docs/ai-gateway/features/dlp/index.mdx b/src/content/docs/ai-gateway/features/dlp/index.mdx
index fed23035a215241..1a2da0f59706eda 100644
--- a/src/content/docs/ai-gateway/features/dlp/index.mdx
+++ b/src/content/docs/ai-gateway/features/dlp/index.mdx
@@ -59,11 +59,11 @@ Because of this buffering:
 
 DLP scanning runs after a cache miss, when AI Gateway forwards the request to the provider and receives a response. The following table describes how each DLP outcome affects caching:
 
-| DLP outcome | Response cached | Behavior |
-| --- | --- | --- |
-| Pass (no findings) | Yes | The response is cached normally according to your gateway cache settings. |
-| Flag | Yes | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
-| Block | No | The provider response is discarded and replaced with a DLP error response (status `400`). |
+| DLP outcome        | Response cached | Behavior                                                                                                                                                                  |
+| ------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pass (no findings) | Yes             | The response is cached normally according to your gateway cache settings.                                                                                                 |
+| Flag               | Yes             | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
+| Block              | No              | The provider response is discarded and replaced with a DLP error response (status `400`).                                                                                 |
 
 **Cache hits skip DLP scanning.** When a subsequent identical request matches a cached response, AI Gateway serves it directly from cache without re-running DLP. This is safe because only responses that already passed DLP (or were flagged, not blocked) are cached. However, if you update your DLP policies after a response has been cached, the cached response is not re-evaluated. It continues to be served until the cache TTL expires.
 
diff --git a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
index 72c2fa37068d4d0..fc4d9ee983694c4 100644
--- a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
+++ b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
@@ -92,8 +92,7 @@ export default {
 
 ## Response Metadata
 
-The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers 
+The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers
 
 - `cf-aig-model` - The model used
 - `cf-aig-provider` - The slug of provider used
-
diff --git a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
index d03c6eb9622ec7d..04c450d92911bd4 100644
--- a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
+++ b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
@@ -124,7 +124,7 @@ You will be prompted to log in after you run `wrangler dev`. When you run `npx w
 
 ```json
 {
-  "response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
+	"response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
 }
 ```
 
diff --git a/src/content/docs/ai-gateway/mcp-server.mdx b/src/content/docs/ai-gateway/mcp-server.mdx
index 9cb472e8825884a..5d7ff3bfddb2e49 100644
--- a/src/content/docs/ai-gateway/mcp-server.mdx
+++ b/src/content/docs/ai-gateway/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - ai-gateway
----
\ No newline at end of file
+---
diff --git a/src/content/docs/ai-gateway/observability/logging/index.mdx b/src/content/docs/ai-gateway/observability/logging/index.mdx
index cfcd1cab3d1200c..1ee3a267485ed02 100644
--- a/src/content/docs/ai-gateway/observability/logging/index.mdx
+++ b/src/content/docs/ai-gateway/observability/logging/index.mdx
@@ -55,9 +55,9 @@ The `cf-aig-collect-log-payload` header allows you to control whether the raw re
 
 This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completion data.
 
-| Header value | Behavior |
-| ------------ | -------- |
-| `true`       | Request and response payloads are stored. |
+| Header value | Behavior                                                               |
+| ------------ | ---------------------------------------------------------------------- |
+| `true`       | Request and response payloads are stored.                              |
 | `false`      | Payload storage is skipped. Metadata-only log entries are still saved. |
 
 In the example below, we use `cf-aig-collect-log-payload` to skip storing the request and response bodies while keeping the metadata log.
diff --git a/src/content/docs/ai-gateway/reference/audit-logs.mdx b/src/content/docs/ai-gateway/reference/audit-logs.mdx
index 0cfe7251d9d7c8a..250b377c6c517ee 100644
--- a/src/content/docs/ai-gateway/reference/audit-logs.mdx
+++ b/src/content/docs/ai-gateway/reference/audit-logs.mdx
@@ -5,6 +5,7 @@ pcx_content_type: concept
 products:
   - ai-gateway
 ---
+
 import { DashButton } from "~/components";
 
 [Audit logs](/fundamentals/account/account-security/review-audit-logs/) provide a comprehensive summary of changes made within your Cloudflare account, including those made to gateways in AI Gateway. This functionality is available on all plan types, free of charge, and is enabled by default.
@@ -13,7 +14,7 @@ import { DashButton } from "~/components";
 
 To view audit logs for AI Gateway, in the Cloudflare dashboard, go to the **Audit logs** page.
 
-  <DashButton url="/?to=/:account/audit-log" />
+<DashButton url="/?to=/:account/audit-log" />
 
 For more information on how to access and use audit logs, refer to [review audit logs documentation](/fundamentals/account/account-security/review-audit-logs/).
 
@@ -33,39 +34,39 @@ Below is an example of an audit log entry showing the creation of a new gateway:
 
 ```json
 {
- "action": {
-     "info": "gateway created",
-     "result": true,
-     "type": "create"
- },
- "actor": {
-     "email": "<ACTOR_EMAIL>",
-     "id": "3f7b730e625b975bc1231234cfbec091",
-     "ip": "fe32:43ed:12b5:526::1d2:13",
-     "type": "user"
- },
- "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
- "interface": "UI",
- "metadata": {},
- "newValue": "",
- "newValueJson": {
-     "cache_invalidate_on_update": false,
-     "cache_ttl": 0,
-     "collect_logs": true,
-     "id": "test",
-     "rate_limiting_interval": 0,
-     "rate_limiting_limit": 0,
-     "rate_limiting_technique": "fixed"
- },
- "oldValue": "",
- "oldValueJson": {},
- "owner": {
-     "id": "1234d848c0b9e484dfc37ec392b5fa8a"
- },
- "resource": {
-     "id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
-     "type": "ai_gateway.gateway"
- },
- "when": "2024-07-17T14:06:11.425Z"
+	"action": {
+		"info": "gateway created",
+		"result": true,
+		"type": "create"
+	},
+	"actor": {
+		"email": "<ACTOR_EMAIL>",
+		"id": "3f7b730e625b975bc1231234cfbec091",
+		"ip": "fe32:43ed:12b5:526::1d2:13",
+		"type": "user"
+	},
+	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+	"interface": "UI",
+	"metadata": {},
+	"newValue": "",
+	"newValueJson": {
+		"cache_invalidate_on_update": false,
+		"cache_ttl": 0,
+		"collect_logs": true,
+		"id": "test",
+		"rate_limiting_interval": 0,
+		"rate_limiting_limit": 0,
+		"rate_limiting_technique": "fixed"
+	},
+	"oldValue": "",
+	"oldValueJson": {},
+	"owner": {
+		"id": "1234d848c0b9e484dfc37ec392b5fa8a"
+	},
+	"resource": {
+		"id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
+		"type": "ai_gateway.gateway"
+	},
+	"when": "2024-07-17T14:06:11.425Z"
 }
 ```
diff --git a/src/content/docs/ai-gateway/reference/limits.mdx b/src/content/docs/ai-gateway/reference/limits.mdx
index 5c0459bc75ae5e7..8b130857ad0477c 100644
--- a/src/content/docs/ai-gateway/reference/limits.mdx
+++ b/src/content/docs/ai-gateway/reference/limits.mdx
@@ -33,11 +33,14 @@ The following limits apply to gateway configurations, logs, and related features
 <sup>1</sup> When you reach the log storage limit for a gateway, you can
 configure your gateway to either automatically delete the oldest logs to make
 room for new ones, or stop saving new logs. You can also use
-[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to
-external storage. Refer to [Automatic log deletion](/ai-gateway/observability/logging/#automatic-log-deletion)
-for more details.
-
-<sup>2</sup> On the free plan, the log storage limit applies to total logs across all gateways in your account. Same auto-delete or stop-saving behavior as <sup>1</sup>.
+[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to external
+storage. Refer to [Automatic log
+deletion](/ai-gateway/observability/logging/#automatic-log-deletion) for more
+details.
+
+<sup>2</sup> On the free plan, the log storage limit applies to total logs
+across all gateways in your account. Same auto-delete or stop-saving behavior as
+<sup>1</sup>.
 
 <sup>3</sup> Logs larger than 10 MB will not be stored.
 
diff --git a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
index 9f0277bdd3a1ac7..d55b0392378c965 100644
--- a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
+++ b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
@@ -106,12 +106,12 @@ The response includes a prediction `id`:
 
 ```json
 {
-  "id": "xyz789...",
-  "status": "starting",
-  "urls": {
-    "get": "https://api.replicate.com/v1/predictions/xyz789...",
-    "cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
-  }
+	"id": "xyz789...",
+	"status": "starting",
+	"urls": {
+		"get": "https://api.replicate.com/v1/predictions/xyz789...",
+		"cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
+	}
 }
 ```
 
@@ -127,7 +127,7 @@ Keep polling until `status` is `succeeded` (or `failed`). When complete, the `ou
 
 ## Next steps
 
-From here you can: 
+From here you can:
 
 - Use [logging](/ai-gateway/observability/logging/) to monitor requests and debug issues.
 - Set up [rate limiting](/ai-gateway/features/rate-limiting/) to control usage.
diff --git a/src/content/docs/ai-gateway/usage/chat-completion.mdx b/src/content/docs/ai-gateway/usage/chat-completion.mdx
index 1280237dc0187bb..c1dbd0f663fb740 100644
--- a/src/content/docs/ai-gateway/usage/chat-completion.mdx
+++ b/src/content/docs/ai-gateway/usage/chat-completion.mdx
@@ -11,11 +11,7 @@ products:
   - ai-gateway
 ---
 
-import {
-	Details,
-  Tabs,
-  TabItem
-} from "~/components";
+import { Details, Tabs, TabItem } from "~/components";
 import CodeSnippets from "~/components/ai-gateway/code-examples.astro";
 
 :::caution[Deprecated]
diff --git a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
index 7c7d8622dd1be29..aa1ad566a1a3a37 100644
--- a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
@@ -11,6 +11,7 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 [Anthropic](https://www.anthropic.com/) helps build reliable, interpretable, and steerable AI systems.
 
 ## Endpoint
+
 **Base URL**
 
 ```txt
@@ -124,17 +125,18 @@ import Anthropic from "@anthropic-ai/sdk";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic`;
 
 const anthropic = new Anthropic({
-	baseURL,
-	defaultHeaders: {
-		Authorization: `Bearer {cf_api_token}`,
-	},
+baseURL,
+defaultHeaders: {
+Authorization: `Bearer {cf_api_token}`,
+},
 });
 
 const message = await anthropic.messages.create({
-	model: "claude-sonnet-4-5",
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
-	max_tokens: 1024,
+model: "claude-sonnet-4-5",
+messages: [{ role: "user", content: "What is Cloudflare?" }],
+max_tokens: 1024,
 });
+
 ```
 </Details>
 
@@ -151,3 +153,4 @@ const message = await anthropic.messages.create({
     }}
 
 />
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
index bbda8d88dad78df..33bc4a3a7827002 100644
--- a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
@@ -52,14 +52,14 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{
 import { AzureOpenAI } from "openai";
 
 const azure_openai = new AzureOpenAI({
-  apiKey: "{azure_api_key}",
-  baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
-  apiVersion: "2023-05-15",
-  defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
+	apiKey: "{azure_api_key}",
+	baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
+	apiVersion: "2023-05-15",
+	defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
 });
 
 const result = await azure_openai.chat.completions.create({
-  model: '{deployment_name}',
-  messages: [{ role: "user", content: "Hello" }],
+	model: "{deployment_name}",
+	messages: [{ role: "user", content: "Hello" }],
 });
 ```
diff --git a/src/content/docs/ai-gateway/usage/providers/baseten.mdx b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
index 24877ce82f34716..54c26a43777ba18 100644
--- a/src/content/docs/ai-gateway/usage/providers/baseten.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
@@ -57,31 +57,31 @@ const gatewayId = "{gateway_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const openai = new OpenAI({
-  apiKey,
-  baseURL,
+	apiKey,
+	baseURL,
 });
 
 const model = "openai/gpt-oss-120b";
 const messages = [{ role: "user", content: "What is Cloudflare?" }];
 
 const chatCompletion = await openai.chat.completions.create({
-  model,
-  messages,
+	model,
+	messages,
 });
 
 console.log(chatCompletion);
 ```
 
 <Render
-  file="chat-completions-providers"
-  product="ai-gateway"
-  params={{
-    name: "Baseten",
-    jsonexample: `
+	file="chat-completions-providers"
+	product="ai-gateway"
+	params={{
+		name: "Baseten",
+		jsonexample: `
 {
   "model": "baseten/{model}"
-}`
-  }}
+}`,
+	}}
 />
 
 ## Model-specific endpoints
@@ -110,15 +110,15 @@ const modelId = "{model_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const response = await fetch(`${baseURL}/model/${modelId}`, {
-  method: "POST",
-  headers: {
-    "Authorization": `Bearer ${basetenApiToken}`,
-    "Content-Type": "application/json",
-  },
-  body: JSON.stringify({
-    prompt: "What is Cloudflare?",
-    max_tokens: 100,
-  }),
+	method: "POST",
+	headers: {
+		Authorization: `Bearer ${basetenApiToken}`,
+		"Content-Type": "application/json",
+	},
+	body: JSON.stringify({
+		prompt: "What is Cloudflare?",
+		max_tokens: 100,
+	}),
 });
 
 const result = await response.json();
diff --git a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
index 1f2df28b2813847..bb8f30200a44e93 100644
--- a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
@@ -43,10 +43,10 @@ AI Gateway handles this complexity for you. When you store your AWS credentials
 
 ### Authentication methods comparison
 
-| Method | `cf-aig-authorization` header | `Authorization` header | Signing |
-| --- | --- | --- | --- |
-| **BYOK (Recommended)** | `Bearer {CF_AIG_TOKEN}` | Not needed | Gateway signs automatically |
-| **Client-side signing** | `Bearer {CF_AIG_TOKEN}` | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
+| Method                  | `cf-aig-authorization` header | `Authorization` header | Signing                              |
+| ----------------------- | ----------------------------- | ---------------------- | ------------------------------------ |
+| **BYOK (Recommended)**  | `Bearer {CF_AIG_TOKEN}`       | Not needed             | Gateway signs automatically          |
+| **Client-side signing** | `Bearer {CF_AIG_TOKEN}`       | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
 
 :::caution[Do not confuse the headers]
 `cf-aig-authorization` authenticates your request to AI Gateway. When using BYOK, you do not need to include any AWS authorization headers because AI Gateway signs the request for you.
@@ -227,5 +227,3 @@ const response = await client.chat.completions.create({
 
 console.log(response.choices[0].message.content);
 ```
-
-
diff --git a/src/content/docs/ai-gateway/usage/providers/fal.mdx b/src/content/docs/ai-gateway/usage/providers/fal.mdx
index 3e67996cbae3c2d..057d6dda7144ddc 100644
--- a/src/content/docs/ai-gateway/usage/providers/fal.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/fal.mdx
@@ -78,21 +78,23 @@ The `x-fal-target-url` format is compliant with the Fal SDKs, so AI Gateway can
 import { fal } from "@fal-ai/client";
 
 fal.config({
-  credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
-  proxyUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal"
+	credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
+	proxyUrl:
+		"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal",
 });
 
 const result = await fal.subscribe("fal-ai/bytedance/seedream/v4/edit", {
-  "input": {
-    "prompt": "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
-    "image_urls": [
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
-      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png"
-    ]
-  }
+	input: {
+		prompt:
+			"Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
+		image_urls: [
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
+			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png",
+		],
+	},
 });
 
 console.log(result.data.images[0]);
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
index 7d986484bd9371b..29e542bf31fb4d9 100644
--- a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
@@ -17,6 +17,7 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 ```txt
 https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio
 ```
+
 Then you can append the endpoint you want to hit, for example: `v1/models/{model}:{generative_ai_rest_resource}`
 
 So your final URL will come together as: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio/v1/models/{model}:{generative_ai_rest_resource}`.
@@ -136,18 +137,19 @@ console.log(response.text);
 import { GoogleGenAI } from "@google/genai";
 
 const ai = new GoogleGenAI({
-  apiKey: "{cf_aig_token}",
-  httpOptions: {
-	  baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
-  }
+apiKey: "{cf_aig_token}",
+httpOptions: {
+baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
+}
 });
 
 const response = await ai.models.generateContent({
-  model: "gemini-2.5-flash",
-  contents: "What is Cloudflare?",
+model: "gemini-2.5-flash",
+contents: "What is Cloudflare?",
 });
 
 console.log(response.text);
+
 ```
 </Details>
 
@@ -164,3 +166,4 @@ console.log(response.text);
     }}
 
 />
+```
diff --git a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
index bc019d9a71628b5..e9213598bdda79c 100644
--- a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
@@ -48,17 +48,17 @@ const ideogramApiKey = "{ideogram_api_key}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/ideogram`;
 
 const response = await fetch(`${baseURL}/v1/ideogram-v3/generate`, {
-  method: "POST",
-  headers: {
-    "Api-Key": ideogramApiKey,
-    "Content-Type": "application/json",
-  },
-  body: JSON.stringify({
-    prompt: "A serene landscape with mountains and a lake at sunset",
-    model: "V_3",
-  }),
+	method: "POST",
+	headers: {
+		"Api-Key": ideogramApiKey,
+		"Content-Type": "application/json",
+	},
+	body: JSON.stringify({
+		prompt: "A serene landscape with mountains and a lake at sunset",
+		model: "V_3",
+	}),
 });
 
 const result = await response.json();
 console.log(result);
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/ai-gateway/usage/rest-api.mdx b/src/content/docs/ai-gateway/usage/rest-api.mdx
index 7dd750f9b04aca9..e2275bfa7e32b91 100644
--- a/src/content/docs/ai-gateway/usage/rest-api.mdx
+++ b/src/content/docs/ai-gateway/usage/rest-api.mdx
@@ -18,12 +18,12 @@ No provider SDKs or API keys are needed. Authentication and billing are handled
 
 Four endpoints are available, each suited to different use cases:
 
-| Endpoint | Format | Use case |
-| -------- | ------ | -------- |
-| `POST /ai/run` | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
-| `POST /ai/v1/chat/completions` | OpenAI chat completions | LLMs — OpenAI SDK compatible |
-| `POST /ai/v1/responses` | OpenAI Responses API | Agentic workflows — OpenAI SDK compatible |
-| `POST /ai/v1/messages` | Anthropic Messages API | LLMs — Anthropic SDK compatible |
+| Endpoint                       | Format                         | Use case                                         |
+| ------------------------------ | ------------------------------ | ------------------------------------------------ |
+| `POST /ai/run`                 | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
+| `POST /ai/v1/chat/completions` | OpenAI chat completions        | LLMs — OpenAI SDK compatible                     |
+| `POST /ai/v1/responses`        | OpenAI Responses API           | Agentic workflows — OpenAI SDK compatible        |
+| `POST /ai/v1/messages`         | Anthropic Messages API         | LLMs — Anthropic SDK compatible                  |
 
 ## Authentication
 
@@ -140,13 +140,13 @@ Point the OpenAI SDK `baseURL` at the Cloudflare API:
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.chat.completions.create({
-  model: "openai/gpt-4.1",
-  messages: [{ role: "user", content: "What is Cloudflare?" }],
+	model: "openai/gpt-4.1",
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -158,13 +158,13 @@ Uses the OpenAI Responses API format for agentic workflows. Compatible with the
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.responses.create({
-  model: "openai/gpt-4.1",
-  input: "What is Cloudflare?",
+	model: "openai/gpt-4.1",
+	input: "What is Cloudflare?",
 });
 ```
 
@@ -194,14 +194,14 @@ Point the Anthropic SDK `baseURL` at the Cloudflare API:
 import Anthropic from "@anthropic-ai/sdk";
 
 const anthropic = new Anthropic({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const message = await anthropic.messages.create({
-  model: "anthropic/claude-sonnet-4-5",
-  max_tokens: 512,
-  messages: [{ role: "user", content: "What is Cloudflare?" }],
+	model: "anthropic/claude-sonnet-4-5",
+	max_tokens: 512,
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -229,11 +229,11 @@ With the OpenAI SDK, set the header via `defaultHeaders`:
 
 ```javascript
 const openai = new OpenAI({
-  apiKey: CLOUDFLARE_API_TOKEN,
-  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
-  defaultHeaders: {
-    "cf-aig-gateway-id": "my-gateway",
-  },
+	apiKey: CLOUDFLARE_API_TOKEN,
+	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+	defaultHeaders: {
+		"cf-aig-gateway-id": "my-gateway",
+	},
 });
 ```
 
@@ -243,17 +243,17 @@ All AI Gateway features configured on that gateway — caching, rate limiting, g
 
 Use `cf-aig-*` headers to control AI Gateway behavior on a per-request basis:
 
-| Header | Type | Description |
-| ------ | ---- | ----------- |
-| `cf-aig-skip-cache` | boolean | Skip the cache for this request. |
-| `cf-aig-cache-ttl` | number | Cache TTL in seconds. |
-| `cf-aig-cache-key` | string | Custom cache key. |
-| `cf-aig-collect-log` | boolean | Turn logging on or off for this request. |
-| `cf-aig-request-timeout` | number | Request timeout in milliseconds. |
-| `cf-aig-max-attempts` | number | Retry attempts (max 5). |
-| `cf-aig-retry-delay` | number | Retry delay in milliseconds (max 5000). |
-| `cf-aig-backoff` | string | Backoff method: `constant`, `linear`, or `exponential`. |
-| `cf-aig-metadata` | JSON string | Custom metadata to attach to the log entry. |
+| Header                   | Type        | Description                                             |
+| ------------------------ | ----------- | ------------------------------------------------------- |
+| `cf-aig-skip-cache`      | boolean     | Skip the cache for this request.                        |
+| `cf-aig-cache-ttl`       | number      | Cache TTL in seconds.                                   |
+| `cf-aig-cache-key`       | string      | Custom cache key.                                       |
+| `cf-aig-collect-log`     | boolean     | Turn logging on or off for this request.                |
+| `cf-aig-request-timeout` | number      | Request timeout in milliseconds.                        |
+| `cf-aig-max-attempts`    | number      | Retry attempts (max 5).                                 |
+| `cf-aig-retry-delay`     | number      | Retry delay in milliseconds (max 5000).                 |
+| `cf-aig-backoff`         | string      | Backoff method: `constant`, `linear`, or `exponential`. |
+| `cf-aig-metadata`        | JSON string | Custom metadata to attach to the log entry.             |
 
 For more details on these options, refer to [Request handling](/ai-gateway/configuration/request-handling/) and [Caching](/ai-gateway/features/caching/).
 
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
index bfc911e09f973c8..dd9b384084acdcf 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
@@ -55,7 +55,7 @@ ws.on("open", () => {
 			},
 		}),
 	);
-})
+});
 
 ws.on("message", (message) => {
 	console.log(message.toString());
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
index 57c34339587a994..f444cff4c7a73ef 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
@@ -272,7 +272,7 @@ let isPlayingAudio = false;
 const rl = readline.createInterface({
 	input: process.stdin,
 	output: process.stdout,
-	prompt: "Enter text to speak (or \"quit\" to exit): ",
+	prompt: 'Enter text to speak (or "quit" to exit): ',
 });
 
 ws.onopen = () => {
diff --git a/src/content/docs/ai-search/api/instances/rest-api.mdx b/src/content/docs/ai-search/api/instances/rest-api.mdx
index 178f1c9d6c69011..37757fbb0ff5362 100644
--- a/src/content/docs/ai-search/api/instances/rest-api.mdx
+++ b/src/content/docs/ai-search/api/instances/rest-api.mdx
@@ -20,8 +20,8 @@ Use the AI Search REST API to manage instances and sync jobs over HTTP.
 
 AI Search APIs are available at two base paths:
 
-| Path                                                                 | Description                                                                 |
-| -------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| Path                                                                     | Description                                                                 |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
 | `/accounts/{account_id}/ai-search/instances/{id}`                        | Operates on a specific instance                                             |
 | `/accounts/{account_id}/ai-search/namespaces/{namespace}/instances/{id}` | Operates on instances within a [namespace](/ai-search/concepts/namespaces/) |
 
diff --git a/src/content/docs/ai-search/api/items/rest-api.mdx b/src/content/docs/ai-search/api/items/rest-api.mdx
index f23b4dd83703914..08634485801ed10 100644
--- a/src/content/docs/ai-search/api/items/rest-api.mdx
+++ b/src/content/docs/ai-search/api/items/rest-api.mdx
@@ -35,8 +35,8 @@ The available operations are the same for both paths. For the namespace-scoped A
 
 Upload, list, get, delete, and download items within an instance. For the full specification, refer to the [Items API reference](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/).
 
-| Operation                                                                                                            | Method   | Description                    |
-| -------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------ |
+| Operation                                                                                                                | Method   | Description                    |
+| ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------ |
 | [Upload](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/upload/)     | `POST`   | Upload a document for indexing |
 | [List](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/list/)         | `GET`    | List all items in an instance  |
 | [Get](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/get/)           | `GET`    | Get item info by ID            |
diff --git a/src/content/docs/ai-search/configuration/models/index.mdx b/src/content/docs/ai-search/configuration/models/index.mdx
index c406d789f32edfa..42a76abb29e721b 100644
--- a/src/content/docs/ai-search/configuration/models/index.mdx
+++ b/src/content/docs/ai-search/configuration/models/index.mdx
@@ -28,12 +28,10 @@ To use AI Search with other model providers:
 
 1. Add provider keys to [AI Gateway](/ai-gateway/configuration/bring-your-own-keys/).
 2. Connect the gateway to AI Search.
-
    - When creating a new AI Search, select the AI Gateway with your provider keys.
    - For an existing AI Search, go to **Settings** and switch to a gateway that has your keys under **Resources**.
 
 3. Select models
-
    - Embedding model: Only available to be changed when creating a new AI Search.
    - Generation model: Can be selected when creating a new AI Search and can be changed at any time in **Settings**.
 
diff --git a/src/content/docs/ai-search/how-to/nlweb.mdx b/src/content/docs/ai-search/how-to/nlweb.mdx
index 25d61bcba3c3cb7..eb36852ae5534f6 100644
--- a/src/content/docs/ai-search/how-to/nlweb.mdx
+++ b/src/content/docs/ai-search/how-to/nlweb.mdx
@@ -67,23 +67,23 @@ You can use the embeddable snippet to add a search UI directly into your website
 
 ```html
 <!-- Add css on head -->
-    <link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css">
-    <link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css">
-
-    <!-- Add container on body -->
-    <div id="docs-search-container"></div>
-
-    <!-- Include JavaScript -->
-    <script type="module">
-      import { NLWebDropdownChat } from 'https://ask.example.com/nlweb-dropdown-chat.js';
-
-      const chat = new NLWebDropdownChat({
-        containerId: 'docs-search-container',
-        site: 'https://ask.example.com',
-        placeholder: 'Search for docs...',
-        endpoint: 'https://ask.example.com'
-      });
-    </script>
+<link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css" />
+<link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css" />
+
+<!-- Add container on body -->
+<div id="docs-search-container"></div>
+
+<!-- Include JavaScript -->
+<script type="module">
+	import { NLWebDropdownChat } from "https://ask.example.com/nlweb-dropdown-chat.js";
+
+	const chat = new NLWebDropdownChat({
+		containerId: "docs-search-container",
+		site: "https://ask.example.com",
+		placeholder: "Search for docs...",
+		endpoint: "https://ask.example.com",
+	});
+</script>
 ```
 
 This lets you serve conversational AI search directly from your own domain, with control over how people and agents access your content.
diff --git a/src/content/docs/ai-search/wrangler-commands.mdx b/src/content/docs/ai-search/wrangler-commands.mdx
index f8e1fa53538eca8..916b781370d0e81 100644
--- a/src/content/docs/ai-search/wrangler-commands.mdx
+++ b/src/content/docs/ai-search/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { WranglerNamespace, WranglerCommand } from "~/components";
 
-<WranglerNamespace namespace="ai-search" />
\ No newline at end of file
+<WranglerNamespace namespace="ai-search" />
diff --git a/src/content/docs/ai/related-products/ai-gateway.mdx b/src/content/docs/ai/related-products/ai-gateway.mdx
index c868d2c8ec2fd75..75063087b321b29 100644
--- a/src/content/docs/ai/related-products/ai-gateway.mdx
+++ b/src/content/docs/ai/related-products/ai-gateway.mdx
@@ -6,5 +6,5 @@ sidebar:
 external_link: /ai-gateway/
 products:
   - ai
-  - ai-gateway  
+  - ai-gateway
 ---
diff --git a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
index 0d4aaf4a63bca3e..c5d95a03c76c5d4 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - analytics
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Cloudflare account analytics lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
@@ -18,29 +18,29 @@ Cloudflare account analytics lets you access a wide range of aggregated metrics
 For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
 :::
 
-***
+---
 
 ## View your account analytics
 
 To view metrics for your site, in the Cloudflare dashboard, go to the **Account Analytics** page.
 
-   <DashButton url="/?to=/:account/analytics" />
+<DashButton url="/?to=/:account/analytics" />
 
-Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to *Review your account metrics* below.
+Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to _Review your account metrics_ below.
 
-***
+---
 
 ## Review your account metrics
 
 This section outlines the aggregated metrics under each category. Before reviewing your metrics, let's define a couple of concepts used in some panels:
 
-* *Rate* -  Reflects the ratio between the amount for a specific data category and the total.
-* *Bandwidth* - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
+- _Rate_ -  Reflects the ratio between the amount for a specific data category and the total.
+- _Bandwidth_ - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
 
 Also, note that:
 
-* To filter metrics for a specific time period, use the dropdown in the top right.
-* Most metrics are grouped into panels representing different aspects of the underlying data.
+- To filter metrics for a specific time period, use the dropdown in the top right.
+- Most metrics are grouped into panels representing different aspects of the underlying data.
 
 ### Summary of metrics
 
@@ -52,21 +52,21 @@ These charts aggregate data for HTTP traffic, and include:
 
 ![Chart showing last week's data for HTTP traffic](~/assets/images/support/hc-dash-account-analytics-map.png)
 
-* Spark lines for *Requests*, *Bandwidth*, *Page views*, and *Visitors* (*Unique IPs)*
-* An interactive map that breaks down the number of requests by country
-* A table combining numerical and spark line data, sorted by total number of requests per country
+- Spark lines for _Requests_, _Bandwidth_, _Page views_, and _Visitors_ (_Unique IPs)_
+- An interactive map that breaks down the number of requests by country
+- A table combining numerical and spark line data, sorted by total number of requests per country
 
 #### Security
 
 ![Panel displaying lines highlighting encryption metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_security_panel.png)
 
-This panel features spark lines highlighting various encryption metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous period.
+This panel features spark lines highlighting various encryption metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous period.
 
 #### Cache
 
 ![Panel displaying lines for caching metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_cache_card.png)
 
-This panel features spark lines for various caching metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected *Last week* as your time period, the previous period refers to the *week* before.
+This panel features spark lines for various caching metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected _Last week_ as your time period, the previous period refers to the _week_ before.
 
 #### Errors
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
index 76dccf882a47092..84e856b537c7e3a 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
@@ -13,7 +13,7 @@ Learn how Cloudflare analytics tracks requests made by [Cloudflare Workers](/wor
 
 With a no-op Worker (a Worker that simply proxies traffic by passing on the original client request to the origin and proxying the response) running on a particular route, the request to the origin is counted as a 'subrequest', separate from initial client to edge request. Thus, unless the Worker responds with a static response and never hits an origin, the eyeball → edge request, and edge → origin request will each be counted separately towards the request or bandwidth count in Analytics. Subrequests are not included in the **Requests** or **Bandwidth** graphs of the Cloudflare **Analytics** app.
 
-***
+---
 
 ## Zone analytics
 
@@ -21,20 +21,20 @@ In the dashboard, the numbers in zone analytics reflect visitor traffic. That is
 
 Similarly, the bandwidth is counted based on the bandwidth that is sent to the client, and status codes reflect the status codes that were served back to the client (so if a subrequest received a 500, but you respond with a 200, a 200 will be shown in the status codes breakdown).
 
-***
+---
 
 ## Worker analytics
 
 For a breakdown of subrequest traffic (origin facing traffic), you may go to the Cloudflare **Analytics** app and select the **Workers** tab. Under the **Workers** tab, below the Service Workers panel, are a **Subrequests** breakdown by count, **Bandwidth** and **Status Codes**. This will help you spot and debug errors at your origin (such as spikes in 500s), and identify your cache-hit ratio to help you understand traffic going to your origin.
 
-***
+---
 
 ## FAQ
 
 **Why do I not have any analytics for Workers?**
 
-* If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
-* If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
+- If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
+- If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
 
 **Will this impact billing?** 
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/index.mdx b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
index 54e99ae3cb5ec74..2aeb75e8f6f6dc4 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/index.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Visit the following pages to learn more about account and zone analytics:
 
diff --git a/src/content/docs/analytics/analytics-engine/grafana.mdx b/src/content/docs/analytics/analytics-engine/grafana.mdx
index e6af88fd7a7a901..96310e19e31d8cc 100644
--- a/src/content/docs/analytics/analytics-engine/grafana.mdx
+++ b/src/content/docs/analytics/analytics-engine/grafana.mdx
@@ -20,10 +20,10 @@ We recommend the use of the [Altinity plugin for Clickhouse](https://grafana.com
 
 Configure the plugin as follows:
 
-* URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
-* Leave all auth settings off.
-* Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
-* No other options need to be set.
+- URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
+- Leave all auth settings off.
+- Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
+- No other options need to be set.
 
 ## Querying timeseries data
 
@@ -35,8 +35,8 @@ SELECT
     blob1 AS label,
     SUM(_sample_interval * double1) / SUM(_sample_interval) AS average_metric
 FROM dataset_name
-WHERE 
-    timestamp <= NOW() 
+WHERE
+    timestamp <= NOW()
     AND timestamp > NOW() - INTERVAL '1' DAY
 GROUP BY blob1, t
 ORDER BY t
diff --git a/src/content/docs/analytics/analytics-engine/index.mdx b/src/content/docs/analytics/analytics-engine/index.mdx
index 2eae0d36b0eab7d..ddee07f45c1808c 100644
--- a/src/content/docs/analytics/analytics-engine/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/index.mdx
@@ -8,15 +8,17 @@ products:
   - workers-analytics-engine
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 Workers Analytics Engine provides unlimited-cardinality analytics at scale, via [a built-in API](/analytics/analytics-engine/get-started/) to write data points from Workers, and a [SQL API](/analytics/analytics-engine/sql-api/) to query that data.
 
 You can use Workers Analytics Engine to:
 
-* Expose custom analytics to your own customers
-* Build usage-based billing systems
-* Understand the health of your service on a per-customer or per-user basis
-* Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
+- Expose custom analytics to your own customers
+- Build usage-based billing systems
+- Understand the health of your service on a per-customer or per-user basis
+- Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
 
- <LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">Get started</LinkButton>
+<LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">
+	Get started
+</LinkButton>
diff --git a/src/content/docs/analytics/analytics-engine/limits.mdx b/src/content/docs/analytics/analytics-engine/limits.mdx
index 293093c33e3343b..d4eb97a73b95fcb 100644
--- a/src/content/docs/analytics/analytics-engine/limits.mdx
+++ b/src/content/docs/analytics/analytics-engine/limits.mdx
@@ -13,10 +13,10 @@ products:
 
 The following limits apply to Workers Analytics Engine:
 
-* Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
-* The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
-* Each index must not be more than 96 bytes.
-* You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
+- Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
+- The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
+- Each index must not be more than 96 bytes.
+- You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
 
 ## Data retention
 
diff --git a/src/content/docs/analytics/analytics-engine/pricing.mdx b/src/content/docs/analytics/analytics-engine/pricing.mdx
index 059f55deae8360d..bef373bc86ebf85 100644
--- a/src/content/docs/analytics/analytics-engine/pricing.mdx
+++ b/src/content/docs/analytics/analytics-engine/pricing.mdx
@@ -23,7 +23,7 @@ Workers Analytics Engine is priced based on two metrics — data points written
 
 Currently, you will not be billed for your use of Workers Analytics Engine. Pricing information here is shared in advance, so that you can estimate what your costs will be once Cloudflare starts billing for usage in the coming months.
 
-If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing. 
+If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing.
 :::
 
 ### Data points written
diff --git a/src/content/docs/analytics/analytics-engine/recipes/index.mdx b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
index f0a1bab71954b46..17c5d1b314b065e 100644
--- a/src/content/docs/analytics/analytics-engine/recipes/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Example implementations of common use cases for Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sampling.mdx b/src/content/docs/analytics/analytics-engine/sampling.mdx
index c358eadeb8f377c..bc8b75c9cac7e72 100644
--- a/src/content/docs/analytics/analytics-engine/sampling.mdx
+++ b/src/content/docs/analytics/analytics-engine/sampling.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](https://en.wikipedia.org/wiki/Sampling_\(statistics\)).
+Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>).
 
 When utilizing sampling, you do not need every single data point to answer questions about a dataset. For a sufficiently large dataset, the [necessary sample size](https://select-statistics.co.uk/blog/importance-effect-sample-size/) does not depend on the size of the original population. Necessary sample size depends on the variance of your measure, the size of the subgroups you analyze, and how accurate your estimate must be.
 
@@ -24,11 +24,11 @@ At a high level, the way sampling works is:
 
 In the following sections, you will learn:
 
-* [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
-* [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
-* [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
-* [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
-* [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
+- [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
+- [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
+- [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
+- [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
+- [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
 
 ## How sampling works
 
@@ -44,15 +44,15 @@ The key point is that the map's quality does not solely depend on the resolution
 
 There are similarities between the how a mapping services handles resolution and Cloudflare Analytics delivers analytics using adaptive samples:
 
-* **How data is stored**:
-  * **Mapping service**: Imagery stored at different resolutions.
-  * **Cloudflare Analytics**: Events stored at different sample rates.
-* **How data is displayed to user**:
-  * **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
-  * **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
-* **How a resolution is selected**:
-  * **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
-  * **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
+- **How data is stored**:
+  - **Mapping service**: Imagery stored at different resolutions.
+  - **Cloudflare Analytics**: Events stored at different sample rates.
+- **How data is displayed to user**:
+  - **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
+  - **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
+- **How a resolution is selected**:
+  - **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
+  - **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
 
 ## How to read sampled data
 
@@ -87,11 +87,11 @@ If we took a [simple random sample](https://en.wikipedia.org/wiki/Simple_random_
 
 ![The same graphic as above, but now based on a 1% sample of the data.](~/assets/images/analytics/sample-data.png)
 
-Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](https://en.wikipedia.org/wiki/Quantization_\(signal_processing\)) and may even be rounded to 0 entirely.
+Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](<https://en.wikipedia.org/wiki/Quantization_(signal_processing)>) and may even be rounded to 0 entirely.
 
 This shows that while a one percent (1%) or even smaller sample of a large population may be sufficient, we may need to store a larger proportion of events for a small population to get accurate results.
 
-We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`.  But if you write lots of data points to a single index value, we will start to sample.
+We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`. But if you write lots of data points to a single index value, we will start to sample.
 
 Here is the same distribution, but now with (a simulation of) equitable sampling applied:
 
@@ -117,23 +117,23 @@ In order to get accurate results with sampled data, select an appropriate value
 
 The index has the following properties, which are important to consider when choosing an index:
 
-* Get accurate summary statistics about your entire dataset, across all index values.
-* Get an accurate count of the number of unique values of your index.
-* Get accurate summary statistics (for example, count, sum) within a particular index value.
-* See the `Top N` values of specific fields that are not in your index.
-* Filter on most fields.
-* Run other aggregations like quantiles.
+- Get accurate summary statistics about your entire dataset, across all index values.
+- Get an accurate count of the number of unique values of your index.
+- Get accurate summary statistics (for example, count, sum) within a particular index value.
+- See the `Top N` values of specific fields that are not in your index.
+- Filter on most fields.
+- Run other aggregations like quantiles.
 
 Some limitations and trade-offs to consider are:
 
-* You may not be able to get accurate unique counts of fields that are not in your index.
-  * For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
-* You may not be able to observe very rare values of fields not in the index.
-  * For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
-* You may not be able to run accurate queries across multiple indices at once.
-  * For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
-* There is no guarantee you can retrieve any one individual record.
-* You cannot necessarily reconstruct exact sequences of events.
+- You may not be able to get accurate unique counts of fields that are not in your index.
+  - For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
+- You may not be able to observe very rare values of fields not in the index.
+  - For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
+- You may not be able to run accurate queries across multiple indices at once.
+  - For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
+- There is no guarantee you can retrieve any one individual record.
+- You cannot necessarily reconstruct exact sequences of events.
 
 It is not recommended to write a unique index value on every row (like a UUID) for most use cases. While this will make it possible to retrieve individual data points very quickly, it will slow down most queries for aggregations and time series.
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-api.mdx b/src/content/docs/analytics/analytics-engine/sql-api.mdx
index 55cfccf8e90d48f..1801c7d93dbaf1a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-api.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-api.mdx
@@ -25,10 +25,10 @@ Use the dashboard to create a token with permission to read analytics data on yo
 2. Select **Create Token**.
 3. Select **Create Custom Token**.
 4. Complete the **Create Custom Token** form as follows:
-   * Give your token a descriptive name.
-   * For **Permissions** select *Account* | *Account Analytics* | *Read*
-   * Optionally configure account and IP restrictions and TTL.
-   * Submit and confirm the form to create the token.
+   - Give your token a descriptive name.
+   - For **Permissions** select _Account_ | _Account Analytics_ | _Read_
+   - Optionally configure account and IP restrictions and TTL.
+   - Submit and confirm the form to create the token.
 5. Make a note of the token string.
 
 ## Querying the API
@@ -63,7 +63,7 @@ The table will have the following columns:
 | ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | dataset                      | string   | This column will contain the dataset name in every row.                                                                                                                                                                                              |
 | timestamp                    | DateTime | The timestamp at which the event was logged in your worker.                                                                                                                                                                                          |
-| \_sample\_interval           | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
+| \_sample_interval            | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
 | index1                       | string   | The index value that was logged with the event. The value in this column is used as the key for sampling.                                                                                                                                            |
 | blob1<br/>...<br/>blob20     | string   | The blob values that were logged with the event.                                                                                                                                                                                                     |
 | double1<br/>...<br/>double20 | double   | The double values that were logged with the event.                                                                                                                                                                                                   |
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
index 4d1827c650f3567..62e8e01ba6ec69f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## count
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
index f8d061a0f4b5635..9a64750c492178a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## bitAnd <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
index 9db9dac5fb7d21a..46e2141c8ef25e0 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## formatDateTime
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
index 851779802af43f3..016f68450f83fef 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## bin <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
index ebe0124792308e4..e8a324356d02009 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Reference documentation describing the SQL supported by Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
index ba40ae26a6009c2..97035f5a95abd0e 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## intDiv
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
index 9a4b8089ef3d6c5..40411492466534f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
@@ -12,7 +12,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## length
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
index f87f1a7eb19e146..1ddf69b03623497 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components"
+import { Badge } from "~/components";
 
 ## toUInt8 <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/worker-querying.mdx b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
index 81c7b08511cf5ca..0a8521edc362e68 100644
--- a/src/content/docs/analytics/analytics-engine/worker-querying.mdx
+++ b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
@@ -11,7 +11,6 @@ products:
   - workers-analytics-engine
 ---
 
-
 import { WranglerConfig } from "~/components";
 
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
diff --git a/src/content/docs/analytics/analytics-integrations/datadog.mdx b/src/content/docs/analytics/analytics-integrations/datadog.mdx
index 579cc03b68a207a..07af42f65157723 100644
--- a/src/content/docs/analytics/analytics-integrations/datadog.mdx
+++ b/src/content/docs/analytics/analytics-integrations/datadog.mdx
@@ -36,7 +36,6 @@ To install the Cloudflare App for Datadog:
 4. Click the **Cloudflare** tile to begin the installation.
 
 5. Next, click **Configuration** and then complete the following:
-
    - **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
 
    - **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
diff --git a/src/content/docs/analytics/analytics-integrations/index.mdx b/src/content/docs/analytics/analytics-integrations/index.mdx
index 12212b2b3fbc24f..f97ccae2ade7ad9 100644
--- a/src/content/docs/analytics/analytics-integrations/index.mdx
+++ b/src/content/docs/analytics/analytics-integrations/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare Enterprise customers can use Cloudflare integrations with their preferred analytics provider and configure ready-to-use Cloudflare Dashboards. Most analytics integrations are built on Cloudflare Logs by using Logpush with either Amazon S3 bucket or GCP Storage bucket.
 
diff --git a/src/content/docs/analytics/analytics-integrations/prometheus.mdx b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
index 10a355c84e93b3d..bcee11a6e7f26eb 100644
--- a/src/content/docs/analytics/analytics-integrations/prometheus.mdx
+++ b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
@@ -59,16 +59,16 @@ Create a Cloudflare API token with the following permissions:
 
 [Create token with pre-filled permissions](https://dash.cloudflare.com/profile/api-tokens?permissionGroupKeys=%5B%7B%22key%22%3A%22analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22workers_scripts%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22ssl_and_certificates%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22firewall_services%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22load_balancers%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_logs%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22magic_transit%22%2C%22type%22%3A%22read%22%7D%5D&name=Cloudflare%20Prometheus%20Exporter)
 
-| Permission | Access | Required |
-|---|---|---|
-| Zone > Analytics | Read | Yes |
-| Account > Account Analytics | Read | Yes |
-| Account > Workers Scripts | Read | Yes |
-| Zone > SSL and Certificates | Read | Optional |
-| Zone > Firewall Services | Read | Optional |
-| Zone > Load Balancers | Read | Optional |
-| Account > Logs | Read | Optional |
-| Account > Magic Transit | Read | Optional |
+| Permission                  | Access | Required |
+| --------------------------- | ------ | -------- |
+| Zone > Analytics            | Read   | Yes      |
+| Account > Account Analytics | Read   | Yes      |
+| Account > Workers Scripts   | Read   | Yes      |
+| Zone > SSL and Certificates | Read   | Optional |
+| Zone > Firewall Services    | Read   | Optional |
+| Zone > Load Balancers       | Read   | Optional |
+| Account > Logs              | Read   | Optional |
+| Account > Magic Transit     | Read   | Optional |
 
 ## Task 3 - Configure Prometheus
 
@@ -76,11 +76,11 @@ Add the exporter as a scrape target in your Prometheus configuration:
 
 ```yaml
 scrape_configs:
-  - job_name: 'cloudflare'
+  - job_name: "cloudflare"
     scrape_interval: 60s
     scrape_timeout: 30s
     static_configs:
-      - targets: ['your-worker.your-subdomain.workers.dev']
+      - targets: ["your-worker.your-subdomain.workers.dev"]
 ```
 
 ### With Basic Auth
@@ -89,14 +89,14 @@ If you configured Basic Auth on the exporter, update your Prometheus configurati
 
 ```yaml
 scrape_configs:
-  - job_name: 'cloudflare'
+  - job_name: "cloudflare"
     scrape_interval: 60s
     scrape_timeout: 30s
     basic_auth:
-      username: 'your-username'
-      password: 'your-password'
+      username: "your-username"
+      password: "your-password"
     static_configs:
-      - targets: ['your-worker.your-subdomain.workers.dev']
+      - targets: ["your-worker.your-subdomain.workers.dev"]
 ```
 
 ## Configuration
@@ -105,32 +105,32 @@ Configuration is resolved in order: **KV overrides** > **environment variables**
 
 Set environment variables in `wrangler.jsonc` or via `wrangler secret put`:
 
-| Variable | Default | Description |
-|---|---|---|
-| `CLOUDFLARE_API_TOKEN` | - | Cloudflare API token (secret) |
-| `SCRAPE_DELAY_SECONDS` | `300` | Delay before fetching metrics (data propagation) |
-| `TIME_WINDOW_SECONDS` | `60` | Query time window |
-| `METRIC_REFRESH_INTERVAL_SECONDS` | `60` | Background refresh interval |
-| `CF_ACCOUNTS` | - | Comma-separated account IDs to include (default: all) |
-| `CF_ZONES` | - | Comma-separated zone IDs to include (default: all) |
-| `METRICS_DENYLIST` | - | Comma-separated list of metrics to exclude |
-| `EXCLUDE_HOST` | `false` | Exclude host labels from metrics |
-| `METRICS_PATH` | `/metrics` | Custom path for metrics endpoint |
-| `BASIC_AUTH_USER` | - | Username for Basic Auth (secret) |
-| `BASIC_AUTH_PASSWORD` | - | Password for Basic Auth (secret) |
+| Variable                          | Default    | Description                                           |
+| --------------------------------- | ---------- | ----------------------------------------------------- |
+| `CLOUDFLARE_API_TOKEN`            | -          | Cloudflare API token (secret)                         |
+| `SCRAPE_DELAY_SECONDS`            | `300`      | Delay before fetching metrics (data propagation)      |
+| `TIME_WINDOW_SECONDS`             | `60`       | Query time window                                     |
+| `METRIC_REFRESH_INTERVAL_SECONDS` | `60`       | Background refresh interval                           |
+| `CF_ACCOUNTS`                     | -          | Comma-separated account IDs to include (default: all) |
+| `CF_ZONES`                        | -          | Comma-separated zone IDs to include (default: all)    |
+| `METRICS_DENYLIST`                | -          | Comma-separated list of metrics to exclude            |
+| `EXCLUDE_HOST`                    | `false`    | Exclude host labels from metrics                      |
+| `METRICS_PATH`                    | `/metrics` | Custom path for metrics endpoint                      |
+| `BASIC_AUTH_USER`                 | -          | Username for Basic Auth (secret)                      |
+| `BASIC_AUTH_PASSWORD`             | -          | Password for Basic Auth (secret)                      |
 
 For a full list of configuration options, refer to the [exporter README](https://github.com/cloudflare/cloudflare-prometheus-exporter#configuration).
 
 ## Endpoints
 
-| Path | Method | Description |
-|---|---|---|
-| `/` | GET | Landing page |
-| `/metrics` | GET | Prometheus metrics |
-| `/health` | GET | Health check |
-| `/config` | GET | Get all runtime config |
-| `/config/:key` | PUT | Set a config override (persisted in KV) |
-| `/config/:key` | DELETE | Reset a config key to its default |
+| Path           | Method | Description                             |
+| -------------- | ------ | --------------------------------------- |
+| `/`            | GET    | Landing page                            |
+| `/metrics`     | GET    | Prometheus metrics                      |
+| `/health`      | GET    | Health check                            |
+| `/config`      | GET    | Get all runtime config                  |
+| `/config/:key` | PUT    | Set a config override (persisted in KV) |
+| `/config/:key` | DELETE | Reset a config key to its default       |
 
 ## Available metrics
 
@@ -160,6 +160,7 @@ For a complete list of metrics with types and labels, refer to the [exporter REA
 Zones on Cloudflare's Free plan do not have access to the GraphQL Analytics API. The exporter automatically detects and skips free tier zones for metrics that require this API.
 
 Free tier zones still export:
+
 - `cloudflare_zone_certificate_validation_status` (SSL certificates)
 - `cloudflare_zone_lb_origin_weight` (Load balancer weights, if configured)
 
diff --git a/src/content/docs/analytics/custom-dashboards.mdx b/src/content/docs/analytics/custom-dashboards.mdx
index 49b08e4bdd64804..11fc76cc324f367 100644
--- a/src/content/docs/analytics/custom-dashboards.mdx
+++ b/src/content/docs/analytics/custom-dashboards.mdx
@@ -28,10 +28,10 @@ Investigate incidents so that when something goes wrong, you can create focused
 
 Custom Dashboards are available to all Cloudflare customers.
 
-| Customer type | Dashboard limit |
-|---------------|-----------------|
-| All Cloudflare customers | Up to 25 dashboards |
-| Log Explorer customers | Up to 100 dashboards |
+| Customer type            | Dashboard limit      |
+| ------------------------ | -------------------- |
+| All Cloudflare customers | Up to 25 dashboards  |
+| Log Explorer customers   | Up to 100 dashboards |
 
 ## Get started
 
@@ -39,13 +39,13 @@ Custom Dashboards are available to all Cloudflare customers.
 
 Templates are the fastest way to get value from Custom Dashboards. Each template is designed around a specific use case and includes pre-configured charts that surface the most relevant metrics.
 
-| Template | Use case |
-|----------|----------|
-| **Bot monitoring** | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors |
-| **API Security** | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns |
-| **Account takeover** | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
-| **API Performance** | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain |
-| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time |
+| Template                   | Use case                                                                                                                                 |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| **Bot monitoring**         | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors              |
+| **API Security**           | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns                           |
+| **Account takeover**       | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
+| **API Performance**        | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain   |
+| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time  |
 
 After selecting a template, you can customize it by adding, removing, or modifying charts to fit your specific needs.
 
@@ -81,15 +81,15 @@ For precise control, configure each element of your chart:
 
 Choose the visualization that best fits your data:
 
-| Chart type | Best for |
-|------------|----------|
+| Chart type     | Best for                                                                                 |
+| -------------- | ---------------------------------------------------------------------------------------- |
 | **Timeseries** | Trends and patterns over time — traffic spikes, latency changes, error rate fluctuations |
-| **Bar** | Comparing values across categories — requests by country, errors by status code |
-| **Donut** | Understanding proportions — cache hit ratio, traffic distribution by content type |
-| **Map** | Geographic patterns — where your traffic originates, regional performance differences |
-| **Stat** | Single important numbers — total requests today, current error rate, p99 latency |
-| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion |
-| **Top N** | Rankings — busiest endpoints, most blocked IPs, top user agents |
+| **Bar**        | Comparing values across categories — requests by country, errors by status code          |
+| **Donut**      | Understanding proportions — cache hit ratio, traffic distribution by content type        |
+| **Map**        | Geographic patterns — where your traffic originates, regional performance differences    |
+| **Stat**       | Single important numbers — total requests today, current error rate, p99 latency         |
+| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion                          |
+| **Top N**      | Rankings — busiest endpoints, most blocked IPs, top user agents                          |
 
 #### Example: Build a security overview chart
 
diff --git a/src/content/docs/analytics/faq/about-analytics.mdx b/src/content/docs/analytics/faq/about-analytics.mdx
index 027f8a07eb32e94..53d5f449641933e 100644
--- a/src/content/docs/analytics/faq/about-analytics.mdx
+++ b/src/content/docs/analytics/faq/about-analytics.mdx
@@ -23,10 +23,10 @@ Refer to [Types of analytics](/analytics/types-of-analytics/) for more informati
 
 The underlying datasets that Cloudflare Analytics captures and processes share the following characteristics:
 
-* All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
-* Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
-* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
-* In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
+- All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
+- Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
+- Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
+- In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
 
 ## Apparent data discrepancies
 
@@ -42,10 +42,10 @@ Finally, it is likely that unique visitor data from the Cloudflare Analytics app
 
 You may not be seeing metrics on Cloudflare Analytics for the following reasons:
 
-* You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
-* If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
-* If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
-* Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
+- You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
+- If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
+- If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
+- Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
 
 :::note
 Activations through a hosting partner works via a [CNAME setup](/dns/zone-setups/partial-setup/) on the `www` record. If most of your traffic actually goes to `domain.com`, [forward your traffic](/rules/url-forwarding/bulk-redirects/) from `domain.com` to `www.domain.com`.
diff --git a/src/content/docs/analytics/faq/index.mdx b/src/content/docs/analytics/faq/index.mdx
index c7d87c530a29c24..555fcdc07a3795f 100644
--- a/src/content/docs/analytics/faq/index.mdx
+++ b/src/content/docs/analytics/faq/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Visit the following pages for commonly asked questions:
 
diff --git a/src/content/docs/analytics/faq/other-faqs.mdx b/src/content/docs/analytics/faq/other-faqs.mdx
index 4e9145ab25ee9ae..86adb232c817e4d 100644
--- a/src/content/docs/analytics/faq/other-faqs.mdx
+++ b/src/content/docs/analytics/faq/other-faqs.mdx
@@ -15,10 +15,8 @@ There is a number of different types of traffic which may originate from **CLOUD
 
 Some sources of traffic from ASN13335 include:
 
-* [Workers subrequests](/workers/runtime-apis/fetch/)
-* [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
-* [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
-* [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
-* Other Cloudflare features like [Health Checks](/health-checks/)
-
-
+- [Workers subrequests](/workers/runtime-apis/fetch/)
+- [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
+- [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
+- [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
+- Other Cloudflare features like [Health Checks](/health-checks/)
diff --git a/src/content/docs/analytics/faq/wae-faqs.mdx b/src/content/docs/analytics/faq/wae-faqs.mdx
index 3693060a2bb2ab8..b88ec97467a6ce7 100644
--- a/src/content/docs/analytics/faq/wae-faqs.mdx
+++ b/src/content/docs/analytics/faq/wae-faqs.mdx
@@ -23,29 +23,24 @@ On the other hand, if you pick a good index that aligns with how you read the da
 
 ### What if I need to index on multiple values?
 
-
 It is possible to concatenate multiple values in your index field. So if you want to index on user ID and hostname, you can write, for example `"$userID:$hostname"` into your index field.
 
 Note that, based on your query pattern, it may make sense to write the same dataset with different indices. It is a common misconception that one should avoid "double-writing" data.
 
 Thanks to sampling, the cost of writing data multiple times can be relatively low. However, reading data inefficiently can result in significant expenses or low-quality results due to sampling.
 
-
 ### How do I know if my data is sampled?
 
 You can use the `_sample_interval` field — again, note that this does not tell you if the results are accurate.
 
 You can tell when data is sampled at read time because sample intervals will be multiples of powers of 10, for example `20` or `700`. There is no hard and fast rule for when sampling starts at read time, but in practice reading longer periods (or more index values) will result in a higher sample interval.
 
-
 ### Why is data missing?
 
-
 Sampling is based largely on the choice of index, as well as other factors like the time range queried and number of indices read. If you are reading from a larger index over a longer time period, and have filtered to a relatively small subgroup within that index, it may not be present due to sampling.
 
 If you need to read accurate results for that subgroup, we suggest that you add that field to your index (refer to [What if I need to index on multiple values](/analytics/faq/wae-faqs/#what-if-i-need-to-index-on-multiple-values)).
 
-
 ### Can I trust sampled data? Are my results accurate?
 
 Sampled data is highly reliable, particularly when a carefully selected index is used.
@@ -56,7 +51,7 @@ In the near future, we plan to expose the [margin of error](https://en.wikipedia
 
 ### How are bursts handled?
 
-Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time.  The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
+Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time. The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
 
 ### How much traffic will trigger sampling?
 
@@ -65,5 +60,3 @@ There is no fixed rule determining when sampling will be triggered.
 We have observed that for workloads like our global CDN, which distribute load around our network, each index value needs about 100 data points per second before sampling is noticeable at all.
 
 Depending on your workload and how you use Workers Analytics Engine, sampling may start at a higher or lower threshold than this. For example, if you are writing out many data points from a single worker execution, it is more likely that your data will be sampled.
-
-
diff --git a/src/content/docs/analytics/graphql-api/errors.mdx b/src/content/docs/analytics/graphql-api/errors.mdx
index b40d61df3dca927..aeead71c606fc32 100644
--- a/src/content/docs/analytics/graphql-api/errors.mdx
+++ b/src/content/docs/analytics/graphql-api/errors.mdx
@@ -13,24 +13,24 @@ The GraphQL Analytics API is a RESTful API based on HTTPS requests and JSON resp
 
 All responses contain an `errors` array, which will be `null` if there are no errors, and include at least one error object if there was an error. Non-null error objects will contain the following fields:
 
-* `message`: a string describing the error.
-* `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
-* `timestamp`: UTC datetime when the error occurred.
+- `message`: a string describing the error.
+- `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
+- `timestamp`: UTC datetime when the error occurred.
 
 ## Example
 
 ```json
 {
-  "data": null,
-  "errors": [
-    {
-      "message": "cannot request data older than 2678400s",
-      "path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
-      "extensions": {
-        "timestamp": "2019-12-09T21:27:19.195060142Z"
-      }
-    }
-  ]
+	"data": null,
+	"errors": [
+		{
+			"message": "cannot request data older than 2678400s",
+			"path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
+			"extensions": {
+				"timestamp": "2019-12-09T21:27:19.195060142Z"
+			}
+		}
+	]
 }
 ```
 
@@ -40,8 +40,8 @@ All responses contain an `errors` array, which will be `null` if there are no er
 
 Sample error messages:
 
-* `unable to execute query, please try again later` (HTTP `503`)
-* `too many queries in progress, please try again later` (HTTP `503`)
+- `unable to execute query, please try again later` (HTTP `503`)
+- `too many queries in progress, please try again later` (HTTP `503`)
 
 These messages indicate a temporary server-side issue. The first message typically means the upstream database is unreachable or returned an error. The second message means the server has reached its maximum number of concurrent queries.
 
@@ -51,10 +51,10 @@ Retry the request after a short delay. If the error persists, check the [Cloudfl
 
 Sample error messages:
 
-* `cannot request data older than...` (HTTP `400`)
-* `number of fields can't be more than...` (HTTP `400`)
-* `limit must be positive number and not greater than...` (HTTP `400`)
-* `query time range is too large...` (HTTP `400`)
+- `cannot request data older than...` (HTTP `400`)
+- `number of fields can't be more than...` (HTTP `400`)
+- `limit must be positive number and not greater than...` (HTTP `400`)
+- `query time range is too large...` (HTTP `400`)
 
 These messages indicate that the query exceeds what is allowed for the particular dataset under the current [plan](https://www.cloudflare.com/plans/), and an upgrade should be considered. Refer to [Node limits](/analytics/graphql-api/limits/#node-limits-and-availability) for details.
 
@@ -62,11 +62,11 @@ These messages indicate that the query exceeds what is allowed for the particula
 
 Sample error messages:
 
-* `error parsing args...` (HTTP `400`)
-* `scalar fields must have no selections` (HTTP `400`)
-* `object field must have selections` (HTTP `400`)
-* `unknown field...` (HTTP `400`)
-* `query contains error, please review it and retry` (HTTP `400`)
+- `error parsing args...` (HTTP `400`)
+- `scalar fields must have no selections` (HTTP `400`)
+- `object field must have selections` (HTTP `400`)
+- `unknown field...` (HTTP `400`)
+- `query contains error, please review it and retry` (HTTP `400`)
 
 These messages indicate that the query cannot be processed because it is malformed. Check the query syntax against the [GraphQL schema](/analytics/graphql-api/getting-started/explore-graphql-schema/) and correct the invalid fields or structure.
 
@@ -74,9 +74,9 @@ These messages indicate that the query cannot be processed because it is malform
 
 Sample error messages:
 
-* `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
-* `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
-* `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
+- `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
+- `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
+- `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
 
 These messages indicate the query exceeded rate or resource limits. Reduce the query complexity, the number of zones or accounts per request, or wait before retrying. Refer to the [Limits](/analytics/graphql-api/limits/) section for more details about rate limits.
 
@@ -84,10 +84,10 @@ These messages indicate the query exceeded rate or resource limits. Reduce the q
 
 Sample error messages:
 
-* `Unauthorized` (HTTP `401`)
-* `not authorized for that account` (HTTP `403`)
-* `zones [...] are not authorized` (HTTP `403`)
-* `does not have access to the path...` (HTTP `403`)
+- `Unauthorized` (HTTP `401`)
+- `not authorized for that account` (HTTP `403`)
+- `zones [...] are not authorized` (HTTP `403`)
+- `does not have access to the path...` (HTTP `403`)
 
 An `Unauthorized` response means the API token or bearer token is missing, expired, or invalid. Verify that you are passing a valid token in the `Authorization` header.
 
@@ -97,6 +97,6 @@ A `403` response means the token does not have the required permissions for the
 
 Sample error message:
 
-* `Internal server error` (HTTP `500`)
+- `Internal server error` (HTTP `500`)
 
 This is a generic error indicating an unexpected failure. If it persists, contact [Cloudflare Support](https://support.cloudflare.com/) with the full request and response, including the `Ray-ID` header from the HTTP response.
diff --git a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
index 2def716afc95aff..4900a64e4e2b8ff 100644
--- a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
+++ b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
@@ -9,14 +9,14 @@ products:
   - graphql-api
 ---
 
-Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time. 
+Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time.
 
 ## Availability
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`). 
-- **Default**: If no confidence level is specified, intervals are not returned. 
+- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`).
+- **Default**: If no confidence level is specified, intervals are not returned.
 
 ## Usage example
 
@@ -28,35 +28,35 @@ To request a confidence interval, use the `confidence(level: X)` argument in you
 
 ```graphql graphql-api-explorer title="A GraphQL query"
 query SingleDatasetWithConfidence($zoneTag: string, $start: Time, $end: Time) {
-  viewer {
-    zones(filter: {zoneTag: $zoneTag}) {
-      firewallEventsAdaptiveGroups(
-        filter: {datetime_gt: $start, datetime_lt: $end}
-        limit: 1000
-      ) {
-        count
-        avg {
-          sampleInterval
-        }
-        confidence(level: 0.95) {
-          count {
-            estimate
-            lower
-            upper
-            sampleSize
-          }
-        }
-      }
-    }
-  }
+	viewer {
+		zones(filter: { zoneTag: $zoneTag }) {
+			firewallEventsAdaptiveGroups(
+				filter: { datetime_gt: $start, datetime_lt: $end }
+				limit: 1000
+			) {
+				count
+				avg {
+					sampleInterval
+				}
+				confidence(level: 0.95) {
+					count {
+						estimate
+						lower
+						upper
+						sampleSize
+					}
+				}
+			}
+		}
+	}
 }
 ```
 
 ### Response
 
-The response includes the following values: 
+The response includes the following values:
 
-- `estimate`: The estimated value, based on sampled data. 
+- `estimate`: The estimated value, based on sampled data.
 - `lower`: The lower bound of the confidence interval.
 - `sampleSize`: The number of sampled data points used to calculate the estimate.
 - `upper`: The upper bound of the confidence interval.
@@ -65,30 +65,30 @@ In this example, the interpretation of the response is that, based on a sample o
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "firewallEventsAdaptiveGroups": [
-            {
-              "avg": {
-                "sampleInterval": 1.0720277625205972
-              },
-              "confidence": {
-                "count": {
-                  "estimate": 42939,
-                  "lower": 42673.44115335711,
-                  "sampleSize": 40054,
-                  "upper": 43204.55884664289
-                }
-              },
-              "count": 42939
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"firewallEventsAdaptiveGroups": [
+						{
+							"avg": {
+								"sampleInterval": 1.0720277625205972
+							},
+							"confidence": {
+								"count": {
+									"estimate": 42939,
+									"lower": 42673.44115335711,
+									"sampleSize": 40054,
+									"upper": 43204.55884664289
+								}
+							},
+							"count": 42939
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
diff --git a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
index 74c6b40c78266f7..d7db4d153f586f2 100644
--- a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
@@ -13,5 +13,4 @@ GraphQL API supports [introspection][1] to explore nodes and provides a way to
 retrieve the user's [limits][2] for every node.
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
-
 [2]: /analytics/graphql-api/features/discovery/settings/
diff --git a/src/content/docs/analytics/graphql-api/features/index.mdx b/src/content/docs/analytics/graphql-api/features/index.mdx
index 7b85fab58b64d62..39fea17f29b3b37 100644
--- a/src/content/docs/analytics/graphql-api/features/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The GraphQL Analytics API offers the following features:
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
index 0e458b325ede871..c6a25630a2aedd7 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
@@ -17,13 +17,13 @@ products:
    ![Editing HTTP Headers Window](~/assets/images/analytics/GraphiQL-edit-http-headers-window.png)
 
 3. Select **Add Header** to configure authentication. You can use Cloudflare Analytics API token authentication (recommended) or Cloudflare API key authentication.
-   * **Token authentication**:
+   - **Token authentication**:
 
      Enter **Authorization** in the **Header Name** field, and enter `Bearer {your-analytics-token}` in the **Header value** field, then select **Save**.
 
      ![Editing HTTP Headers](~/assets/images/analytics/GraphiQL-edit-http-headers-token.png)
 
-   * **Key authentication**:
+   - **Key authentication**:
 
      Enter `X-AUTH-EMAIL` in the **Header name** field and your email address registered with Cloudflare in the **Header value** field, and select **Save**.<br/>
 
@@ -36,10 +36,8 @@ products:
 
 :::note[Note]
 
-
 The right-side response pane is empty when you enter your information correctly. An error displays when there are problems with your header credentials.
 
-
 :::
 
 Now that you have configured authentication, you are ready to run queries using GraphiQL.
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
index ed75b1965e7c919..1e96ffce7142c4b 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
@@ -15,30 +15,40 @@ To secure access to your GraphQL Analytics data, use a Cloudflare API key or tok
 
 This table outlines the differences between Cloudflare API keys and tokens:
 
-
-
 <table>
-  <thead>
-      <tr>
-          <th>Authentication Method</th>
-          <th>Description</th>
-      </tr>
-  </thead>
-  <tbody>
-      <tr>
-        <td><a href='/fundamentals/api/get-started/create-token/'>API Tokens</a></td>
-        <td>Cloudflare recommends API Tokens as the preferred way to interact with Cloudflare APIs. You can configure the scope of tokens to limit access to account and zone resources, and you can define the Cloudflare APIs to which the token authorizes access.</td>
-      </tr>
-      <tr>
-        <td><a href='/fundamentals/api/get-started/keys/'>API Keys</a></td>
-        <td><p>Unique to each Cloudflare user and used only for authentication. API keys do not authorize access to accounts or zones.</p>
-        <p>Use the Global API Key for authentication.</p></td>
-      </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Authentication Method</th>
+			<th>Description</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>
+				<a href="/fundamentals/api/get-started/create-token/">API Tokens</a>
+			</td>
+			<td>
+				Cloudflare recommends API Tokens as the preferred way to interact with
+				Cloudflare APIs. You can configure the scope of tokens to limit access
+				to account and zone resources, and you can define the Cloudflare APIs to
+				which the token authorizes access.
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/fundamentals/api/get-started/keys/">API Keys</a>
+			</td>
+			<td>
+				<p>
+					Unique to each Cloudflare user and used only for authentication. API
+					keys do not authorize access to accounts or zones.
+				</p>
+				<p>Use the Global API Key for authentication.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
-
-
 To create and configure GraphQL Analytics API tokens, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
 
 To find and retrieve API keys, as well as edit HTTP headers for authentication in GraphiQL, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
diff --git a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
index 1839c3f0876e56b..4494649d7315149 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
@@ -28,13 +28,11 @@ Click on the editing pane of GraphiQL and add this base query, replacing
 
 :::note[Note]
 
-
 To find the zone's tag, log in to your Cloudflare account and select the site for
 which you want to obtain the tag. In the Cloudflare dashboard **Overview** page,
 scroll to the **API** section in the right sidebar, which displays your zone and
 account tags.
 
-
 :::
 
 To assist query building, the GraphiQL client has word completion. Insert your
@@ -128,29 +126,16 @@ This example query uses the `zoneTag` query variable to represent the zone ID:
 ![Example of GraphiQL query variables][14]
 
 [1]: /analytics/graphql-api/getting-started/querying-basics/
-
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
-
 [3]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
-
 [4]: ~/assets/images/analytics/graphiql-base-query.png
-
 [5]: ~/assets/images/analytics/graphiql-word-completion.png
-
 [6]: ~/assets/images/analytics/graphiql-set-up-base-query.png
-
 [7]: ~/assets/images/analytics/graphiql-parameters.png
-
 [8]: ~/assets/images/analytics/graphiql-filter-fields.png
-
 [9]: ~/assets/images/analytics/graphiql-filter-values.png
-
 [10]: ~/assets/images/analytics/graphiql-set-up-base-query.png
-
 [11]: ~/assets/images/analytics/graphiql-return-fields.png
-
 [12]: ~/assets/images/analytics/graphiql-query-return-field-values.png
-
 [13]: ~/assets/images/analytics/create-query-fw-data-set-play.png
-
 [14]: ~/assets/images/analytics/graphiql-query-variables.png
diff --git a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
index ab3680fa9a78abb..b1eeb322c398cb7 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
@@ -24,8 +24,8 @@ query:
 
 ```json title="A payload structure for GraphQL API"
 {
-  "query": "{viewer { ... }}",
-  "variables": {}
+	"query": "{viewer { ... }}",
+	"variables": {}
 }
 ```
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
index 0d2d0e248a08cf0..e77cba62457a8e1 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
@@ -79,7 +79,7 @@ query.
 
 For example, `zones` can take a filter of `ZoneFilter_InputObject` type as an
 argument. To view the fields available to filter, select
-**ZoneFilter\_InputObject**.
+**ZoneFilter_InputObject**.
 
 ## Find the datasets available for a zone
 
@@ -122,33 +122,18 @@ The list of fields displays:
 For more information on using GraphiQL, please visit this [guide][16].
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
-
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
-
 [3]: https://altairgraphql.dev/#download
-
 [4]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
-
 [5]: ~/assets/images/analytics/graphiql-docs-link.png
-
 [6]: ~/assets/images/analytics/graphiql-doc-explorer.png
-
 [7]: ~/assets/images/analytics/graphiql-doc-explorer-query-mutations.png
-
 [8]: ~/assets/images/analytics/graphiql-doc-explorer-view-cost.png
-
 [9]: ~/assets/images/analytics/graphiql-doc-explorer-viewer-fields.png
-
 [10]: ~/assets/images/analytics/graphiql-doc-explorer-zones.png
-
 [11]: ~/assets/images/analytics/graphiql-doc-explorer-zone-fields.png
-
 [12]: ~/assets/images/analytics/graphiql-doc-explorer-find-firewall.png
-
 [13]: ~/assets/images/analytics/graphiql-doc-explorer-firewallevents-definition.png
-
 [14]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-type-definition.png
-
 [15]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-fields.png
-
 [16]: /analytics/graphql-api/getting-started/compose-graphql-query/
diff --git a/src/content/docs/analytics/graphql-api/getting-started/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
index 2ba6111561b125e..6b82273dfd942ef 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
@@ -9,19 +9,19 @@ products:
   - graphql-api
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Use these articles to get started with the Cloudflare GraphQL API:
 
-* [Authentication][1] - walks you through the options and the steps required to
+- [Authentication][1] - walks you through the options and the steps required to
   set up your access to Cloudflare API successfully,
-* [Querying basics][2] - brings simple query examples for you to start exploring
+- [Querying basics][2] - brings simple query examples for you to start exploring
   the GraphQL API,
-* [Introspect the GraphQL schema][3] - explains how-to surf the schema with
+- [Introspect the GraphQL schema][3] - explains how-to surf the schema with
   GraphQL client,
-* [Create a query in a GraphQL client][4] - describes how to build and run a
+- [Create a query in a GraphQL client][4] - describes how to build and run a
   query against the Cloudflare GraphQL API in the GraphQL clients,
-* [Use curl to query the GraphQL API][5] - walks you through running a query
+- [Use curl to query the GraphQL API][5] - walks you through running a query
   against the Cloudflare GraphQL API from the command line.
 
 For examples of how to build your own GraphQL Analytics dashboard and query
@@ -29,17 +29,13 @@ specific information, such as Firewall and Workers events, please refer to
 [Tutorials][6].
 
 :::note[Data unavailability: Customer Metadata Boundary configuration]
- <Render file="customer_metadata_boundary_error" product="analytics" /> 
+
+<Render file="customer_metadata_boundary_error" product="analytics" />
 :::
 
 [1]: /analytics/graphql-api/getting-started/authentication/
-
 [2]: /analytics/graphql-api/getting-started/querying-basics/
-
 [3]: /analytics/graphql-api/getting-started/explore-graphql-schema/
-
 [4]: /analytics/graphql-api/getting-started/compose-graphql-query/
-
 [5]: /analytics/graphql-api/getting-started/execute-graphql-query/
-
 [6]: /analytics/graphql-api/tutorials/
diff --git a/src/content/docs/analytics/graphql-api/limits.mdx b/src/content/docs/analytics/graphql-api/limits.mdx
index 5adcc44092add47..41bac079ca31cd6 100644
--- a/src/content/docs/analytics/graphql-api/limits.mdx
+++ b/src/content/docs/analytics/graphql-api/limits.mdx
@@ -19,16 +19,16 @@ plans.
 To support this variety of products, Cloudflare GraphQL API has three layers of
 limits:
 
-* global limits
-* user limits
-* node (dataset) limits
+- global limits
+- user limits
+- node (dataset) limits
 
 ## Global limits
 
 These limits are applied to every query for every plan:
 
-* A zone-scoped query can include up to **10 zones**
-* An account-scoped query can include only **1 account**
+- A zone-scoped query can include up to **10 zones**
+- An account-scoped query can include only **1 account**
 
 Additionally, there is a limited number of queries you can make per request. The total number of queries in a request is equal to the number of zone/account scopes, multiplied by the number of nodes to which they are applied.
 
@@ -46,10 +46,10 @@ the Cloudflare API](/fundamentals/api/reference/limits/).
 
 Each data node has its limits, such as:
 
-* how far back in time can data be requested,
-* the maximum time period (in seconds) that can be requested in one query,
-* the maximum number of fields that can be requested in one query,
-* the maximum number of records that can be returned in one query.
+- how far back in time can data be requested,
+- the maximum time period (in seconds) that can be requested in one query,
+- the maximum number of fields that can be requested in one query,
+- the maximum number of records that can be returned in one query.
 
 Node limits are tied to requested `zoneTag` or `accountTag`. Higher plans have
 access to a greater selection of datasets or fields, and can query over broader historical
diff --git a/src/content/docs/analytics/graphql-api/mcp-server.mdx b/src/content/docs/analytics/graphql-api/mcp-server.mdx
index be3bc98608dc365..79aea053b1121fa 100644
--- a/src/content/docs/analytics/graphql-api/mcp-server.mdx
+++ b/src/content/docs/analytics/graphql-api/mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the GraphQL Analytics MCP server.
 products:
   - analytics
   - graphql-api
----
\ No newline at end of file
+---
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
index 4255d116dd9db69..a0cd2058706d926 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
@@ -17,8 +17,8 @@ If you are currently using the deprecated `httpRequests1mByColoGroups` or `httpR
 
 If you are currently using the Zone Analytics API, the following guide will help you migrate your queries to the new GraphQL Analytics API:
 
-* [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
-* [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
+- [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
+- [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
 
 ## Network Analytics migrations
 
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
index f6c3398fe285308..cfec218853327ed 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: reference
 title: NAv1 to NAv2 schema map
 sidebar:
diff --git a/src/content/docs/analytics/graphql-api/sampling.mdx b/src/content/docs/analytics/graphql-api/sampling.mdx
index ce5299faa9407b8..2dcf4bdf7261ff2 100644
--- a/src/content/docs/analytics/graphql-api/sampling.mdx
+++ b/src/content/docs/analytics/graphql-api/sampling.mdx
@@ -38,15 +38,11 @@ Cloudflare almost always uses **adaptive sampling**, which means the sample rate
 
 The following data nodes are based on fixed sampling, where the sample rate does not vary:
 
-
-
 | Data set                                                                                                                                       |   Rate | Notes                                                                                                                                                                                                |
 | :--------------------------------------------------------------------------------------------------------------------------------------------- | -----: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Firewall Rules Preview<br /><p><b>Nodes:</b><br />`firewallRulePreviewGroups`</p>                                                              |     1% | Use with caution. A 1% sample rate does not provide accurate estimates for datasets smaller than a certain threshold, a scenario the Cloudflare dashboard calls out explicitly but the API does not. |
 | Network Analytics<br /><p><b>Nodes:</b><br />`ipFlows1mGroups`<br />`ipFlows1hGroups`<br />`ipFlows1dGroups`<br />`ipFlows1mAttacksGroups`</p> | 0.012% | Sampling rate is in terms of packet count (1 of every 8,192 packets).                                                                                                                                |
 
-
-
 ## Access to raw data
 
 Because sampling is primarily adaptive and automatically adjusts to provide an accurate estimate, the sampling rate cannot be directly controlled. Enterprise customers have access to raw data via Cloudflare Logs.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
index c74285316775d50..b7bf522c3840234 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
@@ -54,107 +54,107 @@ The returned results will be in JSON format (as requested), so piping the output
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "httpRequestsAdaptiveGroups": [
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-21T10:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19849385,
-                "visits": 4383
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-21T06:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20607204,
-                "visits": 4375
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-26T05:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20170839,
-                "visits": 4519
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-23T08:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20141860,
-                "visits": 4448
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-25T15:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 21070367,
-                "visits": 4469
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-28T08:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19200774,
-                "visits": 4345
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-26T02:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20758067,
-                "visits": 4502
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-20T19:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 22127811,
-                "visits": 4443
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-27T15:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 20480644,
-                "visits": 4268
-              }
-            },
-            {
-              "dimensions": {
-                "datetimeHour": "2022-07-27T17:00:00Z"
-              },
-              "sum": {
-                "edgeResponseBytes": 19885704,
-                "visits": 4287
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"httpRequestsAdaptiveGroups": [
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-21T10:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19849385,
+								"visits": 4383
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-21T06:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20607204,
+								"visits": 4375
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-26T05:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20170839,
+								"visits": 4519
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-23T08:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20141860,
+								"visits": 4448
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-25T15:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 21070367,
+								"visits": 4469
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-28T08:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19200774,
+								"visits": 4345
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-26T02:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20758067,
+								"visits": 4502
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-20T19:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 22127811,
+								"visits": 4443
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-27T15:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 20480644,
+								"visits": 4268
+							}
+						},
+						{
+							"dimensions": {
+								"datetimeHour": "2022-07-27T17:00:00Z"
+							},
+							"sum": {
+								"edgeResponseBytes": 19885704,
+								"visits": 4287
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
@@ -162,13 +162,13 @@ The returned results will be in JSON format (as requested), so piping the output
 
 We are going to use the GraphQL Analytics API to query the top 10 consuming URLs from a zone, helping you identify the URLs with the highest resource usage. Here are some configuration instructions:
 
-* To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
-* Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
-* Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
-* To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
-  * `CURRENTDATE=$(gdate -u +'%FT%TZ')`
-  * `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
-* For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
+- To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
+- Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
+- Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
+- To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
+  - `CURRENTDATE=$(gdate -u +'%FT%TZ')`
+  - `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
+- For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
 
 ### API call
 
@@ -196,4 +196,4 @@ https://api.cloudflare.com/client/v4/graphql \
 }' | jq -r 'try .data.viewer.zones[].topPaths[] | "\"\(.dimensions.metric)\": \(.sum.edgeResponseBytes)"' | sort
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/index.mdx b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
index baf7496c1ef4723..ebcfb6d0cf8b7b2 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/index.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The following resources will help you start exploring your data and creating analytics dashboards:
 
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
index 4fbbc812304c501..7f0e232f641a485 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
@@ -15,9 +15,9 @@ The following API call will request logs for a single Access login event and out
 
 You will need to insert your `<CLOUDFLARE_ACCOUNT_TAG>`, your API credentials in `<API_TOKEN>`[^1], and substitute your own values for the following variables:
 
-* `rayID`: A unique identifier assigned to the authentication request.
-* `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
-* `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
+- `rayID`: A unique identifier assigned to the authentication request.
+- `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
+- `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
 
 ## API Call
 
@@ -65,47 +65,47 @@ https://api.cloudflare.com/client/v4/graphql \
 
 :::note
 
-Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`. 
+Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`.
 :::
 
 ## Response
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "accounts": [
-        {
-          "accessLoginRequestsAdaptiveGroups": [
-            {
-              "dimensions": {
-                "approvingPolicyId": "",
-                "cfRayId": "744927037ce06d68",
-                "country": "US",
-                "datetime": "2022-09-02T20:56:27Z",
-                "deviceId": "",
-                "hasExistingJWT": 0,
-                "hasGatewayEnabled": 0,
-                "hasWarpEnabled": 0,
-                "identityProvider": "nonidentity",
-                "ipAddress": "2a09:bac0:15::814:7b37",
-                "isSuccessfulLogin": 0,
-                "mtlsCertSerialId": "",
-                "mtlsCommonName": "",
-                "mtlsStatus": "NONE",
-                "serviceTokenId": "",
-                "userUuid": ""
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"accounts": [
+				{
+					"accessLoginRequestsAdaptiveGroups": [
+						{
+							"dimensions": {
+								"approvingPolicyId": "",
+								"cfRayId": "744927037ce06d68",
+								"country": "US",
+								"datetime": "2022-09-02T20:56:27Z",
+								"deviceId": "",
+								"hasExistingJWT": 0,
+								"hasGatewayEnabled": 0,
+								"hasWarpEnabled": 0,
+								"identityProvider": "nonidentity",
+								"ipAddress": "2a09:bac0:15::814:7b37",
+								"isSuccessfulLogin": 0,
+								"mtlsCertSerialId": "",
+								"mtlsCommonName": "",
+								"mtlsStatus": "NONE",
+								"serviceTokenId": "",
+								"userUuid": ""
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
 You can compare the query results to your Access policies to understand why a user was blocked. For example, if your application requires a valid mTLS certificate, Access blocked the request shown above because `mtlsStatus`, `mtlsCommonName`, and `mtlsCertSerialId` are empty.
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
index ccd12acea299f70..3e8f9dde667b2df 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
@@ -65,74 +65,74 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "emailRoutingAdaptive": [
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:51:25Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "John <john@email.example.com>",
-              "id": "AfWyaZ7V1TAH",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "How are you doing?",
-              "to": "me@example.com"
-            },
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:30:00Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "eBay <ebay@ebay.co.uk>",
-              "id": "aYPegrIfLWia",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "New offers",
-              "to": "me@example.com"
-            },
-            {
-              "action": "forward",
-              "arc": "none",
-              "datetime": "2026-01-19T10:29:59Z",
-              "dkim": "pass",
-              "dmarc": "pass",
-              "errorDetail": "",
-              "from": "Notification <notifications@example.com>",
-              "id": "nWIl9gs95mY3",
-              "isNDR": 0,
-              "isSpam": 0,
-              "messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
-              "spamScore": 0,
-              "spamThreshold": 5,
-              "spf": "pass",
-              "status": "delivered",
-              "subject": "You're over quota",
-              "to": "me@example.com"
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"emailRoutingAdaptive": [
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:51:25Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "John <john@email.example.com>",
+							"id": "AfWyaZ7V1TAH",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "How are you doing?",
+							"to": "me@example.com"
+						},
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:30:00Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "eBay <ebay@ebay.co.uk>",
+							"id": "aYPegrIfLWia",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "New offers",
+							"to": "me@example.com"
+						},
+						{
+							"action": "forward",
+							"arc": "none",
+							"datetime": "2026-01-19T10:29:59Z",
+							"dkim": "pass",
+							"dmarc": "pass",
+							"errorDetail": "",
+							"from": "Notification <notifications@example.com>",
+							"id": "nWIl9gs95mY3",
+							"isNDR": 0,
+							"isSpam": 0,
+							"messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
+							"spamScore": 0,
+							"spamThreshold": 5,
+							"spf": "pass",
+							"status": "delivered",
+							"subject": "You're over quota",
+							"to": "me@example.com"
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
@@ -176,114 +176,114 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "zones": [
-        {
-          "emailRoutingAdaptiveGroups": [
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T11:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T12:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T13:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T14:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T15:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T16:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T17:00:00Z"
-              }
-            },
-            {
-              "count": 3,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T18:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-18T22:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T01:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T02:00:00Z"
-              }
-            },
-            {
-              "count": 4,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T05:00:00Z"
-              }
-            },
-            {
-              "count": 1,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T08:00:00Z"
-              }
-            },
-            {
-              "count": 5,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T09:00:00Z"
-              }
-            },
-            {
-              "count": 6,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T10:00:00Z"
-              }
-            },
-            {
-              "count": 2,
-              "dimensions": {
-                "datetimeHour": "2026-01-19T11:00:00Z"
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"zones": [
+				{
+					"emailRoutingAdaptiveGroups": [
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T11:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T12:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T13:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T14:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T15:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T16:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T17:00:00Z"
+							}
+						},
+						{
+							"count": 3,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T18:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-18T22:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T01:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T02:00:00Z"
+							}
+						},
+						{
+							"count": 4,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T05:00:00Z"
+							}
+						},
+						{
+							"count": 1,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T08:00:00Z"
+							}
+						},
+						{
+							"count": 5,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T09:00:00Z"
+							}
+						},
+						{
+							"count": 6,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T10:00:00Z"
+							}
+						},
+						{
+							"count": 2,
+							"dimensions": {
+								"datetimeHour": "2026-01-19T11:00:00Z"
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
index deab15ea91ace34..3d4c56d42ef286d 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
@@ -9,8 +9,9 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-endpoint-health-checks"
+<Render
+	file="graphql/query-magic-transit-endpoint-health-checks"
 	product="networking-services"
 />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
index 727a62e37b0ac21..0c1fc135106eaa8 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
@@ -9,8 +9,10 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
-	params={{ productName: "Magic Transit or Cloudflare WAN" }} />
+	params={{ productName: "Magic Transit or Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
index 3ed3c1e2b7fce50..7e2d5a042de9744 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
@@ -9,9 +9,10 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
 	params={{ productName: "Magic Transit or Cloudflare WAN" }}
 />
diff --git a/src/content/docs/analytics/index.mdx b/src/content/docs/analytics/index.mdx
index 8c9eca78825e740..7f6b64667dccaec 100644
--- a/src/content/docs/analytics/index.mdx
+++ b/src/content/docs/analytics/index.mdx
@@ -11,38 +11,52 @@ products:
   - analytics
 ---
 
-import { Feature, RelatedProduct } from "~/components"
+import { Feature, RelatedProduct } from "~/components";
 
 Cloudflare visualizes the metadata collected by our products in the Cloudflare dashboard. Refer to [Types of analytics](/analytics/types-of-analytics/) for more information about the various types of analytics and where they exist in the dashboard.
 
-***
+---
 
 ## Features
 
 <Feature header="Workers Analytics Engine" href="/analytics/analytics-engine/">
-Send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL. 
+	Send unlimited-cardinality data from your Worker to a time-series database.
+	Query it with SQL.
 </Feature>
 
-<Feature header="Account and zone analytics" href="/analytics/account-and-zone-analytics/">
-Provides details about the requests and traffic related to your Cloudflare accounts and zones. 
+<Feature
+	header="Account and zone analytics"
+	href="/analytics/account-and-zone-analytics/"
+>
+	Provides details about the requests and traffic related to your Cloudflare
+	accounts and zones.
 </Feature>
 
-<Feature header="Cloudflare Network Analytics" href="/analytics/network-analytics/">
-Provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. 
+<Feature
+	header="Cloudflare Network Analytics"
+	href="/analytics/network-analytics/"
+>
+	Provides near real-time visibility into network and transport-layer traffic
+	patterns and DDoS attacks.
 </Feature>
 
 <Feature header="GraphQL Analytics API" href="/analytics/graphql-api/">
-Provides all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account. 
+	Provides all of your performance, security, and reliability data from one
+	endpoint. Select exactly what you need, from one metric for a domain to
+	multiple metrics aggregated for your account.
 </Feature>
 
-***
+---
 
 ## Related products
 
 <RelatedProduct header="Workers" href="/workers/" product="workers">
-Cloudflare Workers allows developers to build serverless applications and deploy instantly across the globe for exceptional performance, reliability, and scale. 
+	Cloudflare Workers allows developers to build serverless applications and
+	deploy instantly across the globe for exceptional performance, reliability,
+	and scale.
 </RelatedProduct>
 
 <RelatedProduct header="Logs" href="/logs/" product="logs">
-Detailed logs that contain metadata generated by Cloudflare products helpful for debugging, identifying configuration adjustments, and creating analytics. 
+	Detailed logs that contain metadata generated by Cloudflare products helpful
+	for debugging, identifying configuration adjustments, and creating analytics.
 </RelatedProduct>
diff --git a/src/content/docs/analytics/network-analytics/configure/index.mdx b/src/content/docs/analytics/network-analytics/configure/index.mdx
index 960840cbc5deb03..16e7bfa95e54afc 100644
--- a/src/content/docs/analytics/network-analytics/configure/index.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/network-analytics/configure/share-export.mdx b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
index ebfbca66506210a..4f80063b389f3a8 100644
--- a/src/content/docs/analytics/network-analytics/configure/share-export.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
@@ -11,7 +11,7 @@ products:
   - analytics
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 ## Share Network Analytics filters
 
diff --git a/src/content/docs/analytics/network-analytics/configure/time-range.mdx b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
index f22f93aa5d6e373..4cad33741de7676 100644
--- a/src/content/docs/analytics/network-analytics/configure/time-range.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
@@ -17,7 +17,7 @@ Use the timeframe drop-down list to change the time range over which Network Ana
 
 In the Network Analytics dashboard, the range of historical data you can query is 112 days.
 
-When you select *Previous 30 minutes*, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A *Live* notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
+When you select _Previous 30 minutes_, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A _Live_ notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
 
 ![Timeframe drop-down with Previous 30 minutes selected.](~/assets/images/analytics/network-analytics/timeframe-selector.png)
 
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
index e8908c5bbfc3b1e..72d38cdbd6e45a7 100644
--- a/src/content/docs/analytics/network-analytics/index.mdx
+++ b/src/content/docs/analytics/network-analytics/index.mdx
@@ -12,7 +12,7 @@ products:
   - analytics
 ---
 
-import { InlineBadge, Render } from "~/components"
+import { InlineBadge, Render } from "~/components";
 
 Cloudflare Network Analytics (version 2) provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. Network Analytics visualizes packet and bit-level data, the same data available via the Network Analytics dataset of the GraphQL Analytics API.
 
@@ -22,12 +22,12 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
 
 ## Remarks
 
-* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
+- The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
 
-* The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
+- The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
 
 ## Related resources
 
-* [Cloudflare GraphQL API](/analytics/graphql-api/)
-* [Cloudflare Logpush](/logs/logpush/)
-* [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
\ No newline at end of file
+- [Cloudflare GraphQL API](/analytics/graphql-api/)
+- [Cloudflare Logpush](/logs/logpush/)
+- [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
diff --git a/src/content/docs/analytics/network-analytics/reference/index.mdx b/src/content/docs/analytics/network-analytics/reference/index.mdx
index bfaf9377cbe9497..50a9131063634e7 100644
--- a/src/content/docs/analytics/network-analytics/reference/index.mdx
+++ b/src/content/docs/analytics/network-analytics/reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review reference information about Cloudflare Network Analytics:
 
diff --git a/src/content/docs/analytics/network-analytics/understand/index.mdx b/src/content/docs/analytics/network-analytics/understand/index.mdx
index 364ff4458dc64da..6bbfaed1b7957b3 100644
--- a/src/content/docs/analytics/network-analytics/understand/index.mdx
+++ b/src/content/docs/analytics/network-analytics/understand/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/sampling.mdx b/src/content/docs/analytics/sampling.mdx
index 815514bf77937e5..964b7405a3d5f1a 100644
--- a/src/content/docs/analytics/sampling.mdx
+++ b/src/content/docs/analytics/sampling.mdx
@@ -8,7 +8,7 @@ products:
   - analytics
 ---
 
-[Sampling](https://en.wikipedia.org/wiki/Sampling_(statistics)) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
+[Sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
 
 ## How sampling works
 
@@ -20,17 +20,17 @@ To make this possible, data is stored at multiple resolutions (100%, 10%, 1%), e
 
 Cloudflare's data pipeline handles [over 700 million events per second](https://blog.cloudflare.com/how-we-make-sense-of-too-much-data) (and growing) across its global network. Processing and storing all this data in real-time would be prohibitively expensive and time-consuming. By leveraging carefully designed sampling methods, Cloudflare Analytics delivers accurate and actionable data, balancing precision with performance.
 
-Sampling enables: 
+Sampling enables:
 
 - **Scalability**: Reduces the volume of data processed without compromising insights.
 - **Performance**: Speeds up query execution for analytics.
 - **Cost-Efficiency**: Minimizes resource usage and storage needs.
 
-## Can I trust sampled data? 
+## Can I trust sampled data?
 
 Sampled data is highly reliable, and can provide insights that are as dependable as those derived from full datasets. Cloudflare designs sampling techniques to ensure we capture the essential characteristics of the entire dataset, delivering results you can trust.
 
-Sampling is an approach similarly used in other domains, for instance: 
+Sampling is an approach similarly used in other domains, for instance:
 
 - Google Maps: Just as online maps display lower-resolution images when zoomed out and higher-resolution images when zoomed in — keeping the total number of pixels relatively constant — Cloudflare Analytics dynamically adjusts sampling rates to efficiently provide insights, ensuring queries return consistent and accurate results regardless of dataset size.
 
@@ -44,23 +44,26 @@ In the near future, we plan to expose confidence intervals along with query resu
 
 ## Additional considerations
 
-**When sampling occurs** 
+**When sampling occurs**
+
 - Sampling is typically applied to very high-traffic datasets where full data analysis would be impractical.
 - For smaller datasets, full data analysis is often performed without sampling.
 
-**Sampling rates** 
+**Sampling rates**
+
 - Sampling rates vary depending on the dataset and product.
 - Cloudflare ensures that sampling rates are consistent within a single dataset to maintain accuracy across queries.
 
-**Impact on metrics** 
+**Impact on metrics**
+
 - While sampling reduces the volume of processed data, aggregated metrics like totals, averages, and percentiles are extrapolated based on the sample size. This ensures the reported metrics represent the entire dataset accurately.
 
 **Limitations**
-- Sampling may not capture extremely rare events with very low occurrence rates. 
+
+- Sampling may not capture extremely rare events with very low occurrence rates.
 
 **Sampling in analytics interfaces**
+
 - GraphQL API: Sampling metadata is included in the query response. For more information, refer to the sampling [GraphQL Analytics API](/analytics/graphql-api/sampling/) documentation.
 - Workers Analytics Engine: For more information, refer to the [Workers Analytics Engine](/analytics/analytics-engine/sampling/) documentation.
 - Dashboard Analytics: Displays an icon with the sampled percentage of data, if sampled data was used for the visualization.
-
-
diff --git a/src/content/docs/analytics/types-of-analytics.mdx b/src/content/docs/analytics/types-of-analytics.mdx
index 3754f8a0ce803d1..9b13d4d6e16b1d5 100644
--- a/src/content/docs/analytics/types-of-analytics.mdx
+++ b/src/content/docs/analytics/types-of-analytics.mdx
@@ -40,25 +40,24 @@ Access aggregated traffic, security, and performance metrics for each domain pro
 
 Data available under the **Analytics & Logs** section includes:
 
-* **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
-* **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
-* **Performance** - Origin Performance, Bandwidth Saved.
-* **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
-* **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
-* **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
-* **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
+- **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
+- **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
+- **Performance** - Origin Performance, Bandwidth Saved.
+- **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
+- **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
+- **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
+- **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
 
 ## Product analytics
 
 Beyond the analytics provided for your properties, you can also access analytics related to specific products:
 
-* [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
-* [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
-* [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
-* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
-* [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
-* [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
-
+- [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
+- [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
+- [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
+- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
+- [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
+- [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
 
 ## GraphQL APIs
 
diff --git a/src/content/docs/api-shield/api-gateway.mdx b/src/content/docs/api-shield/api-gateway.mdx
index 7eb6722be62e2c5..159a13ee168f6ba 100644
--- a/src/content/docs/api-shield/api-gateway.mdx
+++ b/src/content/docs/api-shield/api-gateway.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 7
-
 ---
 
 Cloudflare API Shield provides API security, management tools, and integration with the Cloudflare Developer Platform for building new APIs.
diff --git a/src/content/docs/api-shield/glossary.mdx b/src/content/docs/api-shield/glossary.mdx
index f3d2e75924932cd..8cec6bbf2bf209c 100644
--- a/src/content/docs/api-shield/glossary.mdx
+++ b/src/content/docs/api-shield/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 sidebar:
   order: 9
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's API Shield documentation.
 
diff --git a/src/content/docs/api-shield/index.mdx b/src/content/docs/api-shield/index.mdx
index 17d437901096fc5..f95940e11bfbf9e 100644
--- a/src/content/docs/api-shield/index.mdx
+++ b/src/content/docs/api-shield/index.mdx
@@ -11,11 +11,15 @@ head:
     content: Overview
 ---
 
-import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
+import {
+	Description,
+	Feature,
+	Plan,
+	RelatedProduct,
+	Render,
+} from "~/components";
 
-<Description>
-Identify and address your API vulnerabilities.
-</Description>
+<Description>Identify and address your API vulnerabilities.</Description>
 
 <Plan type="ent-add-on" />
 
@@ -37,11 +41,14 @@ Refer to the [Get started](/api-shield/get-started/) guide to set up API Shield.
 ## Features
 
 <Feature header="Security features" href="/api-shield/security/">
-Secure your APIs using API Shield's security features.
+	Secure your APIs using API Shield's security features.
 </Feature>
 
-<Feature header="Management, monitoring, and more" href="/api-shield/management-and-monitoring/">
-Monitor the health of your API endpoints.
+<Feature
+	header="Management, monitoring, and more"
+	href="/api-shield/management-and-monitoring/"
+>
+	Monitor the health of your API endpoints.
 </Feature>
 
 ## Availability
@@ -56,6 +63,11 @@ API Shield currently does not work for JDCloud customers.
 
 ## Related products
 
-<RelatedProduct header="DDoS Protection" href="/ddos-protection/" product="ddos-protection">
-Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised.
+<RelatedProduct
+	header="DDoS Protection"
+	href="/ddos-protection/"
+	product="ddos-protection"
+>
+	Cloudflare DDoS protection secures websites, applications, and entire networks
+	while ensuring the performance of legitimate traffic is not compromised.
 </RelatedProduct>
diff --git a/src/content/docs/api-shield/management-and-monitoring/index.mdx b/src/content/docs/api-shield/management-and-monitoring/index.mdx
index 182cc0cab64e27c..166b939d9e38c8e 100644
--- a/src/content/docs/api-shield/management-and-monitoring/index.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/index.mdx
@@ -6,11 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 5
-  group: 
+  group:
     hideIndex: true
-
 ---
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
index 7139806c6c0866c..34134ffed50f975 100644
--- a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
@@ -6,14 +6,14 @@ products:
 title: Session identifiers
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="session-identifiers" product="api-shield" />
 
 :::note
+
 <Render file="required-session-identifiers" product="api-shield" />
 :::
 
diff --git a/src/content/docs/api-shield/plans.mdx b/src/content/docs/api-shield/plans.mdx
index 7cba5403983b3bc..e54a67a1da3c703 100644
--- a/src/content/docs/api-shield/plans.mdx
+++ b/src/content/docs/api-shield/plans.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 3
-
 ---
 
 Free, Pro, Business, and Enterprise customers without an API Shield subscription can access [Endpoint Management](/api-shield/management-and-monitoring/) and [Schema validation](/api-shield/security/schema-validation/), but no other [API Shield](/api-shield/) features.
@@ -15,10 +14,10 @@ To subscribe to API Shield, upgrade to an Enterprise plan and contact your accou
 
 Limits to endpoints apply to Endpoint Management and Schema validation. Refer to the table below for limits based on your zone plan.
 
-| Plan type | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action |
-| --- | --- | --- | --- | --- |
-| **Free** | 100 | 5 | 200 kB | `Block` only |
-| **Pro** | 250 | 5 | 500 kB | `Block` only |
-| **Business** | 500 | 10 | 2 MB | `Block` only |
-| **Enterprise without API Shield** | 500 | 10 | 5 MB | `Log` or `Block` |
-| **Enterprise with API Shield** | 10,000 | 10+ | 10+ MB | `Log` or `Block` |
\ No newline at end of file
+| Plan type                         | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action      |
+| --------------------------------- | --------------- | ---------------- | -------------------------- | ---------------- |
+| **Free**                          | 100             | 5                | 200 kB                     | `Block` only     |
+| **Pro**                           | 250             | 5                | 500 kB                     | `Block` only     |
+| **Business**                      | 500             | 10               | 2 MB                       | `Block` only     |
+| **Enterprise without API Shield** | 500             | 10               | 5 MB                       | `Log` or `Block` |
+| **Enterprise with API Shield**    | 10,000          | 10+              | 10+ MB                     | `Log` or `Block` |
diff --git a/src/content/docs/api-shield/reference/classic-schema-validation.mdx b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
index 7e5925a84e6068a..4fefbda61645691 100644
--- a/src/content/docs/api-shield/reference/classic-schema-validation.mdx
+++ b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
@@ -12,10 +12,9 @@ sidebar:
     text: Deprecated
   order: 1
   label: Classic Schema validation
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 :::caution[Deprecation notice]
 Classic Schema validation has been deprecated.
@@ -41,14 +40,11 @@ To configure Schema validation in the Cloudflare dashboard:
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Select **Security** > **API Shield**.
 3. Go to **Schema validation** and select **Add schema**.
-4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the *Hostname* field — equal to `api.example.com` — and a check for the *URI Path* field using a regular expression — matching the regex `^/v1`.
-:::caution[Important]
+4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the _Hostname_ field — equal to `api.example.com` — and a check for the _URI Path_ field using a regular expression — matching the regex `^/v1`.
+   :::caution[Important]
 
-To validate the hostname, you must include the *Hostname* field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
-:::
-5. Select **Next**.
-6. Upload your schema file.
-7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
+To validate the hostname, you must include the _Hostname_ field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
+::: 5. Select **Next**. 6. Upload your schema file. 7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
 
 After deploying your API Shield rule, Cloudflare displays a summary of all <GlossaryTooltip term="API endpoint">API endpoints</GlossaryTooltip> organized by their protection level and actions that will occur for non-compliant and unprotected requests.
 
diff --git a/src/content/docs/api-shield/reference/index.mdx b/src/content/docs/api-shield/reference/index.mdx
index d51edc253455ed3..e0fb94f82c8316e 100644
--- a/src/content/docs/api-shield/reference/index.mdx
+++ b/src/content/docs/api-shield/reference/index.mdx
@@ -6,12 +6,11 @@ products:
   - api-shield
 sidebar:
   order: 6
-  group: 
+  group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about API Shield:
 
diff --git a/src/content/docs/api-shield/reference/terraform.mdx b/src/content/docs/api-shield/reference/terraform.mdx
index 823b0b64274405a..8e5c5b8d6c3be74 100644
--- a/src/content/docs/api-shield/reference/terraform.mdx
+++ b/src/content/docs/api-shield/reference/terraform.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 tags:
   - Terraform
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Get started with API Shield using Terraform from the examples below. For more information on how to use Terraform with Cloudflare, refer to the [Terraform documentation](/terraform/).
 
@@ -62,7 +61,7 @@ resource "cloudflare_api_shield_operation" "get_image" {
   host     = "example.com"
   endpoint = "/api/images/{var1}"
 }
- 
+
 resource "cloudflare_api_shield_operation" "post_image" {
   zone_id  = var.zone_id
   method   = "POST"
@@ -75,7 +74,7 @@ resource "cloudflare_api_shield_operation" "post_image" {
 
 :::note
 
-It is required to configure Endpoint Management if you want to set up Schema validation using Terraform. 
+It is required to configure Endpoint Management if you want to set up Schema validation using Terraform.
 :::
 
 Refer to the example configuration below to manage [Schema validation](/api-shield/security/schema-validation/api/) on your zone.
@@ -90,13 +89,13 @@ resource "cloudflare_schema_validation_schemas" "example_schema" {
   source             = file("./schemas/example-schema.yaml")
   validation_enabled = true
 }
- 
+
 # Block all requests that violate schema by default
 resource "cloudflare_schema_validation_settings" "zone_level_settings" {
   zone_id                              = var.zone_id
   validation_default_mitigation_action = "block"
 }
- 
+
 # For endpoint post_image - only log requests that violate schema
 resource "cloudflare_schema_validation_operation_settings" "post_image_log_only" {
   zone_id           = var.zone_id
diff --git a/src/content/docs/api-shield/security/graphql-protection/index.mdx b/src/content/docs/api-shield/security/graphql-protection/index.mdx
index c8c4dfc16b03dd8..6d8f7feb449ca0d 100644
--- a/src/content/docs/api-shield/security/graphql-protection/index.mdx
+++ b/src/content/docs/api-shield/security/graphql-protection/index.mdx
@@ -6,7 +6,6 @@ products:
   - api-shield
 sidebar:
   order: 5
-
 ---
 
 GraphQL is a query language for APIs. In addition to protecting RESTful APIs, Cloudflare can also protect GraphQL APIs.
diff --git a/src/content/docs/api-shield/security/index.mdx b/src/content/docs/api-shield/security/index.mdx
index 36a3a3e4120f463..63dde51928c06d0 100644
--- a/src/content/docs/api-shield/security/index.mdx
+++ b/src/content/docs/api-shield/security/index.mdx
@@ -6,22 +6,19 @@ products:
   - api-shield
 sidebar:
   order: 4
-
 ---
 
-import { DirectoryListing } from "~/components"
-
+import { DirectoryListing } from "~/components";
 
 Cloudflare offers the following features to help secure your APIs:
 
-| Discovery & management | Posture management | Runtime protection |
-| --- | --- | --- |
-| [API Discovery](/api-shield/security/api-discovery/) | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/) | [Schema validation](/api-shield/security/schema-validation/) |
-| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/) | [JWT validation](/api-shield/security/jwt-validation/) |
-| [Sequence Analytics](/api-shield/security/sequence-analytics/) | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/) |
-| | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels) | [Mutual TLS (mTLS)](/api-shield/security/mtls/) |
-| | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) | [GraphQL query protection](/api-shield/security/graphql-protection/) |
-
+| Discovery & management                                                                        | Posture management                                                                 | Runtime protection                                                   |
+| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
+| [API Discovery](/api-shield/security/api-discovery/)                                          | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/)     | [Schema validation](/api-shield/security/schema-validation/)         |
+| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/)             | [JWT validation](/api-shield/security/jwt-validation/)               |
+| [Sequence Analytics](/api-shield/security/sequence-analytics/)                                | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/)     |
+|                                                                                               | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels)  | [Mutual TLS (mTLS)](/api-shield/security/mtls/)                      |
+|                                                                                               | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/)               | [GraphQL query protection](/api-shield/security/graphql-protection/) |
 
 ## Example Cloudflare solutions
 
@@ -29,29 +26,23 @@ Cloudflare API Shield, together with other Cloudflare products, helps protect yo
 
 The following table maps each OWASP vulnerability to the Cloudflare features that address it:
 
-| OWASP issue                                     | Example Cloudflare solution                                                                                                                            |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| OWASP issue                                     | Example Cloudflare solution                                                                                                                                                                                                             |
+| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Broken Object Level Authorization               | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/), [Sequence mitigation], [Schema validation], [JWT validation], [Rate Limiting], [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) |
 | Broken Authentication                           | [Authentication Posture](/api-shield/security/authentication-posture/), [mTLS](/api-shield/security/mtls/), [JWT validation], [Exposed Credential Checks](/waf/managed-rules/check-for-exposed-credentials/), [Bot Management](/bots/)  |
-| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                  |
-| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                   |
-| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                  |
-| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                    |
-| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                       |
-| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                            |
-| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                   |
-| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                  |
+| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
+| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                    |
+| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
+| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                                     |
+| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                                                                                                        |
+| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                                                                                                             |
+| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                                                                                                    |
+| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                                                                                                   |
 
 [Schema validation]: /api-shield/security/schema-validation/
-
 [Sequence mitigation]: /api-shield/security/sequence-mitigation/
-
 [JWT validation]: /api-shield/security/jwt-validation/
-
 [GraphQL Query Protection]: /api-shield/security/graphql-protection/
-
 [Bot management]: /bots/
-
 [Rate limiting]: /waf/rate-limiting-rules/
-
 [WAF managed rules]: /waf/managed-rules/
diff --git a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
index 412e2ee5573001d..e37fc920b98921f 100644
--- a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
@@ -14,7 +14,7 @@ tags:
   - JavaScript
 ---
 
-import { Steps } from "~/components"
+import { Steps } from "~/components";
 
 Use a Worker to automatically keep your identity provider’s latest public key in the JWT validation configuration.
 
diff --git a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
index 102b9af7bb9bb5e..69906adc1b47b63 100644
--- a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
@@ -13,7 +13,7 @@ tags:
   - JSON web token (JWT)
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 You can forward information from a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) to the origin in a header by creating [Transform Rules](/rules/transform/) using claims that Cloudflare has verified via the JSON Web Token.
 
@@ -44,4 +44,4 @@ As an example, to send the `x-send-jwt-claim-user` request header to the origin,
     lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
     ```
     `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT validation and `claim_name` is the JWT claim you want to add to the header.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/api-shield/security/mtls/byo-ca.mdx b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
index 2430485da76550a..90b2c59cd2ff56e 100644
--- a/src/content/docs/api-shield/security/mtls/byo-ca.mdx
+++ b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/client-certificates/byo-ca/
 sidebar:
   order: 3
-
 ---
diff --git a/src/content/docs/api-shield/security/mtls/index.mdx b/src/content/docs/api-shield/security/mtls/index.mdx
index 6652a44adef3c34..c7984dc34ab21f2 100644
--- a/src/content/docs/api-shield/security/mtls/index.mdx
+++ b/src/content/docs/api-shield/security/mtls/index.mdx
@@ -8,7 +8,6 @@ sidebar:
   order: 7
 tags:
   - mTLS
-
 ---
 
 import { GlossaryDefinition, Render } from "~/components";
diff --git a/src/content/docs/api-shield/security/sequence-analytics.mdx b/src/content/docs/api-shield/security/sequence-analytics.mdx
index 34a24e55bdceb85..c70bf1c1ef13f37 100644
--- a/src/content/docs/api-shield/security/sequence-analytics.mdx
+++ b/src/content/docs/api-shield/security/sequence-analytics.mdx
@@ -6,10 +6,9 @@ products:
 title: Sequence Analytics
 sidebar:
   order: 3
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Sequence Analytics tracks the order of API endpoint requests over time, allowing you to discover how users interact with your API. Sequence Analytics groups and highlights important user journeys (sequences) across your API. You can enforce preferred sequences using [Sequence mitigation](/api-shield/security/sequence-mitigation/).
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
index c3bf0a409084cde..33320b54ef171ed 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
@@ -10,24 +10,23 @@ sidebar:
 head:
   - tag: title
     content: Configure sequence mitigation via the API
-
 ---
 
 Configuring sequence mitigation via the API consists of building a rule object by choosing the sequence and setting the type of rule and its action.
 
 ```json title="Example of a rule object"
 {
-    "id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
-    "title": "<RULE_TITLE>",
-    "kind": "allow",
-    "action": "block",
-    "sequence": [
-     "0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
-     "b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
-    ],
-    "priority": 0,
-    "last_updated": "2023-07-24T12:06:51.796286Z",
-    "created_at": "2023-07-24T12:06:51.796286Z"
+	"id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
+	"title": "<RULE_TITLE>",
+	"kind": "allow",
+	"action": "block",
+	"sequence": [
+		"0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
+		"b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
+	],
+	"priority": 0,
+	"last_updated": "2023-07-24T12:06:51.796286Z",
+	"created_at": "2023-07-24T12:06:51.796286Z"
 }
 ```
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
index 08a2a8da0c12da5..5d43aabef5e991b 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
@@ -7,14 +7,14 @@ products:
 sidebar:
   order: 4
   label: Custom rules
-
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
 
 These rules are similar to [cookie sequence rules](/bots/additional-configurations/sequence-rules/) but have a different set of prerequisites:
+
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.
 - Because they require session identifiers, they can only be used on traffic that can be clearly attributed to individual users through session identifiers (authenticated traffic).
 - Because Cloudflare stores the user state in memory and not in a cookie, a session's sequence lifetime is limited to 10 minutes.
@@ -25,6 +25,7 @@ Rules built using these custom rules are similar to the sequence rules that can
 ## Availability
 
 :::note
+
 <Render file="sequence-mitigation-availability" product="api-shield" />
 :::
 
@@ -41,30 +42,30 @@ Each saved endpoint will have an endpoint ID visible in its details page in Endp
 The visitor must wait more than 2 seconds after requesting endpoint `aaaaaaaa` before requesting endpoint `bbbbbbbb`:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and 
+cf.sequence.current_op eq "bbbbbbbb" and
 cf.sequence.msec_since_op["aaaaaaaa"] ge 2000
 ```
 
 The visitor must request endpoints `aaaaaaaa`, then `bbbbbbbb`, then `cccccccc` in that exact order:
 
 ```txt
-cf.sequence.current_op eq "cccccccc" and 
-cf.sequence.previous_ops[0] == "bbbbbbbb" and 
+cf.sequence.current_op eq "cccccccc" and
+cf.sequence.previous_ops[0] == "bbbbbbbb" and
 cf.sequence.previous_ops[1] == "aaaaaaaa"
 ```
 
 The visitor must request endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, but endpoint `aaaaaaaa` can be anywhere in the previous 10 requests:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and 
+cf.sequence.current_op eq "bbbbbbbb" and
 any(cf.sequence.previous_ops[*] == "aaaaaaaa")
 ```
 
 The visitor must request either endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, or endpoint `cccccccc` before endpoint `bbbbbbbb`:
 
 ```txt
-(cf.sequence.current_op eq "bbbbbbbb" and 
-any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or 
-(cf.sequence.current_op eq "bbbbbbbb" and 
+(cf.sequence.current_op eq "bbbbbbbb" and
+any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or
+(cf.sequence.current_op eq "bbbbbbbb" and
 any(cf.sequence.previous_ops[*] == "cccccccc"))
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
index 184e0fe3410c88c..7672a8fafa6039f 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
@@ -6,10 +6,9 @@ products:
   - api-shield
 sidebar:
   order: 4
-
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 Sequence mitigation allows you to enforce request patterns for authenticated clients communicating with your API.
 
@@ -30,7 +29,7 @@ Using sequence mitigation, you can enforce that request pattern with two new seq
 
 :::note
 
-You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/). 
+You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/).
 :::
 
 ## Process
@@ -54,7 +53,6 @@ A negative security model may be useful if you see abusive behavior that is outs
 
 For example, if there was an authorization bug that allowed users to iterate through other users' profiles that contain account numbers via `GET /api/v1/users/{var1}/profile` and then a user tries to make fraudulent funds transfers, you could create a rule to block or log the sequence `GET /api/v1/users/{var1}/profile` to `POST /api/v1/transferFunds`.
 
-
 ## Limitations
 
 ### Endpoint Management
@@ -87,4 +85,4 @@ For example, if you create a rule requiring one endpoint to be requested before
 
 ## Availability
 
-<Render file="sequence-mitigation-availability" product="api-shield" />
\ No newline at end of file
+<Render file="sequence-mitigation-availability" product="api-shield" />
diff --git a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
index ac20b0d38774fb5..4b6e8f08729bae2 100644
--- a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
+++ b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
@@ -6,10 +6,9 @@ products:
 title: Volumetric Abuse Detection
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components"
+import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components";
 
 Cloudflare Volumetric Abuse Detection generates per-endpoint, per-session rate limit recommendations that adjust automatically as your traffic patterns change.
 
@@ -27,7 +26,7 @@ Volumetric Abuse Detection rate limits are a way to prevent blatant volumetric a
 
 Volumetric Abuse Detection analyzes your API's individual session traffic statistics to recommend per-endpoint, per-session rate limits.
 
-To access your endpoints: 
+To access your endpoints:
 
 Old dashboard: **Security** > **API Shield** > **Endpoint Management**
 
@@ -47,7 +46,7 @@ Thresholds are suggested only for endpoints that satisfy all of the following re
 
 After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in the Cloudflare dashboard.
 
-### Rate limiting recommendation calculation 
+### Rate limiting recommendation calculation
 
 Select an endpoint row in **Endpoints** to view its rate limit recommendation. The detail view shows the overall recommended value and percentile-based values (p50, p90, p99).
 
@@ -73,8 +72,8 @@ Refer to the [Rules documentation](/waf/rate-limiting-rules/create-zone-dashboar
 [Rate limit recommendations are available via the API](/api/resources/api_gateway/subresources/operations/methods/get/) if you would like to dynamically update rate limits over time.
 
 <APIRequest
-  path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
-  method="GET"
+	path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
+	method="GET"
 />
 
 ## Special cases
diff --git a/src/content/docs/argo-smart-routing/analytics.mdx b/src/content/docs/argo-smart-routing/analytics.mdx
index 73046eae32ef933..8ba08d6be3c3f77 100644
--- a/src/content/docs/argo-smart-routing/analytics.mdx
+++ b/src/content/docs/argo-smart-routing/analytics.mdx
@@ -22,18 +22,15 @@ You can access Argo analytics for your domain in the [Cloudflare dashboard](http
 
 :::note
 
-
 Detailed performance data within **Origin Performance (Argo)** will only display if Argo has routed at least 500 origin requests within the last 48 hours.
 
-
 :::
 
 ## Types of analytics
 
 The dashboard displays two different views for performance data:
 
-* **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
-
-* **Geography**: A map shows the improvement in response time at each Cloudflare data center.
+- **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
 
-  * A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
+- **Geography**: A map shows the improvement in response time at each Cloudflare data center.
+  - A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
diff --git a/src/content/docs/argo-smart-routing/argo-for-packets.mdx b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
index 8d4a1b15407b0ce..b2e857fe5dca3da 100644
--- a/src/content/docs/argo-smart-routing/argo-for-packets.mdx
+++ b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
@@ -6,7 +6,6 @@ products:
   - argo-smart-routing
 sidebar:
   order: 4
-
 ---
 
 Argo for Packets optimizes IP layer network routing for Cloudflare network services products, including [Magic Transit](/magic-transit/), [Cloudflare WAN](/cloudflare-wan/) (formerly Magic WAN), and [Cloudflare for Offices](https://blog.cloudflare.com/cloudflare-for-offices/).
diff --git a/src/content/docs/artifacts/api/errors.mdx b/src/content/docs/artifacts/api/errors.mdx
index 7545813cd7cbfa2..467365dbf5b37c7 100644
--- a/src/content/docs/artifacts/api/errors.mdx
+++ b/src/content/docs/artifacts/api/errors.mdx
@@ -15,17 +15,17 @@ This is a list of Artifacts errors.
 
 ## Error codes
 
-| Name | Code | Description |
-|------|------|-------------|
-| `ALREADY_EXISTS` | 10201 | The target repository already exists in the namespace. |
-| `NOT_FOUND` | 10200 | The repository or remote resource does not exist. |
-| `IMPORT_IN_PROGRESS` | 10302 | The repository is still being imported and is not yet available. |
-| `FORK_IN_PROGRESS` | 10303 | The repository is still being forked and is not yet available. |
-| `INVALID_INPUT` | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
-| `INVALID_REPO_NAME` | 10101 | The repository name does not meet naming requirements. |
-| `INVALID_TTL` | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds). |
-| `INVALID_URL` | 10104 | The source URL does not point to a valid git repository. |
-| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication. |
-| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached. |
-| `MEMORY_LIMIT` | 10402 | The operation exceeds service memory limits. |
-| `INTERNAL_ERROR` | 10400 | An unexpected internal error occurred. |
+| Name                   | Code  | Description                                                               |
+| ---------------------- | ----- | ------------------------------------------------------------------------- |
+| `ALREADY_EXISTS`       | 10201 | The target repository already exists in the namespace.                    |
+| `NOT_FOUND`            | 10200 | The repository or remote resource does not exist.                         |
+| `IMPORT_IN_PROGRESS`   | 10302 | The repository is still being imported and is not yet available.          |
+| `FORK_IN_PROGRESS`     | 10303 | The repository is still being forked and is not yet available.            |
+| `INVALID_INPUT`        | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
+| `INVALID_REPO_NAME`    | 10101 | The repository name does not meet naming requirements.                    |
+| `INVALID_TTL`          | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds).       |
+| `INVALID_URL`          | 10104 | The source URL does not point to a valid git repository.                  |
+| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication.                            |
+| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached.                               |
+| `MEMORY_LIMIT`         | 10402 | The operation exceeds service memory limits.                              |
+| `INTERNAL_ERROR`       | 10400 | An unexpected internal error occurred.                                    |
diff --git a/src/content/docs/artifacts/api/git-protocol.mdx b/src/content/docs/artifacts/api/git-protocol.mdx
index 0b2fe497d2755c8..df3348a7a33e084 100644
--- a/src/content/docs/artifacts/api/git-protocol.mdx
+++ b/src/content/docs/artifacts/api/git-protocol.mdx
@@ -20,10 +20,10 @@ Use the returned repo `remote` with a regular Git client for `clone`, `fetch`, `
 
 Git routes accept repo access tokens in two forms:
 
-| Format                             | Details                                                                                                                               | Example                                                                                                      |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| Format                             | Details                                                                                                                              | Example                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
 | Bearer token in `http.extraHeader` | Recommended for local workflows. Use the full token string returned by the control plane and keep credentials out of the remote URL. | `git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone` |
-| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`               |
+| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`                  |
 
 ### Token format
 
diff --git a/src/content/docs/artifacts/concepts/repositories.mdx b/src/content/docs/artifacts/concepts/repositories.mdx
index 026597faaae63d4..c00cad8531dd358 100644
--- a/src/content/docs/artifacts/concepts/repositories.mdx
+++ b/src/content/docs/artifacts/concepts/repositories.mdx
@@ -30,11 +30,11 @@ Each repository is isolated from other repositories. Tokens, lifecycle, refs, an
 
 Artifacts exposes the same repository through three interfaces:
 
-| Interface | What you use it for | What it returns |
-| --- | --- | --- |
-| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker | Repository metadata, repository handles, and repo-scoped token results |
-| REST API | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results |
-| Git protocol | Clone, fetch, pull, and push repository contents | Standard Git behavior over HTTPS |
+| Interface       | What you use it for                                                                | What it returns                                                        |
+| --------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
+| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker         | Repository metadata, repository handles, and repo-scoped token results |
+| REST API        | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results    |
+| Git protocol    | Clone, fetch, pull, and push repository contents                                   | Standard Git behavior over HTTPS                                       |
 
 These interfaces point to the same repository.
 
diff --git a/src/content/docs/artifacts/examples/git-client.mdx b/src/content/docs/artifacts/examples/git-client.mdx
index a297d94fb81bf26..10a023272838435 100644
--- a/src/content/docs/artifacts/examples/git-client.mdx
+++ b/src/content/docs/artifacts/examples/git-client.mdx
@@ -11,10 +11,11 @@ products:
 You can use a standard Git client to interact with Artifacts repos. This example walks through clone, but the same approach works for fetch, pull, push, and any other Git operation.
 
 To do this, you need to:
+
 - Fetch the repo's remote URL from the REST API
 - Mint a short-lived token scoped to that repo
 
-Once you have the remote URL and token, you can use them to run Git commands against the repo. 
+Once you have the remote URL and token, you can use them to run Git commands against the repo.
 
 This example assumes the repo already exists and that you have a [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 
@@ -49,11 +50,13 @@ ARTIFACTS_TOKEN=$(printf '%s' "$TOKEN_JSON" | jq -r '.result.plaintext')
 # Clone the repo
 git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone
 ```
+
 You now have a standard Git checkout in `./artifacts-clone`.
 
 This flow is useful when another system owns repo discovery or access control, but your local tooling still expects a normal git remote.
 
 ### Authentication
+
 Treat `ARTIFACTS_TOKEN` as a secret. Keep it out of logs, and prefer `http.extraHeader` over saving credentials in a remote URL.
 
 If you need a self-contained remote URL for a short-lived workflow, extract the token secret and build the authenticated remote only for that command:
diff --git a/src/content/docs/artifacts/guides/authentication.mdx b/src/content/docs/artifacts/guides/authentication.mdx
index ac4559e2184b237..b700afb4e8e3481 100644
--- a/src/content/docs/artifacts/guides/authentication.mdx
+++ b/src/content/docs/artifacts/guides/authentication.mdx
@@ -16,11 +16,11 @@ Review [Namespaces](/artifacts/concepts/namespaces/) first, then use one namespa
 
 ## Compare auth methods
 
-| Interface | Authenticate with | Permissions or scopes | Use for |
-| --- | --- | --- | --- |
-| Workers binding | Configured `artifacts` binding | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`. | Worker code that calls `env.ARTIFACTS` |
-| REST API | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests |
-| Git protocol | Repo-scoped Artifacts token | `read` for clone, fetch, and pull. `write` for push. | Standard Git over HTTPS |
+| Interface       | Authenticate with                                   | Permissions or scopes                                                                   | Use for                                |
+| --------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------- |
+| Workers binding | Configured `artifacts` binding                      | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`.           | Worker code that calls `env.ARTIFACTS` |
+| REST API        | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests            |
+| Git protocol    | Repo-scoped Artifacts token                         | `read` for clone, fetch, and pull. `write` for push.                                    | Standard Git over HTTPS                |
 
 Cloudflare API tokens authenticate control-plane access. Repo-scoped Artifacts tokens authenticate Git access.
 
@@ -79,10 +79,10 @@ curl --request POST "$ARTIFACTS_BASE_URL/repos" \
 
 Git uses repo-scoped Artifacts tokens, not Cloudflare API tokens. Mint these tokens from the Workers binding or the REST API, then use them with the repo `remote` URL.
 
-| Token scope | Allowed commands |
-| --- | --- |
-| `read` | `git clone`, `git fetch`, `git pull` |
-| `write` | `git clone`, `git fetch`, `git pull`, `git push` |
+| Token scope | Allowed commands                                 |
+| ----------- | ------------------------------------------------ |
+| `read`      | `git clone`, `git fetch`, `git pull`             |
+| `write`     | `git clone`, `git fetch`, `git pull`, `git push` |
 
 Use the exact repo `remote` value returned by the Workers binding or REST API:
 
diff --git a/src/content/docs/artifacts/guides/event-subscriptions.mdx b/src/content/docs/artifacts/guides/event-subscriptions.mdx
index 8b1184706241f3d..08ff7f6771fca2b 100644
--- a/src/content/docs/artifacts/guides/event-subscriptions.mdx
+++ b/src/content/docs/artifacts/guides/event-subscriptions.mdx
@@ -13,6 +13,7 @@ import { Render } from "~/components";
 Artifacts emits structured events for repository lifecycle changes — creates, deletes, forks, imports, pushes, clones, fetches, and token changes. By subscribing to these events through [event subscriptions](/queues/event-subscriptions/), you can consume them from a Worker to build commit-driven automation.
 
 For example:
+
 - Run custom workflows when a repository is created or imported
 - Kick off a build and deploy a change when an agent pushes to a repo
 - Trigger a review agent on every push
diff --git a/src/content/docs/artifacts/platform/limits.mdx b/src/content/docs/artifacts/platform/limits.mdx
index 75154c57881d70c..b328482a34c0687 100644
--- a/src/content/docs/artifacts/platform/limits.mdx
+++ b/src/content/docs/artifacts/platform/limits.mdx
@@ -15,9 +15,9 @@ These limits cover naming rules, storage, and request rates for control-plane an
 | Feature                        | Limit                                                                                              |
 | ------------------------------ | -------------------------------------------------------------------------------------------------- |
 | Control-plane request rate     | 2,000 requests per 10 seconds per Artifacts namespace                                              |
-| Git request rate, per artifact     | 2,000 requests per 10 seconds per artifact                                                             |
+| Git request rate, per artifact | 2,000 requests per 10 seconds per artifact                                                         |
 | Maximum storage per repository | 10 GB                                                                                              |
 | Maximum storage per account    | 1 TB (can be raised on request)                                                                    |
-| Maximum number of repositories | Unlimited                                 |
+| Maximum number of repositories | Unlimited                                                                                          |
 | Maximum number of namespaces   | Unlimited                                                                                          |
 | Namespace and repo names       | Start with a letter or digit. Remaining characters may include letters, digits, `.`, `_`, and `-`. |
diff --git a/src/content/docs/artifacts/platform/pricing.mdx b/src/content/docs/artifacts/platform/pricing.mdx
index 8cca99c4745119f..6986d8c6160294c 100644
--- a/src/content/docs/artifacts/platform/pricing.mdx
+++ b/src/content/docs/artifacts/platform/pricing.mdx
@@ -15,10 +15,10 @@ Artifacts pricing is billed on two dimensions:
 
 ## Artifacts pricing
 
-| Unit                          | Workers Free | Workers Paid |
-| ----------------------------- | ------------ | ------------ |
-| Operations (1,000 operations) | Unavailable | First 10,000 per month + $0.15 per additional 1,000 operations |
-| Storage (GB-mo)               | Unavailable | First 1 GB per month + $0.50 per additional GB-mo |
+| Unit                          | Workers Free | Workers Paid                                                   |
+| ----------------------------- | ------------ | -------------------------------------------------------------- |
+| Operations (1,000 operations) | Unavailable  | First 10,000 per month + $0.15 per additional 1,000 operations |
+| Storage (GB-mo)               | Unavailable  | First 1 GB per month + $0.50 per additional GB-mo              |
 
 ## Storage usage
 
diff --git a/src/content/docs/automatic-platform-optimization/about/index.mdx b/src/content/docs/automatic-platform-optimization/about/index.mdx
index 8a627ee1adac90b..8e08942f6c504ec 100644
--- a/src/content/docs/automatic-platform-optimization/about/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/index.mdx
@@ -6,7 +6,6 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 2
-
 ---
 
 With Automatic Platform Optimization (APO), Cloudflare serves your entire site from our edge network, ensuring customers see improved performance when visiting your site. Cloudflare typically only caches static content, but with APO, we can also cache dynamic content — like HTML — to serve the entire site from the cache. This process removes round trips from the origin to drastically improve time to first byte (TTFB) along with other site performance metrics. In addition to caching dynamic content, APO caches third-party scripts to further reduce the number of requests that leave Cloudflare's edge network.
diff --git a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
index 3b36da43020bcd5..c63c3dc4fdccb0f 100644
--- a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
@@ -16,35 +16,33 @@ For questions about a specific plugin not shown in the list, create a thread in
 
 :::note
 
-
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
-
 :::
 
 ## Compatible plugins
 
-* [NitroPack](https://nitropack.io/)
-* [FlyingPress](https://flyingpress.com/)
-* [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
-* [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
-* [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
-* [WooCommerce](https://wordpress.org/plugins/woocommerce/)
-* [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
-* [Object Cache Pro](https://objectcache.pro)
-* [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
-* [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
-* [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
-* [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
-* [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
-* [WPTouch](https://wordpress.org/plugins/wptouch/)
-* [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
-* [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
-* [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
-* [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
-* [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
-* [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
-* [WPML](https://wpml.org/)
-* [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
-* [Imunify360](https://docs.imunify360.com/features/#webshield)
-* [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
+- [NitroPack](https://nitropack.io/)
+- [FlyingPress](https://flyingpress.com/)
+- [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
+- [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
+- [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
+- [WooCommerce](https://wordpress.org/plugins/woocommerce/)
+- [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
+- [Object Cache Pro](https://objectcache.pro)
+- [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
+- [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
+- [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
+- [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
+- [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
+- [WPTouch](https://wordpress.org/plugins/wptouch/)
+- [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
+- [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
+- [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
+- [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
+- [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
+- [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
+- [WPML](https://wpml.org/)
+- [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
+- [Imunify360](https://docs.imunify360.com/features/#webshield)
+- [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
diff --git a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
index 05c85a5ea866629..e4df722b4bb5ebb 100644
--- a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
@@ -6,7 +6,6 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 3
-
 ---
 
 Before you begin using APO, we recommend testing your current site speed. Your site speed results give your website a letter grade and performance rating.
diff --git a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
index e2ba71bfc3a0ea6..422ecb4f5989b1b 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
@@ -33,8 +33,6 @@ We recommend keeping this browser tab or window open and opening a new tab or wi
 
 :::note
 
-
 You may be prompted to confirm the nameserver change with your domain registrar. Confirm or continue after making the update.
 
-
 :::
diff --git a/src/content/docs/automatic-platform-optimization/get-started/index.mdx b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
index 27e95e4ce57100a..1ec49c17ce68232 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with APO
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Before you configure APO for your WordPress site, complete the following tasks.
 
diff --git a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
index a8148c2c7bbb2e6..710c8af46eb1aa8 100644
--- a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
@@ -12,9 +12,9 @@ sidebar:
 
 APO cache by device type provides all of the same benefits of Cloudflare's cache while targeting visitors with content appropriate to their device. Cloudflare evaluates the `User-Agent` header in the HTTP request to identify the device type. Cloudflare then identifies each device type with a case insensitive match to the regex below:
 
-* **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
-* **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
-* **Desktop**: Everything else not matched above.
+- **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
+- **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
+- **Desktop**: Everything else not matched above.
 
 To enable caching by device type, enable the setting from the Cloudflare dashboard's APO card or from the WordPress plugin version 4.4.0 or later.
 
@@ -22,10 +22,8 @@ Once enabled, Cloudflare sends a `CF-Device-Type` HTTP header to your origin wit
 
 :::note
 
-
 Changing Cache By Device Type setting will invalidate Cache.
 
-
 :::
 
 The Cloudflare for WordPress plugin automatically purges all cache variations for updated pages.
diff --git a/src/content/docs/automatic-platform-optimization/reference/index.mdx b/src/content/docs/automatic-platform-optimization/reference/index.mdx
index d3e472301ede3ee..14a92784439d41f 100644
--- a/src/content/docs/automatic-platform-optimization/reference/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/index.mdx
@@ -6,9 +6,8 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
index 80a3a268e1f1395..c1f33213a954200 100644
--- a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
@@ -6,21 +6,20 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 12
-
 ---
 
 The following Page Rules can control APO. Any changes to caching via Page Rules require purging the cache for the changes to take effect.
 
 :::caution
 
-Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability. 
+Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability.
 :::
 
-* **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
+- **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
 
-* **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
+- **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
 
-* **Cache Level: Cache Everything** — APO caches pages with all query strings.
+- **Cache Level: Cache Everything** — APO caches pages with all query strings.
 
   :::caution
 
@@ -28,10 +27,10 @@ Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO
 
   :::
 
-* **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
+- **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
 
-* **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
+- **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
 
-* **Browser Cache TTL** — APO applies custom Browser TTL.
+- **Browser Cache TTL** — APO applies custom Browser TTL.
 
-* `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
+- `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
diff --git a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
index d49a44137e07c34..4c26f989a9835bb 100644
--- a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
@@ -16,46 +16,46 @@ To add a query parameter to our allowlist, [create a post in the community](http
 
 APO serves cached content as long as the query parameters in the URL are one of the following:
 
-* `ref`
-* `utm_source`
-* `utm_medium`
-* `utm_campaign`
-* `utm_term`
-* `utm_content`
-* `utm_expid`
-* `fbclid`
-* `fb_action_ids`
-* `fb_action_types`
-* `fb_source`
-* `mc_cid`
-* `mc_eid`
-* `gclid`
-* `dclid`
-* `_ga`
-* `campaignid`
-* `adgroupid`
-* `_ke`
-* `cn-reloaded`
-* `age-verified`
-* `ao_noptimize`
-* `usqp`
-* `mkt_tok`
-* `epik`
-* `ck_subscriber_id`
+- `ref`
+- `utm_source`
+- `utm_medium`
+- `utm_campaign`
+- `utm_term`
+- `utm_content`
+- `utm_expid`
+- `fbclid`
+- `fb_action_ids`
+- `fb_action_types`
+- `fb_source`
+- `mc_cid`
+- `mc_eid`
+- `gclid`
+- `dclid`
+- `_ga`
+- `campaignid`
+- `adgroupid`
+- `_ke`
+- `cn-reloaded`
+- `age-verified`
+- `ao_noptimize`
+- `usqp`
+- `mkt_tok`
+- `epik`
+- `ck_subscriber_id`
 
 ## Cookies prefixes that always bypass cache
 
-* `wp-`
-* `wordpress`
-* `comment_`
-* `woocommerce_`
-* `xf_`
-* `edd_`
-* `jetpack`
-* `yith_wcwl_session_`
-* `yith_wrvp_`
-* `wpsc_`
-* `ecwid`
-* `ec_`
-* `bookly_`
-* `bookly`
+- `wp-`
+- `wordpress`
+- `comment_`
+- `woocommerce_`
+- `xf_`
+- `edd_`
+- `jetpack`
+- `yith_wcwl_session_`
+- `yith_wrvp_`
+- `wpsc_`
+- `ecwid`
+- `ec_`
+- `bookly_`
+- `bookly`
diff --git a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
index c3ac27a754ccf4a..c14b25e62e38c9f 100644
--- a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
@@ -46,10 +46,10 @@ export default {
 		const originalResponse = await fetch(request);
 
 		// Response properties are immutable. To change them, construct a new Response object.
-    const response = new Response(originalResponse.body, originalResponse);
+		const response = new Response(originalResponse.body, originalResponse);
 
-    // Response headers can be modified through the headers `set` method.
-    response.headers.set("cf-edge-cache", "no-cache");
+		// Response headers can be modified through the headers `set` method.
+		response.headers.set("cf-edge-cache", "no-cache");
 
 		return response;
 	},
diff --git a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
index 4f41ab6c0987264..f680125ba5c4689 100644
--- a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
@@ -6,28 +6,25 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 15
-
 ---
 
 ## WordPress plugin is undetected on Cloudflare dashboard
 
 The WordPress plugin may go undetected on your Cloudflare dashboard for a few reasons.
 
-* Versions older than 3.8.2 of the WordPress plugin are installed.
-  * **Solution:** Install version 4.4.0 of the WordPress plugin.
-* Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
-  * **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
-* WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
-  * **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
+- Versions older than 3.8.2 of the WordPress plugin are installed.
+  - **Solution:** Install version 4.4.0 of the WordPress plugin.
+- Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
+  - **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
+- WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
+  - **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
 
 If your Cloudflare dashboard cannot detect the WordPress plugin after trying the solutions above, ensure you completed all of the steps listed in [Activate the Cloudflare WordPress plugin](/automatic-platform-optimization/get-started/activate-cf-wp-plugin/).
 
 :::note
 
-
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
-
 :::
 
 ## WordPress returns stale content
diff --git a/src/content/docs/billing/get-started/create-billing-profile.mdx b/src/content/docs/billing/get-started/create-billing-profile.mdx
index db1ff0eccc710d9..278be4c84fffc13 100644
--- a/src/content/docs/billing/get-started/create-billing-profile.mdx
+++ b/src/content/docs/billing/get-started/create-billing-profile.mdx
@@ -20,7 +20,7 @@ Customers on an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/co
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**. If no payment method is on file, the dialog opens automatically.
@@ -57,7 +57,7 @@ Optionally, add an additional payment method. Cloudflare automatically retries t
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**.
diff --git a/src/content/docs/billing/get-started/update-billing-info.mdx b/src/content/docs/billing/get-started/update-billing-info.mdx
index 103bc694b8df894..14d3c82fae104fa 100644
--- a/src/content/docs/billing/get-started/update-billing-info.mdx
+++ b/src/content/docs/billing/get-started/update-billing-info.mdx
@@ -20,7 +20,7 @@ If Cloudflare is unable to process your payment, review [Troubleshooting failed
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method** to add a new method, or **Edit** next to an existing one.
@@ -55,7 +55,7 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Delete** next to the payment method you want to remove.
@@ -65,9 +65,9 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 Two address fields exist on your account:
 
-| Field | Where it is used |
-| --- | --- |
-| **Billing profile address** | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening. |
+| Field                              | Where it is used                                                                                                       |
+| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| **Billing profile address**        | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening.                             |
 | **Payment method billing address** | Captured when you add a payment method. Used by the card issuer to authorize each charge. Does not appear on invoices. |
 
 Updating the billing profile address applies to invoices issued after the change. Past invoices keep the address that was on file when they were issued. Updating the billing profile address does not change the address stored on existing payment methods.
@@ -76,7 +76,7 @@ To update the billing profile address:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit** and enter your information.
 3. Review the suggested address in the pop-up window. If the information is correct, select **Confirm**.
@@ -91,7 +91,7 @@ Your billing email address is particularly important if you have [opted into ema
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to **Invoices and documents**.
 3. From **Billing email preference**, select **Change email address**.
@@ -101,13 +101,13 @@ Your billing email address is particularly important if you have [opted into ema
 
 If you added a payment method but did not include a Tax ID, VAT or GST number, you can add or change the Tax ID, VAT or GST number associated with the payment method afterwards.
 
-:::note 
+:::note
 You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, enter your VAT or GST number.
@@ -115,13 +115,13 @@ You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST numbe
 
 ## Remove a Tax ID, VAT, or GST number
 
-:::note 
+:::note
 You cannot remove a VAT or GST number from past invoices. Removing a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, delete the VAT or GST number.
diff --git a/src/content/docs/billing/manage/billable-usage.mdx b/src/content/docs/billing/manage/billable-usage.mdx
index 936144271be0638..3136309de54ce9b 100644
--- a/src/content/docs/billing/manage/billable-usage.mdx
+++ b/src/content/docs/billing/manage/billable-usage.mdx
@@ -40,12 +40,12 @@ Hover over any bar to see the per-product cost breakdown for that day.
 
 Below the chart, a sortable table breaks down usage by product for the full billing period.
 
-| Column | Description |
-| --- | --- |
-| **Product** | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
-| **Total usage** | Total metered usage for the billing period, including any free-tier allowance. |
-| **Billable usage** | Usage that exceeds the free tier and will be charged. |
-| **Usage cost** | Cumulative cost for the product in the selected billing period. |
+| Column             | Description                                                                                                                                              |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Product**        | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
+| **Total usage**    | Total metered usage for the billing period, including any free-tier allowance.                                                                           |
+| **Billable usage** | Usage that exceeds the free tier and will be charged.                                                                                                    |
+| **Usage cost**     | Cumulative cost for the product in the selected billing period.                                                                                          |
 
 Use the **product filter** at the top of the page to narrow the chart and table to specific products.
 
@@ -62,8 +62,6 @@ The dashboard reads from the same data source that generates your monthly invoic
 - Costs reflect the published rate card for your account.
 - The total usage cost shown at the end of a completed billing period matches the usage overage charges on the corresponding invoice.
 
-
-
 ## Set up budget alerts
 
 To get notified when your spend crosses a dollar threshold, you can create budget alerts directly from the dashboard. For detailed instructions, refer to [Budget alerts](/billing/manage/budget-alerts/).
@@ -73,4 +71,3 @@ To get notified when your spend crosses a dollar threshold, you can create budge
 - [Budget alerts](/billing/manage/budget-alerts/) — Get notified when spend crosses a threshold
 - [Usage-based billing](/billing/understand/usage-based-billing/) — Which products use metered billing
 - [How charges accrue](/billing/understand/how-charges-accrue/) — How a request generates charges across products
-
diff --git a/src/content/docs/billing/manage/budget-alerts.mdx b/src/content/docs/billing/manage/budget-alerts.mdx
index 0fb4fdd9330e059..c5cf2ff7f15fc1c 100644
--- a/src/content/docs/billing/manage/budget-alerts.mdx
+++ b/src/content/docs/billing/manage/budget-alerts.mdx
@@ -28,12 +28,12 @@ Budget alerts are available to Pay-as-you-go accounts only. Enterprise contract
 5. Select **Create budget alert**.
 6. Configure the alert:
 
-   | Field | Description |
-   | --- | --- |
-   | **Alert name** | A descriptive name for the alert (for example, "R2 spend warning"). |
-   | **Description** | *(Optional)* A note about when this alert should fire. |
+   | Field                      | Description                                                                                                                                                           |
+   | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | **Alert name**             | A descriptive name for the alert (for example, "R2 spend warning").                                                                                                   |
+   | **Description**            | _(Optional)_ A note about when this alert should fire.                                                                                                                |
    | **Budget threshold (USD)** | The dollar amount that triggers the alert. When your cumulative usage-based spend for the current billing period crosses this value, Cloudflare sends a notification. |
-   | **Email recipients** | One or more email addresses to notify. Select **Add email** to add additional recipients. |
+   | **Email recipients**       | One or more email addresses to notify. Select **Add email** to add additional recipients.                                                                             |
 
 7. Select **Save**.
 
@@ -54,12 +54,12 @@ From there you can edit or delete existing alerts.
 
 Cloudflare offers two types of spend monitoring:
 
-| Feature | Budget alerts | Usage notifications |
-| --- | --- | --- |
-| **Scope** | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
-| **Threshold** | Dollar amount | Product-specific metric (bytes, requests, minutes) |
-| **Setup location** | **Billing** > **Billable Usage** | **Notifications** |
-| **Best for** | Overall cost management | Monitoring a single product |
+| Feature            | Budget alerts                                   | Usage notifications                                       |
+| ------------------ | ----------------------------------------------- | --------------------------------------------------------- |
+| **Scope**          | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
+| **Threshold**      | Dollar amount                                   | Product-specific metric (bytes, requests, minutes)        |
+| **Setup location** | **Billing** > **Billable Usage**                | **Notifications**                                         |
+| **Best for**       | Overall cost management                         | Monitoring a single product                               |
 
 For per-product usage notifications, refer to [Usage-based billing](/billing/understand/usage-based-billing/#usage-based-billing-notifications).
 
diff --git a/src/content/docs/billing/manage/cancel-subscription.mdx b/src/content/docs/billing/manage/cancel-subscription.mdx
index c80dba8a8bcf6e3..5fdf55b5596082d 100644
--- a/src/content/docs/billing/manage/cancel-subscription.mdx
+++ b/src/content/docs/billing/manage/cancel-subscription.mdx
@@ -32,17 +32,17 @@ To disable a subscription:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Select the feature you want to disable under **Active Subscriptions** (Free or Pro customers) or **Plan Extensions** (Enterprise customers).
-4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing *Disable* from a drop-down list.
+4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing _Disable_ from a drop-down list.
 
 ## Step 2: Cancel the subscription in your billing profile
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Find the subscription you want to disable and select **Cancel**.
diff --git a/src/content/docs/billing/manage/invoices.mdx b/src/content/docs/billing/manage/invoices.mdx
index ba940ef55e961bd..43d7879767a806f 100644
--- a/src/content/docs/billing/manage/invoices.mdx
+++ b/src/content/docs/billing/manage/invoices.mdx
@@ -12,10 +12,10 @@ import { DashButton } from "~/components";
 
 You will receive an invoice in the **Billing** section of your Cloudflare account when you:
 
-* Change your Cloudflare plan type.
-* Upgrade or downgrade to or from a paid plan.
-* Add a new domain to a Cloudflare account.
-* Enable or renew a subscription or add-on service.
+- Change your Cloudflare plan type.
+- Upgrade or downgrade to or from a paid plan.
+- Add a new domain to a Cloudflare account.
+- Enable or renew a subscription or add-on service.
 
 For any historical invoices not included in the **Billing** section, [contact Cloudflare support](/support/contacting-cloudflare-support/).
 
@@ -29,25 +29,25 @@ To enable Cloudflare invoice emails which are sent when you add or remove subscr
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
-    
-3. Select **Invoices & Documents**.
-4. From **Billing email preferences**, toggle the notification switch to **On**.
+   <DashButton url="/?to=/:account/billing" />
+
+2. Select **Invoices & Documents**.
+3. From **Billing email preferences**, toggle the notification switch to **On**.
 
 After you enable email invoices, you will receive invoices via email:
 
-* Within one business day of initial set-up.
-* Every month at the end of your billing period.
-* Within one business day for all new purchases.
+- Within one business day of initial set-up.
+- Every month at the end of your billing period.
+- Within one business day for all new purchases.
 
 ## Download invoice
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices & Documents**.
-4. Find the invoice you want to download and select the icon next to the invoice number.
+3. Find the invoice you want to download and select the icon next to the invoice number.
 
 :::note
 Invoices cannot be regenerated after they are issued. Any pending billing updates or changes will appear in the next month's invoice.
diff --git a/src/content/docs/billing/manage/optimize-costs.mdx b/src/content/docs/billing/manage/optimize-costs.mdx
index 1ebb06ae5ce6d13..f4d34d4f201f6a3 100644
--- a/src/content/docs/billing/manage/optimize-costs.mdx
+++ b/src/content/docs/billing/manage/optimize-costs.mdx
@@ -10,10 +10,10 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 ## General strategies
 
-| Strategy | Impact |
-|---|---|
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | Prevents surprise invoices across all products |
-| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives |
+| Strategy                                                                                              | Impact                                                      |
+| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early               | Prevents surprise invoices across all products              |
+| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives            |
 | Understand [how charges accrue](/billing/understand/how-charges-accrue/) across the request lifecycle | Identifies which stage of a request generates the most cost |
 
 ## Per-product optimization
@@ -22,42 +22,42 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 Cached responses are the cheapest path through Cloudflare. Every cache hit avoids origin fetch costs, Argo routing charges, and Workers execution.
 
-| Strategy | What it reduces |
-|---|---|
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
+| Strategy                                                                                                              | What it reduces                                                              |
+| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                                     | Argo data transfer, Workers invocations, origin load                         |
 | Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content that is accessed infrequently | Origin fetches — keeps content cached even when it would normally be evicted |
-| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls | Origin bandwidth and Argo transfer between Cloudflare data centers |
-| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default | Overall cache hit ratio |
+| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls                                              | Origin bandwidth and Argo transfer between Cloudflare data centers           |
+| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default                           | Overall cache hit ratio                                                      |
 
 ### Workers & Durable Objects
 
-| Strategy | What it reduces |
-|---|---|
-| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush | Logpush-enabled Workers requests and Logpush data transfer |
+| Strategy                                                                                                                                                                       | What it reduces                                                                 |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
+| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush                                                                             | Logpush-enabled Workers requests and Logpush data transfer                      |
 | Use the [WebSocket Hibernation API](/durable-objects/best-practices/websockets/#durable-objects-hibernation-websocket-api) for Durable Objects with idle WebSocket connections | Duration (GB-s) charges — billing pauses while the Durable Object is hibernated |
 
 ### R2
 
-| Strategy | What it reduces |
-|---|---|
-| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data |
-| Batch R2 operations where possible instead of per-object reads | Class B operation count |
-| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers | Workers invocations and CPU time |
-| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache | Class B reads — cached objects do not hit R2 |
+| Strategy                                                                                                                | What it reduces                              |
+| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
+| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data              |
+| Batch R2 operations where possible instead of per-object reads                                                          | Class B operation count                      |
+| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers           | Workers invocations and CPU time             |
+| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache            | Class B reads — cached objects do not hit R2 |
 
 ### Stream and Images
 
-| Strategy | What it reduces |
-|---|---|
-| Set appropriate cache headers on Stream embed pages | Repeated Stream delivery minutes |
+| Strategy                                                                                                                           | What it reduces                                  |
+| ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
+| Set appropriate cache headers on Stream embed pages                                                                                | Repeated Stream delivery minutes                 |
 | Use [Image Resizing URL format](/images/optimization/features/) with width/height parameters to serve appropriately sized variants | Transformation count — sized variants are cached |
 
 ### Load Balancing
 
-| Strategy | What it reduces |
-|---|---|
+| Strategy                                                                                      | What it reduces                        |
+| --------------------------------------------------------------------------------------------- | -------------------------------------- |
 | Set health check intervals to the longest acceptable value for your availability requirements | DNS queries to load-balanced hostnames |
-| Use fewer health check regions where regional redundancy is not critical | Health check frequency multiplier |
+| Use fewer health check regions where regional redundancy is not critical                      | Health check frequency multiplier      |
 
 ## Monitor and alert
 
diff --git a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
index 2b082f37ba9f84f..e55450f95a43eb4 100644
--- a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
+++ b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
@@ -12,7 +12,6 @@ import { DashButton } from "~/components";
 
 If automatic payment retries fail and you do not pay manually, your account accrues an overdue balance. While the balance is unpaid, you cannot purchase products, upgrade subscriptions, or update your billing profile. Attempts to do so return an error:
 
-
 **"You cannot add or modify subscriptions or services until the outstanding balance is paid."**
 
 To pay, select **Pay Now** from the **Billing** page in the Cloudflare dashboard. You can pay the entire balance in one transaction or [pay individual invoices](#manually-pay-invoices) separately.
@@ -23,7 +22,7 @@ When an outstanding balance is due, a new invoice will be created in your accoun
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select the most recent invoice - the amount shown should match your outstanding balance
@@ -40,7 +39,7 @@ To pay the total outstanding balance:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Pay overdue balances** section.
 3. Select **Pay now** next to the balance you want to pay.
@@ -53,7 +52,7 @@ If an automatic subscription renewal payment fails, Cloudflare automatically ret
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-    <DashButton url="/?to=/:account/billing" />
+   <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select **Pay now** next to the invoice you want to pay.
diff --git a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
index f4e3aa40ed248b0..181362bc0ffcd63 100644
--- a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
+++ b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
@@ -33,9 +33,9 @@ Instant Bank Payments via Link is available to US-based self-serve accounts acro
 
 Bank-based Link payments appear in your billing history with these identifiers:
 
-| Field | Value |
-| --- | --- |
-| Payment method | `link` |
+| Field            | Value  |
+| ---------------- | ------ |
+| Payment method   | `link` |
 | Last four digits | `0000` |
 
 Card-based Link payments display your card's last four digits, distinguishing them from bank payments.
diff --git a/src/content/docs/billing/threshold-billing.mdx b/src/content/docs/billing/threshold-billing.mdx
index 0c72335ac0c6b0a..856ef82e55f97e7 100644
--- a/src/content/docs/billing/threshold-billing.mdx
+++ b/src/content/docs/billing/threshold-billing.mdx
@@ -27,11 +27,11 @@ You will never be double-charged. The threshold invoice and end-of-cycle invoice
 
 ### Example
 
-| Event | Charge |
-| --- | --- |
-| Combined usage reaches threshold mid-cycle | Threshold invoice charged (for example, $127.50) |
+| Event                                       | Charge                                             |
+| ------------------------------------------- | -------------------------------------------------- |
+| Combined usage reaches threshold mid-cycle  | Threshold invoice charged (for example, $127.50)   |
 | End of billing cycle (total usage was $180) | End-of-cycle invoice charged (for example, $52.50) |
-| **Total charged** | **$180** |
+| **Total charged**                           | **$180**                                           |
 
 ## Products subject to threshold billing
 
diff --git a/src/content/docs/billing/troubleshoot/error-reference.mdx b/src/content/docs/billing/troubleshoot/error-reference.mdx
index e2fbd524b5852d0..ea345499f66f805 100644
--- a/src/content/docs/billing/troubleshoot/error-reference.mdx
+++ b/src/content/docs/billing/troubleshoot/error-reference.mdx
@@ -12,21 +12,21 @@ Use the table below to find common billing error messages, understand what they
 
 ## Error messages
 
-| Error message | Cause | Solution |
-|---|---|---|
-| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/). |
-| "The payment has failed. Please contact your bank or use a different payment method." | Your payment method was declined by your bank. | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
-| "Payment error: authorization failed" | Your bank declined the transaction, or 3DS authentication was not completed. | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
-| "This zone cannot be upgraded" | The account or a previous owner of the domain has an outstanding balance. | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
-| "There is a problem with your billing profile" | Same as "this zone cannot be upgraded" — an unpaid balance exists. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours. |
-| "You cannot modify this subscription since it is currently scheduled to be cancelled" | You are trying to change a subscription that already has a pending cancellation. | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/). |
-| "You can't remove this payment method while it's linked to active subscriptions." | You are trying to delete a payment method that is still tied to paid services. | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
-| "You can't remove a payment method while there are transactions in progress." | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
+| Error message                                                                               | Cause                                                                                 | Solution                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance.                                                   | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/).                                                                                                               |
+| "The payment has failed. Please contact your bank or use a different payment method."       | Your payment method was declined by your bank.                                        | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                             |
+| "Payment error: authorization failed"                                                       | Your bank declined the transaction, or 3DS authentication was not completed.          | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                                          |
+| "This zone cannot be upgraded"                                                              | The account or a previous owner of the domain has an outstanding balance.             | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
+| "There is a problem with your billing profile"                                              | Same as "this zone cannot be upgraded" — an unpaid balance exists.                    | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours.                                                                                             |
+| "You cannot modify this subscription since it is currently scheduled to be cancelled"       | You are trying to change a subscription that already has a pending cancellation.      | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/).     |
+| "You can't remove this payment method while it's linked to active subscriptions."           | You are trying to delete a payment method that is still tied to paid services.        | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).    |
+| "You can't remove a payment method while there are transactions in progress."               | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).                       |
 
 ## Email notifications
 
-| Email subject | What it means | What to do |
-|---|---|---|
+| Email subject                              | What it means                                                                            | What to do                                                                                                                                                                      |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | "We couldn't process your renewal payment" | A recurring subscription charge failed. Cloudflare will retry up to 5 times over 5 days. | Update your payment method or manually pay the invoice before the grace period ends. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
 
 ## Still stuck?
diff --git a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
index 276892b5ec3390d..8cbc680da963f94 100644
--- a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
@@ -10,13 +10,14 @@ products:
 
 When attempting to remove a payment method, you may see one of the following error messages:
 
-* "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
-* "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
+- "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
+- "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
 
 ## Causes
-* You still have active paid subscriptions
-* You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
-* You have an upcoming Registrar domain registration renewal within the next 24 hours
+
+- You still have active paid subscriptions
+- You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
+- You have an upcoming Registrar domain registration renewal within the next 24 hours
 
 ## Solutions
 
@@ -36,19 +37,19 @@ Repeat this for all active paid subscriptions before attempting to remove the pa
 
 If you have cancelled all paid subscriptions, any usage-based products cancelled within the last 30 days may still generate charges. Your payment method must remain on file until those charges are processed. If you recently cancelled any of the following products, wait 30 days before removing your payment method:
 
-* Images
-* Stream
-* Workers
-* Argo
-* Spectrum
-* R2
-* Cache Reserve
-* Load Balancing
-* Rate Limiting
-* Log Explorer
-* Zero Trust
-* Vectorize
-* Analytics
+- Images
+- Stream
+- Workers
+- Argo
+- Spectrum
+- R2
+- Cache Reserve
+- Load Balancing
+- Rate Limiting
+- Log Explorer
+- Zero Trust
+- Vectorize
+- Analytics
 
 After the next monthly invoice is generated, you can remove the payment method.
 
diff --git a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
index b43d3e71c65fec6..eb388902186d5ac 100644
--- a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
@@ -10,16 +10,19 @@ products:
 
 When attempting to cancel or modify a subscription, you may see the following error message:
 
-* "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
+- "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
 
 ## Causes
-* You are attempting to cancel a subscription which you have already requested cancellation for
-* You are attempting to upgrade a subscription for which a cancellation is already scheduled
+
+- You are attempting to cancel a subscription which you have already requested cancellation for
+- You are attempting to upgrade a subscription for which a cancellation is already scheduled
 
 ## Solutions
+
 If you intended to cancel a subscription, the cancellation is already scheduled. Your subscription ends at the close of the current billing period. Refer to the section below to find the exact date.
 
 ### When will my subscription be cancelled?
+
 After requesting cancellation, the subscriptions page shows the end date under "Ending On".
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
@@ -31,6 +34,7 @@ After requesting cancellation, the subscriptions page shows the end date under "
 If you previously cancelled the subscription and have changed your decision, you need to cancel the downgrade.
 
 ### Can I receive a refund for my cancelled subscription?
+
 No refund will be issued for a cancelled subscription - instead, your subscription will remain active until the end of the current billing period.
 
 If you do not wish to pay for the coming billing period, then you should cancel your subscription no later than on the last day of the billing period. You can discover this date by visiting the **Subscriptions** page and checking the renew date, for example “RENEWS ON Aug 29, 2025”.
@@ -55,4 +59,4 @@ If the cancellation hasn’t taken effect yet, you can click **Cancel Downgrade*
 
 - [Cancel subscriptions](/billing/manage/cancel-subscription/) — How cancellations work
 - [Billing policy](/billing/understand/billing-policy/) — Refund policy and billing terms
-- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
\ No newline at end of file
+- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
diff --git a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
index aba89709e47d926..32e60e707eb83a6 100644
--- a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
+++ b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
@@ -34,4 +34,4 @@ You may have to wait up to one billing period for updates to appear in your Clou
 
 - [Invoices](/billing/manage/invoices/) — Download and manage invoices
 - [How Cloudflare billing works](/billing/understand/how-billing-works/) — How to read your invoice
-- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
\ No newline at end of file
+- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
diff --git a/src/content/docs/billing/understand/billing-permissions.mdx b/src/content/docs/billing/understand/billing-permissions.mdx
index f0a656bc1f33ea6..90f8f01686d0a1a 100644
--- a/src/content/docs/billing/understand/billing-permissions.mdx
+++ b/src/content/docs/billing/understand/billing-permissions.mdx
@@ -10,19 +10,19 @@ Access to billing features in the Cloudflare dashboard depends on the role assig
 
 ## Roles and billing capabilities
 
-| Action | Super Administrator | Administrator | Billing |
-|---|---|---|---|
-| View invoices and billing history | Yes | Yes | Yes |
-| Download invoice PDFs | Yes | Yes | Yes |
-| View billable usage dashboard | Yes | Yes | Yes |
-| Pay an outstanding balance | Yes | No | Yes |
-| Add or update payment methods | Yes | No | Yes |
-| Change billing address | Yes | No | Yes |
-| Change billing email | Yes | No | Yes |
-| Set up budget alerts | Yes | Yes | Yes |
-| Change or cancel subscriptions | Yes | Yes | No |
-| Upgrade or downgrade a domain plan | Yes | Yes | No |
-| Manage account members and roles | Yes | No | No |
+| Action                             | Super Administrator | Administrator | Billing |
+| ---------------------------------- | ------------------- | ------------- | ------- |
+| View invoices and billing history  | Yes                 | Yes           | Yes     |
+| Download invoice PDFs              | Yes                 | Yes           | Yes     |
+| View billable usage dashboard      | Yes                 | Yes           | Yes     |
+| Pay an outstanding balance         | Yes                 | No            | Yes     |
+| Add or update payment methods      | Yes                 | No            | Yes     |
+| Change billing address             | Yes                 | No            | Yes     |
+| Change billing email               | Yes                 | No            | Yes     |
+| Set up budget alerts               | Yes                 | Yes           | Yes     |
+| Change or cancel subscriptions     | Yes                 | Yes           | No      |
+| Upgrade or downgrade a domain plan | Yes                 | Yes           | No      |
+| Manage account members and roles   | Yes                 | No            | No      |
 
 :::note
 The Billing role can view and pay but cannot change subscriptions or plans. To both manage subscriptions and handle payments, a user needs the Super Administrator role.
diff --git a/src/content/docs/billing/understand/billing-policy.mdx b/src/content/docs/billing/understand/billing-policy.mdx
index 14a33c5e72ce247..b980bae02a464c9 100644
--- a/src/content/docs/billing/understand/billing-policy.mdx
+++ b/src/content/docs/billing/understand/billing-policy.mdx
@@ -81,15 +81,15 @@ Enterprise account owners receive invoices directly from the Cloudflare accounti
 
 Cloudflare accepts the following payment methods:
 
-* Visa
-* Mastercard
-* American Express
-* Discover
-* PayPal
-* Apple Pay
-* Google Pay
-* Stripe Link
-* UnionPay
+- Visa
+- Mastercard
+- American Express
+- Discover
+- PayPal
+- Apple Pay
+- Google Pay
+- Stripe Link
+- UnionPay
 
 :::note
 Enterprise customers can use ACH payments for Cloudflare plans and subscriptions.
diff --git a/src/content/docs/billing/understand/how-charges-accrue.mdx b/src/content/docs/billing/understand/how-charges-accrue.mdx
index 44a3bbcf2906350..d13bbe22d007ff3 100644
--- a/src/content/docs/billing/understand/how-charges-accrue.mdx
+++ b/src/content/docs/billing/understand/how-charges-accrue.mdx
@@ -26,17 +26,17 @@ Consider a visitor loading a page on a Pro domain that uses Workers, R2, Argo Sm
 
 The visitor's browser resolves the domain. This DNS query is handled by Cloudflare's authoritative DNS.
 
-| Resource | Billing impact |
-|---|---|
+| Resource    | Billing impact                                                                                                                                 |
+| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
 | DNS queries | Included in all plans at no extra charge. If you use Load Balancing, DNS queries to load-balanced hostnames are metered (first 500K included). |
 
 ### 2. Edge request and TLS
 
 The request arrives at the nearest Cloudflare data center. Cloudflare terminates TLS and processes the request.
 
-| Resource | Billing impact |
-|---|---|
-| TLS/SSL | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
+| Resource | Billing impact                                                                              |
+| -------- | ------------------------------------------------------------------------------------------- |
+| TLS/SSL  | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
 
 ### 3. Cache lookup
 
@@ -44,9 +44,9 @@ Cloudflare checks whether a cached response exists for this request.
 
 **Cache hit** — the response is served directly from the edge. No origin fetch occurs. This is the cheapest path.
 
-| Resource | Billing impact |
-|---|---|
-| Bandwidth | Included in all plans. Cloudflare does not charge for bandwidth. |
+| Resource            | Billing impact                                                                                                                                                                                      |
+| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bandwidth           | Included in all plans. Cloudflare does not charge for bandwidth.                                                                                                                                    |
 | Cache Reserve reads | If Cache Reserve is enabled and the asset is served from tiered cache storage, reads are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 **Cache miss** — the request must be forwarded to the origin. Continue to step 4.
@@ -55,53 +55,53 @@ Cloudflare checks whether a cached response exists for this request.
 
 If Argo is enabled, Cloudflare routes the request through the fastest path across its network to your origin.
 
-| Resource | Billing impact |
-|---|---|
+| Resource           | Billing impact                                                                                                                                             |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Argo data transfer | Metered per GB transferred between Cloudflare and your origin. First 1 GB included. Refer to [Argo Smart Routing](/argo-smart-routing/) for current rates. |
 
 ### 5. Workers execution (if configured)
 
 If a Worker is bound to the route, it executes before or instead of fetching from the origin.
 
-| Resource | Billing impact |
-|---|---|
-| Worker requests | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Worker CPU time | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates. |
+| Resource                | Billing impact                                                                                                                                    |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Worker requests         | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Worker CPU time         | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates.        |
+| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates.   |
 
 ### 6. Origin fetch and response
 
 If the Worker or cache miss triggers an origin fetch, Cloudflare retrieves the response from your origin server.
 
-| Resource | Billing impact |
-|---|---|
+| Resource  | Billing impact                                                                   |
+| --------- | -------------------------------------------------------------------------------- |
 | Bandwidth | No charge for data transfer between Cloudflare and your origin (no egress fees). |
 
 ### 7. R2 storage operations (if used)
 
 If the Worker or origin logic reads from or writes to R2, each operation is metered.
 
-| Resource | Billing impact |
-|---|---|
-| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 Class B operations (reads) | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 storage | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 data egress | Free. Cloudflare does not charge for R2 egress. |
+| Resource                       | Billing impact                                                                     |
+| ------------------------------ | ---------------------------------------------------------------------------------- |
+| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.   |
+| R2 Class B operations (reads)  | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.  |
+| R2 storage                     | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 data egress                 | Free. Cloudflare does not charge for R2 egress.                                    |
 
 ### 8. Cache write (miss path)
 
 After fetching from the origin, Cloudflare caches the response at the edge for future requests.
 
-| Resource | Billing impact |
-|---|---|
+| Resource             | Billing impact                                                                                                                                     |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cache Reserve writes | If Cache Reserve is enabled, writes are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 ### 9. Image Resizing (if configured)
 
 If the request triggers Image Resizing (via URL parameters or a Worker), the transformation is metered.
 
-| Resource | Billing impact |
-|---|---|
+| Resource              | Billing impact                                                                                                                       |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
 | Image transformations | First 50,000 included on the Business plan, then metered per request. Refer to [Images pricing](/images/pricing/) for current rates. |
 
 ### 10. Response delivered
@@ -116,15 +116,15 @@ The key takeaway: **cached responses are the cheapest path**. Every cache hit av
 
 ## Cost optimization strategies
 
-| Strategy | Products affected | Impact |
-|---|---|---|
-| Maximize cache hit ratio with appropriate Cache-Control headers | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs |
-| Use Cache Reserve for long-tail content | Cache, origin | Medium — reduces origin fetches for infrequently accessed content |
-| Set appropriate TTLs to avoid unnecessary revalidation | Cache, Argo | Medium — reduces origin round-trips |
-| Use Workers Smart Placement to run Workers closer to your data | Workers CPU time | Medium — reduces execution time for data-dependent Workers |
-| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage | Medium — reduces storage costs for archival data |
-| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/) | All usage-based products | High — visibility is the first step to optimization |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes | All usage-based products | High — prevents surprise invoices |
+| Strategy                                                                            | Products affected               | Impact                                                            |
+| ----------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------- |
+| Maximize cache hit ratio with appropriate Cache-Control headers                     | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs               |
+| Use Cache Reserve for long-tail content                                             | Cache, origin                   | Medium — reduces origin fetches for infrequently accessed content |
+| Set appropriate TTLs to avoid unnecessary revalidation                              | Cache, Argo                     | Medium — reduces origin round-trips                               |
+| Use Workers Smart Placement to run Workers closer to your data                      | Workers CPU time                | Medium — reduces execution time for data-dependent Workers        |
+| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage                      | Medium — reduces storage costs for archival data                  |
+| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/)  | All usage-based products        | High — visibility is the first step to optimization               |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes   | All usage-based products        | High — prevents surprise invoices                                 |
 
 ## Related resources
 
diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx
index 0be6d9d6118dc30..4b7d658484684f6 100644
--- a/src/content/docs/billing/understand/preview-services.mdx
+++ b/src/content/docs/billing/understand/preview-services.mdx
@@ -29,7 +29,7 @@ To enable a preview service, use the **Dashboard link** in the following table.
 | Load Balancing                     | [Load Balancing dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing)          | [Load Balancing docs](/load-balancing/)                                    | [Load Balancing community](https://community.cloudflare.com/tag/loadbalancing) |
 | Advanced Rate Limiting             | [Rate Limiting dashboard](https://dash.cloudflare.com/?to=/:account/:zone/security/waf/rate-limiting-rules) | [Rate Limiting docs](/waf/rate-limiting-rules/)                            | [Rate Limiting community](https://community.cloudflare.com/c/security/6)       |
 | Stream                             | [Stream dashboard](https://dash.cloudflare.com/?to=/:account/stream)                                        | [Stream docs](/stream/)                                                    | [Stream community](https://community.cloudflare.com/tag/cloudflarestream)      |
-| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)        | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
+| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)             | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
 | Web3                               | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3)                                      | [Web3 docs](/web3/)                                                        | [Web3 discord](https://discord.cloudflare.com)                                 |
 | Workers                            | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers)                                      | [Workers docs](/workers/)                                                  | [Workers discord](https://discord.com/invite/cloudflaredev)                    |
 | Zero Trust                         | [Zero Trust dashboard](https://one.dash.cloudflare.com/)                                                    | [Zero Trust docs](/cloudflare-one/)                                        | [Zero Trust community](https://community.cloudflare.com/c/security/access/51)  |
diff --git a/src/content/docs/billing/understand/usage-based-billing.mdx b/src/content/docs/billing/understand/usage-based-billing.mdx
index 2e7cc4c49963e48..c3270b67c1b766d 100644
--- a/src/content/docs/billing/understand/usage-based-billing.mdx
+++ b/src/content/docs/billing/understand/usage-based-billing.mdx
@@ -24,29 +24,29 @@ The following products bill based on consumption. Each product includes a free t
 
 For current overage rates, refer to the [Cloudflare plans page](https://www.cloudflare.com/plans/) or each product's pricing page linked below. Rates may change — the links below are always up to date.
 
-| Product | Billable metric | Free tier (included) | Pricing details |
-|---|---|---|---|
-| [Workers](/workers/platform/pricing/) | Requests, CPU time | 10M requests, 30M CPU-ms | [Workers pricing](/workers/platform/pricing/) |
-| [R2](/r2/pricing/) | Storage, operations | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/) |
-| [Argo Smart Routing](/argo-smart-routing/) | Data transfer (GB) | First 1 GB | [Argo pricing](/argo-smart-routing/) |
-| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage | None | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
-| [Load Balancing](/load-balancing/) | DNS queries | First 500K | [Load Balancing](/load-balancing/) |
-| [Stream](/stream/pricing/) | Minutes stored, minutes viewed | Varies by plan | [Stream pricing](/stream/pricing/) |
-| [Images](/images/pricing/) | Transformations, storage | Varies by plan | [Images pricing](/images/pricing/) |
-| [Spectrum](/spectrum/) | Data transfer (GB) | None | [Spectrum](/spectrum/) |
+| Product                                                       | Billable metric                | Free tier (included)                   | Pricing details                                                       |
+| ------------------------------------------------------------- | ------------------------------ | -------------------------------------- | --------------------------------------------------------------------- |
+| [Workers](/workers/platform/pricing/)                         | Requests, CPU time             | 10M requests, 30M CPU-ms               | [Workers pricing](/workers/platform/pricing/)                         |
+| [R2](/r2/pricing/)                                            | Storage, operations            | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/)                                            |
+| [Argo Smart Routing](/argo-smart-routing/)                    | Data transfer (GB)             | First 1 GB                             | [Argo pricing](/argo-smart-routing/)                                  |
+| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage         | None                                   | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
+| [Load Balancing](/load-balancing/)                            | DNS queries                    | First 500K                             | [Load Balancing](/load-balancing/)                                    |
+| [Stream](/stream/pricing/)                                    | Minutes stored, minutes viewed | Varies by plan                         | [Stream pricing](/stream/pricing/)                                    |
+| [Images](/images/pricing/)                                    | Transformations, storage       | Varies by plan                         | [Images pricing](/images/pricing/)                                    |
+| [Spectrum](/spectrum/)                                        | Data transfer (GB)             | None                                   | [Spectrum](/spectrum/)                                                |
 
 ## Optimize usage-based costs
 
 Reducing usage-based charges starts with understanding where your consumption comes from. Use the [billable usage dashboard](/billing/manage/billable-usage/) to identify which products are driving costs, then apply the strategies below.
 
-| Strategy | What it reduces |
-|---|---|
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
-| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content | Origin fetches for infrequently accessed assets |
-| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs |
-| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers | Workers CPU time |
-| Batch R2 operations where possible instead of per-object reads | R2 Class B operation count |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | All products — prevents surprise invoices |
+| Strategy                                                                                                 | What it reduces                                      |
+| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                        | Argo data transfer, Workers invocations, origin load |
+| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content                  | Origin fetches for infrequently accessed assets      |
+| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs                                     |
+| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers                  | Workers CPU time                                     |
+| Batch R2 operations where possible instead of per-object reads                                           | R2 Class B operation count                           |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early                  | All products — prevents surprise invoices            |
 
 For a detailed walkthrough of how a single request generates charges across multiple products, refer to [How charges accrue](/billing/understand/how-charges-accrue/).
 
diff --git a/src/content/docs/bots/account-abuse-protection.mdx b/src/content/docs/bots/account-abuse-protection.mdx
index ddd1362d953258a..e54a667206310fc 100644
--- a/src/content/docs/bots/account-abuse-protection.mdx
+++ b/src/content/docs/bots/account-abuse-protection.mdx
@@ -12,16 +12,15 @@ sidebar:
   badge:
     text: Early Access
     variant: note
-
 ---
 
-import { Render, Description, DashButton, Steps } from "~/components"
+import { Render, Description, DashButton, Steps } from "~/components";
 
 <Description>
-Identify and mitigate attacks on your customer and user accounts.
+	Identify and mitigate attacks on your customer and user accounts.
 </Description>
 
-Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems. 
+Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems.
 
 ## Availability
 
@@ -38,15 +37,15 @@ Contact your Cloudflare account team to request access.
 User ID is a cryptographically hashed, per-zone identifier that customers can use in [Security Analytics](/waf/analytics/security-analytics/), [Security Rules](/waf/custom-rules/), and [Managed Transforms](/rules/transform/managed-transforms/reference/). Hashed User IDs are created by encrypting the primary credentials your users provide, converting them into opaque identifiers unique to your zone. This allows traffic analysis while protecting user privacy. With access to hashed User ID, website owners can:
 
 - Review which users have the most activity on your website.
-- Find the details on a specific user's characteristics and activity patterns.  
-- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.  
-- Combine fields to see when accounts are being targeted with leaked credentials.  
+- Find the details on a specific user's characteristics and activity patterns.
+- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.
+- Combine fields to see when accounts are being targeted with leaked credentials.
 - Manage network patterns or signals associated with specific users.
 
 :::note[Data privacy]
-User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications. 
+User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications.
 
-Other Cloudflare customers cannot access your user profiles. They are unique to your zone. 
+Other Cloudflare customers cannot access your user profiles. They are unique to your zone.
 :::
 
 User ID is an opt-in feature that can be enabled in Security Settings.
@@ -65,13 +64,13 @@ To enable, edit, or disable the setting:
 
 ### Ephemeral IDs
 
-Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection. 
+Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection.
 
 Refer to [Fraud detection with ephemeral IDs](/turnstile/tutorials/fraud-detection-with-ephemeral-ids/) for more information.
 
 ### Account takeover detections
 
-Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks. 
+Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks.
 
 Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/) for more information.
 
@@ -85,25 +84,25 @@ Account takeover (ATO) detections are not available for accounts using the [Data
 
 ### Prerequisites
 
-Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior. 
+Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior.
 
 #### Security Settings
 
-- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections. 
+- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections.
 
-#### Eligible traffic 
+#### Eligible traffic
 
-Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations. 
+Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations.
 
 - Sign-ups: Cloudflare automatically monitors traffic on endpoints that match common sign up endpoints.
 - Login: Cloudflare automatically monitors traffic on endpoints that match common login endpoints.
 
 Verify that your endpoints are properly labeled to ensure Cloudflare can detect and monitor them correctly.
 
-<Render 
-  file="endpoint-label-warning" 
-  product="bots"
-  params={{ one: "or sign up" }} 
+<Render
+	file="endpoint-label-warning"
+	product="bots"
+	params={{ one: "or sign up" }}
 />
 
 :::tip[Enhanced with leaked credential detections]
@@ -114,43 +113,43 @@ Cloudflare also recommends enabling [Leaked credentials detection](/waf/detectio
 
 ### Detections
 
-Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints. 
+Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints.
 
 #### Account creation
 
-Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure. 
+Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure.
 
-You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email. 
+You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email.
 
 #### Suspicious emails
 
-Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections. 
+Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections.
 
-Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching. 
+Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching.
 
-| Detection tag | Description |
-| --- | --- |
-| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services. |
-| `cf.fraud.email_risk` | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
+| Detection tag                         | Description                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services.                                                                                                                                                                                                                                                                            |
+| `cf.fraud.email_risk`                 | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
 
---- 
+---
 
 ### Mitigations
 
-The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic. 
+The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic.
 
 #### Security Rules
 
 The following fields can be used in new and existing Security Rules.
 
-| Field | Description | Values |
-| --- | --- | --- |
-| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False` |
-| `cf.fraud.email_risk` | Measures risk of email based on randomness of characters in the username and domain. | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
+| Field                                  | Description                                                                                        | Values                                                                                                                                                                                                                                                              |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False`                                                                                                                                                                                                                                                   |
+| `cf.fraud.email_risk`                  | Measures risk of email based on randomness of characters in the username and domain.               | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
 
 #### Other rules
 
-You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin. 
+You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin.
 
 #### LogPush
 
@@ -160,12 +159,12 @@ You can add Fraud detection fields to existing or new [LogPush](/logs/logpush/)
 
 ## Analytics
 
-You can find Fraud data and detections in Security Analytics, where you can see top User IDs. 
+You can find Fraud data and detections in Security Analytics, where you can see top User IDs.
 
 <DashButton url="/?to=/:account/:zone/security/analytics" />
 
-Fraud fields can be used as filters to identify suspicious patterns in your traffic. 
+Fraud fields can be used as filters to identify suspicious patterns in your traffic.
 
-The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers. 
+The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers.
 
 A user level profile also provides a quick way to review the latest events associated with a user so that you can identify any anomalies and create a custom rule to log, block, or challenge that user.
diff --git a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
index 61260abf06b336f..b666e3479ba08d7 100644
--- a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
+++ b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
@@ -12,7 +12,7 @@ sidebar:
   label: Block AI Bots
 ---
 
-import { Render, Steps, DashButton } from "~/components"
+import { Render, Steps, DashButton } from "~/components";
 
 :::note[Block AI bots availability]
 The **Block AI bots** feature is only available in the new [application security dashboard](/security/).
@@ -35,4 +35,4 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
   5. Select **Save** to save your configuration.
 </Steps>
 
-To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
\ No newline at end of file
+To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
diff --git a/src/content/docs/bots/additional-configurations/custom-rules.mdx b/src/content/docs/bots/additional-configurations/custom-rules.mdx
index 287bace657d036c..fca74fa82b41d73 100644
--- a/src/content/docs/bots/additional-configurations/custom-rules.mdx
+++ b/src/content/docs/bots/additional-configurations/custom-rules.mdx
@@ -16,17 +16,17 @@ Bot protection on Cloudflare works through two complementary mechanisms: built-i
 
 The following features are configured through toggles and dropdowns in [Security Settings](/security/settings/). They do not require you to write any rule expressions.
 
-| Feature | What it does | Availability |
-| --- | --- | --- |
-| [Block AI bots](/bots/additional-configurations/block-ai-bots/) | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans |
-| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/) | Feeds non-compliant AI crawlers into a maze of generated content | All plans |
-| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/) | Prepends AI crawler disallow directives to your `robots.txt` | All plans |
-| Super Bot Fight Mode > **Definitely automated** | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1 | Pro, Business, Enterprise |
-| Super Bot Fight Mode > **Likely automated** | Blocks or challenges traffic with a bot score of 2-29 | Business, Enterprise |
-| [Verified bots](/bots/concepts/bot/verified-bots/) | Managed category of high-trust bots (Googlebot, Bingbot, and others) | Pro, Business, Enterprise |
-| [Static resource protection](/bots/additional-configurations/static-resources/) | Extends bot actions to cover static file types | Pro, Business, Enterprise |
-| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/) | Allows WordPress loopback requests through bot protection | Pro, Business, Enterprise |
-| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript | All plans (automatic on Free) |
+| Feature                                                                                | What it does                                                                                       | Availability                  |
+| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- |
+| [Block AI bots](/bots/additional-configurations/block-ai-bots/)                        | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans                     |
+| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/)                          | Feeds non-compliant AI crawlers into a maze of generated content                                   | All plans                     |
+| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/)              | Prepends AI crawler disallow directives to your `robots.txt`                                       | All plans                     |
+| Super Bot Fight Mode > **Definitely automated**                                        | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1                    | Pro, Business, Enterprise     |
+| Super Bot Fight Mode > **Likely automated**                                            | Blocks or challenges traffic with a bot score of 2-29                                              | Business, Enterprise          |
+| [Verified bots](/bots/concepts/bot/verified-bots/)                                     | Managed category of high-trust bots (Googlebot, Bingbot, and others)                               | Pro, Business, Enterprise     |
+| [Static resource protection](/bots/additional-configurations/static-resources/)        | Extends bot actions to cover static file types                                                     | Pro, Business, Enterprise     |
+| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/)              | Allows WordPress loopback requests through bot protection                                          | Pro, Business, Enterprise     |
+| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript                    | All plans (automatic on Free) |
 
 Bot settings update automatically as Cloudflare identifies new bot signatures and AI crawlers, while custom rules require manual updates. They do not count toward your [custom rule limits](/waf/custom-rules/#availability), and apply uniformly across your domain without the risk of expression errors.
 
diff --git a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
index ce92bacfafafb92..d36b1802e907d09 100644
--- a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
@@ -12,7 +12,6 @@ Cloudflare bot detection includes additional signals to catch different kinds of
 
 Bot management customers automatically benefit from the residential proxy detection improvement below, which lowers the [bot score](/bots/concepts/bot-score/) for matched requests. Using the detection ID in [custom rules](/waf/custom-rules/) provides even more visibility and control over mitigating residential proxy traffic.
 
-
-| <div style="width:100px">Detection ID</div> | Description                              |
-| ------------------------------------------ | ---------------------------------------- |
-| `50331651`                                 | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
+| <div style="width:100px">Detection ID</div> | Description                                                                                                                                                                                                                                                                               |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `50331651`                                  | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
diff --git a/src/content/docs/bots/additional-configurations/index.mdx b/src/content/docs/bots/additional-configurations/index.mdx
index 0768d508f998fd1..bc876caf734e5e0 100644
--- a/src/content/docs/bots/additional-configurations/index.mdx
+++ b/src/content/docs/bots/additional-configurations/index.mdx
@@ -11,11 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Additional Bots configurations
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on additional bot management configurations:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
index b575e485e4d47b1..f8af19b5b7de7b0 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 1
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 [**JA3**](https://github.com/salesforce/ja3) and [**JA4**](https://github.com/FoxIO-LLC/ja4) **fingerprints** identify TLS clients based on how they initiate connections. Each client type (browser, bot, or application) has distinct connection characteristics, so the resulting fingerprint acts as a stable identifier across different destination IPs, ports, and certificates.
 
@@ -17,64 +16,62 @@ JA4 improves on JA3 by sorting ClientHello extensions, which reduces the number
 
 :::note
 
-JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management. 
+JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management.
 :::
 
 <Render file="signals-intelligence-and-ja4" product="bots" />
 
 ```json
-
 {
-  "ja4Signals": {
-    "h2h3_ratio_1h": 0.98826485872269,
-    "heuristic_ratio_1h": 7.288895722013e-05,
-    "reqs_quantile_1h": 0.99905741214752,
-    "uas_rank_1h": 901,
-    "browser_ratio_1h": 0.93640440702438,
-    "paths_rank_1h": 655,
-    "reqs_rank_1h": 850,
-    "cache_ratio_1h": 0.18918327987194,
-    "ips_rank_1h": 662,
-    "ips_quantile_1h": 0.99926590919495
-  },
-  "jaSignalsParsed": {
-    "ratios": {
-      "h2h3_ratio_1h": 0.98826485872269,
-      "heuristic_ratio_1h": 7.288895722013e-05,
-      "browser_ratio_1h": 0.93640440702438,
-      "cache_ratio_1h": 0.18918327987194
-    },
-    "ranks": {
-      "uas_rank_1h": 901,
-      "paths_rank_1h": 655,
-      "reqs_rank_1h": 850,
-      "ips_rank_1h": 662
-    },
-    "quantiles": {
-      "reqs_quantile_1h": 0.99905741214752,
-      "ips_quantile_1h": 0.99926590919495
-    }
-  }
+	"ja4Signals": {
+		"h2h3_ratio_1h": 0.98826485872269,
+		"heuristic_ratio_1h": 7.288895722013e-5,
+		"reqs_quantile_1h": 0.99905741214752,
+		"uas_rank_1h": 901,
+		"browser_ratio_1h": 0.93640440702438,
+		"paths_rank_1h": 655,
+		"reqs_rank_1h": 850,
+		"cache_ratio_1h": 0.18918327987194,
+		"ips_rank_1h": 662,
+		"ips_quantile_1h": 0.99926590919495
+	},
+	"jaSignalsParsed": {
+		"ratios": {
+			"h2h3_ratio_1h": 0.98826485872269,
+			"heuristic_ratio_1h": 7.288895722013e-5,
+			"browser_ratio_1h": 0.93640440702438,
+			"cache_ratio_1h": 0.18918327987194
+		},
+		"ranks": {
+			"uas_rank_1h": 901,
+			"paths_rank_1h": 655,
+			"reqs_rank_1h": 850,
+			"ips_rank_1h": 662
+		},
+		"quantiles": {
+			"reqs_quantile_1h": 0.99905741214752,
+			"ips_quantile_1h": 0.99926590919495
+		}
+	}
 }
-
 ```
 
 When JA4 Signals are missing, the output appears as follows:
 
 ```json output title="Missing JA4 signals output"
 {
-  "ja4Signals": {},
-  "jaSignalsParsed": {
-    "ratios": {},
-    "ranks": {},
-    "quantiles": {}
-  }
+	"ja4Signals": {},
+	"jaSignalsParsed": {
+		"ratios": {},
+		"ranks": {},
+		"quantiles": {}
+	}
 }
 ```
 
 :::note
 
-This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/). 
+This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/).
 :::
 
 <Render file="ja3-ja4-null" product="bots" />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
index 2a86d9d70cbc989..23baf713cc11a7c 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Bot Management customers can view aggregate intelligence data for each [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/) based on traffic across the Cloudflare network. Use this data to understand why a request received a specific bot score or to feed into your own machine learning models running in [Cloudflare Workers](/workers/) or at your origin.
 
diff --git a/src/content/docs/bots/additional-configurations/javascript-detections.mdx b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
index 69e80bc8893eef4..e3c29b9383911ff 100644
--- a/src/content/docs/bots/additional-configurations/javascript-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
@@ -7,4 +7,4 @@ products:
 external_link: /cloudflare-challenges/challenge-types/javascript-detections/
 sidebar:
   order: 3
----
\ No newline at end of file
+---
diff --git a/src/content/docs/bots/concepts/bot-tags.mdx b/src/content/docs/bots/concepts/bot-tags.mdx
index ce7772981cc0afe..f498c1ebd7862df 100644
--- a/src/content/docs/bots/concepts/bot-tags.mdx
+++ b/src/content/docs/bots/concepts/bot-tags.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 3
-
 ---
 
-import { Render, GlossaryTooltip } from "~/components"
+import { Render, GlossaryTooltip } from "~/components";
 
 <GlossaryTooltip term="bot tags">Bot tags</GlossaryTooltip> provide more detail about *why* Cloudflare assigned a <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/">bot score</GlossaryTooltip> to a request.
 
diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx
index 79b102ed14105a3..8135d2506798f9c 100644
--- a/src/content/docs/bots/concepts/bot/index.mdx
+++ b/src/content/docs/bots/concepts/bot/index.mdx
@@ -29,7 +29,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni
 <Render file="verified-bots" product="bots" />
 
 :::note
-The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability). 
+The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability).
 :::
 
 ## AI bots
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
index 79b4ca637337d88..51b8af2d0e34705 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
@@ -9,7 +9,6 @@ sidebar:
 learning_center:
   title: What is a bot?
   link: https://www.cloudflare.com/learning/bots/what-is-a-bot/
-
 ---
 
 A signed agent is a bot controlled by an end user and verified through [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) cryptographic signatures.
@@ -33,4 +32,4 @@ Once Cloudflare approves a signed agent, it should appear on [Cloudflare Radar's
 
 ## Verification method
 
-The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
\ No newline at end of file
+The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
index 4b3a2e13bca22e5..7012c9a37f3a779 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
@@ -5,9 +5,8 @@ description: Requirements an agent must meet to be listed as a Cloudflare signed
 products:
   - bots
 sidebar:
-    order: 3
-    label: Policy
-
+  order: 3
+  label: Policy
 ---
 
 In order to be listed by Cloudflare as a signed agent, your agent must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
@@ -64,4 +63,4 @@ If any of the requirements to validate are breached, a service will be removed f
 The following are examples of breaches of policy:
 
 - The service has vulnerabilities that have not been patched.
-- The disclosed purpose of the service does not reflect on the traffic.
\ No newline at end of file
+- The disclosed purpose of the service does not reflect on the traffic.
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
index 0a353f6982931b7..35f535378a55bd9 100644
--- a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
@@ -5,12 +5,11 @@ description: Requirements a bot must meet to be listed as a Cloudflare verified
 products:
   - bots
 sidebar:
-    order: 5
-    label: Policy
-
+  order: 5
+  label: Policy
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
 
diff --git a/src/content/docs/bots/concepts/index.mdx b/src/content/docs/bots/concepts/index.mdx
index 24071d2b6d12abd..6c7d7f72e402af2 100644
--- a/src/content/docs/bots/concepts/index.mdx
+++ b/src/content/docs/bots/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on bot concepts:
 
diff --git a/src/content/docs/bots/get-started/index.mdx b/src/content/docs/bots/get-started/index.mdx
index 4082e3406e6058c..e3dd198f6f0fb99 100644
--- a/src/content/docs/bots/get-started/index.mdx
+++ b/src/content/docs/bots/get-started/index.mdx
@@ -12,10 +12,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with Cloudflare bot solutions
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to get started with Cloudflare's bot solutions based on your plan type:
 
diff --git a/src/content/docs/bots/glossary.mdx b/src/content/docs/bots/glossary.mdx
index 0fbbfcdccbc2f94..51cd6fdaf56a98f 100644
--- a/src/content/docs/bots/glossary.mdx
+++ b/src/content/docs/bots/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 10
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Bots documentation.
 
diff --git a/src/content/docs/bots/plans/bm-subscription.mdx b/src/content/docs/bots/plans/bm-subscription.mdx
index 3d5517526b98383..c0946617758e924 100644
--- a/src/content/docs/bots/plans/bm-subscription.mdx
+++ b/src/content/docs/bots/plans/bm-subscription.mdx
@@ -105,17 +105,17 @@ Zones that have [Enterprise Bot Management](/bots/get-started/bot-management/) e
 
 Bot Management customers have both bot settings (configured in **Security Settings**) and the ability to create custom rules using bot score fields. Start with the bot settings for baseline protection, then add custom rules only when you need additional control.
 
-| Feature | Handled by bot settings | When to use custom rules instead |
-| --- | --- | --- |
-| Block or challenge definitely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
-| Block or challenge likely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
-| Allow or block verified bots | No | Granular control by verified bot category |
-| Block AI crawlers | Yes | Target individual AI crawlers using detection IDs |
-| Protect static resources | No | Exclude static resources from specific rules |
-| Optimize for WordPress | No | No |
-| Forward bot data to origin | No | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/) |
-| Detection ID targeting | No | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/) |
-| JA3/JA4 fingerprint rules | No | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
+| Feature                                         | Handled by bot settings | When to use custom rules instead                                                                  |
+| ----------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
+| Block or challenge definitely automated traffic | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
+| Block or challenge likely automated traffic     | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
+| Allow or block verified bots                    | No                      | Granular control by verified bot category                                                         |
+| Block AI crawlers                               | Yes                     | Target individual AI crawlers using detection IDs                                                 |
+| Protect static resources                        | No                      | Exclude static resources from specific rules                                                      |
+| Optimize for WordPress                          | No                      | No                                                                                                |
+| Forward bot data to origin                      | No                      | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/)                          |
+| Detection ID targeting                          | No                      | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/)                       |
+| JA3/JA4 fingerprint rules                       | No                      | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
 
 For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
 
diff --git a/src/content/docs/bots/reference/alerts.mdx b/src/content/docs/bots/reference/alerts.mdx
index 76c74e5d486644c..039399e05dda310 100644
--- a/src/content/docs/bots/reference/alerts.mdx
+++ b/src/content/docs/bots/reference/alerts.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 4
-
 ---
 
-import { AvailableNotifications, Steps, DashButton } from "~/components"
+import { AvailableNotifications, Steps, DashButton } from "~/components";
 
 Bot alerts inform you when Cloudflare detects spikes in your traffic with any of the following characteristics:
 
@@ -17,7 +16,7 @@ Bot alerts inform you when Cloudflare detects spikes in your traffic with any of
 - An increase in traffic on available dimensions in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 - Filters of your choosing in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 
---- 
+---
 
 ## Alert types
 
@@ -73,5 +72,5 @@ You can also choose to group by the following dimensions so that they can be ale
 - Bot Detection IDs
 
 :::note
-Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/). 
-:::
\ No newline at end of file
+Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/).
+:::
diff --git a/src/content/docs/bots/reference/bot-management-variables.mdx b/src/content/docs/bots/reference/bot-management-variables.mdx
index 8b78f19b39ba24e..388e76e2a3c7d80 100644
--- a/src/content/docs/bots/reference/bot-management-variables.mdx
+++ b/src/content/docs/bots/reference/bot-management-variables.mdx
@@ -6,21 +6,21 @@ products:
   - bots
 sidebar:
   order: 2
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Ruleset Engine fields
 
 Bot Management provides access to several [new variables](/ruleset-engine/rules-language/fields/reference/?field-category=Bots) within the expression builder of Ruleset Engine-based products such as [WAF custom rules](/waf/custom-rules/).
 
 - **Bot Score** (`cf.bot_management.score`): An integer between 1-99 that indicates [Cloudflare's level of certainty](/bots/concepts/bot-score/) that a request comes from a bot.
-- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot. 
-  
-  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service. 
-  
+- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot.
+
+  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service.
+
   We also use additional validation methods, including checking ASN blocks and public lists. If these methods are unavailable, Cloudflare utilizes internal data and machine learning to identify and verify legitimate IP addresses from good bots. Most customers choose to [allow this traffic](/ruleset-engine/rules-language/fields/reference/cf.bot_management.verified_bot/).
+
 - **Serves Static Resource** (`cf.bot_management.static_resource`): An identifier that matches [file extensions](/bots/additional-configurations/static-resources/) for many types of static resources. Use this variable if you send emails that retrieve static images.
 - **ja3Hash** (`cf.bot_management.ja3_hash`) and **ja4** (`cf.bot_management.ja4`): A [**JA3/JA4 fingerprint**](/bots/additional-configurations/ja3-ja4-fingerprint/) helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
 - **Bot Detection IDs** (`cf.bot_management.detection_ids`): List of IDs that correlate to the Bot Management heuristic detections made on a request (you can have multiple heuristic detections on the same request).
diff --git a/src/content/docs/bots/reference/bot-verification/index.mdx b/src/content/docs/bots/reference/bot-verification/index.mdx
index c074fd2973d2c84..ea311232d0c71de 100644
--- a/src/content/docs/bots/reference/bot-verification/index.mdx
+++ b/src/content/docs/bots/reference/bot-verification/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 1
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's validation methods for [Verified](/bots/concepts/bot/verified-bots/) and [Signed](/bots/concepts/bot/signed-agents/) bots.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
index 9d65f3cb32d07cf..e21b0eabee315f3 100644
--- a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
+++ b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
@@ -5,12 +5,11 @@ description: Verify bot identity by matching request IP addresses against publis
 products:
   - bots
 sidebar:
-    order: 3
-    label: IP validation
-
+  order: 3
+  label: IP validation
 ---
 
-import { GlossaryTooltip, Steps } from "~/components"
+import { GlossaryTooltip, Steps } from "~/components";
 
 The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. IP validation is only used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/).
 
@@ -57,4 +56,4 @@ Generic user-agents include:
 - `node-fetch`
 - `okhttp`
 - `python-requests`
-- `uTorrent`
\ No newline at end of file
+- `uTorrent`
diff --git a/src/content/docs/bots/reference/index.mdx b/src/content/docs/bots/reference/index.mdx
index d98d7d7b81bce95..f157689e81141cc 100644
--- a/src/content/docs/bots/reference/index.mdx
+++ b/src/content/docs/bots/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's bot solutions:
 
diff --git a/src/content/docs/bots/reference/machine-learning-models.mdx b/src/content/docs/bots/reference/machine-learning-models.mdx
index 49af33d0da4309d..bdaac08a260b29c 100644
--- a/src/content/docs/bots/reference/machine-learning-models.mdx
+++ b/src/content/docs/bots/reference/machine-learning-models.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
 tags:
   - AI
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Enable auto-updates to the Machine Learning models
 
@@ -39,4 +38,4 @@ By not updating to the latest version, you will be using a Machine Learning mode
 | v6      | Significantly improved scoring for native Android application traffic. <br/><br/>Improved scoring on the newest versions of Chromium browsers.                                                                                              | Q1 2022     |
 | v7      | Increased recognition of distributed botnets. <br/><br/>Improved HTTP/3 scoring.                                                                                                                                                            | Q1 2024     |
 | v8      | Improved detection of residential proxies. <br/><br/>Increased weight on network level traffic characteristics.                                                                                                                             | Q2 2024     |
-| v9      | Improved model consistency and model efficacy against randomization attack techniques | Q2 2025     |
+| v9      | Improved model consistency and model efficacy against randomization attack techniques                                                                                                                                                       | Q2 2025     |
diff --git a/src/content/docs/bots/reference/sample-terms.mdx b/src/content/docs/bots/reference/sample-terms.mdx
index 3c05cc2e80dd3e8..2ba93ce64ee1935 100644
--- a/src/content/docs/bots/reference/sample-terms.mdx
+++ b/src/content/docs/bots/reference/sample-terms.mdx
@@ -8,7 +8,6 @@ sidebar:
   order: 5
 tags:
   - AI
-
 ---
 
 Cloudflare recommends that customers consider updating their Terms of Service to address bots specifically related to Artificial Intelligence (AI) training and data scraping. The text below provides an informational example of the kind of language that could be added to a website's terms of use.
@@ -19,8 +18,7 @@ Cloudflare recommends that customers consider updating their Terms of Service to
 
 :::caution[Disclaimer]
 
-This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome. 
+This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome.
 
-This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file. 
+This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file.
 :::
-
diff --git a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
index 363aa1c84d09636..b8453361111ca0c 100644
--- a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
+++ b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
@@ -6,10 +6,9 @@ products:
   - bots
 sidebar:
   order: 1
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/additional-configurations/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
 
diff --git a/src/content/docs/bots/troubleshooting/false-positives.mdx b/src/content/docs/bots/troubleshooting/false-positives.mdx
index 377e7ac13199bff..7d7dadcae903c10 100644
--- a/src/content/docs/bots/troubleshooting/false-positives.mdx
+++ b/src/content/docs/bots/troubleshooting/false-positives.mdx
@@ -7,7 +7,6 @@ products:
 sidebar:
   order: 3
   label: False positives
-
 ---
 
 import { Render } from "~/components";
@@ -25,4 +24,4 @@ You cannot bypass or skip Bot Fight Mode using the _Skip_ action in WAF custom r
 
 Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.
 
-If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
\ No newline at end of file
+If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
diff --git a/src/content/docs/bots/troubleshooting/index.mdx b/src/content/docs/bots/troubleshooting/index.mdx
index b1e6d5b78a345c4..821d9ed42c52b76 100644
--- a/src/content/docs/bots/troubleshooting/index.mdx
+++ b/src/content/docs/bots/troubleshooting/index.mdx
@@ -12,12 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot issues with Bots
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to troubleshoot issues with Cloudflare's bot solutions:
 
 <DirectoryListing />
-
diff --git a/src/content/docs/bots/workers-templates/index.mdx b/src/content/docs/bots/workers-templates/index.mdx
index aae030a3a8b29b2..6bf57e8cbfb768f 100644
--- a/src/content/docs/bots/workers-templates/index.mdx
+++ b/src/content/docs/bots/workers-templates/index.mdx
@@ -12,10 +12,9 @@ sidebar:
 head:
   - tag: title
     content: Workers templates
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the templates below to integrate Bot Management with [Cloudflare Workers](/workers/):
 
diff --git a/src/content/docs/browser-run/features/index.mdx b/src/content/docs/browser-run/features/index.mdx
index 6ef34df2029deea..8f79040189134a4 100644
--- a/src/content/docs/browser-run/features/index.mdx
+++ b/src/content/docs/browser-run/features/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/browser-run/how-to/deploy-worker.mdx b/src/content/docs/browser-run/how-to/deploy-worker.mdx
index 808b712441c47df..d15deee8a1e1894 100644
--- a/src/content/docs/browser-run/how-to/deploy-worker.mdx
+++ b/src/content/docs/browser-run/how-to/deploy-worker.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 1
 products:
   - browser-run
-  - workers 
+  - workers
 ---
 
 import {
diff --git a/src/content/docs/browser-run/mcp-server.mdx b/src/content/docs/browser-run/mcp-server.mdx
index 3d7ba05eaeadd22..a79dc14dcabbbb1 100644
--- a/src/content/docs/browser-run/mcp-server.mdx
+++ b/src/content/docs/browser-run/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - browser-run
----
\ No newline at end of file
+---
diff --git a/src/content/docs/browser-run/quick-actions/api-reference.mdx b/src/content/docs/browser-run/quick-actions/api-reference.mdx
index 15e3e787ca1f282..dc44d9a5ba8d2e4 100644
--- a/src/content/docs/browser-run/quick-actions/api-reference.mdx
+++ b/src/content/docs/browser-run/quick-actions/api-reference.mdx
@@ -4,7 +4,7 @@ title: Reference
 description: View the complete Browser Run Quick Actions API reference for all available endpoints and parameters.
 external_link: /api/resources/browser_rendering/
 sidebar:
- order: 15
+  order: 15
 products:
   - browser-run
 ---
diff --git a/src/content/docs/browser-run/reference/browser-close-reasons.mdx b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
index 3fe11accbc5a78a..cfb411b73a356c1 100644
--- a/src/content/docs/browser-run/reference/browser-close-reasons.mdx
+++ b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
@@ -24,13 +24,13 @@ Browser Run sessions are billed based on [usage](/browser-run/pricing/). We do n
 
 ## Close reasons
 
-| Reason | Description |
-| --- | --- |
-| **Normal closure** | Your code called `browser.close()` and the session ended normally. No action needed. |
-| **Browser idle** | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
-| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks. |
-| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block. |
-| **Session evicted** | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic. |
+| Reason               | Description                                                                                                                                                                                                                                                                        |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Normal closure**   | Your code called `browser.close()` and the session ended normally. No action needed.                                                                                                                                                                                               |
+| **Browser idle**     | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
+| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks.                               |
+| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block.                                                    |
+| **Session evicted**  | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic.                                                                            |
 
 ## Handling unexpected closures
 
@@ -38,18 +38,18 @@ Sessions can close at any time due to infrastructure events, network issues, or
 
 ```js
 async function runBrowser(env) {
-  let browser;
-  try {
-    browser = await puppeteer.launch(env.MYBROWSER);
-    const page = await browser.newPage();
-    await page.goto("https://example.com");
-    // Your browser automation logic
-  } catch (error) {
-    console.error("Browser session ended unexpectedly:", error.message);
-    // Retry or return an error response
-  } finally {
-    await browser?.close();
-  }
+	let browser;
+	try {
+		browser = await puppeteer.launch(env.MYBROWSER);
+		const page = await browser.newPage();
+		await page.goto("https://example.com");
+		// Your browser automation logic
+	} catch (error) {
+		console.error("Browser session ended unexpectedly:", error.message);
+		// Retry or return an error response
+	} finally {
+		await browser?.close();
+	}
 }
 ```
 
@@ -57,13 +57,13 @@ For long-running or critical workflows, consider adding retry logic:
 
 ```js
 async function runWithRetry(env, maxRetries = 3) {
-  for (let attempt = 1; attempt <= maxRetries; attempt++) {
-    try {
-      return await runBrowser(env);
-    } catch (error) {
-      if (attempt === maxRetries) throw error;
-      console.log(`Attempt ${attempt} failed, retrying...`);
-    }
-  }
+	for (let attempt = 1; attempt <= maxRetries; attempt++) {
+		try {
+			return await runBrowser(env);
+		} catch (error) {
+			if (attempt === maxRetries) throw error;
+			console.log(`Attempt ${attempt} failed, retrying...`);
+		}
+	}
 }
 ```
diff --git a/src/content/docs/byoip/address-maps/setup.mdx b/src/content/docs/byoip/address-maps/setup.mdx
index 9e80f9aa794cc37..4ded8d833123a77 100644
--- a/src/content/docs/byoip/address-maps/setup.mdx
+++ b/src/content/docs/byoip/address-maps/setup.mdx
@@ -11,7 +11,13 @@ sidebar:
   label: Setup
 ---
 
-import { GlossaryTooltip, APIRequest, DashButton, Tabs, TabItem } from "~/components";
+import {
+	GlossaryTooltip,
+	APIRequest,
+	DashButton,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 Consider the sections below to learn how to set up address maps.
 
@@ -120,13 +126,13 @@ Default SNI for Spectrum can only be created via API using the [Create Address M
 Do not include any membership in your command. Your API command should resemble the following:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/address_maps"
-  method="POST"
-  json={{
-		"description": "default_sni",
-		"default_sni": "sni.example.com",
-		"enabled": false,
-		"ips": ["192.0.0.1"],
-		"memberships": [],
+	path="/accounts/{account_id}/addressing/address_maps"
+	method="POST"
+	json={{
+		description: "default_sni",
+		default_sni: "sni.example.com",
+		enabled: false,
+		ips: ["192.0.0.1"],
+		memberships: [],
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/byoip/changelog.mdx b/src/content/docs/byoip/changelog.mdx
index 389731c7bfc427f..bee100a7b07c3bc 100644
--- a/src/content/docs/byoip/changelog.mdx
+++ b/src/content/docs/byoip/changelog.mdx
@@ -14,4 +14,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/byoip.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductReleaseNotes />
\ No newline at end of file
+<ProductReleaseNotes />
diff --git a/src/content/docs/byoip/concepts/index.mdx b/src/content/docs/byoip/concepts/index.mdx
index 646653a0d44f0e6..7a7f4b5b8de1b6d 100644
--- a/src/content/docs/byoip/concepts/index.mdx
+++ b/src/content/docs/byoip/concepts/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the topics below for more information about concepts related to BYOIP.
 
diff --git a/src/content/docs/byoip/concepts/prefix-delegations.mdx b/src/content/docs/byoip/concepts/prefix-delegations.mdx
index 65ddd820ea83124..2c7fa214ed734aa 100644
--- a/src/content/docs/byoip/concepts/prefix-delegations.mdx
+++ b/src/content/docs/byoip/concepts/prefix-delegations.mdx
@@ -10,7 +10,6 @@ sidebar:
 
 Prefix delegations allow a prefix owner (Account A) to grant another Cloudflare account (Account B) permission to use all or part of their BYOIP prefix. The original prefix remains managed by Account A, but Account B can use the delegated IPs with CDN services (including Cloudflare for SaaS) or Spectrum. Refer to [service bindings](/byoip/service-bindings/) for more information on the services an IP can be bound to.
 
-
 ## CDN
 
 CDN delegations allow you to use the IP(s) with [Address Maps](/byoip/address-maps/) or [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) customers.
diff --git a/src/content/docs/byoip/glossary.mdx b/src/content/docs/byoip/glossary.mdx
index 8b3f72c3e98e200..21eb58070060e3a 100644
--- a/src/content/docs/byoip/glossary.mdx
+++ b/src/content/docs/byoip/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 12
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's BYOIP documentation.
 
diff --git a/src/content/docs/byoip/route-leak-detection.mdx b/src/content/docs/byoip/route-leak-detection.mdx
index 7b25fea18deee8c..b42d00458f0abed 100644
--- a/src/content/docs/byoip/route-leak-detection.mdx
+++ b/src/content/docs/byoip/route-leak-detection.mdx
@@ -6,10 +6,9 @@ products:
   - byoip
 sidebar:
   order: 8
-
 ---
 
-import { AvailableNotifications, DashButton } from "~/components"
+import { AvailableNotifications, DashButton } from "~/components";
 
 Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
 
diff --git a/src/content/docs/byoip/service-bindings/index.mdx b/src/content/docs/byoip/service-bindings/index.mdx
index 0078224d0428db2..51ae83d822bc673 100644
--- a/src/content/docs/byoip/service-bindings/index.mdx
+++ b/src/content/docs/byoip/service-bindings/index.mdx
@@ -79,4 +79,5 @@ When adding a service binding for a given IP address, it must be either a CDN se
 <DirectoryListing />
 
 [^1]: Layer 7 HTTP-based
-[^2]: Layer 4 or Layer 7 HTTP with custom ports
\ No newline at end of file
+
+[^2]: Layer 4 or Layer 7 HTTP with custom ports
diff --git a/src/content/docs/byoip/troubleshooting/index.mdx b/src/content/docs/byoip/troubleshooting/index.mdx
index c3c66603d15744f..b83821670151137 100644
--- a/src/content/docs/byoip/troubleshooting/index.mdx
+++ b/src/content/docs/byoip/troubleshooting/index.mdx
@@ -36,13 +36,12 @@ Instead, you can use Address Maps to set a default SNI for IPs on your account o
 
 When onboarding BYOIP prefixes via the API, you may encounter the following errors:
 
-| Error code | Meaning | Resolution |
-|---|---|---|
+| Error code                      | Meaning                                                                                                     | Resolution                                                                                                                                                                                                                                                                             |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `prefix_not_valid_and_approved` | The prefix has not passed IRR validation, RPKI validation, and ownership verification (or manual approval). | Verify all three validation steps have completed. If one or more are failing, check prefix registration with your Regional Internet Registry (RIR) and your RPKI ROA configuration. If validation is passing but you are still seeing this error, contact support for manual approval. |
-| `incomplete_bgp_deployment` | Cannot create a BGP prefix without a default edge service binding configured. | Configure a default edge service binding before creating BGP prefixes. |
-| `advertise_state_locked` | Cannot create a BGP prefix — the default edge service binding is still deploying. | Wait for the edge service binding deployment to complete, then retry. |
+| `incomplete_bgp_deployment`     | Cannot create a BGP prefix without a default edge service binding configured.                               | Configure a default edge service binding before creating BGP prefixes.                                                                                                                                                                                                                 |
+| `advertise_state_locked`        | Cannot create a BGP prefix — the default edge service binding is still deploying.                           | Wait for the edge service binding deployment to complete, then retry.                                                                                                                                                                                                                  |
 
 :::note
 Self-serve BYOIP onboarding is not supported when BYOIP is used as a Magic Transit on-ramp configuration. For more information, refer to [Magic Transit with CDN](/byoip/service-bindings/magic-transit-with-cdn/).
 :::
-
diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
index 5bd9e4060218ead..4e48745c1d36d41 100644
--- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
+++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
@@ -105,10 +105,7 @@ For example:
 
 ### Operations
 
-<Render
-  file="cache-reserve-operations"
-  product="cache"
-/>
+<Render file="cache-reserve-operations" product="cache" />
 
 ## Cache Reserve billing examples
 
@@ -152,10 +149,10 @@ Cache Reserve is designed for use with [Tiered Cache](/cache/how-to/tiered-cache
 ## Cache Reserve Analytics
 
 <Render
-  file="cache-reserve-analytics"
+	file="cache-reserve-analytics"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
diff --git a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
index 22a7ef8c9ba65a7..e94802d8e09921e 100644
--- a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
@@ -4,10 +4,9 @@ description: Signal search engine crawlers when content changes with IndexNow.
 products:
   - cache
 title: Crawler Hints
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Crawler Hints uses Cloudflare cache signals to tell search engines when your content has likely changed, so they crawl your site at the right time instead of guessing.
 
@@ -41,6 +40,6 @@ After enabling Crawler Hints, Cloudflare will begin sending hints to search engi
 
 When enabled, Crawler Hints is a global setting for your entire website. You can stop a specific page from being indexed by either:
 
-* Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
-* Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
-* Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
+- Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
+- Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
+- Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
diff --git a/src/content/docs/cache/advanced-configuration/early-hints.mdx b/src/content/docs/cache/advanced-configuration/early-hints.mdx
index 0dbc92752839ea9..cc491452932a8a8 100644
--- a/src/content/docs/cache/advanced-configuration/early-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/early-hints.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Preload assets with 103 Early Hints to speed up page loads.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 When a browser requests a page, the origin server takes time to prepare the full response. Early Hints uses this wait time to send the browser a preliminary `103` response containing `Link` headers that tell the browser which assets it will need. The browser can start loading those assets before the full response arrives, which speeds up page loads.
 
@@ -15,10 +14,8 @@ Early Hints is defined in [RFC 8297](https://httpwg.org/specs/rfc8297.html) as a
 
 :::note[Note]
 
-
 Early Hints is currently only supported over HTTP/2 and HTTP/3.
 
-
 :::
 
 For more information about Early Hints, refer to the [Cloudflare](https://blog.cloudflare.com/early-hints) and [Google Chrome](https://developer.chrome.com/en/blog/early-hints/) blogs.
@@ -40,16 +37,14 @@ For more information about Early Hints, refer to the [Cloudflare](https://blog.c
 
 Early Hints are only generated and cached:
 
-* For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
-* On 200, 301, or 302 response return codes
-* When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
+- For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
+- On 200, 301, or 302 response return codes
+- When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
 
 :::note
 
-
 Early Hints cache entries are keyed by request URI and ignore query strings.
 
-
 :::
 
 ## Emit Early Hints
@@ -60,7 +55,7 @@ Currently, only certain browser versions will take action to preload or preconne
 
 Additionally, keep the following in mind:
 
-* Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
-* Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
-* Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
-* You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
+- Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
+- Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
+- Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
+- You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
diff --git a/src/content/docs/cache/advanced-configuration/index.mdx b/src/content/docs/cache/advanced-configuration/index.mdx
index 9efd5cc15381ed7..12fa7c03f59e222 100644
--- a/src/content/docs/cache/advanced-configuration/index.mdx
+++ b/src/content/docs/cache/advanced-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
index 0b41b69eb776303..05e6363b11a6dad 100644
--- a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
+++ b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
@@ -9,14 +9,14 @@ tags:
   - WordPress
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 **Query String Sort** increases cache-hit rates by first sorting query strings into a consistent order before checking the Cloudflare cache.
 
 By default, Cloudflare’s cache treats resources as distinct if their URL query strings are in a different order. For instance, these resources are cached separately:
 
-* `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
-* `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
+- `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
+- `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
 
 Query String Sort changes this behavior. If two query strings exist with the same name, the URL is sorted by the parameter value. For example:
 
@@ -30,7 +30,7 @@ would be sorted to:
 
 <FeatureTable id="cache.query_string_sort" />
 
-***
+---
 
 ## Enable Query String Sort
 
@@ -41,7 +41,7 @@ To enable Query String Sort:
 3. Go to **Caching** > **Configuration**.
 4. For **Enable Query String Sort**, switch the toggle to **On**.
 
-***
+---
 
 ## Unexpected behavior with WordPress admin pages
 
@@ -49,19 +49,17 @@ When a site or an application requires exact query string ordering, enabling Que
 
 For example in the WordPress admin UI, you might notice any of the following behaviors:
 
-* No media appear in the Media Library
-* Inability to customize the site via **Appearance** > **Customize**
-* Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
-* Inability to edit menus in **Appearance** > **Menus**
+- No media appear in the Media Library
+- Inability to customize the site via **Appearance** > **Customize**
+- Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
+- Inability to edit menus in **Appearance** > **Menus**
 
 To understand why this happens, note that WordPress [concatenates JavaScript files](https://developer.wordpress.org/advanced-administration/wordpress/wp-config/#disable-javascript-concatenation) to speed up the administration interface. The way WordPress implements this involves multiple occurrences of `load[]` parameters in the query string, where the order of those parameters is crucial.
 
 :::note
 
-
 Note that more recent versions of WordPress may not experience this issue, as a patch has been implemented in WordPress since 2019. The patch can be found at [WordPress Core Trac Changeset 45456](https://core.trac.wordpress.org/changeset/45456).
 
-
 :::
 
 ### Identify the problem
@@ -100,15 +98,15 @@ For example, you might have an image resizing endpoint or a search form, where t
 
 To minimize problems, consider:
 
-* Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
-* Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
-* Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
+- Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
+- Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
+- Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
 
 To learn more about Cache Rules, visit [Cache Rules](/cache/how-to/cache-rules/).
 
-***
+---
 
 ## Related resources
 
-* [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
-* [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
+- [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
+- [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
diff --git a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
index 8d6b138d7f117d2..4f0f14a99828213 100644
--- a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
+++ b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
@@ -42,8 +42,8 @@ In this example, you run an e-commerce site and want to display prices in the lo
    - **Operator:** `equals`
    - **Value:** `Canada`
 6. Under **Then...**
-    - for **Path**, select **Preserve**.
-    - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
+   - for **Path**, select **Preserve**.
+   - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
 7. Select **Save**.
 
 Now, requests from Canada to `/products/item` will be transformed to `/products/item?loc=ca` before reaching your origin or the cache, creating a distinct cache entry.
@@ -65,14 +65,14 @@ To enable this feature, create a _variants rule_ using the API. This rule maps f
 For example, the following API call tells Cloudflare that for `.jpeg` and `.jpg` files, your origin can serve `image/webp` and `image/avif` variants:
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp", "image/avif"],
-      jpg: ["image/webp", "image/avif"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp", "image/avif"],
+			jpg: ["image/webp", "image/avif"],
+		},
+	}}
 />
 
 After creating the rule, Cloudflare will create distinct cache entries for each image variant, improving performance for users with modern browsers.
@@ -100,26 +100,27 @@ In this example, you run an A/B test controlled by a cookie named `ab-test` (wit
 const CACHE_DURATION = 30 * 24 * 60 * 60; // 30 days
 
 export default {
-  async fetch(request) {
-    // Construct a new URL for the cache key based on the A/B cookie
-    const abCookie = request.headers.get('Cookie')?.match(/ab-test=([^;]+)/)?.[1] || 'control';
-    const url = new URL(request.url);
-    url.pathname = `/ab-test/${abCookie}${url.pathname}`;
-
-    const cacheKey = new Request(url, request);
-    const cache = caches.default;
-
-    let response = await cache.match(cacheKey);
-    if (!response) {
-      // If not in cache, fetch from origin
-      response = await fetch(request);
-      response = new Response(response.body, response);
-      response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
-      // Put the response into cache with the custom key
-      await cache.put(cacheKey, response.clone());
-    }
-    return response;
-  },
+	async fetch(request) {
+		// Construct a new URL for the cache key based on the A/B cookie
+		const abCookie =
+			request.headers.get("Cookie")?.match(/ab-test=([^;]+)/)?.[1] || "control";
+		const url = new URL(request.url);
+		url.pathname = `/ab-test/${abCookie}${url.pathname}`;
+
+		const cacheKey = new Request(url, request);
+		const cache = caches.default;
+
+		let response = await cache.match(cacheKey);
+		if (!response) {
+			// If not in cache, fetch from origin
+			response = await fetch(request);
+			response = new Response(response.body, response);
+			response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
+			// Put the response into cache with the custom key
+			await cache.put(cacheKey, response.clone());
+		}
+		return response;
+	},
 };
 ```
 
@@ -151,13 +152,13 @@ If your origin serves different content types (for example, `application/json` v
    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
-3. Enter  rule name, such as `Vary by Accept Header`.
+3. Enter rule name, such as `Vary by Accept Header`.
 4. Set the condition for the rule to apply (for example, a specific hostname or path).
 5. Under **Cache key**, select **Use custom key**.
 6. Select **Add new**.
-    - **Type**: `Header`
-    - **Name**: `Accept`
-    - **Value**: Add each `value`, or leave empty for all.
+   - **Type**: `Header`
+   - **Name**: `Accept`
+   - **Value**: Add each `value`, or leave empty for all.
 7. Select **Deploy**.
 
 This configuration creates separate cache entries based on the `Accept` header value, respecting your API's content negotiation.
@@ -176,28 +177,28 @@ This Worker detects whether a visitor is on a mobile or desktop device and creat
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    const userAgent = request.headers.get('User-Agent') || '';
-    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
+	async fetch(request, env, ctx) {
+		const userAgent = request.headers.get("User-Agent") || "";
+		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
 
-    // Create a new URL for the cache key that includes the device type
-    const url = new URL(request.url);
-    url.pathname = `/${deviceType}${url.pathname}`;
+		// Create a new URL for the cache key that includes the device type
+		const url = new URL(request.url);
+		url.pathname = `/${deviceType}${url.pathname}`;
 
-    const cacheKey = new Request(url, request);
-    const cache = caches.default;
+		const cacheKey = new Request(url, request);
+		const cache = caches.default;
 
-    let response = await cache.match(cacheKey);
+		let response = await cache.match(cacheKey);
 
-    if (!response) {
-      console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
-      response = await fetch(request);
-      let responseToCache = response.clone();
-      ctx.waitUntil(cache.put(cacheKey, responseToCache));
-    }
+		if (!response) {
+			console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
+			response = await fetch(request);
+			let responseToCache = response.clone();
+			ctx.waitUntil(cache.put(cacheKey, responseToCache));
+		}
 
-    return response;
-  },
+		return response;
+	},
 };
 ```
 
@@ -211,28 +212,28 @@ This Worker detects if a visitor is on a mobile device or a desktop and creates
 
 ```js
 export default {
-  async fetch(request) {
-    // 1. Determine the device type from the User-Agent header
-    const userAgent = request.headers.get('User-Agent') || '';
-    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
-
-    // 2. Create a custom cache key by appending the device type to the URL
-    const customCacheKey = `${request.url}-${deviceType}`;
-
-    // 3. Fetch the response. Cloudflare's cache automatically uses the
-    //    customCacheKey for cache operations (match, put).
-    const response = await fetch(request, {
-      cf: {
-        cacheKey: customCacheKey,
-      },
-    });
-
-    // Optionally, you can modify the response before returning it
-    // For example, add a header to indicate which cache key was used
-    const newResponse = new Response(response.body, response);
-    newResponse.headers.set("X-Cache-Key", customCacheKey);
-    return newResponse;
-  },
+	async fetch(request) {
+		// 1. Determine the device type from the User-Agent header
+		const userAgent = request.headers.get("User-Agent") || "";
+		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
+
+		// 2. Create a custom cache key by appending the device type to the URL
+		const customCacheKey = `${request.url}-${deviceType}`;
+
+		// 3. Fetch the response. Cloudflare's cache automatically uses the
+		//    customCacheKey for cache operations (match, put).
+		const response = await fetch(request, {
+			cf: {
+				cacheKey: customCacheKey,
+			},
+		});
+
+		// Optionally, you can modify the response before returning it
+		// For example, add a header to indicate which cache key was used
+		const newResponse = new Response(response.body, response);
+		newResponse.headers.set("X-Cache-Key", customCacheKey);
+		return newResponse;
+	},
 };
 ```
 
@@ -256,11 +257,11 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 3. Enter a name, such as `Vary by RSC Header`.
 4. In **If incoming requests match**, select **Custom filter expression**.
 5. Under **When incoming requests match**, manually edit the expression so that it checks for the presence of the `RSC` header:
-    - `has_key(http.request.headers, "rsc")`
+   - `has_key(http.request.headers, "rsc")`
 
 6. Under **Then**:
-    - For **Path**, select **Preserve**.
-    - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
+   - For **Path**, select **Preserve**.
+   - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
 
 7. Select **Save**.
 
@@ -269,8 +270,7 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 Alternatively, use [Snippets](/rules/snippets/) or [Custom Cache Keys](/cache/how-to/cache-keys) to add the `RSC` header directly to the cache key without modifying the visible URL. This provides a cleaner URL but requires more advanced configuration.
 
 :::note[Availability]
+
 - Snippets: Pro, Business, Enterprise
 - Custom Cache Keys: Enterprise only
-:::
-
-
+  :::
diff --git a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
index ab7ed953aa09229..1209ddf6440e3ee 100644
--- a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
+++ b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Serve images in the best format for each visitor browser.
 products:
   - cache
-
 ---
 
-import { Details, FeatureTable, APIRequest } from "~/components"
+import { Details, FeatureTable, APIRequest } from "~/components";
 
 The `Vary` HTTP response header tells Cloudflare that an origin can serve different versions of the same resource depending on the request headers. For images, this allows your origin to serve modern formats like WebP or AVIF to browsers that support them, while continuing to serve JPEG or PNG to others.
 
@@ -25,20 +24,19 @@ Vary for images is available for Pro, Business, and Enterprise customers.
 
 You can use vary for images on the file extensions below if the origin server sends the `Vary: Accept` response header. If the origin server sends `Vary: Accept` but does not serve the set variant, the response is not cached and displays `BYPASS` in the cache status in the response header. Additionally, the list of variant types the origin serves for each extension must be configured so that Cloudflare decides which variant to serve without contacting the origin server.
 
-
 <Details header="File extensions enabled for varying">
-  <ul>
-    <li>.avif</li>
-    <li>.bmp</li>
-    <li>.gif</li>
-    <li>.jpg</li>
-    <li>.jpeg</li>
-    <li>.jp2</li>
-    <li>.png</li>
-    <li>.tif</li>
-    <li>.tiff</li>
-    <li>.webp</li>
-  </ul>
+	<ul>
+		<li>.avif</li>
+		<li>.bmp</li>
+		<li>.gif</li>
+		<li>.jpg</li>
+		<li>.jpeg</li>
+		<li>.jp2</li>
+		<li>.png</li>
+		<li>.tif</li>
+		<li>.tiff</li>
+		<li>.webp</li>
+	</ul>
 </Details>
 
 ## Enable vary for images
@@ -48,46 +46,40 @@ Vary for Images is enabled through Cloudflare's API by creating a variants rule.
 ### Create a variants rule
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp", "image/avif"],
-      jpg: ["image/webp", "image/avif"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp", "image/avif"],
+			jpg: ["image/webp", "image/avif"],
+		},
+	}}
 />
 
 ### Modify to only allow WebP variants
 
 <APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="PATCH"
-  json={{
-    value: {
-      jpeg: ["image/webp"],
-      jpg: ["image/webp"]
-    }
-  }}
+	path="/zones/{zone_id}/cache/variants"
+	method="PATCH"
+	json={{
+		value: {
+			jpeg: ["image/webp"],
+			jpg: ["image/webp"],
+		},
+	}}
 />
 
 ### Delete the rule
 
-<APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="DELETE"
-/>
+<APIRequest path="/zones/{zone_id}/cache/variants" method="DELETE" />
 
 ### Get the rule
 
-<APIRequest
-  path="/zones/{zone_id}/cache/variants"
-  method="GET"
-/>
+<APIRequest path="/zones/{zone_id}/cache/variants" method="GET" />
 
 To learn more about purging varied images, refer to [Purge varied images](/cache/how-to/purge-cache/purge-varied-images/).
 
 ## Limitations
 
-* For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
-* Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
+- For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
+- Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
diff --git a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
index 3978e79c7e9bb20..f115a63a6b91c56 100644
--- a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
+++ b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
@@ -19,22 +19,22 @@ A Content Delivery Network (CDN) like Cloudflare relies on cache keys to compare
 
 To deepen your understanding of the risks and vulnerabilities associated with cache poisoning, consult the following resources:
 
-* [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
-* [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
+- [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
+- [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
 
 ## Only cache files that are truly static
 
 Review the caching configuration for your origin web server and ensure you are caching files that are static and do not depend on user input in any way. To learn more about Cloudflare caching, review:
 
-* [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
-* [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
+- [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
+- [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
 
 ## Do not trust data in HTTP headers
 
 Attackers can exploit HTTP headers to inject malicious content into cached responses. For example, if your application reflects an untrusted header value in the response body, an attacker could use this to perform cross-site scripting (XSS) through the cache. To reduce this risk:
 
-* Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
-* Do not include untrusted header values in your response body.
+- Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
+- Do not include untrusted header values in your response body.
 
 ## Do not trust GET request bodies
 
@@ -44,6 +44,6 @@ Cloudflare caches contents of GET request bodies, but they are not included in t
 
 To keep informed about Internet security threats, Cloudflare recommends that you monitor web security advisories on a regular basis. Some of the more popular advisories include:
 
-* [Drupal Security Advisories](https://www.drupal.org/security)
-* [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
-* [Laminas Security Advisories](https://getlaminas.org/security/advisories)
+- [Drupal Security Advisories](https://www.drupal.org/security)
+- [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
+- [Laminas Security Advisories](https://getlaminas.org/security/advisories)
diff --git a/src/content/docs/cache/cache-security/cache-deception-armor.mdx b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
index a008458a9255072..2b41dc71ac0ea52 100644
--- a/src/content/docs/cache/cache-security/cache-deception-armor.mdx
+++ b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
@@ -24,9 +24,9 @@ In the newsfeed example above, if `http://www.example.com/newsfeed` is a script
 
 ### Exceptions
 
-* If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
-* Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
-* Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
+- If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
+- Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
+- Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
 
 ## Enable Cache Deception Armor
 
diff --git a/src/content/docs/cache/cache-security/cors.mdx b/src/content/docs/cache/cache-security/cors.mdx
index 5f1e357e312c2fe..3f70fe69412f798 100644
--- a/src/content/docs/cache/cache-security/cors.mdx
+++ b/src/content/docs/cache/cache-security/cors.mdx
@@ -12,8 +12,8 @@ A cross-origin request occurs when a webpage on one origin (for example, `a.exam
 
 Cloudflare supports CORS by:
 
-* Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
-* Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
+- Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
+- Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
 
 The `Access-Control-Allow-Origin` header lets a server specify rules for sharing its resources with external origins. A server may respond with different `Access-Control-Allow-Origin` values depending on the `Origin` header in the request. These headers are often present on [cacheable content](/cache/concepts/default-cache-behavior/).
 
@@ -21,9 +21,9 @@ The `Access-Control-Allow-Origin` header lets a server specify rules for sharing
 
 If you add or change CORS configuration at your origin web server, purging the Cloudflare cache by URL does not update the CORS headers. Force Cloudflare to retrieve the new CORS headers via one of the following options:
 
-* Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
-* Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
-* Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
+- Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
+- Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
+- Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
 
 ## Add or change CORS headers on Cloudflare
 
@@ -32,4 +32,3 @@ You can use one of following methods to set CORS headers using Cloudflare produc
 - Use a [Worker](/workers/): Refer to [CORS header proxy](/workers/examples/cors-header-proxy/) for an example.
 - Configure a [Snippet](/rules/snippets/): Refer to [Define CORS headers](/rules/snippets/examples/define-cors-headers/) for an example.
 - Use [Transform Rules](/rules/transform/): Refer to [Add a wildcard CORS response header](/rules/transform/examples/add-cors-header/) for an example.
-
diff --git a/src/content/docs/cache/cache-security/index.mdx b/src/content/docs/cache/cache-security/index.mdx
index 6f753ca961b67d0..3287619c54fa92c 100644
--- a/src/content/docs/cache/cache-security/index.mdx
+++ b/src/content/docs/cache/cache-security/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following content to learn more about cache security.
 
diff --git a/src/content/docs/cache/concepts/cache-behavior.mdx b/src/content/docs/cache/concepts/cache-behavior.mdx
index 212cd5cec8fe30f..ca4b43ee981b90a 100644
--- a/src/content/docs/cache/concepts/cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/cache-behavior.mdx
@@ -11,8 +11,8 @@ tags:
 
 This page describes how Cloudflare's cache system behaves in interaction with:
 
-* `HEAD` requests
-* `Set-Cookie` response headers
+- `HEAD` requests
+- `Set-Cookie` response headers
 
 ## Interaction of `HEAD` requests with Cache
 
@@ -24,8 +24,8 @@ When you make a `HEAD` request for a cacheable resource and Cloudflare does not
 
 For non-cacheable requests, `Set-Cookie` is always preserved. For cacheable requests, there are three possible behaviors:
 
-* `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
+- `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
 
-* `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
+- `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
 
-* `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
+- `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
diff --git a/src/content/docs/cache/concepts/cache-responses.mdx b/src/content/docs/cache/concepts/cache-responses.mdx
index a1f3935e1f26ba9..20f1007625c6956 100644
--- a/src/content/docs/cache/concepts/cache-responses.mdx
+++ b/src/content/docs/cache/concepts/cache-responses.mdx
@@ -7,7 +7,6 @@ products:
 head:
   - tag: title
     content: Cloudflare cache responses
-
 ---
 
 The `CF-Cache-Status` header output indicates whether a resource is cached or not. To investigate cache responses returned by this header, use services like [Redbot](https://redbot.org/), [webpagetest.org](http://www.webpagetest.org/), or a visual tool like [Cloudflare Optics plugin](https://chromewebstore.google.com/detail/cloudflare-optics/mdjgbjnbdnhneejmmaabmccfehigbjbe).
@@ -32,13 +31,13 @@ The resource was not found in Cloudflare's cache and was served from the origin
 
 Cloudflare generated a response that denotes the asset is not eligible for caching. This may have happened because:
 
-* A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
+- A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
 
-* A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
+- A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
 
-* A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
+- A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
 
-* A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
+- A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
 
 ## EXPIRED
 
diff --git a/src/content/docs/cache/concepts/cdn-cache-control.mdx b/src/content/docs/cache/concepts/cdn-cache-control.mdx
index 81e86ba54273c84..ae3401ebbb3fa3b 100644
--- a/src/content/docs/cache/concepts/cdn-cache-control.mdx
+++ b/src/content/docs/cache/concepts/cdn-cache-control.mdx
@@ -18,11 +18,11 @@ If a [Cache Response Rule](/cache/how-to/cache-response-rules/) sets `Cache-Cont
 
 When no Cache Response Rule applies, an origin can:
 
-* Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
+- Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
 
-* Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
+- Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
 
-* Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
+- Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
 
 Additionally, surrogates will not honor `Cache-Control` headers in the response from an origin. For example, if the `Surrogate-Control` header is present within the response, Cloudflare ignores any `Cache-Control` directives, even if the `Surrogate-Control` header does not contain directives.
 
@@ -52,61 +52,61 @@ Use `CDN-Cache-Control` when you want to manage cached asset’s TTLs separately
 
 Headers:
 
-* `Cache-Control: max-age=14400, s-maxage=84000`
-* `Cloudflare-CDN-Cache-Control: max-age=24400`
-* `CDN-Cache-Control: max-age=18000`
+- `Cache-Control: max-age=14400, s-maxage=84000`
+- `Cloudflare-CDN-Cache-Control: max-age=24400`
+- `CDN-Cache-Control: max-age=18000`
 
 Cache behavior:
 
 <table>
-  <tbody>
-    <th colspan="5" rowspan="1">
-      Caches
-    </th>
-    <th colspan="5" rowspan="1">
-      Cache TTL (seconds)
-    </th>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Origin Server Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        14400
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Network Shared Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        84000
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Cloudflare Edge
-      </td>
-      <td colspan="5" rowspan="1">
-        24400
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Other CDNs
-      </td>
-      <td colspan="5" rowspan="1">
-        18000
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Browser Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        14400
-      </td>
-    </tr>
-  </tbody>
+	<tbody>
+		<th colspan="5" rowspan="1">
+			Caches
+		</th>
+		<th colspan="5" rowspan="1">
+			Cache TTL (seconds)
+		</th>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Origin Server Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				14400
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Network Shared Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				84000
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Cloudflare Edge
+			</td>
+			<td colspan="5" rowspan="1">
+				24400
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Other CDNs
+			</td>
+			<td colspan="5" rowspan="1">
+				18000
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Browser Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				14400
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ### Specify when to serve stale content
@@ -115,43 +115,43 @@ Use `CDN-Cache-Control` headers in conjunction with `Cache-Control` headers to s
 
 Headers:
 
-* `Cache-Control: stale-if-error=400`
-* `Cloudflare-CDN-Cache-Control: stale-if-error=60`
-* `CDN-Cache-Control: stale-if-error=200`
+- `Cache-Control: stale-if-error=400`
+- `Cloudflare-CDN-Cache-Control: stale-if-error=60`
+- `CDN-Cache-Control: stale-if-error=200`
 
 Behavior in response to [5XX error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/):
 
 <table>
-  <tbody>
-    <th colspan="5" rowspan="1">
-      Caches
-    </th>
-    <th colspan="5" rowspan="1">
-      Stale served (seconds) in response to error
-    </th>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Origin Cache Layer/Network Cache/Browser Cache
-      </td>
-      <td colspan="5" rowspan="1">
-        400 (if it assumes the directive applies)
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Cloudflare Edge
-      </td>
-      <td colspan="5" rowspan="1">
-        60
-      </td>
-    </tr>
-    <tr>
-      <td colspan="5" rowspan="1">
-        Other CDN
-      </td>
-      <td colspan="5" rowspan="1">
-        200
-      </td>
-    </tr>
-  </tbody>
+	<tbody>
+		<th colspan="5" rowspan="1">
+			Caches
+		</th>
+		<th colspan="5" rowspan="1">
+			Stale served (seconds) in response to error
+		</th>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Origin Cache Layer/Network Cache/Browser Cache
+			</td>
+			<td colspan="5" rowspan="1">
+				400 (if it assumes the directive applies)
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Cloudflare Edge
+			</td>
+			<td colspan="5" rowspan="1">
+				60
+			</td>
+		</tr>
+		<tr>
+			<td colspan="5" rowspan="1">
+				Other CDN
+			</td>
+			<td colspan="5" rowspan="1">
+				200
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/docs/cache/concepts/customize-cache.mdx b/src/content/docs/cache/concepts/customize-cache.mdx
index c4f49110ea13c65..1a9047525da3655 100644
--- a/src/content/docs/cache/concepts/customize-cache.mdx
+++ b/src/content/docs/cache/concepts/customize-cache.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: Methods for customizing cache behavior with rules, Workers, and headers.
 products:
   - cache
-
 ---
 
 Some possible combinations of origin web server settings and Cloudflare [Cache Rules](/cache/how-to/cache-rules/) include:
@@ -13,21 +12,21 @@ Some possible combinations of origin web server settings and Cloudflare [Cache R
 
 For example, create a `/static/` subdirectory at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
-* Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
+- Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
 
 ## Append a unique file extension to static pages
 
 For example, create a `.shtml` file extension for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
-* Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
+- Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
 
 ## Add a query string to a resource’s URL to mark the content as static
 
 For example, add a `static=true` query string for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-* Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
-* Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
+- Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
+- Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
 
 Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a Cache-Control header of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.
diff --git a/src/content/docs/cache/concepts/default-cache-behavior.mdx b/src/content/docs/cache/concepts/default-cache-behavior.mdx
index 0f9a375df7316c6..6749f5b82907cf1 100644
--- a/src/content/docs/cache/concepts/default-cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/default-cache-behavior.mdx
@@ -7,20 +7,24 @@ products:
 head:
   - tag: title
     content: Default Cache Behavior
-
 ---
 
-import { FeatureTable, GlossaryTooltip, Render, DashButton } from "~/components"
+import {
+	FeatureTable,
+	GlossaryTooltip,
+	Render,
+	DashButton,
+} from "~/components";
 
 Cloudflare respects the origin web server’s cache headers in the following order unless an [Edge Cache TTL cache rule](/cache/how-to/cache-rules/settings/#edge-ttl) overrides the headers. Refer to the [Edge TTL](/cache/how-to/configure-cache-status-code/#edge-ttl) section for details on default TTL behavior.
 
-* Cloudflare **does not** cache the resource when:
-  * The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
-  * The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
-  * The HTTP request method is anything other than a `GET`.
-* Cloudflare **does** cache the resource when:
-  * The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
-  * The `Expires` header is set to a future date.
+- Cloudflare **does not** cache the resource when:
+  - The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
+  - The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
+  - The HTTP request method is anything other than a `GET`.
+- Cloudflare **does** cache the resource when:
+  - The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
+  - The `Expires` header is set to a future date.
 
 :::note
 Cloudflare does cache the resource even if there is no `Cache-Control` header based on [status codes](/cache/how-to/configure-cache-status-code/#edge-ttl).
@@ -36,8 +40,8 @@ When [Origin Cache Control](/cache/concepts/cache-control/) is enabled on an Ent
 
 Clients can send range requests to be served from the cache using the `Range` header. Note that:
 
- - If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
- - If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
+- If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
+- If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
 
 ## Request collapsing
 
@@ -64,10 +68,10 @@ Cloudflare only caches based on file extension and not by MIME type. The Cloudfl
 To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/) to create a rule to cache everything.
 
 <Render
-  file="edge-ttl"
+	file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
@@ -75,14 +79,14 @@ To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/)
 
 Cloudflare’s CDN provides several cache customization options:
 
-* Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
+- Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
 
- <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+<DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
-* Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
-* Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
+- Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
+- Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
 
- <DashButton url="/?to=/:account/:zone/caching/configuration" />
+<DashButton url="/?to=/:account/:zone/caching/configuration" />
 
 ### Upload limits
 
@@ -96,8 +100,8 @@ If you require a larger upload, you can group requests into smaller chunks, uplo
 
 Cloudflare cacheable file limits:
 
-* Free, Pro and Business customers have a limit of 512 MB.
-* For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
+- Free, Pro and Business customers have a limit of 512 MB.
+- For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
 
 ## When does Cloudflare cache successfully?
 
diff --git a/src/content/docs/cache/concepts/index.mdx b/src/content/docs/cache/concepts/index.mdx
index 9d7aa540158df71..c39bdbe713dbf77 100644
--- a/src/content/docs/cache/concepts/index.mdx
+++ b/src/content/docs/cache/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-    
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts and components of Cloudflare Cache.
 
diff --git a/src/content/docs/cache/concepts/retention-vs-freshness.mdx b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
index 1148870b16f91ca..86ee2ef5d7736c5 100644
--- a/src/content/docs/cache/concepts/retention-vs-freshness.mdx
+++ b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: How cache retention and TTL freshness differ in Cloudflare.
 products:
   - cache
-
 ---
 
 In the context of Cloudflare CDN (Content Delivery Network), retention and freshness refer to two separate but related concepts. For an object in cache, freshness is how long it should be considered valid without consulting its source, while retention refers to how long it stays in cache before being removed.
@@ -19,8 +18,8 @@ Cloudflare uses a Least Recently Used (LRU) algorithm to decide which objects to
 
 Freshness, also known as Time to Live (TTL), determines how long a cache can use an object without checking with the origin again. For example, if an object has a TTL of five minutes, the cache serves it directly for five minutes after first receiving it. After five minutes, Cloudflare must check with the origin to confirm the object is still valid before serving it again. There are a few ways to configure TTLs for resources served through Cloudflare's CDN:
 
-* Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
+- Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
 
-* Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
+- Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
 
 If an object in cache is no longer fresh, Cloudflare revalidates it with the origin. When [`stale-while-revalidate`](/cache/concepts/cache-control/#revalidation) is set, revalidation happens asynchronously at expiry — visitors continue to be served from cache while Cloudflare fetches a fresh copy in the background. Without this directive, incoming requests wait for the origin to respond before receiving content. The origin can either confirm the cached object is still valid (refreshing its TTL) or return a new version to replace it. Refer to [Revalidation](/cache/concepts/revalidation/) for details.
diff --git a/src/content/docs/cache/concepts/revalidation.mdx b/src/content/docs/cache/concepts/revalidation.mdx
index be6792de1f48057..f289dc2c55c0ce6 100644
--- a/src/content/docs/cache/concepts/revalidation.mdx
+++ b/src/content/docs/cache/concepts/revalidation.mdx
@@ -4,7 +4,6 @@ pcx_content_type: concept
 description: How Cloudflare revalidates stale cached content with your origin.
 products:
   - cache
-
 ---
 
 ## Stale-while-revalidate
diff --git a/src/content/docs/cache/get-started.mdx b/src/content/docs/cache/get-started.mdx
index ab1be9257230ee3..485414c218db17e 100644
--- a/src/content/docs/cache/get-started.mdx
+++ b/src/content/docs/cache/get-started.mdx
@@ -13,7 +13,7 @@ head:
     content: Get started with Cache
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare speeds up your website by caching content across globally distributed data centers.
 
@@ -21,12 +21,12 @@ Content can be static or dynamic. Static content — such as images, CSS, and Ja
 
 Cloudflare caches static content based on the following factors:
 
-* [Caching levels](/cache/how-to/set-caching-levels/)
-* [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
-* Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
-* [Origin cache-control headers](/cache/concepts/cache-control/)
-* Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
-* Cache rules that bypass cache on cookie
+- [Caching levels](/cache/how-to/set-caching-levels/)
+- [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+- Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
+- [Origin cache-control headers](/cache/concepts/cache-control/)
+- Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
+- Cache rules that bypass cache on cookie
 
 Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, or content hosted on [DNS-only (unproxied)](/dns/proxy-status/) DNS records.
 
@@ -34,35 +34,35 @@ Cloudflare only caches resources within the Cloudflare data center that serve th
 
 Discover the benefits of caching with Cloudflare's CDN and understand the default cache behavior.
 
-* [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
-* [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
-* [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+- [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
+- [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
+- [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
 
 ## Make more resources cacheable
 
 Configure your settings to cache static HTML or cache anonymous page views of dynamic content.
 
-* [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
-* [Specify which resources to cache](/cache/concepts/customize-cache/)
-* [Understand Origin Cache Control](/cache/concepts/cache-control/)
-* [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
+- [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
+- [Specify which resources to cache](/cache/concepts/customize-cache/)
+- [Understand Origin Cache Control](/cache/concepts/cache-control/)
+- [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
 
 ## Improve cache HIT rates
 
 Include or exclude query strings, optimize cache keys, or enable [Tiered Cache](/cache/how-to/tiered-cache/) to improve HIT rates and reduce traffic to your origin.
 
-* [Choose a cache level](/cache/how-to/set-caching-levels/)
-* [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
-* [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
-* [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
+- [Choose a cache level](/cache/how-to/set-caching-levels/)
+- [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
+- [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
+- [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
 
 ## Secure your cache configuration
 
 Control resources a client is allowed to load and set access permissions to allow different origins to access your origin's resources. Protect your site from web cache deception attacks while still caching static assets.
 
-* [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
-* [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
-* [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
+- [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
+- [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
+- [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
 
 ## Features that alter cached content
 
@@ -70,16 +70,16 @@ Some Cloudflare features modify your HTML or cached objects at the edge to enabl
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. Cloudflare removes the changes when you disable the feature and purge the cache.
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. The changes are removed if the feature is disabled and the cache is purged.
 
-* [Rocket Loader](/speed/optimization/content/rocket-loader/)
-* [Polish](/images/polish/)
-* [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
-* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
-* [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
+- [Rocket Loader](/speed/optimization/content/rocket-loader/)
+- [Polish](/images/polish/)
+- [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
+- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
+- [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
 
 ## Troubleshoot
 
 Resolve common caching concerns.
 
-* [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
-* [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
-* [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
+- [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
+- [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
+- [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
diff --git a/src/content/docs/cache/glossary.mdx b/src/content/docs/cache/glossary.mdx
index 93414f59d8d1137..ae52887a0324745 100644
--- a/src/content/docs/cache/glossary.mdx
+++ b/src/content/docs/cache/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Cache documentation.
 products:
   - cache
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Cache documentation.
 
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
index 5e0cffeecb60098..26540e1b1bc9dfc 100644
--- a/src/content/docs/cache/how-to/always-online.mdx
+++ b/src/content/docs/cache/how-to/always-online.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Serve cached pages when your origin server is unavailable.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Cloudflare’s Always Online feature is now integrated with the [Internet Archive](https://archive.org/) so that visitors can access a portion of your website even when your origin server is unreachable and a Cloudflare-cached version is unavailable. When your origin is unreachable, Always Online checks Cloudflare’s cache for a stale or expired version of your website. If a version does not exist, Cloudflare goes to the Internet Archive to fetch and serve static portions of your website.
 
@@ -46,10 +45,8 @@ Here is how to enable Always Online in the dashboard:
 
 :::note[Note]
 
-
 When turning on Always Online, you are also enabling the Internet Archive integration.
 
-
 :::
 
 Refer to [Always Online](/cache/troubleshooting/always-online/) for best practices, limitations, and FAQs.
diff --git a/src/content/docs/cache/how-to/cache-keys.mdx b/src/content/docs/cache/how-to/cache-keys.mdx
index 59b3e1e4cd98538..8afbd280f376234 100644
--- a/src/content/docs/cache/how-to/cache-keys.mdx
+++ b/src/content/docs/cache/how-to/cache-keys.mdx
@@ -14,16 +14,16 @@ head:
     content: Cache Keys
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.
 
 A default cache key includes:
 
 1. Full URL:
-   * scheme - could be HTTP or HTTPS.
-   * host - for example, `www.cloudflare.com`
-   * URI with query string - for example, `/logo.jpg?utm_source=newsletter`
+   - scheme - could be HTTP or HTTPS.
+   - host - for example, `www.cloudflare.com`
+   - URI with query string - for example, `/logo.jpg?utm_source=newsletter`
 2. Origin header sent by client (for CORS support).
 3. `x-http-method-override`, `x-http-method`, and `x-method-override` headers.
 4. `x-forwarded-host`, `x-host`, `x-forwarded-scheme` (unless http or https), `x-original-url`, `x-rewrite-url`, and `forwarded` headers.
@@ -51,8 +51,8 @@ When [URL normalization](/rules/normalization/) is enabled, we recommend also en
 
 There are a couple of common reasons to change the Cache Key Template. You might change the Cache Key Template to:
 
-* Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
-* Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
+- Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
+- Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
 
 ### Impact of SSL settings on Cache behavior
 
@@ -90,9 +90,9 @@ If you include the query string foo in a URL like `https://www.example.com/?foo=
 
 #### Usage notes
 
-* To include all query string parameters (the default behavior), use include: `"\*"`
-* To ignore query strings, use exclude: `"\*"`
-* To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
+- To include all query string parameters (the default behavior), use include: `"\*"`
+- To ignore query strings, use exclude: `"\*"`
+- To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
 
 ### Headers
 
@@ -102,13 +102,13 @@ When you include a header, the header value is included in the Cache Key. For ex
 
 In the **Include headers and selected values** section, you can add header names and their values to the cache key. For custom headers, values are optional, but for the following restricted headers, you must include one to 10 specific values:
 
-  * `accept`
-  * `accept-charset`
-  * `accept-encoding`
-  * `accept-datetime`
-  * `accept-language`
-  * `referer`
-  * `user-agent`
+- `accept`
+- `accept-charset`
+- `accept-encoding`
+- `accept-datetime`
+- `accept-language`
+- `referer`
+- `user-agent`
 
 To check for the presence of a header without including its actual value, use the **Check presence of** option.
 
@@ -116,28 +116,28 @@ Currently, you can only exclude the `Origin` header. The `Origin` header is alwa
 
 Additionally, you cannot include the following headers:
 
-* Headers that re-implement cache or proxy features
-  * `connection`
-  * `content-length`
-  * `cache-control`
-  * `if-match`
-  * `if-modified-since`
-  * `if-none-match`
-  * `if-unmodified-since`
-  * `range`
-  * `upgrade`
-* Headers that are covered by other Cache Key features
-  * `cookie`
-  * `host`
-* Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
-* Headers that are already included in the custom Cache Key template, for example, `origin`
+- Headers that re-implement cache or proxy features
+  - `connection`
+  - `content-length`
+  - `cache-control`
+  - `if-match`
+  - `if-modified-since`
+  - `if-none-match`
+  - `if-unmodified-since`
+  - `range`
+  - `upgrade`
+- Headers that are covered by other Cache Key features
+  - `cookie`
+  - `host`
+- Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
+- Headers that are already included in the custom Cache Key template, for example, `origin`
 
 ### Host
 
 Host determines which host header to include in the Cache Key.
 
-* If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
-* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
+- If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
+- If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
 
 ### Cookie
 
@@ -151,9 +151,9 @@ You cannot include cookies specific to Cloudflare. Cloudflare cookies are prefix
 
 User feature fields add features about the end-user (client) into the Cache Key.
 
-* `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
-* `geo` includes the client’s country, derived from the IP address
-* `lang` includes the first language code contained in the `Accept-Language` header sent by the client
+- `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
+- `geo` includes the client’s country, derived from the IP address
+- `lang` includes the first language code contained in the `Accept-Language` header sent by the client
 
 ## Availability
 
diff --git a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
index f8032d4bd1be12e..7c75c81a407e301 100644
--- a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
+++ b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
@@ -30,7 +30,6 @@ 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 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:
@@ -43,7 +42,8 @@ import { Render, DashButton } from "~/components";
    - **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**.
 
-   <Render file="rules-creation-dash-dns-popup" product="rules" />
+<Render file="rules-creation-dash-dns-popup" product="rules" />
diff --git a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
index ba3e5a14e0342aa..24434a23533ec9f 100644
--- a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: false
 pcx_content_type: navigation
 description: Example cache rule configurations for common use cases.
@@ -8,10 +7,9 @@ products:
 title: Examples
 sidebar:
   order: 8
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In the following sections, you can find common cache rules examples.
 
diff --git a/src/content/docs/cache/how-to/cache-rules/order.mdx b/src/content/docs/cache/how-to/cache-rules/order.mdx
index 40377bc15fa1145..5810d731d8608f8 100644
--- a/src/content/docs/cache/how-to/cache-rules/order.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/order.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Order and priority
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cache rules affect requests differently from Page Rules. This is how they are applied:
 
diff --git a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
index 6541177a91b6aa8..b1875b3767c20c3 100644
--- a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
@@ -13,7 +13,7 @@ head:
     content: Migration from Page Rules
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 If you are migrating from Page Rules, there is a behavior change between Page Rules and Cache Rules.
 
@@ -64,10 +64,8 @@ If you prefer, you can select **Edit expression** and paste the following expres
 
 :::note[Note]
 
-
 Remember to create the rules in the specified order: first, the `bypass everything` rule, and then the `cache all default cacheable file extensions` rule.
 
 ![Rules order](~/assets/images/cache/rule-order.png)
 
-
 :::
diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
index 2c71df51f6c0e94..c30d541d4d833c7 100644
--- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx
+++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
@@ -8,7 +8,7 @@ tags:
   - REST API
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin.
 
@@ -19,10 +19,10 @@ Setting cache TTL based on response status overrides the [default cache behavior
 The maximum caching limit for Free, Pro, and Business customers is 512 MB per file, and the maximum caching limit for Enterprise customers is 5 GB per file. If you need to raise the limits, contact your Customer Success Manager.
 
 <Render
-  file="edge-ttl"
+	file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile"
+		conditional: "dedicated-cache-tile",
 	}}
 />
 
@@ -79,9 +79,9 @@ curl --request PUT \
 
 Provide a JSON object containing status codes and their corresponding TTLs. Each key-value pair in the cache TTL by status cache rule has the following syntax:
 
-* `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
-* `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
-* `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
+- `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
+- `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
+- `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
 
 ## Set cache TTL by response status via a Cloudflare Worker
 
@@ -98,4 +98,4 @@ The **cacheTtlByStatus** option is a version of the **cacheTtl** feature that de
 
 For example, if a user specifies a TTL of one hour for status `200` and 0 seconds (cache and always revalidate) for status `304`, the asset will be cached for 1 hour. After it expires, we revalidate with the origin. If the origin returns a `304`, each subsequent request will trigger revalidation. If the origin continues to return `304`, this cycle will persist.
 
-This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
\ No newline at end of file
+This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
index 9bd8eb61f1eeb6f..c26df5fd963f037 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: Configure edge and browser cache TTL for your resources.
 products:
   - cache
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 ## Edge Cache TTL
 
@@ -21,17 +20,16 @@ For more information on how to set up Edge Cache TTL, refer to [Cache rules](/ca
 
 The Browser Cache TTL sets the expiration for resources cached in a visitor’s browser. By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers but overrides those headers if:
 
-* The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
-* The origin web server does not send a `Cache-Control` or an `Expires` header.
+- The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
+- The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a cache rule, Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
 :::note[Note]
 
-
-* Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
-* If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
-* Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser. 
+- Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
+- If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
+- Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.
   :::
 
 <FeatureTable id="cache.browser_cache_ttl" />
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
index fcaf35844aa8d00..bed629ee6ba70c8 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 3
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +14,8 @@ Specify a time for a visitor’s Browser Cache TTL to accelerate the page load f
 
 By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers. Cloudflare overrides any `Cache-Control` or `Expires` headers with values set via the **Browser Cache TTL** option under **Caching** on your dashboard if:
 
-* The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
-* The origin web server does not send a `Cache-Control` or an `Expires` header.
+- The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
+- The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a [Cache Rule](/cache/how-to/cache-rules/), Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
@@ -26,10 +25,8 @@ Nevertheless, the value you set via Cache Rule will be ignored if `Cache-Control
 
 :::note[Note]
 
-
 If you modify cached assets, the new asset is not displayed to repeat visitors before the Browser Cache TTL duration. [Purging Cloudflare’s cache](/cache/how-to/purge-cache/) does not affect assets cached in a visitor’s browser.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Caching** page.
diff --git a/src/content/docs/cache/how-to/index.mdx b/src/content/docs/cache/how-to/index.mdx
index 80c1f5c0266452d..9bb4c1c487aacad 100644
--- a/src/content/docs/cache/how-to/index.mdx
+++ b/src/content/docs/cache/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
index eccbbdee17432d8..f33d3c2f25167fd 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 4
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Purging by hostname means that all assets at URLs with a host that matches one of the provided values will be instantly purged from the cache.
 
@@ -20,9 +19,9 @@ Purging by hostname means that all assets at URLs with a host that matches one o
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Hostname**.
 4. Follow the syntax instructions:
-   * One hostname per line.
-   * Separated by commas.
-   * You can purge up to 30 hostnames at a time.
+   - One hostname per line.
+   - Separated by commas.
+   - You can purge up to 30 hostnames at a time.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
index 1eba5da16e5ee10..20267fbc6318106 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 With purge by single-file, cached resources are instantly removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific Cloudflare data center that served the request.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
index 0531322accc993e..0b305a3f14ae32d 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 3
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more.
 
@@ -23,10 +22,8 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 
 :::caution[Warning]
 
-
 Be careful when purging. A cache MISS can cause execution delays by requiring a fetch from your origin server.
 
-
 :::
 
 ## Add Cache-Tag HTTP response headers
@@ -35,19 +32,19 @@ You add cache-tags to your web content in `Cache-Tag` HTTP response headers to a
 
 When your content reaches our edge network, Cloudflare:
 
-* Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
-* Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
-* Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
+- Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
+- Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
+- Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
 
 ## A few things to remember
 
-* A single HTTP response can have more than one `Cache-Tag` HTTP header field.
-* The minimum length of a cache-tag is one byte.
-* Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
-* For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
-* The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
-* Spaces are not allowed in cache-tags.
-* Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
+- A single HTTP response can have more than one `Cache-Tag` HTTP header field.
+- The minimum length of a cache-tag is one byte.
+- Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
+- For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
+- The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
+- Spaces are not allowed in cache-tags.
+- Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
 
 ## Purge using cache-tags
 
@@ -62,7 +59,6 @@ When your content reaches our edge network, Cloudflare:
 
 For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
 
-
 ## Resulting cache status
 
 Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests.
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
index 831850a380c6d9f..d251d69477368b4 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
@@ -25,18 +25,18 @@ For a Cache Key based on device type, purge the asset by passing the `CF-Device-
 Refer to the example API request below to instantly purge all mobile assets on the root webpage.
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "CF-Device-Type": "mobile"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"CF-Device-Type": "mobile",
+				},
+			},
+		],
+	}}
 />
 
 ## Purge by geo
@@ -44,18 +44,18 @@ Refer to the example API request below to instantly purge all mobile assets on t
 Instantly purge resources for a location-based Cache Key by specifying the two-letter country code. Spain is used in the example below.
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "CF-IPCountry": "ES"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"CF-IPCountry": "ES",
+				},
+			},
+		],
+	}}
 />
 
 ## Purge by language
@@ -63,16 +63,16 @@ Instantly purge resources for a location-based Cache Key by specifying the two-l
 For a Cache Key based on language, purge the asset by passing the `accept-language` header. Refer to the example API request below to instantly purge all assets in Chinese (PRC).
 
 <APIRequest
-  path="/zones/{zone_id}/purge_cache"
-  method="POST"
-  json={{
-    files: [
-      {
-        url: "http://my.website.com/",
-        headers: {
-          "accept-language": "zh-CN"
-        }
-      }
-    ]
-  }}
+	path="/zones/{zone_id}/purge_cache"
+	method="POST"
+	json={{
+		files: [
+			{
+				url: "http://my.website.com/",
+				headers: {
+					"accept-language": "zh-CN",
+				},
+			},
+		],
+	}}
 />
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
index 1253a3d847f6bfb..42378f5e362023e 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
@@ -6,10 +6,9 @@ products:
   - cache
 sidebar:
   order: 2
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 To maintain optimal site performance, Cloudflare strongly recommends using single-file (by URL) purging instead of a complete cache purge.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
index 2da37b5840f703d..f2953ab487936d9 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 7
-
 ---
 
 Purging varied images instantly purges all content variants for that URL. This behavior occurs so that if an image changes, you can easily update the cache with a single purge request instead of trying to determine the potential number of out-of-date variants. The behavior is true regardless of [purge type](/cache/how-to/purge-cache/) used, such as [single file](/cache/how-to/purge-cache/purge-by-single-file/), [tag](/cache/how-to/purge-cache/purge-by-tags/), or [hostname](/cache/how-to/purge-cache/purge-by-hostname/).
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
index 06f0af7f6b98cd4..837b8a1faf20235 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
@@ -6,7 +6,6 @@ products:
   - cache
 sidebar:
   order: 8
-
 ---
 
 To purge zone versions via the Cloudflare API, follow these steps:
@@ -23,44 +22,44 @@ This API call will return a JSON response similar to the example below:
 
 ```json
 {
-  "result": {
-    "environments": [
-      {
-        "name": "Production",
-        "ref": "12abcd3e45f678940a573f51834a54",
-        "version": 0,
-        "expression": "(cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "before": "5d41402abc4b2a76b9719d911017c"
-        }
-      },
-      {
-        "name": "Staging",
-        "ref": "5d41402abc4b2a76b9719d911017c",
-        "version": 0,
-        "expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "before": "49f0bad299687c62334182178bfd",
-          "after": "12abcd3e45f678940a573f51834a54"
-        }
-      },
-      {
-        "name": "Development",
-        "ref": "49f0bad299687c62334182178bfd",
-        "version": 0,
-        "expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
-        "locked_on_deployment": false,
-        "position": {
-          "after": "5d41402abc4b2a76b9719d911017c"
-        }
-      }
-    ]
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"environments": [
+			{
+				"name": "Production",
+				"ref": "12abcd3e45f678940a573f51834a54",
+				"version": 0,
+				"expression": "(cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"before": "5d41402abc4b2a76b9719d911017c"
+				}
+			},
+			{
+				"name": "Staging",
+				"ref": "5d41402abc4b2a76b9719d911017c",
+				"version": 0,
+				"expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"before": "49f0bad299687c62334182178bfd",
+					"after": "12abcd3e45f678940a573f51834a54"
+				}
+			},
+			{
+				"name": "Development",
+				"ref": "49f0bad299687c62334182178bfd",
+				"version": 0,
+				"expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
+				"locked_on_deployment": false,
+				"position": {
+					"after": "5d41402abc4b2a76b9719d911017c"
+				}
+			}
+		]
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -76,7 +75,7 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/purge_cache/
 
 To purge non-production environments, you must use a new `purge_cache` endpoint and specify the environment you would like to purge.
 
-To purge the Staging environment from the example above, send a request to the following endpoint: 
+To purge the Staging environment from the example above, send a request to the following endpoint:
 
 ```bash
 https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/5d41402abc4b2a76b9719d911017c/purge_cache/
@@ -90,4 +89,4 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/49f0bad299687c
 
 :::note
 When purging everything for a non-production cache environment, all files for that specific cache environment will be purged. However, when purging everything for the production environment, all files will be purged across all environments.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
index 315411bd1db2ac1..38922ec63e70388 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
@@ -6,24 +6,23 @@ products:
   - cache
 sidebar:
   order: 5
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 You can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
 
-* `www.example.com`
-* `www.example.com/foo`
-* `www.example.com/foo/bar`
-* `www.example.com/foo/bar/baz`
-* `www.example.com/foo/bar/baz/qux.jpg`
+- `www.example.com`
+- `www.example.com/foo`
+- `www.example.com/foo/bar`
+- `www.example.com/foo/bar/baz`
+- `www.example.com/foo/bar/baz/qux.jpg`
 
 Purging by prefix is useful in different scenarios, such as:
 
-* Purging everything within a directory.
-* Increasing control over cached objects in a path.
-* Simplifying the number of purge calls sent.
+- Purging everything within a directory.
+- Increasing control over cached objects in a path.
+- Simplifying the number of purge calls sent.
 
 1. In the Cloudflare dashboard, go to the **Configuration** page.
 
@@ -32,8 +31,8 @@ Purging by prefix is useful in different scenarios, such as:
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Prefix**.
 4. Follow the syntax instructions.
-   * One prefix per line.
-   * Maximum 30 prefixes per API call.
+   - One prefix per line.
+   - Maximum 30 prefixes per API call.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
@@ -41,10 +40,8 @@ For information on rate limits, refer to the [Availability and limits](/cache/ho
 
 :::caution[Warning]
 
-
 If you have a [Transform Rule](/rules/transform/) in place that is modifying part of a URL path, you must use the post-transformed (origin) URL when performing a prefix purge so that purge can take effect.
 
-
 :::
 
 ## Resulting cache status
@@ -58,21 +55,19 @@ Depending on whether the upper tier has the resource or not, and whether the end
 
 There are several limitations regarding purge by prefix:
 
-* Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
-* Purge requests are limited to 30 prefixes per request.
-* [Purge rate-limits apply](/api/resources/cache/methods/purge/).
-* URI query strings & fragments cannot purge by prefix:
-  * `www.example.com/foo?a=b` (query string)
-  * `www.example.com/foo#bar` (fragment)
+- Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
+- Purge requests are limited to 30 prefixes per request.
+- [Purge rate-limits apply](/api/resources/cache/methods/purge/).
+- URI query strings & fragments cannot purge by prefix:
+  - `www.example.com/foo?a=b` (query string)
+  - `www.example.com/foo#bar` (fragment)
 
 :::caution[Warning]
 
-
 Because purge by prefix purges a directory, any URI for a resource within the purged directory is purged regardless of query string or fragment (though fragments are not generally sent by browsers). Purge by prefix rules do not accept fragments and query strings.
 
 Example: If you purge `foo.com/bar`, any asset that starts with `foo.com/bar` will be purged, for example, `foo.com/bar/baz`, `foo.com/bar?good=bad`, etc. and purging `foo.com/bar?good=bad` itself will not work.
 
-
 :::
 
 ## Purge by prefix normalization
diff --git a/src/content/docs/cache/how-to/set-caching-levels.mdx b/src/content/docs/cache/how-to/set-caching-levels.mdx
index 4d6a0dee4f74ba7..84cb1614461925d 100644
--- a/src/content/docs/cache/how-to/set-caching-levels.mdx
+++ b/src/content/docs/cache/how-to/set-caching-levels.mdx
@@ -7,23 +7,20 @@ products:
 head:
   - tag: title
     content: Caching levels
-
 ---
 
 Caching levels determine how much of your website’s static content Cloudflare should cache. Cloudflare’s CDN caches static content according to the levels below.
 
-* **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
-* **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
-* **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
+- **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
+- **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
+- **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
 
 You can adjust the caching level from the dashboard under **Caching** > **Configuration** > **Caching level**.
 
 :::note[Note]
 
-
 Ignore Query String only disregards the query string for static file extensions. For example, Cloudflare serves the `style.css` resource to requests for either `style.css?this` or `style.css?that`.
 
-
 :::
 
 ## API Caching level values
diff --git a/src/content/docs/cache/interaction-cloudflare-products/index.mdx b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
index 449a56ed4e7345c..842985c69a31adc 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/index.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-    
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare caches content at data centers close to your visitors so your origin server handles fewer requests. The pages below explain how caching works when you also use Workers, R2 storage, or WAF security rules, and what to watch out for when combining them.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
index ed54947bc4e5f34..11c3946c910d777 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Enable cache in an R2 bucket
-
 ---
 
 By default, R2 buckets are private. To serve R2 objects through Cloudflare's cache, you need to attach a domain name you control — called a [Custom Domain](/r2/buckets/public-buckets/#custom-domains) — to the bucket. This creates a public URL backed by Cloudflare's network, so requests for your stored files go through Cloudflare's cache instead of hitting R2 directly every time.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
index fb6bf25720d358f..5f5d22b02dd934b 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
@@ -23,7 +23,7 @@ accTitle: Connections with Cloudflare
 A[User's request] --> B[WAF] --> C[Cache] --> D[R2]
 ```
 
-<br/>
+<br />
 
 ## Presigned URLs
 
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
index 390f1369a9cee75..a7765d2c345f3a1 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: How Workers interact with Cache Rules
-
 ---
 
 When you use both [Cache Rules](/cache/how-to/cache-rules/) and [Workers](/workers/) on the same request, the Worker's cache settings take priority — but only when the required [compatibility flags](#compatibility-flags) are enabled.
@@ -39,10 +38,10 @@ These flags must be enabled to allow Workers scripts to override Cache Rules. If
 
 A Worker's [compatibility date](/workers/configuration/compatibility-dates/) determines which flags are active by default. When you set a compatibility date, all flags with an enable date on or before that date are automatically turned on.
 
-| Flag | Enabled by default | Prerequisite |
-| --- | --- | --- |
-| `request_cf_overrides_cache_rules` (Fetch API) | Compatibility dates on or after `2025-04-02` | None |
-| `cache_api_compat_flags` | Compatibility dates on or after `2025-04-19` | None |
+| Flag                                                     | Enabled by default                           | Prerequisite                      |
+| -------------------------------------------------------- | -------------------------------------------- | --------------------------------- |
+| `request_cf_overrides_cache_rules` (Fetch API)           | Compatibility dates on or after `2025-04-02` | None                              |
+| `cache_api_compat_flags`                                 | Compatibility dates on or after `2025-04-19` | None                              |
 | `cache_api_request_cf_overrides_cache_rules` (Cache API) | Compatibility dates on or after `2025-05-19` | Requires `cache_api_compat_flags` |
 
 The Cache API has an extra requirement: `cache_api_compat_flags` must be enabled for any compatibility flags to take effect on the Cache API. Without it, the Cache API ignores all compatibility flags, even ones you explicitly list in your configuration.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
index 0b90c7883ab5180..91df57a65ed0396 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Customize cache behavior with Workers
-
 ---
 
 You can use [Workers](/workers/) to customize cache behavior on Cloudflare's network. Workers run as middleware in the request lifecycle — a single Worker handles both the request and response phases. When a request arrives, it hits the Worker before the cache is checked. The Worker can modify the incoming request (for example, rewrite the URL or add headers), then call `fetch()` to continue the request through the cache. When the response comes back — whether from cache or from the origin server — the Worker can also modify the response before it is sent to the visitor.
@@ -46,4 +45,4 @@ Workers offer two ways to interact with the cache. Use `fetch()` when your Worke
 
 - **Cache API**: Allows you to programmatically store, retrieve, and delete responses in Cloudflare's cache using `caches.default` or `caches.open()`. Unlike `fetch()`, the Cache API only operates on the cache in the data center handling the current request — it does not interact with Tiered Cache. Use the Cache API when you need to cache responses that did not come from an origin. For more details, refer to [Using the Cache API](/workers/examples/cache-api/).
 
-To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
\ No newline at end of file
+To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
diff --git a/src/content/docs/cache/performance-review/cache-analytics.mdx b/src/content/docs/cache/performance-review/cache-analytics.mdx
index 5e225c6a89340c7..6db30fa95015ec1 100644
--- a/src/content/docs/cache/performance-review/cache-analytics.mdx
+++ b/src/content/docs/cache/performance-review/cache-analytics.mdx
@@ -4,10 +4,9 @@ pcx_content_type: concept
 description: View cache hit rates and bandwidth savings in Cache Analytics.
 products:
   - cache
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Cache Analytics shows how much of your site's traffic is served from Cloudflare's cache versus your origin server. When content is served from cache, visitors get faster page loads and your origin web server handles less traffic. Use Cache Analytics to identify resources that are [missing from cache](/cache/concepts/cache-responses/#miss), [expired](/cache/concepts/cache-responses/#expired) (cached copy is outdated), or [ineligible for caching](/cache/concepts/cache-responses/#noneunknown) (not eligible for caching). You can filter by hostname, review the top URLs that miss cache, and query up to three days of data.
 
@@ -19,7 +18,7 @@ Cache Analytics shows how much of your site's traffic is served from Cloudflare'
 
 In the Cloudflare dashboard, go to the **Caching** page.
 
-   <DashButton url="/?to=/:account/:zone/caching" />
+<DashButton url="/?to=/:account/:zone/caching" />
 
 ## Requests vs Data Transfer
 
diff --git a/src/content/docs/cache/performance-review/cache-performance.mdx b/src/content/docs/cache/performance-review/cache-performance.mdx
index 528344752e6ef3d..9e4e9ebc7569a11 100644
--- a/src/content/docs/cache/performance-review/cache-performance.mdx
+++ b/src/content/docs/cache/performance-review/cache-performance.mdx
@@ -24,7 +24,6 @@ Depending on the [cache status](/cache/concepts/cache-responses/) you receive, y
 Use [Cache Analytics](/cache/performance-review/cache-analytics/) to identify cache performance issues. The following examples show how to filter for common problems and resolve them.
 
 - Not caching HTML.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Dynamic**.
   - Resolution: Set a Cloudflare Cache Rule to [cache dynamic content](/cache/how-to/cache-rules/examples/cache-everything/).
 
@@ -35,14 +34,12 @@ This option caches all HTML regardless of the presence of dynamic content (conte
 - Checking for the presence of a cookie.
 - Excluding requests that match known dynamic content file paths.
 - Excluding requests with dynamic content extensions (or no extension).
-:::
+  :::
 
 - Short cache expiration TTL.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Revalidated**.
   - Resolution: [Increase Cloudflare's Edge Cache TTL via a Cache Rule](/cache/how-to/cache-rules/examples/edge-ttl/).
 
 - Need to enable Tiered Cache or custom cache key.
-
   - Identify the issue: Select **Add filter** and select **Cache status equals Miss**.
   - Resolution: [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) or [create a custom cache key](/cache/how-to/cache-rules/examples/custom-cache-key/).
diff --git a/src/content/docs/cache/performance-review/index.mdx b/src/content/docs/cache/performance-review/index.mdx
index 62a5b788d098027..b2b00f57fe7dfb6 100644
--- a/src/content/docs/cache/performance-review/index.mdx
+++ b/src/content/docs/cache/performance-review/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 8
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use Cache Analytics to understand how effectively Cloudflare caches your content, and apply optimization techniques to improve your cache hit ratio and reduce origin server load.
 
diff --git a/src/content/docs/cache/plans.mdx b/src/content/docs/cache/plans.mdx
index e8f54313de37f9f..a4543e9bf53afe7 100644
--- a/src/content/docs/cache/plans.mdx
+++ b/src/content/docs/cache/plans.mdx
@@ -10,13 +10,12 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="cache" />
\ No newline at end of file
+<ProductFeatures id="cache" />
diff --git a/src/content/docs/cache/reference/cdn-reference-architecture.mdx b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
index 4681ed5552d3aa6..145f83c1cb84f3c 100644
--- a/src/content/docs/cache/reference/cdn-reference-architecture.mdx
+++ b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
@@ -5,5 +5,4 @@ products:
   - cache
 title: CDN Reference Architecture
 external_link: /reference-architecture/architectures/cdn/
-
 ---
diff --git a/src/content/docs/cache/reference/development-mode.mdx b/src/content/docs/cache/reference/development-mode.mdx
index c6f9d879d1f7baf..417c841881601c5 100644
--- a/src/content/docs/cache/reference/development-mode.mdx
+++ b/src/content/docs/cache/reference/development-mode.mdx
@@ -4,16 +4,15 @@ pcx_content_type: how-to
 description: Bypass the cache temporarily with Development Mode.
 products:
   - cache
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript.
 
 :::note
 
-To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache). 
+To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache).
 :::
 
 ## Enable Development Mode
diff --git a/src/content/docs/cache/reference/index.mdx b/src/content/docs/cache/reference/index.mdx
index 57aa94f03cf5680..fa4c9cb8953cc15 100644
--- a/src/content/docs/cache/reference/index.mdx
+++ b/src/content/docs/cache/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the reference content to learn more about specific caching functionality.
 
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx
index c5011e04ae13af4..bd25e5e49df3439 100644
--- a/src/content/docs/cache/troubleshooting/always-online.mdx
+++ b/src/content/docs/cache/troubleshooting/always-online.mdx
@@ -36,16 +36,13 @@ Always Online does not trigger for HTTP response codes such as [404](/support/tr
 ## Frequently asked questions
 
 1. How can I know if a page has been crawled?
-
    - You can go to the [Internet Archive](https://web.archive.org/) and search for the page URL to see if it has been crawled or not.
    - You can also check this via the [Internet Archive Availability API](https://archive.org/help/wayback_api.php).
 
 2. Why were not pages x, y, and z crawled?
-
    - Since Cloudflare only requests to crawl the most popular pages on the site, it is possible that there will be missing pages. If you really want to archive a page, then you can visit the [Internet Archive](https://web.archive.org/save) save page and ask them to crawl a particular page.
 
 3. What IP addresses do we need to allowlist to make sure crawling works?
-
    - IP Range: `207.241.224.0/20` and `208.70.24.0/21`. Note that this ip range belongs to Internet Archive and NOT Cloudflare, since it is the Internet Archive that does the crawling.
 
 4. What user agent should the origin expect to see?
diff --git a/src/content/docs/cache/troubleshooting/index.mdx b/src/content/docs/cache/troubleshooting/index.mdx
index 6d019d87491a048..43a1ccb36799ea9 100644
--- a/src/content/docs/cache/troubleshooting/index.mdx
+++ b/src/content/docs/cache/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The following topics are useful for troubleshooting Cache issues.
 
diff --git a/src/content/docs/china-network/concepts/global-acceleration.mdx b/src/content/docs/china-network/concepts/global-acceleration.mdx
index d5cf13877556bdc..65a11d18c9950e0 100644
--- a/src/content/docs/china-network/concepts/global-acceleration.mdx
+++ b/src/content/docs/china-network/concepts/global-acceleration.mdx
@@ -30,14 +30,14 @@ Organizations that serve content or connect employees in Mainland China face con
 
 Global Acceleration can support the following scenarios:
 
-| Service                                                                                 | Scenario                                                            |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
+| Service                                                                                 | Scenario                                                                                           |
+| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
 | [CDN Global Acceleration](#cdn-global-acceleration)                                     | Improved performance for dynamic content (API responses, personalized pages) on China Network CDN. |
-| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                       |
-| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                              |
-| [ICP](#icp-services)                                                                    | China Network prerequisite.                                         |
-| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                       |
-| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China. |
+| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                                                      |
+| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                                                             |
+| [ICP](#icp-services)                                                                    | China Network prerequisite.                                                                        |
+| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                                                      |
+| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China.                  |
 
 ## CDN Global Acceleration
 
diff --git a/src/content/docs/china-network/reference/available-products.mdx b/src/content/docs/china-network/reference/available-products.mdx
index f5ba030c4d27bda..0ae2911eaa5b486 100644
--- a/src/content/docs/china-network/reference/available-products.mdx
+++ b/src/content/docs/china-network/reference/available-products.mdx
@@ -37,7 +37,7 @@ The following products and features are available on the Cloudflare China Networ
 | [R2](/r2/)[^3]                                                            | Object storage for all your data.                                                                                                                  |
 | [Assets](/workers/static-assets/)                                         | Upload static assets (HTML, CSS, images and other files) as part of your Worker — Cloudflare will handle caching and serving them to web browsers. |
 | [Environment variables](/workers/configuration/environment-variables/)    | Attach text strings or JSON values to your Worker.                                                                                                 |
-| [Images](/images/optimization/transformations/bindings/)[^4]                          | Store, transform, optimize, and deliver images at scale.                                                                                           |
+| [Images](/images/optimization/transformations/bindings/)[^4]              | Store, transform, optimize, and deliver images at scale.                                                                                           |
 | [mTLS](/workers/runtime-apis/bindings/mtls/)                              | Securely connect to backend servers over [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).                        |
 | [Rate Limiting](/workers/runtime-apis/bindings/rate-limit/)               | Define rate limits and write code around them in your Worker.                                                                                      |
 | [Secrets](/workers/configuration/secrets/)                                | Attach encrypted text values to your Worker.                                                                                                       |
diff --git a/src/content/docs/client-ip-geolocation/about/index.mdx b/src/content/docs/client-ip-geolocation/about/index.mdx
index 28a8f360c648938..eeb0a5dfa94995f 100644
--- a/src/content/docs/client-ip-geolocation/about/index.mdx
+++ b/src/content/docs/client-ip-geolocation/about/index.mdx
@@ -10,10 +10,8 @@ description: Learn how Cloudflare Firewall Rules work.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 Cloudflare Client IP Geolocation helps you understand where in the world a given client is located, even if their true client IP address is obscured by Cloudflare's proxy systems. We offer this service to ensure customers have high-quality experiences interacting with origins that rely on geolocation — such as mapping providers — and origin operators can deliver the right content to the right users. Ensuring origins know where clients are located avoids problems associated with traditional VPNs that obscure a consumer’s geolocation and allow circumvention of geographic restrictions on content.
@@ -30,7 +28,7 @@ If a VPN user tries to use an interposed VPN or proxy system that attempts to hi
 
 ## Technical explanation
 
-We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like *MaxMind*, *IP 2 Location*, and *Neustar*.
+We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like _MaxMind_, _IP 2 Location_, and _Neustar_.
 
 When Cloudflare receives an inbound request from a WARP or 1.1.1.1 user, we first geolocate the IP address that made the connection to Cloudflare. Then, we select an egress IP that maps to the client geolocation. We then discard Client IP information to preserve user privacy but return their true geographic location.
 
diff --git a/src/content/docs/client-ip-geolocation/faq/index.mdx b/src/content/docs/client-ip-geolocation/faq/index.mdx
index c7687b23fc2d865..85a00673fec5ea2 100644
--- a/src/content/docs/client-ip-geolocation/faq/index.mdx
+++ b/src/content/docs/client-ip-geolocation/faq/index.mdx
@@ -10,10 +10,8 @@ description: Answers to common questions.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 ## Website operators
diff --git a/src/content/docs/client-ip-geolocation/get-started.mdx b/src/content/docs/client-ip-geolocation/get-started.mdx
index 7bfddd2706bc177..f6115e8f83f2b6f 100644
--- a/src/content/docs/client-ip-geolocation/get-started.mdx
+++ b/src/content/docs/client-ip-geolocation/get-started.mdx
@@ -10,18 +10,16 @@ description: Set up Client IP Geolocation for your network.
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 There are several things you can do to best handle traffic from Cloudflare VPN and forward-proxy users:
 
-* **Origin operators**:
-  * Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
-  * To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
-* **Geolocation data providers**:
-  * Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
-* **Users of WARP and 1.1.1.1**:
-  * Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
+- **Origin operators**:
+  - Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
+  - To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
+- **Geolocation data providers**:
+  - Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
+- **Users of WARP and 1.1.1.1**:
+  - Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
diff --git a/src/content/docs/client-ip-geolocation/index.mdx b/src/content/docs/client-ip-geolocation/index.mdx
index 5464f9a0cb448ee..bd7c326b3032781 100644
--- a/src/content/docs/client-ip-geolocation/index.mdx
+++ b/src/content/docs/client-ip-geolocation/index.mdx
@@ -11,27 +11,27 @@ products:
 description: Add geolocation data for clients behind Cloudflare proxies.
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 :::note
 
-
 Client IP Geolocation is currently in closed Beta testing.
 
-
 :::
 
 Cloudflare designed [Cloudflare WARP](/warp-client/) and [1.1.1.1](/1.1.1.1/) to make Internet browsing more private and secure. These applications encrypt last-mile connections and make it more difficult for others to use client IP addresses in user fingerprinting.
 
 However, unlike legacy VPN applications, we never designed WARP or 1.1.1.1 to hide user locations or allow users to misrepresent their true geographic location. As a web property operator, you can use **Client IP Geolocation** to map Cloudflare egress IP addresses to specific geolocations.
 
- <LinkButton variant="primary" href="/client-ip-geolocation/get-started/">Get started</LinkButton> <LinkButton variant="secondary" href="/client-ip-geolocation/about/">Learn more</LinkButton>
-
+<LinkButton variant="primary" href="/client-ip-geolocation/get-started/">
+	Get started
+</LinkButton>
+<LinkButton variant="secondary" href="/client-ip-geolocation/about/">
+	Learn more
+</LinkButton>
 
 :::note
 
-
 Client IP Geolocation is different from the [Cloudflare IP Geolocation setting](/network/ip-geolocation/), which helps you capture country codes for visitors.
 
-
 :::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
index c3af18280364b77..e8e7c1e8e6a9464 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
@@ -214,4 +214,4 @@ The custom error token provides diagnostic information or specific functionality
     </html>
   ```
   </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
index 82759d6a2395e0b..a5b7daf4949db75 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
@@ -29,4 +29,4 @@ fetch("/my-api-endpoint").then((response) => {
 		// Process response as usual
 	}
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
index bc5eb92be6854f4..6c07e3d158b50d9 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
@@ -56,4 +56,4 @@ To ensure your API calls are protected without breaking single-page applications
 
 By enabling Pre-clearance, the Turnstile widget issues a persistent clearance cookie (`cf_clearance`) upon successful human verification on an initial HTML page. This cookie pre-clears the visitor to interact with sensitive API endpoints secured by WAF rules, allowing you to deploy granular security without forcing a disruptive Challenge Page response.
 
-For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
\ No newline at end of file
+For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
index ca4edef555c115d..9f1f938bab49aa4 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
@@ -19,4 +19,4 @@ When observing a Cloudflare Challenge page, a visitor could:
 
 :::note
 Visitors must enable JavaScript and cookies on their browser to be able to pass any type of Challenge.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
index 5ccae5620b19ca2..e0f3d123a4bb4d7 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on available challenge types:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
index 3a4bd64156f9af5..5c15a8df1753eff 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
@@ -16,7 +16,7 @@ Turnstile differs from Challenges Pages in that the challenge does not pause the
 
 In most cases, nothing further is required from the visitor. However, if necessary, Turnstile may display a simple checkbox that the visitor must click to proceed.
 
-After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions. 
+After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions.
 
 <Render file="siteverify-warning" product="turnstile" />
 
@@ -26,20 +26,18 @@ While there are three types of widgets that you can choose to implement on your
 
 - **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a challenge based on the signals gathered from the visitor's browser and presents an interaction only if it detects potentially automated traffic.
 
-- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity. 
+- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity.
 
 - **Invisible**: The widget is completely invisible to the visitor, but the challenge still runs in the background.
 
   :::note[Link to Cloudflare's Turnstile Privacy Policy]
-  <Render
-    file="privacy-policy"
-    product="turnstile"
-  />
+
+  <Render file="privacy-policy" product="turnstile" />
   :::
 
 ## Implementation
 
-When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey. 
+When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey.
 
 The sitekey is used with [client-side rendering](/turnstile/get-started/client-side-rendering/#implicitly-render-the-turnstile-widget) by adding it to the `<div>` container placeholder. You will then place that `<div>` code snippet where you want to add the widget to your site page or form.
 
diff --git a/src/content/docs/cloudflare-challenges/concepts/index.mdx b/src/content/docs/cloudflare-challenges/concepts/index.mdx
index 8587e3ba1d8f3f0..181b5dfde7eb724 100644
--- a/src/content/docs/cloudflare-challenges/concepts/index.mdx
+++ b/src/content/docs/cloudflare-challenges/concepts/index.mdx
@@ -7,11 +7,11 @@ products:
 sidebar:
   order: 2
   label: About
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on how challenges work:
 
diff --git a/src/content/docs/cloudflare-challenges/index.mdx b/src/content/docs/cloudflare-challenges/index.mdx
index b1612b44767b991..08083dc2ca79e13 100644
--- a/src/content/docs/cloudflare-challenges/index.mdx
+++ b/src/content/docs/cloudflare-challenges/index.mdx
@@ -11,7 +11,8 @@ sidebar:
 import { Render, Description, Plan, RelatedProduct } from "~/components";
 
 <Description>
-	Challenges are security mechanisms used by Cloudflare to verify whether a visitor to your site is a real human and not a bot or automated script.
+	Challenges are security mechanisms used by Cloudflare to verify whether a
+	visitor to your site is a real human and not a bot or automated script.
 </Description>
 
 When a Challenge is issued, Cloudflare asks the browser to perform a series of checks that help confirm the visitor's legitimacy. This process involves evaluating client-side signals (data gathered from the visitor's browser environment) or asking a visitor to take minimal action such as checking a box or selecting a button.
diff --git a/src/content/docs/cloudflare-challenges/reference/index.mdx b/src/content/docs/cloudflare-challenges/reference/index.mdx
index 3c0a6f05993d737..fe3f9e06287d1c6 100644
--- a/src/content/docs/cloudflare-challenges/reference/index.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group: 
+  group:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Cloudflare Challenges:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
index a8b394b4c4b0410..d5d5ad31165401a 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
@@ -8,45 +8,43 @@ sidebar:
   order: 4
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
-Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge. 
+Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge.
 
-Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of. 
+Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of.
 
 ## Overview
 
-Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis. 
+Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis.
 
 ### Supported browsers
 
 The following browsers are officially supported and tested.
 
 <Details header="Google Chrome (desktop and mobile)">
-  - Current version and two previous major versions
-  - Chromium-based browsers and Chromium-based browsers that track the current Chrome stable version
-  
-  :::caution
-  Beta, Dev, Canary, Nightly, or other unreleased builds are not officially supported.
-  :::
+	- Current version and two previous major versions - Chromium-based browsers
+	and Chromium-based browsers that track the current Chrome stable version
+	:::caution Beta, Dev, Canary, Nightly, or other unreleased builds are not
+	officially supported. :::
 </Details>
 
 <Details header="Mozilla Firefox">
-  - Current version and two previous major versions
-  - Extended Support Release (ESR) versions are supported
+	- Current version and two previous major versions - Extended Support Release
+	(ESR) versions are supported
 </Details>
 
 <Details header="Safari">
-  - Current version and two previous major versions
-  - iOS Safari on current iOS version and two previous major versions
+	- Current version and two previous major versions - iOS Safari on current iOS
+	version and two previous major versions
 </Details>
 
 <Details header="Microsoft Edge">
-  - Current version and two previous major versions
-  </Details>
+	- Current version and two previous major versions
+</Details>
 
 <Details header="Samsung Internet Browser">
-  - Current version and two previous major versions
+	- Current version and two previous major versions
 </Details>
 
 ### Limited browser support
@@ -81,19 +79,19 @@ Browser extensions can interfere with challenges in several ways.
 - Browser automation tools are often detected as potential bots and may cause challenge failures.
 
 :::note
-If challenges consistently fail, try temporarily disabling extensions and reload the page. 
+If challenges consistently fail, try temporarily disabling extensions and reload the page.
 :::
 
 ### Device emulation and developer tools
 
 Challenges are designed to distinguish between real human users and automated traffic. When device emulation is enabled (such as through browser developer tools), it can trigger bot detection mechanisms.
 
-- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices. 
+- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices.
 - Developer tools may modify browser behavior or expose debugging information that changes how challenges operate.
 - Automation frameworks like Selenium, Puppeteer, or Playwright are specifically detected as non-human traffic.
 
 :::note
-For developers testing applications, we recommend using real devices rather than emulated environments when possible. 
+For developers testing applications, we recommend using real devices rather than emulated environments when possible.
 
 If you must use emulation, be aware that challenges may be more difficult to pass, and do not reflect the real experience on mobile devices.
 :::
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
index 3b3282d4adca332..c9c87ed0b0cddc3 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
@@ -12,30 +12,30 @@ sidebar:
 
 ## Multi-language support
 
-Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface. 
+Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface.
 
-For language support specific to Challenge Pages, refer to the table below. 
+For language support specific to Challenge Pages, refer to the table below.
 
-| Language                         | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
-| -------------------------------- | ----------------------------- | ----------------------------- |
-| Arabic (Egypt)                   | `ar-eg`                       | `ar`                          |
-| Chinese (Simplified, China)      | `zh-cn`                       | `zh`                          |
-| Chinese (Traditional, Taiwan)    | `zh-tw`                       | --                            |
-| Dutch (Netherlands)              | `nl-nl`                       | `nl`                          |
-| English (United States)          | `en-us`                       | `en`                          |
-| French (France)                  | `fr-fr`                       | `fr`                          |
-| German (Germany)                 | `de-de`                       | `de`                          |
-| Indonesian (Indonesia)           | `id-id`                       | `id`                          |
-| Italian (Italy)                  | `it-it`                       | `it`                          |
-| Japanese (Japan)                 | `ja-jp`                       | `ja`                          |
-| Korean (Korea)                   | `ko-kr`                       | `ko`                          |
-| Persian                          |  --                           | `fa`
-| Polish (Poland)                  | `pl-pl`                       | `pl`                          |
-| Portuguese (Brazil)              | `pt-br`                       | `pt`                          |
-| Russian (Russia)                 | `ru-ru`                       | `ru`                          |
-| Spanish (Spain)                  | `es-es`                       | `es`                          |
-| Turkish (Turkey)                 | `tr-tr`                       | `tr`                          |
+| Language                      | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
+| ----------------------------- | ----------------------------- | ----------------------------- |
+| Arabic (Egypt)                | `ar-eg`                       | `ar`                          |
+| Chinese (Simplified, China)   | `zh-cn`                       | `zh`                          |
+| Chinese (Traditional, Taiwan) | `zh-tw`                       | --                            |
+| Dutch (Netherlands)           | `nl-nl`                       | `nl`                          |
+| English (United States)       | `en-us`                       | `en`                          |
+| French (France)               | `fr-fr`                       | `fr`                          |
+| German (Germany)              | `de-de`                       | `de`                          |
+| Indonesian (Indonesia)        | `id-id`                       | `id`                          |
+| Italian (Italy)               | `it-it`                       | `it`                          |
+| Japanese (Japan)              | `ja-jp`                       | `ja`                          |
+| Korean (Korea)                | `ko-kr`                       | `ko`                          |
+| Persian                       | --                            | `fa`                          |
+| Polish (Poland)               | `pl-pl`                       | `pl`                          |
+| Portuguese (Brazil)           | `pt-br`                       | `pt`                          |
+| Russian (Russia)              | `ru-ru`                       | `ru`                          |
+| Spanish (Spain)               | `es-es`                       | `es`                          |
+| Turkish (Turkey)              | `tr-tr`                       | `tr`                          |
 
 ### Turnstile language support
 
-For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
\ No newline at end of file
+For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
diff --git a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
index d9da862f3207f6c..0403f66ba3ed126 100644
--- a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
@@ -8,10 +8,9 @@ tags:
   - Debugging
 sidebar:
   order: 2
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Challenge loops
 
@@ -35,6 +34,6 @@ Ensure your browser is updated to the latest version to maintain compatibility.
 
 Follow the steps below to ensure that your environment is properly configured.
 
-<Render file="troubleshooting-steps" product="turnstile"/>
+<Render file="troubleshooting-steps" product="turnstile" />
 
 If none of the above resolves your issue, contact the website administrator with the [error code](/turnstile/troubleshooting/client-side-errors/error-codes/) and Ray ID or submit a [feedback report](/turnstile/troubleshooting/feedback-reports/) through the Turnstile widget by selecting **Submit Feedback**.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
index 360ff1b151ff9d5..7ff0b1bb50a2ea4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
@@ -9,20 +9,19 @@ sidebar:
 head:
   - tag: title
     content: Backoff schedule | Hostname validation
-
 ---
 
 After you create a custom hostname, Cloudflare has to [validate that hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/).
 
 Attempts to validate a Custom Hostname are distributed over seven days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
 
-* For the first 10 attempts:
+- For the first 10 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.05, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
 ```
 
-* For the remaining 65 attempts:
+- For the remaining 65 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.15, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
index 3583929fa75cde3..e53e217ee14dd51 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Error codes - Custom Hostname Validation
-
 ---
 
 When you [validate a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/), you might encounter the following error codes.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
index 4e23151ad107b4f..12b2229cd3ba429 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Pre-validation methods - Custom Hostname Validation
-
 ---
 
 Pre-validation methods help verify domain ownership before your customer's traffic is proxying through Cloudflare.
@@ -30,10 +29,8 @@ TXT validation is when your customer adds a `TXT` record to their authoritative
 
 :::note
 
-
 If your customer cannot update their authoritative DNS, you could also use [HTTP validation](#http-tokens).
 
-
 :::
 
 To set up `TXT` validation:
@@ -42,21 +39,23 @@ To set up `TXT` validation:
 
    ```json null {11-12}
    {
-   "result": [
-       {
-       "id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
-       "hostname": "app.example.com",
-       // ...
-       "status": "pending",
-       "verification_errors": ["custom hostname does not CNAME to this zone."],
-       "ownership_verification": {
-           "type": "txt",
-           "name": "_cf-custom-hostname.app.example.com",
-           "value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
-       },
-       "created_at": "2020-03-04T19:04:02.705068Z"
-       }
-   ]
+   	"result": [
+   		{
+   			"id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
+   			"hostname": "app.example.com",
+   			// ...
+   			"status": "pending",
+   			"verification_errors": [
+   				"custom hostname does not CNAME to this zone."
+   			],
+   			"ownership_verification": {
+   				"type": "txt",
+   				"name": "_cf-custom-hostname.app.example.com",
+   				"value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
+   			},
+   			"created_at": "2020-03-04T19:04:02.705068Z"
+   		}
+   	]
    }
    ```
 
@@ -82,18 +81,18 @@ To get and use the `ownership_verification` record:
 
    ```json title="Example response (truncated)" {8-9}
    {
-     "result": [
-       {
-         "id": "24c8c68e-bec2-49b6-868e-f06373780630",
-         "hostname": "app.example.com",
-         // ...
-         "ownership_verification_http": {
-             "http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
-             "http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
-         },
-         "created_at": "2020-03-04T20:06:04.117122Z"
-       }
-     ]
+   	"result": [
+   		{
+   			"id": "24c8c68e-bec2-49b6-868e-f06373780630",
+   			"hostname": "app.example.com",
+   			// ...
+   			"ownership_verification_http": {
+   				"http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
+   				"http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
+   			},
+   			"created_at": "2020-03-04T20:06:04.117122Z"
+   		}
+   	]
    }
    ```
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
index 37075f00034342b..4cc01d36fb14628 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
@@ -15,7 +15,7 @@ description: Learn how to move hostnames between different zones.
 
 As a SaaS provider, you may want, or have, multiple zones to manage hostnames. Each zone can have different configurations or origins, as well as correlate to varying products. You might shift custom hostnames between zones to enable or disable certain features. Cloudflare allows migration within the same account through the steps below:
 
-***
+---
 
 ## CNAME
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
index 9623b2a72514ec3..3c056f32553e457 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
@@ -11,7 +11,7 @@ sidebar:
   order: 7
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can use custom hostname analytics for two general purposes: exploring how your customers use your product and sharing the benefits provided by Cloudflare with your customers.
 
@@ -19,19 +19,17 @@ These analytics include **Site Analytics**, **Bot Analytics**, **Cache Analytics
 
 :::note
 
-
 The plan of your Cloudflare for SaaS application determines the analytics available for your custom hostnames.
 
-
 :::
 
 ## Explore customer usage
 
 Use custom hostname analytics to help your organization with billing and infrastructure decisions, answering questions like:
 
-* "How many total requests is your service getting?"
-* "Is one customer transferring significantly more data than the others?"
-* "How many global customers do you have and where are they distributed?"
+- "How many total requests is your service getting?"
+- "Is one customer transferring significantly more data than the others?"
+- "How many global customers do you have and where are they distributed?"
 
 If you see one customer is using more data than another, you might increase their bill. If requests are increasing in a certain geographic region, you might want to increase the origin servers in that region.
 
@@ -41,9 +39,9 @@ To access custom hostname analytics, either [use the dashboard](/analytics/faq/a
 
 With custom hostname analytics, you can also share site information with your customers, including data about:
 
-* How many pageviews their site is receiving.
-* Whether their site has a large percentage of bot traffic.
-* How fast their site is.
+- How many pageviews their site is receiving.
+- Whether their site has a large percentage of bot traffic.
+- How fast their site is.
 
 Build custom dashboards to share this information by specifying an individual custom hostname in `clientRequestHTTPHost` field of [any dataset](/analytics/graphql-api/features/data-sets/) that includes this field.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
index 55fbfb5650d6322..5e86134809b77f7 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
@@ -6,7 +6,6 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Argo Smart Routing uses real-time global network information to route traffic on the fastest possible path across the Internet. Regardless of geographic location, this allows Cloudflare to optimize routing to make it faster, more reliable, and more secure. As a SaaS provider, you may want to emphasize the quickest traffic delivery for your end customers. To do so, [enable Argo Smart Routing](/argo-smart-routing/get-started/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
index 16b0b87aaa5f035..9b9a27e309eb3ba 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
@@ -6,7 +6,6 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Cloudflare makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers. Content can be either static or dynamic: static content is “cacheable” or eligible for caching, and dynamic content is “uncacheable” or ineligible for caching. The cached copies of content are stored physically closer to users, optimized to be fast, and do not require recomputing.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
index 439f92b92dc27a1..74ec34298a49532 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
@@ -12,13 +12,13 @@ import { APIRequest } from "~/components";
 
 [Early Hints](/cache/advanced-configuration/early-hints/) allows the browser to begin loading resources while the origin server is compiling the full response. This improves webpage’s loading speed for the end user. As a SaaS provider, you may prioritize speed for some of your custom hostnames. Using custom metadata, you can [enable Early Hints](/cache/advanced-configuration/early-hints/#enable-early-hints) per custom hostname.
 
-***
+---
 
 ## Prerequisites
 
 Before you can employ Early Hints for SaaS, you need to create a custom hostname. Review [Get Started with Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) if you have not already done so.
 
-***
+---
 
 ## Enable Early Hints per custom hostname via the API
 
@@ -29,51 +29,51 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
 3. If you are [creating a new custom hostname](/api/resources/custom_hostnames/methods/create/), make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames"
-  method="POST"
-  json={{
-		"hostname": "<CUSTOM_HOSTNAME>",
-		"ssl": {
-			"method": "http",
-			"type": "dv",
-			"settings": {
-				"http2": "on",
-				"min_tls_version": "1.2",
-				"tls_1_3": "on",
-				"early_hints": "on"
-				},
-				"bundle_method": "ubiquitous",
-				"wildcard": false
+	path="/zones/{zone_id}/custom_hostnames"
+	method="POST"
+	json={{
+		hostname: "<CUSTOM_HOSTNAME>",
+		ssl: {
+			method: "http",
+			type: "dv",
+			settings: {
+				http2: "on",
+				min_tls_version: "1.2",
+				tls_1_3: "on",
+				early_hints: "on",
 			},
+			bundle_method: "ubiquitous",
+			wildcard: false,
+		},
 	}}
 />
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames"
-  method="GET"
-  parameters={{
-		hostname:"{hostname}"
+	path="/zones/{zone_id}/custom_hostnames"
+	method="GET"
+	parameters={{
+		hostname: "{hostname}",
 	}}
 />
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
-  method="PATCH"
-  json={{
-		"ssl": {
-			"method": "http",
-			"type": "dv",
-			"settings": {
-				"http2": "on", // Note: These settings will be set to default if not included when updating early hints
-				"min_tls_version": "1.2",
-				"tls_1_3": "on",
-				"early_hints": "on"
-				}
+	path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+	method="PATCH"
+	json={{
+		ssl: {
+			method: "http",
+			type: "dv",
+			settings: {
+				http2: "on", // Note: These settings will be set to default if not included when updating early hints
+				min_tls_version: "1.2",
+				tls_1_3: "on",
+				early_hints: "on",
 			},
+		},
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
index 599383a86465771..1f00c930036f700 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
@@ -6,12 +6,11 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
-
 ---
 
 Cloudflare for SaaS allows you to deliver the best performance to your end customers by helping enable you to reduce latency through:
 
-* [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
-* [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
-* [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
-* By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
+- [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
+- [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
+- [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
+- By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
index beee8c46e86d55c..8e173849b2eee87 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-authorities/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
index 66293af0636f89f..0914ddfc956673d 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
index 2e40b6f99d15771..aaeb2fc1941b5f1 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
index c6b4665a4571939..b13a64d43827f6c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-and-hostname-priority/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
index 6b92b6171e4f460..8f572172a0a7569 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Custom Certificate Signing Requests
-
 ---
 
 ## Success codes
@@ -23,33 +22,33 @@ head:
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                        |
-| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                              |
-| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                             |
-| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                           |
-| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                             |
-| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                          |
-| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                      |
-| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                       |
-| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                      |
-| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                             |
-| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&*()=+{}[]                                                                                                                                       |
-| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                        |
-| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                          |
-| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                        |
-| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                  |
-| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                            |
-| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                        |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                       |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                            |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                       |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                           |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                  |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                              |
-| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                   |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                 |
+| ---------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                       |
+| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                          |
+| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                      |
+| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                                      |
+| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                                   |
+| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                               |
+| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                                |
+| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                               |
+| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                                      |
+| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&\*()=+{}[]                                                                                                                                                   |
+| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                 |
+| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                   |
+| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                                 |
+| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                           |
+| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                                     |
+| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                    |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                           |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                       |
+| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                    |
 | 403              | 1404           | Access to generating CSRs has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you. |
-| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                        |
-| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                  |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                |
+| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                 |
+| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                           |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
index e55d19e7fac4ad4..fc889f9bb826a89 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Status codes - Custom hostnames
-
 ---
 
-***
+---
 
 ## Success codes
 
@@ -24,66 +23,66 @@ head:
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | DELETE | 200 OK       |
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | PATCH  | 202 Accepted |
 
-***
+---
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                        |
-| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                 |
-| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                   |
-| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                         |
-| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                            |
-| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                 |
-| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                           |
-| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                            |
-| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                      |
-| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                     |
-| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                            |
-| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                        |
-| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                               |
-| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                     |
-| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                |
-| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                    |
-| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                  |
-| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                            |
-| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                             |
-| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                             |
-| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                             |
-| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                        |
-| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
-| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                   |
-| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                      |
-| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                        |
-| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                            |
-| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                     |
-| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                  |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                      |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                            |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                        |
-| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                |
-| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                           |
-| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid  customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
-| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                              |
-| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                               |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                          |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                          |
+| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                      |
+| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                |
+| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                  |
+| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                        |
+| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                           |
+| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                 |
+| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                |
+| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                          |
+| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                           |
+| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                     |
+| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                           |
+| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                    |
+| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                               |
+| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
+| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                 |
+| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                           |
+| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                            |
+| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                            |
+| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                       |
+| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                               |
+| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                      |
+| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                     |
+| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                       |
+| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                             |
+| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                           |
+| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                    |
+| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                    |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                           |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                       |
+| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                               |
+| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                          |
+| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
+| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                             |
+| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                              |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
index 51109dbc3c37bd3..7ecb44f98f46429 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When you perform [TXT](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/) domain control validation, you will need to share these tokens with your customers.
 
@@ -19,8 +18,9 @@ However, these tokens expire after a certain amount of time, depending on your c
 | --------------------- | -------------- |
 | Let's Encrypt         | 7 days         |
 | Google Trust Services | 14 days        |
-| SSL.com | 14 days        |
+| SSL.com               | 14 days        |
 
 :::caution
- <Render file="dcv-invalid-token-situations" product="ssl" />
+
+<Render file="dcv-invalid-token-situations" product="ssl" />
 :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
index 916488e61763006..b13acdc07c26874 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
@@ -32,13 +32,13 @@ Using a [TXT](#dns-txt-record) or [HTTP](#http-token) validation method helps yo
 
 #### DNS TXT Record
 
-When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership\_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
+When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
 
 #### HTTP Token
 
-When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership\_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
+When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
 
-Cloudflare sends GET requests to the http\_url using `User-Agent: Cloudflare Custom Hostname Verification`.
+Cloudflare sends GET requests to the http_url using `User-Agent: Cloudflare Custom Hostname Verification`.
 
 If you validated a hostname that is not proxying traffic through Cloudflare, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app when the HTTP token is verified (under the **Custom Hostnames** tab).
 
@@ -73,10 +73,8 @@ Once the migration has been started for your zone(s), Cloudflare will require ev
 
 :::note
 
-
 You can revert the migration at any time.
 
-
 :::
 
 ### Before the migration
@@ -85,15 +83,15 @@ Before your migration, you should:
 
 1. To test validation methods, set up a test zone and ask your account team to enable SSL for SaaS v2.
 2. Wait for your account team to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
-   * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
-   * `test_active`: Passed CNAME verification
-   * `test_active_apex`: Passed Apex Proxy verification
-   * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
-   * `test_failed`: Failed hostname verification 25 times
+   - `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
+   - `test_active`: Passed CNAME verification
+   - `test_active_apex`: Passed Apex Proxy verification
+   - `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
+   - `test_failed`: Failed hostname verification 25 times
 3. Review the results of our pre-migration tool (run by your account team) using one of the following methods:
-   * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
-   * Via a CSV file (provided by your account team)
-   * Via the Cloudflare dashboard:
+   - Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
+   - Via a CSV file (provided by your account team)
+   - Via the Cloudflare dashboard:
      ![Review SSL migration status in the dashboard](~/assets/images/cloudflare-for-platforms/ssl-migration-status.png)
 4. Approve the migration. Your account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
index edf8ce49e980942..2264ad62fa3dbc5 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Resources for SaaS customers
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare partners with many [SaaS providers](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/) to extend our performance and security benefits to your website.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
index 0681efe793946a6..63c9a0ce28c29a6 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
@@ -30,12 +30,12 @@ This is not an exhaustive list of Cloudflare products and features.
 | [China Network](/china-network/)                                                                    | No            | No                 |                                                                                                                                                                                                                                                                                                                                                                   |
 | [DNS](/dns/)                                                                                        | Yes\*         | Yes                | As a SaaS customer, do not remove the records related to your Cloudflare for SaaS setup.<br/><br/>Otherwise, your traffic will begin routing away from your SaaS provider.                                                                                                                                                                                        |
 | [HTTP/2 prioritization](https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/) | Yes           | Yes\*              | This feature must be enabled on the customer zone to function.                                                                                                                                                                                                                                                                                                    |
-| [Image resizing](/images/optimization/transformations/overview/)                                                         | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Image resizing](/images/optimization/transformations/overview/)                                    | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | IPv6                                                                                                | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [IPv6 Compatibility](/network/ipv6-compatibility/)                                                  | Yes           | Yes\*              | If the customer zone has **IPv6 Compatibility** enabled, generally the SaaS zone should as well.<br/><br/>If not, make sure the SaaS zone enables [Pseudo IPv4](/network/pseudo-ipv4/).                                                                                                                                                                           |
 | [Load Balancing](/load-balancing/)                                                                  | No            | Yes                | Customer zones can still use Load Balancing for non-O2O traffic.                                                                                                                                                                                                                                                                                                  |
 | [Page Rules](/rules/page-rules/)                                                                    | Yes\*         | Yes                | Page Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                                |
-| [Origin Rules](/rules/origin-rules/)                                                                | No           | Yes                |                                                                                                                                                                                                                                       |
+| [Origin Rules](/rules/origin-rules/)                                                                | No            | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Client-side security](/client-side-security/) (formerly Page Shield)                               | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Polish](/images/polish/)                                                                           | Yes\*         | Yes                | Polish only runs on cached assets. If the customer zone is bypassing cache for SaaS zone destined traffic, then images optimized by Polish will not be loaded from origin.                                                                                                                                                                                        |
 | [Rate Limiting](/waf/rate-limiting-rules/)                                                          | Yes\*         | Yes                | Rate Limiting rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
index 8f5c695a4ed8b46..cff52354c33fa79 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
@@ -31,9 +31,9 @@ Webflow customers can enable O2O on any Cloudflare zone plan.
 
 To enable O2O for a specific hostname within a Cloudflare Zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with your Webflow site name as the target. Webflow's domain addition setup will walk you through other validation steps.
 
-| Type    | Name                 | Target                | Proxy status |
-| ------- | -------------------- | --------------------- | ------------ |
-| `CNAME` | `<YOUR_DOMAIN>`      | `cdn.webflow.com`     | Proxied      |
+| Type    | Name            | Target            | Proxy status |
+| ------- | --------------- | ----------------- | ------------ |
+| `CNAME` | `<YOUR_DOMAIN>` | `cdn.webflow.com` | Proxied      |
 
 ## Zone hold
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
index 5f503f70abb253c..38885b976200c1e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
index 541ee92bd1ce3a3..335795eba693675 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Manage custom certificates
-
 ---
 
-import { Render, TabItem, Tabs } from "~/components"
+import { Render, TabItem, Tabs } from "~/components";
 
 Learn how to manage custom certificates for your Cloudflare for SaaS custom hostnames. For use cases and limitations, refer to [custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/).
 
@@ -86,7 +85,7 @@ To replace a single custom certificate within a certificate pack that contains t
 
 You can only replace an RSA certificate with another RSA certificate, or an ECDSA certificate with another ECDSA certificate.
 
-***
+---
 
 ## Move to a Cloudflare certificate
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
index 4a1ffdb4234511d..3b173935c952ce9 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
@@ -11,16 +11,15 @@ sidebar:
 head:
   - tag: title
     content: Delegated domain control validation (DCV)
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Delegated DCV allows SaaS providers to delegate the DCV process to Cloudflare.
 
 DCV Delegation requires your customers to place a one-time record at their authoritative DNS that allows Cloudflare to auto-renew all future certificate orders, so that there is no manual intervention from you or your customers at the time of the renewal.
 
-***
+---
 
 ## Setup
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
index 60f518c1628966e..e4cb716dca2b5d4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting | Certificate validation
-
 ---
 
 ## High-risk domains
@@ -20,7 +19,7 @@ Occasionally, a domain will be flagged as “high risk” by Cloudflare’s CA p
 
 If a domain is flagged by the CA, you need to contact Support before validation can finish. The API call will return indicating the failure, along with a link to where the ticket can be filed.
 
-***
+---
 
 ## Certificate Authority Authorization (CAA) records
 
@@ -44,26 +43,26 @@ In some cases, the validation may be prevented because your hostname points to a
 
 In this case you would need to either select a Certificate Authority whose CAA records are present at the target, or review the configuration with the service provider that owns the target.
 
-***
+---
 
 ## Time outs
 
 If a certificate issuance times out, the error message will indicate where the timeout occurred:
 
-* Timed Out (Initializing)
-* Timed Out (Validation)
-* Timed Out (Issuance)
-* Timed Out (Deployment)
-* Timed Out (Deletion)
+- Timed Out (Initializing)
+- Timed Out (Validation)
+- Timed Out (Issuance)
+- Timed Out (Deployment)
+- Timed Out (Deletion)
 
 To fix this error, send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) through the API or select **Refresh** for the specific custom hostname in the dashboard. If using the API, make sure that the `--data` field contains an `ssl` object with the same `method` and `type` as the original request.
 
 If these return an error, delete and recreate the custom hostname.
 
-***
+---
 
 ## Immediate validation checks
 
 You can send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) to request an immediate validation check on any certificate. The PATCH data should include the same `ssl` object as the original request.
 
-***
+---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
index 3545c355b84844b..7ac9fd652e89438 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 5
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 When you [create a webhook notification](/notifications/get-started/configure-webhooks/) for **SSL for SaaS Custom Hostnames**, you may want to automate responses to specific events (certificate issuance, failed validation, etc.).
 
@@ -26,38 +26,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.validation.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.validation.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -67,49 +67,49 @@ Cloudflare sends this alert each time a certificate remains in a `pending_valida
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.validation.failed",
-      "created_at": "2018-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_validation",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "blog.example.com reported as potential risk: google_safe_browsing"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.validation.failed",
+			"created_at": "2018-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_validation",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "blog.example.com reported as potential risk: google_safe_browsing"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate issuance
 
@@ -121,38 +121,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.issuance.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.issuance.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -162,49 +162,49 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.issuance.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "caa_error: blog.example.com"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.issuance.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "caa_error: blog.example.com"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate deployment
 
@@ -216,38 +216,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_dep
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deployment.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "active",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deployment.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "active",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -257,42 +257,42 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deployment.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deployment.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate deletion
 
@@ -302,34 +302,34 @@ Cloudflare sends this alert when certificates move from a status of `pending_del
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deletion.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "deleted"
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deletion.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "deleted"
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -339,38 +339,38 @@ Cloudflare sends this alert each time a certificate remains in status of `pendin
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.deletion.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deletion"
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.deletion.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deletion"
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
-***
+---
 
 ## Certificate renewal
 
@@ -382,43 +382,43 @@ The actions that you need to perform to renew certificates depend on your [valid
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "status": "active",
-      "hosts": ["blog.example.com"],
-      "issuer": "DigiCertInc",
-      "serial_number": "1001172778337169491",
-      "signature": "ECDSAWithSHA256",
-      "uploaded_on": "2021-11-17T04:33:54.561747Z",
-      "expires_on": "2022-11-21T12:00:00Z",
-      "custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"status": "active",
+			"hosts": ["blog.example.com"],
+			"issuer": "DigiCertInc",
+			"serial_number": "1001172778337169491",
+			"signature": "ECDSAWithSHA256",
+			"uploaded_on": "2021-11-17T04:33:54.561747Z",
+			"expires_on": "2022-11-21T12:00:00Z",
+			"custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -428,38 +428,38 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.succeeded",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_deployment",
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.succeeded",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_deployment",
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -469,45 +469,45 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-  "metadata": {
-    "event": {
-      "id": "<<WEBHOOK_ID>",
-      "type": "ssl.custom_hostname_certificate.renewal.failed",
-      "created_at": "2022-02-09T00:03:28.385080Z"
-    },
-    "account": {
-      "id": "<<ACCOUNT_ID>"
-    },
-    "zone": {
-      "id": "<<ZONE_ID>"
-    }
-  },
-  "data": {
-    "id": "<<CUSTOM_HOSTNAME_ID>",
-    "hostname": "blog.com",
-    "ssl": {
-      "id": "<<CERTIFICATE_ID>",
-      "type": "dv",
-      "method": "cname",
-      "status": "pending_issuance",
-      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-      "cname_target": "dcv.digicert.com",
-      "validation_errors": [
-        {
-          "message": "caa_error: blog.example.com"
-        }
-      ],
-      "settings": {
-        "min_tls_version": "1.2",
-        "http2": "on"
-      }
-    },
-    "custom_metadata": {
-      "key1": "value1",
-      "key2": "value2"
-    },
-    "custom_origin_server": "0001.blog.com"
-  }
+	"metadata": {
+		"event": {
+			"id": "<<WEBHOOK_ID>",
+			"type": "ssl.custom_hostname_certificate.renewal.failed",
+			"created_at": "2022-02-09T00:03:28.385080Z"
+		},
+		"account": {
+			"id": "<<ACCOUNT_ID>"
+		},
+		"zone": {
+			"id": "<<ZONE_ID>"
+		}
+	},
+	"data": {
+		"id": "<<CUSTOM_HOSTNAME_ID>",
+		"hostname": "blog.com",
+		"ssl": {
+			"id": "<<CERTIFICATE_ID>",
+			"type": "dv",
+			"method": "cname",
+			"status": "pending_issuance",
+			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+			"cname_target": "dcv.digicert.com",
+			"validation_errors": [
+				{
+					"message": "caa_error: blog.example.com"
+				}
+			],
+			"settings": {
+				"min_tls_version": "1.2",
+				"http2": "on"
+			}
+		},
+		"custom_metadata": {
+			"key1": "value1",
+			"key2": "value2"
+		},
+		"custom_origin_server": "0001.blog.com"
+	}
 }
 ```
 
@@ -521,6 +521,9 @@ This behavior is because each custom hostname can only have one certificate atta
 
 You can configure alerts to receive notifications for changes in your custom hostname certificates.
 
-<AvailableNotifications product="SSL/TLS" notificationFilter="SSL for SaaS Custom Hostnames Alert" />
+<AvailableNotifications
+	product="SSL/TLS"
+	notificationFilter="SSL for SaaS Custom Hostnames Alert"
+/>
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
index 79e692861ae83d3..dad31a4c49f6b78 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
@@ -6,13 +6,12 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
-
 ---
 
 Cloudflare for SaaS provides increased security per custom hostname through:
 
-* [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
-  * [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
-  * [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
-* Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
-* Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
+- [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
+  - [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
+  - [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
+- Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
+- Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
index a9b88bc6d3f027e..8c044e098c1a507 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
@@ -9,7 +9,7 @@ sidebar:
   label: Setup
 ---
 
-import { DashButton, APIRequest, } from "~/components";
+import { DashButton, APIRequest } from "~/components";
 
 [Web Application Firewall (WAF)](/waf/) allows you to create additional security measures through Cloudflare. As a SaaS provider, you can link custom rules, rate limiting rules, and managed rules to your custom hostnames. This provides more control to keep your domains safe from malicious traffic.
 
@@ -74,40 +74,38 @@ This assigns custom metadata to your custom hostname so that it has a security t
 2. Build your rules either [through the dashboard](/waf/custom-rules/create-dashboard/) or via the API. An example rate limiting rule, corresponding to `"security_level"` low, is shown below as an API call.
 
 <APIRequest
-  path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
-  method="PUT"
-  json={{
-		"rules": [
+	path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
+	method="PUT"
+	json={{
+		rules: [
 			{
-				"action": "block",
-				"ratelimit": {
-					"characteristics": [
-						"cf.colo.id",
-						"ip.src"
-					],
-					"period": 10,
-					"requests_per_period": 2,
-					"mitigation_timeout": 60
+				action: "block",
+				ratelimit: {
+					characteristics: ["cf.colo.id", "ip.src"],
+					period: 10,
+					requests_per_period: 2,
+					mitigation_timeout: 60,
 				},
-				"expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
-			}
-		]
+				expression:
+					'lookup_json_string(cf.hostname.metadata, "security_level") eq "low" and http.request.uri contains "login"',
+			},
+		],
 	}}
 	parameters={{
-		ruleset_phase: "http_ratelimit"
+		ruleset_phase: "http_ratelimit",
 	}}
 />
 
 To build rules through the dashboard:
 
-1. In the Cloudflare dashboard, go to the **WAF** page.
+1.  In the Cloudflare dashboard, go to the **WAF** page.
 
-		<DashButton url="/?to=/:account/application-security/waf" />
+        <DashButton url="/?to=/:account/application-security/waf" />
 
-2. Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
+2.  Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
 
-3. Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
+3.  Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
 
-   :::caution
-   This API call will replace any existing rate limiting rules in the zone.
-   :::
+    :::caution
+    This API call will replace any existing rate limiting rules in the zone.
+    :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
index 5f74db1bcc4eac2..44166be7219fb59 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /data-localization/how-to/cloudflare-for-saas/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
index b3bba3fd7a2c5ea..e385caf0bc3f783 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
@@ -55,9 +55,9 @@ You do not need to add individual Worker routes for each custom hostname. The wi
 
      For example, if your zone is `saasprovider.com` and you want `api.saasprovider.com` to bypass the Worker, create an additional route `api.saasprovider.com/*` with no Worker assigned. More specific routes take precedence over wildcard routes.
 
-    - **Route only custom hostname traffic to the Worker**:
-     - **Route**: `vanity.customer.com`
-     - **Worker**: Select the Worker used for your SaaS application.
+   - **Route only custom hostname traffic to the Worker**:
+   - **Route**: `vanity.customer.com`
+   - **Worker**: Select the Worker used for your SaaS application.
 
 5. Click **Save**.
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
index b5e1b4537b932f3..7c32801c1a98fdd 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
@@ -9,11 +9,13 @@ sidebar:
 products:
   - cloudflare-for-platforms
 ---
+
 import { Aside } from "@astrojs/starlight/components";
 
 When you deploy User Workers through Workers for Platforms, you can attach [bindings](/workers/runtime-apis/bindings/) to give them access to resources like [KV namespaces](/kv/), [D1 databases](/d1/), [R2 buckets](/r2/), and more. This enables your end customers to build more powerful applications without you having to build the infrastructure components yourself.
 
 With bindings, each of your users can have their own:
+
 - [KV namespace](/kv/) that they can use to store and retrieve data
 - [R2 bucket](/r2/) that they can use to store files and assets
 - [Analytics Engine](/analytics/analytics-engine/) dataset that they can use to collect observability data
@@ -26,9 +28,11 @@ Each User Worker can only access the bindings that are explicitly attached to it
 ![Resource Isolation Model](~/assets/images/reference-architecture/programmable-platforms/programmable-platforms-5.svg "Resource Isolation Model")
 
 ## Adding a KV Namespace to a User Worker
+
 This example walks through how to create a [KV namespace](/kv/) and attach it to a User Worker. The same process can be used to attach to other [bindings](/workers/runtime-apis/bindings/).
 
 ### 1. Create a KV namespace
+
 Create a KV namespace using the [Cloudflare API](/api/resources/kv/subresources/namespaces/methods/bulk_update/).
 
 ### 2. Attach the KV namespace to the User Worker
@@ -58,6 +62,7 @@ curl -X PUT \
   }' \
   -F 'worker.js=@/path/to/worker.js'
 ```
+
 Now, the User Worker has can access the `USER_KV` binding through the `env` argument using `env.USER_DATA.get()`, `env.USER_DATA.put()`, and other KV methods.
 
 Note: If you plan to add new bindings to the Worker, use the `keep_bindings` parameter to ensure existing bindings are preserved while adding new ones.
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
index 6a9982c4fc08bc4..9cdf87f9fd91826 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
@@ -31,7 +31,7 @@ A [Tail Worker](/workers/observability/logs/tail-workers/) receives information
 
 Use [Tail Workers](/workers/observability/logs/tail-workers/) instead of Logpush if you want granular control over formatting before logs are sent to their destination to receive [diagnostics channel events](/workers/runtime-apis/nodejs/diagnostics-channel), or if you want logs delivered in real-time.
 
-Adding a Tail Worker to  your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
+Adding a Tail Worker to your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
 
 ## Analytics
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
index b5f72ee55754ce1..a5d3d76bafe414b 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-for-platforms
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Script limits
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
index 4ed59262b2ebb15..c7998ff2541bb30 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
@@ -18,7 +18,7 @@ import {
 	ResourcesBySelector,
 } from "~/components";
 
-The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically. 
+The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically.
 
 ### Prerequisites
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
index 378810ebff4dd3e..4842b92536a2d6c 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
@@ -18,11 +18,11 @@ In untrusted mode:
 - Each Worker has an isolated cache, when using the [Cache API](/workers/runtime-apis/cache/) or when making subrequests using `fetch()`, which egress via [Cloudflare's cache](/cache/)
 - [`caches.default`](/workers/reference/how-the-cache-works/#cache-api) is disabled for all Workers in the namespace
 
-This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access. 
+This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access.
 
 ### Trusted Mode
 
-If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code. 
+If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code.
 
 In trusted mode:
 
@@ -31,9 +31,10 @@ In trusted mode:
 
 :::note
 In trusted mode, Workers can potentially access cached responses from other Workers in the namespace. Only enable this if you control all Worker code or have appropriate cache key isolation strategies.
-::: 
+:::
 
 To convert a namespace from untrusted to trusted:
+
 ```bash
 curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace_name}" \
   -H "Authorization: Bearer {api_token}" \
@@ -42,14 +43,16 @@ curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/
     "name": "{namespace_name}",
     "trusted_workers": true
   }'
-  ```
+```
 
-If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it. 
+If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it.
 
 ### Maintaining cache isolation in trusted mode
-If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
+
+If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys.
 
 ## Related Resources
-* [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
-* [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
-* [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
\ No newline at end of file
+
+- [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
+- [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
+- [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
diff --git a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
index 1d4db0fb3f37d82..c2bc163fbb4b639 100644
--- a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
+++ b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
@@ -12,7 +12,6 @@ sidebar:
 head:
   - tag: title
     content: Minimal suggested ruleset
-
 ---
 
 The suggested minimal ruleset blocks some known common vectors for DDoS attacks and permits all other ESP, TCP, UDP, GRE and ICMP traffic.
@@ -66,17 +65,17 @@ The information below covers traffic type, how the port is used, and reasons for
 
 The list below is a common list of traffic types you should also consider blocking or restricting inbound.
 
-* SFTP, TFTP
-* SSH, Telnet
-* RDP
-* RCP
-* SMCP
-* NTP
-  * Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
-* MS-SQL
-  * Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
-* HTTP and HTTPS
-  * If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
+- SFTP, TFTP
+- SSH, Telnet
+- RDP
+- RCP
+- SMCP
+- NTP
+  - Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
+- MS-SQL
+  - Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
+- HTTP and HTTPS
+  - If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
 
 If relevant to your environment, consider blocking based on geolocation data, which blocks traffic based on the country or user when an end user's IP address is registered in the geolocation database.
 
diff --git a/src/content/docs/cloudflare-network-firewall/index.mdx b/src/content/docs/cloudflare-network-firewall/index.mdx
index f5c445fd27e1de4..f546e7f0e9b2faa 100644
--- a/src/content/docs/cloudflare-network-firewall/index.mdx
+++ b/src/content/docs/cloudflare-network-firewall/index.mdx
@@ -20,8 +20,8 @@ import {
 } from "~/components";
 
 <Description>
-	Filter and block unwanted traffic at Cloudflare's global network,
-	before it reaches your infrastructure.
+	Filter and block unwanted traffic at Cloudflare's global network, before it
+	reaches your infrastructure.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
index 70c21d97f76d65a..53c0015446461f2 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
@@ -304,4 +304,4 @@ Due to the nature of Cloudflare network, your traffic may traverse various physi
 
 - Multiple PCAP Files: A single full PCAP capture may produce many small PCAP files, as a capture is taken for each physical server your traffic traverses in a Cloudflare location.
   - You can get more granular by applying packet-specific filters like protocol, port (and more) to target the traffic you need.
-- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
\ No newline at end of file
+- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
index 6f7330a2abce626..2ee588985ab4a4f 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
@@ -174,7 +174,7 @@ To start collecting packet captures with R2, you first need to configure it prop
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-	<DashButton url="/?to=/:account/r2/overview" />
+   <DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -218,4 +218,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
diff --git a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
index 190cc5e6da18dfa..1833bff8925d2c5 100644
--- a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
+++ b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
@@ -21,9 +21,9 @@ Traffic passing through Cloudflare's network is evaluated by several independent
 Each system operates independently. Traffic blocked by an earlier system never reaches later systems for evaluation.
 
 :::caution
-	Creating an allow rule in Network Firewall does **not** bypass DDoS
-	protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
-	rules, you must configure bypasses in those systems separately.
+Creating an allow rule in Network Firewall does **not** bypass DDoS
+protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
+rules, you must configure bypasses in those systems separately.
 :::
 
 To diagnose blocked traffic, use [Network Analytics](/analytics/network-analytics/) to identify which system is blocking the traffic and why. If Network Analytics does not provide enough information, you can use packet captures for deeper analysis.
@@ -99,4 +99,4 @@ If you cannot identify the issue from Network Analytics, use [packet captures](/
 - [Network Analytics](/analytics/network-analytics/)
 - [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/)
 - [Network Firewall rule configuration](/cloudflare-network-firewall/how-to/add-policies/)
-- [Packet captures](/cloudflare-network-firewall/packet-captures/)
\ No newline at end of file
+- [Packet captures](/cloudflare-network-firewall/packet-captures/)
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
index 24eaf60c6cf1b66..3b09b3e2ad4da6e 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
index db274e1c338cdc3..69fc5cb5e2e1111 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
@@ -7,7 +7,7 @@ title: Require Access protection
 sidebar:
   order: 3
 tags:
-- Security
+  - Security
 ---
 
 Cloudflare Access allows you to require Access protection for all hostnames in your account. When this setting is turned on, traffic to any hostname without a matching [Access application](/cloudflare-one/access-controls/applications/) is automatically blocked.
@@ -23,13 +23,13 @@ Turning on Access protection blocks traffic to any hostname that does not have a
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **Zero Trust** > **Access controls** > **Access settings**.
 2. Turn on **Block traffic to all domains in this account**. You will see a dialog confirming you understand the scope of this change. Select **Confirm**.
 
-	Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
+   Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
 
 3. (Optional) Under **Hostnames to Exempt**, select specific domains to exempt from the **Block traffic to all domains in this account** setting. Traffic to exempted hostnames is allowed even if no Access application exists.
 
-	:::note
-	Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
-	:::
+   :::note
+   Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
+   :::
 
 ## Allow traffic to a hostname
 
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
index d5cc04f026c092a..d74a4f8adf061e0 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
@@ -100,6 +100,7 @@ Users who match a policy configured with a _Same as application session timeout_
 When [Authenticate with Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/#configure-client-sessions-in-access) is enabled for an Access application, the Cloudflare One Client session duration takes precedence over all other session durations (application, policy, and global). As long as the Cloudflare One Client session is valid and the user is running the Cloudflare One Client, the user will not be prompted to re-authenticate with the IdP — even if the global session has expired.
 
 ### MFA session duration
+
 If you use [independent multi-factor authentication (MFA)](/cloudflare-one/access-controls/access-settings/independent-mfa/), the MFA session duration determines how long a user can log in to Cloudflare Access without being prompted for MFA. The MFA session is independent of the global, policy, and application session durations. When logging in to an Access app with [MFA enabled](/cloudflare-one/access-controls/policies/mfa-requirements/#configure-independent-mfa-for-an-application), users must complete an MFA challenge if their last MFA authentication falls outside the configured session duration. After authenticating with their identity provider, users are prompted for MFA. The [`CF_Device` cookie](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#cf_device) ensures both authentication steps occur on the same device. MFA session durations do not affect how long a user has access to the application (that is controlled by the [application token](#session-durations)).
 
 ### Order of enforcement
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
index 603b94d330906d6..f387963685b0849 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
index cfff5ab05a7f8ee..f4dd978b1db79a4 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
@@ -179,9 +179,9 @@ You can assign aliases to tools to give them clearer names in the portal. Aliase
 
 Aliases can be set at two levels:
 
-| Level | Field | Scope |
-| ----- | ----- | ----- |
-| **Server-level** | `alias` | Applies to the tool across all portals that include this server |
+| Level            | Field          | Scope                                                                                   |
+| ---------------- | -------------- | --------------------------------------------------------------------------------------- |
+| **Server-level** | `alias`        | Applies to the tool across all portals that include this server                         |
 | **Portal-level** | `portal_alias` | Applies only within this specific portal and takes priority over the server-level alias |
 
 When a tool has multiple names configured, the portal uses the following priority order: `portal_alias` > `server_alias` > `alias` > original tool name.
@@ -245,11 +245,11 @@ Unlike the dashboard, the API does not automatically create a DNS record for you
 
 The `auth_type` field accepts the following values:
 
-| Value | Description |
-| ----- | ----------- |
-| `oauth` | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
-| `bearer` | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`. |
-| `unauthenticated` | The server does not require authentication. |
+| Value             | Description                                                                                                                                          |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `oauth`           | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
+| `bearer`          | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`.                                                   |
+| `unauthenticated` | The server does not require authentication.                                                                                                          |
 
 ### Force sync an MCP server
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
index b342006708c137a..8b12f3259058db0 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
@@ -57,18 +57,18 @@ The payload contains the actual claim and user information to pass to the applic
 }
 ```
 
-| Field          | Description                                                                                                                                                                                                                                                                                     |
-| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                                    |
-| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                 |
-| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                             |
-| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                               |
-| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                           |
-| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                           |
-| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                       |
-| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                  |
+| Field          | Description                                                                                                                                                                                                                                                                                               |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                |
+| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                           |
+| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                                       |
+| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                                         |
+| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                                     |
+| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                                     |
+| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                                 |
+| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                            |
 | sub            | The ID of the user. This value is unique to an email address per account. The user would get a different `sub` if they are [removed](/cloudflare-one/team-and-resources/users/seat-management/#remove-a-user) and re-added to your Zero Trust organization, or if they log into a different organization. |
-| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                  |
+| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                            |
 
 #### Custom SAML attributes and OIDC claims
 
@@ -86,26 +86,26 @@ curl -H 'cookie: CF_Authorization=<user-token>' https://<your-team-name>.cloudfl
 
 Access will return a JSON structure containing the following data:
 
-| Field                | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| email                | The email address of the user.                                              |
-| idp                  | Data from your identity provider.                                           |
-| geo                  | The country where the user authenticated from.                              |
-| user_uuid            | The ID of the user.                                                         |
-| devicePosture        | The device posture attributes.                                              |
-| account_id           | The account ID for your organization.                                       |
-| iat                  | The timestamp indicating when the user logged in.                           |
-| ip                   | The IP address of the user.                                                 |
-| auth_status          | The status if authenticating with mTLS.                                     |
-| common_name          | The common name on the mTLS client certificate.                             |
-| service_token_id     | The Client ID of the service token used for authentication.                 |
-| service_token_status | True if authentication was through a service token instead of an IdP.       |
-| is_warp              | True if the user enabled WARP.                                              |
-| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team.       |
-| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team. |
-| device_id            | The ID of the device used for authentication.                               |
-| version              | The version of the `get-identity` object.                                   |
-| device_sessions      | A list of all sessions initiated by the user.                               |
+| Field                | Description                                                                                |
+| -------------------- | ------------------------------------------------------------------------------------------ |
+| email                | The email address of the user.                                                             |
+| idp                  | Data from your identity provider.                                                          |
+| geo                  | The country where the user authenticated from.                                             |
+| user_uuid            | The ID of the user.                                                                        |
+| devicePosture        | The device posture attributes.                                                             |
+| account_id           | The account ID for your organization.                                                      |
+| iat                  | The timestamp indicating when the user logged in.                                          |
+| ip                   | The IP address of the user.                                                                |
+| auth_status          | The status if authenticating with mTLS.                                                    |
+| common_name          | The common name on the mTLS client certificate.                                            |
+| service_token_id     | The Client ID of the service token used for authentication.                                |
+| service_token_status | True if authentication was through a service token instead of an IdP.                      |
+| is_warp              | True if the user enabled WARP.                                                             |
+| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team. |
+| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team.      |
+| device_id            | The ID of the device used for authentication.                                              |
+| version              | The version of the `get-identity` object.                                                  |
+| device_sessions      | A list of all sessions initiated by the user.                                              |
 
 ### Service token authentication
 
@@ -121,15 +121,15 @@ Access will return a JSON structure containing the following data:
 }
 ```
 
-| Field       | Description                                                                                                                                      |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| type        | The type of Access token (`app` for application token or `org` for global session token).                                                        |
+| Field       | Description                                                                                                                                                                    |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| type        | The type of Access token (`app` for application token or `org` for global session token).                                                                                      |
 | aud         | The [application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application. |
-| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                 |
-| iss         | The Cloudflare Access domain URL for the application.                                                                                            |
-| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                      |
-| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                   |
-| sub         | Contains an empty string when authentication was through a service token.                                                                        |
+| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                                               |
+| iss         | The Cloudflare Access domain URL for the application.                                                                                                                          |
+| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                                                    |
+| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                                                 |
+| sub         | Contains an empty string when authentication was through a service token.                                                                                                      |
 
 ## Signature
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
index 6ac256251bea1e9..3917b42fff99c6f 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
@@ -197,7 +197,10 @@ export default {
 		const newRequest = new Request(url.toString(), request);
 
 		newRequest.headers.set("cf-access-client-id", env.CF_ACCESS_CLIENT_ID);
-		newRequest.headers.set("cf-access-client-secret", env.CF_ACCESS_CLIENT_SECRET);
+		newRequest.headers.set(
+			"cf-access-client-secret",
+			env.CF_ACCESS_CLIENT_SECRET,
+		);
 		try {
 			const response = await fetch(newRequest);
 
@@ -227,7 +230,7 @@ npx wrangler deploy
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.
 
-	<DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select your newly created Worker.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
index 5b1182c9666a6e2..03576d37f7ff815 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
@@ -188,13 +188,13 @@ The authorization flow proceeds as follows:
 
 Both managed OAuth and [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) allow non-browser clients to authenticate with Access-protected applications, but they serve different use cases:
 
-| | Managed OAuth | Service tokens |
-| --- | --- | --- |
-| **Authentication model** | User-based — the end user logs in through their identity provider | Machine-based — a shared secret authenticates the service itself |
-| **Best for** | Interactive CLI tools, AI agents, SDKs where a human initiates the request | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication |
-| **User identity** | Access knows which user made the request | No user identity — requests are attributed to the service token |
-| **Policy enforcement** | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
-| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials | Requires distributing and rotating Client ID and Client Secret |
+|                           | Managed OAuth                                                                    | Service tokens                                                                                  |
+| ------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **Authentication model**  | User-based — the end user logs in through their identity provider                | Machine-based — a shared secret authenticates the service itself                                |
+| **Best for**              | Interactive CLI tools, AI agents, SDKs where a human initiates the request       | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication             |
+| **User identity**         | Access knows which user made the request                                         | No user identity — requests are attributed to the service token                                 |
+| **Policy enforcement**    | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
+| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials  | Requires distributing and rotating Client ID and Client Secret                                  |
 
 Use managed OAuth when you want non-browser clients to authenticate users the same way a browser would — the user logs in once, and the client receives an OAuth token to make requests on their behalf.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
index 52fef67da2246a1..cadc87d1fda6ab5 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
@@ -59,12 +59,15 @@ Some SaaS applications provide the Redirect URL after you [configure the SSO pro
 
 11. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-12. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "saas" }}/>
+12. <Render
+    	file="access/access-choose-idps"
+    	product="cloudflare-one"
+    	params={{ appType: "saas" }}
+    />
 
 13. (Optional) Go to **Additional settings** to customize the application experience:
-
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
-	- <Render file="access/access-block-page" product="cloudflare-one" />
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
+    - <Render file="access/access-block-page" product="cloudflare-one" />
 
 14. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
index c554be332b64448..cee76077b2de270 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-- SSO
+  - SSO
 ---
 
 This guide covers how to configure [Grafana Cloud](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/authorization/#configure-oauth-20-with-generic-oauth) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
index b7a904dc94c5681..c343d9ad68ce913 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-- SSO
+  - SSO
 ---
 
 This guide covers how to configure [Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
index 3118fcac0cec9c2..01dc8bf2c1ccd20 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
@@ -6,10 +6,9 @@ products:
 title: SaaS applications
 sidebar:
   order: 1
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare Access allows you to add an additional authentication layer to your SaaS applications. When you integrate a SaaS application with Access, users log in to the application with Cloudflare as the Single Sign-On provider. The user is then redirected to the configured identity providers for that application and are only granted access if they pass your Access policies.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
index ae83f5143d310dc..2cfa346e15fc6c3 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
@@ -7,8 +7,8 @@ title: Browser-rendered terminal
 sidebar:
   order: 3
 tags:
-- SSH
-- RDP
+  - SSH
+  - RDP
 ---
 
 import { Render } from "~/components";
@@ -31,7 +31,10 @@ To turn on browser rendering for an SSH or VNC application:
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/). Select **Configure**.
 3. Turn on **Allow access through browser-based RDP, SSH, or VNC sessions**, then select _SSH_ or _VNC_.
-	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
+   <Render
+   	file="access/self-hosted-app/browser-rendering-policies"
+   	product="cloudflare-one"
+   />
 4. Select **Save**.
 
 When users authenticate and visit the URL of the application, Cloudflare will render a terminal in their browser.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
index e0badb2c31fe6c0..203505a89c9fa0e 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
@@ -7,8 +7,8 @@ title: Arbitrary TCP
 sidebar:
   order: 11
 tags:
-- TCP
-- SSH
+  - TCP
+  - SSH
 ---
 
 Cloudflare Access provides a mechanism for end users to authenticate with their single sign-on (SSO) provider and connect to resources over arbitrary TCP without being on a virtual private network (VPN).
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
index 0e09be8ca535069..242e714857c5c7a 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
@@ -7,7 +7,7 @@ title: Enable automatic cloudflared authentication
 sidebar:
   order: 2
 tags:
-- Authentication
+  - Authentication
 ---
 
 When users connect to an Access application through `cloudflared`, the browser prompts them to allow access by displaying this page:
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
index 2f0c700b0197311..7b753f951aa5916 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
   label: Private network applications (legacy)
 tags:
-- Private networks
+  - Private networks
 ---
 
 :::caution
@@ -35,7 +35,6 @@ Existing **Private Network** applications continue to function and can still be
 7. Select **Next**. You will see two auto-generated Gateway Network policies: one that allows access to the destination IP and another that blocks access.
 
 8. Modify the policies to include additional identity-based conditions. For example:
-
    - **Policy 1**
 
      | Selector       | Operator      | Value            | Logic | Action |
@@ -53,4 +52,4 @@ Existing **Private Network** applications continue to function and can still be
 
 9. Select **Add application**.
 
-Your application will appear on the **Applications** page.
\ No newline at end of file
+Your application will appear on the **Applications** page.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
index 00a20e37e19d6cb..4b7341a9ec0afcb 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
@@ -11,7 +11,7 @@ sidebar:
   label: Add a self-hosted private application
 ---
 
-import { Render, GlossaryTooltip, } from "~/components";
+import { Render, GlossaryTooltip } from "~/components";
 
 You can configure a self-hosted Access application to manage access to specific IPs or hostnames on your private network.
 
@@ -28,54 +28,59 @@ This feature replaces the legacy [private network app type](/cloudflare-one/acce
 
 ## Add your application to Access
 
-1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+1.  In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
-2. Select **Create new application**.
+2.  Select **Create new application**.
 
-3. Select **Self-hosted and private**.
+3.  Select **Self-hosted and private**.
 
-4.  To add an application using its private IP:
-		1. Select **Add private IP**.
-		2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`).
-		3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+4.  To add an application using its private IP: 1. Select **Add private IP**. 2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`). 3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-			Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
+        	Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
 
-5. To add an application using its private hostname:
-	1. Select **Add private hostname**.
-	2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
-	3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+5.  To add an application using its private hostname:
+    1. Select **Add private hostname**.
+    2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
+    3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-	:::note
-	- **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
-	- **Non-HTTPS applications**:  Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
+    :::note
+    - **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
+    - **Non-HTTPS applications**: Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
 
-		<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one"/>
+      <Render
+      	file="gateway/egress-selector-cgnat-ips"
+      	product="cloudflare-one"
+      />
 
-		For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
+      For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
 
 6.  <Render file="access/add-access-policies" product="cloudflare-one" />
-7.  <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "private" }}/>
+7.  <Render
+    	file="access/access-choose-idps"
+    	product="cloudflare-one"
+    	params={{ appType: "private" }}
+    />
 
-8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
+8.  <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
-9. <Render file="access/session-duration" product="cloudflare-one" />
+9.  <Render file="access/session-duration" product="cloudflare-one" />
 
-   If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
+    If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+    - **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
 
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	- **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
-
-		:::note
-		Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
-		:::
-
-	- <Render file="access/access-block-page" product="cloudflare-one" />
-	- The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
-		<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
+      :::note
+      Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
+      :::
 
+    - <Render file="access/access-block-page" product="cloudflare-one" />
+    - The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
+      <Render
+      	file="access/self-hosted-app/advanced-settings"
+      	product="cloudflare-one"
+      />
 
 11. Select **Create**.
 
@@ -113,8 +118,11 @@ An Access application defined by a private hostname takes precedence over an Acc
 
 ### Browser Isolation is not compatible with apps on non-`443` ports
 
-<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
+<Render
+	file="access/self-hosted-app/browser-isolation-non-443"
+	product="cloudflare-one"
+/>
 
 ### Google Chrome restricts access to private hostnames
 
-<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one"/>
+<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
index 3dfe9164a038ef3..2de16fa32411bf7 100644
--- a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Available Access events
 
-<Render file="event-subscriptions/access-events" product="queues" />
\ No newline at end of file
+<Render file="event-subscriptions/access-events" product="queues" />
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
index 1c0b4d46c3a4704..899ed27993f86f3 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
@@ -6,7 +6,6 @@ products:
 title: Application paths
 sidebar:
   order: 5
-
 ---
 
 Application paths define the URLs protected by an Access policy. When adding a self-hosted application to Access, you can choose to protect the entire website by entering its apex domain, or alternatively, protect specific subdomains and paths.
@@ -27,9 +26,9 @@ When you create an application for a specific subdomain or path, you can use ast
 
 A wildcard in the **Subdomain** field only matches that specific subdomain level. It does not cover the apex domain or multiple levels of the subdomain. If you want to cover multiple subdomain levels, you can use multiple wildcards.
 
-| Application     | Covers                                       | Does not cover |
-| --------------- | -------------------------------------------- | -------------- |
-| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com`  |
+| Application     | Covers                                       | Does not cover                            |
+| --------------- | -------------------------------------------- | ----------------------------------------- |
+| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com` |
 
 #### Match all paths of an apex domain
 
@@ -43,9 +42,9 @@ To protect an apex domain and all of the paths under it, leave the **Path** fiel
 
 Using a wildcard in the **Subdomain** field does not cover the parent subdomain nor the apex domain.
 
-| Application          | Covers                                                 | Does not cover                          |
-| -------------------- | ------------------------------------------------------ | --------------------------------------- |
-| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com`  <br/> `example.com` |
+| Application          | Covers                                                 | Does not cover                         |
+| -------------------- | ------------------------------------------------------ | -------------------------------------- |
+| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com` <br/> `example.com` |
 
 #### Partially match subdomains
 
@@ -73,8 +72,8 @@ Using a wildcard in the middle of the **Path** field covers multiple segments of
 
 ### Limitations
 
-* At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
-* At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
+- At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
+- At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
 
 ## Subdomain setups
 
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
index c8ec944860e8d4b..e08ee885d64e235 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
@@ -145,29 +145,29 @@ When you add a rule to your Cloudflare Access policy, you will be asked to speci
 
 Non-identity attributes are polled continuously, meaning they are evaluated with each new HTTP request for changes during the [user session](/cloudflare-one/access-controls/access-settings/session-management/). If you have configured [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/), you can force a user to re-attest all attributes with Access whenever you revoke the user in the IdP or update their IdP group membership.
 
-| Selector                 | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
-| Emails                   | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Emails ending in         | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
-| External Evaluation      | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
-| IP ranges                | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
-| Country                  | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
-| Everyone                 | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
-| Common Name              | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
-| Valid Certificate        | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Service Token            | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Any Access Service Token | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
-| User Risk Score          | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
-| Linked App Token         | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                   | ✅               | ✅                               | ❌                       |
-| Login Methods            | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
-| Authentication Method    | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
-| Identity provider group  | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
-| SAML Group               | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
-| OIDC Claim               | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Device posture           | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
-| Warp                     | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
-| Gateway                  | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
-| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                                | ✅               | ❌                               | ✅                       |
+| Selector                  | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
+| Emails                    | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Emails ending in          | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
+| External Evaluation       | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
+| IP ranges                 | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
+| Country                   | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
+| Everyone                  | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
+| Common Name               | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
+| Valid Certificate         | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Service Token             | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Any Access Service Token  | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
+| User Risk Score           | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
+| Linked App Token          | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                      | ✅               | ✅                               | ❌                       |
+| Login Methods             | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
+| Authentication Method     | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
+| Identity provider group   | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
+| SAML Group                | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
+| OIDC Claim                | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Device posture            | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
+| Warp                      | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
+| Gateway                   | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
+| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                               | ✅               | ❌                               | ✅                       |
 
 <sup>1</sup> For SaaS applications, Access can only enforce policies at the time
 of initial sign on and when reissuing the SaaS session. Once the user has
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
index 7213c910db20077..11eeaa22045b223 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
@@ -54,7 +54,7 @@ To delete a reusable Access policy:
 
 ## Test your policies
 
-You can test your Access policies against all existing user identities in your Zero Trust organization.  For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
+You can test your Access policies against all existing user identities in your Zero Trust organization. For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
 
 Cloudflare will use the most recent device that was authenticated with Access to test your policies.
 
@@ -76,25 +76,22 @@ You can test your Access application policies against your user population befor
 
 To test if users have access to an application:
 
-1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
-2. Locate the application you want to test and select **Configure**.
-3. Go to **Policies** > **Policy tester**.
-4. To test all active users in your organization, select **Test policies**.
+1.  In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+2.  Locate the application you want to test and select **Configure**.
+3.  Go to **Policies** > **Policy tester**.
+4.  To test all active users in your organization, select **Test policies**.
 
-		The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
+        The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
 
-5. To perform a detailed test on a single user:
+5.  To perform a detailed test on a single user:
 
-	a. If you made any changes to your policies, first save the application.
+    a. If you made any changes to your policies, first save the application.
 
-	b. Select **testing a single user**.
+    b. Select **testing a single user**.
 
-	c. Enter their email address and select **Test policies**.
+    c. Enter their email address and select **Test policies**.
 
-	The single user test results will show:
-		- Whether the user is allowed or denied access to this application based on all configured policies.
-		- The user's identity from their most recent Access login attempt.
-		- Whether the user matches individual Allow, Block, or Bypass policies.
+    The single user test results will show: - Whether the user is allowed or denied access to this application based on all configured policies. - The user's identity from their most recent Access login attempt. - Whether the user matches individual Allow, Block, or Bypass policies.
 
 ## Legacy policies
 
@@ -114,8 +111,8 @@ To migrate legacy policies to reusable policies:
 You can use the API to convert a legacy policy into a reusable policy. To convert a legacy policy, make a `PUT` request with an empty request body:
 
 <APIRequest
-  path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
-  method="PUT"
+	path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
+	method="PUT"
 />
 
 The policy is now removed from the applications endpoint (`/access/apps/$APP_ID/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/$POLICY_ID`).
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
index ef3c106a4c83c56..3759f0ffb3db29b 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Require purpose justification after login
-
 ---
 
 Cloudflare Access allows security and IT teams to present users with a purpose justification screen directly after they log in to an Access application. This allows organizations to audit not only for who is accessing their resources, but also for why they are requesting access.
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
index 3c320499e0997ac..a3fccad67a5f5e6 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
@@ -7,7 +7,7 @@ title: Temporary authentication
 sidebar:
   order: 11
 tags:
-- Authentication
+  - Authentication
 ---
 
 With Cloudflare Access, you can require that users obtain approval before they can access a specific self-hosted application or SaaS application. The administrator will receive an email notification to approve or deny the request. Unlike a typical Allow policy, the user will have to request access at the end of each session. This allows you to define the users who should have persistent access and those who must request temporary access.
@@ -20,9 +20,9 @@ With Cloudflare Access, you can require that users obtain approval before they c
 4. Under **Additional settings**, turn on [**Purpose justification**](/cloudflare-one/access-controls/policies/require-purpose-justification/).
 5. Turn on **Temporary authentication**.
 6. Enter the **Email addresses of the approvers**.
-	:::note
-	Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	:::
+   :::note
+   Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
+   :::
 7. Save the policy.
 
 Temporary authentication is now enabled for users who match this policy. You can optionally add a second **Allow** policy for users who should have persistent access. Be sure the policy order is set to allow persistent users through.
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
index 7ff124cd8eb6d90..a9f7713dccc5a33 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
@@ -13,4 +13,3 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
-
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
index 64603599f027224..28d4336eca249b9 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
@@ -7,8 +7,8 @@ title: Service tokens
 sidebar:
   order: 6
 tags:
-- JSON web token (JWT)
-- Authentication
+  - JSON web token (JWT)
+  - Authentication
 ---
 
 import {
diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index e29b38b2b415178..2b66eb6b6433481 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -62,19 +62,19 @@ This page lists the default account limits for rules, applications, fields, and
 
 ## Cloudflare Tunnel
 
-| Feature                                            | Limit |
-| -------------------------------------------------- | ----- |
-| `cloudflared` tunnels per account                  | 1,000 |
+| Feature                                            | Limit                               |
+| -------------------------------------------------- | ----------------------------------- |
+| `cloudflared` tunnels per account                  | 1,000                               |
 | Routes (CIDR routes + Hostname routes) per account | 1,000 (shared with Cloudflare Mesh) |
-| Active `cloudflared` replicas per tunnel           | 25    |
-| Virtual networks per account                       | 1,000 |
+| Active `cloudflared` replicas per tunnel           | 25                                  |
+| Virtual networks per account                       | 1,000                               |
 
 ## Cloudflare Mesh
 
-| Feature                                            | Limit |
-| -------------------------------------------------- | ----- |
-| Mesh nodes per account                             | 50    |
-| Routes (CIDR routes) per account                   | 1,000 (shared with Cloudflare Tunnel) |
+| Feature                          | Limit                                 |
+| -------------------------------- | ------------------------------------- |
+| Mesh nodes per account           | 50                                    |
+| Routes (CIDR routes) per account | 1,000 (shared with Cloudflare Tunnel) |
 
 ## Digital Experience Monitoring (DEX)
 
@@ -106,6 +106,7 @@ This page lists the default account limits for rules, applications, fields, and
 | Gateway API policy expression | 140,000         |
 
 ## Cloudflare One Client
+
 | Feature                                                                    | Limit  |
 | -------------------------------------------------------------------------- | ------ |
 | Characters per device profile expression                                   | 10,000 |
diff --git a/src/content/docs/cloudflare-one/changelog/tunnel.mdx b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
index 7d4677d85c9b423..5c1f6285b4348a4 100644
--- a/src/content/docs/cloudflare-one/changelog/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog, Render } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog
-	product="tunnel"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
 
 ## 2024-10-17
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
index 64994724c683773..508f0cb7179a5a0 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
@@ -29,13 +29,13 @@ Templates provide Cloudflare-managed starting points for sensitivity schemas and
 
 Data Classification works alongside detection entries and DLP profiles.
 
-| Component | What it does |
-| --- | --- |
+| Component         | What it does                                                                                                            |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
 | Detection entries | Detect specific content such as patterns, datasets, document fingerprints, AI prompt topics, and predefined detections. |
-| Labels | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content. |
-| Templates | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups. |
-| Data classes | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags. |
-| DLP profiles | Apply detection and classification logic to DLP scanning and enforcement workflows. |
+| Labels            | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content.        |
+| Templates         | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups.                                 |
+| Data classes      | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags.      |
+| DLP profiles      | Apply detection and classification logic to DLP scanning and enforcement workflows.                                     |
 
 In general, detection entries help identify sensitive content. Data Classification helps organize and label that content so administrators can identify its severity, understand where it exists, and apply it consistently. DLP profiles then apply that logic to scanning and enforcement workflows.
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
index 76a268ab8c5fbda..2e931248090f21d 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
@@ -182,16 +182,16 @@ Your new document entry will replace the original document entry. If your file u
 
 DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
 
-| Detection entry | Description |
-| --- | --- |
-| Content: PII | Prompt contains personal information such as names, SSNs, or email addresses. |
-| Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials. |
-| Content: Source Code | Prompt contains actual source code, code snippets, or proprietary algorithms. |
-| Content: Customer Data | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
-| Content: Financial Information | Prompt contains financial numbers or confidential business data. |
-| Intent: PII | Prompt requests specific personal information about individuals. |
-| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities. |
-| Intent: Jailbreak | Prompt attempts to circumvent AI security policies. |
+| Detection entry                       | Description                                                                                       |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| Content: PII                          | Prompt contains personal information such as names, SSNs, or email addresses.                     |
+| Content: Credentials and Secrets      | Prompt contains API keys, passwords, or other sensitive credentials.                              |
+| Content: Source Code                  | Prompt contains actual source code, code snippets, or proprietary algorithms.                     |
+| Content: Customer Data                | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
+| Content: Financial Information        | Prompt contains financial numbers or confidential business data.                                  |
+| Intent: PII                           | Prompt requests specific personal information about individuals.                                  |
+| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities.                      |
+| Intent: Jailbreak                     | Prompt attempts to circumvent AI security policies.                                               |
 
 Each detection entry is categorized as either **Content** or **Intent**:
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
index ccd073189323e6d..e948a705b784d4a 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
@@ -14,151 +14,151 @@ Predefined detection entries are Cloudflare-managed detections for specific type
 
 You can add any predefined detection entry directly to a custom [DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/#build-a-custom-profile) or [data class](/cloudflare-one/data-loss-prevention/data-classification/build-a-data-class/). Use the following reference to review all predefined detection entries currently supported by Cloudflare DLP.
 
-| Detection entry | Description |
-| --- | --- |
-| AI Prompt Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials |
-| AI Prompt Content: Customer data | Prompt contains customer names, projects, business activities, or confidential customer contexts |
-| AI Prompt Content: Financial Information | Prompt contains actual financial numbers or confidential business data |
-| AI Prompt Content: PII | Prompt contains personal information (names, SSNs, emails, etc.) |
-| AI Prompt Content: Source code | Prompt contains source code, code snippets, or proprietary algorithms |
-| AI Prompt Intent: Code Abuse and Malicious Code | Malicious code or attempts to exploit vulnerabilities |
-| AI Prompt Intent: Jailbreak | Prompt attempts to circumvent security policies |
-| AI Prompt Intent: PII | Prompt requests specific personal information about individuals |
-| Amazon AWS Access Key ID | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`. |
-| Amazon AWS Secret Access Key | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`. |
-| American Express Card Number | Detects American Express credit card numbers such as "378282246310005". |
-| American Express Text | Detects mentions of the American Express brand name such as "American Express". |
-| AU Passport Number | Detects Australian passport numbers such as "L1234567". |
-| Australia Address | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000". |
-| Australia Business (ABN) | Detects Australian Business Numbers (ABN) such as "51 824 753 556". |
-| Australia Company (ACN) | Detects Australian Company Numbers (ACN) such as "001 000 004". |
-| Australia Medicare | Detects Australian Medicare card numbers such as "2000000006". |
-| Australia Passport | Detects Australian passport numbers such as "L1234567". |
-| Australia Tax File Number | Detects Australian Tax File Numbers (TFN) such as "85 655 734". |
-| Austria SSN (SV-Nummer) | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180". |
-| Austria Tax ID | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789". |
-| Austria VAT (UID) | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678". |
-| Belgium Tax ID (NN) | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61". |
-| Belgium VAT | Detects Belgian VAT numbers such as "BE0000000097". |
-| Bitcoin Wallet | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2". |
-| Brazil CNPJ | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81". |
-| Brazil CPF (Tax ID) | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25". |
-| Bulgaria Uniform Civil (EGN) | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007". |
-| C | Detects C source code. |
-| C# | Detects C# source code. |
-| C++ | Detects C++ source code. |
-| Canada Bank Account Number | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567". |
-| Canada Health Number | Detects Canadian provincial health card numbers such as "1234-567-897". |
-| Canada Passport | Detects Canadian passport numbers such as "AB123456". |
-| Canada PHIN (Manitoba) | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009". |
-| Canada Physical Address | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1". |
-| Canada Social Insurance Number | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474". |
-| Chile National ID (RUT) | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5". |
-| China ID Card | Detects Chinese resident identity card numbers such as "11010519491231002X". |
-| Cloudflare Account Owned API Token | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`. |
-| Cloudflare User API Key | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`. |
-| Cloudflare User API Token | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`. |
-| Croatia Personal ID (OIB) | Detects Croatian personal identification numbers (OIB) such as "10000000005". |
-| Denmark Tax (CPR) | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008". |
-| Diners Club Card Number | Detects Diners Club credit card numbers such as "30121690374838". |
-| Discord Webhook | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`. |
-| Email Address | Detects email addresses such as "test@example.com". |
-| Ethereum Wallet | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F". |
-| EU Passport | Detects EU member state passport numbers such as "AB1234567". |
-| FDA Active Ingredients | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB". |
-| FDA Drug Names | Detects FDA-registered drug names such as "ABACAVIR". |
-| Finland Tax ID | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y". |
-| France CNI (National ID) | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901". |
-| France Passport | Detects French passport numbers such as "12AB34567". |
-| France Social Security Number | Detects French social security (INSEE) numbers such as "145081849670637". |
-| France Tax ID (SPI) | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123". |
-| France VAT | Detects French VAT numbers such as "FR12000000000". |
-| Full Name | Detects personal full names. |
-| Generic CVV Card Number | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033". |
-| Germany Tax ID | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005". |
-| Germany VAT | Detects German VAT numbers (USt-IdNr) such as "DE100000003". |
-| GitHub PAT | Detects GitHub personal access tokens such as a token beginning with `ghp_`. |
-| Go | Detects Go source code. |
-| Google GCP API Key | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`. |
-| Greece Tax (AFM) | Detects Greek tax identification numbers (AFM) such as "100000003". |
-| Haskell | Detects Haskell source code. |
-| Hong Kong Identity Card Number | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)". |
-| Hungary Tax | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008". |
-| IBAN | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59". |
-| ICD-10 FY2023 Short Description | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified". |
-| ICD-11 Short Description | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS". |
-| India Aadhaar | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124". |
-| India GST (GSTIN) | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5". |
-| India PAN Card | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F". |
-| India Voter ID | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567". |
-| Indonesia Identity Card Number | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011". |
-| Indonesia Tax (NPWP) | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345". |
-| Ireland Tax (PPS) | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA". |
-| Ireland VAT | Detects Ireland VAT numbers such as "IE1234567T". |
-| Italy Fiscal Code | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z". |
-| Japan Address | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001". |
-| Japan My Number (Corp) | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002". |
-| Japan My Number (Person) | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005". |
-| Japan Names (Kanji) | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎". |
-| Japan Passport | Detects Japanese passport numbers such as "TZ1234567". |
-| Java | Detects Java source code. |
-| JavaScript | Detects JavaScript source code. |
-| Korea Resident Number (RRN) | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567". |
-| Lua | Detects Lua source code. |
-| Luxembourg Tax | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345". |
-| Luxembourg VAT | Detects Luxembourg VAT numbers such as "LU10000053". |
-| Malaysian National Identity Card Number | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354". |
-| Mastercard Card Number | Detects Mastercard credit card numbers such as "5252 5971 4219 4116". |
-| Mastercard Text | Detects mentions of the Mastercard brand name such as "Mastercard". |
-| Microsoft Azure Client Secret | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`. |
-| MX CLABE (Bank) | Detects Mexican CLABE bank account numbers such as "032180000118359719". |
-| MX CURP | Detects Mexican CURP codes such as "GOMC850515HJCRRR05". |
-| Netherlands BSN | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782". |
-| Netherlands VAT | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01". |
-| NPM Token | Detects npm registry access tokens such as a token beginning with `npm_`. |
-| NZ NHI Number | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016". |
-| NZ Tax (IRD) | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850". |
-| OpenAI API Key | Detects OpenAI API keys such as a key beginning with `sk-proj-`. |
-| Peru Tax (RUC) | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001". |
-| Peru Unique ID (DNI) | Detects Peruvian national identity numbers (DNI) such as "12345678". |
-| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1". |
-| Poland National ID (PESEL) | Detects Polish national identification numbers (PESEL) such as "85051500006". |
-| Poland REGON | Detects Polish National Business Registry numbers (REGON) such as "100000008". |
-| Poland Tax (NIP) | Detects Polish tax identification numbers (NIP) such as "123-456-32-18". |
-| Portugal Tax (NIF) | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002". |
-| PyPI Token | Detects PyPI package upload tokens such as a token beginning with `pypi-`. |
-| Python | Detects Python source code. |
-| R | Detects R source code. |
-| Rust | Detects Rust source code. |
-| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H". |
-| Slack API Token | Detects Slack API tokens such as a token beginning with `xoxb-`. |
-| Slack Webhook | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`. |
-| Spain DNI/NIF | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z". |
-| Spain SSN | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890". |
-| Spain Tax (CIF) | Detects Spanish corporate tax identification codes (CIF) such as "A58818501". |
-| SSH Private Key | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----". |
-| Stripe Granular Restricted Key | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`. |
-| Stripe Standard Secret Key | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`. |
-| Sweden Tax | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874". |
-| SWIFT | Detects SWIFT/BIC business identifier codes such as "PMFAUS66". |
-| Swift | Detects Swift source code. |
-| Taiwan National Identification Number | Detects Taiwan national identification numbers such as "W171845961". |
-| Thai Identity Card Number | Detects Thai national identity card numbers such as "4-8547-01245-28-9". |
-| UAE Passport | Detects United Arab Emirates passport numbers such as "A1234567". |
-| Union Pay Card Number | Detects UnionPay credit card numbers such as "6250941006528599". |
-| Union Pay Text | Detects mentions of the UnionPay brand name such as "Union Pay". |
-| United Kingdom National Insurance Number | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C". |
-| United Kingdom NHS Number | Detects UK NHS patient identification numbers such as "485-585-0454". |
-| United States ABA Routing Number | Detects US ABA bank routing numbers such as "021000021". |
-| United States SSN Numeric Detection | Detects US Social Security Numbers such as "123-45-6789". |
-| United States SSN Text | Detects mentions of "SSN" or "social security" as a keyword, such as "social security". |
-| Unsanitized HAR File | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
-| Uruguay ID (CI) | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8". |
-| US Driver's License Number | Detects US driver's license numbers such as "CA License: A1234567". |
-| US Individual Tax Identification Number (ITIN) | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678". |
-| US Mailing Address | Detects US mailing addresses such as "100 First St, Chicago, IL 60601". |
-| US Passport Number | Detects US passport numbers such as "A12345678". |
-| US Phone Number | Detects US phone numbers such as "555-555-5555". |
-| US Physical Address | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601". |
-| Visa Card Number | Detects Visa credit card numbers such as "4111 1111 1111 1111". |
-| Visa Text | Detects mentions of the Visa brand name such as "Visa". |
+| Detection entry                                      | Description                                                                                                                                                                  |
+| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| AI Prompt Content: Credentials and Secrets           | Prompt contains API keys, passwords, or other sensitive credentials                                                                                                          |
+| AI Prompt Content: Customer data                     | Prompt contains customer names, projects, business activities, or confidential customer contexts                                                                             |
+| AI Prompt Content: Financial Information             | Prompt contains actual financial numbers or confidential business data                                                                                                       |
+| AI Prompt Content: PII                               | Prompt contains personal information (names, SSNs, emails, etc.)                                                                                                             |
+| AI Prompt Content: Source code                       | Prompt contains source code, code snippets, or proprietary algorithms                                                                                                        |
+| AI Prompt Intent: Code Abuse and Malicious Code      | Malicious code or attempts to exploit vulnerabilities                                                                                                                        |
+| AI Prompt Intent: Jailbreak                          | Prompt attempts to circumvent security policies                                                                                                                              |
+| AI Prompt Intent: PII                                | Prompt requests specific personal information about individuals                                                                                                              |
+| Amazon AWS Access Key ID                             | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`.                                                                                                             |
+| Amazon AWS Secret Access Key                         | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`.                                                                                           |
+| American Express Card Number                         | Detects American Express credit card numbers such as "378282246310005".                                                                                                      |
+| American Express Text                                | Detects mentions of the American Express brand name such as "American Express".                                                                                              |
+| AU Passport Number                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
+| Australia Address                                    | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000".                                                                        |
+| Australia Business (ABN)                             | Detects Australian Business Numbers (ABN) such as "51 824 753 556".                                                                                                          |
+| Australia Company (ACN)                              | Detects Australian Company Numbers (ACN) such as "001 000 004".                                                                                                              |
+| Australia Medicare                                   | Detects Australian Medicare card numbers such as "2000000006".                                                                                                               |
+| Australia Passport                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
+| Australia Tax File Number                            | Detects Australian Tax File Numbers (TFN) such as "85 655 734".                                                                                                              |
+| Austria SSN (SV-Nummer)                              | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180".                                                                                                  |
+| Austria Tax ID                                       | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789".                                                                                            |
+| Austria VAT (UID)                                    | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678".                                                                                                             |
+| Belgium Tax ID (NN)                                  | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61".                                                                          |
+| Belgium VAT                                          | Detects Belgian VAT numbers such as "BE0000000097".                                                                                                                          |
+| Bitcoin Wallet                                       | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2".                                                                                               |
+| Brazil CNPJ                                          | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81".                                                                                   |
+| Brazil CPF (Tax ID)                                  | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25".                                                                                       |
+| Bulgaria Uniform Civil (EGN)                         | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007".                                                                                                          |
+| C                                                    | Detects C source code.                                                                                                                                                       |
+| C#                                                   | Detects C# source code.                                                                                                                                                      |
+| C++                                                  | Detects C++ source code.                                                                                                                                                     |
+| Canada Bank Account Number                           | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567".                                                                         |
+| Canada Health Number                                 | Detects Canadian provincial health card numbers such as "1234-567-897".                                                                                                      |
+| Canada Passport                                      | Detects Canadian passport numbers such as "AB123456".                                                                                                                        |
+| Canada PHIN (Manitoba)                               | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009".                                                                                          |
+| Canada Physical Address                              | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1".                                                                                |
+| Canada Social Insurance Number                       | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474".                                                                                                       |
+| Chile National ID (RUT)                              | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5".                                                                         |
+| China ID Card                                        | Detects Chinese resident identity card numbers such as "11010519491231002X".                                                                                                 |
+| Cloudflare Account Owned API Token                   | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`.                                                                                        |
+| Cloudflare User API Key                              | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`.                                                                                                               |
+| Cloudflare User API Token                            | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`.                                                                                                          |
+| Croatia Personal ID (OIB)                            | Detects Croatian personal identification numbers (OIB) such as "10000000005".                                                                                                |
+| Denmark Tax (CPR)                                    | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008".                                                                                           |
+| Diners Club Card Number                              | Detects Diners Club credit card numbers such as "30121690374838".                                                                                                            |
+| Discord Webhook                                      | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`.                                                                                        |
+| Email Address                                        | Detects email addresses such as "test@example.com".                                                                                                                          |
+| Ethereum Wallet                                      | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F".                                                                                      |
+| EU Passport                                          | Detects EU member state passport numbers such as "AB1234567".                                                                                                                |
+| FDA Active Ingredients                               | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB".                                                                                                   |
+| FDA Drug Names                                       | Detects FDA-registered drug names such as "ABACAVIR".                                                                                                                        |
+| Finland Tax ID                                       | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y".                                                                                        |
+| France CNI (National ID)                             | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901".                                                                            |
+| France Passport                                      | Detects French passport numbers such as "12AB34567".                                                                                                                         |
+| France Social Security Number                        | Detects French social security (INSEE) numbers such as "145081849670637".                                                                                                    |
+| France Tax ID (SPI)                                  | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123".                                                                                       |
+| France VAT                                           | Detects French VAT numbers such as "FR12000000000".                                                                                                                          |
+| Full Name                                            | Detects personal full names.                                                                                                                                                 |
+| Generic CVV Card Number                              | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033".                                                                          |
+| Germany Tax ID                                       | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005".                                                                               |
+| Germany VAT                                          | Detects German VAT numbers (USt-IdNr) such as "DE100000003".                                                                                                                 |
+| GitHub PAT                                           | Detects GitHub personal access tokens such as a token beginning with `ghp_`.                                                                                                 |
+| Go                                                   | Detects Go source code.                                                                                                                                                      |
+| Google GCP API Key                                   | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`.                                                                                                              |
+| Greece Tax (AFM)                                     | Detects Greek tax identification numbers (AFM) such as "100000003".                                                                                                          |
+| Haskell                                              | Detects Haskell source code.                                                                                                                                                 |
+| Hong Kong Identity Card Number                       | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)".                                                                                                         |
+| Hungary Tax                                          | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008".                                                                                        |
+| IBAN                                                 | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59".                                                                                     |
+| ICD-10 FY2023 Short Description                      | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified".                                                                                          |
+| ICD-11 Short Description                             | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS".                                                                                                    |
+| India Aadhaar                                        | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124".                                                                                             |
+| India GST (GSTIN)                                    | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5".                                                                              |
+| India PAN Card                                       | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F".                                                                                         |
+| India Voter ID                                       | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567".                                                                                                                 |
+| Indonesia Identity Card Number                       | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011".                                                                                               |
+| Indonesia Tax (NPWP)                                 | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345".                                                                                    |
+| Ireland Tax (PPS)                                    | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA".                                                                                                     |
+| Ireland VAT                                          | Detects Ireland VAT numbers such as "IE1234567T".                                                                                                                            |
+| Italy Fiscal Code                                    | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z".                                                                                                    |
+| Japan Address                                        | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001".                                                                                   |
+| Japan My Number (Corp)                               | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002".                                                                                      |
+| Japan My Number (Person)                             | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005".                                                                                      |
+| Japan Names (Kanji)                                  | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎".                                                                            |
+| Japan Passport                                       | Detects Japanese passport numbers such as "TZ1234567".                                                                                                                       |
+| Java                                                 | Detects Java source code.                                                                                                                                                    |
+| JavaScript                                           | Detects JavaScript source code.                                                                                                                                              |
+| Korea Resident Number (RRN)                          | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567".                                                                                           |
+| Lua                                                  | Detects Lua source code.                                                                                                                                                     |
+| Luxembourg Tax                                       | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345".                                                                                      |
+| Luxembourg VAT                                       | Detects Luxembourg VAT numbers such as "LU10000053".                                                                                                                         |
+| Malaysian National Identity Card Number              | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354".                                                                                           |
+| Mastercard Card Number                               | Detects Mastercard credit card numbers such as "5252 5971 4219 4116".                                                                                                        |
+| Mastercard Text                                      | Detects mentions of the Mastercard brand name such as "Mastercard".                                                                                                          |
+| Microsoft Azure Client Secret                        | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`.                                                                                                      |
+| MX CLABE (Bank)                                      | Detects Mexican CLABE bank account numbers such as "032180000118359719".                                                                                                     |
+| MX CURP                                              | Detects Mexican CURP codes such as "GOMC850515HJCRRR05".                                                                                                                     |
+| Netherlands BSN                                      | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782".                                                                                       |
+| Netherlands VAT                                      | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01".                                                                                                             |
+| NPM Token                                            | Detects npm registry access tokens such as a token beginning with `npm_`.                                                                                                    |
+| NZ NHI Number                                        | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016".                                                                                                   |
+| NZ Tax (IRD)                                         | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850".                                                                                        |
+| OpenAI API Key                                       | Detects OpenAI API keys such as a key beginning with `sk-proj-`.                                                                                                             |
+| Peru Tax (RUC)                                       | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001".                                                                                                |
+| Peru Unique ID (DNI)                                 | Detects Peruvian national identity numbers (DNI) such as "12345678".                                                                                                         |
+| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1".                                                                                        |
+| Poland National ID (PESEL)                           | Detects Polish national identification numbers (PESEL) such as "85051500006".                                                                                                |
+| Poland REGON                                         | Detects Polish National Business Registry numbers (REGON) such as "100000008".                                                                                               |
+| Poland Tax (NIP)                                     | Detects Polish tax identification numbers (NIP) such as "123-456-32-18".                                                                                                     |
+| Portugal Tax (NIF)                                   | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002".                                                                            |
+| PyPI Token                                           | Detects PyPI package upload tokens such as a token beginning with `pypi-`.                                                                                                   |
+| Python                                               | Detects Python source code.                                                                                                                                                  |
+| R                                                    | Detects R source code.                                                                                                                                                       |
+| Rust                                                 | Detects Rust source code.                                                                                                                                                    |
+| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H".                                                                                                        |
+| Slack API Token                                      | Detects Slack API tokens such as a token beginning with `xoxb-`.                                                                                                             |
+| Slack Webhook                                        | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`.                                                                                 |
+| Spain DNI/NIF                                        | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z".                                                                                                     |
+| Spain SSN                                            | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890".                                                                                           |
+| Spain Tax (CIF)                                      | Detects Spanish corporate tax identification codes (CIF) such as "A58818501".                                                                                                |
+| SSH Private Key                                      | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----".                                                                                              |
+| Stripe Granular Restricted Key                       | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`.                                                                                        |
+| Stripe Standard Secret Key                           | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`.                                                                                            |
+| Sweden Tax                                           | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874".                                                                                              |
+| SWIFT                                                | Detects SWIFT/BIC business identifier codes such as "PMFAUS66".                                                                                                              |
+| Swift                                                | Detects Swift source code.                                                                                                                                                   |
+| Taiwan National Identification Number                | Detects Taiwan national identification numbers such as "W171845961".                                                                                                         |
+| Thai Identity Card Number                            | Detects Thai national identity card numbers such as "4-8547-01245-28-9".                                                                                                     |
+| UAE Passport                                         | Detects United Arab Emirates passport numbers such as "A1234567".                                                                                                            |
+| Union Pay Card Number                                | Detects UnionPay credit card numbers such as "6250941006528599".                                                                                                             |
+| Union Pay Text                                       | Detects mentions of the UnionPay brand name such as "Union Pay".                                                                                                             |
+| United Kingdom National Insurance Number             | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C".                                                                                                        |
+| United Kingdom NHS Number                            | Detects UK NHS patient identification numbers such as "485-585-0454".                                                                                                        |
+| United States ABA Routing Number                     | Detects US ABA bank routing numbers such as "021000021".                                                                                                                     |
+| United States SSN Numeric Detection                  | Detects US Social Security Numbers such as "123-45-6789".                                                                                                                    |
+| United States SSN Text                               | Detects mentions of "SSN" or "social security" as a keyword, such as "social security".                                                                                      |
+| Unsanitized HAR File                                 | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
+| Uruguay ID (CI)                                      | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8".                                                                                     |
+| US Driver's License Number                           | Detects US driver's license numbers such as "CA License: A1234567".                                                                                                          |
+| US Individual Tax Identification Number (ITIN)       | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678".                                                                                          |
+| US Mailing Address                                   | Detects US mailing addresses such as "100 First St, Chicago, IL 60601".                                                                                                      |
+| US Passport Number                                   | Detects US passport numbers such as "A12345678".                                                                                                                             |
+| US Phone Number                                      | Detects US phone numbers such as "555-555-5555".                                                                                                                             |
+| US Physical Address                                  | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601".                                                                               |
+| Visa Card Number                                     | Detects Visa credit card numbers such as "4111 1111 1111 1111".                                                                                                              |
+| Visa Text                                            | Detects mentions of the Visa brand name such as "Visa".                                                                                                                      |
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
index 96398de8d42e757..abd3ab310d2558c 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
@@ -37,10 +37,10 @@ The following secrets are validated with regex.
 
 The following Cloudflare API credentials are validated algorithmically using a checksum. Only credentials generated after [Cloudflare's token format update](/fundamentals/api/get-started/token-formats/) will be matched by these entries.
 
-| Detection entry | Format |
-| --- | --- |
-| Cloudflare User API Key | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum |
-| Cloudflare User API Token | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Detection entry                    | Format                                                                         |
+| ---------------------------------- | ------------------------------------------------------------------------------ |
+| Cloudflare User API Key            | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum  |
+| Cloudflare User API Token          | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 | Cloudflare Account Owned API Token | `cfat_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 
 ## Financial Information
@@ -52,7 +52,6 @@ The following Cloudflare API credentials are validated algorithmically using a c
 
 Credit card numbers begin with a six or eight-digit Issuer Identification Number (IIN) and are followed by up to 23 additional digits. Card verification values (CVVs) are not validated.
 
-
 In the table below, entries use one of three validation methods. [Luhn's algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is a checksum formula used to verify credit card numbers. Entries validated "with checksum" use an arithmetic check specific to that number format. Entries validated "with regex" match a known text pattern without performing a mathematical check.
 
 | Detection entry                  | Notes                                                                             |
@@ -74,9 +73,9 @@ In the table below, entries use one of three validation methods. [Luhn's algorit
 
 The **Unsanitized HAR** predefined profile detects HTTP Archive (HAR) files in traffic that have not been processed by Cloudflare's HAR sanitizer. HAR files frequently contain sensitive data such as session cookies, authorization headers, and other credentials.
 
-| Detection entry       | Notes                                                                                                                           |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| Unsanitized HAR file  | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
+| Detection entry      | Notes                                                                                                                                                              |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Unsanitized HAR file | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
 
 You can use this profile in a Gateway HTTP policy to block HAR file uploads or redirect users to `https://har-sanitizer.pages.dev/` to sanitize the file before uploading. For more information, refer to [common DLP policies](/cloudflare-one/data-loss-prevention/dlp-policies/common-policies/).
 
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
index 2ec67b8a7f2d86d..1df5ea81ecd5b67 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
index 014c621a7fcbb9e..4b180d527caeea5 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
@@ -166,9 +166,9 @@ Email security displays the following details:
 
 #### Cloudy summaries
 
-The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. 
+The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted.
 
-Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). 
+Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values).
 
 **View all signatures** allows you to view all the detections that triggered on the email, including detections that did not determine the final disposition.
 
diff --git a/src/content/docs/cloudflare-one/email-security/reference/index.mdx b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
index ed22d9cc45c63d0..554e42af73200ca 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
index e72de496842e22a..f29fd4a0c946be4 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
@@ -19,4 +19,4 @@ Currently, you can process emails in the following regions:
 - US
 - Germany
 - India
-- Australia
\ No newline at end of file
+- Australia
diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
index 04516541176d46d..67304fed00d84ff 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
@@ -21,8 +21,8 @@ To configure auto-move events:
 5. Under **Auto-moves**, select **Configure**.
 6. For each disposition (malicious, spam, bulk, suspicious, spoof), choose what happens to matching emails:
    - **Soft delete - user recoverable**: Moves the message to the user's **Recoverable Items - Deleted** folder. The user can still find and restore the message. This option is only available for Microsoft 365 customers. Refer to [Microsoft 365 Exchange data deletion](https://learn.microsoft.com/en-us/compliance/assurance/assurance-exchange-online-data-deletion) for more information.
-   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it. 
+   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it.
    - **Move to trash**: Moves the message to the user's trash or deleted items folder. This option is only available for Google Workspace users.
    - **Move to junk**: Moves the message to the user's junk or spam folder.
    - **No action**: Leaves the message where it is. Email security still records the disposition, but does not move the message.
-7. Select **Save**.
\ No newline at end of file
+7. Select **Save**.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
index d4eaee4d21f7a1b..447a71c6bb9e4af 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
@@ -10,11 +10,11 @@ sidebar:
 
 This guide describes how to configure detection settings to mitigate impersonation risks while ensuring legitimate delivery.
 
-Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address. 
+Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address.
 
 For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to mitigate delivery disruptions.
 
-To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific.  In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
+To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific. In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
 
 ## Policy selection criteria
 
@@ -36,4 +36,4 @@ Example use cases:
 
 - Prioritize static IPs: Use known and owned, static IP addresses for relay servers. Avoid [ephemeral IP addresses](https://docs.cloud.google.com/vpc/docs/ip-addresses#ephemeral_and_static_ip_addresses) as their transient nature can lead to policy degradation.
 - Enforce Sender Verification: Always have **Sender Verification (Recommended)** enabled in the Cloudflare dashboard. It validates the originating system's email authentication records (namely [SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), and [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) against the domain to ensure authenticity.
-- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
\ No newline at end of file
+- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
index 8481b73230a9b54..efaa4f6b773fcca 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
index fffa7bf2fdd3e28..7c3b68ba2333939 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="email-security/domain-information" product="cloudflare-one" />
\ No newline at end of file
+<Render file="email-security/domain-information" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
index 4a962408af45bb5..9a9a590d97573b0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
index 0365a23705fb682..b5fed567bea01e0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
index 03b7792d24ac057..d3771d0098d4bb0 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
@@ -21,4 +21,4 @@ To set up PhishNet Microsoft 365:
 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**.
 4. Select **Upload custom apps**.
 5. Choose **Provide link to manifest file** and paste the URL you copied from the Cloudflare One dashboard.
-6. Verify and complete the wizard.
\ No newline at end of file
+6. Verify and complete the wizard.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
index 414eff1eb5c872e..0d1522a54efcba7 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
@@ -27,4 +27,4 @@ You have now successfully installed Cloudflare PhishNet.
 1. In your Gmail web client, open the message you would like to flag as either spam or phish.
 2. Select the PhishNet logo on the side panel.
 3. Under **Select Submission Type**, select **Spam** or **Phish**.
-4. Select **Submit Report**.
\ No newline at end of file
+4. Select **Submit Report**.
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
index 9e049608ac65e75..4190cae0904f56e 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
@@ -15,4 +15,4 @@ To view the destination addresses of user and team submissions:
 3. Select **Settings**.
 4. Go to **Phish submission** > **Submission addresses** > **View**.
 
-The dashboard will display **User submission addresses** and **Team submission addresses**.
\ No newline at end of file
+The dashboard will display **User submission addresses** and **Team submission addresses**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
index c65b4336fa5ad20..43e57d4a1c293fa 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
@@ -15,24 +15,24 @@ import { Markdown } from "~/components";
 
 Before you start the onboarding process, you will have to:
 
-1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline. 
+1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline.
 2. Learn about dispositions, impersonation registry, and submissions.
 3. Know the steps to configure your email environment correctly.
 
 The following table compares features available across API, BCC/Journaling and MX/Inline:
 
-| Feature             	| Microsoft 365                                       	| Google Workspace                  	| Others (On-prem/Cloud)                                   	|
-|---------------------	|-----------------------------------------------------	|-----------------------------------	|----------------------------------------------------------	|
-| Deployment type     	| API and MX                                          	| BCC and MX                        	| MX only                                                  	|
-| API integration     	| Microsoft Graph API                                 	| BCC only                          	| None                                                     	|
-| BCC/Journaling      	| Uses a Journal Rule in the Microsoft Purview portal 	| Uses BCC rules                    	| Uses journaling                                          	|
-| Inline/MX Mode      	| MX records point to Cloudflare                      	| MX records point to Cloudflare    	| MX records point to Cloudflare                           	|
-| Message remediation 	| Auto-moves through Read/Write API                   	| Auto-moves through Read/Write API 	| Messages can be blocked, quarantined, or modified inline 	|
+| Feature             | Microsoft 365                                       | Google Workspace                  | Others (On-prem/Cloud)                                   |
+| ------------------- | --------------------------------------------------- | --------------------------------- | -------------------------------------------------------- |
+| Deployment type     | API and MX                                          | BCC and MX                        | MX only                                                  |
+| API integration     | Microsoft Graph API                                 | BCC only                          | None                                                     |
+| BCC/Journaling      | Uses a Journal Rule in the Microsoft Purview portal | Uses BCC rules                    | Uses journaling                                          |
+| Inline/MX Mode      | MX records point to Cloudflare                      | MX records point to Cloudflare    | MX records point to Cloudflare                           |
+| Message remediation | Auto-moves through Read/Write API                   | Auto-moves through Read/Write API | Messages can be blocked, quarantined, or modified inline |
 
 Note that:
 
 - All email providers support MX/Inline deployment.
-- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or  post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
+- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
 - Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/).
 
 ## 1. Choose a deployment
diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
index 5c704f3a770261e..61054ee69b7887b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
@@ -43,4 +43,4 @@ To stop scanning domains:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**.
-4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
\ No newline at end of file
+4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
index 43b90fbe16e9a31..f61e4bcb70cd12f 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
index 57f5aa4227abd1d..8bb78df403639c3 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
index 327257b4eb0b5e5..ad3849aad352d63 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
@@ -11,4 +11,4 @@ sidebar:
 BCC/Journaling deployment is a post-delivery type of deployment. Cloudflare analyzes emails after they reach the user's inbox. Every time you receive an email, your email provider will send a blind copy to Cloudflare for an analysis.
 
 - Choose [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/) if your email provider is Gmail.
-- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
\ No newline at end of file
+- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
index 943a2e42ca67928..776f45cf8537714 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
index 8ff736556bdbdba..ac23a96bd6a598d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
@@ -95,7 +95,6 @@ To verift that your domain has been added successfully and that your emails are
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**.
 
-
 ## Next steps
 
-<Render file="email-security/enable-logs" product="cloudflare-one" />
\ No newline at end of file
+<Render file="email-security/enable-logs" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
index 4c636aa1972e3b4..6e14bc7bb3cbd1b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
@@ -22,7 +22,6 @@ To use Email security, you will need to have:
 	product="cloudflare-one"
 />
 
-
 ## Manually add domains
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
index f15a938e8733a92..e5945fa7ffe219b 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
@@ -11,6 +11,6 @@ sidebar:
 next: false
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
index 34f65be10df2f54..be6fcfaa82de80d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
@@ -16,7 +16,7 @@ Add all of the following addresses to your mail provider's IP allowlist.
 
 Microsoft 365 does not support IPv6 addresses or the following IPv4 ranges:
 
-- `104.30.32.0/19` 
+- `104.30.32.0/19`
 - `134.195.26.0/23`
 
 If you use Microsoft 365, use the individual `/24` blocks (256 addresses each) listed in [Microsoft 365 `/24` addresses](#microsoft-365-24-addresses) instead.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
index 53963c84381f2fe..fce333e04ebd1b6 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
@@ -10,8 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
index d33970c173669e0..2bcd30388647a00 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
@@ -27,4 +27,4 @@ To set up a partner domain:
 
 To edit a partner domain, select the three dots > **Edit**.
 
-To delete a partner domain, select the three dots > **Delete**.
\ No newline at end of file
+To delete a partner domain, select the three dots > **Delete**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
index 35bc8f11bdcdad3..a1e35434d0580f7 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
@@ -10,8 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
index 7f5428d95fbf8ef..4c76d96d35736ed 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
index 14e7f12e83a674d..e04482e75dcf67e 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
@@ -52,4 +52,4 @@ To view submissions:
 3. Choose from the following submission types:
    - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions.
    - [**User submissions**](/cloudflare-one/email-security/submissions/user-submissions/): View emails your users submitted for submissions.
-   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
\ No newline at end of file
+   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
index aff37d96e27156f..87a9a602b6c10cb 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
@@ -36,4 +36,4 @@ To enable Invalid submission email notifications:
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
-3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
\ No newline at end of file
+3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
diff --git a/src/content/docs/cloudflare-one/faq/devices-faq.mdx b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
index d37af87433794e5..86a6908deaaf164 100644
--- a/src/content/docs/cloudflare-one/faq/devices-faq.mdx
+++ b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
@@ -7,7 +7,6 @@ sidebar:
   order: 6
 head: []
 description: Review frequently asked questions about devices in Cloudflare Zero Trust.
-
 ---
 
 [❮ Back to FAQ](/cloudflare-one/faq/)
@@ -20,8 +19,8 @@ As the Cloudflare One Client has replaced WinDivert with WinTun architecture, al
 
 As our [Network Map](https://www.cloudflare.com/en-gb/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the data center (colo) you are connecting to isn't necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-* Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
-* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+- Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
+- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
 
 ## Why is my public IP address sometimes visible?
 
@@ -50,8 +49,8 @@ An [OS firewall rule](/cloudflare-one/team-and-resources/devices/cloudflare-one-
 
 If your private network is [exposed via Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/):
 
-* Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
-* Verify that the user is allowed through by your Access and Gateway policies.
-* Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
+- Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
+- Verify that the user is allowed through by your Access and Gateway policies.
+- Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
 
 When contacting Cloudflare support, ensure that you include [Cloudflare One Client debug logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/) for your device. These logs will help Cloudflare support understand the overall architecture of your machine and networks.
diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
index 94280945992ed4c..f1c5be808fd91bf 100644
--- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
@@ -133,4 +133,4 @@ In **Gateway insights**, you can view a report on your Gateway firewall policies
 In **CASB**, you can review instances of security issues — such as misconfigurations, unauthorized user activity, and shadow IT — found in your SaaS integrations by [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).
 
 - Integrations by number of findings
-- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
\ No newline at end of file
+- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
diff --git a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
index 2295744544866ab..3ab91476f6fa6d1 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
@@ -24,19 +24,19 @@ To view the AI security report dashboard:
 
 To populate the AI security report dashboard, you must have:
 
-* [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
-* User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
-* [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
+- [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
+- User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
+- [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
 
 ## Available insights
 
 The AI security report dashboard includes the following panels and metrics:
 
-* [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
-* [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
-* [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
-* [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
-* [Access login events to MCP servers](#access-login-events-to-mcp-servers)
+- [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
+- [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
+- [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
+- [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
+- [Access login events to MCP servers](#access-login-events-to-mcp-servers)
 
 ### Top 5 visited AI applications by user count
 
@@ -50,10 +50,10 @@ Use this chart to monitor adoption trends and detect new or unauthorized AI tool
 Reports the total number of AI applications identified and their review statuses.  
 Statuses include:
 
-* Unreviewed — Applications not yet evaluated by administrators.  
-* In Review — Applications currently under review for approval.  
-* Unapproved — Applications that are restricted or blocked.  
-* Approved — Applications explicitly permitted for organizational use.
+- Unreviewed — Applications not yet evaluated by administrators.
+- In Review — Applications currently under review for approval.
+- Unapproved — Applications that are restricted or blocked.
+- Approved — Applications explicitly permitted for organizational use.
 
 ### Data uploaded to Artificial Intelligence applications by status
 
@@ -66,4 +66,4 @@ Displays the number of Model Context Protocol (MCP) servers protected by [Cloudf
 
 ### Access login events to MCP servers
 
-Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
\ No newline at end of file
+Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
diff --git a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
index 475a4c3d35c46ac..7a066e04802a46a 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
@@ -29,20 +29,20 @@ To view the Application Access Report dashboard:
 
 To populate the Application Access Report dashboard, you must have:
 
-* At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
-* Users authenticating to these applications through Cloudflare Access.
+- At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
+- Users authenticating to these applications through Cloudflare Access.
 
 ## Available insights
 
 The Application Access Report dashboard includes the following panels and metrics:
 
-* [Summary of Access activity](#summary-of-access-activity)
-* [Access events](#access-events)
-* [Access decisions by event count](#access-decisions-by-event-count)
-* [Access applications by event count](#access-applications-by-event-count)
-* [Access events by type](#access-events-by-type)
-* [Top counts of event details](#top-counts-of-event-details)
-* [Access admin metrics](#access-admin-metrics)
+- [Summary of Access activity](#summary-of-access-activity)
+- [Access events](#access-events)
+- [Access decisions by event count](#access-decisions-by-event-count)
+- [Access applications by event count](#access-applications-by-event-count)
+- [Access events by type](#access-events-by-type)
+- [Top counts of event details](#top-counts-of-event-details)
+- [Access admin metrics](#access-admin-metrics)
 
 ### Summary of Access activity
 
@@ -55,7 +55,7 @@ You can use this graph to review user authentication activity and detect unusual
 
 ### Access decisions by event count
 
-Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).  
+Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).
 
 ### Access applications by event count
 
@@ -71,11 +71,11 @@ This panel helps administrators understand how users are authenticating across a
 
 Lists the most common Access event attributes, including:
 
-* Application name — Displays the top accessed applications.
-* Identity provider — Shows which identity providers (IdPs) were most used.
-* Users — Lists top users by number of login events.
-* Countries — Displays top countries where users logged in.
-* IP addresses — Lists the top source IPs associated with login events.
+- Application name — Displays the top accessed applications.
+- Identity provider — Shows which identity providers (IdPs) were most used.
+- Users — Lists top users by number of login events.
+- Countries — Displays top countries where users logged in.
+- IP addresses — Lists the top source IPs associated with login events.
 
 These insights help administrators identify usage patterns and trends.
 
@@ -83,7 +83,7 @@ These insights help administrators identify usage patterns and trends.
 
 Provides a summary of Access configurations made by admin in your organization, including:
 
-* Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
-* Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
+- Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
+- Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
 
-This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
\ No newline at end of file
+This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
diff --git a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
index 7768588f1179831..cc397c6684cbb8e 100644
--- a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
@@ -7,5 +7,4 @@ title: MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dex-analysis
 sidebar:
   order: 90
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
index 056e13ea2ec0cca..1309beff1282a3f 100644
--- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
@@ -35,12 +35,12 @@ To view analytics on a per-device level, go to [Device monitoring](/cloudflare-o
 
 - **Connectivity status**: Percentage of devices in a given Cloudflare One Client state.
 
-  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                               |
-  | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                          |
-  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                           |
+  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                                                         |
+  | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                               |
+  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                                |
   | Paused       | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [admin override code](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes). Paused clients will [auto-connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) after a timeout period. |
-  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                            |
+  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                 |
 
 - **Mode**: [Client mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) deployed on the device.
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
index 0823f895e22fb5c..7336bc04cde6cad 100644
--- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
@@ -42,7 +42,7 @@ Review the available selectors and their scope in the following list.
 | **Operating system version** | For specifying an operating system version (use Operator `in`) or versions (use Operator `is`).                                   |
 | **Managed network**          | For specifying users accessing the network from the office (managed network) compared to those accessing remotely.                |
 | **SAML attributes**          | For specifying a value from the [SAML Attribute Assertion](/cloudflare-one/traffic-policies/identity-selectors/#saml-attributes). |
-| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                          |
+| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                 |
 
 ## Add a rule to a test
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
index 15a13b2b8c484f9..d09f0e887f56c41 100644
--- a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
@@ -20,4 +20,8 @@ To control which users or groups run a test, use [DEX rules](/cloudflare-one/ins
 
 ## Export DEX application test logs
 
-<Render file="dex/logpush-export" product="cloudflare-one" params={{ applicationTests: true }} />
+<Render
+	file="dex/logpush-export"
+	product="cloudflare-one"
+	params={{ applicationTests: true }}
+/>
diff --git a/src/content/docs/cloudflare-one/insights/index.mdx b/src/content/docs/cloudflare-one/insights/index.mdx
index 84559d3b901bfca..53baf5cb249a412 100644
--- a/src/content/docs/cloudflare-one/insights/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/index.mdx
@@ -40,18 +40,16 @@ If your device is experiencing connectivity issues, Cloudflare recommends starti
 
 1. Use [Analytics Dashboards](/cloudflare-one/insights/analytics/) to understand trends and for visualizations of your log data.
 
-    Administrators typically start with Analytics Dashboards because they offer:
-
-    - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
-    - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
+   Administrators typically start with Analytics Dashboards because they offer:
+   - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
+   - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
 
 2. Use [Logs](/cloudflare-one/insights/logs/) as needed for event-level verification.
 
-    Use Logs when you need to:
-
-    - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
-    - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
-    - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
+   Use Logs when you need to:
+   - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
+   - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
+   - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
 
 ### User-reported issues
 
@@ -59,4 +57,4 @@ Users may report problems like slow or failing connections to internal apps.
 
 1. Start with [Analytics Dashboards](/cloudflare-one/insights/analytics/) to review whether the issue impacts others.
 2. Check [Logs](/cloudflare-one/insights/logs/) for failed authentication attempts, blocked requests, or unexpected policy matches.
-3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
\ No newline at end of file
+3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
index 304fa8f96f03164..0761b8662b76208 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
@@ -16,18 +16,18 @@ To view admin activity logs, log in to the [Cloudflare dashboard](https://dash.c
 
 ## Explanation of the fields
 
-| Field           | Description                                           | Example Value                                                                      |
-| ----------------| ------------------------------------------------------| -----------------------------------------------------------------------------------|
-| Email           | User who performed the action                         | josephli@cloudflare.com                                                            |
-| Product         | Cloudflare product being modified                     | Tunnel                                                                             |
-| Resource        | Specific resource type within the product             | Route                                                                              |
-| Event           | Action performed (Create, Update, Delete)             | Create                                                                             |
-| Date            | Timestamp of when the action occurred                 | April 30, 2026 • 12:19 AM                                                          |
-| User IP Address | IP address of the user who made the change            | 2a09:bac6:6447:523::83:30                                                          |
-| Interface       | How the change was initiated                          | API                                                                                |
-| Audit record    | Unique identifier for the audit log entry             | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                               |
-| Old value       | Previous configuration state (empty for creates)      | {}                                                                                 |
-| New value       | New configuration state after the change              | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
+| Field           | Description                                      | Example Value                                                                          |
+| --------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------- |
+| Email           | User who performed the action                    | josephli@cloudflare.com                                                                |
+| Product         | Cloudflare product being modified                | Tunnel                                                                                 |
+| Resource        | Specific resource type within the product        | Route                                                                                  |
+| Event           | Action performed (Create, Update, Delete)        | Create                                                                                 |
+| Date            | Timestamp of when the action occurred            | April 30, 2026 • 12:19 AM                                                              |
+| User IP Address | IP address of the user who made the change       | 2a09:bac6:6447:523::83:30                                                              |
+| Interface       | How the change was initiated                     | API                                                                                    |
+| Audit record    | Unique identifier for the audit log entry        | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                                   |
+| Old value       | Previous configuration state (empty for creates) | {}                                                                                     |
+| New value       | New configuration state after the change         | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
 
 ## Export admin activity logs
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
index b2a31ec6e175c94..32b6c971303f04d 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
@@ -30,17 +30,18 @@ To view Gateway activity logs:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Choose a type of Gateway log:
-	- **DNS query logs**
-	- **Network logs**
-	- **HTTP request logs**
-	:::note[Log viewer (beta)]
-	Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
-	:::
+   - **DNS query logs**
+   - **Network logs**
+   - **HTTP request logs**
+     :::note[Log viewer (beta)]
+     Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
+     :::
 3. (Optional) Filter the logs that display in the log viewer. You can filter logs by their timestamp and event details (such as host, URL, user email, policy action, and more).
 
-	:::tip
-	Querying for fewer fields improves log loading performance.
-	:::
+   :::tip
+   Querying for fewer fields improves log loading performance.
+   :::
+
 4. Select an individual timestamp to investigate the event in more detail.
 
 ## Selective logging
@@ -61,16 +62,16 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Basic information
 
-| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                             |
-| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                        |
+| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                                       |
+| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                                  |
 | **Email**             | Email address of the user who registered the Cloudflare One Client where traffic originated from. If a non-identity on-ramp (such as a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)) or machine-level authentication (such as a [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/)) was used, this value will be `non_identity@<team-domain>.cloudflareaccess.com`. |
-| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                      |
-| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                           |
-| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                           |
-| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                    |
+| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                                |
+| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                            |
+| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                                     |
+| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                              |
 
 #### Configuration information
 
@@ -85,14 +86,14 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Identities
 
-| Field                  | Description                                                                                                                                                                                                        |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Field                  | Description                                                                                                                                                                                                                  |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who registered the Cloudflare One Client where traffic originated from.                                                                                                                            |
-| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                              |
+| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                                        |
 | **Registration ID**    | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered for a particular email. The same physical device may have multiple registration IDs.           |
 | **Device name**        | Display name of the device returned by the operating system to the Cloudflare One Client. Typically this is the hostname of a device. Not all devices will have a device name. Device names are not guaranteed to be unique. |
 | **Device ID**          | UUID of the device connected with the Cloudflare One Client. Each physical device in your organization will have a UUID.                                                                                                     |
-| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                |
+| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                          |
 
 #### DNS query details
 
@@ -182,14 +183,14 @@ To log failed connections, use [network session logs](/logs/logpush/logpush-job/
 
 #### Identities
 
-| Field                  | Description                                                                           |
-| ---------------------- | ------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                     |
+| ---------------------- | ----------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user sending the packet. This is generated by the Cloudflare One Client.   |
 | **User ID**            | ID of the user sending the packet. This is generated by the Cloudflare One Client.              |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.           |
-| **Device name**        | Name of the device that sent the packet.                                              |
+| **Device name**        | Name of the device that sent the packet.                                                        |
 | **Device ID**          | ID of the physical device that sent the packet. This is generated by the Cloudflare One Client. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                            |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                      |
 
 #### Network query details
 
@@ -228,7 +229,7 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 | Field                        | Description                                                                                                                                                                                                                                                                                                                              |
 | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Host**                     | Hostname in the HTTP header for the HTTP request. Gateway will log the SNI in this field if it responded to the request with a Do Not Inspect action. If Gateway does not receive the SNI, this field will be empty.                                                                                                                     |
-| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                               |
+| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                     |
 | **Action**                   | The Gateway [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) taken based on the first rule that matched (such as Allow or Block).                                                                                                                                                                                        |
 | **Request ID**               | Unique ID of the request.                                                                                                                                                                                                                                                                                                                |
 | **Time**                     | Date and time of the HTTP request.                                                                                                                                                                                                                                                                                                       |
@@ -252,14 +253,14 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 
 #### Identities
 
-| Field                  | Description                                                                                                                   |
-| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                             |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                    |
 | **User ID**            | ID of the user who made the request. This is generated by the Cloudflare One Client.                                                    |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.                                                   |
-| **Device name**        | Name of the device that made the request.                                                                                     |
+| **Device name**        | Name of the device that made the request.                                                                                               |
 | **Device ID**          | ID of the physical device that made the request. This is generated by the Cloudflare One Client on the device that created the request. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                    |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                              |
 
 #### HTTP query details
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
index bc1f6d84f202733..5a3e6717195a05e 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
@@ -15,6 +15,6 @@ import { DirectoryListing } from "~/components";
 
 The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment.
 
-<DirectoryListing button={true}/>
+<DirectoryListing button={true} />
 
 For additional datasets and long-term log storage, refer to [Logpush](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
index 9a69bac2bfb4fe7..ec364aac8147715 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
@@ -33,7 +33,7 @@ Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/
 | Field               | Description                                                                                                                                                                                                                    |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**           | Email used to register the device with Zero Trust.                                                                                                                                                                             |
-| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                    |
+| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                                |
 | **Registration ID** | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered. The same physical device may have multiple registration IDs if multiple users share the device. |
 
 ### Posture details
diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
index 375008abd658fd5..0d6bfb37f1273e2 100644
--- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
@@ -38,23 +38,23 @@ For more information on supported destinations, refer to [Enable destinations](/
 
 Logpush supports all [dashboard logs](/cloudflare-one/insights/logs/dashboard-logs/) as well as additional datasets not available in the Cloudflare One dashboard. Refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/) for a list of all available fields.
 
-| Dataset                                                                                                    | Description                                                                                                                                              |
-| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                    |
-| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                          |
-| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                |
-| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                             |
-| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                     |
-| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                   |
-| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                          |
-| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                              |
-| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                            |
-| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                          |
-| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                     |
-| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) |
+| Dataset                                                                                                    | Description                                                                                                                                                            |
+| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                                  |
+| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                                        |
+| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                              |
+| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                                           |
+| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                                   |
+| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                                |
+| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                                        |
+| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                                            |
+| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                                          |
+| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                                        |
+| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                                   |
+| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/)               |
 | [WARP Config Changes](/logs/logpush/logpush-job/datasets/account/warp_config_changes/)                     | Event logs that Cloudflare generates whenever a device changes [profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) |
-| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                       |
-| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                    |
+| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                                     |
+| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                                  |
 
 ## Verify regional map application
 
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
index b326012ef5deb96..cc0006a02875a8c 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
@@ -176,7 +176,7 @@ When you validate an R2 bucket, exclude the `access-key-id` and `secret-access-k
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-	<DashButton url="/?to=/:account/r2/overview" />
+   <DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -220,4 +220,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
index f8b03fb96ce715a..26abc473b6c624b 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-one
 sidebar:
   order: 1
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Packet captures allow you to record raw network traffic data passing through Cloudflare's network so you can inspect it offline in tools like Wireshark. This is useful for diagnosing connectivity issues, verifying firewall rules, or investigating unexpected traffic patterns.
 
@@ -35,4 +34,4 @@ Full packet captures will collect new traffic sent to Cloudflare's network after
 
 Refer to the articles in this section to learn how to use packet captures.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
index abe3862c5a9b050..62b2709c8e9fc6c 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
@@ -78,14 +78,14 @@ Flag organization access issues to help enforce best practices.
 
 <Render file="casb/data-loss-prevention" product="cloudflare-one" />
 
-| Finding type                                                  | Severity |
-| ------------------------------------------------------------- | -------- |
-| Anthropic: Downloadable File with DLP Profile match           | High     |
-| Anthropic: Claude Chat User Prompt with DLP Profile match     | High     |
-| Anthropic: Claude Chat Assistant Response with DLP Profile match | High  |
-| Anthropic: Claude Chat Uploaded File with DLP Profile match   | High     |
-| Anthropic: Claude Chat Generated File with DLP Profile match  | High     |
-| Anthropic: Claude Project File with DLP Profile match         | High     |
-| Anthropic: Claude Project Document with DLP Profile match     | High     |
-| Anthropic: Claude Chat Artifact with DLP Profile match        | High     |
-| Anthropic: Claude Project Instructions with DLP Profile match | High     |
+| Finding type                                                     | Severity |
+| ---------------------------------------------------------------- | -------- |
+| Anthropic: Downloadable File with DLP Profile match              | High     |
+| Anthropic: Claude Chat User Prompt with DLP Profile match        | High     |
+| Anthropic: Claude Chat Assistant Response with DLP Profile match | High     |
+| Anthropic: Claude Chat Uploaded File with DLP Profile match      | High     |
+| Anthropic: Claude Chat Generated File with DLP Profile match     | High     |
+| Anthropic: Claude Project File with DLP Profile match            | High     |
+| Anthropic: Claude Project Document with DLP Profile match        | High     |
+| Anthropic: Claude Chat Artifact with DLP Profile match           | High     |
+| Anthropic: Claude Project Instructions with DLP Profile match    | High     |
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
index a4f8fc32d81828a..9b59aa70fcbddaa 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
@@ -30,4 +30,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot-fedramp",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
index 6c36357bcb412de..b3db2aa1d185051 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
@@ -22,4 +22,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
index 9e0e96c4c48ecff..e82f7aac39559b8 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
@@ -60,7 +60,7 @@ https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
 | `name`         | `${user:name}`       |
 | `surName`      | `${user:familyName}` |
 
-| `givenName`    | `${user:givenName}`  |
+| `givenName` | `${user:givenName}` |
 
 ![Configuring attribute statements in IAM Identity Center](~/assets/images/cloudflare-one/identity/aws/aws-saml-attributes.png)
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
index b11fbe6575bd942..d01bcec09cbb731 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
@@ -46,8 +46,8 @@ Make a `POST` request to the [Identity Providers](/api/resources/zero_trust/subr
 
 ## Configuration options
 
-| Option | Description | Default |
-| --- | --- | --- |
+| Option                          | Description                                                                                                                                                                  | Default  |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
 | **Restrict to account members** | When enabled, only users who are members of your Cloudflare account can authenticate. When disabled, any Cloudflare user can authenticate (subject to your Access policies). | Disabled |
 
 ## Use Cloudflare account membership in policies
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
index f15160944863211..c9d7965c3fd2706 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
@@ -12,7 +12,7 @@ import { Render } from "~/components";
 
 Use these steps to set up Facebook as your identity provider.
 
-1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one. 
+1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one.
 
 2. Select **Create App** at the top-right. The **Create an app** card displays.
 
@@ -42,7 +42,7 @@ Use these steps to set up Facebook as your identity provider.
 
 15. Select **Settings**, and ensure that **Use Strict Mode for redirect URIs** slider is set to **Yes**.
 
-15. In the **Valid OAuth Redirect URIs** field, enter the following URL:
+16. In the **Valid OAuth Redirect URIs** field, enter the following URL:
 
     ```txt
     https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
@@ -50,7 +50,7 @@ Use these steps to set up Facebook as your identity provider.
 
     <Render file="find-team-name" product="cloudflare-one" />
 
-16. Select **Save Changes**.
+17. Select **Save Changes**.
 
 To test that your connection is working, follow the steps on [SSO Integration](/cloudflare-one/integrations/identity-providers/#test-idps-in-cloudflare-one).
 
@@ -65,4 +65,4 @@ To test that your connection is working, follow the steps on [SSO Integration](/
 	"type": "facebook",
 	"name": "my example idp"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
index 8ffadf28cdfd7c6..583bae2a4359175 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
@@ -55,8 +55,8 @@ To configure GitHub access in both GitHub and Cloudflare One:
 14. Select **Save**.
 
 15. Select **Finish setup** to launch a GitHub authorization page. You will be asked to grant the following permissions to Cloudflare Access:
-	- Organizations and teams (read-only)
-	- Email addresses (read-only)
+    - Organizations and teams (read-only)
+    - Email addresses (read-only)
 
 16. Select **Authorize**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
index 643ef76b062e609..e8868c73cbac521 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
@@ -10,7 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-
 Cloudflare One integrates with your organization's identity provider to apply Cloudflare One and Secure Web Gateway policies. If you work with partners, contractors, or other organizations, you can integrate multiple identity providers simultaneously.
 
 As an alternative to configuring an identity provider, Cloudflare One can send a [one-time PIN (OTP)](/cloudflare-one/integrations/identity-providers/one-time-pin/) to approved email addresses. No configuration needed — simply add a user's email address to an [Access policy](/cloudflare-one/access-controls/policies/) and to the group that allows your team to reach the application. You can simultaneously configure an OTP and an identity provider to allow users to use their own authentication method.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
index 2ef2f3ad811f160..88472d050f21f91 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
@@ -78,13 +78,13 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
 
    ![Configuring the Groups claim filter in Okta](~/assets/images/cloudflare-one/identity/okta/okta-2.png)
 
-
 9. Set **Groups claim filter** to _Matches regex_ and its value to `.*`.
 
 :::note[Token claim expressions]
+
 - Groups managed outside of Okta (for example, Microsoft Entra ID or Google groups) may require different regex values. For more information, refer to the Okta documentation on [Groups Claims](https://support.okta.com/help/s/article/Why-isnt-my-Groups-claim-returning-Active-Directory-groups) and [OpenID Connect Claims](https://support.okta.com/help/s/article/Can-we-retrieve-both-Active-Directory-and-Okta-groups-in-OpenID-Connect-claims).
 - To configure more complex expressions, refer to Okta's [token claims documentation](https://help.okta.com/okta_help.htm?type=oie&locale=en&id=federated-claims-overview).
-:::
+  :::
 
 10. In the **General** tab, copy the **Client ID** and **Client secret**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
index 6e57a4c17621c6c..9d30c743f2b37e0 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
@@ -46,7 +46,6 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C
    | `givenName`           | Given Name     |
    | `surName`             | Family Name    |
 
-
    These [SAML attributes](/cloudflare-one/integrations/identity-providers/generic-saml/#saml-attributes) tell Cloudflare Access who the user is.
 
 9. Set the application to **Active**.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
index 1dfbd4cc2c93d21..698b9665695a37d 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
@@ -37,12 +37,10 @@ To set up Signed AuthN requests:
    Ensure that your IdP validation uses the most recent certificate. Cloudflare Access routinely rotates the public key as a security measure.
 
    Cloudflare Access uses a certificate that includes the following 2 distinguished name fields:
-
    - **Issuer Distinguished Name** - `CN=cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
    - **Subject Distinguished Name** - `CN=*.cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
 
    Most IdP configurations require 3 components to enforce AuthN signature verification:
-
    - **Certificate issuer [distinguished name (DN)](https://knowledge.digicert.com/generalinformation/INFO1745.html)**
    - **Certificate subject distinguished name**
    - **Public certificate**
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
index 164e679ec887af6..470285aa6aaa407 100644
--- a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
@@ -18,8 +18,8 @@ Service-to-service integrations allow the Cloudflare One Client to get device po
 
 ## Supported operating systems
 
-| Device posture check                                                                        | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| ------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| Device posture check                                                                    | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| --------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
 | [Custom integration](/cloudflare-one/integrations/service-providers/custom/)            | ✅    | ✅      | ✅    | ✅  | ✅               |
 | [Crowdstrike](/cloudflare-one/integrations/service-providers/crowdstrike/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
 | [Kolide](/cloudflare-one/integrations/service-providers/kolide/)                        | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
index e973af0760d4ab3..ff02d7946387387 100644
--- a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
@@ -11,13 +11,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-one-connectivity-options"
-  product="networking-services"
-  params={{
-    unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-    connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
-    cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-    onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/"
-  }}
+	file="cloudflare-one-connectivity-options"
+	product="networking-services"
+	params={{
+		unifiedRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
index 7e26c4da5a75875..c69c567e9be0058 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
@@ -37,6 +37,7 @@ flowchart LR
   node --> db
   node --> printer
 ```
+
 ## Manage routes
 
 Use CIDR routes to forward traffic from your mesh node to devices on your local network.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
index 4d20096eb33e2fd..98f1c0ce87d79e1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
@@ -15,8 +15,8 @@ Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`,
 
 The following table lists the cipher suites supported by `cloudflared`:
 
-| Protocol support | Cipher suites |
-|------------------|----------------|
-| TLS 1.3 only | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256` |
-| TLS 1.2 only | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
-| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA` |
+| Protocol support            | Cipher suites                                                                                                                                                                                                                                                                              |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| TLS 1.3 only                | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256`                                                                                                                                                                                                 |
+| TLS 1.2 only                | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
+| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`                                                                                                                     |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
index f60f0eecf786013..e0edd83ad74e895 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 3
 ---
 
-import { DirectoryListing  } from "~/components";
+import { DirectoryListing } from "~/components";
 
 After [creating your Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/), you can configure various aspects of how `cloudflared` runs and connects your infrastructure to Cloudflare's network. This section covers advanced configuration options to optimize tunnel performance, security, and availability.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
index b6e4ec71f36882d..19d5f191ab29920 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
@@ -13,11 +13,13 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/origin-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
-  }}
+	file="tunnel/origin-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+		validatingJwtURL:
+			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
index 3b9c067dddd114d..f6088ef1050edb8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
@@ -65,70 +65,70 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-	<Tabs syncKey="dashPlusAPI">
-	<TabItem label="Dashboard">
-	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
-	2. Select a `cloudflared` tunnel and select **Edit**.
-	3. Select **Refresh token**.
-	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
-
-	</TabItem>
-	<TabItem label="API">
-		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
-
-				```sh
-				openssl rand -base64 32
-				```
-
-				```sh output
-				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
-				```
-
-	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
-
-			<APIRequest
-				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-				method="PATCH"
-				json={{
-					name: "Example tunnel",
-					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
-				}}
-			/>
-
-			```sh output {18}
-			{
-				"success": true,
-				"errors": [],
-				"messages": [],
-				"result": {
-					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
-					"account_tag": "699d98642c564d2e855e9661899b7252",
-					"created_at": "2024-12-04T22:03:26.291225Z",
-					"deleted_at": null,
-					"name": "Example tunnel",
-					"connections": [],
-					"conns_active_at": null,
-					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
-					"tun_type": "cfd_tunnel",
-					"metadata": {},
-					"status": "inactive",
-					"remote_config": true,
-					"token": "eyJhIjoiNWFiNGU5Z..."
-				}
-			}
-			```
-
-	3.  Copy the `token` value shown in the output.
-
-	</TabItem>
-	</Tabs>
-
-	After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
+   <Tabs syncKey="dashPlusAPI">
+   	<TabItem label="Dashboard">
+   	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
+   	2. Select a `cloudflared` tunnel and select **Edit**.
+   	3. Select **Refresh token**.
+   	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+   
+   	</TabItem>
+   	<TabItem label="API">
+   		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
+   
+   				```sh
+   				openssl rand -base64 32
+   				```
+   
+   				```sh output
+   				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
+   				```
+   
+   	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
+   
+   			<APIRequest
+   				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+   				method="PATCH"
+   				json={{
+   					name: "Example tunnel",
+   					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
+   				}}
+   			/>
+   
+   			```sh output {18}
+   			{
+   				"success": true,
+   				"errors": [],
+   				"messages": [],
+   				"result": {
+   					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
+   					"account_tag": "699d98642c564d2e855e9661899b7252",
+   					"created_at": "2024-12-04T22:03:26.291225Z",
+   					"deleted_at": null,
+   					"name": "Example tunnel",
+   					"connections": [],
+   					"conns_active_at": null,
+   					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
+   					"tun_type": "cfd_tunnel",
+   					"metadata": {},
+   					"status": "inactive",
+   					"remote_config": true,
+   					"token": "eyJhIjoiNWFiNGU5Z..."
+   				}
+   			}
+   			```
+   
+   	3.  Copy the `token` value shown in the output.
+   
+   	</TabItem>
+   	</Tabs>
+
+   After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
 2. On half of your `cloudflared` replicas, reinstall the `cloudflared` service with the new token. For example, on a Linux host:
 
    ```sh
-	 sudo cloudflared service uninstall
+    sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
@@ -140,9 +140,9 @@ To rotate a tunnel token:
 
    While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
-5. Wait 10 minutes for traffic to route through the new connectors.
+4. Wait 10 minutes for traffic to route through the new connectors.
 
-6. Repeat steps 2, 3, and 4 for the second half of the replicas.
+5. Repeat steps 2, 3, and 4 for the second half of the replicas.
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
@@ -163,7 +163,7 @@ If your tunnel token is compromised, we recommend taking the following steps:
 3. On each `cloudflared` replica, update `cloudflared` to use the new token. For example, on a Linux host:
 
    ```sh
-	 sudo cloudflared service uninstall
+    sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
index 6840e8a166897b2..c545b148afb32c3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
@@ -14,15 +14,21 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/run-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    usageMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    tunnelWithFirewallURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
-    tunnelPermissionsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
-    createRemoteTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
-    faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/"
-  }}
+	file="tunnel/run-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		usageMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		tunnelWithFirewallURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
+		tunnelPermissionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
+		createRemoteTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
+		faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
index 0a7cbccf1dcbcbc..81564acce0df5df 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
@@ -32,7 +32,10 @@ When `cloudflared` receives a request from a device, it uses the ports on the ho
 - `cloudflared` should be deployed on a dedicated host machine. This model is typically appropriate, but there may be serverless or clustered workflows where a dedicated host is not possible.
 - The host machine should allocate 50,000 ports to be available for use by the `cloudflared` service. The remaining ports are reserved for system administrative processes.
 
-<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
+<Render
+	file="tunnel/availability/port-configuration"
+	product="cloudflare-one"
+/>
 
 ### Private DNS
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
index 5954dd3c2bbff27..73321967dcd5876 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
@@ -35,22 +35,29 @@ Ensure port `7844` is allowed for both TCP and UDP protocols (for `http2` and `q
 <Render file="tunnel/firewall/required-ports" product="cloudflare-one" />
 
 #### SNI-enforcing firewalls
+
 <Render file="tunnel/firewall/sni-hostnames" product="cloudflare-one" />
 
 ### Region US
 
 <Render
-  file="tunnel/firewall/us-region-ports"
-  product="cloudflare-one"
-  params={{ regionURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region" }}
+	file="tunnel/firewall/us-region-ports"
+	product="cloudflare-one"
+	params={{
+		regionURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region",
+	}}
 />
 
 ### Region FedRAMP High
 
 <Render
-  file="tunnel/firewall/fedramp-high-ports"
-  product="cloudflare-one"
-  params={{ tunnelTokenURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/" }}
+	file="tunnel/firewall/fedramp-high-ports"
+	product="cloudflare-one"
+	params={{
+		tunnelTokenURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/",
+	}}
 />
 
 ### Optional
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
index 57b31886ddd0a26..a02784740a89917 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Deploy Cloudflare Tunnel in your environment — from cloud VMs to Kubernetes clusters, with Infrastructure as Code support.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
index 1c27eaad46459cc..2e42733bf93cb6e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
@@ -86,7 +86,6 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
-
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
index 60b688f0c55e95a..6dad6b29b8df2dc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
@@ -31,12 +31,12 @@ import { Render } from "~/components";
 
 ## Manage private networks
 
-| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cloudflared tunnel route ip add <IP/CIDR> <NAME or UUID>` | Adds any network route space (represented as a CIDR) to your routing table. That network space becomes reachable for requests egressing from a user's machine as long as it is using the Cloudflare One Client and is enrolled in the same account that is running the tunnel chosen here. Further, those requests will be proxied to the specified tunnel, and reach an IP in the given CIDR, as long as that IP is reachable from the tunnel. To assign the IP route to a specific [Virtual Network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/), use the `--vnet` option. |
-| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | `cloudflared tunnel route ip delete`                       | Deletes the row for a given CIDR from your routing table. That portion of your network will no longer be reachable by the Cloudflare One Client.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
index e79d92232542499..75fdb3581cab640 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 102
 head: []
 description: View associated copyrights.
-
 ---
 
-***
+---
 
 [https://github.com/BurntSushi/toml](https://github.com/BurntSushi/toml)
 
@@ -36,7 +35,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/Sirupsen/logrus](https://github.com/Sirupsen/logrus)
 
@@ -62,7 +61,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/beorn7/perks/](https://github.com/beorn7/perks/)
 
@@ -87,7 +86,7 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-***
+---
 
 [https://github.com/certifi/gocertifi](https://github.com/certifi/gocertifi)
 
@@ -95,7 +94,7 @@ This Source Code Form is subject to the terms of the Mozilla Public License,
 v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain
 one at [http://mozilla.org/MPL/2.0/](http://mozilla.org/MPL/2.0/).
 
-***
+---
 
 [https://github.com/coreos/go-oidc/](https://github.com/coreos/go-oidc/)
 [https://github.com/coreos/go-systemd/](https://github.com/coreos/go-systemd/)
@@ -306,7 +305,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/facebookgo/grace](https://github.com/facebookgo/grace)
 
@@ -319,14 +318,14 @@ Copyright (c) 2015, Facebook, Inc. All rights reserved.
 Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-* Redistributions of source code must retain the above copyright notice, this
+- Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-* Redistributions in binary form must reproduce the above copyright notice,
+- Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-* Neither the name Facebook nor the names of its contributors may be used to
+- Neither the name Facebook nor the names of its contributors may be used to
   endorse or promote products derived from this software without specific
   prior written permission.
 
@@ -341,7 +340,7 @@ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/getsentry/raven-go](https://github.com/getsentry/raven-go)
 
@@ -352,13 +351,13 @@ Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
 met:
 
-* Redistributions of source code must retain the above copyright
+- Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the above
+- Redistributions in binary form must reproduce the above
   copyright notice, this list of conditions and the following disclaimer
   in the documentation and/or other materials provided with the
   distribution.
-* Neither the name of Apollic Software, LLC nor the names of its
+- Neither the name of Apollic Software, LLC nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 
@@ -374,7 +373,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/glycerine/rbtree](https://github.com/glycerine/rbtree)
 
@@ -398,7 +397,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/golang/protobuf](https://github.com/golang/protobuf)
 
@@ -434,7 +433,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
 [https://github.com/lib/pq](https://github.com/lib/pq)
 
@@ -447,9 +446,9 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-***
+---
 
-[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\\_protobuf\\_extensions/pbutil)
+[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\_protobuf\_extensions/pbutil)
 
 ```
                              Apache License
@@ -659,7 +658,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/mitchellh/go-homedir](https://github.com/mitchellh/go-homedir)
 
@@ -685,7 +684,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
-***
+---
 
 [https://github.com/pkg/errors](https://github.com/pkg/errors)
 
@@ -695,10 +694,10 @@ All rights reserved.
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
 
-* Redistributions of source code must retain the above copyright notice, this
+- Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-* Redistributions in binary form must reproduce the above copyright notice,
+- Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
@@ -713,10 +712,10 @@ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-***
+---
 
-[https://github.com/prometheus/client\_golang](https://github.com/prometheus/client_golang)
-[https://github.com/prometheus/client\_model](https://github.com/prometheus/client_model)
+[https://github.com/prometheus/client_golang](https://github.com/prometheus/client_golang)
+[https://github.com/prometheus/client_model](https://github.com/prometheus/client_model)
 [https://github.com/prometheus/common](https://github.com/prometheus/common)
 [https://github.com/prometheus/procfs](https://github.com/prometheus/procfs)
 
@@ -928,7 +927,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://github.com/urfave/cli](https://github.com/urfave/cli)
 
@@ -954,7 +953,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-***
+---
 
 [https://github.com/go-yaml/yaml](https://github.com/go-yaml/yaml)
 
@@ -1166,7 +1165,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
-***
+---
 
 [https://zombiezen.com/go/capnproto2](https://zombiezen.com/go/capnproto2)
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
index c3079b110404278..6299a916a068aac 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
@@ -6,7 +6,6 @@ products:
 title: License
 sidebar:
   order: 51
-
 ---
 
 Apache License
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
index e880dc05a8955b9..1004578cbdb1b59 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
@@ -30,12 +30,12 @@ Follow this guide to set up a Cloudflare Tunnel using the API.
 Make a `POST` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/create/) endpoint:
 
 <APIRequest
-  path="/accounts/{account_id}/cfd_tunnel"
-  method="POST"
-  json={{
-    name: "api-tunnel",
-    config_src: "cloudflare",
-  }}
+	path="/accounts/{account_id}/cfd_tunnel"
+	method="POST"
+	json={{
+		name: "api-tunnel",
+		config_src: "cloudflare",
+	}}
 />
 
 ```sh output
@@ -80,46 +80,47 @@ Before you publish an application through your tunnel, you must:
 
 Follow these steps to publish an application to the Internet. If you are looking to connect a private resource, skip to the [Connect a network](#3b-connect-a-network) section.
 
-1. Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
-
-		<APIRequest
-			path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
-			method="PUT"
-			json={{
-				config: {
-					ingress: [
-						{
-							hostname: "app.example.com",
-							service: "http://localhost:8001",
-							originRequest: {},
-						},
-						{
-							service: "http_status:404",
-						},
-					],
-				},
-			}}
-		/>
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
-
-   Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
-
-2. [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
-
-		<APIRequest
-			path="/zones/{zone_id}/dns_records"
-			method="POST"
-			json={{
-				type: "CNAME",
-				proxied: true,
-				name: "app.example.com",
-				content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
-			}}
-		/>
-
-   This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
+1.  Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
+
+        <APIRequest
+        	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
+        	method="PUT"
+        	json={{
+        		config: {
+        			ingress: [
+        				{
+        					hostname: "app.example.com",
+        					service: "http://localhost:8001",
+        					originRequest: {},
+        				},
+        				{
+        					service: "http_status:404",
+        				},
+        			],
+        		},
+        	}}
+        />
+
+    :::note
+    If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+    :::
+
+    Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
+
+2.  [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
+
+        <APIRequest
+        	path="/zones/{zone_id}/dns_records"
+        	method="POST"
+        	json={{
+        		type: "CNAME",
+        		proxied: true,
+        		name: "app.example.com",
+        		content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
+        	}}
+        />
+
+    This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
 
 This application will be publicly available on the Internet once you [run the tunnel](#4-install-and-run-the-tunnel). To allow or block specific users, [create an Access application](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/).
 
@@ -128,13 +129,13 @@ This application will be publicly available on the Internet once you [run the tu
 To connect a private network through your tunnel, [add a tunnel route](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/create/):
 
 <APIRequest
-  path="/accounts/{account_id}/teamnet/routes"
-  method="POST"
-  json={{
-    network: "172.16.0.0/16",
-    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-    comment: "Example private network route",
-  }}
+	path="/accounts/{account_id}/teamnet/routes"
+	method="POST"
+	json={{
+		network: "172.16.0.0/16",
+		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+		comment: "Example private network route",
+	}}
 />
 
 `cloudflared` can now route traffic to these destination IPs. To configure Zero Trust policies and connect as a user, refer to [Connect private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/).
@@ -150,11 +151,11 @@ Install `cloudflared` on your server and run the tunnel using the `token` value
 To check if the tunnel is serving traffic:
 
 <APIRequest
-  path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-  method="GET"
-  parameters={{
-    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-  }}
+	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+	method="GET"
+	parameters={{
+		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+	}}
 />
 
 ```sh output
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
index 87b44a017b40937..18e2da263fc28c1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
@@ -18,7 +18,11 @@ Follow this step-by-step guide to create your first [remotely-managed tunnel](/c
 
 ## 1. Create a tunnel
 
-<Stream id="4b75ad2aa58700602e94b148827687a2" title="How to set up Cloudflare Tunnel" thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png" />
+<Stream
+	id="4b75ad2aa58700602e94b148827687a2"
+	title="How to set up Cloudflare Tunnel"
+	thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png"
+/>
 
 <Render file="tunnel/create-tunnel" product="cloudflare-one" />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
index ca65ff18a9887ff..2482ef654c8cfb8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Set up your first tunnel
-
 ---
 
-import { DirectoryListing, GlossaryTooltip } from "~/components"
+import { DirectoryListing, GlossaryTooltip } from "~/components";
 
 To create and manage tunnels, you will need to install and authenticate <GlossaryTooltip term="cloudflared"><code>cloudflared</code></GlossaryTooltip> on your origin server. `cloudflared` is what connects your server to Cloudflare's global network.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
index 017e02c4b363879..6dda076ed46e587 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
@@ -13,8 +13,8 @@ tags:
 
 import { Render, Stream } from "~/components";
 
-:::note[Looking to expose public applications?] 
-This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel). 
+:::note[Looking to expose public applications?]
+This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel).
 :::
 
 Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (`cloudflared`) creates [outbound-only connections](#outbound-only-connections) to Cloudflare's global network. Cloudflare Tunnel can connect HTTP web servers, [SSH servers](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/), [remote desktops](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/), and other protocols safely to Cloudflare. This way, your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
index 25b86d04e55286d..d346bec2114ef0d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Monitor tunnels
 sidebar:
   order: 9
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
index a23a3c04da466a9..90b446cff03deba 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
@@ -6,10 +6,9 @@ products:
 title: Notifications
 sidebar:
   order: 1
-
 ---
 
-import { AvailableNotifications } from "~/components"
+import { AvailableNotifications } from "~/components";
 
 Administrators can receive an alert when Cloudflare Tunnels in an account change their health or deployment status. Notifications can be delivered via email, webhook, and third-party services.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
index b2dd6df9595c190..e80b571a1bbc009 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
@@ -24,9 +24,9 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 4. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/) for this tunnel route. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
 
-	:::note
-	To create a new virtual network, select **Manage virtual networks**.
-	:::
+   :::note
+   To create a new virtual network, select **Manage virtual networks**.
+   :::
 
 ## 2. Set up the client
 
@@ -34,7 +34,11 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ## 3. Route private network IPs through the Cloudflare One Client
 
-<Render file="tunnel/warp-to-tunnel-route-ips" product="cloudflare-one" params={{ one: "private network"}}/>
+<Render
+	file="tunnel/warp-to-tunnel-route-ips"
+	product="cloudflare-one"
+	params={{ one: "private network" }}
+/>
 
 ## 4. (Recommended) Filter network traffic with Gateway
 
@@ -46,7 +50,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ### Zero Trust policies
 
-<Render file="tunnel/catch-all-policy" product="cloudflare-one"/>
+<Render file="tunnel/catch-all-policy" product="cloudflare-one" />
 
 If you have applications clearly defined by IPs or hostnames, we recommend [creating an Access application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) and managing user access alongside your SaaS and other web apps. Alternatively, if you prefer to secure a private network using a traditional firewall model, you can build Gateway network and DNS policies for IP ranges and domains.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
index 9322c427b9241f5..03dd3b5c2c280f9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
@@ -18,5 +18,6 @@ On the client side, end users connect to Cloudflare's global network using the C
 ![Diagram displaying connections between a device, Cloudflare, and a private network.](~/assets/images/cloudflare-one/connections/private-ips-diagram.png)
 
 To enable remote access to your private network, refer to the following guides:
+
 - [**Connect a private hostname**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/): Route network traffic to an internal application using its hostname.
-- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
\ No newline at end of file
+- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
index 180ab16892b1bcf..f4e9849be0a0224 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 By default, all DNS requests on the user device are resolved by Cloudflare's [public DNS resolver](/1.1.1.1/) except for common top level domains used for local resolution (such as `localhost`). You can connect an internal DNS resolver to Cloudflare and use it to resolve non-publicly routed domains.
 
@@ -18,24 +18,23 @@ By default, all DNS requests on the user device are resolved by Cloudflare's [pu
 
 To resolve private DNS queries:
 
-1. [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
+1.  [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
 
-2. Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
+2.  Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
 
-		:::note
+        :::note
 
-		Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
+        Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
 
-		:::
+        :::
 
-3. Route specific DNS queries to your internal DNS resolver using one of the following options:
+3.  Route specific DNS queries to your internal DNS resolver using one of the following options:
+    - [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
+    - Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
 
-	- [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
-	- Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
+4.  [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
 
-4. [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
-
-5. Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
+5.  Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
 
 The Cloudflare One Client will now send DNS queries to your internal DNS resolver for resolution. To learn more, refer to [How the Cloudflare One Client handles DNS requests](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/#how-the-warp-client-handles-dns-requests).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
index 98430c7fdc1b90a..99d934881a0f10d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
@@ -17,13 +17,14 @@ import { Render } from "~/components";
 ## Create a DNS record
 
 <Render
-  file="tunnel/dns-records-create"
-  product="cloudflare-one"
-  params={{
-    certPemURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem"
-  }}
+	file="tunnel/dns-records-create"
+	product="cloudflare-one"
+	params={{
+		certPemURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem",
+	}}
 />
 
 ## Cloudflare settings
 
-<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
\ No newline at end of file
+<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
index 17cb132130adfc8..f658fb166750775 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
@@ -15,10 +15,12 @@ import { Render } from "~/components";
 When you [add a published application route](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application) to a Cloudflare Tunnel, you are instructing Cloudflare to proxy requests for your public hostname to a service running privately behind `cloudflared`.
 
 <Render
-  file="tunnel/protocols-table"
-  product="cloudflare-one"
-  params={{
-    disableTlsVerificationURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
-    locallyManagedTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications"
-  }}
+	file="tunnel/protocols-table"
+	product="cloudflare-one"
+	params={{
+		disableTlsVerificationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
+		locallyManagedTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
index 05468c98e98ec02..cbb16832f033141 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
@@ -25,12 +25,14 @@ When you add a [published application route](/cloudflare-one/networks/connectors
 ### Create a load balancer
 
 <Render
-  file="tunnel/availability/load-balancer-create"
-  product="cloudflare-one"
-  params={{
-    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-    tunnelIdLocation: "the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**"
-  }}
+	file="tunnel/availability/load-balancer-create"
+	product="cloudflare-one"
+	params={{
+		publishedAppRouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+		tunnelIdLocation:
+			"the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**",
+	}}
 />
 
 Refer to the [Load Balancing documentation](/load-balancing/) for more details on load balancer settings and configurations.
@@ -79,6 +81,7 @@ graph LR
 ```
 
 As shown in the diagram, a typical setup includes:
+
 - A dedicated Cloudflare Tunnel per data center.
 - One load balancer pool per tunnel. The load balancer hostname is set to the user-facing application hostname (`app.example.com`).
 - One load balancer endpoint per pool. The endpoint host header is set to the `cloudflared` published application hostname (`server1.example.com`)
@@ -146,12 +149,12 @@ Here is an example of what your DNS records will look like before and after sett
 | CNAME | app1 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app2 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app1 | `<UUID_2>.cfargotunnel.com` |
-| CNAME | app2 | `<UUID_2>.cfargotunnel.com`  |
+| CNAME | app2 | `<UUID_2>.cfargotunnel.com` |
 
 **After**:
 | Type | Name | Content |
 | ---- | ---- | ------- |
-| LB   | `lb.example.com` | n/a |
+| LB | `lb.example.com` | n/a |
 | CNAME | app1 | `lb.example.com` |
 | CNAME | app2 | `lb.example.com` |
 
@@ -160,11 +163,12 @@ Here is an example of what your DNS records will look like before and after sett
 ### Monitors and TCP tunnel origins
 
 <Render
-  file="tunnel/availability/load-balancer-tcp-monitors"
-  product="cloudflare-one"
-  params={{
-    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application"
-  }}
+	file="tunnel/availability/load-balancer-tcp-monitors"
+	product="cloudflare-one"
+	params={{
+		publishedAppRouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+	}}
 />
 
 ### Session affinity and replicas
@@ -174,9 +178,10 @@ The load balancer does not distinguish between [replicas](/cloudflare-one/networ
 ### Local connection preference
 
 <Render
-  file="tunnel/availability/load-balancer-local-connection"
-  product="cloudflare-one"
-  params={{
-    replicasURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/"
-  }}
+	file="tunnel/availability/load-balancer-local-connection"
+	product="cloudflare-one"
+	params={{
+		replicasURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
index d9c0787deeffdfa..ee3c9509de79961 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
@@ -74,5 +74,4 @@ If you see an error with the title `This site can't provide a secure connection`
 
 If you added a [multi-level subdomain](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) as Cloudflare's Universal certificate will not cover the public hostname by default.
 
-
 For more information on Tunnel errors, view your [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) or [contact Cloudflare Support](/support/contacting-cloudflare-support/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
index 04c3693aabbaeb1..0c3a0e8a6720af6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
@@ -28,44 +28,53 @@ The steps for getting diagnostic logs depend on your `cloudflared` deployment en
 These instructions apply to remotely-managed and locally-managed tunnels running directly on the host machine.
 
 <Render
-  file="tunnel/diagnostics/host-environment"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/host-environment"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address",
+	}}
 />
 
 ### Docker
 
 <Render
-  file="tunnel/diagnostics/docker"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/docker"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		defaultMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
+	}}
 />
 
 ### Kubernetes
 
 <Render
-  file="tunnel/diagnostics/kubernetes"
-  product="cloudflare-one"
-  params={{
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
-  }}
+	file="tunnel/diagnostics/kubernetes"
+	product="cloudflare-one"
+	params={{
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+		defaultMetricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
+	}}
 />
 
 ## cloudflared-diag files
 
 <Render
-  file="tunnel/diagnostics/tunnel-diag-file"
-  product="cloudflare-one"
-  params={{
-    runParametersURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
-    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
-    loglevelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server"
-  }}
+	file="tunnel/diagnostics/tunnel-diag-file"
+	product="cloudflare-one"
+	params={{
+		runParametersURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
+		logsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+		metricsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
+		loglevelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
index 281adab55837939..61105e303be197e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 10
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore resources to help you resolve issues with Cloudflare Tunnel connectivity and configuration.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
index 465c95783571898..19b86f3981d6630 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
@@ -7,12 +7,11 @@ title: Use cases
 hidden: false
 sidebar:
   order: 4
-
 ---
 
 Cloudflare Tunnel creates a secure, outbound-only connection between your services and Cloudflare by deploying a lightweight connector in your environment. Here is how to use tunnels with some specific services:
 
-* [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
-* [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
-* [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
-* [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
+- [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
+- [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
+- [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
+- [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
index c39aca829aac5a9..8ae62963190d27f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
@@ -17,4 +17,4 @@ Cloudflare offers three ways to secure RDP:
 
 - [Browser-based RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser/)
 - [RDP with Cloudflare One Client](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client/)
-- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
\ No newline at end of file
+- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
index 7830923733b5e59..e9787ea4da56ea5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
@@ -57,7 +57,7 @@ By default, Internet Explorer will be installed and configured in [Enhanced Secu
 
 <Render file="tunnel/connect-private-network" product="cloudflare-one" />
 
-3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the  **Internal IP** of the VM instance.
+3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the **Internal IP** of the VM instance.
 
 4. (Optional) [Set up Zero Trust policies](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#4-recommended-filter-network-traffic-with-gateway) to fine-tune access to your server.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
index dfb0e2feed3b4db..de8d6a6065a81b3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
@@ -31,160 +31,159 @@ There are a number of different VNC server versions, deployments, and instances.
 
 For demonstration purposes, we will create a TightVNC server on an Ubuntu virtual machine (VM) hosted in Google Cloud Project (GCP). We will configure the VNC server to run XFCE, a lightweight desktop environment suitable for remote access. If you already have a VNC server installed, you can skip this step and [go to Step 2](#2-connect-the-server-to-cloudflare).
 
-1. Open a terminal window for your Ubuntu VM.
+1.  Open a terminal window for your Ubuntu VM.
 
-2. Install XFCE and TightVNC by running the following command:
+2.  Install XFCE and TightVNC by running the following command:
 
-		```sh
-		sudo apt update
-		sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
+        ```sh
+        sudo apt update
+        sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
 
-		```
+        ```
 
-		This command installs the desktop, some helpful utilities, and the VNC server software.
+        This command installs the desktop, some helpful utilities, and the VNC server software.
 
-3. To initialize the VNC server:
+3.  To initialize the VNC server:
+    1. Create a VNC server instance:
 
-	1. Create a VNC server instance:
+       ```sh
+       vncserver
+       ```
 
-		```sh
-		vncserver
-		```
+    2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
 
-	2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
+       TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
 
-		TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
+    3. You will be asked if you want to create a view-only password. You can press `n` for no.
 
-	3. You will be asked if you want to create a view-only password. You can press `n` for no.
+    4. Kill this initial session so that you can edit its configuration:
 
-	4. Kill this initial session so that you can edit its configuration:
+       ```sh
+       vncserver -kill :1
+       ```
 
-		```sh
-		vncserver -kill :1
-		```
-4. Configure VNC to launch the XFCE desktop:
+4.  Configure VNC to launch the XFCE desktop:
+    1. Create a VNC configuration directory if it is missing:
 
-	1. Create a VNC configuration directory if it is missing:
+    ```sh
+    mkdir -p ~/.vnc
+    ```
 
-	```sh
-	mkdir -p ~/.vnc
-	```
+    2. Open the `xstartup` file using a text editor. For example,
 
-	2. Open the `xstartup` file using a text editor. For example,
+    ```sh
+    vim ~/.vnc/xstartup
+    ```
 
-	```sh
-	vim ~/.vnc/xstartup
-	```
+    3. Update the file to the following configuration:
 
-	3. Update the file to the following configuration:
+    ```bash
+    #!/bin/sh
+    unset SESSION_MANAGER
+    unset DBUS_SESSION_BUS_ADDRESS
+    startxfce4
+    ```
 
-	```bash
-	#!/bin/sh
-	unset SESSION_MANAGER
-	unset DBUS_SESSION_BUS_ADDRESS
-	startxfce4
-	```
+    4. Make the file executable:
 
-	4. Make the file executable:
+    ```sh
+    chmod +x ~/.vnc/xstartup
+    ```
 
-	```sh
-	chmod +x ~/.vnc/xstartup
-	```
+5.  Start the VNC server again:
 
-5. Start the VNC server again:
-	```sh
-	vncserver -localhost :1
-	```
+    ```sh
+    vncserver -localhost :1
+    ```
 
-	The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
+    The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
 
-6. (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
+6.  (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
+    1. Open a terminal on the client machine.
 
-	1. Open a terminal on the client machine.
+    2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
 
-	2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
+       ```sh
+       gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
+       ```
 
-		```sh
-		gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
-		```
+    3. Open your preferred VNC viewer application.
 
-	3. Open your preferred VNC viewer application.
+    4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
 
-	4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
+    You should see the Ubuntu VM desktop.
 
-	You should see the Ubuntu VM desktop.
+7.  (Optional) Configure the VNC server to start on boot:
+    1. Find the full path to the `vncserver` command:
 
-7. (Optional) Configure the VNC server to start on boot:
+       ```sh
+       which vncserver
+       ```
 
-	1. Find the full path to the `vncserver` command:
+       ```sh output
+       /usr/bin/vncserver
+       ```
 
-		```sh
-		which vncserver
-		```
-		```sh output
-		/usr/bin/vncserver
-		```
-	2. Create a new service configuration file:
+    2. Create a new service configuration file:
 
-	```sh
-	sudo vim /etc/systemd/system/vncserver@.service
-	```
+    ```sh
+    sudo vim /etc/systemd/system/vncserver@.service
+    ```
 
-	3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
+    3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
 
-		```toml
-		[Unit]
-		Description=Start TightVNC server at startup
-		After=syslog.target network.target
+       ```toml
+       [Unit]
+       Description=Start TightVNC server at startup
+       After=syslog.target network.target
 
-		[Service]
-		Type=forking
-		User=[YOUR_USERNAME]
-		WorkingDirectory=/home/[YOUR_USERNAME]
+       [Service]
+       Type=forking
+       User=[YOUR_USERNAME]
+       WorkingDirectory=/home/[YOUR_USERNAME]
 
-		PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
+       PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
 
-		ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
-		ExecStart=/usr/bin/vncserver -localhost :%i
-		ExecStop=/usr/bin/vncserver -kill :%i
+       ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
+       ExecStart=/usr/bin/vncserver -localhost :%i
+       ExecStop=/usr/bin/vncserver -kill :%i
 
-		[Install]
-		WantedBy=multi-user.target
-		```
+       [Install]
+       WantedBy=multi-user.target
+       ```
 
-		4. Reload `systemd` to read in the new service file:
+       4. Reload `systemd` to read in the new service file:
 
-		```sh
-		sudo systemctl daemon-reload
-		```
+       ```sh
+       sudo systemctl daemon-reload
+       ```
 
-		5. Enable the service to start at boot:
+       5. Enable the service to start at boot:
 
-		```sh
-		sudo systemctl enable vncserver@1.service
-		```
+       ```sh
+       sudo systemctl enable vncserver@1.service
+       ```
 
-		The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
+       The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
+       6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
 
-		6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
+       ```sh
+       sudo loginctl enable-linger [YOUR_USERNAME]
+       ```
 
-		```sh
-		sudo loginctl enable-linger [YOUR_USERNAME]
-		```
+       7. Start the service:
 
-		7. Start the service:
+       ```sh
+       sudo systemctl start vncserver@1.service
+       ```
 
-		```sh
-		sudo systemctl start vncserver@1.service
-		```
+       8. Check its status:
 
-		8. Check its status:
+       ```sh
+       sudo systemctl status vncserver@1.service
+       ```
 
-		```sh
-		sudo systemctl status vncserver@1.service
-		```
-
-		The VNC server will now start automatically every time the VM boots.
+       The VNC server will now start automatically every time the VM boots.
 
 ## 2. Connect the server to Cloudflare
 
@@ -198,7 +197,7 @@ For demonstration purposes, we will create a TightVNC server on an Ubuntu virtua
 
 5. For **Service**, select _TCP_ and enter `localhost:<5901>`. If the VNC server is on a different machine from where you installed the tunnel, enter `<SERVER_IP>:5901`.
 
-	Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
+   Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
 
 6. Save the route.
 
@@ -220,7 +219,10 @@ Create a Cloudflare Access application that users can access through their brows
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
+   <Render
+   	file="access/self-hosted-app/browser-rendering-policies"
+   	product="cloudflare-one"
+   />
 
 7. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
index 621709d181b4715..7f5b8371def9c4d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
@@ -6,7 +6,8 @@ products:
 sidebar:
   order: 10
 head: []
-description: Use Cloudflare WAN's different analytic options for an overview of the
+description:
+  Use Cloudflare WAN's different analytic options for an overview of the
   performance of your sites, or to troubleshoot potential issues.
 tags:
   - Analytics
@@ -16,15 +17,21 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		networkAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		traceRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
-		graphQlTunnelBandwidthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/"
-		 }}
+		networkAnalyticsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		traceRoutes:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
+		graphQlTunnelBandwidthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		siteAnalyticsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
index d3c2fff924b3af7..f685696ff741fda 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -15,4 +15,11 @@ head:
 
 import { Render } from "~/components";
 
-<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" params={{ breakoutTrafficURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/" }} />
\ No newline at end of file
+<Render
+	file="mconn/network-options/app-aware-policies/netflow"
+	product="networking-services"
+	params={{
+		breakoutTrafficURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
index 4694b2188d10e76..81bc27fef3b688e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
@@ -15,9 +15,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN"
+		magicWord: "CF1 Cloudflare WAN",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
index c7a0918e9e4281f..0a93283b55966af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
index 761d5ad3c83ef95..12fc47ede0c7643 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -12,9 +12,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
index 6c2c604b49fd3c4..a7cdd1152a38d1e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -12,8 +12,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }} />
+	params={{ productName: "Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
index 9a1e57ebda7c9dd..294f9511dcdaaa2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
@@ -13,18 +13,21 @@ tags:
   - Analytics
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions: "Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions:
+			"Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "CF1 Cloudflare WAN",
 		networkOverviewPageName: "Network visibility",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
-		}}
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
+	}}
 />
 
 ### Set thresholds for site health
@@ -34,6 +37,7 @@ import { Render } from "~/components"
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index e934890d0601507..e5c5a9d02461bc1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,35 +11,59 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "hardware",
-	productName: "Cloudflare One Appliance",
-	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "CF1 Cloudflare WAN",
-	sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-	wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-	lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-	noConnectorShows: "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
-	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "The Connector is shipped to you deactivated",
-	hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-  maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "hardware",
+		productName: "Cloudflare One Appliance",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "CF1 Cloudflare WAN",
+		sfpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+		lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+		noConnectorShows:
+			"You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage: "The Connector is shipped to you deactivated",
+		hardSoftConn:
+			"You need to deploy two Connectors in your premises before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		referenceInformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index e8ca4f7240d425e..7d8436c9226ce40 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,10 +4,8 @@ description: Reference information for SFP+ port information in Zero Trust netwo
 products:
   - cloudflare-one
 title: SFP+ port information
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info"
-	product="networking-services" />
+<Render file="mconn/sfp-port-info" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
index 6a1b94bdb249832..5299a10b9e18f37 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
@@ -10,34 +10,56 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "virtual",
-	productName: "Cloudflare One Appliance",
-	productNameVirtual: "Virtual Appliance",
-	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "CF1 Cloudflare WAN",
-	wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
-	lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
-	noConnectorShows: "For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
-	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "Virtual Appliance is deactivated after you install it",
-	hardSoftConn: "You need to install two Virtual Appliances before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "virtual",
+		productName: "Cloudflare One Appliance",
+		productNameVirtual: "Virtual Appliance",
+		maintenanceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "CF1 Cloudflare WAN",
+		wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
+		lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
+		noConnectorShows:
+			"For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage: "Virtual Appliance is deactivated after you install it",
+		hardSoftConn:
+			"You need to install two Virtual Appliances before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+		referenceInformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
index ffd0a4c4b645784..c0051513debf6e3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+		troubleshootingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
index fb436734ed7d217..cb114ce2b99fa6c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,9 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Virtual Appliance",
-		virtualUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		}}
+		virtualUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index ac563378234270b..c7cbae7c3ceabbf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -14,6 +14,9 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-		}} />
+		hardwareConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
index 35e5bf0f59c7313..6bcfc54764da629 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
@@ -6,7 +6,6 @@ products:
 title: Deactivate Connector
 sidebar:
   order: 8
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
index f2b21ce17eccf65..490ed326c212d3f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
@@ -6,7 +6,6 @@ products:
 title: Heartbeat
 sidebar:
   order: 9
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 922634423e75753..630305e6d60c767 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
index c7b5151598427ee..056b0ca5a650163 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
@@ -6,7 +6,6 @@ title: Interrupt window
 description: Learn how to set up when Connector can update its systems.
 sidebar:
   order: 10
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 3949eb19c151c2e..98554bc18b3cf72 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -15,5 +15,5 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		}}
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index b7f774b674a7b81..3a9310c33020487 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,12 +9,16 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "breakout",
-	featureName: "Breakout traffic",
-	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
-	dashName: "CF1 Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "breakout",
+		featureName: "Breakout traffic",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		whatHappensApp:
+			"will now go directly to the Internet and bypass Cloudflare's filtering",
+		dashName: "CF1 Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
index b12153e883b952b..0468257e119128d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
@@ -4,14 +4,16 @@ description: How Application-aware policies works in Zero Trust networking.
 products:
   - cloudflare-one
 title: Application-aware policies
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/overview"
+<Render
+	file="mconn/network-options/app-aware-policies/overview"
 	product="networking-services"
 	params={{
-	gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
-	appTypesGatewayURL: "/cloudflare-one/policies/gateway/application-app-types/"
-	}} />
+		gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
+		appTypesGatewayURL:
+			"/cloudflare-one/policies/gateway/application-app-types/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 4067d211b871836..5aac85459c295d4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,11 +9,13 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "prioritized",
-	featureName: "Prioritized traffic",
-	whatHappensApp: "is now processed first by Connector",
-	dashName: "CF1 Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "prioritized",
+		featureName: "Prioritized traffic",
+		whatHappensApp: "is now processed first by Connector",
+		dashName: "CF1 Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 2c0fe51a6772f0b..fb14bed9a02c912 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,11 +8,13 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-relay"
+<Render
+	file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
+		cfVsCoreDashNamingMwanCni:
+			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
 	}}
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index c8a992aa8ac61b7..54ddbc7c233c16a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,9 +8,10 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-server"
+<Render
+	file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index a3ba4bd0341904e..525082ff11a2ee0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,9 +8,11 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render
+	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
index bda0220b0ebbf27..d3bb4e7b3f2a648 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index b6dc835b4894396..bfd8e592fdc15f9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,11 +8,15 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/link-aggregation"
+<Render
+	file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 1ccd87afb778419..5405768ac68156c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,14 +4,17 @@ products:
   - cloudflare-one
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Connector to  re-use address spaces locally.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/nat-subnet"
+<Render
+	file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-	hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-  virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
\ No newline at end of file
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 43b9ee7508fbdd0..b5133cb7577975e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,12 +6,16 @@ title: Network segmentation
 description: Define policies to define if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/network-segmentation"
+<Render
+	file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index 741b251ec5b73f3..00ebfc4681edb6c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,15 +4,19 @@ products:
   - cloudflare-one
 title: Routed subnets
 description: Learn how to configure routed subnets on a Connector, including setting static routes and next-hop addresses for complex LAN setups.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/routed-subnets"
+<Render
+	file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		netSubnetURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
index 63e642f8fee211d..be5fdb923289884 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
@@ -16,17 +16,28 @@ import { Render } from "~/components";
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		haSetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
-		ecmpRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		multipleWansURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
-		sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		hardConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		haSetupURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
+		ecmpRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		multipleWansURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
+		sfpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
 		vlanIdURL: "#vlan-id",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		hcFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		dhcpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
-		routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/"
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		hcFrequencyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		dhcpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
+		routedSubnetsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		networkSegmentationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 3806aad41029a92..bec67a3bb4ce2d5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -17,8 +17,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		activateURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		activateURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
index 5c087c6432ea87f..854c24e84e725b5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
@@ -16,12 +16,14 @@ import { Render } from "~/components";
 	params={{
 		dashInfo:
 			"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
-		graphQL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		graphQL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
 		notificationsPath:
 			"[notifications wizard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		magicWord: "CF1 Cloudflare WAN"
+		networkAnalytics:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		magicWord: "CF1 Cloudflare WAN",
 	}}
 />
 
@@ -39,7 +41,8 @@ import { Render } from "~/components";
 	file="tunnel-health/mconn-heartbeat-health"
 	product="networking-services"
 	params={{
-		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		heartbeatURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
index 3b09a3fa29ff311..5c56ccb5ff6fcbf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
@@ -18,7 +18,9 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		magicTunnelHealthCheckCalculation:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/",
-		networkAnalyticsPath: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		healthChecks: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsPath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		healthChecks:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index 4a5d426468f3433..33927b2f361233a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -12,4 +12,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
+<Render
+	file="cloudflare-wan/custom-ike-id-ipsec"
+	product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
index 066c118ccf4222d..e3d0145968a7905 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,10 +15,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		greIpsecTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		greIpsecTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
index f9858038dbd480e..d1d59be9414d68b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
@@ -16,7 +16,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		healthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		healthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		addTunnelsPath:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 26d6f25b6a74b55..ca3e788d025bd8b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,10 +13,11 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-  file="routing/configure-cloudflare-source-ips"
-  product="networking-services"
-  params={{
-    unifiedRoutingLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/"
-  }}
+	file="routing/configure-cloudflare-source-ips"
+	product="networking-services"
+	params={{
+		unifiedRoutingLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 2fd957397c1f902..334a23c9167b3af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -6,29 +6,37 @@ products:
 sidebar:
   order: 2
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		trafficSteeringPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		trafficSteeringPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		addTunnelsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table"
+		routingTableName: "Cloudflare Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 1f5ce39957c3508..d615ab646878dd7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -12,26 +12,41 @@ tags:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		cniLink: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		tunnelHealthChecksPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		tunnelsAndEncapsulationPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayPagePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		cniLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		updateHCFrequencyPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		tunnelHealthChecksPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
+		tunnelHealthDash:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		sitesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		configureARRURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
index 478096429eb0edf..8d38559e9f784a5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
index 91c321110a4e9fa..006aa7559219809 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -15,8 +15,11 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
index ee5e8e31b67dd5d..7cfe5c8a32d1f27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index 2e3362c2297a304..c44c422d412e3e9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/alibaba-cloud"
-  product="networking-services"
-  params={{
-    ipSecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/alibaba-cloud"
+	product="networking-services"
+	params={{
+		ipSecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
index 47bdff355de0e2a..53f7609c41d4c0e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
@@ -10,10 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aruba-edgeconnect"
-  product="networking-services"
-  params={{
-		tunnelHealthCheckUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+<Render
+	file="cloudflare-wan/third-party/aruba-edgeconnect"
+	product="networking-services"
+	params={{
+		tunnelHealthCheckUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		magicFirewallUrl: "/cloudflare-network-firewall/",
-		gatewayUrl: "/cloudflare-one/traffic-policies/"
-  }} />
+		gatewayUrl: "/cloudflare-one/traffic-policies/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
index dd27825eb60ed8a..4dde9787ebca0b6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
@@ -6,14 +6,17 @@ products:
 title: Amazon AWS Transit Gateway
 tags:
   - AWS
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aws"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/aws"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index 6e4f1a3573cbf12..b02d849640387d0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-virtual-wan"
-  product="networking-services"
-  params={{
-  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  cloudflareDocumentationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-virtual-wan"
+	product="networking-services"
+	params={{
+		tunnelHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		ipsecTunnelUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		cloudflareDocumentationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index 6308449fc485359..e3af7916ddaaf15 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
-  product="networking-services"
-  params={{
-  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  staticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-vpn-gateway"
+	product="networking-services"
+	params={{
+		ipsecTunnelUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		tunnelHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
index 3692dd21b4e45ca..61a653693d0b777 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index 26cd14b751b3d81..df5158c103fe80f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -10,6 +10,7 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-ios-xe"
-  product="networking-services"
+<Render
+	file="cloudflare-wan/third-party/cisco-ios-xe"
+	product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 2bf5636cbdce15a..b752d4f85dab6f7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -10,15 +10,25 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render
+	file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
-		trafficSteeringUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		paloAltoGuideUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-	}} />
+		antiReplayProtectionUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		unifiedRoutingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		supportedConfigParametersUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		paloAltoGuideUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 4af42ab35a2bc43..0da4cb37c63d84d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fitelnet"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    typeId_ipv4_addrUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fitelnet"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		typeId_ipv4_addrUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
index 3869ebd7e5a01ea..e71cf29b9f07669 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -10,12 +10,19 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fortinet"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    equalCostMultipathRoutingEcmpUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fortinet"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		equalCostMultipathRoutingEcmpUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
index e35533f9aa61fae..e8e6fe1d8fc944a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
@@ -12,9 +12,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/google"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/google"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
index 28c8eb38103e3a7..88548b31947b629 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
index 9041812a55d647d..f3b4d51ebae092c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,10 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/juniper"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/juniper"
+	product="networking-services"
+	params={{
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
index 544a2fd71e1b10b..4fe095992306cb0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -10,9 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/oracle"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/oracle"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
index 74648ea559442b1..d3a02cd42315066 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,10 +13,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/palo-alto"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/palo-alto"
+	product="networking-services"
+	params={{
+		mssClampingUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
index 5c7329f8bb2a15d..8beb36669a01a5a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -11,10 +11,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/pfsense"
-  product="networking-services"
-  params={{
-    configureTwoIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    staticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/pfsense"
+	product="networking-services"
+	params={{
+		configureTwoIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		staticRouteUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 681705328bc2479..e2236e3c62ec88c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sonicwall"
-  product="networking-services"
-  params={{
-    ipsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    creatingYourIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createYourStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sonicwall"
+	product="networking-services"
+	params={{
+		ipsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		creatingYourIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createYourStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index b2a4c4249e87375..afc7910dc9d12af 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -10,11 +10,17 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sophos-firewall"
-  product="networking-services"
-  params={{
-    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    ikeIdUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sophos-firewall"
+	product="networking-services"
+	params={{
+		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		ikeIdUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
index ceba0f994025298..bb005e68632169a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -11,8 +11,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/strongswan"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/strongswan"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index a97b5659741e9d7..9a96fafe0bfa4ab 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -11,9 +11,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-wan/third-party/ubiquiti"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN"
-  }}
+	file="cloudflare-wan/third-party/ubiquiti"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
index f944858befeffef..736fbd873bbdd38 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -10,8 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/velocloud"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/velocloud"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
index 1d4fe3f1866abf4..c7dc2d9c75ba0a6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -11,10 +11,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/viptela"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/viptela"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		ciscoIosXeUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
index 75be63a9bfe72a6..e79d26181aeb494 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -10,6 +10,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos"
-  product="networking-services"
-/>
+<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
index 77d9af6a973237c..b2355afb2d6994d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -10,9 +10,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/yamaha"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/yamaha"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
index f8e8f7694c90053..8cf6de52ad11759 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
@@ -16,12 +16,19 @@ import { Render } from "~/components";
 	params={{
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		configureConnectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		configureMwanManually: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		greReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		mtuReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/"
+		configureConnectorUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		configureMwanManually:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ipsecReferenceUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		mtuReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		wanTransformationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
index 8aac7ee6d2a4275..c804130785b3a29 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
@@ -20,13 +20,19 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		connectorName: "Cloudflare One Appliance",
 		connectorCta: "Use Cloudflare One Appliance",
-		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		connectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
-		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/"
+		connectorUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		zeroTrustUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		bgpRoutesUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		wanTransformationUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
index a8d18b418df7a40..c54c3b324cf1b28 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
@@ -5,7 +5,6 @@ pcx_content_type: reference
 description: Reference information for Third party licenses in Zero Trust networking.
 products:
   - cloudflare-one
-
 ---
 
 import text from "./3rdparty.txt?raw";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
index 70f7ed48d19fc64..653b31922480265 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 12
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
index b6c275104b79281..475873e33440e3a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
@@ -13,14 +13,21 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
+<Render
+	file="magic-cni"
+	product="networking-services"
+	params={{ magicWord: "Cloudflare WAN" }}
+/>
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
index 0e0944033ed0838..506e7260402fd54 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
@@ -17,11 +17,17 @@ import { Render } from "~/components";
 		magicWord: "CF1 Cloudflare WAN",
 		productNameWAN: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/"
+		connectorURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		cniURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		thirdPartyIntegrationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
index f827135b0192839..bdb55cdaa44ca58 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -5,7 +5,8 @@ products:
 title: Anti-replay protection
 tags:
   - IPsec
-description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description:
+  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
index 6a168b9730c3943..32b8afa7e6f4527 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cloudflareTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
index 4fa1452c2f1d01c..a51b28317cfdf42 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
@@ -12,29 +12,53 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/reference/device-compatibility"
-  product="networking-services"
-  params={{
-    supportedConfigurationParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    arubaEdgeconnectUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-    ciscoMerakiStaticUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-    ciscoSdWanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
-    fortinetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
-    fitelnetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
-    juniperUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
-    paloAltoUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-    pfsenseUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
-    sonicwallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
-    sophosFirewallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
-    strongswanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
-    ubiquitiUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
-    velocloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
-    vyosUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
-    yamahaUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
-    alibabaCloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-    awsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
-    azureUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
-    googleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
-    oracleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/"
-  }} />
+<Render
+	file="cloudflare-wan/reference/device-compatibility"
+	product="networking-services"
+	params={{
+		supportedConfigurationParametersUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		arubaEdgeconnectUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+		ciscoIosXeUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+		ciscoMerakiStaticUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+		ciscoSdWanUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
+		fortinetUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
+		fitelnetUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
+		juniperUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
+		paloAltoUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		pfsenseUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
+		sonicwallUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
+		sophosFirewallUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
+		strongswanUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
+		ubiquitiUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
+		velocloudUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
+		vyosUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
+		yamahaUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
+		alibabaCloudUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+		awsUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
+		azureUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
+		googleUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
+		oracleUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index e48aacf091b3898..32c6047307e94c8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -19,14 +19,18 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		mssURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		productURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		mssURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		productURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index f4b1ec66d7f87c2..c08c54539b5b3b6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,13 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination"	}}
+	params={{
+		tunnelStatePath:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
index c9bbdad031b4e3d..936eef5bb11c21b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
index dad3b9a5d8d8777..a6693ef9af219d6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN"
+		productName: "Cloudflare WAN",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
index 354bdbd705088a9..c5d20719e86eb64 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
@@ -17,22 +17,30 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-  	magicWord: "CF1 Cloudflare WAN",
-  	productName: "Cloudflare WAN",
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-  	greIpsecReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-  	createStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  	editStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
-  	setupBgpPeering: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
-		legacyHCs: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
-		tunnelHCsPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		cfTunnelURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		greIpsecReferenceURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		createStaticRoute:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		editStaticRoute:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
+		setupBgpPeering:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		sourceIPsURL:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/",
 		virtualNetworkName: "Cloudflare Virtual Network",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
index 276bc867f82dcd8..f8b615e6070db55 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -18,12 +18,16 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		addTunnels: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
-		staticRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		staticRoutes:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelEndpoints:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
index d122736e9eeaedc..eace55f088f5192 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
@@ -9,14 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="cloudflare-wan/security-filters"
+<Render
+	file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/"
+		gatewayURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
index 2eb4a9483c2622f..e5bc049482c1740 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,10 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
index 1e718eb8e9c31ce..fb5782e5fef4adf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 3f0cd1c1f120d63..23dbe5aa1465d70 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -10,14 +10,19 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index 41ea7fb74a080e1..dd1b594c265542e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -13,14 +13,18 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 49a3d8aef991d65..fca3b17df568c35 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -14,17 +14,24 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
index a1fce7bc5634d3c..0dcfa150778deae 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
@@ -17,11 +17,15 @@ import { Render } from "~/components";
 	file="cloudflare-wan/wan-transformation"
 	product="networking-services"
 	params={{
-		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		connectivityOptionsUrl: "/cloudflare-one/networks/connectivity-options/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		applianceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		secureWanTrafficUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
+		zeroTrustUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		applianceUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		secureWanTrafficUrl:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
index 37ab275a843c03d..c39636c40320181 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
@@ -18,21 +18,36 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfAutoCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
-		cfManualCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
-		decryptTlsURL: "/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
-		doNotInspectURL: "/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
-		warpChecksURL: "/cloudflare-one/reusable-components/posture-checks/client-checks/",
-		osVersionChecks: "/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
-		mwanOnrampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		gatewayResolverPoliciesURL: "/cloudflare-one/traffic-policies/resolver-policies/",
-		gatewayInternalDnsURL: "/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
+		warpURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfAutoCertificatesURL:
+			"/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
+		cfManualCertificatesURL:
+			"/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
+		decryptTlsURL:
+			"/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
+		doNotInspectURL:
+			"/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
+		warpChecksURL:
+			"/cloudflare-one/reusable-components/posture-checks/client-checks/",
+		osVersionChecks:
+			"/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
+		mwanOnrampsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+		gatewayResolverPoliciesURL:
+			"/cloudflare-one/traffic-policies/resolver-policies/",
+		gatewayInternalDnsURL:
+			"/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
 		egressPoliciesURL: "/cloudflare-one/traffic-policies/egress-policies/",
-		gatewayLogsURL: "/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
-		tcpMssClampingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		ikeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		gatewayLogsURL:
+			"/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
+		tcpMssClampingURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		ikeURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
index 021d27ca4f6f08d..a6aa06e27222024 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
@@ -18,15 +18,23 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/warp"
 	product="networking-services"
 	params={{
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		setupZeroTrustAccountURL: "/cloudflare-one/setup/#2-create-a-zero-trust-organization",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		setupZeroTrustAccountURL:
+			"/cloudflare-one/setup/#2-create-a-zero-trust-organization",
 		ztDashPath: "My Team > Devices",
-		splitTunnelsURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
-		warpDeploymentURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
-		warpIngressIpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
+		splitTunnelsURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
+		warpDeploymentURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
+		warpIngressIpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
 		mwanConnectorName: "Cloudflare One Appliance",
-		domainFallbackURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
+		domainFallbackURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index d1ca77abe7c8a72..0d372fbdcc0d99f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -15,10 +15,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
+		greIpsecURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
index 86daf36cc1a9660..510e6bd01921e87 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
@@ -9,7 +9,6 @@ head:
   - tag: title
     content: Cloudflare One integration tutorials
 description: Learn how to integrate Cloudflare WAN with other Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
index 1bcbcba64603e90..a634aba89cca3ac 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
@@ -16,8 +16,11 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/security-services"
 	product="networking-services"
 	params={{
-		networkFirewallURL: "/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
-		gatewaySetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
-		wanTransformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		networkFirewallURL:
+			"/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
+		gatewaySetupURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		wanTransformationURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
index 1db111952cb9cd0..21c15ec9d2d739b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-one
 ---
 
-import { Steps } from '~/components';
+import { Steps } from "~/components";
 
 You can scope Cloudflare member permissions to individual [Cloudflare Tunnel](/tunnel/) instances and [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) nodes, instead of granting account-wide access to every Tunnel and Mesh node. This enables least-privilege delegation for private networking operations — for example, letting a support operator stream logs from a single Tunnel without exposing the rest of your account.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
index 24eaa0394bc62b2..7c6fe57320f8f26 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
@@ -10,7 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
-
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
index 8bfca8fb0871aec..189b65dec009c19 100644
--- a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
@@ -29,9 +29,9 @@ To add a CIDR route:
 3. In **CIDR**, enter the IP address or CIDR range that you wish to route through the tunnel (for example, `10.0.0.1` or `10.0.0.0/24`). This can be a private or public IP.
 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare.
 5. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/virtual-networks/) for this tunnel route. A virtual network is a private routing domain that provides routing isolation within your account. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
-		:::note
-		Virtual networks are only supported for `cloudflared` tunnels.
-		:::
+   :::note
+   Virtual networks are only supported for `cloudflared` tunnels.
+   :::
 6. Select **Create**.
 
 Cloudflare will now route requests to your private network. However, the route does not automatically capture traffic from end users. To enable client-side connectivity, refer to the [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/) or
@@ -61,9 +61,10 @@ Published application routes expose applications to the Internet via a domain th
 
 :::note[Prerequisites]
 Before you publish an application, ensure you have:
+
 - [Created a Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) using `cloudflared`.
 - [Added a website to Cloudflare](/fundamentals/manage-domains/add-site/).
-:::
+  :::
 
 To add a published application route to an existing tunnel:
 
@@ -74,13 +75,13 @@ To add a published application route to an existing tunnel:
 3. Go to the **Published application routes** tab and select **Add a published application route**.
 
 4. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-	:::note
-	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-	:::
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
 
 5. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example:
-	- **Type**: _HTTP_
-	- **URL**: `localhost:8000`
+   - **Type**: _HTTP_
+   - **URL**: `localhost:8000`
 
 6. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
@@ -91,4 +92,3 @@ Anyone on the Internet can now access the application at the specified hostname.
 ## Add a WAN route
 
 WAN routes define the IP network segments (such as `10.0.0.0/24`) that are reachable via a GRE or IPsec tunnel. To add a WAN route, refer to the [WAN Connectors documentation](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/).
-
diff --git a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
index 90e480866276de9..308de57b07e7f48 100644
--- a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
@@ -23,14 +23,14 @@ When planning your private network addressing and configuring [Split Tunnel](/cl
 | ------------------------------------------------------------- | ---------------- | ------------ |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `100.64.0.0/12`  | Yes          |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `100.80.0.0/16`  | No           |
-| [Device IPs](#device-ips)                           | `100.96.0.0/12`  | Yes          |
+| [Device IPs](#device-ips)                                     | `100.96.0.0/12`  | Yes          |
 | [Private Load Balancer IPs](#private-load-balancer-ips)       | `100.112.0.0/16` | Yes          |
 
 ## IPv6 ranges
 
 | Name                                                          | Default CIDR               | Configurable |
 | ------------------------------------------------------------- | -------------------------- | ------------ |
-| [Device IPs](#device-ips)                           | `2606:4700:0cf1:1000::/64` | No           |
+| [Device IPs](#device-ips)                                     | `2606:4700:0cf1:1000::/64` | No           |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `2606:4700:0cf1:4000::/64` | No           |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `2606:4700:0cf1:5000::/64` | No           |
 
diff --git a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
index 6a8f6c283d0c8b1..be5f7bea46c3b41 100644
--- a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
@@ -17,11 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare One",
-		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		configureRoutesURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		trafficSteeringURL:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		privateNetworksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
index 0749407053febed..c3ff67b1fdb0308 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
@@ -24,4 +24,4 @@ Alternatively, to use a keyboard shortcut, press `CTRL + ALT + Z`.
 
 ## Languages
 
-The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
\ No newline at end of file
+The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
index c608dbdef4888a2..3ad4acc8218df86 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
@@ -12,7 +12,6 @@ tags:
 
 import { Render } from "~/components";
 
-
 :::note
 Remote browser isolation is available as an add-on to Zero Trust Pay-as-you-go and Enterprise plans.
 :::
@@ -30,4 +29,3 @@ Cloudflare Browser Isolation is a security product. In order to serve transparen
 ## Troubleshooting
 
 For help resolving common issues with Browser Isolation, refer to [Troubleshoot Browser Isolation](/cloudflare-one/remote-browser-isolation/troubleshooting/).
-
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
index b4040d192dbbf47..e7f230098916d61 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
@@ -83,4 +83,7 @@ You no longer need to isolate both the Identity Provider (IdP) and Service Provi
 
 ## Browser Isolation is not compatible with private apps on non-`443` ports
 
-<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
+<Render
+	file="access/self-hosted-app/browser-isolation-non-443"
+	product="cloudflare-one"
+/>
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
index a74778b93fcbd01..21df1128ff02665 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
@@ -34,8 +34,8 @@ Browser Isolation uses WebRTC (a real-time communication protocol) for low-laten
 
 In order to pass WebRTC traffic, the remoting client must be able to connect to the following IP addresses:
 
-| IP range                                                                 | Port range    | Protocol |
-| ------------------------------------------------------------------------ | ------------- | -------- |
+| IP range                                                                                                           | Port range    | Protocol |
+| ------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
 | IPv4: `162.159.201.10 - 162.159.201.255` <br/> IPv4: `172.64.73.0 - 172.64.73.255` <br/> IPv6: `2606:4700:f2::/48` | 10000 - 59999 | UDP      |
 
 Each remote browser instance is randomly assigned a port, and the port that a user is allocated to will change often and without notice.
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
index c45a25eaf8d13b8..9e910279a1fe9a8 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
@@ -15,13 +15,13 @@ Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudfl
 
 Setup instructions vary depending on how you want to connect your devices to Cloudflare. Refer to the links below to view the setup guide for each deployment option.
 
-| Connection                                                                                                | Mode         | Description                                                                                                          |
-| --------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
-| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                       |
-| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                     |
-| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                           |
-| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network).                                 |
-| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`. |
+| Connection                                                                                                | Mode         | Description                                                                                                                                       |
+| --------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                                          |
+| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                                                  |
+| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).     |
+| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network). |
+| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`.                              |
 
 **In-line** mode means traffic is inspected as it flows through Gateway — users browse to websites using normal URLs, not a special Cloudflare prefix. Some in-line methods require device or network configuration, such as installing the Cloudflare One Client or configuring a PAC file. **Prefixed URL** mode requires users to visit a Cloudflare-hosted URL that wraps the target website.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
index f0ab810ee252406..318f06a6fc92ed4 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
@@ -79,7 +79,7 @@ You can add a Mailto link to your custom block page, which allows users to direc
 | Source IP    | The public source IP of the user device.                                                                                                                                                                                    |
 | Account ID   | The Cloudflare account associated with the block policy.                                                                                                                                                                    |
 | User ID      | The ID of the user who visited the page. Currently, User IDs are not surfaced in the dashboard and can only be viewed by calling the [API](/api/resources/zero_trust/subresources/access/subresources/users/methods/list/). |
-| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                           |
+| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                 |
 | Block Reason | Your policy-specific block message.                                                                                                                                                                                         |
 
 ## Configure policy block behavior
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
index c7cde6525fc3b70..96799f2d3e915f6 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
index 1b02eaa266e0cf7..ccfd4fb9efc2beb 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
@@ -49,24 +49,23 @@ You can use the following commands to validate if the posture check is working a
 1. Open a PowerShell window.
 2. List all installed antivirus products registered with Windows Security Center:
 
-	```powershell
-	Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
-	```
-
-	```powershell output
-	<redacted>
-	displayName              : Windows Defender
-	instanceGuid             : {00000000-0000-0000-0000-000000000000}
-	pathToSignedProductExe   : windowsdefender://
-	pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
-	productState             : 397568
-	timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
-	PSComputerName           : ENDPOINT-01
-	```
+   ```powershell
+   Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
+   ```
+
+   ```powershell output
+   <redacted>
+   displayName              : Windows Defender
+   instanceGuid             : {00000000-0000-0000-0000-000000000000}
+   pathToSignedProductExe   : windowsdefender://
+   pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
+   productState             : 397568
+   timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
+   PSComputerName           : ENDPOINT-01
+   ```
 
 3. Microsoft does not support decoding the `productState` from the `SecurityCenter2` namespace. To verify that an antivirus product is active, open the [Windows Security app](https://support.microsoft.com/en-us/windows/stay-protected-with-the-windows-security-app-2ae0363d-0ada-c064-8b56-6a39afb6a963). The **Virus & threat protection** panel should say `No action needed` with a green checkmark.
 
-	To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
+   To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
 
 4. If you configured a maximum antivirus signature age in your posture check, compare the `timestamp` in the PowerShell output against the current system time. If the difference exceeds the configured number of days, the posture check will fail.
-
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
index daec64a910742b5..6e24b6094c78b8c 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
@@ -38,12 +38,12 @@ The Application Check device posture attribute checks that a specific applicatio
    2. **Operating system**: Select your operating system.
    3. **Application path**: Enter the file path for the executable that will be running (for example, `C:\Program Files\myfolder\myfile.exe`).
 
-		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
 
    :::note
    - Be sure to enter the binary file path, not the application launch path. When checking for an application on macOS, a common mistake is to enter `/Applications/ApplicationName.app`. This will not work as `ApplicationName.app` is a folder. The executable file that will be running is located within the folder, for example `ApplicationName.app/Contents/MacOS/ApplicationName`.
    - Some applications change their file path after an update. Ensure that the application is always in a stable location or use environment variables.
-	 :::
+     :::
 
 5. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint of the publishing certificate](#determine-the-signing-thumbprint) used to sign the binary. Adding this information will enable the check to ensure that the application was signed by the expected software developer.
 6. **SHA-256 (optional)**: Enter the [SHA-256 value](#determine-the-sha-256-value) of the binary. This is used to ensure the integrity of the binary file on the device.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
index bcf50cd88967c96..d0a1f568446a035 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
@@ -38,7 +38,8 @@ The File Check device posture attribute checks for the presence of a file on a d
    2. **Operating system**: Select your operating system.
    3. **File Path**: Enter a file path (for example, `c:\my folder\myfile.exe`).
 
-		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+
    4. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-signing-thumbprint) of the publishing certificate used to sign the file. Adding this information will enable the check to ensure that the file was signed by the expected software developer.
    5. **SHA-256 (optional)**: Enter the [SHA-256 value](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-sha-256-value) of the file. This is used to ensure the integrity of the file on the device.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
index 1d1d08a80225a0d..b580c8ae61cbeb2 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
@@ -36,12 +36,13 @@ The Firewall device posture attribute ensures that a firewall is running on a de
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Configure **Enable firewall check** based on your desired security policy:
-	- **Enabled**: (Recommended) The posture check passes only if the firewall is running.
-	- **Disabled**: The posture check passes only if the firewall is turned off.
+   - **Enabled**: (Recommended) The posture check passes only if the firewall is running.
+   - **Disabled**: The posture check passes only if the firewall is turned off.
+
+   :::note
+   The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
+   :::
 
-	:::note
-	The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
-	:::
 7. Select **Save**.
 
 Next, go to **Insights** > **Logs** > **Posture logs** and verify that the firewall check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
index 1ceee1540f5307e..00d1b33264aa55e 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
@@ -6,33 +6,32 @@ products:
 title: Cloudflare One Client checks
 sidebar:
   order: 1
-
 ---
 
 These device posture checks are performed by the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/). To use this feature, you must [deploy the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) to your devices and enable the desired posture checks.
 
 ## Supported Client modes
 
-* Traffic and DNS mode
-* Traffic only mode
-* Posture only mode
+- Traffic and DNS mode
+- Traffic only mode
+- Posture only mode
 
 ## Supported operating systems
 
-| Device posture check                                                                          | macOS | Windows | Linux       | iOS | Android/ChromeOS |
-| --------------------------------------------------------------------------------------------- | ----- | ------- | ----------- | --- | ---------------- |
-| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
-| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌     | ❌       | ❌           | ✅   | ✅                |
-| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
-| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅     | ✅       | ❌           | ❌   | ❌                |
-| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅     | ✅       | ✅           | ✅   | ✅                |
-| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅     | ✅       | ✅           | ❌   | ❌                |
-| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                          | ✅    | ✅      | ✅    | ❌  | ❌  |
+| Device posture check                                                                                       | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| ---------------------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)                   | ❌    | ✅      | ❌    | ❌  | ❌               |
+| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌    | ❌      | ❌    | ✅  | ✅               |
+| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌    | ✅      | ❌    | ❌  | ❌               |
+| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅    | ✅      | ❌    | ❌  | ❌               |
+| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅    | ✅      | ✅    | ✅  | ✅               |
+| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
+| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
index e30d916ac2409c1..92e23f910d1ba59 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
@@ -36,7 +36,7 @@ The OS Version device posture attribute checks whether the version of a device's
 
 5.  (Optional) Configure additional OS-specific fields:
 
-		<Tabs>
+<Tabs>
 		<TabItem label="Windows">
 		To check that Windows devices have required security patches and features installed, include an Update Build Revision (UBR) number in the OS version check.
 		- **Update Build Revision**: Enter the Windows UBR you want devices to match (for example, `3803`). The UBR is the fourth part of the full Windows version number (for example, in `10.0.19045.3803`, the UBR is `3803`).
@@ -77,6 +77,7 @@ Operating systems display version numbers in different ways. This section covers
 ### Windows
 
 Windows version numbers consist of four parts: `Major.Minor.Build.UBR`. For example, `10.0.19045.3803` where:
+
 - `10.0` is the **Version** (Major.Minor)
 - `19045` is the **Build** number
 - `3803` is the **UBR** (Update Build Revision)
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
index fe3b97910a59def..14c460754260543 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
@@ -37,7 +37,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru
 ## 1. Enable the WARP check
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Traffic settings**.
-2. Ensure that *Allow Secure Web Gateway to proxy traffic** is enabled.
+2. Ensure that \*Allow Secure Web Gateway to proxy traffic\*\* is enabled.
 3. Go to **Reusable components** > **Posture checks**.
 4. In **Cloudflare One Client checks**, select **Add a check**.
 5. Select **WARP**, then select **Save**.
diff --git a/src/content/docs/cloudflare-one/reusable-components/tags.mdx b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
index affffb57c1a52f9..9cf337c0f0573e9 100644
--- a/src/content/docs/cloudflare-one/reusable-components/tags.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
@@ -11,4 +11,3 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
-
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
index 06e26a64c28ed43..be1e46ccc11fec2 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
@@ -109,8 +109,8 @@ Use when you only want to enforce [Cloudflare One Client device posture checks](
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                   | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                          | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | Full security with all filtering capabilities    | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | DNS filtering without routing device traffic     | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | Traffic routing with existing DNS infrastructure | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
index 3ddfb9848c66291..7042d96a25bd81b 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
@@ -19,6 +19,7 @@ This section covers the most common issues you might encounter as you deploy the
 ## Connectivity and registration
 
 ### Stuck on "Disconnected" or frequent flapping
+
 If the Cloudflare One Client is stuck in the `Disconnected` state or frequently changes between `Connected` and `Disconnected`, this indicates that the client cannot establish a connection to Cloudflare's global network.
 
 In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/), `daemon.log` will typically show one or more of the following errors:
@@ -27,61 +28,75 @@ In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/clou
 - Connectivity checks timing out for `connectivity.cloudflareclient.com`.
 
 **Common causes**:
+
 - **Firewall blocks**: A local or network firewall is blocking the [required IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 - **VPN interference**: A third-party VPN is fighting for control over the routing table or DNS. Refer to the [VPN compatibility guide](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/vpn/).
 - **ISP blocks**: Your country or ISP may be explicitly blocking client traffic.
 
 ### Registration error (Authentication Expired)
+
 When registering the client, you may see `Authentication Expired` or `Registration error. Please try again later`.
 
 **Common causes**:
+
 - **System clock out of sync**: Your computer system clock must be properly synced via NTP. If your clock is off by more than 20 seconds, the authentication token (JWT) will be invalid.
 - **Prompt timeout**: You must complete the registration in your browser and return to the client within one minute of the prompt.
 
 ### (Linux) DNS connectivity check failed
+
 This error often means that `systemd-resolved` is not allowing the client to resolve DNS requests. In `daemon.log`, you will see `DNS connectivity check failed to resolve host="warp-svc."`.
 
 **Solution**:
+
 1. Add `ResolveUnicastSingleLabel=yes` to `/etc/systemd/resolved.conf`.
 2. Ensure no other DNS servers are explicitly configured in that file.
 3. Restart the service: `sudo systemctl restart systemd-resolved.service`.
 
 ### (Mac/Linux) Invalid character in resolv.conf
+
 The client cannot parse `resolv.conf` files containing invalid characters like `!@#$%^&*()<>?` in `search` directives. Remove these characters to restore service.
 
 ## Browser and certificate issues
 
 ### "Your connection is not private" or untrusted warnings
+
 Advanced security features require the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) to be trusted on the device.
 
 - **Chrome/Edge**: These browsers cache certificates. If you installed the certificate while the browser was running, you must restart the browser.
 - **Root certificate expiry**: The default Cloudflare root certificate expired on February 2, 2025. If you are seeing errors, [generate and activate a new certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) in the dashboard.
 
 ### 2025 Certificate migration
+
 Starting with version 2024.12.554.0, the client can automatically install new certificates as soon as they are **Available** in the dashboard. For older versions, certificates had to be marked **In-Use** first. Ensure **Install CA to system certificate store** is enabled in your [Device settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).
 
 ## Windows-specific issues
 
 ### Windows shows "No Internet access"
+
 This is often a cosmetic error with Windows Network Connectivity Status Indicator (NCSI). Apps like Outlook or JumpCloud may refuse to connect because of this status.
 
 **Solution**:
 Configure NCSI to detect the client's local DNS proxy and use active probing by setting these registry keys to `1`:
+
 - `HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS`
 - `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\EnableActiveProbing`
 
 ### Setup Wizard ends prematurely
+
 This usually indicates a missing dependency, such as .NET Framework `4.7.2` or later. Legacy systems (like Windows 10 Enterprise 1607) may require a manual update of the [.NET Framework Runtime](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net472).
 
 ## Other environment issues
 
 ### WSL2 connectivity
+
 If WSL2 loses connectivity, check your [split tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). The IP range used by WSL to communicate with the host may be accidentally included in the tunnel. Exclude the WSL network range to restore connectivity.
 
 ### SMTP port 25 blocked
+
 By default, the client blocks outgoing traffic on port `25` to prevent spam. Use port `587` or `465` for encrypted email, or contact your account team to request an unblock.
 
 ### Admin override codes expired
+
 [Admin override codes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes) are time-sensitive and adhere to fixed-hour blocks. A code generated at 9:30 AM with a 1-hour timeout will expire at 10:00 AM because its validity is counted within the 9:00 AM-10:00 AM window.
 
 ---
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
index 41e24ebbe3edf84..57570302af9994e 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
@@ -16,22 +16,22 @@ The Cloudflare One Client (formerly WARP) GUI displays the following status mess
 
 To print status messages to the console, run the `warp-cli -l status` command before connecting the client.
 
-| Status message                       | Description                                                                                                                                                                                                                                                                        |
-| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                           |
-| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                              |
-| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                           |
-| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                             |
-| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                              |
-| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                       |
+| Status message                       | Description                                                                                                                                                                                                                                                                                                  |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                                              |
+| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                                                        |
+| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                                                     |
+| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                                                       |
+| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                                          |
+| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                                                 |
 | Setting up your routing table        | Updates the [system routing table](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#routing-table) based on your [Split Tunnel rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). |
-| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                |
-| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                   |
-| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                |
-| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                       |
-| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                  |
-| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                              |
-| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                             |
-| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                 |
-| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                  |
-| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                           |
+| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                            |
+| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                                             |
+| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                                          |
+| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                                   |
+| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                                            |
+| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                                                 |
+| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                                      |
+| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                                           |
+| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                                     |
+| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                                              |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
index 1a48f5bece5c008..2bff092a3e7064e 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
@@ -59,82 +59,82 @@ You can collect client diagnostic logs remotely from the Zero Trust dashboard by
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                            |
-| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                     |
-| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                         |
-| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                                                 |
-| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                     |
-| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                      |
-| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                            |
-| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                         |
-| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                   |
-| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                                   |
-| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                                                 |
-| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                             |
-| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                       |
-| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                              |
-| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                             |
-| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                     |
-| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                     |
-| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                          |
-| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                         |
+| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                                   |
+| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                            |
+| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                              |
+| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                           |
+| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                        |
+| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                 |
+| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                                   |
+| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                                |
+| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                          |
+| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                         |
+| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                            |
+| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                                    |
+| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                              |
+| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                                     |
+| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                                    |
+| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                            |
+| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                            |
+| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                                 |
+| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                                |
 | `dns-check.txt`                                                                                     | Verifies that the Cloudflare One Client DNS servers are set as system default. For [operating modes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) where DNS filtering is enabled, this file contains the IPs of the local DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                |
-| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                           |
-| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                |
-| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                                  |
-| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                          |
-| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                     |
-| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                    |
-| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                            |
-| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                        |
-| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                        |
-| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                           |
-| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                      |
-| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                            |
-| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                  |
-| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                 |
-| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                                  |
-| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                    |
-| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                      |
-| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                       |
-| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
-| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                   |
-| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                     |
-| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                          |
-| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                            |
-| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                             |
-| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                              |
-| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                           |
-| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                            |
-| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                            |
-| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                          |
-| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
-| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                            |
-| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                            |
-| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                              |
-| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                              |
-| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                       |
-| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                |
-| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                            |
-| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                             |
-| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                |
-| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                        |
-| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                               |
-| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                   |
-| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                      |
-| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                               |
-| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                  |
-| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                              |
-| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                               |
-| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                       |
-| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                  |
+| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                       |
+| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                                  |
+| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                       |
+| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                           |
+| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                                 |
+| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                            |
+| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                           |
+| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                                   |
+| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                               |
+| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                               |
+| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                                  |
+| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                             |
+| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                                   |
+| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                         |
+| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                        |
+| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                        |
+| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                           |
+| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                             |
+| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                              |
+| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
+| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                          |
+| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                            |
+| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                                 |
+| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                                              |
+| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                    |
+| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                                     |
+| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                  |
+| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                                   |
+| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                                   |
+| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                                 |
+| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
+| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                                   |
+| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                                   |
+| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                                     |
+| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                                     |
+| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                              |
+| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                       |
+| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                  |
+| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                        |
+| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                       |
+| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                               |
+| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                          |
+| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                          |
+| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                             |
+| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                                           |
+| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                         |
+| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                                     |
+| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                                      |
+| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                              |
+| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                         |
 | `warp-settings.txt`                                                                                 | [Cloudflare One Client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/) applied to the device.                                                                                                                                                                                                                 |
-| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                              |
-| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                        |
-| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                        |
-| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                               |
+| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                                     |
+| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                               |
+| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                               |
+| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                                      |
 
 #### Multiple versions of the same log
 
@@ -161,14 +161,14 @@ This enables a few more logging features:
 - DNS logs for [service modes with DNS filtering](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/)
 - One-shot connectivity checks (same information as `connectivity.txt`, collected when extra debug logging starts rather than when `warp-diag` runs)
 - One-shot traceroutes to:
-	- DNS resolver IPs
-	- DNS resolver hostname
-	- Device API endpoint IPs
-	- Device API endpoint hostname
-	- Tunnel edge connection IPs
+  - DNS resolver IPs
+  - DNS resolver hostname
+  - Device API endpoint IPs
+  - Device API endpoint hostname
+  - Tunnel edge connection IPs
 - On Windows, if you are an administrator:
-	- [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
-	- [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
+  - [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
+  - [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
 
 If extra debug logging is enabled, the command `warp-cli debug extra reconnect` forces the tunnel connection to restart.
 This can be useful for collecting log information if the tunnel connection fails.
@@ -246,19 +246,19 @@ The following log files are available for iOS, Android, and ChromeOS devices.
 
 #### iOS
 
-| Name                                    | Description           |
-| --------------------------------------- | ------------------------------------ |
-| **Extension logs**                          | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                   |
-| **Application logs**                        | Logs from the iOS app process, including GUI events, setting changes, and API calls.                         |
-| **Qlogs**                                  | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID. |
+| Name                 | Description                                                                                                                                                                                 |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Extension logs**   | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
+| **Application logs** | Logs from the iOS app process, including GUI events, setting changes, and API calls.                                                                                                        |
+| **Qlogs**            | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID.                                                    |
 
 #### Android/ChromeOS
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| Name             | Description                           |
-| ---------------- | ---------------------------------------------------- |
-| `unhandled_exception.log`   | Captures errors in the Android application layer that were not caught and could have crashed the app.                                |
-| `console.log` | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes. |
-| `native_tunnel.log`  | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                        |
-| `<connection_id>.sqlog`    | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. |
+| Name                      | Description                                                                                                                                                                                 |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `unhandled_exception.log` | Captures errors in the Android application layer that were not caught and could have crashed the app.                                                                                       |
+| `console.log`             | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes.                                                |
+| `native_tunnel.log`       | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
+| `<connection_id>.sqlog`   | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections.                                                                                                                     |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
index e4307d464bc1c09..80e66ab48ee8d61 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
@@ -20,13 +20,13 @@ A single physical device can have [multiple device registrations](/cloudflare-on
 
 ## Key concepts
 
-| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                                      |
-| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                                            |
-| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                                                |
-| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                             |
-| Device registration                                                                  |  An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
-| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                                                                |
+| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                         |
+| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                             |
+| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                  |
+| Device registration                                                                  | An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
+| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                       |
 
 ## Review device registration status
 
@@ -102,20 +102,20 @@ If the user or service token can successfully re-authenticate, a new device regi
 
 Registrations can have the following statuses:
 
-| Status | Description |
-| --- | --- |
-| **Active** | Registered and able to connect via the Cloudflare One Client. This is the expected operational state. |
+| Status      | Description                                                                                                  |
+| ----------- | ------------------------------------------------------------------------------------------------------------ |
+| **Active**  | Registered and able to connect via the Cloudflare One Client. This is the expected operational state.        |
 | **Revoked** | The registration's public key is invalidated. Revocation does not release the assigned virtual IP addresses. |
 
 ## Manage device registrations
 
 The following table summarizes the actions available for managing device registrations and devices. For all actions, if the user or service token can still re-authenticate, a new registration will be created automatically. To permanently remove access, refer to [Device management](#device-management).
 
-| Action                                                 | What it does                                                                                             | Virtual IPs released?                                  | When to use                                                                                                                                                                                  |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                                                    | You want to fully remove a user's enrollment from a device and free up the virtual IP.                                                                                                       |
-| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                                                     | You want to temporarily block a device from connecting but preserve the registration record. |
-| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes | You want to fully remove a device and all associated registrations.                                                                                                                 |
+| Action                                                 | What it does                                                                                             | Virtual IPs released? | When to use                                                                                  |
+| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------- |
+| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                   | You want to fully remove a user's enrollment from a device and free up the virtual IP.       |
+| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                    | You want to temporarily block a device from connecting but preserve the registration record. |
+| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes                   | You want to fully remove a device and all associated registrations.                          |
 
 ### Delete a device registration
 
@@ -213,8 +213,9 @@ To block a service token from re-authenticating, you must either:
 
 1. Delete the enrollment policy associated with the token, or modify the enrollment policy to no longer include the token (by removing its specific Include rule).
 2. (Optional) [Delete the service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).
-      <br/> You cannot use this service token to create new registrations.
-      <br/> You cannot delete a service token while it is attached to a device enrollment policy.
+   <br /> You cannot use this service token to create new registrations.
+   <br /> You cannot delete a service token while it is attached to a device
+   enrollment policy.
 3. Delete the service token [device registration](/cloudflare-one/team-and-resources/devices/device-registration/#delete-a-device-registration).
 4. (Optional) To fully decommission a device, [remove user access](/cloudflare-one/team-and-resources/devices/device-registration/#remove-user-access), if any exists. Devices with existing registrations will remain connected to Cloudflare until those specific device registrations are manually deleted.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
index 55005c37db7e2b8..8e70dfe2c679456 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
@@ -26,12 +26,12 @@ Review how this change impacts certificate propagation to your end-user devices
 
 Zero Trust will indicate if a certificate is ready for use in inspection based on its deployment status:
 
-| Deployment status    | Description                                                                                                                                                      |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                   |
-| Pending              | The certificate is being activated or deactivated for use.                                                                                                       |
+| Deployment status    | Description                                                                                                                                                                |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                             |
+| Pending              | The certificate is being activated or deactivated for use.                                                                                                                 |
 | Available            | The certificate is deployed across the Cloudflare global network and ready to be turned on. The Cloudflare One Client will install the certificate on your users' devices. |
-| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                   |
+| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                             |
 
 ## Generate a Cloudflare root certificate
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
index 08917bf7ed0f8f9..8d64d7b39cd4c59 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
@@ -754,115 +754,115 @@ To install a certificate for use in a Docker container:
 4. Add the certificate to your Docker image:
 
    <Tabs> <TabItem label="During build process">
-
-   To add the certificate to your Dockerfile to install it during the build process:
-   1. Add the certificate install directions to your Dockerfile. For example:
-
-      ```docker title="Red Hat-based images"
-      FROM registry.access.redhat.com/ubi9/ubi:latest
-      # Or FROM centos:7 or FROM fedora:38
-
-      # Install necessary certificates package
-      RUN dnf install -y ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
-      RUN update-ca-trust extract
-      ```
-
-      ```docker title="Debian-based images"
-      FROM debian:12
-      # Or FROM ubuntu:22.04
-
-      # Install necessary certificates package
-      RUN apt-get update && apt-get install -y ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-      RUN update-ca-certificates
-      ```
-
-      ```docker title="Alpine-based images"
-      FROM alpine:3.18
-
-      # Install necessary certificates package
-      RUN apk add --no-cache ca-certificates
-
-      # Copy and add Cloudflare root certificate
-      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-      RUN update-ca-certificates
-      ```
-
-   2. Build the Docker image:
-
-      ```sh
-      docker build -t <your-container-name> .
-      ```
-
-   3. Verify the certificate was installed:
-
-      ```sh title="Red Hat-based images"
-      docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-      ```
-
-      ```sh title="Debian and Alpine-based images"
-      docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
-      ```
-
-   </TabItem>
-
-   <TabItem label="During runtime">
-
-   To add the certificate to your Docker Compose file to install it during runtime:
-   1. Add the certificate install directions to your `docker-compose.yml` file. For example:
-
-      ```yaml title="Red Hat-based containers"
-      version: '3'
-      services:
-      	redhat-app:
-      		image: registry.access.redhat.com/ubi9/ubi:latest
-       		volumes:
-       			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
-       		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
-      ```
-
-      ```yaml title="Debian-based containers"
-      version: '3'
-      services:
-      	debian-app:
-      		image: debian:12
-       		volumes:
-       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
-       		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
-      ```
-
-      ```yaml title="Alpine-based containers"
-      version: '3'
-      services:
-      	alpine-app:
-      		image: alpine:3.18
-       		volumes:
-       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
-       		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
-      ```
-
-   2. Run the container:
-
-      ```sh
-      docker-compose up
-      ```
-
-   3. Verify the certificate was installed:
-
-      ```sh title="Red Hat-based containers"
-      docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-      ```
-
-      ```sh title="Debian and Alpine-based containers"
-      docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
-      ```
-
-   </TabItem> </Tabs>
+   
+      To add the certificate to your Dockerfile to install it during the build process:
+      1. Add the certificate install directions to your Dockerfile. For example:
+   
+         ```docker title="Red Hat-based images"
+         FROM registry.access.redhat.com/ubi9/ubi:latest
+         # Or FROM centos:7 or FROM fedora:38
+   
+         # Install necessary certificates package
+         RUN dnf install -y ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
+         RUN update-ca-trust extract
+         ```
+   
+         ```docker title="Debian-based images"
+         FROM debian:12
+         # Or FROM ubuntu:22.04
+   
+         # Install necessary certificates package
+         RUN apt-get update && apt-get install -y ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+         RUN update-ca-certificates
+         ```
+   
+         ```docker title="Alpine-based images"
+         FROM alpine:3.18
+   
+         # Install necessary certificates package
+         RUN apk add --no-cache ca-certificates
+   
+         # Copy and add Cloudflare root certificate
+         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+         RUN update-ca-certificates
+         ```
+   
+      2. Build the Docker image:
+   
+         ```sh
+         docker build -t <your-container-name> .
+         ```
+   
+      3. Verify the certificate was installed:
+   
+         ```sh title="Red Hat-based images"
+         docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+         ```
+   
+         ```sh title="Debian and Alpine-based images"
+         docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
+         ```
+   
+      </TabItem>
+   
+      <TabItem label="During runtime">
+   
+      To add the certificate to your Docker Compose file to install it during runtime:
+      1. Add the certificate install directions to your `docker-compose.yml` file. For example:
+   
+         ```yaml title="Red Hat-based containers"
+         version: '3'
+         services:
+         	redhat-app:
+         		image: registry.access.redhat.com/ubi9/ubi:latest
+          		volumes:
+          			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
+          		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
+         ```
+   
+         ```yaml title="Debian-based containers"
+         version: '3'
+         services:
+         	debian-app:
+         		image: debian:12
+          		volumes:
+          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
+          		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
+         ```
+   
+         ```yaml title="Alpine-based containers"
+         version: '3'
+         services:
+         	alpine-app:
+         		image: alpine:3.18
+          		volumes:
+          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
+          		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
+         ```
+   
+      2. Run the container:
+   
+         ```sh
+         docker-compose up
+         ```
+   
+      3. Verify the certificate was installed:
+   
+         ```sh title="Red Hat-based containers"
+         docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+         ```
+   
+         ```sh title="Debian and Alpine-based containers"
+         docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
+         ```
+   
+      </TabItem> </Tabs>
 
 ### Command-line tools
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
index 5ec0ab6973dad12..442499bd33c48ff 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
@@ -61,16 +61,17 @@ While the Okta integration is turned on, Cloudflare One will send any user risk
 ## Predefined risk behaviors
 
 By default, all predefined behaviors are disabled. When a behavior is enabled, Cloudflare One will continuously evaluate all users within the organization for the behavior. You can [change the risk level](#change-risk-behavior-risk-levels) for predefined behaviors if the default assignment does not suit your environment.
-| Risk behavior                         | Requirements                                                                                                | Description                                                                                                                                                                                                            | Evaluation timing |
+| Risk behavior | Requirements | Description | Evaluation timing |
 | -------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
-| Impossible travel                      | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/)                                            | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
-| High number of DLP policies triggered  | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/)                     | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/).                                  | Evaluated per-request in milliseconds. |
-| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user.                                          | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
+| Impossible travel | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/) | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
+| High number of DLP policies triggered | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/) | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/). | Evaluated per-request in milliseconds. |
+| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
 | CrowdStrike Low ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 0-50 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information.| Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | CrowdStrike Medium ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 50-79 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | Interaction with Malicious File | [Gateway AV scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/) or [File sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/) | User uploads or downloads a file flagged as malicious by Gateway's AV scanner or file sandboxing. Risk is elevated even if the file is blocked. | Evaluated per-request in milliseconds. |
-| Suspicious Security Domain Visited  | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| Suspicious Security Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+
 ## Manage risk behaviors
 
 To toggle risk behaviors, go to **Risk score** > **Risk behaviors**.
@@ -92,9 +93,9 @@ You can change the risk level for a behavior at any time.
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Teams & Resources**.
 2. Go to **Users**.
 3. Select **Risk score** > **Risk behaviors**.
-2. Select the risk behavior you want to modify.
-3. In the drop-down menu, choose your desired risk level.
-4. Select **Save**.
+4. Select the risk behavior you want to modify.
+5. In the drop-down menu, choose your desired risk level.
+6. Select **Save**.
 
 ## Use risk scores in Access policies
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
index c8ace201fdac273..2ce86cab7d6270b 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
@@ -8,10 +8,9 @@ tags:
   - SCIM
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers to synchronize user identity information with cloud applications and services. After configuring SCIM, user identities that you create, edit, or delete in the identity provider are automatically updated across all supported applications. This makes it easier for IT admins to onboard new users, update their groups and permissions, and revoke access in the event of an employee termination or security breach.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
index 1cf937a40bfe8b7..2f4b39bfbcd969d 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 User logs show a list of all users who have authenticated to Cloudflare One. For each user who has logged in, you can view their enrolled devices, login history, seat usage, and identity used for policy enforcement.
 
@@ -20,7 +20,7 @@ This page lists all users who have registered the Cloudflare One Client or authe
 
 ### Available logs
 
-* **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
-* **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
-* **Devices**: Devices registered to the user via the Cloudflare One Client.
-* **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
+- **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
+- **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
+- **Devices**: Devices registered to the user via the Cloudflare One Client.
+- **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
diff --git a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
index 64308a2ccb340c0..f788aa791bdb0b6 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
@@ -38,8 +38,8 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 | Resolve nel.cloudflare.com through 1.1.1.1                                                | `00000001-0034-45a0-8333-f339451fba46` | `nel.cloudflare.com`                                                                                                                                      | resolve |
 | Allow DNS queries for api.cloudflare.com domain                                           | `00000001-5eea-4932-8dd5-8e1ec9770396` | `api.cloudflare.com`                                                                                                                                      | allow   |
 | Resolve api.cloudflare.com through 1.1.1.1                                                | `00000001-4f0c-4f86-9b96-5d26123a194b` | `api.cloudflare.com`                                                                                                                                      | resolve |
-| Allow DNS queries for one.dash.cloudflare.com domain                                    | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                               | allow   |
-| Resolve one.dash.cloudflare.com through 1.1.1.1                                         | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                               | resolve |
+| Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                                 | allow   |
+| Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                                 | resolve |
 | Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-a9fd-40de-a662-51d3a3ae0ad8` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | allow   |
 | Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-70f2-4eea-b711-201bca434ed4` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | resolve |
 | Allow DNS queries for dash.cloudflare.com domain                                          | `00000001-0c2a-4b31-8606-3e5a1d87c1bf` | `dash.cloudflare.com` and `dash.fed.cloudflare.com`                                                                                                       | allow   |
@@ -59,14 +59,14 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 
 ## Network proxy policies
 
-| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                    | Action | Description                                                                                                                                                   |
-| --------------------------------------------------- | -------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                   | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
-| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows Zero Trust client.                                                                                                                                     |
-| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                            | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
+| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                  | Action | Description                                                                                                                                                   |
+| --------------------------------------------------- | -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                 | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
+| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows Zero Trust client.                                                                                                                                     |
+| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                          | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
 | Allow Zero Trust Services                           | `00000001-e1e8-421b-a0fe-895397489f28` | Hostname | `one.dash.cloudflare.com`, `help.teams.cloudflare.com`, `blocked.teams.cloudflare.com`, `blocked.teams.fed.cloudflare.com`, `api.cloudflare.com`, `api.fed.cloudflare.com`, `cloudflarestatus.com`, `www.cloudflarestatus.com`, `one.dash.cloudflare.com`, `one.dash.fed.cloudflare.com`, `help.one.cloudflare.com`, `dash.cloudflare.com`, `dash.fed.cloudflare.com`, and `developers.cloudflare.com` | allow  | Allows Cloudflare Zero Trust services.                                                                                                                        |
-| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
-| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                                | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
+| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
+| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                              | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
 
 ## HTTP inspection policies
 
diff --git a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
index 84848c8086de50c..2df964a6c3a878e 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
@@ -50,15 +50,15 @@ To use HTTP policies to filter all HTTPS traffic on all ports when using a defau
 
 Gateway supports detection and filtering of the following protocols:
 
-| Protocol                                                          | Notes                                                                                        |
-| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| HTTP                                                              | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
-| HTTP2                                                             | Hypertext Transfer Protocol Version 2.                                                       |
-| SSH                                                               | Secure Shell Protocol — remote login and command execution.                                  |
-| TLS                                                               | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
-| DCERPC                                                            | Distributed Computing Environment / Remote Procedure Call.                                   |
-| MQTT                                                              | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
-| TPKT                                                              | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
+| Protocol     | Notes                                                                                        |
+| ------------ | -------------------------------------------------------------------------------------------- |
+| HTTP         | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
+| HTTP2        | Hypertext Transfer Protocol Version 2.                                                       |
+| SSH          | Secure Shell Protocol — remote login and command execution.                                  |
+| TLS          | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
+| DCERPC       | Distributed Computing Environment / Remote Procedure Call.                                   |
+| MQTT         | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
+| TPKT         | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
 | IMAP         | Internet Message Access Protocol — email retrieval.                                          |
 | POP3         | Post Office Protocol v3 — email retrieval.                                                   |
 | SMTP         | Simple Mail Transfer Protocol — email sending.                                               |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
index 61657d39a175ca7..da83a0d0f8b94ed 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
@@ -17,7 +17,7 @@ For Magic Transit egress traffic, consider the following:
 - Network Firewall rules apply to both Magic Transit ingress and egress traffic passing through Cloudflare.
 - If you have a "default drop" catchall rule (a final rule that blocks all traffic not matched by earlier rules) for ingress traffic, you must add an earlier rule to permit traffic sourced from your Magic Transit prefix with the destination as **any** to allow outbound egress traffic.
 
-   For example, place the following allow rule before any default-drop catchall rule:
+  For example, place the following allow rule before any default-drop catchall rule:
 
-   **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
-   **Action**: Allow
+  **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
+  **Action**: Allow
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
index 353d64288db846e..7ad5f83b0ccb97c 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
@@ -22,9 +22,9 @@ There are two approaches for setting up tiered policies, depending on your deplo
 ## Organizations vs. Tenant API
 
 | Feature                    | [Cloudflare Organizations](/cloudflare-one/traffic-policies/tiered-policies/organizations/) | [Tenant API](/cloudflare-one/traffic-policies/tiered-policies/tenant-api/) |
-| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                         |
-| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                          |
-| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                      |
-| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                         |
-| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                                  |
+| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                   |
+| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                    |
+| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                |
+| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                   |
+| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                            |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
index 61dee092052c3ac..558bcf16daff10b 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
@@ -21,7 +21,6 @@ The Tenant API platform only supports [DNS policies](/cloudflare-one/traffic-pol
 
 For more information, refer to the [Cloudflare Zero Trust for managed service providers](https://blog.cloudflare.com/gateway-managed-service-provider/) blog post.
 
-
 ## Get started
 
 To set up the Tenant API, refer to [Get started](/tenant/get-started/). Once you have provisioned and configured your customer's Cloudflare accounts, you can create [DNS policies](/cloudflare-one/traffic-policies/dns-policies/).
diff --git a/src/content/docs/cloudflare-one/troubleshooting/access.mdx b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
index b6396e705f97636..b8ece1182ed0454 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/access.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Access troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/access-controls/troubleshooting/">
-  Full Access troubleshooting guide ❯
+	Full Access troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
index c31dd68373abe7a..e4cf3238d0cd8bd 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Browser Isolation documentation.
 
 <LinkButton href="/cloudflare-one/remote-browser-isolation/troubleshooting/">
-  Browser Isolation troubleshooting ❯
+	Browser Isolation troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
index 064db32c9b01121..72cda8b9e748c03 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full CASB documentation.
 
 <LinkButton href="/cloudflare-one/integrations/cloud-and-saas/troubleshooting/">
-  CASB troubleshooting ❯
+	CASB troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
index 304a4016752f5ba..a15cd8ee067f5b5 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
@@ -32,12 +32,15 @@ For all issues, please include:
 Depending on the product, providing diagnostic files is critical for a technical investigation.
 
 ### Cloudflare One Client (WARP)
+
 If the issue involves the Cloudflare One Client, run the `warp-diag` command on the affected device and attach the resulting `.zip` file to your case. For more information, refer to [Diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/).
 
 ### Cloudflare Tunnel
+
 If the issue involves Cloudflare Tunnel, run the `cloudflared tunnel diag` command and provide the generated report. For more information, refer to [Tunnel diagnostic logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs/).
 
 ### Access and Gateway
+
 For issues related to authentication loops, blocked websites, or policy enforcement:
 
 - **HAR file**: Provide a [HAR file](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file) captured while reproducing the issue.
@@ -46,6 +49,7 @@ For issues related to authentication loops, blocked websites, or policy enforcem
 - **Request ID**: For Gateway issues, you can find the `request_id` (HTTP logs) or `query_id` (DNS logs) in your [Gateway logs](/cloudflare-one/traffic-policies/troubleshooting/).
 
 ### Digital Experience Monitoring (DEX)
+
 For issues with DEX tests or device monitoring, provide a [remote capture](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/) from the Zero Trust dashboard.
 
 ---
diff --git a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
index 731999d5fb8036d..8c96f5ab4305ba3 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full DEX documentation.
 
 <LinkButton href="/cloudflare-one/insights/dex/troubleshooting/">
-  DEX troubleshooting ❯
+	DEX troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
index c84e1260e343735..690763e57e48c08 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Email Security documentation.
 
 <LinkButton href="/cloudflare-one/email-security/troubleshooting/">
-  Email Security troubleshooting ❯
+	Email Security troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
index e38ab6f5acae44e..0d5841ea8bb17d1 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Gateway troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/traffic-policies/troubleshooting/">
-  Full Gateway troubleshooting guide ❯
+	Full Gateway troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
index 1d692f0aa4341e2..eb881c4c7e9300a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
@@ -12,18 +12,25 @@ import { Render, LinkButton } from "~/components";
 
 Explore common issues and solutions for Cloudflare Tunnel.
 
-<Render 
-  file="tunnel/common-errors" 
-  product="cloudflare-one" 
-  params={{
-    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-    protocolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
-    configFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-    originServerNameURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    caPoolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    noTLSVerifyURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-    ulimitsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/"
-  }} 
+<Render
+	file="tunnel/common-errors"
+	product="cloudflare-one"
+	params={{
+		logsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+		protocolURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
+		configFileURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+		originServerNameURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		caPoolURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		noTLSVerifyURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+		ulimitsURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/",
+	}}
 />
 
 ---
@@ -33,5 +40,5 @@ Explore common issues and solutions for Cloudflare Tunnel.
 For more information, refer to the full Tunnel troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/">
-  Full Tunnel troubleshooting guide ❯
+	Full Tunnel troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
index 82128a0306e3847..4012b24a1e816aa 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
@@ -15,11 +15,16 @@ import { Render, LinkButton } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
 
@@ -30,5 +35,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity/">
-  Full connectivity troubleshooting guide ❯
+	Full connectivity troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
index 0c2b64583258ccf..7cbca452e33919a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 32
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore resources to help you resolve issues with Cloudflare WAN (formerly Magic WAN) connectivity, routing, and tunnel health.
 
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
index 2499d5ff7d77041..2787fccd3b01cf7 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
@@ -8,15 +8,20 @@ sidebar:
   order: 33
 ---
 
-import { Render, LinkButton } from "~/components"
+import { Render, LinkButton } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
 
@@ -27,5 +32,5 @@ import { Render, LinkButton } from "~/components"
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/">
-  Full IPsec troubleshooting guide ❯
+	Full IPsec troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
index 6766ee8164db987..732752846b608d7 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
@@ -11,16 +11,20 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "CF1 Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "CF1 Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
 
 ---
@@ -30,5 +34,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/">
-  Full routing and BGP guide ❯
+	Full routing and BGP guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
index 4ed284bd72ee49e..b2a3db82e0e9e8d 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
@@ -11,19 +11,26 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
 
 ---
@@ -33,5 +40,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/">
-  Full tunnel health guide ❯
+	Full tunnel health guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
index 4511789b45bde5c..a5fe18d5dcf8599 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare One Client documentation.
 
 <LinkButton href="/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/">
-  Cloudflare One Client troubleshooting ❯
+	Cloudflare One Client troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
index fbfa9dc10b86312..8758982fe37aa85 100644
--- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
+++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
@@ -91,26 +91,26 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
    - `<CLIENT_ID>`: your Entra ID **Application (client) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-   	"$schema": "./node_modules/wrangler/config-schema.json",
-   	"name": "risky-users",
-   	"compatibility_date": "$today",
-   	"main": "src/index.js",
-   	"workers_dev": false,
-   	"account_id": "<ACCOUNT-ID>",
-   	"vars": {
-   		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
-   		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
-   	},
-   	"triggers": {
-   		"crons": ["* * * * *"],
-   	},
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+      	"$schema": "./node_modules/wrangler/config-schema.json",
+      	"name": "risky-users",
+      	"compatibility_date": "$today",
+      	"main": "src/index.js",
+      	"workers_dev": false,
+      	"account_id": "<ACCOUNT-ID>",
+      	"vars": {
+      		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
+      		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
+      	},
+      	"triggers": {
+      		"crons": ["* * * * *"],
+      	},
+      }
+      ```
+   
+      </WranglerConfig>
 
 :::note
 
diff --git a/src/content/docs/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-wan/analytics/index.mdx
index 7591d777198e731..8730a735f15a9f2 100644
--- a/src/content/docs/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/index.mdx
@@ -12,7 +12,8 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
@@ -21,6 +22,6 @@ Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance an
 		traceRoutes: "/cloudflare-wan/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/cloudflare-wan/analytics/query-bandwidth/",
 		graphQlTunnelHealthURL: "/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/"
+		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
index c961a9e26011107..d02a87f11d097c0 100644
--- a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -17,6 +17,7 @@ import { Render } from "~/components";
 	file="mconn/network-options/app-aware-policies/netflow"
 	product="networking-services"
 	params={{
-		breakoutTrafficURL: "/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/"
+		breakoutTrafficURL:
+			"/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
index adb2d9fc1ad3f0a..3694ed5590489c3 100644
--- a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
@@ -13,9 +13,10 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Cloudflare WAN"
+		magicWord: "Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
index 84a4a80f0ea9f2d..34889d808b65f54 100644
--- a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
index f62f8a3cac1ad1a..7ec650366209348 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -6,12 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel bandwidth analytics with GraphQL
 sidebar:
   order: 6
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
index 8c71bfa0ecc6910..2c6eea69fb48cbe 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -6,11 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel health check results with GraphQL
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }} />
+	params={{ productName: "Cloudflare WAN" }}
+/>
diff --git a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
index 8a916f198158f40..a3c3c203418a701 100644
--- a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
@@ -9,21 +9,23 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare WAN network overview
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions: "Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions:
+			"Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "Cloudflare WAN",
 		networkOverviewPageName: "Network overview",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL: "/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
-		}}
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL:
+			"/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
+	}}
 />
 
 ### Set thresholds for site health
@@ -33,6 +35,7 @@ import { Render } from "~/components"
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/changelog.mdx b/src/content/docs/cloudflare-wan/changelog.mdx
index 5e8580b361df863..dab8b24716303bb 100644
--- a/src/content/docs/cloudflare-wan/changelog.mdx
+++ b/src/content/docs/cloudflare-wan/changelog.mdx
@@ -12,7 +12,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/cloudflare-wan/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="cloudflare-wan" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="cloudflare-wan"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2025-02-14
 
@@ -78,4 +81,4 @@ Customers using Gateway to filter traffic to Magic WAN destinations will now see
 
 **Network segmentation**
 
-You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
\ No newline at end of file
+You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index 1ae5d831a62d218..6e7bcd9b792dfd6 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,35 +11,54 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mconn/configure-connectors"
+<Render
+	file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-	magicWord: "hardware",
-	productName: "Cloudflare One Appliance",
-	maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-	dashName: "Cloudflare WAN",
-	sfpURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-	wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-	lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-	noConnectorShows: "You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
-	networkSegmentationURL: "/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-	dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-  dhcpRelayURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-  reserveIpAddressesURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-	shippedLanguage: "The Cloudflare One Appliance is shipped to you deactivated",
-	hardSoftConn: "You need to deploy two Appliances in your premises before you can set up a site in high availability.",
-	hcConfigsURL: "/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-	ipsecTunnelsRefURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-	vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-	healthCheckFrequencyURL: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-	routedSubnetsURL: "/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-	interruptWindowURL: "/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-	tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
-	wanSettingsURL: "/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-	sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-	networkOptionsURL: "/cloudflare-wan/configuration/appliance/network-options/",
-  maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-  referenceInformationURL: "/cloudflare-wan/configuration/appliance/reference/",
-  troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
-	}} />
+		magicWord: "hardware",
+		productName: "Cloudflare One Appliance",
+		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+		dashName: "Cloudflare WAN",
+		sfpURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+		lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+		noConnectorShows:
+			"You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
+		networkSegmentationURL:
+			"/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		dhcpServerURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpRelayURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+		reserveIpAddressesURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+		shippedLanguage:
+			"The Cloudflare One Appliance is shipped to you deactivated",
+		hardSoftConn:
+			"You need to deploy two Appliances in your premises before you can set up a site in high availability.",
+		hcConfigsURL:
+			"/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+		ipsecTunnelsRefURL:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+		vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+		healthCheckFrequencyURL:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		routedSubnetsURL:
+			"/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		interruptWindowURL:
+			"/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+		tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
+		wanSettingsURL:
+			"/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
+		networkOptionsURL:
+			"/cloudflare-wan/configuration/appliance/network-options/",
+		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+		referenceInformationURL:
+			"/cloudflare-wan/configuration/appliance/reference/",
+		troubleshootingURL:
+			"/cloudflare-wan/configuration/appliance/troubleshooting/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index 71ca26721aa0603..b3fa278d08bae29 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,10 +4,8 @@ description: SFP+ port specifications for the hardware Appliance.
 products:
   - cloudflare-wan
 title: SFP+ port information
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info"
-	product="networking-services" />
\ No newline at end of file
+<Render file="mconn/sfp-port-info" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
index c37e1581eefa1cb..8f201a38e5455a4 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,6 +14,7 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
+		troubleshootingURL:
+			"/cloudflare-wan/configuration/appliance/troubleshooting/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
index 2de202a6c0d9a45..ffbd3902d481e2e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,9 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl: "/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl:
+			"/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Cloudflare One Virtual Appliance",
-		virtualUrl: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
+		virtualUrl:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index f2cfc7422c36ccd..75d2c374e500dc1 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -12,6 +12,9 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-		}} />
+		hardwareConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index d4cbc5987d03273..2b74af67e463be6 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
index 071ef98749d5405..967aa8ccb663c13 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/register-hardware-appliance"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)"
+		dashName: "Cloudflare WAN (formerly Magic WAN)",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index b53cd5b9f9965c3..5b789f4f9046d5d 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -12,6 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/remove-connectors"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)"
+		dashName: "Cloudflare WAN (formerly Magic WAN)",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 9bdf18008a25f54..46c95fb5d790192 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,15 +9,18 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "breakout",
-	featureName: "Breakout traffic",
-	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
-	dashName: "Cloudflare WAN",
-	}} />
+		magicWord: "breakout",
+		featureName: "Breakout traffic",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+		whatHappensApp:
+			"will now go directly to the Internet and bypass Cloudflare's filtering",
+		dashName: "Cloudflare WAN",
+	}}
+/>
 
 ## Breakout by source
 
@@ -27,11 +30,11 @@ Source-based breakout is configured via the API and Terraform.
 
 ### Match criteria
 
-| Criterion             | Behavior                                                                                          |
-| --------------------- | ------------------------------------------------------------------------------------------------- |
-| Source LAN interface  | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
-| Source CIDR / IP range| All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
+| Criterion              | Behavior                                                                                                            |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| Source LAN interface   | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
+| Source CIDR / IP range | All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
 
 The same criteria can be used to mark traffic as **prioritized** instead of broken out. Refer to [Prioritized traffic](/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic/) for details.
 
-Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
\ No newline at end of file
+Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 709867b882cbf6b..dce54b18e5ae528 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,11 +9,13 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render
+	file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-	magicWord: "prioritized",
-	featureName: "Prioritized traffic",
-	whatHappensApp: "is now processed first by Connector",
-	dashName: "Cloudflare WAN",
-	}} />
\ No newline at end of file
+		magicWord: "prioritized",
+		featureName: "Prioritized traffic",
+		whatHappensApp: "is now processed first by Connector",
+		dashName: "Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
index 1625f2d8f072527..cdde5b9bfd22fea 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
@@ -20,35 +20,35 @@ DHCP options are configured via the API and Terraform.
 
 Each option is defined by three fields:
 
-| Field           | Description                                         | Example                |
-| --------------- | --------------------------------------------------- | ---------------------- |
-| `option_number` | The DHCP option code (1–254).                       | `67`                   |
-| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                 |
-| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0`  |
+| Field           | Description                                         | Example               |
+| --------------- | --------------------------------------------------- | --------------------- |
+| `option_number` | The DHCP option code (1–254).                       | `67`                  |
+| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                |
+| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0` |
 
 ### Value type encoding
 
-| Type      | Format                                                      | Example value                 |
-| --------- | ----------------------------------------------------------- | ----------------------------- |
-| `ip`      | A dotted-quad IPv4 address.                                 | `10.20.30.40`                 |
-| `integer` | A decimal integer.                                          | `0`                           |
-| `text`    | A UTF-8 string.                                             | `boot/x64/pxelinux.0`         |
-| `hex`     | A colon-separated sequence of bytes, used for sub-options.  | `01:04:aa:bb:cc`              |
+| Type      | Format                                                     | Example value         |
+| --------- | ---------------------------------------------------------- | --------------------- |
+| `ip`      | A dotted-quad IPv4 address.                                | `10.20.30.40`         |
+| `integer` | A decimal integer.                                         | `0`                   |
+| `text`    | A UTF-8 string.                                            | `boot/x64/pxelinux.0` |
+| `hex`     | A colon-separated sequence of bytes, used for sub-options. | `01:04:aa:bb:cc`      |
 
 ## Common PXE / iPXE options
 
 The most frequently used options for PXE / iPXE boot are:
 
-| Option | Type    | Purpose                                                                              |
-| ------ | ------- | ------------------------------------------------------------------------------------ |
-| 60     | `text`  | Vendor class identifier (typically `PXEClient`).                                     |
-| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                                |
-| 67     | `text`  | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).                   |
-| 43     | `hex`   | Vendor-specific information; sub-option layout is vendor-defined.                    |
-| 175    | `hex`   | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more).          |
-| 209    | `text`  | iPXE configuration file URI.                                                         |
-| 210    | `text`  | iPXE configuration file path prefix.                                                 |
-| 211    | `text`  | iPXE configuration file path.                                                        |
+| Option | Type           | Purpose                                                                     |
+| ------ | -------------- | --------------------------------------------------------------------------- |
+| 60     | `text`         | Vendor class identifier (typically `PXEClient`).                            |
+| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                               |
+| 67     | `text`         | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).          |
+| 43     | `hex`          | Vendor-specific information; sub-option layout is vendor-defined.           |
+| 175    | `hex`          | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more). |
+| 209    | `text`         | iPXE configuration file URI.                                                |
+| 210    | `text`         | iPXE configuration file path prefix.                                        |
+| 211    | `text`         | iPXE configuration file path.                                               |
 
 For a complete list of standard DHCP option codes, refer to the [IANA BOOTP/DHCP parameters registry](https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml).
 
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 7a2bc1beac7de02..46f826cc1ad4c6b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,11 +8,13 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-relay"
+<Render
+	file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
+		cfVsCoreDashNamingMwanCni:
+			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
 	}}
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 2d895e9f31c584b..6577eeb5272f5ce 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,9 +8,10 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-server"
+<Render
+	file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN"
+		dashName: "Cloudflare WAN",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index 5c0bcbed619c268..f5fed31c4c5855e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,9 +8,11 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render
+	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL:
+			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
index b651bbe1b01b881..a9f4fad888935fe 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index 3eab8ea9a7bb2bf..2cbcd17985e02d7 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,11 +8,15 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/link-aggregation"
+<Render
+	file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 007bef4f404e26e..8f1cbe1ed9a4b20 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,14 +4,17 @@ products:
   - cloudflare-wan
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Cloudflare One Appliance to re-use address spaces locally.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/nat-subnet"
+<Render
+	file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-	hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-  virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 32603d94e6a92ca..822619f84e0b5cf 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,13 +6,16 @@ title: Network segmentation
 description: Define policies to determine if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/network-segmentation"
+<Render
+	file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index a7d739e9540ba6a..caa93793bc8278e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,15 +4,19 @@ products:
   - cloudflare-wan
 title: Routed subnets
 description: Learn how to configure routed subnets on a Cloudflare One Appliance, including setting static routes and next-hop addresses for complex LAN setups.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mconn/network-options/routed-subnets"
+<Render
+	file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL: "/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}} />
+		netSubnetURL:
+			"/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL:
+			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 0190821520209fd..17809b37e6377e7 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -15,8 +15,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		activateURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL: "/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
+		activateURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL:
+			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL:
+			"/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index eca36e5f7e8eb4b..bdbd8aaf1e5dec4 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -10,4 +10,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
+<Render
+	file="cloudflare-wan/custom-ike-id-ipsec"
+	product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
index 5e0399f52cb9889..b4d9501da0d4693 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,10 +15,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		greIpsecTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecTunnelsURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		connectorURL: "/cloudflare-wan/configuration/appliance/",
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
+		magicTunnelHcsURL:
+			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 9a7d3b257246a34..0432393f1f1c0ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,10 +13,11 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-  file="routing/configure-cloudflare-source-ips"
-  product="networking-services"
-  params={{
-    unifiedRoutingLink: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/"
-  }}
+	file="routing/configure-cloudflare-source-ips"
+	product="networking-services"
+	params={{
+		unifiedRoutingLink:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 8335fb6e9cf3559..e5b02b3a5366e73 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 2
 head: []
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -19,17 +18,23 @@ import { Render } from "~/components"
 		magicWord: "Cloudflare WAN",
 		trafficSteeringPage: "/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization:
+			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		addTunnelsURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table"
+		routingTableName: "Cloudflare Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 41b3800804ce8c9..9fb7c93867e3747 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -11,26 +11,36 @@ description: Learn how to configure IPsec or GRE tunnels for Cloudflare WAN.
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/cloudflare-wan/reference/anti-replay-protection/",
 		cniLink: "/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthDash:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
+		configureARRURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
index 4a554e27b3969b6..9e7d62f8d1aeab1 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
index ac5910dadeb36ca..38b42c7e4dd0350 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -16,8 +16,9 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-wan/configuration/index.mdx
index 13702b827029038..5ddfb172a16c533 100644
--- a/src/content/docs/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
index 76af852c660c808..4a444cbdbff83f9 100644
--- a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
@@ -17,6 +17,7 @@ import { Render } from "~/components";
 	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
 	params={{
-		mwanAccount: "Have a Multi-Cloud Networking account. Contact your account team to learn more.",
+		mwanAccount:
+			"Have a Multi-Cloud Networking account. Contact your account team to learn more.",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index bb10e2869c1ee67..ff1a38a9ff1a28e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -4,15 +4,19 @@ pcx_content_type: integration-guide
 description: Connect Alibaba Cloud VPN Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/alibaba-cloud"
-  product="networking-services"
-  params={{
-    ipSecTunnelsUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/alibaba-cloud"
+	product="networking-services"
+	params={{
+		ipSecTunnelsUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
index f9028eefecd609a..58ce92bd34520fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
@@ -4,14 +4,17 @@ description: Connect Amazon AWS Transit Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Amazon AWS Transit Gateway
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/aws"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/aws"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index f041179a7d471bc..a76d15bdf214c1a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -8,11 +8,16 @@ title: Microsoft Azure Virtual WAN
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-virtual-wan"
-  product="networking-services"
-  params={{
-  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  cloudflareDocumentationUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-virtual-wan"
+	product="networking-services"
+	params={{
+		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+		ipsecTunnelUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		cloudflareDocumentationUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index 79e3ab4a2c3e78e..f424bafbae91997 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -8,11 +8,16 @@ title: Microsoft Azure VPN Gateway
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
-  product="networking-services"
-  params={{
-  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-  staticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/azure-vpn-gateway"
+	product="networking-services"
+	params={{
+		ipsecTunnelUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		tunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
index be31f60acc7149a..2cc5b0788919598 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -9,8 +9,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index cba0f106bf12657..8831ea12bbf6ea5 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -4,11 +4,11 @@ description: Connect Cisco IOS XE to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Cisco IOS XE
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-ios-xe"
-  product="networking-services"
+<Render
+	file="cloudflare-wan/third-party/cisco-ios-xe"
+	product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 896e02c855659fd..4191b38bc630e29 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -8,15 +8,22 @@ title: Cisco Meraki MX (static routing)
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render
+	file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl: "/cloudflare-wan/reference/anti-replay-protection/",
+		antiReplayProtectionUrl:
+			"/cloudflare-wan/reference/anti-replay-protection/",
 		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		unifiedRoutingUrl:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		trafficSteeringUrl: "/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedConfigParametersUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		paloAltoGuideUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-	}} />
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
index e28d8ba4847ab6f..4ab6dfd8b7b76e9 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -4,15 +4,19 @@ description: Connect Furukawa Electric FITELnet to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Furukawa Electric FITELnet
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fitelnet"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    typeId_ipv4_addrUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fitelnet"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		typeId_ipv4_addrUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
index 5a12895743cb66e..cf11763d0a341ab 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -8,12 +8,19 @@ title: Fortinet
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/fortinet"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    equalCostMultipathRoutingEcmpUrl: "/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/fortinet"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		equalCostMultipathRoutingEcmpUrl:
+			"/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
index 6f89300b8494e05..2ae56b6dbe49b81 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
@@ -4,14 +4,17 @@ description: Connect Google Cloud VPN to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Google Cloud VPN
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/google"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/google"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
index f6e508d000a5d0d..c73eca34c84c602 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
index 3818804b0252018..85e683e79c81b16 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,10 +10,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/juniper"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/juniper"
+	product="networking-services"
+	params={{
+		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
index 78849f6cad28825..1f2ddeaeeefca8f 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -4,14 +4,17 @@ description: Connect Oracle Cloud to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Oracle Cloud
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/oracle"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/oracle"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createAStaticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
index 110c15959491f36..a95d9f3fabecc02 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,10 +13,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/palo-alto"
-  product="networking-services"
-  params={{
-    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/palo-alto"
+	product="networking-services"
+	params={{
+		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
index d86dc81c4715843..862ad0f4b4e8284 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -5,15 +5,19 @@ products:
   - cloudflare-wan
 title: pfSense
 reviewed: 2024-06-20
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/pfsense"
-  product="networking-services"
-  params={{
-    configureTwoIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    staticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/pfsense"
+	product="networking-services"
+	params={{
+		configureTwoIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		staticRouteUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 26a76c80f25db4e..536b6c9ff0ab552 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -4,16 +4,21 @@ pcx_content_type: integration-guide
 description: Connect SonicWall to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sonicwall"
-  product="networking-services"
-  params={{
-    ipsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    creatingYourIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    createYourStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sonicwall"
+	product="networking-services"
+	params={{
+		ipsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		creatingYourIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		createYourStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index b6d0e9a1f52a074..1d3ab31ab967c03 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -4,16 +4,21 @@ pcx_content_type: integration-guide
 description: Connect Sophos Firewall to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/sophos-firewall"
-  product="networking-services"
-  params={{
-    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    ikeIdUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/sophos-firewall"
+	product="networking-services"
+	params={{
+		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		ikeIdUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		checkTunnelHealthInTheDashboardUrl:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
index fc4d45f5469a352..bac9233cb7a5f21 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -4,13 +4,15 @@ description: Connect strongSwan to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: strongSwan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/strongswan"
-  product="networking-services"
-  params={{
-    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/strongswan"
+	product="networking-services"
+	params={{
+		bidirectionalHealthChecksUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 868c273f24c50f6..5f49238ade5259c 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -9,9 +9,9 @@ title: Ubiquiti
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-wan/third-party/ubiquiti"
-  product="networking-services"
-  params={{
-    magicWord: "Cloudflare WAN",
-  }}
+	file="cloudflare-wan/third-party/ubiquiti"
+	product="networking-services"
+	params={{
+		magicWord: "Cloudflare WAN",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
index fc2441a6857269e..03266a7985edc32 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -4,13 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Velocloud to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/velocloud"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/velocloud"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
index b6b97c01cebaf9d..cbcaa056c559724 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -4,15 +4,18 @@ pcx_content_type: integration-guide
 description: Connect Cisco SD-WAN to Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/viptela"
-  product="networking-services"
-  params={{
-    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/viptela"
+	product="networking-services"
+	params={{
+		configureTunnelEndpointsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
index 0ccbceefbb7c339..da8b1fef607c6af 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -8,6 +8,4 @@ title: VyOS
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos"
-  product="networking-services"
-/>
+<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
index c117c2a4435efd5..3e0e9e8caca4dee 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -8,9 +8,13 @@ title: Yamaha RTX Router
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/yamaha"
-  product="networking-services"
-  params={{
-    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
-  }} />
+<Render
+	file="cloudflare-wan/third-party/yamaha"
+	product="networking-services"
+	params={{
+		addTunnelsUrl:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		configureStaticRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-wan/get-started.mdx
index b2f98f780c0e192..50110e083ff7170 100644
--- a/src/content/docs/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-wan/get-started.mdx
@@ -17,11 +17,14 @@ import { Render } from "~/components";
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
 		configureConnectorUrl: "/cloudflare-wan/configuration/appliance/",
-		configureMwanManually: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureMwanManually:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		greReferenceURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		ipsecReferenceUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		mtuReferenceURL: "/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-wan/wan-transformation/"
+		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/glossary.mdx b/src/content/docs/cloudflare-wan/glossary.mdx
index 9707d04db10e16a..5b50582a0620f31 100644
--- a/src/content/docs/cloudflare-wan/glossary.mdx
+++ b/src/content/docs/cloudflare-wan/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - cloudflare-wan
 sidebar:
   order: 14
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare WAN (formerly Magic WAN) documentation.
 
diff --git a/src/content/docs/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-wan/index.mdx
index 5eac1897c216694..9a0cea6bca082c4 100644
--- a/src/content/docs/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-wan/index.mdx
@@ -27,8 +27,9 @@ import { Render } from "~/components";
 		connectorUrl: "/cloudflare-wan/configuration/appliance/",
 		thirdPartyUrl: "/cloudflare-wan/configuration/third-party/",
 		zeroTrustUrl: "/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		bgpRoutesUrl:
+			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
 		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/"
+		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
index de5decbd83487cb..9d694953eaa9562 100644
--- a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
@@ -5,10 +5,9 @@ pcx_content_type: reference
 description: Third-party licenses used in Cloudflare WAN.
 products:
   - cloudflare-wan
-
 ---
 
 import text from "./3rdparty.txt?raw";
 import { Markdown } from "~/components";
 
-<Markdown text={text} inline={false} />
\ No newline at end of file
+<Markdown text={text} inline={false} />
diff --git a/src/content/docs/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-wan/legal/index.mdx
index e2e9dc5f914a078..907e5abf6f28688 100644
--- a/src/content/docs/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-wan/legal/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 12
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-wan/network-interconnect.mdx
index 2f3024d241fa36f..86be9e7f16b6297 100644
--- a/src/content/docs/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-wan/network-interconnect.mdx
@@ -13,14 +13,20 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
+<Render
+	file="magic-cni"
+	product="networking-services"
+	params={{ magicWord: "Cloudflare WAN" }}
+/>
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/"
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-wan/on-ramps.mdx
index 86da6b248ebe042..32fdec0f6eabfab 100644
--- a/src/content/docs/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-wan/on-ramps.mdx
@@ -22,6 +22,6 @@ import { Render } from "~/components";
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/"
+		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/",
 	}}
-	/>
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
index a081ee8130d1870..9ed3368c2c98be2 100644
--- a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -4,7 +4,8 @@ products:
   - cloudflare-wan
 title: Anti-replay protection
 head: []
-description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description:
+  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
index fbec0cd8573df1d..cc92b6c823ab972 100644
--- a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
+		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
index a504caad9990939..dbcdf9a17252a75 100644
--- a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
@@ -10,29 +10,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/reference/device-compatibility"
-  product="networking-services"
-  params={{
-    supportedConfigurationParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    arubaEdgeconnectUrl: "/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-    ciscoMerakiStaticUrl: "/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-    ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
-    fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
-    fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
-    juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
-    paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-    pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
-    sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
-    sophosFirewallUrl: "/cloudflare-wan/configuration/third-party/sophos-firewall/",
-    strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
-    ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
-    velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
-    vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
-    yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
-    alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-    awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
-    azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
-    googleUrl: "/cloudflare-wan/configuration/third-party/google/",
-    oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/"
-  }} />
+<Render
+	file="cloudflare-wan/reference/device-compatibility"
+	product="networking-services"
+	params={{
+		supportedConfigurationParametersUrl:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		arubaEdgeconnectUrl:
+			"/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+		ciscoMerakiStaticUrl:
+			"/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+		ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
+		fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
+		fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
+		juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
+		paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
+		pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
+		sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
+		sophosFirewallUrl:
+			"/cloudflare-wan/configuration/third-party/sophos-firewall/",
+		strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
+		ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
+		velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
+		vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
+		yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
+		alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+		awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
+		azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
+		googleUrl: "/cloudflare-wan/configuration/third-party/google/",
+		oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 68d4b4a66826115..6cf088b347f6d36 100644
--- a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -20,12 +20,14 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		mssURL: "/cloudflare-wan/get-started/#set-maximum-segment-size",
 		productURL: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 6a4cb0f5b700132..0251f5066fd362c 100644
--- a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,12 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down" }}
+	params={{
+		tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-wan/reference/index.mdx
index ae239f4ddfc37af..1de78f741d45c97 100644
--- a/src/content/docs/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-wan/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
index c0e144ba5def202..433a4d677c2c8b1 100644
--- a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN"
-		}}
-/>
\ No newline at end of file
+		productName: "Cloudflare WAN",
+	}}
+/>
diff --git a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
index 5f34c73baea554a..9d1d78aca887206 100644
--- a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
@@ -23,7 +23,8 @@ import { Render } from "~/components";
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
index 98d45cc88d50519..af8dd8496a2775f 100644
--- a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -17,12 +17,15 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		addTunnels: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate:
+			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
 		staticRoutes: "/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
index cb97c92d8e4803d..7a88bf96e8c4a54 100644
--- a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
@@ -15,11 +15,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
+		configureRoutesURL:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
 		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		privateNetworksURL:
+			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-wan/security.mdx
index 20d951ee8b334c0..8a6e3df9eaad074 100644
--- a/src/content/docs/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-wan/security.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="cloudflare-wan/security-filters"
+<Render
+	file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/"
+		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
index a190ec5d61db5ed..220b98e58c0e0a5 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
 		routingBgpLink: "/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		checkHealthDashLink:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
index 905787c40bc06f3..5d7bf235ac3cb37 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 13
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 274a58ce5258d51..dc1236e65423f20 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -8,14 +8,16 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/"
+		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index ed25cd90faf8949..a43339acccd25e2 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -11,14 +11,16 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "Cloudflare WAN",
-    productName: "Cloudflare WAN",
-    trafficSteeringLink: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/cloudflare-wan/configuration/how-to/configure-routes/",
-    tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "Cloudflare WAN",
+		productName: "Cloudflare WAN",
+		trafficSteeringLink:
+			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink:
+			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 807fee1aad43dc6..485d6bb04a1e428 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -11,17 +11,21 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Cloudflare WAN",
-    healthCheckDefault: "_Bidirectional_",
-    tunnelsConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-    antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Cloudflare WAN",
+		healthCheckDefault: "_Bidirectional_",
+		tunnelsConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
+		configureTunnelsLink:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index ad22094662587ee..095f4976ce553d9 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -13,10 +13,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL:
+			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
+		trafficSteeringURL:
+			"/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL:
+			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
index 7a6e010f13f8f63..566bc65d5095477 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
@@ -11,13 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="cloudflare-one-connectivity-options"
-  product="networking-services"
-  params={{
-    unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-    greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-    connectorURL: "/cloudflare-wan/configuration/appliance/",
-    cniURL: "/cloudflare-wan/network-interconnect/",
-    onRampsURL: "/cloudflare-wan/on-ramps/"
-  }}
+	file="cloudflare-one-connectivity-options"
+	product="networking-services"
+	params={{
+		unifiedRoutingURL:
+			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		connectorURL: "/cloudflare-wan/configuration/appliance/",
+		cniURL: "/cloudflare-wan/network-interconnect/",
+		onRampsURL: "/cloudflare-wan/on-ramps/",
+	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
index 039a590ad02f2f0..52b072c14394b76 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
@@ -8,9 +8,9 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare One integration tutorials
-description: Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
+description:
+  Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
   Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/constellation/platform/index.mdx b/src/content/docs/constellation/platform/index.mdx
index 8d627d53915bd45..1b6cdafb1ff1640 100644
--- a/src/content/docs/constellation/platform/index.mdx
+++ b/src/content/docs/constellation/platform/index.mdx
@@ -7,6 +7,6 @@ products:
   - constellation
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/containers/examples/cron.mdx b/src/content/docs/containers/examples/cron.mdx
index beb5c71d036990a..fa89b747782586a 100644
--- a/src/content/docs/containers/examples/cron.mdx
+++ b/src/content/docs/containers/examples/cron.mdx
@@ -57,32 +57,37 @@ Use a cron expression in your Wrangler config to specify the schedule:
 Then in your Worker, call your Container from the "scheduled" handler:
 
 ```ts
-import { Container, getContainer } from '@cloudflare/containers';
+import { Container, getContainer } from "@cloudflare/containers";
 
 export class CronContainer extends Container {
-  sleepAfter = '10s';
+	sleepAfter = "10s";
 
-  override onStart() {
-    console.log('Starting container');
-  }
+	override onStart() {
+		console.log("Starting container");
+	}
 
-  override onStop() {
-    console.log('Container stopped');
-  }
+	override onStop() {
+		console.log("Container stopped");
+	}
 }
 
 export default {
-  async fetch(): Promise<Response> {
-    return new Response("This Worker runs a cron job to execute a container on a schedule.");
-  },
+	async fetch(): Promise<Response> {
+		return new Response(
+			"This Worker runs a cron job to execute a container on a schedule.",
+		);
+	},
 
-  async scheduled(_controller: any, env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> }) {
-    let container = getContainer(env.CRON_CONTAINER);
-    await container.start({
-      envVars: {
+	async scheduled(
+		_controller: any,
+		env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> },
+	) {
+		let container = getContainer(env.CRON_CONTAINER);
+		await container.start({
+			envVars: {
 				MESSAGE: "Start Time: " + new Date().toISOString(),
-      }
-    })
-  },
+			},
+		});
+	},
 };
 ```
diff --git a/src/content/docs/containers/examples/durable-object-interface.mdx b/src/content/docs/containers/examples/durable-object-interface.mdx
index f957451fa12358b..d54c84506542fc7 100644
--- a/src/content/docs/containers/examples/durable-object-interface.mdx
+++ b/src/content/docs/containers/examples/durable-object-interface.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Various examples calling Containers directly from Durable Objects
 pcx_content_type: example
 title: Using Durable Objects Directly
diff --git a/src/content/docs/containers/examples/index.mdx b/src/content/docs/containers/examples/index.mdx
index eb6ca3b44e7d6f7..5cf608f97ac0ecc 100644
--- a/src/content/docs/containers/examples/index.mdx
+++ b/src/content/docs/containers/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: false
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/containers/platform-details/placement.mdx b/src/content/docs/containers/platform-details/placement.mdx
index bcb40145e1c38a1..67d5a76095272fe 100644
--- a/src/content/docs/containers/platform-details/placement.mdx
+++ b/src/content/docs/containers/platform-details/placement.mdx
@@ -34,10 +34,10 @@ Limited capacity regions (ME, OC, AFR) cannot be used exclusively. Include at le
 
 Use the `jurisdiction` constraint to restrict containers to compliance boundaries:
 
-| Jurisdiction | Regions    | Use case           |
-| ------------ | ---------- | ------------------ |
-| `eu`         | EEUR, WEUR | EU data residency  |
-| `fedramp`    | ENAM, WNAM | FedRAMP regions    |
+| Jurisdiction | Regions    | Use case          |
+| ------------ | ---------- | ----------------- |
+| `eu`         | EEUR, WEUR | EU data residency |
+| `fedramp`    | ENAM, WNAM | FedRAMP regions   |
 
 When you specify both `jurisdiction` and `regions`, the regions must be valid for that jurisdiction. For example, specifying `jurisdiction: "eu"` with `regions: ["ENAM"]` is invalid.
 
diff --git a/src/content/docs/containers/pricing.mdx b/src/content/docs/containers/pricing.mdx
index a26fc07ae355276..504db4e7c197e95 100644
--- a/src/content/docs/containers/pricing.mdx
+++ b/src/content/docs/containers/pricing.mdx
@@ -22,7 +22,7 @@ Containers are billed for every 10ms that they are actively running at the follo
 
 You only pay for what you use — charges start when a request is sent to the container or when it is manually started. Charges stop after the container instance goes to sleep, which can happen automatically after a timeout. This makes it easy to scale to zero, and allows you to get high utilization even with bursty traffic.
 
-Memory and disk usage are based on the *provisioned resources* for the instance type you select, while CPU usage is based on *active usage* only.
+Memory and disk usage are based on the _provisioned resources_ for the instance type you select, while CPU usage is based on _active usage_ only.
 
 #### Instance Types
 
diff --git a/src/content/docs/containers/ssh.mdx b/src/content/docs/containers/ssh.mdx
index fab40ae97a43594..bc91bd0cdc3968d 100644
--- a/src/content/docs/containers/ssh.mdx
+++ b/src/content/docs/containers/ssh.mdx
@@ -58,4 +58,4 @@ wrangler containers ssh <INSTANCE_ID>
 
 ## Process visibility
 
-Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
\ No newline at end of file
+Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
diff --git a/src/content/docs/d1/best-practices/local-development.mdx b/src/content/docs/d1/best-practices/local-development.mdx
index f6f28cdf1259255..a225fec2f2d3b74 100644
--- a/src/content/docs/d1/best-practices/local-development.mdx
+++ b/src/content/docs/d1/best-practices/local-development.mdx
@@ -137,8 +137,6 @@ Users of wrangler `2.x` must use the `--persist` flag: previous versions of wran
 
 You can use Miniflare's [support for D1](https://miniflare.dev/storage/d1) to create D1 databases you can use for testing:
 
-
-
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/d1/best-practices/query-d1.mdx b/src/content/docs/d1/best-practices/query-d1.mdx
index 74e5a405162b2c2..6f4eddbd73c830b 100644
--- a/src/content/docs/d1/best-practices/query-d1.mdx
+++ b/src/content/docs/d1/best-practices/query-d1.mdx
@@ -52,15 +52,16 @@ Given the following JSON object (`type:blob`) in a column named `sensor_reading`
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
+
 ```sql
 -- Extract the temperature value
 SELECT json_extract(sensor_reading, '$.measurement.temp_f')-- returns "77.4" as TEXT
@@ -80,22 +81,24 @@ This requires you to:
 
 ```js title="index.js"
 export default {
-    async fetch(request, env) {
-        const {pathname} = new URL(request.url);
-        const companyName1 = `Bs Beverages`;
-        const companyName2 = `Around the Horn`;
-        const stmt = env.DB.prepare(`SELECT * FROM Customers WHERE CompanyName = ?`);
-
-        if (pathname === `/RUN`) {
-            const returnValue = await stmt.bind(companyName1).run();
-            return Response.json(returnValue);
-        }
-
-        return new Response(
-            `Welcome to the D1 API Playground!
+	async fetch(request, env) {
+		const { pathname } = new URL(request.url);
+		const companyName1 = `Bs Beverages`;
+		const companyName2 = `Around the Horn`;
+		const stmt = env.DB.prepare(
+			`SELECT * FROM Customers WHERE CompanyName = ?`,
+		);
+
+		if (pathname === `/RUN`) {
+			const returnValue = await stmt.bind(companyName1).run();
+			return Response.json(returnValue);
+		}
+
+		return new Response(
+			`Welcome to the D1 API Playground!
 						\nChange the URL to test the various methods inside your index.js file.`,
-        );
-    },
+		);
+	},
 };
 ```
 
@@ -114,6 +117,7 @@ You can use Wrangler commands to query a D1 database. Note that Wrangler command
 ```sh
 npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ```
+
 ```sh output
 🌀 Mapping SQL input into an array of statements
 🌀 Executing on local database production-db-backend (<DATABASE_ID>) from .wrangler/state/v3/d1:
@@ -128,4 +132,4 @@ npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ├────────────┼─────────────────────┼───────────────────┤
 │ 13         │ Bs Beverages        │ Random Name       │
 └────────────┴─────────────────────┴───────────────────┘
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/d1/best-practices/remote-development.mdx b/src/content/docs/d1/best-practices/remote-development.mdx
index 40be666bf1fb1f5..4efe9586181686f 100644
--- a/src/content/docs/d1/best-practices/remote-development.mdx
+++ b/src/content/docs/d1/best-practices/remote-development.mdx
@@ -17,17 +17,16 @@ D1 supports remote development using the [dashboard playground](/workers/playgro
 
 :::note
 
-
 This guide assumes you have previously created a Worker, and a D1 database.
 
 Users new to D1 and/or Cloudflare Workers should read the [D1 tutorial](/d1/get-started/) to install `wrangler` and deploy their first database.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select an existing Worker.
 3. Go to the **Bindings** tab.
 4. Select **Add binding**.
@@ -44,14 +43,14 @@ Use the following Worker script to verify that the Worker has access to the boun
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    const res = await env.DB.prepare("SELECT 1;").run();
-    return new Response(JSON.stringify(res, null, 2));
-  },
+	async fetch(request, env, ctx) {
+		const res = await env.DB.prepare("SELECT 1;").run();
+		return new Response(JSON.stringify(res, null, 2));
+	},
 };
 ```
 
 ## Related resources
 
-* Learn [how to debug D1](/d1/observability/debug-d1/).
-* Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
+- Learn [how to debug D1](/d1/observability/debug-d1/).
+- Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
diff --git a/src/content/docs/d1/best-practices/retry-queries.mdx b/src/content/docs/d1/best-practices/retry-queries.mdx
index 02bc218ed30d67e..0dafe17addbbd3c 100644
--- a/src/content/docs/d1/best-practices/retry-queries.mdx
+++ b/src/content/docs/d1/best-practices/retry-queries.mdx
@@ -27,20 +27,20 @@ You can use libraries abstracting that already like [`@cloudflare/actors`](https
 import { tryWhile } from "@cloudflare/actors";
 
 function queryD1Example(d1: D1Database, sql: string) {
-  return await tryWhile(async () => {
-    return await d1.prepare(sql).run();
-  }, shouldRetry);
+	return await tryWhile(async () => {
+		return await d1.prepare(sql).run();
+	}, shouldRetry);
 }
 
 function shouldRetry(err: unknown, nextAttempt: number) {
-  const errMsg = String(err);
-  const isRetryableError =
-    errMsg.includes("Network connection lost") ||
-    errMsg.includes("storage caused object to be reset") ||
-    errMsg.includes("reset because its code was updated");
-  if (nextAttempt <= 5 && isRetryableError) {
-    return true;
-  }
-  return false;
+	const errMsg = String(err);
+	const isRetryableError =
+		errMsg.includes("Network connection lost") ||
+		errMsg.includes("storage caused object to be reset") ||
+		errMsg.includes("reset because its code was updated");
+	if (nextAttempt <= 5 && isRetryableError) {
+		return true;
+	}
+	return false;
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
index cf575cec298ffee..5ba46a35c327eba 100644
--- a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
+++ b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
@@ -7,5 +7,5 @@ sidebar:
   order: 11
 products:
   - d1
-  - pages  
+  - pages
 ---
diff --git a/src/content/docs/d1/best-practices/use-indexes.mdx b/src/content/docs/d1/best-practices/use-indexes.mdx
index dc25d04079a3170..b363212f5718cc1 100644
--- a/src/content/docs/d1/best-practices/use-indexes.mdx
+++ b/src/content/docs/d1/best-practices/use-indexes.mdx
@@ -16,9 +16,9 @@ Indexes enable D1 to improve query performance over the indexed columns for comm
 
 Indexes are useful:
 
-* When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
-* For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
-* In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
+- When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
+- For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
+- In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
 
 Indexes are automatically updated when the table and column(s) they reference are inserted, updated or deleted. You do not need to manually update an index after you write to the table it references.
 
@@ -114,7 +114,7 @@ Using an index can reduce the number of rows read by a query. Use the `meta` obj
 
 ## Multi-column indexes
 
-For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either *all* of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
+For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either _all_ of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
 
 Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions(customer_id, transaction_date)`, the following table shows when the index is used (or not):
 
@@ -126,16 +126,16 @@ Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions
 
 Notes:
 
-* If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
-* With the same index, a query that uses only `transaction_date` and `shipping_status` would *not* use the index, as you have not used `customer_id` (the leftmost column) in the query.
+- If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
+- With the same index, a query that uses only `transaction_date` and `shipping_status` would _not_ use the index, as you have not used `customer_id` (the leftmost column) in the query.
 
 ## Partial indexes
 
 Partial indexes are indexes over a subset of rows in a table. Partial indexes are defined by the use of a `WHERE` clause when creating the index. A partial index can be useful to omit certain rows, such as those where values are `NULL` or where rows with a specific value are present across queries.
 
-* A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
-* This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
-* Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
+- A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
+- This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
+- Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
 
 A partial index that filters out completed orders from the index would resemble the following:
 
@@ -153,7 +153,7 @@ Use `DROP INDEX` to remove an index. Dropped indexes cannot be restored.
 
 Take note of the following considerations when creating indexes:
 
-* Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
-* You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
-* Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
-* Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
+- Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
+- You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
+- Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
+- Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
diff --git a/src/content/docs/d1/configuration/environments.mdx b/src/content/docs/d1/configuration/environments.mdx
index d006e54c8c8878d..9211ae269c77fa0 100644
--- a/src/content/docs/d1/configuration/environments.mdx
+++ b/src/content/docs/d1/configuration/environments.mdx
@@ -78,22 +78,20 @@ Therefore, the above binding is equivalent to:
 
 ```json
 {
-  "production": {
-    "d1_databases": [
-      {
-        "binding": "DB",
-        "database_name": "DATABASE_NAME",
-        "database_id": "DATABASE_ID"
-      }
-    ]
-  }
+	"production": {
+		"d1_databases": [
+			{
+				"binding": "DB",
+				"database_name": "DATABASE_NAME",
+				"database_id": "DATABASE_ID"
+			}
+		]
+	}
 }
 ```
 
 ### Example
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -127,25 +125,25 @@ The above is equivalent to the following structure in JSON:
 
 ```json
 {
-  "env": {
-    "production": {
-      "d1_databases": [
-        {
-          "binding": "BINDING_NAME_2",
-          "database_id": "UUID_2",
-          "database_name": "DATABASE_NAME_2"
-        }
-      ]
-    },
-    "staging": {
-      "d1_databases": [
-        {
-          "binding": "BINDING_NAME_1",
-          "database_id": "UUID_1",
-          "database_name": "DATABASE_NAME_1"
-        }
-      ]
-    }
-  }
+	"env": {
+		"production": {
+			"d1_databases": [
+				{
+					"binding": "BINDING_NAME_2",
+					"database_id": "UUID_2",
+					"database_name": "DATABASE_NAME_2"
+				}
+			]
+		},
+		"staging": {
+			"d1_databases": [
+				{
+					"binding": "BINDING_NAME_1",
+					"database_id": "UUID_1",
+					"database_name": "DATABASE_NAME_1"
+				}
+			]
+		}
+	}
 }
 ```
diff --git a/src/content/docs/d1/get-started.mdx b/src/content/docs/d1/get-started.mdx
index c5ee956264ad848..5d22a0fe3363f7c 100644
--- a/src/content/docs/d1/get-started.mdx
+++ b/src/content/docs/d1/get-started.mdx
@@ -9,7 +9,17 @@ products:
   - d1
 ---
 
-import { Render, PackageManagers, Steps, FileTree, Tabs, TabItem, TypeScriptExample, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	FileTree,
+	Tabs,
+	TabItem,
+	TypeScriptExample,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 This guide instructs you through:
 
diff --git a/src/content/docs/d1/observability/billing.mdx b/src/content/docs/d1/observability/billing.mdx
index 31ef2103ba9196a..1a4a8d3fffc9712 100644
--- a/src/content/docs/d1/observability/billing.mdx
+++ b/src/content/docs/d1/observability/billing.mdx
@@ -21,6 +21,7 @@ Total account billable usage analytics for D1 are available in the Cloudflare da
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
    <DashButton url="/?to=/:account/billing" />
+
 2. Go to **Billable Usage**.
 
 From here you can view charts of your account's D1 usage on a daily or month-to-date timeframe.
@@ -32,5 +33,6 @@ Note that billable usage history is stored for a maximum of 30 days.
 Usage-based billing notifications are available within the [Cloudflare dashboard](https://dash.cloudflare.com) for users looking to monitor their total account usage.
 
 Notifications on the following metrics are available:
+
 - Rows Read
-- Rows Written
\ No newline at end of file
+- Rows Written
diff --git a/src/content/docs/d1/platform/limits.mdx b/src/content/docs/d1/platform/limits.mdx
index 4c61da8679fd68e..21cb95db52dfab3 100644
--- a/src/content/docs/d1/platform/limits.mdx
+++ b/src/content/docs/d1/platform/limits.mdx
@@ -10,24 +10,24 @@ products:
 
 import { Render } from "~/components";
 
-| Feature                                                                                                             | Limit                                             |
-| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| Databases per account                                                                                               | 50,000 (Workers Paid) [^1] / 10 (Free)            |
-| Maximum database size                                                                                               | 10 GB (Workers Paid) / 500 MB (Free)              |
-| Maximum storage per account                                                                                         | 1 TB (Workers Paid) [^2] / 5 GB (Free)             |
-| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                                         | 30 days (Workers Paid) / 7 days (Free)            |
-| Maximum Time Travel restore operations                                                                              | 10 restores per 10 minutes (per database)          |
+| Feature                                                                                         | Limit                                             |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| Databases per account                                                                           | 50,000 (Workers Paid) [^1] / 10 (Free)            |
+| Maximum database size                                                                           | 10 GB (Workers Paid) / 500 MB (Free)              |
+| Maximum storage per account                                                                     | 1 TB (Workers Paid) [^2] / 5 GB (Free)            |
+| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                     | 30 days (Workers Paid) / 7 days (Free)            |
+| Maximum Time Travel restore operations                                                          | 10 restores per 10 minutes (per database)         |
 | Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#subrequests)) | 1000 (Workers Paid) / 50 (Free)                   |
-| Maximum number of columns per table                                                                                 | 100                                               |
-| Maximum number of rows per table                                                                                    | Unlimited (excluding per-database storage limits) |
-| Maximum string, `BLOB` or table row size                                                                            | 2,000,000 bytes (2 MB)                            |
-| Maximum SQL statement length                                                                                        | 100,000 bytes (100 KB)                            |
-| Maximum bound parameters per query                                                                                  | 100                                               |
-| Maximum arguments per SQL function                                                                                  | 32                                                |
-| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                                            | 50 bytes                                          |
-| Maximum bindings per Workers script                                                                                 | Approximately 5,000 [^3]                          |
-| Maximum SQL query duration                                                                                          | 30 seconds [^4]                                   |
-| Maximum file import (`d1 execute`) size                                                                             | 5 GB [^5]                                         |
+| Maximum number of columns per table                                                             | 100                                               |
+| Maximum number of rows per table                                                                | Unlimited (excluding per-database storage limits) |
+| Maximum string, `BLOB` or table row size                                                        | 2,000,000 bytes (2 MB)                            |
+| Maximum SQL statement length                                                                    | 100,000 bytes (100 KB)                            |
+| Maximum bound parameters per query                                                              | 100                                               |
+| Maximum arguments per SQL function                                                              | 32                                                |
+| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                        | 50 bytes                                          |
+| Maximum bindings per Workers script                                                             | Approximately 5,000 [^3]                          |
+| Maximum SQL query duration                                                                      | 30 seconds [^4]                                   |
+| Maximum file import (`d1 execute`) size                                                         | 5 GB [^5]                                         |
 
 :::note[Batch limits]
 Limits for individual queries (listed above) apply to each individual statement contained within a batch statement. For example, the maximum SQL statement length of 100 KB applies to each statement inside a `db.batch()`.
diff --git a/src/content/docs/d1/reference/community-projects.mdx b/src/content/docs/d1/reference/community-projects.mdx
index a095bb554ffe1f5..2974e7452d65edb 100644
--- a/src/content/docs/d1/reference/community-projects.mdx
+++ b/src/content/docs/d1/reference/community-projects.mdx
@@ -12,10 +12,8 @@ Members of the Cloudflare developer community and broader developer ecosystem ha
 
 :::note
 
-
 Community projects are not maintained by the Cloudflare D1 team. They are managed and updated by the project authors.
 
-
 :::
 
 ## Projects
@@ -37,57 +35,57 @@ knex-cloudflare-d1 is the Cloudflare D1 dialect for Knex.js. Note that this is n
 
 [Prisma ORM](https://www.prisma.io/orm) is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to its intuitive data model, automated migrations, type-safety and auto-completion.
 
-* [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
-* [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
+- [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
+- [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
 
 ### D1 adapter for Kysely ORM
 
 Kysely is a type-safe and autocompletion-friendly typescript SQL query builder. With this adapter you can interact with D1 with the familiar Kysely interface.
 
-* [Kysely GitHub](https://github.com/koskimas/kysely)
-* [D1 adapter](https://github.com/aidenwallis/kysely-d1)
+- [Kysely GitHub](https://github.com/koskimas/kysely)
+- [D1 adapter](https://github.com/aidenwallis/kysely-d1)
 
 ### feathers-kysely
 
 The `feathers-kysely` database adapter follows the FeathersJS Query Syntax standard and works with any framework. It is built on the D1 adapter for Kysely and supports passing queries directly from client applications. Since the FeathersJS query syntax is a subset of MongoDB's syntax, this is a great tool for MongoDB users to use Cloudflare D1 without previous SQL experience.
 
-* [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
-* [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
+- [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
+- [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
 
 ### Drizzle ORM
 
 Drizzle is a headless TypeScript ORM with a head which runs on Node, Bun and Deno. Drizzle ORM lives on the Edge and it is a JavaScript ORM too. It comes with a drizzle-kit CLI companion for automatic SQL migrations generation. Drizzle automatically generates your D1 schema based on types you define in TypeScript, and exposes an API that allows you to query your database directly.
 
-* [Docs](https://orm.drizzle.team/docs)
-* [GitHub](https://github.com/drizzle-team/drizzle-orm)
-* [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
+- [Docs](https://orm.drizzle.team/docs)
+- [GitHub](https://github.com/drizzle-team/drizzle-orm)
+- [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
 
 ### workers-qb
 
 `workers-qb` is a zero-dependency query builder that provides a simple standardized interface while keeping the benefits and speed of using raw queries over a traditional ORM. While not intended to provide ORM-like functionality, `workers-qb` makes it easier to interact with your database from code for direct SQL access.
 
-* [GitHub](https://github.com/G4brym/workers-qb)
-* [Documentation](https://workers-qb.massadas.com/)
+- [GitHub](https://github.com/G4brym/workers-qb)
+- [Documentation](https://workers-qb.massadas.com/)
 
 ### d1-console
 
 Instead of running the `wrangler d1 execute` command in your terminal every time you want to interact with your database, you can interact with D1 from within the `d1-console`. Created by a Discord Community Champion, this gives the benefit of executing multi-line queries, obtaining command history, and viewing a cleanly formatted table output.
 
-* [GitHub](https://github.com/isaac-mcfadyen/d1-console)
+- [GitHub](https://github.com/isaac-mcfadyen/d1-console)
 
 ### L1
 
 `L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
 
-* [GitHub](https://github.com/renoki-co/l1)
-* [Packagist](https://packagist.org/packages/renoki-co/l1)
+- [GitHub](https://github.com/renoki-co/l1)
+- [Packagist](https://packagist.org/packages/renoki-co/l1)
 
 ### Staff Directory - a D1-based demo
 
 Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/honox), and [Cloudflare Pages](/pages/). It uses D1 to store employee data, and is an example of a full-stack application built on top of D1.
 
-* [GitHub](https://github.com/lauragift21/staff-directory)
-* [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
+- [GitHub](https://github.com/lauragift21/staff-directory)
+- [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
 
 ### NuxtHub
 
@@ -95,9 +93,9 @@ Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/ho
 
 `NuxtHub` also provides a way to use your remote D1 database in development using the `npx nuxt dev --remote` command.
 
-* [GitHub](https://github.com/nuxt-hub/core)
-* [Documentation](https://hub.nuxt.com)
-* [Example](https://github.com/Atinux/nuxt-todos-edge)
+- [GitHub](https://github.com/nuxt-hub/core)
+- [Documentation](https://hub.nuxt.com)
+- [Example](https://github.com/Atinux/nuxt-todos-edge)
 
 ## Feedback
 
diff --git a/src/content/docs/d1/reference/data-security.mdx b/src/content/docs/d1/reference/data-security.mdx
index 810de22ec7f45ea..ab79357a7114750 100644
--- a/src/content/docs/d1/reference/data-security.mdx
+++ b/src/content/docs/d1/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of D1, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/d1/reference/faq.mdx b/src/content/docs/d1/reference/faq.mdx
index 112c665dd4004ad..e86017db8b829fa 100644
--- a/src/content/docs/d1/reference/faq.mdx
+++ b/src/content/docs/d1/reference/faq.mdx
@@ -12,8 +12,8 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="faq-pricing" product="d1"/>
+<Render file="faq-pricing" product="d1" />
 
 ## Limits
 
-<Render file="faq-limits" product="d1"/>
\ No newline at end of file
+<Render file="faq-limits" product="d1" />
diff --git a/src/content/docs/d1/reference/generated-columns.mdx b/src/content/docs/d1/reference/generated-columns.mdx
index 5d116b3321076a7..ccadcdb1b12d227 100644
--- a/src/content/docs/d1/reference/generated-columns.mdx
+++ b/src/content/docs/d1/reference/generated-columns.mdx
@@ -18,8 +18,8 @@ Generated columns can also have [indexes defined](/d1/best-practices/use-indexes
 
 There are two types of generated columns:
 
-* `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
-* `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
+- `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
+- `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
 
 When omitted from a generated column expression, generated columns default to the `VIRTUAL` type. The `STORED` type is recommended when the generated column is compute intensive. For example, when parsing large JSON structures.
 
@@ -40,13 +40,13 @@ As a concrete example, to automatically extract the `location` value from the fo
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
 
@@ -100,6 +100,6 @@ ADD COLUMN expires_at AS (date(timestamp, '+30 days'));
 
 ## Additional considerations
 
-* Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
-* Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
-* Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
+- Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
+- Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
+- Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
diff --git a/src/content/docs/d1/reference/glossary.mdx b/src/content/docs/d1/reference/glossary.mdx
index 5fe0afff9a376e2..87e1a98504fae41 100644
--- a/src/content/docs/d1/reference/glossary.mdx
+++ b/src/content/docs/d1/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - d1
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's D1 documentation.
 
diff --git a/src/content/docs/d1/reference/migrations.mdx b/src/content/docs/d1/reference/migrations.mdx
index 50d3292c20ea584..20dc9869915cbc2 100644
--- a/src/content/docs/d1/reference/migrations.mdx
+++ b/src/content/docs/d1/reference/migrations.mdx
@@ -16,9 +16,9 @@ Database migrations are a way of versioning your database. Each migration is sto
 
 Currently, the migrations system aims to be simple yet effective. With the current implementation, you can:
 
-* [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
-* [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
-* [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
+- [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
+- [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
+- [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
 
 Every migration file in the `migrations` folder has a specified version number in the filename. Files are listed in sequential order. Every migration file is an SQL file where you can specify queries to be run.
 
diff --git a/src/content/docs/d1/sql-api/foreign-keys.mdx b/src/content/docs/d1/sql-api/foreign-keys.mdx
index 1c38b8d8d995ec3..fdc9e715186ae46 100644
--- a/src/content/docs/d1/sql-api/foreign-keys.mdx
+++ b/src/content/docs/d1/sql-api/foreign-keys.mdx
@@ -47,13 +47,13 @@ A foreign key relationship can be defined when creating a table via `CREATE TABL
 
 To illustrate this with an example based on an e-commerce website with two tables:
 
-* A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
-* An `orders` table that maps an order back to a `user_id` in the user table.
+- A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
+- An `orders` table that maps an order back to a `user_id` in the user table.
 
 This mapping is defined as `FOREIGN KEY`, which ensures that:
 
-* You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
-* `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
+- You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
+- `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
 
 ```sql
 CREATE TABLE users (
@@ -77,22 +77,22 @@ You can define multiple foreign key relationships per-table, and foreign key def
 
 ## Foreign key actions
 
-You can define *actions* as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining *actions* makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
+You can define _actions_ as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining _actions_ makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
 
 There are five actions you can set when defining the `ON UPDATE` and/or `ON DELETE` clauses as part of a foreign key relationship. You can also define different actions for `ON UPDATE` and `ON DELETE` depending on your requirements.
 
-* `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
-* `RESTRICT` - A parent key cannot be updated or deleted when *any* child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
-* `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
-* `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
-* `NO ACTION` - Take no action.
+- `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
+- `RESTRICT` - A parent key cannot be updated or deleted when _any_ child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
+- `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
+- `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
+- `NO ACTION` - Take no action.
 
 :::caution[CASCADE usage]
 
 Although `CASCADE` can be the desired behavior in some cases, deleting child rows across tables can have undesirable effects and/or result in unintended side effects for your users.
 :::
 
-In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that *other* users can no longer look up or refer to scores that were still valid.
+In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that _other_ users can no longer look up or refer to scores that were still valid.
 
 ```sql
 CREATE TABLE users (
@@ -111,6 +111,6 @@ CREATE TABLE scores (
 
 ## Next Steps
 
-* Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
-* Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
-* Understand how [database migrations work](/d1/reference/migrations/) with D1.
+- Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
+- Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
+- Understand how [database migrations work](/d1/reference/migrations/) with D1.
diff --git a/src/content/docs/d1/sql-api/query-json.mdx b/src/content/docs/d1/sql-api/query-json.mdx
index 9b44068ab62c958..82c65b749bd3e7f 100644
--- a/src/content/docs/d1/sql-api/query-json.mdx
+++ b/src/content/docs/d1/sql-api/query-json.mdx
@@ -12,10 +12,10 @@ products:
 
 D1 has built-in support for querying and parsing JSON data stored within a database. This enables you to:
 
-* [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
-* Insert and/or replace values within an object or array.
-* [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
-* Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
+- [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
+- Insert and/or replace values within an object or array.
+- [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
+- Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
 
 One of the biggest benefits to parsing JSON within D1 directly is that it can directly reduce the number of round-trips (queries) to your database. It reduces the cases where you have to read a JSON object into your application (1), parse it, and then write it back (2).
 
@@ -25,18 +25,18 @@ This allows you to more precisely query over data and reduce the result set your
 
 JSON data is stored as a `TEXT` column in D1. JSON types follow the same [type conversion rules](/d1/worker-api/#type-conversion) as D1 in general, including:
 
-* A JSON null is treated as a D1 `NULL`.
-* A JSON number is treated as an `INTEGER` or `REAL`.
-* Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
-* Object and array values as `TEXT`.
+- A JSON null is treated as a D1 `NULL`.
+- A JSON number is treated as an `INTEGER` or `REAL`.
+- Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
+- Object and array values as `TEXT`.
 
 ## Supported functions
 
 The following table outlines the JSON functions built into D1 and example usage.
 
-* The `json` argument placeholder can be a JSON object, array, string, number or a null value.
-* The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
-* The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
+- The `json` argument placeholder can be a JSON object, array, string, number or a null value.
+- The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
+- The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
 
 | Function                                                    | Description                                                                                                                                                    | Example                                                                                   |
 | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
@@ -53,7 +53,7 @@ The following table outlines the JSON functions built into D1 and example usage.
 | `json_replace(json, path, value)`                           | Insert a value at the given path. Overwrites an existing value, but does not create a new key if it doesn't exist.                                             |                                                                                           |
 | `json_set(json, path, value)`                               | Insert a value at the given path. Overwrites an existing value.                                                                                                |                                                                                           |
 | `json_type(json)` - `json_type(json, path)`                 | Return the type of the provided value or value at the specified path. Returns one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`. | `json_type('{"temperatures":[73.6, 77.8, 80.2]}', '$.temperatures')` returns `array`      |
-| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                  |
+| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                   |
 | `json_quote(value)`                                         | Converts the provided SQL value into its JSON representation.                                                                                                  | `json_quote('[1, 2, 3]')` returns `[1,2,3]`                                               |
 | `json_group_array(value)`                                   | Returns the provided value(s) as a JSON array.                                                                                                                 |                                                                                           |
 | `json_each(value)` - `json_each(value, path)`               | Returns each element within the object as an individual row. It will only traverse the top-level object.                                                       |                                                                                           |
@@ -102,9 +102,9 @@ Refer to [Generated columns](/d1/reference/generated-columns/) to learn more abo
 
 There are three ways to extract a value from a JSON object in D1:
 
-* The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
-* The `->` operator, which returns a JSON representation of the value.
-* The `->>` operator, which returns an SQL representation of the value.
+- The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
+- The `->` operator, which returns a JSON representation of the value.
+- The `->>` operator, which returns an SQL representation of the value.
 
 The `->` and `->>` operators functions both operate similarly to the same operators in PostgreSQL and MySQL/MariaDB.
 
@@ -112,13 +112,13 @@ Given the following JSON object in a column named `sensor_reading`, you can extr
 
 ```json
 {
-    "measurement": {
-        "temp_f": "77.4",
-        "aqi": [21, 42, 58],
-        "o3": [18, 500],
-        "wind_mph": "13",
-        "location": "US-NY"
-    }
+	"measurement": {
+		"temp_f": "77.4",
+		"aqi": [21, 42, 58],
+		"o3": [18, 500],
+		"wind_mph": "13",
+		"location": "US-NY"
+	}
 }
 ```
 
@@ -148,8 +148,12 @@ For example, given the following JSON object stored in a column called `login_hi
 
 ```json
 {
-    "user_id": "abc12345",
-    "previous_logins": ["2023-03-31T21:07:14-05:00", "2023-03-28T08:21:02-05:00", "2023-03-28T05:52:11-05:00"]
+	"user_id": "abc12345",
+	"previous_logins": [
+		"2023-03-31T21:07:14-05:00",
+		"2023-03-28T08:21:02-05:00",
+		"2023-03-28T05:52:11-05:00"
+	]
 }
 ```
 
@@ -164,7 +168,13 @@ You can also use `json_array_length` as a predicate in a more complex query - fo
 You can insert a value into an existing JSON object or array using `json_insert()`. For example, if you have a `TEXT` column called `login_history` in a `users` table containing the following object:
 
 ```json
-{"history": ["2023-05-13T15:13:02+00:00", "2023-05-14T07:11:22+00:00", "2023-05-15T15:03:51+00:00"]}
+{
+	"history": [
+		"2023-05-13T15:13:02+00:00",
+		"2023-05-14T07:11:22+00:00",
+		"2023-05-15T15:03:51+00:00"
+	]
+}
 ```
 
 To add a new timestamp to the `history` array within our `login_history` column, write a query resembling the following:
@@ -197,11 +207,11 @@ This would extract only the `value` column from the table returned by `json_each
 
 `json_each` effectively returns a table with multiple columns, with the most relevant being:
 
-* `key` - the key (or index).
-* `value` - the literal value of each element parsed by `json_each`.
-* `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
-* `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
-* `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
+- `key` - the key (or index).
+- `value` - the literal value of each element parsed by `json_each`.
+- `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
+- `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
+- `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
 
 In this example, `SELECT * FROM json_each('[183183, 13913, 94944]')` would return a table resembling the below:
 
@@ -215,12 +225,12 @@ key|value|type|id|fullkey|path
 You can use `json_each` with [D1 Workers Binding API](/d1/worker-api/) in a Worker by creating a statement and using `JSON.stringify` to pass an array as a [bound parameter](/d1/worker-api/d1-database/#guidance):
 
 ```ts
-const stmt = context.env.DB
-    .prepare("UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))")
-const resp = await stmt.bind(
-    "2023-05-16T11:24:08+00:00",
-    JSON.stringify([183183, 13913, 94944])
-    ).run()
+const stmt = context.env.DB.prepare(
+	"UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))",
+);
+const resp = await stmt
+	.bind("2023-05-16T11:24:08+00:00", JSON.stringify([183183, 13913, 94944]))
+	.run();
 ```
 
 This would only update rows in your `users` table where the `id` matches one of the three provided.
diff --git a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
index 986d25d5413005e..2a203c8cb9975a9 100644
--- a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
+++ b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
@@ -12,7 +12,13 @@ description: >-
   This tutorial shows how to create an API that allows you to securely run queries against a D1 database. The API can be used to customize access controls and/or limit what tables can be queried.
 ---
 
-import { Render, PackageManagers, Steps, Details, WranglerConfig } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	Details,
+	WranglerConfig,
+} from "~/components";
 
 In this tutorial, you will learn how to create an API that allows you to securely run queries against a D1 database.
 
diff --git a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
index 3ae7982d8bf2cca..64bb7a1593def46 100644
--- a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
+++ b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
@@ -230,7 +230,7 @@ npx prisma migrate diff --from-empty --to-schema-datamodel ./prisma/schema.prism
 
 </TabItem>
 </Tabs>
- 
+
 This stores a SQL statement to create a new `User` table in your migration file from before, here is what it looks like:
 
 <GitHubCode
diff --git a/src/content/docs/data-localization/compatibility.mdx b/src/content/docs/data-localization/compatibility.mdx
index 472524c6f61c822..724dbfd2c9587c6 100644
--- a/src/content/docs/data-localization/compatibility.mdx
+++ b/src/content/docs/data-localization/compatibility.mdx
@@ -29,19 +29,19 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                                    | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------ | --------------- | ----------------- | -------------------------- |
 | Caching/CDN                                | ✅              | ✅                | ✅                         |
-| Cache Reserve                              | ⚫️             | 🚧                | ✅ [^29]                   |
-| DNS                                        | ⚫️             | 🚧 [^33]          | ✅                         |
-| HTTP/3 (with QUIC)                         | ⚫️             | ✘                 | ⚫️                        |
+| Cache Reserve                              | ⚫️              | 🚧                | ✅ [^29]                   |
+| DNS                                        | ⚫️              | 🚧 [^33]          | ✅                         |
+| HTTP/3 (with QUIC)                         | ⚫️              | ✘                 | ⚫️                         |
 | Image Resizing                             | ✅              | ✅ [^6]           | 🚧 [^1]                    |
 | Load Balancing                             | ✅              | ✅                | 🚧 [^1]                    |
-| Network Error Logging (NEL)                | ⚫️             | ⚫️               | ✘                          |
+| Network Error Logging (NEL)                | ⚫️              | ⚫️                | ✘                          |
 | Onion Routing                              | ✘               | ✘                 | ✘                          |
 | O2O                                        | ✘               | ✘                 | ✘                          |
 | Stream Delivery                            | ✅              | ✅                | ✅                         |
 | Tiered Caching                             | ✅              | 🚧 [^2]           | 🚧 [^30]                   |
 | Trace                                      | ✘               | ✘                 | ✘                          |
-| Waiting Room                               | ⚫️             | ✅                | ✅                         |
-| Web Analytics / Real User Monitoring (RUM) | ⚫️             | ⚫️               | ✘ [^43]                    |
+| Waiting Room                               | ⚫️              | ✅                | ✅                         |
+| Web Analytics / Real User Monitoring (RUM) | ⚫️              | ⚫️                | ✘ [^43]                    |
 | Zaraz                                      | ✅              | ✅                | ✅                         |
 
 ---
@@ -50,18 +50,18 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------- | --------------- | ----------------- | -------------------------- |
-| Advanced Certificate Manager                | ⚫️             | ⚫️               | ⚫️                        |
+| Advanced Certificate Manager                | ⚫️              | ⚫️                | ⚫️                         |
 | Advanced DDoS Protection                    | ✅              | ✅                | 🚧 [^3]                    |
 | API Shield                                  | ✅              | ✅                | 🚧 [^4]                    |
 | Bot Management                              | ✅              | ✅                | ✅                         |
 | Client-side security (formerly Page Shield) | ✅              | ✅                | ✅                         |
-| DNS Firewall                                | ⚫️             | ⚫️               | ✅                         |
+| DNS Firewall                                | ⚫️              | ⚫️                | ✅                         |
 | Rate Limiting                               | ✅              | ✅                | ✅ [^37]                   |
 | SSL                                         | ✅              | ✅                | ✅                         |
 | Cloudflare for SaaS                         | ✘               | ✅                | ✅                         |
-| Turnstile                                   | ⚫️             | ✘                 | ✅ [^38]                   |
+| Turnstile                                   | ⚫️              | ✘                 | ✅ [^38]                   |
 | WAF/L7 Firewall                             | ✅              | ✅                | ✅                         |
-| DMARC Management                            | ⚫️             | ⚫️               | ✅                         |
+| DMARC Management                            | ⚫️              | ⚫️                | ✅                         |
 
 ---
 
@@ -69,24 +69,24 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                        | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------ | --------------- | ----------------- | -------------------------- |
-| Cloudflare Images              | ⚫️             | ✅ [^36]          | 🚧 [^35]                   |
+| Cloudflare Images              | ⚫️              | ✅ [^36]          | 🚧 [^35]                   |
 | AI Gateway                     | ✘               | ✘                 | 🚧 [^39]                   |
 | AI Search                      | ✘ [^46]         | ✘ [^47]           | 🚧 [^48]                   |
 | AI Security for Apps           | ✘               | ✘                 | ✘                          |
 | Cloudflare Pages               | ✅ [^11]        | ✅ [^11]          | 🚧 [^1]                    |
-| Cloudflare D1                  | ⚫️             | ⚫️               | 🚧 [^40]                   |
-| Durable Objects                | ⚫️             | ✅ [^7]           | 🚧 [^1]                    |
-| Email Routing                  | ⚫️             | ⚫️               | ✅                         |
+| Cloudflare D1                  | ⚫️              | ⚫️                | 🚧 [^40]                   |
+| Durable Objects                | ⚫️              | ✅ [^7]           | 🚧 [^1]                    |
+| Email Routing                  | ⚫️              | ⚫️                | ✅                         |
 | Remote MCP Server              | ✅ [^44]        | ✅ [^45]          | 🚧 [^1]                    |
 | R2                             | ✅ [^27]        | ✅ [^8]           | ✅ [^28]                   |
-| Smart Placement                | ⚫️             | ✘                 | ✘                          |
-| Stream                         | ⚫️             | ✘                 | 🚧 [^1]                    |
-| Vectorize                      | ⚫️             | ✘                 | ✘                          |
+| Smart Placement                | ⚫️              | ✘                 | ✘                          |
+| Stream                         | ⚫️              | ✘                 | 🚧 [^1]                    |
+| Vectorize                      | ⚫️              | ✘                 | ✘                          |
 | Workers (deployed on a Zone)   | ✅              | ✅                | 🚧 [^41]                   |
-| Workers AI                     | ⚫️             | ✘                 | ✅                         |
-| Workers KV                     | ⚫️             | ✘                 | ✅ [^34]                   |
+| Workers AI                     | ⚫️              | ✘                 | ✅                         |
+| Workers KV                     | ⚫️              | ✘                 | ✅ [^34]                   |
 | Workers.dev                    | ✘               | ✘                 | ✘                          |
-| Workers Analytics Engine (WAE) | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Workers Analytics Engine (WAE) | ⚫️              | ⚫️                | 🚧 [^1]                    |
 
 ---
 
@@ -95,11 +95,11 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------------- | --------------- | ----------------- | -------------------------- |
 | Argo Smart Routing          | ✅              | ✘ [^9]            | ✘ [^10]                    |
-| Static IP/BYOIP             | ⚫️             | ✅ [^26]          | ⚫️                        |
-| Cloudflare Network Firewall | ⚫️             | ⚫️               | ✅                         |
-| Network Flow                | ⚫️             | ⚫️               | 🚧 [^1]                    |
-| Magic Transit               | ⚫️             | ⚫️               | ✅ [^3]                    |
-| Cloudflare WAN              | ⚫️             | ⚫️               | ✅                         |
+| Static IP/BYOIP             | ⚫️              | ✅ [^26]          | ⚫️                         |
+| Cloudflare Network Firewall | ⚫️              | ⚫️                | ✅                         |
+| Network Flow                | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Magic Transit               | ⚫️              | ⚫️                | ✅ [^3]                    |
+| Cloudflare WAN              | ⚫️              | ⚫️                | ✅                         |
 | Spectrum                    | ✅              | ✅ [^42]          | ✅                         |
 
 ---
@@ -108,9 +108,9 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product      | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------ | --------------- | ----------------- | -------------------------- |
-| Logpull      | ⚫️             | ⚫️               | 🚧 [^12]                   |
-| Logpush      | ⚫️             | ✅                | 🚧 [^13]                   |
-| Log Explorer | ⚫️             | ⚫️               | ✘ [^23]                    |
+| Logpull      | ⚫️              | ⚫️                | 🚧 [^12]                   |
+| Logpush      | ⚫️              | ✅                | 🚧 [^13]                   |
+| Log Explorer | ⚫️              | ⚫️                | ✘ [^23]                    |
 
 ---
 
@@ -119,13 +119,13 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product               | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------- | --------------- | ----------------- | -------------------------- |
 | Access                | 🚧 [^14]        | 🚧 [^15]          | ✅ [^16]                   |
-| Browser Isolation     | ⚫️             | 🚧 [^17]          | ✅                         |
-| CASB                  | ⚫️             | ⚫️               | ✘                          |
-| Cloudflare Tunnel     | ⚫️             | 🚧 [^18]          | ⚫️                        |
-| Digital Experience    | ⚫️             | ⚫️               | 🚧 [^49]                   |
-| DLP                   | ⚫️ [^19]       | ⚫️ [^19]         | 🚧 [^31]                   |
+| Browser Isolation     | ⚫️              | 🚧 [^17]          | ✅                         |
+| CASB                  | ⚫️              | ⚫️                | ✘                          |
+| Cloudflare Tunnel     | ⚫️              | 🚧 [^18]          | ⚫️                         |
+| Digital Experience    | ⚫️              | ⚫️                | 🚧 [^49]                   |
+| DLP                   | ⚫️ [^19]        | ⚫️ [^19]          | 🚧 [^31]                   |
 | Gateway               | 🚧 [^20]        | 🚧 [^21]          | 🚧 [^22]                   |
-| Cloudflare One Client | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Cloudflare One Client | ⚫️              | ⚫️                | 🚧 [^1]                    |
 
 [^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
 
diff --git a/src/content/docs/data-localization/geo-key-manager.mdx b/src/content/docs/data-localization/geo-key-manager.mdx
index 6bafbbf4ad50e68..510eb40b49191a5 100644
--- a/src/content/docs/data-localization/geo-key-manager.mdx
+++ b/src/content/docs/data-localization/geo-key-manager.mdx
@@ -9,7 +9,6 @@ tags:
   - Compliance
 sidebar:
   order: 4
-
 ---
 
 Geo Key Manager offers enhanced control over the storage location of your private SSL/TLS keys — the cryptographic keys that Cloudflare uses to decrypt your HTTPS traffic. By restricting where these keys are stored, you can ensure compliance with regional data regulations and security requirements.
@@ -24,7 +23,7 @@ Geo Key Manager was restricted to the US, EU, and high-security data centers, bu
 
 The following diagram shows what happens when an end user connects to a Cloudflare data center that does not hold your private key. Because TLS termination requires the private key, the local data center must request a temporary session key (a short-lived symmetric encryption key) from a data center in an authorized region. Once the session key is established, the local data center can decrypt traffic for the remainder of the connection without contacting the key-holding data center again. This extra step adds latency on the first request, which can be as much as a second if the key-holding data center is geographically distant.
 
-<br/>
+<br />
 
 ```mermaid
 sequenceDiagram
@@ -41,6 +40,6 @@ sequenceDiagram
     User-->>CloudflarePoP: Subsequent requests use the Session Key
 ```
 
-<br/>
+<br />
 
 For detailed information on setup and supported options, refer to [Geo Key Manager documentation](/ssl/edge-certificates/geokey-manager/).
diff --git a/src/content/docs/ddos-protection/about/components.mdx b/src/content/docs/ddos-protection/about/components.mdx
index fdad5713c8a928e..9161b6dd7d87b5a 100644
--- a/src/content/docs/ddos-protection/about/components.mdx
+++ b/src/content/docs/ddos-protection/about/components.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 ![Diagram with the main components providing protection against DDoS attacks at Cloudflare](~/assets/images/ddos-protection/ddos-diagram.png)
 
diff --git a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
index 2be132500131a7d..921203e498c7fda 100644
--- a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
+++ b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
@@ -9,10 +9,9 @@ sidebar:
 learning_center:
   title: What is a DDoS attack?
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To detect and mitigate <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attacks</GlossaryTooltip>, Cloudflare's autonomous edge and centralized DDoS systems analyze traffic samples out of path, which allows Cloudflare to asynchronously detect DDoS attacks without causing latency or impacting performance.
 
@@ -31,13 +30,13 @@ You can set an override expression for the [HTTP DDoS Attack Protection](/ddos-p
 
 Once attack traffic matches a rule, Cloudflare's systems will track that traffic and generate a real-time signature to surgically match against the attack pattern and mitigate the attack without impacting legitimate traffic. The rules are able to generate different signatures based on various properties of the attacks and the signal strength of each attribute. For example, if the attack is distributed — that is, originating from many source IPs — then the source IP field will not serve as a strong indicator, and the rule will not choose the source IP field as part of the attack signature. Once generated, the fingerprint is propagated as a mitigation rule to the most optimal location on the Cloudflare global network for cost-efficient mitigation. These mitigation rules are ephemeral and will expire shortly after the attack has ended, which happens when no additional traffic has been matched to the rule.
 
-| Actions | Description |
-| --- | --- |
-| Block | Matching requests are denied access to the site. |
-| Managed Challenge | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
-| Interactive Challenge | The client that made the request must pass an interactive Challenge. |
-| Log | Records matching requests in the Cloudflare Logs. |
-| Use rule defaults | Uses the default action that is pre-defined for each rule. |
+| Actions               | Description                                                                                             |
+| --------------------- | ------------------------------------------------------------------------------------------------------- |
+| Block                 | Matching requests are denied access to the site.                                                        |
+| Managed Challenge     | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
+| Interactive Challenge | The client that made the request must pass an interactive Challenge.                                    |
+| Log                   | Records matching requests in the Cloudflare Logs.                                                       |
+| Use rule defaults     | Uses the default action that is pre-defined for each rule.                                              |
 
 ## Thresholds
 
diff --git a/src/content/docs/ddos-protection/about/index.mdx b/src/content/docs/ddos-protection/about/index.mdx
index 65805b05908aecd..c294dbc5482978b 100644
--- a/src/content/docs/ddos-protection/about/index.mdx
+++ b/src/content/docs/ddos-protection/about/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: About Cloudflare DDoS protection
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare provides unmetered and unlimited <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">distributed denial-of-service (DDoS)</GlossaryTooltip> protection at layers 3, 4, and 7 to all customers on all plans and services.
 
@@ -20,4 +19,4 @@ The protection is enabled by Cloudflare's [Autonomous DDoS Protection Edge](/ddo
 
 The Autonomous Edge includes multiple dynamic mitigation rules exposed as [managed rulesets](/ddos-protection/managed-rulesets/), which provide comprehensive protection against a variety of DDoS attacks across layers 3/4 and layer 7 of the OSI model.
 
-[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
\ No newline at end of file
+[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
index 80a1257af1beb09..011867f5ba98440 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
@@ -10,7 +10,6 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced DNS Protection via API
-
 ---
 
 Use the [Cloudflare API](/api/) to configure Advanced DNS Protection via API.
@@ -29,11 +28,11 @@ The `{account_id}` argument is the [account ID](/fundamentals/account/find-accou
 
 The following table summarizes the available operations.
 
-| Operation | Verb + Endpoint |
-| --- | --- |
-| List DNS protection rules | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account. |
-| Add a DNS protection rule | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account. |
-| Get a DNS protection rule | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
-| Update a DNS protection rule | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account. |
-| Delete a DNS protection rule | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account. |
-| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account. |
\ No newline at end of file
+| Operation                       | Verb + Endpoint                                                                                                                                                               |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List DNS protection rules       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account.                                 |
+| Add a DNS protection rule       | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account.                                      |
+| Get a DNS protection rule       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
+| Update a DNS protection rule    | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account.              |
+| Delete a DNS protection rule    | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account.           |
+| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account.                   |
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
index 1c556c9c56533bc..803a3e818448f83 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
-
 ---
 
 # JSON object
@@ -20,15 +19,15 @@ This page contains an example of the DNS protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "mode": "monitoring",
-  "profile_sensitivity": "medium",
-  "rate_sensitivity": "medium",
-  "burst_sensitivity": "medium",
-  "created_on": "2023-10-01T13:10:38.762503+01:00",
-  "modified_on": "2023-10-01T13:10:38.762503+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"mode": "monitoring",
+	"profile_sensitivity": "medium",
+	"rate_sensitivity": "medium",
+	"burst_sensitivity": "medium",
+	"created_on": "2023-10-01T13:10:38.762503+01:00",
+	"modified_on": "2023-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -40,4 +39,4 @@ The `profile_sensitivity` field value must be one of `low` (default), `medium`,
 
 The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`, `medium`, or `high`.
 
-For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
\ No newline at end of file
+For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
index 703796d727a36f1..52ffefc830a024b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced TCP Protection and Advanced DNS Protection via the API
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages to configure Advanced TCP Protection and Advanced DNS Protection via the API.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
index 75c5ed4d2392138..2783ca32b25243f 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
@@ -8,7 +8,6 @@ tags:
   - REST API
 sidebar:
   order: 2
-
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/#endpoints).
@@ -24,18 +23,18 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<PROGRAM_ID>",
-      "name": "rate-limiter",
-      "status": "success",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<PROGRAM_ID>",
+			"name": "rate-limiter",
+			"status": "success",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -52,16 +51,16 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<PROGRAM_ID>",
-    "name": "program",
-    "status": "success",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<PROGRAM_ID>",
+		"name": "program",
+		"status": "success",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -69,15 +68,15 @@ If the program fails compilation or verification, the API returns a detailed err
 
 ```json title="Example error response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "code": 1001,
-      "message": "Program verification failed: invalid memory access at line 42"
-    }
-  ],
-  "messages": []
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"code": 1001,
+			"message": "Program verification failed: invalid memory access at line 42"
+		}
+	],
+	"messages": []
 }
 ```
 
@@ -95,16 +94,16 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<PROGRAM_ID>",
-    "name": "program",
-    "status": "success",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<PROGRAM_ID>",
+		"name": "program",
+		"status": "success",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -120,10 +119,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": null,
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -138,21 +137,21 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID>",
-      "program_id": "<PROGRAM_ID>",
-      "scope": "global",
-      "name": "global",
-      "mode": "enabled",
-      "expression": "",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<RULE_ID>",
+			"program_id": "<PROGRAM_ID>",
+			"scope": "global",
+			"name": "global",
+			"mode": "enabled",
+			"expression": "",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -174,19 +173,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "global",
-    "name": "global",
-    "mode": "monitoring",
-    "expression": "",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "global",
+		"name": "global",
+		"mode": "monitoring",
+		"expression": "",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -211,19 +210,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "enabled",
-    "expression": "ip.dst in { 192.0.2.0/24 }",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "enabled",
+		"expression": "ip.dst in { 192.0.2.0/24 }",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -245,19 +244,19 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "program_id": "<PROGRAM_ID>",
-    "scope": "global",
-    "name": "global",
-    "mode": "enabled",
-    "expression": "",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"program_id": "<PROGRAM_ID>",
+		"scope": "global",
+		"name": "global",
+		"mode": "enabled",
+		"expression": "",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -275,10 +274,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": null,
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -299,7 +298,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 The output PCAP file contains the same packets as the input file, but with annotations on each packet.
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
index e9ea67979faf416..5a3cb4ee6ba3756 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
@@ -12,7 +12,6 @@ sidebar:
 head:
   - tag: title
     content: Configure Programmable Flow Protection via API
-
 ---
 
 Use the [Cloudflare API](/api/) to configure Programmable Flow Protection.
@@ -33,30 +32,30 @@ The tables in the following sections summarize the available operations.
 
 ### Program operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List programs | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
-| Upload a program | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account. |
-| Get a program | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program. |
-| Update a program | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program. |
-| Delete a program | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account. |
-| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account. |
+| Operation           | Method and endpoint / Description                                                                                                                       |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List programs       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
+| Upload a program    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account.                            |
+| Get a program       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program.          |
+| Update a program    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program.                       |
+| Delete a program    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account.     |
+| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account.                |
 
 ### Rule operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List rules | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
-| Create a rule | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account. |
-| Get a rule | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule. |
-| Update a rule | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account. |
-| Delete a rule | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account. |
-| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account. |
+| Operation        | Method and endpoint / Description                                                                                                                 |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List rules       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
+| Create a rule    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account.                            |
+| Get a rule       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule.             |
+| Update a rule    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account.           |
+| Delete a rule    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account.        |
+| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account.                |
 
 ### Debug operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
+| Operation       | Method and endpoint / Description                                                                                                                                                                |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Debug with PCAP | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}/pcap`</p>Runs a program against a PCAP file and returns an annotated PCAP with program verdicts. |
 
 ## Pagination
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
index f0fffca40457798..7857e0cab2af7ad 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Programmable Flow Protection API - JSON objects
-
 ---
 
 This page contains examples of the JSON objects used in the Programmable Flow Protection API.
@@ -20,47 +19,47 @@ This page contains examples of the JSON objects used in the Programmable Flow Pr
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "name": "rate-limiter",
-  "status": "success",
-  "created_on": "2024-01-01T13:06:04.721954+01:00",
-  "modified_on": "2024-01-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"name": "rate-limiter",
+	"status": "success",
+	"created_on": "2024-01-01T13:06:04.721954+01:00",
+	"modified_on": "2024-01-01T13:06:04.721954+01:00"
 }
 ```
 
-| Field | Description |
-| --- | --- |
-| `id` | Unique identifier for the program. |
-| `name` | Name of the program, derived from the uploaded filename. |
-| `status` | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
-| `created_on` | Timestamp when the program was created. |
-| `modified_on` | Timestamp when the program was last modified. |
+| Field         | Description                                                                                                                                             |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | Unique identifier for the program.                                                                                                                      |
+| `name`        | Name of the program, derived from the uploaded filename.                                                                                                |
+| `status`      | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
+| `created_on`  | Timestamp when the program was created.                                                                                                                 |
+| `modified_on` | Timestamp when the program was last modified.                                                                                                           |
 
 ## Rule
 
 ```json
 {
-  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-  "program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "mode": "enabled",
-  "expression": "ip.dst in { 192.0.2.0/24 }",
-  "created_on": "2024-01-01T13:10:38.762503+01:00",
-  "modified_on": "2024-01-01T13:10:38.762503+01:00"
+	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+	"program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"mode": "enabled",
+	"expression": "ip.dst in { 192.0.2.0/24 }",
+	"created_on": "2024-01-01T13:10:38.762503+01:00",
+	"modified_on": "2024-01-01T13:10:38.762503+01:00"
 }
 ```
 
-| Field | Description |
-| --- | --- |
-| `id` | Unique identifier for the rule. |
-| `program_id` | The ID of the program this rule executes. |
-| `scope` | The scope of the rule. Must be one of `global`, `region`, or `datacenter`. |
-| `name` | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code. |
-| `mode` | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`. |
-| `expression` | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
-| `created_on` | Timestamp when the rule was created. |
-| `modified_on` | Timestamp when the rule was last modified. |
+| Field         | Description                                                                                                                       |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | Unique identifier for the rule.                                                                                                   |
+| `program_id`  | The ID of the program this rule executes.                                                                                         |
+| `scope`       | The scope of the rule. Must be one of `global`, `region`, or `datacenter`.                                                        |
+| `name`        | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code.                 |
+| `mode`        | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`.                                                             |
+| `expression`  | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
+| `created_on`  | Timestamp when the rule was created.                                                                                              |
+| `modified_on` | Timestamp when the rule was last modified.                                                                                        |
 
 ### Scope
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
index 8e87b35dd014b57..c8ce427c16455cb 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
@@ -8,7 +8,6 @@ tags:
   - REST API
 sidebar:
   order: 2
-
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/tcp-protection/#endpoints).
@@ -24,12 +23,12 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json title="Example response"
 {
-  "result": {
-    "enabled": false
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"enabled": false
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -58,16 +57,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "prefix": "203.0.113/24",
-      "comment": "My prefix",
-      "excluded": false
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"prefix": "203.0.113/24",
+			"comment": "My prefix",
+			"excluded": false
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -95,27 +94,27 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "id": "<PREFIX_1_ID>",
-      "prefix": "192.0.2.0/24",
-      "excluded": false,
-      "comment": "Game ranges",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    },
-    {
-      "id": "<PREFIX_2_ID>",
-      "prefix": "192.0.2.2/26",
-      "excluded": true,
-      "comment": "Range for a specific game",
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<PREFIX_1_ID>",
+			"prefix": "192.0.2.0/24",
+			"excluded": false,
+			"comment": "Game ranges",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		},
+		{
+			"id": "<PREFIX_2_ID>",
+			"prefix": "192.0.2.2/26",
+			"excluded": true,
+			"comment": "Range for a specific game",
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -130,19 +129,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": [
-    {
-      "id": "<ALLOWLIST_PREFIX_ID>",
-      "prefix": "192.0.2.127",
-      "comment": "Single IP address in allowlist",
-      "enabled": true,
-      "created_on": "<TIMESTAMP>",
-      "modified_on": "<TIMESTAMP>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<ALLOWLIST_PREFIX_ID>",
+			"prefix": "192.0.2.127",
+			"comment": "Single IP address in allowlist",
+			"enabled": true,
+			"created_on": "<TIMESTAMP>",
+			"modified_on": "<TIMESTAMP>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -163,17 +162,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<ALLOWLIST_PREFIX_1_ID>",
-    "prefix": "203.0.113.0/26",
-    "comment": "Partner range",
-    "enabled": true,
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<ALLOWLIST_PREFIX_1_ID>",
+		"prefix": "203.0.113.0/26",
+		"comment": "Partner range",
+		"enabled": true,
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -196,19 +195,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<SYN_FLOOD_RULE_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "monitoring",
-    "rate_sensitivity": "medium",
-    "burst_sensitivity": "medium",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<SYN_FLOOD_RULE_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "monitoring",
+		"rate_sensitivity": "medium",
+		"burst_sensitivity": "medium",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -233,19 +232,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<OOS_TCP_RULE_ID>",
-    "scope": "region",
-    "name": "WEUR",
-    "mode": "monitoring",
-    "rate_sensitivity": "low",
-    "burst_sensitivity": "low",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<OOS_TCP_RULE_ID>",
+		"scope": "region",
+		"name": "WEUR",
+		"mode": "monitoring",
+		"rate_sensitivity": "low",
+		"burst_sensitivity": "low",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -267,16 +266,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<SYN_FLOOD_FILTER_ID>",
-    "expression": "ip.dst in { 192.0.2.0/24 }",
-    "mode": "monitoring",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<SYN_FLOOD_FILTER_ID>",
+		"expression": "ip.dst in { 192.0.2.0/24 }",
+		"mode": "monitoring",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -298,17 +297,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-  "result": {
-    "id": "<OOS_TCP_FILTER_ID>",
-    "expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
-    "mode": "disabled",
-    "created_on": "<TIMESTAMP>",
-    "modified_on": "<TIMESTAMP>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<OOS_TCP_FILTER_ID>",
+		"expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
+		"mode": "disabled",
+		"created_on": "<TIMESTAMP>",
+		"modified_on": "<TIMESTAMP>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
-Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
\ No newline at end of file
+Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
index 54d00d15660f858..5af3cfacb95b70f 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
@@ -12,7 +12,6 @@ head:
     content: Configure Advanced TCP Protection via API
 tags:
   - TCP
-
 ---
 
 You can configure Advanced TCP Protection using the Advanced TCP Protection API.
@@ -37,81 +36,81 @@ The tables in the following sections summarize the available operations.
 
 ### General operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| Get Advanced TCP Protection status | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
+| Operation                             | Method and endpoint / Description                                                                                                                                   |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Get Advanced TCP Protection status    | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
 | Update Advanced TCP Protection status | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Enables or disables Advanced TCP Protection.                        |
 
 ### Prefix operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account. |
+| Operation            | Method and endpoint / Description                                                                                                                             |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List prefixes        | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account.                 |
 | Add prefixes in bulk | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/bulk`</p>Adds prefixes in bulk to the account (up to 300 prefixes per request). |
-| Get a prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix. |
-| Update a prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix. |
-| Delete a prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix. |
-| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account. |
+| Get a prefix         | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix.                       |
+| Update a prefix      | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix.                                    |
+| Delete a prefix      | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix.                                   |
+| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account.                           |
 
 ### Allowlist operations
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List allowlisted prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
-| Add an allowlisted prefix | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
-| Get an allowlisted prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
-| Update an allowlisted prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist. |
-| Delete an allowlisted prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist. |
-| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist. |
+| Operation                       | Method and endpoint / Description                                                                                                                            |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List allowlisted prefixes       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
+| Add an allowlisted prefix       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
+| Get an allowlisted prefix       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
+| Update an allowlisted prefix    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist.              |
+| Delete an allowlisted prefix    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist.           |
+| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist.                       |
 
 ### SYN Flood Protection operations
 
 #### Rules
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List SYN flood rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account. |
-| Add a SYN flood rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account. |
-| Get a SYN flood rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
-| Update a SYN flood rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account. |
-| Delete a SYN flood rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account. |
-| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account. |
+| Operation                  | Method and endpoint / Description                                                                                                                                        |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List SYN flood rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account.                                 |
+| Add a SYN flood rule       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account.                                      |
+| Get a SYN flood rule       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
+| Update a SYN flood rule    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account.              |
+| Delete a SYN flood rule    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account.           |
+| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account.                   |
 
 #### Filters
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List SYN flood filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account. |
-| Add a SYN flood filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account. |
-| Get a SYN flood filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
-| Update a SYN flood filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account. |
-| Delete a SYN flood filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account. |
-| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account. |
+| Operation                    | Method and endpoint / Description                                                                                                                                              |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List SYN flood filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account.                                   |
+| Add a SYN flood filter       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account.                                        |
+| Get a SYN flood filter       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
+| Update a SYN flood filter    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account.              |
+| Delete a SYN flood filter    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account.           |
+| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account.                     |
 
 ### Out-of-state TCP Protection operations
 
 #### Rules
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List out-of-state TCP rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account. |
-| Add an out-of-state TCP rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account. |
-| Get an out-of-state TCP rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
-| Update an out-of-state TCP rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account. |
-| Delete an out-of-state TCP rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account. |
-| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account. |
+| Operation                         | Method and endpoint / Description                                                                                                                                                    |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List out-of-state TCP rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account.                                 |
+| Add an out-of-state TCP rule      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account.                                     |
+| Get an out-of-state TCP rule      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
+| Update an out-of-state TCP rule   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account.              |
+| Delete an out-of-state TCP rule   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account.           |
+| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account.                   |
 
 #### Filters
 
-| Operation | Method and endpoint / Description |
-| --- | --- |
-| List out-of-state TCP filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account. |
-| Add an out-of-state TCP filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account. |
-| Get an out-of-state TCP filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
-| Update an out-of-state TCP filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account. |
-| Delete an out-of-state TCP filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account. |
-| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account. |
+| Operation                           | Method and endpoint / Description                                                                                                                                                          |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| List out-of-state TCP filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account.                                   |
+| Add an out-of-state TCP filter      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account.                                       |
+| Get an out-of-state TCP filter      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
+| Update an out-of-state TCP filter   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account.              |
+| Delete an out-of-state TCP filter   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account.           |
+| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account.                     |
 
 ## Pagination
 
-The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
\ No newline at end of file
+The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
index b2186e3c55edc9b..1368cbecbe0cfe8 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
@@ -11,7 +11,6 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
-
 ---
 
 This page contains an example of the TCP protection rule JSON object used in the API.
@@ -20,12 +19,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "prefix": "192.0.2.0/24",
-  "comment": "Game ranges",
-  "excluded": false,
-  "created_on": "2022-01-01T13:06:04.721954+01:00",
-  "modified_on": "2022-01-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"prefix": "192.0.2.0/24",
+	"comment": "Game ranges",
+	"excluded": false,
+	"created_on": "2022-01-01T13:06:04.721954+01:00",
+	"modified_on": "2022-01-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -33,12 +32,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "prefix": "192.0.2.0/24",
-  "comment": "Game ranges",
-  "enabled": true,
-  "created_on": "2021-10-01T13:06:04.721954+01:00",
-  "modified_on": "2021-10-01T13:06:04.721954+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"prefix": "192.0.2.0/24",
+	"comment": "Game ranges",
+	"enabled": true,
+	"created_on": "2021-10-01T13:06:04.721954+01:00",
+	"modified_on": "2021-10-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -48,13 +47,13 @@ The `prefix` field can contain an IP address or a CIDR range.
 
 ```json
 {
-  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-  "scope": "region",
-  "name": "WEUR",
-  "rate_sensitivity": "medium",
-  "burst_sensitivity": "medium",
-  "created_on": "2021-10-01T13:10:38.762503+01:00",
-  "modified_on": "2021-10-01T13:10:38.762503+01:00"
+	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+	"scope": "region",
+	"name": "WEUR",
+	"rate_sensitivity": "medium",
+	"burst_sensitivity": "medium",
+	"created_on": "2021-10-01T13:10:38.762503+01:00",
+	"modified_on": "2021-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -66,11 +65,11 @@ The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`
 
 ```json
 {
-  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-  "expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
-  "mode": "enabled",
-  "created_on": "2022-11-01T13:10:38.762503+01:00",
-  "modified_on": "2022-11-01T13:10:38.762503+01:00"
+	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+	"expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
+	"mode": "enabled",
+	"created_on": "2022-11-01T13:10:38.762503+01:00",
+	"modified_on": "2022-11-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -86,4 +85,4 @@ The `expression` field is a [Rules language expression](/ruleset-engine/rules-la
 Expressions of SYN flood protection and out-of-state TCP protection filters do not currently support functions.
 :::
 
-The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
\ No newline at end of file
+The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
index 7906194f1a69e0b..e542bce53c6b4fa 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
@@ -9,9 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Add a prefix to Advanced DDoS Protection
-
 ---
-import { Steps, DashButton } from "~/components"
+
+import { Steps, DashButton } from "~/components";
 
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
@@ -28,4 +28,4 @@ To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to
 :::note[Note]
 
 The **Add existing prefix** list will not display leased prefixes, but you can add them manually in the Cloudflare dashboard or [using the API](/ddos-protection/advanced-ddos-systems/api/). You cannot add [delegated prefixes](/byoip/concepts/prefix-delegations/) to Advanced TCP Protection.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
index df2d627092922fe..405eeb35a0dab05 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 5
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
@@ -26,4 +25,4 @@ To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 :::note
 
 Prefixes or subsets added as _Excluded_ will not be protected by Advanced TCP Protection.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
index 19ab785b897da72..87c03f48746ed33 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: How-to guides
 description: How-to guides for configuring Advanced TCP Protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
index 7ee74065ee74642..fe36b285e12bed7 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
@@ -8,11 +8,9 @@ sidebar:
   group:
     hideIndex: true
   order: 6
-
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on Cloudflare's Advanced DDoS systems:
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
index 495f1aa4c759f15..bedd9eaac204c3e 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
@@ -39,20 +39,20 @@ Once thresholds are configured, the Advanced DDoS Protection systems have been i
 
 Automatic thresholds for Cloudflare's Advanced DDoS Protection system optimizes the detection and mitigation of DDoS attacks by automatically calculating appropriate traffic thresholds for each system for each customer account. This system applies to Advanced TCP Protection (specifically SYN Flood Protection and Out-of-State TCP Flood Protection) and Advanced DNS Protection.
 
-Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds. 
+Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds.
 
 #### Process
 
-The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below. 
+The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below.
 
 - The `flowtrackd` account was created within the past 7 to 10 days.
 - The account has at least one configured global threshold (rate and burst). This can be a threshold that was automatically provisioned by the system or manually provisioned by Cloudflare.
 
 These checks are performed independently for SYN Flood Protection, Out-of-State TCP Flood Protection, and Advanced DNS Protection. The criteria does not require the presence of any rules to be configured. Accounts initially provisioned by the automatic system will have default thresholds. Otherwise, thresholds may be unconfigured if they are not set by Cloudflare.
 
-After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic. 
+After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic.
 
-Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst. 
+Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst.
 
 Thresholds are derived using the 95th percentile (P95) of observed traffic over the preceding seven days:
 
@@ -60,9 +60,9 @@ Thresholds are derived using the 95th percentile (P95) of observed traffic over
 - Out-of-State TCP Flood Protection: Based on all other TCP flag traffic.
 - Advanced DNS Protection: Based on DNS over UDP traffic.
 
-While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance. 
+While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance.
 
-The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team. 
+The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team.
 
 #### Implementation
 
@@ -70,7 +70,7 @@ You should enable the automatically provisioned rules. Initially, these rules wi
 
 #### Recalculation
 
-Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration. 
+Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration.
 
 #### Overrides
 
@@ -82,7 +82,7 @@ If you are actively under attack and diverting traffic to Cloudflare, the automa
 
 #### Limitations
 
-Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated. 
+Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated.
 
 The auto-threshold calculation component currently runs only in PDX. Therefore, this feature is not compatible if you have enabled Data Localization Services (DLS) and are located outside of the US, such as EU CMB. Future improvements will address this limitation.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
index 5c86d3ba72f115a..8e7eeb417b2d7c0 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
@@ -60,7 +60,7 @@ The Programmable Flow Protection system supports the [Data Localization suite](/
 :::caution[Beta functionality limitations]
 
 For more information on beta services, refer to section 2.6 in the [Enterprise Terms of Service](https://www.cloudflare.com/enterpriseterms/).
-  :::
+:::
 
 ### Write a basic program
 
@@ -210,6 +210,7 @@ The steps below write a sample program that drops all User Datagram Protocol (UD
 </Steps>
 
 For reference, the example below is the basic program in its entirety:
+
 ```c
 #define CF_EBPF_HELPER_V0
 
@@ -269,7 +270,6 @@ cf_ebpf_main(void *state)
 }
 ```
 
-
 ### Write a complex program: challenge-based response
 
 The example program below implements a UDP-based challenge-response mechanism using helper functions to maintain state between packets from the same source IP. This is useful for mitigating DDoS attacks by requiring clients to prove they can receive and respond to challenges before allowing their traffic through.
@@ -644,12 +644,12 @@ For reference, the example below is the rate limiting program in its entirety:
 #define RATE_LIMIT 100         // Maximum packets allowed per window
 #define WINDOW_SECONDS 60      // Time window in seconds
 
-// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the 
+// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the
 // table hold a timestamp and a counter to accomplish a ratelimit.
-// 
-// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted. 
+//
+// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted.
 // Values are also garbage collected from the table every 1hr.
-// 
+//
 // The macros below pack the timestamp (upper 32 bits) and counter (lower 32 bits) into 64-bit data
 // into a value that we can store into the source IP table.
 #define PACK_STATE(ts, count) (((uint64_t)(ts) << 32) | ((uint64_t)(count) & 0xFFFFFFFF))
@@ -727,14 +727,15 @@ If an incoming packet's source IP is blocklisted in the source IP state table, t
 
 The source IP state table stores state keyed by source IP address. Each entry contains:
 
-| Field | Type | Description |
-| --- | --- | --- |
-| Status | Enum | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
-| User data | `u64` | A user-defined value you can set for any purpose. |
+| Field     | Type  | Description                                                                                      |
+| --------- | ----- | ------------------------------------------------------------------------------------------------ |
+| Status    | Enum  | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
+| User data | `u64` | A user-defined value you can set for any purpose.                                                |
 
 The default maximum capacity is 1,000 entries.
 
 Use the following helper functions to interact with this table:
+
 - `get_src_ip_status` — Retrieve the status of the current packet's source IP.
 - `set_src_ip_status` — Set the status of the current packet's source IP.
 - `get_src_ip_data` — Retrieve the user data for the current packet's source IP.
@@ -747,6 +748,7 @@ The flow state table stores state keyed by the 4-tuple: source IP, source port,
 The default maximum capacity is 10,000 entries.
 
 Use the following helper functions to interact with this table:
+
 - `get_flow_data` — Retrieve the user data for the current flow.
 - `set_flow_data` — Store user data for the current flow.
 
@@ -768,32 +770,32 @@ Helper functions may be removed or changed. New helper functions may be introduc
 
 The table below provides a list of currently supported helper functions:
 
-| Function name       | Function signature                                                               | Description                                                                                                                                                                                                                             |
-| ------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `rand`      | `uint64_t rand(void)`                                                                           | Generates a random unsigned integer.                                                                                                                                                                                                    |
-| `timestamp` | `uint64_t timestamp(void)` | Returns the current timestamp. |
-| `hash_md5` | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes MD5 hash of the source buffer and stores result in destination buffer. |
-| `hash_sha256` | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-256 hash of the source buffer and stores result in destination buffer. |
-| `hash_sha512` | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-512 hash of the source buffer and stores result in destination buffer. |
-| `hash_crc32` | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes CRC32 hash of the source buffer and stores result in destination buffer. |
-| `hmac_sha256` | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer. |
-| `hmac_sha512` | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer. |
-| `set_challenge` | `int set_challenge(uint8_t *src, size_t src_len)` | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset. |
-| `get_src_ip_status` | `uint64_t get_src_ip_status(void)` | Retrieves the status value associated with the source IP address from the state table. |
-| `set_src_ip_status` | `int set_src_ip_status(uint64_t status)` | Sets the status value associated with the source IP address in the state table. |
-| `get_src_ip_data` | `int get_src_ip_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the source IP address from the state table. |
-| `set_src_ip_data` | `int set_src_ip_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the source IP address in the state table. |
-| `get_flow_data` | `int get_flow_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the current flow from the state table. |
-| `set_flow_data` | `int set_flow_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the current flow in the state table. |
-| `entropy` | `double entropy(uint8_t *src, size_t src_len)` | Calculates the entropy of the source buffer. |
-| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)` | Sets a custom tag for network analytics reporting. Defaults to `0` if not set. |
-| `ntohs` | `uint16_t ntohs(uint16_t netshort)` | Converts a 16-bit integer from network byte order to host byte order. |
-| `htons` | `uint16_t htons(uint16_t hostshort)` | Converts a 16-bit integer from host byte order to network byte order. |
-| `ntohl` | `uint32_t ntohl(uint32_t netlong)` | Converts a 32-bit integer from network byte order to host byte order. |
-| `htonl` | `uint32_t htonl(uint32_t hostlong)` | Converts a 32-bit integer from host byte order to network byte order. |
-| `ntohll` | `uint64_t ntohll(uint64_t netlonglong)` | Converts a 64-bit integer from network byte order to host byte order. |
-| `htonll` | `uint64_t htonll(uint64_t hostlonglong)` | Converts a 64-bit integer from host byte order to network byte order. |
-| `parse_packet_data` | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)` | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
+| Function name               | Function signature                                                                          | Description                                                                                                                                                                                                                             |
+| --------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rand`                      | `uint64_t rand(void)`                                                                       | Generates a random unsigned integer.                                                                                                                                                                                                    |
+| `timestamp`                 | `uint64_t timestamp(void)`                                                                  | Returns the current timestamp.                                                                                                                                                                                                          |
+| `hash_md5`                  | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)`                                  | Computes MD5 hash of the source buffer and stores result in destination buffer.                                                                                                                                                         |
+| `hash_sha256`               | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-256 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
+| `hash_sha512`               | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-512 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
+| `hash_crc32`                | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)`                                | Computes CRC32 hash of the source buffer and stores result in destination buffer.                                                                                                                                                       |
+| `hmac_sha256`               | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
+| `hmac_sha512`               | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
+| `set_challenge`             | `int set_challenge(uint8_t *src, size_t src_len)`                                           | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset.                                                                                                                                                 |
+| `get_src_ip_status`         | `uint64_t get_src_ip_status(void)`                                                          | Retrieves the status value associated with the source IP address from the state table.                                                                                                                                                  |
+| `set_src_ip_status`         | `int set_src_ip_status(uint64_t status)`                                                    | Sets the status value associated with the source IP address in the state table.                                                                                                                                                         |
+| `get_src_ip_data`           | `int get_src_ip_data(uint8_t *dst, size_t dst_len)`                                         | Retrieves custom data associated with the source IP address from the state table.                                                                                                                                                       |
+| `set_src_ip_data`           | `int set_src_ip_data(uint8_t *src, size_t src_len)`                                         | Stores custom data associated with the source IP address in the state table.                                                                                                                                                            |
+| `get_flow_data`             | `int get_flow_data(uint8_t *dst, size_t dst_len)`                                           | Retrieves custom data associated with the current flow from the state table.                                                                                                                                                            |
+| `set_flow_data`             | `int set_flow_data(uint8_t *src, size_t src_len)`                                           | Stores custom data associated with the current flow in the state table.                                                                                                                                                                 |
+| `entropy`                   | `double entropy(uint8_t *src, size_t src_len)`                                              | Calculates the entropy of the source buffer.                                                                                                                                                                                            |
+| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)`                                                  | Sets a custom tag for network analytics reporting. Defaults to `0` if not set.                                                                                                                                                          |
+| `ntohs`                     | `uint16_t ntohs(uint16_t netshort)`                                                         | Converts a 16-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htons`                     | `uint16_t htons(uint16_t hostshort)`                                                        | Converts a 16-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `ntohl`                     | `uint32_t ntohl(uint32_t netlong)`                                                          | Converts a 32-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htonl`                     | `uint32_t htonl(uint32_t hostlong)`                                                         | Converts a 32-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `ntohll`                    | `uint64_t ntohll(uint64_t netlonglong)`                                                     | Converts a 64-bit integer from network byte order to host byte order.                                                                                                                                                                   |
+| `htonll`                    | `uint64_t htonll(uint64_t hostlonglong)`                                                    | Converts a 64-bit integer from host byte order to network byte order.                                                                                                                                                                   |
+| `parse_packet_data`         | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)`   | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
 
 ---
 
@@ -805,7 +807,7 @@ With the exception of `rand`, `timestamp`, `ntohs`, `htons`, `ntohl`, `htonl`, `
 
 To upload a program, navigate to Networking > L3/4 DDoS protection > Advanced Protection in the Cloudflare dashboard. Then select the tab titled Programmable Flow Protection.
 
-Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code. 
+Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code.
 
 The Cloudflare API will receive the source code in the `C` file, compile it into BPF bytecode, and run the verifier against it.
 
@@ -813,12 +815,11 @@ If compilation or verification fails, the API will return a detailed error messa
 
 If compilation and verification succeeds, Cloudflare will store the source code and object file to the account and return the program ID.
 
-
 ### Update a program
 
 During the development process, you may find it useful to update the same program (identified by the same program ID) instead of repeatedly creating new programs as new resources.
 
-To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code. 
+To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code.
 
 :::note
 It is possible to update and overwrite a program that is currently in use by one or more rules. When doing so, you will be warned that the program is currently active and will be overwritten. However, if an active program is being updated with a program that either does not compile or can not be verified, the update will fail and the old program will continue to be in use.
@@ -832,7 +833,7 @@ A link icon next to the program name indicates that the program is currently in
 
 ### Delete a program
 
-To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**. 
+To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**.
 
 Note that you will not be able to delete a program that is referenced in an active Rule.
 
@@ -887,10 +888,11 @@ curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/programmab
 
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
+
 ---
 
 ## Safe program and rule deployment best practices
@@ -1011,7 +1013,7 @@ struct cf_ebpf_parsed_headers {
    uint8_t        *data_end;
 };
 
-/* 
+/*
 * IPv4 header, used as field of cf_ebpf_parsed_headers */
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ip.h#L87
 */
@@ -1034,10 +1036,10 @@ struct iphdr {
     uint32_t daddr;
 };
 
-/* 
+/*
 * IPv6 header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ipv6.h#L118
-*/ 
+*/
 struct ipv6hdr {
 #if defined(__BYTE_ORDER__) && __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
     uint8_t  version:4,
@@ -1054,7 +1056,7 @@ struct ipv6hdr {
     uint8_t  daddr[16];
 };
 
-/* 
+/*
 * UDP header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/udp.h#L23
 */
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
index 36422e1fcf667c9..05220d120fb6f68 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
@@ -19,6 +19,7 @@ Always transition from Monitoring mode to Mitigation (Enabled) mode. Do not swit
 When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Protection begins a learning period to observe existing connection state. Long-lived connections that pre-date this learning period may be dropped because they have no state in the tracker.
 
 **Recommended procedure:**
+
 1. Set to **Monitoring** mode for at least 4 hours (longer if your network has long-lived connections).
 2. Review the Monitoring mode logs in [Network Analytics](/analytics/network-analytics/) to confirm legitimate traffic patterns.
 3. Switch to **Mitigation (Enabled)** mode.
@@ -27,12 +28,12 @@ When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Pro
 
 Check the **Mitigation reason** field in the **Advanced TCP Protection** tab of [Network Analytics](/analytics/network-analytics/) and use the reason to identify the cause:
 
-| Mitigation reason | Likely cause | Action |
-|---|---|---|
-| **Not found** | Learning period was incomplete, or long-lived connections pre-date ATP activation | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled) |
-| **Unexpected** | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
-| **Out of sequence** | Packet reordering or packet loss in the network path | Increase burst sensitivity threshold for the affected colo |
-| Drops during traffic spikes only | Burst sensitivity threshold too low | Increase burst sensitivity (keep rate sensitivity the same) |
+| Mitigation reason                | Likely cause                                                                              | Action                                                                                                  |
+| -------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| **Not found**                    | Learning period was incomplete, or long-lived connections pre-date ATP activation         | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled)                                |
+| **Unexpected**                   | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
+| **Out of sequence**              | Packet reordering or packet loss in the network path                                      | Increase burst sensitivity threshold for the affected colo                                              |
+| Drops during traffic spikes only | Burst sensitivity threshold too low                                                       | Increase burst sensitivity (keep rate sensitivity the same)                                             |
 
 **Threshold tuning:** Adjust burst sensitivity before rate sensitivity. Burst sensitivity handles momentary spikes; rate sensitivity controls sustained packet rates.
 
diff --git a/src/content/docs/ddos-protection/best-practices/index.mdx b/src/content/docs/ddos-protection/best-practices/index.mdx
index c90d2aafc0fd31d..d5e1f5b2afacde1 100644
--- a/src/content/docs/ddos-protection/best-practices/index.mdx
+++ b/src/content/docs/ddos-protection/best-practices/index.mdx
@@ -9,10 +9,9 @@ sidebar:
     hideIndex: true
 head: []
 description: Learn about best practices for configuring Cloudflare's DDoS protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on DDoS protection best practices:
 
diff --git a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
index 4be4546f04f6fa5..07721304f2cfb3c 100644
--- a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
+++ b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
@@ -11,7 +11,7 @@ tags:
   - Caching
 ---
 
-import { GlossaryTooltip, Steps } from "~/components"
+import { GlossaryTooltip, Steps } from "~/components";
 
 Cloudflare's network automatically mitigates large <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">DDoS attacks</GlossaryTooltip>, but these attacks can still affect your application.
 
@@ -35,4 +35,4 @@ In addition to the steps for all customers, Cloudflare Enterprise customers subs
 
 ## Magic Transit customers
 
-In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
\ No newline at end of file
+In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
diff --git a/src/content/docs/ddos-protection/best-practices/third-party.mdx b/src/content/docs/ddos-protection/best-practices/third-party.mdx
index 5e4e9065879bfc6..f7d646f767015f2 100644
--- a/src/content/docs/ddos-protection/best-practices/third-party.mdx
+++ b/src/content/docs/ddos-protection/best-practices/third-party.mdx
@@ -25,7 +25,7 @@ Therefore, it is recommended that you **use the [Cloudflare CDN](/cache/)**, whi
 - You perform DDoS filtering in the first point of contact from the Internet, which is a recommended best practice.
 
 :::caution[L3/4 DDoS mitigation accuracy]
-Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation. 
+Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation.
 
 When traffic is proxied through another vendor, the vendor's IP addresses are available to Cloudflare's network-layer protection systems rather than the true client IP addresses. This lack of visibility into the original source can lead to less effective automated mitigation and potential false positives.
 :::
diff --git a/src/content/docs/ddos-protection/botnet-threat-feed.mdx b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
index ba3a7ca8409be2e..8058f8d886012b1 100644
--- a/src/content/docs/ddos-protection/botnet-threat-feed.mdx
+++ b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
@@ -14,9 +14,9 @@ learning_center:
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-botnet/
 tags:
   - REST API
-
 ---
-import { Steps, APIRequest, DashButton } from "~/components"
+
+import { Steps, APIRequest, DashButton } from "~/components";
 
 The Cloudflare DDoS Botnet Threat Feed is a threat intelligence feed for service providers (SPs) such as hosting providers and Internet service providers (ISPs) that provides information about their own IP addresses that have participated in HTTP DDoS attacks as observed from Cloudflare's global network. The feed aims to help service providers stop the abuse and reduce DDoS attacks originating from within their networks.
 
@@ -85,7 +85,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
 - The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
 - Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
 - When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
-:::
+  :::
 
 To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:
 
@@ -103,23 +103,23 @@ Retrieves all the data in the botnet tracking database for a given ASN (currentl
 The provided `{asn}` must be affiliated with your account.
 
 <APIRequest
-  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
-  method="GET"
+	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
+	method="GET"
 />
 
 ```json output
 {
-  "result": [
-    {
-      "cidr": "127.0.0.1/32",
-      "date": "1970-01-01T00:00:00Z",
-      "offense_count": 10000
-    },
-    // ... other entries ...
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"cidr": "127.0.0.1/32",
+			"date": "1970-01-01T00:00:00Z",
+			"offense_count": 10000
+		}
+		// ... other entries ...
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -135,22 +135,22 @@ The provided `{asn}` must be affiliated with your account.
 `{date}` must be an ISO 8601-formatted date: `YYYY-MM-DD`. If no date is specified, the API responds with the data from the day before.
 
 <APIRequest
-  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
-  method="GET"
+	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
+	method="GET"
 />
 
 ```json output
 {
-  "result": [
-    {
-      "cidr": "127.0.0.1/32",
-      "date": "2024-05-05T00:00:00Z",
-      "offense_count": 10000
-    },
-    // ... other entries ...
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"cidr": "127.0.0.1/32",
+			"date": "2024-05-05T00:00:00Z",
+			"offense_count": 10000
+		}
+		// ... other entries ...
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
index 23e89367c6df2b1..294386d75a7913f 100644
--- a/src/content/docs/ddos-protection/get-started.mdx
+++ b/src/content/docs/ddos-protection/get-started.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 3
-
 ---
 
-import { Steps } from "~/components"
+import { Steps } from "~/components";
 
 ## Free, Pro, and Business plans
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
index d811b5a27be035b..da3c36e2cef5dc2 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
@@ -55,7 +55,7 @@ Cloudflare HTTP DDoS Protection can also initiate mitigation based on the origin
 This rule is available for zones on any plan.
 :::
 
-While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules: 
+While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules:
 
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by configuring the HTTP DDoS Attack Protection managed ruleset.
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
index aa5cf2850cf749b..d30b1f397074ef2 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
@@ -6,7 +6,6 @@ products:
   - ddos-protection
 sidebar:
   order: 5
-
 ---
 
 The DDoS Attack Protection managed rulesets provide comprehensive protection against a [variety of DDoS attacks](/ddos-protection/about/attack-coverage/) across L3/4 (network layer) and L7 (application layer) of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/).
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
index 08ab036ae1868dc..ec4a3407ca3c976 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
@@ -54,7 +54,7 @@ While you can manually override a rule from `Log` to `Block`, consider the follo
 
 - The default action of a rule is decided during the testing period. Cloudflare may set its default action to **DDoS Dynamic**, which may use rate-limiting or a multi-step mitigation combination based on traffic factors. By applying a manual `Block` override, you prevent your configuration from automatically inheriting the more nuanced DDoS Dynamic action once it is released.
 
-If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action. 
+If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action.
 
 ## Availability
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
index 679aaba3f002a27..526d496f44f19d3 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Override examples for Network-layer DDoS Attack Protection
-
 ---
 
-import { Details, GlossaryTooltip, DashButton } from "~/components"
+import { Details, GlossaryTooltip, DashButton } from "~/components";
 
 ## Use cases
 
@@ -36,11 +35,12 @@ To avoid disruptions during initial deployment, you can create a _Log_ only –
 
 1. In the Cloudflare dashboard, go to the **Security rules** page.
 
-    <DashButton url="/?to=/:account/:zone/security/security-rules" />
+   <DashButton url="/?to=/:account/:zone/security/security-rules" />
+
 2. Go to the **DDoS protection** tab.
 3. On **HTTP DDoS attack protection**, select **Create override**.
 4. Set the **Scope** to _Apply to all incoming requests_.
 5. Under **Ruleset configuration**:
-    - Set the **Ruleset action** to _Log_.
-    - Set the **Ruleset sensitivity** to _Essentially Off_. 
-6. Select **Save**. 
\ No newline at end of file
+   - Set the **Ruleset action** to _Log_.
+   - Set the **Ruleset sensitivity** to _Essentially Off_.
+6. Select **Save**.
diff --git a/src/content/docs/ddos-protection/reference/alerts.mdx b/src/content/docs/ddos-protection/reference/alerts.mdx
index 02ded106c58f5b9..2d58a70a27086ca 100644
--- a/src/content/docs/ddos-protection/reference/alerts.mdx
+++ b/src/content/docs/ddos-protection/reference/alerts.mdx
@@ -108,4 +108,4 @@ To investigate a possibly ongoing attack, select **View Dashboard**. To go to th
 - In some cases, HTTP DDoS attack alerts will reference the attacked zone name instead of the attacked hostname. This occurs when the attack signature does not include information on the attacked hostname because it is not a strong indicator for identifying attack requests. For more information on attack signatures, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
 - DDoS alerts are currently only available for DDoS attacks detected and mitigated by the [DDoS managed rulesets](/ddos-protection/managed-rulesets/). Alerts are not yet available for DDoS attacks detected and mitigated by the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), the [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), or the [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) system.
 - You will not receive duplicate DDoS alerts within the same one-hour time frame.
-- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
\ No newline at end of file
+- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
diff --git a/src/content/docs/ddos-protection/reference/index.mdx b/src/content/docs/ddos-protection/reference/index.mdx
index 1ffe418f0eceaf3..3ae60ce4bd017c0 100644
--- a/src/content/docs/ddos-protection/reference/index.mdx
+++ b/src/content/docs/ddos-protection/reference/index.mdx
@@ -9,10 +9,9 @@ sidebar:
     hideIndex: true
 head: []
 description: Reference information for Cloudflare's DDoS protection.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Cloudflare DDoS protection:
 
diff --git a/src/content/docs/ddos-protection/reference/logs.mdx b/src/content/docs/ddos-protection/reference/logs.mdx
index f0d23899c38c060..1bbc798b5e49584 100644
--- a/src/content/docs/ddos-protection/reference/logs.mdx
+++ b/src/content/docs/ddos-protection/reference/logs.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: DDoS logs
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Retrieve HTTP events using [Cloudflare Logs](/logs/) to integrate them into your <GlossaryTooltip term="SIEM">SIEM systems</GlossaryTooltip>.
 
diff --git a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
index 187dff380ea2545..20dba8ba991db4e 100644
--- a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
+++ b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
@@ -6,10 +6,9 @@ products:
   - ddos-protection
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 After onboarding to Cloudflare, you may want to simulate DDoS attacks against your Internet properties to test the protection, [reporting](/ddos-protection/reference/reports/), and [alerting](/ddos-protection/reference/alerts/) mechanisms. Follow the guidelines in this section to simulate a DDoS attack.
 
diff --git a/src/content/docs/dmarc-management/enable.mdx b/src/content/docs/dmarc-management/enable.mdx
index 1eeb169d8368e0c..c38ef8ef703db1d 100644
--- a/src/content/docs/dmarc-management/enable.mdx
+++ b/src/content/docs/dmarc-management/enable.mdx
@@ -10,7 +10,6 @@ sidebar:
     text: Beta
 tags:
   - DNS
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -30,4 +29,4 @@ To enable DMARC Management:
    - If no DMARC record is found, Cloudflare will automatically invite you to add one that you can edit later. Select **Add** to continue.
    - If a DMARC record is found in your zone, Cloudflare will add another `rua` (Reporting URI for Aggregate data) entry to it. The `rua` tag specifies the URI (typically a `mailto:` address) where aggregate DMARC reports are sent. This additional entry uses a Cloudflare email address so that Cloudflare can receive and process DMARC reports on your behalf. Select **Next** to continue.
 
-DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
\ No newline at end of file
+DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
diff --git a/src/content/docs/dmarc-management/security-records.mdx b/src/content/docs/dmarc-management/security-records.mdx
index 2ec513fecf908f2..df2912e19e4d6cc 100644
--- a/src/content/docs/dmarc-management/security-records.mdx
+++ b/src/content/docs/dmarc-management/security-records.mdx
@@ -29,4 +29,4 @@ To set up email security records:
 
 ## Edit or delete records
 
-Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
\ No newline at end of file
+Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
diff --git a/src/content/docs/dmarc-management/statistics.mdx b/src/content/docs/dmarc-management/statistics.mdx
index 58a5e6ea804a49b..b9186d28b90635d 100644
--- a/src/content/docs/dmarc-management/statistics.mdx
+++ b/src/content/docs/dmarc-management/statistics.mdx
@@ -11,7 +11,6 @@ head:
     content: Review DMARC statistics
 tags:
   - DNS
-
 ---
 
 DMARC Management (beta) allows you to review whether emails sent on your behalf passed or failed DMARC, SPF, and DKIM authentication checks.
diff --git a/src/content/docs/dns/additional-options/index.mdx b/src/content/docs/dns/additional-options/index.mdx
index 66b93896ae59062..2c2a6572e2ac236 100644
--- a/src/content/docs/dns/additional-options/index.mdx
+++ b/src/content/docs/dns/additional-options/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Beyond [setting up your zone](/dns/zone-setups/) and [updating your DNS records](/dns/manage-dns-records/), you may want to customize the following settings in Cloudflare DNS:
 
diff --git a/src/content/docs/dns/changelog.mdx b/src/content/docs/dns/changelog.mdx
index b1163dea5558b84..3c688d1cb2da69d 100644
--- a/src/content/docs/dns/changelog.mdx
+++ b/src/content/docs/dns/changelog.mdx
@@ -12,7 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelogs/dns/. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="dns"/>
+<ProductChangelog product="dns" />
 
 ## 2025-01-27
 
@@ -26,11 +26,11 @@ Records returned by the API will no longer contain the `zone_id` and `zone_name`
 
 When creating [TXT records](/dns/manage-dns-records/reference/dns-record-types/#txt) via the dashboard you will now find:
 
-* Field validation errors if double quotes `"` are added inconsistently.
-* Automatically quoted TXT content upon save if no quotes exist in the record content field.
+- Field validation errors if double quotes `"` are added inconsistently.
+- Automatically quoted TXT content upon save if no quotes exist in the record content field.
 
 ## 2024-10-07
 
 **API support for per-record CNAME flattening**
 
-Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
\ No newline at end of file
+Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx
index 918f0fcc6932086..521021c63c3011d 100644
--- a/src/content/docs/dns/cname-flattening/index.mdx
+++ b/src/content/docs/dns/cname-flattening/index.mdx
@@ -31,4 +31,4 @@ For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), re
 
 - CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
 - CNAME to a different Cloudflare account is prohibited and will result in [Error 1014: CNAME Cross-User Banned](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/)
-- <Render file="cname-flattening-callout" product="dns" />
\ No newline at end of file
+- <Render file="cname-flattening-callout" product="dns" />
diff --git a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
index 675a692b4527d82..22b36e298b9f3bf 100644
--- a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
+++ b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
@@ -11,7 +11,13 @@ head:
     content: Set up CNAME flattening
 ---
 
-import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 :::note
 
diff --git a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
index 3b579df96996538..c961134f600f565 100644
--- a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
+++ b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Protect against random prefix attacks
-
 ---
 
 import { APIRequest } from "~/components";
@@ -23,10 +22,10 @@ In order to enable automatic mitigation of [random prefix attacks](/dns/dns-fire
    	path="/accounts/{account_id}/dns_firewall/{dns_firewall_id}"
    	method="PATCH"
    	json={{
-      "attack_mitigation": {
-        "enabled": true,
-        "only_when_upstream_unhealthy": true,
-      }
+   		attack_mitigation: {
+   			enabled: true,
+   			only_when_upstream_unhealthy: true,
+   		},
    	}}
    />
 
@@ -34,8 +33,6 @@ Once you receive a `200` success response from the API, queries identified as be
 
 :::note
 
-
 If you do not specify otherwise in your API call, Cloudflare automatically sets the `"only_when_upstream_unhealthy"` parameter to true, which means that Cloudflare will only mitigate attacks when we detect that the upstream is unresponsive (possibly as a result of an attack). This setting can also be changed via the API, using a request similar to the ones shown above.
 
-
 :::
diff --git a/src/content/docs/dns/dnssec/dnssec-states.mdx b/src/content/docs/dns/dnssec/dnssec-states.mdx
index 5b40526a38a6545..381c0a152b40f23 100644
--- a/src/content/docs/dns/dnssec/dnssec-states.mdx
+++ b/src/content/docs/dns/dnssec/dnssec-states.mdx
@@ -6,17 +6,16 @@ products:
 title: DNSSEC states
 sidebar:
   order: 4
-
 ---
 
 This page describes different DNSSEC states and how they relate to the responses you get from the [DNSSEC details API endpoint](/api/resources/dns/subresources/dnssec/methods/get/).
 
-| State            | API response                                                     | Description                                                                                                                                                                       |
-| ---------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                         |
-| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                 |
-| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                            |
-| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                        |
+| State            | API response                                                     | Description                                                                                                                                                                                 |
+| ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                                   |
+| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                           |
+| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                                      |
+| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                                  |
 | Deleted          | `"status":"disabled"`<br /> `"modified_on": null`                | DNSSEC has never been enabled for the zone or DNSSEC has been disabled and then deleted using the [Delete DNSSEC records endpoint](/api/resources/dns/subresources/dnssec/methods/delete/). |
 
 :::caution
diff --git a/src/content/docs/dns/dnssec/enable-nsec3.mdx b/src/content/docs/dns/dnssec/enable-nsec3.mdx
index 710497fda89108a..adc9d72f7a3971a 100644
--- a/src/content/docs/dns/dnssec/enable-nsec3.mdx
+++ b/src/content/docs/dns/dnssec/enable-nsec3.mdx
@@ -22,8 +22,8 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met
 	path="/zones/{zone_id}/dnssec"
 	method="PATCH"
 	json={{
-		"dnssec_use_nsec3": true,
-		"status": "active"
+		dnssec_use_nsec3: true,
+		status: "active",
 	}}
 />
 
diff --git a/src/content/docs/dns/dnssec/index.mdx b/src/content/docs/dns/dnssec/index.mdx
index a4f8af210e23313..d58d3d633a1fcfb 100644
--- a/src/content/docs/dns/dnssec/index.mdx
+++ b/src/content/docs/dns/dnssec/index.mdx
@@ -6,14 +6,13 @@ products:
 title: DNSSEC
 sidebar:
   order: 8
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="dnssec-definition" product="dns" />
 
-***
+---
 
 ## Disable DNSSEC
 
@@ -21,7 +20,7 @@ import { Render } from "~/components"
 
 <Render file="dnssec-enabled-migration" product="dns" />
 
-***
+---
 
 ## Enable DNSSEC
 
@@ -37,7 +36,7 @@ When you enable DNSSEC, Cloudflare signs your zone, publishes your public signin
 
 <Render file="dnssec-auto-add" product="dns" />
 
-***
+---
 
 ## Other DNSSEC setup options
 
@@ -45,14 +44,14 @@ If you are using Cloudflare as your Secondary DNS provider and want to configure
 
 If you want to set up DNSSEC on a subdomain zone, refer to [Subdomain DNSSEC](/dns/zone-setups/subdomain-setup/dnssec/).
 
-***
+---
 
 ## Limitations
 
 If your registrar does not support DNSSEC with Cloudflare's preferred cipher choice (Algorithm 13), you have several options:
 
-* Contact your registrar to ask for DNSSEC with modern encryption.
-* Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
-* File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
+- Contact your registrar to ask for DNSSEC with modern encryption.
+- Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
+- File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
 
-If your top-level domain does not support DNSSEC with Algorithm 13 (also known as *ECDSA Curve P-256 with SHA-256*), [contact that top-level domain](https://www.iana.org/domains/root/db).
\ No newline at end of file
+If your top-level domain does not support DNSSEC with Algorithm 13 (also known as _ECDSA Curve P-256 with SHA-256_), [contact that top-level domain](https://www.iana.org/domains/root/db).
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
index dea0d2d6371ecdd..1fd48842270e6c8 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: About multi-signer DNSSEC
-
 ---
 
 Multi-signer DNSSEC consists of two models that allow different authoritative DNS providers to serve the same zone and have DNSSEC enabled at the same time.
@@ -20,7 +19,6 @@ You can [set up multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/) usi
 
 ## How it works
 
-
 :::note
 This is a simplified explanation to give you context and clarify what is involved in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/setup/). For technical details refer to [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html). To read more about DNSSEC, refer to [How DNSSEC works](https://www.cloudflare.com/dns/dnssec/how-dnssec-works/).
 :::
@@ -95,4 +93,4 @@ Multi-signer DNSSEC involves coordinating cryptographic keys across multiple pro
 1. Verify that both providers have each other's ZSKs in their DNSKEY RRsets.
 2. Confirm that both DS records are present at the registrar.
 3. Use DNSSEC validation tools to test resolution from both providers.
-4. Monitor for validation errors during the transition period.
\ No newline at end of file
+4. Monitor for validation errors during the transition period.
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
index 99825944a7ae3ae..b2c476f53cf14a9 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
@@ -173,4 +173,4 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
 
 1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
 
-2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
\ No newline at end of file
+2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
diff --git a/src/content/docs/dns/dnssec/validation-and-key-management.mdx b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
index 83711e5a34916e7..307aec3cbfdc7e4 100644
--- a/src/content/docs/dns/dnssec/validation-and-key-management.mdx
+++ b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
@@ -30,9 +30,9 @@ This is why you cannot simply keep your existing DS record when migrating to Clo
 
 When you enable DNSSEC, Cloudflare automatically publishes **CDS** (Child Delegation Signer) and **CDNSKEY** (Child DNSKEY) records in your zone. These records automate the chain of trust management between your domain and the Top-Level Domain registry.
 
-| Record | Purpose | Contents |
-| --- | --- | --- |
-| **CDS** | High-level instruction | A hashed version of the public key (same data as a DS record) |
+| Record      | Purpose                | Contents                                                                           |
+| ----------- | ---------------------- | ---------------------------------------------------------------------------------- |
+| **CDS**     | High-level instruction | A hashed version of the public key (same data as a DS record)                      |
 | **CDNSKEY** | Public key instruction | The full public Key Signing Key (KSK) for the parent to generate its own DS record |
 
 Registrars that support [RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html) periodically scan your domain for these records and automatically update the DS record at the registry level. This eliminates manual DS record management and ensures seamless key rollovers.
@@ -46,4 +46,4 @@ Not all registrars support automatic CDS/CDNSKEY scanning. If your registrar doe
 ## DNSKEY flags
 
 - **ZSKs (Zone Signing Keys)**: flag `256`
-- **KSKs (Key Signing Keys)**: flag `257`
\ No newline at end of file
+- **KSKs (Key Signing Keys)**: flag `257`
diff --git a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
index 266d6dcc5a7d28d..37222616afae066 100644
--- a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
+++ b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
@@ -6,7 +6,6 @@ products:
 title: DNSSEC keys
 sidebar:
   order: 5
-
 ---
 
 With [Foundation DNS](/dns/foundation-dns/), you can request that the ZSK/KSK pair that is used for [DNSSEC](/dns/dnssec/) is unique to your Cloudflare account. To opt in to this feature, contact your account team.
@@ -17,4 +16,4 @@ All zones within your Cloudflare account - regardless of using [standard](/dns/n
 
 For more background information, refer to [How DNSSEC works](https://www.cloudflare.com/learning/dns/dnssec/how-dnssec-works/).
 
-For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
\ No newline at end of file
+For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
diff --git a/src/content/docs/dns/foundation-dns/index.mdx b/src/content/docs/dns/foundation-dns/index.mdx
index 0c60c2a7c820aca..bb4381b3a49156f 100644
--- a/src/content/docs/dns/foundation-dns/index.mdx
+++ b/src/content/docs/dns/foundation-dns/index.mdx
@@ -6,22 +6,21 @@ products:
 title: Foundation DNS
 sidebar:
   order: 4
-
 ---
 
 Foundation DNS is the Cloudflare DNS offering for enterprise customers.
 
 With Foundation DNS, you get access to increased reliability, security, and insights. Features include the following:
 
-* [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
-  * Strategically distributed IPs to enhance resiliency
-  * Reduced exposure to incidents or software regression
-  * More consistent nameserver assignment
-* [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
-* Additional DNS settings, including:
-  * [Zone defaults](/dns/additional-options/dns-zone-defaults/)
-  * [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
-  * Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
+- [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
+  - Strategically distributed IPs to enhance resiliency
+  - Reduced exposure to incidents or software regression
+  - More consistent nameserver assignment
+- [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
+- Additional DNS settings, including:
+  - [Zone defaults](/dns/additional-options/dns-zone-defaults/)
+  - [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
+  - Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
 
 ## Availability
 
@@ -33,5 +32,5 @@ Both advanced nameservers and unique ZSK/KSK are opt-in configurations. Refer to
 
 ## Related resources
 
-* [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
-* [Product page](https://www.cloudflare.com/dns/foundation-dns/)
+- [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
+- [Product page](https://www.cloudflare.com/dns/foundation-dns/)
diff --git a/src/content/docs/dns/glossary.mdx b/src/content/docs/dns/glossary.mdx
index c7e9390c51ff273..6b99f261ae66987 100644
--- a/src/content/docs/dns/glossary.mdx
+++ b/src/content/docs/dns/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 30
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's DNS documentation.
 
diff --git a/src/content/docs/dns/internal-dns/analytics.mdx b/src/content/docs/dns/internal-dns/analytics.mdx
index af54b9d66ef1e04..b1608c69e81f1a0 100644
--- a/src/content/docs/dns/internal-dns/analytics.mdx
+++ b/src/content/docs/dns/internal-dns/analytics.mdx
@@ -28,4 +28,4 @@ The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to c
 
 Leverage Logpush jobs for [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation.
 
-You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
\ No newline at end of file
+You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
index 115c06fb29de7c0..304c2d379c31eef 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
@@ -6,10 +6,9 @@ products:
 title: Create subdomain records
 sidebar:
   order: 4
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="create-subdomain-record" product="dns" />
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
index bcaca8ad13ed17d..6cfa20495a46cc1 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
@@ -6,24 +6,23 @@ products:
 title: Set up email records
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 There are three reasons to set up email records for your domain:
 
-* To make sure your domain can [receive email](#receive-email).
-* To make sure your domain can [send and receive email](#send-and-receive-email).
-* To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
+- To make sure your domain can [receive email](#receive-email).
+- To make sure your domain can [send and receive email](#send-and-receive-email).
+- To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
 
 The exact values for your DNS mail records depend on your email provider. If you have issues, review the [Troubleshooting](/dns/troubleshooting/email-issues/) and contact your email service provider to confirm your DNS records are correct.
 
-***
+---
 
 <Render file="add-mx-records" product="dns" />
 
-***
+---
 
 ## Prevent domain spoofing
 
@@ -35,4 +34,4 @@ Refer to [Security records](/dmarc-management/security-records/) to learn how to
 
 ## Proxy SMTP traffic
 
-By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
\ No newline at end of file
+By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
diff --git a/src/content/docs/dns/manage-dns-records/how-to/index.mdx b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
index f0d1c4dd9c45127..8ec9e0fc39b8c4d 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
@@ -11,10 +11,9 @@ head:
   - tag: title
     content: DNS records - How to
 description: Learn how to use Cloudflare DNS to manage your DNS records.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following resources for more information about creating and maintaining DNS records:
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
index e8f26982405820e..44177c0cbae3d1a 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
@@ -6,7 +6,6 @@ products:
 title: Dynamically update DNS records
 sidebar:
   order: 13
-
 ---
 
 Most Internet service providers and some hosting providers dynamically update their customer's IP addresses. If this situation applies to you, you need an automated solution to dynamically update your DNS records in Cloudflare.
@@ -17,4 +16,4 @@ Create a script to monitor IP address changes and then have that script push cha
 
 ## ddclient
 
-[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
\ No newline at end of file
+[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
index 9768ac45ceeda63..980e98757c3145e 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
@@ -6,7 +6,6 @@ products:
 title: Round-robin DNS
 sidebar:
   order: 18
-
 ---
 
 To randomly distribute traffic across multiple servers, set up multiple DNS `A` or `AAAA` records for the same hostname.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
index d21e31b5faedd36..886b037b118a29a 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
@@ -7,10 +7,9 @@ source: https://support.cloudflare.com/hc/en-us/articles/360021357131-Delegating
 title: Delegate subdomains
 sidebar:
   order: 20
-
 ---
 
-import { FeatureTable, DashButton, Render } from "~/components"
+import { FeatureTable, DashButton, Render } from "~/components";
 
 Subdomain delegation allows different individuals, teams, or organizations to manage different subdomains of a site.
 
@@ -30,7 +29,7 @@ Cloudflare's CDN and security services are not applied to delegated subdomains.
 
 <FeatureTable id="dns.subdomain_delegation" />
 
-***
+---
 
 ## Delegate a subdomain (outgoing)
 
@@ -43,12 +42,12 @@ To delegate a subdomain such as `blog.example.com`, tell DNS resolvers where to
    <DashButton url="/?to=/:account/:zone/dns/records" />
 
 4. Create `NS` records for the subdomain. For example:
-   * `blog.example.com NS ns1.externalhost.com`
-   * `blog.example.com NS ns2.externalhost.com`
-   * `blog.example.com NS ns3.externalhost.com`
-   :::note
-   The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
-   :::
+   - `blog.example.com NS ns1.externalhost.com`
+   - `blog.example.com NS ns2.externalhost.com`
+   - `blog.example.com NS ns3.externalhost.com`
+     :::note
+     The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
+     :::
 5. (Optional) If the delegated nameserver has DNSSEC enabled, [add the `DS` record](/dns/dnssec/#1-activate-dnssec-in-cloudflare) in Cloudflare.
 
 ### Limits
diff --git a/src/content/docs/dns/manage-dns-records/reference/index.mdx b/src/content/docs/dns/manage-dns-records/reference/index.mdx
index 435c9bbea21f1f9..1bbba02e42aadf2 100644
--- a/src/content/docs/dns/manage-dns-records/reference/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/index.mdx
@@ -11,9 +11,8 @@ head:
   - tag: title
     content: Reference — DNS records
 description: Check information about record types, status and additional options.
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
index 99740688e33b318..67e4399d03b9c75 100644
--- a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: DNS record comments and tags
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 Use DNS record comments and tags to categorize and clarify the purpose of DNS records within Cloudflare.
 
@@ -20,19 +19,17 @@ Comments provide a unique descriptions for specific records, whereas tags group
 
 These attributes are particularly useful when:
 
-* Multiple teams are managing DNS records within the same zone.
-* Your zone contains a large number of DNS records.
-* You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
+- Multiple teams are managing DNS records within the same zone.
+- Your zone contains a large number of DNS records.
+- You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
 
 :::note
 
-
 The information in record attributes will not impact DNS record resolution or propagation timing and is only meant for your private reference. This information is only visible to [members](/fundamentals/manage-members/manage/) of your Cloudflare account and is not visible publicly.
 
-
 :::
 
-***
+---
 
 ## Availability
 
@@ -46,7 +43,7 @@ Comments and tags are only supported for [primary zones (full setup)](/dns/zone-
 
 <FeatureTable id="dns.record_tags" />
 
-***
+---
 
 ## Add or edit record attributes
 
@@ -56,7 +53,7 @@ You can also add or edit attributes by [exporting and re-importing](/dns/manage-
 
 When exporting and importing, special tags starting by `cf-` allow you to control specific Cloudflare configurations. On export, these tags are automatically added to reflect the current configuration for each record on your zone. Refer to [reserved cf- tags](/dns/manage-dns-records/how-to/import-and-export/#reserved-cf--tags) for details.
 
-***
+---
 
 ## Reference
 
diff --git a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
index 41114679b9e211e..3f25313a41b3cd5 100644
--- a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
@@ -6,7 +6,6 @@ products:
 title: Time to Live (TTL)
 sidebar:
   order: 3
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -33,4 +32,4 @@ A TTL of **Auto** is set to 300 seconds (five minutes).
 
 ## Nameserver TTL
 
-[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
\ No newline at end of file
+[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
index 2abc708b8e738ad..4df29d02c4d8f19 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
@@ -29,7 +29,6 @@ When your zone has DNS records that are not proxied, the **DNS Records** page di
 
 `Proxying is required for most security and performance features. Set your DNS records to proxied by clicking "Edit" in the table below, to benefit from DDoS protection, security rules, caching, and more.`
 
-
 Individual DNS records may also display warnings. The specific message depends on whether the record can be proxied.
 
 ---
@@ -51,4 +50,4 @@ When a DNS-only record points to the same origin server as a proxied record, a `
 To mitigate this risk:
 
 - Analyze the impact of hosting multiple services on the same origin server in cases when you cannot avoid having DNS-only records.
-- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
\ No newline at end of file
+- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
index 104ad57575d8b7f..6dc331f5f84f29c 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
@@ -11,11 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS records
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
 
-* [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
+- [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
diff --git a/src/content/docs/dns/nameservers/advanced-nameservers.mdx b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
index 6138cff878b675f..e545226613700b5 100644
--- a/src/content/docs/dns/nameservers/advanced-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
@@ -7,5 +7,4 @@ title: Advanced nameservers
 external_link: /dns/foundation-dns/advanced-nameservers/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
index c9268ed929c445c..d6fd863c76c52cf 100644
--- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
@@ -56,6 +56,7 @@ The next step depends on whether you are using [Cloudflare Registrar](/registrar
 
 - If you are using Cloudflare Registrar for your domain, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to add the custom nameservers and IP addresses as glue records to the domain.
 - If you are not using Cloudflare Registrar for your domain, add the zone custom nameservers at your registrar as your authoritative nameservers and as glue (A and AAAA) records ([RFC 1912](https://www.rfc-editor.org/rfc/rfc1912.html)). If you do not add these records, DNS lookups for your domain will fail.
+
 ### Secondary zones
 
 If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), you can still set up zone custom nameservers. After following the [steps above](/dns/nameservers/custom-nameservers/zone-custom-nameservers/#primary-zones-full-setup) to create zone custom nameservers, do the following:
diff --git a/src/content/docs/dns/private-origins/index.mdx b/src/content/docs/dns/private-origins/index.mdx
index 8398f269855ab93..49be787e2f6008e 100644
--- a/src/content/docs/dns/private-origins/index.mdx
+++ b/src/content/docs/dns/private-origins/index.mdx
@@ -23,7 +23,8 @@ import {
 } from "~/components";
 
 <Description>
-Proxy HTTP/HTTPS traffic from public hostnames to origins in your private network.
+	Proxy HTTP/HTTPS traffic from public hostnames to origins in your private
+	network.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/dns/reference/all-features.mdx b/src/content/docs/dns/reference/all-features.mdx
index 9186a4860de7efa..8ef860d82833097 100644
--- a/src/content/docs/dns/reference/all-features.mdx
+++ b/src/content/docs/dns/reference/all-features.mdx
@@ -7,10 +7,9 @@ sidebar:
   order: 4
 head: []
 description: Review information on all Cloudflare DNS features and their availability.
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
diff --git a/src/content/docs/dns/reference/analytics-mcp-server.mdx b/src/content/docs/dns/reference/analytics-mcp-server.mdx
index de1faf7d51e1b2b..6d120789cebde25 100644
--- a/src/content/docs/dns/reference/analytics-mcp-server.mdx
+++ b/src/content/docs/dns/reference/analytics-mcp-server.mdx
@@ -7,5 +7,4 @@ title: Analytics MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dns-analytics
 sidebar:
   order: 90
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/dns/reference/best-practices.mdx b/src/content/docs/dns/reference/best-practices.mdx
index c4fe1210a6d1a7e..9ef1525a0d2fb08 100644
--- a/src/content/docs/dns/reference/best-practices.mdx
+++ b/src/content/docs/dns/reference/best-practices.mdx
@@ -7,5 +7,4 @@ title: Migrate DNS from BIND
 external_link: /learning-paths/dns-best-practices/concepts/
 sidebar:
   order: 4
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/dns/reference/domain-connect.mdx b/src/content/docs/dns/reference/domain-connect.mdx
index 06e2489b08294a7..fa4d6d8026995b0 100644
--- a/src/content/docs/dns/reference/domain-connect.mdx
+++ b/src/content/docs/dns/reference/domain-connect.mdx
@@ -23,8 +23,8 @@ In practice, this means that when a user that owns `example.com` and has Cloudfl
 
 ### Before you begin
 
-* Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
-* Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
+- Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
+- Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
 
 ### 1. Add templates to the repository
 
@@ -32,12 +32,12 @@ Domain Connect templates are published and maintained on a GitHub repository.
 
 1. Create a fork of the [templates repository](https://github.com/Domain-Connect/Templates).
 2. Add your template. You can create a copy of one of the existing templates and edit it according to your needs.
-   * Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
-	 :::note
-	 Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
-	 :::
-   * If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
-   * You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
+   - Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
+     :::note
+     Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
+     :::
+   - If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
+   - You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
 3. Make sure you follow the naming format defined by Domain Connect: `<providerId>.<serviceId>.json`.
 
 :::note[Tip]
@@ -155,4 +155,4 @@ The most common issues after template onboarding are validation errors, typicall
 
 You can fix these by republishing the signature, using tools such as the one provided by [Domain Connect](https://exampleservice.domainconnect.org/sig). Additionally, you can test signature validation with this [public key debug tool](https://github.com/kerolasa/dc-debug-pubkey).
 
-[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
\ No newline at end of file
+[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
diff --git a/src/content/docs/dns/reference/index.mdx b/src/content/docs/dns/reference/index.mdx
index e12d2e5c169f815..51f81d1b1b3aeac 100644
--- a/src/content/docs/dns/reference/index.mdx
+++ b/src/content/docs/dns/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/reference/recommended-third-party-tools.mdx b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
index 3382d1ddc811487..61e3bd775e91b13 100644
--- a/src/content/docs/dns/reference/recommended-third-party-tools.mdx
+++ b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
@@ -7,15 +7,14 @@ sidebar:
   order: 3
 head: []
 description: List of recommended third-party tools for DNS testing and troubleshooting.
-
 ---
 
 You can use the third-party tools listed below to test and troubleshoot DNS settings.
 
-* [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
+- [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
 
-* [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
+- [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
 
-* [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
+- [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
 
-* [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
+- [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
diff --git a/src/content/docs/dns/troubleshooting/email-issues.mdx b/src/content/docs/dns/troubleshooting/email-issues.mdx
index 417ecfa92fdf7e1..291bb8f2240fef4 100644
--- a/src/content/docs/dns/troubleshooting/email-issues.mdx
+++ b/src/content/docs/dns/troubleshooting/email-issues.mdx
@@ -85,12 +85,12 @@ If you are not sure whether the DNS content itself is correct, compare it with t
 
 Common examples include:
 
-| Provider | MX records | SPF record |
-| --- | --- | --- |
-| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all` |
-| Microsoft 365 | `<your-domain>.mail.protection.outlook.com` (priority `0`) | `v=spf1 include:spf.protection.outlook.com -all` |
-| iCloud Mail | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`) | `v=spf1 include:icloud.com ~all` |
-| Mailgun | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`) | `v=spf1 include:mailgun.org ~all` |
+| Provider         | MX records                                                                                                                                                                           | SPF record                                       |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
+| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all`            |
+| Microsoft 365    | `<your-domain>.mail.protection.outlook.com` (priority `0`)                                                                                                                           | `v=spf1 include:spf.protection.outlook.com -all` |
+| iCloud Mail      | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`)                                                                                                                    | `v=spf1 include:icloud.com ~all`                 |
+| Mailgun          | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`)                                                                                                                              | `v=spf1 include:mailgun.org ~all`                |
 
 Always confirm the exact values with your provider before making changes.
 
diff --git a/src/content/docs/dns/troubleshooting/index.mdx b/src/content/docs/dns/troubleshooting/index.mdx
index 2ad611b0f95694a..b616c9d14356e9f 100644
--- a/src/content/docs/dns/troubleshooting/index.mdx
+++ b/src/content/docs/dns/troubleshooting/index.mdx
@@ -9,8 +9,13 @@ sidebar:
   label: Full resources list
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 The following topics are useful for troubleshooting DNS issues.
 
-<ResourcesBySelector directory="dns" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+<ResourcesBySelector
+	directory="dns"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
index 96a01af7dd298db..1b87486546a0e69 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
@@ -11,7 +11,13 @@ description: >-
   If you initially configured a full setup you can later convert your zone to use incoming zone transfers (Cloudflare as secondary).
 ---
 
-import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 If you initially configured a [primary setup (full)](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/).
 
@@ -37,14 +43,14 @@ Follow the steps below to achieve this conversion.
    <Render file="tsig-definition" product="dns" />
 
    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
-
-   <Render file="tsig-create-dash" product="dns" />
-
-   </TabItem> <TabItem label="API">
-
-   <Render file="tsig-create-api" product="dns" />
-
-   </TabItem> </Tabs>
+   
+      <Render file="tsig-create-dash" product="dns" />
+   
+      </TabItem> <TabItem label="API">
+   
+      <Render file="tsig-create-api" product="dns" />
+   
+      </TabItem> </Tabs>
 
 3. Create a peer server.
 
@@ -58,8 +64,8 @@ Follow the steps below to achieve this conversion.
    <DashButton url="/?to=/:account/:zone/dns/settings" />
 
 3. Select **Manage linked peers** under **DNS Zone Transfers**.
-3. Link the peer server you created in the previous steps and select **Save**.
-4. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
-5. Confirm the DNS records are transferring as expected.
-6. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
-7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
+4. Link the peer server you created in the previous steps and select **Save**.
+5. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
+6. Confirm the DNS records are transferring as expected.
+7. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
+8. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
index f25552f8df2c42b..6c458149ea4d45b 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
@@ -66,7 +66,7 @@ If you are counting on Universal SSL certificates to cover your website or appli
 :::
 
 Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page
- and add the DS record to your registrar.
+and add the DS record to your registrar.
 
 Once all the DNS TTLs expire, all your DNS queries will be answered by the Cloudflare global network.
 
diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx
index 04bc2c37ce4a3a5..42226cfb7ad094d 100644
--- a/src/content/docs/dns/zone-setups/conversions/index.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/index.mdx
@@ -15,4 +15,4 @@ import { DirectoryListing } from "~/components";
 
 You can perform the following DNS setup conversions:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/full-setup/index.mdx b/src/content/docs/dns/zone-setups/full-setup/index.mdx
index 6a5717e76167fdf..f92648b37069542 100644
--- a/src/content/docs/dns/zone-setups/full-setup/index.mdx
+++ b/src/content/docs/dns/zone-setups/full-setup/index.mdx
@@ -19,4 +19,4 @@ For this to work, you must go through a few steps that involve not only Cloudfla
 
 ## Availability
 
-<FeatureTable id="dns.full_setup" />
\ No newline at end of file
+<FeatureTable id="dns.full_setup" />
diff --git a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
index 45952ff6ebee99e..1697f7240a301ac 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: DNS resolution in partial zones
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 When you have a partial zone (<GlossaryTooltip term="CNAME setup" link="/dns/zone-setups/partial-setup/">CNAME setup</GlossaryTooltip>), Cloudflare handles DNS records a bit differently from primary zones (full setup) in order to internally resolve the origin server where proxied HTTP requests are sent to.
 
@@ -62,7 +61,7 @@ When you avoid this situation - meaning you do not have the **target** of the CN
       end
 ```
 
-***
+---
 
 ## Records pointing to a partial zone within the same account
 
@@ -115,4 +114,4 @@ If such setup is in place, the subdomain (`www.partialzone.com` in this example)
       subgraph Authoritative DNS
       C
       end
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
index 0afa82eb5bc7ecb..627350007665712 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
@@ -13,7 +13,15 @@ description: >-
   A CNAME setup (also known as partial) allows you to use Cloudflare's reverse proxy while maintaining your primary and authoritative DNS provider.
 ---
 
-import { Details, Render, GlossaryTooltip, Steps, Tabs, TabItem, APIRequest } from "~/components";
+import {
+	Details,
+	Render,
+	GlossaryTooltip,
+	Steps,
+	Tabs,
+	TabItem,
+	APIRequest,
+} from "~/components";
 
 <Render file="partial-setup-definition" product="dns" />
 
@@ -40,7 +48,6 @@ A CNAME setup (partial) is only available to customers on a Business or Enterpri
 
 ## 1. Convert your zone and review DNS records
 
-
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 :::caution[Make sure you have the correct plan]
diff --git a/src/content/docs/dns/zone-setups/reference/domain-status.mdx b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
index 2d26b5684dba1b2..9541eaa1de5c4f2 100644
--- a/src/content/docs/dns/zone-setups/reference/domain-status.mdx
+++ b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
@@ -69,11 +69,11 @@ After you add your domain, Cloudflare performs checks on a schedule to confirm y
 
 The activation check behavior depends on your zone setup:
 
-| Zone setup                                                                                                                                                                                                                          | Activation requirement                                                                                                                            |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                           | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)      | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.         |
-| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                             | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                     |
+| Zone setup                                                                                                                                                                                                                      | Activation requirement                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                      | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/) | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.           |
+| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                        | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                       |
 
 ### Expected behavior for different plans
 
diff --git a/src/content/docs/dns/zone-setups/reference/index.mdx b/src/content/docs/dns/zone-setups/reference/index.mdx
index a6c71ff65f2b7a8..6185d7acd7149ea 100644
--- a/src/content/docs/dns/zone-setups/reference/index.mdx
+++ b/src/content/docs/dns/zone-setups/reference/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Reference — DNS zone setups
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
index 58cb7e6b8986b33..363f7e2bbee2c84 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Migrate subdomain to a new account
-
 ---
 
 When using a [subdomain setup](/dns/zone-setups/subdomain-setup/), you can have your subdomain as a separate zone within the same account as the parent domain or within a different account.
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
index 7523187ca70b247..1a8c8cfae71d112 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
@@ -9,15 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Rollback subdomain setup
-
 ---
 
 Refer to the following process to understand how you can rollback a [subdomain setup](/dns/zone-setups/subdomain-setup/) and recreate the corresponding subdomain DNS records in an existing parent zone within Cloudflare.
 
 ## Before you begin
 
-* This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
-* In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
+- This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
+- In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
 
 :::caution[Important]
 
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
index ed7910947587eae..8cbfcf5e76c38b0 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
@@ -9,17 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on full setup
-
 ---
 
 When the parent zone is using a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
 :::note
 
-
 The following steps are similar if your Cloudflare parent zone is in a secondary setup, with the only difference that you will use your external primary DNS provider to make any necessary adjustments to DNS records.
 
-
 :::
 
 ## Subdomain does not exist
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
index 46a0cf3ae1e1d99..0ae18341ccfb5ac 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on partial setup
-
 ---
 
-import { Details, TabItem, Tabs } from "~/components"
+import { Details, TabItem, Tabs } from "~/components";
 
 When the parent zone is using a [CNAME setup (partial)](/dns/zone-setups/partial-setup/)[^2], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
diff --git a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
index d7b45d34cc6ea33..485e9d9090a0bfb 100644
--- a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
+++ b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS setups
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
index ee6a63ef200265e..6c1cdba3b2785b7 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
@@ -17,7 +17,7 @@ When you [make edits](/dns/manage-dns-records/how-to/create-dns-records/) to Clo
 
 ## How to
 
-* [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
+- [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
index 854dcfad6b2831a..284707a6b0416f1 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
@@ -10,7 +10,6 @@ sidebar:
 
 Consider the sections below to understand the expected behaviors, depending on DNS record type and proxied status.
 
-
 ## Proxied records
 
 For each [proxied DNS record](/dns/proxy-status/) in your zone, Cloudflare will transfer out two `A` and two `AAAA` records.
@@ -42,4 +41,4 @@ The following records are not transferred out when you use Cloudflare as primary
 
 :::note
 Proxied Load Balancing records are transferred as explained in [Proxied records](#proxied-records).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
index bfd1df6c824f6a5..f5191d5c420f6ce 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Secondary DNS
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your secondary DNS.
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
index 463cb6408c5cbb2..2bb69c6bc3e6288 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
@@ -23,8 +23,8 @@ B & C <--DNS lookups--> D[Resolver] <--DNS lookups--> E((User))
 
 ## How to
 
-* [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
-* Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
+- [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
+- Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
index a21202b1749130a..b8a0e6712109252 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
@@ -81,4 +81,4 @@ Once you create a CNAME record at the apex, existing A or AAAA records on the zo
 
 ## Verify that your records are proxied
 
-Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
\ No newline at end of file
+Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
diff --git a/src/content/docs/durable-objects/api/alarms.mdx b/src/content/docs/durable-objects/api/alarms.mdx
index 4d576fbe8cd6cb3..fa9a03af7538bea 100644
--- a/src/content/docs/durable-objects/api/alarms.mdx
+++ b/src/content/docs/durable-objects/api/alarms.mdx
@@ -38,42 +38,42 @@ Although each Durable Object can only have one alarm set at a time, you can mana
 import { DurableObject } from "cloudflare:workers";
 
 export class AgentServer extends DurableObject {
-  // Schedule a one-time or recurring event
-  async scheduleEvent(id, runAt, repeatMs = null) {
-    await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
-    const currentAlarm = await this.ctx.storage.getAlarm();
-    if (!currentAlarm || runAt < currentAlarm) {
-      await this.ctx.storage.setAlarm(runAt);
-    }
-  }
-
-  async alarm() {
-    const now = Date.now();
-    const events = await this.ctx.storage.list({ prefix: "event:" });
-    let nextAlarm = null;
-
-    for (const [key, event] of events) {
-      if (event.runAt <= now) {
-        await this.processEvent(event);
-        if (event.repeatMs) {
-          event.runAt = now + event.repeatMs;
-          await this.ctx.storage.put(key, event);
-        } else {
-          await this.ctx.storage.delete(key);
-        }
-      }
-      // Track the next event time
-      if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
-        nextAlarm = event.runAt;
-      }
-    }
-
-    if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
-  }
-
-  async processEvent(event) {
-    // Your event handling logic here
-  }
+	// Schedule a one-time or recurring event
+	async scheduleEvent(id, runAt, repeatMs = null) {
+		await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
+		const currentAlarm = await this.ctx.storage.getAlarm();
+		if (!currentAlarm || runAt < currentAlarm) {
+			await this.ctx.storage.setAlarm(runAt);
+		}
+	}
+
+	async alarm() {
+		const now = Date.now();
+		const events = await this.ctx.storage.list({ prefix: "event:" });
+		let nextAlarm = null;
+
+		for (const [key, event] of events) {
+			if (event.runAt <= now) {
+				await this.processEvent(event);
+				if (event.repeatMs) {
+					event.runAt = now + event.repeatMs;
+					await this.ctx.storage.put(key, event);
+				} else {
+					await this.ctx.storage.delete(key);
+				}
+			}
+			// Track the next event time
+			if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
+				nextAlarm = event.runAt;
+			}
+		}
+
+		if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
+	}
+
+	async processEvent(event) {
+		// Your event handling logic here
+	}
 }
 ```
 
@@ -82,7 +82,6 @@ export class AgentServer extends DurableObject {
 ### `getAlarm`
 
 - <code>getAlarm()</code>: <Type text="number | null" />
-
   - If there is an alarm set, then return the currently set alarm time as the number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
   - If `getAlarm` is called while an [`alarm`](/durable-objects/api/alarms/#alarm) is already running, it returns `null` unless `setAlarm` has also been called since the alarm handler started running.
@@ -90,7 +89,6 @@ export class AgentServer extends DurableObject {
 ### `setAlarm`
 
 - <code> setAlarm(scheduledTimeMs <Type text="number" />) </code>: <Type text="void" />
-
   - Set the time for the alarm to run. Specify the time as the number of milliseconds elapsed since the UNIX epoch.
   - If you call `setAlarm` when there is already one scheduled, it will override the existing alarm.
 
@@ -103,7 +101,6 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `deleteAlarm`
 
 - `deleteAlarm()`: <Type text='void' />
-
   - Unset the alarm if there is a currently set alarm.
 
   - Calling `deleteAlarm()` inside the `alarm()` handler may prevent retries on a best-effort basis, but is not guaranteed.
@@ -113,11 +110,9 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `alarm`
 
 - <code>alarm(alarmInfo <Type text="Object" />)</code>: <Type text="void" />
-
   - Called by the system when a scheduled alarm time is reached.
 
   - The optional parameter `alarmInfo` object has two properties:
-
     - `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
     - `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
 
diff --git a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
index 541d4b55aeebebd..c41b19cc99bc69c 100644
--- a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
@@ -8,7 +8,16 @@ products:
   - durable-objects
 ---
 
-import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	GlossaryTooltip,
+	TypeScriptExample,
+	Details,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 :::note
 This page documents the storage API for legacy KV-backed Durable Objects.
@@ -83,6 +92,6 @@ KV-backed Durable Objects provide KV API methods which are asynchronous.
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
index 2e6c605ca634618..70afb0cebace527 100644
--- a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
@@ -8,7 +8,16 @@ products:
   - durable-objects
 ---
 
-import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	GlossaryTooltip,
+	TypeScriptExample,
+	Details,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 :::note
 This page documents the storage API for the newer SQLite-backed Durable Objects.
@@ -136,7 +145,11 @@ class MyDurableObject(DurableObject):
 - When writing data, every row update of an index counts as an additional row. However, indexes may be beneficial for read-heavy use cases. Refer to [Index for SQLite Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#indexes-in-sqlite).
 - Writing data to [SQLite virtual tables](https://www.sqlite.org/vtab.html) also counts towards rows written.
 
-<Render file="d1-do-supported-sqlite-extensions" product="d1" params={{ product: "Durable Objects support" }}/>
+<Render
+	file="d1-do-supported-sqlite-extensions"
+	product="d1"
+	params={{ product: "Durable Objects support" }}
+/>
 
 ### `exec`
 
@@ -161,7 +174,10 @@ Always consume the cursor fully before yielding the event loop. Call `.toArray()
 ```ts
 // ✅ Safe: cursor is fully consumed before any await
 const rows = this.ctx.storage.sql.exec("SELECT * FROM users").toArray();
-const result = await fetch("https://example.com", { method: "POST", body: JSON.stringify(rows) });
+const result = await fetch("https://example.com", {
+	method: "POST",
+	body: JSON.stringify(rows),
+});
 ```
 
 ```ts
@@ -351,6 +367,6 @@ ctx.storage.onNextSessionRestoreBookmark(bookmark)
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
index cbcc52ad9c8be68..28b40fdda357f9f 100644
--- a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
+++ b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
@@ -11,10 +11,13 @@ products:
 import { Render, GlossaryTooltip, WranglerConfig } from "~/components";
 
 <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> are a
+
 powerful compute API that provides a compute with storage building block. Each
 Durable Object has its own private, transactional, and strongly consistent
 storage. Durable Objects
+
 <GlossaryTooltip term="Storage API">Storage API</GlossaryTooltip> provides
+
 access to a Durable Object's attached storage.
 
 A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
diff --git a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
index 1f90f81aa40a253..163f0a7cc9d2cb5 100644
--- a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
+++ b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
@@ -82,7 +82,7 @@ Durable Objects will occasionally shut down and objects are restarted, which wil
 
 When a Durable Object is shut down, the object instance is automatically restarted and new requests are routed to the new instance. In-flight requests are handled as follows:
 
-- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage.  If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
+- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage. If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
 - **WebSocket connections**: WebSocket requests are terminated automatically during shutdown. This is so that the new instance can take over the connection as soon as possible.
 - **Other invocations (email, cron)**: Other invocations are treated similarly to HTTP requests.
 
diff --git a/src/content/docs/durable-objects/examples/agents.mdx b/src/content/docs/durable-objects/examples/agents.mdx
index 0a633feca9fcda1..822795f49b71103 100644
--- a/src/content/docs/durable-objects/examples/agents.mdx
+++ b/src/content/docs/durable-objects/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - durable-objects
----
\ No newline at end of file
+---
diff --git a/src/content/docs/durable-objects/examples/index.mdx b/src/content/docs/durable-objects/examples/index.mdx
index a885b12632c278f..3c4df69e31c31d3 100644
--- a/src/content/docs/durable-objects/examples/index.mdx
+++ b/src/content/docs/durable-objects/examples/index.mdx
@@ -14,4 +14,7 @@ import { ResourcesBySelector, GlossaryTooltip } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Durable Objects.
 
-<ResourcesBySelector types={["example"]} directory="durable-objects/examples/" />
+<ResourcesBySelector
+	types={["example"]}
+	directory="durable-objects/examples/"
+/>
diff --git a/src/content/docs/durable-objects/examples/websocket-server.mdx b/src/content/docs/durable-objects/examples/websocket-server.mdx
index 6c9fed4be7d126e..24b3a890045da9a 100644
--- a/src/content/docs/durable-objects/examples/websocket-server.mdx
+++ b/src/content/docs/durable-objects/examples/websocket-server.mdx
@@ -12,7 +12,13 @@ products:
   - durable-objects
 ---
 
-import { TabItem, Tabs, GlossaryTooltip, WranglerConfig, TypeScriptExample } from "~/components";
+import {
+	TabItem,
+	Tabs,
+	GlossaryTooltip,
+	WranglerConfig,
+	TypeScriptExample,
+} from "~/components";
 
 This example shows how to build a WebSocket server using <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> and Workers. The example exposes an endpoint to create a new WebSocket connection. This WebSocket connection echos any message while including the total number of WebSocket connections currently established. For more information, refer to [Use Durable Objects with WebSockets](/durable-objects/best-practices/websockets/).
 
diff --git a/src/content/docs/durable-objects/observability/data-studio.mdx b/src/content/docs/durable-objects/observability/data-studio.mdx
index 847423a93b479a1..39fe7cf43e104b3 100644
--- a/src/content/docs/durable-objects/observability/data-studio.mdx
+++ b/src/content/docs/durable-objects/observability/data-studio.mdx
@@ -40,4 +40,4 @@ You need to have at least the `Workers Platform Admin` [role](/fundamentals/mana
 
 All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/) for your security and compliance needs.
 
-- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
\ No newline at end of file
+- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
diff --git a/src/content/docs/durable-objects/platform/known-issues.mdx b/src/content/docs/durable-objects/platform/known-issues.mdx
index a590711f8bcb13e..8d63e009732811e 100644
--- a/src/content/docs/durable-objects/platform/known-issues.mdx
+++ b/src/content/docs/durable-objects/platform/known-issues.mdx
@@ -38,4 +38,4 @@ The Workers editor in the [Cloudflare dashboard](https://dash.cloudflare.com/) a
 
 Currently, when developing locally (using `npx wrangler dev`), Durable Object [alarm methods](/durable-objects/api/alarms) may fail after a hot reload (if you edit the code while the code is running locally).
 
-To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
\ No newline at end of file
+To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx
index ef53c2fd80d3d9c..26f4a596ac0219e 100644
--- a/src/content/docs/durable-objects/platform/limits.mdx
+++ b/src/content/docs/durable-objects/platform/limits.mdx
@@ -77,4 +77,3 @@ For Durable Object classes with [SQLite storage](/durable-objects/api/sqlite-sto
 <Render file="do-faq-limits" product="durable-objects" />
 
 <Render file="wall-time-limits" product="workers" />
-
diff --git a/src/content/docs/durable-objects/reference/data-location.mdx b/src/content/docs/durable-objects/reference/data-location.mdx
index 4f4ced530d3685f..9465de9ade8d4de 100644
--- a/src/content/docs/durable-objects/reference/data-location.mdx
+++ b/src/content/docs/durable-objects/reference/data-location.mdx
@@ -58,9 +58,9 @@ Note that it is also possible to specify a jurisdiction by creating an individua
 
 ### Supported locations
 
-| Parameter | Location                     |
-| --------- | ---------------------------- |
-| eu        | The European Union           |
+| Parameter | Location                       |
+| --------- | ------------------------------ |
+| eu        | The European Union             |
 | fedramp   | FedRAMP-compliant data centers |
 
 ## Provide a location hint
@@ -102,10 +102,14 @@ Hints are a best effort and not a guarantee. Unlike with jurisdictions, Durable
 | afr       | Africa <sup>2</sup>        |
 | me        | Middle East <sup>2</sup>   |
 
-<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the future.
+<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the
+future.
 
-<sup>2</sup> Durable Objects currently do not spawn in this location. Instead, the Durable Object will spawn in a nearby location which does support Durable Objects. For example, Durable Objects hinted to South America spawn in Eastern North America instead.
+<sup>2</sup> Durable Objects currently do not spawn in this location. Instead,
+the Durable Object will spawn in a nearby location which does support Durable
+Objects. For example, Durable Objects hinted to South America spawn in Eastern
+North America instead.
 
 ## Additional resources
 
-- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
\ No newline at end of file
+- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
diff --git a/src/content/docs/durable-objects/reference/data-security.mdx b/src/content/docs/durable-objects/reference/data-security.mdx
index e91b874429d9483..d410809c1239ec7 100644
--- a/src/content/docs/durable-objects/reference/data-security.mdx
+++ b/src/content/docs/durable-objects/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of Durable Objects, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/durable-objects/reference/environments.mdx b/src/content/docs/durable-objects/reference/environments.mdx
index 21a1b30c3e2981f..ac38518bf59f293 100644
--- a/src/content/docs/durable-objects/reference/environments.mdx
+++ b/src/content/docs/durable-objects/reference/environments.mdx
@@ -43,8 +43,6 @@ Durable Object bindings are not inherited. For example, you can define an enviro
 
 Because Wrangler appends the [environment name](/workers/wrangler/environments/) to the top-level name when publishing, for a Worker named `worker-name` the above example is equivalent to:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -71,8 +69,6 @@ Because Wrangler appends the [environment name](/workers/wrangler/environments/)
 
 If you want an environment-specific binding that accesses the same Objects as the top-level binding, specify the top-level Worker code name explicitly using `script_name`:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -118,9 +114,10 @@ To start remote development:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select an existing Worker.
 3. Select the **Edit code** icon located on the upper-right of the screen.
 
 :::caution
 Remote development is only available for KV-backed Durable Objects. SQLite-backed Durable Objects do not support remote development.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/durable-objects/reference/faq.mdx b/src/content/docs/durable-objects/reference/faq.mdx
index 2cff6f2d62e279c..84262a5b52de7b9 100644
--- a/src/content/docs/durable-objects/reference/faq.mdx
+++ b/src/content/docs/durable-objects/reference/faq.mdx
@@ -12,12 +12,12 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="do-faq-pricing" product="durable-objects"/>
+<Render file="do-faq-pricing" product="durable-objects" />
 
 ## Limits
 
-<Render file="do-faq-limits" product="durable-objects"/>
+<Render file="do-faq-limits" product="durable-objects" />
 
 ## Metrics and analytics
 
-<Render file="do-faq-metrics-and-analytics" product="durable-objects"/>
\ No newline at end of file
+<Render file="do-faq-metrics-and-analytics" product="durable-objects" />
diff --git a/src/content/docs/durable-objects/reference/glossary.mdx b/src/content/docs/durable-objects/reference/glossary.mdx
index b95a0d5b0e6b08d..1e9b3d062d8832e 100644
--- a/src/content/docs/durable-objects/reference/glossary.mdx
+++ b/src/content/docs/durable-objects/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - durable-objects
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Durable Objects documentation.
 
diff --git a/src/content/docs/durable-objects/reference/in-memory-state.mdx b/src/content/docs/durable-objects/reference/in-memory-state.mdx
index 772169b848b90bd..7ef26232dd22b2b 100644
--- a/src/content/docs/durable-objects/reference/in-memory-state.mdx
+++ b/src/content/docs/durable-objects/reference/in-memory-state.mdx
@@ -20,21 +20,21 @@ A common pattern is to initialize a Durable Object from [persistent storage](/du
 import { DurableObject } from "cloudflare:workers";
 
 export class Counter extends DurableObject {
-  constructor(ctx, env) {
-    super(ctx, env);
-    // `blockConcurrencyWhile()` ensures no requests are delivered until
-    // initialization completes.
-    this.ctx.blockConcurrencyWhile(async () => {
-      let stored = await this.ctx.storage.get("value");
-      // After initialization, future reads do not need to access storage.
-      this.value = stored || 0;
-    });
-  }
-
-  // Handle HTTP requests from clients.
-  async fetch(request) {
-    // use this.value rather than storage
-  }
+	constructor(ctx, env) {
+		super(ctx, env);
+		// `blockConcurrencyWhile()` ensures no requests are delivered until
+		// initialization completes.
+		this.ctx.blockConcurrencyWhile(async () => {
+			let stored = await this.ctx.storage.get("value");
+			// After initialization, future reads do not need to access storage.
+			this.value = stored || 0;
+		});
+	}
+
+	// Handle HTTP requests from clients.
+	async fetch(request) {
+		// use this.value rather than storage
+	}
 }
 ```
 
diff --git a/src/content/docs/durable-objects/video-tutorials.mdx b/src/content/docs/durable-objects/video-tutorials.mdx
index 4af3068247492a4..4390949faf52bc7 100644
--- a/src/content/docs/durable-objects/video-tutorials.mdx
+++ b/src/content/docs/durable-objects/video-tutorials.mdx
@@ -11,11 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Introduction to Durable Objects"
-        description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
-        href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
-    />
+	<LinkCard
+		title="Introduction to Durable Objects"
+		description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
+		href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
+	/>
 </CardGrid>
-
-
diff --git a/src/content/docs/dynamic-workers/usage/bindings.mdx b/src/content/docs/dynamic-workers/usage/bindings.mdx
index 5fed51bc8b0efe7..2970ac1c09b9962 100644
--- a/src/content/docs/dynamic-workers/usage/bindings.mdx
+++ b/src/content/docs/dynamic-workers/usage/bindings.mdx
@@ -10,7 +10,7 @@ products:
 
 import { WranglerConfig } from "~/components";
 
-Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use. 
+Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use.
 
 This allows you to:
 
@@ -21,7 +21,8 @@ This allows you to:
 ## Custom Bindings with Dynamic Workers
 
 With custom bindings, you:
-- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer. 
+
+- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer.
 - **Pass it to the Dynamic Worker as a binding**: It just calls methods like `this.env.CHAT_ROOM.post("Hello!")` without knowing anything about the implementation behind it.
 
 ### How it works
@@ -29,54 +30,65 @@ With custom bindings, you:
 #### Step 1: Define the binding
 
 To create a custom binding, your loader Worker needs to implement a [`WorkerEntrypoint` class](/workers/runtime-apis/bindings/service-bindings/rpc#the-workerentrypoint-class) and export it. The methods you define on this class are the methods the Dynamic Worker will be able to call.
+
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint {
-  async post(text: string): Promise<void> {
-    // Your implementation here
-  }
+	async post(text: string): Promise<void> {
+		// Your implementation here
+	}
 }
 ```
+
 #### Step 2: Pass it to the Dynamic Worker
-Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`. 
+
+Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`.
 
 ```ts
 let chatRoom = ctx.exports.ChatRoom({ props: { roomName: "#bot-chat" } });
 
 let worker = env.LOADER.load({
-  env: { CHAT_ROOM: chatRoom },
-  // ...
+	env: { CHAT_ROOM: chatRoom },
+	// ...
 });
 ```
 
-From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call: 
+From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call:
+
 ```ts
 // Inside the Dynamic Worker
 await this.env.CHAT_ROOM.post("Hello!");
 ```
+
 #### Step 3: Customize per user with props
-One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user. 
+
+One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user.
 
 ```ts
 // Same class, different props per user
-let aliceRoom = ctx.exports.ChatRoom({ props: { roomName: "#alice", apiKey: ALICE_KEY } });
-let bobRoom   = ctx.exports.ChatRoom({ props: { roomName: "#bob", apiKey: BOB_KEY } });
+let aliceRoom = ctx.exports.ChatRoom({
+	props: { roomName: "#alice", apiKey: ALICE_KEY },
+});
+let bobRoom = ctx.exports.ChatRoom({
+	props: { roomName: "#bob", apiKey: BOB_KEY },
+});
 ```
 
 When the Dynamic Worker calls a method on the binding, it's actually making a call back to your loader Worker, that's where the method runs. Inside that method, you can read the `props` via [`this.ctx.props`](/workers/runtime-apis/context#props). Only the loader Worker has access to the props, the Dynamic Worker never sees them.
 
 ```ts
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-  async post(text: string): Promise<void> {
-    // Props are set when the stub is created — the Dynamic Worker never sees them
-    let roomName = this.ctx.props.roomName;
-    await postToChat(roomName, text);
-  }
+	async post(text: string): Promise<void> {
+		// Props are set when the stub is created — the Dynamic Worker never sees them
+		let roomName = this.ctx.props.roomName;
+		await postToChat(roomName, text);
+	}
 }
 ```
 
 ### Example: Chat room agent
+
 Here's a complete example putting it all together. Say you're building a platform where AI agents can post to chat rooms. Each agent should only be able to post to its assigned room and it should never see the API key used to authenticate.
 
 You define a `ChatRoom` class in your parent Worker. This class has a `post` method, the only method the Dynamic Worker can call on this binding. Inside this class, you control which room the message goes to, which API key is used, and what name is attached to the message.
@@ -85,44 +97,46 @@ You define a `ChatRoom` class in your parent Worker. This class has a `post` met
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-  async post(text: string): Promise<void> {
-    let { apiKey, botName, roomName } = this.ctx.props;
+	async post(text: string): Promise<void> {
+		let { apiKey, botName, roomName } = this.ctx.props;
 
-    // Prefix the message with the bot's name.
-    text = `[${botName}]: ${text}`;
+		// Prefix the message with the bot's name.
+		text = `[${botName}]: ${text}`;
 
-    // Send it to the chat service.
-    await postToChat(apiKey, roomName, text);
-  }
+		// Send it to the chat service.
+		await postToChat(apiKey, roomName, text);
+	}
 }
 
 type ChatRoomProps = {
-  apiKey: string;
-  roomName: string;
-  botName: string;
+	apiKey: string;
+	roomName: string;
+	botName: string;
 };
 ```
+
 You export one `ChatRoom` class, but each stub you create can have different `props` — a different room name, a different API key, a different bot name. The `props` are set when you create the stub, and the Dynamic Worker never sees them.
 
 Now pass it to a Dynamic Worker:
+
 ```ts
 // Create a stub scoped to a specific room.
 let chatRoom = ctx.exports.ChatRoom({
-  props: {
-    apiKey,
-    roomName: "#bot-chat",
-    botName: "Robo",
-  },
+	props: {
+		apiKey,
+		roomName: "#bot-chat",
+		botName: "Robo",
+	},
 });
 
 let worker = env.LOADER.load({
-  env: {
-    CHAT_ROOM: chatRoom,
-  },
-  compatibilityDate: "$today",
-  mainModule: "index.js",
-  modules: {
-    "index.js": `
+	env: {
+		CHAT_ROOM: chatRoom,
+	},
+	compatibilityDate: "$today",
+	mainModule: "index.js",
+	modules: {
+		"index.js": `
       export class Agent extends WorkerEntrypoint {
         async run() {
           // This is all the Dynamic Worker sees.
@@ -130,13 +144,14 @@ let worker = env.LOADER.load({
         }
       }
     `,
-  },
-  globalOutbound: null,
+	},
+	globalOutbound: null,
 });
 
 return worker.getEntrypoint("Agent").run();
 ```
-The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages. 
+
+The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages.
 
 ### Tip: Tell your agent about the types
 
@@ -146,45 +161,52 @@ Make sure your `WorkerEntrypoint` class extends the TypeScript type so the decla
 
 ## Passing normal Workers bindings
 
-To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose. 
+To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose.
 
 ### Example: Scoping a KV namespace per customer
 
 First, bind the KV namespace to your loader Worker. Then in your loader Worker, export a class that uses the KV binding and defines the methods Dynamic Workers can call:
+
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
-export class MyStorage extends WorkerEntrypoint<Cloudflare.Env, MyStorageProps> {
-  // Export this class from your loader Worker
-  // The Dynamic Worker will be able to call get() and put()
-  async get(key: string): Promise<string | null> {
-    // Prefix the key so this customer can only access their own data
-    return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
-  }
-
-  async put(key: string, value: string): Promise<void> {
-    await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
-  }
+export class MyStorage extends WorkerEntrypoint<
+	Cloudflare.Env,
+	MyStorageProps
+> {
+	// Export this class from your loader Worker
+	// The Dynamic Worker will be able to call get() and put()
+	async get(key: string): Promise<string | null> {
+		// Prefix the key so this customer can only access their own data
+		return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
+	}
+
+	async put(key: string, value: string): Promise<void> {
+		await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
+	}
 }
 
 type MyStorageProps = {
-  prefix: string;
+	prefix: string;
 };
 ```
+
 Then pass it to the Dynamic Worker with a customer-specific prefix:
+
 ```ts
 // Create a stub scoped to this customer's prefix
 let storage = ctx.exports.MyStorage({
-  props: { prefix: `customer-${customerId}` },
+	props: { prefix: `customer-${customerId}` },
 });
 
 let worker = env.LOADER.load({
-  env: { STORAGE: storage },
-  // ...
+	env: { STORAGE: storage },
+	// ...
 });
 ```
 
 The Dynamic Worker just uses it like any other binding:
+
 ```ts
 // Inside the Dynamic Worker, it just sees STORAGE with get and put
 let value = await this.env.STORAGE.get("settings");
@@ -197,7 +219,7 @@ For persistent storage that lives with each Dynamic Worker, see [Durable Object
 
 ## Capability-based Sandboxing
 
-Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it.  If it hasn't received a stub for something, it can't access it. 
+Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it. If it hasn't received a stub for something, it can't access it.
 
 This is powered by Workers RPC, also known as [Cap'n Web](https://github.com/cloudflare/capnweb), an RPC system designed to pass object references across security boundaries. When a Dynamic Worker receives a stub, it can call that object's methods and each call is an RPC back to the original object in your loader Worker. Stubs have no global identifier and cannot be forged, the only way to obtain one is to receive it.
 
diff --git a/src/content/docs/email-routing/email-workers/local-development.mdx b/src/content/docs/email-routing/email-workers/local-development.mdx
index 7764c919d997f0d..ab7767665ecebf0 100644
--- a/src/content/docs/email-routing/email-workers/local-development.mdx
+++ b/src/content/docs/email-routing/email-workers/local-development.mdx
@@ -41,7 +41,7 @@ You can now test receiving, replying, and sending emails in your local environme
 Consider this example Email Worker script that uses the open source [`postal-mime`](https://www.npmjs.com/package/postal-mime) email parser:
 
 ```ts
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
 	async email(message, env, ctx) {
@@ -79,31 +79,31 @@ This is what you get in the console:
 
 ```json
 {
-  headers: [
-    {
-      key: 'received',
-      value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
-    },
-    { key: 'from', value: '"John" <sender@example.com>' },
-    { key: 'reply-to', value: 'sender@example.com' },
-    { key: 'to', value: 'recipient@example.com' },
-    { key: 'subject', value: 'Testing Email Workers Local Dev' },
-    { key: 'content-type', value: 'text/html; charset="windows-1252"' },
-    { key: 'x-mailer', value: 'Curl' },
-    { key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
-    {
-      key: 'message-id',
-      value: '<6114391943504294873000@ZSH-GHOSTTY>'
-    }
-  ],
-  from: { address: 'sender@example.com', name: 'John' },
-  to: [ { address: 'recipient@example.com', name: '' } ],
-  replyTo: [ { address: 'sender@example.com', name: '' } ],
-  subject: 'Testing Email Workers Local Dev',
-  messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
-  date: '2024-08-27T15:49:44.000Z',
-  html: 'Hi there\n',
-  attachments: []
+	"headers": [
+		{
+			"key": "received",
+			"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
+		},
+		{ "key": "from", "value": "\"John\" <sender@example.com>" },
+		{ "key": "reply-to", "value": "sender@example.com" },
+		{ "key": "to", "value": "recipient@example.com" },
+		{ "key": "subject", "value": "Testing Email Workers Local Dev" },
+		{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
+		{ "key": "x-mailer", "value": "Curl" },
+		{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
+		{
+			"key": "message-id",
+			"value": "<6114391943504294873000@ZSH-GHOSTTY>"
+		}
+	],
+	"from": { "address": "sender@example.com", "name": "John" },
+	"to": [{ "address": "recipient@example.com", "name": "" }],
+	"replyTo": [{ "address": "sender@example.com", "name": "" }],
+	"subject": "Testing Email Workers Local Dev",
+	"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
+	"date": "2024-08-27T15:49:44.000Z",
+	"html": "Hi there\n",
+	"attachments": []
 }
 ```
 
@@ -113,23 +113,27 @@ Wrangler can also simulate sending emails locally. Consider this example Email W
 
 ```ts
 import { EmailMessage } from "cloudflare:email";
-import { createMimeMessage } from 'mimetext';
+import { createMimeMessage } from "mimetext";
 
 export default {
 	async fetch(request, env, ctx) {
 		const msg = createMimeMessage();
-		msg.setSender({ name: 'Sending email test', addr: 'sender@example.com' });
-		msg.setRecipient('recipient@example.com');
-		msg.setSubject('An email generated in a worker');
+		msg.setSender({ name: "Sending email test", addr: "sender@example.com" });
+		msg.setRecipient("recipient@example.com");
+		msg.setSubject("An email generated in a worker");
 		msg.addMessage({
-			contentType: 'text/plain',
+			contentType: "text/plain",
 			data: `Congratulations, you just sent an email from a worker.`,
 		});
 
-		var message = new EmailMessage('sender@example.com', 'recipient@example.com', msg.asRaw());
+		var message = new EmailMessage(
+			"sender@example.com",
+			"recipient@example.com",
+			msg.asRaw(),
+		);
 		await env.EMAIL.send(message);
 		return Response.json({ ok: true });
-	}
+	},
 };
 ```
 
@@ -163,9 +167,9 @@ Congratulations, you just sent an email from a worker.
 Likewise, [`EmailMessage`](/email-routing/email-workers/runtime-api/#emailmessage-definition)'s `forward()` and `reply()` methods are also simulated locally. Consider this Worker that receives an email, parses it, replies to the sender, and forwards the original message to one your verified recipient addresses:
 
 ```ts
-import * as PostalMime from 'postal-mime';
-import { createMimeMessage } from 'mimetext';
-import { EmailMessage } from 'cloudflare:email';
+import * as PostalMime from "postal-mime";
+import { createMimeMessage } from "mimetext";
+import { EmailMessage } from "cloudflare:email";
 
 export default {
 	async email(message, env: any, ctx: any) {
@@ -179,16 +183,23 @@ export default {
 
 		// creates reply message
 		const msg = createMimeMessage();
-		msg.setSender({ name: 'Thank you for your contact', addr: 'sender@example.com' });
+		msg.setSender({
+			name: "Thank you for your contact",
+			addr: "sender@example.com",
+		});
 		msg.setRecipient(message.from);
-		msg.setHeader('In-Reply-To', message.headers.get('Message-ID'));
-		msg.setSubject('An email generated in a worker');
+		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+		msg.setSubject("An email generated in a worker");
 		msg.addMessage({
-			contentType: 'text/plain',
+			contentType: "text/plain",
 			data: `This is an automated reply. We received you email with the subject "${email.subject}", and will handle it as soon as possible.`,
 		});
 
-		const replyMessage = new EmailMessage('sender@example.com', message.from, msg.asRaw());
+		const replyMessage = new EmailMessage(
+			"sender@example.com",
+			message.from,
+			msg.asRaw(),
+		);
 
 		await message.reply(replyMessage);
 		await message.forward("recipient@example.com");
@@ -205,4 +216,4 @@ Run `npx wrangler dev` and use curl to `POST` the same message from the [Receive
   /var/folders/33/pn86qymd0w50htvsjp93rys40000gn/T/miniflare-381a79d7efa4e991607b30a079f6b17d/files/email/a1db7ebb-ccb4-45ef-b315-df49c6d820c0.eml
 [wrangler:inf] Email handler forwarded message with
   rcptTo: recipient@example.com
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
index abe2ab9e1917b97..9b1bca4d651c33d 100644
--- a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
+++ b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
@@ -17,37 +17,39 @@ import { EmailMessage } from "cloudflare:email";
 import { createMimeMessage } from "mimetext";
 
 export default {
-  async email(message, env, ctx) {
-
-    const ticket = createTicket(message);
-
-    const msg = createMimeMessage();
-    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
-    msg.setRecipient(message.from);
-    msg.setSubject("Email Routing Auto-reply");
-    msg.addMessage({
-      contentType: 'text/plain',
-      data: `We got your message, your ticket number is ${ ticket.id }`
-    });
-
-    const replyMessage = new EmailMessage(
-      "<SENDER>@example.com",
-      message.from,
-      msg.asRaw()
-    );
-
-    await message.reply(replyMessage);
-  }
-}
+	async email(message, env, ctx) {
+		const ticket = createTicket(message);
+
+		const msg = createMimeMessage();
+		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+		msg.setSender({
+			name: "Thank you for your contact",
+			addr: "<SENDER>@example.com",
+		});
+		msg.setRecipient(message.from);
+		msg.setSubject("Email Routing Auto-reply");
+		msg.addMessage({
+			contentType: "text/plain",
+			data: `We got your message, your ticket number is ${ticket.id}`,
+		});
+
+		const replyMessage = new EmailMessage(
+			"<SENDER>@example.com",
+			message.from,
+			msg.asRaw(),
+		);
+
+		await message.reply(replyMessage);
+	},
+};
 ```
 
 To mitigate security risks and abuse, replying to incoming emails has a few requirements and limits:
 
-* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
-* The email can only be replied to once in the same `EmailMessage` event.
-* The recipient in the reply must match the incoming sender.
-* The outgoing sender domain must match the same domain that received the email.
-* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
+- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
+- The email can only be replied to once in the same `EmailMessage` event.
+- The recipient in the reply must match the incoming sender.
+- The outgoing sender domain must match the same domain that received the email.
+- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
 
-If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
\ No newline at end of file
+If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
diff --git a/src/content/docs/email-routing/get-started/audit-logs.mdx b/src/content/docs/email-routing/get-started/audit-logs.mdx
index ea56a04e458c21b..ecd9b2792350842 100644
--- a/src/content/docs/email-routing/get-started/audit-logs.mdx
+++ b/src/content/docs/email-routing/get-started/audit-logs.mdx
@@ -13,9 +13,9 @@ products:
 
 Audit logs for Email Routing are available in the [Cloudflare dashboard](https://dash.cloudflare.com/?account=audit-log). The following changes to Email Routing will be displayed:
 
-* Add/edit Rule
-* Add address
-* Address change status
-* Enable/disable/unlock zone
+- Add/edit Rule
+- Add address
+- Address change status
+- Enable/disable/unlock zone
 
 Refer to [Review audit logs](/fundamentals/account/account-security/review-audit-logs/) for more information.
diff --git a/src/content/docs/email-routing/get-started/index.mdx b/src/content/docs/email-routing/get-started/index.mdx
index 79651ecf8525c75..4f3a50117f3555f 100644
--- a/src/content/docs/email-routing/get-started/index.mdx
+++ b/src/content/docs/email-routing/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 To enable Email Routing, start by creating a custom email address linked to a destination address or Email Worker. This forms an **email rule**. You can enable or disable rules from the Cloudflare dashboard. Refer to [Enable Email Routing](/email-routing/get-started/enable-email-routing) for more details.
 
diff --git a/src/content/docs/email-routing/graphql-example.mdx b/src/content/docs/email-routing/graphql-example.mdx
index 1026c732af09d68..01e88cb7c926f54 100644
--- a/src/content/docs/email-routing/graphql-example.mdx
+++ b/src/content/docs/email-routing/graphql-example.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 10
 products:
   - email-routing
----
\ No newline at end of file
+---
diff --git a/src/content/docs/email-routing/limits.mdx b/src/content/docs/email-routing/limits.mdx
index aa0c9137f7e93b4..7ba2a9378e24cab 100644
--- a/src/content/docs/email-routing/limits.mdx
+++ b/src/content/docs/email-routing/limits.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Email Workers size limits
 
diff --git a/src/content/docs/email-routing/postmaster.mdx b/src/content/docs/email-routing/postmaster.mdx
index f2e0afee4304d44..5024a5fca40679d 100644
--- a/src/content/docs/email-routing/postmaster.mdx
+++ b/src/content/docs/email-routing/postmaster.mdx
@@ -223,7 +223,6 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
-
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
@@ -236,4 +235,4 @@ Email Routing does not support sending or replying from your Cloudflare domain.
 
 ### "`.`" is treated as a normal character for custom addresses
 
-The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
\ No newline at end of file
+The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
diff --git a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
index 5b19f941bc3973c..d5a45e53b881844 100644
--- a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
+++ b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
@@ -17,8 +17,8 @@ You can check the status of your DNS records in the **Settings** section of Emai
 
 Check the status of your account's DNS records in the **Email DNS records** card:
 
-* **Email DNS records configured** - DNS records are properly configured.
-* **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
+- **Email DNS records configured** - DNS records are properly configured.
+- **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
 
 ### Start disabling
 
@@ -36,8 +36,8 @@ Select **View DNS records** for a list of the required `MX` and sender policy fr
 
 If you are having trouble with your account's DNS records, refer to the [Troubleshooting](/email-routing/troubleshooting/) section.
 
-## _dc-mx DNS responses
+## \_dc-mx DNS responses
 
 If you see a DNS response with a `_dc-mx` prefix (for example, `_dc-mx.a1b2c3d4e5f6.example.com`), Cloudflare inserted it automatically. This response appears when your `MX` record points to a hostname that is [proxied](/dns/proxy-status/) through Cloudflare. The `_dc-mx` target itself resolves directly to your origin IP address so that mail traffic bypasses the proxy and reaches your mail server.
 
-For more information, refer to [_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
+For more information, refer to [\_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
diff --git a/src/content/docs/email-routing/setup/index.mdx b/src/content/docs/email-routing/setup/index.mdx
index 9e8e6168e7d9d3d..a985b31913d2240 100644
--- a/src/content/docs/email-routing/setup/index.mdx
+++ b/src/content/docs/email-routing/setup/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-routing/troubleshooting/index.mdx b/src/content/docs/email-routing/troubleshooting/index.mdx
index 6049ae5a1dbf1b6..320a435287a9f78 100644
--- a/src/content/docs/email-routing/troubleshooting/index.mdx
+++ b/src/content/docs/email-routing/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Email Routing warns you when your DNS records are not properly configured. In Email Routing's **Overview** page, you will see a message explaining what type of problem your account's DNS records have.
 
diff --git a/src/content/docs/email-security/account-setup/index.mdx b/src/content/docs/email-security/account-setup/index.mdx
index 58b9191302f4924..115b19e40df6b41 100644
--- a/src/content/docs/email-security/account-setup/index.mdx
+++ b/src/content/docs/email-security/account-setup/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
index 1a386467767d7a5..74464f58cb9a20e 100644
--- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
+++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 1. Log in to the [Google Cloud Console](https://console.cloud.google.com/welcome/new). From the dashboard, select **CREATE OR SELECT PROJECT**.
 2. Provide the details for the new project, and select **CREATE** to start your new project.
@@ -19,4 +19,4 @@ import { Render } from "~/components"
 
 ## Next steps
 
-Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
\ No newline at end of file
+Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
diff --git a/src/content/docs/email-security/deployment/inline/reference/index.mdx b/src/content/docs/email-security/deployment/inline/reference/index.mdx
index 3acddcd2503e68e..d967052afafa9a8 100644
--- a/src/content/docs/email-security/deployment/inline/reference/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/inline/setup/index.mdx b/src/content/docs/email-security/deployment/inline/setup/index.mdx
index 9d77a311b1def17..7944841692ccc8f 100644
--- a/src/content/docs/email-security/deployment/inline/setup/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/setup/index.mdx
@@ -11,7 +11,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For help getting started with an [inline setup](/email-security/deployment/inline/), refer to the following guides:
 
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
index b36be50d7f74394..1d64d9275d3103e 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
@@ -15,11 +15,11 @@ Alert Webhooks allow you to connect external services to Email security, includi
 - Slack
 - Email addresses
 - <GlossaryTooltip
-  	term="SIEM"
-  	link="/email-security/reporting/siem-integration/"
-  >
-  	SIEM
-  </GlossaryTooltip>
+    	term="SIEM"
+    	link="/email-security/reporting/siem-integration/"
+    >
+    	SIEM
+    </GlossaryTooltip>
 - Microsoft Teams
 
 ## Create an alert webhook
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
index 064f16bbe246605..bcf17ca94340495 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/email-policies/index.mdx b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
index 970060f35bca548..f02050d417bebf4 100644
--- a/src/content/docs/email-security/email-configuration/email-policies/index.mdx
+++ b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 <Render file="contact-support" product="email-security" />
 
diff --git a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
index cf276be7c979d2c..57eafdbc713f614 100644
--- a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
+++ b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/lists/index.mdx b/src/content/docs/email-security/email-configuration/lists/index.mdx
index fb788ae5a7833ef..309b6ba3c5e4a88 100644
--- a/src/content/docs/email-security/email-configuration/lists/index.mdx
+++ b/src/content/docs/email-security/email-configuration/lists/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx
index 0f8848970f558ed..1f577dece7e60c7 100644
--- a/src/content/docs/email-security/migrate-to-email-security.mdx
+++ b/src/content/docs/email-security/migrate-to-email-security.mdx
@@ -45,15 +45,15 @@ To invite users in Zero Trust Email security:
 
 Once you have added new account members, you will have to assign each member an [Email security role](/cloudflare-one/roles-permissions/#email-security-roles).
 
-| Area 1              | Email security                                                            | Description                                                                                                                                                                                             |
-| ------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Area 1              | Email security                                                            | Description                                                                                                                                                                                                                  |
+| ------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | N/A                 | Cloudflare Zero Trust                                                     | Can edit Cloudflare [Zero Trust](/cloudflare-one/). Has administrator access to all Zero Trust products including Access, Gateway, the Cloudflare One Client, Tunnel, Browser Isolation, CASB, DLP, DEX, and Email security. |
-| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                 |
-| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                 |
-| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                          |
-| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                        |
-| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                               |
-| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                              |
+| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                                      |
+| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                                      |
+| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                                               |
+| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                                             |
+| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                                                    |
+| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                                                   |
 
 ## Create webhooks
 
@@ -142,12 +142,12 @@ This table displays the difference in terminology used when creating policies:
 
 This table displays the difference in terminology used when finding emails whose disposition is incorrect:
 
-| Area 1                                                                                                                                                                                   | Email security                                                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| Area 1                                                                                                                                                                                   | Email security                                                                                       |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | Report [false negative](/email-security/email-configuration/phish-submissions/#false-negatives)/[false positive](/email-security/email-configuration/phish-submissions/#false-positives) | [Submit messages for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) |
-| N/A                                                                                                                                                                                      | Escalate user submissions                                                                |
-| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)         |
-| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)         |
+| N/A                                                                                                                                                                                      | Escalate user submissions                                                                            |
+| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)                     |
+| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)                     |
 
 ## Business Email Compromise
 
diff --git a/src/content/docs/email-security/reference/index.mdx b/src/content/docs/email-security/reference/index.mdx
index 9f7509bd9cf9280..c38a16a0de9f080 100644
--- a/src/content/docs/email-security/reference/index.mdx
+++ b/src/content/docs/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/email-service/api/index.mdx b/src/content/docs/email-service/api/index.mdx
index 44e78505396a107..d03187150053624 100644
--- a/src/content/docs/email-service/api/index.mdx
+++ b/src/content/docs/email-service/api/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/api/route-emails/email-handler.mdx b/src/content/docs/email-service/api/route-emails/email-handler.mdx
index a5e96e60aafc443..4de6233a27266e7 100644
--- a/src/content/docs/email-service/api/route-emails/email-handler.mdx
+++ b/src/content/docs/email-service/api/route-emails/email-handler.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 products:
   - email-service
-  - workers 
+  - workers
 ---
 
 import { Tabs, TabItem } from "~/components";
diff --git a/src/content/docs/email-service/api/route-emails/index.mdx b/src/content/docs/email-service/api/route-emails/index.mdx
index 5d7f8f3f10cb0db..1d26611cdc87d0d 100644
--- a/src/content/docs/email-service/api/route-emails/index.mdx
+++ b/src/content/docs/email-service/api/route-emails/index.mdx
@@ -14,4 +14,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/api/send-emails/rest-api.mdx b/src/content/docs/email-service/api/send-emails/rest-api.mdx
index 7435885f3824271..91cbd43aa37da94 100644
--- a/src/content/docs/email-service/api/send-emails/rest-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/rest-api.mdx
@@ -135,14 +135,14 @@ A successful response returns the delivery status for each recipient:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "delivered": ["recipient@example.com"],
-    "permanent_bounces": [],
-    "queued": []
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"delivered": ["recipient@example.com"],
+		"permanent_bounces": [],
+		"queued": []
+	}
 }
 ```
 
@@ -156,29 +156,29 @@ The REST API returns standard Cloudflare API error responses. A failed request r
 
 ```json
 {
-  "success": false,
-  "errors": [
-    {
-      "code": 10001,
-      "message": "email.sending.error.invalid_request_schema"
-    }
-  ],
-  "messages": [],
-  "result": null
+	"success": false,
+	"errors": [
+		{
+			"code": 10001,
+			"message": "email.sending.error.invalid_request_schema"
+		}
+	],
+	"messages": [],
+	"result": null
 }
 ```
 
 Common REST API error codes:
 
-| HTTP Status | Code | Message | Description |
-| ----------- | ---- | ------- | ----------- |
-| 400 | 10001 | `email.sending.error.invalid_request_schema` | Invalid request format |
-| 400 | 10200 | `email.sending.error.email.invalid` | Invalid email content |
-| 400 | 10201 | `email.sending.error.email.no_content_length` | Missing content length |
-| 400 | 10202 | `email.sending.error.email.too_big` | Email exceeds size limit |
-| 403 | 10203 | `email.sending.error.email.sending_disabled` | Sending disabled for this zone/account |
-| 429 | 10004 | `email.sending.error.throttled` | Rate limit exceeded |
-| 500 | 10002 | `email.sending.error.internal_server` | Internal server error |
+| HTTP Status | Code  | Message                                       | Description                            |
+| ----------- | ----- | --------------------------------------------- | -------------------------------------- |
+| 400         | 10001 | `email.sending.error.invalid_request_schema`  | Invalid request format                 |
+| 400         | 10200 | `email.sending.error.email.invalid`           | Invalid email content                  |
+| 400         | 10201 | `email.sending.error.email.no_content_length` | Missing content length                 |
+| 400         | 10202 | `email.sending.error.email.too_big`           | Email exceeds size limit               |
+| 403         | 10203 | `email.sending.error.email.sending_disabled`  | Sending disabled for this zone/account |
+| 429         | 10004 | `email.sending.error.throttled`               | Rate limit exceeded                    |
+| 500         | 10002 | `email.sending.error.internal_server`         | Internal server error                  |
 
 :::note[Workers binding vs REST API errors]
 The REST API returns standard Cloudflare API numeric error codes, while the [Workers binding](/email-service/api/send-emails/workers-api/) throws errors with string codes (for example, `E_SENDER_NOT_VERIFIED`). Refer to the [Workers API error codes table](/email-service/api/send-emails/workers-api/#error-codes) for the string error codes.
diff --git a/src/content/docs/email-service/api/send-emails/workers-api.mdx b/src/content/docs/email-service/api/send-emails/workers-api.mdx
index 83244ea4c0e7dbb..ad7de8aa161ea02 100644
--- a/src/content/docs/email-service/api/send-emails/workers-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/workers-api.mdx
@@ -235,27 +235,27 @@ export default {
 
 The following error codes may be returned when sending emails:
 
-| Error Code                      | Description                             | Common Causes                                                 |
-| ------------------------------- | --------------------------------------- | ------------------------------------------------------------- |
-| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data |
-| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                     |
-| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                           |
-| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                     |
-| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`      |
-| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam     |
-| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                         |
-| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                        |
-| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection             |
-| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                    |
-| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                   |
-| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                         |
+| Error Code                      | Description                             | Common Causes                                                                              |
+| ------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------ |
+| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data                              |
+| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                                                  |
+| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                                                        |
+| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                                                  |
+| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`                                   |
+| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam                                  |
+| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                                                      |
+| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                                                     |
+| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection                                          |
+| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                                                 |
+| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                                                |
+| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                                                      |
 | `E_HEADER_NOT_ALLOWED`          | Header not allowed                      | Header is platform-controlled or not on the [whitelist](/email-service/reference/headers/) |
-| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field    |
-| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                   |
-| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                |
-| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                  |
-| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                       |
-| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers               |
+| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field                                 |
+| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                                                |
+| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                                             |
+| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                                               |
+| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                                                    |
+| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers                                            |
 
 ## Legacy `EmailMessage` API
 
diff --git a/src/content/docs/email-service/concepts/index.mdx b/src/content/docs/email-service/concepts/index.mdx
index 6dacc309b767a1c..20dd8baf3869d18 100644
--- a/src/content/docs/email-service/concepts/index.mdx
+++ b/src/content/docs/email-service/concepts/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/configuration/index.mdx b/src/content/docs/email-service/configuration/index.mdx
index d7381d7a1565017..d8ae4416f025c07 100644
--- a/src/content/docs/email-service/configuration/index.mdx
+++ b/src/content/docs/email-service/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
index be8214fb629d3e3..7b743963157b998 100644
--- a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
+++ b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
@@ -44,138 +44,145 @@ id = "your-kv-namespace-id"
 ## Hard bounce detection
 
 ```javascript
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
-  async email(message, env, ctx) {
-    // Parse the raw email message
-    const parser = new PostalMime.default();
-    const rawEmail = new Response(message.raw);
-    const email = await parser.parse(await rawEmail.arrayBuffer());
-
-    // Check if this is a bounce notification
-    if (isBounceNotification(email)) {
-      const bounceInfo = await parseBounceInfo(email);
-
-      if (bounceInfo.type === 'hard') {
-        await handleHardBounce(bounceInfo, env);
-        console.log(`Hard bounce processed for: ${bounceInfo.originalRecipient}`);
-        return;
-      }
-    }
-
-    // Forward non-bounce emails normally
-    await message.forward('admin@yourdomain.com');
-  },
+	async email(message, env, ctx) {
+		// Parse the raw email message
+		const parser = new PostalMime.default();
+		const rawEmail = new Response(message.raw);
+		const email = await parser.parse(await rawEmail.arrayBuffer());
+
+		// Check if this is a bounce notification
+		if (isBounceNotification(email)) {
+			const bounceInfo = await parseBounceInfo(email);
+
+			if (bounceInfo.type === "hard") {
+				await handleHardBounce(bounceInfo, env);
+				console.log(
+					`Hard bounce processed for: ${bounceInfo.originalRecipient}`,
+				);
+				return;
+			}
+		}
+
+		// Forward non-bounce emails normally
+		await message.forward("admin@yourdomain.com");
+	},
 };
 
 function isBounceNotification(email) {
-  // Check common bounce indicators
-  const subject = email.subject?.toLowerCase() || '';
-  const fromAddress = email.from?.address?.toLowerCase() || '';
-
-  // Common bounce indicators
-  const bounceSubjects = [
-    'mail delivery failed',
-    'undelivered mail returned to sender',
-    'delivery status notification',
-    'returned mail',
-    'mail system error'
-  ];
-
-  const bounceFromPatterns = [
-    'mailer-daemon',
-    'mail-daemon',
-    'postmaster',
-    'noreply',
-    'bounce'
-  ];
-
-  return bounceSubjects.some(phrase => subject.includes(phrase)) ||
-         bounceFromPatterns.some(pattern => fromAddress.includes(pattern));
+	// Check common bounce indicators
+	const subject = email.subject?.toLowerCase() || "";
+	const fromAddress = email.from?.address?.toLowerCase() || "";
+
+	// Common bounce indicators
+	const bounceSubjects = [
+		"mail delivery failed",
+		"undelivered mail returned to sender",
+		"delivery status notification",
+		"returned mail",
+		"mail system error",
+	];
+
+	const bounceFromPatterns = [
+		"mailer-daemon",
+		"mail-daemon",
+		"postmaster",
+		"noreply",
+		"bounce",
+	];
+
+	return (
+		bounceSubjects.some((phrase) => subject.includes(phrase)) ||
+		bounceFromPatterns.some((pattern) => fromAddress.includes(pattern))
+	);
 }
 
 async function parseBounceInfo(email) {
-  const text = email.text || '';
-  const html = email.html || '';
-  const content = text + ' ' + html;
-
-  // Extract original recipient email
-  const recipientMatch = content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
-                        content.match(/([^\s<]+@[^\s>]+)/);
-
-  const originalRecipient = recipientMatch ? recipientMatch[1] : null;
-
-  // Determine bounce type based on content
-  const hardBounceIndicators = [
-    'user unknown',
-    'no such user',
-    'invalid recipient',
-    'recipient address rejected',
-    'mailbox unavailable',
-    'domain not found',
-    '5.1.1', // SMTP error code for bad destination mailbox
-    '5.1.2', // SMTP error code for bad destination system
-    '5.4.1', // SMTP error code for no answer from host
-  ];
-
-  const isHardBounce = hardBounceIndicators.some(indicator =>
-    content.toLowerCase().includes(indicator.toLowerCase())
-  );
-
-  return {
-    type: isHardBounce ? 'hard' : 'soft',
-    originalRecipient,
-    reason: extractBounceReason(content),
-    timestamp: new Date().toISOString()
-  };
+	const text = email.text || "";
+	const html = email.html || "";
+	const content = text + " " + html;
+
+	// Extract original recipient email
+	const recipientMatch =
+		content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
+		content.match(/([^\s<]+@[^\s>]+)/);
+
+	const originalRecipient = recipientMatch ? recipientMatch[1] : null;
+
+	// Determine bounce type based on content
+	const hardBounceIndicators = [
+		"user unknown",
+		"no such user",
+		"invalid recipient",
+		"recipient address rejected",
+		"mailbox unavailable",
+		"domain not found",
+		"5.1.1", // SMTP error code for bad destination mailbox
+		"5.1.2", // SMTP error code for bad destination system
+		"5.4.1", // SMTP error code for no answer from host
+	];
+
+	const isHardBounce = hardBounceIndicators.some((indicator) =>
+		content.toLowerCase().includes(indicator.toLowerCase()),
+	);
+
+	return {
+		type: isHardBounce ? "hard" : "soft",
+		originalRecipient,
+		reason: extractBounceReason(content),
+		timestamp: new Date().toISOString(),
+	};
 }
 
 function extractBounceReason(content) {
-  // Extract the specific error message
-  const reasonPatterns = [
-    /diagnostic[- ]code:\s*(.+)/i,
-    /reason:\s*(.+)/i,
-    /error:\s*(.+)/i,
-    /(5\.\d+\.\d+[^.\n]*)/i
-  ];
-
-  for (const pattern of reasonPatterns) {
-    const match = content.match(pattern);
-    if (match) {
-      return match[1].trim().split('\n')[0]; // Take first line only
-    }
-  }
-
-  return 'Unknown bounce reason';
+	// Extract the specific error message
+	const reasonPatterns = [
+		/diagnostic[- ]code:\s*(.+)/i,
+		/reason:\s*(.+)/i,
+		/error:\s*(.+)/i,
+		/(5\.\d+\.\d+[^.\n]*)/i,
+	];
+
+	for (const pattern of reasonPatterns) {
+		const match = content.match(pattern);
+		if (match) {
+			return match[1].trim().split("\n")[0]; // Take first line only
+		}
+	}
+
+	return "Unknown bounce reason";
 }
 
 async function handleHardBounce(bounceInfo, env) {
-  if (!bounceInfo.originalRecipient) {
-    console.log('Could not extract original recipient from bounce');
-    return;
-  }
-
-  // Add to suppression list in KV
-  await env.SUPPRESSION_LIST.put(
-    bounceInfo.originalRecipient,
-    JSON.stringify({
-      type: 'hard_bounce',
-      reason: bounceInfo.reason,
-      timestamp: bounceInfo.timestamp,
-      status: 'suppressed'
-    }),
-    {
-      metadata: {
-        bounceType: 'hard',
-        addedDate: bounceInfo.timestamp
-      }
-    }
-  );
-
-  console.log(`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`);
+	if (!bounceInfo.originalRecipient) {
+		console.log("Could not extract original recipient from bounce");
+		return;
+	}
+
+	// Add to suppression list in KV
+	await env.SUPPRESSION_LIST.put(
+		bounceInfo.originalRecipient,
+		JSON.stringify({
+			type: "hard_bounce",
+			reason: bounceInfo.reason,
+			timestamp: bounceInfo.timestamp,
+			status: "suppressed",
+		}),
+		{
+			metadata: {
+				bounceType: "hard",
+				addedDate: bounceInfo.timestamp,
+			},
+		},
+	);
+
+	console.log(
+		`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`,
+	);
 }
-````
+```
 
 ## Testing hard bounce handling
 
diff --git a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
index a7a6a6f31405fa0..4f7199cce0ef4f7 100644
--- a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
+++ b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
@@ -40,7 +40,7 @@ class SimpleSpamFilter implements SpamFilter {
 		"winner",
 		"congratulations",
 		"inheritance",
-		"lottery"
+		"lottery",
 	];
 
 	private trustedDomains = ["company.com", "trusted-partner.com", "vendor.net"];
@@ -83,7 +83,10 @@ class SimpleSpamFilter implements SpamFilter {
 		}
 
 		// Check for suspicious sender patterns
-		if (sender.includes("noreply") && subject.toLowerCase().includes("urgent")) {
+		if (
+			sender.includes("noreply") &&
+			subject.toLowerCase().includes("urgent")
+		) {
 			score += 2;
 			reasons.push("Suspicious noreply + urgent combination");
 		}
@@ -101,31 +104,33 @@ const spamFilter = new SimpleSpamFilter();
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const startTime = Date.now();
-		
+
 		// Check for spam
 		const spamCheck = await spamFilter.checkSpam(message);
 
 		// Track spam check metrics
 		env.EMAIL_ANALYTICS?.writeDataPoint({
 			blobs: [
-				'spam_check_completed',
+				"spam_check_completed",
 				message.from,
 				message.to,
-				spamCheck.isSpam ? 'spam' : 'legitimate'
+				spamCheck.isSpam ? "spam" : "legitimate",
 			],
 			doubles: [
 				1, // Count
 				spamCheck.score,
-				Date.now() - startTime
+				Date.now() - startTime,
 			],
 			indexes: [
 				`spam_detected:${spamCheck.isSpam}`,
-				`score_range:${getScoreRange(spamCheck.score)}`
-			]
+				`score_range:${getScoreRange(spamCheck.score)}`,
+			],
 		});
 
 		if (spamCheck.isSpam) {
-			console.log(`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`);
+			console.log(
+				`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`,
+			);
 			message.setReject(`Message rejected: ${spamCheck.reasons[0]}`);
 			return;
 		}
@@ -141,13 +146,13 @@ export default {
 };
 
 function getScoreRange(score: number): string {
-	if (score < 0) return 'trusted';
-	if (score === 0) return 'neutral';
-	if (score === 1) return 'suspicious';
-	return 'spam';
+	if (score < 0) return "trusted";
+	if (score === 0) return "neutral";
+	if (score === 1) return "suspicious";
+	return "spam";
 }
 ```
 
 ## Advanced spam detection with AI
 
-For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
\ No newline at end of file
+For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
diff --git a/src/content/docs/email-service/get-started/send-emails.mdx b/src/content/docs/email-service/get-started/send-emails.mdx
index 14f5fccbd0ab3f5..cb5765ac4807d02 100644
--- a/src/content/docs/email-service/get-started/send-emails.mdx
+++ b/src/content/docs/email-service/get-started/send-emails.mdx
@@ -54,14 +54,14 @@ A successful response includes the delivery status for each recipient:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "delivered": ["recipient@example.com"],
-    "permanent_bounces": [],
-    "queued": []
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"delivered": ["recipient@example.com"],
+		"permanent_bounces": [],
+		"queued": []
+	}
 }
 ```
 
@@ -84,14 +84,14 @@ If you are building on Cloudflare Workers, you can use the Workers binding for n
 2.  Add the email binding to your Wrangler configuration file:
 
     <WranglerConfig>
-
-    ```toml
-    [[send_email]]
-    name = "EMAIL"
-    remote = true
-    ```
-
-    </WranglerConfig>
+    
+        ```toml
+        [[send_email]]
+        name = "EMAIL"
+        remote = true
+        ```
+    
+        </WranglerConfig>
 
 3.  Create your Worker code in `src/index.ts`:
 
@@ -147,4 +147,4 @@ Now that you can send emails, explore advanced features:
 
 - **[Route incoming emails](/email-service/get-started/route-emails/)** - Process emails sent to your domain
 - **[API reference](/email-service/api/send-emails/)** - Complete API documentation
-- **[Examples](/email-service/examples/)** - Real-world implementation patterns
\ No newline at end of file
+- **[Examples](/email-service/examples/)** - Real-world implementation patterns
diff --git a/src/content/docs/email-service/local-development/index.mdx b/src/content/docs/email-service/local-development/index.mdx
index 9b9df2443a3e182..90f0be957d8c338 100644
--- a/src/content/docs/email-service/local-development/index.mdx
+++ b/src/content/docs/email-service/local-development/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Test and develop your email applications locally using Wrangler before deploying to production.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/local-development/routing.mdx b/src/content/docs/email-service/local-development/routing.mdx
index caf0d02137925c7..50adb9e89ffd9e6 100644
--- a/src/content/docs/email-service/local-development/routing.mdx
+++ b/src/content/docs/email-service/local-development/routing.mdx
@@ -35,30 +35,30 @@ name = "EMAIL"
 ## Basic routing worker
 
 ```javascript
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
-  async email(message, env, ctx) {
-    // Parse the raw email message
-    const parser = new PostalMime.default();
-    const rawEmail = new Response(message.raw);
-    const email = await parser.parse(await rawEmail.arrayBuffer());
-
-    console.log('Received email:', {
-      from: message.from,
-      to: message.to,
-      subject: email.subject,
-      text: email.text,
-      html: email.html
-    });
-
-    // Route based on recipient
-    if (message.to.includes('support@')) {
-      await message.forward('support-team@company.com');
-    } else {
-      await message.forward('general@company.com');
-    }
-  },
+	async email(message, env, ctx) {
+		// Parse the raw email message
+		const parser = new PostalMime.default();
+		const rawEmail = new Response(message.raw);
+		const email = await parser.parse(await rawEmail.arrayBuffer());
+
+		console.log("Received email:", {
+			from: message.from,
+			to: message.to,
+			subject: email.subject,
+			text: email.text,
+			html: email.html,
+		});
+
+		// Route based on recipient
+		if (message.to.includes("support@")) {
+			await message.forward("support-team@company.com");
+		} else {
+			await message.forward("general@company.com");
+		}
+	},
 };
 ```
 
diff --git a/src/content/docs/email-service/platform/index.mdx b/src/content/docs/email-service/platform/index.mdx
index 56789154dfe88e9..c4e599e6b17ffc9 100644
--- a/src/content/docs/email-service/platform/index.mdx
+++ b/src/content/docs/email-service/platform/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/platform/pricing.mdx b/src/content/docs/email-service/platform/pricing.mdx
index 914f0b2cf37e5a8..4dfa8f6a7c2c0c2 100644
--- a/src/content/docs/email-service/platform/pricing.mdx
+++ b/src/content/docs/email-service/platform/pricing.mdx
@@ -14,9 +14,9 @@ Cloudflare Email Service pricing is based on your Cloudflare plan and email usag
 
 Email Routing is available on both the Workers Free and Workers Paid plans. Email Sending is only available on the Workers Paid plan.
 
-|                                                         | Workers Free     | Workers Paid     |
-| ------------------------------------------------------- | ---------------- | ---------------- |
-| **Outbound emails (Email Sending)**                     | Not available    | 3,000 included per month, then $0.35 per 1,000 emails |
-| **Inbound emails (Email Routing)**                      | Unlimited        | Unlimited        |
+|                                     | Workers Free  | Workers Paid                                          |
+| ----------------------------------- | ------------- | ----------------------------------------------------- |
+| **Outbound emails (Email Sending)** | Not available | 3,000 included per month, then $0.35 per 1,000 emails |
+| **Inbound emails (Email Routing)**  | Unlimited     | Unlimited                                             |
 
 Email Routing Workers is billed according to [Workers pricing](/workers/platform/pricing/).
diff --git a/src/content/docs/email-service/reference/index.mdx b/src/content/docs/email-service/reference/index.mdx
index fb104b8db015bee..667dce89f146995 100644
--- a/src/content/docs/email-service/reference/index.mdx
+++ b/src/content/docs/email-service/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
     hideIndex: true
 products:
   - email-service
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/email-service/reference/postmaster.mdx b/src/content/docs/email-service/reference/postmaster.mdx
index e5f357aa33574bd..329745da9935650 100644
--- a/src/content/docs/email-service/reference/postmaster.mdx
+++ b/src/content/docs/email-service/reference/postmaster.mdx
@@ -164,7 +164,6 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
-
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
diff --git a/src/content/docs/firewall/api/cf-filters/delete.mdx b/src/content/docs/firewall/api/cf-filters/delete.mdx
index b6c9144e5c5757d..3d3ea8b45311d7f 100644
--- a/src/content/docs/firewall/api/cf-filters/delete.mdx
+++ b/src/content/docs/firewall/api/cf-filters/delete.mdx
@@ -24,17 +24,17 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>"
-    },
-    {
-      "id": "<FILTER_ID_2>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID_1>"
+		},
+		{
+			"id": "<FILTER_ID_2>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -51,13 +51,13 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID>"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID>"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/get.mdx b/src/content/docs/firewall/api/cf-filters/get.mdx
index c4c4d34c089e8f4..f60ae9c7c41a342 100644
--- a/src/content/docs/firewall/api/cf-filters/get.mdx
+++ b/src/content/docs/firewall/api/cf-filters/get.mdx
@@ -23,47 +23,47 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>",
-      "paused": false,
-      "description": "Login from office",
-      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "Login",
-      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_3>",
-      "paused": false,
-      "description": "not /api",
-      "expression": "not http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_4>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_5>",
-      "paused": false,
-      "expression": "ip.src eq 93.184.216.0"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result_info": {
-    "page": 1,
-    "per_page": 25,
-    "count": 5,
-    "total_count": 5,
-    "total_pages": 1
-  }
+	"result": [
+		{
+			"id": "<FILTER_ID_1>",
+			"paused": false,
+			"description": "Login from office",
+			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "Login",
+			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_3>",
+			"paused": false,
+			"description": "not /api",
+			"expression": "not http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_4>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_5>",
+			"paused": false,
+			"expression": "ip.src eq 93.184.216.0"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result_info": {
+		"page": 1,
+		"per_page": 25,
+		"count": 5,
+		"total_count": 5,
+		"total_pages": 1
+	}
 }
 ```
 
@@ -79,14 +79,14 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters/{filter_id}"
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<FILTER_ID>",
-    "paused": false,
-    "description": "Login from office",
-    "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<FILTER_ID>",
+		"paused": false,
+		"description": "Login from office",
+		"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/post.mdx b/src/content/docs/firewall/api/cf-filters/post.mdx
index ec20a4e1f410ada..966cc67d408dcfc 100644
--- a/src/content/docs/firewall/api/cf-filters/post.mdx
+++ b/src/content/docs/firewall/api/cf-filters/post.mdx
@@ -43,39 +43,39 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID_1>",
-      "paused": false,
-      "expression": "ip.src eq 93.184.216.0"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_3>",
-      "paused": false,
-      "description": "not /api",
-      "expression": "not http.request.uri.path matches \"^/api/.*$\""
-    },
-    {
-      "id": "<FILTER_ID_4>",
-      "paused": false,
-      "description": "Login",
-      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    },
-    {
-      "id": "<FILTER_ID_5>",
-      "paused": false,
-      "description": "Login from office",
-      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID_1>",
+			"paused": false,
+			"expression": "ip.src eq 93.184.216.0"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_3>",
+			"paused": false,
+			"description": "not /api",
+			"expression": "not http.request.uri.path matches \"^/api/.*$\""
+		},
+		{
+			"id": "<FILTER_ID_4>",
+			"paused": false,
+			"description": "Login",
+			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		},
+		{
+			"id": "<FILTER_ID_5>",
+			"paused": false,
+			"description": "Login from office",
+			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/put.mdx b/src/content/docs/firewall/api/cf-filters/put.mdx
index 4a08764ea671787..a0412eac414fc43 100644
--- a/src/content/docs/firewall/api/cf-filters/put.mdx
+++ b/src/content/docs/firewall/api/cf-filters/put.mdx
@@ -38,23 +38,23 @@ curl --request PUT \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<FILTER_ID>",
-      "paused": false,
-      "description": "IP of example.org",
-      "expression": "ip.src eq 93.184.216.0"
-    },
-    {
-      "id": "<FILTER_ID_2>",
-      "paused": false,
-      "description": "/api",
-      "expression": "http.request.uri.path matches \"^/api/.*$\""
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<FILTER_ID>",
+			"paused": false,
+			"description": "IP of example.org",
+			"expression": "ip.src eq 93.184.216.0"
+		},
+		{
+			"id": "<FILTER_ID_2>",
+			"paused": false,
+			"description": "/api",
+			"expression": "http.request.uri.path matches \"^/api/.*$\""
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -78,14 +78,14 @@ curl --request PUT \
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<FILTER_ID>",
-    "paused": false,
-    "description": "Login from office",
-    "expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<FILTER_ID>",
+		"paused": false,
+		"description": "Login from office",
+		"expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/validation.mdx b/src/content/docs/firewall/api/cf-filters/validation.mdx
index 42402810e50cc29..191219397a1902a 100644
--- a/src/content/docs/firewall/api/cf-filters/validation.mdx
+++ b/src/content/docs/firewall/api/cf-filters/validation.mdx
@@ -10,8 +10,6 @@ description: Validate firewall rule expressions via the API.
 
 The Cloudflare Filters API supports an endpoint for validating expressions.
 
-
-
 ## Examples
 
 ### Validate expression via query string
@@ -24,14 +22,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr?expression=ip.s
 
 ```json title="Response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
-    }
-  ],
-  "messages": null
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
+		}
+	],
+	"messages": null
 }
 ```
 
@@ -57,14 +55,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr" \
 
 ```json title="Response"
 {
-  "result": null,
-  "success": false,
-  "errors": [
-    {
-      "message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
-    }
-  ],
-  "messages": null
+	"result": null,
+	"success": false,
+	"errors": [
+		{
+			"message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
+		}
+	],
+	"messages": null
 }
 ```
 
diff --git a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
index 493daca2fecd16a..c396807b1630fa8 100644
--- a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
+++ b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
@@ -24,9 +24,9 @@ A filter object typically looks like the following:
 
 ```json
 {
-  "id": "<FILTER_ID>",
-  "expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
-  "description": "WordPress login paths via the login page or mobile RPC endpoint"
+	"id": "<FILTER_ID>",
+	"expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
+	"description": "WordPress login paths via the login page or mobile RPC endpoint"
 }
 ```
 
@@ -38,8 +38,8 @@ The expression specified in this example filter is:
 
 This filter expression has a `(this or that) and not this` structure designed to:
 
-* Capture two WordPress paths that may be subject to brute force password attacks, and
-* Exclude traffic that comes from the IP address `93.184.216.34`.
+- Capture two WordPress paths that may be subject to brute force password attacks, and
+- Exclude traffic that comes from the IP address `93.184.216.34`.
 
 Imagine that this is an IP for your office. This expression demonstrates a filter that might be used (in a firewall rule) to block access to the WordPress login when accessed outside the office network.
 
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
index fa662e947375338..75c661f0deb8cc4 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
@@ -23,70 +23,70 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID_1>",
-      "paused": false,
-      "description": "allow API traffic without challenge",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_1>",
-        "expression": "http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "/api"
-      }
-    },
-    {
-      "id": "<RULE_ID_2>",
-      "paused": false,
-      "description": "do not challenge login from office",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_2>",
-        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login from office"
-      }
-    },
-    {
-      "id": "<RULE_ID_3>",
-      "paused": false,
-      "description": "challenge login",
-      "action": "challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_3>",
-        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login"
-      }
-    },
-    {
-      "id": "<RULE_ID_4>",
-      "paused": false,
-      "description": "Non-interactive challenge site",
-      "action": "js_challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_4>",
-        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "not /api"
-      }
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result_info": {
-    "page": 1,
-    "per_page": 25,
-    "count": 4,
-    "total_count": 4,
-    "total_pages": 1
-  }
+	"result": [
+		{
+			"id": "<RULE_ID_1>",
+			"paused": false,
+			"description": "allow API traffic without challenge",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_1>",
+				"expression": "http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "/api"
+			}
+		},
+		{
+			"id": "<RULE_ID_2>",
+			"paused": false,
+			"description": "do not challenge login from office",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_2>",
+				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login from office"
+			}
+		},
+		{
+			"id": "<RULE_ID_3>",
+			"paused": false,
+			"description": "challenge login",
+			"action": "challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_3>",
+				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login"
+			}
+		},
+		{
+			"id": "<RULE_ID_4>",
+			"paused": false,
+			"description": "Non-interactive challenge site",
+			"action": "js_challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_4>",
+				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "not /api"
+			}
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result_info": {
+		"page": 1,
+		"per_page": 25,
+		"count": 4,
+		"total_count": 4,
+		"total_pages": 1
+	}
 }
 ```
 
@@ -102,21 +102,21 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules/{rule_
 
 ```json title="Response"
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "paused": false,
-    "description": "do not challenge login from office",
-    "action": "allow",
-    "priority": null,
-    "filter": {
-      "id": "<FILTER_ID>",
-      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-      "paused": false,
-      "description": "Login from office"
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"paused": false,
+		"description": "do not challenge login from office",
+		"action": "allow",
+		"priority": null,
+		"filter": {
+			"id": "<FILTER_ID>",
+			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+			"paused": false,
+			"description": "Login from office"
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
index b3ec7601d83b43b..3c5f3df30b5c373 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
@@ -15,10 +15,8 @@ This example creates several firewall rules using a single API call.
 
 :::note
 
-
 To create a firewall rule you need a [filter](/firewall/api/cf-filters/what-is-a-filter/) identifier (`id`). If you have not created a filter yet, refer to the [Cloudflare Filters API documentation](/firewall/api/cf-filters/).
 
-
 :::
 
 ```bash title="Request"
@@ -60,62 +58,62 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-  "result": [
-    {
-      "id": "<RULE_ID_1>",
-      "paused": false,
-      "description": "Do not challenge login from office",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_1>",
-        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login from office"
-      }
-    },
-    {
-      "id": "<RULE_ID_2>",
-      "paused": false,
-      "description": "Challenge login",
-      "action": "challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_2>",
-        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-        "paused": false,
-        "description": "Login"
-      }
-    },
-    {
-      "id": "<RULE_ID_3>",
-      "paused": false,
-      "description": "Non-interactive challenge site",
-      "action": "js_challenge",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_3>",
-        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "not /api"
-      }
-    },
-    {
-      "id": "<RULE_ID_4>",
-      "paused": false,
-      "description": "Allow API traffic without challenge",
-      "action": "allow",
-      "priority": null,
-      "filter": {
-        "id": "<FILTER_ID_4>",
-        "expression": "http.request.uri.path matches \"^/api/.*$\"",
-        "paused": false,
-        "description": "/api"
-      }
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"id": "<RULE_ID_1>",
+			"paused": false,
+			"description": "Do not challenge login from office",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_1>",
+				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login from office"
+			}
+		},
+		{
+			"id": "<RULE_ID_2>",
+			"paused": false,
+			"description": "Challenge login",
+			"action": "challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_2>",
+				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+				"paused": false,
+				"description": "Login"
+			}
+		},
+		{
+			"id": "<RULE_ID_3>",
+			"paused": false,
+			"description": "Non-interactive challenge site",
+			"action": "js_challenge",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_3>",
+				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "not /api"
+			}
+		},
+		{
+			"id": "<RULE_ID_4>",
+			"paused": false,
+			"description": "Allow API traffic without challenge",
+			"action": "allow",
+			"priority": null,
+			"filter": {
+				"id": "<FILTER_ID_4>",
+				"expression": "http.request.uri.path matches \"^/api/.*$\"",
+				"paused": false,
+				"description": "/api"
+			}
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
index 0d5982f433847fe..3136c338ab132ce 100644
--- a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
+++ b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
@@ -73,7 +73,6 @@ While your priority numbering scheme can be arbitrary, keep the following in min
 - **Rules without a priority number are evaluated last**, in order of their action precedence. For example, a rule with the _Log_ action is evaluated before a rule that has the _Block_ action. For more on action precedence, refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/).
 - **Avoid using the number `1` as a priority** to make rule order modification easier in the future.
 - **Consider grouping ranges of priority numbers into categories** that have some meaning for your deployment. Here are some examples:
-
   - 5000-9999: Trusted IP addresses
   - 10000-19999: Blocking rules for bad crawlers
   - 20000-29999: Blocking rules for abusive users/spam
diff --git a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
index 94c7ab99e5aa858..1fb0715951d644a 100644
--- a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
+++ b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
@@ -21,7 +21,7 @@ To enable editing access by your Account Team:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page. (You must be logged in as a **Super Administrator**).
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Editing Permission**, switch the toggle to **On**.
 3. Select a duration.
@@ -29,8 +29,6 @@ To enable editing access by your Account Team:
 
 :::note
 
-
 In an emergency, Cloudflare Support can override your **Editing Permissions** and make updates to your account, but your Super Administrator will receive an email and the action will be recorded in your [Audit Logs](/fundamentals/account/account-security/review-audit-logs/) with an **Action** of **Break glass**.
 
-
 :::
diff --git a/src/content/docs/fundamentals/account/account-security/index.mdx b/src/content/docs/fundamentals/account/account-security/index.mdx
index 62434c63a9879ee..774bf0f5dba2826 100644
--- a/src/content/docs/fundamentals/account/account-security/index.mdx
+++ b/src/content/docs/fundamentals/account/account-security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
index 44b877f610b9365..3f045d04d65881c 100644
--- a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
+++ b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
@@ -14,12 +14,10 @@ Refer to the [blog post](https://blog.cloudflare.com/helping-keep-customers-safe
 
 :::note[Note]
 
-
 Cloudflare does not have additional information about the specific breach or Internet service that potentially lost your password.
 
 Popular online tools such as [Have I Been Pwned](https://haveibeenpwned.com/) can help you better understand where your external accounts were attacked. If you reused this password in other systems, it is recommended that you reset it in those as well.
 
-
 :::
 
 If your password is found in a data breach, we will email you information on how to reset your password and prompt you to do so in the Cloudflare dashboard.
diff --git a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
index bacbe900335ef0a..be25f61733a7a37 100644
--- a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
+++ b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
@@ -18,7 +18,7 @@ To view the active sessions associated with your email address:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 
diff --git a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
index 9e379c53fec4c81..f93945373a085e6 100644
--- a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
+++ b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 Zone holds prevent other teams in your organization from adding zones that are already active in another account.
 
@@ -24,7 +24,7 @@ Zone holds are enabled by default for all Enterprise zones.
 
 When you enable a zone hold, no one else can [add your zone](/fundamentals/manage-domains/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
 
-*The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed.*
+_The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed._
 
 To enable a zone hold:
 
diff --git a/src/content/docs/fundamentals/account/create-account.mdx b/src/content/docs/fundamentals/account/create-account.mdx
index cc509b79ec43b6f..e93d05d94fd8d52 100644
--- a/src/content/docs/fundamentals/account/create-account.mdx
+++ b/src/content/docs/fundamentals/account/create-account.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components"
+import { DashButton, Render } from "~/components";
 
 To create a Cloudflare account:
 
@@ -29,7 +29,7 @@ To change your account name:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page.
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Account Name**, select **Change Name**.
 3. Enter a new account name.
@@ -37,13 +37,13 @@ To change your account name:
 
 ## Best practices
 
-<Render file="create-account-best-practices" product="fundamentals" /> 
+<Render file="create-account-best-practices" product="fundamentals" />
 
-Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain. 
+Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain.
 
 Once you [set up an account](/fundamentals/account/), you have several ways to interact with Cloudflare.
 
-## Interact with Cloudflare 
+## Interact with Cloudflare
 
 If you prefer working without code, you can manage your account and domain settings through the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
@@ -62,4 +62,3 @@ For those who prefer to interact with Cloudflare programmatically, you can use s
 | [cloudflare-go](https://github.com/cloudflare/cloudflare-go)                           | [README](https://github.com/cloudflare/cloudflare-go#readme)         | The official Go library for the Cloudflare API.                                |
 | [cloudflare-typescript](https://github.com/cloudflare/cloudflare-typescript)           | [README](https://github.com/cloudflare/cloudflare-typescript#readme) | The official TypeScript library for the Cloudflare API.                        |
 | [cloudflare-python](https://github.com/cloudflare/cloudflare-python)                   | [README](https://github.com/cloudflare/cloudflare-python#readme)     | The official Python library for the Cloudflare API.                            |
-
diff --git a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
index d942475ab7e6765..535d145aa95d13f 100644
--- a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
+++ b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
@@ -16,10 +16,10 @@ Once you [set up a new account](/fundamentals/account/) and [add your domain](/f
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button at the end of the account row.
-![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
+   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
 
 3. Select **Copy account ID**.
 
@@ -29,17 +29,17 @@ To copy the account ID when you only have one account:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and locate your account.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button next to your account name.
 3. From the list that appears, select **Copy account ID**.
-![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
+   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
 
 ## Copy your Zone ID
 
 1. In the Cloudflare dashboard, go to the **Account** home and locate your account.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. From the **Overview** page for your account, locate the **API** section towards the bottom of the page.
 
@@ -53,7 +53,7 @@ You can also find your account ID from the **Workers & Pages** section of your a
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-    <DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. The **Account details** section contains your **Account ID**.
 3. To copy the Account ID, select **Click to copy**.
diff --git a/src/content/docs/fundamentals/account/index.mdx b/src/content/docs/fundamentals/account/index.mdx
index 78335a849e9c2ba..ed12e22c5045241 100644
--- a/src/content/docs/fundamentals/account/index.mdx
+++ b/src/content/docs/fundamentals/account/index.mdx
@@ -10,7 +10,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 If you need help setting up a new Cloudflare account, refer to the following resources:
 
diff --git a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
index 90ef1f2f6f50643..692fcea9aa69c90 100644
--- a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
+++ b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
@@ -21,7 +21,7 @@ To restrict the API access for the entire account:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Locate the **Enable API Access** section and then update the setting.
 
@@ -29,16 +29,14 @@ To restrict the API access for the entire account:
 
 :::note
 
-
 Member-level settings will override the account-level setting. If a specific member has API access enabled whereas the account has the access disabled, that member can still call APIs related to the Enterprise account.
 
-
 :::
 
 To restrict the API access for a specific member:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Click on the member to expand and choose the intended **API Access**. If `Account Default`, then it follows the account level setting.
diff --git a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
index f58ab298b5d15c4..8f1f58e538d2e66 100644
--- a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
+++ b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
@@ -114,24 +114,20 @@ To fetch all available permission groups and their IDs, use the [List permission
 
 ```json output
 {
-  "result": [
-    {
-      "id": "19637fbb73d242c0a92845d8db0b95b1",
-      "name": "AI Crawl Control Read",
-      "description": "Grants access to reading AI Crawl Control",
-      "scopes": [
-        "com.cloudflare.api.account.zone"
-      ]
-    },
-    {
-      "id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
-      "name": "AI Crawl Control Write",
-      "description": "Grants access to reading and editing AI Crawl Control",
-      "scopes": [
-        "com.cloudflare.api.account.zone"
-      ]
-    },
-    // (...)
+	"result": [
+		{
+			"id": "19637fbb73d242c0a92845d8db0b95b1",
+			"name": "AI Crawl Control Read",
+			"description": "Grants access to reading AI Crawl Control",
+			"scopes": ["com.cloudflare.api.account.zone"]
+		},
+		{
+			"id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
+			"name": "AI Crawl Control Write",
+			"description": "Grants access to reading and editing AI Crawl Control",
+			"scopes": ["com.cloudflare.api.account.zone"]
+		}
+		// (...)
 	]
 }
 ```
diff --git a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
index d084a748cb05a70..487d294ea4ff9cf 100644
--- a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
+++ b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
@@ -11,8 +11,8 @@ products:
 
 API tokens can be restricted at runtime in two ways:
 
-* [Client IP address range filtering](#client-ip-address-range-filtering)
-* [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
+- [Client IP address range filtering](#client-ip-address-range-filtering)
+- [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
 
 ## Client IP address range filtering
 
@@ -26,17 +26,14 @@ Client IP address range filtering is not applied to the [Verify Token](https://d
 
 :::
 
-
 ## Time to live (TTL) constraints
 
 By default, tokens do not expire and are long lived. Defining a TTL sets when a token starts being valid and when a token is no longer valid. This is often referred to as `notBefore` and `notAfter`. Setting these timestamps limits the lifetime of the token to the defined period. Not setting the start date or `notBefore` means the token is active as soon as it is created. Not setting the end date or `notAfter` means the token does not expire.
 
 :::note
 
-
 Dates selected are defined as 00:00 UTC of that day. For finer grained time selection, use the [API](/fundamentals/api/).
 
-
 :::
 
 ![Time to Live selection calendar](~/assets/images/fundamentals/api/ttl.png)
diff --git a/src/content/docs/fundamentals/api/index.mdx b/src/content/docs/fundamentals/api/index.mdx
index fc2b5ca4dd7c1ca..5c920d17b99595e 100644
--- a/src/content/docs/fundamentals/api/index.mdx
+++ b/src/content/docs/fundamentals/api/index.mdx
@@ -11,7 +11,7 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use the following resources to learn more about Cloudflare's REST API:
 
diff --git a/src/content/docs/fundamentals/api/reference/index.mdx b/src/content/docs/fundamentals/api/reference/index.mdx
index 2b69ab6e04041ec..51171664a4e68eb 100644
--- a/src/content/docs/fundamentals/api/reference/index.mdx
+++ b/src/content/docs/fundamentals/api/reference/index.mdx
@@ -11,6 +11,6 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/api/reference/limits.mdx b/src/content/docs/fundamentals/api/reference/limits.mdx
index 056310a63a2cf5e..af4f24a26742004 100644
--- a/src/content/docs/fundamentals/api/reference/limits.mdx
+++ b/src/content/docs/fundamentals/api/reference/limits.mdx
@@ -11,7 +11,11 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="api-rate-limits" product="fundamentals"  params={{showHeading: true}} />
+<Render
+	file="api-rate-limits"
+	product="fundamentals"
+	params={{ showHeading: true }}
+/>
 
 ## Rate limiting headers
 
diff --git a/src/content/docs/fundamentals/api/troubleshooting.mdx b/src/content/docs/fundamentals/api/troubleshooting.mdx
index f1b15f7ee9bdbf6..442eb608d3525d0 100644
--- a/src/content/docs/fundamentals/api/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/api/troubleshooting.mdx
@@ -23,15 +23,15 @@ curl "https://api.cloudflare.com/client/v4/user/tokens/verify" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "f267e341f3dd4697bd3b9f71dd96247f",
-    "status": "active",
-    "not_before": "2018-07-01T05:20:00Z",
-    "expires_on": "2020-01-01T00:00:00Z"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "f267e341f3dd4697bd3b9f71dd96247f",
+		"status": "active",
+		"not_before": "2018-07-01T05:20:00Z",
+		"expires_on": "2020-01-01T00:00:00Z"
+	}
 }
 ```
 
diff --git a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
index fc8a96817900340..7bb8ee6aba29a4d 100644
--- a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
+++ b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
@@ -8,11 +8,15 @@ products:
   - fundamentals
 ---
 
-import { Stream, GlossaryTooltip } from "~/components"
+import { Stream, GlossaryTooltip } from "~/components";
 
 To optimize your website or web application, Cloudflare provides [DNS](https://www.cloudflare.com/learning/dns/what-is-dns/) and [CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) services, so we can [reverse proxy](https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/) the web traffic to and from your domain.
 
-<Stream id="980c8494f2403b95473d2ed687b4f402" title="How Cloudflare DNS works for your domain" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public" />
+<Stream
+	id="980c8494f2403b95473d2ed687b4f402"
+	title="How Cloudflare DNS works for your domain"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public"
+/>
 
 ## DNS explained
 
diff --git a/src/content/docs/fundamentals/concepts/index.mdx b/src/content/docs/fundamentals/concepts/index.mdx
index 6a64b49f7e2d8a3..52496a8fd9b8022 100644
--- a/src/content/docs/fundamentals/concepts/index.mdx
+++ b/src/content/docs/fundamentals/concepts/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
index 31af11a5ba634c1..ffb08d179a6080f 100644
--- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
+++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
@@ -10,7 +10,7 @@ products:
 
 Internet traffic is made up of people, services, and agents requesting online resources from wherever they are hosted. Your resources may be publicly available, like a website or application that anyone on the Internet can access. Or your resources may be privately available, like an internal app or network that only your employees and partners should be able to access.
 
-Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.  
+Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.
 
 For example, you may not always want the direct traffic because it can come from malicious sources, like hackers, or in the form of [DDoS attacks](https://www.cloudflare.com/learning/ddos/ddos-attack-tools/how-to-ddos/). Additionally, depending on the location where the request originated, you want to ensure the traffic is [routed through the most efficient and fastest path](/argo-smart-routing/).
 
@@ -36,18 +36,18 @@ One example of on-ramping traffic to Cloudflare is updating your public website
 
 However, maybe you need to protect a private application that is not directly available on the Internet. In this scenario, you can:
 
-* Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
-* For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
+- Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
+- For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
 
 With these options, any request from a user device can access internal private applications via the secure private tunnels.
 
 Refer to the list below for products you can use to on-ramp traffic to Cloudflare.
 
-* [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
-* [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
-* [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
-* [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
-* The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
+- [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
+- [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
+- [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
+- [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
+- The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
 
 ### Off-ramp traffic from Cloudflare
 
@@ -61,6 +61,6 @@ You can also utilize [caching](/cache/) to help with performance. Instead of off
 
 Refer to the list below for products you can use to off-ramp traffic from Cloudflare.
 
-* [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
-* [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
-* [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
\ No newline at end of file
+- [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
+- [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
+- [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
diff --git a/src/content/docs/fundamentals/index.mdx b/src/content/docs/fundamentals/index.mdx
index 4fbceb5e645cec0..6da0f6862aab3d2 100644
--- a/src/content/docs/fundamentals/index.mdx
+++ b/src/content/docs/fundamentals/index.mdx
@@ -24,6 +24,6 @@ Refer to the list below for additional Cloudflare resources.
 - [Cloudflare blog](https://blog.cloudflare.com)
 - [Cloudflare's Go library](https://github.com/cloudflare/cloudflare-go)
 - [Cloudflare system status](https://www.cloudflarestatus.com/)
-- [Cloudflare Radar](https://radar.cloudflare.com) 
-- [Cloudflare TV](https://cloudflare.tv/schedule) 
+- [Cloudflare Radar](https://radar.cloudflare.com)
+- [Cloudflare TV](https://cloudflare.tv/schedule)
 - [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
diff --git a/src/content/docs/fundamentals/manage-domains/add-site.mdx b/src/content/docs/fundamentals/manage-domains/add-site.mdx
index 081c4aeb68c902e..e089a041cbe43bc 100644
--- a/src/content/docs/fundamentals/manage-domains/add-site.mdx
+++ b/src/content/docs/fundamentals/manage-domains/add-site.mdx
@@ -7,7 +7,13 @@ products:
   - fundamentals
 ---
 
-import { DashButton, GlossaryTooltip, Render, Stream, Details } from "~/components";
+import {
+	DashButton,
+	GlossaryTooltip,
+	Render,
+	Stream,
+	Details,
+} from "~/components";
 
 After you onboard your domain, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
 
@@ -77,6 +83,7 @@ If you encounter unexpected results when changing your nameservers, refer to the
 ## Further options
 
 ### Other DNS setups
+
 - To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/).
 - To use one or more DNS providers, refer to [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
 - Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
@@ -89,4 +96,4 @@ If you encounter unexpected results when changing your nameservers, refer to the
 
 [^2]: Enterprise customers can onboard these using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
 
-[^3]: A security feature that protects DNS records from spoofing
\ No newline at end of file
+[^3]: A security feature that protects DNS records from spoofing
diff --git a/src/content/docs/fundamentals/manage-domains/domain-version.mdx b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
index 124534a2bf1c4e0..80c3dfce25a53ae 100644
--- a/src/content/docs/fundamentals/manage-domains/domain-version.mdx
+++ b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
@@ -8,28 +8,25 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 [Version Management](/version-management/) is available for Enterprise customers and allows you to safely test, deploy, and roll back changes to your zone configurations.
 
-
 ## Enable versioning
 
-
 <Render file="enable-versioning" product="version-management" />
 
-
 ## (Optional) Create additional environments
 
 <Render file="enable-default-creation" product="version-management" />
 
 These environments each serve a specific purpose and are accessed differently: <Render file="environment-defaults" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" /> <br/>
+<Render file="create-environment-situation" product="version-management" />
+<br />
 
 For more details, refer to [Create environment](/version-management/how-to/environments/#create-environment).
 
-
 ## Update configurations
 
 <Render file="edit-version" product="version-management" />
@@ -40,7 +37,6 @@ For more details, refer to [Create environment](/version-management/how-to/envir
 
 ## Promote version
 
-
 Next, [promote](/version-management/how-to/environments/#change-environment-version) your version through your different environments.
 
 <Render file="promote-version" product="version-management" />
@@ -50,5 +46,3 @@ After promoting to each environment, test the new version in your new environmen
 ## Repeat
 
 For new changes to your zone, [create a new version](/version-management/how-to/versions/#create-version) and repeat this process.
-
-
diff --git a/src/content/docs/fundamentals/manage-domains/move-domain.mdx b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
index adb048fe514eab7..554db841218b10c 100644
--- a/src/content/docs/fundamentals/manage-domains/move-domain.mdx
+++ b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
@@ -30,13 +30,11 @@ To transfer a domain from one Cloudflare account to another, you will need:
 
 :::caution
 
-
 Before transferring an active Cloudflare domain to another Cloudflare account, you must remove any [DNSSEC configurations](/dns/dnssec/) and [add-ons or subscriptions](/billing/manage/cancel-subscription/).
 
 We also recommend [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records of your zone while it is in the previous account. Then, you can [import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the correct DNS records into the new account.
 If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
-
 :::
 
 If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](#issue-new-certificates) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
diff --git a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
index 1ac459d5abe6896..8887da35f668294 100644
--- a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
+++ b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
@@ -12,7 +12,7 @@ To troubleshoot your site, you can pause Cloudflare globally. This will send tra
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and domain.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Within **Overview**, choose **Advanced Actions** > **Pause Cloudflare on Site**.
 
@@ -22,7 +22,7 @@ The process of pausing Cloudflare takes five minutes or less. This approach is p
 Disabling a zone does not impact Spectrum applications.
 :::
 
-***
+---
 
 ## Alternatives to global pause
 
diff --git a/src/content/docs/fundamentals/manage-members/index.mdx b/src/content/docs/fundamentals/manage-members/index.mdx
index 854f89c1e4e7eca..349b6e8ec38dafd 100644
--- a/src/content/docs/fundamentals/manage-members/index.mdx
+++ b/src/content/docs/fundamentals/manage-members/index.mdx
@@ -12,7 +12,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 On any Cloudflare account, you can collaborate by adding members to your account and assigning them access via one or several policies.
 
diff --git a/src/content/docs/fundamentals/manage-members/policies.mdx b/src/content/docs/fundamentals/manage-members/policies.mdx
index 6ca9aafa9521ce1..36f550450d46ae3 100644
--- a/src/content/docs/fundamentals/manage-members/policies.mdx
+++ b/src/content/docs/fundamentals/manage-members/policies.mdx
@@ -27,8 +27,8 @@ For example, you may want to assign multiple policies and use scopes to control
 
 A set of standard API endpoints is present on every account that allow access to your members, which has recently been enhanced by a list of `resourceGroups` and `PermissionGroups`.
 
-* A `resourceGroup` is a unique identifier for the scope for which a policy applies.
-* A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
+- A `resourceGroup` is a unique identifier for the scope for which a policy applies.
+- A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
 
 Refer to the [API documentation](/api/) for more information.
 
@@ -44,4 +44,3 @@ To understand a member’s full access, check both the **Members** and **User Gr
 
 Cloudflare is actively working on improvements to consolidate this view in a future update.
 :::
-
diff --git a/src/content/docs/fundamentals/manage-members/roles.mdx b/src/content/docs/fundamentals/manage-members/roles.mdx
index c7a01704fb29721..e6e4019dccc01f9 100644
--- a/src/content/docs/fundamentals/manage-members/roles.mdx
+++ b/src/content/docs/fundamentals/manage-members/roles.mdx
@@ -28,7 +28,7 @@ Account-scoped roles apply across an entire Cloudflare account, and through all
 | Application Security Reports Read                            | Can read Application Security Reports.                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audit Logs Viewer                                            | Can view [Audit Logs](/fundamentals/account/account-security/review-audit-logs/).                                                                                                                                                                                                                                                                                                                                                 |
 | Bot Management (Account-Wide)                                | Can edit [Bot Management](/bots/plans/bm-subscription/) (including [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/)) configurations for all domains in account.                                                                                                                                                                                                                                                    |
-| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                                      |
+| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                          |
 | Cache Purge                                                  | Can purge the edge cache and allows the reading of zone settings.                                                                                                                                                                                                                                                                                                                                                                 |
 | Cloudflare Access                                            | Can edit [Cloudflare Access](/cloudflare-one/access-controls/policies/) and [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).                                                                                                                                                                                                                                                                          |
 | Cloudflare CASB                                              | Can edit [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/fundamentals/manage-members/scope.mdx b/src/content/docs/fundamentals/manage-members/scope.mdx
index ecfacf62744dfa0..e75d47dafac71c1 100644
--- a/src/content/docs/fundamentals/manage-members/scope.mdx
+++ b/src/content/docs/fundamentals/manage-members/scope.mdx
@@ -19,7 +19,7 @@ To allow for flexible combinations of access to users, Cloudflare currently has
 - **Domain groups:** Use when you have related domains that share the same access needs, for example, all production domains.
 - **Specific resources:** Use when access should be limited to individual resources.
 
-***
+---
 
 ## Choose the scope of roles
 
@@ -33,15 +33,13 @@ If you want the member to have a policy that applies across your account, use th
 
 | Field    | Value         |
 | -------- | ------------- |
-| Operator | *Include*     |
-| Type     | *All domains* |
+| Operator | _Include_     |
+| Type     | _All domains_ |
 
 :::note
 
-
 You can only assign [account-scoped roles](/fundamentals/manage-members/roles/#account-scoped-roles) as part of these types of policies
 
-
 :::
 
 ### Specific domains
@@ -50,9 +48,9 @@ If you want the member to have a policy that applies to a specific domain, use t
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | *Include*           |
-| Type     | *A specific domain* |
-| Name     | *A specific domain* |
+| Operator | _Include_           |
+| Type     | _A specific domain_ |
+| Name     | _A specific domain_ |
 
 ### Domain groups
 
@@ -64,11 +62,10 @@ To create a domain group:
 
 1. In the Cloudflare dashboard, go to the **Settings** > **Lists** page. (You must be logged in as a **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/)).
 
-    <DashButton url="/?to=/:account/configurations" />
+   <DashButton url="/?to=/:account/configurations" />
 
 2. For **Domain Group Manager**, select **Create**.
 3. Create your domain group:
-
    1. Select the domains to include.
    2. Add a **Name**.
    3. Select **Create**.
@@ -81,43 +78,40 @@ To assign a member permissions to a domain group, use the following combination
 
 | Field    | Value           |
 | -------- | --------------- |
-| Operator | *Include*       |
-| Type     | *Domain Group*  |
-| Name     | *Example Group* |
+| Operator | _Include_       |
+| Type     | _Domain Group_  |
+| Name     | _Example Group_ |
 
 :::note
 
-
 With Domain Groups, you can only assign [domain-scoped roles](/fundamentals/manage-members/roles/#domain-scoped-roles) to these members.
 
-
 :::
 
-
 ### Specific resources
 
 If you want the member to have a policy that applies to a specific resource, use the following combination of fields.
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | *Include*           |
-| Type     | *Granular* |
-| Product  | *Product Name* |
-| Resource  | *Specific Resource* |
+| Operator | _Include_           |
+| Type     | _Granular_          |
+| Product  | _Product Name_      |
+| Resource | _Specific Resource_ |
 
 #### Available scopes
 
 You can assign the following resource-specific scopes to members:
 
-| Scope                                     | Description                                                                                                                                              |
-| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Individual Access applications               | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                                   |
-| Individual Access identity providers (IdPs)  | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                                    |
-| Individual Access policies                   | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                            |
-| Individual Access service tokens             | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                           |
-| Individual Access infrastructure targets     | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/).        |
-| Individual Cloudflare Tunnel instances       | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                                |
-| Individual Cloudflare Mesh nodes             | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                          |
+| Scope                                       | Description                                                                                                                                       |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Individual Access applications              | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                            |
+| Individual Access identity providers (IdPs) | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                     |
+| Individual Access policies                  | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                     |
+| Individual Access service tokens            | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                    |
+| Individual Access infrastructure targets    | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/). |
+| Individual Cloudflare Tunnel instances      | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                         |
+| Individual Cloudflare Mesh nodes            | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                   |
 
 :::note
 When using scopes for specific resources, you can only assign [resource-scoped roles](/fundamentals/manage-members/roles/#resource-scoped-roles) to these members.
diff --git a/src/content/docs/fundamentals/manage-members/user-groups.mdx b/src/content/docs/fundamentals/manage-members/user-groups.mdx
index 6ac8ab7b5b960bc..ac0ff7d261fe721 100644
--- a/src/content/docs/fundamentals/manage-members/user-groups.mdx
+++ b/src/content/docs/fundamentals/manage-members/user-groups.mdx
@@ -10,9 +10,9 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Tabs, TabItem } from '~/components';
+import { DashButton, Tabs, TabItem } from "~/components";
 
-User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of. 
+User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of.
 
 :::note
 User Group permissions are inherited by each member of the group but are not currently reflected in the role field on the **Members** page. To view a member’s full set of permissions, check both:
@@ -23,21 +23,21 @@ User Group permissions are inherited by each member of the group but are not cur
 Cloudflare is actively working on improving this experience to make inherited and direct permissions easier to view.
 :::
 
-## Create a User Group manually 
+## Create a User Group manually
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Select the **Groups** tab.
 3. Select **Create a Group** and enter a name and description for your new group.
 4. Select **Create group** to confirm your changes. The **Group members** tab displays.
-5. Select **Add members**. 
+5. Select **Add members**.
 6. Select the relevant members you want to include in the group and select **Add to Group**.
 
 ### Assign a Permission Policy
 
-With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group. 
+With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -86,24 +86,23 @@ PAYLOAD
 
 ## Create a User Group with SCIM
 
-Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account. 
-
+Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account.
 
 :::note
 If you use the [Cloudflare dashboard SCIM integration](/fundamentals/account/account-security/scim-setup/), you can sync Groups from an upstream Identity Provider. This allows you to centralize user and group management at your identity provider.
 
 Note that when managing User Groups via SCIM:
-- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API. 
+
+- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API.
 - The integration requires one external SCIM application per Cloudflare account.
 - Cloudflare does not currently support updating user profile fields (`firstName`, `lastName`, or `email`) via SCIM. If those attributes change in your IdP, they will not be updated in Cloudflare. These values are only set during initial provisioning.
-:::
-
+  :::
 
 To set up a user group with SCIM, refer to the [Provisioning with SCIM guide](/fundamentals/account/account-security/scim-setup/).
 
 ### Set up permissions for User Groups
 
-After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it. 
+After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/docs/fundamentals/new-features/index.mdx b/src/content/docs/fundamentals/new-features/index.mdx
index 8f052702ba7fe7e..00ba70c15225ddb 100644
--- a/src/content/docs/fundamentals/new-features/index.mdx
+++ b/src/content/docs/fundamentals/new-features/index.mdx
@@ -10,8 +10,8 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare offers several RSS feeds to help you consume content programmatically.
 
-<DirectoryListing/>
+<DirectoryListing />
diff --git a/src/content/docs/fundamentals/organizations/limitations.mdx b/src/content/docs/fundamentals/organizations/limitations.mdx
index 732b548986c8775..037c78efb4df0b2 100644
--- a/src/content/docs/fundamentals/organizations/limitations.mdx
+++ b/src/content/docs/fundamentals/organizations/limitations.mdx
@@ -14,7 +14,7 @@ The following limitations apply during the public beta.
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Organization creation   | You must be a Super Administrator of an Enterprise account to create an Organization.                                                                                                       |
 | Adding accounts         | Once you've created an Organization, accounts of any plan type can be added. You must have Super Administrator access to the account, and it cannot already belong to another Organization. |
-| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                                |
+| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                              |
 | Roles                   | Organization Super Administrator is the only role available during the beta. Additional roles will be available in a future release.                                                        |
-| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                       |
+| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                                              |
 | Account removal         | Self-service account removal is not yet available. To remove an account from your Organization, contact [Cloudflare Support](/support/contacting-cloudflare-support/).                      |
diff --git a/src/content/docs/fundamentals/organizations/setup.mdx b/src/content/docs/fundamentals/organizations/setup.mdx
index 3cb26686125e379..cb9c27ffabafa59 100644
--- a/src/content/docs/fundamentals/organizations/setup.mdx
+++ b/src/content/docs/fundamentals/organizations/setup.mdx
@@ -101,11 +101,11 @@ You can manage Organizations using the [Cloudflare Terraform provider](https://r
 
 You may encounter the following errors during the setup flow. Please see below for more information on how to resolve these.
 
-| Error | Description |
-| --- | --- |
-| Organization management is only available on the Enterprise plan at this time. | You are not a member of any Enterprise accounts. |
-| You need a super admin role on an enterprise account to create an Organization. | You are not a Super Administrator of an Enterprise account. |
-| One or more of your enterprise accounts is already part of an Organization. | You may not create another organization because your accounts are already in an organization. |
-| You have reached the maximum number of organizations. | You may not create another organization because you already have one. |
-| An Organization has already been created for accounts associated with your company. Please contact your company administrator. | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
-| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it.| This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data. |
+| Error                                                                                                                                                | Description                                                                                                                                                                                                              |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Organization management is only available on the Enterprise plan at this time.                                                                       | You are not a member of any Enterprise accounts.                                                                                                                                                                         |
+| You need a super admin role on an enterprise account to create an Organization.                                                                      | You are not a Super Administrator of an Enterprise account.                                                                                                                                                              |
+| One or more of your enterprise accounts is already part of an Organization.                                                                          | You may not create another organization because your accounts are already in an organization.                                                                                                                            |
+| You have reached the maximum number of organizations.                                                                                                | You may not create another organization because you already have one.                                                                                                                                                    |
+| An Organization has already been created for accounts associated with your company. Please contact your company administrator.                       | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
+| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it. | This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data.                  |
diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx
index 297c524991656ee..aa834449efa4ed4 100644
--- a/src/content/docs/fundamentals/performance/improve-seo.mdx
+++ b/src/content/docs/fundamentals/performance/improve-seo.mdx
@@ -12,10 +12,8 @@ In practice, SEO is primarily about quality content, user experience, and not ma
 
 :::note[Tip:]
 
-
 For general guidelines around SEO, refer to [Google's recommendations](https://developers.google.com/search/docs/advanced/guidelines/overview).
 
-
 :::
 
 ## SEO improvements with Cloudflare
@@ -47,9 +45,9 @@ Depending on your domain's security settings, you might accidentally block searc
 
 If you notice SEO issues, make sure your:
 
-* [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
-* [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
-* [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
+- [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
+- [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
+- [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
 
 If you still notice issues with search engine crawlers, refer to our [Troubleshooting guide](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/).
 
@@ -57,7 +55,7 @@ If you still notice issues with search engine crawlers, refer to our [Troublesho
 
 The following characteristics do not affect your domain's SEO:
 
-* **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
-* **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
-* **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
-* **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
+- **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
+- **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
+- **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
+- **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
diff --git a/src/content/docs/fundamentals/performance/index.mdx b/src/content/docs/fundamentals/performance/index.mdx
index 4fa36b844e2eec8..8c00c87f68d593b 100644
--- a/src/content/docs/fundamentals/performance/index.mdx
+++ b/src/content/docs/fundamentals/performance/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/performance/test-speed.mdx b/src/content/docs/fundamentals/performance/test-speed.mdx
index 12ea8823571be55..246a968ab7ae1c4 100644
--- a/src/content/docs/fundamentals/performance/test-speed.mdx
+++ b/src/content/docs/fundamentals/performance/test-speed.mdx
@@ -8,7 +8,7 @@ products:
 
 Cloudflare offers several tools to test the speed of your website, as well as the speed of your Internet connection.
 
-***
+---
 
 ## Test website speed
 
@@ -24,11 +24,11 @@ If you experience any issues, make sure you are not blocking specific [user agen
 
 If your domain is not yet active on Cloudflare or you want to measure the before and after improvements of using Cloudflare, Cloudflare recommends using the following third-party tools:
 
-* [PageGym](https://pagegym.com/)
-* [GTmetrix](https://gtmetrix.com/)
-* [DebugBear](https://www.debugbear.com/test/website-speed)
-* [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
-* [WebPageTest](https://www.webpagetest.org/)
+- [PageGym](https://pagegym.com/)
+- [GTmetrix](https://gtmetrix.com/)
+- [DebugBear](https://www.debugbear.com/test/website-speed)
+- [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
+- [WebPageTest](https://www.webpagetest.org/)
 
 If you use these third-party tools, you should do the following to test website speed:
 
@@ -46,13 +46,11 @@ Based on the results of these speed tests, you may want to explore other ways to
 
 :::note
 
-
 Cloudflare does not consider Time to First Byte (TTFB) the most important measure of page load speed. If you are concerned about a slower TTFB while using Cloudflare, refer to our blog post about [Cloudflare and TTFB](http://blog.cloudflare.com/ttfb-time-to-first-byte-considered-meaningles/).
 
-
 :::
 
-***
+---
 
 ## Test Internet speed
 
diff --git a/src/content/docs/fundamentals/reference/best-practices.mdx b/src/content/docs/fundamentals/reference/best-practices.mdx
index a237a1d635c541d..6d8aa19d844e6f7 100644
--- a/src/content/docs/fundamentals/reference/best-practices.mdx
+++ b/src/content/docs/fundamentals/reference/best-practices.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account. 
+More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account.
 
 You can lose access to your account and or domain for several reasons: Death, divorce, disgruntled employee, or simply missing an email notification.
 
@@ -19,7 +19,7 @@ To help prevent loss of access:
 
 ## Relationships, partnerships, and business ventures
 
-Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active. 
+Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active.
 
 If you have a domain name or a portfolio of domain names for your business, ensuring you have a strict organization policy when it comes to vendor account creation or domain name registration is critical. The steps below will ensure your organization is the owner of the account and or domain names:
 
@@ -37,4 +37,4 @@ Most if not all online services have automated billing processes that will attem
 
 ## Deceased account holder or registrant
 
-While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you. 
+While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you.
diff --git a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
index f040e11a6251600..070a9aa8b37e5a3 100644
--- a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
+++ b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
@@ -12,12 +12,12 @@ This endpoint is managed and served by Cloudflare. It cannot be modified or cust
 
 A few examples include (but are not limited to):
 
-* [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
-* [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
-* [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
-* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
-* [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
-* [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
+- [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
+- [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
+- [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
+- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
+- [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
+- [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
 
 ## Recommended exclusions
 
diff --git a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
index dd7a00e47dce594..e99011bb53a7c81 100644
--- a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
+++ b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
@@ -13,7 +13,6 @@ Ray IDs are particularly useful when evaluating Security Events for patterns or
 Ray IDs are added as a [request header, cf-ray](/fundamentals/reference/http-headers/#cf-ray), to the connection from Cloudflare to the origin web server.
 As such the Ray IDs can be found using the Developer Tools in your browser or using curl with the `-v` option to show the headers.
 
-
 :::caution
 Ray IDs are not guaranteed to be unique for every request. In some situations, different requests may have the same Ray ID.
 :::
@@ -34,7 +33,7 @@ Please note that Security Events may use sampled data to improve performance. If
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer allows you to [build queries](/log-explorer/log-search/) for filtering specific Ray IDs.
 
diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
index 5a3fae1ade1c6bd..4d7916b94c2550d 100644
--- a/src/content/docs/fundamentals/reference/connection-limits.mdx
+++ b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), there are often two established [TCP connections](/fundamentals/reference/tcp-connections/): the first is between the requesting client to Cloudflare and the second is between Cloudflare and the origin server. Each connection has their own set of TCP and HTTP limits, which are documented below.
 
@@ -24,16 +24,16 @@ When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/h
 If you are using [Cloudflare tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), refer to [Origin configuration](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) to view or modify your connection settings.
 :::
 
-| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
-| ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/)                       |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | No                                                                             |
-| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
-| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
+| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                          | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits)        |
+| ----------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/) |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | No                                                                                    |
+| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                  | Yes                                                                                   |
+| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                 | No                                                                                    |
 
 ## Configurable limits
 
diff --git a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
index d1039a6ef7988a6..d4c1619380433f2 100644
--- a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
+++ b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
@@ -32,11 +32,11 @@ Yes, Cloudflare does collect a limited amount of data about your key. We store t
 
 Some self-signed keys and keys from certain manufacturers have been found to [not meet this requirement](https://www.chromium.org/security-keys) and should be avoided if you are minimizing your online privacy risk.
 
-***
+---
 
 For more details on how we set up Cryptographic Attestation of Personhood, refer to the [introductory blog post](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/).
 
-***
+---
 
 ## What devices are and are not allowed?
 
@@ -44,21 +44,21 @@ For more details on how we set up Cryptographic Attestation of Personhood, refer
 
 CAP supports a wide variety of hardware authenticators:
 
-* **Roaming (cross-platform) authenticators**:
-  * *Supported*: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
-  * *Examples*: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
-* **Platform authenticators:**
-  * *Examples*: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
+- **Roaming (cross-platform) authenticators**:
+  - _Supported_: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
+  - _Examples_: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
+- **Platform authenticators:**
+  - _Examples_: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
 
 ### Known limitations
 
 Most combinations of of web browsers and WebAuthn-capable authenticators will work, but there are some known compatibility issues with WebAuthn attestation that may prevent CAP from working successfully:
 
-* **Basic CAP**:
-  * *macOS desktop*: For TouchID, browser must be Safari
-  * *Android*: Browser must be Chrome
-* **CAP with Zero-Knowledge Proof**:
-  * *Apple platform authenticators* (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
+- **Basic CAP**:
+  - _macOS desktop_: For TouchID, browser must be Safari
+  - _Android_: Browser must be Chrome
+- **CAP with Zero-Knowledge Proof**:
+  - _Apple platform authenticators_ (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
 
 We are updating this list as the ecosystem evolves and as we continue to test different combinations.
 
@@ -74,16 +74,16 @@ If you do not have the necessary hardware (such as a Yubikey), you can still sol
 
 ## What are the common error codes and what do they mean?
 
-* **Unsupported\_att\_fmt**:
-  * *Cause*: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use *Firefox* and select the option to "anonymise your key".
-  * *Solution:* If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
-* **Unsupported\_issuer**:
-  * *Cause*: Your key is currently not supported.
-  * *Solution*: Use a [supported key](#allowed-devices).
+- **Unsupported_att_fmt**:
+  - _Cause_: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use _Firefox_ and select the option to "anonymise your key".
+  - _Solution:_ If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
+- **Unsupported_issuer**:
+  - _Cause_: Your key is currently not supported.
+  - _Solution_: Use a [supported key](#allowed-devices).
 
 ## Related resources
 
-* [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
-* [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
-* [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
-* [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
+- [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
+- [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
+- [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
+- [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
diff --git a/src/content/docs/fundamentals/reference/glossary.mdx b/src/content/docs/fundamentals/reference/glossary.mdx
index 32fb01bd11d1fa6..0656993c5d88b81 100644
--- a/src/content/docs/fundamentals/reference/glossary.mdx
+++ b/src/content/docs/fundamentals/reference/glossary.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's documentation.
 
diff --git a/src/content/docs/fundamentals/reference/google-analytics.mdx b/src/content/docs/fundamentals/reference/google-analytics.mdx
index 2f936dae6e12865..1e67ecfa7422f9b 100644
--- a/src/content/docs/fundamentals/reference/google-analytics.mdx
+++ b/src/content/docs/fundamentals/reference/google-analytics.mdx
@@ -19,10 +19,8 @@ Cloudflare only affects analytics tools that read logs directly from your web se
 
 :::note
 
-
 To troubleshoot potential issues with Google Analytics, refer to [Common GA setup mistakes](https://support.google.com/analytics/answer/1009683).
 
-
 :::
 
 ## Zaraz
@@ -31,8 +29,6 @@ As an alternative to the standard setup of Google Analytics with tag/snippet, Cl
 
 :::note
 
-
 Details about features of Google Analytics that are unavailable with Zaraz can be found in [Zaraz FAQ](/zaraz/faq/#tools)
 
-
 :::
diff --git a/src/content/docs/fundamentals/reference/index.mdx b/src/content/docs/fundamentals/reference/index.mdx
index edf24d7ad793faf..e239c0c053a0085 100644
--- a/src/content/docs/fundamentals/reference/index.mdx
+++ b/src/content/docs/fundamentals/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
index 15fcb26bc9607e2..1587fb70d0d1b81 100644
--- a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
+++ b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
@@ -10,14 +10,15 @@ products:
   - fundamentals
 ---
 
-Cloudflare's first iteration of SCIM integration introduced a concept called *Virtual Groups*, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.  
+Cloudflare's first iteration of SCIM integration introduced a concept called _Virtual Groups_, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.
+
+While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:
 
-While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:  
 - They could not be renamed or deleted in the IdP.
 - They could not be managed within Cloudflare.
 - Functionally, managing a Virtual Group was equivalent to syncing users and editing each member’s policies individually.
 
-With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.  
+With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.
 
 If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtual Group from your IdP to Cloudflare, no action is needed.
 
@@ -32,9 +33,7 @@ If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtua
 
 ## More resources
 
-* [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)  
-* [User Groups documentation](/fundamentals/manage-members/user-groups/)  
-* [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)  
-* [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)  
-
-
+- [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)
+- [User Groups documentation](/fundamentals/manage-members/user-groups/)
+- [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)
+- [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)
diff --git a/src/content/docs/fundamentals/reference/partners.mdx b/src/content/docs/fundamentals/reference/partners.mdx
index 5e6be4d2e93fd82..a066448644a58cd 100644
--- a/src/content/docs/fundamentals/reference/partners.mdx
+++ b/src/content/docs/fundamentals/reference/partners.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 [Cloudflare Technology Partners](https://www.cloudflare.com/partners/technology-partners/) offer purpose-built integrations with our products, providing expanded functionality for our users. Learn how to configure these integrations with our tutorials and how-to guides.
 
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
index 7e65a2e16b6a01a..106282e9575100c 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
@@ -17,7 +17,7 @@ Unfortunately, while most people respect these limitations and understand they e
 
 The following are some recommendations for using Cloudflare's services based on what may have brought you to this page.
 
-***
+---
 
 ## I'm a website operator and my content was redirected for Terms of Service violations
 
@@ -25,9 +25,9 @@ If you are on a Free, Pro, or Business Plan and your application appears to be s
 
 ## Options for web admins to remove redirects
 
-* **Serve redirected content from a grey-clouded sub-domain**
+- **Serve redirected content from a grey-clouded sub-domain**
 
-* **Serve redirected content from a paid service as outlined below**
+- **Serve redirected content from a paid service as outlined below**
 
 ## Delivering videos with Cloudflare using paid products
 
@@ -43,14 +43,14 @@ To get started with Stream, visit **Stream** from your Dashboard or [sign up](ht
 
 [Stream Delivery](https://www.cloudflare.com/products/stream-delivery/) offers caching and delivery of video content through Cloudflare data centers around the globe. This CDN feature is only available on the Cloudflare Enterprise Plan. Please [contact sales](https://www.cloudflare.com/products/stream-delivery/#) if you'd like to explore this option.
 
-***
+---
 
 ## Getting information on the content you are delivering
 
 If you need more information about the content your zone is serving (for example, content type), you can use the following tools:
 
-* Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
-* Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
+- Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
+- Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
 
 ![Cache Analytics - Identify type of traffic being transferred](~/assets/images/support/traffic-types.png)
 
@@ -58,6 +58,6 @@ If you need more information about the content your zone is serving (for example
 
 If you have additional questions about redirection (e.g. if you believe your content was redirected in error and have supporting evidence), file a [support ticket](https://dash.cloudflare.com/redirect?account=support) and include the following information:
 
-* Name of your domain
-* Description of the problem
-* Description of the content you're serving through Cloudflare's network
+- Name of your domain
+- Description of the problem
+- Description of the content you're serving through Cloudflare's network
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
index 1187f88b49dbde0..a0e6c30419d4e4c 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/redirects.mdx b/src/content/docs/fundamentals/reference/redirects.mdx
index cd7ef6cc592e166..faf74ce66f949a6 100644
--- a/src/content/docs/fundamentals/reference/redirects.mdx
+++ b/src/content/docs/fundamentals/reference/redirects.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare offers a variety of ways to perform <GlossaryTooltip term="redirect">URL redirects</GlossaryTooltip>, which tell a visitor's browser that the location of a page has been changed.
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
index c5e1d5484357c60..3a4e6c9b913f065 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
@@ -18,6 +18,6 @@ Our Trust & Safety team sends abuse reports to the domain owner or the abuse poi
 
 To assist with timely resolution and avoid potential service interruptions:
 
-* Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
-* Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
-* Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
+- Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
+- Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
+- Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
diff --git a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
index b216ceff2722d04..5c3cff418dfa842 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
@@ -13,31 +13,31 @@ products:
 
 Use Cloudflare's [online abuse form](https://abuse.cloudflare.com/) to report different types of abuse.
 
-***
+---
 
 ## DMCA complaints
 
 Valid [Digital Millennium Copyright Act (DMCA)](https://www.copyright.gov/dmca/) complaints must provide all of the following details:
 
-* A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
-* Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
-* Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
-* Your contact information, including your address, telephone number, and email address.
-* A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
-* A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
+- A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
+- Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
+- Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
+- Your contact information, including your address, telephone number, and email address.
+- A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
+- A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
 
-***
+---
 
 ## Phishing
 
 Valid phishing reports must provide all of the following details:
 
-* The domain in question.
-* The specific link to the phishing page.
+- The domain in question.
+- The specific link to the phishing page.
 
 After Cloudflare confirms existence of the phishing page, Cloudflare provides a warning page to visitors accessing the phishing link. Cloudflare also notifies the site owner to clean the malicious files from their origin web server.
 
-***
+---
 
 ## Trademark infringement
 
@@ -45,7 +45,7 @@ Cloudflare only acknowledges abuse reports from trademark holders or their legal
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
-***
+---
 
 ## Malware sites
 
@@ -53,7 +53,7 @@ Legitimate reports of malware URLs are blocked from loading via Cloudflare.
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
-***
+---
 
 ## Child exploitation material
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/index.mdx b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
index 1607f978b92b9c9..211b1f859b80956 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/index.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
@@ -19,7 +19,7 @@ When it comes to reports of abuse on websites that use our services, our ability
 
 ## Resources
 
-* [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
-* [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
-* [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
-* [Submit abuse report](https://www.cloudflare.com/abuse/form)
+- [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
+- [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
+- [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
+- [Submit abuse report](https://www.cloudflare.com/abuse/form)
diff --git a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
index bd36756a9df63e7..3da4ad19a0ab288 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
@@ -19,8 +19,10 @@ Cloudflare offers three ways for you to submit an abuse report:
 - Public form: Refer to [Submit an Abuse Report](https://abuse.cloudflare.com/) to learn more.
 - The Cloudflare dashboard, on the **Abuse reports** page.
 
-    <DashButton url="/?to=/:account/abuse-reports" />
-  Optionally, filter the reports based on date, report status, report type, and domain.
+  <DashButton url="/?to=/:account/abuse-reports" />
+  Optionally, filter the reports based on date, report status, report type, and
+  domain.
+
 - The Cloudflare API: Use the [Abuse Reports API](/api/resources/abuse_reports/) to submit an abuse report.
 
 ## View submitted reports
@@ -29,7 +31,7 @@ Users with Admin, Super Admin, or Trust & Safety roles can view any abuse report
 
 1. In the Cloudflare dashboard, go to the **Abuse reports** page.
 
-    <DashButton url="/?to=/:account/abuse-reports" />
+   <DashButton url="/?to=/:account/abuse-reports" />
 
 2. Optionally, filter the reports based on date, report status, report type, and domain.
 
@@ -37,6 +39,6 @@ If there was a mitigation against your website due to the abuse allegation, you
 
 ## Receive notifications
 
-You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites. 
+You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites.
 
-For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
\ No newline at end of file
+For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
diff --git a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
index 1b46a73b2f45f59..31a4b85d98924b4 100644
--- a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
+++ b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
@@ -21,7 +21,7 @@ These lifecycle stages may be referred to in different terms across Cloudflare p
 
 ### Early access
 
-During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will  often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
+During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
 
 ### Active support
 
@@ -41,13 +41,13 @@ While Cloudflare cannot provide support for all older versions of our libraries
 
 The SDK ecosystem follows semantic versioning, which defines versions as follows:
 
-* MAJOR version when there are backward-incompatible changes made.
-* MINOR version when functionality is added in a backward compatible-manner.
-* PATCH version for backward-compatible bug fixes (without any improvements).
+- MAJOR version when there are backward-incompatible changes made.
+- MINOR version when functionality is added in a backward compatible-manner.
+- PATCH version for backward-compatible bug fixes (without any improvements).
 
 :::caution
 
-As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases *may* contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
+As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases _may_ contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
 
 If this is not suitable for your use case, pin to a known good version or use the previous major version of the library.
 :::
@@ -62,5 +62,5 @@ Alongside the automatic migration approach, we provide documentation on the chan
 
 ## Related resources
 
-* [Semantic versioning definitions](https://semver.org/)
-* [Cloudflare's Terraform documentation](/terraform/)
+- [Semantic versioning definitions](https://semver.org/)
+- [Cloudflare's Terraform documentation](/terraform/)
diff --git a/src/content/docs/fundamentals/reference/tcp-connections.mdx b/src/content/docs/fundamentals/reference/tcp-connections.mdx
index 2a10e61edd13149..7662f578f5197a6 100644
--- a/src/content/docs/fundamentals/reference/tcp-connections.mdx
+++ b/src/content/docs/fundamentals/reference/tcp-connections.mdx
@@ -18,7 +18,7 @@ accTitle: Connections with Cloudflare
 A[Visitor] <-- Connection --> B[Cloudflare global network] <-- Connection --> C[Origin server]
 ```
 
-<br/>
+<br />
 
 User traffic is routed to the nearest Cloudflare data center based on the shortest [Border Gateway Protocol](https://www.cloudflare.com/learning/security/glossary/what-is-bgp/) (BGP) path, thanks to [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) routing. Cloudflare then processes the request. In case a request is not served from Cloudflare’s data centers, Cloudflare will open a connection to the origin server to forward the request.
 
@@ -36,10 +36,8 @@ For connections to users, Cloudflare has a default idle timeout of 400 seconds.
 
 :::note
 
-
 Be aware that even if there are keep-alives, Cloudflare cannot guarantee to keep a connection, since besides idleness, there are other reasons, like capacity balancing, data center maintenance or node restarts that can cause disconnections. Having this in mind, applications should be structured to handle disconnections gracefully.
 
-
 :::
 
 TCP connection settings between the user and Cloudflare, and between Cloudflare and Origin can be customized for Enterprise customers. Reach out to your account team for more details.
diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx
index b9e4589f7feeebc..7f18e62f0b0f805 100644
--- a/src/content/docs/fundamentals/reference/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/reference/troubleshooting.mdx
@@ -15,42 +15,42 @@ When you [set up Cloudflare](/fundamentals/account/), you may experience the fol
 
 ## Error messages
 
-* [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
-* [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
-* [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
-* [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
-* [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
-* [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
-* [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
-* [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
+- [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
+- [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
+- [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
+- [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
+- [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
+- [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
+- [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
+- [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
 
 ## Behavior
 
-* [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
-* [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
-* [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
-* [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
-* [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
-* [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
-* [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
+- [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
+- [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
+- [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
+- [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
+- [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
+- [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
+- [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
 
 ## Cloudflare
 
-* [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
-* [Contact Cloudflare support](/support/contacting-cloudflare-support/)
-* [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
+- [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
+- [Contact Cloudflare support](/support/contacting-cloudflare-support/)
+- [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
 
 ## General resources
 
-* [DNS FAQ](/dns/faq/)
-* [SSL/TLS FAQ](/ssl/faq/)
+- [DNS FAQ](/dns/faq/)
+- [SSL/TLS FAQ](/ssl/faq/)
 
 ## Is Cloudflare attacking me
 
 Two common scenarios falsely lead to the perception that Cloudflare is attacking your site:
 
-* Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
-* The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
+- Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
+- The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
 
 Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare's network.
 
diff --git a/src/content/docs/fundamentals/security/index.mdx b/src/content/docs/fundamentals/security/index.mdx
index 530676a405630c9..6998badd02eba4c 100644
--- a/src/content/docs/fundamentals/security/index.mdx
+++ b/src/content/docs/fundamentals/security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/security/pci-scans.mdx b/src/content/docs/fundamentals/security/pci-scans.mdx
index 6d67add60af9062..267a0d3f3e9bc55 100644
--- a/src/content/docs/fundamentals/security/pci-scans.mdx
+++ b/src/content/docs/fundamentals/security/pci-scans.mdx
@@ -11,10 +11,8 @@ products:
 
 :::note
 
-
 Cloudflare is PCI certified as a Data Processor. Refer to [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities) and Cloudflare's PCI DSS Responsibility Matrix for more information.
 
-
 :::
 
 PCI scanners are tools used to identify security weaknesses. When a business undergoes a compliance audit, PCI scan results are used for compliance verification.
@@ -39,7 +37,7 @@ However, customers can easily block all unwanted traffic to these ports by using
 
 You can find all our public compliance resources in the following pages:
 
-* [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
-* [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
+- [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
+- [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
 
 You can access Compliance documents in the Cloudflare dashboard by selecting your account where you are a Super Administrator and then navigating to **Support** > **Compliance Documents**.
diff --git a/src/content/docs/fundamentals/security/under-ddos-attack.mdx b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
index fec2c129035f0eb..2b0568e28ce011d 100644
--- a/src/content/docs/fundamentals/security/under-ddos-attack.mdx
+++ b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
@@ -7,7 +7,7 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="ddos-definition-and-diagram" product="learning-paths" />
 
@@ -15,9 +15,9 @@ import { Render } from "~/components"
 
 Common signs that you are under DDoS attack include:
 
-* Your site is offline or slow to respond to requests.
-* Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
-* Strange requests appear in your origin web server logs that do not match normal visitor behavior.
+- Your site is offline or slow to respond to requests.
+- Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
+- Strange requests appear in your origin web server logs that do not match normal visitor behavior.
 
 :::note
 
diff --git a/src/content/docs/fundamentals/user-profiles/2fa.mdx b/src/content/docs/fundamentals/user-profiles/2fa.mdx
index 57dc48b28cb5962..62092f62c5e8c8f 100644
--- a/src/content/docs/fundamentals/user-profiles/2fa.mdx
+++ b/src/content/docs/fundamentals/user-profiles/2fa.mdx
@@ -6,12 +6,10 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components"
-
+import { DashButton, Render } from "~/components";
 
 <Render file="2fa-enable" product="support" />
 
-
 ## Configure security key authentication for two-factor Cloudflare login
 
 :::caution
@@ -111,7 +109,7 @@ Regenerating your backup codes will invalidate your previous codes.
 
 1. Log in to the Cloudflare dashboard.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Authentication**.
@@ -129,17 +127,17 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 1. Log in to the Cloudflare dashboard.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Profile**.
 3. Select the **Authentication**.
    - To remove your security key:
-      1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
-      2. Select **Delete**.
-      3. Enter your Cloudflare password, then select **Remove**.
+     1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
+     2. Select **Delete**.
+     3. Enter your Cloudflare password, then select **Remove**.
    - To remove your TOTP mobile application authentication:
-      1. Select **Delete method** in the **Mobile App Authentication** card.
-      2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
+     1. Select **Delete method** in the **Mobile App Authentication** card.
+     2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
 
 ![how to disable your TOTP mobile application authentication.](https://developerdocsgifs.cloudflaretraining.com/resampled_5fps_disable_mobile_auth_v2_final.gif)
 
@@ -147,18 +145,18 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 If you lose access to a mobile device, security key, or authentication code, you can solve these issues by using a backup code or retrieving a backup code from your preferred authentication app.
 
-Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid\&hl=en\&oco=0).
+Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid&hl=en&oco=0).
 
 When setting up 2FA, you should have saved your backup codes in a secure location. To restore lost access using a Cloudflare backup code:
 
 1. Retrieve the backup code from where you stored it.
 2. Go to the [Cloudflare login page](https://dash.cloudflare.com/login), enter your username and password and select **Log in**.
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 3. You should see a page titled **Two-Factor Authentication**
-   * If it has a text box, enter one of your backup codes and select **Log in**.
-   * If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
+   - If it has a text box, enter one of your backup codes and select **Log in**.
+   - If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
 
 :::note
 
@@ -167,7 +165,7 @@ Once you use a backup code, it becomes invalid.
 
 ## Related resources
 
-* [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en\&ref_topic=2954345\&co=GENIE.Platform%3DiOS\&oco=0)
-* [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
-* [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
-* [Account recovery](/fundamentals/user-profiles/account-recovery/)
+- [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en&ref_topic=2954345&co=GENIE.Platform%3DiOS&oco=0)
+- [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
+- [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
+- [Account recovery](/fundamentals/user-profiles/account-recovery/)
diff --git a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
index 31d166bcf9914c5..05298913d04f3cd 100644
--- a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
+++ b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
@@ -12,7 +12,7 @@ If you do not have access to your 2FA account or backup codes and cannot current
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
-      <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. On the **Two-Factor Authentication** page, select **Try recovery** on **Lost all 2FA devices and backup codes?**.
 3. Select **Begin recovery**.
@@ -24,8 +24,8 @@ If you see **Device verified**, you will receive an email within 3-5 days with i
 
 If you see **Device verification failed**, you may be able to try again considering the following:
 
-   * If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
-   * Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
-   * You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
+- If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
+- Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
+- You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
 
-If you are still unable to verify your device, follow the instructions to *Request manual verification* on the **Device verification failed** page.
+If you are still unable to verify your device, follow the instructions to _Request manual verification_ on the **Device verification failed** page.
diff --git a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
index f848ead54c25ce4..7e8b24b3c6504bf 100644
--- a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
+++ b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
@@ -62,7 +62,7 @@ If you forget the email address associated with your application:
 
 ## Forgot your password
 
-You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option. 
+You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option.
 
 If you forget the password associated with your email address:
 
diff --git a/src/content/docs/fundamentals/user-profiles/customize-account.mdx b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
index e2069315ad718cd..c7b80fefce89a7c 100644
--- a/src/content/docs/fundamentals/user-profiles/customize-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
@@ -35,9 +35,9 @@ Adjust how the Cloudflare dashboard appears on your device.
 
 2. Go to **Profile**.
 3. From **Settings** > **Dashboard appearance**, choose a value:
-   * **Dark**: Defaults to darker colors.
-   * **Light**: Defaults to lighter colors.
-   * **Use system setting**: Defaults to the option used on your device.
+   - **Dark**: Defaults to darker colors.
+   - **Light**: Defaults to lighter colors.
+   - **Use system setting**: Defaults to the option used on your device.
 
 Your dashboard display will update to the new appearance setting automatically.
 
diff --git a/src/content/docs/fundamentals/user-profiles/delete-account.mdx b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
index 94289a564a45da4..09b79d815f25fa7 100644
--- a/src/content/docs/fundamentals/user-profiles/delete-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
@@ -28,7 +28,7 @@ Before Cloudflare can cancel your account and delete your personal information,
 - [Disable auto-renew for your Registrar domain(s)](/registrar/account-options/renew-domains#set-up-automatic-renewals)
 - If you are using a Cloudflare [CNAME setup](/dns/zone-setups/partial-setup/), [update your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) at your DNS provider to point to your website IPs or hostnames instead of Cloudflare.
 - [Delete payment information](/billing/get-started/update-billing-info/#delete-a-payment-method)
-- (*Optional*) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
+- (_Optional_) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
 
 ## Delete your Cloudflare account
 
@@ -49,7 +49,7 @@ All domains, subscriptions, and billing information on your account will be remo
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Delete this user**.
@@ -61,4 +61,3 @@ All domains, subscriptions, and billing information on your account will be remo
 Cloudflare will purge your personal information within a year of a deletion request unless required to retain it for legal obligations (such as ongoing abuse investigations or pending litigation). Refer to the [Cloudflare Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/) for further information about the deletion of personal information following the cancellation of your account.
 
 :::
-
diff --git a/src/content/docs/fundamentals/user-profiles/login.mdx b/src/content/docs/fundamentals/user-profiles/login.mdx
index e81d66c7afbac91..9152dcc59e82381 100644
--- a/src/content/docs/fundamentals/user-profiles/login.mdx
+++ b/src/content/docs/fundamentals/user-profiles/login.mdx
@@ -27,6 +27,7 @@ Enter your email address and password.
 If your admin has enabled [enabled SSO](/fundamentals/manage-members/dashboard-sso/), enter your email address.
 
 ### Social login
+
 Social login allows you to sign in with a trusted 3rd party sign in service such as Apple, Google, or GitHub. Social login is only available for accounts with a verified email address, or accounts that signed up via social login initially. If you have additionally configured two-factor authentication on your account, that will be presented in addition to any login and two-factor authentication provided by the social login provider.
 
 :::note
@@ -43,12 +44,11 @@ To set a password, go to [Forgot Password](https://dash.cloudflare.com/forgot-pa
 You will receive an email with instructions to set your password. Once created, use your email and the new password to log in.
 :::
 
-
 #### Sign in with Apple
 
-* **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
+- **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
 
-* **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
+- **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
 
 If you chose to share your email when creating a Cloudflare account with Apple ID and want to set a password and obtain an API key, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) login page and select **Forgot your password?** to trigger a password reset email.
 
@@ -73,4 +73,3 @@ If you created your Cloudflare account using Apple Relay and decide to change yo
 - Sign in with GitHub uses the [Primary email address](https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address) which is set on your GitHub account. If you change your primary email address in GitHub, you will not be able to log into your Cloudflare account using GitHub social login.
 
 - If you select **Sign in with GitHub** with an email that does not already have a Cloudflare account associated with it, Cloudflare will create a new account and allow you to sign in using **Sign in with GitHub** option moving forward.
-
diff --git a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
index ce1ca48798a83bb..8dfe5802aeb8a3b 100644
--- a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
+++ b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
@@ -25,14 +25,14 @@ Email MFA can only be disabled by enabling [two-factor authentication](/fundamen
 
 ## Troubleshoot MFA
 
-Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from *[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)*\_**.**\_
+Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from _[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)_\_**.**\_
 
 Other times, emails are rejected by the recipient email service. Cloudflare will try again it will flag your email address after several attempts and no further emails will be sent.
 
 If you still do not receive an email after ensuring your email service is not flagging Cloudflare, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
 
-***
+---
 
 ## Related resources
 
-* [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
+- [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
index b3fc9378ed0e2b3..430a7d78421a34a 100644
--- a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
+++ b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
@@ -34,7 +34,7 @@ If you cannot find your verification email or your email has expired, request an
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified).
@@ -47,11 +47,11 @@ To check your verification:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, your email address will have `(verified)` added after it.
 
 If your email is still not verified, try clicking the verification link in a different browser or a private window.
 
-If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
\ No newline at end of file
+If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
diff --git a/src/content/docs/google-tag-gateway/index.mdx b/src/content/docs/google-tag-gateway/index.mdx
index df04561d2b6e7ba..313bd3117c71010 100644
--- a/src/content/docs/google-tag-gateway/index.mdx
+++ b/src/content/docs/google-tag-gateway/index.mdx
@@ -8,8 +8,8 @@ sidebar:
   order: 1
 tags:
   - Google
-
 ---
+
 import { DashButton } from "~/components";
 
 Google tag gateway for advertisers allows website owners using Cloudflare as a CDN to get the most out of ad measurement tools with just a few clicks. It allows you to deploy Google scripts using your own domain, enhancing data privacy and improving signal measurement recovery. Unlike standard setups where tags are requested from a Google domain, Google tag gateway for advertisers loads the tag from your domain and sends measurement events to your domain, where they are forwarded to Google.
@@ -25,6 +25,7 @@ Google tag gateway for advertisers is free to use. Requests routed through the g
 Site owners can enable this feature in one of two ways: through the Google tag console, or through the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/tag-management/google-tag-gateway).
 
 ### Configure in Google Tag Manager
+
 The fastest way to set up Google tag gateway for advertisers is in Google Tag Manager. [Follow the steps in Google's Help Center](https://support.google.com/analytics/answer/16061641).
 
 ### Configure in the Cloudflare dashboard
@@ -43,7 +44,7 @@ Your Cloudflare dashboard user must have one of the following [Account Roles](/f
 ![Google tag gateway for advertisers configuration](~/assets/images/google-tag-gateway/google-tag-configuration.png)
 
 4. Add your Google tag ID and the path on your website reserved for the Google tag.
-The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
+   The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
 
 ![Add to ID and path](~/assets/images/google-tag-gateway/google-tag-id-path.png)
 
@@ -62,6 +63,7 @@ If you need different tag behavior for specific subdomains (for example, only fi
 This approach lets you maintain a single zone-wide Google tag gateway configuration while still customizing tag behavior per subdomain.
 
 ## Related resources
+
 - [Google Developer Docs: Set up Google tag gateway for advertisers](https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide?setup=auto)
 - [Google Help Center: Set up Google tag gateway for advertisers in the Google tag with Cloudflare](https://support.google.com/tagmanager/answer/16061406)
 - [Google Help Center: Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare](https://support.google.com/analytics/answer/16061641)
diff --git a/src/content/docs/health-checks/concepts/health-checks-regions.mdx b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
index 2cafe5f8e78ba1a..65a3eecbc16b25f 100644
--- a/src/content/docs/health-checks/concepts/health-checks-regions.mdx
+++ b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
@@ -6,7 +6,6 @@ products:
   - health-checks
 sidebar:
   order: 4
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/health-checks/concepts/index.mdx b/src/content/docs/health-checks/concepts/index.mdx
index 63214119f1c7c7c..4bf31c3559d964a 100644
--- a/src/content/docs/health-checks/concepts/index.mdx
+++ b/src/content/docs/health-checks/concepts/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts involved in Cloudflare Health Checks.
 
diff --git a/src/content/docs/health-checks/health-checks-analytics.mdx b/src/content/docs/health-checks/health-checks-analytics.mdx
index 0270a58b2a3f59a..532c92b0c481ca8 100644
--- a/src/content/docs/health-checks/health-checks-analytics.mdx
+++ b/src/content/docs/health-checks/health-checks-analytics.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
 tags:
   - Analytics
-
 ---
 
-import { AvailableNotifications, Render, DashButton } from "~/components"
+import { AvailableNotifications, Render, DashButton } from "~/components";
 
 <Render file="smart-shield-callout" product="smart-shield" />
 
diff --git a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
index 6ac6065ecb7a80e..7f000b24d42b7cc 100644
--- a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
+++ b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
@@ -6,10 +6,9 @@ products:
   - health-checks
 sidebar:
   order: 9
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 You can [configure notification emails](/health-checks/how-to/health-checks-notifications/#configure-notifications) to be alerted when the Health Check detects that there is a change in the status of your origin server. Cloudflare will send you an email within seconds so you can take the necessary action before customers are impacted.
 
@@ -31,12 +30,10 @@ The email provides information to determine what caused the health status change
 
 :::note
 
-
 A notification is only sent after a change of status in the majority of all selected region(s).
 
 For a single region, this will be 2 of 3 data centers. With 13 regions selected, this will be 7 of 13 regions.
 
-
 :::
 
 See [common error codes](/health-checks/health-checks-analytics/#common-error-codes) for more information regarding the cause of any changes to your Health Check.
diff --git a/src/content/docs/health-checks/how-to/index.mdx b/src/content/docs/health-checks/how-to/index.mdx
index 0ee79dad8ccb82c..db9952b5952d517 100644
--- a/src/content/docs/health-checks/how-to/index.mdx
+++ b/src/content/docs/health-checks/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 See the following pages for more information about standalone Health Checks:
 
diff --git a/src/content/docs/health-checks/how-to/zone-lockdown.mdx b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
index 591c602337a1232..a4478cdeee2a61a 100644
--- a/src/content/docs/health-checks/how-to/zone-lockdown.mdx
+++ b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Zone lockdown migration guide
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
+<Render file="zone-lockdown" product="smart-shield" />
diff --git a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
index c65b5e2f272d5e2..2062eeebed2f06a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
@@ -34,7 +34,7 @@ npm i -D drizzle-kit tsx @types/node
 
 Add the required Node.js compatibility flags and Hyperdrive binding to your `wrangler.jsonc` file:
 
-<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive"/>
+<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive" />
 
 ## 2. Configure Drizzle
 
@@ -75,7 +75,7 @@ import { users } from "./db/schema";
 
 export interface Env {
 	HYPERDRIVE: Hyperdrive;
-  }
+}
 
 export default {
 	async fetch(request, env, ctx): Promise<Response> {
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
index e193a5b10a6b006..2d0266f83dce9cd 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
@@ -25,12 +25,13 @@ You can connect Hyperdrive to any existing Prisma Postgres database by using you
 2. Select **Connect to your database** > **Any client**.
 3. Select **Generate database credentials**. Copy the connection string for your Prisma Postgres database.
 4. Edit the connection string to make it compatible with Hyperdrive.
-  - Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
-  - The final string will look like:
-  
-   ```txt ins="database_name"
-   postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
-    ```   
+
+- Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
+- The final string will look like:
+
+````txt ins="database_name"
+postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
+ ```
 
 :::note
 
@@ -38,7 +39,7 @@ An alternative to the Prisma Data Platform is to use the [`create-db`](https://w
 
 ```bash
 npx create-db@latest
-```
+````
 
 :::
 
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
index 9c1996a98116a4a..72797b0b520501a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
@@ -32,7 +32,7 @@ With a database user, password, database endpoint (hostname and port) and databa
 
 :::note
 
-When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers. 
+When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers.
 
 :::
 
diff --git a/src/content/docs/hyperdrive/observability/troubleshooting.mdx b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
index 4ef6f14661763a2..1c6ad7bce772665 100644
--- a/src/content/docs/hyperdrive/observability/troubleshooting.mdx
+++ b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
@@ -32,10 +32,10 @@ Hyperdrive will also issue an empty test query, a `;` in PostgreSQL, to validate
 
 Hyperdrive may also emit `Failed to connect to the provided database` when it fails to connect to the database when attempting to create a Hyperdrive configuration. This is possible when the TLS (SSL) certificates are misconfigured. Here is a non-exhaustive table of potential failure to connect errors:
 
-| Error message | Details               | Recommended fixes |
-| ---------- | -------------------- | --------------------- |
-| Server return error and closed connection. | This message occurs when you attempt to connect to a database that has client certificate verification enabled. | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
-| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database. |
+| Error message                                 | Details                                                                                                                                                                                               | Recommended fixes                                                                                                                                                     |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Server return error and closed connection.    | This message occurs when you attempt to connect to a database that has client certificate verification enabled.                                                                                       | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
+| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database.                                      |
 
 ## Connection errors
 
@@ -46,16 +46,14 @@ Hyperdrive errors that do not map 1:1 with an error message code [documented by
 
 Hyperdrive may also encounter `ErrorResponse` wire protocol messages sent by your database. Hyperdrive will pass these errors through unchanged when possible.
 
-
-
 ### Hyperdrive specific errors
 
-| Error Message                                          | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
-| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Internal error.`                                      | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                                                               |
-| `Failed to acquire a connection from the pool.`        | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
-| `Server connection attempt failed: connection_refused` | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
-| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases. | Remove prepared statements from your MySQL queries. |
+| Error Message                                                           | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
+| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Internal error.`                                                       | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                    |
+| `Failed to acquire a connection from the pool.`                         | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
+| `Server connection attempt failed: connection_refused`                  | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
+| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases.                            | Remove prepared statements from your MySQL queries.                                                                                                                                                                                                                                            |
 
 ### Node errors
 
@@ -75,8 +73,8 @@ If your queries are not being cached despite Hyperdrive having caching enabled,
 
 ### Driver errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| Error Message                                              | Details                                                                                                                                              | Recommended fixes                                                                                                                                                                               |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `Code generation from strings disallowed for this context` | The database driver you are using is attempting to use the `eval()` command, which is unsupported on Cloudflare Workers (common in `mysql2` driver). | Configure the database driver to not use `eval()`. See how to [configure `mysql2` to disable the usage of `eval()`](/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/mysql2/). |
 
 ### Stale connection and I/O context errors
@@ -85,46 +83,46 @@ These errors occur when a database client or connection is created in the global
 
 #### Workers runtime errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.` | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function. |
-| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request. | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
+| Error Message                                                                                                                                                                                                                  | Details                                                                                                                     | Recommended fixes                                                                                                                                                             |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.`                                           | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function.                                                                                      |
+| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request.                         | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
 
 #### node-postgres (`pg`) errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Connection terminated` | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request. | Create a new `Client` inside your handler instead of reusing one from a prior request. |
-| `Connection terminated unexpectedly` | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request. |
-| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests). | Create a new `Client` inside your handler. Do not store clients in global variables. |
-| `Client was closed and is not queryable` | A query was attempted on a client whose `.end()` method was already called. | Create a new `Client` inside your handler instead of reusing one. |
-| `Cannot use a pool after calling end on the pool` | `pool.connect()` was called on a `Pool` instance that has already been ended. | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
-| `Client has already been connected. You cannot reuse a client.` | `client.connect()` was called on a client that was already connected in a previous invocation. | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected. |
+| Error Message                                                    | Details                                                                                                                                         | Recommended fixes                                                                                                                         |
+| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `Connection terminated`                                          | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request.                                     | Create a new `Client` inside your handler instead of reusing one from a prior request.                                                    |
+| `Connection terminated unexpectedly`                             | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request.                                                                              |
+| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests).                                                 | Create a new `Client` inside your handler. Do not store clients in global variables.                                                      |
+| `Client was closed and is not queryable`                         | A query was attempted on a client whose `.end()` method was already called.                                                                     | Create a new `Client` inside your handler instead of reusing one.                                                                         |
+| `Cannot use a pool after calling end on the pool`                | `pool.connect()` was called on a `Pool` instance that has already been ended.                                                                   | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
+| `Client has already been connected. You cannot reuse a client.`  | `client.connect()` was called on a client that was already connected in a previous invocation.                                                  | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected.                                            |
 
 #### Postgres.js (`postgres`) errors
 
 Postgres.js error messages include the error code and the target host. The `code` property on the error object contains the error code.
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `write CONNECTION_ENDED <host>:<port>` | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`. | Create a new `postgres()` instance inside your handler. |
-| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request. |
-| `write CONNECTION_CLOSED <host>:<port>` | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`. | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
+| Error Message                              | Details                                                                                                                                                                                 | Recommended fixes                                                                                                                           |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `write CONNECTION_ENDED <host>:<port>`     | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`.                                              | Create a new `postgres()` instance inside your handler.                                                                                     |
+| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request.                                                                   |
+| `write CONNECTION_CLOSED <host>:<port>`    | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`.                                                                        | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
 
 #### mysql2 errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error. | Create a new connection inside your handler instead of reusing one from global scope. |
-| `Connection lost: The server closed the connection.` | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request. |
-| `Pool is closed.` | `pool.getConnection()` was called on a pool that has already been closed. | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
+| Error Message                                              | Details                                                                                                                           | Recommended fixes                                                                                                                          |
+| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error.                                  | Create a new connection inside your handler instead of reusing one from global scope.                                                      |
+| `Connection lost: The server closed the connection.`       | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request.                                                                             |
+| `Pool is closed.`                                          | `pool.getConnection()` was called on a pool that has already been closed.                                                         | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
 
 #### mysql errors
 
-| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
-| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `Cannot enqueue Query after fatal error.` | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`. | Create a new connection inside your handler instead of reusing one from global scope. |
-| `Cannot enqueue Query after invoking quit.` | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`. | Create a new connection inside your handler for every request. |
+| Error Message                                                   | Details                                                                                                                                   | Recommended fixes                                                                            |
+| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| `Cannot enqueue Query after fatal error.`                       | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`.        | Create a new connection inside your handler instead of reusing one from global scope.        |
+| `Cannot enqueue Query after invoking quit.`                     | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`.                               | Create a new connection inside your handler for every request.                               |
 | `Cannot enqueue Handshake after already enqueuing a Handshake.` | `.connect()` was called on a connection that was already connected in a previous request. Error code: `PROTOCOL_ENQUEUE_HANDSHAKE_TWICE`. | Create a new connection per request. mysql connections cannot be reconnected once connected. |
 
 ### Improve performance
diff --git a/src/content/docs/hyperdrive/platform/limits.mdx b/src/content/docs/hyperdrive/platform/limits.mdx
index 76f3f59ff4ae007..312468a7fe964d7 100644
--- a/src/content/docs/hyperdrive/platform/limits.mdx
+++ b/src/content/docs/hyperdrive/platform/limits.mdx
@@ -14,10 +14,10 @@ The following limits apply to Hyperdrive configurations, connections, and querie
 
 These limits apply when creating or updating Hyperdrive configurations.
 
-| Limit                          | Free                  | Paid                  |
-| ------------------------------ | --------------------- | --------------------- |
-| Maximum configured databases   | 10 per account        | 25 per account        |
-| Maximum username length [^1]   | 63 characters (bytes) | 63 characters (bytes) |
+| Limit                             | Free                  | Paid                  |
+| --------------------------------- | --------------------- | --------------------- |
+| Maximum configured databases      | 10 per account        | 25 per account        |
+| Maximum username length [^1]      | 63 characters (bytes) | 63 characters (bytes) |
 | Maximum database name length [^1] | 63 characters (bytes) | 63 characters (bytes) |
 
 [^1]: This is a limit enforced by PostgreSQL. Some database providers may enforce smaller limits.
@@ -26,10 +26,10 @@ These limits apply when creating or updating Hyperdrive configurations.
 
 These limits apply to connections between Hyperdrive and your origin database.
 
-| Limit                              | Free                     | Paid                      |
-| ---------------------------------- | ------------------------ | ------------------------- |
-| Initial connection timeout         | 15 seconds               | 15 seconds                |
-| Idle connection timeout            | 10 minutes               | 10 minutes                |
+| Limit                                                        | Free            | Paid             |
+| ------------------------------------------------------------ | --------------- | ---------------- |
+| Initial connection timeout                                   | 15 seconds      | 15 seconds       |
+| Idle connection timeout                                      | 10 minutes      | 10 minutes       |
 | Maximum origin database connections (per configuration) [^2] | ~20 connections | ~100 connections |
 
 Hyperdrive does not limit the number of concurrent client connections from your Workers. However, Hyperdrive limits connections to your origin database because most hosted databases have connection limits.
@@ -40,9 +40,9 @@ Hyperdrive does not limit the number of concurrent client connections from your
 
 When Hyperdrive cannot acquire a connection to your origin database, you may see one of the following errors:
 
-| Error message | Cause |
-| ------------- | ----- |
-| `Failed to acquire a connection from the pool.` | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause. |
+| Error message                                          | Cause                                                                                                                                                           |
+| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Failed to acquire a connection from the pool.`        | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause.                           |
 | `Server connection attempt failed: connection_refused` | Your origin database is rejecting connections. This can occur when a firewall blocks Hyperdrive, or when your database provider's connection limit is exceeded. |
 
 For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdrive/observability/troubleshooting/).
@@ -51,10 +51,10 @@ For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdriv
 
 These limits apply to queries sent through Hyperdrive.
 
-| Limit                              | Free      | Paid      |
-| ---------------------------------- | --------- | --------- |
+| Limit                              | Free       | Paid       |
+| ---------------------------------- | ---------- | ---------- |
 | Maximum query (statement) duration | 60 seconds | 60 seconds |
-| Maximum cached query response size | 50 MB     | 50 MB     |
+| Maximum cached query response size | 50 MB      | 50 MB      |
 
 Queries exceeding the maximum duration are terminated. Query responses larger than 50 MB are not cached but are still returned to your Worker.
 
diff --git a/src/content/docs/hyperdrive/platform/storage-options.mdx b/src/content/docs/hyperdrive/platform/storage-options.mdx
index 15e4357c49ab353..e47f0bee278b20d 100644
--- a/src/content/docs/hyperdrive/platform/storage-options.mdx
+++ b/src/content/docs/hyperdrive/platform/storage-options.mdx
@@ -9,5 +9,5 @@ products:
   - hyperdrive
   - kv
   - r2
-  - d1 
+  - d1
 ---
diff --git a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
index 79d2a4c9a8334f6..634a4a834452673 100644
--- a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
+++ b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
@@ -12,4 +12,4 @@ import { WranglerNamespace } from "~/components";
 
 The following [Wrangler commands](/workers/wrangler/) apply to Hyperdrive.
 
-<WranglerNamespace namespace="hyperdrive" />
\ No newline at end of file
+<WranglerNamespace namespace="hyperdrive" />
diff --git a/src/content/docs/hyperdrive/tutorials/index.mdx b/src/content/docs/hyperdrive/tutorials/index.mdx
index 303882afc56a048..20365d245d2b967 100644
--- a/src/content/docs/hyperdrive/tutorials/index.mdx
+++ b/src/content/docs/hyperdrive/tutorials/index.mdx
@@ -10,7 +10,7 @@ products:
   - workers
 ---
 
-import { GlossaryTooltip, ListTutorials } from "~/components"
+import { GlossaryTooltip, ListTutorials } from "~/components";
 
 View <GlossaryTooltip term="tutorial">tutorials</GlossaryTooltip> to help you get started with Hyperdrive.
 
diff --git a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
index b9f564b90204b67..83a5d692b9d5e21 100644
--- a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
+++ b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
@@ -3,7 +3,7 @@ reviewed: 2023-10-30
 difficulty: Beginner
 pcx_content_type: tutorial
 title: Create a serverless, globally distributed time-series API with Timescale
-products:	[workers]
+products: [workers]
 tags:
   - PostgreSQL
   - TypeScript
diff --git a/src/content/docs/images/optimization/make-responsive-images.mdx b/src/content/docs/images/optimization/make-responsive-images.mdx
index a0dcd9f7f0c9726..951c3590cc0ae6e 100644
--- a/src/content/docs/images/optimization/make-responsive-images.mdx
+++ b/src/content/docs/images/optimization/make-responsive-images.mdx
@@ -68,12 +68,7 @@ The browser evaluates screen size, pixel density, and network conditions, then s
 The snippet below shows how `srcset` can be used within an `<img>` tag to serve one of two possible sizes, depending on the user's device pixel ratio:
 
 ```html
-<img
-	src="portrait-800w.jpg"
-	srcset="
-		portrait-1600.jpg 2x,
-	"
-/>
+<img src="portrait-800w.jpg" srcset="portrait-1600.jpg 2x" />
 ```
 
 Instead of pre-generating each size, use Images to point every `srcset` entry at the same source image with a different `width` parameter and pixel density descriptor (for example, `2x`). Once the browser selects the right width for the user's device pixel ratio, Cloudflare dynamically generates the resized version on request:
@@ -164,11 +159,11 @@ The default breakpoints for client hints are: `320`, `768`, `960`, and `1200` pi
 The following table shows the widths that Cloudflare will pick based on the default breakpoints. If the detected viewport width exceeds the largest breakpoint, the image is served at that largest breakpoint.
 
 | Detected viewport width | Served image width |
-| ---------- | ------------- |
-| 280px          | 320px         |
-| 500px          | 768px         |
-| 960px          | 960px         |
-| 1500px          | 1200px        |
+| ----------------------- | ------------------ |
+| 280px                   | 320px              |
+| 500px                   | 768px              |
+| 960px                   | 960px              |
+| 1500px                  | 1200px             |
 
 You can override the default breakpoints using the [`wbreakpoints`](/images/optimization/features/#width) sub-parameter, which accepts positive integers separated by semicolons.
 
diff --git a/src/content/docs/images/optimization/transformations/flows.mdx b/src/content/docs/images/optimization/transformations/flows.mdx
index 90b4c423f905e10..c9d36c389aba1ca 100644
--- a/src/content/docs/images/optimization/transformations/flows.mdx
+++ b/src/content/docs/images/optimization/transformations/flows.mdx
@@ -6,10 +6,12 @@ sidebar:
   products:
     - images
 ---
+
 import { Description, Render } from "~/components";
 
 <Description>
-	Define automated rules to optimize remote images without writing any code or changing your existing URLs.
+	Define automated rules to optimize remote images without writing any code or
+	changing your existing URLs.
 </Description>
 
 Flows let you automatically apply image optimization to requests on your zone.
@@ -32,6 +34,7 @@ Currently, Cloudflare supports flows for Fastly Image Optimizer. When enabled, C
 A **custom flow** lets you define your own conditions and actions for image optimization.
 
 This is well-suited for situations where you want to optimize your images broadly and consistently, such as:
+
 - **Automatic format conversion** — Transcode all images to modern formats like AVIF or WebP across your entire site.
 - **Responsive sizing** — Automatically resize images based on each user's device.
 - **Directory-based optimization** — Enforce a consistent size for all images in a particular path, such as 100x100 for images where the path contains `/thumbnail`.
@@ -41,16 +44,19 @@ This is well-suited for situations where you want to optimize your images broadl
 Before setting up a flow, make sure that transformations are turned on for your zone under **Images** > **Transformations** in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/images/transformations).
 
 When an image is requested on your zone, Cloudflare checks to see whether the request matches the conditions for any of your configured flows:
+
 - Flows are evaluated from top to bottom in the order that they appear in the dashboard.
 - If a request matches more than one flow, only the first matching flow will run.
 - If no flow matches, then the request passes through to your origin unmodified.
 - To control priority, you can reorder flows in the dashboard.
 
 If the request matches a flow's conditions, then Cloudflare rewrites the URL to pass through the Images service with the specified parameters:
+
 - A custom flow triggers only on requests for [supported image extensions](/images/get-started/limits/). HTML pages, CSS files, and other non-images are never affected.
 - A provider flow evaluates requests based on provider-specific optimization parameters. For example, a Fastly provider flow triggers only when the request contains parameters like `?width`, `?height`, or `?fit`. Cloudflare will ignore any unrecognized parameters.
 
 In your request lifecycle, flows are evaluated after standard HTTP [redirect rules](/rules/url-forwarding/):
+
 - Any existing URL rewrites or redirect rules will be applied before Images evaluates the request, which may affect matching behavior.
 - Flows include built-in loop prevention. If the request is already coming from the Images service, then the flow will not re-trigger on that subrequest.
 
@@ -59,6 +65,7 @@ In your request lifecycle, flows are evaluated after standard HTTP [redirect rul
 Currently, Cloudflare supports flows to handle migrations from Fastly Image Optimizer.
 
 To add a provider flow:
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Images** > **Transformations** and select your zone.
 3. Select the **Automation** tab, then select **Add provider flow**.
@@ -122,11 +129,11 @@ Cloudflare determines the optimal width using either [client hints](/images/opti
 
 You can fine-tune the `width=auto` behavior with the following sub-parameters:
 
-| Sub-parameter | Description | Default |
-| --- | --- | --- |
-| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints) | `320;768;960;1200` |
-| `wmobile` | Override default width, in pixels, for mobile devices (user-agent detection) | `768` |
-| `wdesktop` | Override default width, in pixels, for desktop devices (user-agent detection) | `1200` |
+| Sub-parameter  | Description                                                                   | Default            |
+| -------------- | ----------------------------------------------------------------------------- | ------------------ |
+| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints)                  | `320;768;960;1200` |
+| `wmobile`      | Override default width, in pixels, for mobile devices (user-agent detection)  | `768`              |
+| `wdesktop`     | Override default width, in pixels, for desktop devices (user-agent detection) | `1200`             |
 
 To learn how `width=auto` works, refer to our guide on [serving responsive images](/images/optimization/make-responsive-images/).
 
diff --git a/src/content/docs/images/optimization/transformations/overview.mdx b/src/content/docs/images/optimization/transformations/overview.mdx
index d623c6694db1f47..7de24256a768de1 100644
--- a/src/content/docs/images/optimization/transformations/overview.mdx
+++ b/src/content/docs/images/optimization/transformations/overview.mdx
@@ -11,7 +11,8 @@ products:
 import { Description, Render } from "~/components";
 
 <Description>
-	Transformations are requests to optimize and manipulate remote images that are stored outside of Images.
+	Transformations are requests to optimize and manipulate remote images that are
+	stored outside of Images.
 </Description>
 
 When you ship applications on Cloudflare, you can use Images to automatically optimize and cache your images from any origin.
diff --git a/src/content/docs/key-transparency/api/epochs.mdx b/src/content/docs/key-transparency/api/epochs.mdx
index d9a24544386e49e..6aa0c01a45d12dd 100644
--- a/src/content/docs/key-transparency/api/epochs.mdx
+++ b/src/content/docs/key-transparency/api/epochs.mdx
@@ -49,7 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}/audit
 - If `root` is defined for the namespace, the first epoch must match it (number and digest).
 - Epochs must be increasing. Second epoch is 2, third is 3, etc.
 - Epochs must have a unique digest or it will be rejected.
-- Epochs cannot be republished. 
+- Epochs cannot be republished.
 - Digest must be a 32 byte string hex encoded (length 64).
 
 If a namespace is disabled, you receive the following error:
diff --git a/src/content/docs/key-transparency/api/index.mdx b/src/content/docs/key-transparency/api/index.mdx
index c390a1774ee252d..64b24fdf3146f9d 100644
--- a/src/content/docs/key-transparency/api/index.mdx
+++ b/src/content/docs/key-transparency/api/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/key-transparency/api/namespaces.mdx b/src/content/docs/key-transparency/api/namespaces.mdx
index 3e42e5b0a09d29b..055e97b897823f2 100644
--- a/src/content/docs/key-transparency/api/namespaces.mdx
+++ b/src/content/docs/key-transparency/api/namespaces.mdx
@@ -20,8 +20,8 @@ The following fields are required when making a `POST` request:
 - `name`
 - `public`
 - `root`
-- `signature_version`: 
-  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor 
+- `signature_version`:
+  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor
   - 0x0002 for [bincode serialisation](https://github.com/bincode-org/bincode/blob/trunk/docs/spec.md) E25519 serialisation by the Auditor
 
 The `log_directory` field is optional. If set, Cloudflare will use it to fetch audit proofs and validate them.
@@ -49,6 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces' \
 ```
 
 After publishing the first epoch, `status` will show `Online`. Possible statuses include:
+
 - `Online`
 - `Initialization`
 - `Disabled`
@@ -73,7 +74,6 @@ If a log state has been corrupted, lost, or needs to be sharded to be maintainab
 
 This API is authenticated via [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).
 
-
 ```sh
 curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}' \
         	-H 'Content-Type: application/json' \
@@ -89,4 +89,4 @@ curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespa
   "audits_uri": "/namespaces/your.new.log.com/audits",
   "signature_version": 1
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/kv/api/delete-key-value-pairs.mdx b/src/content/docs/kv/api/delete-key-value-pairs.mdx
index f4275b10c635eef..e8173282815e34f 100644
--- a/src/content/docs/kv/api/delete-key-value-pairs.mdx
+++ b/src/content/docs/kv/api/delete-key-value-pairs.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
@@ -22,25 +22,24 @@ An example of deleting a key-value pair from within a Worker:
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    try {
-      await env.NAMESPACE.delete("first-key");
-
-      return new Response("Successful delete", {
-        status: 200
-      });
-    }
-    catch (e)
-    {
-      return new Response(e.message, {status: 500});
-    }
-  },
+	async fetch(request, env, ctx) {
+		try {
+			await env.NAMESPACE.delete("first-key");
+
+			return new Response("Successful delete", {
+				status: 200,
+			});
+		} catch (e) {
+			return new Response(e.message, { status: 500 });
+		}
+	},
 };
 ```
 
 ## Reference
 
 The following method is provided to delete from KV:
+
 - [delete()](#delete-method)
 
 ### `delete()` method
@@ -53,14 +52,13 @@ env.NAMESPACE.delete(key);
 
 #### Parameters
 
-* `key`: `string`
-  * The key to associate with the value.
+- `key`: `string`
+  - The key to associate with the value.
 
 #### Response
 
-* `response`: `Promise<void>`
-  * A `Promise` that resolves if the delete is successful.
-
+- `response`: `Promise<void>`
+  - A `Promise` that resolves if the delete is successful.
 
 This method returns a promise that you should `await` on to verify successful deletion. Calling `delete()` on a non-existing key is returned as a successful delete.
 
@@ -75,4 +73,5 @@ Delete more than one key-value pair at a time with Wrangler or [via the REST API
 The bulk REST API can accept up to 10,000 KV pairs at once. Bulk writes are not supported using the [KV binding](/kv/concepts/kv-bindings/).
 
 ## Other methods to access KV
+
 You can also [delete key-value pairs from the command line with Wrangler](/kv/reference/kv-commands/#kv-namespace-delete) or [with the REST API](/api/resources/kv/subresources/namespaces/subresources/values/methods/delete/).
diff --git a/src/content/docs/kv/concepts/kv-bindings.mdx b/src/content/docs/kv/concepts/kv-bindings.mdx
index 025824dc80e64ab..1710c1db27c0aad 100644
--- a/src/content/docs/kv/concepts/kv-bindings.mdx
+++ b/src/content/docs/kv/concepts/kv-bindings.mdx
@@ -52,14 +52,14 @@ With this, the deployed Worker will have a `TODO` field in their environment obj
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    // Get the value for the "to-do:123" key
-    // NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
-    let value = await env.TODO.get("to-do:123");
-
-    // Return the value, as is, for the Response
-    return new Response(value);
-  },
+	async fetch(request, env, ctx) {
+		// Get the value for the "to-do:123" key
+		// NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
+		let value = await env.TODO.get("to-do:123");
+
+		// Return the value, as is, for the Response
+		return new Response(value);
+	},
 };
 ```
 
@@ -97,13 +97,13 @@ An example might look like:
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-  constructor(ctx, env) {
-    super(ctx, env);
-  }
-
-  async fetch(request) {
-    const valueFromKV = await this.env.NAMESPACE.get("someKey");
-    return new Response(valueFromKV);
-  }
+	constructor(ctx, env) {
+		super(ctx, env);
+	}
+
+	async fetch(request) {
+		const valueFromKV = await this.env.NAMESPACE.get("someKey");
+		return new Response(valueFromKV);
+	}
 }
 ```
diff --git a/src/content/docs/kv/concepts/kv-namespaces.mdx b/src/content/docs/kv/concepts/kv-namespaces.mdx
index 7867efd8d6aaab6..0919c833f8ab666 100644
--- a/src/content/docs/kv/concepts/kv-namespaces.mdx
+++ b/src/content/docs/kv/concepts/kv-namespaces.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - kv
 ---
+
 import { Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 A KV namespace is a key-value database replicated to Cloudflare’s global network.
@@ -23,17 +24,14 @@ KV namespace IDs are public and bound to your account.
 
 To bind KV namespaces to your Worker, assign an array of the below object to the `kv_namespaces` key.
 
-* `binding` <Type text="string" /> <MetaInfo text="required" />
-
-  * The binding name used to refer to the KV namespace.
-
-* `id` <Type text="string" /> <MetaInfo text="required" />
+- `binding` <Type text="string" /> <MetaInfo text="required" />
+  - The binding name used to refer to the KV namespace.
 
-  * The ID of the KV namespace.
+- `id` <Type text="string" /> <MetaInfo text="required" />
+  - The ID of the KV namespace.
 
-* `preview_id` <Type text="string" /> <MetaInfo text="optional" />
-
-  * The ID of the KV namespace used during `wrangler dev`.
+- `preview_id` <Type text="string" /> <MetaInfo text="optional" />
+  - The ID of the KV namespace used during `wrangler dev`.
 
 Example:
 
@@ -59,6 +57,7 @@ To bind the namespace to your Worker in the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your **Worker**.
 3. Select **Settings** > **Bindings**.
 4. Select **Add**.
diff --git a/src/content/docs/kv/get-started.mdx b/src/content/docs/kv/get-started.mdx
index 1087ab11b86e2ce..2940849e4bb17a3 100644
--- a/src/content/docs/kv/get-started.mdx
+++ b/src/content/docs/kv/get-started.mdx
@@ -3,7 +3,7 @@ title: Getting started
 description: Create a KV namespace, write key-value pairs, and read data from Workers KV using Wrangler or the dashboard.
 pcx_content_type: get-started
 summary: |
-    Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
+  Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
 reviewed: 2025-05-19
 sidebar:
   order: 2
@@ -11,7 +11,18 @@ products:
   - kv
 ---
 
-import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem, WranglerConfig, GitHubCode, DashButton } from "~/components";
+import {
+	Render,
+	PackageManagers,
+	Steps,
+	FileTree,
+	Details,
+	Tabs,
+	TabItem,
+	WranglerConfig,
+	GitHubCode,
+	DashButton,
+} from "~/components";
 
 Workers KV provides low-latency, high-throughput global storage to your [Cloudflare Workers](/workers/) applications. Workers KV is ideal for storing user configuration data, routing data, A/B testing configurations and authentication tokens, and is well suited for read-heavy workloads.
 
diff --git a/src/content/docs/kv/glossary.mdx b/src/content/docs/kv/glossary.mdx
index 6b9c8f69e63c1a2..fca60dffa616ae9 100644
--- a/src/content/docs/kv/glossary.mdx
+++ b/src/content/docs/kv/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's KV documentation.
 
diff --git a/src/content/docs/kv/observability/index.mdx b/src/content/docs/kv/observability/index.mdx
index 9f1c8fd90be7853..8f1670df25b7b57 100644
--- a/src/content/docs/kv/observability/index.mdx
+++ b/src/content/docs/kv/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - kv
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/kv/observability/metrics-analytics.mdx b/src/content/docs/kv/observability/metrics-analytics.mdx
index c341d12aa8f4c3c..01ac3d93bddf26b 100644
--- a/src/content/docs/kv/observability/metrics-analytics.mdx
+++ b/src/content/docs/kv/observability/metrics-analytics.mdx
@@ -32,6 +32,7 @@ Per-namespace analytics for KV are available in the Cloudflare dashboard. To vie
 1. In the Cloudflare dashboard, go to the **Workers KV** page.
 
    <DashButton url="/?to=/:account/workers/kv/namespaces" />
+
 2. Select an existing namespace.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/kv/platform/pricing.mdx b/src/content/docs/kv/platform/pricing.mdx
index 2fbcd27b1c0dc52..e52462c5d821622 100644
--- a/src/content/docs/kv/platform/pricing.mdx
+++ b/src/content/docs/kv/platform/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="kv_pricing" product="workers" />
 
diff --git a/src/content/docs/kv/reference/data-security.mdx b/src/content/docs/kv/reference/data-security.mdx
index 56ffef1944f609a..5c00ce589165eee 100644
--- a/src/content/docs/kv/reference/data-security.mdx
+++ b/src/content/docs/kv/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of KV, including:
 
-* Encryption-at-rest (EAR).
-* Encryption-in-transit (EIT).
-* Cloudflare's compliance certifications.
+- Encryption-at-rest (EAR).
+- Encryption-in-transit (EIT).
+- Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/kv/reference/environments.mdx b/src/content/docs/kv/reference/environments.mdx
index ef1e9305aea8aa3..dc41508ef498dcf 100644
--- a/src/content/docs/kv/reference/environments.mdx
+++ b/src/content/docs/kv/reference/environments.mdx
@@ -68,8 +68,6 @@ Specifying an environment with the optional `--env` flag allows you to publish W
 
 For example, you could use separate staging and production KV namespaces for KV data in your Wrangler file:
 
-
-
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/kv/reference/kv-commands.mdx b/src/content/docs/kv/reference/kv-commands.mdx
index 431cd3c20f17a6f..fe72655a36d9f3d 100644
--- a/src/content/docs/kv/reference/kv-commands.mdx
+++ b/src/content/docs/kv/reference/kv-commands.mdx
@@ -8,9 +8,9 @@ products:
   - kv
 ---
 
-import {Render} from "~/components"
+import { Render } from "~/components";
 
-<Render file="wrangler-commands/kv" product="workers"/>
+<Render file="wrangler-commands/kv" product="workers" />
 
 ## Deprecations
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
index e12e1fb27bbc69d..390d7d7727dc08f 100644
--- a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
@@ -5,7 +5,7 @@ pcx_content_type: overview
 sidebar:
   order: 5
   label: Audit Logs - v2
-  badge: 
+  badge:
     text: Beta
 description: Use the updated Audit Logs v2 interface.
 products:
diff --git a/src/content/docs/learning-paths/application-security/account-security/index.mdx b/src/content/docs/learning-paths/application-security/account-security/index.mdx
index cb51b549f91cf51..8bd856a5fcab2d3 100644
--- a/src/content/docs/learning-paths/application-security/account-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/index.mdx
@@ -18,6 +18,6 @@ Make sure your account's security basics are configured properly.
 
 By the end of this module, you will be able to:
 
-* Secure your account
-* Understand and configure the most common settings for Cloudflare's Application Security Products
-* Explore advanced security products such as Bot Management and API Protection
+- Secure your account
+- Understand and configure the most common settings for Cloudflare's Application Security Products
+- Explore advanced security products such as Bot Management and API Protection
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
index 7b0bddc7ba7917f..040aa06f0220922 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="account-manage-active-sessions" product="fundamentals" />
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
index 808ba2c05ca7dad..f58aa925b394692 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 :::note
 Audit Logs version 2 is available in beta. Refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/) for more details.
diff --git a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
index 29a6b9e44022824..f7846d7a368fa45 100644
--- a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
@@ -12,11 +12,11 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="2fa-overview" product="support" />
 
-***
+---
 
 ## Enable 2FA
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
index 2f7bec4ece18e95..d9d1cae9beaab73 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="bic-description" product="waf" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
index 6358ef403930629..33a0732d1aa3a3e 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
@@ -12,10 +12,10 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare automatically detects and mitigates DDoS attacks using its [Autonomous Edge](/ddos-protection/about/components/#autonomous-edge), which is always-on. `Advanced` protections are reserved for Magic Transit customers.
 
 <Render file="ddos-attack-coverage" product="ddos-protection" />
 
-Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/)  to dive deeper into this subject.
+Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/) to dive deeper into this subject.
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
index d3c76bce71f7ce2..636464957d64e91 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="dnssec-definition" product="dns" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
index f9c577f4d3368d9..5432c5e8c039ee4 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
@@ -18,4 +18,4 @@ As soon as you onboard your domain to Cloudflare, you are automatically protecte
 
 By the end of this module, you will be able to:
 
-* Understand the most common security controls your applications will have access to
+- Understand the most common security controls your applications will have access to
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
index a68ec976eb10fae..3d460f58056b631 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Mutual TLS (mTLS) authentication uses client certificates to ensure traffic between client and server is bidirectionally secure and trusted. mTLS also allows requests that do not authenticate via an identity provider — such as Internet-of-things (IoT) devices — to demonstrate they can reach a given resource.
 
diff --git a/src/content/docs/learning-paths/application-security/firewall/index.mdx b/src/content/docs/learning-paths/application-security/firewall/index.mdx
index 6ee96f14dba91e6..78fffa803dc49c0 100644
--- a/src/content/docs/learning-paths/application-security/firewall/index.mdx
+++ b/src/content/docs/learning-paths/application-security/firewall/index.mdx
@@ -18,5 +18,5 @@ Cloudflare's Web Application Firewall (WAF) is used to protect websites from a w
 
 By the end of this module, you will be able to:
 
-* Understand the different WAF components that Cloudflare offers
-* Understand the main features within each WAF offering
+- Understand the different WAF components that Cloudflare offers
+- Understand the main features within each WAF offering
diff --git a/src/content/docs/learning-paths/application-security/lists/configuration.mdx b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
index 0a7cc2639adf13f..de13360e165d887 100644
--- a/src/content/docs/learning-paths/application-security/lists/configuration.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Both Custom and Managed Lists are located in the account settings. Refer to [Features by plan type](/learning-paths/application-security/lists/features/) for more information on plan eligibility.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/features.mdx b/src/content/docs/learning-paths/application-security/lists/features.mdx
index 96704045ef785d4..4ea1c31ecbdd63e 100644
--- a/src/content/docs/learning-paths/application-security/lists/features.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { FeatureTable, Render } from "~/components"
+import { FeatureTable, Render } from "~/components";
 
 List availability varies according to the list type and your Cloudflare plan and subscriptions.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/index.mdx b/src/content/docs/learning-paths/application-security/lists/index.mdx
index 5278a33aaa568ba..852a5c8744856ab 100644
--- a/src/content/docs/learning-paths/application-security/lists/index.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/index.mdx
@@ -14,12 +14,12 @@ products:
 
 Cloudflare Lists is a WAF feature that enables administrators to groups identifiers together, such as IPs, hostnames or ASNs, and reference the list by other Cloudflare products such as [Custom rules](/waf/custom-rules/). Cloudflare currently supports the following types of lists:
 
-* [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
-* [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
+- [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
+- [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Understand all the options Cloudflare's Lists products offer
-* Understand the advanced configurations provided to you with a paid offering
+- Understand all the options Cloudflare's Lists products offer
+- Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
index b14eddd109c6d34..9823a3c2fca778d 100644
--- a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
index ceee8008c0ec64e..21914e63f80aefc 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
@@ -14,14 +14,14 @@ products:
 
 Let's step through an example. If your `/create-account` page is being attacked, you will create a rule to limit the amount of requests, per `counting characteristic`, that you feel comfortable permitting through to your origin.
 
-The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, *after* 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
+The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, _after_ 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
 
-***
+---
 
 ![rate-limiting-create-account-endpoint](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint.png)
 ![rate-limiting-create-account-endpoint-block](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint-block.png)
 
-***
+---
 
 ## Advanced configuration
 
@@ -29,14 +29,14 @@ In the previous module, we reviewed the various configurations available per pla
 
 The rule below is being created on the `enterprise` plan, so we are no longer limited to default configurations.
 
-* The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
-* Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
-* Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
-* Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
+- The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
+- Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
+- Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
+- Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
 
 ![rate-limiting-advanced-config-1](~/assets/images/waf/rate-limiting-rules/rl-advanced-config.png)
 
-***
+---
 
 ## Best practices
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
index 21aa7c300cdb961..606b48b86302118 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Rate limiting is composed of the following parameters:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
index 75a9a0e25347d72..45270f5ec40f21e 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
@@ -18,5 +18,5 @@ Rate Limiting mitigates excessive request rates for specific URLs or for an enti
 
 By the end of this module, you will be able to:
 
-* Understand all the options Cloudflare's Rate Limiting product offers
-* Understand the advanced configurations provided to you with a paid offering
+- Understand all the options Cloudflare's Rate Limiting product offers
+- Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
index 7eb7c2accedce4b..81787364edb5b8b 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
index 06d7cf0e3aa85f1..2533b2fabe4489e 100644
--- a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="brand-protection-definition" product="security-center" />
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/index.mdx b/src/content/docs/learning-paths/application-security/security-center/index.mdx
index 3c114e0c0f9d8d6..443cd3864fd9da6 100644
--- a/src/content/docs/learning-paths/application-security/security-center/index.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/index.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="security-center-definition" product="security-center" />
 
@@ -20,5 +20,5 @@ import { Render } from "~/components"
 
 By the end of this module, you will be able to:
 
-* Understand the primary Security Center features such as Security Insights and Brand Protection
-* Review and manage security risks at the account level, encompassing all of your domains in one unified view
+- Understand the primary Security Center features such as Security Insights and Brand Protection
+- Review and manage security risks at the account level, encompassing all of your domains in one unified view
diff --git a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
index 54e046c2db79eed..9ce422510bb4427 100644
--- a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
@@ -16,7 +16,7 @@ Now that you have [connected your private applications](/learning-paths/clientle
 
 By the end of this module, you will be able to:
 
-* Add your application to Cloudflare Access.
-* Create an Access policy.
-* Design reusable policies.
-* Design a domain structure for your applications.
+- Add your application to Cloudflare Access.
+- Create an Access policy.
+- Design reusable policies.
+- Design a domain structure for your applications.
diff --git a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
index 38a2051d7e24d98..5450985227dcb8e 100644
--- a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
@@ -16,7 +16,7 @@ Configure advanced Access policies to meet the specific requirements of your app
 
 By the end of this module, you will be able to:
 
-* Check identity-based attributes that are not directly supported by the Access policy builder.
-* Deliver sensitive web applications in an isolated browser.
-* Apply Gateway HTTP policies without a device client.
-* Connect to applications using their private hostnames without a device client.
+- Check identity-based attributes that are not directly supported by the Access policy builder.
+- Deliver sensitive web applications in an isolated browser.
+- Apply Gateway HTTP policies without a device client.
+- Connect to applications using their private hostnames without a device client.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
index 700dfb2c429be48..ba3876cbb069c62 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
@@ -27,6 +27,6 @@ To configure Clientless Web Isolation to augment clientless access, refer to [th
 
 ## Best practices
 
-* For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
-* If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
-* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
+- For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
+- If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
+- You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
index 236369d2c8ea5d8..3d6978794492877 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
@@ -10,10 +10,10 @@ products:
   - cloudflare-one
 ---
 
-As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access.  However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
+As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access. However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Connect to private web applications using their private hostnames.
+- Connect to private web applications using their private hostnames.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
index 1c76266d3e00159..96467fa3ad74ab3 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
@@ -16,4 +16,4 @@ Review the concepts behind clientless access.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose and benefits of clientless access.
\ No newline at end of file
+- Understand the purpose and benefits of clientless access.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
index 446f1e1c72913e7..9b3e4a2a40a5b80 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
@@ -12,7 +12,7 @@ products:
 
 Clientless access is a deployment option of a [Zero Trust Network Access (ZTNA)](https://www.cloudflare.com/learning/access-management/what-is-ztna/) service that provides secure access to internal applications without requiring end users to install any software. Users access corporate resources like intranet web apps, SSH terminals, and Windows servers through RDP from their web browser. Clientless access is commonly used to provide internal, [least-privilege access](https://www.cloudflare.com/learning/access-management/principle-of-least-privilege/) to users on unmanaged devices. Users may include third-party contractors, suppliers, and partners, or employees using personal mobile phones as part of an organization's bring-your-own-device (BYOD) policy.
 
-IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as  preventing uploads/downloads or copy/paste, or incorporating DLP policies.
+IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as preventing uploads/downloads or copy/paste, or incorporating DLP policies.
 
 ## Alternatives to clientless access
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
index 7015fc5b6c802b5..7eb4c09d0ecbf01 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
@@ -20,9 +20,9 @@ For an additional point of availability, add a [`cloudflared` replica](/cloudfla
 
 To make your applications easier to manage, standardize the public hostnames that you publish your applications on. Here are a few examples of how customers manage their public hostnames:
 
-* Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
-* If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
-* Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
+- Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
+- If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
+- Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
 
 ## Disable TLS verification
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
index 3120d43f30efdce..9c6cbcd138686f2 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To enable clientless access to your applications, you will need to create a Cloudflare Tunnel that publishes applications to a domain on Cloudflare. A published application creates a public DNS record that routes traffic to a specific address, protocol, and port associated with a private application. For example, you can define a public hostname (`mywebapp.example.com`) to provide access to a web server running on `https://localhost:8080`. When a user goes to `mywebapp.example.com` in their browser, their request will first route to a Cloudflare data center where it is inspected against your configured security policies. Cloudflare will then forward validated requests down your tunnel to the web server.
 
@@ -32,9 +32,8 @@ All users on the Internet can now connect to this application via its public hos
 
 If the tunnel is disconnected:
 
-* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
-
+- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
 
 :::
 
@@ -42,5 +41,5 @@ If the tunnel is disconnected:
 
 For more control over how traffic routes through your tunnel, refer to the following links:
 
-* [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
-* [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
+- [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
+- [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
index fe443c8a8e5c306..4f9337b3961247c 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
@@ -16,5 +16,5 @@ Cloudflare Tunnel allows you to securely connect your applications to Cloudflare
 
 By the end of this module, you will be able to:
 
-* Create a Cloudflare Tunnel.
-* Publish your application via a public hostname.
+- Create a Cloudflare Tunnel.
+- Publish your application via a public hostname.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
index 49e6a3bcf50f75b..a14fda563a6432d 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/app-launcher" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
index 3f202ae036ff2e9..3de4f9ba2ef5141 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/block-page" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
index 23e9d4431ca5719..6a740a977e9de4c 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/bookmarks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
index 681cb50fbfb8882..01df3d80b023dd8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
@@ -16,7 +16,7 @@ Cloudflare Access offers several ways to customize the look and feel of the user
 
 By the end of this module, you will be able to:
 
-* Configure the App Launcher so that users can open all applications from single dashboard.
-* Add bookmarks to the App Launcher for applications that are not behind Access.
-* Customize the Access login page with your organization's branding.
-* Display custom block pages when a user is blocked by your Access policies.
+- Configure the App Launcher so that users can open all applications from single dashboard.
+- Add bookmarks to the App Launcher for applications that are not behind Access.
+- Customize the Access login page with your organization's branding.
+- Display custom block pages when a user is blocked by your Access policies.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
index 0784ac3db460bb8..b04f07439a4c9c8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The Access login page is where users select their identity provider (IdP) or One-Time PIN prior to accessing the application. Customers who only use one IdP usually enable **Apply instant authentication** for their applications, which redirects end users directly to the SSO login page. If you are using multiple IdPs, we recommend customizing the Access login page to match your branding and minimize user confusion.
 
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
index 6b8b7f8ee3ace2f..65bd38ce4da91e9 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
index bf6be752e98fce7..0348346f1053ba1 100644
--- a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
@@ -18,7 +18,7 @@ If you need to deliver access to non-browser based applications, refer to our co
 
 By the end of this module, you will be able to:
 
-* Set up a Cloudflare account.
-* Add your domain to Cloudflare.
-* Create a Zero Trust organization to manage applications and policies.
-* Configure an identity provider (IdP) for user authentication.
+- Set up a Cloudflare account.
+- Add your domain to Cloudflare.
+- Create a Zero Trust organization to manage applications and policies.
+- Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
index 238af10cab095cb..f519cc3082b5669 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
@@ -12,10 +12,10 @@ products:
 
 Most customers have a heterogeneous private application portfolio; some are home-built, some are internal managed services, some have SSO integrations available, and some rely on HTML or other forms of authentication. With that in mind, we recommend that you mix-and-match [onboarding solutions](/learning-paths/clientless-access/migrate-applications/integrated-sso/#potential-solutions) to fit the needs of each individual application. As shown in the table below, you can bucket applications into a series of stack-ranked categories that prioritize ease of implementation and total organizational impact.
 
-| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                             | Outcome                                                                                                                                                                                                                                                      |
-| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                     |
-| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                             |
-| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                     |
-| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.      | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
-| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                                                            | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                                                |
+| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                         | Outcome                                                                                                                                                                                                                                                  |
+| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                 |
+| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                         |
+| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                 |
+| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.          | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
+| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                             | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                 |
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
index 87fd2e5aafa3f63..9221ff52404a5f0 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
@@ -21,6 +21,6 @@ The remaining modules (Modules 6-9) discuss special considerations and setup opt
 
 By the end of this module, you will be able to:
 
-* Manage applications that are directly integrated with an identity provider.
-* Pass user information from Cloudflare Access to your application.
-* Review best practices for onboarding different types of internal applications.
+- Manage applications that are directly integrated with an identity provider.
+- Pass user information from Cloudflare Access to your application.
+- Review best practices for onboarding different types of internal applications.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
index 05491e91bbf7537..237820c4e1c9ca7 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
@@ -31,12 +31,12 @@ app.internal.com")
 
 If your applications use integrated SSO, there are a number of different paths you can take to onboard your applications to Cloudflare Access.
 
-| Solution                                                                                                                       | Steps required                                                                                                     | Pros                                                                                                                                                                        | Cons                                                                                                                     |
-| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                                | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                        | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
-| Present applications on existing internal domains with identical external domains delegated to Cloudflare                      | Add domains to Cloudflare that match internal domains                                                              | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
-| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li> | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
-| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                       | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/)           | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
+| Solution                                                                                                                   | Steps required                                                                                                      | Pros                                                                                                                                                                        | Cons                                                                                                                     |
+| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                            | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                         | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
+| Present applications on existing internal domains with identical external domains delegated to Cloudflare                  | Add domains to Cloudflare that match internal domains                                                               | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
+| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li>  | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
+| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                   | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/) | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
 
 ## Recommended solution
 
diff --git a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
index 7412e5a55b1652c..596225f3171052b 100644
--- a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
@@ -16,4 +16,4 @@ Integrate Cloudflare Access into your private application development pipeline.
 
 By the end of this module, you will be able to:
 
-* Publish internal applications to Cloudflare using Terraform.
+- Publish internal applications to Cloudflare using Terraform.
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
index 69453ef2d875700..1e092ce574856b2 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
@@ -11,7 +11,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To set up a Zero Trust organization:
 
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
index 721649155e70883..c0853f8ed750a7f 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
@@ -16,6 +16,6 @@ Get started by creating a Cloudflare account and initializing the Zero Trust and
 
 By the end of this module, you will have:
 
-* Created a Cloudflare account.
-* Initialized the Zero Trust dashboard.
-* Initialized the Area 1 dashboard.
+- Created a Cloudflare account.
+- Initialized the Zero Trust dashboard.
+- Initialized the Area 1 dashboard.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
index 098f42bdf6a93f6..c6dc2bacee257d2 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
@@ -16,7 +16,7 @@ Learn the technical concepts behind Project Cybersafe Schools.
 
 By the end of this module, you will be able to:
 
-* Understand the purpose of the Children’s Internet Protection Act (CIPA).
-* Describe the life of a DNS request.
-* Explain how DNS filtering works to control which websites users can access.
-* Understand the benefits of protecting your email inbox.
+- Understand the purpose of the Children’s Internet Protection Act (CIPA).
+- Describe the life of a DNS request.
+- Explain how DNS filtering works to control which websites users can access.
+- Understand the benefits of protecting your email inbox.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
index af663840fbd1be0..c7e8ff61a49fecf 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
@@ -16,9 +16,9 @@ DNS filtering is a technique to block access to websites or online content. DNS
 
 DNS filtering is commonly used to:
 
-* Protect school data from phishing, ransomware, and malware.
-* Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
-* Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
+- Protect school data from phishing, ransomware, and malware.
+- Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
+- Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
 
 ## How DNS filtering works
 
@@ -52,17 +52,17 @@ DNS filtering only applies to the hostname — `subdomain.domain.tld`. You canno
 
 Secure Web Gateways (SWGs) offer a greater set of capabilities, including:
 
-* [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
-* L4 firewalls to block ports and protocols
-* Antivirus scanning
-* [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
-* [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
+- [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
+- L4 firewalls to block ports and protocols
+- Antivirus scanning
+- [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
+- [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
 
 However, this can make SWGs more complex to deploy. Therefore, many organizations will start with DNS filtering as an initial layer of defense against Internet threats.
 
 ## Related resources
 
-* For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
+- For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
 
 ## Next steps
 
diff --git a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
index 75e5801177a4b47..c3c1b8bad4a14a0 100644
--- a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
+++ b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
@@ -10,8 +10,12 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To verify that your DNS traffic is sent to Gateway:
 
-<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
+<Render
+	file="gateway/verify-connectivity"
+	product="cloudflare-one"
+	params={{ one: "DNS", two: "queries" }}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
index b47b3a80514a788..eb3666dd5133b61 100644
--- a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
@@ -11,4 +11,4 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="magic-transit/advertise-prefixes"	product="networking-services" />
\ No newline at end of file
+<Render file="magic-transit/advertise-prefixes" product="networking-services" />
diff --git a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
index 6d99098e5ffbd39..49959caa851cad4 100644
--- a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
@@ -14,6 +14,6 @@ Learn core concepts about Magic Transit and its functionality, in order to prote
 ## Objectives
 
 By the end of this module you will be able to:
+
 - Understand what Magic Transit is
 - Why you should use it to protect your IP network
-
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
index 96178b835574113..a62c27d80ec53ce 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare DDoS protection automatically detects and mitigates Distributed Denial of Service (DDoS) attacks using its Autonomous Edge. Magic Transit customers have access to additional features, such as:
 
@@ -26,7 +26,10 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/tcp-protection-intro" product="ddos-protection" />
 
-<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
+<Render
+	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
+	product="ddos-protection"
+/>
 
 #### Setup
 
@@ -36,8 +39,11 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/dns-protection-intro" product="ddos-protection" />
 
-<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
+<Render
+	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
+	product="ddos-protection"
+/>
 
 #### Setup
 
-<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
\ No newline at end of file
+<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
index 482c2b215ae173f..51c5f4f2f692123 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -19,12 +19,16 @@ import { Render } from "~/components"
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT:
+			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table"
+		routingTableName: "Magic Transit Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
index 4c93f4789229aab..bd53e3d65b54e92 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
@@ -11,22 +11,31 @@ products:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
-	}} />
\ No newline at end of file
+		unifiedRoutingURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
+	}}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
index 6f1888d2fbbff7e..b98f8551ad40475 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
@@ -14,6 +14,6 @@ In this unit you will learn how to set up tunnels and routes to steer traffic.
 ## Objectives
 
 By the end of this module you will be able to:
+
 - Create tunnels on both the Cloudflare side and your router side to connect to your infrastructure.
 - Configure static routes or dynamic routes with BGP peering to steer your traffic via next-hop from Cloudflare's global network to your connected networks.
-
diff --git a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
index 1efb22a01b5feef..40adf54d7baae5f 100644
--- a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
@@ -17,7 +17,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation:
+			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
@@ -32,4 +33,4 @@ Cloudflare also recommends that you enable the following account notifications f
 - (Optional) Advanced Layer 3/4 DDoS Attack Alert
 - (Optional) Cloudflare status - Maintenance Notification (in case you want to be alerted regarding maintenance in specific Cloudflare data centers).
 
-Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
\ No newline at end of file
+Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
diff --git a/src/content/docs/learning-paths/data-center-protection/get-started.mdx b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
index 58e23aba7e9451b..16b63ff273ced89 100644
--- a/src/content/docs/learning-paths/data-center-protection/get-started.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
@@ -9,6 +9,10 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Learning Path" }} />
\ No newline at end of file
+<Render
+	file="magic-transit/get-started"
+	product="networking-services"
+	params={{ magicWord: "Learning Path" }}
+/>
diff --git a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
index 7d6e4bdd8b5ba93..88f72d32072ad16 100644
--- a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
@@ -10,6 +10,7 @@ products:
 ---
 
 After setting up your Magic Transit product, Cloudflare validates:
+
 - Tunnel connectivity
 - Tunnel and endpoint [health checks](/magic-transit/reference/tunnel-health-checks/#types-of-health-checks)
 - Letter of Agency (LOA)
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
index 4b7ab7651839800..efe4d0f80aa7a93 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
@@ -14,7 +14,7 @@ Migrating your DNS from an on-premises BIND solution to a cloud-based provider l
 
 By the end of this module, you will be able to:
 
-* Plan and take inventory of your DNS migration.
-* Prepare for the migration with minimal downtime.
-* Learn how to make the actual switch to Cloudflare.
-* Verify and stabilize after your migration.
+- Plan and take inventory of your DNS migration.
+- Prepare for the migration with minimal downtime.
+- Learn how to make the actual switch to Cloudflare.
+- Verify and stabilize after your migration.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
index 05eae75787849b0..ac9f126e6cfb046 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
@@ -12,55 +12,55 @@ Detailed planning is the cornerstone of a successful DNS migration.
 
 ## 1. Understand your current BIND setup
 
-1. Identify all DNS zones currently hosted on your BIND servers.  
-2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.  
-3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.  
-   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.  
+1. Identify all DNS zones currently hosted on your BIND servers.
+2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.
+3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.
+   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.
    - For policy-based internal DNS, consider Cloudflare Zero Trust features such as DNS policies and Internal DNS (Beta). For more details, refer to [Cloudflare DNS](/dns/) and [Internal DNS](/dns/internal-dns/).
-4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:  
-   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.  
-   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.  
-   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:  
-      - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)  
-      - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)  
+4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:
+   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.
+   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.
+   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:
+     - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)
+     - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)
 
-      These setups document how to restrict which IP addresses can perform zone transfers.
+     These setups document how to restrict which IP addresses can perform zone transfers.
 
-5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.  
+5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.
 
 ## 2. Define scope and objectives
 
-Clearly list all domain names to be migrated and define success criteria for the migration.  
+Clearly list all domain names to be migrated and define success criteria for the migration.
 
 ## 3. Cloudflare account and familiarization
 
-1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.  
-2. Familiarize yourself with the Cloudflare DNS dashboard and its features.  
+1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.
+2. Familiarize yourself with the Cloudflare DNS dashboard and its features.
 3. Consider the different [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) you can manage on Cloudflare and how they map from BIND.
 
 ## 4. DNSSEC strategy (critical)
 
-Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.  
+Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.
 
-Cloudflare supports two main migration approaches when DNSSEC is enabled: 
+Cloudflare supports two main migration approaches when DNSSEC is enabled:
 
-   - Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.  
-   - Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).  
+- Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.
+- Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
-**Disable-and-re-enable approach (safer for most teams):**  
+**Disable-and-re-enable approach (safer for most teams):**
 
-1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.  
-2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.  
+1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.
+2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.
 
-*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.  
+\*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.
 
 For more information about DNSSEC on Cloudflare, refer to [DNSSEC](/dns/dnssec/).
 
 ## 5. Choose migration window
 
-Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.  
+Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.
 
 ## 6. Develop communication and rollback plan
 
-- Communication: Plan how to communicate with stakeholders before, during, and after the migration.  
-- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
\ No newline at end of file
+- Communication: Plan how to communicate with stakeholders before, during, and after the migration.
+- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
index f53af665ca87cfd..b3b2d045d7021ec 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
@@ -14,49 +14,49 @@ Careful preparation will minimize downtime and issues during the cutover.
 
 ## 1. Reduce DNS record TTLs (Time To Live)
 
-At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).  
+At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).
 
-This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.  
+This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.
 
-- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).  
+- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).
 
 ## 2. Export zone files from BIND
 
-Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.  
+Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.
 
 ## 3. Add domains to Cloudflare
 
-1. Log in to your Cloudflare dashboard.  
+1. Log in to your Cloudflare dashboard.
 
    <DashButton url="/?to=/:account/home" />
 
-2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.  
+2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.
 
 ## 4. Import DNS Records into Cloudflare
 
-Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.  
-   
-   <DashButton url="/?to=/:account/home" />
+Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.
+
+<DashButton url="/?to=/:account/home" />
 
-- Verification (Crucial): 
-   - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.  
-   - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.  
-   - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).  
-- Proxy status (orange vs grey cloud):  
-   - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.  
-   - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).  
-   - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
+- Verification (Crucial):
+  - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.
+  - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.
+  - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).
+- Proxy status (orange vs grey cloud):
+  - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.
+  - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).
+  - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
 
 ## 5. DNSSEC preparation (if currently enabled)
 
-Complete this step before you change your nameservers at the registrar.  
+Complete this step before you change your nameservers at the registrar.
 
 :::note
 
-For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy,  refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
 :::
 
-- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.  
+- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.
 - **Wait for DS TTL:** Wait at least the full DS record TTL published at the parent zone, and preferably up to 1.5 times that TTL, before you change nameservers. This ensures that validating resolvers stop expecting the old DNSSEC chain. The typical TTL duration for DS records is set to +24 hours (86,400 seconds).
-- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.  
+- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
index 7307e676b28660a..1decb20de5cda62 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
@@ -12,30 +12,29 @@ Phase 3 is when you make the actual switch to Cloudflare.
 
 ## 1. Final verification
 
-Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.  
+Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.
 
 ## 2. Update nameservers at your registrar
 
-   1. Log in to your domain registrar's control panel for each domain.  
-   2. Navigate to the section for managing nameservers.  
-   3. Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.  
-   4. Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).  
-   5. Save the changes.  
+1.  Log in to your domain registrar's control panel for each domain.
+2.  Navigate to the section for managing nameservers.
+3.  Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.
+4.  Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).
+5.  Save the changes.
 
 ## 3. Monitor propagation
 
-- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).  
-- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.  
-   - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)  
-   - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
-   - `whois yourdomain.com`
-   - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
-   
-   You are looking for the Cloudflare nameservers to be reported consistently. 
+- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).
+- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.
+  - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)
+  - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
+  - `whois yourdomain.com`
+  - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
+  You are looking for the Cloudflare nameservers to be reported consistently.
 
 ## 4. Initial testing
 
 Once propagation appears to be widespread, perform basic resolution tests for critical records (for example, your website's `A` record and any `MX` records, if you had them set up).
 
-- `dig yourdomain.com A +short`  
-- `dig yourdomain.com MX +short`
\ No newline at end of file
+- `dig yourdomain.com A +short`
+- `dig yourdomain.com MX +short`
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
index e1f0d1f96eb1bac..e08e73b597e57b0 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
@@ -14,47 +14,49 @@ After the cutover, verify and stabilize.
 
 ## 1. Thorough testing and validation
 
-1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.  
-2. Test from different networks and geographical locations if possible.  
-3. Monitor application logs for any DNS-related errors.  
+1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.
+2. Test from different networks and geographical locations if possible.
+3. Monitor application logs for any DNS-related errors.
 
 ## 2. Enable DNSSEC in Cloudflare (if disabled earlier)
 
 Enable DNSSEC only after you are confident that DNS is resolving correctly through Cloudflare and that nameserver changes have fully propagated. In practice, plan for at least one full DS TTL after you add new DS records at the registrar.
 
-**Action in Cloudflare:**  
-   1. In the Cloudflare dashboard, go to your zone's **DNS Settings**.  
+**Action in Cloudflare:**
 
-      <DashButton url="/?to=/:account/:zone/dns/settings" />
+1.  In the Cloudflare dashboard, go to your zone's **DNS Settings**.
 
-   2. Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details. 
- 
-**Action at registrar:**  
-   1. Log in to your domain registrar.  
-   2. Navigate to the DNSSEC management section for your domain.  
-   3. Add the `DS` record details provided by Cloudflare.  
+    <DashButton url="/?to=/:account/:zone/dns/settings" />
+
+2.  Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details.
+
+**Action at registrar:**
+
+1.  Log in to your domain registrar.
+2.  Navigate to the DNSSEC management section for your domain.
+3.  Add the `DS` record details provided by Cloudflare.
 
 After adding the `DS` record, allow time for propagation and then validate your configuration with tools such as [DNSViz](https://dnsviz.net) or [Verisign's DNSSEC debugger](https://dnssec-debugger.verisignlabs.com/). For more information, refer to [DNSSEC](/dns/dnssec/).
 
-   :::note
-    If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
-   :::
+:::note
+If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
+:::
 
 ## 3. Adjust TTLs in Cloudflare
 
-After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).  
+After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).
 
 Higher TTLs improve resolver cache efficiency and can reduce latency by allowing recursive resolvers to reuse cached answers for longer, at the cost of slower propagation when you make changes.
 
 ## 4. Review and enable Cloudflare proxy features
 
-If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.  
+If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.
 
 ## 5. Decommission On-Prem BIND servers
 
 Only after a significant stabilization period (for example, several days to a week after full propagation and successful testing) and when you are fully confident in the Cloudflare setup, decommission the on-premise BIND servers.
 
-Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.   
+Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.
 
 ## 6. Update internal documentation and monitoring
 
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
index 8e23617d11caed2..5d966db6e4f2e51 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
@@ -8,15 +8,15 @@ products:
   - dns
 ---
 
-- Plan meticulously: Do not rush the planning and preparation phases.  
-- Communicate clearly: Keep stakeholders informed.  
-- Lower TTLs in advance: This is crucial for a faster cutover.  
-- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.  
-- Verify, verify, verify: Double-check record imports and functionality at each stage.  
-- Test thoroughly: From multiple locations and for all critical services.  
-- Have a rollback plan: Know how to revert if necessary.  
-- Migrate during low traffic: Minimize potential user impact.  
-- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.  
+- Plan meticulously: Do not rush the planning and preparation phases.
+- Communicate clearly: Keep stakeholders informed.
+- Lower TTLs in advance: This is crucial for a faster cutover.
+- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.
+- Verify, verify, verify: Double-check record imports and functionality at each stage.
+- Test thoroughly: From multiple locations and for all critical services.
+- Have a rollback plan: Know how to revert if necessary.
+- Migrate during low traffic: Minimize potential user impact.
+- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.
 - Take advantage of Cloudflare features: Once stable, explore and implement Cloudflare's security and performance enhancements.
 
-By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
\ No newline at end of file
+By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
index 13c9e675861f17d..a1bed2340a8f735 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
@@ -12,4 +12,3 @@ products:
   - dlp
   - casb
 ---
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
index 4f342e9997e31ea..776126418ebd729 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
@@ -20,4 +20,3 @@ The goal of this learning path is to provide Cloudflare One users with the strat
 - Monitor AI usage: Utilize Cloudflare One's tools, such as the Shadow IT dashboard and API CASB integrations, to gain visibility into both sanctioned and unsanctioned AI application usage.
 - Build security policies: Create granular security policies using Cloudflare Gateway to control AI usage, prevent data loss with DLP, and manage user behavior through actions like blocking or redirecting.
 - Secure sanctioned models: Apply Zero Trust principles to sanctioned AI models and internal services like Model Context Protocol (MCP) servers to ensure secure access and protect sensitive data from being exposed.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
index c8811b8737b69c2..29330ef6e90787c 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
@@ -22,4 +22,3 @@ MCP uses a client-server architecture where an AI agent acts as the client and s
 ## What are the security concerns with MCP?
 
 MCP doesn't have native authentication, authorization, or encryption. Because it functions similarly to an API, many of the same security considerations apply. If developers do not proactively implement security measures like Transport Layer Security (TLS) and rate limiting, MCP servers can be vulnerable to attacks, data leaks, and unauthorized access. Organizations must ensure that they validate inputs and protect confidential data to secure their MCP implementations.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
index 1d18a0ebba41b16..97b3651ba7daa5d 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
@@ -18,4 +18,3 @@ Shadow AI is the use of any AI tool or application by employees without the form
 Since it may not be feasible to eliminate all instances of shadow AI, organizations can manage the risks by taking a balanced approach. First, it is essential to foster collaboration and open communication between IT and other departments to understand why employees are using these tools. Next, implement guardrails by developing a flexible governance framework with clear guidelines on which types of AI systems can be used and how sensitive information should be handled. Finally, monitor AI usage with network tools to track what is being used and educate employees on the risks of unauthorized AI.
 
 To combat the risks associated with shadow AI, Cloudflare's API-driven CASB integrates with SaaS applications and cloud environments to scan for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
index f98c47c842d9d81..2f4c30d5cb527a1 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
@@ -16,4 +16,4 @@ To use the recommended AI security solutions in this learning path, you will nee
 
 :::note
 If you are new to securing your Internet traffic, refer to [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/) to get started and then return to this learning path to continue securing your organizations.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
index 67b07408d9070cd..7b68b9d51991f49 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
@@ -17,6 +17,7 @@ Before you can secure AI, you need to understand your organization's goals and c
 The level of risk you are willing to accept will determine how quickly you need to act and how deeply you need to implement security measures. Your specific concerns will then guide the exact security approaches you take to monitor and control AI usage.
 
 To begin, consider these questions to help shape your strategy:
+
 - Sanctioned versus shadow AI: Are your employees already using approved AI services, or are you primarily concerned with shadow AI — unapproved applications that may pose a risk? Note: Some approved vendors may offer embedded AI functionality. Consider whether those AI services are a risk, too.
 - Data sensitivity: What types of sensitive data do you currently monitor, classify, and protect? This will help you identify what you need to safeguard when employees interact with AI. If you have not determined this yet, refer to [Define your sensitive data](/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention/#define-your-sensitive-data) to learn more.
 - Encouraging user behavior: Do you want to encourage or limit user engagement with AI? How much do you expect your employees to use AI in a controlled, sanctioned way?
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
index b5caf20d92a283f..d466618622bbdb9 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
@@ -16,4 +16,4 @@ Businesses are eager to realize the potential boosts to productivity and efficie
 
 IT and security leaders are often asked to address risks and deal with increasing challenges like the use of shadow AI before they have an AI security strategy.
 
-Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively. 
+Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
index 48c3654da15b283..5edae280f6bbf30 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
@@ -17,4 +17,3 @@ Monitoring AI usage is one of the first steps in assessing holistic risk. Cloudf
 After you begin to understand your organization's AI usage, you should develop a balanced perspective on what constitutes sanctioned use of a tool. A good practice is to review applications in phases and then apply security policies based on those phases. For example, you can apply different security policies to applications that are considered approved, unapproved, unreviewed, or in review until they pass your corporate security standards and data privacy reviews.
 
 This section will detail options for assessing and understanding that risk by using inline (client) and out-of-band (API CASB) based methods.
-
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
index 38cfd98df28c2ac..18a65bd00076557 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
@@ -13,10 +13,11 @@ products:
 ---
 
 When you enable [TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/#turn-on-tls-decryption), you can review the prompts and responses for supported AI applications. This allows you to understand three key things about AI application usage:
+
 - The sanctioned and unsanctioned AI tools your users are engaging with.
 - How they are interacting with them.
 - What information they are sharing.
 
 ![Log entry for a prompt detected using AI prompt protection.](~/assets/images/learning-paths/holistic-ai-security/gateway-prompt-log.png)
 
-You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
\ No newline at end of file
+You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
index c60e183df9211b9..aacf8456e79fe1c 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
@@ -20,7 +20,6 @@ To review how your organization uses AI apps, start with the Cloudflare [Shadow
 
 ![Shadow IT dashboard showing utilization of application statuses (Approved, Unapproved, In Review, Unreviewed).](~/assets/images/learning-paths/holistic-ai-security/shadowit-dashboard-ai-apps.png)
 
-This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as *Approved*. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
+This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as _Approved_. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
 
 ![The App Library filtered to show some of the supported Artificial Intelligence applications.](~/assets/images/learning-paths/holistic-ai-security/ai-app-type-app-library.png)
-
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
index 9d1796cbc8e77a5..da4bbe2960c586f 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { GlossaryDefinition, Render } from "~/components"
+import { GlossaryDefinition, Render } from "~/components";
 
 There's more to a load balancer than just distributing traffic, however.
 
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
index 2a58f062dc5eeeb..7369a7445edbd8d 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
@@ -14,7 +14,7 @@ Learn the concepts behind load balancing, whether you are using Cloudflare or an
 
 By the end of this module, you will be able to:
 
-* Explain what load balancing is.
-* Describe the differences between load balancers, pools, and servers.
-* Explain what pool health is and how it affects load balancer traffic.
-* List the different ways your traffic can be routed.
+- Explain what load balancing is.
+- Describe the differences between load balancers, pools, and servers.
+- Explain what pool health is and how it affects load balancer traffic.
+- List the different ways your traffic can be routed.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
index 7dd7ff6d269783a..e132195e0f7fb3a 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
@@ -8,13 +8,13 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 At it's most basic, load balancing is made up of three components:
 
-* **Pools**: Which contain one or more endpoints.
-* **Endpoints**: Which respond to individual requests.
-* **A load balancer**: Which decides which traffic goes to each pool.
+- **Pools**: Which contain one or more endpoints.
+- **Endpoints**: Which respond to individual requests.
+- **A load balancer**: Which decides which traffic goes to each pool.
 
 ## How it works
 
@@ -22,7 +22,7 @@ Normally, requests to your application would go to individual servers directly.
 
 With a load balancer, requests first go through the load balancer. Your load balancer then routes requests to specific pools.
 
-<Render file="load-balancing-diagram" product="load-balancing" /> <br/>
+<Render file="load-balancing-diagram" product="load-balancing" /> <br />
 
 Within each pool, requests then go to individual endpoints. And that endpoint is what responds to the request.
 
@@ -37,6 +37,6 @@ Within each pool, requests then go to individual endpoints. And that endpoint is
       end
 ```
 
-<br/>
+<br />
 
 This progression of load balancer --> pool --> endpoint is the core part of how a load balancer works.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
index b5cf54d4113227f..d8019a91c1cf983 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
@@ -8,11 +8,11 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Before, we covered how requests move from load balancers to pools and then from pools to individual servers.
 
-What we did not mention, however, was *how* the load balancer and pools make those decisions.
+What we did not mention, however, was _how_ the load balancer and pools make those decisions.
 
 This is a concept known as routing.
 
@@ -60,5 +60,5 @@ Often, load balancers have a special pool known as the **Fallback Pool**, which
 
 Finally, specific settings can also affect the ways a load balancer distributes traffic, such as:
 
-* Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
-* Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
+- Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
+- Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
index 6337e5cf7172cd6..cc8e287532908ff 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="custom-rules-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/index.mdx b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
index eeee73027d3ca18..370f197fbab2a2d 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
@@ -14,7 +14,7 @@ Explore the configuration choices available for your Cloudflare load balancer.
 
 By the end of this module, you will be able to:
 
-* Describe the difference between load balancing at different layers of the network stack.
-* Identify when a load balancer should utilize session affinity.
-* Describe the different policies for endpoint steering and traffic steering.
-* List the different options available to monitor server health.
+- Describe the difference between load balancing at different layers of the network stack.
+- Identify when a load balancer should utilize session affinity.
+- Describe the different policies for endpoint steering and traffic steering.
+- List the different options available to monitor server health.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
index 34aa1d6847c2ece..820f34fada45575 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
@@ -20,10 +20,8 @@ If you want to share a load balancing configuration across multiple hostnames, y
 
 :::note
 
-
 You could also achieve the same goal or create more advanced routing decisions by setting up DNS Overrides within [Origin Rules](/rules/origin-rules/) on each hostname that override the hostname to `lb.example.com`.
 
-
 :::
 
 ## Unique configurations
diff --git a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
index d03dbb9b4796bd1..b430e5865cbd6a6 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
@@ -8,17 +8,17 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="origin-steering-definition" product="load-balancing" />
 
-***
+---
 
 ## Policies
 
 <Render file="origin-steering-policies" product="load-balancing" />
 
-***
+---
 
 ## Weights
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
index dd99e87ee3c3d01..70a7b3e021585fc 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="session-affinity-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
index 9ced34523117fe9..3b370b1ed392b31 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
@@ -8,8 +8,8 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
-<Render file="traffic-steering-definition" product="load-balancing" /> <br/>
+<Render file="traffic-steering-definition" product="load-balancing" /> <br />
 
 <DirectoryListing folder="load-balancing/understand-basics/traffic-steering/steering-policies" />
diff --git a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
index a1fbbb640bf00cb..1b2a9ce5c84006d 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
@@ -8,15 +8,15 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 With Cloudflare, you can choose between three types of load balancers:
 
-* [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
-* [DNS-only](#dns-only-load-balancing)
-* [Layer 4 (TCP)](#layer-4-load-balancing)
+- [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
+- [DNS-only](#dns-only-load-balancing)
+- [Layer 4 (TCP)](#layer-4-load-balancing)
 
-***
+---
 
 ## Layer 7 load balancing
 
@@ -26,7 +26,7 @@ With Cloudflare, you can choose between three types of load balancers:
 
 <Render file="layer-7-load-balancing-benefits" product="load-balancing" />
 
-***
+---
 
 ## DNS-only load balancing
 
@@ -34,13 +34,13 @@ With Cloudflare, you can choose between three types of load balancers:
 
 ### Benefits
 
-<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br/>
+<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br />
 
 ### Limitations
 
 <Render file="dns-load-balancing-limitations" product="load-balancing" />
 
-***
+---
 
 ## Layer 4 load balancing
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
index e44453449357179..a34dcbf56c1a141 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="confirm-pool-health" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
index f963bd4a1cc3aee..54cf2a41d9f5d89 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
@@ -10,8 +10,8 @@ products:
 
 Before setting up anything related to your load balancer, make sure you test that production hostnames meet the following criteria:
 
-* Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
-* Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
+- Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
+- Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 
 After confirming each of these conditions are met, you can proceed with setting up your load balancer.
 
@@ -19,5 +19,5 @@ After confirming each of these conditions are met, you can proceed with setting
 
 Depending on your preferences and infrastructure, you might route traffic to your load balancer in different ways:
 
-* For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
-* However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
+- For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
+- However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/index.mdx b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
index 20b76253146a2fe..2f7ceb3e5cd7744 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
@@ -14,13 +14,13 @@ Create a load balancer that monitors endpoint health and intelligently routes tr
 
 By the end of this module, you will be able to:
 
-* Configure a monitor and health checks.
-* Create a pool.
-* Create a load balancer.
-* Analyze traffic patterns.
+- Configure a monitor and health checks.
+- Create a pool.
+- Create a load balancer.
+- Analyze traffic patterns.
 
 ## Prerequisites
 
-* Multiple endpoints, either physical or cloud-based.
-* Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
-* Two hostnames, one for test traffic and the other for production traffic.
+- Multiple endpoints, either physical or cloud-based.
+- Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
+- Two hostnames, one for test traffic and the other for production traffic.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
index 7dea7a8b054a166..5cb5b8556548c35 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Your load balancer should be receiving production traffic (and you can confirm this by reviewing the [analytics](/load-balancing/reference/load-balancing-analytics/)).
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
index f2dda24cae894f0..5f6e8812e2b018b 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
@@ -8,6 +8,6 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="route-production-traffic" product="load-balancing" />
diff --git a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
index 158ed1dbb6f5b89..a9014dbe620e151 100644
--- a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
+++ b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
@@ -20,10 +20,10 @@ Some common mTLS use cases are:
 
 There are two main ways to use mTLS at Cloudflare, either by using the Application Security offering (optionally including [API Shield](/api-shield/)) or [Cloudflare Access](/cloudflare-one/access-controls/policies/). Below is a non-exhaustive overview table of their differences:
 
-| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | Client Certificate Details                                            | Forwarded to the origin server via [Cloudflare API](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-api), [Cloudflare Workers](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-workers), and [Managed Transforms](/ssl/client-certificates/forward-a-client-certificate/#managed-transforms). | Forwarded to the origin server via [Cloudflare API](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-api), [Cloudflare Workers](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-workers), and [Managed Transforms](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#managed-transforms). Client Certificate headers and [Cf-Access-Jwt-Assertion](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/) JWT header can be forwarded to the origin server. |
-| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                         |
+| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                                                     |
diff --git a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
index 93042dd1fa01f4d..4bc6231c21b5a96 100644
--- a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
+++ b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
@@ -26,4 +26,4 @@ mTLS user authentication is included with Cloudflare Access and depends on the n
 
 ## Option 3: mTLS Service Authentication
 
-The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
\ No newline at end of file
+The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
index 16c8ccf32ad86d5..c481f87de2d65a0 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 Cloudflare provides analytics for [security events](/waf/analytics/security-events/), [traffic patterns](/analytics/account-and-zone-analytics/zone-analytics/), and more according to the level of your zone's plan.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
index a4da185bc6f5065..05f03d0f144275e 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
@@ -15,7 +15,7 @@ Learn how to customize and augment Cloudflare’s DDoS protection.
 
 By the end of this module, you will be able to:
 
-* Audit DNS records to prevent accidental IP address exposures.
-* Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
-* Augment Cloudflare's default analytics to examine attacks in more detail.
-* Evaluate different ways to restrict external connections to your origin server.
+- Audit DNS records to prevent accidental IP address exposures.
+- Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
+- Augment Cloudflare's default analytics to examine attacks in more detail.
+- Evaluate different ways to restrict external connections to your origin server.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
index c37bbf8ec26a7db..c2f9d500ff25ee7 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
@@ -15,6 +15,6 @@ Get world-class DDoS protection with a few simple steps.
 
 By the end of this module, you will be able to:
 
-* List the built-in DDoS protection measures provided by Cloudflare.
-* Implement a few, simple customizations to improve DDoS protection.
-* Set up DDoS-related notifications.
+- List the built-in DDoS protection measures provided by Cloudflare.
+- Implement a few, simple customizations to improve DDoS protection.
+- Set up DDoS-related notifications.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
index d464cb2979e60be..882b2ac86f7af63 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 The first - and often easiest - step of DDoS protection is making sure your DNS records are [proxied](/dns/proxy-status/) through Cloudflare.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
index 52946023a5865ab..504b661aeade97c 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Another part of preparing for DDoS attacks is knowing when your application is being attacked.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
index 315ae18c24d496c..2dde4bb728e4cad 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
@@ -13,8 +13,8 @@ In some circumstances - specifically when an application allows client-initiated
 
 When you use an SSL/TLS certificate issued by Cloudflare[^1], you can reduce the impact of this vulnerability by:
 
-* Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
-* Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
+- Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
+- Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
 
 [^1]: Meaning either [Universal](/ssl/edge-certificates/universal-ssl/) or [Advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
index cfb31f718c1afba..5d276a7499bc51b 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
@@ -15,5 +15,5 @@ Learn the concepts behind DDoS attacks and protection, whether you are using Clo
 
 By the end of this module, you will be able to:
 
-* Explain what a DDoS attack is and how it could affect your application.
-* List the common ways to prevent DDoS attacks.
+- Explain what a DDoS attack is and how it could affect your application.
+- List the common ways to prevent DDoS attacks.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
index bc327a66a03d394..55992a486b4f980 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
@@ -18,7 +18,7 @@ With Cloudflare Zero Trust, you can apply granular security policies to all traf
 
 By the end of this module, you will be able to:
 
-* Create Zero Trust policies to secure access to your private network.
-* Enforce Cloudflare One Client session timeouts.
-* Display custom block messages.
-* Discover Shadow IT within your private network.
+- Create Zero Trust policies to secure access to your private network.
+- Enforce Cloudflare One Client session timeouts.
+- Display custom block messages.
+- Discover Shadow IT within your private network.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
index 29387c50590e5a7..78c93a432dea818 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
@@ -17,11 +17,11 @@ Most policy building for private network access happens within the Gateway DNS a
 
 Before building your policies, it is helpful to ask yourself a few questions:
 
-* Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
-* Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
-* Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
-* Do you have sources of truth for identity and device posture that will be used in policies?
-* Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
+- Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
+- Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
+- Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
+- Do you have sources of truth for identity and device posture that will be used in policies?
+- Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
 
 ## Prepare to build policies
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
index 943c9627d37f792..a78d1ef69ea07de 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Most legacy VPNs have a global timeout setting that requires end users to log in every X hours or resets VPN profiles at a certain frequency. By doing continuous identity evaluation, a Zero Trust security model eliminates the need for most of the user-interrupting workflows triggered by session timeouts. However, there can still be valid reasons to want users to reauthenticate, either on a recurring basis or to access specific, highly-sensitive or regulated internal services.
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
index 10077edc657d785..43ea4220994ee40 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
@@ -43,11 +43,13 @@ Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build
 [Logs](/cloudflare-one/insights/logs/) provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment.
 
 To review traffic activity for applications protected by Access:
+
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **Access authentication logs**.
 3. Review the [per-request logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#per-request-logs) for your application.
 
 To review traffic activity in the [Gateway logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/):
+
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **HTTP request logs**, **Network logs**, or **DNS query logs** depending on your investigation scope.
 
@@ -98,7 +100,8 @@ To create a device connectivity anomaly notification:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-    <DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select **Add**.
 3. Find **Product** DEX and **Alert type** Device connectivity anomaly, and choose **Select**.
 4. Name the notification.
@@ -116,4 +119,4 @@ Once your policies are live, you can use [DEX tests](/learning-paths/replace-vpn
 
 To learn how to use Logs, Analytics, and DEX together during real-world situations, like onboarding, daily monitoring, and troubleshooting, refer to [Insights](/cloudflare-one/insights/) for more example use cases.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
index f21582fa384073e..e227e835a77f69b 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
@@ -17,6 +17,6 @@ Concepts explain the basic ideas behind how Cloudflare Zero Trust works.
 
 By the end of this module, you will be able to:
 
-* Explain how Cloudflare works.
-* Describe the purpose of a VPN.
-* Understand the benefits of switching to a Zero Trust architecture.
+- Explain how Cloudflare works.
+- Describe the purpose of a VPN.
+- Understand the benefits of switching to a Zero Trust architecture.
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
index 9d605a12bcca0b2..92bfa07cbd99ff5 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
index 62f98d74710996a..7a46245dacacf0c 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
@@ -12,7 +12,7 @@ products:
   - gateway
 ---
 
-import { Render, Tabs, TabItem } from "~/components"
+import { Render, Tabs, TabItem } from "~/components";
 
 Cloudflare Tunnel is an outbound-only daemon service that can run on nearly any host machine and proxies local traffic once validated from the Cloudflare network. User traffic initiated from the Cloudflare One Client onramps to Cloudflare, passes down your Cloudflare Tunnel connections, and terminates automatically in your local network. Traffic reaching your internal applications or services will carry the local source IP address of the host machine running the `cloudflared` daemon.
 
@@ -73,17 +73,16 @@ All internal applications and services in this IP range are now connected to Clo
 
 If the tunnel is disconnected:
 
-* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
-
+- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
 
 :::
 
 ## Best practices
 
-* Segregate production and staging traffic among different Cloudflare tunnels.
-* Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
-* Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
-* [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
-* [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
-* [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
+- Segregate production and staging traffic among different Cloudflare tunnels.
+- Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
+- Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
+- [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
+- [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
+- [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
index d36ecb80dd109d4..9ff188f45e603dd 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
@@ -33,17 +33,17 @@ There are [multiple ways](/reference-architecture/architectures/sase/#connecting
 
 ## Comparison table
 
-|                       | Cloudflare Mesh                 | Cloudflare Tunnel           |
-| --------------------- | ------------------------------- | --------------------------- |
-| Bidirectional traffic | ✅                              | ❌                          |
-| High availability     | ✅ (active-passive)             | ✅ (active-active replicas) |
-| Source IP of request  | Virtual IP of requesting device | `cloudflared` host machine  |
-| Host machine          | Linux (amd64, arm64)            | Linux, macOS, Windows       |
-| IPv4                  | ✅                              | ✅                          |
-| IPv6                  | ✅                              | ✅                          |
-| OSI layer             | L3                              | L7                          |
-| Protocol              | MASQUE                          | QUIC or HTTP/2              |
-| Protocols proxied     | TCP, UDP, ICMP                  | HTTP/S, TCP, SSH, RDP, SMB  |
+|                       | Cloudflare Mesh                                                        | Cloudflare Tunnel                                                                                                                                                                                                                                   |
+| --------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bidirectional traffic | ✅                                                                     | ❌                                                                                                                                                                                                                                                  |
+| High availability     | ✅ (active-passive)                                                    | ✅ (active-active replicas)                                                                                                                                                                                                                         |
+| Source IP of request  | Virtual IP of requesting device                                        | `cloudflared` host machine                                                                                                                                                                                                                          |
+| Host machine          | Linux (amd64, arm64)                                                   | Linux, macOS, Windows                                                                                                                                                                                                                               |
+| IPv4                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
+| IPv6                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
+| OSI layer             | L3                                                                     | L7                                                                                                                                                                                                                                                  |
+| Protocol              | MASQUE                                                                 | QUIC or HTTP/2                                                                                                                                                                                                                                      |
+| Protocols proxied     | TCP, UDP, ICMP                                                         | HTTP/S, TCP, SSH, RDP, SMB                                                                                                                                                                                                                          |
 | Connection handling   | End-to-end — preserves long-lived TCP connections across the full path | Proxied — TCP connections are terminated and re-established at Cloudflare, which can interrupt long-lived sessions (for example, SAP transactions, database replication streams, or persistent RDP sessions may drop when `cloudflared` reconnects) |
 
 ## Recommendation
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
index 8dfc2d8f3e258e1..73d7ed1fcc063fd 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
@@ -17,6 +17,6 @@ This module covers how to connect your private network services and applications
 
 By the end of this module, you will be able to:
 
-* Create a Cloudflare Tunnel.
-* Configure private network routes for your tunnel.
-* Understand how to size and scale your tunnel.
+- Create a Cloudflare Tunnel.
+- Configure private network routes for your tunnel.
+- Understand how to size and scale your tunnel.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
index c6b1493e5165c97..536d489c6b31be9 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
@@ -10,7 +10,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="tunnel/virtual-networks-intro" product="cloudflare-one" />
 
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
index 91c1e173b09527c..061277556b36313 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Now that you have a Cloudflare Tunnel up and running, evaluate whether `cloudflared` has enough system resources to handle the expected volume of requests from end users. <Render file="tunnel/availability/tunnel-capacity-intro" product="cloudflare-one" />
 If you have exhausted the ports on a single machine, you will need to add additional servers running `cloudflared`.
diff --git a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
index 9add3ff07321ee9..b7e1bbfc5ccef53 100644
--- a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
@@ -13,7 +13,7 @@ products:
 
 To make the most of this learning path, make sure that you have the following:
 
-* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-* A private network with applications or services that are available locally or via a VPN.
-* A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
-* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
+- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+- A private network with applications or services that are available locally or via a VPN.
+- A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
+- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
index a516b09d3f257d6..1b88fb9f8b8b920 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
@@ -19,7 +19,7 @@ Learn how to troubleshoot your ZTNA deployment.
 
 By the end of this module, you will be able to:
 
-* Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
-* Fix the most common causes of connectivity issues.
+- Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
+- Fix the most common causes of connectivity issues.
 
 <Render file="warp/troubleshooting-guide-reference" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
index e4c61751d31b4a3..4a8c12e1c07aa82 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="tunnel/troubleshoot-private-networks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
index fa82b98809cbb10..d83c0f50abab201 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
@@ -18,6 +18,6 @@ DNS security is an important, wide-reaching, and early action in the lifecycle o
 
 By the end of this module, you will be able to:
 
-* Create your first Gateway DNS policy.
-* Build an allow or block list for use in firewall policies.
-* Onboard networks to Gateway to filter DNS queries.
+- Create your first Gateway DNS policy.
+- Build an allow or block list for use in firewall policies.
+- Onboard networks to Gateway to filter DNS queries.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
index 3a42196c4090ecc..3264f26eb9ea844 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
@@ -16,18 +16,16 @@ Now that you have created firewall policies to secure your organization, you can
 
 :::note
 
-
 The following module requires [egress policies](/cloudflare-one/traffic-policies/egress-policies/), a feature only available on Enterprise plans. If you are not an Enterprise user, you can skip ahead to [Secure SaaS applications](/learning-paths/secure-internet-traffic/secure-saas-applications/).
 
 For more information on egress policies, contact your account team.
 
-
 :::
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-* Understand when your organization may need source IP anchoring.
-* Create egress policies to make use of dedicated egress IPs.
-* Follow best practices for deploying egress IPs.
+- Understand when your organization may need source IP anchoring.
+- Create egress policies to make use of dedicated egress IPs.
+- Follow best practices for deploying egress IPs.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
index b67afebdb19655c..486ba1b10c7e8c0 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
@@ -18,7 +18,7 @@ After securing your organization's DNS queries and network level traffic, you ca
 
 By the end of this module, you will be able to:
 
-* Understand how and when to use TLS inspection to decrypt HTTPS traffic.
-* Configure and enable Data Loss Prevention to protect your organization's sensitive data.
-* Protect user endpoints with Browser Isolation.
-* Add recommended HTTP security policies.
+- Understand how and when to use TLS inspection to decrypt HTTPS traffic.
+- Configure and enable Data Loss Prevention to protect your organization's sensitive data.
+- Protect user endpoints with Browser Isolation.
+- Add recommended HTTP security policies.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
index 71711da35cc0387..8d4115bd0b7fde1 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
@@ -18,5 +18,5 @@ Learn the core concepts of using Cloudflare Zero Trust functionality to provide
 
 By the end of this module, you will be able to:
 
-* Understand what products and features Cloudflare offers.
-* Describe how Cloudflare implements Internet traffic and SaaS app security.
+- Understand what products and features Cloudflare offers.
+- Describe how Cloudflare implements Internet traffic and SaaS app security.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
index 319216b4c04291b..a22224d4e229731 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
@@ -36,12 +36,12 @@ Cloudflare supports filtering HTTP/S traffic sent via a PAC file on a user devic
 
 Cloudflare Browser Isolation runs a headless, Chromium-based browser for your users to accomplish their secure browsing needs. It can be activated via an Access application, a Gateway policy, or by using link-based isolation (reverse proxy). In this model, your users can connect from any device to a proxy website to browse the Internet while applying all your Gateway HTTP policies and inspection requirements.
 
-|                                   | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
-| --------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
-| Supported OS                      | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
-| Configurable via MDM              | Yes                                  | Yes            | N/A                                   |
-| Gateway policy types supported    | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
-| Identity-based policies supported | Yes                                  | No             | Yes                                   |
+|                                                                                                 | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
+| Supported OS                                                                                    | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
+| Configurable via MDM                                                                            | Yes                                  | Yes            | N/A                                   |
+| Gateway policy types supported                                                                  | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
+| Identity-based policies supported                                                               | Yes                                  | No             | Yes                                   |
 | [Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Yes                                  | Yes            | Yes                                   |
 
 ## Network on-ramps
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
index 14f947c033c85f7..0317f717c9237be 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
@@ -14,5 +14,5 @@ products:
 
 To make the most of securing your Internet traffic and SaaS apps, make sure that you have the following:
 
-* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
+- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
index 1dcb52b2c614a63..e67e85f67da54d6 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
@@ -18,6 +18,6 @@ Now that you have deployed dedicated egress IPs and created egress policies to a
 
 By the end of this module, you will be able to:
 
-* Secure your SaaS applications by integrating them with Cloudflare CASB.
-* Control access to your SSO front door.
-* Layer multiple security methods for protecting SaaS apps.
+- Secure your SaaS applications by integrating them with Cloudflare CASB.
+- Control access to your SSO front door.
+- Layer multiple security methods for protecting SaaS apps.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
index 52d73e8318fb87d..92db03a4e2e98a1 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
@@ -18,10 +18,10 @@ products:
 
 Access for SaaS integrates directly with your SaaS app using standard protocols (such as SAML) to become the primary enforcement point for user access. Access calls your identity provider (IdP) of choice and uses additional security signals about your users and devices to make policy decisions. Benefits of Access for SaaS include:
 
-* A streamlined experience for users on both managed and unmanaged devices.
-* Application of baseline policies requiring specific concepts such as device posture and endpoint control.
-* Distinct access methodology for contractors.
-* Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
+- A streamlined experience for users on both managed and unmanaged devices.
+- Application of baseline policies requiring specific concepts such as device posture and endpoint control.
+- Distinct access methodology for contractors.
+- Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
 
 ### SSO integrations
 
@@ -29,10 +29,8 @@ You can pair Access for SaaS with the [App Launcher](/cloudflare-one/access-cont
 
 :::note[SCIM provisioning limitation]
 
-
 Access for SaaS supports SCIM passthrough in an API-only closed beta. If you require SCIM passthrough, contact your account team.
 
-
 :::
 
 ## Configure your SSO provider
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
index 4028b6ad5e95765..3e738d411947195 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
@@ -22,6 +22,6 @@ This guide will provide you with a baseline of recommended policies to build and
 
 By the end of this module, you will be able to:
 
-* Understand the order Gateway enforces policies for filtering traffic.
-* Create reusable lists for Gateway policies.
-* Subscribe to indicator feeds for advanced threat intelligence.
+- Understand the order Gateway enforces policies for filtering traffic.
+- Create reusable lists for Gateway policies.
+- Subscribe to indicator feeds for advanced threat intelligence.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
index d37b3443e21db00..288ad4bd4f9c714 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When building DNS, network, or HTTP policies to block malicious activity for your organization, you can use external indicator feeds supplied by Cloudflare and other third-party providers.
 
@@ -20,4 +20,4 @@ When building DNS, network, or HTTP policies to block malicious activity for you
 
 <Render file="indicator-feeds-overview" product="security-center" />
 
-To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
\ No newline at end of file
+To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
index 4613217ef45c558..075efbb8570f006 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Gateway follows a specific order of enforcement as traffic travels through the Cloudflare global network to the Internet:
 
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
index 094d430d9789447..779c314e0307099 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
@@ -16,4 +16,4 @@ By the end of this module, you will be able to:
 
 - Explain how Cloudflare works.
 - Describe what Email security is.
-- Understand how Cloudflare prevents email-based phishing attacks.
\ No newline at end of file
+- Understand how Cloudflare prevents email-based phishing attacks.
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
index 325d8d4fbe5e300..a81f77056268cbd 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
@@ -16,4 +16,4 @@ As organizations continue to adopt Microsoft 365 and Google Workspace to enhance
 
 Analysts agree that consolidating capabilities to minimize overlapping functionality is helping organizations reduce cost and complexity. However, they also advise organizations to carefully assess native features to ensure they satisfy all use cases. As Microsoft and Google continue to build out its essential email security features, the growing overlap with SEGs has given organizations an opportunity to streamline security operations by leveraging capabilities already included in their E3 or E5 license.
 
-This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
\ No newline at end of file
+This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
index 606e29d7f67ce79..6810419da647886 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="what-is-cloudflare" product="fundamentals" />
\ No newline at end of file
+<Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
index 972a75f3e69fb82..e751db0ccb39b91 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
@@ -10,4 +10,4 @@ products:
 
 Despite email's importance as a communication method, security and privacy were not built into the [The Simple Mail Transfer Protocol (SMTP) protocol](https://www.cloudflare.com/learning/email-security/what-is-smtp/). As a result, email is a major attack vector.
 
-Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
\ No newline at end of file
+Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
index 1134bd825289830..2476b73b8cb70b2 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
@@ -12,4 +12,4 @@ products:
 
 Phishing attackers disguise themselves as a reputable source. With an enticing or seemingly urgent request, an attacker lures the victim into providing information, just as a person uses bait while fishing.
 
-Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
\ No newline at end of file
+Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
index a017783809f59cb..09e0b06afb41ca9 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
@@ -49,4 +49,4 @@ In addition, Email security allows you to:
 
 - [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry).
 - [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry).
-- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
\ No newline at end of file
+- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
index 665a142ede96132..8df6912430c831b 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
@@ -21,7 +21,6 @@ To enable audit logs:
 2. Select your storage destination.
 3. Select the three dots > **Edit**.
 4. Under **Configure logpush job**:
-
    - **Job name**: Enter the job name, if it is not already prepopulated.
    - **If logs match** > Select **Filtered logs**:
      - **Field**: Choose `ResourceType`.
@@ -30,4 +29,4 @@ To enable audit logs:
 
 5. Select **Submit**.
 
-You can now view logs via the Cloudflare dashboard.
\ No newline at end of file
+You can now view logs via the Cloudflare dashboard.
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
index 0378058f8d87ec6..fbbb6474283ca81 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
@@ -30,4 +30,4 @@ To add a user to the impersonation registry:
      - **Add users or groups**: Choose the users or groups you want to register.
 6. Select **Save**.
 
-For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
\ No newline at end of file
+For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
index 461cbd6dbd19774..2e7a4d8bfb7cbe7 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
@@ -10,4 +10,4 @@ products:
 
 With Email security, there is limited manual configuration and tuning. The Active Directory sync, allow policies, and additional detections are important to consider when you set up Email security.
 
-In this module, you will configure your email environment.
\ No newline at end of file
+In this module, you will configure your email environment.
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
index 3cc5f8cd3fe2d8c..ba4ad5c0c65ba4a 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
@@ -33,4 +33,4 @@ To set up PhishNet for Google Workspace:
 1. Log in to the Google Workspace Marketplace using an administrator account.
 2. Select **Admin install** to install Cloudflare PhishNet.
 
-Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
\ No newline at end of file
+Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
index 34c5572c1d9bd7f..6efc9e48a5b5f2c 100644
--- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
@@ -16,4 +16,4 @@ Ensure you have completed the previous modules before enabling auto-moves.
 
 Auto-move events are events where emails are automatically moved to different inboxes based on the disposition assigned to them by Email security.
 
-When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
\ No newline at end of file
+When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
index a5209b5455fedb9..20822f04cf3be59 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
@@ -20,8 +20,8 @@ If you are a Google Workspace user, you can enable Email security via [BCC setup
 
 ![Google Workspace BCC deployment diagram](~/assets/email-security/Gmail_Deployment_BCC.png)
 
-With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection. 
+With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection.
 
 ![Microsoft 365 and Google Workspace MX/Inline](~/assets/email-security/Email_security_Deployment_Inline.png)
 
-Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
\ No newline at end of file
+Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
index 16e8a6a9cc6b7f5..ddf2e2a40c90def 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
@@ -8,4 +8,4 @@ products:
   - email-security
 ---
 
-To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account. 
\ No newline at end of file
+To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
index a83c5051a08616c..891d3080a754f62 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
@@ -16,4 +16,4 @@ The API deployment with Email security offers:
 - Agentless deployment for Microsoft 365.
 - Office 365 directory integration to retrieve user and group information and prevent user impersonation.
 
-![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
\ No newline at end of file
+![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
index 28bf9247f9c6975..3743a5c02f2a30e 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
@@ -11,4 +11,4 @@ products:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**.
-4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
\ No newline at end of file
+4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
index 447dea2119c80ba..1c65ac9d9434a5c 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
@@ -12,7 +12,7 @@ products:
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**.
 4. Enable **Microsoft Integration**:
-   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. 
+   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration.
    2. **Name integration**: Add your integration name, then select **Continue**.
    3. **Authorize integration**:
       - Select **Authorize**. Selecting **Authorize** will take you to the Microsoft Sign in page where you will have to enter your email address.
@@ -20,4 +20,4 @@ products:
       - After selecting **Next**, the system will show a dialog box with a list of requested permissions. Select **Accept** to authorize Email security. Upon authorization, you will be redirected to a page where you can review details and enroll integration.
    4. **Review details**: Review your integration details, then:
       - Select **Complete Email security set up** where you will be able to connect your domains and configure auto-moves.
-      - Select **Continue to Email security**.
\ No newline at end of file
+      - Select **Continue to Email security**.
diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
index e5a57972d2a82f0..40565ed07e17558 100644
--- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
@@ -17,4 +17,4 @@ There are two different ways to [submit a phish](/cloudflare-one/email-security/
   - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you.
 - Admin submission:
   - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address.
-  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
\ No newline at end of file
+  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
diff --git a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
index 3432b43cd002658..47bf090845f40be 100644
--- a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
@@ -20,15 +20,15 @@ To learn more about our service offerings, refer to [Customer Success offerings]
 
 For the security and protection of your account, be sure to register all account users.
 
-1. In the Cloudflare dashboard, go to the  **Manage Account** > **Members** page.
+1. In the Cloudflare dashboard, go to the **Manage Account** > **Members** page.
 
-    <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Select more than one Super Administrator to ensure appropriate access when needed.
 
 :::note
 
-Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users. 
+Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users.
 
 :::
 
@@ -50,7 +50,7 @@ We strongly advise against credential-sharing which can jeopardize the trust and
   Certificates managed by Cloudflare are auto-renewed.
   :::
 - Review your Operational and Disaster recovery preparedness
-    - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
-    - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
+  - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
+  - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
 - Review and update your current users' access
-- Check your domain registry validity
\ No newline at end of file
+- Check your domain registry validity
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
index 11fe9044b199b1c..d58062e1f6e2e72 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
@@ -14,16 +14,14 @@ products:
 
 Use the [Workers Analytics Engine](/analytics/analytics-engine/) to send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL.
 
-
 ## Account and zone analytics
 
 Use [Account and zone analytics](/analytics/account-and-zone-analytics/) to provide details about the requests and traffic related to your Cloudflare accounts and zones.
 
-
 ## Cloudflare Network Analytics
 
 Use [Cloudflare Network Analytics](/analytics/network-analytics/) to provide near real-time visibility into network and transport-layer traffic patterns and DDoS attacks.
 
 ## GraphQL Analytics API
 
-Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
\ No newline at end of file
+Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
index d594e17850fe651..7be8e912c96ed9a 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
@@ -16,26 +16,21 @@ import { DashButton } from "~/components";
 
 By default, Cloudflare [caches static content](/cache/concepts/default-cache-behavior/) such as images, CSS, and JavaScript. However, you can extend Cloudflare caching to work with HTML by creating custom [Cache Rules](/cache/how-to/cache-rules/).
 
-
 ### Cache more requests
 
-1. In  the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page. 
+1. In the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page.
 
-    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+   <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
 3. For When incoming requests match, enter either your entire website or a specific path on your application, based on the Hostname or URI Path. Refer to the [available fields](/cache/how-to/cache-rules/settings/#fields).
 4. For Cache eligibility, define how these requests should be cached and for how long. Refer to the available [cache eligibility settings](/cache/how-to/cache-rules/settings/#eligible-for-cache-settings).
 5. You can then monitor the effectiveness of your cache settings using [Cache Analytics](/cache/performance-review/cache-analytics/) and update your configuration according to our [Cache performance guide](/cache/performance-review/cache-performance/).
 
-
 ### Advanced cache optimizations
 
-
-
-* [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
-* [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
-
+- [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
+- [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
 
 ## Tiered Cache
 
@@ -45,7 +40,6 @@ It works by dividing Cloudflare's data centers into a hierarchy of lower-tiers a
 
 Refer to [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) to get started.
 
-
 ### Cache Reserve
 
 [Cache Reserve](/cache/advanced-configuration/cache-reserve/) is a large, persistent data store implemented on top of [R2](/r2/).
@@ -54,38 +48,32 @@ With a single click in the dashboard, your cacheable content will be written to
 
 This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
 
-
 ## Cloudflare Waiting Room
 
 [Cloudflare Waiting Room](/waiting-room/) allows you to route excess users of your website to a customized waiting room, helping preserve customer experience and protect origin servers from being overwhelmed with requests.
 
-
 ## Use Cloudflare IP addresses
 
 Take action to prevent attacks to your application during peak season by configuring your firewall to only accept traffic from Cloudflare IP addresses. By only allowing [Cloudflare IPs](https://www.cloudflare.com/ips), you can prevent attackers from bypassing Cloudflare and sending requests directly to your origin.
 
 Refer to [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) for more information.
 
-
 ## Monitor traffic
 
 You can use the Cloudflare dashboard to closely monitor the traffic on your domain and fine-tune your cache and security settings accordingly.
 
-
 ### Zone and Account analytics
 
 [Cloudflare zone analytics](/analytics/account-and-zone-analytics/zone-analytics/) gives you access to a wide range of metrics, collected at the website or domain level.
 
 [Cloudflare account analytics](/analytics/account-and-zone-analytics/account-analytics/) lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
-
 ### Security Analytics and Security Events
 
 [Security Analytics](/waf/analytics/security-analytics/) displays information about all incoming HTTP requests for your domain, including requests not handled by Cloudflare security products.
 
 You can also use the [Security Events](/waf/analytics/security-events/) to review mitigated requests and tailor your security configurations.
 
-
 ### Cache Analytics
 
-You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
\ No newline at end of file
+You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
index 63efb8a1e0f3aef..2655eccdda8256f 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
index 46f719837ac8da1..6434accda802398 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
@@ -14,17 +14,14 @@ products:
 
 Use [Logpush](/logs/logpush/) to push your request or event logs to your cloud service provider using Logpush, which can be configured via the Cloudflare dashboard or API.
 
-
 ## Instant Logs
 
 Use [Instant Logs](/logs/instant-logs/) to view HTTP request logs instantly in the Cloudflare dashboard or the CLI.
 
-
 ## Logs Engine
 
-Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.  
-
+Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.
 
 ## Log Explorer
 
-Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API. 
\ No newline at end of file
+Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
index 07a1c32748a4a4b..075b1e688bd6801 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
@@ -10,7 +10,6 @@ products:
   - ddos-protection
 ---
 
-
 [User Agent (UA) Blocking](/waf/tools/user-agent-blocking/) rules match against specific User-Agent request headers sent by the browser or application accessing your site. UA rules are applied against the entire domain, and after a rule is triggered, you can decide which action to take against the visitor.
 
 Actions:
diff --git a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
index 8a5b929f561880a..c0d4fe2c9a50ebe 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Review the list below for guidance on securing your account.
 
-<DirectoryListing folder="fundamentals/account/account-security" />
\ No newline at end of file
+<DirectoryListing folder="fundamentals/account/account-security" />
diff --git a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
index 9fb487a7190ccfd..8508360fa7d7ac7 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
@@ -14,13 +14,10 @@ products:
 
 IP Access Rules can be applied based on:
 
-
-
-* IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
-* IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
-* ASN
-* Country or the Tor network
-
+- IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
+- IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
+- ASN
+- Country or the Tor network
 
 :::note
 
@@ -34,4 +31,3 @@ Actions:
 - Non-Interactive Challenge: Visitors will be shown a non-interactive challenge before allowed access.
 - Interactive Challenge: Visitors will be shown an interactive challenge before allowed access.
 - Allowlist: Ensures that an IP address will never be blocked from accessing your site. This supersedes any Cloudflare security profile.
-
diff --git a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
index 1c28bd66975b7dd..2436739e7c61285 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
@@ -1,7 +1,7 @@
 ---
 title: What to do when under attack
 pcx_content_type: overview
-sidebar: 
+sidebar:
   order: 9
 description: Respond to active DDoS attacks.
 products:
@@ -16,14 +16,12 @@ If you are under attack and have this feature enabled during the attack, visitor
 
 Refer to [I'm Under Attack Mode](https://developers.cloudflare.com/fundamentals/reference/under-attack-mode/) for more information.
 
-
 ## Change Access Control List (ACL)
 
 An ACL refers to rules that are applied to port numbers or IP addresses that are available on a host permitting use of the service. When you only allow Cloudflare IPs, you eliminate threats attempting to attack your origin IP range.
 
 Refer to [Cloudflare IP Ranges](https://www.cloudflare.com/ips) for more information.
 
-
 ## Change Origin IPs and update Cloudflare DNS records
 
 If your origin is still being attacked, consider moving your Origin IPs and updating your Cloudflare DNS records.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/index.mdx b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
index cd4191d21fbf2c9..4e47eb5f69bf264 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/support/index.mdx b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
index 38e3bfb1f22fb97..289654ff24ecd81 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
\ No newline at end of file
+---
diff --git a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
index 1ae293e1c4a56e6..0ce3a91e3055cfd 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
@@ -10,15 +10,14 @@ products:
   - ddos-protection
 ---
 
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
-
-| Support type | Resource |
-| ------------ | -------- |
-| Self-serve questions | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals |
-| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team |
-| Non-critical production issues (reactive) | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
-| Critical issues such as attacks (reactive) | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)| 
+| Support type                                      | Resource                                                                                     |
+| ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| Self-serve questions                              | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals          |
+| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team                                                     |
+| Non-critical production issues (reactive)         | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
+| Critical issues such as attacks (reactive)        | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)       |
 
 :::note
 For security reasons, Cloudflare Support only assists individuals whose email addresses are validated against the list of registered account contacts. Review and update all contacts accordingly in your Cloudflare Dashboard. For more information, refer to [Manage members](/fundamentals/manage-members/).
diff --git a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
index 2865a6b3e04b8af..898e3bb0f7ac8ed 100644
--- a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
@@ -24,13 +24,13 @@ If your application is built on Cloudflare, then Cloudflare would act as the ori
 
 An example tech stack for an application built on Cloudflare would look like:
 
-* [Domain Registrar](/registrar/) to buy a new your domain.
-* [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
-* [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
-* [Storage resources](/workers/platform/storage-options/) to persist different types of data.
-* [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
-* [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
-* [AI](/use-cases/ai/) to run machine learning models.
+- [Domain Registrar](/registrar/) to buy a new your domain.
+- [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
+- [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
+- [Storage resources](/workers/platform/storage-options/) to persist different types of data.
+- [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
+- [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
+- [AI](/use-cases/ai/) to run machine learning models.
 
 And more depending on your use case.
 
@@ -42,11 +42,11 @@ When you add your application to Cloudflare, Cloudflare's global network of serv
 
 After you add your application to [Cloudflare](/fundamentals/concepts/how-cloudflare-works/), you can:
 
-* Use Workers to augment the application by deploying code.
-* Add storage resources available on the Developer Platform.
-* Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
-* Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
-* Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
+- Use Workers to augment the application by deploying code.
+- Add storage resources available on the Developer Platform.
+- Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
+- Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
+- Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
 
 And more depending on your use case.
 
@@ -54,8 +54,8 @@ And more depending on your use case.
 
 By reading this page, you have:
 
-* Learned the scale of Cloudflare's global network.
-* Explored the product offering to know what Cloudflare can offer for users like you.
-* Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
+- Learned the scale of Cloudflare's global network.
+- Explored the product offering to know what Cloudflare can offer for users like you.
+- Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
 
 In the next section, you will be introduced to the fundamentals of serverless computing, the concept behind Cloudflare Workers.
diff --git a/src/content/docs/learning-paths/workers/concepts/index.mdx b/src/content/docs/learning-paths/workers/concepts/index.mdx
index e293a2f1d9d87d7..9837915441175e0 100644
--- a/src/content/docs/learning-paths/workers/concepts/index.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/index.mdx
@@ -16,6 +16,6 @@ Learn the concepts behind what makes Cloudflare Workers reliable, scalable and f
 
 By the end of this module, you will learn:
 
-* What Cloudflare is.
-* The difference between serverless computing and cloud computing paradigms.
-* How Workers works.
+- What Cloudflare is.
+- The difference between serverless computing and cloud computing paradigms.
+- How Workers works.
diff --git a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
index 1fd5f921d05c1ed..c9f1788b07d3213 100644
--- a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
@@ -40,8 +40,8 @@ Developers and organizations using serverless computing are billed on a usage mo
 
 By reading this page, you have:
 
-* Been introduced to the serverless computing concept that is behind Cloudflare Workers.
-* Reviewed the differences between legacy on-premise and cloud computing infrastructure.
-* Analyzed the key differences between the cloud computing and serverless computing paradigms.
+- Been introduced to the serverless computing concept that is behind Cloudflare Workers.
+- Reviewed the differences between legacy on-premise and cloud computing infrastructure.
+- Analyzed the key differences between the cloud computing and serverless computing paradigms.
 
 In the next section, you will learn about what makes Workers, a serverless computing platform that is part of the larger Cloudflare Developer Platform, unique in its architecture from other serverless computing providers.
diff --git a/src/content/docs/learning-paths/workers/devplat/index.mdx b/src/content/docs/learning-paths/workers/devplat/index.mdx
index f792c7ba4cbfda3..365fd4fa0f8d551 100644
--- a/src/content/docs/learning-paths/workers/devplat/index.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/index.mdx
@@ -16,5 +16,5 @@ The Cloudflare Developer Platform allows you to build full-stack applications wi
 
 By the end of this module, you will learn:
 
-* Cloudflare Developer Platform's product offering.
-* What storage options are available to your Worker.
+- Cloudflare Developer Platform's product offering.
+- What storage options are available to your Worker.
diff --git a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
index 20e6536f1ef0349..5a516cca6e30fc3 100644
--- a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { Render, YouTube } from "~/components"
+import { Render, YouTube } from "~/components";
 
 The [Cloudflare Developer Platform](https://www.cloudflare.com/developer-platform/products/) offers various services to empower developers to build full-stack applications, including: [compute](https://www.cloudflare.com/developer-platform/products/#compute), [storage](https://www.cloudflare.com/developer-platform/products/#storage), [web development, image optimization, video streaming](https://www.cloudflare.com/developer-platform/products/#webdev) and [AI](https://ai.cloudflare.com/).
 
diff --git a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
index 4783f290410f89f..491c0bb0dc6773c 100644
--- a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
@@ -18,8 +18,8 @@ You can build and develop your Worker on the Cloudflare dashboard, without needi
 
 The Cloudflare Developer Platform ecosystem has two command-line interfaces (CLI):
 
-* C3: To create new projects.
-* Wrangler: To build and deploy your projects.
+- C3: To create new projects.
+- Wrangler: To build and deploy your projects.
 
 ## C3
 
@@ -45,7 +45,7 @@ Cloudflare recommends choosing and using one [source of truth](/workers/wrangler
 
 By reading this page, you have learned:
 
-* How to use C3 to create new Workers and Pages projects.
-* How to use Wrangler to develop, configure, and delete your projects.
+- How to use C3 to create new Workers and Pages projects.
+- How to use Wrangler to develop, configure, and delete your projects.
 
 In the next section, you will learn more about the Cloudflare dashboard before moving on to deploy your first Worker.
diff --git a/src/content/docs/learning-paths/workers/get-started/first-application.mdx b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
index 422ae8875a66d14..5797be4e53286d6 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-application.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
@@ -9,6 +9,7 @@ description: Build an AI application with Hono.
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 ## Build an AI application with Hono and Workers
@@ -17,21 +18,21 @@ If you have already created your first Worker and want to learn what more you ca
 
 In this course, you will:
 
-* Deploy your first Worker.
-* Develop your application locally.
-* Add the Hono framework to your project.
-* Integrate Workers AI into your project.
+- Deploy your first Worker.
+- Develop your application locally.
+- Add the Hono framework to your project.
+- Integrate Workers AI into your project.
 
 <div style="position: relative; padding-top: 56.25%;">
-    <iframe
-        src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
-        style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-        allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-        allowfullscreen="true">
-    </iframe>
+	<iframe
+		src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
 </div>
 
-<br/>
+<br />
 
 Find [the video on YouTube](https://youtu.be/H7Qe96fqg1M?si=GVkdGLrmb1faiHma) and explore other Cloudflare Workers tutorials.
 
diff --git a/src/content/docs/learning-paths/workers/get-started/index.mdx b/src/content/docs/learning-paths/workers/get-started/index.mdx
index 39b04e54f6794eb..a25e920d7e95452 100644
--- a/src/content/docs/learning-paths/workers/get-started/index.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/index.mdx
@@ -14,6 +14,6 @@ Deploy your first Worker to the Cloudflare global network by
 
 By the end of this module, you will learn:
 
-* The difference between C3 (`create-cloudflare` CLI) and Wrangler.
-* How to use the Cloudflare dashboard to manage your Workers.
-* How to create and deploy your first Worker.
+- The difference between C3 (`create-cloudflare` CLI) and Wrangler.
+- How to use the Cloudflare dashboard to manage your Workers.
+- How to create and deploy your first Worker.
diff --git a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
index cc182b7d7c81178..a01215316a0f040 100644
--- a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
+++ b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
@@ -7,7 +7,6 @@ products:
 head:
   - tag: title
     content: Load balance additional DNS records
-
 ---
 
 In addition to load balancing between DNS records used for IP resolution — `A`, `AAAA`, and `CNAME` records — Enterprise customers can also load balance between **MX** and **SRV** records.
@@ -17,7 +16,7 @@ In addition to load balancing between DNS records used for IP resolution — `A`
 To load balance between multiple mail servers:
 
 1. Make sure you have the [required DNS records](/dns/manage-dns-records/how-to/email-records/#send-and-receive-email) for your mail servers.
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *SMTP*.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _SMTP_.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your mail servers and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. Since it will forward SMTP traffic, the load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
 
@@ -26,6 +25,6 @@ To load balance between multiple mail servers:
 To load balance between different **SRV** records, which contain significantly more information than many other DNS records:
 
 1. [Create your SRV records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records).
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *UDP-ICMP* or *TCP*.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _UDP-ICMP_ or _TCP_.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your various SRV records and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. This load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
diff --git a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
index 26703586383732d..826228781b9546b 100644
--- a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
+++ b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Route traffic through a Cloudflare Tunnel
-
 ---
 
 Cloudflare Tunnel (formerly Argo Tunnel) establishes a secure outbound connection which runs in your infrastructure to connect the applications and machines to Cloudflare.
diff --git a/src/content/docs/load-balancing/additional-options/index.mdx b/src/content/docs/load-balancing/additional-options/index.mdx
index fa8021c02caae66..67bfe4b67c3ffd3 100644
--- a/src/content/docs/load-balancing/additional-options/index.mdx
+++ b/src/content/docs/load-balancing/additional-options/index.mdx
@@ -6,22 +6,21 @@ products:
 title: Additional configuration
 sidebar:
   order: 49
-
 ---
 
 Beyond [creating a simple load balancer](/load-balancing/load-balancers/create-load-balancer/), you may want to further customize how your load balancer routes traffic or integrate your load balancer with other Cloudflare products.
 
 ## Customize load balancer behavior
 
-* Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
-* Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
-* Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
+- Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
+- Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
+- Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
 
 ## Integrate with other Cloudflare products
 
-* Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
-* Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
+- Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
+- Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
 
 ## Integrate with 3rd parties
 
-* Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
+- Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
index ce90921b4f41919..e0591ff2cfa42ea 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Balancing with the China Network
 sidebar:
   order: 15
-
 ---
 
 ## Prerequisites
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
index 3fa85bff4993517..ef52ac1aafb7236 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
@@ -9,16 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Load Balancing expressions
-
 ---
 
 [Load Balancing rules](/load-balancing/additional-options/load-balancing-rules/) use two kinds of expressions:
 
-* [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (*equals* or *less than*, for example).
+- [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (_equals_ or _less than_, for example).
 
-* [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (*and*, *or*, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
+- [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (_and_, _or_, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
 
-***
+---
 
 ## Simple expressions
 
@@ -44,11 +43,11 @@ In general, simple expressions use this pattern:
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
-***
+---
 
 ## Compound expressions
 
-A compound expression uses a **logical operator** (*and*, *or*, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
+A compound expression uses a **logical operator** (_and_, _or_, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
 
 The example expression below returns true when both the HTTP request URI path contains `/content` and the query string contains `webserver`:
 
@@ -67,7 +66,7 @@ A compound expression can be an operand of a logical operator. This allows multi
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
-***
+---
 
 ## Working with expressions
 
diff --git a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
index 135607380a8e453..ec4cd87db9d1d86 100644
--- a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
+++ b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
@@ -6,19 +6,16 @@ products:
 title: Override HTTP Host headers
 sidebar:
   order: 16
-
 ---
 
 When your application needs specialized routing (`CNAME` setup or custom hosts like Heroku), you can customize the `Host` header used in health monitors on a per-endpoint or per-monitor level.
 
 :::caution[Important]
 
-
 If you set a header override on an individual endpoint, it will take precedence over a header override set on a monitor.
 
 Also, if you configure an [Origin Rule](/rules/origin-rules/) that overrides the hostname and set up a header override in your Load Balancer configuration, the Load Balancer configuration will take precedence over the Origin Rule hostname override.
 
-
 :::
 
 ## Per endpoint Host header override
@@ -27,13 +24,13 @@ To balance traffic across multiple hosts, add `Host` headers to individual endpo
 
 For example, you might have a pool with endpoints hosted in multiple AppEngine projects or Amazon S3 buckets. You also might want to set up specific failover endpoints within a pool.
 
-Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic *without* a `Host` header override.
+Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic _without_ a `Host` header override.
 
 If you need an endpoint `Host` header override, add it when [creating](/load-balancing/pools/create-pool/) or editing a pool. For security reasons, this header must meet one of the following criteria:
 
-* Is a subdomain of a zone associated with this account
-* Matches the endpoint address
-* Publicly resolves to the endpoint address
+- Is a subdomain of a zone associated with this account
+- Matches the endpoint address
+- Publicly resolves to the endpoint address
 
 ## Host header prioritization
 
@@ -41,19 +38,16 @@ If you set a header override on an individual endpoint, it will take precedence
 
 For example, you might have a load balancer for `www.example.com` with the following setup:
 
-* Pools:
-
-  * Pool 1:
-
-    * Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
-    * Endpoint 2
-
-  * Pool 2:
+- Pools:
+  - Pool 1:
+    - Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
+    - Endpoint 2
 
-    * Endpoint 3
-    * Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
+  - Pool 2:
+    - Endpoint 3
+    - Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
 
-* Monitor (`Host` header set to `www.example.com`)
+- Monitor (`Host` header set to `www.example.com`)
 
 In this scenario, health monitor requests for **Endpoint 1** would use `lb-app-a.example.com`, health monitor requests for **Endpoint 4** would use `lb-app-b.example.com`, and all other health monitor requests would default to `www.example.com`. For more information on updating your custom host configuration to be compatible with Cloudflare, see [Configure Cloudflare and Heroku over HTTPS](/support/third-party-software/others/configure-cloudflare-and-heroku-over-https/).
 
diff --git a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
index 800fefee9fab77d..f9d25700c2ef3e6 100644
--- a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
+++ b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
@@ -6,7 +6,6 @@ products:
 title: Integrate with PagerDuty
 sidebar:
   order: 41
-
 ---
 
 To integrate Cloudflare health monitor notifications with PagerDuty, follow the steps outlined in PagerDuty’s [Email Integration Guide](https://www.pagerduty.com/docs/guides/email-integration-guide/). If you do not have a PagerDuty account, you will first need to set that up.
diff --git a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
index 44d8e5917088c19..934c8b9eaad2618 100644
--- a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
+++ b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
@@ -18,10 +18,8 @@ To direct traffic away from your endpoint immediately, [adjust settings on the p
 
 :::note
 
-
 If you want to divert traffic from an endpoint to prevent it from becoming unhealthy, use [Load Shedding](/load-balancing/additional-options/load-shedding/) instead.
 
-
 :::
 
 ## Before you begin
@@ -34,10 +32,8 @@ If a pool falls below its **Health Threshold**, it will be considered **Unhealth
 
 :::note
 
-
 Endpoint drain is only available for [proxied load balancers (orange-clouded)](/load-balancing/understand-basics/proxy-modes/).
 
-
 :::
 
 With [session-based load balancing](/load-balancing/understand-basics/session-affinity/), it is important to direct all requests from a particular end user to a specific endpoint. Otherwise, information about the user session — such as items in their shopping cart — may be lost and lead to negative business outcomes.
@@ -63,10 +59,10 @@ To remove an endpoint from rotation while still preserving session continuity, s
 To direct traffic away from an endpoint immediately:
 
 1. Do one of the following actions:
-   * On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
-   * On the pool, disable the endpoint.
-   * On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
+   - On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
+   - On the pool, disable the endpoint.
+   - On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
 2. Monitor [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) to make sure no requests are reaching the pool.
-   * If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
+   - If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
 3. Perform your required maintenance or upgrades.
 4. Undo the changes you made in **Step 1**.
diff --git a/src/content/docs/load-balancing/api-reference.mdx b/src/content/docs/load-balancing/api-reference.mdx
index beaae8039b92f86..5fcef7600b948c2 100644
--- a/src/content/docs/load-balancing/api-reference.mdx
+++ b/src/content/docs/load-balancing/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/load_balancers/methods/get/
 sidebar:
   order: 152
-
 ---
diff --git a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
index 2d257351a66f0cf..290ae83ee3bfbe9 100644
--- a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
+++ b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
@@ -9,10 +9,9 @@ head:
   - tag: title
     content: Enable Load Balancing
 description: Learn how to enable load balancing.
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Load balancing is an add-on for your account, meaning your account needs a [billing profile](/billing/get-started/create-billing-profile/).
 
diff --git a/src/content/docs/load-balancing/get-started/index.mdx b/src/content/docs/load-balancing/get-started/index.mdx
index 718f24899007689..42931ed740f8d8a 100644
--- a/src/content/docs/load-balancing/get-started/index.mdx
+++ b/src/content/docs/load-balancing/get-started/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Get started
 sidebar:
   order: 1
-
 ---
 
 Get started with load balancing in one of two ways:
 
-* [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
-* [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
+- [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
+- [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
diff --git a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
index 47be390136f8260..9e97aeac3cc0923 100644
--- a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
+++ b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
@@ -6,7 +6,6 @@ products:
 title: Common configurations
 sidebar:
   order: 6
-
 ---
 
 Consider the following sections to understand how to achieve some commonly used load balancer configurations.
@@ -39,13 +38,11 @@ This setup speeds up overall requests, but is more vulnerable to planned or unpl
 
 To set up a load balancer with **active-active failover**, either:
 
-* Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
-* Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
+- Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
+- Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
 
 :::note
 
-
 For more background reading on server failover and common configurations, refer to [our Learning Center](https://www.cloudflare.com/learning/performance/what-is-server-failover/).
 
-
 :::
diff --git a/src/content/docs/load-balancing/monitors/index.mdx b/src/content/docs/load-balancing/monitors/index.mdx
index 4f3257567e10daf..1e9332fef2a2c18 100644
--- a/src/content/docs/load-balancing/monitors/index.mdx
+++ b/src/content/docs/load-balancing/monitors/index.mdx
@@ -86,6 +86,6 @@ The following table summarizes the different types of monitors available in Clou
 | ------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | HTTP/HTTPS   | Public and private | Used for HTTP and HTTPS endpoints with specific protocol attributes.                                                                                                                       | The probe is configured with settings and success criteria such as Method, Simulate Zone, Follow Redirects, Request Headers, and Response Body. The probe then evaluates the configured success criteria using the HTTP protocol. Throughout the configured timeout period, the TCP connection is kept active using [keep-alives](/fundamentals/reference/tcp-connections/#tcp-connections-and-keep-alives), even if no response is received. | Success is based on meeting the configured HTTP success criteria. No response within the configured timeout and retries is considered unhealthy.   |
 | TCP          | Public and private | Checks TCP connectivity by attempting to open a connection to the endpoint.                                                                                                                | The monitor sends a TCP SYN message to the specified port. A successful health check requires receiving a SYN/ACK message to establish the connection. The connection is closed by sending a FIN or RST packet, or by receiving a FIN packet from the endpoint.                                                                                                                                                                               | Failure to establish a TCP connection within the configured timeout and retries is considered unhealthy.                                           |
-| ICMP Ping    | Public and Tunnel | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
-| UDP-ICMP     | Public and Tunnel | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
+| ICMP Ping    | Public and Tunnel  | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
+| UDP-ICMP     | Public and Tunnel  | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
 | SMTP         | Public             | Verifies SMTP availability at the application layer.                                                                                                                                       | The monitor establishes a TCP connection and sends an SMTP HELO command. It expects a reply with code 250. The monitor then sends an SMTP QUIT command, expecting a reply with code 221. At the end of each interval, the TCP connection is closed by sending a TCP FIN packet.                                                                                                                                                               | The endpoint must respond with correct SMTP codes (250 for HELO, 221 for QUIT) within the configured timeout and retries to be considered healthy. |
diff --git a/src/content/docs/load-balancing/monitors/monitor-groups.mdx b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
index 50904c9a7de3215..c9523c593355ecb 100644
--- a/src/content/docs/load-balancing/monitors/monitor-groups.mdx
+++ b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
@@ -6,7 +6,6 @@ products:
 title: Monitor Groups
 sidebar:
   order: 48
-
 ---
 
 Group multiple health monitors together to create sophisticated health checks for your applications, ensuring more intelligent and resilient traffic steering.
diff --git a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
index db0595b89b0b6ef..3d3b8c26fad9827 100644
--- a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
+++ b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
@@ -33,8 +33,10 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to
 1. Go to **Load Balancing** at the account level and select **Create a Load Balancer**.
 2. Select **Private Load Balancer**.
 3. On the next step you can choose to associate this load balancer with either:
- - A CGNAT IP from the Cloudflare range or
- - A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
+
+- A CGNAT IP from the Cloudflare range or
+- A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
+
 4. Add a descriptive name to identify your Load Balancer.
 5. Proceed through the setup.
 
diff --git a/src/content/docs/load-balancing/reference-architecture-external-link.mdx b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
index 09dbce736aec377..0183c3d39e2e8f3 100644
--- a/src/content/docs/load-balancing/reference-architecture-external-link.mdx
+++ b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
@@ -7,5 +7,4 @@ title: Reference architecture
 external_link: /reference-architecture/architectures/load-balancing/
 sidebar:
   order: 150
-
 ---
diff --git a/src/content/docs/load-balancing/reference/index.mdx b/src/content/docs/load-balancing/reference/index.mdx
index ec8770d1780404a..e6f4d8d2d6c3b20 100644
--- a/src/content/docs/load-balancing/reference/index.mdx
+++ b/src/content/docs/load-balancing/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 50
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 See the following pages for more information about Cloudflare Load Balancing:
 
diff --git a/src/content/docs/load-balancing/reference/limitations.mdx b/src/content/docs/load-balancing/reference/limitations.mdx
index 5bde030458bc22e..c46c0f6c8a12462 100644
--- a/src/content/docs/load-balancing/reference/limitations.mdx
+++ b/src/content/docs/load-balancing/reference/limitations.mdx
@@ -6,13 +6,12 @@ products:
 title: Limitations
 sidebar:
   order: 48
-
 ---
 
- Name | Non-Enterprise | Enterprise |
- --- | --- | --- |
- Load balancers | 20 | custom |
- Monitor intervals | 15s (min), 3600s (max) | 10s (min), 3600s (max) |
- Monitors | 1.5x the number of pools | 1.5x the number of pools |
- Endpoints | 20 | custom |
- Pools | 20 | custom |
+| Name              | Non-Enterprise           | Enterprise               |
+| ----------------- | ------------------------ | ------------------------ |
+| Load balancers    | 20                       | custom                   |
+| Monitor intervals | 15s (min), 3600s (max)   | 10s (min), 3600s (max)   |
+| Monitors          | 1.5x the number of pools | 1.5x the number of pools |
+| Endpoints         | 20                       | custom                   |
+| Pools             | 20                       | custom                   |
diff --git a/src/content/docs/load-balancing/reference/migration-guides/index.mdx b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
index aecc03630e37bc8..f1e1ae6e2a682da 100644
--- a/src/content/docs/load-balancing/reference/migration-guides/index.mdx
+++ b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
index ede4a1cdcb502e9..9f0e7e87097a25c 100644
--- a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
@@ -6,7 +6,6 @@ products:
 title: Common error codes
 sidebar:
   order: 51
-
 ---
 
 The Cloudflare Load Balancing API adds global health to each pool and endpoint. It also gives you a view into what our network sees at a wider level. Cloudflare uses a quorum system to determine pool and endpoint health status. The quorum is taken from PoPs responsible for running health monitor requests in a region, and the majority result is used.
@@ -23,7 +22,7 @@ If a health monitor request fails, the breakdown will include the reason.
 
 Common troubleshooting causes and solutions are listed below.
 
-***
+---
 
 ## TCP connection failed
 
@@ -35,7 +34,7 @@ Our health monitor requests failed to establish a TCP connection to your endpoin
 
 This typically occurs when there is a network failure between Cloudflare and your endpoint, and/or a firewall refused to allow our connection. Ensure your network and firewall configurations are not interfering with load balancing traffic.
 
-***
+---
 
 ## HTTP timeout occurred
 
@@ -47,7 +46,7 @@ The endpoint failed to return an HTTP response within the timeout configured. Th
 
 We recommend increasing the HTTP response timeout to allow the endpoint to respond.
 
-***
+---
 
 ## Response code mismatch error
 
@@ -67,7 +66,7 @@ You may also see this issue if you have a monitor configured to use HTTP connect
 
 Either change your Cloudflare monitor configuration to use HTTPS, or set the value of `follow_redirect` to `true` so that we can resolve the correct status code.
 
-***
+---
 
 ## Response body mismatch error
 
@@ -75,13 +74,13 @@ Either change your Cloudflare monitor configuration to use HTTPS, or set the val
 
 The response body returns from your endpoint and does not include the (case-insensitive) value of `expected_body` configured in your monitor.
 
-Note that we only read the first 10 KB of the response. If you return a larger response, and the expected\_body is not in the first 10 KB, the health monitor request will fail.
+Note that we only read the first 10 KB of the response. If you return a larger response, and the expected_body is not in the first 10 KB, the health monitor request will fail.
 
 ### Solution
 
-Ensure the expected\_body is in the first 10 KB of the response body.
+Ensure the expected_body is in the first 10 KB of the response body.
 
-***
+---
 
 ## TLS untrusted certificate error
 
@@ -93,7 +92,7 @@ The certificate is not trusted by a public Certificate Authority (CA).
 
 If you're using a self-signed certificate, we recommend either using a publicly trusted certificate or setting the `allow_insecure` property on your monitor to `true`.
 
-***
+---
 
 ## TLS name mismatch error
 
@@ -105,7 +104,7 @@ Our health monitor (client) was not able to match a name on the server certifica
 
 Use the List Monitors command to confirm that the `header` value set in the Cloudflare monitor is correct and the Update Monitors command to make any necessary changes.
 
-***
+---
 
 ## TLS protocol error
 
@@ -117,7 +116,7 @@ This error can occur if you’re using an older version of TLS or your endpoint
 
 Ensure that your endpoint supports TLS 1.0 or greater and is configured for HTTPS.
 
-***
+---
 
 ## TLS unrecognized name error
 
@@ -129,7 +128,7 @@ The server did not recognize the name provided by the client. When a host header
 
 Set the host header in your monitor object.
 
-***
+---
 
 ## No route to host error
 
@@ -141,7 +140,7 @@ The IP address cannot be reached from our network. Common causes are ISP or host
 
 Make sure IP is accurate, and if it is check if there is an ISP or hosting provider network issue.
 
-***
+---
 
 ## Exceeded quota error
 
@@ -155,10 +154,10 @@ If you're using the **Cloudflare API**, you will receive an error message.
 
 ### Solution
 
-* Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
-* Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
+- Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
+- Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
 
-***
+---
 
 ## TCP Timeout
 
@@ -170,7 +169,7 @@ Data transmission was not acknowledged and retransmit of data did not succeed.
 
 Confirm whether the SYN-ACK for the handshake takes place at your endpoint and [contact Cloudflare Support](/support/contacting-cloudflare-support/).
 
-***
+---
 
 ## TLS Handshake Failure
 
@@ -182,7 +181,7 @@ Indicates that the browser's connection to the web server is not secure.
 
 Change wifi networks, connect to a wired network, or verify the network connection is stable.
 
-***
+---
 
 ## Network Unreachable
 
@@ -194,7 +193,7 @@ Cloudflare cannot connect to the endpoint due to network unavailability. This is
 
 Check either the IP entered for the endpoint in Cloudflare's Load Balancer configuration or the IP returned via DNS for the endpoint hostname.
 
-***
+---
 
 ## HTTP Invalid Response
 
@@ -206,7 +205,7 @@ Usually caused by an HTTP 502 error or bad gateway.
 
 Ensure the endpoint responds to requests and that no applications have crashed or are under high load.
 
-***
+---
 
 ## DNS Unknown Host
 
@@ -218,7 +217,7 @@ The endpoint hostname does not exist.
 
 Confirm the endpoint resolves to an IP address.
 
-***
+---
 
 ## Connection Reset by Peer
 
@@ -230,7 +229,7 @@ A network error occurred while the client received data from the endpoint.
 
 Confirm whether the endpoint is experiencing a high amount of traffic or an error.
 
-***
+---
 
 ## Monitor Config Error
 
@@ -242,7 +241,7 @@ There was a configuration error in the monitor and no checks are run against the
 
 Review your monitor configuration to ensure it matches an expected request to your endpoint.
 
-***
+---
 
 ## DNS Internal
 
@@ -254,7 +253,7 @@ The endpoint's hostname resolves to an internal or orange-clouded IP address. No
 
 Cloudflare does not allow use of an endpoint hostname that is proxied by Cloudflare.
 
-***
+---
 
 ## Load Balancing Not Enabled
 
@@ -266,7 +265,7 @@ Load Balancing is not enabled for your account or zone.
 
 For Enterprise customers, reach out to your Cloudflare Account Team. Free, Pro, and Business customers should [Enable Load Balancing](/load-balancing/get-started/enable-load-balancing/).
 
-***
+---
 
 ## Validation failed error
 
@@ -278,7 +277,7 @@ You will receive an error if you try to set the host header value while configur
 
 Cloudflare now restricts configured [endpoint host headers](/load-balancing/additional-options/override-http-host-headers/) to fully qualified domain names (FQDNs) that are immediate subdomains of a zone associated with the account. For example, this host header would be the same zone as the load balancer itself, but pools may be used across multiple Load balancers.
 
-***
+---
 
 ## Object referenced by other objects
 
@@ -290,7 +289,7 @@ You will receive this error when you attempt to delete a pool that is referenced
 
 Remove the pool from the load balancer's geo steering configuration. If your load balancer no longer uses geo steering, you will need to [re-enable geo steering](/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering/) and then remove the pool.
 
-***
+---
 
 ## Other Failure
 
diff --git a/src/content/docs/load-balancing/troubleshooting/index.mdx b/src/content/docs/load-balancing/troubleshooting/index.mdx
index ab1582dd07df552..2a9154394f0dda7 100644
--- a/src/content/docs/load-balancing/troubleshooting/index.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 151
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more guidance related to common issues with load balancers, refer to the following resources:
 
diff --git a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
index f9b35fca372872e..49722335e1400f4 100644
--- a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
@@ -4,7 +4,6 @@ description: Answers to common Load Balancing questions.
 products:
   - load-balancing
 title: FAQs
-
 ---
 
 ## Overview
@@ -17,7 +16,7 @@ Are you trying to turn on Load Balancing? [Enable Load
 Balancing](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing).
 :::
 
-***
+---
 
 ## Why is my origin receiving so many health monitor requests?
 
@@ -35,7 +34,7 @@ To reduce traffic, reduce the number of selected regions or choose an option bes
 
 If you have a low interval for your health monitor requests, you may increase the traffic sent to your endpoints.
 
-***
+---
 
 ## Why is my endpoint or pool considered unhealthy?
 
@@ -43,15 +42,15 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 If you know that your endpoint is healthy but load balancing is reporting it as unhealthy, check the following settings on the [monitor](/load-balancing/monitors):
 
-* Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
-* Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
-* If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
-* If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
-* Try increasing the **Timeout** value.
-* Review the **Host Header** for the health monitor.
-* If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
+- Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
+- Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
+- If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
+- If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
+- Try increasing the **Timeout** value.
+- Review the **Host Header** for the health monitor.
+- If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
 
-***
+---
 
 ## Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?
 
@@ -59,7 +58,7 @@ You occasionally might see traffic routed away from a pool if a health monitor r
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
-***
+---
 
 ## What happens when a pool or endpoint becomes unhealthy?
 
@@ -77,7 +76,7 @@ To avoid these scenarios:
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
-***
+---
 
 ## What is the difference between Load Balancing and Health Checks?
 
@@ -85,7 +84,7 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 [Cloudflare Health Checks](/health-checks/) are identical to monitors within a load balancer, but only meant for probing server health (and not distributing traffic).
 
-***
+---
 
 ## Why do I see different numbers of requests in Load Balancing Analytics?
 
@@ -93,16 +92,16 @@ You may see different numbers of requests when reviewing [Load Balancing Analyti
 
 Load balancing **requests** are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds. This built-in caching is often the cause of an discrepancies.
 
-***
+---
 
 ## I'm seeing a specific error code for my load balancer or monitor.
 
 For a list of specific error codes and next steps, refer to [Load Balancing Troubleshooting](/load-balancing/troubleshooting).
 
-***
+---
 
 ## Related resources
 
-* [Endpoint and pool health](/load-balancing/understand-basics/health-details)
-* [Monitors](/load-balancing/monitors)
-* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
+- [Endpoint and pool health](/load-balancing/understand-basics/health-details)
+- [Monitors](/load-balancing/monitors)
+- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
diff --git a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
index 5932d2fa80bf195..0d58152b129b64d 100644
--- a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
+++ b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
@@ -6,10 +6,9 @@ products:
 title: Adaptive routing
 sidebar:
   order: 18
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Adaptive routing controls features that modify the routing of requests to pools and endpoints in response to dynamic conditions, such as during the interval between active health monitoring requests. <Render file="zero-downtime-failover-retry-on-error" product="fundamentals" />
 
diff --git a/src/content/docs/load-balancing/understand-basics/index.mdx b/src/content/docs/load-balancing/understand-basics/index.mdx
index c85c1403d1845cf..792addac1391985 100644
--- a/src/content/docs/load-balancing/understand-basics/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review the following topics to learn more about the basic concepts and components involved in Cloudflare Load Balancing.
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
index fdba031ab13f323..923d4f04f8cf0f3 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
@@ -6,7 +6,6 @@ products:
 title: Traffic steering
 sidebar:
   order: 4
-
 ---
 
 When requests come to your load balancer, it distributes them across your pools and endpoints according to three factors:
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
index 0c4c24f3ea88b14..4cdb38526cfe80e 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Hash steering
-
 ---
 
 **Hash steering** guides Cloudflare to send requests to endpoints based on a combination of [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) and previous requests from that IP address. Ensures requests from the same IP address will hit the same endpoint, but actual traffic distribution may differ from endpoint weights.
@@ -23,6 +22,3 @@ When a request originates from a browser, it lacks an `x-forwarded-for` header,
 ### Workaround
 
 To ensure Hash Steering works correctly when using a Worker in front of a Load Balancer, manually set the `x-forwarded-for` header in the Worker to the client's original IP address. By manually setting `x-forwarded-for` to `CF-Connecting-IP`, Hash Steering will function as expected, ensuring traffic consistency for end users.
-
-
-
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
index c51194139beb164..02a10b15022975c 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Endpoint-level steering
-
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to endpoints that currently have the lowest number of outstanding requests.
@@ -22,9 +21,9 @@ Least Outstanding Requests steering is best to use if your endpoints are easily
 
 ```json title="Pools"
 {
-  "origin_steering": {
-    "policy": "least_outstanding_requests"
-  }
+	"origin_steering": {
+		"policy": "least_outstanding_requests"
+	}
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
index 80045c618e6408a..537f0a763c9de2a 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Random steering
-
 ---
 
 **Random steering** sends requests to endpoints purely based on [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights). Distributes traffic more accurately, but may cause requests from the same IP to hit different endpoints.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
index 666b471d0af1334..f64ceb698d2ba17 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Dynamic steering
-
 ---
 
 **Dynamic steering** uses health monitor data to identify the fastest pool for a given Cloudflare Region or data center.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
index 4ad16dc07656f19..944941d3224b8ce 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
@@ -20,6 +20,7 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components";
 ## EDNS Client Subnet (ECS) support
 
 <GlossaryTooltip term="EDNS Client Subnet (ECS)"> EDNS Client Subnet (ECS) </GlossaryTooltip> support provides customers with more control over location-based steering during
+
 gray-clouded DNS resolutions and can be used for proximity or geo (country) steering.
 
 Customers can configure their load balancer using the `location_strategy` parameter, which includes the properties `prefer_ecs` and `mode`.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
index a52ce97da3eb882..b6cd01080f74721 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Steering policies
-
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to pools that currently have the lowest number of outstanding requests.
@@ -22,7 +21,7 @@ Least Outstanding Requests steering is best to use if your pools are easily over
 
 ```json title="Load Balancers"
 {
-  "steering_policy": "least_outstanding_requests"
+	"steering_policy": "least_outstanding_requests"
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
index 2b5fbd7114d502e..b5922711d2d91b3 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Proximity steering
-
 ---
 
 **Proximity steering** routes visitors or internal services to the closest physical data center.
@@ -18,21 +17,19 @@ To use proximity steering on a load balancer, you first need to add GPS coordina
 
 ## When to add proximity steering
 
-* For new pools, add GPS coordinates when you create a pool.
-* For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
+- For new pools, add GPS coordinates when you create a pool.
+- For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
 
 ## How to add proximity steering
 
 To add coordinates when creating or editing a pool:
 
-1. Click the *Configure coordinates for Proximity Steering* dropdown.
+1. Click the _Configure coordinates for Proximity Steering_ dropdown.
 2. Enter the latitude and longitude or drag a marker on the map.
 3. Select **Save**.
 
 :::caution[Warning:]
 
-
 For accurate proximity steering, add GPS coordinates to all pools within the same load balancer.
 
-
 :::
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
index 22d271801178c9b..4cb1a555bf452a2 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Standard traffic steering policies
-
 ---
 
 **Standard steering** policies include **Off - Failover** and **Random**.
diff --git a/src/content/docs/log-explorer/api.mdx b/src/content/docs/log-explorer/api.mdx
index 305c470002dd3d8..6bdcc752a5d4156 100644
--- a/src/content/docs/log-explorer/api.mdx
+++ b/src/content/docs/log-explorer/api.mdx
@@ -8,7 +8,7 @@ products:
   - log-explorer
 ---
 
-Configuration and Log searches are also available via a public API. 
+Configuration and Log searches are also available via a public API.
 
 ## Authentication
 
@@ -18,7 +18,7 @@ For detailed information on permissions required for each Log Explorer feature,
 
 ## Query data
 
-Log Explorer includes a SQL API for submitting queries. 
+Log Explorer includes a SQL API for submitting queries.
 
 For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
 
@@ -77,4 +77,4 @@ This command returns the following request details:
 	"errors": [],
 	"messages": []
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/log-explorer/changelog.mdx b/src/content/docs/log-explorer/changelog.mdx
index 2f97c532c5ac0e6..707f755e2c52edd 100644
--- a/src/content/docs/log-explorer/changelog.mdx
+++ b/src/content/docs/log-explorer/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="log-explorer" />
\ No newline at end of file
+<ProductChangelog product="log-explorer" />
diff --git a/src/content/docs/log-explorer/example-queries.mdx b/src/content/docs/log-explorer/example-queries.mdx
index 3d9b6d9cb490e20..265a16759a71279 100644
--- a/src/content/docs/log-explorer/example-queries.mdx
+++ b/src/content/docs/log-explorer/example-queries.mdx
@@ -131,5 +131,5 @@ FROM http_requests
 WHERE {{ timeFilter }}
 GROUP BY ClientRequestPath
 ORDER BY avg_ttfb DESC
-LIMIT 10 
+LIMIT 10
 ```
diff --git a/src/content/docs/log-explorer/index.mdx b/src/content/docs/log-explorer/index.mdx
index 89e85b9513fb688..8d7a69052b79578 100644
--- a/src/content/docs/log-explorer/index.mdx
+++ b/src/content/docs/log-explorer/index.mdx
@@ -8,15 +8,16 @@ products:
   - log-explorer
 ---
 
-import { Description, Feature, RelatedProduct } from "~/components"
+import { Description, Feature, RelatedProduct } from "~/components";
 
 <Description>
-Store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
+	Store and explore your Cloudflare logs directly within the Cloudflare
+	dashboard or API.
 </Description>
 
 Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third-party tools.
 
-Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include: 
+Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include:
 
 - **Reduced cost and complexity**: Drastically reduce the expense and operational overhead associated with forwarding, storing, and analyzing terabytes of log data in external tools.
 - **Faster detection and triage**: Access Cloudflare-native logs directly, eliminating cumbersome data pipelines and the ingest lags that delay critical security insights.
@@ -27,14 +28,14 @@ Contract customers can choose to store their logs in Log Explorer for up to two
 
 ## Permissions
 
-Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards. 
- 
-| Feature | Required Permission | Description |
-|----------|--------------------|--------------|
-| **Manage datasets** | `Logs Edit` | Add, enable, or disable datasets. |
-| **Log Search** | `Logs Read` | Query logs in the dashboard or via API. |
-| **Log Search (save query)** | `Logs Write` | Save log search queries. |
-| **Custom dashboards** | `Analytics Read` | Create and view custom dashboards. |
+Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards.
+
+| Feature                     | Required Permission | Description                             |
+| --------------------------- | ------------------- | --------------------------------------- |
+| **Manage datasets**         | `Logs Edit`         | Add, enable, or disable datasets.       |
+| **Log Search**              | `Logs Read`         | Query logs in the dashboard or via API. |
+| **Log Search (save query)** | `Logs Write`        | Save log search queries.                |
+| **Custom dashboards**       | `Analytics Read`    | Create and view custom dashboards.      |
 
 These permissions apply across both the dashboard and the API, and must be granted at either the account or zone level depending on which datasets you need to access.
 
@@ -43,27 +44,30 @@ Authentication with the API can be done via an API token or API key with an emai
 ## Features
 
 <Feature header="Log Search" href="/log-explorer/log-search/">
-Explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
+	Explore your Cloudflare logs directly within the Cloudflare dashboard or
+	[API](/log-explorer/api/).
 </Feature>
 
 <Feature header="Custom dashboards" href="/log-explorer/custom-dashboards/">
-Design customized views for tracking application security, performance, and usage metrics.
+	Design customized views for tracking application security, performance, and
+	usage metrics.
 </Feature>
 
 <Feature header="Manage datasets" href="/log-explorer/manage-datasets/">
-Manage the data you want to store within Log Explorer. 
+	Manage the data you want to store within Log Explorer.
 </Feature>
 
-<Feature header="API" href= "/log-explorer/api/">
-Manage configuration and perform queries via the API.
+<Feature header="API" href="/log-explorer/api/">
+	Manage configuration and perform queries via the API.
 </Feature>
 
 ## Related products
 
 <RelatedProduct header="Logpush" href="/logs/" product="logs">
-Forward Cloudflare logs to third-party tools for debugging, identifying configuration adjustments, and creating analytics dashboards.
+	Forward Cloudflare logs to third-party tools for debugging, identifying
+	configuration adjustments, and creating analytics dashboards.
 </RelatedProduct>
 
 <RelatedProduct header="Analytics" href="/analytics/" product="analytics">
-Visualize the metadata collected by our products in the Cloudflare dashboard.
-</RelatedProduct>
\ No newline at end of file
+	Visualize the metadata collected by our products in the Cloudflare dashboard.
+</RelatedProduct>
diff --git a/src/content/docs/logs/auditlogs-mcp-server.mdx b/src/content/docs/logs/auditlogs-mcp-server.mdx
index c0a8f2dd81e60e2..36c461b0633126a 100644
--- a/src/content/docs/logs/auditlogs-mcp-server.mdx
+++ b/src/content/docs/logs/auditlogs-mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the Audit Logs MCP server on GitHub.
 products:
   - logs
   - audit-logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/changelog/audit-logs.mdx b/src/content/docs/logs/changelog/audit-logs.mdx
index 146a75efedab424..2e97637e3f86291 100644
--- a/src/content/docs/logs/changelog/audit-logs.mdx
+++ b/src/content/docs/logs/changelog/audit-logs.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="audit-logs" />
\ No newline at end of file
+<ProductChangelog product="audit-logs" />
diff --git a/src/content/docs/logs/changelog/index.mdx b/src/content/docs/logs/changelog/index.mdx
index 337ffa7afa5c1cb..771bbd8160cd93c 100644
--- a/src/content/docs/logs/changelog/index.mdx
+++ b/src/content/docs/logs/changelog/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: View recent changes to Cloudflare Logs.
 products:
   - logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/changelog/logs.mdx b/src/content/docs/logs/changelog/logs.mdx
index 69133c374ad154f..7f30b4e52b1ad87 100644
--- a/src/content/docs/logs/changelog/logs.mdx
+++ b/src/content/docs/logs/changelog/logs.mdx
@@ -13,5 +13,3 @@ import { ProductChangelog } from "~/components";
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
 <ProductChangelog product="logs" />
-
-
diff --git a/src/content/docs/logs/faq/common-calculations.mdx b/src/content/docs/logs/faq/common-calculations.mdx
index 97fe1a4a59bed1f..0252af63297f09c 100644
--- a/src/content/docs/logs/faq/common-calculations.mdx
+++ b/src/content/docs/logs/faq/common-calculations.mdx
@@ -20,5 +20,3 @@ The best way to calculate bytes served by the origin is to use the `CacheRespons
 ### How do I calculate bandwidth usage for my zone?
 
 Bandwidth (or data transfer) can be calculated by adding the `EdgeResponseBytes` field in HTTP request logs. There are some types of requests that are not factored into bandwidth calculations. In order to only include relevant requests in calculations, add the filter `ClientRequestSource = 'eyeball'`.
-
-
diff --git a/src/content/docs/logs/faq/general-faq.mdx b/src/content/docs/logs/faq/general-faq.mdx
index dc0077117908e87..0be1d8058566c6f 100644
--- a/src/content/docs/logs/faq/general-faq.mdx
+++ b/src/content/docs/logs/faq/general-faq.mdx
@@ -32,7 +32,6 @@ Yes. The time period for which you pull or receive logs is based on our processi
 
 Not at this time. Talk to your Cloudflare account team or [Cloudflare Support](/support/contacting-cloudflare-support/) if you are interested in other formats and we will consider them for the future.
 
-
 ### Is it possible to track cache purge requests in the logs?
 
 Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/audit-logs/).
@@ -41,5 +40,3 @@ Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/au
 
 Requests are logged only after they successfully reach our proxy.
 It means that requests failing during the TCP or TLS handshake between the client and the Cloudflare proxy will not be available in the logs.
-
-
diff --git a/src/content/docs/logs/faq/instant-logs.mdx b/src/content/docs/logs/faq/instant-logs.mdx
index b2c23c3ee7e6a1c..1ec7a24289b2ae0 100644
--- a/src/content/docs/logs/faq/instant-logs.mdx
+++ b/src/content/docs/logs/faq/instant-logs.mdx
@@ -14,7 +14,6 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
-
 ### I am getting an HTTP 301 when attempting to connect to my WebSocket. What can I do?
 
 Make sure you are using the `wss://` protocol when connecting to your WebSocket.
@@ -34,5 +33,3 @@ Finally, make sure the destination is proxied through Cloudflare (also known as
 ### I am getting an error fetching my data. How can I solve this?
 
 Make sure you have the correct permissions. To use Instant Logs you need Super Administrator, Administrator, Log Share, or Log Share Reader permissions.
-
-
diff --git a/src/content/docs/logs/faq/logpull-api.mdx b/src/content/docs/logs/faq/logpull-api.mdx
index 28623ba05c80d58..04a52d4ae5aeb26 100644
--- a/src/content/docs/logs/faq/logpull-api.mdx
+++ b/src/content/docs/logs/faq/logpull-api.mdx
@@ -12,17 +12,12 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
-
 ### How long are logs retained?
 
 Cloudflare makes logs available for at least three days and up to seven days. If you need your logs for a longer time period, download and store them locally.
 
-
 ### I am asking for logs for the time window of 16:10-16:13. However, the timestamps in the logs show requests that are before this time period. Why does that happen?
 
-
 When you make a call for the time period of 16:10-16:13, you are actually asking for the logs that were received and processed by our system during that time (hence the endpoint name, `logs/received`). The received time is the time the logs are written to disk. There is some delay between the time the request hits the Cloudflare edge and the time it is received and processed. The **request time** is what you see in the log itself: **EdgeStartTimestamp** and **EdgeEndTimestamp** tell you when the edge started and stopped processing the request.
 
 The advantage of basing the responses on the **time received** rather than the request or edge time is not needing to worry about late-arriving logs. As long as you are calling our API for continuous time segments, you will always get all of your logs without making duplicate calls. If we based the response on request time, you could never be sure that all the logs for that request time had been processed.
-
-
diff --git a/src/content/docs/logs/faq/worker-subrequests.mdx b/src/content/docs/logs/faq/worker-subrequests.mdx
index 3d51ed73a21100d..d1652e3ff63fadd 100644
--- a/src/content/docs/logs/faq/worker-subrequests.mdx
+++ b/src/content/docs/logs/faq/worker-subrequests.mdx
@@ -19,10 +19,10 @@ Because the initial log entry only covers the request from the client to the Wor
 
 ### What the two log entries represent
 
-| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                    |
-| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------- |
+| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                                      |
+| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------------------------- |
 | Initial request   | `eyeball`                           | End-user request to the Worker         | `OriginResponseStatus` is `0`, `OriginIP` is empty |
-| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                    |
+| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                   |
 
 Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for the full list of possible `ClientRequestSource` values.
 
@@ -30,10 +30,10 @@ Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for t
 
 Each log entry has its own `RayID`. The Worker subrequest also includes `ParentRayID`, which is the `RayID` of the request that triggered it — its immediate parent.
 
-| Field         | Initial request                            | Worker subrequest                          |
-| ------------- | ------------------------------------------ | ------------------------------------------ |
-| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest       |
-| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it   |
+| Field         | Initial request                            | Worker subrequest                        |
+| ------------- | ------------------------------------------ | ---------------------------------------- |
+| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest     |
+| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it |
 
 To correlate the two records:
 
diff --git a/src/content/docs/logs/glossary.mdx b/src/content/docs/logs/glossary.mdx
index 5996605fa39a008..986f0dca8ab17e7 100644
--- a/src/content/docs/logs/glossary.mdx
+++ b/src/content/docs/logs/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - logs
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Logs documentation.
 
diff --git a/src/content/docs/logs/logpull/index.mdx b/src/content/docs/logs/logpull/index.mdx
index b22aea276e0eb94..3629ad283b4166f 100644
--- a/src/content/docs/logs/logpull/index.mdx
+++ b/src/content/docs/logs/logpull/index.mdx
@@ -8,16 +8,14 @@ products:
   - logs
 ---
 
-import { DirectoryListing, FeatureTable } from "~/components"
+import { DirectoryListing, FeatureTable } from "~/components";
 
 Cloudflare Logpull is a REST API for consuming request logs over HTTP. These logs contain data related to the connecting client, the request path through the Cloudflare network, and the response from the origin web server. This data is useful for enriching existing logs on an origin server. Logpull is available to customers on the Enterprise plan.
 
 :::caution
 
-
 Logpull is considered a legacy feature and we recommend using [Logpush](/logs/logpush/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
 
-
 :::
 
 Review the following content to learn more about Logpull.
diff --git a/src/content/docs/logs/logpull/requesting-logs.mdx b/src/content/docs/logs/logpull/requesting-logs.mdx
index c7443bca08d6d5c..685501c9631c889 100644
--- a/src/content/docs/logs/logpull/requesting-logs.mdx
+++ b/src/content/docs/logs/logpull/requesting-logs.mdx
@@ -12,20 +12,20 @@ products:
 
 The three endpoints supported by the Logpull API are:
 
-* `GET /logs/received` - returns HTTP request log data based on the parameters specified
-* `GET /logs/received/fields` - returns the list of all available log fields
-* `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
+- `GET /logs/received` - returns HTTP request log data based on the parameters specified
+- `GET /logs/received/fields` - returns the list of all available log fields
+- `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
 
 ## Required authentication headers
 
 The following headers are required for all endpoint calls:
 
-* `X-Auth-Email` - the Cloudflare account email address associated with the domain
-* `X-Auth-Key` - the Cloudflare API key
+- `X-Auth-Email` - the Cloudflare account email address associated with the domain
+- `X-Auth-Key` - the Cloudflare API key
 
 Alternatively, API tokens with Logs Read permissions can also be used for authentication:
 
-* `Authorization: Bearer <API_TOKEN>`
+- `Authorization: Bearer <API_TOKEN>`
 
 ## Parameters
 
@@ -45,11 +45,9 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}?[&fiel
 
 The following table describes the parameters available:
 
-
-
 | Parameter      | Description                                                                                                                                                                                                                                                                                                                          | Applies to                                | Required |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | -------- |
-| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p>                                                                                                                                                 | /logs/received                            | Yes      |
+| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p> | /logs/received                            | Yes      |
 | end            | <p>- Exclusive</p> <p>- Same format as <em>start</em></p> <p>- Must be at least 1 minute earlier than now and later than <em>start</em></p>                                                                                                                                                                                          | /logs/received                            | Yes      |
 | count          | <p>- Return up to that many records</p> <p>- Do not include if returning all records</p> <p>- Results are not sorted; therefore, different data for repeated requests is likely</p> <p></p> <p>- Applies to number of total records returned, not number of sampled records</p>                                                      | /logs/received                            | No       |
 | sample         | <p>- Return only a sample of records</p> <p>- Do not include if returning all records</p> <p>- Value can range from `0.0` (exclusive) to `1.0` (inclusive)</p> <p>- `sample=0.1` means return 10% (1 in 10) of all records</p> <p>- Results are random; therefore, different numbers of results for repeated requests are likely</p> | /logs/received                            | No       |
@@ -57,18 +55,14 @@ The following table describes the parameters available:
 | timestamps     | <p>- Format in which timestamp fields will be returned</p> <p>- Value options are: `unixnano` (default), `unix`, `rfc3339`</p> <p>- Timestamps returned as integers for `unix` and `unixnano` and as strings for `rfc3339`</p>                                                                                                       | <p>/logs/received</p> <p>/logs/rayids</p> | No       |
 | CVE-2021-44228 | <p>- Optional redaction for [CVE-2021-44228](https://www.cve.org/CVERecord?id=CVE-2021-44228). This option will replace every occurrence of the string `${` with `x{`.</p> <p> For example: `CVE-2021-44228=true` </p>                                                                                                               | <p>/logs/received</p>                     | No       |
 
-
-
 :::note[Note]
 
-
 The maximum time range from **start** to **end** cannot exceed 1 hour. Because **start** is inclusive and **end** is exclusive, to get all the data for every minute, starting at 10AM, the proper values are:
 
 `start=2018-05-15T10:00:00Z&end=2018-05-15T10:01:00Z`, then `start=2018-05-15T10:01:00Z&end=2018-05-15T10:02:00Z` and so on.
 
 The overlap will be handled correctly.
 
-
 :::
 
 ## Example API requests using cURL
@@ -91,10 +85,8 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}}
 
 :::note[Note]
 
-
 The IATA code returned as part of the **RayID** does not need to included in the request. For example, if you have a **RayID** such as `49ddb3e70e665831-DFW`, only include `49ddb3e70e665831` in your request.
 
-
 :::
 
 ## Fields
diff --git a/src/content/docs/logs/logpull/understanding-the-basics.mdx b/src/content/docs/logs/logpull/understanding-the-basics.mdx
index 0464c6ff3cdf093..bdd4d1622f13746 100644
--- a/src/content/docs/logs/logpull/understanding-the-basics.mdx
+++ b/src/content/docs/logs/logpull/understanding-the-basics.mdx
@@ -10,7 +10,7 @@ products:
 
 ## Access pattern
 
-The basic access pattern is *give me all the logs for zone Z for minute M* where the minute *M* refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
+The basic access pattern is _give me all the logs for zone Z for minute M_ where the minute _M_ refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
 
 To start, try running your query every minute. If responses are too small, go up to 5 minutes as this will be appropriate for most zones. If the responses are too large, try going down to 15 seconds.
 
@@ -24,7 +24,7 @@ Because our log processing system ingests data in batches, most zones with less
 
 The `logs/received` API endpoint exposes data by time received, which is the time the event was written to disk in the Cloudflare Logs aggregation system.
 
-Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from *rsyslog* (albeit in chunks).
+Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from _rsyslog_ (albeit in chunks).
 
 This means that to obtain logs for a given time range, you can issue one call for each consecutive minute (or other time range). Because log lines are batched by time received and made available, there is no late arriving data. A response for a given minute will never change. You do not have to repeatedly poll a given time range to receive logs as they converge on our aggregation system.
 
@@ -32,7 +32,7 @@ This means that to obtain logs for a given time range, you can issue one call fo
 
 The Logpull API returns data in NDJSON format, whereby each log line is a valid JSON object. Major analysis tools like Google BigQuery and AWS Kinesis require this format.
 
-To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into *jq* using the *slurp* (or simply *s*) flag:
+To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into _jq_ using the _slurp_ (or simply _s_) flag:
 
 `<API request data> | jq -s`
 
@@ -42,15 +42,15 @@ The following is a sample log with default fields:
 
 ```json
 {
-  "ClientIP": "89.163.242.206",
-  "ClientRequestHost": "www.theburritobot.com",
-  "ClientRequestMethod": "GET",
-  "ClientRequestURI": "/static/img/testimonial-hipster.png",
-  "EdgeEndTimestamp": 1506702504461999900,
-  "EdgeResponseBytes": 69045,
-  "EdgeResponseStatus": 200,
-  "EdgeStartTimestamp": 1506702504433000200,
-  "RayID": "3a6050bcbe121a87"
+	"ClientIP": "89.163.242.206",
+	"ClientRequestHost": "www.theburritobot.com",
+	"ClientRequestMethod": "GET",
+	"ClientRequestURI": "/static/img/testimonial-hipster.png",
+	"EdgeEndTimestamp": 1506702504461999900,
+	"EdgeResponseBytes": 69045,
+	"EdgeResponseStatus": 200,
+	"EdgeStartTimestamp": 1506702504433000200,
+	"RayID": "3a6050bcbe121a87"
 }
 ```
 
diff --git a/src/content/docs/logs/logpush-mcp-server.mdx b/src/content/docs/logs/logpush-mcp-server.mdx
index 606c4e683714467..66fb1c45f2e2f73 100644
--- a/src/content/docs/logs/logpush-mcp-server.mdx
+++ b/src/content/docs/logs/logpush-mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Access the Logpush MCP server on GitHub.
 products:
   - logs
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
index 4ab48625e439d06..fd2d2d005e6d33d 100644
--- a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
+++ b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
@@ -12,10 +12,8 @@ You can manage your Cloudflare Logpush service using Python. In the script below
 
 :::note
 
-
 The examples below are for zone-scoped datasets. Account-scoped datasets should use `<ACCOUNT_ID>` instead of `<ZONE_ID>`.
 
-
 :::
 
 ```python
diff --git a/src/content/docs/logs/logpush/examples/index.mdx b/src/content/docs/logs/logpush/examples/index.mdx
index d593b40a49fe8db..17da91fca9f2307 100644
--- a/src/content/docs/logs/logpush/examples/index.mdx
+++ b/src/content/docs/logs/logpush/examples/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/index.mdx b/src/content/docs/logs/logpush/index.mdx
index c97ab2846f221ff..e93944723bd2eb9 100644
--- a/src/content/docs/logs/logpush/index.mdx
+++ b/src/content/docs/logs/logpush/index.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { FeatureTable, LinkButton } from "~/components"
+import { FeatureTable, LinkButton } from "~/components";
 
 Logpush delivers logs in batches as quickly as possible, with no minimum batch size, potentially delivering files more than once per minute. This capability enables Cloudflare to provide information almost in real time, in smaller file sizes.
 
@@ -57,8 +57,6 @@ There is currently a max limit of **4 Logpush jobs per zone**. Trying to create
 
 :::note
 
-
 Users without an Enterprise plan can still access [Workers Trace Events Logpush](/workers/observability/logs/logpush/) by subscribing to the [Workers Paid](/workers/platform/pricing/) plan.
 
-
 :::
diff --git a/src/content/docs/logs/logpush/logpush-health.mdx b/src/content/docs/logs/logpush/logpush-health.mdx
index 10604407f89dd20..9f31536d4532a8a 100644
--- a/src/content/docs/logs/logpush/logpush-health.mdx
+++ b/src/content/docs/logs/logpush/logpush-health.mdx
@@ -20,17 +20,17 @@ Health notifications work alongside the Health Dashboard to provide both real-ti
 
 ## Access Health Dashboards
 
-1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.  
-2. Go to the **Health** tab.  
-3. Select the job you want to analyze.  
-4. Specify the time range you want to review.  
-5. *(Optional)* From the **Jobs** tab, locate the job you want to analyze.  
-6. Hover over the **Job Health (24h)** column for that job and select **View Health**.  
+1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.
+2. Go to the **Health** tab.
+3. Select the job you want to analyze.
+4. Specify the time range you want to review.
+5. _(Optional)_ From the **Jobs** tab, locate the job you want to analyze.
+6. Hover over the **Job Health (24h)** column for that job and select **View Health**.
 7. You will be redirected to the **Health** tab, where you can select the desired time range for analysis.
 
 ### Data availability and API access
 
-- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.  
+- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.
 - The raw health metrics can be queried via the `logpushHealthAdaptiveGroups` dataset in the GraphQL API.
 - You can explore or test queries using the [Cloudflare GraphQL Explorer](https://graphql.cloudflare.com/explorer).
 
@@ -62,7 +62,7 @@ Indicates that all upload attempts for a batch were exhausted without success. W
 
 ## Health dashboard flow
 
-The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.  
+The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.
 
 Each view highlights a different aspect of job performance — what was delivered and how reliably it was delivered.
 
@@ -72,23 +72,23 @@ Each view highlights a different aspect of job performance — what was delivere
 
 #### Charts and metrics
 
-- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.  
-    - **Successful Uploads** - Total number of batches successfully uploaded.  
-    - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
+- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.
+  - **Successful Uploads** - Total number of batches successfully uploaded.
+  - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
 
-- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.  
-    - **Uploaded Log Lines** - Total number of log lines successfully delivered.  
-    - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
+- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.
+  - **Uploaded Log Lines** - Total number of log lines successfully delivered.
+  - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
 
-- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.  
-    - **Uncompressed Data (raw)** - Total size of log data before compression.  
-    - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
+- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.
+  - **Uncompressed Data (raw)** - Total size of log data before compression.
+  - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
 
 #### When to use
 
 Start here to assess overall data delivery health:
 
-- High upload success and stable data volume indicate a healthy Logpush job.  
+- High upload success and stable data volume indicate a healthy Logpush job.
 - Drops, spikes, or failed uploads suggest delivery issues — proceed to **Upload Reliability** to investigate root causes.
 
 ### Upload Reliability
@@ -97,37 +97,37 @@ Upload Reliability helps you identify factors affecting reliability, stability,
 
 #### Charts and metrics
 
-- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.  
-    - **Success Rate** - Percentage of batches successfully uploaded.  
-    - **Successful Uploads** - Total number of batches successfully completed.
+- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.
+  - **Success Rate** - Percentage of batches successfully uploaded.
+  - **Successful Uploads** - Total number of batches successfully completed.
 
-- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.  
-    - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.  
-    - **Average Upload Duration** - Average time taken to upload logs after they are generated.
+- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.
+  - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.
+  - **Average Upload Duration** - Average time taken to upload logs after they are generated.
 
-- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.  
-    - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
+- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.
+  - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
 
 #### When to use
 
 Use this view to troubleshoot reliability issues:
 
-- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.  
+- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.
 - Combine with **Upload Health** metrics to correlate delivery success with underlying reliability patterns.
 
 ## Troubleshooting guide
 
 The Logpush Health Dashboards help you monitor the status, reliability, and performance of your Logpush jobs. Use this guide to interpret each chart, identify the root cause of anomalies, and take corrective action.
 
-| Chart name | Symptom | What it means | Possible causes | Recommended actions |
-|-----------------|-------------|-------------------|----------------------|--------------------------|
-| **Batch Upload Success vs Failure** | Failed uploads | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/>  - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
-| **Log Lines Uploaded** | Dropped log lines or reduced delivery volume | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches. | - Spike in failed uploads. <br/>  - Destination ingestion limits or partial uploads. | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/>  - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes. |
-| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches. | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits. | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries. |
-| **Uploaded Logs by Status Code** | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries. | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination. | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size. |
-| **Retry Attempts** | Frequent retry activity | Uploads are repeatedly failing and retried multiple times. | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination. | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review. |
-| **Avg. Upload Duration** | Long upload times | Uploads are taking longer than expected, indicating latency or oversized batches. | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays. | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings. |
-| **Destination Availability** | Low or unstable availability | Cloudflare cannot consistently connect to your destination. | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare. | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings. |
+| Chart name                                  | Symptom                                       | What it means                                                                                                                                 | Possible causes                                                                                                                                                                                                       | Recommended actions                                                                                                                                                                                                                           |
+| ------------------------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Batch Upload Success vs Failure**         | Failed uploads                                | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/> - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
+| **Log Lines Uploaded**                      | Dropped log lines or reduced delivery volume  | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches.                                                 | - Spike in failed uploads. <br/> - Destination ingestion limits or partial uploads.                                                                                                                                   | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/> - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes.                                               |
+| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume                | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches.                                       | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits.                                                                                                         | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries.                                                                                             |
+| **Uploaded Logs by Status Code**            | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries.                                                                                     | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination.                                                                                                   | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size.                                                                                         |
+| **Retry Attempts**                          | Frequent retry activity                       | Uploads are repeatedly failing and retried multiple times.                                                                                    | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination.                                                                                                    | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review.                                                             |
+| **Avg. Upload Duration**                    | Long upload times                             | Uploads are taking longer than expected, indicating latency or oversized batches.                                                             | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays.                                                                                                 | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings.                                                                                        |
+| **Destination Availability**                | Low or unstable availability                  | Cloudflare cannot consistently connect to your destination.                                                                                   | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare.                                                                                           | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings.                                                                             |
 
 ## Understanding retry behavior
 
diff --git a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
index 6a98f17905433ca..d7b7dd78507d62e 100644
--- a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
@@ -18,19 +18,19 @@ You can locate `{zone_id}` and `{account_id}` arguments based on the [Find zone
 The `{job_id}` argument is numeric, like 123456.
 The `{dataset_id}` argument indicates the log category (such as `http_requests` or `audit_logs`).
 
-| Operation | Description                                 | API                                                                                                                                                                                              |
+| Operation | Description                                 | API                                                                                            |
 | --------- | ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                                             |
-| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)                                     |
-| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                                                 |
-| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)        |
+| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                      |
+| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
+| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                        |
+| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
 | `GET`     | Retrieve all available fields for a dataset | [Documentation](/api/resources/logpush/subresources/datasets/subresources/fields/methods/get/) |
-| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                                      |
-| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                           |
-| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/) |
-| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                                      |
-| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                      |
-| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                           |
+| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                      |
+| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                      |
+| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/)             |
+| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
+| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
+| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                  |
 
 For concrete examples, refer to the tutorials in [Logpush examples](/logs/logpush/examples/).
 
@@ -47,25 +47,25 @@ Before creating a new job, ownership of the destination must be proven.
 To issue an ownership challenge token to your destination:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/ownership"
-  method="POST"
-  json={{
-    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-  }}
+	path="/zones/{zone_id}/logpush/ownership"
+	method="POST"
+	json={{
+		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+	}}
 />
 
 A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path, if appropriate for your destination):
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "valid": true,
-    "message": "",
-    "filename": "<PATH_TO_CHALLENGE_FILE>.txt"
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"valid": true,
+		"message": "",
+		"filename": "<PATH_TO_CHALLENGE_FILE>.txt"
+	},
+	"success": true
 }
 ```
 
@@ -138,23 +138,23 @@ For more information on the value for your cloud storage provider, consult the f
 To check if a destination is already in use:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/validate/destination/exists"
-  method="POST"
-  json={{
-    destination_conf: "s3://foo",
-  }}
+	path="/zones/{zone_id}/logpush/validate/destination/exists"
+	method="POST"
+	json={{
+		destination_conf: "s3://foo",
+	}}
 />
 
 Response
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "exists": false
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"exists": false
+	},
+	"success": true
 }
 ```
 
@@ -173,28 +173,28 @@ The kind parameter cannot be used to update existing Logpush jobs. You can only
 :::
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/jobs"
-  method="POST"
-  json={{
-    name: "<DOMAIN_NAME>",
-    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-    dataset: "http_requests",
-    output_options: {
-      field_names: [
-        "ClientIP",
-        "ClientRequestHost",
-        "ClientRequestMethod",
-        " ClientRequestURI",
-        "EdgeEndTimestamp",
-        "EdgeResponseBytes",
-        "EdgeResponseStatus",
-        "EdgeStartTimestamp",
+	path="/zones/{zone_id}/logpush/jobs"
+	method="POST"
+	json={{
+		name: "<DOMAIN_NAME>",
+		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+		dataset: "http_requests",
+		output_options: {
+			field_names: [
+				"ClientIP",
+				"ClientRequestHost",
+				"ClientRequestMethod",
+				" ClientRequestURI",
+				"EdgeEndTimestamp",
+				"EdgeResponseBytes",
+				"EdgeResponseStatus",
+				"EdgeStartTimestamp",
 				"RayID",
-      ],
+			],
 			timestamp_format: "rfc3339",
-    },
+		},
 		kind: "edge",
-  }}
+	}}
 />
 
 ## Options
@@ -205,7 +205,7 @@ If you are still using logpull_options, here are the options that you can custom
 
 1. **Fields** (optional): Refer to [Datasets](/logs/logpush/logpush-job/datasets/) for the currently available fields. The list of fields is also accessible directly from the API: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields`. Default fields: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields/default`.
 2. **Timestamp format** (optional): The format in which timestamp fields will be returned. Value options: `unixnano` (nanoseconds unit - default), `unix` (seconds unit), `rfc3339` (seconds unit).
-3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`.  To enable it, set `"CVE-2021-44228": true`.
+3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`. To enable it, set `"CVE-2021-44228": true`.
 
 :::note[Note]
 
@@ -215,26 +215,26 @@ The **CVE-2021-44228** parameter can only be set through the API at this time. U
 To check if the selected **logpull_options** are valid:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/validate/origin"
-  method="POST"
-  json={{
+	path="/zones/{zone_id}/logpush/validate/origin"
+	method="POST"
+	json={{
 		logpull_options:
 			"fields=RayID,ClientIP,EdgeStartTimestamp&timestamps=rfc3339&CVE-2021-44228=true",
 		dataset: "http_requests",
-  }}
+	}}
 />
 
 Response
 
 ```json
 {
-  "errors": [],
-  "messages": [],
-  "result": {
-    "valid": true,
-    "message": ""
-  },
-  "success": true
+	"errors": [],
+	"messages": [],
+	"result": {
+		"valid": true,
+		"message": ""
+	},
+	"success": true
 }
 ```
 
@@ -280,10 +280,10 @@ When customer-configured sampling is applied, the `SampleInterval` field value i
 
 These parameters control the size of each upload batch — not how quickly data is delivered. Use them to prevent overloading your destination with uploads that are too large or too small.
 
-| Parameter | Description | Default |
-| --- | --- | --- |
-| `max_upload_bytes` | Maximum uncompressed file size of a batch of logs. | Varies by destination |
-| `max_upload_records` | Maximum number of log lines per batch. | 100,000 |
+| Parameter                     | Description                                                               | Default               |
+| ----------------------------- | ------------------------------------------------------------------------- | --------------------- |
+| `max_upload_bytes`            | Maximum uncompressed file size of a batch of logs.                        | Varies by destination |
+| `max_upload_records`          | Maximum number of log lines per batch.                                    | 100,000               |
 | `max_upload_interval_seconds` | Maximum time-span of log data per batch (used during catch-up scenarios). | Varies by destination |
 
 :::note
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
index 618a7f86d3a5d55..a9bd442099c837b 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
index 2068e23086295d9..452263a6cac1017 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
@@ -1,8 +1,8 @@
 ---
 pcx_content_type: reference
-title: CMB support by dataset 
+title: CMB support by dataset
 external_link: /data-localization/metadata-boundary/logpush-datasets/
 description: Learn about cmb support by dataset  in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
index 64c4408ce21b874..d57a162728ea19b 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
@@ -12,25 +12,25 @@ products:
 
 The datasets below describe the fields available by log category:
 
-* [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
-* [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
+- [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
+- [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
 
 ## API
 
 The list of fields can also be accessed directly from the API using the following endpoints:
 
-* For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
+- For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
 
-* For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
+- For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
 
 The `<DATASET>` argument indicates the log category. For example, `http_requests`, `spectrum_events`, `firewall_events`, `nel_reports`, or `dns_logs`.
 
 ## Availability
 
-* The availability of Logpush dataset fields depends on your subscription plan.
-* Zone-scoped HTTP requests are available in both Logpush and Logpull.
-* [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
-* All other datasets are only available through Logpush.
+- The availability of Logpush dataset fields depends on your subscription plan.
+- Zone-scoped HTTP requests are available in both Logpush and Logpull.
+- [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
+- All other datasets are only available through Logpush.
 
 ## Deprecation
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
index f21b39be05e2657..3916cd8f337d26e 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
@@ -49,7 +49,7 @@ Whether the response was cached or not.
 
 Type: `int`
 
-Integer value of response code. For more information refer to  [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
+Integer value of response code. For more information refer to [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
 
 ## SourceIP
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
index b44ea90a6fa6a98..d9de685d205d4d0 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
index 6b8090800495242..12b4d2e27bc5489 100644
--- a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
@@ -8,9 +8,8 @@ products:
   - logpush
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
 Edge Log Delivery allows customers to send logs directly from Cloudflare’s edge to their destination of choice. You can configure the maximum interval for your log batches between 30 seconds and five minutes. However, you cannot specify a minimum interval for log batches, meaning that log files may be sent in shorter intervals than the maximum specified. Compared to Logpush, Edge Log Delivery sends logs with lower latency, more frequently, and in smaller batches.
 
 Edge Log Delivery is only available for HTTP request logs. Refer to the [API configuration](/logs/logpush/logpush-job/api-configuration/#kind) page for steps on how to configure a job to use Edge Log Delivery.
-
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
index 65b671327acdea2..e9823d82ca24e5c 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
@@ -42,9 +42,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
index 301c4bcbaf9e976..437fe5b4f67cf0f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
@@ -79,6 +79,7 @@ signedResourceTypes must be Object only (srt=o)
 ```
 
 To resolve this error, regenerate your SAS token using [Storage Explorer](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer) with the correct permissions:
+
 - Service: Blob-only (`ss=b`)
 - Resource type: Object-only (`srt=o`)
 - Permissions: Write-only
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
index bde5e5a6cadf67d..bfc9e8b76c9f8f2 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
@@ -40,22 +40,23 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 1. Register or use an existing zone for the dedicated egress IPs pool.
 2. Contact your account team to get the ID for your dedicated egress IPs pool.
 3. Make a `PATCH` request to the [Edit Zone Setting](/api/resources/zones/subresources/settings/methods/edit/) endpoint:
-  - Specify `aegis` as the setting ID in the URL.
-  - In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
+
+- Specify `aegis` as the setting ID in the URL.
+- In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
 
 <APIRequest
-  path="/zones/{zone_id}/settings/{setting_id}"
-  method="PATCH"
-  json={{
-		  "id": "aegis",
-			"value": {
-				"enabled": true,
-				"pool_id": "<YOUR_EGRESS_POOL_ID>",
-				},
+	path="/zones/{zone_id}/settings/{setting_id}"
+	method="PATCH"
+	json={{
+		id: "aegis",
+		value: {
+			enabled: true,
+			pool_id: "<YOUR_EGRESS_POOL_ID>",
+		},
 	}}
 	parameters={{
-    setting_id: "aegis",
-  }}
+		setting_id: "aegis",
+	}}
 />
 
 ## 3. Proxy zone setup
@@ -66,7 +67,6 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 
 2. If needed, configure [origin rules](/rules/origin-rules/) to specify a custom port. This is useful if your destination only accepts traffic on a non standard port, for example `12345`. You can configure `logpush.yourdestinationendpoint.com` (without specifying a port, as Cloudflare by default only proxies traffic on HTTP/HTTPS ports) to proxy to `yourdestinationendpoint.com:12345`.
 
-
 ## 4. Configure Logpush
 
 1. Create a Logpush job with the following details:
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
index 037278d7af513e7..271f74a01e3f258 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
@@ -11,22 +11,20 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Push your Cloudflare logs to Elastic for instant visibility and insights. Enabling this integration with Elastic comes with a predefined dashboard to view all of your Cloudflare observability and security data with ease.
 
 The Cloudflare Logpush integration can be used in three different modes to collect data:
 
-* **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
-* **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
-* **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
+- **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
+- **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
+- **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
 
 :::note[Note]
 
-
 Elastic recommends the AWS S3 SQS mode.
 
-
 :::
 
 ## Enable Logpush Job in Cloudflare
@@ -44,17 +42,18 @@ Add the same custom header along with its value on both sides for additional sec
 For example, while creating a job along with a header and value for a particular dataset:
 
 <APIRequest
-  path="/zones/{zone_id}/logpush/jobs"
-  method="POST"
-  json={{
-    name: "<PUBLIC_DOMAIN>",
-    destination_conf: "https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
-    dataset: "http_requests",
-    output_options: {
-      field_names: ["RayID", "EdgeStartTimestamp"],
-      timestamp_format: "rfc3339"
-    }
-  }}
+	path="/zones/{zone_id}/logpush/jobs"
+	method="POST"
+	json={{
+		name: "<PUBLIC_DOMAIN>",
+		destination_conf:
+			"https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
+		dataset: "http_requests",
+		output_options: {
+			field_names: ["RayID", "EdgeStartTimestamp"],
+			timestamp_format: "rfc3339",
+		},
+	}}
 />
 
 ## Enable the Integration in Elastic
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
index 559b432c8b43b4e..79d92a490df72b5 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
@@ -39,9 +39,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
index 54b030d14362706..bc517b5783e0a01 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 To configure a QRadar/Cloudflare integration you have the option to use one of the following methods:
 
@@ -22,57 +22,113 @@ To send Cloudflare logs to QRadar you need to create a [Logpush job to HTTP endp
 ### Cloudflare Firewall events
 
 <APIRequest
-  method="POST"
-  path="/zones/{zone_id}/logpush/jobs"
-  json={{
-    name: "<NAME>",
-    output_options: {
-      field_names: [
-        "Action", "ClientIP", "ClientASN", "ClientASNDescription", "ClientCountry", "ClientIPClass",
-        "ClientRefererHost", "ClientRefererPath", "ClientRefererQuery", "ClientRefererScheme",
-        "ClientRequestHost", "ClientRequestMethod", "ClientRequestPath", "ClientRequestProtocol",
-        "ClientRequestQuery", "ClientRequestScheme", "ClientRequestUserAgent", "EdgeColoCode",
-        "EdgeResponseStatus", "Kind", "MatchIndex", "Metadata", "OriginResponseStatus",
-        "OriginatorRayID", "RayID", "RuleID", "Source", "Datetime"
-      ],
-      timestamp_format: "rfc3339"
-    },
-    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-    max_upload_bytes: 5000000,
-    max_upload_records: 1000,
-    dataset: "firewall_events",
-    enabled: true
-  }}
+	method="POST"
+	path="/zones/{zone_id}/logpush/jobs"
+	json={{
+		name: "<NAME>",
+		output_options: {
+			field_names: [
+				"Action",
+				"ClientIP",
+				"ClientASN",
+				"ClientASNDescription",
+				"ClientCountry",
+				"ClientIPClass",
+				"ClientRefererHost",
+				"ClientRefererPath",
+				"ClientRefererQuery",
+				"ClientRefererScheme",
+				"ClientRequestHost",
+				"ClientRequestMethod",
+				"ClientRequestPath",
+				"ClientRequestProtocol",
+				"ClientRequestQuery",
+				"ClientRequestScheme",
+				"ClientRequestUserAgent",
+				"EdgeColoCode",
+				"EdgeResponseStatus",
+				"Kind",
+				"MatchIndex",
+				"Metadata",
+				"OriginResponseStatus",
+				"OriginatorRayID",
+				"RayID",
+				"RuleID",
+				"Source",
+				"Datetime",
+			],
+			timestamp_format: "rfc3339",
+		},
+		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+		max_upload_bytes: 5000000,
+		max_upload_records: 1000,
+		dataset: "firewall_events",
+		enabled: true,
+	}}
 />
 
-
 ### Cloudflare HTTP events
 
 <APIRequest
-  method="POST"
-  path="/zones/{zone_id}/logpush/jobs"
-  json={{
-    name: "<NAME>",
-    output_options: {
-      field_names: [
-        "ClientRequestMethod", "EdgeResponseStatus", "ClientIP", "ClientSrcPort", "CacheCacheStatus",
-        "ClientCountry", "ClientDeviceType", "ClientIPClass", "ClientMTLSAuthCertFingerprint", "ClientMTLSAuthStatus",
-        "ClientRegionCode", "ClientRequestBytes", "ClientRequestHost", "ClientRequestPath", "ClientRequestProtocol",
-        "ClientRequestReferer", "ClientRequestScheme", "ClientRequestSource", "ClientRequestURI", "ClientRequestUserAgent",
-        "ClientSSLCipher", "ClientSSLProtocol", "ClientXRequestedWith", "EdgeEndTimestamp", "EdgeRequestHost",
-        "EdgeResponseBodyBytes", "EdgeResponseBytes", "EdgeServerIP", "EdgeStartTimestamp", "SecurityActions",
-        "SecurityRuleIDs", "SecuritySources", "OriginIP", "OriginResponseStatus", "OriginSSLProtocol", "ParentRayID",
-        "RayID", "SecurityAction", "WAFAttackScore", "SecurityRuleID", "SecurityRuleDescription", "WAFSQLiAttackScore",
-        "WAFXSSAttackScore", "EdgeStartTimestamp"
-      ],
-      timestamp_format: "rfc3339"
-    },
-    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-    max_upload_bytes: 5000000,
-    max_upload_records: 1000,
-    dataset: "http_requests",
-    enabled: true
-  }}
+	method="POST"
+	path="/zones/{zone_id}/logpush/jobs"
+	json={{
+		name: "<NAME>",
+		output_options: {
+			field_names: [
+				"ClientRequestMethod",
+				"EdgeResponseStatus",
+				"ClientIP",
+				"ClientSrcPort",
+				"CacheCacheStatus",
+				"ClientCountry",
+				"ClientDeviceType",
+				"ClientIPClass",
+				"ClientMTLSAuthCertFingerprint",
+				"ClientMTLSAuthStatus",
+				"ClientRegionCode",
+				"ClientRequestBytes",
+				"ClientRequestHost",
+				"ClientRequestPath",
+				"ClientRequestProtocol",
+				"ClientRequestReferer",
+				"ClientRequestScheme",
+				"ClientRequestSource",
+				"ClientRequestURI",
+				"ClientRequestUserAgent",
+				"ClientSSLCipher",
+				"ClientSSLProtocol",
+				"ClientXRequestedWith",
+				"EdgeEndTimestamp",
+				"EdgeRequestHost",
+				"EdgeResponseBodyBytes",
+				"EdgeResponseBytes",
+				"EdgeServerIP",
+				"EdgeStartTimestamp",
+				"SecurityActions",
+				"SecurityRuleIDs",
+				"SecuritySources",
+				"OriginIP",
+				"OriginResponseStatus",
+				"OriginSSLProtocol",
+				"ParentRayID",
+				"RayID",
+				"SecurityAction",
+				"WAFAttackScore",
+				"SecurityRuleID",
+				"SecurityRuleDescription",
+				"WAFSQLiAttackScore",
+				"WAFXSSAttackScore",
+				"EdgeStartTimestamp",
+			],
+			timestamp_format: "rfc3339",
+		},
+		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+		max_upload_bytes: 5000000,
+		max_upload_records: 1000,
+		dataset: "http_requests",
+		enabled: true,
+	}}
 />
 
 Cloudflare checks the accessibility of the IP address, port, and validates the certificate of the HTTP Receive log source. If all parameters are valid, a Logpush is created, and starts to send events to HTTP Receiver log source.
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
index c9e507400e4736f..e30073dde0691a1 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
@@ -79,7 +79,7 @@ When configuring your Logpush job using IAM Access Keys, ensure that the IAM use
 kinesis://<STREAM_NAME>?region=<AWS_REGION>&access-key-id=<AWS_ACCESS_KEY_ID>&secret-access-key=<AWS_SECRET_ACCESS_KEY>
 ```
 
-### IAM Access Key example 
+### IAM Access Key example
 
 ```bash
 $ curl https://api.cloudflare.com/client/v4/zones/$ZONE_TAG/logpush/jobs \
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
index b5a8ad2efe5d08a..c8e74bd58ce5b1c 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about exabeam in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
index ebd93fd74f3fe4e..e035c9cab36b111 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about sekoia in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
index 33a79b6922e260b..9b27ff95df6e41f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about taegis in Cloudflare Logs.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/filters.mdx b/src/content/docs/logs/logpush/logpush-job/filters.mdx
index e3d0dec59462d05..70fd97b0bc41bcc 100644
--- a/src/content/docs/logs/logpush/logpush-job/filters.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/filters.mdx
@@ -100,11 +100,10 @@ Here is an example request using cURL via API:
 To set filters through the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
- 
+
    For account: <DashButton url="/?to=/:account/logs" />
- 
-   For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
+   For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select the dataset you want to push to a storage service. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
 3. Below **Select data fields**, in the **Filter** section, you can set up your filters.
diff --git a/src/content/docs/logs/logpush/logpush-job/index.mdx b/src/content/docs/logs/logpush/logpush-job/index.mdx
index 552977e3e38e2b6..9f631a5d38edfd0 100644
--- a/src/content/docs/logs/logpush/logpush-job/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: Configure and manage Logpush job settings.
 products:
   - logpush
----
\ No newline at end of file
+---
diff --git a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
index 69caff8184b218b..0c4922d8910409d 100644
--- a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
@@ -70,17 +70,17 @@ Your bucket's IAM/access controls and Cloudflare account security are the primar
 
 ## Which destinations require an ownership challenge?
 
-| Destination | Ownership challenge required |
-| --- | --- |
-| AWS S3 | Yes (or use access key/secret key) |
-| Google Cloud Storage | Yes |
-| Azure Blob Storage | Yes |
-| Sumo Logic | Yes |
-| S3-compatible storage | No |
-| HTTP endpoints | No |
-| Datadog | No |
-| Splunk | No |
-| New Relic | No |
+| Destination           | Ownership challenge required       |
+| --------------------- | ---------------------------------- |
+| AWS S3                | Yes (or use access key/secret key) |
+| Google Cloud Storage  | Yes                                |
+| Azure Blob Storage    | Yes                                |
+| Sumo Logic            | Yes                                |
+| S3-compatible storage | No                                 |
+| HTTP endpoints        | No                                 |
+| Datadog               | No                                 |
+| Splunk                | No                                 |
+| New Relic             | No                                 |
 
 For destinations that do not require an ownership challenge, Cloudflare uses alternative authentication methods such as API keys or tokens.
 
diff --git a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
index 090c84dab4fef92..b69e56fe07a33a4 100644
--- a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
+++ b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
@@ -9,12 +9,12 @@ products:
   - logs
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components";
 
 Cloudflare will deploy some updates to security-related fields in Cloudflare Logs. These updates will affect the following datasets:
 
-* [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
-* [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
+- [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
+- [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
 
 ## Timeline
 
@@ -26,18 +26,18 @@ For the log fields being added, Cloudflare will gradually start adding them to l
 
 For the log fields being renamed, Cloudflare will:
 
-* **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
-* **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
+- **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
+- **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
 
 For the log fields being removed, Cloudflare is announcing them as deprecated. Their removal from logs datasets will occur on August 1, 2023.
 
 In addition to these Cloudflare Logs changes, Cloudflare will also add new security-related fields to the following [GraphQL datasets](/analytics/graphql-api/features/data-sets/):
 
-* `httpRequestsAdaptive `
-* `httpRequestsAdaptiveGroups`
-* `firewallEventsAdaptive`
-* `firewallEventsAdaptiveGroups`
-* `firewallEventsAdaptiveByTimeGroups`
+- `httpRequestsAdaptive `
+- `httpRequestsAdaptiveGroups`
+- `firewallEventsAdaptive`
+- `firewallEventsAdaptiveGroups`
+- `firewallEventsAdaptiveByTimeGroups`
 
 ### Phase 2 (August 1, 2023)
 
@@ -49,27 +49,23 @@ For the log fields being removed, Cloudflare will also remove them from the Clou
 
 The following concepts are used below in the reviewed field descriptions:
 
-* **Terminating action:** One of the following actions:
-
-  * `block`
-  * `js_challenge`
-  * `managed_challenge`
-  * `challenge` (*Interactive Challenge*)
+- **Terminating action:** One of the following actions:
+  - `block`
+  - `js_challenge`
+  - `managed_challenge`
+  - `challenge` (_Interactive Challenge_)
 
 For more information on these actions, refer to the [Actions](/ruleset-engine/rules-language/actions/) reference in the Rules language documentation.
 
-* **Security rule:** One of the following rule types:
-
-  * [WAF managed rule](/waf/managed-rules/)
-  * [WAF custom rule](/waf/custom-rules/)
-  * [WAF rate limiting rule](/waf/rate-limiting-rules/)
+- **Security rule:** One of the following rule types:
+  - [WAF managed rule](/waf/managed-rules/)
+  - [WAF custom rule](/waf/custom-rules/)
+  - [WAF rate limiting rule](/waf/rate-limiting-rules/)
 
 ## HTTP Requests dataset changes
 
 The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) dataset according to the two-phase strategy outlined in the [timeline](#timeline):
 
-
-
 | New field name            | Type         | Description                                                                        | Old field name<br/>(deprecated on Aug 1, 2023) |
 | ------------------------- | ------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------- |
 | `SecurityRuleID`          | String       | Rule ID of the security rule that triggered a terminating action, if any.          | `WAFRuleID`                                    |
@@ -79,12 +75,8 @@ The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpus
 | `SecurityActions`         | String Array | Array of actions that Cloudflare security products performed on the request.       | `FirewallMatchesActions`                       |
 | `SecuritySources`         | String Array | Array of Cloudflare security products that matched the request.                    | `FirewallMatchesSources`                       |
 
-
-
 The following fields are now deprecated and they will be removed from the HTTP Requests dataset on August 1, 2023:
 
-
-
 | Deprecated field name | Notes                                                                 |
 | --------------------- | --------------------------------------------------------------------- |
 | `WAFProfile`          | Used in the previous version of WAF managed rules (now deprecated).   |
@@ -92,44 +84,30 @@ The following fields are now deprecated and they will be removed from the HTTP R
 | `EdgeRateLimitID`     | Used in the previous version of rate limiting rules (now deprecated). |
 | `SecurityLevel`       | N/A                                                                   |
 
-
-
 ## Firewall Events dataset changes
 
 The following fields will be added to the [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/) dataset:
 
-
-
 | Field name    | Type   | Description                                                        |
 | ------------- | ------ | ------------------------------------------------------------------ |
 | `Description` | String | The description of the rule triggered by the request.              |
 | `Ref`         | String | The user-defined identifier for the rule triggered by the request. |
 
-
-
 ## Changes to GraphQL datasets
 
 Cloudflare will add the following fields to the `httpRequestsAdaptive `and `httpRequestsAdaptiveGroups `datasets:
 
-
-
 | Field name       | Type   | Description                                                              |
 | ---------------- | ------ | ------------------------------------------------------------------------ |
 | `securityAction` | String | Action of the security rule that triggered a terminating action, if any. |
 | `securitySource` | String | Source of the security rule that triggered a terminating action, if any. |
 
-
-
 Cloudflare will also add the following field to the `firewallEventsAdaptive`, `firewallEventsAdaptiveGroups`, and `firewallEventsAdaptiveByTimeGroups` datasets:
 
-
-
 | Field name    | Type   | Description                                           |
 | ------------- | ------ | ----------------------------------------------------- |
 | `description` | String | The description of the rule triggered by the request. |
 
-
-
 These new fields will become gradually available.
 
 For more information on the available datasets, refer to [GraphQL datasets](/analytics/graphql-api/features/data-sets/).
@@ -143,8 +121,8 @@ After updating Logpush jobs, you may need to update external filters or reports
 ### Update Logpush job in the dashboard
 
 1. In the Cloudflare dashboard, go to the **Logpush** page.
- 
-    <DashButton url="/?to=/:account/:zone/analytics/logs" />
+
+   <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select **Edit** next to the Logpush job you wish to edit.
 3. Under **Select data fields**, update the fields in your job. The new security log fields are available under **General**.
@@ -152,7 +130,7 @@ After updating Logpush jobs, you may need to update external filters or reports
 
 ### Update Logpush job via API
 
-Follow the instructions in [Update output\_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
+Follow the instructions in [Update output_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
 
 ### Update Logpush job via Terraform
 
diff --git a/src/content/docs/logs/reference/change-notices/index.mdx b/src/content/docs/logs/reference/change-notices/index.mdx
index 73f10f158563f08..9457944fa3b5f78 100644
--- a/src/content/docs/logs/reference/change-notices/index.mdx
+++ b/src/content/docs/logs/reference/change-notices/index.mdx
@@ -11,6 +11,6 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/reference/clientrequestsource.mdx b/src/content/docs/logs/reference/clientrequestsource.mdx
index 142639187d95beb..13558a727481adb 100644
--- a/src/content/docs/logs/reference/clientrequestsource.mdx
+++ b/src/content/docs/logs/reference/clientrequestsource.mdx
@@ -11,8 +11,6 @@ products:
 
 The possible values for the `ClientRequestSource` field are the following:
 
-
-
 | Value | Request source     | Description                                                                                                                             |
 | ----- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
 | `0`   | unknown            | Should never happen.                                                                                                                    |
@@ -28,4 +26,3 @@ The possible values for the `ClientRequestSource` field are the following:
 | `10`  | sslDetector        | A request made by Cloudflare's [SSL Detector system](https://blog.cloudflare.com/ssl-tls-recommender/).                                 |
 | `11`  | earlyHintsCache    | An [Early Hint request](https://blog.cloudflare.com/early-hints/).                                                                      |
 | `12`  | inBrowserChallenge | An end user request caused by a Cloudflare security product (Challenges, JavaScript Detections). These requests never reach the origin. |
-
diff --git a/src/content/docs/logs/reference/index.mdx b/src/content/docs/logs/reference/index.mdx
index 2dee7feaa4467ed..31fafb51510ff9a 100644
--- a/src/content/docs/logs/reference/index.mdx
+++ b/src/content/docs/logs/reference/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 These reference resources are useful for gaining a more in-depth understanding of the terminology and status codes that are part of the Cloudflare Logs data. This information is especially important when integrating your data with third-party tools:
 
diff --git a/src/content/docs/logs/reference/security-fields.mdx b/src/content/docs/logs/reference/security-fields.mdx
index c1dfac2c6154b28..af844e299e4e427 100644
--- a/src/content/docs/logs/reference/security-fields.mdx
+++ b/src/content/docs/logs/reference/security-fields.mdx
@@ -13,8 +13,6 @@ The Security fields contain rules to block requests that contain specific types
 
 ## SecurityActions
 
-
-
 | Value                                  | Action         | Description                                                                                                                                                |
 | -------------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `unknown`                              | Unknown        | Take no other action.                                                                                                                                      |
@@ -27,19 +25,15 @@ The Security fields contain rules to block requests that contain specific types
 | `challengeSolved`                      | Allow          | Allow once interactive challenge solved.                                                                                                                   |
 | `challengeBypassed`                    | Allow          | Interactive challenge is not issued again because the visitor had previously passed an interactive challenge and a valid `cf_clearance` cookie is present. |
 | `jschallengeSolved`                    | Allow          | Allow once non-interactive challenge solved.                                                                                                               |
-| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                  |
+| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                 |
 | `bypass`                               | Allow          | Bypass all subsequent firewall rules.                                                                                                                      |
 | `managedChallenge`                     | Challenge Drop | Issue managed challenge.                                                                                                                                   |
 | `managedChallengeNonInteractiveSolved` | Allow          | Allow once the managed challenge is solved via non-interactive interstitial page.                                                                          |
 | `managedChallengeInteractiveSolved`    | Allow          | Allow once the managed challenged is solved via interactive interstitial page.                                                                             |
 | `managedChallengeBypassed`             | Allow          | Challenge was not presented because visitor had clearance from previous challenge.                                                                         |
 
-
-
 ## SecuritySources
 
-
-
 | Value             | Description                                                                                                      |
 | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
 | `unknown`         | Used if an event is received from a new source but the logging system has not been updated.                      |
diff --git a/src/content/docs/logs/reference/waf-fields.mdx b/src/content/docs/logs/reference/waf-fields.mdx
index 421f434955eb3f0..e53ba194338c1b2 100644
--- a/src/content/docs/logs/reference/waf-fields.mdx
+++ b/src/content/docs/logs/reference/waf-fields.mdx
@@ -13,8 +13,6 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 
 ## WAF Action
 
-
-
 | Value                                      | Action          | Description                                  |
 | ------------------------------------------ | --------------- | -------------------------------------------- |
 | <span style="font-weight: 400;">`0`</span> | Unknown         | Take no other action.                        |
@@ -24,11 +22,9 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 | <span style="font-weight: 400;">`4`</span> | Challenge Drop  | Unused.                                      |
 | <span style="font-weight: 400;">`5`</span> | Log             | Take no action other than logging the event. |
 
-
-
 ## Deprecated fields for internal Cloudflare use
 
 The values of these fields are subject to change by Cloudflare at any time and are irrelevant for customer data analysis:
 
-* WAFFlags
-* WAFMatchedVar
+- WAFFlags
+- WAFMatchedVar
diff --git a/src/content/docs/magic-transit/about.mdx b/src/content/docs/magic-transit/about.mdx
index d24ff959ee90edf..dc0086ba6a2fe2a 100644
--- a/src/content/docs/magic-transit/about.mdx
+++ b/src/content/docs/magic-transit/about.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: About Magic Transit
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Magic Transit is a network security and performance solution that offers Distributed Denial of Service ([DDoS](/ddos-protection/)) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 
diff --git a/src/content/docs/magic-transit/alerts.mdx b/src/content/docs/magic-transit/alerts.mdx
index c0c7de7a4836d78..f8cadf60286d59c 100644
--- a/src/content/docs/magic-transit/alerts.mdx
+++ b/src/content/docs/magic-transit/alerts.mdx
@@ -6,10 +6,9 @@ products:
   - magic-transit
 sidebar:
   order: 14
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your network.
 
diff --git a/src/content/docs/magic-transit/analytics/index.mdx b/src/content/docs/magic-transit/analytics/index.mdx
index 04ca8e61b7d11ce..dfe4e5e0295bb7b 100644
--- a/src/content/docs/magic-transit/analytics/index.mdx
+++ b/src/content/docs/magic-transit/analytics/index.mdx
@@ -13,13 +13,14 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="analytics/overview"
+<Render
+	file="analytics/overview"
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
 		traceRoutes: "/magic-transit/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
-		 }}
-/>
\ No newline at end of file
+		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/",
+	}}
+/>
diff --git a/src/content/docs/magic-transit/analytics/network-analytics.mdx b/src/content/docs/magic-transit/analytics/network-analytics.mdx
index 14e7c6f5b8cbfd3..c872539c3620160 100644
--- a/src/content/docs/magic-transit/analytics/network-analytics.mdx
+++ b/src/content/docs/magic-transit/analytics/network-analytics.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit Network Analytics
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="analytics/network-analytics"
+<Render
+	file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Magic Transit"
+		magicWord: "Magic Transit",
 	}}
 />
diff --git a/src/content/docs/magic-transit/analytics/packet-captures.mdx b/src/content/docs/magic-transit/analytics/packet-captures.mdx
index 0dd8a83c52fb2da..8ef49043b64053d 100644
--- a/src/content/docs/magic-transit/analytics/packet-captures.mdx
+++ b/src/content/docs/magic-transit/analytics/packet-captures.mdx
@@ -7,5 +7,4 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
index e20b8573ade07d3..6f46709874eb1bc 100644
--- a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
+++ b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
@@ -11,9 +11,10 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql"
+<Render
+	file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Magic Transit" }}
 />
diff --git a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
index ec044cf25d36e9c..347e8ce8854d5cd 100644
--- a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
@@ -11,8 +11,10 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="graphql/query-magic-transit-health-checks"
+<Render
+	file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Magic Transit" }} />
+	params={{ productName: "Magic Transit" }}
+/>
diff --git a/src/content/docs/magic-transit/changelog.mdx b/src/content/docs/magic-transit/changelog.mdx
index df426867ae71afe..f3d81cf0accb7be 100644
--- a/src/content/docs/magic-transit/changelog.mdx
+++ b/src/content/docs/magic-transit/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/magic-transit/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="magic-transit" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="magic-transit"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/magic-transit/cloudflare-ips.mdx b/src/content/docs/magic-transit/cloudflare-ips.mdx
index 4ee1316b242c1ab..9812bcc56adb708 100644
--- a/src/content/docs/magic-transit/cloudflare-ips.mdx
+++ b/src/content/docs/magic-transit/cloudflare-ips.mdx
@@ -8,23 +8,26 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="magic-transit/cloudflare-ips"
 	product="networking-services"
 	params={{
 		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
-		mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
-		}} />
+		mtLpStaticRoute:
+			"/magic-transit/how-to/configure-routes/#configure-static-routes",
+		mtLpBgpPeering:
+			"/magic-transit/how-to/configure-routes/#configure-bgp-routes",
+	}}
+/>
 
 ## Check your Cloudflare IPs
 
 <Render
-  file="check-leased-ips"
+	file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "Anycast IPs for Magic Transit"
+		product: "Anycast IPs for Magic Transit",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/get-started.mdx b/src/content/docs/magic-transit/get-started.mdx
index eec224e8dbadd55..8efc46ed319d06b 100644
--- a/src/content/docs/magic-transit/get-started.mdx
+++ b/src/content/docs/magic-transit/get-started.mdx
@@ -10,6 +10,10 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Magic Transit" }} />
\ No newline at end of file
+<Render
+	file="magic-transit/get-started"
+	product="networking-services"
+	params={{ magicWord: "Magic Transit" }}
+/>
diff --git a/src/content/docs/magic-transit/glossary.mdx b/src/content/docs/magic-transit/glossary.mdx
index b14631d9375bd84..089812e9c6ecd3e 100644
--- a/src/content/docs/magic-transit/glossary.mdx
+++ b/src/content/docs/magic-transit/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Magic Transit documentation.
 products:
   - magic-transit
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Magic Transit documentation.
 
diff --git a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
index ec7bc738458e71d..e8f018925c30330 100644
--- a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
+++ b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
@@ -8,7 +8,15 @@ sidebar:
   order: 5
 ---
 
-import { APIRequest, DashButton, Details, GlossaryTooltip, Render, Tabs, TabItem } from "~/components"
+import {
+	APIRequest,
+	DashButton,
+	Details,
+	GlossaryTooltip,
+	Render,
+	Tabs,
+	TabItem,
+} from "~/components";
 
 ## Onboard prefixes
 
@@ -67,11 +75,11 @@ You should only use one control method per prefix at any given time. Mixing mult
 Create a [POST request](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/create/) to add a BGP prefix. For example:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
-  method="POST"
-  json={{
-    "cidr": "192.0.2.0/24"
-  }}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
+	method="POST"
+	json={{
+		cidr: "192.0.2.0/24",
+	}}
 />
 
 ### Advertise or withdraw a BGP prefix
@@ -117,7 +125,7 @@ Refer to [Safely withdraw a BYOIP prefix](#safely-withdraw-a-byoip-prefix) for m
 
 ### Delete an IP prefix
 
-You can only delete a prefix with an *Unapproved* status. To delete prefixes with a different status, contact your administrator or account manager.
+You can only delete a prefix with an _Unapproved_ status. To delete prefixes with a different status, contact your administrator or account manager.
 
 1. Go to the **Routes** page.
 
@@ -137,11 +145,11 @@ BGP has different mechanisms to control route priorities which are set by the pe
 Refer to the following example for how to prepend AS13335 three times to a BGP prefix:
 
 <APIRequest
-path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-method="PATCH"
-json={{
-	"asn_prepend_count": 3
-}}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+	method="PATCH"
+	json={{
+		asn_prepend_count: 3,
+	}}
 />
 
 AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once provides a smoother traffic migration and minimizes packet loss during a change of provider.
@@ -155,8 +163,6 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
 - **Introduce new provider**: You begin advertising the same prefix from your alternate provider with a standard (shorter) `AS_PATH`.
 - **Final state**: External networks now receive two advertisements: the prepended route through Cloudflare and the non-prepended route through your new provider. The external network will select a path based on its BGP policy rules.
 
-
-
 :::caution
 Cloudflare's internal network enforces local preference for traffic delivery to Magic Transit, even if a more specific or shorter path route is available on the public Internet. Withdraw the prefix from Cloudflare to avoid delivery of Cloudflare-sourced traffic over Magic Transit. This preference is local to our internal network and does not impact the route decision process of other networks.
 
@@ -165,27 +171,32 @@ For example, if you have a CDN zone with a Magic Transit-protected origin that i
 
 ## Safely withdraw a BYOIP prefix
 
-<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
+<Render
+	file="magic-transit/safely-withdraw-byoip-prefix"
+	product="networking-services"
+/>
 
 ## BGP control to Magic Transit Virtual Network routing table
 
 ### Automatically announce and withdraw anycast-based Magic BGP routes
 
 If you use CNI with Dataplane v2, GRE or IPsec tunnels, you can:
+
 - Automatically withdraw your prefixes from Cloudflare's global edge infrastructure when you withdraw all matching BGP learned prefixes from the Magic Transit Virtual Network routing table.
 - Automatically advertise your prefixes through Cloudflare's global edge infrastructure when you have at least one matching BGP learned prefix in the Magic Transit Virtual Network routing table.
 
 To enable automatic global announcement and withdrawal, enable this feature on the BGP prefix using the [Addressing API](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/edit/). For example:
 
 <APIRequest
-  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-  method="PATCH"
-  json={{
-    "auto_advertise_withdraw": true
-  }}
+	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+	method="PATCH"
+	json={{
+		auto_advertise_withdraw: true,
+	}}
 />
 
 Once you configure this for a BGP prefix, Cloudflare applies the following logic:
+
 - If there are no BGP routes in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare withdraws the BGP prefix.
 - If there is at least one BGP route in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare announces the BGP prefix.
 
@@ -316,7 +327,10 @@ If you use CNI with Dataplane v2, GRE or IPsec tunnels to on-ramp your network t
 
 Magic Transit supports both static routing and BGP to steer traffic from Cloudflare's network to your configured off-ramps (GRE tunnels, IPsec tunnels, or CNI). Cloudflare does not currently support advertisement of routes for traffic engineering purposes. As a best practice to reduce last-hop latency, consider scoping your routes regionally.
 
-<Render file="reference/traffic-steering-region-codes" product="networking-services" />
+<Render
+	file="reference/traffic-steering-region-codes"
+	product="networking-services"
+/>
 
 The default setting for static route regions is **All Regions**. Configure scoping for your traffic in the **Region code** section when [adding](/magic-transit/how-to/configure-routes/#create-a-static-route) or [editing](/magic-transit/how-to/configure-routes/#edit-a-static-route) a static route.
 
diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx
index c3053044b8b28e3..0dfce207230821b 100644
--- a/src/content/docs/magic-transit/how-to/configure-routes.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx
@@ -11,7 +11,7 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="routing/configure-routes"
@@ -21,12 +21,16 @@ import { Render } from "~/components"
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights:
+			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT:
+			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table"
+		routingTableName: "Magic Transit Virtual Network routing table",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
index af1eee331945798..ab317378e353ddc 100644
--- a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
@@ -14,23 +14,31 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="routing/configure-tunnels"
+<Render
+	file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults:
+			"For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
+		unifiedRoutingURL:
+			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL:
+			"/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
index ccf843678ccbee2..7910debecdaac0e 100644
--- a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
+++ b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
@@ -7,6 +7,6 @@ head: []
 description: You can determine which users have, or do not have, configuration edit access for Magic products.
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="magic-user-role" product="networking-services" />
diff --git a/src/content/docs/magic-transit/how-to/index.mdx b/src/content/docs/magic-transit/how-to/index.mdx
index 962bded34f466cd..a80f260452a9bd5 100644
--- a/src/content/docs/magic-transit/how-to/index.mdx
+++ b/src/content/docs/magic-transit/how-to/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
index b08bce6faedffc0..95d51e29e27e30d 100644
--- a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
@@ -8,6 +8,9 @@ sidebar:
   order: 6
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
\ No newline at end of file
+<Render
+	file="magic-transit/safely-withdraw-byoip-prefix"
+	product="networking-services"
+/>
diff --git a/src/content/docs/magic-transit/network-flow.mdx b/src/content/docs/magic-transit/network-flow.mdx
index 9af74ab7d1573b5..d77808bebde34fe 100644
--- a/src/content/docs/magic-transit/network-flow.mdx
+++ b/src/content/docs/magic-transit/network-flow.mdx
@@ -6,16 +6,15 @@ products:
   - magic-transit
 sidebar:
   order: 10
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
 	}}
 />
diff --git a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
index 99ee9ad379632a8..7218ba148af08d2 100644
--- a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
@@ -14,11 +14,13 @@ import { Render } from "~/components";
 	file="tunnel-health/check-tunnel-healthchecks-dash"
 	product="networking-services"
 	params={{
-		dashInfo: "The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
+		dashInfo:
+			"The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
 		graphQL: "/magic-transit/analytics/query-tunnel-health/",
-		notificationsPath: "[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
+		notificationsPath:
+			"[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/magic-transit/analytics/network-analytics/"
+		networkAnalytics: "/magic-transit/analytics/network-analytics/",
 	}}
 />
 
@@ -26,7 +28,7 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
 />
 
@@ -34,4 +36,4 @@ import { Render } from "~/components";
 
 If you received a tunnel health alert but are unsure whether it affects your traffic, refer to [Troubleshoot connectivity](/magic-transit/troubleshooting/connectivity/) to determine whether the alert is relevant.
 
-If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
\ No newline at end of file
+If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
diff --git a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
index d606ec4dcd288b1..32dcf34acba8937 100644
--- a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation:
+			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/network-health/index.mdx b/src/content/docs/magic-transit/network-health/index.mdx
index 909456bebc21630..ac18e64e89dac4c 100644
--- a/src/content/docs/magic-transit/network-health/index.mdx
+++ b/src/content/docs/magic-transit/network-health/index.mdx
@@ -8,23 +8,23 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Magic Transit uses health check probes to determine the status of tunnels. Cloudflare uses this information to steer traffic through the best available route and warn you about potential issues with a tunnel. Service-level indicators (SLIs) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [How Cloudflare calculates tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/) for more information about SLIs and SLOs.
 
 There are two types of health checks available: endpoint and tunnel health checks.
 
- - Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
+- Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
 
-	Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
+  Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
 
-	During onboarding, you specify IP addresses to configure endpoint health checks.
+  During onboarding, you specify IP addresses to configure endpoint health checks.
 
 - Tunnel health checks monitor the status of the tunnels that route traffic from Cloudflare to your origin network. Magic Transit relies on health checks to steer traffic to the best available routes.
 
-	During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
+  During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
 
-	You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
+  You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
 
 Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/) for a deep dive into the different types of health checks, what they do, and how they work.
 
@@ -32,10 +32,10 @@ Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/)
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
 />
 
 Refer to the following pages for details on how to use the various network health checks available.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
index b734e7357208bff..3fedb7f8c2cb1a3 100644
--- a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
+++ b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
@@ -14,7 +14,7 @@ tags:
   - ICMP
 ---
 
-import { CURL, Render, DashButton } from '~/components';
+import { CURL, Render, DashButton } from "~/components";
 
 Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
 
@@ -43,32 +43,35 @@ Refer to the [API documentation](/api/resources/diagnostics/subresources/endpoin
 <Render file="account-id-api-key" product="networking-services" />
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-  method="POST"
-  json={{
-    "check_type": "icmp",
-    "endpoint": "8.31.160.1",
-    "name": "Datacenter 1 - primary"
-  }}
+	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+	method="POST"
+	json={{
+		check_type: "icmp",
+		endpoint: "8.31.160.1",
+		name: "Datacenter 1 - primary",
+	}}
 />
 
 ```json output
 {
-    "result": {
-        "id": "<HEALTH_CHECK_ID>",
-        "check_type": "icmp",
-        "endpoint": "8.31.160.1",
-        "name": "Datacenter 1 - primary"
-    },
-    "success": true,
-    "errors": [],
-    "messages": []
+	"result": {
+		"id": "<HEALTH_CHECK_ID>",
+		"check_type": "icmp",
+		"endpoint": "8.31.160.1",
+		"name": "Datacenter 1 - primary"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Query endpoint health checks with GraphQL
 
-<Render file="graphql/query-magic-transit-endpoint-health-checks" product="networking-services" />
+<Render
+	file="graphql/query-magic-transit-endpoint-health-checks"
+	product="networking-services"
+/>
 
 ## Configure alerts for endpoint health checks
 
@@ -77,23 +80,23 @@ You can set up alerts to be notified when the state of your endpoint's health is
 1. Make a `GET` request to get a list of IDs for all of the endpoint health checks configured:
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-  method="GET"
+	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+	method="GET"
 />
 
 ```json output
 {
-    "result": [
-        {
-            "id": "<HEALTH_CHECK_ID>",
-            "check_type": "icmp",
-            "endpoint": "8.31.160.1",
-            "name": "Datacenter 1 - primary"
-        }
-    ],
-    "success": true,
-    "errors": [],
-    "messages": []
+	"result": [
+		{
+			"id": "<HEALTH_CHECK_ID>",
+			"check_type": "icmp",
+			"endpoint": "8.31.160.1",
+			"name": "Datacenter 1 - primary"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -103,13 +106,13 @@ You can set up alerts to be notified when the state of your endpoint's health is
 <DashButton url="/?to=/:account/notifications" />
 
 4. Select **Add**.
-5. From the drop-down menu, select *Magic Transit*.
+5. From the drop-down menu, select _Magic Transit_.
 6. Select **Magic Endpoint Health Check Alert**.
 7. Provide a name for your new notification and optionally provide a description.
-8. In the *Service Level Objective (SLO)* drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
-	- **High** - 99%
-	- **Medium** - 98%
-	- **Low** - 97%
+8. In the _Service Level Objective (SLO)_ drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
+   - **High** - 99%
+   - **Medium** - 98%
+   - **Low** - 97%
 9. In the drop-down menu below SLOs, select the `id` value that matches the `id` you got through the API in step 1. This `id` should match the endpoint health check you want to get notifications for.
 10. Select your preferred notification method (such as email or webhooks).
 11. Select **Save**.
diff --git a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
index 5abf823c7864447..cc01a8092fae660 100644
--- a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
@@ -17,7 +17,8 @@ import { Render } from "~/components";
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",
-		addTunnelsPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels"
+		addTunnelsPath:
+			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
@@ -25,6 +26,6 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit"
+		productName: "Magic Transit",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/magic-transit/network-interconnect.mdx b/src/content/docs/magic-transit/network-interconnect.mdx
index 44619ba947f13ef..d9cb97232b3510b 100644
--- a/src/content/docs/magic-transit/network-interconnect.mdx
+++ b/src/content/docs/magic-transit/network-interconnect.mdx
@@ -13,4 +13,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" />
\ No newline at end of file
+<Render file="magic-cni" product="networking-services" />
diff --git a/src/content/docs/magic-transit/on-demand.mdx b/src/content/docs/magic-transit/on-demand.mdx
index 019f50728fcda3c..75c387b34768ef6 100644
--- a/src/content/docs/magic-transit/on-demand.mdx
+++ b/src/content/docs/magic-transit/on-demand.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit on-demand
-
 ---
 
 If you have access to the Magic Transit on-demand option, you can [configure prefix advertisement](/byoip/concepts/dynamic-advertisement/best-practices/#configure-dynamic-advertisement) from the **IP Prefixes** page in your Cloudflare account home or through the [Cloudflare API](/api/resources/addressing/subresources/prefixes/subresources/advertisement_status/methods/edit/).
diff --git a/src/content/docs/magic-transit/partners/index.mdx b/src/content/docs/magic-transit/partners/index.mdx
index bfd05db0b774788..6ee348692df331a 100644
--- a/src/content/docs/magic-transit/partners/index.mdx
+++ b/src/content/docs/magic-transit/partners/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 15
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
index 7bc128098d8f68c..535769eb632525c 100644
--- a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
+++ b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
@@ -18,7 +18,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
-		productPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		productPath:
+			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
index 6b1bfa5d9f79f7f..dc972d88c678590 100644
--- a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
@@ -22,12 +22,13 @@ import { Render } from "~/components";
 		mssURL: "/magic-transit/get-started/#set-maximum-segment-size",
 		productURL: "/magic-transit/reference/anti-replay-protection/",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		magicWord: "Magic Transit"
+		magicWord: "Magic Transit",
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
+
 - [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/magic-transit/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 1fba89abfb6a2f8..f9fbf42cffa7459 100644
--- a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,9 +8,12 @@ sidebar:
   order: 9
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="reference/magic-tunnels-slos"
+<Render
+	file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down" }}
+	params={{
+		tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down",
+	}}
 />
diff --git a/src/content/docs/magic-transit/reference/index.mdx b/src/content/docs/magic-transit/reference/index.mdx
index 19ff0a30a962cbc..fe0a8581aa501bb 100644
--- a/src/content/docs/magic-transit/reference/index.mdx
+++ b/src/content/docs/magic-transit/reference/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 16
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/reference/mtu-mss.mdx b/src/content/docs/magic-transit/reference/mtu-mss.mdx
index aea2b11b3a8ca3a..c35b312d04d675d 100644
--- a/src/content/docs/magic-transit/reference/mtu-mss.mdx
+++ b/src/content/docs/magic-transit/reference/mtu-mss.mdx
@@ -20,6 +20,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
-		productName: "Magic Transit"
-		}}
+		productName: "Magic Transit",
+	}}
 />
diff --git a/src/content/docs/magic-transit/reference/traffic-steering.mdx b/src/content/docs/magic-transit/reference/traffic-steering.mdx
index 6343ed66f6690f6..3864fa3d06c3f68 100644
--- a/src/content/docs/magic-transit/reference/traffic-steering.mdx
+++ b/src/content/docs/magic-transit/reference/traffic-steering.mdx
@@ -22,7 +22,8 @@ import { Render } from "~/components";
 		routingTableName: "Magic Transit Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
index cc8c425a16b925c..9f4b6435299ad5a 100644
--- a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
@@ -20,11 +20,12 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		addTunnels: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		changeHealthCheckRate:
+			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
 		staticRoutes: "/magic-transit/how-to/configure-routes/",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/"
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
index ff5293328e0537b..bc19d9e2ed3a087 100644
--- a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
@@ -17,8 +17,9 @@ import { Render } from "~/components";
 		productName: "Magic Transit",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
 		routingBgpLink: "/magic-transit/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		checkHealthDashLink:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
 	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/index.mdx b/src/content/docs/magic-transit/troubleshooting/index.mdx
index 6487eea738df77b..24dc284181dfdf0 100644
--- a/src/content/docs/magic-transit/troubleshooting/index.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/index.mdx
@@ -12,6 +12,6 @@ tags:
   - Debugging
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
index bacfef32c5f77a3..3ad6b0cbb6091ce 100644
--- a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
@@ -12,15 +12,17 @@ tags:
   - Logging
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="ipsec-logs-troubleshooting"
+<Render
+	file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		mtuMssLink: "/magic-transit/reference/mtu-mss/"
+		mtuMssLink: "/magic-transit/reference/mtu-mss/",
 	}}
 />
 
@@ -29,6 +31,7 @@ import { Render } from "~/components"
 Some customer routers cannot fully disable IPsec anti-replay protection, which is required for optimal Magic Transit operation (packet reordering at the Cloudflare edge can otherwise trigger false drops).
 
 **If your router does not support disabling anti-replay:**
+
 1. Check whether your router supports configuring a **replay window size**. Setting this to `0` is equivalent to disabling anti-replay protection.
 2. If neither disabling anti-replay nor setting the window size to `0` is supported, **the router cannot be used as a Magic Transit IPsec on-ramp**. Consider using a GRE tunnel or Cloudflare Network Interconnect (CNI) instead.
 
@@ -41,4 +44,3 @@ If your ISP is blocking these response packets, health checks will fail even whe
 **Symptom:** Health checks fail but application traffic flows normally through the tunnel.
 
 **Resolution:** Switch to bidirectional health checks, which send both the probe and the response through the tunnel. Bidirectional health checks require egress traffic to be turned on for your Magic Transit configuration. For more information, refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/).
-
diff --git a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
index d207cbb1af0bab8..43b9bb867569e75 100644
--- a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
@@ -11,14 +11,15 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="troubleshoot-routing-bgp"
-  product="networking-services"
-  params={{
-    magicWord: "Magic Transit",
-    productName: "Magic Transit",
-    trafficSteeringLink: "/magic-transit/reference/traffic-steering/#route-prioritization",
-    configureRoutesLink: "/magic-transit/how-to/configure-routes/",
-    tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
-  }}
+	file="troubleshoot-routing-bgp"
+	product="networking-services"
+	params={{
+		magicWord: "Magic Transit",
+		productName: "Magic Transit",
+		trafficSteeringLink:
+			"/magic-transit/reference/traffic-steering/#route-prioritization",
+		configureRoutesLink: "/magic-transit/how-to/configure-routes/",
+		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
index 1f0887e6040a0f8..747fc6d131cd7b6 100644
--- a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
@@ -14,17 +14,20 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel-health/troubleshoot-tunnel-health"
-  product="networking-services"
-  params={{
-    productName: "Magic Transit",
-    healthCheckDefault: "_Unidirectional_ (direct server return)",
-    tunnelsConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-    checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
-    antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
-    tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-    configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
-    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-    supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
-  }}
+	file="tunnel-health/troubleshoot-tunnel-health"
+	product="networking-services"
+	params={{
+		productName: "Magic Transit",
+		healthCheckDefault: "_Unidirectional_ (direct server return)",
+		tunnelsConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		checkHealthDashLink:
+			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
+		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
+		configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+		supportedIpsecConfigLink:
+			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+	}}
 />
diff --git a/src/content/docs/moq/feature-matrix.mdx b/src/content/docs/moq/feature-matrix.mdx
index 200715e6e3a4ba2..92148c292bc4988 100644
--- a/src/content/docs/moq/feature-matrix.mdx
+++ b/src/content/docs/moq/feature-matrix.mdx
@@ -3,81 +3,80 @@ pcx_content_type: get-started
 title: MoQ Feature Matrix
 sidebar:
   order: 18
-
 ---
 
 ## Draft-14 Messages
 
 ### Supported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_CANCEL | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message                            | Support | Relevant specification                                                                           |
+| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_CANCEL           | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_OK               | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_ERROR            | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_OK                         | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE                  | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_DONE             | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_DONE                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_OK                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ### Unsupported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| GOAWAY | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| MAX_REQUEST_ID | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| REQUESTS_BLOCKED | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_CANCEL | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message                   | Support | Relevant specification                                                                           |
+| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| GOAWAY                    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| MAX_REQUEST_ID            | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| REQUESTS_BLOCKED          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_ERROR             | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH                     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_OK                  | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_ERROR               | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_ERROR        | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE       | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_OK    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_ERROR | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE_NAMESPACE     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ## Draft-07 Messages
 
 ### Supported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| ANNOUNCE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_CANCEL | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS_REQUEST | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_DONE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| MAX_SUBSCRIBE_ID | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message                            | Support | Relevant specification                                                                           |
+| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| ANNOUNCE_OK                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_ERROR                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_CANCEL                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS_REQUEST               | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE                           | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNANNOUNCE                         | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_DONE                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| MAX_SUBSCRIBE_ID                   | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
 
 ### Unsupported
 
-| Message | Support | Relevant specification |
-| ------- | ------- | ---------------------- |
-| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| GOAWAY | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_CANCEL | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message                   | Support | Relevant specification                                                                           |
+| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
+| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| GOAWAY                    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES       | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_OK    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_ERROR | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE_ANNOUNCES     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH                     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_OK                  | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_ERROR               | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
diff --git a/src/content/docs/moq/index.mdx b/src/content/docs/moq/index.mdx
index 838ca1c7516741e..d02f8400089cf48 100644
--- a/src/content/docs/moq/index.mdx
+++ b/src/content/docs/moq/index.mdx
@@ -22,7 +22,7 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Frequently Asked Questions
 
-* What about Safari?
+- What about Safari?
 
   Safari does not yet have fully functional WebTransport support. Apple never publicly commits to timelines for new features like this. However, Apple has indicated their [intent to support WebTransport](https://github.com/WebKit/standards-positions/issues/18#issuecomment-1495890122). An Apple employee is even a co-author of the [WebTransport over HTTP/3](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/) draft. Since Safari 18.4 (2025-03-31), an early (not yet fully functional) implementation of the WebTransport API has been available for testing behind a developer-mode / advanced settings feature flag (including on iOS).
 
@@ -30,12 +30,12 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Known Issues
 
-* Extra Subgroup header field
+- Extra Subgroup header field
+
+  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits.
 
-  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits. 
-  
   In section 7.3.1, `draft-ietf-moq-transport-07` [specifies](https://www.ietf.org/archive/id/draft-ietf-moq-transport-07.html#section-7.3.1):
-  
+
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Track Alias (i),
@@ -44,8 +44,9 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-  
+
   Whereas our implementation expects and produces:
+
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Subscribe ID (i),
@@ -55,5 +56,5 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-  
+
   This was erroroneously left over from a previous draft version and will be fixed in a future release. Thank you to [@yuki-uchida](https://github.com/yuki-uchida) for reporting.
diff --git a/src/content/docs/multi-cloud-networking/changelog.mdx b/src/content/docs/multi-cloud-networking/changelog.mdx
index 4374533a030deb1..4bbf7ded14ca757 100644
--- a/src/content/docs/multi-cloud-networking/changelog.mdx
+++ b/src/content/docs/multi-cloud-networking/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/multi-cloud-networking/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="multi-cloud-networking" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="multi-cloud-networking"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-11-21
 
diff --git a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
index d388a38c069f08b..d20a8425820479e 100644
--- a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
+++ b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
@@ -6,12 +6,15 @@ products:
 title: Cloud on-ramps
 sidebar:
   order: 3
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="routing/mcn-cloudflare-wan-on-ramps"
+<Render
+	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
-	params={{ mwanAccount: "Have a Cloudflare WAN account. Contact your account team to learn more." }}
+	params={{
+		mwanAccount:
+			"Have a Cloudflare WAN account. Contact your account team to learn more.",
+	}}
 />
diff --git a/src/content/docs/multi-cloud-networking/get-started.mdx b/src/content/docs/multi-cloud-networking/get-started.mdx
index 04c91b1108e2aa5..ef3448467003242 100644
--- a/src/content/docs/multi-cloud-networking/get-started.mdx
+++ b/src/content/docs/multi-cloud-networking/get-started.mdx
@@ -25,7 +25,7 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 1. Go to the **Cloud integrations (beta)** page.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **AWS integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -38,29 +38,29 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 ```json
 {
-    "Version": "2012-10-17",
-    "Statement": [
-        {
-            "Effect": "Allow",
-            "Action": [
-                "ec2:AcceptTransitGatewayPeeringAttachment",
-                "ec2:CreateTransitGatewayPeeringAttachment",
-                "ec2:DeleteTransitGatewayPeeringAttachment",
-                "ec2:DescribeRegions",
-                "ec2:DescribeTransitGatewayPeeringAttachments",
-                "ec2:RejectTransitGatewayPeeringAttachment",
-                "ec2:GetManagedPrefixListEntries",
-                "ec2:CreateManagedPrefixList",
-                "ec2:ModifyManagedPrefixList",
-                "ec2:DeleteManagedPrefixList",
-                "ec2:CreateTransitGatewayPrefixListReference",
-                "ec2:DeleteTransitGatewayPrefixListReference",
-                "ec2:GetTransitGatewayPrefixListReferences",
-                "ec2:ModifyTransitGatewayPrefixListReference"
-            ],
-            "Resource": "*"
-        }
-    ]
+	"Version": "2012-10-17",
+	"Statement": [
+		{
+			"Effect": "Allow",
+			"Action": [
+				"ec2:AcceptTransitGatewayPeeringAttachment",
+				"ec2:CreateTransitGatewayPeeringAttachment",
+				"ec2:DeleteTransitGatewayPeeringAttachment",
+				"ec2:DescribeRegions",
+				"ec2:DescribeTransitGatewayPeeringAttachments",
+				"ec2:RejectTransitGatewayPeeringAttachment",
+				"ec2:GetManagedPrefixListEntries",
+				"ec2:CreateManagedPrefixList",
+				"ec2:ModifyManagedPrefixList",
+				"ec2:DeleteManagedPrefixList",
+				"ec2:CreateTransitGatewayPrefixListReference",
+				"ec2:DeleteTransitGatewayPrefixListReference",
+				"ec2:GetTransitGatewayPrefixListReferences",
+				"ec2:ModifyTransitGatewayPrefixListReference"
+			],
+			"Resource": "*"
+		}
+	]
 }
 ```
 
@@ -69,15 +69,15 @@ Once Cloudflare has the credentials required to access your cloud environments,
 1. Create an [AWS role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html) with the following settings:
    - **Trusted entity type**: Select **Custom trust policy**, and paste the custom trust policy returned by the Cloudflare dashboard.
    - **Permissions**: Add the IAM policy you created in the previous step, along with these AWS-managed policies:
-      - `NetworkAdministrator`
-      - `AmazonEC2ReadOnlyAccess`
-      - `AmazonVPCReadOnlyAccess`
-      - `IAMReadOnlyAccess`
+     - `NetworkAdministrator`
+     - `AmazonEC2ReadOnlyAccess`
+     - `AmazonVPCReadOnlyAccess`
+     - `IAMReadOnlyAccess`
    - **ARN**: Copy the ARN for your newly created user.
 
    :::note
-	 The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-	 :::
+   The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+   :::
 
 2. Select **I authorize Cloudflare to access my AWS account.**
 3. Select **Authorize**.
@@ -92,7 +92,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Azure integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -115,8 +115,8 @@ Multi-Cloud Networking does not support personal Microsoft accounts. Sign in usi
 6. In **Verify account ownership**, [add the tags displayed in the Cloudflare dashboard](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources-portal).
 
    :::note
-	 The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-	 :::
+   The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+   :::
 
 7. Select **I authorize Cloudflare to access my Azure account.** If your account does not have administrator privileges, you may need to pass this link to an account that has administrator privileges.
 8. Select **Authorize**.
@@ -131,7 +131,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Google integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -142,8 +142,8 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. Create a new [GCP service account](https://cloud.google.com/iam/docs/service-accounts-create) in your **Google account** > **GCP Console** > **IAM & Admin** > **Service Accounts**.
 2. Grant the new service account these roles:
-	- `Compute Network Admin`
-	- `Compute Viewer`
+   - `Compute Network Admin`
+   - `Compute Viewer`
 3. Under **IAM & Admin** > **Service Accounts**, select the service account you just created, and navigate to the **Permissions** tab.
 4. Grant the **Service Account Token Creator** role to our bot account to allow it to impersonate this service account. Learn how to grant a specific role [in Google's documentation](https://cloud.google.com/iam/docs/manage-access-service-accounts#grant-single-role):
    - `mcn-integrations-bot-prod@mcn-gcp-01.iam.gserviceaccount.com`
@@ -163,4 +163,4 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 - [Set up Cloudflare WAN](/multi-cloud-networking/cloud-on-ramps/) as an on-ramp to your cloud.
 - [Manage resources](/multi-cloud-networking/manage-resources/) found by Multi-Cloud Networking.
-- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
\ No newline at end of file
+- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
diff --git a/src/content/docs/multi-cloud-networking/manage-resources.mdx b/src/content/docs/multi-cloud-networking/manage-resources.mdx
index 4307d7b9da2de5c..b9eb3e0bc385769 100644
--- a/src/content/docs/multi-cloud-networking/manage-resources.mdx
+++ b/src/content/docs/multi-cloud-networking/manage-resources.mdx
@@ -6,7 +6,6 @@ products:
 title: Manage resources
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,7 @@ To browse the resources in your catalog:
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select a resource to inspect its details.
@@ -30,7 +29,7 @@ You can change which cloud account the integration is linked to or delete the in
 
 1. Go to **Cloud integrations**.
 
-	<DashButton url="/?to=/:account/mcn/integrations" />
+   <DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select your integration > **Edit**.
 3. In **Linked account details**, select **Link integration to a different cloud account**.
@@ -43,7 +42,7 @@ You can download a JSON file containing metadata and configuration for all your
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select **Download catalog**.
diff --git a/src/content/docs/multi-cloud-networking/reference.mdx b/src/content/docs/multi-cloud-networking/reference.mdx
index 8c37c24b0eabb74..16d0b78776c4c47 100644
--- a/src/content/docs/multi-cloud-networking/reference.mdx
+++ b/src/content/docs/multi-cloud-networking/reference.mdx
@@ -6,7 +6,6 @@ products:
 title: Reference
 sidebar:
   order: 5
-
 ---
 
 Refer to this page for details about how Cloudflare orchestrates VPN connectivity to your cloud networks.
diff --git a/src/content/docs/network-error-logging/get-started.mdx b/src/content/docs/network-error-logging/get-started.mdx
index e211ba22e5e901a..2b07fd6d29a8e84 100644
--- a/src/content/docs/network-error-logging/get-started.mdx
+++ b/src/content/docs/network-error-logging/get-started.mdx
@@ -6,7 +6,6 @@ products:
   - network-error-logging
 tags:
   - Logging
-
 ---
 
 import { DashButton } from "~/components";
@@ -17,7 +16,7 @@ To enable Network Error Logging for Free and Pro zones:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Network** and locate **Network Error Logging Monitoring**.
 3. Select the toggle to enable Network Error Logging.
diff --git a/src/content/docs/network-error-logging/how-to.mdx b/src/content/docs/network-error-logging/how-to.mdx
index 6aac695c1d00025..74f33f4e7eeadff 100644
--- a/src/content/docs/network-error-logging/how-to.mdx
+++ b/src/content/docs/network-error-logging/how-to.mdx
@@ -11,21 +11,20 @@ head:
 description: NEL reports show you why a request failed, the country a request
   failed from, and last mile network a request failed from, and the likely
   intended Cloudflare data center.
-
 ---
 
 import { DashButton } from "~/components";
 
 Use NEL reports to view information such as:
 
-* Why a request failed
-* The country a request failed from
-* The last mile network a request failed from
-* The Cloudflare data center the request was most likely meant for
+- Why a request failed
+- The country a request failed from
+- The last mile network a request failed from
+- The Cloudflare data center the request was most likely meant for
 
 1. Log in to your Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select **Analytics & Logs** > **Edge Reachability**.
 
diff --git a/src/content/docs/network-error-logging/index.mdx b/src/content/docs/network-error-logging/index.mdx
index b712cac7782fb54..9f1acd04e344ba5 100644
--- a/src/content/docs/network-error-logging/index.mdx
+++ b/src/content/docs/network-error-logging/index.mdx
@@ -34,21 +34,21 @@ A sample Network Error Report payload appears as follows:
 
 ```json
 {
-  "age": 20,
-  "type": "network-error",
-  "url": "https://example.com/previous-page",
-  "body": {
-    "elapsed_time": 18,
-    "method": "POST",
-    "phase": "dns",
-    "protocol": "http/1.1",
-    "referrer": "https://example.com/previous-page",
-    "sampling_fraction": 1,
-    "server_ip": "",
-    "status_code": 0,
-    "type": "dns.name_not_resolved",
-    "url": "https://example-host.com/"
-  }
+	"age": 20,
+	"type": "network-error",
+	"url": "https://example.com/previous-page",
+	"body": {
+		"elapsed_time": 18,
+		"method": "POST",
+		"phase": "dns",
+		"protocol": "http/1.1",
+		"referrer": "https://example.com/previous-page",
+		"sampling_fraction": 1,
+		"server_ip": "",
+		"status_code": 0,
+		"type": "dns.name_not_resolved",
+		"url": "https://example-host.com/"
+	}
 }
 ```
 
@@ -56,9 +56,9 @@ A sample Network Error Report payload appears as follows:
 
 Cloudflare uses geolocation lookups to extract the following information from every client IP in a NEL report:
 
-* Client ASN
-* Client country
-* Client metro area
+- Client ASN
+- Client country
+- Client metro area
 
 Cloudflare uses internal lookups to associate the above data with a customer domain and customer account.
 
@@ -67,9 +67,10 @@ Cloudflare does not store any PII or user-specific data, and any IP data is only
 The client IP address is only stored in volatile memory for the lifetime of the request to Cloudflare’s NEL endpoint (order of milliseconds) and is dropped immediately after the request completes. Cloudflare does not log the client IP address anywhere in the Network Error Logging pipeline.
 
 NEL reports contain information about the end user's network conditions, which could be considered sensitive. Cloudflare takes privacy seriously and has implemented the following safeguards:
-* Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
-* Reports do not contain personally identifiable information (PII).
-* Customers can opt out of having their end users consume the NEL headers using one of the following methods:
+
+- Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
+- Reports do not contain personally identifiable information (PII).
+- Customers can opt out of having their end users consume the NEL headers using one of the following methods:
   1. **Self-service (Zone setting)** — Use the dashboard toggle or API (`PATCH /zones/{zone_id}/settings/nel`) to disable NEL for your zone. This can be re-enabled by any zone administrator at any time.
   2. **Permanent opt-out via Support** — Contact Cloudflare support to have the `nel___enable` feature flag disabled at the product level. This prevents NEL from being enabled on your zone entirely and cannot be reversed by zone administrators.
-For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
+     For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
diff --git a/src/content/docs/network-flow/api.mdx b/src/content/docs/network-flow/api.mdx
index abedf0335eb08a4..86093e48a9529bf 100644
--- a/src/content/docs/network-flow/api.mdx
+++ b/src/content/docs/network-flow/api.mdx
@@ -6,9 +6,8 @@ products:
   - network-flow
 sidebar:
   order: 9
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mnm/api" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/api" product="networking-services" />
diff --git a/src/content/docs/network-flow/changelog.mdx b/src/content/docs/network-flow/changelog.mdx
index b94beaa04726a51..c0a384cb7ba3378 100644
--- a/src/content/docs/network-flow/changelog.mdx
+++ b/src/content/docs/network-flow/changelog.mdx
@@ -13,4 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-flow/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="network-flow" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="network-flow"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
diff --git a/src/content/docs/network-flow/cloud-flow-logs.mdx b/src/content/docs/network-flow/cloud-flow-logs.mdx
index b3b71aa0230d535..1f7b9357b839a4c 100644
--- a/src/content/docs/network-flow/cloud-flow-logs.mdx
+++ b/src/content/docs/network-flow/cloud-flow-logs.mdx
@@ -16,4 +16,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/cloud-flow-logs" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/cloud-flow-logs" product="networking-services" />
diff --git a/src/content/docs/network-flow/faq.mdx b/src/content/docs/network-flow/faq.mdx
index 83e76018f873f71..7f18175619785c3 100644
--- a/src/content/docs/network-flow/faq.mdx
+++ b/src/content/docs/network-flow/faq.mdx
@@ -11,6 +11,6 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="mnm/faqs" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/faqs" product="networking-services" />
diff --git a/src/content/docs/network-flow/get-started.mdx b/src/content/docs/network-flow/get-started.mdx
index 8129f8e3bb7ce5a..4c52c7365d5e149 100644
--- a/src/content/docs/network-flow/get-started.mdx
+++ b/src/content/docs/network-flow/get-started.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/get-started" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/get-started" product="networking-services" />
diff --git a/src/content/docs/network-flow/glossary.mdx b/src/content/docs/network-flow/glossary.mdx
index 560fd3884273263..3000aa1c392cf88 100644
--- a/src/content/docs/network-flow/glossary.mdx
+++ b/src/content/docs/network-flow/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - network-flow
 sidebar:
   order: 10
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Network Flow (formerly Magic Network Monitoring) documentation.
 
diff --git a/src/content/docs/network-flow/magic-transit-integration.mdx b/src/content/docs/network-flow/magic-transit-integration.mdx
index 8defa83ac2a41fc..0b4ac3859f62b97 100644
--- a/src/content/docs/network-flow/magic-transit-integration.mdx
+++ b/src/content/docs/network-flow/magic-transit-integration.mdx
@@ -8,16 +8,15 @@ tags:
   - Integration
 sidebar:
   order: 7
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
 	}}
 />
diff --git a/src/content/docs/network-flow/network-flow-free.mdx b/src/content/docs/network-flow/network-flow-free.mdx
index ca7198f7f03d8fe..645bf56f6cb3a17 100644
--- a/src/content/docs/network-flow/network-flow-free.mdx
+++ b/src/content/docs/network-flow/network-flow-free.mdx
@@ -11,6 +11,6 @@ head:
     content: Network Flow free version
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="mnm/network-flow-free" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/index.mdx b/src/content/docs/network-flow/routers/index.mdx
index dc7bb414eb48ca9..476c0017b240362 100644
--- a/src/content/docs/network-flow/routers/index.mdx
+++ b/src/content/docs/network-flow/routers/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
index 3d1f2222d0b7878..58e65c53add4e60 100644
--- a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
+++ b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
@@ -11,9 +11,8 @@ sidebar:
 head: []
 description: A step-by-step configuration guide for exporting NetFlow or IPFIX
   data to Cloudflare's network.
-
 ---
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
index 82158fe7ad97cf0..b8cd99b68ae977e 100644
--- a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
+++ b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
@@ -9,7 +9,6 @@ sidebar:
   order: 2
 head: []
 description: The best sampling rate recommendations for your network's traffic volume.
-
 ---
 
 import { Render } from "~/components";
@@ -17,4 +16,4 @@ import { Render } from "~/components";
 <Render
 	file="mnm/routers/recommended-sampling-rate"
 	product="networking-services"
-	/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/network-flow/routers/sflow-config.mdx b/src/content/docs/network-flow/routers/sflow-config.mdx
index ee37c4c868a8ac4..5b7ba843d316df0 100644
--- a/src/content/docs/network-flow/routers/sflow-config.mdx
+++ b/src/content/docs/network-flow/routers/sflow-config.mdx
@@ -14,7 +14,4 @@ description: A step-by-step configuration guide for exporting sFlow data to
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/routers/sflow-config"
-	product="networking-services"
-	/>
\ No newline at end of file
+<Render file="mnm/routers/sflow-config" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/supported-routers.mdx b/src/content/docs/network-flow/routers/supported-routers.mdx
index 45a57d81dc9d9a9..410865594728185 100644
--- a/src/content/docs/network-flow/routers/supported-routers.mdx
+++ b/src/content/docs/network-flow/routers/supported-routers.mdx
@@ -13,7 +13,4 @@ description: A list of open source, NetFlow, and sFlow routers.
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/routers/supported-routers"
-	product="networking-services"
-	/>
\ No newline at end of file
+<Render file="mnm/routers/supported-routers" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/index.mdx b/src/content/docs/network-flow/rules/index.mdx
index ef9d83a02553c40..ff541e592e5802a 100644
--- a/src/content/docs/network-flow/rules/index.mdx
+++ b/src/content/docs/network-flow/rules/index.mdx
@@ -14,4 +14,3 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="mnm/rules/overview" product="networking-services" />
-
diff --git a/src/content/docs/network-flow/rules/rule-notifications.mdx b/src/content/docs/network-flow/rules/rule-notifications.mdx
index 0f85c34f0e1fd3d..cfc447c89cb41dd 100644
--- a/src/content/docs/network-flow/rules/rule-notifications.mdx
+++ b/src/content/docs/network-flow/rules/rule-notifications.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/rule-notifications" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/rule-notifications" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
index 9dfff3f061f5c5d..34d38296b6570d4 100644
--- a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
+++ b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
diff --git a/src/content/docs/network-flow/rules/static-threshold.mdx b/src/content/docs/network-flow/rules/static-threshold.mdx
index 172ca611aa68db2..fa5fca21e7cef6f 100644
--- a/src/content/docs/network-flow/rules/static-threshold.mdx
+++ b/src/content/docs/network-flow/rules/static-threshold.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/static-threshold" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/rules/static-threshold" product="networking-services" />
diff --git a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
index 0b0bb68e1ebbc8d..d43167ed7936fd7 100644
--- a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
+++ b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
@@ -15,4 +15,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
\ No newline at end of file
+<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
diff --git a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
index f7562708d10bd0d..8b86d643dd5ade2 100644
--- a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
+++ b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
@@ -19,4 +19,7 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/encrypt-network-flow-data" product="networking-services" />
\ No newline at end of file
+<Render
+	file="mnm/tutorials/encrypt-network-flow-data"
+	product="networking-services"
+/>
diff --git a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
index 00c00c094490f32..26f062040cac4f3 100644
--- a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
+++ b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
@@ -20,4 +20,4 @@ import { Render } from "~/components";
 
 <Render file="mnm/tutorials/graphql-analytics" product="networking-services" />
 
-<Render file="case-sensitivity-note" product="analytics" />
\ No newline at end of file
+<Render file="case-sensitivity-note" product="analytics" />
diff --git a/src/content/docs/network-flow/tutorials/index.mdx b/src/content/docs/network-flow/tutorials/index.mdx
index 8fae75e32ca4f24..a13ee6bc966bfd7 100644
--- a/src/content/docs/network-flow/tutorials/index.mdx
+++ b/src/content/docs/network-flow/tutorials/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/network-interconnect/changelog.mdx b/src/content/docs/network-interconnect/changelog.mdx
index 5b15e2c668e23f3..64c3877fd409947 100644
--- a/src/content/docs/network-interconnect/changelog.mdx
+++ b/src/content/docs/network-interconnect/changelog.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-interconnect/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog product="network-interconnect" hideEntry="2024-06-16-cloudflare-one"/>
+<ProductChangelog
+	product="network-interconnect"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx
index 16c0b376aa76fb9..daba42777661fd5 100644
--- a/src/content/docs/network-interconnect/get-started.mdx
+++ b/src/content/docs/network-interconnect/get-started.mdx
@@ -11,7 +11,7 @@ tags:
   - GCP
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 :::note[BGP architecture and resiliency]
 CNI supports BGP peering with the Cloudflare Virtual Network routing table. BGP over CNI is in closed beta and is not currently available to new customers. If you are interested in BGP peering over CNI, contact your account team.
@@ -26,7 +26,7 @@ For detailed information about BGP architecture, Edge Resiliency Mode, and route
 Your Cloudflare account team determines CNI eligibility and port availability. Notably:
 
 - CNI ports are currently offered at no charge to Enterprise customers.
-	- Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
+  - Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
 - CNI is available at select Cloudflare data centers:
   - The type of Dataplane offered in that location will determine specifications of the supported connection, such as the MTU.
   - The diversity offered in the location will vary.
@@ -43,36 +43,37 @@ To peer with Cloudflare, advertise prefixes with a prefix length of `/24` or sho
 ## Technical specifications
 
 - **Supported port types**:
-	- **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
-	- **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
+  - **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
+  - **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
 - **Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection.
 - **IP addressing:** All CNI connections and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare.
 - **VLAN support:**
-	- **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
-	- **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
+  - **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
+  - **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
 - **MTU considerations:**
-	- **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
-	- **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
+  - **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
+  - **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
 - **Bidirectional Forwarding Detection (BFD):**
-	- **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
-	- **Dataplane v2**: Not yet supported.
+  - **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
+  - **Dataplane v2**: Not yet supported.
 - **Link Aggregation Control Protocol (LACP)**:
-	- **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
-	- **Dataplane v2**: Not yet supported. Use ECMP instead.
+  - **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
+  - **Dataplane v2**: Not yet supported. Use ECMP instead.
 
 ## Performance characteristics
 
 The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration.
 
-| Direction (use case) | 10G Circuit | 100G Circuit |
-|----------------------|-------------|--------------|
-| From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps |
-| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
-| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection  |
+| Direction (use case)                            | 10G Circuit                                                                                     | 100G Circuit                                                                                    |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| From Cloudflare to Customer (all use cases)     | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
+| From Customer to Cloudflare (peering use case)  | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
+| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection |
 
 ## Service expectations
 
 Consider the following service levels when planning your deployment:
+
 - **No Formal SLA**:
   - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms).
   - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel.
@@ -98,8 +99,8 @@ The process of provisioning a CNI typically takes two to four weeks, depending o
 1. **Submit request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process.
 2. **Review configuration**: For the v1 Dataplane, the Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document. For the v2 Dataplane, this step is not necessary.
 3. **Order connection**:
-	- For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
-	- For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
+   - For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
+   - For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
 4. **Configure network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document.
 5. **Test and verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and, if applicable, verify that the BGP session can be established.
 6. Enable tunnel health checks for [Magic Transit](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) and/or [Cloudflare WAN](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels).
@@ -142,7 +143,7 @@ To connect to AWS Direct Connect:
 
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select **Create an interconnect**.
 3. Under **Cloud Interconnect**, select **Create new**.
@@ -162,9 +163,5 @@ You can now select **View interconnects** for a list of all interconnects on you
 
 After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect:
 
-- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP:
-		- Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths.
-		- Note that routes advertised by BGP from GCP Cloud Router will be ignored.
-- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router:
-		- Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes).
-		- Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
+- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP: - Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths. - Note that routes advertised by BGP from GCP Cloud Router will be ignored.
+- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router: - Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes). - Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
diff --git a/src/content/docs/network-interconnect/index.mdx b/src/content/docs/network-interconnect/index.mdx
index 80bde6dd95d9bb1..9b63e926dc454eb 100644
--- a/src/content/docs/network-interconnect/index.mdx
+++ b/src/content/docs/network-interconnect/index.mdx
@@ -11,10 +11,10 @@ head:
     content: Overview
 ---
 
-import { Description, Plan, RelatedProduct, Render } from "~/components"
+import { Description, Plan, RelatedProduct, Render } from "~/components";
 
 <Description>
-Connect your network infrastructure directly to Cloudflare
+	Connect your network infrastructure directly to Cloudflare
 </Description>
 
 <Plan type="enterprise" />
@@ -24,6 +24,7 @@ Cloudflare Network Interconnect (CNI) allows you to connect your network infrast
 ## Benefits
 
 Enterprises use CNI to achieve:
+
 - **Enhanced Performance**: Gain lower latency and more consistent network throughput.
 - **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet.
 
@@ -31,15 +32,16 @@ Enterprises use CNI to achieve:
 
 Choose the connection type for your infrastructure and operational needs.
 
-| | Direct Interconnect | Partner Interconnect | Cloud Interconnect |
-| --- | --- | --- | --- |
-| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare. |
-| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
-| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. |
+|                    | Direct Interconnect                                                                                                     | Partner Interconnect                                                                                       | Cloud Interconnect                                                                                                                              |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Port type**      | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners.            | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare.             |
+| **Operations**     | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment.                    | Your partner manages the connection logistics, often through a software-defined networking portal.         | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
+| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability.                     | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services.                                    |
 
 ## Dataplane
 
 Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection:
+
 - **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports Generic Routing Encapsulation (GRE) tunnels for connecting with the Cloudflare Virtual Network, with optional GRE-less delivery for Magic Transit Direct Server Return.
 - **Dataplane v2**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte Maximum Transmission Unit (MTU) bidirectionally.
 
@@ -55,15 +57,25 @@ To protect against a single point of failure, it is critical to design your CNI
 
 Refer to [Service Expectations](/network-interconnect/get-started/#service-expectations) for more information.
 
-***
+---
 
 ## Related products
 
-<RelatedProduct header="Magic Transit" href="/magic-transit/" product="magic-transit">
-Magic Transit is a network security and performance solution that offers Distributed Denial of Service (DDoS) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
+<RelatedProduct
+	header="Magic Transit"
+	href="/magic-transit/"
+	product="magic-transit"
+>
+	Magic Transit is a network security and performance solution that offers
+	Distributed Denial of Service (DDoS) protection, traffic acceleration, and
+	more for on-premise, cloud-hosted, and hybrid networks.
 </RelatedProduct>
 
-<RelatedProduct header="Cloudflare WAN" href="/cloudflare-wan/" product="cloudflare-wan">
-Improve security and performance for your entire corporate network, reducing cost and operation complexity.
+<RelatedProduct
+	header="Cloudflare WAN"
+	href="/cloudflare-wan/"
+	product="cloudflare-wan"
+>
+	Improve security and performance for your entire corporate network, reducing
+	cost and operation complexity.
 </RelatedProduct>
-
diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
index 861b447fcad7132..1b73b9485ee8d93 100644
--- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
+++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 5
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 ## Monitoring
 
@@ -22,17 +22,18 @@ The Status column displays three statuses:
 - **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
 - **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The **Pending** status will disappear after the customer completes the cross-connect and status moves to **Active**.
 
-
 ## Alerts (v1 dataplane only)
 
 You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
 
 **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only.
+
 - You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections.
 - You will be notified if the details of a scheduled maintenance change or if it is canceled.
 - For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments.
 
 **Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network.
+
 - You will be warned about potentially disruptive maintenance at the PoP level.
 - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these.
 - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits.
@@ -43,7 +44,7 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-	<DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
 
 2. Select **Add**.
 3. From the product drop-down menu, select _Cloudflare Network Interconnect_.
@@ -55,9 +56,10 @@ You can configure notifications for upcoming CNI maintenance events using the No
 ### Enable Cloudflare Status Maintenance Notification
 
 First, identify the PoP code for your CNI circuit:
+
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select the CNI you want to enable notifications for.
 3. In the menu that appears, note the Data Center code (for example, `gru-b`).
diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx
index a94aa4bae85717a..2cf09f24173e915 100644
--- a/src/content/docs/network-interconnect/operational-guidance.mdx
+++ b/src/content/docs/network-interconnect/operational-guidance.mdx
@@ -52,4 +52,4 @@ If no system-wide problems are reported, gather the following information before
 - **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
 - **Physical Layer**: Light levels of the CNI link (if applicable).
 - **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
-- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
\ No newline at end of file
+- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
diff --git a/src/content/docs/network/index.mdx b/src/content/docs/network/index.mdx
index e6d3e05e3d5a401..e9f9e837d33f580 100644
--- a/src/content/docs/network/index.mdx
+++ b/src/content/docs/network/index.mdx
@@ -11,38 +11,48 @@ products:
   - network
 ---
 
-import { Description, Feature, Plan, RelatedProduct } from "~/components"
+import { Description, Feature, Plan, RelatedProduct } from "~/components";
 
-<Description>
-Manage network settings for your website.
-</Description>
+<Description>Manage network settings for your website.</Description>
 
 <Plan type="all" />
 
-***
+---
 
 ## Features
 
 <Feature header="IP Geolocation" href="/network/ip-geolocation/">
-Include the country code of the visitor location with all requests to your website.
+	Include the country code of the visitor location with all requests to your
+	website.
 </Feature>
 
 <Feature header="IPv6 Compatibility" href="/network/ipv6-compatibility/">
-Enable IPv6 support and gateway.
+	Enable IPv6 support and gateway.
 </Feature>
 
 <Feature header="WebSockets" href="/network/websockets/">
-Allow WebSockets connections to your origin server.
+	Allow WebSockets connections to your origin server.
 </Feature>
 
-***
+---
 
 ## Related products
 
-<RelatedProduct header="China Network" href="/china-network/" product="china-network">
-The Cloudflare China Network is a package of selected Cloudflare’s performance and security products running on data centers located in mainland China and operated by Cloudflare’s partner JD Cloud.
+<RelatedProduct
+	header="China Network"
+	href="/china-network/"
+	product="china-network"
+>
+	The Cloudflare China Network is a package of selected Cloudflare’s performance
+	and security products running on data centers located in mainland China and
+	operated by Cloudflare’s partner JD Cloud.
 </RelatedProduct>
 
-<RelatedProduct header="Managed Transforms" href="/rules/transform/managed-transforms/" product="rules">
-Managed Transforms allow you to perform common adjustments to HTTP request and response headers with the click of a button.
+<RelatedProduct
+	header="Managed Transforms"
+	href="/rules/transform/managed-transforms/"
+	product="rules"
+>
+	Managed Transforms allow you to perform common adjustments to HTTP request and
+	response headers with the click of a button.
 </RelatedProduct>
diff --git a/src/content/docs/network/websockets.mdx b/src/content/docs/network/websockets.mdx
index 77ff14da6b28963..dbb08884e375a08 100644
--- a/src/content/docs/network/websockets.mdx
+++ b/src/content/docs/network/websockets.mdx
@@ -89,4 +89,3 @@ Cloudflare will close a WebSocket connection when no data is transmitted in eith
 ### Session affinity for load-balanced WebSocket origins
 
 If your WebSocket origin is behind a Cloudflare Load Balancer, turn on **Session affinity** to ensure all requests from the same client are routed to the same origin server. Without session affinity, a WebSocket reconnect may land on a different origin that does not have the session state.
-
diff --git a/src/content/docs/notifications/get-started/configure-pagerduty.mdx b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
index fef6662b17543be..a4e84b32aedd7cb 100644
--- a/src/content/docs/notifications/get-started/configure-pagerduty.mdx
+++ b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
@@ -12,7 +12,7 @@ import { DashButton } from "~/components";
 
 :::note
 
-This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/). 
+This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/).
 :::
 
 Cloudflare’s Notification service supports routing notifications to PagerDuty. By sending notifications to PagerDuty you can leverage the same service definitions and escalation paths that you would for other third-party services that you connect to PagerDuty.
@@ -23,14 +23,15 @@ To use PagerDuty as a connected service, you must [sign up for a PagerDuty accou
 
 :::note
 
-According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner. 
+According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner.
 :::
 
 ## Connect PagerDuty to a Cloudflare account
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **Connect**.
 4. Log in to your [PagerDuty account](https://www.pagerduty.com/) to connect it to your Cloudflare account.
@@ -48,8 +49,9 @@ Disconnecting PagerDuty will disable any notifications being sent to PagerDuty w
 If other delivery destinations were selected, then those notifications will still be routed as configured.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **View** on the PagerDuty service you want to disconnect.
 4. Select **Disconnect** > **Confirm**.
diff --git a/src/content/docs/notifications/get-started/index.mdx b/src/content/docs/notifications/get-started/index.mdx
index 4e0d0a3fba2ffc8..04bb4821e3116e6 100644
--- a/src/content/docs/notifications/get-started/index.mdx
+++ b/src/content/docs/notifications/get-started/index.mdx
@@ -36,8 +36,9 @@ This guide will help you create, edit, test, or delete notifications using the C
 You can create a notification via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select **Add**.
 3. On the notification you want to create, choose **Select**.
 4. Name the notification.
@@ -45,7 +46,7 @@ You can create a notification via the Cloudflare dashboard.
 
 :::note
 
-Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks. 
+Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks.
 :::
 
 6. (Optional) Specify any additional options for the notification, if required. For example, some notifications require that you select one or more domains or services.
@@ -58,8 +59,9 @@ The browser will navigate back to the list of notifications, where the new notif
 You can edit existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to modify, select **Edit**.
 3. Make your changes as needed and select **Save**.
 
@@ -70,8 +72,9 @@ The browser will navigate back to the list of notifications.
 You can delete or disable existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to disable, select the **Enabled** toggle. To delete it, select **Delete**.
 
 ### Mute a notification
@@ -79,8 +82,9 @@ You can delete or disable existing Notifications via the Cloudflare dashboard.
 You can temporarily mute a notification to stop receiving alerts for a set period of time. Muted notifications create a silence that automatically expires after the specified duration.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. On the notification that you want to mute, select **Mute**.
 3. Select a duration preset (**1h**, **12h**, or **24h**), or set a custom time range using the **Start Time** and **End Time** fields.
 4. Select **Save**.
@@ -95,8 +99,9 @@ While a notification is muted, alerts that would have triggered it are suppresse
 You can view, edit, or delete existing silences from the **Silences** tab.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-  
-    <DashButton url="/?to=/:account/notifications" />
+
+   <DashButton url="/?to=/:account/notifications" />
+
 2. Select the **Silences** tab.
 3. To create a new silence, select **Add**. To modify an existing silence, select **Edit**. To remove a silence before it expires, select **Delete**.
 
diff --git a/src/content/docs/notifications/index.mdx b/src/content/docs/notifications/index.mdx
index a1d547bdecee617..829b5519eba15c2 100644
--- a/src/content/docs/notifications/index.mdx
+++ b/src/content/docs/notifications/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: overview
 title: Notifications
 sidebar:
@@ -9,7 +8,7 @@ products:
 description: Configure alerts for your Cloudflare account.
 ---
 
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
 <Plan type="all" />
 
@@ -29,4 +28,4 @@ The availability of delivery methods like PagerDuty and webhooks in Free or Prof
 
 - PagerDuty is available in zones on a Free/Professional plan if your Cloudflare account has at least one zone in a Business plan (or higher).
 - Webhooks are available in zones on a Free plan if your Cloudflare account has at least one zone in a Professional plan (or higher).
-:::
+  :::
diff --git a/src/content/docs/notifications/notification-available.mdx b/src/content/docs/notifications/notification-available.mdx
index 6712c3aee831957..b41697b971f7c3d 100644
--- a/src/content/docs/notifications/notification-available.mdx
+++ b/src/content/docs/notifications/notification-available.mdx
@@ -8,7 +8,7 @@ products:
 description: Browse available notification types by product.
 ---
 
-import { AvailableNotifications } from "~/components"
+import { AvailableNotifications } from "~/components";
 
 Available Notifications depend on your Cloudflare plan. Cloudflare offers a variety of Notifications for our products and services, such as [Billing](/billing/), [Denial of Service protection](/ddos-protection/), [Magic Transit](/magic-transit/), and [SSL/TLS](/ssl/).
 
diff --git a/src/content/docs/notifications/notification-history.mdx b/src/content/docs/notifications/notification-history.mdx
index 57b80f9b1bd7402..4bbc04b274ecd9b 100644
--- a/src/content/docs/notifications/notification-history.mdx
+++ b/src/content/docs/notifications/notification-history.mdx
@@ -32,5 +32,5 @@ Notification History is available on all plans. The amount of history clients ha
 
 :::note
 
-Customers will not be able to access Notification History from before 2021-10-11. 
+Customers will not be able to access Notification History from before 2021-10-11.
 :::
diff --git a/src/content/docs/notifications/reference/index.mdx b/src/content/docs/notifications/reference/index.mdx
index 38d8d2becb9beec..6d7a07ae02df9e1 100644
--- a/src/content/docs/notifications/reference/index.mdx
+++ b/src/content/docs/notifications/reference/index.mdx
@@ -10,7 +10,7 @@ products:
 description: Reference information for Cloudflare Notifications.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Notifications:
 
diff --git a/src/content/docs/notifications/reference/traffic-alerts.mdx b/src/content/docs/notifications/reference/traffic-alerts.mdx
index 9741d0e2d2dcc30..42527aee765f7ca 100644
--- a/src/content/docs/notifications/reference/traffic-alerts.mdx
+++ b/src/content/docs/notifications/reference/traffic-alerts.mdx
@@ -28,7 +28,7 @@ This approach does not work as well for low traffic zones. If there are not many
 
 ### Service-level objective recommendations
 
-SLOs determine the sensitivity of an alert.  For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
+SLOs determine the sensitivity of an alert. For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
 
 Your traffic levels impact the accuracy of high sensitivity alerts. High sensitivity alerts are not recommended for zones with low traffic since the Error Rate alert will likely alert on every 5xx error. However, If you have a zone that has very high traffic (hundreds of millions of requests per day), High Sensitivity SLOs are recommended.
 
diff --git a/src/content/docs/pages/configuration/api.mdx b/src/content/docs/pages/configuration/api.mdx
index 5f49f4fd6a70543..d813c97fe6c9adf 100644
--- a/src/content/docs/pages/configuration/api.mdx
+++ b/src/content/docs/pages/configuration/api.mdx
@@ -19,6 +19,7 @@ To create an API token:
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
+
 2. Select **Create Token**.
 3. You can go to **Edit Cloudflare Workers** template > **Use template** or go to **Create Custom Token** > **Get started**. If you create a custom token, you will need to make sure to add the **Cloudflare Pages** permission with **Edit** access.
 
diff --git a/src/content/docs/pages/configuration/build-caching.mdx b/src/content/docs/pages/configuration/build-caching.mdx
index 3cd918887d0b276..436cc3e60e5c6d3 100644
--- a/src/content/docs/pages/configuration/build-caching.mdx
+++ b/src/content/docs/pages/configuration/build-caching.mdx
@@ -37,15 +37,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                                          |
-| ---------- | ----------------------------------------------------------- |
-| Astro      | `node_modules/.astro`                                       |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
-| Eleventy   | `.cache`                                                    |
-| Gatsby     | `.cache`, `public`                                          |
-| Next.js    | `.next/cache`                                               |
-| Nuxt       | `node_modules/.cache/nuxt`                                  |
-| SvelteKit  | `node_modules/.cache/imagetools`                            |
+| Framework  | Directories cached                            |
+| ---------- | --------------------------------------------- |
+| Astro      | `node_modules/.astro`                         |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
+| Eleventy   | `.cache`                                      |
+| Gatsby     | `.cache`, `public`                            |
+| Next.js    | `.next/cache`                                 |
+| Nuxt       | `node_modules/.cache/nuxt`                    |
+| SvelteKit  | `node_modules/.cache/imagetools`              |
 
 ### Limits
 
diff --git a/src/content/docs/pages/configuration/build-image.mdx b/src/content/docs/pages/configuration/build-image.mdx
index d2c7006afebcc61..e4596187251d055 100644
--- a/src/content/docs/pages/configuration/build-image.mdx
+++ b/src/content/docs/pages/configuration/build-image.mdx
@@ -88,6 +88,7 @@ To migrate to this new version, configure your Pages project settings in the das
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Deployments** > **All deployments** > and select the latest version.
 
@@ -109,7 +110,6 @@ Cloudflare Pages builds are run in a [gVisor](https://gvisor.dev/docs/) containe
 
 <PagesBuildEnvironment />
 
-
 ## Build Image Policy
 
 ### Build Image Version Deprecation
@@ -131,6 +131,7 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
+
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -140,6 +141,7 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
+
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
 - **Plan for migration** when you receive update notices
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
\ No newline at end of file
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
diff --git a/src/content/docs/pages/configuration/deploy-hooks.mdx b/src/content/docs/pages/configuration/deploy-hooks.mdx
index 66418eb9f810990..b40eb6d48f435bb 100644
--- a/src/content/docs/pages/configuration/deploy-hooks.mdx
+++ b/src/content/docs/pages/configuration/deploy-hooks.mdx
@@ -19,6 +19,7 @@ To create a Deploy Hook:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Builds** and select **Add deploy hook** to start configuration.
 
diff --git a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
index 377ecb62654d209..46e064b4a0d8063 100644
--- a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
+++ b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
@@ -68,6 +68,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Import from an existing Git repository**.
 3. Select your new GitHub repository.
 4. In the **Set up builds and deployments**, set `npm run build` as the **Build command**, and `dist` as the **Build output directory**.
diff --git a/src/content/docs/pages/functions/api-reference.mdx b/src/content/docs/pages/functions/api-reference.mdx
index e15d8a9a4aa0a15..9a521a8c592d30b 100644
--- a/src/content/docs/pages/functions/api-reference.mdx
+++ b/src/content/docs/pages/functions/api-reference.mdx
@@ -18,35 +18,27 @@ The following methods can be used to configure your Pages Function.
 The `onRequest` method will be called unless a more specific `onRequestVerb` method is exported. For example, if both `onRequest` and `onRequestGet` are exported, only `onRequestGet` will be called for `GET` requests.
 
 - <code>onRequest(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all requests no matter what the request method is, as long as no specific request verb (like one of the methods below) is exported.
 
 - <code>onRequestGet(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `GET` requests.
 
 - <code>onRequestPost(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `POST` requests.
 
 - <code>onRequestPatch(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `PATCH` requests.
 
 - <code>onRequestPut(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `PUT` requests.
 
 - <code>onRequestDelete(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `DELETE` requests.
 
 - <code>onRequestHead(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `HEAD` requests.
 
 - <code>onRequestOptions(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
-
   - This function will be invoked on all `OPTIONS` requests.
 
 ### `env.ASSETS.fetch()`
diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx
index b6f53b59192f9eb..4b1016b85d127f3 100644
--- a/src/content/docs/pages/functions/bindings.mdx
+++ b/src/content/docs/pages/functions/bindings.mdx
@@ -14,7 +14,13 @@ products:
   - durable-objects
 ---
 
-import { Render, TabItem, Tabs, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 A [binding](/workers/runtime-apis/bindings/) enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like [KV](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2](/r2/), and [D1](/d1/). You can set bindings for both production and preview environments.
 
@@ -37,6 +43,7 @@ To configure a KV namespace binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **KV namespace**.
 4. Give your binding a name under **Variable name**.
@@ -97,6 +104,7 @@ To configure a Durable Object binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Durable Object**.
 4. Give your binding a name under **Variable name**.
@@ -161,6 +169,7 @@ To configure a R2 bucket binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **R2 bucket**.
 4. Give your binding a name under **Variable name**.
@@ -233,6 +242,7 @@ To configure a D1 database binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add**> **D1 database bindings**.
 4. Give your binding a name under **Variable name**.
@@ -309,12 +319,13 @@ To configure a Vectorize index binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 3. Select your Pages project > **Settings**.
 4. Go to **Bindings** > **Add** > **Vectorize index**.
 5. Give your binding a name under **Variable name**.
 6. Under **Vectorize index**, select your desired Vectorize index.
-8. Redeploy your project for the binding to take effect.
+7. Redeploy your project for the binding to take effect.
 
 ### Use Vectorize index bindings
 
@@ -449,6 +460,7 @@ To configure a Workers AI binding via the Cloudflare dashboard:
 1. Go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings**.
 3. Select your Pages environment > **Bindings** > **Add** > **Workers AI**.
 4. Give your binding a name under **Variable name**.
@@ -522,6 +534,7 @@ To configure a Service binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Service binding**.
 4. Give your binding a name under **Variable name**.
@@ -586,6 +599,7 @@ To configure a queue producer binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Queue**.
 4. Give your binding a name under **Variable name**.
@@ -662,6 +676,7 @@ To configure a Hyperdrive binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Hyperdrive**.
 4. Give your binding a name under **Variable name**.
@@ -735,6 +750,7 @@ To configure an Analytics Engine binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Analytics engine**.
 4. Give your binding a name under **Variable name**.
@@ -796,6 +812,7 @@ To configure an environment variable via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add** .
 4. After setting a variable name and value, select **Save**.
@@ -854,6 +871,7 @@ To add secrets to your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add**.
 4. Set a variable name and value.
diff --git a/src/content/docs/pages/functions/examples/ab-testing.mdx b/src/content/docs/pages/functions/examples/ab-testing.mdx
index 96d45b37cd3e0f8..125a99e100cd193 100644
--- a/src/content/docs/pages/functions/examples/ab-testing.mdx
+++ b/src/content/docs/pages/functions/examples/ab-testing.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up an A/B test by controlling what page is served based on cookies.
   This version supports passing the request through to test and control on the
   origin.
diff --git a/src/content/docs/pages/functions/examples/cors-headers.mdx b/src/content/docs/pages/functions/examples/cors-headers.mdx
index 0011928013bbd10..48c58ea881e153c 100644
--- a/src/content/docs/pages/functions/examples/cors-headers.mdx
+++ b/src/content/docs/pages/functions/examples/cors-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: A Pages Functions for appending CORS headers.
 tags:
   - Headers
diff --git a/src/content/docs/pages/functions/examples/index.mdx b/src/content/docs/pages/functions/examples/index.mdx
index 26f22f52cf8ceca..a7ae43643a007ce 100644
--- a/src/content/docs/pages/functions/examples/index.mdx
+++ b/src/content/docs/pages/functions/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: Examples
 description: Code examples for common Pages Functions use cases.
diff --git a/src/content/docs/pages/functions/metrics.mdx b/src/content/docs/pages/functions/metrics.mdx
index 12b285087c355a7..802ad2e19dd4a42 100644
--- a/src/content/docs/pages/functions/metrics.mdx
+++ b/src/content/docs/pages/functions/metrics.mdx
@@ -19,6 +19,7 @@ Functions metrics aggregate request data for an individual Pages project. To vie
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. In your Pages project, select **Functions Metrics**.
 
diff --git a/src/content/docs/pages/functions/plugins/community-plugins.mdx b/src/content/docs/pages/functions/plugins/community-plugins.mdx
index 164f24737e7be5c..69d5080b51c5b6f 100644
--- a/src/content/docs/pages/functions/plugins/community-plugins.mdx
+++ b/src/content/docs/pages/functions/plugins/community-plugins.mdx
@@ -17,7 +17,6 @@ The following are some of the community-maintained Pages Plugins. If you have cr
 - [proxyflare-for-pages](https://github.com/flaregun-net/proxyflare-for-pages)
 
   Move traffic around your Cloudflare Pages domain with ease. Proxyflare is a reverse-proxy that enables you to:
-
   - Port forward, redirect, and reroute HTTP and websocket traffic anywhere on the Internet.
   - Mount an entire website on a subpath (for example, `mysite.com/docs`) on your apex domain.
   - Serve static text (like `robots.txt` and other structured metadata) from any endpoint.
diff --git a/src/content/docs/pages/get-started/c3.mdx b/src/content/docs/pages/get-started/c3.mdx
index 68c5c783012edad..c88153d094feefa 100644
--- a/src/content/docs/pages/get-started/c3.mdx
+++ b/src/content/docs/pages/get-started/c3.mdx
@@ -10,7 +10,6 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 products:
   - pages
-
 ---
 
 import {
@@ -85,30 +84,24 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
 />
 
 - `DIRECTORY` <Type text="string" /> <MetaInfo text="optional" />
-
   - The directory where the application should be created. The name of the application is taken from the directory name.
 
 - `NESTED ARGS..` <Type text="string[]" /> <MetaInfo text="optional" />
-
   - CLI arguments to pass to eventual third party CLIs C3 might invoke (in the case of full-stack applications).
 
 - `--category` <Type text="string" /> <MetaInfo text="optional" />
-
   - The kind of templates that should be created.
 
   - The possible values for this option are:
-
     - `hello-world`: Hello World example
     - `web-framework`: Framework Starter
     - `demo`: Application Starter
     - `remote-template`: Template from a GitHub repo
 
 - `--type` <Type text="string" /> <MetaInfo text="optional" />
-
   - The type of application that should be created.
 
   - The possible values for this option are:
-
     - `hello-world`: A basic "Hello World" Cloudflare Worker.
     - `hello-world-durable-object`: A [Durable Object](/durable-objects/) and a Worker to communicate with it.
     - `common`: A Cloudflare Worker which implements a common example of routing/proxying functionalities.
@@ -118,11 +111,9 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `pre-existing`: Fetch a Worker initialized from the Cloudflare dashboard.
 
 - `--framework` <Type text="string" /> <MetaInfo text="optional" />
-
   - The type of framework to use to create a web application (when using this option, `--type` is ignored).
 
   - The possible values for this option are:
-
     - `angular`
     - `astro`
     - `docusaurus`
@@ -139,11 +130,9 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `vue`
 
 - `--template` <Type text="string" /> <MetaInfo text="optional" />
-
   - Create a new project via an external template hosted in a git repository
 
   - The value for this option may be specified as any of the following:
-
     - `user/repo`
     - `git@github.com:user/repo`
     - `https://github.com/user/repo`
@@ -156,7 +145,6 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the `degit` [docs](https://github.com/Rich-Harris/degit) for more details.
 
     At a minimum, templates must contain the following:
-
     - `package.json`
     - [Wrangler configuration file](/pages/functions/wrangler-configuration/)
     - `src/` containing a worker script referenced from the Wrangler configuration file
@@ -164,51 +152,40 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the [templates folder](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare/templates) of this repo for more examples.
 
 - `--deploy` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Deploy your application after it has been created.
 
 - `--lang` <Type text="string" /> <MetaInfo text="(default: ts) optional" />
-
   - The programming language of the template.
 
   - The possible values for this option are:
-
     - `ts`
     - `js`
     - `python`
 
 - `--ts` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Use TypeScript in your application. Deprecated. Use `--lang=ts` instead.
 
 - `--git` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Initialize a local git repository for your application.
 
 - `--open` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Open with your browser the deployed application (this option is ignored if the application is not deployed).
 
 - `--existing-script` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of an existing Cloudflare Workers script to clone locally. When using this option, `--type` is coerced to `pre-existing`.
 
   - When `--existing-script` is specified, `deploy` will be ignored.
 
 - `-y`, `--accept-defaults` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Use all the default C3 options each can also be overridden by specifying it.
 
 - `--auto-update` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
-
   - Automatically uses the latest version of C3.
 
 - `-v`, `--version` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Show version number.
 
 - `-h`, `--help` <Type text="boolean" /> <MetaInfo text="optional" />
-
   - Show a help message.
 
 :::note
diff --git a/src/content/docs/pages/get-started/direct-upload.mdx b/src/content/docs/pages/get-started/direct-upload.mdx
index 9f7252898b5ddba..f1f5228ef2053d0 100644
--- a/src/content/docs/pages/get-started/direct-upload.mdx
+++ b/src/content/docs/pages/get-started/direct-upload.mdx
@@ -8,7 +8,6 @@ description: Upload your prebuilt assets to Pages and deploy them via the
   Wrangler CLI or the Cloudflare dashboard.
 products:
   - pages
-
 ---
 
 import { Render, DashButton } from "~/components";
@@ -128,6 +127,7 @@ To deploy with drag and drop:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Get started** > **Drag and drop your files**.
 3. Enter your project name in the provided field and drag and drop your assets.
 4. Select **Deploy site**.
diff --git a/src/content/docs/pages/get-started/git-integration.mdx b/src/content/docs/pages/get-started/git-integration.mdx
index 3b6cb58789596cb..5ac8218965fb505 100644
--- a/src/content/docs/pages/get-started/git-integration.mdx
+++ b/src/content/docs/pages/get-started/git-integration.mdx
@@ -7,7 +7,6 @@ head:
 description: Connect your Git provider to Pages.
 products:
   - pages
-
 ---
 
 import { Details, Render } from "~/components";
diff --git a/src/content/docs/pages/get-started/index.mdx b/src/content/docs/pages/get-started/index.mdx
index 328bd28a8396d9c..e76af4b0b86da8a 100644
--- a/src/content/docs/pages/get-started/index.mdx
+++ b/src/content/docs/pages/get-started/index.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 2
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/add-custom-http-headers.mdx b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
index 3402e5e5a66d4e5..7dedb62c0645ef1 100644
--- a/src/content/docs/pages/how-to/add-custom-http-headers.mdx
+++ b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
@@ -5,7 +5,6 @@ description: Customize HTTP headers on Cloudflare Pages using a Workers function
 products:
   - pages
   - workers
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/docs/pages/how-to/build-commands-branches.mdx b/src/content/docs/pages/how-to/build-commands-branches.mdx
index 46ab3dfafb2d1a1..d91423afb902d99 100644
--- a/src/content/docs/pages/how-to/build-commands-branches.mdx
+++ b/src/content/docs/pages/how-to/build-commands-branches.mdx
@@ -5,7 +5,6 @@ title: Set build commands per branch
 description: Run different build commands on specific branches in your Cloudflare Pages project.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -46,6 +45,7 @@ To put your changes into effect:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
 4. Update the **Build command** field value to `bash build.sh` and select **Save**.
diff --git a/src/content/docs/pages/how-to/custom-branch-aliases.mdx b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
index a50f4c6b38fe0a3..818ca533a5bf852 100644
--- a/src/content/docs/pages/how-to/custom-branch-aliases.mdx
+++ b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
@@ -4,7 +4,6 @@ title: Add a custom domain to a branch
 description: Point a custom domain to a specific branch deployment of your Cloudflare Pages project.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -32,6 +31,7 @@ To do this:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Select **Custom domains** > **Setup a custom domain**.
 4. Input the domain you would like to use, such as `staging.example.com`
diff --git a/src/content/docs/pages/how-to/enable-zaraz.mdx b/src/content/docs/pages/how-to/enable-zaraz.mdx
index a421e08bb06a094..20a3092b435873c 100644
--- a/src/content/docs/pages/how-to/enable-zaraz.mdx
+++ b/src/content/docs/pages/how-to/enable-zaraz.mdx
@@ -4,7 +4,6 @@ title: Enable Zaraz
 description: Set up Zaraz on your Cloudflare Pages project using a custom domain.
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/index.mdx b/src/content/docs/pages/how-to/index.mdx
index d2707643d72ee16..3da369ff33b9913 100644
--- a/src/content/docs/pages/how-to/index.mdx
+++ b/src/content/docs/pages/how-to/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: How to
 description: Step-by-step guides for common Cloudflare Pages tasks and configurations.
@@ -9,7 +8,6 @@ sidebar:
     hideIndex: true
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/npm-private-registry.mdx b/src/content/docs/pages/how-to/npm-private-registry.mdx
index 95889b262b4dd84..a03e59ef22f9dc3 100644
--- a/src/content/docs/pages/how-to/npm-private-registry.mdx
+++ b/src/content/docs/pages/how-to/npm-private-registry.mdx
@@ -4,7 +4,6 @@ title: Install private packages
 description: Use custom npm registries and private dependencies in your Cloudflare Pages builds.
 products:
   - pages
-
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
index 8780a611c5c465c..76183d80849d09f 100644
--- a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
+++ b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
@@ -5,7 +5,6 @@ description: Use Cloudflare Tunnel to share locally running Pages projects over
 products:
   - pages
   - tunnel
-
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) runs a lightweight daemon (`cloudflared`) in your infrastructure that establishes outbound connections (Tunnels) between your origin web server and the Cloudflare global network. In practical terms, you can use Cloudflare Tunnel to allow remote access to services running on your local machine. It is an alternative to popular tools like [Ngrok](https://ngrok.com), and provides free, long-running tunnels via the [TryCloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/trycloudflare/) service.
diff --git a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
index e70f762274f2772..4349352400a31e5 100644
--- a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
+++ b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
@@ -6,7 +6,6 @@ sidebar:
   hidden: true
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
index 1770a4c1621da73..5526154ba6650bd 100644
--- a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
+++ b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
@@ -4,7 +4,6 @@ title: Use Direct Upload with continuous integration
 description: Deploy prebuilt assets to Cloudflare Pages using Wrangler in your CI/CD pipeline.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -29,6 +28,7 @@ To generate an API token:
 1. In the Cloudflare dashboard, go to the **API Tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
+
 2. Select **Create Token**.
 3. Under **Custom Token**, select **Get started**.
 4. Name your API Token in the **Token name** field.
@@ -43,7 +43,7 @@ Now that you have created your API token, you can use it to push your project fr
 
 To find your account ID, go to the **Zone Overview** page in the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/:zone/" />
+<DashButton url="/?to=/:account/:zone/" />
 
 Find your account ID in the **API** section on the right-hand side menu.
 
diff --git a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
index 2d7fb92626a856d..8e750ac70df0a77 100644
--- a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
+++ b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
@@ -4,7 +4,6 @@ title: Use Pages Functions for A/B testing
 description: Implement A/B testing in Cloudflare Pages using Pages Functions and cookies.
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -162,4 +161,5 @@ After you have deployed your application, review your middleware Function:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings** > **Functions** > **Configuration**.
diff --git a/src/content/docs/pages/how-to/web-analytics.mdx b/src/content/docs/pages/how-to/web-analytics.mdx
index 723b5241d55c0e2..80cab7cc7a0ebda 100644
--- a/src/content/docs/pages/how-to/web-analytics.mdx
+++ b/src/content/docs/pages/how-to/web-analytics.mdx
@@ -4,7 +4,6 @@ title: Enable Web Analytics
 description: Set up Cloudflare Web Analytics on your Pages project with one-click configuration.
 products:
   - pages
-
 ---
 
 import { Render, DashButton } from "~/components";
@@ -24,6 +23,7 @@ To view the metrics associated with your Pages project:
 1. In the Cloudflare dashboard, go to the **Web Analytics** page.
 
    <DashButton url="/?to=/:account/web-analytics" />
+
 2. Select the analytics associated with your Pages project.
 
 For more details about how to use Web Analytics, refer to the [Web Analytics documentation](/web-analytics/data-metrics/).
diff --git a/src/content/docs/pages/migrations/index.mdx b/src/content/docs/pages/migrations/index.mdx
index dfac1294f41d646..462426a9667eb83 100644
--- a/src/content/docs/pages/migrations/index.mdx
+++ b/src/content/docs/pages/migrations/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: navigation
 title: Migration guides
 description: Migrate your existing site from another platform to Cloudflare Pages.
@@ -8,7 +7,6 @@ sidebar:
   order: 4
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/index.mdx b/src/content/docs/pages/platform/index.mdx
index 1a133b13acfc655..925be7f4266e12b 100644
--- a/src/content/docs/pages/platform/index.mdx
+++ b/src/content/docs/pages/platform/index.mdx
@@ -8,7 +8,6 @@ sidebar:
     hideIndex: true
 products:
   - pages
-
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/known-issues.mdx b/src/content/docs/pages/platform/known-issues.mdx
index cd105ebacb7fa5e..3a0b439ae2c0327 100644
--- a/src/content/docs/pages/platform/known-issues.mdx
+++ b/src/content/docs/pages/platform/known-issues.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 4
 products:
   - pages
-
 ---
 
 import { DashButton } from "~/components";
@@ -40,7 +39,6 @@ Here are some known bugs and issues with Cloudflare Pages:
 ## Custom Domains
 
 - It is currently not possible to add a custom domain with
-
   - a wildcard, for example, `*.domain.com`.
   - a Worker already routed on that domain.
 
@@ -67,6 +65,7 @@ If you would like to enable [Cloudflare Access](https://www.cloudflare.com/teams
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Settings** > **Enable access policy**.
 4. Select **Manage** on the Access policy created for your preview deployments.
diff --git a/src/content/docs/pages/platform/limits.mdx b/src/content/docs/pages/platform/limits.mdx
index dd994f7de3cd191..372373843e2b19a 100644
--- a/src/content/docs/pages/platform/limits.mdx
+++ b/src/content/docs/pages/platform/limits.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 1
 products:
   - pages
-
 ---
 
 import { Render } from "~/components";
@@ -18,10 +17,10 @@ Below are limits observed by the Cloudflare Free plan. For more details on remov
 ## Builds
 
 Each time you push new code to your Git repository, Pages will build and deploy your site. Build limits depend on your plan:
-|                  | Free              | Pro                 | Business             |
+| | Free | Pro | Business |
 | ---------------- | ----------------- | ------------------- | -------------------- |
-| Builds           | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
-| Builds per month | 500               | 5,000               | 20,000               |
+| Builds | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
+| Builds per month | 500 | 5,000 | 20,000 |
 
 Builds will timeout after 20 minutes. Concurrent builds are counted per account.
 
diff --git a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
index 880fe3088aafd05..499da32c9d96168 100644
--- a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
+++ b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
@@ -114,7 +114,7 @@ import ContactForm from "./ContactForm";
 Then insert the form into the page as a react component:
 
 ```jsx
-<ContactForm />
+<ContactForm />;
 ```
 
 For example, you can update your `src/App.js` file to add the form:
diff --git a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
index d8a492d5d29124e..413e037121afc72 100644
--- a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
+++ b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
@@ -365,6 +365,7 @@ After you have pushed your project to GitHub, deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Import an existing Git repository**.
 3. Select the new GitHub repository that you created and select **Begin setup**.
 4. In the **Set up builds and deployments** section, under **Build settings** > **Framework preset**, choose _Nuxt_. Pages will set the correct fields for you automatically.
diff --git a/src/content/docs/pipelines/reference/wrangler-commands.mdx b/src/content/docs/pipelines/reference/wrangler-commands.mdx
index 655d91f87e8a583..154b40b6ccb4976 100644
--- a/src/content/docs/pipelines/reference/wrangler-commands.mdx
+++ b/src/content/docs/pipelines/reference/wrangler-commands.mdx
@@ -10,5 +10,4 @@ products:
 
 import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="pipelines"/>
-
+<WranglerNamespace namespace="pipelines" />
diff --git a/src/content/docs/pipelines/sinks/manage-sinks.mdx b/src/content/docs/pipelines/sinks/manage-sinks.mdx
index 7623ca305f5c3e1..5f4d14b28b01f0a 100644
--- a/src/content/docs/pipelines/sinks/manage-sinks.mdx
+++ b/src/content/docs/pipelines/sinks/manage-sinks.mdx
@@ -101,4 +101,4 @@ Deleting a sink stops all data writes to that destination.
 ## Limitations
 
 - Sinks cannot be modified after creation. To change sink configuration, you must delete and recreate the sink.
-- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
\ No newline at end of file
+- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
diff --git a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
index b47c9b02de9b990..da91b792332d4d5 100644
--- a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
+++ b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
@@ -521,7 +521,6 @@ uuid()
 Returns the string which is replaced by another string from the specified position and specified count length.
 For example, `overlay('Txxxxas' placing 'hom' from 2 for 4) → Thomas`
 
-
 ```
 overlay(str PLACING substr FROM pos [FOR count])
 ```
diff --git a/src/content/docs/privacy-gateway/get-started.mdx b/src/content/docs/privacy-gateway/get-started.mdx
index 41f956ba77f1276..05973978d5a98cd 100644
--- a/src/content/docs/privacy-gateway/get-started.mdx
+++ b/src/content/docs/privacy-gateway/get-started.mdx
@@ -14,13 +14,13 @@ Privacy Gateway implementation consists of three main parts:
 2. Client configuration (operated by you).
 3. Connection to a Privacy Gateway Relay Server (operated by Cloudflare).
 
-***
+---
 
 ## Before you begin
 
 Privacy Gateway is currently in closed beta. If you are interested, [contact us](https://www.cloudflare.com/lp/privacy-edge/).
 
-***
+---
 
 ## Step 1 - Configure your server
 
@@ -34,13 +34,13 @@ Applications can also implement this functionality themselves. Details about [pu
 
 Use the following resources for help with server configuration:
 
-* **Go**:
-  * [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
-  * [Gateway library](https://github.com/chris-wood/ohttp-go)
-* **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
-* **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
+- **Go**:
+  - [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
+  - [Gateway library](https://github.com/chris-wood/ohttp-go)
+- **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
+- **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
 
-***
+---
 
 ## Step 2 - Configure your client
 
@@ -52,21 +52,21 @@ Additionally, app developers need to [configure the client](#resources-1) to fet
 
 Use the following resources for help with client configuration:
 
-* **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
-* **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
-* **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
+- **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
+- **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
+- **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
 
-***
+---
 
 ## Step 3 - Review your application
 
 After you have configured your client and server, review your application to make sure you are only sending intended data to Cloudflare and the application backend. In particular, application data should not contain anything unique to an end-user, as this would invalidate the benefits that OHTTP provides.
 
-* Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
-* Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
-* Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
+- Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
+- Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
+- Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
 
-***
+---
 
 ## Step 4 - Relay requests through Cloudflare
 
diff --git a/src/content/docs/privacy-gateway/reference/index.mdx b/src/content/docs/privacy-gateway/reference/index.mdx
index 50d23832e8505f7..bdcb0f1f7729beb 100644
--- a/src/content/docs/privacy-gateway/reference/index.mdx
+++ b/src/content/docs/privacy-gateway/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - privacy-gateway
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/privacy-gateway/reference/legal.mdx b/src/content/docs/privacy-gateway/reference/legal.mdx
index 22928aac224e0f6..8f68db4684d0d76 100644
--- a/src/content/docs/privacy-gateway/reference/legal.mdx
+++ b/src/content/docs/privacy-gateway/reference/legal.mdx
@@ -24,5 +24,5 @@ Cloudflare retains the Privacy Gateway Logs information for the most recent quar
 
 ## What Privacy Gateway customers see
 
-* The application content of requests.
-* The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
+- The application content of requests.
+- The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
diff --git a/src/content/docs/privacy-gateway/reference/metrics.mdx b/src/content/docs/privacy-gateway/reference/metrics.mdx
index f40cb4d6ffbc6ee..6a0751366ca483b 100644
--- a/src/content/docs/privacy-gateway/reference/metrics.mdx
+++ b/src/content/docs/privacy-gateway/reference/metrics.mdx
@@ -10,8 +10,8 @@ products:
 
 Privacy Gateway now supports enhanced monitoring through our GraphQL API, providing detailed insights into your gateway traffic and performance. To access these metrics, ensure you have:
 
-* A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
-* An API token with Analytics Read permissions.
+- A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
+- An API token with Analytics Read permissions.
   We offer two GraphQL nodes to retrieve metrics: `ohttpMetricsAdaptive` and `ohttpMetricsAdaptiveGroups`. The first node provides comprehensive request data, while the second facilitates grouped analytics.
 
 ## ohttpMetricsAdaptive
@@ -20,33 +20,27 @@ The `ohttpMetricsAdaptive` node is designed for detailed insights into individua
 
 ### Key Arguments
 
-
-
-* `filter` required
-  * Apply filters to narrow down your data set. `accountTag` is a required filter.
-* `limit`  optional
-  * Specify the maximum number of records to return.
-* `orderBy` optional
-  * Choose how to sort your data, with options for various dimensions and metrics.
-
+- `filter` required
+  - Apply filters to narrow down your data set. `accountTag` is a required filter.
+- `limit` optional
+  - Specify the maximum number of records to return.
+- `orderBy` optional
+  - Choose how to sort your data, with options for various dimensions and metrics.
 
 ### Available Fields
 
-
-
-* `bytesToClient` int optional
-  * The number of bytes returned to the client.
-* `bytesToGateway` int optional
-  * Total bytes received from the client.
-* `colo` string optional
-  * Airport code of the Cloudflare data center that served the request.
-* `datetime` Time optional
-  * The date and time when the event was recorded.
-* `gatewayStatusCode` int optional
-  * Status code returned by the gateway.
-* `relayStatusCode` int optional
-  * Status code returned by the relay.
-
+- `bytesToClient` int optional
+  - The number of bytes returned to the client.
+- `bytesToGateway` int optional
+  - Total bytes received from the client.
+- `colo` string optional
+  - Airport code of the Cloudflare data center that served the request.
+- `datetime` Time optional
+  - The date and time when the event was recorded.
+- `gatewayStatusCode` int optional
+  - Status code returned by the gateway.
+- `relayStatusCode` int optional
+  - Status code returned by the relay.
 
 This node is useful for a granular view of traffic, helping you identify patterns, performance issues, or anomalies in your data flow.
 
@@ -56,66 +50,56 @@ The `ohttpMetricsAdaptiveGroups` node allows for aggregated analysis of OHTTP re
 
 ### Key Arguments
 
-
-
-* `filter` required
-  * Apply filters to narrow down your data set. `accountTag` is a required filter.
-* `limit`  optional
-  * Specify the maximum number of records to return.
-* `orderBy` optional
-  * Choose how to sort your data, with options for various dimensions and metrics.
-
+- `filter` required
+  - Apply filters to narrow down your data set. `accountTag` is a required filter.
+- `limit` optional
+  - Specify the maximum number of records to return.
+- `orderBy` optional
+  - Choose how to sort your data, with options for various dimensions and metrics.
 
 ### Available Fields
 
-
-
-* `count` int optional
-  * The number of records that meet the criteria.
-* `dimensions` optional
-  * Specifies the grouping dimensions for your data.
-* `sum` optional
-  * Aggregated totals for various metrics, per dimension.
-
+- `count` int optional
+  - The number of records that meet the criteria.
+- `dimensions` optional
+  - Specifies the grouping dimensions for your data.
+- `sum` optional
+  - Aggregated totals for various metrics, per dimension.
 
 **Dimensions**
 
 You can group your metrics by various dimensions to get a more segmented view of your data:
 
-
-* `colo` string optional
-  * The airport code of the Cloudflare data center.
-* `date` Date optional
-  * The date of OHTTP request metrics.
-* `datetimeFifteenMinutes` Time optional
-  * Timestamp truncated to fifteen minutes.
-* `datetimeFiveMinutes` Time optional
-  * Timestamp truncated to five minutes.
-* `datetimeHour` Time optional
-  * Timestamp truncated to the hour.
-* `datetimeMinute` Time optional
-  * Timestamp truncated to the minute.
-* `endpoint` string optional
-  * The appId that generated traffic.
-* `gatewayStatusCode` int optional
-  * Status code returned by the gateway.
-* `relayStatusCode` int optional
-  * Status code returned by the relay.
-
+- `colo` string optional
+  - The airport code of the Cloudflare data center.
+- `date` Date optional
+  - The date of OHTTP request metrics.
+- `datetimeFifteenMinutes` Time optional
+  - Timestamp truncated to fifteen minutes.
+- `datetimeFiveMinutes` Time optional
+  - Timestamp truncated to five minutes.
+- `datetimeHour` Time optional
+  - Timestamp truncated to the hour.
+- `datetimeMinute` Time optional
+  - Timestamp truncated to the minute.
+- `endpoint` string optional
+  - The appId that generated traffic.
+- `gatewayStatusCode` int optional
+  - Status code returned by the gateway.
+- `relayStatusCode` int optional
+  - Status code returned by the relay.
 
 **Sum Fields**
 
 Sum fields offer a cumulative view of various metrics over your selected time period:
 
-
-* `bytesToClient` int optional
-  * Total bytes sent from the gateway to the client.
-* `bytesToGateway` int optional
-  * Total bytes from the client to the gateway.
-* `clientRequestErrors` int optional
-  * Total number of client request errors.
-* `gatewayResponseErrors` int optional
-  * Total number of gateway response errors.
-
+- `bytesToClient` int optional
+  - Total bytes sent from the gateway to the client.
+- `bytesToGateway` int optional
+  - Total bytes from the client to the gateway.
+- `clientRequestErrors` int optional
+  - Total number of client request errors.
+- `gatewayResponseErrors` int optional
+  - Total number of gateway response errors.
 
 Utilize the ohttpMetricsAdaptiveGroups node to gain comprehensive, aggregated insights into your traffic patterns, helping you optimize performance and user experience.
diff --git a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
index f6f435416d2e986..e319b9824e7ef2c 100644
--- a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
+++ b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
@@ -12,6 +12,6 @@ When [using Privacy Gateway](/privacy-gateway/get-started/), the majority of Clo
 
 However, the following products are not compatible:
 
-* [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
-* [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
-* [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
+- [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
+- [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
+- [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
diff --git a/src/content/docs/privacy-proxy/concepts/authentication.mdx b/src/content/docs/privacy-proxy/concepts/authentication.mdx
index 5adead0bc45a818..344ac01c3d65a39 100644
--- a/src/content/docs/privacy-proxy/concepts/authentication.mdx
+++ b/src/content/docs/privacy-proxy/concepts/authentication.mdx
@@ -14,11 +14,11 @@ Privacy Proxy requires clients to authenticate before proxying traffic. This pag
 
 Privacy Proxy supports three authentication methods:
 
-| Method | Use case | Privacy level |
-| -------- | ---------- | --------------- |
-| Pre-shared key (PSK) | Proof of concept, testing | Lower |
-| Privacy Pass tokens | Client to server | High |
-| mTLS | Server to server | Higher |
+| Method               | Use case                  | Privacy level |
+| -------------------- | ------------------------- | ------------- |
+| Pre-shared key (PSK) | Proof of concept, testing | Lower         |
+| Privacy Pass tokens  | Client to server          | High          |
+| mTLS                 | Server to server          | Higher        |
 
 ---
 
@@ -166,7 +166,7 @@ Proxy A (which you operate) authenticates users. Common methods include:
 - Privacy Pass tokens issued by your infrastructure
 - Client certificates (mTLS)
 
-### Proxy A to Proxy B 
+### Proxy A to Proxy B
 
 Proxy B authenticates itself to Proxy A using TLS. Depending on your configuration, this can use:
 
diff --git a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
index 72190396733d8b8..dfe5168ada7b9a2 100644
--- a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
+++ b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
@@ -65,12 +65,12 @@ In a double-hop deployment, you operate the first proxy (Proxy A), and Cloudflar
 
 The double-hop architecture ensures:
 
-| Information | Proxy A (you) | Proxy B (Cloudflare) |
-| ------------- | --------------- | ---------------------- |
-| Client IP address | Yes | No |
-| User account | Yes | No |
-| Destination server | Encrypted | Yes |
-| Request content | Encrypted | Encrypted |
+| Information        | Proxy A (you) | Proxy B (Cloudflare) |
+| ------------------ | ------------- | -------------------- |
+| Client IP address  | Yes           | No                   |
+| User account       | Yes           | No                   |
+| Destination server | Encrypted     | Yes                  |
+| Request content    | Encrypted     | Encrypted            |
 
 Proxy A knows who the user is but cannot see where they are going (the destination is encrypted). Proxy B knows the destination but not who is making the request. Neither party has the complete picture.
 
@@ -90,13 +90,13 @@ Double-hop deployment works well when:
 
 ## Comparison
 
-| Aspect | Single-hop | Double-hop |
-| -------- | ------------ | ------------ |
-| Infrastructure | Cloudflare only | You + Cloudflare |
-| Privacy separation | Proxy sees identity + destination | Split across two parties |
-| Operational complexity | Lower | Higher |
-| Authentication | Cloudflare-managed | You manage first-hop auth |
-| Use case | Browser VPNs, simple privacy | Maximum privacy separation |
+| Aspect                 | Single-hop                        | Double-hop                 |
+| ---------------------- | --------------------------------- | -------------------------- |
+| Infrastructure         | Cloudflare only                   | You + Cloudflare           |
+| Privacy separation     | Proxy sees identity + destination | Split across two parties   |
+| Operational complexity | Lower                             | Higher                     |
+| Authentication         | Cloudflare-managed                | You manage first-hop auth  |
+| Use case               | Browser VPNs, simple privacy      | Maximum privacy separation |
 
 ---
 
diff --git a/src/content/docs/privacy-proxy/concepts/geolocation.mdx b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
index 987c5e96e5514ab..2c60dc4cbde92c0 100644
--- a/src/content/docs/privacy-proxy/concepts/geolocation.mdx
+++ b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
@@ -30,12 +30,12 @@ Privacy Proxy uses geohashes to preserve location without revealing precise coor
 A [geohash](https://en.wikipedia.org/wiki/Geohash) is a compact representation of latitude and longitude. Geohashes use a hierarchical encoding where longer strings represent more precise locations:
 
 | Geohash length | Approximate area |
-| ---------------- | ------------------ |
-| 1 character | ~5,000 km |
-| 2 characters | ~1,250 km |
-| 3 characters | ~150 km |
-| 4 characters | ~40 km |
-| 5 characters | ~5 km |
+| -------------- | ---------------- |
+| 1 character    | ~5,000 km        |
+| 2 characters   | ~1,250 km        |
+| 3 characters   | ~150 km          |
+| 4 characters   | ~40 km           |
+| 5 characters   | ~5 km            |
 
 Privacy Proxy uses reduced-precision geohashes (typically four to five characters) to locate users to a city or region without pinpointing their exact location.
 
diff --git a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
index 3c4634922f9757c..6d1b3146f38fc82 100644
--- a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
+++ b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
@@ -35,15 +35,14 @@ Privacy Proxy uses the MASQUE protocol suite to create encrypted tunnels between
 
 Throughout this process, the proxy learns the destination but not the content. The destination learns the egress IP address but not the client's real IP.
 
-
 ## MASQUE protocols
 
 [MASQUE](https://datatracker.ietf.org/wg/masque/about/) (Multiplexed Application Substrate over QUIC Encryption) defines methods for proxying traffic over HTTP. Privacy Proxy supports two MASQUE methods:
 
-| Method | Transport | Use case |
-| -------- | ----------- | ---------- |
-| HTTP CONNECT | TCP | Traditional HTTPS traffic |
-| CONNECT-UDP | UDP | QUIC-based traffic, real-time applications |
+| Method       | Transport | Use case                                   |
+| ------------ | --------- | ------------------------------------------ |
+| HTTP CONNECT | TCP       | Traditional HTTPS traffic                  |
+| CONNECT-UDP  | UDP       | QUIC-based traffic, real-time applications |
 
 Both methods create encrypted tunnels where the proxy forwards traffic without inspecting the content. The proxy sees only the destination hostname and port, not the actual requests, paths, or data exchanged.
 
@@ -55,11 +54,11 @@ For a technical deep dive into how these protocols work, refer to our [blog post
 
 Privacy Proxy creates a privacy boundary between user identity and user activity:
 
-| Information | Who knows it |
-| ------------- | -------------- |
+| Information                         | Who knows it                                                  |
+| ----------------------------------- | ------------------------------------------------------------- |
 | User identity (IP address, account) | Authentication service, first-hop proxy (if using double-hop) |
-| Destination server | Privacy Proxy, destination server |
-| Request content | Client, destination server only |
+| Destination server                  | Privacy Proxy, destination server                             |
+| Request content                     | Client, destination server only                               |
 
 The proxy authenticates users to verify they have permission to use the service, but authentication happens separately from proxying. Once authenticated, the proxy forwards traffic without linking individual requests to specific users.
 
diff --git a/src/content/docs/privacy-proxy/get-started.mdx b/src/content/docs/privacy-proxy/get-started.mdx
index f07aa967b04f5d0..951b12a8ad7876e 100644
--- a/src/content/docs/privacy-proxy/get-started.mdx
+++ b/src/content/docs/privacy-proxy/get-started.mdx
@@ -37,7 +37,7 @@ curl -v \
   https://example.com
 ```
 
-### Use Chaussette 
+### Use Chaussette
 
 [Chaussette](/privacy-proxy/reference/client-libraries/#chaussette) is a local SOCKS5 proxy that handles authentication and forwards requests to Privacy Proxy.
 
diff --git a/src/content/docs/privacy-proxy/reference/http-headers.mdx b/src/content/docs/privacy-proxy/reference/http-headers.mdx
index 39788fd3a51a37b..da3750df07b72b9 100644
--- a/src/content/docs/privacy-proxy/reference/http-headers.mdx
+++ b/src/content/docs/privacy-proxy/reference/http-headers.mdx
@@ -30,10 +30,10 @@ Privacy Pass token format:
 Proxy-Authorization: PrivateToken token=<base64-encoded-token>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
-| `<key>` | The pre-shared key provided by Cloudflare |
-| `<base64-encoded-token>` | A base64-encoded Privacy Pass token |
+| Parameter                | Description                               |
+| ------------------------ | ----------------------------------------- |
+| `<key>`                  | The pre-shared key provided by Cloudflare |
+| `<base64-encoded-token>` | A base64-encoded Privacy Pass token       |
 
 ### GraphQL Analytics API request headers
 
@@ -47,10 +47,10 @@ Specifies the client's geographic location for egress IP selection. Optional but
 sec-ch-geohash: <geohash>-<country_code>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
-| `<geohash>` | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
-| `<country_code>` | ISO 3166-1 alpha-2 country code |
+| Parameter        | Description                                                                          |
+| ---------------- | ------------------------------------------------------------------------------------ |
+| `<geohash>`      | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
+| `<country_code>` | ISO 3166-1 alpha-2 country code                                                      |
 
 ```http title="Example"
 sec-ch-geohash: u4pruydqqvj-GB
@@ -72,8 +72,8 @@ Provides timing information about proxy processing. This is part of the [OpenTel
 Server-Timing: proxy;dur=<milliseconds>
 ```
 
-| Parameter | Description |
-| ----------- | ------------- |
+| Parameter        | Description                                             |
+| ---------------- | ------------------------------------------------------- |
 | `<milliseconds>` | Processing time in milliseconds introduced by the proxy |
 
 ```http title="Example"
@@ -99,9 +99,9 @@ sec-ch-geohash: 9q8yy-US
 
 The proxy responds with a status code indicating success or failure:
 
-| Status | Meaning |
-| -------- | --------- |
-| `200 OK` | Tunnel established successfully |
-| `403 Forbidden` | Authentication failed |
-| `502 Bad Gateway` | Could not connect to destination |
-| `503 Service Unavailable` | Proxy temporarily unavailable |
+| Status                    | Meaning                          |
+| ------------------------- | -------------------------------- |
+| `200 OK`                  | Tunnel established successfully  |
+| `403 Forbidden`           | Authentication failed            |
+| `502 Bad Gateway`         | Could not connect to destination |
+| `503 Service Unavailable` | Proxy temporarily unavailable    |
diff --git a/src/content/docs/privacy-proxy/reference/proxy-status.mdx b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
index 8a0a873a9b6ca6f..3cd177c2306ccca 100644
--- a/src/content/docs/privacy-proxy/reference/proxy-status.mdx
+++ b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
@@ -16,29 +16,29 @@ The `proxyStatus` dimension provides proxy-level error classification. This fiel
 
 ## `proxyStatus` values
 
-| Value | Description |
-| --- | --- |
-| `dns_error` | The proxy encountered a DNS error when resolving the next hop hostname. |
-| `dns_timeout` | The proxy timed out while resolving the next hop hostname. |
-| `destination_not_found` | The proxy cannot determine the appropriate next hop for this request. |
-| `destination_unavailable` | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
-| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address. |
-| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address. |
-| `connection_refused` | The proxy's connection to the next hop was refused. |
-| `connection_terminated` | The proxy's connection to the next hop was closed before any response was received. |
-| `connection_timeout` | The proxy's attempt to open a connection to the next hop timed out. |
-| `connection_read_timeout` | The proxy was expecting data on a connection but received none within the configured time limit. |
-| `connection_write_timeout` | The proxy was attempting to write data to a connection but was unable to. |
-| `connection_limit_reached` | The proxy's configured connection limit to the next hop has been exceeded. |
-| `source_addr_in_use` | The proxy cannot assign a source address when connecting to the next hop. |
-| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure). |
-| `tls_protocol_error` | The proxy encountered a TLS error when communicating with the next hop. |
-| `tls_certificate_error` | The proxy encountered an error verifying the certificate presented by the next hop. |
-| `http_request_error` | The proxy is generating a client (4xx) response on the origin's behalf. |
-| `http_upgrade_failed` | The HTTP Upgrade between the proxy and the next hop failed. |
-| `http_request_denied` | The proxy rejected the HTTP request based on its configuration or policy. |
-| `proxy_internal_error` | The proxy encountered an internal error unrelated to the origin. |
-| `proxy_loop_detected` | The proxy tried to forward the request to itself. |
-| `http_protocol_error` | The proxy encountered an HTTP protocol error when communicating with the next hop. |
-| `http_response_incomplete` | The proxy received an incomplete response from the next hop. |
-| `rate_limited` | The client has reached the maximum number of connections per second to a single origin. |
+| Value                       | Description                                                                                          |
+| --------------------------- | ---------------------------------------------------------------------------------------------------- |
+| `dns_error`                 | The proxy encountered a DNS error when resolving the next hop hostname.                              |
+| `dns_timeout`               | The proxy timed out while resolving the next hop hostname.                                           |
+| `destination_not_found`     | The proxy cannot determine the appropriate next hop for this request.                                |
+| `destination_unavailable`   | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
+| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address.                          |
+| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address.                                            |
+| `connection_refused`        | The proxy's connection to the next hop was refused.                                                  |
+| `connection_terminated`     | The proxy's connection to the next hop was closed before any response was received.                  |
+| `connection_timeout`        | The proxy's attempt to open a connection to the next hop timed out.                                  |
+| `connection_read_timeout`   | The proxy was expecting data on a connection but received none within the configured time limit.     |
+| `connection_write_timeout`  | The proxy was attempting to write data to a connection but was unable to.                            |
+| `connection_limit_reached`  | The proxy's configured connection limit to the next hop has been exceeded.                           |
+| `source_addr_in_use`        | The proxy cannot assign a source address when connecting to the next hop.                            |
+| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure).           |
+| `tls_protocol_error`        | The proxy encountered a TLS error when communicating with the next hop.                              |
+| `tls_certificate_error`     | The proxy encountered an error verifying the certificate presented by the next hop.                  |
+| `http_request_error`        | The proxy is generating a client (4xx) response on the origin's behalf.                              |
+| `http_upgrade_failed`       | The HTTP Upgrade between the proxy and the next hop failed.                                          |
+| `http_request_denied`       | The proxy rejected the HTTP request based on its configuration or policy.                            |
+| `proxy_internal_error`      | The proxy encountered an internal error unrelated to the origin.                                     |
+| `proxy_loop_detected`       | The proxy tried to forward the request to itself.                                                    |
+| `http_protocol_error`       | The proxy encountered an HTTP protocol error when communicating with the next hop.                   |
+| `http_response_incomplete`  | The proxy received an incomplete response from the next hop.                                         |
+| `rate_limited`              | The client has reached the maximum number of connections per second to a single origin.              |
diff --git a/src/content/docs/pulumi/tutorial/index.mdx b/src/content/docs/pulumi/tutorial/index.mdx
index a221bc981254072..2d5a00e48f838d0 100644
--- a/src/content/docs/pulumi/tutorial/index.mdx
+++ b/src/content/docs/pulumi/tutorial/index.mdx
@@ -12,19 +12,16 @@ products:
 Before you begin, make sure you [install Pulumi](/pulumi/installing/).
 
 1. [Add a Site](/pulumi/tutorial/add-site/)
-
    - Bring your existing site under Cloudflare with Pulumi IaC.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Zone and DNS records.
 
 2. [Manage secrets](/pulumi/tutorial/manage-secrets/)
-
    - Develop Workers securely with Pulumi ESC and Wrangler.
    - Introduction to the ESC CLI and the Wrangler CLI.
    - Manage Cloudflare credentials, Worker secrets, and `.dev.vars`.
 
 3. [Deploy a Worker](/pulumi/tutorial/hello-world/)
-
    - Brief introduction to deploying a Cloudflare Workers application with Pulumi.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Worker script, Worker route, and DNS record.
diff --git a/src/content/docs/queues/configuration/configure-queues.mdx b/src/content/docs/queues/configuration/configure-queues.mdx
index 67aaf22fcf32e57..cec7b05be692f5a 100644
--- a/src/content/docs/queues/configuration/configure-queues.mdx
+++ b/src/content/docs/queues/configuration/configure-queues.mdx
@@ -15,35 +15,33 @@ import { WranglerConfig, Type } from "~/components";
 
 Cloudflare Queues can be configured using [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Cloudflare's Developer Platform, which includes [Workers](/workers/), [R2](/r2/), and other developer products.
 
-
 Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
 
 Use the options below to configure your queue.
 
 :::note
 
-
 Below are options for queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
 
-
 :::
 
 ## Queue configuration
+
 The following queue level settings can be configured using Wrangler:
 
 ```sh
 npx wrangler queues update <QUEUE-NAME> --delivery-delay-secs 60 --message-retention-period-secs 3000
 ```
 
-* `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
-	* How long a published message is delayed for, before it is delivered to consumers.
-	* Must be between 0 and 86400 (24 hours).
-	* Defaults to 0.
+- `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
+  - How long a published message is delayed for, before it is delivered to consumers.
+  - Must be between 0 and 86400 (24 hours).
+  - Defaults to 0.
 
-* `--message-retention-period-secs`  <Type text="number" /> <Type text="optional" />
-	* How long messages are retained on the Queue.
-	* Defaults to 345600 (4 days).
-	* Must be between 60 and 1209600 (14 days)
+- `--message-retention-period-secs` <Type text="number" /> <Type text="optional" />
+  - How long messages are retained on the Queue.
+  - Defaults to 345600 (4 days).
+  - Must be between 60 and 1209600 (14 days)
 
 ## Producer Worker configuration
 
@@ -68,24 +66,16 @@ To produce to a queue, set up a binding in your Wrangler file. These options sho
 
 </WranglerConfig>
 
+- <code>queue</code> <Type text="string" />
+  - The name of the queue.
 
-
-* <code>queue</code> <Type text="string" />
-
-  * The name of the queue.
-
-* <code>binding</code> <Type text="string" />
-
-  * The name of the binding, which is a JavaScript variable.
-
-
+- <code>binding</code> <Type text="string" />
+  - The name of the binding, which is a JavaScript variable.
 
 ## Consumer Worker Configuration
 
 To consume messages from one or more queues, set up a binding in your Wrangler file. These options should be used when a Worker wants to receive messages from a queue.
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -108,39 +98,29 @@ To consume messages from one or more queues, set up a binding in your Wrangler f
 
 Refer to [Limits](/queues/platform/limits) to review the maximum values for each of these options.
 
+- <code>queue</code> <Type text="string" />
+  - The name of the queue.
 
+- <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of messages allowed in each batch.
+  - Defaults to `10` messages.
 
-* <code>queue</code> <Type text="string" />
-
-  * The name of the queue.
-
-* <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of messages allowed in each batch.
-  * Defaults to `10` messages.
-
-* <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of seconds to wait until a batch is full.
-  * Defaults to `5` seconds.
-
-* <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
-
-  * The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
-  * Defaults to `3` retries.
-
-* <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
-
-  * The name of another queue to send a message if it fails processing at least `max_retries` times.
-  * If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
-  * If there is no queue with the specified name, it will be created automatically.
-
-* <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
+- <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of seconds to wait until a batch is full.
+  - Defaults to `5` seconds.
 
-  * The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
-  * Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
+- <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
+  - Defaults to `3` retries.
 
+- <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
+  - The name of another queue to send a message if it fails processing at least `max_retries` times.
+  - If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
+  - If there is no queue with the specified name, it will be created automatically.
 
+- <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
+  - The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
+  - Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
 ## Pull-based
 
diff --git a/src/content/docs/queues/configuration/consumer-concurrency.mdx b/src/content/docs/queues/configuration/consumer-concurrency.mdx
index 072aa3381bd5001..503b8d2fdba5fa2 100644
--- a/src/content/docs/queues/configuration/consumer-concurrency.mdx
+++ b/src/content/docs/queues/configuration/consumer-concurrency.mdx
@@ -71,7 +71,7 @@ To configure the concurrency settings for your consumer Worker from the dashboar
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select your queue > **Settings**.
 3. Select **Edit Consumer** under Consumer details.
diff --git a/src/content/docs/queues/configuration/index.mdx b/src/content/docs/queues/configuration/index.mdx
index fb230019e4a5916..bc7e0d0237bb4c5 100644
--- a/src/content/docs/queues/configuration/index.mdx
+++ b/src/content/docs/queues/configuration/index.mdx
@@ -8,6 +8,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/configuration/javascript-apis.mdx b/src/content/docs/queues/configuration/javascript-apis.mdx
index 9a34dca675084e9..a948c75c6c39862 100644
--- a/src/content/docs/queues/configuration/javascript-apis.mdx
+++ b/src/content/docs/queues/configuration/javascript-apis.mdx
@@ -94,30 +94,27 @@ A binding that allows a producer to send messages to a Queue.
 
 ```ts
 interface Queue<Body = unknown> {
-  send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
-  sendBatch(messages: Iterable<MessageSendRequest<Body>>, options?: QueueSendBatchOptions): Promise<QueueSendResult>;
-  metrics(): Promise<QueueMetrics>;
+	send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
+	sendBatch(
+		messages: Iterable<MessageSendRequest<Body>>,
+		options?: QueueSendBatchOptions,
+	): Promise<QueueSendResult>;
+	metrics(): Promise<QueueMetrics>;
 }
 ```
 
+- `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
+  - Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+  - When the promise resolves, the message is confirmed to be written to disk.
+  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
 
+- `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
+  - Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
+  - The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
+  - When the promise resolves, the messages are confirmed to be written to disk.
 
-* `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
-
-  * Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-  * When the promise resolves, the message is confirmed to be written to disk.
-  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
-
-* `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
-
-  * Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
-  * The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
-  * When the promise resolves, the messages are confirmed to be written to disk.
-
-* `metrics()` <Type text="Promise<QueueMetrics>" />
-
-  * Returns realtime [QueueMetrics](#queuemetrics) for the queue.
-
+- `metrics()` <Type text="Promise<QueueMetrics>" />
+  - Returns realtime [QueueMetrics](#queuemetrics) for the queue.
 
 ### `MessageSendRequest`
 
@@ -125,54 +122,44 @@ A wrapper type used for sending message batches.
 
 ```ts
 interface MessageSendRequest<Body = unknown> {
-  body: Body;
-  contentType?: QueueContentType;
-  delaySeconds?: number;
+	body: Body;
+	contentType?: QueueContentType;
+	delaySeconds?: number;
 }
 ```
 
+- <code>body</code> <Type text="unknown" />
+  - The body of the message.
+  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
+- <code>contentType</code> <Type text="QueueContentType" />
+  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-* <code>body</code> <Type text="unknown" />
-
-  * The body of the message.
-  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-
-* <code>contentType</code> <Type text="QueueContentType" />
-
-  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  * See [QueuesContentType](#queuescontenttype) for possible values.
-
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be an integer between 0 and 86400 (24 hours).
-
-
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be an integer between 0 and 86400 (24 hours).
 
 ### `QueueSendOptions`
 
 Optional configuration that applies when sending a message to a queue.
 
-* <code>contentType</code> <Type text="QueuesContentType" />
-
-  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  * As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
-  * See [QueuesContentType](#queuescontenttype) for possible values.
+- <code>contentType</code> <Type text="QueuesContentType" />
+  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  - As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
+  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
 
 ### `QueueSendBatchOptions`
 
 Optional configuration that applies when sending a batch of messages to a queue.
 
-* <code>delaySeconds</code> <Type text="number" />
-
-  * The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be a positive integer.
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be a positive integer.
 
 ### `QueuesContentType`
 
@@ -183,17 +170,15 @@ A union type containing valid message content types.
 type QueuesContentType = "text" | "bytes" | "json" | "v8";
 ```
 
-* Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
-* Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
-* Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
-* Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+- Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
+- Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
+- Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+- Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
 
 :::note
 
-
 The default content type for Queues changed to `json` (from `v8`) to improve compatibility with pull-based consumers for any Workers with a [compatibility date](/workers/configuration/compatibility-flags/#queues-send-messages-in-json-format) after `2024-03-18`.
 
-
 :::
 
 If you specify an invalid content type, or if your specified content type does not match the message content's type, the send operation will fail with an error.
@@ -210,15 +195,11 @@ interface QueueSendResult {
 }
 ```
 
+- <code>metadata</code> <Type text="object" />
+  - Contains metadata about the queue after the send operation.
 
-
-* <code>metadata</code> <Type text="object" />
-
-  * Contains metadata about the queue after the send operation.
-
-* <code>metadata.metrics</code> <Type text="QueueMetrics" />
-
-  * Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
+- <code>metadata.metrics</code> <Type text="QueueMetrics" />
+  - Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
 
 ### `QueueMetrics`
 
@@ -232,19 +213,14 @@ interface QueueMetrics {
 }
 ```
 
+- <code>backlogCount</code> <Type text="number" />
+  - The number of messages currently in the queue.
 
+- <code>backlogBytes</code> <Type text="number" />
+  - The total size of messages in the queue, in bytes.
 
-* <code>backlogCount</code> <Type text="number" />
-
-  * The number of messages currently in the queue.
-
-* <code>backlogBytes</code> <Type text="number" />
-
-  * The total size of messages in the queue, in bytes.
-
-* <code>oldestMessageTimestamp</code> <Type text="number" />
-
-  * The timestamp (in milliseconds since epoch) of the oldest message in the queue.
+- <code>oldestMessageTimestamp</code> <Type text="number" />
+  - The timestamp (in milliseconds since epoch) of the oldest message in the queue.
 
 ## Consumer
 
@@ -262,10 +238,8 @@ If the `queue()` function throws, or the promise returned by it or any of the pr
 
 :::note
 
-
 `waitUntil()` is the only supported method to run tasks (such as logging or metrics calls) that resolve after a queue handler has completed. Promises that have not resolved by the time the queue handler returns may not complete and will not block completion of execution.
 
-
 :::
 
 <Tabs syncKey="workersExamples">
@@ -304,19 +278,19 @@ You can type queue messages with `Queue<T>` on the producer and `ExportedHandler
 
 ```ts
 type MyMessage = {
-  id: string;
+	id: string;
 };
 
 interface Env {
-  MY_QUEUE: Queue<MyMessage>;
+	MY_QUEUE: Queue<MyMessage>;
 }
 
 export default {
-  async queue(batch) {
-    for (const message of batch.messages) {
-      console.log(message.body.id);
-    }
-  },
+	async queue(batch) {
+		for (const message of batch.messages) {
+			console.log(message.body.id);
+		}
+	},
 } satisfies ExportedHandler<Env, MyMessage>;
 ```
 
@@ -325,7 +299,7 @@ For primitive messages, use `Queue<number>` or `satisfies ExportedHandler<Env, n
 Or alternatively, a queue consumer can be written using the (deprecated) service worker syntax:
 
 ```js
-addEventListener('queue', (event) => {
+addEventListener("queue", (event) => {
 	event.waitUntil(handleMessages(event));
 });
 ```
@@ -334,10 +308,8 @@ In service worker syntax, `event` provides the same fields and methods as `Messa
 
 :::note
 
-
 When performing asynchronous tasks in your queue handler that iterates through messages, use an asynchronous version of iterating through your messages. For example, `for (const m of batch.messages)`or `await Promise.all(batch.messages.map(work))` allow for waiting for the results of asynchronous calls. `batch.messages.forEach()` does not.
 
-
 :::
 
 ### `MessageBatch`
@@ -346,34 +318,25 @@ A batch of messages that are sent to a consumer Worker.
 
 ```ts
 interface MessageBatch<Body = unknown> {
-  readonly queue: string;
-  readonly messages: readonly Message<Body>[];
-  ackAll(): void;
-  retryAll(options?: QueueRetryOptions): void;
+	readonly queue: string;
+	readonly messages: readonly Message<Body>[];
+	ackAll(): void;
+	retryAll(options?: QueueRetryOptions): void;
 }
 ```
 
+- <code>queue</code> <Type text="string" />
+  - The name of the Queue that belongs to this batch.
 
+- <code>messages</code> <Type text="Message[]" />
+  - An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
 
-* <code>queue</code> <Type text="string" />
-
-  * The name of the Queue that belongs to this batch.
-
-* <code>messages</code> <Type text="Message[]" />
-
-  * An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
-
-* <code>ackAll()</code> <Type text="void" />
-
-
-  * Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
-
-* <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
-
-  * Marks every message to be retried in the next batch.
-  * Supports an optional `options` object.
-
+- <code>ackAll()</code> <Type text="void" />
+  - Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
+- <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
+  - Marks every message to be retried in the next batch.
+  - Supports an optional `options` object.
 
 ### `Message`
 
@@ -381,44 +344,34 @@ A message that is sent to a consumer Worker.
 
 ```ts
 interface Message<Body = unknown> {
-  readonly id: string;
-  readonly timestamp: Date;
-  readonly body: Body;
+	readonly id: string;
+	readonly timestamp: Date;
+	readonly body: Body;
 	readonly attempts: number;
-  ack(): void;
-  retry(options?: QueueRetryOptions): void;
+	ack(): void;
+	retry(options?: QueueRetryOptions): void;
 }
 ```
 
+- <code>id</code> <Type text="string" />
+  - A unique, system-generated ID for the message.
 
+- <code>timestamp</code> <Type text="Date" />
+  - A timestamp when the message was sent.
 
-* <code>id</code> <Type text="string" />
-
-  * A unique, system-generated ID for the message.
-
-* <code>timestamp</code> <Type text="Date" />
-
-  * A timestamp when the message was sent.
-
-* <code>body</code> <Type text="unknown" />
-
-  * The body of the message.
-  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-
-* <code>attempts</code> <Type text="number" />
-
-	* The number of times the consumer has attempted to process this message. Starts at 1.
-
-* <code>ack()</code> <Type text="void" />
-
-  * Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
-
-* <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
+- <code>body</code> <Type text="unknown" />
+  - The body of the message.
+  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
-  * Marks a message to be retried in the next batch.
-  * Supports an optional `options` object.
+- <code>attempts</code> <Type text="number" />
+  - The number of times the consumer has attempted to process this message. Starts at 1.
 
+- <code>ack()</code> <Type text="void" />
+  - Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
+- <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
+  - Marks a message to be retried in the next batch.
+  - Supports an optional `options` object.
 
 ### `QueueRetryOptions`
 
@@ -426,13 +379,13 @@ Optional configuration when marking a message or a batch of messages for retry.
 
 ```ts
 interface QueueRetryOptions {
-  delaySeconds?: number;
+	delaySeconds?: number;
 }
 ```
 
-* <code>delaySeconds</code> <Type text="number" />
+- <code>delaySeconds</code> <Type text="number" />
+  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  - Must be a positive integer.
 
-  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  * Must be a positive integer.
-* When the promise resolves, the messages are written to disk.
-  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+- When the promise resolves, the messages are written to disk.
+  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
diff --git a/src/content/docs/queues/configuration/local-development.mdx b/src/content/docs/queues/configuration/local-development.mdx
index 69ba57856a90286..557fb80e5c067c5 100644
--- a/src/content/docs/queues/configuration/local-development.mdx
+++ b/src/content/docs/queues/configuration/local-development.mdx
@@ -23,6 +23,7 @@ To develop locally with Queues, you will need:
 ## Start a local development session
 
 Open your terminal and run the following commands to start a local development session:
+
 ```sh
 npx wrangler@latest dev
 ```
@@ -40,13 +41,15 @@ Local development sessions create a standalone, local-only environment that mirr
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/general/#dev) to learn more about how to configure a local development session.
 
 ## Separating producer & consumer Workers
+
 Wrangler supports running multiple Workers simultaneously with a single command. If your architecture separates the producer and consumer into distinct Workers, you can use this functionality to test the entire message flow locally.
 
 :::caution
 Support for running multiple Workers at once with one Wrangler command is experimental, and subject to change as we work on the experience. If you run into bugs or have any feedback, [open an issue on the workers-sdk repository](https://github.com/cloudflare/workers-sdk/issues/new)
 :::
 
-For example, if your project has the following directory structure: 
+For example, if your project has the following directory structure:
+
 ```
 producer-worker/
 ├── wrangler.jsonc
@@ -57,6 +60,7 @@ producer-worker/
 ```
 
 You can start development servers for both workers with the following command:
+
 ```sh
 npx wrangler@latest dev -c wrangler.jsonc -c consumer-worker/wrangler.jsonc --persist-to .wrangler/state
 ```
@@ -67,4 +71,5 @@ When the producer Worker sends messages to the queue, the consumer Worker will a
 :::
 
 ## Known Issues
+
 - Queues does not support Wrangler remote mode (`wrangler dev --remote`).
diff --git a/src/content/docs/queues/configuration/pause-purge.mdx b/src/content/docs/queues/configuration/pause-purge.mdx
index 0ca72cdbb02b121..aa3e793a9a0dc2e 100644
--- a/src/content/docs/queues/configuration/pause-purge.mdx
+++ b/src/content/docs/queues/configuration/pause-purge.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - queues
 ---
+
 import { WranglerConfig, Type, MetaInfo } from "~/components";
 
 ## Pause Delivery
@@ -38,9 +39,11 @@ $ npx wrangler queues resume-delivery <QUEUE-NAME>
   - The name of the queue for which delivery should be resumed.
 
 ### What happens to HTTP Pull consumers with a paused queue?
+
 When a queue is paused, messages cannot be pulled by an [HTTP pull based consumer](/queues/configuration/pull-consumers). Requests to pull messages will receive a `409` response, along with an error message stating `queue_delivery_paused`.
 
 ## Purge queue
+
 Purging a queue permanently deletes any messages currently stored in the Queue. Purging is useful while developing a new application, especially to clear out any test data. It can also be useful in production to handle scenarios when a batch of bad messages have been sent to a Queue.
 
 Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the queue.
@@ -50,7 +53,9 @@ Purging a queue is an irreversible operation. Make sure to use this operation ca
 :::
 
 ### Purge queue using Wrangler
+
 The following command will purge messages from your queue. You will be prompted to enter the queue name to confirm the operation.
+
 ```sh
 $ npx wrangler queues purge <QUEUE-NAME>
 
@@ -58,4 +63,5 @@ This operation will permanently delete all the messages in Queue <QUEUE-NAME>. T
 ```
 
 ### Does purging a Queue affect my bill?
+
 Purging a queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.
diff --git a/src/content/docs/queues/event-subscriptions/index.mdx b/src/content/docs/queues/event-subscriptions/index.mdx
index 7fea1b1b89a7a1d..8d7a0aa847de518 100644
--- a/src/content/docs/queues/event-subscriptions/index.mdx
+++ b/src/content/docs/queues/event-subscriptions/index.mdx
@@ -12,7 +12,7 @@ products:
   - workers
 ---
 
-import { LinkCard } from "~/components"
+import { LinkCard } from "~/components";
 
 Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products (e.g., [KV](/kv/), [Workers AI](/workers-ai), [Workers](/workers)) can publish structured events to a queue, which you can then consume with Workers or [HTTP pull consumers](/queues/configuration/pull-consumers/) to build custom workflows, integrations, or logic.
 
@@ -34,4 +34,4 @@ An event is a structured record of something happening in your Cloudflare accoun
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event types and their corresponding data schemas."
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
index aa2f5a7998b8f6d..d7dc089f45b0751 100644
--- a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
+++ b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
@@ -8,11 +8,7 @@ sidebar:
   order: 1
 ---
 
-import {
-	Steps,
-	LinkCard,
-	DashButton,
-} from "~/components";
+import { Steps, LinkCard, DashButton } from "~/components";
 
 Learn how to:
 
@@ -102,4 +98,4 @@ npx wrangler queues subscription delete <queue-name> --id <subscription-id>
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event sources and types that you can subscribe to."
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
index 58bc8f327afbbc5..4875bc7d1174f24 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
@@ -22,7 +22,6 @@ This allows you to write to a Queue from any service or programming language tha
 - A [queue created](/queues/get-started/#3-create-a-queue) via the [Cloudflare dashboard](https://dash.cloudflare.com) or the [wrangler CLI](/workers/wrangler/install-and-update/).
 - A Cloudflare API token with the `Queues Edit` permission.
 
-
 ### 1. Send a test message
 
 To make sure you successfully authenticate and write a message to your queue, use `curl` on the command line:
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
index 45926ceeb6e587d..fb595d622adf56c 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
@@ -66,7 +66,10 @@ export default {
 			messages = await req.json();
 		} catch {
 			// Return a HTTP 400 (Bad Request) if the payload isn't JSON
-			return Response.json({ error: "payload not valid JSON" }, { status: 400 });
+			return Response.json(
+				{ error: "payload not valid JSON" },
+				{ status: 400 },
+			);
 		}
 
 		// Publish to the Queue
diff --git a/src/content/docs/queues/examples/send-errors-to-r2.mdx b/src/content/docs/queues/examples/send-errors-to-r2.mdx
index ba6649a7b277a6a..0ff30d559be40f2 100644
--- a/src/content/docs/queues/examples/send-errors-to-r2.mdx
+++ b/src/content/docs/queues/examples/send-errors-to-r2.mdx
@@ -63,33 +63,33 @@ interface Env {
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      return doRequest(req);
-    } catch (e) {
-      const error: ErrorMessage = {
-        message: e instanceof Error ? e.message : String(e),
-        stack: e instanceof Error ? e.stack : undefined,
-      };
-      await env.ERROR_QUEUE.send(error);
-      return new Response(error.message, { status: 500 });
-    }
-  },
-  async queue(batch, env, ctx): Promise<void> {
-    let file = "";
-    for (const message of batch.messages) {
-      const error = message.body;
-      file += error.stack ?? error.message;
-      file += "\r\n";
-    }
-    await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			return doRequest(req);
+		} catch (e) {
+			const error: ErrorMessage = {
+				message: e instanceof Error ? e.message : String(e),
+				stack: e instanceof Error ? e.stack : undefined,
+			};
+			await env.ERROR_QUEUE.send(error);
+			return new Response(error.message, { status: 500 });
+		}
+	},
+	async queue(batch, env, ctx): Promise<void> {
+		let file = "";
+		for (const message of batch.messages) {
+			const error = message.body;
+			file += error.stack ?? error.message;
+			file += "\r\n";
+		}
+		await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
+	},
 } satisfies ExportedHandler<Env, ErrorMessage>;
 
 function doRequest(request: Request): Response {
-  if (Math.random() > 0.5) {
-    return new Response("Success!");
-  }
-  throw new Error("Failed!");
+	if (Math.random() > 0.5) {
+		return new Response("Success!");
+	}
+	throw new Error("Failed!");
 }
 ```
diff --git a/src/content/docs/queues/examples/send-messages-from-dash.mdx b/src/content/docs/queues/examples/send-messages-from-dash.mdx
index 6d384b6b6bd668a..1a2b6cc2f1b7455 100644
--- a/src/content/docs/queues/examples/send-messages-from-dash.mdx
+++ b/src/content/docs/queues/examples/send-messages-from-dash.mdx
@@ -22,14 +22,14 @@ To send messages from the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select the queue to send a message to.
 3. Select the **Messages** tab.
 4. Select **Send**.
 5. Choose your message **Content Type**: _Text_ or _JSON_.
-5. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
-6. Select **Send**.
+6. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
+7. Select **Send**.
 
 Your message will be sent to the queue.
 
diff --git a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
index 481b9a11fe9e225..4803ac4d16c217c 100644
--- a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
+++ b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
@@ -73,45 +73,45 @@ Extending the `DurableObject` base class makes your `Env` available on `this.env
 import { DurableObject } from "cloudflare:workers";
 
 interface Env {
-  YOUR_QUEUE: Queue;
-  YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
+	YOUR_QUEUE: Queue;
+	YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    // Assume each Durable Object is mapped to a userId in a query parameter
-    // In a production application, this will be a userId defined by your application
-    // that you validate (and/or authenticate) first.
-    const url = new URL(req.url);
-    const userIdParam = url.searchParams.get("userId");
-
-    if (userIdParam) {
-      // Get a stub that allows you to call that Durable Object
-      const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
-
-      // Pass the request to that Durable Object and await the response
-      // This invokes the constructor once on your Durable Object class (defined further down)
-      // on the first initialization, and the fetch method on each request.
-      // We pass the original Request to the Durable Object's fetch method
-      const response = await durableObjectStub.fetch(req);
-
-      // This would return "wrote to queue", but you could return any response.
-      return response;
-    }
-    return new Response("userId must be provided", { status: 400 });
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		// Assume each Durable Object is mapped to a userId in a query parameter
+		// In a production application, this will be a userId defined by your application
+		// that you validate (and/or authenticate) first.
+		const url = new URL(req.url);
+		const userIdParam = url.searchParams.get("userId");
+
+		if (userIdParam) {
+			// Get a stub that allows you to call that Durable Object
+			const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
+
+			// Pass the request to that Durable Object and await the response
+			// This invokes the constructor once on your Durable Object class (defined further down)
+			// on the first initialization, and the fetch method on each request.
+			// We pass the original Request to the Durable Object's fetch method
+			const response = await durableObjectStub.fetch(req);
+
+			// This would return "wrote to queue", but you could return any response.
+			return response;
+		}
+		return new Response("userId must be provided", { status: 400 });
+	},
 } satisfies ExportedHandler<Env>;
 
 export class YourDurableObject extends DurableObject<Env> {
-  async fetch(req: Request): Promise<Response> {
-    // Error handling elided for brevity.
-    // Publish to your queue
-    await this.env.YOUR_QUEUE.send({
-      id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
-      // Write any other properties to your queue
-    });
-
-    return new Response("wrote to queue");
-  }
+	async fetch(req: Request): Promise<Response> {
+		// Error handling elided for brevity.
+		// Publish to your queue
+		await this.env.YOUR_QUEUE.send({
+			id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
+			// Write any other properties to your queue
+		});
+
+		return new Response("wrote to queue");
+	}
 }
 ```
diff --git a/src/content/docs/queues/glossary.mdx b/src/content/docs/queues/glossary.mdx
index 845aecc4bdd10b3..4bb72d0ab69bbf6 100644
--- a/src/content/docs/queues/glossary.mdx
+++ b/src/content/docs/queues/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - queues
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Queues documentation.
 
diff --git a/src/content/docs/queues/observability/index.mdx b/src/content/docs/queues/observability/index.mdx
index c9ebe21e8103fb1..7becde1ad32ae99 100644
--- a/src/content/docs/queues/observability/index.mdx
+++ b/src/content/docs/queues/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/observability/metrics.mdx b/src/content/docs/queues/observability/metrics.mdx
index e003fb8ca5507e5..39c918a48ff366b 100644
--- a/src/content/docs/queues/observability/metrics.mdx
+++ b/src/content/docs/queues/observability/metrics.mdx
@@ -74,10 +74,10 @@ The `queueMessageOperationsAdaptiveGroups` dataset provides the following dimens
 
 You can access realtime backlog metrics via the [Queues REST API](/api/resources/queues/) and [JavaScript API](/queues/configuration/javascript-apis/). These metrics provide point-in-time values rather than aggregated data.
 
-| Metric                   | Field Name                 | Description                                                    |
-| ------------------------ | -------------------------- | -------------------------------------------------------------- |
-| Backlog count            | `backlog_count`            | Number of messages currently in the queue                      |
-| Backlog bytes            | `backlog_bytes`            | Total size of messages in the queue, in bytes                  |
+| Metric                   | Field Name                    | Description                                                    |
+| ------------------------ | ----------------------------- | -------------------------------------------------------------- |
+| Backlog count            | `backlog_count`               | Number of messages currently in the queue                      |
+| Backlog bytes            | `backlog_bytes`               | Total size of messages in the queue, in bytes                  |
 | Oldest message timestamp | `oldest_message_timestamp_ms` | Timestamp (in milliseconds) of the oldest message in the queue |
 
 To retrieve these metrics via the REST API, use the metrics endpoint (`/accounts/{account_id}/queues/{queue_id}/metrics`).
diff --git a/src/content/docs/queues/platform/index.mdx b/src/content/docs/queues/platform/index.mdx
index a227085598b92e9..db2ed89685726c9 100644
--- a/src/content/docs/queues/platform/index.mdx
+++ b/src/content/docs/queues/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/platform/limits.mdx b/src/content/docs/queues/platform/limits.mdx
index 4ca7f09527545a6..7da1292c246a72b 100644
--- a/src/content/docs/queues/platform/limits.mdx
+++ b/src/content/docs/queues/platform/limits.mdx
@@ -8,42 +8,49 @@ products:
   - queues
 ---
 
-import { Render, WranglerConfig } from "~/components"
+import { Render, WranglerConfig } from "~/components";
 
 :::caution
 The following limits apply to both Workers Paid and Workers Free plans with the exception of **Message Retention**, which is non-configurable at 24 hours for the Workers Free plan.
 :::
 
-| Feature                                       									| Limit                                                         |
-| ----------------------------------------------------------------| ------------------------------------------------------------- |
-| Queues                                        									| 10,000 per account								                            |
-| Message size                                  									| 128 KB <sup>1</sup>                                           |
-| Message retries                               									| 100                                                           |
-| Maximum consumer batch size                   									| 100 messages 								                                  |
-| Maximum messages per `sendBatch` call         									| 100 (or 256KB in total)                                       |
-| Maximum Batch wait time                       									| 60 seconds                                                    |
-| Per-queue message throughput    																| 5,000 messages per second <sup>2</sup>                        |
-| Message retention period <sup>3</sup>         									| [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration). |
-| Per-queue backlog size <sup>4</sup>           									| 25GB                                                          |
-| Concurrent consumer invocations               									| 250 <sup>push-based only</sup>                                |
-| Consumer duration (wall clock time) 														| 15 minutes <sup>5</sup>                                       |
-| [Consumer CPU time](/workers/platform/limits/#cpu-time)| [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) 							|
-| `visibilityTimeout` (pull-based queues)       									| 12 hours                                                      |
-| `delaySeconds` (when sending or retrying)     									| 24 hours                                                      |
-
-<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100 bytes of internal metadata that counts towards total message limits.
-
-<sup>2</sup> Exceeding the maximum message throughput will cause the `send()` and `sendBatch()` methods to throw an exception with a `Too Many Requests` error until your producer falls below the limit.
-
-<sup>3</sup> Messages in a queue that reach the maximum message retention are deleted from the queue. Queues does not delete messages in the same queue that have not reached this limit.
-
-<sup>4</sup> Individual queues that reach this limit will receive a `Storage Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
+| Feature                                                 | Limit                                                                                             |
+| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| Queues                                                  | 10,000 per account                                                                                |
+| Message size                                            | 128 KB <sup>1</sup>                                                                               |
+| Message retries                                         | 100                                                                                               |
+| Maximum consumer batch size                             | 100 messages                                                                                      |
+| Maximum messages per `sendBatch` call                   | 100 (or 256KB in total)                                                                           |
+| Maximum Batch wait time                                 | 60 seconds                                                                                        |
+| Per-queue message throughput                            | 5,000 messages per second <sup>2</sup>                                                            |
+| Message retention period <sup>3</sup>                   | [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration).        |
+| Per-queue backlog size <sup>4</sup>                     | 25GB                                                                                              |
+| Concurrent consumer invocations                         | 250 <sup>push-based only</sup>                                                                    |
+| Consumer duration (wall clock time)                     | 15 minutes <sup>5</sup>                                                                           |
+| [Consumer CPU time](/workers/platform/limits/#cpu-time) | [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) |
+| `visibilityTimeout` (pull-based queues)                 | 12 hours                                                                                          |
+| `delaySeconds` (when sending or retrying)               | 24 hours                                                                                          |
+
+<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100
+bytes of internal metadata that counts towards total message limits.
+
+<sup>2</sup> Exceeding the maximum message throughput will cause the `send()`
+and `sendBatch()` methods to throw an exception with a `Too Many Requests` error
+until your producer falls below the limit.
+
+<sup>3</sup> Messages in a queue that reach the maximum message retention are
+deleted from the queue. Queues does not delete messages in the same queue that
+have not reached this limit.
+
+<sup>4</sup> Individual queues that reach this limit will receive a `Storage
+Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
 
 <sup>5</sup> Refer to [Workers limits](/workers/platform/limits/#cpu-time).
 
 <Render file="limits_increase" product="workers" />
 
 ### Increasing Queue Consumer Worker CPU Limits
+
 [Queue consumer Workers](/queues/reference/how-queues-works/#consumers) are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#account-plan-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O.
 
 By default, the maximum CPU time per consumer Worker invocation is set to 30 seconds, but can be increased by setting `limits.cpu_ms` in your Wrangler configuration:
diff --git a/src/content/docs/queues/platform/pricing.mdx b/src/content/docs/queues/platform/pricing.mdx
index f8336c97f5b08a3..0a2d005b5559044 100644
--- a/src/content/docs/queues/platform/pricing.mdx
+++ b/src/content/docs/queues/platform/pricing.mdx
@@ -11,7 +11,7 @@ products:
   - queues
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="queues_pricing" product="workers" />
 
@@ -19,23 +19,16 @@ import { Render } from "~/components"
 
 If an application writes, reads and deletes (consumes) one million messages a day (in a 30 day month), and each message is less than 64 KB in size, the estimated bill for the month would be:
 
-
-
 |                     | Total Usage           | Free Usage | Billed Usage | Price      |
 | ------------------- | --------------------- | ---------- | ------------ | ---------- |
 | Standard operations | 3 \* 30 \* 1,000,000  | 1,000,000  | 89,000,000   | $35.60     |
 |                     | (write, read, delete) |            |              |            |
 | **TOTAL**           |                       |            |              | **$35.60** |
 
-
-
 An application that writes, reads and deletes (consumes) 100 million \~127 KB messages (each message counts as two 64 KB chunks) per month would have an estimated bill resembling the following:
 
-
-
 |                     | Total Usage                  | Free Usage | Billed Usage | Price       |
 | ------------------- | ---------------------------- | ---------- | ------------ | ----------- |
 | Standard operations | 2 \* 3 \* 100 \* 1,000,000   | 1,000,000  | 599,000,000  | $239.60     |
 |                     | (2x ops for > 64KB messages) |            |              |             |
 | **TOTAL**           |                              |            |              | **$239.60** |
-
diff --git a/src/content/docs/queues/reference/delivery-guarantees.mdx b/src/content/docs/queues/reference/delivery-guarantees.mdx
index 1f78e3276a09305..bd589fd8317c267 100644
--- a/src/content/docs/queues/reference/delivery-guarantees.mdx
+++ b/src/content/docs/queues/reference/delivery-guarantees.mdx
@@ -12,8 +12,8 @@ Delivery guarantees define how strongly a messaging system enforces the delivery
 
 As you make stronger guarantees about message delivery, the system needs to perform more checks and acknowledgments to ensure that messages are delivered, or maintain state to ensure a message is only delivered the specified number of times. This increases the latency of the system and reduces the overall throughput of the system. Each message may require an additional internal acknowledgements, and an equivalent number of additional roundtrips, before it can be considered delivered.
 
-* **Queues provides *at least once* delivery by default** in order to optimize for reliability.
-* This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
-* For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
+- **Queues provides _at least once_ delivery by default** in order to optimize for reliability.
+- This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
+- For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
 
 In cases where processing the same message more than once would introduce unintended behaviour, generating a unique ID when writing the message to the queue and using that as the primary key on database inserts and/or as an idempotency key to de-duplicate the message after processing. For example, using this idempotency key as the ID in an upstream email API or payment API will allow those services to reject the duplicate on your behalf, without you having to carry additional state in your application.
diff --git a/src/content/docs/queues/reference/error-codes.mdx b/src/content/docs/queues/reference/error-codes.mdx
index 1a227b114e29bfe..94d502fd00435b6 100644
--- a/src/content/docs/queues/reference/error-codes.mdx
+++ b/src/content/docs/queues/reference/error-codes.mdx
@@ -17,7 +17,7 @@ For the [JavaScript APIs](/queues/configuration/javascript-apis/), Queues operat
 ```js
 try {
 	await env.MY_QUEUE.send("message", { delaySeconds: 999999 });
-    return new Response("Sent message to the queue");
+	return new Response("Sent message to the queue");
 } catch (error) {
 	console.error(error);
 	return new Response("Failed to send message to the queue", { status: 500 });
@@ -28,20 +28,18 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ```json
 {
-  "errors": [
-    {
-      "code": 7003,
-      "message": "No route for the URI",
-      "documentation_url": "documentation_url",
-      "source": {
-        "pointer": "pointer"
-      }
-    }
-  ],
-  "messages": [
-    "string"
-  ],
-  "success": true
+	"errors": [
+		{
+			"code": 7003,
+			"message": "No route for the URI",
+			"documentation_url": "documentation_url",
+			"source": {
+				"pointer": "pointer"
+			}
+		}
+	],
+	"messages": ["string"],
+	"success": true
 }
 ```
 
@@ -49,19 +47,19 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ### Client side errors
 
-| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                                                                                       |
-| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                                                                                       |
-| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                                                                            |
-| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                                                                             |
-| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                                                                                       |
-| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                                                                                   |
+| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                           |
+| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                           |
+| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                |
+| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                 |
+| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                           |
+| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                       |
 | 10203      | MessageMetadataInvalid   | Invalid message metadata (includes invalid content type and invalid delay) | Ensure `contentType` is one of `text`, `bytes`, `json`, or `v8`. Ensure the message delay does not exceed the [maximum of 24 hours](/queues/platform/limits/) |
-| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                                                                                           |
-| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                                                                             |
-| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                                                                                      |
-| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                                                                                         |
-| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                                                                                                                         |
+| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                               |
+| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                 |
+| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                          |
+| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                             |
+| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                    |
 
 ### 429 type errors
 
diff --git a/src/content/docs/queues/reference/how-queues-works.mdx b/src/content/docs/queues/reference/how-queues-works.mdx
index efc649900122fdd..807d34b52e91d6c 100644
--- a/src/content/docs/queues/reference/how-queues-works.mdx
+++ b/src/content/docs/queues/reference/how-queues-works.mdx
@@ -29,9 +29,9 @@ Queues does not guarantee that messages will be delivered to a consumer in the s
 
 Developers can create multiple queues. Creating multiple queues can be useful to:
 
-* Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
-* Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
-* Configure different batching strategies for each consumer connected to a queue.
+- Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
+- Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
+- Configure different batching strategies for each consumer connected to a queue.
 
 For most applications, a single producer Worker per queue, with a single consumer Worker consuming messages from that queue allows you to logically separate the processing for each of your queues.
 
@@ -43,31 +43,29 @@ For example, if we bound a queue named `my-first-queue` to a binding of `MY_FIRS
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    const message = {
-      url: req.url,
-      method: req.method,
-      headers: Object.fromEntries(req.headers),
-    };
-
-    await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
-    return new Response("Sent!");
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		const message = {
+			url: req.url,
+			method: req.method,
+			headers: Object.fromEntries(req.headers),
+		};
+
+		await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
+		return new Response("Sent!");
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
 :::note
 
-
 You can also use [`context.waitUntil()`](/workers/runtime-apis/context/#waituntil) to send the message without blocking the response.
 
 Note that because `waitUntil()` is non-blocking, any errors raised from the `send()` or `sendBatch()` methods on a queue will be implicitly ignored.
 
-
 :::
 
 A queue can have multiple producer Workers. For example, you may have multiple producer Workers writing events or logs to a shared queue based on incoming HTTP requests from users. There is no limit to the total number of producer Workers that can write to a single queue.
@@ -82,25 +80,25 @@ To explicitly set the content type or specify an alternative content type, pass
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    const message = {
-      url: req.url,
-      method: req.method,
-      headers: Object.fromEntries(req.headers),
-    };
-    try {
-      await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
-      return new Response("Sent!");
-    } catch (e) {
-      // Catch cases where send fails, including due to a mismatched content type
-      const msg = e instanceof Error ? e.message : "Unknown error";
-      return Response.json({ error: msg }, { status: 500 });
-    }
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		const message = {
+			url: req.url,
+			method: req.method,
+			headers: Object.fromEntries(req.headers),
+		};
+		try {
+			await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
+			return new Response("Sent!");
+		} catch (e) {
+			// Catch cases where send fails, including due to a mismatched content type
+			const msg = e instanceof Error ? e.message : "Unknown error";
+			return Response.json({ error: msg }, { status: 500 });
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -108,21 +106,21 @@ To only accept simple strings when writing to a queue, set `{ contentType: "text
 
 ```ts
 interface Env {
-  readonly MY_FIRST_QUEUE: Queue;
+	readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      // This will throw an exception (error) if you pass a non-string to the queue,
-      // such as a native JavaScript object or ArrayBuffer.
-      await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
-      return new Response("Sent!");
-    } catch (e) {
-      const msg = e instanceof Error ? e.message : "Unknown error";
-      return Response.json({ error: msg }, { status: 500 });
-    }
-  },
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			// This will throw an exception (error) if you pass a non-string to the queue,
+			// such as a native JavaScript object or ArrayBuffer.
+			await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
+			return new Response("Sent!");
+		} catch (e) {
+			const msg = e instanceof Error ? e.message : "Unknown error";
+			return Response.json({ error: msg }, { status: 500 });
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -139,22 +137,22 @@ A queue can only have one type of consumer configured.
 
 ### Create a consumer Worker
 
-A consumer is the term for a client that is subscribing to or *consuming* messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
+A consumer is the term for a client that is subscribing to or _consuming_ messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
 
 ```ts
 interface Env {
-  // Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
+	// Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
 }
 
 export default {
-  async queue(batch, env, ctx): Promise<void> {
-    // Do something with messages in the batch
-    // i.e. write to R2 storage, D1 database, or POST to an external API
-    for (const msg of batch.messages) {
-      // Process each message
-      console.log(msg.body);
-    }
-  },
+	async queue(batch, env, ctx): Promise<void> {
+		// Do something with messages in the batch
+		// i.e. write to R2 storage, D1 database, or POST to an external API
+		for (const msg of batch.messages) {
+			// Process each message
+			console.log(msg.body);
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -182,42 +180,40 @@ Importantly, each queue can only have one active consumer. This allows Cloudflar
 
 :::note[Best practice]
 
-
 Configure a single consumer per queue. This both logically separates your queues, and ensures that errors (failures) in processing messages from one queue do not impact your other queues.
 
-
 :::
 
 Notably, you can use the same consumer with multiple queues. The queue handler that defines your consumer Worker will be invoked by the queues it is connected to.
 
-* The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
-* This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
+- The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
+- This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
 
 For example, a consumer configured to consume messages from multiple queues would resemble the following:
 
 ```ts
 interface Env {
-  // Add your bindings here
+	// Add your bindings here
 }
 
 export default {
-  async queue(batch, env, ctx): Promise<void> {
-    // MessageBatch has a `queue` property we can switch on
-    switch (batch.queue) {
-      case "log-queue":
-        // Write the batch to R2
-        break;
-      case "debug-queue":
-        // Write the message to the console or to another queue
-        break;
-      case "email-reset":
-        // Trigger a password reset email via an external API
-        break;
-      default:
-        // Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
-        break;
-    }
-  },
+	async queue(batch, env, ctx): Promise<void> {
+		// MessageBatch has a `queue` property we can switch on
+		switch (batch.queue) {
+			case "log-queue":
+				// Write the batch to R2
+				break;
+			case "debug-queue":
+				// Write the message to the console or to another queue
+				break;
+			case "email-reset":
+				// Trigger a password reset email via an external API
+				break;
+			default:
+				// Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
+				break;
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
diff --git a/src/content/docs/queues/reference/index.mdx b/src/content/docs/queues/reference/index.mdx
index 5470c10d9bcf385..a4b4b60c39f76b3 100644
--- a/src/content/docs/queues/reference/index.mdx
+++ b/src/content/docs/queues/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
index ca3746a34a661dd..1f5af0257e338e5 100644
--- a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
+++ b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
@@ -27,15 +27,15 @@ This page summarizes supported features, limitations, and best practices.
 | 173 scalar functions                                    | Yes       | Math, string, datetime, regex, crypto, array, map, struct, JSON              |
 | 33 aggregate functions                                  | Yes       | Basic, approximate, statistical, bitwise, boolean, positional                |
 | Approximate aggregates                                  | Yes       | `approx_distinct`, `approx_median`, `approx_percentile_cont`, `approx_top_k` |
-| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions           |
+| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions              |
 | CTEs (`WITH ... AS`)                                    | Yes       | Can reference different tables and include JOINs                             |
 | JOINs (INNER, LEFT, RIGHT, FULL OUTER, CROSS)           | Yes       | All standard join types                                                      |
-| Implicit joins (comma FROM)                              | Yes       |                                                                              |
-| Subqueries (`IN`, `NOT IN`)                              | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
-| Subqueries (`EXISTS`, `NOT EXISTS`)                      | Yes       | semi-join and anti-join patterns                                             |
-| Scalar subqueries                                        | Yes       | In SELECT, WHERE, HAVING                                                     |
-| Derived tables (FROM subqueries)                         | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
-| Self-joins                                               | Yes       | Same table with different aliases                                            |
+| Implicit joins (comma FROM)                             | Yes       |                                                                              |
+| Subqueries (`IN`, `NOT IN`)                             | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
+| Subqueries (`EXISTS`, `NOT EXISTS`)                     | Yes       | semi-join and anti-join patterns                                             |
+| Scalar subqueries                                       | Yes       | In SELECT, WHERE, HAVING                                                     |
+| Derived tables (FROM subqueries)                        | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
+| Self-joins                                              | Yes       | Same table with different aliases                                            |
 | Window functions (`OVER`)                               | No        |                                                                              |
 | `SELECT DISTINCT`                                       | No        | Use `approx_distinct`                                                        |
 | `OFFSET`                                                | No        |                                                                              |
@@ -49,44 +49,44 @@ For the full SQL syntax, refer to the [SQL reference](/r2-sql/sql-reference/).
 
 ## Unsupported SQL features
 
-| Feature                                                                       | Error                                                    |
-| :---------------------------------------------------------------------------- | :------------------------------------------------------- |
-| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported`  |
-| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`    |
-| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                             |
-| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`    |
-| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                     |
-| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                     |
-| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                            |
-| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                            |
-| Nested (parenthesized) joins                                                  | Not supported                                            |
-| `LATERAL` derived tables                                                      | Not supported                                            |
-| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                            |
+| Feature                                                                       | Error                                                   |
+| :---------------------------------------------------------------------------- | :------------------------------------------------------ |
+| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported` |
+| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`   |
+| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                            |
+| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`   |
+| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                    |
+| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                    |
+| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                           |
+| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                           |
+| Nested (parenthesized) joins                                                  | Not supported                                           |
+| `LATERAL` derived tables                                                      | Not supported                                           |
+| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                           |
 
 ---
 
 ## Unsupported expression patterns
 
-| Pattern                                                 | Alternative                                                                                       |
-| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------ |
-| `func(DISTINCT ...)` on any aggregate                   | Use `approx_distinct` for counting                                                                |
-| `PERCENTILE_CONT` / `PERCENTILE_DISC`                   | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
-| `MEDIAN`                                                | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
-| `ARRAY_AGG`                                             | No alternative (unsupported for memory safety)                                                    |
-| `STRING_AGG`                                            | No alternative (unsupported for memory safety)                                                    |
-| `NOT IN` subquery on nullable columns                   | Use `NOT EXISTS` with a correlated subquery instead                                               |
+| Pattern                               | Alternative                                                                                       |
+| :------------------------------------ | :------------------------------------------------------------------------------------------------ |
+| `func(DISTINCT ...)` on any aggregate | Use `approx_distinct` for counting                                                                |
+| `PERCENTILE_CONT` / `PERCENTILE_DISC` | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
+| `MEDIAN`                              | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
+| `ARRAY_AGG`                           | No alternative (unsupported for memory safety)                                                    |
+| `STRING_AGG`                          | No alternative (unsupported for memory safety)                                                    |
+| `NOT IN` subquery on nullable columns | Use `NOT EXISTS` with a correlated subquery instead                                               |
 
 ---
 
 ## Runtime constraints
 
-| Constraint                           | Details                                                                                               |
-| :----------------------------------- | :---------------------------------------------------------------------------------------------------- |
+| Constraint                           | Details                                                                                                                                                                                    |
+| :----------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Multi-table queries                  | JOINs, subqueries (IN, EXISTS, scalar, derived tables), and multi-table CTEs are supported. Performance depends on intermediate result size; use WHERE filters to manage join selectivity. |
-| Partitioned and unpartitioned tables  | Both partitioned and unpartitioned Iceberg tables are supported.                                       |
-| Parquet format only                  | No CSV, JSON, or other formats.                                                                       |
-| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                  |
-| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                       |
+| Partitioned and unpartitioned tables | Both partitioned and unpartitioned Iceberg tables are supported.                                                                                                                           |
+| Parquet format only                  | No CSV, JSON, or other formats.                                                                                                                                                            |
+| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                                                                                                       |
+| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                                                                                                            |
 
 ---
 
diff --git a/src/content/docs/r2-sql/reference/wrangler-commands.mdx b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
index 26a591c683434f5..f9765698d06f77d 100644
--- a/src/content/docs/r2-sql/reference/wrangler-commands.mdx
+++ b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { Render, Type, MetaInfo } from "~/components";
 
-<Render file="wrangler-commands/r2-sql" product="workers" />
\ No newline at end of file
+<Render file="wrangler-commands/r2-sql" product="workers" />
diff --git a/src/content/docs/r2-sql/sql-reference/index.mdx b/src/content/docs/r2-sql/sql-reference/index.mdx
index 70227b97d4db20a..58ed3641062a224 100644
--- a/src/content/docs/r2-sql/sql-reference/index.mdx
+++ b/src/content/docs/r2-sql/sql-reference/index.mdx
@@ -194,14 +194,14 @@ R2 SQL supports joining multiple Iceberg tables in a single query. All join type
 
 ### Supported join types
 
-| Join type        | Syntax                              | Description                                                        |
-| :--------------- | :---------------------------------- | :----------------------------------------------------------------- |
-| Inner join       | `INNER JOIN ... ON`                 | Returns rows that match in both tables                             |
-| Left outer join  | `LEFT JOIN ... ON`                  | Returns all rows from the left table, NULLs for non-matching right |
-| Right outer join | `RIGHT JOIN ... ON`                 | Returns all rows from the right table, NULLs for non-matching left |
-| Full outer join  | `FULL OUTER JOIN ... ON`            | Returns all rows from both tables, NULLs where no match            |
-| Cross join       | `CROSS JOIN`                        | Cartesian product of both tables                                   |
-| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id`  | Comma-separated tables with join condition in `WHERE`              |
+| Join type        | Syntax                            | Description                                                        |
+| :--------------- | :-------------------------------- | :----------------------------------------------------------------- |
+| Inner join       | `INNER JOIN ... ON`               | Returns rows that match in both tables                             |
+| Left outer join  | `LEFT JOIN ... ON`                | Returns all rows from the left table, NULLs for non-matching right |
+| Right outer join | `RIGHT JOIN ... ON`               | Returns all rows from the right table, NULLs for non-matching left |
+| Full outer join  | `FULL OUTER JOIN ... ON`          | Returns all rows from both tables, NULLs where no match            |
+| Cross join       | `CROSS JOIN`                      | Cartesian product of both tables                                   |
+| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id` | Comma-separated tables with join condition in `WHERE`              |
 
 ### Syntax
 
@@ -264,6 +264,7 @@ SELECT * FROM (t1 JOIN t2 ON t1.id = t2.id) JOIN t3 ON t2.id = t3.id
 -- Supported
 SELECT * FROM t1 JOIN t2 ON t1.id = t2.id JOIN t3 ON t2.id = t3.id
 ```
+
 :::
 
 ### Best practices for joins
@@ -358,6 +359,7 @@ WHERE NOT EXISTS (
 )
 LIMIT 20
 ```
+
 :::
 
 ### `EXISTS` / `NOT EXISTS` subqueries
diff --git a/src/content/docs/r2/api/error-codes.mdx b/src/content/docs/r2/api/error-codes.mdx
index 49ec6f7e7bff0ec..27e9cbdf09979fb 100644
--- a/src/content/docs/r2/api/error-codes.mdx
+++ b/src/content/docs/r2/api/error-codes.mdx
@@ -16,10 +16,10 @@ For the **Workers API**, R2 operations throw exceptions that you can catch. The
 
 ```js
 try {
-  await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
+	await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
 } catch (error) {
-  console.error(error.message);
-  // "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
+	console.error(error.message);
+	// "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
 }
 ```
 
@@ -37,59 +37,59 @@ For the **S3-compatible API**, errors are returned as XML in the response body:
 
 ### Authentication and authorization errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10002 | Unauthorized | 401 | Missing or invalid authentication credentials. | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired. |
-| 10003 | AccessDenied | 403 | Insufficient permissions for the requested operation. | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
-| 10018 | ExpiredRequest | 400 | Presigned URL or request signature has expired. | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature. |
-| 10035 | SignatureDoesNotMatch | 403 | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues. |
-| 10042 | NotEntitled | 403 | Account not entitled to this feature. | Ensure your account has an [R2 subscription](/r2/pricing/). |
+| Error Code | S3 Code               | HTTP Status | Details                                                | Recommended Fix                                                                                         |
+| ---------- | --------------------- | ----------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
+| 10002      | Unauthorized          | 401         | Missing or invalid authentication credentials.         | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired.    |
+| 10003      | AccessDenied          | 403         | Insufficient permissions for the requested operation.  | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
+| 10018      | ExpiredRequest        | 400         | Presigned URL or request signature has expired.        | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature.                                |
+| 10035      | SignatureDoesNotMatch | 403         | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues.                            |
+| 10042      | NotEntitled           | 403         | Account not entitled to this feature.                  | Ensure your account has an [R2 subscription](/r2/pricing/).                                             |
 
 ### Bucket errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10005 | InvalidBucketName | 400 | Bucket name does not meet naming requirements. | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric. |
-| 10006 | NoSuchBucket | 404 | The specified bucket does not exist. | Verify the bucket name is correct and the bucket exists in your account. |
-| 10008 | BucketNotEmpty | 409 | Cannot delete bucket that contains objects. | Delete all objects in the bucket before deleting the bucket. |
-| 10009 | TooManyBuckets | 400 | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
-| 10073 | BucketConflict | 409 | Bucket name already exists. | Choose a different bucket name. Bucket names must be unique within your account. |
+| Error Code | S3 Code           | HTTP Status | Details                                                     | Recommended Fix                                                                                       |
+| ---------- | ----------------- | ----------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| 10005      | InvalidBucketName | 400         | Bucket name does not meet naming requirements.              | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric.     |
+| 10006      | NoSuchBucket      | 404         | The specified bucket does not exist.                        | Verify the bucket name is correct and the bucket exists in your account.                              |
+| 10008      | BucketNotEmpty    | 409         | Cannot delete bucket that contains objects.                 | Delete all objects in the bucket before deleting the bucket.                                          |
+| 10009      | TooManyBuckets    | 400         | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
+| 10073      | BucketConflict    | 409         | Bucket name already exists.                                 | Choose a different bucket name. Bucket names must be unique within your account.                      |
 
 ### Object errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10007 | NoSuchKey | 404 | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted. |
-| 10020 | InvalidObjectName | 400 | Object key contains invalid characters or is too long. | Use valid UTF-8 characters. Maximum key length is 1024 bytes. |
-| 100100 | EntityTooLarge | 400 | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart). | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
-| 10012 | MetadataTooLarge | 400 | Custom metadata exceeds the 8,192 byte limit. | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata. |
-| 10069 | ObjectLockedByBucketPolicy | 403 | Object is protected by a bucket lock rule and cannot be modified or deleted. | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/). |
+| Error Code | S3 Code                    | HTTP Status | Details                                                                                                                                                         | Recommended Fix                                                                                                                   |
+| ---------- | -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| 10007      | NoSuchKey                  | 404         | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted.                                                             |
+| 10020      | InvalidObjectName          | 400         | Object key contains invalid characters or is too long.                                                                                                          | Use valid UTF-8 characters. Maximum key length is 1024 bytes.                                                                     |
+| 100100     | EntityTooLarge             | 400         | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart).                                                                                     | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
+| 10012      | MetadataTooLarge           | 400         | Custom metadata exceeds the 8,192 byte limit.                                                                                                                   | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata.                                                |
+| 10069      | ObjectLockedByBucketPolicy | 403         | Object is protected by a bucket lock rule and cannot be modified or deleted.                                                                                    | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/).                                      |
 
 ### Upload and request errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10033 | MissingContentLength | 411 | `Content-Length` header required but missing. | Include the `Content-Length` header in PUT/POST requests. |
-| 10013 | IncompleteBody | 400 | Request body terminated before expected `Content-Length`. | Ensure the full request body is sent. Check for network interruptions or client timeouts. |
-| 10014 | InvalidDigest | 400 | Checksum header format is malformed. | Ensure checksums are properly encoded (base64 for SHA/CRC checksums). |
-| 10037 | BadDigest | 400 | Provided checksum does not match the uploaded content. | Verify data integrity and retry the upload. |
-| 10039 | InvalidRange | 416 | Requested byte range is not satisfiable. | Ensure the range start is less than object size. Check `Range` header format. |
-| 10031 | PreconditionFailed | 412 | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
+| Error Code | S3 Code              | HTTP Status | Details                                                                           | Recommended Fix                                                                                                                                                                     |
+| ---------- | -------------------- | ----------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10033      | MissingContentLength | 411         | `Content-Length` header required but missing.                                     | Include the `Content-Length` header in PUT/POST requests.                                                                                                                           |
+| 10013      | IncompleteBody       | 400         | Request body terminated before expected `Content-Length`.                         | Ensure the full request body is sent. Check for network interruptions or client timeouts.                                                                                           |
+| 10014      | InvalidDigest        | 400         | Checksum header format is malformed.                                              | Ensure checksums are properly encoded (base64 for SHA/CRC checksums).                                                                                                               |
+| 10037      | BadDigest            | 400         | Provided checksum does not match the uploaded content.                            | Verify data integrity and retry the upload.                                                                                                                                         |
+| 10039      | InvalidRange         | 416         | Requested byte range is not satisfiable.                                          | Ensure the range start is less than object size. Check `Range` header format.                                                                                                       |
+| 10031      | PreconditionFailed   | 412         | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
 
 ### Multipart upload errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10011 | EntityTooSmall | 400 | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB. |
-| 10024 | NoSuchUpload | 404 | Multipart upload does not exist or was aborted. | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
-| 10025 | InvalidPart | 400 | One or more parts could not be found when completing the upload. | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`. |
-| 10048 | InvalidPart | 400 | All non-trailing parts must have the same size. | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads. |
+| Error Code | S3 Code        | HTTP Status | Details                                                                 | Recommended Fix                                                                                                                                               |
+| ---------- | -------------- | ----------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10011      | EntityTooSmall | 400         | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB.                                                                                                         |
+| 10024      | NoSuchUpload   | 404         | Multipart upload does not exist or was aborted.                         | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
+| 10025      | InvalidPart    | 400         | One or more parts could not be found when completing the upload.        | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`.                                                                 |
+| 10048      | InvalidPart    | 400         | All non-trailing parts must have the same size.                         | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads.                                                  |
 
 ### Service errors
 
-| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
-|------------|------|-------------|---------|-----------------|
-| 10001 | InternalError | 500 | An internal error occurred. | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
-| 10043 | ServiceUnavailable | 503 | Service is temporarily unavailable. | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com). |
-| 10054 | ClientDisconnect | 400 | Client disconnected before request completed. | Check network connectivity and retry. |
-| 10058 | TooManyRequests | 429 | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/). |
+| Error Code | S3 Code            | HTTP Status | Details                                                                                                                   | Recommended Fix                                                                                                   |
+| ---------- | ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| 10001      | InternalError      | 500         | An internal error occurred.                                                                                               | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
+| 10043      | ServiceUnavailable | 503         | Service is temporarily unavailable.                                                                                       | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com).                      |
+| 10054      | ClientDisconnect   | 400         | Client disconnected before request completed.                                                                             | Check network connectivity and retry.                                                                             |
+| 10058      | TooManyRequests    | 429         | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/).               |
diff --git a/src/content/docs/r2/api/index.mdx b/src/content/docs/r2/api/index.mdx
index ea9d2d32f1163c9..c7113b1969a8c64 100644
--- a/src/content/docs/r2/api/index.mdx
+++ b/src/content/docs/r2/api/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 R2 provides three API surfaces for interacting with your data:
 
diff --git a/src/content/docs/r2/api/s3/extensions.mdx b/src/content/docs/r2/api/s3/extensions.mdx
index 79016396a6a9091..3d837887f7d5b66 100644
--- a/src/content/docs/r2/api/s3/extensions.mdx
+++ b/src/content/docs/r2/api/s3/extensions.mdx
@@ -16,13 +16,11 @@ HTTP header names and values may only contain ASCII characters, which is a small
 
 :::caution[Metadata variance]
 
-Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted. 
+Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted.
 :::
 
 These headers map to the `httpMetadata` field in the [R2 bindings](/workers/runtime-apis/bindings/):
 
-
-
 | HTTP Header           | Property Name                     |
 | --------------------- | --------------------------------- |
 | `Content-Encoding`    | `httpMetadata.contentEncoding`    |
@@ -73,8 +71,6 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 `ListBuckets` supports all the same search parameters as `ListObjectsV2` in R2 because some customers may have more than 1,000 buckets. Because tooling, like existing S3 libraries, may not expose a way to set these search parameters, these values may also be sent in via headers. Values in headers take precedence over the search parameters.
 
-
-
 | Search parameter     | HTTP Header             | Meaning                                                           |
 | -------------------- | ----------------------- | ----------------------------------------------------------------- |
 | `prefix`             | `cf-prefix`             | Show buckets with this prefix only.                               |
@@ -85,8 +81,6 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 The XML response contains a `NextContinuationToken` and `IsTruncated` elements as appropriate. Since these may not be accessible from existing S3 APIs, these are also available in response headers:
 
-
-
 | XML Response Element    | HTTP Response Header         | Meaning                                                                                        |
 | ----------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------- |
 | `IsTruncated`           | `cf-is-truncated`            | This is set to `true` if the list of buckets returned is not all the buckets on the account.   |
@@ -101,15 +95,15 @@ The XML response contains a `NextContinuationToken` and `IsTruncated` elements a
 
 :::note
 
-This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81). 
+This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81).
 :::
 
 `CopyObject` already supports conditions that relate to the source object through the `x-amz-copy-source-if-...` headers as part of our compliance with the S3 API. In addition to this, R2 supports an R2 specific set of headers that allow the `CopyObject` operation to be conditional on the target object:
 
-* `cf-copy-destination-if-match`
-* `cf-copy-destination-if-none-match`
-* `cf-copy-destination-if-modified-since`
-* `cf-copy-destination-if-unmodified-since`
+- `cf-copy-destination-if-match`
+- `cf-copy-destination-if-none-match`
+- `cf-copy-destination-if-modified-since`
+- `cf-copy-destination-if-unmodified-since`
 
 These headers work akin to the similarly named conditional headers supported on `PutObject`. When the preceding state of the destination object to does not match the specified conditions the `CopyObject` operation will be rejected with a `412 PreconditionFailed` error code.
 
diff --git a/src/content/docs/r2/api/s3/presigned-urls.mdx b/src/content/docs/r2/api/s3/presigned-urls.mdx
index 4b4c1fc51449c91..bda593cdc55a82e 100644
--- a/src/content/docs/r2/api/s3/presigned-urls.mdx
+++ b/src/content/docs/r2/api/s3/presigned-urls.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import {Tabs, TabItem, LinkCard } from "~/components";
+import { Tabs, TabItem, LinkCard } from "~/components";
 
 Presigned URLs are an [S3 concept](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) for granting temporary access to objects without exposing your API credentials. A presigned URL includes signature parameters in the URL itself, authorizing anyone with the URL to perform a specific operation (like `GetObject` or `PutObject`) on a specific object until the URL expires.
 
@@ -24,10 +24,10 @@ Presigned URLs are generated client-side with no communication with R2, requirin
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern | Grants | Good for |
-| --- | --- | --- |
-| Presigned URLs (this page) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
-| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
+| Pattern                                                    | Grants                                                                                                         | Good for                                                                                                                   |
+| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Presigned URLs (this page)                                 | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
 
 ## Generate a presigned URL
 
@@ -136,6 +136,7 @@ aws s3 presign --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com \
 </Tabs>
 
 For complete examples and additional operations, refer to the SDK-specific documentation:
+
 - [AWS SDK for JavaScript](/r2/examples/aws/aws-sdk-js-v3/#generate-presigned-urls)
 - [AWS SDK for Python (Boto3)](/r2/examples/aws/boto3/#generate-presigned-urls)
 - [AWS CLI](/r2/examples/aws/aws-cli/#generate-presigned-urls)
diff --git a/src/content/docs/r2/api/s3/temporary-credentials.mdx b/src/content/docs/r2/api/s3/temporary-credentials.mdx
index eabe88c5d475d9f..42a48a5428e8ec4 100644
--- a/src/content/docs/r2/api/s3/temporary-credentials.mdx
+++ b/src/content/docs/r2/api/s3/temporary-credentials.mdx
@@ -16,10 +16,10 @@ Use temporary credentials to delegate access without issuing a long-lived token.
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern | Grants | Good for |
-| --- | --- | --- |
-| Temporary credentials (this page) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
-| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| Pattern                                      | Grants                                                                                                         | Good for                                                                                                                   |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Temporary credentials (this page)            | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
+| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
 
 ## Generate temporary credentials
 
@@ -108,11 +108,11 @@ For example, `actions: ["GetObject", "HeadObject"]` grants read of individual ob
 
 Valid actions:
 
-| Category | Actions |
-| --- | --- |
-| Read | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
-| Write | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject` |
-| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload` |
+| Category  | Actions                                                                                                               |
+| --------- | --------------------------------------------------------------------------------------------------------------------- |
+| Read      | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
+| Write     | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject`                                                            |
+| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload`            |
 
 ### Paths
 
@@ -122,8 +122,8 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-  "prefixes": ["uploads/user-123/"],
-  "objects": ["shared/manifest.json"]
+	"prefixes": ["uploads/user-123/"],
+	"objects": ["shared/manifest.json"],
 }
 ```
 
@@ -131,10 +131,10 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-  "paths": {
-    "prefixPaths": ["uploads/user-123/"],
-    "objectPaths": ["shared/manifest.json"]
-  }
+	"paths": {
+		"prefixPaths": ["uploads/user-123/"],
+		"objectPaths": ["shared/manifest.json"],
+	},
 }
 ```
 
@@ -205,25 +205,25 @@ Treat temporary credentials as bearer tokens. Anyone in possession of all three
 ## Related resources
 
 <LinkCard
-  title="Authenticate against R2 with temporary credentials"
-  href="/r2/examples/authenticate-r2-temp-credentials/"
-  description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
+	title="Authenticate against R2 with temporary credentials"
+	href="/r2/examples/authenticate-r2-temp-credentials/"
+	description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
 />
 
 <LinkCard
-  title="Presigned URLs"
-  href="/r2/api/s3/presigned-urls/"
-  description="Grant single-operation access to a specific object without issuing credentials."
+	title="Presigned URLs"
+	href="/r2/api/s3/presigned-urls/"
+	description="Grant single-operation access to a specific object without issuing credentials."
 />
 
 <LinkCard
-  title="R2 API tokens"
-  href="/r2/api/tokens/"
-  description="Create the parent token that temporary credentials derive from."
+	title="R2 API tokens"
+	href="/r2/api/tokens/"
+	description="Create the parent token that temporary credentials derive from."
 />
 
 <LinkCard
-  title="Error codes"
-  href="/r2/api/error-codes/"
-  description="Authentication and authorization error codes returned by R2."
+	title="Error codes"
+	href="/r2/api/error-codes/"
+	description="Authentication and authorization error codes returned by R2."
 />
diff --git a/src/content/docs/r2/api/workers/workers-api-reference.mdx b/src/content/docs/r2/api/workers/workers-api-reference.mdx
index b7489165a08ccee..d60ffa3b2d79709 100644
--- a/src/content/docs/r2/api/workers/workers-api-reference.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-reference.mdx
@@ -103,40 +103,33 @@ class Default(WorkerEntrypoint):
 </Tabs>
 
 - `head` <Type text="(key: string): Promise<R2Object | null>" />
-
   - Retrieves the `R2Object` for the given key containing only object metadata, if the key exists, and `null` if the key does not exist.
 
 - `get` <Type text="(key: string, options?: R2GetOptions): Promise<R2ObjectBody | R2Object | null>" />
-
   - Retrieves the `R2ObjectBody` for the given key containing object metadata and the object body as a <code>ReadableStream</code>, if the key exists, and `null` if the key does not exist.
   - In the event that a precondition specified in <code>options</code> fails, <code>get()</code> returns an <code>R2Object</code> with <code>body</code> undefined.
 
 - `put` <Type text="(key: string, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | null | Blob, options?: R2PutOptions): Promise<R2Object | null>" />
-
   - Stores the given <code>value</code> and metadata under the associated <code>key</code>. Once the write succeeds, returns an `R2Object` containing metadata about the stored Object.
   - In the event that a precondition specified in <code>options</code> fails, <code>put()</code> returns `null`, and the object will not be stored.
   - R2 writes are strongly consistent. Once the Promise resolves, all subsequent read operations will see this key value pair globally.
 
 - `delete` <Type text="(key: string | string[]): Promise<void>" />
-
   - Deletes the given <code>values</code> and metadata under the associated <code>keys</code>. Once the delete succeeds, returns <code>void</code>.
   - R2 deletes are strongly consistent. Once the Promise resolves, all subsequent read operations will no longer see the provided key value pairs globally.
   - Up to 1000 keys may be deleted per call.
 
 - `list` <Type text="(options?: R2ListOptions): Promise<R2Objects>" />
-
-  * Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
-  * The returned list of objects is ordered lexicographically.
-  * Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
-  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
+  - Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
+  - The returned list of objects is ordered lexicographically.
+  - Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
+  - To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
 
 * `createMultipartUpload` <Type text="(key: string, options?: R2MultipartOptions): Promise<R2MultipartUpload>" />
-
   - Creates a multipart upload.
   - Returns Promise which resolves to an `R2MultipartUpload` object representing the newly created multipart upload. Once the multipart upload has been created, the multipart upload can be immediately interacted with globally, either through the Workers API, or through the S3 API.
 
 - `resumeMultipartUpload` <Type text="(key: string, uploadId: string): R2MultipartUpload" />
-
   - Returns an object representing a multipart upload with the given key and uploadId.
   - The resumeMultipartUpload operation does not perform any checks to ensure the validity of the uploadId, nor does it verify the existence of a corresponding active multipart upload. This is done to minimize latency before being able to call subsequent operations on the `R2MultipartUpload` object.
 
@@ -145,15 +138,12 @@ class Default(WorkerEntrypoint):
 `R2Object` is created when you `PUT` an object into an R2 bucket. `R2Object` represents the metadata of an object based on the information provided by the uploader. Every object that you `PUT` into an R2 bucket will have an `R2Object` created.
 
 - `key` <Type text="string" />
-
   - The object's key.
 
 - `version` <Type text="string" />
-
   - Random unique string associated with a specific upload of a key.
 
 - `size` <Type text="number" />
-
   - Size of the object in bytes.
 
 - `etag` <Type text="string" />
@@ -166,39 +156,30 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 - The etag associated with the object upload.
 
 - `httpEtag` <Type text="string" />
-
   - The object's etag, in quotes so as to be returned as a header.
 
 - `uploaded` <Type text="Date" />
-
   - A Date object representing the time the object was uploaded.
 
 - `httpMetadata` <Type text="R2HTTPMetadata" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" />
-
   - A map of custom, user-defined metadata associated with the object.
 
 - `range` <Type text="R2Range" />
-
   - A `R2Range` object containing the returned range of the object.
 
 - `checksums` <Type text="R2Checksums" />
-
   - A `R2Checksums` object containing the stored checksums of the object. Refer to [checksums](#checksums).
 
 - `writeHttpMetadata` <Type text="(headers: Headers): void" />
-
   - Retrieves the `httpMetadata` from the `R2Object` and applies their corresponding HTTP headers to the `Headers` input object. Refer to [HTTP Metadata](#http-metadata).
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
-
   - The storage class associated with the object. Refer to [Storage Classes](#storage-class).
 
 - `ssecKeyMd5` <Type text="string" />
-
   - Hex-encoded MD5 hash of the [SSE-C](/r2/examples/ssec) key used for encryption (if one was provided). Hash can be used to identify which key is needed to decrypt object.
 
 ## `R2ObjectBody` definition
@@ -206,27 +187,21 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 `R2ObjectBody` represents an object's metadata combined with its body. It is returned when you `GET` an object from an R2 bucket. The full list of keys for `R2ObjectBody` includes the list below and all keys inherited from [`R2Object`](#r2object-definition).
 
 - `body` <Type text="ReadableStream" />
-
   - The object's value.
 
 - `bodyUsed` <Type text="boolean" />
-
   - Whether the object's value has been consumed or not.
 
 - `arrayBuffer` <Type text="(): Promise<ArrayBuffer>" />
-
   - Returns a Promise that resolves to an `ArrayBuffer` containing the object's value.
 
 - `text` <Type text="(): Promise<string>" />
-
   - Returns a Promise that resolves to an string containing the object's value.
 
 - `json` <Type text="<T>() : Promise<T>" />
-
   - Returns a Promise that resolves to the given object containing the object's value.
 
 - `blob` <Type text="(): Promise<Blob>" />
-
   - Returns a Promise that resolves to a binary Blob containing the object's value.
 
 ## `R2MultipartUpload` definition
@@ -244,24 +219,19 @@ A multipart upload can be completed or aborted at any time, either through the S
 :::
 
 - `key` <Type text="string" />
-
   - The `key` for the multipart upload.
 
 - `uploadId` <Type text="string" />
-
   - The `uploadId` for the multipart upload.
 
 - `uploadPart` <Type text="(partNumber: number, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | Blob, options?: R2MultipartOptions): Promise<R2UploadedPart>" />
-
   - Uploads a single part with the specified part number to this multipart upload. Each part must be uniform in size with an exception for the final part which can be smaller.
   - Returns an `R2UploadedPart` object containing the `etag` and `partNumber`. These `R2UploadedPart` objects are required when completing the multipart upload.
 
 - `abort` <Type text="(): Promise<void>" />
-
   - Aborts the multipart upload. Returns a Promise that resolves when the upload has been successfully aborted.
 
 - `complete` <Type text="(uploadedParts: R2UploadedPart[]): Promise<R2Object>" />
-
   - Completes the multipart upload with the given parts.
   - Returns a Promise that resolves when the complete operation has finished. Once this happens, the object is immediately accessible globally by any subsequent read operation.
 
@@ -270,15 +240,12 @@ A multipart upload can be completed or aborted at any time, either through the S
 ### R2GetOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
-
   - Specifies that the object should only be returned given satisfaction of certain conditions in the `R2Conditional` or in the conditional Headers. Refer to [Conditional operations](#conditional-operations).
 
 - `range` <Type text="R2Range" />
-
   - Specifies that only a specific length (from an optional offset) or suffix of bytes from the object should be returned. Refer to [Ranged reads](#ranged-reads).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 #### Ranged reads
@@ -292,29 +259,23 @@ There are 3 variations of arguments that can be used in a range:
 - A suffix.
 
 - `offset` <Type text="number" />
-
   - The byte to begin returning data from, inclusive.
 
 - `length` <Type text="number" />
-
   - The number of bytes to return. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 - `suffix` <Type text="number" />
-
   - The number of bytes to return from the end of the file, starting from the last byte. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 ### R2PutOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
-
   - Specifies that the object should only be stored given satisfaction of certain conditions in the `R2Conditional`. Refer to [Conditional operations](#conditional-operations).
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
-
   - A map of custom, user-defined metadata that will be stored with the object.
 
 :::note
@@ -324,73 +285,57 @@ Only a single hashing algorithm can be specified at once.
 :::
 
 - `md5` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A md5 hash to use to check the received object's integrity.
 
 - `sha1` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-1 hash to use to check the received object's integrity.
 
 - `sha256` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-256 hash to use to check the received object's integrity.
 
 - `sha384` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-384 hash to use to check the received object's integrity.
 
 - `sha512` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
-
   - A SHA-512 hash to use to check the received object's integrity.
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
-
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2MultipartOptions
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
-
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
-
   - A map of custom, user-defined metadata that will be stored with the object.
 
 - `storageClass` <Type text="string" />
-
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
-
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2ListOptions
 
 - `limit` <Type text="number" /> <MetaInfo text="optional" />
-
   - The number of results to return. Defaults to `1000`, with a maximum of `1000`.
 
   - If `include` is set, you may receive fewer than `limit` results in your response to accommodate metadata.
 
 - `prefix` <Type text="string" /> <MetaInfo text="optional" />
-
   - The prefix to match keys against. Keys will only be returned if they start with given prefix.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
-
   - An opaque token that indicates where to continue listing objects from. A cursor can be retrieved from a previous list operation.
 
 - `delimiter` <Type text="string" /> <MetaInfo text="optional" />
-
   - The character to use when grouping keys.
 
 - `include` <Type text="Array<string>" /> <MetaInfo text="optional" />
-
   - Can include `httpMetadata` and/or `customMetadata`. If included, items returned by the list will include the specified metadata.
 
   - Note that there is a limit on the total amount of data that a single `list` operation can return. If you request data, you may receive fewer than `limit` results in your response to accommodate metadata.
@@ -435,19 +380,15 @@ while (truncated) {
 An object containing an `R2Object` array, returned by `BUCKET_BINDING.list()`.
 
 - `objects` <Type text="Array<R2Object>" />
-
   - An array of objects matching the `list` request.
 
 - `truncated` boolean
-
   - If true, indicates there are more results to be retrieved for the current `list` request.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
-
   - A token that can be passed to future `list` calls to resume listing from that point. Only present if truncated is true.
 
 - `delimitedPrefixes` <Type text="Array<string>" />
-
   - If a delimiter has been specified, contains all prefixes between the specified prefix and the next occurrence of the delimiter.
 
   - For example, if no prefix is provided and the delimiter is '/', `foo/bar/baz` would return `foo` as a delimited prefix. If `foo/` was passed as a prefix with the same structure and delimiter, `foo/bar` would be returned as a delimited prefix.
@@ -459,19 +400,15 @@ You can pass an `R2Conditional` object to `R2GetOptions` and `R2PutOptions`. If
 If the condition check for `put()` fails, `null` will be returned instead of the `R2Object`.
 
 - `etagMatches` <Type text="string" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object's etag matches the given string.
 
 - `etagDoesNotMatch` <Type text="string" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object's etag does not match the given string.
 
 - `uploadedBefore` <Type text="Date" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object was uploaded before the given date.
 
 - `uploadedAfter` <Type text="Date" /> <MetaInfo text="optional" />
-
   - Performs the operation if the object was uploaded after the given date.
 
 Alternatively, you can pass a `Headers` object containing conditional headers to `R2GetOptions` and `R2PutOptions`. For information on these conditional headers, refer to [the MDN docs on conditional requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditional_requests#conditional_headers). All conditional headers aside from `If-Range` are supported.
@@ -499,23 +436,18 @@ Generally, these fields match the HTTP metadata passed when the object was creat
 If a checksum was provided when using the `put()` binding, it will be available on the returned object under the `checksums` property. The MD5 checksum will be included by default for non-multipart objects.
 
 - `md5` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The MD5 checksum of the object.
 
 - `sha1` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-1 checksum of the object.
 
 - `sha256` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-256 checksum of the object.
 
 - `sha384` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-384 checksum of the object.
 
 - `sha512` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
-
   - The SHA-512 checksum of the object.
 
 ### `R2UploadedPart`
@@ -523,11 +455,9 @@ If a checksum was provided when using the `put()` binding, it will be available
 An `R2UploadedPart` object represents a part that has been uploaded. `R2UploadedPart` objects are returned from `uploadPart` operations and must be passed to `completeMultipartUpload` operations.
 
 - `partNumber` <Type text="number" />
-
   - The number of the part.
 
 - `etag` <Type text="string" />
-
   - The `etag` of the part.
 
 ### Storage Class
diff --git a/src/content/docs/r2/api/workers/workers-api-usage.mdx b/src/content/docs/r2/api/workers/workers-api-usage.mdx
index 6cfb3742ecf0dbe..3201040184b441e 100644
--- a/src/content/docs/r2/api/workers/workers-api-usage.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-usage.mdx
@@ -251,6 +251,7 @@ class Default(WorkerEntrypoint):
 ```
 </TabItem>
 </Tabs>
+
 <Render file="request-dot-clone-warning" product="workers" />
 
 ## 5. Bucket access and privacy
diff --git a/src/content/docs/r2/buckets/bucket-locks.mdx b/src/content/docs/r2/buckets/bucket-locks.mdx
index 464a1623fef1b18..d7bcec562a81685 100644
--- a/src/content/docs/r2/buckets/bucket-locks.mdx
+++ b/src/content/docs/r2/buckets/bucket-locks.mdx
@@ -22,6 +22,7 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Select **Add rule** and enter the rule name, prefix, and retention period.
@@ -97,6 +98,7 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 
@@ -119,6 +121,7 @@ For more information on required parameters and examples of how to get bucket lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Locate the rule you want to remove, select the `...` icon next to it, and then select **Delete**.
diff --git a/src/content/docs/r2/buckets/cors.mdx b/src/content/docs/r2/buckets/cors.mdx
index 509574538198e4b..e377d4c3587d41b 100644
--- a/src/content/docs/r2/buckets/cors.mdx
+++ b/src/content/docs/r2/buckets/cors.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) is a standardized method that prevents domain X from accessing the resources of domain Y. It does so by using special headers in HTTP responses from domain Y, that allow your browser to verify that domain Y permits domain X to access these resources.
 
@@ -56,13 +56,13 @@ The following example allows browser-based uploads from `https://example.com` wi
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -83,6 +83,7 @@ If you set a CORS policy on a bucket that is already serving traffic using a cus
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. Select **Settings**.
 4. Under **CORS Policy**, select **Add CORS policy**.
@@ -99,14 +100,14 @@ You can configure CORS rules using the [Wrangler CLI](/r2/reference/wrangler-com
 
 ```json title="cors.json"
 {
-  "rules": [
-    {
-      "allowed": {
-        "origins": ["https://example.com"],
-        "methods": ["GET"]
-      }
-    }
-  ]
+	"rules": [
+		{
+			"allowed": {
+				"origins": ["https://example.com"],
+				"methods": ["GET"]
+			}
+		}
+	]
 }
 ```
 
@@ -126,13 +127,13 @@ npx wrangler r2 bucket cors list <BUCKET_NAME>
 
 The following fields in an R2 CORS policy map to HTTP response headers. These response headers are only returned when the incoming HTTP request is a valid CORS request.
 
-| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                           | Example                                                                                                                                                                                                                              |
-| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                          | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
-| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                         | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
-| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
+| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                                     | Example                                                                                                                                                                                                                              |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                    | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
+| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                   | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
+| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                          | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
 | `ExposeHeaders`  | Specifies the headers that can be exposed back, and accessed by, the JavaScript making the cross-origin request. If you need to access headers beyond the [safelisted response headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers#examples), such as `Content-Encoding` or `cf-cache-status`, you must specify it here. | `Content-Encoding`, `cf-cache-status`, `Date`                                                                                                                                                                                        |
-| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                         | `3600`                                                                                                                                                                                                                               |
+| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                                   | `3600`                                                                                                                                                                                                                               |
 
 ## Example
 
diff --git a/src/content/docs/r2/buckets/delete-buckets.mdx b/src/content/docs/r2/buckets/delete-buckets.mdx
index cae21c981e67944..71cdbc593f9c6e8 100644
--- a/src/content/docs/r2/buckets/delete-buckets.mdx
+++ b/src/content/docs/r2/buckets/delete-buckets.mdx
@@ -27,6 +27,7 @@ The dashboard provides an **Empty Bucket** action that handles this for you, reg
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you want to empty.
 3. Go to the **Settings** tab.
 4. Scroll to the **Empty Bucket** section.
@@ -86,6 +87,7 @@ You can delete a bucket in various ways.
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you want to delete.
 3. Go to the **Settings** tab.
 4. Scroll to the **Delete Bucket** section. If the bucket is not empty, select **Empty Bucket** first to clear all objects.
@@ -129,25 +131,25 @@ curl -X DELETE "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/r2/bu
 ## Related resources
 
 <LinkCard
-  title="Delete objects"
-  href="/r2/objects/delete-objects/"
-  description="Delete individual objects or folders from an R2 bucket."
+	title="Delete objects"
+	href="/r2/objects/delete-objects/"
+	description="Delete individual objects or folders from an R2 bucket."
 />
 
 <LinkCard
-  title="Bucket locks"
-  href="/r2/buckets/bucket-locks/"
-  description="Prevent accidental deletion by setting retention policies on objects."
+	title="Bucket locks"
+	href="/r2/buckets/bucket-locks/"
+	description="Prevent accidental deletion by setting retention policies on objects."
 />
 
 <LinkCard
-  title="Object lifecycles"
-  href="/r2/buckets/object-lifecycles/"
-  description="Automatically expire objects after a specified period instead of emptying manually."
+	title="Object lifecycles"
+	href="/r2/buckets/object-lifecycles/"
+	description="Automatically expire objects after a specified period instead of emptying manually."
 />
 
 <LinkCard
-  title="Create buckets"
-  href="/r2/buckets/create-buckets/"
-  description="Create a new R2 bucket after deleting an existing one."
+	title="Create buckets"
+	href="/r2/buckets/create-buckets/"
+	description="Create a new R2 bucket after deleting an existing one."
 />
diff --git a/src/content/docs/r2/buckets/event-notifications.mdx b/src/content/docs/r2/buckets/event-notifications.mdx
index b0fe30eb775ad6f..e910f9b896e6223 100644
--- a/src/content/docs/r2/buckets/event-notifications.mdx
+++ b/src/content/docs/r2/buckets/event-notifications.mdx
@@ -26,6 +26,7 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select the bucket you'd like to add an event notification rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Event notifications** card.
 4. Select **Add notification** and choose the queue you'd like to receive notifications and the [type of events](/r2/buckets/event-notifications/#event-types) that will trigger them.
@@ -66,10 +67,10 @@ Event notification rules determine the [event types](/r2/buckets/event-notificat
 
 ## Event types
 
-| Event type | Description | Trigger actions |
-|------------|-------------|----------------|
+| Event type      | Description                                                                 | Trigger actions                                                                      |
+| --------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
 | `object-create` | Triggered when new objects are created or existing objects are overwritten. | <ul><li>`PutObject`</li><li>`CopyObject`</li><li>`CompleteMultipartUpload`</li></ul> |
-| `object-delete` | Triggered when an object is explicitly removed from the bucket. | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul> |
+| `object-delete` | Triggered when an object is explicitly removed from the bucket.             | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul>                         |
 
 ## Message format
 
@@ -95,19 +96,19 @@ Queue consumers receive notifications as [Messages](/queues/configuration/javasc
 
 ### Properties
 
-| Property | Type | Description |
-|----------|------|-------------|
-| `account` | String | The Cloudflare account ID that the event is associated with. |
-| `action` | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
-| `bucket` | String | The name of the bucket where the event occurred. |
-| `object` | Object | A nested object containing details about the object involved in the event. |
-| `object.key` | String | The key (or name) of the object within the bucket. |
-| `object.size` | Number | The size of the object in bytes. Note: not present for object-delete events. |
-| `object.eTag` | String | The entity tag (eTag) of the object. Note: not present for object-delete events. |
-| `eventTime` | String | The time when the action that triggered the event occurred. |
-| `copySource` | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`. |
-| `copySource.bucket` | String | The bucket that contained the source object. |
-| `copySource.object` | String | The name of the source object. |
+| Property            | Type   | Description                                                                                                                                              |
+| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `account`           | String | The Cloudflare account ID that the event is associated with.                                                                                             |
+| `action`            | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
+| `bucket`            | String | The name of the bucket where the event occurred.                                                                                                         |
+| `object`            | Object | A nested object containing details about the object involved in the event.                                                                               |
+| `object.key`        | String | The key (or name) of the object within the bucket.                                                                                                       |
+| `object.size`       | Number | The size of the object in bytes. Note: not present for object-delete events.                                                                             |
+| `object.eTag`       | String | The entity tag (eTag) of the object. Note: not present for object-delete events.                                                                         |
+| `eventTime`         | String | The time when the action that triggered the event occurred.                                                                                              |
+| `copySource`        | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`.                         |
+| `copySource.bucket` | String | The bucket that contained the source object.                                                                                                             |
+| `copySource.object` | String | The name of the source object.                                                                                                                           |
 
 ## Notes
 
diff --git a/src/content/docs/r2/buckets/index.mdx b/src/content/docs/r2/buckets/index.mdx
index 6b32cf898b1518c..56bda3ed5e0d4ce 100644
--- a/src/content/docs/r2/buckets/index.mdx
+++ b/src/content/docs/r2/buckets/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 With object storage, all of your objects are stored in buckets. Buckets do not contain folders that group the individual files, but instead, buckets have a flat structure which simplifies the way you access and retrieve the objects in your bucket.
 
diff --git a/src/content/docs/r2/buckets/object-lifecycles.mdx b/src/content/docs/r2/buckets/object-lifecycles.mdx
index 8aa7719e17e7b1a..0eaef01b4fefed0 100644
--- a/src/content/docs/r2/buckets/object-lifecycles.mdx
+++ b/src/content/docs/r2/buckets/object-lifecycles.mdx
@@ -35,6 +35,7 @@ When you create an object lifecycle rule, you can specify which prefix you would
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object Lifecycle Rules**, select **Add rule**.
@@ -186,6 +187,7 @@ console.log(
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object lifecycle rules**, select the rules you would like to delete.
diff --git a/src/content/docs/r2/buckets/storage-classes.mdx b/src/content/docs/r2/buckets/storage-classes.mdx
index d26bd2b34d5a359..329e212d619b99e 100644
--- a/src/content/docs/r2/buckets/storage-classes.mdx
+++ b/src/content/docs/r2/buckets/storage-classes.mdx
@@ -6,22 +6,22 @@ products:
   - r2
 ---
 
-import { Badge, Tabs, TabItem } from "~/components"
+import { Badge, Tabs, TabItem } from "~/components";
 
 Storage classes allow you to trade off between the cost of storage and the cost of accessing data. Every object stored in R2 has an associated storage class.
 
 All storage classes share the following characteristics:
 
-* Compatible with Workers API, S3 API, and public buckets.
-* 99.999999999% (eleven 9s) of annual durability.
-* No minimum object size.
+- Compatible with Workers API, S3 API, and public buckets.
+- 99.999999999% (eleven 9s) of annual durability.
+- No minimum object size.
 
 ## Available storage classes
 
-| Storage class                  | Minimum storage duration  | Data retrieval fees (processing) | Egress fees (data transfer to Internet)  |
-|--------------------------------|---------------------------|----------------------------------|------------------------------------------|
-| Standard                       | None                      | None                             | None                                     |
-| Infrequent Access              | 30 days                   | Yes                              | None                                     |
+| Storage class     | Minimum storage duration | Data retrieval fees (processing) | Egress fees (data transfer to Internet) |
+| ----------------- | ------------------------ | -------------------------------- | --------------------------------------- |
+| Standard          | None                     | None                             | None                                    |
+| Infrequent Access | 30 days                  | Yes                              | None                                    |
 
 For more information on how storage classes impact pricing, refer to [Pricing](/r2/pricing/).
 
@@ -31,11 +31,11 @@ Standard storage is designed for data that is accessed frequently. This is the d
 
 #### Example use cases
 
-* Website and application data
-* Media content (e.g., images, video)
-* Storing large datasets for analysis and processing
-* AI training data
-* Other workloads involving frequently accessed data
+- Website and application data
+- Media content (e.g., images, video)
+- Storing large datasets for analysis and processing
+- AI training data
+- Other workloads involving frequently accessed data
 
 ### Infrequent Access storage
 
@@ -47,9 +47,9 @@ For objects stored in Infrequent Access storage, you will be charged for the obj
 
 #### Example use cases
 
-* Long-term data archiving (for example, logs and historical records needed for compliance)
-* Data backup and disaster recovery
-* Long tail user-generated content
+- Long-term data archiving (for example, logs and historical records needed for compliance)
+- Data backup and disaster recovery
+- Long tail user-generated content
 
 ## Set default storage class for buckets
 
diff --git a/src/content/docs/r2/data-migration/index.mdx b/src/content/docs/r2/data-migration/index.mdx
index 05a1dabde3c991d..1fc637f6979b11a 100644
--- a/src/content/docs/r2/data-migration/index.mdx
+++ b/src/content/docs/r2/data-migration/index.mdx
@@ -58,4 +58,4 @@ Quickly and easily migrate data from other cloud providers to R2. Explore each o
 	</tbody>
 </table>
 
-For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
\ No newline at end of file
+For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
diff --git a/src/content/docs/r2/data-migration/migration-strategies.mdx b/src/content/docs/r2/data-migration/migration-strategies.mdx
index 9771c0a5eb95eb3..484528cc3c1eabc 100644
--- a/src/content/docs/r2/data-migration/migration-strategies.mdx
+++ b/src/content/docs/r2/data-migration/migration-strategies.mdx
@@ -60,4 +60,4 @@ You can create separate jobs with prefixes such as:
 - `/photos/2024` to migrate all 2024 files
 - `/photos/202` to migrate all files from 2023 and 2024
 
-Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
\ No newline at end of file
+Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
diff --git a/src/content/docs/r2/data-migration/sippy.mdx b/src/content/docs/r2/data-migration/sippy.mdx
index 66ef2a76b92a898..5715798fe2b8a77 100644
--- a/src/content/docs/r2/data-migration/sippy.mdx
+++ b/src/content/docs/r2/data-migration/sippy.mdx
@@ -85,10 +85,10 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 
 When enabled, Sippy exposes metrics that help you understand the progress of your ongoing migrations.
 
-| Metric | Description |
-|--------|-------------|
+| Metric                   | Description                                                                                                                                                    |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Requests served by Sippy | The percentage of overall requests served by R2 over a period of time. A higher percentage indicates that fewer requests need to be made to the source bucket. |
-| Data migrated by Sippy | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes. |
+| Data migrated by Sippy   | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes.                                                 |
 
 To view current and historical metrics:
 
@@ -138,12 +138,12 @@ Cloudflare currently supports copying data from the following cloud object stora
 
 When Sippy is enabled, it changes the behavior of certain actions on your R2 bucket across [Workers](/r2/api/workers/), [S3 API](/r2/api/s3/), and [public buckets](/r2/buckets/public-buckets/).
 
-| Action | New behavior |
-|--------|-------------|
-| GetObject | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
-| HeadObject | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket. |
-| PutObject | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket. |
-| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul> |
+| Action       | New behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| GetObject    | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
+| HeadObject   | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| PutObject    | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 
 Actions not listed above have no change in behavior. For more information, refer to [Workers API reference](/r2/api/workers/workers-api-reference/) or [S3 API compatibility](/r2/api/s3/api/).
 
diff --git a/src/content/docs/r2/data-migration/super-slurper.mdx b/src/content/docs/r2/data-migration/super-slurper.mdx
index 584c6edca51ca0f..9788052b63d58ac 100644
--- a/src/content/docs/r2/data-migration/super-slurper.mdx
+++ b/src/content/docs/r2/data-migration/super-slurper.mdx
@@ -32,6 +32,7 @@ For migration use cases that do not meet the above criteria, we recommend using
 1. In the Cloudflare dashboard, go to the **R2 data migration** page.
 
    <DashButton url="/?to=/:account/r2/slurper" />
+
 2. Select **Migrate files**.
 3. Select the source cloud storage provider that you will be migrating data from.
 4. Enter your source bucket name and associated credentials and select **Next**.
@@ -136,7 +137,11 @@ You can now use this JSON key file when enabling Super Slurper.
 
 ### ETags
 
-<Render file="migrator-etag-caveat" params={{ one: "Super Slurper" }} product="r2" />
+<Render
+	file="migrator-etag-caveat"
+	params={{ one: "Super Slurper" }}
+	product="r2"
+/>
 
 ### Archive storage classes
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
index a4c2c23cbae798d..d603be9a7e32e27 100644
--- a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
@@ -7,7 +7,7 @@ products:
   - r2
 ---
 
-import { PackageManagers, Tabs, TabItem } from '~/components';
+import { PackageManagers, Tabs, TabItem } from "~/components";
 
 The following example shows how to authenticate against R2 using the S3 API and an API token.
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
index 76b0c32d6744f0f..0d2a8e4861600f8 100644
--- a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
@@ -40,14 +40,14 @@ The response wraps the credentials in a `result` object:
 
 ```json
 {
-  "result": {
-    "accessKeyId": "<accessKeyId>",
-    "secretAccessKey": "<secretAccessKey>",
-    "sessionToken": "<sessionToken>"
-  },
-  "errors": [],
-  "messages": [],
-  "success": true
+	"result": {
+		"accessKeyId": "<accessKeyId>",
+		"secretAccessKey": "<secretAccessKey>",
+		"sessionToken": "<sessionToken>"
+	},
+	"errors": [],
+	"messages": [],
+	"success": true
 }
 ```
 
@@ -63,77 +63,77 @@ The following helper signs a JWT with your parent secret access key and derives
 import { SignJWT } from "jose";
 
 type R2Scope =
-  | "object-read-only"
-  | "object-read-write"
-  | "admin-read-only"
-  | "admin-read-write";
+	| "object-read-only"
+	| "object-read-write"
+	| "admin-read-only"
+	| "admin-read-write";
 
 export interface TempCredentialOptions {
-  scope: R2Scope;
-  // Optional: narrow the credential to specific S3 operations.
-  actions?: string[];
-  // Time-to-live in seconds. Defaults to 1 hour.
-  ttlSeconds?: number;
-  // Optional: restrict access to specific prefixes or objects.
-  paths?: { prefixPaths?: string[]; objectPaths?: string[] };
+	scope: R2Scope;
+	// Optional: narrow the credential to specific S3 operations.
+	actions?: string[];
+	// Time-to-live in seconds. Defaults to 1 hour.
+	ttlSeconds?: number;
+	// Optional: restrict access to specific prefixes or objects.
+	paths?: { prefixPaths?: string[]; objectPaths?: string[] };
 }
 
 export async function createTempCredentials(
-  endpoint: string,
-  accountId: string,
-  parentAccessKeyId: string,
-  parentSecretAccessKey: string,
-  bucket: string,
-  opts: TempCredentialOptions,
+	endpoint: string,
+	accountId: string,
+	parentAccessKeyId: string,
+	parentSecretAccessKey: string,
+	bucket: string,
+	opts: TempCredentialOptions,
 ): Promise<{
-  accessKeyId: string;
-  secretAccessKey: string;
-  sessionToken: string;
+	accessKeyId: string;
+	secretAccessKey: string;
+	sessionToken: string;
 }> {
-  const ttl = opts.ttlSeconds ?? 3600;
-
-  const claims: Record<string, unknown> = {
-    bucket,
-    scope: opts.scope,
-  };
-
-  if (opts.actions !== undefined && opts.actions.length > 0) {
-    claims.actions = opts.actions;
-  }
-
-  if (opts.paths !== undefined) {
-    claims.paths = {
-      prefixPaths: opts.paths.prefixPaths ?? [],
-      objectPaths: opts.paths.objectPaths ?? [],
-    };
-  }
-
-  // Sign the JWT with the parent secret access key. R2 validates this signature.
-  const jwt = await new SignJWT(claims)
-    .setProtectedHeader({ alg: "HS256", typ: "JWT" })
-    .setSubject(accountId)
-    .setIssuer(parentAccessKeyId)
-    .setAudience(new URL(endpoint).host)
-    .setIssuedAt()
-    .setExpirationTime(`${ttl}s`)
-    .sign(new TextEncoder().encode(parentSecretAccessKey));
-
-  // The temporary secret access key is the SHA-256 hex digest of the signed JWT.
-  const digest = await crypto.subtle.digest(
-    "SHA-256",
-    new TextEncoder().encode(jwt),
-  );
-  const secretAccessKey = Array.from(new Uint8Array(digest))
-    .map((b) => b.toString(16).padStart(2, "0"))
-    .join("");
-
-  return {
-    // Reuse the parent access key ID as the temporary access key ID.
-    accessKeyId: parentAccessKeyId,
-    secretAccessKey,
-    // The session token is base64("jwt/" + signed JWT).
-    sessionToken: btoa(`jwt/${jwt}`),
-  };
+	const ttl = opts.ttlSeconds ?? 3600;
+
+	const claims: Record<string, unknown> = {
+		bucket,
+		scope: opts.scope,
+	};
+
+	if (opts.actions !== undefined && opts.actions.length > 0) {
+		claims.actions = opts.actions;
+	}
+
+	if (opts.paths !== undefined) {
+		claims.paths = {
+			prefixPaths: opts.paths.prefixPaths ?? [],
+			objectPaths: opts.paths.objectPaths ?? [],
+		};
+	}
+
+	// Sign the JWT with the parent secret access key. R2 validates this signature.
+	const jwt = await new SignJWT(claims)
+		.setProtectedHeader({ alg: "HS256", typ: "JWT" })
+		.setSubject(accountId)
+		.setIssuer(parentAccessKeyId)
+		.setAudience(new URL(endpoint).host)
+		.setIssuedAt()
+		.setExpirationTime(`${ttl}s`)
+		.sign(new TextEncoder().encode(parentSecretAccessKey));
+
+	// The temporary secret access key is the SHA-256 hex digest of the signed JWT.
+	const digest = await crypto.subtle.digest(
+		"SHA-256",
+		new TextEncoder().encode(jwt),
+	);
+	const secretAccessKey = Array.from(new Uint8Array(digest))
+		.map((b) => b.toString(16).padStart(2, "0"))
+		.join("");
+
+	return {
+		// Reuse the parent access key ID as the temporary access key ID.
+		accessKeyId: parentAccessKeyId,
+		secretAccessKey,
+		// The session token is base64("jwt/" + signed JWT).
+		sessionToken: btoa(`jwt/${jwt}`),
+	};
 }
 ```
 
@@ -145,17 +145,17 @@ import { createTempCredentials } from "./temp-credentials";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const creds = await createTempCredentials(
-  R2_URL,
-  ACCOUNT_ID,
-  PARENT_ACCESS_KEY_ID,
-  PARENT_SECRET_ACCESS_KEY,
-  "my-bucket",
-  {
-    scope: "object-read-only",
-    actions: ["GetObject", "HeadObject"],
-    ttlSeconds: 900,
-    paths: { prefixPaths: ["data/"] },
-  },
+	R2_URL,
+	ACCOUNT_ID,
+	PARENT_ACCESS_KEY_ID,
+	PARENT_SECRET_ACCESS_KEY,
+	"my-bucket",
+	{
+		scope: "object-read-only",
+		actions: ["GetObject", "HeadObject"],
+		ttlSeconds: 900,
+		paths: { prefixPaths: ["data/"] },
+	},
 );
 ```
 
@@ -169,10 +169,10 @@ import { AwsClient } from "aws4fetch";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const client = new AwsClient({
-  accessKeyId: ACCESS_KEY_ID,
-  secretAccessKey: SECRET_ACCESS_KEY,
-  sessionToken: SESSION_TOKEN,
-  service: "s3",
+	accessKeyId: ACCESS_KEY_ID,
+	secretAccessKey: SECRET_ACCESS_KEY,
+	sessionToken: SESSION_TOKEN,
+	service: "s3",
 });
 
 // Allowed: object under the data/ prefix.
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
index 8c7b8736c9498a9..1fb6ee02263c766 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
@@ -58,9 +58,7 @@ console.log(await S3.send(new ListBucketsCommand({})));
 //     }
 // }
 
-console.log(
-	await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })),
-);
+console.log(await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })));
 // {
 //     '$metadata': {
 //       httpStatusCode: 200,
@@ -157,13 +155,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -182,5 +180,6 @@ const putUrl = await getSignedUrl(
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
index 3143d3c15d33437..a7845d865d25f16 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
@@ -74,11 +74,11 @@ You can also generate presigned links that can be used to share public read or w
 ```ts
 // Use the expires property to determine how long the presigned link is valid.
 console.log(
-await s3.getSignedUrlPromise("getObject", {
-	Bucket: "my-bucket",
-	Key: "dog.png",
-	Expires: 3600,
-}),
+	await s3.getSignedUrlPromise("getObject", {
+		Bucket: "my-bucket",
+		Key: "dog.png",
+		Expires: 3600,
+	}),
 );
 // You can also create links for operations such as putObject to allow temporary write access to a specific key.
 // Specify ContentType to restrict uploads to a specific file type.
@@ -115,13 +115,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -137,5 +137,6 @@ const putUrl = await s3.getSignedUrlPromise("putObject", {
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
index e19b20b7d19fdd1..ef0c34ebe76c4fc 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
@@ -104,4 +104,3 @@ To download a file using the GET URL:
 ```bash
 curl -X GET "https://<your-presigned-get-url>" -o downloaded-file.txt
 ```
-
diff --git a/src/content/docs/r2/examples/aws/aws4fetch.mdx b/src/content/docs/r2/examples/aws/aws4fetch.mdx
index 6330b4a288944d3..51411a247aef736 100644
--- a/src/content/docs/r2/examples/aws/aws4fetch.mdx
+++ b/src/content/docs/r2/examples/aws/aws4fetch.mdx
@@ -144,13 +144,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -172,5 +172,6 @@ const putUrl = signedRequest.url.toString();
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/boto3.mdx b/src/content/docs/r2/examples/aws/boto3.mdx
index fe1fe466ad3d55c..9dce860b7a623d6 100644
--- a/src/content/docs/r2/examples/aws/boto3.mdx
+++ b/src/content/docs/r2/examples/aws/boto3.mdx
@@ -118,13 +118,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-  {
-    "AllowedOrigins": ["https://example.com"],
-    "AllowedMethods": ["PUT"],
-    "AllowedHeaders": ["Content-Type"],
-    "ExposeHeaders": ["ETag"],
-    "MaxAgeSeconds": 3600
-  }
+	{
+		"AllowedOrigins": ["https://example.com"],
+		"AllowedMethods": ["PUT"],
+		"AllowedHeaders": ["Content-Type"],
+		"ExposeHeaders": ["ETag"],
+		"MaxAgeSeconds": 3600
+	}
 ]
 ```
 
@@ -145,5 +145,6 @@ put_url = s3.generate_presigned_url(
 ```
 
 When a client uses this presigned URL, they must:
+
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/custom-header.mdx b/src/content/docs/r2/examples/aws/custom-header.mdx
index 59695cb8019c958..31c3e784bed5934 100644
--- a/src/content/docs/r2/examples/aws/custom-header.mdx
+++ b/src/content/docs/r2/examples/aws/custom-header.mdx
@@ -45,35 +45,32 @@ print(response)
 `aws-sdk-js-v3` allows the customization of request behavior through the use of its [middleware stack](https://aws.amazon.com/blogs/developer/middleware-stack-modular-aws-sdk-js/). This example adds a middleware to the client which adds a header to every `PutObject` request being made.
 
 ```ts
-import {
-  PutObjectCommand,
-  S3Client,
-} from "@aws-sdk/client-s3";
+import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-  region: "auto", // Required by SDK but not used by R2
-  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-  credentials: {
-    accessKeyId: ACCESS_KEY_ID,
-    secretAccessKey: SECRET_ACCESS_KEY,
-  },
+	region: "auto", // Required by SDK but not used by R2
+	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+	credentials: {
+		accessKeyId: ACCESS_KEY_ID,
+		secretAccessKey: SECRET_ACCESS_KEY,
+	},
 });
 
 client.middlewareStack.add(
-  (next, context) => async (args) => {
-      const r = args.request as RequestInit
-      r.headers["cf-create-bucket-if-missing"] = "true";
+	(next, context) => async (args) => {
+		const r = args.request as RequestInit;
+		r.headers["cf-create-bucket-if-missing"] = "true";
 
-      return await next(args)
-    },
-  { step: 'build', name: 'customHeaders' },
-)
+		return await next(args);
+	},
+	{ step: "build", name: "customHeaders" },
+);
 
 const command = new PutObjectCommand({
-  Bucket: "my_bucket",
-  Key: "my_key",
-  Body: "my_data"
+	Bucket: "my_bucket",
+	Key: "my_key",
+	Body: "my_data",
 });
 
 const response = await client.send(command);
@@ -127,44 +124,40 @@ print(response)
 Here we again configure the header we would like to set by creating a middleware, but this time we add the middleware to the request itself instead of to the whole client.
 
 ```ts
-import {
-  PutObjectCommand,
-  S3Client,
-} from "@aws-sdk/client-s3";
+import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-  region: "auto", // Required by SDK but not used by R2
-  // Provide your Cloudflare account ID
-  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-  credentials: {
-    accessKeyId: ACCESS_KEY_ID,
-    secretAccessKey: SECRET_ACCESS_KEY,
-  },
+	region: "auto", // Required by SDK but not used by R2
+	// Provide your Cloudflare account ID
+	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+	credentials: {
+		accessKeyId: ACCESS_KEY_ID,
+		secretAccessKey: SECRET_ACCESS_KEY,
+	},
 });
 
 const command = new PutObjectCommand({
-  Bucket: "my_bucket",
-  Key: "my_key",
-  Body: "my_data"
+	Bucket: "my_bucket",
+	Key: "my_key",
+	Body: "my_data",
 });
 
-const headers = { 'If-Match': '"29d911f495d1ba7cb3a4d7d15e63236a"' }
+const headers = { "If-Match": '"29d911f495d1ba7cb3a4d7d15e63236a"' };
 command.middlewareStack.add(
-  (next) =>
-    (args) => {
-      const r = args.request as RequestInit
-
-      Object.entries(headers).forEach(
-        ([k, v]: [key: string, value: string]): void => {
-          r.headers[k] = v
-        },
-      )
-
-      return next(args)
-    },
-  { step: 'build', name: 'customHeaders' },
-)
+	(next) => (args) => {
+		const r = args.request as RequestInit;
+
+		Object.entries(headers).forEach(
+			([k, v]: [key: string, value: string]): void => {
+				r.headers[k] = v;
+			},
+		);
+
+		return next(args);
+	},
+	{ step: "build", name: "customHeaders" },
+);
 const response = await client.send(command);
 
 console.log(response);
diff --git a/src/content/docs/r2/examples/cache-api.mdx b/src/content/docs/r2/examples/cache-api.mdx
index 8b5d8ebd9354ccc..c5b5a3f0b9d2437 100644
--- a/src/content/docs/r2/examples/cache-api.mdx
+++ b/src/content/docs/r2/examples/cache-api.mdx
@@ -11,67 +11,64 @@ Use the [Cache API](/workers/runtime-apis/cache/) to store R2 objects in Cloudfl
 
 :::note
 
-
 You will need to [connect a custom domain](/workers/configuration/routing/custom-domains/) or [route](/workers/configuration/routing/routes/) to your Worker in order to use the Cache API. Cache API operations in the Cloudflare Workers dashboard editor, Playground previews, and any `*.workers.dev` deployments will have no impact.
 
-
 :::
 
 ```js
-
 export default {
-  async fetch(request, env, context) {
-    try {
-      const url = new URL(request.url);
-
-      // Construct the cache key from the cache URL
-      const cacheKey = new Request(url.toString(), request);
-      const cache = caches.default;
-
-      // Check whether the value is already available in the cache
-      // if not, you will need to fetch it from R2, and store it in the cache
-      // for future access
-      let response = await cache.match(cacheKey);
-
-      if (response) {
-        console.log(`Cache hit for: ${request.url}.`);
-        return response;
-      }
-
-      console.log(
-        `Response for request url: ${request.url} not present in cache. Fetching and caching request.`
-      );
-
-      // If not in cache, get it from R2
-      const objectKey = url.pathname.slice(1);
-      const object = await env.MY_BUCKET.get(objectKey);
-      if (object === null) {
-        return new Response('Object Not Found', { status: 404 });
-      }
-
-      // Set the appropriate object headers
-      const headers = new Headers();
-      object.writeHttpMetadata(headers);
-      headers.set('etag', object.httpEtag);
-
-      // Cache API respects Cache-Control headers. Setting s-max-age to 10
-      // will limit the response to be in cache for 10 seconds max
-      // Any changes made to the response here will be reflected in the cached value
-      headers.append('Cache-Control', 's-maxage=10');
-
-      response = new Response(object.body, {
-        headers,
-      });
-
-      // Store the fetched response as cacheKey
-      // Use waitUntil so you can return the response without blocking on
-      // writing to cache
-      context.waitUntil(cache.put(cacheKey, response.clone()));
-
-      return response;
-    } catch (e) {
-      return new Response('Error thrown ' + e.message);
-    }
-  },
+	async fetch(request, env, context) {
+		try {
+			const url = new URL(request.url);
+
+			// Construct the cache key from the cache URL
+			const cacheKey = new Request(url.toString(), request);
+			const cache = caches.default;
+
+			// Check whether the value is already available in the cache
+			// if not, you will need to fetch it from R2, and store it in the cache
+			// for future access
+			let response = await cache.match(cacheKey);
+
+			if (response) {
+				console.log(`Cache hit for: ${request.url}.`);
+				return response;
+			}
+
+			console.log(
+				`Response for request url: ${request.url} not present in cache. Fetching and caching request.`,
+			);
+
+			// If not in cache, get it from R2
+			const objectKey = url.pathname.slice(1);
+			const object = await env.MY_BUCKET.get(objectKey);
+			if (object === null) {
+				return new Response("Object Not Found", { status: 404 });
+			}
+
+			// Set the appropriate object headers
+			const headers = new Headers();
+			object.writeHttpMetadata(headers);
+			headers.set("etag", object.httpEtag);
+
+			// Cache API respects Cache-Control headers. Setting s-max-age to 10
+			// will limit the response to be in cache for 10 seconds max
+			// Any changes made to the response here will be reflected in the cached value
+			headers.append("Cache-Control", "s-maxage=10");
+
+			response = new Response(object.body, {
+				headers,
+			});
+
+			// Store the fetched response as cacheKey
+			// Use waitUntil so you can return the response without blocking on
+			// writing to cache
+			context.waitUntil(cache.put(cacheKey, response.clone()));
+
+			return response;
+		} catch (e) {
+			return new Response("Error thrown " + e.message);
+		}
+	},
 };
 ```
diff --git a/src/content/docs/r2/examples/terraform.mdx b/src/content/docs/r2/examples/terraform.mdx
index 70ba59913732088..6298b67ad2b5e29 100644
--- a/src/content/docs/r2/examples/terraform.mdx
+++ b/src/content/docs/r2/examples/terraform.mdx
@@ -7,18 +7,17 @@ products:
   - r2
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="keys" product="r2" /><br/>
+<Render file="keys" product="r2" />
+<br />
 
 This example shows how to configure R2 with Terraform using the [Cloudflare provider](https://github.com/cloudflare/terraform-provider-cloudflare).
 
 :::note[Note for using AWS provider]
 
-
 When using the Cloudflare Terraform provider, you can only manage buckets. To configure items such as CORS and object lifecycles, you will need to use the [AWS Provider](/r2/examples/terraform-aws/).
 
-
 :::
 
 With [`terraform`](https://developer.hashicorp.com/terraform/downloads) installed, create `main.tf` and copy the content below replacing with your API Token.
diff --git a/src/content/docs/r2/get-started/cli.mdx b/src/content/docs/r2/get-started/cli.mdx
index 96eb679c9c1e3f1..9d545d0ef4b0755 100644
--- a/src/content/docs/r2/get-started/cli.mdx
+++ b/src/content/docs/r2/get-started/cli.mdx
@@ -8,7 +8,14 @@ products:
   - r2
 ---
 
-import { PackageManagers, LinkCard, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	PackageManagers,
+	LinkCard,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 Manage R2 buckets and objects directly from your terminal. Use CLI tools to automate tasks and manage objects.
 
diff --git a/src/content/docs/r2/get-started/index.mdx b/src/content/docs/r2/get-started/index.mdx
index f23578ee0cbb2f0..dd498e4f6f5b795 100644
--- a/src/content/docs/r2/get-started/index.mdx
+++ b/src/content/docs/r2/get-started/index.mdx
@@ -16,6 +16,7 @@ Cloudflare R2 Storage allows developers to store large amounts of unstructured d
 ## Before you begin
 
 You need a Cloudflare account with an R2 subscription. If you do not have one:
+
 1. Go to the [Cloudflare Dashboard](https://dash.cloudflare.com/).
 2. Select **Storage & databases > R2 > Overview**
 3. Complete the checkout flow to add an R2 subscription to your account.
diff --git a/src/content/docs/r2/get-started/s3.mdx b/src/content/docs/r2/get-started/s3.mdx
index d8f07cb88333887..30f8f11008b2c09 100644
--- a/src/content/docs/r2/get-started/s3.mdx
+++ b/src/content/docs/r2/get-started/s3.mdx
@@ -8,7 +8,14 @@ products:
   - r2
 ---
 
-import { LinkCard, PackageManagers, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	LinkCard,
+	PackageManagers,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 R2 provides support for a [S3-compatible API](/r2/api/s3/api/), which means you can use any S3 SDK, library, or tool to interact with your buckets. If you have existing code that works with S3, you can use it with R2 by changing the endpoint URL.
 
diff --git a/src/content/docs/r2/get-started/workers-api.mdx b/src/content/docs/r2/get-started/workers-api.mdx
index 2fca2b0febc4696..408785ea7255ff2 100644
--- a/src/content/docs/r2/get-started/workers-api.mdx
+++ b/src/content/docs/r2/get-started/workers-api.mdx
@@ -15,7 +15,7 @@ import {
 	Render,
 	Tabs,
 	TabItem,
-	Steps
+	Steps,
 } from "~/components";
 
 [Workers](/workers/) let you run code at the edge. When you bind an R2 bucket to a Worker, you can read and write objects directly using the [Workers API](/r2/api/workers/workers-api-usage/).
diff --git a/src/content/docs/r2/objects/delete-objects.mdx b/src/content/docs/r2/objects/delete-objects.mdx
index a890b14c861b46d..30dedcd5ba096ac 100644
--- a/src/content/docs/r2/objects/delete-objects.mdx
+++ b/src/content/docs/r2/objects/delete-objects.mdx
@@ -17,6 +17,7 @@ You can delete objects from R2 using the dashboard, Workers API, S3 API, or comm
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. (Optional) Select the **View prefixes as directories** checkbox to view prefixes grouped as [folders](/r2/objects/#prefixes-and-folders).
 4. Select the objects or folders you want to delete. You can select a mix of both in the same operation.
@@ -110,19 +111,19 @@ wrangler r2 object delete test-bucket/image.png
 ## Related resources
 
 <LinkCard
-  title="Delete buckets"
-  href="/r2/buckets/delete-buckets/"
-  description="Empty all objects from a bucket and permanently delete it."
+	title="Delete buckets"
+	href="/r2/buckets/delete-buckets/"
+	description="Empty all objects from a bucket and permanently delete it."
 />
 
 <LinkCard
-  title="Bucket locks"
-  href="/r2/buckets/bucket-locks/"
-  description="Protect objects from accidental deletion with retention policies."
+	title="Bucket locks"
+	href="/r2/buckets/bucket-locks/"
+	description="Protect objects from accidental deletion with retention policies."
 />
 
 <LinkCard
-  title="Object lifecycles"
-  href="/r2/buckets/object-lifecycles/"
-  description="Automatically expire objects after a specified period."
+	title="Object lifecycles"
+	href="/r2/buckets/object-lifecycles/"
+	description="Automatically expire objects after a specified period."
 />
diff --git a/src/content/docs/r2/objects/download-objects.mdx b/src/content/docs/r2/objects/download-objects.mdx
index d060979a0b675d4..78ebe64fe9940ee 100644
--- a/src/content/docs/r2/objects/download-objects.mdx
+++ b/src/content/docs/r2/objects/download-objects.mdx
@@ -17,6 +17,7 @@ You can download objects from R2 using the dashboard, Workers API, S3 API, or co
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Locate the object you want to download.
 4. Select **...** for the object and click **Download**.
@@ -108,4 +109,4 @@ Use [Wrangler](/workers/wrangler/install-and-update/) to download objects. Run t
 wrangler r2 object get test-bucket/image.png
 ```
 
-The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
\ No newline at end of file
+The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
diff --git a/src/content/docs/r2/objects/index.mdx b/src/content/docs/r2/objects/index.mdx
index 7cee8cf9e982a0c..147e55a78a576d7 100644
--- a/src/content/docs/r2/objects/index.mdx
+++ b/src/content/docs/r2/objects/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing, Render } from "~/components";
 
 Objects are individual files or data that you store in an R2 bucket. Each object is identified by its key, a string like `images/photo.png`.
 
@@ -22,4 +22,4 @@ The R2 dashboard groups objects that share a common prefix into folders when the
 
 <DirectoryListing />
 
-<Render file="link-to-workers-r2-api" product="r2"/>
\ No newline at end of file
+<Render file="link-to-workers-r2-api" product="r2" />
diff --git a/src/content/docs/r2/platform/audit-logs.mdx b/src/content/docs/r2/platform/audit-logs.mdx
index 56b604e8c1363a0..ca1e6d74b1b1059 100644
--- a/src/content/docs/r2/platform/audit-logs.mdx
+++ b/src/content/docs/r2/platform/audit-logs.mdx
@@ -22,18 +22,18 @@ For more information on how to access and use audit logs, refer to [Review audit
 
 The following configuration actions are logged:
 
-| Operation | Description |
-|-----------|-------------|
-| CreateBucket | Creation of a new bucket. |
-| DeleteBucket | Deletion of an existing bucket. |
-| AddCustomDomain | Addition of a custom domain to a bucket. |
-| RemoveCustomDomain | Removal of a custom domain from a bucket. |
-| ChangeBucketVisibility | Change to the managed public access (`r2.dev`) settings of a bucket. |
-| PutBucketStorageClass | Change to the default storage class of a bucket. |
-| PutBucketLifecycleConfiguration | Change to the object lifecycle configuration of a bucket. |
-| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket. |
-| PutBucketCors | Change to the CORS configuration for a bucket. |
-| DeleteBucketCors | Deletion of the CORS configuration for a bucket. |
+| Operation                          | Description                                                          |
+| ---------------------------------- | -------------------------------------------------------------------- |
+| CreateBucket                       | Creation of a new bucket.                                            |
+| DeleteBucket                       | Deletion of an existing bucket.                                      |
+| AddCustomDomain                    | Addition of a custom domain to a bucket.                             |
+| RemoveCustomDomain                 | Removal of a custom domain from a bucket.                            |
+| ChangeBucketVisibility             | Change to the managed public access (`r2.dev`) settings of a bucket. |
+| PutBucketStorageClass              | Change to the default storage class of a bucket.                     |
+| PutBucketLifecycleConfiguration    | Change to the object lifecycle configuration of a bucket.            |
+| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket.         |
+| PutBucketCors                      | Change to the CORS configuration for a bucket.                       |
+| DeleteBucketCors                   | Deletion of the CORS configuration for a bucket.                     |
 
 :::note
 Logs for data access operations, such as `GetObject` and `PutObject`, are not included in audit logs. To log HTTP requests made to public R2 buckets, use the [HTTP requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) Logpush dataset.
@@ -45,23 +45,22 @@ Below is an example of an audit log entry showing the creation of a new bucket:
 
 ```json
 {
-  "action": { "info": "CreateBucket", "result": true, "type": "create" },
-  "actor": {
-    "email": "<ACTOR_EMAIL>",
-    "id": "3f7b730e625b975bc1231234cfbec091",
-    "ip": "fe32:43ed:12b5:526::1d2:13",
-    "type": "user"
-  },
-  "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-  "interface": "API",
-  "metadata": { "zone_name": "r2.cloudflarestorage.com" },
-  "newValue": "",
-  "newValueJson": {},
-  "oldValue": "",
-  "oldValueJson": {},
-  "owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
-  "resource": { "id": "my-bucket", "type": "r2.bucket" },
-  "when": "2024-07-15T16:32:52.412Z"
+	"action": { "info": "CreateBucket", "result": true, "type": "create" },
+	"actor": {
+		"email": "<ACTOR_EMAIL>",
+		"id": "3f7b730e625b975bc1231234cfbec091",
+		"ip": "fe32:43ed:12b5:526::1d2:13",
+		"type": "user"
+	},
+	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+	"interface": "API",
+	"metadata": { "zone_name": "r2.cloudflarestorage.com" },
+	"newValue": "",
+	"newValueJson": {},
+	"oldValue": "",
+	"oldValueJson": {},
+	"owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
+	"resource": { "id": "my-bucket", "type": "r2.bucket" },
+	"when": "2024-07-15T16:32:52.412Z"
 }
-
 ```
diff --git a/src/content/docs/r2/platform/metrics-analytics.mdx b/src/content/docs/r2/platform/metrics-analytics.mdx
index 91288c6dcf21e47..e28dc53a56af003 100644
--- a/src/content/docs/r2/platform/metrics-analytics.mdx
+++ b/src/content/docs/r2/platform/metrics-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 R2 exposes analytics that allow you to inspect the requests and storage of the buckets in your account.
 
@@ -16,8 +16,8 @@ The metrics displayed for a bucket in the [Cloudflare dashboard](https://dash.cl
 
 R2 currently has two datasets:
 
-| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                          |
-| --------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- |
+| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                                  |
+| --------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------- |
 | Operations                              | `r2OperationsAdaptiveGroups`                         | This dataset consists of the operations taken on a bucket within an account. |
 | Storage                                 | `r2StorageAdaptiveGroups`                            | This dataset consists of the storage of a bucket within an account.          |
 
@@ -58,6 +58,7 @@ Per-bucket analytics for R2 are available in the Cloudflare dashboard. To view c
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/r2/platform/troubleshooting.mdx b/src/content/docs/r2/platform/troubleshooting.mdx
index e42a38c8bff9748..726ef97a385e92b 100644
--- a/src/content/docs/r2/platform/troubleshooting.mdx
+++ b/src/content/docs/r2/platform/troubleshooting.mdx
@@ -21,6 +21,7 @@ If you do have a CORS issue, refer to [Resolving CORS issues](#if-it-is-actually
 1. Open developer tools on your browser.
 2. Go to the **Network** tab and find the failing request. You may need to reload the page, as requests are only logged after developer tools have been opened.
 3. Check the response headers for the following two headers:
+
 - `cf-cache-status`
 - `cf-mitigated`
 
@@ -64,7 +65,7 @@ If your users are directly uploading to the bucket (for example, using the S3 or
 
 ### Bucket sharding
 
-For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket.  While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
+For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket. While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
 
 ## Objects named `This object is unnamed`
 
@@ -84,4 +85,4 @@ For example, uploading an object named `example/` into an R2 bucket will be disp
 <FileTree>
 - example
   - `This object is unnamed`
-</FileTree>
\ No newline at end of file
+</FileTree>
diff --git a/src/content/docs/r2/pricing.mdx b/src/content/docs/r2/pricing.mdx
index 7c3d3a55663af73..6d420e4740d8b39 100644
--- a/src/content/docs/r2/pricing.mdx
+++ b/src/content/docs/r2/pricing.mdx
@@ -27,13 +27,13 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 ## R2 pricing
 
-|                                    | Standard storage         | Infrequent Access storage                               |
-| ---------------------------------- | ------------------------ | ------------------------------------------------------- |
-| Storage                            | $0.015 / GB-month        | $0.01 / GB-month                                        |
-| Class A Operations                 | $4.50 / million requests | $9.00 / million requests                                |
-| Class B Operations                 | $0.36 / million requests | $0.90 / million requests                                |
-| Data Retrieval (processing)        | None                     | $0.01 / GB                                              |
-| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                                               |
+|                                    | Standard storage         | Infrequent Access storage |
+| ---------------------------------- | ------------------------ | ------------------------- |
+| Storage                            | $0.015 / GB-month        | $0.01 / GB-month          |
+| Class A Operations                 | $4.50 / million requests | $9.00 / million requests  |
+| Class B Operations                 | $0.36 / million requests | $0.90 / million requests  |
+| Data Retrieval (processing)        | None                     | $0.01 / GB                |
+| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                 |
 
 :::caution[Billable unit rounding]
 Cloudflare rounds up your usage to the next billing unit.
@@ -43,7 +43,7 @@ For example:
 - If you have performed one million and one operations, you will be billed for two million operations.
 - If you have used 1.1 GB-month, you will be billed for 2 GB-month.
 - If you have retrieved data (for infrequent access storage) for 1.1 GB, you will be billed for 2 GB.
-:::
+  :::
 
 ### Free tier
 
@@ -92,10 +92,10 @@ Data retrieval fees apply when you access or retrieve data from the Infrequent A
 
 For objects stored in Infrequent Access storage, you will be charged for the object for the minimum storage duration even if the object was deleted, moved, or replaced before the specified duration.
 
-| Storage class                                          | Minimum storage duration |
-| ------------------------------------------------------ | ------------------------ |
-| Standard storage                                       | None                     |
-| Infrequent Access storage                              | 30 days                  |
+| Storage class             | Minimum storage duration |
+| ------------------------- | ------------------------ |
+| Standard storage          | None                     |
+| Infrequent Access storage | 30 days                  |
 
 ## R2 Data Catalog pricing
 
@@ -127,25 +127,25 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 If a user writes 1,000 objects in R2 **Standard storage** for 1 month with an average size of 1 GB and reads each object 1,000 times during the month, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85      |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00       |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00       |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA         | None              | $0.00       |
-| **TOTAL**                   |                                                               |              |                   | **$14.85**  |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price      |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ---------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85     |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00      |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00      |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | None              | $0.00      |
+| **TOTAL**                   |                                                               |              |                   | **$14.85** |
 
 ### Infrequent access example
 
 If a user writes 1,000 objects in R2 Infrequent Access storage with an average size of 1 GB, stores them for 5 days, and then deletes them (delete operations are free), and during those 5 days each object is read 1,000 times, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA           | 1,000 GB-months   | $10.00      |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA           | 1,000             | $9.00       |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA           | 1 million         | $0.90       |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | 1,000 GB          | $10.00      |
-| **TOTAL**                   |                                                               |              |                   | **$29.90**  |
+|                             | Usage                                                         | Free Tier | Billable Quantity | Price      |
+| --------------------------- | ------------------------------------------------------------- | --------- | ----------------- | ---------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA        | 1,000 GB-months   | $10.00     |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA        | 1,000             | $9.00      |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA        | 1 million         | $0.90      |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA        | 1,000 GB          | $10.00     |
+| **TOTAL**                   |                                                               |           |                   | **$29.90** |
 
 Note that the minimal storage duration for infrequent access storage is 30 days, which means the billable quantity is 1,000 GB-months, rather than 167 GB-months.
 
diff --git a/src/content/docs/r2/r2-sql.mdx b/src/content/docs/r2/r2-sql.mdx
index 690e0b283548807..727a004053c732a 100644
--- a/src/content/docs/r2/r2-sql.mdx
+++ b/src/content/docs/r2/r2-sql.mdx
@@ -10,4 +10,4 @@ description: >-
   R2 SQL is a serverless SQL interface for Cloudflare R2, enabling querying and analyzing data.
 products:
   - r2
----
\ No newline at end of file
+---
diff --git a/src/content/docs/r2/reference/data-location.mdx b/src/content/docs/r2/reference/data-location.mdx
index 64607b3dbd621ac..a55ac28a3ebbc87 100644
--- a/src/content/docs/r2/reference/data-location.mdx
+++ b/src/content/docs/r2/reference/data-location.mdx
@@ -29,6 +29,7 @@ You can choose to automatically create your bucket in the closest available regi
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, leave _None_ selected for automatic selection or choose a region from the list.
@@ -79,6 +80,7 @@ Use Jurisdictional Restrictions when you need to ensure data is stored and proce
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
diff --git a/src/content/docs/r2/reference/data-security.mdx b/src/content/docs/r2/reference/data-security.mdx
index 15c1260d9648ae3..96c66a58a3eb8df 100644
--- a/src/content/docs/r2/reference/data-security.mdx
+++ b/src/content/docs/r2/reference/data-security.mdx
@@ -26,10 +26,8 @@ Access over plaintext HTTP (without TLS/SSL) can be disabled by connecting a [cu
 
 :::note
 
-
 R2 custom domains use Cloudflare for SaaS certificates and cannot be customized. Even if you have [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/), the advanced certificate will not be used due to [certificate prioritization](/ssl/reference/certificate-and-hostname-priority/).
 
-
 :::
 
 ## Compliance
diff --git a/src/content/docs/r2/reference/durability.mdx b/src/content/docs/r2/reference/durability.mdx
index 177e6ed4bd08d13..5d15f76865bd036 100644
--- a/src/content/docs/r2/reference/durability.mdx
+++ b/src/content/docs/r2/reference/durability.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-R2 is designed to provide 99.999999999% (eleven 9s) of annual durability.  This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
+R2 is designed to provide 99.999999999% (eleven 9s) of annual durability. This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
 
 ## How R2 achieves eleven-nines durability
 
@@ -22,7 +22,7 @@ R2's durability is built on multiple layers of redundancy and data protection:
 
 ### Considerations
 
-* Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
-* R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
-* Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
-* Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
+- Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
+- R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
+- Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
+- Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
diff --git a/src/content/docs/r2/reference/unicode-interoperability.mdx b/src/content/docs/r2/reference/unicode-interoperability.mdx
index 1543c6629fa5744..77796a1f1294a90 100644
--- a/src/content/docs/r2/reference/unicode-interoperability.mdx
+++ b/src/content/docs/r2/reference/unicode-interoperability.mdx
@@ -16,8 +16,8 @@ R2 preserves the encoding for display though. When you list the objects, you wil
 
 There are still some platform-specific differences to consider:
 
-* Windows and macOS filenames are case-insensitive while R2 and Linux are not.
-* Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
-* Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
+- Windows and macOS filenames are case-insensitive while R2 and Linux are not.
+- Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
+- Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
 
 If it is important for you to be able to bypass the unicode equivalence and use byte-oriented key names, contact your Cloudflare account team.
diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx
index 0c041c84fc44833..1025cfea8f7c9bb 100644
--- a/src/content/docs/r2/tutorials/cloudflare-access.mdx
+++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx
@@ -49,7 +49,7 @@ To create an Access application for your R2 bucket:
    Ensure that your policies only allow the users within your organization that need access to this R2 bucket.
    :::
 
-6. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
+5. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
 
 ## 3. Connect a custom domain
 
diff --git a/src/content/docs/r2/tutorials/mastodon.mdx b/src/content/docs/r2/tutorials/mastodon.mdx
index 3a1bb7b0eae2ed8..dd7a6b339aace64 100644
--- a/src/content/docs/r2/tutorials/mastodon.mdx
+++ b/src/content/docs/r2/tutorials/mastodon.mdx
@@ -23,10 +23,8 @@ Different from the default hostname of your Mastodon instance, object storage fo
 
 :::note
 
-
 If you move from R2 to another S3 compatible service later on, you can continue using the same hostname determined in this step. We do not recommend changing the hostname after the instance has been running to avoid breaking historical file references. In such a scenario, [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) can be used to instruct requests reaching the previous hostname to refer to the new hostname.
 
-
 :::
 
 ### 2. Create and set up an R2 bucket
@@ -34,6 +32,7 @@ If you move from R2 to another S3 compatible service later on, you can continue
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select **Create bucket**.
 3. Enter your bucket name and then select **Create bucket**. This name is internal when setting up your Mastodon instance and is not publicly accessible.
 4. Once the bucket is created, navigate to the **Settings** tab of this bucket and copy the value of **S3 API**.
diff --git a/src/content/docs/r2/tutorials/postman.mdx b/src/content/docs/r2/tutorials/postman.mdx
index 2c8fbc313867b2b..4bec7f80443cc16 100644
--- a/src/content/docs/r2/tutorials/postman.mdx
+++ b/src/content/docs/r2/tutorials/postman.mdx
@@ -11,7 +11,7 @@ products:
 
 import { DashButton } from "~/components";
 
-Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290) includes a complete list of operations supported by the platform.
+Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290) includes a complete list of operations supported by the platform.
 
 ## 1. Purchase R2
 
@@ -19,11 +19,11 @@ This guide assumes that you have made a Cloudflare account and purchased R2.
 
 ## 2. Explore R2 in Postman
 
-Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
+Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
 
 ## 3. Configure your R2 credentials
 
-In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
+In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
 
 To execute basic operations, you must set the `account-id`, `r2-access-key-id`, and `r2-secret-access-key` variables in the Postman dashboard > **Variables**.
 
@@ -32,8 +32,9 @@ To do this:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. In **R2**, under **Manage R2 API Tokens** on the right side of the dashboard, copy your Cloudflare account ID.
-3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation).
+3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation).
 4. Set the **CURRENT VALUE** of `account-id` to your Cloudflare account ID and select **Save**.
 
 Next, generate an R2 API token:
@@ -41,6 +42,7 @@ Next, generate an R2 API token:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. On the right hand sidebar, select **Manage R2 API Tokens**.
 3. Select **Create API token**.
 4. Name your token **Postman** by selecting the pencil icon next to the API name and grant it the **Edit** permission.
@@ -49,7 +51,7 @@ Guard this token and the **Access Key ID** and **Secret Access Key** closely. Yo
 
 After you have created your API token in the Cloudflare dashboard:
 
-1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation) > **Variables**.
+1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation) > **Variables**.
 2. Copy `Access Key ID` value from the Cloudflare dashboard and paste it into Postman’s `r2-access-key-id` variable value and select **Save**.
 3. Copy the `Secret Access Key` value from the Cloudflare dashboard and paste it into Postman’s `r2-secret-access-key` variable value and select **Save**.
 
diff --git a/src/content/docs/r2/video-tutorials.mdx b/src/content/docs/r2/video-tutorials.mdx
index 67585e1469ac91a..f92a3914495462c 100644
--- a/src/content/docs/r2/video-tutorials.mdx
+++ b/src/content/docs/r2/video-tutorials.mdx
@@ -12,9 +12,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Introduction to R2"
-        description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
-        href="/learning-paths/r2-intro/series/r2-1/"
-    />
+	<LinkCard
+		title="Introduction to R2"
+		description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
+		href="/learning-paths/r2-intro/series/r2-1/"
+	/>
 </CardGrid>
diff --git a/src/content/docs/radar/concepts/index.mdx b/src/content/docs/radar/concepts/index.mdx
index e8c3c876f284ebb..e439f4733f5f884 100644
--- a/src/content/docs/radar/concepts/index.mdx
+++ b/src/content/docs/radar/concepts/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/concepts/normalization.mdx b/src/content/docs/radar/concepts/normalization.mdx
index dbf55dfbe42a9f7..3a2a09e5b4ebd78 100644
--- a/src/content/docs/radar/concepts/normalization.mdx
+++ b/src/content/docs/radar/concepts/normalization.mdx
@@ -19,7 +19,7 @@ Refer to the `result.meta.normalization` property in the response to check which
 | `PERCENTAGE`            | Values represent percentages.                                                                                                                                                    |
 | `PERCENTAGE_CHANGE`     | Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period.                                   |
 | `OVERLAPPED_PERCENTAGE` | Values represent percentages that exceed 100% due to overlap.                                                                                                                    |
-| `MIN_MAX`               | Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)).                                                  |
+| `MIN_MAX`               | Values have been normalized using [min-max](<https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_(min-max_normalization)>).                                                  |
 | `MIN0_MAX`              | Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
 | `RAW_VALUES`            | Values are raw and have not been changed.                                                                                                                                        |
 
diff --git a/src/content/docs/radar/get-started/configure-alerts.mdx b/src/content/docs/radar/get-started/configure-alerts.mdx
index 6e7641992176d98..64ad4396db7c424 100644
--- a/src/content/docs/radar/get-started/configure-alerts.mdx
+++ b/src/content/docs/radar/get-started/configure-alerts.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications when Radar detects changes impacting countries, regions, or autonomous systems.
 
diff --git a/src/content/docs/radar/get-started/embed.mdx b/src/content/docs/radar/get-started/embed.mdx
index 249eccb402d8918..bf036cde8f960ad 100644
--- a/src/content/docs/radar/get-started/embed.mdx
+++ b/src/content/docs/radar/get-started/embed.mdx
@@ -25,8 +25,8 @@ Charts supporting this feature will have a share icon next to its description.
 
 1. Select the Share icon next to the description of the chart you wish to share.
 2. Select between Fixed Time and Real Time.
-   * Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
-   * Fixed Time will always display a chart with only the currently visible data points.
+   - Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
+   - Fixed Time will always display a chart with only the currently visible data points.
 3. Select Copy Code and paste the code into your web page.
 
 **Note**: Your current selections, such as date range, location, autonomous system (ASN), and visible series, will be reflected in the shared chart.
diff --git a/src/content/docs/radar/get-started/index.mdx b/src/content/docs/radar/get-started/index.mdx
index 1ce36868a710f4f..809a736dd35ebc9 100644
--- a/src/content/docs/radar/get-started/index.mdx
+++ b/src/content/docs/radar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/get-started/making-comparisons.mdx b/src/content/docs/radar/get-started/making-comparisons.mdx
index 9bffd560f9e690b..984fcafb3a77490 100644
--- a/src/content/docs/radar/get-started/making-comparisons.mdx
+++ b/src/content/docs/radar/get-started/making-comparisons.mdx
@@ -35,26 +35,26 @@ The response (shortened below for brevity) uses the provided `name` property to
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "us_data": {
-      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
-      "values": [ "0.871752", "1" ]
-    },
-    "pt_data": {
-      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
-      "values": [ "0.020457", "0.012313" ]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-10-26T17:00:00Z",
-        "endTime": "2022-11-02T17:00:00Z"
-      },
-      "aggInterval": "ONE_HOUR",
+	"success": true,
+	"errors": [],
+	"result": {
+		"us_data": {
+			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
+			"values": ["0.871752", "1"]
+		},
+		"pt_data": {
+			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
+			"values": ["0.020457", "0.012313"]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-10-26T17:00:00Z",
+				"endTime": "2022-11-02T17:00:00Z"
+			},
+			"aggInterval": "ONE_HOUR"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -81,14 +81,24 @@ Now, in the `result` property, you should get something like this:
 
 ```json
 {
-  "this_week": {
-    "timestamps": [ "2022-10-27T13:00:00Z", "2022-10-27T14:00:00Z", "...", "2022-11-03T12:00:00Z" ],
-    "values": [ "0.794321", "1", "...", "0.718433"]
-  },
-  "previous_week": {
-    "timestamps": [ "2022-10-20T13:00:00Z", "2022-10-20T14:00:00Z", "...", "2022-10-27T12:00:00Z" ],
-    "values": [ "0.774392", "0.835071", "...", "0.720181"]
-  }
+	"this_week": {
+		"timestamps": [
+			"2022-10-27T13:00:00Z",
+			"2022-10-27T14:00:00Z",
+			"...",
+			"2022-11-03T12:00:00Z"
+		],
+		"values": ["0.794321", "1", "...", "0.718433"]
+	},
+	"previous_week": {
+		"timestamps": [
+			"2022-10-20T13:00:00Z",
+			"2022-10-20T14:00:00Z",
+			"...",
+			"2022-10-27T12:00:00Z"
+		],
+		"values": ["0.774392", "0.835071", "...", "0.720181"]
+	}
 }
 ```
 
@@ -118,11 +128,21 @@ The `result` property should return a response like this:
 ```json
 {
 	"tonga": {
-		"timestamps": ["2022-10-15T02:00:00Z", "2022-10-15T03:00:00Z", "2022-10-15T04:00:00Z", "2022-10-15T05:00:00Z"],
+		"timestamps": [
+			"2022-10-15T02:00:00Z",
+			"2022-10-15T03:00:00Z",
+			"2022-10-15T04:00:00Z",
+			"2022-10-15T05:00:00Z"
+		],
 		"values": ["1.0", "0.832473", "0.820083", "0.79408"]
 	},
 	"tonga_outage": {
-		"timestamps": ["2022-01-15T02:00:00Z", "2022-01-15T03:00:00Z", "2022-01-15T04:00:00Z", "2022-01-15T05:00:00Z"],
+		"timestamps": [
+			"2022-01-15T02:00:00Z",
+			"2022-01-15T03:00:00Z",
+			"2022-01-15T04:00:00Z",
+			"2022-01-15T05:00:00Z"
+		],
 		"values": ["0.354105", "0.357287", "0.181811", "0.044198"]
 	}
 }
diff --git a/src/content/docs/radar/investigate/application-layer-attacks.mdx b/src/content/docs/radar/investigate/application-layer-attacks.mdx
index bef19dc325ce63d..62b6591ff068b45 100644
--- a/src/content/docs/radar/investigate/application-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/application-layer-attacks.mdx
@@ -40,27 +40,27 @@ From the abbreviated response below, we can conclude that distributed denial-of-
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks": {
-      "timestamps": ["2022-11-05T11:00:00Z", ".."],
-      "ddos": ["53.824302", "54.305823",  ".."],
-      "waf": ["39.760956", "39.31228",  ".."],
-      "ip_reputation": ["5.623487", "5.485468",  ".."],
-      "access_rules": ["0.648368", "0.676456",  ".."],
-      "bot_management": ["0.139733", "0.217155",  ".."],
-      "api_shield": ["0.003154", "0.002819",  ".."],
-      "data_loss_prevention": ["0.0", "0.0",  ".."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-05T11:00:00Z",
-        "endTime": "2022-11-06T11:00:00Z"
-      },
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks": {
+			"timestamps": ["2022-11-05T11:00:00Z", ".."],
+			"ddos": ["53.824302", "54.305823", ".."],
+			"waf": ["39.760956", "39.31228", ".."],
+			"ip_reputation": ["5.623487", "5.485468", ".."],
+			"access_rules": ["0.648368", "0.676456", ".."],
+			"bot_management": ["0.139733", "0.217155", ".."],
+			"api_shield": ["0.003154", "0.002819", ".."],
+			"data_loss_prevention": ["0.0", "0.0", ".."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-05T11:00:00Z",
+				"endTime": "2022-11-06T11:00:00Z"
+			}
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -79,9 +79,9 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"attacks_gb": {
 			"waf": "75.012138",
 			"ddos": "18.539149",
@@ -90,10 +90,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 			"bot_management": "0.131998",
 			"api_shield": "0.003178",
 			"data_loss_prevention": "0.0"
-  	},
+		},
 		"meta": {
 			// ...
-    }
+		}
 	}
 }
 ```
@@ -115,10 +115,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks_target": [
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks_target": [
 			{
 				"targetCountryName": "Belgium",
 				"targetCountryAlpha2": "BE",
@@ -150,14 +150,14 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 				"rank": 5
 			}
 		],
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-05T12:00:00Z",
-        "endTime": "2022-11-06T12:00:00Z"
-      },
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-05T12:00:00Z",
+				"endTime": "2022-11-06T12:00:00Z"
+			}
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
@@ -178,9 +178,9 @@ A typical response will be similar to the following:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"originCountryName": "United States",
@@ -223,10 +223,10 @@ A typical response will be similar to the following:
 				"rank": 5
 			}
 		],
-    "meta": {
+		"meta": {
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/dns.mdx b/src/content/docs/radar/investigate/dns.mdx
index 59db1f37eb09dbc..837edba24ef5632 100644
--- a/src/content/docs/radar/investigate/dns.mdx
+++ b/src/content/docs/radar/investigate/dns.mdx
@@ -27,9 +27,9 @@ The response shows that most queries come from the United States and Brazil:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "US",
@@ -43,9 +43,9 @@ The response shows that most queries come from the United States and Brazil:
 			}
 		],
 		"meta": {
-      // ...
-    }
-  }
+			// ...
+		}
+	}
 }
 ```
 
@@ -60,9 +60,9 @@ Returns the following response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "RU",
@@ -76,9 +76,9 @@ Returns the following response:
 			}
 		],
 		"meta": {
-      // ...
-    }
-  }
+			// ...
+		}
+	}
 }
 ```
 
@@ -86,7 +86,7 @@ As expected, most queries come from Russia.
 
 :::note
 
-Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
+Note that these examples return the total number of DNS queries from a location to a hostname, _out_ of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
 :::
 
 You can also provide multiple hostnames. Refer to [Get DNS top locations](/api/resources/radar/subresources/dns/subresources/top/methods/locations/) for more information. This is useful when the application you want to explore uses several hostnames to serve its content (like a hostname for the main website, another hostname dedicated to its API, etc.).
diff --git a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
index 9c025150aa46f67..26d9f65fea55f7d 100644
--- a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
+++ b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
@@ -8,10 +8,10 @@ products:
   - radar
 ---
 
-Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/),  Cloudflare's public DNS resolver.  Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
+Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/), Cloudflare's public DNS resolver. Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
 
-* An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
-* An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
+- An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
+- An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
 
 ## List of endpoints
 
@@ -26,10 +26,10 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "top_0": [
+	"success": true,
+	"errors": [],
+	"result": {
+		"top_0": [
 			{
 				"rank": 1,
 				"domain": "google.com"
@@ -50,8 +50,8 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 				"rank": 5,
 				"domain": "apple.com"
 			}
-    ]
-  },
+		]
+	},
 	"meta": {
 		// ...
 	}
@@ -75,24 +75,21 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets?limit=10&datasetType=R
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"datasets": [
 			{
 				"id": 213,
 				"title": "Top 1000000 ranking domains",
 				"description": "Unordered top 1000000 from 2023-01-02 to 2023-01-09",
 				"type": "RANKING_BUCKET",
-				"tags": [
-					"GLOBAL",
-					"top_1000000"
-				],
+				"tags": ["GLOBAL", "top_1000000"],
 				"meta": {
 					"top": 1000000
 				},
 				"alias": "ranking_top_1000000"
-			},
+			}
 			// ...
 		]
 	}
@@ -114,9 +111,9 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets/download" \
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"dataset": {
 			"url": "https://example.com/download"
 		}
diff --git a/src/content/docs/radar/investigate/http-requests.mdx b/src/content/docs/radar/investigate/http-requests.mdx
index 8fcdba8ef35ed24..f850973ae9af912 100644
--- a/src/content/docs/radar/investigate/http-requests.mdx
+++ b/src/content/docs/radar/investigate/http-requests.mdx
@@ -19,9 +19,9 @@ Most of the charts in the [Adoption and Usage](https://radar.cloudflare.com/adop
 
 These endpoints can be broadly split into:
 
-* `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
-* `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
-* `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
+- `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
+- `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
+- `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
 
 ## List of endpoints
 
@@ -40,29 +40,29 @@ Here is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "human": {
-      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-      "mobile": ["52.5532", "52.146628", ".."],
-      "desktop": ["47.394791", "47.800731", ".."],
-      "other": ["0.052009", "0.052642", ".."]
-    },
-    "bot": {
-      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-      "desktop": ["83.833892", "84.017711", ".."],
-      "mobile": ["16.156748", "15.969936", ".."],
-      "other": ["0.00936", "0.012353", ".."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-03T13:00:00Z",
-        "endTime": "2022-11-04T13:00:00Z"
-      },
-      "normalization": "PERCENTAGE"
-    }
-  }
+	"success": true,
+	"errors": [],
+	"result": {
+		"human": {
+			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+			"mobile": ["52.5532", "52.146628", ".."],
+			"desktop": ["47.394791", "47.800731", ".."],
+			"other": ["0.052009", "0.052642", ".."]
+		},
+		"bot": {
+			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+			"desktop": ["83.833892", "84.017711", ".."],
+			"mobile": ["16.156748", "15.969936", ".."],
+			"other": ["0.00936", "0.012353", ".."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-03T13:00:00Z",
+				"endTime": "2022-11-04T13:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
+		}
+	}
 }
 ```
 
@@ -90,9 +90,9 @@ Here is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"human": {
 			"mobile": "54.967243",
 			"desktop": "44.974006",
@@ -103,7 +103,7 @@ Here is the abbreviated response:
 			"mobile": "16.707455",
 			"other": "0.017093"
 		}
-  }
+	}
 }
 ```
 
@@ -122,9 +122,9 @@ This returns the following:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"human": {
 			"IPv4": "76.213647",
 			"IPv6": "23.786353"
@@ -133,7 +133,7 @@ This returns the following:
 			"IPv4": "91.492032",
 			"IPv6": "8.507968"
 		}
-  }
+	}
 }
 ```
 
@@ -156,9 +156,9 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"ipv6": [
 			{
 				"clientCountryAlpha2": "IN",
@@ -186,7 +186,7 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 				"value": "39.1514"
 			}
 		]
-  }
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/index.mdx b/src/content/docs/radar/investigate/index.mdx
index c377e8628eba30c..5c1a9cd5a898a6c 100644
--- a/src/content/docs/radar/investigate/index.mdx
+++ b/src/content/docs/radar/investigate/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Explore the different types of data available in Cloudflare Radar, from NetFlows (what feeds the [Internet Traffic Change](https://radar.cloudflare.com/) chart in Radar) to HTTP requests and DNS queries.
 
diff --git a/src/content/docs/radar/investigate/netflows.mdx b/src/content/docs/radar/investigate/netflows.mdx
index 1d7c85ee2290995..3971efa9cabc498 100644
--- a/src/content/docs/radar/investigate/netflows.mdx
+++ b/src/content/docs/radar/investigate/netflows.mdx
@@ -36,9 +36,9 @@ This is the abbreviated response:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS3243_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.565885", "0.586434", "..."]
@@ -64,9 +64,9 @@ The abbreviated response is:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
@@ -92,9 +92,9 @@ which would lead to a response like this:
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
+	"success": true,
+	"errors": [],
+	"result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
diff --git a/src/content/docs/radar/investigate/network-layer-attacks.mdx b/src/content/docs/radar/investigate/network-layer-attacks.mdx
index edd685c50ae34f8..56394fa33270271 100644
--- a/src/content/docs/radar/investigate/network-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/network-layer-attacks.mdx
@@ -35,36 +35,36 @@ If we inspect the abbreviated response below, we can conclude that globally, at
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "global": {
-      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-      "udp": ["50.784034", "51.055221", "..."],
-      "tcp": ["49.213944", "48.943769", "..."],
-      "icmp": ["0.002023", "0.001009", "..."],
-      "gre": ["0.0", "0.0", "0.0", "..."]
-    },
-    "singapore": {
-      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-      "tcp": ["79.605287", "83.943885", "..."],
-      "udp": ["20.394594", "16.056115", "..."],
-      "icmp": ["0.000119", "0.0", "..."],
-      "gre": ["0.0", "0.0", "..."]
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-06T13:00:00Z",
-        "endTime": "2022-11-07T13:00:00Z"
-      },
-      "normalization": "PERCENTAGE",
+	"success": true,
+	"errors": [],
+	"result": {
+		"global": {
+			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+			"udp": ["50.784034", "51.055221", "..."],
+			"tcp": ["49.213944", "48.943769", "..."],
+			"icmp": ["0.002023", "0.001009", "..."],
+			"gre": ["0.0", "0.0", "0.0", "..."]
+		},
+		"singapore": {
+			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+			"tcp": ["79.605287", "83.943885", "..."],
+			"udp": ["20.394594", "16.056115", "..."],
+			"icmp": ["0.000119", "0.0", "..."],
+			"gre": ["0.0", "0.0", "..."]
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-06T13:00:00Z",
+				"endTime": "2022-11-07T13:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
-We can also conclude that the distribution of network layer attacks coming from Singapore  — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
+We can also conclude that the distribution of network layer attacks coming from Singapore — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
 
 For more information refer to the [API reference](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) for this endpoint.
 
@@ -81,24 +81,24 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer3/summary?location
 
 ```json
 {
-  "success": true,
-  "errors": [],
-  "result": {
-    "attacks_ru": {
-      "udp": "86.682356",
-      "tcp": "11.928664",
-      "gre": "1.381015",
-      "icmp": "0.007965"
-    },
-    "meta": {
-      "dateRange": {
-        "startTime": "2022-11-06T15:00:00Z",
-        "endTime": "2022-11-07T15:00:00Z"
-      },
-      "normalization": "PERCENTAGE",
+	"success": true,
+	"errors": [],
+	"result": {
+		"attacks_ru": {
+			"udp": "86.682356",
+			"tcp": "11.928664",
+			"gre": "1.381015",
+			"icmp": "0.007965"
+		},
+		"meta": {
+			"dateRange": {
+				"startTime": "2022-11-06T15:00:00Z",
+				"endTime": "2022-11-07T15:00:00Z"
+			},
+			"normalization": "PERCENTAGE"
 			// ...
-    }
-  }
+		}
+	}
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/outages.mdx b/src/content/docs/radar/investigate/outages.mdx
index 6d6f0d662f2a97e..4627c42298d06d6 100644
--- a/src/content/docs/radar/investigate/outages.mdx
+++ b/src/content/docs/radar/investigate/outages.mdx
@@ -12,13 +12,13 @@ products:
 
 Refer the [blog post](https://blog.cloudflare.com/announcing-cloudflare-radar-outage-center/) for more information but, in short, Radar provides the following information:
 
-* **Location**: Where was the outage?
-* **ASN**: What autonomous system experienced a disruption in connectivity?
-* **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
-* **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
-* **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
-* **Start time**: When did the outage start?
-* **End time**: When did the outage end?
+- **Location**: Where was the outage?
+- **ASN**: What autonomous system experienced a disruption in connectivity?
+- **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
+- **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
+- **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
+- **Start time**: When did the outage start?
+- **End time**: When did the outage end?
 
 ## List of endpoints
 
diff --git a/src/content/docs/radar/investigate/url-scanner.mdx b/src/content/docs/radar/investigate/url-scanner.mdx
index ec99e52a8ef0c7b..ab5ce64f3fd1662 100644
--- a/src/content/docs/radar/investigate/url-scanner.mdx
+++ b/src/content/docs/radar/investigate/url-scanner.mdx
@@ -14,7 +14,7 @@ To better understand Internet usage around the world, use Cloudflare's URL Scann
 
 ## Use the API
 
-To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with *Account* > *URL Scanner* in the **Permissions** group, and select *Edit* as the access level.
+To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with _Account_ > _URL Scanner_ in the **Permissions** group, and select _Edit_ as the access level.
 
 Once you have the token, and you know your `account_id`, you are ready to make your first request to the API at `https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/`.
 
@@ -37,11 +37,11 @@ A successful response will have a status code of `200` and be similar to the fol
 
 ```json
 {
-  "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-  "api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-  "visibility": "public",
-  "url": "https://www.example.com",
-  "message": "Submission successful"
+	"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+	"api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+	"visibility": "public",
+	"url": "https://www.example.com",
+	"message": "Submission successful"
 }
 ```
 
@@ -56,11 +56,9 @@ Here's an example request body with some custom configuration options:
 ```json
 {
 	"url": "https://example.com",
-	"screenshotsResolutions": [
-		"desktop", "mobile", "tablet"
-	],
-  "customagent": "XXX-my-user-agent",
-  "referer": "example",
+	"screenshotsResolutions": ["desktop", "mobile", "tablet"],
+	"customagent": "XXX-my-user-agent",
+	"referer": "example",
 	"customHeaders": {
 		"Authorization": "xxx-token"
 	},
@@ -68,7 +66,7 @@ Here's an example request body with some custom configuration options:
 }
 ```
 
-Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In  effect, only users with knowledge of the scan ID will be able to access it.
+Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In effect, only users with knowledge of the scan ID will be able to access it.
 
 There will also be three screenshots taken of the webpage, one per target device type. The [`User-Agent`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) will be set as "XXX-my-user-agent". Note that you can set any custom HTTP header, including [Authorization](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Authorization).
 
@@ -84,38 +82,38 @@ While the scan is in progress, the HTTP status code will be `404`; once it is fi
 
 The response will include, among others, the following top properties:
 
-* `task` - Information on the scan submission.
-* `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
-* `data.requests` - Request chains involved in the page load.
-* `data.cookies` - Cookies set by the page.
-* `data.globals` - Non-standard JavaScript global variables.
-* `data.console` - Console logs.
-* `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
-* `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
-* `lists.ips` - IPs contacted.
-* `lists.asns` - AS Numbers contacted.
-* `lists.domains` - Hostnames contacted, including `dns` record information.
-* `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
-* `lists.certificates` - TLS certificates of HTTP responses.
-* `verdicts` - Verdicts on malicious content.
+- `task` - Information on the scan submission.
+- `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
+- `data.requests` - Request chains involved in the page load.
+- `data.cookies` - Cookies set by the page.
+- `data.globals` - Non-standard JavaScript global variables.
+- `data.console` - Console logs.
+- `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
+- `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
+- `lists.ips` - IPs contacted.
+- `lists.asns` - AS Numbers contacted.
+- `lists.domains` - Hostnames contacted, including `dns` record information.
+- `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
+- `lists.certificates` - TLS certificates of HTTP responses.
+- `verdicts` - Verdicts on malicious content.
 
 Some examples of more specific properties include:
 
-* `task.uuid` - ID of the scan.
-* `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
-* `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
-* `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
-* `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
-* `meta.processors.phishing` - What kind of phishing, if any, was detected.
-* `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
-* `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
-* `page.url` - URL of the primary request, after all HTTP redirects.
-* `page.country` - Country name from geolocation data associated with the main IP address contacted.
-* `page.history` - Main page history, including any HTTP redirects.
-* `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
-* `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
-* `page.favicon.hash` - MD5 hash of the favicon.
-* `verdicts.overall.malicious` - Whether the website was considered malicious *at the time of the scan*. Please check the remaining properties for each subsystem(s) for specific threats detected.
+- `task.uuid` - ID of the scan.
+- `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
+- `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
+- `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
+- `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
+- `meta.processors.phishing` - What kind of phishing, if any, was detected.
+- `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
+- `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
+- `page.url` - URL of the primary request, after all HTTP redirects.
+- `page.country` - Country name from geolocation data associated with the main IP address contacted.
+- `page.history` - Main page history, including any HTTP redirects.
+- `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
+- `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
+- `page.favicon.hash` - MD5 hash of the favicon.
+- `verdicts.overall.malicious` - Whether the website was considered malicious _at the time of the scan_. Please check the remaining properties for each subsystem(s) for specific threats detected.
 
 The [Get URL Scan](/api/resources/url_scanner/subresources/scans/methods/get/) API endpoint documentation contains the full response schema.
 
@@ -132,7 +130,6 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/v2/s
 --header "Authorization: Bearer <API_TOKEN>"
 ```
 
-
 If, instead, you wanted to search for scans that made at least one request to the hostname `cdnjs.cloudflare.com`, for example sites that use a JavaScript library hosted at `cdnjs.cloudflare.com`, use the query parameter `hostname=cdnjs.cloudflare.com`:
 
 ```bash
@@ -153,14 +150,13 @@ Some other example queries:
 
 Go to [Search URL scans](/api/resources/url_scanner/subresources/scans/methods/list/) in the API documentation for the full list of available options.
 
-
 ### Security Center
 
 Alternatively, you can search in the Security Center:
 
 1. In the Cloudflare dashboard, go to the **Investigate** page.
 
-	 <DashButton url="/?to=/:account/security-center/investigate" />
+   <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your query and select **Search**.
 
@@ -176,7 +172,7 @@ To scan a URL based on your geographic location:
 2. Go to **Location** > Select which country to scan the URL from.
 3. Select **Scan now**.
 
-You can also use the [API](https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20) to scan a URL from a specific location.
+You can also use the [API](<https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20>) to scan a URL from a specific location.
 
 In Security Center, you can retrieve pre-filtered information by:
 
@@ -187,4 +183,4 @@ In Security Center, you can retrieve pre-filtered information by:
 - Identical ASN
 - Identical IP
 - Identical domain
-- Identical final URL (after all redirections)
\ No newline at end of file
+- Identical final URL (after all redirections)
diff --git a/src/content/docs/radar/mcp-server.mdx b/src/content/docs/radar/mcp-server.mdx
index ef902ec41e498a5..56303e7fd5ac8ad 100644
--- a/src/content/docs/radar/mcp-server.mdx
+++ b/src/content/docs/radar/mcp-server.mdx
@@ -10,4 +10,4 @@ sidebar:
     variant: note
 products:
   - radar
----
\ No newline at end of file
+---
diff --git a/src/content/docs/radar/reference/index.mdx b/src/content/docs/radar/reference/index.mdx
index 605b54567f61ed5..1223e257fc2e24e 100644
--- a/src/content/docs/radar/reference/index.mdx
+++ b/src/content/docs/radar/reference/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Review reference information related to Cloudflare Radar:
 
diff --git a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
index 7b84e9fcb6eff4b..d08ecc4c77e6915 100644
--- a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
+++ b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
@@ -6,7 +6,7 @@ products:
   - radar
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Quarterly DDoS threat reports provide a comprehensive overview of <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attack</GlossaryTooltip> insights and trends over a three-month period.
 
@@ -14,7 +14,7 @@ Thanks to our vast network, Cloudflare provides insights on the evolving threat
 
 Find the latest quarterly DDoS threat reports in the [**Reports**](https://radar.cloudflare.com/reports) section of Cloudflare Radar.
 
-***
+---
 
 ## Methodologies
 
@@ -58,7 +58,7 @@ To calculate the attack size, duration, attack vectors, and emerging threats, Cl
 
 However, in the **Network layer attack distribution** graph of the [**Security & Attacks**](https://radar.cloudflare.com/security-and-attacks) Radar page these trends are calculated by number of bytes instead. Since attacks may vary greatly in number of bytes from one another, this could lead to trends differing between the quarterly reports and the graph displayed in Cloudflare Radar.
 
-***
+---
 
 ## Final remarks
 
diff --git a/src/content/docs/randomness-beacon/about/background.mdx b/src/content/docs/randomness-beacon/about/background.mdx
index 34ad6ab86602697..3985a768398b9d4 100644
--- a/src/content/docs/randomness-beacon/about/background.mdx
+++ b/src/content/docs/randomness-beacon/about/background.mdx
@@ -11,7 +11,7 @@ products:
 description: History and development of the drand project.
 ---
 
-Over the years, a generation of public randomness (often referred to as *common coins*) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
+Over the years, a generation of public randomness (often referred to as _common coins_) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
 
 Realizing this, [Ewa Syta](http://ewa.syta.us/) started a project on [Scalable Bias-Resistant Distributed Randomness](https://eprint.iacr.org/2016/1067) during her PhD studies under the supervision of [Michael J. Fischer](http://www.cs.yale.edu/homes/fischer/) and [Bryan Ford](https://bford.info/) at Yale University. After Bryan moved to EPFL in 2015, the new members of the DEDIS team at EPFL ([Nicolas Gailly](https://github.com/nikkolasg/), [Linus Gasser](https://people.epfl.ch/linus.gasser), [Philipp Jovanovic](https://jovanovic.io/), [Ismail Khoffi](https://ismailkhoffi.com/), [Eleftherios Kokoris Kogias](https://lefteriskk.github.io/)) joined the project and together published a research paper at the [2017 IEEE Symposium on Security and Privacy](https://ieeexplore.ieee.org/abstract/document/7958592).
 
diff --git a/src/content/docs/randomness-beacon/about/future.mdx b/src/content/docs/randomness-beacon/about/future.mdx
index 486975f9356ffc8..76c17926bf29159 100644
--- a/src/content/docs/randomness-beacon/about/future.mdx
+++ b/src/content/docs/randomness-beacon/about/future.mdx
@@ -15,10 +15,10 @@ As of spring 2020, the drand network is production-ready and can now be consider
 
 While the project has reached a mature state, we believe there are several ways for drand to continue to evolve.
 
-* We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
+- We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
 
-* We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
+- We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
 
-* We would like to consider standardization of the core drand protocol.
+- We would like to consider standardization of the core drand protocol.
 
 We are proud to be a part of these efforts and hope to see even more adoption of drand in third-party applications and systems.
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
index 59049a2b40a28d4..0678464a6ad4525 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
@@ -12,11 +12,11 @@ drand is an efficient randomness beacon daemon that utilizes pairing-based crypt
 
 This is an overview of the cryptographic building blocks drand uses to generate publicly-verifiable, unbiasable, and unpredictable randomness in a distributed manner.
 
-The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are *n* participants, out of which at most *f\<n* are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of *t-f+1* nodes work together to successfully execute cryptographic operations.
+The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are _n_ participants, out of which at most _f\<n_ are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of _t-f+1_ nodes work together to successfully execute cryptographic operations.
 
-Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where *t-of-n* participants are required to sign a transaction using a threshold signature scheme.
+Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where _t-of-n_ participants are required to sign a transaction using a threshold signature scheme.
 
 :::note[Note]
 
-This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts. 
+This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts.
 :::
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
index b3c4780456fd4fd..c39777be50f168c 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
@@ -16,11 +16,11 @@ First, we explain pairing-based cryptography (PBC), which has become quite popul
 
 Pairing-based cryptography is based on bilinear groups `(𝔾1,𝔾2,𝔾𝑡)`, where `𝔾1`, `𝔾2`, and `𝔾𝑡` are cyclic groups of prime order `𝑝` with generators `𝑔1`, `𝑔2`, and `𝑔𝑡`, respectively, and a pairing operation `𝑒:𝔾1×𝔾2→𝔾𝑡` with these properties:
 
-* **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
+- **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
 
-* **Non-degeneracy:** `𝑒≠1`
+- **Non-degeneracy:** `𝑒≠1`
 
-* **Computability:** There exists an efficient algorithm to compute `𝑒`.
+- **Computability:** There exists an efficient algorithm to compute `𝑒`.
   drand currently uses the Barreto-Lynn-Scott curve BLS12-381.
 
 ## BLS Signatures
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
index 1931a7beb984bc1..27152a46a610de6 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
@@ -8,7 +8,7 @@ products:
 description: Learn about the distributed key generation phase.
 ---
 
-In the drand setup phase, you create a collective private and public key pair shared among *𝑛* participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
+In the drand setup phase, you create a collective private and public key pair shared among _𝑛_ participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
 
 A DKG is performed in a fully distributed manner, avoiding any single points of failure. This is an overview of the different sub-components of the drand DKG implementation.
 
@@ -36,7 +36,7 @@ Note that you can use any subset of `𝑡-of-𝑛` shares to perform Lagrange in
 
 SSS scheme assumes that the dealer is honest, but this may not always hold in practice. A Verifiable Secret Sharing (VSS) scheme protects against malicious dealers by enabling participants to verify that their shares are consistent with those dealt to other nodes, ensuring that the shared secret can be correctly reconstructed later.
 
-drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A *cyclic group* means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
+drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A _cyclic group_ means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
 
 ### Share Distribution
 
diff --git a/src/content/docs/realtime/agents/index.mdx b/src/content/docs/realtime/agents/index.mdx
index 251f1183eda51db..841ef041c51d3c4 100644
--- a/src/content/docs/realtime/agents/index.mdx
+++ b/src/content/docs/realtime/agents/index.mdx
@@ -10,6 +10,6 @@ products:
   - realtime
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing/>
+<DirectoryListing />
diff --git a/src/content/docs/realtime/realtimekit/ai/index.mdx b/src/content/docs/realtime/realtimekit/ai/index.mdx
index 69baea7896467dd..0b4b56d2c3a2e40 100644
--- a/src/content/docs/realtime/realtimekit/ai/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/index.mdx
@@ -17,7 +17,7 @@ RealtimeKit provides AI-powered features using Cloudflare's AI infrastructure to
 ## Available features
 
 | Feature                                                  | Description                                 |
-| -------------------------------------------------------- | -----------------------------------------   |
+| -------------------------------------------------------- | ------------------------------------------- |
 | [Transcription](/realtime/realtimekit/ai/transcription/) | Real-time and end-of-meeting speech-to-text |
 | [Summary](/realtime/realtimekit/ai/summary/)             | AI-generated meeting summaries              |
 
diff --git a/src/content/docs/realtime/realtimekit/ai/summary.mdx b/src/content/docs/realtime/realtimekit/ai/summary.mdx
index 47577ad2f26f95d..f541baa92f1c99c 100644
--- a/src/content/docs/realtime/realtimekit/ai/summary.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/summary.mdx
@@ -20,44 +20,44 @@ Set `summarize_on_end: true` when [creating a meeting](/realtime/realtimekit/con
 
 ```json
 {
-  "title": "Product Review",
-  "ai_config": {
-    "transcription": {
-      "language": "en-US"
-    },
-    "summarization": {
-      "word_limit": 500,
-      "text_format": "markdown",
-      "summary_type": "team_meeting"
-    }
-  },
-  "summarize_on_end": true
+	"title": "Product Review",
+	"ai_config": {
+		"transcription": {
+			"language": "en-US"
+		},
+		"summarization": {
+			"word_limit": 500,
+			"text_format": "markdown",
+			"summary_type": "team_meeting"
+		}
+	},
+	"summarize_on_end": true
 }
 ```
 
 ## Configuration
 
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `word_limit` | number | 300 | Summary length (150-1000 words) |
-| `text_format` | string | `plain_text` | Output format: `plain_text` or `markdown` |
-| `summary_type` | string | `general` | Meeting context for tailored summaries |
+| Option         | Type   | Default      | Description                               |
+| -------------- | ------ | ------------ | ----------------------------------------- |
+| `word_limit`   | number | 300          | Summary length (150-1000 words)           |
+| `text_format`  | string | `plain_text` | Output format: `plain_text` or `markdown` |
+| `summary_type` | string | `general`    | Meeting context for tailored summaries    |
 
 ### Summary types
 
 Choose a type that matches your meeting for better results:
 
-| Type | Best for |
-|------|----------|
-| `general` | Any meeting (default) |
-| `team_meeting` | Regular team syncs |
-| `daily_standup` | Agile standups |
-| `one_on_one_meeting` | 1:1 meetings |
-| `sales_call` | Customer sales conversations |
-| `client_check_in` | Client status updates |
-| `interview` | Job interviews |
-| `lecture` | Educational content |
-| `code_review` | Technical code reviews |
+| Type                 | Best for                     |
+| -------------------- | ---------------------------- |
+| `general`            | Any meeting (default)        |
+| `team_meeting`       | Regular team syncs           |
+| `daily_standup`      | Agile standups               |
+| `one_on_one_meeting` | 1:1 meetings                 |
+| `sales_call`         | Customer sales conversations |
+| `client_check_in`    | Client status updates        |
+| `interview`          | Job interviews               |
+| `lecture`            | Educational content          |
+| `code_review`        | Technical code reviews       |
 
 ## Consume summaries
 
@@ -67,11 +67,11 @@ Configure `meeting.summary` event in [webhooks](/api/resources/realtime_kit/subr
 
 ```json
 {
-  "event": "meeting.summary",
-  "meetingId": "meeting-123",
-  "sessionId": "session-456",
-  "summaryDownloadUrl": "https://...",
-  "summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
+	"event": "meeting.summary",
+	"meetingId": "meeting-123",
+	"sessionId": "session-456",
+	"summaryDownloadUrl": "https://...",
+	"summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
 }
 ```
 
@@ -103,16 +103,19 @@ With `text_format: "markdown"` and `summary_type: "team_meeting"`:
 ## Meeting Summary
 
 ### Key Discussion Points
+
 - Reviewed Q4 roadmap priorities
 - Discussed deployment timeline for v2.0
 - Identified blockers for the auth migration
 
 ### Action Items
+
 - @alice: Update design specs by Friday
 - @bob: Schedule security review
 - @charlie: Create migration runbook
 
 ### Decisions Made
+
 - Approved moving forward with Kubernetes migration
 - Delayed analytics dashboard to next sprint
 ```
diff --git a/src/content/docs/realtime/realtimekit/ai/transcription.mdx b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
index fbedd591aeb9eb5..0c3a1720bf0478a 100644
--- a/src/content/docs/realtime/realtimekit/ai/transcription.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 RealtimeKit provides two transcription modes powered by Cloudflare Workers AI:
 
 | Mode               | Model                                                                | Use Case                       |
-| ----------------   | -------------------------------------------------------------------- | ------------------------------ |
+| ------------------ | -------------------------------------------------------------------- | ------------------------------ |
 | **Real-time**      | [Deepgram Nova-3](/workers-ai/models/nova-3/)                        | Live captions during meeting   |
 | **End-of-meeting** | [Whisper Large v3 Turbo](/workers-ai/models/whisper-large-v3-turbo/) | Accurate offline transcription |
 
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
index bfe857bd9ca8b92..f4de77a1ba6d15d 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
@@ -12,48 +12,50 @@ This module consists of the `ai` object which is used to interface with product'
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
 
-
-* [RTKAi](#module_RTKAi)
-    * _instance_
-        * [.telemetry](#module_RTKAi+telemetry)
-        * [.onTranscript(transcript)](#module_RTKAi+onTranscript)
-    * _static_
-        * [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
-        * [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
+- [RTKAi](#module_RTKAi)
+  - _instance_
+    - [.telemetry](#module_RTKAi+telemetry)
+    - [.onTranscript(transcript)](#module_RTKAi+onTranscript)
+  - _static_
+    - [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
+    - [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
 
 <a name="module_RTKAi+telemetry"></a>
 
 ### meeting.ai.telemetry
+
 **Kind**: instance property of [<code>RTKAi</code>](#module_RTKAi)  
 <a name="module_RTKAi+onTranscript"></a>
 
 ### meeting.ai.onTranscript(transcript)
-**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)
+
+| Param      | Type                           | Description                                 |
+| ---------- | ------------------------------ | ------------------------------------------- |
 | transcript | <code>TranscriptionData</code> | Transcript data received for a participant. |
 
 <a name="module_RTKAi.parseTranscript"></a>
 
 ### meeting.ai.parseTranscript(transcriptData, [isPartialTranscript])
+
 Parse a single line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| transcriptData | <code>string</code> |  | The transcript data to parse |
+| Param                 | Type                 | Default            | Description                       |
+| --------------------- | -------------------- | ------------------ | --------------------------------- |
+| transcriptData        | <code>string</code>  |                    | The transcript data to parse      |
 | [isPartialTranscript] | <code>boolean</code> | <code>false</code> | Whether the transcript is partial |
 
 <a name="module_RTKAi.parseTranscripts"></a>
 
 ### meeting.ai.parseTranscripts(transcriptData)
+
 Parse a multi-line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param          | Type                | Description                  |
+| -------------- | ------------------- | ---------------------------- |
 | transcriptData | <code>string</code> | The transcript data to parse |
-
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
index f0dc2d5d09f31ea..c5262c512d5524e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
@@ -10,340 +10,367 @@ web_core_version: 1.2.4
 
 This is the chat module, which can be used to send and receive messages from the meeting.
 
-
-* [RTKChat](#module_RTKChat)
-    * [module.exports](#exp_module_RTKChat--module.exports) ⏏
-        * [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
-        * ~~[.messages](#module_RTKChat--module.exports+messages)~~
-        * [.telemetry](#module_RTKChat--module.exports+telemetry)
-        * [.pinned](#module_RTKChat--module.exports+pinned)
-        * [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
-        * [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
-        * [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
-        * [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
-        * [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
-        * [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
-        * [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
-        * [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
-        * [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
-        * [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
-        * [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
-        * [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
-        * [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
-        * [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
-        * [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
-        * [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
-        * ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
-        * ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
-        * [.pin(id)](#module_RTKChat--module.exports+pin)
-        * [.unpin(id)](#module_RTKChat--module.exports+unpin)
-        * [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
-        * [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
-        * [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
-        * ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
-        * ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
+- [RTKChat](#module_RTKChat)
+  - [module.exports](#exp_module_RTKChat--module.exports) ⏏
+    - [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
+    - ~~[.messages](#module_RTKChat--module.exports+messages)~~
+    - [.telemetry](#module_RTKChat--module.exports+telemetry)
+    - [.pinned](#module_RTKChat--module.exports+pinned)
+    - [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
+    - [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
+    - [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
+    - [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
+    - [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
+    - [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
+    - [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
+    - [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
+    - [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
+    - [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
+    - [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
+    - [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
+    - [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
+    - [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
+    - [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
+    - [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
+    - ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
+    - ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
+    - [.pin(id)](#module_RTKChat--module.exports+pin)
+    - [.unpin(id)](#module_RTKChat--module.exports+unpin)
+    - [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
+    - [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
+    - [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
+    - ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
+    - ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
 
 <a name="exp_module_RTKChat--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKChat--module.exports_new"></a>
 
 #### new module.exports(context, chatSocketHandler, self, participants)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| chatSocketHandler | <code>RTKChatSocketHandler</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
+| Param             | Type                              |
+| ----------------- | --------------------------------- |
+| context           | <code>Context</code>              |
+| chatSocketHandler | <code>RTKChatSocketHandler</code> |
+| self              | <code>Self</code>                 |
+| participants      | <code>Participants</code>         |
 
 <a name="module_RTKChat--module.exports+messages"></a>
 
 #### ~~module.exports.messages~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+pinned"></a>
 
 #### module.exports.pinned
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 **Deprecated.**: This property is deprecated. Please use `fetchPinnedMessages()` instead.
 Returns an array of pinned messages.  
 <a name="module_RTKChat--module.exports+setMaxTextLimit"></a>
 
 #### module.exports.setMaxTextLimit(limit)
+
 Set the max character limit of a text message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param | Type                | Description                             |
+| ----- | ------------------- | --------------------------------------- |
 | limit | <code>number</code> | Max character limit for a text message. |
 
 <a name="module_RTKChat--module.exports+sendMessageInternal"></a>
 
 #### module.exports.sendMessageInternal(message, [participantIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>MessagePayload</code> | Message payload to send. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param            | Type                              | Description                             |
+| ---------------- | --------------------------------- | --------------------------------------- |
+| message          | <code>MessagePayload</code>       | Message payload to send.                |
 | [participantIds] | <code>Array.&lt;string&gt;</code> | Participant ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendTextMessageInternal"></a>
 
 #### module.exports.sendTextMessageInternal(message, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>string</code> | Text message to send. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                              | Description                      |
+| --------- | --------------------------------- | -------------------------------- |
+| message   | <code>string</code>               | Text message to send.            |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessageInternal"></a>
 
 #### module.exports.sendImageMessageInternal(image, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send.              |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessageInternal"></a>
 
 #### module.exports.sendFileMessageInternal(file, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | File to send. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | File to send.                    |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKChat--module.exports+sendTextMessage"></a>
 
 #### module.exports.sendTextMessage(message, [peerIds])
+
 Sends a chat text message to the room.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>string</code> | The message that must be sent to the room. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                              | Description                                |
+| --------- | --------------------------------- | ------------------------------------------ |
+| message   | <code>string</code>               | The message that must be sent to the room. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to.           |
 
 <a name="module_RTKChat--module.exports+sendCustomMessage"></a>
 
 #### module.exports.sendCustomMessage(message, [peerIds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>CustomMessagePayload</code> | Custom message payload. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                              | Description                      |
+| --------- | --------------------------------- | -------------------------------- |
+| message   | <code>CustomMessagePayload</code> | Custom message payload.          |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessage"></a>
 
 #### module.exports.sendImageMessage(image, [peerIds])
+
 Sends an image message to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent.    |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessage"></a>
 
 #### module.exports.sendFileMessage(file, [peerIds])
+
 Sends a file to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | A File object. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
+| Param     | Type                                              | Description                      |
+| --------- | ------------------------------------------------- | -------------------------------- |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | A File object.                   |
+| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendMessage"></a>
 
 #### module.exports.sendMessage(message, [participantIds])
+
 Sends a message to the meeting. This method can be used to send text, image,
 or file messages. The message type is determined by the key 'type' in `message`
 object.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| message | <code>MessagePayload</code> | An object including the type and content of the message. |
-| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants. |
+| Param            | Type                              | Description                                              |
+| ---------------- | --------------------------------- | -------------------------------------------------------- |
+| message          | <code>MessagePayload</code>       | An object including the type and content of the message. |
+| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants.      |
 
 <a name="module_RTKChat--module.exports+editTextMessage"></a>
 
 #### module.exports.editTextMessage(messageId, message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                | Description                |
+| --------- | ------------------- | -------------------------- |
 | messageId | <code>string</code> | Id of the message to edit. |
-| message | <code>string</code> | Updated text message. |
+| message   | <code>string</code> | Updated text message.      |
 
 <a name="module_RTKChat--module.exports+editImageMessage"></a>
 
 #### module.exports.editImageMessage(messageId, image)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| image | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                |
+| --------- | ------------------------------------------------- | -------------------------- |
+| messageId | <code>string</code>                               | Id of the message to edit. |
+| image     | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file.        |
 
 <a name="module_RTKChat--module.exports+editFileMessage"></a>
 
 #### module.exports.editFileMessage(messageId, file)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| file | <code>File</code> \| <code>ReactNativeFile</code> | Updated file. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                                              | Description                |
+| --------- | ------------------------------------------------- | -------------------------- |
+| messageId | <code>string</code>                               | Id of the message to edit. |
+| file      | <code>File</code> \| <code>ReactNativeFile</code> | Updated file.              |
 
 <a name="module_RTKChat--module.exports+editMessage"></a>
 
 #### module.exports.editMessage(messageId, message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
-| messageId | <code>string</code> | Id of the message to edit. |
-| message | <code>MessagePayload</code> | Updated message payload. |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                        | Description                |
+| --------- | --------------------------- | -------------------------- |
+| messageId | <code>string</code>         | Id of the message to edit. |
+| message   | <code>MessagePayload</code> | Updated message payload.   |
 
 <a name="module_RTKChat--module.exports+deleteMessage"></a>
 
 #### module.exports.deleteMessage(messageId)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+
+| Param     | Type                | Description                  |
+| --------- | ------------------- | ---------------------------- |
 | messageId | <code>string</code> | Id of the message to delete. |
 
 <a name="module_RTKChat--module.exports+getMessagesByUser"></a>
 
 #### ~~module.exports.getMessagesByUser(userId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                | Description                                    |
+| ------ | ------------------- | ---------------------------------------------- |
 | userId | <code>string</code> | The user id of the user that sent the message. |
 
 <a name="module_RTKChat--module.exports+getMessagesByType"></a>
 
 #### ~~module.exports.getMessagesByType(type)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| type | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
+| Param | Type                                                                                                                                                                 | Description                                   |
+| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
+| type  | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
 
 <a name="module_RTKChat--module.exports+pin"></a>
 
 #### module.exports.pin(id)
+
 Pins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | ID of the message to be pinned |
+| Param | Type                | Description                    |
+| ----- | ------------------- | ------------------------------ |
+| id    | <code>string</code> | ID of the message to be pinned |
 
 <a name="module_RTKChat--module.exports+unpin"></a>
 
 #### module.exports.unpin(id)
+
 Unpins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | ID of the message to be unpinned |
+| Param | Type                | Description                      |
+| ----- | ------------------- | -------------------------------- |
+| id    | <code>string</code> | ID of the message to be unpinned |
 
 <a name="module_RTKChat--module.exports+fetchPublicMessages"></a>
 
 #### module.exports.fetchPublicMessages(options)
+
 Fetches messages from the chat with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                             | Description                                                                                            |
+| ------- | -------------------------------- | ------------------------------------------------------------------------------------------------------ |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching messages, including timestamp, limit, and direction for pagination. |
 
 <a name="module_RTKChat--module.exports+fetchPrivateMessages"></a>
 
 #### module.exports.fetchPrivateMessages(options)
+
 Fetches private messages between the current user and another participant with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                                     | Description                                                                                                                             |
+| ------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
 | options | <code>FetchPrivateMessagesOptions</code> | Configuration options for fetching private messages, including private RTKChat ID (User ID of the participant) and pagination settings. |
 
 <a name="module_RTKChat--module.exports+fetchPinnedMessages"></a>
 
 #### module.exports.fetchPinnedMessages(options)
+
 Fetches pinned messages with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param   | Type                             | Description                                                                                    |
+| ------- | -------------------------------- | ---------------------------------------------------------------------------------------------- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching pinned messages, including timestamp, limit, and direction. |
 
 <a name="module_RTKChat--module.exports+getMessages"></a>
 
 #### ~~module.exports.getMessages(timeStamp, size, reversed, [offset])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
-| Param | Type | Default |
-| --- | --- | --- |
-| timeStamp | <code>number</code> |  | 
-| size | <code>number</code> |  | 
-| reversed | <code>boolean</code> |  | 
-| [offset] | <code>number</code> | <code>0</code> | 
+| Param     | Type                 | Default        |
+| --------- | -------------------- | -------------- |
+| timeStamp | <code>number</code>  |                |
+| size      | <code>number</code>  |                |
+| reversed  | <code>boolean</code> |                |
+| [offset]  | <code>number</code>  | <code>0</code> |
 
 <a name="module_RTKChat--module.exports+searchMessages"></a>
 
 #### ~~module.exports.searchMessages(query, [filters])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
+**_Deprecated_**
 
-| Param | Type |
-| --- | --- |
-| query | <code>string</code> | 
-| [filters] | <code>SearchFilters</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
 
+| Param     | Type                       |
+| --------- | -------------------------- |
+| query     | <code>string</code>        |
+| [filters] | <code>SearchFilters</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
index 4f7519ff80810fe..05ce7315d3a789b 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
@@ -10,91 +10,96 @@ web_core_version: 1.2.4
 
 This consists of the methods to facilitate connected meetings
 
-
-* [RTKConnectedMeetings](#module_RTKConnectedMeetings)
-    * [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
-        * [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
-        * [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
-        * [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
-        * [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
-        * [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
-        * [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
-        * [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
+- [RTKConnectedMeetings](#module_RTKConnectedMeetings)
+  - [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
+    - [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
+    - [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
+    - [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
+    - [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
+    - [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
+    - [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
+    - [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
 
 <a name="exp_module_RTKConnectedMeetings--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKConnectedMeetings--module.exports_new"></a>
 
 #### new module.exports(context)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings"></a>
 
 #### module.exports.getRTKConnectedMeetings()
+
 get connected meeting state
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 <a name="module_RTKConnectedMeetings--module.exports+createMeetings"></a>
 
 #### module.exports.createMeetings(request)
+
 create connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| request | <code>Array.&lt;{title: string}&gt;</code> | 
+| Param   | Type                                       |
+| ------- | ------------------------------------------ |
+| request | <code>Array.&lt;{title: string}&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+updateMeetings"></a>
 
 #### module.exports.updateMeetings(request)
+
 update meeting title
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| request | <code>Array.&lt;{id: string, title: string}&gt;</code> | 
+| Param   | Type                                                   |
+| ------- | ------------------------------------------------------ |
+| request | <code>Array.&lt;{id: string, title: string}&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+deleteMeetings"></a>
 
 #### module.exports.deleteMeetings(meetingIds)
+
 delete connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type |
-| --- | --- |
-| meetingIds | <code>Array.&lt;string&gt;</code> | 
+| Param      | Type                              |
+| ---------- | --------------------------------- |
+| meetingIds | <code>Array.&lt;string&gt;</code> |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipants"></a>
 
 #### module.exports.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)
+
 Trigger event to move participants
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| sourceMeetingId | <code>string</code> | id of source meeting |
-| destinationMeetingId | <code>string</code> | id of destination meeting |
-| participantIds | <code>Array.&lt;string&gt;</code> | list of id of the participants |
+| Param                | Type                              | Description                    |
+| -------------------- | --------------------------------- | ------------------------------ |
+| sourceMeetingId      | <code>string</code>               | id of source meeting           |
+| destinationMeetingId | <code>string</code>               | id of destination meeting      |
+| participantIds       | <code>Array.&lt;string&gt;</code> | list of id of the participants |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset"></a>
 
 #### module.exports.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)
-Trigger event to move participants with custom preset
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+Trigger event to move participants with custom preset
 
-| Param | Type | Description |
-| --- | --- | --- |
-| sourceMeetingId | <code>string</code> | id of source meeting |
-| destinationMeetingId | <code>string</code> | id of destination meeting |
-| participants | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |  |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
 
+| Param                | Type                                                      | Description               |
+| -------------------- | --------------------------------------------------------- | ------------------------- |
+| sourceMeetingId      | <code>string</code>                                       | id of source meeting      |
+| destinationMeetingId | <code>string</code>                                       | id of destination meeting |
+| participants         | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |                           |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
index 4d2d4d56bab5c91..2706403d75acd35 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
@@ -11,55 +11,59 @@ web_core_version: 1.2.4
 The RTKLivestream module represents the state of the current livestream, and allows
 to start/stop live streams.
 
-
-* [RTKLivestream](#module_RTKLivestream)
-    * [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
-        * [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
-        * [.telemetry](#module_RTKLivestream--module.exports+telemetry)
-        * [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
-        * [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
-        * [.stop()](#module_RTKLivestream--module.exports+stop)
+- [RTKLivestream](#module_RTKLivestream)
+  - [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
+    - [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
+    - [.telemetry](#module_RTKLivestream--module.exports+telemetry)
+    - [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
+    - [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
+    - [.stop()](#module_RTKLivestream--module.exports+stop)
 
 <a name="exp_module_RTKLivestream--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKLivestream--module.exports_new"></a>
 
 #### new module.exports(context, self)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
+| self    | <code>Self</code>    |
 
 <a name="module_RTKLivestream--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 <a name="module_RTKLivestream--module.exports+setRTKLivestreamState"></a>
 
 #### module.exports.setRTKLivestreamState(livestreamState)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| livestreamState | <code>RTKLivestreamState</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+
+| Param           | Type                            |
+| --------------- | ------------------------------- |
+| livestreamState | <code>RTKLivestreamState</code> |
 
 <a name="module_RTKLivestream--module.exports+start"></a>
 
 #### module.exports.start([livestreamConfig])
+
 Starts livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
 
-| Param | Type |
-| --- | --- |
-| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> | 
+| Param              | Type                                  |
+| ------------------ | ------------------------------------- |
+| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> |
 
 <a name="module_RTKLivestream--module.exports+stop"></a>
 
 #### module.exports.stop()
+
 Stops livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
index 8a3447521dfd9b2..9752ca8616beba0 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
@@ -10,51 +10,54 @@ web_core_version: 1.2.4
 
 This consists of the metadata of the meeting, such as the room name and the title.
 
-
-* [RTKMeta](#module_RTKMeta)
-    * [module.exports](#exp_module_RTKMeta--module.exports) ⏏
-        * [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
-        * [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
-        * [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
-        * [.viewType](#module_RTKMeta--module.exports+viewType)
-        * [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
-        * [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
-        * [.sessionId](#module_RTKMeta--module.exports+sessionId)
-        * [.meetingId](#module_RTKMeta--module.exports+meetingId)
-        * [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
-        * [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
+- [RTKMeta](#module_RTKMeta)
+  - [module.exports](#exp_module_RTKMeta--module.exports) ⏏
+    - [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
+    - [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
+    - [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
+    - [.viewType](#module_RTKMeta--module.exports+viewType)
+    - [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
+    - [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
+    - [.sessionId](#module_RTKMeta--module.exports+sessionId)
+    - [.meetingId](#module_RTKMeta--module.exports+meetingId)
+    - [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
+    - [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
 
 <a name="exp_module_RTKMeta--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKMeta--module.exports_new"></a>
 
 #### new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| viewType | <code>string</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
-| meetingTitle | <code>string</code> | 
+| Param             | Type                           |
+| ----------------- | ------------------------------ |
+| context           | <code>Context</code>           |
+| self              | <code>Self</code>              |
+| viewType          | <code>string</code>            |
+| roomSocketHandler | <code>RoomSocketHandler</code> |
+| meetingTitle      | <code>string</code>            |
 
 <a name="module_RTKMeta--module.exports+selfActiveTab"></a>
 
 #### module.exports.selfActiveTab
+
 Represents the current active tab
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+broadcastTabChanges"></a>
 
 #### module.exports.broadcastTabChanges
+
 Represents whether current user is spotlighted
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+viewType"></a>
 
 #### module.exports.viewType
+
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -62,47 +65,52 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKMeta--module.exports+meetingStartedTimestamp"></a>
 
 #### module.exports.meetingStartedTimestamp
+
 The timestamp of the time when the meeting started.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingTitle"></a>
 
 #### module.exports.meetingTitle
+
 The title of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+sessionId"></a>
 
 #### module.exports.sessionId
+
 (Experimental) The sessionId this meeting object is part of.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingId"></a>
 
 #### module.exports.meetingId
+
 The room name of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+setBroadcastTabChanges"></a>
 
 #### module.exports.setBroadcastTabChanges(broadcastTabChanges)
+
 Sets current user as broadcasting tab changes
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
 
-| Param | Type |
-| --- | --- |
-| broadcastTabChanges | <code>boolean</code> | 
+| Param               | Type                 |
+| ------------------- | -------------------- |
+| broadcastTabChanges | <code>boolean</code> |
 
 <a name="module_RTKMeta--module.exports+setSelfActiveTab"></a>
 
 #### module.exports.setSelfActiveTab(spotlightTab, tabChangeSource)
-Sets current active tab for user
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+Sets current active tab for user
 
-| Param | Type |
-| --- | --- |
-| spotlightTab | <code>ActiveTab</code> | 
-| tabChangeSource | <code>TabChangeSource</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| spotlightTab    | <code>ActiveTab</code>       |
+| tabChangeSource | <code>TabChangeSource</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
index 5ab88c872e965cd..12a5b874df4f649 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
@@ -11,68 +11,72 @@ web_core_version: 1.2.4
 This module represents a single participant in the meeting.
 The participant object can be accessed from one of the participant lists
 present in the `meeting.participants` object. For example,
+
 ```ts
 const participant1 = meeting.participants.active.get(participantId);
 const participant2 = meeting.participants.joined.get(participantId);
 const participant3 = meeting.participants.active.toArray()[0];
-const participant4 = meeting.participants.active.toArray().filter((p) => p.name === 'John');
+const participant4 = meeting.participants.active
+	.toArray()
+	.filter((p) => p.name === "John");
 ```
 
-
-* [RTKParticipant](#module_RTKParticipant)
-    * [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
-        * [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
-        * [.id](#module_RTKParticipant--module.exports+id)
-        * [.userId](#module_RTKParticipant--module.exports+userId)
-        * [.name](#module_RTKParticipant--module.exports+name)
-        * [.picture](#module_RTKParticipant--module.exports+picture)
-        * [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
-        * ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
-        * [.device](#module_RTKParticipant--module.exports+device)
-        * [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
-        * [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
-        * [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
-        * [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
-        * [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
-        * [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
-        * [.producers](#module_RTKParticipant--module.exports+producers)
-        * [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
-        * [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
-        * [.presetName](#module_RTKParticipant--module.exports+presetName)
-        * [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
-        * [.telemetry](#module_RTKParticipant--module.exports+telemetry)
-        * [.isPinned](#module_RTKParticipant--module.exports+isPinned)
-        * [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
-        * [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
-        * [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
-        * [.pin()](#module_RTKParticipant--module.exports+pin)
-        * [.unpin()](#module_RTKParticipant--module.exports+unpin)
-        * [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
-        * [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
-        * [.kick()](#module_RTKParticipant--module.exports+kick)
-        * [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
-        * [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
-        * [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
-        * [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
+- [RTKParticipant](#module_RTKParticipant)
+  - [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
+    - [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
+    - [.id](#module_RTKParticipant--module.exports+id)
+    - [.userId](#module_RTKParticipant--module.exports+userId)
+    - [.name](#module_RTKParticipant--module.exports+name)
+    - [.picture](#module_RTKParticipant--module.exports+picture)
+    - [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
+    - ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
+    - [.device](#module_RTKParticipant--module.exports+device)
+    - [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
+    - [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
+    - [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
+    - [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
+    - [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
+    - [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
+    - [.producers](#module_RTKParticipant--module.exports+producers)
+    - [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
+    - [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
+    - [.presetName](#module_RTKParticipant--module.exports+presetName)
+    - [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
+    - [.telemetry](#module_RTKParticipant--module.exports+telemetry)
+    - [.isPinned](#module_RTKParticipant--module.exports+isPinned)
+    - [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
+    - [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
+    - [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
+    - [.pin()](#module_RTKParticipant--module.exports+pin)
+    - [.unpin()](#module_RTKParticipant--module.exports+unpin)
+    - [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
+    - [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
+    - [.kick()](#module_RTKParticipant--module.exports+kick)
+    - [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
+    - [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
+    - [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
+    - [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
 
 <a name="exp_module_RTKParticipant--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipant--module.exports_new"></a>
 
 #### new module.exports(context, participant, self, roomSocket)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| participant | <code>IRTKParticipant</code> | 
-| self | <code>Self</code> | 
-| roomSocket | <code>RoomSocketHandler</code> | 
+| Param       | Type                           |
+| ----------- | ------------------------------ |
+| context     | <code>Context</code>           |
+| participant | <code>IRTKParticipant</code>   |
+| self        | <code>Self</code>              |
+| roomSocket  | <code>RoomSocketHandler</code> |
 
 <a name="module_RTKParticipant--module.exports+id"></a>
 
 #### module.exports.id
+
 The peer ID of the participant.
 The participants are indexed by this ID in the participant map.
 
@@ -80,148 +84,171 @@ The participants are indexed by this ID in the participant map.
 <a name="module_RTKParticipant--module.exports+userId"></a>
 
 #### module.exports.userId
+
 The user ID of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+name"></a>
 
 #### module.exports.name
+
 The name of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+picture"></a>
 
 #### module.exports.picture
+
 The picture of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+customRTKParticipantId"></a>
 
 #### module.exports.customRTKParticipantId
+
 The custom id of the participant set during Add RTKParticipant REST API
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+clientSpecificId"></a>
 
 #### ~~module.exports.clientSpecificId~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+device"></a>
 
 #### module.exports.device
+
 The device configuration of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoTrack"></a>
 
 #### module.exports.videoTrack
+
 The participant's video track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioTrack"></a>
 
 #### module.exports.audioTrack
+
 The participant's audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareTracks"></a>
 
 #### module.exports.screenShareTracks
+
 The participant's screenshare video and audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoEnabled"></a>
 
 #### module.exports.videoEnabled
+
 This is true if the participant's video is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioEnabled"></a>
 
 #### module.exports.audioEnabled
+
 This is true if the participant's audio is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareEnabled"></a>
 
 #### module.exports.screenShareEnabled
+
 This is true if the participant is screensharing.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+producers"></a>
 
 #### module.exports.producers
+
 producers created by participant
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+manualProducerConfig"></a>
 
 #### module.exports.manualProducerConfig
+
 producer config passed during manual subscription
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+supportsRemoteControl"></a>
 
 #### module.exports.supportsRemoteControl
+
 This is true if the participant supports remote control.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+presetName"></a>
 
 #### module.exports.presetName
+
 The preset of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+stageStatus"></a>
 
 #### module.exports.stageStatus
+
 Denotes the participants's current stage status.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+isPinned"></a>
 
 #### module.exports.isPinned
+
 Returns true if the participant is pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+setVideoEnabled"></a>
 
 #### module.exports.setVideoEnabled(videoEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| videoEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param        | Type                 | Default           |
+| ------------ | -------------------- | ----------------- |
+| videoEnabled | <code>boolean</code> |                   |
+| [emitEvent]  | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+setAudioEnabled"></a>
 
 #### module.exports.setAudioEnabled(audioEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| audioEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param        | Type                 | Default           |
+| ------------ | -------------------- | ----------------- |
+| audioEnabled | <code>boolean</code> |                   |
+| [emitEvent]  | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+setScreenShareEnabled"></a>
 
 #### module.exports.setScreenShareEnabled(screenShareEnabled, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| screenShareEnabled | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param              | Type                 | Default           |
+| ------------------ | -------------------- | ----------------- |
+| screenShareEnabled | <code>boolean</code> |                   |
+| [emitEvent]        | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+pin"></a>
 
 #### module.exports.pin()
+
 Returns `participant.id` if user has permission
 to pin participants.
 
@@ -229,6 +256,7 @@ to pin participants.
 <a name="module_RTKParticipant--module.exports+unpin"></a>
 
 #### module.exports.unpin()
+
 Returns `participant.id` if user has permission
 to unpin participants.
 
@@ -236,16 +264,18 @@ to unpin participants.
 <a name="module_RTKParticipant--module.exports+setIsPinned"></a>
 
 #### module.exports.setIsPinned(isPinned, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| isPinned | <code>boolean</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param       | Type                 | Default           |
+| ----------- | -------------------- | ----------------- |
+| isPinned    | <code>boolean</code> |                   |
+| [emitEvent] | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipant--module.exports+disableAudio"></a>
 
 #### module.exports.disableAudio()
+
 Disables audio for this participant.
 Requires the permission to disable participant audio.
 
@@ -253,6 +283,7 @@ Requires the permission to disable participant audio.
 <a name="module_RTKParticipant--module.exports+kick"></a>
 
 #### module.exports.kick()
+
 Kicks this participant from the meeting.
 Requires the permission to kick a participant.
 
@@ -260,6 +291,7 @@ Requires the permission to kick a participant.
 <a name="module_RTKParticipant--module.exports+disableVideo"></a>
 
 #### module.exports.disableVideo()
+
 Disables video for this participant.
 Requires the permission to disable video for a participant.
 
@@ -267,29 +299,31 @@ Requires the permission to disable video for a participant.
 <a name="module_RTKParticipant--module.exports+registerVideoElement"></a>
 
 #### module.exports.registerVideoElement(videoElem)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| videoElem | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param     | Type                          |
+| --------- | ----------------------------- |
+| videoElem | <code>HTMLVideoElement</code> |
 
 <a name="module_RTKParticipant--module.exports+deregisterVideoElement"></a>
 
 #### module.exports.deregisterVideoElement([videoElem])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| [videoElem] | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+
+| Param       | Type                          |
+| ----------- | ----------------------------- |
+| [videoElem] | <code>HTMLVideoElement</code> |
 
 <a name="module_RTKParticipant--module.exports+updateVideo"></a>
 
 #### module.exports.updateVideo(e)
-Internal method, do not use
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
+Internal method, do not use
 
-| Param | Type |
-| --- | --- |
-| e | <code>HTMLVideoElement</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
 
+| Param | Type                          |
+| ----- | ----------------------------- |
+| e     | <code>HTMLVideoElement</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
index f10720836d026ca..c894fa0a1e8958c 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
@@ -14,55 +14,57 @@ For example, when a participant is added to this map, a `participantJoined` even
 emitted from the map. When a participant object emits an event `videoUpdate`, the map
 re-emits that event (provided the participant is present in the map).
 
-
-* [RTKParticipantMap](#module_RTKParticipantMap)
-    * [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
-        * [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
-        * [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
-        * [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
-        * [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
+- [RTKParticipantMap](#module_RTKParticipantMap)
+  - [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
+    - [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
+    - [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
+    - [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
+    - [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
 
 <a name="exp_module_RTKParticipantMap--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipantMap--module.exports_new"></a>
 
 #### new module.exports(logger, [options])
 
-| Param | Type |
-| --- | --- |
-| logger | <code>Logger</code> | 
-| [options] | <code>MapEvents</code> | 
+| Param     | Type                   |
+| --------- | ---------------------- |
+| logger    | <code>Logger</code>    |
+| [options] | <code>MapEvents</code> |
 
 <a name="module_RTKParticipantMap--module.exports+add"></a>
 
 #### module.exports.add(participant, [emitEvent])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| participant | <code>T</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+
+| Param       | Type                 | Default           |
+| ----------- | -------------------- | ----------------- |
+| participant | <code>T</code>       |                   |
+| [emitEvent] | <code>boolean</code> | <code>true</code> |
 
 <a name="module_RTKParticipantMap--module.exports+clear"></a>
 
 #### module.exports.clear([emitEvent], [removeListeners])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
-| [removeListeners] | <code>boolean</code> | <code>false</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+
+| Param             | Type                 | Default            |
+| ----------------- | -------------------- | ------------------ |
+| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
+| [removeListeners] | <code>boolean</code> | <code>false</code> |
 
 <a name="module_RTKParticipantMap--module.exports+delete"></a>
 
 #### module.exports.delete(participantId, [emitEvent], [removeListeners])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| participantId | <code>string</code> |  | 
-| [emitEvent] | <code>boolean</code> | <code>true</code> | 
-| [removeListeners] | <code>boolean</code> | <code>false</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
 
+| Param             | Type                 | Default            |
+| ----------------- | -------------------- | ------------------ |
+| participantId     | <code>string</code>  |                    |
+| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
+| [removeListeners] | <code>boolean</code> | <code>false</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
index 6cc9cfa343f6be8..85f7c46ef94b31e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
@@ -10,106 +10,114 @@ web_core_version: 1.2.4
 
 This module represents all the participants in the meeting (except the local user).
 It consists of 4 maps:
+
 - `joined`: A map of all participants that have joined the meeting.
 - `waitlisted`: A map of all participants that have been added to the waitlist.
 - `active`: A map of active participants who should be displayed in the meeting grid.
 - `pinned`: A map of pinned participants.
 
-
 * [RTKParticipants](#module_RTKParticipants)
-    * [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
-        * [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
-        * [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
-        * [.joined](#module_RTKParticipants--module.exports+joined)
-        * ~~[.active](#module_RTKParticipants--module.exports+active)~~
-        * [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
-        * [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
-        * [.pinned](#module_RTKParticipants--module.exports+pinned)
-        * [.all](#module_RTKParticipants--module.exports+all)
-        * [.pip](#module_RTKParticipants--module.exports+pip)
-        * [.telemetry](#module_RTKParticipants--module.exports+telemetry)
-        * [.viewMode](#module_RTKParticipants--module.exports+viewMode)
-        * [.currentPage](#module_RTKParticipants--module.exports+currentPage)
-        * [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
-        * [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
-        * [.count](#module_RTKParticipants--module.exports+count)
-        * [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
-        * [.pageCount](#module_RTKParticipants--module.exports+pageCount)
-        * [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
-        * [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
-        * [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
-        * [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
-        * [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
-        * [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
-        * [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
-        * [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
-        * [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
-        * [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
-        * ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
-        * ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
-        * ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
-        * [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
-        * [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
-        * [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
-        * [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
+  - [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
+    - [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
+    - [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
+    - [.joined](#module_RTKParticipants--module.exports+joined)
+    - ~~[.active](#module_RTKParticipants--module.exports+active)~~
+    - [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
+    - [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
+    - [.pinned](#module_RTKParticipants--module.exports+pinned)
+    - [.all](#module_RTKParticipants--module.exports+all)
+    - [.pip](#module_RTKParticipants--module.exports+pip)
+    - [.telemetry](#module_RTKParticipants--module.exports+telemetry)
+    - [.viewMode](#module_RTKParticipants--module.exports+viewMode)
+    - [.currentPage](#module_RTKParticipants--module.exports+currentPage)
+    - [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
+    - [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
+    - [.count](#module_RTKParticipants--module.exports+count)
+    - [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
+    - [.pageCount](#module_RTKParticipants--module.exports+pageCount)
+    - [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
+    - [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
+    - [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
+    - [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
+    - [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
+    - [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
+    - [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
+    - [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
+    - [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
+    - [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
+    - ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
+    - ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
+    - ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
+    - [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
+    - [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
+    - [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
+    - [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
 
 <a name="exp_module_RTKParticipants--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKParticipants--module.exports_new"></a>
 
 #### new module.exports(context, self, roomSocketHandler)
+
 This constructs a new Participant object and maintains
 the maps of active/joined/waitlisted/pinned/selectedPeers maps.
 self : Self
 
-
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| Param             | Type                           |
+| ----------------- | ------------------------------ |
+| context           | <code>Context</code>           |
+| self              | <code>Self</code>              |
+| roomSocketHandler | <code>RoomSocketHandler</code> |
 
 <a name="module_RTKParticipants--module.exports+waitlisted"></a>
 
 #### module.exports.waitlisted
+
 Returns a list of participants waiting to join the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+joined"></a>
 
 #### module.exports.joined
+
 Returns a list of all participants in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+active"></a>
 
 #### ~~module.exports.active~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+videoSubscribed"></a>
 
 #### module.exports.videoSubscribed
+
 Returns a list of participants whose video streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+audioSubscribed"></a>
 
 #### module.exports.audioSubscribed
+
 Returns a list of participants whose audio streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+pinned"></a>
 
 #### module.exports.pinned
+
 Returns a list of participants who have been pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+all"></a>
 
 #### module.exports.all
+
 Returns all added participants irrespective of whether they are currently
 in the meeting or not
 
@@ -117,16 +125,19 @@ in the meeting or not
 <a name="module_RTKParticipants--module.exports+pip"></a>
 
 #### module.exports.pip
+
 Return the controls for Picture-in-Picture
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+viewMode"></a>
 
 #### module.exports.viewMode
+
 Indicates whether the meeting is in 'ACTIVE_GRID' mode or 'PAGINATED' mode.
 
 In 'ACTIVE_GRID' mode, participants are populated in the participants.active map
@@ -141,6 +152,7 @@ changed by the user using setPage(page).
 <a name="module_RTKParticipants--module.exports+currentPage"></a>
 
 #### module.exports.currentPage
+
 This indicates the current page that has been set by the user in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -148,24 +160,28 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+lastActiveSpeaker"></a>
 
 #### module.exports.lastActiveSpeaker
+
 This stores the `participantId` of the last participant who spoke in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+selectedPeers"></a>
 
 #### module.exports.selectedPeers
+
 Keeps a list of all participants who have been present in the selected peers list.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+count"></a>
 
 #### module.exports.count
+
 Returns the number of participants who are joined in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount"></a>
 
 #### module.exports.maxActiveRTKParticipantsCount
+
 Returns the maximum number of participants that can be present in
 the active map.
 
@@ -173,6 +189,7 @@ the active map.
 <a name="module_RTKParticipants--module.exports+pageCount"></a>
 
 #### module.exports.pageCount
+
 Returns the number of pages that are available in the meeting in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -180,187 +197,204 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount"></a>
 
 #### module.exports.setMaxActiveRTKParticipantsCount(limit)
+
 Updates the maximum number of participants that are populated in
 the active map.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param | Type                | Description       |
+| ----- | ------------------- | ----------------- |
 | limit | <code>number</code> | Updated max limit |
 
 <a name="module_RTKParticipants--module.exports+acceptWaitingRoomRequest"></a>
 
 #### module.exports.acceptWaitingRoomRequest(id)
+
 Accepts requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | peerId or userId of the waitlisted participant. |
+| Param | Type                | Description                                     |
+| ----- | ------------------- | ----------------------------------------------- |
+| id    | <code>string</code> | peerId or userId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest"></a>
 
 #### module.exports.acceptAllWaitingRoomRequest(userIds)
+
 We need a new event for socket service events
 since if we send them all together, sequence of events
 can be unreliable
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type |
-| --- | --- |
-| userIds | <code>Array.&lt;string&gt;</code> | 
+| Param   | Type                              |
+| ------- | --------------------------------- |
+| userIds | <code>Array.&lt;string&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+rejectWaitingRoomRequest"></a>
 
 #### module.exports.rejectWaitingRoomRequest(id)
+
 Rejects requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | participantId of the waitlisted participant. |
+| Param | Type                | Description                                  |
+| ----- | ------------------- | -------------------------------------------- |
+| id    | <code>string</code> | participantId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+setViewMode"></a>
 
 #### module.exports.setViewMode(viewMode)
+
 Sets the view mode of the meeting to either ACTIVE_GRID or PAGINATED.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param    | Type                  | Description                                          |
+| -------- | --------------------- | ---------------------------------------------------- |
 | viewMode | <code>ViewMode</code> | The mode in which the active map should be populated |
 
 <a name="module_RTKParticipants--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(peerIds, [kinds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerIds | <code>Array.&lt;string&gt;</code> | 
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+
+| Param   | Type                                                                                                                          |
+| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(peerIds, [kinds])
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerIds | <code>Array.&lt;string&gt;</code> | 
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+
+| Param   | Type                                                                                                                          |
+| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
 
 <a name="module_RTKParticipants--module.exports+setPage"></a>
 
 #### module.exports.setPage(page)
+
 Populates the active map with participants present in the page number
 indicated by the parameter `page` in PAGINATED mode.
 Does not do anything in ACTIVE_GRID mode.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| page | <code>number</code> | The page number to be set. |
+| Param | Type                | Description                |
+| ----- | ------------------- | -------------------------- |
+| page  | <code>number</code> | The page number to be set. |
 
 <a name="module_RTKParticipants--module.exports+disableAllAudio"></a>
 
 #### module.exports.disableAllAudio(allowUnmute)
+
 Disables audio for all participants in the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param       | Type                 | Description                                        |
+| ----------- | -------------------- | -------------------------------------------------- |
 | allowUnmute | <code>boolean</code> | Allow participants to unmute after they are muted. |
 
 <a name="module_RTKParticipants--module.exports+disableAllVideo"></a>
 
 #### module.exports.disableAllVideo()
+
 Disables video for all participants in the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+disableAudio"></a>
 
 #### ~~module.exports.disableAudio(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                    |
+| ------------- | ------------------- | ------------------------------ |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+disableVideo"></a>
 
 #### ~~module.exports.disableVideo(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                    |
+| ------------- | ------------------- | ------------------------------ |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+kick"></a>
 
 #### ~~module.exports.kick(participantId)~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param         | Type                | Description                     |
+| ------------- | ------------------- | ------------------------------- |
 | participantId | <code>string</code> | ID of participant to be kicked. |
 
 <a name="module_RTKParticipants--module.exports+kickAll"></a>
 
 #### module.exports.kickAll()
+
 Kicks all participants from the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+broadcastMessage"></a>
 
 #### module.exports.broadcastMessage(type, payload, target)
+
 Broadcasts the message to participants
 
 If no `target` is specified it is sent to all participants including `self`.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| type | <code>string</code> |  |
-| payload | <code>BroadcastMessagePayload</code> |  |
-| target | <code>BroadcastMessageTarget</code> | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
+| Param   | Type                                 | Description                                                                                                                           |
+| ------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
+| type    | <code>string</code>                  |                                                                                                                                       |
+| payload | <code>BroadcastMessagePayload</code> |                                                                                                                                       |
+| target  | <code>BroadcastMessageTarget</code>  | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
 
 <a name="module_RTKParticipants--module.exports+getAllJoinedPeers"></a>
 
 #### module.exports.getAllJoinedPeers(searchQuery, limit, offset)
+
 Returns all peers currently present in the room
 If you are in a group call, use `meeting.participants.joined`
 instead
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
 
-| Param | Type |
-| --- | --- |
-| searchQuery | <code>string</code> | 
-| limit | <code>number</code> | 
-| offset | <code>number</code> | 
+| Param       | Type                |
+| ----------- | ------------------- |
+| searchQuery | <code>string</code> |
+| limit       | <code>number</code> |
+| offset      | <code>number</code> |
 
 <a name="module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin"></a>
 
 #### module.exports.getRTKParticipantsInMeetingPreJoin()
+
 Returns all peers currently in the room, is a non paginated call
 and should only be used if you are in a non room joined state,
 if in a joined group call, use `meeting.participants.joined`
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
index e8da972e0b7c931..ac3f6c4b61d2b82 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
@@ -10,52 +10,52 @@ web_core_version: 1.2.4
 
 The PermissionPreset class represents the meeting permissions for the current participant
 
-
-* [PermissionPreset](#module_PermissionPreset)
-    * _instance_
-        * [.stageEnabled](#module_PermissionPreset+stageEnabled)
-        * [.stageAccess](#module_PermissionPreset+stageAccess)
-        * [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
-        * [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
-        * [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
-        * [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
-        * [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
-        * [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
-        * [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
-        * [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
-        * [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
-        * [.kickParticipant](#module_PermissionPreset+kickParticipant)
-        * [.pinParticipant](#module_PermissionPreset+pinParticipant)
-        * [.canRecord](#module_PermissionPreset+canRecord)
-        * ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
-        * [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
-        * [.plugins](#module_PermissionPreset+plugins)
-        * [.polls](#module_PermissionPreset+polls)
-        * ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
-        * ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
-        * [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
-        * ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
-        * [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
-        * ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
-        * [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
-        * [.chatPublic](#module_PermissionPreset+chatPublic)
-        * [.chatPrivate](#module_PermissionPreset+chatPrivate)
-        * [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
-        * [.showParticipantList](#module_PermissionPreset+showParticipantList)
-        * ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
-        * [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
-        * ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
-        * ~~[.canPresent](#module_PermissionPreset+canPresent)~~
-        * ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
-        * ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
-        * [.canLivestream](#module_PermissionPreset+canLivestream)
-    * _static_
-        * [.fromResponse()](#module_PermissionPreset.fromResponse)
-        * [.default()](#module_PermissionPreset.default)
+- [PermissionPreset](#module_PermissionPreset)
+  - _instance_
+    - [.stageEnabled](#module_PermissionPreset+stageEnabled)
+    - [.stageAccess](#module_PermissionPreset+stageAccess)
+    - [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
+    - [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
+    - [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
+    - [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
+    - [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
+    - [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
+    - [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
+    - [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
+    - [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
+    - [.kickParticipant](#module_PermissionPreset+kickParticipant)
+    - [.pinParticipant](#module_PermissionPreset+pinParticipant)
+    - [.canRecord](#module_PermissionPreset+canRecord)
+    - ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
+    - [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
+    - [.plugins](#module_PermissionPreset+plugins)
+    - [.polls](#module_PermissionPreset+polls)
+    - ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
+    - ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
+    - [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
+    - ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
+    - [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
+    - ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
+    - [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
+    - [.chatPublic](#module_PermissionPreset+chatPublic)
+    - [.chatPrivate](#module_PermissionPreset+chatPrivate)
+    - [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
+    - [.showParticipantList](#module_PermissionPreset+showParticipantList)
+    - ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
+    - [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
+    - ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
+    - ~~[.canPresent](#module_PermissionPreset+canPresent)~~
+    - ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
+    - ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
+    - [.canLivestream](#module_PermissionPreset+canLivestream)
+  - _static_
+    - [.fromResponse()](#module_PermissionPreset.fromResponse)
+    - [.default()](#module_PermissionPreset.default)
 
 <a name="module_PermissionPreset+stageEnabled"></a>
 
 ### meeting.self.permissions.stageEnabled
+
 The `stageEnabled` property returns a boolean value.
 If `true`, stage management is available for the participant.
 
@@ -63,6 +63,7 @@ If `true`, stage management is available for the participant.
 <a name="module_PermissionPreset+stageAccess"></a>
 
 ### meeting.self.permissions.stageAccess
+
 The `stageAccess` property dictates how a user interacts with the stage.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 
@@ -70,6 +71,7 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 <a name="module_PermissionPreset+acceptWaitingRequests"></a>
 
 ### meeting.self.permissions.acceptWaitingRequests
+
 The `acceptWaitingRequests` returns boolean value.
 If `true`, participant can accept the request of waiting participant.
 
@@ -77,6 +79,7 @@ If `true`, participant can accept the request of waiting participant.
 <a name="module_PermissionPreset+requestProduceVideo"></a>
 
 ### meeting.self.permissions.requestProduceVideo
+
 The `requestProduceVideo` returns boolean value.
 If `true`, participant can send request to participants
 about producing video.
@@ -85,6 +88,7 @@ about producing video.
 <a name="module_PermissionPreset+requestProduceAudio"></a>
 
 ### meeting.self.permissions.requestProduceAudio
+
 The `requestProduceAudio` returns boolean value.
 If `true`, participant can send request to participants
 about producing audio.
@@ -93,6 +97,7 @@ about producing audio.
 <a name="module_PermissionPreset+requestProduceScreenshare"></a>
 
 ### meeting.self.permissions.requestProduceScreenshare
+
 The `requestProduceScreenshare` returns boolean value.
 If `true`, participant can send request to participants
 about sharing screen.
@@ -101,6 +106,7 @@ about sharing screen.
 <a name="module_PermissionPreset+canAllowParticipantAudio"></a>
 
 ### meeting.self.permissions.canAllowParticipantAudio
+
 The `canAllowParticipantAudio` returns boolean value.
 If `true`, participant can enable other participants` audio.
 
@@ -108,6 +114,7 @@ If `true`, participant can enable other participants` audio.
 <a name="module_PermissionPreset+canAllowParticipantScreensharing"></a>
 
 ### meeting.self.permissions.canAllowParticipantScreensharing
+
 The `canAllowParticipantScreensharing` returns boolean value.
 If `true`, participant can enable other participants` screen share.
 
@@ -115,6 +122,7 @@ If `true`, participant can enable other participants` screen share.
 <a name="module_PermissionPreset+canAllowParticipantVideo"></a>
 
 ### meeting.self.permissions.canAllowParticipantVideo
+
 The `canAllowParticipantVideo` returns boolean value.
 If `true`, participant can enable other participants` video.
 
@@ -122,18 +130,21 @@ If `true`, participant can enable other participants` video.
 <a name="module_PermissionPreset+canDisableParticipantAudio"></a>
 
 ### meeting.self.permissions.canDisableParticipantAudio
+
 If `true`, a participant can disable other participants` audio.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canDisableParticipantVideo"></a>
 
 ### meeting.self.permissions.canDisableParticipantVideo
+
 If `true`, a participant can disable other participants` video.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+kickParticipant"></a>
 
 ### meeting.self.permissions.kickParticipant
+
 The `kickParticipant` returns boolean value.
 If `true`, participant can remove other participants from the meeting.
 
@@ -141,6 +152,7 @@ If `true`, participant can remove other participants from the meeting.
 <a name="module_PermissionPreset+pinParticipant"></a>
 
 ### meeting.self.permissions.pinParticipant
+
 The `pinParticipant` returns boolean value.
 If `true`, participant can pin a participant in the meeting.
 
@@ -148,6 +160,7 @@ If `true`, participant can pin a participant in the meeting.
 <a name="module_PermissionPreset+canRecord"></a>
 
 ### meeting.self.permissions.canRecord
+
 The `canRecord` returns boolean value.
 If `true`, participant can record the meeting.
 
@@ -155,12 +168,14 @@ If `true`, participant can record the meeting.
 <a name="module_PermissionPreset+waitingRoomType"></a>
 
 ### ~~meeting.self.permissions.waitingRoomType~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+waitingRoomBehaviour"></a>
 
 ### meeting.self.permissions.waitingRoomBehaviour
+
 The `waitingRoomType` returns string value.
 type of waiting room behavior
 possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
@@ -169,6 +184,7 @@ possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
 <a name="module_PermissionPreset+plugins"></a>
 
 ### meeting.self.permissions.plugins
+
 The `plugins` tells if the participant can act on plugins
 there are 2 permissions with boolean values, `canStart` and `canClose`.
 
@@ -176,6 +192,7 @@ there are 2 permissions with boolean values, `canStart` and `canClose`.
 <a name="module_PermissionPreset+polls"></a>
 
 ### meeting.self.permissions.polls
+
 The `polls` tells if the participant can use polls.
 There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewResults`
 
@@ -183,18 +200,21 @@ There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewRes
 <a name="module_PermissionPreset+produceVideo"></a>
 
 ### ~~meeting.self.permissions.produceVideo~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+requestProduce"></a>
 
 ### ~~meeting.self.permissions.requestProduce~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceVideo"></a>
 
 ### meeting.self.permissions.canProduceVideo
+
 The `canProduceVideo` shows permissions for enabling video.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -202,12 +222,14 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceScreenshare"></a>
 
 ### ~~meeting.self.permissions.produceScreenshare~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceScreenshare"></a>
 
 ### meeting.self.permissions.canProduceScreenshare
+
 The `canProduceScreenshare` shows permissions for sharing screen.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -215,12 +237,14 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceAudio"></a>
 
 ### ~~meeting.self.permissions.produceAudio~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceAudio"></a>
 
 ### meeting.self.permissions.canProduceAudio
+
 The `canProduceAudio` shows permissions for enabling audio.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -228,6 +252,7 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+chatPublic"></a>
 
 ### meeting.self.permissions.chatPublic
+
 The `chatPublic` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send chat
@@ -238,6 +263,7 @@ there are 4 permissions
 <a name="module_PermissionPreset+chatPrivate"></a>
 
 ### meeting.self.permissions.chatPrivate
+
 The `chatPrivate` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send private chat
@@ -249,6 +275,7 @@ there are 4 permissions
 <a name="module_PermissionPreset+hiddenParticipant"></a>
 
 ### meeting.self.permissions.hiddenParticipant
+
 The `hiddenParticipant` returns boolean value.
 If `true`, participant is hidden.
 
@@ -256,6 +283,7 @@ If `true`, participant is hidden.
 <a name="module_PermissionPreset+showParticipantList"></a>
 
 ### meeting.self.permissions.showParticipantList
+
 The `showParticipantList` returns boolean value.
 If `true`, participant list can be shown to the participant.
 
@@ -263,12 +291,14 @@ If `true`, participant list can be shown to the participant.
 <a name="module_PermissionPreset+canChangeParticipantRole"></a>
 
 ### ~~meeting.self.permissions.canChangeParticipantRole~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canChangeParticipantPermissions"></a>
 
 ### meeting.self.permissions.canChangeParticipantPermissions
+
 The `canChangeParticipantPermissions` returns boolean value.
 If `true`, allow changing the participants' permissions.
 
@@ -276,40 +306,47 @@ If `true`, allow changing the participants' permissions.
 <a name="module_PermissionPreset+canChangeTheme"></a>
 
 ### ~~meeting.self.permissions.canChangeTheme~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canPresent"></a>
 
 ### ~~meeting.self.permissions.canPresent~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+acceptPresentRequests"></a>
 
 ### ~~meeting.self.permissions.acceptPresentRequests~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+maxScreenShareCount"></a>
 
 ### ~~meeting.self.permissions.maxScreenShareCount~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canLivestream"></a>
 
 ### meeting.self.permissions.canLivestream
+
 Livestream
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset.fromResponse"></a>
 
 ### meeting.self.permissions.fromResponse()
+
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 **Deprecated.**: Use init()  
 <a name="module_PermissionPreset.default"></a>
 
 ### meeting.self.permissions.default()
+
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
-**Deprecated.**: Use init()  
+**Deprecated.**: Use init()
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
index 72747a12f6bdcac..6cb2dd696a9ff5f 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
@@ -46,76 +46,76 @@ Code from ui-kit. Same method used in the avatar component
 **Kind**: global function  
 <a name="_init"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
+| Param   | Type                 |
+| ------- | -------------------- |
+| context | <code>Context</code> |
+| self    | <code>Self</code>    |
 
 <a name="init"></a>
 
 Initialize PiP and prepare sources
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| [options] | <code>Object</code> | 
-| [options.height] | <code>number</code> | 
-| [options.width] | <code>number</code> | 
+| Param            | Type                |
+| ---------------- | ------------------- |
+| [options]        | <code>Object</code> |
+| [options.height] | <code>number</code> |
+| [options.width]  | <code>number</code> |
 
 <a name="disableSource"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| source | <code>string</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| source | <code>string</code> |
 
 <a name="addSource"></a>
 
 Add a video source from the participant grid
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| id | <code>string</code> | id for the source (ex. participant id) |
-| element | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source |
-| enabled | <code>boolean</code> | if source is enabled |
-| [displayText] | <code>string</code> | two character display text |
+| Param         | Type                          | Description                            |
+| ------------- | ----------------------------- | -------------------------------------- |
+| id            | <code>string</code>           | id for the source (ex. participant id) |
+| element       | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source  |
+| enabled       | <code>boolean</code>          | if source is enabled                   |
+| [displayText] | <code>string</code>           | two character display text             |
 
 <a name="updateSource"></a>
 
 Update a video source
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| id | <code>string</code> | 
-| source | <code>any</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| id     | <code>string</code> |
+| source | <code>any</code>    |
 
 <a name="removeSource"></a>
 
 Remove the video source for the participant
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Description |
-| --- | --- |
-| id | id for the source (ex. participant id) |
+| Param | Description                            |
+| ----- | -------------------------------------- |
+| id    | id for the source (ex. participant id) |
 
 <a name="removePinnedSource"></a>
 
 Remove the pinned source
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Description |
-| --- | --- |
-| id | id for the source (ex. participant id) |
+| Param | Description                            |
+| ----- | -------------------------------------- |
+| id    | id for the source (ex. participant id) |
 
 <a name="removeAllSources"></a>
 
@@ -126,4 +126,4 @@ Remove all sources
 
 Enable PiP
 
-**Kind**: global function  
+**Kind**: global function
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
index 68d9b48f76fb51b..1dc5407b42362d4 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
@@ -11,145 +11,159 @@ web_core_version: 1.2.4
 The RTKPlugin module represents a single plugin in the meeting.
 A plugin can be obtained from one of the plugin arrays in `meeting.plugins`.
 For example,
+
 ```ts
 const plugin1 = meeting.plugins.active.get(pluginId);
 const plugin2 = meeting.plugins.all.get(pluginId);
 ```
 
-
-* [RTKPlugin](#module_RTKPlugin)
-    * [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
-        * [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
-        * [.telemetry](#module_RTKPlugin--module.exports+telemetry)
-        * [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
-        * [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
-        * [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
-        * [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
-        * [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
-        * [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
-        * [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
-        * [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
-        * ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
-        * ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
-        * [.activate()](#module_RTKPlugin--module.exports+activate)
-        * [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
+- [RTKPlugin](#module_RTKPlugin)
+  - [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
+    - [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
+    - [.telemetry](#module_RTKPlugin--module.exports+telemetry)
+    - [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
+    - [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
+    - [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
+    - [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
+    - [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
+    - [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
+    - [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
+    - [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
+    - ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
+    - ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
+    - [.activate()](#module_RTKPlugin--module.exports+activate)
+    - [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
 
 <a name="exp_module_RTKPlugin--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKPlugin--module.exports_new"></a>
 
 #### new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| plugin | <code>RTKPluginResponse</code> | 
-| pluginSocketHandler | <code>RTKPluginSocketHandler</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
-| chat | <code>Chat</code> | 
-| meetingTitle | <code>string</code> | 
+| Param               | Type                                |
+| ------------------- | ----------------------------------- |
+| context             | <code>Context</code>                |
+| plugin              | <code>RTKPluginResponse</code>      |
+| pluginSocketHandler | <code>RTKPluginSocketHandler</code> |
+| self                | <code>Self</code>                   |
+| participants        | <code>Participants</code>           |
+| chat                | <code>Chat</code>                   |
+| meetingTitle        | <code>string</code>                 |
 
 <a name="module_RTKPlugin--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+sendIframeEvent"></a>
 
 #### module.exports.sendIframeEvent(message)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type | Description |
-| --- | --- | --- |
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param   | Type                                | Description                              |
+| ------- | ----------------------------------- | ---------------------------------------- |
 | message | <code>RTKPluginIframeMessage</code> | Socket message forwarded to this plugin. |
 
 <a name="module_RTKPlugin--module.exports+handleIframeMessage"></a>
 
 #### module.exports.handleIframeMessage(iframeMessage)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| iframeMessage | <code>RTKPluginIframeMessage</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param         | Type                                |
+| ------------- | ----------------------------------- |
+| iframeMessage | <code>RTKPluginIframeMessage</code> |
 
 <a name="module_RTKPlugin--module.exports+sendData"></a>
 
 #### module.exports.sendData(payload)
+
 This method is used to send arbitrary data to the plugin.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| payload | <code>SendDataOptions</code> | The payload that you want to send inside the plugin. |
-| payload.eventName | <code>string</code> | Name of the event. This is used to listen for the event in plugin SDK. |
-| payload.data | <code>any</code> | Data you wish to emit. It can assume any data type. |
+| Param             | Type                         | Description                                                            |
+| ----------------- | ---------------------------- | ---------------------------------------------------------------------- |
+| payload           | <code>SendDataOptions</code> | The payload that you want to send inside the plugin.                   |
+| payload.eventName | <code>string</code>          | Name of the event. This is used to listen for the event in plugin SDK. |
+| payload.data      | <code>any</code>             | Data you wish to emit. It can assume any data type.                    |
 
 <a name="module_RTKPlugin--module.exports+removeRTKPluginView"></a>
 
 #### module.exports.removeRTKPluginView(viewId)
+
 This method is used for cleaning up event listeners attached to an iframe. It must
 be used before the iframe is removed from the DOM.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
+| Param  | Type                | Default                          | Description                                                        |
+| ------ | ------------------- | -------------------------------- | ------------------------------------------------------------------ |
 | viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+addRTKPluginView"></a>
 
 #### module.exports.addRTKPluginView(iframe, viewId)
+
 This method adds the communication layer between the plugin inside the iframe
 and the core application (meeting object) in the main window.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |  | Iframe element to display this plugin. |
-| viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
+| Param  | Type                                                              | Default                          | Description                                                        |
+| ------ | ----------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------ |
+| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |                                  | Iframe element to display this plugin.                             |
+| viewId | <code>string</code>                                               | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+setActive"></a>
 
 #### module.exports.setActive(active)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| active | <code>boolean</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+
+| Param  | Type                 |
+| ------ | -------------------- |
+| active | <code>boolean</code> |
 
 <a name="module_RTKPlugin--module.exports+activateForSelf"></a>
 
 #### module.exports.activateForSelf()
+
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivateForSelf"></a>
 
 #### module.exports.deactivateForSelf()
+
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+enable"></a>
 
 #### ~~module.exports.enable()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+disable"></a>
 
 #### ~~module.exports.disable()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+activate"></a>
 
 #### module.exports.activate()
+
 Activate this plugin for all participants.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivate"></a>
 
 #### module.exports.deactivate()
+
 Deactivate this plugin for all participants.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
index 8ea2b9486986701..ff22e5a74589e76 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
@@ -9,37 +9,40 @@ web_core_version: 1.2.4
 <a name="module_RTKPlugins"></a>
 
 The RTKPlugins module consists of all the plugins in the meeting. It has 2 maps:
+
 - `all`: Consists of all the plugins in the meeting.
 - `active`: Consists of the plugins that are currently in use.
 
-
 * [RTKPlugins](#module_RTKPlugins)
-    * [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
-        * [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
-        * [.all](#module_RTKPlugins--module.exports+all)
-        * [.active](#module_RTKPlugins--module.exports+active)
+  - [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
+    - [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
+    - [.all](#module_RTKPlugins--module.exports+all)
+    - [.active](#module_RTKPlugins--module.exports+active)
 
 <a name="exp_module_RTKPlugins--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKPlugins--module.exports_new"></a>
 
 #### new module.exports(logger)
 
-| Param | Type |
-| --- | --- |
-| logger | <code>Logger</code> | 
+| Param  | Type                |
+| ------ | ------------------- |
+| logger | <code>Logger</code> |
 
 <a name="module_RTKPlugins--module.exports+all"></a>
 
 #### module.exports.all
+
 All plugins accessible by the current user.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
 <a name="module_RTKPlugins--module.exports+active"></a>
 
 #### module.exports.active
+
 All plugins that are currently enabled in the room.
 
-**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
+**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
index 95f20dbb49fe688..25d6abf2a17b0fe 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
@@ -10,41 +10,42 @@ web_core_version: 1.2.4
 
 The RTKPolls module consists of the polls that have been created in the meeting.
 
-
-* [RTKPolls](#module_RTKPolls)
-    * [.items](#module_RTKPolls+items)
-    * [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
-    * [.vote(pollId, index)](#module_RTKPolls+vote)
+- [RTKPolls](#module_RTKPolls)
+  - [.items](#module_RTKPolls+items)
+  - [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
+  - [.vote(pollId, index)](#module_RTKPolls+vote)
 
 <a name="module_RTKPolls+items"></a>
 
 ### meeting.polls.items
+
 An array of poll items.
 
 **Kind**: instance property of [<code>RTKPolls</code>](#module_RTKPolls)  
 <a name="module_RTKPolls+create"></a>
 
 ### meeting.polls.create(question, options, anonymous, hideVotes)
+
 Creates a poll in the meeting.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
 
-| Param | Default | Description |
-| --- | --- | --- |
-| question |  | The question that is to be voted for. |
-| options |  | The options of the poll. |
-| anonymous | <code>false</code> | If true, the poll votes are anonymous. |
+| Param     | Default            | Description                                |
+| --------- | ------------------ | ------------------------------------------ |
+| question  |                    | The question that is to be voted for.      |
+| options   |                    | The options of the poll.                   |
+| anonymous | <code>false</code> | If true, the poll votes are anonymous.     |
 | hideVotes | <code>false</code> | If true, the votes on the poll are hidden. |
 
 <a name="module_RTKPolls+vote"></a>
 
 ### meeting.polls.vote(pollId, index)
+
 Casts a vote on an existing poll.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
 
-| Param | Description |
-| --- | --- |
+| Param  | Description                                |
+| ------ | ------------------------------------------ |
 | pollId | The ID of the poll that is to be voted on. |
-| index | The index of the option. |
-
+| index  | The index of the option.                   |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
index 4b2dd3b6116b3dd..e63b1525fae136c 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
@@ -11,39 +11,43 @@ web_core_version: 1.2.4
 The RTKRecording module represents the state of the current recording, and allows
 to start/stop recordings and check if there's a recording in progress.
 
-
-* [RTKRecording](#module_RTKRecording)
-    * [.telemetry](#module_RTKRecording+telemetry)
-    * [.start()](#module_RTKRecording+start)
-    * [.stop()](#module_RTKRecording+stop)
-    * [.pause()](#module_RTKRecording+pause)
-    * [.resume()](#module_RTKRecording+resume)
+- [RTKRecording](#module_RTKRecording)
+  - [.telemetry](#module_RTKRecording+telemetry)
+  - [.start()](#module_RTKRecording+start)
+  - [.stop()](#module_RTKRecording+stop)
+  - [.pause()](#module_RTKRecording+pause)
+  - [.resume()](#module_RTKRecording+resume)
 
 <a name="module_RTKRecording+telemetry"></a>
 
 ### meeting.recording.telemetry
+
 **Kind**: instance property of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+start"></a>
 
 ### meeting.recording.start()
+
 Starts recording the meeting.
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+stop"></a>
 
 ### meeting.recording.stop()
+
 Stops all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+pause"></a>
 
 ### meeting.recording.pause()
+
 Pauses all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+resume"></a>
 
 ### meeting.recording.resume()
+
 Resumes all recording currently in 'PAUSED' state
 
-**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
+**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
index aa4a71840eac6b8..1ad8cd81f058059 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
@@ -12,42 +12,43 @@ The RTKSelf module represents the current user, and allows to modify the state
 of the user in the meeting. The audio and video streams of the user can be retrieved from
 this module.
 
-
-* [RTKSelf](#module_RTKSelf)
-    * [.telemetry](#module_RTKSelf+telemetry)
-    * [.peerId](#module_RTKSelf+peerId)
-    * [.roomState](#module_RTKSelf+roomState)
-    * [.permissions](#module_RTKSelf+permissions)
-    * [.config](#module_RTKSelf+config)
-    * [.roomJoined](#module_RTKSelf+roomJoined)
-    * [.isPinned](#module_RTKSelf+isPinned)
-    * [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
-    * [.setName(name)](#module_RTKSelf+setName)
-    * [.setupTracks(options)](#module_RTKSelf+setupTracks)
-    * [.enableAudio()](#module_RTKSelf+enableAudio)
-    * [.enableVideo()](#module_RTKSelf+enableVideo)
-    * [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
-    * [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
-    * [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
-    * [.disableAudio()](#module_RTKSelf+disableAudio)
-    * [.disableVideo()](#module_RTKSelf+disableVideo)
-    * [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
-    * [.getAllDevices()](#module_RTKSelf+getAllDevices)
-    * [.setIsPinned()](#module_RTKSelf+setIsPinned)
-    * [.pin()](#module_RTKSelf+pin)
-    * [.unpin()](#module_RTKSelf+unpin)
-    * [.hide()](#module_RTKSelf+hide)
-    * [.show()](#module_RTKSelf+show)
-    * [.setDevice(device)](#module_RTKSelf+setDevice)
-    * [.updateVideo()](#module_RTKSelf+updateVideo)
+- [RTKSelf](#module_RTKSelf)
+  - [.telemetry](#module_RTKSelf+telemetry)
+  - [.peerId](#module_RTKSelf+peerId)
+  - [.roomState](#module_RTKSelf+roomState)
+  - [.permissions](#module_RTKSelf+permissions)
+  - [.config](#module_RTKSelf+config)
+  - [.roomJoined](#module_RTKSelf+roomJoined)
+  - [.isPinned](#module_RTKSelf+isPinned)
+  - [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
+  - [.setName(name)](#module_RTKSelf+setName)
+  - [.setupTracks(options)](#module_RTKSelf+setupTracks)
+  - [.enableAudio()](#module_RTKSelf+enableAudio)
+  - [.enableVideo()](#module_RTKSelf+enableVideo)
+  - [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
+  - [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
+  - [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
+  - [.disableAudio()](#module_RTKSelf+disableAudio)
+  - [.disableVideo()](#module_RTKSelf+disableVideo)
+  - [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
+  - [.getAllDevices()](#module_RTKSelf+getAllDevices)
+  - [.setIsPinned()](#module_RTKSelf+setIsPinned)
+  - [.pin()](#module_RTKSelf+pin)
+  - [.unpin()](#module_RTKSelf+unpin)
+  - [.hide()](#module_RTKSelf+hide)
+  - [.show()](#module_RTKSelf+show)
+  - [.setDevice(device)](#module_RTKSelf+setDevice)
+  - [.updateVideo()](#module_RTKSelf+updateVideo)
 
 <a name="module_RTKSelf+telemetry"></a>
 
 ### meeting.self.telemetry
+
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+peerId"></a>
 
 ### meeting.self.peerId
+
 NOTE(ishita1805): Discussed with Ravindra, added a duplicate for consistency
 when using identifiers in Locker.
 We might want to look at deprecating the `id` sometime later.
@@ -56,6 +57,7 @@ We might want to look at deprecating the `id` sometime later.
 <a name="module_RTKSelf+roomState"></a>
 
 ### meeting.self.roomState
+
 Returns the current state of room
 init - Initial State
 joined - User is in the meeting
@@ -69,67 +71,76 @@ ended - The meeting was ended
 <a name="module_RTKSelf+permissions"></a>
 
 ### meeting.self.permissions
+
 Returns the current permission given to the user for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+config"></a>
 
 ### meeting.self.config
+
 Returns configuration for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+roomJoined"></a>
 
 ### meeting.self.roomJoined
+
 Returns true if the local participant has joined the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+isPinned"></a>
 
 ### meeting.self.isPinned
+
 Returns true if the current user is pinned.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+cleanupEvents"></a>
 
 ### meeting.self.cleanupEvents()
+
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setName"></a>
 
 ### meeting.self.setName(name)
+
 The name of the user can be set by calling this method.
 This will get reflected to other participants ONLY if
 this method is called before the room is joined.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| name | <code>string</code> | Name of the user. |
+| Param | Type                | Description       |
+| ----- | ------------------- | ----------------- |
+| name  | <code>string</code> | Name of the user. |
 
 <a name="module_RTKSelf+setupTracks"></a>
 
 ### meeting.self.setupTracks(options)
+
 Sets up the local media tracks.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
-| options | <code>Object</code> | The audio and video options. |
-| [options.video] | <code>boolean</code> | If true, the video stream is fetched. |
-| [options.audio] | <code>boolean</code> | If true, the audio stream is fetched. |
+| Param                | Type                 | Description                                       |
+| -------------------- | -------------------- | ------------------------------------------------- |
+| options              | <code>Object</code>  | The audio and video options.                      |
+| [options.video]      | <code>boolean</code> | If true, the video stream is fetched.             |
+| [options.audio]      | <code>boolean</code> | If true, the audio stream is fetched.             |
 | [options.forceReset] | <code>boolean</code> | If true, force resets tracks before re-acquiring. |
 
 <a name="module_RTKSelf+enableAudio"></a>
 
 ### meeting.self.enableAudio()
+
 This method is used to unmute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+enableVideo"></a>
 
 ### meeting.self.enableVideo()
+
 This method is used to start streaming the local participant's video
 to the meeting.
 
@@ -137,6 +148,7 @@ to the meeting.
 <a name="module_RTKSelf+updateVideoConstraints"></a>
 
 ### meeting.self.updateVideoConstraints()
+
 This method is used to apply constraints to the current video
 stream.
 
@@ -144,6 +156,7 @@ stream.
 <a name="module_RTKSelf+enableScreenShare"></a>
 
 ### meeting.self.enableScreenShare()
+
 This method is used to start sharing the local participant's screen
 to the meeting.
 
@@ -151,6 +164,7 @@ to the meeting.
 <a name="module_RTKSelf+updateScreenshareConstraints"></a>
 
 ### meeting.self.updateScreenshareConstraints()
+
 This method is used to apply constraints to the current screenshare
 stream.
 
@@ -158,34 +172,40 @@ stream.
 <a name="module_RTKSelf+disableAudio"></a>
 
 ### meeting.self.disableAudio()
+
 This method is used to mute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableVideo"></a>
 
 ### meeting.self.disableVideo()
+
 This participant is used to disable the local participant's video.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableScreenShare"></a>
 
 ### meeting.self.disableScreenShare()
+
 This method is used to stop sharing the local participant's screen.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+getAllDevices"></a>
 
 ### meeting.self.getAllDevices()
+
 Returns all media devices accessible by the local participant.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setIsPinned"></a>
 
 ### meeting.self.setIsPinned()
+
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+pin"></a>
 
 ### meeting.self.pin()
+
 Returns `self.id` if user has permission
 to pin participants.
 
@@ -193,6 +213,7 @@ to pin participants.
 <a name="module_RTKSelf+unpin"></a>
 
 ### meeting.self.unpin()
+
 Returns `self.id` if user has permission
 to unpin participants.
 
@@ -200,29 +221,33 @@ to unpin participants.
 <a name="module_RTKSelf+hide"></a>
 
 ### meeting.self.hide()
+
 Hide's user's tile in the UI (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+show"></a>
 
 ### meeting.self.show()
+
 Show's user's tile in the UI if hidden (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setDevice"></a>
 
 ### meeting.self.setDevice(device)
+
 Change the current media device that is being used by the local participant.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                         | Description                                                                                      |
+| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
 
 <a name="module_RTKSelf+updateVideo"></a>
 
 ### meeting.self.updateVideo()
+
 Internal method, do not use
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
index 9e2d6335663b878..be8f537561e76eb 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
@@ -147,16 +147,16 @@ Returns true if screen share is enabled.
 **Kind**: global variable  
 <a name="init"></a>
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Default |
-| --- | --- | --- |
-| options | <code>Object</code> |  | 
-| [options.video] | <code>boolean</code> |  | 
-| [options.audio] | <code>boolean</code> |  | 
-| [options.constraints] | <code>MediaConstraints</code> |  | 
-| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
-| [context] | <code>Context</code> | <code></code> | 
+| Param                 | Type                          | Default            |
+| --------------------- | ----------------------------- | ------------------ |
+| options               | <code>Object</code>           |                    |
+| [options.video]       | <code>boolean</code>          |                    |
+| [options.audio]       | <code>boolean</code>          |                    |
+| [options.constraints] | <code>MediaConstraints</code> |                    |
+| [skipAwaits]          | <code>boolean</code>          | <code>false</code> |
+| [context]             | <code>Context</code>          | <code></code>      |
 
 <a name="addAudioMiddleware"></a>
 
@@ -165,21 +165,21 @@ If there are more than 1 audio middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| audioMiddleware | <code>AudioMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| audioMiddleware | <code>AudioMiddleware</code> |
 
 <a name="removeAudioMiddleware"></a>
 
 Removes the audio middleware, if it is there.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| audioMiddleware | <code>AudioMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| audioMiddleware | <code>AudioMiddleware</code> |
 
 <a name="removeAllAudioMiddlewares"></a>
 
@@ -193,32 +193,32 @@ If there are more than 1 video middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| videoMiddleware | <code>VideoMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| videoMiddleware | <code>VideoMiddleware</code> |
 
 <a name="setVideoMiddlewareGlobalConfig"></a>
 
 Sets global config to be used by video middlewares.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| config | <code>VideoMiddlewareGlobalConfig</code> | config |
-| config.disablePerFrameCanvasRendering | <code>boolean</code> | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas,  it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
+| Param                                 | Type                                     | Description                                                                                                                                                                                                                                                                                               |
+| ------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| config                                | <code>VideoMiddlewareGlobalConfig</code> | config                                                                                                                                                                                                                                                                                                    |
+| config.disablePerFrameCanvasRendering | <code>boolean</code>                     | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas, it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
 
 <a name="removeVideoMiddleware"></a>
 
 Removes the video middleware, if it is there.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type |
-| --- | --- |
-| videoMiddleware | <code>VideoMiddleware</code> | 
+| Param           | Type                         |
+| --------------- | ---------------------------- |
+| videoMiddleware | <code>VideoMiddleware</code> |
 
 <a name="removeAllVideoMiddlewares"></a>
 
@@ -249,20 +249,19 @@ Returns the local participant's speaker devices.
 
 Returns the local participant's device, indexed by ID and kind.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
-| deviceId | <code>string</code> | The ID of the device. |
-| kind | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
+| Param    | Type                                                                                                 | Description                                       |
+| -------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| deviceId | <code>string</code>                                                                                  | The ID of the device.                             |
+| kind     | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
 
 <a name="setDevice"></a>
 
 Change the current media device that is being used by the local participant.
 
-**Kind**: global function  
+**Kind**: global function
 
-| Param | Type | Description |
-| --- | --- | --- |
+| Param  | Type                         | Description                                                                                      |
+| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
-
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
index 787b7778e4ea72e..35bd0dcc153011f 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
@@ -13,70 +13,76 @@ RTKStage refers to a virtual area, where participants stream are visible to othe
 When a participant is off stage, they are not producing media
 but only consuming media from participants who are on RTKStage
 
-
-* [RTKStage](#module_RTKStage)
-    * [module.exports](#exp_module_RTKStage--module.exports) ⏏
-        * [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
-        * [.telemetry](#module_RTKStage--module.exports+telemetry)
-        * [.peerId](#module_RTKStage--module.exports+peerId)
-        * [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
-        * [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
-        * [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
-        * [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
-        * [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
-        * [.join()](#module_RTKStage--module.exports+join)
-        * [.leave()](#module_RTKStage--module.exports+leave)
-        * [.kick(userIds)](#module_RTKStage--module.exports+kick)
+- [RTKStage](#module_RTKStage)
+  - [module.exports](#exp_module_RTKStage--module.exports) ⏏
+    - [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
+    - [.telemetry](#module_RTKStage--module.exports+telemetry)
+    - [.peerId](#module_RTKStage--module.exports+peerId)
+    - [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
+    - [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
+    - [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
+    - [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
+    - [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
+    - [.join()](#module_RTKStage--module.exports+join)
+    - [.leave()](#module_RTKStage--module.exports+leave)
+    - [.kick(userIds)](#module_RTKStage--module.exports+kick)
 
 <a name="exp_module_RTKStage--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKStage--module.exports_new"></a>
 
 #### new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)
 
-| Param | Type |
-| --- | --- |
-| context | <code>Context</code> | 
-| self | <code>Self</code> | 
-| participants | <code>Participants</code> | 
-| stageSocketHandler | <code>RTKStageSocketHandler</code> | 
-| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| Param              | Type                               |
+| ------------------ | ---------------------------------- |
+| context            | <code>Context</code>               |
+| self               | <code>Self</code>                  |
+| participants       | <code>Participants</code>          |
+| stageSocketHandler | <code>RTKStageSocketHandler</code> |
+| roomSocketHandler  | <code>RoomSocketHandler</code>     |
 
 <a name="module_RTKStage--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
+
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+peerId"></a>
 
 #### module.exports.peerId
+
 Returns the peerId of the current user
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+getAccessRequests"></a>
 
 #### module.exports.getAccessRequests()
+
 Method to fetch all RTKStage access requests from viewers
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+requestAccess"></a>
 
 #### module.exports.requestAccess()
+
 Method to send a request to privileged users to join the stage
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+cancelRequestAccess"></a>
 
 #### module.exports.cancelRequestAccess()
+
 Method to cancel a previous RTKStage join request
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+grantAccess"></a>
 
 #### module.exports.grantAccess()
+
 Method to grant access to RTKStage.
-	This can be in response to a RTKStage Join request but it can be called on other users as well
+This can be in response to a RTKStage Join request but it can be called on other users as well
 
 `permissions.acceptRTKStageRequests` privilege required
 
@@ -84,6 +90,7 @@ Method to grant access to RTKStage.
 <a name="module_RTKStage--module.exports+denyAccess"></a>
 
 #### module.exports.denyAccess()
+
 Method to deny access to RTKStage.
 This should be called in response to a RTKStage Join request
 
@@ -91,6 +98,7 @@ This should be called in response to a RTKStage Join request
 <a name="module_RTKStage--module.exports+join"></a>
 
 #### module.exports.join()
+
 Method to join the stage
 Users either need to have the permission in the preset or must be accepted by a privileged
 user to call this method
@@ -99,6 +107,7 @@ user to call this method
 <a name="module_RTKStage--module.exports+leave"></a>
 
 #### module.exports.leave()
+
 Method to leave the stage
 Users must either be on the stage already or be accepted to join the stage
 to call this method
@@ -107,13 +116,13 @@ to call this method
 <a name="module_RTKStage--module.exports+kick"></a>
 
 #### module.exports.kick(userIds)
+
 Method to kick a user off the stage
 
 `permissions.acceptRTKStageRequests` privilege required
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
-
-| Param | Type |
-| --- | --- |
-| userIds | <code>Array.&lt;string&gt;</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)
 
+| Param   | Type                              |
+| ------- | --------------------------------- |
+| userIds | <code>Array.&lt;string&gt;</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
index c27dd5a9443bf19..51d98a4f1ebc2ea 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
@@ -12,127 +12,136 @@ This module represents a single global store.
 The store can be accessed from the `meeting.stores` module.
 
 **Returns**: An instance of RTKStore.  
-**Example**  
+**Example**
+
 ```js
-const handRaiseRTKStore = meeting.stores.stores.get('handRaise');
+const handRaiseRTKStore = meeting.stores.stores.get("handRaise");
 ```
 
-* [RTKStore](#module_RTKStore) ⇒
-    * [module.exports](#exp_module_RTKStore--module.exports) ⏏
-        * [new module.exports(args)](#new_module_RTKStore--module.exports_new)
-        * [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
-        * [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
-        * [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
-        * [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
-        * [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
-        * [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
-        * [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
-        * [.populate(data)](#module_RTKStore--module.exports+populate)
+- [RTKStore](#module_RTKStore) ⇒
+  - [module.exports](#exp_module_RTKStore--module.exports) ⏏
+    - [new module.exports(args)](#new_module_RTKStore--module.exports_new)
+    - [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
+    - [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
+    - [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
+    - [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
+    - [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
+    - [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
+    - [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
+    - [.populate(data)](#module_RTKStore--module.exports+populate)
 
 <a name="exp_module_RTKStore--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKStore--module.exports_new"></a>
 
 #### new module.exports(args)
 
-| Param | Type |
-| --- | --- |
-| args | <code>Object</code> | 
-| args.name | <code>string</code> | 
-| args.socketHandler | <code>PluginSocketHandler</code> | 
-| args.meetingId | <code>string</code> | 
+| Param              | Type                             |
+| ------------------ | -------------------------------- |
+| args               | <code>Object</code>              |
+| args.name          | <code>string</code>              |
+| args.socketHandler | <code>PluginSocketHandler</code> |
+| args.meetingId     | <code>string</code>              |
 
 <a name="module_RTKStore--module.exports+set"></a>
 
 #### module.exports.set(key, value, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Sets a value in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| value | <code>any</code> |  | Data to be set. |
-| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
+| Param  | Type                 | Default            | Description                             |
+| ------ | -------------------- | ------------------ | --------------------------------------- |
+| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
+| value  | <code>any</code>     |                    | Data to be set.                         |
+| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
 
 <a name="module_RTKStore--module.exports+bulkSet"></a>
 
 #### module.exports.bulkSet(data) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Sets multiple values in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type |
-| --- | --- |
-| data | <code>Array.&lt;{key: string, payload: any}&gt;</code> | 
+| Param | Type                                                   |
+| ----- | ------------------------------------------------------ |
+| data  | <code>Array.&lt;{key: string, payload: any}&gt;</code> |
 
 <a name="module_RTKStore--module.exports+update"></a>
 
 #### module.exports.update(key, value, [sync]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Updates an already existing value in the store.
 If the value stored is `['a', 'b']`, the operation
 `store.update(key, ['c'])` will modify
 the value to `['a','b','c']`.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| value | <code>any</code> |  | Data to be updated. |
+| Param  | Type                 | Default           | Description                             |
+| ------ | -------------------- | ----------------- | --------------------------------------- |
+| key    | <code>string</code>  |                   | Unique identifier used to store value.  |
+| value  | <code>any</code>     |                   | Data to be updated.                     |
 | [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
 
 <a name="module_RTKStore--module.exports+delete"></a>
 
 #### module.exports.delete(key, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Deletes a key value pair form the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type | Default | Description |
-| --- | --- | --- | --- |
-| key | <code>string</code> |  | Unique identifier used to store value. |
-| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
+| Param  | Type                 | Default            | Description                             |
+| ------ | -------------------- | ------------------ | --------------------------------------- |
+| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
+| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
 
 <a name="module_RTKStore--module.exports+bulkDelete"></a>
 
 #### module.exports.bulkDelete(data) ⇒ <code>Promise.&lt;void&gt;</code>
+
 Deletes multiple values from the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
 
-| Param | Type |
-| --- | --- |
-| data | <code>Array.&lt;{key: string}&gt;</code> | 
+| Param | Type                                     |
+| ----- | ---------------------------------------- |
+| data  | <code>Array.&lt;{key: string}&gt;</code> |
 
 <a name="module_RTKStore--module.exports+get"></a>
 
 #### module.exports.get(key) ⇒ <code>any</code>
+
 Returns value for the given key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>any</code> - Value for the given key.  
+**Returns**: <code>any</code> - Value for the given key.
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
+| Param | Type                | Description                            |
+| ----- | ------------------- | -------------------------------------- |
+| key   | <code>string</code> | Unique identifier used to store value. |
 
 <a name="module_RTKStore--module.exports+getAll"></a>
 
 #### module.exports.getAll() ⇒ <code>RTKStoreData</code>
+
 Returns the entire store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
@@ -140,55 +149,59 @@ Returns the entire store.
 <a name="module_RTKStore--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKStore--module.exports+updateBulkRateLimits"></a>
 
 #### module.exports.updateBulkRateLimits(num, period)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| num | <code>number</code> | 
-| period | <code>number</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+
+| Param  | Type                |
+| ------ | ------------------- |
+| num    | <code>number</code> |
+| period | <code>number</code> |
 
 <a name="module_RTKStore--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(key, cb) ⇒ <code>void</code>
+
 Listens for data change on a store key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void  
+**Returns**: <code>void</code> - void
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
-| cb | <code>function</code> | The callback function that gets executed when data is modified. |
+| Param | Type                  | Description                                                     |
+| ----- | --------------------- | --------------------------------------------------------------- |
+| key   | <code>string</code>   | Unique identifier used to store value.                          |
+| cb    | <code>function</code> | The callback function that gets executed when data is modified. |
 
 <a name="module_RTKStore--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(key, [cb]) ⇒ <code>void</code>
+
 Removes all listeners for a key on the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void  
+**Returns**: <code>void</code> - void
 
-| Param | Type | Description |
-| --- | --- | --- |
-| key | <code>string</code> | Unique identifier used to store value. |
-| [cb] | <code>function</code> | Callback to be removed. |
+| Param | Type                  | Description                            |
+| ----- | --------------------- | -------------------------------------- |
+| key   | <code>string</code>   | Unique identifier used to store value. |
+| [cb]  | <code>function</code> | Callback to be removed.                |
 
 <a name="module_RTKStore--module.exports+populate"></a>
 
 #### module.exports.populate(data)
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| data | <code>RTKStoreData</code> | 
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
 
+| Param | Type                      |
+| ----- | ------------------------- |
+| data  | <code>RTKStoreData</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
index 88539296c8905b0..e5a1e74b8e69bcf 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
@@ -10,72 +10,78 @@ web_core_version: 1.2.4
 
 The RTKThemePreset class represents the meeting theme for the current participant
 
-
-* [RTKThemePreset](#module_RTKThemePreset)
-    * [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
-        * [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
-        * _instance_
-            * ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
-            * ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
-            * ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
-            * ~~[.header](#module_RTKThemePreset--module.exports+header)~~
-            * ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
-            * [.viewType](#module_RTKThemePreset--module.exports+viewType)
-            * [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
-            * [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
-            * [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
-            * ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
-            * [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
-        * _static_
-            * [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
-            * [.default()](#module_RTKThemePreset--module.exports.default)
-            * [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
+- [RTKThemePreset](#module_RTKThemePreset)
+  - [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
+    - [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
+    - _instance_
+      - ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
+      - ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
+      - ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
+      - ~~[.header](#module_RTKThemePreset--module.exports+header)~~
+      - ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
+      - [.viewType](#module_RTKThemePreset--module.exports+viewType)
+      - [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
+      - [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
+      - [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
+      - ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
+      - [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
+    - _static_
+      - [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
+      - [.default()](#module_RTKThemePreset--module.exports.default)
+      - [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
 
 <a name="exp_module_RTKThemePreset--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RTKThemePreset--module.exports_new"></a>
 
 #### new module.exports(preset)
 
-| Param | Type |
-| --- | --- |
-| preset | <code>PresetV2CamelCased</code> | 
+| Param  | Type                            |
+| ------ | ------------------------------- |
+| preset | <code>PresetV2CamelCased</code> |
 
 <a name="module_RTKThemePreset--module.exports+setupScreen"></a>
 
 #### ~~module.exports.setupScreen~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+waitingRoom"></a>
 
 #### ~~module.exports.waitingRoom~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+controlBar"></a>
 
 #### ~~module.exports.controlBar~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+header"></a>
 
 #### ~~module.exports.header~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+pipMode"></a>
 
 #### ~~module.exports.pipMode~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+viewType"></a>
 
 #### module.exports.viewType
+
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -83,6 +89,7 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKThemePreset--module.exports+livestreamViewerQualities"></a>
 
 #### module.exports.livestreamViewerQualities
+
 The `livestreamViewerQualities` specifies the allowed qualities of a stream,
 that can be viewed by a livestream viewer
 
@@ -90,6 +97,7 @@ that can be viewed by a livestream viewer
 <a name="module_RTKThemePreset--module.exports+maxVideoStreams"></a>
 
 #### module.exports.maxVideoStreams
+
 The `maxVideoStreams` contains the maximum video
 streams for mobile and desktop
 
@@ -97,6 +105,7 @@ streams for mobile and desktop
 <a name="module_RTKThemePreset--module.exports+maxScreenShareCount"></a>
 
 #### module.exports.maxScreenShareCount
+
 The `maxScreenShareCount` contains the maximum
 possible concurrent screen shares
 
@@ -104,37 +113,41 @@ possible concurrent screen shares
 <a name="module_RTKThemePreset--module.exports+plugins"></a>
 
 #### ~~module.exports.plugins~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+disabledPlugins"></a>
 
 #### module.exports.disabledPlugins
+
 The `disabledPlugins` property returns id of all disabled plugins
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports.fromResponse"></a>
 
 #### module.exports.fromResponse(preset)
+
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
-**Deprecated.**: Use init()  
+**Deprecated.**: Use init()
 
-| Param | Type |
-| --- | --- |
-| preset | <code>PresetV2CamelCased</code> | 
+| Param  | Type                            |
+| ------ | ------------------------------- |
+| preset | <code>PresetV2CamelCased</code> |
 
 <a name="module_RTKThemePreset--module.exports.default"></a>
 
 #### module.exports.default()
+
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 **Deprecated.**: Use init()  
 <a name="module_RTKThemePreset--module.exports.init"></a>
 
 #### module.exports.init([preset], [useDefault])
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [preset] | <code>PresetV2CamelCased</code> |  | 
-| [useDefault] | <code>boolean</code> | <code>true</code> | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)
 
+| Param        | Type                            | Default           |
+| ------------ | ------------------------------- | ----------------- |
+| [preset]     | <code>PresetV2CamelCased</code> |                   |
+| [useDefault] | <code>boolean</code>            | <code>true</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
index 1afafcb4fd4b751..31f2a68764c9ee9 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
@@ -13,45 +13,46 @@ An object of the RealtimeKitClient class can be created using
 `await RealtimeKitClient.init({ ... })`. Typically, an object of `RealtimeKitClient` is
 named `meeting`.
 
-
-* [RealtimeKitClient](#module_RealtimeKitClient)
-    * [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
-        * [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
-        * _instance_
-            * [.participants](#module_RealtimeKitClient--module.exports+participants)
-            * [.self](#module_RealtimeKitClient--module.exports+self)
-            * [.meta](#module_RealtimeKitClient--module.exports+meta)
-            * [.ai](#module_RealtimeKitClient--module.exports+ai)
-            * [.plugins](#module_RealtimeKitClient--module.exports+plugins)
-            * [.chat](#module_RealtimeKitClient--module.exports+chat)
-            * [.polls](#module_RealtimeKitClient--module.exports+polls)
-            * [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
-            * [.__internals__](#module_RealtimeKitClient--module.exports+__internals__)
-            * [.join()](#module_RealtimeKitClient--module.exports+join)
-            * [.leave()](#module_RealtimeKitClient--module.exports+leave)
-            * ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
-            * ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
-        * _static_
-            * [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
-            * [.init(options)](#module_RealtimeKitClient--module.exports.init)
-            * [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
+- [RealtimeKitClient](#module_RealtimeKitClient)
+  - [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
+    - [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
+    - _instance_
+      - [.participants](#module_RealtimeKitClient--module.exports+participants)
+      - [.self](#module_RealtimeKitClient--module.exports+self)
+      - [.meta](#module_RealtimeKitClient--module.exports+meta)
+      - [.ai](#module_RealtimeKitClient--module.exports+ai)
+      - [.plugins](#module_RealtimeKitClient--module.exports+plugins)
+      - [.chat](#module_RealtimeKitClient--module.exports+chat)
+      - [.polls](#module_RealtimeKitClient--module.exports+polls)
+      - [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
+      - [.**internals**](#module_RealtimeKitClient--module.exports+__internals__)
+      - [.join()](#module_RealtimeKitClient--module.exports+join)
+      - [.leave()](#module_RealtimeKitClient--module.exports+leave)
+      - ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
+      - ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
+    - _static_
+      - [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
+      - [.init(options)](#module_RealtimeKitClient--module.exports.init)
+      - [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
 
 <a name="exp_module_RealtimeKitClient--module.exports"></a>
 
 ### module.exports ⏏
+
 **Kind**: Exported class  
 <a name="new_module_RealtimeKitClient--module.exports_new"></a>
 
 #### new module.exports(context, controller)
 
-| Param | Type |
-| --- | --- |
-| context | <code>IContext</code> | 
-| controller | <code>Controller</code> | 
+| Param      | Type                    |
+| ---------- | ----------------------- |
+| context    | <code>IContext</code>   |
+| controller | <code>Controller</code> |
 
 <a name="module_RealtimeKitClient--module.exports+participants"></a>
 
 #### module.exports.participants
+
 The `participants` object consists of 4 maps of participants,
 `waitlisted`, `joined`, `active`, `pinned`. The maps are indexed by
 `peerId`s, and the values are the corresponding participant objects.
@@ -60,6 +61,7 @@ The `participants` object consists of 4 maps of participants,
 <a name="module_RealtimeKitClient--module.exports+self"></a>
 
 #### module.exports.self
+
 The `self` object can be used to manipulate audio and video settings,
 and other configurations for the local participant. This exposes methods
 to enable and disable media tracks, share the user's screen, etc.
@@ -68,6 +70,7 @@ to enable and disable media tracks, share the user's screen, etc.
 <a name="module_RealtimeKitClient--module.exports+meta"></a>
 
 #### module.exports.meta
+
 The `room` object stores information about the current meeting, such
 as chat messages, polls, room name, etc.
 
@@ -75,6 +78,7 @@ as chat messages, polls, room name, etc.
 <a name="module_RealtimeKitClient--module.exports+ai"></a>
 
 #### module.exports.ai
+
 The `ai` object is used to interface with AI features.
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
@@ -83,6 +87,7 @@ features such as summary, and agenda using this object.
 <a name="module_RealtimeKitClient--module.exports+plugins"></a>
 
 #### module.exports.plugins
+
 The `plugins` object stores information about the plugins available in
 the current meeting. It exposes methods to activate and deactivate them.
 
@@ -90,6 +95,7 @@ the current meeting. It exposes methods to activate and deactivate them.
 <a name="module_RealtimeKitClient--module.exports+chat"></a>
 
 #### module.exports.chat
+
 The chat object stores the chat messages that were sent in the meeting.
 This includes text messages, images, and files.
 
@@ -97,6 +103,7 @@ This includes text messages, images, and files.
 <a name="module_RealtimeKitClient--module.exports+polls"></a>
 
 #### module.exports.polls
+
 The polls object stores the polls that were initiated in the meeting.
 It exposes methods to create and vote on polls.
 
@@ -104,6 +111,7 @@ It exposes methods to create and vote on polls.
 <a name="module_RealtimeKitClient--module.exports+connectedMeetings"></a>
 
 #### module.exports.connectedMeetings
+
 The connectedMeetings object stores the connected meetings states.
 It exposes methods to create/read/update/delete methods for connected meetings.
 
@@ -111,15 +119,17 @@ It exposes methods to create/read/update/delete methods for connected meetings.
 <a name="module_RealtimeKitClient--module.exports+__internals__"></a>
 
 #### module.exports.\_\_internals\_\_
-The __internals__ object exposes the internal tools & utilities such as features and logger
+
+The **internals** object exposes the internal tools & utilities such as features and logger
 so that client can utilise the same to build their own feature based UI.
-Logger (__internals__.logger) can be used to send logs to servers
-	to inform  of issues, if any, proactively.
+Logger (**internals**.logger) can be used to send logs to servers
+to inform of issues, if any, proactively.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+join"></a>
 
 #### module.exports.join()
+
 The `join()` method can be used to join the meeting.
 A `roomJoined` event is emitted on `self` when the room
 is joined successfully.
@@ -128,65 +138,70 @@ is joined successfully.
 <a name="module_RealtimeKitClient--module.exports+leave"></a>
 
 #### module.exports.leave()
+
 The `leave()` method can be used to leave a meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+joinRoom"></a>
 
 #### ~~module.exports.joinRoom()~~
-***Deprecated***
+
+**_Deprecated_**
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+leaveRoom"></a>
 
 #### ~~module.exports.leaveRoom([state])~~
-***Deprecated***
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
+**_Deprecated_**
+
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
-| Param | Type |
-| --- | --- |
-| [state] | <code>LeaveRoomState</code> | 
+| Param   | Type                        |
+| ------- | --------------------------- |
+| [state] | <code>LeaveRoomState</code> |
 
 <a name="module_RealtimeKitClient--module.exports.initMedia"></a>
 
 #### module.exports.initMedia([options], [skipAwaits], [cachedUserDetails])
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param | Type | Default |
-| --- | --- | --- |
-| [options] | <code>Object</code> |  | 
-| [options.video] | <code>boolean</code> |  | 
-| [options.audio] | <code>boolean</code> |  | 
-| [options.constraints] | <code>MediaConstraints</code> |  | 
-| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
-| [cachedUserDetails] | <code>CachedUserDetails</code> |  | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+
+| Param                 | Type                           | Default            |
+| --------------------- | ------------------------------ | ------------------ |
+| [options]             | <code>Object</code>            |                    |
+| [options.video]       | <code>boolean</code>           |                    |
+| [options.audio]       | <code>boolean</code>           |                    |
+| [options.constraints] | <code>MediaConstraints</code>  |                    |
+| [skipAwaits]          | <code>boolean</code>           | <code>false</code> |
+| [cachedUserDetails]   | <code>CachedUserDetails</code> |                    |
 
 <a name="module_RealtimeKitClient--module.exports.init"></a>
 
 #### module.exports.init(options)
+
 The `init` method can be used to instantiate the RealtimeKitClient class.
 This returns an instance of RealtimeKitClient, which can be used to perform
 actions on the meeting.
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
-| Param | Description |
-| --- | --- |
-| options | The options object. |
+| Param             | Description                                     |
+| ----------------- | ----------------------------------------------- |
+| options           | The options object.                             |
 | options.authToken | The authorization token received using the API. |
-| options.baseURI | The base URL of the API. |
-| options.defaults | The default audio and video settings. |
+| options.baseURI   | The base URL of the API.                        |
+| options.defaults  | The default audio and video settings.           |
 
 <a name="module_RealtimeKitClient--module.exports.setupContext"></a>
 
 #### module.exports.setupContext(peerId, options, meetingId, args)
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param | Type |
-| --- | --- |
-| peerId | <code>string</code> | 
-| options | <code>RealtimeKitClientOptions</code> | 
-| meetingId | <code>string</code> | 
-| args | <code>any</code> | 
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
 
+| Param     | Type                                  |
+| --------- | ------------------------------------- |
+| peerId    | <code>string</code>                   |
+| options   | <code>RealtimeKitClientOptions</code> |
+| meetingId | <code>string</code>                   |
+| args      | <code>any</code>                      |
diff --git a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
index b94947abd5d3245..d9e3105165b252d 100644
--- a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
+++ b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
@@ -23,6 +23,7 @@ The following SDKs are collectively referred to as Web SDKs:
 - [`@cloudflare/realtimekit-virtual-background`](https://www.npmjs.com/package/@cloudflare/realtimekit-virtual-background)
 
 Overview of licenses:
+
 - Apache-2.0 (3)
 - ISC (1)
 - MIT (16)
@@ -813,10 +814,12 @@ Apache License
 ## RealtimeKit Android SDKs
 
 The following SDKs are collectively referred to as Android SDKs:
+
 - [`com.cloudflare.realtimekit:core-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-android)
 - [`com.cloudflare.realtimekit:ui-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/ui-android)
 
 Overview of licenses:
+
 - Apache-2.0 (24)
 
 ### Apache-2.0 (15 packages)
@@ -1932,11 +1935,13 @@ Apache License
 ## RealtimeKit iOS SDKs
 
 The following SDKs are collectively referred to as iOS SDKs:
+
 - [`RealtimeKit`](https://github.com/dyte-in/RealtimeKitCoreiOS)
 - [`RealtimeKitUI`](https://github.com/dyte-in/RealtimeKitUI)
 - [`RealtimeKit KMM Core`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-iosarm64)
 
 Overview of licenses:
+
 - Apache-2.0 (8)
 
 ### Apache-2.0 (4 packages)
@@ -2812,10 +2817,12 @@ Apache License
 ## RealtimeKit Flutter SDKs
 
 The following SDKs are collectively referred to as Flutter SDKs:
+
 - [`realtimekit_core`](https://pub.dev/packages/realtimekit_core)
 - [`realtimekit_ui`](https://pub.dev/packages/realtimekit_ui)
 
 Overview of licenses:
+
 - Apache-2.0 (1)
 - BSD-3-Clause (55)
 - MIT (10)
@@ -2848,7 +2855,7 @@ Used by:
 [watcher](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2014, the Dart project authors. 
+Copyright 2014, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -2892,7 +2899,7 @@ Used by:
 [typed_data](https://github.com/dart-lang/core)
 
 ```
-Copyright 2015, the Dart project authors. 
+Copyright 2015, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3167,7 +3174,7 @@ Used by:
 [term_glyph](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2017, the Dart project authors. 
+Copyright 2017, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3205,7 +3212,7 @@ Used by:
 [package_config](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2019, the Dart project authors. 
+Copyright 2019, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3243,7 +3250,7 @@ Used by:
 [logging](https://github.com/dart-lang/core)
 
 ```
-Copyright 2013, the Dart project authors. 
+Copyright 2013, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3281,7 +3288,7 @@ Used by:
 [test_core](https://github.com/dart-lang/test)
 
 ```
-Copyright 2018, the Dart project authors. 
+Copyright 2018, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3751,11 +3758,11 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ```
 
-### BSD-3-Clause (_fe_analyzer_shared)
+### BSD-3-Clause (\_fe_analyzer_shared)
 
 Used by:
 
-[_fe_analyzer_shared](https://github.com/dart-lang/sdk)
+[\_fe_analyzer_shared](https://github.com/dart-lang/sdk)
 
 ```
 Copyright 2019, the Dart project authors.
@@ -3923,7 +3930,7 @@ Used by:
 [web_socket_channel](https://github.com/dart-lang/http)
 
 ```
-Copyright 2016, the Dart project authors. 
+Copyright 2016, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3994,7 +4001,7 @@ Used by:
 [web_socket](https://github.com/dart-lang/http)
 
 ```
-Copyright 2024, the Dart project authors. 
+Copyright 2024, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4030,7 +4037,7 @@ Used by:
 [frontend_server_client](https://github.com/dart-lang/webdev)
 
 ```
-Copyright 2020, the Dart project authors. 
+Copyright 2020, the Dart project authors.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4610,10 +4617,12 @@ THE SOFTWARE.
 ## RealtimeKit React Native SDKs
 
 The following SDKs are collectively referred to as React Native SDKs:
+
 - [`@cloudflare/realtimekit-react-native`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native)
 - [`@cloudflare/realtimekit-react-native-ui`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native-ui)
 
 Overview of licenses:
+
 - Apache-2.0 (3)
 - BSD-2-Clause (10)
 - BSD-3-Clause (3)
@@ -6696,25 +6705,25 @@ The MIT License
 
 Copyright (c) 2013 Dominic Tarr
 
-Permission is hereby granted, free of charge, 
-to any person obtaining a copy of this software and 
-associated documentation files (the "Software"), to 
-deal in the Software without restriction, including 
-without limitation the rights to use, copy, modify, 
-merge, publish, distribute, sublicense, and/or sell 
-copies of the Software, and to permit persons to whom 
-the Software is furnished to do so, 
+Permission is hereby granted, free of charge,
+to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to
+deal in the Software without restriction, including
+without limitation the rights to use, copy, modify,
+merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom
+the Software is furnished to do so,
 subject to the following conditions:
 
-The above copyright notice and this permission notice 
+The above copyright notice and this permission notice
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -7691,25 +7700,25 @@ The MIT License
 
 Copyright (c) 2015 John Hiesey
 
-Permission is hereby granted, free of charge, 
-to any person obtaining a copy of this software and 
-associated documentation files (the "Software"), to 
-deal in the Software without restriction, including 
-without limitation the rights to use, copy, modify, 
-merge, publish, distribute, sublicense, and/or sell 
-copies of the Software, and to permit persons to whom 
-the Software is furnished to do so, 
+Permission is hereby granted, free of charge,
+to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to
+deal in the Software without restriction, including
+without limitation the rights to use, copy, modify,
+merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom
+the Software is furnished to do so,
 subject to the following conditions:
 
-The above copyright notice and this permission notice 
+The above copyright notice and this permission notice
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -8668,7 +8677,7 @@ Used by:
 ```
 The MIT License (MIT)
 
-Copyright (c) 2015 
+Copyright (c) 2015
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9197,7 +9206,7 @@ Used by:
 [convert-source-map](https://github.com/thlorenz/convert-source-map)
 
 ```
-Copyright 2013 Thorsten Lorenz. 
+Copyright 2013 Thorsten Lorenz.
 All rights reserved.
 
 Permission is hereby granted, free of charge, to any person
@@ -9547,7 +9556,7 @@ exhaustive, and do not form part of our licenses.
      such as asking that all changes be marked or described.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
-     for the public: 
+     for the public:
 	wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
@@ -10881,4 +10890,4 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
index 3a3cdb4f8122af5..837b0108533d03f 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
@@ -18,15 +18,15 @@ RealtimeKit's watermark feature enables you to include an image as a watermark i
 
 ```json
 {
-  "video_config": {
-    "watermark": {
-      "url": "https://test.io/images/client-logos-6.webp",
-      "position": "left top",
-      "size": {
-        "height": 20,
-        "width": 100
-      }
-    }
-  }
+	"video_config": {
+		"watermark": {
+			"url": "https://test.io/images/client-logos-6.webp",
+			"position": "left top",
+			"size": {
+				"height": 20,
+				"width": 100
+			}
+		}
+	}
 }
 ```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
index e79a05b4153957e..f6ff1aa7a6b2ed3 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
@@ -26,9 +26,9 @@ example:
 
 ```json
 {
-  "video_config": {
-    "codec": "H264"
-  }
+	"video_config": {
+		"codec": "H264"
+	}
 }
 ```
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
index dd3305069dadec9..5fa72f9105b9299 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
@@ -17,9 +17,9 @@ Visit the following pages to learn more about recording meetings:
 
 <DirectoryListing />
 
-RealtimeKit can record the audio and video of multiple users in a meeting, as well as interactions with RealtimeKit plugins, in a single file using composite recording mode. RealtimeKit can also record separate participant audio tracks using track recording.
+RealtimeKit can record the audio and video of multiple users in a meeting, as well as interactions with RealtimeKit plugins, in a single file using composite recording mode. RealtimeKit can also record separate participant audio tracks using [track recording](/realtime/realtimekit/recording-guide/track-recording/).
 
-## How does composite recording work
+## How does RealtimeKit recording work?
 
 Composite recordings are powered by anonymous virtual bot users who join your
 meeting, record it, and then upload it to RealtimeKit's Cloudflare R2 bucket. For video files,
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
index 67da5cc041affca..81744c2746450cb 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
@@ -12,13 +12,13 @@ products:
 
 The recording of a meeting can have the following states:
 
-| Name      | Description                                                                                                                                                                                                                                         |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                  |
-| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                      |
+| Name      | Description                                                                                                                                                                                                                                                |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                         |
+| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                             |
 | UPLOADING | The recording has been stopped and the file is being uploaded to the cloud storage. If you have not specified storage details, then the files will be uploaded only to RealtimeKit's server. Any RTMP and livestreaming link will also stop at this stage. |
-| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                     |
-| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                    |
+| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                            |
+| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                           |
 
 ## Fetching the state
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
index a530264178e2cd7..740b8984d91accc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
index 9022f7eef15914a..be354415f804c68 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-ai-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
-</rtk-ai-toggle>
+<rtk-ai-toggle [meeting]="meeting" size="md" variant="button"> </rtk-ai-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
index 36207327073578c..05bb2a1ea2666d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-ai-transcriptions component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
@@ -26,9 +27,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-transcriptions
- [initialTranscriptions]="[]"
- [meeting]="meeting">
+<rtk-ai-transcriptions [initialTranscriptions]="[]" [meeting]="meeting">
 </rtk-ai-transcriptions>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
index 936d95be25b08c0..8d64f23b0df3f0b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ai component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai
- [meeting]="meeting"
- size="md"
- [view]="aiview">
-</rtk-ai>
+<rtk-ai [meeting]="meeting" size="md" [view]="aiview"> </rtk-ai>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
index 690fb5c0632fc17..74fb58b92b23308 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-grid component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-grid
- [config]="defaultUiConfig"
- [hideSelf]="true"
- [meeting]="meeting">
+	[config]="defaultUiConfig"
+	[hideSelf]="true"
+	[meeting]="meeting"
+>
 </rtk-audio-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
index dbb17aafd24724b..9fa0eff7807d9be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-tile component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-tile
- [config]="defaultUiConfig"
- [meeting]="meeting"
- [participant]="participant">
+	[config]="defaultUiConfig"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-audio-tile>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
index 1622d030b9255cf..cc99527e230b702 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-audio-visualizer component (Angular Library)
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ An audio visualizer component which visualizes a participants audio.
 ```html
 <!-- component.html -->
 <rtk-audio-visualizer
- [hideMuted]="true"
- [isScreenShare]="true"
- [participant]="participant">
+	[hideMuted]="true"
+	[isScreenShare]="true"
+	[participant]="participant"
+>
 </rtk-audio-visualizer>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
index ff5a9ab19b357c0..6bd382f5ba1c7b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-avatar component (Angular Library)
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ Avatar component which renders a participant's image or their initials.
 
 ```html
 <!-- component.html -->
-<rtk-avatar
- participant="example"
- size="md"
- variant="circular">
-</rtk-avatar>
+<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
index b310482b33cdfe8..942b66a929beefc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-breakout-room-manager component (Angular Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-breakout-room-manager
- [allowDelete]="true"
- [assigningParticipants]="true"
- [defaultExpanded]="true">
+	[allowDelete]="true"
+	[assigningParticipants]="true"
+	[defaultExpanded]="true"
+>
 </rtk-breakout-room-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
index 2d1f1e58d56e53f..8d2a38f304f03fd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-breakout-room-participants component (Angular
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-breakout-room-participants
- [meeting]="meeting"
- participantIds="example"
- selectedParticipantIds="example">
+	[meeting]="meeting"
+	participantIds="example"
+	selectedParticipantIds="example"
+>
 </rtk-breakout-room-participants>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
index bbe7a129471cfef..6b60a42d4f64b07 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-breakout-rooms-manager component (Angular Lib
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-breakout-rooms-manager
- [meeting]="meeting">
-</rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager [meeting]="meeting"> </rtk-breakout-rooms-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
index dab4a3a9ced6758..e769d064ce27906 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-breakout-rooms-toggle component (Angular Libr
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A button which toggles visibility of breakout rooms.
 ```html
 <!-- component.html -->
 <rtk-breakout-rooms-toggle
- [iconPack]="defaultIconPack"
- [meeting]="meeting"
- size="md">
+	[iconPack]="defaultIconPack"
+	[meeting]="meeting"
+	size="md"
+>
 </rtk-breakout-rooms-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
index 706f133335069c4..a9399e40c4b7a2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-broadcast-message-modal component (Angular Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-broadcast-message-modal
- [meeting]="meeting">
-</rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal [meeting]="meeting"> </rtk-broadcast-message-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
index ed08f480b320ab1..49d3ca7ffe6a357 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-button component (Angular Library)
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A button that follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-button
- [disabled]="true"
- [kind]="buttonkind"
- [reverse]="true">
+<rtk-button [disabled]="true" [kind]="buttonkind" [reverse]="true">
 </rtk-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
index 755404225238040..92270e3c97fe0e1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-camera-selector component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -39,9 +41,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-camera-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-camera-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
index 00b9d2b1e4bdd06..db38dc91c0aac70 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-camera-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles your camera.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ A button which toggles your camera.
 
 ```html
 <!-- component.html -->
-<rtk-camera-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-camera-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-camera-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
index 66da419d1dea460..5dc17611c79b114 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-caption-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-caption-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-caption-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-caption-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
index ee2887a10f7e46a..b6ff46e4d62c8d9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat-composer-ui component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-composer-ui
- [canSendFiles]="true"
- [canSendTextMessage]="true"
- size="md">
+	[canSendFiles]="true"
+	[canSendTextMessage]="true"
+	size="md"
+>
 </rtk-chat-composer-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
index 407b10b43a4197f..3b98703d1ac78cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-chat-composer-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
@@ -37,9 +38,9 @@ A component which renders a chat composer
 ```html
 <!-- component.html -->
 <rtk-chat-composer-view
- [canSendFiles]="true"
- [canSendTextMessage]="true"
- inputTextPlaceholder="example">
+	[canSendFiles]="true"
+	[canSendTextMessage]="true"
+	inputTextPlaceholder="example"
+>
 </rtk-chat-composer-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
index 400bbe3d46a8aaa..18489ada36fdf99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
@@ -5,9 +5,10 @@ description: API reference for rtk-chat-header component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
@@ -17,4 +18,3 @@ products:
 <!-- component.html -->
 <rtk-chat-header></rtk-chat-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
index de48d16b7b4d731..98cb5beca666769 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
@@ -5,29 +5,30 @@ description: API reference for rtk-chat-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
@@ -42,10 +43,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-message
- [alignRight]="true"
- [canDelete]="true"
- [canEdit]="true">
+<rtk-chat-message [alignRight]="true" [canDelete]="true" [canEdit]="true">
 </rtk-chat-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
index ce18aa44fb427c7..b42f6dc5f8f79eb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-chat-messages-ui-paginated component (Angular
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui-paginated
- [meeting]="meeting"
- [privateChatRecipient]="participant | null"
- size="md">
+	[meeting]="meeting"
+	[privateChatRecipient]="participant | null"
+	size="md"
+>
 </rtk-chat-messages-ui-paginated>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
index 30863c471104539..5241b26b67f1ef7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-chat-messages-ui component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui
- [canPinMessages]="true"
- [messages]="[]"
- selectedGroup="example">
+	[canPinMessages]="true"
+	[messages]="[]"
+	selectedGroup="example"
+>
 </rtk-chat-messages-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
index c523cd074c0f8b5..674604a158dad2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-search-results component (Angular Librar
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-search-results
- channelId="example"
- [meeting]="meeting"
- query="example">
+	channelId="example"
+	[meeting]="meeting"
+	query="example"
+>
 </rtk-chat-search-results>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
index 0ab9edbe1fcae7c..784cf425f1ad9a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-chat-selector-ui component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-selector-ui
- [groups]="[]"
- selectedGroupId="example"
- selfUserId="example">
+	[groups]="[]"
+	selectedGroupId="example"
+	selfUserId="example"
+>
 </rtk-chat-selector-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
index e7e5178d7c5072b..ef6a41c79405f4a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-selector component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-selector
- [meeting]="meeting"
- size="md">
-</rtk-chat-selector>
+<rtk-chat-selector [meeting]="meeting" size="md"> </rtk-chat-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
index 1973396bb8401c2..942cba2a0f25e3c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
@@ -5,23 +5,28 @@ description: API reference for rtk-chat-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of chat.
- You need to pass the `meeting` object to it to see the unread messages count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'chat' }
- ```
+You need to pass the `meeting` object to it to see the unread messages count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "chat";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -36,10 +41,6 @@ A button which toggles visibility of chat.
 
 ```html
 <!-- component.html -->
-<rtk-chat-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-chat-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-chat-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
index 12504ff17633de3..b968cfe975421fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat component (Angular Library)
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 
 ```html
 <!-- component.html -->
-<rtk-chat
- [meeting]="meeting"
- size="md">
-</rtk-chat>
+<rtk-chat [meeting]="meeting" size="md"> </rtk-chat>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
index fe930adaf1f7baf..eea055224c112f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-clock component (Angular Library)
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ Shows the time elapsed in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-clock
- [meeting]="meeting"
- size="md">
-</rtk-clock>
+<rtk-clock [meeting]="meeting" size="md"> </rtk-clock>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
index 9af1775bf822f6f..cd3a2dc87b17a9f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-confirmation-modal component (Angular Library
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,8 +30,5 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-confirmation-modal
- [meeting]="meeting">
-</rtk-confirmation-modal>
+<rtk-confirmation-modal [meeting]="meeting"> </rtk-confirmation-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
index 52a23c6c3a7c14b..85344ab73bbbe9e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-controlbar-button component (Angular Library)
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A skeleton component used for composing custom controlbar buttons.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar-button
- [brandIcon]="true"
- [disabled]="true"
- icon="example">
+<rtk-controlbar-button [brandIcon]="true" [disabled]="true" icon="example">
 </rtk-controlbar-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
index e7d739a49130cb7..f06437464f138a2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-controlbar component (Angular Library)
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,10 +34,6 @@ Controlbar component provides you with various designs as variants.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar
- [disableRender]="true"
- [meeting]="meeting"
- size="md">
+<rtk-controlbar [disableRender]="true" [meeting]="meeting" size="md">
 </rtk-controlbar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
index 1dcbd9f1997daff..61d79e5a7230d1b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-counter component (Angular Library)
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A number picker with increment and decrement buttons.
 
 ```html
 <!-- component.html -->
-<rtk-counter
- minValue="42"
- size="md"
- value="42">
-</rtk-counter>
+<rtk-counter minValue="42" size="md" value="42"> </rtk-counter>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
index 958771b9756d2be..b878475ad72fa65 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-audio component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-audio
- [meeting]="meeting"
- size="md">
-</rtk-debugger-audio>
+<rtk-debugger-audio [meeting]="meeting" size="md"> </rtk-debugger-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
index d6002b9a6aecd84..c78c0ff33fa40dd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-screenshare component (Angular Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-screenshare
- [meeting]="meeting"
- size="md">
+<rtk-debugger-screenshare [meeting]="meeting" size="md">
 </rtk-debugger-screenshare>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
index 60e7d5bb6289f9b..ea1d6d90d2b938e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-system component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-system
- [meeting]="meeting"
- size="md">
-</rtk-debugger-system>
+<rtk-debugger-system [meeting]="meeting" size="md"> </rtk-debugger-system>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
index 6c7e30bd9fcf7f5..3e69cb73fef0b73 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-debugger-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-debugger-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-debugger-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
index d5210d91dc9db4d..2a84fafef9eb27b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-video component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-video
- [meeting]="meeting"
- size="md">
-</rtk-debugger-video>
+<rtk-debugger-video [meeting]="meeting" size="md"> </rtk-debugger-video>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
index 40b74b2e1ab8c69..f73efac1fa88dbf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-debugger component (Angular Library)
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,5 @@ A troubleshooting component to identify and fix any issues in the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-debugger
- [meeting]="meeting"
- size="md">
-</rtk-debugger>
+<rtk-debugger [meeting]="meeting" size="md"> </rtk-debugger>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
index c1de127979df06a..db0a49fdc7627bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
@@ -5,24 +5,26 @@ description: API reference for rtk-dialog-manager component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -37,9 +39,5 @@ A component which handles all dialog elements in a component such as:
 
 ```html
 <!-- component.html -->
-<rtk-dialog-manager
- [meeting]="meeting"
- size="md">
-</rtk-dialog-manager>
+<rtk-dialog-manager [meeting]="meeting" size="md"> </rtk-dialog-manager>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
index 9635ed56702713b..76e69151c16a283 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-dialog component (Angular Library)
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A dialog component.
 ```html
 <!-- component.html -->
 <rtk-dialog
- [disableEscapeKey]="true"
- [hideCloseButton]="true"
- [meeting]="meeting">
+	[disableEscapeKey]="true"
+	[hideCloseButton]="true"
+	[meeting]="meeting"
+>
 </rtk-dialog>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
index a8934fc38c1e469..41ba93a5da182cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-emoji-picker-button component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker-button
- [isActive]="true">
-</rtk-emoji-picker-button>
+<rtk-emoji-picker-button [isActive]="true"> </rtk-emoji-picker-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
index 4247ddbd5c1ce10..01b94d697105b34 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-emoji-picker component (Angular Library)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A very simple emoji picker component.
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker
- [focusWhenOpened]="true">
-</rtk-emoji-picker>
+<rtk-emoji-picker [focusWhenOpened]="true"> </rtk-emoji-picker>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
index b354fa28a6845bf..b2ad7d8f8e7eea2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-ended-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A screen which shows a meeting has ended.
 
 ```html
 <!-- component.html -->
-<rtk-ended-screen
- [meeting]="meeting"
- size="md">
-</rtk-ended-screen>
+<rtk-ended-screen [meeting]="meeting" size="md"> </rtk-ended-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
index 8344ce746896053..57ffa8f9039d89a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-file-dropzone component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-dropzone
- [hostEl]="htmlelement">
-</rtk-file-dropzone>
+<rtk-file-dropzone [hostEl]="htmlelement"> </rtk-file-dropzone>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
index 48e4cca9eee6790..858399c5abccaed 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-file-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ A component which renders a file message.
 
 ```html
 <!-- component.html -->
-<rtk-file-message-view
- name="example"
- size="42"
- url="example">
+<rtk-file-message-view name="example" size="42" url="example">
 </rtk-file-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
index a19ab17f5b413c7..d32dd9edc995033 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-file-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-message
- [isContinued]="true"
- [message]="filemessage"
- [now]="date">
+<rtk-file-message [isContinued]="true" [message]="filemessage" [now]="date">
 </rtk-file-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
index 4bda6955ac1042e..2470555e83eff13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-file-picker-button component (Angular Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-file-picker-button
- filter="example"
- [icon]="defaultIconPack"
- label="example">
+	filter="example"
+	[icon]="defaultIconPack"
+	label="example"
+>
 </rtk-file-picker-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
index f1d002421e860d8..04544ab3ecc21c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-fullscreen-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles full screen mode for any
- existing `rtk-meeting` component in the DOM.
+existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property        | Type                | Required | Default           | Description                  |
+| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
+| `size`          | `Size`              | ✅       | -                 | Size                         |
+| `states`        | `States`            | ✅       | -                 | States object                |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
+| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
+| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ A button which toggles full screen mode for any
 
 ```html
 <!-- component.html -->
-<rtk-fullscreen-toggle
- size="md"
- [targetElement]="htmlelement"
- variant="button">
+<rtk-fullscreen-toggle size="md" [targetElement]="htmlelement" variant="button">
 </rtk-fullscreen-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
index 535638be929e69a..04a546d6b3f89a5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-grid-pagination component (Angular Library)
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A component which allows you to change current page and view mode
 ```html
 <!-- component.html -->
 <rtk-grid-pagination
- [meeting]="meeting"
- size="md"
- [variant]="gridpaginationvariants">
+	[meeting]="meeting"
+	size="md"
+	[variant]="gridpaginationvariants"
+>
 </rtk-grid-pagination>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
index bd36da17a99fc2e..0c97b4b23ee5ea2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-grid component (Angular Library)
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
@@ -36,10 +37,5 @@ The main grid component which abstracts all the grid handling logic and renders
 
 ```html
 <!-- component.html -->
-<rtk-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
-</rtk-grid>
+<rtk-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
index 6308160dae44850..c09018ff727582b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-header component (Angular Library)
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,10 +34,5 @@ A component that houses all the header components.
 
 ```html
 <!-- component.html -->
-<rtk-header
- [disableRender]="true"
- [meeting]="meeting"
- size="md">
-</rtk-header>
+<rtk-header [disableRender]="true" [meeting]="meeting" size="md"> </rtk-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
index b78675a57bf3f47..fdb32d3739e666a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-icon component (Angular Library)
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
@@ -28,10 +29,5 @@ An icon component which accepts an svg string and renders it.
 
 ```html
 <!-- component.html -->
-<rtk-icon
- icon="example"
- size="md"
- variant="primary">
-</rtk-icon>
+<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
index 98bd3fd010f365a..a5a0b562a10c71e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-idle-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A screen that handles the idle state,
 
 ```html
 <!-- component.html -->
-<rtk-idle-screen
- [meeting]="meeting">
-</rtk-idle-screen>
+<rtk-idle-screen [meeting]="meeting"> </rtk-idle-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
index ae4305bd0b859b1..b6624557f5b530d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-image-message-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A component which renders an image message.
 
 ```html
 <!-- component.html -->
-<rtk-image-message-view
- url="example">
-</rtk-image-message-view>
+<rtk-image-message-view url="example"> </rtk-image-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
index e61a9e43a995966..57f711994dc6ea4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-image-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-image-message
- [isContinued]="true"
- [message]="imagemessage"
- [now]="date">
+<rtk-image-message [isContinued]="true" [message]="imagemessage" [now]="date">
 </rtk-image-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
index ce55f03e3a1012b..a5c26ec0490046f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-image-viewer component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows an image sent via chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-viewer
- [image]="imagemessage"
- size="md">
-</rtk-image-viewer>
+<rtk-image-viewer [image]="imagemessage" size="md"> </rtk-image-viewer>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
index 87a5a453715b10c..4a0ff811c795716 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
@@ -5,11 +5,12 @@ description: API reference for rtk-information-tooltip component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
@@ -24,8 +25,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-information-tooltip
- [iconPack]="defaultIconPack">
+<rtk-information-tooltip [iconPack]="defaultIconPack">
 </rtk-information-tooltip>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
index 877a7a5fef233c5..54215fd0fe361ad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-join-stage component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-join-stage
- [dataConfig]="modaldataconfig"
- [meeting]="meeting"
- size="md">
+<rtk-join-stage [dataConfig]="modaldataconfig" [meeting]="meeting" size="md">
 </rtk-join-stage>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
index 28820eb49fe7d0e..57d4746414928cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-leave-button component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description |
+| ---------- | ------------------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size`              | ✅       | -                 | Size        |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A button which toggles visilibility of the leave confirmation dialog.
 
 ```html
 <!-- component.html -->
-<rtk-leave-button
- size="md"
- variant="button">
-</rtk-leave-button>
+<rtk-leave-button size="md" variant="button"> </rtk-leave-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
index 46d14fe211c640f..97cb75f991a2535 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-leave-meeting component (Angular Library)
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A component which allows you to leave a meeting or
 
 ```html
 <!-- component.html -->
-<rtk-leave-meeting
- [meeting]="meeting">
-</rtk-leave-meeting>
+<rtk-leave-meeting [meeting]="meeting"> </rtk-leave-meeting>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
index 04858c6a723e9f5..5822982df0f5a65 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-indicator component (Angular Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-indicator
- [meeting]="meeting"
- size="md">
+<rtk-livestream-indicator [meeting]="meeting" size="md">
 </rtk-livestream-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
index 35b411555cd3561..4aedae8a958db06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-player component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-player
- [meeting]="meeting"
- size="md">
-</rtk-livestream-player>
+<rtk-livestream-player [meeting]="meeting" size="md"> </rtk-livestream-player>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
index b965a5d73aa5a9c..43e52a53ecca76d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-livestream-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -28,10 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-livestream-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-livestream-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
index c7422b474f26bde..8a910a96dda8544 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-logo component (Angular Library)
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 
 ```html
 <!-- component.html -->
-<rtk-logo
- logoUrl="example"
- [meeting]="meeting">
-</rtk-logo>
+<rtk-logo logoUrl="example" [meeting]="meeting"> </rtk-logo>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
index a7f872c4122307b..b5b816456292b1a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
@@ -5,12 +5,13 @@ description: API reference for rtk-markdown-view component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
@@ -25,9 +26,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-markdown-view
- maxLength="42"
- text="example">
-</rtk-markdown-view>
+<rtk-markdown-view maxLength="42" text="example"> </rtk-markdown-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
index 31cbdb86d3736f2..6adbeb63b44a99a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-meeting-title component (Angular Library)
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ Displays the title of the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-meeting-title
- [meeting]="meeting">
-</rtk-meeting-title>
+<rtk-meeting-title [meeting]="meeting"> </rtk-meeting-title>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
index f1727781860d6f0..fb1306311adea67 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
@@ -5,27 +5,28 @@ description: API reference for rtk-meeting component (Angular Library)
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
@@ -41,9 +42,9 @@ A single component which renders an entire meeting UI.
 ```html
 <!-- component.html -->
 <rtk-meeting
- [applyDesignSystem]="true"
- [config]="defaultUiConfig"
- [gridLayout]="gridlayout1">
+	[applyDesignSystem]="true"
+	[config]="defaultUiConfig"
+	[gridLayout]="gridlayout1"
+>
 </rtk-meeting>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
index b640c6b002c812a..ec230b806744c2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-menu-item component (Angular Library)
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -29,9 +30,6 @@ A menu item component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-item
- [menuVariant]="'primary' | 'secondary'"
- size="md">
+<rtk-menu-item [menuVariant]="'primary' | 'secondary'" size="md">
 </rtk-menu-item>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
index 7637b0961658634..cc93e411c5ade5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-menu-list component (Angular Library)
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -28,8 +29,5 @@ A menu list component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-list
- [menuVariant]="'primary' | 'secondary'">
-</rtk-menu-list>
+<rtk-menu-list [menuVariant]="'primary' | 'secondary'"> </rtk-menu-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
index 166ba3bed89a7cc..75bea868f269ae2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-menu component (Angular Library)
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A menu component.
 
 ```html
 <!-- component.html -->
-<rtk-menu
- offset="42"
- [placement]="placement"
- size="md">
-</rtk-menu>
+<rtk-menu offset="42" [placement]="placement" size="md"> </rtk-menu>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
index 3a2c6f64fdbcb64..c6e6a410829ecf7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-message-list-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders list of messages.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
-| `messages` | `Message[]` | ✅ | - | Messages to render |
-| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
-| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
+| Property            | Type                                | Required | Default           | Description                                                                   |
+| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
+| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
+| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
+| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
+| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
+| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
+| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ A component which renders list of messages.
 ```html
 <!-- component.html -->
 <rtk-message-list-view
- estimateItemSize="42"
- [loadMore]="(lastmessage: message)"
- [messages]="[]">
+	estimateItemSize="42"
+	[loadMore]="(lastmessage: message)"
+	[messages]="[]"
+>
 </rtk-message-list-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
index b9ab493f273c95c..cf2cd2949c924ba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
@@ -5,24 +5,25 @@ description: API reference for rtk-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
@@ -37,10 +38,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-message-view
- [actions]="[]"
- authorName="example"
- avatarUrl="example">
+<rtk-message-view [actions]="[]" authorName="example" avatarUrl="example">
 </rtk-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
index a99b4422c32892b..2f9fa6aaf5f2e0e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-mic-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles your microphone.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ A button which toggles your microphone.
 
 ```html
 <!-- component.html -->
-<rtk-mic-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-mic-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-mic-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
index e387ad7b10c0480..1cd58cb2ab66302 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-microphone-selector component (Angular Librar
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -39,9 +41,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-microphone-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-microphone-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
index fce5f3ee1150759..bc1d583c35d077b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
@@ -5,26 +5,27 @@ description: API reference for rtk-mixed-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -39,10 +40,5 @@ A grid component which handles screenshares, plugins and participants.
 
 ```html
 <!-- component.html -->
-<rtk-mixed-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
-</rtk-mixed-grid>
+<rtk-mixed-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-mixed-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
index da82abf95847f76..b6d4f9cd6a2fb91 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
@@ -5,20 +5,24 @@ description: API reference for rtk-more-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -33,8 +37,5 @@ A button which toggles visibility of a more menu.
 
 ```html
 <!-- component.html -->
-<rtk-more-toggle
- size="md">
-</rtk-more-toggle>
+<rtk-more-toggle size="md"> </rtk-more-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
index 267acdbbab6197c..e1a63a750b62c5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-mute-all-button component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -28,10 +29,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-button
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-mute-all-button [meeting]="meeting" size="md" variant="button">
 </rtk-mute-all-button>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
index fd686e57c8f8e71..406a2e94c9b8462 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-mute-all-confirmation component (Angular Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-confirmation
- [meeting]="meeting">
-</rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation [meeting]="meeting"> </rtk-mute-all-confirmation>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
index ab2fdfe0ef135b8..4f21452d80b34f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-name-tag component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
@@ -33,9 +34,9 @@ A component which shows a participant's name.
 ```html
 <!-- component.html -->
 <rtk-name-tag
- [isScreenShare]="true"
- [meeting]="meeting"
- [participant]="participant">
+	[isScreenShare]="true"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-name-tag>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
index 7a1feeae085082d..2776b79be409e22 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-network-indicator component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-network-indicator
- [isScreenShare]="true"
- [meeting]="meeting"
- [participant]="participant">
+	[isScreenShare]="true"
+	[meeting]="meeting"
+	[participant]="participant"
+>
 </rtk-network-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
index 4bb7b34755028e3..3125a0458248d60 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-notification component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ A component which shows a notification.
 
 ```html
 <!-- component.html -->
-<rtk-notification
- [notification]="notification"
- [paused]="true"
- size="md">
+<rtk-notification [notification]="notification" [paused]="true" size="md">
 </rtk-notification>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
index 7d3957e28575b5d..29874314310420f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-notifications component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -33,9 +34,5 @@ A component which handles notifications.
 
 ```html
 <!-- component.html -->
-<rtk-notifications
- [meeting]="meeting"
- size="md">
-</rtk-notifications>
+<rtk-notifications [meeting]="meeting" size="md"> </rtk-notifications>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
index da6b60ff9959d29..f7b0a744c973685 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-overlay-modal component (Angular Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,8 +30,5 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-overlay-modal
- [meeting]="meeting">
-</rtk-overlay-modal>
+<rtk-overlay-modal [meeting]="meeting"> </rtk-overlay-modal>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
index a37ab406bfe13c8..3a22d1b7e3c7e6a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-paginated-list component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-paginated-list
- [autoScroll]="true"
- [createNodes]="[]"
- emptyListLabel="example">
+	[autoScroll]="true"
+	[createNodes]="[]"
+	emptyListLabel="example"
+>
 </rtk-paginated-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
index a77302d526005b6..dc709547d180829 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participant-count component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-participant-count
- [meeting]="meeting"
- size="md">
-</rtk-participant-count>
+<rtk-participant-count [meeting]="meeting" size="md"> </rtk-participant-count>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
index fbdb48390bc0073..354d7029075e454 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-participant-setup component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -33,14 +34,14 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participant-setup
- [isPreview]="true"
- [nameTagPosition]="| 'bottom-left'
+	[isPreview]="true"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
     | 'top-center'"
- [participant]="participant">
+	[participant]="participant"
+>
 </rtk-participant-setup>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
index a87d31044667f2c..e4417402b7a4053 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-participant-tile component (Angular Library)
 products:
   - realtime
 ---
+
 A component which plays a participants video and allows for placement
- of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -37,14 +38,14 @@ A component which plays a participants video and allows for placement
 ```html
 <!-- component.html -->
 <rtk-participant-tile
- [isPreview]="true"
- [meeting]="meeting"
- [nameTagPosition]="| 'bottom-left'
+	[isPreview]="true"
+	[meeting]="meeting"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'">
+    | 'top-center'"
+>
 </rtk-participant-tile>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
index 1dda330a33b1b70..2cb75bb1541d4dc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-participant component (Angular Library)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A participant entry component used inside `rtk-participants` which shows data li
 ```html
 <!-- component.html -->
 <rtk-participant
- [meeting]="meeting"
- [participant]="participant"
- [view]="participantviewmode">
+	[meeting]="meeting"
+	[participant]="participant"
+	[view]="participantviewmode"
+>
 </rtk-participant>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
index 8d1dd8043548405..f35effb4020a5a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-audio component (Angular Library
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
@@ -30,8 +31,8 @@ A component which plays all the audio from participants and screenshares.
 ```html
 <!-- component.html -->
 <rtk-participants-audio
- [meeting]="meeting"
- [preloadedAudioElem]="htmlaudioelement">
+	[meeting]="meeting"
+	[preloadedAudioElem]="htmlaudioelement"
+>
 </rtk-participants-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
index 805eb1630f5565d..a0ad0b85a8677ae 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-participants-stage-list component (Angular Li
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
@@ -36,9 +37,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-participants-stage-list
- [hideHeader]="true"
- [meeting]="meeting"
- search="example">
+	[hideHeader]="true"
+	[meeting]="meeting"
+	search="example"
+>
 </rtk-participants-stage-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
index 0963dbb1699ef78..883999ff9c3ed7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-stage-queue component (Angular L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-stage-queue
- [meeting]="meeting"
- size="md"
- [view]="participantsviewmode">
+	[meeting]="meeting"
+	size="md"
+	[view]="participantsviewmode"
+>
 </rtk-participants-stage-queue>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
index dea0f244da4a0d5..bb5751a926de3b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
@@ -5,22 +5,27 @@ description: API reference for rtk-participants-toggle component (Angular Librar
 products:
   - realtime
 ---
+
 A button which toggles visibility of participants.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'participants' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "participants";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -35,10 +40,6 @@ A button which toggles visibility of participants.
 
 ```html
 <!-- component.html -->
-<rtk-participants-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-participants-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-participants-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
index 4ae0ae15cc28d5d..db2b020c8b88ab8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-participants-viewer-list component (Angular L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-viewer-list
- [hideHeader]="true"
- [meeting]="meeting"
- search="example">
+	[hideHeader]="true"
+	[meeting]="meeting"
+	search="example"
+>
 </rtk-participants-viewer-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
index 073a3e467d62514..f31d8a204b73fd3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-waiting-list component (Angular
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-waiting-list
- [meeting]="meeting"
- size="md"
- [view]="participantsviewmode">
+	[meeting]="meeting"
+	size="md"
+	[view]="participantsviewmode"
+>
 </rtk-participants-waiting-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
index f1984d1798d8879..b771206de02ce49 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-participants component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
@@ -34,9 +35,9 @@ A component which lists all participants, with ability to
 ```html
 <!-- component.html -->
 <rtk-participants
- [defaultParticipantsTabId]="participantstabid"
- [meeting]="meeting"
- size="md">
+	[defaultParticipantsTabId]="participantstabid"
+	[meeting]="meeting"
+	size="md"
+>
 </rtk-participants>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
index dec4a8e63bdaed2..683752123d4ac43 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-permissions-message component (Angular Librar
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,8 +31,5 @@ A component which shows permission related troubleshooting
 
 ```html
 <!-- component.html -->
-<rtk-permissions-message
- [meeting]="meeting">
-</rtk-permissions-message>
+<rtk-permissions-message [meeting]="meeting"> </rtk-permissions-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
index 94aad79b50a76a9..930b8fea7a6f96a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-pinned-message-selector component (Angular Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,8 +27,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pinned-message-selector
- [meeting]="meeting">
-</rtk-pinned-message-selector>
+<rtk-pinned-message-selector [meeting]="meeting"> </rtk-pinned-message-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
index ff56f4f7c8fc58c..3b85d1e48dc9a96 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-pip-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
@@ -30,10 +31,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pip-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-pip-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-pip-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
index 2adc29e0fe4d37f..8bc1fdc55db3407 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-plugin-main component (Angular Library)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which loads a plugin.
 
 ```html
 <!-- component.html -->
-<rtk-plugin-main
- [meeting]="meeting"
- [plugin]="rtkplugin">
-</rtk-plugin-main>
+<rtk-plugin-main [meeting]="meeting" [plugin]="rtkplugin"> </rtk-plugin-main>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
index 1e55dfd168ff802..78da2d41fbb440d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
@@ -5,22 +5,27 @@ description: API reference for rtk-plugins-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of plugins.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'plugins' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "plugins";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -35,10 +40,6 @@ A button which toggles visibility of plugins.
 
 ```html
 <!-- component.html -->
-<rtk-plugins-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-plugins-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-plugins-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
index ef10daccef93a00..916242388b0671a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-plugins component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A component which lists all available plugins from their preset,
 
 ```html
 <!-- component.html -->
-<rtk-plugins
- [meeting]="meeting"
- size="md">
-</rtk-plugins>
+<rtk-plugins [meeting]="meeting" size="md"> </rtk-plugins>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
index ed3e4b10df95868..92e52060d4aa885 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-poll-form component (Angular Library)
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,9 +28,5 @@ A component that lets you create a poll.
 
 ```html
 <!-- component.html -->
-<rtk-poll-form
- [iconPack]="defaultIconPack"
- [t]="rtki18n">
-</rtk-poll-form>
+<rtk-poll-form [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-poll-form>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
index 9c50bc3106f4e74..ef928546a835336 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-poll component (Angular Library)
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A poll component.
 
 ```html
 <!-- component.html -->
-<rtk-poll
- [permissions]="rtkpermissionspreset"
- [poll]="poll"
- self="example">
+<rtk-poll [permissions]="rtkpermissionspreset" [poll]="poll" self="example">
 </rtk-poll>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
index 8ee05f66d6d0c1e..4bc3fdff2d81dca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
@@ -5,23 +5,28 @@ description: API reference for rtk-polls-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of polls.
- You need to pass the `meeting` object to it to see the unread polls count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'polls' }
- ```
+You need to pass the `meeting` object to it to see the unread polls count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "polls";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -36,10 +41,6 @@ A button which toggles visibility of polls.
 
 ```html
 <!-- component.html -->
-<rtk-polls-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-polls-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-polls-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
index 0ccd3069c42b635..32b89fad2be1ffb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-polls component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A component which lists all available plugins a user can access with
 
 ```html
 <!-- component.html -->
-<rtk-polls
- [meeting]="meeting"
- size="md">
-</rtk-polls>
+<rtk-polls [meeting]="meeting" size="md"> </rtk-polls>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
index ad5090fddeb9402..51f3ba8000a0d15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-recording-indicator component (Angular Librar
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -30,9 +31,6 @@ A component which indicates the recording status of a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-indicator
- [meeting]="meeting"
- size="md">
+<rtk-recording-indicator [meeting]="meeting" size="md">
 </rtk-recording-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
index 5bc2e14496eecf7..47452de08e7ec1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-recording-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A button which toggles recording state of a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-toggle
- [disabled]="true"
- [meeting]="meeting"
- size="md">
+<rtk-recording-toggle [disabled]="true" [meeting]="meeting" size="md">
 </rtk-recording-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
index dec1ea51ccfddcc..00b6c6adc2aabc0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-screen-share-toggle component (Angular Librar
 products:
   - realtime
 ---
+
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -31,10 +32,6 @@ A button which toggles your screenshare.
 
 ```html
 <!-- component.html -->
-<rtk-screen-share-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-screen-share-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-screen-share-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
index f678a4456bcdc0a..ab7da66afebf434 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-screenshare-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which plays a participant's screenshared video.
- It also allows for placement of other components similar to `rtk-participant-tile`.
- This component will not render anything if the participant hasn't start screensharing.
+It also allows for placement of other components similar to `rtk-participant-tile`.
+This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property               | Type                                                                                                                     | Required | Default           | Description             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
+| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
+| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
+| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
+| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
+| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
+| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
+| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
+| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
 
 ## Usage Examples
 
@@ -36,14 +37,14 @@ A component which plays a participant's screenshared video.
 ```html
 <!-- component.html -->
 <rtk-screenshare-view
- [hideFullScreenButton]="true"
- [meeting]="meeting"
- [nameTagPosition]="| 'bottom-left'
+	[hideFullScreenButton]="true"
+	[meeting]="meeting"
+	[nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'">
+    | 'top-center'"
+>
 </rtk-screenshare-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
index 5818d8214fc8651..066d024c27fab77 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-audio component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -38,9 +40,5 @@ A component which lets to manage your audio devices and audio preferences.
 
 ```html
 <!-- component.html -->
-<rtk-settings-audio
- [meeting]="meeting"
- size="md">
-</rtk-settings-audio>
+<rtk-settings-audio [meeting]="meeting" size="md"> </rtk-settings-audio>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
index 56af8d465416a8d..d003ef750b8f9f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
@@ -5,21 +5,25 @@ description: API reference for rtk-settings-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of settings module.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSettings: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSettings: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description   |
+| ---------- | ------------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`              | ✅       | -                 | Size          |
+| `states`   | `States`            | ✅       | -                 | States object |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
 
 ## Usage Examples
 
@@ -34,9 +38,5 @@ A button which toggles visibility of settings module.
 
 ```html
 <!-- component.html -->
-<rtk-settings-toggle
- size="md"
- variant="button">
-</rtk-settings-toggle>
+<rtk-settings-toggle size="md" variant="button"> </rtk-settings-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
index 19b1a2ff5f132a7..381c51a0e2cf855 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-video component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -38,9 +40,5 @@ A component which lets to manage your camera devices and your video preferences.
 
 ```html
 <!-- component.html -->
-<rtk-settings-video
- [meeting]="meeting"
- size="md">
-</rtk-settings-video>
+<rtk-settings-video [meeting]="meeting" size="md"> </rtk-settings-video>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
index 339be6009cf2424..9789b422d1f2837 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-settings component (Angular Library)
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -31,9 +32,5 @@ A settings component to see and change your audio/video devices
 
 ```html
 <!-- component.html -->
-<rtk-settings
- [meeting]="meeting"
- size="md">
-</rtk-settings>
+<rtk-settings [meeting]="meeting" size="md"> </rtk-settings>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
index d142bf62459ec14..1406ce5ff38d369 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-setup-screen component (Angular Library)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -32,9 +33,5 @@ A screen shown before joining the meeting, where you can edit your display name,
 
 ```html
 <!-- component.html -->
-<rtk-setup-screen
- [meeting]="meeting"
- size="md">
-</rtk-setup-screen>
+<rtk-setup-screen [meeting]="meeting" size="md"> </rtk-setup-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
index 8126edad79c871c..94db2e01d33f007 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-sidebar-ui component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
@@ -32,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-sidebar-ui
- currentTab="example"
- [focusCloseButton]="true"
- [hideCloseAction]="true">
+	currentTab="example"
+	[focusCloseButton]="true"
+	[hideCloseAction]="true"
+>
 </rtk-sidebar-ui>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
index bfd8e5e11b5177c..71e210674395a9d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-sidebar component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
@@ -36,9 +37,9 @@ A component which handles the sidebar and
 ```html
 <!-- component.html -->
 <rtk-sidebar
- [defaultSection]="rtksidebarsection"
- [enabledSections]="[]"
- [meeting]="meeting">
+	[defaultSection]="rtksidebarsection"
+	[enabledSections]="[]"
+	[meeting]="meeting"
+>
 </rtk-sidebar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
index ea88ffe55f9f48e..bf202dd85e47787 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-simple-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -34,10 +35,6 @@ A grid component which renders only the participants in a simple grid.
 
 ```html
 <!-- component.html -->
-<rtk-simple-grid
- aspectRatio="example"
- gap="42"
- [meeting]="meeting">
+<rtk-simple-grid aspectRatio="example" gap="42" [meeting]="meeting">
 </rtk-simple-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
index c19b21a731b3bcd..16628f891f7fa01 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
@@ -5,26 +5,28 @@ description: API reference for rtk-speaker-selector component (Angular Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -40,9 +42,9 @@ A component which lets to manage your audio devices and audio preferences.
 ```html
 <!-- component.html -->
 <rtk-speaker-selector
- [meeting]="meeting"
- size="md"
- [variant]="'full' | 'inline'">
+	[meeting]="meeting"
+	size="md"
+	[variant]="'full' | 'inline'"
+>
 </rtk-speaker-selector>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
index 915451bf50a7527..47ea91cffa10d78 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spinner component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ A component which shows an animating spinner.
 
 ```html
 <!-- component.html -->
-<rtk-spinner
- size="md">
-</rtk-spinner>
+<rtk-spinner size="md"> </rtk-spinner>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
index f88cc7f531eac2c..c3e3916f6cc12bb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
@@ -5,27 +5,29 @@ description: API reference for rtk-spotlight-grid component (Angular Library)
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -40,10 +42,6 @@ A grid component that renders two lists of participants: `pinnedParticipants` an
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-grid
- aspectRatio="example"
- gap="42"
- gridSize="md">
+<rtk-spotlight-grid aspectRatio="example" gap="42" gridSize="md">
 </rtk-spotlight-grid>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
index 60b6debe69e9082..ddb740d3af6b233 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spotlight-indicator component (Angular Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-indicator
- [meeting]="meeting"
- size="md">
+<rtk-spotlight-indicator [meeting]="meeting" size="md">
 </rtk-spotlight-indicator>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
index 8e92fdc9598d17a..27bcf1579495dbe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-stage-toggle component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `states`   | `States1`           | ✅       | -                 | States         |
+| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -29,10 +30,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-stage-toggle
- [meeting]="meeting"
- size="md"
- variant="button">
+<rtk-stage-toggle [meeting]="meeting" size="md" variant="button">
 </rtk-stage-toggle>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
index ccffa6559353763..0b94a4fd1566c92 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-stage component (Angular Library)
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -28,9 +29,5 @@ A component used as a stage that commonly houses
 
 ```html
 <!-- component.html -->
-<rtk-stage
- [iconPack]="defaultIconPack"
- [t]="rtki18n">
-</rtk-stage>
+<rtk-stage [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-stage>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
index f8993d18641c090..75c781fb19e4ce2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-switch component (Angular Library)
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
@@ -30,10 +31,5 @@ A switch component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-switch
- [checked]="true"
- [disabled]="true"
- [readonly]="true">
-</rtk-switch>
+<rtk-switch [checked]="true" [disabled]="true" [readonly]="true"> </rtk-switch>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
index 1c8cf7cad9f42ff..339bfe235fceedb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-tab-bar component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-tab-bar
- [activeTab]="tab"
- [layout]="gridlayout1"
- [meeting]="meeting">
+<rtk-tab-bar [activeTab]="tab" [layout]="gridlayout1" [meeting]="meeting">
 </rtk-tab-bar>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
index cba219399b00342..b2a412cd7210059 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-text-composer-view component (Angular Library
 products:
   - realtime
 ---
+
 A component which renders a text composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `placeholder` | `string` | ✅ | - | Placeholder text |
-| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
-| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `value` | `string` | ✅ | - | Default value for text input |
+| Property            | Type                              | Required | Default           | Description                                   |
+| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
+| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
+| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
+| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
+| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
+| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
+| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
+| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
+| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
+| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
 
 ## Usage Examples
 
@@ -35,9 +36,9 @@ A component which renders a text composer
 ```html
 <!-- component.html -->
 <rtk-text-composer-view
- [disabled]="true"
- [keyDownHandler]="(e: keyboardevent)"
- maxLength="42">
+	[disabled]="true"
+	[keyDownHandler]="(e: keyboardevent)"
+	maxLength="42"
+>
 </rtk-text-composer-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
index 1ccf18977b7aa7d..45ba2ef88c72b20 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-text-message-view component (Angular Library)
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
@@ -27,9 +28,6 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message-view
- [isMarkdown]="true"
- text="example">
+<rtk-text-message-view [isMarkdown]="true" text="example">
 </rtk-text-message-view>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
index 5060b6599375a57..230e3211e03b994 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-text-message component (Angular Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -32,10 +33,6 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-text-message
- [isContinued]="true"
- [message]="textmessage"
- [now]="date">
+<rtk-text-message [isContinued]="true" [message]="textmessage" [now]="date">
 </rtk-text-message>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
index 4e6f62691aef692..371a6eec0e5bcf2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-tooltip component (Angular Library)
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
@@ -33,10 +34,5 @@ Tooltip component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-tooltip
- delay="42"
- [disabled]="true"
- [kind]="tooltipkind">
-</rtk-tooltip>
+<rtk-tooltip delay="42" [disabled]="true" [kind]="tooltipkind"> </rtk-tooltip>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
index 4f6fe2ff039b589..570133cd5d8d464 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-transcript component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows a transcript.
 
 ```html
 <!-- component.html -->
-<rtk-transcript
- [t]="rtki18n"
- transcript="example">
-</rtk-transcript>
+<rtk-transcript [t]="rtki18n" transcript="example"> </rtk-transcript>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
index 4e6c1192fcba044..578013baff0705a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-transcripts component (Angular Library)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,8 +32,5 @@ A component which handles transcripts.
 
 ```html
 <!-- component.html -->
-<rtk-transcripts
- [meeting]="meeting">
-</rtk-transcripts>
+<rtk-transcripts [meeting]="meeting"> </rtk-transcripts>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
index 0bfe8c1b9050c14..8602181f2eb682c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ui-provider component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
@@ -31,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-ui-provider
- [config]="defaultUiConfig"
- [mode]="meeting"
- [showSetupScreen]="true">
+	[config]="defaultUiConfig"
+	[mode]="meeting"
+	[showSetupScreen]="true"
+>
 </rtk-ui-provider>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
index bb61879c99d4f26..f64a1ff20e41f82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-viewer-count component (Angular Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
@@ -29,9 +30,5 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-viewer-count
- [meeting]="meeting"
- variant="primary">
-</rtk-viewer-count>
+<rtk-viewer-count [meeting]="meeting" variant="primary"> </rtk-viewer-count>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
index 63be1a12b781fd2..040843c9c08f95e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-virtualized-participant-list component (Angul
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
@@ -29,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-virtualized-participant-list
- bufferedItemsCount="42"
- [emptyListElement]="htmlelement"
- itemHeight="42">
+	bufferedItemsCount="42"
+	[emptyListElement]="htmlelement"
+	itemHeight="42"
+>
 </rtk-virtualized-participant-list>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
index 46061d522a85431..ed0bda90edc56eb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-waiting-screen component (Angular Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -27,8 +28,5 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-waiting-screen
- [meeting]="meeting">
-</rtk-waiting-screen>
+<rtk-waiting-screen [meeting]="meeting"> </rtk-waiting-screen>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
index 7f6ea96d5eaefa0..8ef6d5dcdfadf48 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
index e270c77642b2c4a..4a58db7ec3bb580 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-ai-transcriptions component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
@@ -24,16 +25,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai-transcriptions>
-</rtk-ai-transcriptions>
+<rtk-ai-transcriptions> </rtk-ai-transcriptions>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ai-transcriptions");
+	const el = document.querySelector("rtk-ai-transcriptions");
 
-  el.initialTranscriptions= [];
-  el.meeting= meeting
+	el.initialTranscriptions = [];
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
index 970e391d75c32bc..a55ac07cacbbec6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ai component (Web Components (HTML) Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai
- size="md">
-</rtk-ai>
+<rtk-ai size="md"> </rtk-ai>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ai");
+	const el = document.querySelector("rtk-ai");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
index 2d9130e9d8e4121..ac1e4eef81b052e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-grid>
-</rtk-audio-grid>
+<rtk-audio-grid> </rtk-audio-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-grid");
+	const el = document.querySelector("rtk-audio-grid");
 
-  el.config= defaultUiConfig
-  el.hideSelf= true;
-  el.meeting= meeting
+	el.config = defaultUiConfig;
+	el.hideSelf = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
index 8959b0dde236c5c..6b7d96a935dd7f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-audio-tile component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-tile>
-</rtk-audio-tile>
+<rtk-audio-tile> </rtk-audio-tile>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-tile");
+	const el = document.querySelector("rtk-audio-tile");
 
-  el.config= defaultUiConfig
-  el.meeting= meeting
-  el.participant= participant
+	el.config = defaultUiConfig;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
index 813eab6b421006a..8ff29c76cd061be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-audio-visualizer component (Web Components (H
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
@@ -31,17 +32,15 @@ An audio visualizer component which visualizes a participants audio.
 ### With Properties
 
 ```html
-<rtk-audio-visualizer>
-</rtk-audio-visualizer>
+<rtk-audio-visualizer> </rtk-audio-visualizer>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-audio-visualizer");
+	const el = document.querySelector("rtk-audio-visualizer");
 
-  el.hideMuted= true;
-  el.isScreenShare= true;
-  el.participant= participant
+	el.hideMuted = true;
+	el.isScreenShare = true;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
index 7f8b81f1043b96d..d3d2acf95812bd9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-avatar component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
@@ -28,18 +29,13 @@ Avatar component which renders a participant's image or their initials.
 ### With Properties
 
 ```html
-<rtk-avatar
- participant="example"
- size="md"
- variant="circular">
-</rtk-avatar>
+<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-avatar");
+	const el = document.querySelector("rtk-avatar");
 
-  el.participant= {};
+	el.participant = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
index 0ffde64de310896..08565892ad5d286 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-breakout-room-manager component (Web Componen
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
@@ -31,17 +32,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-room-manager>
-</rtk-breakout-room-manager>
+<rtk-breakout-room-manager> </rtk-breakout-room-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-room-manager");
+	const el = document.querySelector("rtk-breakout-room-manager");
 
-  el.allowDelete= true;
-  el.assigningParticipants= true;
-  el.defaultExpanded= true;
+	el.allowDelete = true;
+	el.assigningParticipants = true;
+	el.defaultExpanded = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
index a27e85c3f7202e5..90bf0a7a6599970 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-breakout-room-participants component (Web Com
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -30,18 +31,18 @@ A component which lists all participants, with ability to
 
 ```html
 <rtk-breakout-room-participants
- participantIds="example"
- selectedParticipantIds="example">
+	participantIds="example"
+	selectedParticipantIds="example"
+>
 </rtk-breakout-room-participants>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-room-participants");
+	const el = document.querySelector("rtk-breakout-room-participants");
 
-  el.meeting= meeting
-  el.participantIds= [];
-  el.selectedParticipantIds= [];
+	el.meeting = meeting;
+	el.participantIds = [];
+	el.selectedParticipantIds = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
index 4d3fe5430be46fe..8186a41e5b921c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-breakout-rooms-manager component (Web Compone
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-manager>
-</rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager> </rtk-breakout-rooms-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-rooms-manager");
+	const el = document.querySelector("rtk-breakout-rooms-manager");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
index 12e8adafccffa1d..330651ce2800cee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-breakout-rooms-toggle component (Web Componen
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
@@ -30,17 +31,14 @@ A button which toggles visibility of breakout rooms.
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-toggle
- size="md">
-</rtk-breakout-rooms-toggle>
+<rtk-breakout-rooms-toggle size="md"> </rtk-breakout-rooms-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-breakout-rooms-toggle");
+	const el = document.querySelector("rtk-breakout-rooms-toggle");
 
-  el.iconPack= defaultIconPack
-  el.meeting= meeting
+	el.iconPack = defaultIconPack;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
index c701b24f24c37b6..90a5bf9760e290c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-broadcast-message-modal component (Web Compon
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-broadcast-message-modal>
-</rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal> </rtk-broadcast-message-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-broadcast-message-modal");
+	const el = document.querySelector("rtk-broadcast-message-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
index 190ce0bd634cebf..2257bd8dc185484 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-button component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
@@ -29,16 +30,14 @@ A button that follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-button>
-</rtk-button>
+<rtk-button> </rtk-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-button");
+	const el = document.querySelector("rtk-button");
 
-  el.disabled= true;
-  el.reverse= true;
+	el.disabled = true;
+	el.reverse = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
index 839aea969dea5f1..31e3f2482ecb54c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-camera-selector component (Web Components (HT
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-camera-selector
- size="md">
-</rtk-camera-selector>
+<rtk-camera-selector size="md"> </rtk-camera-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-camera-selector");
+	const el = document.querySelector("rtk-camera-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
index 6062945d8cda350..7726ca148fdf888 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat-composer-ui component (Web Components (H
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-composer-ui
- size="md">
-</rtk-chat-composer-ui>
+<rtk-chat-composer-ui size="md"> </rtk-chat-composer-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-composer-ui");
+	const el = document.querySelector("rtk-chat-composer-ui");
 
-  el.canSendFiles= true;
-  el.canSendTextMessage= true;
+	el.canSendFiles = true;
+	el.canSendTextMessage = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
index 4f0b587d7e57cda..6f24d73d4050be8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-chat-composer-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
@@ -34,17 +35,15 @@ A component which renders a chat composer
 ### With Properties
 
 ```html
-<rtk-chat-composer-view
- inputTextPlaceholder="example">
+<rtk-chat-composer-view inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-composer-view");
+	const el = document.querySelector("rtk-chat-composer-view");
 
-  el.canSendFiles= true;
-  el.canSendTextMessage= true;
+	el.canSendFiles = true;
+	el.canSendTextMessage = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
index 00331fb11033be4..d53fa58a0768116 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
@@ -5,9 +5,10 @@ description: API reference for rtk-chat-header component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
@@ -16,4 +17,3 @@ products:
 ```html
 <rtk-chat-header></rtk-chat-header>
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
index b49edd649f06ee1..67158b1da131121 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
@@ -5,29 +5,30 @@ description: API reference for rtk-chat-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
@@ -40,17 +41,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-message>
-</rtk-chat-message>
+<rtk-chat-message> </rtk-chat-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-message");
+	const el = document.querySelector("rtk-chat-message");
 
-  el.alignRight= true;
-  el.canDelete= true;
-  el.canEdit= true;
+	el.alignRight = true;
+	el.canDelete = true;
+	el.canEdit = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
index 1a1f8d1bb2a313f..9b334cb50256afd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-chat-messages-ui-paginated component (Web Com
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui-paginated
- size="md">
-</rtk-chat-messages-ui-paginated>
+<rtk-chat-messages-ui-paginated size="md"> </rtk-chat-messages-ui-paginated>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-messages-ui-paginated");
+	const el = document.querySelector("rtk-chat-messages-ui-paginated");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
index 4315ce89d3ea880..91b79ea94878ffb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-chat-messages-ui component (Web Components (H
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
@@ -30,17 +31,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui
- selectedGroup="example">
-</rtk-chat-messages-ui>
+<rtk-chat-messages-ui selectedGroup="example"> </rtk-chat-messages-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-messages-ui");
+	const el = document.querySelector("rtk-chat-messages-ui");
 
-  el.canPinMessages= true;
-  el.messages= [];
+	el.canPinMessages = true;
+	el.messages = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
index 12510bac6bda05a..fd7ba927fca8daa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-search-results component (Web Components
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,17 +29,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-search-results
- channelId="example"
- query="example">
+<rtk-chat-search-results channelId="example" query="example">
 </rtk-chat-search-results>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-search-results");
+	const el = document.querySelector("rtk-chat-search-results");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
index 88fd33ff9a1e098..713fb73bd989f34 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-chat-selector-ui component (Web Components (H
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
@@ -27,17 +28,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector-ui
- selectedGroupId="example"
- selfUserId="example">
+<rtk-chat-selector-ui selectedGroupId="example" selfUserId="example">
 </rtk-chat-selector-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-selector-ui");
+	const el = document.querySelector("rtk-chat-selector-ui");
 
-  el.groups= [];
+	el.groups = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
index 35043d7c0f2796e..f41ed748ffb2bcf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-chat-selector component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector
- size="md">
-</rtk-chat-selector>
+<rtk-chat-selector size="md"> </rtk-chat-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat-selector");
+	const el = document.querySelector("rtk-chat-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
index f1f46fa4254dfc0..d296e1f85861da7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-chat component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 ### With Properties
 
 ```html
-<rtk-chat
- size="md">
-</rtk-chat>
+<rtk-chat size="md"> </rtk-chat>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-chat");
+	const el = document.querySelector("rtk-chat");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
index f4befa6dbda7af6..f29acbd05520f7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-clock component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ Shows the time elapsed in a meeting.
 ### With Properties
 
 ```html
-<rtk-clock
- size="md">
-</rtk-clock>
+<rtk-clock size="md"> </rtk-clock>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-clock");
+	const el = document.querySelector("rtk-clock");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
index 59a36b5e16679da..54bd7f2399df487 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-confirmation-modal component (Web Components
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-confirmation-modal>
-</rtk-confirmation-modal>
+<rtk-confirmation-modal> </rtk-confirmation-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-confirmation-modal");
+	const el = document.querySelector("rtk-confirmation-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
index 59c9be5f52f7987..b63c726196d6d84 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-controlbar-button component (Web Components (
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A skeleton component used for composing custom controlbar buttons.
 ### With Properties
 
 ```html
-<rtk-controlbar-button
- icon="example">
-</rtk-controlbar-button>
+<rtk-controlbar-button icon="example"> </rtk-controlbar-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-controlbar-button");
+	const el = document.querySelector("rtk-controlbar-button");
 
-  el.brandIcon= true;
-  el.disabled= true;
+	el.brandIcon = true;
+	el.disabled = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
index c303a5102cb22ac..326a72bac0165d4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-controlbar component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ Controlbar component provides you with various designs as variants.
 ### With Properties
 
 ```html
-<rtk-controlbar
- size="md">
-</rtk-controlbar>
+<rtk-controlbar size="md"> </rtk-controlbar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-controlbar");
+	const el = document.querySelector("rtk-controlbar");
 
-  el.disableRender= true;
-  el.meeting= meeting
+	el.disableRender = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
index 59bbbbf35837964..762c4d9d8d1cfc9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-counter component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
@@ -28,17 +29,14 @@ A number picker with increment and decrement buttons.
 ### With Properties
 
 ```html
-<rtk-counter
- size="md">
-</rtk-counter>
+<rtk-counter size="md"> </rtk-counter>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-counter");
+	const el = document.querySelector("rtk-counter");
 
-  el.minValue= 42;
-  el.value= 42;
+	el.minValue = 42;
+	el.value = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
index 8733f92d520e775..22f1b026cd01b82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-audio component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-audio
- size="md">
-</rtk-debugger-audio>
+<rtk-debugger-audio size="md"> </rtk-debugger-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-audio");
+	const el = document.querySelector("rtk-debugger-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
index f7f80fd287b5ef1..9435b3bec0238c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-screenshare component (Web Component
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-screenshare
- size="md">
-</rtk-debugger-screenshare>
+<rtk-debugger-screenshare size="md"> </rtk-debugger-screenshare>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-screenshare");
+	const el = document.querySelector("rtk-debugger-screenshare");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
index a7cc1725cc28364..a80a0f3c3252295 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-system component (Web Components (HT
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-system
- size="md">
-</rtk-debugger-system>
+<rtk-debugger-system size="md"> </rtk-debugger-system>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-system");
+	const el = document.querySelector("rtk-debugger-system");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
index 84a90649d07675a..9deac224fdf1a02 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-debugger-video component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,16 +27,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-video
- size="md">
-</rtk-debugger-video>
+<rtk-debugger-video size="md"> </rtk-debugger-video>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger-video");
+	const el = document.querySelector("rtk-debugger-video");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
index a8141d499177b06..7d345ee443ecde8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-debugger component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A troubleshooting component to identify and fix any issues in the meeting.
 ### With Properties
 
 ```html
-<rtk-debugger
- size="md">
-</rtk-debugger>
+<rtk-debugger size="md"> </rtk-debugger>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-debugger");
+	const el = document.querySelector("rtk-debugger");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
index ba7f8b4cd15bf85..3709d9d501cd38e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
@@ -5,24 +5,26 @@ description: API reference for rtk-dialog-manager component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -35,16 +37,13 @@ A component which handles all dialog elements in a component such as:
 ### With Properties
 
 ```html
-<rtk-dialog-manager
- size="md">
-</rtk-dialog-manager>
+<rtk-dialog-manager size="md"> </rtk-dialog-manager>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-dialog-manager");
+	const el = document.querySelector("rtk-dialog-manager");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
index 170ade6492a1274..d361f6b14ccdb8b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-dialog component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
@@ -32,17 +33,15 @@ A dialog component.
 ### With Properties
 
 ```html
-<rtk-dialog>
-</rtk-dialog>
+<rtk-dialog> </rtk-dialog>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-dialog");
+	const el = document.querySelector("rtk-dialog");
 
-  el.disableEscapeKey= true;
-  el.hideCloseButton= true;
-  el.meeting= meeting
+	el.disableEscapeKey = true;
+	el.hideCloseButton = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
index f21db9738750267..7060d45d649d00a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-draft-attachment-view component (Web Componen
 products:
   - realtime
 ---
+
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property     | Type                                                 | Required | Default           | Description           |
+| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
+| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
+| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A component which renders the draft attachment to send
 ### With Properties
 
 ```html
-<rtk-draft-attachment-view>
-</rtk-draft-attachment-view>
+<rtk-draft-attachment-view> </rtk-draft-attachment-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-draft-attachment-view");
+	const el = document.querySelector("rtk-draft-attachment-view");
 
-  el.attachment= {};
+	el.attachment = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
index f67d8a0f096c864..be00c3a6e33ad46 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-emoji-picker-button component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
@@ -24,15 +25,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-emoji-picker-button>
-</rtk-emoji-picker-button>
+<rtk-emoji-picker-button> </rtk-emoji-picker-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-emoji-picker-button");
+	const el = document.querySelector("rtk-emoji-picker-button");
 
-  el.isActive= true;
+	el.isActive = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
index a0876babb985962..69aabd63c26f21f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-emoji-picker component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A very simple emoji picker component.
 ### With Properties
 
 ```html
-<rtk-emoji-picker>
-</rtk-emoji-picker>
+<rtk-emoji-picker> </rtk-emoji-picker>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-emoji-picker");
+	const el = document.querySelector("rtk-emoji-picker");
 
-  el.focusWhenOpened= true;
+	el.focusWhenOpened = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
index 6aa6297284ea709..e5388b1585fd982 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-ended-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A screen which shows a meeting has ended.
 ### With Properties
 
 ```html
-<rtk-ended-screen
- size="md">
-</rtk-ended-screen>
+<rtk-ended-screen size="md"> </rtk-ended-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ended-screen");
+	const el = document.querySelector("rtk-ended-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
index a9528f31a65a0cc..fdf7e9e77e382ba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-file-dropzone component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
@@ -24,14 +25,11 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-dropzone>
-</rtk-file-dropzone>
+<rtk-file-dropzone> </rtk-file-dropzone>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-dropzone");
-
+	const el = document.querySelector("rtk-file-dropzone");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
index 1764939b1ca0276..083396274de8c83 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-file-message-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
@@ -27,17 +28,13 @@ A component which renders a file message.
 ### With Properties
 
 ```html
-<rtk-file-message-view
- name="example"
- url="example">
-</rtk-file-message-view>
+<rtk-file-message-view name="example" url="example"> </rtk-file-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-message-view");
+	const el = document.querySelector("rtk-file-message-view");
 
-  el.size= 42;
+	el.size = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
index 811a6cce1a3b65e..936feef21b37fa9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-file-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-message>
-</rtk-file-message>
+<rtk-file-message> </rtk-file-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-message");
+	const el = document.querySelector("rtk-file-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
index 54b3d5dd21d7da8..851138e1627613b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-file-picker-button component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
@@ -26,17 +27,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-picker-button
- filter="example"
- label="example">
+<rtk-file-picker-button filter="example" label="example">
 </rtk-file-picker-button>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-file-picker-button");
+	const el = document.querySelector("rtk-file-picker-button");
 
-  el.icon= defaultIconPack
+	el.icon = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
index f3865d72720b943..d663d791207416c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-grid-pagination component (Web Components (HT
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A component which allows you to change current page and view mode
 ### With Properties
 
 ```html
-<rtk-grid-pagination
- size="md">
-</rtk-grid-pagination>
+<rtk-grid-pagination size="md"> </rtk-grid-pagination>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-grid-pagination");
+	const el = document.querySelector("rtk-grid-pagination");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
index cf79955eff09681..31eef43afae392f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-grid component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
@@ -34,17 +35,13 @@ The main grid component which abstracts all the grid handling logic and renders
 ### With Properties
 
 ```html
-<rtk-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-grid>
+<rtk-grid aspectRatio="example" gridSize="md"> </rtk-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-grid");
+	const el = document.querySelector("rtk-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
index 1fb6ec7f5c5a1b6..a89c57e5b374cc4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-header component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ A component that houses all the header components.
 ### With Properties
 
 ```html
-<rtk-header
- size="md">
-</rtk-header>
+<rtk-header size="md"> </rtk-header>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-header");
+	const el = document.querySelector("rtk-header");
 
-  el.disableRender= true;
-  el.meeting= meeting
+	el.disableRender = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
index 581f5e42555059a..225e4d075df1fad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-icon component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
@@ -26,17 +27,11 @@ An icon component which accepts an svg string and renders it.
 ### With Properties
 
 ```html
-<rtk-icon
- icon="example"
- size="md"
- variant="primary">
-</rtk-icon>
+<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-icon");
-
+	const el = document.querySelector("rtk-icon");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
index a2e6c178b6c1e82..54a72fdf6f17b5b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-idle-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A screen that handles the idle state,
 ### With Properties
 
 ```html
-<rtk-idle-screen>
-</rtk-idle-screen>
+<rtk-idle-screen> </rtk-idle-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-idle-screen");
+	const el = document.querySelector("rtk-idle-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
index 707341e71c859f2..4faebe0ab376143 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-image-message-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
@@ -26,15 +27,11 @@ A component which renders an image message.
 ### With Properties
 
 ```html
-<rtk-image-message-view
- url="example">
-</rtk-image-message-view>
+<rtk-image-message-view url="example"> </rtk-image-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-message-view");
-
+	const el = document.querySelector("rtk-image-message-view");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
index 76c23bbf2dfca99..cb324944fd49d2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-image-message component (Web Components (HTML
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-image-message>
-</rtk-image-message>
+<rtk-image-message> </rtk-image-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-message");
+	const el = document.querySelector("rtk-image-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
index da7064e9253ab13..b7e74691417c0f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-image-viewer component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -27,15 +28,11 @@ A component which shows an image sent via chat.
 ### With Properties
 
 ```html
-<rtk-image-viewer
- size="md">
-</rtk-image-viewer>
+<rtk-image-viewer size="md"> </rtk-image-viewer>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-image-viewer");
-
+	const el = document.querySelector("rtk-image-viewer");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
index 7950fc7f2bc101a..f638b70c50e83d4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
@@ -5,11 +5,12 @@ description: API reference for rtk-information-tooltip component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
@@ -22,15 +23,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-information-tooltip>
-</rtk-information-tooltip>
+<rtk-information-tooltip> </rtk-information-tooltip>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-information-tooltip");
+	const el = document.querySelector("rtk-information-tooltip");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
index 36d7fcfd41612fa..7cbac34216b6b9a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-join-stage component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-join-stage
- size="md">
-</rtk-join-stage>
+<rtk-join-stage size="md"> </rtk-join-stage>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-join-stage");
+	const el = document.querySelector("rtk-join-stage");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
index 60d83d6896b419b..7953645ed11d440 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-leave-meeting component (Web Components (HTML
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A component which allows you to leave a meeting or
 ### With Properties
 
 ```html
-<rtk-leave-meeting>
-</rtk-leave-meeting>
+<rtk-leave-meeting> </rtk-leave-meeting>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-leave-meeting");
+	const el = document.querySelector("rtk-leave-meeting");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
index 67707911b550145..7089f2c65e4c3b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-indicator component (Web Component
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-indicator
- size="md">
-</rtk-livestream-indicator>
+<rtk-livestream-indicator size="md"> </rtk-livestream-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-livestream-indicator");
+	const el = document.querySelector("rtk-livestream-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
index 5e6da815b9a6c32..4d35b373ccbafc2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-livestream-player component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-player
- size="md">
-</rtk-livestream-player>
+<rtk-livestream-player size="md"> </rtk-livestream-player>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-livestream-player");
+	const el = document.querySelector("rtk-livestream-player");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
index f6713bd26d22ab2..cb8ff8473cd8a3e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-logo component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 ### With Properties
 
 ```html
-<rtk-logo
- logoUrl="example">
-</rtk-logo>
+<rtk-logo logoUrl="example"> </rtk-logo>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-logo");
+	const el = document.querySelector("rtk-logo");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
index d1381ac73ca5828..811851e7e12e984 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
@@ -5,12 +5,13 @@ description: API reference for rtk-markdown-view component (Web Components (HTML
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
@@ -23,16 +24,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-markdown-view
- text="example">
-</rtk-markdown-view>
+<rtk-markdown-view text="example"> </rtk-markdown-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-markdown-view");
+	const el = document.querySelector("rtk-markdown-view");
 
-  el.maxLength= 42;
+	el.maxLength = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
index ba9885092147cbb..55697cb504158d1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-meeting-title component (Web Components (HTML
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ Displays the title of the meeting.
 ### With Properties
 
 ```html
-<rtk-meeting-title>
-</rtk-meeting-title>
+<rtk-meeting-title> </rtk-meeting-title>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-meeting-title");
+	const el = document.querySelector("rtk-meeting-title");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
index 0a6abda1bfb826a..753af9e783bf586 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
@@ -5,27 +5,28 @@ description: API reference for rtk-meeting component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
@@ -38,16 +39,14 @@ A single component which renders an entire meeting UI.
 ### With Properties
 
 ```html
-<rtk-meeting>
-</rtk-meeting>
+<rtk-meeting> </rtk-meeting>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-meeting");
+	const el = document.querySelector("rtk-meeting");
 
-  el.applyDesignSystem= true;
-  el.config= defaultUiConfig
+	el.applyDesignSystem = true;
+	el.config = defaultUiConfig;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
index 169675ff5a4498c..c9fd4b7ff50b042 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-menu-item component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,15 +28,11 @@ A menu item component.
 ### With Properties
 
 ```html
-<rtk-menu-item
- size="md">
-</rtk-menu-item>
+<rtk-menu-item size="md"> </rtk-menu-item>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu-item");
-
+	const el = document.querySelector("rtk-menu-item");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
index 88b9d8538638163..6735e67c1b647e8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-menu-list component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -26,14 +27,11 @@ A menu list component.
 ### With Properties
 
 ```html
-<rtk-menu-list>
-</rtk-menu-list>
+<rtk-menu-list> </rtk-menu-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu-list");
-
+	const el = document.querySelector("rtk-menu-list");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
index 12ad508b8b32180..bb093d6585896ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-menu component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A menu component.
 ### With Properties
 
 ```html
-<rtk-menu
- size="md">
-</rtk-menu>
+<rtk-menu size="md"> </rtk-menu>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-menu");
+	const el = document.querySelector("rtk-menu");
 
-  el.offset= 42;
+	el.offset = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
index cdb30bac0e60ed4..f409f90de250597 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-message-list-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders list of messages.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
-| `messages` | `Message[]` | ✅ | - | Messages to render |
-| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
-| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
+| Property            | Type                                | Required | Default           | Description                                                                   |
+| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
+| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
+| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
+| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
+| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
+| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
+| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
 
 ## Usage Examples
 
@@ -29,16 +30,14 @@ A component which renders list of messages.
 ### With Properties
 
 ```html
-<rtk-message-list-view>
-</rtk-message-list-view>
+<rtk-message-list-view> </rtk-message-list-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-message-list-view");
+	const el = document.querySelector("rtk-message-list-view");
 
-  el.estimateItemSize= 42;
-  el.messages= [];
+	el.estimateItemSize = 42;
+	el.messages = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
index 728e84fc9321401..09def76b8fce5db 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
@@ -5,24 +5,25 @@ description: API reference for rtk-message-view component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
@@ -35,17 +36,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-message-view
- authorName="example"
- avatarUrl="example">
-</rtk-message-view>
+<rtk-message-view authorName="example" avatarUrl="example"> </rtk-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-message-view");
+	const el = document.querySelector("rtk-message-view");
 
-  el.actions= [];
+	el.actions = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
index 1565dc06501cfad..0e2adb948d754a3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-microphone-selector component (Web Components
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-microphone-selector
- size="md">
-</rtk-microphone-selector>
+<rtk-microphone-selector size="md"> </rtk-microphone-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-microphone-selector");
+	const el = document.querySelector("rtk-microphone-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
index d399d66944cd6fc..79ad17a23ebacab 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
@@ -5,26 +5,27 @@ description: API reference for rtk-mixed-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -37,17 +38,13 @@ A grid component which handles screenshares, plugins and participants.
 ### With Properties
 
 ```html
-<rtk-mixed-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-mixed-grid>
+<rtk-mixed-grid aspectRatio="example" gridSize="md"> </rtk-mixed-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-mixed-grid");
+	const el = document.querySelector("rtk-mixed-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
index 43e569451c44e9b..83ee618b019e4c1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
@@ -5,20 +5,24 @@ description: API reference for rtk-more-toggle component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
@@ -31,15 +35,11 @@ A button which toggles visibility of a more menu.
 ### With Properties
 
 ```html
-<rtk-more-toggle
- size="md">
-</rtk-more-toggle>
+<rtk-more-toggle size="md"> </rtk-more-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-more-toggle");
-
+	const el = document.querySelector("rtk-more-toggle");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
index 8100fe45db00611..6bb1b8bdce29e58 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-mute-all-confirmation component (Web Componen
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-mute-all-confirmation>
-</rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation> </rtk-mute-all-confirmation>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-mute-all-confirmation");
+	const el = document.querySelector("rtk-mute-all-confirmation");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
index f6cee72609ed898..14082b5393b2820 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-name-tag component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
@@ -30,17 +31,15 @@ A component which shows a participant's name.
 ### With Properties
 
 ```html
-<rtk-name-tag>
-</rtk-name-tag>
+<rtk-name-tag> </rtk-name-tag>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-name-tag");
+	const el = document.querySelector("rtk-name-tag");
 
-  el.isScreenShare= true;
-  el.meeting= meeting
-  el.participant= participant
+	el.isScreenShare = true;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
index a87b7aea196b1a0..b5241b2075c51f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-network-indicator component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
@@ -26,17 +27,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-network-indicator>
-</rtk-network-indicator>
+<rtk-network-indicator> </rtk-network-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-network-indicator");
+	const el = document.querySelector("rtk-network-indicator");
 
-  el.isScreenShare= true;
-  el.meeting= meeting
-  el.participant= participant
+	el.isScreenShare = true;
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
index e175a377ba80f6e..4573caf03b498f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-notification component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A component which shows a notification.
 ### With Properties
 
 ```html
-<rtk-notification
- size="md">
-</rtk-notification>
+<rtk-notification size="md"> </rtk-notification>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-notification");
+	const el = document.querySelector("rtk-notification");
 
-  el.paused= true;
+	el.paused = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
index 1854740c5dd7087..c914a13e3c8be1a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-notifications component (Web Components (HTML
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -31,16 +32,13 @@ A component which handles notifications.
 ### With Properties
 
 ```html
-<rtk-notifications
- size="md">
-</rtk-notifications>
+<rtk-notifications size="md"> </rtk-notifications>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-notifications");
+	const el = document.querySelector("rtk-notifications");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
index 0cb6286a078603e..9364cd4626d354c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-overlay-modal component (Web Components (HTML
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-overlay-modal>
-</rtk-overlay-modal>
+<rtk-overlay-modal> </rtk-overlay-modal>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-overlay-modal");
+	const el = document.querySelector("rtk-overlay-modal");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
index ef79cf0de81f3f7..4cde117f427306e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-paginated-list component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
@@ -31,17 +32,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-paginated-list
- emptyListLabel="example">
-</rtk-paginated-list>
+<rtk-paginated-list emptyListLabel="example"> </rtk-paginated-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-paginated-list");
+	const el = document.querySelector("rtk-paginated-list");
 
-  el.autoScroll= true;
-  el.createNodes= [];
+	el.autoScroll = true;
+	el.createNodes = [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
index d62e21d5129aa82..7719882d3fb4be7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participant-count component (Web Components (
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-participant-count
- size="md">
-</rtk-participant-count>
+<rtk-participant-count size="md"> </rtk-participant-count>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-count");
+	const el = document.querySelector("rtk-participant-count");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
index caf9dc47c1b7c3f..f6bd84e42574673 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-participant-setup component (Web Components (
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -30,16 +31,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-participant-setup>
-</rtk-participant-setup>
+<rtk-participant-setup> </rtk-participant-setup>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-setup");
+	const el = document.querySelector("rtk-participant-setup");
 
-  el.isPreview= true;
-  el.participant= participant
+	el.isPreview = true;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
index 4cab2f0eb1eca60..9a88d9c0a727ee0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
@@ -5,23 +5,24 @@ description: API reference for rtk-participant-tile component (Web Components (H
 products:
   - realtime
 ---
+
 A component which plays a participants video and allows for placement
- of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
+| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
+| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
+| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
+| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
+| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
+| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
+| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
+| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
+| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
@@ -34,16 +35,14 @@ A component which plays a participants video and allows for placement
 ### With Properties
 
 ```html
-<rtk-participant-tile>
-</rtk-participant-tile>
+<rtk-participant-tile> </rtk-participant-tile>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant-tile");
+	const el = document.querySelector("rtk-participant-tile");
 
-  el.isPreview= true;
-  el.meeting= meeting
+	el.isPreview = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
index bb8ac1dd6367703..b353795e7b1d39f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-participant component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
@@ -32,16 +33,14 @@ A participant entry component used inside `rtk-participants` which shows data li
 ### With Properties
 
 ```html
-<rtk-participant>
-</rtk-participant>
+<rtk-participant> </rtk-participant>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participant");
+	const el = document.querySelector("rtk-participant");
 
-  el.meeting= meeting
-  el.participant= participant
+	el.meeting = meeting;
+	el.participant = participant;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
index 1f8797c35adb77e..60421301e0a2c48 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-audio component (Web Components
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A component which plays all the audio from participants and screenshares.
 ### With Properties
 
 ```html
-<rtk-participants-audio>
-</rtk-participants-audio>
+<rtk-participants-audio> </rtk-participants-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-audio");
+	const el = document.querySelector("rtk-participants-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
index 01d0f27f271ce7e..fd655a61d22ef33 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-participants-stage-list component (Web Compon
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
@@ -33,17 +34,14 @@ A component which lists all participants, with ability to
 ### With Properties
 
 ```html
-<rtk-participants-stage-list
- search="example">
-</rtk-participants-stage-list>
+<rtk-participants-stage-list search="example"> </rtk-participants-stage-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-stage-list");
+	const el = document.querySelector("rtk-participants-stage-list");
 
-  el.hideHeader= true;
-  el.meeting= meeting
+	el.hideHeader = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
index 963520bc7e53b54..7032a7bf6eae0d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-stage-queue component (Web Compo
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-stage-queue
- size="md">
-</rtk-participants-stage-queue>
+<rtk-participants-stage-queue size="md"> </rtk-participants-stage-queue>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-stage-queue");
+	const el = document.querySelector("rtk-participants-stage-queue");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
index bb79d669d9e7c10..a9ac8f17b8c789a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-participants-viewer-list component (Web Compo
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-viewer-list
- search="example">
-</rtk-participants-viewer-list>
+<rtk-participants-viewer-list search="example"> </rtk-participants-viewer-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-viewer-list");
+	const el = document.querySelector("rtk-participants-viewer-list");
 
-  el.hideHeader= true;
-  el.meeting= meeting
+	el.hideHeader = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
index bb42583235f5ab8..f2090258605a509 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-participants-waiting-list component (Web Comp
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-waiting-list
- size="md">
-</rtk-participants-waiting-list>
+<rtk-participants-waiting-list size="md"> </rtk-participants-waiting-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants-waiting-list");
+	const el = document.querySelector("rtk-participants-waiting-list");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
index 1ba0901c553c486..746ec51d0d8660b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-participants component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
@@ -31,16 +32,13 @@ A component which lists all participants, with ability to
 ### With Properties
 
 ```html
-<rtk-participants
- size="md">
-</rtk-participants>
+<rtk-participants size="md"> </rtk-participants>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-participants");
+	const el = document.querySelector("rtk-participants");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
index 57a566accadd160..150b3a750c1b030 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-permissions-message component (Web Components
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,15 +29,13 @@ A component which shows permission related troubleshooting
 ### With Properties
 
 ```html
-<rtk-permissions-message>
-</rtk-permissions-message>
+<rtk-permissions-message> </rtk-permissions-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-permissions-message");
+	const el = document.querySelector("rtk-permissions-message");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
index a125dffe72ae892..5d603b6e59daf8b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
@@ -5,13 +5,14 @@ description: API reference for rtk-pinned-message-selector component (Web Compon
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -24,15 +25,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-pinned-message-selector>
-</rtk-pinned-message-selector>
+<rtk-pinned-message-selector> </rtk-pinned-message-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-pinned-message-selector");
+	const el = document.querySelector("rtk-pinned-message-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
index 35331c64a8d6e7d..2d619085455442a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-plugin-main component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -27,15 +28,13 @@ A component which loads a plugin.
 ### With Properties
 
 ```html
-<rtk-plugin-main>
-</rtk-plugin-main>
+<rtk-plugin-main> </rtk-plugin-main>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-plugin-main");
+	const el = document.querySelector("rtk-plugin-main");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
index 162f337bb6592f1..6461be9451e19f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-plugins component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A component which lists all available plugins from their preset,
 ### With Properties
 
 ```html
-<rtk-plugins
- size="md">
-</rtk-plugins>
+<rtk-plugins size="md"> </rtk-plugins>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-plugins");
+	const el = document.querySelector("rtk-plugins");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
index 0272f65d9b3b48e..3e1e182ae6b3e03 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-poll-form component (Web Components (HTML) Li
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ A component that lets you create a poll.
 ### With Properties
 
 ```html
-<rtk-poll-form>
-</rtk-poll-form>
+<rtk-poll-form> </rtk-poll-form>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-poll-form");
+	const el = document.querySelector("rtk-poll-form");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
index c7c9985644e098f..74d94c512226da3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-poll component (Web Components (HTML) Library
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
@@ -29,15 +30,11 @@ A poll component.
 ### With Properties
 
 ```html
-<rtk-poll
- self="example">
-</rtk-poll>
+<rtk-poll self="example"> </rtk-poll>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-poll");
-
+	const el = document.querySelector("rtk-poll");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
index bef8f30b7725c38..98f0ca7892e6576 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-polls component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A component which lists all available plugins a user can access with
 ### With Properties
 
 ```html
-<rtk-polls
- size="md">
-</rtk-polls>
+<rtk-polls size="md"> </rtk-polls>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-polls");
+	const el = document.querySelector("rtk-polls");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
index d30318ecc55e3a5..4d369e04d632069 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-recording-indicator component (Web Components
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -28,16 +29,13 @@ A component which indicates the recording status of a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-indicator
- size="md">
-</rtk-recording-indicator>
+<rtk-recording-indicator size="md"> </rtk-recording-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-recording-indicator");
+	const el = document.querySelector("rtk-recording-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
index ec59e9f219e9f7f..a98b211032c1cbb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-recording-toggle component (Web Components (H
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A button which toggles recording state of a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-toggle
- size="md">
-</rtk-recording-toggle>
+<rtk-recording-toggle size="md"> </rtk-recording-toggle>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-recording-toggle");
+	const el = document.querySelector("rtk-recording-toggle");
 
-  el.disabled= true;
-  el.meeting= meeting
+	el.disabled = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
index a90c136dff9c22a..1f9320fd4015e72 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-screenshare-view component (Web Components (H
 products:
   - realtime
 ---
+
 A component which plays a participant's screenshared video.
- It also allows for placement of other components similar to `rtk-participant-tile`.
- This component will not render anything if the participant hasn't start screensharing.
+It also allows for placement of other components similar to `rtk-participant-tile`.
+This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
+| Property               | Type                                                                                                                     | Required | Default           | Description             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
+| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
+| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
+| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
+| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
+| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
+| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
+| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
+| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
 
 ## Usage Examples
 
@@ -33,16 +34,14 @@ A component which plays a participant's screenshared video.
 ### With Properties
 
 ```html
-<rtk-screenshare-view>
-</rtk-screenshare-view>
+<rtk-screenshare-view> </rtk-screenshare-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-screenshare-view");
+	const el = document.querySelector("rtk-screenshare-view");
 
-  el.hideFullScreenButton= true;
-  el.meeting= meeting
+	el.hideFullScreenButton = true;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
index be7787328820925..eb030d8fd7c3939 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-audio component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-settings-audio
- size="md">
-</rtk-settings-audio>
+<rtk-settings-audio size="md"> </rtk-settings-audio>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings-audio");
+	const el = document.querySelector("rtk-settings-audio");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
index 523484ecbd3ff73..90b1ddf72d04d58 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
@@ -5,25 +5,27 @@ description: API reference for rtk-settings-video component (Web Components (HTM
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -36,16 +38,13 @@ A component which lets to manage your camera devices and your video preferences.
 ### With Properties
 
 ```html
-<rtk-settings-video
- size="md">
-</rtk-settings-video>
+<rtk-settings-video size="md"> </rtk-settings-video>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings-video");
+	const el = document.querySelector("rtk-settings-video");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
index 4dd3286895b7a97..5dd39a1a89173b9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-settings component (Web Components (HTML) Lib
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -29,16 +30,13 @@ A settings component to see and change your audio/video devices
 ### With Properties
 
 ```html
-<rtk-settings
- size="md">
-</rtk-settings>
+<rtk-settings size="md"> </rtk-settings>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-settings");
+	const el = document.querySelector("rtk-settings");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
index 622524c4fd4f8c8..2f276604dd912f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-setup-screen component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -30,16 +31,13 @@ A screen shown before joining the meeting, where you can edit your display name,
 ### With Properties
 
 ```html
-<rtk-setup-screen
- size="md">
-</rtk-setup-screen>
+<rtk-setup-screen size="md"> </rtk-setup-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-setup-screen");
+	const el = document.querySelector("rtk-setup-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
index f7ebcc96c331885..8902143e96624a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-sidebar-ui component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
@@ -29,17 +30,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-sidebar-ui
- currentTab="example">
-</rtk-sidebar-ui>
+<rtk-sidebar-ui currentTab="example"> </rtk-sidebar-ui>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-sidebar-ui");
+	const el = document.querySelector("rtk-sidebar-ui");
 
-  el.focusCloseButton= true;
-  el.hideCloseAction= true;
+	el.focusCloseButton = true;
+	el.hideCloseAction = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
index d03131c5d572243..a22797273800cff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
@@ -5,22 +5,23 @@ description: API reference for rtk-sidebar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
@@ -33,16 +34,14 @@ A component which handles the sidebar and
 ### With Properties
 
 ```html
-<rtk-sidebar>
-</rtk-sidebar>
+<rtk-sidebar> </rtk-sidebar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-sidebar");
+	const el = document.querySelector("rtk-sidebar");
 
-  el.enabledSections= [];
-  el.meeting= meeting
+	el.enabledSections = [];
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
index 222b8ffafe1e97e..1614ba1605368b3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-simple-grid component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -32,17 +33,14 @@ A grid component which renders only the participants in a simple grid.
 ### With Properties
 
 ```html
-<rtk-simple-grid
- aspectRatio="example">
-</rtk-simple-grid>
+<rtk-simple-grid aspectRatio="example"> </rtk-simple-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-simple-grid");
+	const el = document.querySelector("rtk-simple-grid");
 
-  el.gap= 42;
-  el.meeting= meeting
+	el.gap = 42;
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
index 1c3c4ff1ad54559..ee3244f04afe45c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
@@ -5,26 +5,28 @@ description: API reference for rtk-speaker-selector component (Web Components (H
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
@@ -37,16 +39,13 @@ A component which lets to manage your audio devices and audio preferences.
 ### With Properties
 
 ```html
-<rtk-speaker-selector
- size="md">
-</rtk-speaker-selector>
+<rtk-speaker-selector size="md"> </rtk-speaker-selector>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-speaker-selector");
+	const el = document.querySelector("rtk-speaker-selector");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
index 1b2a10a9aa431a4..729aa072d8e8358 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spinner component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
@@ -25,15 +26,11 @@ A component which shows an animating spinner.
 ### With Properties
 
 ```html
-<rtk-spinner
- size="md">
-</rtk-spinner>
+<rtk-spinner size="md"> </rtk-spinner>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spinner");
-
+	const el = document.querySelector("rtk-spinner");
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
index feaee337d8349f1..0aba1ad132414cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
@@ -5,27 +5,29 @@ description: API reference for rtk-spotlight-grid component (Web Components (HTM
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
@@ -38,17 +40,13 @@ A grid component that renders two lists of participants: `pinnedParticipants` an
 ### With Properties
 
 ```html
-<rtk-spotlight-grid
- aspectRatio="example"
- gridSize="md">
-</rtk-spotlight-grid>
+<rtk-spotlight-grid aspectRatio="example" gridSize="md"> </rtk-spotlight-grid>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spotlight-grid");
+	const el = document.querySelector("rtk-spotlight-grid");
 
-  el.gap= 42;
+	el.gap = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
index fb0fcf76dbe0835..db3971dcecc6fba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-spotlight-indicator component (Web Components
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-spotlight-indicator
- size="md">
-</rtk-spotlight-indicator>
+<rtk-spotlight-indicator size="md"> </rtk-spotlight-indicator>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-spotlight-indicator");
+	const el = document.querySelector("rtk-spotlight-indicator");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
index 0f37d1d696ab3f4..99bc88ba74ef425 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-stage component (Web Components (HTML) Librar
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
@@ -26,15 +27,13 @@ A component used as a stage that commonly houses
 ### With Properties
 
 ```html
-<rtk-stage>
-</rtk-stage>
+<rtk-stage> </rtk-stage>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-stage");
+	const el = document.querySelector("rtk-stage");
 
-  el.iconPack= defaultIconPack
+	el.iconPack = defaultIconPack;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
index 899e19c8037f8c5..cd5071fb1a445d1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-switch component (Web Components (HTML) Libra
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ A switch component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-switch>
-</rtk-switch>
+<rtk-switch> </rtk-switch>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-switch");
+	const el = document.querySelector("rtk-switch");
 
-  el.checked= true;
-  el.disabled= true;
-  el.readonly= true;
+	el.checked = true;
+	el.disabled = true;
+	el.readonly = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
index 37b7c05e987b351..0eb2929868dce57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-tab-bar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-tab-bar>
-</rtk-tab-bar>
+<rtk-tab-bar> </rtk-tab-bar>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-tab-bar");
+	const el = document.querySelector("rtk-tab-bar");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
index 47adf5034bc93ca..22603bbe1ca64f7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
@@ -5,21 +5,22 @@ description: API reference for rtk-text-composer-view component (Web Components
 products:
   - realtime
 ---
+
 A component which renders a text composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `placeholder` | `string` | ✅ | - | Placeholder text |
-| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
-| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `value` | `string` | ✅ | - | Default value for text input |
+| Property            | Type                              | Required | Default           | Description                                   |
+| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
+| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
+| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
+| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
+| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
+| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
+| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
+| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
+| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
+| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
 
 ## Usage Examples
 
@@ -32,16 +33,14 @@ A component which renders a text composer
 ### With Properties
 
 ```html
-<rtk-text-composer-view>
-</rtk-text-composer-view>
+<rtk-text-composer-view> </rtk-text-composer-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-composer-view");
+	const el = document.querySelector("rtk-text-composer-view");
 
-  el.disabled= true;
-  el.maxLength= 42;
+	el.disabled = true;
+	el.maxLength = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
index 4e15cd5f1fcdb7f..c7802ea87ac4cbc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-text-message-view component (Web Components (
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
@@ -25,16 +26,13 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message-view
- text="example">
-</rtk-text-message-view>
+<rtk-text-message-view text="example"> </rtk-text-message-view>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-message-view");
+	const el = document.querySelector("rtk-text-message-view");
 
-  el.isMarkdown= true;
+	el.isMarkdown = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
index 6163072c5b51c71..db080a025087bed 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
@@ -5,19 +5,20 @@ description: API reference for rtk-text-message component (Web Components (HTML)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
@@ -30,15 +31,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-text-message>
-</rtk-text-message>
+<rtk-text-message> </rtk-text-message>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-text-message");
+	const el = document.querySelector("rtk-text-message");
 
-  el.isContinued= true;
+	el.isContinued = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
index 6e38e8bb3887731..ff346f3104717b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
@@ -5,20 +5,21 @@ description: API reference for rtk-tooltip component (Web Components (HTML) Libr
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
@@ -31,16 +32,14 @@ Tooltip component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-tooltip>
-</rtk-tooltip>
+<rtk-tooltip> </rtk-tooltip>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-tooltip");
+	const el = document.querySelector("rtk-tooltip");
 
-  el.delay= 42;
-  el.disabled= true;
+	el.delay = 42;
+	el.disabled = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
index f0631ca86b905bd..5ed0883121e7db1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-transcript component (Web Components (HTML) L
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows a transcript.
 ### With Properties
 
 ```html
-<rtk-transcript
- transcript="example">
-</rtk-transcript>
+<rtk-transcript transcript="example"> </rtk-transcript>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-transcript");
+	const el = document.querySelector("rtk-transcript");
 
-  el.transcript= {};
+	el.transcript = {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
index f75a986f1cfd9de..c734652bd0fbcd1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
@@ -5,18 +5,19 @@ description: API reference for rtk-transcripts component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -29,15 +30,13 @@ A component which handles transcripts.
 ### With Properties
 
 ```html
-<rtk-transcripts>
-</rtk-transcripts>
+<rtk-transcripts> </rtk-transcripts>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-transcripts");
+	const el = document.querySelector("rtk-transcripts");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
index 041148907fcb623..3387ed120b39d4e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
@@ -5,17 +5,18 @@ description: API reference for rtk-ui-provider component (Web Components (HTML)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
@@ -28,17 +29,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-ui-provider>
-</rtk-ui-provider>
+<rtk-ui-provider> </rtk-ui-provider>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-ui-provider");
+	const el = document.querySelector("rtk-ui-provider");
 
-  el.config= defaultUiConfig
-  el.mode= meeting
-  el.showSetupScreen= true;
+	el.config = defaultUiConfig;
+	el.mode = meeting;
+	el.showSetupScreen = true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
index 4d041852272b5c6..42c4225721997e0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
@@ -5,16 +5,17 @@ description: API reference for rtk-viewer-count component (Web Components (HTML)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
@@ -27,16 +28,13 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-viewer-count
- variant="primary">
-</rtk-viewer-count>
+<rtk-viewer-count variant="primary"> </rtk-viewer-count>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-viewer-count");
+	const el = document.querySelector("rtk-viewer-count");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
index 9856cd393b4f8d3..d551b47a44c6b52 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
@@ -5,15 +5,16 @@ description: API reference for rtk-virtualized-participant-list component (Web C
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
@@ -26,16 +27,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-virtualized-participant-list>
-</rtk-virtualized-participant-list>
+<rtk-virtualized-participant-list> </rtk-virtualized-participant-list>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-virtualized-participant-list");
+	const el = document.querySelector("rtk-virtualized-participant-list");
 
-  el.bufferedItemsCount= 42;
-  el.itemHeight= 42;
+	el.bufferedItemsCount = 42;
+	el.itemHeight = 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
index 5486f52a36737c7..f65c231d33c3ab5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
@@ -5,14 +5,15 @@ description: API reference for rtk-waiting-screen component (Web Components (HTM
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
@@ -25,15 +26,13 @@ products:
 ### With Properties
 
 ```html
-<rtk-waiting-screen>
-</rtk-waiting-screen>
+<rtk-waiting-screen> </rtk-waiting-screen>
 ```
 
-
 ```html
 <script>
-  const el = document.querySelector("rtk-waiting-screen");
+	const el = document.querySelector("rtk-waiting-screen");
 
-  el.meeting= meeting
+	el.meeting = meeting;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
index 301d8b7d3bff009..248a49136afe991 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
@@ -10,11 +10,11 @@ A pressable menu item within a menu.
 
 ## Properties
 
-| Property   | Type                                  | Required | Default | Description            |
-| ---------- | ------------------------------------- | -------- | ------- | ---------------------- |
-| `children` | `ReactNode`                           | ✅       | -       | Menu item content      |
-| `onClick`  | `(ev) => {}` | ❌       | -       | Press handler callback |
-| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'`        | ❌       | -       | Size variant           |
+| Property   | Type                           | Required | Default | Description            |
+| ---------- | ------------------------------ | -------- | ------- | ---------------------- |
+| `children` | `ReactNode`                    | ✅       | -       | Menu item content      |
+| `onClick`  | `(ev) => {}`                   | ❌       | -       | Press handler callback |
+| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'` | ❌       | -       | Size variant           |
 
 ## Usage Examples
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
index 0ec727fad6c4379..422840190bc663c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkAi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `AIView` | ✅ | - | View type |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| `view`     | `AIView`   | ✅       | -                       | View type      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAi } from '@cloudflare/realtimekit-react-ui';
+import { RtkAi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAi />;
+	return <RtkAi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAi } from '@cloudflare/realtimekit-react-ui';
+import { RtkAi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAi
-      meeting={meeting}
-      size="md"
-      view={aiview}
-    />
-  );
+	return <RtkAi meeting={meeting} size="md" view={aiview} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
index 8545071a098a60f..396561410fcfa72 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkAiToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAiToggle />;
+	return <RtkAiToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAiToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkAiToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
index ef4f69f64146916..676a14f2675ae81 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
@@ -5,38 +5,33 @@ description: API reference for RtkAiTranscriptions component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type           | Required | Default         | Description            |
+| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
+| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
+| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
+| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAiTranscriptions />;
+	return <RtkAiTranscriptions />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
+import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAiTranscriptions
-      initialTranscriptions={[]}
-      meeting={meeting}
-    />
-  );
+	return <RtkAiTranscriptions initialTranscriptions={[]} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
index 5a8f8fedf34406a..75ece5db8d70097 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
@@ -5,43 +5,39 @@ description: API reference for RtkAudioGrid component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description                      |
+| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
+| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
+| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
+| `size`     | `Size1`     | ✅       | -                 | Size                             |
+| `states`   | `States1`   | ✅       | -                 | States                           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioGrid />;
+	return <RtkAudioGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioGrid
-      config={defaultUiConfig}
-      hideSelf={true}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkAudioGrid config={defaultUiConfig} hideSelf={true} meeting={meeting} />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
index 71a65e966b788a4..5c8a03c08f715b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkAudioTile component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property      | Type        | Required | Default           | Description        |
+| ------------- | ----------- | -------- | ----------------- | ------------------ |
+| `config`      | `UIConfig`  | ✅       | -                 | Config             |
+| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
+| `participant` | `Peer`      | ✅       | -                 | Participant object |
+| `size`        | `Size`      | ✅       | -                 | Size               |
+| `states`      | `States1`   | ✅       | -                 | States             |
+| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioTile />;
+	return <RtkAudioTile />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioTile
-      config={defaultUiConfig}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkAudioTile
+			config={defaultUiConfig}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
index 9f5b3941640b98a..33a40cf994b8247 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkAudioVisualizer component (React Library)
 products:
   - realtime
 ---
+
 An audio visualizer component which visualizes a participants audio.
- Commonly used inside `rtk-name-tag`.
+Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
+| Property        | Type                     | Required | Default           | Description                                                                                   |
+| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
+| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
+| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
+| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
+| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
+| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
+| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAudioVisualizer />;
+	return <RtkAudioVisualizer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
+import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAudioVisualizer
-      hideMuted={true}
-      isScreenShare={true}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkAudioVisualizer
+			hideMuted={true}
+			isScreenShare={true}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
index 0e6ffdb430de443..b48ab891f56912c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkAvatar component (React Library)
 products:
   - realtime
 ---
+
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
+| Property      | Type                                                                 | Required | Default           | Description        |
+| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
+| `size`        | `Size`                                                               | ✅       | -                 | Size               |
+| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
+| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
+import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkAvatar />;
+	return <RtkAvatar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
+import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkAvatar
-      participant="example"
-      size="md"
-      variant="circular"
-    />
-  );
+	return <RtkAvatar participant="example" size="md" variant="circular" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
index 487dc6287788cc7..a8884efc78197e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkBreakoutRoomManager component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `allowDelete` | `boolean` | ✅ | - | allow room delete |
-| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
-| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isDragMode` | `boolean` | ✅ | - | Drag mode |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
-| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                | Type                 | Required | Default           | Description                      |
+| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
+| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
+| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
+| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
+| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
+| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
+| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
+| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
+| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
+| `states`                | `States`             | ✅       | -                 | States object                    |
+| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomManager />;
+	return <RtkBreakoutRoomManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomManager
-      allowDelete={true}
-      assigningParticipants={true}
-      defaultExpanded={true}
-    />
-  );
+	return (
+		<RtkBreakoutRoomManager
+			allowDelete={true}
+			assigningParticipants={true}
+			defaultExpanded={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
index fb2341581602302..2004a147afe14a6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkBreakoutRoomParticipants component (React Libr
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participantIds` | `string[]` | ✅ | - | Participant ids |
-| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                 | Type       | Required | Default           | Description           |
+| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
+| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
+| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
+| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
+| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
+| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomParticipants />;
+	return <RtkBreakoutRoomParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomParticipants
-      meeting={meeting}
-      participantIds="example"
-      selectedParticipantIds="example"
-    />
-  );
+	return (
+		<RtkBreakoutRoomParticipants
+			meeting={meeting}
+			participantIds="example"
+			selectedParticipantIds="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
index 50f3260dcf7a651..dcbcea2d4770056 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkBreakoutRoomsManager component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomsManager />;
+	return <RtkBreakoutRoomsManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomsManager
-      meeting={meeting}
-    />
-  );
+	return <RtkBreakoutRoomsManager meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
index 380c96f9f1541ef..437ddd1710ebf57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkBreakoutRoomsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of breakout rooms.
- You need to pass the `meeting` object to it.
+You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ✅ | - | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ✅ | - | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default | Description    |
+| ---------- | ------------------- | -------- | ------- | -------------- |
+| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
+| `size`     | `Size`              | ✅       | -       | Size           |
+| `states`   | `States`            | ✅       | -       | States object  |
+| `t`        | `RtkI18n`           | ✅       | -       | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBreakoutRoomsToggle />;
+	return <RtkBreakoutRoomsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBreakoutRoomsToggle
-      iconPack={defaultIconPack}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkBreakoutRoomsToggle
+			iconPack={defaultIconPack}
+			meeting={meeting}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
index 856b11cff1b3d13..2117f12536528dd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkBroadcastMessageModal component (React Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States1`  | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkBroadcastMessageModal />;
+	return <RtkBroadcastMessageModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkBroadcastMessageModal
-      meeting={meeting}
-    />
-  );
+	return <RtkBroadcastMessageModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
index 5be7a8515fbc268..4662a4cb4703613 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
@@ -5,44 +5,38 @@ description: API reference for RtkButton component (React Library)
 products:
   - realtime
 ---
+
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
-| `kind` | `ButtonKind` | ✅ | - | Button type |
-| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
-| `size` | `Size` | ✅ | - | Size |
-| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
-| `variant` | `ButtonVariant` | ✅ | - | Button variant |
+| Property   | Type                        | Required | Default | Description                          |
+| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
+| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
+| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
+| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
+| `size`     | `Size`                      | ✅       | -       | Size                                 |
+| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
+| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkButton />;
+	return <RtkButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkButton
-      disabled={true}
-      kind={buttonkind}
-      reverse={true}
-    />
-  );
+	return <RtkButton disabled={true} kind={buttonkind} reverse={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
index 5964ca5795dff5d..5bd7f5725ed45f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
@@ -5,51 +5,52 @@ description: API reference for RtkCameraSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCameraSelector />;
+	return <RtkCameraSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCameraSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkCameraSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
index f32d538b0d242cb..ef0f7be9cbd784b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCameraToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your camera.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCameraToggle />;
+	return <RtkCameraToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCameraToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkCameraToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
index 4e5a7b0e9ae81e2..ccb44bea4849232 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCaptionToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCaptionToggle />;
+	return <RtkCaptionToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCaptionToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkCaptionToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
index 08109cd1a6900d2..88044716a737a05 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkChat component (React Library)
 products:
   - realtime
 ---
+
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default                 | Description    |
+| ----------- | ----------- | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`      | ✅       | -                       | Size           |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChat } from '@cloudflare/realtimekit-react-ui';
+import { RtkChat } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChat />;
+	return <RtkChat />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChat } from '@cloudflare/realtimekit-react-ui';
+import { RtkChat } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChat
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkChat meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
index 3c8a6961bebc260..f71eb84400228a3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkChatComposerUi component (React Library)
 products:
   - realtime
 ---
+
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type                                                                                                    | Required | Default           | Description                         |
+| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
+| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
+| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
+| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
+| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
+| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
+| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatComposerUi />;
+	return <RtkChatComposerUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatComposerUi
-      canSendFiles={true}
-      canSendTextMessage={true}
-      size="md"
-    />
-  );
+	return (
+		<RtkChatComposerUi
+			canSendFiles={true}
+			canSendTextMessage={true}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
index 2ebfa2b0d2a24e3..3f5eabaf3bbce7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
@@ -5,49 +5,49 @@ description: API reference for RtkChatComposerView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a chat composer
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
-| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
-| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
-| `maxLength` | `number` | ✅ | - | Max length for text input |
-| `message` | `string` | ✅ | - | Message to be pre-populated |
-| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
-| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
-| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type                                          | Required | Default           | Description                             |
+| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
+| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
+| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
+| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
+| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
+| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
+| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
+| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
+| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
+| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
+| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
+| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatComposerView />;
+	return <RtkChatComposerView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatComposerView
-      canSendFiles={true}
-      canSendTextMessage={true}
-      inputTextPlaceholder="example"
-    />
-  );
+	return (
+		<RtkChatComposerView
+			canSendFiles={true}
+			canSendTextMessage={true}
+			inputTextPlaceholder="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
index b8d221aa00d5d75..172ac6463eae729 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
@@ -5,19 +5,19 @@ description: API reference for RtkChatHeader component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-*No properties available.*
+_No properties available._
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatHeader />;
+	return <RtkChatHeader />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
index 62095db66fa56ee..06b7622778baee0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
@@ -5,55 +5,49 @@ description: API reference for RtkChatMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `alignRight` | `boolean` | ✅ | - | aligns message to right |
-| `canDelete` | `boolean` | ✅ | - | can delete message |
-| `canEdit` | `boolean` | ✅ | - | can edit message |
-| `canPin` | `boolean` | ✅ | - | can pin this message |
-| `canReply` | `boolean` | ✅ | - | can quote reply this message |
-| `child` | `HTMLElement` | ✅ | - | Child |
-| `disableControls` | `boolean` | ✅ | - | disables controls |
-| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | is continued |
-| `isSelf` | `boolean` | ✅ | - | if sender is self |
-| `isUnread` | `boolean` | ✅ | - | is unread |
-| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
-| `message` | `Message` | ✅ | - | message item |
-| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default           | Description                            |
+| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
+| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
+| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
+| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
+| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
+| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
+| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
+| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
+| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
+| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
+| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
+| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
+| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
+| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
+| `message`              | `Message`     | ✅       | -                 | message item                           |
+| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
+| `size`                 | `Size`        | ✅       | -                 | Size                                   |
+| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessage />;
+	return <RtkChatMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessage
-      alignRight={true}
-      canDelete={true}
-      canEdit={true}
-    />
-  );
+	return <RtkChatMessage alignRight={true} canDelete={true} canEdit={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
index 39be829497f47dc..24dfa75d1e264c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkChatMessagesUi component (React Library)
 products:
   - realtime
 ---
+
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `messages` | `Chat[]` | ✅ | - | Chat Messages |
-| `selectedGroup` | `string` | ✅ | - | Selected group key |
-| `selfUserId` | `string` | ✅ | - | User ID of self user |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type        | Required | Default           | Description                         |
+| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
+| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
+| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
+| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
+| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
+| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
+| `size`           | `Size1`     | ✅       | -                 | Size                                |
+| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessagesUi />;
+	return <RtkChatMessagesUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessagesUi
-      canPinMessages={true}
-      messages={[]}
-      selectedGroup="example"
-    />
-  );
+	return (
+		<RtkChatMessagesUi
+			canPinMessages={true}
+			messages={[]}
+			selectedGroup="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
index 2050ab5a26bc247..5891af64b276945 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkChatMessagesUiPaginated component (React Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type                  | Required | Default           | Description                                                                                      |
+| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
+| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
+| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
+| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
+| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatMessagesUiPaginated />;
+	return <RtkChatMessagesUiPaginated />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatMessagesUiPaginated
-      meeting={meeting}
-      privateChatRecipient={participant | null}
-      size="md"
-    />
-  );
+	return (
+		<RtkChatMessagesUiPaginated
+			meeting={meeting}
+			privateChatRecipient={participant | null}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
index 8218e3a1de98dcc..7b498cd1db28fe1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkChatSearchResults component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `channelId` | `string` | ✅ | - | Channel id |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `query` | `string` | ✅ | - | Search query |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description    |
+| ----------- | ----------- | -------- | ----------------- | -------------- |
+| `channelId` | `string`    | ✅       | -                 | Channel id     |
+| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
+| `query`     | `string`    | ✅       | -                 | Search query   |
+| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSearchResults />;
+	return <RtkChatSearchResults />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSearchResults
-      channelId="example"
-      meeting={meeting}
-      query="example"
-    />
-  );
+	return (
+		<RtkChatSearchResults
+			channelId="example"
+			meeting={meeting}
+			query="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
index d57247e25b7d5f0..377f279bef2cd5e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkChatSelector component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type         | Required | Default                 | Description    |
+| ----------- | ------------ | -------- | ----------------------- | -------------- |
+| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
+| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
+| `size`      | `Size`       | ✅       | -                       | Size           |
+| `states`    | `States1`    | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSelector />;
+	return <RtkChatSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSelector
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkChatSelector meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
index 780c0f8d5ddc863..883fee41a51d0de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkChatSelectorUi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `groups` | `ChatGroup[]` | ✅ | - | Participants |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `selectedGroupId` | `string` | ✅ | - | Selected participant |
-| `selfUserId` | `string` | ✅ | - | Self User ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
+| Property          | Type                     | Required | Default           | Description          |
+| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
+| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
+| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
+| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
+| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
+| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
+| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatSelectorUi />;
+	return <RtkChatSelectorUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatSelectorUi
-      groups={[]}
-      selectedGroupId="example"
-      selfUserId="example"
-    />
-  );
+	return (
+		<RtkChatSelectorUi
+			groups={[]}
+			selectedGroupId="example"
+			selfUserId="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
index 93bb6e482beaa63..23fa8dea93d070a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
@@ -5,49 +5,47 @@ description: API reference for RtkChatToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of chat.
- You need to pass the `meeting` object to it to see the unread messages count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'chat' }
- ```
+You need to pass the `meeting` object to it to see the unread messages count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "chat";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkChatToggle />;
+	return <RtkChatToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkChatToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkChatToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
index 5b51f5833c33a3f..6671c8edffa9090 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkClock component (React Library)
 products:
   - realtime
 ---
+
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkClock } from '@cloudflare/realtimekit-react-ui';
+import { RtkClock } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkClock />;
+	return <RtkClock />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkClock } from '@cloudflare/realtimekit-react-ui';
+import { RtkClock } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkClock
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkClock meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
index 03354726cb31f89..31eb8135db4c518 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
@@ -5,40 +5,36 @@ description: API reference for RtkConfirmationModal component (React Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkConfirmationModal />;
+	return <RtkConfirmationModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkConfirmationModal
-      meeting={meeting}
-    />
-  );
+	return <RtkConfirmationModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
index 23812e3db206ab2..70878abe0db3e5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkControlbar component (React Library)
 products:
   - realtime
 ---
+
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkControlbar />;
+	return <RtkControlbar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkControlbar
-      disableRender={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkControlbar disableRender={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
index d0e6e508caf9480..d9027e6aa0875b4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
@@ -5,47 +5,43 @@ description: API reference for RtkControlbarButton component (React Library)
 products:
   - realtime
 ---
+
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
-| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
-| `icon` | `string` | ✅ | - | Icon |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
-| `label` | `string` | ✅ | - | Label of button |
-| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
+| Property      | Type                 | Required | Default           | Description                                                    |
+| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
+| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
+| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
+| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
+| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
+| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
+| `label`       | `string`             | ✅       | -                 | Label of button                                                |
+| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
+| `size`        | `Size`               | ✅       | -                 | Size                                                           |
+| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkControlbarButton />;
+	return <RtkControlbarButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkControlbarButton
-      brandIcon={true}
-      disabled={true}
-      icon="example"
-    />
-  );
+	return (
+		<RtkControlbarButton brandIcon={true} disabled={true} icon="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
index 7b619a1539d261f..2f691f8771858ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkCounter component (React Library)
 products:
   - realtime
 ---
+
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `minValue` | `number` | ✅ | - | Minimum value |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `value` | `number` | ✅ | - | Initial value |
+| Property   | Type        | Required | Default           | Description   |
+| ---------- | ----------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
+| `minValue` | `number`    | ✅       | -                 | Minimum value |
+| `size`     | `Size1`     | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
+| `value`    | `number`    | ✅       | -                 | Initial value |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
+import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkCounter />;
+	return <RtkCounter />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
+import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkCounter
-      minValue={42}
-      size="md"
-      value={42}
-    />
-  );
+	return <RtkCounter minValue={42} size="md" value={42} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
index f053eb720bed15d..e50a8ecb11348d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkDebugger component (React Library)
 products:
   - realtime
 ---
+
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebugger />;
+	return <RtkDebugger />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebugger
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebugger meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
index 7dc5d08497e8bd7..e3b258be377ed38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerAudio component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerAudio />;
+	return <RtkDebuggerAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerAudio
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerAudio meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
index 84e96a1f71fb63a..62053832f219996 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerScreenshare component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerScreenshare />;
+	return <RtkDebuggerScreenshare />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerScreenshare
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerScreenshare meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
index 351882399cc12df..fa2fc78d58a6309 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerSystem component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerSystem />;
+	return <RtkDebuggerSystem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerSystem
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerSystem meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
index a31dd78c42d4145..5e693f7e36fb65e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkDebuggerToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerToggle />;
+	return <RtkDebuggerToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkDebuggerToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
index c74f2cb9062572f..f5819d9caac23ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkDebuggerVideo component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `states`   | `States1`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDebuggerVideo />;
+	return <RtkDebuggerVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDebuggerVideo
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDebuggerVideo meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
index fe104ba37211c2a..46fbf93818f24f8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkDialog component (React Library)
 products:
   - realtime
 ---
+
 A dialog component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
-| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property           | Type       | Required | Default                 | Description                            |
+| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
+| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
+| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
+| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
+| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
+| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
+| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
+| `size`             | `Size`     | ✅       | -                       | Size                                   |
+| `states`           | `States`   | ✅       | -                       | States object                          |
+| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDialog />;
+	return <RtkDialog />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDialog
-      disableEscapeKey={true}
-      hideCloseButton={true}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkDialog
+			disableEscapeKey={true}
+			hideCloseButton={true}
+			meeting={meeting}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
index 61ee80cd7643468..736b239555dd6c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
@@ -5,49 +5,45 @@ description: API reference for RtkDialogManager component (React Library)
 products:
   - realtime
 ---
+
 A component which handles all dialog elements in a component such as:
- - rtk-settings
- - rtk-leave-meeting
- - rtk-permissions-message
- - rtk-image-viewer
- - rtk-breakout-rooms-manager
- This components depends on the values from `states` object.
+
+- rtk-settings
+- rtk-leave-meeting
+- rtk-permissions-message
+- rtk-image-viewer
+- rtk-breakout-rooms-manager
+  This components depends on the values from `states` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDialogManager />;
+	return <RtkDialogManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
+import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDialogManager
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkDialogManager meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
index a5285022bbe30c4..90c0d95b4208a0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkDraftAttachmentView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property     | Type                                                 | Required | Default           | Description           |
+| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
+| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
+| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
+import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkDraftAttachmentView />;
+	return <RtkDraftAttachmentView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
+import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkDraftAttachmentView
-      attachment={{}}
-    />
-  );
+	return <RtkDraftAttachmentView attachment={{}} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
index c43046ea84826be..8a0e1b654ee40a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkEmojiPicker component (React Library)
 products:
   - realtime
 ---
+
 A very simple emoji picker component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property          | Type       | Required | Default           | Description                               |
+| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
+| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
+| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
+| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEmojiPicker />;
+	return <RtkEmojiPicker />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEmojiPicker
-      focusWhenOpened={true}
-    />
-  );
+	return <RtkEmojiPicker focusWhenOpened={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
index fb41c2305bae5b8..dd15556f86ad2a2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkEmojiPickerButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isActive` | `boolean` | ✅ | - | Active state indicator |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description            |
+| ---------- | ----------- | -------- | ----------------- | ---------------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
+| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEmojiPickerButton />;
+	return <RtkEmojiPickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEmojiPickerButton
-      isActive={true}
-    />
-  );
+	return <RtkEmojiPickerButton isActive={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
index f5d34bcb49b8d47..9e06d6de13b10ac 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkEndedScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Global states |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | Global states |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
+| `size`     | `Size`     | ✅       | -                       | Size          |
+| `states`   | `States`   | ✅       | -                       | Global states |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkEndedScreen />;
+	return <RtkEndedScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkEndedScreen
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkEndedScreen meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
index 249558fdf892cff..d000f71a09a18c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkFileDropzone component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type          | Required | Default           | Description                                 |
+| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
+| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
+| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
+| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileDropzone />;
+	return <RtkFileDropzone />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileDropzone
-      hostEl={htmlelement}
-    />
-  );
+	return <RtkFileDropzone hostEl={htmlelement} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
index 160e6d45a1c3e0d..0d763747bc4f21b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkFileMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
- A component which renders a file message from chat.
+A component which renders a file message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `FileMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileMessage />;
+	return <RtkFileMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileMessage
-      isContinued={true}
-      message={filemessage}
-      now={date}
-    />
-  );
+	return <RtkFileMessage isContinued={true} message={filemessage} now={date} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
index baf330586b09a46..64098e714003e5e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkFileMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a file message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `name` | `string` | ✅ | - | Name of the file |
-| `size` | `number` | ✅ | - | Size of the file |
-| `url` | `string` | ✅ | - | Url of the file |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `name`     | `string`    | ✅       | -                 | Name of the file |
+| `size`     | `number`    | ✅       | -                 | Size of the file |
+| `url`      | `string`    | ✅       | -                 | Url of the file  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFileMessageView />;
+	return <RtkFileMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFileMessageView
-      name="example"
-      size={42}
-      url="example"
-    />
-  );
+	return <RtkFileMessageView name="example" size={42} url="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
index 7695557d4ce9b2e..f495c13464a820e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkFilePickerButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `filter` | `string` | ✅ | - | File type filter to open file picker with |
-| `icon` | `keyof IconPack1` | ✅ | - | Icon |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `label` | `string` | ✅ | - | Label for tooltip |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type              | Required | Default           | Description                               |
+| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
+| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
+| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
+| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
+| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
+| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFilePickerButton />;
+	return <RtkFilePickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFilePickerButton
-      filter="example"
-      icon={defaultIconPack}
-      label="example"
-    />
-  );
+	return (
+		<RtkFilePickerButton
+			filter="example"
+			icon={defaultIconPack}
+			label="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
index 4dfd50432f2e792..0abc92d640e427b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkFullscreenToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles full screen mode for any
- existing `rtk-meeting` component in the DOM.
+existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property        | Type                | Required | Default           | Description                  |
+| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
+| `size`          | `Size`              | ✅       | -                 | Size                         |
+| `states`        | `States`            | ✅       | -                 | States object                |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
+| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
+| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkFullscreenToggle />;
+	return <RtkFullscreenToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkFullscreenToggle
-      size="md"
-      targetElement={htmlelement}
-      variant="button"
-    />
-  );
+	return (
+		<RtkFullscreenToggle
+			size="md"
+			targetElement={htmlelement}
+			variant="button"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
index ba09d23bb59421f..f927f0f83579df1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
@@ -5,49 +5,43 @@ description: API reference for RtkGrid component (React Library)
 products:
   - realtime
 ---
+
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `gap` | `number` | ✅ | - | Gap between participants |
-| `gridSize` | `GridSize` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `layout` | `GridLayout` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `overrides` | `any` | ✅ | - | @deprecated |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type         | Required | Default                 | Description                          |
+| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
+| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
+| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
+| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
+| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
+| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
+| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
+| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
+| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
+| `size`        | `Size`       | ✅       | -                       | Size                                 |
+| `states`      | `States`     | ✅       | -                       | States                               |
+| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkGrid />;
+	return <RtkGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
index 5f237bf642f2544..2ec869ec68a635d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkGridPagination component (React Library)
 products:
   - realtime
 ---
+
 A component which allows you to change current page and view mode
- of active participants list. This is reflected in the `rtk-grid` component.
+of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size Prop |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
+| Property   | Type                     | Required | Default           | Description    |
+| ---------- | ------------------------ | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
+| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
+| `states`   | `States`                 | ✅       | -                 | States         |
+| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
+import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkGridPagination />;
+	return <RtkGridPagination />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
+import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkGridPagination
-      meeting={meeting}
-      size="md"
-      variant={gridpaginationvariants}
-    />
-  );
+	return (
+		<RtkGridPagination
+			meeting={meeting}
+			size="md"
+			variant={gridpaginationvariants}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
index 10ccda38fa97f7e..ae22b18378bd4c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkHeader component (React Library)
 products:
   - realtime
 ---
+
 A component that houses all the header components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
+| Property        | Type                 | Required | Default                 | Description                      |
+| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
+| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
+| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
+| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
+| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
+| `size`          | `Size`               | ✅       | -                       | Size                             |
+| `states`        | `States`             | ✅       | -                       | States                           |
+| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
+| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkHeader />;
+	return <RtkHeader />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
+import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkHeader
-      disableRender={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkHeader disableRender={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
index f7283d6288d99a4..16a092f54b2dbce 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkIcon component (React Library)
 products:
   - realtime
 ---
+
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `icon` | `string` | ✅ | - | Icon |
-| `size` | `Size1` | ✅ | - | Size |
-| `variant` | `IconVariant` | ✅ | - | Icon variant |
+| Property  | Type          | Required | Default | Description  |
+| --------- | ------------- | -------- | ------- | ------------ |
+| `icon`    | `string`      | ✅       | -       | Icon         |
+| `size`    | `Size1`       | ✅       | -       | Size         |
+| `variant` | `IconVariant` | ✅       | -       | Icon variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
+import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkIcon />;
+	return <RtkIcon />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
+import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkIcon
-      icon="example"
-      size="md"
-      variant="primary"
-    />
-  );
+	return <RtkIcon icon="example" size="md" variant="primary" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
index 673fc18b193b110..c1bb80f2c5f6df1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkIdleScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen that handles the idle state,
- i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description   |
+| ---------- | ---------- | -------- | ----------------------- | ------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkIdleScreen />;
+	return <RtkIdleScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkIdleScreen
-      meeting={meeting}
-    />
-  );
+	return <RtkIdleScreen meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
index 8c0288f2c73bdea..55513c0267caef0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
@@ -5,45 +5,41 @@ description: API reference for RtkImageMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
- A component which renders an image message from chat.
+A component which renders an image message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `ImageMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type           | Required | Default           | Description                                             |
+| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageMessage />;
+	return <RtkImageMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageMessage
-      isContinued={true}
-      message={imagemessage}
-      now={date}
-    />
-  );
+	return (
+		<RtkImageMessage isContinued={true} message={imagemessage} now={date} />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
index c780f5404911db6..7bbc3cd4d39a23a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkImageMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders an image message.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `url` | `string` | ✅ | - | Url of the image |
+| Property   | Type        | Required | Default           | Description      |
+| ---------- | ----------- | -------- | ----------------- | ---------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
+| `url`      | `string`    | ✅       | -                 | Url of the image |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageMessageView />;
+	return <RtkImageMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageMessageView
-      url="example"
-    />
-  );
+	return <RtkImageMessageView url="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
index 91083a36a5cc7cd..9df4c2bb772122b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkImageViewer component (React Library)
 products:
   - realtime
 ---
+
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `image` | `ImageMessage` | ✅ | - | Image message |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type           | Required | Default           | Description   |
+| ---------- | -------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
+| `image`    | `ImageMessage` | ✅       | -                 | Image message |
+| `size`     | `Size`         | ✅       | -                 | Size          |
+| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkImageViewer />;
+	return <RtkImageViewer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
+import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkImageViewer
-      image={imagemessage}
-      size="md"
-    />
-  );
+	return <RtkImageViewer image={imagemessage} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
index 0fbe8b295b4e90a..59bb5a4a42279d0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
@@ -5,35 +5,31 @@ description: API reference for RtkInformationTooltip component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkInformationTooltip />;
+	return <RtkInformationTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkInformationTooltip
-      iconPack={defaultIconPack}
-    />
-  );
+	return <RtkInformationTooltip iconPack={defaultIconPack} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
index 980d877c6c2be1c..cb2514eb8f698d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
@@ -5,43 +5,39 @@ description: API reference for RtkJoinStage component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property     | Type              | Required | Default                 | Description    |
+| ------------ | ----------------- | -------- | ----------------------- | -------------- |
+| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
+| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
+| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
+| `size`       | `Size`            | ✅       | -                       | Size           |
+| `states`     | `States`          | ✅       | -                       | States object  |
+| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkJoinStage />;
+	return <RtkJoinStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkJoinStage
-      dataConfig={modaldataconfig}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkJoinStage dataConfig={modaldataconfig} meeting={meeting} size="md" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
index cbadd40c668ffb5..bd0118ecce5e460 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkLeaveButton component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description |
+| ---------- | ------------------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size`              | ✅       | -                 | Size        |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLeaveButton />;
+	return <RtkLeaveButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLeaveButton
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkLeaveButton size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
index 381df4d5a32d9a8..caaa57aa9b7489a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkLeaveMeeting component (React Library)
 products:
   - realtime
 ---
+
 A component which allows you to leave a meeting or
- end meeting for all, if you have the permission.
+end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLeaveMeeting />;
+	return <RtkLeaveMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLeaveMeeting
-      meeting={meeting}
-    />
-  );
+	return <RtkLeaveMeeting meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
index c460afe367c3aba..f32e008ce30ba45 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkLivestreamIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamIndicator />;
+	return <RtkLivestreamIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkLivestreamIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
index f2825122178db2e..76bcbcc4f131e9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkLivestreamPlayer component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description    |
+| ---------- | ----------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
+| `size`     | `Size1`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamPlayer />;
+	return <RtkLivestreamPlayer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamPlayer
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkLivestreamPlayer meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
index 5a02a6110c65ab6..bbc41afc7185d64 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkLivestreamToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLivestreamToggle />;
+	return <RtkLivestreamToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLivestreamToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkLivestreamToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
index eb4e53ce7220d26..9477a16d30710b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkLogo component (React Library)
 products:
   - realtime
 ---
+
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `logoUrl` | `string` | ✅ | - | Logo URL |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
+import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkLogo />;
+	return <RtkLogo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
+import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkLogo
-      logoUrl="example"
-      meeting={meeting}
-    />
-  );
+	return <RtkLogo logoUrl="example" meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
index b4a60b36bb5affb..55fbf4dd7de4c88 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
@@ -5,37 +5,32 @@ description: API reference for RtkMarkdownView component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
-| `text` | `string` | ✅ | - | raw text to render as markdown |
+| Property    | Type     | Required | Default | Description                              |
+| ----------- | -------- | -------- | ------- | ---------------------------------------- |
+| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
+| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMarkdownView />;
+	return <RtkMarkdownView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMarkdownView
-      maxLength={42}
-      text="example"
-    />
-  );
+	return <RtkMarkdownView maxLength={42} text="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
index 46f187b5651c348..fc2ab8e84fcd5de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
@@ -5,53 +5,53 @@ description: API reference for RtkMeeting component (React Library)
 products:
   - realtime
 ---
+
 A single component which renders an entire meeting UI.
- It loads your preset and renders the UI based on it.
- With this component, you don't have to handle all the states,
- dialogs and other smaller bits of managing the application.
+It loads your preset and renders the UI based on it.
+With this component, you don't have to handle all the states,
+dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
-| `config` | `UIConfig` | ✅ | - | UI Config |
-| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `mode` | `MeetingMode` | ✅ | - | Fill type |
-| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property               | Type          | Required | Default            | Description                                                         |
+| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
+| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
+| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
+| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
+| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
+| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
+| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
+| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
+| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
+| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
+| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
+| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMeeting />;
+	return <RtkMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMeeting
-      applyDesignSystem={true}
-      config={defaultUiConfig}
-      gridLayout={gridlayout1}
-    />
-  );
+	return (
+		<RtkMeeting
+			applyDesignSystem={true}
+			config={defaultUiConfig}
+			gridLayout={gridlayout1}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
index 390e091d34851d8..8e26823a9775b15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkMeetingTitle component (React Library)
 products:
   - realtime
 ---
+
 Displays the title of the meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMeetingTitle />;
+	return <RtkMeetingTitle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMeetingTitle
-      meeting={meeting}
-    />
-  );
+	return <RtkMeetingTitle meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
index 5f5db9ac9f51c5d..9ee83f7cee4ea0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkMenu component (React Library)
 products:
   - realtime
 ---
+
 A menu component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `offset` | `number` | ✅ | - | Offset in px |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property    | Type        | Required | Default           | Description       |
+| ----------- | ----------- | -------- | ----------------- | ----------------- |
+| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
+| `offset`    | `number`    | ✅       | -                 | Offset in px      |
+| `placement` | `Placement` | ✅       | -                 | Placement of menu |
+| `size`      | `Size`      | ✅       | -                 | Size              |
+| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenu />;
+	return <RtkMenu />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenu
-      offset={42}
-      placement={placement}
-      size="md"
-    />
-  );
+	return <RtkMenu offset={42} placement={placement} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
index 07d2090f6869fa5..e3ed88af47b32ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkMenuItem component (React Library)
 products:
   - realtime
 ---
+
 A menu item component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `size`        | `Size`                     | ✅       | -                 | Size        |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenuItem />;
+	return <RtkMenuItem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenuItem
-      menuVariant={'primary' | 'secondary'}
-      size="md"
-    />
-  );
+	return <RtkMenuItem menuVariant={"primary" | "secondary"} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
index 3abcdf3681cf82c..c8535a1fd33ef85 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
@@ -5,39 +5,35 @@ description: API reference for RtkMenuList component (React Library)
 products:
   - realtime
 ---
+
 A menu list component.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                       | Required | Default           | Description |
+| ------------- | -------------------------- | -------- | ----------------- | ----------- |
+| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
+| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMenuList />;
+	return <RtkMenuList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
+import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMenuList
-      menuVariant={'primary' | 'secondary'}
-    />
-  );
+	return <RtkMenuList menuVariant={"primary" | "secondary"} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
index a821d60dd934f37..80a9a91264a8c83 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkMessageView component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
-| `authorName` | `string` | ✅ | - | Author display label |
-| `avatarUrl` | `string` | ✅ | - | Avatar image url |
-| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
-| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
-| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
-| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
-| `messageType` | `Message['type']` | ✅ | - | Type of message |
-| `pinned` | `boolean` | ✅ | - | Is message pinned |
-| `time` | `Date` | ✅ | - | Time when message was sent |
-| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
-| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
+| Property         | Type                       | Required | Default           | Description                             |
+| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
+| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
+| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
+| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
+| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
+| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
+| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
+| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
+| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
+| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
+| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
+| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
+| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
+| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
+| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMessageView />;
+	return <RtkMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMessageView
-      actions={[]}
-      authorName="example"
-      avatarUrl="example"
-    />
-  );
+	return (
+		<RtkMessageView actions={[]} authorName="example" avatarUrl="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
index 8a828fa1df70a57..cc03a1979681184 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkMicToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your microphone.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMicToggle />;
+	return <RtkMicToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMicToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkMicToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
index 7635bf3bc850417..bddd6410870b69d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
@@ -5,51 +5,52 @@ description: API reference for RtkMicrophoneSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMicrophoneSelector />;
+	return <RtkMicrophoneSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMicrophoneSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkMicrophoneSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
index 9797cef0997f626..2a84e600445f8a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
@@ -5,52 +5,46 @@ description: API reference for RtkMixedGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
-| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                  | Type          | Required | Default                 | Description                                             |
+| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
+| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
+| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
+| `states`                  | `States`      | ✅       | -                       | States object                                           |
+| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMixedGrid />;
+	return <RtkMixedGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMixedGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkMixedGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
index 2c8f9d6008454df..ec75917e7d6794f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
@@ -5,44 +5,43 @@ description: API reference for RtkMoreToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of a more menu.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeMoreMenu: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeMoreMenu: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description   |
+| ---------- | ---------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`     | ✅       | -                 | Size          |
+| `states`   | `States`   | ✅       | -                 | States object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMoreToggle />;
+	return <RtkMoreToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMoreToggle
-      size="md"
-    />
-  );
+	return <RtkMoreToggle size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
index 0a61a27b14d57cb..9ff1d6062e97f3a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
@@ -5,41 +5,35 @@ description: API reference for RtkMuteAllButton component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMuteAllButton />;
+	return <RtkMuteAllButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMuteAllButton
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkMuteAllButton meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
index 6964b04a06fce07..de60763a8da782a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkMuteAllConfirmation component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkMuteAllConfirmation />;
+	return <RtkMuteAllConfirmation />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
+import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkMuteAllConfirmation
-      meeting={meeting}
-    />
-  );
+	return <RtkMuteAllConfirmation meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
index 653d3e71c13c219..b24255b2688e80e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkNameTag component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a participant's name.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
+| Property        | Type                | Required | Default           | Description                               |
+| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
+| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
+| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
+| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
+| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
+| `size`          | `Size`              | ✅       | -                 | Size                                      |
+| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
+| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
+import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNameTag />;
+	return <RtkNameTag />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
+import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNameTag
-      isScreenShare={true}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkNameTag
+			isScreenShare={true}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
index cdc9b9d26f6014c..badca357da7d298 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkNetworkIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `participant` | `Peer` | ✅ | - | Participant or Self |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| Property        | Type        | Required | Default           | Description         |
+| --------------- | ----------- | -------- | ----------------- | ------------------- |
+| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
+| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
+| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
+| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
+| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNetworkIndicator />;
+	return <RtkNetworkIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNetworkIndicator
-      isScreenShare={true}
-      meeting={meeting}
-      participant={participant}
-    />
-  );
+	return (
+		<RtkNetworkIndicator
+			isScreenShare={true}
+			meeting={meeting}
+			participant={participant}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
index 011b505c0f96d15..5aecde35407d99b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
@@ -5,45 +5,41 @@ description: API reference for RtkNotification component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a notification.
- You need to remove the element after you receive the
- `rtkNotificationDismiss` event.
+You need to remove the element after you receive the
+`rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `notification` | `Notification` | ✅ | - | Message |
-| `paused` | `boolean` | ✅ | - | Stops timeout when true |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type           | Required | Default           | Description             |
+| -------------- | -------------- | -------- | ----------------- | ----------------------- |
+| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
+| `notification` | `Notification` | ✅       | -                 | Message                 |
+| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
+| `size`         | `Size`         | ✅       | -                 | Size                    |
+| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNotification />;
+	return <RtkNotification />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNotification
-      notification={notification}
-      paused={true}
-      size="md"
-    />
-  );
+	return (
+		<RtkNotification notification={notification} paused={true} size="md" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
index a6479a63c2b3dc3..b4cf3563bdaf55e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
@@ -5,45 +5,40 @@ description: API reference for RtkNotifications component (React Library)
 products:
   - realtime
 ---
+
 A component which handles notifications.
- You can configure which notifications you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which notifications you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkNotifications />;
+	return <RtkNotifications />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
+import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkNotifications
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkNotifications meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
index 075d2ad41e4e7f1..f4a1c236a9e1ff3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
@@ -5,40 +5,36 @@ description: API reference for RtkOverlayModal component (React Library)
 products:
   - realtime
 ---
+
 A confirmation modal.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkOverlayModal />;
+	return <RtkOverlayModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
+import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkOverlayModal
-      meeting={meeting}
-    />
-  );
+	return <RtkOverlayModal meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
index 9c2aa7dd5fa68fa..4efdfe198d33ae2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkPaginatedList component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
-| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
-| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
-| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `pageSize` | `number` | ✅ | - | Page Size |
-| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
-| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
-| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property         | Type                                                   | Required | Default           | Description                                    |
+| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
+| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
+| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
+| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
+| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
+| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
+| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
+| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
+| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
+| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
+| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
+import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPaginatedList />;
+	return <RtkPaginatedList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
+import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPaginatedList
-      autoScroll={true}
-      createNodes={[]}
-      emptyListLabel="example"
-    />
-  );
+	return (
+		<RtkPaginatedList
+			autoScroll={true}
+			createNodes={[]}
+			emptyListLabel="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
index ccc8cb4e191bc51..516579dd9a334b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkParticipant component (React Library)
 products:
   - realtime
 ---
+
 A participant entry component used inside `rtk-participants` which shows data like:
- name, picture and media device status.
- You can perform privileged actions on the participant too.
+name, picture and media device status.
+You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participant` | `Peer` | ✅ | - | Participant object |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
+| Property      | Type                  | Required | Default                 | Description              |
+| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
+| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
+| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
+| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
+| `participant` | `Peer`                | ✅       | -                       | Participant object       |
+| `states`      | `States1`             | ✅       | -                       | States                   |
+| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
+| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipant />;
+	return <RtkParticipant />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipant
-      meeting={meeting}
-      participant={participant}
-      view={participantviewmode}
-    />
-  );
+	return (
+		<RtkParticipant
+			meeting={meeting}
+			participant={participant}
+			view={participantviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
index e8cd175555dcd38..328f0c14986aba0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkParticipantCount component (React Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantCount />;
+	return <RtkParticipantCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantCount
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkParticipantCount meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
index 7606fca272f529b..91ef45fb563d602 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkParticipants component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property                   | Type                | Required | Default                 | Description     |
+| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
+| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
+| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
+| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
+| `size`                     | `Size`              | ✅       | -                       | Size            |
+| `states`                   | `States`            | ✅       | -                       | States object   |
+| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipants />;
+	return <RtkParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipants
-      defaultParticipantsTabId={participantstabid}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return (
+		<RtkParticipants
+			defaultParticipantsTabId={participantstabid}
+			meeting={meeting}
+			size="md"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
index 8ef488005d52a27..b758d16591fc32d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkParticipantsAudio component (React Library)
 products:
   - realtime
 ---
+
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type               | Required | Default           | Description                 |
+| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
+| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
+| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
+| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsAudio />;
+	return <RtkParticipantsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsAudio
-      meeting={meeting}
-      preloadedAudioElem={htmlaudioelement}
-    />
-  );
+	return (
+		<RtkParticipantsAudio
+			meeting={meeting}
+			preloadedAudioElem={htmlaudioelement}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
index b00d785b2acf701..135d60ff19db841 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkParticipantsStageList component (React Library
 products:
   - realtime
 ---
+
 A component which lists all participants, with ability to
- run privileged actions on each participant according to your permissions.
+run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                          |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
+| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
+| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
+| `search`     | `string`               | ✅       | -                       | Search                               |
+| `size`       | `Size`                 | ✅       | -                       | Size                                 |
+| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
+| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsStageList />;
+	return <RtkParticipantsStageList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsStageList
-      hideHeader={true}
-      meeting={meeting}
-      search="example"
-    />
-  );
+	return (
+		<RtkParticipantsStageList
+			hideHeader={true}
+			meeting={meeting}
+			search="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
index 4e41381ce80f30a..8528f80bb052dd6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsStageQueue component (React Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsStageQueue />;
+	return <RtkParticipantsStageQueue />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsStageQueue
-      meeting={meeting}
-      size="md"
-      view={participantsviewmode}
-    />
-  );
+	return (
+		<RtkParticipantsStageQueue
+			meeting={meeting}
+			size="md"
+			view={participantsviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
index 9c8fdaf5ece9fe4..0301d934942ee7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
@@ -5,48 +5,46 @@ description: API reference for RtkParticipantsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of participants.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'participants' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "participants";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsToggle />;
+	return <RtkParticipantsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkParticipantsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
index 2122d23e95a3666..a8153f7ffc87a99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkParticipantsViewerList component (React Librar
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `search` | `string` | ✅ | - | Search |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property     | Type                   | Required | Default                 | Description                     |
+| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
+| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `search`     | `string`               | ✅       | -                       | Search                          |
+| `size`       | `Size1`                | ✅       | -                       | Size                            |
+| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsViewerList />;
+	return <RtkParticipantsViewerList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsViewerList
-      hideHeader={true}
-      meeting={meeting}
-      search="example"
-    />
-  );
+	return (
+		<RtkParticipantsViewerList
+			hideHeader={true}
+			meeting={meeting}
+			search="example"
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
index 3a889887010026a..4649b0bfc0e82fd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsWaitingList component (React Libra
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
+| Property   | Type                   | Required | Default                 | Description                     |
+| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
+| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
+| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
+| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
+| `size`     | `Size1`                | ✅       | -                       | Size                            |
+| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
+| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkParticipantsWaitingList />;
+	return <RtkParticipantsWaitingList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
+import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkParticipantsWaitingList
-      meeting={meeting}
-      size="md"
-      view={participantsviewmode}
-    />
-  );
+	return (
+		<RtkParticipantsWaitingList
+			meeting={meeting}
+			size="md"
+			view={participantsviewmode}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
index 3772370f932a5c4..d775d0fe83a22f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
@@ -5,41 +5,37 @@ description: API reference for RtkPermissionsMessage component (React Library)
 products:
   - realtime
 ---
+
 A component which shows permission related troubleshooting
- information.
+information.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPermissionsMessage />;
+	return <RtkPermissionsMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPermissionsMessage
-      meeting={meeting}
-    />
-  );
+	return <RtkPermissionsMessage meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
index 6ec7ca9cc8718b2..3204dca64827f0c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
@@ -5,37 +5,33 @@ description: API reference for RtkPinnedMessageSelector component (React Library
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPinnedMessageSelector />;
+	return <RtkPinnedMessageSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPinnedMessageSelector
-      meeting={meeting}
-    />
-  );
+	return <RtkPinnedMessageSelector meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
index 2c97be980f7bfe7..7fa13266f256c40 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkPipToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default                 | Description    |
+| ---------- | ------------------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
+| `size`     | `Size1`             | ✅       | -                       | Size           |
+| `states`   | `States1`           | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPipToggle />;
+	return <RtkPipToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPipToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPipToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
index 558894132225b7a..c3e69d48c2363ad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkPluginMain component (React Library)
 products:
   - realtime
 ---
+
 A component which loads a plugin.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting |
-| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type        | Required | Default           | Description |
+| ---------- | ----------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
+| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
+| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
+| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPluginMain />;
+	return <RtkPluginMain />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPluginMain
-      meeting={meeting}
-      plugin={rtkplugin}
-    />
-  );
+	return <RtkPluginMain meeting={meeting} plugin={rtkplugin} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
index 6deb86e4607c003..d965a8cd11d84f3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkPlugins component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins from their preset,
- and ability to enable or disable plugins.
+and ability to enable or disable plugins.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
+import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPlugins />;
+	return <RtkPlugins />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
+import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPlugins
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkPlugins meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
index 68b70c406caf1cc..ea36e607b88f055 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
@@ -5,48 +5,46 @@ description: API reference for RtkPluginsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of plugins.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'plugins' }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "plugins";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPluginsToggle />;
+	return <RtkPluginsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPluginsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPluginsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
index aa4fe6fd115a016..3005624ec80b0f9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
@@ -5,44 +5,40 @@ description: API reference for RtkPoll component (React Library)
 products:
   - realtime
 ---
+
 A poll component.
- Shows a poll where a user can vote.
+Shows a poll where a user can vote.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
-| `poll` | `Poll` | ✅ | - | Poll |
-| `self` | `string` | ✅ | - | Self ID |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type                   | Required | Default           | Description        |
+| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
+| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
+| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
+| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
+| `self`        | `string`               | ✅       | -                 | Self ID            |
+| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
+import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPoll />;
+	return <RtkPoll />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
+import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPoll
-      permissions={rtkpermissionspreset}
-      poll={poll}
-      self="example"
-    />
-  );
+	return (
+		<RtkPoll permissions={rtkpermissionspreset} poll={poll} self="example" />
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
index 83cc1ae5190f3c2..e875461eed40218 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkPollForm component (React Library)
 products:
   - realtime
 ---
+
 A component that lets you create a poll.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPollForm />;
+	return <RtkPollForm />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPollForm
-      iconPack={defaultIconPack}
-      t={rtki18n}
-    />
-  );
+	return <RtkPollForm iconPack={defaultIconPack} t={rtki18n} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
index 4277a2b47bfdace..d6c56afb6b26cca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkPolls component (React Library)
 products:
   - realtime
 ---
+
 A component which lists all available plugins a user can access with
- the ability to enable or disable them as per their permissions.
+the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
+import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPolls />;
+	return <RtkPolls />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
+import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPolls
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkPolls meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
index f50a1cdaceb586b..ce797b91301661d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
@@ -5,49 +5,47 @@ description: API reference for RtkPollsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of polls.
- You need to pass the `meeting` object to it to see the unread polls count badge.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSidebar: boolean; sidebar: 'polls' }
- ```
+You need to pass the `meeting` object to it to see the unread polls count badge.
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSidebar: boolean;
+	sidebar: "polls";
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkPollsToggle />;
+	return <RtkPollsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkPollsToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkPollsToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
index 5c2762db23494d2..80fd74b508c85d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
@@ -5,42 +5,37 @@ description: API reference for RtkRecordingIndicator component (React Library)
 products:
   - realtime
 ---
+
 A component which indicates the recording status of a meeting.
- It will not render anything if no recording is taking place.
+It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkRecordingIndicator />;
+	return <RtkRecordingIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkRecordingIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkRecordingIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
index 0f80e38da1040bc..37ff40da4c4e3e2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
@@ -5,47 +5,41 @@ description: API reference for RtkRecordingToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles recording state of a meeting.
- Only a privileged user can perform this action,
- thus the button will not be visible for participants
- who don't have the permission to record a meeting.
+Only a privileged user can perform this action,
+thus the button will not be visible for participants
+who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `disabled` | `boolean` | ✅ | - | Disable the button |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description        |
+| ---------- | ------------------- | -------- | ----------------- | ------------------ |
+| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
+| `size`     | `Size`              | ✅       | -                 | Size               |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkRecordingToggle />;
+	return <RtkRecordingToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkRecordingToggle
-      disabled={true}
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkRecordingToggle disabled={true} meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
index 52908befd7de5b5..f2af8f3196dc19e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
@@ -5,44 +5,38 @@ description: API reference for RtkScreenShareToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size`              | ✅       | -                 | Size           |
+| `states`   | `States`            | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkScreenShareToggle />;
+	return <RtkScreenShareToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkScreenShareToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkScreenShareToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
index 2b52d0ae178ce6d..71105173b22229f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
@@ -5,43 +5,38 @@ description: API reference for RtkSettings component (React Library)
 products:
   - realtime
 ---
+
 A settings component to see and change your audio/video devices
- as well as see your connection quality.
+as well as see your connection quality.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettings />;
+	return <RtkSettings />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettings
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettings meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
index 81dfd8b2b09dd43..3519e84e54fc498 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkSettingsAudio component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsAudio />;
+	return <RtkSettingsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsAudio
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettingsAudio meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
index be09e3aaa6d7c96..d3a027941137787 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
@@ -5,46 +5,44 @@ description: API reference for RtkSettingsToggle component (React Library)
 products:
   - realtime
 ---
+
 A button which toggles visibility of settings module.
- When clicked it emits a `rtkStateUpdate` event with the data:
- ```ts
- { activeSettings: boolean; }
- ```
+When clicked it emits a `rtkStateUpdate` event with the data:
+
+```ts
+{
+	activeSettings: boolean;
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description   |
+| ---------- | ------------------- | -------- | ----------------- | ------------- |
+| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
+| `size`     | `Size`              | ✅       | -                 | Size          |
+| `states`   | `States`            | ✅       | -                 | States object |
+| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsToggle />;
+	return <RtkSettingsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsToggle
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkSettingsToggle size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
index e8ecedcb858f5f0..004752677fc71bb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
@@ -5,50 +5,46 @@ description: API reference for RtkSettingsVideo component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your camera devices and your video preferences.
- Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
- ```ts
- {
-  prefs: {
-    mirrorVideo: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+
+```ts
+{
+	prefs: {
+		mirrorVideo: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size`     | ✅       | -                 | Size           |
+| `states`   | `States`   | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSettingsVideo />;
+	return <RtkSettingsVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
+import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSettingsVideo
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSettingsVideo meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
index b7d2b949edf7209..9425271184560e0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
@@ -5,44 +5,39 @@ description: API reference for RtkSetupScreen component (React Library)
 products:
   - realtime
 ---
+
 A screen shown before joining the meeting, where you can edit your display name,
- and media settings.
+and media settings.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `size`     | `Size`     | ✅       | -                       | Size           |
+| `states`   | `States`   | ✅       | -                       | States object  |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSetupScreen />;
+	return <RtkSetupScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSetupScreen
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSetupScreen meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
index 1304726dd69f9a7..a911ce5c3815222 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkSidebar component (React Library)
 products:
   - realtime
 ---
+
 A component which handles the sidebar and
- you can customize which sections you want, and which section you want as the default.
+you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
-| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `view` | `RtkSidebarView` | ✅ | - | View type |
+| Property          | Type                | Required | Default                 | Description                 |
+| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
+| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
+| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
+| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
+| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
+| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
+| `size`            | `Size`              | ✅       | -                       | Size                        |
+| `states`          | `States`            | ✅       | -                       | States object               |
+| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
+| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSidebar />;
+	return <RtkSidebar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSidebar
-      defaultSection={rtksidebarsection}
-      enabledSections={[]}
-      meeting={meeting}
-    />
-  );
+	return (
+		<RtkSidebar
+			defaultSection={rtksidebarsection}
+			enabledSections={[]}
+			meeting={meeting}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
index 01b17c6dd9ffc5a..476c5b291b984ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkSidebarUi component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `currentTab` | `string` | ✅ | - | Default tab to open |
-| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
-| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
-| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
-| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
-| `view` | `RtkSidebarView1` | ✅ | - | View |
+| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
+| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
+| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
+| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
+| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
+| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
+| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
+| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
+| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSidebarUi />;
+	return <RtkSidebarUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
+import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSidebarUi
-      currentTab="example"
-      focusCloseButton={true}
-      hideCloseAction={true}
-    />
-  );
+	return (
+		<RtkSidebarUi
+			currentTab="example"
+			focusCloseButton={true}
+			hideCloseAction={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
index 1a39406c2ae6fc3..000057d63bf902c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
@@ -5,47 +5,41 @@ description: API reference for RtkSimpleGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property       | Type       | Required | Default                 | Description                                             |
+| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
+| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
+| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
+| `size`         | `Size`     | ✅       | -                       | Size                                                    |
+| `states`       | `States`   | ✅       | -                       | States object                                           |
+| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSimpleGrid />;
+	return <RtkSimpleGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSimpleGrid
-      aspectRatio="example"
-      gap={42}
-      meeting={meeting}
-    />
-  );
+	return <RtkSimpleGrid aspectRatio="example" gap={42} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
index ef6967aefdd7575..04e2e6cc9985238 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
@@ -5,52 +5,53 @@ description: API reference for RtkSpeakerSelector component (React Library)
 products:
   - realtime
 ---
+
 A component which lets to manage your audio devices and audio preferences.
- Emits `rtkStateUpdate` event with data for muting notification sounds:
- ```ts
- {
-  prefs: {
-    muteNotificationSounds: boolean
-  }
- }
- ```
+Emits `rtkStateUpdate` event with data for muting notification sounds:
+
+```ts
+{
+	prefs: {
+		muteNotificationSounds: boolean;
+	}
+}
+```
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
+| Property   | Type                 | Required | Default           | Description    |
+| ---------- | -------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
+| `size`     | `Size`               | ✅       | -                 | Size           |
+| `states`   | `States`             | ✅       | -                 | States object  |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpeakerSelector />;
+	return <RtkSpeakerSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpeakerSelector
-      meeting={meeting}
-      size="md"
-      variant={'full' | 'inline'}
-    />
-  );
+	return (
+		<RtkSpeakerSelector
+			meeting={meeting}
+			size="md"
+			variant={"full" | "inline"}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
index f465d60658ede2a..28454314a99f114 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkSpinner component (React Library)
 products:
   - realtime
 ---
+
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `size` | `Size1` | ✅ | - | Size |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `size`     | `Size1`    | ✅       | -                 | Size        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpinner />;
+	return <RtkSpinner />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpinner
-      size="md"
-    />
-  );
+	return <RtkSpinner size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
index 0bf9ca54bc892c6..78418e203326306 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
@@ -5,53 +5,48 @@ description: API reference for RtkSpotlightGrid component (React Library)
 products:
   - realtime
 ---
+
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
- You can customize the layout to a `column` view, by default is is `row`.
- - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
- - Participants from `participants[]` array are rendered in a smaller grid.
+You can customize the layout to a `column` view, by default is is `row`.
+
+- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+- Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `gap` | `number` | ✅ | - | Gap between participant tiles |
-| `gridSize` | `GridSize1` | ✅ | - | Grid size |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `participants` | `Peer[]` | ✅ | - | Participants |
-| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property             | Type          | Required | Default                 | Description                                             |
+| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
+| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
+| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
+| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
+| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
+| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
+| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
+| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
+| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
+| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
+| `size`               | `Size`        | ✅       | -                       | Size                                                    |
+| `states`             | `States`      | ✅       | -                       | States object                                           |
+| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpotlightGrid />;
+	return <RtkSpotlightGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpotlightGrid
-      aspectRatio="example"
-      gap={42}
-      gridSize="md"
-    />
-  );
+	return <RtkSpotlightGrid aspectRatio="example" gap={42} gridSize="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
index 6b3cf9e708c5b27..4777d387761bd9c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkSpotlightIndicator component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description    |
+| ---------- | ---------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
+| `size`     | `Size1`    | ✅       | -                 | Size           |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSpotlightIndicator />;
+	return <RtkSpotlightIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
+import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSpotlightIndicator
-      meeting={meeting}
-      size="md"
-    />
-  );
+	return <RtkSpotlightIndicator meeting={meeting} size="md" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
index 2d45d987a733a92..317f51dde0bca13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
@@ -5,40 +5,35 @@ description: API reference for RtkStage component (React Library)
 products:
   - realtime
 ---
+
 A component used as a stage that commonly houses
- the `grid` and `sidebar` components.
+the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description |
+| ---------- | ---------- | -------- | ----------------- | ----------- |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkStage />;
+	return <RtkStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStage } from '@cloudflare/realtimekit-react-ui';
+import { RtkStage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkStage
-      iconPack={defaultIconPack}
-      t={rtki18n}
-    />
-  );
+	return <RtkStage iconPack={defaultIconPack} t={rtki18n} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
index cb4ca66a237f1fe..348c55faae4ad7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
@@ -5,42 +5,36 @@ description: API reference for RtkStageToggle component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size1` | ✅ | - | Size |
-| `states` | `States1` | ✅ | - | States |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
-| `variant` | `ControlBarVariant` | ✅ | - | Variant |
+| Property   | Type                | Required | Default           | Description    |
+| ---------- | ------------------- | -------- | ----------------- | -------------- |
+| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
+| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
+| `size`     | `Size1`             | ✅       | -                 | Size           |
+| `states`   | `States1`           | ✅       | -                 | States         |
+| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
+| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkStageToggle />;
+	return <RtkStageToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
+import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkStageToggle
-      meeting={meeting}
-      size="md"
-      variant="button"
-    />
-  );
+	return <RtkStageToggle meeting={meeting} size="md" variant="button" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
index 45b7bebc4f42df5..d70d8ba438e9132 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
@@ -5,43 +5,37 @@ description: API reference for RtkSwitch component (React Library)
 products:
   - realtime
 ---
+
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
-| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default           | Description                           |
+| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
+| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
+| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
+| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
+import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkSwitch />;
+	return <RtkSwitch />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
+import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkSwitch
-      checked={true}
-      disabled={true}
-      readonly={true}
-    />
-  );
+	return <RtkSwitch checked={true} disabled={true} readonly={true} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
index 4b92e54781696ee..d425e9836824989 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkTabBar component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `activeTab` | `Tab` | ✅ | - | Active tab |
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
-| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `size` | `Size` | ✅ | - | Size |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `tabs` | `Tab[]` | ✅ | - | Tabs |
+| Property    | Type          | Required | Default                 | Description    |
+| ----------- | ------------- | -------- | ----------------------- | -------------- |
+| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
+| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
+| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
+| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
+| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
+| `size`      | `Size`        | ✅       | -                       | Size           |
+| `states`    | `States`      | ✅       | -                       | States object  |
+| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
+| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
+import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTabBar />;
+	return <RtkTabBar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
+import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTabBar
-      activeTab={tab}
-      layout={gridlayout1}
-      meeting={meeting}
-    />
-  );
+	return <RtkTabBar activeTab={tab} layout={gridlayout1} meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
index b13d5561c20349b..275064c3a0e30cf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
@@ -5,45 +5,39 @@ description: API reference for RtkTextMessage component (React Library)
 products:
   - realtime
 ---
+
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
- A component which renders a text message from chat.
+A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
-| `message` | `TextMessage` | ✅ | - | Text message object |
-| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
-| `showBubble` | `boolean` | ✅ | - | show message in bubble |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property      | Type          | Required | Default           | Description                                             |
+| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
+| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
+| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
+| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
+| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
+| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
+| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTextMessage />;
+	return <RtkTextMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTextMessage
-      isContinued={true}
-      message={textmessage}
-      now={date}
-    />
-  );
+	return <RtkTextMessage isContinued={true} message={textmessage} now={date} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
index 181ebc339cd53d8..05911d805ffcb0f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
@@ -5,39 +5,34 @@ description: API reference for RtkTextMessageView component (React Library)
 products:
   - realtime
 ---
+
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
-| `text` | `string` | ✅ | - | Text message |
+| Property     | Type      | Required | Default | Description                               |
+| ------------ | --------- | -------- | ------- | ----------------------------------------- |
+| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
+| `text`       | `string`  | ✅       | -       | Text message                              |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTextMessageView />;
+	return <RtkTextMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
+import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTextMessageView
-      isMarkdown={true}
-      text="example"
-    />
-  );
+	return <RtkTextMessageView isMarkdown={true} text="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
index d2bfb5b64eb3958..c1621ec9cec5946 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
@@ -5,46 +5,40 @@ description: API reference for RtkTooltip component (React Library)
 products:
   - realtime
 ---
+
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
-| `disabled` | `boolean` | ✅ | - | Disabled |
-| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
-| `label` | `string` | ✅ | - | Tooltip label |
-| `open` | `boolean` | ✅ | - | Open |
-| `placement` | `Placement` | ✅ | - | Placement of menu |
-| `size` | `Size` | ✅ | - | Size |
-| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
+| Property    | Type             | Required | Default | Description                      |
+| ----------- | ---------------- | -------- | ------- | -------------------------------- |
+| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
+| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
+| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
+| `label`     | `string`         | ✅       | -       | Tooltip label                    |
+| `open`      | `boolean`        | ✅       | -       | Open                             |
+| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
+| `size`      | `Size`           | ✅       | -       | Size                             |
+| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTooltip />;
+	return <RtkTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
+import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTooltip
-      delay={42}
-      disabled={true}
-      kind={tooltipkind}
-    />
-  );
+	return <RtkTooltip delay={42} disabled={true} kind={tooltipkind} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
index de37a7083168217..bbcf034ad560898 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkTranscript component (React Library)
 products:
   - realtime
 ---
+
 A component which shows a transcript.
- You need to remove the element after you receive the
- `rtkTranscriptDismiss` event.
+You need to remove the element after you receive the
+`rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
+| Property     | Type                                   | Required | Default         | Description |
+| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
+| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTranscript />;
+	return <RtkTranscript />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTranscript
-      t={rtki18n}
-      transcript="example"
-    />
-  );
+	return <RtkTranscript t={rtki18n} transcript="example" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
index f0c0d8559cc445a..42bf35aa1892a1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
@@ -5,42 +5,38 @@ description: API reference for RtkTranscripts component (React Library)
 products:
   - realtime
 ---
+
 A component which handles transcripts.
- You can configure which transcripts you want to see and which ones you want to hear.
- There are also certain limits which you can set as well.
+You can configure which transcripts you want to see and which ones you want to hear.
+There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `states` | `States` | ✅ | - | States object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property  | Type       | Required | Default                 | Description    |
+| --------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
+| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
+| `states`  | `States`   | ✅       | -                       | States object  |
+| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkTranscripts />;
+	return <RtkTranscripts />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
+import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkTranscripts
-      meeting={meeting}
-    />
-  );
+	return <RtkTranscripts meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
index ae022070d0bc868..539123ffabfd8ae 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkUiProvider component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig1` | ✅ | - | Config |
-| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
-| `mode` | `MeetingMode1` | ✅ | - | Fill type |
-| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
-| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
-| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
+| Property          | Type              | Required | Default            | Description                         |
+| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
+| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
+| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
+| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
+| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
+| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
+| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
+| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
+import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkUiProvider />;
+	return <RtkUiProvider />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
+import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkUiProvider
-      config={defaultUiConfig}
-      mode={meeting}
-      showSetupScreen={true}
-    />
-  );
+	return (
+		<RtkUiProvider
+			config={defaultUiConfig}
+			mode={meeting}
+			showSetupScreen={true}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
index 6cd926ddcacf256..1ba972a480e5bf9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
@@ -5,41 +5,36 @@ description: API reference for RtkViewerCount component (React Library)
 products:
   - realtime
 ---
+
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
-| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
+| Property   | Type                 | Required | Default           | Description          |
+| ---------- | -------------------- | -------- | ----------------- | -------------------- |
+| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
+| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
+| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
+| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkViewerCount />;
+	return <RtkViewerCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
+import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkViewerCount
-      meeting={meeting}
-      variant="primary"
-    />
-  );
+	return <RtkViewerCount meeting={meeting} variant="primary" />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
index 5357ad00b4bb2f2..a0e877a59bc623a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkVirtualizedParticipantList component (React Li
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
-| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
-| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
-| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
-| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
+| Property             | Type                           | Required | Default | Description                                              |
+| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
+| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
+| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
+| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
+| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
+| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
+import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkVirtualizedParticipantList />;
+	return <RtkVirtualizedParticipantList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
+import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkVirtualizedParticipantList
-      bufferedItemsCount={42}
-      emptyListElement={htmlelement}
-      itemHeight={42}
-    />
-  );
+	return (
+		<RtkVirtualizedParticipantList
+			bufferedItemsCount={42}
+			emptyListElement={htmlelement}
+			itemHeight={42}
+		/>
+	);
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
index 7a88d11a1ddcc8e..80ab41447906b03 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
@@ -5,38 +5,34 @@ description: API reference for RtkWaitingScreen component (React Library)
 products:
   - realtime
 ---
+
 ## Properties
 
-| Property | Type | Required | Default | Description |
-|----------|------|----------|---------|-------------|
-| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
-| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
-| `meeting` | `Meeting` | ✅ | - | Meeting object |
-| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| Property   | Type       | Required | Default                 | Description    |
+| ---------- | ---------- | -------- | ----------------------- | -------------- |
+| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
+| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
+| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
+| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return <RtkWaitingScreen />;
+	return <RtkWaitingScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
+import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
 
 function MyComponent() {
-  return (
-    <RtkWaitingScreen
-      meeting={meeting}
-    />
-  );
+	return <RtkWaitingScreen meeting={meeting} />;
 }
 ```
-
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
index e278b3204222b09..484d77e089e0389 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
\ No newline at end of file
+---
diff --git a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
index 167875d1b34c213..97583e8bcbbb2dc 100644
--- a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
+++ b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-import { Aside } from "~/components"
+import { Aside } from "~/components";
 
 ## Cloudflare Realtime vs. Traditional SFUs
 
@@ -31,7 +31,10 @@ Cloudflare Realtime addresses these limitations by leveraging Cloudflare's globa
 - **Decentralized Architecture:** There are no dedicated servers for Realtime. Every server within Cloudflare's network contributes to handling Realtime, ensuring scalability and reliability. This approach mirrors the distributed nature of Cloudflare's products such as 1.1.1.1 DNS or Cloudflare's CDN.
 
 <Aside type="tip">
-**See it in action:** Explore our [interactive Global SFU visualization](https://realtime-sfu.dev-demos.workers.dev) to see how participants connect to their nearest Cloudflare datacenter and how media flows across the global backbone.
+	**See it in action:** Explore our [interactive Global SFU
+	visualization](https://realtime-sfu.dev-demos.workers.dev) to see how
+	participants connect to their nearest Cloudflare datacenter and how media
+	flows across the global backbone.
 </Aside>
 
 ## How Cloudflare Realtime Works
diff --git a/src/content/docs/realtime/sfu/changelog.mdx b/src/content/docs/realtime/sfu/changelog.mdx
index e41f539ea385e1c..1c9d09e442ea9d3 100644
--- a/src/content/docs/realtime/sfu/changelog.mdx
+++ b/src/content/docs/realtime/sfu/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/realtime.yaml. --> */}
 
-<ProductReleaseNotes />
\ No newline at end of file
+<ProductReleaseNotes />
diff --git a/src/content/docs/realtime/sfu/datachannels.mdx b/src/content/docs/realtime/sfu/datachannels.mdx
index fb486465f76084c..f60c593ca262bb6 100644
--- a/src/content/docs/realtime/sfu/datachannels.mdx
+++ b/src/content/docs/realtime/sfu/datachannels.mdx
@@ -22,7 +22,7 @@ DataChannels on Cloudflare Realtime can scale up to many subscribers per publish
 
 ### How to use DataChannels
 
-1. Create  two Realtime sessions, one for the publisher and one for the subscribers.
+1. Create two Realtime sessions, one for the publisher and one for the subscribers.
 2. Create a DataChannel by calling /datachannels/new with the location set to "local" and the dataChannelName set to the name of the DataChannel.
 3. Create a DataChannel by calling /datachannels/new with the location set to "remote" and the sessionId set to the sessionId of the publisher.
 4. Use the DataChannel to send data from the publisher to the subscribers.
diff --git a/src/content/docs/realtime/sfu/get-started.mdx b/src/content/docs/realtime/sfu/get-started.mdx
index c629ade1a9f321c..43ee74f34fe8975 100644
--- a/src/content/docs/realtime/sfu/get-started.mdx
+++ b/src/content/docs/realtime/sfu/get-started.mdx
@@ -10,10 +10,8 @@ products:
 
 :::note[Before you get started:]
 
-
 You must first [create a Cloudflare account](/fundamentals/account/create-account/).
 
-
 :::
 
 ## Create your first app
@@ -21,7 +19,7 @@ You must first [create a Cloudflare account](/fundamentals/account/create-accoun
 Every Realtime App is a separate environment, so you can make one for development, staging and production versions for your product.
 Either using [Dashboard](https://dash.cloudflare.com/?to=/:account/realtime/sfu), or the [API](/api/resources/calls/subresources/sfu/methods/create/) create a Realtime App. When you create a Realtime App, you will get:
 
-* App ID
-* App Secret
+- App ID
+- App Secret
 
 These two combined will allow you to make API Realtime from your backend server to Realtime.
diff --git a/src/content/docs/realtime/sfu/limits.mdx b/src/content/docs/realtime/sfu/limits.mdx
index b68859142236802..df32c721be0f051 100644
--- a/src/content/docs/realtime/sfu/limits.mdx
+++ b/src/content/docs/realtime/sfu/limits.mdx
@@ -12,28 +12,28 @@ Understanding the limits and timeouts of Cloudflare Realtime is crucial for opti
 
 ## Free
 
-* Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
-* Data transfer from your client to Cloudflare is always free of charge.
+- Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
+- Data transfer from your client to Cloudflare is always free of charge.
 
 ## Limits
 
-* **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
+- **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
 
-* **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
+- **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
 
-* **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
+- **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
 
 ## Inactivity Timeout
 
-* **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
+- **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
 
 ## PeerConnection Requirements
 
-* **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
+- **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
 
 ## Handling Connectivity Issues
 
-* **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
+- **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
 
 Adhering to these limits and understanding the timeout behaviors will help ensure that your applications remain responsive and stable while providing a seamless user experience.
 
@@ -43,19 +43,18 @@ Cloudflare Realtime supports the following codecs:
 
 ### Supported video codecs
 
-* **H264**
-* **H265**
-* **VP8**
-* **VP9**
-* **AV1**
+- **H264**
+- **H265**
+- **VP8**
+- **VP9**
+- **AV1**
 
 ### Supported audio codecs
 
-* **Opus**
-* **G.711 PCM (A-law)**
-* **G.711 PCM (µ-law)**
+- **Opus**
+- **G.711 PCM (A-law)**
+- **G.711 PCM (µ-law)**
 
 :::note
 For external 48kHz PCM support refer to the [WebSocket adapter](/realtime/sfu/media-transport-adapters/websocket-adapter/)
 :::
-
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
index a9a0f3df0ddbf5b..2edd1740c70cb39 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
@@ -47,6 +47,7 @@ graph LR
 **Adapter instance**: Each connection creates a unique instance with an `adapterId` to manage its lifecycle.
 
 **Location types**:
+
 - `local` (Ingest): Receives media from external endpoints to create new WebRTC tracks
 - `remote` (Stream): Sends media from existing WebRTC tracks to external endpoints
 
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
index ea922e873043cc4..818a1d69f4a3779 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
@@ -206,11 +206,11 @@ POST /v1/apps/{appId}/adapters/websocket/close
 
 ```json
 {
-  "tracks": [
-    {
-      "adapterId": "string"
-    }
-  ]
+	"tracks": [
+		{
+			"adapterId": "string"
+		}
+	]
 }
 ```
 
@@ -242,6 +242,7 @@ message Packet {
 **Ingest mode (buffer)**: Only the `payload` field is used, containing chunks of audio data.
 
 **Stream mode (egress)**:
+
 - For audio frames:
   - `sequenceNumber`: Incremental packet counter
   - `timestamp`: Timestamp for synchronization
@@ -267,12 +268,14 @@ Connects to your WebSocket endpoint:
 ### Message format
 
 #### Buffer mode (ingest)
+
 - **Binary messages**: PCM audio data in chunks
 - **Maximum message size**: 32 KB per WebSocket message
 - **Important**: Account for serialization overhead when chunking audio buffers
 - Send audio in small, frequent chunks rather than large batches
 
-#### Stream mode (egress)  
+#### Stream mode (egress)
+
 - **Binary messages**: Individual frames with metadata (audio or video)
 - Audio frames include:
   - Timestamp information
@@ -330,11 +333,11 @@ Usage counts towards your Cloudflare Realtime free tier of 1,000 GB.
 
 ## Error handling
 
-| Error Code | Description |
-|------------|-------------|
-| `400` | Invalid request parameters |
-| `404` | Session or track not found |
-| `503` | Adapter not found (for close operations) |
+| Error Code | Description                              |
+| ---------- | ---------------------------------------- |
+| `400`      | Invalid request parameters               |
+| `404`      | Session or track not found               |
+| `503`      | Adapter not found (for close operations) |
 
 ## Reference implementations
 
diff --git a/src/content/docs/realtime/sfu/sessions-tracks.mdx b/src/content/docs/realtime/sfu/sessions-tracks.mdx
index 0acfcba0d460671..8f88a1a807fd435 100644
--- a/src/content/docs/realtime/sfu/sessions-tracks.mdx
+++ b/src/content/docs/realtime/sfu/sessions-tracks.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**,  **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
+Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**, **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
 
 ## Application
 
@@ -18,17 +18,17 @@ A Realtime Application is an environment within different Sessions and Tracks ca
 
 A **Session** in Cloudflare Realtime correlates directly to a WebRTC PeerConnection. It represents the establishment of a communication channel between a client and the nearest Cloudflare data center, as determined by Cloudflare's anycast routing. Typically, a client will maintain a single Session, encompassing all communications between the client and Cloudflare.
 
-* **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
-* **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
-* **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
+- **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
+- **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
+- **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
 
 ## Tracks
 
 Within a Session, there can be one or more **Tracks**.
 
-* **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
-* **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
-* **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
+- **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
+- **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
+- **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
 
 ## Realtime as a Programmable "Switchboard"
 
@@ -38,9 +38,9 @@ The analogy of a switchboard is apt for understanding Realtime. Historically, sw
 
 While many SFUs utilize concepts like "rooms" to manage media streams among users, this approach has scalability and flexibility limitations. Cloudflare Realtime opts for a more granular and flexible model with Sessions and Tracks, enabling a wide range of use cases:
 
-* Large-scale remote events, like 'fireside chats' with thousands of participants.
-* Interactive conversations with the ability to bring audience members "on stage."
-* Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
+- Large-scale remote events, like 'fireside chats' with thousands of participants.
+- Interactive conversations with the ability to bring audience members "on stage."
+- Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
 
 ### Presence Protocol vs. Media Flow
 
diff --git a/src/content/docs/realtime/turn/custom-domains.mdx b/src/content/docs/realtime/turn/custom-domains.mdx
index 9103a2e08eaf8a9..16baeeb56029ffa 100644
--- a/src/content/docs/realtime/turn/custom-domains.mdx
+++ b/src/content/docs/realtime/turn/custom-domains.mdx
@@ -12,9 +12,9 @@ Cloudflare Realtime TURN service supports using custom domains for UDP, and TCP
 
 | Protocol      | Custom domains | Primary port | Alternate port |
 | ------------- | -------------- | ------------ | -------------- |
-| STUN over UDP | ✅              | 3478/udp     | 53/udp         |
-| TURN over UDP | ✅              | 3478/udp     | 53 udp         |
-| TURN over TCP | ✅              | 3478/tcp     | 80/tcp         |
+| STUN over UDP | ✅             | 3478/udp     | 53/udp         |
+| TURN over UDP | ✅             | 3478/udp     | 53 udp         |
+| TURN over TCP | ✅             | 3478/tcp     | 80/tcp         |
 | TURN over TLS | No             | 5349/tcp     | 443/tcp        |
 
 ## Setting up a CNAME record
@@ -23,20 +23,16 @@ To use custom domains for TURN, you must create a CNAME DNS record pointing to `
 
 :::caution
 
-
 Do not resolve the address of `turn.cloudflare.com` or `stun.cloudflare.com` or use an IP address as the value you input to your DNS record. Only CNAME records are supported.
 
-
 :::
 
 Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for custom domains.
 
 :::note
 
-
 If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
-
 :::
 
 There is no additional charge to using a custom hostname with Cloudflare Realtime TURN.
diff --git a/src/content/docs/realtime/turn/generate-credentials.mdx b/src/content/docs/realtime/turn/generate-credentials.mdx
index bbb75c2c0e043bf..3f1c3bf4bf971ac 100644
--- a/src/content/docs/realtime/turn/generate-credentials.mdx
+++ b/src/content/docs/realtime/turn/generate-credentials.mdx
@@ -18,8 +18,8 @@ You should keep your TURN key on the server side (don't share it with the browse
 
 With a TURN key you can:
 
-* Generate TURN credentials that expire
-* Revoke previously issued TURN credentials
+- Generate TURN credentials that expire
+- Revoke previously issued TURN credentials
 
 ## Create credentials
 
@@ -36,12 +36,9 @@ The **201 (Created)** response below can then be passed on to your front-end app
 
 ```json
 {
-  "iceServers": [
+	"iceServers": [
 		{
-			"urls": [
-				"stun:stun.cloudflare.com:3478",
-				"stun:stun.cloudflare.com:53"
-			]
+			"urls": ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"]
 		},
 		{
 			"urls": [
@@ -67,12 +64,9 @@ Use `iceServers` as follows when instantiating the `RTCPeerConnection`:
 
 ```js
 const myPeerConnection = new RTCPeerConnection({
-  iceServers: [
-    {
-      urls: [
-				"stun:stun.cloudflare.com:3478",
-				"stun:stun.cloudflare.com:53"
-			]
+	iceServers: [
+		{
+			urls: ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"],
 		},
 		{
 			urls: [
@@ -81,14 +75,15 @@ const myPeerConnection = new RTCPeerConnection({
 				"turn:turn.cloudflare.com:3478?transport=tcp",
 				"turn:turn.cloudflare.com:80?transport=tcp",
 				"turns:turn.cloudflare.com:5349?transport=tcp",
-				"turns:turn.cloudflare.com:443?transport=tcp"
-      ],
-			"username": "bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
-			"credential": "ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0"
-    },
-  ],
+				"turns:turn.cloudflare.com:443?transport=tcp",
+			],
+			username:
+				"bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
+			credential:
+				"ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0",
+		},
+	],
 });
-
 ```
 
 The `ttl` value can be adjusted to expire the short lived key in a certain amount of time. This value should be larger than the time you'd expect the users to use the TURN service. For example, if you're using TURN for a video conferencing app, the value should be set to the longest video call you'd expect to happen in the app.
diff --git a/src/content/docs/realtime/turn/replacing-existing.mdx b/src/content/docs/realtime/turn/replacing-existing.mdx
index 2ed8f3af74ea916..7fdfd0d0da1642f 100644
--- a/src/content/docs/realtime/turn/replacing-existing.mdx
+++ b/src/content/docs/realtime/turn/replacing-existing.mdx
@@ -14,12 +14,12 @@ If you are a existing TURN provider but would like to switch to providing Cloudf
 
 Cloudflare Realtime TURN service can reduce tangible and untangible costs associated with TURN servers:
 
-* Server costs (AWS EC2 etc)
-* Bandwidth costs (Egress, load balancing etc)
-* Time and effort to set up a TURN process and maintenance of server
-* Scaling the servers up and down
-* Maintain the TURN server with security and feature updates
-* Maintain high availability
+- Server costs (AWS EC2 etc)
+- Bandwidth costs (Egress, load balancing etc)
+- Time and effort to set up a TURN process and maintenance of server
+- Scaling the servers up and down
+- Maintain the TURN server with security and feature updates
+- Maintain high availability
 
 ## Recommendations
 
@@ -56,8 +56,8 @@ When billing for TURN usage in your application, it's crucial to understand and
 
 The sampling process in TURN analytics works on two levels:
 
-* At data collection: Usage data points may be sampled if they are generated too quickly.
-* At query time: Additional sampling may occur if the query is too complex or covers a large time range.
+- At data collection: Usage data points may be sampled if they are generated too quickly.
+- At query time: Additional sampling may occur if the query is too complex or covers a large time range.
 
 To ensure accurate billing, write a single query that sums TURN usage per customer per time period, returning a single value. Avoid using queries that list usage for multiple customers simultaneously.
 
@@ -65,20 +65,16 @@ By following these guidelines and understanding how TURN analytics handles sampl
 
 :::note
 
-
 Cloudflare Realtime only bills for traffic from Cloudflare's servers to your client, called `egressBytes`.
 
-
 :::
 
 ### Example queries
 
 :::caution[Incorrect approach example]
 
-
 Querying TURN usage for multiple customers in a single query can lead to inaccurate results. This is because the usage pattern of one customer could affect the sampling rate applied to another customer's data, potentially skewing the results.
 
-
 :::
 
 ```
diff --git a/src/content/docs/realtime/turn/rfc-matrix.mdx b/src/content/docs/realtime/turn/rfc-matrix.mdx
index 88bffe6390fe56f..b2a69b56b7450d0 100644
--- a/src/content/docs/realtime/turn/rfc-matrix.mdx
+++ b/src/content/docs/realtime/turn/rfc-matrix.mdx
@@ -12,23 +12,23 @@ products:
 
 | Protocol | Support | Relevant specification                                                                                    |
 | -------- | ------- | --------------------------------------------------------------------------------------------------------- |
-| UDP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TCP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TLS      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| UDP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TCP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TLS      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
 | DTLS     | No      | [draft-petithuguenin-tram-turn-dtls-00](http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00) |
 
 ## TURN client to TURN server protocols
 
-| Protocol                                        | Support                                                                                                                        | Relevant specification                                                                                               |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
-| TURN (base RFC)                                 | ✅                                                                                                                              | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
+| Protocol                                        | Support                                                                                                                               | Relevant specification                                                                                               |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| TURN (base RFC)                                 | ✅                                                                                                                                    | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
 | TURN REST API                                   | ✅ (See [FAQ](/realtime/turn/faq/#does-cloudflare-realtime-turn-support-the-expired-ietf-rfc-draft-draft-uberti-behave-turn-rest-00)) | [draft-uberti-behave-turn-rest-00](http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)                      |
-| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                              | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
-| ALPN support for STUN & TURN                    | ✅                                                                                                                              | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
-| TURN Bandwidth draft specs                      | No                                                                                                                             | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
-| TURN-bis (with dual allocation) draft specs     | No                                                                                                                             | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
-| TCP relaying TURN extension                     | No                                                                                                                             | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
-| IPv6 extension for TURN                         | No                                                                                                                             | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
-| oAuth third-party TURN/STUN authorization       | No                                                                                                                             | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
-| DTLS support (for TURN)                         | No                                                                                                                             | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
-| Mobile ICE (MICE) support                       | No                                                                                                                             | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
+| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                                    | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
+| ALPN support for STUN & TURN                    | ✅                                                                                                                                    | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
+| TURN Bandwidth draft specs                      | No                                                                                                                                    | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
+| TURN-bis (with dual allocation) draft specs     | No                                                                                                                                    | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
+| TCP relaying TURN extension                     | No                                                                                                                                    | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
+| IPv6 extension for TURN                         | No                                                                                                                                    | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
+| oAuth third-party TURN/STUN authorization       | No                                                                                                                                    | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
+| DTLS support (for TURN)                         | No                                                                                                                                    | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
+| Mobile ICE (MICE) support                       | No                                                                                                                                    | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx
index 737fee4c2b7c58b..22b77e10e9ae65d 100644
--- a/src/content/docs/reference-architecture/architectures/sase.mdx
+++ b/src/content/docs/reference-architecture/architectures/sase.mdx
@@ -318,13 +318,13 @@ Organizations may also connect their network locations directly to the Cloudflar
 
 The following table summarizes the different methods of connecting networks to Cloudflare:
 
-| **Use case**                                                                                                                                           | **Recommended**                             | **Alternative solution**                                                                                      |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)**  | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment                           |
-| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                          | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
-| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                          | **N/A**                                                                                                       |
-| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh** | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required                              |
-| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh** | **N/A**                                                                                                       |
+| **Use case**                                                                                                                                           | **Recommended**                            | **Alternative solution**                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------- |
+| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)** | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment   |
+| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                         | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
+| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                         | **N/A**                                                                               |
+| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh**                        | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required      |
+| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh**                        | **N/A**                                                                               |
 
 Each of these methods of connecting and routing traffic can be deployed concurrently from any location. The following diagram highlights how different connectivity methods can be used in a single architecture.
 
@@ -343,8 +343,8 @@ Note the following traffic flows:
 _Note: Labels in this image may reflect a previous product name._
 
 <sub>
-	*Note: All of the endpoints connected via Cloudflare Mesh or device agent
-	are automatically assigned IP addresses from the 100.96.0.0/12 address range,
+	*Note: All of the endpoints connected via Cloudflare Mesh or device agent are
+	automatically assigned IP addresses from the 100.96.0.0/12 address range,
 	while endpoints connected to Cloudflare WAN retain their assigned RFC1918
 	private IP addresses. `cloudflared` can be deployed in any of the locations by
 	an application owner to provide hostname-based connectivity to the
diff --git a/src/content/docs/reference-architecture/architectures/security.mdx b/src/content/docs/reference-architecture/architectures/security.mdx
index 3d627ba4e4372c4..f773fce4c276399 100644
--- a/src/content/docs/reference-architecture/architectures/security.mdx
+++ b/src/content/docs/reference-architecture/architectures/security.mdx
@@ -527,7 +527,7 @@ Existing private infrastructure can be complex. Cloudflare provides a variety of
 | [Cloudflare WAN](/cloudflare-wan/)                                                                            | IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                                   | Connecting existing network routers to Cloudflare. Allowing all traffic into and out of the network to go through Cloudflare.                                                       |
 | [Cloudflare One Appliance](/cloudflare-wan/configuration/appliance/)                                          | Appliance-based IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                   | Uses the same technology as Cloudflare WAN; however, instead of using existing networking devices, a dedicated appliance or virtual machine is used — the Cloudflare One Appliance. |
 | [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/)                                         | Software agent deployed on servers or alongside services like Kubernetes for creating a tunnel for incoming connections to private applications or networks. | IT admins or application owners can easily install this tunnel software to expose their application to the Cloudflare network.                                                      |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)           | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                                       | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
 | [WARP Desktop Agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                       | Software agent deployed on user devices, creating a tunnel for traffic to and from private applications and networks.                                        | Connecting end user devices like phones and laptops to be part of the Cloudflare network.                                                                                           |
 | [Cloudflare Network Interconnect](https://www.cloudflare.com/network-services/products/network-interconnect/) | Direct connection between your physical networks and Cloudflare.                                                                                             | When your applications live in the same data centers we operate in, we can connect those networks directly to Cloudflare.                                                           |
 
diff --git a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
index 7365c6406dda2f5..fb6d969b7413b35 100644
--- a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
+++ b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
@@ -485,15 +485,15 @@ Now, you will learn how to secure RDP access as a private IP application:
 
 As mentioned before, private IP applications work because Cloudflare proxies the IP range across its network. The nature of this application necessitates the use of the device client, as unless the user is connected to Cloudflare (and more specifically, unless they can take advantage of the Client-to-Tunnel connectivity), they will not be able to reach non-local RFC 1918 addresses.
 
-| Traffic                                  |                                                                 |
-| :--------------------------------------- | :-------------------------------------------------------------- |
-| Destination IP                           | 169.254.255.254                                                 |
-| Destination Port                         | 3389                                                            |
-| **Identity**                             |                                                                 |
-| User Group Names                         | Server Admins                                                   |
-| **Device Posture**                       |                                                                 |
-| Passed Device Posture Checks             | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
-| **Action**                               | Allow                                                           |
+| Traffic                                            |                                                                 |
+| :------------------------------------------------- | :-------------------------------------------------------------- |
+| Destination IP                                     | 169.254.255.254                                                 |
+| Destination Port                                   | 3389                                                            |
+| **Identity**                                       |                                                                 |
+| User Group Names                                   | Server Admins                                                   |
+| **Device Posture**                                 |                                                                 |
+| Passed Device Posture Checks                       | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
+| **Action**                                         | Allow                                                           |
 | **Enforce Cloudflare One Client session duration** | 60m0s                                                           |
 
 Defining the application here is simple, as Cloudflare automatically fills in the IP range, and you need to limit the detected protocol to RDP. However, the rules for private IP applications are slightly different. You will notice they appear as network policies under the Cloudflare Gateway menu, despite managing them in Access. Certain options, such as checking for MFA and external evaluation, do not appear here. However, these attributes can be verified when the user activates their device client and authenticates to their organization.
diff --git a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
index dc60c3bd546f404..6b66d65a74db8d4 100644
--- a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
+++ b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
@@ -33,15 +33,15 @@ This solution supports subdomains under your own zone while also allowing your c
 
 Before looking at how Cloudflare can be configured to protect your SaaS application through your custom hostnames, it's worth reviewing the benefits of taking this approach.
 
-| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                                                       |
-| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                                                               |
-| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                                                    |
-| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                                                               |
-| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                                                    |
+| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                   |
+| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                           |
+| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                |
+| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                           |
+| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                |
 | O2O                      | For end-customers who already proxy traffic through Cloudflare, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) may be required. Generally, it's recommended for those end-customers to [not proxy](/dns/proxy-status/#dns-only-records) the hostnames used by the SaaS provider. If O2O functionality is required, please review the [product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/). |
-| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                                                                |
+| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                            |
 
 ## Products included in this guide
 
diff --git a/src/content/docs/reference-architecture/diagrams/ai/index.mdx b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
index a86575102d8dcfa..31b853acdc50598 100644
--- a/src/content/docs/reference-architecture/diagrams/ai/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
@@ -12,6 +12,6 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
index 65249beeb1e0af4..b78ee67b330dcc6 100644
--- a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
@@ -12,6 +12,6 @@ products:
   - cache
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
index 0e82981e3eafb7b..52648681f876333 100644
--- a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
+++ b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
@@ -1,7 +1,20 @@
 ---
 title: Optimizing and securing connected transportation systems
 pcx_content_type: reference-architecture-diagram
-products: [argo-smart-routing, api-shield, cache, ddos-protection, dns-firewall, load-balancing, r2, workers, ssl, waf, workers-ai]
+products:
+  [
+    argo-smart-routing,
+    api-shield,
+    cache,
+    ddos-protection,
+    dns-firewall,
+    load-balancing,
+    r2,
+    workers,
+    ssl,
+    waf,
+    workers-ai,
+  ]
 sidebar:
   order: 1
   label: Connected transportation systems
@@ -29,7 +42,6 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
 2. **Cloudflare anycast network**: Cloudflare uses [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) networking and is one of the world's most connected and geographically distributed networks. Traffic is routed to the nearest Cloudflare data center, which reduces the number of network hops, dynamically adapts to changing network conditions, and ensures data takes the shortest path to its destination, minimizing latency and maximizing reliability.
 
 3. **Security services**:
-
    1. **API Shield**: Cloudflare's [API Shield](/api-shield/get-started/) protects critical APIs from unauthorized access and abuse, ensuring secure data exchange between connected systems.
    2. **Web Application Firewall (WAF)**: Cloudflare's [WAF](/waf/) helps block malicious traffic and prevent application or API vulnerabilities from being exploited, safeguarding your network, devices and applications.
    3. **DDoS Protection**: Cloudflare's [DDoS protection](/ddos-protection/about/attack-coverage/), covering the network, transport and application layer, prevents volumetric attacks that could compromise the availability of connected systems. By providing multi-layered protection, Cloudflare is able to mitigate a wide variety of DDoS threats. At lower layers, Cloudflare defends against high-volume attacks such as SYN floods, UDP floods, and other types of protocol-based disruptions that can overwhelm network resources. At the application layer, more sophisticated attacks targeting the application itself, such as HTTP floods \- which aim to exhaust server resources and disrupt user-facing services \- are blocked even in the face of [large-scale DDoS attempts](https://blog.cloudflare.com/tag/ddos-reports/).
@@ -37,7 +49,6 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
    5. **TLS encryption**: [TLS encryption](/ssl/edge-certificates/) ensures that data exchanged across the network is protected from interception, maintaining data integrity and privacy.
 
 4. **Performance and reliability services**:
-
    1. **Content Delivery Network (CDN)**: [Distribute content](https://www.cloudflare.com/en-gb/learning/cdn/what-is-a-cdn/) efficiently across the network, reducing latency for end users by caching data closer to them.
    2. **Load balancing**: [Distribute incoming traffic](/load-balancing/get-started/quickstart/) across multiple servers or data centers, ensuring optimal resource utilization, preventing single points of failure, and improving the performance of connected systems.
    3. **Cloudflare Workers**: Our serverless compute platform, [Cloudflare Workers](/workers/), allows data processing at the edge, reducing the need for data to travel long distances and significantly reducing latency. Combined with related services like [Workers KV](/kv/get-started/) and [D1](https://www.cloudflare.com/en-gb/developer-platform/products/d1/), Cloudflare's edge-based storage solutions enable efficient data management close to the user. Workers KV allows for quick, read-heavy data access, perfect for caching configurations and frequently used data, while D1 provides a serverless SQL database for more robust storage needs. Additionally, Cloudflare's [Durable Objects](https://blog.cloudflare.com/sqlite-in-durable-objects/) help manage stateful interactions at the edge, facilitating real-time data consistency. These tools together allow for seamless data processing, storage and lazy updates to core services, minimizing back-and-forth to centralized servers and ensuring faster, more efficient performance.
diff --git a/src/content/docs/reference-architecture/diagrams/network/index.mdx b/src/content/docs/reference-architecture/diagrams/network/index.mdx
index dab7f9b29c2ac8b..8d297fcb542d684 100644
--- a/src/content/docs/reference-architecture/diagrams/network/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/network/index.mdx
@@ -12,6 +12,6 @@ products:
   - magic-transit
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/sase/index.mdx b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
index 952f8cbb7035014..5a5bcdc66e7f753 100644
--- a/src/content/docs/reference-architecture/diagrams/sase/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
@@ -12,6 +12,6 @@ products:
   - cloudflare-one
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/security/index.mdx b/src/content/docs/reference-architecture/diagrams/security/index.mdx
index 6e7f959a2bf1894..b6a5e7116f9b9ab 100644
--- a/src/content/docs/reference-architecture/diagrams/security/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/security/index.mdx
@@ -12,6 +12,6 @@ products:
   - waf
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
index be169cd2360397e..80a5daa8d28537b 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
@@ -1,7 +1,32 @@
 ---
 title: Fullstack applications
 pcx_content_type: reference-architecture-diagram
-products: [ai-gateway, agents, api-shield, bots, containers, d1, ddos-protection, durable-objects, images, kv, logs, pages, pipelines, queues, r2, realtime, ssl, stream, vectorize, waf, workflows, workers, workers-ai]
+products:
+  [
+    ai-gateway,
+    agents,
+    api-shield,
+    bots,
+    containers,
+    d1,
+    ddos-protection,
+    durable-objects,
+    images,
+    kv,
+    logs,
+    pages,
+    pipelines,
+    queues,
+    r2,
+    realtime,
+    ssl,
+    stream,
+    vectorize,
+    waf,
+    workflows,
+    workers,
+    workers-ai,
+  ]
 sidebar:
   order: 1
   label: Fullstack applications
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
index fd828080d0d13a7..ec24b3e2d1e0920 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
@@ -11,6 +11,6 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
index 59502f5c65c9030..37a97208f955c57 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
@@ -94,7 +94,6 @@ Data observability and control is crucial for security. [Outbound Workers](/clou
 1. **Management Interface**: Interact with the platform through GUI, API, or CLI interfaces.
 
 2. **Platform Processing**: Process these interactions to:
-
    - Transform and bundle code
    - Perform security checks
    - Apply configuration
diff --git a/src/content/docs/reference-architecture/diagrams/storage/index.mdx b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
index bed6aa10ef8f5ae..c1a8deb1e885b1a 100644
--- a/src/content/docs/reference-architecture/diagrams/storage/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
@@ -11,6 +11,6 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/implementation-guides/index.mdx b/src/content/docs/reference-architecture/implementation-guides/index.mdx
index 2904c70b1df0a79..050e352a4e30355 100644
--- a/src/content/docs/reference-architecture/implementation-guides/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/index.mdx
@@ -23,4 +23,4 @@ Implementation guides provide [step-by-step instructions](/reference-architectur
 
 ## Application Security
 
-- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
\ No newline at end of file
+- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
diff --git a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
index 5c5f919b63c0538..2fdb4a789da4092 100644
--- a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
@@ -19,4 +19,4 @@ Zero Trust implementation guides walk you through the steps to deploy a Zero Tru
 - [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/)
 - [Replace your VPN](/learning-paths/replace-vpn/concepts/)
 - [Deploy Zero Trust Web Access](/learning-paths/clientless-access/concepts/)
-- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
\ No newline at end of file
+- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
diff --git a/src/content/docs/registrar/account-options/domain-contact-updates.mdx b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
index c68e021cdb34a52..33cc9a043acdbdd 100644
--- a/src/content/docs/registrar/account-options/domain-contact-updates.mdx
+++ b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
@@ -12,18 +12,18 @@ It is important that you keep your contact details accurate and up-to-date. [ICA
 
 The contact information you can update includes:
 
-* First name
-* Last name
-* Email
-* Organization
-* Phone
-* Address including City, State/Province, Postal code & Country
+- First name
+- Last name
+- Email
+- Organization
+- Phone
+- Address including City, State/Province, Postal code & Country
 
 To update your registrant contacts:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find **Default contact** and select **Edit**.
 3. Update the relevant information, and select **Save**.
@@ -32,10 +32,10 @@ To update your registrant contacts:
 
 If you change any of the following fields, Cloudflare Registrar will require a Change of Registrant approval before the changes are finalized:
 
-* First name
-* Last name
-* Organization
-* Email address
+- First name
+- Last name
+- Organization
+- Email address
 
 If you update any of the fields mentioned above, Cloudflare Registrar will send an approval email to the current registrant's email address. The approval email contains a link to a web page where the requested change may be viewed and approved or rejected. If the pending change is not approved or rejected within seven days, the request will automatically be canceled.
 
@@ -43,11 +43,9 @@ If you do not update these fields, your contact information is updated immediate
 
 :::caution[Important]
 
-
 After selecting the link in the approval email Cloudflare sends you, you have the option to accept or reject the contact changes. If you select the **Accept** button, your domain will be transfer-locked for 60 days.
 
-If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox *before* selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
-
+If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox _before_ selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
 
 :::
 
diff --git a/src/content/docs/registrar/account-options/domain-management.mdx b/src/content/docs/registrar/account-options/domain-management.mdx
index b00b69c71cdde48..436f7461a485b3f 100644
--- a/src/content/docs/registrar/account-options/domain-management.mdx
+++ b/src/content/docs/registrar/account-options/domain-management.mdx
@@ -6,7 +6,7 @@ products:
 description: Manage your registered domains in the dashboard.
 ---
 
-import { DashButton, LinkButton } from "~/components"
+import { DashButton, LinkButton } from "~/components";
 
 ## Domain status
 
@@ -14,9 +14,9 @@ When your domain is registered with Cloudflare, you can review your domain statu
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date. 
+2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date.
 3. Select **Manage domain** to review the Auto-Renew status for your domain.
 
 ## Billing information
@@ -25,7 +25,7 @@ Domain registrations will not appear in the **Active Subscriptions** section of
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to check and select **Manage**.
 3. Refer to **Registration** for information regarding your domain fees. From here, you can also opt to [renew or extend](/registrar/account-options/renew-domains/) your domain registration.
@@ -36,7 +36,7 @@ Cloudflare redacts WHOIS information from your domain by default. However, we do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to edit and select **Manage** > **Contacts**.
 3. Select **Edit** in any of the contacts you previously set up. This allows you to update the contact information for the selected domain only. It will not update the contact information for other domains within the account.
@@ -62,10 +62,10 @@ There may be instances where users may wish to delete a domain prior to expirati
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-3. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
-4. If the domain is deletable the button will be active.  The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
-5. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
+2. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
+3. If the domain is deletable the button will be active. The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
+4. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
 
 Once all steps are completed, the domain will then be scheduled for deletion. To understand more about the timelines and potential reasons why a domain cannot be deleted, refer to the Registrar [FAQ](/registrar/faq/#domain-deletions).
diff --git a/src/content/docs/registrar/account-options/icloud-domains.mdx b/src/content/docs/registrar/account-options/icloud-domains.mdx
index 7cd576b2342f223..51ea04635dec389 100644
--- a/src/content/docs/registrar/account-options/icloud-domains.mdx
+++ b/src/content/docs/registrar/account-options/icloud-domains.mdx
@@ -17,7 +17,7 @@ You will need an active iCloud+ subscription to add a custom email domain.
 
 If you want to buy a custom email domain, go to your [iCloud](https://www.icloud.com/settings/) settings and scroll down to **Custom Email Domain**.
 
-***
+---
 
 ## Log in to Cloudflare
 
@@ -31,7 +31,7 @@ If you had signed up with Apple, signing into Cloudflare is as easy as clicking
 
 If you had signed up with Cloudflare, signing into Cloudflare can be done with your email and password.
 
-***
+---
 
 ## Billing information
 
@@ -39,9 +39,9 @@ If you had signed up with Cloudflare, signing into Cloudflare can be done with y
 
 For domain registration, Cloudflare supports the following payment methods:
 
-* Credit Card
-* PayPal
-* Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
+- Credit Card
+- PayPal
+- Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
 
 For domain renewals, Apple Pay does not currently support recurring payments. You can either add another payment method (Credit Card or PayPal) for automatic renewals or log into [your account](#log-in-to-cloudflare) near the renewal date and use Apple Pay.
 
@@ -51,7 +51,7 @@ Users may see a price estimate in both U.S. Dollars and a local currency. This i
 
 The final payment will be charged in US dollars.
 
-***
+---
 
 ## Email issues
 
@@ -67,7 +67,7 @@ If you are not receiving emails intended for your new email address, review your
 
 If your domain has records similar to those listed above and you are still experiencing problems with your new email address, contact [Apple Support](https://support.apple.com/).
 
-***
+---
 
 ## Domain website
 
@@ -80,7 +80,7 @@ If you want your domain to be a fully functioning website, you will need to:
 1. **Build your website**: Either using [Cloudflare Pages](/pages/), a website builder, or files hosted on a server.
 2. **Update your Cloudflare DNS**: To direct visitors looking for your domain name to the actual content on your website ([detailed guide](/dns/manage-dns-records/how-to/create-zone-apex/)).
 
-***
+---
 
 ## Landing Page
 
@@ -92,18 +92,16 @@ If you do not want to have Landing Page enabled:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
-3. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
-4. Scroll to Landing Page and select **Disable**.
+2. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
+3. Scroll to Landing Page and select **Disable**.
 
 You now have Landing Page disabled. The page can also be re-enabled through the same process.
 
 :::note
 
-
 Customers must disable the landing page before they can add DNS records
 to point to a new website.
 
-
 :::
diff --git a/src/content/docs/registrar/account-options/index.mdx b/src/content/docs/registrar/account-options/index.mdx
index c28da7b171d3437..0ad0fed63956d72 100644
--- a/src/content/docs/registrar/account-options/index.mdx
+++ b/src/content/docs/registrar/account-options/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Explore Cloudflare Registrar account options.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/account-options/inter-account-transfer.mdx b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
index 9ec8ed6c910675e..8089af6ebb59ebd 100644
--- a/src/content/docs/registrar/account-options/inter-account-transfer.mdx
+++ b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
@@ -15,28 +15,29 @@ This process only applies to domains which are registered with Cloudflare Regist
 
 Before proceeding, please be aware of the following:
 
-* WHOIS contact information will be moved as is.
-* No other configuration will be moved.
-* After successful move, the registration will be transfer-locked for 30 days.
-* The target account will become responsible for domain renewals going forward.
+- WHOIS contact information will be moved as is.
+- No other configuration will be moved.
+- After successful move, the registration will be transfer-locked for 30 days.
+- The target account will become responsible for domain renewals going forward.
 
 ## 1. Prepare for the move
 
 Before you request the move, you will need to do the following:
 
-* Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
-* Add the domain as a website to the new account and select a plan.
-* [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
+- Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
+- Add the domain as a website to the new account and select a plan.
+- [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
 
 The following pre-conditions must be met before the domain can be moved:
-* The domain must have been registered more than 10 days ago.
-* The domain must be added to the new account as a website and a plan must be selected.
-* The domain must not be administratively locked, such as being locked due to a dispute or court order.
-* The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
-* The registrant email address must be verified.
-* A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
-* DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
-* If the current zone is locked, the lock must be released.
+
+- The domain must have been registered more than 10 days ago.
+- The domain must be added to the new account as a website and a plan must be selected.
+- The domain must not be administratively locked, such as being locked due to a dispute or court order.
+- The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
+- The registrant email address must be verified.
+- A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
+- DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
+- If the current zone is locked, the lock must be released.
 
 ## 2. Submit the move request
 
diff --git a/src/content/docs/registrar/account-options/renew-domains.mdx b/src/content/docs/registrar/account-options/renew-domains.mdx
index dda7c66958054bd..285bff694c78d57 100644
--- a/src/content/docs/registrar/account-options/renew-domains.mdx
+++ b/src/content/docs/registrar/account-options/renew-domains.mdx
@@ -21,10 +21,8 @@ If you decide you no longer need the domain, [disable auto-renew for your domain
 
 :::note[Note]
 
-
 The first auto-renew attempt will occur approximately 30 days prior to expiration. If you wish to disable auto-renew, do so at least 30 days prior to the expiration date.
 
-
 :::
 
 You can continue to keep your domain registered with Cloudflare for the time remaining until the expiration date. If you decide you want to keep the domain, enable auto-renew at any time prior to expiration.
@@ -35,7 +33,7 @@ If you want your domains to renew automatically, keep the default settings for y
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to automatically renew, and make sure the **Auto-renew** toggle is enabled.
 
@@ -47,10 +45,8 @@ If the renewal fails, you will receive an email notification and Cloudflare will
 
 :::note
 
-
 If you want to delete your domain from Cloudflare, **disable** Auto-Renew first.
 
-
 :::
 
 ## Renew a domain manually
@@ -59,7 +55,7 @@ You can renew a domain at any time. To renew a domain registered with Cloudflare
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to renew and select **Manage**.
 3. In **Registration** select **Renew/Extend Domain**.
@@ -72,24 +68,22 @@ Once Cloudflare validates your payment, the status of your domain changes to **R
 
 Once a domain is registered, Registrar sends the following expiration notices to the Super Admin of the domain:
 
-* A monthly email listing all domains set to renew automatically within the next 45 days.
-* A monthly email listing all domains expiring in the next 60-90 days.
+- A monthly email listing all domains set to renew automatically within the next 45 days.
+- A monthly email listing all domains expiring in the next 60-90 days.
 
 In addition to the Super Admin, the following expiration notices are sent to the WHOIS Registrant contact associated with the domain:
 
-* A weekly email listing all domains expiring within the next month.
-* A daily email listing all domains expiring in seven days.
-* An email one day after a domain expires.
-* An email 20 days after the expiration date.
+- A weekly email listing all domains expiring within the next month.
+- A daily email listing all domains expiring in seven days.
+- An email one day after a domain expires.
+- An email 20 days after the expiration date.
 
 :::note
 
-
 If you do not renew your domain before the expiration date, your domain will enter a Redemption Grace Period (RGP) for 30 days. These domains are not deleted and you can restore them to your account, but restoration may require an additional fee. You cannot transfer domains during the RGP.
 
 All renewals are final and Cloudflare will not issue refunds.
 
 When renewing a domain, additional years are always added to the current expiration date regardless of when the renewal takes place.
 
-
 :::
diff --git a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
index b699b2181413945..9c7bbb499016c44 100644
--- a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
+++ b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
@@ -13,9 +13,9 @@ import { DashButton } from "~/components";
 
 Cloudflare Registrar makes it easy to transfer your domain to another registrar. Be aware that ICANN rules prohibit a domain from being transferred if:
 
-* The domain has been transferred within the last 60 days;
-* The domain was registered within the last 60 days;
-* If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
+- The domain has been transferred within the last 60 days;
+- The domain was registered within the last 60 days;
+- If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
 
 Follow the instructions below to transfer your domain out from Cloudflare.
 
@@ -28,7 +28,7 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to transfer, and select **Manage**.
 3. Select **Configuration** > **Unlock**.
@@ -37,8 +37,8 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 If you lose your authentication code, you can get a new one by:
 
-* Selecting the **Regenerate** button;
-* Locking the domain and repeating steps 1-6.
+- Selecting the **Regenerate** button;
+- Locking the domain and repeating steps 1-6.
 
 ## 2. Transfer to a new registrar
 
diff --git a/src/content/docs/registrar/account-options/whois-redaction.mdx b/src/content/docs/registrar/account-options/whois-redaction.mdx
index 54f84e462053f44..ae936db97b56984 100644
--- a/src/content/docs/registrar/account-options/whois-redaction.mdx
+++ b/src/content/docs/registrar/account-options/whois-redaction.mdx
@@ -20,8 +20,8 @@ Cloudflare’s WHOIS service can be found at [https://rdap.cloudflare.com/](http
 
 WHOIS redaction removes most contact information categorized as personal data (such as registrant name, email address, postal address) from the published WHOIS record for a domain. These fields will read `Data Redacted`. The nameserver, domain lock information, and date records for a domain are still available publicly. The following fields will continue to show in WHOIS, due to ICANN policy:
 
-* Registrant state/province
-* Registrant country
+- Registrant state/province
+- Registrant country
 
 Cloudflare still maintains the authoritative, unredacted, record of your WHOIS data. You can modify this information at any time. Refer to [Registrant contact updates](/registrar/account-options/domain-contact-updates) for more information.
 
diff --git a/src/content/docs/registrar/custom-domain-protection.mdx b/src/content/docs/registrar/custom-domain-protection.mdx
index 5175f44c6cba05f..7c230831d9ec50c 100644
--- a/src/content/docs/registrar/custom-domain-protection.mdx
+++ b/src/content/docs/registrar/custom-domain-protection.mdx
@@ -12,8 +12,8 @@ Cloudflare offers [Custom Domain Protection](https://www.cloudflare.com/products
 
 Custom Domain Protection offers additional safeguard features for registered domains, including:
 
-* **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
-* **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
-* **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
+- **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
+- **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
+- **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
 
 Contact your account team if you are interested in Cloudflare's Custom Domain Protection.
diff --git a/src/content/docs/registrar/get-started/index.mdx b/src/content/docs/registrar/get-started/index.mdx
index 0337c455830ed00..adddbd0c163091c 100644
--- a/src/content/docs/registrar/get-started/index.mdx
+++ b/src/content/docs/registrar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Set up Client IP Geolocation for your network.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/get-started/register-domain.mdx b/src/content/docs/registrar/get-started/register-domain.mdx
index b3d8c632b668672..7f46b29e462ccda 100644
--- a/src/content/docs/registrar/get-started/register-domain.mdx
+++ b/src/content/docs/registrar/get-started/register-domain.mdx
@@ -10,15 +10,14 @@ description: Register a new domain with Cloudflare.
 
 import { DashButton, Render } from "~/components";
 
-
 ## Prerequisites and restrictions
 
 :::note[Cloudflare nameservers]
 All domains acquired via Cloudflare Registrar use Cloudflare nameservers, automatically [protecting and speeding up](/fundamentals/concepts/how-cloudflare-works/) your content or services. You will not be able to change to another DNS provider's nameservers while using Cloudflare Registrar.
 :::
 
-* Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
-* You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
+- Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
+- You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
 
 <Render file="icann-unverified-email" product="registrar" />
 
@@ -30,16 +29,14 @@ If you are registering a `.us` domain, refer to the [Additional requirements for
 
 1. In the Cloudflare dashboard, go to the **Register domains** page.
 
-    <DashButton url="/?to=/:account/registrar/register" />
+   <DashButton url="/?to=/:account/registrar/register" />
 
 2. In the search box, enter the domain name you wish to register, and select **Search**. You may also enter one or more keywords. The search results will contain a list of suggested domains. If the domain you entered does not appear in the list, this means it is not available for registration.
 
 :::caution[Important]
 
-
 Cloudflare Registrar currently does not support internationalized domain names (IDNs), also known as unicode. For that reason, you cannot search for words with special characters, such as `à`, `ü`, `ç`, among others.
 
-
 :::
 
 3. Select **Purchase** on the domain you wish to register. In rare instances, a domain that is not available for registration may appear in the search results. After selecting **Purchase**, a definitive availability check will be performed to confirm that the domain is actually available for registration.
@@ -52,12 +49,10 @@ Cloudflare Registrar currently does not support internationalized domain names (
 
 :::note
 
-
 If you have previously registered or transferred a domain name, the form will be filled in advance with the information from your default contact. If not, you will need to fill out the form.
 
 It is important that you provide complete and accurate contact information. If you do not follow this recommendation, the domain registration may be suspended and/or canceled.
 
-
 :::
 
 6. In **Payment**, select which type of payment you want to use. If you already have a billing profile, Cloudflare uses this information to automatically fill the form. If there is no billing profile, you need to enter your payment information.
@@ -72,8 +67,6 @@ The registration process may take up to 30 seconds to complete. Once the registr
 
 At this time, you can only use ASCII characters for contact data. If the default contact has non-ASCII characters, you will need to update the domain contact details before proceeding. Cloudflare recommends that you update your default contact information to include ASCII characters only.
 
-
-
 | Field        | Required? | Restrictions                                                                                                                   |
 | ------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
 | First Name   | Yes       | Minimum of two letters.                                                                                                        |
@@ -89,8 +82,6 @@ At this time, you can only use ASCII characters for contact data. If the default
 | Country      | Yes       | You must select one from the drop-down options.                                                                                |
 | Postal Code  | Yes       | Must be a properly formatted postal code.                                                                                      |
 
-
-
 When you register a domain with Cloudflare, your personal information is redacted when permitted by the registry. Refer to [WHOIS redaction](/registrar/account-options/whois-redaction/) for more information.
 
 ## Next steps
diff --git a/src/content/docs/registrar/top-level-domains/uk-domains.mdx b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
index 33034fbe090ae38..4ec5d8a00c26f8f 100644
--- a/src/content/docs/registrar/top-level-domains/uk-domains.mdx
+++ b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
@@ -22,22 +22,16 @@ Cloudflare currently supports the transfer of `.uk`, `co.uk`, `org.uk`, and `me.
 
 1. In the Cloudflare dashboard, go to the **Transfer domains** page.
 
-    <DashButton url="/?to=/:account/registrar/transfer" />
+   <DashButton url="/?to=/:account/registrar/transfer" />
 
-Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain.
-2. Select the domains you wish to transfer.
-3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process.
-4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days.
-5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
+Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain. 2. Select the domains you wish to transfer. 3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process. 4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days. 5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
 
 :::caution[Warning]
 
-
 If you request your current registrar to update the IPS tag before completing the checkout process, the transfer request will be automatically rejected. You must complete the checkout process before requesting the IPS tag update.
 
 For security reasons, domains transferred to Cloudflare Registrar are locked for 60 days before they can be transferred out to another Registrar.
 
-
 :::
 
 ## Transfer a .UK domain to another registrar
@@ -52,8 +46,6 @@ Your new registrar is responsible for accepting the transfer. Cloudflare has no
 
 :::note
 
-
 If you do not know the IPS tag, contact your new registrar for instructions. Your new registrar may require you to follow some additional steps before starting the transfer process.
 
-
 :::
diff --git a/src/content/docs/registrar/whoisrequests.mdx b/src/content/docs/registrar/whoisrequests.mdx
index 445ca659095fc8e..95317e78416dd66 100644
--- a/src/content/docs/registrar/whoisrequests.mdx
+++ b/src/content/docs/registrar/whoisrequests.mdx
@@ -10,7 +10,7 @@ description: Submit WHOIS disclosure requests to Cloudflare.
 
 This page describes the mechanism and process for submitting a disclosure request to Cloudflare for WHOIS data under Section 10 of the Internet Corporation for Assigned Names and Number's ("ICANN") [Registration Data Policy](https://www.icann.org/en/contracted-parties/consensus-policies/registration-data-policy).
 
-Please read the following instructions carefully.  
+Please read the following instructions carefully.
 
 ## 1. Prepare your request
 
@@ -18,7 +18,7 @@ Your request must include the following elements:
 
 - Your name
 - The requestor's name, mailing address, and email
-- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity.  If the latter, identify whether the requestor is an individual, corporation, or government
+- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity. If the latter, identify whether the requestor is an individual, corporation, or government
 - Any power of Attorney statements or similar statements evidencing authorization to act on the requestor's behalf, where applicable and relevant
 - A list of data element values requested by the requestor
 - Information about the legal rights of the requestor and specific rationale and basis for the request
diff --git a/src/content/docs/resource-tagging/get-started.mdx b/src/content/docs/resource-tagging/get-started.mdx
index 5a8aa68ee493d82..b9bc956239e99a5 100644
--- a/src/content/docs/resource-tagging/get-started.mdx
+++ b/src/content/docs/resource-tagging/get-started.mdx
@@ -26,13 +26,13 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys
 
 ### Interpreting the response
 
-| Response | Meaning | Action |
-| --- | --- | --- |
-| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step. |
-| **403** mentioning "permission" or "role" | The caller lacks required permissions. | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope. |
-| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance. |
-| **401 Unauthorized** | Authentication failed. | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header. |
-| Any other response | Unexpected error. | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
+| Response                                             | Meaning                                                            | Action                                                                                                                                                        |
+| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step.                                                                                                                                     |
+| **403** mentioning "permission" or "role"            | The caller lacks required permissions.                             | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope.                    |
+| **403** mentioning "feature" or "gate"               | Tagging is not enabled for this account.                           | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance.                                                                         |
+| **401 Unauthorized**                                 | Authentication failed.                                             | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header.                                                        |
+| Any other response                                   | Unexpected error.                                                  | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
 
 ## 2. Create your first tags
 
diff --git a/src/content/docs/resource-tagging/how-to/index.mdx b/src/content/docs/resource-tagging/how-to/index.mdx
index 8c39e93b47e1641..daacb0f1c1aa2d4 100644
--- a/src/content/docs/resource-tagging/how-to/index.mdx
+++ b/src/content/docs/resource-tagging/how-to/index.mdx
@@ -7,6 +7,6 @@ head:
     content: How-to guides
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/how-to/manage-tags.mdx b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
index 813ad1a57752b9b..9625cc22be99763 100644
--- a/src/content/docs/resource-tagging/how-to/manage-tags.mdx
+++ b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
@@ -75,9 +75,9 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags?reso
 
 ```json
 {
-  "environment": "production",
-  "team": "platform",
-  "cost-center": "engineering"
+	"environment": "production",
+	"team": "platform",
+	"cost-center": "engineering"
 }
 ```
 
diff --git a/src/content/docs/resource-tagging/reference/error-codes.mdx b/src/content/docs/resource-tagging/reference/error-codes.mdx
index 7f1cd73a0d758bf..026f122644541f7 100644
--- a/src/content/docs/resource-tagging/reference/error-codes.mdx
+++ b/src/content/docs/resource-tagging/reference/error-codes.mdx
@@ -8,19 +8,19 @@ description: Tagging API error codes, causes, and resolutions.
 
 ## Error code reference
 
-| Code | HTTP status | Message | Likely cause | Resolution |
-| --- | --- | --- | --- | --- |
-| `1002` | 400 | Invalid set payload | Request body is malformed or missing required fields | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
-| `1003` | 400 | `resource_type` and `resource_id` are required | Missing query parameters | Include both `resource_type` and `resource_id` in the query string |
-| `1006` | 400 | Invalid resource type | Unsupported resource type | Use a [supported resource type](/resource-tagging/reference/resource-types/) |
-| `1007` | 400 | tag parameter must be in format... | Tag filter syntax is incorrect | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/) |
-| `1009` | 400 | `tag_key` is required | Missing `tag_key` parameter | Include the `tag_key` path parameter |
-| `1010` | 400 | too many tag filters (maximum 20) | More than 20 `tag` query parameters | Reduce filters to 20 or fewer, or split across multiple requests |
-| `1011` | 400 | tag key too long (maximum 256 characters) | Tag key exceeds 256 characters | Shorten the tag key |
-| `1012` | 400 | tag value too long (maximum 1024 characters) | Tag value exceeds 1,024 characters | Shorten the tag value |
-| `1013` | 400 | too many OR values in tag filter (maximum 10) | More than 10 comma-separated values in a single filter | Split into multiple filters |
-| `1014` | 400 | Invalid tag key | Key contains invalid characters | Use only letters, digits, `_`, `.`, `-` |
-| `1015` | 400 | Invalid delete payload | Delete request body is malformed | Verify the body includes `resource_type` and `resource_id` |
+| Code   | HTTP status | Message                                        | Likely cause                                           | Resolution                                                                    |
+| ------ | ----------- | ---------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------- |
+| `1002` | 400         | Invalid set payload                            | Request body is malformed or missing required fields   | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
+| `1003` | 400         | `resource_type` and `resource_id` are required | Missing query parameters                               | Include both `resource_type` and `resource_id` in the query string            |
+| `1006` | 400         | Invalid resource type                          | Unsupported resource type                              | Use a [supported resource type](/resource-tagging/reference/resource-types/)  |
+| `1007` | 400         | tag parameter must be in format...             | Tag filter syntax is incorrect                         | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/)   |
+| `1009` | 400         | `tag_key` is required                          | Missing `tag_key` parameter                            | Include the `tag_key` path parameter                                          |
+| `1010` | 400         | too many tag filters (maximum 20)              | More than 20 `tag` query parameters                    | Reduce filters to 20 or fewer, or split across multiple requests              |
+| `1011` | 400         | tag key too long (maximum 256 characters)      | Tag key exceeds 256 characters                         | Shorten the tag key                                                           |
+| `1012` | 400         | tag value too long (maximum 1024 characters)   | Tag value exceeds 1,024 characters                     | Shorten the tag value                                                         |
+| `1013` | 400         | too many OR values in tag filter (maximum 10)  | More than 10 comma-separated values in a single filter | Split into multiple filters                                                   |
+| `1014` | 400         | Invalid tag key                                | Key contains invalid characters                        | Use only letters, digits, `_`, `.`, `-`                                       |
+| `1015` | 400         | Invalid delete payload                         | Delete request body is malformed                       | Verify the body includes `resource_type` and `resource_id`                    |
 
 :::note[Error 1007 note]
 The error message text references `:` as the tag filter separator (for example, `key:value`), but the API implementation uses `=` in query parameters (for example, `tag=key=value`). The error message is outdated — always use `=` when constructing tag filters.
diff --git a/src/content/docs/resource-tagging/reference/index.mdx b/src/content/docs/resource-tagging/reference/index.mdx
index 6de666492e69204..9361dd2c4b8a0cd 100644
--- a/src/content/docs/resource-tagging/reference/index.mdx
+++ b/src/content/docs/resource-tagging/reference/index.mdx
@@ -7,6 +7,6 @@ head:
     content: Reference
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/reference/limits.mdx b/src/content/docs/resource-tagging/reference/limits.mdx
index 350cb2973f6183a..85a5ee4696d5f45 100644
--- a/src/content/docs/resource-tagging/reference/limits.mdx
+++ b/src/content/docs/resource-tagging/reference/limits.mdx
@@ -8,14 +8,14 @@ description: API limits, tag key validation rules, and pagination behavior.
 
 ## API limits
 
-| Limit | Value | Error code |
-| --- | --- | --- |
-| Maximum tags per account | 10,000 (beta) | N/A |
-| Maximum tag key length | 256 characters | `1011` |
-| Maximum tag value length | 1,024 characters | `1012` |
-| Maximum tag filters per query | 20 | `1010` |
-| Maximum OR values per filter | 10 | `1013` |
-| Results per page | 100 (fixed) | N/A |
+| Limit                         | Value            | Error code |
+| ----------------------------- | ---------------- | ---------- |
+| Maximum tags per account      | 10,000 (beta)    | N/A        |
+| Maximum tag key length        | 256 characters   | `1011`     |
+| Maximum tag value length      | 1,024 characters | `1012`     |
+| Maximum tag filters per query | 20               | `1010`     |
+| Maximum OR values per filter  | 10               | `1013`     |
+| Results per page              | 100 (fixed)      | N/A        |
 
 When a limit is exceeded, the API returns `400 Bad Request` with the corresponding error code.
 
@@ -45,16 +45,16 @@ Tag keys must follow these character rules:
 
 ### Examples
 
-| Key | Valid | Reason |
-| --- | --- | --- |
-| `environment` | Yes | Letters only |
-| `team_name` | Yes | Underscore |
-| `cost-center` | Yes | Hyphen |
-| `owner.email` | Yes | Period |
-| `env123` | Yes | Letters and digits |
-| `env name` | **No** | Contains space |
-| `team@work` | **No** | Special character `@` |
-| (empty) | **No** | Empty string |
+| Key           | Valid  | Reason                |
+| ------------- | ------ | --------------------- |
+| `environment` | Yes    | Letters only          |
+| `team_name`   | Yes    | Underscore            |
+| `cost-center` | Yes    | Hyphen                |
+| `owner.email` | Yes    | Period                |
+| `env123`      | Yes    | Letters and digits    |
+| `env name`    | **No** | Contains space        |
+| `team@work`   | **No** | Special character `@` |
+| (empty)       | **No** | Empty string          |
 
 Invalid tag keys return `400 Bad Request` with error code `1014`.
 
@@ -63,6 +63,7 @@ Invalid tag keys return `400 Bad Request` with error code `1014`.
 List endpoints use cursor-based pagination with a fixed page size of 100. The page size is not configurable.
 
 Paginated endpoints:
+
 - `GET /accounts/{account_id}/tags/keys`
 - `GET /accounts/{account_id}/tags/resources`
 - `GET /accounts/{account_id}/tags/values/{tag_key}`
diff --git a/src/content/docs/resource-tagging/reference/resource-types.mdx b/src/content/docs/resource-tagging/reference/resource-types.mdx
index 65c23a2da688ce7..0d2bab2a3ec669c 100644
--- a/src/content/docs/resource-tagging/reference/resource-types.mdx
+++ b/src/content/docs/resource-tagging/reference/resource-types.mdx
@@ -12,51 +12,51 @@ The Tagging API supports the following resource types across account-level and z
 
 Use `/accounts/{account_id}/tags` endpoints for these resource types.
 
-| Resource type | Required extra fields | Description |
-| --- | --- | --- |
-| `account` | None | The Cloudflare account itself |
-| `access_application` | None | Access application |
-| `access_group` | None | Access group |
-| `account_ruleset` | None | Account-level ruleset |
-| `ai_gateway` | None | AI Gateway |
-| `alerting_policy` | None | Notification policy |
-| `alerting_webhook` | None | Notification webhook destination |
-| `cloudflared_tunnel` | None | Cloudflare Tunnel |
-| `d1_database` | None | D1 database |
-| `durable_object_namespace` | None | Durable Objects namespace |
-| `gateway_list` | None | Gateway list |
-| `gateway_rule` | None | Gateway rule |
-| `image` | None | Cloudflare Image |
-| `kv_namespace` | None | Workers KV namespace |
-| `load_balancer_monitor` | None | Load Balancer monitor |
-| `load_balancer_pool` | None | Load Balancer pool |
-| `pages_project` | None | Pages project |
-| `queue` | None | Queue |
-| `r2_bucket` | None | R2 bucket |
-| `resource_share` | None | Resource share |
-| `stream_live_input` | None | Stream live input |
-| `stream_video` | None | Stream video |
-| `vectorize_index` | None | Vectorize index |
-| `worker` | None | Workers script |
-| `worker_version` | `worker_id` | Specific version of a Worker |
+| Resource type              | Required extra fields | Description                      |
+| -------------------------- | --------------------- | -------------------------------- |
+| `account`                  | None                  | The Cloudflare account itself    |
+| `access_application`       | None                  | Access application               |
+| `access_group`             | None                  | Access group                     |
+| `account_ruleset`          | None                  | Account-level ruleset            |
+| `ai_gateway`               | None                  | AI Gateway                       |
+| `alerting_policy`          | None                  | Notification policy              |
+| `alerting_webhook`         | None                  | Notification webhook destination |
+| `cloudflared_tunnel`       | None                  | Cloudflare Tunnel                |
+| `d1_database`              | None                  | D1 database                      |
+| `durable_object_namespace` | None                  | Durable Objects namespace        |
+| `gateway_list`             | None                  | Gateway list                     |
+| `gateway_rule`             | None                  | Gateway rule                     |
+| `image`                    | None                  | Cloudflare Image                 |
+| `kv_namespace`             | None                  | Workers KV namespace             |
+| `load_balancer_monitor`    | None                  | Load Balancer monitor            |
+| `load_balancer_pool`       | None                  | Load Balancer pool               |
+| `pages_project`            | None                  | Pages project                    |
+| `queue`                    | None                  | Queue                            |
+| `r2_bucket`                | None                  | R2 bucket                        |
+| `resource_share`           | None                  | Resource share                   |
+| `stream_live_input`        | None                  | Stream live input                |
+| `stream_video`             | None                  | Stream video                     |
+| `vectorize_index`          | None                  | Vectorize index                  |
+| `worker`                   | None                  | Workers script                   |
+| `worker_version`           | `worker_id`           | Specific version of a Worker     |
 
 ## Zone-level resources
 
 Use `/zones/{zone_id}/tags` endpoints for these resource types.
 
-| Resource type | Required extra fields | Description |
-| --- | --- | --- |
-| `access_application_policy` | `access_application_id` | Access application policy |
-| `api_gateway_operation` | None | API Gateway operation |
-| `custom_certificate` | None | Custom SSL certificate |
-| `custom_hostname` | None | Custom hostname (SSL for SaaS) |
-| `dns_record` | None | DNS record |
-| `healthcheck` | None | Health check |
-| `load_balancer` | None | Load Balancer |
-| `managed_client_certificate` | None | Managed client certificate (mTLS) |
-| `worker_route` | None | Worker route |
-| `zone` | None | DNS zone |
-| `zone_ruleset` | None | Zone-level ruleset |
+| Resource type                | Required extra fields   | Description                       |
+| ---------------------------- | ----------------------- | --------------------------------- |
+| `access_application_policy`  | `access_application_id` | Access application policy         |
+| `api_gateway_operation`      | None                    | API Gateway operation             |
+| `custom_certificate`         | None                    | Custom SSL certificate            |
+| `custom_hostname`            | None                    | Custom hostname (SSL for SaaS)    |
+| `dns_record`                 | None                    | DNS record                        |
+| `healthcheck`                | None                    | Health check                      |
+| `load_balancer`              | None                    | Load Balancer                     |
+| `managed_client_certificate` | None                    | Managed client certificate (mTLS) |
+| `worker_route`               | None                    | Worker route                      |
+| `zone`                       | None                    | DNS zone                          |
+| `zone_ruleset`               | None                    | Zone-level ruleset                |
 
 ## Extra fields
 
diff --git a/src/content/docs/rules/normalization/settings.mdx b/src/content/docs/rules/normalization/settings.mdx
index 5caa0fb2aa550f7..7243dde493afff1 100644
--- a/src/content/docs/rules/normalization/settings.mdx
+++ b/src/content/docs/rules/normalization/settings.mdx
@@ -35,8 +35,8 @@ Default value: _Off_
 
 Configures URLs sent to the origin:
 
-  - When enabled, requests sent to the origin are normalized.
-  - When disabled, requests sent to the origin are not modified.
+- When enabled, requests sent to the origin are normalized.
+- When disabled, requests sent to the origin are not modified.
 
 You can only view and enable this option when **Normalize incoming URLs** is enabled.
 
diff --git a/src/content/docs/rules/snippets/when-to-use.mdx b/src/content/docs/rules/snippets/when-to-use.mdx
index e86e4a0e07433ec..37954e262869ef1 100644
--- a/src/content/docs/rules/snippets/when-to-use.mdx
+++ b/src/content/docs/rules/snippets/when-to-use.mdx
@@ -86,7 +86,7 @@ Snippets are ideal for fast, cost-free request and response modifications at the
 | Route traffic dynamically between [origin servers](/rules/snippets/examples/serve-different-origin/)                                                                                                          |    ✅    |   ✅    |
 | [Authenticate](/rules/snippets/examples/auth-with-headers/) requests, [pre-sign](/cache/interaction-cloudflare-products/waf-snippets/) URLs, run [A/B testing](/rules/snippets/examples/ab-testing-same-url/) |    ✅    |   ✅    |
 | Define logic using [JavaScript and Web APIs](/workers/languages/javascript/)                                                                                                                                  |    ✅    |   ✅    |
-| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                                       |    ❌    |   ✅    |
+| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                           |    ❌    |   ✅    |
 | Store persistent data (for example, [KV](/kv/), [Durable Objects](/durable-objects/), and [D1](/d1/))                                                                                                         |    ❌    |   ✅    |
 | Build [APIs](/d1/tutorials/build-a-comments-api/) and [full-stack applications](/pages/framework-guides/deploy-an-astro-site/#video-tutorial)                                                                 |    ❌    |   ✅    |
 | Use TypeScript, Python, Rust, or other programming [languages](/workers/languages/)                                                                                                                           |    ❌    |   ✅    |
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
index 7167193080e4368..d28441888bab606 100644
--- a/src/content/docs/rules/transform/managed-transforms/reference.mdx
+++ b/src/content/docs/rules/transform/managed-transforms/reference.mdx
@@ -87,7 +87,6 @@ Turning on [IP geolocation](/network/ip-geolocation/) will send a `cf-ipcountry`
 
 Cloudflare always converts non-ASCII characters to UTF-8 in HTTP request and response header values. This applies to location headers added by the **Add visitor location headers** managed transform.
 
-
 ### Add "True-Client-IP" header
 
 :::note
diff --git a/src/content/docs/ruleset-engine/about/index.mdx b/src/content/docs/ruleset-engine/about/index.mdx
index 4627da09be58e13..b2b96116594e34b 100644
--- a/src/content/docs/ruleset-engine/about/index.mdx
+++ b/src/content/docs/ruleset-engine/about/index.mdx
@@ -9,18 +9,17 @@ sidebar:
 head:
   - tag: title
     content: About Ruleset Engine
-
 ---
 
 The Cloudflare Ruleset Engine allows you to create and deploy rules and rulesets. The engine syntax, inspired by the Wireshark Display Filter language, is defined by the [Rules language](/ruleset-engine/rules-language/). Cloudflare uses the Ruleset Engine in different products, allowing you to configure several products using the same basic syntax.
 
 There are several elements involved in the configuration and use of the Ruleset Engine. These elements are:
 
-* [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
-* [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
-* [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
+- [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
+- [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
+- [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
 
-***
+---
 
 ## Get started
 
diff --git a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
index 195f92316c007d2..4ead3afce0027eb 100644
--- a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
+++ b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
@@ -7,5 +7,4 @@ title: Adjust an L3/4 DDoS rule
 external_link: /ddos-protection/managed-rulesets/network/network-overrides/configure-api/#configure-an-override-for-the-network-layer-ddos-attack-protection-managed-ruleset
 sidebar:
   order: 7
-
 ---
diff --git a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
index 4e1b9c1603ab0bf..5e0d01303a761d5 100644
--- a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
+++ b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
@@ -34,14 +34,12 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 :::note
 
-
 The Rulesets API endpoints require a value for `{account_id}` or `{zone_id}`.
 
 To retrieve a list of accounts you have access to, use the [List Accounts](/api/resources/accounts/methods/list/) operation. Note the IDs of the accounts you want to manage.
 
 To retrieve a list of zones you have access to, use the [List Zones](/api/resources/zones/methods/list/) operation. Note the IDs of the zones you want to manage.
 
-
 :::
 
 The Cloudflare Rulesets API supports the operations outlined below. Visit the associated links for API endpoints and examples.
@@ -49,206 +47,235 @@ The Cloudflare Rulesets API supports the operations outlined below. Visit the as
 ## List and view rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Method</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">List existing rulesets</a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the list of existing rulesets at the account level or at the zone level.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">View a specific ruleset</a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the properties of the most recent version of a specific ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
-          List all versions of a ruleset
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns a list of all the versions of a ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
-          View a specific version of a ruleset
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns the configuration of a specific version of a ruleset, including its rules.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
-          List rules in a managed ruleset with a specific tag
-        </a>
-      </td>
-      <td>
-        <code>GET</code>
-      </td>
-      <td>
-        <p>Returns a list of all the rules in a managed ruleset with a specific tag.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Method</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">
+					List existing rulesets
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the list of existing rulesets at the account level or at the
+					zone level.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">
+					View a specific ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the properties of the most recent version of a specific
+					ruleset.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
+					List all versions of a ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>Returns a list of all the versions of a ruleset.</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
+					View a specific version of a ruleset
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns the configuration of a specific version of a ruleset,
+					including its rules.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
+					List rules in a managed ruleset with a specific tag
+				</a>
+			</td>
+			<td>
+				<code>GET</code>
+			</td>
+			<td>
+				<p>
+					Returns a list of all the rules in a managed ruleset with a specific
+					tag.
+				</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Create rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
-      </td>
-      <td>
-        <code>POST</code>
-      </td>
-      <td>
-        <p>Creates a new ruleset or a new phase entry point.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
+			</td>
+			<td>
+				<code>POST</code>
+			</td>
+			<td>
+				<p>Creates a new ruleset or a new phase entry point.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Update and deploy rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/update/">Update or deploy a ruleset</a>
-      </td>
-      <td>
-        <code>PUT</code>
-      </td>
-      <td>
-        <p>
-          Updates the basic properties of a ruleset and the list of rules in the ruleset.
-          <br />
-          Allows you to configure the execution of managed rulesets.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/add-rule/">Add a rule to a ruleset</a>
-      </td>
-      <td>
-        <code>POST</code>
-      </td>
-      <td>
-        <p>
-          Adds a single rule to an existing ruleset.
-          <br />
-          Allows you to add a single rule without having to include all the existing ruleset rules
-          in the request.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/update-rule/">Update a rule in a ruleset</a>
-      </td>
-      <td>
-        <code>PATCH</code>
-      </td>
-      <td>
-        <p>
-          Updates the definition of a single rule within a ruleset.
-          <br />
-          Allows you to change the order of a rule in a ruleset.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete-rule/">Delete a rule in a ruleset</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes a single rule in a ruleset.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/update/">
+					Update or deploy a ruleset
+				</a>
+			</td>
+			<td>
+				<code>PUT</code>
+			</td>
+			<td>
+				<p>
+					Updates the basic properties of a ruleset and the list of rules in the
+					ruleset.
+					<br />
+					Allows you to configure the execution of managed rulesets.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/add-rule/">
+					Add a rule to a ruleset
+				</a>
+			</td>
+			<td>
+				<code>POST</code>
+			</td>
+			<td>
+				<p>
+					Adds a single rule to an existing ruleset.
+					<br />
+					Allows you to add a single rule without having to include all the
+					existing ruleset rules in the request.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/update-rule/">
+					Update a rule in a ruleset
+				</a>
+			</td>
+			<td>
+				<code>PATCH</code>
+			</td>
+			<td>
+				<p>
+					Updates the definition of a single rule within a ruleset.
+					<br />
+					Allows you to change the order of a rule in a ruleset.
+				</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete-rule/">
+					Delete a rule in a ruleset
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes a single rule in a ruleset.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Delete rulesets
 
 <table>
-  <thead>
-    <tr>
-      <th>Operation</th>
-      <th>Verb</th>
-      <th>Notes</th>
-    </tr>
-  </thead>
-  <tbody style="vertical-align:top">
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">Delete a ruleset</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes all the versions of a ruleset.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">Delete a ruleset version</a>
-      </td>
-      <td>
-        <code>DELETE</code>
-      </td>
-      <td>
-        <p>Deletes a specific version of a ruleset.</p>
-      </td>
-    </tr>
-  </tbody>
+	<thead>
+		<tr>
+			<th>Operation</th>
+			<th>Verb</th>
+			<th>Notes</th>
+		</tr>
+	</thead>
+	<tbody style="vertical-align:top">
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">
+					Delete a ruleset
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes all the versions of a ruleset.</p>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">
+					Delete a ruleset version
+				</a>
+			</td>
+			<td>
+				<code>DELETE</code>
+			</td>
+			<td>
+				<p>Deletes a specific version of a ruleset.</p>
+			</td>
+		</tr>
+	</tbody>
 </table>
diff --git a/src/content/docs/sandbox/bridge/http-api.mdx b/src/content/docs/sandbox/bridge/http-api.mdx
index 8454191fa57021e..ba425ec0d9cf393 100644
--- a/src/content/docs/sandbox/bridge/http-api.mdx
+++ b/src/content/docs/sandbox/bridge/http-api.mdx
@@ -28,10 +28,10 @@ When `SANDBOX_API_KEY` is not configured, authentication is skipped for local de
 
 The bridge serves its own API documentation:
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
-| `GET` | `/v1/openapi` | Interactive HTML documentation. |
+| Method | Route              | Description                          |
+| ------ | ------------------ | ------------------------------------ |
+| `GET`  | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
+| `GET`  | `/v1/openapi`      | Interactive HTML documentation.      |
 
 Both routes accept authentication via Bearer header or `?token=` query parameter.
 
@@ -39,25 +39,25 @@ When running locally with `npm run dev`, open `http://localhost:8787/v1/openapi`
 
 ## Sandbox lifecycle
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox` | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id` | Destroy the sandbox container. Returns `204`. |
-| `GET` | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
+| Method   | Route                     | Description                                                   |
+| -------- | ------------------------- | ------------------------------------------------------------- |
+| `POST`   | `/v1/sandbox`             | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`.       |
+| `DELETE` | `/v1/sandbox/:id`         | Destroy the sandbox container. Returns `204`.                 |
+| `GET`    | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
 
 ## Command execution
 
-| Method | Route | Description |
-|---|---|---|
+| Method | Route                  | Description                                           |
+| ------ | ---------------------- | ----------------------------------------------------- |
 | `POST` | `/v1/sandbox/:id/exec` | Run a command. Response is an SSE stream (see below). |
 
 The `/exec` endpoint accepts a JSON body:
 
 ```json
 {
-  "argv": ["sh", "-lc", "echo hello"],
-  "timeout_ms": 10000,
-  "cwd": "/workspace"
+	"argv": ["sh", "-lc", "echo hello"],
+	"timeout_ms": 10000,
+	"cwd": "/workspace"
 }
 ```
 
@@ -69,27 +69,27 @@ Each element of the `argv` array is escaped using ANSI-C `$'...'` quoting before
 
 The response is a `text/event-stream` with the following event types:
 
-| Event | Data | Description |
-|---|---|---|
-| `stdout` | Base64-encoded chunk | Standard output from the command. |
-| `stderr` | Base64-encoded chunk | Standard error from the command. |
-| `exit` | `{"exit_code": N}` | Command completed. Terminal event. |
-| `error` | `{"error": "…", "code": "…"}` | Command failed. Terminal event. |
+| Event    | Data                          | Description                        |
+| -------- | ----------------------------- | ---------------------------------- |
+| `stdout` | Base64-encoded chunk          | Standard output from the command.  |
+| `stderr` | Base64-encoded chunk          | Standard error from the command.   |
+| `exit`   | `{"exit_code": N}`            | Command completed. Terminal event. |
+| `error`  | `{"error": "…", "code": "…"}` | Command failed. Terminal event.    |
 
 ## File operations
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`). |
-| `PUT` | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
+| Method | Route                    | Description                                                                  |
+| ------ | ------------------------ | ---------------------------------------------------------------------------- |
+| `GET`  | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`).                 |
+| `PUT`  | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
 
 The file path is encoded in the URL after `/file/`. All paths must resolve within `/workspace`. Path traversal attempts (for example, `../../etc/passwd`) are rejected.
 
 ## Workspace persistence
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes. |
+| Method | Route                     | Description                                                        |
+| ------ | ------------------------- | ------------------------------------------------------------------ |
+| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes.    |
 | `POST` | `/v1/sandbox/:id/hydrate` | Populate `/workspace` from a tar archive sent as the request body. |
 
 The `/persist` endpoint accepts an optional `excludes` query parameter — a comma-separated list of relative paths to exclude from the archive.
@@ -98,10 +98,10 @@ The `/hydrate` endpoint accepts a raw tar payload up to 32 MiB.
 
 ## Bucket mounts
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/mount` | Mount an S3-compatible bucket as a local directory. |
-| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket. |
+| Method | Route                     | Description                                         |
+| ------ | ------------------------- | --------------------------------------------------- |
+| `POST` | `/v1/sandbox/:id/mount`   | Mount an S3-compatible bucket as a local directory. |
+| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket.                |
 
 The `/mount` endpoint accepts a JSON body. Two flows are supported:
 
@@ -111,12 +111,12 @@ Omit `endpoint` and pass the Worker R2 binding name in `bucket`:
 
 ```json
 {
-  "bucket": "MY_BUCKET",
-  "mountPath": "/mnt/data",
-  "options": {
-    "readOnly": false,
-    "prefix": "/subdir"
-  }
+	"bucket": "MY_BUCKET",
+	"mountPath": "/mnt/data",
+	"options": {
+		"readOnly": false,
+		"prefix": "/subdir"
+	}
 }
 ```
 
@@ -126,17 +126,17 @@ For an explicit S3-compatible endpoint mount, include `endpoint` and optionally
 
 ```json
 {
-  "bucket": "my-r2-bucket",
-  "mountPath": "/mnt/data",
-  "options": {
-    "endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
-    "readOnly": false,
-    "prefix": "/subdir",
-    "credentials": {
-      "accessKeyId": "...",
-      "secretAccessKey": "..."
-    }
-  }
+	"bucket": "my-r2-bucket",
+	"mountPath": "/mnt/data",
+	"options": {
+		"endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
+		"readOnly": false,
+		"prefix": "/subdir",
+		"credentials": {
+			"accessKeyId": "...",
+			"secretAccessKey": "..."
+		}
+	}
 }
 ```
 
@@ -144,10 +144,10 @@ When `endpoint` is provided, `bucket` means the remote bucket name. Credentials
 
 ## Sessions
 
-| Method | Route | Description |
-|---|---|---|
-| `POST` | `/v1/sandbox/:id/session` | Create a session. Returns `{"id": "<session-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`. |
+| Method   | Route                          | Description                                         |
+| -------- | ------------------------------ | --------------------------------------------------- |
+| `POST`   | `/v1/sandbox/:id/session`      | Create a session. Returns `{"id": "<session-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`.                    |
 
 Sessions isolate working directory, environment variables, and command execution state within a sandbox. Pass the `Session-Id` header on `/exec`, `/file/*`, and `/pty` requests to scope them to a session.
 
@@ -155,35 +155,35 @@ When no `Session-Id` header is provided, requests use the sandbox default sessio
 
 ## Terminal (PTY)
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
+| Method | Route                 | Description                         |
+| ------ | --------------------- | ----------------------------------- |
+| `GET`  | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
 
 Query parameters:
 
-| Parameter | Type | Default | Description |
-|---|---|---|---|
-| `cols` | number | `80` | Terminal width in columns. |
-| `rows` | number | `24` | Terminal height in rows. |
-| `shell` | string | — | Shell binary (for example, `/bin/bash`). |
-| `session` | string | — | Session ID for session-scoped PTY. |
+| Parameter | Type   | Default | Description                              |
+| --------- | ------ | ------- | ---------------------------------------- |
+| `cols`    | number | `80`    | Terminal width in columns.               |
+| `rows`    | number | `24`    | Terminal height in rows.                 |
+| `shell`   | string | —       | Shell binary (for example, `/bin/bash`). |
+| `session` | string | —       | Session ID for session-scoped PTY.       |
 
 The WebSocket carries binary frames for terminal I/O and JSON text frames for control messages:
 
-| Direction | Frame type | Content |
-|---|---|---|
-| Client to server | Binary | UTF-8 encoded keystrokes. |
-| Server to client | Binary | Terminal output including ANSI escape sequences. |
+| Direction        | Frame type  | Content                                                                        |
+| ---------------- | ----------- | ------------------------------------------------------------------------------ |
+| Client to server | Binary      | UTF-8 encoded keystrokes.                                                      |
+| Server to client | Binary      | Terminal output including ANSI escape sequences.                               |
 | Client to server | Text (JSON) | Control messages (for example, `{"type": "resize", "cols": 120, "rows": 30}`). |
-| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`). |
+| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`).                                    |
 
 ## Warm pool
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/v1/pool/stats` | Current pool statistics. |
-| `POST` | `/v1/pool/prime` | Start the warm pool alarm loop. |
-| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers. |
+| Method | Route                         | Description                     |
+| ------ | ----------------------------- | ------------------------------- |
+| `GET`  | `/v1/pool/stats`              | Current pool statistics.        |
+| `POST` | `/v1/pool/prime`              | Start the warm pool alarm loop. |
+| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers.  |
 
 The warm pool pre-starts sandbox containers so new sessions boot instantly. Configure it with environment variables in `wrangler.jsonc`:
 
@@ -201,9 +201,9 @@ A cron trigger (`* * * * *`) primes the pool automatically after deployment. Set
 
 ## Health check
 
-| Method | Route | Description |
-|---|---|---|
-| `GET` | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
+| Method | Route     | Description                                             |
+| ------ | --------- | ------------------------------------------------------- |
+| `GET`  | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
 
 ## Related resources
 
diff --git a/src/content/docs/sandbox/concepts/containers.mdx b/src/content/docs/sandbox/concepts/containers.mdx
index dd9a725669a262e..e1a711233feb34b 100644
--- a/src/content/docs/sandbox/concepts/containers.mdx
+++ b/src/content/docs/sandbox/concepts/containers.mdx
@@ -30,16 +30,18 @@ apt-get update && apt-get install -y redis-server
 The container provides a standard Linux filesystem. You can read and write anywhere you have permissions.
 
 **Standard directories**:
+
 - `/workspace` - Default working directory for user code
 - `/tmp` - Temporary files
 - `/home` - User home directory
 - `/usr/bin`, `/usr/local/bin` - Executable binaries
 
 **Example**:
+
 ```typescript
-await sandbox.writeFile('/workspace/app.py', 'print("Hello")');
-await sandbox.writeFile('/tmp/cache.json', '{}');
-await sandbox.exec('ls -la /workspace');
+await sandbox.writeFile("/workspace/app.py", 'print("Hello")');
+await sandbox.writeFile("/tmp/cache.json", "{}");
+await sandbox.exec("ls -la /workspace");
 ```
 
 ## Process management
@@ -47,20 +49,23 @@ await sandbox.exec('ls -la /workspace');
 Processes run as you'd expect in a regular Linux environment.
 
 **Foreground processes** (`exec()`):
+
 ```typescript
-const result = await sandbox.exec('npm test');
+const result = await sandbox.exec("npm test");
 // Waits for completion, returns output
 ```
 
 **Background processes** (`startProcess()`):
+
 ```typescript
-const process = await sandbox.startProcess('node server.js');
+const process = await sandbox.startProcess("node server.js");
 // Returns immediately, process runs in background
 ```
 
 ## Network capabilities
 
 **Outbound connections** work:
+
 ```bash
 curl https://api.example.com/data
 pip install requests
@@ -68,9 +73,10 @@ npm install express
 ```
 
 **Inbound connections** require port exposure:
+
 ```typescript
 const { hostname } = new URL(request.url);
-await sandbox.startProcess('python -m http.server 8000');
+await sandbox.startProcess("python -m http.server 8000");
 const exposed = await sandbox.exposePort(8000, { hostname });
 console.log(exposed.url); // Public URL
 ```
@@ -80,6 +86,7 @@ When using `wrangler dev`, you must add `EXPOSE` directives to your Dockerfile f
 :::
 
 **Localhost** works within sandbox:
+
 ```bash
 redis-server &      # Start server
 redis-cli ping      # Connect locally
@@ -88,15 +95,18 @@ redis-cli ping      # Connect locally
 ## Security
 
 **Between sandboxes** (isolated):
+
 - Each sandbox is a separate container
 - Filesystem, memory and network are all isolated
 
 **Within sandbox** (shared):
+
 - All processes see the same files
 - Processes can communicate with each other
 - Environment variables are session-scoped
 
 To run untrusted code, use separate sandboxes per user:
+
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
@@ -104,6 +114,7 @@ const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ## Limitations
 
 **Cannot**:
+
 - Load kernel modules or access host hardware
 
 ## Related resources
diff --git a/src/content/docs/sandbox/concepts/preview-urls.mdx b/src/content/docs/sandbox/concepts/preview-urls.mdx
index 7fdf50c71ce90b4..43eecbf9c151321 100644
--- a/src/content/docs/sandbox/concepts/preview-urls.mdx
+++ b/src/content/docs/sandbox/concepts/preview-urls.mdx
@@ -24,9 +24,9 @@ const req = await fetch(`${tunnel.url}/api/users`); // => GET http://localhost:8
 
 Cloudflare Tunnel support currently has the following limitations:
 
- - No control over generated URL.
- - No authentication mechanism beyond randomly generated URL.
- - Each URL uses an additional `cloudflared` process on the sandbox.
+- No control over generated URL.
+- No authentication mechanism beyond randomly generated URL.
+- Each URL uses an additional `cloudflared` process on the sandbox.
 
 :::note[Production requires custom domain]
 We are working on production deployments, custom hostnames and authentication for Cloudflare Tunnel support. In the mean time we recommend using `exposePort()` and `proxyToSandbox()` documented below under [Production usage, stable URLs and custom domains](#).
diff --git a/src/content/docs/sandbox/concepts/sandboxes.mdx b/src/content/docs/sandbox/concepts/sandboxes.mdx
index e0828106d246dbd..cd86f4ac0b8f21d 100644
--- a/src/content/docs/sandbox/concepts/sandboxes.mdx
+++ b/src/content/docs/sandbox/concepts/sandboxes.mdx
@@ -126,8 +126,8 @@ try {
 Containers with [`keepAlive: true`](/sandbox/configuration/sandbox-options/#keepalive) require explicit management since they do not timeout automatically:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, 'persistent-task', {
-  keepAlive: true
+const sandbox = getSandbox(env.Sandbox, "persistent-task", {
+	keepAlive: true,
 });
 
 // Later, when done with long-running work
diff --git a/src/content/docs/sandbox/concepts/security.mdx b/src/content/docs/sandbox/concepts/security.mdx
index 5c15d8d4295ba00..9954cb9833e9732 100644
--- a/src/content/docs/sandbox/concepts/security.mdx
+++ b/src/content/docs/sandbox/concepts/security.mdx
@@ -36,7 +36,7 @@ For complete isolation, use separate sandboxes per user:
 const userSandbox = getSandbox(env.Sandbox, `user-${userId}`);
 
 // Bad - Users sharing one sandbox
-const shared = getSandbox(env.Sandbox, 'shared');
+const shared = getSandbox(env.Sandbox, "shared");
 // Users can read each other's files!
 ```
 
@@ -53,12 +53,12 @@ await sandbox.exec(`cat ${filename}`);
 // User could input: "file.txt; rm -rf /"
 
 // Safe - validate input
-const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, '');
+const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, "");
 await sandbox.exec(`cat ${filename}`);
 
 // Better - use file API
-await sandbox.writeFile('/tmp/input', userInput);
-await sandbox.exec('cat /tmp/input');
+await sandbox.writeFile("/tmp/input", userInput);
+await sandbox.exec("cat /tmp/input");
 ```
 
 ## Authentication
@@ -69,16 +69,16 @@ Sandbox IDs provide basic access control but aren't cryptographically secure. Ad
 
 ```typescript
 export default {
-  async fetch(request: Request, env: Env): Promise<Response> {
-    const userId = await authenticate(request);
-    if (!userId) {
-      return new Response('Unauthorized', { status: 401 });
-    }
-
-    // User can only access their sandbox
-    const sandbox = getSandbox(env.Sandbox, userId);
-    return Response.json({ authorized: true });
-  }
+	async fetch(request: Request, env: Env): Promise<Response> {
+		const userId = await authenticate(request);
+		if (!userId) {
+			return new Response("Unauthorized", { status: 401 });
+		}
+
+		// User can only access their sandbox
+		const sandbox = getSandbox(env.Sandbox, userId);
+		return Response.json({ authorized: true });
+	},
 };
 ```
 
@@ -125,15 +125,18 @@ Use environment variables, not hardcoded secrets:
 
 ```typescript
 // Bad - hardcoded in file
-await sandbox.writeFile('/workspace/config.js', `
+await sandbox.writeFile(
+	"/workspace/config.js",
+	`
   const API_KEY = 'sk_live_abc123';
-`);
+`,
+);
 
 // Good - use environment variables
-await sandbox.startProcess('node app.js', {
-  env: {
-    API_KEY: env.API_KEY,  // From Worker environment binding
-  }
+await sandbox.startProcess("node app.js", {
+	env: {
+		API_KEY: env.API_KEY, // From Worker environment binding
+	},
 });
 ```
 
@@ -141,10 +144,10 @@ Clean up temporary sensitive data:
 
 ```typescript
 try {
-  await sandbox.writeFile('/tmp/sensitive.txt', secretData);
-  await sandbox.exec('python process.py /tmp/sensitive.txt');
+	await sandbox.writeFile("/tmp/sensitive.txt", secretData);
+	await sandbox.exec("python process.py /tmp/sensitive.txt");
 } finally {
-  await sandbox.deleteFile('/tmp/sensitive.txt');
+	await sandbox.deleteFile("/tmp/sensitive.txt");
 }
 ```
 
@@ -178,30 +181,34 @@ This pattern is useful when accessing GitHub for private repository operations,
 ## Best practices
 
 **Use separate sandboxes for isolation**:
+
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
 
 **Validate all inputs**:
+
 ```typescript
-const safe = input.replace(/[^a-zA-Z0-9._-]/g, '');
+const safe = input.replace(/[^a-zA-Z0-9._-]/g, "");
 await sandbox.exec(`command ${safe}`);
 ```
 
 **Use environment variables for secrets**:
+
 ```typescript
-await sandbox.startProcess('node app.js', {
-  env: { API_KEY: env.API_KEY }
+await sandbox.startProcess("node app.js", {
+	env: { API_KEY: env.API_KEY },
 });
 ```
 
 **Clean up temporary resources**:
+
 ```typescript
 try {
-  const sandbox = getSandbox(env.Sandbox, sessionId);
-  await sandbox.exec('npm test');
+	const sandbox = getSandbox(env.Sandbox, sessionId);
+	await sandbox.exec("npm test");
 } finally {
-  await sandbox.destroy();
+	await sandbox.destroy();
 }
 ```
 
diff --git a/src/content/docs/sandbox/concepts/sessions.mdx b/src/content/docs/sandbox/concepts/sessions.mdx
index 1697cf6e8795d7f..dd054b3036ce8f7 100644
--- a/src/content/docs/sandbox/concepts/sessions.mdx
+++ b/src/content/docs/sandbox/concepts/sessions.mdx
@@ -18,14 +18,14 @@ Sessions are bash shell execution contexts within a sandbox. Think of them like
 Every sandbox has a default session that maintains shell state between commands while the container is active:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
+const sandbox = getSandbox(env.Sandbox, "my-sandbox");
 
 // These commands run in the default session
 await sandbox.exec("cd /app");
-await sandbox.exec("pwd");  // Output: /app
+await sandbox.exec("pwd"); // Output: /app
 
 await sandbox.exec("export MY_VAR=hello");
-await sandbox.exec("echo $MY_VAR");  // Output: hello
+await sandbox.exec("echo $MY_VAR"); // Output: hello
 ```
 
 Working directory, environment variables, and exported variables carry over between commands. This state resets if the container restarts due to inactivity.
@@ -36,7 +36,7 @@ The container automatically creates sessions on first use. If you reference a no
 
 ```typescript
 // This session doesn't exist yet
-const result = await sandbox.exec('echo hello', { sessionId: 'new-session' });
+const result = await sandbox.exec("echo hello", { sessionId: "new-session" });
 // Container automatically creates 'new-session' with defaults:
 // - cwd: '/workspace'
 // - env: {} (empty)
@@ -47,15 +47,15 @@ This behavior is particularly relevant after deleting a session:
 ```typescript
 // Create and configure a session
 const session = await sandbox.createSession({
-  id: 'temp',
-  env: { MY_VAR: 'value' }
+	id: "temp",
+	env: { MY_VAR: "value" },
 });
 
 // Delete the session
-await sandbox.deleteSession('temp');
+await sandbox.deleteSession("temp");
 
 // Using the same session ID again works - auto-created with defaults
-const result = await sandbox.exec('echo $MY_VAR', { sessionId: 'temp' });
+const result = await sandbox.exec("echo $MY_VAR", { sessionId: "temp" });
 // Output: (empty) - MY_VAR is not set in the freshly created session
 ```
 
@@ -67,15 +67,15 @@ Create additional sessions for isolated shell contexts:
 
 ```typescript
 const buildSession = await sandbox.createSession({
-  id: "build",
-  env: { NODE_ENV: "production" },
-  cwd: "/build"
+	id: "build",
+	env: { NODE_ENV: "production" },
+	cwd: "/build",
 });
 
 const testSession = await sandbox.createSession({
-  id: "test",
-  env: { NODE_ENV: "test" },
-  cwd: "/test"
+	id: "test",
+	env: { NODE_ENV: "test" },
+	cwd: "/test",
 });
 
 // Different shell contexts
@@ -87,8 +87,8 @@ You can also set a default command timeout for all commands in a session:
 
 ```typescript
 const session = await sandbox.createSession({
-  id: "ci",
-  commandTimeoutMs: 30000 // 30s timeout for all commands
+	id: "ci",
+	commandTimeoutMs: 30000, // 30s timeout for all commands
 });
 
 await session.exec("npm test"); // Times out after 30s if still running
@@ -101,24 +101,27 @@ Individual commands can override the session timeout with the `timeout` option o
 Each session has its own:
 
 **Shell environment**:
+
 ```typescript
 await session1.exec("export MY_VAR=hello");
-await session2.exec("echo $MY_VAR");  // Empty - different shell
+await session2.exec("echo $MY_VAR"); // Empty - different shell
 ```
 
 **Working directory**:
+
 ```typescript
 await session1.exec("cd /workspace/project1");
-await session2.exec("pwd");  // Different working directory
+await session2.exec("pwd"); // Different working directory
 ```
 
 **Environment variables** (set via `createSession` options):
+
 ```typescript
 const session1 = await sandbox.createSession({
-  env: { API_KEY: 'key-1' }
+	env: { API_KEY: "key-1" },
 });
 const session2 = await sandbox.createSession({
-  env: { API_KEY: 'key-2' }
+	env: { API_KEY: "key-2" },
 });
 ```
 
@@ -127,42 +130,47 @@ const session2 = await sandbox.createSession({
 All sessions in a sandbox share:
 
 **Filesystem**:
+
 ```typescript
-await session1.writeFile('/workspace/file.txt', 'data');
-await session2.readFile('/workspace/file.txt');  // Can read it
+await session1.writeFile("/workspace/file.txt", "data");
+await session2.readFile("/workspace/file.txt"); // Can read it
 ```
 
 **Processes**:
+
 ```typescript
-await session1.startProcess('node server.js');
-await session2.listProcesses();  // Sees the server
+await session1.startProcess("node server.js");
+await session2.listProcesses(); // Sees the server
 ```
 
 ## When to use sessions
 
 **Use sessions when**:
+
 - You need isolated shell state for different tasks
 - Running parallel operations with different environments
 - Keeping AI agent credentials separate from app runtime
 
 **Example - separate dev and runtime environments**:
+
 ```typescript
 // Phase 1: AI agent writes code (with API keys)
 const devSession = await sandbox.createSession({
-  id: "dev",
-  env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY }
+	id: "dev",
+	env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY },
 });
 await devSession.exec('ai-tool "build a web server"');
 
 // Phase 2: Run the code (without API keys)
 const appSession = await sandbox.createSession({
-  id: "app",
-  env: { PORT: "3000" }
+	id: "app",
+	env: { PORT: "3000" },
 });
 await appSession.exec("node server.js");
 ```
 
 **Use separate sandboxes when**:
+
 - You need complete isolation (untrusted code)
 - Different users require fully separated environments
 - Independent resource allocation is needed
@@ -172,28 +180,31 @@ await appSession.exec("node server.js");
 ### Session cleanup
 
 **Clean up temporary sessions** to free resources while keeping the sandbox running:
+
 ```typescript
 try {
-  const session = await sandbox.createSession({ id: 'temp' });
-  await session.exec('command');
+	const session = await sandbox.createSession({ id: "temp" });
+	await session.exec("command");
 } finally {
-  await sandbox.deleteSession('temp');
+	await sandbox.deleteSession("temp");
 }
 ```
 
 **Default session cannot be deleted**:
+
 ```typescript
 // This throws an error
-await sandbox.deleteSession('default');
+await sandbox.deleteSession("default");
 // Error: Cannot delete default session. Use sandbox.destroy() instead.
 ```
 
 ### Filesystem isolation
 
 **Sessions share filesystem** - file operations affect all sessions:
+
 ```typescript
 // Bad - affects all sessions
-await session.exec('rm -rf /workspace/*');
+await session.exec("rm -rf /workspace/*");
 
 // For untrusted code isolation, use separate sandboxes
 const userSandbox = getSandbox(env.Sandbox, userId);
diff --git a/src/content/docs/sandbox/configuration/environment-variables.mdx b/src/content/docs/sandbox/configuration/environment-variables.mdx
index 522821f21e1c931..2bd802277756cba 100644
--- a/src/content/docs/sandbox/configuration/environment-variables.mdx
+++ b/src/content/docs/sandbox/configuration/environment-variables.mdx
@@ -18,10 +18,10 @@ These environment variables configure how the Sandbox SDK behaves. Set these as
 
 ### SANDBOX_TRANSPORT
 
-| | |
-|---|---|
-| **Type** | `"http"` \| `"websocket"` |
-| **Default** | `"http"` |
+|             |                           |
+| ----------- | ------------------------- |
+| **Type**    | `"http"` \| `"websocket"` |
+| **Default** | `"http"`                  |
 
 Controls the transport protocol for SDK-to-container communication. WebSocket transport multiplexes all operations over a single persistent connection, avoiding [subrequest limits](/workers/platform/limits/#subrequests) when performing many SDK operations per request.
 
@@ -39,10 +39,10 @@ See [Transport modes](/sandbox/configuration/transport/) for a complete guide in
 
 ### COMMAND_TIMEOUT_MS
 
-| | |
-|---|---|
-| **Type** | `number` (milliseconds) |
-| **Default** | None (no timeout) |
+|             |                         |
+| ----------- | ----------------------- |
+| **Type**    | `number` (milliseconds) |
+| **Default** | None (no timeout)       |
 
 Sets a global default timeout for every `exec()` call. When set, any command that exceeds this duration raises an error on the caller side and closes the connection.
 
@@ -95,9 +95,9 @@ await sandbox.setEnvVars({
 
 ```typescript
 await sandbox.setEnvVars({
-	API_KEY: 'new-key',     // Sets API_KEY
-	OLD_SECRET: undefined,  // Unsets OLD_SECRET
-	DEBUG_MODE: null        // Unsets DEBUG_MODE
+	API_KEY: "new-key", // Sets API_KEY
+	OLD_SECRET: undefined, // Unsets OLD_SECRET
+	DEBUG_MODE: null, // Unsets DEBUG_MODE
 });
 ```
 
@@ -153,12 +153,12 @@ The Sandbox SDK supports unsetting environment variables by passing `undefined`
 ```typescript
 await sandbox.setEnvVars({
 	// Set new values
-	API_KEY: 'new-key',
+	API_KEY: "new-key",
 	DATABASE_URL: env.DATABASE_URL,
 
 	// Unset variables (removes them from the environment)
 	OLD_API_KEY: undefined,
-	TEMP_TOKEN: null
+	TEMP_TOKEN: null,
 });
 ```
 
@@ -172,7 +172,7 @@ await sandbox.setEnvVars({
 
 ```typescript
 // Use a temporary token
-await sandbox.setEnvVars({ TEMP_TOKEN: 'abc123' });
+await sandbox.setEnvVars({ TEMP_TOKEN: "abc123" });
 await sandbox.exec('curl -H "Authorization: $TEMP_TOKEN" api.example.com');
 
 // Clean up the token
@@ -184,8 +184,8 @@ await sandbox.setEnvVars({ TEMP_TOKEN: undefined });
 ```typescript
 await sandbox.setEnvVars({
 	API_KEY: env.API_KEY,
-	DEBUG_MODE: env.NODE_ENV === 'development' ? 'true' : undefined,
-	PROFILING: env.ENABLE_PROFILING ? 'true' : undefined
+	DEBUG_MODE: env.NODE_ENV === "development" ? "true" : undefined,
+	PROFILING: env.ENABLE_PROFILING ? "true" : undefined,
 });
 ```
 
diff --git a/src/content/docs/sandbox/configuration/transport.mdx b/src/content/docs/sandbox/configuration/transport.mdx
index dce27bacce1ff87..18e5f33fc1b515d 100644
--- a/src/content/docs/sandbox/configuration/transport.mdx
+++ b/src/content/docs/sandbox/configuration/transport.mdx
@@ -22,7 +22,6 @@ The Sandbox SDK supports three transport modes for communication between the Dur
 - **NEW: RPC transport** - All SDK operations are multiplexed over a single persistent WebSocket connection. Will replace HTTP as the default transport in future. Available since 0.9.1.
 - **Deprecated: WebSocket transport** - All SDK operations are multiplexed over a single persistent WebSocket. Superseded by RPC transport which uses an improved protocol.
 
-
 ## When to use RPC transport
 
 Use the RPC transport when your Worker or Durable Object makes many SDK operations per request. This avoids hitting [subrequest limits](/workers/platform/limits/#subrequests).
@@ -112,11 +111,13 @@ No application code changes are needed. The SDK automatically uses the configure
 ### Connection lifecycle
 
 **HTTP transport:**
+
 - Creates a new HTTP request for each SDK operation
 - No persistent connection
 - Each request is independent and stateless
 
 **RPC transport:**
+
 - Establishes a WebSocket connection on the first SDK operation
 - Maintains the persistent connection for all subsequent operations
 - Connection is closed when the sandbox sleeps or is evicted
@@ -136,6 +137,7 @@ Your code remains identical regardless of transport mode.
 All transports provide identical error handling behavior. The SDK automatically retries on transient errors (like 503 responses) with exponential backoff.
 
 WebSocket-specific behavior:
+
 - Connection failures trigger automatic reconnection
 - The SDK transparently handles WebSocket disconnections
 - In-flight operations are not lost during reconnection
@@ -154,7 +156,6 @@ Switching between transports requires no code changes.
 Using the `rpc` transport requires version 0.9.1 or newer. If you are using an older version of the Sandbox SDK upgrade and deploy your application with the newer `@cloudflare/sandbox` and image first. Otherwise there will be issues with newer SDK clients attempting to connect to older sandboxes that do not support the new transport.
 :::
 
-
 Add `SANDBOX_TRANSPORT` to your `wrangler.jsonc`:
 
 <WranglerConfig>
diff --git a/src/content/docs/sandbox/guides/production-deployment.mdx b/src/content/docs/sandbox/guides/production-deployment.mdx
index 27c08a0c143f74a..c0f0ed75abf6508 100644
--- a/src/content/docs/sandbox/guides/production-deployment.mdx
+++ b/src/content/docs/sandbox/guides/production-deployment.mdx
@@ -24,10 +24,11 @@ The `.workers.dev` domain does not support wildcard subdomains, so production de
 If your worker runs on a subdomain (for example, `sandbox.yourdomain.com`), preview URLs become second-level wildcards like `*.sandbox.yourdomain.com`. Cloudflare's Universal SSL only covers first-level wildcards (`*.yourdomain.com`), so you need a certificate covering `*.sandbox.yourdomain.com`. Without it, preview URLs will fail with TLS handshake errors.
 
 You have three options:
+
 - **Deploy on the apex domain** (`yourdomain.com`) so preview URLs stay at the first level (`*.yourdomain.com`), which Universal SSL covers automatically. This is the simplest option.
 - **Use [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/)** ($10/month) to provision a certificate for `*.sandbox.yourdomain.com` through the Cloudflare dashboard.
 - **Upload a custom certificate** from a provider like [Let's Encrypt](https://letsencrypt.org/) (free). Generate a wildcard certificate for `*.sandbox.yourdomain.com` using the DNS-01 challenge, then upload it via the Cloudflare dashboard under **SSL/TLS > Edge Certificates > [Custom Certificates](/ssl/edge-certificates/custom-certificates/)**. You will need to renew it before expiry.
-:::
+  :::
 
 ## Prerequisites
 
@@ -42,7 +43,7 @@ You have three options:
 In the Cloudflare dashboard, go to your domain and create an A record:
 
 - **Type**: A
-- **Name**: * (wildcard)
+- **Name**: \* (wildcard)
 - **IPv4 address**: 192.0.2.0
 - **Proxy status**: Proxied (orange cloud)
 
@@ -87,8 +88,8 @@ Test that preview URLs work:
 // Extract hostname from request
 const { hostname } = new URL(request.url);
 
-const sandbox = getSandbox(env.Sandbox, 'test-sandbox');
-await sandbox.startProcess('python -m http.server 8080');
+const sandbox = getSandbox(env.Sandbox, "test-sandbox");
+await sandbox.startProcess("python -m http.server 8080");
 const exposed = await sandbox.exposePort(8080, { hostname });
 
 console.log(exposed.url);
diff --git a/src/content/docs/sandbox/platform/pricing.mdx b/src/content/docs/sandbox/platform/pricing.mdx
index cc9fe5632a5b833..cf39a5eba58829c 100644
--- a/src/content/docs/sandbox/platform/pricing.mdx
+++ b/src/content/docs/sandbox/platform/pricing.mdx
@@ -13,6 +13,7 @@ Sandbox SDK pricing is determined by the underlying [Containers](/containers/) p
 ## Containers Pricing
 
 Refer to [Containers pricing](/containers/pricing/) for complete details on:
+
 - vCPU, memory, and disk usage rates
 - Network egress pricing
 - Instance types and their costs
@@ -20,6 +21,7 @@ Refer to [Containers pricing](/containers/pricing/) for complete details on:
 ## Related Pricing
 
 When using Sandbox, you'll also be billed for:
+
 - [Workers](/workers/platform/pricing/) - Handles incoming requests to your sandbox
 - [Durable Objects](/durable-objects/platform/pricing/) - Powers each sandbox instance
 - [Workers Logs](/workers/observability/logs/workers-logs/#pricing) - Optional observability (if enabled)
diff --git a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
index 992afa80321cc03..5e0e4d91dfa660e 100644
--- a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
+++ b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
@@ -25,6 +25,7 @@ An API that accepts questions like "What's the 100th Fibonacci number?", uses Cl
 <Render file="prereqs" product="workers" />
 
 You'll also need:
+
 - An [Anthropic API key](https://console.anthropic.com/) for Claude
 - [Docker](https://www.docker.com/) running locally
 
@@ -52,11 +53,11 @@ Install the Anthropic SDK:
 
 Replace the contents of `src/index.ts`:
 
-```typescript
-import { getSandbox, type Sandbox } from '@cloudflare/sandbox';
-import Anthropic from '@anthropic-ai/sdk';
+````typescript
+import { getSandbox, type Sandbox } from "@cloudflare/sandbox";
+import Anthropic from "@anthropic-ai/sdk";
 
-export { Sandbox } from '@cloudflare/sandbox';
+export { Sandbox } from "@cloudflare/sandbox";
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -65,7 +66,10 @@ interface Env {
 
 export default {
 	async fetch(request: Request, env: Env): Promise<Response> {
-		if (request.method !== 'POST' || new URL(request.url).pathname !== '/execute') {
+		if (
+			request.method !== "POST" ||
+			new URL(request.url).pathname !== "/execute"
+		) {
 			return new Response('POST /execute with { "question": "your question" }');
 		}
 
@@ -73,65 +77,74 @@ export default {
 			const { question } = await request.json();
 
 			if (!question) {
-				return Response.json({ error: 'Question is required' }, { status: 400 });
+				return Response.json(
+					{ error: "Question is required" },
+					{ status: 400 },
+				);
 			}
 
 			// Use Claude to generate Python code
 			const anthropic = new Anthropic({ apiKey: env.ANTHROPIC_API_KEY });
 			const codeGeneration = await anthropic.messages.create({
-				model: 'claude-sonnet-4-5',
+				model: "claude-sonnet-4-5",
 				max_tokens: 1024,
-				messages: [{
-					role: 'user',
-					content: `Generate Python code to answer: "${question}"
+				messages: [
+					{
+						role: "user",
+						content: `Generate Python code to answer: "${question}"
 
 Requirements:
 - Use only Python standard library
 - Print the result using print()
 - Keep code simple and safe
 
-Return ONLY the code, no explanations.`
-				}],
+Return ONLY the code, no explanations.`,
+					},
+				],
 			});
 
-			const generatedCode = codeGeneration.content[0]?.type === 'text'
-				? codeGeneration.content[0].text
-				: '';
+			const generatedCode =
+				codeGeneration.content[0]?.type === "text"
+					? codeGeneration.content[0].text
+					: "";
 
 			if (!generatedCode) {
-				return Response.json({ error: 'Failed to generate code' }, { status: 500 });
+				return Response.json(
+					{ error: "Failed to generate code" },
+					{ status: 500 },
+				);
 			}
 
 			// Strip markdown code fences if present
 			const cleanCode = generatedCode
-				.replace(/^```python?\n?/, '')
-				.replace(/\n?```\s*$/, '')
+				.replace(/^```python?\n?/, "")
+				.replace(/\n?```\s*$/, "")
 				.trim();
 
 			// Execute the code in a sandbox
-			const sandbox = getSandbox(env.Sandbox, 'demo-user');
-			await sandbox.writeFile('/tmp/code.py', cleanCode);
-			const result = await sandbox.exec('python /tmp/code.py');
+			const sandbox = getSandbox(env.Sandbox, "demo-user");
+			await sandbox.writeFile("/tmp/code.py", cleanCode);
+			const result = await sandbox.exec("python /tmp/code.py");
 
 			return Response.json({
 				success: result.success,
 				question,
 				code: generatedCode,
 				output: result.stdout,
-				error: result.stderr
+				error: result.stderr,
 			});
-
 		} catch (error: any) {
 			return Response.json(
-				{ error: 'Internal server error', message: error.message },
-				{ status: 500 }
+				{ error: "Internal server error", message: error.message },
+				{ status: 500 },
 			);
 		}
 	},
 };
-```
+````
 
 **How it works:**
+
 1. Receives a question via POST to `/execute`
 2. Uses Claude to generate Python code
 3. Writes code to `/tmp/code.py` in the sandbox
@@ -176,11 +189,11 @@ Response:
 
 ```json
 {
-  "success": true,
-  "question": "What is the 10th Fibonacci number?",
-  "code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
-  "output": "55\n",
-  "error": ""
+	"success": true,
+	"question": "What is the 10th Fibonacci number?",
+	"code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
+	"output": "55\n",
+	"error": ""
 }
 ```
 
@@ -228,6 +241,7 @@ curl -X POST https://ai-code-executor.YOUR_SUBDOMAIN.workers.dev/execute \
 ## What you built
 
 You created an AI code execution system that:
+
 - Accepts natural language questions
 - Generates Python code with Claude
 - Executes code securely in isolated sandboxes
diff --git a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
index 5497b602e6f0f38..13784a7bf7fb634 100644
--- a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
+++ b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
@@ -119,24 +119,27 @@ export default {
 			}
 
 			async function streamToBase64(stream) {
-			  const blob = await new Response(stream).blob();
-			  const buffer = await blob.arrayBuffer();
-			  const bytes = new Uint8Array(buffer);
-
-			  // Convert to base64
-			  let binary = '';
-			  for (let i = 0; i < bytes.length; i++) {
-			    binary += String.fromCharCode(bytes[i]);
-			  }
-			  return btoa(binary);
+				const blob = await new Response(stream).blob();
+				const buffer = await blob.arrayBuffer();
+				const bytes = new Uint8Array(buffer);
+
+				// Convert to base64
+				let binary = "";
+				for (let i = 0; i < bytes.length; i++) {
+					binary += String.fromCharCode(bytes[i]);
+				}
+				return btoa(binary);
 			}
 
 			// Check for generated chart
 			let chart = null;
 			try {
-				const { content, mimeType } = await sandbox.readFile("/workspace/chart.png", {
-					encoding: "none"
-				});
+				const { content, mimeType } = await sandbox.readFile(
+					"/workspace/chart.png",
+					{
+						encoding: "none",
+					},
+				);
 				chart = `data:${mimeType};base64,${await streamToBase64(content)}`;
 			} catch {
 				// No chart generated
diff --git a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
index 1a964dfdb7b13da..cc84853855df6ca 100644
--- a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
+++ b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
@@ -39,9 +39,15 @@ cd test-pipeline
 Replace `src/index.ts`:
 
 ```typescript
-import { getSandbox, proxyToSandbox, parseSSEStream, type Sandbox, type ExecEvent } from '@cloudflare/sandbox';
+import {
+	getSandbox,
+	proxyToSandbox,
+	parseSSEStream,
+	type Sandbox,
+	type ExecEvent,
+} from "@cloudflare/sandbox";
 
-export { Sandbox } from '@cloudflare/sandbox';
+export { Sandbox } from "@cloudflare/sandbox";
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -53,34 +59,39 @@ export default {
 		const proxyResponse = await proxyToSandbox(request, env);
 		if (proxyResponse) return proxyResponse;
 
-		if (request.method !== 'POST') {
-			return new Response('POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }');
+		if (request.method !== "POST") {
+			return new Response(
+				'POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }',
+			);
 		}
 
 		try {
 			const { repoUrl, branch } = await request.json();
 
 			if (!repoUrl) {
-				return Response.json({ error: 'repoUrl required' }, { status: 400 });
+				return Response.json({ error: "repoUrl required" }, { status: 400 });
 			}
 
 			const sandbox = getSandbox(env.Sandbox, `test-${Date.now()}`);
 
 			try {
 				// Clone repository
-				console.log('Cloning repository...');
+				console.log("Cloning repository...");
 				let cloneUrl = repoUrl;
-				
-				if (env.GITHUB_TOKEN && cloneUrl.includes('github.com')) {
-					cloneUrl = cloneUrl.replace('https://', `https://${env.GITHUB_TOKEN}@`);
+
+				if (env.GITHUB_TOKEN && cloneUrl.includes("github.com")) {
+					cloneUrl = cloneUrl.replace(
+						"https://",
+						`https://${env.GITHUB_TOKEN}@`,
+					);
 				}
 
 				await sandbox.gitCheckout(cloneUrl, {
 					...(branch && { branch }),
 					depth: 1,
-					targetDir: 'repo'
+					targetDir: "repo",
 				});
-				console.log('Repository cloned');
+				console.log("Repository cloned");
 
 				// Detect project type
 				const projectType = await detectProjectType(sandbox);
@@ -89,38 +100,42 @@ export default {
 				// Install dependencies
 				const installCmd = getInstallCommand(projectType);
 				if (installCmd) {
-					console.log('Installing dependencies...');
-					const installStream = await sandbox.execStream(`cd /workspace/repo && ${installCmd}`);
-					
+					console.log("Installing dependencies...");
+					const installStream = await sandbox.execStream(
+						`cd /workspace/repo && ${installCmd}`,
+					);
+
 					let installExitCode = 0;
 					for await (const event of parseSSEStream<ExecEvent>(installStream)) {
-						if (event.type === 'stdout' || event.type === 'stderr') {
+						if (event.type === "stdout" || event.type === "stderr") {
 							console.log(event.data);
-						} else if (event.type === 'complete') {
+						} else if (event.type === "complete") {
 							installExitCode = event.exitCode;
 						}
 					}
-					
+
 					if (installExitCode !== 0) {
 						return Response.json({
 							success: false,
-							error: 'Install failed',
-							exitCode: installExitCode
+							error: "Install failed",
+							exitCode: installExitCode,
 						});
 					}
-					console.log('Dependencies installed');
+					console.log("Dependencies installed");
 				}
 
 				// Run tests
-				console.log('Running tests...');
+				console.log("Running tests...");
 				const testCmd = getTestCommand(projectType);
-				const testStream = await sandbox.execStream(`cd /workspace/repo && ${testCmd}`);
-				
+				const testStream = await sandbox.execStream(
+					`cd /workspace/repo && ${testCmd}`,
+				);
+
 				let testExitCode = 0;
 				for await (const event of parseSSEStream<ExecEvent>(testStream)) {
-					if (event.type === 'stdout' || event.type === 'stderr') {
+					if (event.type === "stdout" || event.type === "stderr") {
 						console.log(event.data);
-					} else if (event.type === 'complete') {
+					} else if (event.type === "complete") {
 						testExitCode = event.exitCode;
 					}
 				}
@@ -130,13 +145,11 @@ export default {
 					success: testExitCode === 0,
 					exitCode: testExitCode,
 					projectType,
-					message: testExitCode === 0 ? 'All tests passed' : 'Tests failed'
+					message: testExitCode === 0 ? "All tests passed" : "Tests failed",
 				});
-
 			} finally {
 				await sandbox.destroy();
 			}
-
 		} catch (error: any) {
 			return Response.json({ error: error.message }, { status: 500 });
 		}
@@ -145,38 +158,46 @@ export default {
 
 async function detectProjectType(sandbox: any): Promise<string> {
 	try {
-		await sandbox.readFile('/workspace/repo/package.json');
-		return 'nodejs';
+		await sandbox.readFile("/workspace/repo/package.json");
+		return "nodejs";
 	} catch {}
 
 	try {
-		await sandbox.readFile('/workspace/repo/requirements.txt');
-		return 'python';
+		await sandbox.readFile("/workspace/repo/requirements.txt");
+		return "python";
 	} catch {}
 
 	try {
-		await sandbox.readFile('/workspace/repo/go.mod');
-		return 'go';
+		await sandbox.readFile("/workspace/repo/go.mod");
+		return "go";
 	} catch {}
 
-	return 'unknown';
+	return "unknown";
 }
 
 function getInstallCommand(projectType: string): string {
 	switch (projectType) {
-		case 'nodejs': return 'npm install';
-		case 'python': return 'pip install -r requirements.txt || pip install -e .';
-		case 'go': return 'go mod download';
-		default: return '';
+		case "nodejs":
+			return "npm install";
+		case "python":
+			return "pip install -r requirements.txt || pip install -e .";
+		case "go":
+			return "go mod download";
+		default:
+			return "";
 	}
 }
 
 function getTestCommand(projectType: string): string {
 	switch (projectType) {
-		case 'nodejs': return 'npm test';
-		case 'python': return 'python -m pytest || python -m unittest discover';
-		case 'go': return 'go test ./...';
-		default: return 'echo "Unknown project type"';
+		case "nodejs":
+			return "npm test";
+		case "python":
+			return "python -m pytest || python -m unittest discover";
+		case "go":
+			return "go test ./...";
+		default:
+			return 'echo "Unknown project type"';
 	}
 }
 ```
@@ -203,10 +224,10 @@ You will see progress logs in the wrangler console, and receive a JSON response:
 
 ```json
 {
-  "success": true,
-  "exitCode": 0,
-  "projectType": "nodejs",
-  "message": "All tests passed"
+	"success": true,
+	"exitCode": 0,
+	"projectType": "nodejs",
+	"message": "All tests passed"
 }
 ```
 
@@ -225,6 +246,7 @@ npx wrangler secret put GITHUB_TOKEN
 ## What you built
 
 An automated testing pipeline that:
+
 - Clones Git repositories
 - Detects project type (Node.js, Python, Go)
 - Installs dependencies automatically
diff --git a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
index 022b3803088764b..fc519d4cc81608a 100644
--- a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
+++ b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
@@ -19,7 +19,10 @@ Cloudflare provides a self-managed environment for [Claude Managed Agents](https
 
 This integration ships as an open-source deployment template. Fork the repo, deploy it to your Cloudflare account, and customize it as needed.
 
-<LinkButton variant="secondary" href="https://github.com/cloudflare/claude-managed-agents">
+<LinkButton
+	variant="secondary"
+	href="https://github.com/cloudflare/claude-managed-agents"
+>
 	Get Started
 </LinkButton>
 
@@ -66,15 +69,15 @@ You need a Workers Paid plan or Enterprise account. [Containers](/containers/) (
 
 The repository includes detailed documentation on each capability:
 
-| Topic | What it covers |
-| --- | --- |
-| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md) | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings |
-| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md) | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing |
-| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md) | Pick the best agent execution environment |
-| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md) | Give agents their own email addresses and sending abilities |
-| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md) | Observable agent browser interactions with Browser Run |
-| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md) | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
-| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md) | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend |
-| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types |
-| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md) | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses |
-| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md) | Secure access to the CMA control plane |
+| Topic                                                                                                                                    | What it covers                                                                                                                                                   |
+| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md)   | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings                                                                             |
+| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md)               | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing                               |
+| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md)           | Pick the best agent execution environment                                                                                                                        |
+| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md)                                         | Give agents their own email addresses and sending abilities                                                                                                      |
+| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md)                 | Observable agent browser interactions with Browser Run                                                                                                           |
+| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md)                         | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
+| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md)                     | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend                                                                                            |
+| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types                                                                                                                      |
+| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md)                                       | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses                               |
+| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md)                                 | Secure access to the CMA control plane                                                                                                                           |
diff --git a/src/content/docs/sandbox/tutorials/code-review-bot.mdx b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
index daeeff910905556..98052e0f745d6e9 100644
--- a/src/content/docs/sandbox/tutorials/code-review-bot.mdx
+++ b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
@@ -108,9 +108,7 @@ export default {
 			) {
 				console.log(`Starting review for PR #${payload.pull_request.number}`);
 				// Use waitUntil to ensure the review completes even after response is sent
-				ctx.waitUntil(
-					reviewPullRequest(payload, env).catch(console.error),
-				);
+				ctx.waitUntil(reviewPullRequest(payload, env).catch(console.error));
 				return Response.json({ message: "Review started" });
 			}
 
diff --git a/src/content/docs/secrets-store/audit-logs.mdx b/src/content/docs/secrets-store/audit-logs.mdx
index 144a24543be86f5..90f826135f55949 100644
--- a/src/content/docs/secrets-store/audit-logs.mdx
+++ b/src/content/docs/secrets-store/audit-logs.mdx
@@ -17,4 +17,4 @@ sidebar:
   - A boolean `"value_modified": true` is presented when the secret value is edited.
 - Delete
 
-For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
\ No newline at end of file
+For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
diff --git a/src/content/docs/secrets-store/index.mdx b/src/content/docs/secrets-store/index.mdx
index 4d1e230e37ff9e9..e2ed5d0af9f4441 100644
--- a/src/content/docs/secrets-store/index.mdx
+++ b/src/content/docs/secrets-store/index.mdx
@@ -16,7 +16,8 @@ head:
 import { Description, Plan } from "~/components";
 
 <Description>
-Encrypt and store sensitive information as secrets that are securely reusable across your account.
+	Encrypt and store sensitive information as secrets that are securely reusable
+	across your account.
 </Description>
 
 <Plan id="secrets_store.properties.availability.summary" />
diff --git a/src/content/docs/secrets-store/integrations/ai-gateway.mdx b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
index 918c8bcfa39217c..af789df84d1a0c0 100644
--- a/src/content/docs/secrets-store/integrations/ai-gateway.mdx
+++ b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
@@ -8,4 +8,4 @@ external_link: /ai-gateway/configuration/bring-your-own-keys/
 sidebar:
   order: 3
   label: AI Gateway
----
\ No newline at end of file
+---
diff --git a/src/content/docs/secrets-store/integrations/index.mdx b/src/content/docs/secrets-store/integrations/index.mdx
index 64d5175c5fd2e82..a5ce8b0cbe2a887 100644
--- a/src/content/docs/secrets-store/integrations/index.mdx
+++ b/src/content/docs/secrets-store/integrations/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/secrets-store/manage-secrets/how-to.mdx b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
index 2fd99158d2495e9..cb9d42efdc308d9 100644
--- a/src/content/docs/secrets-store/manage-secrets/how-to.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
@@ -155,4 +155,4 @@ Refer to [Secrets Store API](/api/resources/secrets_store/) for the full API doc
 	method="DELETE"
 />
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/docs/secrets-store/manage-secrets/index.mdx b/src/content/docs/secrets-store/manage-secrets/index.mdx
index 17a01164f12187d..e9a5f2e3ffdfc0c 100644
--- a/src/content/docs/secrets-store/manage-secrets/index.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/index.mdx
@@ -28,4 +28,4 @@ If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler)
 - [Create a secret](/secrets-store/manage-secrets/how-to/#create-a-secret)
 - [Duplicate a secret](/secrets-store/manage-secrets/how-to/#duplicate-a-secret)
 - [Edit a secret](/secrets-store/manage-secrets/how-to/#edit-a-secret)
-- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
\ No newline at end of file
+- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
diff --git a/src/content/docs/security-center/brand-protection.mdx b/src/content/docs/security-center/brand-protection.mdx
index 3a021e91ce70f25..064f17815b2cfeb 100644
--- a/src/content/docs/security-center/brand-protection.mdx
+++ b/src/content/docs/security-center/brand-protection.mdx
@@ -54,7 +54,7 @@ To start searching for new domains that might be trying to impersonate your bran
 
 5. To export all matches from a saved query, select your **Query name** > select the three dots > **Export matches**.
 
-In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the  **Show dismissed matches** toggle in the Cloudflare dashboard.
+In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the **Show dismissed matches** toggle in the Cloudflare dashboard.
 
 ### Logo search (AI-powered)
 
diff --git a/src/content/docs/security-center/changelog.mdx b/src/content/docs/security-center/changelog.mdx
index 1c92506953963cf..889cbe1b2ec6c7b 100644
--- a/src/content/docs/security-center/changelog.mdx
+++ b/src/content/docs/security-center/changelog.mdx
@@ -16,20 +16,20 @@ import { ProductChangelog } from "~/components";
 
 ## 2025-02-03
 
-* Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
+- Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
 
 ## 2025-01-20
 
-* On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
+- On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
 
 ## 2024-09-23
 
-* Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
+- Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
 
 ## 2024-09-19
 
-* Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
+- Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
 
 ## 2024-07-22
 
-* Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
+- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
diff --git a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
index 6749f8a8b7ee551..e90c084b944a737 100644
--- a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
+++ b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
@@ -7,5 +7,4 @@ products:
 external_link: https://www.cloudflare.com/threat-intelligence/
 sidebar:
   order: 10
-
 ---
diff --git a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
index 55fbf7081e51889..33bd1dd3898a1bd 100644
--- a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
+++ b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
@@ -10,9 +10,7 @@ sidebar:
     text: Beta
 ---
 
-import { Details } from "~/components"
-
-
+import { Details } from "~/components";
 
 Open Port Scanning allows [Magic Transit](/magic-transit/) and [Bring your Own IPs](/byoip/) users to efficiently monitor IP ranges for security vulnerabilities. This API enables users to scan their designated IP ranges, detect any open ports, and receive daily notifications regarding newly opened ports.
 
@@ -21,24 +19,24 @@ You can access this feature via the [API](/api/resources/cloudforce_one/subresou
 ## Prerequisites
 
 - Cloudforce One Administrator, Administrator and Super Administrator roles.
-- Account token: **Custom API Token** >  **Cloudforce One:Edit**. 
+- Account token: **Custom API Token** > **Cloudforce One:Edit**.
 
 To create a custom API token:
 
 1. From the [Cloudflare dashboard](https://dash.cloudflare.com/profile/api-tokens/), go to **My Profile** > **API Tokens** for user tokens. Go to **Create Custom Token** > **Get started**.
 2. Enter a **Token name**, for example, `Open Port Scanning`.
 3. In **Permissions**:
-    - Choose **Account**.
-    - Select **Cloudforce One** as the account.
-    - Choose **Edit** access.
+   - Choose **Account**.
+   - Select **Cloudforce One** as the account.
+   - Choose **Edit** access.
 4. In Client IP Address Filtering:
-    - In **Operator**, select `is in`.
-    - In **Value**, enter a valid IP address.
+   - In **Operator**, select `is in`.
+   - In **Value**, enter a valid IP address.
 5. Select **Continue to summary**.
 6. Review the token, then select **Create Token**.
 
 :::note
-The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules. 
+The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules.
 :::
 
 ## Configure Open Port Scanning
@@ -46,150 +44,56 @@ The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce O
 To configure Open Port Scanning, follow these steps:
 
 1. **Create a new scan config**:
-    - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
-    - **Frequency**: Enter the scan frequency in days.
-    - **Ports**: Select the ports to scan. Choose among:
-        - All
-        - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
-        - List of specific ports
+   - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
+   - **Frequency**: Enter the scan frequency in days.
+   - **Ports**: Select the ports to scan. Choose among:
+     - All
+     - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
+     - List of specific ports
 2. **Scan IPs**: Initiate the scanning process. The system will analyze the specified IP ranges to identify any open ports.
 3. **Generate list of open ports**: Once the scan is complete, the API will generate a list of detected open ports for review and action.
-4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude  any ports that do not require immediate attention.
+4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude any ports that do not require immediate attention.
 5. **View differences from previous scan**: The API will highlight any changes in open ports since the last scan, allowing you to quickly assess new vulnerabilities.
-6. **Stop scanning**: If necessary, you can stop  the scanning process at any time.
-7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open. 
+6. **Stop scanning**: If necessary, you can stop the scanning process at any time.
+7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open.
 
 :::note[Beta feature notice]
 Open Port Scanning feature is currently in closed beta. The Cloudforce One team appreciates your feedback as the team works to enhance its functionality and user experience.
-If you want to subscribe  to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
+If you want to subscribe to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
 :::
 
 ## Default ports
 
 <Details header="List of default ports">
-- `80`
-- `631`
-- `161`
-- `137`
-- `123`
-- `138`
-- `1434`
-- `445`
-- `135`
-- `67`
-- `23`
-- `53`
-- `443`
-- `21`
-- `139`
-- `22`
-- `500`
-- `68`
-- `520`
-- `1900`
-- `25`
-- `4500`
-- `514`
-- `49152`
-- `162`
-- `69`
-- `5353`
-- `111`
-- `49154`
-- `3389`
-- `110`
-- `1701`
-- `998`
-- `996`
-- `997`
-- `999`
-- `3283`
-- `49153`
-- `445`
-- `1812`
-- `136`
-- `139`
-- `143`
-- `53`
-- `2222`
-- `135`
-- `3306`
-- `2049`
-- `32768`
-- `5060`
-- `8080`
-- `1025`
-- `1433`
-- `3456`
-- `80`
-- `1723`
-- `111`
-- `995`
-- `993`
-- `20031`
-- `1026`
-- `7`
-- `5900`
-- `1646`
-- `1645`
-- `593`
-- `1025`
-- `518`
-- `2048`
-- `626`
-- `1027`
-- `587`
-- `177`
-- `1719`
-- `427`
-- `497`
-- `8888`
-- `4444`
-- `1023`
-- `65024`
-- `199`
-- `19`
-- `9`
-- `49193`
-- `1029`
-- `1720`
-- `49`
-- `465`
-- `88`
-- `1028`
-- `17185`
-- `1718`
-- `49186`
-- `548`
-- `113`
-- `81`
-- `6001`
-- `2000`
-- `10000`
-- `31337`
+	- `80` - `631` - `161` - `137` - `123` - `138` - `1434` - `445` - `135` - `67`
+	- `23` - `53` - `443` - `21` - `139` - `22` - `500` - `68` - `520` - `1900` -
+	`25` - `4500` - `514` - `49152` - `162` - `69` - `5353` - `111` - `49154` -
+	`3389` - `110` - `1701` - `998` - `996` - `997` - `999` - `3283` - `49153` -
+	`445` - `1812` - `136` - `139` - `143` - `53` - `2222` - `135` - `3306` -
+	`2049` - `32768` - `5060` - `8080` - `1025` - `1433` - `3456` - `80` - `1723`
+	- `111` - `995` - `993` - `20031` - `1026` - `7` - `5900` - `1646` - `1645` -
+	`593` - `1025` - `518` - `2048` - `626` - `1027` - `587` - `177` - `1719` -
+	`427` - `497` - `8888` - `4444` - `1023` - `65024` - `199` - `19` - `9` -
+	`49193` - `1029` - `1720` - `49` - `465` - `88` - `1028` - `17185` - `1718` -
+	`49186` - `548` - `113` - `81` - `6001` - `2000` - `10000` - `31337`
 </Details>
 
 ## Frequently Asked Questions
 
 1. What IPs will the scan come from?
-
-    - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
-    - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
-    - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241` 
+   - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
+   - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
+   - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241`
 
 2. Can the Port Scanner bypass other security rules configured?
-
-    - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
+   - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
 
 3. How long do scans take?
-
-    - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
+   - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
 
 4. Can I stop automatic scanning?
-
-    - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
+   - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
 
 5. What are the limitations for the scans?
-
-    - Scans are limited to ranges of up to 5,000 IPs.
-    - The API scans both IPv4 and IPv6 IP addresses.
\ No newline at end of file
+   - Scans are limited to ranges of up to 5,000 IPs.
+   - The API scans both IPv4 and IPv6 IP addresses.
diff --git a/src/content/docs/security-center/investigate/change-categorization.mdx b/src/content/docs/security-center/investigate/change-categorization.mdx
index c2efde74687cbbf..bc56bde0cf28d7a 100644
--- a/src/content/docs/security-center/investigate/change-categorization.mdx
+++ b/src/content/docs/security-center/investigate/change-categorization.mdx
@@ -6,7 +6,6 @@ products:
   - security-center
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/docs/security-center/investigate/index.mdx b/src/content/docs/security-center/investigate/index.mdx
index f63c519b1be248a..6a3e0202c62c662 100644
--- a/src/content/docs/security-center/investigate/index.mdx
+++ b/src/content/docs/security-center/investigate/index.mdx
@@ -6,7 +6,6 @@ products:
   - security-center
 sidebar:
   order: 6
-
 ---
 
 :::note[User permission]
diff --git a/src/content/docs/security-center/investigate/investigate-threats.mdx b/src/content/docs/security-center/investigate/investigate-threats.mdx
index 48ce56a091e23fd..8056b226555f5c8 100644
--- a/src/content/docs/security-center/investigate/investigate-threats.mdx
+++ b/src/content/docs/security-center/investigate/investigate-threats.mdx
@@ -6,10 +6,9 @@ products:
   - security-center
 sidebar:
   order: 3
-
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Users can investigate the details of an IP address, domain name, URL, or Autonomous System Number (ASN). You can find the Investigate feature in your Cloudflare account's Security Center and in [Cloudflare Radar](https://radar.cloudflare.com/scan).
 
@@ -106,4 +105,4 @@ To download a report:
    <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your domain and select **Search**.
-3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
\ No newline at end of file
+3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
diff --git a/src/content/docs/security-center/investigate/scan-limits.mdx b/src/content/docs/security-center/investigate/scan-limits.mdx
index 4a87a3ad19d63d5..00c9e0921faf0d5 100644
--- a/src/content/docs/security-center/investigate/scan-limits.mdx
+++ b/src/content/docs/security-center/investigate/scan-limits.mdx
@@ -5,17 +5,13 @@ products:
   - security-center
 head: []
 description: Limits
-
 ---
 
 URL scans are limited by search history, Public and Unlisted visibility, and requests per second across different Cloudflare plans.
 
-
-
 | Cloudflare Plan    | Search history | Public scans (per month) | Unlisted scans (per month) | Rate limit       |
 | ------------------ | -------------- | ------------------------ | -------------------------- | ---------------- |
 | **Free / Radar**   | last 50 scans  | 5,000                    | none                       | 1 per 10 seconds |
 | **Self serve**     | 30 days        | 5,000                    | 500                        | 1 per 10 seconds |
 | **Enterprise**     | 12 months      | 10,000                   | 5,000                      | 12 per second    |
 | **Cloudforce One** | Unlimited      | 75,000                   | 20,000                     | 12 per second    |
-
diff --git a/src/content/docs/security/overview.mdx b/src/content/docs/security/overview.mdx
index 544b227b7e54dfc..91001dcbbfba6db 100644
--- a/src/content/docs/security/overview.mdx
+++ b/src/content/docs/security/overview.mdx
@@ -24,10 +24,11 @@ The Security overview page displays:
 
 ## Security action items
 
-**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity. 
-  - **Action item types**:
-    - Suspicious activity
-    - Security insight
+**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity.
+
+- **Action item types**:
+  - Suspicious activity
+  - Security insight
 - **Criticality**: Your action items are ranked by the highest criticality, showing critical first, moderate, and low respectively.
 - **Filters**: You can filter your action items by Criticality, Insight Type, and Security Category.
   - Criticality:
@@ -35,20 +36,20 @@ The Security overview page displays:
     - Moderate
     - Critical
   - Insight Types:
-    - Suspicious activity 
-    - Exposed infrastructure 
-    - Insecure configuration 
+    - Suspicious activity
+    - Exposed infrastructure
+    - Insecure configuration
     - Configuration suggestion
     - Compliance Violation
     - Email Security
     - Weak Authentication
-  - Security Category: 
+  - Security Category:
     - Web application exploits
     - AI exploits
-    - DDoS attacks 
-    - Bot traffic 
-    - API abuse 
-    - Client-side abuse 
+    - DDoS attacks
+    - Bot traffic
+    - API abuse
+    - Client-side abuse
     - Fraud
 - **Review**: Review your security action items for more detailed information and recommended actions to resolve.
 - **Load more**: View the full list of security action items.
@@ -71,14 +72,14 @@ Archiving a detected suspicious activity will only archive that item from the se
 
 To view when an action item’s status was changed and the rationale provided for that change, use the following API commands to retrieve audit logs:
 
-| Method | Path | Description |
-| ------ | ---- | ----------- |
-| `GET` | `/api/accounts/{accountID}/insights/audit-log` | List all audit logs for an account |
-| `GET` | `/api/accounts/{accountID}/insights/{insightID}/audit-log` | List audit logs for a specific issue |
-| `GET` | `/api/accounts/{accountID}/issues/audit-log` | List all audit logs for account issues |
-| `GET` | `/api/accounts/{accountID}/issues/{insightID}/audit-log` | List all audit logs for a specific issue |
-| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log` | List all audit logs for a domain |
-| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
+| Method | Path                                                                      | Description                                      |
+| ------ | ------------------------------------------------------------------------- | ------------------------------------------------ |
+| `GET`  | `/api/accounts/{accountID}/insights/audit-log`                            | List all audit logs for an account               |
+| `GET`  | `/api/accounts/{accountID}/insights/{insightID}/audit-log`                | List audit logs for a specific issue             |
+| `GET`  | `/api/accounts/{accountID}/issues/audit-log`                              | List all audit logs for account issues           |
+| `GET`  | `/api/accounts/{accountID}/issues/{insightID}/audit-log`                  | List all audit logs for a specific issue         |
+| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log`             | List all audit logs for a domain                 |
+| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
 
 Refer to our [Security Center API documentation](/api/resources/security_center) to review the action item audit logs by account, domain, or a specific `issue_id`.
 
@@ -93,4 +94,4 @@ View the patterns and highlights from your domain's traffic in the past 30 days.
 The Cloudflare dashboard displays:
 
 - **Monthly requests**: View the monthly requests and traffic that has been mitigated by Cloudflare.
-- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
\ No newline at end of file
+- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
diff --git a/src/content/docs/smart-shield/concepts/index.mdx b/src/content/docs/smart-shield/concepts/index.mdx
index 1120c7c003aa4c3..12403e47aa9a979 100644
--- a/src/content/docs/smart-shield/concepts/index.mdx
+++ b/src/content/docs/smart-shield/concepts/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/concepts/network-diagram.mdx b/src/content/docs/smart-shield/concepts/network-diagram.mdx
index 3eec884e62a0d79..307591a0ae523f1 100644
--- a/src/content/docs/smart-shield/concepts/network-diagram.mdx
+++ b/src/content/docs/smart-shield/concepts/network-diagram.mdx
@@ -16,4 +16,4 @@ Requests from visitors first reach a nearby lower-tier data center. For static (
 
 For dynamic (non-cacheable) requests, [Argo Smart Routing](/smart-shield/configuration/argo/) finds the fastest network path to your origin. Between Cloudflare's upper-tier data centers and your origin, [connection reuse](/smart-shield/concepts/connection-reuse/) packages multiple requests into a single connection, reducing the total number of connections your origin handles.
 
-[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
\ No newline at end of file
+[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
diff --git a/src/content/docs/smart-shield/configuration/argo.mdx b/src/content/docs/smart-shield/configuration/argo.mdx
index 16a4fce8d7e97be..0d1fcae78001d37 100644
--- a/src/content/docs/smart-shield/configuration/argo.mdx
+++ b/src/content/docs/smart-shield/configuration/argo.mdx
@@ -18,4 +18,4 @@ Available with Smart Shield + Argo and Smart Shield Advanced.
 
 Cloudflare provides analytics to show the performance benefits of Argo Smart Routing.
 
-<Render file="argo-analytics" product="smart-shield" />
\ No newline at end of file
+<Render file="argo-analytics" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
index 14f71bac0cc40fc..3e14a1542d4343a 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
@@ -14,9 +14,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-  file="cache-reserve-analytics"
-  product="cache"
+	file="cache-reserve-analytics"
+	product="cache"
 	params={{
 		conditional: "smart-shield-tile",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
index 8eeb03f8661c785..9c1e9769086a7e3 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
@@ -40,4 +40,4 @@ You can remove all data stored in Cache Reserve. In most cases, deletion takes a
 
 :::note
 If you want to purge your cache instead, refer to [cache configurations](/cache/how-to/purge-cache/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
index 5d0b8457ad806be..40b660890f6f6f9 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
@@ -13,7 +13,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-  file="cache-reserve-operations"
-  product="cache"
-/>
\ No newline at end of file
+<Render file="cache-reserve-operations" product="cache" />
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
index 6b011755c7d6d69..4af2a88245d5455 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
@@ -38,7 +38,7 @@ flowchart LR
 
 If the server does not have access to an applicable IP, the following options are checked and the first that is possible will take place:
 
-* Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
+- Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
 
 ```mermaid
 flowchart LR
@@ -55,7 +55,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-* Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
+- Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
 
 ```mermaid
 flowchart LR
@@ -77,7 +77,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-* Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
+- Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
 
 ```mermaid
 flowchart LR
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
index c7f7d638be9549d..44ef7eec5859bde 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Refer to the pages below to understand how Dedicated CDN Egress IPs work.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
index 4ed679361eb9526..2275ff704685684 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
@@ -24,9 +24,9 @@ Dedicated CDN Egress IPs was formerly known as Cloudflare Aegis ([release blog p
 
 With Dedicated CDN Egress IPs, you can:
 
-* Lock down your network firewall to only allow traffic from your dedicated IPs.
-* Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
-* Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
+- Lock down your network firewall to only allow traffic from your dedicated IPs.
+- Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
+- Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
 
 ## Scope
 
@@ -40,4 +40,4 @@ Dedicated CDN Egress IPs are included within [BGP advertisement over CNI](/netwo
 
 <DirectoryListing />
 
-[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
\ No newline at end of file
+[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
index bf1bd852f10c57a..7e7eb7f4fe8699d 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
@@ -16,7 +16,7 @@ Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data and monitor
 
 <Render file="concurrent-connections-explainer" product="smart-shield" />
 
-Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the  [example](#example) below for a quickstart.
+Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the [example](#example) below for a quickstart.
 
 ## GraphQL schema
 
@@ -25,19 +25,19 @@ The specific schema to get Dedicated CDN Egress IPs data is called `aegisIpUtili
 You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions:
 
 - `datetimeFiveMinutes` <Type text="time" />
-    - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
+  - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
 
 - `popName` <Type text="string" />
-    - The Cloudflare point of presence (PoP). For example, `sjc`.
+  - The Cloudflare point of presence (PoP). For example, `sjc`.
 
 - `egressIp` <Type text="string" />
-    - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
+  - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
 
 - `origin` <Type text="string" />
-    - Origin IP and port. For example, `203.0.113.150:443`.
+  - Origin IP and port. For example, `203.0.113.150:443`.
 
 - `popUtilizationKey` <Type text="string" />
-    - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
+  - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
 
 ## Example
 
@@ -47,100 +47,100 @@ You can also select the button at the bottom to use this query for your account
 
 ```graphql graphql-api-explorer "popName: "<CLOUDFLARE_POP>"" "egressIp: "<YOUR_EGRESS_IP>"" "origin: "<ORIGIN_IP_AND_PORT>""
 query AegisIpUtilizationQuery(
-  $accountTag: string
-  $datetimeStart: string
-  $datetimeEnd: string
+	$accountTag: string
+	$datetimeStart: string
+	$datetimeEnd: string
 ) {
-  viewer {
-    utilization: accounts(filter: { accountTag: $accountTag }) {
-      avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        avg {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          popName: "<CLOUDFLARE_POP>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          egressIp: "<YOUR_EGRESS_IP>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-
-      filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
-        limit: 100
-        filter: {
-          datetimeFiveMinutes_geq: $datetimeStart
-          datetimeFiveMinutes_leq: $datetimeEnd
-          origin: "<ORIGIN_IP_AND_PORT>"
-        }
-        orderBy: [datetimeFiveMinutes_ASC]
-      ) {
-        max {
-          utilization
-        }
-        dimensions {
-          datetimeFiveMinutes
-          popUtilizationKey
-        }
-      }
-    }
-  }
+	viewer {
+		utilization: accounts(filter: { accountTag: $accountTag }) {
+			avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				avg {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					popName: "<CLOUDFLARE_POP>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					egressIp: "<YOUR_EGRESS_IP>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+
+			filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
+				limit: 100
+				filter: {
+					datetimeFiveMinutes_geq: $datetimeStart
+					datetimeFiveMinutes_leq: $datetimeEnd
+					origin: "<ORIGIN_IP_AND_PORT>"
+				}
+				orderBy: [datetimeFiveMinutes_ASC]
+			) {
+				max {
+					utilization
+				}
+				dimensions {
+					datetimeFiveMinutes
+					popUtilizationKey
+				}
+			}
+		}
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
index f36cbde97e071bb..da17ba92284032c 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
@@ -63,4 +63,4 @@ Workers subrequests — requests from one Worker to another — are expected to
 
 For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
 
-[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
\ No newline at end of file
+[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
diff --git a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
index 121427dcf85f924..2ff26322bf71a01 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
@@ -15,7 +15,4 @@ import { Render } from "~/components";
 
 Use Health Checks analytics to debug possible origin issues.
 
-<Render
-  file="health-checks-analytics"
-	product="smart-shield"
-/>
\ No newline at end of file
+<Render file="health-checks-analytics" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/health-checks/index.mdx b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
index ca2d659d7d5eb14..0f3fdf5c2c0f9a7 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/index.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
@@ -24,4 +24,4 @@ Available for Pro, Business, and Enterprise customers in all Smart Shield packag
 
 ## Further reading
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
index 292d644b16b754d..07cacf201721425 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
@@ -20,8 +20,8 @@ Refer to the section below to learn how to manage your Smart Shield health check
 3. For Health Checks, select **Manage**.
 4. Select **Create** or find an existing health check and select **Edit**.
 5. Fill out the form or edit existing values, paying special attention to:
-   * The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
-   * **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
+   - The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
+   - **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
 6. Select **Save and Deploy**.
 
 ## Configure alerts
diff --git a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
index 5a42572ca2e935b..e269a8febaf8111 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
@@ -15,4 +15,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
+<Render file="zone-lockdown" product="smart-shield" />
diff --git a/src/content/docs/smart-shield/configuration/index.mdx b/src/content/docs/smart-shield/configuration/index.mdx
index 9a1b637e55751a5..6244ba2195424e8 100644
--- a/src/content/docs/smart-shield/configuration/index.mdx
+++ b/src/content/docs/smart-shield/configuration/index.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
index 9073a8017865420..49cf513c617947e 100644
--- a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
@@ -16,4 +16,4 @@ import { Render } from "~/components";
 Available with Smart Shield Advanced.
 :::
 
-<Render file="regional-tiered-cache" product="cache" />
\ No newline at end of file
+<Render file="regional-tiered-cache" product="cache" />
diff --git a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
index f7fafaa47aea6a9..9b9c6760721cd54 100644
--- a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
@@ -18,4 +18,4 @@ Available in all Smart Shield packages.
 
 With data centers around the world, Cloudflare caches content very close to end users. However, if a piece of content is not in cache, the Cloudflare data centers must contact the origin server to receive the cacheable content. Tiered cache works by dividing Cloudflare's data centers into a hierarchy of lower-tiers and upper-tiers, where only upper-tiers can ask your origin for content.
 
-<Render file="smart-tiered-cache" product="cache" />
\ No newline at end of file
+<Render file="smart-tiered-cache" product="cache" />
diff --git a/src/content/docs/spectrum/about/byoip.mdx b/src/content/docs/spectrum/about/byoip.mdx
index b574fc12e5048f2..3e3fb82322e59aa 100644
--- a/src/content/docs/spectrum/about/byoip.mdx
+++ b/src/content/docs/spectrum/about/byoip.mdx
@@ -5,22 +5,18 @@ description: Use your own IP addresses with Spectrum applications.
 products:
   - spectrum
 weight: 0
-
 ---
 
-import { APIRequest, Render } from "~/components"
+import { APIRequest, Render } from "~/components";
 
 When creating a Spectrum application, Cloudflare normally assigns an arbitrary IP from Cloudflare’s IP pool to your application. If you want to be explicit in your network setup or use your own IP addresses, BYOIP with Spectrum allows you to do just that.
 
 BYOIP stands for [Bring Your Own IP](/byoip/). If you own an IP prefix you can migrate it to Cloudflare. After migration, Cloudflare broadcasts your IP prefix and traffic is routed to the global Cloudflare network. However, without configuration, Cloudflare will not know how to handle this traffic. The last step is to add Spectrum applications for all applications that you wish to protect with the IP addresses you want associated with them.
 
-
 :::caution
 
-
 When switching from non-BYOIP to BYOIP, if you are already using a Spectrum application, you need to delete your configurations and recreate new ones.
 
-
 :::
 
 The smallest prefixes that Cloudflare currently supports is /24 for IPv4 and /48 for IPv6.
@@ -35,22 +31,22 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 
 ```json
 {
-  "id": "4590376cf2994d72cee36828ec4eff19",
-  "protocol": "tcp/22",
-  "dns": {
-    "type": "ADDRESS",
-    "name": "ssh.example.com"
-  },
-  "origin_direct": ["tcp://192.0.2.1:22"],
-  "ip_firewall": true,
-  "proxy_protocol": false,
-  "spp": false,
-  "tls": "off",
-  "traffic_type": "direct",
-  "edge_ips": {
-    "type": "static",
-    "ips": ["198.51.100.10", "2001:DB8::1"]
-  }
+	"id": "4590376cf2994d72cee36828ec4eff19",
+	"protocol": "tcp/22",
+	"dns": {
+		"type": "ADDRESS",
+		"name": "ssh.example.com"
+	},
+	"origin_direct": ["tcp://192.0.2.1:22"],
+	"ip_firewall": true,
+	"proxy_protocol": false,
+	"spp": false,
+	"tls": "off",
+	"traffic_type": "direct",
+	"edge_ips": {
+		"type": "static",
+		"ips": ["198.51.100.10", "2001:DB8::1"]
+	}
 }
 ```
 
@@ -59,25 +55,20 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 In the example below, the application routes traffic through Cloudflare’s HTTP pipeline, including WAF, Workers and CDN functionality.
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    protocol: "tcp/80",
-    dns: {
-      type: "ADDRESS",
-      name: "www.example.com"
-    },
-    origin_direct: [
-      "tcp://192.0.2.1:80"
-    ],
-    tls: "off",
-    traffic_type: "http",
-    edge_ips: {
-      type: "static",
-      ips: [
-        "198.51.100.10",
-        "2001:DB8::1"
-      ]
-    }
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		protocol: "tcp/80",
+		dns: {
+			type: "ADDRESS",
+			name: "www.example.com",
+		},
+		origin_direct: ["tcp://192.0.2.1:80"],
+		tls: "off",
+		traffic_type: "http",
+		edge_ips: {
+			type: "static",
+			ips: ["198.51.100.10", "2001:DB8::1"],
+		},
+	}}
 />
diff --git a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
index 21f55d4cd8281c7..30cfcf85e672028 100644
--- a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
+++ b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
@@ -5,7 +5,6 @@ description: Layer 3 and 4 DDoS protection for TCP and UDP Spectrum applications
 products:
   - spectrum
 weight: 0
-
 ---
 
 Spectrum provides DDoS Protection at layers 3-4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/), that is against TCP and UDP based DDoS attacks.
diff --git a/src/content/docs/spectrum/about/ftp.mdx b/src/content/docs/spectrum/about/ftp.mdx
index 1d666adace4bcc4..68f7e8ff116275c 100644
--- a/src/content/docs/spectrum/about/ftp.mdx
+++ b/src/content/docs/spectrum/about/ftp.mdx
@@ -13,17 +13,15 @@ Enabling Spectrum for FTP is not straightforward due to the implementation of th
 
 :::note
 
-
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
-
 :::
 
 ## How FTP Operates
 
 FTP leverages two different sockets, one for issuing commands and the other for actual data transfer. The control socket takes care of users logging in and sending commands, and the data socket is where directory listings and files actually get transferred.
 
-There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects *back* to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
+There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects _back_ to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
 
 In passive mode, the FTP server communicates a port that the client should connect to, which is done on the control socket via a PASV command. By default, the FTP server responds with the IP address that it is listening on. This scenario is fine for servers running directly on a public-facing IP but creates issues when a server is behind an NAT, firewall, or Cloudflare Spectrum.
 
@@ -31,7 +29,7 @@ Alternatively, more modern FTP server software supports [FTP extensions](https:/
 
 ## What Does and Does Not Work
 
-Spectrum is able to protect servers serving FTP traffic in *passive mode only*. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
+Spectrum is able to protect servers serving FTP traffic in _passive mode only_. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
 
 Passive mode in combination with EPSV works out of the box with no origin-side configuration required. Note that the client must also support EPSV for this to work. Traditional passive mode with PASV is possible with minimal origin-side configuration (see below, Protecting an FTP server with Spectrum)
 
@@ -71,14 +69,14 @@ Example configuration for [vsftpd](https://security.appspot.com/vsftpd.html):
 
 To use Spectrum TCP to proxy and protect FTPS, specifically ProFTPD, the following example configuration is recommended:
 
-* **Control Port**: Port 21
-* **Data Ports**: Port ranges 50000-50500
+- **Control Port**: Port 21
+- **Data Ports**: Port ranges 50000-50500
 
 On the ProFTPD server side use the following example configuration:
 
-* `MasqueradeAddress`: `www.example.com`
-* `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
-* `PassivePorts`: `50000-50500`
+- `MasqueradeAddress`: `www.example.com`
+- `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
+- `PassivePorts`: `50000-50500`
 
 For more details, refer to the [ProFTPD documentation](http://www.proftpd.org/docs/modules/mod_core.html).
 
diff --git a/src/content/docs/spectrum/about/index.mdx b/src/content/docs/spectrum/about/index.mdx
index a45de1bbf3080f6..79bf764731996bb 100644
--- a/src/content/docs/spectrum/about/index.mdx
+++ b/src/content/docs/spectrum/about/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information about concepts related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/about/static-ip.mdx b/src/content/docs/spectrum/about/static-ip.mdx
index f075127c3337700..9ad484844461329 100644
--- a/src/content/docs/spectrum/about/static-ip.mdx
+++ b/src/content/docs/spectrum/about/static-ip.mdx
@@ -5,10 +5,9 @@ description: Assign persistent IP addresses to your Spectrum applications.
 products:
   - spectrum
 weight: 0
-
 ---
 
-import { APIRequest, Render } from "~/components"
+import { APIRequest, Render } from "~/components";
 
 When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.
 
@@ -29,35 +28,30 @@ Once you get your static IP from Cloudflare, you can use it via API, just like [
 When creating a Spectrum application through the API, specify the static IPs that you have been provided. See, for instance, the API example below that creates an application routing traffic through Cloudflare’s HTTP pipeline.
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    protocol: "tcp/80",
-    dns: {
-      type: "ADDRESS",
-      name: "www.example.com"
-    },
-    origin_direct: [
-      "tcp://192.0.2.1:80"
-    ],
-    tls: "off",
-    traffic_type: "http",
-    edge_ips: {
-      type: "static",
-      ips: [
-        "198.51.100.10",
-        "2001:DB8::1"
-      ]
-    }
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		protocol: "tcp/80",
+		dns: {
+			type: "ADDRESS",
+			name: "www.example.com",
+		},
+		origin_direct: ["tcp://192.0.2.1:80"],
+		tls: "off",
+		traffic_type: "http",
+		edge_ips: {
+			type: "static",
+			ips: ["198.51.100.10", "2001:DB8::1"],
+		},
+	}}
 />
 
 ## Check your static IPs
 
 <Render
-  file="check-leased-ips"
+	file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "static IPs for Spectrum"
+		product: "static IPs for Spectrum",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/docs/spectrum/glossary.mdx b/src/content/docs/spectrum/glossary.mdx
index 5dfed742cc6ccb5..e858503baad6ca3 100644
--- a/src/content/docs/spectrum/glossary.mdx
+++ b/src/content/docs/spectrum/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - spectrum
 sidebar:
   order: 7
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Spectrum documentation.
 
diff --git a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
index 3961a4766160937..bed4a42932be361 100644
--- a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
+++ b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
@@ -5,7 +5,6 @@ description: Pass client IP information to your origin using Proxy protocol v1 o
 products:
   - spectrum
 weight: 0
-
 ---
 
 import { DashButton } from "~/components";
@@ -16,10 +15,8 @@ Some services you run may require knowledge of the true client IP. In those case
 
 :::note
 
-
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
-
 :::
 
 ## Enable Proxy Protocol v1 for TCP
diff --git a/src/content/docs/spectrum/how-to/index.mdx b/src/content/docs/spectrum/how-to/index.mdx
index 9f660cc61eee6f5..8edbdf1ca9239c5 100644
--- a/src/content/docs/spectrum/how-to/index.mdx
+++ b/src/content/docs/spectrum/how-to/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information on completing Spectrum related tasks, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/protocols-per-plan.mdx b/src/content/docs/spectrum/protocols-per-plan.mdx
index 6ae364f5a9f92e8..b82fd38bf63e579 100644
--- a/src/content/docs/spectrum/protocols-per-plan.mdx
+++ b/src/content/docs/spectrum/protocols-per-plan.mdx
@@ -6,10 +6,9 @@ products:
   - spectrum
 sidebar:
   order: 2
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 On this table, you have information about which protocols are available per plan.
 
diff --git a/src/content/docs/spectrum/reference/analytics.mdx b/src/content/docs/spectrum/reference/analytics.mdx
index 8ad2a392de6915f..3f021a4dd31e9fb 100644
--- a/src/content/docs/spectrum/reference/analytics.mdx
+++ b/src/content/docs/spectrum/reference/analytics.mdx
@@ -9,12 +9,10 @@ tags:
   - Analytics
 ---
 
-import { Render, APIRequest } from "~/components"
+import { Render, APIRequest } from "~/components";
 
 Cloudflare measures the following metrics for every connection.
 
-
-
 | Metric         | Name                                | Example | Unit                 |
 | -------------- | ----------------------------------- | ------- | -------------------- |
 | count          | Count of total events               | `1000`  | Count                |
@@ -25,14 +23,10 @@ Cloudflare measures the following metrics for every connection.
 | duration90th   | 90th percentile connection duration | `1.0`   | Time in milliseconds |
 | duration99th   | 99th percentile connection duration | `1.0`   | Time in milliseconds |
 
-
-
 ## Additional dimensions
 
 You can divide your analytics further by the following dimensions.
 
-
-
 | Dimension | Name                          | Example                                                              |
 | --------- | ----------------------------- | -------------------------------------------------------------------- |
 | event     | Connection Event              | `connect`, `progress`, `disconnect`, `originError`, `clientFiltered` |
@@ -40,14 +34,10 @@ You can divide your analytics further by the following dimensions.
 | coloName  | Colo Name                     | `SFO`                                                                |
 | ipVersion | IP version used by the client | `4`, `6`                                                             |
 
-
-
 ## Operators for filtering
 
 Use the operators below to filter data.
 
-
-
 | Operator | Name                     | URL Encoded |
 | -------- | ------------------------ | ----------- |
 | `==`     | Equals                   | `%3D%3D`    |
@@ -57,8 +47,6 @@ Use the operators below to filter data.
 | `>=`     | Greater than or equal to | `%3E%3D`    |
 | `<=`     | Less than or equal to    | `%3C%3D`    |
 
-
-
 <Render file="api-combine-filters" product="fundamentals" />
 
 ## Analytics request structure
@@ -68,26 +56,26 @@ Use the operators below to filter data.
 /api/v4/zones/{zone_id}/spectrum/analytics/events/bytime?metrics=METRICS&dimensions=DIMENSIONS&filters=FILTERS&since=FROM_TS&sort=SORT&until=TO_TS&limit=LIMIT
 ```
 
-* METRICS is one or more metrics (such as count) to compute
-* DIMENSIONS can be used to break down the data by given attributes
-* FILTERS used to filter rows by one or more dimensions (see Filters section below)
-* SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
-* TO\_TS is that end of time interval to query, defaults to current time
-* FROM\_TS is that start of time interval to query, defaults to TO\_TS - 6 hours
-* STEP is used to select time series resolution when using endpoint:
-* auto or omitted - selects time step most appropriate to time interval
-  * year
-  * quarter
-  * month
-  * week
-  * day
-  * hour
+- METRICS is one or more metrics (such as count) to compute
+- DIMENSIONS can be used to break down the data by given attributes
+- FILTERS used to filter rows by one or more dimensions (see Filters section below)
+- SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
+- TO_TS is that end of time interval to query, defaults to current time
+- FROM_TS is that start of time interval to query, defaults to TO_TS - 6 hours
+- STEP is used to select time series resolution when using endpoint:
+- auto or omitted - selects time step most appropriate to time interval
+  - year
+  - quarter
+  - month
+  - week
+  - day
+  - hour
 
 ## Analytics query example
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/analytics/events/summary"
-  method="GET"
+	path="/zones/{zone_id}/spectrum/analytics/events/summary"
+	method="GET"
 />
 
 Refer to the [Spectrum API documentation](/api/resources/spectrum/subresources/analytics/subresources/aggregates/subresources/currents/methods/get/) for more examples of API requests.
diff --git a/src/content/docs/spectrum/reference/index.mdx b/src/content/docs/spectrum/reference/index.mdx
index 1cb17fdcb764a75..2f5495921b7c522 100644
--- a/src/content/docs/spectrum/reference/index.mdx
+++ b/src/content/docs/spectrum/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/reference/layer-7-analytics.mdx b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
index ac15ed1aa946651..ed2b0717d749251 100644
--- a/src/content/docs/spectrum/reference/layer-7-analytics.mdx
+++ b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - spectrum
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Even when you have Spectrum enabled to handle Layer 4 traffic (for example, TCP/UDP connections), you may still notice traffic in your Layer 7 (L7) analytics dashboard. This is due to the way Cloudflare's Layer 7 <GlossaryTooltip term="content delivery network (CDN)">CDN</GlossaryTooltip>
  and Spectrum handle customer identity differently.
@@ -42,4 +42,4 @@ This means traffic for this hostname undergoes the standard Layer 7 CDN products
 
 If you want to prevent traffic for Layer-4-only Spectrum hostnames from being proxied through Layer 7 to your origin (including unwanted scans or requests), we recommend implementing a Layer 7 WAF (Web Application Firewall) rule. This rule can block traffic directed at specific hostnames or ports, ensuring that only legitimate traffic reaches your Spectrum service.
 
-For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
\ No newline at end of file
+For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
diff --git a/src/content/docs/spectrum/reference/logs.mdx b/src/content/docs/spectrum/reference/logs.mdx
index 0ee954278aec0d5..e5c27ce81e5be5e 100644
--- a/src/content/docs/spectrum/reference/logs.mdx
+++ b/src/content/docs/spectrum/reference/logs.mdx
@@ -19,8 +19,6 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 
 ## Status Codes
 
-
-
 | Code | Description                                                                                        |
 | ---- | -------------------------------------------------------------------------------------------------- |
 | 0    | Connection was opened successfully.                                                                |
@@ -52,4 +50,3 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 | 533  | Internal error while resolving origin to an IP.                                                    |
 | 540  | The client/edge TLS handshake failed due to an invalid configuration.                              |
 | 999  | Unknown connection error.                                                                          |
-
diff --git a/src/content/docs/spectrum/reference/settings-by-plan.mdx b/src/content/docs/spectrum/reference/settings-by-plan.mdx
index c243f1c03952069..9865188065dbb98 100644
--- a/src/content/docs/spectrum/reference/settings-by-plan.mdx
+++ b/src/content/docs/spectrum/reference/settings-by-plan.mdx
@@ -5,19 +5,12 @@ description: Spectrum API fields and settings available by Cloudflare plan.
 products:
   - spectrum
 weight: 0
-
 ---
 
-
-
 Certain fields in Spectrum request and response bodies require an Enterprise plan. To upgrade your plan, contact your account team.
 
 Spectrum properties requiring an Enterprise plan:
 
-
-
-
-
 | Name                 | Type    | Description                                                                                                                                                                                                                                                                                                              | Example                                                    |
 | -------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
 | `origin_dns`         | object  | Method and parameters used to discover the origin server address via DNS. Valid record types are `A`, `AAAA`, `SRV` and empty (both `A` and `AAA`).<br />A request must contain either an `origin_dns` parameter or an `origin_direct` parameter. When both are specified the service returns an `HTTP 400 Bad Request`. | `origin_dns: {type: A, name: mqtt.example.com, ttl: 1200}` |
@@ -25,11 +18,6 @@ Spectrum properties requiring an Enterprise plan:
 | `proxy_protocol`     | string  | Enables Proxy Protocol to the origin. Spectrum supports `v1`, `v2`, and `simple` proxy protocols. Refer to [Proxy Protocol](/spectrum/how-to/enable-proxy-protocol/) for more details.                                                                                                                                   | `off`                                                      |
 | `ip_firewall`        | boolean | Enables IP Access rules for this application.                                                                                                                                                                                                                                                                            | `true`                                                     |
 | `tls`                | string  | Type of TLS termination for the application. Options are `off` (default, also known as Passthrough), `flexible`, `full`, and `strict`. Refer to [Configuration Options](/spectrum/reference/configuration-options/) for descriptions of each.                                                                            | `full`                                                     |
-| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic\_type set to `direct`.                                                                                                                                                                                  | `true`                                                     |
-
-
-
-
+| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic_type set to `direct`.                                                                                                                                                                                   | `true`                                                     |
 
 Review the [Spectrum API documentation](/api/resources/spectrum/subresources/apps/methods/list/) for example API requests.
-
diff --git a/src/content/docs/speed/aim.mdx b/src/content/docs/speed/aim.mdx
index c8139eed9a0013a..95fc9acbd18a0d7 100644
--- a/src/content/docs/speed/aim.mdx
+++ b/src/content/docs/speed/aim.mdx
@@ -4,7 +4,6 @@ description: Measure real-world internet quality metrics for your visitors.
 products:
   - speed
 title: Aggregated Internet Measurement
-
 ---
 
 Aggregated Internet Measurement (AIM) helps you understand your Internet quality to identify scenarios that your Internet connection is good or bad for. Typically, an Internet speed test provides you with upload and download speeds, which may not always provide a holistic view of your Internet quality.
@@ -15,28 +14,28 @@ AIM uses a scoring rubric that assigns point values based on speed tests to help
 
 AIM analyzes the following metrics to generate your score:
 
-* Latency
-* Packet Loss
-* Download
-* Upload
-* Loaded Latency
-* Jitter
+- Latency
+- Packet Loss
+- Download
+- Upload
+- Loaded Latency
+- Jitter
 
-After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC.  These scores will indicate how good your Internet is in each of these scenarios.
+After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC. These scores will indicate how good your Internet is in each of these scenarios.
 
 The possible network scores are:
 
-* Bad
-* Poor
-* Average
-* Good
-* Great
+- Bad
+- Poor
+- Average
+- Good
+- Great
 
 ## Improve your network score
 
 You have a few options to help improve network scores.
 
-* **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
-* **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
-* **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
-* **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
+- **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
+- **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
+- **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
+- **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
diff --git a/src/content/docs/speed/glossary.mdx b/src/content/docs/speed/glossary.mdx
index fc3634a28e51568..2fb9f99dba9493c 100644
--- a/src/content/docs/speed/glossary.mdx
+++ b/src/content/docs/speed/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Speed documentation.
 products:
   - speed
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Speed documentation.
 
diff --git a/src/content/docs/speed/observatory/dashboard.mdx b/src/content/docs/speed/observatory/dashboard.mdx
index 1017a25218c61a5..6a18975aceb0150 100644
--- a/src/content/docs/speed/observatory/dashboard.mdx
+++ b/src/content/docs/speed/observatory/dashboard.mdx
@@ -40,11 +40,10 @@ The **Network Performance** section shows timing data that can help pinpoint whe
 
 - **Time to First Byte (TTFB)**: Measures the time between the initial request and the first byte of the response.
 - **Time to Last Byte (TTLB) Breakdown**: Provides a breakdown of response phases:
-
-    - DNS resolution time
-    - TCP connection time
-    - Request processing time at the server
-    - Response transfer time
+  - DNS resolution time
+  - TCP connection time
+  - Request processing time at the server
+  - Response transfer time
 
 This breakdown helps identify whether delays are caused by DNS, connection setup, server processing, or response delivery.
 
@@ -77,4 +76,4 @@ Use the Speed Overview dashboard to:
 - Track **Core Web Vitals** to ensure a good user experience.
 - Analyze **Network Performance** to identify latency bottlenecks.
 - Diagnose errors with **HTTP Traffic** insights.
-- Confirm site reliability using **Synthetic Monitoring** results.
\ No newline at end of file
+- Confirm site reliability using **Synthetic Monitoring** results.
diff --git a/src/content/docs/speed/observatory/rum-beacon.mdx b/src/content/docs/speed/observatory/rum-beacon.mdx
index 66c0e8035856ce1..8e343c58ee410d5 100644
--- a/src/content/docs/speed/observatory/rum-beacon.mdx
+++ b/src/content/docs/speed/observatory/rum-beacon.mdx
@@ -8,7 +8,6 @@ tags:
   - Privacy
 sidebar:
   order: 4
- 
 ---
 
 The RUM beacon is a JavaScript snippet that runs when a Cloudflare customer enables RUM through [Web Analytics](/web-analytics/) or [Observatory](/speed/observatory/). This script runs in users' browsers when they visit the customer's site, and its purpose is to collect performance-related data, for example, page load time, and send it to Cloudflare's systems for processing. This [data](/web-analytics/data-metrics/) is then presented to the customer, providing valuable insights into the website's performance and usage.
@@ -17,7 +16,7 @@ The RUM beacon script can be enabled into a webpage in two ways:
 
 - **One-click setup**: For [sites proxied through Cloudflare](/web-analytics/get-started/#sites-proxied-through-cloudflare) that have Web Analytics enabled, the snippet can be _automatically_ injected into pages as the HTML response passes through Cloudflare's edge network to the browser by simply enabling the automatic injection option.
 
-- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML. 
+- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML.
 
 ## Data collection
 
@@ -25,36 +24,36 @@ Once downloaded to the browser, the RUM beacon script runs as JavaScript in the
 
 The data collected from the browser is summarized in the table below:
 
-| Field      | Example  | Description  | How it is collected    |
-|------------|----------|--------------|------------------------|
-| `pageloadId`  | 0c698922-8d60-40bf-85ac-7982b5f8034d  | The unique ID for the page. | Generated in the browser code.  |
-| `referrer`    | https://cfrumtest.com/ | The referring page URL. | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
-| `startTime`  | 1693488419352  | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                        |
-| `memory` | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }` | Measures memory heap size. | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                              |
-| `timings` | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming) | Timing data. | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)     |
-| `timingV2` | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                   |
-| `resources`  | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | Resource timing data.  | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                     |
-| `firstPaint` | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | Paint timing data. | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) |
-| `firstContentfulPaint` | 209  | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1] |
-| `FCP`        | 209 | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `LCP`        | 209 | Largest Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `CLS`        | 0.001 | Cumulative Layout Shift metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-                                                           |
-| `TTFB`       | 0.03 | Time to First Byte metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `INP`        | 1.23 | Interaction to Next Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
-| `landingPath`| https://cfrumtest.com/  | The landing page URL. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | 
+| Field                  | Example                                                                                                              | Description                                  | How it is collected                                                                                                                                                                                                                                                                                       |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pageloadId`           | 0c698922-8d60-40bf-85ac-7982b5f8034d                                                                                 | The unique ID for the page.                  | Generated in the browser code.                                                                                                                                                                                                                                                                            |
+| `referrer`             | https://cfrumtest.com/                                                                                               | The referring page URL.                      | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
+| `startTime`            | 1693488419352                                                                                                        | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                                                                                                                                                                         |
+| `memory`               | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }`                               | Measures memory heap size.                   | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                                                                                                                                                                                    |
+| `timings`              | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming)                    | Timing data.                                 | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)                                                                                                                                                           |
+| `timingV2`             | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data.                      | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
+| `resources`            | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)     | Resource timing data.                        | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                                                                                                                                                                    |
+| `firstPaint`           | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)           | Paint timing data.                           | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)                                                                                                                                                                                          |
+| `firstContentfulPaint` | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `FCP`                  | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `LCP`                  | 209                                                                                                                  | Largest Contentful Paint metric.             | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `CLS`                  | 0.001                                                                                                                | Cumulative Layout Shift metric.              | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+|  |
+| `TTFB`                 | 0.03                                                                                                                 | Time to First Byte metric.                   | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `INP`                  | 1.23                                                                                                                 | Interaction to Next Paint metric.            | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
+| `landingPath`          | https://cfrumtest.com/                                                                                               | The landing page URL.                        | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
 
 ## Data processing
 
 RUM data is generally processed at the nearest Cloudflare data center based on how the incoming request is routed. This is determined by a number of factors including [Anycast](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) and [Unimog](https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/). Since RUM data does not use location services, it may be processed in a different country or region from where it originated. Although the RUM service receives the client/source IP address from the beacon as part of normal HTTP request handling process, it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs.
 
-## Privacy information 
+## Privacy information
 
 The RUM beacon script does not store any data in the browser or access any storage data, such as [cookies](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie), [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage), [sessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage), IP address, or [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB). The data we collect is performance data from the browser performance [APIs](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API). This performance data is ephemeral and only relates to the current webpage that is being viewed. If the user refreshes their browser, all the previous performance data is gone and new performance data starts being available. This data is not stored or accessed from anywhere on the device, it is only available as in-memory data.
 
 ## RUM excluding EEA/EU
 
-Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.   
+Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.
 
 Free customers have RUM enabled automatically, with EU traffic excluded, and can switch it off if they prefer. Customers on other plans may enable RUM as needed.
 
@@ -64,5 +63,4 @@ Free customers have RUM enabled automatically, with EU traffic excluded, and can
 
     </div>
 
-
-[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
\ No newline at end of file
+[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
diff --git a/src/content/docs/speed/observatory/run-speed-test.mdx b/src/content/docs/speed/observatory/run-speed-test.mdx
index b86b5c58655a186..5ae182cbf4eb09c 100644
--- a/src/content/docs/speed/observatory/run-speed-test.mdx
+++ b/src/content/docs/speed/observatory/run-speed-test.mdx
@@ -50,20 +50,19 @@ RUM uses a lightweight JavaScript beacon to collect the information Observatory
 Quota limits for the number of tests you can run per month are currently the following:
 
 | Plan       | One-off tests | Recurring tests | Frequency of recurring tests |
-|------------|---------------|-----------------|------------------------------|
+| ---------- | ------------- | --------------- | ---------------------------- |
 | Pro        | 50            | 5               | Daily                        |
 | Business   | 100           | 10              | Daily                        |
 | Enterprise | 150           | 15              | Daily                        |
 
 **Available Regions (all plans):**
 
-| Region                | Region              | Region             |
-|------------------------|---------------------|--------------------|
-| Iowa, USA             | Hamina, Finland     | Changhua County, Taiwan |
-| South Carolina, USA   | Madrid, Spain       | Tokyo, Japan       |
-| North Virginia, USA   | St. Ghislain, Belgium | Osaka, Japan      |
-| Dallas, USA           | Eemshaven, Netherlands | Jurong West, Singapore |
-| Oregon, USA           | Milan, Italy        | Sydney, Australia  |
-| London, England       | Paris, France       | Mumbai, India      |
-| Frankfurt, Germany    | Tel Aviv, Israel    | São Paulo, Brazil  |
-
+| Region              | Region                 | Region                  |
+| ------------------- | ---------------------- | ----------------------- |
+| Iowa, USA           | Hamina, Finland        | Changhua County, Taiwan |
+| South Carolina, USA | Madrid, Spain          | Tokyo, Japan            |
+| North Virginia, USA | St. Ghislain, Belgium  | Osaka, Japan            |
+| Dallas, USA         | Eemshaven, Netherlands | Jurong West, Singapore  |
+| Oregon, USA         | Milan, Italy           | Sydney, Australia       |
+| London, England     | Paris, France          | Mumbai, India           |
+| Frankfurt, Germany  | Tel Aviv, Israel       | São Paulo, Brazil       |
diff --git a/src/content/docs/speed/observatory/test-results.mdx b/src/content/docs/speed/observatory/test-results.mdx
index a9b42c82085bb1a..c6bf699af5e19a6 100644
--- a/src/content/docs/speed/observatory/test-results.mdx
+++ b/src/content/docs/speed/observatory/test-results.mdx
@@ -6,7 +6,6 @@ products:
 title: Understand test results
 sidebar:
   order: 3
-
 ---
 
 The test result page shows you how your website performed regarding several key industry metrics. Some of these metrics are presented for synthetic tests and the real user monitoring, and others only apply to synthetic tests or only to real user monitoring.
@@ -36,19 +35,19 @@ These metrics result from the synthetic tests.
 
 These metrics are collected as part of the real user data, as they require real user interaction with a page.
 
-| Metric                                                  | Definition                                                                                                                                                                       |
-| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page.                                                       |
+| Metric                                                  | Definition                                                                                                                 |
+| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page. |
 
 Refer to [Data and metrics](/web-analytics/data-metrics/) for more information about the metrics you can find in the Real User Monitoring dashboard. You can find details about [Core Web Vitals](/web-analytics/data-metrics/core-web-vitals/), the debug view and the data collected.
 
 ## Network monitoring metrics
 
-| Metric                                            | Definition                                                                                                          |
-| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Wait Time | Measures the time spent waiting for the server to send back the first byte of a response after a request is made.                                           |
-| Load Time | Measures the total time it takes for a web page to fully load in a user’s browser from the network.                                                         |
-| Time to First Byte ([TTFB](https://web.dev/articles/ttfb))  | Measures the duration between initiating a web page request and receiving the first byte from the server. |
-| Server Response Time | Measures the time it takes for a server to respond to a request from a user's browser.                                                           |
-| Connect Time | Measures the time taken to establish a connection between the user's browser and the web server.                                                         | 
-| TLS Time | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.                                                  | 
\ No newline at end of file
+| Metric                                                     | Definition                                                                                                        |
+| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| Wait Time                                                  | Measures the time spent waiting for the server to send back the first byte of a response after a request is made. |
+| Load Time                                                  | Measures the total time it takes for a web page to fully load in a user’s browser from the network.               |
+| Time to First Byte ([TTFB](https://web.dev/articles/ttfb)) | Measures the duration between initiating a web page request and receiving the first byte from the server.         |
+| Server Response Time                                       | Measures the time it takes for a server to respond to a request from a user's browser.                            |
+| Connect Time                                               | Measures the time taken to establish a connection between the user's browser and the web server.                  |
+| TLS Time                                                   | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.       |
diff --git a/src/content/docs/speed/optimization/content/apo.mdx b/src/content/docs/speed/optimization/content/apo.mdx
index bf378bf7685846b..f706bab097e8e8c 100644
--- a/src/content/docs/speed/optimization/content/apo.mdx
+++ b/src/content/docs/speed/optimization/content/apo.mdx
@@ -7,5 +7,4 @@ title: Automatic Platform Optimization
 external_link: /automatic-platform-optimization/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/content/compression.mdx b/src/content/docs/speed/optimization/content/compression.mdx
index 93ad3418e9054de..e021ae803ef2b55 100644
--- a/src/content/docs/speed/optimization/content/compression.mdx
+++ b/src/content/docs/speed/optimization/content/compression.mdx
@@ -22,9 +22,9 @@ Cloudflare compresses content in two ways: between Cloudflare and your website v
 In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.
 
 <Stream
-  id="9103750883217fcb9274666fd57ebac1"
-  title="Content compression"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
+	id="9103750883217fcb9274666fd57ebac1"
+	title="Content compression"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
 />
 
 :::note
diff --git a/src/content/docs/speed/optimization/content/early-hints.mdx b/src/content/docs/speed/optimization/content/early-hints.mdx
index 3263897899e5f21..f40d05197e0f6de 100644
--- a/src/content/docs/speed/optimization/content/early-hints.mdx
+++ b/src/content/docs/speed/optimization/content/early-hints.mdx
@@ -7,5 +7,4 @@ title: Early Hints
 external_link: /cache/advanced-configuration/early-hints/
 sidebar:
   order: 5
-
 ---
diff --git a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
index b5627175aec2342..778b154ef43acac 100644
--- a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
+++ b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
@@ -28,7 +28,10 @@ To test that the Fonts feature is working correctly, follow these steps:
 For the feature to work, the response HTML (when the feature is disabled) must include a link tag with `href` pointing to `fonts.googleapis.com`. You can check this on the browser by viewing the source code of the webpage. As an example of what to look for, the following link tag is for the Roboto Google Font:
 
 ```html
-<link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">
+<link
+	href="https://fonts.googleapis.com/css2?family=Roboto&display=swap"
+	rel="stylesheet"
+/>
 ```
 
 If the tag does not exist in the HTML, but you are still sure that your page is using Google Fonts, it might be that your hosting provider is optimizing your Google Fonts on the server. This can prevent Cloudflare Fonts from working properly.
diff --git a/src/content/docs/speed/optimization/content/index.mdx b/src/content/docs/speed/optimization/content/index.mdx
index a778f875d6059cc..e1a5decf41e6b26 100644
--- a/src/content/docs/speed/optimization/content/index.mdx
+++ b/src/content/docs/speed/optimization/content/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
index 148e6cc5d93b485..115046f10c28f12 100644
--- a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
+++ b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
@@ -23,15 +23,13 @@ Rocket Loader will still optimize the loading of all other scripts on the page.
 
 :::note
 
-
 If Rocket Loader is only impacting a specific page, use a [Configuration Rule](/rules/configuration-rules/) to exclude that page by URL.
 
-
 :::
 
 ## Limitations
 
-* Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
-* If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
-* The `data-cfasync` attribute must be added before the `src` attribute.
-* Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
+- Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
+- If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
+- The `data-cfasync` attribute must be added before the `src` attribute.
+- Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
diff --git a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
index 8b56ec1c37765c8..e17a32a6e8a3b82 100644
--- a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
+++ b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
@@ -43,11 +43,11 @@ Shared dictionaries work when all of the following are true:
 
 The protocol uses two new request and response headers and two new content encodings:
 
-| Header                           | Direction        | Purpose                                                                                            |
-| -------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
+| Header                           | Direction        | Purpose                                                                                             |
+| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- |
 | `Use-As-Dictionary`              | Origin → browser | Marks a response as usable as a dictionary for future requests matching the supplied `match` value. |
-| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.           |
-| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).     |
+| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.            |
+| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).      |
 
 The first response for a versioned asset includes `Use-As-Dictionary`, and the browser stores the response. On subsequent requests for assets matching the pattern, the browser sends `Available-Dictionary: :<sha256>:` and adds `dcb, dcz` to `Accept-Encoding`. Your origin compresses the new asset against the dictionary and returns it with `Content-Encoding: dcb` or `dcz`. The browser uses its stored copy to reconstruct the full response.
 
diff --git a/src/content/docs/speed/optimization/content/smart-hints.mdx b/src/content/docs/speed/optimization/content/smart-hints.mdx
index 74a30be29625c81..9df2f2740a81901 100644
--- a/src/content/docs/speed/optimization/content/smart-hints.mdx
+++ b/src/content/docs/speed/optimization/content/smart-hints.mdx
@@ -7,5 +7,4 @@ title: Smart Hints
 external_link: https://blog.cloudflare.com/smart-hints/
 sidebar:
   order: 8
-
 ---
diff --git a/src/content/docs/speed/optimization/content/speed-brain.mdx b/src/content/docs/speed/optimization/content/speed-brain.mdx
index e0de7cbfe69f617..979f0002e29fc50 100644
--- a/src/content/docs/speed/optimization/content/speed-brain.mdx
+++ b/src/content/docs/speed/optimization/content/speed-brain.mdx
@@ -10,7 +10,13 @@ sidebar:
 description: Learn how Speed Brain enhances web performance by prefetching likely next pages, improving metrics like LCP and TTFB.
 ---
 
-import { FeatureTable, TabItem, Tabs, APIRequest, DashButton } from "~/components";
+import {
+	FeatureTable,
+	TabItem,
+	Tabs,
+	APIRequest,
+	DashButton,
+} from "~/components";
 
 Speed Brain is a tool for improving web page performance by prefetching the most likely next navigation.
 
@@ -111,7 +117,6 @@ You can also configure Speed Brain using Terraform. For more details, refer to t
 ## Caveats
 
 - Since prefetch responses are not guaranteed to be rendered by the browser, Speed Brain includes two safeguards to minimize the risk of [unsafe prefetching](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#unsafe_prefetching):
-
   - Speed Brain will not prefetch on routes that run Workers. Without this safeguard, prefetch requests could inadvertently run Worker logic that assumes the incoming request is a normal (that is, not a prefetch) request. An example of this could be an incrementing page view counter running in a Worker. A page view counter should not increment if the page is not actually rendered in the browser.
 
   - Prefetch requests will never reach origin servers. Prefetch requests only serve content that is stored in Cloudflare’s Cache. If the content is not in Cache, the prefetch request will not continue to origin servers. Without this safeguard, origin server state could be modified despite the prefetch response not being rendered in the browser. An example of this could be a prefetch `GET` request to a sign-out URL inadvertently triggering a sign-out action on the server.
diff --git a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
index 274ba87dc345bae..e125fcbbe0254bf 100644
--- a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Optimization issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/image-resizing.mdx b/src/content/docs/speed/optimization/images/image-resizing.mdx
index 5e5c8613ef540aa..6594df5754962d0 100644
--- a/src/content/docs/speed/optimization/images/image-resizing.mdx
+++ b/src/content/docs/speed/optimization/images/image-resizing.mdx
@@ -7,5 +7,4 @@ title: Image Resizing
 external_link: /images/optimization/transformations/overview/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/images/index.mdx b/src/content/docs/speed/optimization/images/index.mdx
index d027767b2a3faf5..c079cac0a17b480 100644
--- a/src/content/docs/speed/optimization/images/index.mdx
+++ b/src/content/docs/speed/optimization/images/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/polish.mdx b/src/content/docs/speed/optimization/images/polish.mdx
index c529447865e7b61..631c4cbe263d8c9 100644
--- a/src/content/docs/speed/optimization/images/polish.mdx
+++ b/src/content/docs/speed/optimization/images/polish.mdx
@@ -7,5 +7,4 @@ title: Polish
 external_link: /images/polish/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
index 1f8d029c7d93ae9..cb64aa9539c46b7 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Image issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
index 9ac31a532e60906..fb72840fc7b149a 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
@@ -5,7 +5,6 @@ products:
   - speed
 source: https://support.cloudflare.com/hc/en-us/articles/200168046-Will-Cloudflare-s-image-optimization-features-help-if-I-m-already-optimizing-images-
 title: Image optimization on optimized images
-
 ---
 
 Cloudflare's [image optimization features](/speed/optimization/images/) will likely not help much if you are already optimizing your images in some way (Smush.it, etc.).
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
index 26bdaff52e6866e..ce279de1efcba70 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
@@ -6,5 +6,4 @@ products:
 title: Polish statuses
 external_link: /images/polish/cf-polished-statuses/
 weight: 0
-
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
index ed4e61afdf15934..12268c9dc18cddc 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
@@ -15,9 +15,9 @@ If images are missing from your website, other Cloudflare features may be interf
 To troubleshoot:
 
 1. Perform one of the following actions:
+   - [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
+   - [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
+   - Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 
-   * [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
-   * [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
-   * Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 2. Retest the image load in a private browser tab.
 3. If the issue is not fixed, try another of the actions suggested in Step 1.
diff --git a/src/content/docs/speed/optimization/index.mdx b/src/content/docs/speed/optimization/index.mdx
index bd80c971ba9878a..83b3fba317047d6 100644
--- a/src/content/docs/speed/optimization/index.mdx
+++ b/src/content/docs/speed/optimization/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The Optimization section will show you a list of Cloudflare products that are recommended for enhancing your website's performance.
 
diff --git a/src/content/docs/speed/optimization/measurement.mdx b/src/content/docs/speed/optimization/measurement.mdx
index 016533a4dd1986e..89a7f989f4b71dc 100644
--- a/src/content/docs/speed/optimization/measurement.mdx
+++ b/src/content/docs/speed/optimization/measurement.mdx
@@ -6,7 +6,6 @@ products:
 title: Measurement
 sidebar:
   order: 2
-
 ---
 
 Enable measurement to track your traffic in a privacy-first manner, optimizing your site's speed tools. To access this feature, you need to enable [Web Analytics](/web-analytics/) on your website. This analytics tool leverages [Real User Measurement](/speed/observatory/run-speed-test/#enable-real-user-monitoring-rum) (RUM) data, providing insights based on actual user interactions to enhance site performance effectively.
diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx
index 74d4e0a9ae7f530..13e54b4c22eaedd 100644
--- a/src/content/docs/speed/optimization/protocol/http2.mdx
+++ b/src/content/docs/speed/optimization/protocol/http2.mdx
@@ -56,10 +56,10 @@ The origin web server may be sending improperly formatted HTTP response headers.
 
 #### Resolution
 
-Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements: 
+Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements:
 
 - [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5)
-- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) 
+- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1)
 - [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1)
 
 ### Compression issues
diff --git a/src/content/docs/speed/optimization/protocol/index.mdx b/src/content/docs/speed/optimization/protocol/index.mdx
index fdfe4aa14eb11b1..094dadd43d13cf2 100644
--- a/src/content/docs/speed/optimization/protocol/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/index.mdx
@@ -8,9 +8,8 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
index 45783c25f400853..957822a95ff61cf 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
@@ -4,7 +4,6 @@ description: Fix Enhanced HTTP/2 Prioritization issues on iOS and Safari.
 products:
   - speed
 title: Enhanced HTTP/2 Prioritization negatively affects iOS/Safari devices
-
 ---
 
 Occasionally, [Enhanced HTTP/2 Prioritization](/speed/optimization/protocol/enhanced-http2-prioritization/) can negatively affect the experience of visitors using Safari on macOS or any browser on iOS.
@@ -17,10 +16,8 @@ If visitors using using Safari on macOS or any browser on iOS are experiencing i
 
 :::note
 
-
 Sometimes, [HTTP/2](/speed/optimization/protocol/http2/) will cause **Enhanced HTTP/2 Prioritization** to be re-enabled automatically.
 
 If you notice this happening, also disable **HTTP/2**.
 
-
 :::
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
index 0d6974f96123177..804f216d9cf3f8c 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Protocol optimization issues
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/recommendations.mdx b/src/content/docs/speed/optimization/recommendations.mdx
index 1367d8efb7789e2..aac4598f71a5531 100644
--- a/src/content/docs/speed/optimization/recommendations.mdx
+++ b/src/content/docs/speed/optimization/recommendations.mdx
@@ -6,7 +6,6 @@ products:
 title: Recommendations
 sidebar:
   order: 1
-
 ---
 
 In the **Recommendations** tab, with one click you can enable all the recommended settings available for your plan. You can enable all the recommended settings at once or you can also just enable the ones you want.
diff --git a/src/content/docs/speed/smart-shield.mdx b/src/content/docs/speed/smart-shield.mdx
index 76f0af22755c9f7..9fc997ea18add10 100644
--- a/src/content/docs/speed/smart-shield.mdx
+++ b/src/content/docs/speed/smart-shield.mdx
@@ -7,5 +7,4 @@ title: Smart Shield
 sidebar:
   order: 4
 external_link: /smart-shield/
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/speed/troubleshooting.mdx b/src/content/docs/speed/troubleshooting.mdx
index 1a73653e90dc280..6f7d78e7f34c259 100644
--- a/src/content/docs/speed/troubleshooting.mdx
+++ b/src/content/docs/speed/troubleshooting.mdx
@@ -7,12 +7,15 @@ title: Troubleshooting
 hideChildren: true
 sidebar:
   order: 20
-
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 The following topics are useful for troubleshooting Speed issues.
 
-<ResourcesBySelector directory="speed" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
-
+<ResourcesBySelector
+	directory="speed"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/ssl/changelog.mdx b/src/content/docs/ssl/changelog.mdx
index c96ac0914a9da7c..96577c758525512 100644
--- a/src/content/docs/ssl/changelog.mdx
+++ b/src/content/docs/ssl/changelog.mdx
@@ -16,7 +16,7 @@ import { ProductChangelog } from "~/components";
 
 ## 2024-10-18
 
-**New cloudflare\_branding flag allows hostnames with over 64 characters for all CAs**
+**New cloudflare_branding flag allows hostnames with over 64 characters for all CAs**
 
 To order certificates for hostnames longer than 64 characters, customers can now use the `cloudflare_branding` flag when ordering a certificate via [API](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/create/). Setting `cloudflare_branding` to `true` will cause `sni.cloudflaressl.com` to be used as the common name, while the long hostname is added as part of the subject alternative name (SAN).
 
@@ -24,4 +24,4 @@ To order certificates for hostnames longer than 64 characters, customers can now
 
 **SSL.com available with ACM and SSL for SaaS**
 
-SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
\ No newline at end of file
+SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
diff --git a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
index fda3782b24250c6..129b0ea9d7b037b 100644
--- a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
@@ -15,4 +15,4 @@ import { Render } from "~/components";
 
 <Render file="add-client-certificate-rfc9440" product="ssl" />
 
-<Render file="forward-client-certificate" product="ssl" />
\ No newline at end of file
+<Render file="forward-client-certificate" product="ssl" />
diff --git a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
index 20bc4a82a73822d..c362c3ea0cbfc69 100644
--- a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
@@ -6,7 +6,6 @@ products:
 title: Revoke a client certificate
 sidebar:
   order: 8
-
 ---
 
 import { DashButton } from "~/components";
@@ -26,10 +25,8 @@ It is not possible to permanently delete client certificates generated with the
 
 :::caution[Important]
 
-
 After revoking a certificate, you must update any mTLS rules that check for the presence of a client certificate so that they block all requests that include a revoked certificate.
 
 For more information, refer to [Check for revoked certificates](/api-shield/security/mtls/configure/#check-for-revoked-certificates).
 
-
 :::
diff --git a/src/content/docs/ssl/concepts.mdx b/src/content/docs/ssl/concepts.mdx
index 2f0333d5ec7c728..074f33eaa264a9e 100644
--- a/src/content/docs/ssl/concepts.mdx
+++ b/src/content/docs/ssl/concepts.mdx
@@ -25,9 +25,9 @@ Since [Cloudflare's global network](https://www.cloudflare.com/network/) is at t
 The [edge certificates](/ssl/edge-certificates/) are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the [Cloudflare Dashboard](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
 
 <Stream
-  id="fe9344af4ab476bf81f4447000f36db66"
-  title="SSL/TLS concepts"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
+	id="fe9344af4ab476bf81f4447000f36db66"
+	title="SSL/TLS concepts"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
 />
 
 ### Origin certificate
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
index 18550b308521f31..c4d44c211b0ec09 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
@@ -30,9 +30,9 @@ If you are a SaaS provider looking to restrict cipher suites for connections to
 
 Custom cipher suites is a hostname-level setting, which implies that:
 
-* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
-* The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
-* If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
+- When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
+- The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
+- If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
 
 ## Scope
 
@@ -50,4 +50,4 @@ This documentation only refers to connections [between clients and the Cloudflar
 
 Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hostname-priority/) to determine which setting to apply.
 
-ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
\ No newline at end of file
+ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
index 7aae1bb58f1bbd9..c8b458d6184c218 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
@@ -16,31 +16,31 @@ tags:
 
 Cloudflare supports the following cipher suites by default. If needed, you can [restrict your website or application](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) to only use specific cipher suites.
 
-| Cipher name | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name |
-| -------------------------------- | ---------------- | ------------------------------------------------------------------------ | ------------ | --------------------------------------------------- |
-| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02b]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256      |
-| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca9]    | TLS\_ECDHE\_ECDSA\_WITH\_CHACHA20\_POLY1305\_SHA256 |
-| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02f]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256        |
-| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca8]    | TLS\_ECDHE\_RSA\_WITH\_CHACHA20\_POLY1305\_SHA256   |
-| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc023]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256      |
-| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                   | \[0xc009]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA         |
-| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc027]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256        |
-| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc013]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA           |
-| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                   | \[0x9c]      | TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256               |
-| AES128-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3c]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256               |
-| AES128-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x2f]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA                  |
-| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02c]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384      |
-| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc024]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384      |
-| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc030]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384        |
-| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc028]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384        |
-| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc014]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA           |
-| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                   | \[0x9d]      | TLS\_RSA\_WITH\_AES\_256\_GCM\_SHA384               |
-| AES256-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3d]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256               |
-| AES256-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x35]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA                  |
-| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                   | \[0x0a]      | TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA                 |
-| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x01}  | TLS\_AES\_128\_GCM\_SHA256                          |
-| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x02}  | TLS\_AES\_256\_GCM\_SHA384                          |
-| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x03}  | TLS\_CHACHA20\_POLY1305\_SHA256                     |
+| Cipher name                      | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name                                     |
+| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------- |
+| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02b]    | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256       |
+| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca9]    | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 |
+| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02f]    | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256         |
+| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca8]    | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   |
+| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc023]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256       |
+| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                                              | \[0xc009]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA          |
+| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc027]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256         |
+| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc013]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA            |
+| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                                              | \[0x9c]      | TLS_RSA_WITH_AES_128_GCM_SHA256               |
+| AES128-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3c]      | TLS_RSA_WITH_AES_128_CBC_SHA256               |
+| AES128-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x2f]      | TLS_RSA_WITH_AES_128_CBC_SHA                  |
+| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02c]    | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384       |
+| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc024]    | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384       |
+| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc030]    | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384         |
+| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc028]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384         |
+| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc014]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA            |
+| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                                              | \[0x9d]      | TLS_RSA_WITH_AES_256_GCM_SHA384               |
+| AES256-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3d]      | TLS_RSA_WITH_AES_256_CBC_SHA256               |
+| AES256-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x35]      | TLS_RSA_WITH_AES_256_CBC_SHA                  |
+| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                                              | \[0x0a]      | TLS_RSA_WITH_3DES_EDE_CBC_SHA                 |
+| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x01} | TLS_AES_128_GCM_SHA256                        |
+| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x02} | TLS_AES_256_GCM_SHA384                        |
+| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x03} | TLS_CHACHA20_POLY1305_SHA256                  |
 
 :::note[* TLS 1.3 minimum protocol]
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
index 33d50ea3a037245..186ef035f3bc82f 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Once you set up SSL/TLS on your application, you can adjust the following settings on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page:
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
index cb0cd6575e94980..c5f7c351636e7ea 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
@@ -8,7 +8,14 @@ sidebar:
   order: 13
 ---
 
-import { FeatureTable, TabItem, Tabs, APIRequest, Render, DashButton } from "~/components";
+import {
+	FeatureTable,
+	TabItem,
+	Tabs,
+	APIRequest,
+	Render,
+	DashButton,
+} from "~/components";
 
 Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer.
 
@@ -86,13 +93,13 @@ Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hos
 In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and authentication placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
 <APIRequest
-  path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
-  method="PUT"
-  json={{
-		"value": "1.2"
+	path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
+	method="PUT"
+	json={{
+		value: "1.2",
 	}}
 	parameters={{
-		setting_id: "min_tls_version"
+		setting_id: "min_tls_version",
 	}}
 />
 
@@ -100,7 +107,6 @@ In the following example, the minimum TLS version for a specific hostname will b
 
 If you are a SaaS provider looking to configure minimum TLS version for your custom hostnames, refer to the Cloudflare for SaaS [TLS management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version).
 
-
 ## Test supported TLS versions
 
-<Render file="test-tls-version" product="ssl" />
\ No newline at end of file
+<Render file="test-tls-version" product="ssl" />
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
index 0e4362cf11468cb..f302408667237f8 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
@@ -10,7 +10,14 @@ tags:
   - TLS
 ---
 
-import { Details, FeatureTable, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	Details,
+	FeatureTable,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 TLS 1.3 enables the latest version of the TLS protocol (when supported) for improved security and performance.
 
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
index 4a643427148e0dc..9de3f9a1b2d4d87 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
@@ -6,19 +6,15 @@ products:
 title: API commands
 sidebar:
   order: 5
-
 ---
 
 Use the following API commands to manage advanced certificates. If you are using our API for the first time, review our [API documentation](/fundamentals/api/).
 
-
-
-| Command                                                                                                                                                 | Method   | Endpoint                                             | Additional notes                                                                            |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                     | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
-| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                                                                             |
-| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                       | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
+| Command                                                                                                                                                        | Method   | Endpoint                                             | Additional notes                                                                            |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                                                | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
+| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                                                              | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                  |
+| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                                                   | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
 | [List certificate packs in a zone](/api/resources/ssl/subresources/certificate_packs/methods/list/)                                                            | `GET`    | `zones/<<ZONE_ID>>/ssl/certificate_packs?status=all` | This API call returns all certificate packs for a domain (Universal, Custom, and Advanced). |
 | List Cipher Suite settings: [Get zone setting](/api/resources/zones/subresources/settings/methods/get/) with `ciphers` as the setting name in the URI path     | `GET`    | `zones/<<ZONE_ID>>/settings/ciphers`                 |                                                                                             |
 | Change Cipher Suite settings: [Edit zone setting](/api/resources/zones/subresources/settings/methods/edit/) with `ciphers` as the setting name in the URI path | `PATCH`  | `zones/<<ZONE_ID>>/settings/ciphers`                 | To restore default settings, send a blank array in the `value` parameter.                   |
-
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
index 8bb9170bb3e5e55..6261626f47813e8 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
@@ -10,7 +10,13 @@ description: Learn how to create, delete and perform other operations to manage
   your Cloudflare Advanced SSL certificates.
 ---
 
-import { AvailableNotifications, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	AvailableNotifications,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 ## Create a certificate
 
diff --git a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
index cd1a9df4c9a9acd..9612b1b4e300149 100644
--- a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
@@ -6,10 +6,9 @@ products:
 title: Backup certificates
 sidebar:
   order: 9
-
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 If Cloudflare is providing [authoritative DNS](/dns/zone-setups/full-setup/) for your domain, Cloudflare will issue a backup [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for every standard Universal certificate issued.
 
diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx
index 81472be5e1532d4..d8baa4eef05cff2 100644
--- a/src/content/docs/ssl/edge-certificates/caa-records.mdx
+++ b/src/content/docs/ssl/edge-certificates/caa-records.mdx
@@ -77,4 +77,3 @@ Check CAA at all levels of your CNAME chain:
 dig yourdomain.com CAA +short
 dig cname-target.com CAA +short
 ```
-
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
index cc1c3b4df79dbed..96fb56d94da1db3 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
@@ -6,7 +6,6 @@ products:
 title: Bundle methodologies
 sidebar:
   order: 4
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -43,4 +42,4 @@ The related value for the `bundle_method` parameter when using the [API](/api/re
 
 User-defined allows you to paste your own certificate chain and present that bundle to clients. If you are using a self-signed certificate (not recommended), you must use this mode.
 
-The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
\ No newline at end of file
+The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
index b6e2aa56fcc596a..450b178703c442c 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
@@ -8,10 +8,9 @@ sidebar:
 head: []
 description: Learn how renewal and expiration work when using Cloudflare Custom
   SSL certificates.
-
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components";
 
 ## Renew custom certificates
 
diff --git a/src/content/docs/ssl/edge-certificates/ech.mdx b/src/content/docs/ssl/edge-certificates/ech.mdx
index 0fbfdfc7d498d82..f41c594d329fe41 100644
--- a/src/content/docs/ssl/edge-certificates/ech.mdx
+++ b/src/content/docs/ssl/edge-certificates/ech.mdx
@@ -35,7 +35,7 @@ In practice, this means that any intermediary that is looking at your traffic wi
 
 In the example below, a user is visiting `example.com`. Without ECH, any intermediate networks will be able to detect the website being accessed by the user. With ECH, the visible information will be limited to `cloudflare-ech.com` instead.
 
-<br/>
+<br />
 
 ```mermaid
 flowchart LR
@@ -46,7 +46,7 @@ A(User visits <code>example.com</code>)
     A -- Without ECH  --> D(intermediaries see <code>example.com</code>)-->B(Cloudflare)
 ```
 
-<br/>
+<br />
 
 For more details about ECH protocol technology, refer to our [introductory blog](https://blog.cloudflare.com/encrypted-client-hello/).
 
diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
index 1f5ef82895c17f4..01b85e22786233d 100644
--- a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
+++ b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
@@ -31,7 +31,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 | WEUR        | Western Europe        |
 | WNAM        | Western North America |
 
-***
+---
 
 ## Available countries
 
@@ -39,7 +39,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 
 Examples of supported countries are Japan, Canada, India, and Australia.
 
-***
+---
 
 ## Highest security data centers
 
diff --git a/src/content/docs/ssl/edge-certificates/index.mdx b/src/content/docs/ssl/edge-certificates/index.mdx
index ffb763f9a56da56..e7cf9b2a13c1a4d 100644
--- a/src/content/docs/ssl/edge-certificates/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/index.mdx
@@ -22,7 +22,7 @@ This behavior occurs when all of the following conditions are true:
 
 - The zone is on a [subdomain setup](/dns/zone-setups/subdomain-setup/).
 - The certificate has a subject or SAN that is a wildcard for the zone's parent domain.
-:::
+  :::
 
 ## Use cases
 
diff --git a/src/content/docs/ssl/edge-certificates/staging-environment.mdx b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
index 339031829e8da8c..19eb3fbbdf32035 100644
--- a/src/content/docs/ssl/edge-certificates/staging-environment.mdx
+++ b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
@@ -8,22 +8,21 @@ sidebar:
   order: 8
   badge:
     text: Beta
-
 ---
 
-import { FeatureTable, DashButton } from "~/components"
+import { FeatureTable, DashButton } from "~/components";
 
 Use your certificate staging environment to test new custom (modern) certificates before pushing them to your production environment. This process helps you solve potential certificate problems **before** there's an incident, such as when:
 
-* You make a mistake when uploading a new custom certificate.
-* You misunderstand the order of your certificates.
-* Clients have previously pinned your custom certificate, causing a TLS termination error.
+- You make a mistake when uploading a new custom certificate.
+- You misunderstand the order of your certificates.
+- Clients have previously pinned your custom certificate, causing a TLS termination error.
 
 ## Availability
 
 <FeatureTable id="ssl.staging_environment" />
 
-***
+---
 
 ## Use your staging environment
 
@@ -49,9 +48,9 @@ curl --resolve <HOSTNAME>:<PORT>:<STAGING_IP> https://<HOSTNAME> -iv
 
 You should confirm whether:
 
-* TLS termination is successful.
-* The right certificate is being served at the edge.
-* Any clients are pinning the old certificate.
+- TLS termination is successful.
+- The right certificate is being served at the edge.
+- Any clients are pinning the old certificate.
 
 ### 3. Push certificate to production
 
@@ -78,7 +77,7 @@ If you roll out a custom (modern) certificate to production and encounter issues
 3. Select **Deactivate**.
 4. Select **Push to Staging**.
 
-***
+---
 
 ## Limitations
 
@@ -90,5 +89,5 @@ Currently, staging environments are only available to Enterprise customers parti
 
 At the moment, staging environments have limited functionality:
 
-* Only custom (modern) certificates
-* Only accessed via the dashboard
+- Only custom (modern) certificates
+- Only accessed via the dashboard
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
index 3104afffd410349..70ebac7297e8244 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
@@ -9,13 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Universal SSL
-
 ---
 
-import { AvailableNotifications, Render } from "~/components"
+import { AvailableNotifications, Render } from "~/components";
 
 You can configure alerts to receive notifications for changes in your certificates.
 
-<AvailableNotifications product="SSL/TLS" notificationFilter="Universal SSL Alert" />
+<AvailableNotifications
+	product="SSL/TLS"
+	notificationFilter="Universal SSL Alert"
+/>
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
index b594fc5113be2e0..818182201a137ed 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
@@ -25,13 +25,11 @@ To avoid errors with your domain, either [upload a custom certificate](/ssl/edge
 If you disable Universal SSL, you may experience errors with the following scenarios:
 
 - **Enabled features**:
-
   - [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/)
   - [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/)
   - [Opportunistic Encryption](/ssl/edge-certificates/additional-options/opportunistic-encryption/)
 
 - **Other setups**:
-
   - [Page Rules](/rules/page-rules/) that redirect traffic to HTTPS
   - HTTP to HTTPS redirects at your origin web server
 
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
index 9caba32b58ee4c2..e18e34ce743050c 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
@@ -17,10 +17,10 @@ If a certificate issuance times out, Cloudflare tells you where in the chain of
 
 To resolve timeout issues, try one or more of the following options:
 
-* Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
-* [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
-* Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
-* Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
+- Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
+- [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
+- Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
+- Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
 
 ## Delete certificates
 
diff --git a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
index f525157d8b998f3..08f0a67ed984db2 100644
--- a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Get started with Keyless SSL
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The way you set up Keyless SSL depends on how you route traffic to your keyless server.
 
diff --git a/src/content/docs/ssl/keyless-ssl/glossary.mdx b/src/content/docs/ssl/keyless-ssl/glossary.mdx
index e64a45f3d972083..ac939b4a2946953 100644
--- a/src/content/docs/ssl/keyless-ssl/glossary.mdx
+++ b/src/content/docs/ssl/keyless-ssl/glossary.mdx
@@ -9,7 +9,6 @@ head:
   - tag: title
     content: Glossary | Keyless SSL
 description: Learn more about the common terms related to Keyless SSL.
-
 ---
 
 ## Cloudflare Keyless SSL key server (“key server”)
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
index 0ca6a0fe976beb8..3804977bcd01432 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
@@ -69,7 +69,6 @@ brew install azure-cli
    ```
 
 4. If the key server is running in an Azure VM in the same account, use **Managed services** for authorization:
-
    1. Enable managed services on the VM in the UI.
    2. Give your service user (associated with your VM) HSM sign permissions
 
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
index df9caf0b486ccaf..18a3cbbad52b8b7 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
@@ -14,4 +14,4 @@ You can use Cloudflare Keyless SSL with [Fortanix Data Security Manager (DSM)](h
 
 You must have a [Data Security Manager Enterprise Tier](https://www.fortanix.com/start-your-free-trial) and set up a group and an application assigned to the group.
 
-For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
\ No newline at end of file
+For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
index fd448a9791cb833..a28200144687ee8 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
@@ -6,12 +6,11 @@ products:
 title: Hardware security modules
 sidebar:
   order: 2
-
 ---
 
 In addition to private keys stored on disk, Keyless SSL supports keys stored in a Hardware Security Module (HSM) via the PKCS#11 standard. Keyless uses PKCS#11 for signing and decrypting payloads without having direct access to the private keys.
 
-***
+---
 
 ## Why use Keyless SSL with an HSM?
 
@@ -19,7 +18,7 @@ Hardware Security Modules (HSMs) facilitate a higher level of protection for you
 
 Moreover, many HSMs are also capable of generating keys and producing cryptographically secure randomness. Some are purpose-built to perform cryptographic computations more efficiently.
 
-***
+---
 
 ## Communicating using PKCS#11
 
@@ -45,4 +44,4 @@ Also, the following cloud HSM offerings have been tested with Keyless SSL:
 - [Azure Managed HSM](/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm/)
 - [Fortanix DSM](/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm/)
 - [IBM Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/ibm-cloud-hsm/)
-- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
\ No newline at end of file
+- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
diff --git a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
index 459196f2dd78e7d..f2176ee72e743cd 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
@@ -6,7 +6,6 @@ products:
 title: High availability
 sidebar:
   order: 3
-
 ---
 
 The Cloudflare Keyless SSL server runs as a single binary with minimal dependencies and is designed to be robust and reliable. However, the network between your key server and Cloudflare may not be, which could prevent new TLS connections.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/index.mdx b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
index 4c22ae751c29b2c..78c6fba61f6ed5e 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Reference — Keyless SSL
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more information on Keyless SSL, refer to the following resources:
 
diff --git a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
index 08105e84ad0afe6..b0c023f66fe907a 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
@@ -8,7 +8,6 @@ tags:
   - TLS
 sidebar:
   order: 7
-
 ---
 
 Keyless Delegation is Cloudflare's implementation of the emerging delegated credentials standard ([RFC 9345](https://www.rfc-editor.org/rfc/rfc9345.html)). When you upload a certificate for use with Keyless that has the special extension permitting the use of delegated credentials, Cloudflare will automatically produce a delegated credential and use it at the edge with clients that support this feature. The handshakes will complete without the extra latency induced by reaching back to the Keyless Server, and there are [additional advantages to flexibility in algorithm choice](https://blog.cloudflare.com/keyless-delegation/).
diff --git a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
index 0e9d1a59aa73910..292a3c66bcec5c5 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
@@ -6,13 +6,10 @@ products:
 title: Key server metrics
 sidebar:
   order: 5
-
 ---
 
 The gokeyless key server exposes a [Prometheus](https://prometheus.io/) metrics endpoint that you can use to monitor signing performance, error rates, connection health, and certificate expiry. This endpoint can also be scraped by the OpenTelemetry Collector Prometheus receiver, making the metrics available to any OpenTelemetry-compatible backend.
 
-
-
 ## Metrics endpoint
 
 By default, metrics are served at:
@@ -31,24 +28,24 @@ The endpoint serves only `/metrics`. There are no additional HTTP endpoints such
 
 All histogram metrics share the same bucket configuration: 15 exponential buckets starting at 100 microseconds, doubling each step up to approximately 1.64 seconds, plus a final `+Inf` bucket.
 
-| Bucket | Upper bound |
-| --- | --- |
-| 1 | 100 µs |
-| 2 | 200 µs |
-| 3 | 400 µs |
-| 4 | 800 µs |
-| 5 | 1.6 ms |
-| 6 | 3.2 ms |
-| 7 | 6.4 ms |
-| 8 | 12.8 ms |
-| 9 | 25.6 ms |
-| 10 | 51.2 ms |
-| 11 | 102 ms |
-| 12 | 205 ms |
-| 13 | 410 ms |
-| 14 | 819 ms |
-| 15 | ~1.64 s |
-| +Inf | Anything above ~1.64 s |
+| Bucket | Upper bound            |
+| ------ | ---------------------- |
+| 1      | 100 µs                 |
+| 2      | 200 µs                 |
+| 3      | 400 µs                 |
+| 4      | 800 µs                 |
+| 5      | 1.6 ms                 |
+| 6      | 3.2 ms                 |
+| 7      | 6.4 ms                 |
+| 8      | 12.8 ms                |
+| 9      | 25.6 ms                |
+| 10     | 51.2 ms                |
+| 11     | 102 ms                 |
+| 12     | 205 ms                 |
+| 13     | 410 ms                 |
+| 14     | 819 ms                 |
+| 15     | ~1.64 s                |
+| +Inf   | Anything above ~1.64 s |
 
 :::note
 When using a hardware security module (HSM) with a PKCS#11 session pool, the pool wait timeout is hardcoded at 10 seconds. A pool exhaustion event will therefore always appear in the `+Inf` bucket. Spikes in `+Inf` observations on signing operations with `error="cryptography error"` are a direct indicator of PKCS#11 session pool saturation.
@@ -69,45 +66,45 @@ The `opcode` label uses the full constant name from the gokeyless protocol.
 
 #### RSA operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpRSADecrypt` | `0x01` | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3) |
-| `OpRSASignMD5SHA1` | `0x02` | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
-| `OpRSASignSHA1` | `0x03` | RSA PKCS#1 v1.5 signature over SHA1 |
-| `OpRSASignSHA224` | `0x04` | RSA PKCS#1 v1.5 signature over SHA224 |
-| `OpRSASignSHA256` | `0x05` | RSA PKCS#1 v1.5 signature over SHA256 |
-| `OpRSASignSHA384` | `0x06` | RSA PKCS#1 v1.5 signature over SHA384 |
-| `OpRSASignSHA512` | `0x07` | RSA PKCS#1 v1.5 signature over SHA512 |
-| `OpRSAPSSSignSHA256` | `0x35` | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3 |
-| `OpRSAPSSSignSHA384` | `0x36` | RSASSA-PSS signature over SHA384 |
-| `OpRSAPSSSignSHA512` | `0x37` | RSASSA-PSS signature over SHA512 |
+| `opcode` label       | Wire value | Description                                                                   |
+| -------------------- | ---------- | ----------------------------------------------------------------------------- |
+| `OpRSADecrypt`       | `0x01`     | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3)     |
+| `OpRSASignMD5SHA1`   | `0x02`     | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
+| `OpRSASignSHA1`      | `0x03`     | RSA PKCS#1 v1.5 signature over SHA1                                           |
+| `OpRSASignSHA224`    | `0x04`     | RSA PKCS#1 v1.5 signature over SHA224                                         |
+| `OpRSASignSHA256`    | `0x05`     | RSA PKCS#1 v1.5 signature over SHA256                                         |
+| `OpRSASignSHA384`    | `0x06`     | RSA PKCS#1 v1.5 signature over SHA384                                         |
+| `OpRSASignSHA512`    | `0x07`     | RSA PKCS#1 v1.5 signature over SHA512                                         |
+| `OpRSAPSSSignSHA256` | `0x35`     | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3           |
+| `OpRSAPSSSignSHA384` | `0x36`     | RSASSA-PSS signature over SHA384                                              |
+| `OpRSAPSSSignSHA512` | `0x37`     | RSASSA-PSS signature over SHA512                                              |
 
 #### ECDSA operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpECDSASignMD5SHA1` | `0x12` | ECDSA signature over MD5+SHA1 combined hash |
-| `OpECDSASignSHA1` | `0x13` | ECDSA signature over SHA1 |
-| `OpECDSASignSHA224` | `0x14` | ECDSA signature over SHA224 |
-| `OpECDSASignSHA256` | `0x15` | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
-| `OpECDSASignSHA384` | `0x16` | ECDSA signature over SHA384 |
-| `OpECDSASignSHA512` | `0x17` | ECDSA signature over SHA512 |
+| `opcode` label       | Wire value | Description                                                      |
+| -------------------- | ---------- | ---------------------------------------------------------------- |
+| `OpECDSASignMD5SHA1` | `0x12`     | ECDSA signature over MD5+SHA1 combined hash                      |
+| `OpECDSASignSHA1`    | `0x13`     | ECDSA signature over SHA1                                        |
+| `OpECDSASignSHA224`  | `0x14`     | ECDSA signature over SHA224                                      |
+| `OpECDSASignSHA256`  | `0x15`     | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
+| `OpECDSASignSHA384`  | `0x16`     | ECDSA signature over SHA384                                      |
+| `OpECDSASignSHA512`  | `0x17`     | ECDSA signature over SHA512                                      |
 
 #### Other signing
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpEd25519Sign` | `0x18` | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
+| `opcode` label  | Wire value | Description                                                                  |
+| --------------- | ---------- | ---------------------------------------------------------------------------- |
+| `OpEd25519Sign` | `0x18`     | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
 
 #### Sealing and infrastructure operations
 
-| `opcode` label | Wire value | Description |
-| --- | --- | --- |
-| `OpSeal` | `0x21` | Encrypt a blob using the server's sealing key — used for TLS session tickets |
-| `OpUnseal` | `0x22` | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated |
-| `OpRPC` | `0x23` | Execute a named function registered on the server. Available to all connection types |
-| `OpCustom` | `0x24` | Execute a custom function set in the server configuration. Available to unrestricted connections only |
-| `OpPing` | `0xF1` | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved |
+| `opcode` label | Wire value | Description                                                                                           |
+| -------------- | ---------- | ----------------------------------------------------------------------------------------------------- |
+| `OpSeal`       | `0x21`     | Encrypt a blob using the server's sealing key — used for TLS session tickets                          |
+| `OpUnseal`     | `0x22`     | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated  |
+| `OpRPC`        | `0x23`     | Execute a named function registered on the server. Available to all connection types                  |
+| `OpCustom`     | `0x24`     | Execute a custom function set in the server configuration. Available to unrestricted connections only |
+| `OpPing`       | `0xF1`     | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved      |
 
 ---
 
@@ -124,15 +121,15 @@ This metric does not include time a request spends waiting for a connection sema
 
 Opcodes are grouped into coarser categories for this label:
 
-| `type` label | Opcodes included |
-| --- | --- |
-| `rsa` | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*` |
-| `ecdsa` | All `OpECDSASign*` |
-| `ed25519` | `OpEd25519Sign` |
-| `rpc` | `OpRPC` |
-| `custom` | `OpCustom` |
-| `other` | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
-| `unknown` | Any unrecognised opcode byte |
+| `type` label | Opcodes included                                                  |
+| ------------ | ----------------------------------------------------------------- |
+| `rsa`        | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*`             |
+| `ecdsa`      | All `OpECDSASign*`                                                |
+| `ed25519`    | `OpEd25519Sign`                                                   |
+| `rpc`        | `OpRPC`                                                           |
+| `custom`     | `OpCustom`                                                        |
+| `other`      | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
+| `unknown`    | Any unrecognised opcode byte                                      |
 
 :::note
 `OpPing` is grouped into `other` alongside `OpSeal` and `OpUnseal`. Ping round-trip latency cannot be separated from seal and unseal operation latency in this metric.
@@ -142,20 +139,20 @@ Opcodes are grouped into coarser categories for this label:
 
 For successful requests the value is `no error`. All other values indicate a failed operation.
 
-| `error` label | Description | Common cause |
-| --- | --- | --- |
-| `no error` | Operation completed successfully | — |
-| `cryptography error` | HSM or signing operation failed | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
-| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result | Key not loaded in keystore, incorrect SKI in request |
-| `read failure` | I/O read error during the operation | Disk error reading key file |
-| `version mismatch` | Protocol version not supported | Client and server version skew |
-| `bad opcode` | Unknown opcode received | `OpCustom` sent with no custom handler configured |
-| `unexpected opcode` | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request |
-| `malformed message` | TLV parse failure | Corrupt or truncated packet |
-| `internal error` | Non-cryptographic server-side failure | Sealer is nil, RPC dispatch error |
-| `certificate not found` | Certificate lookup failed | Certificate not loaded |
-| `sealing key expired` | `OpUnseal` blob is too old to decrypt | TLS session ticket key rotation — blob sealed with a key that has since been retired |
-| `remote configuration error` | Remote key server is misconfigured | Key points to an unreachable or misconfigured remote key server |
+| `error` label                                       | Description                             | Common cause                                                                                          |
+| --------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `no error`                                          | Operation completed successfully        | —                                                                                                     |
+| `cryptography error`                                | HSM or signing operation failed         | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
+| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result           | Key not loaded in keystore, incorrect SKI in request                                                  |
+| `read failure`                                      | I/O read error during the operation     | Disk error reading key file                                                                           |
+| `version mismatch`                                  | Protocol version not supported          | Client and server version skew                                                                        |
+| `bad opcode`                                        | Unknown opcode received                 | `OpCustom` sent with no custom handler configured                                                     |
+| `unexpected opcode`                                 | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request                                         |
+| `malformed message`                                 | TLV parse failure                       | Corrupt or truncated packet                                                                           |
+| `internal error`                                    | Non-cryptographic server-side failure   | Sealer is nil, RPC dispatch error                                                                     |
+| `certificate not found`                             | Certificate lookup failed               | Certificate not loaded                                                                                |
+| `sealing key expired`                               | `OpUnseal` blob is too old to decrypt   | TLS session ticket key rotation — blob sealed with a key that has since been retired                  |
+| `remote configuration error`                        | Remote key server is misconfigured      | Key points to an unreachable or misconfigured remote key server                                       |
 
 ---
 
@@ -197,16 +194,16 @@ It is **not** recorded for `OpPing`, `OpSeal`, `OpUnseal`, `OpRPC`, or `OpCustom
 
 Counts connection-level transport failures. This metric reflects problems at the network or TLS layer — it does not count signing errors or key lookup failures, which are reported in the `error` label of the duration histograms.
 
-| Scenario | Counted? |
-| --- | --- |
-| TLS handshake failure | No |
-| Client disconnected before TLS handshake (EOF) | No |
-| Failure determining connection trust level after TLS | Yes |
-| Non-EOF read error on an established connection | Yes |
-| Write error when delivering a response | Yes |
-| Read timeout — graceful connection drain | No |
-| Signing error, including PKCS#11 pool timeout | No |
-| Key not found | No |
+| Scenario                                             | Counted? |
+| ---------------------------------------------------- | -------- |
+| TLS handshake failure                                | No       |
+| Client disconnected before TLS handshake (EOF)       | No       |
+| Failure determining connection trust level after TLS | Yes      |
+| Non-EOF read error on an established connection      | Yes      |
+| Write error when delivering a response               | Yes      |
+| Read timeout — graceful connection drain             | No       |
+| Signing error, including PKCS#11 pool timeout        | No       |
+| Key not found                                        | No       |
 
 ---
 
@@ -218,18 +215,19 @@ Counts connection-level transport failures. This metric reflects problems at the
 Reports the expiration time (`NotAfter`) of each certificate loaded by the key server as a Unix timestamp. One time series is emitted per certificate.
 
 This metric is updated:
+
 - At startup, for the server authentication certificate (`auth_cert`) and the Cloudflare CA certificate (`cloudflare_ca_cert`).
 - On each successful inbound TLS connection, for the peer certificates presented by the connecting client.
 
-| Label | Description |
-| --- | --- |
-| `source` | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
-| `serial_no` | Certificate serial number |
-| `cn` | Subject Common Name |
-| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names |
-| `ca` | `1` if the certificate is a CA certificate, `0` otherwise |
-| `server` | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise |
-| `client` | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise |
+| Label       | Description                                                                              |
+| ----------- | ---------------------------------------------------------------------------------------- |
+| `source`    | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
+| `serial_no` | Certificate serial number                                                                |
+| `cn`        | Subject Common Name                                                                      |
+| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names                            |
+| `ca`        | `1` if the certificate is a CA certificate, `0` otherwise                                |
+| `server`    | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise                   |
+| `client`    | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise                   |
 
 :::note
 `server_utilization` is a registered `GaugeVec` metric that is never written to by the key server. Because no label values are ever set, it emits no time series in the `/metrics` output at all. Do not use it.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
index 22b7833a2be107e..4edb4db09bab546 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
@@ -6,7 +6,6 @@ products:
 title: Scaling and benchmarking
 sidebar:
   order: 4
-
 ---
 
 Cloudflare's Keyless SSL technology was designed to scale to accommodate any sized workload using vertical and horizontal scaling, and pre-computation techniques wherever possible, such as ECDSA. The goals of the architectural design of the key server are to minimize latency while maximizing signing operations per second.
@@ -15,7 +14,7 @@ Each key server uses a worker pool model, with incoming client connections handl
 
 Where needed, multiple key servers can be deployed and balanced between using your preferred ingress load balancing configuration. For full high availability, make sure to deploy sufficient key servers to handle twice the expected workload.
 
-***
+---
 
 ## Key type
 
@@ -25,7 +24,7 @@ ECDSA signing can be broken down into two steps. Since the first step — genera
 
 Additional details can be found in the [gokeyless server readme file](https://github.com/cloudflare/gokeyless#readme) file.
 
-***
+---
 
 ## Benchmarks
 
diff --git a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
index 4f8047f3f0bc964..725673be1dbd8c2 100644
--- a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
+++ b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
@@ -6,7 +6,6 @@ products:
 title: Upgrade your key server
 sidebar:
   order: 4
-
 ---
 
 Periodically, you may need to update your key server when using Cloudflare's Keyless SSL.
@@ -25,8 +24,6 @@ To upgrade your key server:
 
 :::caution
 
-
 If you are running a [high availability configuration](/ssl/keyless-ssl/reference/high-availability/), upgrade one server at a time as new TLS connections will fail to terminate at Cloudflare's global network without a functioning key server.
 
-
 :::
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
index c8ca40f070b5e2a..bda18f6939d8966 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
@@ -24,10 +24,9 @@ Global, [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/
 - Make sure your zone is using an [SSL/TLS encryption mode](/ssl/origin-configuration/ssl-modes/) of **Full** or higher.
 
 - Consider your security and certificate needs:
+  - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
 
-   - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
-
-   - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
+  - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
 
 ## 1. Download the Cloudflare certificate
 
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
index d2d6befaa600c0d..5ab7622aa6b0069 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
@@ -11,9 +11,8 @@ sidebar:
 head:
   - tag: title
     content: Set up Authenticated Origin Pulls
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
index 051fcf061c534ca..8a042656568dd34 100644
--- a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
+++ b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
@@ -28,19 +28,19 @@ The list order is based on how the cipher suites appear in the [ClientHello](htt
 
 | Cipher name                        | TLS 1.0 | TLS 1.1 | TLS 1.2 | TLS 1.3 |
 | ---------------------------------- | ------- | ------- | ------- | ------- |
-| AEAD-AES128-GCM-SHA256 [^1]        | ❌       | ❌       | ❌       | ✅       |
-| AEAD-AES256-GCM-SHA384 [^1]        | ❌       | ❌       | ❌       | ✅       |
-| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌       | ❌       | ❌       | ✅       |
-| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES128-GCM-SHA256        | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES128-SHA               | ✅       | ✅       | ✅       | ❌       |
-| AES128-GCM-SHA256                  | ❌       | ❌       | ✅       | ❌       |
-| AES128-SHA                         | ✅       | ✅       | ✅       | ❌       |
-| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES256-GCM-SHA384        | ❌       | ❌       | ✅       | ❌       |
-| ECDHE-RSA-AES256-SHA384            | ❌       | ❌       | ✅       | ❌       |
-| AES256-SHA                         | ✅       | ✅       | ✅       | ❌       |
-| DES-CBC3-SHA                       | ✅       | ❌       | ❌       | ❌       |
+| AEAD-AES128-GCM-SHA256 [^1]        | ❌      | ❌      | ❌      | ✅      |
+| AEAD-AES256-GCM-SHA384 [^1]        | ❌      | ❌      | ❌      | ✅      |
+| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌      | ❌      | ❌      | ✅      |
+| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES128-GCM-SHA256        | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES128-SHA               | ✅      | ✅      | ✅      | ❌      |
+| AES128-GCM-SHA256                  | ❌      | ❌      | ✅      | ❌      |
+| AES128-SHA                         | ✅      | ✅      | ✅      | ❌      |
+| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES256-GCM-SHA384        | ❌      | ❌      | ✅      | ❌      |
+| ECDHE-RSA-AES256-SHA384            | ❌      | ❌      | ✅      | ❌      |
+| AES256-SHA                         | ✅      | ✅      | ✅      | ❌      |
+| DES-CBC3-SHA                       | ✅      | ❌      | ❌      | ❌      |
 
 ### TLS 1.3 cipher suites
 
@@ -67,4 +67,4 @@ ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RS
 ssl_prefer_server_ciphers on;
 ```
 
-[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
\ No newline at end of file
+[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
diff --git a/src/content/docs/ssl/origin-configuration/index.mdx b/src/content/docs/ssl/origin-configuration/index.mdx
index aac15f2f4132e15..ca68ac364da293b 100644
--- a/src/content/docs/ssl/origin-configuration/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn more about SSL/TLS protection options for your origin servers:
 
diff --git a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
index b417523729d50b6..6669b3202cadc81 100644
--- a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
+++ b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
@@ -64,7 +64,7 @@ If the user does not have **API Access**, this error is returned.
 
 Make sure that the user creating the certificate has access to the API. You can check in the account **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+<DashButton url="/?to=/:account/members" />
 
 - The default setting for the account is specified in the card **Enable API Access**.
 - Specific user API Access (which can override the default setting) is presented after selecting the user in the list of members.
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
index 087e14efa75240d..c19aaa19e4e96d1 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
@@ -16,9 +16,9 @@ import { Stream, Render, TabItem, Tabs } from "~/components";
 When you set your encryption mode to **Full**, Cloudflare allows HTTPS connections between your visitor and Cloudflare and makes connections to the origin using the scheme requested by the visitor. If your visitor uses `http`, then Cloudflare connects to the origin using plaintext HTTP and vice versa.
 
 <Stream
-  id="a1e79096a2b042e0525a8543c232279a"
-  title="Configure Full encryption mode"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
+	id="a1e79096a2b042e0525a8543c232279a"
+	title="Configure Full encryption mode"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
 />
 
 ## Use when
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
index d914207fd292d04..ffbf39cb4685b3c 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
@@ -45,7 +45,7 @@ Automatic SSL/TLS leverages advanced methods developed by the SSL/TLS Recommende
 Automatic SSL/TLS will not change your setting to a less secure encryption mode. For example, if your origin certificate expires, the encryption mode will not change from **Full (strict)** to **Full**. You must ensure the validity of your origin SSL/TLS configuration at all times.
 :::
 
-Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode.  If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
+Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode. If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
 
 Flexible → Full/Strict transitions are handled with extra caution since the origin scheme change (HTTP → HTTPS) alters cache keys. In this case, the ramp-up may proceed more slowly to allow cache warm-up before resuming standard increments.
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
index 60489481ea636f2..44f4f531ad50fd4 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
@@ -23,12 +23,11 @@ When you set your encryption mode to **Strict (SSL-Only Origin Pull)**, connecti
 The certificate presented by the origin will be validated the same as with [Full (strict) mode](/ssl/origin-configuration/ssl-modes/full-strict/).
 
 <Stream
-  id="f407072cb5b4837c8c3a58a69cde90b5"
-  title="Configure Strict encryption mode"
-  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
+	id="f407072cb5b4837c8c3a58a69cde90b5"
+	title="Configure Strict encryption mode"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
 />
 
-
 ## Use when
 
 You want the most secure configuration available for your origin, you are an Enterprise customer, and you meet the requirements for [**Full (strict)** mode](/ssl/origin-configuration/ssl-modes/full-strict/).
diff --git a/src/content/docs/ssl/reference/all-features.mdx b/src/content/docs/ssl/reference/all-features.mdx
index 83243c2d35356e9..e4526a1b070534c 100644
--- a/src/content/docs/ssl/reference/all-features.mdx
+++ b/src/content/docs/ssl/reference/all-features.mdx
@@ -7,13 +7,12 @@ sidebar:
   order: 9
 head: []
 description: Review information on all Cloudflare SSL/TLS features and their availability.
-
 ---
 
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="ssl" />
\ No newline at end of file
+<ProductFeatures id="ssl" />
diff --git a/src/content/docs/ssl/reference/browser-compatibility.mdx b/src/content/docs/ssl/reference/browser-compatibility.mdx
index a7af16592d73bd7..964b497ae00d5c6 100644
--- a/src/content/docs/ssl/reference/browser-compatibility.mdx
+++ b/src/content/docs/ssl/reference/browser-compatibility.mdx
@@ -8,7 +8,6 @@ sidebar:
 head: []
 description: Review information about browser compatibility for the different
   Cloudflare SSL/TLS offerings.
-
 ---
 
 Cloudflare attempts to provide compatibility for as wide a range of user agents (browsers, API clients, etc.) as possible. However, the specific set of supported clients can vary depending on the different SSL/TLS certificate types, your visitor's [browser version](#non-sni-support), and the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that issues the certificate.
@@ -31,13 +30,13 @@ Although [SNI extensions](https://www.cloudflare.com/learning/ssl/what-is-sni/)
 
 To support non-SNI requests, you can:
 
-* [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
+- [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
 
   Note that `Legacy` custom certificates are not compatible with [BYOIP](/byoip/) and that, unlike [Universal SSL](/ssl/edge-certificates/universal-ssl/) or [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/), Cloudflare does not manage issuance and renewal for [custom certificates](/ssl/edge-certificates/custom-certificates/).
 
-* (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
+- (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
 
-* (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
+- (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
 
 ## HTTPS records
 
@@ -55,4 +54,4 @@ If you need HTTPS records without Universal SSL, you can manually add them, but
 
 Cloudflare's OCSP implementation uses HTTP/1.1 by default for plain HTTP connections.
 
-For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
\ No newline at end of file
+For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
diff --git a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
index 2c27bca6871ec0e..455857836c90c94 100644
--- a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
+++ b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
@@ -7,14 +7,13 @@ sidebar:
   order: 4
 head: []
 description: Learn about how Cloudflare decides which certificate and associated SSL/TLS settings to apply to individual hostnames.
-
 ---
 
 import { GlossaryTooltip } from "~/components";
 
 When a new certificate is created, Cloudflare first deploys the certificate and then serves it.
 
-***
+---
 
 ## Certificate deployment
 
@@ -42,17 +41,17 @@ For any given hostname, Cloudflare uses the following order to determine which c
 In this case, when the certificate with the closest expiration date is renewed, it will then become the one with the latest expiration date and get presented.
 :::
 
-***
+---
 
 ## Certificate presentation
 
 Cloudflare uses the following order to determine the certificate and settings used during a TLS handshake:
 
-1. **SNI match**: Certificates and settings that match the SNI hostname *exactly* take precedence.
+1. **SNI match**: Certificates and settings that match the SNI hostname _exactly_ take precedence.
 2. **SNI wildcard match**: If there is not an exact match between the hostname and SNI hostname, Cloudflare uses certificates and settings that match an SNI wildcard.
 3. **IP address**: If no SNI is presented, Cloudflare uses certificate based on the IP address (the hostname can support TLS handshakes made without SNI).
 
-***
+---
 
 ## Hostname priority
 
@@ -61,13 +60,11 @@ When multiple <GlossaryTooltip term="proxy status">proxied DNS records</Glossary
 Cloudflare determines this priority in the following order, assuming each record exists and is proxied (orange-clouded):
 
 1. **Exact hostname match**:
-
    1. [New custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) (belonging to a SaaS provider)
    2. [Legacy custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning/) (belonging to a SaaS provider)
    3. [DNS](/dns/proxy-status/) (belonging to the logical DNS zone)
 
 2. **Wildcard hostname match**:
-
    1. DNS (belonging to the logical DNS zone)
    2. New custom hostname (belonging to a SaaS provider)
 
@@ -79,9 +76,9 @@ If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudf
 
 Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`. Customer2 is a SaaS provider that creates and successfully [verifies the new custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/) `shop.example.com`. Afterward, traffic starts routing over Customer2's zone:
 
-* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
-* If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
-* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
+- If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
+- If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
+- If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
 
 #### Scenario 2
 
diff --git a/src/content/docs/ssl/reference/certificate-authorities.mdx b/src/content/docs/ssl/reference/certificate-authorities.mdx
index 0acd5bbcd68336c..07206f1e5b03d00 100644
--- a/src/content/docs/ssl/reference/certificate-authorities.mdx
+++ b/src/content/docs/ssl/reference/certificate-authorities.mdx
@@ -137,4 +137,4 @@ The following table lists the CAA record content for each CA:
 | SSL.com               | `ssl.com`                            |
 | Sectigo               | `sectigo.com`                        |
 
-[^1]: A payment gateway used with some ecommerce plugins.
\ No newline at end of file
+[^1]: A payment gateway used with some ecommerce plugins.
diff --git a/src/content/docs/ssl/reference/certificate-pinning.mdx b/src/content/docs/ssl/reference/certificate-pinning.mdx
index ab7622846e0f1d2..0c8cf4aa06ead76 100644
--- a/src/content/docs/ssl/reference/certificate-pinning.mdx
+++ b/src/content/docs/ssl/reference/certificate-pinning.mdx
@@ -7,7 +7,6 @@ sidebar:
   order: 8
 head: []
 description: Learn why Cloudflare does not support HTTP public key pinning (HPKP) and consider an alternative solution to prevent certificate misissuance.
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
index bf7f12feedcf976..0886b9f6b8540b5 100644
--- a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
+++ b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
@@ -5,7 +5,6 @@ products:
   - ssl
 source: https://support.cloudflare.com/hc/en-us/articles/4422920018317-Cloudflare-and-CVE-2019-1559
 title: Cloudflare and CVE-2019-1559
-
 ---
 
 The [GOLDENDOODLE and Zombie POODLE attacks](https://www.tripwire.com/state-of-security/vulnerability-management/zombie-poodle-goldendoodle/) affect applications that use certain cipher suites associated with TLS 1.2.
@@ -20,6 +19,6 @@ Even though your application is not vulnerable to CVE-2019-1559, some security s
 
 To remove these warnings, refer to [Customize cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) and exclude the following ciphers:
 
-* `ECDHE-ECDSA-AES256-SHA384`
-* `ECDHE-ECDSA-AES128-SHA256`
-* `ECDHE-RSA-AES256-SHA384`
+- `ECDHE-ECDSA-AES256-SHA384`
+- `ECDHE-ECDSA-AES128-SHA256`
+- `ECDHE-RSA-AES256-SHA384`
diff --git a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
index c2b34ec0ba65fc4..d90f31506bc85cd 100644
--- a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
+++ b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
@@ -34,31 +34,31 @@ Refer to [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum
 
 There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:
 
-* Header compression in TLS
-* Header compression in SPDY 3.1
-* RC4
-* SSL 3.0
-* Renegotiation with clients
-* DHE ciphersuites
-* Export-grade ciphers
+- Header compression in TLS
+- Header compression in SPDY 3.1
+- RC4
+- SSL 3.0
+- Renegotiation with clients
+- DHE ciphersuites
+- Export-grade ciphers
 
 Cloudflare mitigations protect against several attacks:
 
-* CRIME
-* BREACH
-* POODLE
-* RC4 Cryptographic Weaknesses
-* SSL Renegotiation Attack
-* Protocol Downgrade Attacks
-* FREAK
-* LogJam
-* 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
+- CRIME
+- BREACH
+- POODLE
+- RC4 Cryptographic Weaknesses
+- SSL Renegotiation Attack
+- Protocol Downgrade Attacks
+- FREAK
+- LogJam
+- 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
 
 Cloudflare provides additional mitigations for:
 
-* Heartbleed
-* Lucky Thirteen
-* CCS injection vulnerability
+- Heartbleed
+- Lucky Thirteen
+- CCS injection vulnerability
 
 Cloudflare has patched all servers against these vulnerabilities. Also, the [Cloudflare Web Application Firewall](/waf/) has managed rules that mitigate several of these vulnerabilities including Heartbleed and ShellShock.
 
@@ -70,5 +70,5 @@ Security scans that note the presence of ROBOT while on Cloudflare are a false p
 
 A vulnerability in the use of the Triple DES (3DES) encryption algorithm in the Transport Layer Security (TLS) protocol. Sweet32 is currently a proof of concept attack, there are no known examples of this in the wild. Cloudflare has manually mitigated the vulnerability for TLS 1.0 in the following manner:
 
-* The attacker must collect 32GB of data from a single TLS session.
-* Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
+- The attacker must collect 32GB of data from a single TLS session.
+- Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
diff --git a/src/content/docs/ssl/reference/index.mdx b/src/content/docs/ssl/reference/index.mdx
index cdb3e27983cc833..09459738c3be6af 100644
--- a/src/content/docs/ssl/reference/index.mdx
+++ b/src/content/docs/ssl/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 For more on Cloudflare SSL/TLS, refer to these articles:
 
diff --git a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
index 99bfb37d1c5d06d..dac25cb8479e6f3 100644
--- a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
@@ -34,14 +34,13 @@ This means that Entrust certificates will be issued using SSL.com roots.
 
 Since Cloudflare also [partners with SSL.com](/ssl/reference/certificate-authorities/), you can switch from uploading custom certificates to using Cloudflare-managed certificates. This change brings the following advantages:
 
-* Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
-* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
-* Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
-* If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
+- Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
+- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
+- Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
+- If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
 
 ## More resources
 
-* [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
-* [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
-* [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
-
+- [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
+- [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
+- [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
diff --git a/src/content/docs/ssl/reference/migration-guides/index.mdx b/src/content/docs/ssl/reference/migration-guides/index.mdx
index c7d41fe832e31ba..a2d9c7e09c8f5eb 100644
--- a/src/content/docs/ssl/reference/migration-guides/index.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 These guides walk you through the migration processes associated with various changes in Cloudflare's SSL/TLS infrastructure.
 
diff --git a/src/content/docs/ssl/reference/protocols.mdx b/src/content/docs/ssl/reference/protocols.mdx
index 4431c3f94d47833..5fc1e33f6ac60f0 100644
--- a/src/content/docs/ssl/reference/protocols.mdx
+++ b/src/content/docs/ssl/reference/protocols.mdx
@@ -13,10 +13,10 @@ tags:
 
 Cloudflare supports the following TLS protocols:
 
-* TLS 1.0
-* TLS 1.1
-* TLS 1.2
-* TLS 1.3
+- TLS 1.0
+- TLS 1.1
+- TLS 1.2
+- TLS 1.3
 
 TLS 1.0 is the [version that Cloudflare sets by default](/ssl/edge-certificates/additional-options/minimum-tls/) for all customers using certificate-based encryption.
 
@@ -42,12 +42,12 @@ TLS 1.3 has become widely adopted. As a general rule, Cloudflare recommends sett
 
 However, not all browser versions support TLS 1.2 and above. Depending on your particular business situation, this may present some limitations in using stronger encryption standards:
 
-* Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
+- Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
 
-* For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
+- For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
 
 ## Related resources
 
-* [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
-* [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
-* [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
+- [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
+- [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
+- [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
diff --git a/src/content/docs/ssl/saas.mdx b/src/content/docs/ssl/saas.mdx
index 3e85a7dff75970e..fcce7104fc2969a 100644
--- a/src/content/docs/ssl/saas.mdx
+++ b/src/content/docs/ssl/saas.mdx
@@ -7,5 +7,4 @@ title: Cloudflare for SaaS
 external_link: /cloudflare-for-platforms/cloudflare-for-saas/
 sidebar:
   order: 7
-
 ---
diff --git a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
index e7e9028c7ed7c8e..3061e3715c16c1c 100644
--- a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
@@ -171,4 +171,4 @@ When clicking `Approve Certificate` on a Certificate Approval renewal email, you
 
 ### Resolution
 
-Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
\ No newline at end of file
+Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
diff --git a/src/content/docs/ssl/troubleshooting/index.mdx b/src/content/docs/ssl/troubleshooting/index.mdx
index 098ba6ffb1eb8d0..d6196df82ab4540 100644
--- a/src/content/docs/ssl/troubleshooting/index.mdx
+++ b/src/content/docs/ssl/troubleshooting/index.mdx
@@ -10,11 +10,15 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting
-
 ---
 
-import { ResourcesBySelector } from "~/components"
+import { ResourcesBySelector } from "~/components";
 
 For FAQs and other troubleshooting information, refer to the following resources:
 
-<ResourcesBySelector directory="ssl" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+<ResourcesBySelector
+	directory="ssl"
+	types={["faq", "troubleshooting"]}
+	filterables={["pcx_content_type"]}
+	showDescriptions={false}
+/>
diff --git a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
index 5b2b86f88806a9d..8499af2e2c86769 100644
--- a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
@@ -10,7 +10,6 @@ sidebar:
 learning_center:
   title: What is mixed content?
   link: https://www.cloudflare.com/learning/ssl/what-is-mixed-content/
-
 ---
 
 Domains added to Cloudflare receive SSL certificates and can serve traffic over HTTPS. However, after starting to use Cloudflare, some customers notice missing content or page rendering issues when they first serve HTTPS traffic.
@@ -21,7 +20,7 @@ Normally, if your website loads all resources securely over HTTPS, visitors obse
 
 This indicates your site has a working SSL certificate and all resources loaded by the site are loaded over HTTPS. The green lock assures visitors that their connection is safe. One of the [symptoms of mixed content](#symptoms-of-mixed-content-occurrence) is that different icons appear instead of the green lock icon.
 
-***
+---
 
 ## Symptoms of mixed content occurrence
 
@@ -31,8 +30,8 @@ Most modern browsers block HTTP requests on secure HTTPS pages. Blocked content
 
 Each web browser uses different methods to warn visitors about mixed content on a website, potentially including:
 
-* A yellow triangle or information symbol beside the URL bar
-* Messages mentioning "secure content"
+- A yellow triangle or information symbol beside the URL bar
+- Messages mentioning "secure content"
 
 ### **Console logs**
 
@@ -46,7 +45,7 @@ For mixed content errors, the browser refuses to load the resources over an inse
 
 Information on using the browser’s debug tools to locate these issues are found in the documentation for [Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content) and [Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content). Alternatively, you can view your page source and find specific references of *http\://* for paths to other resources.
 
-***
+---
 
 ## Resolution
 
@@ -60,12 +59,12 @@ There are two methods to resolve mixed content errors.
 
 ### WordPress users
 
-Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the *Automatic HTTPS rewrites* option within the plugin.
+Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the _Automatic HTTPS rewrites_ option within the plugin.
 
-***
+---
 
 ## Related resources
 
-* [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
-* [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
-* [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
+- [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
+- [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
+- [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
diff --git a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
index 3ffbddefe30f522..759b5d1a646ae8d 100644
--- a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
+++ b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
@@ -14,7 +14,11 @@ description: Learn how to troubleshoot ERR_SSL_VERSION_OR_CIPHER_MISMATCH when
 
 import { Stream, Render } from "~/components";
 
-<Stream id="03e51d8a6f9a15e16969b8cc117d9225" title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public" />
+<Stream
+	id="03e51d8a6f9a15e16969b8cc117d9225"
+	title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
+	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public"
+/>
 
 After you [add a new domain](/fundamentals/manage-domains/add-site/) to Cloudflare, your visitors' browsers might display one of the following errors:
 
diff --git a/src/content/docs/stream/edit-videos/adding-captions.mdx b/src/content/docs/stream/edit-videos/adding-captions.mdx
index a5d5afcbca787ae..1cadfef74b3cd32 100644
--- a/src/content/docs/stream/edit-videos/adding-captions.mdx
+++ b/src/content/docs/stream/edit-videos/adding-captions.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 5
 products:
   - stream
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -149,15 +148,15 @@ Example response:
 
 ```json
 {
-  "result": {
-    "language": "en",
-    "label": "English (auto-generated)",
-    "generated": true,
-    "status": "inprogress"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"language": "en",
+		"label": "English (auto-generated)",
+		"generated": true,
+		"status": "inprogress"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -253,15 +252,15 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-  "result": {
-    "language": "en",
-    "label": "English",
-    "generated": false,
-    "status": "ready"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"language": "en",
+		"label": "English",
+		"generated": false,
+		"status": "ready"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -339,23 +338,23 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-  "result": [
-    {
-      "language": "en",
-      "label": "English (auto-generated)",
-      "generated": true,
-      "status": "inprogress"
-    },
-    {
-      "language": "de",
-      "label": "Deutsch",
-      "generated": false,
-      "status": "ready"
-    }
-  ],
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": [
+		{
+			"language": "en",
+			"label": "English (auto-generated)",
+			"generated": true,
+			"status": "inprogress"
+		},
+		{
+			"language": "de",
+			"label": "Deutsch",
+			"generated": false,
+			"status": "ready"
+		}
+	],
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
@@ -371,7 +370,7 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/<VIDEO_UID>/ca
 
 ### Example response to get the caption file for a video
 
-``` text
+```text
 WEBVTT
 
 1
@@ -458,25 +457,25 @@ deleted.
 
 ```json
 {
-  "result": "",
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": "",
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Limitations
 
-* A video must be uploaded before a caption can be attached to it. In the following
+- A video must be uploaded before a caption can be attached to it. In the following
   example URLs, the video's ID is referenced as `media_id`.
-* Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
+- Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
   formatted caption files. If you have a differently formatted caption file,
   use [a tool to convert your file to WebVTT](https://subtitletools.com/convert-to-vtt-online)
   prior to uploading it.
-* Videos may include several language captions, but each language must be unique.
+- Videos may include several language captions, but each language must be unique.
   For example, a video may have English, French, and German captions associated
   with it, but it cannot have two French captions.
-* Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
+- Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
   if you need to upload a larger file.
 
 ## Most common language codes
@@ -505,4 +504,4 @@ deleted.
 | pl            | Polish           |
 | uk            | Ukrainian        |
 | my            | Burmese          |
-| th            | Thai             |
\ No newline at end of file
+| th            | Thai             |
diff --git a/src/content/docs/stream/edit-videos/player-enhancements.mdx b/src/content/docs/stream/edit-videos/player-enhancements.mdx
index c439bce5564db4f..17a4d16c0a03c04 100644
--- a/src/content/docs/stream/edit-videos/player-enhancements.mdx
+++ b/src/content/docs/stream/edit-videos/player-enhancements.mdx
@@ -4,8 +4,8 @@ title: Add player enhancements
 description: Customize the Cloudflare Stream player with branding, logos, and share links.
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 With player enhancements, you can modify your video player to incorporate elements of your branding such as your logo, and customize additional options to present to your viewers.
@@ -14,10 +14,10 @@ The player enhancements are automatically applied to videos using the Stream Pla
 
 ## Properties
 
-* `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
-* `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
-* `channel_link`: The URL users will be directed to when selecting the logo from the video player.
-* `logo`: A valid HTTPS URL for the image of your logo.
+- `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
+- `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
+- `channel_link`: The URL users will be directed to when selecting the logo from the video player.
+- `logo`: A valid HTTPS URL for the image of your logo.
 
 ## Customize your own player
 
@@ -61,6 +61,6 @@ You can also pull the JSON by using the endpoint below.
    <DashButton url="/?to=/:account/stream/videos" />
 
 2. Select a video from the list to edit it.
-4. Select the **Public Details** tab.
-5. From **Public Details**, enter information in the text fields for the properties you want to set.
-6. When you are done, select **Save**.
+3. Select the **Public Details** tab.
+4. From **Public Details**, enter information in the text fields for the properties you want to set.
+5. When you are done, select **Save**.
diff --git a/src/content/docs/stream/examples/dash-js.mdx b/src/content/docs/stream/examples/dash-js.mdx
index 08404220937a1dd..734287e03dbb82d 100644
--- a/src/content/docs/stream/examples/dash-js.mdx
+++ b/src/content/docs/stream/examples/dash-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and the DASH reference
   player (dash.js)
 tags:
diff --git a/src/content/docs/stream/examples/hls-js.mdx b/src/content/docs/stream/examples/hls-js.mdx
index aeb76104307a2ce..db446e6987ec0c9 100644
--- a/src/content/docs/stream/examples/hls-js.mdx
+++ b/src/content/docs/stream/examples/hls-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and the HLS reference
   player (hls.js)
 tags:
@@ -25,12 +24,12 @@ products:
 		<video id="video"></video>
 		<script>
 			if (Hls.isSupported()) {
-				const video = document.getElementById('video');
+				const video = document.getElementById("video");
 				const hls = new Hls();
 				hls.attachMedia(video);
 				hls.on(Hls.Events.MEDIA_ATTACHED, () => {
 					hls.loadSource(
-						'https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8'
+						"https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
 					);
 				});
 			}
diff --git a/src/content/docs/stream/examples/index.mdx b/src/content/docs/stream/examples/index.mdx
index 8fb98577e0d6f90..53469dcc7069b34 100644
--- a/src/content/docs/stream/examples/index.mdx
+++ b/src/content/docs/stream/examples/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 hideChildren: true
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/stream/examples/obs-from-scratch/index.mdx b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
index ca8948b5ccc2a81..6eab955a0b28cfb 100644
--- a/src/content/docs/stream/examples/obs-from-scratch/index.mdx
+++ b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up and start your first Live Stream using OBS (Open Broadcaster
   Software) Studio
 pcx_content_type: example
diff --git a/src/content/docs/stream/examples/rtmps_playback.mdx b/src/content/docs/stream/examples/rtmps_playback.mdx
index 206b7ad224a4c78..c614726f2680f0a 100644
--- a/src/content/docs/stream/examples/rtmps_playback.mdx
+++ b/src/content/docs/stream/examples/rtmps_playback.mdx
@@ -17,9 +17,10 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the RTMPS _playback_ key for your live input from either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/srt_playback.mdx b/src/content/docs/stream/examples/srt_playback.mdx
index 86ff42d0f0555d5..3b5100f826b36a3 100644
--- a/src/content/docs/stream/examples/srt_playback.mdx
+++ b/src/content/docs/stream/examples/srt_playback.mdx
@@ -17,9 +17,10 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the SRT Playback URL for your live input from either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/stream-player.mdx b/src/content/docs/stream/examples/stream-player.mdx
index b542eeb0bb0f3c4..a948e755d04215e 100644
--- a/src/content/docs/stream/examples/stream-player.mdx
+++ b/src/content/docs/stream/examples/stream-player.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with the Cloudflare Stream Player
 tags:
   - Playback
@@ -19,12 +18,12 @@ products:
 	<head> </head>
 	<body>
 		<div style="position: relative; padding-top: 56.25%;">
-		<iframe
-			src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-			style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-			allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-			allowfullscreen="true"
-		></iframe>
+			<iframe
+				src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+				style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+				allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+				allowfullscreen="true"
+			></iframe>
 		</div>
 	</body>
 </html>
diff --git a/src/content/docs/stream/examples/video-js.mdx b/src/content/docs/stream/examples/video-js.mdx
index e8fbb571e4df8ae..e6a2aad84dcfd9f 100644
--- a/src/content/docs/stream/examples/video-js.mdx
+++ b/src/content/docs/stream/examples/video-js.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and Video.js
 tags:
   - Playback
@@ -32,7 +31,7 @@ products:
 		</video-js>
 
 		<script>
-			const vid = document.getElementById('vid1');
+			const vid = document.getElementById("vid1");
 			const player = videojs(vid);
 		</script>
 	</body>
diff --git a/src/content/docs/stream/examples/vidstack.mdx b/src/content/docs/stream/examples/vidstack.mdx
index 50ee3a7e270f9f3..fee573dfe355731 100644
--- a/src/content/docs/stream/examples/vidstack.mdx
+++ b/src/content/docs/stream/examples/vidstack.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of video playback with Cloudflare Stream and Vidstack
 tags:
   - Playback
@@ -19,13 +18,13 @@ products:
 There's a few options to choose from when getting started with Vidstack, follow any of the links
 below to get setup. You can replace the player `src` with `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8` to test Cloudflare Stream.
 
-* [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
-* [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
-* [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
-* [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
-* [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
-* [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
-* [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
+- [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
+- [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
+- [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
+- [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
+- [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
+- [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
+- [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
 
 ## Examples
 
diff --git a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
index 67fd72638c29427..84765138fc82658 100644
--- a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
+++ b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - stream
 ---
+
 import { DashButton } from "~/components";
 
 Stream provides analytics about both live video and video uploaded to Stream, via the GraphQL API described below, as well as on the Stream **Analytics** page of the Cloudflare dashboard.
diff --git a/src/content/docs/stream/getting-analytics/index.mdx b/src/content/docs/stream/getting-analytics/index.mdx
index 0b87d38fd44efbc..ddc5d2b46f2d12e 100644
--- a/src/content/docs/stream/getting-analytics/index.mdx
+++ b/src/content/docs/stream/getting-analytics/index.mdx
@@ -6,20 +6,21 @@ sidebar:
   order: 8
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 Stream provides server-side analytics that can be used to:
 
-* Identify most viewed video content in your app or platform.
-* Identify where content is viewed from and when it is viewed.
-* Understand which creators on your platform are publishing the most viewed content, and analyze trends.
+- Identify most viewed video content in your app or platform.
+- Identify where content is viewed from and when it is viewed.
+- Understand which creators on your platform are publishing the most viewed content, and analyze trends.
 
 You can access data on either:
+
 - The Stream **Analytics** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/analytics" />
+  <DashButton url="/?to=/:account/stream/analytics" />
 
 - The [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics).
 
diff --git a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
index b4650f2f9bc28c2..2f19eae42ea7fc3 100644
--- a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
+++ b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
@@ -6,7 +6,6 @@ sidebar:
   order: 2
 products:
   - stream
-
 ---
 
 The Stream player has full support for live viewer counts by default. To get the viewer count for live videos for use with third party players, make a `GET` request to the `/views` endpoint.
diff --git a/src/content/docs/stream/manage-video-library/index.mdx b/src/content/docs/stream/manage-video-library/index.mdx
index f1c87b325b33406..b4ece17f01bbf40 100644
--- a/src/content/docs/stream/manage-video-library/index.mdx
+++ b/src/content/docs/stream/manage-video-library/index.mdx
@@ -9,4 +9,3 @@ sidebar:
 products:
   - stream
 ---
-
diff --git a/src/content/docs/stream/manage-video-library/searching.mdx b/src/content/docs/stream/manage-video-library/searching.mdx
index 385d98f5df957d0..78979f3e8fe99a6 100644
--- a/src/content/docs/stream/manage-video-library/searching.mdx
+++ b/src/content/docs/stream/manage-video-library/searching.mdx
@@ -4,7 +4,6 @@ title: Search for videos
 description: Search your Cloudflare Stream video library by name using the Stream API.
 products:
   - stream
-
 ---
 
 You can search for videos by name through the Stream API by adding a `search` query parameter to the [list media files](/api/resources/stream/methods/list/) endpoint.
diff --git a/src/content/docs/stream/stream-api.mdx b/src/content/docs/stream/stream-api.mdx
index 14a6a735991b555..3cb2866bfef54bb 100644
--- a/src/content/docs/stream/stream-api.mdx
+++ b/src/content/docs/stream/stream-api.mdx
@@ -7,5 +7,4 @@ sidebar:
   order: 11
 products:
   - stream
-
 ---
diff --git a/src/content/docs/stream/stream-live/custom-domains.mdx b/src/content/docs/stream/stream-live/custom-domains.mdx
index cbea1246aae4f56..9d386faca81de66 100644
--- a/src/content/docs/stream/stream-live/custom-domains.mdx
+++ b/src/content/docs/stream/stream-live/custom-domains.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 3
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 With custom ingest domains, you can configure your RTMPS feeds to use an ingest URL that you specify instead of using `live.cloudflare.com.`
@@ -21,7 +21,6 @@ Custom Ingest Domains cannot be configured for domains with [zone holds](/fundam
 
 :::
 
-
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
 
    <DashButton url="/?to=/:account/stream/inputs" />
diff --git a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
index de3dd780bfe12a4..6cc5f62c4cb10f5 100644
--- a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
+++ b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
@@ -9,18 +9,16 @@ sidebar:
   order: 4
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 You can enable downloads for live stream videos from the Cloudflare dashboard. Videos are available for download after they enter the **Ready** state.
 
 :::note
 
-
 Downloadable MP4s are only available for live recordings under four hours. Live recordings exceeding four hours can be played at a later time but cannot be downloaded as an MP4.
 
-
 :::
 
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
diff --git a/src/content/docs/stream/stream-live/dvr-for-live.mdx b/src/content/docs/stream/stream-live/dvr-for-live.mdx
index 47ae2985c0d2fce..3bcb1c067f39da8 100644
--- a/src/content/docs/stream/stream-live/dvr-for-live.mdx
+++ b/src/content/docs/stream/stream-live/dvr-for-live.mdx
@@ -13,14 +13,14 @@ manifest URL.
 
 ## Stream Player
 
-``` html title="Stream Player embed format"
+```html title="Stream Player embed format"
 <div style="position: relative; padding-top: 56.25%;">
-  <iframe
-    src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
-    style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-    allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-    allowfullscreen="true"
-  ></iframe>
+	<iframe
+		src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
 </div>
 ```
 
@@ -37,7 +37,7 @@ When DVR mode is enabled the Stream Player will:
 
 ## HLS manifest for custom players
 
-``` text title="HLS manifest URL format"
+```text title="HLS manifest URL format"
 https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/manifest/video.m3u8?dvrEnabled=true
 ```
 
diff --git a/src/content/docs/stream/stream-live/index.mdx b/src/content/docs/stream/stream-live/index.mdx
index 3234ba97f8bbef7..7baf513e8a40a50 100644
--- a/src/content/docs/stream/stream-live/index.mdx
+++ b/src/content/docs/stream/stream-live/index.mdx
@@ -9,7 +9,6 @@ sidebar:
   order: 4
 products:
   - stream
-
 ---
 
 Cloudflare Stream lets you or your users [stream live video](https://www.cloudflare.com/learning/video/what-is-live-streaming/), and play live video in your website or app, without managing and configuring any of your own infrastructure.
@@ -37,7 +36,7 @@ With ABR, client video players need to be provided with estimates of how much ba
 
 ### How it works
 
-If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution.  This ensures that as many viewers as possible view the highest quality level.
+If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution. This ensures that as many viewers as possible view the highest quality level.
 
 Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the manifest will be higher — a stream like this has a high bitrate and requires more bandwidth. This ensures that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
 
@@ -59,7 +58,7 @@ After the live stream ends, you can [replay live stream recordings](/stream/stre
 
 Stream Live is billed identically to the rest of Cloudflare Stream.
 
-* You pay $5 per 1000 minutes of recorded video.
-* You pay $1 per 1000 minutes of delivered video.
+- You pay $5 per 1000 minutes of recorded video.
+- You pay $1 per 1000 minutes of delivered video.
 
 All Stream Live videos are automatically recorded. There is no additional cost for encoding and packaging live videos.
diff --git a/src/content/docs/stream/stream-live/live-instant-clipping.mdx b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
index 900ea4ee817bc3f..7c329e9302fd291 100644
--- a/src/content/docs/stream/stream-live/live-instant-clipping.mdx
+++ b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
@@ -10,10 +10,8 @@ Stream supports generating clips of live streams and recordings so creators and
 
 :::note[Note:]
 
-
 Clipping works differently for uploaded / on-demand videos. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
 
-
 :::
 
 ## Prerequisites
@@ -32,18 +30,12 @@ To help users replay and seek recent content, request a preview manifest by addi
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID||INPUT_ID>/manifest/video.m3u8?duration=5m
 ```
 
-
-
-* `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
-
+- `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
 
 When the preview manifest is delivered, inspect the headers for two properties:
 
-
-
-* `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the *broadcast* start time, not the *preview* start time.
-* `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an *input* ID because the clip URL should reference the *video* ID.
-
+- `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the _broadcast_ start time, not the _preview_ start time.
+- `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an _input_ ID because the clip URL should reference the _video_ ID.
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -59,38 +51,44 @@ let currentPreviewVideoID;
 
 // Override the pLoader (playlist loader) to read the manifest headers:
 class pLoader extends Hls.DefaultConfig.loader {
-  constructor(config) {
-    super(config);
-    var load = this.load.bind(this);
-    this.load = function (context, config, callbacks) {
-      if (context.type == 'manifest') {
-        var onSuccess = callbacks.onSuccess;
-        // copy the existing onSuccess handler to fire it later.
-
-        callbacks.onSuccess = function (response, stats, context, networkDetails) {
-          // The fourth argument here is undocumented in HLS.js but contains
-          // the response object for the manifest fetch, which gives us headers:
-
-          currentPreviewStart =
-            parseFloat(networkDetails.getResponseHeader('preview-start-seconds'));
-          // Save the start time of the preview manifest
-
-          currentPreviewVideoID =
-            networkDetails.getResponseHeader('stream-media-id');
-          // Save the video ID in case the preview was loaded with an input ID
-
-          onSuccess(response, stats, context);
-          // And fire the existing success handler.
-        };
-      }
-      load(context, config, callbacks);
-    };
-  }
+	constructor(config) {
+		super(config);
+		var load = this.load.bind(this);
+		this.load = function (context, config, callbacks) {
+			if (context.type == "manifest") {
+				var onSuccess = callbacks.onSuccess;
+				// copy the existing onSuccess handler to fire it later.
+
+				callbacks.onSuccess = function (
+					response,
+					stats,
+					context,
+					networkDetails,
+				) {
+					// The fourth argument here is undocumented in HLS.js but contains
+					// the response object for the manifest fetch, which gives us headers:
+
+					currentPreviewStart = parseFloat(
+						networkDetails.getResponseHeader("preview-start-seconds"),
+					);
+					// Save the start time of the preview manifest
+
+					currentPreviewVideoID =
+						networkDetails.getResponseHeader("stream-media-id");
+					// Save the video ID in case the preview was loaded with an input ID
+
+					onSuccess(response, stats, context);
+					// And fire the existing success handler.
+				};
+			}
+			load(context, config, callbacks);
+		};
+	}
 }
 
 // Specify the new loader class when setting up HLS
 const hls = new Hls({
-  pLoader: pLoader,
+	pLoader: pLoader,
 });
 ```
 
@@ -102,11 +100,8 @@ To play a clip of a live stream or recording, request a clip manifest with a dur
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/manifest/clip.m3u8?time=600s&duration=30s
 ```
 
-
-
-* `time` string start time of the clip in seconds, from the start of the live stream or recording
-* `duration` string duration of the clip in seconds, up to 60 seconds max
-
+- `time` string start time of the clip in seconds, from the start of the live stream or recording
+- `duration` string duration of the clip in seconds, up to 60 seconds max
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -118,8 +113,6 @@ An MP4 of the clip can also be generated dynamically to be saved and shared on o
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/clip.mp4?time=600s&duration=30s&filename=clip.mp4
 ```
 
-
-
-* `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
-* `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
-* `filename` string *(optional)* a filename for the clip
+- `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
+- `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
+- `filename` string _(optional)_ a filename for the clip
diff --git a/src/content/docs/stream/stream-live/simulcasting.mdx b/src/content/docs/stream/stream-live/simulcasting.mdx
index e5f03f9003c3432..0f88a8a94fd31ff 100644
--- a/src/content/docs/stream/stream-live/simulcasting.mdx
+++ b/src/content/docs/stream/stream-live/simulcasting.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 5
 products:
   - stream
-
 ---
+
 import { DashButton } from "~/components";
 
 Simulcasting lets you forward your live stream to third-party platforms such as Twitch, YouTube, Facebook, Twitter, and more. You can simulcast to up to 50 concurrent destinations from each live input. To begin simulcasting, select an input and add one or more Outputs.
@@ -28,30 +28,32 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/live_inputs/<I
 
 ```json title="Response"
 {
-  "result": {
-    "uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
-    "url": "rtmp://a.rtmp.youtube.com/live2",
-    "streamKey": "<redacted>"
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
+		"url": "rtmp://a.rtmp.youtube.com/live2",
+		"streamKey": "<redacted>"
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 ## Control when you start and stop simulcasting
 
 You can enable and disable individual live outputs with either:
+
 - The **Live inputs** page of the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
+
 - [The API](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/update/)
 
 This allows you to:
 
-* Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
-* Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
-* Give your own users manual control over when they go live to specific simulcasting destinations.
+- Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
+- Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
+- Give your own users manual control over when they go live to specific simulcasting destinations.
 
 When a live output is disabled, video is not simulcast to the live output, even when actively streaming to the corresponding live input.
 
@@ -68,11 +70,11 @@ By default, all live outputs are enabled.
 
 ## Manage outputs
 
-| Command                                                                  | Method   | Endpoint                                                                 |
-| ------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------ |
-| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)      | `GET`    | `accounts/:account_identifier/stream/live_inputs`                        |
-| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/) | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier` |
-| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs` |
-| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/) | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
+| Command                                                                                                                                      | Method   | Endpoint                                                                                        |
+| -------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------- |
+| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)                                                                 | `GET`    | `accounts/:account_identifier/stream/live_inputs`                                               |
+| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/)                                                             | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier`                        |
+| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET`    | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs`                     |
+| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/)                                      | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
 
 If the associated live input is already retransmitting to this output when you make the `DELETE` request, that output will be disconnected within 30 seconds.
diff --git a/src/content/docs/stream/stream-live/start-stream-live.mdx b/src/content/docs/stream/stream-live/start-stream-live.mdx
index 0f114459ebb8755..7c32e2b8b669da8 100644
--- a/src/content/docs/stream/stream-live/start-stream-live.mdx
+++ b/src/content/docs/stream/stream-live/start-stream-live.mdx
@@ -22,6 +22,7 @@ After you subscribe to Stream, you can create Live Inputs in Dash or via the API
 ## Use the dashboard
 
 **Step 1:** In the Cloudflare dashboard, go to the **Live inputs** page and create a live input.
+
 <DashButton url="/?to=/:account/stream/inputs" />
 
 ![Create live input field from dashboard](~/assets/images/stream/create-live-input-from-stream-dashboard.png)
diff --git a/src/content/docs/stream/stream-live/troubleshooting.mdx b/src/content/docs/stream/stream-live/troubleshooting.mdx
index d82985f4c5dfeff..48973fe852b3b32 100644
--- a/src/content/docs/stream/stream-live/troubleshooting.mdx
+++ b/src/content/docs/stream/stream-live/troubleshooting.mdx
@@ -7,7 +7,8 @@ sidebar:
 products:
   - stream
 ---
-import {Details, DashButton } from "~/components"
+
+import { Details, DashButton } from "~/components";
 
 In addition to following the live stream troubleshooting steps in this guide, make sure that your video settings align with [Cloudflare live stream recommendations](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If you use OBS, you can also check these [OBS-specific recommendations](/stream/examples/obs-from-scratch/#6-optional-optimize-settings).
 
@@ -23,29 +24,37 @@ If your live stream is buffering, freezing, experiencing latency issues, or havi
 
 3. Look at your **Keyframe Interval** chart.
 
-	It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform.
-			* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
-
-	  	* If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
+   It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform. \* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
+   - If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
 
-	<Details header="What is a keyframe interval?">
-	The keyframe interval (also called GOP size) is a measurement of how often keyframes are sent to Stream. A shorter keyframe interval requires more Internet bandwidth on the broadcast side, but can reduce glass-to-glass latency. A longer keyframe requires less Internet bandwidth and can reduce buffering and freezing, but can increase glass-to-glass latency.
-	</Details>
+   <Details header="What is a keyframe interval?">
+   	The keyframe interval (also called GOP size) is a measurement of how often
+   	keyframes are sent to Stream. A shorter keyframe interval requires more
+   	Internet bandwidth on the broadcast side, but can reduce glass-to-glass
+   	latency. A longer keyframe requires less Internet bandwidth and can reduce
+   	buffering and freezing, but can increase glass-to-glass latency.
+   </Details>
 
-3. Look at your **Upload-to-Duration Ratio** chart.
+4. Look at your **Upload-to-Duration Ratio** chart.
 
-	It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
-    * [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
+   It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
+   - [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
 
-    * Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
-	   * If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
-	   * If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
+   - Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
+     - If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
+     - If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
 
-    * Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
+   - Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
 
-	<Details header="What is the upload-to-duration ratio?">
-	The upload-to-duration ratio is a measurement of how long it takes to upload a part of the stream compared to how long that part would take to play. A ratio of less than 100% means that the stream is uploading at least as fast as it would take to play, so most users should not experience buffering or freezing. A ratio of 100% or more means that your video is uploading slower than it would take to play, so it is likely that most users will experience buffering and freezing.
-	</Details>
+   <Details header="What is the upload-to-duration ratio?">
+   	The upload-to-duration ratio is a measurement of how long it takes to
+   	upload a part of the stream compared to how long that part would take to
+   	play. A ratio of less than 100% means that the stream is uploading at least
+   	as fast as it would take to play, so most users should not experience
+   	buffering or freezing. A ratio of 100% or more means that your video is
+   	uploading slower than it would take to play, so it is likely that most
+   	users will experience buffering and freezing.
+   </Details>
 
 ## Encoder failing to connect or keeps disconnecting
 
@@ -55,22 +64,22 @@ If your encoder shows a connection error such as "Failed to connect to server" o
 
 - Verify that the live input is enabled. A live input that is _disabled_ will reject all incoming connections. You can enable or disable a live input from the **Live inputs** page in the Dashboard or via the API using the `enabled` property.
 
-   <DashButton url="/?to=/:account/stream/inputs" />
+  <DashButton url="/?to=/:account/stream/inputs" />
 
-   ```bash
-   curl -X GET \
-   --header "Authorization: Bearer <API_TOKEN>" \
-   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
-   ```
+  ```bash
+  curl -X GET \
+  --header "Authorization: Bearer <API_TOKEN>" \
+  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
+  ```
 
-   If `enabled` is `false` in the response, update the live input to enable it:
+  If `enabled` is `false` in the response, update the live input to enable it:
 
-   ```bash
-   curl --request PUT \
-   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
-   --header "Authorization: Bearer <API_TOKEN>" \
-   --data '{"enabled": true}'
-   ```
+  ```bash
+  curl --request PUT \
+  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
+  --header "Authorization: Bearer <API_TOKEN>" \
+  --data '{"enabled": true}'
+  ```
 
 - If you use [Live Webhooks](/stream/stream-live/webhooks/), check for a `live_input.errored` event. The webhook payload includes an [error code](/stream/stream-live/webhooks/#error-codes) that can help you troubleshoot the specific cause.
 
@@ -84,4 +93,4 @@ If your encoder is connected and the dashboard shows a green **Connected** statu
 
 - Verify that your encoder is sending [AAC audio](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If it is not, set your encoder's settings to AAC explicitly.
 
-- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to *variable* or *automatic*, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
\ No newline at end of file
+- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to _variable_ or _automatic_, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
diff --git a/src/content/docs/stream/stream-live/webhooks.mdx b/src/content/docs/stream/stream-live/webhooks.mdx
index b80693318e6d6cb..2f298bf7ca81d9d 100644
--- a/src/content/docs/stream/stream-live/webhooks.mdx
+++ b/src/content/docs/stream/stream-live/webhooks.mdx
@@ -8,7 +8,7 @@ products:
   - stream
 ---
 
-import { AvailableNotifications,DashButton } from "~/components"
+import { AvailableNotifications, DashButton } from "~/components";
 
 Stream Live offers webhooks to notify your service when an Input connects, disconnects, or encounters an error with Stream Live.
 
@@ -40,15 +40,15 @@ Webhooks works differently for uploaded / on-demand videos. For more information
 
 ```json title="Example webhook payload"
 {
-  "name": "Live Webhook Test",
-  "text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
-  "data": {
-    "notification_name": "Stream Live Input",
-    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-    "event_type": "live_input.disconnected",
-    "updated_at": "2022-01-13T11:43:41.855717910Z"
-  },
-  "ts": 1642074233
+	"name": "Live Webhook Test",
+	"text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
+	"data": {
+		"notification_name": "Stream Live Input",
+		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+		"event_type": "live_input.disconnected",
+		"updated_at": "2022-01-13T11:43:41.855717910Z"
+	},
+	"ts": 1642074233
 }
 ```
 
@@ -58,30 +58,30 @@ If there are issues detected with the input, the `event_type` will be `live_inpu
 
 ## Error codes
 
-* `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
-* `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
-* `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
-* `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
-* `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
+- `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
+- `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
+- `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
+- `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
+- `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
 
 ```json title="Example live_input.errored webhook payload"
 {
-  "name": "Live Webhook Test",
-  "text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
-  "data": {
-    "notification_name": "Stream Live Input",
-    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-    "event_type": "live_input.errored",
-    "updated_at": "2024-07-09T18:07:51.077371662Z",
-    "live_input_errored": {
-      "error": {
-        "code": "ERR_GOP_OUT_OF_RANGE",
-        "message": "Input GOP size or keyframe interval is out of range."
-      },
-      "video_codec": "",
-      "audio_codec": ""
-    }
-  },
-  "ts": 1720548474,
+	"name": "Live Webhook Test",
+	"text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
+	"data": {
+		"notification_name": "Stream Live Input",
+		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+		"event_type": "live_input.errored",
+		"updated_at": "2024-07-09T18:07:51.077371662Z",
+		"live_input_errored": {
+			"error": {
+				"code": "ERR_GOP_OUT_OF_RANGE",
+				"message": "Input GOP size or keyframe interval is out of range."
+			},
+			"video_codec": "",
+			"audio_codec": ""
+		}
+	},
+	"ts": 1720548474
 }
 ```
diff --git a/src/content/docs/stream/transform-videos/bindings.mdx b/src/content/docs/stream/transform-videos/bindings.mdx
index 5e17fac1f2f59de..8d5cd162e0df120 100644
--- a/src/content/docs/stream/transform-videos/bindings.mdx
+++ b/src/content/docs/stream/transform-videos/bindings.mdx
@@ -13,7 +13,6 @@ products:
 
 import { WranglerConfig, InlineBadge } from "~/components";
 
-
 A [binding](/workers/runtime-apis/bindings/) connects your [Worker](/workers/) to external resources on the Developer Platform, like [Media Transformations](/stream/transform-videos/), [R2 buckets](/r2/buckets/), or [KV namespaces](/kv/concepts/kv-namespaces/).
 
 You can bind the Media Transformations API to your Worker to transform, resize, and extract content from videos without requiring them to be accessible through a URL.
@@ -155,8 +154,8 @@ export default {
 		const frame = await env.MEDIA.input(video.body)
 			.transform({ width: 720 })
 			.output({
-				mode: 'frame',
-				time: '3s',
+				mode: "frame",
+				time: "3s",
 			})
 			.response();
 
@@ -166,13 +165,10 @@ export default {
 			prompt: "Generate a caption for this image",
 			max_tokens: 512,
 		};
-		const response = await env.AI.run(
-			"@cf/unum/uform-gen2-qwen-500m",
-			payload
-		);
+		const response = await env.AI.run("@cf/unum/uform-gen2-qwen-500m", payload);
 		return new Response(JSON.stringify(response));
-	}
-}
+	},
+};
 ```
 
 ### Extract audio
@@ -214,28 +210,22 @@ export default {
 		const audio = await env.MEDIA.input(video.body)
 			.transform()
 			.output({
-				mode: 'audio',
-				})
+				mode: "audio",
+			})
 			.response();
 
 		// Prepare and run Workers AI inference
 		const payload = {
 			audio: [...new Uint8Array(await audio.arrayBuffer())],
 		};
-		const response = await env.AI.run(
-			"@cf/openai/whisper",
-			payload
-		);
+		const response = await env.AI.run("@cf/openai/whisper", payload);
 
 		// response will have props {text, word_count, vtt, words}
-		return new Response(
-			JSON.stringify(response, null, 2),
-			{
-				headers: {'Content-Type': 'application/json'}
-			}
-		);
-	}
-}
+		return new Response(JSON.stringify(response, null, 2), {
+			headers: { "Content-Type": "application/json" },
+		});
+	},
+};
 ```
 
 ### Store transformed output in R2
diff --git a/src/content/docs/stream/transform-videos/index.mdx b/src/content/docs/stream/transform-videos/index.mdx
index cd79ead8f896bd9..1d9dfe55c0bc0b1 100644
--- a/src/content/docs/stream/transform-videos/index.mdx
+++ b/src/content/docs/stream/transform-videos/index.mdx
@@ -7,17 +7,15 @@ sidebar:
 products:
   - stream
 ---
+
 import { DashButton } from "~/components";
 
 :::note[Media Transformations is now GA:]
 
-
 Billing for Media Transformations began on November 1st, 2025.
 
-
 :::
 
-
 You can optimize and manipulate videos stored _outside_ of Cloudflare Stream with Media Transformations. Transformed videos and images are served from one of your zones on Cloudflare.
 
 To transform a video or image, you must [enable transformations](/stream/transform-videos/#getting-started) for your zone. If your zone already has Image Transformations enabled, you can also optimize videos with Media Transformations.
diff --git a/src/content/docs/stream/uploading-videos/index.mdx b/src/content/docs/stream/uploading-videos/index.mdx
index 1e357b50c36f54c..8d01549e5d26ccf 100644
--- a/src/content/docs/stream/uploading-videos/index.mdx
+++ b/src/content/docs/stream/uploading-videos/index.mdx
@@ -12,17 +12,15 @@ Before you upload your video, review the options for uploading a video, supporte
 
 ## Upload options
 
-| Upload method	| When to use |
-|---------------|-------------|
-|[Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)| Upload videos from the Stream Dashboard without writing any code.
-|[Upload with a link](/stream/uploading-videos/upload-via-link/)| Upload videos using a link, such as an S3 bucket or content management system.
-|[Upload video file](/stream/uploading-videos/upload-video-file/)| Upload videos stored on a computer.
-|[Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/)| Allows end users of your website or app to upload videos directly to Cloudflare Stream.
-
+| Upload method                                                              | When to use                                                                             |
+| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
+| [Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)       | Upload videos from the Stream Dashboard without writing any code.                       |
+| [Upload with a link](/stream/uploading-videos/upload-via-link/)            | Upload videos using a link, such as an S3 bucket or content management system.          |
+| [Upload video file](/stream/uploading-videos/upload-video-file/)           | Upload videos stored on a computer.                                                     |
+| [Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/) | Allows end users of your website or app to upload videos directly to Cloudflare Stream. |
 
 ## Supported video formats
 
-
 :::note
 Files must be less than 30 GB, and content should be encoded and uploaded in the same frame rate it was recorded.
 :::
diff --git a/src/content/docs/stream/uploading-videos/player-api.mdx b/src/content/docs/stream/uploading-videos/player-api.mdx
index ba0c652f2710a62..afe17603c50c36e 100644
--- a/src/content/docs/stream/uploading-videos/player-api.mdx
+++ b/src/content/docs/stream/uploading-videos/player-api.mdx
@@ -22,103 +22,82 @@ Multiple attributes can be used together, added one after each other like this:
 
 ## Supported attributes
 
-* `autoplay` boolean
-
-  * Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
+- `autoplay` boolean
+  - Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
 
   :::note
   To disable video autoplay, the `autoplay` attribute needs to be removed altogether as this attribute. Setting `autoplay="false"` will not work; the video will autoplay if the attribute is there in the `<stream>` tag.
 
 In addition, some browsers now prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, see [new video policies for iOS](https://webkit.org/blog/6784/new-video-policies-for-ios/).
-  :::
-
-* `controls` boolean
-
-  * Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
-
-* `height` integer
-
-  * The height of the video's display area, in CSS pixels.
+:::
 
-* `loop` boolean
+- `controls` boolean
+  - Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
 
-  * A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
+- `height` integer
+  - The height of the video's display area, in CSS pixels.
 
-* `muted` boolean
+- `loop` boolean
+  - A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
 
-  * A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
+- `muted` boolean
+  - A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
 
-* `preload` string | null
-
-  * This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
+- `preload` string | null
+  - This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
 
   :::note
   The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
   :::
 
-* `poster` string
-
-  * A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
-
-* `src` string
+- `poster` string
+  - A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
 
-  * The video id from the video you've uploaded to Cloudflare Stream should be included here.
+- `src` string
+  - The video id from the video you've uploaded to Cloudflare Stream should be included here.
 
-* `width` integer
-
-  * The width of the video's display area, in CSS pixels.
+- `width` integer
+  - The width of the video's display area, in CSS pixels.
 
 ## Methods
 
-* `play()` Promise
-
-  * Start video playback.
-
-* `pause()` null
+- `play()` Promise
+  - Start video playback.
 
-  * Pause video playback.
+- `pause()` null
+  - Pause video playback.
 
 ## Properties
 
-* `autoplay`
+- `autoplay`
+  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
-  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+- `controls`
+  - Sets or returns whether the video should display controls (like play/pause etc.)
 
-* `controls`
+- `currentTime`
+  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-  * Sets or returns whether the video should display controls (like play/pause etc.)
+- `duration` readonly
+  - Returns the duration of the video in seconds.
 
-* `currentTime`
+- `ended` readonly
+  - Returns whether the video has ended.
 
-  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+- `loop`
+  - Sets or returns whether the video should start over when it reaches the end
 
-* `duration` readonly
+- `muted`
+  - Sets or returns whether the audio should be played with the video
 
-  * Returns the duration of the video in seconds.
+- `paused` readonly
+  - Returns whether the video is paused
 
-* `ended` readonly
+- `preload`
+  - Sets or returns whether the video should be preloaded upon element load.
 
-  * Returns whether the video has ended.
-
-* `loop`
-
-  * Sets or returns whether the video should start over when it reaches the end
-
-* `muted`
-
-  * Sets or returns whether the audio should be played with the video
-
-* `paused` readonly
-
-  * Returns whether the video is paused
-
-* `preload`
-
-  * Sets or returns whether the video should be preloaded upon element load.
-
-* `volume`
-
-  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+- `volume`
+  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -126,102 +105,78 @@ In addition, some browsers now prevent videos with audio from playing automatica
 
 Stream supports most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-* `abort`
-
-  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+- `abort`
+  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-* `canplay`
+- `canplay`
+  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-  * Sent when enough data is available that the media can be played, at least for a couple of frames.
+- `canplaythrough`
+  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-* `canplaythrough`
+- `durationchange`
+  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+- `ended`
+  - Sent when playback completes.
 
-* `durationchange`
+- `error`
+  - Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+- `loadeddata`
+  - The first frame of the media has finished loading.
 
-* `ended`
+- `loadedmetadata`
+  - The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
 
-  * Sent when playback completes.
+- `loadstart`
+  - Sent when loading of the media begins.
 
-* `error`
+- `pause`
+  - Sent when the playback state is changed to paused (paused property is true).
 
-  * Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+- `play`
+  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
 
-* `loadeddata`
+- `playing`
+  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
 
-  * The first frame of the media has finished loading.
+- `progress`
+  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
 
-* `loadedmetadata`
+- `ratechange`
+  - Sent when the playback speed changes.
 
-   * The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
+- `seeked`
+  - Sent when a seek operation completes.
 
-* `loadstart`
+- `seeking`
+  - Sent when a seek operation begins.
 
-  * Sent when loading of the media begins.
+- `stalled`
+  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
 
-* `pause`
+- `suspend`
+  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
 
-  * Sent when the playback state is changed to paused (paused property is true).
+- `timeupdate`
+  - The time indicated by the element's currentTime attribute has changed.
 
-* `play`
+- `volumechange`
+  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
-  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
-
-* `playing`
-
-  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
-
-* `progress`
-
-  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
-
-* `ratechange`
-
-  * Sent when the playback speed changes.
-
-* `seeked`
-
-  * Sent when a seek operation completes.
-
-* `seeking`
-
-  * Sent when a seek operation begins.
-
-* `stalled`
-
-  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
-
-* `suspend`
-
-  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
-
-* `timeupdate`
-
-  * The time indicated by the element's currentTime attribute has changed.
-
-* `volumechange`
-
-  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
-
-* `waiting`
-
-  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+- `waiting`
+  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-* `stream-adstart`
-
-  * Fires when `ad-url` attribute is present and the ad begins playback
-
-* `stream-adend`
-
-  * Fires when `ad-url` attribute is present and the ad finishes playback
+- `stream-adstart`
+  - Fires when `ad-url` attribute is present and the ad begins playback
 
-* `stream-adtimeout`
+- `stream-adend`
+  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-  * Fires when `ad-url` attribute is present and the ad took too long to load.
+- `stream-adtimeout`
+  - Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
index aff3f05547c7c42..44e7fb9660de859 100644
--- a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
+++ b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
@@ -176,27 +176,21 @@ The tus protocol allows you to add optional parameters in the [`Upload-Metadata`
 Setting arbitrary metadata values in the `Upload-Metadata` header sets values in the [meta key in Stream API](/api/resources/stream/methods/list/).
 
 - `name`
-
   - Setting this key will set `meta.name` in the API and display the value as the name of the video in the dashboard.
 
 - `requiresignedurls`
-
   - If this key is present, the video playback for this video will be required to use signed URLs after upload.
 
 - `scheduleddeletion`
-
   - Specifies a date and time when a video will be deleted. After a video is deleted, it is no longer viewable and no longer counts towards storage for billing. The specified date and time cannot be earlier than 30 days or later than 1,096 days from the video's created timestamp.
 
 - `allowedorigins`
-
   - An array of strings listing origins allowed to display the video. This will set the [allowed origins setting](/stream/viewing-videos/securing-your-stream/#security-considerations) for the video.
 
 - `thumbnailtimestamppct`
-
   - Specify the default thumbnail [timestamp percentage](/stream/viewing-videos/displaying-thumbnails/). Note that percentage is a floating point value between 0.0 and 1.0.
 
 - `watermark`
-
   - The watermark profile UID.
 
 ## Set creator property
diff --git a/src/content/docs/stream/uploading-videos/upload-via-link.mdx b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
index 1d7071ca08fb038..2b140c2dc1d2686 100644
--- a/src/content/docs/stream/uploading-videos/upload-via-link.mdx
+++ b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
@@ -8,11 +8,7 @@ products:
   - stream
 ---
 
-import {
-	Tabs,
-	TabItem,
-	LinkButton,
-} from "~/components"
+import { Tabs, TabItem, LinkButton } from "~/components";
 
 If you have videos stored in a cloud storage bucket, you can pass a HTTP link for the file, and Stream will fetch the file on your behalf.
 
@@ -108,45 +104,45 @@ You can optionally use [webhooks](/stream/manage-video-library/using-webhooks/)
 
 ```json {3,6}
 {
-  "result": {
-    "uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
-    "thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
-    "thumbnailTimestampPct": 0,
-    "readyToStream": false,
-    "status": {
-      "state": "downloading"
-    },
-    "meta": {
-      "downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
-      "name": "My First Stream Video"
-    },
-    "created": "2020-10-16T20:20:17.872170843Z",
-    "modified": "2020-10-16T20:20:17.872170843Z",
-    "size": 9032701,
-    "preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
-    "allowedOrigins": [],
-    "requireSignedURLs": false,
-    "uploaded": "2020-10-16T20:20:17.872170843Z",
-    "uploadExpiry": null,
-    "maxSizeBytes": 0,
-    "maxDurationSeconds": 0,
-    "duration": -1,
-    "input": {
-      "width": -1,
-      "height": -1
-    },
-    "playback": {
-      "hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
-      "dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
-    },
-    "watermark": null
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
+		"thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
+		"thumbnailTimestampPct": 0,
+		"readyToStream": false,
+		"status": {
+			"state": "downloading"
+		},
+		"meta": {
+			"downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
+			"name": "My First Stream Video"
+		},
+		"created": "2020-10-16T20:20:17.872170843Z",
+		"modified": "2020-10-16T20:20:17.872170843Z",
+		"size": 9032701,
+		"preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
+		"allowedOrigins": [],
+		"requireSignedURLs": false,
+		"uploaded": "2020-10-16T20:20:17.872170843Z",
+		"uploadExpiry": null,
+		"maxSizeBytes": 0,
+		"maxDurationSeconds": 0,
+		"duration": -1,
+		"input": {
+			"width": -1,
+			"height": -1
+		},
+		"playback": {
+			"hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+			"dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
+		},
+		"watermark": null
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
 After the video is uploaded, you can use the video `uid` shown in the example response above to play the video using the [Stream video player](/stream/viewing-videos/using-the-stream-player/).
 
-If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
\ No newline at end of file
+If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
diff --git a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
index cc8a1491f78e4b0..1aa988048c1fe40 100644
--- a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
+++ b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
@@ -10,10 +10,8 @@ products:
 
 :::note
 
-
 Stream thumbnails are not supported for videos with non-square pixels.
 
-
 :::
 
 ## Use Case 1: Generating a thumbnail on-the-fly
@@ -22,29 +20,32 @@ A thumbnail from your video can be generated using a special link where you spec
 
 `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270`
 
-<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270" alt="Example of thumbnail image generated from example video" />
+<img
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270"
+	alt="Example of thumbnail image generated from example video"
+/>
 
 Using the `poster` query parameter in the embed URL, you can set a thumbnail to any time in your video. If [signed URLs](/stream/viewing-videos/securing-your-stream/) are required, you must use a signed URL instead of video UIDs.
 
 ```html
 <iframe
-  src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-  style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-  allowfullscreen="true"
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+	style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+	allowfullscreen="true"
 ></iframe>
 ```
 
 Supported URL attributes are:
 
-* **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
-* **`height`** (default `640`)
-* **`width`** (default `640`)
-* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  * **`crop`** cut parts of the video that doesn't fit in the given size
-  * **`clip`** preserve the entire frame and decrease the size of the image within given size
-  * **`scale`** distort the image to fit the given size
-  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+- **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
+- **`height`** (default `640`)
+- **`width`** (default `640`)
+- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  - **`crop`** cut parts of the video that doesn't fit in the given size
+  - **`clip`** preserve the entire frame and decrease the size of the image within given size
+  - **`scale`** distort the image to fit the given size
+  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
 
 ## Use Case 2: Set the default thumbnail timestamp using the API
 
@@ -67,17 +68,20 @@ Stream supports animated GIFs as thumbnails. Viewing animated thumbnails does no
 
 ` https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s`
 
-<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s" alt="Animated gif example, generated on-demand from Cloudflare Stream" />
+<img
+	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s"
+	alt="Animated gif example, generated on-demand from Cloudflare Stream"
+/>
 
 Supported URL attributes for animated thumbnails are:
 
-* **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
-* **`height`** (default `640`)
-* **`width`** (default `640`)
-* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  * **`crop`** cut parts of the video that doesn't fit in the given size
-  * **`clip`** preserve the entire frame and decrease the size of the image within given size
-  * **`scale`** distort the image to fit the given size
-  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
-* **`duration`** (default `5s`)
-* **`fps`** (default `8`)
+- **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
+- **`height`** (default `640`)
+- **`width`** (default `640`)
+- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  - **`crop`** cut parts of the video that doesn't fit in the given size
+  - **`clip`** preserve the entire frame and decrease the size of the image within given size
+  - **`scale`** distort the image to fit the given size
+  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+- **`duration`** (default `5s`)
+- **`fps`** (default `8`)
diff --git a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
index 0ae5a7967717599..979b5f8d99e2f35 100644
--- a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
+++ b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
@@ -15,134 +15,103 @@ To use this SDK, add an additional `<script>` tag to your website:
 ```html
 <!-- You can use styles and CSS on this iframe element where the video player will appear -->
 <iframe
-  src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
-  style="border: none"
-  height="720"
-  width="1280"
-  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-  allowfullscreen="true"
-  id="stream-player"
+	src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
+	style="border: none"
+	height="720"
+	width="1280"
+	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+	allowfullscreen="true"
+	id="stream-player"
 ></iframe>
 
 <script src="https://embed.cloudflarestream.com/embed/sdk.latest.js"></script>
 
 <!-- Your JavaScript code below-->
 <script>
-  const player = Stream(document.getElementById('stream-player'));
-  player.addEventListener('play', () => {
-    console.log('playing!');
-  });
-  player.play().catch(() => {
-    console.log('playback failed, muting to try again');
-    player.muted = true;
-    player.play();
-  });
+	const player = Stream(document.getElementById("stream-player"));
+	player.addEventListener("play", () => {
+		console.log("playing!");
+	});
+	player.play().catch(() => {
+		console.log("playback failed, muting to try again");
+		player.muted = true;
+		player.play();
+	});
 </script>
 ```
 
 ## Methods
 
+- `play()` Promise
+  - Start video playback.
 
-
-* `play()` Promise
-
-  * Start video playback.
-
-* `pause()` null
-
-  * Pause video playback.
-
-
+- `pause()` null
+  - Pause video playback.
 
 ## Properties
 
-
-
-* `autoplay` boolean
-
-  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+- `autoplay` boolean
+  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
 :::note
 
-
 Some browsers prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, review the [iOS video policies](https://webkit.org/blog/6784/new-video-policies-for-ios/).
 
-
 :::
 
-* `buffered` TimeRanges readonly
-
-  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+- `buffered` TimeRanges readonly
+  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-* `controls` boolean
+- `controls` boolean
+  - Sets or returns whether the video should display controls (like play/pause etc.)
 
-  * Sets or returns whether the video should display controls (like play/pause etc.)
+- `currentTime` integer
+  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-* `currentTime` integer
-
-  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
-
-* `defaultTextTrack`
-
-  * Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
+- `defaultTextTrack`
+  - Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
 
 :::note
 
-
-This will *only* work once during initialization. Beyond that point the user has full control over their text track settings.
-
+This will _only_ work once during initialization. Beyond that point the user has full control over their text track settings.
 
 :::
 
-* `duration` integer readonly
-
-  * Returns the duration of the video in seconds.
-
-* `ended` boolean readonly
-
-  * Returns whether the video has ended.
-
-* `letterboxColor` string
-
-  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
-
-* `loop` boolean
-
-  * Sets or returns whether the video should start over when it reaches the end
+- `duration` integer readonly
+  - Returns the duration of the video in seconds.
 
-* `muted` boolean
+- `ended` boolean readonly
+  - Returns whether the video has ended.
 
-  * Sets or returns whether the audio should be played with the video
+- `letterboxColor` string
+  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
 
-* `paused` boolean readonly
+- `loop` boolean
+  - Sets or returns whether the video should start over when it reaches the end
 
-  * Returns whether the video is paused
+- `muted` boolean
+  - Sets or returns whether the audio should be played with the video
 
-* `played` TimeRanges readonly
+- `paused` boolean readonly
+  - Returns whether the video is paused
 
-  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+- `played` TimeRanges readonly
+  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-* `preload` boolean
-
-  * Sets or returns whether the video should be preloaded upon element load.
+- `preload` boolean
+  - Sets or returns whether the video should be preloaded upon element load.
 
 :::note
 
-
 The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
 
-
 :::
 
-* `primaryColor` string
-
-  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
-
-* `volume` float
-
-  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
-
+- `primaryColor` string
+  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
 
+- `volume` float
+  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -150,109 +119,78 @@ The `<video>` element does not force the browser to follow the value of this att
 
 We support most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
+- `abort`
+  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
+- `canplay`
+  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-* `abort`
+- `canplaythrough`
+  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+- `durationchange`
+  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-* `canplay`
+- `ended`
+  - Sent when playback completes.
 
-  * Sent when enough data is available that the media can be played, at least for a couple of frames.
+- `error`
+  - Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-* `canplaythrough`
+- `loadeddata`
+  - The first frame of the media has finished loading.
 
-  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+- `loadedmetadata`
+  - The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
 
-* `durationchange`
+- `loadstart`
+  - Sent when loading of the media begins.
 
-  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+- `pause`
+  - Sent when the playback state is changed to paused (paused property is true).
 
-* `ended`
+- `play`
+  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
 
-  * Sent when playback completes.
+- `playing`
+  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
 
-* `error`
+- `progress`
+  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
 
-  * Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+- `ratechange`
+  - Sent when the playback speed changes.
 
-* `loadeddata`
+- `seeked`
+  - Sent when a seek operation completes.
 
-  * The first frame of the media has finished loading.
+- `seeking`
+  - Sent when a seek operation begins.
 
-* `loadedmetadata`
+- `stalled`
+  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
 
-  * The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
+- `suspend`
+  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
 
-* `loadstart`
-
-  * Sent when loading of the media begins.
-
-* `pause`
-
-  * Sent when the playback state is changed to paused (paused property is true).
-
-* `play`
-
-  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
-
-* `playing`
-
-  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
-
-* `progress`
-
-  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
-
-* `ratechange`
-
-  * Sent when the playback speed changes.
-
-* `seeked`
-
-  * Sent when a seek operation completes.
-
-* `seeking`
-
-  * Sent when a seek operation begins.
-
-* `stalled`
-
-  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
-
-* `suspend`
-
-  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
-
-* `timeupdate`
-
-  * The time indicated by the element's currentTime attribute has changed.
-
-* `volumechange`
-
-  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
-
-* `waiting`
-
-  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+- `timeupdate`
+  - The time indicated by the element's currentTime attribute has changed.
 
+- `volumechange`
+  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
+- `waiting`
+  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard Events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
+- `stream-adstart`
+  - Fires when `ad-url` attribute is present and the ad begins playback
 
+- `stream-adend`
+  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-* `stream-adstart`
-
-  * Fires when `ad-url` attribute is present and the ad begins playback
-
-* `stream-adend`
-
-  * Fires when `ad-url` attribute is present and the ad finishes playback
-
-* `stream-adtimeout`
-
-  * Fires when `ad-url` attribute is present and the ad took too long to load.
-
+- `stream-adtimeout`
+  - Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
index 4d5dded596a44eb..e65a1289cbbf95e 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
@@ -14,7 +14,7 @@ The purpose of Deprecated API content is to communicate that Cloudflare no longe
 
 instructional, straightforward
 
-## content\_type
+## content_type
 
 `reference`
 
@@ -24,7 +24,7 @@ instructional, straightforward
 
 **Deprecated endpoint name**: Must match what existed in the non-deprecated [Endpoint](/style-guide/api-content-strategy/api-content-types/endpoints/).
 
-**Context**:  Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
+**Context**: Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
 
 **Replacement**: A description of and/or link to the alternative endpoint OR an explanation as to why Cloudflare is removing the capability of that endpoint.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
index f73e8c33466bbfe..6529edfc70b1ed6 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
@@ -18,21 +18,19 @@ An endpoint is used to make HTTPS requests, and the `GET`, `POST`, `PUT`, `PATCH
 
 :::note
 
-
 The required components apply to newly created endpoints. Existing endpoints will **not** be modified.
 
-
 :::
 
 **Title**: Title of the endpoint using sentence casing (first word capitalized). The titles do not use punctuation marks at the end of the title. Simple cases usually take one of the following forms:
 
 Endpoints that act on/return a single item: verb + indefinite article + singular resource name.
 
-* Example: Get a list item
+- Example: Get a list item
 
 Endpoints that act on/return a collection of items: verb + plural resource name.
 
-* Example: Get list items
+- Example: Get list items
 
 **Description**: Describes what the endpoint does or how it should be used. Use punctuation at the end of the description.
 
@@ -54,11 +52,11 @@ When writing the titles and descriptions, keep our voice and tone in mind. Be co
 
 Below are some examples of endpoint titles and descriptions for reference:
 
-* **Get domain**: Fetches a single domain.
-* **List workers**: Fetches a list of uploaded workers.
-* **List pools**: Lists configured pools.
-* **Create waiting room**: Creates a new waiting room.
-* **Update health check**: Updates configured health checks.
+- **Get domain**: Fetches a single domain.
+- **List workers**: Fetches a list of uploaded workers.
+- **List pools**: Lists configured pools.
+- **Create waiting room**: Creates a new waiting room.
+- **Update health check**: Updates configured health checks.
 
 ## Example
 
@@ -70,4 +68,4 @@ Below are some examples of endpoint titles and descriptions for reference:
 
 **Method**: `GET`
 
-**Endpoint**: user/audit\_logs
+**Endpoint**: user/audit_logs
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
index 5b998bffe2e51f0..59e3387e3c346d0 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
index a31e895ce8f45c1..aebb7c2e49d8230 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
@@ -46,7 +46,7 @@ Below are some examples of parameter descriptions for reference:
 
 **version**: The Cloudflare One Client version.
 
-**per\_page**: Sets the maximum number of requested results.
+**per_page**: Sets the maximum number of requested results.
 
 **enabled**: Enables or disable a load balancer.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
index 26a17b8a4f34fc5..c24e2857250568e 100644
--- a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
@@ -21,9 +21,9 @@ To automatically incorporate our conventions into your examples, use:
 
 Use long parameter names for clarity:
 
-* `--header` (instead of `-H`)
-* `--request` (when needed, instead of `-X`)
-* `--data` (instead of `-d`)
+- `--header` (instead of `-H`)
+- `--request` (when needed, instead of `-X`)
+- `--data` (instead of `-d`)
 
 You do not need to use the `--url` parameter since it is the main cURL parameter. Also, the URL does not need to be enclosed in double quotes (`""`), except if it contains a `?` character (that is, when it includes a query string).
 
@@ -45,9 +45,9 @@ If you must suggest the use of this tool, you can add a link to the [Make API ca
 
 ### Preliminary notes
 
-* Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
-* Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
-* Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
+- Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
+- Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
+- Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
 
 The same placeholder name should correspond to the same value – use different placeholder names for different ID values. You can use the same request placeholders in the response, if they should match the values in the request.
 
@@ -149,7 +149,7 @@ Enclose the JSON payload ( the `--data` command-line argument) in single quotes
 
 The recommended way of escaping a single quote inside the body is the following (assuming the user will run the command in a bash-like terminal):
 
-* Replace the single quote `'` with `'\''`
+- Replace the single quote `'` with `'\''`
 
 Which means "close string, add escaped single quote, begin string again".
 
@@ -203,28 +203,28 @@ A response starts either with an object (`{ ... }`) or a list (`[ ... ]`). The i
 (}|])
 ```
 
-* If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
-* Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
+- If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
+- Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
 
 ### Full response example
 
 ```json
 {
-  "result": {
-    "id": "<RULE_ID>",
-    "paused": false,
-    "description": "do not challenge login from office",
-    "action": "allow",
-    "priority": null,
-    "filter": {
-      "id": "<FILTER_ID>",
-      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-      "paused": false,
-      "description": "Login from office"
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "<RULE_ID>",
+		"paused": false,
+		"description": "do not challenge login from office",
+		"action": "allow",
+		"priority": null,
+		"filter": {
+			"id": "<FILTER_ID>",
+			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+			"paused": false,
+			"description": "Login from office"
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
diff --git a/src/content/docs/style-guide/components/anchor-heading.mdx b/src/content/docs/style-guide/components/anchor-heading.mdx
index 22d6bd5d8b60e19..3a3195eb29ef0a3 100644
--- a/src/content/docs/style-guide/components/anchor-heading.mdx
+++ b/src/content/docs/style-guide/components/anchor-heading.mdx
@@ -17,7 +17,11 @@ The `AnchorHeading` component defines headings. Specifically, `AnchorHeading` pe
 ```mdx live
 import { AnchorHeading } from "~/components";
 
-<AnchorHeading title="How to use AnchorHeading" slug="use-anchorheading" depth={2} />
+<AnchorHeading
+	title="How to use AnchorHeading"
+	slug="use-anchorheading"
+	depth={2}
+/>
 ```
 
 Markdown files (including partials) have this behavior by default, applied via rehype plugins. Therefore, the `AnchorHeading` component is usually only required when writing headings yourself inside components, or when working on non-markdown files.
@@ -25,7 +29,8 @@ Markdown files (including partials) have this behavior by default, applied via r
 To override the ID given to a heading within Markdown, add an MDX comment at the end of the line:
 
 ```mdx live
-## foo {/*bar*/}
+## foo {/* bar */}
+
 {/* HTML: <h2 id="bar">foo</h2> */}
 ```
 
@@ -33,4 +38,4 @@ To override the ID given to a heading within Markdown, add an MDX comment at the
 
 The `AnchorHeading` component emulates the behavior of the [`rehype-slug`](https://github.com/rehypejs/rehype-slug) and the [`rehype-autolink-headings`](https://github.com/rehypejs/rehype-autolink-headings). It adds an `id` based on the output of [`github-slugger`](https://github.com/Flet/github-slugger/) to the heading, as well as adding a button to copy a link to that particular heading.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/style-guide/components/available-notifications.mdx b/src/content/docs/style-guide/components/available-notifications.mdx
index 52d9d0e9f2ec6d7..ef0ad606272bc27 100644
--- a/src/content/docs/style-guide/components/available-notifications.mdx
+++ b/src/content/docs/style-guide/components/available-notifications.mdx
@@ -14,14 +14,19 @@ import { AvailableNotifications } from "~/components";
 
 <AvailableNotifications product="Traffic Monitoring" />
 <AvailableNotifications
-    product="dns"
-    notificationFilter="Secondary DNS all Primaries Failing"
+	product="dns"
+	notificationFilter="Secondary DNS all Primaries Failing"
 />
 ```
 
 ## Notifications
 
-import { Code } from "~/components"
-import glossary from "~/content/notifications/index.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/notifications/index.yaml?raw";
 
-<Code title="/src/content/notifications/index.yaml" code={glossary} lang="yaml" wrap={true} />
\ No newline at end of file
+<Code
+	title="/src/content/notifications/index.yaml"
+	code={glossary}
+	lang="yaml"
+	wrap={true}
+/>
diff --git a/src/content/docs/style-guide/components/description.mdx b/src/content/docs/style-guide/components/description.mdx
index 4d91bb6f10f8f27..75456e07bf8c711 100644
--- a/src/content/docs/style-guide/components/description.mdx
+++ b/src/content/docs/style-guide/components/description.mdx
@@ -8,9 +8,7 @@ products:
 ---
 
 ```mdx live
-import { Description } from "~/components"
+import { Description } from "~/components";
 
-<Description>
-    Hello, world!
-</Description>
-```
\ No newline at end of file
+<Description>Hello, world!</Description>
+```
diff --git a/src/content/docs/style-guide/components/example.mdx b/src/content/docs/style-guide/components/example.mdx
index eb0ba2069a80284..2d3de76617e19e9 100644
--- a/src/content/docs/style-guide/components/example.mdx
+++ b/src/content/docs/style-guide/components/example.mdx
@@ -10,17 +10,13 @@ products:
 Use the `<Example>` component to add a box around some content. This can be useful when you want to demonstrate or showcase something without it being confused by the surrounding text.
 
 ```mdx live
-import { Example } from "~/components"
+import { Example } from "~/components";
 
-<Example>
-    Hello, world!
-</Example>
+<Example>Hello, world!</Example>
 
-{/*
-    `title` is an optional string which customizes the title of your example card
-*/}
+{/_
+`title` is an optional string which customizes the title of your example card
+_/}
 
-<Example title="Hello world">
-    Hello, world!
-</Example>
-```
\ No newline at end of file
+<Example title="Hello world">Hello, world!</Example>
+```
diff --git a/src/content/docs/style-guide/components/feature-table.mdx b/src/content/docs/style-guide/components/feature-table.mdx
index 7018dd906b70056..c839be1febca17e 100644
--- a/src/content/docs/style-guide/components/feature-table.mdx
+++ b/src/content/docs/style-guide/components/feature-table.mdx
@@ -14,7 +14,7 @@ If the feature information includes an `Availability` row and you would like to
 This component pulls information from the `index.json` file in `src/content/plans/`.
 
 ```mdx live
-import { FeatureTable } from "~/components"
+import { FeatureTable } from "~/components";
 
 <FeatureTable id="analytics.logpush" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/feature.mdx b/src/content/docs/style-guide/components/feature.mdx
index ce6073fbff74c41..1b795ccb977fbf1 100644
--- a/src/content/docs/style-guide/components/feature.mdx
+++ b/src/content/docs/style-guide/components/feature.mdx
@@ -12,15 +12,15 @@ The `<Feature>` component lists features available in the product and provides a
 The header parameter supplies the feature name and the href parameter supplies the link to the feature. Text wrapped in the component supplies the description.
 
 ```mdx
-import { Feature } from "~/components"
+import { Feature } from "~/components";
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-   Hello, world!
+	Hello, world!
 </Feature>
 ```
 
-import { Feature } from "~/components"
+import { Feature } from "~/components";
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-   Hello, world!
+	Hello, world!
 </Feature>
diff --git a/src/content/docs/style-guide/components/glossary-definition.mdx b/src/content/docs/style-guide/components/glossary-definition.mdx
index 379a96198932f4f..7a95c0d7c2a7584 100644
--- a/src/content/docs/style-guide/components/glossary-definition.mdx
+++ b/src/content/docs/style-guide/components/glossary-definition.mdx
@@ -12,14 +12,18 @@ Use the this component to add extra information to an existing glossary entry. `
 ## Component
 
 ```mdx live
-import { GlossaryDefinition } from "~/components"
+import { GlossaryDefinition } from "~/components";
 
 <GlossaryDefinition term="example" prepend="The definition for example is: " />
 ```
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
 
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/glossary-tooltip.mdx b/src/content/docs/style-guide/components/glossary-tooltip.mdx
index 0efadd82370ed12..8f0e06da3c09d3d 100644
--- a/src/content/docs/style-guide/components/glossary-tooltip.mdx
+++ b/src/content/docs/style-guide/components/glossary-tooltip.mdx
@@ -22,7 +22,11 @@ import { GlossaryTooltip } from "~/components"
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
-
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
+
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/glossary.mdx b/src/content/docs/style-guide/components/glossary.mdx
index 1bf06744eadfba7..df05ad6c06dab82 100644
--- a/src/content/docs/style-guide/components/glossary.mdx
+++ b/src/content/docs/style-guide/components/glossary.mdx
@@ -14,14 +14,18 @@ Create the glossary entries in a file dedicated to your product. These YAML file
 ## Component
 
 ```mdx live
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 <Glossary />
 ```
 
 ## Glossary
 
-import { Code } from "~/components"
-import glossary from "~/content/glossary/style-guide.yaml?raw"
+import { Code } from "~/components";
+import glossary from "~/content/glossary/style-guide.yaml?raw";
 
-<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
+<Code
+	title="/src/content/glossary/style-guide.yaml"
+	code={glossary}
+	lang="yaml"
+/>
diff --git a/src/content/docs/style-guide/components/inline-badge.mdx b/src/content/docs/style-guide/components/inline-badge.mdx
index b0c325af0bf4068..6e49dc901618e2c 100644
--- a/src/content/docs/style-guide/components/inline-badge.mdx
+++ b/src/content/docs/style-guide/components/inline-badge.mdx
@@ -12,17 +12,18 @@ products:
 Our current recommendation is to avoid inline badges, since they may hurt readability.
 
 Guidelines:
+
 - Mention beta/alpha/early access in the feature's main documentation page (use the [`<Badge>`](/style-guide/components/badges/) component for this purpose).
 - If an additional reference is needed in the middle of the text, use "(beta)", with no special formatting, after the feature name.
 - For instructions related to the feature (such as instructions on turning the feature on or off), you may mention again it's in beta, and also include "(beta)" in the side nav.
-:::
+  :::
 
 ## Component
 
 To adopt this styling in a React component, apply the `sl-badge` class to a `span` element.
 
 ```mdx live
-import { InlineBadge } from '~/components';
+import { InlineBadge } from "~/components";
 
 ### Alpha <InlineBadge preset="alpha" />
 
@@ -44,24 +45,24 @@ Either `preset` or `text` and `variant` must be specified.
 ### Presets
 
 - `alpha`
-    - **Text**: `Alpha`
-    - **Variant** `success`
+  - **Text**: `Alpha`
+  - **Variant** `success`
 
 - `beta`
-    - **Text**: `Beta`
-    - **Variant** `caution`
+  - **Text**: `Beta`
+  - **Variant** `caution`
 
 - `deprecated`
-    - **Text**: `Deprecated`
-    - **Variant** `danger`
+  - **Text**: `Deprecated`
+  - **Variant** `danger`
 
 - `early-access`
-    - **Text**: `Early Access`
-    - **Variant** `note`
+  - **Text**: `Early Access`
+  - **Variant** `note`
 
 - `legacy`
-    - **Text**: `Legacy`
-    - **Variant** `danger`
+  - **Text**: `Legacy`
+  - **Variant** `danger`
 
 ### Text
 
@@ -70,16 +71,16 @@ Any string.
 ### Variant
 
 - `note`
-    - **Color**: Blue
+  - **Color**: Blue
 
 - `tip`
-    - **Color**: Purple
+  - **Color**: Purple
 
 - `danger`
-    - **Color**: Red
+  - **Color**: Red
 
 - `caution`
-    - **Color**: Orange
+  - **Color**: Orange
 
 - `success`
-    - **Color**: Green
\ No newline at end of file
+  - **Color**: Green
diff --git a/src/content/docs/style-guide/components/link-cards.mdx b/src/content/docs/style-guide/components/link-cards.mdx
index da6aaeafc9831a0..0adc8e6059e72d6 100644
--- a/src/content/docs/style-guide/components/link-cards.mdx
+++ b/src/content/docs/style-guide/components/link-cards.mdx
@@ -8,21 +8,21 @@ products:
 ---
 
 ```mdx live wrap
-import { CardGrid, LinkCard } from "~/components"
+import { CardGrid, LinkCard } from "~/components";
 
 <LinkCard
-    title="foo"
-    description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-    href="/style-guide/components/link-cards/"
+	title="foo"
+	description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+	href="/style-guide/components/link-cards/"
 />
 
 <CardGrid>
-{[...Array(4).keys()].map(() => (
-    <LinkCard
-        title="foo"
-        description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-        href="/style-guide/components/link-cards/"
-    />
-))}
+	{[...Array(4).keys()].map(() => (
+		<LinkCard
+			title="foo"
+			description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+			href="/style-guide/components/link-cards/"
+		/>
+	))}
 </CardGrid>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/list-tutorials.mdx b/src/content/docs/style-guide/components/list-tutorials.mdx
index c225a6b23e4a78c..c67b80ab5057fa1 100644
--- a/src/content/docs/style-guide/components/list-tutorials.mdx
+++ b/src/content/docs/style-guide/components/list-tutorials.mdx
@@ -15,4 +15,4 @@ import { ListTutorials } from "~/components";
 
 ## Associated content types
 
-- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
\ No newline at end of file
+- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
diff --git a/src/content/docs/style-guide/components/package-managers.mdx b/src/content/docs/style-guide/components/package-managers.mdx
index 7b9c3137bd4b3b3..4c5f8298b9152d9 100644
--- a/src/content/docs/style-guide/components/package-managers.mdx
+++ b/src/content/docs/style-guide/components/package-managers.mdx
@@ -10,7 +10,7 @@ products:
 This component is provided by the [`starlight-package-managers` package.](https://github.com/HiDeoo/starlight-package-managers)
 
 ```mdx live
-import { PackageManagers } from "~/components"
+import { PackageManagers } from "~/components";
 
 <PackageManagers pkg="wrangler" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/pages-build-preset.mdx b/src/content/docs/style-guide/components/pages-build-preset.mdx
index 976dc1433f725e5..3480c8339307db2 100644
--- a/src/content/docs/style-guide/components/pages-build-preset.mdx
+++ b/src/content/docs/style-guide/components/pages-build-preset.mdx
@@ -8,8 +8,8 @@ products:
 ---
 
 ```mdx live
-import { PagesBuildPreset } from "~/components"
+import { PagesBuildPreset } from "~/components";
 
 <PagesBuildPreset framework="gatsby" />
 <PagesBuildPreset framework="next-js" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/plan.mdx b/src/content/docs/style-guide/components/plan.mdx
index 07b591b1274a686..1b1457fa37ceb98 100644
--- a/src/content/docs/style-guide/components/plan.mdx
+++ b/src/content/docs/style-guide/components/plan.mdx
@@ -14,9 +14,8 @@ To specify a special feature use `<Plan id="<FIRST_PRODUCT>.<SECOND-PRODUCT>.pro
 
 Refer to the examples below for more information.
 
-
 ```mdx live
-import { Plan } from "~/components"
+import { Plan } from "~/components";
 
 <Plan type="all" />
 <Plan type="paid" />
@@ -27,4 +26,4 @@ import { Plan } from "~/components"
 <Plan type="workers-all" />
 <Plan type="workers-paid" />
 <Plan id="web3.ethereum.properties.availability.summary" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/product-availability-text.mdx b/src/content/docs/style-guide/components/product-availability-text.mdx
index 83689f8bbba4207..77e2bca0cf78b1d 100644
--- a/src/content/docs/style-guide/components/product-availability-text.mdx
+++ b/src/content/docs/style-guide/components/product-availability-text.mdx
@@ -19,10 +19,10 @@ Cloud Connector <ProductAvailabilityText product="cloud-connector" /> allows you
 
 ## Props
 
-| Prop | Type | Required | Default | Description |
-| --- | --- | --- | --- | --- |
-| `product` | `string` | Yes | — | Product slug matching a file in `src/content/directory/`. |
-| `parentheses` | `string` | No | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
+| Prop          | Type     | Required | Default  | Description                                                                                                |
+| ------------- | -------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------- |
+| `product`     | `string` | Yes      | —        | Product slug matching a file in `src/content/directory/`.                                                  |
+| `parentheses` | `string` | No       | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
 
 ## Behavior
 
diff --git a/src/content/docs/style-guide/components/product-features.mdx b/src/content/docs/style-guide/components/product-features.mdx
index 199e0ded2498a76..bea56b72ab74c5e 100644
--- a/src/content/docs/style-guide/components/product-features.mdx
+++ b/src/content/docs/style-guide/components/product-features.mdx
@@ -10,6 +10,7 @@ products:
 Use when you need to list all available features within a product grouping inside of the `index.json` file in `src/content/plans/`. For the id property, specify the product object you want to use.
 
 ```mdx live
-import { ProductFeatures } from "~/components"
+import { ProductFeatures } from "~/components";
 
-<ProductFeatures id="dns" />
\ No newline at end of file
+<ProductFeatures id="dns" />
+```
diff --git a/src/content/docs/style-guide/components/related-product.mdx b/src/content/docs/style-guide/components/related-product.mdx
index 8de8d8c11cdca07..99c45329075a2a1 100644
--- a/src/content/docs/style-guide/components/related-product.mdx
+++ b/src/content/docs/style-guide/components/related-product.mdx
@@ -17,10 +17,11 @@ Use in Overview pages.
 import { RelatedProduct } from "~/components";
 
 <RelatedProduct header="R2" href="/r2/" product="r2">
-    Store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.
+	Store large amounts of unstructured data without the costly egress bandwidth
+	fees associated with typical cloud storage services.
 </RelatedProduct>
 
 <RelatedProduct header="Images" href="/images/" product="images">
-    A suite of products tailored to your image-processing needs.
+	A suite of products tailored to your image-processing needs.
 </RelatedProduct>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/rule-id.mdx b/src/content/docs/style-guide/components/rule-id.mdx
index d2a33c41ef0ebd7..f5b213de131b2bc 100644
--- a/src/content/docs/style-guide/components/rule-id.mdx
+++ b/src/content/docs/style-guide/components/rule-id.mdx
@@ -8,7 +8,7 @@ products:
 ---
 
 ```mdx live
-import { RuleID } from "~/components"
+import { RuleID } from "~/components";
 
 <RuleID id="abcdefghijklmnopqrstuvwxyz" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/steps.mdx b/src/content/docs/style-guide/components/steps.mdx
index 26b09c984dee440..a8ad45e2b122573 100644
--- a/src/content/docs/style-guide/components/steps.mdx
+++ b/src/content/docs/style-guide/components/steps.mdx
@@ -15,4 +15,4 @@ import { Steps } from "~/components"
 2. Wrap your numbered list in the `Steps` components
 3. Done!
 </Steps>
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
index 824d45bb57c3001..7208cf19466a58c 100644
--- a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
+++ b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
@@ -40,7 +40,7 @@ An optional object containing `base` (`string`) and `subtract` (`string[]`) prop
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
 	}}
 />
 
@@ -51,7 +51,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
 	}}
 />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/type-highlighting.mdx b/src/content/docs/style-guide/components/type-highlighting.mdx
index a95852acfc7dc55..26f7c06002aa2bb 100644
--- a/src/content/docs/style-guide/components/type-highlighting.mdx
+++ b/src/content/docs/style-guide/components/type-highlighting.mdx
@@ -32,4 +32,4 @@ import { Type, MetaInfo } from "~/components";
   - The name of your service.
 - `local` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
   - If the service should run locally or not.
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/components/usage.mdx b/src/content/docs/style-guide/components/usage.mdx
index 337c49995287617..b1548e52b571c45 100644
--- a/src/content/docs/style-guide/components/usage.mdx
+++ b/src/content/docs/style-guide/components/usage.mdx
@@ -11,4 +11,4 @@ import { ComponentsUsage } from "~/components";
 
 This page contains a breakdown of each component and the pages where they are used.
 
-<ComponentsUsage />
\ No newline at end of file
+<ComponentsUsage />
diff --git a/src/content/docs/style-guide/components/wrangler-namespace.mdx b/src/content/docs/style-guide/components/wrangler-namespace.mdx
index fab2bbf305de528..6ebac49e56a3019 100644
--- a/src/content/docs/style-guide/components/wrangler-namespace.mdx
+++ b/src/content/docs/style-guide/components/wrangler-namespace.mdx
@@ -32,4 +32,4 @@ import { WranglerNamespace } from "~/components";
 - `namespace` <Type text="string" /> <MetaInfo text="required" />
   - The namespace to pull the related commands from (`d1`, `hyperdrive`).
 - `headingLevel` <Type text="boolean" /> <MetaInfo text="(default: 2) optional" />
-  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
\ No newline at end of file
+  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
diff --git a/src/content/docs/style-guide/components/youtube.mdx b/src/content/docs/style-guide/components/youtube.mdx
index 8b24f0d71780445..b7dd62471b86ad2 100644
--- a/src/content/docs/style-guide/components/youtube.mdx
+++ b/src/content/docs/style-guide/components/youtube.mdx
@@ -7,12 +7,12 @@ products:
   - style-guide
 ---
 
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 <YouTube id="XHvmX3FhTwU" />
 
 ```mdx
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 <YouTube id="XHvmX3FhTwU" />
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/style-guide/contributions.mdx b/src/content/docs/style-guide/contributions.mdx
index 5921a50b9de6eba..26f56188f64db34 100644
--- a/src/content/docs/style-guide/contributions.mdx
+++ b/src/content/docs/style-guide/contributions.mdx
@@ -2,23 +2,27 @@
 title: Contributions
 description: Learn how to contribute to the Cloudflare Docs.
 sidebar:
-    order: 1
+  order: 1
 products:
   - style-guide
 ---
+
 import { Details } from "~/components";
 
 The [Cloudflare Docs](https://developers.cloudflare.com/) are open source and hosted on the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs) on GitHub. This means that anyone, including those who are not part of the Cloudflare organization, can contribute to them. We welcome all suggestions that help keep our docs high quality and up to date.
 
 To contribute to our docs, you will need to [create an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) (if you do not have one already) and log in. Then you have three options:
-* [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
-* [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
-* [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
+
+- [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
+- [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
+- [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
 
 In addition to using the [Cloudflare Style Guide](/style-guide/) for guidance on grammar and style, we recommend browsing our [components](/style-guide/components/) to add additional formatting such as buttons, tabs, and collapsible sections.
 
 ## Create a GitHub issue
+
 To create a GitHub issue:
+
 1. [Log in to GitHub](https://github.com/login) and go to the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs).
 2. Select **Issues** and then **New issue**.
 3. Select the issue type, fill out the form, and select **Create**.
@@ -26,53 +30,63 @@ To create a GitHub issue:
 [Learn more about creating GitHub issues.](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue)
 
 ## Quick edit
+
 To quickly create a pull request using the edit button:
+
 1. [Log in to GitHub](https://github.com/login).
 2. Go to the page you want to edit in the [Cloudflare Docs](https://developers.cloudflare.com/)
 3. Select <Details header="**Edit** or **Edit page**">Every page in the Cloudflare Docs (including this one) has an **Edit** button on the right sidebar and an **Edit page** button on the very bottom of the page.
- ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
-The page's Markdown opens.
-	:::note
-	The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
-	:::
+   ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
+   The page's Markdown opens.
+   :::note
+   The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
+   :::
 4. Make your edits and select **Commit changes**.
 5. In the form, update the **Commit message** with the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 6. Update the **Extended description** with more details about what you changed and why. The more details, the better.
 7. Select **Propose changes** > **Create pull request** > **Create pull request** again.
 
 ## Full development
+
 To edit and create a pull request with the [full development workflow](https://docs.github.com/en/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace):
+
 1. [Log in to GitHub](https://github.com/login) and [fork the cloudflare-docs repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
 2. If you are editing in your web browser (with [Codespaces](https://docs.github.com/en/codespaces)), move on to step 3.
-<br/>If you are editing on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)):
-	* (Required) Install [Node.js](https://nodejs.org/en) (version 24 or later).
-	* (Recommended, but not required) Install [Volta](https://volta.sh/) for easier package management.
-	* (Required) [Clone the fork to your local machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
+   <br />
+   If you are editing on your local machine (with [Visual Studio
+   Code](https://code.visualstudio.com/)): * (Required) Install
+   [Node.js](https://nodejs.org/en) (version 24 or later). * (Recommended, but
+   not required) Install [Volta](https://volta.sh/) for easier package
+   management. * (Required) [Clone the fork to your local
+   machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
 3. Create a branch from your fork (or from your clone).
-3. Make your edits.
-:::note[Preview your edits]
-To preview your edits, you need to install `pnpm`.
- ```bash
- pnpm install
- ```
+4. Make your edits.
+   :::note[Preview your edits]
+   To preview your edits, you need to install `pnpm`.
+
+```bash
+pnpm install
+```
+
 Then, run `pnpm run dev`.
- ```bash
- pnpm run dev
- ```
+
+```bash
+pnpm run dev
+```
+
 A link will appear in the terminal, `https://localhost:1111/`, where you can preview your edits. This link automatically updates with any new edits you make.
-:::
-5. Commit your changes.
-6. Push your commits to your branch and then back to your fork.
-7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
+::: 5. Commit your changes. 6. Push your commits to your branch and then back to your fork. 7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 
 ## After you create an issue or PR
+
 After you create an issue or PR, a member of the Cloudflare organization will review your suggestion. Here is what to expect:
-* A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
-* If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
-* If your changes are approved:
-	* For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
-	* For GitHub PRs, the Cloudflare member will merge your PR.
-* If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
+
+- A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
+- If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
+- If your changes are approved:
+  - For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
+  - For GitHub PRs, the Cloudflare member will merge your PR.
+- If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
 
 Thank you for contributing to our open-source ecosystem and being a part of the Cloudflare community.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
index 899c473a810e03e..38e5c2fa935864f 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
@@ -18,9 +18,9 @@ When at all possible, Cloudflare seeks to avoid creating static representations
 
 Potential examples include:
 
-* Exhaustive listing of fields
-* Replicating API content in developer docs
-* Maintaining lists of potential options in the UI (i.e., Alert types)
-* Verified Bots
+- Exhaustive listing of fields
+- Replicating API content in developer docs
+- Maintaining lists of potential options in the UI (i.e., Alert types)
+- Verified Bots
 
 The preferred approach would be speak more generally to the categories or specific, high-value fields.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
index 335031ce0afc95f..f02e3493fdef2c0 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
@@ -12,14 +12,12 @@ A code sample or line of text that shows the specific structure of a request/res
 
 :::note
 
-
 If you are unsure about when to categorize something as an example or tutorial, remember:
 
 Examples are a component attribute and are typically a snippet of code a user might copy and paste to run a task. Examples should not have multiple steps. A tutorial might contain an example, but an example will not contain a tutorial.
 
 Tutorials are a content type, typically longer form, and contain multiple steps to help users connect products to real-world scenarios.
 
-
 :::
 
 ## Used in
@@ -36,9 +34,9 @@ Explain what the code sample does in a short sentence.
 
 These could include:
 
-* Example requests and responses
-* Example inputs and outputs
-* Field values for UI and/or API
+- Example requests and responses
+- Example inputs and outputs
+- Field values for UI and/or API
 
 ## Additional information
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
index eb6cc09d35a217d..d2ac5552b440a7c 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
@@ -56,21 +56,16 @@ entries:
 Relevant values include the following:
 
 - `productName` string required
-
   - Core product associated with this file. Should always match the same formatting / styling used in `associated_products`.
 
 - `entries` object required
-
   - `term` string required
-
     - The glossary term itself.
 
   - `general_definition` string required
-
     - Definition of the term. Should be general enough to apply to multiple products. Should also start with a lowercase letter unless starting with a proper noun.
 
   - `associated_products` array optional
-
     - If the term is associated with other products. Any names used should correspond to the `productName` of that associated file.
 
 ### Usage
@@ -109,11 +104,9 @@ Is a quoted definition that comes from:
 Properties are:
 
 - `term` string required
-
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
-
   - Text to add before a definition.
 
 #### Glossary tooltip
@@ -129,15 +122,12 @@ Here's a <GlossaryTooltip term="active zone">tooltip</GlossaryTooltip> example.
 Properties are:
 
 - `term` string required
-
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
-
   - Text to add before a definition.
 
 - `link` string optional
-
   - Wraps the inner text in a markdown link, similar to normal markdown formatting.
 
 Because of space limitations, the tooltip will always default to the short definition of a term, meaning the definition text before the first line break.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
index 0e75f19c6dc5e99..6027b8e869f159d 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
index 017decd9096ef80..c412e4ff4c12769 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
@@ -28,15 +28,15 @@ This reference architecture is designed for IT or security professionals with so
 
 To build a stronger baseline understanding of Cloudflare, we recommend the following resources:
 
-* What is Cloudflare? | Website (5 minute read) or video (2 minutes)
-* Solution Brief: Cloudflare One (3 minute read)
-* Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
-* Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
+- What is Cloudflare? | Website (5 minute read) or video (2 minutes)
+- Solution Brief: Cloudflare One (3 minute read)
+- Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
+- Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
 
 Those who read this reference architecture will learn:
 
-* How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
-* How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
-* How to plan for deploying Cloudflare One
+- How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
+- How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
+- How to plan for deploying Cloudflare One
 
 While this document examines Cloudflare One at a technical level, it does not offer fine detail about every product in the platform. Instead, it looks at how all the services in Cloudflare One enable networking and network security to be consolidated on one architecture. Visit the developer documentation for further information specific to a product area or use case.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
index 5935c28d4a85d09..aa2c818fd681979 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
@@ -44,15 +44,15 @@ Cross-links between related pages create a navigable knowledge graph. When an AI
 
 Every page with a `pcx_content_type` should include links to related pages in its **Related resources** section. Use the following table to determine which content types to link to from each page.
 
-| Content type | Must link to |
-| --- | --- |
-| Concept | Related how-to or get-started page; related reference page |
-| How-to | Prerequisite concept page; relevant configuration page; troubleshooting page |
-| Get started | Next-level how-to pages; product overview page |
-| Troubleshooting | Related how-to page; relevant configuration page |
-| Configuration | Parent how-to or get-started page; relevant concept page |
-| Reference | Related concept page; how-to pages that use the reference |
-| Tutorial | Related product overview; prerequisite get-started page |
+| Content type    | Must link to                                                                 |
+| --------------- | ---------------------------------------------------------------------------- |
+| Concept         | Related how-to or get-started page; related reference page                   |
+| How-to          | Prerequisite concept page; relevant configuration page; troubleshooting page |
+| Get started     | Next-level how-to pages; product overview page                               |
+| Troubleshooting | Related how-to page; relevant configuration page                             |
+| Configuration   | Parent how-to or get-started page; relevant concept page                     |
+| Reference       | Related concept page; how-to pages that use the reference                    |
+| Tutorial        | Related product overview; prerequisite get-started page                      |
 
 Links should be bidirectional. If a concept page links to a how-to, the how-to should link back to the concept page. This ensures that users (and AI systems) can traverse between pages in either direction.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
index 7971b04fd461597..6bd0cb8c746ca6e 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
@@ -20,7 +20,7 @@ If an operation occurs inside of a code block, use the formatting associated wit
 
 ## Example
 
-| Correct                       | Incorrect         |
-| ----------------------------- | ----------------- |
-| 25 / 30                       | 25/30             |
+| Correct             | Incorrect         |
+| ------------------- | ----------------- |
+| 25 / 30             | 25/30             |
 | `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏` | e(aP,bQ)=e(P,Q)ab |
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
index dd344888b67b5bd..365813c38ea3809 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
@@ -20,9 +20,9 @@ One to two sentences
 
 It should answer:
 
-* What happens now?
-* What was the end result of the procedure?
-* What do users do next?
+- What happens now?
+- What was the end result of the procedure?
+- What do users do next?
 
 ## Cross-linking
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
index f17397285f578bf..59f4a527a66fde9 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
@@ -52,7 +52,7 @@ Use a warning to alert a reader to behavior that could impact the security of a
 
 ## Recommendations
 
-* **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
-* **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
-* **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
-* **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
+- **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
+- **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
+- **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
+- **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
index b0d981549ac0adf..f696235502bd1f7 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
@@ -14,10 +14,10 @@ The information architecture (IA) of the Cloudflare developer documentation foll
 
 At launch, Cloudflare Developer Platform products are recommended to include the following high-level sections. The following is a recommended guideline based on standard user journey flow (Learn, Get started, Configure, Test, Deploy, Asses, Maintain, etc.) and is intended to serve as a helpful reference to the documentation writer and collaborators. Depending on the product and as products mature, the IA may grow out of this structure or differ from this structure based on what you can do with the product. For an example of a more mature product that differs from this IA, refer to the [Cloudflare Stream documentation](/stream/).
 
-* [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
-* [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
-* [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
-* Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
-* [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
-* [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
-* Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
+- [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
+- [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
+- [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
+- Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
+- [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
+- [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
+- Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
diff --git a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
index 1b38177313b1f44..5ec373d9988218e 100644
--- a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
+++ b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
@@ -80,9 +80,9 @@ In nested menus, use bold for the word not the symbol.
 
 Example: **Dashboard** > **This** > **That**
 
-## *Italics*
+## _Italics_
 
-Use *italics* when referring to an option that customers can select from, like in dropdown menus.
+Use _italics_ when referring to an option that customers can select from, like in dropdown menus.
 
 Do not use italics when referring to the state of a toggle - for example, enabled/disabled should not be italicized.
 
@@ -94,32 +94,32 @@ Text in this font denotes text or characters that you should enter from the keyb
 
 ### Examples of elements we monospace
 
-| Element                                                    | Example                                                                                                    |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
-| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                       |
-| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                              |
-| API commands                                               | The endpoint supports `GET` for JSON format.                                                               |
-| Terminal commands                                          | Run the command `wrangler login`.                                                                          |
-| Attribute names and values                                 | `type`, `name`                                                                                             |
-| Class names                                                | `button-primary`                                                                                           |
-| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                   |
-| Data types                                                 | (`string`, `number`, `int64`)                                                                              |
-| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                         |
-| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink.  |
-| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                  |
-| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                         |
-| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                     |
-| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                        |
-| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                            |
-| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                      |
-| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx. |
-| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                       |
-| HTTP header names                                          | `Content-Length`                                                                                           |
-| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                               |
-| IAM role names                                             | `roles/storage.admin`                                                                                      |
-| Language keywords                                          | `in`, `await`                                                                                              |
-| Method and function names                                  | `handleRequest`                                                                                            |
-| Namespace aliases                                          | `numpy`                                                                                                    |
-| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                         |
-| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                     |
-| Text input                                                 | `"Hello Worker"`                                                                                           |
+| Element                                                    | Example                                                                                                                                                                                      |
+| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                                                                                                         |
+| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                                                                                                                |
+| API commands                                               | The endpoint supports `GET` for JSON format.                                                                                                                                                 |
+| Terminal commands                                          | Run the command `wrangler login`.                                                                                                                                                            |
+| Attribute names and values                                 | `type`, `name`                                                                                                                                                                               |
+| Class names                                                | `button-primary`                                                                                                                                                                             |
+| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                                                                                                     |
+| Data types                                                 | (`string`, `number`, `int64`)                                                                                                                                                                |
+| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                                                                                                           |
+| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink. |
+| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                                                                                                    |
+| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                                                                                                           |
+| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                                                                                                       |
+| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                                                                                                            |
+| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                                                                                                              |
+| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                                                                                                        |
+| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx.                                                                                   |
+| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                                                                                                         |
+| HTTP header names                                          | `Content-Length`                                                                                                                                                                             |
+| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                                                                                                                 |
+| IAM role names                                             | `roles/storage.admin`                                                                                                                                                                        |
+| Language keywords                                          | `in`, `await`                                                                                                                                                                                |
+| Method and function names                                  | `handleRequest`                                                                                                                                                                              |
+| Namespace aliases                                          | `numpy`                                                                                                                                                                                      |
+| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                                                                                                           |
+| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                                                                                                       |
+| Text input                                                 | `"Hello Worker"`                                                                                                                                                                             |
diff --git a/src/content/docs/style-guide/formatting/dates-and-times.mdx b/src/content/docs/style-guide/formatting/dates-and-times.mdx
index ab9f427759fec31..70172f50376d6b5 100644
--- a/src/content/docs/style-guide/formatting/dates-and-times.mdx
+++ b/src/content/docs/style-guide/formatting/dates-and-times.mdx
@@ -10,9 +10,9 @@ products:
 
 To account for internationalization and inclusivity of all locales, use the ISO-8601 (YYYY-MM-DD hh:mm:ss) standard when writing dates and times as much as possible.
 
-In general, documentation should strive to represent universal truth, not 
-something time-bound. This is why semgrep may flag uses of explicit dates 
-or month names or years because often become out-of-date and not be 
+In general, documentation should strive to represent universal truth, not
+something time-bound. This is why semgrep may flag uses of explicit dates
+or month names or years because often become out-of-date and not be
 revised later.
 
 ## Blogs
diff --git a/src/content/docs/style-guide/formatting/external-references.mdx b/src/content/docs/style-guide/formatting/external-references.mdx
index 19253920fd68de6..49120127e781b06 100644
--- a/src/content/docs/style-guide/formatting/external-references.mdx
+++ b/src/content/docs/style-guide/formatting/external-references.mdx
@@ -11,9 +11,9 @@ When referencing external resources, ensure that you are linking to a trustworth
 
 For general websites, consider the following recommendations about the link text:
 
-* Use the website name if you are linking to the home page.
-* Use the page name if you are linking to a specific page.
-* Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
+- Use the website name if you are linking to the home page.
+- Use the page name if you are linking to a specific page.
+- Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
 When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
diff --git a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
index 316c3540dcbba9d..7ef14947ec6845d 100644
--- a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
+++ b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
@@ -8,8 +8,8 @@ products:
 
 You can refer both to file types and file extensions in documentation:
 
-* File types: Accepted file formats are JSON and YAML.
-* File extensions: Upload the `.txt` file to the dashboard.
+- File types: Accepted file formats are JSON and YAML.
+- File extensions: Upload the `.txt` file to the dashboard.
 
 When referring to a specific file type, always use regular text formatting, write the file type in uppercase, and avoid the initial dot (you are referring to the file type, not the file extension).
 
@@ -17,7 +17,7 @@ When referring to a specific extension, always monospace the file, include a dot
 
 Additional examples:
 
-* The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
-* Additionally, this plist can be wrapped in a `.mobileconfig` file.
-* If you would like to test how this feature works, here is a sample `.csv` file.
-* Concatenate the string to a text-based `.pem` file.
+- The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
+- Additionally, this plist can be wrapped in a `.mobileconfig` file.
+- If you would like to test how this feature works, here is a sample `.csv` file.
+- Concatenate the string to a text-based `.pem` file.
diff --git a/src/content/docs/style-guide/formatting/index.mdx b/src/content/docs/style-guide/formatting/index.mdx
index 8c1d56e0c307810..7ec4a59dacb722c 100644
--- a/src/content/docs/style-guide/formatting/index.mdx
+++ b/src/content/docs/style-guide/formatting/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/keyboard-keys.mdx b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
index d9faeed37a3cd77..9dad67aca460e95 100644
--- a/src/content/docs/style-guide/formatting/keyboard-keys.mdx
+++ b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
@@ -14,16 +14,20 @@ products:
 ## Formatting keyboard shortcuts
 
 When telling readers what keyboard shortcuts to use to achieve a result:
+
 - Place the keyboard shortcut in between backticks (monospace formatting)
 - Use uppercase letters with the abbreviated version of the key (`CTRL` instead of `CONTROL`, `CMD` instead of `COMMAND`for example)
 - Wrap the complete keyboard shortcut in between backticks, including the plus sign:
-	- **Do**:
-	```mdx
-	`CTRL + C`
-	```
-
-	- **Don't**:
-	```mdx
-	`CTRL` + `C`
-	```
-- Do not use the old `<kbd></kbd>` component
\ No newline at end of file
+  - **Do**:
+
+  ```mdx
+  `CTRL + C`
+  ```
+
+  - **Don't**:
+
+  ```mdx
+  `CTRL` + `C`
+  ```
+
+- Do not use the old `<kbd></kbd>` component
diff --git a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
index 382bab58c8d7d78..02c81845f3a290b 100644
--- a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
+++ b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
@@ -9,6 +9,7 @@ products:
 When adding a note to a page, always use this special note formatting. There are three types of formatted notes: `note`, `caution`, and `tip`.
 
 Here is some additional information about notes:
+
 - The color of the note depends on the type of note: `note` is blue, `caution` is yellow, and `tip` is purple.
 - For every note type, the header text is optional.
 - All note types can contain text and additional formatting like lists, code blocks, and images.
diff --git a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
index 5085765a1f2090b..96a4801c772e1e3 100644
--- a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
+++ b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
@@ -10,26 +10,26 @@ products:
 
 In body text, spell out whole numbers from zero through nine.
 
-* Example: We have added three more servers.
+- Example: We have added three more servers.
 
 For numbers greater than or equal to 10, use digits.
 
-* Example: The message is 32 bytes long, \[...]
+- Example: The message is 32 bytes long, \[...]
 
 For analytics, display metrics with numerals.
 Use commas for numbers with more than 3 digits (no spaces). Note the differences in numerical punctuation for translation.
 
-* 300
-* 1,000
-* 7,465
+- 300
+- 1,000
+- 7,465
 
 ## Using k to indicate thousands
 
 Do not put a space between the number and k.
 
-Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for *kilobytes*.
+Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for _kilobytes_.
 
-* Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
+- Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
 
 ## Units of measurement
 
@@ -45,14 +45,14 @@ Many CPU architectures either do not allow execution of the machine code, which
 
 In general, only abbreviate units of measurements when they modify specific quantities/numbers. When you need to abbreviate them:
 
-| ✅     | ❌      | Rationale                                              |
+| ✅    | ❌     | Rationale                                              |
 | ----- | ------ | ------------------------------------------------------ |
 | 10 m  | 10m    | Always include a space between the number and the unit |
 | 10 cm | 10 cms | Unit symbols should unaltered in the plural.           |
 
 **Always include a space between a numerical value and the corresponding unit of measurement.** Although both formats are widely used, the metric system standardized the use of a space before a unit of measurement and should be used as a guideline to keep content consistent and clear.
 
-| ✅                                                | ❌                                           | Rationale                                                                                                   |
+| ✅                                               | ❌                                          | Rationale                                                                                                   |
 | ------------------------------------------------ | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
 | 128 GB                                           | 128 gb, 128gb, 128GB                        | Units of measurement should always be capitalized and spaced out from their corresponding numerical values. |
 | This network has a capacity of over **30 Tbps.** | This network has a capacity of over 30Tbps. | Adding a space between ‘30’ and ‘Tbps’ makes this sentence easier to read.                                  |
diff --git a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
index e44f43ed36fdc50..25c6ca97daeed00 100644
--- a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
+++ b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
@@ -10,5 +10,5 @@ Product names should follow a noun-verb agreement such that the verb is singular
 
 Examples:
 
-* Cloudflare Pages enables/allows.
-* Cloudflare Workers executes/propagates.
+- Cloudflare Pages enables/allows.
+- Cloudflare Workers executes/propagates.
diff --git a/src/content/docs/style-guide/formatting/structure/index.mdx b/src/content/docs/style-guide/formatting/structure/index.mdx
index e2f981f9d22a682..3498fa8f873c716 100644
--- a/src/content/docs/style-guide/formatting/structure/index.mdx
+++ b/src/content/docs/style-guide/formatting/structure/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/structure/lists.mdx b/src/content/docs/style-guide/formatting/structure/lists.mdx
index 94571bd31ee8c27..35a60f4a49b706c 100644
--- a/src/content/docs/style-guide/formatting/structure/lists.mdx
+++ b/src/content/docs/style-guide/formatting/structure/lists.mdx
@@ -8,15 +8,15 @@ products:
 
 There are three types of lists:
 
-* Bulleted lists for unordered items
-* Numbered lists for ordered items
-* Embedded lists for items within a sentence
+- Bulleted lists for unordered items
+- Numbered lists for ordered items
+- Embedded lists for items within a sentence
 
 Here are some tips when creating lists:
 
-* Keep list items parallel
-* Start numbered lists with a command (imperative verb)
-* Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
+- Keep list items parallel
+- Start numbered lists with a command (imperative verb)
+- Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
 
 ## Bullet points
 
@@ -25,26 +25,37 @@ Bullet points help the reader's eye focus on a list of important elements.
 However, as with any other aspect of writing, they should be used mindfully. Below is a list of when you should and should not resort to bullet points.
 
 <table>
-  <thead>
-    <tr>
-        <th>❌ Do not use bullet points</th>
-        <th>✅ Use bullet points</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-        <td>To outline <b>processes</b> (prefer numbered lists)</td>
-        <td>To list <b>facts</b></td>
-    </tr>
-    <tr>
-        <td>To explain your reasoning (it is a blog post, not a list of system requirements)</td>
-        <td>To list <b>data</b></td>
-    </tr>
-    <tr>
-        <td>-</td>
-        <td>To list <b>options</b></td>
-    </tr>
-    </tbody>
+	<thead>
+		<tr>
+			<th>❌ Do not use bullet points</th>
+			<th>✅ Use bullet points</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>
+				To outline <b>processes</b> (prefer numbered lists)
+			</td>
+			<td>
+				To list <b>facts</b>
+			</td>
+		</tr>
+		<tr>
+			<td>
+				To explain your reasoning (it is a blog post, not a list of system
+				requirements)
+			</td>
+			<td>
+				To list <b>data</b>
+			</td>
+		</tr>
+		<tr>
+			<td>-</td>
+			<td>
+				To list <b>options</b>
+			</td>
+		</tr>
+	</tbody>
 </table>
 
 ## Bulleted lists
@@ -55,8 +66,8 @@ Do not punctuate bullet points unless each item is a full sentence.
 
 If bullet point items are followed by a description, use a colon after the heading and capitalize the description. For example,
 
-* **Item 1**: Description 1
-* **Item 2**: Description 2
+- **Item 1**: Description 1
+- **Item 2**: Description 2
 
 For bullet points, try to stick to the "six-pack" rule: no more than six bullets, each made up of six words or less.
 
@@ -67,14 +78,14 @@ Refer to [The best way to use bullet points](https://thewritinghabit.blog/2016/0
 When you find yourself creating a list of bullet points, go through this checklist:
 
 1. Do all bullet points belong together?
-   * Check that all the elements in the list are logically connected.
+   - Check that all the elements in the list are logically connected.
 2. Do I have more three or more bullet points, but less than six?
-   * Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
+   - Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
 3. Are all bullet points shorter than three lines of text?
-   * Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
+   - Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
 4. Is punctuation consistent?
-   * End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
+   - End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
 5. Do all bullet points start with the most important word we want the reader to remember?
-   * Make sure the "head" of your bullet point is not hiding after a long circumlocution.
+   - Make sure the "head" of your bullet point is not hiding after a long circumlocution.
 6. Do all bullet points start with the same part of speech?
-   * If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
+   - If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
diff --git a/src/content/docs/style-guide/formatting/structure/tables.mdx b/src/content/docs/style-guide/formatting/structure/tables.mdx
index d43a5fa3787672b..7a79ef760d68e39 100644
--- a/src/content/docs/style-guide/formatting/structure/tables.mdx
+++ b/src/content/docs/style-guide/formatting/structure/tables.mdx
@@ -12,14 +12,14 @@ Using tables to simplify content and data provides a comprehensive way to arrang
 
 Here are some tips when creating tables:
 
-* Label column headers.
-* Label row headers if appropriate.
-* Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
-* Avoid too much text.
-* Aim for parallelism within the column.
-* Keep tables as simple and as small as possible.
-* Sort rows in a logical order. If no logical order exists, use alphabetical order.
-* <Render file="table-guidelines" product="style-guide" />
+- Label column headers.
+- Label row headers if appropriate.
+- Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
+- Avoid too much text.
+- Aim for parallelism within the column.
+- Keep tables as simple and as small as possible.
+- Sort rows in a logical order. If no logical order exists, use alphabetical order.
+- <Render file="table-guidelines" product="style-guide" />
 
 ## Introductory sentences
 
@@ -29,25 +29,25 @@ When referring to a table, use a phrase like "the following table" or "the prece
 
 ## Column headings
 
-* Use sentence case.
-* Write concise headings that clearly describe the column content.
-* Do not end column headings with punctuation, including periods, ellipses, or colons.
-* Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
+- Use sentence case.
+- Write concise headings that clearly describe the column content.
+- Do not end column headings with punctuation, including periods, ellipses, or colons.
+- Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
 
 ```html
 <thead>
-  <tr>
-    <th scope="col">Name</th>
-    <th scope="col">Description</th>
-  </tr>
+	<tr>
+		<th scope="col">Name</th>
+		<th scope="col">Description</th>
+	</tr>
 </thead>
 ```
 
 ## Table placement
 
-* Place each table directly after the sentence that introduces it.
-* Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
-* If a table has footnotes, place them immediately after the table.
+- Place each table directly after the sentence that introduces it.
+- Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
+- If a table has footnotes, place them immediately after the table.
 
 ## Table captions
 
@@ -62,9 +62,9 @@ In Markdown, place the caption as a bold line immediately before the table:
 ```markdown
 **Table 1.** Supported DNS record types
 
-| Type | Description |
-| --- | --- |
-| A | Maps a domain to an IPv4 address |
+| Type | Description                      |
+| ---- | -------------------------------- |
+| A    | Maps a domain to an IPv4 address |
 | AAAA | Maps a domain to an IPv6 address |
 ```
 
@@ -72,19 +72,22 @@ In HTML, use the `caption` element as the first child of the `table` element:
 
 ```html
 <table>
-  <caption><b>Table 1.</b> Supported DNS record types</caption>
-  <thead>
-    <tr>
-      <th scope="col">Type</th>
-      <th scope="col">Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>A</td>
-      <td>Maps a domain to an IPv4 address</td>
-    </tr>
-  </tbody>
+	<caption>
+		<b>Table 1.</b>
+		Supported DNS record types
+	</caption>
+	<thead>
+		<tr>
+			<th scope="col">Type</th>
+			<th scope="col">Description</th>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>A</td>
+			<td>Maps a domain to an IPv4 address</td>
+		</tr>
+	</tbody>
 </table>
 ```
 
@@ -94,8 +97,8 @@ Tables display pieces of information that have some sort of relationship.
 
 Example:
 
-* Dates and descriptions, like a changelog
-* A list of products with attributes
+- Dates and descriptions, like a changelog
+- A list of products with attributes
 
 ## When not to use tables
 
@@ -139,7 +142,7 @@ The rendered output looks like this:
 | Syntax    | Description |    Test Text |
 | :-------- | :---------: | -----------: |
 | Header    |    Title    | Here is this |
-| Paragraph |     Text    |     And more |
+| Paragraph |    Text     |     And more |
 
 ## Formatting text in tables
 
diff --git a/src/content/docs/style-guide/frontmatter/sidebar.mdx b/src/content/docs/style-guide/frontmatter/sidebar.mdx
index ec8a552cab6f221..b28d8a5f1d52ccb 100644
--- a/src/content/docs/style-guide/frontmatter/sidebar.mdx
+++ b/src/content/docs/style-guide/frontmatter/sidebar.mdx
@@ -215,5 +215,5 @@ sidebar:
 
 ### Automatic "Beta" badges
 
-A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status. 
-This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`. 
+A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status.
+This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`.
diff --git a/src/content/docs/style-guide/grammar/index.mdx b/src/content/docs/style-guide/grammar/index.mdx
index d70d2ce818eea88..c7d3f0ea3544cd9 100644
--- a/src/content/docs/style-guide/grammar/index.mdx
+++ b/src/content/docs/style-guide/grammar/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
index 3241618b639da6b..bffb664c1bd3269 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
@@ -6,7 +6,7 @@ products:
   - style-guide
 ---
 
-Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word *acronym* to refer to both).
+Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word _acronym_ to refer to both).
 
 ## Long and short versions of a word
 
@@ -16,7 +16,7 @@ The short versions of the words are not abbreviations, and if you use them, you
 
 If you are not sure whether a word is an abbreviation or just a short version of a longer word, here is a list of [common abbreviations](https://abbreviations.yourdictionary.com/articles/list-of-commonly-used-abbreviations.html). If that does not settle the issue, use the speaking test: if you speak the short version as a word ("This is a demo version of the product"), you can usually treat it as a word and not an abbreviation.
 
-If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer *applications* on Cloudflare for Teams are not shortened to *apps*. Depending on the use case, application might be the preferred term, especially due to translation.
+If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer _applications_ on Cloudflare for Teams are not shortened to _apps_. Depending on the use case, application might be the preferred term, especially due to translation.
 
 ## When to spell out a term
 
@@ -24,28 +24,28 @@ In general, when an abbreviation is likely to be unfamiliar to the audience, spe
 
 If the first mention of a term occurs in a heading or title, you can use the abbreviation and then spell out the abbreviation in the first paragraph that follows the heading or title.
 
-When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out *application programming interface*. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
+When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out _application programming interface_. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
 
-In some cases, spelling out a term does not help the reader understand the term. For example, writing out *portable document format* does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
+In some cases, spelling out a term does not help the reader understand the term. For example, writing out _portable document format_ does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
 
 The following abbreviations rarely need to be spelled out:
 
-* API
-* DVD
-* File formats such as PDF or XML
-* HTML
-* PC
-* RAM
-* REST
-* Units of measure such as MB or GB
-* URL
-* USB
+- API
+- DVD
+- File formats such as PDF or XML
+- HTML
+- PC
+- RAM
+- REST
+- Units of measure such as MB or GB
+- URL
+- USB
 
 ## Abbreviations not to use
 
 Prefer English terms over Latin abbreviations. Do not use i.e. or e.g. Instead, use **that is** or **for example**, respectively.
 
-One exception: avoid both *etc.* and *and so on* wherever possible, but if you really need to use one, use *etc.* Always include the period, even if a comma follows immediately after.
+One exception: avoid both _etc._ and _and so on_ wherever possible, but if you really need to use one, use _etc._ Always include the period, even if a comma follows immediately after.
 
 Do not use Internet slang abbreviations such as tl;dr, IMO, FYI, or others.
 
@@ -55,16 +55,16 @@ Use the most common form of a word. If the full spelled-out word is common and e
 
 Follow these guidelines:
 
-* Do not use periods with acronyms or initialisms.
-* Put a period at the end of a shortened word, except for date and time abbreviations.
-* If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
-* Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
+- Do not use periods with acronyms or initialisms.
+- Put a period at the end of a shortened word, except for date and time abbreviations.
+- If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
+- Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
 
 ## i.e. vs e.g.
 
 While similar, these two Latin abbreviations carry very different meanings.
 
-* **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
-  * The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
-* **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
-  * Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
+- **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
+  - The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
+- **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
+  - Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
index 1b9979cc0ba573e..3d4836341a01f1b 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
@@ -6,10 +6,10 @@ products:
   - style-guide
 ---
 
-**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some  terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
+**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
 
-* If the term already exists, link to a good existing explanation.
+- If the term already exists, link to a good existing explanation.
 
-* If your document is introducing the term, define the term.
+- If your document is introducing the term, define the term.
 
-* **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods  between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word  — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
+- **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
index fbbcad12c379e14..ca1c548ad846c7e 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
@@ -10,7 +10,7 @@ products:
 
 Each product, service, and feature should be properly spelled and capitalized when used in any content, both to ensure consistency across all channels and to differentiate common performance and security technologies (for example: load balancing, bot management, and web application firewalls) from specific Cloudflare solutions (for example: Cloudflare Load Balancing, Cloudflare Bot Management, and Cloudflare Web Application Firewall).
 
-| ✅                                                                                                                                                           | ❌                                                                                                                                                | Rationale                                                                                                                                   |
+| ✅                                                                                                                                                          | ❌                                                                                                                                               | Rationale                                                                                                                                   |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | This interactive demo provides three different scenarios on how to utilize **Cloudflare Rate Limiting** to protect your endpoints from suspicious requests. | This interactive demo provides three different scenarios on how to utilize **rate limiting** to protect your endpoints from suspicious requests. | This demo is specific to a Cloudflare product (Cloudflare Rate Limiting), not a tutorial on utilizing generic rate limiting.                |
 | The **Cloudflare Web Application Firewall (WAF)** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.       | Our **web application firewall** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.             | Cloudflare Web Application Firewall (WAF) is a specific product we offer and should be capitalized and identified with the Cloudflare name. |
@@ -19,75 +19,109 @@ Each product, service, and feature should be properly spelled and capitalized wh
 
 **When to use Waiting Room capitalized and singular:**
 
-* Naming the product: *Waiting Room keeps wait times low by dynamically managing traffic.*
-* Page title: *Access Waiting Room*
-* Preceded by “Cloudflare”: *Cloudflare Waiting Room allows organizations to…*
-* Preceding a feature name: *Waiting Room Event Scheduling*
+- Naming the product: _Waiting Room keeps wait times low by dynamically managing traffic._
+- Page title: _Access Waiting Room_
+- Preceded by “Cloudflare”: _Cloudflare Waiting Room allows organizations to…_
+- Preceding a feature name: _Waiting Room Event Scheduling_
 
 **When to waiting room(s) lower-case and in singular or plural:**
 
-* Used as an object: *Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room.*
-* Capitalize only the first word when at the beginning of a sentence:  *Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated.*
-* Capitalize only the first word when it is the title of a subsection: *### Waiting room template*
+- Used as an object: _Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room._
+- Capitalize only the first word when at the beginning of a sentence: _Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated._
+- Capitalize only the first word when it is the title of a subsection: _### Waiting room template_
 
 ## Common capitalization conventions
 
 <table>
-  <tr>
-    <th style="width:20%">✅</th>
-    <th style="width:20%">❌</th>
-    <th>Rationale</th>
-  </tr>
-  <tr>
-    <td>CAPTCHA, reCAPTCHA</td>
-    <td>Captcha, captcha, recaptcha, Recaptcha</td>
-    <td>A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are not bots.</td>
-  </tr>
-  <tr>
-    <td>cloud</td>
-    <td>Cloud, "cloud"</td>
-    <td>The <b>cloud</b> is a network of remote servers used to store and maintain data. </td>
-  </tr>
-  <tr>
-    <td>DDoS</td>
-    <td>ddos, DDOS</td>
-    <td>A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a targeted server.</td>
-  </tr>
-  <tr>
-    <td>denial-of-service (DoS)</td>
-    <td>denial of service, Denial-of-Service, Denial-Of-Service, Denial of Service, dos, Dos, DOS</td>
-    <td>DDoS is a type of <b>DoS</b> attack.</td>
-  </tr>
-  <tr>
-    <td>Enterprise, enterprise</td>
-    <td>ent, ENT</td>
-    <td>Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise customers are enterprise companies, but not all enterprises are Enterprise customers. </td>
-  </tr>
-  <tr>
-    <td>Internet</td>
-    <td>internet</td>
-    <td>Disabling this option may cause all devices to lose <b>Internet</b> connectivity.</td>
-  </tr>
-  <tr>
-    <td>SSL</td>
-    <td>ssl</td>
-    <td><b>SSL</b> is an encryption-based Internet security protocol.</td>
-  </tr>
-  <tr>
-    <td>TLS</td>
-    <td>tls</td>
-    <td><b>TLS</b> is a security protocol designed to facilitate privacy and data security for communications over the Internet..</td>
-  </tr>
-  <tr>
-    <td>WAF</td>
-    <td>waf</td>
-    <td><b>WAF</b> is a security system that helps protect web applications by filtering and monitoring HTTP traffic between a web application and the Internet. </td>
-  </tr>
-  <tr>
-    <td>Zero Trust</td>
-    <td>zero trust</td>
-    <td><b>Cloudflare</b> Access is a Zero Trust solution that secures inbound connections to your protected applications.</td>
-  </tr>
+	<tr>
+		<th style="width:20%">✅</th>
+		<th style="width:20%">❌</th>
+		<th>Rationale</th>
+	</tr>
+	<tr>
+		<td>CAPTCHA, reCAPTCHA</td>
+		<td>Captcha, captcha, recaptcha, Recaptcha</td>
+		<td>
+			A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are
+			not bots.
+		</td>
+	</tr>
+	<tr>
+		<td>cloud</td>
+		<td>Cloud, "cloud"</td>
+		<td>
+			The <b>cloud</b> is a network of remote servers used to store and maintain
+			data.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>DDoS</td>
+		<td>ddos, DDOS</td>
+		<td>
+			A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a
+			targeted server.
+		</td>
+	</tr>
+	<tr>
+		<td>denial-of-service (DoS)</td>
+		<td>
+			denial of service, Denial-of-Service, Denial-Of-Service, Denial of
+			Service, dos, Dos, DOS
+		</td>
+		<td>
+			DDoS is a type of <b>DoS</b> attack.
+		</td>
+	</tr>
+	<tr>
+		<td>Enterprise, enterprise</td>
+		<td>ent, ENT</td>
+		<td>
+			Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or
+			a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise
+			customers are enterprise companies, but not all enterprises are Enterprise
+			customers.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>Internet</td>
+		<td>internet</td>
+		<td>
+			Disabling this option may cause all devices to lose <b>Internet</b>{" "}
+			connectivity.
+		</td>
+	</tr>
+	<tr>
+		<td>SSL</td>
+		<td>ssl</td>
+		<td>
+			<b>SSL</b> is an encryption-based Internet security protocol.
+		</td>
+	</tr>
+	<tr>
+		<td>TLS</td>
+		<td>tls</td>
+		<td>
+			<b>TLS</b> is a security protocol designed to facilitate privacy and data
+			security for communications over the Internet..
+		</td>
+	</tr>
+	<tr>
+		<td>WAF</td>
+		<td>waf</td>
+		<td>
+			<b>WAF</b> is a security system that helps protect web applications by
+			filtering and monitoring HTTP traffic between a web application and the
+			Internet.{" "}
+		</td>
+	</tr>
+	<tr>
+		<td>Zero Trust</td>
+		<td>zero trust</td>
+		<td>
+			<b>Cloudflare</b> Access is a Zero Trust solution that secures inbound
+			connections to your protected applications.
+		</td>
+	</tr>
 </table>
 
 ## Headings
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
index 1e61e8bfdd8ecf5..e7f8868af4430c8 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
@@ -11,31 +11,34 @@ products:
 Whitespace is used in our blog posts and product content. For the sake of consistency, follow these conventions when using them:
 
 <table>
-  <tr>
-    <th style="width:20%">✅</th>
-    <th style="width:20%">❌</th>
-    <th>Example</th>
-  </tr>
-  <tr>
-    <td>nameserver</td>
-    <td>name servers</td>
-    <td>Change your nameservers to Cloudflare's.</td>
-  </tr>
-  <tr>
-    <td>hostname</td>
-    <td>host name</td>
-    <td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
-  </tr>
-  <tr>
-    <td>data center</td>
-    <td>datacenter</td>
-    <td>Cloudflare updates the new setting across all of our data centers around the world.</td>
-  </tr>
-  <tr>
-    <td>checkbox</td>
-    <td>check box</td>
-    <td>Select the Transfer lock checkbox before continuing the setup.</td>
-  </tr>
+	<tr>
+		<th style="width:20%">✅</th>
+		<th style="width:20%">❌</th>
+		<th>Example</th>
+	</tr>
+	<tr>
+		<td>nameserver</td>
+		<td>name servers</td>
+		<td>Change your nameservers to Cloudflare's.</td>
+	</tr>
+	<tr>
+		<td>hostname</td>
+		<td>host name</td>
+		<td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
+	</tr>
+	<tr>
+		<td>data center</td>
+		<td>datacenter</td>
+		<td>
+			Cloudflare updates the new setting across all of our data centers around
+			the world.
+		</td>
+	</tr>
+	<tr>
+		<td>checkbox</td>
+		<td>check box</td>
+		<td>Select the Transfer lock checkbox before continuing the setup.</td>
+	</tr>
 </table>
 
 When using compound words that have a preposition in them (think log in, or set up), they should be written as two separate words when they are verbs, and as one word when they are nouns.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
index fdb9214b95f5fc2..72a9ab7762531bd 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
@@ -6,4 +6,4 @@ products:
   - style-guide
 ---
 
-Avoid using contractions such as *don't*, *won't*, and *can't*.
+Avoid using contractions such as _don't_, _won't_, and _can't_.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
index dd8d05d847d9506..72d3c0deacba961 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
index deb7014e128ee54..76a0418aeb4ab62 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
@@ -14,7 +14,7 @@ Make sure it is clear who or what pronouns are in reference to. Pronouns act as
 
 Substitute "we" or "I" with "Cloudflare" if you need to represent Cloudflare. You do not need to use "we" constantly. However, use it when it is the best choice grammatically.
 
-| ✅                                                           | ❌                                                                 |
+| ✅                                                          | ❌                                                                |
 | ----------------------------------------------------------- | ----------------------------------------------------------------- |
 | Cloudflare recommends you submit image or plain text files. | We recommend closing your files before you restart your computer. |
 
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
index 187e021787a2e58..5f490a47e38f572 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
@@ -8,4 +8,4 @@ products:
 
 In general, avoid the 's construction to show possession by an inanimate object as doing so personifies the object.
 
-Example: *the device's address*.
+Example: _the device's address_.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
index 10c8af546776d4a..8e3704dfdac8622 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
@@ -8,6 +8,6 @@ products:
 
 You can put a preposition at the end of a sentence, but do not do it often. Your sentences can sound stilted if you try to avoid putting the preposition at the end.
 
-| ✅                                                     | ❌                                                          |
+| ✅                                                    | ❌                                                         |
 | ----------------------------------------------------- | ---------------------------------------------------------- |
 | Open the application you are submitting an image for. | Open the application for which you are submitting an icon. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
index 415d78fa7023e8f..39a5939c88506d9 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
@@ -18,6 +18,6 @@ Example: After you open the file, save it to your desktop with a different name.
 
 Use the Oxford comma. The Oxford comma should break up lists of three or more items in a sentence.
 
-Example:  Stream for Free, Pro, and Business plans
+Example: Stream for Free, Pro, and Business plans
 
 Without the Oxford comma, readers might misunderstand this header as free streaming for Pro and Business plans.
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
index 2773cd5a9e97ed4..6e37346b1c896c4 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
@@ -14,9 +14,9 @@ Dashes look like hyphens, but are wider. An em dash is the widest type of dash.
 
 Examples:
 
-* The most up-to-date software can be found here.
+- The most up-to-date software can be found here.
 
-* It takes 24-48 hours for the data to upload.
+- It takes 24-48 hours for the data to upload.
 
 :::note
 
@@ -26,7 +26,7 @@ Never include whitespaces around a hyphen.
 
 Additional examples:
 
-| ✅                                                                                                                    | ❌                                                                                                                    | Rationale                                                                                                                                                                                 |
+| ✅                                                                                                                   | ❌                                                                                                                   | Rationale                                                                                                                                                                                 |
 | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Protect your Internet property from common vulnerabilities with our enterprise-class Web Application Firewall (WAF). | Protect your Internet property from common vulnerabilities with our enterprise class Web Application Firewall (WAF). | ‘Enterprise-class’ refers to the ability of something to scale with and handle the needs of large enterprises. A hyphen is necessary because the compound modifier comes before the noun. |
 | Our WAF is enterprise class.                                                                                         | Our WAF is enterprise-class.                                                                                         | ‘Enterprise class’ modifies ‘WAF.’ A hyphen is not necessary because the compound modifier comes after the noun.                                                                          |
@@ -35,17 +35,17 @@ Additional examples:
 
 **Use em dashes to break up thoughts within a single sentence.** Em dashes (—) or double dashes (--) with spaces around them may be used to break up thoughts within a sentence. Single dashes (-), or hyphens, are commonly used to write compound words/modifiers and should never be used to break up thoughts in this way.
 
-* Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
+- Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
 
-* Shortcut for PC users: Hold down the Alt key and type 0151
+- Shortcut for PC users: Hold down the Alt key and type 0151
 
 Dashes are used in pairs (in place of parenthesis) or alone (in place of a semicolon or colon).
 
 Examples:
 
-* Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
+- Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
 
-* Embed yourself in the team — the best results will come when trust is built.
+- Embed yourself in the team — the best results will come when trust is built.
 
 :::note
 
@@ -54,7 +54,7 @@ Following AP style guides, and to improve readability, we include whitespaces be
 
 Additional examples:
 
-| ✅                                                                                                                                                  | ❌                                                                                                                                                | Rationale                                                                                                                                                      |
+| ✅                                                                                                                                                 | ❌                                                                                                                                               | Rationale                                                                                                                                                      |
 | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | The app has made security and privacy core to the company’s mission — and that is why it chose Cloudflare to provide an extra layer of protection. | The app has made security and privacy core to the company’s mission—and that is why it chose Cloudflare to provide an extra layer of protection. | An em dash with spaces on both sides is the appropriate way to distinguish the offset phrase at the end of this sentence.                                      |
 | ACME has always looked deeply into two sources of traffic -- organic and direct traffic.                                                           | ACME has always looked deeply into two sources of traffic - organic and direct traffic.                                                          | A double dash is the appropriate way to clarify different types of traffic at the end of this sentence. A hyphen should not be used in place of a double dash. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
index d73f721061e8356..6c7364bfdbb410d 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/how-we-docs/our-site.mdx b/src/content/docs/style-guide/how-we-docs/our-site.mdx
index 99ca2d006472130..22522e9cde5ff47 100644
--- a/src/content/docs/style-guide/how-we-docs/our-site.mdx
+++ b/src/content/docs/style-guide/how-we-docs/our-site.mdx
@@ -28,7 +28,6 @@ We use [Starlight](https://starlight.astro.build/) for our docs, which is a free
 
 Astro's [component overrides](https://starlight.astro.build/guides/overriding-components/) and [plugins](https://starlight.astro.build/resources/plugins/) system were a big part of us [choosing this framework](https://blog.cloudflare.com/open-source-all-the-way-down-upgrading-our-developer-documentation/) and have exponentially increased our [site's capabilities](/style-guide/components/) (without much extra work).
 
-
 ## Builds
 
 We use [GitHub Actions](https://github.com/features/actions) to build our site, which is then [hosted](#hosting) on Cloudflare.
diff --git a/src/content/docs/style-guide/how-we-docs/reviews.mdx b/src/content/docs/style-guide/how-we-docs/reviews.mdx
index da23b24233aa04c..26cc6567c416368 100644
--- a/src/content/docs/style-guide/how-we-docs/reviews.mdx
+++ b/src/content/docs/style-guide/how-we-docs/reviews.mdx
@@ -25,14 +25,14 @@ For pull requests, we use a specific [GitHub action](https://github.com/cloudfla
 - [Label products](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-products/): We add labels for the top-level product folder, which helps writers scan incoming pull requests and see which are relevant to them.
 - [Label size](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-size/): We add labels for the size of the pull request, which helps writers see the relative size of the difference. It's not a perfect measure, but we use the lines changed to estimate the size of the pull request:
 
-	<GitHubCode
-		repo="cloudflare/cloudflare-docs"
-		file=".github/actions/label-size/index.ts"
-		commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
-		lines="20-36"
-		lang="ts"
-		code={{ title: "label-size.ts" }}
-	/>
+  <GitHubCode
+  	repo="cloudflare/cloudflare-docs"
+  	file=".github/actions/label-size/index.ts"
+  	commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
+  	lines="20-36"
+  	lang="ts"
+  	code={{ title: "label-size.ts" }}
+  />
 
 - [Assign codeowners](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/assign-pr): We use our [CODEOWNERS](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/CODEOWNERS) file to automatically assign people to pull requests based on the files changed. This assignment helps writers scan and filter to see which pull requests are relevant to them.
 
@@ -42,7 +42,6 @@ For issues, we use a similar [GitHub action](https://github.com/cloudflare/cloud
 
 Our [script](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/issue-label-assign) treats issues because usually they contain links to our site instead of files within the repository. We grab the associated links in the issue description fields and then use those to assign writers (again based on `CODEOWNERS`) and add product labels.
 
-
 ## Streamline reviews
 
 To streamline reviews, we use several automations to help solve common reviewer issues.
@@ -68,7 +67,7 @@ We have a specific part of [CI](https://github.com/cloudflare/cloudflare-docs/bl
 
 ### What changed?
 
-We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub). 
+We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub).
 
 We are in the process of migrating to [Workers Builds](/workers/ci-cd/builds/git-integration/github-integration/), which provides that functionality natively.
 
@@ -104,4 +103,4 @@ This workflow - we hope - balances the needs our of team with a healthy respect
 
 We intentionally avoid the [`stale` workflow](https://github.com/github/docs/blob/main/.github/workflows/stale.yml) that closes pull requests or issues that have been inactive for a specific period of time.
 
-In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
\ No newline at end of file
+In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
diff --git a/src/content/docs/support/contacting-cloudflare-support.mdx b/src/content/docs/support/contacting-cloudflare-support.mdx
index ac84963b72ae9f0..657813bb6f05df5 100644
--- a/src/content/docs/support/contacting-cloudflare-support.mdx
+++ b/src/content/docs/support/contacting-cloudflare-support.mdx
@@ -39,7 +39,7 @@ As a Cloudflare customer, you can contact Cloudflare for support via the communi
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------- | ----------- | ----------- |
 | [Community](https://community.cloudflare.com/)<br/>Join the community to ask basic troubleshooting questions and to view the latest resources (such as tips for resolving common issues and configuration guidance). | Yes        | Yes      | Recommended | Recommended |
 | [Discord](https://discord.cloudflare.com/)<br/>Join the Discord community to ask basic troubleshooting questions (mainly focused on the Developer Platform).                                                         | Yes        | Yes      | Recommended | Recommended |
-| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]        |
+| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]      |
 | **Chat**<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                                                      | Yes        | Yes      | No          | No          |
 | **Emergency Phone** <br/>Use phone support to reach out during emergencies such as site outages or DDoS attacks.                                                                                                     | Yes        | No       | No          | No          |
 
@@ -83,7 +83,12 @@ In both cases, you will also need your **Unique Customer ID** (refer to [Finding
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
+<LinkButton
+	href="https://dash.cloudflare.com/?to=/:account/support"
+	icon="external"
+>
+	Go to Support
+</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -97,7 +102,12 @@ Your Unique Customer ID is required when calling the emergency phone line, regar
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
+<LinkButton
+	href="https://dash.cloudflare.com/?to=/:account/support"
+	icon="external"
+>
+	Go to Support
+</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -131,21 +141,21 @@ To submit a support case, follow these steps:
 5. Enter a detailed summary of the issue you’re experiencing.
 
 6. Complete the case submission fields as completely as possible with the following information. _(**Please note** that missing information will increase the time it takes to resolve your issue and our team may not be able to investigate without enough information. Please review [Gathering information for troubleshooting sites](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) and make sure you include all needed information.)_
-    \- A detailed description of the issue with the following information:
-    - Timestamp (UTC)
-    - ZoneName/ZoneID
-    - Problem frequency
-    - Steps to reproduce the issue, with actual results vs expected results
-      \- Any necessary information for a technical investigation
-    - A description of the actual results vs expected results
-    - Steps to reproduce the issue, with example URLs 
-    - Exact error messages
-    - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
-    - Screenshots
-    - Relevant logs from the origin web server
-    - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
-      \- Priority level, impact to service / production
-      \- Any collaborators whom you wish to be cc'd on the case
+   \- A detailed description of the issue with the following information:
+   - Timestamp (UTC)
+   - ZoneName/ZoneID
+   - Problem frequency
+   - Steps to reproduce the issue, with actual results vs expected results
+     \- Any necessary information for a technical investigation
+   - A description of the actual results vs expected results
+   - Steps to reproduce the issue, with example URLs 
+   - Exact error messages
+   - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
+   - Screenshots
+   - Relevant logs from the origin web server
+   - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
+     \- Priority level, impact to service / production
+     \- Any collaborators whom you wish to be cc'd on the case
 
 7. Click **Submit Case**.
 
diff --git a/src/content/docs/support/index.mdx b/src/content/docs/support/index.mdx
index d6fc7fa654994ef..113e68d713a7601 100644
--- a/src/content/docs/support/index.mdx
+++ b/src/content/docs/support/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
index f4dcbec1ff8594c..318aef05f182daf 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
@@ -15,14 +15,14 @@ When you switch a theme or customise a theme within the WordPress admin panel, t
 
 Automatic Cache Management uses native hooks built into WordPress. The Cloudflare WordPress plugin purges the following cache URLs:
 
-* deleted\_post
-* edit\_post
-* delete\_attachment
-* autoptimize\_action\_cachepurged (for compatibility with the Autoptimize WordPress plugin)
-* switch\_theme
-* customize\_save\_after
-
-***
+- deleted_post
+- edit_post
+- delete_attachment
+- autoptimize_action_cachepurged (for compatibility with the Autoptimize WordPress plugin)
+- switch_theme
+- customize_save_after
+
+---
 
 ## Enable Automatic Cache Management
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
index 9a95b6b8ff0e658..0993a2e99b86ad7 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
@@ -9,7 +9,7 @@ products:
 
 HTTP/2 Server Push allows a website to push content to a browser, without having to wait for the HTML of one page to render first. In conjunction with the concurrency support built into HTTP/2, Server Push is able to dramatically reduce the amount of requests needed to load your website.
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733367/http2-server-push-2.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733367/http2-server-push-2.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-http2_server_push_2.png)
 
@@ -23,12 +23,12 @@ define('CLOUDFLARE_HTTP2_SERVER_PUSH_ACTIVE', true);
 
 You should insert this line above where it says *"/\* That's all, stop editing! Happy blogging. \*/*", like follows:|
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733547/Screen\_Shot\_2017-02-09\_at\_16.09.31.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733547/Screen_Shot_2017-02-09_at_16.09.31.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2017_02_09_at_16_09_31.png)
 
 You should then start to see requests coming in which are initiated through Server Push, for example, in the Network tab of Chrome Development Tools you should see some assets have "Push" as the initiator:
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2016_04_26_at_15_08_59.png)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
index 2f68ed6b392d2da..bd0724c70711abf 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
@@ -11,7 +11,7 @@ Content Management Systems make it easy to create, update, and manage content. H
 
 There are many Cloudflare features that can be used for preventing such attacks, but they can also disrupt normal administrative processes such as logging in or uploading images. With proper configuration, you can protect your site from attacks without losing important functionality.
 
-***
+---
 
 ## Stage One: Improve Site Security
 
@@ -29,13 +29,13 @@ The [WAF Managed Rulesets](/waf/managed-rules/) are pre-configured rulesets that
 
 While the feature to customize these managed rulesets required a paid plan, the [Free Cloudflare Managed Ruleset](https://blog.cloudflare.com/waf-for-everyone/#the-free-cloudflare-managed-ruleset) is automatically deployed on any new Cloudflare zone. This ruleset is specially designed to reduce false positives to a minimum across a very broad range of traffic types. As of today, the ruleset contains the following rules:
 
-* Log4J rules matching payloads in the URI and HTTP headers;
-* Shellshock rules;
-* Rules matching very common WordPress exploits;
+- Log4J rules matching payloads in the URI and HTTP headers;
+- Shellshock rules;
+- Rules matching very common WordPress exploits;
 
 Additionally, you can configure many aspects of the [OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/), including the anomaly threshold, paranoia level, and individual rules. One good practice is to ensure any rules related to XSS and SQL injection are enabled.
 
-***
+---
 
 ## Stage Two: Restore Administrative Functions
 
@@ -56,12 +56,12 @@ Next, you can use this information to create a Skip Rule that excludes only the
 
 It is recommended to make this rule as tightly defined as possible, particularly without the additional protections listed below. While the exact content will be site-specific, some possible fields to use are:
 
-* IP Source Address
-* AS Num
-* Cookie
-* User Agent
+- IP Source Address
+- AS Num
+- Cookie
+- User Agent
 
-Make sure to apply the rule *only* to the admin portion of your CMS. With WordPress for example, you can set a condition like '*URI Path contains /wp-admin/*'.
+Make sure to apply the rule _only_ to the admin portion of your CMS. With WordPress for example, you can set a condition like '_URI Path contains /wp-admin/_'.
 
 Any of these fields can be spoofed, so this is not a security measure on its own. The purpose is to restore administrative functions only to conditions that may need them, while using other tools and features (including strong passwords on your CMS logins!) to secure access.
 
@@ -77,7 +77,7 @@ After this is complete, you will want to create a similar rule for any rulesets
 
 Make sure to set your Skip rules to be at a higher priority than the Execute rules.
 
-***
+---
 
 ## Stage Three: Restrict Access
 
@@ -102,7 +102,7 @@ Do the following:
 3. [Enable mTLS](/ssl/client-certificates/enable-mtls/) by adding the correct host.
 4. In **SSL/TLS** > **Client Certificates**, select **Create mTLS Rule**.
 5. Under **When incoming requests match**, enter a value for the **URI Path** field to narrow the rule scope to the admin section, otherwise you will block your visitors from accessing the public content.
-6. Set the rule to *Block* any requests made to your admin panel if the client certificate is not verified.
+6. Set the rule to _Block_ any requests made to your admin panel if the client certificate is not verified.
 7. Select **Deploy**. This creates a WAF custom rule that checks all requests to the admin section for a valid client certificate.
 
 **Note:** If you have issues getting your certificate to verify, try accessing the page in a private window. If it works, the previous successful TLS state may be cached in your browser.
@@ -113,13 +113,13 @@ Rate limiting rules can help protect your login page from an attacker trying to
 
 Rate Limiting Rules are now available unmetered, on all plans. For more information, refer to the [developer documentation](/waf/rate-limiting-rules/).
 
-***
+---
 
 ## Resources
 
-* [WAF Managed Rules](/waf/managed-rules/)
-* [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
-* [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
-* [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
-* [Client certificates](/ssl/client-certificates/)
-* [Rate limiting rules](/waf/rate-limiting-rules/)
+- [WAF Managed Rules](/waf/managed-rules/)
+- [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
+- [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
+- [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
+- [Client certificates](/ssl/client-certificates/)
+- [Rate limiting rules](/waf/rate-limiting-rules/)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
index 7f619ce81d0c809..a520969018400e2 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Content Management System (CMS) support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
index 72cf2b3808b2ec2..b1a0aaaa794a451 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
@@ -14,16 +14,16 @@ If you are using [Cloudflare's WordPress plugin](/automatic-platform-optimizatio
 
 ![Cloudflare's one-click configuration WordPress plugin.](~/assets/images/support/dash-optimize_wordpress.png)
 
-| **Setting**                            | **Value**                          |
-| -------------------------------------- | ---------------------------------- |
-| Caching level                          | Standard                           |
-| Browser Cache TTL                      | 4 hours                            |
-| Always Online                          | On                                 |
-| Development Mode                       | Disabled                           |
-| IPV6 Compatibility                     | On                                 |
-| WebSockets                             | On                                 |
-| IP Geolocation                         | On                                 |
-| Email Address Obfuscation              | On                                 |
-| Hotlink Protection                     | Off                                |
-| Image optimization (Polish)            | Off (unless on Pro or higher plan) |
-| Rocket Loader                          | Off                                |
+| **Setting**                 | **Value**                          |
+| --------------------------- | ---------------------------------- |
+| Caching level               | Standard                           |
+| Browser Cache TTL           | 4 hours                            |
+| Always Online               | On                                 |
+| Development Mode            | Disabled                           |
+| IPV6 Compatibility          | On                                 |
+| WebSockets                  | On                                 |
+| IP Geolocation              | On                                 |
+| Email Address Obfuscation   | On                                 |
+| Hotlink Protection          | Off                                |
+| Image optimization (Polish) | Off (unless on Pro or higher plan) |
+| Rocket Loader               | Off                                |
diff --git a/src/content/docs/support/third-party-software/forum-software/index.mdx b/src/content/docs/support/third-party-software/forum-software/index.mdx
index 6b8e3da66053d73..a3bd9f78a0ca9a2 100644
--- a/src/content/docs/support/third-party-software/forum-software/index.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Forum Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
index 1b3e0496d4d3820..0669bac8222e466 100644
--- a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
@@ -13,14 +13,14 @@ Many widely used forum platforms are compatible with Cloudflare.
 
 These include:
 
-* [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
-* vBulletin
-* Xenforo
-* MyBB
+- [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
+- vBulletin
+- Xenforo
+- MyBB
 
 If you have a forum using these platforms, you can increase its speed and safety by adding Cloudflare.
 
-***
+---
 
 ## Steps
 
diff --git a/src/content/docs/support/third-party-software/index.mdx b/src/content/docs/support/third-party-software/index.mdx
index b79e7fe82f69cfc..64ef43df834abe9 100644
--- a/src/content/docs/support/third-party-software/index.mdx
+++ b/src/content/docs/support/third-party-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Third-Party Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/index.mdx b/src/content/docs/support/third-party-software/others/index.mdx
index 70b8ce2974da5f2..d253e19c2efccb6 100644
--- a/src/content/docs/support/third-party-software/others/index.mdx
+++ b/src/content/docs/support/third-party-software/others/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Others support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
index 4cbb158f3f19295..a32fb2d6902eb8f 100644
--- a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
+++ b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
@@ -13,7 +13,7 @@ Cloudflare launched Bandwidth Alliance in 2018 – a group of forward-looking cl
 
 Cloudflare customers using Azure can lower their egress bills between Cloudflare and Azure via [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/virtual-network/routing-preference-overview).
 
-***
+---
 
 ## How to
 
@@ -31,9 +31,9 @@ To lower your data transfer costs from Azure and Cloudflare: 
 
 For additional details, refer to [Configure network routing preference for Azure Storage](https://docs.microsoft.com/en-us/azure/storage/common/configure-network-routing-preference?tabs=azure-portal) and [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/storage/common/network-routing-preference).
 
-***
+---
 
 ## Related resources
 
-* [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
-* [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
+- [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
+- [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
index 3a30b097d7d9ced..f5af757c7bdc872 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
@@ -26,7 +26,7 @@ This process will allow us to link your account inside our new support system.
 
 If you are a free account customer, you do not have access to this feature, but you can get assistance in many other ways:
 
-* By joining the conversation in our [Community forums](https://community.cloudflare.com/).
-* By joining our [Discord server](https://discord.cloudflare.com/).
-* By checking out our [Documentation](/).
-* By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
+- By joining the conversation in our [Community forums](https://community.cloudflare.com/).
+- By joining our [Discord server](https://discord.cloudflare.com/).
+- By checking out our [Documentation](/).
+- By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
index a1ec1b9e2b99753..2a8ae8a1e746734 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
@@ -23,18 +23,18 @@ customers due to security and liability concerns.
 
 Use this table to quickly identify which troubleshooting method to use based on your issue:
 
-| Issue Type | Recommended Tool | When to Use |
-|------------|------------------|-------------|
-| Page not loading correctly | [HAR file](#generate-a-har-file) | Visual issues, broken elements, slow page loads |
-| JavaScript errors | [Console log](#export-console-log) | CORS errors, scripts failing, browser-side errors |
-| Protocol errors (QUIC/HTTP2) | [NetLog dump](#capture-a-netlog-dump) | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR` |
-| Slow response times | [curl (performance)](#performance) | Measuring latency, TLS handshake times |
-| HTTP errors (5xx, 4xx) | [curl (HTTP errors)](#http-errors) | Determining if errors originate from Cloudflare or origin |
-| Caching issues | [curl (caching)](#caching) | Cache misses, stale content, cache headers |
-| SSL/TLS certificate issues | [curl (SSL/TLS)](#ssltls-certificates) | Certificate errors, TLS version issues |
-| Connection timeouts/drops | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr) | Network path issues, latency between hops |
-| Packet loss, connection resets | [Packet capture](#run-packet-captures) | Layer 3/4 issues, SSL handshake failures |
-| Identifying serving location | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests |
+| Issue Type                     | Recommended Tool                                                                    | When to Use                                               |
+| ------------------------------ | ----------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| Page not loading correctly     | [HAR file](#generate-a-har-file)                                                    | Visual issues, broken elements, slow page loads           |
+| JavaScript errors              | [Console log](#export-console-log)                                                  | CORS errors, scripts failing, browser-side errors         |
+| Protocol errors (QUIC/HTTP2)   | [NetLog dump](#capture-a-netlog-dump)                                               | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR`     |
+| Slow response times            | [curl (performance)](#performance)                                                  | Measuring latency, TLS handshake times                    |
+| HTTP errors (5xx, 4xx)         | [curl (HTTP errors)](#http-errors)                                                  | Determining if errors originate from Cloudflare or origin |
+| Caching issues                 | [curl (caching)](#caching)                                                          | Cache misses, stale content, cache headers                |
+| SSL/TLS certificate issues     | [curl (SSL/TLS)](#ssltls-certificates)                                              | Certificate errors, TLS version issues                    |
+| Connection timeouts/drops      | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr)                         | Network path issues, latency between hops                 |
+| Packet loss, connection resets | [Packet capture](#run-packet-captures)                                              | Layer 3/4 issues, SSL handshake failures                  |
+| Identifying serving location   | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests        |
 
 ---
 
@@ -53,7 +53,7 @@ A HTTP Archive (HAR) records all web browser requests including the request and
 :::caution
 
 A HAR file can include sensitive details such as passwords, payment
-information, and private keys. 
+information, and private keys.
 
 Remove sensitive information using a [HAR Sanitizer](https://har-sanitizer.pages.dev/).
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
index 2d097e0a9229ebd..75fdc9854918fee 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
@@ -6,6 +6,6 @@ products:
   - support
 ---
 
-Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability. 
+Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability.
 
 In instances where performance and reliability are in conflict, our systems are designed to prioritize a stable connection over a local one.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
index 058aa4d051dd35b..256522df2decdc4 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for General Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
index acc27ba05615fa5..738bb5db1983575 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
@@ -8,18 +8,18 @@ products:
 
 This article may help if you are unable to receive transactional emails from Cloudflare. These types of email include:
 
-* email verification
-* forgot / reset password
-* any other type of automated notification generated by the Cloudflare dashboard
+- email verification
+- forgot / reset password
+- any other type of automated notification generated by the Cloudflare dashboard
 
 If you are expecting but not receiving these emails from Cloudflare, review the following.
 
 ## Causes
 
-* Your email address is incorrect or mistyped in the Cloudflare dashboard
-* Your email server or mailbox is not working
-* Your mail server or software is filtering or blocking messages from Cloudflare
-* Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
+- Your email address is incorrect or mistyped in the Cloudflare dashboard
+- Your email server or mailbox is not working
+- Your mail server or software is filtering or blocking messages from Cloudflare
+- Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
 
 ## Solution
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
index 3a81d5514edb8f9..d7bbd6cd5dbd72d 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
@@ -6,17 +6,17 @@ products:
   - support
 ---
 
-Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare. 
+Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare.
 
 This appears to restrict data transfer to approximately 16 KB per connection, which renders most websites, including those of our customers, inaccessible or unusable for visitors from Russia.
 
 What to expect with your website:
 
-- This is not due to a misconfiguration of your Cloudflare settings. 
+- This is not due to a misconfiguration of your Cloudflare settings.
 - You will likely see a significant drop in traffic from users in Russia in your Cloudflare Analytics.
 - Your visitors in Russia may experience connection failures or sites that do not load properly.
-- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users. 
+- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users.
 
 If you are a Cloudflare enterprise customer, contact your account team for further assistance.
 
-For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/). 
\ No newline at end of file
+For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/).
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
index 37ece0e92f767e7..eeef01c3bebc4e4 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
@@ -30,15 +30,15 @@ F5 session cookies can have arbitrary names but typically follow a specific form
 
 - Without encryption (trivially decoded to show origin server IP and port):
 
-   ```txt
-   BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
-   ```
+  ```txt
+  BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
+  ```
 
 - With encryption:
 
-   ```txt
-   BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
-   ```
+  ```txt
+  BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
+  ```
 
 #### 2. Test for the issue
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
index 78c13a35999c2b2..e47931dd17c1429 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
@@ -9,46 +9,46 @@ products:
 
 Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
 
-***
+---
 
 ## Disable Anti-bot modules
 
 Search engine crawlers' requests, when proxied through Cloudflare, can be blocked by anti-bot modules installed on your origin server. Try disabling any anti-bot modules to prevent your origin from blocking these requests.
 
-***
+---
 
 ## Adjust Google and Bing crawl rates
 
 To optimize CDN performance, Google and Bing assign special crawl rates to websites that use CDN services in order. Special crawl rates do not negatively affect Search Engine Optimization (SEO) and Search Engine Results Pages (SERPs). To change your crawl rates for Bing and Google, follow the guides below:
 
-* Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
-* Change your Bing crawl rate via guidance from Bing’s documentation:
-  * [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
-  * [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
+- Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
+- Change your Bing crawl rate via guidance from Bing’s documentation:
+  - [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
+  - [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
 
-***
+---
 
 ## Prevent crawl errors
 
 Review the following recommendations to prevent crawler errors:
 
-* Monitor the performance and availability of your website using a third-party tool:
-  * [StatusCake](http://www.statuscake.com/)
-  * [Pingdom](http://www.pingdom.com/)
-  * [Monitor.Us](http://www.monitor.us/)
-  * [Updown](https://updown.io/)
+- Monitor the performance and availability of your website using a third-party tool:
+  - [StatusCake](http://www.statuscake.com/)
+  - [Pingdom](http://www.pingdom.com/)
+  - [Monitor.Us](http://www.monitor.us/)
+  - [Updown](https://updown.io/)
 
-* Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
+- Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
 
   Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
 
-* Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
+- Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
 
-* Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
+- Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
 
 Google uses a [variety of User-Agents](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers) to crawl your website. You can [test your `robots.txt` via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
 
-* Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
+- Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
 
 `Disallow: /cdn-cgi/`
 
@@ -57,10 +57,10 @@ Google uses a [variety of User-Agents](https://developers.google.com/search/docs
 Errors for `cdn-cgi` do not impact site rankings.
 :::
 
-* Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
-* [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
+- Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943).
+- [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
 
-***
+---
 
 ## Troubleshoot crawl errors
 
@@ -107,7 +107,7 @@ If the above troubleshooting steps do not resolve your crawl errors, follow the
 3. Click **Download** to export the list of errors as a `.csv` file.
 4. Provide the downloaded `.csv` file to Cloudflare support.
 
-***
+---
 
 ## Related resources
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
index f5f8373a02c6fde..fd1f90255a9adde 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
@@ -15,7 +15,7 @@ For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
 
 ### Common use cases
 
-A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. 
+A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing.
 For example:
 
 - If the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
index 6f67fbca6e007e6..b62f398bfdbf194 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
@@ -21,4 +21,4 @@ If the client resends the request with the same credentials and the challenge re
 
 ### Cloudflare-specific information
 
-When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
\ No newline at end of file
+When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
index dc315ae8a719b89..5ab48647ac86db3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
@@ -19,4 +19,4 @@ For example, if a client requests content in a specific language or character se
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
\ No newline at end of file
+Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
index 8083045fa4bc840..dd4f38c4aa51099 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
@@ -18,4 +18,4 @@ This error typically occurs in environments where a proxy server is used as an i
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
\ No newline at end of file
+Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
index 5b3115cc744996f..f2e5da4a9064ce3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
@@ -21,4 +21,4 @@ This error typically occurs when a client fails to send a complete request withi
 
 If a `408` error occurs on a Cloudflare-powered site, it is most often being proxied from the origin. In these cases, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly.
 
-Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
\ No newline at end of file
+Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
index 87e414554c0bf55..c0098ba91b387b4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
@@ -22,4 +22,4 @@ This error typically happens with a `PUT` request when multiple clients are atte
 
 ### Cloudflare-specific information
 
-Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
\ No newline at end of file
+Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
index efdb6f72bdc5fe1..17e6ee5ff4d269a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
@@ -23,4 +23,4 @@ This status is commonly applied to deprecated content, such as outdated pages or
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
+Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
index 2bbf1fafa9e5767..47fe8d6954c39bd 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
@@ -19,4 +19,4 @@ This status code can occur in various scenarios, such as when a client sends an
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
+Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
index 6c46a3195a74a9e..11efe2add1f92d6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
@@ -19,4 +19,4 @@ One common use case for the `412 Precondition Failed` status code is version con
 
 ### Cloudflare-specific information
 
-Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
\ No newline at end of file
+Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
index df0769a0b4bfd44..effc3539c4d9e6a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
@@ -27,4 +27,4 @@ The upload limit for the Cloudflare API depends on your plan. If you exceed this
 
 Keep in mind, customers can reduce the **Maximum Upload Size** from the zone's **Network** page which can cause a `413`.
 
-If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
\ No newline at end of file
+If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
index d27ba07b657f86b..c6b7876ce046cf3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
@@ -19,4 +19,4 @@ For example, if a client is attempting a `GET` request with an unusually long UR
 
 ### Cloudflare-specific information
 
-Cloudflare will generate a `414` response if the URI length exceeds 32KB.
\ No newline at end of file
+Cloudflare will generate a `414` response if the URI length exceeds 32KB.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
index 62c07d24e2e5251..bf00d11dff44238 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
@@ -19,4 +19,4 @@ This error can happen when a client requests a byte range outside the bounds of
 
 ### Cloudflare-specific information
 
-Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
\ No newline at end of file
+Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
index 5ad66dd00072ced..711500dca7e9bae 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
@@ -19,4 +19,4 @@ Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify
 
 ### Cloudflare-specific information
 
-Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
\ No newline at end of file
+Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
index 995be774a343c75..7d4d40af9d2bd76 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
@@ -32,4 +32,3 @@ Cloudflare applies rate limiting to requests for R2 managed public buckets acces
 #### Website end users
 
 Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
index 4d7d15261e11b47..7a3792b883d662c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
@@ -19,4 +19,4 @@ This occurs when access to a resource is blocked due to court orders, copyright
 
 ### Cloudflare-specific information
 
-Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
\ No newline at end of file
+Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
index d9e3fe99f491207..c2a6601666766b7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
@@ -15,7 +15,7 @@ products:
 
 ## Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), which can be useful to investigate HTTP Errors.
 
@@ -27,7 +27,6 @@ For a complete description of this error refer to the [Error 400](/support/troub
 
 For a complete description of this error refer to the [Error 401](/support/troubleshooting/http-status-codes/4xx-client-error/error-401/) page.
 
-
 ## 402 Payment Required
 
 The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231).
@@ -36,7 +35,6 @@ The `402 Payment Required` status code is reserved for future use and is not yet
 
 For a complete description of this error refer to the [Error 403](/support/troubleshooting/http-status-codes/4xx-client-error/error-403/) page.
 
-
 ## 404 Not Found
 
 For a complete description of this error refer to the [Error 404](/support/troubleshooting/http-status-codes/4xx-client-error/error-404/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
index 36deca809c49e5c..18167b8092b1b9b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
@@ -20,4 +20,4 @@ This error occurs when there are duplicate list items in a single operation to a
 
 ### Resolution
 
-You need to remove the duplicate item and try again.
\ No newline at end of file
+You need to remove the duplicate item and try again.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
index ec68460a428d719..107785e0dccf2ec 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
@@ -20,4 +20,4 @@ This error occurs when the source URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the source URL.
\ No newline at end of file
+You need to use a shorter URL as the source URL.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
index 687c3022a1391f4..c5307d8789975fb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
@@ -20,4 +20,4 @@ This error occurs when the target URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the target URL.
\ No newline at end of file
+You need to use a shorter URL as the target URL.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
index 16221ebbff83170..e061d57515adeb3 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
index 263401952d5dc31..16897ff09f53dfb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
\ No newline at end of file
+You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
index ba1cd6d9d14c953..1bc04c5dadad755 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
@@ -17,4 +17,4 @@ This error occurs when you specify a URL redirect status code that is not suppor
 
 ### Resolution
 
-Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
\ No newline at end of file
+Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
index 5d066ea9c0d5f2c..a68813f6502ebc5 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve path suffix** option in a redir
 
 ### Resolution
 
-Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
\ No newline at end of file
+Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
index 343a60e375b1269..085dc2ea7f596d2 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect has an invalid scheme, w
 
 ### Resolution
 
-Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
index e037df5b8d6fdca..172b34e6b076576 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a user info com
 
 ### Resolution
 
-You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
index e4399c78df33671..a7ea0e0f82e50c6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect does not include an auth
 
 ### Resolution
 
-Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
\ No newline at end of file
+Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
index 36d65f8b2d2d541..371faef69c84269 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a port (for exa
 
 ### Resolution
 
-Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
+Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
index 4cacdc75502b532..c0c9c3440aa4398 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve query string** option of a URL
 
 ### Resolution
 
-To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
\ No newline at end of file
+To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
index d6b879890b89165..1198b1552a6e89e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
@@ -20,4 +20,4 @@ This error occurs when different types of list items (such as IP addresses, host
 Remove the list items that do not apply to the list type. This means:
 
 - Removing IP addresses from a request to add items to a Bulk Redirect List.
-- Removing URL redirects from a request to add items to an IP list.
\ No newline at end of file
+- Removing URL redirects from a request to add items to an IP list.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
index 158e45e84a4d659..6c39cf94fee9dc4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
@@ -21,4 +21,4 @@ Make sure you are adding the items to the correct list:
 
 - Custom lists with IP addresses (IP lists) can only contain IP addresses as list items.
 - Custom lists with hostnames can only contain hostnames as list items.
-- Bulk Redirect Lists can only contain URL redirects as list items.
\ No newline at end of file
+- Bulk Redirect Lists can only contain URL redirects as list items.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
index 37a293ffd69b91e..7d137ba67522622 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
@@ -17,4 +17,4 @@ This error occurs when you have more than the maximum number of URL redirects wi
 
 ### Resolution
 
-Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
\ No newline at end of file
+Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
index eb841ff74628814..617ad8ff0c6f421 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL of a URL redirect does not include a schem
 
 ### Resolution
 
-Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
\ No newline at end of file
+Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
index c47d1c3dccc0286..1b97c64adc8da93 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
@@ -76,4 +76,4 @@ For a complete description of this error refer to the [Error 10059](/support/tro
 
 ## Error 10060: Missing scheme in redirect target URL
 
-For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
\ No newline at end of file
+For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
index ed56fe2d03d4b5c..23d789e3acc15d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
@@ -27,4 +27,4 @@ Cloudflare halted the request for one of the following reasons:
 
 - If an A record within your Cloudflare DNS app points to a [Cloudflare IP address](https://www.cloudflare.com/ips/), update the IP address to your origin web server IP address. Reach out to your hosting provider if you need help obtaining the origin IP address.
 - There is a reverse-proxy at your origin that sends the request back through the Cloudflare proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.
-- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
\ No newline at end of file
+- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
index ccc795620204019..2c3f226dc6e792c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
@@ -1,13 +1,13 @@
 ---
 pcx_content_type: troubleshooting
-title: Error 1002 
+title: Error 1002
 source: null
 description: Troubleshoot Cloudflare 1002 error code.
 products:
   - support
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 ## Error 1002: DNS points to Prohibited IP
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
index e1345953169f933..23dc25e82509737 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
@@ -19,4 +19,3 @@ This error indicates that the host is not configured to serve web traffic.
 ### Resolution
 
 If the issue persists beyond five minutes, [contact Cloudflare Support](/support/contacting-cloudflare-support/).
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
index 0927129b5cce7e1..3f1e6d6819b72b2 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
@@ -19,4 +19,3 @@ The owner of the website (for example, `example.com`) has banned the country or
 
 - If you are a site visitor, contact the site owner and ask them to allow your IP address.
 - If you are the site owner, ensure that the reported IP address is allowed under the [IP Access rules](/waf/tools/ip-access-rules/) security feature.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
index 1f107b8f72b7f05..8c178fd7a6ca6f1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
@@ -22,6 +22,5 @@ Another common cause is connecting a custom domain to an R2 bucket, where the do
 - To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/).
 - To allow connecting to a R2 bucket with a custom domain, disable the [zone hold](/fundamentals/account/account-security/zone-holds/) feature on the custom domain target zone to resolve the 1014 error.
 - To allow connections to an R2 bucket whose zone is banned:
-
   - First, check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one).
   - Second, make sure that you have no unpaid invoice(s), as you will not be able to enable any new services until [any outstanding balance](/billing/manage/pay-invoices-overdue-balances/) is addressed. If this does not resolve the issue, contact your account team.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
index 9b401eee437c5d7..27a7f8ca892a5ae 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
@@ -27,4 +27,4 @@ For example, the following URI path rewrite expression is not valid:
 
 To fix the expression above, add a `/` prefix:
 
-`concat("/", lower(ip.src.country), http.request.uri.path)`
\ No newline at end of file
+`concat("/", lower(ip.src.country), http.request.uri.path)`
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
index 8ca43a2009913cf..a07128b006e1a78 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
@@ -18,4 +18,3 @@ You are trying to modify an HTTP header that Request Header Transform Rules cann
 ### Resolution
 
 Make sure you are not trying to modify one of the [reserved HTTP request headers](/rules/transform/request-header-modification/#important-remarks).
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
index 1468ee4c28b0408..ca8eb720fb9b8ca 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
@@ -57,4 +57,3 @@ To avoid exceeding memory limits:
 
 - [Error 1101](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1101/) - Workers JavaScript runtime exception
 - [Error 503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503/) - Service temporarily unavailable (can be caused by Workers CPU or memory limits)
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
index a31eb60f8fa2f99..064d799dd10135c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
@@ -32,7 +32,6 @@ For a complete description of this error refer to the [Error 1000](/support/trou
 
 For a complete description of this error refer to the [Error 1001](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/) page.
 
-
 ## Error 1002: DNS points to Prohibited IP
 
 For a complete description of this error refer to the [Error 1002: DNS points to Prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002/#error-1002-dns-points-to-prohibited-ip) page.
@@ -85,12 +84,10 @@ For a complete description of this error refer to the [Error 1014](/support/trou
 
 For a complete description of this error refer to the [Error 1015](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1015/) page.
 
-
 ## Error 1016: Origin DNS error
 
 For a complete description of this error refer to the [Error 1016](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016/) page.
 
-
 ## Error 1018: Could not find host
 
 For a complete description of this error refer to the [Error 1018](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1018/) page.
@@ -154,4 +151,3 @@ For a complete description of this error refer to the [Error 1104](/support/trou
 ## Error 1200: Cache connection limit
 
 For a complete description of this error refer to the [Error 1200](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1200/) page.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
index 137fd47bdd00bcb..aa184c991eb318f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
@@ -18,4 +18,4 @@ Cloudflare Workers returns a `501` error when a request uses an HTTP method that
 
 ### Resolution
 
-- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
\ No newline at end of file
+- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
index f03079632ed610b..4f5ba4cb59b6c1d 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
@@ -52,10 +52,10 @@ If you are using Workers, check the Workers dashboard for error logs and resourc
 
 Use the error page content to determine whether a 503 was generated by Cloudflare or your origin server:
 
-| Signal | Interpretation |
-|--------|---------------|
-| Error page HTML contains `cloudflare` or `cloudflare-nginx` | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
-| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly |
+| Signal                                                              | Interpretation                                                                                                                     |
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| Error page HTML contains `cloudflare` or `cloudflare-nginx`         | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
+| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly                                                                                             |
 
 ### Cloudflare-generated 503
 
@@ -64,4 +64,3 @@ A Cloudflare-generated 503 indicates a connectivity issue in a Cloudflare data c
 ### Origin-generated 503
 
 If your origin generated a 503, check origin server logs for signs of overload: CPU/memory saturation, exhausted connection pool, or application-level maintenance mode.
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
index 1ce4d0ddda9a4a1..c5e17a3afac58f5 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
@@ -68,4 +68,3 @@ To distinguish between the two, check the `CacheStatus` field in the same log re
 Do not conclude your origin returned a 5xx error solely because `OriginResponseStatus = 0`. Always check `CacheStatus` first to determine whether Cloudflare contacted the origin at all.
 
 :::
-
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
index 1759ae0d321392e..a49d78dbb7cbe12 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
@@ -21,7 +21,6 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 ### Resolution
 
 - Contact your hosting provider and share the [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist in troubleshooting these common causes:
-
   - [Cloudflare IP addresses](https://www.cloudflare.com/ips/) are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider allows **all Cloudflare IP ranges** (most common cause). You can use a [Cloudflare WAF Custom Rule](/waf/custom-rules/use-cases/block-by-geographical-location/) if you need to restrict traffic from geographical locations.
   - An overloaded or offline origin web server drops incoming requests.
   - [Keepalives](http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html) are disabled at the origin web server.
@@ -32,9 +31,8 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 
 - If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a `522` error. Consider using a [Route](/workers/configuration/routing/), targeting another hostname, or enabling the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) instead.
 
-- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`. 
+- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`.
 
 - If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before [contacting Cloudflare support](/support/contacting-cloudflare-support/):
-
   - An [MTR or traceroute](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#perform-a-traceroute) from your origin web server to a [Cloudflare IP address](http://www.cloudflare.com/ips) that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
   - Details from the hosting provider's investigation, such as pertinent logs or conversations with the hosting provider.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
index b67257eb3168ed7..b075caaba321bfa 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
@@ -18,7 +18,6 @@ The error `524` occurs if the origin web server acknowledges (ACK) the resource
 
 Error `524` can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/) (or 6.5 seconds in the case of [Cloudflare Images](/images/)). This timeout cannot be adjusted.
 
-
 ### Resolution at your origin
 
 Here are the options we suggest to work around this issue:
@@ -31,7 +30,7 @@ Here are the options we suggest to work around this issue:
 
 :::note
 
-Logging request response time at your origin web server may help identify the cause of resource slowness. 
+Logging request response time at your origin web server may help identify the cause of resource slowness.
 Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as [Apache](http://httpd.apache.org/docs/current/mod/mod_log_config.html) or [Nginx](http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format).
 :::
 
@@ -42,7 +41,7 @@ Here are some other actions you can take on the Cloudflare side:
 - If you regularly run HTTP requests that take over 120 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
 - Enterprise customers can increase the `524` timeout up to 6,000 seconds:
   - If your content can be cached, you can create a [Cache Rule](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only) with the `Proxy Read Timeout` setting. The content needs to be cacheable for the rule to be triggered, but does not need to be cached.
-  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/). 
+  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/).
 
 :::note
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
index 5278dcbd17ebc5f..1e57ec517869150 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
@@ -43,4 +43,4 @@ If `525` errors occur intermittently, review the origin web server error logs to
 
 - [Review the cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/) used by your server to ensure they are compatible with Cloudflare.
 
-- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
\ No newline at end of file
+- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
index d438cc1893edcbb..1bd602ef3df5764 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
@@ -46,7 +46,7 @@ To view Error Analytics:
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific Ray ID, which can be useful to investigate HTTP Errors.
 
@@ -72,7 +72,6 @@ For a complete description of this error refer to the [Error 503](/support/troub
 
 For a complete description of this error refer to the [Error 520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) page.
 
-
 ## Error 521: web server is down
 
 For a complete description of this error refer to the [Error 521](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) page.
@@ -85,17 +84,14 @@ For a complete description of this error refer to the [Error 522](/support/troub
 
 For a complete description of this error refer to the [Error 523](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) page.
 
-
 ## Error 524: a timeout occurred
 
 For a complete description of this error refer to the [Error 524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) page.
 
-
 ## Error 525: SSL handshake failed
 
 For a complete description of this error refer to the [Error 525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/) page.
 
-
 ## Error 526: invalid SSL certificate
 
 For a complete description of this error refer to the [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
index f0c29b1fb117d8a..ec947473bacdc11 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
@@ -28,9 +28,8 @@ Reproduce the error and inspect response headers using one of:
 
 ## Using cf-error-type for diagnosis
 
-| `cf-error-type` prefix | Origin | Next step |
-|---|---|---|
-| `1xxx` | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
-| `1101` / `1102` | Workers runtime | Check `wrangler tail` for the exception |
-| `52x` | Origin connectivity | Check origin server is up and reachable |
-
+| `cf-error-type` prefix | Origin              | Next step                                              |
+| ---------------------- | ------------------- | ------------------------------------------------------ |
+| `1xxx`                 | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
+| `1101` / `1102`        | Workers runtime     | Check `wrangler tail` for the exception                |
+| `52x`                  | Origin connectivity | Check origin server is up and reachable                |
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
index 01c72d0bc87c34f..6c1c9d2be8a69d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for HTTP Status Codes support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/index.mdx
index d81e4565fde34b9..03006375415d51d 100644
--- a/src/content/docs/support/troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
index 3594cec54c60318..09b614cc99e93e2 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Below you will find links to the relevant sections for Restoring Visitor IPs support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
index dd9d3148e61c91c..e1a34f3e2f2c079 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
@@ -216,7 +216,7 @@ Use the [`ngx_http_realip_module` Nginx module](http://nginx.org/en/docs/http/ng
 
 ```
 #example IP address
-set_real_ip_from 192.0.2.1; 
+set_real_ip_from 192.0.2.1;
 
 #use any of the following two
 
@@ -463,6 +463,7 @@ For more details, refer to [Custom header original IP detection extension](https
 If you are running an application behind [Caddy](https://caddyserver.com/) that relies on the `X-Forwarded-For` header, you can configure Caddy to override the header with Cloudflare's [CF-Connecting-IP header](/fundamentals/reference/http-headers/#cf-connecting-ip).
 
 It is advised that you also only accept traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/); otherwise, the header could be spoofed. That's why, in the second example, we handle this as part of the Caddy configuration. Alternatively, you can handle this at the firewall level, which is usually easier to automate. If you already have a firewall or other measure in place to ensure this, your Caddyfile could look like this:
+
 ```txt title="Caddyfile"
 https://example.com {
     reverse_proxy localhost:8080 {
@@ -473,6 +474,7 @@ https://example.com {
 ```
 
 If you want Caddy to handle only accepting traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/), you can use a configuration like this one:
+
 ```txt title="Caddyfile"
 https://example.com {
     # Restrict access to Cloudflare IPs (https://www.cloudflare.com/ips/)
@@ -494,6 +496,7 @@ https://example.com {
     }
 }
 ```
+
 ---
 
 ## Related Resources
diff --git a/src/content/docs/tenant/how-to/index.mdx b/src/content/docs/tenant/how-to/index.mdx
index 036aa6d32db9c09..5b478d437d47b4b 100644
--- a/src/content/docs/tenant/how-to/index.mdx
+++ b/src/content/docs/tenant/how-to/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/tenant/index.mdx b/src/content/docs/tenant/index.mdx
index f669fc53278a372..a9bea30e67a18fc 100644
--- a/src/content/docs/tenant/index.mdx
+++ b/src/content/docs/tenant/index.mdx
@@ -19,7 +19,7 @@ These APIs are built into our Client v4 API library to provide a streamlined onb
 
 As you dive into the Tenant API, take advantage of the following resources:
 
-* [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
-* [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
-* [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
-* [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
+- [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
+- [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
+- [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
+- [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
diff --git a/src/content/docs/tenant/reference/index.mdx b/src/content/docs/tenant/reference/index.mdx
index ed9d4e28bbe4895..cc579a35dcc72f4 100644
--- a/src/content/docs/tenant/reference/index.mdx
+++ b/src/content/docs/tenant/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/terraform/advanced-topics/best-practices.mdx b/src/content/docs/terraform/advanced-topics/best-practices.mdx
index e3dd89c7e78f2e0..8bc08838c5a7125 100644
--- a/src/content/docs/terraform/advanced-topics/best-practices.mdx
+++ b/src/content/docs/terraform/advanced-topics/best-practices.mdx
@@ -189,10 +189,8 @@ Using modules also increases the difficulty of debugging or reproducing issues a
 
 :::caution
 
-
 This advice also applies to [Terraform dynamic blocks](https://www.terraform.io/language/expressions/dynamic-blocks) that allow you to do logic in your HCL. Since these dynamic blocks are always evaluated, you can get yourself into situations where you have logic bugs in your configuration (and making the end result unreproducible).
 
-
 :::
 
 ## Migrate resources into Terraform
diff --git a/src/content/docs/terraform/how-to/create-partial-zone.mdx b/src/content/docs/terraform/how-to/create-partial-zone.mdx
index 7ddc5bbf8335cb9..b6532b8ca83d6a4 100644
--- a/src/content/docs/terraform/how-to/create-partial-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-partial-zone.mdx
@@ -39,6 +39,7 @@ resource "cloudflare_zone" "subdomain_example_com" {
 ```
 
 Then, in a new Terraform plan and apply cycle, upgrade the zone to a Business plan or higher:
+
 ```hcl
 resource "cloudflare_zone_subscription" "example_zone_subscription" {
   zone_id = cloudflare_zone.subdomain_example_com.id
@@ -72,4 +73,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Partial zone setup](/dns/zone-setups/partial-setup/)
 - [Convert a full zone to partial](/dns/zone-setups/conversions/convert-full-to-partial/)
-- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
\ No newline at end of file
+- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
diff --git a/src/content/docs/terraform/how-to/create-secondary-zone.mdx b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
index df90ad68810ec8a..ab90c9a7bf683c7 100644
--- a/src/content/docs/terraform/how-to/create-secondary-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
@@ -13,7 +13,9 @@ products:
 ---
 
 A [subdomain zone](/dns/zone-setups/subdomain-setup/) lets you manage a subdomain in a separate Cloudflare zone from the parent domain. This is useful for access control and team management. This guide shows how to automate the setup using the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs). It is only available for Enterprise accounts
+
 > NOTE: subdomain setup is only available for Enterprise accounts
+
 ## Prerequisites
 
 - Terraform installed. Refer to [Get started](/terraform/installing/).
@@ -43,4 +45,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Subdomain setup](/dns/zone-setups/subdomain-setup/)
 - [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
-- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
\ No newline at end of file
+- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
diff --git a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
index 2ab6af754503c16..4fe8686bb0585da 100644
--- a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
+++ b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
@@ -24,4 +24,4 @@ Use this:
 
 ```txt "zones[0]"
 zone_id = data.cloudflare_zones.example_com.zones[0].id`
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/terraform/tutorial/index.mdx b/src/content/docs/terraform/tutorial/index.mdx
index 9eb9b90d3aaf527..0a16482753a93c7 100644
--- a/src/content/docs/terraform/tutorial/index.mdx
+++ b/src/content/docs/terraform/tutorial/index.mdx
@@ -10,41 +10,41 @@ products:
 
 Before you begin, [install Terraform](/terraform/installing/). Each tutorial builds on the previous, so you should complete the tutorials in the order shown below.
 
-:::note 
+:::note
 If you are upgrading from v4, review the [migration guide](https://github.com/cloudflare/terraform-provider-cloudflare/blob/main/docs/guides/version-5-upgrade.md) for breaking changes.
 :::
 
 ## [1 – Initialize Terraform](/terraform/tutorial/initialize-terraform/)
 
-* Brief introduction.
-* Introduction of `terraform init`, `plan`, `apply`, and `show`.
-* Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
+- Brief introduction.
+- Introduction of `terraform init`, `plan`, `apply`, and `show`.
+- Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
 
 ## [2 – Track your history](/terraform/tutorial/track-history/)
 
-* Store Cloudflare configuration in source control.
+- Store Cloudflare configuration in source control.
 
 ## [3 – Configure HTTPS settings](/terraform/tutorial/configure-https-settings/)
 
-* Modify zone settings.
-* Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
+- Modify zone settings.
+- Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
 
 ## [4 – Improve performance and reliability](/terraform/tutorial/use-load-balancing/)
 
-* Add load balancing rules.
-* Resources covered:
-  * [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
-  * [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
-  * [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
+- Add load balancing rules.
+- Resources covered:
+  - [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
+  - [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
+  - [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
 
 ## [5 – Add exceptions with page rules](/terraform/tutorial/add-page-rules/)
 
-* Add page rule.
-* Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
-* Increase security level for a specific URL: `/expensive-db-call`.
-* Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
+- Add page rule.
+- Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
+- Increase security level for a specific URL: `/expensive-db-call`.
+- Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
 
 ## [6 – Revert configuration](/terraform/tutorial/revert-configuration/)
 
-* Review change history.
-* Roll back changes.
+- Review change history.
+- Roll back changes.
diff --git a/src/content/docs/time-services/index.mdx b/src/content/docs/time-services/index.mdx
index 28cf018d1d9c55a..e0533cac714f018 100644
--- a/src/content/docs/time-services/index.mdx
+++ b/src/content/docs/time-services/index.mdx
@@ -12,7 +12,7 @@ products:
 description: Synchronize time with Cloudflare NTP, NTS, and Roughtime.
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Learn more about Cloudflare’s suite of time services.
 
diff --git a/src/content/docs/time-services/roughtime/index.mdx b/src/content/docs/time-services/roughtime/index.mdx
index c63fcd5c61e6ed3..fa744d4dd0b4954 100644
--- a/src/content/docs/time-services/roughtime/index.mdx
+++ b/src/content/docs/time-services/roughtime/index.mdx
@@ -16,7 +16,7 @@ Endpoints on the Internet often synchronize their clocks using the [Network Time
 
 As a result, a man-in-the-middle attacker can easily influence a victim’s clock. By moving them back in time, the attacker can, for example, force a victim to accept an expired (and possibly compromised) TLS certificate or session ticket.
 
-For many applications, *precise* network time is not essential. It is sufficient to have *accurate* time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
+For many applications, _precise_ network time is not essential. It is sufficient to have _accurate_ time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
 
 ## Next steps
 
diff --git a/src/content/docs/time-services/roughtime/recipes.mdx b/src/content/docs/time-services/roughtime/recipes.mdx
index 47cfdd6f2bd8e21..c7873f7d93f6904 100644
--- a/src/content/docs/time-services/roughtime/recipes.mdx
+++ b/src/content/docs/time-services/roughtime/recipes.mdx
@@ -21,28 +21,28 @@ formatted as a JSON object. For example:
 
 ```json
 {
-  "servers": [
-    {
-      "name": "Cloudflare-Roughtime-2",
-      "publicKeyType": "ed25519",
-      "publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
-      "addresses": [
-        {
-          "protocol": "udp",
-          "address": "roughtime.cloudflare.com:2003"
-        }
-      ]
-    }
-  ]
+	"servers": [
+		{
+			"name": "Cloudflare-Roughtime-2",
+			"publicKeyType": "ed25519",
+			"publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
+			"addresses": [
+				{
+					"protocol": "udp",
+					"address": "roughtime.cloudflare.com:2003"
+				}
+			]
+		}
+	]
 }
 ```
 
-It includes each server's *root public key*. When the server starts, it
-generates an *online* public/secret key pair. The root secret key is used to create a *delegation* for the online public key and the online secret key is used to sign the response.
+It includes each server's _root public key_. When the server starts, it
+generates an _online_ public/secret key pair. The root secret key is used to create a _delegation_ for the online public key and the online secret key is used to sign the response.
 
 The delegation serves the same function as a traditional [X.509 certificate](https://en.wikipedia.org/wiki/X.509) on the web. The client first uses the root public key to verify the delegation, then uses the online public key to verify the response.
 
-Because the response is *auditable*, the protocol makes each client accountable to provide accurate time.
+Because the response is _auditable_, the protocol makes each client accountable to provide accurate time.
 
 The configuration also encodes the type of signature algorithm used by the
 server (currently only [Ed25519](https://en.wikipedia.org/wiki/EdDSA) is supported). Lastly, the configuration contains a list of addresses where the service can be reached and which transport protocol to use to reach them (currently only UDP is supported).
diff --git a/src/content/docs/time-services/tos.mdx b/src/content/docs/time-services/tos.mdx
index 919e1a6c1d5e131..3045d87449c98de 100644
--- a/src/content/docs/time-services/tos.mdx
+++ b/src/content/docs/time-services/tos.mdx
@@ -8,4 +8,4 @@ products:
 description: Cloudflare Time Services terms of use.
 ---
 
-By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
\ No newline at end of file
+By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
diff --git a/src/content/docs/tunnel/advanced/origin-parameters.mdx b/src/content/docs/tunnel/advanced/origin-parameters.mdx
index 765569e743882e5..8b0a1173bb017e7 100644
--- a/src/content/docs/tunnel/advanced/origin-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/origin-parameters.mdx
@@ -13,11 +13,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/origin-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
-    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
-  }}
+	file="tunnel/origin-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/tunnel/advanced/local-management/configuration-file/",
+		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+		validatingJwtURL:
+			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
+	}}
 />
diff --git a/src/content/docs/tunnel/advanced/run-parameters.mdx b/src/content/docs/tunnel/advanced/run-parameters.mdx
index 3024141c055de62..61f30d9abf493ba 100644
--- a/src/content/docs/tunnel/advanced/run-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/run-parameters.mdx
@@ -13,15 +13,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-  file="tunnel/run-parameters"
-  product="cloudflare-one"
-  params={{
-    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
-    metricsURL: "/tunnel/monitoring/#metrics",
-    usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
-    tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
-    tunnelPermissionsURL: "/tunnel/advanced/local-management/tunnel-permissions/",
-    createRemoteTunnelURL: "/tunnel/get-started/",
-    faqURL: "/tunnel/troubleshooting/"
-  }}
+	file="tunnel/run-parameters"
+	product="cloudflare-one"
+	params={{
+		configurationFileURL:
+			"/tunnel/advanced/local-management/configuration-file/",
+		metricsURL: "/tunnel/monitoring/#metrics",
+		usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
+		tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
+		tunnelPermissionsURL:
+			"/tunnel/advanced/local-management/tunnel-permissions/",
+		createRemoteTunnelURL: "/tunnel/get-started/",
+		faqURL: "/tunnel/troubleshooting/",
+	}}
 />
diff --git a/src/content/docs/tunnel/changelog.mdx b/src/content/docs/tunnel/changelog.mdx
index 9a0b8f86b225617..dd0771082a7b9ac 100644
--- a/src/content/docs/tunnel/changelog.mdx
+++ b/src/content/docs/tunnel/changelog.mdx
@@ -12,7 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog
-	product="tunnel"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
\ No newline at end of file
+<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
diff --git a/src/content/docs/tunnel/deployment-guides/terraform.mdx b/src/content/docs/tunnel/deployment-guides/terraform.mdx
index 13890c8c111c1c4..cc28a315060b536 100644
--- a/src/content/docs/tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/tunnel/deployment-guides/terraform.mdx
@@ -80,7 +80,6 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
-
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/tunnel/downloads/system-requirements.mdx b/src/content/docs/tunnel/downloads/system-requirements.mdx
index 252a3704e2bda8c..df9a49384ea6c6e 100644
--- a/src/content/docs/tunnel/downloads/system-requirements.mdx
+++ b/src/content/docs/tunnel/downloads/system-requirements.mdx
@@ -17,7 +17,11 @@ import { Render, TunnelCalculator } from "~/components";
 Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availability) on two dedicated hosts per location with a minimum of 4 GB RAM and 4 CPU cores. Allocate 50,000 ports per host.
 
 ## Port configuration
-<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
+
+<Render
+	file="tunnel/availability/port-configuration"
+	product="cloudflare-one"
+/>
 
 ## ulimits (Linux and macOS)
 
@@ -26,6 +30,7 @@ Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availabil
 ## Capacity calculator
 
 To estimate tunnel capacity requirements for your deployment:
+
 1. Use the [metrics endpoint](/tunnel/monitoring/#cloudflared-metrics) to measure `cloudflared_tcp_total_sessions` and `cloudflared_udp_total_sessions`.
 2. Compute the average **TCP requests per second** by dividing `cloudflared_tcp_total_sessions` by total time.
 3. Compute the average **Non-DNS UDP requests per second** by dividing `cloudflared_udp_total_sessions` by total time.
diff --git a/src/content/docs/tunnel/troubleshooting.mdx b/src/content/docs/tunnel/troubleshooting.mdx
index 0c02d1a8ecf4b9a..06fba9a65a218a4 100644
--- a/src/content/docs/tunnel/troubleshooting.mdx
+++ b/src/content/docs/tunnel/troubleshooting.mdx
@@ -121,6 +121,7 @@ As a quick test, run:
 ```sh
 curl -v https://region1.v2.argotunnel.com:7844
 ```
+
 If the connection hangs, traffic is being dropped between your host and Cloudflare.
 
 To test if `cloudflared` can connect on port `7844`, run:
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
index 51b265f76e5f1f0..b2a3eaa4e14958f 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
@@ -7,7 +7,6 @@ products:
 sidebar:
   order: 4
   label: Any Hostname
-
 ---
 
 The Any Hostname feature removes the requirement to specify hostnames during widget creation, allowing widgets to function on any domain.
@@ -24,31 +23,37 @@ When using the Any Hostname feature, it is essential to implement additional val
 
 ```js title="Example response"
 async function validateTurnstileWithHostname(token, expectedHostnames = []) {
-  const response = await fetch('https://challenges.cloudflare.com/turnstile/v0/siteverify', {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/json' },
-    body: JSON.stringify({
-      secret: process.env.TURNSTILE_SECRET,
-      response: token
-    })
-  });
-
-  const result = await response.json();
-
-  if (!result.success) {
-    return { valid: false, error: 'Token validation failed' };
-  }
-
-  // Additional hostname validation when using Any Hostname
-  if (expectedHostnames.length > 0 && !expectedHostnames.includes(result.hostname)) {
-    return { 
-      valid: false, 
-      error: 'Hostname not in allowed list',
-      hostname: result.hostname 
-    };
-  }
-
-  return { valid: true, data: result };
+	const response = await fetch(
+		"https://challenges.cloudflare.com/turnstile/v0/siteverify",
+		{
+			method: "POST",
+			headers: { "Content-Type": "application/json" },
+			body: JSON.stringify({
+				secret: process.env.TURNSTILE_SECRET,
+				response: token,
+			}),
+		},
+	);
+
+	const result = await response.json();
+
+	if (!result.success) {
+		return { valid: false, error: "Token validation failed" };
+	}
+
+	// Additional hostname validation when using Any Hostname
+	if (
+		expectedHostnames.length > 0 &&
+		!expectedHostnames.includes(result.hostname)
+	) {
+		return {
+			valid: false,
+			error: "Hostname not in allowed list",
+			hostname: result.hostname,
+		};
+	}
+
+	return { valid: true, data: result };
 }
 ```
 
@@ -58,10 +63,12 @@ Use `action` and `cData` parameters to track widget usage sources.
 
 ```html
 <!-- Widget with tracking information -->
-<div class="cf-turnstile" 
-     data-sitekey="your-site-key"
-     data-action="customer-portal"
-     data-cdata="tenant-123"></div>
+<div
+	class="cf-turnstile"
+	data-sitekey="your-site-key"
+	data-action="customer-portal"
+	data-cdata="tenant-123"
+></div>
 ```
 
 ---
@@ -73,4 +80,4 @@ The Any Hostname feature is particularly valuable for customers with:
 - Large domain portfolios with many domains to manage individually.
 - Dynamic subdomain creation and frequently create subdomains or customer-specific domains.
 - Multi-tenant applications such as SaaS platforms serving multiple customer domains.
-- Development environments that test across various staging and development domains.
\ No newline at end of file
+- Development environments that test across various staging and development domains.
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
index 2ec95bf7163dc6f..a54d5062f8d33e7 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
@@ -6,10 +6,9 @@ products:
   - turnstile
 sidebar:
   order: 2
-
 ---
 
-import { DashButton, Steps, Tabs, TabItem, Details } from "~/components"
+import { DashButton, Steps, Tabs, TabItem, Details } from "~/components";
 
 Hostname management controls where your Turnstile widgets can be used by specifying which domains are authorized to load and execute your widgets. This security measure prevents unauthorized use of your widgets on domains that you do not control.
 
@@ -36,7 +35,7 @@ The following formats are not valid and will not be accepted:
 - Schemes such as `http://example.com` or `https://example.com`
 - Ports such as `example.com:443` or `subdomain.example.com:8080`
 - Paths such as `example.com/path` or `subdomain.example.com/login`
-:::
+  :::
 
 ### Subdomain behavior
 
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
index eaa623056629f2a..c8b59dade309ca5 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
@@ -8,7 +8,6 @@ tags:
   - Cookies
 sidebar:
   order: 3
-
 ---
 
 [Pre-clearance](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) allows Turnstile to issue clearance cookies that can be used across your Cloudflare-protected domains. This feature requires specific hostname configuration for proper functionality.
@@ -17,18 +16,18 @@ sidebar:
 
 For pre-clearance to work correctly, you must:
 
-1. Use a registered Cloudflare zone. 
+1. Use a registered Cloudflare zone.
+
+   The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones.
+
+2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance.
 
-    The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones. 
+   The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile.
 
-2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance. 
-    
-    The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile. 
-    
-    For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`. 
+   For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`.
 
 ## Validation
 
 The clearance cookie `cf_clearance` will only be accepted on domains that match the widget's configured hostnames, are registered as zones in your Cloudflare account, and have challenges enabled through Cloudflare's security settings.
 
-If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
\ No newline at end of file
+If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
diff --git a/src/content/docs/turnstile/additional-configuration/index.mdx b/src/content/docs/turnstile/additional-configuration/index.mdx
index fa53423d1ca145e..c1dd255c43c229e 100644
--- a/src/content/docs/turnstile/additional-configuration/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile's additional configurations:
 
diff --git a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
index f4882feb0c77f50..ff23f12fc0c683d 100644
--- a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
+++ b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile
 sidebar:
   order: 3
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/turnstile/concepts/challenges.mdx b/src/content/docs/turnstile/concepts/challenges.mdx
index fa67c9f121a081a..2049cf0d9334a17 100644
--- a/src/content/docs/turnstile/concepts/challenges.mdx
+++ b/src/content/docs/turnstile/concepts/challenges.mdx
@@ -7,5 +7,4 @@ products:
 external_link: /cloudflare-challenges/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/turnstile/concepts/index.mdx b/src/content/docs/turnstile/concepts/index.mdx
index 4545231c8047916..f8bdd001acb61db 100644
--- a/src/content/docs/turnstile/concepts/index.mdx
+++ b/src/content/docs/turnstile/concepts/index.mdx
@@ -8,11 +8,10 @@ sidebar:
   order: 3
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile's concepts:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/extensions/google-firebase.mdx b/src/content/docs/turnstile/extensions/google-firebase.mdx
index 2456c9d7c189b62..7ecd2d24ede91af 100644
--- a/src/content/docs/turnstile/extensions/google-firebase.mdx
+++ b/src/content/docs/turnstile/extensions/google-firebase.mdx
@@ -10,10 +10,9 @@ tags:
 sidebar:
   order: 2
   label: Google Firebase
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 Turnstile is [available as an extension](https://extensions.dev/extensions/cloudflare/cloudflare-turnstile-app-check-provider) with [Google's Firebase](https://firebase.google.com/) platform as an [App Check](https://firebase.google.com/docs/app-check) provider. You can leverage Cloudflare Turnstile's bot detection and challenge capabilities to ensure that requests to your Firebase backend services are verified and only authentic human visitors can interact with your application.
 
@@ -119,25 +118,25 @@ const expressApp = express();
 const firebaseApp = initializeApp();
 
 const appCheckVerification = async (req, res, next) => {
-    const appCheckToken = req.header("X-Firebase-AppCheck");
+	const appCheckToken = req.header("X-Firebase-AppCheck");
 
-    if (!appCheckToken) {
-        res.status(401);
-        return next("Unauthorized");
-    }
+	if (!appCheckToken) {
+		res.status(401);
+		return next("Unauthorized");
+	}
 
-    try {
-        const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
+	try {
+		const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
 
-        // If verifyToken() succeeds, continue with the next middleware function in the stack.
-        return next();
-    } catch (err) {
-        res.status(401);
-        return next("Unauthorized");
-    }
-}
+		// If verifyToken() succeeds, continue with the next middleware function in the stack.
+		return next();
+	} catch (err) {
+		res.status(401);
+		return next("Unauthorized");
+	}
+};
 
 expressApp.get("/yourApiEndpoint", [appCheckVerification], (req, res) => {
-    // Handle request.
+	// Handle request.
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/extensions/index.mdx b/src/content/docs/turnstile/extensions/index.mdx
index 2649807908e1165..e7d4e7afeae3a2f 100644
--- a/src/content/docs/turnstile/extensions/index.mdx
+++ b/src/content/docs/turnstile/extensions/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 9
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile extensions:
 
diff --git a/src/content/docs/turnstile/extensions/pages-plugin.mdx b/src/content/docs/turnstile/extensions/pages-plugin.mdx
index e3a41748a59f3ca..963a6bb4dee2004 100644
--- a/src/content/docs/turnstile/extensions/pages-plugin.mdx
+++ b/src/content/docs/turnstile/extensions/pages-plugin.mdx
@@ -7,5 +7,4 @@ title: Pages Plugin
 external_link: /pages/functions/plugins/turnstile/
 sidebar:
   order: 1
-
 ---
diff --git a/src/content/docs/turnstile/extensions/waiting-room.mdx b/src/content/docs/turnstile/extensions/waiting-room.mdx
index 474416b1df638c3..1153676741e4dc1 100644
--- a/src/content/docs/turnstile/extensions/waiting-room.mdx
+++ b/src/content/docs/turnstile/extensions/waiting-room.mdx
@@ -7,5 +7,4 @@ title: Waiting Room Analytics
 external_link: /waiting-room/waiting-room-analytics/#turnstile-widget-traffic
 sidebar:
   order: 3
-
 ---
diff --git a/src/content/docs/turnstile/get-started/widget-management/api.mdx b/src/content/docs/turnstile/get-started/widget-management/api.mdx
index 4342df29d7ee58e..9c0738b7d0d5cda 100644
--- a/src/content/docs/turnstile/get-started/widget-management/api.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/api.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - REST API
 sidebar:
-    order: 2
-    label: API
+  order: 2
+  label: API
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Use the [Cloudflare API](/api/resources/turnstile/) for programmatic widget management and automation.
 
@@ -25,47 +25,44 @@ Before you begin, you must have:
 ### Create a widget via the API
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets"
-  method="POST"
-  json={{
-    domains: ["example.com"],
-    mode: "managed",
-    name: "My Example Turnstile Widget",
-  }}
+	path="/accounts/{account_id}/challenges/widgets"
+	method="POST"
+	json={{
+		domains: ["example.com"],
+		mode: "managed",
+		name: "My Example Turnstile Widget",
+	}}
 />
 
 ### Manage widgets via the API
 
-<APIRequest
-  path="/accounts/{account_id}/challenges/widgets"
-  method="GET"
-/>
+<APIRequest path="/accounts/{account_id}/challenges/widgets" method="GET" />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="GET"
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="GET"
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="PUT"
-  json={{
-    domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
-    mode: "invisible",
-    name: "blog.cloudflare.com login form",
-    clearance_level: "interactive",
-  }}
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="PUT"
+	json={{
+		domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
+		mode: "invisible",
+		name: "blog.cloudflare.com login form",
+		clearance_level: "interactive",
+	}}
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
-  method="POST"
-  json={{
-    invalidate_immediately: false,
-  }}
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
+	method="POST"
+	json={{
+		invalidate_immediately: false,
+	}}
 />
 
 <APIRequest
-  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-  method="DELETE"
-/>
\ No newline at end of file
+	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+	method="DELETE"
+/>
diff --git a/src/content/docs/turnstile/get-started/widget-management/index.mdx b/src/content/docs/turnstile/get-started/widget-management/index.mdx
index bcb9b3c62a9e45f..70a4816c948455b 100644
--- a/src/content/docs/turnstile/get-started/widget-management/index.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about managing Turnstile widgets:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
index d39317f90ca363c..22a01e0fa0389de 100644
--- a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - Terraform
 sidebar:
-    order: 3
-    label: Terraform
+  order: 3
+  label: Terraform
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Manage Turnstile widgets as code using Terraform for version control and automated deployments.
 
@@ -153,7 +153,7 @@ locals {
 
 resource "cloudflare_turnstile_widget" "app_widget" {
   for_each = local.environments
-  
+
   account_id = var.account_id
   name       = "App Widget - ${each.key}"
   domains    = each.value.domains
@@ -195,4 +195,4 @@ cf-terraforming generate \
 ```shell title="Import existing widget"
 terraform import cloudflare_turnstile_widget.existing_widget \
   $ACCOUNT_ID/$WIDGET_SITEKEY
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/migration/hcaptcha.mdx b/src/content/docs/turnstile/migration/hcaptcha.mdx
index 87ff8fe69db29c4..bbe32fd8f917c8d 100644
--- a/src/content/docs/turnstile/migration/hcaptcha.mdx
+++ b/src/content/docs/turnstile/migration/hcaptcha.mdx
@@ -46,7 +46,7 @@ Turnstile supports:
 
 - the `render()` call
 - hCaptcha invisible mode with the `execute()` call
-:::
+  :::
 
 ## Server-side integration
 
diff --git a/src/content/docs/turnstile/reference/index.mdx b/src/content/docs/turnstile/reference/index.mdx
index ed8c7d7668f0cc2..0f952082dda1ea1 100644
--- a/src/content/docs/turnstile/reference/index.mdx
+++ b/src/content/docs/turnstile/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about Turnstile:
 
diff --git a/src/content/docs/turnstile/reference/supported-browsers.mdx b/src/content/docs/turnstile/reference/supported-browsers.mdx
index 28bdb4eb396bfad..837dbda385d3c26 100644
--- a/src/content/docs/turnstile/reference/supported-browsers.mdx
+++ b/src/content/docs/turnstile/reference/supported-browsers.mdx
@@ -7,5 +7,4 @@ title: Supported browsers
 external_link: /cloudflare-challenges/reference/supported-browsers/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/turnstile/reference/supported-languages.mdx b/src/content/docs/turnstile/reference/supported-languages.mdx
index f0338658d106a98..8263d260812b2fd 100644
--- a/src/content/docs/turnstile/reference/supported-languages.mdx
+++ b/src/content/docs/turnstile/reference/supported-languages.mdx
@@ -8,7 +8,6 @@ tags:
   - Localization
 sidebar:
   order: 3
-
 ---
 
 Turnstile supports `auto` (default), which uses the visitor's browser language if it is supported. You can also explicitly set the widget's language using the [client-side configuration attribute](/turnstile/get-started/client-side-rendering/#configurations) to one listed on the table below:
diff --git a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
index 12e1785bd51cc86..8b37a576667565e 100644
--- a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
+++ b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
@@ -7,5 +7,4 @@ title: Turnstile Privacy Addendum
 external_link: https://www.cloudflare.com/turnstile-privacy-policy/
 sidebar:
   order: 2
-
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
index 6a51837058ce17d..b38f8de49356b2c 100644
--- a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
@@ -7,5 +7,4 @@ title: Challenge solve issues
 external_link: /cloudflare-challenges/troubleshooting/challenge-solve-issues/
 sidebar:
   order: 4
-
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
index fd6c9090b063095..e0c9bc9938840cc 100644
--- a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
@@ -9,22 +9,21 @@ tags:
   - JavaScript
 sidebar:
   order: 3
-
 ---
 
 import { Tabs, TabItem } from "~/components";
 
-There are instances where Turnstile may encounter problems, invoking the `error-callback`. 
+There are instances where Turnstile may encounter problems, invoking the `error-callback`.
 
-These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures. 
+These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures.
 
-When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues. 
+When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues.
 
 Refer to the [Error codes](/turnstile/troubleshooting/client-side-errors/error-codes/) for troubleshooting guidance to address specific error conditions.
 
 ## Error handling
 
-The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur. 
+The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur.
 
 This callback mechanism gives you complete control over how errors are presented to visitors and allows you to implement custom recovery strategies tailored to your application's needs.
 
@@ -58,28 +57,30 @@ An error callback will retrieve an error code as its first parameter. This error
 
 ```js wrap
 function handleTurnstileError(errorCode) {
-  const errorFamily = Math.floor(errorCode / 1000);
-  
-  switch(errorFamily) {
-    case 100:
-      showMessage('Please refresh the page and try again.');
-      break;
-    case 110:
-      showMessage('Configuration error. Please contact support.');
-      break;
-    case 300:
-    case 600:
-      showMessage('Security check failed. Please try refreshing or using a different browser.');
-      break;
-    default:
-      showMessage('An unexpected error occurred. Please try again.');
-  }
+	const errorFamily = Math.floor(errorCode / 1000);
+
+	switch (errorFamily) {
+		case 100:
+			showMessage("Please refresh the page and try again.");
+			break;
+		case 110:
+			showMessage("Configuration error. Please contact support.");
+			break;
+		case 300:
+		case 600:
+			showMessage(
+				"Security check failed. Please try refreshing or using a different browser.",
+			);
+			break;
+		default:
+			showMessage("An unexpected error occurred. Please try again.");
+	}
 }
 ```
 
 ## Retry
 
-By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention. 
+By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention.
 
 This automatic retry mechanism is useful for [mobile visitors](/turnstile/get-started/mobile-implementation/) who may experience intermittent connectivity or visitors on networks with occasional stability issues.
 
@@ -88,34 +89,34 @@ When subsequent failures due to retries are observed, the error callback can be
 ```js wrap
 let retryCount = 0;
 
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  'error-callback': function(errorCode) {
-    retryCount++;
-    
-    if (retryCount <= 2) {
-      console.log(`Turnstile retry attempt ${retryCount}`);
-      return false; // Let Turnstile handle the retry
-    } else {
-      showPersistentErrorMessage(errorCode);
-      return true; // We'll handle it from here
-    }
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	"error-callback": function (errorCode) {
+		retryCount++;
+
+		if (retryCount <= 2) {
+			console.log(`Turnstile retry attempt ${retryCount}`);
+			return false; // Let Turnstile handle the retry
+		} else {
+			showPersistentErrorMessage(errorCode);
+			return true; // We'll handle it from here
+		}
+	},
 });
 ```
 
 You can adjust the retry behavior by setting the retry value to `never` instead of the default `auto`. This will result in Turnstile not automatically retrying, giving you control over when and how recovery attempts are made. If there is any issue or error verifying the visitor, the widget will not retry and will remain in the respective failure state until you take manual action.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  retry: 'never',
-  'error-callback': function(errorCode) {
-    // You control all retry logic
-    setTimeout(() => {
-      turnstile.reset('#my-widget');
-    }, 3000);
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	retry: "never",
+	"error-callback": function (errorCode) {
+		// You control all retry logic
+		setTimeout(() => {
+			turnstile.reset("#my-widget");
+		}, 3000);
+	},
 });
 ```
 
@@ -124,11 +125,11 @@ You may call `turnstile.reset()` in the corresponding `error-callback` to manual
 The interval between retries for Turnstile can be configured by the `retry-interval` option, allowing you to optimize retry timing for your visitors’ typical network conditions. A longer interval may be more appropriate for visitors on slower or less reliable connections, while shorter intervals work well in environments with typically stable connectivity.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  retry: 'auto',
-  'retry-interval': 8000, // Wait 8 seconds between retries
-  'error-callback': handleError
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	retry: "auto",
+	"retry-interval": 8000, // Wait 8 seconds between retries
+	"error-callback": handleError,
 });
 ```
 
@@ -141,23 +142,23 @@ For instance, in a scenario where the Turnstile widget is implemented within a f
 In such instances, the `timeout-callback` of the widget is activated, enabling the widget to reset itself as needed and provide appropriate guidance. This callback allows you to implement user-friendly timeout handling, such as highlighting the Turnstile widget, displaying a notification, or automatically refreshing the challenge.
 
 ```js wrap
-turnstile.render('#my-widget', {
-  sitekey: 'your-sitekey',
-  callback: function(token) {
-    console.log('Challenge completed successfully');
-  },
-  'timeout-callback': function() {
-    console.log('Challenge timed out - user action required');
-    document.getElementById('challenge-notice').textContent = 
-      'Please complete the security check above to continue.';
-    
-    // Optionally highlight the widget
-    document.getElementById('my-widget').style.border = '2px solid orange';
-  },
-  'expired-callback': function() {
-    console.log('Token expired - challenge needs refresh');
-    document.getElementById('challenge-notice').textContent = 
-      'Security check expired. Please try again.';
-  }
+turnstile.render("#my-widget", {
+	sitekey: "your-sitekey",
+	callback: function (token) {
+		console.log("Challenge completed successfully");
+	},
+	"timeout-callback": function () {
+		console.log("Challenge timed out - user action required");
+		document.getElementById("challenge-notice").textContent =
+			"Please complete the security check above to continue.";
+
+		// Optionally highlight the widget
+		document.getElementById("my-widget").style.border = "2px solid orange";
+	},
+	"expired-callback": function () {
+		console.log("Token expired - challenge needs refresh");
+		document.getElementById("challenge-notice").textContent =
+			"Security check expired. Please try again.";
+	},
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/turnstile/troubleshooting/index.mdx b/src/content/docs/turnstile/troubleshooting/index.mdx
index 9732a59701eb192..62155e4b61f1542 100644
--- a/src/content/docs/turnstile/troubleshooting/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 8
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information about troubleshooting Turnstile:
 
diff --git a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
index 50d1cebeb5a11e6..ce67d78a5431377 100644
--- a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
+++ b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
@@ -6,10 +6,9 @@ products:
   - turnstile
 sidebar:
   order: 2
-
 ---
 
-import { GlossaryTooltip, DashButton, Steps } from "~/components"
+import { GlossaryTooltip, DashButton, Steps } from "~/components";
 
 You can rotate the <GlossaryTooltip term="secret key">secret key</GlossaryTooltip> using the following steps:
 
diff --git a/src/content/docs/turnstile/troubleshooting/testing.mdx b/src/content/docs/turnstile/troubleshooting/testing.mdx
index 32e507a1005bb68..41f98655c15fd16 100644
--- a/src/content/docs/turnstile/troubleshooting/testing.mdx
+++ b/src/content/docs/turnstile/troubleshooting/testing.mdx
@@ -9,10 +9,9 @@ tags:
 sidebar:
   order: 1
   label: Testing
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Use dummy sitekeys and secret keys to test your Turnstile implementation without triggering real challenges that would interfere with automated testing suites.
 
@@ -27,23 +26,23 @@ Dummy keys solve this by providing predictable, controlled responses that work w
 
 ## Test sitekeys
 
-| Sitekey | Behavior | Widget Type | Use case |
-| ------- | -------- | ----------- | -------- |
-| `1x00000000000000000000AA` | Always passes | Visible | Test successful form submissions |
-| `2x00000000000000000000AB` | Always fails | Visible | Test error handling and retry logic |
-| `1x00000000000000000000BB` | Always passes | Invisible | Test invisible widget success flows |
-| `2x00000000000000000000BB` | Always fails | Invisible | Test invisible widget error handling |
-| `3x00000000000000000000FF` | Forces interactive challenge | Visible | Test user interaction scenarios |
+| Sitekey                    | Behavior                     | Widget Type | Use case                             |
+| -------------------------- | ---------------------------- | ----------- | ------------------------------------ |
+| `1x00000000000000000000AA` | Always passes                | Visible     | Test successful form submissions     |
+| `2x00000000000000000000AB` | Always fails                 | Visible     | Test error handling and retry logic  |
+| `1x00000000000000000000BB` | Always passes                | Invisible   | Test invisible widget success flows  |
+| `2x00000000000000000000BB` | Always fails                 | Invisible   | Test invisible widget error handling |
+| `3x00000000000000000000FF` | Forces interactive challenge | Visible     | Test user interaction scenarios      |
 
 ## Test secret keys
 
 Use these secret keys for server-side validation testing:
 
-| Secret key | Behavior | Use case |
-| ---------- | -------- | -------- |
-| `1x0000000000000000000000000000000AA` | Always passes validation | Test successful token validation |
-| `2x0000000000000000000000000000000AA` | Always fails validation | Test validation error handling |
-| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling |
+| Secret key                            | Behavior                            | Use case                         |
+| ------------------------------------- | ----------------------------------- | -------------------------------- |
+| `1x0000000000000000000000000000000AA` | Always passes validation            | Test successful token validation |
+| `2x0000000000000000000000000000000AA` | Always fails validation             | Test validation error handling   |
+| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling    |
 
 ---
 
@@ -78,9 +77,10 @@ Replace your production secret key with a test secret key.
 
 ```js
 // Environment-based configuration
-const SECRET_KEY = process.env.NODE_ENV === 'production' 
-  ? process.env.TURNSTILE_SECRET_KEY 
-  : '1x0000000000000000000000000000000AA';
+const SECRET_KEY =
+	process.env.NODE_ENV === "production"
+		? process.env.TURNSTILE_SECRET_KEY
+		: "1x0000000000000000000000000000000AA";
 
 // Use in validation
 const validation = await validateTurnstile(token, SECRET_KEY);
@@ -96,7 +96,7 @@ Set up different keys for different environments.
 TURNSTILE_SITEKEY=1x00000000000000000000AA
 TURNSTILE_SECRET_KEY=1x0000000000000000000000000000000AA
 
-# .env.test  
+# .env.test
 TURNSTILE_SITEKEY=2x00000000000000000000AB
 TURNSTILE_SECRET_KEY=2x0000000000000000000000000000000AA
 
@@ -126,27 +126,26 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ```json title="Success response"
 {
-  "success": true,
-  "challenge_ts": "2022-02-28T15:14:30.096Z",
-  "hostname": "localhost",
-  "error-codes": [],
-  "action": "test",
-  "cdata": "test-data"
+	"success": true,
+	"challenge_ts": "2022-02-28T15:14:30.096Z",
+	"hostname": "localhost",
+	"error-codes": [],
+	"action": "test",
+	"cdata": "test-data"
 }
 ```
 
 ```json title="Failure response"
 {
-  "success": false,
-  "error-codes": ["invalid-input-response"]
+	"success": false,
+	"error-codes": ["invalid-input-response"]
 }
-
 ```
 
 ```json title="Token already redeemed"
 {
-  "success": false,
-  "error-codes": ["timeout-or-duplicate"]
+	"success": false,
+	"error-codes": ["timeout-or-duplicate"]
 }
 ```
 
@@ -154,8 +153,8 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ## Testing scenarios
 
-| Test sitekey | Test secret key | <div style="width:200px">Test case</div> |
-| ------------ | --------------- | --------- |
-| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation. |
-| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail. |
-| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
\ No newline at end of file
+| Test sitekey               | Test secret key                       | <div style="width:200px">Test case</div>                             |
+| -------------------------- | ------------------------------------- | -------------------------------------------------------------------- |
+| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation.        |
+| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail.                                   |
+| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
diff --git a/src/content/docs/turnstile/turnstile-analytics/index.mdx b/src/content/docs/turnstile/turnstile-analytics/index.mdx
index b580a70e9a92a88..1ad2a0c6a7bcde0 100644
--- a/src/content/docs/turnstile/turnstile-analytics/index.mdx
+++ b/src/content/docs/turnstile/turnstile-analytics/index.mdx
@@ -9,10 +9,9 @@ sidebar:
   order: 5
 description: Use Turnstile Analytics to view the number of challenges issued,
   the challenge solve rate, and the metrics of issued challenges.
-
 ---
 
-import { Render, DirectoryListing, DashButton } from "~/components"
+import { Render, DirectoryListing, DashButton } from "~/components";
 
 Turnstile Analytics shows widget statistics across traffic dimensions like hostname, country, browser, and IP address. Use these metrics to identify where challenge activity is highest and whether specific sources are failing or bypassing challenges.
 
@@ -38,4 +37,4 @@ The metrics show changes in the solve rate, widget traffic, and top actions for
 
 Refer to the pages below for more information about Turnstile Analytics:
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
index 6a6c10bc60370a8..a4a5ca21b6e199c 100644
--- a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
+++ b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
@@ -28,10 +28,11 @@ For more details, refer to the [testing documentation](/turnstile/troubleshootin
 :::caution
 
 Never use test credentials in production. Always ensure:
+
 - Test credentials are only used in test environments.
 - Production credentials are properly protected.
 - Your deployment process prevents test credentials from reaching production.
-:::
+  :::
 
 ## Implementation
 
@@ -40,26 +41,27 @@ The key to implementing test-environment detection is identifying test requests
 ```typescript
 // Detect test environments using IP addresses or headers
 function isTestEnvironment(request) {
-  const testIPs = ['127.0.0.1', '::1'];
-  const isTestIP = testIPs.includes(request.ip);
-  const hasTestHeader = request.headers['x-test-environment'] === 'secret-token';
+	const testIPs = ["127.0.0.1", "::1"];
+	const isTestIP = testIPs.includes(request.ip);
+	const hasTestHeader =
+		request.headers["x-test-environment"] === "secret-token";
 
-  return isTestIP || hasTestHeader;
+	return isTestIP || hasTestHeader;
 }
 
 // Use the appropriate credentials based on the environment
 function getTurnstileCredentials(request) {
-  if (isTestEnvironment(request)) {
-    return {
-      sitekey: '1x00000000000000000000AA',
-      secretKey: '1x0000000000000000000000000000000AA'
-    };
-  }
-
-  return {
-    sitekey: process.env.TURNSTILE_SITE_KEY,
-    secretKey: process.env.TURNSTILE_SECRET_KEY
-  };
+	if (isTestEnvironment(request)) {
+		return {
+			sitekey: "1x00000000000000000000AA",
+			secretKey: "1x0000000000000000000000000000000AA",
+		};
+	}
+
+	return {
+		sitekey: process.env.TURNSTILE_SITE_KEY,
+		secretKey: process.env.TURNSTILE_SECRET_KEY,
+	};
 }
 ```
 
@@ -68,9 +70,9 @@ function getTurnstileCredentials(request) {
 When rendering your page, inject the appropriate sitekey based on the environment:
 
 ```typescript
-app.get('/your-form', (req, res) => {
-  const { sitekey } = getTurnstileCredentials(req);
-  res.render('form', { sitekey });
+app.get("/your-form", (req, res) => {
+	const { sitekey } = getTurnstileCredentials(req);
+	res.render("form", { sitekey });
 });
 ```
 
@@ -112,16 +114,16 @@ For Cypress or similar E2E testing frameworks:
 ```typescript
 // Set test header for all test requests
 beforeEach(() => {
-  cy.intercept('*', (req) => {
-    req.headers['x-test-environment'] = 'secret-token';
-  });
+	cy.intercept("*", (req) => {
+		req.headers["x-test-environment"] = "secret-token";
+	});
 });
 
 // Your test can now interact with the form normally
-it('submits form successfully', () => {
-  cy.visit('/your-form');
-  cy.get('form').submit();
-  // Turnstile will automatically pass verification
+it("submits form successfully", () => {
+	cy.visit("/your-form");
+	cy.get("form").submit();
+	// Turnstile will automatically pass verification
 });
 ```
 
diff --git a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
index cd516941cbdc5e1..865dade6b1b9bde 100644
--- a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
+++ b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
@@ -27,7 +27,7 @@ Traditional IP-based detection fails because each request appears to come from a
 - You must have basic familiarity with Turnstile integration. Refer to [Get started with Turnstile](/turnstile/get-started/) for more information.
 
 :::caution[Ephemeral IDs are not guaranteed to be unique]
-Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID. 
+Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID.
 
 Use Ephemeral IDs to detect high-volume abuse patterns, not to uniquely identify individual devices. Always set detection thresholds high enough to avoid false positives.
 :::
@@ -241,4 +241,4 @@ Ephemeral IDs are privacy-preserving. They are scoped to your account, short-liv
 
 - [Ephemeral IDs](/turnstile/additional-configuration/ephemeral-id/)
 - [Server-side validation](/turnstile/get-started/server-side-validation/)
-- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
\ No newline at end of file
+- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
diff --git a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
index c7a73ce8527faa1..ebc66f19cfe4972 100644
--- a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
+++ b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
@@ -85,7 +85,13 @@ Add the Turnstile widget to your existing login form:
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
+	<input
+		type="password"
+		id="password"
+		placeholder="Password"
+		autocomplete="off"
+		required
+	/>
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
diff --git a/src/content/docs/use-cases/e-commerce/performance.mdx b/src/content/docs/use-cases/e-commerce/performance.mdx
index 7c7d4fc51d1f3db..82a7e010f0ab221 100644
--- a/src/content/docs/use-cases/e-commerce/performance.mdx
+++ b/src/content/docs/use-cases/e-commerce/performance.mdx
@@ -51,4 +51,4 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 2. [Set up Cloudflare Images](/images/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
 4. [Configure Zaraz](/zaraz/get-started/)
-5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
+5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
diff --git a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
index 9a2ebfe22516874..a073c15a2066185 100644
--- a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
+++ b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
@@ -11,21 +11,29 @@ sidebar:
 
 import { DashButton, Render, Steps, TabItem, Tabs } from "~/components";
 
-HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages: 
+HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages:
 
 1. Configure your SSL/TLS encryption mode.
 2. Redirect all HTTP requests to HTTPS.
 3. Harden your HTTPS setup with minimum TLS versions and HSTS.
 4. Monitor third-party scripts on your pages.
-5. Verify your configuration. 
+5. Verify your configuration.
 
 The core workflow is available on Free, Pro, and Business plans.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Client-Side Security is the exception: it is configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Client-Side Security is the exception: it is configured at the account level.",
+	}}
+/>
 
 ## Configure your SSL/TLS encryption mode
 
 Your SSL/TLS encryption mode controls how Cloudflare connects to your origin server. For end-to-end encryption, use **Full (strict)** — it encrypts both connections and verifies your origin certificate. For a detailed comparison of all available modes, refer to [Encryption modes](/ssl/origin-configuration/ssl-modes/).
+
 ### Check your current mode
 
 <Steps>
@@ -75,6 +83,7 @@ If your origin already has a valid certificate from a publicly trusted certifica
 9. Select **OK**.
 
 </Steps>
+
 :::note
 For details about working with certificates programmatically, refer to [API calls](/ssl/origin-configuration/origin-ca/#api-calls).
 :::
@@ -92,6 +101,7 @@ For details about working with certificates programmatically, refer to [API call
 4. Enable SSL and port `443` at your origin web server.
 
 </Steps>
+
 :::note
 If you do not see your server listed, search the [DigiCert documentation](https://www.digicert.com/search-results) or contact your hosting provider.
 :::
@@ -109,13 +119,15 @@ After installing a valid certificate on your origin server, set the encryption m
 <Render file="change-encryption-mode-api" product="ssl" />
 
 </TabItem> </Tabs>
+
 :::caution
 If your site shows a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) after changing the encryption mode, your origin certificate may not meet the requirements for Full (strict). The certificate must be unexpired, issued by a trusted CA or Cloudflare Origin CA, and contain a Common Name (CN) or Subject Alternative Name (SAN) that matches your hostname. For redirect loop issues, refer to [ERR_TOO_MANY_REDIRECTS](/ssl/troubleshooting/too-many-redirects/).
 :::
 
 ## Redirect all HTTP requests to HTTPS
 
-Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this: 
+Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this:
+
 1. Always Use HTTPS redirects HTTP requests to HTTPS
 2. Automatic HTTPS Rewrites fixes mixed content references in your page HTML
 
@@ -154,6 +166,7 @@ If only some parts of your application can support HTTPS traffic, do not turn on
 </Steps>
 
 </TabItem> </Tabs>
+
 ### Turn on Automatic HTTPS Rewrites
 
 Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resource URLs in your page HTML to HTTPS. This is useful for sites where you do not control all asset URLs, such as CMS-hosted content or embedded third-party resources.
@@ -175,6 +188,7 @@ Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resourc
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `automatic_https_rewrites` as the setting name in the URI path, and the `value` parameter set to `"on"`.
 
 </TabItem> </Tabs>
+
 :::note
 Automatic HTTPS Rewrites does not rewrite all HTTP URLs. Some passive content (such as images) may not be rewritten, which can still cause mixed content warnings. For details on how rewrites work and troubleshooting, refer to [Automatic HTTPS Rewrites](/ssl/edge-certificates/additional-options/automatic-https-rewrites/) and [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/).
 :::
@@ -204,6 +218,7 @@ TLS 1.0 and 1.1 have known vulnerabilities and are no longer considered secure.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `min_tls_version` as the setting name in the URI path, and the `value` parameter set to `"1.2"`.
 
 </TabItem> </Tabs>
+
 :::note[Per-hostname minimum TLS version requires Advanced Certificate Manager]
 To set minimum TLS versions for individual hostnames instead of the entire zone, refer to [Per-hostname setup](/ssl/edge-certificates/additional-options/minimum-tls/#per-hostname). This requires an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription.
 :::
@@ -229,6 +244,7 @@ TLS 1.3 provides faster handshakes and improved security over TLS 1.2.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `tls_1_3` as the setting name in the URI path, and the `value` parameter set to `"on"`. To also turn on 0-RTT (Zero Round Trip Time Resumption), set the value to `"zrt"`.
 
 </TabItem> </Tabs>
+
 ### Turn on HSTS
 
 HTTP Strict Transport Security (HSTS) adds a response header that tells browsers to connect to your site over HTTPS only, even if a link or redirect tries to send them over HTTP. HSTS protects against protocol downgrade attacks.
@@ -272,6 +288,7 @@ Before turning on HSTS, confirm these prerequisites:
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `security_header` as the setting name in the URI path, and specify the `value` object that includes your HSTS settings.
 
 </TabItem> </Tabs>
+
 ### Review your cipher suites
 
 Cloudflare's default cipher suites provide strong encryption for most sites. You do not need to change them unless a security audit or compliance requirement specifies particular cipher configurations.
@@ -299,6 +316,7 @@ HTTPS encrypts data in transit, but third-party scripts loaded by your pages can
 3. Turn on **Continuous script monitoring**.
 
 </Steps>
+
 ### Review detected resources
 
 After turning on monitoring, it may take some time for Cloudflare to generate a list of detected scripts on your domain.
@@ -314,6 +332,7 @@ After turning on monitoring, it may take some time for Cloudflare to generate a
 3. Review the list of detected scripts. Check for unknown or unexpected scripts from domains you do not recognize.
 
 </Steps>
+
 Depending on your Cloudflare plan, you may also be able to review connections made by scripts and check them for malicious activity. For setup details, refer to [Get started with client-side security](/client-side-security/get-started/).
 
 :::note[Content security rules require Client-Side Security Advanced]
diff --git a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
index 4cfed58dfe9b42a..0e5abbc0284d7c9 100644
--- a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
+++ b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
@@ -15,7 +15,14 @@ import { Render, Steps, DashButton } from "~/components";
 
 Contact, registration, and checkout forms are common targets for automated abuse. This guide covers form protection: verifying that visitors are human, limiting repeated submissions, and blocking known attack patterns. The core workflow uses features available on all plans. Pro and Business plan features are included as callouts.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Add Turnstile to your forms
 
@@ -35,14 +42,18 @@ Add the Turnstile script and widget `div` element to each form you want to prote
 
 ```html
 <form id="contact-form" action="/submit" method="POST">
-  <input type="text" name="name" placeholder="Name" required />
-  <input type="email" name="email" placeholder="Email" required />
-  <textarea name="message" placeholder="Message" required></textarea>
-  <div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
-  <button type="submit">Submit</button>
+	<input type="text" name="name" placeholder="Name" required />
+	<input type="email" name="email" placeholder="Email" required />
+	<textarea name="message" placeholder="Message" required></textarea>
+	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
+	<button type="submit">Submit</button>
 </form>
 
-<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
+<script
+	src="https://challenges.cloudflare.com/turnstile/v0/api.js"
+	async
+	defer
+></script>
 ```
 
 The widget renders in the form and generates a token when the visitor passes verification. The token is included in the form submission as the `cf-turnstile-response` field.
@@ -57,26 +68,26 @@ Call the Siteverify API before processing any form submission:
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
 async function validateTurnstile(token, remoteip) {
-  try {
-    const response = await fetch(
-      "https://challenges.cloudflare.com/turnstile/v0/siteverify",
-      {
-        method: "POST",
-        headers: { "Content-Type": "application/json" },
-        body: JSON.stringify({
-          secret: SECRET_KEY,
-          response: token,
-          remoteip: remoteip,
-        }),
-      },
-    );
-
-    const result = await response.json();
-    return result;
-  } catch (error) {
-    console.error("Turnstile validation error:", error);
-    return { success: false, "error-codes": ["internal-error"] };
-  }
+	try {
+		const response = await fetch(
+			"https://challenges.cloudflare.com/turnstile/v0/siteverify",
+			{
+				method: "POST",
+				headers: { "Content-Type": "application/json" },
+				body: JSON.stringify({
+					secret: SECRET_KEY,
+					response: token,
+					remoteip: remoteip,
+				}),
+			},
+		);
+
+		const result = await response.json();
+		return result;
+	} catch (error) {
+		console.error("Turnstile validation error:", error);
+		return { success: false, "error-codes": ["internal-error"] };
+	}
 }
 ```
 
@@ -116,7 +127,17 @@ The **Request rate analysis** tab in Security Analytics displays request rate di
 
 Create a rule that limits how many times a single IP address can submit to your form endpoint within a given period. Adjust the path, threshold, and period for your site.
 
-<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit contact form submissions", expression: '(http.request.uri.path eq "/contact" and http.request.method eq "POST")', expressionHelp: 'Replace "/contact" with your form endpoint path.', threshold: "5" }} />
+<Render
+	file="create-rate-limiting-rule"
+	product="waf"
+	params={{
+		ruleName: "Rate limit contact form submissions",
+		expression:
+			'(http.request.uri.path eq "/contact" and http.request.method eq "POST")',
+		expressionHelp: 'Replace "/contact" with your form endpoint path.',
+		threshold: "5",
+	}}
+/>
 
 :::note
 Rate limiting rule parameters (counting characteristics, periods, number of rules) vary by plan. For the full availability matrix, refer to [Rate limiting rules](/waf/rate-limiting-rules/#availability).
diff --git a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
index cfa61e65fe47d61..e1db4f92ef75e8b 100644
--- a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
+++ b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
@@ -11,16 +11,18 @@ sidebar:
   label: Stop account takeover
 ---
 
-import {
-  Steps,
-  DashButton,
-  GlossaryTooltip,
-  Render,
-} from "~/components";
+import { Steps, DashButton, GlossaryTooltip, Render } from "~/components";
 
 When your site has login pages, you need to decide how to verify that visitors are human, how aggressively to limit failed attempts, and which request patterns to block. This guide covers five stages: enforce HTTPS, turn on bot protection, add [Turnstile](/turnstile/) to your login form, create Application Security [rate limiting rules](/waf/rate-limiting-rules/) and [custom rules](/waf/custom-rules/) for suspicious patterns, and monitor for ongoing attacks using [SSL/TLS](/ssl/) transport security and [Cloudflare bot solutions](/bots/). The core workflow covers features available on Free, Pro, and Business plans. Enterprise features such as leaked credentials custom detection locations and Bot Management custom rules are included as callouts.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Enforce HTTPS to protect credentials in transit
 
@@ -98,10 +100,17 @@ You need both the sitekey and secret key in the following steps.
 #### 2. Add the client-side snippet
 
 Add the Turnstile script and widget container to your login form. Replace `<YOUR-SITE-KEY>` with the sitekey from the previous step.
+
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
+	<input
+		type="password"
+		id="password"
+		placeholder="Password"
+		autocomplete="off"
+		required
+	/>
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
@@ -118,6 +127,7 @@ The widget renders inside the `div` and produces a token when the visitor passes
 #### 3. Validate the token on your server
 
 Before processing the form submission, send the token to the Turnstile siteverify endpoint to confirm the visitor passed the challenge.
+
 ```js title="server.js"
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
@@ -156,6 +166,7 @@ For the complete response format, error codes, and examples in other languages,
 #### Test your implementation
 
 Turnstile provides test site keys that return predictable results without contacting the Siteverify API.
+
 - **Always passes**: Use site key `1x00000000000000000000AA` and secret key `1x0000000000000000000000000000000AA` to simulate a successful challenge.
 - **Always blocks**: Use site key `2x00000000000000000000AB` and secret key `2x0000000000000000000000000000000AA` to simulate a failed challenge.
 - **Forces interactive challenge**: Use site key `3x00000000000000000000FF` to test the interactive challenge flow.
@@ -172,7 +183,18 @@ The following example creates a rate limiting rule that issues a Managed Challen
 Managed Challenge and other [challenge types](/cloudflare-challenges/challenge-types/challenge-pages/) require an HTML response to render. They do not work for non-HTML responses such as AJAX/XHR requests, which are common on login endpoints that use single-page applications (SPAs) or API-based authentication. If your login flow uses AJAX, consider using [Turnstile Pre-Clearance](/turnstile/additional-configuration/pre-clearance-support/) instead.
 :::
 
-<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit login endpoint", expression: 'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"', expressionHelp: 'Replace `example.com` with your domain and `/login` with your login endpoint path.', threshold: "5" }} />
+<Render
+	file="create-rate-limiting-rule"
+	product="waf"
+	params={{
+		ruleName: "Rate limit login endpoint",
+		expression:
+			'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"',
+		expressionHelp:
+			"Replace `example.com` with your domain and `/login` with your login endpoint path.",
+		threshold: "5",
+	}}
+/>
 
 :::note
 (Optional) To count only failed login attempts instead of all matching requests, Business plan and above users can add a separate counting expression under **Increment counter when**:
@@ -320,7 +342,7 @@ Enterprise customers with Bot Management get additional tools for login protecti
 - **Custom rules with bot scores**: combine `cf.bot_management.score` with login path matching for precise control. Refer to [Custom rules for bot protection](/bots/additional-configurations/custom-rules/).
 - **Account takeover detections**: monitor suspicious login volume and failure rates using detection IDs in custom rules and rate limiting rules. Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/).
 - **Account Abuse Protection** (Early Access): detect account fraud patterns beyond credential stuffing. Refer to [Account Abuse Protection](/bots/account-abuse-protection/).
-:::
+  :::
 
 ## Monitor for ongoing compromise attempts
 
diff --git a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
index df0cbabb8f7a2aa..82e2fbcd9c90854 100644
--- a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
+++ b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
@@ -14,7 +14,14 @@ import { Tabs, TabItem, Steps, Render, DashButton } from "~/components";
 
 The right defense against malicious bot traffic depends on the traffic patterns on your site and your plan. This guide covers a layered approach using [Cloudflare Bots](/bots/), [Cloudflare Application Security](/waf/) (also known as Web Application Firewall or WAF), and [Turnstile](/turnstile/), from baseline protection to targeted custom rules. The core workflow uses features on Free, Pro, and Business plans, with callouts for Enterprise options.
 
-<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
+<Render
+	file="domain-scope-note"
+	product="use-cases"
+	params={{
+		exception:
+			"Turnstile is the exception: widgets are configured at the account level.",
+	}}
+/>
 
 ## Review your bot traffic
 
diff --git a/src/content/docs/use-cases/web-apps/performance.mdx b/src/content/docs/use-cases/web-apps/performance.mdx
index f3ac9b09881123e..8fa2bc53968700d 100644
--- a/src/content/docs/use-cases/web-apps/performance.mdx
+++ b/src/content/docs/use-cases/web-apps/performance.mdx
@@ -39,10 +39,9 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 
 - **Edge logic** - Run custom performance optimizations at the edge, such as HTML rewriting and dynamic content assembly, without round-trips to your origin
 
-
 ## Get started
 
 1. [Configure Cache Rules](/cache/how-to/cache-rules/)
 2. [Enable Argo Smart Routing](/argo-smart-routing/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
-4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
+4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
diff --git a/src/content/docs/vectorize/best-practices/index.mdx b/src/content/docs/vectorize/best-practices/index.mdx
index de610d3a68aed70..b5663efc9edfdd9 100644
--- a/src/content/docs/vectorize/best-practices/index.mdx
+++ b/src/content/docs/vectorize/best-practices/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/best-practices/list-vectors.mdx b/src/content/docs/vectorize/best-practices/list-vectors.mdx
index d623e334eb65385..0c5754e5d12cfb3 100644
--- a/src/content/docs/vectorize/best-practices/list-vectors.mdx
+++ b/src/content/docs/vectorize/best-practices/list-vectors.mdx
@@ -43,6 +43,7 @@ To see recently added or removed vectors, you must start a new list-vectors requ
 ### Response structure
 
 Each response includes:
+
 - `count`: Number of vectors returned in this response
 - `totalCount`: Total number of vectors in the index
 - `isTruncated`: Whether there are more vectors available
@@ -70,4 +71,4 @@ wrangler vectorize list-vectors my-index --count=1000
 wrangler vectorize list-vectors my-index --count=1000 --cursor="<cursor-from-response>"
 
 # Repeat until no more results
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/vectorize/demos.mdx b/src/content/docs/vectorize/demos.mdx
index d908b0b5883751d..f98a71856f7f16a 100644
--- a/src/content/docs/vectorize/demos.mdx
+++ b/src/content/docs/vectorize/demos.mdx
@@ -8,7 +8,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, ResourcesBySelector } from "~/components"
+import { GlossaryTooltip, ResourcesBySelector } from "~/components";
 
 Learn how you can use Vectorize within your existing architecture.
 
@@ -16,4 +16,11 @@ Learn how you can use Vectorize within your existing architecture.
 
 Explore the following <GlossaryTooltip term="reference architecture">reference architectures</GlossaryTooltip> that use Vectorize:
 
-<ResourcesBySelector types={["reference-architecture","design-guide","reference-architecture-diagram"]} products={["vectorize"]} />
+<ResourcesBySelector
+	types={[
+		"reference-architecture",
+		"design-guide",
+		"reference-architecture-diagram",
+	]}
+	products={["vectorize"]}
+/>
diff --git a/src/content/docs/vectorize/examples/agents.mdx b/src/content/docs/vectorize/examples/agents.mdx
index c7eb3790d39040b..e9bd2deab309881 100644
--- a/src/content/docs/vectorize/examples/agents.mdx
+++ b/src/content/docs/vectorize/examples/agents.mdx
@@ -9,4 +9,4 @@ description: Build AI-powered Agents on Cloudflare
 products:
   - vectorize
   - agents
----
\ No newline at end of file
+---
diff --git a/src/content/docs/vectorize/examples/index.mdx b/src/content/docs/vectorize/examples/index.mdx
index b7aaf4f768acdcd..f5b3b57929be9d3 100644
--- a/src/content/docs/vectorize/examples/index.mdx
+++ b/src/content/docs/vectorize/examples/index.mdx
@@ -11,7 +11,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, DirectoryListing } from "~/components"
+import { GlossaryTooltip, DirectoryListing } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Vectorize.
 
diff --git a/src/content/docs/vectorize/get-started/index.mdx b/src/content/docs/vectorize/get-started/index.mdx
index 2ea3f1ce7462b31..44c0cdc6b7ec9e3 100644
--- a/src/content/docs/vectorize/get-started/index.mdx
+++ b/src/content/docs/vectorize/get-started/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/platform/index.mdx b/src/content/docs/vectorize/platform/index.mdx
index 1be91e4d2f5aaf8..0dde65d6a58df96 100644
--- a/src/content/docs/vectorize/platform/index.mdx
+++ b/src/content/docs/vectorize/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/reference/index.mdx b/src/content/docs/vectorize/reference/index.mdx
index f297e13f34d84b6..8f496dea995d462 100644
--- a/src/content/docs/vectorize/reference/index.mdx
+++ b/src/content/docs/vectorize/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/about.mdx b/src/content/docs/version-management/about.mdx
index 6c6e429bda9459d..1587b66c14e88d6 100644
--- a/src/content/docs/version-management/about.mdx
+++ b/src/content/docs/version-management/about.mdx
@@ -9,7 +9,7 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Version Management works through a combination of **environments** and **versions**.
 
@@ -47,7 +47,7 @@ stateDiagram-v2
 
 ## Environments
 
-<Render file="environment-definition" product="version-management" /> <br/>
+<Render file="environment-definition" product="version-management" /> <br />
 
 After you [enable](/version-management/how-to/enable/) version management, you will have the ability to create default environments:
 
@@ -59,7 +59,7 @@ To send traffic to specific environments, send requests to that environment that
 
 ## Versions
 
-<Render file="version-definition" product="version-management" /> <br/>
+<Render file="version-definition" product="version-management" /> <br />
 
 <Render file="enable-default-creation" product="version-management" />
 
diff --git a/src/content/docs/version-management/how-to/compare-versions.mdx b/src/content/docs/version-management/how-to/compare-versions.mdx
index 587f8e9dea1faed..1b6ec4ea51148f4 100644
--- a/src/content/docs/version-management/how-to/compare-versions.mdx
+++ b/src/content/docs/version-management/how-to/compare-versions.mdx
@@ -19,7 +19,7 @@ To compare versions:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management** > **Comparisons**.
diff --git a/src/content/docs/version-management/how-to/environments.mdx b/src/content/docs/version-management/how-to/environments.mdx
index 7b1de502b4273a7..9c26342241ce248 100644
--- a/src/content/docs/version-management/how-to/environments.mdx
+++ b/src/content/docs/version-management/how-to/environments.mdx
@@ -9,44 +9,43 @@ products:
   - version-management
 ---
 
-import { DashButton, Render } from "~/components"
+import { DashButton, Render } from "~/components";
 
 <Render file="environment-definition" product="version-management" />
 
-***
+---
 
 ## Create environment
 
 <Render file="enable-default-creation" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" /> <br/>
+<Render file="create-environment-situation" product="version-management" />
+<br />
 
 To create a new environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Go to **Environments**.
 4. Select **Create Environment**.
 5. Provide the following information:
 
-* **Environment Name**: A unique, descriptive name for the environment.
-* [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
-* **Initial position**: Controls where this environment should be in your testing process.
+- **Environment Name**: A unique, descriptive name for the environment.
+- [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
+- **Initial position**: Controls where this environment should be in your testing process.
 
 6. Select **Create**.
 
 :::note
 
-
 You can only adjust the [**Read-only Environment**](/version-management/reference/read-only-environments/) configuration after an environment has been created.
 
-
 :::
 
-***
+---
 
 ## Edit environment
 
@@ -54,7 +53,7 @@ To edit an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -62,7 +61,7 @@ To edit an environment:
 5. Make any required changes.
 6. Select **Save**.
 
-***
+---
 
 ## Change environment version
 
@@ -74,7 +73,7 @@ For more details on the flow of versions and environments, refer to [How it work
 
 Promotion moves a version from a lower-ranked environment to the next highest one.
 
-<Render file="promote-version" product="version-management" /> <br/>
+<Render file="promote-version" product="version-management" /> <br />
 
 ### Roll back a version
 
@@ -84,13 +83,13 @@ To roll back a version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
 4. On a specific environment, select **Roll back**.
 
-***
+---
 
 ## Delete environment
 
@@ -98,7 +97,7 @@ To delete an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -107,8 +106,6 @@ To delete an environment:
 
 :::note
 
-
 You cannot delete your **Production** environment.
 
-
 :::
diff --git a/src/content/docs/version-management/how-to/index.mdx b/src/content/docs/version-management/how-to/index.mdx
index 94f85edeb05a853..688bebd5f8faf4c 100644
--- a/src/content/docs/version-management/how-to/index.mdx
+++ b/src/content/docs/version-management/how-to/index.mdx
@@ -3,7 +3,7 @@ title: How to
 pcx_content_type: navigation
 sidebar:
   order: 4
-  group: 
+  group:
     hideIndex: true
 
 description: Guides for managing versions and environments.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/how-to/versions.mdx b/src/content/docs/version-management/how-to/versions.mdx
index 2bacb859b39b82d..df497bbd391bd24 100644
--- a/src/content/docs/version-management/how-to/versions.mdx
+++ b/src/content/docs/version-management/how-to/versions.mdx
@@ -25,7 +25,7 @@ To create a new version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **Clone**. This will copy over all configurations from that version.
@@ -78,7 +78,7 @@ To view metrics:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **View Metrics**.
diff --git a/src/content/docs/version-management/reference/available-configurations.mdx b/src/content/docs/version-management/reference/available-configurations.mdx
index d9d33c1d24d8f15..bf748224eda2e08 100644
--- a/src/content/docs/version-management/reference/available-configurations.mdx
+++ b/src/content/docs/version-management/reference/available-configurations.mdx
@@ -9,24 +9,22 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When you use Version Management, you can edit various configurations, such as [WAF custom rules](/waf/custom-rules/) and [Cache](/cache/).
 
 Generally, you are allowed to edit all zone-level configurations except for the following:
 
-* [DNS](/dns/)
-* [Spectrum](/spectrum/)
-* Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
-* [Zero Trust](/cloudflare-one/) and Access policies
-* [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
+- [DNS](/dns/)
+- [Spectrum](/spectrum/)
+- Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
+- [Zero Trust](/cloudflare-one/) and Access policies
+- [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
 
 :::note
 
-
 For the most up-to-date list of these configurations, start [editing configurations within a version](/version-management/how-to/versions/#change-configurations-in-a-version) in the Cloudflare dashboard.
 
-
 :::
 
 ## Limitations
diff --git a/src/content/docs/version-management/reference/index.mdx b/src/content/docs/version-management/reference/index.mdx
index 38759a3843efde4..042d6149a274f5b 100644
--- a/src/content/docs/version-management/reference/index.mdx
+++ b/src/content/docs/version-management/reference/index.mdx
@@ -3,7 +3,7 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 5
-  group: 
+  group:
     hideIndex: true
 
 description: Reference information for AI Crawl Control.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/reference/read-only-environments.mdx b/src/content/docs/version-management/reference/read-only-environments.mdx
index b6e45386b17cec4..36c12fc21a35a82 100644
--- a/src/content/docs/version-management/reference/read-only-environments.mdx
+++ b/src/content/docs/version-management/reference/read-only-environments.mdx
@@ -9,14 +9,15 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 When an environment is read-only, versions deployed to this environment will permanently become read-only. This configuration protects sensitive environments from accidental changes.
 
 **Version Zero** is an exception to this rule and is always editable.
 
-<Render file="production-read-only-default" product="version-management" /> <br/>
+<Render file="production-read-only-default" product="version-management" />
+<br />
 
-For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** *after* your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
+For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** _after_ your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
 
 To change the read-only status of an environment, [edit the environment](/version-management/how-to/environments/#edit-environment).
diff --git a/src/content/docs/waf/custom-rules/create-dashboard.mdx b/src/content/docs/waf/custom-rules/create-dashboard.mdx
index 5e974d601239c71..a48edb1f3026c30 100644
--- a/src/content/docs/waf/custom-rules/create-dashboard.mdx
+++ b/src/content/docs/waf/custom-rules/create-dashboard.mdx
@@ -15,7 +15,6 @@ head:
 
 import { Render, Tabs, TabItem, Steps, DashButton } from "~/components";
 
-
 <Tabs syncKey="dashNewNav"> <TabItem label="New dashboard" icon="rocket">
 
 <Steps>
diff --git a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
index 749a72275225954..6775abcaf7788d7 100644
--- a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
+++ b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
@@ -10,4 +10,4 @@ import { Render } from "~/components";
 
 You can build an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
 
-<Render file="sequence-custom-rules" product="api-shield" />
\ No newline at end of file
+<Render file="sequence-custom-rules" product="api-shield" />
diff --git a/src/content/docs/waf/glossary.mdx b/src/content/docs/waf/glossary.mdx
index e777165a6bf1999..f7ce048d441c2e7 100644
--- a/src/content/docs/waf/glossary.mdx
+++ b/src/content/docs/waf/glossary.mdx
@@ -6,10 +6,9 @@ products:
   - waf
 sidebar:
   order: 17
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's WAF documentation.
 
diff --git a/src/content/docs/waf/managed-rules/index.mdx b/src/content/docs/waf/managed-rules/index.mdx
index d24fec1853393e0..dcdce6b4f353b4b 100644
--- a/src/content/docs/waf/managed-rules/index.mdx
+++ b/src/content/docs/waf/managed-rules/index.mdx
@@ -81,4 +81,3 @@ This means a rule with a terminal action (such as Block or Managed Challenge) in
 ### WAF exceptions
 
 WAF exceptions (skip rules) are rules with a `skip` action deployed to the `http_request_firewall_managed` phase entry-point ruleset. They are evaluated in list order within the entry-point ruleset — a skip rule only bypasses `execute` rules listed after it. Place exceptions before the managed ruleset execute rules they are intended to skip. For more information, refer to [WAF exceptions](/waf/managed-rules/waf-exceptions/).
-
diff --git a/src/content/docs/waf/tools/index.mdx b/src/content/docs/waf/tools/index.mdx
index 2547f0abc231788..93bf5ec8fba60f0 100644
--- a/src/content/docs/waf/tools/index.mdx
+++ b/src/content/docs/waf/tools/index.mdx
@@ -12,7 +12,6 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-
 The Cloudflare WAF offers the following additional tools:
 
 <DirectoryListing />
diff --git a/src/content/docs/waf/tools/privacy-pass.mdx b/src/content/docs/waf/tools/privacy-pass.mdx
index dce774674951b17..253f4e8bd646159 100644
--- a/src/content/docs/waf/tools/privacy-pass.mdx
+++ b/src/content/docs/waf/tools/privacy-pass.mdx
@@ -7,7 +7,6 @@ source: https://support.cloudflare.com/hc/en-us/articles/115001992652-Using-Priv
 title: Privacy Pass
 tags:
   - Privacy
-
 ---
 
 [Privacy Pass](https://datatracker.ietf.org/wg/privacypass/about/) specifies an extensible protocol for creating and redeeming anonymous and transferable tokens. Its specification is maintained by the IETF.
@@ -15,7 +14,7 @@ Cloudflare provides "Silk - Privacy Pass Client". This is a Chrome and Firefox b
 
 For instance, a visitor IP address with poor reputation may receive a Cloudflare challenge page before gaining access to a Cloudflare-protected website. Privacy Pass allows the visitor to solve a challenge with or without interaction, depending on the device. Solving this challenge is coordinated with a third party attester in such a way that Cloudflare does not see the attestation method or the interaction, preserving visitors' privacy while maintaining a high level of security.
 
-***
+---
 
 ## Set up Privacy Pass
 
@@ -23,12 +22,12 @@ For instance, a visitor IP address with poor reputation may receive a Cloudflare
 
 Your end users should download the Privacy Pass extension for either Google Chrome or Firefox:
 
-* [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
-* [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
+- [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
+- [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
 
 The Privacy Pass code is [available on GitHub](https://github.com/cloudflare/pp-browser-extension). You can report any issues in this repository.
 
-***
+---
 
 ## Support for Privacy Pass v1 (legacy)
 
diff --git a/src/content/docs/waf/troubleshooting/faq.mdx b/src/content/docs/waf/troubleshooting/faq.mdx
index d7e6a3b09ec4447..a3a09ba5996df45 100644
--- a/src/content/docs/waf/troubleshooting/faq.mdx
+++ b/src/content/docs/waf/troubleshooting/faq.mdx
@@ -34,6 +34,7 @@ If you are using a regular expression, it is recommended that you test it with a
 If you have [SSL/TLS certificates](/ssl/) managed by Cloudflare, every time a certificate is issued or renewed, a [domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/dcv-flow/) must happen. When a certificate is in `pending_validation` state and there are valid DCV tokens in place, some Cloudflare security features such as [custom rules](/waf/custom-rules/) and [Managed Rules](/waf/managed-rules/) will be automatically disabled on specific DCV paths (for example, `/.well-known/pki-validation/` and `/.well-known/acme-challenge/`).
 
 These automatic bypasses do not appear in [Trace](/rules/trace-request/) results.
+
 ### Why have I been blocked?
 
 Cloudflare may block requests when it detects activity that could be unsafe. Common reasons include:
diff --git a/src/content/docs/waiting-room/about.mdx b/src/content/docs/waiting-room/about.mdx
index ae5c646b790822d..85b25d1bb61107e 100644
--- a/src/content/docs/waiting-room/about.mdx
+++ b/src/content/docs/waiting-room/about.mdx
@@ -6,10 +6,9 @@ products:
   - waiting-room
 sidebar:
   order: 2
-
 ---
 
-import { LinkButton, Render } from "~/components"
+import { LinkButton, Render } from "~/components";
 
 Waiting Room queues visitors when your traffic approaches a previously defined threshold that might otherwise bring an application down.
 
@@ -21,7 +20,6 @@ Once you have [created and activated a waiting room](/waiting-room/get-started/)
 
 - If a page is not experiencing heavy traffic, a visitor accesses the page directly.
 - If page traffic approaches a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
-
   - Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
   - While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
   - When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
@@ -47,4 +45,4 @@ The other factor is the Waiting Room state, which is maintained at the local dat
 
 The Waiting Room state is updated with global information every few seconds. We have a pipeline set up in Cloudflare [Durable Objects](/durable-objects/) that ensures changes in traffic get propagated around the world. This architecture ensures that we do not introduce additional latency, as well as that we are making decisions with as near-time accuracy as possible.
 
-For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
\ No newline at end of file
+For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
diff --git a/src/content/docs/waiting-room/additional-options/create-events.mdx b/src/content/docs/waiting-room/additional-options/create-events.mdx
index 123834ddd12dbc3..6fba618cbc22dd8 100644
--- a/src/content/docs/waiting-room/additional-options/create-events.mdx
+++ b/src/content/docs/waiting-room/additional-options/create-events.mdx
@@ -6,7 +6,6 @@ products:
 title: Create scheduled events
 sidebar:
   order: 4
-
 ---
 
 When you want to customize the behavior of a waiting room for a specific period of time — such as changing the queueing method or increasing the total active users — set up a **scheduled event**. You can do this from the dashboard or via the API.
@@ -21,7 +20,7 @@ Only some customers can support scheduled events with their waiting rooms. For m
 
 1. Within your application, go to **Traffic** > **Waiting Room**.
 
-2. Expand a waiting room  and select **Schedule event**.
+2. Expand a waiting room and select **Schedule event**.
 
 3. Customize the details for your event: name the event, add a description (optional), and select a Start Date Time and an End Date Time.
 
@@ -65,23 +64,21 @@ If you are using a [custom template](/waiting-room/how-to/customize-waiting-room
 
 :::note
 
-
 If you need to create overlapping events, use different waiting rooms.
 
-
 :::
 
 ### Parameters
 
 Though most parameters are identical to those in a regular waiting room, there are a few unique to creating an event. For a complete list of event settings, please refer to [Create an Event](/api/resources/waiting_rooms/subresources/events/methods/create/).
 
-* `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
-* `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
-* `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
-* `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
-* `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
-* `description`: A text description providing more detail about the event.
-* `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
+- `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
+- `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
+- `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
+- `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
+- `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
+- `description`: A text description providing more detail about the event.
+- `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
 
 ### Queueing methods
 
@@ -99,8 +96,8 @@ Users who reach your application **during the prequeue period** are [randomly as
 
 To set up a "lottery", include the [following parameters](#parameters) in your API request:
 
-* `prequeue_start_time`
-* `shuffle_at_event_start`
+- `prequeue_start_time`
+- `shuffle_at_event_start`
 
 ## Preview an event configuration
 
@@ -125,12 +122,12 @@ Follow these steps if you would like to deploy a scheduled maintenance page, wit
 1. [Create a waiting room](/waiting-room/how-to/create-waiting-room/) with [Passthrough](/waiting-room/reference/queueing-methods/#passthrough) queueing method enabled.
 2. Create a waiting room event for this room with [Reject](/waiting-room/reference/queueing-methods/#reject) queueing method enabled.
 
-After the scheduled event has ended, users will have access to your site.  You can end the maintenance window before the scheduled event is over by setting the event to disabled.
+After the scheduled event has ended, users will have access to your site. You can end the maintenance window before the scheduled event is over by setting the event to disabled.
 
 ## Other API commands
 
-| Function                                                          | Command  |
-| ----------------------------------------------------------------- | -------- |
-| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)   | `GET`    |
+| Function                                                                                | Command  |
+| --------------------------------------------------------------------------------------- | -------- |
+| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)      | `GET`    |
 | [List scheduled events](/api/resources/waiting_rooms/subresources/events/methods/list/) | `GET`    |
-| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)         | `DELETE` |
+| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)        | `DELETE` |
diff --git a/src/content/docs/waiting-room/additional-options/index.mdx b/src/content/docs/waiting-room/additional-options/index.mdx
index 92470e9cc3b208c..bd77dc9b14cc6ad 100644
--- a/src/content/docs/waiting-room/additional-options/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Beyond [creating a waiting room](/waiting-room/get-started/), you may want to further customize how your waiting room functions.
 
diff --git a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
index bd9c6161eebc229..8eac756e51d27f1 100644
--- a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
+++ b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
@@ -6,7 +6,6 @@ products:
 title: Combine with Cloudflare for SaaS
 sidebar:
   order: 7
-
 ---
 
 If your application is using a custom hostname — meaning your SaaS provider is using [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) — your application can support a waiting room.
diff --git a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
index 0f15a5bf0d091f7..c39b032cfdb8839 100644
--- a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Waiting Room Rules
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In this section, we will list the Waiting Room rules available.
 
diff --git a/src/content/docs/waiting-room/api-reference.mdx b/src/content/docs/waiting-room/api-reference.mdx
index b91d98532f5c31c..893bc601dbd2942 100644
--- a/src/content/docs/waiting-room/api-reference.mdx
+++ b/src/content/docs/waiting-room/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/waiting_rooms/methods/list/
 sidebar:
   order: 10
-
 ---
diff --git a/src/content/docs/waiting-room/glossary.mdx b/src/content/docs/waiting-room/glossary.mdx
index 5e0ec50ac37db3d..aa5be06af954401 100644
--- a/src/content/docs/waiting-room/glossary.mdx
+++ b/src/content/docs/waiting-room/glossary.mdx
@@ -4,10 +4,9 @@ pcx_content_type: glossary
 description: Definitions for terms used across Waiting Room documentation.
 products:
   - waiting-room
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Waiting Room documentation.
 
diff --git a/src/content/docs/waiting-room/how-to/control-user-session.mdx b/src/content/docs/waiting-room/how-to/control-user-session.mdx
index a8981dcd2100717..9f585b420804aa8 100644
--- a/src/content/docs/waiting-room/how-to/control-user-session.mdx
+++ b/src/content/docs/waiting-room/how-to/control-user-session.mdx
@@ -8,13 +8,13 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Adjust these settings to control how long a user can hold their place on your site after leaving the waiting room.
 
 ## Session duration
 
-Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes.  Each new request restarts a user’s time to stay active equal to **session duration**. 
+Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes. Each new request restarts a user’s time to stay active equal to **session duration**.
 
 ## Disable session renewal to limit browsing time
 
@@ -24,9 +24,9 @@ You can limit each user’s time on your site to only one session duration by ch
 
 To terminate a user's session when they perform a specific action, you can send a command to the waiting room using an HTTP header on the response from your origin. This command tells the waiting room to revoke the session of the user associated with the current response. This allows spots to open up more dynamically and may increase throughput from your queue.
 
-To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard. 
+To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard.
 To enable this feature through the [Cloudflare API](/api/resources/waiting_rooms/methods/update/), update the `enabled_origin_commands` property to include the value `”revoke”` in the list of enabled origin commands.
- 
+
 Then, to return a revocation origin command and revoke the user's session associated with the current request, add the `Cf-Waiting-Room-Command: revoke` HTTP header to the response from your origin.
 
 To get the number of sessions revoked, you can query `sessionsRevoked` metrics from your [Waiting Room analytics](/waiting-room/waiting-room-analytics/#graphql-analytics) data via GraphQL API.
diff --git a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
index ea279a612cbaf63..f826cb8f5c312f5 100644
--- a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
 title: Edit and delete waiting rooms
 sidebar:
   order: 5
-
 ---
 
 import { APIRequest } from "~/components";
@@ -41,36 +40,36 @@ For details about updating an active waiting room, refer to [Best practices](/wa
 [Replace](https://api.cloudflare.com#waiting-room-update-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="PUT"
-  json={{
-    name: "webshop-waiting-room",
-    host: "example.com",
-    new_users_per_minute: 200,
-    total_active_users: 300
-  }}
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="PUT"
+	json={{
+		name: "webshop-waiting-room",
+		host: "example.com",
+		new_users_per_minute: 200,
+		total_active_users: 300,
+	}}
 />
 
 [Update](https://api.cloudflare.com#waiting-room-patch-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="PATCH"
-  json={{
-    name: "webshop-waiting-room",
-    host: "example.com",
-    new_users_per_minute: 200,
-    total_active_users: 300
-  }}
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="PATCH"
+	json={{
+		name: "webshop-waiting-room",
+		host: "example.com",
+		new_users_per_minute: 200,
+		total_active_users: 300,
+	}}
 />
 
-
 You only need to include the fields you want to update in the payload of the PATCH request.
+
 ### Delete a waiting room
 
 Delete a waiting room by appending the following endpoint in the [Waiting Room API](https://api.cloudflare.com#waiting-room-delete-waiting-room) to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="DELETE"
-/>
\ No newline at end of file
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="DELETE"
+/>
diff --git a/src/content/docs/waiting-room/how-to/index.mdx b/src/content/docs/waiting-room/how-to/index.mdx
index be1f971a0c6909b..38bb6f03248845f 100644
--- a/src/content/docs/waiting-room/how-to/index.mdx
+++ b/src/content/docs/waiting-room/how-to/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Common tasks
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 When working with Cloudflare Waiting Room, you will commonly perform the following tasks:
 
diff --git a/src/content/docs/waiting-room/how-to/json-response.mdx b/src/content/docs/waiting-room/how-to/json-response.mdx
index 4851e4a1a5bc96a..71bc059dc58e13a 100644
--- a/src/content/docs/waiting-room/how-to/json-response.mdx
+++ b/src/content/docs/waiting-room/how-to/json-response.mdx
@@ -65,13 +65,11 @@ In a browser environment, the page automatically refreshes every `refreshInterva
 These are some of the places where the JSON-friendly response can be consumed (this list is not exhaustive):
 
 1. In a mobile app traffic
-
    - **Integrate Waiting Room variables** – Create a new template in your mobile app to receive the JSON response. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Allow cookies** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your mobile app will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Consume JSON data** - Make a request to the Waiting Room endpoint with the `Accept: application/json` header.
 
 2. Inside Cloudflare Workers (or in your own backend service)
-
    - **Integrate Waiting Room variables** – Expect a JSON response in your backend API. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Include cookies in the request header** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your backend API will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Enable JSON response** - Via the dashboard or via the API.
diff --git a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
index f17f0406cc79484..00fa24999781e3f 100644
--- a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
 title: Monitor waiting room status
 sidebar:
   order: 3
-
 ---
 
 import { APIRequest } from "~/components";
@@ -23,37 +22,37 @@ Open the **Waiting Room** dashboard to view the list of your waiting rooms.
 
 The **Status** column displays the current state of the waiting room:
 
-* **Not queueing**:
-  * Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
-  * Shows estimated number of users in the application.
-* **Queueing**:
-  * Waiting room enabled and sending visitors to waiting room.
-  * Shows estimated number of users in the queue.
-  * On hover, shows maximum wait time expected for users.
-* **Disabled**: The waiting room is suspended.
-* **Queue-all**:
-  * Forces all traffic to queue in the waiting room.
-  * On hover, shows estimated number of users in the queue.
+- **Not queueing**:
+  - Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
+  - Shows estimated number of users in the application.
+- **Queueing**:
+  - Waiting room enabled and sending visitors to waiting room.
+  - Shows estimated number of users in the queue.
+  - On hover, shows maximum wait time expected for users.
+- **Disabled**: The waiting room is suspended.
+- **Queue-all**:
+  - Forces all traffic to queue in the waiting room.
+  - On hover, shows estimated number of users in the queue.
 
 ## Status in the API
 
 [Check whether traffic is queueing in a configured waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) by appending the following endpoint to the Cloudflare API base URL:
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
-  method="GET"
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
+	method="GET"
 />
 
 The response is:
 
-* `queueing` if visitors are currently queueing in the waiting room.
-* `not_queueing` if the room is empty or if the waiting room is suspended.
+- `queueing` if visitors are currently queueing in the waiting room.
+- `not_queueing` if the room is empty or if the waiting room is suspended.
 
 To check whether a configured waiting room is suspended or whether the traffic is force-queued to the waiting room, append the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-  method="GET"
+	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+	method="GET"
 />
 
 The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/get/) for a configured waiting room:
@@ -88,13 +87,13 @@ The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/g
 
 The value of `suspended` indicates whether a waiting room is activated or suspended:
 
-* `false`: The waiting room is activated.
-* `true`: The waiting room is suspended.
+- `false`: The waiting room is activated.
+- `true`: The waiting room is suspended.
 
 The value of `queue_all` indicates whether all traffic is forced to queue in the waiting room:
 
-* `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
-* `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
+- `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
+- `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
 
 ## Queueing activation
 
@@ -108,5 +107,5 @@ To help prevent a waiting room from active queueing, increase the values for `ne
 
 :::note
 
-Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products. 
+Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products.
 :::
diff --git a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
index d8e1e831c020a7e..3f4ca5fb6eafa52 100644
--- a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
@@ -6,7 +6,6 @@ products:
   - waiting-room
 sidebar:
   order: 2
-
 ---
 
 When [configuring a waiting room](/waiting-room/how-to/create-waiting-room/), you need to indicate which pages the waiting room will cover.
@@ -21,8 +20,8 @@ You cannot add any hostname and path combinations already configured for another
 
 A single waiting room can be applied to multiple custom hostnames as long as the following is true:
 
-* The apex domain is the same between the custom hostnames
-* Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
+- The apex domain is the same between the custom hostnames
+- Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
 
 ## Custom hostnames
 
diff --git a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
index 3876ca31bccde46..5039172c35fa4e8 100644
--- a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
+++ b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
@@ -6,7 +6,6 @@ products:
 title: Access Waiting Room
 sidebar:
   order: 1
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,6 +14,6 @@ Use Cloudflare Waiting Room to create a holding area where users can queue to ac
 
 To access Waiting Room on the Cloudflare dashboard, go to the **Waiting Room** page.
 
-   <DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
+<DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
 
 Use the dashboard to [create, edit, update, and delete](/waiting-room/how-to/) waiting rooms.
diff --git a/src/content/docs/waiting-room/plans.mdx b/src/content/docs/waiting-room/plans.mdx
index 29189c6fe19e6d5..a4041473cdfc940 100644
--- a/src/content/docs/waiting-room/plans.mdx
+++ b/src/content/docs/waiting-room/plans.mdx
@@ -10,10 +10,9 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
-
 ---
 
-import { FeatureTable, Render } from "~/components"
+import { FeatureTable, Render } from "~/components";
 
 The features available for a waiting room depend on your plan type. You can only have **one plan** per zone.
 
diff --git a/src/content/docs/waiting-room/reference/configuration-settings.mdx b/src/content/docs/waiting-room/reference/configuration-settings.mdx
index 20481e7adaee0c6..0d6c313160fc12b 100644
--- a/src/content/docs/waiting-room/reference/configuration-settings.mdx
+++ b/src/content/docs/waiting-room/reference/configuration-settings.mdx
@@ -7,15 +7,18 @@ products:
 title: Configuration settings
 sidebar:
   order: 2
-
 ---
 
-import { Description, LinkButton } from "~/components"
+import { Description, LinkButton } from "~/components";
 
 You can customize a variety of options for your waiting rooms.
 
- <LinkButton variant="primary" href="#dashboard-settings">Dashboard settings</LinkButton> <LinkButton variant="secondary" href="#additional-details">Additional details</LinkButton>
-
+<LinkButton variant="primary" href="#dashboard-settings">
+	Dashboard settings
+</LinkButton>
+<LinkButton variant="secondary" href="#additional-details">
+	Additional details
+</LinkButton>
 
 ## Dashboard settings
 
diff --git a/src/content/docs/waiting-room/reference/index.mdx b/src/content/docs/waiting-room/reference/index.mdx
index 4567f07d6834f80..386e738762a9e82 100644
--- a/src/content/docs/waiting-room/reference/index.mdx
+++ b/src/content/docs/waiting-room/reference/index.mdx
@@ -8,10 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Use the following reference information when setting up and deploying your waiting rooms:
 
diff --git a/src/content/docs/waiting-room/reference/waiting-room-api.mdx b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
index cd9d3e20bb3a293..9d57a00c62e2a34 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-api.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
@@ -4,7 +4,6 @@ description: API commands for managing waiting rooms.
 products:
   - waiting-room
 title: API commands
-
 ---
 
 Cloudflare Waiting Room redirect visitors to virtual waiting rooms when they are trying to access web pages that have high volumes of traffic.
@@ -25,17 +24,17 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 ## Manage your waiting room
 
-| Operation                                                                 | Method + URL stub                                             | Notes                              |
-| ------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
-| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)     | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
-| [Create waiting room](/api/resources/waiting_rooms/methods/create/)   | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
-| [Waiting room details](/api/resources/waiting_rooms/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
-| [Update waiting room](/api/resources/waiting_rooms/methods/update/)   | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
-| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/)   | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
-| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)     | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
+| Operation                                                           | Method + URL stub                                             | Notes                              |
+| ------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
+| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)    | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
+| [Create waiting room](/api/resources/waiting_rooms/methods/create/) | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
+| [Waiting room details](/api/resources/waiting_rooms/methods/get/)   | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
+| [Update waiting room](/api/resources/waiting_rooms/methods/update/) | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
+| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/) | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
+| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)    | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
 
 ## Fetch the current status of a waiting room
 
-| Operation                                                                                        | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
-| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation                                                                                                   | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
+| ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [Get the current status of a waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}/status` | <ul><li>Returns <code>queueing</code> if the queue is activated (clients are put in the waiting room).</li><li>Returns <code>not\_queueing</code> if the queue is not activated or if the waiting room is suspended.</li></ul> |
diff --git a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
index fc575945d64c011..999050767f022fd 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
@@ -12,24 +12,22 @@ A waiting room only uses the `__cfwaitingroom` cookie when a visitor requests ac
 
 :::caution[Important:]
 
-
 Cloudflare Waiting Room requires the `__cfwaitingroom` cookie. When a waiting room is actively queueing, users cannot visit that host and path combination without enabling cookies.
 
-
 :::
 
 ## Cookie function
 
 The `__cfwaitingroom` cookie is used to:
 
-* Track a user's position in the waiting room queue and serve them in the correct order.
-* Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
-* To allow re-entry for a period of time (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
+- Track a user's position in the waiting room queue and serve them in the correct order.
+- Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
+- To allow re-entry for a period of time (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
 
 ## Cookie expiration time
 
-* While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
-* When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)).
+- While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
+- When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)).
 
 ## Customize cookie name
 
diff --git a/src/content/docs/waiting-room/troubleshooting.mdx b/src/content/docs/waiting-room/troubleshooting.mdx
index 79df5d5298f08bd..0ff28fdedd01e62 100644
--- a/src/content/docs/waiting-room/troubleshooting.mdx
+++ b/src/content/docs/waiting-room/troubleshooting.mdx
@@ -7,17 +7,16 @@ title: FAQ
 structured_data: true
 sidebar:
   order: 11
-
 ---
 
 Below you will find answers to our most commonly asked questions about the Waiting Room.
 
-* [Configuration](#configuration)
-* [Features and products](#features-and-products)
-* [User behavior](#user-behavior)
-* [Monitor your waiting room](#monitor-your-waiting-room)
+- [Configuration](#configuration)
+- [Features and products](#features-and-products)
+- [User behavior](#user-behavior)
+- [Monitor your waiting room](#monitor-your-waiting-room)
 
-***
+---
 
 ## Configuration
 
@@ -25,7 +24,6 @@ Below you will find answers to our most commonly asked questions about the Waiti
 
 Yes. For more details, refer to [Customize a waiting room](/waiting-room/how-to/customize-waiting-room/).
 
-
 ### Why does my waiting room look different than how I designed it?
 
 If you have [customized your waiting room template](/waiting-room/how-to/customize-waiting-room):
@@ -35,10 +33,8 @@ If you have [customized your waiting room template](/waiting-room/how-to/customi
 
 :::note[Note]
 
-
 Only Enterprise customers can customize the appearance of their waiting room.
 
-
 :::
 
 ### What can I update when my waiting room is actively queueing?
@@ -47,69 +43,51 @@ You can update a [waiting room's template](/waiting-room/how-to/customize-waitin
 
 You can also update the [configuration settings](/waiting-room/reference/configuration-settings) of a waiting room, but only make these changes when necessary. These changes may impact the estimated wait time shown to end users and cause unnecessary confusion.
 
-
-
-
 ## Features and products
 
 ### Which features are included in my Waiting Room plan?
 
 To check which features are available to different plan types, refer to [Plans](/waiting-room/plans/).
 
-
-
 ### How does Waiting Room interact with other Cloudflare products?
 
 Some Cloudflare products run before a waiting room acts on traffic:
 
-* DDoS Mitigation
-* Web Application Firewall (WAF)
-* Bot Management
-* Page Rules
+- DDoS Mitigation
+- Web Application Firewall (WAF)
+- Bot Management
+- Page Rules
 
 Other Cloudflare products run after a waiting room acts on traffic:
 
-* Workers
-
-
-
+- Workers
 
 ## User behavior
 
-
 ### What happens if a user refreshes their tab when in a waiting room?
 
 A manual tab refresh has no effect on a user's position in your waiting room.
 
 However, if they close their tab and then try to access the application again during active queueing, they will lose their spot and have to go to the back of the queue.
 
-
 ### What happens if a queued user leaves the queue?
 
 When a user joins the queue, they are placed into a bucket which is their general position in line. When a user leaves the queue (closes the browser or tab), their place in line is held for five minutes after the last refresh. This grace period allows users to keep their position in line if they experience a brief disconnection. After five minutes, the grace period expires and they are no longer counted as waiting in the queue.
 
-
-
 ## Monitor your waiting room
 
-
 ### Why do I observe a few users being queued in the dashboard?
 
-
 Some users might be queued before your waiting room reaches is limit due to architectural designs. For more details on the behavior and how to fix it, refer to [​​Queueing activation](/waiting-room/how-to/monitor-waiting-room#queueing-activation).
 
-
-
 ### Why are some users not being queued in my waiting room?
 
-
 If you notice users not being queued to your waiting room, make sure the path you defined exactly matches the path of your website.
 
 The path is case-sensitive, so if you have a waiting room set up for `/Black-Friday-Sale` and users go to `/black-friday-sale`, they will bypass your waiting room.
 
 For more details, refer to [Best practices](/waiting-room/reference/best-practices).
 
-
 ### Why are users being blocked from entering my waiting room?
 
 If you have Rate Limiting, check your [rate limiting rules](/waf/rate-limiting-rules/).
@@ -118,17 +96,15 @@ The Waiting Room queue page refreshes every 20 seconds by populating the refresh
 
 Your user also might not have [cookies](/waiting-room/reference/waiting-room-cookie) enabled. If they do not enable cookies and your waiting room is actively queueing traffic, they will not reach your endpoint until the queueing stops.
 
-
 ### Why is the estimated wait time increasing for some users?
 
 Estimated wait times may increase if the rate of users leaving your site decreases. The estimated wait time is updated upon each page refresh based on the most recently available information about the rate of slots opening up on your site and the number of users ahead of the user in line. To make this increase less likely, you could limit the amount of time users are allowed to spend on your site by disabling session renewal. Be aware that, if you change your traffic settings, estimated wait times will change as well.
 
-
 ### Why is `new users per minute` low when there is capacity available?
 
 The `new users per minute` metric tracks how many users were accepted to the origin in the last minute. It is only incremented when a queued user refreshes and is accepted to the origin. If the waiting room queueing method is set to `fifo`, we will wait until all queued users in a minute-based bucket are accepted before moving to the next bucket. If many of the users in a bucket have abandoned the queue, then the waiting room must wait until their place in line expires before moving on to the next bucket. This can cause `new users per minute` to be low when only a small percentage of queued users are actually still waiting.
 
-This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting  them in an infinite queue.
+This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting them in an infinite queue.
 
 ### Why are my Waiting Room analytics and Google analytics not matching?
 
@@ -142,8 +118,8 @@ Another key difference is that Waiting Room runs on requests made to the origin,
 
 ### Why did my traffic exceed the New Users Per Minute threshold?
 
-Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally. 
+Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally.
 
 In the case of a rapid spike — rising to several thousand users within a minute — the global state propagation process takes approximately two minutes, resulting in a delay before all data centers become aware of the spike. If this information is not disseminated quickly enough to other locations, temporary overshooting may occur, particularly when lower limits are in place.
 
-This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
\ No newline at end of file
+This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
diff --git a/src/content/docs/warp-client/get-started/linux.mdx b/src/content/docs/warp-client/get-started/linux.mdx
index 8aaf86985cb9983..5d816a7dfe1846d 100644
--- a/src/content/docs/warp-client/get-started/linux.mdx
+++ b/src/content/docs/warp-client/get-started/linux.mdx
@@ -78,19 +78,20 @@ To enable [WARP+ Unlimited](/warp-client/warp-modes/#warp-unlimited) on Linux, y
 2. Go to **Settings** > **Account** and copy the **Key** value.
 3. On your Linux device, run the following command:
 
-	```sh
-	warp-cli registration license <KEY>
-	```
+   ```sh
+   warp-cli registration license <KEY>
+   ```
+
 4. Verify the new registration:
 
-	```sh
-	warp-cli registration show
-	```
+   ```sh
+   warp-cli registration show
+   ```
 
-	```sh output
-	Account type: Unlimited
-	...
-	```
+   ```sh output
+   Account type: Unlimited
+   ...
+   ```
 
 Your WARP+ Unlimited subscription is now active on this device.
 
diff --git a/src/content/docs/warp-client/known-issues-and-faq.mdx b/src/content/docs/warp-client/known-issues-and-faq.mdx
index b4e0b7837fc2175..3f43023c46ff622 100644
--- a/src/content/docs/warp-client/known-issues-and-faq.mdx
+++ b/src/content/docs/warp-client/known-issues-and-faq.mdx
@@ -7,7 +7,6 @@ products:
 structured_data: true
 sidebar:
   order: 5
-
 ---
 
 Below you will find answers to our most commonly asked questions regarding the WARP client. If you cannot find the answer you are looking for, refer to the [community page](https://community.cloudflare.com/) to explore more resources.
@@ -16,9 +15,9 @@ Below you will find answers to our most commonly asked questions regarding the W
 
 As our [Network Map](https://www.cloudflare.com/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the server you are connecting to is not necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-* We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
-* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
-* Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
+- We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
+- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+- Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
 
 ## Does WARP reveal my IP address to websites I visit?
 
@@ -36,7 +35,6 @@ Cloudflare WARP is in part powered by [1.1.1.1](/1.1.1.1/), the world's fastest
 
 Cloudflare WARP and the 1.1.1.1 with WARP applications go through performance testing that includes battery, network and CPU on a regular basis. In addition, both applications are used by millions of users worldwide that help us stay on top of issues across a wide variety of devices, networks, sites and applications.
 
-
 ## What is the version of .NET Framework required for the Windows client?
 
 The WARP client for Windows requires .NET Framework version 4.7.2 or later to be installed on your computer.
diff --git a/src/content/docs/warp-client/legal/3rdparty.mdx b/src/content/docs/warp-client/legal/3rdparty.mdx
index 10a5097703b90b5..26189309784c944 100644
--- a/src/content/docs/warp-client/legal/3rdparty.mdx
+++ b/src/content/docs/warp-client/legal/3rdparty.mdx
@@ -5,14 +5,13 @@ pcx_content_type: reference
 description: Third-party licenses used in the WARP client.
 products:
   - warp-client
-
 ---
 
 Following is the third party license information for our desktop applications. License information for our iOS and Android clients can be found in-app.
 
 ## Windows
 
-* ### NetSparkle
+- ### NetSparkle
 
 Copyright (c) 2020 Deadpikle
 
@@ -20,7 +19,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### Reactive Extensions
+- ### Reactive Extensions
 
 Copyright (c) .NET Foundation and Contributors
 
@@ -28,7 +27,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### NLog
+- ### NLog
 
 Copyright (c) 2016, NLog
 
@@ -40,7 +39,7 @@ Redistribution and use in source and binary forms, with or without modification,
 
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### Visual Studio App Center SDK for .NET
+- ### Visual Studio App Center SDK for .NET
 
 Copyright (c) Microsoft Corporation
 
@@ -50,9 +49,9 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### Font-Awesome-WPF
+- ### Font-Awesome-WPF
 
 Copyright (c) 2014-2016 charri
 
@@ -62,7 +61,7 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### WpfScreenHelper
+- ### WpfScreenHelper
 
 Copyright (c) 2014 Michael Denny
 
@@ -74,7 +73,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ## Mac
 
-* ### Sparkle
+- ### Sparkle
 
 Copyright (c) 2006-2013 Andy Matuschak.
 Copyright (c) 2009-2013 Elgato Systems GmbH.
@@ -89,7 +88,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### ITSwitch
+- ### ITSwitch
 
 Copyright 2014 Ilija Tovilo
 
@@ -99,7 +98,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-* ### Visual Studio App Center SDK for Apple platforms
+- ### Visual Studio App Center SDK for Apple platforms
 
 Copyright (c) Microsoft Corporation
 
@@ -109,7 +108,7 @@ MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ## Rust
 
@@ -119,22 +118,21 @@ This section lists the licenses of the projects used in cargo-about.
 
 Overview of licenses:
 
-* [MIT](#mit-license) (54)
-* [Apache](#apache-license-20) (41)
-* [BSD](#bsd-3-clause-new-or-revised-license) (8)
-* [BSD](#bsd-2-clause-simplified-license) (3)
-* [ISC](#isc-license) (3)
-* [BSD](#bsd-zero-clause-license) (2)
-* [Mozilla](#mozilla-public-license-20) (2)
-* [OpenSSL](#openssl-license) (1)
+- [MIT](#mit-license) (54)
+- [Apache](#apache-license-20) (41)
+- [BSD](#bsd-3-clause-new-or-revised-license) (8)
+- [BSD](#bsd-2-clause-simplified-license) (3)
+- [ISC](#isc-license) (3)
+- [BSD](#bsd-zero-clause-license) (2)
+- [Mozilla](#mozilla-public-license-20) (2)
+- [OpenSSL](#openssl-license) (1)
 
 All license text:
 
-* ### BSD Zero Clause License
+- ### BSD Zero Clause License
 
   #### Used by:
-
-  * [managed](https://github.com/m-labs/rust-managed.git)
+  - [managed](https://github.com/m-labs/rust-managed.git)
 
   Copyright (C) 2017 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -149,11 +147,10 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### BSD Zero Clause License
+- ### BSD Zero Clause License
 
   #### Used by:
-
-  * [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
+  - [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
 
   Copyright (C) 2016 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -168,136 +165,135 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [addr](https://github.com/addr-rs/addr)
-  * [addr2line](https://github.com/gimli-rs/addr2line)
-  * [anyhow](https://github.com/dtolnay/anyhow)
-  * [arc-swap](https://github.com/vorner/arc-swap)
-  * [async-trait](https://github.com/dtolnay/async-trait)
-  * [autocfg](https://github.com/cuviper/autocfg)
-  * [backoff](https://github.com/ihrwein/backoff)
-  * [backtrace](https://github.com/rust-lang/backtrace-rs)
-  * [base64](https://github.com/marshallpierce/rust-base64)
-  * [bitflags](https://github.com/bitflags/bitflags)
-  * [bumpalo](https://github.com/fitzgen/bumpalo)
-  * [bzip2](https://github.com/alexcrichton/bzip2-rs)
-  * [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
-  * [cache-padded](https://github.com/stjepang/cache-padded)
-  * [cc](https://github.com/alexcrichton/cc-rs)
-  * [cfg-if](https://github.com/alexcrichton/cfg-if)
-  * [concurrent-queue](https://github.com/stjepang/concurrent-queue)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  * [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
-  * [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
-  * [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
-  * [ct-logs](https://github.com/ctz/ct-logs)
-  * [either](https://github.com/bluss/either)
-  * [errno](https://github.com/lambda-fairy/rust-errno)
-  * [error-chain](https://github.com/rust-lang-nursery/error-chain)
-  * [event-listener](https://github.com/stjepang/event-listener)
-  * [flate2](https://github.com/rust-lang/flate2-rs)
-  * [fnv](https://github.com/servo/rust-fnv)
-  * [form\_urlencoded](https://github.com/servo/rust-url)
-  * [gcc](https://github.com/alexcrichton/gcc-rs)
-  * [getopts](https://github.com/rust-lang/getopts)
-  * [gimli](https://github.com/gimli-rs/gimli)
-  * [hashbrown](https://github.com/rust-lang/hashbrown)
-  * [heck](https://github.com/withoutboats/heck)
-  * [hermit-abi](https://github.com/hermitcore/libhermit-rs)
-  * [httparse](https://github.com/seanmonstar/httparse)
-  * [hyper-rustls](https://github.com/ctz/hyper-rustls)
-  * [idna](https://github.com/servo/rust-url/)
-  * [indexmap](https://github.com/bluss/indexmap)
-  * [itoa](https://github.com/dtolnay/itoa)
-  * [jni](https://github.com/jni-rs/jni-rs)
-  * [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
-  * [lazy\_static](https://github.com/rust-lang-nursery/lazy-static.rs)
-  * [libc](https://github.com/rust-lang/libc)
-  * [lock\_api](https://github.com/Amanieu/parking_lot)
-  * [match\_cfg](https://github.com/gnzlbg/match_cfg)
-  * [mime](https://github.com/hyperium/mime)
-  * [miow](https://github.com/yoshuawuyts/miow)
-  * [num](https://github.com/rust-num/num)
-  * [num](https://github.com/rust-num/num)
-  * [num-bigint](https://github.com/rust-num/num-bigint)
-  * [num-complex](https://github.com/rust-num/num-complex)
-  * [num-complex](https://github.com/rust-num/num-complex)
-  * [num-integer](https://github.com/rust-num/num-integer)
-  * [num-iter](https://github.com/rust-num/num-iter)
-  * [num-rational](https://github.com/rust-num/num-rational)
-  * [num-rational](https://github.com/rust-num/num-rational)
-  * [num-traits](https://github.com/rust-num/num-traits)
-  * [num\_cpus](https://github.com/seanmonstar/num_cpus)
-  * [object](https://github.com/gimli-rs/object)
-  * [once\_cell](https://github.com/matklad/once_cell)
-  * [openssl-probe](https://github.com/alexcrichton/openssl-probe)
-  * [parking\_lot](https://github.com/Amanieu/parking_lot)
-  * [parking\_lot\_core](https://github.com/Amanieu/parking_lot)
-  * [paste](https://github.com/dtolnay/paste)
-  * [percent-encoding](https://github.com/servo/rust-url/)
-  * [pfctl](https://github.com/mullvad/pfctl-rs)
-  * [pkg-config](https://github.com/rust-lang/pkg-config-rs)
-  * [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
-  * [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
-  * [proc-macro2](https://github.com/alexcrichton/proc-macro2)
-  * [quote](https://github.com/dtolnay/quote)
-  * [regex](https://github.com/rust-lang/regex)
-  * [regex-syntax](https://github.com/rust-lang/regex)
-  * [reqwest](https://github.com/seanmonstar/reqwest)
-  * [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
-  * [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
-  * [rustversion](https://github.com/dtolnay/rustversion)
-  * [scopeguard](https://github.com/bluss/scopeguard)
-  * [sct](https://github.com/ctz/sct.rs)
-  * [secret-service](https://github.com/hwchen/secret-service-rs.git)
-  * [semver](https://github.com/dtolnay/semver)
-  * [serde](https://github.com/serde-rs/serde)
-  * [serde\_derive](https://github.com/serde-rs/serde)
-  * [serde\_json](https://github.com/serde-rs/json)
-  * [serde\_repr](https://github.com/dtolnay/serde-repr)
-  * [signal-hook-registry](https://github.com/vorner/signal-hook)
-  * [size\_format](https://github.com/aticu/size_format)
-  * [slog](https://github.com/slog-rs/slog)
-  * [slog-async](https://github.com/slog-rs/async)
-  * [slog-scope](https://github.com/slog-rs/scope)
-  * [slog-stdlog](https://github.com/slog-rs/stdlog)
-  * [slog-term](https://github.com/slog-rs/term)
-  * [smallvec](https://github.com/servo/rust-smallvec)
-  * [socket2](https://github.com/alexcrichton/socket2-rs)
-  * [socket2](https://github.com/rust-lang/socket2)
-  * [syn](https://github.com/dtolnay/syn)
-  * [tempfile](https://github.com/Stebalien/tempfile)
-  * [term](https://github.com/Stebalien/term)
-  * [thiserror](https://github.com/dtolnay/thiserror)
-  * [thiserror-impl](https://github.com/dtolnay/thiserror)
-  * [thread\_local](https://github.com/Amanieu/thread_local-rs)
-  * [time](https://github.com/time-rs/time)
-  * [toml](https://github.com/alexcrichton/toml-rs)
-  * [tungstenite](https://github.com/snapview/tungstenite-rs)
-  * [unicode-bidi](https://github.com/servo/unicode-bidi)
-  * [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
-  * [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
-  * [unicode-width](https://github.com/unicode-rs/unicode-width)
-  * [unicode-xid](https://github.com/unicode-rs/unicode-xid)
-  * [url](https://github.com/servo/rust-url)
-  * [version\_check](https://github.com/SergioBenitez/version_check)
-  * [wasi](https://github.com/bytecodealliance/wasi)
-  * [wasi](https://github.com/bytecodealliance/wasi)
-  * [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
-  * [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
-  * [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
-  * [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
-  * [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
-  * [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
-  * [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
+  - [addr](https://github.com/addr-rs/addr)
+  - [addr2line](https://github.com/gimli-rs/addr2line)
+  - [anyhow](https://github.com/dtolnay/anyhow)
+  - [arc-swap](https://github.com/vorner/arc-swap)
+  - [async-trait](https://github.com/dtolnay/async-trait)
+  - [autocfg](https://github.com/cuviper/autocfg)
+  - [backoff](https://github.com/ihrwein/backoff)
+  - [backtrace](https://github.com/rust-lang/backtrace-rs)
+  - [base64](https://github.com/marshallpierce/rust-base64)
+  - [bitflags](https://github.com/bitflags/bitflags)
+  - [bumpalo](https://github.com/fitzgen/bumpalo)
+  - [bzip2](https://github.com/alexcrichton/bzip2-rs)
+  - [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
+  - [cache-padded](https://github.com/stjepang/cache-padded)
+  - [cc](https://github.com/alexcrichton/cc-rs)
+  - [cfg-if](https://github.com/alexcrichton/cfg-if)
+  - [concurrent-queue](https://github.com/stjepang/concurrent-queue)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  - [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
+  - [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
+  - [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
+  - [ct-logs](https://github.com/ctz/ct-logs)
+  - [either](https://github.com/bluss/either)
+  - [errno](https://github.com/lambda-fairy/rust-errno)
+  - [error-chain](https://github.com/rust-lang-nursery/error-chain)
+  - [event-listener](https://github.com/stjepang/event-listener)
+  - [flate2](https://github.com/rust-lang/flate2-rs)
+  - [fnv](https://github.com/servo/rust-fnv)
+  - [form_urlencoded](https://github.com/servo/rust-url)
+  - [gcc](https://github.com/alexcrichton/gcc-rs)
+  - [getopts](https://github.com/rust-lang/getopts)
+  - [gimli](https://github.com/gimli-rs/gimli)
+  - [hashbrown](https://github.com/rust-lang/hashbrown)
+  - [heck](https://github.com/withoutboats/heck)
+  - [hermit-abi](https://github.com/hermitcore/libhermit-rs)
+  - [httparse](https://github.com/seanmonstar/httparse)
+  - [hyper-rustls](https://github.com/ctz/hyper-rustls)
+  - [idna](https://github.com/servo/rust-url/)
+  - [indexmap](https://github.com/bluss/indexmap)
+  - [itoa](https://github.com/dtolnay/itoa)
+  - [jni](https://github.com/jni-rs/jni-rs)
+  - [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
+  - [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs)
+  - [libc](https://github.com/rust-lang/libc)
+  - [lock_api](https://github.com/Amanieu/parking_lot)
+  - [match_cfg](https://github.com/gnzlbg/match_cfg)
+  - [mime](https://github.com/hyperium/mime)
+  - [miow](https://github.com/yoshuawuyts/miow)
+  - [num](https://github.com/rust-num/num)
+  - [num](https://github.com/rust-num/num)
+  - [num-bigint](https://github.com/rust-num/num-bigint)
+  - [num-complex](https://github.com/rust-num/num-complex)
+  - [num-complex](https://github.com/rust-num/num-complex)
+  - [num-integer](https://github.com/rust-num/num-integer)
+  - [num-iter](https://github.com/rust-num/num-iter)
+  - [num-rational](https://github.com/rust-num/num-rational)
+  - [num-rational](https://github.com/rust-num/num-rational)
+  - [num-traits](https://github.com/rust-num/num-traits)
+  - [num_cpus](https://github.com/seanmonstar/num_cpus)
+  - [object](https://github.com/gimli-rs/object)
+  - [once_cell](https://github.com/matklad/once_cell)
+  - [openssl-probe](https://github.com/alexcrichton/openssl-probe)
+  - [parking_lot](https://github.com/Amanieu/parking_lot)
+  - [parking_lot_core](https://github.com/Amanieu/parking_lot)
+  - [paste](https://github.com/dtolnay/paste)
+  - [percent-encoding](https://github.com/servo/rust-url/)
+  - [pfctl](https://github.com/mullvad/pfctl-rs)
+  - [pkg-config](https://github.com/rust-lang/pkg-config-rs)
+  - [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
+  - [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
+  - [proc-macro2](https://github.com/alexcrichton/proc-macro2)
+  - [quote](https://github.com/dtolnay/quote)
+  - [regex](https://github.com/rust-lang/regex)
+  - [regex-syntax](https://github.com/rust-lang/regex)
+  - [reqwest](https://github.com/seanmonstar/reqwest)
+  - [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
+  - [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
+  - [rustversion](https://github.com/dtolnay/rustversion)
+  - [scopeguard](https://github.com/bluss/scopeguard)
+  - [sct](https://github.com/ctz/sct.rs)
+  - [secret-service](https://github.com/hwchen/secret-service-rs.git)
+  - [semver](https://github.com/dtolnay/semver)
+  - [serde](https://github.com/serde-rs/serde)
+  - [serde_derive](https://github.com/serde-rs/serde)
+  - [serde_json](https://github.com/serde-rs/json)
+  - [serde_repr](https://github.com/dtolnay/serde-repr)
+  - [signal-hook-registry](https://github.com/vorner/signal-hook)
+  - [size_format](https://github.com/aticu/size_format)
+  - [slog](https://github.com/slog-rs/slog)
+  - [slog-async](https://github.com/slog-rs/async)
+  - [slog-scope](https://github.com/slog-rs/scope)
+  - [slog-stdlog](https://github.com/slog-rs/stdlog)
+  - [slog-term](https://github.com/slog-rs/term)
+  - [smallvec](https://github.com/servo/rust-smallvec)
+  - [socket2](https://github.com/alexcrichton/socket2-rs)
+  - [socket2](https://github.com/rust-lang/socket2)
+  - [syn](https://github.com/dtolnay/syn)
+  - [tempfile](https://github.com/Stebalien/tempfile)
+  - [term](https://github.com/Stebalien/term)
+  - [thiserror](https://github.com/dtolnay/thiserror)
+  - [thiserror-impl](https://github.com/dtolnay/thiserror)
+  - [thread_local](https://github.com/Amanieu/thread_local-rs)
+  - [time](https://github.com/time-rs/time)
+  - [toml](https://github.com/alexcrichton/toml-rs)
+  - [tungstenite](https://github.com/snapview/tungstenite-rs)
+  - [unicode-bidi](https://github.com/servo/unicode-bidi)
+  - [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
+  - [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
+  - [unicode-width](https://github.com/unicode-rs/unicode-width)
+  - [unicode-xid](https://github.com/unicode-rs/unicode-xid)
+  - [url](https://github.com/servo/rust-url)
+  - [version_check](https://github.com/SergioBenitez/version_check)
+  - [wasi](https://github.com/bytecodealliance/wasi)
+  - [wasi](https://github.com/bytecodealliance/wasi)
+  - [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
+  - [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
+  - [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
+  - [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
+  - [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
+  - [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
+  - [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
 
     ```
                           Apache License
@@ -306,7 +302,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -505,11 +500,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [adler](https://github.com/jonas-schievink/adler.git)
+  - [adler](https://github.com/jonas-schievink/adler.git)
 
     ```
                           Apache License
@@ -518,7 +512,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -717,33 +710,32 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [aes](https://github.com/RustCrypto/block-ciphers)
-  * [aes-soft](https://github.com/RustCrypto/block-ciphers)
-  * [aesni](https://github.com/RustCrypto/block-ciphers)
-  * [block-buffer](https://github.com/RustCrypto/utils)
-  * [block-buffer](https://github.com/RustCrypto/utils)
-  * [block-modes](https://github.com/RustCrypto/block-ciphers)
-  * [block-padding](https://github.com/RustCrypto/utils)
-  * [block-padding](https://github.com/RustCrypto/utils)
-  * [byte-tools](https://github.com/RustCrypto/utils)
-  * [cipher](https://github.com/RustCrypto/traits)
-  * [cpufeatures](https://github.com/RustCrypto/utils)
-  * [crypto-mac](https://github.com/RustCrypto/traits)
-  * [crypto-mac](https://github.com/RustCrypto/traits)
-  * [digest](https://github.com/RustCrypto/traits)
-  * [digest](https://github.com/RustCrypto/traits)
-  * [fake-simd](https://github.com/RustCrypto/utils)
-  * [hmac](https://github.com/RustCrypto/MACs)
-  * [hmac](https://github.com/RustCrypto/MACs)
-  * [opaque-debug](https://github.com/RustCrypto/utils)
-  * [opaque-debug](https://github.com/RustCrypto/utils)
-  * [sha-1](https://github.com/RustCrypto/hashes)
-  * [sha2](https://github.com/RustCrypto/hashes)
-  * [sha2](https://github.com/RustCrypto/hashes)
+  - [aes](https://github.com/RustCrypto/block-ciphers)
+  - [aes-soft](https://github.com/RustCrypto/block-ciphers)
+  - [aesni](https://github.com/RustCrypto/block-ciphers)
+  - [block-buffer](https://github.com/RustCrypto/utils)
+  - [block-buffer](https://github.com/RustCrypto/utils)
+  - [block-modes](https://github.com/RustCrypto/block-ciphers)
+  - [block-padding](https://github.com/RustCrypto/utils)
+  - [block-padding](https://github.com/RustCrypto/utils)
+  - [byte-tools](https://github.com/RustCrypto/utils)
+  - [cipher](https://github.com/RustCrypto/traits)
+  - [cpufeatures](https://github.com/RustCrypto/utils)
+  - [crypto-mac](https://github.com/RustCrypto/traits)
+  - [crypto-mac](https://github.com/RustCrypto/traits)
+  - [digest](https://github.com/RustCrypto/traits)
+  - [digest](https://github.com/RustCrypto/traits)
+  - [fake-simd](https://github.com/RustCrypto/utils)
+  - [hmac](https://github.com/RustCrypto/MACs)
+  - [hmac](https://github.com/RustCrypto/MACs)
+  - [opaque-debug](https://github.com/RustCrypto/utils)
+  - [opaque-debug](https://github.com/RustCrypto/utils)
+  - [sha-1](https://github.com/RustCrypto/hashes)
+  - [sha2](https://github.com/RustCrypto/hashes)
+  - [sha2](https://github.com/RustCrypto/hashes)
 
     ```
                           Apache License
@@ -752,7 +744,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -949,18 +940,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ascii](https://github.com/tomprogrammer/rust-ascii)
+  - [ascii](https://github.com/tomprogrammer/rust-ascii)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1161,15 +1150,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [async-channel](https://github.com/smol-rs/async-channel)
-  * [ipconfig](https://github.com/liranringel/ipconfig)
-  * [log](https://github.com/rust-lang/log)
-  * [safemem](https://github.com/abonander/safemem)
-  * [uuid](https://github.com/uuid-rs/uuid)
+  - [async-channel](https://github.com/smol-rs/async-channel)
+  - [ipconfig](https://github.com/liranringel/ipconfig)
+  - [log](https://github.com/rust-lang/log)
+  - [safemem](https://github.com/abonander/safemem)
+  - [uuid](https://github.com/uuid-rs/uuid)
 
     ```
                           Apache License
@@ -1178,7 +1166,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1377,32 +1364,30 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [cesu8](https://github.com/emk/cesu8-rs)
-  * [ident\_case](https://github.com/TedDriggs/ident_case)
-  * [ioctl-sys](https://github.com/jmesmon/ioctl)
-  * [psl](https://github.com/addr-rs/psl)
-  * [psl-types](https://github.com/addr-rs/psl-types)
-  * [rustls](https://github.com/ctz/rustls)
-  * [security-framework](https://github.com/kornelski/rust-security-framework)
-  * [security-framework](https://github.com/kornelski/rust-security-framework)
-  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  * [system-configuration](https://github.com/mullvad/system-configuration-rs)
-  * [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
-  * [tinyvec\_macros](https://github.com/Soveu/tinyvec_macros)
-  * [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
-  * [winapi-x86\_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  - [cesu8](https://github.com/emk/cesu8-rs)
+  - [ident_case](https://github.com/TedDriggs/ident_case)
+  - [ioctl-sys](https://github.com/jmesmon/ioctl)
+  - [psl](https://github.com/addr-rs/psl)
+  - [psl-types](https://github.com/addr-rs/psl-types)
+  - [rustls](https://github.com/ctz/rustls)
+  - [security-framework](https://github.com/kornelski/rust-security-framework)
+  - [security-framework](https://github.com/kornelski/rust-security-framework)
+  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  - [system-configuration](https://github.com/mullvad/system-configuration-rs)
+  - [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
+  - [tinyvec_macros](https://github.com/Soveu/tinyvec_macros)
+  - [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  - [winapi-x86_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
@@ -1424,7 +1409,6 @@ All license text:
   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
 
   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
-
   2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
 
   3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
@@ -1471,11 +1455,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [chrono](https://github.com/chronotope/chrono)
+  - [chrono](https://github.com/chronotope/chrono)
 
   Rust-chrono is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2]. Copyright (c) 2014--2017, Kang Seonghoon and
@@ -1715,24 +1698,23 @@ All license text:
   limitations under the License.
   ```
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [crc32fast](https://github.com/srijs/rust-crc32fast)
-  * [derive\_builder](https://github.com/colin-kiegel/rust-derive-builder)
-  * [derive\_builder\_core](https://github.com/colin-kiegel/rust-derive-builder)
-  * [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
-  * [hex](https://github.com/KokaKiwi/rust-hex)
-  * [jni-sys](https://github.com/sfackler/rust-jni-sys)
-  * [log-panics](https://github.com/sfackler/rust-log-panics)
-  * [quick-error](http://github.com/tailhook/quick-error)
-  * [resolv-conf](http://github.com/tailhook/resolv-conf)
-  * [trust-dns-https](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
-  * [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
-  * [unreachable](https://github.com/reem/rust-unreachable.git)
+  - [crc32fast](https://github.com/srijs/rust-crc32fast)
+  - [derive_builder](https://github.com/colin-kiegel/rust-derive-builder)
+  - [derive_builder_core](https://github.com/colin-kiegel/rust-derive-builder)
+  - [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
+  - [hex](https://github.com/KokaKiwi/rust-hex)
+  - [jni-sys](https://github.com/sfackler/rust-jni-sys)
+  - [log-panics](https://github.com/sfackler/rust-log-panics)
+  - [quick-error](http://github.com/tailhook/quick-error)
+  - [resolv-conf](http://github.com/tailhook/resolv-conf)
+  - [trust-dns-https](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
+  - [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
+  - [unreachable](https://github.com/reem/rust-unreachable.git)
 
     ```
                              Apache License
@@ -1741,7 +1723,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1942,18 +1923,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dbus](https://github.com/diwic/dbus-rs)
+  - [dbus](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2154,19 +2133,17 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dbus](https://github.com/diwic/dbus-rs)
-  * [libdbus-sys](https://github.com/diwic/dbus-rs)
+  - [dbus](https://github.com/diwic/dbus-rs)
+  - [libdbus-sys](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2367,11 +2344,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [deadqueue](https://github.com/bikeshedder/deadqueue)
+  - [deadqueue](https://github.com/bikeshedder/deadqueue)
 
     ```
                              Apache License
@@ -2380,7 +2356,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2581,13 +2556,12 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [diff](https://github.com/utkarshkukreti/diff.rs)
-  * [ipnetwork](https://github.com/achanda/ipnetwork)
-  * [winapi](https://github.com/retep998/winapi-rs)
+  - [diff](https://github.com/utkarshkukreti/diff.rs)
+  - [ipnetwork](https://github.com/achanda/ipnetwork)
+  - [winapi](https://github.com/retep998/winapi-rs)
 
     ```
                              Apache License
@@ -2596,7 +2570,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2797,14 +2770,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [dirs](https://github.com/soc/dirs-rs)
-  * [dirs-next](https://github.com/xdg-rs/dirs)
-  * [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
-  * [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
+  - [dirs](https://github.com/soc/dirs-rs)
+  - [dirs-next](https://github.com/xdg-rs/dirs)
+  - [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
+  - [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
 
     ```
                           Apache License
@@ -2813,7 +2785,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2983,12 +2954,11 @@ All license text:
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [encoding\_rs](https://github.com/hsivonen/encoding_rs)
-  * [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
+  - [encoding_rs](https://github.com/hsivonen/encoding_rs)
+  - [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
 
     ```
                              Apache License
@@ -2997,7 +2967,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3198,11 +3167,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [err-derive](https://gitlab.com/torkleyy/err-derive)
+  - [err-derive](https://gitlab.com/torkleyy/err-derive)
 
     ```
                              Apache License
@@ -3211,7 +3179,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3412,19 +3379,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [futures](https://github.com/rust-lang/futures-rs)
-  * [futures-channel](https://github.com/rust-lang/futures-rs)
-  * [futures-core](https://github.com/rust-lang/futures-rs)
-  * [futures-executor](https://github.com/rust-lang/futures-rs)
-  * [futures-io](https://github.com/rust-lang/futures-rs)
-  * [futures-macro](https://github.com/rust-lang/futures-rs)
-  * [futures-sink](https://github.com/rust-lang/futures-rs)
-  * [futures-task](https://github.com/rust-lang/futures-rs)
-  * [futures-util](https://github.com/rust-lang/futures-rs)
+  - [futures](https://github.com/rust-lang/futures-rs)
+  - [futures-channel](https://github.com/rust-lang/futures-rs)
+  - [futures-core](https://github.com/rust-lang/futures-rs)
+  - [futures-executor](https://github.com/rust-lang/futures-rs)
+  - [futures-io](https://github.com/rust-lang/futures-rs)
+  - [futures-macro](https://github.com/rust-lang/futures-rs)
+  - [futures-sink](https://github.com/rust-lang/futures-rs)
+  - [futures-task](https://github.com/rust-lang/futures-rs)
+  - [futures-util](https://github.com/rust-lang/futures-rs)
 
     ```
                           Apache License
@@ -3433,7 +3399,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3633,20 +3598,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [getrandom](https://github.com/rust-random/getrandom)
-  * [getrandom](https://github.com/rust-random/getrandom)
-  * [rand](https://github.com/rust-random/rand)
-  * [rand](https://github.com/rust-random/rand)
-  * [rand\_chacha](https://github.com/rust-random/rand)
-  * [rand\_chacha](https://github.com/rust-random/rand)
-  * [rand\_core](https://github.com/rust-random/rand)
-  * [rand\_core](https://github.com/rust-random/rand)
-  * [rand\_hc](https://github.com/rust-random/rand)
-  * [rand\_hc](https://github.com/rust-random/rand)
+  - [getrandom](https://github.com/rust-random/getrandom)
+  - [getrandom](https://github.com/rust-random/getrandom)
+  - [rand](https://github.com/rust-random/rand)
+  - [rand](https://github.com/rust-random/rand)
+  - [rand_chacha](https://github.com/rust-random/rand)
+  - [rand_chacha](https://github.com/rust-random/rand)
+  - [rand_core](https://github.com/rust-random/rand)
+  - [rand_core](https://github.com/rust-random/rand)
+  - [rand_hc](https://github.com/rust-random/rand)
+  - [rand_hc](https://github.com/rust-random/rand)
 
     ```
                           Apache License
@@ -3655,7 +3619,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3854,11 +3817,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [hkdf](https://github.com/RustCrypto/KDFs/)
+  - [hkdf](https://github.com/RustCrypto/KDFs/)
 
     ```
                           Apache License
@@ -3867,7 +3829,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4064,11 +4025,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [http](https://github.com/hyperium/http)
+  - [http](https://github.com/hyperium/http)
 
     ```
                           Apache License
@@ -4077,7 +4037,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4276,18 +4235,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [httpdate](https://github.com/pyfisch/httpdate)
+  - [httpdate](https://github.com/pyfisch/httpdate)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction,
@@ -4346,7 +4303,6 @@ All license text:
   "Contributor" shall mean Licensor and any individual or Legal Entity
   on behalf of whom a Contribution has been received by Licensor and
   subsequently incorporated within the Work.
-
   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
@@ -4410,7 +4366,6 @@ All license text:
   for any such Derivative Works as a whole, provided Your use,
   reproduction, and distribution of the Work otherwise complies with
   the conditions stated in this License.
-
   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
@@ -4484,11 +4439,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
+  - [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
 
     ```
                              Apache License
@@ -4497,7 +4451,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4699,11 +4652,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ipnet](https://github.com/krisprice/ipnet)
+  - [ipnet](https://github.com/krisprice/ipnet)
 
     ```
                              Apache License
@@ -4712,7 +4664,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4913,11 +4864,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [keyring](https://github.com/hwchen/keyring-rs.git)
+  - [keyring](https://github.com/hwchen/keyring-rs.git)
 
     ```
                           Apache License
@@ -4926,7 +4876,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5125,14 +5074,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
-  * [lru-cache](https://github.com/contain-rs/lru-cache)
-  * [process\_path](https://github.com/wesleywiser/process_path)
-  * [vec\_map](https://github.com/contain-rs/vec-map)
+  - [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
+  - [lru-cache](https://github.com/contain-rs/lru-cache)
+  - [process_path](https://github.com/wesleywiser/process_path)
+  - [vec_map](https://github.com/contain-rs/vec-map)
 
     ```
                           Apache License
@@ -5141,7 +5089,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5340,14 +5287,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [miniz\_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
-  * [pin-project](https://github.com/taiki-e/pin-project)
-  * [pin-project-internal](https://github.com/taiki-e/pin-project)
-  * [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
+  - [miniz_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
+  - [pin-project](https://github.com/taiki-e/pin-project)
+  - [pin-project-internal](https://github.com/taiki-e/pin-project)
+  - [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
 
     ```
                              Apache License
@@ -5356,7 +5302,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5528,11 +5473,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ntapi](https://github.com/MSxDOS/ntapi)
+  - [ntapi](https://github.com/MSxDOS/ntapi)
 
     ```
                              Apache License
@@ -5541,7 +5485,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5742,11 +5685,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
+  - [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
 
     ```
                           Apache License
@@ -5755,7 +5697,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5954,11 +5895,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
+  - [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
 
     ```
                           Apache License
@@ -5967,7 +5907,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6164,11 +6103,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
+  - [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6177,7 +6115,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6376,11 +6313,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
+  - [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6389,7 +6325,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6588,11 +6523,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [remove\_dir\_all](https://github.com/XAMPPRocky/remove_dir_all.git)
+  - [remove_dir_all](https://github.com/XAMPPRocky/remove_dir_all.git)
 
     ```
                           Apache License
@@ -6601,7 +6535,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6789,11 +6722,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [rolling-file](https://github.com/Axcient/rolling-file-rs)
+  - [rolling-file](https://github.com/Axcient/rolling-file-rs)
 
   rolling-file is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2].
@@ -7034,11 +6966,10 @@ All license text:
   limitations under the License.
   ```
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [ryu](https://github.com/dtolnay/ryu)
+  - [ryu](https://github.com/dtolnay/ryu)
 
     ```
                              Apache License
@@ -7047,7 +6978,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7248,12 +7178,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [serde\_urlencoded](https://github.com/nox/serde_urlencoded)
-  * [utf-8](https://github.com/SimonSapin/rust-utf8)
+  - [serde_urlencoded](https://github.com/nox/serde_urlencoded)
+  - [utf-8](https://github.com/SimonSapin/rust-utf8)
 
     ```
                           Apache License
@@ -7262,7 +7191,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7434,11 +7362,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [tinyvec](https://github.com/Lokathor/tinyvec)
+  - [tinyvec](https://github.com/Lokathor/tinyvec)
 
     ```
                              Apache License
@@ -7447,7 +7374,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7648,11 +7574,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [tokio-rustls](https://github.com/tokio-rs/tls)
+  - [tokio-rustls](https://github.com/tokio-rs/tls)
 
     ```
                           Apache License
@@ -7661,7 +7586,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7860,11 +7784,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [typenum](https://github.com/paholg/typenum)
+  - [typenum](https://github.com/paholg/typenum)
 
     ```
                           Apache License
@@ -7873,7 +7796,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8072,11 +7994,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [webbrowser](https://github.com/amodm/webbrowser-rs)
+  - [webbrowser](https://github.com/amodm/webbrowser-rs)
 
   Copyright (c) 2015 Amod Malviya
 
@@ -8103,7 +8024,6 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8275,11 +8195,10 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [widestring](https://github.com/starkat99/widestring-rs.git)
+  - [widestring](https://github.com/starkat99/widestring-rs.git)
 
     ```
                           Apache License
@@ -8288,7 +8207,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8487,11 +8405,10 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [windows-service](https://github.com/mullvad/windows-service-rs)
+  - [windows-service](https://github.com/mullvad/windows-service-rs)
 
     ```
                           Apache License
@@ -8500,7 +8417,6 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8699,16 +8615,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-* ### Apache License 2.0
+- ### Apache License 2.0
 
   #### Used by:
-
-  * [winlog](https://gitlab.com/arbitrix/winlog)
+  - [winlog](https://gitlab.com/arbitrix/winlog)
 
   This software is licensed under either of
-
-  * Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
-  * MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
+  - Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+  - MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
 
   at your option.
 
@@ -8719,7 +8633,6 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8942,17 +8855,15 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [ip\_network](https://github.com/JakubOnderka/ip_network)
+  - [ip_network](https://github.com/JakubOnderka/ip_network)
 
   Copyright (c) 2017, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8970,17 +8881,15 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [ip\_network\_table](https://github.com/JakubOnderka/ip_network_table)
+  - [ip_network_table](https://github.com/JakubOnderka/ip_network_table)
 
   Copyright (c) 2018, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8998,19 +8907,17 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 2-Clause "Simplified" License
+- ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-
-  * [mach](https://github.com/fitzgen/mach)
-  * [mach](https://github.com/fitzgen/mach)
+  - [mach](https://github.com/fitzgen/mach)
+  - [mach](https://github.com/fitzgen/mach)
 
   Copyright (c) 2015, Nick Fitzgerald
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9029,12 +8936,11 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [app-center](https://github.com/vkrasnov/appcenter-rs)
-  * [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
+  - [app-center](https://github.com/vkrasnov/appcenter-rs)
+  - [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
 
   BSD 3-Clause License
 
@@ -9043,7 +8949,6 @@ All license text:
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9066,11 +8971,10 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [boringtun](https://github.com/cloudflare/boringtun)
+  - [boringtun](https://github.com/cloudflare/boringtun)
 
   Copyright (c) 2019 Cloudflare, Inc. All rights reserved.
 
@@ -9084,11 +8988,10 @@ All license text:
 
   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [etherparse](https://github.com/JulianSchmid/etherparse)
+  - [etherparse](https://github.com/JulianSchmid/etherparse)
 
   BSD 3-Clause License
 
@@ -9120,18 +9023,16 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [instant](https://github.com/sebcrozet/instant)
+  - [instant](https://github.com/sebcrozet/instant)
 
   Copyright (c) 2019, Sébastien Crozet
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9154,17 +9055,15 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [nel](https://crates.io/crates/nel/0.1.4)
+  - [nel](https://crates.io/crates/nel/0.1.4)
 
   Copyright 2021 Cloudflare, Inc. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
-
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9187,18 +9086,16 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [subtle](https://github.com/dalek-cryptography/subtle)
+  - [subtle](https://github.com/dalek-cryptography/subtle)
 
   Copyright (c) 2016-2017 Isis Agora Lovecruft, Henry de Valence. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
-
   1. Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
 
@@ -9222,11 +9119,10 @@ All license text:
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### BSD 3-Clause "New" or "Revised" License
+- ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-
-  * [webpki](https://github.com/briansmith/webpki)
+  - [webpki](https://github.com/briansmith/webpki)
 
   // Copyright 2015 The Chromium Authors. All rights reserved.
   //
@@ -9256,11 +9152,10 @@ All license text:
   // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   // Copyright 2017 Brian Smith.
   //
@@ -9276,7 +9171,7 @@ All license text:
   // OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
   // CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-  \#\[macro\_use]
+  \#\[macro_use]
   pub mod constant;
 
   \#\[cfg(feature = "alloc")]
@@ -9284,11 +9179,10 @@ All license text:
 
   pub mod montgomery;
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [untrusted](https://github.com/briansmith/untrusted)
+  - [untrusted](https://github.com/briansmith/untrusted)
 
   // Copyright 2015-2016 Brian Smith.
   //
@@ -9304,11 +9198,10 @@ All license text:
   // ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
   // OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-* ### ISC License
+- ### ISC License
 
   #### Used by:
-
-  * [webpki](https://github.com/briansmith/webpki)
+  - [webpki](https://github.com/briansmith/webpki)
 
   Except as otherwise noted, this project is licensed under the following
   (ISC-style) terms:
@@ -9330,15 +9223,14 @@ All license text:
   The files under third-party/chromium are licensed as described in
   third-party/chromium/LICENSE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [aho-corasick](https://github.com/BurntSushi/aho-corasick)
-  * [byteorder](https://github.com/BurntSushi/byteorder)
-  * [memchr](https://github.com/BurntSushi/memchr)
-  * [regex-automata](https://github.com/BurntSushi/regex-automata)
-  * [walkdir](https://github.com/BurntSushi/walkdir)
+  - [aho-corasick](https://github.com/BurntSushi/aho-corasick)
+  - [byteorder](https://github.com/BurntSushi/byteorder)
+  - [memchr](https://github.com/BurntSushi/memchr)
+  - [regex-automata](https://github.com/BurntSushi/regex-automata)
+  - [walkdir](https://github.com/BurntSushi/walkdir)
 
   The MIT License (MIT)
 
@@ -9362,11 +9254,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ansi\_term](https://crates.io/crates/ansi_term)
+  - [ansi_term](https://crates.io/crates/ansi_term)
 
   The MIT License (MIT)
 
@@ -9390,11 +9281,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ansi\_term](https://github.com/ogham/rust-ansi-term)
+  - [ansi_term](https://github.com/ogham/rust-ansi-term)
 
   The MIT License (MIT)
 
@@ -9418,11 +9308,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [atty](https://github.com/softprops/atty)
+  - [atty](https://github.com/softprops/atty)
 
   Copyright (c) 2015-2019 Doug Tangren
 
@@ -9445,11 +9334,10 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [bytes](https://github.com/tokio-rs/bytes)
+  - [bytes](https://github.com/tokio-rs/bytes)
 
   Copyright (c) 2018 Carl Lerche
 
@@ -9477,11 +9365,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [clap](https://github.com/clap-rs/clap)
+  - [clap](https://github.com/clap-rs/clap)
 
   The MIT License (MIT)
 
@@ -9505,11 +9392,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [combine](https://github.com/Marwes/combine)
+  - [combine](https://github.com/Marwes/combine)
 
   The MIT License (MIT)
 
@@ -9533,13 +9419,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [darling](https://github.com/TedDriggs/darling)
-  * [darling\_core](https://github.com/TedDriggs/darling)
-  * [darling\_macro](https://github.com/TedDriggs/darling)
+  - [darling](https://github.com/TedDriggs/darling)
+  - [darling_core](https://github.com/TedDriggs/darling)
+  - [darling_macro](https://github.com/TedDriggs/darling)
 
   MIT License
 
@@ -9563,11 +9448,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [data-encoding](https://github.com/ia0/data-encoding)
+  - [data-encoding](https://github.com/ia0/data-encoding)
 
   The MIT License (MIT)
 
@@ -9592,17 +9476,16 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [dispatch](http://github.com/SSheldon/rust-dispatch)
-  * [netlink-packet-core](https://github.com/little-dude/netlink)
-  * [netlink-packet-route](https://github.com/little-dude/netlink)
-  * [netlink-packet-utils](https://github.com/little-dude/netlink)
-  * [netlink-sys](https://github.com/little-dude/netlink)
-  * [tokio-macros](https://github.com/tokio-rs/tokio)
-  * [void](https://github.com/reem/rust-void.git)
+  - [dispatch](http://github.com/SSheldon/rust-dispatch)
+  - [netlink-packet-core](https://github.com/little-dude/netlink)
+  - [netlink-packet-route](https://github.com/little-dude/netlink)
+  - [netlink-packet-utils](https://github.com/little-dude/netlink)
+  - [netlink-sys](https://github.com/little-dude/netlink)
+  - [tokio-macros](https://github.com/tokio-rs/tokio)
+  - [void](https://github.com/reem/rust-void.git)
 
   MIT License
 
@@ -9612,11 +9495,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
+  - [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
 
   MIT License
 
@@ -9640,11 +9522,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
+  - [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
 
   MIT License
 
@@ -9668,11 +9549,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [generic-array](https://github.com/fizyk20/generic-array.git)
+  - [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9696,11 +9576,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [generic-array](https://github.com/fizyk20/generic-array.git)
+  - [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9724,11 +9603,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [h2](https://github.com/hyperium/h2)
+  - [h2](https://github.com/hyperium/h2)
 
   Copyright (c) 2017 h2 authors
 
@@ -9756,11 +9634,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [hostname](https://github.com/svartalf/hostname)
+  - [hostname](https://github.com/svartalf/hostname)
 
   MIT License
 
@@ -9785,11 +9662,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [http-body](https://github.com/hyperium/http-body)
+  - [http-body](https://github.com/hyperium/http-body)
 
   Copyright (c) 2019 Hyper Contributors
 
@@ -9817,11 +9693,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [hyper](https://github.com/hyperium/hyper)
+  - [hyper](https://github.com/hyperium/hyper)
 
   Copyright (c) 2014-2021 Sean McArthur
 
@@ -9843,11 +9718,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ip\_network\_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
+  - [ip_network_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
 
   Copyright (c) 2016 Hroi Sigurdsson
 
@@ -9875,11 +9749,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [iprange](https://github.com/sticnarf/iprange-rs)
+  - [iprange](https://github.com/sticnarf/iprange-rs)
 
   MIT License
 
@@ -9903,11 +9776,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
+  - [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
 
   The MIT License
 
@@ -9930,11 +9802,10 @@ All license text:
   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [matchers](https://github.com/hawkw/matchers)
+  - [matchers](https://github.com/hawkw/matchers)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -9956,11 +9827,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [matches](https://github.com/SimonSapin/rust-std-candidates)
+  - [matches](https://github.com/SimonSapin/rust-std-candidates)
 
   Copyright (c) 2014-2016 Simon Sapin
 
@@ -9988,11 +9858,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [memoffset](https://github.com/Gilnaa/memoffset)
+  - [memoffset](https://github.com/Gilnaa/memoffset)
 
   Copyright (c) 2017 Gilad Naaman
 
@@ -10014,11 +9883,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [mio](https://github.com/tokio-rs/mio)
+  - [mio](https://github.com/tokio-rs/mio)
 
   Copyright (c) 2014 Carl Lerche and other MIO contributors
 
@@ -10040,11 +9908,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [nix](https://github.com/nix-rust/nix)
+  - [nix](https://github.com/nix-rust/nix)
 
   The MIT License (MIT)
 
@@ -10068,11 +9935,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [plist](https://github.com/ebarnard/rust-plist/)
+  - [plist](https://github.com/ebarnard/rust-plist/)
 
   Copyright (c) 2015 Edward Barnard
 
@@ -10094,11 +9960,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [powershell\_script](https://github.com/cfsamson/powershell-script)
+  - [powershell_script](https://github.com/cfsamson/powershell-script)
 
   The MIT License (MIT)
 
@@ -10110,11 +9975,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [redox\_syscall](https://gitlab.redox-os.org/redox-os/syscall)
+  - [redox_syscall](https://gitlab.redox-os.org/redox-os/syscall)
 
   Copyright (c) 2017 Redox OS Developers
 
@@ -10139,11 +10003,10 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [redox\_users](https://gitlab.redox-os.org/redox-os/users)
+  - [redox_users](https://gitlab.redox-os.org/redox-os/users)
 
   The MIT License (MIT)
 
@@ -10167,11 +10030,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   The MIT License (MIT)
 
@@ -10196,12 +10058,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [same-file](https://github.com/BurntSushi/same-file)
-  * [winapi-util](https://github.com/BurntSushi/winapi-util)
+  - [same-file](https://github.com/BurntSushi/same-file)
+  - [winapi-util](https://github.com/BurntSushi/winapi-util)
 
   The MIT License (MIT)
 
@@ -10225,11 +10086,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [schannel](https://github.com/steffengy/schannel-rs)
+  - [schannel](https://github.com/steffengy/schannel-rs)
 
   Copyright (c) 2015 steffengy
 
@@ -10239,11 +10099,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
+  - [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
 
   MIT License
 
@@ -10267,11 +10126,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sharded-slab](https://github.com/hawkw/sharded-slab)
+  - [sharded-slab](https://github.com/hawkw/sharded-slab)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -10293,11 +10151,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [slab](https://github.com/tokio-rs/slab)
+  - [slab](https://github.com/tokio-rs/slab)
 
   Copyright (c) 2019 Carl Lerche
 
@@ -10325,11 +10182,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [smbios-lib](https://github.com/jrgerber/smbios-lib)
+  - [smbios-lib](https://github.com/jrgerber/smbios-lib)
 
   MIT License
 
@@ -10353,12 +10209,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [spin](https://github.com/mvdnes/spin-rs.git)
-  * [zip](https://github.com/zip-rs/zip.git)
+  - [spin](https://github.com/mvdnes/spin-rs.git)
+  - [zip](https://github.com/zip-rs/zip.git)
 
   The MIT License (MIT)
 
@@ -10382,12 +10237,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [strsim](https://github.com/dguo/strsim-rs)
-  * [strsim](https://github.com/dguo/strsim-rs)
+  - [strsim](https://github.com/dguo/strsim-rs)
+  - [strsim](https://github.com/dguo/strsim-rs)
 
   The MIT License (MIT)
 
@@ -10412,11 +10266,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [synstructure](https://github.com/mystor/synstructure)
+  - [synstructure](https://github.com/mystor/synstructure)
 
   Copyright 2016 Nika Layzell
 
@@ -10426,11 +10279,10 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sys-info](https://github.com/FillZpp/sys-info-rs)
+  - [sys-info](https://github.com/FillZpp/sys-info-rs)
 
   The MIT License (MIT)
 
@@ -10454,11 +10306,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
+  - [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
 
   The MIT License (MIT)
 
@@ -10482,11 +10333,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [take\_mut](https://github.com/Sgeo/take_mut)
+  - [take_mut](https://github.com/Sgeo/take_mut)
 
   The MIT License (MIT)
 
@@ -10510,11 +10360,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [textwrap](https://github.com/mgeisler/textwrap)
+  - [textwrap](https://github.com/mgeisler/textwrap)
 
   MIT License
 
@@ -10538,12 +10387,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tokio](https://github.com/tokio-rs/tokio)
-  * [tokio-util](https://github.com/tokio-rs/tokio)
+  - [tokio](https://github.com/tokio-rs/tokio)
+  - [tokio-util](https://github.com/tokio-rs/tokio)
 
   Copyright (c) 2021 Tokio Contributors
 
@@ -10571,11 +10419,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
+  - [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
 
   Copyright (c) 2017 Daniel Abramov
   Copyright (c) 2017 Alexey Galakhov
@@ -10598,11 +10445,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [totp-lite](https://github.com/fosskers/totp-lite)
+  - [totp-lite](https://github.com/fosskers/totp-lite)
 
   MIT License
 
@@ -10626,11 +10472,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tower-service](https://github.com/tower-rs/tower)
+  - [tower-service](https://github.com/tower-rs/tower)
 
   Copyright (c) 2019 Tower Contributors
 
@@ -10658,17 +10503,16 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [tracing](https://github.com/tokio-rs/tracing)
-  * [tracing-appender](https://github.com/tokio-rs/tracing)
-  * [tracing-attributes](https://github.com/tokio-rs/tracing)
-  * [tracing-core](https://github.com/tokio-rs/tracing)
-  * [tracing-log](https://github.com/tokio-rs/tracing)
-  * [tracing-serde](https://github.com/tokio-rs/tracing)
-  * [tracing-subscriber](https://github.com/tokio-rs/tracing)
+  - [tracing](https://github.com/tokio-rs/tracing)
+  - [tracing-appender](https://github.com/tokio-rs/tracing)
+  - [tracing-attributes](https://github.com/tokio-rs/tracing)
+  - [tracing-core](https://github.com/tokio-rs/tracing)
+  - [tracing-log](https://github.com/tokio-rs/tracing)
+  - [tracing-serde](https://github.com/tokio-rs/tracing)
+  - [tracing-subscriber](https://github.com/tokio-rs/tracing)
 
   Copyright (c) 2019 Tokio Contributors
 
@@ -10696,11 +10540,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [try-lock](https://github.com/seanmonstar/try-lock)
+  - [try-lock](https://github.com/seanmonstar/try-lock)
 
   Copyright (c) 2018 Sean McArthur
   Copyright (c) 2016 Alex Crichton
@@ -10723,11 +10566,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [want](https://github.com/seanmonstar/want)
+  - [want](https://github.com/seanmonstar/want)
 
   Copyright (c) 2018-2019 Sean McArthur
 
@@ -10749,13 +10591,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [winreg](https://github.com/gentoo90/winreg-rs)
-  * [winreg](https://github.com/gentoo90/winreg-rs)
-  * [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
+  - [winreg](https://github.com/gentoo90/winreg-rs)
 
   Copyright (c) 2015 Igor Shaula
 
@@ -10777,11 +10618,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [winres](https://github.com/mxre/winres)
+  - [winres](https://github.com/mxre/winres)
 
   Copyright 2016 Max Resch
 
@@ -10809,11 +10649,10 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-* ### MIT License
+- ### MIT License
 
   #### Used by:
-
-  * [xml-rs](https://github.com/netvl/xml-rs)
+  - [xml-rs](https://github.com/netvl/xml-rs)
 
   The MIT License (MIT)
 
@@ -10837,12 +10676,10 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-* ### Mozilla Public License 2.0
+- ### Mozilla Public License 2.0
 
   #### Used by:
-
-  * [cbindgen](https://github.com/eqrion/cbindgen/)
-
+  - [cbindgen](https://github.com/eqrion/cbindgen/)
   1. Definitions
 
   ***
@@ -10929,7 +10766,6 @@ All license text:
   whether by contract or otherwise, or (b) ownership of more than
   fifty percent (50%) of the outstanding shares or beneficial
   ownership of such entity.
-
   2. License Grants and Conditions
 
   ***
@@ -11001,7 +10837,6 @@ All license text:
 
   Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
   in Section 2.1.
-
   3. Responsibilities
 
   ***
@@ -11064,7 +10899,6 @@ All license text:
   indemnity or liability terms You offer. You may include additional
   disclaimers of warranty and limitations of liability specific to any
   jurisdiction.
-
   4. Inability to Comply Due to Statute or Regulation
 
   ***
@@ -11078,7 +10912,6 @@ All license text:
   Software under this License. Except to the extent prohibited by statute
   or regulation, such description must be sufficiently detailed for a
   recipient of ordinary skill to be able to understand it.
-
   5. Termination
 
   ***
@@ -11114,7 +10947,6 @@ All license text:
 
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \* \* \* 7. Limitation of Liability \* \* -------------------------- \* \* \* \* Under no circumstances and under no legal theory, whether tort \* \* (including negligence), contract, or otherwise, shall any \* \* Contributor, or anyone who distributes Covered Software as \* \* permitted above, be liable to You for any direct, indirect, \* \* special, incidental, or consequential damages of any character \* \* including, without limitation, damages for lost profits, loss of \* \* goodwill, work stoppage, computer failure or malfunction, or any \* \* and all other commercial damages or losses, even if such party \* \* shall have been informed of the possibility of such damages. This \* \* limitation of liability shall not apply to liability for death or \* \* personal injury resulting from such party's negligence to the \* \* extent applicable law prohibits such limitation. Some \* \* jurisdictions do not allow the exclusion or limitation of \* \* incidental or consequential damages, so this exclusion and \* \* limitation may not apply to You. \* \* \*
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
-
   8. Litigation
 
   ***
@@ -11125,7 +10957,6 @@ All license text:
   jurisdiction, without reference to its conflict-of-law provisions.
   Nothing in this Section shall prevent a party's ability to bring
   cross-claims or counter-claims.
-
   9. Miscellaneous
 
   ***
@@ -11136,7 +10967,6 @@ All license text:
   necessary to make it enforceable. Any law or regulation which provides
   that the language of a contract shall be construed against the drafter
   shall not be used to construe this License against a Contributor.
-
   10. Versions of the License
 
   ***
@@ -11188,14 +11018,12 @@ All license text:
   This Source Code Form is "Incompatible With Secondary Licenses", as
   defined by the Mozilla Public License, v. 2.0.
 
-* ### Mozilla Public License 2.0
+- ### Mozilla Public License 2.0
 
   #### Used by:
-
-  * [webpki-roots](https://github.com/ctz/webpki-roots)
+  - [webpki-roots](https://github.com/ctz/webpki-roots)
 
   Mozilla Public License Version 2.0
-
   1. Definitions
 
      1.1. "Contributor" means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.
@@ -11353,11 +11181,10 @@ All license text:
    This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0.
   ```
 
-* ### OpenSSL License
+- ### OpenSSL License
 
   #### Used by:
-
-  * [ring](https://github.com/briansmith/ring)
+  - [ring](https://github.com/briansmith/ring)
 
   /\* Copyright (C) 1995-1998 Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)) \* All rights reserved. \* \* This package is an SSL implementation written \* by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)). \* The implementation was written so as to conform with Netscapes SSL. \* \* This library is free for commercial and non-commercial use as long as \* the following conditions are aheared to. The following conditions \* apply to all code found in this distribution, be it the RC4, RSA, \* lhash, DES, etc., code; not just the SSL code. The SSL documentation \* included with this distribution is covered by the same copyright terms \* except that the holder is Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com)). \* \* Copyright remains Eric Young's, and as such any Copyright notices in \* the code are not to be removed. \* If this package is used in a product, Eric Young should be given attribution \* as the author of the parts of the library used. \* This can be in the form of a textual message at program startup or \* in documentation (online or textual) provided with the package. \* \* Redistribution and use in source and binary forms, with or without \* modification, are permitted provided that the following conditions \* are met: \* 1. Redistributions of source code must retain the copyright \* notice, this list of conditions and the following disclaimer. \* 2. Redistributions in binary form must reproduce the above copyright \* notice, this list of conditions and the following disclaimer in the \* documentation and/or other materials provided with the distribution. \* 3. All advertising materials mentioning features or use of this software \* must display the following acknowledgement: \* "This product includes cryptographic software written by \* Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com))" \* The word 'cryptographic' can be left out if the rouines from the library \* being used are not cryptographic related :-). \* 4. If you include any Windows specific code (or a derivative thereof) from \* the apps directory (application code) you must include an acknowledgement: \* "This product includes software written by Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com))" \* \* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND \* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE \* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE \* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE \* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL \* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS \* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) \* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT \* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY \* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF \* SUCH DAMAGE. \* \* The licence and distribution terms for any publically available version or \* derivative of this code cannot be changed. i.e. this code cannot simply be \* copied and put under another distribution licence \* \[including the GNU Public Licence.]
   \*/
diff --git a/src/content/docs/warp-client/legal/index.mdx b/src/content/docs/warp-client/legal/index.mdx
index eda71adda87c679..2a3706602febaf7 100644
--- a/src/content/docs/warp-client/legal/index.mdx
+++ b/src/content/docs/warp-client/legal/index.mdx
@@ -7,9 +7,8 @@ title: Legal
 hideChildren: true
 sidebar:
   order: 6
-
 ---
 
-* [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
-* [Application Terms of Service](https://www.cloudflare.com/application/terms/)
-* [Third party licenses](/warp-client/legal/3rdparty/)
+- [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
+- [Application Terms of Service](https://www.cloudflare.com/application/terms/)
+- [Third party licenses](/warp-client/legal/3rdparty/)
diff --git a/src/content/docs/warp-client/privacy.mdx b/src/content/docs/warp-client/privacy.mdx
index 92288d9c01bb7c0..b9d5bb1a7061d21 100644
--- a/src/content/docs/warp-client/privacy.mdx
+++ b/src/content/docs/warp-client/privacy.mdx
@@ -8,7 +8,6 @@ tags:
   - Privacy
 sidebar:
   order: 4
-
 ---
 
 The WARP Client application uses a VPN profile and/or service that enables us to intercept and secure your DNS queries and to transmit data from your device through the Cloudflare network, depending on the services you have enabled. We only collect limited DNS query and traffic data (excluding payload) that is sent to our network when you have the app enabled on your device. All information is handled in accordance with our [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/).
diff --git a/src/content/docs/web-analytics/configuration-options/filters.mdx b/src/content/docs/web-analytics/configuration-options/filters.mdx
index 27174f2f041e941..8ad627a79b2582d 100644
--- a/src/content/docs/web-analytics/configuration-options/filters.mdx
+++ b/src/content/docs/web-analytics/configuration-options/filters.mdx
@@ -5,7 +5,6 @@ products:
 title: Filters
 head: []
 description: Learn how to use filters in Cloudflare Web Analytics.
-
 ---
 
 import { DashButton } from "~/components";
@@ -25,4 +24,4 @@ To filter the data shown on Web Analytics:
 
 - By default, Web Analytics shows data for the previous 24 hours. Adjust the time range using the dropdown menu above the graph.
 - Select and drag the cursor on the graph to choose a custom time period.
-- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
\ No newline at end of file
+- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
diff --git a/src/content/docs/web-analytics/configuration-options/index.mdx b/src/content/docs/web-analytics/configuration-options/index.mdx
index 390e5e32d1c7476..4a728a05e606d7f 100644
--- a/src/content/docs/web-analytics/configuration-options/index.mdx
+++ b/src/content/docs/web-analytics/configuration-options/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Configuration options
 sidebar:
   order: 4
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Customize your Web Analytics views by using filters and rules.
 
diff --git a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
index 0b5369d3af5186b..4766dc07ffc8926 100644
--- a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
+++ b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
@@ -6,7 +6,6 @@ products:
 title: Core Web Vitals
 sidebar:
   order: 3
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,10 +14,8 @@ import { DashButton } from "~/components";
 
 :::note
 
-
 Core Web Vitals is currently only supported in Chromium browsers, with Safari and Firefox coming soon.
 
-
 :::
 
 ## Access Core Web Vitals
@@ -32,7 +29,7 @@ To access Core Web Vitals:
 
 2. Select your website and select **Core Web Vitals**.
 
-###  Core Web Vitals metrics
+### Core Web Vitals metrics
 
 Core Web Vitals is divided into three main sections, each one with information about a specific feature that affects user experience:
 
diff --git a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
index 503d9caaf70f22e..407d22e05366193 100644
--- a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
+++ b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
@@ -11,7 +11,7 @@ tags:
   - Privacy
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Web Analytics relies on the `performance.getEntriesByType('navigation')` object to collect metrics about page load performance. If Navigation Timing Level 2 is not supported, then [`performance.timing` (Level 1)](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) is used.
 
diff --git a/src/content/docs/web-analytics/data-metrics/dimensions.mdx b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
index 3caceecb45f0a80..2f8158417df0f8f 100644
--- a/src/content/docs/web-analytics/data-metrics/dimensions.mdx
+++ b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
@@ -6,7 +6,6 @@ products:
 title: Dimensions
 sidebar:
   order: 4
-
 ---
 
 Dimensions are the labels used to describe different types of metrics or data. For example, **Referer** is the data collected from external links referring visits to a page, while **Browser** shows which browsers accessed your website.
@@ -28,14 +27,14 @@ Below you can find a list of the different dimensions you can use to filter Web
 
 ## Navigation types
 
-| Type                    | Cache hit? | Explanation |
-| ----------------------- | ---------- | ----------- |
-| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
-| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
-| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document. |
-| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document. |
-| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
-| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Type                    | Cache hit? | Explanation                                                                                                                                                                                                                                                                                                                                                |
+| ----------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                              |
+| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                  |
+| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                    |
+| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document.                                                                                                                                                                                                     |
+| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                                               |
+| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                                   |
 | Back-forward            | ❌         | The visitor used the back/forward buttons/gestures in their browser but the previously-loaded document either not found or stale in the browsers HTTP cache OR a feature was used which prevents using the cache (refer to the explanation in [Back/forward cache](https://web.dev/articles/bfcache)), so a network request was made to load the document. |
-| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
-| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity. |
+| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                             |
+| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity.                                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
index 65577424b5e1480..d3db219922bbfb9 100644
--- a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
+++ b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
@@ -6,14 +6,13 @@ products:
 title: High-level metrics
 sidebar:
   order: 1
-
 ---
 
 Understanding the key metrics in web analytics is essential for optimizing your website’s performance and user experience. Here are the high-level metrics tracked by Cloudflare Web Analytics:
 
-* **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
-* **Page views** - A successful HTTP response with a content-type of HTML.
-* **Page load time** - The total amount of time required to load the page.
-* **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
+- **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
+- **Page views** - A successful HTTP response with a content-type of HTML.
+- **Page load time** - The total amount of time required to load the page.
+- **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
 
 ![Web Analytics overview page](~/assets/images/web-analytics/dash-web_analytics-overview.png)
diff --git a/src/content/docs/web-analytics/data-metrics/index.mdx b/src/content/docs/web-analytics/data-metrics/index.mdx
index 701245c37266099..7295662b2a7dd44 100644
--- a/src/content/docs/web-analytics/data-metrics/index.mdx
+++ b/src/content/docs/web-analytics/data-metrics/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Data and metrics
 sidebar:
   order: 5
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 In this section, you can find information about the data and metrics available in Web Analytics.
 
diff --git a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
index ed4e1dedbe02b6b..17d8640e8fe0887 100644
--- a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
+++ b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
@@ -6,7 +6,6 @@ products:
 title: Page load time
 sidebar:
   order: 2
-
 ---
 
 Page load time summary gives you an overview of how long your web page takes to load, broken down by area. To access Page load time:
diff --git a/src/content/docs/web-analytics/faq.mdx b/src/content/docs/web-analytics/faq.mdx
index 57b722a62fab5d6..50db67fa11ae9e8 100644
--- a/src/content/docs/web-analytics/faq.mdx
+++ b/src/content/docs/web-analytics/faq.mdx
@@ -123,11 +123,11 @@ For manual embedding, this script instead connects to `cloudflareinsights.com`,
 connect-src [...existing values...] cloudflareinsights.com
 ```
 
-### How can I enforce Subresource Integrity (SRI) with the JS beacon? 
+### How can I enforce Subresource Integrity (SRI) with the JS beacon?
 
 If you're using the automated injection (i.e. not the manually-embedded script approach mentioned above), Cloudflare automatically includes an `integrity` attribute in the `<script>`. This ensures the script will only execute if a local hash of its downloaded contents match the integrity hash supplied in the HTML.
 
-Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure 
+Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure
 
 ### Can I use the same JS Snippet for a different domain?
 
@@ -159,11 +159,11 @@ When aggregating metrics in the Cloudflare Dashboard or querying the GraphQL API
 
 Note: the GraphQL API exposes a `sampleInterval` field to indicate which level of sampling has been applied to the query.
 
-* The beacon script will fire on every pageview.
-* The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
-* We store the unsampled data for 7 days.
-* We also aggregate it down so it's around 10% of the original volume for long-term storage.
-* Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
+- The beacon script will fire on every pageview.
+- The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
+- We store the unsampled data for 7 days.
+- We also aggregate it down so it's around 10% of the original volume for long-term storage.
+- Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
 
 ### Can I see server-side analytics by URL?
 
diff --git a/src/content/docs/web-analytics/get-started/rum-beacon.mdx b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
index 11ec40779ef5cee..675f6808ea47e52 100644
--- a/src/content/docs/web-analytics/get-started/rum-beacon.mdx
+++ b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
@@ -5,5 +5,4 @@ products:
   - web-analytics
 title: RUM beacon for Web Analytics
 external_link: /speed/observatory/rum-beacon/
-
----
\ No newline at end of file
+---
diff --git a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
index 6b3368cab792483..9ae208a6c8ea4c5 100644
--- a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
+++ b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
@@ -21,9 +21,9 @@ If you want to disable the automatic tracking for SPAs, you can do so by adding
 
 ```html
 <script
-  defer
-  src="https://static.cloudflareinsights.com/beacon.min.js"
-  data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
+	defer
+	src="https://static.cloudflareinsights.com/beacon.min.js"
+	data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
 ></script>
 ```
 
@@ -33,7 +33,7 @@ If you are using Google Tag Manager (GTM), you can disable SPA tracking by passi
 
 ```html
 <script
-  defer
-  src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
+	defer
+	src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
 ></script>
 ```
diff --git a/src/content/docs/web-analytics/limits.mdx b/src/content/docs/web-analytics/limits.mdx
index cc30789f0796155..8a2772d9e9f328e 100644
--- a/src/content/docs/web-analytics/limits.mdx
+++ b/src/content/docs/web-analytics/limits.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Web Analytics - Limits
-
 ---
 
 Cloudflare limits the number of sites for which you can track web analytics, as well as the number of rules allowed for each plan type. Refer to the following tables for more information.
diff --git a/src/content/docs/web3/about.mdx b/src/content/docs/web3/about.mdx
index e71d0319dd669a7..12c2faf886781b6 100644
--- a/src/content/docs/web3/about.mdx
+++ b/src/content/docs/web3/about.mdx
@@ -29,4 +29,4 @@ Only available for gateways to EVM-based chains, such as [Ethereum](/web3/how-to
 
 Write operations submit new data to the network. For example, sending a transaction or deploying a smart contract. The gateway forwards your request to one of Cloudflare's Ethereum nodes, which places the transaction in its mempool (a queue of pending transactions waiting to be included in a block).
 
-From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
\ No newline at end of file
+From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
diff --git a/src/content/docs/web3/api-reference.mdx b/src/content/docs/web3/api-reference.mdx
index a71630e4616b775..6580ba64f458124 100644
--- a/src/content/docs/web3/api-reference.mdx
+++ b/src/content/docs/web3/api-reference.mdx
@@ -7,5 +7,4 @@ title: API reference
 external_link: /api/resources/web3/subresources/hostnames/methods/list/
 sidebar:
   order: 6
-
 ---
diff --git a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
index e8c6ae241ad289f..8fa017a894a1131 100644
--- a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Concepts - Ethereum Gateways
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 As you get started with Cloudflare's Ethereum Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ethereum-gateway/reference/index.mdx b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
index 0ac05bf3f8fd5a3..2bb1163debfdf53 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - Ethereum
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
index 424052aeb898254..ae20777dcb9b048 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
@@ -6,7 +6,6 @@ products:
 title: Kill Switches
 sidebar:
   order: 6
-
 ---
 
 When writing contracts, be especially careful to write secure code and include a
@@ -16,7 +15,7 @@ the smart contract that can be exploited, this can lead to the theft of
 resources from the smart contract or from other individuals.
 
 This was brought into sharp focus during the [infamous DAO
-incident](https://en.wikipedia.org/wiki/The_DAO_\(organization\)). The DAO smart
+incident](<https://en.wikipedia.org/wiki/The_DAO_(organization)>). The DAO smart
 contract acted as a complex, decentralized venture capital fund and held Ether
 worth $250 million at its peak collected from a group of investors. Hackers
 exploited vulnerabilities in the smart contract, stealing $50 million worth of
@@ -24,7 +23,7 @@ Ether.
 
 Because there is no way to undo transactions in Ether, there was a highly
 controversial “hard fork," where the majority of the community agreed to accept
-a block that contained an *irregular state change* that essentially drained all
+a block that contained an _irregular state change_ that essentially drained all
 DAO funds into a special “WithdrawDAO” recovery contract. By convincing enough
 miners to accept this irregular block as valid, the DAO was able to return
 investors funds. However, not everyone agreed with the chain, with those who
@@ -59,7 +58,7 @@ trustworthiness.
 The trust placed in consensus-based algorithms is based on the assumption that
 most people are honest, or more accurately that no sufficiently large subset of
 people can be made to collude to produce a malicious outcome. This is the
-*democratisation of trust*. In the DAO attack, a majority of nodes agreed to
+_democratisation of trust_. In the DAO attack, a majority of nodes agreed to
 accept an irregular state transition. This effectively undid the damage of the
 attack, and shows how, at least in the world of blockchain, perception is
 reality. Because most people “believed" -- accepted this irregular block, it
diff --git a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
index fe72e9e11b576ae..a786977025d3db2 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
@@ -8,7 +8,6 @@ tags:
   - Migration
 sidebar:
   order: 5
-
 ---
 
 Though Cloudflare's Ethereum Gateway launched with support for the Rinkeby testnet, Rinkeby did not run through [The Merge](https://ethereum.org/en/upgrades/merge/) and - as a result - will no longer be a reliable staging environment for mainnet.
@@ -36,20 +35,20 @@ curl https://web3-trial.cloudflare-eth.com/v1/rinkeby \
 
 ```js title="Previous JS Fetch API" {2}
 await fetch(
-  new Request('https://web3-trial.cloudflare-eth.com/v1/rinkeby', {
-    method: 'POST',
-    body: JSON.stringify({
-      jsonrpc: '2.0',
-      method: 'eth_getBlockByNumber',
-      params: ['0x2244', true],
-      id: 1,
-    }),
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  })
-).then(resp => {
-  return resp.json();
+	new Request("https://web3-trial.cloudflare-eth.com/v1/rinkeby", {
+		method: "POST",
+		body: JSON.stringify({
+			jsonrpc: "2.0",
+			method: "eth_getBlockByNumber",
+			params: ["0x2244", true],
+			id: 1,
+		}),
+		headers: {
+			"Content-Type": "application/json",
+		},
+	}),
+).then((resp) => {
+	return resp.json();
 });
 ```
 
@@ -68,19 +67,19 @@ curl https://web3-trial.cloudflare-eth.com/v1/sepolia \
 
 ```js title="New JS Fetch API" {2}
 await fetch(
-  new Request('https://web3-trial.cloudflare-eth.com/v1/sepolia', {
-    method: 'POST',
-    body: JSON.stringify({
-      jsonrpc: '2.0',
-      method: 'eth_getBlockByNumber',
-      params: ['0x2244', true],
-      id: 1,
-    }),
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  })
-).then(resp => {
-  return resp.json();
+	new Request("https://web3-trial.cloudflare-eth.com/v1/sepolia", {
+		method: "POST",
+		body: JSON.stringify({
+			jsonrpc: "2.0",
+			method: "eth_getBlockByNumber",
+			params: ["0x2244", true],
+			id: 1,
+		}),
+		headers: {
+			"Content-Type": "application/json",
+		},
+	}),
+).then((resp) => {
+	return resp.json();
 });
 ```
diff --git a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
index b4932918c9e909b..dbc5a494061f6e0 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Supported networks - Ethereum Gateway
-
 ---
 
 Currently, Cloudflare Ethereum gateways support [interacting with](/web3/how-to/use-ethereum-gateway/) the following networks.
diff --git a/src/content/docs/web3/how-to/index.mdx b/src/content/docs/web3/how-to/index.mdx
index 09b45998630efc4..f6ebb1af9d9b691 100644
--- a/src/content/docs/web3/how-to/index.mdx
+++ b/src/content/docs/web3/how-to/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Web3 - How to
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
index 3987b7170bde027..d15b08583b61f0b 100644
--- a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
+++ b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
@@ -6,7 +6,6 @@ products:
 title: Use IPFS gateway
 sidebar:
   order: 2
-
 ---
 
 Once you have an IPFS gateway — meaning that you [create a new gateway](/web3/how-to/manage-gateways/#create-a-gateway) with a `target` of **IPFS** — you can get data from the IPFS network by using a URL.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
index 46ac314920cbb5a..f4449ce98f8c009 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
@@ -8,7 +8,6 @@ tags:
   - DNS
 sidebar:
   order: 4
-
 ---
 
 When you set up a gateway with a DNSLink record, that gateway is restricted to a particular piece of content — either a specific Content Identifier (CID) or an Interplanetary Name Service (IPNS) hostname. This is called a restricted gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
index 1f800c90518ab08..77d6c15618f0cde 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
@@ -9,10 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Concepts - IPFS Gateway
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 As you get started with Cloudflare's IPFS Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
index b47002eb8b4134b..754e32b96952c90 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
@@ -6,13 +6,12 @@ products:
 title: Automated deployments
 sidebar:
   order: 6
-
 ---
 
 Static sites are easy to deploy automatically. The code of the site is usually kept in a Git repository and deployed by pushing the latest commit to a repository that's connected to a Continuous Integration service like [Travis CI](https://travis-ci.org/), or by pushing to a repository directly on the server and activating a post-receive hook. Either way, the production version of the site is built and then copied into the serving path of an Apache or NGINX instance.
 
 IPFS usually fits into these systems: instead of copying the production version of a website into the serving path of an HTTP server, you would upload the same files to an IPFS node and update your DNS records with the new hash. There are several tools that help with different parts of this:
 
-* [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
-* [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
-* [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
+- [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
+- [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
+- [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/reference/index.mdx b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
index c69067dd176b415..10c80255fdf7a98 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - IPFS
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
index 574f2ebad732b96..81ab323e9cf901a 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
@@ -6,7 +6,6 @@ products:
 title: Peering
 sidebar:
   order: 5
-
 ---
 
 If you are running an IPFS node that serves many requests - like a public HTTP gateway - you may be able to speed up queries by maintaining long-lived connections to nodes that provide a large volume of data.
@@ -15,81 +14,57 @@ This process is known as **Peering** and you can tell IPFS to prioritize Cloudfl
 
 ```json
 {
-  "Peering": {
-    "Peers": [
-      {
-        "ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
-        "Addrs": [
-          "/dnsaddr/node-1.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
-        "Addrs": [
-          "/dnsaddr/node-2.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
-        "Addrs": [
-          "/dnsaddr/node-3.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
-        "Addrs": [
-          "/dnsaddr/node-4.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
-        "Addrs": [
-          "/dnsaddr/node-5.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
-        "Addrs": [
-          "/dnsaddr/node-6.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
-        "Addrs": [
-          "/dnsaddr/node-7.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
-        "Addrs": [
-          "/dnsaddr/node-8.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
-        "Addrs": [
-          "/dnsaddr/node-9.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
-        "Addrs": [
-          "/dnsaddr/node-10.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
-        "Addrs": [
-          "/dnsaddr/node-11.ingress.cloudflare-ipfs.com"
-        ]
-      },
-      {
-        "ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
-        "Addrs": [
-          "/dnsaddr/node-12.ingress.cloudflare-ipfs.com"
-        ]
-      }
-    ]
-  }
+	"Peering": {
+		"Peers": [
+			{
+				"ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
+				"Addrs": ["/dnsaddr/node-1.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
+				"Addrs": ["/dnsaddr/node-2.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
+				"Addrs": ["/dnsaddr/node-3.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
+				"Addrs": ["/dnsaddr/node-4.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
+				"Addrs": ["/dnsaddr/node-5.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
+				"Addrs": ["/dnsaddr/node-6.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
+				"Addrs": ["/dnsaddr/node-7.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
+				"Addrs": ["/dnsaddr/node-8.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
+				"Addrs": ["/dnsaddr/node-9.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
+				"Addrs": ["/dnsaddr/node-10.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
+				"Addrs": ["/dnsaddr/node-11.ingress.cloudflare-ipfs.com"]
+			},
+			{
+				"ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
+				"Addrs": ["/dnsaddr/node-12.ingress.cloudflare-ipfs.com"]
+			}
+		]
+	}
 }
 ```
diff --git a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
index f66712b07d379ed..9ae156f2b234174 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
@@ -6,14 +6,13 @@ products:
 title: Using IPFS with your website
 sidebar:
   order: 5
-
 ---
 
 Though it is not required, it is strongly recommended that websites hosted on IPFS use only relative links, unless linking to a different domain. This is because data can be accessed in many different (but ultimately equivalent) ways:
 
-* From your custom domain: `https://ipfs.tech/index.html`
-* From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
-* By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
+- From your custom domain: `https://ipfs.tech/index.html`
+- From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
+- By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
 
 Using only relative links within a web application supports all of these at once, and gives the most flexibility to the user. The exact method for switching to relative links, if you do not use them already, depends on the framework you use.
 
diff --git a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
index b76805532e21a27..658a32e0017e5e9 100644
--- a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
+++ b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
@@ -8,7 +8,6 @@ tags:
   - Debugging
 sidebar:
   order: 11
-
 ---
 
 ## Cloudflare-specific
diff --git a/src/content/docs/web3/reference/gateway-dns-records.mdx b/src/content/docs/web3/reference/gateway-dns-records.mdx
index c7ca135a158f53d..44ce03c721e9985 100644
--- a/src/content/docs/web3/reference/gateway-dns-records.mdx
+++ b/src/content/docs/web3/reference/gateway-dns-records.mdx
@@ -8,13 +8,12 @@ tags:
   - DNS
 sidebar:
   order: 1
-
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), Cloudflare automatically creates and adds records to your Cloudflare DNS so your gateway can receive and route traffic appropriately:
 
-* **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
-* **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
+- **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
+- **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
 
 These records cannot be edited within Cloudflare DNS. To make edits, you will have to [edit the gateway configuration](/web3/how-to/manage-gateways/#edit-a-gateway) itself.
 
diff --git a/src/content/docs/web3/reference/gateway-status.mdx b/src/content/docs/web3/reference/gateway-status.mdx
index f48cc0df30a6a4e..b8f41477bb010ac 100644
--- a/src/content/docs/web3/reference/gateway-status.mdx
+++ b/src/content/docs/web3/reference/gateway-status.mdx
@@ -6,7 +6,6 @@ products:
 title: Gateway status
 sidebar:
   order: 2
-
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), it can have one of several statuses.
diff --git a/src/content/docs/web3/reference/index.mdx b/src/content/docs/web3/reference/index.mdx
index 000a9dc1764b37c..d5e84b5cb473800 100644
--- a/src/content/docs/web3/reference/index.mdx
+++ b/src/content/docs/web3/reference/index.mdx
@@ -9,9 +9,8 @@ sidebar:
 head:
   - tag: title
     content: Reference - Web3 Gateways
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/reference/migration-guide.mdx b/src/content/docs/web3/reference/migration-guide.mdx
index 438c79c9d19f639..aa20fe71fbcb5ac 100644
--- a/src/content/docs/web3/reference/migration-guide.mdx
+++ b/src/content/docs/web3/reference/migration-guide.mdx
@@ -8,14 +8,13 @@ tags:
   - Migration
 sidebar:
   order: 4
-
 ---
 
 As announced in [our blog post](https://blog.cloudflare.com/ea-web3-gateways/), Cloudflare is deprecating legacy hostnames that point to our public gateway endpoints at `cloudflare-eth.com` and `cloudflare-ipfs.com`.
 
 If you created a hostname pointing to these gateways during the [private beta](https://blog.cloudflare.com/announcing-web3-gateways/), you should migrate to use our new Web3 gateways to avoid a disruption in service.
 
-***
+---
 
 ## Migration guide
 
diff --git a/src/content/docs/workers-ai/agents.mdx b/src/content/docs/workers-ai/agents.mdx
index 6987307dd6a54f5..b54052a2ddfb2a5 100644
--- a/src/content/docs/workers-ai/agents.mdx
+++ b/src/content/docs/workers-ai/agents.mdx
@@ -9,9 +9,12 @@ sidebar:
   order: 7
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
-<div style={{ textAlign: 'center', marginBottom: '2rem' }}>
-  <p>Build AI assistants that can perform complex tasks on behalf of your users using Cloudflare Workers AI and Agents.</p>
-  <LinkButton href="/agents/">Go to Agents documentation</LinkButton>
-</div>
\ No newline at end of file
+<div style={{ textAlign: "center", marginBottom: "2rem" }}>
+	<p>
+		Build AI assistants that can perform complex tasks on behalf of your users
+		using Cloudflare Workers AI and Agents.
+	</p>
+	<LinkButton href="/agents/">Go to Agents documentation</LinkButton>
+</div>
diff --git a/src/content/docs/workers-ai/api-reference.mdx b/src/content/docs/workers-ai/api-reference.mdx
index 62cc80dfcec7e8a..d4399b2cedbf0b1 100644
--- a/src/content/docs/workers-ai/api-reference.mdx
+++ b/src/content/docs/workers-ai/api-reference.mdx
@@ -7,5 +7,4 @@ products:
   - workers-ai
 sidebar:
   order: 9
-
 ---
diff --git a/src/content/docs/workers-ai/configuration/bindings.mdx b/src/content/docs/workers-ai/configuration/bindings.mdx
index 51750be8e394b68..679ad1f230931bf 100644
--- a/src/content/docs/workers-ai/configuration/bindings.mdx
+++ b/src/content/docs/workers-ai/configuration/bindings.mdx
@@ -43,33 +43,27 @@ To configure a Workers AI binding in your Pages Function, you must use the Cloud
 `async env.AI.run()` runs a model. Takes a model as the first parameter, and an object as the second parameter.
 
 ```javascript
-const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
-    prompt: "What is the origin of the phrase 'Hello, World'"
+const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
+	prompt: "What is the origin of the phrase 'Hello, World'",
 });
 ```
 
 **Parameters**
 
-
-
-* `model` <Type text="string" /> <MetaInfo text="required" />
-
-  * The model to run.
+- `model` <Type text="string" /> <MetaInfo text="required" />
+  - The model to run.
 
   **Supported options**
-
-  * `stream` <Type text="boolean" /> <MetaInfo text="optional" />
-    * Returns a stream of results as they are available.
-
-
+  - `stream` <Type text="boolean" /> <MetaInfo text="optional" />
+    - Returns a stream of results as they are available.
 
 ```javascript
-const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
-    prompt: "What is the origin of the phrase 'Hello, World'",
-    stream: true
+const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
+	prompt: "What is the origin of the phrase 'Hello, World'",
+	stream: true,
 });
 
 return new Response(answer, {
-    headers: { "content-type": "text/event-stream" }
+	headers: { "content-type": "text/event-stream" },
 });
 ```
diff --git a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
index fe7d83c834c46c7..9daadf9eb13e568 100644
--- a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
+++ b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
@@ -14,9 +14,9 @@ Use Workers AI with [Chat UI](https://github.com/huggingface/chat-ui?tab=readme-
 
 You will need the following:
 
-* A [Cloudflare account](https://dash.cloudflare.com)
-* Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
-* An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
+- A [Cloudflare account](https://dash.cloudflare.com)
+- Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
+- An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
 
 ## Setup
 
@@ -28,20 +28,20 @@ When setting up your models, specify the `cloudflare` endpoint.
 
 ```json
 {
-  "name" : "nousresearch/hermes-2-pro-mistral-7b",
-  "tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
-  "parameters": {
-    "stop": ["<|im_end|>"]
-  },
-  "endpoints" : [
-    {
-      "type": "cloudflare",
-      // optionally specify these if not included in .env.local
-      "accountId": "your-account-id",
-      "apiToken": "your-api-token"
-      //
-    }
-  ]
+	"name": "nousresearch/hermes-2-pro-mistral-7b",
+	"tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
+	"parameters": {
+		"stop": ["<|im_end|>"]
+	},
+	"endpoints": [
+		{
+			"type": "cloudflare",
+			// optionally specify these if not included in .env.local
+			"accountId": "your-account-id",
+			"apiToken": "your-api-token"
+			//
+		}
+	]
 }
 ```
 
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
index 1f531e7b4d8115a..defd31249419534 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
@@ -20,7 +20,7 @@ To do so a `getWeather` function is defined that is passed to the LLM as tool.
 The `getWeather`function extracts the user's location from the request and calls the external weather API via the Workers' [`Fetch API`](/workers/runtime-apis/fetch/) and returns the result.
 
 ```ts title="Embedded function calling example with fetch()"
-import { runWithTools } from '@cloudflare/ai-utils';
+import { runWithTools } from "@cloudflare/ai-utils";
 
 type Env = {
 	AI: Ai;
@@ -31,14 +31,14 @@ export default {
 		// Define function
 		const getWeather = async (args: { numDays: number }) => {
 			const { numDays } = args;
-      // Location is extracted from request based on
-      // https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
-      const lat = request.cf?.latitude
-      const long = request.cf?.longitude
+			// Location is extracted from request based on
+			// https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
+			const lat = request.cf?.latitude;
+			const long = request.cf?.longitude;
 
-      // Interpolate values for external API call
+			// Interpolate values for external API call
 			const response = await fetch(
-				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`
+				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`,
 			);
 			return response.text();
 		};
@@ -46,35 +46,37 @@ export default {
 		const response = await runWithTools(
 			env.AI,
 			// Model with function calling support
-			'@hf/nousresearch/hermes-2-pro-mistral-7b',
+			"@hf/nousresearch/hermes-2-pro-mistral-7b",
 			{
 				// Messages
 				messages: [
 					{
-						role: 'user',
-						content: 'What the weather like the next 5 days? Respond as text',
+						role: "user",
+						content: "What the weather like the next 5 days? Respond as text",
 					},
 				],
 				// Definition of available tools the AI model can leverage
 				tools: [
 					{
-						name: 'getWeather',
-						description: 'Get the weather for the next [numDays] days',
+						name: "getWeather",
+						description: "Get the weather for the next [numDays] days",
 						parameters: {
-							type: 'object',
+							type: "object",
 							properties: {
-								numDays: { type: 'numDays', description: 'number of days for the weather forecast' },
+								numDays: {
+									type: "numDays",
+									description: "number of days for the weather forecast",
+								},
 							},
-							required: ['numDays'],
+							required: ["numDays"],
 						},
 						// reference to previously defined function
 						function: getWeather,
 					},
 				],
-			}
+			},
 		);
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
-
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
index f70be9e51f5b064..1f3842dcb258da4 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
@@ -12,6 +12,7 @@ description: Learn how to use Cloudflare Workers AI to interact with KV storage,
 Interact with persistent storage to retrieve or store information enables for powerful use cases.
 
 In this example we show how embedded function calling can interact with other resources on the Cloudflare Developer Platform with a few lines of code.
+
 ## Pre-Requisites
 
 For this example to work, you need to provision a [KV](/kv/) namespace first. To do so, follow the [KV - Get started ](/kv/get-started/) guide.
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
index 99f3b4077c79279..0d5b64aae3a9a86 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
@@ -15,54 +15,54 @@ Oftentimes APIs are defined and documented via [OpenAPI specification](https://s
 In this example the LLM will describe the a Github user, based Github's API and its OpenAPI spec.
 
 ```ts title="Embedded function calling example from OpenAPI Spec"
-import { createToolsFromOpenAPISpec, runWithTools } from '@cloudflare/ai-utils';
+import { createToolsFromOpenAPISpec, runWithTools } from "@cloudflare/ai-utils";
 
 type Env = {
 	AI: Ai;
 };
 
-const APP_NAME = 'cf-fn-calling-example-app';
+const APP_NAME = "cf-fn-calling-example-app";
 
 export default {
 	async fetch(request, env, ctx) {
 		const toolsFromOpenAPISpec = [
 			// You can pass the OpenAPI spec link or contents directly
 			...(await createToolsFromOpenAPISpec(
-				'https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json',
+				"https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json",
 				{
 					overrides: [
 						{
 							matcher: ({ url }) => {
-								return url.hostname === 'api.github.com';
+								return url.hostname === "api.github.com";
 							},
 							// for all requests on *.github.com, we'll need to add a User-Agent.
 							values: {
 								headers: {
-									'User-Agent': APP_NAME,
+									"User-Agent": APP_NAME,
 								},
 							},
 						},
 					],
-				}
+				},
 			)),
 		];
 
 		const response = await runWithTools(
 			env.AI,
-			'@hf/nousresearch/hermes-2-pro-mistral-7b',
+			"@hf/nousresearch/hermes-2-pro-mistral-7b",
 			{
 				messages: [
 					{
-						role: 'user',
-						content: 'Who is cloudflare on Github and how many repos does the organization have?',
+						role: "user",
+						content:
+							"Who is cloudflare on Github and how many repos does the organization have?",
 					},
 				],
 				tools: toolsFromOpenAPISpec,
-			}
+			},
 		);
 
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
-
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
index 559cf113e209a3a..c246533acd9ad9b 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare has a unique [embedded function calling](https://blog.cloudflare.com/embedded-function-calling) feature that allows you to execute function code alongside your tool call inference. Our npm package [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) is the developer toolkit to get started.
 
@@ -21,10 +21,8 @@ Embedded function calling can be used to easily make complex agents that interac
 
 :::caution[REST API support]
 
-
 Embedded function calling depends on features native to the Workers platform. This means that embedded function calling is only supported via [Cloudflare Workers](/workers-ai/get-started/workers-wrangler/), not via the [REST API](/workers-ai/get-started/rest-api/).
 
-
 :::
 
 ## Resources
diff --git a/src/content/docs/workers-ai/get-started/dashboard.mdx b/src/content/docs/workers-ai/get-started/dashboard.mdx
index 2ba3fce6dbc68cc..e22a698bbeddce6 100644
--- a/src/content/docs/workers-ai/get-started/dashboard.mdx
+++ b/src/content/docs/workers-ai/get-started/dashboard.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Follow this guide to create a Workers AI application using the Cloudflare dashboard.
 
@@ -26,11 +26,12 @@ To create a Workers AI application:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Under **Select a template**, select **LLM Chat App**.
 4. Select **Deploy**.
 5. Name your Worker, then select **Create and deploy**.
-5. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
+6. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
 
 ## Development
 
diff --git a/src/content/docs/workers-ai/get-started/index.mdx b/src/content/docs/workers-ai/get-started/index.mdx
index 707509ca784b6a0..a6eeb86d18d02ef 100644
--- a/src/content/docs/workers-ai/get-started/index.mdx
+++ b/src/content/docs/workers-ai/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 There are several options to build your Workers AI projects on Cloudflare. To get started, choose your preferred method:
 
@@ -16,8 +16,6 @@ There are several options to build your Workers AI projects on Cloudflare. To ge
 
 :::note
 
-
 These examples are geared towards creating new Workers AI projects. For help adding Workers AI to an existing Worker, refer to [Workers Bindings](/workers-ai/configuration/bindings/).
 
-
 :::
diff --git a/src/content/docs/workers-ai/get-started/rest-api.mdx b/src/content/docs/workers-ai/get-started/rest-api.mdx
index e25c56fa87f355a..bd2a6f0630db0aa 100644
--- a/src/content/docs/workers-ai/get-started/rest-api.mdx
+++ b/src/content/docs/workers-ai/get-started/rest-api.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 This guide will instruct you through setting up and deploying your first Workers AI project. You will use the Workers AI REST API to experiment with a large language model (LLM).
 
@@ -28,6 +28,7 @@ To get these values:
 1. In the Cloudflare dashboard, go to the **Workers AI** page.
 
    <DashButton url="/?to=/:account/ai/workers-ai" />
+
 2. Select **Use REST API**.
 3. Get your API token:
    1. Select **Create a Workers AI API Token**.
diff --git a/src/content/docs/workers-ai/guides/agents.mdx b/src/content/docs/workers-ai/guides/agents.mdx
index 1e57ab991facb86..86751d6187c1375 100644
--- a/src/content/docs/workers-ai/guides/agents.mdx
+++ b/src/content/docs/workers-ai/guides/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workers-ai
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
index bc3a24a9954b382..3b27b14dfda0ebb 100644
--- a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
@@ -14,9 +14,7 @@ products:
   - workers-ai
 ---
 
-
-
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 A handy way to explore all of the models available on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -26,7 +24,7 @@ You can [download the DeepSeek Coder notebook](/workers-ai/static/documentation/
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
-***
+---
 
 ## Exploring Code Generation Using DeepSeek Coder
 
@@ -229,8 +227,8 @@ if __name__ == '__main__':
 
 In this test case, we have two tests:
 
-* `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
-* `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
+- `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
+- `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
 
 If all these tests pass, it means that the `full_name` method is working as expected. If any of these tests fail, it
 
@@ -346,9 +344,9 @@ display(Markdown(f"""
 
 ```json
 {
-  "firstName": "Craig",
-  "lastName": "Dennis",
-  "numKids": 2,
-  "interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
+	"firstName": "Craig",
+	"lastName": "Dennis",
+	"numKids": 2,
+	"interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
 }
 ```
diff --git a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
index 3ca61769775d494..bb75cb0837843ae 100644
--- a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
@@ -17,9 +17,7 @@ products:
   - workers-ai
 ---
 
-
-
-import { YouTube } from "~/components"
+import { YouTube } from "~/components";
 
 A great way to explore the models that are available to you on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -29,7 +27,7 @@ You can [download the Workers AI Text Generation Exploration notebook](/workers-
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
-***
+---
 
 ## How to Choose The Right Text Generation Model
 
@@ -148,7 +146,7 @@ questions = [
 speed_date(models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -172,9 +170,9 @@ speed_date(models, questions)
 
 *Generated in *3.63* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -194,9 +192,9 @@ speed_date(models, questions)
 
 *Generated in *4.33* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -216,9 +214,9 @@ speed_date(models, questions)
 
 *Generated in *3.15* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -242,9 +240,9 @@ Remember, these are just a few examples, and your use cases may vary depending o
 
 *Generated in *2.92* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -272,7 +270,7 @@ That's me in a nutshell! I'm ready to help with a wide range of tasks, so feel f
 
 *Generated in *10.28* seconds*
 
-***
+---
 
 ### Language Translation
 
@@ -299,7 +297,7 @@ questions = [f"""Translate "{phrase}" from "English" to "{language}" """
 speed_date(proud_translator_models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -389,9 +387,9 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *3.44* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -467,7 +465,7 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *1.51* seconds*
 
-***
+---
 
 ### Information Retrieval and Summarization
 
@@ -493,7 +491,7 @@ questions = [f"""Summarize the book "{book}" into a few sentences. Ensure to inc
 speed_date(proud_summarizers, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -521,9 +519,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *8.34* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -545,9 +543,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.04* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -569,7 +567,7 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.66* seconds*
 
-***
+---
 
 ### Content Creation
 
@@ -591,7 +589,7 @@ questions = [
 speed_date(proud_content_creator_models, questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -627,9 +625,9 @@ I hope these suggestions help! Let me know if you have any other questions or if
 
 *Generated in *1.13* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -659,9 +657,9 @@ Tagline: "Say goodbye to cable chaos and hello to a clutter-free workspace with
 
 *Generated in *1.33* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -702,15 +700,15 @@ Sure, here's a headline for a blog on why you should use me specifically over ot
 
 Here's a brief summary of why I stand out from other models:
 
-* Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
-* Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
-* Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
+- Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
+- Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
+- Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
 
 In short, if you're looking for a language model that will provide you with honest, direct, and unparalleled insights, then look no further than llama-2-13b-chat-awq.
 
 *Generated in *10.24* seconds*
 
-***
+---
 
 ### Text Classification
 
@@ -741,7 +739,7 @@ sentiment_questions = [sentiment_prompt_template.format(text=comment) for commen
 speed_date(proud_classifiers, sentiment_questions)
 ```
 
-***
+---
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -787,9 +785,9 @@ The sentiment of the text is positive.
 
 *Generated in *0.89* seconds*
 
-***
+---
 
-***
+---
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -833,4 +831,4 @@ The sentiment of the text is positive.
 
 *Generated in *1.93* seconds*
 
-***
+---
diff --git a/src/content/docs/workers-ai/platform/data-usage.mdx b/src/content/docs/workers-ai/platform/data-usage.mdx
index 9b29840f9db5768..bab6821ff99f590 100644
--- a/src/content/docs/workers-ai/platform/data-usage.mdx
+++ b/src/content/docs/workers-ai/platform/data-usage.mdx
@@ -19,7 +19,7 @@ Your inputs (e.g., text prompts, image submissions, audio files, etc.), outputs
 
 For Workers AI:
 
-* You own, and are responsible for, all of your Customer Content.
-* Cloudflare does not make your Customer Content available to any other Cloudflare customer.
-* Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
-* Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
+- You own, and are responsible for, all of your Customer Content.
+- Cloudflare does not make your Customer Content available to any other Cloudflare customer.
+- Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
+- Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
diff --git a/src/content/docs/workers-ai/platform/pricing.mdx b/src/content/docs/workers-ai/platform/pricing.mdx
index fd38831c6ee17fc..474edbfe1bdd8fb 100644
--- a/src/content/docs/workers-ai/platform/pricing.mdx
+++ b/src/content/docs/workers-ai/platform/pricing.mdx
@@ -35,38 +35,38 @@ The Price in Tokens column is equivalent to the Price in Neurons column - the di
 
 ## LLM model pricing
 
-| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                       |
-| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                |
-| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                |
-| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
-| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
-| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                              |
-| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                               |
-| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                               |
-| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
-| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
-| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
-| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                              |
-| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                |
-| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                               |
-| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                               |
-| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
-| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
-| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
-| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                               |
-| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                               |
-| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
-| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                |
-| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                |
-| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                              |
-| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens |
+| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                        |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                 |
+| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
+| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
+| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                               |
+| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                                |
+| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
+| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
+| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
+| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                               |
+| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                 |
+| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                                |
+| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                                |
+| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
+| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
+| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
+| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                                |
+| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
+| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
+| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                 |
+| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                 |
+| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                               |
+| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens  |
 | @cf/moonshotai/kimi-k2.6                     | $0.950 per M input tokens <br/> $0.160 per M cached input tokens <br/> $4.000 per M output tokens | 86364 neurons per M input tokens <br/> 14545 neurons per M cached input tokens <br/> 363636 neurons per M output tokens |
-| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
+| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                 |
 
 ## Embeddings model pricing
 
diff --git a/src/content/docs/workers-vpc/configuration/index.mdx b/src/content/docs/workers-vpc/configuration/index.mdx
index aee79d0d23cdc78..e669ed279505b79 100644
--- a/src/content/docs/workers-vpc/configuration/index.mdx
+++ b/src/content/docs/workers-vpc/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
index e5d02896289509c..da1a8323544eed5 100644
--- a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
+++ b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
@@ -128,6 +128,7 @@ resource "cloudflare_connectivity_directory_service" "my_database" {
 ```
 
 Valid values for `cert_verification_mode` are:
+
 - `verify_full` (default)
 - `verify_ca`
 - `disabled`
diff --git a/src/content/docs/workers-vpc/examples/private-api.mdx b/src/content/docs/workers-vpc/examples/private-api.mdx
index 48bc4d0013d7733..09e90435cc172fe 100644
--- a/src/content/docs/workers-vpc/examples/private-api.mdx
+++ b/src/content/docs/workers-vpc/examples/private-api.mdx
@@ -87,7 +87,9 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch data from internal API and process it before returning
-			const response = await env.INTERNAL_API.fetch("http://10.0.1.50:8080/api/data");
+			const response = await env.INTERNAL_API.fetch(
+				"http://10.0.1.50:8080/api/data",
+			);
 
 			// Use the response of the private API to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
index 12fb5230fee07fe..3312f993bec679d 100644
--- a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
+++ b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
@@ -125,7 +125,9 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch a file from the private S3 bucket via VPC endpoint
-			const response = await env.S3_STORAGE.fetch("https://s3.us-west-2.amazonaws.com/my-bucket/data.json");
+			const response = await env.S3_STORAGE.fetch(
+				"https://s3.us-west-2.amazonaws.com/my-bucket/data.json",
+			);
 
 			// Use the response from S3 to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
index 6bc0349de2f2609..60995de99ab8b3c 100644
--- a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
+++ b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
@@ -72,15 +72,19 @@ export default {
 		const url = new URL(request.url);
 
 		// Route to internal services
-		if (url.pathname.startsWith('/api/users')) {
-			const response = await env.USER_SERVICE.fetch("https://user-api.internal.example.com" + url.pathname);
+		if (url.pathname.startsWith("/api/users")) {
+			const response = await env.USER_SERVICE.fetch(
+				"https://user-api.internal.example.com" + url.pathname,
+			);
 			return response;
-		} else if (url.pathname.startsWith('/api/orders')) {
-			const response = await env.ORDER_SERVICE.fetch("https://orders-api.internal.example.com" + url.pathname);
+		} else if (url.pathname.startsWith("/api/orders")) {
+			const response = await env.ORDER_SERVICE.fetch(
+				"https://orders-api.internal.example.com" + url.pathname,
+			);
 			return response;
 		}
 
-		return new Response('Not Found', { status: 404 });
+		return new Response("Not Found", { status: 404 });
 	},
 };
 ```
@@ -107,4 +111,3 @@ curl https://api-gateway.workers.dev/api/orders
 - Implement [rate limiting](/durable-objects/api/)
 - Set up [monitoring and alerting](/analytics/analytics-engine/)
 - Explore [other examples](/workers-vpc/examples/)
-
diff --git a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
index 570cd2dcec2d850..42c63e8209e1e50 100644
--- a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
+++ b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
@@ -53,6 +53,7 @@ When you merge the PR, Workers Builds will update your build and deploy commands
 If Workers Builds detects a mismatch between your Worker name in the Cloudflare dashboard and the `name` field in your Wrangler configuration file, it will create a pull request to fix the conflict.
 
 This can happen when:
+
 - You rename your Worker in the dashboard but not in your config file
 - You connect a repository that was previously used with a different Worker
 - The `name` field in your config does not match the connected Worker
diff --git a/src/content/docs/workers/ci-cd/builds/build-caching.mdx b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
index 83e4dd1c9c17496..603f75d3db137a1 100644
--- a/src/content/docs/workers/ci-cd/builds/build-caching.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
@@ -35,15 +35,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                                          |
-| ---------- | ----------------------------------------------------------- |
-| Astro      | `node_modules/.astro`                                       |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
-| Eleventy   | `.cache`                                                    |
-| Gatsby     | `.cache`, `public`                                          |
-| Next.js    | `.next/cache`                                               |
-| Nuxt       | `node_modules/.cache/nuxt`                                  |
-| SvelteKit  | `node_modules/.cache/imagetools`                            |
+| Framework  | Directories cached                            |
+| ---------- | --------------------------------------------- |
+| Astro      | `node_modules/.astro`                         |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
+| Eleventy   | `.cache`                                      |
+| Gatsby     | `.cache`, `public`                            |
+| Next.js    | `.next/cache`                                 |
+| Nuxt       | `node_modules/.cache/nuxt`                    |
+| SvelteKit  | `node_modules/.cache/imagetools`              |
 
 :::note
 [Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers.
diff --git a/src/content/docs/workers/ci-cd/builds/build-image.mdx b/src/content/docs/workers/ci-cd/builds/build-image.mdx
index 828b464902269e7..0daab950f2f9c35 100644
--- a/src/content/docs/workers/ci-cd/builds/build-image.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-image.mdx
@@ -91,7 +91,6 @@ Workers Builds are run in the following environment:
 | **Build Environment** | Ubuntu 24.04 |
 | **Architecture**      | x86_64       |
 
-
 ## Build Image Policy
 
 ### Preinstalled Software Updates
@@ -102,6 +101,7 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
+
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -111,5 +111,6 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
+
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
\ No newline at end of file
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
index 032d023592e4d4f..6d533ab9b2cede9 100644
--- a/src/content/docs/workers/ci-cd/builds/configuration.mdx
+++ b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -8,7 +8,13 @@ products:
   - workers
 ---
 
-import { DirectoryListing, Render, Tabs, TabItem, DashButton } from "~/components";
+import {
+	DirectoryListing,
+	Render,
+	Tabs,
+	TabItem,
+	DashButton,
+} from "~/components";
 
 When connecting your Git repository to your Worker, you can customize the configurations needed to build and deploy your Worker.
 
@@ -35,7 +41,7 @@ Note that when you update and save build settings, the updated settings will be
 | **Git repository**                                                                                                    | Choose the Git repository you would like to connect your Worker to.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | **Git branch**                                                                                                        | Select the branch you would like Cloudflare to listen to for new commits. This will be defaulted to `main`.                                                                                                                                                                                                                                                                                                                                                                            |
 | **Build command** _(Optional)_                                                                                        | Set a build command if your project requires a build step (e.g. `npm run build`). This is necessary, for example, when using a [front-end framework](/workers/ci-cd/builds/configuration/#framework-support) such as Next.js or Remix.                                                                                                                                                                                                                                                 |
-| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                                 |
+| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                         |
 | **[Non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command)** | Set a command to run when executing [a build for commit on a non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds). This will default to `npx wrangler versions upload` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                    |
 | **Root directory** _(Optional)_                                                                                       | Specify the path to your project. The root directory defines where the build command will be run and can be helpful in [monorepos](/workers/ci-cd/builds/advanced-setups/#monorepos) to isolate a specific project within the repository for builds.                                                                                                                                                                                                                                   |
 | **[API token](/workers/ci-cd/builds/configuration/#api-token)** _(Optional)_                                          | The API token is used to authenticate your build request and authorize the upload and deployment of your Worker to Cloudflare. By default, Cloudflare will automatically generate an API token for your account when using Workers Builds, and continue to use this API token for all subsequent builds. Alternatively, you can [create your own API token](/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication/#generate-tokens), or select one that you already own. |
@@ -128,4 +134,4 @@ The following system environment variables are injected by default (but can be o
 | `WORKERS_CI`            | `1`                             | Changing build behaviour when run on Workers Builds versus locally                      |
 | `WORKERS_CI_BUILD_UUID` | `<build-uuid-of-current-build>` | Passing the Build UUID along to custom workflows                                        |
 | `WORKERS_CI_COMMIT_SHA` | `<sha1-hash-of-current-commit>` | Passing current commit ID to error reporting, for example, Sentry                       |
-| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
\ No newline at end of file
+| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
index 19c36e00c988216..6438ba7c4ac10cf 100644
--- a/src/content/docs/workers/ci-cd/builds/index.mdx
+++ b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -7,6 +7,7 @@ sidebar:
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets you connect a new or existing Worker to a GitHub or GitLab repository, enabling automated builds and deployments for your Worker on push.
@@ -16,6 +17,7 @@ The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets yo
 ### Connect a new Worker
 
 To create a new Worker and connect it to a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -30,6 +32,7 @@ To create a new Worker and connect it to a GitHub or GitLab repository:
 ### Connect an existing Worker
 
 To connect an existing Worker to a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -71,14 +74,15 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 ## Disconnecting builds
 
 To disconnect a Worker from a GitHub or GitLab repository:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select the Worker you want to disconnect from a repository.
-4. Select **Settings** and then **Builds**.
-5. Select **Disconnect**.
+3. Select **Settings** and then **Builds**.
+4. Select **Disconnect**.
 
 If you want to switch to a different repository for your Worker, you must first disable builds, then reconnect to select the new repository.
 
-To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
\ No newline at end of file
+To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
diff --git a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
index 12161e725454792..b5fe2e420f07c48 100644
--- a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
+++ b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
@@ -8,19 +8,19 @@ products:
   - workers
 ---
 
-Workers Builds has the following limits. 
+Workers Builds has the following limits.
 
-| Metric                | Free plan       | Paid plans                                 |
-| --------------------- | --------------- | ------------------------------------------ |
-| **Build minutes**     | 3,000 per month | 6,000 per month (then, +$0.005 per minute) |
-| **Concurrent builds** | 1               | 6                                          |
-| **Build timeout**     | 20 minutes      | 20 minutes                                 |
-| **Deploy Hooks**      | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account |
-| **CPU**               | 2 vCPU          | 4 vCPU                                     |
-| **Memory**            | 8 GB            | 8 GB                                       |
-| **Disk space**        | 20 GB           | 20 GB                                      |
-| **Environment variables**  | 64              | 64                                        |
-| **Size per environment variable**  | 5 KB            | 5 KB                                       |
+| Metric                            | Free plan                              | Paid plans                                 |
+| --------------------------------- | -------------------------------------- | ------------------------------------------ |
+| **Build minutes**                 | 3,000 per month                        | 6,000 per month (then, +$0.005 per minute) |
+| **Concurrent builds**             | 1                                      | 6                                          |
+| **Build timeout**                 | 20 minutes                             | 20 minutes                                 |
+| **Deploy Hooks**                  | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account     |
+| **CPU**                           | 2 vCPU                                 | 4 vCPU                                     |
+| **Memory**                        | 8 GB                                   | 8 GB                                       |
+| **Disk space**                    | 20 GB                                  | 20 GB                                      |
+| **Environment variables**         | 64                                     | 64                                         |
+| **Size per environment variable** | 5 KB                                   | 5 KB                                       |
 
 ## Definitions
 
diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
index 19e65105b5e0d03..34a4b8f9fba5a10 100644
--- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
+++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
@@ -35,6 +35,7 @@ On Wrangler v3 and up, Workers Builds automatically matches the name of the conn
 `✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. wrangler deploy path/to/script) or the main config field.`
 
 If you see this error, a Wrangler configuration file is likely missing from the root directory. Navigate to **Settings** > **Build** > **Build Configuration** to update the root directory, or add a [Wrangler configuration file](/workers/wrangler/configuration/) to the specified directory.
+
 ### Incorrect account_id
 
 `Could not route to /client/v4/accounts/<Account ID>/workers/services/<Worker name>, perhaps your object identifier is invalid? [code: 7003]`
diff --git a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
index 2eae230b3612062..f67f5ae1685a419 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
@@ -5,6 +5,7 @@ description: Integrate Workers development into your existing GitHub Actions wor
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitHub Actions](https://github.com/marketplace/actions/deploy-to-cloudflare-workers-with-wrangler). Here is how you can set up your GitHub Actions workflow.
@@ -20,6 +21,7 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
 ### API token
 
 To create an API token to authenticate Wrangler in your CI job:
+
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
diff --git a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
index ad35eea9bad7ff5..713a4dfc47d7707 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
@@ -5,6 +5,7 @@ description: Integrate Workers development into your existing GitLab Pipelines w
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitLab CI/CD](https://docs.gitlab.com/ee/ci/pipelines/index.html). Here is how you can set up your Gitlab CI/CD pipeline.
diff --git a/src/content/docs/workers/configuration/integrations/index.mdx b/src/content/docs/workers/configuration/integrations/index.mdx
index 23a188bf0e4e94c..e9f73b20e932138 100644
--- a/src/content/docs/workers/configuration/integrations/index.mdx
+++ b/src/content/docs/workers/configuration/integrations/index.mdx
@@ -14,24 +14,24 @@ One of the key features of Cloudflare Workers is the ability to integrate with o
 
 Cloudflare Workers offers several types of integrations, including:
 
-* [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
-* [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
-* [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
+- [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
+- [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
+- [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
 
 ## How to use integrations
 
 To use any of the available integrations:
 
-* Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
-* In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
-* Use the provided APIs and functions to connect to the integration and access its data or functionality.
-* Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
+- Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
+- In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
+- Use the provided APIs and functions to connect to the integration and access its data or functionality.
+- Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
 
 ## Tips and best practices
 
 To help you get the most out of using integrations with Cloudflare Workers:
 
-* Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
-* Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
-* Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
-* Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
+- Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
+- Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
+- Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
+- Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
diff --git a/src/content/docs/workers/configuration/routing/custom-domains.mdx b/src/content/docs/workers/configuration/routing/custom-domains.mdx
index be78f27efb57efa..dccd631d43e8638 100644
--- a/src/content/docs/workers/configuration/routing/custom-domains.mdx
+++ b/src/content/docs/workers/configuration/routing/custom-domains.mdx
@@ -14,7 +14,7 @@ Custom Domains allow you to connect your Worker to a domain or subdomain, withou
 
 Custom Domains are routes to a domain or subdomain (such as `example.com` or `shop.example.com`) within a Cloudflare zone where the Worker is the origin.
 
-Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with.  If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
+Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with. If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
 
 Custom Domains can stack on top of each other. For example, if you have Worker A attached to `app.example.com` and Worker B attached to `api.example.com`, Worker A can call `fetch()` on `api.example.com` and invoke Worker B.
 
@@ -33,10 +33,8 @@ Custom Domains can be attached to your Worker via the Cloudflare dashboard, [Wra
 
 :::caution
 
-
 You cannot create a Custom Domain on a hostname with an existing CNAME DNS record or on a zone you do not own.
 
-
 :::
 
 ### Set up a Custom Domain in the dashboard
@@ -77,8 +75,6 @@ To configure a Custom Domain in your [Wrangler configuration file](/workers/wran
 
 To configure multiple Custom Domains:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -106,8 +102,8 @@ On the same zone, if a Worker is attempting to communicate with a target Worker
 
 For example, consider the following scenario, where both Workers are running on the `example.com` Cloudflare zone:
 
-* `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
-* `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
+- `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
+- `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
 
 If `worker-a` sends a fetch request to `worker-b`, the request will fail, because of the limitation on same-zone fetch requests. `worker-a` must have a service binding to `worker-b` for this request to resolve.
 
@@ -115,9 +111,9 @@ If `worker-a` sends a fetch request to `worker-b`, the request will fail, becaus
 export default {
 	fetch(request) {
 		// This will fail
-		return fetch("https://shop.example.com")
-	}
-}
+		return fetch("https://shop.example.com");
+	},
+};
 ```
 
 However, if `worker-b` was instead set up to run on the Custom Domain `shop.example.com`, the fetch request would succeed.
@@ -142,15 +138,15 @@ For example, consider the following workflow:
 ```js title="auth-worker" {8}
 export default {
 	fetch(request) {
-		const url = new URL(request.url)
-		if(url.searchParams.get("auth") !== "SECRET_TOKEN") {
-			return new Response(null, { status: 401 })
+		const url = new URL(request.url);
+		if (url.searchParams.get("auth") !== "SECRET_TOKEN") {
+			return new Response(null, { status: 401 });
 		} else {
 			// This will invoke `api-worker`
-			return fetch(request)
+			return fetch(request);
 		}
-	}
-}
+	},
+};
 ```
 
 ## Certificates
@@ -166,10 +162,10 @@ Because Custom Domains require an exact hostname match, a Worker attached to `ex
 - [Redirect from www to root](/rules/url-forwarding/examples/redirect-www-to-root/)
 - [Redirect from root to www](/rules/url-forwarding/examples/redirect-root-to-www/)
 
-You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting *from*, so that Cloudflare can apply the redirect rule.
+You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting _from_, so that Cloudflare can apply the redirect rule.
 
-  - For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
-  - For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+- For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+- For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
 
 :::note
 `192.0.2.0` (A record) and `100::` (AAAA record) are [reserved placeholder addresses](/dns/manage-dns-records/how-to/create-dns-records/#originless-setups) for originless setups. Because the DNS record is proxied, requests never reach this address — Cloudflare intercepts them and applies your redirect rule.
@@ -224,4 +220,4 @@ To migrate the route `example.com/*` in your [Wrangler configuration file](/work
    </WranglerConfig>
 
 4. Run `npx  wrangler deploy` to create the Custom Domain your Worker will run on.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/workers/configuration/routing/routes.mdx b/src/content/docs/workers/configuration/routing/routes.mdx
index 867c38239a1de4e..977bc4da059df0f 100644
--- a/src/content/docs/workers/configuration/routing/routes.mdx
+++ b/src/content/docs/workers/configuration/routing/routes.mdx
@@ -95,8 +95,6 @@ Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `z
 
 To add multiple routes:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -194,12 +192,12 @@ Because `*` matches zero or more of **any character** (not just subdomains), `*e
 
 The following examples illustrate the difference between `*example.com/*` and `*.example.com/*`:
 
-| Request URL | `*example.com/*` | `*.example.com/*` |
-|---|---|---|
-| `https://example.com/` | Matches | Does not match |
-| `https://www.example.com/path` | Matches | Matches |
-| `https://myexample.com/` | Matches | Does not match |
-| `https://not-example.com/` | Does not match | Does not match |
+| Request URL                    | `*example.com/*` | `*.example.com/*` |
+| ------------------------------ | ---------------- | ----------------- |
+| `https://example.com/`         | Matches          | Does not match    |
+| `https://www.example.com/path` | Matches          | Matches           |
+| `https://myexample.com/`       | Matches          | Does not match    |
+| `https://not-example.com/`     | Does not match   | Does not match    |
 
 #### Paths may optionally end with `*`
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-existing.mdx b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
index 5ec6aea9c3faf4a..005eac692d1bd1f 100644
--- a/src/content/docs/workers/configuration/sites/start-from-existing.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
@@ -40,16 +40,16 @@ To deploy a pre-existing static site project, start with a pre-generated site. W
 2. Add your site's build/output directory to the Wrangler file:
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "site": {
-       "bucket": "./public" // <-- Add your build directory name here.
-     }
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "site": {
+          "bucket": "./public" // <-- Add your build directory name here.
+        }
+      }
+      ```
+   
+      </WranglerConfig>
 
    The default directories for the most popular static site generators are listed below:
    - Hugo: `public`
@@ -138,14 +138,14 @@ async function handleEvent(event) {
 6. Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone. Add a `route` property to the Wrangler file.
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "route": "https://example.com/*"
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "route": "https://example.com/*"
+      }
+      ```
+   
+      </WranglerConfig>
 
    :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
index 8dd326cda0b305d..4406df19ce0437c 100644
--- a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
@@ -55,39 +55,39 @@ The template project contains the following files and directories:
 - Change the `name` property to the name of your project:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "$schema": "./node_modules/wrangler/config-schema.json",
-    "name": "my-site"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "$schema": "./node_modules/wrangler/config-schema.json",
+      "name": "my-site"
+    }
+    ```
+  
+    </WranglerConfig>
 
 - Consider updating`compatibility_date` to today's date to get access to the most recent Workers features:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "compatibility_date": "yyyy-mm-dd"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "compatibility_date": "yyyy-mm-dd"
+    }
+    ```
+  
+    </WranglerConfig>
 
 - Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-    "route": "https://example.com/*"
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+      "route": "https://example.com/*"
+    }
+    ```
+  
+    </WranglerConfig>
 
   :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-worker.mdx b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
index 55e9d74a41f69f7..78314e60913a490 100644
--- a/src/content/docs/workers/configuration/sites/start-from-worker.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
@@ -24,16 +24,16 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st
 2. Add configuration to your Wrangler file to point to it.
 
    <WranglerConfig>
-
-   ```jsonc
-   {
-     "site": {
-       "bucket": "./public" // Add the directory with your static assets!
-     }
-   }
-   ```
-
-   </WranglerConfig>
+   
+      ```jsonc
+      {
+        "site": {
+          "bucket": "./public" // Add the directory with your static assets!
+        }
+      }
+      ```
+   
+      </WranglerConfig>
 
 3. Install the `@cloudflare/kv-asset-handler` package in your project:
 
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
index c32f452efe28734..c5f131c4787fd9c 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
@@ -6,6 +6,7 @@ description: Upload versions of Workers and create deployments to release new ve
 products:
   - workers
 ---
+
 import { DashButton } from "~/components";
 
 Versions track changes to your Worker. Deployments configure how those changes are deployed to your traffic.
@@ -107,4 +108,3 @@ Refer to [Migrate from Service Workers to ES modules](/workers/reference/migrate
 ### Durable Object migrations
 
 Uploading a version with [Durable Object migrations](/durable-objects/reference/durable-objects-migrations/) is not supported. Use [`wrangler deploy`](/workers/wrangler/commands/workers/#deploy) if you are applying a [Durable Object migration](/durable-objects/reference/durable-objects-migrations/).
-
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
index 6e0adad52574968..49bb0247b41f32f 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
@@ -65,9 +65,9 @@ If you forward the original request object, the override header carries through
 ```js
 // The override header from the inbound request is forwarded to the downstream Worker.
 export default {
-  async fetch(request, env) {
-    return env.MY_SERVICE.fetch(request);
-  },
+	async fetch(request, env) {
+		return env.MY_SERVICE.fetch(request);
+	},
 };
 ```
 
@@ -76,15 +76,15 @@ Alternatively, you can set an override header explicitly:
 ```js
 // Replace the version ID with the target version from `wrangler versions list`.
 export default {
-  async fetch(request, env) {
-    const response = await env.MY_SERVICE.fetch("https://example.com/", {
-      headers: {
-        "Cloudflare-Workers-Version-Overrides":
-          'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
-      },
-    });
-    return response;
-  },
+	async fetch(request, env) {
+		const response = await env.MY_SERVICE.fetch("https://example.com/", {
+			headers: {
+				"Cloudflare-Workers-Version-Overrides":
+					'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
+			},
+		});
+		return response;
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/configuration/workers-with-page-rules.mdx b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
index f165f162646c204..b50db0cc22a9f9c 100644
--- a/src/content/docs/workers/configuration/workers-with-page-rules.mdx
+++ b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
@@ -32,43 +32,39 @@ If you are experiencing Page Rule errors when running Workers, contact your Clou
 
 The following Page Rules may not work as expected when an incoming request is matched to a Worker route:
 
-* Always Online
-* [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
-* [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
-* [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
-* [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
-* [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
-* [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
-* Disable Apps
-* [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
-* [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
-* [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
-* [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
-* Host Header Override
-* [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
-* [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
-* [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
-* [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
-* [SSL](/workers/configuration/workers-with-page-rules/#ssl)
+- Always Online
+- [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
+- [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
+- [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
+- [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
+- [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
+- [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
+- Disable Apps
+- [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
+- [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
+- [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
+- [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
+- Host Header Override
+- [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
+- [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
+- [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
+- [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
+- [SSL](/workers/configuration/workers-with-page-rules/#ssl)
 
 This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.
 
 :::caution[Testing]
 
-
 Due to ongoing changes to the Workers runtime, detailed documentation on how these rules will be affected are updated following testing.
 
-
 :::
 
 To learn what these Page Rules do, refer to [Page Rules](/rules/page-rules/).
 
 :::note[Same zone versus other zone]
 
-
 A same zone subrequest is a request the Worker makes to an orange-clouded hostname in the same zone the Worker runs on. Depending on your DNS configuration, any request that falls outside that definition may be considered an other zone request by the Cloudflare network.
 
-
 :::
 
 ### Always Use HTTPS
@@ -137,11 +133,11 @@ A same zone subrequest is a request the Worker makes to an orange-clouded hostna
 
 ### Email Obfuscation
 
-| Source     | Target     | Behavior       |
-| -------------------------|------------|------------|
-| Client     | Worker     | Rule Ignored   |
-| Worker     | Same Zone  | Rule Respected |
-| Worker     | Other Zone | Rule Ignored   |
+| Source | Target     | Behavior       |
+| ------ | ---------- | -------------- |
+| Client | Worker     | Rule Ignored   |
+| Worker | Same Zone  | Rule Respected |
+| Worker | Other Zone | Rule Ignored   |
 
 ### Forwarding URL
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
index ddd98b108387e07..39d7ac436e98f44 100644
--- a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
@@ -12,9 +12,9 @@ import { Render, PackageManagers, Tabs, TabItem } from "~/components";
 
 :::note
 
-The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client. 
+The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client.
 
-If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/). 
+If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/).
 
 :::
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/turso.mdx b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
index 8467e1c8801cf6a..a144bb3ba616abd 100644
--- a/src/content/docs/workers/databases/third-party-integrations/turso.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
@@ -92,7 +92,7 @@ To set up an integration with Turso:
    ```sh
    # Get your database URL
    turso db show my-db --url
-   
+
    # Create an authentication token
    turso db tokens create my-db
    ```
@@ -103,8 +103,8 @@ To set up an integration with Turso:
    # Add the database URL as a secret
    npx wrangler secret put TURSO_URL
    # When prompted, paste your database URL
-   
-   # Add the authentication token as a secret  
+
+   # Add the authentication token as a secret
    npx wrangler secret put TURSO_AUTH_TOKEN
    # When prompted, paste your authentication token
    ```
diff --git a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
index ebdc513a162cfd2..e34c59345e8275b 100644
--- a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
@@ -17,7 +17,6 @@ To set up an integration with Upstash:
 1. You need an existing Upstash database to connect to. [Create an Upstash database](https://docs.upstash.com/redis#create-a-database) or [load data from an existing database to Upstash](https://docs.upstash.com/redis/howto/connectclient).
 
 2. Insert some data to your Upstash database. You can add data to your Upstash database in two ways:
-
    - Use the CLI directly from your Upstash console.
    - Alternatively, install [redis-cli](https://redis.io/docs/getting-started/installation/) locally and run the following commands.
 
@@ -53,7 +52,7 @@ To set up an integration with Upstash:
    # Add the Upstash Redis URL as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_URL
    # When prompted, paste your Upstash Redis REST URL
-   
+
    # Add the Upstash Redis token as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_TOKEN
    # When prompted, paste your Upstash Redis REST token
diff --git a/src/content/docs/workers/databases/third-party-integrations/xata.mdx b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
index 31cf393a9843646..a7bcec8e02894d4 100644
--- a/src/content/docs/workers/databases/third-party-integrations/xata.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
@@ -10,7 +10,6 @@ import { Render, TabItem, Tabs } from "~/components";
 
 [Xata](https://xata.io) is a PostgreSQL database platform designed to help developers operate and scale databases with enhanced productivity and performance. Xata provides features like instant copy-on-write database branches, zero-downtime schema changes, data anonymization, AI-powered performance monitoring, and BYOC.
 
-
 :::note
 
 You can connect to Xata using [Hyperdrive](/hyperdrive), which provides connection pooling and reduces the amount of round trips required to create a secure connection from Workers to your database.
diff --git a/src/content/docs/workers/development-testing/multi-workers.mdx b/src/content/docs/workers/development-testing/multi-workers.mdx
index 42e37c1197aff58..c90270083c2c91e 100644
--- a/src/content/docs/workers/development-testing/multi-workers.mdx
+++ b/src/content/docs/workers/development-testing/multi-workers.mdx
@@ -22,11 +22,11 @@ We recommend this approach as the default for most development workflows as it e
 You can run multiple Workers in a single dev command by passing multiple configuration files to your dev server:
 
 **Using Wrangler**
-   
+
 <PackageManagers
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
 />
 
 The first config (`./app/wrangler.jsonc`) is treated as the primary Worker, exposed at `http://localhost:8787`. Additional configs (e.g. `./api/wrangler.jsonc`) run as auxiliary Workers, available via service bindings or tail consumers from the primary Worker.
@@ -40,16 +40,16 @@ import { defineConfig } from "vite";
 import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
-  plugins: [
-    cloudflare({
-      configPath: "./app/wrangler.jsonc",
-      auxiliaryWorkers: [
-        {
-          configPath: "./api/wrangler.jsonc",
-        },
-      ],
-    }),
-  ],
+	plugins: [
+		cloudflare({
+			configPath: "./app/wrangler.jsonc",
+			auxiliaryWorkers: [
+				{
+					configPath: "./api/wrangler.jsonc",
+				},
+			],
+		}),
+	],
 });
 ```
 
@@ -68,17 +68,17 @@ Then run:
 You can also run each Worker in separate dev commands, each with its own terminal and configuration.
 
 <PackageManagers
-  comment="Terminal 1"
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./app/wrangler.jsonc"
+	comment="Terminal 1"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./app/wrangler.jsonc"
 />
 
 <PackageManagers
-  comment="Terminal 2"
-  type="exec"
-  pkg="wrangler"
-  args="dev -c ./api/wrangler.jsonc"
+	comment="Terminal 2"
+	type="exec"
+	pkg="wrangler"
+	args="dev -c ./api/wrangler.jsonc"
 />
 
 These Workers run in different dev commands but can still communicate with each other via service bindings or tail consumers **regardless of whether they are started with `wrangler dev` or `vite dev`**.
diff --git a/src/content/docs/workers/development-testing/testing.mdx b/src/content/docs/workers/development-testing/testing.mdx
index d085cb4f503f58c..c5a0a61aa1c1e8c 100644
--- a/src/content/docs/workers/development-testing/testing.mdx
+++ b/src/content/docs/workers/development-testing/testing.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 7
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/development-testing/vite-plugin.mdx b/src/content/docs/workers/development-testing/vite-plugin.mdx
index f11a1758026f45d..60632a1db291f01 100644
--- a/src/content/docs/workers/development-testing/vite-plugin.mdx
+++ b/src/content/docs/workers/development-testing/vite-plugin.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 1
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx
index 1a033e8825cce5d..e61fa08d45b3e14 100644
--- a/src/content/docs/workers/examples/103-early-hints.mdx
+++ b/src/content/docs/workers/examples/103-early-hints.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Allow a client to request static assets while waiting for the HTML response.
 tags:
   - Middleware
@@ -16,6 +15,7 @@ reviewed: 2022-08-12
 products:
   - workers
 ---
+
 import { DashButton, Steps, TabItem, Tabs } from "~/components";
 
 If you want to get started quickly, click on the button below.
diff --git a/src/content/docs/workers/examples/ab-testing.mdx b/src/content/docs/workers/examples/ab-testing.mdx
index 28b72e57b042734..bf57cc1256414cd 100644
--- a/src/content/docs/workers/examples/ab-testing.mdx
+++ b/src/content/docs/workers/examples/ab-testing.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set up an A/B test by controlling what response is served based on
   cookies. This version supports passing the request through to test and control
   on the origin, bypassing random assignment.
diff --git a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
index 3947c1f80350fb6..79830e09a3e34f0 100644
--- a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
+++ b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Access custom Cloudflare properties and control how Cloudflare features
   are applied to every request.
 tags:
diff --git a/src/content/docs/workers/examples/aggregate-requests.mdx b/src/content/docs/workers/examples/aggregate-requests.mdx
index 4666d5fd1baf002..05f04def29f8b17 100644
--- a/src/content/docs/workers/examples/aggregate-requests.mdx
+++ b/src/content/docs/workers/examples/aggregate-requests.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send two GET request to two urls and aggregates the responses into one
   response.
 tags:
diff --git a/src/content/docs/workers/examples/alter-headers.mdx b/src/content/docs/workers/examples/alter-headers.mdx
index cec4c62a5d08212..129e244ab485ac0 100644
--- a/src/content/docs/workers/examples/alter-headers.mdx
+++ b/src/content/docs/workers/examples/alter-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Example of how to add, change, or delete headers sent in a request or
   returned in a response.
 tags:
diff --git a/src/content/docs/workers/examples/auth-with-headers.mdx b/src/content/docs/workers/examples/auth-with-headers.mdx
index 4903f1f12598379..cf1ff87eee06ec7 100644
--- a/src/content/docs/workers/examples/auth-with-headers.mdx
+++ b/src/content/docs/workers/examples/auth-with-headers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Allow or deny a request based on a known pre-shared key in a header.
   This is not meant to replace the WebCrypto API.
 tags:
diff --git a/src/content/docs/workers/examples/basic-auth.mdx b/src/content/docs/workers/examples/basic-auth.mdx
index 84e8be086b49095..c4dbb71353b6c7f 100644
--- a/src/content/docs/workers/examples/basic-auth.mdx
+++ b/src/content/docs/workers/examples/basic-auth.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Shows how to restrict access using the HTTP Basic schema.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/block-on-tls.mdx b/src/content/docs/workers/examples/block-on-tls.mdx
index 43831741eb75193..c6edd048d5fafdc 100644
--- a/src/content/docs/workers/examples/block-on-tls.mdx
+++ b/src/content/docs/workers/examples/block-on-tls.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Inspects the incoming request's TLS version and blocks if under TLSv1.2.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/bulk-origin-proxy.mdx b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
index 6760d74eafdc8fb..943e7b6c4e8fea0 100644
--- a/src/content/docs/workers/examples/bulk-origin-proxy.mdx
+++ b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Resolve requests to your domain to a set of proxy third-party origin URLs.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/bulk-redirects.mdx b/src/content/docs/workers/examples/bulk-redirects.mdx
index 623d39afaf43402..f6c5d881a4b4ef6 100644
--- a/src/content/docs/workers/examples/bulk-redirects.mdx
+++ b/src/content/docs/workers/examples/bulk-redirects.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Redirect requests to certain URLs based on a mapped object to the
   request's URL.
 tags:
diff --git a/src/content/docs/workers/examples/cache-api.mdx b/src/content/docs/workers/examples/cache-api.mdx
index 3bb0c1b6578703f..34e592721b3174c 100644
--- a/src/content/docs/workers/examples/cache-api.mdx
+++ b/src/content/docs/workers/examples/cache-api.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the Cache API to store responses in Cloudflare's cache.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-post-request.mdx b/src/content/docs/workers/examples/cache-post-request.mdx
index 2fb05d6f62ead04..3c7f7548bf22aef 100644
--- a/src/content/docs/workers/examples/cache-post-request.mdx
+++ b/src/content/docs/workers/examples/cache-post-request.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Cache POST requests using the Cache API.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-tags.mdx b/src/content/docs/workers/examples/cache-tags.mdx
index 0a85395341521d5..248effca15f46bc 100644
--- a/src/content/docs/workers/examples/cache-tags.mdx
+++ b/src/content/docs/workers/examples/cache-tags.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send Additional Cache Tags using Workers
 tags:
   - Caching
diff --git a/src/content/docs/workers/examples/cache-using-fetch.mdx b/src/content/docs/workers/examples/cache-using-fetch.mdx
index 2270d27f236d16a..b3f9f1cd60b870c 100644
--- a/src/content/docs/workers/examples/cache-using-fetch.mdx
+++ b/src/content/docs/workers/examples/cache-using-fetch.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Determine how to cache a resource by setting TTLs, custom cache keys,
   and cache headers in a fetch request.
 tags:
@@ -564,6 +563,6 @@ When `no-cache` is supplied the cache is forced to revalidate the currently cach
 origin.
 
 ```js
-fetch(request, { cache: 'no-store'});
-fetch(request, { cache: 'no-cache'});
+fetch(request, { cache: "no-store" });
+fetch(request, { cache: "no-cache" });
 ```
diff --git a/src/content/docs/workers/examples/conditional-response.mdx b/src/content/docs/workers/examples/conditional-response.mdx
index f6b109c19de1a2f..0772d216c56f507 100644
--- a/src/content/docs/workers/examples/conditional-response.mdx
+++ b/src/content/docs/workers/examples/conditional-response.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Return a response based on the incoming request's URL, HTTP method,
   User Agent, IP address, ASN or device type.
 tags:
diff --git a/src/content/docs/workers/examples/cors-header-proxy.mdx b/src/content/docs/workers/examples/cors-header-proxy.mdx
index 8335f92850f2e62..c6eacdd133464f7 100644
--- a/src/content/docs/workers/examples/cors-header-proxy.mdx
+++ b/src/content/docs/workers/examples/cors-header-proxy.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Add the necessary CORS headers to a third party API response.
 tags:
   - Security
@@ -716,4 +715,3 @@ return response.json()
 }
 ```
 </TabItem> </Tabs>
-
diff --git a/src/content/docs/workers/examples/country-code-redirect.mdx b/src/content/docs/workers/examples/country-code-redirect.mdx
index ca3af654f791168..19a10589a4fb622 100644
--- a/src/content/docs/workers/examples/country-code-redirect.mdx
+++ b/src/content/docs/workers/examples/country-code-redirect.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Redirect a response based on the country code in the header of a visitor.
 tags:
   - Redirects
diff --git a/src/content/docs/workers/examples/data-loss-prevention.mdx b/src/content/docs/workers/examples/data-loss-prevention.mdx
index 8483ccab86121e9..ce5c655a6d71251 100644
--- a/src/content/docs/workers/examples/data-loss-prevention.mdx
+++ b/src/content/docs/workers/examples/data-loss-prevention.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Protect sensitive data to prevent data loss, and send alerts to a
   webhooks server in the event of a data breach.
 tags:
diff --git a/src/content/docs/workers/examples/debugging-logs.mdx b/src/content/docs/workers/examples/debugging-logs.mdx
index ac22a6f78f37918..33128a13520e036 100644
--- a/src/content/docs/workers/examples/debugging-logs.mdx
+++ b/src/content/docs/workers/examples/debugging-logs.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send debugging information in an errored response to a logging service.
 tags:
   - Debugging
diff --git a/src/content/docs/workers/examples/extract-cookie-value.mdx b/src/content/docs/workers/examples/extract-cookie-value.mdx
index 26eeba1adfb4182..2d1e1e7afa6b59d 100644
--- a/src/content/docs/workers/examples/extract-cookie-value.mdx
+++ b/src/content/docs/workers/examples/extract-cookie-value.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Given the cookie name, get the value of a cookie. You can also use
   cookies for A/B testing.
 tags:
diff --git a/src/content/docs/workers/examples/fetch-json.mdx b/src/content/docs/workers/examples/fetch-json.mdx
index e803fee74e049cb..ea574ed80ffa5a5 100644
--- a/src/content/docs/workers/examples/fetch-json.mdx
+++ b/src/content/docs/workers/examples/fetch-json.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send a GET request and read in JSON from the response. Use to fetch
   external data.
 pcx_content_type: example
diff --git a/src/content/docs/workers/examples/geolocation-app-weather.mdx b/src/content/docs/workers/examples/geolocation-app-weather.mdx
index da915f46349f806..903b1906ea7da65 100644
--- a/src/content/docs/workers/examples/geolocation-app-weather.mdx
+++ b/src/content/docs/workers/examples/geolocation-app-weather.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Fetch weather data from an API using the user's geolocation data.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-custom-styling.mdx b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
index 9e5888fbd2a51de..9010b98d7034c34 100644
--- a/src/content/docs/workers/examples/geolocation-custom-styling.mdx
+++ b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Personalize website styling based on localized user time.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-hello-world.mdx b/src/content/docs/workers/examples/geolocation-hello-world.mdx
index ca32cc280b07052..9e9f01f835ea0c3 100644
--- a/src/content/docs/workers/examples/geolocation-hello-world.mdx
+++ b/src/content/docs/workers/examples/geolocation-hello-world.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Get all geolocation data fields and display them in HTML.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/hot-link-protection.mdx b/src/content/docs/workers/examples/hot-link-protection.mdx
index 4a7d1a997e16191..b0773924fca66d4 100644
--- a/src/content/docs/workers/examples/hot-link-protection.mdx
+++ b/src/content/docs/workers/examples/hot-link-protection.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Block other websites from linking to your content. This is useful for
   protecting images.
 tags:
diff --git a/src/content/docs/workers/examples/modify-request-property.mdx b/src/content/docs/workers/examples/modify-request-property.mdx
index 7b0dff4cea7b789..fe5199d30781dab 100644
--- a/src/content/docs/workers/examples/modify-request-property.mdx
+++ b/src/content/docs/workers/examples/modify-request-property.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Create a modified request with edited properties based off of an
   incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/modify-response.mdx b/src/content/docs/workers/examples/modify-response.mdx
index 6638180c480b268..75b8731aae95371 100644
--- a/src/content/docs/workers/examples/modify-response.mdx
+++ b/src/content/docs/workers/examples/modify-response.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Fetch and modify response properties which are immutable by creating a
   copy first.
 tags:
diff --git a/src/content/docs/workers/examples/multiple-cron-triggers.mdx b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
index 52d717075365808..70ffa53d857fde0 100644
--- a/src/content/docs/workers/examples/multiple-cron-triggers.mdx
+++ b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Set multiple Cron Triggers on three different schedules.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/openai-sdk-streaming.mdx b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
index 20dc1d448fe2b7e..4a56649266440a9 100644
--- a/src/content/docs/workers/examples/openai-sdk-streaming.mdx
+++ b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the OpenAI v4 SDK to stream responses from OpenAI.
 tags:
   - AI
diff --git a/src/content/docs/workers/examples/post-json.mdx b/src/content/docs/workers/examples/post-json.mdx
index 6b01ab31537684d..c14f7e3a5c83c6a 100644
--- a/src/content/docs/workers/examples/post-json.mdx
+++ b/src/content/docs/workers/examples/post-json.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send a POST request with JSON data. Use to share data with external servers.
 tags:
   - JSON
diff --git a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
index c18930609c886b2..0204a2732ca6e07 100644
--- a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
+++ b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Protect against timing attacks by safely comparing values using
   `timingSafeEqual`.
 tags:
diff --git a/src/content/docs/workers/examples/read-post.mdx b/src/content/docs/workers/examples/read-post.mdx
index c805138d150cb88..6ec581eff46a60c 100644
--- a/src/content/docs/workers/examples/read-post.mdx
+++ b/src/content/docs/workers/examples/read-post.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Serve an HTML form, then read POST requests. Use also to read JSON or
   POST data from an incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/return-html.mdx b/src/content/docs/workers/examples/return-html.mdx
index 3cd587b30a97fae..065b623759cdcc6 100644
--- a/src/content/docs/workers/examples/return-html.mdx
+++ b/src/content/docs/workers/examples/return-html.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Deliver an HTML page from an HTML string directly inside the Worker script.
 demo: https://returning-html.workers-sites-examples.workers.dev
 tags:
diff --git a/src/content/docs/workers/examples/rewrite-links.mdx b/src/content/docs/workers/examples/rewrite-links.mdx
index cd10efbb5239087..e20265b28ed4a5b 100644
--- a/src/content/docs/workers/examples/rewrite-links.mdx
+++ b/src/content/docs/workers/examples/rewrite-links.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Rewrite URL links in HTML using the HTMLRewriter. This is useful for
   JAMstack websites.
 tags:
diff --git a/src/content/docs/workers/examples/signing-requests.mdx b/src/content/docs/workers/examples/signing-requests.mdx
index f1e685251d8fc52..7d98b2922d35a5f 100644
--- a/src/content/docs/workers/examples/signing-requests.mdx
+++ b/src/content/docs/workers/examples/signing-requests.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Verify a signed request using the HMAC and SHA-256 algorithms or return a 403.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
index d20ca8a4a5aa54b..6f97419c267b833 100644
--- a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
+++ b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Inject [Turnstile](/turnstile/) implicitly into HTML elements using the
   HTMLRewriter runtime API.
 tags:
diff --git a/src/content/docs/workers/examples/websockets.mdx b/src/content/docs/workers/examples/websockets.mdx
index cd919a2ecbdd2e4..84e5dc0f892523c 100644
--- a/src/content/docs/workers/examples/websockets.mdx
+++ b/src/content/docs/workers/examples/websockets.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Use the WebSockets API to communicate in real time with your Cloudflare Workers.
 tags:
   - WebSockets
@@ -82,8 +81,8 @@ async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<worker::Res
 ```
 
 </TabItem> </Tabs>
-After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
+After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
@@ -136,7 +135,6 @@ The `WebSocketPair` constructor returns an Object, with the `0` and `1` keys eac
 
 In order to begin communicating with the `client` WebSocket in your Worker, call `accept` on the `server` WebSocket. This will tell the Workers runtime that it should listen for WebSocket data and keep the connection open with your `client` WebSocket:
 
-
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
diff --git a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
index 8311463a2303071..bf7151b9c2d494c 100644
--- a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
+++ b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
@@ -10,13 +10,14 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers with AI & agent frameworks.
+	Create full-stack applications deployed to Cloudflare Workers with AI & agent
+	frameworks.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/ai-and-agents" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing
+	folder="workers/framework-guides/ai-and-agents"
+	maxDepth={2}
+/>
diff --git a/src/content/docs/workers/framework-guides/apis/index.mdx b/src/content/docs/workers/framework-guides/apis/index.mdx
index 7c65dfc89d5ab12..e3e0997d8023893 100644
--- a/src/content/docs/workers/framework-guides/apis/index.mdx
+++ b/src/content/docs/workers/framework-guides/apis/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers using APIs.
+	Create full-stack applications deployed to Cloudflare Workers using APIs.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/index.mdx b/src/content/docs/workers/framework-guides/index.mdx
index e7fd39e00a6aecf..7c7d795d9e3aa13 100644
--- a/src/content/docs/workers/framework-guides/index.mdx
+++ b/src/content/docs/workers/framework-guides/index.mdx
@@ -11,13 +11,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack applications deployed to Cloudflare Workers.
+	Create full-stack applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides" maxDepth={4}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides" maxDepth={4} />
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
index 03a98d1fc26641a..f7fc7a59d1511ee 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
@@ -5,4 +5,4 @@ pcx_content_type: navigation
 external_link: https://docs.expo.dev/eas/hosting/reference/worker-runtime/
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
index 6cc8183f77ec8c3..be6cede9f5c8287 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack mobile applications deployed to Cloudflare Workers.
+	Create full-stack mobile applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/web-apps/astro.mdx b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
index a1e4aaf3e9ea768..b90f2936598dcff 100644
--- a/src/content/docs/workers/framework-guides/web-apps/astro.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
@@ -87,11 +87,27 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Astro"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: "dist/_worker.js/index.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: ./dist, binding: ASSETS" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: "dist/_worker.js/index.js",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: ./dist, binding: ASSETS",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{ label: "adapter", file: "astro.config.mjs", value: "@astrojs/cloudflare" },
+		{
+			label: "adapter",
+			file: "astro.config.mjs",
+			value: "@astrojs/cloudflare",
+		},
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/index.mdx b/src/content/docs/workers/framework-guides/web-apps/index.mdx
index cb372caec51f847..87009d6003a290e 100644
--- a/src/content/docs/workers/framework-guides/web-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/index.mdx
@@ -10,13 +10,10 @@ products:
   - workers
 ---
 
-import {
-	Description,
-	DirectoryListing
-} from "~/components";
+import { Description, DirectoryListing } from "~/components";
 
 <Description>
-Create full-stack web applications deployed to Cloudflare Workers.
+	Create full-stack web applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2}/>
\ No newline at end of file
+<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2} />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
index db924f15079e094..0cd619c91b471d7 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
@@ -24,9 +24,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Analog"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
index 8dbf8a2eccef565..c12d9db29798dfc 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
@@ -29,7 +29,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Angular"
 	configs={[
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/browser" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/browser",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
index 6f0ab43afa2d870..b098122622c408a 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
@@ -75,7 +75,6 @@ Docusaurus is designed to be easy to use and customizable, making it a popular c
 
 If your Docusaurus project is entirely pre-rendered (which it usually is), follow these steps:
 
-
 <Steps>
 1.  **Add a Wrangler configuration file.**
 
@@ -116,4 +115,3 @@ If your Docusaurus project is entirely pre-rendered (which it usually is), follo
 Bindings are a way to connect your Docusaurus project to other Cloudflare services, enabling you to store and retrieve data within your application.
 
 <Render file="frameworks-bindings" product="workers" />
-
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
index 5b69a489c1fe3d0..8373da96cbbdb96 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
@@ -33,8 +33,6 @@ import {
 
 [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create/deploy-to-workers&repository=https://github.com/cloudflare/templates/tree/main/vite-react-template)
 
-
-
 ## What is Hono?
 
 [Hono](https://hono.dev/) is an ultra-fast, lightweight framework for building web applications, and works fantastically with Cloudflare Workers.
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
index eb6f1cd2cdff605..2c8eb7ea43bc8ed 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
@@ -8,4 +8,4 @@ sidebar:
     hideIndex: true
 products:
   - workers
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
index 775117671401c50..bf3f6b53620a121 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
@@ -29,9 +29,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Nuxt"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "preset", file: "nuxt.config.ts", value: "cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
index 520223f8048b1ce..0b4849166b7c4fc 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
@@ -33,9 +33,21 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Solid Start"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".output/server/index.mjs",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .output/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
index 11a06ef6dfe2634..6d8e6bedc97a74c 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
@@ -30,8 +30,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Waku"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/public" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/public",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -89,4 +97,4 @@ You can serve static assets in your Waku application by adding them to the `./pu
 
 During the build process, Waku copies `.js`, `.css`, `.html`, and `.txt` files from this directory into the final assets output. `.txt` files are used for storing data used by Server Components that are rendered at build time.
 
-<Render file="workers-assets-routing-summary" product="workers" />
\ No newline at end of file
+<Render file="workers-assets-routing-summary" product="workers" />
diff --git a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
index 7218158dad2f5ea..59f1211f42978e5 100644
--- a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
@@ -29,8 +29,6 @@ import {
 
 This is a simple getting started guide. For detailed documentation on how to use the Cloudflare OpenNext adapter, visit the [OpenNext website](https://opennext.js.org/cloudflare).
 
-
-
 ## What is Next.js?
 
 [Next.js](https://nextjs.org/) is a [React](https://react.dev/) framework for building full stack applications.
@@ -43,23 +41,23 @@ You can deploy your Next.js app to Cloudflare Workers using the OpenNext adapter
 
 Most Next.js features are supported by the Cloudflare OpenNext adapter:
 
-| Feature                               | Cloudflare adapter   | Notes                                                                        |
-| ------------------------------------- | -------------------- | ---------------------------------------------------------------------------- |
-| App Router                            | 🟢 supported         |                                                                              |
-| Pages Router                          | 🟢 supported         |                                                                              |
-| Route Handlers                        | 🟢 supported         |                                                                              |
-| React Server Components               | 🟢 supported         |                                                                              |
-| Static Site Generation (SSG)          | 🟢 supported         |                                                                              |
-| Server-Side Rendering (SSR)           | 🟢 supported         |                                                                              |
-| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                                              |
-| Server Actions                        | 🟢 supported         |                                                                              |
-| Response streaming                    | 🟢 supported         |                                                                              |
-| asynchronous work with `next/after`   | 🟢 supported         |                                                                              |
-| Middleware                            | 🟢 supported         |                                                                              |
-| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/) |
-| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                                               |
-| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js                                |
-| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported                  |
+| Feature                               | Cloudflare adapter   | Notes                                                       |
+| ------------------------------------- | -------------------- | ----------------------------------------------------------- |
+| App Router                            | 🟢 supported         |                                                             |
+| Pages Router                          | 🟢 supported         |                                                             |
+| Route Handlers                        | 🟢 supported         |                                                             |
+| React Server Components               | 🟢 supported         |                                                             |
+| Static Site Generation (SSG)          | 🟢 supported         |                                                             |
+| Server-Side Rendering (SSR)           | 🟢 supported         |                                                             |
+| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                             |
+| Server Actions                        | 🟢 supported         |                                                             |
+| Response streaming                    | 🟢 supported         |                                                             |
+| asynchronous work with `next/after`   | 🟢 supported         |                                                             |
+| Middleware                            | 🟢 supported         |                                                             |
+| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/)                 |
+| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                              |
+| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js               |
+| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported |
 
 ## Deploy a new Next.js project on Workers
 
@@ -133,8 +131,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Next.js"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: ".open-next/worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .open-next/assets" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .open-next/assets",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "adapter", file: "package.json", value: "@opennextjs/cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
index 226dd6d9fc4c19e..a69d19964c7156c 100644
--- a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
@@ -96,4 +96,4 @@ RedwoodSDK is a framework for building server-side web applications on Cloudflar
 
 	The first time you run the command it might fail and ask you to create a workers.dev subdomain. Go to the dashboard and open the Workers menu. Opening the Workers landing page for the first time will create a workers.dev subdomain automatically.
 
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
index 16233bdaac9a5ea..0c4e1f8d44d8645 100644
--- a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
@@ -31,11 +31,27 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="SvelteKit"
 	configs={[
-		{ label: "main", file: "wrangler.jsonc", value: ".svelte-kit/cloudflare/_worker.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: .svelte-kit/cloudflare" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "main",
+			file: "wrangler.jsonc",
+			value: ".svelte-kit/cloudflare/_worker.js",
+		},
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: .svelte-kit/cloudflare",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{ label: "adapter", file: "svelte.config.js", value: "@sveltejs/adapter-cloudflare" },
+		{
+			label: "adapter",
+			file: "svelte.config.js",
+			value: "@sveltejs/adapter-cloudflare",
+		},
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vike.mdx b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
index 27dd268608448ee..6218d56b5d4a81a 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vike.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
@@ -10,13 +10,12 @@ products:
 ---
 
 import { AutoconfigDiagram, Steps, PackageManagers } from "~/components";
-import { Tabs, TabItem } from '@astrojs/starlight/components';
+import { Tabs, TabItem } from "@astrojs/starlight/components";
 
 You can deploy your [Vike](https://vike.dev) app to Cloudflare using the Vike extension [`vike-photon`](https://vike.dev/vike-photon).
 
 All app types (SSR/SPA/SSG) are supported.
 
-
 :::tip[Already have a Vike project?]
 Run `wrangler deploy` in a project without a Wrangler configuration file and Wrangler will automatically detect Vike, generate the necessary configuration, and deploy your project.
 
@@ -29,8 +28,16 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Vike"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/server/index.js" },
-		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/client" },
-		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
+		{
+			label: "assets",
+			file: "wrangler.jsonc",
+			value: "directory: dist/client",
+		},
+		{
+			label: "compatibility_flags",
+			file: "wrangler.jsonc",
+			value: "nodejs_compat",
+		},
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -43,7 +50,6 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 
 Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `vike-photon` with `@photonjs/cloudflare`.
 
-
 ## Add to existing app
 
 <Steps>
@@ -92,31 +98,29 @@ Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `v
 To access Cloudflare APIs (such as [D1](/d1/) and [KV](/kv/)), use [bindings](/workers/runtime-apis/bindings/) which are available via the `env` object [imported from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global).
 
 ```ts
-import { env } from 'cloudflare:workers'
+import { env } from "cloudflare:workers";
 // Key-value store
-env.KV.get('my-key')
+env.KV.get("my-key");
 // Environment variable
-env.LOG_LEVEL
+env.LOG_LEVEL;
 // ...
 ```
 
 > Example of using Cloudflare D1:
+>
 > <PackageManagers
 > 	type="create"
 > 	pkg="vike@latest"
 > 	args="--react --hono --drizzle --cloudflare"
 > />
-> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an ORM.
+> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an
+> ORM.
 
 ## TypeScript
 
 If you use TypeScript, run [`wrangler types`](/workers/wrangler/commands/general/#types) whenever you change your Cloudflare configuration to update the `worker-configuration.d.ts` file.
 
-<PackageManagers
-	type="exec"
-	pkg="wrangler"
-	args="types"
-/>
+<PackageManagers type="exec" pkg="wrangler" args="types" />
 
 Then commit:
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vue.mdx b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
index e3f18d090e9e901..155e8df3c77be19 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vue.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
@@ -34,9 +34,9 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
 	args="my-vue-app --framework=vue"
 />
 
-    		 <Details header="How is this project set up?">
-        			Below is a simplified file tree of the project.
-        			<FileTree>
+		 <Details header="How is this project set up?">
+    			Below is a simplified file tree of the project.
+    			<FileTree>
     						- my-vue-app
     							- src/
     									- App.vue
@@ -47,17 +47,17 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
     							- wrangler.jsonc
         			</FileTree>
 
-        			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
-        			In this file:
-        					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
-        					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
-        					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
+    			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
+    			In this file:
+    					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
+    					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
+    					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-    						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
+						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-    						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
-    						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
-        		</Details>
+						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
+						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
+    		</Details>
 
 ## 2. Develop locally with the [Cloudflare Vite plugin](/workers/vite-plugin/)
 
diff --git a/src/content/docs/workers/get-started/dashboard.mdx b/src/content/docs/workers/get-started/dashboard.mdx
index 927871405d844f0..93f5ddc844d62d9 100644
--- a/src/content/docs/workers/get-started/dashboard.mdx
+++ b/src/content/docs/workers/get-started/dashboard.mdx
@@ -29,14 +29,15 @@ To get started with a new Workers application:
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
-3. Select **Create application**. From here, you can:
-    * Select from the gallery of production-ready templates
-    * Import an existing Git repository on your own account
-    * Let Cloudflare clone and bootstrap a public repository containing a Workers application.
+2. Select **Create application**. From here, you can:
+   - Select from the gallery of production-ready templates
+   - Import an existing Git repository on your own account
+   - Let Cloudflare clone and bootstrap a public repository containing a Workers application.
 3. Once you have connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and select **Deploy**.
 4. Cloudflare will kick off a new build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain.
 
 ## Continue development
+
 Applications started in the dashboard are set up with Git to help kickstart your development workflow. To continue developing on your repository, you can run:
 
 ```bash
@@ -60,8 +61,8 @@ git commit -m "your message"
 git push origin main
 ```
 
-
 To do more:
+
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.
diff --git a/src/content/docs/workers/get-started/quickstarts.mdx b/src/content/docs/workers/get-started/quickstarts.mdx
index c4c9aaa383a02c3..5b4c0d7dd74919f 100644
--- a/src/content/docs/workers/get-started/quickstarts.mdx
+++ b/src/content/docs/workers/get-started/quickstarts.mdx
@@ -1,5 +1,4 @@
 ---
-
 pcx_content_type: get-started
 title: Templates
 sidebar:
diff --git a/src/content/docs/workers/languages/javascript/index.mdx b/src/content/docs/workers/languages/javascript/index.mdx
index a2697d4edad3d26..ad25a7a59321ff9 100644
--- a/src/content/docs/workers/languages/javascript/index.mdx
+++ b/src/content/docs/workers/languages/javascript/index.mdx
@@ -8,16 +8,15 @@ products:
   - workers
 ---
 
-
 The Workers platform is designed to be [JavaScript standards compliant](https://ecma-international.org/publications-and-standards/standards/ecma-262/) and web-interoperable, and supports JavaScript standards, as defined by [TC39](https://tc39.es/) (ECMAScript). Wherever possible, it uses web platform APIs, so that code can be reused across client and server, as well as across [WinterCG](https://wintercg.org/) JavaScript runtimes.
 
 Refer to [Runtime APIs](/workers/runtime-apis/) for more information on specific JavaScript APIs available in Workers.
 
 ### Resources
 
-* [Getting Started](/workers/get-started/guide/)
-* [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
-* [TypeScript type definitions](https://github.com/cloudflare/workers-types)
-* [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
-* [Tutorials](/workers/tutorials/)
-* [Examples](/workers/examples/?languages=JavaScript)
+- [Getting Started](/workers/get-started/guide/)
+- [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
+- [TypeScript type definitions](https://github.com/cloudflare/workers-types)
+- [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
+- [Tutorials](/workers/tutorials/)
+- [Examples](/workers/examples/?languages=JavaScript)
diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx
index d45ef218a482019..57b1c75a4621975 100644
--- a/src/content/docs/workers/observability/errors.mdx
+++ b/src/content/docs/workers/observability/errors.mdx
@@ -15,22 +15,21 @@ Review Workers errors and exceptions.
 
 When a Worker running in production has an error that prevents it from returning a response, the client will receive an error page with an error code, defined as follows:
 
-| Error code | Meaning                                                                                                                                         |
-| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `1101`     | Worker threw a JavaScript exception.                                                                                                            |
-| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                           |
-| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                         |
-| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                           |
-| `1021`     | Worker has requested a host it cannot access.                                                                                                   |
-| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                       |
-| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                               |
-| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                       |
+| Error code | Meaning                                                                                                                                                                                                                                                             |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `1101`     | Worker threw a JavaScript exception.                                                                                                                                                                                                                                |
+| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                                                                                                                                               |
+| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                                                                                                                                             |
+| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                                                                                                                                               |
+| `1021`     | Worker has requested a host it cannot access.                                                                                                                                                                                                                       |
+| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                                                                                                                                           |
+| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                                                                                                                                                   |
+| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                                                                                                                                          |
 | `1042`     | Worker tried to fetch from another Worker on the same zone, which is only [supported](/workers/runtime-apis/fetch/) when the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) is used. |
-| `10162`    | Module has an unsupported Content-Type.                                                                                                         |
+| `10162`    | Module has an unsupported Content-Type.                                                                                                                                                                                                                             |
 
 Other `11xx` errors generally indicate a problem with the Workers runtime itself. Refer to the [status page](https://www.cloudflarestatus.com) if you are experiencing an error.
 
-
 ### Loop limit
 
 A Worker cannot call itself or another Worker more than 16 times. In order to prevent infinite loops between Workers, the [`CF-EW-Via`](/fundamentals/reference/http-headers/#cf-ew-via) header's value is an integer that indicates how many invocations are left. Every time a Worker is invoked, the integer will decrement by 1. If the count reaches zero, a [`1019`](#error-pages-generated-by-workers) error is returned.
@@ -191,23 +190,23 @@ If you need to share state across requests, consider using [Durable Objects](/du
 
 These errors occur when a Worker is uploaded or modified.
 
-| Error code | Meaning                                                                                                                         |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| `10006`    | Could not parse your Worker's code.                                                                                             |
-| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                       |
-| `10015`    | Account is not entitled to use Workers.                                                                                         |
-| `10016`    | Invalid Worker name.                                                                                                            |
-| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.             |
-| `10026`    | Could not parse request body.                                                                                                   |
-| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size). |
-| `10035`    | Multiple attempts to modify a resource at the same time                                                                         |
-| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                           |
-| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                        |
-| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                     |
-| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables).     |
-| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                           |
-| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                        |
-| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.              |
+| Error code | Meaning                                                                                                                     |
+| ---------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `10006`    | Could not parse your Worker's code.                                                                                         |
+| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                   |
+| `10015`    | Account is not entitled to use Workers.                                                                                     |
+| `10016`    | Invalid Worker name.                                                                                                        |
+| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.         |
+| `10026`    | Could not parse request body.                                                                                               |
+| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size).                               |
+| `10035`    | Multiple attempts to modify a resource at the same time                                                                     |
+| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                       |
+| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                    |
+| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                 |
+| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables). |
+| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                       |
+| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                    |
+| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.          |
 
 ### Validation Errors (10021)
 
@@ -236,6 +235,7 @@ Runtime errors will occur within the runtime, do not throw up an error page, and
 ## Identify errors: Workers Metrics
 
 To review whether your application is experiencing any downtime or returning any errors:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
index 586b51c9eed17af..105fea21b7e83dc 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
@@ -8,10 +8,11 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Axiom is a serverless log analytics platform that helps you store, search, and analyze massive amounts of data. By exporting your Cloudflare Workers application telemetry to Axiom, you can:
-- Store and query logs and traces at scale 
+
+- Store and query logs and traces at scale
 - Create dashboards and alerts to monitor your Workers
 
 ![Trace view with timing information displayed on a timeline](~/assets/images/workers-observability/axiom-example.png)
@@ -29,6 +30,7 @@ Before you begin, ensure you have:
 ## Step 1: Create a dataset
 
 If you don't already have a dataset to send data to:
+
 1. Log in to your [Axiom account](https://app.axiom.co/)
 2. Navigate to **Datasets** in the left sidebar
 3. Click **New Dataset**
@@ -56,6 +58,7 @@ Now you'll create destinations in the Cloudflare dashboard that point to Axiom.
 ### Axiom OTLP endpoints
 
 Axiom provides separate OTLP endpoints for traces and logs:
+
 - **Traces**: `https://api.axiom.co/v1/traces`
 - **Logs**: `https://api.axiom.co/v1/logs`
 
@@ -67,13 +70,13 @@ Axiom provides separate OTLP endpoints for traces and logs:
    - **Destination Name**: `axiom-traces` (or any descriptive name)
    - **Destination Type**: Select **Traces**
    - **OTLP Endpoint**: `https://api.axiom.co/v1/traces` (or `/v1/logs`)
-   - **Custom Headers**: Add two required headers: 
-     -  Authentication header 
-        - Header name: `Authorization`
-        - Header value: `Bearer <your-api-token>` 
-     - Dataset header: 
+   - **Custom Headers**: Add two required headers:
+     - Authentication header
+       - Header name: `Authorization`
+       - Header value: `Bearer <your-api-token>`
+     - Dataset header:
        - Header name: `X-Axiom-Dataset`
-       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`) 
+       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`)
 4. Click **Save**
 
 ## Step 3: Configure your Worker
@@ -104,6 +107,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Axiom. 
+It may take a few minutes after deployment for data to appear in Axiom.
 :::
-
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
index 8592f3ba188c813..996992e42bfb4d6 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
@@ -7,9 +7,11 @@ sidebar:
 products:
   - workers
 ---
-import {WranglerConfig} from "~/components";
+
+import { WranglerConfig } from "~/components";
 
 Grafana Cloud is a fully managed observability platform that provides visualization, alerting, and analytics for your telemetry data. By exporting your Cloudflare Workers telemetry to Grafana Cloud, you can:
+
 - Visualize distributed traces in **Grafana Tempo** to understand request flows and performance bottlenecks
 - Query and analyze logs in **Grafana Loki** alongside your traces
 
@@ -30,24 +32,25 @@ Before you begin, ensure you have:
 2. From your organization's home page, navigate to **Connections** → **Add new connection**
 3. Search for "OpenTelemetry" and select **OpenTelemetry (OTLP)**
 4. Select **Quickstart** then select **JavaScript**
-6. Click **Create a new token**
-7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
-8. Click on **Close** without copying the token
-9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
+5. Click **Create a new token**
+6. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
+7. Click on **Close** without copying the token
+8. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
 
+## Step 2: Set up destination
 
-## Step 2: Set up destination 
 1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
 2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
-3. From Grafana, copy your Otel endpoint, auth header, and auth value 
-  * Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs) 
-  * Your custom header should include: 
-      * Your auth header name `Authorization`
-      * Your auth header value `Basic MTMxxx...`
+3. From Grafana, copy your Otel endpoint, auth header, and auth value
+
+- Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs)
+- Your custom header should include:
+  - Your auth header name `Authorization`
+  - Your auth header value `Basic MTMxxx...`
 
 ## Step 3: Configure your Worker
 
-With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export. 
+With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
 
 <WranglerConfig>
 
@@ -70,8 +73,8 @@ With your destination created in the Cloudflare dashboard, update your Worker's
 
 </WranglerConfig>
 
-After updating your configuration, deploy your Worker for the changes to take effect. 
+After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Grafana Cloud. 
+It may take a few minutes after deployment for data to appear in Grafana Cloud.
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
index 847f103352c625f..9b00d57e583249b 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
@@ -8,9 +8,10 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Honeycomb is an observability platform built for high-cardinality data that helps you understand and debug your applications. By exporting your Cloudflare Workers application telemetry to Honeycomb, you can:
+
 - Visualize traces to understand request flows and identify performance bottlenecks
 - Query and analyze logs with unlimited dimensionality across any attribute
 - Create custom queries and dashboards to monitor your Workers
@@ -44,11 +45,12 @@ The API key will look something like: `hcaik_01hq...`
 
 ## Step 2: Configure Cloudflare destinations
 
-Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb. 
+Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb.
 
 ### Honeycomb OTLP endpoints
 
 Honeycomb provides separate OTLP endpoints for traces and logs:
+
 - **Traces**: `https://api.honeycomb.io/v1/traces`
 - **Logs**: `https://api.honeycomb.io/v1/logs`
 
@@ -107,5 +109,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Honeycomb. 
+It may take a few minutes after deployment for data to appear in Honeycomb.
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
index fd45dd3b86981fd..fbafabca9cdfc0f 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
@@ -25,18 +25,18 @@ You can export the following types of telemetry data:
 
 Below are common OTLP endpoint formats for popular observability providers. Refer to your provider's documentation for specific details and authentication requirements.
 
-| Provider                                                                                | Traces Endpoint                                              | Logs Endpoint                                                |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)         | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
-| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
-| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)              | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
-| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                 | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
-| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)               | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
-| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)             | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
-| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)              | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
-| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/) | `https://otlp.nr-data.net/v1/traces` | `https://otlp.nr-data.net/v1/logs` |
-| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp` | N/A |
-| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp) | `http://splunk.internal:4318/v1/traces` | `http://splunk.internal:4318/v1/logs` |
+| Provider                                                                                          | Traces Endpoint                                              | Logs Endpoint                                                |
+| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)                   | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
+| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/)           | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
+| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)                        | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
+| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                           | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
+| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)                         | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
+| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)                       | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
+| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)                        | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
+| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/)  | `https://otlp.nr-data.net/v1/traces`                         | `https://otlp.nr-data.net/v1/logs`                           |
+| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp`          | N/A                                                          |
+| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp)                          | `http://splunk.internal:4318/v1/traces`                      | `http://splunk.internal:4318/v1/logs`                        |
 
 :::note[Authentication]
 Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.
@@ -109,11 +109,11 @@ After creating a destination, you can monitor its health and delivery status in
 
 ### Status indicators
 
-| Status                  | Description                                                             | Troubleshooting                                                                                               |
-| ----------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                               |
+| Status                  | Description                                                             | Troubleshooting                                                                                                |
+| ----------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                                |
 | **Never run**           | No data has been delivered to this destination.                         | •Check if your Worker is receiving traffic <br /> • Review sampling rates (low rates generate less data)<br /> |
-| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                     |
+| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                      |
 
 ## Limits and pricing
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
index 0f42b67c6bb7168..69002849ba8e0f1 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 PostHog is a product analytics platform that helps you understand user behavior and debug issues. By exporting your Cloudflare Workers application telemetry to PostHog, you can:
 
@@ -41,10 +41,10 @@ The API key should look something like: `phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 PostHog has different endpoints depending on your data region:
 
-| Region | Logs Endpoint |
-| ------ | ------------- |
+| Region           | Logs Endpoint                        |
+| ---------------- | ------------------------------------ |
 | **US** (default) | `https://us.i.posthog.com/i/v1/logs` |
-| **EU** | `https://eu.i.posthog.com/i/v1/logs` |
+| **EU**           | `https://eu.i.posthog.com/i/v1/logs` |
 
 You can find your region in your PostHog project settings or by checking the URL when logged into PostHog (either `us.posthog.com` or `eu.posthog.com`).
 
@@ -104,6 +104,7 @@ Once your Worker is deployed and receiving traffic:
 3. Your Worker logs will appear with severity levels, timestamps, and attributes
 
 You can filter logs by:
+
 - **Severity level** (trace, debug, info, warn, error, fatal)
 - **Time range**
 - **Custom attributes** added to your log entries
@@ -115,25 +116,25 @@ You can add custom attributes to your logs using standard `console` methods with
 
 ```javascript
 export default {
-  async fetch(request, env) {
-    // Basic logging
-    console.log("Processing request");
-
-    // Logs with additional context
-    console.info("User action", {
-      userId: "user_123",
-      action: "api_call",
-      path: new URL(request.url).pathname
-    });
-
-    // Error logging with details
-    console.error("Request failed", {
-      error: "Connection timeout",
-      retryCount: 3
-    });
-
-    return new Response("OK");
-  }
+	async fetch(request, env) {
+		// Basic logging
+		console.log("Processing request");
+
+		// Logs with additional context
+		console.info("User action", {
+			userId: "user_123",
+			action: "api_call",
+			path: new URL(request.url).pathname,
+		});
+
+		// Error logging with details
+		console.error("Request failed", {
+			error: "Connection timeout",
+			retryCount: 3,
+		});
+
+		return new Response("OK");
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
index 57d0992698f5e67..1c602ea7225b551 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
@@ -8,9 +8,10 @@ products:
   - workers
 ---
 
-import {WranglerConfig} from "~/components";
+import { WranglerConfig } from "~/components";
 
 Sentry is a software monitoring tool that helps developers identify and debug performance issues and errors. From end-to-end distributed tracing to performance monitoring, Sentry provides code-level observability that makes it easy to diagnose issues and learn continuously about your application code health across systems and services. By exporting your Cloudflare Workers application telemetry to Sentry, you can:
+
 - Query logs and traces in Sentry
 - Create custom alerts and dashboards to monitor your Workers
 
@@ -37,6 +38,7 @@ If you don't already have a Sentry project to send data to, you'll need to creat
 ## Step 2: Get your Sentry OTLP endpoints
 
 Sentry provides separate OTLP endpoints for traces and logs which you can use to send your telemetry data to Sentry.
+
 - **Traces**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`
 - **Logs**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`
 
@@ -57,23 +59,24 @@ To set up a destination in the Cloudflare dashboard, navigate to your Cloudflare
 ### Traces Destination
 
 To configure your traces destination, click **Add destination** and configure the following:
-   - **Destination Name**: `sentry-traces` (or any descriptive name)
-   - **Destination Type**: Select **Traces**
-   - **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
-   - **Custom Headers**: Add the Sentry authentication header:
-     - Header name: `x-sentry-auth`
-     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
+
+- **Destination Name**: `sentry-traces` (or any descriptive name)
+- **Destination Type**: Select **Traces**
+- **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
+- **Custom Headers**: Add the Sentry authentication header:
+  - Header name: `x-sentry-auth`
+  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ### Logs destination
 
 To configure your logs destination, click **Add destination** and configure the following:
-   - **Destination Name**: `sentry-logs` (or any descriptive name)
-   - **Destination Type**: Select **Logs**
-   - **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
-   - **Custom Headers**: Add the Sentry authentication header:
-     - Header name: `x-sentry-auth`
-     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
+- **Destination Name**: `sentry-logs` (or any descriptive name)
+- **Destination Type**: Select **Logs**
+- **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
+- **Custom Headers**: Add the Sentry authentication header:
+  - Header name: `x-sentry-auth`
+  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ## Step 4: Configure your Worker
 
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 72b1c12297f3d02..2b21d8e285a2a6b 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -17,10 +17,8 @@ import { WranglerConfig, DashButton } from "~/components";
 
 :::caution
 
-
 Workers Trace Events Logpush is not available for zones on the [Cloudflare China Network](/china-network/).
 
-
 :::
 
 ## Verify your Logpush access
@@ -30,6 +28,7 @@ Minimum required Wrangler version: 2.2.0. Check your version by running `wrangle
 :::
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
+
 1. In the Cloudflare dashboard, go to the **Members** page.
 
    <DashButton url="/?to=/:account/members" />
@@ -43,6 +42,7 @@ Alternatively, create a new [API token](/fundamentals/api/get-started/create-tok
 ### Via the Cloudflare dashboard
 
 To create a Logpush job in the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Logpush** page.
 
    <DashButton url="/?to=/:account/logs" />
@@ -117,6 +117,7 @@ curl --request PUT \
 ### Dashboard
 
 To enable Logpush logging via the dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -147,30 +148,30 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-  "Exceptions": [
-    {
-      "Name": "SampleError",
-      "Message": "something went wrong",
-      "TimestampMs": 0
-    },
-    {
-      "Name": "AuthError",
-      "Message": "unable to process request authentication from client",
-      "TimestampMs": 1
-    },
-  ],
-  "Logs": [
-    {
-      "Level": "log",
-      "Message": ["Hello "],
-      "TimestampMs": 0
-    },
-    {
-      "Level": "log",
-      "Message": ["World!"],
-      "TimestampMs": 0
-    }
-  ]
+	"Exceptions": [
+		{
+			"Name": "SampleError",
+			"Message": "something went wrong",
+			"TimestampMs": 0
+		},
+		{
+			"Name": "AuthError",
+			"Message": "unable to process request authentication from client",
+			"TimestampMs": 1
+		}
+	],
+	"Logs": [
+		{
+			"Level": "log",
+			"Message": ["Hello "],
+			"TimestampMs": 0
+		},
+		{
+			"Level": "log",
+			"Message": ["World!"],
+			"TimestampMs": 0
+		}
+	]
 }
 ```
 
@@ -178,24 +179,24 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-  "Exceptions": [
-    {
-      "name": "SampleError",
-      "message": "something went wrong",
-      "TimestampMs": 0
-    },
-    {
-      "name": "AuthError",
-      "message": "unable to <<<Logpush: exception messages truncated>>>",
-      "TimestampMs": 1
-    },
-  ],
-  "Logs": [
-    {
-      "Level": "log",
-      "Message": ["<<<Logpush: messages truncated>>>"],
-      "TimestampMs": 0
-    }
-  ]
+	"Exceptions": [
+		{
+			"name": "SampleError",
+			"message": "something went wrong",
+			"TimestampMs": 0
+		},
+		{
+			"name": "AuthError",
+			"message": "unable to <<<Logpush: exception messages truncated>>>",
+			"TimestampMs": 1
+		}
+	],
+	"Logs": [
+		{
+			"Level": "log",
+			"Message": ["<<<Logpush: messages truncated>>>"],
+			"TimestampMs": 0
+		}
+	]
 }
 ```
diff --git a/src/content/docs/workers/observability/logs/real-time-logs.mdx b/src/content/docs/workers/observability/logs/real-time-logs.mdx
index 65b48530222963a..32ea43c6b2fedf7 100644
--- a/src/content/docs/workers/observability/logs/real-time-logs.mdx
+++ b/src/content/docs/workers/observability/logs/real-time-logs.mdx
@@ -25,6 +25,7 @@ Real-time logs are not available for zones on the [Cloudflare China Network](/ch
 ## View logs from the dashboard
 
 To view real-time logs associated with any deployed Worker using the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
index 1f162b257fc1d15..88e00843194056a 100644
--- a/src/content/docs/workers/observability/logs/workers-logs.mdx
+++ b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -53,7 +53,7 @@ You must add the observability setting for your Worker to write logs to Workers
 
 [Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for an environment named `staging`: 1. Add the following configuration below `[env.staging]`
 
-    <WranglerConfig>
+<WranglerConfig>
 
     ```jsonc
     {
@@ -70,8 +70,8 @@ You must add the observability setting for your Worker to write logs to Workers
 
     </WranglerConfig>
 
-    2. Deploy your Worker with `npx wrangler deploy -e staging`
-    3. Repeat step 1 and 2 for each environment.
+2. Deploy your Worker with `npx wrangler deploy -e staging`
+3. Repeat step 1 and 2 for each environment.
 
 ## View logs from the dashboard
 
diff --git a/src/content/docs/workers/observability/metrics-and-analytics.mdx b/src/content/docs/workers/observability/metrics-and-analytics.mdx
index ef28c321eb02f2a..3f270c3f47959fb 100644
--- a/src/content/docs/workers/observability/metrics-and-analytics.mdx
+++ b/src/content/docs/workers/observability/metrics-and-analytics.mdx
@@ -54,6 +54,7 @@ Subrequests are requests triggered by calling `fetch` from within a Worker. A su
 ### Wall time per execution
 
 <GlossaryTooltip term="wall-clock time">Wall time</GlossaryTooltip> represents
+
 the elapsed time in milliseconds between the start of a Worker invocation, and
 when the Workers runtime determines that no more JavaScript needs to run.
 Specifically, wall time per execution chart measures the wall time that the
diff --git a/src/content/docs/workers/observability/source-maps.mdx b/src/content/docs/workers/observability/source-maps.mdx
index 2872e097f8f75a0..20d213c75c986ae 100644
--- a/src/content/docs/workers/observability/source-maps.mdx
+++ b/src/content/docs/workers/observability/source-maps.mdx
@@ -45,10 +45,8 @@ You can then view the stack trace when streaming [real-time logs](/workers/obser
 
 :::note
 
-
 The source map is retrieved after your Worker invocation completes — it's an asynchronous process that does not impact your Worker's CPU utilization or performance. Source maps are not accessible inside the Worker at runtime, if you `console.log()` the [stack property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/stack) within a Worker, you will not get a deobfuscated stack trace.
 
-
 :::
 
 When Cloudflare attempts to remap a stack trace to the Worker's source map, it does so line-by-line, remapping as much as possible. If a line of the stack trace cannot be remapped for any reason, Cloudflare will leave that line of the stack trace unchanged, and continue to the next line of the stack trace.
@@ -59,10 +57,9 @@ When Cloudflare attempts to remap a stack trace to the Worker's source map, it d
 Minimum required Wrangler version for source maps: 3.46.0. Check your version by running `wrangler --version`.
 :::
 
-
-| Description                    | Limit         |
-| ------------------------------ | ------------- |
-| Maximum Source Map Size        | 15 MB gzipped |
+| Description             | Limit         |
+| ----------------------- | ------------- |
+| Maximum Source Map Size | 15 MB gzipped |
 
 ## Example
 
@@ -88,6 +85,6 @@ With **source maps uploaded**: all methods reference the correct files and line
 
 ## Related resources
 
-* [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
-* [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
-* [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
+- [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
+- [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
+- [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
diff --git a/src/content/docs/workers/platform/betas.mdx b/src/content/docs/workers/platform/betas.mdx
index 99cebde932f6ce9..e151ed5f512fd42 100644
--- a/src/content/docs/workers/platform/betas.mdx
+++ b/src/content/docs/workers/platform/betas.mdx
@@ -12,11 +12,11 @@ products:
 
 These are the current alphas and betas relevant to the Cloudflare Workers platform.
 
-* **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
-* Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
+- **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
+- Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
 
 | Product                                           | Private Beta | Public Beta | More Info                                                                   |
 | ------------------------------------------------- | ------------ | ----------- | --------------------------------------------------------------------------- |
-| Email Workers                                     |              | ✅           | [Docs](/email-routing/email-workers/)                                       |
-| Green Compute                                     |              | ✅           | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
-| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅           | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
+| Email Workers                                     |              | ✅          | [Docs](/email-routing/email-workers/)                                       |
+| Green Compute                                     |              | ✅          | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
+| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅          | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
diff --git a/src/content/docs/workers/platform/built-with-cloudflare.mdx b/src/content/docs/workers/platform/built-with-cloudflare.mdx
index b9ae5fb6977f6da..42aafcb95946784 100644
--- a/src/content/docs/workers/platform/built-with-cloudflare.mdx
+++ b/src/content/docs/workers/platform/built-with-cloudflare.mdx
@@ -45,4 +45,4 @@ The Built with Cloudflare button is an SVG and can be embedded anywhere. Use the
 https://workers.cloudflare.com/built-with-cloudflare.svg
 ```
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/docs/workers/platform/changelog/historical-changelog.mdx b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
index 0b2cbd209519aa6..6ecdf4d3609fbdb 100644
--- a/src/content/docs/workers/platform/changelog/historical-changelog.mdx
+++ b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
@@ -16,374 +16,374 @@ This page tracks changes made to Cloudflare Workers before 2023. For a view of m
 
 ## 2022-12-16
 
-* Conditional `PUT` requests have been fixed in the R2 bindings API.
+- Conditional `PUT` requests have been fixed in the R2 bindings API.
 
 ## 2022-12-02
 
-* Queues no longer support calling `send()` with an undefined JavaScript value as the message.
+- Queues no longer support calling `send()` with an undefined JavaScript value as the message.
 
 ## 2022-11-30
 
-* The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
-* Extended the R2 binding API to include support for multipart uploads.
+- The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
+- Extended the R2 binding API to include support for multipart uploads.
 
 ## 2022-11-17
 
-* V8 update: 10.6 → 10.8
+- V8 update: 10.6 → 10.8
 
 ## 2022-11-02
 
-* Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
+- Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
 
 ## 2022-10-21
 
-* The alarm retry limit will no longer apply to errors that are our fault.
-* Compatibility dates have been added for multiple flags including the new streams implementation.
-* `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
+- The alarm retry limit will no longer apply to errors that are our fault.
+- Compatibility dates have been added for multiple flags including the new streams implementation.
+- `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
 
 ## 2022-10-10
 
-* Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
-* `console.log` now prints more information about certain objects, for example Promises.
-* The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
+- Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
+- `console.log` now prints more information about certain objects, for example Promises.
+- The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
 
 ## 2022-09-16
 
-* R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
-* Allow deleting multiple keys at once in R2 bindings.
-* Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
-* User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
-* Updated V8 to 10.6.
+- R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
+- Allow deleting multiple keys at once in R2 bindings.
+- Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
+- User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
+- Updated V8 to 10.6.
 
 ## 2022-08-12
 
-* A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
-* When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
-* Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
-* Validation errors during Worker upload for module scripts now include correct line and column numbers.
-* Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
+- A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
+- When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
+- Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
+- Validation errors during Worker upload for module scripts now include correct line and column numbers.
+- Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
 
 ## 2022-07-08
 
-* Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
+- Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
 
 ## 2022-06-24
 
-* `wrangler dev` in global network preview mode now supports scheduling alarms.
-* R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
-* Some Web Cryptography API error messages include more information now.
-* Updated V8 from 10.2 to 10.3.
+- `wrangler dev` in global network preview mode now supports scheduling alarms.
+- R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
+- Some Web Cryptography API error messages include more information now.
+- Updated V8 from 10.2 to 10.3.
 
 ## 2022-06-18
 
-* Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
-* The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
+- Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
+- The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
 
 ## 2022-06-09
 
-* No externally-visible changes.
+- No externally-visible changes.
 
 ## 2022-06-03
 
-* It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
-* Preview in Quick Edit now correctly uses the correct R2 bindings.
-* Updated V8 from 10.1 to 10.2.
+- It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
+- Preview in Quick Edit now correctly uses the correct R2 bindings.
+- Updated V8 from 10.1 to 10.2.
 
 ## 2022-05-26
 
-* The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
-* R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
+- The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
+- R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
 
 ## 2022-05-19
 
-* R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
-* ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
-* Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
-* R2: Better runtime support for additional ranges.
-* R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
+- R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
+- ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
+- Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
+- R2: Better runtime support for additional ranges.
+- R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
 
 ## 2022-05-12
 
-* Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
-* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-* Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
-* R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
-* R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
-* Added `startAfter` option to the `list()` method in the Durable Object storage API.
+- Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
+- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+- Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+- R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
+- R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
+- Added `startAfter` option to the `list()` method in the Durable Object storage API.
 
 ## 2022-05-05
 
-* `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
-* Fix generated types for Date.
-* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-* Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+- `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
+- Fix generated types for Date.
+- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+- Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
 
 ## 2022-04-29
 
-* Minor V8 update: 10.0 → 10.1.
-* R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
+- Minor V8 update: 10.0 → 10.1.
+- R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
 
 ## 2022-04-22
 
-* Major V8 update: 9.9 → 10.0.
+- Major V8 update: 9.9 → 10.0.
 
 ## 2022-04-14
 
-* Performance and stability improvements.
+- Performance and stability improvements.
 
 ## 2022-04-08
 
-* The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
-* R2 error responses now include better details.
+- The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
+- R2 error responses now include better details.
 
 ## 2022-03-24
 
-* A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
-* When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
-* The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
+- A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
+- When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
+- The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
 
 ## 2022-03-17
 
-* The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
-* When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
-* Fix R2 publish date rendering.
-* Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
-* When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
+- The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
+- When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
+- Fix R2 publish date rendering.
+- Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
+- When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
 
 ## 2022-03-11
 
-* Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
-* Implementations of `CompressionStream` and `DecompressionStream` are now available.
+- Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
+- Implementations of `CompressionStream` and `DecompressionStream` are now available.
 
 ## 2022-03-04
 
-* Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
-* With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
-* A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
-* The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
-* An implementation of `URLPattern` is now available.
+- Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
+- With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
+- A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
+- The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
+- An implementation of `URLPattern` is now available.
 
 ## 2022-02-25
 
-* The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
-* Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
-* Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
+- The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
+- Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
+- Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
 
 ## 2022-02-18
 
-* `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
+- `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
 
 ## 2022-02-11
 
-* WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
+- WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
 
 ## 2022-02-05
 
-* Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
-* `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
-* A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
+- Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
+- `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
+- A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
 
 ## 2022-01-28
 
-* No user-visible changes.
+- No user-visible changes.
 
 ## 2022-01-20
 
-* Updated V8: 9.7 → 9.8.
+- Updated V8: 9.7 → 9.8.
 
 ## 2022-01-17
 
-* `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
-* Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
+- `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
+- Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
 
 ## 2022-01-07
 
-* The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
+- The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
 
 ## 2021-12-22
 
-* Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
+- Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
 
 ## 2021-12-10
 
-* Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
-* `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
-* Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
-* `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
-* Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
-* Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
+- Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
+- `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
+- Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
+- `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
+- Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
+- Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
 
 ## 2021-12-02
 
-* The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
-* Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
+- The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
+- Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
 
 ## 2021-11-19
 
-* Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
-* Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
-* [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
+- Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
+- Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
+- [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
 
 ## 2021-11-12
 
-* The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
-* Unhandled rejection warnings will be printed to the inspector console.
+- The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
+- Unhandled rejection warnings will be printed to the inspector console.
 
 ## 2021-11-05
 
-* Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
-* Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams\_byob\_reader\_detaches\_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
+- Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
+- Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams_byob_reader_detaches_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
 
 ## 2021-10-21
 
-* Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
-* The `unhandledrejection` and `rejectionhandled` events are now supported.
-* The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
-* Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
-* The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
+- Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
+- The `unhandledrejection` and `rejectionhandled` events are now supported.
+- The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
+- Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
+- The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
 
 ## 2021-10-14
 
-* `request.signal` will always return an `AbortSignal`.
-* Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
-* Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
+- `request.signal` will always return an `AbortSignal`.
+- Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
+- Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
 
 ## 2021-09-24
 
-* The `AbortController` and `AbortSignal` objects are now available.
-* The Web Platform `queueMicrotask` API is now available.
-* It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
-* The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
-* Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
-* The `Event` object now supports most standard methods and properties.
-* V8 updated from 9.3 to 9.4.
+- The `AbortController` and `AbortSignal` objects are now available.
+- The Web Platform `queueMicrotask` API is now available.
+- It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
+- The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
+- Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
+- The `Event` object now supports most standard methods and properties.
+- V8 updated from 9.3 to 9.4.
 
 ## 2021-09-03
 
-* The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
-* Durable Objects are now scheduled more evenly around a colocation (colo).
+- The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
+- Durable Objects are now scheduled more evenly around a colocation (colo).
 
 ## 2021-08-05
 
-* No user-facing changes. Just bug fixes & internal maintenance.
+- No user-facing changes. Just bug fixes & internal maintenance.
 
 ## 2021-07-30
 
-* Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
-* Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
+- Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
+- Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
 
 ## 2021-07-23
 
-* Performance and stability improvements.
+- Performance and stability improvements.
 
 ## 2021-07-16
 
-* Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
-* Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
-* Durable Object constructors may now initiate I/O, such as `fetch()` calls.
-* Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
-* In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
+- Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
+- Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
+- Durable Object constructors may now initiate I/O, such as `fetch()` calls.
+- Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
+- In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
 
 ## 2021-07-13
 
-* The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
+- The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
 
 ## 2021-07-01
 
-* Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
-* Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
+- Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
+- Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
 
 ## 2021-06-27
 
-* WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
+- WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
 
 ## 2021-06-17
 
 Changes this week:
 
-* Updated V8 from 9.1 to 9.2.
-* `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
+- Updated V8 from 9.1 to 9.2.
+- `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
 
 ## 2021-06-11
 
 Changes this week:
 
-* Turn on V8 Sparkplug compiler.
-* Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
+- Turn on V8 Sparkplug compiler.
+- Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
 
 ## 2021-06-04
 
 Changes this week:
 
-* WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
-* `request.cf` is no longer missing when writing Workers using modules syntax.
+- WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
+- `request.cf` is no longer missing when writing Workers using modules syntax.
 
 ## 2021-05-14
 
 Changes this week:
 
-* Improve error messages coming from the WebCrypto API.
-* Updated V8: 9.0 → 9.1
+- Improve error messages coming from the WebCrypto API.
+- Updated V8: 9.0 → 9.1
 
 Changes in an earlier release:
 
-* WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
-* WebCrypto: Add support for RSA-OAEP
-* WebCrypto: HKDF implemented.
-* Fix recently-introduced backwards clock jumps in Durable Objects.
-* `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1\_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
+- WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
+- WebCrypto: Add support for RSA-OAEP
+- WebCrypto: HKDF implemented.
+- Fix recently-introduced backwards clock jumps in Durable Objects.
+- `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
 
 ## 2021-04-29
 
 Changes this week:
 
-* WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
-* The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
+- WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
+- The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
 
 ## 2021-04-23
 
 Changes this week:
 
-* In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
-* For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
-* When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
-* Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
-* When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
-* When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-* When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-* `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
+- In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
+- For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
+- When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
+- Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
+- When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
+- When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+- When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+- `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
 
 ## 2021-04-19
 
 Changes since the last post on 3/26:
 
-* Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
-* Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
-* Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
-* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-* Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
-* WebCrypto: Key derivation for ECDH.
-* WebCrypto: Support ECDH key generation & import.
-* WebCrypto: Support ECDSA key generation.
-* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-* Improved exception messages thrown by the WebCrypto API somewhat.
-* `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
-* `passThroughOnException` is now available under the ctx argument to module handlers
-* Reliability improvements for Durable Objects
-* Reliability improvements for Durable Objects persistent storage API
-* `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
+- Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
+- Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
+- Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
+- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+- Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
+- WebCrypto: Key derivation for ECDH.
+- WebCrypto: Support ECDH key generation & import.
+- WebCrypto: Support ECDSA key generation.
+- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+- Improved exception messages thrown by the WebCrypto API somewhat.
+- `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
+- `passThroughOnException` is now available under the ctx argument to module handlers
+- Reliability improvements for Durable Objects
+- Reliability improvements for Durable Objects persistent storage API
+- `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
 
 ## 2021-03-26
 
 Changes this week:
 
-* Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
+- Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
 
 ## 2021-03-11
 
 New this week:
 
-* When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
+- When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
 
 (It looks like no release notes were posted the last few weeks, but there were no new user-visible changes to report.)
 
@@ -391,56 +391,56 @@ New this week:
 
 Changes this week:
 
-* In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
-* A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
+- In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
+- A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
 
 ## 2021-02-05
 
 New this week:
 
-* V8 has been updated from 8.8 to 8.9.
-* During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
+- V8 has been updated from 8.8 to 8.9.
+- During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
 
 New last week (forgot to post):
 
-* Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
+- Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
 
 ## 2021-01-22
 
 New in the past week:
 
-* Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
+- Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
 
 ## 2021-01-14
 
 Changes this week:
 
-* Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
+- Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
 
 ## 2021-01-07
 
 Changes this week:
 
-* No user-visible changes.
+- No user-visible changes.
 
 Changes in the prior release:
 
-* Fixed delivery of WebSocket “error” events.
-* Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
+- Fixed delivery of WebSocket “error” events.
+- Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
 
 ## 2020-12-10
 
 Changes this week:
 
-* Major V8 update: 8.7.220.29 -> 8.8.278.8
+- Major V8 update: 8.7.220.29 -> 8.8.278.8
 
 ## 2019-09-19
 
 Changes this week:
 
-* Unannounced new feature. (Stay tuned.)
-* Enforced new limit on concurrent subrequests (see below).
-* Stability improvements.
+- Unannounced new feature. (Stay tuned.)
+- Enforced new limit on concurrent subrequests (see below).
+- Stability improvements.
 
 **Concurrent Subrequest Limit**
 
@@ -472,129 +472,129 @@ We chose the limit of 6 concurrent connections based on the fact that Chrome enf
 
 Changes this week:
 
-* Durable Objects storage API now supports listing keys by prefix.
-* Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
-* `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
-* Fixed off-by-one line numbers in Worker exceptions.
-* Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
-* Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
+- Durable Objects storage API now supports listing keys by prefix.
+- Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
+- `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
+- Fixed off-by-one line numbers in Worker exceptions.
+- Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
+- Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
 
 ## 2020-11-13
 
 Changes over the past week:
 
-* `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
-* Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
+- `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
+- Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
 
 ## 2020-11-05
 
 Changes this week:
 
-* Major V8 update: 8.6 -> 8.7
-* Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
+- Major V8 update: 8.6 -> 8.7
+- Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
 
 ## 2020-10-05
 
 We had our usual weekly release last week, but:
 
-* No user-visible changes.
+- No user-visible changes.
 
 ## 2020-09-24
 
 Changes this week:
 
-* Internal changes to support upcoming features.
+- Internal changes to support upcoming features.
 
 Also, a change from the 2020-09-08 release that it seems we forgot to post:
 
-* V8 major update: 8.5 -> 8.6
+- V8 major update: 8.5 -> 8.6
 
 ## 2020-08-03
 
 Changes last week:
 
-* Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
-* Upgraded V8 from 8.4 to 8.5.
+- Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
+- Upgraded V8 from 8.4 to 8.5.
 
 ## 2020-07-09
 
 Changes this week:
 
-* Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
-* Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
+- Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
+- Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
 
 Changes last week (… forgot to post):
 
-* `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
+- `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
 
 Changes the week before last (… also… forgot to post… we really need to code up a bot for this):
 
-* The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
+- The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
 
 ## 2020-05-15
 
 Changes this week:
 
-* Implemented API for yet-to-be-announced new feature.
+- Implemented API for yet-to-be-announced new feature.
 
 ## 2020-04-20
 
 Looks like we forgot to post release notes for a couple weeks. Releases still are happening weekly as always, but the “post to the community” step is insufficiently automated…
 4/2 release:
 
-* Fixed a source of long garbage collection paused in memory limit enforcement.
+- Fixed a source of long garbage collection paused in memory limit enforcement.
 
 4/9 release:
 
-* No publicly-visible changes.
+- No publicly-visible changes.
 
 4/16 release:
 
-* In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
+- In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
 
 ## 2020-03-26
 
 New this week:
 
-* Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
+- Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
 
 ## 2020-02-28
 
 New from the past two weeks:
 
-* Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
-* Major V8 update: 8.0 -> 8.1
-* Minor bug fixes.
+- Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
+- Major V8 update: 8.0 -> 8.1
+- Minor bug fixes.
 
 ## 2020-02-13
 
 Changes over the last couple weeks:
 
-* Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
-* Performance and stability improvements.
+- Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
+- Performance and stability improvements.
 
 ## 2020-01-24
 
 It has been a while since we posted release notes, partly due to the holidays. Here is what is new over the past month:
 
-* Performance and stability improvements.
-* A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
-* Updated V8 7.9 -> 8.0.
+- Performance and stability improvements.
+- A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
+- Updated V8 7.9 -> 8.0.
 
 ## 2019-12-12
 
 New this week:
 
-* We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
-* Fixed a significant source of daemonDown (1105) errors.
+- We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
+- Fixed a significant source of daemonDown (1105) errors.
 
 ## 2019-12-06
 
 Runtime release notes covering the past few weeks:
 
-* Increased total per-request `Cache.put()` limit to 5GiB.
-* Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
-* Added a helpful error message explaining AES decryption failures.
-* Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
-* More “internal errors” were converted to useful user-facing errors.
-* Stability improvements and bug fixes.
+- Increased total per-request `Cache.put()` limit to 5GiB.
+- Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
+- Added a helpful error message explaining AES decryption failures.
+- Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
+- More “internal errors” were converted to useful user-facing errors.
+- Stability improvements and bug fixes.
diff --git a/src/content/docs/workers/platform/changelog/index.mdx b/src/content/docs/workers/platform/changelog/index.mdx
index c4945fcbdae6f6c..dd80529874c454a 100644
--- a/src/content/docs/workers/platform/changelog/index.mdx
+++ b/src/content/docs/workers/platform/changelog/index.mdx
@@ -17,7 +17,7 @@ import { ProductReleaseNotes } from "~/components";
 
 This changelog details meaningful changes made to Workers across the Cloudflare dashboard, Wrangler, the API, and the workerd runtime. These changes are not configurable.
 
-This is *different* from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
+This is _different_ from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
 
 {/* <!-- Actual content lives in /src/content/release-notes/workers.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx
index 7e4e69499728faa..38a84a62e234adb 100644
--- a/src/content/docs/workers/platform/known-issues.mdx
+++ b/src/content/docs/workers/platform/known-issues.mdx
@@ -14,7 +14,7 @@ Below are some known bugs and issues to be aware of when using Cloudflare Worker
 
 ## Route specificity
 
-* When defining route specificity, a trailing `/*` in your pattern may not act as expected.
+- When defining route specificity, a trailing `/*` in your pattern may not act as expected.
 
 Consider two different Workers, each deployed to the same zone. Worker A is assigned the `example.com/images/*` route and Worker B is given the `example.com/images*` route pattern. With these in place, here are how the following URLs will be resolved:
 
@@ -44,11 +44,11 @@ When adding a wildcard on a subdomain, here are how the following URLs will be r
 
 ## wrangler dev
 
-* When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
+- When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
 
 ```js
 const request = new Request(url, incomingRequest);
-request.headers.delete('cf-workers-preview-token');
+request.headers.delete("cf-workers-preview-token");
 return await fetch(request);
 ```
 
@@ -90,11 +90,11 @@ For Workers subrequests, requests can only be made to URLs, not to IP addresses
 For example, in the zone `example.com` create a record of type `A` with the name `server` and value `192.0.2.1`, and then use:
 
 ```js
-await fetch('http://server.example.com')
+await fetch("http://server.example.com");
 ```
 
 Do not use:
 
 ```js
-await fetch('http://192.0.2.1')
+await fetch("http://192.0.2.1");
 ```
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
index d306aaec2558390..929570df6454101 100644
--- a/src/content/docs/workers/platform/pricing.mdx
+++ b/src/content/docs/workers/platform/pricing.mdx
@@ -27,9 +27,9 @@ All [Pages Functions](/pages/functions/) are billed as Workers. All pricing and
 
 Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, contact your Account Manager.
 
-|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                |
+|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                      |
 | **Standard** | 10 million included per month <br /> +$0.30 per additional million | No charge or limit for duration | 30 million CPU milliseconds included per month<br /> +$0.02 per additional million CPU milliseconds<br /><br/> Max of [5 minutes of CPU time](/workers/platform/limits/#account-plan-limits) per invocation (default: 30 seconds)<br /> Max of 15 minutes of CPU time per [Cron Trigger](/workers/configuration/cron-triggers/) or [Queue Consumer](/queues/configuration/javascript-apis/#consumer) invocation |
 
 <sup>1</sup> Inbound requests to your Worker. Cloudflare does not bill for
diff --git a/src/content/docs/workers/reference/how-the-cache-works.mdx b/src/content/docs/workers/reference/how-the-cache-works.mdx
index 53aad4dd28b3f81..fb3c5d8662710f6 100644
--- a/src/content/docs/workers/reference/how-the-cache-works.mdx
+++ b/src/content/docs/workers/reference/how-the-cache-works.mdx
@@ -17,11 +17,9 @@ Cloudflare Workers run before the cache but can also be utilized to modify asset
 Conceptually, there are two ways to interact with Cloudflare’s Cache using a Worker:
 
 - Call to [`fetch()`](/workers/runtime-apis/fetch/) in a Workers script. Requests proxied through Cloudflare are cached even without Workers according to a zone’s default or configured behavior (for example, static assets like files ending in `.jpg` are cached by default). Workers can further customize this behavior by:
-
   - Setting Cloudflare cache rules (that is, operating on the `cf` object of a [request](/workers/runtime-apis/request/)).
 
 - Store responses using the [Cache API](/workers/runtime-apis/cache/) from a Workers script. This allows caching responses that did not come from an origin and also provides finer control by:
-
   - Customizing cache behavior of any asset by setting headers such as `Cache-Control` on the response passed to `cache.put()`.
 
   - Caching responses generated by the Worker itself through `cache.put()`.
@@ -62,11 +60,9 @@ A("You have a Worker script that runs on <code>https://</code><code>example.com/
 Assets stored in the cache through [Cache API](/workers/runtime-apis/cache/) operations can be purged in a couple of ways:
 
 - Call `cache.delete` within a Worker to invalidate the cache for the asset with a matching request variable.
-
   - Assets purged in this way are only purged locally to the data center the Worker runtime was executed.
 
 - To purge an asset globally, use the standard [cache purge options](/cache/how-to/purge-cache/). Based on cache API implementation, not all cache purge endpoints function for purging assets stored by the Cache API.
-
   - All assets on a zone can be purged by using the [Purge Everything](/cache/how-to/purge-cache/purge-everything/) cache operation. This purge will remove all assets associated with a Cloudflare zone from cache in all data centers regardless of the method set.
 
   - [Cache Tags](/cache/how-to/purge-cache/purge-by-tags/#add-cache-tag-http-response-headers) can be added to requests dynamically in a Worker by calling `response.headers.append()` and appending `Cache-Tag` values dynamically to that request. Once set, those tags can be used to selectively purge assets from cache without invalidating all cached assets on a zone.
diff --git a/src/content/docs/workers/reference/how-workers-works.mdx b/src/content/docs/workers/reference/how-workers-works.mdx
index 4a44795d4bf2054..8d93ed5dfa09491 100644
--- a/src/content/docs/workers/reference/how-workers-works.mdx
+++ b/src/content/docs/workers/reference/how-workers-works.mdx
@@ -9,7 +9,7 @@ products:
   - workers
 ---
 
-import { Render, WorkersIsolateDiagram } from "~/components"
+import { Render, WorkersIsolateDiagram } from "~/components";
 
 Though Cloudflare Workers behave similarly to [JavaScript](https://www.cloudflare.com/learning/serverless/serverless-javascript/) in the browser or in Node.js, there are a few differences in how you have to think about your code. Under the hood, the Workers runtime uses the [V8 engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/) — the same engine used by Chromium and Node.js. The Workers runtime also implements many of the standard [APIs](/workers/runtime-apis/) available in most modern browsers.
 
@@ -27,13 +27,13 @@ The three largest differences are: Isolates, Compute per Request, and Distribute
 
 <Render file="isolate-description" product="workers" />
 
-<WorkersIsolateDiagram/>
+<WorkersIsolateDiagram />
 
 A given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons:
 
-* Resource limitations on the machine.
-* A suspicious script - anything seen as trying to break out of the isolate sandbox.
-* Individual [resource limits](/workers/platform/limits/).
+- Resource limitations on the machine.
+- A suspicious script - anything seen as trying to break out of the isolate sandbox.
+- Individual [resource limits](/workers/platform/limits/).
 
 Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingency.
 
@@ -52,6 +52,6 @@ Because there is no guarantee that any two user requests will be routed to the s
 
 ## Related resources
 
-* [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
-* [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
-* [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
+- [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
+- [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
+- [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
diff --git a/src/content/docs/workers/reference/protocols.mdx b/src/content/docs/workers/reference/protocols.mdx
index fe7f15baf21e464..bd089af6329ec22 100644
--- a/src/content/docs/workers/reference/protocols.mdx
+++ b/src/content/docs/workers/reference/protocols.mdx
@@ -10,10 +10,10 @@ products:
 
 Cloudflare Workers support the following protocols and interfaces:
 
-| Protocol               | Inbound                                                                                                                                                                                                                                                                                                          | Outbound                                                                                                     |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                               | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                                |
-| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
-| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                           |                                     |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
-| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |
+| Protocol               | Inbound                                                                                                                                                                                                                                                                                                         | Outbound                                                                                        |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                              | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                   |
+| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                            | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/) |
+| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                                                                                                            |                                                                                                 |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                 |
+| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                 | [Email Workers](/email-routing/email-workers/)                                                  |
diff --git a/src/content/docs/workers/reference/security-model.mdx b/src/content/docs/workers/reference/security-model.mdx
index f45407e36b6b093..d79f5a740d88d0d 100644
--- a/src/content/docs/workers/reference/security-model.mdx
+++ b/src/content/docs/workers/reference/security-model.mdx
@@ -7,7 +7,7 @@ products:
   - workers
 ---
 
-import { WorkersArchitectureDiagram } from "~/components"
+import { WorkersArchitectureDiagram } from "~/components";
 
 This article includes an overview of Cloudflare security architecture, and then addresses two frequently asked about issues: V8 bugs and Spectre.
 
@@ -25,7 +25,7 @@ For more details, refer to [this talk](https://www.infoq.com/presentations/cloud
 
 Beginning with a quick overview of the Workers runtime architecture:
 
-<WorkersArchitectureDiagram/>
+<WorkersArchitectureDiagram />
 
 There are two fundamental parts of designing a code sandbox: secure isolation and API design.
 
@@ -172,7 +172,7 @@ In Workers, you can get the current time using the JavaScript Date API by callin
 ```js
 let start = Date.now();
 for (let i = 0; i < 1e6; i++) {
-  doSpectreAttack();
+	doSpectreAttack();
 }
 let end = Date.now();
 ```
diff --git a/src/content/docs/workers/runtime-apis/bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/index.mdx
index a1b72465e91fb65..c395b7d9593aa09 100644
--- a/src/content/docs/workers/runtime-apis/bindings/index.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/index.mdx
@@ -121,38 +121,37 @@ Bindings are located on the `env` object, which can be accessed in several ways:
   [DurableObject](/durable-objects/), and [Workflow](/workflows/):
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-  ```js
-  export class MyDurableObject extends DurableObject {
-  	async sayHello() {
-  		return `Hi, ${this.env.NAME}!`;
-  	}
-  }
-  ```
-  </TabItem> <TabItem label="Python" icon="seti:python">
-  ```python
-  from workers import WorkerEntrypoint, Response
-
-  class Default(WorkerEntrypoint):
-  	async def fetch(self, request):
-  		return Response(f"Hi {self.env.NAME}")
-  ```
-  </TabItem></Tabs>
-
+    ```js
+    export class MyDurableObject extends DurableObject {
+    	async sayHello() {
+    		return `Hi, ${this.env.NAME}!`;
+    	}
+    }
+    ```
+    </TabItem> <TabItem label="Python" icon="seti:python">
+    ```python
+    from workers import WorkerEntrypoint, Response
+  
+    class Default(WorkerEntrypoint):
+    	async def fetch(self, request):
+    		return Response(f"Hi {self.env.NAME}")
+    ```
+    </TabItem></Tabs>
 
 * It can be imported from `cloudflare:workers`:
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-  ```js
-  import { env } from "cloudflare:workers";
-  console.log(`Hi, ${env.Name}`);
-  ```
-  </TabItem> <TabItem label="Python" icon="seti:python">
-  ```python
-  from workers import import_from_javascript
-  env = import_from_javascript("cloudflare:workers").env
-  print(f"Hi, {env.NAME}")
-  ```
-  </TabItem></Tabs>
+    ```js
+    import { env } from "cloudflare:workers";
+    console.log(`Hi, ${env.Name}`);
+    ```
+    </TabItem> <TabItem label="Python" icon="seti:python">
+    ```python
+    from workers import import_from_javascript
+    env = import_from_javascript("cloudflare:workers").env
+    print(f"Hi, {env.NAME}")
+    ```
+    </TabItem></Tabs>
 
 ### Importing `env` as a global
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
index 90cbad356d0ff57..6354459443f42ff 100644
--- a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
@@ -6,16 +6,16 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components"
+import { TabItem, Tabs, WranglerConfig } from "~/components";
 
 The Rate Limiting API lets you define rate limits and write code around them in your Worker.
 
 You can use it to enforce:
 
-* Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
-* Different rate limits for different types of customers or users (ex: free vs. paid)
-* Resource-specific or path-specific limits (ex: limit per API route)
-* Any combination of the above
+- Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
+- Different rate limits for different types of customers or users (ex: free vs. paid)
+- Resource-specific or path-specific limits (ex: limit per API route)
+- Any combination of the above
 
 The Rate Limiting API is backed by the same infrastructure that serves [rate limiting rules](/waf/rate-limiting-rules/).
 
@@ -96,15 +96,13 @@ export default {
 
 The `limit()` API accepts a single argument — a configuration object with the `key` field.
 
-* The key you provide can be any `string` value.
-* A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
+- The key you provide can be any `string` value.
+- A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
 
 You can define and configure multiple rate limiting configurations per Worker, which allows you to define different limits against incoming request and/or user parameters as needed to protect your application or upstream APIs.
 
 For example, here is how you can define two rate limiting configurations for free and paid tier users:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -139,12 +137,12 @@ For example, here is how you can define two rate limiting configurations for fre
 
 A rate limiting binding has the following settings:
 
-| Setting | Type | Description |
-| --- | --- | --- |
-| `namespace_id` | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
-| `simple` | `object` | The rate limit configuration. `simple` is the only supported type. |
-| `simple.limit` | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`. |
-| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`. |
+| Setting         | Type     | Description                                                                                                                                                                                                                                     |
+| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `namespace_id`  | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
+| `simple`        | `object` | The rate limit configuration. `simple` is the only supported type.                                                                                                                                                                              |
+| `simple.limit`  | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`.                                                                                                                                                               |
+| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`.                                                                                                                                                                 |
 
 :::note
 Two rate limiting bindings that share the same `namespace_id` — even across different Workers on the same account — share the same rate limit counters for a given key. This is intentional and allows you to enforce a single rate limit across multiple Workers.
@@ -178,19 +176,19 @@ For example, to apply a rate limit of 1500 requests per minute, you would define
 
 The `key` passed to the `limit` function, that determines what to rate limit on, should represent a unique characteristic of a user or class of user that you wish to rate limit.
 
-* Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
-* It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
+- Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
+- It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
 
 ```ts
 // Recommended: use a key that represents a specific user or class of user
-const url = new URL(req.url)
-const userId = url.searchParams.get("userId") || ""
-const { success } = await env.MY_RATE_LIMITER.limit({ key: userId })
+const url = new URL(req.url);
+const userId = url.searchParams.get("userId") || "";
+const { success } = await env.MY_RATE_LIMITER.limit({ key: userId });
 
 // Not recommended:  many users may share a single IP, especially on mobile networks
 // or when using privacy-enabling proxies
-const ipAddress = req.headers.get("cf-connecting-ip") || ""
-const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })
+const ipAddress = req.headers.get("cf-connecting-ip") || "";
+const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress });
 ```
 
 ## Locality
@@ -208,7 +206,7 @@ The underlying counters are cached on the same machine that your Worker runs in,
 This means that while in your code you `await` a call to the `limit()` method:
 
 ```javascript
-const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId })
+const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId });
 ```
 
 You are not waiting on a network request. You can use the Rate Limiting API without introducing any meaningful latency to your Worker.
@@ -223,11 +221,11 @@ For example, if many requests come in to your Worker in a single Cloudflare loca
 
 Rate limiting bindings are not currently visible in the Cloudflare dashboard. To monitor rate-limited requests from your Worker:
 
-* **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
-* **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
+- **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
+- **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
 
 ## Examples
 
-* [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
-* [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
-* [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
+- [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
+- [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
+- [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
index a30129269dd55d9..153b3d20f4de2f8 100644
--- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
@@ -30,16 +30,14 @@ For example, consider the following Worker that implements a [`fetch()` handler]
 
 ```js
 export default {
-  async fetch(request, env, ctx) {
-    return new Response("Hello World!");
-  }
-}
+	async fetch(request, env, ctx) {
+		return new Response("Hello World!");
+	},
+};
 ```
 
 The following Worker declares a binding to the Worker above:
 
-
-
 <WranglerConfig>
 
 ```jsonc
@@ -74,12 +72,12 @@ If you construct a new request manually, rather than forwarding an existing one,
 
 ```js
 export default {
-  async fetch(request, env) {
-    // provide a valid URL
-    let newRequest = new Request("https://valid-url.com", { method: "GET" });
-    let response = await env.WORKER_B.fetch(newRequest);
-    return response;
-  }
+	async fetch(request, env) {
+		// provide a valid URL
+		let newRequest = new Request("https://valid-url.com", { method: "GET" });
+		let response = await env.WORKER_B.fetch(newRequest);
+		return response;
+	},
 };
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/stream.mdx b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
index 8614dfafc2d517e..f07806aa6308be8 100644
--- a/src/content/docs/workers/runtime-apis/bindings/stream.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
@@ -4,5 +4,4 @@ title: Stream
 external_link: /stream/manage-video-library/bindings/
 head: []
 description: Upload, manage, and deliver video with Cloudflare Stream.
-
 ---
diff --git a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
index 53634f635526565..f6647c550ce60aa 100644
--- a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
@@ -15,7 +15,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components"
+import { TabItem, Tabs, WranglerConfig } from "~/components";
 
 The version metadata binding can be used to access metadata associated with a [version](/workers/configuration/versions-and-deployments/#versions) from inside the Workers runtime.
 
diff --git a/src/content/docs/workers/runtime-apis/cache.mdx b/src/content/docs/workers/runtime-apis/cache.mdx
index cc26647ff0a0df2..6347b07bd87cc61 100644
--- a/src/content/docs/workers/runtime-apis/cache.mdx
+++ b/src/content/docs/workers/runtime-apis/cache.mdx
@@ -30,7 +30,7 @@ This individualized zone cache object differs from Cloudflare’s Global CDN. Fo
 
 :::
 
-***
+---
 
 ## Accessing Cache
 
@@ -44,7 +44,7 @@ await cache.match(request);
 You may create and manage additional Cache instances via the [`caches.open`](https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage/open) method.
 
 ```js
-let myCache = await caches.open('custom:cache');
+let myCache = await caches.open("custom:cache");
 await myCache.match(request);
 ```
 
@@ -56,28 +56,28 @@ When using the cache API, avoid overriding the hostname in cache requests, as th
 // recommended approach: use your Worker hostname to ensure efficient caching
 request.url = "https://your-Worker-hostname.com/";
 
-let myCache = await caches.open('custom:cache');
+let myCache = await caches.open("custom:cache");
 let response = await myCache.match(request);
 ```
 
 :::
 
-***
+---
 
 ## Headers
 
 Our implementation of the Cache API respects the following HTTP headers on the response passed to `put()`:
 
-* `Cache-Control`
-  * Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
-* `Cache-Tag`
-  * Allows resource purging by tag(s) later.
-* `ETag`
-  * Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
-* `Expires` string
-  * A string that specifies when the resource becomes invalid.
-* `Last-Modified`
-  * Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
+- `Cache-Control`
+  - Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
+- `Cache-Tag`
+  - Allows resource purging by tag(s) later.
+- `ETag`
+  - Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
+- `Expires` string
+  - A string that specifies when the resource becomes invalid.
+- `Last-Modified`
+  - Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
 
 This differs from the web browser Cache API as they do not honor any headers on the request or response.
 
@@ -89,7 +89,7 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 
 :::
 
-***
+---
 
 ## Methods
 
@@ -99,9 +99,8 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 cache.put(request, response);
 ```
 
-* <code>put(request, response)</code> : Promise
-
-  * Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
+- <code>put(request, response)</code> : Promise
+  - Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
 
 :::note
 
@@ -111,20 +110,19 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 
 #### Parameters
 
-* `request` string | Request
+- `request` string | Request
+  - Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
 
-  * Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
-
-* `response` Response
-  * A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
+- `response` Response
+  - A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
 
 #### Invalid parameters
 
 `cache.put` will throw an error if:
 
-* The `request` passed is a method other than `GET`.
-* The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
-* The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
+- The `request` passed is a method other than `GET`.
+- The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
+- The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
 
 #### Errors
 
@@ -136,40 +134,34 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 cache.match(request, options);
 ```
 
-* <code>match(request, options)</code> : Promise`<Response | undefined>`
-
-  * Returns a promise wrapping the response object keyed to that request.
+- <code>match(request, options)</code> : Promise`<Response | undefined>`
+  - Returns a promise wrapping the response object keyed to that request.
 
 :::note
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
 :::
 
-
 #### Parameters
 
-* `request` string | Request
+- `request` string | Request
+  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
-  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
-
-* `options`
-  * Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
+- `options`
+  - Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
 
 Unlike the browser Cache API, Cloudflare Workers do not support the `ignoreSearch` or `ignoreVary` options on `match()`. You can accomplish this behavior by removing query strings or HTTP headers at `put()` time.
 
 Our implementation of the Cache API respects the following HTTP headers on the request passed to `match()`:
 
-* `Range`
-
-  * Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
-
-* `If-Modified-Since`
+- `Range`
+  - Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
 
-  * Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
+- `If-Modified-Since`
+  - Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
 
-* `If-None-Match`
-
-  * Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
+- `If-None-Match`
+  - Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
 
 :::note
 
@@ -188,12 +180,12 @@ If you use Cloudflare Logs, you may see these `504` responses with the `RequestS
 cache.delete(request, options);
 ```
 
-* <code>delete(request, options)</code> : Promise`<boolean>`
+- <code>delete(request, options)</code> : Promise`<boolean>`
 
 Deletes the `Response` object from the cache and returns a `Promise` for a Boolean response:
 
-* `true`: The response was cached but is now deleted
-* `false`: The response was not in the cache at the time of deletion.
+- `true`: The response was cached but is now deleted
+- `false`: The response was not in the cache at the time of deletion.
 
 :::caution[Global purges]
 
@@ -203,18 +195,17 @@ The `cache.delete` method only purges content of the cache in the data center th
 
 #### Parameters
 
-* `request` string | Request
-
-  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+- `request` string | Request
+  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
-* `options` object
-  * Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+- `options` object
+  - Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
 
-***
+---
 
 ## Related resources
 
-* [How the cache works](/workers/reference/how-the-cache-works/)
-* [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
-* [Example: using the Cache API](/workers/examples/cache-api/)
-* [Example: caching POST requests](/workers/examples/cache-post-request/)
+- [How the cache works](/workers/reference/how-the-cache-works/)
+- [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
+- [Example: using the Cache API](/workers/examples/cache-api/)
+- [Example: caching POST requests](/workers/examples/cache-post-request/)
diff --git a/src/content/docs/workers/runtime-apis/console.mdx b/src/content/docs/workers/runtime-apis/console.mdx
index 6ed3997531c52a7..f1861458031b416 100644
--- a/src/content/docs/workers/runtime-apis/console.mdx
+++ b/src/content/docs/workers/runtime-apis/console.mdx
@@ -18,39 +18,39 @@ The table below enumerates each method, and the extent to which it is supported
 
 All methods noted as "✅ supported" have the following behavior:
 
-* They will be written to the console in local dev (`npx wrangler@latest dev`)
-* They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
-* They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
+- They will be written to the console in local dev (`npx wrangler@latest dev`)
+- They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
+- They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
 
 All methods noted as "🟡 partial support" have the following behavior:
 
-* In both production and local development the method can be safely called, but will do nothing (no op)
-* In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
+- In both production and local development the method can be safely called, but will do nothing (no op)
+- In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
 
 Refer to [Log from Workers](https://developers.cloudflare.com/workers/observability/log-from-workers/) for more on debugging and adding logs to Workers.
 
 | Method                                                                                                         | Behavior                                                                                           |
 | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                        |
-| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                        |
-| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                        |
-| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                        |
-| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                        |
+| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                       |
+| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                       |
+| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                       |
+| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                       |
+| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                       |
 | [`console.clear()`](https://developer.mozilla.org/en-US/docs/Web/API/console/clear_static)                     | 🟡 partial support                                                                                 |
 | [`console.count()`](https://developer.mozilla.org/en-US/docs/Web/API/console/count_static)                     | 🟡 partial support                                                                                 |
 | [`console.group()`](https://developer.mozilla.org/en-US/docs/Web/API/console/group_static)                     | 🟡 partial support                                                                                 |
 | [`console.table()`](https://developer.mozilla.org/en-US/docs/Web/API/console/table_static)                     | 🟡 partial support                                                                                 |
 | [`console.trace()`](https://developer.mozilla.org/en-US/docs/Web/API/console/trace_static)                     | 🟡 partial support                                                                                 |
-| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                            |
-| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                            |
-| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                            |
-| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                            |
-| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                            |
-| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                            |
-| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                            |
-| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                            |
-| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                            |
-| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                            |
-| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                            |
-| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                            |
+| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                           |
+| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                           |
+| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                           |
+| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                           |
+| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                           |
+| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                           |
+| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                           |
+| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                           |
+| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                           |
+| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                           |
+| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                           |
+| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                           |
 | [`console.createTask()`](https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces) | 🔴 Will throw an exception in production, but works in local dev, Quick Editor, and remote preview |
diff --git a/src/content/docs/workers/runtime-apis/encoding.mdx b/src/content/docs/workers/runtime-apis/encoding.mdx
index 7f2f363e0232ea5..1c2d6dd741d8730 100644
--- a/src/content/docs/workers/runtime-apis/encoding.mdx
+++ b/src/content/docs/workers/runtime-apis/encoding.mdx
@@ -24,24 +24,15 @@ let encoder = new TextEncoder();
 
 ### Properties
 
-
-
-* `encoder.encoding` DOMString read-only
-  * The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
-
-
+- `encoder.encoding` DOMString read-only
+  - The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
 
 ### Methods
 
+- <code>encode(inputUSVString)</code> : Uint8Array
+  - Encodes a string input.
 
-
-* <code>encode(inputUSVString)</code> : Uint8Array
-
-  * Encodes a string input.
-
-
-
-***
+---
 
 ## TextDecoder
 
@@ -59,25 +50,16 @@ let decoder = new TextDecoder();
 
 ### Properties
 
+- `decoder.encoding` DOMString read-only
+  - The name of the decoder that describes the method the `TextDecoder` uses.
 
+- `decoder.fatal` boolean read-only
+  - Indicates if the error mode is fatal.
 
-* `decoder.encoding` DOMString read-only
-
-  * The name of the decoder that describes the method the `TextDecoder` uses.
-
-* `decoder.fatal` boolean read-only
-
-  * Indicates if the error mode is fatal.
-
-* `decoder.ignoreBOM` boolean read-only
-  * Indicates if the byte-order marker is ignored.
-
-
+- `decoder.ignoreBOM` boolean read-only
+  - Indicates if the byte-order marker is ignored.
 
 ### Methods
 
-
-
-* `decode()` : DOMString
-  * Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
-
+- `decode()` : DOMString
+  - Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
diff --git a/src/content/docs/workers/runtime-apis/eventsource.mdx b/src/content/docs/workers/runtime-apis/eventsource.mdx
index 789989011083673..e8678e44d07dd79 100644
--- a/src/content/docs/workers/runtime-apis/eventsource.mdx
+++ b/src/content/docs/workers/runtime-apis/eventsource.mdx
@@ -19,12 +19,8 @@ The [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource
 let eventSource = new EventSource(url, options);
 ```
 
-
-
-* `url` USVString - The URL to which to connect.
-* `options` EventSourceInit - An optional dictionary containing any optional settings.
-
-
+- `url` USVString - The URL to which to connect.
+- `options` EventSourceInit - An optional dictionary containing any optional settings.
 
 By default, the `EventSource` will use the global `fetch()` function under the
 covers to make requests. If you need to use a different fetch implementation as
@@ -32,10 +28,10 @@ provided by a Cloudflare Workers binding, you can pass the `fetcher` option:
 
 ```js
 export default {
-  async fetch(req, env) {
-    let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
-    // ...
-  }
+	async fetch(req, env) {
+		let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
+		// ...
+	},
 };
 ```
 
@@ -43,49 +39,34 @@ Note that the `fetcher` option is a Cloudflare Workers specific extension.
 
 ### Properties
 
-
-
-* `eventSource.url` USVString read-only
-  * The URL of the event source.
-* `eventSource.readyState` USVString read-only
-  * The state of the connection.
-* `eventSource.withCredentials` Boolean read-only
-  * A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
-
-
+- `eventSource.url` USVString read-only
+  - The URL of the event source.
+- `eventSource.readyState` USVString read-only
+  - The state of the connection.
+- `eventSource.withCredentials` Boolean read-only
+  - A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
 
 ### Methods
 
-
-
-* `eventSource.close()`
-  * Closes the connection.
-* `eventSource.onopen`
-  * An event handler called when a connection is opened.
-* `eventSource.onmessage`
-  * An event handler called when a message is received.
-* `eventSource.onerror`
-  * An event handler called when an error occurs.
-
-
+- `eventSource.close()`
+  - Closes the connection.
+- `eventSource.onopen`
+  - An event handler called when a connection is opened.
+- `eventSource.onmessage`
+  - An event handler called when a message is received.
+- `eventSource.onerror`
+  - An event handler called when an error occurs.
 
 ### Events
 
-
-
-* `message`
-  * Fired when a message is received.
-* `open`
-  * Fired when the connection is opened.
-* `error`
-  * Fired when an error occurs.
-
-
+- `message`
+  - Fired when a message is received.
+- `open`
+  - Fired when the connection is opened.
+- `error`
+  - Fired when an error occurs.
 
 ### Class Methods
 
-
-
-* <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
-  * This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
-
+- <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
+  - This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
diff --git a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
index afee782db35b496..17256889d32d9bb 100644
--- a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
@@ -13,36 +13,27 @@ Incoming HTTP requests to a Worker are passed to the `fetch()` handler as a [`Re
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response('Hello World!');
+		return new Response("Hello World!");
 	},
 };
 ```
 
 :::note
 
-
 The Workers runtime does not support `XMLHttpRequest` (XHR). Learn the difference between `XMLHttpRequest` and `fetch()` in the [MDN](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) documentation.
 
-
 :::
 
 ### Parameters
 
+- `request` Request
+  - The incoming HTTP request.
 
+- `env` object
+  - The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
 
-* `request` Request
-
-  * The incoming HTTP request.
-
-* `env` object
-
-  * The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
-
-* <code>ctx.waitUntil(promisePromise)</code> : void
-
-  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
-
-* <code>ctx.passThroughOnException()</code> : void
-
-  * Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
+- <code>ctx.waitUntil(promisePromise)</code> : void
+  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
 
+- <code>ctx.passThroughOnException()</code> : void
+  - Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
diff --git a/src/content/docs/workers/runtime-apis/handlers/index.mdx b/src/content/docs/workers/runtime-apis/handlers/index.mdx
index f62e15838d7d289..0ce1d48c75d798b 100644
--- a/src/content/docs/workers/runtime-apis/handlers/index.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/index.mdx
@@ -9,14 +9,14 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Handlers are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker. For example, the `fetch()` handler receives an HTTP request, and can return a response:
 
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response('Hello World!');
+		return new Response("Hello World!");
 	},
 };
 ```
diff --git a/src/content/docs/workers/runtime-apis/handlers/tail.mdx b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
index 7c6fbbaa19a19ad..b95fc4c33d0ffea 100644
--- a/src/content/docs/workers/runtime-apis/handlers/tail.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
@@ -18,170 +18,124 @@ To configure a Tail Worker, refer to [Tail Workers documentation](/workers/obser
 
 ```js
 export default {
-  async tail(events, env, ctx) {
-    fetch("<YOUR_ENDPOINT>", {
-      method: "POST",
-      body: JSON.stringify(events),
-    })
-  }
-}
+	async tail(events, env, ctx) {
+		fetch("<YOUR_ENDPOINT>", {
+			method: "POST",
+			body: JSON.stringify(events),
+		});
+	},
+};
 ```
 
 ### Parameters
 
+- `events` array
+  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
 
+- `env` object
+  - An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
 
-* `events` array
-
-  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
-
-* `env` object
-
-  * An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
-
-* `ctx` object
-  * An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
-
-
+- `ctx` object
+  - An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
 
 ### Properties
 
+- `event.type` string
+  - The type of event. This will always return `"tail"`.
 
+- `event.traces` array
+  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
 
-* `event.type` string
-
-  * The type of event. This will always return `"tail"`.
-
-* `event.traces` array
-
-  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
-
-* <code>event.waitUntil(promisePromise)</code> : void
-
-  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
-
-
+- <code>event.waitUntil(promisePromise)</code> : void
+  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
 
 ### `TailItems`
 
 #### Properties
 
-
-
-* `scriptName` string
-
-  * The name of the producer script.
-
-* `event` object
-
-  * Contains information about the Worker’s triggering event.
-    * For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
-    * For other event types: `null`, currently.
-
-* `eventTimestamp` number
-
-  * Measured in epoch time.
-
-* `logs` array
-
-  * An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
-
-* `exceptions` array
-
-  * An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
-
-* `outcome` string
-
-  * The outcome of the Worker invocation, one of:
-    * `unknown`: outcome status was not set.
-    * `ok`: The worker invocation succeeded.
-    * `exception`: An unhandled exception was thrown.  This can happen for many reasons, including:
-      * An uncaught JavaScript exception.
-      * A fetch handler that does not result in a Response.
-      * An internal error.
-    * `exceededCpu`: The Worker invocation exceeded either its CPU limits.
-    * `exceededMemory`: The Worker invocation exceeded memory limits.
-    * `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
-    * `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
-    * `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
-
-
+- `scriptName` string
+  - The name of the producer script.
+
+- `event` object
+  - Contains information about the Worker’s triggering event.
+    - For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
+    - For other event types: `null`, currently.
+
+- `eventTimestamp` number
+  - Measured in epoch time.
+
+- `logs` array
+  - An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
+
+- `exceptions` array
+  - An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
+
+- `outcome` string
+  - The outcome of the Worker invocation, one of:
+    - `unknown`: outcome status was not set.
+    - `ok`: The worker invocation succeeded.
+    - `exception`: An unhandled exception was thrown. This can happen for many reasons, including:
+      - An uncaught JavaScript exception.
+      - A fetch handler that does not result in a Response.
+      - An internal error.
+    - `exceededCpu`: The Worker invocation exceeded either its CPU limits.
+    - `exceededMemory`: The Worker invocation exceeded memory limits.
+    - `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
+    - `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
+    - `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
 
 :::note[Outcome is not the same as HTTP status.]
 
 Outcome is equivalent to the exit status of a script and an indicator of whether it has fully run to completion. A Worker outcome may differ from a response code if, for example:
 
-* a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
-* a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
+- a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
+- a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
   :::
 
 ### `FetchEventInfo`
 
 #### Properties
 
+- `request` object
+  - A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
 
-
-* `request` object
-
-  * A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
-
-* `response` object
-
-  * A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
-
+- `response` object
+  - A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
 
 ### `TailRequest`
 
 #### Properties
 
+- `cf` object
+  - Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
 
+- `headers` object
+  - Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
 
-* `cf` object
-
-  * Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
-
-* `headers` object
-
-  * Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
-
-* `method` string
-
-  * The HTTP request method.
-
-* `url` string
-
-  * The HTTP request URL (redacted by default).
-
+- `method` string
+  - The HTTP request method.
 
+- `url` string
+  - The HTTP request URL (redacted by default).
 
 #### Methods
 
-
-
-* `getUnredacted()` object
-
-  * Returns a TailRequest object with unredacted properties
-
-
+- `getUnredacted()` object
+  - Returns a TailRequest object with unredacted properties
 
 Some of the properties of `TailRequest` are redacted by default to make it harder to accidentally record sensitive information, like user credentials or API tokens. The redactions use heuristic rules, so they are subject to false positives and negatives. Clients can call `getUnredacted()` to bypass redaction, but they should always be careful about what information is retained, whether using the redaction or not.
 
-* Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
-* URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
-* Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
-* Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
+- Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
+- URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
+- Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
+- Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
 
 ### `TailResponse`
 
 #### Properties
 
-
-
-* `status` number
-
-  * The HTTP status code.
-
-
+- `status` number
+  - The HTTP status code.
 
 ### `TailLog`
 
@@ -189,20 +143,14 @@ Records information sent to console functions.
 
 #### Properties
 
+- `timestamp` number
+  - Measured in epoch time.
 
+- `level` string
+  - A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
 
-* `timestamp` number
-
-  * Measured in epoch time.
-
-* `level` string
-
-  * A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
-
-* `message` object
-
-  * The array of parameters passed to the console function.
-
+- `message` object
+  - The array of parameters passed to the console function.
 
 ### `TailException`
 
@@ -210,22 +158,15 @@ Records an unhandled exception that occurred during the Worker invocation.
 
 #### Properties
 
+- `timestamp` number
+  - Measured in epoch time.
 
+- `name` string
+  - The error type (For example,`Error`, `TypeError`, etc.).
 
-* `timestamp` number
-
-  * Measured in epoch time.
-
-* `name` string
-
-  * The error type (For example,`Error`, `TypeError`, etc.).
-
-* `message` object
-
-  * The error description (For example, `"x" is not a function`).
-
-
+- `message` object
+  - The error description (For example, `"x" is not a function`).
 
 ## Related resources
 
-* [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
+- [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
diff --git a/src/content/docs/workers/runtime-apis/headers.mdx b/src/content/docs/workers/runtime-apis/headers.mdx
index 5fd387aafea782c..f7a50f6ec116fc8 100644
--- a/src/content/docs/workers/runtime-apis/headers.mdx
+++ b/src/content/docs/workers/runtime-apis/headers.mdx
@@ -17,16 +17,16 @@ When a header name possesses multiple values, those values will be concatenated
 ```js
 let headers = new Headers();
 
-headers.get('x-foo'); //=> null
+headers.get("x-foo"); //=> null
 
-headers.set('x-foo', '123');
-headers.get('x-foo'); //=> "123"
+headers.set("x-foo", "123");
+headers.get("x-foo"); //=> "123"
 
-headers.set('x-foo', 'hello');
-headers.get('x-foo'); //=> "hello"
+headers.set("x-foo", "hello");
+headers.get("x-foo"); //=> "hello"
 
-headers.append('x-foo', 'world');
-headers.get('x-foo'); //=> "hello, world"
+headers.append("x-foo", "world");
+headers.get("x-foo"); //=> "hello, world"
 ```
 
 ## Differences
@@ -61,7 +61,6 @@ console.log(headers.getAll("Set-Cookie"));
 
 In Cloudflare Workers, the `Headers.get` method returns a [`USVString`](https://mdn2.netlify.app/en-us/docs/web/api/usvstring/) instead of a [`ByteString`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String), which is specified by the web standard. For most scenarios, this should have no noticeable effect. To compare the differences between these two string classes, refer to this [Playground example](https://workers.cloudflare.com/playground#LYVwNgLglgDghgJwgegGYHsHALQBM4RwDcABAEbogB2+CAngLzbMutvvsCMALAJx-cAzAHZeANkG8AHAAZOU7t2EBWAEy9eqsXNWdOALg5HjbHv34jxk2fMUr1m7Z12cAsACgAwuioQApr7YACJQAM4w6KFQ0D76JBhYeATEJFRwwH4MAERQNH4AHgB0AFahWaSoUGAB6Zk5eUWlWR7evgEQ2AAqdDB+cXAwMGBQAMYEUD7IxXAAbnChIwiwEADUwOi44H4eHgURSCS4fqhw4BAkAN7uAJDzdFQj8X4QIwAWABQIfgCOIH6hEAAlJcbtdqucxucGCQsoBeDcAXHtZUHgkggCCoKSeAgkaFUPwAdxInQKEAAog8Nn4EO9AYUAiNKe9IYDkc8SPTKbgsVCSABlCBLKgAc0KqAQ6GAnleiG8R3ehQVaIx3JZoIZVFC6GqhTA6CF7yynVeYRIJrgJAAqryAGr8wVCkj46KvEjmyH6LIAGhIzLVPk12t1+sNxtCprD5oAQnR-Hbcg6nRAXW7sT5LZ0AGLYKQe70co5cgiq67XZDIEgACT8cCOCAjXxIoRAg0iflwJAg6EdmAA1iQfGA6I7nSRo7GBfHQt6yGj+yAEKCy6bgEM-BlfOM0yBQv9LTa48LQoUiaHUiSSMM8cOwGASDBBec4Ivy-jEFR466KLOk2FCqzzq81a1mGuIEpWQFUqE7wXDC+ZttgkJZHEcGFucAC+xbXF8EDzlQZ6EgASv8EQan4BpSn4Ix9pQ5xJn4JAAAatAGfgMa6NAdoBJBEeE-r0YBNaQR2XY7vRdFzhAMCzgyK6IGE-qFF6lwkAJwEkBhNxoe4aEeCYelGGYAiWBI0hyAoShqBoWg6HoLQ+P4gQhLxUQxFQcQJDg+CEKQaQZNkGSEF5cDlPEVQ1H5WRkLqZDNF49ntF0PR9K6gzDJCExUFMmpUDs7gXFkwBwLkAD66ybNUSH1EcjRlDp7j6Q1rCGRYogmTY5n2FZTguMwHhAA).
 
-
 ## Cloudflare headers
 
 Cloudflare sets a number of its own custom headers on incoming requests and outgoing responses. While some may be used for its own tracking and bookkeeping, many of these can be useful to your own applications – or Workers – too.
@@ -70,5 +69,5 @@ For a list of documented Cloudflare request headers, refer to [Cloudflare HTTP h
 
 ## Related resources
 
-* [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
-* [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
\ No newline at end of file
+- [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
+- [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
diff --git a/src/content/docs/workers/runtime-apis/messagechannel.mdx b/src/content/docs/workers/runtime-apis/messagechannel.mdx
index 34a69e18a8ca1ac..dc8e4475fe3ec30 100644
--- a/src/content/docs/workers/runtime-apis/messagechannel.mdx
+++ b/src/content/docs/workers/runtime-apis/messagechannel.mdx
@@ -19,10 +19,10 @@ currently limited to uses with a single Worker instance. This means that you can
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log('Received message:', event.data);
+	console.log("Received message:", event.data);
 };
 
-port2.postMessage('Hello from port2!');
+port2.postMessage("Hello from port2!");
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -31,13 +31,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-* Transfer lists are currently not supported. This means that you will not be able to transfer
+- Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-	are errors serializing or deserializing the message data. Instead, the error will be thrown when
-	the `postMessage` method is called on the sending port.
-* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+  are errors serializing or deserializing the message data. Instead, the error will be thrown when
+  the `postMessage` method is called on the sending port.
+- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/docs/workers/runtime-apis/nodejs/util.mdx b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
index 2e7372f4d555bc0..7a797483bdc8683 100644
--- a/src/content/docs/workers/runtime-apis/nodejs/util.mdx
+++ b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
@@ -35,16 +35,16 @@ await promisifiedFoo(args);
 Similarly to `promisify`, `callbackify` converts a Promise-returning async function into a Node.js-style callback function:
 
 ```js
-import { callbackify } from 'node:util';
+import { callbackify } from "node:util";
 
 async function foo(args) {
-  throw new Error('boom');
+	throw new Error("boom");
 }
 
 const callbackifiedFoo = callbackify(foo);
 
 callbackifiedFoo(args, (err, value) => {
-  if (err) throw err;
+	if (err) throw err;
 });
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/performance.mdx b/src/content/docs/workers/runtime-apis/performance.mdx
index 0465b6db640c78a..f8c14e1b3cc76b2 100644
--- a/src/content/docs/workers/runtime-apis/performance.mdx
+++ b/src/content/docs/workers/runtime-apis/performance.mdx
@@ -21,7 +21,7 @@ When Workers are deployed to Cloudflare, as a security measure to [mitigate agai
 ```typescript title="Time is frozen — start will have the exact same value as end."
 const start = performance.now();
 for (let i = 0; i < 1e6; i++) {
-  // do expensive work
+	// do expensive work
 }
 const end = performance.now();
 const timing = end - start; // 0
diff --git a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
index a0677b887aebf4c..acf48ac5f2c6e48 100644
--- a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
@@ -18,9 +18,9 @@ An exception thrown by an RPC method implementation will propagate to the caller
 
 ### Unsupported error types
 
-* If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
-* The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
-* Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
+- If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
+- The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
+- Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
 
 ## Additional properties
 
diff --git a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
index 2a80b67db3d88e2..5bb6019d5d24910 100644
--- a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
@@ -16,7 +16,7 @@ Some method names are reserved or have special semantics.
 
 ## Special Methods
 
-For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does *not* apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
+For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does _not_ apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
 
 ### `fetch()`
 
@@ -36,12 +36,12 @@ The `connect()` method of the `WorkerEntrypoint` class is reserved for opening a
 
 The following method (or property) names may not be used as RPC methods on any RPC type (including `WorkerEntrypoint`, `DurableObject`, and `RpcTarget`):
 
-* `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
-* `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
+- `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
+- `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
 
 The following methods are disallowed only on `WorkerEntrypoint` and `DurableObject`, but allowed on `RpcTarget`. These methods have historically had special meaning to Durable Objects, where they are used to handle certain system-generated events.
 
-* `alarm`
-* `webSocketMessage`
-* `webSocketClose`
-* `webSocketError`
+- `alarm`
+- `webSocketMessage`
+- `webSocketClose`
+- `webSocketError`
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
index 72512cc6f9f0f85..8ec8b621e64213b 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
@@ -13,47 +13,33 @@ A `ReadableStream` is returned by the `readable` property inside [`TransformStre
 
 ## Properties
 
-
-
-* `locked` boolean
-  * A Boolean value that indicates if the readable stream is locked to a reader.
-
-
+- `locked` boolean
+  - A Boolean value that indicates if the readable stream is locked to a reader.
 
 ## Methods
 
+- <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
+  - Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
 
-
-* <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
-
-  * Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
-
-* <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
-
-  * Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
+- <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
+  - Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
 
 ```js
-let reader = readable.getReader({ mode: 'byob' });
+let reader = readable.getReader({ mode: "byob" });
 ```
 
-
-
 ### `PipeToOptions`
 
+- `preventClose` bool
+  - When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
 
+- `preventAbort` bool
+  - When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
 
-* `preventClose` bool
-
-  * When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
-
-* `preventAbort` bool
-
-  * When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
-* [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
+- [Streams](/workers/runtime-apis/streams/)
+- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+- [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
index cff8e9257521f97..c8a67b7ecf18fec 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
@@ -24,50 +24,41 @@ A `ReadableStreamBYOBReader` is not instantiated via its constructor. Rather, it
 
 ```js
 const { readable, writable } = new TransformStream();
-const reader = readable.getReader({ mode: 'byob' });
+const reader = readable.getReader({ mode: "byob" });
 ```
 
-***
+---
 
 ## Methods
 
+- <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+  - Returns a promise with the next available chunk of data read into a passed-in buffer.
 
+- <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+  - Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read. The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
+    - If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
+    - If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
+    - If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
+    - If the stream errors, the promise rejects.
+    - `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
 
-* <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-
-  * Returns a promise with the next available chunk of data read into a passed-in buffer.
-
-* <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-
-  * Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read.  The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
-
-    * If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
-    * If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
-    * If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
-    * If the stream errors, the promise rejects.
-    * `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
-
-
-
-***
+---
 
 ## Common issues
 
 :::caution[Warning]
 
-
 `read` provides no control over the minimum number of bytes that should be read into the buffer. Even if you allocate a 1 MiB buffer, the kernel is perfectly within its rights to fulfill this read with a single byte, whether or not an EOF immediately follows.
 
 In practice, the Workers team has found that `read` typically fills only 1% of the provided buffer.
 
 `readAtLeast` is a non-standard extension to the Streams API which allows users to specify that at least `minElements` elements must be read into the buffer before resolving the read. For a `Uint8Array` (the most common case), each element is one byte, so `minElements` is effectively a byte count. If the stream ends before `minElements` elements are available, the partial data that was read is still returned rather than throwing an error — refer to the [`readAtLeast` method documentation above](#methods) for the full details.
 
-
 :::
 
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
+- [Streams](/workers/runtime-apis/streams/)
+- [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
index 72a05a4edd97f20..41d4eaf45b54a02 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
@@ -23,44 +23,32 @@ const { readable, writable } = new TransformStream();
 const reader = readable.getReader();
 ```
 
-***
+---
 
 ## Properties
 
-
-
-* `reader.closed` : Promise
-
-  * A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
-
-
+- `reader.closed` : Promise
+  - A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
 
 ## Methods
 
+- `read()` : Promise
+  - A promise that returns the next available chunk of data being passed through the reader queue.
 
-
-* `read()` : Promise
-
-  * A promise that returns the next available chunk of data being passed through the reader queue.
-
-* <code>cancel(reasonstringoptional)</code> : void
-
-  * Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
+- <code>cancel(reasonstringoptional)</code> : void
+  - Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet read is lost.
   :::
 
-* `releaseLock()` : void
-
-  * Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+- `releaseLock()` : void
+  - Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
index 029a878e9e847be..46c9e41542ea8b0 100644
--- a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
@@ -13,7 +13,7 @@ A transform stream consists of a pair of streams: a writable stream, known as it
 
 Workers currently only implements an identity transform stream, a type of transform stream which forwards all chunks written to its writable side to its readable side, without any changes.
 
-***
+---
 
 ## Constructor
 
@@ -21,26 +21,17 @@ Workers currently only implements an identity transform stream, a type of transf
 let { readable, writable } = new TransformStream();
 ```
 
-
-
-* `TransformStream()` TransformStream
-
-  * Returns a new identity transform stream.
-
-
+- `TransformStream()` TransformStream
+  - Returns a new identity transform stream.
 
 ## Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## `IdentityTransformStream`
 
@@ -54,26 +45,17 @@ The `IdentityTransformStream` readable side supports [bring your own buffer (BYO
 let { readable, writable } = new IdentityTransformStream();
 ```
 
-
-
-* `IdentityTransformStream()` IdentityTransformStream
-
-  * Returns a new identity transform stream.
-
-
+- `IdentityTransformStream()` IdentityTransformStream
+  - Returns a new identity transform stream.
 
 ### Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## `FixedLengthStream`
 
@@ -85,29 +67,20 @@ The `FixedLengthStream` is a specialization of `IdentityTransformStream` that li
 let { readable, writable } = new FixedLengthStream(1000);
 ```
 
-
-
-* `FixedLengthStream(length)` FixedLengthStream
-
-  * Returns a new identity transform stream.
-  * `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
-
-
+- `FixedLengthStream(length)` FixedLengthStream
+  - Returns a new identity transform stream.
+  - `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
 
 ### Properties
 
+- `readable` ReadableStream
+  - An instance of a `ReadableStream`.
+- `writable` WritableStream
+  - An instance of a `WritableStream`.
 
-
-* `readable` ReadableStream
-  * An instance of a `ReadableStream`.
-* `writable` WritableStream
-  * An instance of a `WritableStream`.
-
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
+- [Streams](/workers/runtime-apis/streams/)
+- [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
index 799ddf11156ada5..1040f59de92975c 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
@@ -15,9 +15,9 @@ A typical way to write to a `WritableStream` is to pipe a [`ReadableStream`](/wo
 
 ```js
 readableStream
-  .pipeTo(writableStream)
-  .then(() => console.log('All data successfully written!'))
-  .catch(e => console.error('Something went wrong!', e));
+	.pipeTo(writableStream)
+	.then(() => console.log("All data successfully written!"))
+	.catch((e) => console.error("Something went wrong!", e));
 ```
 
 To write to a `WritableStream` directly, you must use its writer.
@@ -31,36 +31,25 @@ Refer to the [WritableStreamDefaultWriter](/workers/runtime-apis/streams/writabl
 
 ## Properties
 
-
-
-* `locked` boolean
-
-  * A Boolean value to indicate if the writable stream is locked to a writer.
-
-
+- `locked` boolean
+  - A Boolean value to indicate if the writable stream is locked to a writer.
 
 ## Methods
 
-
-
-* <code>abort(reasonstringoptional)</code> : Promise\<void>
-
-  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+- <code>abort(reasonstringoptional)</code> : Promise\<void>
+  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-* `getWriter()` : WritableStreamDefaultWriter
-
-  * Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+- `getWriter()` : WritableStreamDefaultWriter
+  - Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
index 9778261db7f5088..fda65a4afb87bbd 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
@@ -18,71 +18,57 @@ A writer is used when you want to write directly to a [`WritableStream`](/worker
 
 ```js
 function writeArrayToStream(array, writableStream) {
-  const writer = writableStream.getWriter();
-  array.forEach(chunk => writer.write(chunk).catch(() => {}));
+	const writer = writableStream.getWriter();
+	array.forEach((chunk) => writer.write(chunk).catch(() => {}));
 
-  return writer.close();
+	return writer.close();
 }
 
 writeArrayToStream([1, 2, 3, 4, 5], writableStream)
-  .then(() => console.log('All done!'))
-  .catch(e => console.error('Error with the stream: ' + e));
+	.then(() => console.log("All done!"))
+	.catch((e) => console.error("Error with the stream: " + e));
 ```
 
 ## Properties
 
+- `writer.desiredSize` int
+  - The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
 
-
-* `writer.desiredSize` int
-
-  * The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
-
-* `writer.closed` Promise\<void>
-
-  * A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
-
-
+- `writer.closed` Promise\<void>
+  - A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
 
 ## Methods
 
-
-
-* <code>abort(reasonstringoptional)</code> : Promise\<void>
-
-  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+- <code>abort(reasonstringoptional)</code> : Promise\<void>
+  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-* `close()` : Promise\<void>
-
-  * Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
+- `close()` : Promise\<void>
+  - Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
 
-* `releaseLock()` : void
-
-  * Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
+- `releaseLock()` : void
+  - Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
 
 ```js
 let writer = writable.getWriter();
 // Write a preamble.
-writer.write(new TextEncoder().encode('foo bar'));
+writer.write(new TextEncoder().encode("foo bar"));
 // While that’s still writing, pipe the rest of the body from somewhere else.
 writer.releaseLock();
 await someResponse.body.pipeTo(writable);
 ```
 
-* <code>write(chunkany)</code> : Promise\<void>
-
-  * Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
-  * The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+- <code>write(chunkany)</code> : Promise\<void>
+  - Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
+  - The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
 
-
-
-***
+---
 
 ## Related resources
 
-* [Streams](/workers/runtime-apis/streams/)
-* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+- [Streams](/workers/runtime-apis/streams/)
+- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
index be6e3593489cb39..ef899b752b54415 100644
--- a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
+++ b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
@@ -29,143 +29,132 @@ The `connect()` function returns a TCP socket, with both a [readable](/workers/r
 `connect()` is provided as a [Runtime API](/workers/runtime-apis/), and is accessed by importing the `connect` function from `cloudflare:sockets`. This process is similar to how one imports built-in modules in Node.js. Refer to the following codeblock for an example of creating a TCP socket, writing to it, and returning the readable side of the socket as a response:
 
 ```typescript
-import { connect } from 'cloudflare:sockets';
+import { connect } from "cloudflare:sockets";
 
 export default {
-  async fetch(req): Promise<Response> {
-    const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
-    const url = new URL(req.url);
-
-    try {
-      const socket = connect(gopherAddr);
-
-      const writer = socket.writable.getWriter()
-      const encoder = new TextEncoder();
-      const encoded = encoder.encode(url.pathname + "\r\n");
-      await writer.write(encoded);
-      await writer.close();
-
-      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
-    } catch (error) {
-      return new Response("Socket connection failed: " + error, { status: 500 });
-    }
-  }
+	async fetch(req): Promise<Response> {
+		const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
+		const url = new URL(req.url);
+
+		try {
+			const socket = connect(gopherAddr);
+
+			const writer = socket.writable.getWriter();
+			const encoder = new TextEncoder();
+			const encoded = encoder.encode(url.pathname + "\r\n");
+			await writer.write(encoded);
+			await writer.close();
+
+			return new Response(socket.readable, {
+				headers: { "Content-Type": "text/plain" },
+			});
+		} catch (error) {
+			return new Response("Socket connection failed: " + error, {
+				status: 500,
+			});
+		}
+	},
 } satisfies ExportedHandler;
 ```
 
-
-
-* <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
-  * `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
-
+- <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
+  - `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
 
 ### `SocketAddress`
 
+- `hostname` string
+  - The hostname to connect to. Example: `cloudflare.com`.
 
-
-* `hostname` string
-  * The hostname to connect to. Example: `cloudflare.com`.
-
-* `port` number
-  * The port number to connect to. Example: `5432`.
-
-
+- `port` number
+  - The port number to connect to. Example: `5432`.
 
 ### `SocketOptions`
 
+- `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
+  - Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
+  - `off` — Do not use TLS.
+  - `on` — Use TLS.
+  - `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
 
-
-* `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
-  * Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
-  * `off` — Do not use TLS.
-  * `on` — Use TLS.
-  * `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
-
-* `allowHalfOpen` boolean — Defaults to `false`
-  * Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
-  * This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
-
-
+- `allowHalfOpen` boolean — Defaults to `false`
+  - Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
+  - This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
 
 ### `SocketInfo`
 
+- `remoteAddress` string | null
+  - The address of the remote peer the socket is connected to. May not always be set.
 
-
-* `remoteAddress` string | null
-  * The address of the remote peer the socket is connected to. May not always be set.
-
-* `localAddress` string | null
-  * The address of the local network endpoint for this socket. May not always be set.
-
-
+- `localAddress` string | null
+  - The address of the local network endpoint for this socket. May not always be set.
 
 ### `Socket`
 
+- <code>readable</code> : ReadableStream
+  - Returns the readable side of the TCP socket.
 
+- <code>writable</code> : WritableStream
+  - Returns the writable side of the TCP socket.
+  - The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
 
-* <code>readable</code> : ReadableStream
-  * Returns the readable side of the TCP socket.
-
-* <code>writable</code> : WritableStream
-  * Returns the writable side of the TCP socket.
-  * The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
-
-* `opened` `Promise<SocketInfo>`
-  * This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
-
-* `closed` `Promise<void>`
-  * This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
-
-* `close()` `Promise<void>`
-  * Closes the TCP socket. Both the readable and writable streams are forcibly closed.
+- `opened` `Promise<SocketInfo>`
+  - This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
 
-* <code>startTls()</code> : Socket
-  * Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
+- `closed` `Promise<void>`
+  - This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
 
+- `close()` `Promise<void>`
+  - Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
+- <code>startTls()</code> : Socket
+  - Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
 ## Opportunistic TLS (StartTLS)
 
 Many TCP-based systems, including databases and email servers, require that clients use opportunistic TLS (otherwise known as [StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS)) when connecting. In this pattern, the client first creates an insecure TCP socket, without TLS, and then upgrades it to a secure TCP socket, that uses TLS. The `connect()` API simplifies this by providing a method, `startTls()`, which returns a new `Socket` instance that uses TLS:
 
 ```typescript
-import { connect } from "cloudflare:sockets"
+import { connect } from "cloudflare:sockets";
 
 const address = {
-  hostname: "example-postgres-db.com",
-  port: 5432
+	hostname: "example-postgres-db.com",
+	port: 5432,
 };
 const socket = connect(address, { secureTransport: "starttls" });
 const secureSocket = socket.startTls();
 ```
 
-* `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
-* Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
-* `startTls()` should only be called once on an existing socket.
+- `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
+- Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
+- `startTls()` should only be called once on an existing socket.
 
 ## Handle errors
 
 To handle errors when creating a new TCP socket, reading from a socket, or writing to a socket, wrap these calls inside [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) statement blocks. The following example opens a connection to Google.com, initiates a HTTP request, and returns the response. If this fails and throws an exception, it returns a [`500`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-500/) response:
 
 ```typescript
-import { connect } from 'cloudflare:sockets';
+import { connect } from "cloudflare:sockets";
 const connectionUrl = { hostname: "google.com", port: 80 };
-export interface Env { }
+export interface Env {}
 export default {
-  async fetch(req, env, ctx): Promise<Response> {
-    try {
-      const socket = connect(connectionUrl);
-      const writer = socket.writable.getWriter();
-      const encoder = new TextEncoder();
-      const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
-      await writer.write(encoded);
-      await writer.close();
-
-      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
-    } catch (error) {
-      return new Response(`Socket connection failed: ${error}`, { status: 500 });
-    }
-  }
+	async fetch(req, env, ctx): Promise<Response> {
+		try {
+			const socket = connect(connectionUrl);
+			const writer = socket.writable.getWriter();
+			const encoder = new TextEncoder();
+			const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
+			await writer.write(encoded);
+			await writer.close();
+
+			return new Response(socket.readable, {
+				headers: { "Content-Type": "text/plain" },
+			});
+		} catch (error) {
+			return new Response(`Socket connection failed: ${error}`, {
+				status: 500,
+			});
+		}
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -174,7 +163,7 @@ export default {
 You can close a TCP connection by calling `close()` on the socket. This will close both the readable and writable sides of the socket.
 
 ```typescript
-import { connect } from "cloudflare:sockets"
+import { connect } from "cloudflare:sockets";
 
 const socket = connect({ hostname: "my-url.com", port: 70 });
 const reader = socket.readable.getReader();
@@ -186,11 +175,11 @@ const reader = socket.readable.getReader(); // This fails
 
 ## Considerations
 
-* Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
-* TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
-* Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
-* By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
-* Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
+- Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
+- TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
+- Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
+- By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
+- Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
 
 ## Troubleshooting
 
diff --git a/src/content/docs/workers/runtime-apis/web-crypto.mdx b/src/content/docs/workers/runtime-apis/web-crypto.mdx
index 9e3a0f0faaaf9f3..5bb7cee5fad993b 100644
--- a/src/content/docs/workers/runtime-apis/web-crypto.mdx
+++ b/src/content/docs/workers/runtime-apis/web-crypto.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 ## Background
 
@@ -19,13 +19,13 @@ Performing cryptographic operations using the Web Crypto API is significantly fa
 The Web Crypto API is implemented through the `SubtleCrypto` interface, accessible via the global `crypto.subtle` binding. A simple example of calculating a digest (also known as a hash) is:
 
 ```js
-const myText = new TextEncoder().encode('Hello world!');
+const myText = new TextEncoder().encode("Hello world!");
 
 const myDigest = await crypto.subtle.digest(
-  {
-    name: 'SHA-256',
-  },
-  myText // The data you want to hash as an ArrayBuffer
+	{
+		name: "SHA-256",
+	},
+	myText, // The data you want to hash as an ArrayBuffer
 );
 
 console.log(new Uint8Array(myDigest));
@@ -38,27 +38,17 @@ Some common uses include [signing requests](/workers/examples/signing-requests/)
 The Web Crypto API differs significantly from the [Node.js Crypto API](/workers/runtime-apis/nodejs/crypto/). If you are working with code that relies on the Node.js Crypto API, you can use it by enabling the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/).
 :::
 
-***
+---
 
 ## Constructors
 
-
-
-* <code>crypto.DigestStream(algorithm)</code> DigestStream
-
-  * A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
-
-
+- <code>crypto.DigestStream(algorithm)</code> DigestStream
+  - A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
 
 ### Parameters
 
-
-
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
-
-
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
 ### Usage
 
@@ -122,27 +112,16 @@ export default {
 
 ## Methods
 
+- <code>crypto.randomUUID()</code> : string
+  - Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
 
-
-* <code>crypto.randomUUID()</code> : string
-
-  * Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
-
-* <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
-
-  * Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
-
-
+- <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
+  - Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
 
 ### Parameters
 
-
-
-* <code>buffer</code>ArrayBufferView
-
-  * Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
-
-
+- <code>buffer</code>ArrayBufferView
+  - Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
 
 ## SubtleCrypto Methods
 
@@ -150,358 +129,219 @@ These methods are all accessed via [`crypto.subtle`](https://developer.mozilla.o
 
 ### encrypt
 
-
-
-* <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
-
-
+- <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>BufferSource
-
-
+- <code>data</code>BufferSource
 
 ### decrypt
 
-
-
-* <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
-
-
+- <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>BufferSource
-
-
+- <code>data</code>BufferSource
 
 ### sign
 
-
-
-* <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
-
-
+- <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>data</code>ArrayBuffer
-
-
+- <code>data</code>ArrayBuffer
 
 ### verify
 
-
-
-* <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
-
-  * Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
-
-
+- <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
+  - Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>signature</code>ArrayBuffer
-
-* <code>data</code>ArrayBuffer
-
+- <code>signature</code>ArrayBuffer
 
+- <code>data</code>ArrayBuffer
 
 ### digest
 
-
-
-* <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
-
-
+- <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>string | object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
-
-* <code>algorithm</code>string | object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
-
-* <code>data</code>ArrayBuffer
-
-
+- <code>data</code>ArrayBuffer
 
 ### generateKey
 
-
-
-* <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
-
-  * Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
+- <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
+  - Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
 
   ```js
   let keyPair = await crypto.subtle.generateKey(
-    {
-      name: 'AES-GCM',
-      length: 256,
-    },
-    true,
-    ['encrypt', 'decrypt']
+  	{
+  		name: "AES-GCM",
+  		length: 256,
+  	},
+  	true,
+  	["encrypt", "decrypt"],
   );
   ```
 
-
-
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
+- <code>extractable</code>bool
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
-
-
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
 ### deriveKey
 
-
-
-* <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
-
-
+- <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
+- <code>baseKeyCryptoKey</code>
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
-
-* <code>baseKeyCryptoKey</code>
-
-* <code>derivedKeyAlgorithmobject</code>
-
-  * Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
-
-* <code>extractablebool</code>
-
-* <code>keyUsagesArray</code>
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
+- <code>derivedKeyAlgorithmobject</code>
+  - Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
+- <code>extractablebool</code>
 
+- <code>keyUsagesArray</code>
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
 ### deriveBits
 
-
-
-* <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
-
-  * Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
-
-
+- <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
+  - Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
 
 #### Parameters
 
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
 
+- <code>baseKey</code>CryptoKey
 
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
-
-* <code>baseKey</code>CryptoKey
-
-* <code>length</code>int
-
-  * Length of the bit string to derive.
-
-
+- <code>length</code>int
+  - Length of the bit string to derive.
 
 ### importKey
 
-
-
-* <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
-
-
+- <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
+- <code>keyData</code>ArrayBuffer
 
-* <code>format</code>string
-
-  * Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
-
-* <code>keyData</code>ArrayBuffer
-
-* <code>algorithm</code>object
-
-  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
+- <code>algorithm</code>object
+  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
+- <code>extractable</code>bool
 
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
 ### exportKey
 
-
-
-* <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
-
-  * Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
-
-
+- <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
+  - Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
 
-
-* <code>format</code>string
-
-  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
-
-* <code>key</code>CryptoKey
-
-
+- <code>key</code>CryptoKey
 
 ### wrapKey
 
-
-
-* <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
-
-  * Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
-
-
+- <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
+  - Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
 
 #### Parameters
 
+- <code>format</code>string
+  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
 
+- <code>key</code>CryptoKey
 
-* <code>format</code>string
-
-  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
-
-* <code>key</code>CryptoKey
-
-* <code>wrappingKey</code>CryptoKey
-
-* <code>wrapAlgo</code>object
-
-  * Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
-
+- <code>wrappingKey</code>CryptoKey
 
+- <code>wrapAlgo</code>object
+  - Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
 
 ### unwrapKey
 
-
-
-* <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
-
-  * Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
-
-
+- <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
+  - Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
 
 #### Parameters
 
+- <code>format</code>string
+  - Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
+- <code>key</code>CryptoKey
 
-* <code>format</code>string
-
-  * Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>key</code>CryptoKey
-
-* <code>unwrappingKey</code>CryptoKey
+- <code>unwrappingKey</code>CryptoKey
 
-* <code>unwrapAlgo</code>object
+- <code>unwrapAlgo</code>object
+  - Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
-  * Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>unwrappedKeyAlgo</code>object
-
-  * Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
-
-* <code>extractable</code>bool
-
-* <code>keyUsages</code>Array
-
-  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
+- <code>unwrappedKeyAlgo</code>object
+  - Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
+- <code>extractable</code>bool
 
+- <code>keyUsages</code>Array
+  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
 ### timingSafeEqual
 
-
-
-* <code>timingSafeEqual(a, b)</code> : bool
-
-  * Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
-
-
+- <code>timingSafeEqual(a, b)</code> : bool
+  - Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
 
 #### Parameters
 
+- <code>a</code>ArrayBuffer | TypedArray
 
-
-* <code>a</code>ArrayBuffer | TypedArray
-
-* <code>b</code>ArrayBuffer | TypedArray
-
-
+- <code>b</code>ArrayBuffer | TypedArray
 
 ### Supported algorithms
 
@@ -511,8 +351,6 @@ A checkmark (✓) indicates that this feature is believed to be fully supported
 An x (✘) indicates that this feature is part of the specification but not implemented.<br/>
 If a feature only implements the operation partially, details are listed.
 
-
-
 | Algorithm                                          | sign()<br/>verify() | encrypt()<br/>decrypt() | digest() | deriveBits()<br/>deriveKey() | generateKey() | wrapKey()<br/>unwrapKey() | exportKey() | importKey() |
 | :------------------------------------------------- | :------------------ | :---------------------- | :------- | :--------------------------- | :------------ | :------------------------ | :---------- | :---------- |
 | RSASSA PKCS1 v1.5                                  | ✓                   |                         |          |                              | ✓             |                           | ✓           | ✓           |
@@ -536,24 +374,27 @@ If a feature only implements the operation partially, details are listed.
 | HKDF                                               |                     |                         |          | ✓                            |               |                           |             | ✓           |
 | PBKDF2                                             |                     |                         |          | ✓                            |               |                           |             | ✓           |
 
-
-
 **Footnotes:**
 
-1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves API](https://wicg.github.io/webcrypto-secure-curves).
+1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves
+   API](https://wicg.github.io/webcrypto-secure-curves).
 
-2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the Ed25519 curve in addition to the Secure Curves version. Since this algorithm is non-standard, note the following while using it:
+2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the
+   Ed25519 curve in addition to the Secure Curves version. Since this algorithm
+   is non-standard, note the following while using it:
+   - Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
+   - Unlike NodeJS, Cloudflare will not support raw import of private keys.
+   - The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
 
-   * Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
-   * Unlike NodeJS, Cloudflare will not support raw import of private keys.
-   * The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
+3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is
+   supported in Cloudflare Workers for interacting with legacy systems that
+   require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for
+   security.
 
-3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is supported in Cloudflare Workers for interacting with legacy systems that require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for security.
-
-***
+---
 
 ## Related resources
 
-* [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
-* [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
-* [Example: signing requests](/workers/examples/signing-requests/)
+- [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
+- [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
+- [Example: signing requests](/workers/examples/signing-requests/)
diff --git a/src/content/docs/workers/runtime-apis/webassembly/index.mdx b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
index d4a1cb8a2d546a5..492c0ae788ec4ea 100644
--- a/src/content/docs/workers/runtime-apis/webassembly/index.mdx
+++ b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
@@ -9,18 +9,18 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 [WebAssembly](https://webassembly.org/) (abbreviated Wasm) allows you to compile languages like [Rust](/workers/languages/rust/), Go, or C to a binary format that can run in a wide variety of environments, including [web browsers](https://developer.mozilla.org/en-US/docs/WebAssembly#browser_compatibility), Cloudflare Workers, and other WebAssembly runtimes.
 
 You can use WebAssembly to:
 
-* Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
-	:::note
-		`WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
-	:::
+- Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
+  :::note
+  `WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
+  :::
 
-* Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
+- Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
 
 Most programming languages can be compiled to Wasm, although support varies across languages and compilers. Guides are available for the following languages:
 
@@ -50,5 +50,5 @@ WASI is an earlier and more rapidly evolving set of standards than Wasm. WASI su
 
 ### Resources on WebAssembly
 
-* [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
-* [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
+- [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
+- [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
diff --git a/src/content/docs/workers/runtime-apis/websockets.mdx b/src/content/docs/workers/runtime-apis/websockets.mdx
index 6178ac08aa6b4b7..bf31fea43cc174c 100644
--- a/src/content/docs/workers/runtime-apis/websockets.mdx
+++ b/src/content/docs/workers/runtime-apis/websockets.mdx
@@ -14,10 +14,8 @@ WebSockets allow you to communicate in real time with your Cloudflare Workers se
 
 :::note
 
-
 If your application needs to coordinate among multiple WebSocket connections, such as a chat room or game match, you will need clients to send messages to a single-point-of-coordination. Durable Objects provide a single-point-of-coordination for Cloudflare Workers, and are often used in parallel with WebSockets to persist state over multiple clients and connections. In this case, refer to [Durable Objects](/durable-objects/) to get started, and prefer using the Durable Objects' extended [WebSockets API](/durable-objects/best-practices/websockets/).
 
-
 :::
 
 ## Constructor
@@ -39,148 +37,97 @@ let [client, server] = Object.values(new WebSocketPair());
 
 ### accept
 
-
-
-* <code>accept(options?)</code>
-
-  * Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
+- <code>accept(options?)</code>
+  - Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
 
 #### Parameters
 
-
-
-* `options` object optional
-
-  * An optional configuration object with the following properties:
-
-    * `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
-
-
+- `options` object optional
+  - An optional configuration object with the following properties:
+    - `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
 
 ### addEventListener
 
-
-
-* <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
-
-  * Add callback functions to be executed when an event has occurred on the WebSocket.
-
-
+- <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
+  - Add callback functions to be executed when an event has occurred on the WebSocket.
 
 #### Parameters
 
+- `event` WebSocketEvent
+  - The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
 
-
-* `event` WebSocketEvent
-
-  * The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
-
-* <code>callbackFunction(messageMessage)</code> Function
-
-  * A function to be called when the WebSocket responds to a specific event.
-
-
+- <code>callbackFunction(messageMessage)</code> Function
+  - A function to be called when the WebSocket responds to a specific event.
 
 ### close
 
-
-
-* <code>close(codenumber, reasonstring)</code>
-
-  * Close the WebSocket connection.
-
-
+- <code>close(codenumber, reasonstring)</code>
+  - Close the WebSocket connection.
 
 #### Parameters
 
+- <code>codeinteger</code> optional
+  - An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
 
-
-* <code>codeinteger</code> optional
-
-  * An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
-
-* <code>reasonstring</code> optional
-
-  * A human-readable string indicating why the WebSocket connection was closed.
-
-
+- <code>reasonstring</code> optional
+  - A human-readable string indicating why the WebSocket connection was closed.
 
 ### send
 
-
-
-* <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
-
-  * Send a message to the other WebSocket in this WebSocket pair.
-
-
+- <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
+  - Send a message to the other WebSocket in this WebSocket pair.
 
 #### Parameters
 
+- <code>messagestring</code>
+  - The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
 
-
-* <code>messagestring</code>
-
-  * The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
-
-
-
-***
+---
 
 ## Properties
 
 ### readyState
 
-* `readyState` number
+- `readyState` number
+  - Returns the current state of the WebSocket connection. Possible values:
 
-  * Returns the current state of the WebSocket connection. Possible values:
-
-    | Constant | Value | Description |
-    | --- | --- | --- |
-    | `WebSocket.CONNECTING` | `0` | The connection is not yet open. |
-    | `WebSocket.OPEN` | `1` | The connection is open and ready to communicate. |
-    | `WebSocket.CLOSING` | `2` | The connection is in the process of closing. |
-    | `WebSocket.CLOSED` | `3` | The connection is closed. |
+    | Constant               | Value | Description                                      |
+    | ---------------------- | ----- | ------------------------------------------------ |
+    | `WebSocket.CONNECTING` | `0`   | The connection is not yet open.                  |
+    | `WebSocket.OPEN`       | `1`   | The connection is open and ready to communicate. |
+    | `WebSocket.CLOSING`    | `2`   | The connection is in the process of closing.     |
+    | `WebSocket.CLOSED`     | `3`   | The connection is closed.                        |
 
 ### binaryType
 
-* `binaryType` string
-
-  * Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+- `binaryType` string
+  - Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
 
-***
+---
 
 ## Events
 
+- <code>close</code>* An event indicating the WebSocket has closed. The
+  `CloseEvent` includes `code` (number), `reason` (string), and `wasClean`
+  (boolean) properties.
 
+- <code>error</code>* An event indicating there was an error with the WebSocket.
 
-* <code>close</code>
-  * An event indicating the WebSocket has closed. The `CloseEvent` includes `code` (number), `reason` (string), and `wasClean` (boolean) properties.
-
-* <code>error</code>
-  * An event indicating there was an error with the WebSocket.
-
-* <code>message</code>
-  * An event indicating a new message received from the client, including the data passed by the client.
-
-
+- <code>message</code>
+  - An event indicating a new message received from the client, including the data passed by the client.
 
 :::note
-WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes).  If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
+WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes). If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
 :::
 
 ## Types
 
 ### Message
 
+- `data` any - The data passed back from the other WebSocket in your pair.
+- `type` string - Defaults to `message`.
 
-
-* `data` any - The data passed back from the other WebSocket in your pair.
-* `type` string - Defaults to `message`.
-
-
-
-***
+---
 
 ## Close behavior
 
@@ -190,10 +137,10 @@ If you still call `close()` inside the `close` event handler, the call is silent
 
 ```js
 server.addEventListener("close", (event) => {
-  // readyState is already CLOSED — no need to call server.close().
-  console.log(server.readyState); // WebSocket.CLOSED
-  console.log(event.code);        // 1000
-  console.log(event.wasClean);    // true
+	// readyState is already CLOSED — no need to call server.close().
+	console.log(server.readyState); // WebSocket.CLOSED
+	console.log(event.code); // 1000
+	console.log(event.wasClean); // true
 });
 ```
 
@@ -205,12 +152,12 @@ The automatic close behavior can interfere with WebSocket proxying, where a Work
 server.accept({ allowHalfOpen: true });
 
 server.addEventListener("close", (event) => {
-  // readyState is still CLOSING here, giving you time
-  // to coordinate the close on the other side.
-  console.log(server.readyState); // WebSocket.CLOSING
+	// readyState is still CLOSING here, giving you time
+	// to coordinate the close on the other side.
+	console.log(server.readyState); // WebSocket.CLOSING
 
-  // Manually close when ready.
-  server.close(event.code, "done");
+	// Manually close when ready.
+	server.close(event.code, "done");
 });
 ```
 
@@ -224,7 +171,7 @@ WebSockets created with `new WebSocket(url)` always auto-reply to Close frames a
 
 On compatibility dates before `2026-04-07` (or with the `web_socket_manual_reply_to_close` flag), receiving a Close frame leaves the WebSocket in `CLOSING` state, and your code must call `close()` to complete the handshake. Failing to do so can result in `1006` abnormal closure errors on the client.
 
-***
+---
 
 ## Binary messages
 
@@ -236,7 +183,7 @@ The `binaryType` property itself is always available. To opt back into `ArrayBuf
 
 ```js
 const resp = await fetch("https://example.com", {
-  headers: { Upgrade: "websocket" },
+	headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -245,11 +192,11 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-  if (typeof event.data === "string") {
-    // Text frame.
-  } else {
-    // event.data is an ArrayBuffer because we set binaryType above.
-  }
+	if (typeof event.data === "string") {
+		// Text frame.
+	} else {
+		// event.data is an ArrayBuffer because we set binaryType above.
+	}
 });
 ```
 
@@ -276,9 +223,9 @@ This flag has no effect on the Durable Object hibernatable WebSocket [`webSocket
 
 :::
 
-***
+---
 
 ## Related resources
 
-* [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
-* [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
+- [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
+- [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
diff --git a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
index 31e081797dd1ada..0ba52cb42d3e81a 100644
--- a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
+++ b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
@@ -14,10 +14,7 @@ Full-stack applications are web applications which are span both the client and
 
 The following full-stack frameworks are natively supported by Workers:
 
-<DirectoryListing
-	folder="workers/framework-guides/web-apps"
-	tag="full-stack"
-/>
+<DirectoryListing folder="workers/framework-guides/web-apps" tag="full-stack" />
 <DirectoryListing
 	folder="workers/framework-guides/web-apps/more-web-frameworks"
 	tag="full-stack"
diff --git a/src/content/docs/workers/testing/miniflare/storage/cache.md b/src/content/docs/workers/testing/miniflare/storage/cache.md
index 78aac412fb542af..c7c385b4cbe8025 100644
--- a/src/content/docs/workers/testing/miniflare/storage/cache.md
+++ b/src/content/docs/workers/testing/miniflare/storage/cache.md
@@ -86,7 +86,9 @@ console.log(await res.text()); // 2
 You can programmatically purge all entries from a cache using the `purgeCache` method on the `Miniflare` instance. This is useful during development when cached assets need to be cleared without restarting the instance:
 
 ```js
-const mf = new Miniflare({ /* options */ });
+const mf = new Miniflare({
+	/* options */
+});
 
 // Purge the default cache and get the number of entries purged
 const count = await mf.purgeCache();
diff --git a/src/content/docs/workers/testing/vitest-integration/recipes.mdx b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
index 79fb21b23ea73f1..d125b33d9e53931 100644
--- a/src/content/docs/workers/testing/vitest-integration/recipes.mdx
+++ b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
@@ -30,4 +30,4 @@ Recipes are examples that help demonstrate how to write unit tests and integrati
 - [Resolving modules with Vite Dependency Pre-Bundling](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/module-resolution)
 - [Mocking Workers AI and Vectorize bindings in unit tests](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/ai-vectorize)
 - [Tests using the Images binding](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/images)
-- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
\ No newline at end of file
+- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
diff --git a/src/content/docs/workers/vite-plugin/tutorial.mdx b/src/content/docs/workers/vite-plugin/tutorial.mdx
index c5b6e9446a92aa4..ef7f05b8c086add 100644
--- a/src/content/docs/workers/vite-plugin/tutorial.mdx
+++ b/src/content/docs/workers/vite-plugin/tutorial.mdx
@@ -205,6 +205,7 @@ This opts out of interpreting the `Sec-Fetch-Mode` header.
 ```
 
 </WranglerConfig>
+
 :::
 
 ### Call the API from the client
diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx
index 8b28f295cdc13b8..ccabcb8262755a1 100644
--- a/src/content/docs/workers/wrangler/api.mdx
+++ b/src/content/docs/workers/wrangler/api.mdx
@@ -50,9 +50,7 @@ const result = await experimental_generateTypes(options);
 ### Parameters
 
 - `options` <Type text="object" /> <MetaInfo text="optional" />
-
   - Optional options object mirroring the `wrangler types` CLI flags:
-
     - `config` `string | string[]`
 
       Path to the Wrangler configuration file to use. Can be an array for multi-config type resolution.
@@ -90,19 +88,15 @@ const result = await experimental_generateTypes(options);
 `experimental_generateTypes()` returns a `Promise` resolving to an object containing the following fields:
 
 - `content` `string`
-
   - Combined formatted output containing all generated sections, including headers and both env and runtime types.
 
 - `env` `string | null`
-
   - Generated environment and bindings types, or `null` when env types are excluded.
 
 - `path` `string`
-
   - Target declaration file path associated with this generation run.
 
 - `runtime` `string | null`
-
   - Generated runtime types, or `null` when runtime types are excluded.
 
 ### Usage
@@ -506,22 +500,22 @@ The bindings supported by `getPlatformProxy` are:
     For example, you might have the following binding in a Wrangler configuration file read by `getPlatformProxy`.
 
     <WranglerConfig>
-            
-                ```jsonc
-                {
-                  "durable_objects": {
-                    "bindings": [
-                      {
-                        "name": "MyDurableObject",
-                        "class_name": "MyDurableObject",
-                        "script_name": "external-do-worker"
+                
+                    ```jsonc
+                    {
+                      "durable_objects": {
+                        "bindings": [
+                          {
+                            "name": "MyDurableObject",
+                            "class_name": "MyDurableObject",
+                            "script_name": "external-do-worker"
+                          }
+                        ]
                       }
-                    ]
-                  }
-                }
-                ```
-            
-                </WranglerConfig>
+                    }
+                    ```
+                
+                    </WranglerConfig>
 
     You will need to declare your Durable Object `"MyDurableObject"` in another Worker, called `external-do-worker` in this example.
 
@@ -541,14 +535,14 @@ The bindings supported by `getPlatformProxy` are:
     That Worker also needs a Wrangler configuration file that looks like this:
 
     <WranglerConfig>
-                    ```json
-                    {
-                    	"name": "external-do-worker",
-                    	"main": "src/index.ts",
-                    	"compatibility_date": "XXXX-XX-XX"
-                    }
-                    ```
-                    </WranglerConfig>
+                        ```json
+                        {
+                        	"name": "external-do-worker",
+                        	"main": "src/index.ts",
+                        	"compatibility_date": "XXXX-XX-XX"
+                        }
+                        ```
+                        </WranglerConfig>
 
     If you are not using RPC with your Durable Object, you can run a separate Wrangler dev session alongside your framework development server.
 
diff --git a/src/content/docs/workers/wrangler/commands/r2.mdx b/src/content/docs/workers/wrangler/commands/r2.mdx
index 60266e3b8e29b81..fb437a18a9717a9 100644
--- a/src/content/docs/workers/wrangler/commands/r2.mdx
+++ b/src/content/docs/workers/wrangler/commands/r2.mdx
@@ -10,7 +10,6 @@ import { Render } from "~/components";
 
 Manage your [R2](/r2/) configurations using Wrangler.
 
-
 <Render file="wrangler-commands/r2" product="workers" />
 
 ## R2 SQL
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
index f32639e194e9391..d19eda7c7872fca 100644
--- a/src/content/docs/workers/wrangler/configuration.mdx
+++ b/src/content/docs/workers/wrangler/configuration.mdx
@@ -1839,26 +1839,26 @@ A common example of using a redirected configuration is where a custom build too
 - First, the user writes code that uses Cloudflare Workers resources, configured via a user's Wrangler configuration file like the following:
 
   <WranglerConfig>
-
-  ```jsonc
-  {
-  	"$schema": "./node_modules/wrangler/config-schema.json",
-  	"name": "my-worker",
-  	"main": "src/index.ts",
-  	"vars": {
-  		"MY_VARIABLE": "production variable",
-  	},
-  	"env": {
-  		"staging": {
-  			"vars": {
-  				"MY_VARIABLE": "staging variable",
-  			},
-  		},
-  	},
-  }
-  ```
-
-  </WranglerConfig>
+  
+    ```jsonc
+    {
+    	"$schema": "./node_modules/wrangler/config-schema.json",
+    	"name": "my-worker",
+    	"main": "src/index.ts",
+    	"vars": {
+    		"MY_VARIABLE": "production variable",
+    	},
+    	"env": {
+    		"staging": {
+    			"vars": {
+    				"MY_VARIABLE": "staging variable",
+    			},
+    		},
+    	},
+    }
+    ```
+  
+    </WranglerConfig>
 
   This configuration points `main` at the user's code entry-point and defines the `MY_VARIABLE` variable in two different environments.
 
@@ -1872,8 +1872,8 @@ A common example of using a redirected configuration is where a custom build too
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>
-  	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
-  </FileTree>
+    	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
+    </FileTree>
 
 The generated `dist/wrangler.jsonc` might contain:
 
@@ -1896,4 +1896,4 @@ And the `.wrangler/deploy/config.json` contains the path to the generated config
 {
 	"configPath": "../../dist/wrangler.jsonc"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/docs/workers/wrangler/custom-builds.mdx b/src/content/docs/workers/wrangler/custom-builds.mdx
index 0b63ae3bd2a8037..e22e4bc6c269534 100644
--- a/src/content/docs/workers/wrangler/custom-builds.mdx
+++ b/src/content/docs/workers/wrangler/custom-builds.mdx
@@ -21,15 +21,12 @@ Wrangler runs [esbuild](https://esbuild.github.io/) by default as part of the `d
 Custom builds are configured by adding a `[build]` section in your [Wrangler configuration file](/workers/wrangler/configuration/), and using the following options for configuring your custom build.
 
 - `command` <Type text="string" /> <MetaInfo text="optional" />
-
   - The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used. This command will be run as part of `wrangler dev` and `npx wrangler deploy`.
 
 - `cwd` <Type text="string" /> <MetaInfo text="optional" />
-
   - The directory in which the command is executed.
 
 - `watch_dir` <Type text="string | string\[]" /> <MetaInfo text="optional" />
-
   - The directory to watch for changes while using `wrangler dev`. Defaults to the current working directory.
 
 Example:
@@ -54,12 +51,12 @@ When Wrangler runs your custom build command, it sets the `WRANGLER_COMMAND` env
 
 The possible values are:
 
-| Value              | Wrangler command triggered               |
-| ------------------ | ---------------------------------------- |
-| `dev`              | `wrangler dev`                           |
-| `deploy`           | `wrangler deploy`                        |
-| `versions upload`  | `wrangler versions upload`               |
-| `types`            | `wrangler types`                         |
+| Value             | Wrangler command triggered |
+| ----------------- | -------------------------- |
+| `dev`             | `wrangler dev`             |
+| `deploy`          | `wrangler deploy`          |
+| `versions upload` | `wrangler versions upload` |
+| `types`           | `wrangler types`           |
 
 For example, you can use this to apply different build settings for development and production:
 
diff --git a/src/content/docs/workers/wrangler/deprecations.mdx b/src/content/docs/workers/wrangler/deprecations.mdx
index 3b4d23ccc8c99eb..ab606324004172b 100644
--- a/src/content/docs/workers/wrangler/deprecations.mdx
+++ b/src/content/docs/workers/wrangler/deprecations.mdx
@@ -83,82 +83,89 @@ This no longer has any effect, after the [rollout of Workers Standard Pricing](h
 
 Wrangler v2 introduces new fields for configuration and new features for developing and deploying a Worker, while deprecating some redundant fields.
 
-* `wrangler.toml` is no longer mandatory.
-* `dev` and `publish` accept CLI arguments.
-* `tail` can be run on arbitrary Worker names.
-* `init` creates a project boilerplate.
-* JSON bindings for `vars`.
-* Local mode for `wrangler dev`.
-* Module system (for both modules and service worker format Workers).
-* DevTools.
-* TypeScript support.
-* Sharing development environment on the Internet.
-* Wider platform compatibility.
-* Developer hotkeys.
-* Better configuration validation.
+- `wrangler.toml` is no longer mandatory.
+- `dev` and `publish` accept CLI arguments.
+- `tail` can be run on arbitrary Worker names.
+- `init` creates a project boilerplate.
+- JSON bindings for `vars`.
+- Local mode for `wrangler dev`.
+- Module system (for both modules and service worker format Workers).
+- DevTools.
+- TypeScript support.
+- Sharing development environment on the Internet.
+- Wider platform compatibility.
+- Developer hotkeys.
+- Better configuration validation.
 
 The following video describes some of the major changes in Wrangler v2, and shows you how Wrangler v2 can help speed up your workflow.
 
-<div style="position: relative; padding-top: 56.25%;"><iframe src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600" style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;" allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;" allowfullscreen="true"></iframe></div>
+<div style="position: relative; padding-top: 56.25%;">
+	<iframe
+		src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+		allowfullscreen="true"
+	></iframe>
+</div>
 
 ### Common deprecations
 
 Refer to the following list for common fields that are no longer required.
 
-* `type` is no longer required. Wrangler will infer the correct project type automatically.
-* `zone_id` is no longer required. It can be deduced from the routes directly.
-* `build.upload.format` is no longer used. The format is now inferred automatically from the code.
-* `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
-* `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
-* `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
+- `type` is no longer required. Wrangler will infer the correct project type automatically.
+- `zone_id` is no longer required. It can be deduced from the routes directly.
+- `build.upload.format` is no longer used. The format is now inferred automatically from the code.
+- `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
+- `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
+- `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
   Here are the Wrangler v1 commands that are no longer supported:
-* `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
-* `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
-* `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
-* `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
-* `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
+- `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
+- `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
+- `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
+- `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
+- `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
 
 #### New fields
 
 These are new fields that can be added to your [Wrangler configuration file](/workers/wrangler/configuration/).
 
-* **`main`**: `string`, optional
+- **`main`**: `string`, optional
 
   The `main` field is used to specify an entry point to the Worker. It may be in the established service worker format, or the newer, preferred modules format. An entry point is now explicitly required, and can be configured either via the `main` field, or passed directly as a command line, for example, `wrangler dev index.js`. This field replaces the legacy `build.upload.main` field (which only applied to modules format Workers).
 
-* **`rules`**: `array`, optional
+- **`rules`**: `array`, optional
 
   The `rules` field is an array of mappings between module types and file patterns. It instructs Wrangler to interpret specific files differently than JavaScript. For example, this is useful for reading text-like content as text files, or compiled WASM as ready to instantiate and execute. These rules can apply to Workers of both the established service worker format, and the newer modules format. This field replaces the legacy `build.upload.rules` field (which only applied to modules format Workers).
 
-{/* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
+{/\* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
 
-  The `legacy_env` field toggles how environments are handled by `wrangler`.
+The `legacy_env` field toggles how environments are handled by `wrangler`.
 
-  - When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
-  - When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
-    Read more at (ref:)[] --> */}
+- When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
+- When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
+  Read more at (ref:)[] --> \*/}
 
-{/* <!-- - **`services`**: TODO
+{/\* <!-- - **`services`**: TODO
 
 - **`node-compat`**: TODO
 
-- **`public`**: TODO --> */}
+- **`public`**: TODO --> \*/}
 
 #### Non-mandatory fields
 
 A few configuration fields which were previously required, are now optional in particular situations. They can either be inferred, or added as an optimization. No fields are required anymore when starting with Wrangler v2, and you can gradually add configuration as the need arises.
 
-* **`name`**: `string`
+- **`name`**: `string`
 
   The `name` configuration field is now not required for `wrangler dev`, or any of the `wrangler kv:*` commands. Further, it can also be passed as a command line argument as `--name <name>`. It is still required for `wrangler deploy`.
 
-* **`account_id`**: `string`
+- **`account_id`**: `string`
 
   The `account_id` field is not required for any of the commands. Any relevant commands will check if you are logged in, and if not, will prompt you to log in. Once logged in, it will use your account ID and will not prompt you again until your login session expires. If you have multiple account IDs, you will be presented with a list of accounts to choose from.
 
   You can still configure `account_id` in your Wrangler file, or as an environment variable `CLOUDFLARE_ACCOUNT_ID`. This makes startup faster and bypasses the list of choices if you have multiple IDs. The `CLOUDFLARE_API_TOKEN` environment variable is also useful for situations where it is not possible to login interactively. To learn more, visit [Running in CI/CD](/workers/ci-cd/external-cicd/).
 
-* **`workers_dev`** `boolean`, default: `true` when no routes are present
+- **`workers_dev`** `boolean`, default: `true` when no routes are present
 
   The `workers_dev` field is used to indicate that the Worker should be published to a `*.workers.dev` subdomain. For example, for a Worker named `my-worker` and a previously configured `*.workers.dev` subdomain `username`, the Worker will get published to `my-worker.username.workers.dev.com`. This field is not mandatory, and defaults to `true` when `route` or `routes` are not configured. When routes are present, it defaults to `false`. If you want to neither publish it to a `*.workers.dev` subdomain nor any routes, set `workers_dev` to `false`. This useful when you are publishing a Worker as a standalone service that can only be accessed from another Worker with (`services`).
 
@@ -166,27 +173,26 @@ A few configuration fields which were previously required, are now optional in p
 
 A few configuration fields are deprecated, but their presence is not a breaking change yet. It is recommended to read the warning messages and follow the instructions to migrate to the new configuration. They will be removed and stop working in a future version.
 
-* **`zone_id`**: `string`, deprecated
+- **`zone_id`**: `string`, deprecated
 
   The `zone_id` field is deprecated and will be removed in a future release. It is now inferred from `route`/`routes`, and optionally from `dev.host` when using `wrangler dev`. This also makes it simpler to deploy a single Worker to multiple domains.
 
-* **`build.upload`**: `object`, deprecated
+- **`build.upload`**: `object`, deprecated
 
   The `build.upload` field is deprecated and will be removed in a future release. Its usage results in a warning with suggestions on rewriting the configuration file to remove the warnings.
-
-  * `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
-  * `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
-  * `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
+  - `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
+  - `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
+  - `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
 
 #### Deprecated fields (breaking)
 
 A few configuration fields are deprecated and will not work as expected anymore. It is recommended to read the error messages and follow the instructions to migrate to the new configuration.
 
-* **`site.entry-point`**: `string`, deprecated
+- **`site.entry-point`**: `string`, deprecated
 
   The `site.entry-point` configuration was used to specify an entry point for Workers with a `[site]` configuration. This has been replaced by the top-level `main` field.
 
-* **`type`**: `rust` | `javascript` | `webpack`, deprecated
+- **`type`**: `rust` | `javascript` | `webpack`, deprecated
 
   The `type` configuration was used to specify the type of Worker. It has since been made redundant and is now inferred from usage. If you were using `type = "webpack"` (and the optional `webpack_config` field), you should read the [webpack migration guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to modify your project and use a custom build instead.
 
@@ -226,11 +232,11 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 ### Other deprecated behavior
 
-* Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
+- Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
 
-* Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
+- Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
 
-* Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
+- Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
 
   ```
   project
@@ -244,7 +250,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
   import SomeDependency from "some-dependency.js";
 
   addEventListener("fetch", (event) => {
-    // ...
+  	// ...
   });
   ```
 
@@ -259,8 +265,8 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Commands
 
-| Command     | v1 | v2 | Notes                                          |
-| ----------- | -- | -- | ---------------------------------------------- |
+| Command     | v1  | v2  | Notes                                          |
+| ----------- | --- | --- | ---------------------------------------------- |
 | `publish`   | ✅  | ✅  |                                                |
 | `dev`       | ✅  | ✅  |                                                |
 | `preview`   | ✅  | ❌  | Removed, use `dev` instead.                    |
@@ -271,7 +277,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 | `route`     | ✅  | ❌  | Removed, use `publish` instead.                |
 | `tail`      | ✅  | ✅  |                                                |
 | `kv`        | ✅  | ✅  |                                                |
-| `r2`        | 🚧 | ✅  | Introduced in Wrangler v1.19.8.                |
+| `r2`        | 🚧  | ✅  | Introduced in Wrangler v1.19.8.                |
 | `pages`     | ❌  | ✅  |                                                |
 | `config`    | ✅  | ❓  |                                                |
 | `login`     | ✅  | ✅  |                                                |
@@ -282,15 +288,15 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Configuration
 
-| Property              | v1 | v2 | Notes                                                                                                                                            |
-| --------------------- | -- | -- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Property              | v1  | v2  | Notes                                                                                           |
+| --------------------- | --- | --- | ----------------------------------------------------------------------------------------------- |
 | `type = "webpack"`    | ✅  | ❌  | Removed, refer to [this guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to migrate. |
-| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                                                                   |
-| `type = "javascript"` | ✅  | 🚧 | No longer required, can be omitted.                                                                                                              |
+| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                  |
+| `type = "javascript"` | ✅  | 🚧  | No longer required, can be omitted.                                                             |
 
 #### Features
 
-| Feature    | v1 | v2 | Notes                                                                                                                                                                                                 |
-| ---------- | -- | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Feature    | v1  | v2  | Notes                                                                                                                                                                                                 |
+| ---------- | --- | --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | TypeScript | ❌  | ✅  | You can give wrangler a TypeScript file, and it will automatically transpile it to JavaScript using [`esbuild`](https://github.com/evanw/esbuild) under-the-hood.                                     |
 | Local mode | ❌  | ✅  | `wrangler dev --local` will run your Worker on your local machine instead of on our network. This is powered by [Miniflare](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare/). |
diff --git a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
index 8092bb1422993dd..6f633bb98248e76 100644
--- a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
+++ b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
@@ -12,10 +12,8 @@ There are no special instructions for migrating from Wrangler v2 to v3. You shou
 
 :::caution
 
-
 If you tried to update to Wrangler v3 prior to v3.3, you may have experienced some compatibility issues with older operating systems. Please try again with the latest v3 where those have been resolved.
 
-
 :::
 
 ## Deprecations
diff --git a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
index 5c0712ab06b89e5..a700b3c6cef0bbc 100644
--- a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
+++ b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
@@ -12,7 +12,13 @@ products:
   - workers
 ---
 
-import { Render, Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
+import {
+	Render,
+	Type,
+	MetaInfo,
+	WranglerConfig,
+	DashButton,
+} from "~/components";
 
 <Render file="wrangler-v1-deprecation" product="workers" />
 
diff --git a/src/content/docs/workflows/build/index.mdx b/src/content/docs/workflows/build/index.mdx
index 317e4c6fd68d3d8..d37b306c71a2e1e 100644
--- a/src/content/docs/workflows/build/index.mdx
+++ b/src/content/docs/workflows/build/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/build/test-workflows.mdx b/src/content/docs/workflows/build/test-workflows.mdx
index bf533e4a14be140..8752df04fd942ab 100644
--- a/src/content/docs/workflows/build/test-workflows.mdx
+++ b/src/content/docs/workflows/build/test-workflows.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 11
 products:
   - workflows
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workflows/examples/agents.mdx b/src/content/docs/workflows/examples/agents.mdx
index 4395885fbb20f1b..dabdf0389fd185b 100644
--- a/src/content/docs/workflows/examples/agents.mdx
+++ b/src/content/docs/workflows/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workflows
----
\ No newline at end of file
+---
diff --git a/src/content/docs/workflows/examples/backup-d1.mdx b/src/content/docs/workflows/examples/backup-d1.mdx
index a22c45b46fda50d..1ef6fc225a7cfea 100644
--- a/src/content/docs/workflows/examples/backup-d1.mdx
+++ b/src/content/docs/workflows/examples/backup-d1.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Export a D1 database into R2 storage with Workflows
 products: [d1, r2]
 tags:
diff --git a/src/content/docs/workflows/examples/send-invoices.mdx b/src/content/docs/workflows/examples/send-invoices.mdx
index 290cf8159582787..88c4d7c81871595 100644
--- a/src/content/docs/workflows/examples/send-invoices.mdx
+++ b/src/content/docs/workflows/examples/send-invoices.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Send invoice when shopping cart is checked out and paid for
 products: [d1, email-routing]
 tags:
diff --git a/src/content/docs/workflows/examples/twilio.mdx b/src/content/docs/workflows/examples/twilio.mdx
index f9a9331974d6ad1..08df323ebf3258d 100644
--- a/src/content/docs/workflows/examples/twilio.mdx
+++ b/src/content/docs/workflows/examples/twilio.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Integrate Workflows with Twilio. Learn how to receive and send text messages and phone calls via APIs and Webhooks.
 products: [workers]
 pcx_content_type: example
diff --git a/src/content/docs/workflows/examples/wait-for-event.mdx b/src/content/docs/workflows/examples/wait-for-event.mdx
index 95cc28394e9e6ec..0e46962c459c1ab 100644
--- a/src/content/docs/workflows/examples/wait-for-event.mdx
+++ b/src/content/docs/workflows/examples/wait-for-event.mdx
@@ -1,5 +1,4 @@
 ---
-
 summary: Implement a Cloudflare Workflow that processes user-uploaded images, awaits human approval, and performs AI-based image tagging upon approval.
 tags:
   - Typescript
@@ -13,7 +12,7 @@ products:
   - workflows
 ---
 
-import {  GitHubCode, WranglerConfig } from "~/components"
+import { GitHubCode, WranglerConfig } from "~/components";
 
 This example demonstrates how to use the `waitForEvent()` API in Cloudflare Workflows to introduce a human-in-the-loop step. The Workflow is triggered by an image upload, during which metadata is stored in a D1 database. The Workflow then waits for user approval, and upon approval, it uses Workers AI to generate image tags, which are stored in the database. An accompanying Next.js frontend application facilitates the image upload and approval process.
 
@@ -45,12 +44,12 @@ The `index.ts` file defines the core logic of the Cloudflare Workflow responsibl
 For the complete implementation of the `index.ts` file, please refer to the [GitHub repository](https://github.com/cloudflare/docs-examples/blob/main/workflows/waitForEvent/workflow/src/index.ts).
 
 <GitHubCode
-  repo="cloudflare/docs-examples"
-  file="workflows/waitForEvent/workflow/src/index.ts"
-  commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
-  lang="ts"
+	repo="cloudflare/docs-examples"
+	file="workflows/waitForEvent/workflow/src/index.ts"
+	commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
+	lang="ts"
 	lines="17-57"
-  useTypeScriptExample={true}
+	useTypeScriptExample={true}
 />
 
 ## Workflow wrangler.jsonc
diff --git a/src/content/docs/workflows/observability/index.mdx b/src/content/docs/workflows/observability/index.mdx
index 9fb63d677e9caec..8a5a7d7938f5dfc 100644
--- a/src/content/docs/workflows/observability/index.mdx
+++ b/src/content/docs/workflows/observability/index.mdx
@@ -5,11 +5,11 @@ pcx_content_type: navigation
 sidebar:
   order: 5
   group:
-   hideIndex: true
+    hideIndex: true
 products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/python/bindings.mdx b/src/content/docs/workflows/python/bindings.mdx
index ea31fe2f488a996..a861b88223cc0f3 100644
--- a/src/content/docs/workflows/python/bindings.mdx
+++ b/src/content/docs/workflows/python/bindings.mdx
@@ -153,7 +153,7 @@ class Default(WorkerEntrypoint):
 Send an event to a workflow instance.
 
 - <code>send_event(options)</code>* `type` - the type of event to send to the
-  workflow instance. * `payload` - the payload to send to the workflow instance.
+  workflow instance. \* `payload` - the payload to send to the workflow instance.
 
 ```python
 from pyodide.ffi import to_js
diff --git a/src/content/docs/workflows/reference/changelog.mdx b/src/content/docs/workflows/reference/changelog.mdx
index beba6e99cb7a9fe..00df519b89f7276 100644
--- a/src/content/docs/workflows/reference/changelog.mdx
+++ b/src/content/docs/workflows/reference/changelog.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: changelog
-title: Release notes 
+title: Release notes
 description: Latest release notes and changes for Cloudflare Workflows.
 release_notes_file_name:
   - workflows
@@ -10,7 +10,7 @@ products:
   - workflows
 ---
 
-import { ProductReleaseNotes } from "~/components"
+import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /data/changelogs/workflows.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workflows/reference/glossary.mdx b/src/content/docs/workflows/reference/glossary.mdx
index e19733552053c95..c6bc3d0908b0a9d 100644
--- a/src/content/docs/workflows/reference/glossary.mdx
+++ b/src/content/docs/workflows/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Glossary } from "~/components"
+import { Glossary } from "~/components";
 
 Review the definitions for terms used across Cloudflare's Workflows documentation.
 
diff --git a/src/content/docs/workflows/reference/index.mdx b/src/content/docs/workflows/reference/index.mdx
index 89abc260ef45793..6df95f6daddcdc4 100644
--- a/src/content/docs/workflows/reference/index.mdx
+++ b/src/content/docs/workflows/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/reference/pricing.mdx b/src/content/docs/workflows/reference/pricing.mdx
index db0a2a5aa7c5f2e..283b87cdbd8653d 100644
--- a/src/content/docs/workflows/reference/pricing.mdx
+++ b/src/content/docs/workflows/reference/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 :::note
 
@@ -18,19 +18,19 @@ Workflows is included in both the Free and Paid [Workers plans](/workers/platfor
 
 Workflows pricing is identical to [Workers Standard pricing](/workers/platform/pricing/#workers) and are billed on three dimensions:
 
-* **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
-* **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
-* **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
+- **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
+- **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
+- **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
 
 A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle, does not incur CPU time.
 
 ### Workflows Pricing
 
-| Unit | Workers Free | Workers Paid |
-|------|--------------|--------------|
-| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers)| 10 million included per month + $0.30 per additional million	|
-| CPU time (ms) | 10 milliseconds of CPU time per invocation | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
-| Storage (GB-mo) | 1GB | 1GB included per month + $0.20/ GB-month |
+| Unit                | Workers Free                                                                        | Workers Paid                                                                                   |
+| ------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers) | 10 million included per month + $0.30 per additional million                                   |
+| CPU time (ms)       | 10 milliseconds of CPU time per invocation                                          | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
+| Storage (GB-mo)     | 1GB                                                                                 | 1GB included per month + $0.20/ GB-month                                                       |
 
 :::note[CPU limits]
 
@@ -48,10 +48,10 @@ Storage billing for Workflows will go live on September 15th, 2025.
 
 Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to [Durable Objects SQL storage](/durable-objects/platform/pricing/#sqlite-storage-backend). A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).
 
-* Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
-* By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
-* When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
-* Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
+- Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
+- By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
+- When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
+- Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
 
 An instance that attempts to store state when your have reached the storage limit on the Free plan will cause an error to be thrown.
 
diff --git a/src/content/docs/workflows/reference/wrangler-commands.mdx b/src/content/docs/workflows/reference/wrangler-commands.mdx
index b80050771f16411..2ad49f1ed36f4a1 100644
--- a/src/content/docs/workflows/reference/wrangler-commands.mdx
+++ b/src/content/docs/workflows/reference/wrangler-commands.mdx
@@ -8,6 +8,6 @@ products:
   - workflows
 ---
 
-import {WranglerNamespace} from "~/components";
+import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="workflows"/>
+<WranglerNamespace namespace="workflows" />
diff --git a/src/content/docs/workflows/videos.mdx b/src/content/docs/workflows/videos.mdx
index 0b45561d7cdf80d..8d5a6926d7c97fa 100644
--- a/src/content/docs/workflows/videos.mdx
+++ b/src/content/docs/workflows/videos.mdx
@@ -11,9 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-    <LinkCard
-        title="Build an application using Cloudflare Workflows"
-        description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
-        href="/learning-paths/workflows-course/series/workflows-1/"
-    />
+	<LinkCard
+		title="Build an application using Cloudflare Workflows"
+		description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
+		href="/learning-paths/workflows-course/series/workflows-1/"
+	/>
 </CardGrid>
diff --git a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
index 07719d8b84e7244..e537c733bce84dd 100644
--- a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
+++ b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
@@ -6,7 +6,6 @@ products:
 title: Data layer compatibility mode
 sidebar:
   order: 3
-
 ---
 
 Cloudflare Zaraz offers backwards compatibility with the `dataLayer` function found in tag management software, used to track events and other parameters. This way you can keep your current implementation and Cloudflare Zaraz will automatically collect your events.
@@ -28,10 +27,10 @@ Events will only be sent to Zaraz if your pushed object includes an `event` key.
 
 ```js
 dataLayer.push({
-  event: 'purchase',
-  price: '24',
-  currency: 'USD',
-  transactionID: '12345678',
+	event: "purchase",
+	price: "24",
+	currency: "USD",
+	transactionID: "12345678",
 });
 ```
 
@@ -41,6 +40,6 @@ Because Zaraz converts the `dataLayer.push()` call to `zaraz.track()`, creating
 
 | Rule type    | Variable name | Match operation | Match string |
 | ------------ | ------------- | --------------- | ------------ |
-| *Match rule* | *Event Name*  | *Equals*        | `purchase`   |
+| _Match rule_ | _Event Name_  | _Equals_        | `purchase`   |
 
 We do not recommend using `dataLayer`. However, as many websites employ it, Cloudflare Zaraz has this automatic translation layer that converts it to `zaraz.track()`.
diff --git a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
index 571d8120641dd8c..359716b4e8520a1 100644
--- a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
+++ b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: Use Zaraz on domains not proxied by Cloudflare
-
 ---
 
 You can load Zaraz on domains that are not proxied through Cloudflare. However, you will need to create a separate domain, or subdomain, proxied by Cloudflare (also [known as orange-clouded](https://community.cloudflare.com/t/step-3-enabling-the-orange-cloud/52715) domains), and load the script from it:
diff --git a/src/content/docs/zaraz/advanced/google-consent-mode.mdx b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
index 32b7951c7c0b104..730a6cf363a3bba 100644
--- a/src/content/docs/zaraz/advanced/google-consent-mode.mdx
+++ b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
@@ -6,7 +6,6 @@ products:
 title: Google Consent Mode
 sidebar:
   order: 4
-
 ---
 
 ## Background
@@ -15,7 +14,7 @@ sidebar:
 
 You can also use Google Analytics and Google Ads without cookies by selecting **Permissions** and disabling **Access client key-value store**.
 
-***
+---
 
 ## Consent Mode v2
 
@@ -28,12 +27,12 @@ Often websites will want to set a default consent status that denies all categor
 If that is not what your website needs, and instead you want to set the default consent status in a more granular way, use the reserved `google_consent_default` property:
 
 ```js
-zaraz.set("google_consent_default",  {
-  'ad_storage': 'denied',
-  'ad_user_data': 'denied',
-  'ad_personalization': 'denied',
-  'analytics_storage': 'denied'
-})
+zaraz.set("google_consent_default", {
+	ad_storage: "denied",
+	ad_user_data: "denied",
+	ad_personalization: "denied",
+	analytics_storage: "denied",
+});
 ```
 
 After the above code is executed, the consent status will be saved to `localStorage` and will be included with every subsequent Zaraz event.
@@ -45,12 +44,12 @@ Note that the code should be included as part of your website HTML code, usually
 After the user has provided their consent preferences you can set the new status using the reserved `google_consent_update` property. If you are using the Zaraz Consent Management Platform, you can use the [Consent Choices Updated event](/zaraz/consent-management/api/#consent-choices-updated) to know when to update the Google Consent status.
 
 ```js
-zaraz.set("google_consent_update",  {
-  'ad_storage': 'granted',
-  'ad_user_data': 'denied',
-  'ad_personalization': 'granted',
-  'analytics_storage': 'denied'
-})
+zaraz.set("google_consent_update", {
+	ad_storage: "granted",
+	ad_user_data: "denied",
+	ad_personalization: "granted",
+	analytics_storage: "denied",
+});
 ```
 
 All subsequent events will include the information about both the default and the updated consent status.
diff --git a/src/content/docs/zaraz/advanced/import-export.mdx b/src/content/docs/zaraz/advanced/import-export.mdx
index 450eddcbc977e9a..578d82719d2e9dc 100644
--- a/src/content/docs/zaraz/advanced/import-export.mdx
+++ b/src/content/docs/zaraz/advanced/import-export.mdx
@@ -6,7 +6,6 @@ products:
 title: Configuration Import & Export
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To export your Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Advanced**.
 3. Click "Export" to download your configuration.
 
@@ -27,16 +27,15 @@ To export your Zaraz configuration:
 
 :::caution
 
-
 Importing a Zaraz configuration replaces your existing configuration, meaning that any information you did not back up could be lost. Consider exporting your existing configuration before importing a new one.
 
-
 :::
 
 To import a Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Advanced**.
 3. Click **Browse** to select your configuration file, and **Import** to import it.
diff --git a/src/content/docs/zaraz/advanced/index.mdx b/src/content/docs/zaraz/advanced/index.mdx
index 9b8a538527e1ac3..1b0c3fd82039d96 100644
--- a/src/content/docs/zaraz/advanced/index.mdx
+++ b/src/content/docs/zaraz/advanced/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Advanced options
 sidebar:
   order: 7
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
index 7e825c97731546d..568da28f0043abf 100644
--- a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
+++ b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
@@ -60,7 +60,8 @@ As with regular tools, it is recommended that you [create the triggers](/zaraz/c
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > [**Third-party tools**](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/tools-config/tools/catalog).
 3. Select **Add new tool** and choose **Custom Managed Component** from the tools library page. Select **Continue** to confirm your selection.
 4. In **Select Custom MC**, choose a Custom Managed Component that you have deployed to your account, such as `custom-mc-my-new-counter-mc`. Select **Continue**.
diff --git a/src/content/docs/zaraz/advanced/load-selectively.mdx b/src/content/docs/zaraz/advanced/load-selectively.mdx
index f9384c91755a2cc..1d02673007eda4d 100644
--- a/src/content/docs/zaraz/advanced/load-selectively.mdx
+++ b/src/content/docs/zaraz/advanced/load-selectively.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Zaraz selectively
 sidebar:
   order: 1
-
 ---
 
 You can use [Configuration Rules](/rules/configuration-rules/) to load Zaraz selectively on specific URLs or subdomains. Configuration Rules can also be used to block Zaraz from loading based on cookies, IP addresses or anything else related to a request.
@@ -15,8 +14,6 @@ Refer to [Configuration Rules](/rules/configuration-rules/) documentation to lea
 
 :::note
 
-
 If you need to block one or more actions from firing in a tool, Cloudflare recommends you use [Blocking Triggers](/zaraz/advanced/blocking-triggers/) instead of Configuration Rules.
 
-
 :::
diff --git a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
index d8ca835447f24d1..ce72a802d046457 100644
--- a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
+++ b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
@@ -6,7 +6,6 @@ products:
 title: Load Zaraz manually
 sidebar:
   order: 5
-
 ---
 
 By default, if your domain is proxied by Cloudflare, Zaraz will automatically inject itself to HTML pages in your site. This makes it easier to get up and running quickly. However, you might want to load Zaraz manually, for example to test Zaraz on specific pages first.
@@ -21,13 +20,13 @@ With the script, your page HTML should be similar to the following:
 
 ```html
 <html>
-  <head>
-    ….
-    <script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
-  </head>
-  <body>
-    …
-  </body>
+	<head>
+		….
+		<script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
+	</head>
+	<body>
+		…
+	</body>
 </html>
 ```
 
diff --git a/src/content/docs/zaraz/advanced/using-jsonata.mdx b/src/content/docs/zaraz/advanced/using-jsonata.mdx
index 925c0718866321c..82292524bfe52e4 100644
--- a/src/content/docs/zaraz/advanced/using-jsonata.mdx
+++ b/src/content/docs/zaraz/advanced/using-jsonata.mdx
@@ -6,7 +6,6 @@ products:
 title: Using JSONata
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To use JSONata inside Zaraz, follow these steps:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Go to **Tools configuration** > **Tools**.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -38,23 +38,22 @@ Converting a string to lowercase is useful if you want to compare it to somethin
 Assuming you are using `zaraz.ecommerce()` to send the cart content like this:
 
 ```js
-zaraz.track('Product List Viewed',
-  {  products:
-    [
-    {
-      sku: '2671033',
-      name: 'V-neck T-shirt',
-      price: 14.99,
-      quantity: 3
-    },{
-      sku: '2671034',
-      name: 'T-shirt',
-      price: 10.99,
-      quantity: 2
-    },
-    ],
-  }
-);
+zaraz.track("Product List Viewed", {
+	products: [
+		{
+			sku: "2671033",
+			name: "V-neck T-shirt",
+			price: 14.99,
+			quantity: 3,
+		},
+		{
+			sku: "2671034",
+			name: "T-shirt",
+			price: 10.99,
+			quantity: 2,
+		},
+	],
+});
 ```
 
 If the field in which you want to show the sum, you will enter `{{ $sum(client.products.(price * quantity)) }}`. This will multiply the price of each product by its quantity, and then sum up the total.
diff --git a/src/content/docs/zaraz/consent-management/api.mdx b/src/content/docs/zaraz/consent-management/api.mdx
index b6feadf8eef42a1..cfbaa929889d835 100644
--- a/src/content/docs/zaraz/consent-management/api.mdx
+++ b/src/content/docs/zaraz/consent-management/api.mdx
@@ -6,7 +6,6 @@ products:
 title: Consent API
 sidebar:
   order: 3
-
 ---
 
 ## Background
@@ -15,7 +14,7 @@ The Consent API allows you to programmatically control all aspects of the Consen
 
 Using the Consent API, you can integrate Zaraz Consent preferences with an external Consent Management Platform, customize your consent modal, or restrict consent management to users in specific regions.
 
-***
+---
 
 ## Events
 
@@ -25,9 +24,8 @@ It can be useful to know when the Consent API is fully loaded on the page so tha
 
 ```js
 document.addEventListener("zarazConsentAPIReady", () => {
-  // do things with the Consent API
+	// do things with the Consent API
 });
-
 ```
 
 ### `Consent Choices Updated`
@@ -36,34 +34,26 @@ This event is fired every time the user makes changes to their consent preferenc
 
 ```js
 document.addEventListener("zarazConsentChoicesUpdated", () => {
-  // read the new consent preferences using `zaraz.consent.getAll();` and do things with it
+	// read the new consent preferences using `zaraz.consent.getAll();` and do things with it
 });
-
 ```
 
-***
+---
 
 ## Properties
 
 The following are properties of the `zaraz.consent` object.
 
+- `modal` boolean
+  - Get or set the current visibility status of the consent modal dialog.
 
+- `purposes` object read-only
+  - An object containing all configured purposes, with their ID, name, description, and order.
 
-* `modal` boolean
-
-  * Get or set the current visibility status of the consent modal dialog.
-
-* `purposes` object read-only
-
-  * An object containing all configured purposes, with their ID, name, description, and order.
-
-* `APIReady` boolean read-only
+- `APIReady` boolean read-only
+  - Indicates whether the Consent API is currently available on the page.
 
-  * Indicates whether the Consent API is currently available on the page.
-
-
-
-***
+---
 
 ## Methods
 
@@ -73,27 +63,18 @@ The following are properties of the `zaraz.consent` object.
 zaraz.consent.get(purposeId);
 ```
 
-
-
-* <code>get(purposeId)</code> : `boolean | undefined`
-
-
+- <code>get(purposeId)</code> : `boolean | undefined`
 
 Get the current consent status for a purpose using the purpose ID.
 
-* `true`: The consent was granted.
-* `false`: The consent was not granted.
-* `undefined`: The purpose does not exist.
+- `true`: The consent was granted.
+- `false`: The consent was not granted.
+- `undefined`: The purpose does not exist.
 
 #### Parameters
 
-
-
-* `purposeId` string
-
-  * The ID representing the Purpose.
-
-
+- `purposeId` string
+  - The ID representing the Purpose.
 
 ### `Set`
 
@@ -101,23 +82,14 @@ Get the current consent status for a purpose using the purpose ID.
 zaraz.consent.set(consentPreferences);
 ```
 
-
-
-* <code>set(consentPreferences)</code> : `undefined`
-
-
+- <code>set(consentPreferences)</code> : `undefined`
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-
-
-* `consentPreferences` object
-
-  * a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
-
-
+- `consentPreferences` object
+  - a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
 
 ### `Get All`
 
@@ -125,11 +97,7 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.getAll();
 ```
 
-
-
-* <code>getAll()</code> : `{ purposeId: boolean }`
-
-
+- <code>getAll()</code> : `{ purposeId: boolean }`
 
 Returns an object with the consent status of all purposes.
 
@@ -139,23 +107,14 @@ Returns an object with the consent status of all purposes.
 zaraz.consent.setAll(consentStatus);
 ```
 
-
-
-* <code>setAll(consentStatus)</code> : `undefined`
-
-
+- <code>setAll(consentStatus)</code> : `undefined`
 
 Set the consent status for all purposes at once.
 
 #### Parameters
 
-
-
-* `consentStatus` boolean
-
-  * Indicates whether the consent was granted or not.
-
-
+- `consentStatus` boolean
+  - Indicates whether the consent was granted or not.
 
 ### `Get All Checkboxes`
 
@@ -163,11 +122,7 @@ Set the consent status for all purposes at once.
 zaraz.consent.getAllCheckboxes();
 ```
 
-
-
-* <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
-
-
+- <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
 
 Returns an object with the checkbox status of all purposes.
 
@@ -177,23 +132,14 @@ Returns an object with the checkbox status of all purposes.
 zaraz.consent.setCheckboxes(checkboxesStatus);
 ```
 
-
-
-* <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
-
-
+- <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-
-
-* `checkboxesStatus` object
-
-  * a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
-
-
+- `checkboxesStatus` object
+  - a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
 
 ### `Set All Checkboxes`
 
@@ -201,23 +147,14 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.setAllCheckboxes(checkboxStatus);
 ```
 
-
-
-* <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
-
-
+- <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
 
 Set the `checkboxStatus` status for all purposes in the consent modal at once.
 
 #### Parameters
 
-
-
-* `checkboxStatus` boolean
-
-  * Indicates whether the purposes should be marked as checked or not.
-
-
+- `checkboxStatus` boolean
+  - Indicates whether the purposes should be marked as checked or not.
 
 ### `Send queued events`
 
@@ -225,11 +162,7 @@ Set the `checkboxStatus` status for all purposes in the consent modal at once.
 zaraz.consent.sendQueuedEvents();
 ```
 
-
-
-* <code>sendQueuedEvents()</code> : `undefined`
-
-
+- <code>sendQueuedEvents()</code> : `undefined`
 
 If some Pageview-based events were not sent due to a lack of consent, they can be sent using this method after consent was granted.
 
@@ -241,32 +174,35 @@ You can combine multiple features of Zaraz to effectively disable Consent Manage
 
 ```html
 <script>
-function getCookie(name) {
-  const value = `; ${document.cookie}`
-  return value?.split(`; ${name}=`)[1]?.split(";")[0]
-}
-
-function handleZarazConsentAPIReady() {
-  const consent_cookie = getCookie("cf_consent")
-  const isEUCountry = "{{system.device.location.isEUCountry}}" === "1"
-  if (!consent_cookie) {
-    if (isEUCountry) {
-      zaraz.consent.modal = true
-    } else {
-      zaraz.consent.setAll(true)
-      zaraz.consent.sendQueuedEvents()
-    }
-  }
-}
-
-if (zaraz.consent?.APIReady) {
-  handleZarazConsentAPIReady()
-} else {
-  document.addEventListener("zarazConsentAPIReady", handleZarazConsentAPIReady)
-}
+	function getCookie(name) {
+		const value = `; ${document.cookie}`;
+		return value?.split(`; ${name}=`)[1]?.split(";")[0];
+	}
+
+	function handleZarazConsentAPIReady() {
+		const consent_cookie = getCookie("cf_consent");
+		const isEUCountry = "{{system.device.location.isEUCountry}}" === "1";
+		if (!consent_cookie) {
+			if (isEUCountry) {
+				zaraz.consent.modal = true;
+			} else {
+				zaraz.consent.setAll(true);
+				zaraz.consent.sendQueuedEvents();
+			}
+		}
+	}
+
+	if (zaraz.consent?.APIReady) {
+		handleZarazConsentAPIReady();
+	} else {
+		document.addEventListener(
+			"zarazConsentAPIReady",
+			handleZarazConsentAPIReady,
+		);
+	}
 </script>
 ```
 
-Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf\_consent"  in the snippet above.
+Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf_consent" in the snippet above.
 
 By letting this Custom HTML tool to run without consent requirements, the modal will appear to all EU visitors, while for other visitors consent will be automatically granted. The `{{ system.device.location.isEUCountry }}` property will be `1` if the visitor is from an EU country and `0` otherwise. You can use any other property or variable to customize the Consent Management behavior in a similar manner, such as `{{ system.device.location.country }}` to restrict consent checks based on country code.
diff --git a/src/content/docs/zaraz/consent-management/custom-css.mdx b/src/content/docs/zaraz/consent-management/custom-css.mdx
index 719f2839cf27872..7827dbae8fb4745 100644
--- a/src/content/docs/zaraz/consent-management/custom-css.mdx
+++ b/src/content/docs/zaraz/consent-management/custom-css.mdx
@@ -6,7 +6,6 @@ products:
 title: Custom CSS
 sidebar:
   order: 2
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,5 +14,6 @@ You can add custom CSS to the Zaraz Consent Management Platform, to make the con
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Find the **Custom CSS** section, and add your custom CSS code as you would on any other HTML editor.
diff --git a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
index 39e50481db06ef5..1a442cb85828653 100644
--- a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
+++ b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable the Consent Management platform (CMP)
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Turn on **Enable Consent Management**.
 3. In **Consent modal text** fill in any legal information required in your country. Use HTML code to format your information as you would in any other HTML editor.
 4. Under **Purposes**, select **Add new Purpose**. Give your new purpose a name and a description. Purposes are the reasons for using third-party tools in your website.
@@ -31,7 +31,8 @@ In your Zaraz consent settings, you can add your consent modal text and purposes
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Select a default language of your choice. The default setting is English.
 3. In **Consent modal text** and **Purposes**, you can select different languages and add translations.
 
@@ -44,7 +45,7 @@ Below is an example that forces the language shown to be American English.
 
 ```html
 <script>
-  zaraz.set('__zarazConsentLanguage', 'en-US')
+	zaraz.set("__zarazConsentLanguage", "en-US");
 </script>
 ```
 
diff --git a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
index 0ab62c99c732fa1..57e58eba4bb79c1 100644
--- a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
+++ b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: IAB Transparency & Consent Framework Compliance
-
 ---
 
 import { DashButton } from "~/components";
@@ -22,7 +21,8 @@ Using the Zaraz Consent Management Platform in IAB TCF Compliance Mode is is opt
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-	<DashButton url="/?to=/:account/tag-management/consent" />
+   <DashButton url="/?to=/:account/tag-management/consent" />
+
 2. Check the **Use IAB TCF compliant modal** option.
 3. Under the **Assign purposes to tools** section, add vendor details to every tool that was not automatically assigned.
 4. Press **Save**.
diff --git a/src/content/docs/zaraz/consent-management/index.mdx b/src/content/docs/zaraz/consent-management/index.mdx
index 57e7e5e3a28277f..577214eacbb7f26 100644
--- a/src/content/docs/zaraz/consent-management/index.mdx
+++ b/src/content/docs/zaraz/consent-management/index.mdx
@@ -11,10 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Zaraz Consent Management platform
-
 ---
 
-Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219\&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
+Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
 
 The consent modal added to your website is concise and gives your users an easy way to opt-in to any purposes of data processing your tools need.
 
@@ -22,12 +21,12 @@ The consent modal added to your website is concise and gives your users an easy
 
 The Zaraz Consent Management platform (CMP) has a **Purposes** section. This is where you will have to create purposes for the third-party tools your website uses. To better understand the terms involved in dealing with personal data, refer to these definitions:
 
-* **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
-* **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
+- **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
+- **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
 
 :::note
 
-All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in. 
+All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in.
 :::
 
 ## Purposes and tools
@@ -36,19 +35,19 @@ When you add a new tool to your website, Zaraz does not assign any purpose to it
 
 The user’s consent preferences are stored within a first-party cookie. This cookie is a JSON file that maps the purposes’ ID to a `true`/`false`/missing value:
 
-* `true` value: The user gave consent.
-* `false`value: The user refused consent.
-* Missing value: The user has not made a choice yet.
+- `true` value: The user gave consent.
+- `false`value: The user refused consent.
+- Missing value: The user has not made a choice yet.
 
 :::caution[Important]
 
-Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR. 
+Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR.
 :::
 
 ## Important things to note
 
-* Purposes that have no tools assigned will not show up in the CMP modal.
-* If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
-* Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
-* If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
-* On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
+- Purposes that have no tools assigned will not show up in the CMP modal.
+- If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
+- Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
+- If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
+- On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
diff --git a/src/content/docs/zaraz/custom-actions/additional-fields.mdx b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
index 76436e214d13c6c..f0bf936140a3a71 100644
--- a/src/content/docs/zaraz/custom-actions/additional-fields.mdx
+++ b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
@@ -6,7 +6,6 @@ products:
 title: Additional fields
 sidebar:
   order: 5
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ Adding an additional field to an action will attach it to this action only, and
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool with the action you want to add the additional field to, and select **Edit**.
 4. Select the action you wish to modify.
@@ -36,7 +36,8 @@ Adding an additional field to the tool sets it as a default field for all of the
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool where you want to add the field, and select **Edit**.
 4. Select **Settings** > **Add Field**.
diff --git a/src/content/docs/zaraz/custom-actions/create-action.mdx b/src/content/docs/zaraz/custom-actions/create-action.mdx
index 7d01b943b05425e..fbb05627895c834 100644
--- a/src/content/docs/zaraz/custom-actions/create-action.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-action.mdx
@@ -16,7 +16,8 @@ To create an action, first [add a third-party tool](/zaraz/get-started/). If you
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate the tool you want to configure an action for, and select **Edit**.
 4. Under Custom actions select **Create action**.
diff --git a/src/content/docs/zaraz/custom-actions/create-trigger.mdx b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
index 7d7d8c141b3ade7..200485ee7f7263e 100644
--- a/src/content/docs/zaraz/custom-actions/create-trigger.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
@@ -14,7 +14,8 @@ Triggers define the conditions under which a tool will start an action. Since a
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Select the **Triggers** tab.
 4. Select **Create trigger**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
index 38a7dae5ee8f9a5..8e83ceeaf6c5a71 100644
--- a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
@@ -6,14 +6,14 @@ products:
 title: Edit tools and actions
 sidebar:
   order: 6
-
 ---
-import { DashButton } from "~/components";
 
+import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools**.
 3. Under **Third-party tools**, locate your tool and select **Edit**.
 
@@ -23,7 +23,8 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select the **Enabled** toggle.
 
@@ -31,7 +32,8 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate the tool you wan to edit and select **Edit**.
 4. Find the action you want to change state, and enable or disable it with the toggle.
@@ -40,6 +42,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select **Delete**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
index 2e9e13f08691d48..23abf7eee383799 100644
--- a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a trigger
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Edit**.
 
@@ -26,6 +26,7 @@ You can edit every field related to the trigger, as well as add new trigger rule
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Delete**.
diff --git a/src/content/docs/zaraz/embeds.mdx b/src/content/docs/zaraz/embeds.mdx
index d2a6e58612bd5d4..72ce24521d03833 100644
--- a/src/content/docs/zaraz/embeds.mdx
+++ b/src/content/docs/zaraz/embeds.mdx
@@ -6,7 +6,6 @@ products:
 title: Embeds
 sidebar:
   order: 6
-
 ---
 
 import { DashButton } from "~/components";
@@ -19,7 +18,8 @@ To add an Embed to Your Website:
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration**.
 3. Click "add new tool" and activate the desired tools on your Cloudflare Zaraz dashboard.
 4. Add a placeholder in your HTML, specifying the necessary attributes. For a generic embed, the snippet looks like this:
@@ -43,7 +43,10 @@ Replace `tweet-id` with the actual tweet ID for the content you wish to embed.
 ### Instagram embed
 
 ```html
-<instagram-post post-url="https://www.instagram.com/p/ABC/" captions="true"></instagram-post>
+<instagram-post
+	post-url="https://www.instagram.com/p/ABC/"
+	captions="true"
+></instagram-post>
 ```
 
 Replace `post-url` with the actual URL for the content you wish to embed. To include posts captions set captions attribute to `true`.
diff --git a/src/content/docs/zaraz/get-started.mdx b/src/content/docs/zaraz/get-started.mdx
index 682f7f02cc686a6..69973cb72ac66dc 100644
--- a/src/content/docs/zaraz/get-started.mdx
+++ b/src/content/docs/zaraz/get-started.mdx
@@ -18,7 +18,8 @@ You can add new third-party tools and load them into your website through the Cl
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. If you have already added a tool before, select **Third-party tools** and click on **Add new tool**.
 3. Choose a tool from the tools catalog. Select **Continue** to confirm your selection.
 4. In **Set up**, configure the settings for your new tool. The information you need to enter will depend on the tool you choose. If you want to use any dynamic properties or variables, select the `+` sign in the drop-down menu next to the relevant field.
diff --git a/src/content/docs/zaraz/history/index.mdx b/src/content/docs/zaraz/history/index.mdx
index a86038b87af35fc..98f0e09c733046c 100644
--- a/src/content/docs/zaraz/history/index.mdx
+++ b/src/content/docs/zaraz/history/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Versions & History
 sidebar:
   order: 8
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Zaraz can work in real-time. In this mode, every change you make is instantly published. You can also enable [Preview & Publish mode](/zaraz/history/preview-mode/), which allows you to test your changes before you commit to them.
 
diff --git a/src/content/docs/zaraz/history/versions.mdx b/src/content/docs/zaraz/history/versions.mdx
index 0ee58afc9464854..d5c71f8201e3f9d 100644
--- a/src/content/docs/zaraz/history/versions.mdx
+++ b/src/content/docs/zaraz/history/versions.mdx
@@ -6,12 +6,10 @@ products:
 title: Versions
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
 
-
 Version History enables you to keep track of all the Zaraz configuration changes made in your website. With Version History you can also revert changes to previous settings should there be a problem.
 
 To access Version History you need to enable [Preview & Publish mode](/zaraz/history/preview-mode/) first. Then, you can access Version History under **Zaraz** > **History**.
@@ -20,11 +18,12 @@ To access Version History you need to enable [Preview & Publish mode](/zaraz/his
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-	<DashButton url="/?to=/:account/tag-management/history" />
-3. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
-   * Date of change
-   * User who made the change
-   * Description of the change
+   <DashButton url="/?to=/:account/tag-management/history" />
+
+2. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
+   - Date of change
+   - User who made the change
+   - Description of the change
 
 ## Revert changes
 
@@ -32,7 +31,8 @@ Version History enables you to revert any changes made to your Zaraz settings.
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-	<DashButton url="/?to=/:account/tag-management/history" />
+   <DashButton url="/?to=/:account/tag-management/history" />
+
 2. Find the changes you want to revert, and select **Restore**.
 3. Confirm you want to revert your changes.
 4. Select **Publish** to publish your changes.
diff --git a/src/content/docs/zaraz/http-events-api.mdx b/src/content/docs/zaraz/http-events-api.mdx
index 657a00899b82342..a4e94957e49f0cd 100644
--- a/src/content/docs/zaraz/http-events-api.mdx
+++ b/src/content/docs/zaraz/http-events-api.mdx
@@ -9,7 +9,6 @@ sidebar:
 head:
   - tag: title
     content: HTTP Events API
-
 ---
 
 import { DashButton } from "~/components";
@@ -24,7 +23,8 @@ To enable the API endpoint:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Under **Endpoints** > **HTTP Events API**, set your desired path. Remember the path is relative to your domain, and it must start with a `/`.
 
 :::caution[Important]
@@ -37,25 +37,25 @@ The endpoint you have configured for the API will receive `POST` requests with a
 
 ```json
 {
-  "events": [
-    {
-      "client": {
-        "__zarazTrack": "transaction successful",
-        "value": "200"
-      }
-    }
-  ]
+	"events": [
+		{
+			"client": {
+				"__zarazTrack": "transaction successful",
+				"value": "200"
+			}
+		}
+	]
 }
 ```
 
 The payload must contain an `events` array. Each Event Object in this array corresponds to one event you want Zaraz to process. The above example is similar to calling `zaraz.track('transaction successful', { value: "200" })` using the Web API.
 
-The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a *Track Property* in the Zaraz dashboard.
+The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a _Track Property_ in the Zaraz dashboard.
 
 There are two reserved keys:
 
-* `__zarazTrack`: The value of this key will be available as *Event Name*. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
-* `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
+- `__zarazTrack`: The value of this key will be available as _Event Name_. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
+- `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
 
 ### The `system` key
 
@@ -65,41 +65,41 @@ The same payload from before will resemble the following example, when we add th
 
 ```json
 {
-  "events": [
-    {
-      "client": {
-        "__zarazTrack": "transaction successful",
-        "value": "200"
-      },
-      "system": {
-        "page": {
-          "url": "https://example.com",
-          "title": "My website"
-        },
-        "device": {
-          "language": "en-US",
-          "ip": "192.168.0.1"
-        }
-      }
-    }
-  ]
+	"events": [
+		{
+			"client": {
+				"__zarazTrack": "transaction successful",
+				"value": "200"
+			},
+			"system": {
+				"page": {
+					"url": "https://example.com",
+					"title": "My website"
+				},
+				"device": {
+					"language": "en-US",
+					"ip": "192.168.0.1"
+				}
+			}
+		}
+	]
 }
 ```
 
 For all available system keys, refer to the table below:
 
-| Property                   | Type  | Description                                                                                |
-| -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------ |
-| `system.cookies`           | Object                         | A key-value object holding cookies from the device associated with the event.              |
-| `system.device.ip`         | String                         | The IP address of the device associated with the event.                                    |
-| `system.device.resolution` | String                         | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
-| `system.device.viewport`   | String                         | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
-| `system.device.language`   | String                         | The language code used by the device associated with the event.                            |
-| `system.device.user-agent` | String                         | The `User-Agent` string of the device associated with the event.                           |
-| `system.page.title`        | String                         | The title of the page associated with the event.                                           |
-| `system.page.url`          | String                         | The URL of the page associated with the event.                                             |
-| `system.page.referrer`     | String                         | The URL of the referrer page in the time the event took place.                             |
-| `system.page.encoding`     | String                         | The encoding of the page associated with the event.                                        |
+| Property                   | Type   | Description                                                                                |
+| -------------------------- | ------ | ------------------------------------------------------------------------------------------ |
+| `system.cookies`           | Object | A key-value object holding cookies from the device associated with the event.              |
+| `system.device.ip`         | String | The IP address of the device associated with the event.                                    |
+| `system.device.resolution` | String | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
+| `system.device.viewport`   | String | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
+| `system.device.language`   | String | The language code used by the device associated with the event.                            |
+| `system.device.user-agent` | String | The `User-Agent` string of the device associated with the event.                           |
+| `system.page.title`        | String | The title of the page associated with the event.                                           |
+| `system.page.url`          | String | The URL of the page associated with the event.                                             |
+| `system.page.referrer`     | String | The URL of the referrer page in the time the event took place.                             |
+| `system.page.encoding`     | String | The encoding of the page associated with the event.                                        |
 
 :::note
 
@@ -112,11 +112,11 @@ For each Event Object in your payload, Zaraz will respond with a Result Object.
 
 Depending on what tools you are loading using Zaraz, the body of the response coming from the API might include information you will want to process. This is because some tools do not have a complete server-side implementation and still depend on cookies, client-side JavaScript or similar mechanisms. Each Result Object can include the following information:
 
-| Result key | Description |
-| --- | --- |
-| `fetch` | Fetch requests that tools want to send from the user browser. |
-| `execute` | JavaScript code that tools want to execute in the user browser. |
-| `return` | Information that tools return. |
-| `cookies` | Cookies that tools want to set for the user. |
+| Result key | Description                                                     |
+| ---------- | --------------------------------------------------------------- |
+| `fetch`    | Fetch requests that tools want to send from the user browser.   |
+| `execute`  | JavaScript code that tools want to execute in the user browser. |
+| `return`   | Information that tools return.                                  |
+| `cookies`  | Cookies that tools want to set for the user.                    |
 
 You do not have to process the information above, but some tools might depend on this to work properly. You can start using the HTTP Events API without processing the information in the table above, and adjust accordingly later.
diff --git a/src/content/docs/zaraz/monitoring/index.mdx b/src/content/docs/zaraz/monitoring/index.mdx
index 7d60ca7c1291ea9..89a3c69828ab590 100644
--- a/src/content/docs/zaraz/monitoring/index.mdx
+++ b/src/content/docs/zaraz/monitoring/index.mdx
@@ -18,8 +18,9 @@ To use Zaraz Monitoring:
 
 1. In the Cloudflare dashboard, go to the **Monitoring** page.
 
-	<DashButton url="/?to=/:account/tag-management/monitoring" />
-3. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
+   <DashButton url="/?to=/:account/tag-management/monitoring" />
+
+2. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
 
 ## Zaraz Monitoring options
 
diff --git a/src/content/docs/zaraz/pricing-info.mdx b/src/content/docs/zaraz/pricing-info.mdx
index dca9b6076413d78..1ca41a948098035 100644
--- a/src/content/docs/zaraz/pricing-info.mdx
+++ b/src/content/docs/zaraz/pricing-info.mdx
@@ -6,7 +6,6 @@ products:
 title: Pricing
 sidebar:
   order: 15
-
 ---
 
 import { DashButton } from "~/components";
@@ -18,13 +17,15 @@ All Zaraz features and tools are always available on all accounts. Learn more ab
 ## The Zaraz Event unit
 
 One Zaraz Event is an event you are sending to Zaraz, whether that is a page view, a `zaraz.track` event, or similar. You can easily see the total number of Zaraz Events you are currently using on the **Monitoring** page of the Cloudflare dashboard:
-   <DashButton url="/?to=/:account/tag-management/monitoring" />
+
+<DashButton url="/?to=/:account/tag-management/monitoring" />
 
 ## Enabling Zaraz Paid
 
 1. In the Cloudflare dashboard, go to the **Zaraz plans** page.
 
-	<DashButton url="/?to=/:account/tag-management/plans" />
+   <DashButton url="/?to=/:account/tag-management/plans" />
+
 2. Click the **Enable Zaraz usage billing** button and follow the instructions.
 
 ## Using Zaraz Free
diff --git a/src/content/docs/zaraz/reference/context.mdx b/src/content/docs/zaraz/reference/context.mdx
index bda539074da4906..6f7df19926f9b1a 100644
--- a/src/content/docs/zaraz/reference/context.mdx
+++ b/src/content/docs/zaraz/reference/context.mdx
@@ -6,7 +6,6 @@ products:
 title: Zaraz Context
 sidebar:
   order: 10
-
 ---
 
 The Zaraz Context is a versatile object that provides a set of configurable properties for Zaraz, a web analytics tool for tracking user behavior on websites. These properties can be accessed and utilized across various components, including [Worker Variables](/zaraz/variables/worker-variables/) and [JSONata expressions](/zaraz/advanced/using-jsonata/).
@@ -17,8 +16,6 @@ System properties, which are automatically collected by Zaraz, provide insights
 
 ### Page information
 
-
-
 | Property               | Type   | Description                                                                                                     |
 | ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------- |
 | `system.page.query`    | Object | Key-Value object containing all query parameters in the current URL.                                            |
@@ -38,8 +35,6 @@ The keys inside the `system.cookies` are the cookies name. The property `system.
 
 ### Device information
 
-
-
 | Property                                   | Type   | Description                                                                                                              |
 | ------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------ |
 | `system.device.ip`                         | String | Visitor incoming IP address.                                                                                             |
@@ -76,8 +71,6 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ### Miscellaneous
 
-
-
 | Property                            | Type   | Description                           |
 | ----------------------------------- | ------ | ------------------------------------- |
 | `system.misc.random`                | Number | Random number unique to each request. |
@@ -87,8 +80,6 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ## Event properties
 
-
-
 | Property              | Type   | Description                                                                                                                                                                                                                                                          |
 | --------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `client.__zarazTrack` | String | Returns the name of the event sent using the Track method of the Web API. Refer to [Zaraz Track](/zaraz/web-api/track/) for more information.                                                                                                                        |
diff --git a/src/content/docs/zaraz/reference/index.mdx b/src/content/docs/zaraz/reference/index.mdx
index 3b3f9005d879c9c..11447093e6b50dc 100644
--- a/src/content/docs/zaraz/reference/index.mdx
+++ b/src/content/docs/zaraz/reference/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Reference
 sidebar:
   order: 9
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/reference/properties-reference.mdx b/src/content/docs/zaraz/reference/properties-reference.mdx
index a6ac0acf199d0b1..abecfe520bf0280 100644
--- a/src/content/docs/zaraz/reference/properties-reference.mdx
+++ b/src/content/docs/zaraz/reference/properties-reference.mdx
@@ -4,8 +4,8 @@ description: Built-in properties available in Zaraz events.
 products:
   - zaraz
 title: Properties reference
-
 ---
+
 import { DashButton } from "~/components";
 
 Cloudflare Zaraz offers properties that you can use when configuring the product. They are helpful to send data to a third-party tool or to create triggers as they have context about a specific user's browser session and the actions they take on the website. Below is a list of the properties you can access from the Cloudflare dashboard and their values.
@@ -14,69 +14,69 @@ Cloudflare Zaraz offers properties that you can use when configuring the product
 
 | Property               | Description                                                                                                                                                                                                                                          |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| *Event Name*           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
-| *Track Property name:* | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
+| _Event Name_           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
+| _Track Property name:_ | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
 
 ## Page Properties
 
 | Property                  | Description                                                                                                            |
 | ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| *Page character encoding* | Returns the document character encoding from `document.characterSet`.                                                  |
-| *Page referrer*           | Returns the page referrer from `document.referrer`.                                                                    |
-| *Page title*              | Returns the page title.                                                                                                |
-| *Query param name:*       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
-| *URL*                     | Returns a string containing the entire URL.                                                                            |
-| *URL base domain*         | Returns the base domain part of the URL, without any subdomains.                                                       |
-| *URL host*                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
-| *URL hostname*            | Returns the domain of the URL.                                                                                         |
-| *URL origin*              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
-| *URL password*            | Returns the password specified before the domain name.                                                                 |
-| *URL pathname*            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
-| *URL port*                | Returns the port number of the URL.                                                                                    |
-| *URL protocol scheme*     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
-| *URL query parameters*    | Returns query parameters provided, beginning with the leading `?` character.                                           |
-| *URL username*            | Returns the username specified before the domain name.                                                                 |
+| _Page character encoding_ | Returns the document character encoding from `document.characterSet`.                                                  |
+| _Page referrer_           | Returns the page referrer from `document.referrer`.                                                                    |
+| _Page title_              | Returns the page title.                                                                                                |
+| _Query param name:_       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
+| _URL_                     | Returns a string containing the entire URL.                                                                            |
+| _URL base domain_         | Returns the base domain part of the URL, without any subdomains.                                                       |
+| _URL host_                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
+| _URL hostname_            | Returns the domain of the URL.                                                                                         |
+| _URL origin_              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
+| _URL password_            | Returns the password specified before the domain name.                                                                 |
+| _URL pathname_            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
+| _URL port_                | Returns the port number of the URL.                                                                                    |
+| _URL protocol scheme_     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
+| _URL query parameters_    | Returns query parameters provided, beginning with the leading `?` character.                                           |
+| _URL username_            | Returns the username specified before the domain name.                                                                 |
 
 ## Cookies
 
 | Property       | Description                                           |
 | -------------- | ----------------------------------------------------- |
-| *Cookie name:* | Returns cookies obtained from the browser `document`. |
+| _Cookie name:_ | Returns cookies obtained from the browser `document`. |
 
 ## Device properties
 
 | Property                   | Description                                                 |
 | -------------------------- | ----------------------------------------------------------- |
-| *Browser engine*           | Returns the type of browser engine (for example, `WebKit`). |
-| *Browser engine version*   | Returns the version of the browser’s engine.                |
-| *Browser name*             | Returns the browser’s name.                                 |
-| *Browser version*          | Returns the browser’s version.                              |
-| *Device CPU*               | Returns the device’s CPU.                                   |
-| *Device IP address*        | Returns the incoming IP address.                            |
-| *Device language*          | Returns the language used.                                  |
-| *Device screen resolution* | Returns the screen resolution of the device.                |
-| *Device type*              | Returns the type of device used (for example, `iPhone`).    |
-| *Device viewport*          | Returns the visible web page area in user’s device.         |
-| *Operating system name*    | Returns the operating system.                               |
-| *Operating system version* | Returns the version of the operating system.                |
-| *User-agent string*        | Returns the browser’s user agent.                           |
+| _Browser engine_           | Returns the type of browser engine (for example, `WebKit`). |
+| _Browser engine version_   | Returns the version of the browser’s engine.                |
+| _Browser name_             | Returns the browser’s name.                                 |
+| _Browser version_          | Returns the browser’s version.                              |
+| _Device CPU_               | Returns the device’s CPU.                                   |
+| _Device IP address_        | Returns the incoming IP address.                            |
+| _Device language_          | Returns the language used.                                  |
+| _Device screen resolution_ | Returns the screen resolution of the device.                |
+| _Device type_              | Returns the type of device used (for example, `iPhone`).    |
+| _Device viewport_          | Returns the visible web page area in user’s device.         |
+| _Operating system name_    | Returns the operating system.                               |
+| _Operating system version_ | Returns the version of the operating system.                |
+| _User-agent string_        | Returns the browser’s user agent.                           |
 
 ## Device location
 
 | Property       | Description                                                                                                                                                                       |
 | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| *City*         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
-| *Continent*    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
-| *Country* code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
-| *EU* country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
-| *Region*       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
-| *Region* code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
-| *Timezone*     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
+| _City_         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
+| _Continent_    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
+| _Country_ code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
+| _EU_ country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
+| _Region_       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
+| _Region_ code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
+| _Timezone_     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
 
 ## Miscellaneous
 
 | Property                   | Description                                     |
 | -------------------------- | ----------------------------------------------- |
-| *Random number*            | Returns a random number unique to each request. |
-| *Timestamp (milliseconds)* | Returns the Unix time in milliseconds.          |
-| *Timestamp (seconds)*      | Returns the Unix time in seconds.               |
+| _Random number_            | Returns a random number unique to each request. |
+| _Timestamp (milliseconds)_ | Returns the Unix time in milliseconds.          |
+| _Timestamp (seconds)_      | Returns the Unix time in seconds.               |
diff --git a/src/content/docs/zaraz/reference/settings.mdx b/src/content/docs/zaraz/reference/settings.mdx
index 886095c024fe466..40f857c4d333de9 100644
--- a/src/content/docs/zaraz/reference/settings.mdx
+++ b/src/content/docs/zaraz/reference/settings.mdx
@@ -13,7 +13,7 @@ import { Plan, DashButton } from "~/components";
 
 To configure Zaraz's general settings, go to the **Settings** page in the Cloudflare dashboard:
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
+<DashButton url="/?to=/:account/tag-management/settings" />
 
 Make sure you save your changes, by selecting the **Save** button after making them.
 
@@ -45,15 +45,15 @@ When you toggle Single Page Application support off, the `pageview` trigger will
 
 Zaraz offers privacy settings you can configure, such as:
 
-* **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
+- **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
 
-* **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
+- **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
 
-* **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
+- **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
 
-* **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
+- **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
 
-* **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
+- **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
 
 ## Injection
 
@@ -93,9 +93,9 @@ Choose whether to prevent Zaraz from loading on suspected bot-initiated requests
 
 The options are:
 
-* **Block none**: Load Zaraz for all requests, even if those come from bots.
-* **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
-* **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
+- **Block none**: Load Zaraz for all requests, even if those come from bots.
+- **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
+- **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
 
 ### Context Enricher
 
diff --git a/src/content/docs/zaraz/reference/supported-tools.mdx b/src/content/docs/zaraz/reference/supported-tools.mdx
index 1b388c261cd4ea2..e20ce7495b724b0 100644
--- a/src/content/docs/zaraz/reference/supported-tools.mdx
+++ b/src/content/docs/zaraz/reference/supported-tools.mdx
@@ -7,7 +7,6 @@ title: Third-party tools
 head:
   - tag: title
     content: Supported tools
-
 ---
 
 Cloudflare Zaraz supports the following third-party tools:
diff --git a/src/content/docs/zaraz/variables/create-variables.mdx b/src/content/docs/zaraz/variables/create-variables.mdx
index 7e4f9894f49c848..cfce350ba75324b 100644
--- a/src/content/docs/zaraz/variables/create-variables.mdx
+++ b/src/content/docs/zaraz/variables/create-variables.mdx
@@ -20,7 +20,8 @@ For example, instead of typing a specific user ID in multiple fields, you can cr
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Variables**.
 3. Select **Create variable**, and give it a name.
 4. In **Variable type** select between `String`, `Masked variable` or `Worker` from the drop-down menu. Use `Masked variable` when you have a private value that you do not want to share, such as an API token.
diff --git a/src/content/docs/zaraz/variables/edit-variables.mdx b/src/content/docs/zaraz/variables/edit-variables.mdx
index 2225f830ff4de41..0c30678d2adc6e5 100644
--- a/src/content/docs/zaraz/variables/edit-variables.mdx
+++ b/src/content/docs/zaraz/variables/edit-variables.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a variable
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Variables**.
 3. Locate the variable you want to edit, and select **Edit** to make your changes.
 4. Select **Save** to save your edits.
@@ -29,7 +29,8 @@ You cannot delete a variable being used in tools or triggers.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate any tools using the variable, and delete the variable from those tools.
 4. Select **Zaraz** > **Tools Configuration** > **Triggers**.
diff --git a/src/content/docs/zaraz/variables/index.mdx b/src/content/docs/zaraz/variables/index.mdx
index 2201ce391be6a3a..98febbeb0a587f0 100644
--- a/src/content/docs/zaraz/variables/index.mdx
+++ b/src/content/docs/zaraz/variables/index.mdx
@@ -6,9 +6,8 @@ products:
 title: Variables
 sidebar:
   order: 6
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/variables/worker-variables.mdx b/src/content/docs/zaraz/variables/worker-variables.mdx
index 3b80fe43170c522..57b8bfa416f7617 100644
--- a/src/content/docs/zaraz/variables/worker-variables.mdx
+++ b/src/content/docs/zaraz/variables/worker-variables.mdx
@@ -6,7 +6,6 @@ products:
 title: Worker Variables
 sidebar:
   order: 10
-
 ---
 
 import { DashButton } from "~/components";
@@ -25,7 +24,8 @@ To create a new Worker in the Cloudflare dashboard:
 
 1. In the Cloudflare dashboard, go to the **Workers and Pages** page.
 
-	<DashButton url="/?to=/:account/workers-and-pages" />
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Give a name to your Worker and select **Deploy**.
 4. Select **Edit code**.
@@ -35,17 +35,17 @@ You have now created a basic Worker that responds with "Hello world." If you use
 Zaraz forwards the Zaraz Context object to your Worker as a JSON payload with a POST request. You can access any property like this:
 
 ```js
-const { system, client } = await request.json()
+const { system, client } = await request.json();
 
 /* System parameters */
-system.page.url.href // URL of the current page
-system.page.query.gclid // Value of the gclid query parameter
-system.device.resolution // Device screen resolution
-system.device.language // Browser preferred language
+system.page.url.href; // URL of the current page
+system.page.query.gclid; // Value of the gclid query parameter
+system.device.resolution; // Device screen resolution
+system.device.language; // Browser preferred language
 
 /* Zaraz Track values */
-client.value // value from `zaraz.track("foo", {value: "bar"})`
-client.products[0].name // name of the first product in an ecommerce call
+client.value; // value from `zaraz.track("foo", {value: "bar"})`
+client.products[0].name; // name of the first product in an ecommerce call
 ```
 
 Keep reading for more complete examples of different use cases or refer to [Zaraz Context](/zaraz/reference/context/).
@@ -56,7 +56,8 @@ Once your Worker is published, configuring a Worker Variable is easy.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select the domain for which you want to configure variables.
 3. Select the **Variables** tab.
 4. Select **Create variable**.
@@ -71,7 +72,8 @@ To use your Worker Variable:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-	<DashButton url="/?to=/:account/tag-management/zaraz" />
+   <DashButton url="/?to=/:account/tag-management/zaraz" />
+
 2. Select the domain for which you want to configure variables.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -86,11 +88,11 @@ Assuming we are sending a list of products in a cart, like this:
 
 ```js
 zaraz.ecommerce("Cart Viewed", {
-  products: [
-    { name: "shirt", price: "50" },
-    { name: "jacket", price: "20" },
-    { name: "hat", price: "30" },
-  ],
+	products: [
+		{ name: "shirt", price: "50" },
+		{ name: "jacket", price: "20" },
+		{ name: "hat", price: "30" },
+	],
 });
 ```
 
@@ -98,18 +100,18 @@ Calculating the sum can be done like this:
 
 ```js
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    // Get an array of all prices
-    const productsPrices = client.products.map((p) => p.price);
+		// Get an array of all prices
+		const productsPrices = client.products.map((p) => p.price);
 
-    // Calculate the sum
-    const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
+		// Calculate the sum
+		const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
 
-    return new Response(sum);
-  },
+		return new Response(sum);
+	},
 };
 ```
 
@@ -119,20 +121,20 @@ Zaraz exposes all cookies automatically under the `system.cookies` object, so th
 
 ```js
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    // Get the value of the cookie "login-cookie"
-    const cookieValue = system.cookies["login-cookie"];
+		// Get the value of the cookie "login-cookie"
+		const cookieValue = system.cookies["login-cookie"];
 
-    const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
-      method: POST,
-      body: cookieValue,
-    });
+		const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
+			method: POST,
+			body: cookieValue,
+		});
 
-    return new Response(userId);
-  },
+		return new Response(userId);
+	},
 };
 ```
 
@@ -148,23 +150,23 @@ You can access this property and hash it like this:
 
 ```js
 async function digestMessage(message) {
-  const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
-  const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
-  const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
-  const hashHex = hashArray
-    .map((b) => b.toString(16).padStart(2, "0"))
-    .join(""); // convert bytes to hex string
-  return hashHex;
+	const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
+	const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
+	const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
+	const hashHex = hashArray
+		.map((b) => b.toString(16).padStart(2, "0"))
+		.join(""); // convert bytes to hex string
+	return hashHex;
 }
 
 export default {
-  async fetch(request, env) {
-    // Parse the Zaraz Context object
-    const { system, client } = await request.json();
+	async fetch(request, env) {
+		// Parse the Zaraz Context object
+		const { system, client } = await request.json();
 
-    const { email } = client;
+		const { email } = client;
 
-    return new Response(await digestMessage(email));
-  },
+		return new Response(await digestMessage(email));
+	},
 };
 ```
diff --git a/src/content/docs/zaraz/web-api/debug-mode.mdx b/src/content/docs/zaraz/web-api/debug-mode.mdx
index a2110d8626e7f2c..3e17a55399dfbf2 100644
--- a/src/content/docs/zaraz/web-api/debug-mode.mdx
+++ b/src/content/docs/zaraz/web-api/debug-mode.mdx
@@ -6,7 +6,6 @@ products:
 title: Debug mode
 sidebar:
   order: 4
-
 ---
 
 import { DashButton } from "~/components";
@@ -16,13 +15,14 @@ You can set this cookie manually or via the `zaraz.debug` helper function availa
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Copy your **Debug Key**.
 3. Open a web browser and access its Developer Tools. For example, to access Developer Tools in Google Chrome, select **View** > **Developer** > **Developer Tools**.
 4. Select the **Console** pane and enter the following command to create a debug cookie:
 
    ```js
-   zaraz.debug("YOUR_DEBUG_KEY")
+   zaraz.debug("YOUR_DEBUG_KEY");
    ```
 
 Zaraz’s debug mode is now enabled. A pop-up window will show up with the debugger information. To exit debug mode, remove the cookie by typing `zaraz.debug()` in the console pane of the browser.
diff --git a/src/content/docs/zaraz/web-api/ecommerce.mdx b/src/content/docs/zaraz/web-api/ecommerce.mdx
index 47b9b8b44b53c60..94708e09a23b5eb 100644
--- a/src/content/docs/zaraz/web-api/ecommerce.mdx
+++ b/src/content/docs/zaraz/web-api/ecommerce.mdx
@@ -31,7 +31,8 @@ You do not need to map e-commerce events to triggers. Zaraz automatically forwar
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-	<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
+
 2. Enable **E-commerce tracking**.
 3. Select **Save**.
 4. Go to **Zaraz** > **Tools Configuration** > **Third-party tools**.
diff --git a/src/content/docs/zaraz/web-api/index.mdx b/src/content/docs/zaraz/web-api/index.mdx
index 15b544bb65b4744..be94552a3782c97 100644
--- a/src/content/docs/zaraz/web-api/index.mdx
+++ b/src/content/docs/zaraz/web-api/index.mdx
@@ -6,10 +6,9 @@ products:
 title: Web API
 sidebar:
   order: 3
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Zaraz provides a client-side web API that you can use anywhere inside the `<body>` tag of a page.
 
diff --git a/src/content/docs/zaraz/web-api/set.mdx b/src/content/docs/zaraz/web-api/set.mdx
index 0d9f29ac5943204..447578481222c7a 100644
--- a/src/content/docs/zaraz/web-api/set.mdx
+++ b/src/content/docs/zaraz/web-api/set.mdx
@@ -9,27 +9,26 @@ sidebar:
 head:
   - tag: title
     content: zaraz.set
-
 ---
 
 You can use `zaraz.set()` anywhere inside the `<body>` tag of a page:
 
 ```js
-zaraz.set(key, value, [options])
+zaraz.set(key, value, [options]);
 ```
 
 Set is useful if you want to make a variable available in all your events without manually setting it every time you are using `zaraz.track()`. For the purpose of this example, assume users in your system have a unique identifier that you want to send to your tools. You might have many `zaraz.track()` calls all sharing this one parameter:
 
 ```js
-zaraz.track("form completed", {userId: "ABC-123"})
+zaraz.track("form completed", { userId: "ABC-123" });
 ```
 
 ```js
-zaraz.track("button clicked", {userId: "ABC-123", value: 200})
+zaraz.track("button clicked", { userId: "ABC-123", value: 200 });
 ```
 
 ```js
-zaraz.track("cart viewed", {items: 3, userId: "ABC-123"})
+zaraz.track("cart viewed", { items: 3, userId: "ABC-123" });
 ```
 
 Here, all the events are collecting the `userId` key, and the code for setting that key repeats itself. With `zaraz.set()` you can avoid repetition by setting the key once when the page loads. Zaraz will then attach this key to all future `zaraz.track()` calls.
@@ -39,23 +38,23 @@ Using the above data as the example, if you use `zaraz.set("userId", "ABC-123")`
 Another example:
 
 ```js
-zaraz.set('product_name', 't-shirt', {scope: 'page'})
+zaraz.set("product_name", "t-shirt", { scope: "page" });
 ```
 
-Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable *Track Property name:*, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
+Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable _Track Property name:_, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
 
 ![Example of how to create a variable with the Set method, tracking t-shirts](~/assets/images/zaraz/set.png)
 
 The `[options]` argument is an optional object and can include a `scope` property that has a string value. This property determines the lifetime of this key, meaning for how long Zaraz should keep attaching it to `zaraz.track()` calls. Allowed values are:
 
-* `page`: To set the key for the context of the current page only.
-* `session`: To make the key last the whole session.
-* `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
+- `page`: To set the key for the context of the current page only.
+- `session`: To make the key last the whole session.
+- `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
 
 In the previous example, `{scope: 'page'}` makes the `product_name` property available to all `zaraz.track()` calls in the current page, but will not affect calls after visitors navigate to other pages.
 
 To unset a variable, set it to `undefined`. The variable will then be removed from all scopes it was included in, and will not be automatically sent with future `zaraz.track` calls. For example:
 
 ```js
-zaraz.set('product_name', undefined)
+zaraz.set("product_name", undefined);
 ```
diff --git a/src/content/partials/1.1.1.1/captive-portals.mdx b/src/content/partials/1.1.1.1/captive-portals.mdx
index 9a22c3361ba00f0..7d4223b076a5f3f 100644
--- a/src/content/partials/1.1.1.1/captive-portals.mdx
+++ b/src/content/partials/1.1.1.1/captive-portals.mdx
@@ -12,4 +12,4 @@ If you are experiencing connectivity issues related to captive portals:
 2. Connect to the Wi-Fi network.
 3. Once the connection has been established, re-add the static IP addresses or enable the 1.1.1.1 app.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/agents/unique-agents.mdx b/src/content/partials/agents/unique-agents.mdx
index d3f96c7f9fa15e9..bd157735e3ad07f 100644
--- a/src/content/partials/agents/unique-agents.mdx
+++ b/src/content/partials/agents/unique-agents.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
@@ -11,4 +10,4 @@ This allows you to avoid synchronizing state across requests: if an Agent instan
 
 If the client disconnects, you can always route the client back to the exact same Agent and pick up where they left off.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ai-crawl-control/plan-comparison.mdx b/src/content/partials/ai-crawl-control/plan-comparison.mdx
index f56f51d865fe7c5..a03e263b7030fed 100644
--- a/src/content/partials/ai-crawl-control/plan-comparison.mdx
+++ b/src/content/partials/ai-crawl-control/plan-comparison.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                       |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)           |
-| Maximum 24-hour analytics window                                                                                              |  Configurable analytics timeframes                                                                                                      |
-| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
\ No newline at end of file
+| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                               |
+| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)                   |
+| Maximum 24-hour analytics window                                                                                              | Configurable analytics timeframes                                                                                                                  |
+| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
diff --git a/src/content/partials/ai-gateway/analytics-dashboard.mdx b/src/content/partials/ai-gateway/analytics-dashboard.mdx
index 9c812ba529cb5bb..5dbb03ea869ad8b 100644
--- a/src/content/partials/ai-gateway/analytics-dashboard.mdx
+++ b/src/content/partials/ai-gateway/analytics-dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To view analytics in the dashboard:
diff --git a/src/content/partials/ai-gateway/logging.mdx b/src/content/partials/ai-gateway/logging.mdx
index ae7983b75652584..9522593e0222102 100644
--- a/src/content/partials/ai-gateway/logging.mdx
+++ b/src/content/partials/ai-gateway/logging.mdx
@@ -1,6 +1,7 @@
 ---
 {}
 ---
+
 import { DashButton } from "~/components";
 
 To change the default log configuration in the dashboard:
diff --git a/src/content/partials/ai-gateway/universal-gateway-example.mdx b/src/content/partials/ai-gateway/universal-gateway-example.mdx
index c0bbda990100faa..6950494e7677012 100644
--- a/src/content/partials/ai-gateway/universal-gateway-example.mdx
+++ b/src/content/partials/ai-gateway/universal-gateway-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```bash title="Request"
diff --git a/src/content/partials/ai-search/rest-api-auth.mdx b/src/content/partials/ai-search/rest-api-auth.mdx
index 84c53bc88b43199..afc3a5199d0f9b0 100644
--- a/src/content/partials/ai-search/rest-api-auth.mdx
+++ b/src/content/partials/ai-search/rest-api-auth.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 All requests require an API token with **AI Search:Edit** and **AI Search:Run** permissions.
 
diff --git a/src/content/partials/analytics/customer_metadata_boundary_error.mdx b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
index aa5a25eabdfe090..892e43f082a7c02 100644
--- a/src/content/partials/analytics/customer_metadata_boundary_error.mdx
+++ b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 If you encounter a message on the dashboard indicating that your data is unavailable due to your account's Metadata Boundary configuration, this is because you are trying to access data that is not stored in your region (that is, you are in the US and trying to access data that is only stored in the EU, or vice versa). If you receive this error message while being in the region where your data is stored, there are two potential reasons why you might get this message:
 
-* Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
+- Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
 
-* If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
+- If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
diff --git a/src/content/partials/analytics/network-analytics-requirements.mdx b/src/content/partials/analytics/network-analytics-requirements.mdx
index 972d6cea688b524..509b51ff43b0ffd 100644
--- a/src/content/partials/analytics/network-analytics-requirements.mdx
+++ b/src/content/partials/analytics/network-analytics-requirements.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 :::note[Requirements]
 
 Network Analytics requires the following:
 
-* A Cloudflare Enterprise plan.
-* Cloudflare Magic Transit or Spectrum.
-* Cloudflare WAN.
+- A Cloudflare Enterprise plan.
+- Cloudflare Magic Transit or Spectrum.
+- Cloudflare WAN.
   :::
diff --git a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
index d2dfe96892e93b6..bc1a23a14f531b7 100644
--- a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
+++ b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Network Analytics v1 (NAv1) is now deprecated.** For more information on Network Analytics v2 (NAv2), refer to [Cloudflare Network Analytics](/analytics/network-analytics/).
diff --git a/src/content/partials/api-shield/label-methodology.mdx b/src/content/partials/api-shield/label-methodology.mdx
index 72400e85c006187..96af54686fabef0 100644
--- a/src/content/partials/api-shield/label-methodology.mdx
+++ b/src/content/partials/api-shield/label-methodology.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-| 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. |
+| 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. |
diff --git a/src/content/partials/api-shield/mtls-api-shield-support.mdx b/src/content/partials/api-shield/mtls-api-shield-support.mdx
index 0224d99943797f8..1588524b353a3c5 100644
--- a/src/content/partials/api-shield/mtls-api-shield-support.mdx
+++ b/src/content/partials/api-shield/mtls-api-shield-support.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/api-shield/mtls-create-rule.mdx b/src/content/partials/api-shield/mtls-create-rule.mdx
index ac25847bffa79f2..8385e54de0b19d4 100644
--- a/src/content/partials/api-shield/mtls-create-rule.mdx
+++ b/src/content/partials/api-shield/mtls-create-rule.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Steps, DashButton } from "~/components"
+import { Steps, DashButton } from "~/components";
 
 <Steps>
 1. In the Cloudflare dashboard, go to **Client Certificates** page.
@@ -16,4 +15,4 @@ import { Steps, DashButton } from "~/components"
 6. Select **Deploy** to make the rule active.
 </Steps>
 
-Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
\ No newline at end of file
+Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
diff --git a/src/content/partials/api-shield/rate-limit-user.mdx b/src/content/partials/api-shield/rate-limit-user.mdx
index 9cdc3591641dfcf..d47e2e46b45069e 100644
--- a/src/content/partials/api-shield/rate-limit-user.mdx
+++ b/src/content/partials/api-shield/rate-limit-user.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ### Rate limit by user (JWT claim)
diff --git a/src/content/partials/api-shield/required-session-identifiers.mdx b/src/content/partials/api-shield/required-session-identifiers.mdx
index a1f6276e094c00c..59e54427d1d871b 100644
--- a/src/content/partials/api-shield/required-session-identifiers.mdx
+++ b/src/content/partials/api-shield/required-session-identifiers.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You must have specific entitlements to configure session identifiers or cookies as a form of identifiers, such as an Enterprise subscription, for features such as [API Discovery](/api-shield/security/api-discovery/), [Sequence Mitigation](/api-shield/security/sequence-mitigation/) or [rate limiting recommendations](/api-shield/security/volumetric-abuse-detection/), and to see results in [Sequence Analytics](/api-shield/security/sequence-analytics/) and [Authentication Posture](/api-shield/security/authentication-posture/).
diff --git a/src/content/partials/api-shield/sequence-mitigation-availability.mdx b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
index 38bbe706bb998a3..94c7f150023934f 100644
--- a/src/content/partials/api-shield/sequence-mitigation-availability.mdx
+++ b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
\ No newline at end of file
+Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
diff --git a/src/content/partials/api-shield/session-identifiers.mdx b/src/content/partials/api-shield/session-identifiers.mdx
index 4e517b779b2b3a9..ef978913a8fe1cf 100644
--- a/src/content/partials/api-shield/session-identifiers.mdx
+++ b/src/content/partials/api-shield/session-identifiers.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 While not strictly required, it is recommended that you configure your <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> when getting started with API Shield. When Cloudflare inspects your API traffic for individual sessions, we can offer more tools for visibility, management, and control.
 
@@ -11,4 +10,4 @@ If you are unsure of the session identifiers that your API uses, consult with yo
 
 Session identifiers should uniquely identify API clients. A common session identifier for API traffic is the `Authorization` header. When a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) is used by the API for client authentication, its value may change over time. You can use a claim value inside the JWT such as `sub` or `email` as a session ID to uniquely identify the session over time.
 
-If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
\ No newline at end of file
+If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
diff --git a/src/content/partials/billing/two-payment-methods.mdx b/src/content/partials/billing/two-payment-methods.mdx
index fcd2e4ffca05097..9db0c042394f0a1 100644
--- a/src/content/partials/billing/two-payment-methods.mdx
+++ b/src/content/partials/billing/two-payment-methods.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/bots/about-plan-considerations.mdx b/src/content/partials/bots/about-plan-considerations.mdx
index 13c3ff7327eaed5..dbee048b258ff34 100644
--- a/src/content/partials/bots/about-plan-considerations.mdx
+++ b/src/content/partials/bots/about-plan-considerations.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 Bot Fight Mode and Super Bot Fight Mode use the same underlying technology that powers our [Bot Management](https://www.cloudflare.com/products/bot-management/) product. Specifically, these products:
 
-* Protect entire domains without endpoint restrictions
-* Cannot be customized, adjusted, or reconfigured via WAF custom rules
+- Protect entire domains without endpoint restrictions
+- Cannot be customized, adjusted, or reconfigured via WAF custom rules
 
 Although these products are designed to fight malicious actors on the Internet, they may challenge API or mobile app traffic. For more granular control, upgrade to [Bot Management for Enterprise](/bots/plans/bm-subscription/).
diff --git a/src/content/partials/bots/analytics-features.mdx b/src/content/partials/bots/analytics-features.mdx
index 8b21959f185efd0..5c8c8cc61b1b641 100644
--- a/src/content/partials/bots/analytics-features.mdx
+++ b/src/content/partials/bots/analytics-features.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare uses adaptive bitrate technology to show sampled data — most customers will see a 1-10% sample depending on how much information they are trying to view. Tooltips on the page will display the current sample rate.
diff --git a/src/content/partials/bots/bfm-change-notice.mdx b/src/content/partials/bots/bfm-change-notice.mdx
index d7474bab9acd502..e4fb1dd54926f1a 100644
--- a/src/content/partials/bots/bfm-change-notice.mdx
+++ b/src/content/partials/bots/bfm-change-notice.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Change notice for Super Bot Fight Mode rulesets]
diff --git a/src/content/partials/bots/bm-analytics-features.mdx b/src/content/partials/bots/bm-analytics-features.mdx
index 7dc1163ab88af8d..9af38b36aca085c 100644
--- a/src/content/partials/bots/bm-analytics-features.mdx
+++ b/src/content/partials/bots/bm-analytics-features.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 For a full tour of Bot Analytics, see [our blog post](https://blog.cloudflare.com/introducing-bot-analytics/). At a high level, the tool includes:
 
-* **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on *automated* and *likely automated* traffic.
-* **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
-* **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
-* **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
+- **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on _automated_ and _likely automated_ traffic.
+- **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
+- **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
+- **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
 
 Bot Analytics shows up to one week of data at a time and can display data up to 30 days old. Bot Analytics displays data in real time in most cases.
diff --git a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
index 792c3896e90dbdb..4a7b8ba166882b8 100644
--- a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
+++ b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
@@ -6,13 +6,13 @@
 
 The following features are handled automatically in **Security Settings** and do not require custom rules:
 
-| Feature | Handled by bot settings | Requires custom rules |
-| --- | --- | --- |
-| Block or challenge definitely automated traffic | Yes | Only for path-specific or threshold-tuned rules |
-| Block or challenge likely automated traffic | Not available on Pro | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
-| Allow or block verified bots | Yes | No |
-| Block AI crawlers | Yes | Only to target individual AI crawlers |
-| Protect static resources | Yes | No |
-| Optimize for WordPress | Yes | No |
+| Feature                                         | Handled by bot settings | Requires custom rules                                    |
+| ----------------------------------------------- | ----------------------- | -------------------------------------------------------- |
+| Block or challenge definitely automated traffic | Yes                     | Only for path-specific or threshold-tuned rules          |
+| Block or challenge likely automated traffic     | Not available on Pro    | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
+| Allow or block verified bots                    | Yes                     | No                                                       |
+| Block AI crawlers                               | Yes                     | Only to target individual AI crawlers                    |
+| Protect static resources                        | Yes                     | No                                                       |
+| Optimize for WordPress                          | Yes                     | No                                                       |
 
-For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
\ No newline at end of file
+For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
diff --git a/src/content/partials/bots/bots-ad.mdx b/src/content/partials/bots/bots-ad.mdx
index da728dfe8e0016d..f690a31c6f51ec3 100644
--- a/src/content/partials/bots/bots-ad.mdx
+++ b/src/content/partials/bots/bots-ad.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Deprecation notice]
diff --git a/src/content/partials/bots/bots-cookie.mdx b/src/content/partials/bots/bots-cookie.mdx
index 43bda678f796566..62c2872d9a483c0 100644
--- a/src/content/partials/bots/bots-cookie.mdx
+++ b/src/content/partials/bots/bots-cookie.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare uses the `__cf_bm` cookie to smooth out the <GlossaryTooltip term="bot score">bot score</GlossaryTooltip> and reduce false positives for actual user sessions.
 
diff --git a/src/content/partials/bots/bots-heuristics.mdx b/src/content/partials/bots/bots-heuristics.mdx
index 4cd143b9744bd18..be4df17066ad18c 100644
--- a/src/content/partials/bots/bots-heuristics.mdx
+++ b/src/content/partials/bots/bots-heuristics.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
\ No newline at end of file
+The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
diff --git a/src/content/partials/bots/bots-jsd.mdx b/src/content/partials/bots/bots-jsd.mdx
index 0db49de66e6f82f..7256269923ab642 100644
--- a/src/content/partials/bots/bots-jsd.mdx
+++ b/src/content/partials/bots/bots-jsd.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The [**JavaScript Detections (JSD)**](/bots/additional-configurations/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines.
diff --git a/src/content/partials/bots/bots-ml.mdx b/src/content/partials/bots/bots-ml.mdx
index df1136f568be04c..a14e20442d1ecca 100644
--- a/src/content/partials/bots/bots-ml.mdx
+++ b/src/content/partials/bots/bots-ml.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
 The **Machine Learning (ML)** engine accounts for the majority of all detections, distinguishing between human and bot traffic. This approach leverages our global network, which proxies billions of requests daily, to identify both automated and human traffic.
 
-The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99). 
+The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99).
 
 The core model relies on the following process:
 
 - Input Variables (X): Various request features (headers, session characteristics, and browser signals) collected from traffic across the Cloudflare network.
 - Output Variable (Y): The predicted probability that a client is human (such as the probability of successfully solving a Challenge). This probability is mapped to the final 1–99 Bot Score.
 
-We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
\ No newline at end of file
+We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
diff --git a/src/content/partials/bots/buttons-plan-pages.mdx b/src/content/partials/bots/buttons-plan-pages.mdx
index f4bb5390173d743..fcacd4331504ccc 100644
--- a/src/content/partials/bots/buttons-plan-pages.mdx
+++ b/src/content/partials/bots/buttons-plan-pages.mdx
@@ -1,8 +1,18 @@
 ---
 {}
-
 ---
 
-import { LinkButton } from "~/components"
+import { LinkButton } from "~/components";
 
- <LinkButton variant="primary" href="/bots/plans/free/">Free</LinkButton> <LinkButton variant="primary" href="/bots/plans/pro/">Pro</LinkButton> <LinkButton variant="primary" href="/bots/plans/biz-and-ent/">Business</LinkButton> <LinkButton variant="primary" href="/bots/plans/bm-subscription/">Bot Management for Enterprise</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/free/">
+	Free
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/pro/">
+	Pro
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/biz-and-ent/">
+	Business
+</LinkButton>
+<LinkButton variant="primary" href="/bots/plans/bm-subscription/">
+	Bot Management for Enterprise
+</LinkButton>
diff --git a/src/content/partials/bots/content-security-policy-limitation.mdx b/src/content/partials/bots/content-security-policy-limitation.mdx
index f62345793fe5368..e42c9647319100a 100644
--- a/src/content/partials/bots/content-security-policy-limitation.mdx
+++ b/src/content/partials/bots/content-security-policy-limitation.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from '~/components';
+import { GlossaryTooltip } from "~/components";
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip>, you need to take additional steps to implement JavaScript Detections:
 
@@ -16,4 +15,4 @@ If you have a <GlossaryTooltip term="content security policy (CSP)">Content Secu
 :::caution[Warning]
 
 JavaScript Detections is not supported with `nonce` set via `<meta>` tags.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/bots/disable-cf-bm-cookie.mdx b/src/content/partials/bots/disable-cf-bm-cookie.mdx
index a19d23bd96c3778..3e1a4f6255413c8 100644
--- a/src/content/partials/bots/disable-cf-bm-cookie.mdx
+++ b/src/content/partials/bots/disable-cf-bm-cookie.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can disable the `__cf_bm` cookie using the `bm_cookie_enabled` field [via the API](/api/resources/bot_management/methods/update/).
diff --git a/src/content/partials/bots/endpoint-label-warning.mdx b/src/content/partials/bots/endpoint-label-warning.mdx
index 3e0748847f1cfbc..1d94ff8d3590322 100644
--- a/src/content/partials/bots/endpoint-label-warning.mdx
+++ b/src/content/partials/bots/endpoint-label-warning.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: endpoint
-
 ---
 
 :::caution[Login {props.one} endpoints]
-Not all login {props.one} endpoints are automatically detected. 
+Not all login {props.one} endpoints are automatically detected.
 
-Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized. 
+Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized.
 
 For example, if you have a non-traditional login endpoint, you should label it with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/). Once you have applied the `cf-log-in` label, Cloudflare will use the labeled endpoint for account takeover detection decisions.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/bots/execution-order.mdx b/src/content/partials/bots/execution-order.mdx
index 458ad91c88f6909..4d3aa8ec0155216 100644
--- a/src/content/partials/bots/execution-order.mdx
+++ b/src/content/partials/bots/execution-order.mdx
@@ -7,4 +7,4 @@ flowchart LR
 accTitle: Super Bot Fight Mode and custom rules execution order diagram
 accDescr: This diagram details the execution order of custom rules before Super Bot Fight Mode managed rules.
 A[Custom rules] --> B[Block AI bots<br>managed rule] --> C[Other SBFM managed rules]
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/bots/flexible-sbfm.mdx b/src/content/partials/bots/flexible-sbfm.mdx
index 207bbda9d1f29ee..d5c7abc133997b6 100644
--- a/src/content/partials/bots/flexible-sbfm.mdx
+++ b/src/content/partials/bots/flexible-sbfm.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-In parts of your site where you want bot traffic, you can use the [*Skip* action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
+In parts of your site where you want bot traffic, you can use the [_Skip_ action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
 
 You can use the [Rules language](/ruleset-engine/rules-language/) and its [operators](/ruleset-engine/rules-language/operators/) and [fields](/ruleset-engine/rules-language/fields/) in custom rules to configure a scoped rule for approved automated traffic in Super Bot Fight Mode.
diff --git a/src/content/partials/bots/ja3-ja4-null.mdx b/src/content/partials/bots/ja3-ja4-null.mdx
index 68bc0569df18296..e8829ace2150293 100644
--- a/src/content/partials/bots/ja3-ja4-null.mdx
+++ b/src/content/partials/bots/ja3-ja4-null.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or empty in logs under specific circumstances:
@@ -9,4 +8,4 @@ The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or emp
 - The field may be empty when a [Worker](/workers/) sends a request to a zone that is either internal to Cloudflare's network (O2O traffic that is not proxied) or to a third-party origin, or when a Worker is routing traffic to the target zone.
 - The fingerprints may be absent when Bot Management itself is skipped for a request, as the feature is responsible for calculating and populating these values.
 
-Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
\ No newline at end of file
+Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
diff --git a/src/content/partials/bots/jsd-availability.mdx b/src/content/partials/bots/jsd-availability.mdx
index 57c501ca55fd5a0..3306814fd548d25 100644
--- a/src/content/partials/bots/jsd-availability.mdx
+++ b/src/content/partials/bots/jsd-availability.mdx
@@ -1,6 +1,5 @@
 ---
 inputParameters: planType;;enablement
-
 ---
 
-For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
\ No newline at end of file
+For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
diff --git a/src/content/partials/bots/plan-get-started.mdx b/src/content/partials/bots/plan-get-started.mdx
index ab81f675f77e822..3e26918905eccd4 100644
--- a/src/content/partials/bots/plan-get-started.mdx
+++ b/src/content/partials/bots/plan-get-started.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To get started, review our [setup guides](/bots/get-started/). If you have any questions, visit the [community](https://community.cloudflare.com/) to engage with other Cloudflare users.
diff --git a/src/content/partials/bots/plan-intro.mdx b/src/content/partials/bots/plan-intro.mdx
index e2f77067f05bc6d..0b5da491920a683 100644
--- a/src/content/partials/bots/plan-intro.mdx
+++ b/src/content/partials/bots/plan-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To learn more about features and functionality, select a plan.
diff --git a/src/content/partials/bots/sequence-rules.mdx b/src/content/partials/bots/sequence-rules.mdx
index 5a37ee6b8ddf181..f1469b3b97b7941 100644
--- a/src/content/partials/bots/sequence-rules.mdx
+++ b/src/content/partials/bots/sequence-rules.mdx
@@ -1,6 +1,9 @@
 ---
 inputParameters: addLink;;Link
-
 ---
 
-<a href={props.two}>{props.one}</a> uses cookies to track the order of requests a user has made and the time between requests and makes them available via [Cloudflare Rules](/rules/). This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
+<a href={props.two}>{props.one}</a> uses cookies to track the order of requests
+a user has made and the time between requests and makes them available via
+[Cloudflare Rules](/rules/). This allows you to write rules that match valid or
+invalid sequences. The specific cookies used to validate sequences are called
+sequence cookies.
diff --git a/src/content/partials/bots/signals-intelligence-and-ja4.mdx b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
index d4985540fd03195..5f9750c2e03b2f8 100644
--- a/src/content/partials/bots/signals-intelligence-and-ja4.mdx
+++ b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 If you want to use JA4 fingerprints and Signals Intelligence, your Workers script must be able to handle the absence of any field in the array, including:
 
-* The possibility that the JA4 fingerprint could be missing.
-* The possibility that the `ja4Signals` array could be missing.
-* Results with `NaN` or `Infinity` values will be excluded from the array.
+- The possibility that the JA4 fingerprint could be missing.
+- The possibility that the `ja4Signals` array could be missing.
+- Results with `NaN` or `Infinity` values will be excluded from the array.
diff --git a/src/content/partials/bots/verified-bots.mdx b/src/content/partials/bots/verified-bots.mdx
index 643ff4708ca88c8..641b00e41848448 100644
--- a/src/content/partials/bots/verified-bots.mdx
+++ b/src/content/partials/bots/verified-bots.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare maintains an internal directory of [verified bot](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/) that are associated with search engine optimization (SEO), website monitoring, and more.
diff --git a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
index d6d1aa6348cc9ab..6674b5b0b076f4f 100644
--- a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
+++ b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
@@ -3,13 +3,14 @@
 If you set a large viewport width and height, your screenshot may appear blurry or pixelated. This can happen if your browser's default `deviceScaleFactor` (which defaults to 1) is not high enough for the viewport.
 
 To fix this, increase the value of the `deviceScaleFactor`.
+
 ```json
 {
-  "url": "https://cloudflare.com/",
-  "viewport": {
-    "width": 3600,
-    "height": 2400,
-    "deviceScaleFactor": 2
-  }
+	"url": "https://cloudflare.com/",
+	"viewport": {
+		"width": 3600,
+		"height": 2400,
+		"deviceScaleFactor": 2
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/byoip/cloudflare-asn-callout.mdx b/src/content/partials/byoip/cloudflare-asn-callout.mdx
index c4c4f51e5e3f276..c2e64662ef201ba 100644
--- a/src/content/partials/byoip/cloudflare-asn-callout.mdx
+++ b/src/content/partials/byoip/cloudflare-asn-callout.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Use Cloudflare's ASN]
 The process described on this page only supports using Cloudflare's ASN (AS13335). If you must announce the prefixes under your own ASN, contact your account team.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/byoip/loa.mdx b/src/content/partials/byoip/loa.mdx
index c4320799ddc0c7b..6f4223cd8341462 100644
--- a/src/content/partials/byoip/loa.mdx
+++ b/src/content/partials/byoip/loa.mdx
@@ -35,4 +35,4 @@ Regards,
 [COMPANY NAME]
 [COMPANY ADDRESS]
 [COMPANY STAMP]
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/byoip/validate-prefix-endpoint.mdx b/src/content/partials/byoip/validate-prefix-endpoint.mdx
index 096f54fc687f97e..3d0fbbd3b42c0d2 100644
--- a/src/content/partials/byoip/validate-prefix-endpoint.mdx
+++ b/src/content/partials/byoip/validate-prefix-endpoint.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
diff --git a/src/content/partials/cache/cache-reserve-billing-note.mdx b/src/content/partials/cache/cache-reserve-billing-note.mdx
index 1d60713a3590fee..6f0fbe8ec743390 100644
--- a/src/content/partials/cache/cache-reserve-billing-note.mdx
+++ b/src/content/partials/cache/cache-reserve-billing-note.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 The billable quantity is rounded up to the nearest million.
 
-
 :::
diff --git a/src/content/partials/cache/cache-reserve-eligibility.mdx b/src/content/partials/cache/cache-reserve-eligibility.mdx
index 4222abac1e72533..426e01aee0d369e 100644
--- a/src/content/partials/cache/cache-reserve-eligibility.mdx
+++ b/src/content/partials/cache/cache-reserve-eligibility.mdx
@@ -7,4 +7,4 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 - Be cacheable, according to Cloudflare's standard [cacheability factors](/cache/).
 - Have a freshness time-to-live (TTL) of at least 10 hours (set by any means such as Cache-Control / [CDN-Cache-Control](/cache/concepts/cache-control/) origin response headers, [Edge Cache TTL](/cache/how-to/edge-browser-cache-ttl/#edge-cache-ttl), [Cache TTL By Status](/cache/how-to/configure-cache-status-code/), or [Cache Rules](/cache/how-to/cache-rules/)),
 - Have a Content-Length response header.
-- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
\ No newline at end of file
+- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
diff --git a/src/content/partials/cache/cache-reserve-intro.mdx b/src/content/partials/cache/cache-reserve-intro.mdx
index e2f420e60a81457..d4dd113880b158a 100644
--- a/src/content/partials/cache/cache-reserve-intro.mdx
+++ b/src/content/partials/cache/cache-reserve-intro.mdx
@@ -4,4 +4,4 @@
 
 Cache Reserve is a large, persistent data store [implemented on top of R2](/r2/). By pushing a single button in the dashboard, your website's cacheable content will be written to Cache Reserve.
 
-In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
\ No newline at end of file
+In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
diff --git a/src/content/partials/cache/cache-reserve-limits.mdx b/src/content/partials/cache/cache-reserve-limits.mdx
index e98031a3e1fb9ba..a8fa9e8ea8c5d44 100644
--- a/src/content/partials/cache/cache-reserve-limits.mdx
+++ b/src/content/partials/cache/cache-reserve-limits.mdx
@@ -7,4 +7,4 @@
 - [Vary for images](/cache/advanced-configuration/vary-for-images/) is currently not compatible with Cache Reserve.
 - Requests to [R2 public buckets linked to a zone's domain](/r2/buckets/public-buckets/) will not use Cache Reserve. Enabling Cache Reserve for the connected zone will use Cache Reserve only for requests not destined for the R2 bucket.
 - Cache Reserve makes requests for uncompressed content directly from the origin. Unlike the standard Cloudflare CDN, Cache Reserve does not include the `Accept-Encoding: gzip` header when sending requests to the origin.
-- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
\ No newline at end of file
+- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
diff --git a/src/content/partials/cache/cache-reserve-operations.mdx b/src/content/partials/cache/cache-reserve-operations.mdx
index 7d9ec8cabea8443..ebbfac04358fb8a 100644
--- a/src/content/partials/cache/cache-reserve-operations.mdx
+++ b/src/content/partials/cache/cache-reserve-operations.mdx
@@ -22,4 +22,4 @@ Other purge methods, such as purge by tag, host, prefix, or purge everything wil
 
 :::note
 Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cache/edge-ttl.mdx b/src/content/partials/cache/edge-ttl.mdx
index 1a84b61e6d0f948..02f8bc5af24dabe 100644
--- a/src/content/partials/cache/edge-ttl.mdx
+++ b/src/content/partials/cache/edge-ttl.mdx
@@ -12,4 +12,4 @@ By default, Cloudflare caches certain HTTP response codes with the following Ed
 | 302, 303         | 20m         |
 | 404, 410         | 3m          |
 
-All other status codes are not cached by default.
\ No newline at end of file
+All other status codes are not cached by default.
diff --git a/src/content/partials/cache/regional-tiered-cache.mdx b/src/content/partials/cache/regional-tiered-cache.mdx
index 2da23da74a44c6f..84f6ff7440bd316 100644
--- a/src/content/partials/cache/regional-tiered-cache.mdx
+++ b/src/content/partials/cache/regional-tiered-cache.mdx
@@ -4,4 +4,4 @@
 
 Regional Tiered Cache provides an additional layer of caching for customers who have a global traffic footprint and want to serve content faster by avoiding network latency when there is a cache `MISS` in a lower-tier, resulting in an upper-tier fetch in a data center located far away.
 
-Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
\ No newline at end of file
+Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
diff --git a/src/content/partials/cache/smart-tiered-cache.mdx b/src/content/partials/cache/smart-tiered-cache.mdx
index f7feae4ba341a37..4cadd0acc82f9d2 100644
--- a/src/content/partials/cache/smart-tiered-cache.mdx
+++ b/src/content/partials/cache/smart-tiered-cache.mdx
@@ -14,4 +14,4 @@ While Smart Tiered Cache selects one Upper Tier per origin, when using Load Bala
 
 #### Caveats
 
-You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
\ No newline at end of file
+You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
diff --git a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
index d395290564350e8..38bc50594dca1b0 100644
--- a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
+++ b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
@@ -8,4 +7,4 @@
 [JavaScript detections](/bots/additional-configurations/javascript-detections/) are stored in the `cf_clearance` cookie.
 
 The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
index a4d3b6a8833f777..3e1cf935e85c7fd 100644
--- a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
+++ b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/). 
+You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/).
 
-Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/). 
\ No newline at end of file
+Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/).
diff --git a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
index ecd1e00cd105b61..6b6ee7d8e7a6954 100644
--- a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With [apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/), SaaS customers need to create an `A` record for their hostname that points to the IP prefix allocated to the SaaS provider's account.
@@ -11,8 +10,6 @@ example.com.  60  IN  A   192.0.2.1
 
 :::note
 
-
 For [BYOIP](/byoip/) customers, Cloudflare automatically enables the Apex Proxy Access feature on your BYOIP block, which allows Custom Hostnames to be activated via [Apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) when Authoritative DNS for a customer's hostname targets any IP addresses in your BYOIP block.
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
index cc1caa4a35ce4a3..e442ded8479e150 100644
--- a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Most customers will have a `CNAME` target, which requires their customers to create a `CNAME` record similar to:
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
index c72ac1bf7f7c156..b778c86451909e7 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
@@ -1,12 +1,10 @@
 ---
 {}
-
 ---
 
 1. To create a custom hostname using the API, use the [Create Custom Hostname](/api/resources/custom_hostnames/methods/create/) endpoint.
+   - You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
 
-   * You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
-
-2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`.  It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
+2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`. It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
 
 The response contains the complete definition of the new custom hostname.
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
index e70192ef25ae6e5..6c4d2491a949000 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
@@ -1,15 +1,12 @@
 ---
 {}
-
 ---
 
 :::note[Default behavior]
 
-
 When you create a custom hostname:
 
-* If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
-* If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
-
+- If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
+- If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
 
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
index 5734dd54f9b5277..0e5a5aff297fbc1 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,10 +10,10 @@ import { DashButton } from "~/components";
 
 2. Select **Add Custom Hostname**.
 3. Add your customer's hostname `app.customer.com` and set the relevant options, including:
-    - The [minimum TLS version](/ssl/reference/protocols/).
-    - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
-    - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
-    - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
-    - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
-    - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
+   - The [minimum TLS version](/ssl/reference/protocols/).
+   - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
+   - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
+   - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+   - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
+   - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
 4. Select **Add Custom Hostname**.
diff --git a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
index 8d09df2ede8e363..2d204cd4201372c 100644
--- a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 A **custom origin server** lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback, such as:
 
-* `soap.stores.com` goes to `origin1.com`
-* `towel.stores.com` goes to `origin2.com`
+- `soap.stores.com` goes to `origin1.com`
+- `towel.stores.com` goes to `origin2.com`
diff --git a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
index dd9e0a9dbf02a89..de24df450fd2452 100644
--- a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
+++ b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
index f75a9b302889462..b93ff80e6e1c8a8 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you first [enable](/cloudflare-for-platforms/cloudflare-for-saas/start/enable/) Cloudflare for SaaS, you need to perform a few steps prior to creating any custom hostnames.
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
index d0487c9804e2705..cfac6c51968d0bb 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render, TabItem, Tabs } from "~/components"
+import { Render, TabItem, Tabs } from "~/components";
 
 You need to perform the following steps for each custom hostname.
 
@@ -50,8 +49,6 @@ To create a custom hostname:
 
 :::note
 
-
 <Render file="issue-certs-preamble" product="cloudflare-for-platforms" />
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
index e69030364c61734..76408b768cb0721 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: planReqs
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 ## Before you begin
 
@@ -14,5 +13,5 @@ Before you start creating custom hostnames:
 3. Review the [Hostname prioritization guidelines](/ssl/reference/certificate-and-hostname-priority/#hostname-priority). Wildcard custom hostnames behave differently than an exact hostname match.
 4. (optional) Review the following documentation:
 
-* [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
-* [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+- [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
+- [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
index 82d0fca0621c733..35edd6886fe0424 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your customer is also using Cloudflare for their domain, they should keep their DNS record pointing to your SaaS provider in place for as long as they want to use your service.
diff --git a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
index 93a809da7f02598..ea5860cd4a1012d 100644
--- a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 Specific (non-wildcard) custom hostnames can use [HTTP based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/http/) for certificate renewals, as long as:
 
-* The hostname is pointing to the SaaS provider.
-* The hostname's traffic is proxying through the Cloudflare network.
+- The hostname is pointing to the SaaS provider.
+- The hostname's traffic is proxying through the Cloudflare network.
 
 If your custom hostnames do not meet these requirements, use another validation method.
diff --git a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
index 3bb70a1297de1a6..7f9762bab2589d4 100644
--- a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For each custom hostname, Cloudflare issues two certificates bundled in chains that maximize browser compatibility (unless you [upload custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/)).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
index 1d723d8f9826ad2..1e684db0ea49bf0 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
 
-* [Caching](/cache/)
-* [Workers](/workers/)
-* [Rules](/rules/)
+- [Caching](/cache/)
+- [Workers](/workers/)
+- [Rules](/rules/)
 
 For a full list of compatible products and potential limitations, refer to [Product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
index 343e065d9148425..1e0fb535dd18bf6 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
@@ -9,4 +9,4 @@ If your own Cloudflare zone is on the Enterprise plan, you have access to the [z
 
 To successfully activate the custom hostname on {props.providerName}, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to {props.providerName}, only the subfeature titled **Also prevent Subdomains** needs to be temporarily disabled.
 
-Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
\ No newline at end of file
+Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
diff --git a/src/content/partials/cloudflare-for-platforms/regional-services.mdx b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
index ee7ffcc908b6aac..c636d4b3c92b405 100644
--- a/src/content/partials/cloudflare-for-platforms/regional-services.mdx
+++ b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you have [regional services](/data-localization/regional-services/) set up for your custom hostnames, Cloudflare always uses the processing region associated with your DNS target record (instead of the processing region of any [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/)).
diff --git a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
index b4bb3909a232e68..092651f810975a3 100644
--- a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
+++ b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your SaaS domain is also a [domain using Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/), you can use your Cloudflare DNS to remove your domain from your SaaS provider.
diff --git a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
index d99a28f10dcf5ed..22b6eab5814cf27 100644
--- a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
+++ b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
\ No newline at end of file
+Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
index b78a7aab90c363e..f92949ab320cc09 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you [create a new hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/issue-certificates/) and choose this validation method, you will see the following values after a few seconds:
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
index 7c01800301e8819..0d895b1350d6147 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare's network to your customers via their own custom or vanity domains.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
index 44c1c73202134c3..cc44b4ab26564b0 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Only certain customers have access to this feature. For more details, see the [Plans page](/cloudflare-for-platforms/cloudflare-for-saas/plans/).
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
index 86394cc77e6b615..6d0ccd57fab6aec 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you would like to request an immediate recheck, [rather than wait for the next retry](/ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/), send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) with the same values as your initial `POST` request.
diff --git a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
index 39515e01e4e3b0a..04ae68397c36d17 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Wildcard custom hostnames require TXT-based validation. As the SaaS provider, you have two options for wildcard custom hostname certificate renewals:
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
index 37093f6529689dd..50ebce2cda146e9 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can access these tokens using the API with the [`GET` custom hostnames endpoint](/api/resources/custom_hostnames/methods/list/).
@@ -9,46 +8,46 @@ For example, here are two tokens highlighted in the API response for a **wildcar
 
 ```json title="Response" {11,12,13,14,15,16,17,18,19,20,21,22}
 {
-  "result": [
-    {
-      "id": "<HOSTNAME_ID>",
-      "hostname": "<HOSTNAME>",
-      "ssl": {
-        "id": "<CERTIFICATE_ID>",
-        "type": "dv",
-        "method": "txt",
-        "status": "pending_validation",
-        "validation_records": [
-          {
-            "status": "pending",
-            "txt_name": "_acme-challenge.<HOSTNAME>",
-            "txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
-          },
-          {
-            "status": "pending",
-            "txt_name": "_acme-challenge.<HOSTNAME>",
-            "txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
-          }
-        ],
-        "settings": {
-          "min_tls_version": "1.0"
-        },
-        "bundle_method": "ubiquitous",
-        "wildcard": true,
-        "certificate_authority": "google"
-      },
-      "status": "pending",
-      "ownership_verification": {
-        "type": "txt",
-        "name": "_cf-custom-hostname.<HOSTNAME>",
-        "value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-      },
-      "ownership_verification_http": {
-        "http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
-        "http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-      },
-      "created_at": "2022-10-06T19:35:33.143257Z"
-    }
-  ]
+	"result": [
+		{
+			"id": "<HOSTNAME_ID>",
+			"hostname": "<HOSTNAME>",
+			"ssl": {
+				"id": "<CERTIFICATE_ID>",
+				"type": "dv",
+				"method": "txt",
+				"status": "pending_validation",
+				"validation_records": [
+					{
+						"status": "pending",
+						"txt_name": "_acme-challenge.<HOSTNAME>",
+						"txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
+					},
+					{
+						"status": "pending",
+						"txt_name": "_acme-challenge.<HOSTNAME>",
+						"txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
+					}
+				],
+				"settings": {
+					"min_tls_version": "1.0"
+				},
+				"bundle_method": "ubiquitous",
+				"wildcard": true,
+				"certificate_authority": "google"
+			},
+			"status": "pending",
+			"ownership_verification": {
+				"type": "txt",
+				"name": "_cf-custom-hostname.<HOSTNAME>",
+				"value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+			},
+			"ownership_verification_http": {
+				"http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
+				"http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+			},
+			"created_at": "2022-10-06T19:35:33.143257Z"
+		}
+	]
 }
 ```
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
index 1b2e4694b7a24a3..b813a3302da20ca 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
index 45dff2d23eddc00..88015281280b9e2 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 Your customers should place these at their authoritative DNS provider under the `"_acme-challenge"` DNS label. Once these TXT records are in place, validation and certificate issuance will automatically complete.
 
 :::note
 
-
 These tokens are different than the hostname validation tokens.
 
-
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
index ff44799c97955f9..b28cac12e8c8a6e 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 These tokens can be fetched through the API or the dashboard when the certificates are in a [pending validation](/ssl/reference/certificate-statuses/#new-certificates) state during custom hostname creation or during certificate renewals.
diff --git a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
index 62c3d6a6525d69f..df573c1be7cd67a 100644
--- a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
+++ b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your hostname is using another validation method, you will need to [update](/api/resources/custom_hostnames/methods/edit/) the `"method"` field in the SSL object to be `"txt"`.
diff --git a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
index e0c4b7896a69330..a7d0a8eb53a6049 100644
--- a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To validate a certificate on a wildcard custom hostname, you should either set up [Delegated DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv/) or [TXT-based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/).
diff --git a/src/content/partials/cloudflare-one/access/access-block-page.mdx b/src/content/partials/cloudflare-one/access/access-block-page.mdx
index 0330f3335eae871..42cdfd762ed89a7 100644
--- a/src/content/partials/cloudflare-one/access/access-block-page.mdx
+++ b/src/content/partials/cloudflare-one/access/access-block-page.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 **Custom block pages**: Choose what users will see when they are denied access to the application.
 
-* **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
-* **Redirect URL**: Redirect to the specified website.
-* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
+- **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
+- **Redirect URL**: Redirect to the specified website.
+- **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
diff --git a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
index 8c24f29e8151dc8..ed3f8e126327b44 100644
--- a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
+++ b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
@@ -11,14 +11,15 @@ params:
 
 4. In **Certificate content**, paste the contents of your root CA.
 
-	If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
-	```txt
-	-----BEGIN CERTIFICATE-----
-	<intermediate.pem>
-	-----END CERTIFICATE-----
-	-----BEGIN CERTIFICATE-----
-	<rootCA.pem>
-	-----END CERTIFICATE-----
-	```
+   If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
 
-	{ props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
\ No newline at end of file
+   ```txt
+   -----BEGIN CERTIFICATE-----
+   <intermediate.pem>
+   -----END CERTIFICATE-----
+   -----BEGIN CERTIFICATE-----
+   <rootCA.pem>
+   -----END CERTIFICATE-----
+   ```
+
+   { props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
diff --git a/src/content/partials/cloudflare-one/access/add-target.mdx b/src/content/partials/cloudflare-one/access/add-target.mdx
index 744e5212117cbde..e96d8060689cd6f 100644
--- a/src/content/partials/cloudflare-one/access/add-target.mdx
+++ b/src/content/partials/cloudflare-one/access/add-target.mdx
@@ -3,15 +3,22 @@ params:
   - protocol
 ---
 
-import { Tabs, TabItem, Render, Details, APIRequest, GlossaryTooltip } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	Details,
+	APIRequest,
+	GlossaryTooltip,
+} from "~/components";
 
 A target represents a single resource in your infrastructure (such as a server, Kubernetes cluster, database, or container) that users will connect to through Cloudflare.
 
 {
-  props.protocol === "rdp" ? (
-		<p> Create a target for each Windows machine that requires RDP access.
+props.protocol === "rdp" ? (
+<p> Create a target for each Windows machine that requires RDP access.
 To create a new target:</p>) :
-	(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
+(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
 }
 
 <Tabs syncKey="dashPlusAPI">
@@ -86,4 +93,4 @@ The following example requires Cloudflare provider version `>=4.45.0`.
 </TabItem>
 </Tabs>
 
-Next, create an Access application to secure the target.
\ No newline at end of file
+Next, create an Access application to secure the target.
diff --git a/src/content/partials/cloudflare-one/access/app-launcher.mdx b/src/content/partials/cloudflare-one/access/app-launcher.mdx
index 7e555517f94da72..b4f2bad751637b9 100644
--- a/src/content/partials/cloudflare-one/access/app-launcher.mdx
+++ b/src/content/partials/cloudflare-one/access/app-launcher.mdx
@@ -54,8 +54,8 @@ To show an Access application in the App Launcher:
 
 6.  In **Application domains**, choose a domain to use for the App Launcher link.
 
-7. (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
+7.  (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
 
 ## Customize App Launcher appearance
 
-To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
\ No newline at end of file
+To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx
index 5090f69c89745fd..f34af47cbd7d9e0 100644
--- a/src/content/partials/cloudflare-one/access/bookmarks.mdx
+++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With Cloudflare One, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
@@ -56,4 +55,4 @@ If you attempt to assign a policy that uses an unsupported feature, the dashboar
 
 :::tip[Device posture policies]
 To show bookmarks only to users on managed devices, assign a policy that requires device posture checks (such as [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)). The bookmark will only appear in the App Launcher for users whose devices satisfy the posture requirements.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/create-service-token.mdx b/src/content/partials/cloudflare-one/access/create-service-token.mdx
index 048dfc0204abc20..1fa69e143298c53 100644
--- a/src/content/partials/cloudflare-one/access/create-service-token.mdx
+++ b/src/content/partials/cloudflare-one/access/create-service-token.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Tabs, TabItem, Details, APIRequest } from '~/components';
+import { Tabs, TabItem, Details, APIRequest } from "~/components";
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
index ad31a3a9469c5c2..5eafbf7d586642f 100644
--- a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
@@ -4,7 +4,7 @@ params:
   - supportgroups?
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Identity providers**.
 
@@ -14,12 +14,12 @@ import { Markdown } from "~/components"
 
 4. (Optional) Configure the following settings:
 
-* **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
-* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
-* **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
-	- _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
-	- _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
-	- _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
+- **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
+- **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
+- **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
+  - _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
+  - _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
+  - _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
 
 5. Select **Regenerate Secret**. Copy the **SCIM Endpoint** and **SCIM Secret**. You will need to enter these values into {props.idp}.
 
diff --git a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
index 7c3cd7116b2f389..4b7ad4e06edeccf 100644
--- a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
+++ b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
@@ -2,7 +2,6 @@
 {}
 ---
 
-
 ```tf
 resource "cloudflare_zero_trust_access_identity_provider" "microsoft_entra_id" {
 	account_id = var.cloudflare_account_id
diff --git a/src/content/partials/cloudflare-one/access/idp-integration.mdx b/src/content/partials/cloudflare-one/access/idp-integration.mdx
index d72214326c20f10..183354135c18212 100644
--- a/src/content/partials/cloudflare-one/access/idp-integration.mdx
+++ b/src/content/partials/cloudflare-one/access/idp-integration.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Render, Tabs, TabItem} from "~/components"
+import { Render, Tabs, TabItem } from "~/components";
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -33,4 +33,4 @@ import {Render, Tabs, TabItem} from "~/components"
 
 		<Render file="access/idp-integration-note" product="cloudflare-one" params={{verb: "use" }} />
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
index 1963b122d60ac7e..d87a8bf152d7198 100644
--- a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
+++ b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Your browser must [allow third-party cookies](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#allow-third-party-cookies-in-the-browser) on the application domain.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
index 0c88cd0f401e32d..6383efe24af3bc3 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
@@ -1,13 +1,12 @@
 ---
 inputParameters: uiLocation;;stepIntro
-
 ---
 
 1. In Miro, select your profile picture > **Settings** > <strong>{props.one}</strong>.
 2. Turn on **SSO/SAML**.
 3. Fill in the following fields:
-   * **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
-   * **Key x509 Certificate**: Public key from application configuration in Cloudflare One
+   - **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
+   - **Key x509 Certificate**: Public key from application configuration in Cloudflare One
 4. In **Domain**, enter the domain you want to configure SSO for and select **Enter**.
 5. {props.two} an email address from that domain and select **send verification**.
 6. Once you receive a verification email, select the link in the email, then select **Save**. When the domain is successfully configured, the **VERIFY EMAIL** label next to the domain in the SSO/SAML configuration page will disappear.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
index ae78bb666c48d5b..ef59bdce1e4d853 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
@@ -4,4 +4,4 @@ params:
   - token
 ---
 
-{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
\ No newline at end of file
+{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
index 4c14a8d7ee82fc2..8d954a610155794 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Enable Cloudflare Access as an identity provider on your Salesforce domain:
diff --git a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
index 0aaa9e7f0ecc8c3..9ef968d9aade80a 100644
--- a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
+++ b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
@@ -4,4 +4,4 @@
 
 :::note
 New users must first [register the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/) or authenticate to an Access application before SCIM provisioning can begin.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
index 3407640eddab5ff..eab1fcef7940eb3 100644
--- a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
+++ b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To secure your origin, you must validate the [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/) issued by Cloudflare Access. Token validation ensures that any requests which bypass Cloudflare Access (for example, due to a network misconfiguration) are rejected.
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
index 759ae3cd92c090e..58d1b77d29be1f9 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - [**Cross-Origin Resource Sharing (CORS) settings**](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors/)
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
index abb27fd686a9a68..4e0f540d68c6438 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 Ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
index c7820c683885328..6ff71b18c02ad6d 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
@@ -13,21 +12,29 @@ import { Render } from "~/components"
 
 4. Select **Add public hostname**.
 
-5. <Render file="access/self-hosted-app/choose-domain" product="cloudflare-one" />
+5. <Render
+   	file="access/self-hosted-app/choose-domain"
+   	product="cloudflare-one"
+   />
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-7. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "public" }}/>
+7. <Render
+   	file="access/access-choose-idps"
+   	product="cloudflare-one"
+   	params={{ appType: "public" }}
+   />
 
 8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
 9. <Render file="access/session-duration" product="cloudflare-one" />
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-
-	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-	- <Render file="access/access-block-page" product="cloudflare-one" />
-	<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
+    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+    - <Render file="access/access-block-page" product="cloudflare-one" />
+      <Render
+      	file="access/self-hosted-app/advanced-settings"
+      	product="cloudflare-one"
+      />
 
 11. Select **Create**.
-
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
index 9c4a7b36eb13bf2..427717a9cdab7ee 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
@@ -1,14 +1,14 @@
 ---
 {}
-
 ---
+
 When using Access self-hosted applications, the majority of Cloudflare products will be compatible with your application.
 
 However, the following products are not supported:
 
-* [Automatic Platform Optimization](/automatic-platform-optimization)
-* [Zaraz](/zaraz)
-* [Google tag gateway for advertisers](/google-tag-gateway)
+- [Automatic Platform Optimization](/automatic-platform-optimization)
+- [Zaraz](/zaraz)
+- [Google tag gateway for advertisers](/google-tag-gateway)
 
 You can disable Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain.
 
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
index 1f73a0a13cfd29a..af5476bb1880972 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
\ No newline at end of file
+Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
diff --git a/src/content/partials/cloudflare-one/access/session-duration.mdx b/src/content/partials/cloudflare-one/access/session-duration.mdx
index ac75de0b9aa9cfa..77ec2d4a99238d0 100644
--- a/src/content/partials/cloudflare-one/access/session-duration.mdx
+++ b/src/content/partials/cloudflare-one/access/session-duration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 In **Session Duration**, choose how often the user's [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token/) should expire.
diff --git a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
index c53f9130b03a46d..21858eabcee3e1e 100644
--- a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
+++ b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
@@ -3,6 +3,6 @@ params:
   - intro
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
\ No newline at end of file
+{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
diff --git a/src/content/partials/cloudflare-one/access/tags.mdx b/src/content/partials/cloudflare-one/access/tags.mdx
index 0afe99bdc346ec1..77a811446a51a56 100644
--- a/src/content/partials/cloudflare-one/access/tags.mdx
+++ b/src/content/partials/cloudflare-one/access/tags.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can label an Access application with up to 25 custom tags. End users can then filter the applications in their [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) by their tags.
diff --git a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
index 90d56df296e1cc3..bfb96fb10ada920 100644
--- a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
+++ b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
@@ -6,4 +6,4 @@ import { Render } from "~/components";
 
 To check if user identities were updated in Cloudflare One, view your [SCIM provisioning logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/).
 
-<Render file="access/scim-requires-login" product="cloudflare-one" />
\ No newline at end of file
+<Render file="access/scim-requires-login" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/aws-resolver.mdx b/src/content/partials/cloudflare-one/aws-resolver.mdx
index 9a9d914decd40c5..9c47b138f5d989e 100644
--- a/src/content/partials/cloudflare-one/aws-resolver.mdx
+++ b/src/content/partials/cloudflare-one/aws-resolver.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 Avoid configuring your [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) or [Resolver Policy](/cloudflare-one/traffic-policies/resolver-policies/) to direct all `*.amazonaws.com` DNS resolution via AWS Route 53 Resolver.
 
 Some AWS endpoints (such as `ssm.us-east-1.amazonaws.com`) are public AWS endpoints that are not resolvable via internal VPC resolution. This can break AWS Console features for users on the Cloudflare One Client.
 
-Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
\ No newline at end of file
+Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
diff --git a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
index e908569bbffc1cf..ddceb27b9e24102 100644
--- a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
+++ b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
@@ -12,4 +12,3 @@
 - [Microsoft 365 Copilot](/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot/)
 - [OpenAI](/cloudflare-one/integrations/cloud-and-saas/openai/)
 - [Anthropic](/cloudflare-one/integrations/cloud-and-saas/anthropic/)
-
diff --git a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
index aada7498182b020..e478a5a5da68b5d 100644
--- a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
+++ b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
@@ -8,4 +8,4 @@ Detect DLP matches in content used and shared within Microsoft's artificial inte
 | --------------------------------------------------------- | -------------------------------------- | -------- |
 | Microsoft: Copilot Referenced File with DLP Profile match | `fa7b06bd-cf63-41fc-9afa-a20598f7a52d` | High     |
 | Microsoft: Copilot AI Response with DLP Profile match     | `176b9299-0cee-4bbb-9c59-b18611228454` | High     |
-| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
\ No newline at end of file
+| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
diff --git a/src/content/partials/cloudflare-one/choose-team-name.mdx b/src/content/partials/cloudflare-one/choose-team-name.mdx
index a8d57921a2efb06..4d29a981f28db0a 100644
--- a/src/content/partials/cloudflare-one/choose-team-name.mdx
+++ b/src/content/partials/cloudflare-one/choose-team-name.mdx
@@ -2,7 +2,6 @@ import { GlossaryTooltip } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
 
-
 2. On the onboarding screen, choose a <GlossaryTooltip term="team name">team name</GlossaryTooltip>. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry.
 
    You can find your team name in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Settings**.
diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
index fe7557d47652954..65c136e3d2c2438 100644
--- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**.
-2. Turn on **Allow users to open a remote browser without the device client**.
\ No newline at end of file
+2. Turn on **Allow users to open a remote browser without the device client**.
diff --git a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
index 7323f05d09189c0..69056d8ee6f20d8 100644
--- a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
+++ b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
@@ -1 +1 @@
-Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
\ No newline at end of file
+Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
index 65a8f00486b5bc1..8305079a6f89537 100644
--- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
+++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
@@ -16,7 +16,7 @@ To capture data from a remote device:
      :::note
      **Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test.
      :::
-		 {props.bestPractice}
+     {props.bestPractice}
 4. Select **Run diagnostics**.
 
 DEX will now send capture requests to the configured devices. If the Cloudflare One Client is disconnected, the capture will time out after 10 minutes.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
index 83843ecfc58460f..fea35b13ae26ba6 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -22,9 +21,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -34,4 +32,4 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 
 12. Review your settings and select **Submit**.
 
-13. Select **Done**.
\ No newline at end of file
+13. Select **Done**.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
index ca5f0f65140cc17..d4376f9c0f71649 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -22,9 +21,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -43,9 +41,8 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
-    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
+    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 18. Select **Next**.
 
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
index a2bfdd54a9efbbb..b2310b379b92a16 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To configure quarantine notifications:
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
index 8e7f70186f96377..01fe2f78cef538f 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
\ No newline at end of file
+Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
diff --git a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
index 3ff7a31c494d759..d49c114294cdce6 100644
--- a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
+++ b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
@@ -1,10 +1,10 @@
 - **Malicious**: Traffic associated with active threat campaigns. Malicious messages invoked multiple phishing verdict triggers and met thresholds for bad behavior.
-    - **Recommendation**: Block.
+  - **Recommendation**: Block.
 - **Spam**: Traffic associated with non-malicious, commercial campaigns.
-    - **Recommendation**: Route to existing Spam quarantine folder.
+  - **Recommendation**: Route to existing Spam quarantine folder.
 - **Bulk**: Traffic often associated with newsletters or marketing campaigns. Refer to [Graymail](https://en.wikipedia.org/wiki/Graymail_%28email%29) for more details.
-    - **Recommendation**: Monitor or tag.
+  - **Recommendation**: Monitor or tag.
 - **Suspicious**: Traffic associated with phishing campaigns (and is under further analysis by our automated systems).
-    - **Recommendation**: Research these messages internally to evaluate legitimacy.
+  - **Recommendation**: Research these messages internally to evaluate legitimacy.
 - **Spoof**: Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) or has mismatching `Envelope From` and `Header From` values.
-    - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
\ No newline at end of file
+  - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
index 23143351441d03b..2edeb49998378d2 100644
--- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx
+++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
@@ -2,17 +2,17 @@ When you configure your domain, the Cloudflare dashboard will display you the fo
 
 - **Domain**: Domain name. Refer to [Manage domains](/cloudflare-one/email-security/setup/manage-domains/) to learn how to add, filter, and delete domains.
 - **Configured method**: The deployment method you used to configure your domain. Depending on how you decided to configure Email security, the dashboard will display:
-    - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
-    - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
-    - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
-- **Status**: Status indicates the state of the configuration. 
-    - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
-    - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
+  - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
+  - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
+  - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
+- **Status**: Status indicates the state of the configuration.
+  - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
+  - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
 - **Service address**: This is the email address you will use to send a copy of your email.
 - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**.
 - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration:
-    1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
-    2. Locate your integration, select **Configure**, then select **Edit**.
-    3. Rename your integration, then select **Save**. 
+  1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
+  2. Locate your integration, select **Configure**, then select **Edit**.
+  3. Rename your integration, then select **Save**.
 - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured.
-- **Date added**: Date when the domain was added.
\ No newline at end of file
+- **Date added**: Date when the domain was added.
diff --git a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
index 33c6c6c71c6243a..5ea5ae3a83f02f1 100644
--- a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
+++ b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
\ No newline at end of file
+[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
diff --git a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
index 49cd1e994f8a9f8..40c2ac71b068bec 100644
--- a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
+++ b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up)
 - A [Zero Trust organization](/cloudflare-one/setup/#2-create-a-zero-trust-organization)
-- A domain to protect
\ No newline at end of file
+- A domain to protect
diff --git a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
index 9a1bdd00693b775..b06118fd3a052a0 100644
--- a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
+++ b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can include an external logo image to display on your custom block page. The block page resizes all images to 146x146 pixels. The URL must be valid and no longer than 2048 characters. Accepted file types include SVG, PNG, JPEG, and GIF.
diff --git a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
index eec835ed93e198e..bbbfc69bd059ecb 100644
--- a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
+++ b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies**.
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
index ea9c95d04ff8dfe..046196f5fdbf1e2 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
 - **IPv4**: `100.80.0.0/16`
-- **IPv6**: `2606:4700:0cf1:4000::/64`
\ No newline at end of file
+- **IPv6**: `2606:4700:0cf1:4000::/64`
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
index 7aafd3c92aef6de..30af62814f0f3df 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
@@ -4,13 +4,13 @@
 
 import { Render, Details, GlossaryTooltip } from "~/components";
 
-| On-ramp method                                                                                      | Compatibility |
-| --------------------------------------------------------------------------------------------------- | ------------- |
-| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                                            | ✅            |
-| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)                        | ✅            |
-| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                                      | ✅            |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) | ✅            |
-| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                                              | 🚧[^1]        |
+| On-ramp method                                                                             | Compatibility |
+| ------------------------------------------------------------------------------------------ | ------------- |
+| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) | ✅            |
+| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)               | ✅            |
+| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                             | ✅            |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                    | ✅            |
+| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                           | 🚧[^1]        |
 
 [^1]: Not compatible with [ECMP routing](/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing). For hostname-based routing to work, DNS queries and the resulting network traffic must reach Cloudflare over the same IPsec/GRE tunnel. <br/>
 
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
index a639506c0b67a66..d1f4b0b967db2ba 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-import { Render, GlossaryTooltip } from "~/components"
+import { Render, GlossaryTooltip } from "~/components";
 
 In your WARP [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel.  Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode):
 
 - **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
 - **Include mode**: Add Split Tunnel entries for the following IP addresses:
-	 	<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
+  <Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
index 07c7d64a068b757..0dbf6f82fe6cd31 100644
--- a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
+++ b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
@@ -28,4 +28,4 @@ import { TabItem, Tabs } from "~/components";
 	}
 	```
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
index 1615bd27d784c47..91940427f366679 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 | Selector    | Operator | Value            | Action         |
 | ----------- | -------- | ---------------- | -------------- |
-| Application | in       | *Do Not Inspect* | Do Not Inspect |
+| Application | in       | _Do Not Inspect_ | Do Not Inspect |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
index a55001b8df4ac2c..24521accd2be220 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | Policy name                 | Selector       | Operator | Value            | Egress method                   |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
index 4e453523e39abb5..7584fb41e2afe19 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
@@ -2,7 +2,7 @@
 inputParameters: selector;;value
 ---
 
-| Selector       | Operator      | Value            | Logic | Action |
-| -------------- | ------------- | ---------------- | ----- | ------ |
-| {props.selector} | in          | <code>{props.value}</code>   | And   | Allow  |
-| User Email     | matches regex | `.*@example.com` |       |        |
+| Selector         | Operator      | Value                      | Logic | Action |
+| ---------------- | ------------- | -------------------------- | ----- | ------ |
+| {props.selector} | in            | <code>{props.value}</code> | And   | Allow  |
+| User Email       | matches regex | `.*@example.com`           |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
index 3b9f11e6ef1ca2b..77ace8200c34cdf 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
@@ -4,4 +4,4 @@
 
 | Selector       | Operator | Value        | Action |
 | -------------- | -------- | ------------ | ------ |
-| Destination IP | in       | `10.0.0.0/8` | Block  |
\ No newline at end of file
+| Destination IP | in       | `10.0.0.0/8` | Block  |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
index 293b0d23be0ff03..1ed03e7aa407058 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-| Selector       | Operator      | Value            | Logic | Action |
-| -------------- | ------------- | ---------------- | ----- | ------ |
-| Host           | in            | `wiki.internal.local`   | And   | Allow  |
-| User Email     | matches regex | `.*@example.com` |       |        |
+| Selector   | Operator      | Value                 | Logic | Action |
+| ---------- | ------------- | --------------------- | ----- | ------ |
+| Host       | in            | `wiki.internal.local` | And   | Allow  |
+| User Email | matches regex | `.*@example.com`      |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
index b23ff64f7475ed7..a7c16e3c1d91ed9 100644
--- a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
+++ b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Resolver policies](/cloudflare-one/traffic-policies/resolver-policies/) provide similar functionality to Local Domain Fallback but occur in Cloudflare Gateway rather than on the local device. This option is recommended if you want more granular control over private DNS resolution. For example, you can ensure that all users in a specific geography use the private DNS server closest to them, ensure that specific conditions are met before resolving private DNS traffic, and apply [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) to private DNS traffic.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
index 64bfa9b16dc161a..5a6e380d089015d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When using an Allow or Block action, you can optionally [block IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category) or [filter categories for `CNAME` records](/cloudflare-one/traffic-policies/domain-categories/#ignore-cname-domain-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
index 9fb4a6872e220df..a9531e7748ee785 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 The country that the request is destined for. Geolocation is determined from the target IP address. To specify a country, enter its [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                            | API example              |
-| ---------------------------------- | ------------------------ |
+| UI name                            | API example                                  |
+| ---------------------------------- | -------------------------------------------- |
 | Destination Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
index 00723a3e876eb59..335ee3ee0daeeca 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With the Device Posture selector, admins can use signals from end-user devices to secure access to their internal and external resources. For example, a security admin can choose to limit all access to internal applications based on whether specific software is installed on a device and/or if the device or software are configured in a particular way.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
index 843d9ab425e324b..76e61efb71ed111 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to DNS queries that arrived to your Gateway Resolver IP address aligned with a registered DNS location. For most Gateway customers, this is an IPv4 anycast address and policies created using this IPv4 address will apply to all DNS locations. However, each DNS location has a dedicated IPv6 address and some Gateway customers have been supplied with a dedicated IPv4 address — these both can be used to apply policies to specific registered DNS locations.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
index 272bcfbd3b2eb4f..526e97d2d3911fd 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to match against DNS queries that arrive via DNS-over-HTTPS (DoH) destined for the DoH endpoint configured for each DNS location. For example, you can use a DNS location with a DoH endpoint of `abcdefg.cloudflare-gateway.com` by choosing the DoH Subdomain selector and inputting a value of `abcdefg`.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
index 05b18f7f521327c..4f8461929b76d11 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-| UI name     | API example                                     |
-| ----------- | ----------------------------------------------- |
+| UI name     | API example                                                    |
+| ----------- | -------------------------------------------------------------- |
 | OIDC Claims | `any(identity.oidc_claims[*] == "\"department=engineering\"")` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
index e61b2a18a69b641..588a6399b52dfb6 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The protocol used to send the packet.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
index 8c09fe7735b8ada..21ddf4a78052f03 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to choose the DNS resource record type that you would like to apply policies against. For example, you can match `A` records for a domain but not `MX` records.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
index 16aa0c58ae0be8d..aa08d0cb5aaa69a 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to match domains (and optionally, [IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category)) belonging to specific [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
index f770cd8258d370f..cfc4e49bf7dcc14 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              | Evaluation phase      |
-| ----------------------------- | ------------------------ | --------------------- |
+| UI name                       | API example                                  | Evaluation phase      |
+| ----------------------------- | -------------------------------------------- | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
index bea70cb9423860e..18542f3726a8e3e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              |
-| ----------------------------- | ------------------------ |
+| UI name                       | API example                                  |
+| ----------------------------- | -------------------------------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
index f770cd8258d370f..cfc4e49bf7dcc14 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
@@ -1,12 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example              | Evaluation phase      |
-| ----------------------------- | ------------------------ | --------------------- |
+| UI name                       | API example                                  | Evaluation phase      |
+| ----------------------------- | -------------------------------------------- | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
index 135f98ad365bdf1..2d8b06452ef3050 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
index 135f98ad365bdf1..2d8b06452ef3050 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
index fee81be8110d5cb..593bd93476a3680 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name    | API example value                           |
-| ---------- | ------------------------------------------- |
+| UI name        | API example value                           |
+| -------------- | ------------------------------------------- |
 | {props.UIname} | `identity.email == "user-name@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
index f1b4aa99de07338..7d9c06487f8bece 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
\ No newline at end of file
+| UI name        | API example                                          |
+| -------------- | ---------------------------------------------------- |
+| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
index 719a72bec8720a8..458d7606be62bb1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
\ No newline at end of file
+| UI name        | API example                                    |
+| -------------- | ---------------------------------------------- |
+| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
index 35fe7cc1e898bed..7d5f097e94c6fa9 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name          | API example                                       |
-| ---------------- | ------------------------------------------------- |
-| {props.UIname} | `identity.groups.name == "\"finance\""` |
\ No newline at end of file
+| UI name        | API example                             |
+| -------------- | --------------------------------------- |
+| {props.UIname} | `identity.groups.name == "\"finance\""` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
index 209566937c34f20..444ae920411c5ae 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name   | API example                    |
-| --------- | ------------------------------ |
-| {props.UIname}  | `identity.name == "user-name"` |
\ No newline at end of file
+| UI name        | API example                    |
+| -------------- | ------------------------------ |
+| {props.UIname} | `identity.name == "user-name"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
index bd7de5ffe296634..253f211beb4c83e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name         | API example                                                                                | Evaluation phase      |
-| --------------- | ------------------------------------------------------------------------------------------ | --------------------- |
-| User Email      | `identity.email == "user@example.com"`                                                     | Before DNS resolution |
-| User Name       | `identity.name == "Test User"`                                                             | Before DNS resolution |
-| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               | Before DNS resolution |
-| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           | Before DNS resolution |
-| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  | Before DNS resolution |
-| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
+| UI name           | API example                                                                                                    | Evaluation phase      |
+| ----------------- | -------------------------------------------------------------------------------------------------------------- | --------------------- |
+| User Email        | `identity.email == "user@example.com"`                                                                         | Before DNS resolution |
+| User Name         | `identity.name == "Test User"`                                                                                 | Before DNS resolution |
+| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   | Before DNS resolution |
+| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               | Before DNS resolution |
+| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       | Before DNS resolution |
+| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
index e963ab12286d3ee..e18e640ce352a0d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name         | API example                                                                                |
-| --------------- | ------------------------------------------------------------------------------------------ |
-| User Email      | `identity.email == "user@example.com"`                                                     |
-| User Name       | `identity.name == "Test User"`                                                             |
-| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               |
-| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           |
-| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  |
-| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
+| UI name           | API example                                                                                                    |
+| ----------------- | -------------------------------------------------------------------------------------------------------------- |
+| User Email        | `identity.email == "user@example.com"`                                                                         |
+| User Name         | `identity.name == "Test User"`                                                                                 |
+| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   |
+| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               |
+| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       |
+| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
index ce7d5d89de6d711..8e62f876db500b1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
 Identity-based selectors include:
 
-* **SAML Attributes**
-* **User Email**
-* **User Group Emails**
-* **User Group IDs**
-* **User Group Names**
-* **User Name**
+- **SAML Attributes**
+- **User Email**
+- **User Group Emails**
+- **User Group IDs**
+- **User Group Names**
+- **User Name**
 
 To use identity-based selectors, enable **Traffic and DNS mode** in the Cloudflare One Client and enroll your user in your organization. For more information, refer to [Identity-based policies](/cloudflare-one/traffic-policies/identity-selectors/).
diff --git a/src/content/partials/cloudflare-one/gateway/value.mdx b/src/content/partials/cloudflare-one/gateway/value.mdx
index a438bb02fbddee1..8ba2eb6529409da 100644
--- a/src/content/partials/cloudflare-one/gateway/value.mdx
+++ b/src/content/partials/cloudflare-one/gateway/value.mdx
@@ -17,8 +17,8 @@ Regular expressions are evaluated using Rust. The Rust implementation is slightl
 
 If you want to match multiple values, you can use the pipe symbol (`|`) as an OR operator. You do not need to use an escape character (`\`) before the pipe symbol. For example, the following expression evaluates to true when the {props.selectordescription} matches either <code>{props.valueOne}</code> or <code>{props.valueTwo}</code>:
 
-| Selector    | Operator        | Value          |
-| ----------- | --------------- | -------------- |
+| Selector         | Operator         | Value                                               |
+| ---------------- | ---------------- | --------------------------------------------------- |
 | {props.selector} | {props.operator} | <code>{props.valueOne}&#124;{props.valueTwo}</code> |
 
 In addition to regular expressions, you can use [logical operators](#logical-operators) to match multiple values.
diff --git a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
index d14d28f9b8b9303..c8d77f235da0dee 100644
--- a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
+++ b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Posture checks** > **Service provider checks**.
 2. Select **Add a check**.
diff --git a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
index 38dd06ceea2f117..251164d2d766ee4 100644
--- a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
+++ b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
@@ -1,6 +1,5 @@
 ---
 inputParameters: param1
-
 ---
 
 Cloudflare One Client is [deployed](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) on the device. For a list of supported modes and operating systems, refer to <a href={props.link}>{props.name}</a>.
diff --git a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
index 41541ce5b9dac6d..5927c815e59262a 100644
--- a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
+++ b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
@@ -4,8 +4,8 @@
 
 To decrypt the log, follow the instructions in the [SSH Logging CLI repository](https://github.com/cloudflare/ssh-log-cli/). In the following example, `sshkey` is the private key that matches the public key uploaded to Cloudflare.
 
-   ```sh
-   ./ssh-log-cli decrypt -i sshlog -k sshkey
-   ```
+```sh
+./ssh-log-cli decrypt -i sshlog -k sshkey
+```
 
-   This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
+This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
diff --git a/src/content/partials/cloudflare-one/ssh/public-key.mdx b/src/content/partials/cloudflare-one/ssh/public-key.mdx
index 6cdb18030f52db0..67338a0b2b7b927 100644
--- a/src/content/partials/cloudflare-one/ssh/public-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/public-key.mdx
@@ -16,9 +16,9 @@
 
 3. In the `ca.pub` file, paste the public key without any modifications.
 
-	```txt title="ca.pub"
-	ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
-	```
+   ```txt title="ca.pub"
+   ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
+   ```
 
    The `ca.pub` file can hold multiple keys, listed one per line. Empty lines and comments starting with `#` are also allowed.
 
diff --git a/src/content/partials/cloudflare-one/ssh/restart-server.mdx b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
index 4e91c37de63e2e5..ea942613d292e20 100644
--- a/src/content/partials/cloudflare-one/ssh/restart-server.mdx
+++ b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Tabs, TabItem, Render } from "~/components"
+import { Tabs, TabItem, Render } from "~/components";
 
 Once you have modified your `sshd` configuration, reload the SSH service on the remote machine for the changes to take effect.
 
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
index 5117c9c548cc54c..edd0dc07d1ee8a5 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 :::note
 
 Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
index 15141e1a16ba29f..667604bc9b6a4ef 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
@@ -43,4 +43,4 @@ import { Render, Details, APIRequest, Tabs, TabItem } from "~/components";
 4. Copy the `public_key` value returned in the response.
 
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
index 35834d8c2063b23..fbcdf62609e8975 100644
--- a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
@@ -3,7 +3,7 @@ params:
   - note
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 To log SSH commands, you will need to generate an HPKE key pair and upload the public key to Cloudflare.
 
diff --git a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
index 2492eb7979d2109..be9833c0d225c55 100644
--- a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
@@ -14,161 +14,161 @@ The following configuration will modify settings in your Cloudflare account.
 
 2.  Add the following resources to `Cloudflare-config.tf`:
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        ```tf
-
-        # Creates a new remotely-managed tunnel for the GCP VM.
-        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-        	account_id    = var.cloudflare_account_id
-        	name          = "Terraform GCP tunnel"
-        	config_src    = "cloudflare"
-        }
-
-        # Reads the token used to run the tunnel on the server.
-        data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
-        	account_id 	= var.cloudflare_account_id
-        	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        }
-
-        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-        resource "cloudflare_dns_record" "http_app" {
-        	zone_id = var.cloudflare_zone_id
-        	name    = "http_app"
-        	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
-        	type    = "CNAME"
-        	ttl     = 1
-        	proxied = true
-        }
-
-        # Configures tunnel with a published application for clientless access.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-        	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        	account_id = var.cloudflare_account_id
-        	config     = {
-        		ingress 	= [
-        			{
-        				hostname = "http_app.${var.cloudflare_zone}"
-        				service  = "http://httpbin:80"
-        			},
-        			{
-        				service  = "http_status:404"
-        			}
-        		]
-        	}
-        }
-
-        # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
-        account_id         = var.cloudflare_account_id
-        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        network            = google_compute_instance.http_server.network_interface.0.network_ip
-        comment            = "Example tunnel route"
-        }
-
-        # Creates a reusable Access policy.
-        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-        	account_id   = var.cloudflare_account_id
-        	name         = "Allow email addresses"
-        	decision     = "allow"
-        	include      = [
-        		{
-        			email = {
-        				email = var.cloudflare_email
-        			}
-        		},
-        		{
-        			email_domain = {
-        				domain = "@example.com"
-        			}
-        		}
-        	]
-        }
-
-        # Creates an Access application to control who can connect to the public hostname.
-        resource "cloudflare_zero_trust_access_application" "http_app" {
-        	account_id       = var.cloudflare_account_id
-        	type             = "self_hosted"
-        	name             = "Access application for http_app.${var.cloudflare_zone}"
-        	domain           = "http_app.${var.cloudflare_zone}"
-        	policies = [
-        		{
-        			id = cloudflare_zero_trust_access_policy.allow_emails.id
-        			precedence = 1
-        		}
-        	]
-        }
-        ```
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        # Generates a 32-byte secret for the tunnel.
-        resource "random_bytes" "tunnel_secret" {
-        	byte_length = 32
-        }
-
-        # Creates a new remotely-managed tunnel for the GCP VM.
-        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-        	account_id = var.cloudflare_account_id
-        	name       = "Terraform GCP tunnel"
-        	secret     = random_bytes.tunnel_secret.base64
-        }
-
-        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-        resource "cloudflare_record" "http_app" {
-        	zone_id = var.cloudflare_zone_id
-        	name    = "http_app"
-        	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
-        	type    = "CNAME"
-        	proxied = true
-        }
-
-        # Configures tunnel with a published application for clientless access.
-        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-        	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        	account_id = var.cloudflare_account_id
-        	config {
-        		ingress_rule {
-        			hostname = "${cloudflare_record.http_app.hostname}"
-        			service  = "http://httpbin:80"
-        		}
-        		ingress_rule {
-        			service  = "http_status:404"
-        		}
-        	}
-        }
-
-        # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
-        resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
-        account_id         = var.cloudflare_account_id
-        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-        network            = google_compute_instance.http_server.network_interface.0.network_ip
-        comment            = "Example tunnel route"
-        }
-
-        # Creates an Access application to control who can connect to the public hostname.
-        resource "cloudflare_zero_trust_access_application" "http_app" {
-        	account_id          = var.cloudflare_account_id
-        	name             = "Access application for http_app.${var.cloudflare_zone}"
-        	domain           = "http_app.${var.cloudflare_zone}"
-        }
-
-        # Creates a (legacy) Access policy for the Access application.
-        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-        	application_id = cloudflare_zero_trust_access_application.http_app.id
-        	account_id        = var.cloudflare_account_id
-        	name           = "Example policy for http_app.${var.cloudflare_zone}"
-        	precedence     = "1"
-        	decision       = "allow"
-        	include {
-        		email = [var.cloudflare_email]
-        	}
-        }
-        ```
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            ```tf
+    
+            # Creates a new remotely-managed tunnel for the GCP VM.
+            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+            	account_id    = var.cloudflare_account_id
+            	name          = "Terraform GCP tunnel"
+            	config_src    = "cloudflare"
+            }
+    
+            # Reads the token used to run the tunnel on the server.
+            data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
+            	account_id 	= var.cloudflare_account_id
+            	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            }
+    
+            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+            resource "cloudflare_dns_record" "http_app" {
+            	zone_id = var.cloudflare_zone_id
+            	name    = "http_app"
+            	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
+            	type    = "CNAME"
+            	ttl     = 1
+            	proxied = true
+            }
+    
+            # Configures tunnel with a published application for clientless access.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+            	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            	account_id = var.cloudflare_account_id
+            	config     = {
+            		ingress 	= [
+            			{
+            				hostname = "http_app.${var.cloudflare_zone}"
+            				service  = "http://httpbin:80"
+            			},
+            			{
+            				service  = "http_status:404"
+            			}
+            		]
+            	}
+            }
+    
+            # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
+            account_id         = var.cloudflare_account_id
+            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            network            = google_compute_instance.http_server.network_interface.0.network_ip
+            comment            = "Example tunnel route"
+            }
+    
+            # Creates a reusable Access policy.
+            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+            	account_id   = var.cloudflare_account_id
+            	name         = "Allow email addresses"
+            	decision     = "allow"
+            	include      = [
+            		{
+            			email = {
+            				email = var.cloudflare_email
+            			}
+            		},
+            		{
+            			email_domain = {
+            				domain = "@example.com"
+            			}
+            		}
+            	]
+            }
+    
+            # Creates an Access application to control who can connect to the public hostname.
+            resource "cloudflare_zero_trust_access_application" "http_app" {
+            	account_id       = var.cloudflare_account_id
+            	type             = "self_hosted"
+            	name             = "Access application for http_app.${var.cloudflare_zone}"
+            	domain           = "http_app.${var.cloudflare_zone}"
+            	policies = [
+            		{
+            			id = cloudflare_zero_trust_access_policy.allow_emails.id
+            			precedence = 1
+            		}
+            	]
+            }
+            ```
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            # Generates a 32-byte secret for the tunnel.
+            resource "random_bytes" "tunnel_secret" {
+            	byte_length = 32
+            }
+    
+            # Creates a new remotely-managed tunnel for the GCP VM.
+            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+            	account_id = var.cloudflare_account_id
+            	name       = "Terraform GCP tunnel"
+            	secret     = random_bytes.tunnel_secret.base64
+            }
+    
+            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+            resource "cloudflare_record" "http_app" {
+            	zone_id = var.cloudflare_zone_id
+            	name    = "http_app"
+            	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
+            	type    = "CNAME"
+            	proxied = true
+            }
+    
+            # Configures tunnel with a published application for clientless access.
+            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+            	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            	account_id = var.cloudflare_account_id
+            	config {
+            		ingress_rule {
+            			hostname = "${cloudflare_record.http_app.hostname}"
+            			service  = "http://httpbin:80"
+            		}
+            		ingress_rule {
+            			service  = "http_status:404"
+            		}
+            	}
+            }
+    
+            # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
+            resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
+            account_id         = var.cloudflare_account_id
+            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+            network            = google_compute_instance.http_server.network_interface.0.network_ip
+            comment            = "Example tunnel route"
+            }
+    
+            # Creates an Access application to control who can connect to the public hostname.
+            resource "cloudflare_zero_trust_access_application" "http_app" {
+            	account_id          = var.cloudflare_account_id
+            	name             = "Access application for http_app.${var.cloudflare_zone}"
+            	domain           = "http_app.${var.cloudflare_zone}"
+            }
+    
+            # Creates a (legacy) Access policy for the Access application.
+            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+            	application_id = cloudflare_zero_trust_access_application.http_app.id
+            	account_id        = var.cloudflare_account_id
+            	name           = "Example policy for http_app.${var.cloudflare_zone}"
+            	precedence     = "1"
+            	decision       = "allow"
+            	include {
+            		email = [var.cloudflare_email]
+            	}
+            }
+            ```
+            </TabItem>
+            </Tabs>
 
 To learn more about these resources, refer to the [Cloudflare provider documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
diff --git a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
index 4eca7f0c1b7957c..e21650fa17456a6 100644
--- a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
@@ -14,88 +14,88 @@ The following configuration defines the specifications for the GCP virtual machi
 
 2.  Add the following content to `GCP-config.tf`:
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        ```tf
-        # OS the server will use
-        data "google_compute_image" "image" {
-        	family  = "ubuntu-2204-lts"
-        	project = "ubuntu-os-cloud"
-        }
-
-        # GCP Instance resource
-        resource "google_compute_instance" "http_server" {
-        	name         = "test"
-        	machine_type = var.machine_type
-        	zone         = var.zone
-        	tags         = []
-        	boot_disk {
-        		initialize_params {
-        			image = data.google_compute_image.image.self_link
-        		}
-        	}
-
-        	network_interface {
-        		network = "default"
-        		access_config {
-        			//Ephemeral IP
-        		}
-        	}
-        	// Optional config to make instance ephemeral
-        /*  scheduling {
-        		preemptible       = true
-        		automatic_restart = false
-        	} */
-
-        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-        		{
-        			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
-        		})
-        }
-        ```
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        # OS the server will use
-        data "google_compute_image" "image" {
-        	family  = "ubuntu-2204-lts"
-        	project = "ubuntu-os-cloud"
-        }
-
-        # GCP Instance resource
-        resource "google_compute_instance" "http_server" {
-        	name         = "test"
-        	machine_type = var.machine_type
-        	zone         = var.zone
-        	tags         = []
-        	boot_disk {
-        		initialize_params {
-        			image = data.google_compute_image.image.self_link
-        		}
-        	}
-
-        	network_interface {
-        		network = "default"
-        		access_config {
-        			//Ephemeral IP
-        		}
-        	}
-        	// Optional config to make instance ephemeral
-        /*  scheduling {
-        		preemptible       = true
-        		automatic_restart = false
-        	} */
-
-        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-        		{
-        			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
-        		})
-        }
-        ```
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            ```tf
+            # OS the server will use
+            data "google_compute_image" "image" {
+            	family  = "ubuntu-2204-lts"
+            	project = "ubuntu-os-cloud"
+            }
+    
+            # GCP Instance resource
+            resource "google_compute_instance" "http_server" {
+            	name         = "test"
+            	machine_type = var.machine_type
+            	zone         = var.zone
+            	tags         = []
+            	boot_disk {
+            		initialize_params {
+            			image = data.google_compute_image.image.self_link
+            		}
+            	}
+    
+            	network_interface {
+            		network = "default"
+            		access_config {
+            			//Ephemeral IP
+            		}
+            	}
+            	// Optional config to make instance ephemeral
+            /*  scheduling {
+            		preemptible       = true
+            		automatic_restart = false
+            	} */
+    
+            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+            		{
+            			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
+            		})
+            }
+            ```
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            # OS the server will use
+            data "google_compute_image" "image" {
+            	family  = "ubuntu-2204-lts"
+            	project = "ubuntu-os-cloud"
+            }
+    
+            # GCP Instance resource
+            resource "google_compute_instance" "http_server" {
+            	name         = "test"
+            	machine_type = var.machine_type
+            	zone         = var.zone
+            	tags         = []
+            	boot_disk {
+            		initialize_params {
+            			image = data.google_compute_image.image.self_link
+            		}
+            	}
+    
+            	network_interface {
+            		network = "default"
+            		access_config {
+            			//Ephemeral IP
+            		}
+            	}
+            	// Optional config to make instance ephemeral
+            /*  scheduling {
+            		preemptible       = true
+            		automatic_restart = false
+            	} */
+    
+            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+            		{
+            			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
+            		})
+            }
+            ```
+            </TabItem>
+            </Tabs>
diff --git a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
index cda294b702f2e15..5afae47ec52d2f1 100644
--- a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
@@ -25,4 +25,4 @@ provider "google" {
 }
 provider "random" {
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/terraform/providers.mdx b/src/content/partials/cloudflare-one/terraform/providers.mdx
index 113455091a647e1..962ef714f4ec1c3 100644
--- a/src/content/partials/cloudflare-one/terraform/providers.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers.mdx
@@ -14,41 +14,41 @@ You will need to declare the [providers](https://registry.terraform.io/browse/pr
 
 2.  Add the following providers to `providers.tf`. The `random` provider is used to generate a tunnel secret.
 
-        <Tabs syncKey="dashPlusAPI">
-        <TabItem label="Terraform (v5)">
-
-        <Render file="terraform/providers-v5" product="cloudflare-one" />
-
-        </TabItem>
-        <TabItem label="Terraform (v4)">
-
-        ```tf
-        terraform {
-        	required_providers {
-        		cloudflare = {
-        			source = "cloudflare/cloudflare"
-        			version = ">= 4.40.0, < 5.0.0"
-        		}
-        		google = {
-        			source = "hashicorp/google"
-        		}
-        		random = {
-        			source = "hashicorp/random"
-        		}
-        	}
-        	required_version = ">= 1.2"
-        }
-
-        # Providers
-        provider "cloudflare" {
-        	api_token    = var.cloudflare_token
-        }
-        provider "google" {
-        	project    = var.gcp_project_id
-        }
-        provider "random" {
-        }
-        ```
-
-        </TabItem>
-        </Tabs>
+    <Tabs syncKey="dashPlusAPI">
+            <TabItem label="Terraform (v5)">
+    
+            <Render file="terraform/providers-v5" product="cloudflare-one" />
+    
+            </TabItem>
+            <TabItem label="Terraform (v4)">
+    
+            ```tf
+            terraform {
+            	required_providers {
+            		cloudflare = {
+            			source = "cloudflare/cloudflare"
+            			version = ">= 4.40.0, < 5.0.0"
+            		}
+            		google = {
+            			source = "hashicorp/google"
+            		}
+            		random = {
+            			source = "hashicorp/random"
+            		}
+            	}
+            	required_version = ">= 1.2"
+            }
+    
+            # Providers
+            provider "cloudflare" {
+            	api_token    = var.cloudflare_token
+            }
+            provider "google" {
+            	project    = var.gcp_project_id
+            }
+            provider "random" {
+            }
+            ```
+    
+            </TabItem>
+            </Tabs>
diff --git a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
index a68729e1c588fba..6abc149ee79e338 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -3,31 +3,37 @@ Review common troubleshooting scenarios for Cloudflare Browser Isolation.
 ## Connectivity and sessions
 
 ### No Browsers Available
+
 If you encounter a `No Browsers Available` alert, please file feedback via the Cloudflare One Client. This error typically indicates a temporary capacity issue in the data center or a connectivity problem between your client and the remote browser.
 
 ### Maximum Sessions Reached
+
 This alert appears if your device attempts to establish more than two concurrent remote browser instances. A browser isolation session is shared across all tabs and windows within the same browser (for example, all Chrome tabs share one session). You can use two different browsers (such as Chrome and Firefox) concurrently, but opening a third will trigger this alert. To release a session, close all tabs and windows in one of your local browsers.
 
 ## Rendering and performance
 
 ### WebGL Rendering Error
+
 Cloudflare Browser Isolation uses Network Vector Rendering (NVR), which does not support WebGL (Web Graphics Library) in all environments. If a website requires WebGL and your device lacks the necessary hardware resources in the virtualized environment, you may see a rendering error.
 
 To resolve this, try enabling software rasterization in your browser:
+
 1. Go to `chrome://flags/#override-software-rendering-list`.
-2. Set **Override software rendering list** to *Enabled*.
+2. Set **Override software rendering list** to _Enabled_.
 3. Select **Relaunch**.
 
 ### Blank screen on Windows
+
 On Windows devices, Clientless Web Isolation may load with a blank screen if there is a conflict between browser mDNS settings and Windows IGMP configuration.
 
-| IGMPLevel | WebRTC Anonymization | Result |
-| --------- | -------------------- | ------ |
-| 0 (disabled) | Enabled / Default | ❌ Blank screen |
-| 0 (disabled) | Disabled | ✅ Works |
-| 2 (enabled) | Enabled / Default | ✅ Works |
+| IGMPLevel    | WebRTC Anonymization | Result          |
+| ------------ | -------------------- | --------------- |
+| 0 (disabled) | Enabled / Default    | ❌ Blank screen |
+| 0 (disabled) | Disabled             | ✅ Works        |
+| 2 (enabled)  | Enabled / Default    | ✅ Works        |
 
 To fix this, either disable **Anonymize local IPs exposed by WebRTC** in your browser flags or ensure `IGMPLevel` is enabled (set to `2`) in your Windows network settings.
 
 ### Rendering issues (CSS/Images)
+
 If a website displays incorrectly (for example, broken CSS or missing images), it may indicate that the remote browser is unable to fetch specific resources from the origin server. Check your [Gateway HTTP logs](/cloudflare-one/traffic-policies/troubleshooting/) for any blocked subresources that might be required by the page.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
index 812e31a9e577986..ea6662dd6b23a61 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
@@ -3,13 +3,17 @@ Use this guide to troubleshoot common issues with Cloud Access Security Broker (
 ## Security findings
 
 ### Findings not appearing
+
 If you do not see findings for an integrated application:
+
 - **Wait for scan**: Initial scans can take up to 24 hours depending on the size of the application.
 - **Permissions**: Ensure the account used to integrate the application has the necessary administrative permissions.
 - **Enabled status**: Verify that the integration is enabled in the Zero Trust dashboard.
 
 ### False positives
+
 If CASB flags a configuration that is intended for your organization:
+
 1. Go to **CASB** &gt; **Findings**.
 2. Select the finding and choose **Dismiss**.
 3. Provide a reason for dismissal to help refine future scans.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
index d9f76c11a762d23..b0b9af1de6363da 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
@@ -3,6 +3,7 @@ Review common troubleshooting scenarios for Digital Experience Monitoring (DEX).
 ## Data visibility
 
 ### No data displayed for certain users
+
 If you do not see DEX data for specific users in your organization, verify the following:
 
 - **Client version**: Ensure the users are running a version of the Cloudflare One Client that supports DEX.
@@ -10,11 +11,13 @@ If you do not see DEX data for specific users in your organization, verify the f
 - **Traffic routing**: DEX requires that traffic to Cloudflare's orchestration API is not blocked by local firewalls or SSL-inspecting proxies.
 
 ### Fleet status not updating
+
 The Fleet status dashboard can take several minutes to reflect changes in device connectivity. If a device remains in an incorrect state, try disconnecting and reconnecting the Cloudflare One Client to force a status update.
 
 ## Remote captures
 
 ### Remote capture fails to start
+
 Remote captures require the Cloudflare One Client to be connected and able to communicate with the Cloudflare control plane. If a capture fails to start:
 
 - Verify the device status in the Zero Trust dashboard.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
index 77aac5be079b8ae..500c1dc89b9f0c0 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
@@ -4,44 +4,51 @@ Review common troubleshooting scenarios for Cloudflare Email Security.
 
 Email Security identifies threats using detections that result in a final disposition. You can inspect email headers to understand why a specific disposition was applied.
 
-| Attribute | Description |
-| --------- | ----------- |
-| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list. |
-| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain. |
-| `NEW_DOMAIN_LINK` | The email contains links to a newly registered domain. |
-| `ENCRYPTED` | The email message is encrypted. |
-| `BEC` | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
+| Attribute           | Description                                                                                                                                 |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list.                                                                                          |
+| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain.                                                                                          |
+| `NEW_DOMAIN_LINK`   | The email contains links to a newly registered domain.                                                                                      |
+| `ENCRYPTED`         | The email message is encrypted.                                                                                                             |
+| `BEC`               | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
 
 ## Detections and reclassification
 
 ### Handle a false positive
-A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam. 
+
+A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam.
 
 **Solution**:
+
 1. In the Email Security dashboard, go to **Investigation**.
 2. Find the email and select **Submit for reclassification**.
 3. Choose the correct disposition (for example, `Clean`).
 4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) list.
 
 ### Handle a false negative
+
 A false negative occurs when a malicious email is not detected by Email Security.
 
 **Solution**:
+
 1. Ensure the email actually passed through Email Security by checking for the `X-CFEmailSecurity-Disposition` header.
 2. Submit the email for reclassification in the dashboard. This is the preferred method for reporting missed detections.
 
 ## Authentication errors
 
 ### DMARC failures
+
 Email Security may mark an email as **SPAM** if it fails DMARC authentication and the sending domain has a `p=reject` or `p=quarantine` policy.
 
 **Solution**:
+
 - Ask the sender to fix their DMARC/SPF/DKIM records.
 - Configure an [Acceptable Sender](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) entry to suppress the failure for that specific sender.
 
 ## Delivery issues
 
 ### Emails are delayed or not arriving
+
 If emails are not being delivered or are arriving with significant latency:
 
 1. **Check MX records**: Ensure your [MX records](/cloudflare-one/email-security/setup/) are correctly configured and pointing to Cloudflare.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
index a5dd284025e9f77..9aa7ada94a6a62d 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
@@ -3,9 +3,11 @@ This guide helps you troubleshoot common issues with Cloudflare Gateway policies
 ## Blocked websites and connectivity
 
 ### A website is blocked incorrectly
+
 If you believe a domain has been incorrectly blocked by Gateway's security categories or threat intelligence, you can use the [Cloudflare Radar categorization feedback form](https://radar.cloudflare.com/categorization-feedback/) to request a review.
 
 ### Error 526: Invalid SSL certificate
+
 Gateway presents a **526** error page when it cannot establish a secure connection to the origin. This typically occurs in two cases:
 
 - **Untrusted origin certificate**: The certificate presented by the origin server is expired, revoked, or issued by an unknown authority.
@@ -14,14 +16,17 @@ Gateway presents a **526** error page when it cannot establish a secure connecti
 For more information, refer to [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ### Error 502: Bad Gateway
+
 This issue can occur when communicating with an origin that partially supports HTTP/2. If the origin requests a downgrade to HTTP/1.1 (for example, via a `RST_STREAM` frame with `HTTP_1_1_REQUIRED`), Gateway will not automatically reissue the request over HTTP/1.1 and will instead return a `502 Bad Gateway`. To resolve this, disable HTTP/2 at the origin server.
 
 ### Untrusted certificate warnings
+
 If users see certificate warnings for every page, ensure that the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) is installed and trusted on their devices. This is required for Gateway to inspect HTTPS traffic.
 
 ## Dashboard and analytics
 
 ### Gateway analytics not displayed
+
 If you do not see analytics on the Gateway Overview page:
 
 - **Verify DNS traffic**: Ensure your devices are actually sending queries to Gateway. Check your [DNS locations](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) and verify the source IPv4 address.
@@ -126,8 +131,8 @@ To resolve this issue:
 
 You have configured Gateway to resolve internal hostnames, but users are unable to access them. For example, a user connected to the Cloudflare One Client tries to access an internal service like `jira.mycompany.local`, but the DNS query fails.
 
-| Common causes                              | Solution                                                                                                                                                                                                                  |
-| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                             |
+| Common causes                              | Solution                                                                                                                                                                                                                                       |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                                               |
 | Split Tunnel excludes the private IP range | If your internal resources are in a private IP range (such as `10.0.0.0/8`), that range must be included in the tunnel. If it is in the Exclude list of your Split Tunnel configuration, the Cloudflare One Client will not proxy the traffic. |
-| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                      |
+| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                                           |
diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
index bec8b880edeb7cc..0a544adaa854c9b 100644
--- a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Render } from "~/components";
@@ -9,4 +8,4 @@ A `1033` error indicates your tunnel is not connected to Cloudflare's network be
 
 First, review whether your tunnel is listed as `Active` in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status:
 
-<Render file="tunnel/tunnel-status" product="cloudflare-one" />
\ No newline at end of file
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
index cf11d2740614eac..b4d07916659c2d7 100644
--- a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
@@ -1,11 +1,12 @@
 ---
 {}
-
 ---
 
 Minimum permissions needed to create, delete, and configure tunnels for an account:
+
 - [Cloudflare Access](/cloudflare-one/roles-permissions/)
 
 Additional permissions needed to [route traffic to a public hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) and to be able to perform `cloudflared login`:
+
 - [DNS](/fundamentals/manage-members/roles/)
-- [Load Balancer](/fundamentals/manage-members/roles/)
\ No newline at end of file
+- [Load Balancer](/fundamentals/manage-members/roles/)
diff --git a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
index 7df9b2e5a62c416..49599f43b544a2f 100644
--- a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To add a published application when creating a new tunnel:
@@ -8,16 +7,16 @@ To add a published application when creating a new tunnel:
 1. Go to the **Published applications** tab.
 
 2. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-	:::note
-	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-	:::
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
 
 3. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example,
-	- **Type**: _HTTP_
-	- **URL**: `localhost:8000`
+   - **Type**: _HTTP_
+   - **URL**: `localhost:8000`
 
 4. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
    ![Example of a published application route in the Cloudflare One dashboard](~/assets/images/cloudflare-one/connections/connect-apps/published-app.png)
 
-5. Select **Save**.
\ No newline at end of file
+5. Select **Save**.
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
index b070a82d446402e..10f16e4d43c7afe 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
index 00915193311f7b7..ceda180a2994ca9 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
@@ -5,10 +5,9 @@ params:
 
 TCP monitors are not supported for tunnel endpoints. Instead, create a health check endpoint on the `cloudflared` host and use an HTTPS monitor. For example, you can use `cloudflared` to return a fixed HTTP status response:
 
-1. <a href={props.publishedAppRouteURL}>Add a published application route</a> for the health check:
-   - **Hostname**: `health-check.example.com`
-   - **Service Type**: _HTTP_STATUS_
-   - **HTTP Status Code**: `200`
+1. <a href={props.publishedAppRouteURL}>Add a published application route</a>
+   for the health check: - **Hostname**: `health-check.example.com` - **Service
+   Type**: _HTTP_STATUS_ - **HTTP Status Code**: `200`
 2. [Create a monitor](/load-balancing/monitors/create-monitor/) with these settings:
    - **Type**: _HTTPS_
    - **Path**: `/`
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
index f61bde5fb1a3556..a96ead9f4e833cc 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
-* Size each host with minimum 4GB of RAM and 4 CPU cores.
-* Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
+- Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
+- Size each host with minimum 4GB of RAM and 4 CPU cores.
+- Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
 
 This setup is usually sufficient to handle traffic from 8,000 users (4,000 per host).
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
index e38f3ea59068e4a..399600466878e2a 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Unlike legacy VPNs where throughput is determined by the server's memory, CPU and other hardware specifications, Cloudflare Tunnel throughput is primarily limited by the number of ports configured in system software. Therefore, when sizing your `cloudflared` server, the most important element is sizing the available ports on the machine to reflect the expected throughput of TCP and UDP traffic.
diff --git a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
index c4aa95aa270a7b2..d3d57f5ddd564cf 100644
--- a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
@@ -3,4 +3,3 @@
 ---
 
 To prevent Cloudflare One Client users from accessing your entire private network, we recommend creating a [catch-all Gateway block policy](/learning-paths/replace-vpn/build-policies/create-policy/#catch-all-policy) for your private IP space. You can then layer on higher priority Allow policies (in either Access or Gateway) which grant users access to specific applications or IPs.
-
diff --git a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
index 32bad08d6a11538..836d5c4e7335fae 100644
--- a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
@@ -1,5 +1,4 @@
 ---
-
 ---
 
 In your device profile, configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) goes through the WARP tunnel. Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode). For example, if your devices use the default `100.96.0.0/12` range:
diff --git a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
index 6c082731f7502d1..c90519fd3fb9a8e 100644
--- a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
@@ -19,4 +18,4 @@
 
    ![Connector appearing in the UI after cloudflared has run](~/assets/images/cloudflare-one/connections/connect-apps/connector.png)
 
-8. Select **Next**.
\ No newline at end of file
+8. Select **Next**.
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
index 0f7caefc4aa0c56..4836708c394928a 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Create a Cloudflare Tunnel in Cloudflare One and run the tunnel on the {props.one}.
 
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
index 2f6208021fb86bc..061651ac15df2a8 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
@@ -11,17 +11,17 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 2.  In the **CIDR** tab, enter the **Private IP address** of your {props.resourceName} (for example, <code>{props.exampleIp}</code>). You can expand the IP range later if necessary.
 3.  In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through the Cloudflare One Client. For example, if you are using Split Tunnels in **Exclude** mode, delete <code>{props.splitTunnelCidr}</code>. We recommend re-adding the IPs that are not explicitly used by your {props.resourceName}.
 
-        To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
-
-        <SubtractIPCalculator
-        	client:load
-        	defaults={{
-        		base: props.splitTunnelCidr,
-        		subtract: props.calcExclude
-        	}}
-        />
-
-        Add the results back to your Split Tunnel Exclude mode list.
+    To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
+    
+    <SubtractIPCalculator
+    	client:load
+    	defaults={{
+    		base: props.splitTunnelCidr,
+    		subtract: props.calcExclude
+    	}}
+    />
+    
+    Add the results back to your Split Tunnel Exclude mode list.
 
 4.  To test on a user device:
     1. [Log in to the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/).
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
index 9e70a1198bb9fb7..170049a7ac5f7c8 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Published applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) allow anyone on the Internet to connect to HTTP resources hosted on your virtual private cloud (VPC). To add a published application for your Cloudflare Tunnel:
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
index 4f15318c29c1162..6980de61dec14cf 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
@@ -24,15 +24,30 @@ params:
 
    ```json
    {
-     "tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
-     "connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
-     "connections": [
-       { "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167"},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.113", "index": 1},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.47", "index": 2},
-       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.73", "index": 3}
-     ],
-     "icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
+   	"tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
+   	"connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
+   	"connections": [
+   		{ "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167" },
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.200.113",
+   			"index": 1
+   		},
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.192.47",
+   			"index": 2
+   		},
+   		{
+   			"isConnected": true,
+   			"protocol": 1,
+   			"edgeAddress": "198.41.200.73",
+   			"index": 3
+   		}
+   	],
+   	"icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
    }
    ```
 
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
index 35a23d38040988e..af11a9afb297c8f 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
@@ -8,18 +8,18 @@ params:
 
 The `cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.
 
-| File name                | Description                                                                                                                                                  | Instance  |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
+| File name                | Description                                                                              | Instance  |
+| ------------------------ | ---------------------------------------------------------------------------------------- | --------- |
 | `cli-configuration.json` | <a href={props.runParametersURL}>Tunnel run parameters</a> used when starting the tunnel | diagnosee |
-| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                                                    | diagnosee |
-| `configuration.json`     | Tunnel configuration parameters                                                                                                                              | diagnosee |
-| `goroutine.pprof`        | goroutine profile made available by `pprof`                                                                                                                  | diagnosee |
-| `heap.pprof`             | heap profile made available by `pprof`                                                                                                                       | diagnosee |
-| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis               | diagnosee |
-| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                          | diagnoser |
-| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                           | diagnoser |
-| `systeminformation.json` | Operating system information and resource usage                                                                                                              | diagnosee |
-| `task-result.json`       | Result of each diagnostic task                                                                                                                               | diagnoser |
-| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                                                                                                  | diagnosee |
+| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                          | diagnosee |
+| `configuration.json`     | Tunnel configuration parameters                                                          | diagnosee |
+| `goroutine.pprof`        | goroutine profile made available by `pprof`                                              | diagnosee |
+| `heap.pprof`             | heap profile made available by `pprof`                                                   | diagnosee |
+| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis       | diagnosee |
+| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                      | diagnoser |
+| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                       | diagnoser |
+| `systeminformation.json` | Operating system information and resource usage                                          | diagnosee |
+| `task-result.json`       | Result of each diagnostic task                                                           | diagnoser |
+| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                              | diagnosee |
 
 [^1]: If the log file is blank, you may need to <a href={props.loglevelURL}>set `--loglevel` to `debug`</a> when you start the tunnel. The `--loglevel` parameter is only required if you ran the tunnel from the CLI using a `cloudflared tunnel run` command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes.
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
index 2f2327ca51fb9e4..e8c007b9d69d74c 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Published applications inherit the Cloudflare settings for their hostname, including [cache rules](/cache/how-to/cache-rules/), [WAF rules](/waf/), and other [Rules](/rules/) configurations. You can change these settings for each hostname in the [Cloudflare dashboard](https://dash.cloudflare.com/).
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
index f3c26351bc152ee..6e023ea0564f577 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you create a tunnel, Cloudflare generates a subdomain at `<UUID>.cfargotunnel.com`. You point a CNAME record at this subdomain to route traffic from your hostname to the tunnel.
diff --git a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
index ad172f22cfae0ee..5fb221e26749de9 100644
--- a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Tunnel supports gRPC traffic via [private subnet routing](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/). Public hostname deployments are not currently supported.
diff --git a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
index da5faccbdab0cc8..91d158683723dd9 100644
--- a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
@@ -5,13 +5,16 @@
 import { Details } from "~/components";
 
 <Details header="Hostname format restrictions">
-- **Character limit:** Must be less than 255 characters.
-- **Supported wildcards:** A single wildcard (`*`) is allowed, and it must represent a full DNS label.
-			Example: `*.internal.local`
-- **Unsupported wildcards:** The following wildcard formats are not supported:
-		- Partial wildcards such as `*-dev.internal.local` or `dev-*.internal.local`.
-		- Wildcards in the middle, such as `foo*bar.internal.local` or `foo.*.internal.local`.
-		- Multiple wildcards in the hostname, such as `*.*.internal.local`.
-- **Wildcard trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`) is assumed. For example, `*.internal.local` is saved as `internal.local` but will match all subdomains at the wildcard level (covers `foo.internal.local` but not `foo.bar.internal.local`).
-- **Dot trimming:** Leading and ending dots (`.`) are allowed but trimmed off.
+	- **Character limit:** Must be less than 255 characters. - **Supported
+	wildcards:** A single wildcard (`*`) is allowed, and it must represent a full
+	DNS label. Example: `*.internal.local` - **Unsupported wildcards:** The
+	following wildcard formats are not supported: - Partial wildcards such as
+	`*-dev.internal.local` or `dev-*.internal.local`. - Wildcards in the middle,
+	such as `foo*bar.internal.local` or `foo.*.internal.local`. - Multiple
+	wildcards in the hostname, such as `*.*.internal.local`. - **Wildcard
+	trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`)
+	is assumed. For example, `*.internal.local` is saved as `internal.local` but
+	will match all subdomains at the wildcard level (covers `foo.internal.local`
+	but not `foo.bar.internal.local`). - **Dot trimming:** Leading and ending dots
+	(`.`) are allowed but trimmed off.
 </Details>
diff --git a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
index 221f41fda76b716..660cd5d5f759ab9 100644
--- a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -47,4 +46,4 @@ import { Tabs, TabItem } from "~/components";
         	docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <TUNNEL_TOKEN>
         	```
 
-</TabItem>  </Tabs>
\ No newline at end of file
+</TabItem>  </Tabs>
diff --git a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
index 3e1b6567d49585d..4fdc32d904e2241 100644
--- a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
@@ -12,16 +12,16 @@ Tunnel permissions determine who can run and manage a Cloudflare Tunnel. Two fil
 
 Refer to the table below for a comparison between the two files and the purposes for which they are intended.
 
-|                         | Account certificate                                                          | Tunnel credential                                         |
-| ----------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------- |
-| **File name**           | `cert.pem`                                                                   | `<TUNNEL-UUID>.json`                                      |
-| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account | Authenticates the tunnel it is associated with            |
-| **Scope**               | Account-wide                                                                 | Tunnel-specific                                           |
-| **File type**           | `.pem`                                                                       | `.json`                                                   |
-| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                    | <a href={props.defaultDirectoryURL}>Default directory</a> |
-| **Issued when running** | `cloudflared tunnel login`                                                   | `cloudflared tunnel create <NAME>`                        |
-| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate)  | Does not expire                                           |
-| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)         | Run a tunnel. Create a config file.                       |
+|                         | Account certificate                                                                                        | Tunnel credential                                         |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| **File name**           | `cert.pem`                                                                                                 | `<TUNNEL-UUID>.json`                                      |
+| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account                               | Authenticates the tunnel it is associated with            |
+| **Scope**               | Account-wide                                                                                               | Tunnel-specific                                           |
+| **File type**           | `.pem`                                                                                                     | `.json`                                                   |
+| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                                                  | <a href={props.defaultDirectoryURL}>Default directory</a> |
+| **Issued when running** | `cloudflared tunnel login`                                                                                 | `cloudflared tunnel create <NAME>`                        |
+| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate) | Does not expire                                           |
+| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)                                       | Run a tunnel. Create a config file.                       |
 
 ## Tunnel ownership
 
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
index 6c50a4d38d46d4a..c3f3293198255e7 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
@@ -9,8 +9,8 @@ You can filter logs by event type (`--event`), event level (`--level`), or sampl
 cloudflared tail --level debug <UUID>
 ```
 
-| Flag         | Description                                                                                                                                                                                           | Allowed values                            | Default value |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
-| `--event`    | Filter by the type of event / request.                                                                                                                                                                | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
+| Flag         | Description                                                                                                                         | Allowed values                            | Default value |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
+| `--event`    | Filter by the type of event / request.                                                                                              | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
 | `--level`    | Return logs at this level and above. Works independently of the <a href={props.loglevelURL}>`--loglevel`</a> setting on the server. | `debug`, `info`, `warn`, `error`, `fatal` | `debug`       |
-| `--sampling` | Sample a fraction of the total logs.                                                                                                                                                                  | Number from `0.0` to `1.0`                | `1.0`         |
+| `--sampling` | Sample a fraction of the total logs.                                                                                                | Number from `0.0` to `1.0`                | `1.0`         |
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
index 9199c7ed894a76f..7e5b276368ef811 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
@@ -3,7 +3,6 @@
 
 import { GlossaryTooltip } from "~/components";
 
-
 Dashboard log streams are only available for <GlossaryTooltip term="remotely-managed tunnel">remotely-managed tunnels</GlossaryTooltip>. To stream tunnel logs from the dashboard:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
index 323c86b55d57992..c5d8a1638544701 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
@@ -12,4 +12,3 @@ To enable logs, <a href={props.runParametersURL}>run the tunnel</a> using the `-
 ```sh
 cloudflared tunnel --loglevel info --logfile cloudflared.log run <UUID>
 ```
-
diff --git a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
index 4e0fc2c84e7e66e..bdc546346c31fc1 100644
--- a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
@@ -19,7 +19,7 @@
 | `cloudflared_tunnel_tunnel_authenticate_success`    | Number of successful tunnel authentication events.                                                         | COUNTER |                                            |
 | `cloudflared_tunnel_tunnel_register_success`        | Number of successful tunnel registrations.                                                                 | COUNTER | `rpcName`                                  |
 | `cloudflared_udp_active_sessions`                   | Concurrent number of UDP sessions that are being proxied to any origin.                                    | GAUGE   |                                            |
-| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER   |                                            |
+| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER |                                            |
 | `coredns_panics_total`                              | Number of panics.                                                                                          | COUNTER |                                            |
 | `quic_client_closed_connections`                    | Number of connections that have been closed.                                                               | COUNTER |                                            |
 | `quic_client_latest_rtt`                            | Latest round-trip time (RTT) measured on a connection.                                                     | GAUGE   | `conn_index`                               |
diff --git a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
index 000cf30ab14fdcb..1b6b39f6f1a5fda 100644
--- a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
@@ -132,8 +132,8 @@ When `true`, Happy Eyeballs is disabled.
 `cloudflared` starts a proxy server to translate HTTP traffic into TCP when proxying, for example, SSH or RDP.
 This configures what type of proxy will be started. Valid options are:
 
-* `""` for the regular proxy
-* `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
+- `""` for the regular proxy
+- `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
 
 ### proxyAddress
 
diff --git a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
index 2fd27a10bd6f00a..53e2484f9439265 100644
--- a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
\ No newline at end of file
+You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
diff --git a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
index 9bed10dd3b8e8ea..b0e9a72f30f6267 100644
--- a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
@@ -6,19 +6,19 @@ params:
 
 The table below lists the service types you can route to a public hostname. Non-HTTP services require [installing `cloudflared` on the client](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/) for end users to connect.
 
-| Service type | Description | Example `service` value |
-| ------------ | ----------- | ----------------------- |
-| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP. | `http://localhost:8000` |
-| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates. | `https://localhost:8000` |
-| UNIX         | Same as HTTP, but uses a Unix socket. | `unix:/home/production/echo.sock` |
-| UNIX + TLS   | Same as HTTPS, but uses a Unix socket. | `unix+tls:/home/production/echo.sock` |
-| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead. | `tcp://localhost:2222` |
-| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22` |
-| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/). | `rdp://localhost:3389` |
-| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access). | `smb://localhost:445` |
-| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code. | `http_status:404` |
-| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address. | `bastion` |
-| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only). | `hello_world` |
+| Service type | Description                                                                                                                                                                                                                                                                                                                                                    | Example `service` value               |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
+| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP.                                                                                                                                                                                                                                                                                           | `http://localhost:8000`               |
+| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates.                                                                                                                                                                               | `https://localhost:8000`              |
+| UNIX         | Same as HTTP, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                          | `unix:/home/production/echo.sock`     |
+| UNIX + TLS   | Same as HTTPS, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                         | `unix+tls:/home/production/echo.sock` |
+| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead.                     | `tcp://localhost:2222`                |
+| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22`                  |
+| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/).                                                                                                                                    | `rdp://localhost:3389`                |
+| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access).                                                                                                                     | `smb://localhost:445`                 |
+| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code.                                                                                                                                                                                                                                                                                                        | `http_status:404`                     |
+| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address.                                                                                                                                                                                                                                                                             | `bastion`                             |
+| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only).                                                                                                                                                                                                                  | `hello_world`                         |
 
 ## IPv6 service addresses
 
diff --git a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
index 05449ecd0346b32..effd28c88ed8811 100644
--- a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
@@ -171,9 +171,9 @@ Specifies the path to a <a href={props.configurationFileURL}>configuration file<
 Requires `cloudflared` version 2025.7.0 or later.
 :::
 
-| Syntax                                                                    | Environment Variable        |
-| ------------------------------------------------------------------------- | --------------------------- |
-| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>`    | `TUNNEL_DNS_RESOLVER_ADDRS` |
+| Syntax                                                                 | Environment Variable        |
+| ---------------------------------------------------------------------- | --------------------------- |
+| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>` | `TUNNEL_DNS_RESOLVER_ADDRS` |
 
 Specifies custom DNS resolver addresses for `cloudflared` to use instead of the host machine's default resolvers. Each address must be in `ip:port` format — providing an IP address without a port will cause `cloudflared` to fail to start. You can specify multiple resolvers by repeating the flag. For example,
 
diff --git a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
index 0a7bafc56310b6d..a0e19ac3f17e0f6 100644
--- a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
@@ -2,9 +2,9 @@
 {}
 ---
 
-| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
-|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
-| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel).                           |
-| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
-| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
+| Status       | Meaning                                                                                                                                                                                                                                                                                                                                | Recommended Action                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Healthy**  | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                                                                                                                                                                                                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| **Inactive** | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                                                                                                                                                                                                   | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel). |
+| **Down**     | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                                                                                                                                                                                                       | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                                                                                           |
+| **Degraded** | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic. | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                                            |
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
index a8aee795acbec88..a868e4cec7f75c4 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
@@ -16,4 +16,4 @@ warp-cli target list
 ├──────────────────────────────────────┼──────────┼───────┼───────────────────────┼──────────────────────┼────────────┤
 │ 01943cff-6130-7989-8bff-cbc02b59a2b1 │ SSH      │ 80    │ hostname: az-target   │ 172.16.0.0 (b1net)   │ alice, bob │
 ╰──────────────────────────────────────┴──────────┴───────┴───────────────────────┴──────────────────────┴────────────╯
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
index 612d5ce51183c58..9fd296c4c4257a5 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
@@ -3,42 +3,42 @@ params:
   - one
 ---
 
-import { Markdown, Details, Tabs, TabItem} from "~/components";
+import { Markdown, Details, Tabs, TabItem } from "~/components";
 import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 
 By default, WARP excludes traffic bound for [RFC 1918 space](https://datatracker.ietf.org/doc/html/rfc1918), which are IP addresses typically used in private networks and not reachable from the Internet. In order for the Cloudflare One Client to send traffic to your <Markdown text={props.one}/>, you must configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that the IP/CIDR of your <Markdown text={props.one}/> routes through the Cloudflare One Client.
 
 1. First, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include** mode.
 2. Edit your Split Tunnel routes depending on the mode:
-  	<Tabs> <TabItem label="Exclude IPs and domains">
-
-		If you are using **Exclude** mode:
-
-		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
-
-		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
-
-		You can use the following calculator to determine which IP addresses to re-add:
-
-			<SubtractIPCalculator
-				client:load
-				defaults={{
-					base: "172.16.0.0/12",
-					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
-				}}
-			/>
-		<Details header="Calculator instructions" open = {true}>
-		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
-		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
-		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
-		</Details>
-
-		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
-
-
-   </TabItem> <TabItem label="Include IPs and domains">
-		If you are using **Include** mode:
-		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
-		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
-
-   </TabItem> </Tabs>
+   <Tabs> <TabItem label="Exclude IPs and domains">
+   
+   		If you are using **Exclude** mode:
+   
+   		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
+   
+   		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
+   
+   		You can use the following calculator to determine which IP addresses to re-add:
+   
+   			<SubtractIPCalculator
+   				client:load
+   				defaults={{
+   					base: "172.16.0.0/12",
+   					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
+   				}}
+   			/>
+   		<Details header="Calculator instructions" open = {true}>
+   		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
+   		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
+   		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
+   		</Details>
+   
+   		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
+   
+   
+      </TabItem> <TabItem label="Include IPs and domains">
+   		If you are using **Include** mode:
+   		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
+   		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
+   
+      </TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
index 88879da57d19361..aed1dc57c84005a 100644
--- a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-It may take up to 10 minutes for newly updated settings to propagate to devices.
\ No newline at end of file
+It may take up to 10 minutes for newly updated settings to propagate to devices.
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
index 885e29755b6d368..cc4a288a0d916a4 100644
--- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105`
diff --git a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
index 0f9cabfed41c022..dfc8ccca98273c3 100644
--- a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
+++ b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components"
+import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components";
 
 <Details header="Certificate requirements">
-   <Render file="byo-ca-mtls-cert-requirements" product="ssl" />
+	<Render file="byo-ca-mtls-cert-requirements" product="ssl" />
 </Details>
 
 To check for an mTLS certificate:
@@ -81,4 +80,4 @@ To check for an mTLS certificate:
 
 5. On your device, add the client certificate to the [system keychain](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#test-in-the-browser).
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
index 565425c2df7ac87..4c9ebbf7bef15c0 100644
--- a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
+++ b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 1. [Download](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and install the Cloudflare One Agent app.
 2. Launch the Cloudflare One Agent app.
diff --git a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
index 0c7940a4582c545..18e8ab3a2beb429 100644
--- a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
+++ b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
@@ -8,4 +8,4 @@ import { GlossaryTooltip } from "~/components";
 
 If your DNS server can be configured to connect to a Cloudflare <GlossaryTooltip term="on-ramp">on-ramp</GlossaryTooltip>, Cloudflare recommends using Gateway Resolver policies rather than Local Domain Fallback. Gateway Resolver policies provide more visibility by allowing you to log and review DNS traffic.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
index 65cc25e27b64395..cb7f6b23c978461 100644
--- a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
+++ b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
@@ -12,4 +12,4 @@ The output will look something like:
 
 ```txt
 SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8662
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
index 77582cb8d22f063..b54554c4a3ae864 100644
--- a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
+++ b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
@@ -6,4 +6,4 @@ To manually refresh your Cloudflare Access session and update your group informa
 
 `https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/refresh-identity`
 
-Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
\ No newline at end of file
+Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
diff --git a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
index 9df1996bb09d5b3..81e72731b5d5abf 100644
--- a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
+++ b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
@@ -1,13 +1,16 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Refer to our [managed deployment instructions](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/) and create a `.plist`, `mdm.xml`, or `.msi` policy file based on your organization's software management tool.
 
-<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we recommend that your policy file only contain the organization name and potentially the onboarding flag, [relying on the dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/) to configure the remaining device settings.
+<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we
+recommend that your policy file only contain the organization name and
+potentially the onboarding flag, [relying on the
+dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/)
+to configure the remaining device settings.
 
 ```xml
 <dict>
diff --git a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
index 40d23df27682b3c..324b01831d1d350 100644
--- a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
+++ b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 The OS version must be specified as a valid [Semver](https://semver.org/). For example, if your device is running OS version `1.2`, you must enter `1.2.0`.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
index e7611c019caec78..591e817aebaf97a 100644
--- a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
+++ b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
@@ -22,4 +22,4 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
 
 <Render file="warp/managed-networks-sha-256" product="cloudflare-one"/>
 
-</TabItem> </Tabs>
\ No newline at end of file
+</TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
index 84e14c59cd4278e..bee309cd06764e9 100644
--- a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
+++ b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
@@ -115,9 +115,9 @@ Avoid vague descriptions and include scenario, timestamps, and steps taken to tr
   <>
     <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p>
 
-    <p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
+<p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
 
-    <p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
+<p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
 
   </>
 ) : props.tunnelMode ? (
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
index d2177c9f8dc51ca..3a4377564d2f4ff 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
-|                       |                                                                               |
-| --------------------- | ----------------------------------------------------------------------------- |
-| **OS version**        | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
-| **Processor**         | AMD64 / x86-64 or ARM64 / AArch64                                   |
-| **HD space**          | 75 MB                                                                         |
-| **Memory**            | 35 MB                                                                         |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^2] |
+|                            |                                                                                                               |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| **OS version**             | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
+| **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                                                             |
+| **HD space**               | 75 MB                                                                                                         |
+| **Memory**                 | 35 MB                                                                                                         |
+| **Network interface type** | Wi-Fi or LAN                                                                                                  |
+| **MTU**                    | 1381 bytes recommended [^2]                                                                                   |
 
 [^1]: On RHEL 9 and later, enable the [Extra Packages for Enterprise Linux (EPEL)](https://docs.fedoraproject.org/en-US/epel/) repository (`sudo dnf install epel-release`) before installing `cloudflare-warp`. EPEL provides dependencies required by the client UI.
 
-[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
index 48053016ac259ca..8742afdde17d699 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-|                       |                                                   |
-| --------------------- | ------------------------------------------------- |
-| **OS version**        | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+                                 |
-| **Processor**         | Intel or M series   |
-| **HD space**          | 75 MB                                             |
-| **Memory**            | 35 MB                                             |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^1] |
+|                            |                                                                    |
+| -------------------------- | ------------------------------------------------------------------ |
+| **OS version**             | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+ |
+| **Processor**              | Intel or M series                                                  |
+| **HD space**               | 75 MB                                                              |
+| **Memory**                 | 35 MB                                                              |
+| **Network interface type** | Wi-Fi or LAN                                                       |
+| **MTU**                    | 1381 bytes recommended [^1]                                        |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
index 7f1dfe65c468ba2..8c0f46bf3c6c5ae 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
-|                            |                                                   |
-| -------------------------- | ------------------------------------------------- |
-| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11                           |
+|                            |                                                                      |
+| -------------------------- | -------------------------------------------------------------------- |
+| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11 |
 | **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                    |
-| **.NET Framework version** | 4.7.2 or later                                    |
-| **HD space**               | 184 MB                                            |
-| **Memory**                 | 3 MB                                              |
-| **Network interface type**  | Wi-Fi or LAN |
-| **MTU** | 1381 bytes recommended [^1] |
+| **.NET Framework version** | 4.7.2 or later                                                       |
+| **HD space**               | 184 MB                                                               |
+| **Memory**                 | 3 MB                                                                 |
+| **Network interface type** | Wi-Fi or LAN                                                         |
+| **MTU**                    | 1381 bytes recommended [^1]                                          |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
diff --git a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
index 168c80b4c6089fd..f13c7f8da379164 100644
--- a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
+++ b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
@@ -1,19 +1,17 @@
 ---
 {}
-
 ---
 
 Perform these steps in the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Team & Resources** > **Devices** > **Device profiles** > **General profiles**.
 
 1. Set your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) to **Exclude IPs and domains**.
 2. [Add the following entries](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to your Split Tunnel Exclude list:
-
-   * Private IP address range exposed by your third-party VPN client. For example,
+   - Private IP address range exposed by your third-party VPN client. For example,
      | Selector | Value |
      | -------- | ----- |
-     | IP Address   | `172.16.0.0/12` |
+     | IP Address | `172.16.0.0/12` |
      |
-   * Server that your third-party VPN client connects to. For example,
+   - Server that your third-party VPN client connects to. For example,
      | Selector | Value |
      | -------- | ----- |
-     | Domain   | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
+     | Domain | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
diff --git a/src/content/partials/cloudflare-one/warp/warp-modes.mdx b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
index ed493a08759ce6b..fe4dbbfb81edeea 100644
--- a/src/content/partials/cloudflare-one/warp/warp-modes.mdx
+++ b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
@@ -4,8 +4,8 @@
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                   | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                          | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/partials/containers/instance-types.mdx b/src/content/partials/containers/instance-types.mdx
index 705a0f3c5970555..0c7e58181689b5f 100644
--- a/src/content/partials/containers/instance-types.mdx
+++ b/src/content/partials/containers/instance-types.mdx
@@ -1,8 +1,8 @@
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------  | ----  |
+| ------------- | ---- | ------- | ----- |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
 | standard-2    | 1    | 6 GiB   | 12 GB |
 | standard-3    | 2    | 8 GiB   | 16 GB |
-| standard-4    | 4    | 12 GiB  | 20 GB |
\ No newline at end of file
+| standard-4    | 4    | 12 GiB  | 20 GB |
diff --git a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
index ea530442f741999..b0f0987a817dc7c 100644
--- a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
+++ b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
@@ -1,6 +1,6 @@
 ---
 params:
-- product
+  - product
 ---
 
 {props.product} a subset of SQLite extensions for added functionality, including:
@@ -9,4 +9,4 @@ params:
 - [JSON extension](https://www.sqlite.org/json1.html) for JSON functions and operators.
 - [Math functions](https://sqlite.org/lang_mathfunc.html).
 
-Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
\ No newline at end of file
+Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
diff --git a/src/content/partials/d1/generate-d1-api-token.mdx b/src/content/partials/d1/generate-d1-api-token.mdx
index 700bee2bfb563e9..2c13c1ba8b60e3d 100644
--- a/src/content/partials/d1/generate-d1-api-token.mdx
+++ b/src/content/partials/d1/generate-d1-api-token.mdx
@@ -21,4 +21,4 @@ import { Steps, DashButton } from "~/components";
 </Steps>
 
 - Refer to [Create API token](/fundamentals/api/get-started/create-token/) for more information on creating API tokens through the Cloudflare dashboard.
-- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
\ No newline at end of file
+- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
index 5c559f1e70ee53e..18b1bdc17d3c358 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
\ No newline at end of file
+Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
index 9a44876d0af0d32..2cba0a9f642281c 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
\ No newline at end of file
+[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
index 1393b132f8df703..54dbbb22ddac8c5 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
@@ -6,4 +6,4 @@
 Advanced TCP and DNS Protection systems are automatically enabled in `Monitor` mode with the default thresholds for new Magic Transit customers and their [authorized prefixes](/magic-transit/how-to/advertise-prefixes/).
 
 Magic Transit customers can also enable the Advanced DDoS systems when the prefixes are ready, change the sensitivity level, or adjust the thresholds by contacting their account team.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
index 3b2d7e3139d2b5a..bd07b8b43cb7890 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
\ No newline at end of file
+Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
index 2c4124f1e232eee..e6d886f65e51b05 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
\ No newline at end of file
+[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
diff --git a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
index a66db33424c00e8..4a2843a4d9281c2 100644
--- a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
+++ b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DDoS reports and DDoS alerts are independent: DDoS reports will include information about any attacks for which you received DDoS alerts.
diff --git a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
index b98f5547923a93c..e752ea9ae03f6d5 100644
--- a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
+++ b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 :::caution[Important]
 
-
 Prefixes in the allowlist will be vulnerable to <GlossaryTooltip term="IP spoofing">IP spoofing</GlossaryTooltip> attacks. If an attacker can guess the source IP addresses you have allowlisted, their packets will be allowlisted.
 
-
 :::
diff --git a/src/content/partials/ddos-protection/atp-filter-definition.mdx b/src/content/partials/ddos-protection/atp-filter-definition.mdx
index 12d6e288ceadf95..523d17768055849 100644
--- a/src/content/partials/ddos-protection/atp-filter-definition.mdx
+++ b/src/content/partials/ddos-protection/atp-filter-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
\ No newline at end of file
+A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
diff --git a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
index 856694a96d0c99c..a961f5d75580c97 100644
--- a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
+++ b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/ddos-protection/create-notification.mdx b/src/content/partials/ddos-protection/create-notification.mdx
index d198471ab167dd0..8a4ea2addd089cb 100644
--- a/src/content/partials/ddos-protection/create-notification.mdx
+++ b/src/content/partials/ddos-protection/create-notification.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
index 6b49ed03060ba7f..b78cd219dfc2f48 100644
--- a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
+++ b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
-| OSI Layer       | Ruleset / Feature                                                                                                      | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| --------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| L3/4            | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                                     | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
-| L3/4            | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1]               | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| L7 (DNS)        | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1]               | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| L7 (HTTP/S)     | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                                 | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                  |
+| OSI Layer   | Ruleset / Feature                                                                                        | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ----------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| L3/4        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                       | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
+| L3/4        | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1] | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| L7 (DNS)    | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1] | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| L7 (HTTP/S) | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                   | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 
 [^1]: Available to Magic Transit customers.
diff --git a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
index 6bd97998baead60..ebb6dc3d1dbdf51 100644
--- a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
+++ b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
\ No newline at end of file
+Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
index ffcd4438247f2b1..a85897a7a575038 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details, Render, Steps, DashButton } from "~/components"
+import { Details, Render, Steps, DashButton } from "~/components";
 
 <Steps>
   1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
@@ -35,4 +35,4 @@ import { Details, Render, Steps, DashButton } from "~/components"
       - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
       :::
   8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
-</Steps>
\ No newline at end of file
+</Steps>
diff --git a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
index b32f56a8b16d56e..03910e37301db8a 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Create multiple rules in the `ddos_l7` phase entry point ruleset to define different overrides for different sets of incoming requests. Set each rule expression according to the traffic whose HTTP DDoS protection you wish to customize.
 
-Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
\ No newline at end of file
+Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
index 21e80e11b8adc25..9b1cf47c23bbb2e 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Highly targeted rules for mitigating DDoS attacks with a high confidence rate. These rules are read-only — you cannot override their sensitivity level or action.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
index 3168c30b815a38a..fcc5ea826e263dc 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The managed ruleset includes some read-only rules that you cannot override.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
index 6f4476224899bd4..0c3e48d1a2ab57c 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 API property name: `"sensitivity_level"`.
@@ -11,15 +10,15 @@ The available sensitivity levels are:
 
 | UI value          | API value   |
 | ----------------- | ----------- |
-| *High*            | `"default"` |
-| *Medium*          | `"medium"`  |
-| *Low*             | `"low"`     |
-| *Essentially Off* | `"eoff"`    |
+| _High_            | `"default"` |
+| _Medium_          | `"medium"`  |
+| _Low_             | `"low"`     |
+| _Essentially Off_ | `"eoff"`    |
 
-The default sensitivity level is *High*.
+The default sensitivity level is _High_.
 
-In most cases, when you select the *Essentially Off* sensitivity level the rule will not trigger for any of the selected actions, including *Log*. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
+In most cases, when you select the _Essentially Off_ sensitivity level the rule will not trigger for any of the selected actions, including _Log_. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
 
-*Essentially Off* means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+_Essentially Off_ means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
 
-**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
\ No newline at end of file
+**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
index 72d2abd12cf1632..2b38abe2e55abcf 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Rules used for testing the detection, mitigation, and alerting capabilities of Cloudflare's DDoS protection products.
diff --git a/src/content/partials/ddos-protection/override-example.mdx b/src/content/partials/ddos-protection/override-example.mdx
index 4e8d68a92360f5f..c25df1b5a153d19 100644
--- a/src/content/partials/ddos-protection/override-example.mdx
+++ b/src/content/partials/ddos-protection/override-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Example
@@ -14,33 +13,33 @@ A DDoS managed ruleset contains the following managed rules:
 The following ruleset overrides have been configured:
 
 - **Ruleset override A**
-   - **Managed rule 1** is set to `block`
+  - **Managed rule 1** is set to `block`
 - **Ruleset override B**
-   - The action of the entire ruleset (or *all managed rules*) is set to `Managed Challenge`
-   - **Managed rule 1** is set to `log`
-   - **Managed rule 2** is set to `log`
+  - The action of the entire ruleset (or _all managed rules_) is set to `Managed Challenge`
+  - **Managed rule 1** is set to `log`
+  - **Managed rule 2** is set to `log`
 - **Ruleset override C**
-   - **Managed rule 3** is set to `log`
+  - **Managed rule 3** is set to `log`
 
-### Use case 
+### Use case
 
 A DDoS attack was detected on **managed rules 1**, **2**, and **3**, and has generated a mitigation rule.
 
-- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules. 
+- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules.
 
 - **Managed rule 2** does not match **ruleset override A**, so Cloudflare proceeds to **ruleset override B**. <br /> **Ruleset override B** matches both all managed rules and **managed rule 2**, but specificity takes precedence. It does not `challenge` and instead proceeds with `log` since it matches the most specific managed rule.
 
-- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets *all managed rules* to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
+- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets _all managed rules_ to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
 
 An additional dimension to take into account is Cloudflare’s DDoS systems will apply a given rule override only if its conditions are met — which includes the Sensitivity level. So, while it needs to match and modify the correct managed rule (or everything in the case of all managed rules above), it also has to meet the specified Sensitivity level of the rule.
 
 - **Rule override A**
-   - *All managed rules* are set to `challenge` at low sensitivity
+  - _All managed rules_ are set to `challenge` at low sensitivity
 
 - **Rule override B**
-   - **Managed rule 1** is set to `log` at default sensitivity
+  - **Managed rule 1** is set to `log` at default sensitivity
 
 You receive a small attack below the threshold for low sensitivity, but above the threshold for high sensitivity on **managed rule 1**.
 
-- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate. 
-- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
\ No newline at end of file
+- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate.
+- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
diff --git a/src/content/partials/ddos-protection/override-logic.mdx b/src/content/partials/ddos-protection/override-logic.mdx
index b9ff54257029827..a4cde6e1c07ac0b 100644
--- a/src/content/partials/ddos-protection/override-logic.mdx
+++ b/src/content/partials/ddos-protection/override-logic.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
 When Cloudflare's DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection managed ruleset. Each mitigation rule is generated from a single managed rule.
 
-All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches. 
+All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches.
 
-You can create only one ruleset override that can contain one or multiple rule overrides. 
+You can create only one ruleset override that can contain one or multiple rule overrides.
 
 :::note
 Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) add-on can create up to 10 ruleset overrides.
@@ -15,4 +14,4 @@ Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanc
 
 A rule override instructs the DDoS system on the action it should take against the attack according to its matching managed rule.
 
-However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override. 
\ No newline at end of file
+However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override.
diff --git a/src/content/partials/dmarc-management/domain-spoofing.mdx b/src/content/partials/dmarc-management/domain-spoofing.mdx
index f67efe27497fedf..789d26bbd41acbb 100644
--- a/src/content/partials/dmarc-management/domain-spoofing.mdx
+++ b/src/content/partials/dmarc-management/domain-spoofing.mdx
@@ -10,8 +10,6 @@ Without email authentication records, anyone can send email that appears to come
 
 :::note
 
-
 For additional background on email security records, refer to the [introductory blog post](https://blog.cloudflare.com/tackling-email-spoofing/).
 
-
 :::
diff --git a/src/content/partials/dns/a-aaaa-definition.mdx b/src/content/partials/dns/a-aaaa-definition.mdx
index 382543d232d0715..7871b0c522c087c 100644
--- a/src/content/partials/dns/a-aaaa-definition.mdx
+++ b/src/content/partials/dns/a-aaaa-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [A and AAAA records](https://www.cloudflare.com/learning/dns/dns-records/dns-a-record/) map a domain name to one or multiple IPv4 or IPv6 address(es).
diff --git a/src/content/partials/dns/acns-tcns-byoip.mdx b/src/content/partials/dns/acns-tcns-byoip.mdx
index 0184972c95cb464..d54a916972d3a46 100644
--- a/src/content/partials/dns/acns-tcns-byoip.mdx
+++ b/src/content/partials/dns/acns-tcns-byoip.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::note
 
diff --git a/src/content/partials/dns/acns-tcns-conditions.mdx b/src/content/partials/dns/acns-tcns-conditions.mdx
index 910dee1af8bb028..8ffad8ef38a32d5 100644
--- a/src/content/partials/dns/acns-tcns-conditions.mdx
+++ b/src/content/partials/dns/acns-tcns-conditions.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2;;param3
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-* {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
-* [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
+- {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
+- [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
diff --git a/src/content/partials/dns/acns-tcns-intro.mdx b/src/content/partials/dns/acns-tcns-intro.mdx
index d75bd29c06d9035..4089262cc29499c 100644
--- a/src/content/partials/dns/acns-tcns-intro.mdx
+++ b/src/content/partials/dns/acns-tcns-intro.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1;;param2;;param3;;param4;;param5
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 {props.one} custom nameservers ({props.two}CNS) allow you to define {props.three}-level custom nameservers and use them for different {props.four} within a Cloudflare {props.five}.
 
diff --git a/src/content/partials/dns/aname-alias-callout.mdx b/src/content/partials/dns/aname-alias-callout.mdx
index 6751169d5c78778..e958df71d713e10 100644
--- a/src/content/partials/dns/aname-alias-callout.mdx
+++ b/src/content/partials/dns/aname-alias-callout.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's [CNAME flattening](/dns/cname-flattening/)[^1] allows you to create CNAME records at your [zone apex](/dns/concepts/#zone-apex), removing the need for those other record types.
 
-[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
\ No newline at end of file
+[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
diff --git a/src/content/partials/dns/api-field-definitions.mdx b/src/content/partials/dns/api-field-definitions.mdx
index af7ea90d28101b2..2629350da26de28 100644
--- a/src/content/partials/dns/api-field-definitions.mdx
+++ b/src/content/partials/dns/api-field-definitions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For field definitions, refer to the [API documentation](/api/resources/dns/subresources/records/methods/create/) (visible once you select the record type under the request body specification).
diff --git a/src/content/partials/dns/cname-definition.mdx b/src/content/partials/dns/cname-definition.mdx
index ac977bc79ea7fe9..324c92c3d9865a3 100644
--- a/src/content/partials/dns/cname-definition.mdx
+++ b/src/content/partials/dns/cname-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [CNAME records](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/) map a domain name to another (canonical) domain name. They can be used to resolve other record types present on the target domain name.
diff --git a/src/content/partials/dns/cname-flattening-callout.mdx b/src/content/partials/dns/cname-flattening-callout.mdx
index 030fec534c89c49..000688fb842401b 100644
--- a/src/content/partials/dns/cname-flattening-callout.mdx
+++ b/src/content/partials/dns/cname-flattening-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If a CNAME target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the CNAME record itself will not be returned directly.
diff --git a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
index 2d6ccf3c0e1d1b4..6c9b25d037c6bfd 100644
--- a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
+++ b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Subdomain setup]
 If you also use subdomain setup[^1], consider the [available combinations](/dns/zone-setups/subdomain-setup/setup/#available-setups) and whether your zone conversion could have any implications.
 :::
 
-[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
\ No newline at end of file
+[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
diff --git a/src/content/partials/dns/dns-errors-ts-action.mdx b/src/content/partials/dns/dns-errors-ts-action.mdx
index 9dfa15e76d1dfa6..4d2f0fe2811d7d4 100644
--- a/src/content/partials/dns/dns-errors-ts-action.mdx
+++ b/src/content/partials/dns/dns-errors-ts-action.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: errorName
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 If you experience <code>{props.one}</code> errors with a newly activated domain, review your DNS settings in the Cloudflare dashboard.
 
diff --git a/src/content/partials/dns/dns-errors-ts-intro.mdx b/src/content/partials/dns/dns-errors-ts-intro.mdx
index cb332968acfcf3d..d1d1d3950aaa5fa 100644
--- a/src/content/partials/dns/dns-errors-ts-intro.mdx
+++ b/src/content/partials/dns/dns-errors-ts-intro.mdx
@@ -1,16 +1,13 @@
 ---
 inputParameters: errorName
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 If you or your visitors experience <code>{props.one}</code> errors after you [activate your domain on Cloudflare](/dns/zone-setups/full-setup/setup/), review your DNS records in Cloudflare.
 
 :::note
 
-
 If your domain is added to Cloudflare by a hosting partner, manage your DNS records via the hosting partner.
 
-
 :::
diff --git a/src/content/partials/dns/dns-nxdomain-warning.mdx b/src/content/partials/dns/dns-nxdomain-warning.mdx
index d9b592cdc25513c..a0aa3e538b03546 100644
--- a/src/content/partials/dns/dns-nxdomain-warning.mdx
+++ b/src/content/partials/dns/dns-nxdomain-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
-If you activate your domain on Cloudflare *without* setting up the correct DNS records for your domain, your visitors may experience [DNS\_PROBE\_FINISHED\_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
-
+If you activate your domain on Cloudflare _without_ setting up the correct DNS records for your domain, your visitors may experience [DNS_PROBE_FINISHED_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
 
 :::
diff --git a/src/content/partials/dns/dns-record-steps.mdx b/src/content/partials/dns/dns-record-steps.mdx
index 058a0bf5c7cacfd..8ab4783d7d17bee 100644
--- a/src/content/partials/dns/dns-record-steps.mdx
+++ b/src/content/partials/dns/dns-record-steps.mdx
@@ -4,7 +4,13 @@ params:
   - example
 ---
 
-import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	Render,
+	GlossaryTooltip,
+	DashButton,
+} from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
@@ -27,4 +33,4 @@ Use the [Create DNS Record API endpoint](/api/resources/dns/subresources/records
     - To point to an IPv6 address, select **AAAA Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the IPv6 address for the field `content`.
     - To point to a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (such as `your-site.host.example.com`), select **CNAME Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the fully qualified domain name for the field `content`.
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/src/content/partials/dns/dns-scan-intro.mdx b/src/content/partials/dns/dns-scan-intro.mdx
index 8901df100607fa7..e54726a33bab66b 100644
--- a/src/content/partials/dns/dns-scan-intro.mdx
+++ b/src/content/partials/dns/dns-scan-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/dns-scan-note.mdx b/src/content/partials/dns/dns-scan-note.mdx
index 636218d0b27de88..eff151ba8112ac8 100644
--- a/src/content/partials/dns/dns-scan-note.mdx
+++ b/src/content/partials/dns/dns-scan-note.mdx
@@ -1,5 +1,5 @@
 ---
 {}
-
 ---
+
 If you add a zone via the [API](/api/resources/zones/methods/create/), you can manually invoke the quick scan with the [Trigger DNS Records Scan endpoint](/api/resources/dns/subresources/records/methods/scan_trigger/).
diff --git a/src/content/partials/dns/dnssec-auto-add.mdx b/src/content/partials/dns/dnssec-auto-add.mdx
index c59ce7dadf53c5d..692574c3903a3ce 100644
--- a/src/content/partials/dns/dnssec-auto-add.mdx
+++ b/src/content/partials/dns/dnssec-auto-add.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Note:]
 
-
 Cloudflare automatically adds **DS** records for domains using Cloudflare Registrar or those using `.ch` and `.cz` top-level domains.
 
-
 :::
diff --git a/src/content/partials/dns/dnssec-cloudflare-steps.mdx b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
index d066c3e5a606e96..97e0be8c4a00e2d 100644
--- a/src/content/partials/dns/dnssec-cloudflare-steps.mdx
+++ b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/dns/dnssec-definition.mdx b/src/content/partials/dns/dnssec-definition.mdx
index 8e4f721549a3dcd..e286d2e3f82b1ed 100644
--- a/src/content/partials/dns/dnssec-definition.mdx
+++ b/src/content/partials/dns/dnssec-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS Security Extensions (DNSSEC) adds an extra layer of authentication to DNS, ensuring requests are not routed to a spoofed domain.
diff --git a/src/content/partials/dns/dnssec-enabled-migration.mdx b/src/content/partials/dns/dnssec-enabled-migration.mdx
index 2baa9a405746770..34be4c281d852e9 100644
--- a/src/content/partials/dns/dnssec-enabled-migration.mdx
+++ b/src/content/partials/dns/dnssec-enabled-migration.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If your previous provider allows you to add DNSKEY records on the zone apex and use these records in responses to DNS queries, refer to this [migration tutorial](/dns/dnssec/dnssec-active-migration/) to learn how to migrate a zone with DNSSEC enabled.
 
-
 :::
diff --git a/src/content/partials/dns/dnssec-registrar-steps.mdx b/src/content/partials/dns/dnssec-registrar-steps.mdx
index 60a42cb75248c8b..bb870033de61d09 100644
--- a/src/content/partials/dns/dnssec-registrar-steps.mdx
+++ b/src/content/partials/dns/dnssec-registrar-steps.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called *ECDSA Curve P-256 with SHA-256*.
+Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called _ECDSA Curve P-256 with SHA-256_.
 
 <Render file="dnssec-providers" product="dns" />
diff --git a/src/content/partials/dns/export-dns-records.mdx b/src/content/partials/dns/export-dns-records.mdx
index 1f8697f19614b35..1c63cb825b5f494 100644
--- a/src/content/partials/dns/export-dns-records.mdx
+++ b/src/content/partials/dns/export-dns-records.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
diff --git a/src/content/partials/dns/internal-dns-beta-note.mdx b/src/content/partials/dns/internal-dns-beta-note.mdx
index 5d69d57445eafa7..5f59566c426a379 100644
--- a/src/content/partials/dns/internal-dns-beta-note.mdx
+++ b/src/content/partials/dns/internal-dns-beta-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/internal-dns-view-conditions.mdx b/src/content/partials/dns/internal-dns-view-conditions.mdx
index b28ccc739a2b0fc..864542fca83a966 100644
--- a/src/content/partials/dns/internal-dns-view-conditions.mdx
+++ b/src/content/partials/dns/internal-dns-view-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - DNS views can be empty, with no [internal zones](/dns/internal-dns/internal-zones/) linked to them.
@@ -8,4 +7,5 @@
 - Each internal DNS zone name must be unique within a given DNS view.
 - Each DNS view name must be unique within a given Cloudflare account.
 
-<sup>1</sup> DNS zones that contain public DNS records and are accessible by public resolvers.
\ No newline at end of file
+<sup>1</sup> DNS zones that contain public DNS records and are accessible by
+public resolvers.
diff --git a/src/content/partials/dns/internal-reference-zone-api.mdx b/src/content/partials/dns/internal-reference-zone-api.mdx
index 05e1180d9227406..830c568f97e562c 100644
--- a/src/content/partials/dns/internal-reference-zone-api.mdx
+++ b/src/content/partials/dns/internal-reference-zone-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -10,14 +9,12 @@ In the following example, internal zone A (ID `8a904aeb565c42cfa207d98f6edea2f3`
 <APIRequest
 	path="/zones/{zone_id}/dns_settings"
 	method="PATCH"
-	json={
-		{
-    "internal_dns": {
-        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51"
-    }
-		}
-	}
+	json={{
+		internal_dns: {
+			reference_zone_id: "8e64c6fb4b514f3faf64de81efc11e51",
+		},
+	}}
 	parameters={{
 		zone_id: "8a904aeb565c42cfa207d98f6edea2f3",
 	}}
-/>
\ No newline at end of file
+/>
diff --git a/src/content/partials/dns/internal-reference-zone-intro.mdx b/src/content/partials/dns/internal-reference-zone-intro.mdx
index 71d7c7621b8fda4..94e58c8e201d0d8 100644
--- a/src/content/partials/dns/internal-reference-zone-intro.mdx
+++ b/src/content/partials/dns/internal-reference-zone-intro.mdx
@@ -5,10 +5,9 @@ params:
 
 During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain.
 
-
 { props.conditional === "get-started-link" && (
-	<p>
-	For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
-	</p>
-	)
-}
\ No newline at end of file
+<p>
+For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
+</p>
+)
+}
diff --git a/src/content/partials/dns/internal-zones-conditions.mdx b/src/content/partials/dns/internal-zones-conditions.mdx
index 64201918a6fb264..33e00fe187436c9 100644
--- a/src/content/partials/dns/internal-zones-conditions.mdx
+++ b/src/content/partials/dns/internal-zones-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
@@ -9,4 +8,5 @@
 - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
 - Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`).
 
-<sup>1</sup> Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved.
\ No newline at end of file
+<sup>1</sup> Logical groupings of internal DNS zones that are referenced by
+Gateway resolver policies to define how a specific query should be resolved.
diff --git a/src/content/partials/dns/linked-peers-limit.mdx b/src/content/partials/dns/linked-peers-limit.mdx
index 07cf4abcd9e4cc3..c18d3fb2b701548 100644
--- a/src/content/partials/dns/linked-peers-limit.mdx
+++ b/src/content/partials/dns/linked-peers-limit.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The maximum number of linked peers per zone is 30.
diff --git a/src/content/partials/dns/minimize-downtime-tip.mdx b/src/content/partials/dns/minimize-downtime-tip.mdx
index b13c26fb8eaa702..ca7fae767a4d48c 100644
--- a/src/content/partials/dns/minimize-downtime-tip.mdx
+++ b/src/content/partials/dns/minimize-downtime-tip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
\ No newline at end of file
+If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
diff --git a/src/content/partials/dns/mix-proxied-and-unproxied.mdx b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
index 8b12a1d041c6e54..c028f99ad6ccb3b 100644
--- a/src/content/partials/dns/mix-proxied-and-unproxied.mdx
+++ b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If you have multiple `A/AAAA` records on the same name and at least one of them is proxied, Cloudflare will treat all `A/AAAA` records on this name as being proxied.
 
-
 :::
diff --git a/src/content/partials/dns/nameserver-preamble.mdx b/src/content/partials/dns/nameserver-preamble.mdx
index 96bf1107d118e88..5b17906420c1020 100644
--- a/src/content/partials/dns/nameserver-preamble.mdx
+++ b/src/content/partials/dns/nameserver-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/nameservers-registrar-callout.mdx b/src/content/partials/dns/nameservers-registrar-callout.mdx
index efdd668bfb70fc7..afcec9106f1f765 100644
--- a/src/content/partials/dns/nameservers-registrar-callout.mdx
+++ b/src/content/partials/dns/nameservers-registrar-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Cloudflare Registrar]
diff --git a/src/content/partials/dns/ns-advanced-vs-custom.mdx b/src/content/partials/dns/ns-advanced-vs-custom.mdx
index 085c0ab10e67144..42e1cfe62cc3fb3 100644
--- a/src/content/partials/dns/ns-advanced-vs-custom.mdx
+++ b/src/content/partials/dns/ns-advanced-vs-custom.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The advantages that come with Foundation DNS [advanced nameservers](/dns/foundation-dns/advanced-nameservers/) are currently not available for [custom nameservers](/dns/nameservers/custom-nameservers/). Make sure you only use one at a time.
diff --git a/src/content/partials/dns/ns-set-omission-callout.mdx b/src/content/partials/dns/ns-set-omission-callout.mdx
index 4255ed43dcb62dd..aceb7ef494144c3 100644
--- a/src/content/partials/dns/ns-set-omission-callout.mdx
+++ b/src/content/partials/dns/ns-set-omission-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/ns-static-ips.mdx b/src/content/partials/dns/ns-static-ips.mdx
index 33542f81098b4ae..f7cb24564edd03d 100644
--- a/src/content/partials/dns/ns-static-ips.mdx
+++ b/src/content/partials/dns/ns-static-ips.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The IPs assigned to each nameserver are static, meaning they will not change without notification.
\ No newline at end of file
+The IPs assigned to each nameserver are static, meaning they will not change without notification.
diff --git a/src/content/partials/dns/ns-update-providers.mdx b/src/content/partials/dns/ns-update-providers.mdx
index 4619e0f648cd65c..207b9774b87ee74 100644
--- a/src/content/partials/dns/ns-update-providers.mdx
+++ b/src/content/partials/dns/ns-update-providers.mdx
@@ -1,42 +1,41 @@
 ---
 {}
-
 ---
 
 This is not an exhaustive list of provider-specific instructions, but the following links may be helpful:
 
-* [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
-* [101Domain](https://help.101domain.com/kb/managing-name-server-records)
-* [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
-* [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
-* [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
-* [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
-* [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
-* [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
-* [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
-* [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
-* [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
-* [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
-* [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
-* [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
-* [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
-* [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
-* [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
-* [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
-* [HostMonster](https://my.hostmonster.com/cgi/help/222)
-* [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
-* [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
-* [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
-* [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
-* [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
-* [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
-* [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
-* [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
-* [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
-* [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
-* [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
-* [Register](https://www.register.com/knowledge)
-* [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
-* [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
-* [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
-* [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
+- [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
+- [101Domain](https://help.101domain.com/kb/managing-name-server-records)
+- [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
+- [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
+- [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
+- [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
+- [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
+- [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
+- [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
+- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
+- [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
+- [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
+- [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
+- [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
+- [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
+- [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
+- [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
+- [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
+- [HostMonster](https://my.hostmonster.com/cgi/help/222)
+- [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
+- [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
+- [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
+- [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
+- [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
+- [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
+- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
+- [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
+- [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
+- [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
+- [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
+- [Register](https://www.register.com/knowledge)
+- [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
+- [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
+- [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
+- [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
diff --git a/src/content/partials/dns/onboard-warning.mdx b/src/content/partials/dns/onboard-warning.mdx
index cd609c994c7516f..883289d67398e5e 100644
--- a/src/content/partials/dns/onboard-warning.mdx
+++ b/src/content/partials/dns/onboard-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you [add a domain](/fundamentals/manage-domains/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
diff --git a/src/content/partials/dns/partial-setup-definition.mdx b/src/content/partials/dns/partial-setup-definition.mdx
index d4a185c7c288b4c..d429d6c760396ab 100644
--- a/src/content/partials/dns/partial-setup-definition.mdx
+++ b/src/content/partials/dns/partial-setup-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 A CNAME setup (also known as partial setup) allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
 
diff --git a/src/content/partials/dns/random-prefix-attack-definition.mdx b/src/content/partials/dns/random-prefix-attack-definition.mdx
index 421e48350e97627..3a4378c97f94a4e 100644
--- a/src/content/partials/dns/random-prefix-attack-definition.mdx
+++ b/src/content/partials/dns/random-prefix-attack-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Random prefix attacks are when someone sends a lot of traffic to subdomains that are highly unlikely to exist (`12345.example.com`, `abcdefg.example.com`), but are still associated with your main domain (`example.com`).
diff --git a/src/content/partials/dns/records-name-field.mdx b/src/content/partials/dns/records-name-field.mdx
index ed33e8cf7fea2e3..ed19a6fb9b2d987 100644
--- a/src/content/partials/dns/records-name-field.mdx
+++ b/src/content/partials/dns/records-name-field.mdx
@@ -3,7 +3,7 @@
 ---
 
 - **Name**: A subdomain or the zone apex (`@`).
-	- The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
-	- DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
-	- There is no requirement to start with a letter or end with a letter or digit.
-	- Underscores are valid in DNS and commonly used for service records.
+  - The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
+  - DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
+  - There is no requirement to start with a letter or end with a letter or digit.
+  - Underscores are valid in DNS and commonly used for service records.
diff --git a/src/content/partials/dns/recover-deleted-domain.mdx b/src/content/partials/dns/recover-deleted-domain.mdx
index 04ea32052b4199c..dd9da29b1c18d12 100644
--- a/src/content/partials/dns/recover-deleted-domain.mdx
+++ b/src/content/partials/dns/recover-deleted-domain.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/manage-domains/add-site/) just like you would for a new domain.
diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx
index 3addd6a512c230f..8a76949a59dd2f5 100644
--- a/src/content/partials/dns/secondary-conversion-unlink.mdx
+++ b/src/content/partials/dns/secondary-conversion-unlink.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -12,4 +11,4 @@ import { DashButton } from "~/components";
 2. Under **DNS Zone Transfers**, and select **Manage linked peers**.
 3. Unlink the peer and select **Save**.
 
-At this point, your zone will be read-only.
\ No newline at end of file
+At this point, your zone will be read-only.
diff --git a/src/content/partials/dns/secondary-dns-override.mdx b/src/content/partials/dns/secondary-dns-override.mdx
index 3479cba6efadd24..e85867604e92094 100644
--- a/src/content/partials/dns/secondary-dns-override.mdx
+++ b/src/content/partials/dns/secondary-dns-override.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Normal incoming zone transfers only provide DNS resolution. If you also want your traffic to benefit from Cloudflare's performance and security features, you need to [set up Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/).
diff --git a/src/content/partials/dns/ssltls-subdomains.mdx b/src/content/partials/dns/ssltls-subdomains.mdx
index 7509364e5359f30..65f7bae8f4f3cc0 100644
--- a/src/content/partials/dns/ssltls-subdomains.mdx
+++ b/src/content/partials/dns/ssltls-subdomains.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your main domain is using Cloudflare's [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/), that certificate also covers all first-level subdomains (`blog.example.com`).
diff --git a/src/content/partials/dns/subdomain-customization.mdx b/src/content/partials/dns/subdomain-customization.mdx
index b3d2fc5d81bd5a3..ca49fdca438e461 100644
--- a/src/content/partials/dns/subdomain-customization.mdx
+++ b/src/content/partials/dns/subdomain-customization.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to customize Cloudflare settings for individual subdomains, your approach will vary depending on your plan.
diff --git a/src/content/partials/dns/third-party-caveat.mdx b/src/content/partials/dns/third-party-caveat.mdx
index 32f0740937afdaf..aa50c4ed3da9acf 100644
--- a/src/content/partials/dns/third-party-caveat.mdx
+++ b/src/content/partials/dns/third-party-caveat.mdx
@@ -1,14 +1,11 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::note
 
-
 When you [add records to Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/), those records should be [DNS-only (unproxied)](/dns/proxy-status/#dns-only-records) until {props.one} verifies your domain. Then, you can switch your DNS records to **Proxied**.
 
-
 :::
diff --git a/src/content/partials/dns/tsig-create-api.mdx b/src/content/partials/dns/tsig-create-api.mdx
index 0ca5c0a9ba3903e..240a4ecc1800410 100644
--- a/src/content/partials/dns/tsig-create-api.mdx
+++ b/src/content/partials/dns/tsig-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create a TSIG using the API, send a [POST](/api/resources/dns/subresources/zone_transfers/subresources/tsigs/methods/create/) request.
diff --git a/src/content/partials/dns/tsig-create-dash.mdx b/src/content/partials/dns/tsig-create-dash.mdx
index b93345590415a34..df306405d917d0e 100644
--- a/src/content/partials/dns/tsig-create-dash.mdx
+++ b/src/content/partials/dns/tsig-create-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -14,7 +13,7 @@ To create a TSIG using the dashboard:
 2. Go to **DNS Settings**.
 3. Under **DNS Zone Transfers**, for **TSIG**, select **Create**.
 4. Enter the following information:
-   * **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
-   * **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
-   * **Algorithm**: Choose a TSIG signing algorithm.
+   - **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
+   - **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
+   - **Algorithm**: Choose a TSIG signing algorithm.
 5. Select **Create**.
diff --git a/src/content/partials/dns/tsig-definition.mdx b/src/content/partials/dns/tsig-definition.mdx
index 74fe88b3a4ddd3a..be7c2d62be93667 100644
--- a/src/content/partials/dns/tsig-definition.mdx
+++ b/src/content/partials/dns/tsig-definition.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 A Transaction Signature (TSIG) authenticates communication between a primary and secondary DNS server.
 
diff --git a/src/content/partials/dns/tsig-name-match.mdx b/src/content/partials/dns/tsig-name-match.mdx
index ffaa6bc70ebfc62..dffb08898eb97bf 100644
--- a/src/content/partials/dns/tsig-name-match.mdx
+++ b/src/content/partials/dns/tsig-name-match.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/dns/why-disable-dnssec.mdx b/src/content/partials/dns/why-disable-dnssec.mdx
index 57db63f976fd9d8..2b37d7c7fa26608 100644
--- a/src/content/partials/dns/why-disable-dnssec.mdx
+++ b/src/content/partials/dns/why-disable-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When your domain has [DNSSEC enabled](https://www.cloudflare.com/learning/dns/dns-security/#what-is-dnssec), your DNS provider digitally signs all your DNS records. This action prevents anyone else from issuing false DNS records on your behalf and redirecting traffic intended for your domain.
diff --git a/src/content/partials/dns/zone-defaults-exceptions.mdx b/src/content/partials/dns/zone-defaults-exceptions.mdx
index 5005703713f7f89..1e74b26d026a49a 100644
--- a/src/content/partials/dns/zone-defaults-exceptions.mdx
+++ b/src/content/partials/dns/zone-defaults-exceptions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones, nor zones that existed previously and are being revived.
diff --git a/src/content/partials/dns/zone-file-size-limit.mdx b/src/content/partials/dns/zone-file-size-limit.mdx
index 4873764d6189ff0..71afea606b6bc17 100644
--- a/src/content/partials/dns/zone-file-size-limit.mdx
+++ b/src/content/partials/dns/zone-file-size-limit.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The zone file size limit is 256 KiB (262144 bytes).
diff --git a/src/content/partials/durable-objects/api-async-kv-legacy.mdx b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
index 1ef05ec94c61a03..a2698461e2eebcd 100644
--- a/src/content/partials/durable-objects/api-async-kv-legacy.mdx
+++ b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Type, MetaInfo, AnchorHeading} from "~/components";
+import { Type, MetaInfo, AnchorHeading } from "~/components";
 
 <AnchorHeading title="get" slug="do-kv-async-get" depth={3} />
 
@@ -107,4 +107,4 @@ The `put()` method returns a `Promise`, but most applications can discard this p
   - Same as the option to [`get()`](#do-kv-async-get), above.
 
 - `noCache` <Type text ='boolean' />
-  - Same as the option to [`get()`](#do-kv-async-get), above.
\ No newline at end of file
+  - Same as the option to [`get()`](#do-kv-async-get), above.
diff --git a/src/content/partials/durable-objects/api-storage-alarms.mdx b/src/content/partials/durable-objects/api-storage-alarms.mdx
index 8deccef0d3d08f2..1014b07d6080c01 100644
--- a/src/content/partials/durable-objects/api-storage-alarms.mdx
+++ b/src/content/partials/durable-objects/api-storage-alarms.mdx
@@ -27,4 +27,4 @@ import { Type, MetaInfo, Render } from "~/components";
 
 #### Supported options
 
-- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
\ No newline at end of file
+- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
diff --git a/src/content/partials/durable-objects/api-storage-other-methods.mdx b/src/content/partials/durable-objects/api-storage-other-methods.mdx
index 05bf6d643f93346..50cc1584f88f26d 100644
--- a/src/content/partials/durable-objects/api-storage-other-methods.mdx
+++ b/src/content/partials/durable-objects/api-storage-other-methods.mdx
@@ -39,4 +39,4 @@ import { Type, MetaInfo } from "~/components";
 - `sync()`: <Type text='Promise' />
   - Synchronizes any pending writes to disk.
 
-  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
\ No newline at end of file
+  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
diff --git a/src/content/partials/durable-objects/api-sync-kv.mdx b/src/content/partials/durable-objects/api-sync-kv.mdx
index 816f231f927d279..84a39a044b3d293 100644
--- a/src/content/partials/durable-objects/api-sync-kv.mdx
+++ b/src/content/partials/durable-objects/api-sync-kv.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {Type, MetaInfo} from "~/components";
+import { Type, MetaInfo } from "~/components";
 
 ### `get`
 
diff --git a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
index ea25a405ba4567b..c869d21821c71a3 100644
--- a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
+++ b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
@@ -2,8 +2,8 @@
 {}
 ---
 
-import {GlossaryTooltip, WranglerConfig} from "~/components";
+import { GlossaryTooltip, WranglerConfig } from "~/components";
 
 ### How can I identify which Durable Object instance generated a log entry?
 
-You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
\ No newline at end of file
+You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
diff --git a/src/content/partials/durable-objects/do-plans-note.mdx b/src/content/partials/durable-objects/do-plans-note.mdx
index 36771fa0ccba055..3c7cb86f3649773 100644
--- a/src/content/partials/durable-objects/do-plans-note.mdx
+++ b/src/content/partials/durable-objects/do-plans-note.mdx
@@ -9,4 +9,4 @@ Durable Objects are available both on Workers Free and Workers Paid plans.
 - **Workers Paid plan**: Durable Objects with either SQLite storage backend or [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) are available.
 
 If you wish to downgrade from a Workers Paid plan to a Workers Free plan, you must first ensure that you have deleted all Durable Object namespaces with the key-value storage backend.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/durable-objects/durable-objects-sql.mdx b/src/content/partials/durable-objects/durable-objects-sql.mdx
index 43eb7777f652040..b13e5deb71af0d6 100644
--- a/src/content/partials/durable-objects/durable-objects-sql.mdx
+++ b/src/content/partials/durable-objects/durable-objects-sql.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
 [SQL API](/durable-objects/api/sqlite-storage-api/#exec) examples below use the following SQL schema:
 
@@ -10,102 +10,114 @@ import { Details } from "~/components"
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-  sql: SqlStorage
-  constructor(ctx: DurableObjectState, env: Env) {
-    super(ctx, env);
-    this.sql = ctx.storage.sql;
+	sql: SqlStorage;
+	constructor(ctx: DurableObjectState, env: Env) {
+		super(ctx, env);
+		this.sql = ctx.storage.sql;
 
-    this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
+		this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
       artistid    INTEGER PRIMARY KEY,
       artistname  TEXT
     );INSERT INTO artist (artistid, artistname) VALUES
       (123, 'Alice'),
       (456, 'Bob'),
-      (789, 'Charlie');`
-    );
-  }
+      (789, 'Charlie');`);
+	}
 }
 ```
 
 Iterate over query results as row objects:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist;");
+let cursor = this.sql.exec("SELECT * FROM artist;");
 
-  for (let row of cursor) {
-    // Iterate over row object and do something
-  }
+for (let row of cursor) {
+	// Iterate over row object and do something
+}
 ```
 
 Convert query results to an array of row objects:
+
 ```ts
-  // Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
-  let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
-  // OR
-  let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
-  // OR
-  let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
+// Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
+let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
+// OR
+let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
+// OR
+let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
 ```
 
 Convert query results to an array of row values arrays:
-```ts
-  // Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
-  let cursor = this.sql.exec("SELECT * FROM artist;");
-  let resultsArray = cursor.raw().toArray();
 
-  // Returns ["artistid","artistname"]
-  let columnNameArray = this.sql.exec("SELECT * FROM artist;").columnNames.toArray();
+```ts
+// Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
+let cursor = this.sql.exec("SELECT * FROM artist;");
+let resultsArray = cursor.raw().toArray();
+
+// Returns ["artistid","artistname"]
+let columnNameArray = this.sql
+	.exec("SELECT * FROM artist;")
+	.columnNames.toArray();
 ```
 
 Get first row object of query results:
+
 ```ts
-  // Returns {"artistid":123,"artistname":"Alice"}
-  let firstRow = this.sql.exec("SELECT * FROM artist ORDER BY artistname DESC;").toArray()[0];
+// Returns {"artistid":123,"artistname":"Alice"}
+let firstRow = this.sql
+	.exec("SELECT * FROM artist ORDER BY artistname DESC;")
+	.toArray()[0];
 ```
 
 Check if query results have exactly one row:
+
 ```ts
-  // returns error
-  this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
+// returns error
+this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
 
-  // returns { artistid: 123, artistname: 'Alice' }
-  let oneRow = this.sql.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice").one()
+// returns { artistid: 123, artistname: 'Alice' }
+let oneRow = this.sql
+	.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice")
+	.one();
 ```
 
 Returned cursor behavior:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-  let result = cursor.next();
-  if (!result.done) {
-    console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
-  } else {
-    // query returned zero results
-  }
-
-  let remainingRows = cursor.toArray();
-  console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+let result = cursor.next();
+if (!result.done) {
+	console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
+} else {
+	// query returned zero results
+}
+
+let remainingRows = cursor.toArray();
+console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 Returned cursor and `raw()` iterator iterate over the same query results:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-  let result = cursor.raw().next();
+let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+let result = cursor.raw().next();
 
-  if (!result.done) {
-    console.log(result.value); // prints [ 123, 'Alice' ]
-  } else {
-    // query returned zero results
-  }
+if (!result.done) {
+	console.log(result.value); // prints [ 123, 'Alice' ]
+} else {
+	// query returned zero results
+}
 
-  console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 `sql.exec().rowsRead()`:
+
 ```ts
-  let cursor = this.sql.exec("SELECT * FROM artist;");
-  cursor.next()
-  console.log(cursor.rowsRead); // prints 1
+let cursor = this.sql.exec("SELECT * FROM artist;");
+cursor.next();
+console.log(cursor.rowsRead); // prints 1
 
-  cursor.toArray(); // consumes remaining cursor
-  console.log(cursor.rowsRead); // prints 3
+cursor.toArray(); // consumes remaining cursor
+console.log(cursor.rowsRead); // prints 3
 ```
-
diff --git a/src/content/partials/durable-objects/recommend-sqlite-do.mdx b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
index dea8504982d30c4..0d406290b88226e 100644
--- a/src/content/partials/durable-objects/recommend-sqlite-do.mdx
+++ b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
@@ -8,4 +8,4 @@ Cloudflare recommends all new Durable Object namespaces use the [SQLite storage
 Additionally, SQLite-backed Durable Objects allow you to store more types of data (such as tables), and offer Point In Time Recovery API which can restore a Durable Object's embedded SQLite database contents (both SQL data and key-value data) to any point in the past 30 days.
 
 The [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) remains for backwards compatibility, and a migration path from KV storage backend to SQLite storage backend for existing Durable Object namespaces will be available in the future.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/durable-objects/what-are-durable-objects.mdx b/src/content/partials/durable-objects/what-are-durable-objects.mdx
index 15b96c85f0f37a6..82e992b0b2297d9 100644
--- a/src/content/partials/durable-objects/what-are-durable-objects.mdx
+++ b/src/content/partials/durable-objects/what-are-durable-objects.mdx
@@ -7,4 +7,4 @@ A Durable Object is a special kind of [Cloudflare Worker](/workers/) which uniqu
 - Each Durable Object has a **globally-unique name**, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together.
 - Each Durable Object has some **durable storage** attached. Since this storage lives together with the object, it is strongly consistent yet fast to access.
 
-Therefore, Durable Objects enable **stateful** serverless applications.
\ No newline at end of file
+Therefore, Durable Objects enable **stateful** serverless applications.
diff --git a/src/content/partials/email-routing/email-routing-definition.mdx b/src/content/partials/email-routing/email-routing-definition.mdx
index b3fc4db641ed951..6359302158f6bd7 100644
--- a/src/content/partials/email-routing/email-routing-definition.mdx
+++ b/src/content/partials/email-routing/email-routing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Email Routing is designed to simplify the way you create and manage email addresses, without needing to keep an eye on additional mailboxes. With Email Routing, you can create any number of custom email addresses to use in situations where you do not want to share your primary email address, such as when you subscribe to a new service or newsletter. Emails are then routed to your preferred email inbox, without you ever having to expose your primary email address.
diff --git a/src/content/partials/email-routing/enable-create-worker.mdx b/src/content/partials/email-routing/enable-create-worker.mdx
index 240b23f507f76ab..0d37ad3ba5aaa03 100644
--- a/src/content/partials/email-routing/enable-create-worker.mdx
+++ b/src/content/partials/email-routing/enable-create-worker.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 4. (Optional) Enter a descriptive Email Worker name in **Create a worker name**.
diff --git a/src/content/partials/email-routing/send-emails-workers-intro.mdx b/src/content/partials/email-routing/send-emails-workers-intro.mdx
index 0e3bcc4027b1122..e71d08e38f239f7 100644
--- a/src/content/partials/email-routing/send-emails-workers-intro.mdx
+++ b/src/content/partials/email-routing/send-emails-workers-intro.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: lastSentence
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 You can send an email about your Worker's activity from your Worker to an email address verified on [Email Routing](/email-routing/setup/email-routing-addresses/#destination-addresses). This is useful for when you want to know about certain types of events being triggered, for example.
 
diff --git a/src/content/partials/email-routing/types-bindings.mdx b/src/content/partials/email-routing/types-bindings.mdx
index a15b5284b492f9d..5d33d135b31a988 100644
--- a/src/content/partials/email-routing/types-bindings.mdx
+++ b/src/content/partials/email-routing/types-bindings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/email-security/add-user.mdx b/src/content/partials/email-security/add-user.mdx
index b36f104c9f96b1f..274d07c1c67b2ae 100644
--- a/src/content/partials/email-security/add-user.mdx
+++ b/src/content/partials/email-security/add-user.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: childParentInfo
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 1. Log in to the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/) {props.one}.
 2. Go to **Settings** (the gear icon).
diff --git a/src/content/partials/email-security/auto-retraction.mdx b/src/content/partials/email-security/auto-retraction.mdx
index bbaf21ca8a016d6..aba4b1ad99db360 100644
--- a/src/content/partials/email-security/auto-retraction.mdx
+++ b/src/content/partials/email-security/auto-retraction.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: hardRetract
-
 ---
 
-import { GlossaryTooltip, Markdown } from "~/components"
+import { GlossaryTooltip, Markdown } from "~/components";
 
 You can set up auto-retraction to automatically move messages matching certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to specific folders within a user's mailbox.
 
@@ -18,12 +17,11 @@ To set up automatic retraction:
 4. Select **Edit**.
 
 5. For each disposition, choose which folder the message should be sent to:
-
-   * **No Action**: Do not move the message.
-   * **Junk Email**: Sends the message to the junk or spam email folder.
-   * **Trash**: Sends the message to the trash or deleted items email folder.
-   * **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
-   * **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
+   - **No Action**: Do not move the message.
+   - **Junk Email**: Sends the message to the junk or spam email folder.
+   - **Trash**: Sends the message to the trash or deleted items email folder.
+   - **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
+   - **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
 
 6. Select **Update Auto-retract Settings**.
 
@@ -33,5 +31,5 @@ Email Security (formerly Area 1) is continuously gathering new information about
 
 You can enable two options:
 
-* **Post Delivery Response**:  Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
-* **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
\ No newline at end of file
+- **Post Delivery Response**: Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
+- **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
diff --git a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
index 06080642f1da59c..5c8fd8d25359499 100644
--- a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Now that Email Security (formerly Area 1) has been authorized to access and retrieve directory information, you will need to configure the Business Email Compromise list.
diff --git a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
index d13f48b4b6e1ecd..423c5edd0ddce5b 100644
--- a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When the Business Email Compromise list is configured, Email Security (formerly Area 1) will enforce the proper match of the sender’s display name and email address. Any variation from this strict requirement will raise a detection event. The reason of detection will be `Protected Name <NAME> should not appear as <non-configured email address>`.
diff --git a/src/content/partials/email-security/contact-support.mdx b/src/content/partials/email-security/contact-support.mdx
index 5378b3ab6111c21..b4a2c7c68ef7575 100644
--- a/src/content/partials/email-security/contact-support.mdx
+++ b/src/content/partials/email-security/contact-support.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::caution[Access to Area 1]
 Beginning October 1, 2025, access and support for Email Security (formerly Area 1) will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
index 5d3c830d646535b..fb9b79de16a89ea 100644
--- a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
 Select from the following BCC addresses to process email in the correct geographic location.
 
-| Host                                        | Location                | Note                                                                                                               |
+| Host                                                                   | Location                | Note                                                                                                               |
 | ---------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `<customer_name>@journaling.mxrecord.io`                               | US                      | Best option to ensure all email traffic processing happens US data centers.                                        |
-| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.           |
-| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.      |
+| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
+| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.        |
 | `<customer_name>@journaling.mailstream-bom.mxrecord.mx`                | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                            |
-| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.                                                            |
+| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
+| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
 | `<customer_name>@journaling.mailstream-syd.area1.cloudflare.net`       | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
 | `<customer_name>@journaling.mailstream-australia.area1.cloudflare.net` | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/mx-deployment-values.mdx b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
index 7159d1c82e5849e..6c51818a2f48130 100644
--- a/src/content/partials/email-security/deployment/mx-deployment-values.mdx
+++ b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | MX Priority | Host                             |
diff --git a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
index c4e31a82c6cc983..0486462814a3d07 100644
--- a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
@@ -1,18 +1,17 @@
 ---
 {}
-
 ---
 
 When configuring the Email Security (formerly Area 1) MX records, it is important to configure hosts with the correct MX priority. This will allow mail flows to the preferred hosts and fail over as needed.
 
 Choose from the following Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
 
-| Host                                                                                                                             | Location                | Note                                                                                                                                                                                  |
-| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                                                                                                 |
-| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.                                                                              |
-| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.
-| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                                                                                               |
-| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.
-| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                                                                                          |
-| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup.                                                                    |
+| Host                                                                                                                             | Location                | Note                                                                                                               |
+| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                              |
+| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
+| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.                                           |
+| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
+| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
+| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
+| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/o365-gcc.mdx b/src/content/partials/email-security/deployment/o365-gcc.mdx
index 94afd5f4a9ae9d6..452dc5782964883 100644
--- a/src/content/partials/email-security/deployment/o365-gcc.mdx
+++ b/src/content/partials/email-security/deployment/o365-gcc.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
index 2de2cfae20b80ed..7e6a508dd4c5951 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create quarantine policies:
@@ -20,9 +19,8 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
index ffd9e7b6f9ee7a9..e797688ae2d418e 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create quarantine policies:
@@ -20,9 +19,8 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
-   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
+   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-allow-message-release.png)
 
@@ -43,9 +41,8 @@ To create quarantine policies:
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-
-    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
-    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
+    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
     ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
index 075e0dfe8e17426..8acc6ea1e36ac83 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: quarantinePolicy
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 You first need to configure the domains you are onboarding on the Email Security (formerly Area 1) dashboard. To configure your domains:
 
@@ -12,9 +11,9 @@ You first need to configure the domains you are onboarding on the Email Security
 3. Go to **Email configuration** > **Domains & Routing** > **Domains**.
 4. Make sure each domain you are onboarding has been added.
 5. For each domain you are configuring, select **...** > **Edit**, and set the following options:
-   * **Domain** - `<YOUR_DOMAIN>`.
-   * **Configured as** - `MX Records`.
-   * **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
-   * **IP Restrictions** - Leave this field empty.
-   * **Outbound TLS** - `Forward all messages over TLS`.
-   * **Quarantine Policy** - {props.one}
+   - **Domain** - `<YOUR_DOMAIN>`.
+   - **Configured as** - `MX Records`.
+   - **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
+   - **IP Restrictions** - Leave this field empty.
+   - **Outbound TLS** - `Forward all messages over TLS`.
+   - **Quarantine Policy** - {props.one}
diff --git a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
index 0f3c8996e8dba65..5ecfa3d112baa85 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
@@ -1,10 +1,9 @@
 ---
 inputParameters: ruleName;;ruleWords;;doFollowing;;img;;ruleName2;;ruleWords2;;doFollowing2;;img2
-
 ---
 
-import { Image } from 'astro:assets';
-import { GlossaryTooltip, Markdown } from "~/components"
+import { Image } from "astro:assets";
+import { GlossaryTooltip, Markdown } from "~/components";
 
 To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Email Security:
 
@@ -15,16 +14,15 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 3. Select **Add a Rule** > **Create a new rule**.
 
 4. Set the following rule conditions:
+   - **Name**: _{props.one}_.
+   - **Apply this rule if**: _The message headers_ > _includes any of these words_.
+     - **Enter text**: `X-Area1Security-Disposition` > **Save**.
+     - **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
+   - **Apply this rule if**: Select **+** to add a second condition.
+   - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+   - **Do the following** - _{props.three}_.
 
-   * **Name**: *{props.one}*.
-   * **Apply this rule if**: *The message headers* > *includes any of these words*.
-     * **Enter text**: `X-Area1Security-Disposition` > **Save**.
-     * **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
-   * **Apply this rule if**: Select **+** to add a second condition.
-   * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-   * **Do the following** - *{props.three}*.
-
- {/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
+{/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
 
 5. Select **Next**.
 
@@ -37,16 +35,15 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 9. Select **Add a Rule** > **Create a new rule**.
 
 10. Set the following rule conditions:
+    - **Name**: _{props.five}_.
+    - **Apply this rule if**: _The message headers_ > _includes any of these words_.
+      - **Enter text**: `X-Area1Security-Disposition` > **Save**.
+      - **Enter words**: _{props.six}_ > **Add** > **Save**.
+    - **Apply this rule if**: Select **+** to add a second condition.
+    - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+    - **Do the following**: _{props.seven}_.
 
-    * **Name**: *{props.five}*.
-    * **Apply this rule if**: *The message headers* > *includes any of these words*.
-      * **Enter text**: `X-Area1Security-Disposition` > **Save**.
-      * **Enter words**: *{props.six}* > **Add** > **Save**.
-    * **Apply this rule if**: Select **+** to add a second condition.
-    * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-    * **Do the following**: *{props.seven}*.
-
- {/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
+{/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
 
 11. Select **Next**.
 
@@ -54,4 +51,4 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 
 13. Review your settings and select **Finish** > **Done**.
 
-14. Select the rule *{props.five}* you have just created, and select **Enable**.
+14. Select the rule _{props.five}_ you have just created, and select **Enable**.
diff --git a/src/content/partials/email-security/deployment/setup-api-overview.mdx b/src/content/partials/email-security/deployment/setup-api-overview.mdx
index 42cb0c0bf4e1c36..749c98c3bfc1b4a 100644
--- a/src/content/partials/email-security/deployment/setup-api-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-api-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Email Security after they have already reached a user's inbox.
@@ -13,18 +12,18 @@ Then, through on integrations with your email provider, Email Security can [retr
 
 When you choose API deployment, you get the following benefits:
 
-* Easy protection for complex email architectures, without requiring any change to mailflow operations.
-* Agentless deployment for Microsoft 365 and Gmail.
-* The initial email protection measures offered by your current email provider.
+- Easy protection for complex email architectures, without requiring any change to mailflow operations.
+- Agentless deployment for Microsoft 365 and Gmail.
+- The initial email protection measures offered by your current email provider.
 
 ## Limitations
 
 However, API deployment also has the following disadvantages:
 
-* Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
-* Email Security requires read and write access to mailboxes.
-* Requires API support from your email provider (does not typically support on-premise providers).
-* Your email provider may throttle API requests from Email Security.
-* Detection rates may be lower if multiple solutions exist.
-* Messages cannot be modified or quarantined.
-* Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
+- Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
+- Email Security requires read and write access to mailboxes.
+- Requires API support from your email provider (does not typically support on-premise providers).
+- Your email provider may throttle API requests from Email Security.
+- Detection rates may be lower if multiple solutions exist.
+- Messages cannot be modified or quarantined.
+- Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
diff --git a/src/content/partials/email-security/deployment/setup-inline-overview.mdx b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
index a7473c6318abaea..70fac3460c076fb 100644
--- a/src/content/partials/email-security/deployment/setup-inline-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 With an **Inline deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), Email Security evaluates email messages before they reach a user's inbox.
 
@@ -15,11 +14,11 @@ More technically, Email Security becomes a hop in the <GlossaryTooltip term="SMT
 
 When you choose an inline deployment, you get the following benefits:
 
-* Messages are processed and physically blocked before delivery to a user's mailbox.
-* Your deployment is simpler, because any complex processing can happen downstream and without modification.
-* Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
-* Email Security can offer high availability and adaptive message pooling.
-* You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
+- Messages are processed and physically blocked before delivery to a user's mailbox.
+- Your deployment is simpler, because any complex processing can happen downstream and without modification.
+- Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
+- Email Security can offer high availability and adaptive message pooling.
+- You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
 
 ## Limitations
 
diff --git a/src/content/partials/email-security/deployment/setup-overview.mdx b/src/content/partials/email-security/deployment/setup-overview.mdx
index d8963b1ca171ef2..272608e20f764f3 100644
--- a/src/content/partials/email-security/deployment/setup-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you configure Email Security (formerly Area 1) Email Security to protect your organization, you can choose between two main setup architectures: Inline and API.
diff --git a/src/content/partials/email-security/email-security-description.mdx b/src/content/partials/email-security/email-security-description.mdx
index f65277d146ce070..a613aab3d39121a 100644
--- a/src/content/partials/email-security/email-security-description.mdx
+++ b/src/content/partials/email-security/email-security-description.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 <GlossaryTooltip term="phishing">Phishing</GlossaryTooltip> is the root cause of upwards of 90% of breaches that lead to financial loss and brand damage. Email Security (formerly Area 1) is a cloud-native service that stops phishing attacks across all threat vectors either at the [edge](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/) or in the cloud.
 
diff --git a/src/content/partials/email-security/outbound-email.mdx b/src/content/partials/email-security/outbound-email.mdx
index 1ed881d40a0dd1b..b7cc2413e883e96 100644
--- a/src/content/partials/email-security/outbound-email.mdx
+++ b/src/content/partials/email-security/outbound-email.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/email-security/rename-area1-to-ces.mdx b/src/content/partials/email-security/rename-area1-to-ces.mdx
index 4e5b20b1df6b4ea..ab1890e42fc4e97 100644
--- a/src/content/partials/email-security/rename-area1-to-ces.mdx
+++ b/src/content/partials/email-security/rename-area1-to-ces.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Area 1 has been renamed]
diff --git a/src/content/partials/email-security/search.mdx b/src/content/partials/email-security/search.mdx
index 2a9c170e7e24c0e..6e314af0ce256bd 100644
--- a/src/content/partials/email-security/search.mdx
+++ b/src/content/partials/email-security/search.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 1. **Detections only** is enabled by default. This means that the system will only search through and display emails that Email Security (formerly Area 1) has marked with a detection <GlossaryTooltip term="disposition" link="/email-security/reference/dispositions-and-attributes/">disposition</GlossaryTooltip>. If you prefer to search through and view all emails that have been processed by Email Security, whether they are marked with a detection disposition or not, disable this option.
 2. The **All detections** drop-down menu allows you to refine your search by detection disposition. This menu will be disabled if **Detections only** is not selected.
 3. By default, the search results are limited to the previous 30 days. Select **Last 30 days** to change this setting.
 4. (Optional) You can download the results from your search in CSV format. The CSV file is capped at 1,000 rows.
 5. The system returns a list of emails that fit your search criteria, and will inform you if there are emails similar to the ones found. If Email Security finds emails similar to the ones returned by your query, select **Show** to display them. Otherwise, select **View** on the email you are interested in. This will show you more information about that particular email, such as:
-   * Disposition (if any)
-   * Email status (for example `Quarantined`)
-   * Sender details (for example, IP address)
+   - Disposition (if any)
+   - Email status (for example `Quarantined`)
+   - Sender details (for example, IP address)
diff --git a/src/content/partials/email-security/service-addresses.mdx b/src/content/partials/email-security/service-addresses.mdx
index 6e22907a82f13d1..5440ee7231acb79 100644
--- a/src/content/partials/email-security/service-addresses.mdx
+++ b/src/content/partials/email-security/service-addresses.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/email-security/sso-enforcement.mdx b/src/content/partials/email-security/sso-enforcement.mdx
index bf094a37f8a0fc8..8ff51749311a532 100644
--- a/src/content/partials/email-security/sso-enforcement.mdx
+++ b/src/content/partials/email-security/sso-enforcement.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
-* **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
-* **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
-* **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
+- **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
+- **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
+- **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
diff --git a/src/content/partials/fundamentals/account-audit-logs-definition.mdx b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
index f8c6c30b76e700a..524d5179caa2fed 100644
--- a/src/content/partials/fundamentals/account-audit-logs-definition.mdx
+++ b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Audit logs summarize the history of changes made within your Cloudflare account. Audit logs include account level actions like login, as well as zone configuration changes.
@@ -9,8 +8,6 @@ Audit Logs are available on all plan types and are captured for both individual
 
 :::note
 
-
 Most beta features will not appear in audit logs until they are out of beta.
 
-
 :::
diff --git a/src/content/partials/fundamentals/account-manage-active-sessions.mdx b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
index 4be15fc6addf57f..68aba8bba607b09 100644
--- a/src/content/partials/fundamentals/account-manage-active-sessions.mdx
+++ b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 In the Cloudflare dashboard, you can view a list of active sessions associated with your email address.
@@ -11,10 +10,8 @@ If you notice any suspicious activity, you can also revoke any active sessions.
 
 :::note
 
-
 By default, the session timeout for the Cloudflare dashboard is 72 hours without any activity.
 
 Some customers can also enforce single-sign on (SSO) by [adding a Dashboard SSO application](/fundamentals/manage-members/dashboard-sso/).
 
-
 :::
diff --git a/src/content/partials/fundamentals/account-member-manage-limitation.mdx b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
index 9d7535b542de061..67c9f962a22856f 100644
--- a/src/content/partials/fundamentals/account-member-manage-limitation.mdx
+++ b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/).
diff --git a/src/content/partials/fundamentals/api-change-api-key.mdx b/src/content/partials/fundamentals/api-change-api-key.mdx
index 215b04ead3be1e3..06ec545d2f3cd2a 100644
--- a/src/content/partials/fundamentals/api-change-api-key.mdx
+++ b/src/content/partials/fundamentals/api-change-api-key.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ If your API key might be compromised, change your API key:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **API Tokens**.
 3. In the **API Keys** section, find your key.
diff --git a/src/content/partials/fundamentals/api-combine-filters.mdx b/src/content/partials/fundamentals/api-combine-filters.mdx
index 6e4a1b16a8df9cf..01c8e615b939694 100644
--- a/src/content/partials/fundamentals/api-combine-filters.mdx
+++ b/src/content/partials/fundamentals/api-combine-filters.mdx
@@ -1,18 +1,15 @@
 ---
 {}
-
 ---
 
 Combine filters using `OR` and `AND` boolean logic:
 
-* `AND` takes precedence over `OR` in all expressions.
-* The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
-* The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
+- `AND` takes precedence over `OR` in all expressions.
+- The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
+- The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
 
   :::note
 
-
   Note that the semicolon is a reserved character in URLs ([RFC 1738](https://www.rfc-editor.org/rfc/rfc1738)) and should be percent-encoded as `%3B`.
 
-
   :::
diff --git a/src/content/partials/fundamentals/api-filter-operators.mdx b/src/content/partials/fundamentals/api-filter-operators.mdx
index fd3a372b4041816..57f6d12acfe8282 100644
--- a/src/content/partials/fundamentals/api-filter-operators.mdx
+++ b/src/content/partials/fundamentals/api-filter-operators.mdx
@@ -1,18 +1,14 @@
 ---
 inputParameters: param1;;param2;;param3;;param4
-
 ---
 
+import { Markdown } from "~/components";
 
-
-import { Markdown } from "~/components"
-
-| Operator | Name                     | Example           | Description                                                          | URL Encoded |
-| -------- | ------------------------ | ----------------- | -------------------------------------------------------------------- | ----------- |
-| `==`     | Equals                   | <code>{props.one}=={props.two}</code>          | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.                           | `%3D%3D`    |
-| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code>         | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>.                    | `!%3D`      |
-| `>`      | Greater than             | `dimension>1000`  | Return results where a dimension is greater than `1000`.             | `%3E`       |
-| `<`      | Less than                | `dimension<1000`  | Return results where a dimension is less than `1000`.                | `%3C`       |
-| `>=`     | Greater than or equal to | `dimension>=1000` | Return results where a dimension is greater than or equal to `1000`. | `%3E%3D`    |
-| `<=`     | Less than or equal to    | `dimension<=1000` | Return results where a dimension is less than or equal to `1000`.    | `%3C%3D`    |
-
+| Operator | Name                     | Example                                  | Description                                                                                  | URL Encoded |
+| -------- | ------------------------ | ---------------------------------------- | -------------------------------------------------------------------------------------------- | ----------- |
+| `==`     | Equals                   | <code>{props.one}=={props.two}</code>    | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.           | `%3D%3D`    |
+| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code> | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>. | `!%3D`      |
+| `>`      | Greater than             | `dimension>1000`                         | Return results where a dimension is greater than `1000`.                                     | `%3E`       |
+| `<`      | Less than                | `dimension<1000`                         | Return results where a dimension is less than `1000`.                                        | `%3C`       |
+| `>=`     | Greater than or equal to | `dimension>=1000`                        | Return results where a dimension is greater than or equal to `1000`.                         | `%3E%3D`    |
+| `<=`     | Less than or equal to    | `dimension<=1000`                        | Return results where a dimension is less than or equal to `1000`.                            | `%3C%3D`    |
diff --git a/src/content/partials/fundamentals/api-rate-limits.mdx b/src/content/partials/fundamentals/api-rate-limits.mdx
index 09202c8b7845f04..37822f640908916 100644
--- a/src/content/partials/fundamentals/api-rate-limits.mdx
+++ b/src/content/partials/fundamentals/api-rate-limits.mdx
@@ -6,16 +6,16 @@ params:
 import { AnchorHeading } from "~/components";
 
 {props.showHeading && (
-	<AnchorHeading title="API token limits" depth={2} />
+<AnchorHeading title="API token limits" depth={2} />
 )}
 
-| Type                    | Limit                               |
-| ----------------------- | ----------------------------------- |
-| Client API per user/account token     | 1200/5 minutes        |
-| Client API per IP       | 200/second                          |
-| GraphQL                 | Varies by query cost. Max 320/5 min |
-| User API token quota    | 50                                  |
-| Account API token quota | 500                                 |
+| Type                              | Limit                               |
+| --------------------------------- | ----------------------------------- |
+| Client API per user/account token | 1200/5 minutes                      |
+| Client API per IP                 | 200/second                          |
+| GraphQL                           | Varies by query cost. Max 320/5 min |
+| User API token quota              | 50                                  |
+| Account API token quota           | 500                                 |
 
 :::note
 The global rate limit for the Cloudflare API is 1,200 requests per five minute period per user, and applies cumulatively regardless of whether the request is made via the dashboard, API key, or API token.
diff --git a/src/content/partials/fundamentals/api-using-api.mdx b/src/content/partials/fundamentals/api-using-api.mdx
index b1ca2470c79d58c..e5ae32ba9e53c09 100644
--- a/src/content/partials/fundamentals/api-using-api.mdx
+++ b/src/content/partials/fundamentals/api-using-api.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 Using the Cloudflare API requires authentication so that Cloudflare knows who is making requests and what permissions you have. [Create an API token](/fundamentals/api/get-started/create-token/) to grant access to the API to perform actions.
 
 :::note
 
-
 You can also authenticate with [API keys](/fundamentals/api/get-started/keys/), but these keys have [several limitations](/fundamentals/api/get-started/keys/#limitations) that make them less secure than API tokens. Whenever possible, use API tokens to interact with the Cloudflare API.
 
-
 :::
diff --git a/src/content/partials/fundamentals/audit-log-api.mdx b/src/content/partials/fundamentals/audit-log-api.mdx
index ce209127d72ff3f..6d53ba9530aa6e7 100644
--- a/src/content/partials/fundamentals/audit-log-api.mdx
+++ b/src/content/partials/fundamentals/audit-log-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To get audit logs from the Cloudflare API, send a [GET request](/api/resources/audit_logs/methods/list/).
diff --git a/src/content/partials/fundamentals/create-account-best-practices.mdx b/src/content/partials/fundamentals/create-account-best-practices.mdx
index 8a878be2c868221..efc376dfbf7bcdb 100644
--- a/src/content/partials/fundamentals/create-account-best-practices.mdx
+++ b/src/content/partials/fundamentals/create-account-best-practices.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you are creating an account for your team or a business, we recommend choosing an email alias or distribution list for your **Email**, such as `cloudflare@example.com`.
diff --git a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
index 5c9104ac3a59f7b..24617a79253e1c1 100644
--- a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
+++ b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
@@ -1,36 +1,35 @@
 ---
 {}
-
 ---
 
 Cloudflare’s recommended CIPA rule blocks the following content subcategories:
 
-* Adult Themes
-* Alcohol
-* Anonymizer
-* Brand Embedding
-* Child Abuse
-* Command and Control & Botnet
-* Cryptomining
-* DGA Domains
-* DNS Tunneling
-* Drugs
-* Gambling
-* Hacking
-* Malware
-* Militancy, Hate & Extremism
-* Nudity
-* P2P
-* Phishing
-* Pornography
-* Private IP Address
-* Profanity
-* Questionable Activities
-* School Cheating
-* Spam
-* Spyware
-* Tobacco
-* Violence
-* Weapons
+- Adult Themes
+- Alcohol
+- Anonymizer
+- Brand Embedding
+- Child Abuse
+- Command and Control & Botnet
+- Cryptomining
+- DGA Domains
+- DNS Tunneling
+- Drugs
+- Gambling
+- Hacking
+- Malware
+- Militancy, Hate & Extremism
+- Nudity
+- P2P
+- Phishing
+- Pornography
+- Private IP Address
+- Profanity
+- Questionable Activities
+- School Cheating
+- Spam
+- Spyware
+- Tobacco
+- Violence
+- Weapons
 
 Review the [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for more information.
diff --git a/src/content/partials/fundamentals/cybersafe-configuration.mdx b/src/content/partials/fundamentals/cybersafe-configuration.mdx
index e8654c6c41b1e83..97c5c85cf1bc3fe 100644
--- a/src/content/partials/fundamentals/cybersafe-configuration.mdx
+++ b/src/content/partials/fundamentals/cybersafe-configuration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To facilitate compliance with CIPA requirements, administrators can [enable a single filtering policy option](/cloudflare-one/traffic-policies/dns-policies/common-policies/#turn-on-cipa-filter). This includes applying the required filter categories to block access to unwanted or harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-description.mdx b/src/content/partials/fundamentals/cybersafe-description.mdx
index 431d708d46e714b..a3f8e1c475bbb46 100644
--- a/src/content/partials/fundamentals/cybersafe-description.mdx
+++ b/src/content/partials/fundamentals/cybersafe-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/sites/default/files/childrens_internet_protection_act_cipa.pdf) is a federal law enacted by the United States Congress to address concerns about children's access to inappropriate or harmful content over the Internet. CIPA requires K-12 schools and libraries that receive certain federal funding to implement Internet safety measures to protect minors from harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-requirements.mdx b/src/content/partials/fundamentals/cybersafe-requirements.mdx
index 833e37f87f33941..e6be7dae9a66a9c 100644
--- a/src/content/partials/fundamentals/cybersafe-requirements.mdx
+++ b/src/content/partials/fundamentals/cybersafe-requirements.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 CIPA mandates that K-12 schools and libraries adopt Internet safety policies that include measures to block or filter access to specific categories of content. These categories encompass a wide range of topics that could be harmful or inappropriate for minors. Compliance with these requirements helps ensure that students' online experiences are safer and more secure.
diff --git a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
index 2e2f41f8016c234..9973f9748eda869 100644
--- a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
+++ b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 This program is only available to eligible school districts. To be eligible, Project Cybersafe School participants must be:
 
-* K-12 public school districts located in the United States.
-* Up to 2,500 students in the district.
+- K-12 public school districts located in the United States.
+- Up to 2,500 students in the district.
diff --git a/src/content/partials/fundamentals/idp-group-deprecation.mdx b/src/content/partials/fundamentals/idp-group-deprecation.mdx
index 05821b931796237..baaae6c04591975 100644
--- a/src/content/partials/fundamentals/idp-group-deprecation.mdx
+++ b/src/content/partials/fundamentals/idp-group-deprecation.mdx
@@ -1,12 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 **Important Update:** Cloudflare now supports native User Groups for enhanced access control. This new feature replaces the previous method of directly assigning Cloudflare roles based on IdP group mappings (identified by the pattern `CF-<accountID> - <Role Name>`), which is deprecated as of June 2nd, 2025. SCIM Virtual Groups will reach end-of-life on December 2, 2025. Update your SCIM configurations using the instructions below to utilize User Groups for seamless provisioning.
 :::
-
-
-
-
diff --git a/src/content/partials/fundamentals/lists-import-notes.mdx b/src/content/partials/fundamentals/lists-import-notes.mdx
index 7b084592eb99561..1325dd37dc9b03c 100644
--- a/src/content/partials/fundamentals/lists-import-notes.mdx
+++ b/src/content/partials/fundamentals/lists-import-notes.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 Cloudflare will apply the following rules when you add items to an existing list (either manually or via CSV file):
 
-* Do not remove any existing list items before updating/adding items.
-* Update items that were already in the list.
-* Add items that were not present in the list.
+- Do not remove any existing list items before updating/adding items.
+- Update items that were already in the list.
+- Add items that were not present in the list.
diff --git a/src/content/partials/fundamentals/new-token-warning.mdx b/src/content/partials/fundamentals/new-token-warning.mdx
index ebba0665c1f6103..794191bf0e51bba 100644
--- a/src/content/partials/fundamentals/new-token-warning.mdx
+++ b/src/content/partials/fundamentals/new-token-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Warning]
 
-
 The token secret is **only shown once**. Do not store the secret in plaintext where others can access it. Anyone with this token can perform the authorized actions against the resources that the token has access to.
 
-
 :::
diff --git a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
index 8339d260cd8f0fd..707af55fc2d4d48 100644
--- a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
+++ b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If **Pseudo IPv4** is set to `Overwrite Headers` - Cloudflare overwrites the existing `Cf-Connecting-IP` and `X-Forwarded-For` headers with a pseudo IPv4 address while preserving the real IPv6 address in `CF-Connecting-IPv6` header.
diff --git a/src/content/partials/fundamentals/revoke-active-sessions.mdx b/src/content/partials/fundamentals/revoke-active-sessions.mdx
index 07d956a61afdf20..fc8a9e0c4c296c9 100644
--- a/src/content/partials/fundamentals/revoke-active-sessions.mdx
+++ b/src/content/partials/fundamentals/revoke-active-sessions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,7 +10,7 @@ To revoke a session:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 3. On a specific section, click **Revoke**.
diff --git a/src/content/partials/fundamentals/ubb-recommendation.mdx b/src/content/partials/fundamentals/ubb-recommendation.mdx
index ec055f77df645ca..d05b58438eb70b2 100644
--- a/src/content/partials/fundamentals/ubb-recommendation.mdx
+++ b/src/content/partials/fundamentals/ubb-recommendation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,16 +10,15 @@ To set up those notifications:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-      <DashButton url="/?to=/:account/notifications" />
+   <DashButton url="/?to=/:account/notifications" />
 
 2. On **Alert Type** of **Usage Based Billing**, click **Select**.
 
 3. Fill out the following information:
-
-   * **Name**
-   * **Product**
-   * **Notification limit** (exact metric will vary based on product)
-   * **Notification email**
+   - **Name**
+   - **Product**
+   - **Notification limit** (exact metric will vary based on product)
+   - **Notification email**
 
    :::note
    Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/).
diff --git a/src/content/partials/fundamentals/user-permissions-table.mdx b/src/content/partials/fundamentals/user-permissions-table.mdx
index 5bcacf794820b2f..0a4067fc83f026d 100644
--- a/src/content/partials/fundamentals/user-permissions-table.mdx
+++ b/src/content/partials/fundamentals/user-permissions-table.mdx
@@ -1,15 +1,14 @@
 ---
 inputParameters: editWord
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-| Name              | Description                                                                                        |
-| ----------------- | -------------------------------------------------------------------------------------------------- |
-| API Tokens Read   | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).               |
-| API Tokens {props.one}     | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).              |
-| Memberships Read  | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
-| Memberships {props.one}    | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
-| User Details Read | Grants read access to user details.                                                                |
-| User Details {props.one}   | Grants write access to user details.                                                               |
+| Name                     | Description                                                                                  |
+| ------------------------ | -------------------------------------------------------------------------------------------- |
+| API Tokens Read          | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).         |
+| API Tokens {props.one}   | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).        |
+| Memberships Read         | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
+| Memberships {props.one}  | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
+| User Details Read        | Grants read access to user details.                                                          |
+| User Details {props.one} | Grants write access to user details.                                                         |
diff --git a/src/content/partials/fundamentals/user-profiles.mdx b/src/content/partials/fundamentals/user-profiles.mdx
index 95d7406967bb114..5f074fa4484f104 100644
--- a/src/content/partials/fundamentals/user-profiles.mdx
+++ b/src/content/partials/fundamentals/user-profiles.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/user-profiles/customize-account/#notifications) and [Language preferences](/fundamentals/user-profiles/customize-account/#language).
 
-To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
\ No newline at end of file
+To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
diff --git a/src/content/partials/fundamentals/view-audit-log.mdx b/src/content/partials/fundamentals/view-audit-log.mdx
index 34f479029436066..ea0694e788fe9fc 100644
--- a/src/content/partials/fundamentals/view-audit-log.mdx
+++ b/src/content/partials/fundamentals/view-audit-log.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +14,6 @@ You can search these audit logs by user email or domain and filter by date range
 
 :::note
 
-
 Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Logpush](/logs/logpush/) to make sure Audit Logs are always available and stored externally.
 
-
 :::
diff --git a/src/content/partials/fundamentals/what-is-cloudflare.mdx b/src/content/partials/fundamentals/what-is-cloudflare.mdx
index 6db16b67782d1fc..7321651a4cf4000 100644
--- a/src/content/partials/fundamentals/what-is-cloudflare.mdx
+++ b/src/content/partials/fundamentals/what-is-cloudflare.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Stream } from "~/components"
+import { Stream } from "~/components";
 
 Cloudflare is one of the world's largest [connectivity cloud networks](https://blog.cloudflare.com/welcome-to-connectivity-cloud). Today, anyone with an Internet presence can have faster and more secure websites and applications thanks to Cloudflare. This includes bloggers, businesses, and even non-profits.
 
diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
index 17b0e04547941b8..7f8df8ff66b23e8 100644
--- a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
+++ b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) is occurring. No other error codes will trigger a zero-downtime failover operation.
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
index a0936f417ad77a4..94ebfc3d69ff887 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
@@ -30,9 +29,7 @@ Specifically:
 - The binding must be [a valid JavaScript variable name](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#variables). For example, `binding = "hyperdrive"` or `binding = "productionDB"` would both be valid names for the binding.
 - Your binding is available in your Worker at `env.<BINDING_NAME>`.
 
-
-If you wish to use a local database during development, you can add a `localConnectionString` to your  Hyperdrive configuration with the connection string of your database:
-
+If you wish to use a local database during development, you can add a `localConnectionString` to your Hyperdrive configuration with the connection string of your database:
 
 <WranglerConfig>
 
@@ -54,4 +51,4 @@ If you wish to use a local database during development, you can add a `localConn
 
 Learn more about setting up [Hyperdrive for local development](/hyperdrive/configuration/local-development/).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
index 2bccc59303de979..55f58eb3fdaebda 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
@@ -2,7 +2,14 @@
 {}
 ---
 
-import { DashButton, WranglerConfig, Render, Tabs, TabItem, Steps } from "~/components";
+import {
+	DashButton,
+	WranglerConfig,
+	Render,
+	Tabs,
+	TabItem,
+	Steps,
+} from "~/components";
 
 To configure Hyperdrive, you will need:
 
diff --git a/src/content/partials/hyperdrive/pooling-mode.mdx b/src/content/partials/hyperdrive/pooling-mode.mdx
index a06f46f412dcfe7..ca988038c32fd15 100644
--- a/src/content/partials/hyperdrive/pooling-mode.mdx
+++ b/src/content/partials/hyperdrive/pooling-mode.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool.
diff --git a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
index b1275de22aeb7e2..f4895b5eecb79bb 100644
--- a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
+++ b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
@@ -37,7 +37,7 @@ export default {
 			// If you are not using array types in your Postgres schema, disable `fetch_types` to avoid an additional round-trip (unnecessary latency)
 			fetch_types: false,
 
-			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.  
+			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.
 			prepare: true,
 		});
 
diff --git a/src/content/partials/learning-paths/cache-basic-diagram.mdx b/src/content/partials/learning-paths/cache-basic-diagram.mdx
index 6555ff5ad8fcf75..c44a888cabcaa1e 100644
--- a/src/content/partials/learning-paths/cache-basic-diagram.mdx
+++ b/src/content/partials/learning-paths/cache-basic-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/learning-paths/cache-optimization.mdx b/src/content/partials/learning-paths/cache-optimization.mdx
index 890676e0f865216..48c74235eb911f9 100644
--- a/src/content/partials/learning-paths/cache-optimization.mdx
+++ b/src/content/partials/learning-paths/cache-optimization.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 A few ways to optimize Cloudflare caching include:
 
-* Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
-* Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
-* Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
+- Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
+- Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
+- Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
diff --git a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
index f15999e994d4aec..6dba0749cadcf88 100644
--- a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Related content**
@@ -10,4 +9,4 @@ For additional resources on the China Network, refer to the following resources:
     - [Cloudflare China Network](/china-network/)
     - [CDN Global Acceleration (formerly China Express)](/china-network/concepts/global-acceleration/)
     - [Internet Content Provider (ICP)](/china-network/concepts/icp/)
-    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
\ No newline at end of file
+    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
diff --git a/src/content/partials/learning-paths/china-network-overview-navigation.mdx b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
index 5e5f0c651602e6f..6e6fee7c6c5dfbd 100644
--- a/src/content/partials/learning-paths/china-network-overview-navigation.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
@@ -1,20 +1,19 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: How to speed up your web traffic inside mainland China"
-          description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
-          href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
-          description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
-          href="/learning-paths/china-network-overview/series/china-express-overview-2/"
-        />              
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: How to speed up your web traffic inside mainland China"
+		description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
+		href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
+		description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
+		href="/learning-paths/china-network-overview/series/china-express-overview-2/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
index 80b90de36b0e2f6..b825a923b79a986 100644
--- a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
+++ b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address, by creating an outbound-only connections to Cloudflare’s global network.
 
-* **Security**: Very secure.
-* **Availability**: All customers.
-* **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
+- **Security**: Very secure.
+- **Availability**: All customers.
+- **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
diff --git a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
index 7b1ca7fcfce93d8..95cf4f8cf529595 100644
--- a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
+++ b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A distributed denial-of-service (DDoS) attack is where a large number of computers or devices, usually controlled by a single attacker, attempt to access a website or online service all at once. This flood of traffic can overwhelm the website's origin servers, causing the site to slow down or even crash.
@@ -18,4 +17,4 @@ sequenceDiagram;
     Origin Server-->>User: Unable to respond to user requests
 ```
 
-<br/>
+<br />
diff --git a/src/content/partials/learning-paths/email-record-origin-ip.mdx b/src/content/partials/learning-paths/email-record-origin-ip.mdx
index 94b82b3791865f7..5b5f2c45e1b9e18 100644
--- a/src/content/partials/learning-paths/email-record-origin-ip.mdx
+++ b/src/content/partials/learning-paths/email-record-origin-ip.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If possible, do not host a mail service on the same server as the web resource you want to protect, since emails sent to non-existent addresses get bounced back to the attacker and reveal the mail server IP address.
diff --git a/src/content/partials/learning-paths/r2-series-navigation.mdx b/src/content/partials/learning-paths/r2-series-navigation.mdx
index fdf03a46c5a8df9..612ab4b973072ca 100644
--- a/src/content/partials/learning-paths/r2-series-navigation.mdx
+++ b/src/content/partials/learning-paths/r2-series-navigation.mdx
@@ -1,34 +1,33 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Getting started with R2"
-          description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
-          href="/learning-paths/r2-intro/series/r2-1/"
-        />          
-      <LinkCard
-          title="Watch Episode 2: Public buckets"
-          description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
-          href="/learning-paths/r2-intro/series/r2-2/"
-        />    
-      <LinkCard
-          title="Watch Episode 3: S3 API compatibility"
-          description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
-          href="/learning-paths/r2-intro/series/r2-3/"
-        />    
-      <LinkCard
-          title="Watch Episode 4: Migrating your bucket data"
-          description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
-          href="/learning-paths/r2-intro/series/r2-4/"
-        />    
-      <LinkCard
-          title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
-          description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
-          href="/learning-paths/r2-intro/series/r2-5/"
-        />                                    
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Getting started with R2"
+		description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
+		href="/learning-paths/r2-intro/series/r2-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: Public buckets"
+		description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
+		href="/learning-paths/r2-intro/series/r2-2/"
+	/>
+	<LinkCard
+		title="Watch Episode 3: S3 API compatibility"
+		description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
+		href="/learning-paths/r2-intro/series/r2-3/"
+	/>
+	<LinkCard
+		title="Watch Episode 4: Migrating your bucket data"
+		description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
+		href="/learning-paths/r2-intro/series/r2-4/"
+	/>
+	<LinkCard
+		title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
+		description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
+		href="/learning-paths/r2-intro/series/r2-5/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/sase-series-navigation.mdx b/src/content/partials/learning-paths/sase-series-navigation.mdx
index c9ac5dace4ee296..67412cf58413313 100644
--- a/src/content/partials/learning-paths/sase-series-navigation.mdx
+++ b/src/content/partials/learning-paths/sase-series-navigation.mdx
@@ -1,40 +1,38 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: The evolution of corporate networks"
-          description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
-          href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 2: Stop hosting your own VPN service"
-          description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
-          href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 3: Secure remote access to your critical infrastructure"
-          description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
-          href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 4: Connect and secure from any network to anywhere"
-          description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: The evolution of corporate networks"
+		description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
+		href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 2: Stop hosting your own VPN service"
+		description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
+		href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 3: Secure remote access to your critical infrastructure"
+		description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
+		href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 4: Connect and secure from any network to anywhere"
+		description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
   "
-          href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
-        />
-        
-      <LinkCard
-          title="Watch Episode 5: Protect your users from Internet risks"
-          description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
-          href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
-      />                           
-        
-    </CardGrid>
+		href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
+	/>
+
+	<LinkCard
+		title="Watch Episode 5: Protect your users from Internet risks"
+		description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
+		href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/warp-series-navigation.mdx b/src/content/partials/learning-paths/warp-series-navigation.mdx
index 30d3c3c2090ec52..af1eed7e2a23691 100644
--- a/src/content/partials/learning-paths/warp-series-navigation.mdx
+++ b/src/content/partials/learning-paths/warp-series-navigation.mdx
@@ -1,19 +1,18 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
-          description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
-          href="/learning-paths/warp-overview-course/series/warp-basics-1/"
-        />              
-      <LinkCard
-          title="Watch Episode 2: WARP diagnostic logs"
-          description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
-          href="/learning-paths/warp-overview-course/series/warp-basics-2/"
-        />                   
-    </CardGrid>
\ No newline at end of file
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
+		description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
+		href="/learning-paths/warp-overview-course/series/warp-basics-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: WARP diagnostic logs"
+		description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
+		href="/learning-paths/warp-overview-course/series/warp-basics-2/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/workflows-series-navigation.mdx b/src/content/partials/learning-paths/workflows-series-navigation.mdx
index 3aef6a36002ba88..f037d68638048ed 100644
--- a/src/content/partials/learning-paths/workflows-series-navigation.mdx
+++ b/src/content/partials/learning-paths/workflows-series-navigation.mdx
@@ -1,24 +1,23 @@
 ---
 {}
-
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
- <CardGrid>
-      <LinkCard
-          title="Watch Episode 1: Understand Cloudflare Workflows"
-          description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
-          href="/learning-paths/workflows-course/series/workflows-1/"
-        />          
-      <LinkCard
-          title="Watch Episode 2: Monitor and batch your website data"
-          description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
-          href="/learning-paths/workflows-course/series/workflows-2/"
-        />    
-      <LinkCard
-          title="Watch Episode 3: Use cron triggers to develop time-aware applications"
-          description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
-          href="/learning-paths/workflows-course/series/workflows-3/"
-        />                          
-    </CardGrid>
+<CardGrid>
+	<LinkCard
+		title="Watch Episode 1: Understand Cloudflare Workflows"
+		description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
+		href="/learning-paths/workflows-course/series/workflows-1/"
+	/>
+	<LinkCard
+		title="Watch Episode 2: Monitor and batch your website data"
+		description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
+		href="/learning-paths/workflows-course/series/workflows-2/"
+	/>
+	<LinkCard
+		title="Watch Episode 3: Use cron triggers to develop time-aware applications"
+		description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
+		href="/learning-paths/workflows-course/series/workflows-3/"
+	/>
+</CardGrid>
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
index 634c2666bff6d5b..1432141f867394c 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Restrict access for users included in an <GlossaryTooltip term="identity provider">identity provider (IdP)</GlossaryTooltip> user group for risky users. This policy ensures your security team can restrict traffic for users of whom malicious or suspicious activity was detected.
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
index 060cde6c1160533..39d1803880c83b2 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Block [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories), such as **Command and Control & Botnet** and **Malware**, based on Cloudflare's threat intelligence.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
index b9a22f0fb157e40..0a419a55b8b121b 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The Cloudflare One Client (known as the Cloudflare One Agent in mobile app stores) encrypts designated traffic from a user's device to Cloudflare's global network. In this learning path, we will first define all of your parameters and deployment rules, and then we will install and connect the client. If you prefer to start the client download now, refer to [Download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/).
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
index 087954988839621..01f20205751345a 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-* Define which users can connect devices to your Zero Trust instance.
-* Configure global and device-specific settings for the Cloudflare One Client.
-* Route user traffic through Cloudflare Gateway.
-* Route domains to a private DNS server, if required.
+- Define which users can connect devices to your Zero Trust instance.
+- Configure global and device-specific settings for the Cloudflare One Client.
+- Route user traffic through Cloudflare Gateway.
+- Route domains to a private DNS server, if required.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
index 21e92853d18e27b..f358209dc42676a 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip, Render} from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 An <GlossaryTooltip term="identity provider" link="https://www.cloudflare.com/learning/access-management/what-is-an-identity-provider/">identity provider (IdP)</GlossaryTooltip> stores and manages users' digital identities. You can integrate your existing identity provider with Cloudflare Zero Trust in order to manage user access to your private network. This requires configuration both in Cloudflare and with the identity provider itself.
 
diff --git a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
index 6af7493ea8d2e78..5317428531592d0 100644
--- a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Manually deploy the Cloudflare One Client on a test device.
-* Create an automated script to use with your organization's managed deployment tool.
-* View user traffic in Zero Trust.
+- Manually deploy the Cloudflare One Client on a test device.
+- Create an automated script to use with your organization's managed deployment tool.
+- View user traffic in Zero Trust.
diff --git a/src/content/partials/learning-paths/zero-trust/create-list.mdx b/src/content/partials/learning-paths/zero-trust/create-list.mdx
index f5cc8a1e77768f5..db39846de4a243f 100644
--- a/src/content/partials/learning-paths/zero-trust/create-list.mdx
+++ b/src/content/partials/learning-paths/zero-trust/create-list.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Gateway supports creating [lists](/cloudflare-one/reusable-components/lists/) of IPs, hostnames, or other entries to reference in your policies.
 
diff --git a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
index 5f2f956a234b5a0..d1c2be740c04bb1 100644
--- a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Device enrollment permissions determine which users can connect new devices to your organization's Cloudflare Zero Trust instance. Once the user registers their device, the Cloudflare One Client will store their identity token and use it to authenticate to services in your private network.
 
diff --git a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
index d7a5d2a680983d6..af96e5d35431904 100644
--- a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
-| Disposition | Description                                                                                                                                                                                  | Recommendation                                                             |   |
-|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---|
-| MALICIOUS   |                                 Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                |                                    Block                                   |   |
-| SUSPICIOUS  |                                             Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                             |         Research these messages internally to evaluate legitimacy.         |   |
-| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |   |
-| SPAM        |                                                                 Traffic associated with non-malicious, commercial campaigns.                                                                 |                  Route to existing Spam quarantine folder.                 |   |
-| BULK        |       Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.       |                               Monitor or tag                               |   |
\ No newline at end of file
+| Disposition | Description                                                                                                                                                                                                                                                                                                                                                                                                                             | Recommendation                                                             |     |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --- |
+| MALICIOUS   | Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                                                                                                                                                                                                                                                                                           | Block                                                                      |     |
+| SUSPICIOUS  | Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                                                                                                                                                                                                                                                                                                                    | Research these messages internally to evaluate legitimacy.                 |     |
+| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |     |
+| SPAM        | Traffic associated with non-malicious, commercial campaigns.                                                                                                                                                                                                                                                                                                                                                                            | Route to existing Spam quarantine folder.                                  |     |
+| BULK        | Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.                                                                                                                                                                                                              | Monitor or tag                                                             |     |
diff --git a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
index e6800e57f7aafd3..8a8dcfab6f7c924 100644
--- a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
+++ b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 With Cloudflare Gateway, you can log and filter DNS, network, and HTTP traffic from devices running the Cloudflare One Client. This includes traffic to the public Internet and traffic directed to your private network. DNS filtering is enabled by default since the Cloudflare One Client sends DNS queries to Cloudflare's public DNS resolver, [1.1.1.1](/1.1.1.1/). To enable network and HTTP filtering, you will need to allow Cloudflare Gateway to proxy that traffic.
diff --git a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
index fd8de62a9baadd6..4c1e0192bd1e400 100644
--- a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Set up a Cloudflare account.
-* Create a Zero Trust organization to manage your devices and policies.
-* Configure an identity provider (IdP) for user authentication.
+- Set up a Cloudflare account.
+- Create a Zero Trust organization to manage your devices and policies.
+- Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/partials/learning-paths/zero-trust/install-agent.mdx b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
index 50221f53efc84d9..c0b8798b2485485 100644
--- a/src/content/partials/learning-paths/zero-trust/install-agent.mdx
+++ b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
@@ -1,32 +1,32 @@
 ---
 inputParameters: WARPsuccess
-
 ---
 
-import { Details, Markdown, Render } from "~/components"
+import { Details, Markdown, Render } from "~/components";
 
 Most admins test by manually downloading the Cloudflare One Client and enrolling in your organization's Cloudflare Zero Trust instance.
 
 ## Install the Cloudflare One Client
 
-1. First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
-2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
-  	<Render file="warp/client-orchestration-ips" product="cloudflare-one" />
+1.  First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
+2.  If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
+
+    <Render file="warp/client-orchestration-ips" product="cloudflare-one" />
 
-	For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
+    For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 
-3. Manually install the Cloudflare One Client on the device.
+3.  Manually install the Cloudflare One Client on the device.
 
-		<Details header="Window, macOS, and Linux">
+        <Details header="Window, macOS, and Linux">
 
-		<Render file="warp/enroll-desktop" product="cloudflare-one" />
+        <Render file="warp/enroll-desktop" product="cloudflare-one" />
 
-		</Details>
+        </Details>
 
-		<Details header="iOS, Android, and ChromeOS">
+        <Details header="iOS, Android, and ChromeOS">
 
-		<Render file="warp/enroll-ios-android" product="cloudflare-one" />
+        <Render file="warp/enroll-ios-android" product="cloudflare-one" />
 
-		</Details>
+        </Details>
 
 The Cloudflare One Client should show as **Connected**. {props.one}
diff --git a/src/content/partials/learning-paths/zero-trust/mdm.mdx b/src/content/partials/learning-paths/zero-trust/mdm.mdx
index d928a456aa181ac..042067aab0fd199 100644
--- a/src/content/partials/learning-paths/zero-trust/mdm.mdx
+++ b/src/content/partials/learning-paths/zero-trust/mdm.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="warp/mdm-intro" product="cloudflare-one" />
 
diff --git a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
index eb80c75bd1fbfa8..d3ea3aaab5d3ff0 100644
--- a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
+++ b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
-import { Render} from "~/components"
+import { Render } from "~/components";
 
 Split tunnel settings determine which traffic the Cloudflare One Client does and does not proxy.
 
 The Cloudflare One Client offers two different split tunnel modes:
 
-* If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
-* If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
+- If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
+- If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
 
 ## Update Split Tunnels mode
 
diff --git a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
index 5e3a0df5f6c077b..21f27878f44c392 100644
--- a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
+++ b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
@@ -1,10 +1,13 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 To validate that Cloudflare is receiving traffic from a user device:
 
-<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
+<Render
+	file="gateway/verify-connectivity"
+	product="cloudflare-one"
+	params={{ one: "DNS", two: "queries" }}
+/>
diff --git a/src/content/partials/load-balancing/components-knowledge-callout.mdx b/src/content/partials/load-balancing/components-knowledge-callout.mdx
index 75cdfecec22253a..b8493c88bd03af8 100644
--- a/src/content/partials/load-balancing/components-knowledge-callout.mdx
+++ b/src/content/partials/load-balancing/components-knowledge-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This guide assumes you are familiar with the Cloudflare [Load Balancing components](/load-balancing/understand-basics/load-balancing-components/).
diff --git a/src/content/partials/load-balancing/custom-rules-definition.mdx b/src/content/partials/load-balancing/custom-rules-definition.mdx
index 87c37f08ebba3d4..49889fc8bc61ee2 100644
--- a/src/content/partials/load-balancing/custom-rules-definition.mdx
+++ b/src/content/partials/load-balancing/custom-rules-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom load balancing rules let you customize the behavior of your load balancer based on the characteristics of a request.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
index 2a826379296653d..b05bdc170e119f5 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your load balancer is attached to a hostname used for an [`MX` or `SRV` record](/load-balancing/additional-options/additional-dns-records/) — and not an `A`, `AAAA`, or `CNAME` record — its proxy mode should be **DNS-only**.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
index 85d6c2a3775c9cf..07047a05eddeed8 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 DNS-only load balancers route traffic by returning specific IP addresses in response to a client's DNS query.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
index bc03d3b58635b6d..ebcffa45dd9ce22 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 In comparison to proxied, layer 7 load balancing, DNS-only load balancing:
 
-* Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
-* Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
-* Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
-* Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
-* Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
-* Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
-* Does not support [Private Network Load Balancing](/load-balancing/private-network/).
+- Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
+- Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
+- Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
+- Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
+- Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
+- Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
+- Does not support [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
index 5a380e226cc7c4b..b5888a2b8e97651 100644
--- a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
+++ b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Since load balancing targets are not limited to origin web servers, the term `endpoints` has been introduced. Refer to [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-other-terms/) for its use in the context of Cloudflare offerings, and to [load balancing concepts](/load-balancing/understand-basics/load-balancing-components/) or [Reference Architecture](/reference-architecture/architectures/load-balancing/) for use case examples.
diff --git a/src/content/partials/load-balancing/fallback-pools.mdx b/src/content/partials/load-balancing/fallback-pools.mdx
index 49f0595e95dc999..bac40469f252c71 100644
--- a/src/content/partials/load-balancing/fallback-pools.mdx
+++ b/src/content/partials/load-balancing/fallback-pools.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This pool is meant to be the pool of last resort, meaning that its health is not taken into account when directing traffic.
diff --git a/src/content/partials/load-balancing/health-check-diagram.mdx b/src/content/partials/load-balancing/health-check-diagram.mdx
index 568033512858810..6b2bfb5560e0f49 100644
--- a/src/content/partials/load-balancing/health-check-diagram.mdx
+++ b/src/content/partials/load-balancing/health-check-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/health-check-regions.mdx b/src/content/partials/load-balancing/health-check-regions.mdx
index cb98a0bc269813a..85b94acbc34ab57 100644
--- a/src/content/partials/load-balancing/health-check-regions.mdx
+++ b/src/content/partials/load-balancing/health-check-regions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For each option selected in a pool's **Health Monitor Regions**, Cloudflare sends health monitor requests from three separate data centers in that region.
diff --git a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
index e1379917600272c..aa5e650fec2b99b 100644
--- a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Layer 4 load balancers route traffic by forwarding traffic to certain ports or IP addresses.
@@ -9,8 +8,6 @@ Cloudflare currently only supports layer 4 load balancing as part of [Cloudflare
 
 :::note
 
-
 Since Spectrum operates at the TCP level, it does not have the information to support features like [session affinity](/load-balancing/understand-basics/session-affinity/), [custom rules](/load-balancing/additional-options/load-balancing-rules/), or caching.
 
-
 :::
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
index 9dfc53ccb56e590..5d6045bd0ac9477 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 In comparison to DNS-only load balancing, layer 7 load balancing:
 
-* Protects endpoints from DDoS attacks by hiding their IP addresses.
-* Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
-* Integrates with other Cloudflare features such as caching, Workers, and the WAF.
-* Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
-* Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
-* More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
-* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
+- Protects endpoints from DDoS attacks by hiding their IP addresses.
+- Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
+- Integrates with other Cloudflare features such as caching, Workers, and the WAF.
+- Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
+- Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
+- More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
+- Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
index 120a77b9f1486a4..78f4d9da0758f11 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Layer 7 load balancers direct traffic to specific endpoints based on information present in each HTTP/HTTPS request (HTTP headers, URI, cookies, type of data, etc.).
diff --git a/src/content/partials/load-balancing/load-balancer-create-api.mdx b/src/content/partials/load-balancing/load-balancer-create-api.mdx
index 8dbe3ed3d7b8337..9110fc3325a87d9 100644
--- a/src/content/partials/load-balancing/load-balancer-create-api.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -9,91 +8,89 @@ For a full list of properties, refer to [Create Load Balancer](/api/resources/lo
 
 :::note
 
-
 Since load balancers only exist on a zone — and not an account — you may need to get the zone `id` with the [List Zones](/api/resources/zones/methods/list/) command.
 
-
 :::
 
 <APIRequest
-  path="/zones/{zone_id}/load_balancers"
-  method="POST"
-  json={{
-    description: "Load Balancer for lb.example.com",
-    name: "lb.example.com",
-    enabled: true,
-    ttl: 30,
-    fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
-    default_pools: [
-      "17b5962d775c646f3f9725cbc7a53df4",
-      "9290f38c5d07c2e2f4df57b1f61d4196",
-      "00920f38ce07c2e2f4df50b1f61d4194"
-    ],
-    proxied: true,
-    steering_policy: "random_steering",
-    session_affinity: "cookie",
-    session_affinity_attributes: {
-      samesite: "Auto",
-      secure: "Auto",
-      drain_duration: 100,
-      zero_downtime_failover: "sticky"
-    },
-    session_affinity_ttl: 5000,
-    adaptive_routing: {
-      failover_across_pools: true
-    },
-    location_strategy: {
-      prefer_ecs: "always",
-      mode: "resolver_ip"
-    },
-    random_steering: {
-      pool_weights: {
-        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-      },
-      default_weight: 0.2
-    }
-  }}
+	path="/zones/{zone_id}/load_balancers"
+	method="POST"
+	json={{
+		description: "Load Balancer for lb.example.com",
+		name: "lb.example.com",
+		enabled: true,
+		ttl: 30,
+		fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
+		default_pools: [
+			"17b5962d775c646f3f9725cbc7a53df4",
+			"9290f38c5d07c2e2f4df57b1f61d4196",
+			"00920f38ce07c2e2f4df50b1f61d4194",
+		],
+		proxied: true,
+		steering_policy: "random_steering",
+		session_affinity: "cookie",
+		session_affinity_attributes: {
+			samesite: "Auto",
+			secure: "Auto",
+			drain_duration: 100,
+			zero_downtime_failover: "sticky",
+		},
+		session_affinity_ttl: 5000,
+		adaptive_routing: {
+			failover_across_pools: true,
+		},
+		location_strategy: {
+			prefer_ecs: "always",
+			mode: "resolver_ip",
+		},
+		random_steering: {
+			pool_weights: {
+				de90f38ced07c2e2f4df50b1f61d4194: 0.3,
+				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5,
+			},
+			default_weight: 0.2,
+		},
+	}}
 />
 
 The response contains the complete definition of the new load balancer.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "699d98642c564d2e855e9661899b7252",
-    "created_on": "2021-01-01T05:20:00.12345Z",
-    "modified_on": "2021-01-01T05:20:00.12345Z",
-    "description": "Load Balancer for lb.example.com",
-    "name": "lb.example.com",
-    "enabled": true,
-    "ttl": 30,
-    "fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
-    "default_pools": [
-      "17b5962d775c646f3f9725cbc7a53df4",
-      "9290f38c5d07c2e2f4df57b1f61d4196",
-      "00920f38ce07c2e2f4df50b1f61d4194"
-    ],
-    "proxied": true,
-    "steering_policy": "random_steering",
-    "session_affinity": "cookie",
-    "session_affinity_attributes": {
-      "samesite": "Auto",
-      "secure": "Auto",
-      "drain_duration": 100,
-      "zero_downtime_failover": "sticky"
-    },
-    "session_affinity_ttl": 5000,
-    "random_steering": {
-      "pool_weights": {
-        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-      },
-      "default_weight": 0.2
-    }
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "699d98642c564d2e855e9661899b7252",
+		"created_on": "2021-01-01T05:20:00.12345Z",
+		"modified_on": "2021-01-01T05:20:00.12345Z",
+		"description": "Load Balancer for lb.example.com",
+		"name": "lb.example.com",
+		"enabled": true,
+		"ttl": 30,
+		"fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
+		"default_pools": [
+			"17b5962d775c646f3f9725cbc7a53df4",
+			"9290f38c5d07c2e2f4df57b1f61d4196",
+			"00920f38ce07c2e2f4df50b1f61d4194"
+		],
+		"proxied": true,
+		"steering_policy": "random_steering",
+		"session_affinity": "cookie",
+		"session_affinity_attributes": {
+			"samesite": "Auto",
+			"secure": "Auto",
+			"drain_duration": 100,
+			"zero_downtime_failover": "sticky"
+		},
+		"session_affinity_ttl": 5000,
+		"random_steering": {
+			"pool_weights": {
+				"de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+			},
+			"default_weight": 0.2
+		}
+	}
 }
 ```
diff --git a/src/content/partials/load-balancing/load-balancer-create.mdx b/src/content/partials/load-balancing/load-balancer-create.mdx
index 0eddd6c4f2e92bb..d0b76484eaea2e6 100644
--- a/src/content/partials/load-balancing/load-balancer-create.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create a Public or a Private load balancer in the dashboard:
@@ -9,31 +8,31 @@ To create a Public or a Private load balancer in the dashboard:
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Public load balancer** 
+2. On the **Load Balancer Setup**, select **Public load balancer**
 
-3. Choose the website to which you want to add this load balancer. 
+3. Choose the website to which you want to add this load balancer.
 
 4. On the **Hostname** page:
-   * Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
-   * From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
-   * Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
-   * Add a description for your load balancer. 
-   * If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
-   * If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
+   - Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
+   - From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
+   - Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
+   - Add a description for your load balancer.
+   - If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
+   - If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
 
 5. Select **Next**.
 
 6. On the **Add a Pool** page:
-   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 7. Select **Next**.
 
 8. On the **Monitors** page:
-   * Review the monitors attached to your pools.
-   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   - Review the monitors attached to your pools.
+   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 9. Select **Next**.
 
@@ -44,28 +43,28 @@ To create a Public or a Private load balancer in the dashboard:
 12. Select **Next**.
 
 13. On the **Review** page:
-    * Review your configuration and make any changes.
-    * Choose whether to **Save as Draft** or **Save and Deploy**.
+    - Review your configuration and make any changes.
+    - Choose whether to **Save as Draft** or **Save and Deploy**.
 
-### Create a Private load balancer 
+### Create a Private load balancer
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Private load balancer** 
+2. On the **Load Balancer Setup**, select **Private load balancer**
 
 3. Associate your load balancer with either a Cloudflare private IP or a specified IP address and create a description for your load balancer.
 
 4. On the **Add a Pool** page:
-   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 5. Select **Next**.
 
 6. On the **Monitors** page:
-   * Review the monitors attached to your pools.
-   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   - Review the monitors attached to your pools.
+   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 7. Select **Next**.
 
@@ -74,5 +73,5 @@ To create a Public or a Private load balancer in the dashboard:
 9. Select **Next**.
 
 10. On the **Review** page:
-    * Review your configuration and make any changes.
-    * Choose whether to **Save as Draft** or **Save and Deploy**.
+    - Review your configuration and make any changes.
+    - Choose whether to **Save as Draft** or **Save and Deploy**.
diff --git a/src/content/partials/load-balancing/load-balancer-definition.mdx b/src/content/partials/load-balancing/load-balancer-definition.mdx
index 7c7f1e2775cb3b6..e955489d0848da8 100644
--- a/src/content/partials/load-balancing/load-balancer-definition.mdx
+++ b/src/content/partials/load-balancing/load-balancer-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.) or IP address.
diff --git a/src/content/partials/load-balancing/load-balancing-diagram.mdx b/src/content/partials/load-balancing/load-balancing-diagram.mdx
index 8f66f37a89cdc36..bc43dd9c4d9b564 100644
--- a/src/content/partials/load-balancing/load-balancing-diagram.mdx
+++ b/src/content/partials/load-balancing/load-balancing-diagram.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/monitor-create-api.mdx b/src/content/partials/load-balancing/monitor-create-api.mdx
index d1d69939d9bd159..cc778566aa44003 100644
--- a/src/content/partials/load-balancing/monitor-create-api.mdx
+++ b/src/content/partials/load-balancing/monitor-create-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { APIRequest } from "~/components";
@@ -8,65 +7,61 @@ import { APIRequest } from "~/components";
 For a full list of monitor properties, refer to [Create Monitor](/api/resources/load_balancers/subresources/monitors/methods/create/). If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
 <APIRequest
-  path="/accounts/{account_id}/load_balancers/monitors"
-  method="POST"
-  json={{
-    type: "https",
-    description: "Login page monitor",
-    method: "GET",
-    path: "/health",
-    header: {
-      Host: ["example.com"],
-      "X-App-ID": ["abc123"]
-    },
-    port: 8080,
-    timeout: 3,
-    retries: 0,
-    interval: 90,
-    expected_body: "alive",
-    expected_codes: "2xx",
-    follow_redirects: true,
-    allow_insecure: true,
-    consecutive_up: 3,
-    consecutive_down: 2,
-    probe_zone: "example.com"
-  }}
+	path="/accounts/{account_id}/load_balancers/monitors"
+	method="POST"
+	json={{
+		type: "https",
+		description: "Login page monitor",
+		method: "GET",
+		path: "/health",
+		header: {
+			Host: ["example.com"],
+			"X-App-ID": ["abc123"],
+		},
+		port: 8080,
+		timeout: 3,
+		retries: 0,
+		interval: 90,
+		expected_body: "alive",
+		expected_codes: "2xx",
+		follow_redirects: true,
+		allow_insecure: true,
+		consecutive_up: 3,
+		consecutive_down: 2,
+		probe_zone: "example.com",
+	}}
 />
 
 The response contains the complete definition of the new monitor.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": ":monitor-id",
-    "created_on": "2021-01-01T05:20:00.12345Z",
-    "modified_on": "2021-01-01T05:20:00.12345Z",
-    "type": "https",
-    "description": "Login page monitor",
-    "method": "GET",
-    "path": "/health",
-    "header": {
-      "Host": [
-        "example.com"
-      ],
-      "X-App-ID": [
-        "abc123"
-      ]
-    },
-    "port": 8080,
-    "timeout": 3,
-    "retries": 0,
-    "interval": 90,
-    "expected_body": "alive",
-    "expected_codes": "2xx",
-    "follow_redirects": true,
-    "allow_insecure": true,
-    "consecutive_up": 3,
-    "consecutive_down": 2,
-    "probe_zone": "example.com"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": ":monitor-id",
+		"created_on": "2021-01-01T05:20:00.12345Z",
+		"modified_on": "2021-01-01T05:20:00.12345Z",
+		"type": "https",
+		"description": "Login page monitor",
+		"method": "GET",
+		"path": "/health",
+		"header": {
+			"Host": ["example.com"],
+			"X-App-ID": ["abc123"]
+		},
+		"port": 8080,
+		"timeout": 3,
+		"retries": 0,
+		"interval": 90,
+		"expected_body": "alive",
+		"expected_codes": "2xx",
+		"follow_redirects": true,
+		"allow_insecure": true,
+		"consecutive_up": 3,
+		"consecutive_down": 2,
+		"probe_zone": "example.com"
+	}
 }
 ```
diff --git a/src/content/partials/load-balancing/monitor-create.mdx b/src/content/partials/load-balancing/monitor-create.mdx
index e886aac579f8934..cba41c6a75cd948 100644
--- a/src/content/partials/load-balancing/monitor-create.mdx
+++ b/src/content/partials/load-balancing/monitor-create.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can create a monitor within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Monitors** tab:
 
diff --git a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
index 203ada096f2b360..000c0980eda9bc6 100644
--- a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
+++ b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **All Data Centers (Enterprise only)**
@@ -17,10 +16,8 @@ Three health monitor probes are sent from each specified region within the pool
 
 :::caution
 
-
 Because of how Cloudflare checks health from [multiple regions](#health-monitor-regions), adding multiple regions — or choosing to check health from **All Data Centers** — can send a lot of traffic to your endpoint.
 
 The same problem can occur when setting low values for a monitor's **Interval**.
 
-
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/load-balancing/monitor-prepare-server.mdx b/src/content/partials/load-balancing/monitor-prepare-server.mdx
index cac096756d634a6..40b7618385d0835 100644
--- a/src/content/partials/load-balancing/monitor-prepare-server.mdx
+++ b/src/content/partials/load-balancing/monitor-prepare-server.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with [Cloudflare IP addresses](https://www.cloudflare.com/ips).
@@ -9,8 +8,6 @@ Each health monitor has the HTTP user-agent of `"Mozilla/5.0 (compatible; Cloudf
 
 :::caution
 
-
 If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our [Monitor troubleshooting guide](/load-balancing/troubleshooting/load-balancing-faq/#why-is-my-endpoint-or-pool-considered-unhealthy).
 
-
 :::
diff --git a/src/content/partials/load-balancing/monitor-settings-basic.mdx b/src/content/partials/load-balancing/monitor-settings-basic.mdx
index 61c55dcb0698619..48d2f9414f6707b 100644
--- a/src/content/partials/load-balancing/monitor-settings-basic.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-basic.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* **Type**: The protocol to use for health monitors
-  * *Non-enterprise customers*: Choose **HTTP**, **HTTPS**, or **TCP**.
-  * *Enterprise customers*: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
-* **Path**: The endpoint path to run health monitor requests against
-* **Port**: The destination port for health monitors
+- **Type**: The protocol to use for health monitors
+  - _Non-enterprise customers_: Choose **HTTP**, **HTTPS**, or **TCP**.
+  - _Enterprise customers_: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
+- **Path**: The endpoint path to run health monitor requests against
+- **Port**: The destination port for health monitors
diff --git a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
index 5ea1696866dbf6b..d6ca1888d5c5948 100644
--- a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
@@ -1,14 +1,11 @@
 ---
 {}
-
 ---
 
 :::note[Note]
 
-
 To increase confidence in pool status, you can also increase the `consecutive_up` and `consecutive_down` fields when [creating a monitor with the API](/api/resources/load_balancers/subresources/monitors/methods/create/).
 
 To become healthy or unhealthy, monitored endpoints must pass this health monitor request the consecutive number of times specified in these parameters.
 
-
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-definition.mdx b/src/content/partials/load-balancing/origin-steering-definition.mdx
index ff95cda09a041f0..41f06c64c7d903e 100644
--- a/src/content/partials/load-balancing/origin-steering-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-definition.mdx
@@ -1,19 +1,16 @@
 ---
 {}
-
 ---
 
 Endpoint steering customizes how each [pool](/load-balancing/pools/) distributes requests to its associated endpoints.
 
 These distributions are a combination of two properties:
 
-* The endpoint steering [policy](#policies) chosen for your pool.
-* The [weights](#weights) assigned to each endpoint.
+- The endpoint steering [policy](#policies) chosen for your pool.
+- The [weights](#weights) assigned to each endpoint.
 
 :::note
 
-
 If an endpoint [becomes unhealthy](/load-balancing/understand-basics/health-details/), your pool will also re-balance traffic according to its endpoint steering policy.
 
-
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-policies.mdx b/src/content/partials/load-balancing/origin-steering-policies.mdx
index f1231eacca1c19e..3588f6aa482ccc6 100644
--- a/src/content/partials/load-balancing/origin-steering-policies.mdx
+++ b/src/content/partials/load-balancing/origin-steering-policies.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you [create a pool](/load-balancing/pools/create-pool/), you have to choose an option for **Endpoint Steering**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
index 02f56f65d616a1b..04b243f9c170afd 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The weight assigned to an endpoint controls the percentage of pool traffic sent to that endpoint. By default, all endpoints within a pool have a weight of **1**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
index 003b326d282ef75..55e5f89bf7d1d0a 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you choose **Hash** for your **Endpoint Steering** or enable [session affinity](/load-balancing/understand-basics/session-affinity/), these options can affect traffic distribution.
diff --git a/src/content/partials/load-balancing/pool-create.mdx b/src/content/partials/load-balancing/pool-create.mdx
index c6b72f1a6076a14..198bbcd758d3fd7 100644
--- a/src/content/partials/load-balancing/pool-create.mdx
+++ b/src/content/partials/load-balancing/pool-create.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can create a pool within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Pools** tab:
 
@@ -12,24 +11,22 @@ You can create a pool within the [load balancer workflow](/load-balancing/load-b
 2. Select the **Pools** tab and then **Create pool**.
 
 3. For your pool, enter the following information:
-   * A name (must be unique)
-   * A description to provide more detail on the name
-   * A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
+   - A name (must be unique)
+   - A description to provide more detail on the name
+   - A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
 
 4. For each endpoint, enter the following information:
-   * A name (must be unique)
-   * The endpoint address or associated hostname
-   * (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
-   * A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
-   * (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
-   * (Optional) The destination port to which the traffic will be served.
+   - A name (must be unique)
+   - The endpoint address or associated hostname
+   - (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
+   - A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
+   - (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
+   - (Optional) The destination port to which the traffic will be served.
 
 :::note[Note]
 
-
 If your endpoint is a website or application hosted on [Cloudflare Pages](/pages/), you will need to fill in the host header field with the project domain for it to resolve correctly.
 
-
 :::
 
 5. Repeat this process for additional endpoints in the pool.
@@ -37,9 +34,9 @@ If your endpoint is a website or application hosted on [Cloudflare Pages](/pages
 6. (Optional) Set up coordinates for [Proximity Steering](/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering/) on the pool.
 
 7. On the pool, update the following information:
-   * **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
-   * **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
-   * **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
-   * **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
+   - **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
+   - **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
+   - **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
+   - **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
 
 8. When finished, select **Save**.
diff --git a/src/content/partials/load-balancing/pool-health-threshold.mdx b/src/content/partials/load-balancing/pool-health-threshold.mdx
index 825e481e8f68a55..ef2bac2c25ed613 100644
--- a/src/content/partials/load-balancing/pool-health-threshold.mdx
+++ b/src/content/partials/load-balancing/pool-health-threshold.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered *Healthy* and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
+The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered _Healthy_ and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
diff --git a/src/content/partials/load-balancing/region-mapping.mdx b/src/content/partials/load-balancing/region-mapping.mdx
index 128fad39ca78170..1bd65acff2b56cc 100644
--- a/src/content/partials/load-balancing/region-mapping.mdx
+++ b/src/content/partials/load-balancing/region-mapping.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 | Region code | Region name            |
diff --git a/src/content/partials/load-balancing/route-production-traffic.mdx b/src/content/partials/load-balancing/route-production-traffic.mdx
index 3e1b688df82eeb7..5da9c7169712872 100644
--- a/src/content/partials/load-balancing/route-production-traffic.mdx
+++ b/src/content/partials/load-balancing/route-production-traffic.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Now that you have set up your load balancer and verified everything is working correctly, you can put the load balancer on a live domain or subdomain:
@@ -8,13 +7,11 @@ Now that you have set up your load balancer and verified everything is working c
 1. If you update your pools and monitors, review the pool health again to make sure everything is working as expected.
 2. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 3. Configure your load balancer to receive production traffic, which could involve either:
-   * Editing the **Hostname** of your existing load balancer.
-   * Updating the `CNAME` record sending traffic to your load balancer.
+   - Editing the **Hostname** of your existing load balancer.
+   - Updating the `CNAME` record sending traffic to your load balancer.
 
 :::note
 
-
 If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [origin rule](/rules/origin-rules/features/#dns-record).
 
-
 :::
diff --git a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
index b6398dd605663ec..8c0d3b883dc0ee3 100644
--- a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
+++ b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Session affinity automatically directs requests from the same client to the same endpoint:
@@ -25,8 +24,8 @@ Session affinity automatically directs requests from the same client to the same
      end
 ```
 
-<br/>
+<br />
 
-All cookie-based sessions default to 23 hours unless you set a custom session *Time to live* (TTL).
+All cookie-based sessions default to 23 hours unless you set a custom session _Time to live_ (TTL).
 
 The session cookie is secure when [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) is enabled. Additionally, HttpOnly is always enabled for the cookie to prevent cross-site scripting attacks.
diff --git a/src/content/partials/load-balancing/session-affinity-definition.mdx b/src/content/partials/load-balancing/session-affinity-definition.mdx
index 457703c7c032ae8..5b2531052f2e4ae 100644
--- a/src/content/partials/load-balancing/session-affinity-definition.mdx
+++ b/src/content/partials/load-balancing/session-affinity-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When you enable session affinity, your load balancer directs all requests from a particular end user to a specific endpoint. This continuity preserves information about the user session — such as items in their shopping cart — that might otherwise be lost if requests were spread out among multiple servers.
diff --git a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
index dfe52808eb3b9c0..4daefe6d4a289dd 100644
--- a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
+++ b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
+- Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
 
-* UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
+- UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
diff --git a/src/content/partials/load-balancing/test-domain-setup.mdx b/src/content/partials/load-balancing/test-domain-setup.mdx
index 8a7c754c580a135..88b53616839ade6 100644
--- a/src/content/partials/load-balancing/test-domain-setup.mdx
+++ b/src/content/partials/load-balancing/test-domain-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Instead of starting on your production domain, you likely should create a load balancer on a test or staging domain. This may involve temporary changes to your monitors and pools, depending on your infrastructure setup.
diff --git a/src/content/partials/load-balancing/traffic-steering-definition.mdx b/src/content/partials/load-balancing/traffic-steering-definition.mdx
index 471d03f63fbe154..84b6a196eba9451 100644
--- a/src/content/partials/load-balancing/traffic-steering-definition.mdx
+++ b/src/content/partials/load-balancing/traffic-steering-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Global traffic steering policies decide how a load balancer routes traffic to attached and healthy pools.
diff --git a/src/content/partials/load-balancing/unexpected-health-statuses.mdx b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
index cc03b813fa18383..9bd3a6cad5b730a 100644
--- a/src/content/partials/load-balancing/unexpected-health-statuses.mdx
+++ b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 If you notice that healthy pools are being marked unhealthy:
 
-* Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
-* Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
+- Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
+- Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
diff --git a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
index 8e1a71d8ff5616f..d0ec34fe725e179 100644
--- a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
+++ b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
@@ -1,13 +1,11 @@
 ---
 {}
-
 ---
 
 When a pool reaches **Critical** health, your load balancer will begin diverting traffic according to its [Traffic steering policy](/load-balancing/understand-basics/traffic-steering/steering-policies/):
 
-* **Off**:
-
-  * If the active pool becomes unhealthy, traffic goes to the next pool in order.
-  * If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
+- **Off**:
+  - If the active pool becomes unhealthy, traffic goes to the next pool in order.
+  - If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
 
-* **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
+- **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
diff --git a/src/content/partials/logs/check-log-retention.mdx b/src/content/partials/logs/check-log-retention.mdx
index 6a5b9c2e8254154..13b4c54b32aacc3 100644
--- a/src/content/partials/logs/check-log-retention.mdx
+++ b/src/content/partials/logs/check-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/disable-log-retention.mdx b/src/content/partials/logs/disable-log-retention.mdx
index 3a89db7ac7c39e0..f13215928cc87a1 100644
--- a/src/content/partials/logs/disable-log-retention.mdx
+++ b/src/content/partials/logs/disable-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-log-retention.mdx b/src/content/partials/logs/enable-log-retention.mdx
index 7d9a9ac4a7a3e7c..46ea7dc9617f844 100644
--- a/src/content/partials/logs/enable-log-retention.mdx
+++ b/src/content/partials/logs/enable-log-retention.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-logpush-job.mdx b/src/content/partials/logs/enable-logpush-job.mdx
index 9c86c3c83faa49b..f571da2cfbdba5a 100644
--- a/src/content/partials/logs/enable-logpush-job.mdx
+++ b/src/content/partials/logs/enable-logpush-job.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
- 
+
    For account: <DashButton url="/?to=/:account/logs" />
- 
+
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
diff --git a/src/content/partials/logs/enable-read-permissions.mdx b/src/content/partials/logs/enable-read-permissions.mdx
index b2b55619a3f5903..0782c628cb0ea41 100644
--- a/src/content/partials/logs/enable-read-permissions.mdx
+++ b/src/content/partials/logs/enable-read-permissions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Ensure **Log Share** permissions are enabled, before attempting to read or configure a Logpush job. For more information refer to the [Roles section](/logs/logpush/permissions/#roles).
diff --git a/src/content/partials/logs/filtering-limitations.mdx b/src/content/partials/logs/filtering-limitations.mdx
index 2d32cc7f88aa921..1f28334e5fc8c7b 100644
--- a/src/content/partials/logs/filtering-limitations.mdx
+++ b/src/content/partials/logs/filtering-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note[Note]
diff --git a/src/content/partials/networking-services/account-id-api-key.mdx b/src/content/partials/networking-services/account-id-api-key.mdx
index c2532c7e6b0a36c..ae09eb187dd2510 100644
--- a/src/content/partials/networking-services/account-id-api-key.mdx
+++ b/src/content/partials/networking-services/account-id-api-key.mdx
@@ -1,16 +1,18 @@
 ---
 {}
-
 ---
 
 import { Markdown } from "~/components";
 
-{/* 
-  Conditional rendering based on showSiteId prop:
-  - When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
-  - When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
+{/\*
+Conditional rendering based on showSiteId prop:
+
+- When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
+- When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
   The ternaries only render the differing prefix and suffix to avoid content duplication.
-*/}
-:::note
-<Markdown text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`} />
-:::
+  \*/}
+  :::note
+  <Markdown
+  	text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`}
+  />
+  :::
diff --git a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
index 665ea039cad5541..e7f64d2d3b9bca3 100644
--- a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
+++ b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
@@ -9,4 +9,4 @@ When you set up an alert for your site, you will be notified when there is an is
 To set up health alerts:
 
 1. Configure <a href={props.magicTunnelHcsURL}>Tunnel health alerts</a> across all of the tunnels associated with each {props.productName} site.
-2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
\ No newline at end of file
+2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
diff --git a/src/content/partials/networking-services/analytics/site-analytics.mdx b/src/content/partials/networking-services/analytics/site-analytics.mdx
index 5f9269dba906210..03a99eb68bf605b 100644
--- a/src/content/partials/networking-services/analytics/site-analytics.mdx
+++ b/src/content/partials/networking-services/analytics/site-analytics.mdx
@@ -7,51 +7,45 @@ params:
   - setGeoCoordinatesURL
 ---
 
-
-
-import { Details, Markdown, DashButton } from "~/components"
+import { Details, Markdown, DashButton } from "~/components";
 
 After adding your sites, the {props.networkOverviewPageName} section of the dashboard provides a summary of the connectivity status and traffic analytics for all your sites. This is a great place to start if you receive a Cloudflare WAN alert, need to begin the troubleshooting process, or are performing routine monitoring. <Markdown text={props.instructions} />
 
 {props.networkOverviewPageName} has the following data types available:
 
 <Details header="Geographic map summary">
-	- [Aggregate Cloudflare WAN site health](#site-health)
-	- [Cloudflare WAN availability status for sites](#no-status-available)
-	- [Cloudflare WAN site geographic location](#no-location-set)
+	- [Aggregate Cloudflare WAN site health](#site-health) - [Cloudflare WAN
+	availability status for sites](#no-status-available) - [Cloudflare WAN site
+	geographic location](#no-location-set)
 </Details>
 
 <Details header="Cloudflare WAN site data table">
-	- Site Name
-	- Site Health
-	- Site Tunnel Names
-	- Site Tunnel Statuses
-	- Site Traffic Sent
-	- Site Traffic Received
+	- Site Name - Site Health - Site Tunnel Names - Site Tunnel Statuses - Site
+	Traffic Sent - Site Traffic Received
 </Details>
 
 <Details header="Cloudflare WAN site data">
-	- Traffic Sent by Tunnel
-	- Traffic Received by Tunnel
+	- Traffic Sent by Tunnel - Traffic Received by Tunnel
 </Details>
 
 To start using network overview:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **${props.networkOverviewPageName}**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
+    <DashButton url="/?to=/:account/networking-insights/health" />
+    </>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
-	</>
 )
 }
 
@@ -83,7 +77,6 @@ The status of a site refers to its health. If your sites show a **No status avai
 
 The dashboard displays the number of sites with no location set, meaning sites for which you did not set up a geographic location. To add a location to a site, find the site you want to add location to, and select **no location set** to edit its location settings. Refer to <a href={props.setGeoCoordinatesURL}>Set geographic coordinates</a> for more information.
 
-
 ### Traffic overview
 
 Traffic overview aggregates all Cloudflare WAN sites configured in your account. Here, you can check summary information about each site like:
@@ -91,4 +84,4 @@ Traffic overview aggregates all Cloudflare WAN sites configured in your account.
 - Site status
 - Traffic sent and received
 
-Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
\ No newline at end of file
+Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
diff --git a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
index fb6b8b613c66bea..9388b0a604a3311 100644
--- a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
+++ b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
@@ -30,7 +30,7 @@ The following table provides a high-level comparison of all connectivity options
 | [Cloudflare Tunnel](#cloudflare-tunnel) | HTTP/2, QUIC | Off-ramp only | Software daemon (`cloudflared`) on server | Exposing private applications without a public IP |
 | [Cloudflare One Client](#cloudflare-one-client) | MASQUE (default), WireGuard | Bidirectional | Client software on end-user devices | Securing remote workforce devices |
 | [Cloudflare Mesh](#cloudflare-mesh) | MASQUE | Bidirectional | Software client on Linux host | Connecting sites with IoT or VoIP devices |
-| [DNS locations](#dns-locations) |  DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration  | Filtering DNS traffic without device agents |
+| [DNS locations](#dns-locations) | DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration | Filtering DNS traffic without device agents |
 | [Proxy endpoints](#proxy-endpoints) | HTTP/HTTPS | On-ramp only | Browser PAC file configuration | Filtering web traffic without device agents |
 | [Clientless Web Isolation](#clientless-web-isolation) | HTTP/HTTPS | On-ramp only | Prefixed URL with Access authentication | Secure web access for unmanaged devices |
 | [GRE tunnels](#gre-tunnels) | GRE | Bidirectional | Network tunnel from router or firewall | Connecting sites with existing network hardware |
@@ -97,9 +97,9 @@ DNS locations allow you to filter DNS traffic from networks without deploying th
 
 DNS locations support multiple endpoint types:
 
-* **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
-* **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
-* **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
+- **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
+- **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
+- **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
 
 Use DNS locations when you need to filter DNS traffic for an entire office or network, per device without installing agents on devices, or integrate with existing network infrastructure.
 
@@ -119,8 +119,8 @@ Proxy endpoints allow you to apply Cloudflare Gateway HTTP policies without inst
 
 Cloudflare One supports two types of proxy endpoints:
 
-* **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
-* **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
+- **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
+- **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
 
 Use proxy endpoints when you need to filter web traffic without device agents, integrate with existing proxy infrastructure, or deploy Gateway alongside other security tools.
 
@@ -283,7 +283,7 @@ The connectivity options on this page connect your private infrastructure, sites
 
 - **Non-HTTP traffic** (TCP/UDP protocols such as gaming, email, or custom services) — refer to [Spectrum](/spectrum/).
 - **Network-level DDoS protection** (for on-premises, cloud-hosted, and hybrid networks) — refer to [Magic Transit](/magic-transit/).
-:::
+  :::
 
 ### Cloudflare One recommendations by team
 
@@ -301,14 +301,14 @@ The team driving your Cloudflare One connectivity project influences which optio
 
 Cloudflare Mesh and Cloudflare One Appliance both provide site-level connectivity, but serve different deployment scenarios.
 
-| Aspect | Cloudflare Mesh | Cloudflare One Appliance |
-| ---- | ---- | ---- |
-| **Protocol** | MASQUE | IPsec |
-| **Deployment model** | Software on Linux host (can run alongside other workloads) | Dedicated hardware appliance or virtual machine |
-| **Best for** | Cloud VPCs, development environments, smaller deployments with an available Linux host | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
-| **Platform support** | Linux only (x86_64, ARM64). Currently in beta. | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox) |
-| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site |
-| **Management** | Configured as a device in the Cloudflare One Client settings | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning |
+| Aspect                | Cloudflare Mesh                                                                                                         | Cloudflare One Appliance                                                           |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| **Protocol**          | MASQUE                                                                                                                  | IPsec                                                                              |
+| **Deployment model**  | Software on Linux host (can run alongside other workloads)                                                              | Dedicated hardware appliance or virtual machine                                    |
+| **Best for**          | Cloud VPCs, development environments, smaller deployments with an available Linux host                                  | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
+| **Platform support**  | Linux only (x86_64, ARM64). Currently in beta.                                                                          | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox)                |
+| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site                                     |
+| **Management**        | Configured as a device in the Cloudflare One Client settings                                                            | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning      |
 
 Use Cloudflare Mesh when you need lightweight, software-only connectivity for cloud workloads or sites where a Linux host is available. Use Cloudflare One Appliance when you need enterprise-grade throughput, high availability, or integration with existing network infrastructure.
 
@@ -457,7 +457,8 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)
 - [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)
 - [Cloudflare WAN](/cloudflare-wan/)
-- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of supported on-ramps
+- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of
+  supported on-ramps
 - [Multi-Cloud Networking](/multi-cloud-networking/) - Automate cloud VPC connectivity
 - [Magic Transit](/magic-transit/)
 - <a href={props.connectorURL}>Cloudflare One Appliance</a>
@@ -467,4 +468,4 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) - Filter web traffic using PAC files
 - [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) - Secure web access without device agents
 
-For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/). 
+For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
index 18c9671ea9ce7f4..d436a168d8d8c4c 100644
--- a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
@@ -15,10 +15,11 @@ VeloCloud has a high availability mechanism that allows customers to specify one
 Cloudflare WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for `<account_id>`, `<tunnel_id>`, and the FQDN wildcard before running the API call.
 
 <CURL
-  url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
-  method="PATCH"
-  json={{
-    "custom_remote_identities":
-			{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
-  }}
+	url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
+	method="PATCH"
+	json={{
+		custom_remote_identities: {
+			fqdn_id: "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com",
+		},
+	}}
 />
diff --git a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
index c7cfca556c7a735..ae7c5d5a52b3fa7 100644
--- a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
@@ -64,11 +64,17 @@ The list of prerequisites below is only for customers planning to connect manual
 
 ##### GRE tunnels as off-ramp
 
-<Render file="cloudflare-wan/mtu-mss/mss-clamping-gre" product="networking-services" />
+<Render
+	file="cloudflare-wan/mtu-mss/mss-clamping-gre"
+	product="networking-services"
+/>
 
 ##### IPsec tunnels
 
-<Render file="cloudflare-wan/mtu-mss/mss-clamping-ipsec" product="networking-services"/>
+<Render
+	file="cloudflare-wan/mtu-mss/mss-clamping-ipsec"
+	product="networking-services"
+/>
 
 :::caution[Important]
 Refer to your device documentation to check if it sets IPsec MSS clamping automatically. If that is not the case and you are using IPsec inside GRE, you have to set MSS clamp manually.
@@ -81,4 +87,4 @@ Refer to <a href={props.mtuReferenceURL}>Maximum transmission unit and maximum s
 <Render
 	file="prerequisites/router-vendor-guidelines-mss-settings-origin"
 	product="networking-services"
-/>
\ No newline at end of file
+/>
diff --git a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
index fc3cadd24324184..027327c70df8bf4 100644
--- a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
@@ -6,4 +6,4 @@ If your network has multiple paths to the same destination — for example, redu
 
 Cloudflare WAN (formerly Magic WAN) uses Private Network Load Balancing, which balances traffic across your private network endpoints. It supports both on-ramping (traffic entering Cloudflare's network) and off-ramping (traffic exiting to your sites).
 
-Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
\ No newline at end of file
+Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
index 361286f6db723bf..031870b0e53efd0 100644
--- a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
@@ -24,41 +24,41 @@ params:
   - oracleUrl
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) is compatible with any device that supports <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> with the <a href={props.supportedConfigurationParametersUrl}>supported configuration parameters</a> or supports <GlossaryTooltip term="GRE tunnel">GRE</GlossaryTooltip>.
 
 The matrix below includes example devices and links to the integration guides.
 
-| Appliance | GRE tunnel | IPsec tunnel |
-| --- | --- | --- |
-| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a> |✅ | ✅ |
-| Cisco ASA | Compatibility on roadmap | Specifications compatible[^1] |
-| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a> | ✅ | ✅ |
-| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a> | - | ✅ |
-| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>  | ✅ | ✅ |
-| <a href={props.fortinetUrl}>Fortinet</a>| Specifications compatible[^1] | ✅ |
-| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a> | - | ✅ |
-| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a> | Specifications compatible[^1] | ✅ |
-| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅ |
-| <a href={props.pfsenseUrl}>pfSense</a>| ✅ | ✅ |
-| Prisma SD-WAN (Palo Alto) | Specifications compatible[^1] | Specifications compatible[^1] |
-| Riverbed  | Specifications compatible[^1] | Specifications compatible[^1] |
-| <a href={props.sonicwallUrl}>SonicWall</a>| - | ✅ |
-| <a href={props.sophosFirewallUrl}>Sophos Firewall</a> | ✅ | ✅ |
-| <a href={props.strongswanUrl}>strongSwan</a> | - | ✅ |
-| <a href={props.ubiquitiUrl}>Ubiquiti</a> | - | ✅ |
-| <a href={props.velocloudUrl}>Velocloud</a> | - | ✅ |
-| Versa  | Specifications compatible[^1] | Compatibility on roadmap |
-| <a href={props.vyosUrl}>VyOS</a>| ✅ | ✅ |
-| <a href={props.yamahaUrl}>Yamaha RTX Router</a> | - | ✅ |
+| Appliance                                                                   | GRE tunnel                    | IPsec tunnel                  |
+| --------------------------------------------------------------------------- | ----------------------------- | ----------------------------- |
+| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a>                   | ✅                            | ✅                            |
+| Cisco ASA                                                                   | Compatibility on roadmap      | Specifications compatible[^1] |
+| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a>                              | ✅                            | ✅                            |
+| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a>   | -                             | ✅                            |
+| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>                              | ✅                            | ✅                            |
+| <a href={props.fortinetUrl}>Fortinet</a>                                    | Specifications compatible[^1] | ✅                            |
+| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a>                  | -                             | ✅                            |
+| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a>  | Specifications compatible[^1] | ✅                            |
+| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅                            |
+| <a href={props.pfsenseUrl}>pfSense</a>                                      | ✅                            | ✅                            |
+| Prisma SD-WAN (Palo Alto)                                                   | Specifications compatible[^1] | Specifications compatible[^1] |
+| Riverbed                                                                    | Specifications compatible[^1] | Specifications compatible[^1] |
+| <a href={props.sonicwallUrl}>SonicWall</a>                                  | -                             | ✅                            |
+| <a href={props.sophosFirewallUrl}>Sophos Firewall</a>                       | ✅                            | ✅                            |
+| <a href={props.strongswanUrl}>strongSwan</a>                                | -                             | ✅                            |
+| <a href={props.ubiquitiUrl}>Ubiquiti</a>                                    | -                             | ✅                            |
+| <a href={props.velocloudUrl}>Velocloud</a>                                  | -                             | ✅                            |
+| Versa                                                                       | Specifications compatible[^1] | Compatibility on roadmap      |
+| <a href={props.vyosUrl}>VyOS</a>                                            | ✅                            | ✅                            |
+| <a href={props.yamahaUrl}>Yamaha RTX Router</a>                             | -                             | ✅                            |
 
-| VPN | GRE tunnel | IPsec tunnel |
-| --- | --- | --- |
-| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | - | ✅ |
-| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>          | - | ✅ |
-| <a href={props.azureUrl}>Azure VPN Gateway</a>                 | - | ✅ |
-| <a href={props.googleUrl}>GCP Cloud VPN</a>                    | - | ✅ |
-| <a href={props.oracleUrl}>Oracle Cloud</a> 										| - | ✅ |
+| VPN                                                           | GRE tunnel | IPsec tunnel |
+| ------------------------------------------------------------- | ---------- | ------------ |
+| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | -          | ✅           |
+| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>         | -          | ✅           |
+| <a href={props.azureUrl}>Azure VPN Gateway</a>                | -          | ✅           |
+| <a href={props.googleUrl}>GCP Cloud VPN</a>                   | -          | ✅           |
+| <a href={props.oracleUrl}>Oracle Cloud</a>                    | -          | ✅           |
 
 [^1]: Specifications compatible per vendor documentation
diff --git a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
index 2c7ce55ec60f37e..2b8dae020681cee 100644
--- a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
@@ -7,4 +7,4 @@ Once your traffic flows through Cloudflare's network, you can apply security pol
 
 **[Cloudflare Network Firewall](/cloudflare-network-firewall/)** filters traffic at layers 3 and 4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/) — the network and transport layers. You can allow or block traffic based on packet characteristics such as source and destination IP addresses, ports, protocols, and packet length. All Cloudflare WAN customers have <a href="/cloudflare-network-firewall/plans/">automatic access to Cloudflare Network Firewall</a>.
 
-**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
\ No newline at end of file
+**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
index 51ffc512d5a6a49..d4b5c75a6d6e558 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
@@ -37,7 +37,7 @@ Additionally, you also need to configure the necessary route table entries for t
 
 5. Take note of the **IP address** you chose, as this corresponds to the customer endpoint IP that you will need to configure on the Cloudflare side of the IPsec tunnel.
 
-6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**.  You will need it to create the IPsec tunnel on Cloudflare's side.
+6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**. You will need it to create the IPsec tunnel on Cloudflare's side.
 
 7. In **Inside IPv4 CIDR**, AWS enforces that only a `/30` block within the `169.254.0.0/16` range can be used. To accommodate this, Cloudflare supports a subset of this IP block. Namely, Cloudflare supports `169.254.240.0/20` to be assigned as the IPsec tunnel's (internal) interface IPs. This example will use `169.254.244.0/30` as the CIDR block for the IPsec tunnel: `169.254.244.1` for the AWS side of the tunnel, and `169.254.244.2` for the Cloudflare side of the tunnel.
 
@@ -84,7 +84,7 @@ After configuring the AWS transit gateway VPN connection and the tunnel as menti
 
 ### Static routes
 
-The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of  `192.168.192.0/26`, you should use it as the prefix for your static route.
+The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of `192.168.192.0/26`, you should use it as the prefix for your static route.
 
 To create a static route:
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
index 2683c003c5db069..58bcc4e8130ad91 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
@@ -36,7 +36,7 @@ Using traditional hub and spoke terminology, a Virtual WAN Hub deployed within a
 4. Select **Create**. Note that the deployment time for the vWAN Hub and VPN Gateway may take 30 minutes or more.
 5. After the VPN Gateway has finished provisioning, go to **Virtual WAN** > **Hubs** > **Your vHub** > **Connectivity** > **VPN (Site to site)**.
 6. In the **Essentials** dropdown select the VPN Gateway listed.
-7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and  `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
+7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
 
 ### 3. Create a VPN site
 
@@ -128,17 +128,17 @@ To create a **VPN Gateway Connection**:
 Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the <a href={props.cloudflareDocumentationUrl}>Cloudflare documentation</a>.
 
 1. **PSK**: Provide the PSK generated by Cloudflare for your IPsec tunnels.
-2. **Protocol**: *IKEv2*
-3. **IPsec**: *Custom*
+2. **Protocol**: _IKEv2_
+3. **IPsec**: _Custom_
    1. **IPsec SA lifetime in seconds**: 28800
    2. **IKE Phase 1**
-      1. **Encryption**: *AES256*
-      2. **Integrity/PRF**: *SHA256*
-      3. **DH Group**: *ECP384*
+      1. **Encryption**: _AES256_
+      2. **Integrity/PRF**: _SHA256_
+      3. **DH Group**: _ECP384_
    3. **IKE Phase 2(IPsec)**
-      1. **IPsec Encryption**: *AES256*
-      2. **IPsec Integrity**: *SHA256*
-      3. **PFS Group**: *ECP384*
+      1. **IPsec Encryption**: _AES256_
+      2. **IPsec Integrity**: _SHA256_
+      3. **PFS Group**: _ECP384_
    4. **Propagate Default Route:** **Disable**
    5. **Use policy based traffic selector**: **Disable**
    6. **Connection mode**: **Initiator Only**
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
index 9a13c91be0214a0..07fb95463263fea 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
@@ -201,7 +201,6 @@ Use the CLI to configure these settings:
 ip route 192.168.1.0 255.255.255.0 tunnel 2
 ```
 
-
 ## Connection test
 
 ### IPsec status
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
index b19e899b9966bbf..64e945e0798b80d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
@@ -42,12 +42,10 @@ By default, the static routes are defined with the priority set to `100`. Cloudf
 
 1. Follow the <a href={props.configureStaticRoutesUrl}>Configure static routes</a> instructions to create a static route.
 2. For the first route, ensure the following settings are defined:
-
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).
 
 3. For the second route, ensure the following settings are defined:
-
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the second IPsec tunnel defined in the previous section.
    - **Tunnel/Next hop**: Select your second tunnel (Tunnel 02 of 02).
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
index 74c35ae14467fa1..c9dfa4d0c897b6d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ## Test Environment
 
-| **Field**                          | **Value**                                      |
-| ---------------------------------- | ---------------------------------------------- |
-| Vendor                             | HPE Juniper Networking                         |
-| Model                              | SRX 320                                        |
-| Release                            | JUNOS 23.4R2-S3.9                              |
-| Date Tested                        | March 2026                                     |
+| **Field**   | **Value**              |
+| ----------- | ---------------------- |
+| Vendor      | HPE Juniper Networking |
+| Model       | SRX 320                |
+| Release     | JUNOS 23.4R2-S3.9      |
+| Date Tested | March 2026             |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**                                      |
-| ---------------------------------- | ---------------------------------------------- |
-| Traffic Selection Criteria         | Route-Based VPN                                |
-| Routing                            | Static                                         |
-| Redundant Tunnels                  | Yes                                            |
-| Tunnel Load Balancing              | Active/Active                                  |
-| IKE Version                        | IKEv2                                          |
-| Authentication                     | Pre-Shared Key                                 |
-| Anti-Replay Protection             | Disabled                                       |
-| NAT Traversal (NAT-T)              | Not Tested                                     |
-| NAT-T Port                         | Not Applicable                                 |
-| Phase 1 - DH-Group                 | Group 20                                       |
-| Phase 1 - Encryption               | AES-256-CBC                                    |
-| Phase 1 - Authentication/Integrity | SHA-256                                        |
-| Phase 2 - DH-Group                 | Group 20                                       |
-| Phase 2 - Transport                | ESP                                            |
-| Phase 2 - Encryption               | AES-256-CBC                                    |
+| **Field**                          | **Value**       |
+| ---------------------------------- | --------------- |
+| Traffic Selection Criteria         | Route-Based VPN |
+| Routing                            | Static          |
+| Redundant Tunnels                  | Yes             |
+| Tunnel Load Balancing              | Active/Active   |
+| IKE Version                        | IKEv2           |
+| Authentication                     | Pre-Shared Key  |
+| Anti-Replay Protection             | Disabled        |
+| NAT Traversal (NAT-T)              | Not Tested      |
+| NAT-T Port                         | Not Applicable  |
+| Phase 1 - DH-Group                 | Group 20        |
+| Phase 1 - Encryption               | AES-256-CBC     |
+| Phase 1 - Authentication/Integrity | SHA-256         |
+| Phase 2 - DH-Group                 | Group 20        |
+| Phase 2 - Transport                | ESP             |
+| Phase 2 - Encryption               | AES-256-CBC     |
 
 ## Cloudflare WAN and HPE Juniper Networking SRX Series Firewalls - Configuration Settings
 
@@ -46,92 +46,92 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_01                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 162.159.135.1                                  |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_01     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.0/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 162.159.135.1     |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`      |
-| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_02                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 172.64.135.1                                   |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_02     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.2/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 172.64.135.1      |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`      |
-| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
 
 ## Customer Premise Equipment - HPE Juniper Networking
 
-| **WAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| WAN Interface                       | ge-0/0/0.0            | ge-0/0/0.0            |
-| IP Address                          | 203.0.113.100/24      | 203.0.113.100/24      |
-| Security Zone                       | untrust               | untrust               |
+| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| WAN Interface     | ge-0/0/0.0          | ge-0/0/0.0          |
+| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
+| Security Zone     | untrust             | untrust             |
 
-| **Virtual Tunnel Interface (VTI)**  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| Tunnel interface                    | st0.1                 | st0.2                 |
-| IP Address                          | 169.254.250.1/31      | 169.254.250.3/31      |
-| Security Zone                       | cloudflare            | cloudflare            |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ---------------------------------- | ------------------- | ------------------- |
+| Tunnel interface                   | st0.1               | st0.2               |
+| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
+| Security Zone                      | cloudflare          | cloudflare          |
 
-| **LAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ----------------------------------- | --------------------- | --------------------- |
-| LAN Interface                       | ge-0/0/1.0            | ge-0/0/1.0            |
-| IP Address                          | 192.168.125.1/24      | 192.168.125.1/24      |
-| Security Zone                       | trust                 | trust                 |
+| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| LAN Interface     | ge-0/0/1.0          | ge-0/0/1.0          |
+| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
+| Security Zone     | trust               | trust               |
 
 ### HPE Juniper Networking SRX Object Names
 
-| **Element**                          | **Object Hierarchy**             | **Name**                        |
-| ------------------------------------ | -------------------------------- | ------------------------------- |
-| Security Zone - Trust                | [ security zones security-zone ] | trust                           |
-| Security Zone - Untrust              | [ security zones security-zone ] | untrust                         |
-| Security Zone - Cloudflare WAN       | [ security zones security-zone ] | cloudflare                      |
-| IKE Proposal (only one required)     | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
-| IKE Policy - Tunnel 1                | [ security ike policy ]          | cf-wan-ike-pol-01               |
-| IKE Policy - Tunnel 2                | [ security ike policy ]          | cf-wan-ike-pol-02               |
-| IKE Gateway - Tunnel 1               | [ security ike gateway ]         | cf-wan-ike-gw-01                |
-| IKE Gateway - Tunnel 2               | [ security ike gateway ]         | cf-wan-ike-gw-02                |
-| IPsec Proposal (only one required)   | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
-| IPsec Policy (only one required)     | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
-| IPsec Tunnel - Tunnel 1              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
-| IPsec Tunnel - Tunnel 2              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
+| **Element**                        | **Object Hierarchy**             | **Name**                        |
+| ---------------------------------- | -------------------------------- | ------------------------------- |
+| Security Zone - Trust              | [ security zones security-zone ] | trust                           |
+| Security Zone - Untrust            | [ security zones security-zone ] | untrust                         |
+| Security Zone - Cloudflare WAN     | [ security zones security-zone ] | cloudflare                      |
+| IKE Proposal (only one required)   | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
+| IKE Policy - Tunnel 1              | [ security ike policy ]          | cf-wan-ike-pol-01               |
+| IKE Policy - Tunnel 2              | [ security ike policy ]          | cf-wan-ike-pol-02               |
+| IKE Gateway - Tunnel 1             | [ security ike gateway ]         | cf-wan-ike-gw-01                |
+| IKE Gateway - Tunnel 2             | [ security ike gateway ]         | cf-wan-ike-gw-02                |
+| IPsec Proposal (only one required) | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
+| IPsec Policy (only one required)   | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
+| IPsec Tunnel - Tunnel 1            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
+| IPsec Tunnel - Tunnel 2            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
 
 ## Assumptions
 
@@ -216,7 +216,7 @@ Configure the following:
 Define an IKE Proposal with the following settings:
 
 | **Attribute**            | **Value**       |
-| ------------------------ | ----------------|
+| ------------------------ | --------------- |
 | authentication-method    | pre-shared-keys |
 | dh-group                 | group20         |
 | authentication-algorithm | sha256          |
@@ -356,13 +356,13 @@ _Perform in Configuration Mode_
 
 The following example allows all source & destination IPs, ports, and protocols/services between `cloudflare` and `trust` as well as between `trust` and `cloudflare`.
 
-| **Attribute**            | **Value**     |
-| ------------------------ | ------------- |
-| source-address           | any           |
-| destination-address      | any           |
-| application              | any           |
-| action                   | permit        |
-| log                      | session-close |
+| **Attribute**       | **Value**     |
+| ------------------- | ------------- |
+| source-address      | any           |
+| destination-address | any           |
+| application         | any           |
+| action              | permit        |
+| log                 | session-close |
 
 ```txt
 set security policies from-zone cloudflare to-zone trust policy cloudflare-to-trust-permit match source-address any
@@ -389,18 +389,18 @@ This example assumes traffic originating from 192.168.125.0/24 (ingress interfac
 Implementing Filter-Based Forwarding (FBF) requires four steps:
 
 1. Create a Forwarding Routing Instance
-    - Think of the Routing Instance as a "bucket" containing an alternate routing table
-    - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
+   - Think of the Routing Instance as a "bucket" containing an alternate routing table
+   - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
 2. Create a Firewall Filter
-    - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
-    - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
+   - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
+   - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
 3. Configure the RIB Group and Bind Routes
-    - Think of this as the "bridge" that copies interface routes to the "bucket"
-    - The Routing Instance is not part of the default routing table.
-    - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
+   - Think of this as the "bridge" that copies interface routes to the "bucket"
+   - The Routing Instance is not part of the default routing table.
+   - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
 4. Apply the Firewall Filter to the ingress traffic interface(s)
-    - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
-    - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
+   - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
+   - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
 
 #### Define a Routing Instance
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
index 51757cc2dd241e8..e64b5b02cda5941 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
@@ -11,15 +11,16 @@ This tutorial shows how to configure IPsec (Internet Protocol Security) between
 You need a pre-shared key to establish the IPsec tunnel. You can use the following code to create a random key:
 
 ```js
-		const a = new Uint8Array(48);
-		crypto.getRandomValues(a);
-		let base64String = btoa(String.fromCharCode.apply(null, a));
+const a = new Uint8Array(48);
+crypto.getRandomValues(a);
+let base64String = btoa(String.fromCharCode.apply(null, a));
 
-		base64String = base64String.replace(/\+/g, '')
-								   .replace(/\//g, '')
-								   .replace(/=/g, '');
+base64String = base64String
+	.replace(/\+/g, "")
+	.replace(/\//g, "")
+	.replace(/=/g, "");
 
-		console.log(base64String.substring(0, 32));
+console.log(base64String.substring(0, 32));
 ```
 
 :::caution
@@ -58,28 +59,28 @@ You can try this code in the [Workers playground](https://workers.cloudflare.com
    - **Dynamic routing gateways (DRG)**: Select the DRG you created in step 2.
    - **Routes to your on-premises network**: Enter a CIDR (Classless Inter-Domain Routing) range you want to route to Cloudflare WAN.
    - **Tunnel 1**
-      - **Name**: Enter a name.
-      - Select **Provide custom shared secret**.
-      - Enter the **pre-shared key** you created in the Prerequisites section.
-      - **IKE (Internet Key Exchange) version**: **IKEv2**
-      - **Routing type**: **Static routing**
-      - **IPv4 inside tunnel interface - CPE**:  Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
-      - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
-         1. Select **Show advanced options**
-         2. Select **Phase one (ISAKMP) configuration**
-            - Select **Set custom configurations**
-            - **Custom encryption algorithm**: **AES_256_CBC**
-            - **Custom authentication algorithm**: **SHA2_256**
-            - **Custom Diffie-Hellman group**: **GROUP20**
-            - **IKE session key lifetime in seconds**: **86400**
-         3. Select **Phase two (IPsec) configuration**
-            - Select **Set custom configurations**
-            - **Custom encryption algorithm**: **AES_256_CBC**
-            - **HMAC (Hash-based Message Authentication Code)_SHA2_256_128**: **HMAC_SHA2_256_128**
-            - **IPsec session key lifetime in seconds**: **28800**
-            - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
-    - **Tunnel 2**
-      - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
+     - **Name**: Enter a name.
+     - Select **Provide custom shared secret**.
+     - Enter the **pre-shared key** you created in the Prerequisites section.
+     - **IKE (Internet Key Exchange) version**: **IKEv2**
+     - **Routing type**: **Static routing**
+     - **IPv4 inside tunnel interface - CPE**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
+     - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
+       1. Select **Show advanced options**
+       2. Select **Phase one (ISAKMP) configuration**
+          - Select **Set custom configurations**
+          - **Custom encryption algorithm**: **AES_256_CBC**
+          - **Custom authentication algorithm**: **SHA2_256**
+          - **Custom Diffie-Hellman group**: **GROUP20**
+          - **IKE session key lifetime in seconds**: **86400**
+       3. Select **Phase two (IPsec) configuration**
+          - Select **Set custom configurations**
+          - **Custom encryption algorithm**: **AES_256_CBC**
+          - **HMAC (Hash-based Message Authentication Code)\_SHA2_256_128**: **HMAC_SHA2_256_128**
+          - **IPsec session key lifetime in seconds**: **28800**
+          - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
+   - **Tunnel 2**
+     - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
 4. Select **Create IPsec connection**
 
 ## Cloudflare WAN
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
index 34b5e4bec7deae3..81fe83217616d1d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ## Test Environment
 
-| **Field**                          | **Value**                                  |
-| ---------------------------------- | ------------------------------------------ |
-| Vendor                             | Palo Alto Networks                         |
-| Model                              | PA-440                                     |
-| Release                            | PAN-OS 11.2.8                              |
-| Date Tested                        | March 2026                                 |
+| **Field**   | **Value**          |
+| ----------- | ------------------ |
+| Vendor      | Palo Alto Networks |
+| Model       | PA-440             |
+| Release     | PAN-OS 11.2.8      |
+| Date Tested | March 2026         |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**                                  |
-| ---------------------------------- | ------------------------------------------ |
-| Traffic Selection Criteria         | Route-Based VPN                            |
-| Routing                            | Static                                     |
-| Redundant Tunnels                  | Yes                                        |
-| Tunnel Load Balancing              | Active/Active                              |
-| IKE Version                        | IKEv2                                      |
-| Authentication                     | Pre-Shared Key                             |
-| Anti-Replay Protection             | Disabled                                   |
-| NAT Traversal (NAT-T)              | Not Tested                                 |
-| NAT-T Port                         | Not Applicable                             |
-| Phase 1 - DH-Group                 | Group 20                                   |
-| Phase 1 - Encryption               | AES-256-CBC                                |
-| Phase 1 - Authentication/Integrity | SHA-256                                    |
-| Phase 2 - DH-Group                 | Group 20                                   |
-| Phase 2 - Transport                | ESP                                        |
-| Phase 2 - Encryption               | AES-256-CBC                                |
+| **Field**                          | **Value**       |
+| ---------------------------------- | --------------- |
+| Traffic Selection Criteria         | Route-Based VPN |
+| Routing                            | Static          |
+| Redundant Tunnels                  | Yes             |
+| Tunnel Load Balancing              | Active/Active   |
+| IKE Version                        | IKEv2           |
+| Authentication                     | Pre-Shared Key  |
+| Anti-Replay Protection             | Disabled        |
+| NAT Traversal (NAT-T)              | Not Tested      |
+| NAT-T Port                         | Not Applicable  |
+| Phase 1 - DH-Group                 | Group 20        |
+| Phase 1 - Encryption               | AES-256-CBC     |
+| Phase 1 - Authentication/Integrity | SHA-256         |
+| Phase 2 - DH-Group                 | Group 20        |
+| Phase 2 - Transport                | ESP             |
+| Phase 2 - Encryption               | AES-256-CBC     |
 
 ## Cloudflare WAN and Palo Alto Networks NGFW - Configuration Settings
 
@@ -46,85 +46,85 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_01                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 162.159.135.1                                  |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_01     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.0/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 162.159.135.1     |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`    |
-| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| Name (required)                      | CF_WAN_TUN_02                                  |
-| Description                          | ---                                            |
-| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
-| IPv6 Interface Address               | ---                                            |
-| Customer Endpoint                    | 203.0.113.100                                  |
-| Cloudflare Endpoint                  | 172.64.135.1                                   |
-| Tunnel health checks                 | True                                           |
-| Rate                                 | Medium                                         |
-| **Type**                             | **Request**                                    |
-| **Direction**                        | **Bidirectional**                              |
-| Target                               | Default                                        |
-| ---                                  | ---                                            |
-| Turn on replay protection            | False                                          |
-| **Automatic return routing**         | **True**                                       |
+| **Attribute**                     | **Value/Address** |
+| --------------------------------- | ----------------- |
+| Name (required)                   | CF_WAN_TUN_02     |
+| Description                       | ---               |
+| IPv4 Interface Address (required) | 169.254.250.2/31  |
+| IPv6 Interface Address            | ---               |
+| Customer Endpoint                 | 203.0.113.100     |
+| Cloudflare Endpoint               | 172.64.135.1      |
+| Tunnel health checks              | True              |
+| Rate                              | Medium            |
+| **Type**                          | **Request**       |
+| **Direction**                     | **Bidirectional** |
+| Target                            | Default           |
+| ---                               | ---               |
+| Turn on replay protection         | False             |
+| **Automatic return routing**      | **True**          |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**                        | **Value/Address**                              |
-| ------------------------------------ | ---------------------------------------------- |
-| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`    |
-| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
+| **Attribute**  | **Value/Address**                           |
+| -------------- | ------------------------------------------- |
+| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
+| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
 
 ## Customer Premise Equipment - Palo Alto Networks
 
-| **WAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| WAN Interface                      | ethernet1/1           | ethernet1/1           |
-| IP Address                         | 203.0.113.100/24      | 203.0.113.100/24      |
-| Security Zone                      | untrust               | untrust               |
+| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| WAN Interface     | ethernet1/1         | ethernet1/1         |
+| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
+| Security Zone     | untrust             | untrust             |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| Tunnel interface                   | tunnel.1              | tunnel.2              |
-| IP Address                         | 169.254.250.1/31      | 169.254.250.3/31      |
-| Security Zone                      | cloudflare            | cloudflare            |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ---------------------------------- | ------------------- | ------------------- |
+| Tunnel interface                   | tunnel.1            | tunnel.2            |
+| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
+| Security Zone                      | cloudflare          | cloudflare          |
 
-| **LAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
-| ---------------------------------- | --------------------- | --------------------- |
-| LAN Interface                      | ethernet1/2           | ethernet1/2           |
-| IP Address                         | 192.168.125.1/24      | 192.168.125.1/24      |
-| Security Zone                      | trust                 | trust                 |
+| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
+| ----------------- | ------------------- | ------------------- |
+| LAN Interface     | ethernet1/2         | ethernet1/2         |
+| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
+| Security Zone     | trust               | trust               |
 
 ### Palo Alto Networks NGFW Object Names
 
-| **Role**                           | **Label/Name**            | **Address**                 |
-| ---------------------------------- | ------------------------- | --------------------------- |
-| CPE Security Zone - Trust          | Zone                      | trust                       |
-| CPE Security Zone - Untrust        | Zone                      | untrust                     |
-| CPE Security Zone - Cloudflare WAN | Zone                      | cloudflare                  |
-| CPE IKE Crypto Profile Name        | IKE Crypto Profile        | ike-aes256cbc-sha256-dh20   |
-| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile      | ipsec-aes256cbc-sha256-dh20 |
+| **Role**                           | **Label/Name**       | **Address**                 |
+| ---------------------------------- | -------------------- | --------------------------- |
+| CPE Security Zone - Trust          | Zone                 | trust                       |
+| CPE Security Zone - Untrust        | Zone                 | untrust                     |
+| CPE Security Zone - Cloudflare WAN | Zone                 | cloudflare                  |
+| CPE IKE Crypto Profile Name        | IKE Crypto Profile   | ike-aes256cbc-sha256-dh20   |
+| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile | ipsec-aes256cbc-sha256-dh20 |
 
 ## Assumptions
 
@@ -271,12 +271,12 @@ Repeat steps for tunnel 2
 
 Define an IKE Crypto Profile with the following settings:
 
-| **Attribute**   | **Value**   |
-| --------------- | ----------- |
-| hash            | sha256      |
-| dh-group        | group20     |
-| encryption      | aes-256-cbc |
-| lifetime hours  | 8           |
+| **Attribute**  | **Value**   |
+| -------------- | ----------- |
+| hash           | sha256      |
+| dh-group       | group20     |
+| encryption     | aes-256-cbc |
+| lifetime hours | 8           |
 
 ###### CLI
 
@@ -639,10 +639,10 @@ Gateway ID      Peer-Address       Gateway Name       Role SN    Algorithm
 
 ```txt
 IKEv2 IPSec Child SAs
-Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST              
-------------                   ----     ------                     --       ------   ---- -------  -------- -----    --              
-cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature           
-cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature           
+Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST
+------------                   ----     ------                     --       ------   ---- -------  -------- -----    --
+cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature
+cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature
 
 Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 ```
@@ -652,7 +652,7 @@ Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 Use [test](https://docs.paloaltonetworks.com/network-security/ipsec-vpn/administration/troubleshooting/troubleshooting-site-to-site-vpn-issues-using-cli) commands to force Phase 1 and Phase 2 security associations:
 
 ```txt
-admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01 
+admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01
 
 Start time: Mar.30 21:23:23
 Initiate 1 IKE SA.
@@ -664,7 +664,7 @@ Initiate 1 IKE SA.
 ```
 
 ```txt
-admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01 
+admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01
 
 Start time: Mar.30 21:26:50
 Initiate 1 IPSec SA for tunnel cf-wan-ipsec-tun-01.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
index 7aff703eec495a2..20b793688afdc79 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
@@ -11,7 +11,6 @@ import { Render } from "~/components";
 This tutorial shows you how to use Cloudflare WAN (formerly Magic WAN) with the following versions of the Sophos Firewall:
 
 - **Sophos form factor tested:**
-
   - Sophos Firewall XGS and XG series hardware
   - Sophos Firewall virtual appliance on VMware
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
index 4a09ab7e89822a7..29458f09ea57950 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
@@ -195,7 +195,7 @@ Once the Edge device is added, you should land on the **Device** tab.
 
 #### User Defined WAN Link
 
-Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result,  the WAN Link must be specified.
+Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result, the WAN Link must be specified.
 
 ![Note the indicator next to GE3.](~/assets/images/cloudflare-wan/third-party/velocloud/image2.png)
 
@@ -215,7 +215,7 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 5. Select the **Network Service** defined earlier. For example, `Magic_WAN_vc-edge-03`.
 6. In the **Action** column, select the **+** button, and configure the following options:
    1. **Public WAN Link**: Choose the Public WAN Link (refer to User-Defined WAN Link)
-   2. **Local Identification Type**: *FQDN*
+   2. **Local Identification Type**: _FQDN_
    3. **Local Identification**: Enter the FQDN specified when configuring Cloudflare WAN IPsec tunnels through the Custom FQDN IKE ID API endpoint.
    4. **PSK**: Enter the Pre-Shared Key. Ensure you use the same PSK for both Cloudflare WAN IPsec tunnels.
    5. **Destination Primary Public IP**: Pre-populated from the Network Service defined earlier.
@@ -227,8 +227,8 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 
 Configure the **Site Subnets** to facilitate:
 
-* Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
-* Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
+- Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
+- Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
 
 1. Go to **Configure** > **Network Services**.
 2. Expand the **Non SD-WAN Destinations through Edge** section.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
index fae8475cf53be20..948613cef1331b1 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
@@ -37,32 +37,32 @@ To create a Secure Internet Gateway (SIG) using vManage:
 1. From **Cisco vManage** under **Configuration**, select **Generic** and **Add Tunnel**.
 2. The table below shows the setting fields and their options.
 
-| Setting             | Type/Detail                               |
-| ------------------- | ----------------------------------------- |
+| Setting             | Type/Detail                           |
+| ------------------- | ------------------------------------- |
 | **Global Template** | Factory_Default_Global_CISCO_Template |
-| **Cisco Banner**    | Factory_Default_Retail_Banner          |
-| **Policy**          | Branch-Local-Policy                       |
+| **Cisco Banner**    | Factory_Default_Retail_Banner         |
+| **Policy**          | Branch-Local-Policy                   |
 
 **Transport & Management VPN settings**
 
-| Setting                           | Type/Detail                         |
-| --------------------------------- | ----------------------------------- |
-| **Cisco VPN 0**                   | GCP-Branch-VPN0                     |
-| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template             |
-| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC     |
-| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface                  |
-| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01 |
+| Setting                           | Type/Detail                     |
+| --------------------------------- | ------------------------------- |
+| **Cisco VPN 0**                   | GCP-Branch-VPN0                 |
+| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template         |
+| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC |
+| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface              |
+| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01  |
 
 **Basic Information settings**
 
-| Setting            | Type/Detail                                 |
-| ------------------ | ------------------------------------------- |
+| Setting            | Type/Detail                             |
+| ------------------ | --------------------------------------- |
 | **Cisco System**   | Default_BootStrap_Cisco_System_Template |
-| **Cisco Logging**  | Default_Logging_Cisco_V01                |
-| **Cisco AAA**      | AWS-Branch-AAA-Template                     |
-| **Cisco BFD**      | Default_BFD_Cisco-V01                     |
-| **Cisco OMP**      | Default_AWS_TGW_CSR_OMP_IPv46_...     |
-| **Cisco Security** | Default_Security_Cisco_V01               |
+| **Cisco Logging**  | Default_Logging_Cisco_V01               |
+| **Cisco AAA**      | AWS-Branch-AAA-Template                 |
+| **Cisco BFD**      | Default_BFD_Cisco-V01                   |
+| **Cisco OMP**      | Default*AWS_TGW_CSR_OMP_IPv46*...       |
+| **Cisco Security** | Default_Security_Cisco_V01              |
 
 When creating the Feature Template, you can choose values that apply globally or that are device specific. For example, the **Tunnel Source IP Address**, **Interface Name** and fields from **Update Tunnel** are device specific and should be chosen accordingly.
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
index 017633fb496566a..82717dcc274bcdf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
@@ -22,19 +22,19 @@ Before proceeding, ensure that you have the anycast IPs assigned to your account
 ### IPsec tunnels
 
 1. Follow the <a href={props.addTunnelsUrl}>Add tunnels</a> instructions to create the required IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
-	- **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
-	- **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
-	- **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
-	- **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
-	- **Health check rate**: _Medium_.
-	- **Health check type**: _Request_.
-	- **Health check direction**: _Bidirectional_.
-	- **Health check target**: _Default_.
-	- **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
-	- **Replay protection**: Do not check the box, to keep this disabled.
+   - **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
+   - **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
+   - **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
+   - **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
+   - **Health check rate**: _Medium_.
+   - **Health check type**: _Request_.
+   - **Health check direction**: _Bidirectional_.
+   - **Health check target**: _Default_.
+   - **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
+   - **Replay protection**: Do not check the box, to keep this disabled.
 
 2. After you create your tunnel, the Cloudflare dashboard will load a list of tunnels set up for your account. Select the IPsec tunnel you have just created, and check the following setting:
-	- **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
+   - **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
 
 ### Static routes
 
@@ -214,4 +214,4 @@ IKE keepalive:
 [Status]: OK
 
 [Next send]: 1 sec after
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
index 7639f10f685149d..e49fb208f2bd10f 100644
--- a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
@@ -36,13 +36,13 @@ On-premises network and security appliances require manual firmware updates, pat
 
 ## Compare WAN approaches
 
-| | Traditional WAN (MPLS) | SD-WAN | Cloudflare One |
-|---|---|---|---|
-| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing. | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling. |
-| **Cost model** | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment. | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model. |
-| **Agility** | Weeks to months to provision new circuits. Rigid topology changes. | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection. |
-| **Security** | Security applied at central data center or per-site firewalls. | Varies by vendor. Some offer integrated security, others require separate appliances. | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
-| **Management** | Separate management for WAN circuits, routers, and security appliances. | Single console for WAN, but security often managed separately. | Single dashboard for network connectivity, routing, firewall rules, and security policies. |
+|                 | Traditional WAN (MPLS)                                                                                | SD-WAN                                                                                             | Cloudflare One                                                                                                   |
+| --------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing.   | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling.  |
+| **Cost model**  | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment.            | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model.                    |
+| **Agility**     | Weeks to months to provision new circuits. Rigid topology changes.                                    | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection.                              |
+| **Security**    | Security applied at central data center or per-site firewalls.                                        | Varies by vendor. Some offer integrated security, others require separate appliances.              | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
+| **Management**  | Separate management for WAN circuits, routers, and security appliances.                               | Single console for WAN, but security often managed separately.                                     | Single dashboard for network connectivity, routing, firewall rules, and security policies.                       |
 
 ## Plan your migration
 
@@ -78,7 +78,11 @@ Organizations that start with Cloudflare WAN for site-to-site connectivity and p
 
 ## Next steps
 
-- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the Cloudflare One Appliance or a third-party device.
-- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all Cloudflare One connectivity options and choose the right combination for your deployment.
-- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported on-ramps for connecting your networks.
+- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the
+  Cloudflare One Appliance or a third-party device.
+- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all
+  Cloudflare One connectivity options and choose the right combination for your
+  deployment.
+- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported
+  on-ramps for connecting your networks.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the architecture of Cloudflare One as a SASE platform.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
index 233eb735ada557b..67d32f2a51ebbf2 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
@@ -21,7 +21,9 @@ params:
 
 import { Render } from "~/components";
 
-<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress traffic.
+<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web
+Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress
+traffic.
 
 You can apply network and HTTP Gateway policies alongside <a href="/cloudflare-network-firewall/">Cloudflare Network Firewall</a> policies (for L3/4 traffic filtering) to Internet-bound traffic or private traffic entering the Cloudflare network through Cloudflare WAN (formerly Magic WAN). Additionally, you can configure Gateway to [resolve DNS queries](#dns-filtering) from Cloudflare WAN.
 
@@ -128,9 +130,9 @@ Source ports are fixed to `1024`-`65535` and cannot be overridden.
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
 
 ## Test Gateway integration
 
@@ -141,6 +143,7 @@ If you are still testing Gateway and Cloudflare is not your default route, confi
 Confirm there is an entry for the test in <a href={props.gatewayLogsURL}>HTTP Gateway Activity Logs</a>.
 
 Verify the following details:
+
 - **Destination IP**: Should be the public IP address of `ifconfig.me`.
 - **Source IP**: Should be the private (WAN) address of the host with the browser.
 - **Outbound connection**: Should be sourced from a Cloudflare WAN IP address, not any public IP address that Cloudflare might be advertising on your behalf.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
index ca49d64696b2380..05ee41c0b931606 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
@@ -1,8 +1,8 @@
 ---
- {}
+{}
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) provides site-to-site connectivity and packet-level security through [Cloudflare Network Firewall](/cloudflare-network-firewall/). The Cloudflare One integrations below extend that foundation with identity-aware security — user-level access policies through [Cloudflare Access](/cloudflare-one/access-controls/), secure Internet egress through [Cloudflare Gateway](/cloudflare-one/traffic-policies/), and device-level routing through the [Cloudflare One Client (formerly WARP)](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/).
 
@@ -10,4 +10,4 @@ Review the tutorials to learn how to use Cloudflare WAN with these Cloudflare On
 
 <DirectoryListing />
 
-If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
\ No newline at end of file
+If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
index 00c200fe13cb9b3..f80c67cfd5709c5 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
@@ -19,7 +19,9 @@ Cloudflare WAN carries three types of traffic, and different security services a
 
 ### Cloudflare Network Firewall
 
-<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides packet-level filtering at layers 3 and 4. You define allow or block rules based on IP addresses, ports, and protocols.
+<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides
+packet-level filtering at layers 3 and 4. You define allow or block rules based
+on IP addresses, ports, and protocols.
 
 - **Applies to**: inbound, outbound, and east-west traffic
 - **Included with**: Cloudflare WAN by default for [standard features](/cloudflare-network-firewall/plans/)
@@ -74,16 +76,16 @@ AI visibility is not a separate inline security service. It is an analytics feat
 
 ## Use-case mapping
 
-| Traffic scenario | Recommended services |
-|---|---|
-| Block traffic between sites by IP, port, or protocol | Network Firewall |
-| Filter DNS queries from branch offices | Gateway DNS policies |
-| Block malware downloads from branch offices | Gateway HTTP policies |
-| Prevent sensitive data uploads to the Internet | DLP (via Gateway HTTP policies) |
-| Isolate risky web browsing from branch users | Browser Isolation (via Gateway HTTP policies) |
-| Detect and block unsanctioned SaaS applications | CASB + Gateway HTTP policies |
-| Monitor employee AI tool usage | AI Security Report (via Gateway) |
-| Protect against DDoS on customer-owned IPs | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
+| Traffic scenario                                     | Recommended services                                          |
+| ---------------------------------------------------- | ------------------------------------------------------------- |
+| Block traffic between sites by IP, port, or protocol | Network Firewall                                              |
+| Filter DNS queries from branch offices               | Gateway DNS policies                                          |
+| Block malware downloads from branch offices          | Gateway HTTP policies                                         |
+| Prevent sensitive data uploads to the Internet       | DLP (via Gateway HTTP policies)                               |
+| Isolate risky web browsing from branch users         | Browser Isolation (via Gateway HTTP policies)                 |
+| Detect and block unsanctioned SaaS applications      | CASB + Gateway HTTP policies                                  |
+| Monitor employee AI tool usage                       | AI Security Report (via Gateway)                              |
+| Protect against DDoS on customer-owned IPs           | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
 
 ## How services compose
 
@@ -99,7 +101,12 @@ This means you can layer multiple security services on the same traffic flow wit
 
 ## Next steps
 
-- <a href={props.gatewaySetupURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a>: Detailed setup guide for Gateway integration with WAN traffic.
-- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure packet-level filtering rules.
+- <a href={props.gatewaySetupURL}>
+  	Connect to Cloudflare Gateway with Cloudflare WAN
+  </a>
+  : Detailed setup guide for Gateway integration with WAN traffic.
+- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure
+  packet-level filtering rules.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the full architecture of Cloudflare One as a SASE platform.
-- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your migration from traditional WAN to Cloudflare.
+- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your
+  migration from traditional WAN to Cloudflare.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
index 41ddc29de0c6c15..ef33bc683575a8e 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
@@ -8,7 +8,7 @@ params:
   - arrURL
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Cloudflare WAN (formerly Magic WAN) can work together with <a href="/cloudflare-one/networks/connectors/cloudflare-tunnel/">Cloudflare Tunnel</a> to provide easy access between your networks and applications.
 
@@ -30,12 +30,12 @@ To route the same prefix to different destinations, use separate [virtual networ
 
 Cloudflare reserves the following IP ranges for Zero Trust services:
 
-| IP range | Purpose |
-| --- | --- |
-| `100.64.0.0/12` | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/) |
-| `100.96.0.0/12` | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
-| `100.80.0.0/16` | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/) |
-| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/) |
+| IP range         | Purpose                                                                                              |
+| ---------------- | ---------------------------------------------------------------------------------------------------- |
+| `100.64.0.0/12`  | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/)       |
+| `100.96.0.0/12`  | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
+| `100.80.0.0/16`  | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/)             |
+| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/)                                           |
 
 Do not configure routes that overlap with these reserved ranges.
 
@@ -51,7 +51,8 @@ Longest-prefix-match routing is the default route selection method. Other mechan
 
 ### Automatic Return Routing (ARR)
 
-<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for return traffic.
+<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for
+return traffic.
 
 When ARR is enabled:
 
@@ -88,7 +89,6 @@ To verify that a `cloudflared` tunnel works correctly with your Cloudflare WAN c
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
-
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
index 02de971802f7fa9..425405bded13584 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
@@ -73,9 +73,9 @@ You must log out and log back in with at least one device to ensure the configur
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL
-		}}
-	/>
+		tracerouteURL: props.tracerouteURL,
+	}}
+/>
 
 ## Double encapsulation
 
@@ -91,7 +91,8 @@ To learn which IP addresses and UDP ports you should exclude to accomplish this,
 	file="mconn/network-options/app-aware-policies/warp-traffic"
 	product="networking-services"
 	params={{
-		warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
+		warpFirewallURL:
+			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/",
 	}}
 />
 
diff --git a/src/content/partials/networking-services/cni-product-use-cases.mdx b/src/content/partials/networking-services/cni-product-use-cases.mdx
index 1e1079f2de90aec..5d902dd611989d8 100644
--- a/src/content/partials/networking-services/cni-product-use-cases.mdx
+++ b/src/content/partials/networking-services/cni-product-use-cases.mdx
@@ -4,13 +4,12 @@
 
 CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications.
 
-
-|  | Dataplane v1 | Dataplane v2 |
-| ---- | ---- | ---- |
-| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Cloudflare WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
-| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. |
-| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
+|                                                                                                                                                                                                         | Dataplane v1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Dataplane v2                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Supported.                                                                                                                                                                |
+| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare.                                              | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
+| **Cloudflare WAN and Zero Trust** <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds.                      | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
+| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence).                                                                                                             | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP.                                                                                                                                                                                                                                                                              | Not supported.                                                                                                                                                            |
+| **Application Security and Performance** <br /> Improve the performance and security of your web applications                                                                                           | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
 
 For more details refer to the [prerequisites section](/network-interconnect/get-started/#prerequisites).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
index 4b05caa926f685e..3776c9a7c06a1bd 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
@@ -104,4 +104,5 @@ curl https://api.cloudflare.com/client/v4/graphql \
 ```
 
 [^1]: For details, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
-[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
+
+[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
index 0471540ec9e7cb8..40149b5bcec5005 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
@@ -17,13 +17,13 @@ You need the following to query endpoint health check data:
 
 The following parameters are some of the most common ones in the `filter` object:
 
-| Parameter | Description |
-| :---- | :---- |
-| `date_geq` | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
-| `date_leq` | _(Optional)_ End date for the query. Uses the same format as `date_geq`. |
-| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions. |
-| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format. |
-| `limit` | Maximum number of result groups to return. |
+| Parameter      | Description                                                                                                                                                                                                                                             |
+| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `date_geq`     | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
+| `date_leq`     | _(Optional)_ End date for the query. Uses the same format as `date_geq`.                                                                                                                                                                                |
+| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions.                                                                                                  |
+| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format.                                                                                                                                                                                                          |
+| `limit`        | Maximum number of result groups to return.                                                                                                                                                                                                              |
 
 You can also filter on any dimension listed in the [Available dimensions](#available-dimensions) table. Append an operator suffix to the dimension name to create a filter — for example, `endpoint_in` to filter by a list of endpoints, or `checkType_neq` to exclude a specific check type. Using a dimension name without a suffix filters for equality. For the full list of supported operators, refer to [Filtering](/analytics/graphql-api/features/filtering/).
 
@@ -31,28 +31,28 @@ You can also filter on any dimension listed in the [Available dimensions](#avail
 
 You can query the following dimensions in the `dimensions` field:
 
-| Dimension | Description |
-| :---- | :---- |
-| `checkId` | The unique ID of the configured health check. |
-| `checkType` | The type of health check (for example, `icmp`). |
-| `endpoint` | The IP address of the endpoint being checked. |
-| `name` | The name assigned to the health check when configured (may be empty if not set). |
-| `date` | Event timestamp truncated to the day. |
-| `datetime` | Full event timestamp. |
-| `datetimeMinute` | Event timestamp truncated to the minute. |
-| `datetimeFiveMinutes` | Event timestamp truncated to five-minute intervals. |
-| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals. |
-| `datetimeHalfOfHour` | Event timestamp truncated to 30-minute intervals. |
-| `datetimeHour` | Event timestamp truncated to the hour. |
+| Dimension                | Description                                                                      |
+| :----------------------- | :------------------------------------------------------------------------------- |
+| `checkId`                | The unique ID of the configured health check.                                    |
+| `checkType`              | The type of health check (for example, `icmp`).                                  |
+| `endpoint`               | The IP address of the endpoint being checked.                                    |
+| `name`                   | The name assigned to the health check when configured (may be empty if not set). |
+| `date`                   | Event timestamp truncated to the day.                                            |
+| `datetime`               | Full event timestamp.                                                            |
+| `datetimeMinute`         | Event timestamp truncated to the minute.                                         |
+| `datetimeFiveMinutes`    | Event timestamp truncated to five-minute intervals.                              |
+| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals.                                |
+| `datetimeHalfOfHour`     | Event timestamp truncated to 30-minute intervals.                                |
+| `datetimeHour`           | Event timestamp truncated to the hour.                                           |
 
 ### Available metrics
 
-| Metric | Description |
-| :---- | :---- |
-| `count` | Total number of health check events in the group. |
-| `sum.total` | Total number of health check probes sent. |
-| `sum.failures` | Number of failed health check probes. |
-| `avg.lossPercentage` | Average calculated loss percentage (0-100). |
+| Metric               | Description                                       |
+| :------------------- | :------------------------------------------------ |
+| `count`              | Total number of health check events in the group. |
+| `sum.total`          | Total number of health check probes sent.         |
+| `sum.failures`       | Number of failed health check probes.             |
+| `avg.lossPercentage` | Average calculated loss percentage (0-100).       |
 
 ### API call
 
@@ -111,43 +111,43 @@ https://api.cloudflare.com/client/v4/graphql \
 
 ```json
 {
-  "data": {
-    "viewer": {
-      "accounts": [
-        {
-          "magicEndpointHealthCheckAdaptiveGroups": [
-            {
-              "count": 288,
-              "dimensions": {
-                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-                "checkType": "icmp",
-                "datetimeFiveMinutes": "2026-01-21T12:00:00Z",
-                "endpoint": "103.21.244.100"
-              },
-              "sum": {
-                "failures": 0,
-                "total": 288
-              }
-            },
-            {
-              "count": 288,
-              "dimensions": {
-                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-                "checkType": "icmp",
-                "datetimeFiveMinutes": "2026-01-21T12:05:00Z",
-                "endpoint": "103.21.244.100"
-              },
-              "sum": {
-                "failures": 2,
-                "total": 288
-              }
-            }
-          ]
-        }
-      ]
-    }
-  },
-  "errors": null
+	"data": {
+		"viewer": {
+			"accounts": [
+				{
+					"magicEndpointHealthCheckAdaptiveGroups": [
+						{
+							"count": 288,
+							"dimensions": {
+								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+								"checkType": "icmp",
+								"datetimeFiveMinutes": "2026-01-21T12:00:00Z",
+								"endpoint": "103.21.244.100"
+							},
+							"sum": {
+								"failures": 0,
+								"total": 288
+							}
+						},
+						{
+							"count": 288,
+							"dimensions": {
+								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+								"checkType": "icmp",
+								"datetimeFiveMinutes": "2026-01-21T12:05:00Z",
+								"endpoint": "103.21.244.100"
+							},
+							"sum": {
+								"failures": 2,
+								"total": 288
+							}
+						}
+					]
+				}
+			]
+		}
+	},
+	"errors": null
 }
 ```
 
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
index f224c2ab01efe75..f9f5e61e69a7e7b 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
@@ -97,4 +97,4 @@ https://api.cloudflare.com/client/v4/graphql \
 #=> }
 ```
 
-[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
+[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
diff --git a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
index 1240490c155138a..630b17ac37eb812 100644
--- a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
+++ b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
@@ -40,7 +40,7 @@ Authentication failures in Phase 1 indicate a PSK mismatch. To resolve:
 
 1. Go to **Connectors** and select your tunnel.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select **Generate new PSK**.
 3. Copy the new PSK exactly — do not add extra spaces or characters.
@@ -72,9 +72,9 @@ Disable anti-replay protection on your tunnel endpoint, or set the replay window
 
 #### Health check type incompatible with stateful firewall
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default *Reply* health check packets because no matching ICMP request exists in their session table.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default _Reply_ health check packets because no matching ICMP request exists in their session table.
 
-Change the health check type from *Reply* to *Request*. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
+Change the health check type from _Reply_ to _Request_. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
 
 #### ISP blocking health check return path
 
@@ -128,7 +128,7 @@ Use IPsec logs to monitor tunnel activity during the key-exchange phase of the I
 
 1. Go to the **Logpush** page.
 
-	<DashButton url="/?to=/:account/logs" />
+   <DashButton url="/?to=/:account/logs" />
 
 2. Select **Create a Logpush job**.
 3. Select **IPsec logs** as your dataset.
diff --git a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
index 01689291e53b1c2..57fe9ec9026d18b 100644
--- a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
+++ b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
@@ -12,8 +12,9 @@ If you are using a Cloudflare IP, you do not need to advertise your prefixes.
 You must [put the appropriate MSS clamps](#set-maximum-segment-size) in place before [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) changes are made. Failure to apply an MSS clamp can result in dropped packets and hard-to-debug connectivity issues.
 
 Also, when using [Cloudflare Network Interconnect](/magic-transit/network-interconnect/) with Magic Transit you must set the following MSS clamp sizes to accommodate additional overhead:
+
 - GRE tunnels over CNI with Dataplane v1: 1476 bytes
 - CNI with Dataplane v2 / CNI with Dataplane v1 with a maximum transmission unit (MTU) size of 1500 bytes handoff does not require an MSS clamp.
 
 MSS clamps are used to backhaul data from the data center where traffic is ingested (close to the end user) to the facility with the CNI link.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
index c10384b93e929ca..2eab7b7b67f803a 100644
--- a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
+++ b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
@@ -3,19 +3,19 @@ params:
   - mtLpCreateTunnel
   - mtLpStaticRoute
   - mtLpBgpPeering
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 To use Magic Transit, you need to own a publicly routable IP address block with a minimum size of `/24`. If you do not own a `/24` address block, you can use Magic Transit with a Cloudflare-owned IP address. This option is helpful if you do not meet the `/24` prefix length requirements or want to protect a smaller network.
 
 To protect your network with a Cloudflare IP address, contact your account manager. After you receive your IP address:
 
 - <a href={props.mtLpCreateTunnel}>Create a tunnel</a>.
-- <a href={props.mtLpStaticRoute}>Set up static routes</a> or <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
+- <a href={props.mtLpStaticRoute}>Set up static routes</a> or
+  <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
 - [Configure health checks](/magic-transit/network-health/run-endpoint-health-checks/).
 - Confirm you properly configured [tunnel](/magic-transit/network-health/update-tunnel-health-checks-frequency/) and endpoint health checks.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.
 
-When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
\ No newline at end of file
+When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
index 312b1d8e17bf88c..df51d0077eac1b3 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
@@ -5,11 +5,9 @@
 The MSS value depends on how your network is set up.
 
 - **Magic Transit ingress-only traffic (DSR):**
-
   - **On your edge router transit ports**: Set a TCP MSS clamp to a maximum of 1,436 bytes.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: Apply the MSS clamp on the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce the current value by 24 bytes.
 
 - **For Magic Transit ingress + egress traffic:**
-
   - **On the Magic Transit GRE tunnel internal interface**: Meaning where the Magic Transit egress traffic will traverse. Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 24 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
index ca0dc864b8bd976..9724b74d99a9784 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
@@ -5,11 +5,9 @@
 For IPsec tunnels, the value you need to specify depends on how your network is set up. The MSS clamping value is lower than for GRE tunnels because the physical interface sees IPsec-encrypted [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/), not TCP packets, and MSS clamping does not apply to those.
 
 - **Magic Transit ingress-only traffic (DSR):**
-
   - **On your edge router transit ports**: Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 140 bytes.
 
 - **Magic Transit ingress + egress traffic:**
-
   - **On your edge router**: Apply this on your Magic Transit IPsec tunnel internal interface (that is, where the Magic Transit egress traffic will traverse). Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,360 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the IPsec-terminating device in your premises) to reduce its current value by 140 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
index b760409416dfd6f..5768c1e380eceba 100644
--- a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
@@ -18,8 +18,8 @@ The following steps outline the recommended multi-step draining process to achie
 2. **Wait for global BGP convergence**: Allow a period of time (typically five to ten minutes) for the new native advertisement to propagate fully across the global routing table, and for routes to converge. This passive waiting period ensures that the majority of traffic has shifted to your local network before the next step.
 3. **Signal BGP withdrawal from the Cloudflare edge**: Once you have verified that traffic has successfully drained, use one of the BGP control methods to stop the advertisement of the prefix from the Cloudflare edge.
 
-	:::caution[ISP route refresh delays may impact traffic]
-	Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
-	:::
+   :::caution[ISP route refresh delays may impact traffic]
+   Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
+   :::
 
-4. The draining process is complete.
\ No newline at end of file
+4. The draining process is complete.
diff --git a/src/content/partials/networking-services/magic-user-role.mdx b/src/content/partials/networking-services/magic-user-role.mdx
index 5f688524a5b726f..72715ce73e544d4 100644
--- a/src/content/partials/networking-services/magic-user-role.mdx
+++ b/src/content/partials/networking-services/magic-user-role.mdx
@@ -12,7 +12,7 @@ For example, if multiple teams manage different Cloudflare products on the same
 
 1. Go to the **Members** page.
 
-	 <DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 2. Under **Members**, enter an existing user's name and select **Search**.
 3. Expand the menu at the end of the user row.
diff --git a/src/content/partials/networking-services/mconn/device-metrics.mdx b/src/content/partials/networking-services/mconn/device-metrics.mdx
index a2fad49b670b4f3..278ab4d0b610b62 100644
--- a/src/content/partials/networking-services/mconn/device-metrics.mdx
+++ b/src/content/partials/networking-services/mconn/device-metrics.mdx
@@ -13,59 +13,59 @@ For example:
 
 ```graphql graphql-api-explorer
 query telemetry(
-  $accountTag: string
-  $snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
-  $snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
-  $snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
-  $limit: int64!
+	$accountTag: string
+	$snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
+	$snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
+	$snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
+	$limit: int64!
 ) {
-  viewer {
-    accounts(filter: { accountTag: $accountTag }) {
-      snapshots: mconnTelemetrySnapshots(
-        filter: $snapshotsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC]
-      ) {
-        max {
-          cpuCount
-          loadAverage1m
-          memoryFreeBytes
-          memoryTotalBytes
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-      snapshotMounts: mconnTelemetrySnapshotMounts(
-        filter: $snapshotMountsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC]
-      ) {
-        max {
-          availableBytes
-          totalBytes
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-      snapshotThermals: mconnTelemetrySnapshotThermals(
-        filter: $snapshotThermalsFilter
-        limit: $limit
-        orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
-      ) {
-        max {
-          currentCelsius
-        }
-        dimensions {
-          connectorId
-          datetimeFiveMinutes
-        }
-      }
-    }
-  }
+	viewer {
+		accounts(filter: { accountTag: $accountTag }) {
+			snapshots: mconnTelemetrySnapshots(
+				filter: $snapshotsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC]
+			) {
+				max {
+					cpuCount
+					loadAverage1m
+					memoryFreeBytes
+					memoryTotalBytes
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+			snapshotMounts: mconnTelemetrySnapshotMounts(
+				filter: $snapshotMountsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC]
+			) {
+				max {
+					availableBytes
+					totalBytes
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+			snapshotThermals: mconnTelemetrySnapshotThermals(
+				filter: $snapshotThermalsFilter
+				limit: $limit
+				orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
+			) {
+				max {
+					currentCelsius
+				}
+				dimensions {
+					connectorId
+					datetimeFiveMinutes
+				}
+			}
+		}
+	}
 }
 ```
 
@@ -75,4 +75,4 @@ The metric `average CPU load` is unique and distinctly different from `CPU utili
 
 CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the Cloudflare One Appliance CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
 
-Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
\ No newline at end of file
+Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
diff --git a/src/content/partials/networking-services/mconn/licence-keys.mdx b/src/content/partials/networking-services/mconn/licence-keys.mdx
index 762bbc9168a849d..19fc13fb15ac9ea 100644
--- a/src/content/partials/networking-services/mconn/licence-keys.mdx
+++ b/src/content/partials/networking-services/mconn/licence-keys.mdx
@@ -3,8 +3,6 @@ params:
   - virtualConnectorName
 ---
 
-
-
 :::note
 You cannot use the same license key twice, or reuse a key once the virtual machine has been registered with Cloudflare. You need a new key from your account team for every new {props.virtualConnectorName}.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
index 720da967d7f0d34..5ed0d70f3420a55 100644
--- a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
@@ -7,4 +7,4 @@ params:
 Before you can activate your Cloudflare One Appliance (formerly Magic WAN Connector), you need to follow Cloudflare's instructions regarding DHCP. For instructions, refer to:
 
 - The <a href={props.hardwareConnectorURL}>hardware version of Cloudflare One Appliance</a>
-- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
\ No newline at end of file
+- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
index abb2c35e51bfd08..69bcf5dfd06bb9d 100644
--- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -3,38 +3,38 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
+    `}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
-	`}
-	inline={false}
-	/>
-	</>
 )
-}
-4. In **Status**, select _Deactivated_ from the drop-down menu.
-5. Select **Update**.
+} 4. In **Status**, select _Deactivated_ from the drop-down menu. 5. Select **Update**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index 0946f2695192a8a..e2cb63fb178ba6b 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -12,4 +12,4 @@ The default password for Cloudflare One Appliance is the serial number (also kno
 
 The default password for Virtual Appliance is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
 
-For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
+For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
index b11277c02a77557..20bffc12db414cc 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -8,34 +8,33 @@ import { DashButton, Markdown } from "~/components";
 In **Basic information**, you can change the name and description of your Cloudflare One Appliance (formerly Magic WAN Connector).
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. In **Basic information** make the necessary changes.
-5. Select **Save**.
\ No newline at end of file
+} 3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**. 4. In **Basic information** make the necessary changes. 5. Select **Save**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
index f71c11c0de55a12..16e6075ed0b533e 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -6,36 +6,32 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Connectors** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+inline={false}
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**.
-5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**.
-6. Make the necessary changes.
-7. Select **Save**.
\ No newline at end of file
+} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**. 5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**. 6. Make the necessary changes. 7. Select **Save**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
index 7a5e68df4e8f5b2..e0c56079072bb08 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
@@ -6,35 +6,35 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a> > **Insights**.
 		2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on.
 		3. Select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/networking-insights/health" />
-				<Markdown
-	text={`
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+<Markdown
+text={`
 		3. Find the site you want to make changes on > select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 		`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
index 267156ca7a1e2d3..79373537351ff1d 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -8,35 +8,33 @@ import { DashButton, Markdown } from "~/components";
 You can only add or remove applications to Breakout traffic and Prioritized traffic. To add or remove applications:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
-4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**.
-5. Select **Add** to add a new application.
-6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
\ No newline at end of file
+} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**. 5. Select **Add** to add a new application. 6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
index c8f54f97a753b77..6a9d81008d379c6 100644
--- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -3,7 +3,7 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 Cloudflare One Appliance (formerly Magic WAN Connector) communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
@@ -18,33 +18,34 @@ There are three symbols for the heartbeat signal that allow you to quickly check
 ### Access Cloudflare One Appliance's heartbeat
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Connectors** page.
 		`}
-	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
-
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
-	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
+    `}
+    inline={false}
+    />
+    </>
+
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
index b94efb16efe2c31..e0ac8962997b44f 100644
--- a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
@@ -3,42 +3,43 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from '~/components';
+import { DashButton, Markdown } from "~/components";
 
 The Interrupt window defines when Cloudflare One Appliance (formerly Magic WAN Connector) can update its systems. When Cloudflare One Appliance is updating, this may result in an interruption to existing connections. Set up a time window that minimizes disruption to your sites.
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks** > **Connectors**.
 		2. In **Appliances** > **Appliances**, select the Cloudflare One Appliance for which you want to set up the update window > **Edit**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
 
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
+    `}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
-	`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
-   - **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
-   - **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
-   - **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
+} 3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
+
+- **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
+- **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
+- **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
index ad72dcbe7fe8d77..622bec3086c2415 100644
--- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
@@ -9,30 +9,27 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag
 
 {/* Dashboard steps for CF1 Cloudflare WAN (Cloudflare One dashboard) */}
 { props.dashName === "CF1 Cloudflare WAN" && (
-	<>
-	<ol>
-		<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
-		<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
-	</ol>
-	</>
+<>
+<ol>
+<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
+<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
+</ol>
+</>
 )
 }
 
 {/* Dashboard steps for Cloudflare WAN (standalone dashboard) */}
 { props.dashName !== "CF1 Cloudflare WAN" && (
-	<>
-	<ol>
-		<li>Go to the <strong>Connectors</strong> page.
-			<br />
-			<DashButton url="/?to=/:account/magic-networks/connections" />
-		</li>
-		<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
-	</ol>
-	</>
+<>
+<ol>
+<li>Go to the <strong>Connectors</strong> page.
+<br />
+<DashButton url="/?to=/:account/magic-networks/connections" />
+</li>
+<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
+</ol>
+</>
 )
-}
-3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard.
-4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account.
-5. Select **Register appliance**.
+} 3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard. 4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account. 5. Select **Register appliance**.
 
-Your device is now registered with your account.
\ No newline at end of file
+Your device is now registered with your account.
diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
index fa154fec8acde27..b9ba61db220dfb4 100644
--- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
@@ -6,6 +6,7 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 When adding or removing Cloudflare One Appliances (formerly Magic WAN Connectors), you need to be aware of the difference between the physical device and its profile.
+
 - The physical device is the hardware at your site.
 - The profile contains the configuration that allows the device to connect to Cloudflare, including your WANs, LANs, traffic steering, and LAN policies.
 
@@ -14,67 +15,69 @@ You can have more than one Cloudflare One Appliance in one profile if you initia
 ## Remove a profile
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to **Appliances** > **Profiles**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to **Appliances** > **Profiles**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
+} 3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
 
 ## Remove a physical device
 
 To remove a Cloudflare One Appliance from your account:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-	<>
-		<Markdown
-	text={`
+<>
+<Markdown
+text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-	inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
+
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-	/>
-		<DashButton url="/?to=/:account/magic-networks/connections" />
+/>
+<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    	<Markdown
+    text={`
+    	2. Go to the **Appliances** tab > **Appliances**.
+    	`}
+    inline={false}
+    />
+    </>
 
-		<Markdown
-	text={`
-		2. Go to the **Appliances** tab > **Appliances**.
-		`}
-	inline={false}
-	/>
-	</>
 )
-}
-3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
\ No newline at end of file
+} 3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 5dc4a5441cd0fde..58394a01819ac0d 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -16,7 +16,7 @@ params:
   - networkSegmentationURL
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
+import { GlossaryTooltip, Render } from "~/components";
 
 The Cloudflare One Appliance (formerly Magic WAN Connector) software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
 
@@ -91,11 +91,14 @@ When a failover occurs, traffic is moved to the new active node. It could take u
 
 This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }} />
+<Render
+	file="mconn/wan-two-tunnels"
+	product="networking-services"
+	params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }}
+/>
 
 When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in Cloudflare One Appliance routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 
-
 Creating several WAN connections also means Cloudflare One Appliance can failover between circuits according to their health.
 
 ### High-capacity use cases
@@ -108,7 +111,7 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ### WAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
 - **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. For details on how Cloudflare calculates priorities, refer to <a href={props.trafficSteeringURL}>Traffic steering</a>.
 - **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. For details, refer to <a href={props.hcFrequencyURL}>Update tunnel health checks frequency</a>.
@@ -116,9 +119,9 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ## LAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
-- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable  DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
+- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
 - **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
 - **Routed subnets:** Configures additional subnets behind a layer 3 router. For details, refer to <a href={props.routedSubnetsURL}>Routed subnets</a>.
 
@@ -126,4 +129,4 @@ If you do not have more than one anycast IP configured in your account, and you
 
 Depending on your use case, you can define policies in your Cloudflare One Appliance to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
-For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
\ No newline at end of file
+For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index 7eb868cf827fa41..d64025ffaf32777 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -7,53 +7,64 @@ params:
   - dashName
 ---
 
-import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
+import {
+	APIRequest,
+	Aside,
+	AnchorHeading,
+	CURL,
+	DashButton,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+} from "~/components";
 
 { props.magicWord === "breakout" && (
-	<>
-		<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
-		<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-	</>
-	)
+<>
+<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
+<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+</>
+)
 }
 
 { props.magicWord === "prioritized" && (
-	<>
-		<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
-		<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
-		<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-	</>
-	)
+<>
+<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
+<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
+<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+</>
+)
 }
 
 { props.magicWord === "breakout" && (
-	<>
-		<pre class="mermaid">
-			{`
-			flowchart LR
-			accTitle: Breakout traffic flow
-			accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
-			a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
-
-			a-- Breakout traffic ---d(Application1) & e(Application2) --> c
-
-			classDef orange fill:#f48120,color: black
-			class a,b orange
-			`}
-		</pre>
-		<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
-		<Aside type="note" title="A note on security">
-		<Markdown
-		text={`
-		We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
+<>
+<pre class="mermaid">
+{`
+flowchart LR
+accTitle: Breakout traffic flow
+accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
+a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
+
+    		a-- Breakout traffic ---d(Application1) & e(Application2) --> c
+
+    		classDef orange fill:#f48120,color: black
+    		class a,b orange
+    		`}
+    	</pre>
+    	<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
+    	<Aside type="note" title="A note on security">
+    	<Markdown
+    	text={`
+    	We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
 
     For details on how Cloudflare routes traffic, refer to <a href="${props.trafficSteeringURL}">Traffic steering</a>.
-		`}
-		inline={false}
-		/>
-		</Aside>
-	</>
-	)
+    	`}
+    	inline={false}
+    	/>
+    	</Aside>
+    </>
+    )
+
 }
 
 ## Add an application to your account
@@ -64,28 +75,28 @@ To add applications to your account:
 
 Send a `POST` request to add new apps to your account.
 
-	<APIRequest
-	path="/accounts/{account_id}/magic/apps"
-	method="POST"
-	json={{
+    <APIRequest
+    path="/accounts/{account_id}/magic/apps"
+    method="POST"
+    json={{
     "managed_app_id": "<APP_ID>",
     "name": "<APP_NAME>",
     "type": "<APP_TYPE>",
-	}}
-	/>
-
-	```json output
-	{
-		"result": {
-			"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
-			"name": "<APP_NAME>",
-			"type": "<APP_TYPE>",
-		},
-		"success": true,
-		"errors": [],
-		"messages": []
-	}
-	```
+    }}
+    />
+
+    ```json output
+    {
+    	"result": {
+    		"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
+    		"name": "<APP_NAME>",
+    		"type": "<APP_TYPE>",
+    	},
+    	"success": true,
+    	"errors": [],
+    	"messages": []
+    }
+    ```
 
 You can now add this new app to the {props.featureName} list in your Cloudflare One Appliance.
 
@@ -315,87 +326,88 @@ You need to delete {props.featureName} applications for each of your existing si
 </TabItem> </Tabs>
 
 { props.magicWord === "breakout" && (
-	<>
-		<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
+<>
+<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
+
+    	<Markdown
+    	text={`
 
-		<Markdown
-		text={`
 You can pin applications to a specific WAN port in Cloudflare One Appliance when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, Cloudflare One Appliance automatically fails over to a standard configured WAN port priority.
 
 With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
 
 To pin applications to a WAN port:
-		`}
-		inline={false}
-		/>
-
-		{ props.dashName === "CF1 Cloudflare WAN" ? (
-			<>
-				<Markdown
-			text={`
-				1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
-				2. Go to **Connectors** > **Appliances** > **Profiles**.
-				3. Select the Cloudflare One Appliance you want to configure > **Edit**.
-			`}
-			inline={false}
-			/>
-			</>
-		) : (
-			<>
-			<Markdown
-				text={`
-					1. Go to the **Connectors** page.
-					`}
-				inline={false}
-				/>
-					<DashButton url="/?to=/:account/magic-networks/connections" />
-
-					<Markdown
-				text={`
-					2. Go to the **Appliances** tab > **Profiles**.
-					`}
-				inline={false}
-				/>
-				<Markdown
-			text={`
-				3. Select your Appliance > **Edit**.
-			`}
-			inline={false}
-			/>
-			</>
-		)
-		}
-		<Markdown
-		text={`
-		4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
-		5. Select the three dots next to it > **Edit application traffic**.
-		6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
-		7. Select **Save**.
-		`}
-		inline={false}
-		/>
-	</>
+`}
+inline={false}
+/>
+
+    	{ props.dashName === "CF1 Cloudflare WAN" ? (
+    		<>
+    			<Markdown
+    		text={`
+    			1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
+    			2. Go to **Connectors** > **Appliances** > **Profiles**.
+    			3. Select the Cloudflare One Appliance you want to configure > **Edit**.
+    		`}
+    		inline={false}
+    		/>
+    		</>
+    	) : (
+    		<>
+    		<Markdown
+    			text={`
+    				1. Go to the **Connectors** page.
+    				`}
+    			inline={false}
+    			/>
+    				<DashButton url="/?to=/:account/magic-networks/connections" />
+
+    				<Markdown
+    			text={`
+    				2. Go to the **Appliances** tab > **Profiles**.
+    				`}
+    			inline={false}
+    			/>
+    			<Markdown
+    		text={`
+    			3. Select your Appliance > **Edit**.
+    		`}
+    		inline={false}
+    		/>
+    		</>
+    	)
+    	}
+    	<Markdown
+    	text={`
+    	4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
+    	5. Select the three dots next to it > **Edit application traffic**.
+    	6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
+    	7. Select **Save**.
+    	`}
+    	inline={false}
+    	/>
+    </>
+
 )
 }
 
-
 {props.magicWord === "breakout" && (
-	<>
-		<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
-	</>
-	)
+<>
+<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
+</>
+)
 }
 
 { props.magicWord === "breakout" && (
-	<>
-	<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
-		<Render
-			file="mconn/network-options/app-aware-policies/warp-traffic"
-			product="networking-services"
-			params={{
+<>
+<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
+<Render
+file="mconn/network-options/app-aware-policies/warp-traffic"
+product="networking-services"
+params={{
 				warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 			}}
-			/>
-	</>
-	)
-}
\ No newline at end of file
+/>
+</>
+)
+}
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
index 70f81778279f769..126ebd7f08071e4 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
@@ -14,7 +14,11 @@ The Cloudflare One Appliance uses NetFlow v9 to export flow data for breakout tr
 
 ### Enable NetFlow exports
 
-<Render file="account-id-api-key" product="networking-services" params={{ showSiteId: true }} />
+<Render
+	file="account-id-api-key"
+	product="networking-services"
+	params={{ showSiteId: true }}
+/>
 
 1. Send a `PUT` request to the Netflow configuration endpoint for your site.
 2. In the JSON body request, you must include the `collector_ip` parameter. To export traffic statistics to Network Flow, use the IP address `162.159.65.1`. This is the only field required to enable the feature.
@@ -25,11 +29,12 @@ Minimal configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		"collector_ip": "162.159.65.1"
+		collector_ip: "162.159.65.1",
 	}}
 />
 
 3. You can customize the configuration by adding optional fields to the JSON payload. These fields include:
+
 - `collector_port`: The UDP port for the collector. The default is `2055`.
 - `sampling_rate`: The rate at which packets are sampled.
 - `active_timeout`: The timeout for active flows in seconds.
@@ -41,11 +46,11 @@ Full configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		"collector_ip": "162.159.65.1",
-		"collector_port": 2055,
-		"sampling_rate": 100,
-		"active_timeout": 60,
-		"inactive_timeout": 30
+		collector_ip: "162.159.65.1",
+		collector_port: 2055,
+		sampling_rate: 100,
+		active_timeout: 60,
+		inactive_timeout: 30,
 	}}
 />
 
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
index 1d2567a03ec9803..f3203bf58619f2c 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
@@ -4,7 +4,7 @@ params:
   - appTypesGatewayURL
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Standard traffic policies match on network-layer attributes like IP addresses and port ranges. Application-aware policies go further — they identify traffic by the application generating it, so you can make routing and security decisions based on what the traffic is, not just where it is going.
 
@@ -19,5 +19,4 @@ With application-aware policies, you can:
 
 For details, refer to the following pages:
 
-
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
index a00df21396023ca..4ef40f59c1c2bc9 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -5,7 +5,14 @@ params:
   - cfVsCoreDashNamingMwanCni
 ---
 
-import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	APIRequest,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, Cloudflare One Appliance (formerly Magic WAN Connector) forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
index 94056a78a61e391..3a9c1d021abc578 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
@@ -3,7 +3,14 @@ params:
   - dashName
 ---
 
-import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
+import {
+	APIRequest,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+	DashButton,
+} from "~/components";
 
 When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN Connector) can also act as a DHCP server in your network. To enable this feature:
 
diff --git a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
index 000cfd917c0229e..dfd266a24e6682a 100644
--- a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
@@ -63,4 +63,3 @@ For step-by-step instructions to configure a LAN and supply a static NAT prefix,
 
 - <a href={props.hardConnectorURL}>Configure hardware Appliance</a>
 - <a href={props.virtualConnectorURL}>Configure Virtual Appliance</a>
-
diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
index 6243e2b3a08d8e5..079bcbe7f92895c 100644
--- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -5,7 +5,14 @@ params:
   - virtualConnectorURL
 ---
 
-import { APIRequest, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
+import {
+	APIRequest,
+	DashButton,
+	Markdown,
+	Render,
+	TabItem,
+	Tabs,
+} from "~/components";
 
 You can define policies in your Cloudflare One Appliance (formerly Magic WAN Connector) to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
index 9509f4c9fe5a7d6..22273d0546df33d 100644
--- a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
@@ -44,7 +44,7 @@ Blue represents directly-attached subnets, and red represents routed subnets.
 	`}
 </pre>
 
-<br/>
+<br />
 
 To add a routed subnet to your LAN, you need:
 
diff --git a/src/content/partials/networking-services/mconn/overview.mdx b/src/content/partials/networking-services/mconn/overview.mdx
index 7ac69fc4e47b806..0aaac9276dd0f51 100644
--- a/src/content/partials/networking-services/mconn/overview.mdx
+++ b/src/content/partials/networking-services/mconn/overview.mdx
@@ -19,4 +19,4 @@ Either option ensures the best possible connectivity to the closest Cloudflare n
 
 Review this section to learn how to configure and deploy {props.hardwareProductName}.
 
-<DirectoryListing />
\ No newline at end of file
+<DirectoryListing />
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
index 1680225d6dfcefe..3c1e9c89c2d55cc 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
@@ -19,7 +19,11 @@ Cloudflare customers can inspect metrics for a specific Cloudflare One Appliance
 
 To find the information above and start troubleshooting your Cloudflare One Appliance:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 
 ### Performance analytics
 
@@ -33,7 +37,11 @@ In Performance analytics you can review your Cloudflare One Appliance's performa
 
 To access performance analytics:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **Performance analytics**.
 
 ### Port analytics
@@ -45,7 +53,11 @@ Port analytics gives you access to information related to the packets sent and r
 
 The dashboard provides this information for all active ports in your Cloudflare One Appliance. To access port analytics:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **Port analytics**.
 
 ### Event logs
@@ -71,15 +83,22 @@ Use Event logs to identify general patterns and changes over time. This is usefu
 
 To access event logs:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
-4. Select **Events**.
-5. You can filter results by specific events, and by time.
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
+4. Select **Events**. 5. You can filter results by specific events, and by time.
 
 ### DHCP leasing
 
 The DHCP leasing section identifies DHCP assigned leases and their expiration dates. To access DHCP leasing:
 
-<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+<Render
+	file="mconn/troubleshooting/troubleshooting-steps"
+	product="networking-services"
+	params={{ dashName: props.dashName }}
+/>
 4. Select **DHCP leasing**.
 
 ## Troubleshooting tips
diff --git a/src/content/partials/networking-services/mconn/vlan-tagging.mdx b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
index d13dfd1e5a4f2a6..787946548bcc7a4 100644
--- a/src/content/partials/networking-services/mconn/vlan-tagging.mdx
+++ b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
@@ -17,4 +17,4 @@ Use VLAN ID <code>0</code> when:
 You can also configure subinterfaces on the {props.virtualConnectorName} by associating the network interface with a Port Group or Distributed Port Group trunk and specifying a VLAN ID in addition to the port associated with the network interface (VLAN ID <code>1</code>-<code>4094</code>).
 
 Refer to <Markdown text={props.url} /> for more information.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
index 304d1616c387e6a..bce930a2152d57d 100644
--- a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
+++ b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
@@ -4,4 +4,4 @@ params:
   - dashName
 ---
 
-When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
+When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
diff --git a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
index 3bf575d2cf83e7d..5419d89b875b933 100644
--- a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
+++ b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
@@ -11,4 +11,4 @@ You will receive the status of the advertisement for each prefix with the follow
 - **Delayed**: The prefix cannot currently be advertised but will attempt advertisement. After the prefix can be advertised, a new notification is sent with the updated status.
 - **Locked**: The prefix is locked and cannot be advertised.
 - **Could not Advertise**: Cloudflare was unable to advertise the prefix. This status can occur for multiple reasons, but usually occurs when you are not allowed to advertise a prefix.
-- **Error**: A general error occurred during prefix advertisement.
\ No newline at end of file
+- **Error**: A general error occurred during prefix advertisement.
diff --git a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
index 0090ebe938488ea..7b58e1a58a4bed2 100644
--- a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
+++ b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
@@ -17,15 +17,19 @@ After Magic Transit activates and your traffic flows through Cloudflare, Cloudfl
 The following diagrams illustrate this process:
 
 <Width size="large">
-	![The diagram shows the flow of traffic when you send flow data from your network to Cloudflare for analysis.](~/assets/images/network-flow/1-flowdata.png)
+	![The diagram shows the flow of traffic when you send flow data from your
+	network to Cloudflare for
+	analysis.](~/assets/images/network-flow/1-flowdata.png)
 </Width>
 
 <Width size="large">
-	![Cloudflare automatically notifies you when Cloudflare detects an attack	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
+	![Cloudflare automatically notifies you when Cloudflare detects an attack
+	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
 </Width>
 
 <Width size="large">
-	![You can create rules to activate Magic Transit automatically, to protect your IP addresses from a DDoS
+	![You can create rules to activate Magic Transit automatically, to protect
+	your IP addresses from a DDoS
 	attack.](~/assets/images/network-flow/3-flowdata.png)
 </Width>
 
diff --git a/src/content/partials/networking-services/mnm/faqs.mdx b/src/content/partials/networking-services/mnm/faqs.mdx
index b4a27eb520e6d6c..b0208fe02c88cf2 100644
--- a/src/content/partials/networking-services/mnm/faqs.mdx
+++ b/src/content/partials/networking-services/mnm/faqs.mdx
@@ -6,7 +6,7 @@ If you cannot find your answer here, refer to the [community page](https://commu
 
 ## I am getting an "Invalid account settings request body: account name format contains illegal characters or is not supported" error when trying to create a rule.
 
-This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 
diff --git a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
index cd765351f8a8f43..46c472367567090 100644
--- a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
+++ b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Configure your router to export <GlossaryTooltip term="sFlow">sFlow</GlossaryTooltip> data to Cloudflare's network for analysis in Network Flow (formerly Magic Network Monitoring). sFlow is a network monitoring protocol that samples network traffic to provide visibility into your network's performance and traffic patterns.
 
diff --git a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
index 4cbd7f7fa55f513..c117433d7d663dc 100644
--- a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
@@ -8,14 +8,14 @@ To use dynamic threshold rules, you must send NetFlow or sFlow data to Cloudflar
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | zscore |
-| **Target** | Can be defined in either bits per second or packets per second. |
-| **Sensitivity** | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic. |
+| Field                  | Description                                                                                                                                                                                                                                                                                                                                              |
+| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                               |
+| **Rule type**          | zscore                                                                                                                                                                                                                                                                                                                                                   |
+| **Target**             | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                                          |
+| **Sensitivity**        | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic.                                                                                                                                                                             |
 | **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. Network Flow supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section. |
+| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section.                                                                      |
 
 ## API documentation
 
@@ -33,4 +33,4 @@ Z = (X - μ) / σ
 
 - `X` = Current traffic value.
 - `μ` = Mean traffic value over the long window.
-- `σ` = Standard deviation over the long window.
\ No newline at end of file
+- `σ` = Standard deviation over the long window.
diff --git a/src/content/partials/networking-services/mnm/rules/overview.mdx b/src/content/partials/networking-services/mnm/rules/overview.mdx
index 64c496cc2672375..f604442b91f7228 100644
--- a/src/content/partials/networking-services/mnm/rules/overview.mdx
+++ b/src/content/partials/networking-services/mnm/rules/overview.mdx
@@ -25,7 +25,7 @@ If you get the following error when trying to create a rule:
 
 `Invalid account settings request body: account name format contains illegal characters or is not supported`
 
-Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 :::
diff --git a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
index cc8a9232c23298e..2a6ee954fa33c84 100644
--- a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
+++ b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, DashButton } from "~/components"
+import { Render, DashButton } from "~/components";
 
 Network Flow (formerly Magic Network Monitoring) can notify you by email, webhook, or PagerDuty when a rule is triggered. When a rule detects a traffic anomaly, notifications alert your team so you can respond — or, if you use Magic Transit with auto-advertisement, Cloudflare can begin mitigating the attack automatically.
 
@@ -16,16 +16,19 @@ For more information on the notification platform, refer to [Notifications docum
 
 ## Notification configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Notification name** | A label to identify this notification in your notifications list. |
-| **Description (optional)** | The description of the notification. |
-| **Webhooks** | One or more webhooks to deliver the notification to. |
-| **Notification email** | One or more email addresses to deliver the notification to. |
+| Field                      | Description                                                       |
+| :------------------------- | :---------------------------------------------------------------- |
+| **Notification name**      | A label to identify this notification in your notifications list. |
+| **Description (optional)** | The description of the notification.                              |
+| **Webhooks**               | One or more webhooks to deliver the notification to.              |
+| **Notification email**     | One or more email addresses to deliver the notification to.       |
 
 ## Rule Auto-Advertisement notifications
 
-<Render file="mnm-auto-advertisement-notifications" product="networking-services" />
+<Render
+	file="mnm-auto-advertisement-notifications"
+	product="networking-services"
+/>
 
 ## Configure rule notifications
 
@@ -41,4 +44,4 @@ To configure notifications for Network Flow rules:
    - **Network Flow: Volumetric Attack** - for static threshold and dynamic threshold notifications
    - **Network Flow: DDoS Attack** - for sFlow DDoS attack notifications
 5. Fill in the notification configuration details.
-6. Select **Save**.
\ No newline at end of file
+6. Select **Save**.
diff --git a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
index b3e8a3d3bc9f6f8..bec5f1386000a0d 100644
--- a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
+++ b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
@@ -12,13 +12,13 @@ To send sFlow data to Cloudflare, your router must support sFlow exports. Refer
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | advanced_ddos |
-| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
-| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes). |
+| Field                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                                                                                                                                                                                                              |
+| **Rule type**          | advanced_ddos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| **Prefix Match**       | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
+| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement).                                                                                                                                                                                                                                                  |
+| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes).                                                                                                                                                                                                                                                                    |
 
 ## API documentation
 
@@ -26,4 +26,4 @@ Refer to the [Rules API documentation](/api/resources/magic_network_monitoring/s
 
 ## Tune the sFlow DDoS alert thresholds
 
-You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
\ No newline at end of file
+You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
diff --git a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
index 8f00ec41f108d69..6f3111db0f8feab 100644
--- a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
@@ -10,15 +10,15 @@ To use static threshold rules, you must send NetFlow or sFlow data to Cloudflare
 
 ## Rule configuration fields
 
-| Field | Description |
-| :---- | :---- |
-| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
-| **Rule type** | threshold |
-| **Rule threshold type** | Can be defined in either bits per second or packets per second. |
-| **Rule threshold** | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum. |
-| **Rule duration** | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes. |
-| **Auto-advertisement** | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
-| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes). |
+| Field                   | Description                                                                                                                                                                                                                                                                                                                    |
+| :---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rule name**           | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                     |
+| **Rule type**           | threshold                                                                                                                                                                                                                                                                                                                      |
+| **Rule threshold type** | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                |
+| **Rule threshold**      | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum.                                                                                                                                       |
+| **Rule duration**       | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes.                                                                                                                                         |
+| **Auto-advertisement**  | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
+| **Rule IP prefix**      | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes).                                                                                                          |
 
 ## API documentation
 
@@ -45,9 +45,9 @@ When you first configure Network Flow, you may not know the typical traffic patt
 This lets you collect baseline traffic data without receiving alerts. After configuring your initial rules, monitor for alerts and review traffic in Network Flow Analytics. Over time, update each rule's threshold based on historical traffic data.
 
 | Threshold type | Recommended rule threshold to collect initial data |
-| :---- 				 | :---- 																						  |
-| Bits 					 | 10 Gbps (10,000,000,000 bits per second) 					|
-| Packets 			 | 10 Mpps (10,000,000 packets per second) 						|
+| :------------- | :------------------------------------------------- |
+| Bits           | 10 Gbps (10,000,000,000 bits per second)           |
+| Packets        | 10 Mpps (10,000,000 packets per second)            |
 
 #### Setting the appropriate threshold
 
@@ -64,9 +64,9 @@ To find the maximum non-attack traffic for a one minute time interval over the p
 2. Select **Add filter**.
 3. In **New filter**, use the drop-down menus to create the following filter:
 
-| Field 						| Operator | Rule name 			|
-| :---- 						| :---- 	 | :---- 		 			|
-| _Monitoring Rule_ | _equals_ | `<RULE_NAME>`  |
+| Field             | Operator | Rule name     |
+| :---------------- | :------- | :------------ |
+| _Monitoring Rule_ | _equals_ | `<RULE_NAME>` |
 
 Once the rule filter is selected in Network Flow Analytics, you can check the historical traffic volume data for the rule over the selected time period. Cloudflare recommends reviewing historical data in seven-day increments, since that is the largest window that shows one-hour time intervals. To select a custom seven-day range, go to the top right corner of Network Flow analytics, open the time window drop-down menu, and select **Custom range**.
 
@@ -80,4 +80,4 @@ Your IP prefixes may experience inconsistent spikes across one-minute intervals.
 
 ### Adjusting rules over time
 
-After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
\ No newline at end of file
+After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
diff --git a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
index db70332705ae2dc..87ca7eb4eb1d41c 100644
--- a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
+++ b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
@@ -2,7 +2,6 @@
 {}
 ---
 
-
 import { GlossaryTooltip, DashButton } from "~/components";
 
 Use the GraphQL Analytics API to retrieve Network Flow (formerly Magic Network Monitoring) <GlossaryTooltip term="flow data">flow data</GlossaryTooltip>.
diff --git a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
index 1afc04ea7741587..2849ce921c3e6a5 100644
--- a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
+++ b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
@@ -6,7 +6,7 @@ Instructions to adjust MSS by applying MSS clamps vary depending on the vendor o
 
 The following table lists several commonly used router vendors with links to MSS clamping instructions:
 
-| Router device | URL |
-| ---					  | --- |
+| Router device | URL                                                                                                                                                                                    |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cisco         | [TCP IP Adjust MSS](https://www.cisco.com/en/US/docs/ios-xml/ios/ipapp/command/ip_tcp_adjust-mss_through_ip_wccp_web-cache_accelerated.html#GUID-68044D35-A53E-42C1-A7AB-9236333DA8C4) |
-| Juniper | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html) |
+| Juniper       | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html)                                           |
diff --git a/src/content/partials/networking-services/reference/longest-prefix-match.mdx b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
index 562deeae9654317..98fb9a953cd67de 100644
--- a/src/content/partials/networking-services/reference/longest-prefix-match.mdx
+++ b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
\ No newline at end of file
+Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
diff --git a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
index 4b89061153d1dcb..660c84eea51122e 100644
--- a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
+++ b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
@@ -4,14 +4,14 @@
 
 Cloudflare has nine geographic regions:
 
-| Region code | Region |
-| ----- | ----- |
-| `AFR` | Africa |
-| `APAC` | Asia Pacific |
-| `EEUR` | Eastern Europe |
-| `ENAM` | Eastern North America |
-| `ME` | Middle East |
-| `OC` | Oceania |
-| `SAM` | South America |
-| `WEUR` | Western Europe |
-| `WNAM` | Western North America |
+| Region code | Region                |
+| ----------- | --------------------- |
+| `AFR`       | Africa                |
+| `APAC`      | Asia Pacific          |
+| `EEUR`      | Eastern Europe        |
+| `ENAM`      | Eastern North America |
+| `ME`        | Middle East           |
+| `OC`        | Oceania               |
+| `SAM`       | South America         |
+| `WEUR`      | Western Europe        |
+| `WNAM`      | Western North America |
diff --git a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
index 4dddd911617f979..666d6fb81f454a0 100644
--- a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
+++ b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
@@ -21,7 +21,8 @@ A tunnel health check probe travels from Cloudflare to the tunnel origin, then r
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN"
+		productName:
+			props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN",
 	}}
 />
 
@@ -113,12 +114,12 @@ To avoid control plane policies enforced by the origin network, you can set tunn
 
 ### Summary table with tunnel health check probe types
 
-| Attribute 					| Type 					| Unidirectional health checks | Bidirectional health checks |
-| :---: 							| :---: 				| :---: 											 | :---: 											 |
-| Source Address 			| Request Style | Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
-| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) |Origin Interface Address (Privately Routable) / Custom Target |
-| Source Address 			| Reply Style		| Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-| Destination Address | Reply Style 	| Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
+|      Attribute      |     Type      |        Unidirectional health checks        |                  Bidirectional health checks                  |
+| :-----------------: | :-----------: | :----------------------------------------: | :-----------------------------------------------------------: |
+|   Source Address    | Request Style |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
+| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+|   Source Address    |  Reply Style  | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+| Destination Address |  Reply Style  |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
 
 ### Graphics summarizing health check types
 
@@ -223,9 +224,10 @@ accDescr: Shows the flow of a unidirectional echo reply health check from Cloudf
 	product="networking-services"
 	params={{
 		mFirewallName: "Cloudflare Network Firewall rules",
-		mFirewallURL: "/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks"
+		mFirewallURL:
+			"/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks",
 	}}
-	/>
+/>
 
 Every Cloudflare data center configured to process your traffic sends tunnel health check probes. The rate at which Cloudflare sends these probes varies based on tunnel and location. You can tune this rate on a per-tunnel basis by modifying the `health_check` rate with the <a href={props.changeHealthCheckRate}>API or the dashboard</a>. You can set the rate as _low_, _mid_, or _high_, with _mid_ being the default.
 
@@ -233,7 +235,6 @@ The actual rate formula considers the number of servers in a Cloudflare data cen
 
 When a probe attempt fails for a <a href={props.probeHealth}>healthy tunnel</a>, each server detecting the failure quickly probes up to two more times to obtain an accurate result. Cloudflare does the same if a tunnel has been down and probes start returning success. Because Cloudflare global network servers send probes up to every second, your network will receive several hundred health check packets per second. Each Cloudflare data center sends only one health check packet as part of a probe, representing a relatively trivial amount of traffic.
 
-
 ## Health state and prioritization
 
 There are three tunnel health states: healthy, degraded, and down.
@@ -305,4 +306,4 @@ Suppose the connectivity issue that set Tunnel 1 health to down becomes resolved
 
 When all three probes return successfully, {props.productName} transitions the tunnel from down to degraded. As part of this transition, Cloudflare reduces the priority penalty for that route so that its priority becomes `500,100`. Because Tunnel 2 has a priority of `200`, traffic continues to flow over Tunnel 2.
 
-Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
\ No newline at end of file
+Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
diff --git a/src/content/partials/networking-services/routing/anycast-warning.mdx b/src/content/partials/networking-services/routing/anycast-warning.mdx
index 4a70b0d9c18b322..581fa4d4006258c 100644
--- a/src/content/partials/networking-services/routing/anycast-warning.mdx
+++ b/src/content/partials/networking-services/routing/anycast-warning.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Anycast routing]
 Cloudflare uses anycast to route traffic. Anycast is a network addressing and routing method that routes incoming requests to different locations. Traffic can arrive at a different geographic location than expected. Not all requests go to the closest data center because Internet routing and peering relationships are complex, and Cloudflare optimizes for performance and reliability.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/routing/bgp-config-steps.mdx b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
index ddf3fa73d94cc70..49bffd5bd2831f1 100644
--- a/src/content/partials/networking-services/routing/bgp-config-steps.mdx
+++ b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
@@ -10,16 +10,16 @@ import { Aside, Markdown } from "~/components";
 5. <Markdown text={props.locateText} />
 6. In **Customer device ASN**, enter the ASN for your network.
 
-	{ props.magicWord !== "Magic Transit" && (
-		<>
-		<Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
-		</>
-		)
-	}
+   { props.magicWord !== "Magic Transit" && (
+   <>
+   <Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
+   </>
+   )
+   }
 
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations and is not a security mechanism.
 8. (Optional) In **Additional Advertised prefix list**, input any additional prefixes you want to advertise alongside your existing routes. Leave this blank if you do not want to advertise extra routes. Typical prefixes to configure here include:
-	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
-	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
-	{ props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
+   - A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
+   - A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
+     { props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
 9. Select **Save**.
diff --git a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
index 2c65310f9047a4a..b45261be84bfb8e 100644
--- a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
+++ b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
@@ -7,6 +7,7 @@ params:
 import { APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 You can configure the source IP address range used by Cloudflare whenever a Cloudflare service, such as Cloudflare Load Balancing, sends traffic to a Cloudflare One private network. This address range is referred to as the Cloudflare Source IP Prefix (or `cloudflare_source` subnet type in the API).
+
 - IPv4 traffic is sourced from `100.64.0.0/12`. This range is configurable.
 - IPv6 traffic is sourced from `2606:4700:cf1:5000::/64`. This range is not configurable.
 
@@ -25,6 +26,7 @@ You must configure routes in your network so that response traffic for these sou
 ## Prerequisites
 
 Before you begin, ensure that:
+
 - You have Cloudflare One <a href={props.unifiedRoutingLink}>Unified Routing (beta)</a>. If your account is not yet on Unified Routing, contact your account team to discuss migration and availability.
 - You have [Cloudflare One Networks Write](/fundamentals/api/reference/permissions/) permission.
 - Your desired new network range meets the following requirements:
diff --git a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
index 17e4497d25e28e8..d22d6e489c92663 100644
--- a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
+++ b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
@@ -37,7 +37,7 @@ Choose this option if you have a single VPC in your cloud to connect to Cloudfla
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -74,7 +74,7 @@ When you configure a hub on-ramp, Cloudflare always manages the VPN tunnel betwe
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -105,7 +105,7 @@ You have successfully created your Cloudflare WAN on-ramp. However, on-ramp crea
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -156,7 +156,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, select **Add new on-ramp** and begin the **Create a Cloudflare WAN cloud on-ramp** workflow following the standard steps.
@@ -169,7 +169,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the on-ramp you want to download > select the three dots > **Download as Terraform**.
@@ -186,7 +186,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to edit.
@@ -203,7 +203,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to delete.
@@ -227,7 +227,7 @@ To override the defaults with custom prefixes:
 
 1. Go to the **Routes** page.
 
-	<DashButton url="/?to=/:account/magic-networks/routes" />
+   <DashButton url="/?to=/:account/magic-networks/routes" />
 
 2. Select **WAN configuration**.
 3. Scroll to **Propagated routes to cloud networks**.
@@ -244,7 +244,7 @@ You can view estimated costs associated with your cloud resources in the Cloudfl
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the cloud on-ramp for which you want to check the estimated costs > select the three dots > **Associated Resources**.
diff --git a/src/content/partials/networking-services/sites/sites-brief.mdx b/src/content/partials/networking-services/sites/sites-brief.mdx
index b562aa89e9a4045..cea114893c8546c 100644
--- a/src/content/partials/networking-services/sites/sites-brief.mdx
+++ b/src/content/partials/networking-services/sites/sites-brief.mdx
@@ -5,4 +5,4 @@ params:
 
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that Cloudflare notifies you when there are issues with the site's on-ramps.
 
-Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
\ No newline at end of file
+Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx
index e49acf781ff2f8d..ab902ad3cbb22b4 100644
--- a/src/content/partials/networking-services/sites/sites.mdx
+++ b/src/content/partials/networking-services/sites/sites.mdx
@@ -13,6 +13,7 @@ import { Markdown, Render, DashButton } from "~/components";
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to quickly check the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
 
 To use a site, start by setting up your on-ramps. On-ramps can be:
+
 - <a href={props.greIpsecTunnelsURL}>GRE or IPsec tunnels</a>
 - <a href={props.connectorURL}>{props.connectorName}</a>
 - Direct <a href={props.cniURL}>CNI link</a>
@@ -22,9 +23,9 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 ## Add a site
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview**, select **Add site**.
@@ -38,35 +39,36 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 		11. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
 		12. Select **Complete setup** to finish setting up your site.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
-	<DashButton url="/?to=/:account/networking-insights/health" />
-
-		<Markdown
-		text={`
-		2. In **Network overview**, select **Add a site**.
-		3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
-		4. Select **Create and continue**.
-		5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
-		6. Select **Continue**.
-		7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
-		8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
-		9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-		10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
-		11. Select **Complete setup** to finish setting up your site.
-		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+
+    	<Markdown
+    	text={`
+    	2. In **Network overview**, select **Add a site**.
+    	3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
+    	4. Select **Create and continue**.
+    	5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
+    	6. Select **Continue**.
+    	7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
+    	8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
+    	9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
+    	10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
+    	11. Select **Complete setup** to finish setting up your site.
+    	`}
+    	inline={false}
+    />
+    </>
+
 )
 }
 
@@ -82,10 +84,13 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 	params={{
 		instructions: "",
 		magicWord: props.magicWord,
-		networkOverviewPageName: props.magicWord === "CF1 Cloudflare WAN" ? "Network visibility" : "Network overview",
+		networkOverviewPageName:
+			props.magicWord === "CF1 Cloudflare WAN"
+				? "Network visibility"
+				: "Network overview",
 		magicTunnelHcsURL: props.magicTunnelHcsURL,
-		setGeoCoordinatesURL: "#set-geographic-coordinates"
-		}}
+		setGeoCoordinatesURL: "#set-geographic-coordinates",
+	}}
 />
 
 ---
@@ -95,9 +100,9 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 ### Add or remove on-ramps
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
@@ -105,31 +110,32 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 		5. Select **Add** to add a new on-ramp.
 		6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
+inline={false}
+/>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
+    <DashButton url="/?to=/:account/networking-insights/health" />
+
+    <Markdown
+    	text={`
+    	2. Go to **Network overview** > **Traffic overview**.
+    	3. Find your site > select the three dots in front of it > **Edit**.
+    	3. Select **On-ramps**.
+    	4. Select **Add** to add a new on-ramp.
+    	5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
+    	`}
+    	inline={false}
+    />
+    </>
 
-	<Markdown
-		text={`
-		2. Go to **Network overview** > **Traffic overview**.
-		3. Find your site > select the three dots in front of it > **Edit**.
-		3. Select **On-ramps**.
-		4. Select **Add** to add a new on-ramp.
-		5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
-		`}
-		inline={false}
-	/>
-	</>
 )
 }
 
@@ -138,36 +144,34 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 If you add geographic coordinates to your site, it will appear in the Network map. To set up or edit geographic coordinates to an existing site:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to **Insights** > **Network visibility**.
 		2. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Go to the **Network health** page.
 		`}
-		inline={false}
-	/>
-	<DashButton url="/?to=/:account/networking-insights/health" />
-		<Markdown
-		text={`
+inline={false}
+/>
+<DashButton url="/?to=/:account/networking-insights/health" />
+<Markdown
+text={`
 		2. Go to **Network overview** > **Traffic overview**.
 		3. Find your site > select the three dots in front of it > **Edit**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 )
-}
-3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
-4. Select **Save**.
+} 3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates. 4. Select **Save**.
 
 ### Set thresholds for site health
 
@@ -176,6 +180,6 @@ If you add geographic coordinates to your site, it will appear in the Network ma
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: props.magicTunnelHcsURL
+		magicTunnelHcsURL: props.magicTunnelHcsURL,
 	}}
 />
diff --git a/src/content/partials/networking-services/troubleshoot-connectivity.mdx b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
index 9a288f95f8861fd..3c84b2a29e2bedd 100644
--- a/src/content/partials/networking-services/troubleshoot-connectivity.mdx
+++ b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
@@ -74,7 +74,7 @@ You can identify which data centers handle your traffic by using **Network Analy
 
 1. Go to the **Network Analytics** page.
 
-	<DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
+   <DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
 
 2. Select **Add filter** and filter traffic by your source IP addresses to isolate your traffic.
 3. Under **Packets summary**, select the **Source data center** tab. If the tab is not visible, select the three-dot menu (`...`) to reveal additional view options and select **Source data center**.
@@ -112,8 +112,13 @@ If you have worked through this guide and cannot resolve the issue, gather the f
 
 ## Related resources
 
-- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
-- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose routing and BGP issues that affect traffic delivery.
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Monitor tunnel status per data center.
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on how health checks work.
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic patterns over time.
+- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve
+  common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
+- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose
+  routing and BGP issues that affect traffic delivery.
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
+  Monitor tunnel status per data center.
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
+  details on how health checks work.
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic
+  patterns over time.
diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
index 33f16ff7be38ee7..f91d7cf6d89d54e 100644
--- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
+++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
@@ -8,7 +8,13 @@ params:
   - magicWord?
 ---
 
-import { Aside, AnchorHeading, DashButton, GlossaryTooltip, Markdown } from "~/components";
+import {
+	Aside,
+	AnchorHeading,
+	DashButton,
+	GlossaryTooltip,
+	Markdown,
+} from "~/components";
 
 The Cloudflare dashboard monitors the health of all <GlossaryTooltip term="anycast">anycast</GlossaryTooltip> tunnels on your account that route traffic from Cloudflare to your origin network.
 
@@ -23,9 +29,9 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 ## Check tunnel health
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
@@ -34,33 +40,34 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
 		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
-
-		<Markdown
-			text={`
-			1. Go to the **Network health** page.
-				`}
-			inline={false}
-		/>
-
-		<DashButton url="/?to=/:account/networking-insights/health" />
-
-		<Markdown
-			text={`
-			2. Select the **Connector health** tab.
-			3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
-			4. Find the tunnel you want to inspect, select the three dots next to it, and select:
-				- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
-				- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
-			5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
-			`}
-			inline={false}
-		/>
-	</>
+<>
+
+    	<Markdown
+    		text={`
+    		1. Go to the **Network health** page.
+    			`}
+    		inline={false}
+    	/>
+
+    	<DashButton url="/?to=/:account/networking-insights/health" />
+
+    	<Markdown
+    		text={`
+    		2. Select the **Connector health** tab.
+    		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+    		4. Find the tunnel you want to inspect, select the three dots next to it, and select:
+    			- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
+    			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
+    		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
+    		`}
+    		inline={false}
+    	/>
+    </>
+
 )
 }
 
@@ -69,48 +76,50 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 You can drill down into a specific tunnel to check its health status and other information.
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-	<>
-	<Markdown
-		text={`
+<>
+<Markdown
+text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		`}
-		inline={false}
-	/>
-	</>
+inline={false}
+/>
+</>
 ) : (
-	<>
+<>
 
-	<Markdown
-			text={`
-			1. Go to the **Network health** page.
-				`}
-			inline={false}
-		/>
+    <Markdown
+    		text={`
+    		1. Go to the **Network health** page.
+    			`}
+    		inline={false}
+    	/>
 
-	<DashButton url="/?to=/:account/networking-insights/health" />
+    <DashButton url="/?to=/:account/networking-insights/health" />
 
-	<Markdown
-			text={`
-2. Select the **Connector health** tab.
-			`}
-			inline={false}
-		/>
-	</>
-)
-}
+    <Markdown
+    		text={`
 
+2. Select the **Connector health** tab.
+   `}
+   inline={false}
+   />
+   </>
+   )
+   }
 
 3. Find and select the tunnel you want to inspect.
 
 The next view displays detailed information about the tunnel, including:
+
 - Status information
-	- Up: More than 80% of health checks pass.
-	- Degraded: More than 40% of health checks pass.
-	- Down: Less than 40% of health checks pass.
+  - Up: More than 80% of health checks pass.
+  - Degraded: More than 40% of health checks pass.
+  - Down: Less than 40% of health checks pass.
 - Health checks passed in the last hour
 - Traffic volume in the last hour
 
 If you select the three dots in front of the tunnel you want to inspect, you have access to the following tools:
+
 - Packet captures: Collect <a href={props.packetCaptures}>packet level data for your traffic</a>
 - Network Analytics: Leverage real-time insights into <a href={props.networkAnalytics}>network analytics</a>.
diff --git a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
index 7b2222fb7119eaf..40f78d258f68ce4 100644
--- a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
+++ b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
@@ -5,4 +5,4 @@ params:
 
 :::note
 {props.productName} customers with [Customer Metadata Boundary](/data-localization/metadata-boundary/) enabled for the European Union can access GRE, IPsec, and CNI (Cloudflare Network Interconnect) health check and traffic volume data in the Cloudflare dashboard and through the API. This ensures that customers who need to be General Data Protection Regulation (GDPR) compliant can access all {props.productName} features.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
index d9eecdf681026ce..a4314a796e274e0 100644
--- a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
+++ b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
@@ -8,14 +8,14 @@ params:
 ---
 
 import {
-  APIRequest,
-  Code,
-  Details,
-  GlossaryTooltip,
-  Render,
-  Tabs,
-  TabItem,
-  DashButton,
+	APIRequest,
+	Code,
+	Details,
+	GlossaryTooltip,
+	Render,
+	Tabs,
+	TabItem,
+	DashButton,
 } from "~/components";
 
 You can configure Tunnel Health Alerts (formerly Magic Tunnel health alerts) to receive email, webhook, and PagerDuty notifications when the percentage of successful <GlossaryTooltip term="tunnel health-check">health checks</GlossaryTooltip> for an IPsec/GRE tunnel drops below the selected <a href={props.magicTunnelHealthCheckCalculation}>service-level objective (SLO)</a>.
@@ -42,14 +42,14 @@ Currently, there are seven SLO threshold values that you can configure through t
 The SLO threshold for Tunnel health alerts is the percentage of successful health checks for each IPsec/GRE tunnel in the alert:
 
 | Alert Sensitivity Level | SLO threshold |
-| --- 										| --- 					|
-| Minimum 								| 95.0 					|
-| Very low 								| 96.0					|
-| Low 										| 97.0 					|
-| Medium 									| 98.0 					|
-| High 										| 99.0 					|
-| Very high 							| 99.5					|
-| Maximum 								| 99.9					|
+| ----------------------- | ------------- |
+| Minimum                 | 95.0          |
+| Very low                | 96.0          |
+| Low                     | 97.0          |
+| Medium                  | 98.0          |
+| High                    | 99.0          |
+| Very high               | 99.5          |
+| Maximum                 | 99.9          |
 
 The time it takes to receive alerts depends on the sensitivity level you configure for your SLO thresholds. Higher sensitivity levels notify you faster when a tunnel's health degrades, but they may also trigger alerts for brief or minor disruptions. Lower sensitivity levels reduce the chance of false alarms but may delay notifications for less severe issues.
 
@@ -57,7 +57,6 @@ While the underlying detection timing remains consistent across sensitivity leve
 
 For details, refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Tunnel health alerts</a>.
 
-
 ## Set up Tunnel Health Alerts
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
index 87ae557ab8ac1a5..be3e95d154d505a 100644
--- a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
@@ -5,4 +5,4 @@ params:
 
 Cloudflare One Appliance (formerly Magic WAN Connector) also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare through HTTPS and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
-Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
\ No newline at end of file
+Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
diff --git a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
index 83373e4b20668f6..a3df68499495d50 100644
--- a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
@@ -19,15 +19,15 @@ This guide helps you diagnose and resolve common tunnel health issues with {prop
 
 Use the following table to match your symptom to the most likely cause and first action:
 
-| Symptom | Most likely cause | First action |
-| :------ | :---------------- | :----------- |
-| Tunnel shows Down, never becomes healthy | Configuration mismatch or firewall blocking IKE | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures). |
-| Dashboard shows "100% degraded" for some colos | Normal — this is a state indicator, not packet loss | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard). |
-| Tunnel flaps between healthy and unhealthy | Anti-replay protection or rekey disruption | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops). |
-| Health checks fail but traffic flows normally | Stateful firewall dropping health check probes | Change health check type from *Reply* to *Request*. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
-| Health checks fail on policy-based VPN tunnels | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
-| All tunnels degraded or down in a specific region | Network path issue between that region and your network | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare. |
-| All tunnels degraded or down globally | Issue at your network edge | Check your tunnel endpoint router and upstream connectivity. |
+| Symptom                                           | Most likely cause                                         | First action                                                                                                                                        |
+| :------------------------------------------------ | :-------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Tunnel shows Down, never becomes healthy          | Configuration mismatch or firewall blocking IKE           | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures).                    |
+| Dashboard shows "100% degraded" for some colos    | Normal — this is a state indicator, not packet loss       | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard).              |
+| Tunnel flaps between healthy and unhealthy        | Anti-replay protection or rekey disruption                | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops).                      |
+| Health checks fail but traffic flows normally     | Stateful firewall dropping health check probes            | Change health check type from _Reply_ to _Request_. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
+| Health checks fail on policy-based VPN tunnels    | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
+| All tunnels degraded or down in a specific region | Network path issue between that region and your network   | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare.                                                          |
+| All tunnels degraded or down globally             | Issue at your network edge                                | Check your tunnel endpoint router and upstream connectivity.                                                                                        |
 
 ### What you can check
 
@@ -46,7 +46,7 @@ Use the following table to match your symptom to the most likely cause and first
 
 If you are experiencing tunnel health issues, check these items first:
 
-1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from *Reply* to *Request*.
+1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from _Reply_ to _Request_.
 2. **Anti-replay protection**: Disable anti-replay protection on your router, or set the replay window to `0`.
 3. **MTU settings**: Verify MTU is set correctly (typically `1476` for GRE, `1400`-`1450` for IPsec).
 4. **IPsec parameters**: Confirm your cryptographic parameters match <a href={props.tunnelsConfigLink}>Cloudflare's supported configuration</a>.
@@ -59,11 +59,11 @@ If you are experiencing tunnel health issues, check these items first:
 
 The [Network health](https://dash.cloudflare.com/?to=/:account/networking-insights/health) page in the Cloudflare dashboard displays three tunnel health states:
 
-| State | Dashboard display | Technical threshold |
-| :---- | :---- | :---- |
-| **Healthy** | More than 80% of health checks pass | Less than 0.1% failure rate |
+| State        | Dashboard display                         | Technical threshold                                                |
+| :----------- | :---------------------------------------- | :----------------------------------------------------------------- |
+| **Healthy**  | More than 80% of health checks pass       | Less than 0.1% failure rate                                        |
 | **Degraded** | Between 40% and 80% of health checks pass | At least 0.1% failures in last five minutes (minimum two failures) |
-| **Down** | Less than 40% of health checks pass | All health checks failed (at least three samples in last second) |
+| **Down**     | Less than 40% of health checks pass       | All health checks failed (at least three samples in last second)   |
 
 The dashboard shows tunnel health as measured from each Cloudflare data center where your traffic lands. It is normal to see some locations reporting degraded status due to Internet path issues. Focus on locations that show traffic in the **Traffic volume (1h)** column.
 
@@ -122,16 +122,16 @@ For instructions on monitoring tunnel status, refer to <a href={props.checkHealt
 
 **Health check type:**
 
-| Type | Behavior | When to use |
-| :---- | :---- | :---- |
-| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls |
-| **Request** | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
+| Type                | Behavior                              | When to use                                                         |
+| :------------------ | :------------------------------------ | :------------------------------------------------------------------ |
+| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls                          |
+| **Request**         | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
 
 **Health check direction:**
 
-| Direction | Behavior | Default for |
-| :---- | :---- | :--- |
-| **Bidirectional** | Probe and response both traverse the tunnel | Cloudflare WAN (formerly Magic WAN) |
+| Direction          | Behavior                                              | Default for                          |
+| :----------------- | :---------------------------------------------------- | :----------------------------------- |
+| **Bidirectional**  | Probe and response both traverse the tunnel           | Cloudflare WAN (formerly Magic WAN)  |
 | **Unidirectional** | Probe traverses tunnel; response returns via Internet | Magic Transit (direct server return) |
 
 :::note
@@ -152,23 +152,23 @@ Unidirectional health checks can be unreliable because intermediate network devi
 
 #### Cause
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP *Reply* packets as health check probes.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP _Reply_ packets as health check probes.
 
-Stateful firewalls inspect these packets and look for a matching ICMP *Request* in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
+Stateful firewalls inspect these packets and look for a matching ICMP _Request_ in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
 
 #### Solution
 
-Change the health check type from *Reply* to *Request*:
+Change the health check type from _Reply_ to _Request_:
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on the affected tunnel.
-3. Under **Health check type**, change from *Reply* to *Request*.
+3. Under **Health check type**, change from _Reply_ to _Request_.
 4. Select **Update tunnel**.
 
-When you use *Request* style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
+When you use _Request_ style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
 
 :::note
 If your firewall drops ICMP request packets as well, verify that your firewall policy permits ICMP traffic on the tunnel interface.
@@ -190,21 +190,21 @@ Cloudflare Network Firewall processes all traffic, including Cloudflare's health
 
 #### Solution
 
-Add an allow rule for ICMP traffic from Cloudflare IP addresses *before* any block rules:
+Add an allow rule for ICMP traffic from Cloudflare IP addresses _before_ any block rules:
 
 1. Go to the **Firewall policies** page.
 
-	<DashButton url="/?to=/:account/network-security/magic_firewall" />
+   <DashButton url="/?to=/:account/network-security/magic_firewall" />
 
 2. Create a new policy with the following parameters:
 
-| Field | Value |
-| :---- | :---- |
-| **Action** | Allow |
-| **Protocol** | ICMP |
-| **Source** | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
+| Field        | Value                                               |
+| :----------- | :-------------------------------------------------- |
+| **Action**   | Allow                                               |
+| **Protocol** | ICMP                                                |
+| **Source**   | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
 
-3. Position this rule *before* any rules that block ICMP traffic.
+3. Position this rule _before_ any rules that block ICMP traffic.
 
 For more information, refer to [Cloudflare Network Firewall rules and endpoint health checks](/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks).
 
@@ -246,7 +246,7 @@ Enable replay protection in the Cloudflare dashboard. This routes all tunnel tra
 
 1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
+   <DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on your IPsec tunnel.
 3. Enable **Replay protection**.
@@ -294,13 +294,11 @@ This behavior is expected and the tunnel will automatically recover. To minimize
 2. **Increase rekey intervals**: Configure longer SA lifetimes on your tunnel endpoint to reduce rekey frequency. Common values are 8-24 hours for IKE SA and 1-8 hours for IPsec SA.
 
 3. **Adjust health check sensitivity**: If brief degradation during rekeys triggers alerts, consider lowering the health check rate:
-
    1. Go to the **Connectors** page.
 
-	<DashButton url="/?to=/:account/magic-networks/connections" />
-
+   <DashButton url="/?to=/:account/magic-networks/connections" />
    2. In **IPsec/GRE tunnels**, select **Edit** on the tunnel.
-   3. Change **Health check rate** to *Low*.
+   3. Change **Health check rate** to _Low_.
 
 4. **Stagger rekey times**: If you have multiple tunnels, configure different SA lifetimes so they do not rekey simultaneously.
 
@@ -352,12 +350,12 @@ For detailed information on how bidirectional health checks work, refer to <a hr
 
 IPsec tunnel establishment can fail due to several configuration mismatches:
 
-| Issue | Symptom |
-| :---- | :---- |
+| Issue                         | Symptom                                         |
+| :---------------------------- | :---------------------------------------------- |
 | **Crypto parameter mismatch** | IKE negotiation fails with "no proposal chosen" |
-| **Incorrect PSK** | Authentication failures in Phase 1 |
-| **Wrong IKE ID format** | Authentication failures despite correct PSK |
-| **Firewall blocking IKE** | No IKE traffic reaches Cloudflare |
+| **Incorrect PSK**             | Authentication failures in Phase 1              |
+| **Wrong IKE ID format**       | Authentication failures despite correct PSK     |
+| **Firewall blocking IKE**     | No IKE traffic reaches Cloudflare               |
 
 #### Solution
 
@@ -365,24 +363,22 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 
    **Phase 1 (IKE)**
 
+| Parameter      | Supported values            |
+| :------------- | :-------------------------- |
+| IKE version    | IKEv2 only                  |
+| Encryption     | AES-GCM-16, AES-CBC-256     |
+| Authentication | SHA-256, SHA-384, SHA-512   |
+| DH Group       | DH group 14, 15, 16, 19, 20 |
 
-| Parameter | Supported values |
-| :---- | :---- |
-| IKE version | IKEv2 only |
-| Encryption | AES-GCM-16, AES-CBC-256 |
-| Authentication | SHA-256, SHA-384, SHA-512 |
-| DH Group | DH group 14, 15, 16, 19, 20 |
-
-   **Phase 2 (IPsec)**
+**Phase 2 (IPsec)**
 
-| Parameter | Supported values |
-| :---- | :---- |
-| Encryption | AES-GCM-16, AES-CBC-256 |
-| Authentication | SHA-256, SHA-512 |
-| PFS Group | DH group 14, 15, 16, 19, 20 |
+| Parameter      | Supported values            |
+| :------------- | :-------------------------- |
+| Encryption     | AES-GCM-16, AES-CBC-256     |
+| Authentication | SHA-256, SHA-512            |
+| PFS Group      | DH group 14, 15, 16, 19, 20 |
 
 2. **Verify the Pre-Shared Key (PSK):**
-
    - Regenerate the PSK in the Cloudflare dashboard
    - Copy the new PSK exactly (no extra spaces or characters)
    - Update your router with the new PSK
@@ -390,7 +386,6 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 3. **Check the IKE ID format:** Cloudflare uses FQDN format for the IKE ID. Ensure your router is configured to accept an FQDN peer identity. The FQDN is displayed in the tunnel details in the Cloudflare dashboard.
 
 4. **Verify firewall rules:** Ensure your edge firewall permits:
-
    - UDP port `500` (IKE)
    - UDP port `4500` (IKE NAT-T)
    - IP protocol `50` (ESP)
@@ -415,7 +410,7 @@ Additionally, some firewalls (such as Check Point) may flag Reply-style health c
 
 #### Solution
 
-1. Change the health check type from *Reply* to *Request*.
+1. Change the health check type from _Reply_ to _Request_.
 2. Configure a loopback address on your tunnel endpoint as the health check target. The target must be:
    - Routable from the tunnel endpoint
    - Covered by the tunnel's traffic selectors (encryption domain)
@@ -431,13 +426,13 @@ Policy-based tunnels use a separate Child SA for each set of traffic selectors.
 
 ### Common vendor-specific issues
 
-| Vendor | Common issue | Solution |
-| :---- | :---- | :---- |
-| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to *Request*; disable anti-replay |
-| **Cisco Meraki** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **AWS VPN Gateway** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **VeloCloud** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
-| **Check Point** | Out-of-state packet drops | Change health check type to *Request* |
+| Vendor                 | Common issue                             | Solution                                                   |
+| :--------------------- | :--------------------------------------- | :--------------------------------------------------------- |
+| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to _Request_; disable anti-replay |
+| **Cisco Meraki**       | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **AWS VPN Gateway**    | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **VeloCloud**          | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
+| **Check Point**        | Out-of-state packet drops                | Change health check type to _Request_                      |
 
 ---
 
@@ -484,8 +479,13 @@ Collect output from these commands (syntax varies by vendor):
 
 ## Resources
 
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on health check behavior
-- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay must be disabled
-- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel setup instructions
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Dashboard navigation guide
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis tools
\ No newline at end of file
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
+  details on health check behavior
+- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay
+  must be disabled
+- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel
+  setup instructions
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
+  Dashboard navigation guide
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis
+  tools
diff --git a/src/content/partials/networking-services/virtual-networks-concept.mdx b/src/content/partials/networking-services/virtual-networks-concept.mdx
index bec7de23f758195..5f791ebd1962872 100644
--- a/src/content/partials/networking-services/virtual-networks-concept.mdx
+++ b/src/content/partials/networking-services/virtual-networks-concept.mdx
@@ -84,18 +84,21 @@ The same CIDR (`10.0.0.0/8`) can exist in each virtual network because they are
 
 Each virtual network maintains its own routing table. Routes added to one virtual network do not appear in another virtual network routing table. However, if traffic does not match a route in the selected virtual network, Cloudflare may fall back to the default virtual network routing table for WAN routes.
 
-<Markdown text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`} inline={false} />
+<Markdown
+	text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`}
+	inline={false}
+/>
 
 ## Virtual networks across Cloudflare
 
 Virtual network support varies by product:
 
-| Product | Virtual network support | Details |
-| --- | --- | --- |
-| Cloudflare Tunnel | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
-| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection |
-| Cloudflare Mesh | Not currently supported | — |
-| Cloudflare WAN | Default only | All IPsec, GRE, and CNI connections use the default virtual network |
+| Product               | Virtual network support   | Details                                                              |
+| --------------------- | ------------------------- | -------------------------------------------------------------------- |
+| Cloudflare Tunnel     | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
+| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection  |
+| Cloudflare Mesh       | Not currently supported   | —                                                                    |
+| Cloudflare WAN        | Default only              | All IPsec, GRE, and CNI connections use the default virtual network  |
 
 ## The default virtual network
 
@@ -120,14 +123,26 @@ If you are familiar with cloud networking concepts, a virtual network is analogo
 
 ## Create and manage virtual networks
 
-<Markdown text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`} inline={false} />
+<Markdown
+	text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`}
+	inline={false}
+/>
 
-<Markdown text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`} inline={false} />
+<Markdown
+	text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`}
+	inline={false}
+/>
 
-<Markdown text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`} inline={false} />
+<Markdown
+	text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`}
+	inline={false}
+/>
 
 ## Related resources
 
-<Markdown text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
+<Markdown
+	text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
 - [Routes](${props.routesURL}) — Define IP and hostname routes through your connectors
-- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`} inline={false} />
+- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`}
+	inline={false}
+/>
diff --git a/src/content/partials/notifications/get-started.mdx b/src/content/partials/notifications/get-started.mdx
index 00b7b4ec3a8f058..829b54d50c6d7ad 100644
--- a/src/content/partials/notifications/get-started.mdx
+++ b/src/content/partials/notifications/get-started.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Refer to [Cloudflare Notifications](/notifications/get-started/) for more information on how to set up an alert.
diff --git a/src/content/partials/pages/c3-adapter.mdx b/src/content/partials/pages/c3-adapter.mdx
index a38fe66ad454db8..32d2a3499fce337 100644
--- a/src/content/partials/pages/c3-adapter.mdx
+++ b/src/content/partials/pages/c3-adapter.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If using [`create-cloudflare` (C3)](https://www.npmjs.com/package/create-cloudflare), you can bypass adding an adapter as C3 automatically installs any necessary adapters and configures them when creating your project.
 
-
 :::
diff --git a/src/content/partials/pages/c3-run-command-no-directory.mdx b/src/content/partials/pages/c3-run-command-no-directory.mdx
index a64961aff54a926..193d0bcd558150b 100644
--- a/src/content/partials/pages/c3-run-command-no-directory.mdx
+++ b/src/content/partials/pages/c3-run-command-no-directory.mdx
@@ -4,5 +4,8 @@
 
 import { PackageManagers } from "~/components";
 
-<PackageManagers type="create" pkg="cloudflare@latest" args="--platform=pages"/>
-
+<PackageManagers
+	type="create"
+	pkg="cloudflare@latest"
+	args="--platform=pages"
+/>
diff --git a/src/content/partials/pages/cli-precedence-over-file.mdx b/src/content/partials/pages/cli-precedence-over-file.mdx
index 11a0cb2f0ebfdd4..b2bc3188eee261f 100644
--- a/src/content/partials/pages/cli-precedence-over-file.mdx
+++ b/src/content/partials/pages/cli-precedence-over-file.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If a binding is specified in a [Wrangler configuration file](/workers/wrangler/configuration/) and via a command-line argument, the command-line argument takes precedence.
 
-
 :::
diff --git a/src/content/partials/pages/custom-domain-steps.mdx b/src/content/partials/pages/custom-domain-steps.mdx
index fee5e4c0dbb152c..20c18cb6fc838aa 100644
--- a/src/content/partials/pages/custom-domain-steps.mdx
+++ b/src/content/partials/pages/custom-domain-steps.mdx
@@ -9,6 +9,7 @@ To add a custom domain:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Custom domains**.
 3. Select **Set up a domain**.
 4. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
index 62859ea9b7e533e..953960ee01038c9 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
@@ -9,6 +9,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
index f70be8044a5cf71..b8561649554de9d 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
@@ -10,6 +10,7 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/do-note.mdx b/src/content/partials/pages/do-note.mdx
index 44f90d7ff7a4785..6490baa6181c199 100644
--- a/src/content/partials/pages/do-note.mdx
+++ b/src/content/partials/pages/do-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You must create a Durable Object Worker and bind it to your Pages project using the Cloudflare dashboard or your Pages project's [Wrangler configuration file](/pages/functions/wrangler-configuration/). You cannot create and deploy a Durable Object within a Pages project.
diff --git a/src/content/partials/pages/framework-guides/create-gh-repo.mdx b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
index 7d4f7ac729dd198..8e6a0ec2e677e3a 100644
--- a/src/content/partials/pages/framework-guides/create-gh-repo.mdx
+++ b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Create a new GitHub repository by visiting [repo.new](https://repo.new). After creating a new repository, go to your newly created project directory to prepare and push your local application to GitHub by running the following commands in your terminal:
diff --git a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
index 46eb8a378cb57e1..9f8e802cee2e978 100644
--- a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
+++ b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Create a GitHub repository
diff --git a/src/content/partials/pages/framework-guides/git-integration.mdx b/src/content/partials/pages/framework-guides/git-integration.mdx
index b904fe727721313..ce38fa80e780d15 100644
--- a/src/content/partials/pages/framework-guides/git-integration.mdx
+++ b/src/content/partials/pages/framework-guides/git-integration.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Git integration
 
diff --git a/src/content/partials/pages/framework-guides/learn-more.mdx b/src/content/partials/pages/framework-guides/learn-more.mdx
index 412a7475b5f45d7..875e06f11937b9d 100644
--- a/src/content/partials/pages/framework-guides/learn-more.mdx
+++ b/src/content/partials/pages/framework-guides/learn-more.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: deployedTarget
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 ## Learn more
 
diff --git a/src/content/partials/pages/get-started-git-connect-pages.mdx b/src/content/partials/pages/get-started-git-connect-pages.mdx
index 9f0e08f89c4e2e7..e2b68a6f9b7f3cc 100644
--- a/src/content/partials/pages/get-started-git-connect-pages.mdx
+++ b/src/content/partials/pages/get-started-git-connect-pages.mdx
@@ -9,18 +9,17 @@ Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitl
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select **Create application** > **Pages** > **Connect to Git**.
 
 You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/).
 
 :::note
 
-
 Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages.
 
 If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages.
 
-
 :::
 
 ### Select your GitHub repository
@@ -29,4 +28,4 @@ You can select a GitHub project from your personal account or an organization yo
 
 ### Select your GitLab repository
 
-If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
\ No newline at end of file
+If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
diff --git a/src/content/partials/pages/get-started-git-manage-site.mdx b/src/content/partials/pages/get-started-git-manage-site.mdx
index 0aa235c6ce61425..6be5dbe386c0e10 100644
--- a/src/content/partials/pages/get-started-git-manage-site.mdx
+++ b/src/content/partials/pages/get-started-git-manage-site.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import {DashButton} from "~/components";
+import { DashButton } from "~/components";
 
 After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments.
 
@@ -15,16 +15,15 @@ To delete your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project > **Settings** > **Delete project**.
 
 :::caution
 
-
 For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions.
 
 For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings.
 
-
 :::
 
 ## Advanced project settings
@@ -33,6 +32,6 @@ In the **Settings** section, you can configure advanced settings, such as changi
 
 ## Related resources
 
-* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
-* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
-* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
\ No newline at end of file
+- Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
+- Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
+- Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
diff --git a/src/content/partials/pages/git-integration-warning.mdx b/src/content/partials/pages/git-integration-warning.mdx
index fe22fd4c858b9dd..29972cbf983d1e4 100644
--- a/src/content/partials/pages/git-integration-warning.mdx
+++ b/src/content/partials/pages/git-integration-warning.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Git integration]
 
-
 Currently, you cannot add Git integration to existing Pages applications. If you have already deployed your application, you need to create a new Pages application in order to add Git integration to it.
 
-
 :::
diff --git a/src/content/partials/pages/prod-branch-update.mdx b/src/content/partials/pages/prod-branch-update.mdx
index 09fee36fe5dc103..cc5195454fc9ea4 100644
--- a/src/content/partials/pages/prod-branch-update.mdx
+++ b/src/content/partials/pages/prod-branch-update.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your project is a [Direct Upload](/pages/get-started/direct-upload/) project, you will not have the option to configure production branch controls. To update your production branch, you will need to manually call the [Update Project](/api/resources/pages/subresources/projects/methods/edit/) endpoint in the API.
diff --git a/src/content/partials/pages/tutorials-before-you-start.mdx b/src/content/partials/pages/tutorials-before-you-start.mdx
index 054f3014bbb4e20..828e29a27d7e760 100644
--- a/src/content/partials/pages/tutorials-before-you-start.mdx
+++ b/src/content/partials/pages/tutorials-before-you-start.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Before you continue
diff --git a/src/content/partials/pages/web-analytics-setup.mdx b/src/content/partials/pages/web-analytics-setup.mdx
index 0c4d814773e0860..5b7a79ede654b56 100644
--- a/src/content/partials/pages/web-analytics-setup.mdx
+++ b/src/content/partials/pages/web-analytics-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -8,6 +7,7 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your Pages project.
 3. Go to **Metrics** and select **Enable** under Web Analytics.
 
diff --git a/src/content/partials/queues/enable-queues.mdx b/src/content/partials/queues/enable-queues.mdx
index 5d055261c9dc78a..2abc709865461de 100644
--- a/src/content/partials/queues/enable-queues.mdx
+++ b/src/content/partials/queues/enable-queues.mdx
@@ -12,6 +12,6 @@ To enable Queues:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-	 <DashButton url="/?to=/:account/workers/queues" />
+   <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select **Enable Queues**.
diff --git a/src/content/partials/queues/event-subscriptions/access-events.mdx b/src/content/partials/queues/event-subscriptions/access-events.mdx
index fc76184e339a0ed..9f74f1279bcec9a 100644
--- a/src/content/partials/queues/event-subscriptions/access-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/access-events.mdx
@@ -6,20 +6,20 @@ Triggered when an application is created.
 
 ```json
 {
-  "type": "cf.access.application.created",
-  "source": {
-    "type": "access"
-  },
-  "payload": {
-    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "My Application"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.access.application.created",
+	"source": {
+		"type": "access"
+	},
+	"payload": {
+		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "My Application"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when an application is deleted.
 
 ```json
 {
-  "type": "cf.access.application.deleted",
-  "source": {
-    "type": "access"
-  },
-  "payload": {
-    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "My Application"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.access.application.deleted",
+	"source": {
+		"type": "access"
+	},
+	"payload": {
+		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "My Application"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
index 520d32a2d17b86f..e25f2024c3d7d08 100644
--- a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
@@ -8,27 +8,27 @@ Triggered when a repository is created.
 
 ```json
 {
-  "type": "cf.artifacts.repo.created",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "0tvugavnogssnwzk",
-    "defaultBranch": "main",
-    "description": "My Artifacts repository",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:46.833Z",
-    "updatedAt": "2026-05-18T15:53:46.833Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:48.187Z"
-  }
+	"type": "cf.artifacts.repo.created",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "0tvugavnogssnwzk",
+		"defaultBranch": "main",
+		"description": "My Artifacts repository",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:46.833Z",
+		"updatedAt": "2026-05-18T15:53:46.833Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:48.187Z"
+	}
 }
 ```
 
@@ -40,27 +40,27 @@ Triggered when a repository is deleted.
 
 ```json
 {
-  "type": "cf.artifacts.repo.deleted",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "0tvugavnogssnwzk",
-    "defaultBranch": "main",
-    "description": "My Artifacts repository",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:46.833Z",
-    "updatedAt": "2026-05-18T15:53:46.833Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:59.914Z"
-  }
+	"type": "cf.artifacts.repo.deleted",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "0tvugavnogssnwzk",
+		"defaultBranch": "main",
+		"description": "My Artifacts repository",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:46.833Z",
+		"updatedAt": "2026-05-18T15:53:46.833Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:59.914Z"
+	}
 }
 ```
 
@@ -72,29 +72,29 @@ Triggered when a repository is forked.
 
 ```json
 {
-  "type": "cf.artifacts.repo.forked",
-  "source": {
-    "type": "artifacts",
-    "namespace": "source-namespace",
-    "repoName": "source-repo"
-  },
-  "payload": {
-    "namespace": "target-namespace",
-    "repoName": "target-repo",
-    "repoId": "5ankv1vhl4xnw7wq",
-    "defaultBranch": "main",
-    "description": "Fork of source-repo",
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:52.384Z",
-    "updatedAt": "2026-05-18T15:53:54.579Z",
-    "lastPushAt": null
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:54.641Z"
-  }
+	"type": "cf.artifacts.repo.forked",
+	"source": {
+		"type": "artifacts",
+		"namespace": "source-namespace",
+		"repoName": "source-repo"
+	},
+	"payload": {
+		"namespace": "target-namespace",
+		"repoName": "target-repo",
+		"repoId": "5ankv1vhl4xnw7wq",
+		"defaultBranch": "main",
+		"description": "Fork of source-repo",
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:52.384Z",
+		"updatedAt": "2026-05-18T15:53:54.579Z",
+		"lastPushAt": null
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:54.641Z"
+	}
 }
 ```
 
@@ -106,29 +106,29 @@ Triggered when a repository is imported from an external Git remote.
 
 ```json
 {
-  "type": "cf.artifacts.repo.imported",
-  "source": {
-    "type": "artifacts",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "repoId": "d7nd72k964cv9kub",
-    "defaultBranch": "main",
-    "description": null,
-    "readOnly": false,
-    "createdAt": "2026-05-18T15:53:54.864Z",
-    "updatedAt": "2026-05-18T15:53:57.737Z",
-    "lastPushAt": null,
-    "sourceUrl": "https://github.com/example/repo.git",
-    "branch": "main"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:58.195Z"
-  }
+	"type": "cf.artifacts.repo.imported",
+	"source": {
+		"type": "artifacts",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"repoId": "d7nd72k964cv9kub",
+		"defaultBranch": "main",
+		"description": null,
+		"readOnly": false,
+		"createdAt": "2026-05-18T15:53:54.864Z",
+		"updatedAt": "2026-05-18T15:53:57.737Z",
+		"lastPushAt": null,
+		"sourceUrl": "https://github.com/example/repo.git",
+		"branch": "main"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:58.195Z"
+	}
 }
 ```
 
@@ -142,44 +142,42 @@ Triggered when commits are pushed to a repository.
 
 ```json
 {
-  "type": "cf.artifacts.repo.pushed",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {
-    "ref": "refs/heads/main",
-    "before": "abc123def456abc123def456abc123def456abc1",
-    "after": "def789ghi012def789ghi012def789ghi012def7",
-    "commits": [
-      {
-        "id": "def789ghi012def789ghi012def789ghi012def7",
-        "message": "Fix bug in authentication",
-        "messageTruncated": false,
-        "timestamp": "2025-05-01T02:48:57.000Z",
-        "author": {
-          "name": "Developer Name",
-          "email": "developer@example.com"
-        },
-        "committer": {
-          "name": "Developer Name",
-          "email": "developer@example.com"
-        },
-        "parents": [
-          "abc123def456abc123def456abc123def456abc1"
-        ]
-      }
-    ],
-    "totalCommitsCount": 1,
-    "commitsTruncated": false
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.artifacts.repo.pushed",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {
+		"ref": "refs/heads/main",
+		"before": "abc123def456abc123def456abc123def456abc1",
+		"after": "def789ghi012def789ghi012def789ghi012def7",
+		"commits": [
+			{
+				"id": "def789ghi012def789ghi012def789ghi012def7",
+				"message": "Fix bug in authentication",
+				"messageTruncated": false,
+				"timestamp": "2025-05-01T02:48:57.000Z",
+				"author": {
+					"name": "Developer Name",
+					"email": "developer@example.com"
+				},
+				"committer": {
+					"name": "Developer Name",
+					"email": "developer@example.com"
+				},
+				"parents": ["abc123def456abc123def456abc123def456abc1"]
+			}
+		],
+		"totalCommitsCount": 1,
+		"commitsTruncated": false
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -191,19 +189,19 @@ Triggered when a repository is cloned.
 
 ```json
 {
-  "type": "cf.artifacts.repo.cloned",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {},
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:51.358Z"
-  }
+	"type": "cf.artifacts.repo.cloned",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:51.358Z"
+	}
 }
 ```
 
@@ -215,19 +213,19 @@ Triggered when updates are fetched from a repository.
 
 ```json
 {
-  "type": "cf.artifacts.repo.fetched",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "my-namespace",
-    "repoName": "my-repo"
-  },
-  "payload": {},
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-18T15:53:51.358Z"
-  }
+	"type": "cf.artifacts.repo.fetched",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "my-namespace",
+		"repoName": "my-repo"
+	},
+	"payload": {},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-18T15:53:51.358Z"
+	}
 }
 ```
 
@@ -239,23 +237,23 @@ Triggered when a repo-scoped token is created. Includes the token ID, scope, and
 
 ```json
 {
-  "type": "cf.artifacts.repo.token.created",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "default",
-    "repoName": "token-evt-repo"
-  },
-  "payload": {
-    "tokenId": "7ngdf3ww3u84t33x",
-    "scope": "read",
-    "expiresAt": "2026-05-20T16:58:14.548Z"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-20T16:58:14.548Z"
-  }
+	"type": "cf.artifacts.repo.token.created",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "default",
+		"repoName": "token-evt-repo"
+	},
+	"payload": {
+		"tokenId": "7ngdf3ww3u84t33x",
+		"scope": "read",
+		"expiresAt": "2026-05-20T16:58:14.548Z"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-20T16:58:14.548Z"
+	}
 }
 ```
 
@@ -267,20 +265,20 @@ Triggered when a repo-scoped token is revoked. Includes the token ID.
 
 ```json
 {
-  "type": "cf.artifacts.repo.token.revoked",
-  "source": {
-    "type": "artifacts.repo",
-    "namespace": "default",
-    "repoName": "token-evt-repo"
-  },
-  "payload": {
-    "tokenId": "7ngdf3ww3u84t33x"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2026-05-20T16:58:14.548Z"
-  }
+	"type": "cf.artifacts.repo.token.revoked",
+	"source": {
+		"type": "artifacts.repo",
+		"namespace": "default",
+		"repoName": "token-evt-repo"
+	},
+	"payload": {
+		"tokenId": "7ngdf3ww3u84t33x"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2026-05-20T16:58:14.548Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/kv-events.mdx b/src/content/partials/queues/event-subscriptions/kv-events.mdx
index 41f5c1399c2dda4..e824a2a4d79909a 100644
--- a/src/content/partials/queues/event-subscriptions/kv-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/kv-events.mdx
@@ -6,20 +6,20 @@ Triggered when a namespace is created.
 
 ```json
 {
-  "type": "cf.kv.namespace.created",
-  "source": {
-    "type": "kv"
-  },
-  "payload": {
-    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "my-kv-namespace"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.kv.namespace.created",
+	"source": {
+		"type": "kv"
+	},
+	"payload": {
+		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "my-kv-namespace"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when a namespace is deleted.
 
 ```json
 {
-  "type": "cf.kv.namespace.deleted",
-  "source": {
-    "type": "kv"
-  },
-  "payload": {
-    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-    "name": "my-kv-namespace"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.kv.namespace.deleted",
+	"source": {
+		"type": "kv"
+	},
+	"payload": {
+		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+		"name": "my-kv-namespace"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/r2-events.mdx b/src/content/partials/queues/event-subscriptions/r2-events.mdx
index b50d8c3a1c19d49..30261e144e2610c 100644
--- a/src/content/partials/queues/event-subscriptions/r2-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/r2-events.mdx
@@ -6,22 +6,22 @@ Triggered when a bucket is created.
 
 ```json
 {
-  "type": "cf.r2.bucket.created",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "jurisdiction": "default",
-    "location": "WNAM",
-    "storageClass": "Standard"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.r2.bucket.created",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"jurisdiction": "default",
+		"location": "WNAM",
+		"storageClass": "Standard"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -33,19 +33,19 @@ Triggered when a bucket is deleted.
 
 ```json
 {
-  "type": "cf.r2.bucket.deleted",
-  "source": {
-    "type": "r2"
-  },
-  "payload": {
-    "name": "my-bucket",
-    "jurisdiction": "default"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.r2.bucket.deleted",
+	"source": {
+		"type": "r2"
+	},
+	"payload": {
+		"name": "my-bucket",
+		"jurisdiction": "default"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
index 4cae246e7055fa3..0cb885462b37f7b 100644
--- a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
@@ -6,33 +6,33 @@ Triggered when a migration job starts.
 
 ```json
 {
-  "type": "cf.superSlurper.job.started",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "overwrite": true,
-    "pathPrefix": "migrations/",
-    "source": {
-      "provider": "s3",
-      "bucket": "source-bucket",
-      "region": "us-east-1",
-      "endpoint": "s3.amazonaws.com"
-    },
-    "destination": {
-      "provider": "r2",
-      "bucket": "destination-bucket",
-      "jurisdiction": "default"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.started",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"overwrite": true,
+		"pathPrefix": "migrations/",
+		"source": {
+			"provider": "s3",
+			"bucket": "source-bucket",
+			"region": "us-east-1",
+			"endpoint": "s3.amazonaws.com"
+		},
+		"destination": {
+			"provider": "r2",
+			"bucket": "destination-bucket",
+			"jurisdiction": "default"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -44,19 +44,19 @@ Triggered when a migration job pauses.
 
 ```json
 {
-  "type": "cf.superSlurper.job.paused",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.paused",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -68,19 +68,19 @@ Triggered when a migration job resumes.
 
 ```json
 {
-  "type": "cf.superSlurper.job.resumed",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.resumed",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -92,23 +92,23 @@ Triggered when a migration job finishes.
 
 ```json
 {
-  "type": "cf.superSlurper.job.completed",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "totalObjectsCount": 1000,
-    "skippedObjectsCount": 10,
-    "migratedObjectsCount": 980,
-    "failedObjectsCount": 10
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.completed",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"totalObjectsCount": 1000,
+		"skippedObjectsCount": 10,
+		"migratedObjectsCount": 980,
+		"failedObjectsCount": 10
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -120,23 +120,23 @@ Triggered when a migration job is manually aborted.
 
 ```json
 {
-  "type": "cf.superSlurper.job.aborted",
-  "source": {
-    "type": "superSlurper"
-  },
-  "payload": {
-    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
-    "totalObjectsCount": 1000,
-    "skippedObjectsCount": 100,
-    "migratedObjectsCount": 500,
-    "failedObjectsCount": 50
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.aborted",
+	"source": {
+		"type": "superSlurper"
+	},
+	"payload": {
+		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
+		"totalObjectsCount": 1000,
+		"skippedObjectsCount": 100,
+		"migratedObjectsCount": 500,
+		"failedObjectsCount": 50
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -148,19 +148,19 @@ Triggered when an object is migrated.
 
 ```json
 {
-  "type": "cf.superSlurper.job.object.migrated",
-  "source": {
-    "type": "superSlurper.job",
-    "jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "payload": {
-    "key": "migrations/file.txt"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.superSlurper.job.object.migrated",
+	"source": {
+		"type": "superSlurper.job",
+		"jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"payload": {
+		"key": "migrations/file.txt"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
index fbdfca03358751d..e9422149256d246 100644
--- a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
@@ -6,24 +6,24 @@ Triggered when an index is created.
 
 ```json
 {
-  "type": "cf.vectorize.index.created",
-  "source": {
-    "type": "vectorize"
-  },
-  "payload": {
-    "name": "my-vector-index",
-    "description": "Index for embeddings",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "modifiedAt": "2025-05-01T02:48:57.132Z",
-    "dimensions": 1536,
-    "metric": "cosine"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.vectorize.index.created",
+	"source": {
+		"type": "vectorize"
+	},
+	"payload": {
+		"name": "my-vector-index",
+		"description": "Index for embeddings",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"modifiedAt": "2025-05-01T02:48:57.132Z",
+		"dimensions": 1536,
+		"metric": "cosine"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -35,18 +35,18 @@ Triggered when an index is deleted.
 
 ```json
 {
-  "type": "cf.vectorize.index.deleted",
-  "source": {
-    "type": "vectorize"
-  },
-  "payload": {
-    "name": "my-vector-index"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.vectorize.index.deleted",
+	"source": {
+		"type": "vectorize"
+	},
+	"payload": {
+		"name": "my-vector-index"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
index 0353629c8d35492..c28ded25de74231 100644
--- a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
@@ -6,20 +6,20 @@ Triggered when a batch request is queued.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.queued",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.queued",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -31,20 +31,20 @@ Triggered when a batch request has completed.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.succeeded",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.succeeded",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -56,22 +56,22 @@ Triggered when a batch request has failed.
 
 ```json
 {
-  "type": "cf.workersAi.model.batch.failed",
-  "source": {
-    "type": "workersAi.model",
-    "modelName": "@cf/baai/bge-base-en-v1.5"
-  },
-  "payload": {
-    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
-    "message": "Model execution failed",
-    "internalCode": 5001,
-    "httpCode": 500
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersAi.model.batch.failed",
+	"source": {
+		"type": "workersAi.model",
+		"modelName": "@cf/baai/bge-base-en-v1.5"
+	},
+	"payload": {
+		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
+		"message": "Model execution failed",
+		"internalCode": 5001,
+		"httpCode": 500
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
index 5a30ffa88665135..c0f0508d1e6468e 100644
--- a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
@@ -6,39 +6,39 @@ Triggered when a build starts.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.started",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "running",
-    "buildOutcome": null,
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": null,
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.started",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "running",
+		"buildOutcome": null,
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": null,
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -50,39 +50,39 @@ Triggered when a build fails.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.failed",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "failed",
-    "buildOutcome": "failure",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:50:00.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.failed",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "failed",
+		"buildOutcome": "failure",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:50:00.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -94,39 +94,39 @@ Triggered when a build is canceled.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.canceled",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "canceled",
-    "buildOutcome": "canceled",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:49:30.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.canceled",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "canceled",
+		"buildOutcome": "canceled",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:49:30.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -138,38 +138,38 @@ Triggered when a build succeeds.
 
 ```json
 {
-  "type": "cf.workersBuilds.worker.build.succeeded",
-  "source": {
-    "type": "workersBuilds.worker",
-    "workerName": "my-worker"
-  },
-  "payload": {
-    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-    "status": "success",
-    "buildOutcome": "success",
-    "createdAt": "2025-05-01T02:48:57.132Z",
-    "initializingAt": "2025-05-01T02:48:58.132Z",
-    "runningAt": "2025-05-01T02:48:59.132Z",
-    "stoppedAt": "2025-05-01T02:50:15.132Z",
-    "buildTriggerMetadata": {
-      "buildTriggerSource": "push_event",
-      "branch": "main",
-      "commitHash": "abc123def456",
-      "commitMessage": "Fix bug in authentication",
-      "author": "developer@example.com",
-      "buildCommand": "npm run build",
-      "deployCommand": "wrangler deploy",
-      "rootDirectory": "/",
-      "repoName": "my-worker-repo",
-      "providerAccountName": "github-user",
-      "providerType": "github"
-    }
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workersBuilds.worker.build.succeeded",
+	"source": {
+		"type": "workersBuilds.worker",
+		"workerName": "my-worker"
+	},
+	"payload": {
+		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+		"status": "success",
+		"buildOutcome": "success",
+		"createdAt": "2025-05-01T02:48:57.132Z",
+		"initializingAt": "2025-05-01T02:48:58.132Z",
+		"runningAt": "2025-05-01T02:48:59.132Z",
+		"stoppedAt": "2025-05-01T02:50:15.132Z",
+		"buildTriggerMetadata": {
+			"buildTriggerSource": "push_event",
+			"branch": "main",
+			"commitHash": "abc123def456",
+			"commitMessage": "Fix bug in authentication",
+			"author": "developer@example.com",
+			"buildCommand": "npm run build",
+			"deployCommand": "wrangler deploy",
+			"rootDirectory": "/",
+			"repoName": "my-worker-repo",
+			"providerAccountName": "github-user",
+			"providerType": "github"
+		}
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workflows-events.mdx b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
index 3df38e1c77de3c5..6c814481a6dbed4 100644
--- a/src/content/partials/queues/event-subscriptions/workflows-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
@@ -6,21 +6,21 @@ Triggered when an instance was created and is awaiting execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.queued",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.queued",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -32,21 +32,21 @@ Triggered when an instance starts or resumes execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.started",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.started",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -58,21 +58,21 @@ Triggered when an instance pauses execution.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.paused",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.paused",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -84,21 +84,21 @@ Triggered when an instance step throws an error.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.errored",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.errored",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -110,21 +110,21 @@ Triggered when an instance is manually terminated.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.terminated",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.terminated",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
 
@@ -136,20 +136,20 @@ Triggered when an instance finishes execution successfully.
 
 ```json
 {
-  "type": "cf.workflows.workflow.instance.completed",
-  "source": {
-    "type": "workflows.workflow",
-    "workflowName": "my-workflow"
-  },
-  "payload": {
-    "versionId": "v1",
-    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-  },
-  "metadata": {
-    "accountId": "f9f79265f388666de8122cfb508d7776",
-    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-    "eventSchemaVersion": 1,
-    "eventTimestamp": "2025-05-01T02:48:57.132Z"
-  }
+	"type": "cf.workflows.workflow.instance.completed",
+	"source": {
+		"type": "workflows.workflow",
+		"workflowName": "my-workflow"
+	},
+	"payload": {
+		"versionId": "v1",
+		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+	},
+	"metadata": {
+		"accountId": "f9f79265f388666de8122cfb508d7776",
+		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+		"eventSchemaVersion": 1,
+		"eventTimestamp": "2025-05-01T02:48:57.132Z"
+	}
 }
 ```
diff --git a/src/content/partials/r2/custom-domain-steps.mdx b/src/content/partials/r2/custom-domain-steps.mdx
index f5c65596995f046..1b858090ebc584b 100644
--- a/src/content/partials/r2/custom-domain-steps.mdx
+++ b/src/content/partials/r2/custom-domain-steps.mdx
@@ -7,6 +7,7 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
+
 2. Select your bucket.
 3. Select **Settings**.
 4. Under **Custom Domains**, select **Add**.
diff --git a/src/content/partials/r2/link-to-workers-r2-api.mdx b/src/content/partials/r2/link-to-workers-r2-api.mdx
index c18ac02fda8ef0a..22e4c599d0521ab 100644
--- a/src/content/partials/r2/link-to-workers-r2-api.mdx
+++ b/src/content/partials/r2/link-to-workers-r2-api.mdx
@@ -4,4 +4,4 @@
 
 ## Other resources
 
-For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
\ No newline at end of file
+For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
diff --git a/src/content/partials/r2/migrator-etag-caveat.mdx b/src/content/partials/r2/migrator-etag-caveat.mdx
index 5b40fec510b86ec..134d0b7745e8eea 100644
--- a/src/content/partials/r2/migrator-etag-caveat.mdx
+++ b/src/content/partials/r2/migrator-etag-caveat.mdx
@@ -1,9 +1,8 @@
 ---
 inputParameters: param1
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 While R2's ETag generation is compatible with S3's during the regular course of operations, ETags are not guaranteed to be equal when an object is migrated using {props.one}.
 {props.one} makes autonomous decisions about the operations it uses when migrating objects to optimize for performance and network usage. It may choose to migrate an object in multiple parts, which affects [ETag calculation](/r2/objects/upload-objects/#etags).
diff --git a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
index 3767632424c95a7..1bdda7b3e476265 100644
--- a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
@@ -1,12 +1,13 @@
 ---
 {}
-
 ---
+
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
+
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/create-your-own-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/create-your-own-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
\ No newline at end of file
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
diff --git a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
index c50d7c9cec90a22..f74bb9079e70dd4 100644
--- a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
@@ -1,12 +1,13 @@
 ---
 {}
-
 ---
+
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
+
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/default-meeting-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/default-meeting-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
\ No newline at end of file
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
index 59cb825253d7aa7..87e72e9cc2d11a8 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
@@ -1,21 +1,22 @@
 ---
 {}
-
 ---
+
 ```js
 await meeting.connectedMeetings.deleteMeetings([
-  "MEETING_ID_TO_CLOSE_1",
-  "MEETING_ID_TO_CLOSE_2",
+	"MEETING_ID_TO_CLOSE_1",
+	"MEETING_ID_TO_CLOSE_2",
 ]);
 ```
+
 This would also trigger `stateUpdate` event updating the list of breakout rooms & participants.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
-  console.log("stateUpdate", {meetings, parentMeeting});
+meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
+	console.log("stateUpdate", { meetings, parentMeeting });
 });
 
 // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
 console.log("Meetings List", meeting.connectedMeetings.meetings);
 console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
index f4af17e0a5883c0..7c577d42c671773 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
@@ -1,15 +1,20 @@
 ---
 {}
-
 ---
+
 ```js
 const breakoutRooms = await meeting.connectedMeetings.createMeetings([
-  { title: "Breakout Room 1" },
-  { title: "Breakout Room 2" },
-  { title: "Breakout Room 3" },
+	{ title: "Breakout Room 1" },
+	{ title: "Breakout Room 2" },
+	{ title: "Breakout Room 3" },
 ]);
 
-console.log("Created Breakout Rooms: ", breakoutRooms.map((room) => "Id:: " + room.id + " --- Title:: " + room.title).join("\n"));
+console.log(
+	"Created Breakout Rooms: ",
+	breakoutRooms
+		.map((room) => "Id:: " + room.id + " --- Title:: " + room.title)
+		.join("\n"),
+);
 ```
 
-`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
\ No newline at end of file
+`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
index dfde78c93ff676c..3047851f75d834f 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
@@ -1,10 +1,10 @@
 ---
 {}
-
 ---
 
 ```js
-const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo =
+	await meeting.connectedMeetings.getConnectedMeetings();
 ```
 
 `breakoutRoomsInfo` is an object containing the list of breakout rooms and their participants, along with details of the parent meeting.
@@ -14,11 +14,11 @@ This data can be used to display the list of breakout rooms & participants in th
 You can also listen to `stateUpdate` event to get the latest list of breakout rooms & participants, as they are updated in real-time.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
-  console.log("stateUpdate", {meetings, parentMeeting});
+meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
+	console.log("stateUpdate", { meetings, parentMeeting });
 
-  // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
-  console.log("Meetings List", meeting.connectedMeetings.meetings);
-  console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
+	// Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
+	console.log("Meetings List", meeting.connectedMeetings.meetings);
+	console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
 });
 ```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
index e10a85c8c58bf11..f77df15d7e5faa7 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
@@ -1,13 +1,16 @@
 ---
 {}
-
 ---
 
 ```js
 // Listen to changingMeeting event to show a custom UI to indicate that a meeting switch is happening
 meeting.connectedMeetings.on("changingMeeting", (meetingId) => {
-	console.log("Switching to breakout room or main meeting with id: " + meetingId);
-	console.log("Show a Custom UI to indicate that a meeting switch is happening");
+	console.log(
+		"Switching to breakout room or main meeting with id: " + meetingId,
+	);
+	console.log(
+		"Show a Custom UI to indicate that a meeting switch is happening",
+	);
 });
 
 // Listen to meetingChanged event to update the meeting object reference
@@ -15,4 +18,4 @@ meeting.connectedMeetings.on("meetingChanged", (newMeeting) => {
 	console.log("Switched to breakout room or main meeting");
 	console.log("Every action now should be performed on this meeting");
 });
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
index be50df93029763f..fbd4d918d2faf36 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
@@ -1,20 +1,21 @@
 ---
 {}
-
 ---
+
 ```js
 // Retrieve list of breakout rooms & participants
-const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo =
+	await meeting.connectedMeetings.getConnectedMeetings();
 
 /*
-* You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
-* Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
-*/
+ * You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
+ * Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
+ */
 
 // Move participants to breakout rooms
 const response = await meeting.connectedMeetings.moveParticipants(
-  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-  ["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
+	"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+	"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+	["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
 );
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
index 1491da6d62c305b..66e13a506f735ec 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
@@ -1,11 +1,12 @@
 ---
 {}
-
 ---
+
 ```js
-const response = await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
-  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-  [{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
-);
-```
\ No newline at end of file
+const response =
+	await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
+		"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+		"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+		[{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
+	);
+```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
index 40805bd8dd7ae50..796eed925700f90 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
@@ -1,20 +1,24 @@
 ---
 {}
-
 ---
+
 ```js
 // Check if breakout rooms are supported
-const areBreakoutRoomsSupported = meeting.connectedMeetings.supportsConnectedMeetings;
+const areBreakoutRoomsSupported =
+	meeting.connectedMeetings.supportsConnectedMeetings;
 
 // Check if any breakout rooms are already created
 const areBreakoutRoomsActive = meeting.connectedMeetings.isActive;
 
 // Check if the current participant has permission to create breakout rooms
-const hasPermissionToCreateBreakoutRooms = meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
+const hasPermissionToCreateBreakoutRooms =
+	meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
 
 // Check if the current participant has permission to switch to parent meeting
-const hasPermissionToSwitchToParentMeeting = meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
+const hasPermissionToSwitchToParentMeeting =
+	meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
 
 // Check if the current participant has permission to switch to connected meeting
-const hasPermissionToSwitchToConnectedMeeting = meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
-```
\ No newline at end of file
+const hasPermissionToSwitchToConnectedMeeting =
+	meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
+```
diff --git a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
index 7ecbc3317f46d23..e3f7d0532664f23 100644
--- a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
+++ b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
@@ -1,417 +1,417 @@
 ---
 {}
-
 ---
+
 ```json
 {
-  "about_call": "About Call",
-  "screen": "Screen",
-  "camera": "Camera",
-  "leave": "Leave",
-  "dismiss": "Dismiss",
-  "logo": "Logo",
-  "page": "Page",
-  "more": "More",
-  "page.prev": "Previous Page",
-  "page.next": "Next Page",
-  "layout": "Layout",
-  "layout.auto": "Auto Layout",
-  "settings": "Settings",
-  "file": "File",
-  "image": "Image",
-  "connection": "Connection",
-  "leave_confirmation": "Are you sure you want to leave the call?",
-  "cancel": "Cancel",
-  "yes": "Yes",
-  "(you)": "(you)",
-  "you": "You",
-  "everyone": "Everyone",
-  "to": "To",
-  "mute": "Mute",
-  "kick": "Kick",
-  "pin": "Pin",
-  "pinned": "Pinned",
-  "accept": "Accept",
-  "unpin": "Unpin",
-  "pip_on": "Show PiP",
-  "pip_off": "Hide PiP",
-  "viewers": "Viewers",
-  "join": "Join",
-  "joined": "Joined",
-  "create": "Create",
-  "close": "Close",
-  "ask": "Ask",
-  "type": "Type",
-  "activate": "Activate",
-  "requests": "Requests",
-  "mic_off": "Mic Off",
-  "disable_mic": "Disable Mic",
-  "mic_on": "Mic On",
-  "enable_mic": "Enable Mic",
-  "audio": "Audio",
-  "test": "Test",
-  "minimize": "Hide Tile",
-  "maximize": "Show Tile",
-  "mute_all": "Mute all",
-  "mute_all.description": "Everyone else in the meeting will be muted.",
-  "mute_all.header": "Are you sure?",
-  "mute_all.allow_unmute": "Allow others to unmute",
-  "video_off": "Video Off",
-  "disable_video": "Disable Video",
-  "video_on": "Video On",
-  "enable_video": "Enable Video",
-  "video": "Video",
-  "offline": "You're offline",
-  "offline.description": "Please ensure that you are connected to the internet.",
-  "disconnected": "You haven't joined the meeting.",
-  "failed": "You've been disconnected",
-  "failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
-  "disconnected.description": "Please join the meeting in order to see and interact with other participants.",
-  "participants": "Participants",
-  "participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
-  "participants.empty_list": "It looks like nobody is here.",
-  "participants.no_pending_requests": "There are no pending requests.",
-  "participants.turn_off_video": "Turn off video",
-  "polls": "Polls",
-  "polls.by": "Poll by",
-  "polls.question": "Poll Question",
-  "polls.question.placeholder": "What is your poll for?",
-  "polls.answers": "Answers",
-  "polls.option": "Add an option.",
-  "polls.option.placeholder": "Enter an option",
-  "polls.results.anon": "Anonymous",
-  "polls.results.hide": "Hide results before voting",
-  "polls.create": "Create Poll",
-  "polls.cancel": "Cancel Poll Creation",
-  "polls.empty": "No polls available",
-  "polls.errors.question_required": "Question is required.",
-  "polls.errors.empty_option": "Empty options not allowed.",
-  "screenshare": "Screen Share",
-  "screenshare.min_preview": "Minimize Preview",
-  "screenshare.max_preview": "Expand Preview",
-  "screenshare.shared": "Your screen is being shared.",
-  "screenshare.start": "Share Screen",
-  "screenshare.stop": "Stop Sharing",
-  "screenshare.error.unknown": "An error occurred while starting screenshare.",
-  "screenshare.error.max_count": "Maximum screen share limit reached.",
-  "plugins": "Plugins",
-  "perm_denied": "Permission denied by browser.",
-  "perm_denied.audio": "Mic Permission denied by browser",
-  "perm_denied.video": "Camera Permission denied by browser",
-  "perm_denied.screenshare": "Screenshare Permission denied by browser",
-  "perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
-  "perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
-  "perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
-  "perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
-  "perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
-  "perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
-  "perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
-  "perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
-  "perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
-  "perm_sys_denied": "Permission denied by system",
-  "perm_sys_denied.audio": "Mic permission denied by system",
-  "perm_sys_denied.video": "Camera permission denied by system",
-  "perm_sys_denied.screenshare": "Screenshare permission denied by system",
-  "perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
-  "perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
-  "perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
-  "perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
-  "perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
-  "perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
-  "perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
-  "perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
-  "perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
-  "perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
-  "perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
-  "perm_could_not_start": "Could not capture device.",
-  "perm_could_not_start.audio": "Unable to start your Microphone",
-  "perm_could_not_start.video": "Unable to start your Camera",
-  "perm_could_not_start.screenshare": "Unable to start your Screenshare",
-  "perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
-  "perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
-  "perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
-  "full_screen": "Full Screen",
-  "full_screen.exit": "Exit Full Screen",
-  "waitlist.header_title": "Waiting",
-  "waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
-  "waitlist.deny_request": "Deny request",
-  "waitlist.accept_request": "Accept request",
-  "waitlist.accept_all": "Accept all",
-  "stage_request.header_title": "Join Stage Requests",
-  "stage_request.deny_request": "Deny request",
-  "stage_request.accept_request": "Accept request",
-  "stage_request.accept_all": "Accept all",
-  "stage_request.deny_all": "Deny all",
-  "stage_request.approval_pending": "Pending",
-  "stage_request.denied": "Denied",
-  "stage_request.request": "Join stage",
-  "stage_request.requested": "Requested",
-  "stage_request.cancel_request": "Cancel request",
-  "stage_request.leave_stage": "Leave stage",
-  "stage_request.request_tip": "Request to join the discussion",
-  "stage_request.leave_tip": "Leave the stage",
-  "stage_request.pending_tip": "Request pending",
-  "stage_request.denied_tip": "Rejected request",
-  "stage.empty_host": "The stage is empty",
-  "stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
-  "stage.empty_viewer": "There is no one on stage",
-  "stage.remove_from_stage": "Remove from stage",
-  "stage.invited_notification": "has been invited to join stage.",
-  "stage.add_to_stage": "Invite to stage",
-  "stage.join_title": "Join Stage",
-  "stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
-  "stage.join_cancel": "Cancel",
-  "stage.join_confirm": "Join",
-  "setup_screen.join_in_as": "Joining as",
-  "setup_screen.your_name": "Your name",
-  "stage.reconnecting": "Reconnecting...",
-  "recording.label": "REC",
-  "recording.indicator": "This meeting is being recorded.",
-  "recording.started": "This meeting is being recorded.",
-  "recording.stopped": "Recording for this meeting has been stopped.",
-  "recording.paused": "Recording for this meeting has been paused.",
-  "recording.error.start": "Error while starting recording.",
-  "recording.error.stop": "Error while stopping recording",
-  "recording.error.resume": "Error while resuming recording",
-  "recording.start": "Start Recording",
-  "recording.stop": "Stop Recording",
-  "recording.resume": "Resume Recording",
-  "recording.starting": "Starting",
-  "recording.stopping": "Stopping",
-  "recording.loading": "Loading",
-  "recording.idle": "Record",
-  "audio_playback": "Play Audio",
-  "audio_playback.title": "Allow Audio Playback",
-  "audio_playback.description": "In order to play audio properly on your device, click the button below.",
-  "breakout_rooms": "Breakout Rooms",
-  "breakout_rooms.room_config_header": "Create Breakout",
-  "breakout_rooms.join_breakout_header": "Join Breakout",
-  "breakout_rooms.empty": "Nobody here yet.",
-  "breakout_rooms.delete": "Delete Room",
-  "breakout_rooms.switch": "Switch",
-  "breakout_rooms.main_room": "Main Room",
-  "breakout_rooms.shuffle_participants": "Shuffle Participants",
-  "breakout_rooms.deselect": "Deselect",
-  "breakout_rooms.selected": "selected",
-  "breakout_rooms.num_of_rooms": "No. of Rooms",
-  "breakout_rooms.approx": "Approx.",
-  "breakout_rooms.participants_per_room": "participants/room",
-  "breakout_rooms.division_text": "when equally divided.",
-  "breakout_rooms.start_breakout": "Start Breakout",
-  "breakout_rooms.close_breakout": "Close Breakout",
-  "breakout_rooms.update_breakout": "Update Breakout",
-  "breakout_rooms.discard_changes": "Discard Changes",
-  "breakout_rooms.room": "Room",
-  "breakout_rooms.rooms": "Rooms",
-  "breakout_rooms.room_name": "Room Name",
-  "breakout_rooms.edit_room_name": "Edit Room Name",
-  "breakout_rooms.save_room_name": "Save Room Name",
-  "breakout_rooms.add_room": "Add",
-  "breakout_rooms.add_room_brief": "Add Room",
-  "breakout_rooms.select_all": "Select all",
-  "breakout_rooms.unassign_all": "Unassign all",
-  "breakout_rooms.assign": "Assign",
-  "breakout_rooms.assign_participants": "Assign Participants",
-  "breakout_rooms.none_assigned": "No participants assigned yet",
-  "breakout_rooms.drag_drop_participants": "Drag and drop participants",
-  "breakout_rooms.click_drop_participants": "Click here to assign",
-  "breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
-  "breakout_rooms.status.select_room": "Select a room to assign",
-  "breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
-  "breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
-  "breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
-  "breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
-  "breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
-  "breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
-  "breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
-  "breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
-  "breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
-  "breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
-  "breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
-  "breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
-  "breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
-  "breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
-  "breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
-  "breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
-  "breakout_rooms.all_assigned": "All participants have been assigned",
-  "breakout_rooms.empty_main_room": "No more participants in the main room.",
-  "breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
-  "breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
-  "ai": "AI",
-  "ai.meeting_ai": "MeetingAI",
-  "ai.home": "Home",
-  "ai.transcriptions": "Transcriptions",
-  "ai.personal": "Personal",
-  "ai.caption_view": "Caption View",
-  "ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
-  "ai.chat.summarise": "Hey AI, summarise this call",
-  "ai.chat.agenda": "Hey AI, what is today's agenda?",
-  "search": "Search",
-  "search.could_not_find": "Couldn't find a participant with the specified name or ID.",
-  "search.empty": "It looks like nobody is here.",
-  "end": "End Meeting",
-  "end.all": "End meeting for all",
-  "ended": "The meeting ended.",
-  "ended.rejected": "Your request to join the meeting was denied.",
-  "ended.left": "You left the meeting.",
-  "ended.kicked": "You were removed from the meeting.",
-  "ended.disconnected": "The call ended because the connection was lost.",
-  "ended.network": "Please check your internet connection and try again.",
-  "ended.unauthorized": "You are not authorized to join this meeting.",
-  "network": "Network",
-  "network.reconnecting": "Connection lost. Trying to reconnect.",
-  "network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
-  "network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
-  "network.leaving": "Automatically leaving the meeting in 10 seconds.",
-  "network.restored": "Connection restored",
-  "network.delay": "Taking too long to reconnect.",
-  "network.lost": "Connection lost",
-  "network.lost_extended": "Connection lost. Please check your network connection.",
-  "livestream": "Livestream",
-  "livestream.indicator": "This meeting is being livestreamed.",
-  "livestream.skip": "Skip to Live",
-  "livestream.idle": "Waiting to go live.",
-  "livestream.starting": "Livestream is starting...",
-  "livestream.stopping": "Livestream is stopping...",
-  "livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
-  "livestream.error.not_supported": "Player not supported.",
-  "livestream.error.not_found": "Playback URL not found.",
-  "livestream.error.unknown": "An unknown error occurred.",
-  "livestream.error.sync": "Could not sync livestream please try again later.",
-  "livestream.error.start": "Error while starting livestream.",
-  "livestream.error.stop": "Error while stopping livestream.",
-  "livestream.go_live": "Go Live",
-  "livestream.end_live": "End Live",
-  "livestream.error": "Error",
-  "cta.help": "Need help on how to do this?",
-  "cta.continue": "Ignore",
-  "cta.reload": "Reload",
-  "cta.confirmation": "Are you sure?",
-  "cta.system_settings": "Open Settings",
-  "remote_access.empty": "There are no remote requests, yet.",
-  "remote_access.requests": "The following people have requested remote control to your screen share.",
-  "remote_access.allow": "Please select whom you want to give access to.",
-  "remote_access.grant": "Grant access",
-  "remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
-  "chat": "Chat",
-  "chat.new": "New",
-  "chat.max_limit_warning": "Max Character Limit",
-  "chat.rate_limit_error": "Please wait before you can send another message",
-  "chat.new_channel": "Create new channel",
-  "chat.channel_name": "Enter channel name",
-  "chat.member_name": "Enter member name",
-  "chat.add_members": "Add members",
-  "chat.delete_msg": "Delete",
-  "chat.edit_msg": "Edit",
-  "chat.send_msg": "Send message",
-  "chat.send_attachment": "Drop files/images to send",
-  "chat.send_img": "Send an image",
-  "chat.send_file": "Send a file",
-  "chat.send_emoji": "Send an emoji",
-  "chat.update_msg": "Update message",
-  "chat.channel_members": "Channel Members",
-  "chat.img.loading": "Loading image",
-  "chat.error.img_not_found": "Image not found",
-  "chat.error.empty_results": "Couldn't find a member with the specified name.",
-  "chat.img.shared_by": "Shared by",
-  "chat.reply": "Reply",
-  "chat.message_placeholder": "Message..",
-  "chat.click_to_send": "Click to send as message",
-  "chat.search_msgs": "Search messages",
-  "chat.search_conversations": "Search conversations",
-  "chat.start_conversation": "Start a conversation..",
-  "chat.empty_search": "No messages found",
-  "chat.empty_channel": "Send a message to get started",
-  "chat.cancel_upload": "Cancel upload",
-  "chat.view_chats": "View chats",
-  "chat.everyone": "everyone",
-  "chat.pinned_msgs": "Pinned messages",
-  "chat.toggle_pinned_msgs": "Toggle pinned messages",
-  "date.today": "Today",
-  "date.yesterday": "Yesterday",
-  "date.sunday": "Sunday",
-  "date.monday": "Monday",
-  "date.tuesday": "Tuesday",
-  "date.wednesday": "Wednesday",
-  "date.thursday": "Thursday",
-  "date.friday": "Friday",
-  "date.saturday": "Saturday",
-  "list.empty": "No items found",
-  "grid.listening": "Listening",
-  "transcript.off": "Turn off Transcripts",
-  "transcript.on": "Turn on Transcripts",
-  "settings.notification_sound": "Notification sound",
-  "settings.microphone_input": "Microphone",
-  "settings.speaker_output": "Speaker",
-  "settings.mirror_video": "Mirror my Video",
-  "settings.camera_off": "Camera is off",
-  "dialog.close": "Close dialog",
-  "notifications.joined": "just joined",
-  "notifications.left": "left",
-  "notifications.requesting_to_join_meeting": "is requesting to join the meeting",
-  "notifications.requested_to_join_stage": "has requested to join stage",
-  "notifications.joined_stage": "has joined stage",
-  "notifications.request_to_join_accepted": "Request to join accepted",
-  "notifications.request_to_join_rejected": "Request to join rejected",
-  "notifications.accept": "Accept",
-  "notifications.new_poll_created_by": "New poll created by",
-  "notifications.connected_to": "Connected to",
-  "notifications.plugin_switched_to": "Plugin switched to",
-  "notifications.remote_control_requested": "has requested for remote control",
-  "notifications.remote_control_request_sent": "Sent remote control request to",
-  "notifications.remote_control_request_accepted": "has granted remote control",
-  "notifications.remote_control_granted": "Granted remote control to",
-  "notifications.remote_control_terminated": "Existing remote control has been terminated",
-  "debugger.troubleshooting.label": "Troubleshooting",
-  "debugger.quality.good": "Good",
-  "debugger.quality.average": "Average",
-  "debugger.quality.poor": "Poor",
-  "debugger.stats.bitrate.label": "Bitrate",
-  "debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
-  "debugger.stats.packet_loss.label": "Packet Loss",
-  "debugger.stats.packet_loss.description": "Amount of data lost during transfer",
-  "debugger.stats.jitter.label": "Jitter",
-  "debugger.stats.jitter.description": "Variance or fluctuation in latency",
-  "debugger.stats.cpu_limitations.label": "CPU Limitations",
-  "debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
-  "debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
-  "debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
-  "debugger.audio.label": "Audio",
-  "debugger.audio.troubleshooting.label": "Audio Troubleshooting",
-  "debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.audio.messages.enable_media": "Please enable mic to see the report.",
-  "debugger.audio.sections.network_media": "Network & Media",
-  "debugger.video.label": "Video",
-  "debugger.video.troubleshooting.label": "Video Troubleshooting",
-  "debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.video.messages.enable_media": "Please enable camera to see the report.",
-  "debugger.video.sections.network_media": "Network & Media",
-  "debugger.screenshare.label": "Screenshare",
-  "debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
-  "debugger.screenshare.sections.network_media": "Network & Media",
-  "debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
-  "debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
-  "debugger.system.label": "System",
-  "debugger.system.troubleshooting.label": "System Troubleshooting",
-  "debugger.system.sections.battery": "Battery",
-  "debugger.system.battery.level.label": "Battery Level",
-  "debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
-  "debugger.system.battery.charging.label": "Battery Charging Status",
-  "debugger.system.battery.charging.description": "A device running on power performs optimally.",
-  "debugger.system.battery.charging.is_charging": "Charging",
-  "debugger.system.battery.charging.is_not_charging": "Not charging"
+	"about_call": "About Call",
+	"screen": "Screen",
+	"camera": "Camera",
+	"leave": "Leave",
+	"dismiss": "Dismiss",
+	"logo": "Logo",
+	"page": "Page",
+	"more": "More",
+	"page.prev": "Previous Page",
+	"page.next": "Next Page",
+	"layout": "Layout",
+	"layout.auto": "Auto Layout",
+	"settings": "Settings",
+	"file": "File",
+	"image": "Image",
+	"connection": "Connection",
+	"leave_confirmation": "Are you sure you want to leave the call?",
+	"cancel": "Cancel",
+	"yes": "Yes",
+	"(you)": "(you)",
+	"you": "You",
+	"everyone": "Everyone",
+	"to": "To",
+	"mute": "Mute",
+	"kick": "Kick",
+	"pin": "Pin",
+	"pinned": "Pinned",
+	"accept": "Accept",
+	"unpin": "Unpin",
+	"pip_on": "Show PiP",
+	"pip_off": "Hide PiP",
+	"viewers": "Viewers",
+	"join": "Join",
+	"joined": "Joined",
+	"create": "Create",
+	"close": "Close",
+	"ask": "Ask",
+	"type": "Type",
+	"activate": "Activate",
+	"requests": "Requests",
+	"mic_off": "Mic Off",
+	"disable_mic": "Disable Mic",
+	"mic_on": "Mic On",
+	"enable_mic": "Enable Mic",
+	"audio": "Audio",
+	"test": "Test",
+	"minimize": "Hide Tile",
+	"maximize": "Show Tile",
+	"mute_all": "Mute all",
+	"mute_all.description": "Everyone else in the meeting will be muted.",
+	"mute_all.header": "Are you sure?",
+	"mute_all.allow_unmute": "Allow others to unmute",
+	"video_off": "Video Off",
+	"disable_video": "Disable Video",
+	"video_on": "Video On",
+	"enable_video": "Enable Video",
+	"video": "Video",
+	"offline": "You're offline",
+	"offline.description": "Please ensure that you are connected to the internet.",
+	"disconnected": "You haven't joined the meeting.",
+	"failed": "You've been disconnected",
+	"failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
+	"disconnected.description": "Please join the meeting in order to see and interact with other participants.",
+	"participants": "Participants",
+	"participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
+	"participants.empty_list": "It looks like nobody is here.",
+	"participants.no_pending_requests": "There are no pending requests.",
+	"participants.turn_off_video": "Turn off video",
+	"polls": "Polls",
+	"polls.by": "Poll by",
+	"polls.question": "Poll Question",
+	"polls.question.placeholder": "What is your poll for?",
+	"polls.answers": "Answers",
+	"polls.option": "Add an option.",
+	"polls.option.placeholder": "Enter an option",
+	"polls.results.anon": "Anonymous",
+	"polls.results.hide": "Hide results before voting",
+	"polls.create": "Create Poll",
+	"polls.cancel": "Cancel Poll Creation",
+	"polls.empty": "No polls available",
+	"polls.errors.question_required": "Question is required.",
+	"polls.errors.empty_option": "Empty options not allowed.",
+	"screenshare": "Screen Share",
+	"screenshare.min_preview": "Minimize Preview",
+	"screenshare.max_preview": "Expand Preview",
+	"screenshare.shared": "Your screen is being shared.",
+	"screenshare.start": "Share Screen",
+	"screenshare.stop": "Stop Sharing",
+	"screenshare.error.unknown": "An error occurred while starting screenshare.",
+	"screenshare.error.max_count": "Maximum screen share limit reached.",
+	"plugins": "Plugins",
+	"perm_denied": "Permission denied by browser.",
+	"perm_denied.audio": "Mic Permission denied by browser",
+	"perm_denied.video": "Camera Permission denied by browser",
+	"perm_denied.screenshare": "Screenshare Permission denied by browser",
+	"perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
+	"perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
+	"perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
+	"perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
+	"perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
+	"perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
+	"perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
+	"perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
+	"perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
+	"perm_sys_denied": "Permission denied by system",
+	"perm_sys_denied.audio": "Mic permission denied by system",
+	"perm_sys_denied.video": "Camera permission denied by system",
+	"perm_sys_denied.screenshare": "Screenshare permission denied by system",
+	"perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
+	"perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
+	"perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
+	"perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
+	"perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
+	"perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
+	"perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
+	"perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
+	"perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
+	"perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
+	"perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
+	"perm_could_not_start": "Could not capture device.",
+	"perm_could_not_start.audio": "Unable to start your Microphone",
+	"perm_could_not_start.video": "Unable to start your Camera",
+	"perm_could_not_start.screenshare": "Unable to start your Screenshare",
+	"perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
+	"perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
+	"perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
+	"full_screen": "Full Screen",
+	"full_screen.exit": "Exit Full Screen",
+	"waitlist.header_title": "Waiting",
+	"waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
+	"waitlist.deny_request": "Deny request",
+	"waitlist.accept_request": "Accept request",
+	"waitlist.accept_all": "Accept all",
+	"stage_request.header_title": "Join Stage Requests",
+	"stage_request.deny_request": "Deny request",
+	"stage_request.accept_request": "Accept request",
+	"stage_request.accept_all": "Accept all",
+	"stage_request.deny_all": "Deny all",
+	"stage_request.approval_pending": "Pending",
+	"stage_request.denied": "Denied",
+	"stage_request.request": "Join stage",
+	"stage_request.requested": "Requested",
+	"stage_request.cancel_request": "Cancel request",
+	"stage_request.leave_stage": "Leave stage",
+	"stage_request.request_tip": "Request to join the discussion",
+	"stage_request.leave_tip": "Leave the stage",
+	"stage_request.pending_tip": "Request pending",
+	"stage_request.denied_tip": "Rejected request",
+	"stage.empty_host": "The stage is empty",
+	"stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
+	"stage.empty_viewer": "There is no one on stage",
+	"stage.remove_from_stage": "Remove from stage",
+	"stage.invited_notification": "has been invited to join stage.",
+	"stage.add_to_stage": "Invite to stage",
+	"stage.join_title": "Join Stage",
+	"stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
+	"stage.join_cancel": "Cancel",
+	"stage.join_confirm": "Join",
+	"setup_screen.join_in_as": "Joining as",
+	"setup_screen.your_name": "Your name",
+	"stage.reconnecting": "Reconnecting...",
+	"recording.label": "REC",
+	"recording.indicator": "This meeting is being recorded.",
+	"recording.started": "This meeting is being recorded.",
+	"recording.stopped": "Recording for this meeting has been stopped.",
+	"recording.paused": "Recording for this meeting has been paused.",
+	"recording.error.start": "Error while starting recording.",
+	"recording.error.stop": "Error while stopping recording",
+	"recording.error.resume": "Error while resuming recording",
+	"recording.start": "Start Recording",
+	"recording.stop": "Stop Recording",
+	"recording.resume": "Resume Recording",
+	"recording.starting": "Starting",
+	"recording.stopping": "Stopping",
+	"recording.loading": "Loading",
+	"recording.idle": "Record",
+	"audio_playback": "Play Audio",
+	"audio_playback.title": "Allow Audio Playback",
+	"audio_playback.description": "In order to play audio properly on your device, click the button below.",
+	"breakout_rooms": "Breakout Rooms",
+	"breakout_rooms.room_config_header": "Create Breakout",
+	"breakout_rooms.join_breakout_header": "Join Breakout",
+	"breakout_rooms.empty": "Nobody here yet.",
+	"breakout_rooms.delete": "Delete Room",
+	"breakout_rooms.switch": "Switch",
+	"breakout_rooms.main_room": "Main Room",
+	"breakout_rooms.shuffle_participants": "Shuffle Participants",
+	"breakout_rooms.deselect": "Deselect",
+	"breakout_rooms.selected": "selected",
+	"breakout_rooms.num_of_rooms": "No. of Rooms",
+	"breakout_rooms.approx": "Approx.",
+	"breakout_rooms.participants_per_room": "participants/room",
+	"breakout_rooms.division_text": "when equally divided.",
+	"breakout_rooms.start_breakout": "Start Breakout",
+	"breakout_rooms.close_breakout": "Close Breakout",
+	"breakout_rooms.update_breakout": "Update Breakout",
+	"breakout_rooms.discard_changes": "Discard Changes",
+	"breakout_rooms.room": "Room",
+	"breakout_rooms.rooms": "Rooms",
+	"breakout_rooms.room_name": "Room Name",
+	"breakout_rooms.edit_room_name": "Edit Room Name",
+	"breakout_rooms.save_room_name": "Save Room Name",
+	"breakout_rooms.add_room": "Add",
+	"breakout_rooms.add_room_brief": "Add Room",
+	"breakout_rooms.select_all": "Select all",
+	"breakout_rooms.unassign_all": "Unassign all",
+	"breakout_rooms.assign": "Assign",
+	"breakout_rooms.assign_participants": "Assign Participants",
+	"breakout_rooms.none_assigned": "No participants assigned yet",
+	"breakout_rooms.drag_drop_participants": "Drag and drop participants",
+	"breakout_rooms.click_drop_participants": "Click here to assign",
+	"breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
+	"breakout_rooms.status.select_room": "Select a room to assign",
+	"breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
+	"breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
+	"breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
+	"breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
+	"breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
+	"breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
+	"breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
+	"breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
+	"breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
+	"breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
+	"breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
+	"breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
+	"breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
+	"breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
+	"breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
+	"breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
+	"breakout_rooms.all_assigned": "All participants have been assigned",
+	"breakout_rooms.empty_main_room": "No more participants in the main room.",
+	"breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
+	"breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
+	"ai": "AI",
+	"ai.meeting_ai": "MeetingAI",
+	"ai.home": "Home",
+	"ai.transcriptions": "Transcriptions",
+	"ai.personal": "Personal",
+	"ai.caption_view": "Caption View",
+	"ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
+	"ai.chat.summarise": "Hey AI, summarise this call",
+	"ai.chat.agenda": "Hey AI, what is today's agenda?",
+	"search": "Search",
+	"search.could_not_find": "Couldn't find a participant with the specified name or ID.",
+	"search.empty": "It looks like nobody is here.",
+	"end": "End Meeting",
+	"end.all": "End meeting for all",
+	"ended": "The meeting ended.",
+	"ended.rejected": "Your request to join the meeting was denied.",
+	"ended.left": "You left the meeting.",
+	"ended.kicked": "You were removed from the meeting.",
+	"ended.disconnected": "The call ended because the connection was lost.",
+	"ended.network": "Please check your internet connection and try again.",
+	"ended.unauthorized": "You are not authorized to join this meeting.",
+	"network": "Network",
+	"network.reconnecting": "Connection lost. Trying to reconnect.",
+	"network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
+	"network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
+	"network.leaving": "Automatically leaving the meeting in 10 seconds.",
+	"network.restored": "Connection restored",
+	"network.delay": "Taking too long to reconnect.",
+	"network.lost": "Connection lost",
+	"network.lost_extended": "Connection lost. Please check your network connection.",
+	"livestream": "Livestream",
+	"livestream.indicator": "This meeting is being livestreamed.",
+	"livestream.skip": "Skip to Live",
+	"livestream.idle": "Waiting to go live.",
+	"livestream.starting": "Livestream is starting...",
+	"livestream.stopping": "Livestream is stopping...",
+	"livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
+	"livestream.error.not_supported": "Player not supported.",
+	"livestream.error.not_found": "Playback URL not found.",
+	"livestream.error.unknown": "An unknown error occurred.",
+	"livestream.error.sync": "Could not sync livestream please try again later.",
+	"livestream.error.start": "Error while starting livestream.",
+	"livestream.error.stop": "Error while stopping livestream.",
+	"livestream.go_live": "Go Live",
+	"livestream.end_live": "End Live",
+	"livestream.error": "Error",
+	"cta.help": "Need help on how to do this?",
+	"cta.continue": "Ignore",
+	"cta.reload": "Reload",
+	"cta.confirmation": "Are you sure?",
+	"cta.system_settings": "Open Settings",
+	"remote_access.empty": "There are no remote requests, yet.",
+	"remote_access.requests": "The following people have requested remote control to your screen share.",
+	"remote_access.allow": "Please select whom you want to give access to.",
+	"remote_access.grant": "Grant access",
+	"remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
+	"chat": "Chat",
+	"chat.new": "New",
+	"chat.max_limit_warning": "Max Character Limit",
+	"chat.rate_limit_error": "Please wait before you can send another message",
+	"chat.new_channel": "Create new channel",
+	"chat.channel_name": "Enter channel name",
+	"chat.member_name": "Enter member name",
+	"chat.add_members": "Add members",
+	"chat.delete_msg": "Delete",
+	"chat.edit_msg": "Edit",
+	"chat.send_msg": "Send message",
+	"chat.send_attachment": "Drop files/images to send",
+	"chat.send_img": "Send an image",
+	"chat.send_file": "Send a file",
+	"chat.send_emoji": "Send an emoji",
+	"chat.update_msg": "Update message",
+	"chat.channel_members": "Channel Members",
+	"chat.img.loading": "Loading image",
+	"chat.error.img_not_found": "Image not found",
+	"chat.error.empty_results": "Couldn't find a member with the specified name.",
+	"chat.img.shared_by": "Shared by",
+	"chat.reply": "Reply",
+	"chat.message_placeholder": "Message..",
+	"chat.click_to_send": "Click to send as message",
+	"chat.search_msgs": "Search messages",
+	"chat.search_conversations": "Search conversations",
+	"chat.start_conversation": "Start a conversation..",
+	"chat.empty_search": "No messages found",
+	"chat.empty_channel": "Send a message to get started",
+	"chat.cancel_upload": "Cancel upload",
+	"chat.view_chats": "View chats",
+	"chat.everyone": "everyone",
+	"chat.pinned_msgs": "Pinned messages",
+	"chat.toggle_pinned_msgs": "Toggle pinned messages",
+	"date.today": "Today",
+	"date.yesterday": "Yesterday",
+	"date.sunday": "Sunday",
+	"date.monday": "Monday",
+	"date.tuesday": "Tuesday",
+	"date.wednesday": "Wednesday",
+	"date.thursday": "Thursday",
+	"date.friday": "Friday",
+	"date.saturday": "Saturday",
+	"list.empty": "No items found",
+	"grid.listening": "Listening",
+	"transcript.off": "Turn off Transcripts",
+	"transcript.on": "Turn on Transcripts",
+	"settings.notification_sound": "Notification sound",
+	"settings.microphone_input": "Microphone",
+	"settings.speaker_output": "Speaker",
+	"settings.mirror_video": "Mirror my Video",
+	"settings.camera_off": "Camera is off",
+	"dialog.close": "Close dialog",
+	"notifications.joined": "just joined",
+	"notifications.left": "left",
+	"notifications.requesting_to_join_meeting": "is requesting to join the meeting",
+	"notifications.requested_to_join_stage": "has requested to join stage",
+	"notifications.joined_stage": "has joined stage",
+	"notifications.request_to_join_accepted": "Request to join accepted",
+	"notifications.request_to_join_rejected": "Request to join rejected",
+	"notifications.accept": "Accept",
+	"notifications.new_poll_created_by": "New poll created by",
+	"notifications.connected_to": "Connected to",
+	"notifications.plugin_switched_to": "Plugin switched to",
+	"notifications.remote_control_requested": "has requested for remote control",
+	"notifications.remote_control_request_sent": "Sent remote control request to",
+	"notifications.remote_control_request_accepted": "has granted remote control",
+	"notifications.remote_control_granted": "Granted remote control to",
+	"notifications.remote_control_terminated": "Existing remote control has been terminated",
+	"debugger.troubleshooting.label": "Troubleshooting",
+	"debugger.quality.good": "Good",
+	"debugger.quality.average": "Average",
+	"debugger.quality.poor": "Poor",
+	"debugger.stats.bitrate.label": "Bitrate",
+	"debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
+	"debugger.stats.packet_loss.label": "Packet Loss",
+	"debugger.stats.packet_loss.description": "Amount of data lost during transfer",
+	"debugger.stats.jitter.label": "Jitter",
+	"debugger.stats.jitter.description": "Variance or fluctuation in latency",
+	"debugger.stats.cpu_limitations.label": "CPU Limitations",
+	"debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
+	"debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
+	"debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
+	"debugger.audio.label": "Audio",
+	"debugger.audio.troubleshooting.label": "Audio Troubleshooting",
+	"debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.audio.messages.enable_media": "Please enable mic to see the report.",
+	"debugger.audio.sections.network_media": "Network & Media",
+	"debugger.video.label": "Video",
+	"debugger.video.troubleshooting.label": "Video Troubleshooting",
+	"debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.video.messages.enable_media": "Please enable camera to see the report.",
+	"debugger.video.sections.network_media": "Network & Media",
+	"debugger.screenshare.label": "Screenshare",
+	"debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
+	"debugger.screenshare.sections.network_media": "Network & Media",
+	"debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
+	"debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
+	"debugger.system.label": "System",
+	"debugger.system.troubleshooting.label": "System Troubleshooting",
+	"debugger.system.sections.battery": "Battery",
+	"debugger.system.battery.level.label": "Battery Level",
+	"debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
+	"debugger.system.battery.charging.label": "Battery Charging Status",
+	"debugger.system.battery.charging.description": "A device running on power performs optimally.",
+	"debugger.system.battery.charging.is_charging": "Charging",
+	"debugger.system.battery.charging.is_not_charging": "Not charging"
 }
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/reference-architecture/description-of-design-guides.mdx b/src/content/partials/reference-architecture/description-of-design-guides.mdx
index ebf33568632639f..cedea82e2560037 100644
--- a/src/content/partials/reference-architecture/description-of-design-guides.mdx
+++ b/src/content/partials/reference-architecture/description-of-design-guides.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Design guides take your knowledge from a reference architecture and walk through the conceptual decisions and directions you should take to implement a specific solution. They do not replace our product documentation, but instead provide guidance on the decisions you should make given a certain solution you are trying to deploy.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
index 6a2206f3b86ff23..8756e82c2b9cbe2 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
index 6a2206f3b86ff23..8756e82c2b9cbe2 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
index a5d6d6bb9b81e53..24ca75fa6ed1a30 100644
--- a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
+++ b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-* What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
+- What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
diff --git a/src/content/partials/registrar/email-verification.mdx b/src/content/partials/registrar/email-verification.mdx
index 4dd91c56e47bc07..2b72b0b433a4f42 100644
--- a/src/content/partials/registrar/email-verification.mdx
+++ b/src/content/partials/registrar/email-verification.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 If you have an [unverified account email address](/fundamentals/user-profiles/verify-email-address/), you will not be able to transfer or register domains. Verify your account email address before proceeding.
 
-
 :::
diff --git a/src/content/partials/registrar/enable-dnssec.mdx b/src/content/partials/registrar/enable-dnssec.mdx
index 237935a506b128b..83ac4c6b7219453 100644
--- a/src/content/partials/registrar/enable-dnssec.mdx
+++ b/src/content/partials/registrar/enable-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ Cloudflare Registrar offers one-click DNSSEC activation for free to all customer
 
 1. In Cloudflare dashboard, go to the **Manage Domains** page.
 
-    <DashButton url="/?to=/:account/registrar/domains" />
+   <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain that you want to activate DNSSEC and select **Manage**.
 3. Select **Configuration** > **Enable DNSSEC**. If DNSSEC was previously activated, select **Disable DNSSEC** to disable it.
diff --git a/src/content/partials/registrar/icann-unverified-email.mdx b/src/content/partials/registrar/icann-unverified-email.mdx
index 665b423fb7c437c..296e965a96cf9c5 100644
--- a/src/content/partials/registrar/icann-unverified-email.mdx
+++ b/src/content/partials/registrar/icann-unverified-email.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 If you purchased your domain through Cloudflare Registrar, [ICANN](https://www.icann.org/) requires you to verify your registrant email address. If your email is unverified or if the verification has expired, ICANN places a hold on the domain and replaces your nameservers with parking server nameservers (NS). Once you complete verification, your nameservers are automatically restored.
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/registrar/requirements.mdx b/src/content/partials/registrar/requirements.mdx
index 23d333ecb86aba7..1178776bde7f938 100644
--- a/src/content/partials/registrar/requirements.mdx
+++ b/src/content/partials/registrar/requirements.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Requirements
diff --git a/src/content/partials/registrar/restrictions.mdx b/src/content/partials/registrar/restrictions.mdx
index 57a9452a3ab5a69..b34956aeb7039bd 100644
--- a/src/content/partials/registrar/restrictions.mdx
+++ b/src/content/partials/registrar/restrictions.mdx
@@ -1,20 +1,20 @@
 ---
 {}
-
 ---
 
 ## Restrictions
 
 To transfer your domain, it must meet the following requirements:
 
-* ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
-* Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
+- ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
+- Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
   :::caution
 
   The transfer of an expired domain may result in an additional year NOT being added during the transfer.
   :::
-* Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
-* Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
-* Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
+
+- Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
+- Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
+- Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
 
 If your domain is listed as available for transfer in the Cloudflare dashboard, these restrictions have already been checked.
diff --git a/src/content/partials/registrar/verify-dnssec.mdx b/src/content/partials/registrar/verify-dnssec.mdx
index cc9f05e4a7120d0..f5182b94b5a1559 100644
--- a/src/content/partials/registrar/verify-dnssec.mdx
+++ b/src/content/partials/registrar/verify-dnssec.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When DNSSEC has been successfully applied to your domain, Cloudflare shows you a confirmed status. Go to [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) in the Cloudflare dashboard, and scroll down to **DNSSEC**.
diff --git a/src/content/partials/rules/configuration-rule-link-to-examples.mdx b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
index 1ff0517f5389e04..037eaeef781404b 100644
--- a/src/content/partials/rules/configuration-rule-link-to-examples.mdx
+++ b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Refer to [Create a configuration rule via API](/rules/configuration-rules/create-api/#example-requests) for complete API examples.
diff --git a/src/content/partials/rules/configuration-rule-promotion.mdx b/src/content/partials/rules/configuration-rule-promotion.mdx
index 3ae68e3cf154e68..6519187465e5160 100644
--- a/src/content/partials/rules/configuration-rule-promotion.mdx
+++ b/src/content/partials/rules/configuration-rule-promotion.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 To use this feature on specific hostnames - instead of across your entire zone - use a [configuration rule](/rules/configuration-rules/).
 
-
 :::
diff --git a/src/content/partials/rules/error-pages-list.mdx b/src/content/partials/rules/error-pages-list.mdx
index e3245503608f21c..7ab22e20464a19f 100644
--- a/src/content/partials/rules/error-pages-list.mdx
+++ b/src/content/partials/rules/error-pages-list.mdx
@@ -11,4 +11,3 @@ import { Details } from "~/components";
 - 1000 class errors
 - Managed challenge / I'm Under Attack Mode
 - Rate limiting block
-
diff --git a/src/content/partials/rules/page-rules-migration.mdx b/src/content/partials/rules/page-rules-migration.mdx
index 49184a9b7fddd3a..88530db810e2ac1 100644
--- a/src/content/partials/rules/page-rules-migration.mdx
+++ b/src/content/partials/rules/page-rules-migration.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/rules/rules-creation-workflow.mdx b/src/content/partials/rules/rules-creation-workflow.mdx
index c5c10393f7fe7b5..457e137376878ed 100644
--- a/src/content/partials/rules/rules-creation-workflow.mdx
+++ b/src/content/partials/rules/rules-creation-workflow.mdx
@@ -11,7 +11,6 @@ Follow this workflow to create {props.ruleName} for a given zone via API:
 1. Use the [List zone rulesets](/api/resources/rulesets/methods/list/) operation to check if there is already a ruleset for the <code>{props.phaseName}</code> phase at the zone level.
 
 2. If the phase ruleset does not exist, create it using the [Create a zone ruleset](/api/resources/rulesets/methods/create/) operation. In the new ruleset properties, set the following values:
-
    - **kind**: `zone`
    - **phase**: <code>{props.phaseName}</code>
 
diff --git a/src/content/partials/rules/rules-templates.mdx b/src/content/partials/rules/rules-templates.mdx
index 15707947ed21c52..327ddbb7e03e964 100644
--- a/src/content/partials/rules/rules-templates.mdx
+++ b/src/content/partials/rules/rules-templates.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
-Cloudflare provides you with rules templates for common use cases. 
+Cloudflare provides you with rules templates for common use cases.
 
 1. In the Cloudflare dashboard, go to the Rules **Overview** page.
 
    <DashButton url="/?to=/:account/:zone/rules/overview" />
 
-2. Select **Templates**, and then select one of the available templates. 
+2. Select **Templates**, and then select one of the available templates.
 
 You can also refer to the [Examples gallery](/rules/examples/) in the developer docs.
diff --git a/src/content/partials/rules/terraform-additional-resources.mdx b/src/content/partials/rules/terraform-additional-resources.mdx
index d12cb288e5d11d2..38d3d167a3b1839 100644
--- a/src/content/partials/rules/terraform-additional-resources.mdx
+++ b/src/content/partials/rules/terraform-additional-resources.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 ## Additional resources
 
 For additional guidance on using Terraform with Cloudflare, refer to the following resources:
 
-* [Terraform documentation](/terraform/)
-* [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
+- [Terraform documentation](/terraform/)
+- [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
diff --git a/src/content/partials/rules/transform/header-valid-names.mdx b/src/content/partials/rules/transform/header-valid-names.mdx
index f286e2ab339e6cc..0e72fbaa66dee00 100644
--- a/src/content/partials/rules/transform/header-valid-names.mdx
+++ b/src/content/partials/rules/transform/header-valid-names.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
-* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-* The following special characters: `-` and `_`
+- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+- The following special characters: `-` and `_`
diff --git a/src/content/partials/rules/transform/header-valid-values.mdx b/src/content/partials/rules/transform/header-valid-values.mdx
index 540ff31d7a51c22..9daf4a9a76a4e18 100644
--- a/src/content/partials/rules/transform/header-valid-values.mdx
+++ b/src/content/partials/rules/transform/header-valid-values.mdx
@@ -1,7 +1,6 @@
 ---
 {}
-
 ---
 
-* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-* The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
+- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+- The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
diff --git a/src/content/partials/ruleset-engine/max-expression-length.mdx b/src/content/partials/ruleset-engine/max-expression-length.mdx
index e8881c097a0cb0c..59d99f613473f9c 100644
--- a/src/content/partials/ruleset-engine/max-expression-length.mdx
+++ b/src/content/partials/ruleset-engine/max-expression-length.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The maximum length of a rule expression is 4,096 characters.
diff --git a/src/content/partials/ruleset-engine/rule-position-values.mdx b/src/content/partials/ruleset-engine/rule-position-values.mdx
index aed905dee8894cd..c83ff42bfcf11a3 100644
--- a/src/content/partials/ruleset-engine/rule-position-values.mdx
+++ b/src/content/partials/ruleset-engine/rule-position-values.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
-* `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
+- `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
 
-* `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
+- `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
 
-* `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
+- `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
 
 :::caution[Important]
 
diff --git a/src/content/partials/security-center/brand-protection-alerts.mdx b/src/content/partials/security-center/brand-protection-alerts.mdx
index 71e7f9d688bd180..30a6ad5713d7bad 100644
--- a/src/content/partials/security-center/brand-protection-alerts.mdx
+++ b/src/content/partials/security-center/brand-protection-alerts.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Brand Protection integrates with Cloudflare's ANS (Alerts Notification Service) to provide configurable alerts when new domains are detected.
diff --git a/src/content/partials/security-center/brand-protection-definition.mdx b/src/content/partials/security-center/brand-protection-definition.mdx
index be50db0bf8b3b06..6707a12034c0016 100644
--- a/src/content/partials/security-center/brand-protection-definition.mdx
+++ b/src/content/partials/security-center/brand-protection-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Brand Protection allows you to proactively identify and mitigate domain impersonation and phishing attacks. By monitoring newly registered domains and visual assets across the Internet, Cloudflare helps protect your brand's reputation and prevents your customers or employees from submitting sensitive information to fraudulent sites.
@@ -9,4 +8,4 @@ Common threats include:
 
 - [Typosquatting](https://en.wikipedia.org/wiki/Typosquatting): For example, typing `cloudfalre.com` instead of `cloudflare.com`.
 - Concatenation of services (`cloudflare-service.com`) often registered by attackers to trick unsuspecting victims into submitting private information such as passwords.
-- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
\ No newline at end of file
+- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
diff --git a/src/content/partials/security-center/scan-frequency.mdx b/src/content/partials/security-center/scan-frequency.mdx
index 78e170a9f3c6a81..d5d4a4b4bfe5c98 100644
--- a/src/content/partials/security-center/scan-frequency.mdx
+++ b/src/content/partials/security-center/scan-frequency.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you enable Security Insights, Cloudflare performs scans automatically. Paying customers (as defined in the table below) are re-scanned daily and can trigger a scan manually:
@@ -8,4 +7,4 @@ Once you enable Security Insights, Cloudflare performs scans automatically. Payi
 | Plan                                      | Scan Frequency | On-Demand |
 | ----------------------------------------- | -------------- | --------- |
 | Accounts on a Free, Pro, or Business plan | Every 7 days   | Yes       |
-| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
\ No newline at end of file
+| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
diff --git a/src/content/partials/security-center/scan-properties.mdx b/src/content/partials/security-center/scan-properties.mdx
index aa07143a1e7c4f7..cb96cf4aa2a437c 100644
--- a/src/content/partials/security-center/scan-properties.mdx
+++ b/src/content/partials/security-center/scan-properties.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment.
-* **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
-* **Risk**: A description of the risk associated with not addressing the issue.
-* **Type**: The insight category.
+- **Severity**: The security risk of the insight. The severity values are: _Moderate_, _High_, and _Critical_. The higher the severity level, the higher the risk of threat to your environment.
+- **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
+- **Risk**: A description of the risk associated with not addressing the issue.
+- **Type**: The insight category.
diff --git a/src/content/partials/security-center/security-insights-definition.mdx b/src/content/partials/security-center/security-insights-definition.mdx
index caeb5d26174c035..b41a47d43774aa0 100644
--- a/src/content/partials/security-center/security-insights-definition.mdx
+++ b/src/content/partials/security-center/security-insights-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Security Insights provides you with a list of insights, covering different areas of your Cloudflare environment, such as: Cloudflare account settings, DNS record configurations, SSL/TLS certificates configurations, Cloudflare Access configurations and Cloudflare WAF configurations.
diff --git a/src/content/partials/smart-shield/argo-analytics.mdx b/src/content/partials/smart-shield/argo-analytics.mdx
index 32f48959a9305a7..de75df8e6e26cee 100644
--- a/src/content/partials/smart-shield/argo-analytics.mdx
+++ b/src/content/partials/smart-shield/argo-analytics.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
\ No newline at end of file
+Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
diff --git a/src/content/partials/smart-shield/argo-intro.mdx b/src/content/partials/smart-shield/argo-intro.mdx
index 268b8495d8fe135..32ea358182d40ac 100644
--- a/src/content/partials/smart-shield/argo-intro.mdx
+++ b/src/content/partials/smart-shield/argo-intro.mdx
@@ -6,5 +6,5 @@ params:
 Argo Smart Routing detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
 
 { props.conditional === "dedicated-argo-tile" && (
-	<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
+<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
 )}
diff --git a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
index 9fa952b07643f85..3d8aa0a11fe62e8 100644
--- a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
+++ b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
\ No newline at end of file
+Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
diff --git a/src/content/partials/smart-shield/dcei-pool-requirements.mdx b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
index 7cafa55a6d95d3e..ac278f7e6a42db8 100644
--- a/src/content/partials/smart-shield/dcei-pool-requirements.mdx
+++ b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
\ No newline at end of file
+Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
diff --git a/src/content/partials/smart-shield/health-checks-analytics.mdx b/src/content/partials/smart-shield/health-checks-analytics.mdx
index 2983c5deb95bc9f..6a9a9c84165553c 100644
--- a/src/content/partials/smart-shield/health-checks-analytics.mdx
+++ b/src/content/partials/smart-shield/health-checks-analytics.mdx
@@ -194,4 +194,4 @@ If the failure cannot be classified as any other type of failure mentioned above
 
 #### Solution
 
-Contact [Cloudflare support](/support/contacting-cloudflare-support/).
\ No newline at end of file
+Contact [Cloudflare support](/support/contacting-cloudflare-support/).
diff --git a/src/content/partials/smart-shield/health-checks-intro.mdx b/src/content/partials/smart-shield/health-checks-intro.mdx
index ed843ebdf208147..5d9ab876a0af7ce 100644
--- a/src/content/partials/smart-shield/health-checks-intro.mdx
+++ b/src/content/partials/smart-shield/health-checks-intro.mdx
@@ -4,4 +4,4 @@
 
 A health check is a service that runs on Cloudflare's edge network to monitor whether an origin server is online. This allows you to view the health of your origin servers even if there is only one origin or you do not yet need to balance traffic across your infrastructure.
 
-Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
\ No newline at end of file
+Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
diff --git a/src/content/partials/smart-shield/health-checks-regions.mdx b/src/content/partials/smart-shield/health-checks-regions.mdx
index bbbbdb12d2c0ec9..4c0e494eaeec2e9 100644
--- a/src/content/partials/smart-shield/health-checks-regions.mdx
+++ b/src/content/partials/smart-shield/health-checks-regions.mdx
@@ -12,8 +12,8 @@ The Internet is not the same everywhere around the world and your users may not
 
 Analytics are presented at two levels:
 
-* Regional Aggregates: Combined results from the three data centers within a specific region.
-* Global Aggregates: Total results across all configured regions and data centers.
+- Regional Aggregates: Combined results from the three data centers within a specific region.
+- Global Aggregates: Total results across all configured regions and data centers.
 
 In the event log, entries are labeled by region or as **Global**. We do not provide granular data for individual data centers.
 
diff --git a/src/content/partials/smart-shield/smart-shield-callout.mdx b/src/content/partials/smart-shield/smart-shield-callout.mdx
index 15c3e70be832e5a..706d52242176099 100644
--- a/src/content/partials/smart-shield/smart-shield-callout.mdx
+++ b/src/content/partials/smart-shield/smart-shield-callout.mdx
@@ -4,4 +4,4 @@
 
 :::note[Smart Shield]
 This functionality is now offered as part of Cloudflare's origin server safeguard, Smart Shield. [Learn more](/smart-shield/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/smart-shield/zone-lockdown.mdx b/src/content/partials/smart-shield/zone-lockdown.mdx
index 77215453e523f54..5181bf0878bc7b3 100644
--- a/src/content/partials/smart-shield/zone-lockdown.mdx
+++ b/src/content/partials/smart-shield/zone-lockdown.mdx
@@ -18,7 +18,7 @@ To bypass zone lockdown using a WAF custom rule:
 
    To allow a specific Health Check, verify if the user agent contains the first 16 characters of the Health Check ID.
 
-3. Set the action to *Skip* and the corresponding feature to **Zone Lockdown** under **More components to skip**.
+3. Set the action to _Skip_ and the corresponding feature to **Zone Lockdown** under **More components to skip**.
 
 ### Via the API
 
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
index d19bdad602512e2..a743f57b374347a 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
@@ -1,50 +1,49 @@
 ---
 {}
-
 ---
 
-import { APIRequest } from "~/components"
+import { APIRequest } from "~/components";
 
 Below is a curl example and the associated data being posted to the API.
 
 **API example:**
 
 <APIRequest
-  path="/zones/{zone_id}/spectrum/apps"
-  method="POST"
-  json={{
-    dns: {
-      type: "CNAME",
-      name: "spectrum-cname.example.com"
-    },
-    ip_firewall: false,
-    protocol: "tcp/22",
-    proxy_protocol: "off",
-    tls: "off",
-    origin_dns: {
-      name: "cname-to-origin.example.com",
-      ttl: 1200
-    },
-    origin_port: 22
-  }}
+	path="/zones/{zone_id}/spectrum/apps"
+	method="POST"
+	json={{
+		dns: {
+			type: "CNAME",
+			name: "spectrum-cname.example.com",
+		},
+		ip_firewall: false,
+		protocol: "tcp/22",
+		proxy_protocol: "off",
+		tls: "off",
+		origin_dns: {
+			name: "cname-to-origin.example.com",
+			ttl: 1200,
+		},
+		origin_port: 22,
+	}}
 />
 
 **Example data:**
 
 ```json
 {
-  "dns": {
-    "type": "CNAME",
-    "name": "spectrum-cname.example.com"
-  },
-  "ip_firewall": false,
-  "protocol": "tcp/22",
-  "proxy_protocol": "off",
-  "tls": "off",
-  "origin_dns": {
-    "name": "cname-to-origin.example.com",
-    "ttl": 1200
-  },
-  "origin_port": 22
+	"dns": {
+		"type": "CNAME",
+		"name": "spectrum-cname.example.com"
+	},
+	"ip_firewall": false,
+	"protocol": "tcp/22",
+	"proxy_protocol": "off",
+	"tls": "off",
+	"origin_dns": {
+		"name": "cname-to-origin.example.com",
+		"ttl": 1200
+	},
+	"origin_port": 22
 }
 ```
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
index 7bca9b160ea79e7..2e354499765aa68 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { DashButton } from "~/components"
+import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Spectrum** page.
 
diff --git a/src/content/partials/speed/rocket-loader-csp.mdx b/src/content/partials/speed/rocket-loader-csp.mdx
index 5f9b9948eb37a16..415fe7be153ccd2 100644
--- a/src/content/partials/speed/rocket-loader-csp.mdx
+++ b/src/content/partials/speed/rocket-loader-csp.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> in place for your domain, you will need to [update your headers](/fundamentals/reference/policies-compliances/content-security-policies/#product-requirements) to support Rocket Loader.
diff --git a/src/content/partials/speed/user-agents.mdx b/src/content/partials/speed/user-agents.mdx
index c0837b69232398f..f5ce8588ee1bd80 100644
--- a/src/content/partials/speed/user-agents.mdx
+++ b/src/content/partials/speed/user-agents.mdx
@@ -1,19 +1,17 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 For **IPv6** Cloudflare Observatory tests originate from **ASN 15169** or **ASN 132892** and are generated with the following user agents:
 
-* Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
-* Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
+- Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
+- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
 
 For **IPv4** Cloudflare Observatory tests originate from **ASN 396982** and are generated with the following user agents:
 
-* Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
-* Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
+- Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
+- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
 
 :::
diff --git a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
index f31818fcb7c6970..684249cf2e95c7c 100644
--- a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
+++ b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The available options for **Validation method** and **Certificate Validity Period** may vary depending on the certificate authority you choose and the hostnames that you include in your Advanced certificate order.
diff --git a/src/content/partials/ssl/acm-definition.mdx b/src/content/partials/ssl/acm-definition.mdx
index dd03df9af1b9a04..b7e35411b9f6074 100644
--- a/src/content/partials/ssl/acm-definition.mdx
+++ b/src/content/partials/ssl/acm-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Use advanced certificates when you want something more customizable than [Universal SSL](/ssl/edge-certificates/universal-ssl/) but still want the convenience of SSL certificate issuance and renewal.
diff --git a/src/content/partials/ssl/acm-validate-cert.mdx b/src/content/partials/ssl/acm-validate-cert.mdx
index 28d8bc6f0d5532f..9927c34e5e8158d 100644
--- a/src/content/partials/ssl/acm-validate-cert.mdx
+++ b/src/content/partials/ssl/acm-validate-cert.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 To check whether your certificates have been validated and reissued:
 
-* **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
-* **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
+- **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
+- **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
diff --git a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
index 1d472785e89e8e2..dff294bdc66047e 100644
--- a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
+++ b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```bash
@@ -24,4 +23,4 @@ curl --silent \
 --header "X-Auth-Email: $MYAUTHEMAIL" \
 --header "X-Auth-Key: $MYAUTHKEY" \
 --data "$request_body"
-```
\ No newline at end of file
+```
diff --git a/src/content/partials/ssl/caa-records-added-by-cf.mdx b/src/content/partials/ssl/caa-records-added-by-cf.mdx
index 1a4489c3befb910..5ff6ca31c6bf4b5 100644
--- a/src/content/partials/ssl/caa-records-added-by-cf.mdx
+++ b/src/content/partials/ssl/caa-records-added-by-cf.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare adds CAA records automatically in the following situations:
@@ -11,7 +10,7 @@ Cloudflare adds CAA records automatically in the following situations:
 These records make sure Cloudflare can still issue Universal certificates on your behalf.
 
 :::note[Subdomain zones caveat]
-CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) -  with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
+CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) - with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
 :::
 
 If Cloudflare has automatically added CAA records on your behalf, these records will not appear in the Cloudflare dashboard. However, if you run a command line query using `dig`, you can see any existing CAA records, including those added by Cloudflare (replacing `example.com` with your own domain on Cloudflare):
diff --git a/src/content/partials/ssl/caa-records-definition.mdx b/src/content/partials/ssl/caa-records-definition.mdx
index 0154a3d0a0fc6b4..fd0343ee0ae9acb 100644
--- a/src/content/partials/ssl/caa-records-definition.mdx
+++ b/src/content/partials/ssl/caa-records-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A Certificate Authority Authorization (CAA) DNS record specifies which certificate authorities (CAs) are allowed to issue certificates for a domain. This record reduces the chance of unauthorized certificate issuance and promotes standardization across your organization.
diff --git a/src/content/partials/ssl/change-encryption-mode-api.mdx b/src/content/partials/ssl/change-encryption-mode-api.mdx
index 56ae28c0a1ced82..c9c759459aa123f 100644
--- a/src/content/partials/ssl/change-encryption-mode-api.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To adjust your encryption mode with the API, send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `ssl` as the setting name in the URI path, and the `value` parameter set to your desired setting (`off`, `flexible`, `full`, `strict`, or `origin_pull`).
diff --git a/src/content/partials/ssl/change-encryption-mode-dash.mdx b/src/content/partials/ssl/change-encryption-mode-dash.mdx
index e7e6afa2c5c9740..a831eabba8bed79 100644
--- a/src/content/partials/ssl/change-encryption-mode-dash.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/cipher-suites-api-linkout.mdx b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
index ceda6f3443c4a1f..630e79915c01b64 100644
--- a/src/content/partials/ssl/cipher-suites-api-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
\ No newline at end of file
+If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
diff --git a/src/content/partials/ssl/cipher-suites-definition.mdx b/src/content/partials/ssl/cipher-suites-definition.mdx
index eea7fc621379f4f..659728684c4e279 100644
--- a/src/content/partials/ssl/cipher-suites-definition.mdx
+++ b/src/content/partials/ssl/cipher-suites-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cipher suites are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/) (and therefore separate from the [SSL/TLS protocol](/ssl/reference/protocols/)).
diff --git a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
index 8d202297dd8d513..308d5f6b820a7d9 100644
--- a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
\ No newline at end of file
+For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
diff --git a/src/content/partials/ssl/ciphers-api-general-notes.mdx b/src/content/partials/ssl/ciphers-api-general-notes.mdx
index 431555f3a04bc82..3461784c3991163 100644
--- a/src/content/partials/ssl/ciphers-api-general-notes.mdx
+++ b/src/content/partials/ssl/ciphers-api-general-notes.mdx
@@ -1,7 +1,7 @@
 ---
 {}
-
 ---
+
 To configure cipher suites per hostname, replace the first two lines by the following:
 
 ```bash
diff --git a/src/content/partials/ssl/cname-cert-verification.mdx b/src/content/partials/ssl/cname-cert-verification.mdx
index 6803cb1241595a9..1af431ba8e62f82 100644
--- a/src/content/partials/ssl/cname-cert-verification.mdx
+++ b/src/content/partials/ssl/cname-cert-verification.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare contacts one of our certificate authority (CA) providers and asks them to issue certificates for the specified hostname. The CA will then inform Cloudflare that we need to demonstrate control of this hostname by returning a `$DCV_TOKEN` at a specified `$DCV_FILENAME`; both the token and the filename are randomly generated by the CA and not known to Cloudflare ahead of time.
diff --git a/src/content/partials/ssl/csr-definition.mdx b/src/content/partials/ssl/csr-definition.mdx
index c3f8ebb7fdbce8c..a77784b8eeb8a0f 100644
--- a/src/content/partials/ssl/csr-definition.mdx
+++ b/src/content/partials/ssl/csr-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Generate a Certificate Signing Request (CSR) to get a custom certificate from the Certificate Authority (CA) of your choice while maintaining control of the private key on Cloudflare. The private key associated with the CSR will be generated by Cloudflare and will never leave our network.
diff --git a/src/content/partials/ssl/custom-cert-ciphers.mdx b/src/content/partials/ssl/custom-cert-ciphers.mdx
index 3f3a5f7954778d6..bba82764fc568eb 100644
--- a/src/content/partials/ssl/custom-cert-ciphers.mdx
+++ b/src/content/partials/ssl/custom-cert-ciphers.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before deploying custom certificates to Cloudflare's global network, Cloudflare automatically groups the certificates into certificate packs.
@@ -9,6 +8,6 @@ A certificate pack is a group of certificates that share the same set of hostnam
 
 Each pack can include up to three certificates, one from each of the following signature algorithms:
 
-* `SHA-2/RSA`
-* `SHA-2/ECDSA`
-* `SHA-1/RSA`
+- `SHA-2/RSA`
+- `SHA-2/ECDSA`
+- `SHA-1/RSA`
diff --git a/src/content/partials/ssl/custom-cert-openssl-commands.mdx b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
index 547be3cbf37680a..7bcbf7ba02b6ffc 100644
--- a/src/content/partials/ssl/custom-cert-openssl-commands.mdx
+++ b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 1. Run the following command to generate a 4096-bit RSA private key, using AES-256 encryption. Enter a passphrase when prompted.
diff --git a/src/content/partials/ssl/custom-certificates-definition.mdx b/src/content/partials/ssl/custom-certificates-definition.mdx
index 64d10e717e0b1ed..8b65b18a079f395 100644
--- a/src/content/partials/ssl/custom-certificates-definition.mdx
+++ b/src/content/partials/ssl/custom-certificates-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom certificates are meant for Business and Enterprise customers who want to use their own SSL certificates.
diff --git a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
index 7cf70fd8b8e6960..fd1a1fad0352eb7 100644
--- a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
+++ b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Custom Origin Trust Store allows you to upload certificate authorities (CAs) that Cloudflare will use to authenticate connections to your origin server. Use this feature to override the default trust store with your preferred CA or CAs.
diff --git a/src/content/partials/ssl/dcv-certificate-renewal.mdx b/src/content/partials/ssl/dcv-certificate-renewal.mdx
index 966d6f3d11cb207..77fff64fa5de773 100644
--- a/src/content/partials/ssl/dcv-certificate-renewal.mdx
+++ b/src/content/partials/ssl/dcv-certificate-renewal.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
 Even if you manually handle DCV when issuing certificates in a [partial DNS setup](/dns/zone-setups/partial-setup/), at certificate renewal, Cloudflare will attempt to automatically perform DCV via HTTP.
 
 If all of the following conditions are confirmed at the first attempt, the renewal happens automatically via [HTTP](/ssl/edge-certificates/changing-dcv-method/methods/http/).
 
-* Hostnames are proxied.
-* Hostnames on the certificate resolve to the IPs assigned to the zone.
-* The certificate does not contain wildcards.
+- Hostnames are proxied.
+- Hostnames on the certificate resolve to the IPs assigned to the zone.
+- The certificate does not contain wildcards.
 
 :::note
 To automatically renew certificates that do not meet the referred criteria, consider using [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/).
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/dcv-conflicting-records.mdx b/src/content/partials/ssl/dcv-conflicting-records.mdx
index c6a89d7d1f55c86..e932ebc41dd7175 100644
--- a/src/content/partials/ssl/dcv-conflicting-records.mdx
+++ b/src/content/partials/ssl/dcv-conflicting-records.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Remove previous TXT records]
@@ -11,4 +10,4 @@ Existing TXT records for `_acme-challenge` will conflict with the delegated DCV
 _acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
 ```
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/dcv-definition.mdx b/src/content/partials/ssl/dcv-definition.mdx
index 88a6cd79a67b650..c5748e6902bfec1 100644
--- a/src/content/partials/ssl/dcv-definition.mdx
+++ b/src/content/partials/ssl/dcv-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before a certificate authority (CA) will issue a certificate for a domain, the requester must prove they have control over that domain. This process is known as domain control validation (DCV).
diff --git a/src/content/partials/ssl/dcv-invalid-token-situations.mdx b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
index d705eaac712405c..785d89543fd4097 100644
--- a/src/content/partials/ssl/dcv-invalid-token-situations.mdx
+++ b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Tokens may also become invalid upon validation failure. For more details, refer to [Domain control validation flow](/ssl/edge-certificates/changing-dcv-method/dcv-flow/#dcv-tokens).
diff --git a/src/content/partials/ssl/dcv-path-security.mdx b/src/content/partials/ssl/dcv-path-security.mdx
index 5501d6eb5a3f734..eb4a9601201193b 100644
--- a/src/content/partials/ssl/dcv-path-security.mdx
+++ b/src/content/partials/ssl/dcv-path-security.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When your certificate is in `pending_validation` and valid tokens are in place, some security features targeting your zone's path for `/.well-known/*` can be automatically bypassed.
diff --git a/src/content/partials/ssl/dcv-renewal-fallback.mdx b/src/content/partials/ssl/dcv-renewal-fallback.mdx
index fd0e39d48edac6e..662ad6b134f61e1 100644
--- a/src/content/partials/ssl/dcv-renewal-fallback.mdx
+++ b/src/content/partials/ssl/dcv-renewal-fallback.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If any one of the conditions is not met, the certificate renewal falls back to your chosen method and you will need to [repeat the DCV process](/ssl/edge-certificates/changing-dcv-method/methods/txt/#get-dcv-values) manually.
diff --git a/src/content/partials/ssl/dcv-validate-patch.mdx b/src/content/partials/ssl/dcv-validate-patch.mdx
index 26c6cda69d9927a..173f9e888cce376 100644
--- a/src/content/partials/ssl/dcv-validate-patch.mdx
+++ b/src/content/partials/ssl/dcv-validate-patch.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To request an immediate recheck, send another [PATCH request](/api/resources/ssl/subresources/verification/methods/edit/) with the same `validation_method` as your current validation method.
diff --git a/src/content/partials/ssl/encryption-mode-definition.mdx b/src/content/partials/ssl/encryption-mode-definition.mdx
index 145f8a9e7617a8f..22d2c160d68d3b2 100644
--- a/src/content/partials/ssl/encryption-mode-definition.mdx
+++ b/src/content/partials/ssl/encryption-mode-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Your zone's **SSL/TLS Encryption Mode** controls how Cloudflare manages two connections: one between your visitors and Cloudflare, and the other between Cloudflare and your origin server.
diff --git a/src/content/partials/ssl/enforce-https-recommendation.mdx b/src/content/partials/ssl/enforce-https-recommendation.mdx
index 9c7faf843ba079a..3bedac422468cc2 100644
--- a/src/content/partials/ssl/enforce-https-recommendation.mdx
+++ b/src/content/partials/ssl/enforce-https-recommendation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Even if your application has an active edge certificate, visitors can still access resources over unsecured HTTP connections.
diff --git a/src/content/partials/ssl/error-rate-limiting.mdx b/src/content/partials/ssl/error-rate-limiting.mdx
index ba85796a11af004..239593e80b8d7b9 100644
--- a/src/content/partials/ssl/error-rate-limiting.mdx
+++ b/src/content/partials/ssl/error-rate-limiting.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 As mentioned in [Certificate authorities](/ssl/reference/certificate-authorities/), specific CAs may have their own limitations. If you use Let’s Encrypt and receive the error below, it means you hit the [duplicate certificate limit](https://letsencrypt.org/docs/duplicate-certificate-limit/) imposed by Let's Encrypt.
diff --git a/src/content/partials/ssl/generic-validation-process.mdx b/src/content/partials/ssl/generic-validation-process.mdx
index 0b3edf72e02fea2..e67dc0bfa07e1cb 100644
--- a/src/content/partials/ssl/generic-validation-process.mdx
+++ b/src/content/partials/ssl/generic-validation-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/geokey-manager-v1.mdx b/src/content/partials/ssl/geokey-manager-v1.mdx
index 38388aa647932b8..c2a97612cff66a7 100644
--- a/src/content/partials/ssl/geokey-manager-v1.mdx
+++ b/src/content/partials/ssl/geokey-manager-v1.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 The first version of Geo Key Manager supports 3 regions: U.S., E.U., and a set of High Security Data Centers. If you would like to restrict your private key to another country or region, [apply for the closed beta](https://www.cloudflare.com/lp/geo-key-manager/) of the new version.
diff --git a/src/content/partials/ssl/get-started-additional-features.mdx b/src/content/partials/ssl/get-started-additional-features.mdx
index 9e7f8fdb53fbfc6..e975392ac50b3c9 100644
--- a/src/content/partials/ssl/get-started-additional-features.mdx
+++ b/src/content/partials/ssl/get-started-additional-features.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 After you have chosen your encryption mode and enforced HTTPS connections, evaluate the following settings:
 
-* [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
-* [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
-* [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
+- [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
+- [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
+- [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
diff --git a/src/content/partials/ssl/http-cname-validation-process.mdx b/src/content/partials/ssl/http-cname-validation-process.mdx
index f5e56eee7eb0688..33d5cd00e2c0499 100644
--- a/src/content/partials/ssl/http-cname-validation-process.mdx
+++ b/src/content/partials/ssl/http-cname-validation-process.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/http-to-txt-schedule.mdx b/src/content/partials/ssl/http-to-txt-schedule.mdx
index 7081625d6110114..94368fb7c494aae 100644
--- a/src/content/partials/ssl/http-to-txt-schedule.mdx
+++ b/src/content/partials/ssl/http-to-txt-schedule.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 - 90-days certificates: after failing for 15 days
 - 30-days certificates: after failing for 7 days
-- 14-days certificates: after failing for 3 days
\ No newline at end of file
+- 14-days certificates: after failing for 3 days
diff --git a/src/content/partials/ssl/keyless-ssl-definition.mdx b/src/content/partials/ssl/keyless-ssl-definition.mdx
index 12b1d3ad53d80e7..7199cc1bbca9e0a 100644
--- a/src/content/partials/ssl/keyless-ssl-definition.mdx
+++ b/src/content/partials/ssl/keyless-ssl-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Keyless SSL allows security-conscious clients to upload their own custom certificates and benefit from Cloudflare, but without exposing their TLS private keys.
diff --git a/src/content/partials/ssl/keyless-tunnel-setup.mdx b/src/content/partials/ssl/keyless-tunnel-setup.mdx
index ff09dc073729618..fc296217a5ba2fd 100644
--- a/src/content/partials/ssl/keyless-tunnel-setup.mdx
+++ b/src/content/partials/ssl/keyless-tunnel-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 This process differs depending on whether you are using the [command line](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/create-local-tunnel/) or the [Cloudflare dashboard](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/).
diff --git a/src/content/partials/ssl/keyless-upload-preamble.mdx b/src/content/partials/ssl/keyless-upload-preamble.mdx
index 1c57296ce980ad0..ae8cfa436a5f20f 100644
--- a/src/content/partials/ssl/keyless-upload-preamble.mdx
+++ b/src/content/partials/ssl/keyless-upload-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Before your key servers can be configured, you must next upload the corresponding SSL certificates to Cloudflare’s edge. During TLS termination, Cloudflare will present these certificates to connecting browsers and then (for non-resumed sessions) communicate with the specified key server to complete the handshake.
diff --git a/src/content/partials/ssl/origin-ca-pause-error.mdx b/src/content/partials/ssl/origin-ca-pause-error.mdx
index a3d2919fcdfbca3..282af35186d78e9 100644
--- a/src/content/partials/ssl/origin-ca-pause-error.mdx
+++ b/src/content/partials/ssl/origin-ca-pause-error.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
 
-Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
\ No newline at end of file
+Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
index 5ce503fae04a18f..ee3c0a0ba7c5962 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -11,10 +10,9 @@ This applies to customers using [Universal](/ssl/edge-certificates/universal-ssl
 
 If one of the hostnames on the certificate is not proxying traffic through Cloudflare, certificate issuance and renewal will vary based on the type of certificate you are using:
 
-* **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
-* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
-
+- **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
+- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 :::tip
 If all hostnames are proxied and non-wildcard but you are using [TXT](/ssl/edge-certificates/changing-dcv-method/methods/txt/) as DCV method for advanced certificates, also consider [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to simplify the process.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
index c506b1aaf0cbe6b..59e04d484d2bc13 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 For wildcard hostname certificates, certificate issuance and renewal varies based on the type of certificate you are using:
 
-* **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
-* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+- **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
+- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 If you cannot use Delegated DCV, you need to use [TXT based DCV](/ssl/edge-certificates/changing-dcv-method/methods/txt/) for certificate issuance and renewal. This means you will need to place one TXT DCV token for every hostname on the certificate. If one or more of the hostnames on the certificate fails to validate, the certificate will not be issued or renewed.
 
diff --git a/src/content/partials/ssl/ssl-mode-errors.mdx b/src/content/partials/ssl/ssl-mode-errors.mdx
index 6c4766d72ecd2c2..2182e11414cdb4f 100644
--- a/src/content/partials/ssl/ssl-mode-errors.mdx
+++ b/src/content/partials/ssl/ssl-mode-errors.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Depending on your origin configuration, you may have to adjust settings to avoid [Mixed Content errors](/ssl/troubleshooting/mixed-content-errors/) or [redirect loops](/ssl/troubleshooting/too-many-redirects/).
diff --git a/src/content/partials/ssl/ssl-mode-no-aop.mdx b/src/content/partials/ssl/ssl-mode-no-aop.mdx
index 4818962513eef71..de73f0f75904e95 100644
--- a/src/content/partials/ssl/ssl-mode-no-aop.mdx
+++ b/src/content/partials/ssl/ssl-mode-no-aop.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Authenticated Origin Pull](/ssl/origin-configuration/authenticated-origin-pull/) does not work when your [**SSL/TLS encryption mode**](/ssl/origin-configuration/ssl-modes/) is set to **Off** or **Flexible**.
diff --git a/src/content/partials/ssl/ssl-recommender-post-setup.mdx b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
index f742c710a2e813c..c20c95e8c8d9494 100644
--- a/src/content/partials/ssl/ssl-recommender-post-setup.mdx
+++ b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 Once enabled, the SSL/TLS Recommender runs an origin scan using the user agent `Cloudflare-SSLDetector` and ignores your `robots.txt` file (except for rules explicitly targeting the user agent).
 
 Based on this initial scan, the Recommender may decide that you could use a stronger [SSL encryption mode](/ssl/origin-configuration/ssl-modes/). It will never recommend a weaker option than what is currently configured.
 
-If so, it will send the application owner an email with the recommended option and add a *Recommended by Cloudflare* tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
+If so, it will send the application owner an email with the recommended option and add a _Recommended by Cloudflare_ tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
 
 If you do not receive an email, keep your current **SSL encryption mode**.
diff --git a/src/content/partials/ssl/ssl-recommender-prereqs.mdx b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
index 5a469237108799e..54a2fb9f09c8532 100644
--- a/src/content/partials/ssl/ssl-recommender-prereqs.mdx
+++ b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 To make sure you do not inadvertently block the **SSL/TLS Recommender**, review your settings to make sure your domain:
 
-* Is accessible.
-* Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
-* Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
+- Is accessible.
+- Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
+- Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
diff --git a/src/content/partials/ssl/test-tls-version.mdx b/src/content/partials/ssl/test-tls-version.mdx
index 610dd99b691b6f9..7795c23bee8e13c 100644
--- a/src/content/partials/ssl/test-tls-version.mdx
+++ b/src/content/partials/ssl/test-tls-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To test supported TLS versions, attempt a request to your website or application while specifying a TLS version.
@@ -17,4 +16,4 @@ If the TLS version you are testing is blocked by Cloudflare, the TLS handshake i
 
 :::note
 Local VPN or a device security client may prevent insecure connections using legacy protocols like TLS 1.0. Make sure to disable such network or security client before running the test on your device.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
index 40fff440b9fdfbe..39ab2370be87926 100644
--- a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
+++ b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You cannot set specific TLS 1.3 ciphers. Instead, you can enable [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) for your entire zone and Cloudflare will use [all applicable TLS 1.3 cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites/). In combination with this, you can still [disable weak cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) for TLS 1.0-1.2.
diff --git a/src/content/partials/ssl/total-tls-character-limitation.mdx b/src/content/partials/ssl/total-tls-character-limitation.mdx
index 2f4bd6c578be433..958bf51b7fa1f6c 100644
--- a/src/content/partials/ssl/total-tls-character-limitation.mdx
+++ b/src/content/partials/ssl/total-tls-character-limitation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
-Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
\ No newline at end of file
+Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
diff --git a/src/content/partials/ssl/txt-validation-api.mdx b/src/content/partials/ssl/txt-validation-api.mdx
index cdf1f38f24b2fcc..26ae11200ce4d88 100644
--- a/src/content/partials/ssl/txt-validation-api.mdx
+++ b/src/content/partials/ssl/txt-validation-api.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 You can access these tokens using the API with the [`GET` request](/api/resources/ssl/subresources/certificate_packs/methods/get/) and including `status=pending_validation` as a request parameter.
@@ -9,31 +8,31 @@ For example, here are two tokens highlighted in the API response for a wildcard
 
 ```json title="Response" {13,14,15,16,17,18,19,20,21,22,23,24}
 {
-  "result": [
-    {
-      "id": "<CERTIFICATE_ID>",
-      "type": "advanced",
-      "hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
-      "primary_certificate": "0",
-      "status": "pending_validation",
-      "certificates": [],
-      "created_on": "2022-10-12T21:46:21.979150Z",
-      "validity_days": 90,
-      "validation_method": "txt",
-      "validation_records": [
-        {
-          "status": "pending",
-          "txt_name": "_acme-challenge.<DOMAIN>.com",
-          "txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
-        },
-        {
-          "status": "pending",
-          "txt_name": "_acme-challenge.<DOMAIN>.com",
-          "txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
-        }
-      ],
-      "certificate_authority": "google"
-    }
-  ]
+	"result": [
+		{
+			"id": "<CERTIFICATE_ID>",
+			"type": "advanced",
+			"hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
+			"primary_certificate": "0",
+			"status": "pending_validation",
+			"certificates": [],
+			"created_on": "2022-10-12T21:46:21.979150Z",
+			"validity_days": 90,
+			"validation_method": "txt",
+			"validation_records": [
+				{
+					"status": "pending",
+					"txt_name": "_acme-challenge.<DOMAIN>.com",
+					"txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
+				},
+				{
+					"status": "pending",
+					"txt_name": "_acme-challenge.<DOMAIN>.com",
+					"txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
+				}
+			],
+			"certificate_authority": "google"
+		}
+	]
 }
 ```
diff --git a/src/content/partials/ssl/txt-validation-dashboard.mdx b/src/content/partials/ssl/txt-validation-dashboard.mdx
index e32eed0b158c9b1..af46b2c550b4575 100644
--- a/src/content/partials/ssl/txt-validation-dashboard.mdx
+++ b/src/content/partials/ssl/txt-validation-dashboard.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/txt-validation-definition.mdx b/src/content/partials/ssl/txt-validation-definition.mdx
index 01de109728d2ed3..adb5d6e522dfef2 100644
--- a/src/content/partials/ssl/txt-validation-definition.mdx
+++ b/src/content/partials/ssl/txt-validation-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 TXT record validation requires the creation of a TXT record in the hostname's authoritative DNS.
diff --git a/src/content/partials/ssl/txt-validation-preamble.mdx b/src/content/partials/ssl/txt-validation-preamble.mdx
index 93faafe1adf5447..f373dcb972851f5 100644
--- a/src/content/partials/ssl/txt-validation-preamble.mdx
+++ b/src/content/partials/ssl/txt-validation-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you [create a new certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) and choose the validation method of **TXT**, your tokens will be ready after a few seconds.
diff --git a/src/content/partials/ssl/universal-ssl-enable-full.mdx b/src/content/partials/ssl/universal-ssl-enable-full.mdx
index ccc7dd4e0694511..4eae263d68c1083 100644
--- a/src/content/partials/ssl/universal-ssl-enable-full.mdx
+++ b/src/content/partials/ssl/universal-ssl-enable-full.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For domains on a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], your domain should **automatically** receive its Universal SSL certificate within **15 minutes to 24 hours** of domain activation[^2].
diff --git a/src/content/partials/ssl/universal-ssl-validity.mdx b/src/content/partials/ssl/universal-ssl-validity.mdx
index ab44a9287adf96f..10512702dea5b86 100644
--- a/src/content/partials/ssl/universal-ssl-validity.mdx
+++ b/src/content/partials/ssl/universal-ssl-validity.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For Universal certificates, Cloudflare controls the validity periods and certificate authorities (CAs), making sure that renewal always occur.
@@ -9,4 +8,4 @@ For Universal certificates, Cloudflare controls the validity periods and certifi
 If you are on a [CNAME setup (partial)](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup), make sure [Domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/) is configured correctly. Refer to [Troubleshooting DCV](/ssl/edge-certificates/changing-dcv-method/troubleshooting/) for further help.
 :::
 
-Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
\ No newline at end of file
+Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
diff --git a/src/content/partials/ssl/ussl-limitations-solutions.mdx b/src/content/partials/ssl/ussl-limitations-solutions.mdx
index ee503a418a8aacd..3fdeeda79faea70 100644
--- a/src/content/partials/ssl/ussl-limitations-solutions.mdx
+++ b/src/content/partials/ssl/ussl-limitations-solutions.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 To prevent insecure connections on a multi-level subdomain, do one of the following:
 
-* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
-* Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
-* Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
+- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
+- Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
+- Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
 
 If none of these solutions work, you could also remove the multi-level subdomain.
diff --git a/src/content/partials/ssl/ussl-limitations-table.mdx b/src/content/partials/ssl/ussl-limitations-table.mdx
index f2f932a5a2b1a7e..7d391d48177e70e 100644
--- a/src/content/partials/ssl/ussl-limitations-table.mdx
+++ b/src/content/partials/ssl/ussl-limitations-table.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 By default, Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) only cover your apex domain and one level of subdomain.
diff --git a/src/content/partials/ssl/validation-level-note.mdx b/src/content/partials/ssl/validation-level-note.mdx
index 03bd8c76025c290..2eb371ceb102413 100644
--- a/src/content/partials/ssl/validation-level-note.mdx
+++ b/src/content/partials/ssl/validation-level-note.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Certificates issued through Cloudflare - [Universal](/ssl/edge-certificates/universal-ssl/), [Advanced](/ssl/edge-certificates/advanced-certificate-manager/), and [Custom Hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) certificates - are Domain Validated (DV). You can [upload a custom certificate](/ssl/edge-certificates/custom-certificates/) if your organization needs OV or EV certificates.
diff --git a/src/content/partials/stream/android_playback_code_snippet.mdx b/src/content/partials/stream/android_playback_code_snippet.mdx
index 6962729cc8a9fce..e60e829108231a9 100644
--- a/src/content/partials/stream/android_playback_code_snippet.mdx
+++ b/src/content/partials/stream/android_playback_code_snippet.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```kotlin
diff --git a/src/content/partials/stream/chromecast_limitations.mdx b/src/content/partials/stream/chromecast_limitations.mdx
index 0aa204b3ebbd6bb..e7a4b69eed6c016 100644
--- a/src/content/partials/stream/chromecast_limitations.mdx
+++ b/src/content/partials/stream/chromecast_limitations.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/stream/ios_playback_code_snippet.mdx b/src/content/partials/stream/ios_playback_code_snippet.mdx
index 5b446692c4df2da..f9d23f1f2ea17d1 100644
--- a/src/content/partials/stream/ios_playback_code_snippet.mdx
+++ b/src/content/partials/stream/ios_playback_code_snippet.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ```swift
diff --git a/src/content/partials/stream/prereqs.mdx b/src/content/partials/stream/prereqs.mdx
index 3c8c70289c8042a..abc70769ba595b1 100644
--- a/src/content/partials/stream/prereqs.mdx
+++ b/src/content/partials/stream/prereqs.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Before you can play videos, you must first [upload a video to Cloudflare Stream](/stream/uploading-videos/) or be [actively streaming to a live input](/stream/stream-live)
 
-
 :::
diff --git a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
index aa189ea437225d8..4359b8da3c410e2 100644
--- a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
+++ b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Before you can play live video, you must first be [actively streaming to a live input](/stream/stream-live/start-stream-live).
 
-
 :::
diff --git a/src/content/partials/stream/srt-supported-modes.mdx b/src/content/partials/stream/srt-supported-modes.mdx
index e265ce9ecd07404..2355744270cb533 100644
--- a/src/content/partials/stream/srt-supported-modes.mdx
+++ b/src/content/partials/stream/srt-supported-modes.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 Stream only supports the SRT caller mode, which is responsible for broadcasting a live stream after a connection is established.
 
-
 :::
diff --git a/src/content/partials/style-guide/directory-listing-definition.mdx b/src/content/partials/style-guide/directory-listing-definition.mdx
index e301ae54c2538d0..3fe2c759e1c53cc 100644
--- a/src/content/partials/style-guide/directory-listing-definition.mdx
+++ b/src/content/partials/style-guide/directory-listing-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
\ No newline at end of file
+Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
diff --git a/src/content/partials/style-guide/icons.mdx b/src/content/partials/style-guide/icons.mdx
index 0ff4d9b2bdff1b2..e7565605607107d 100644
--- a/src/content/partials/style-guide/icons.mdx
+++ b/src/content/partials/style-guide/icons.mdx
@@ -3,4 +3,4 @@ params:
   - component
 ---
 
-Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
\ No newline at end of file
+Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
diff --git a/src/content/partials/style-guide/public-stats-definition.mdx b/src/content/partials/style-guide/public-stats-definition.mdx
index 0feedc632bbe330..5c337b32e6019f3 100644
--- a/src/content/partials/style-guide/public-stats-definition.mdx
+++ b/src/content/partials/style-guide/public-stats-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
\ No newline at end of file
+The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
diff --git a/src/content/partials/style-guide/tab-guidance.mdx b/src/content/partials/style-guide/tab-guidance.mdx
index bbabd5ac6d12ff3..0c4938e1fd9a2ce 100644
--- a/src/content/partials/style-guide/tab-guidance.mdx
+++ b/src/content/partials/style-guide/tab-guidance.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section. 
+The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section.
 
-Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
\ No newline at end of file
+Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
diff --git a/src/content/partials/style-guide/table-guidelines.mdx b/src/content/partials/style-guide/table-guidelines.mdx
index add12c6f1f8fea9..5095d31cef3b176 100644
--- a/src/content/partials/style-guide/table-guidelines.mdx
+++ b/src/content/partials/style-guide/table-guidelines.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
\ No newline at end of file
+Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
diff --git a/src/content/partials/support/2fa-enable.mdx b/src/content/partials/support/2fa-enable.mdx
index f93e4811432751f..dcde0ef633ea1f1 100644
--- a/src/content/partials/support/2fa-enable.mdx
+++ b/src/content/partials/support/2fa-enable.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 We recommend that all Cloudflare user account holders enable two-factor authentication (2FA) to keep your accounts secure. 
diff --git a/src/content/partials/support/2fa-overview.mdx b/src/content/partials/support/2fa-overview.mdx
index 566f562331ebb06..ef795a849728569 100644
--- a/src/content/partials/support/2fa-overview.mdx
+++ b/src/content/partials/support/2fa-overview.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Two-factor authentication (2FA) allows user account owners to add an additional layer of login security to Cloudflare accounts. This additional authentication step requires you to provide both something you know, such as a Cloudflare password, and something you have, such as an authentication code from a mobile device.
diff --git a/src/content/partials/tenant/account-definition.mdx b/src/content/partials/tenant/account-definition.mdx
index 02febfffaee6f3b..9ad1c4090b9bb5a 100644
--- a/src/content/partials/tenant/account-definition.mdx
+++ b/src/content/partials/tenant/account-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An entity that contains various settings, users, and resources (zones, Zero Trust applications, Workers).
diff --git a/src/content/partials/tenant/account-details-preamble.mdx b/src/content/partials/tenant/account-details-preamble.mdx
index 67723262e1208c1..f43626e1f450432 100644
--- a/src/content/partials/tenant/account-details-preamble.mdx
+++ b/src/content/partials/tenant/account-details-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An [**Account**](/tenant/glossary/#account) will contain various settings, resources, and subscriptions to products for users. Each Tenant can have multiple associated accounts.
diff --git a/src/content/partials/tenant/account-details.mdx b/src/content/partials/tenant/account-details.mdx
index 0fe39346e3d974f..beac7c19ba854a0 100644
--- a/src/content/partials/tenant/account-details.mdx
+++ b/src/content/partials/tenant/account-details.mdx
@@ -1,27 +1,20 @@
 ---
 {}
-
 ---
 
-
-
 To retrieve a list of accounts associated with a Tenant details, send a `GET` request to the `/tenants/{tenant_id}/accounts` endpoint. You can find the Tenant tag and all Tenants associated with the user with the [**Tenant Details**](/tenant/how-to/get-tenant-details/) API. The Tenant Accounts API also requires pagination passed as query parameters:
 
-* `page` number
-
-  * Page number of accounts list response, indexed from 1
-
-* `per_page` number
-
-  * Number of accounts to display per page
-
-* `order` string
-  * (optional) Order by a specific column, has to be a valid top-level key from the response
+- `page` number
+  - Page number of accounts list response, indexed from 1
 
-  * `direction` number
-    * (optional) 0 for ascending or 1 for descending, is 0 by default
+- `per_page` number
+  - Number of accounts to display per page
 
+- `order` string
+  - (optional) Order by a specific column, has to be a valid top-level key from the response
 
+  - `direction` number
+    - (optional) 0 for ascending or 1 for descending, is 0 by default
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/tenants/{tenant_id}/accounts?page=1&per_page=10" \
diff --git a/src/content/partials/tenant/account-preamble.mdx b/src/content/partials/tenant/account-preamble.mdx
index f8b3baf7f3775a0..e1243d170a99457 100644
--- a/src/content/partials/tenant/account-preamble.mdx
+++ b/src/content/partials/tenant/account-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Each customer or team that uses Cloudflare should have their own account. This ensures proper security and access of resources. Each account acts as a container of zones and other resources. Depending on your needs, you may even provision multiple accounts for a single customer or team.
diff --git a/src/content/partials/tenant/create-account-api.mdx b/src/content/partials/tenant/create-account-api.mdx
index 7c40a5a7b6cd770..0783c47157f77f3 100644
--- a/src/content/partials/tenant/create-account-api.mdx
+++ b/src/content/partials/tenant/create-account-api.mdx
@@ -1,51 +1,39 @@
 ---
 {}
-
 ---
 
-
-
 To create an account using the API, make a `POST` request to the `/accounts` endpoint and include the following values:
 
-* `name` string
+- `name` string
+  - The name of the account that is displayed in the Cloudflare dashboard.
 
-  * The name of the account that is displayed in the Cloudflare dashboard.
+- `type` enum
+  - Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
 
-* `type` enum
+- `unit` object
+  - Information related to the tenant unit.
 
-  * Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
-
-* `unit` object
-  * Information related to the tenant unit.
-
-  * `id` string
-    * (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
+  - `id` string
+    - (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
 
 ### Know-Your-Customer (optional)
 
 All KYC parameters are text fields, have a 120 character limit, and are optional unless enforced by the Tenant.
 
-* `business_name` string
-
-  * (optional) The name of the business associated with this account.
-
-* `business_address` string
-
-  * (optional) The address of the business associated with this account.
-
-* `business_email` string
-
-  * (optional) The email of the business associated with this account.
-
-* `business_phone` string
-
-  * (optional) The phone number of the business associated with this account.
+- `business_name` string
+  - (optional) The name of the business associated with this account.
 
-* `external_metadata` string
+- `business_address` string
+  - (optional) The address of the business associated with this account.
 
-  * (optional) External metadata for this account.
+- `business_email` string
+  - (optional) The email of the business associated with this account.
 
+- `business_phone` string
+  - (optional) The phone number of the business associated with this account.
 
+- `external_metadata` string
+  - (optional) External metadata for this account.
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/accounts" \
@@ -62,17 +50,17 @@ A successful request will return an HTTP status of `200` and the following respo
 
 ```json title="Response"
 {
-  "result": {
-    "id": "2bab6ace8c72ed3f09b9eca6db1396bb",
-    "name": "<ACCOUNT_NAME>",
-    "type": "standard",
-    "settings": {
-      "enforce_twofactor": false
-    }
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
+	"result": {
+		"id": "2bab6ace8c72ed3f09b9eca6db1396bb",
+		"name": "<ACCOUNT_NAME>",
+		"type": "standard",
+		"settings": {
+			"enforce_twofactor": false
+		}
+	},
+	"success": true,
+	"errors": [],
+	"messages": []
 }
 ```
 
diff --git a/src/content/partials/tenant/create-account-dash.mdx b/src/content/partials/tenant/create-account-dash.mdx
index 5ac799f25ff0d84..b419db913d27be1 100644
--- a/src/content/partials/tenant/create-account-dash.mdx
+++ b/src/content/partials/tenant/create-account-dash.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To create an account under your tenant using the dashboard:
diff --git a/src/content/partials/tenant/create-account-subscription.mdx b/src/content/partials/tenant/create-account-subscription.mdx
index 3079c476a2951ff..5de32a989695839 100644
--- a/src/content/partials/tenant/create-account-subscription.mdx
+++ b/src/content/partials/tenant/create-account-subscription.mdx
@@ -1,25 +1,17 @@
 ---
 {}
-
 ---
 
-
-
 To create an account subscription, send a [POST](/api/resources/accounts/subresources/subscriptions/methods/create/) request to the `/accounts/{account_id}/subscriptions` endpoint and include the following values:
 
-* `rate_plan` object
-
-  * Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
-
-* `component_values` array
-
-  * Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
-
-* `frequency` string
-
-  * How often the subscription is renewed automatically (defaults to `"monthly"`).
+- `rate_plan` object
+  - Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
 
+- `component_values` array
+  - Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
 
+- `frequency` string
+  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
 ```bash title="Request"
 curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/subscriptions' \
diff --git a/src/content/partials/tenant/create-zone-subscription.mdx b/src/content/partials/tenant/create-zone-subscription.mdx
index 4535e906db668f5..bf71f6c38a3b69f 100644
--- a/src/content/partials/tenant/create-zone-subscription.mdx
+++ b/src/content/partials/tenant/create-zone-subscription.mdx
@@ -1,27 +1,19 @@
 ---
 {}
-
 ---
 
-
-
 To create a zone subscription, typically used to upgrade a zone's plan from `PARTNERS_FREE` to a paid [Zone plan](/tenant/reference/subscriptions/#zone-plans), send a [POST](/api/resources/zones/subresources/subscriptions/methods/create/) request to the `/zones/{zone_id}/subscription` endpoint and include the following values:
 
-* `rate_plan` object
-
-  * Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
-
-* `component_values` array
-
-  * Additional services depending on your reseller agreement, such as additional `page_rules`.
-
-* `frequency` string
-
-  * How often the subscription is renewed automatically (defaults to `"monthly"`).
+- `rate_plan` object
+  - Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
 
+- `component_values` array
+  - Additional services depending on your reseller agreement, such as additional `page_rules`.
 
+- `frequency` string
+  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-```bash title="Request (without &#x60;component_values&#x60;)"
+```bash title="Request (without `component_values`)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
@@ -33,7 +25,7 @@ curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 }'
 ```
 
-```bash title="Request (with &#x60;component_values&#x60;)"
+```bash title="Request (with `component_values`)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
diff --git a/src/content/partials/tenant/resource-definition.mdx b/src/content/partials/tenant/resource-definition.mdx
index e8eb77e0f94146a..ccd4f6b5cf492d4 100644
--- a/src/content/partials/tenant/resource-definition.mdx
+++ b/src/content/partials/tenant/resource-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A resource is an entity owned by an account, which could be a zone/domain, a Workers instance, or a Zero Trust application.
diff --git a/src/content/partials/tenant/tenant-admin-definition.mdx b/src/content/partials/tenant/tenant-admin-definition.mdx
index fad90445024fac8..93e8c088ed8bd38 100644
--- a/src/content/partials/tenant/tenant-admin-definition.mdx
+++ b/src/content/partials/tenant/tenant-admin-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once you sign a partner agreement with Cloudflare, we create a special Tenant account and then add your user to that account as a **Tenant admin**. Cloudflare can add multiple users as Tenant admins upon request.
diff --git a/src/content/partials/tenant/tenant-definition.mdx b/src/content/partials/tenant/tenant-definition.mdx
index 750a5387fbdb3c1..c3f7cca0a2e8b7d 100644
--- a/src/content/partials/tenant/tenant-definition.mdx
+++ b/src/content/partials/tenant/tenant-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A **Tenant** is a special type of Cloudflare account that contains other accounts and resources.
diff --git a/src/content/partials/tenant/tenant-details-preamble.mdx b/src/content/partials/tenant/tenant-details-preamble.mdx
index d1b84c3b3cbac7c..a54abfd6e57347a 100644
--- a/src/content/partials/tenant/tenant-details-preamble.mdx
+++ b/src/content/partials/tenant/tenant-details-preamble.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A [**Tenant Admin**](/tenant/glossary/#tenant-admin)'s unit and membership details will be used for access of resources and all Tenant operations on the API. The unit ID (`unit_tag`), for example, can be used to create an account on a specific unit.
diff --git a/src/content/partials/tenant/tenant-details.mdx b/src/content/partials/tenant/tenant-details.mdx
index 131ba5be5b9e779..9ee665e4b7dff30 100644
--- a/src/content/partials/tenant/tenant-details.mdx
+++ b/src/content/partials/tenant/tenant-details.mdx
@@ -1,14 +1,9 @@
 ---
 {}
-
 ---
 
-
-
 To retrieve tenant details, send a `GET` request to the `/user/tenants` endpoint:
 
-
-
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/user/tenants" \
 --header "X-Auth-Email: <EMAIL>" \
diff --git a/src/content/partials/tenant/user-definition.mdx b/src/content/partials/tenant/user-definition.mdx
index 6b17b01a9d90808..a7bb17ad18df033 100644
--- a/src/content/partials/tenant/user-definition.mdx
+++ b/src/content/partials/tenant/user-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A member of a Cloudflare account with their own user profile and [an associated role](/fundamentals/manage-members/roles/) that specifies their privileges within that account.
diff --git a/src/content/partials/terraform/create-r2-buckets.mdx b/src/content/partials/terraform/create-r2-buckets.mdx
index 13c5a4d7689c5d6..3e04904347b494d 100644
--- a/src/content/partials/terraform/create-r2-buckets.mdx
+++ b/src/content/partials/terraform/create-r2-buckets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { TabItem, Tabs } from "~/components";
diff --git a/src/content/partials/terraform/find-ids-managed-rulesets.mdx b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
index e93b48bff9fb814..f096359f08c52fb 100644
--- a/src/content/partials/terraform/find-ids-managed-rulesets.mdx
+++ b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy the managed rulesets.
 
-* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
 
 The deployment of managed rulesets via Terraform requires that you use the ruleset IDs. To find the IDs of managed rulesets, use the [List account rulesets](/api/resources/rulesets/methods/list/) operation. The response will include the description and IDs of existing managed rulesets.
diff --git a/src/content/partials/terraform/find-ids.mdx b/src/content/partials/terraform/find-ids.mdx
index 25181bac1db4ec9..989917bed7dc690 100644
--- a/src/content/partials/terraform/find-ids.mdx
+++ b/src/content/partials/terraform/find-ids.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy rulesets.
 
-* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
diff --git a/src/content/partials/terraform/import-delete-existing-rulesets.mdx b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
index 3b1d669425223b3..b31987c47c68650 100644
--- a/src/content/partials/terraform/import-delete-existing-rulesets.mdx
+++ b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 Terraform assumes that it has complete control over account and zone rulesets. If you already have rulesets configured in your account or zone, do one of the following:
 
-* [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
-* Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
+- [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
+- Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
diff --git a/src/content/partials/terraform/v4-code-snippets.mdx b/src/content/partials/terraform/v4-code-snippets.mdx
index 99de18e73442fe3..485490e7bf66300 100644
--- a/src/content/partials/terraform/v4-code-snippets.mdx
+++ b/src/content/partials/terraform/v4-code-snippets.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 :::note
 Terraform code snippets below refer to the v4 SDK only.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/terraform/v5-code-snippets.mdx b/src/content/partials/terraform/v5-code-snippets.mdx
index 4bd83b42ff17813..65ddb58c386e133 100644
--- a/src/content/partials/terraform/v5-code-snippets.mdx
+++ b/src/content/partials/terraform/v5-code-snippets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::note
diff --git a/src/content/partials/time-services/ntp-definition.mdx b/src/content/partials/time-services/ntp-definition.mdx
index 76dc31d5a57dd6a..df9e63e8a5ab83d 100644
--- a/src/content/partials/time-services/ntp-definition.mdx
+++ b/src/content/partials/time-services/ntp-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [Network Time Protocol](https://tools.ietf.org/html/rfc1305) (NTP) is an Internet protocol designed to synchronize time between computer systems communicating over unreliable and variable-latency network paths. Cloudflare offers its version of NTP for free so you can use our [global anycast network](https://www.cloudflare.com/network/) to synchronize time from our closest server.
diff --git a/src/content/partials/turnstile/challenge-behavior.mdx b/src/content/partials/turnstile/challenge-behavior.mdx
index f60a738f5071a3e..ff0bebf920921ee 100644
--- a/src/content/partials/turnstile/challenge-behavior.mdx
+++ b/src/content/partials/turnstile/challenge-behavior.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare issues challenges through the [Challenge Platform](/cloudflare-challenges/), which is the same underlying technology powering [Turnstile](/turnstile/).
diff --git a/src/content/partials/turnstile/privacy-policy.mdx b/src/content/partials/turnstile/privacy-policy.mdx
index cc7c482ea104785..061f021d37cc27a 100644
--- a/src/content/partials/turnstile/privacy-policy.mdx
+++ b/src/content/partials/turnstile/privacy-policy.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
\ No newline at end of file
+As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
diff --git a/src/content/partials/turnstile/proxied-hostnames.mdx b/src/content/partials/turnstile/proxied-hostnames.mdx
index e8beeab649b6d39..e9d1fd903e735be 100644
--- a/src/content/partials/turnstile/proxied-hostnames.mdx
+++ b/src/content/partials/turnstile/proxied-hostnames.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 If your hostname is proxied through Cloudflare, visitors may experience challenges on your webpages.
diff --git a/src/content/partials/turnstile/security-requirements.mdx b/src/content/partials/turnstile/security-requirements.mdx
index 7a31837435e6e89..2569ee7839e2ca3 100644
--- a/src/content/partials/turnstile/security-requirements.mdx
+++ b/src/content/partials/turnstile/security-requirements.mdx
@@ -1,9 +1,7 @@
 ---
 {}
-
 ---
 
-
 - Server-side validation is mandatory. It is critical to enforce Turnstile tokens with the Siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. You must call Siteverify to complete your Turnstile configuration. Otherwise, it is incomplete and will result in zeroes for token validation when viewing your metrics in [Turnstile Analytics](/turnstile/turnstile-analytics/).
 
 - Tokens expire after 300 seconds (5 minutes). Each token can only be validated once. Expired or used tokens must be replaced with fresh challenges.
diff --git a/src/content/partials/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/siteverify-warning.mdx
index 4e5b0a232868dfd..979c06c7a94acd4 100644
--- a/src/content/partials/turnstile/siteverify-warning.mdx
+++ b/src/content/partials/turnstile/siteverify-warning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 :::caution[Warning]
diff --git a/src/content/partials/turnstile/siteverify.mdx b/src/content/partials/turnstile/siteverify.mdx
index 59ba0e6f92f190a..775e57ebf87175b 100644
--- a/src/content/partials/turnstile/siteverify.mdx
+++ b/src/content/partials/turnstile/siteverify.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
 It is important to [call the Siteverify API](/turnstile/get-started/server-side-validation/). Without calling Siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
 
 - Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
 - Tokens expire after five minutes. Validation must occur within this window to be effective.
-- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
\ No newline at end of file
+- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
diff --git a/src/content/partials/turnstile/test-secret-key.mdx b/src/content/partials/turnstile/test-secret-key.mdx
index 67d4fb5139a1840..142da6b947bd3e3 100644
--- a/src/content/partials/turnstile/test-secret-key.mdx
+++ b/src/content/partials/turnstile/test-secret-key.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 You can test the dummy token generated with testing sitekey via Siteverify API with the testing secret key. Your production secret keys will reject dummy tokens.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
diff --git a/src/content/partials/turnstile/test-sitekey.mdx b/src/content/partials/turnstile/test-sitekey.mdx
index 5ecb3a3c4062605..5bb6f0697d38eaf 100644
--- a/src/content/partials/turnstile/test-sitekey.mdx
+++ b/src/content/partials/turnstile/test-sitekey.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
 You can test your Turnstile widget on your webpage without triggering an actual Cloudflare Challenge by using a testing sitekey.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
diff --git a/src/content/partials/turnstile/troubleshooting-steps.mdx b/src/content/partials/turnstile/troubleshooting-steps.mdx
index 8e9ff7625e051fb..471234502a31d07 100644
--- a/src/content/partials/turnstile/troubleshooting-steps.mdx
+++ b/src/content/partials/turnstile/troubleshooting-steps.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 1. Verify your browser compatibility.
-    - Turnstile supports all major browsers, except Internet Explorer.
-    - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
-    - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
+   - Turnstile supports all major browsers, except Internet Explorer.
+   - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
+   - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
 2. Disable your browser extensions.
-    - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
-    - Temporarily disable all extensions and reload the page.
+   - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
+   - Temporarily disable all extensions and reload the page.
 3. Enable JavaScript.
-    - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
+   - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
 4. Try Incognito or Private mode.
-    - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
+   - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
 5. Test another browser or device.
-    - Switch to a different browser or device to see if the issue is specific to your current setup.
+   - Switch to a different browser or device to see if the issue is specific to your current setup.
 6. Avoid VPNs or proxies.
-    - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
+   - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
 7. Switch to a different network.
-    - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
+   - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
diff --git a/src/content/partials/turnstile/widget-components.mdx b/src/content/partials/turnstile/widget-components.mdx
index 36da69ec11fc53f..a72f62cd2d99b6f 100644
--- a/src/content/partials/turnstile/widget-components.mdx
+++ b/src/content/partials/turnstile/widget-components.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 Each widget gets its own unique sitekey and secret key pair, and options for configurations.
 
-| Component | Description |
-| --- | --- |
-| Sitekey | Public key used to invoke the Turnstile widget on your site. |
-| Secret key | Private key used for server-side token validation. |
-| Configurations | Mode, hostnames, appearance settings, and other options. |
+| Component      | Description                                                  |
+| -------------- | ------------------------------------------------------------ |
+| Sitekey        | Public key used to invoke the Turnstile widget on your site. |
+| Secret key     | Private key used for server-side token validation.           |
+| Configurations | Mode, hostnames, appearance settings, and other options.     |
diff --git a/src/content/partials/vectorize/vectorize-ga.mdx b/src/content/partials/vectorize/vectorize-ga.mdx
index efd48735d4aac5d..78ba16f7ac1273b 100644
--- a/src/content/partials/vectorize/vectorize-ga.mdx
+++ b/src/content/partials/vectorize/vectorize-ga.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Vectorize is now Generally Available]
 
-
 To report bugs or give feedback, go to the [#vectorize Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
-
 :::
diff --git a/src/content/partials/vectorize/vectorize-pricing.mdx b/src/content/partials/vectorize/vectorize-pricing.mdx
index 9281365f50e95ed..8ff2bf6036a4c2c 100644
--- a/src/content/partials/vectorize/vectorize-pricing.mdx
+++ b/src/content/partials/vectorize/vectorize-pricing.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-|                                     | [Workers Free](/workers/platform/pricing/#workers)       | [Workers Paid](/workers/platform/pricing/#workers)                              |
-| ----------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------- |
-| **Total queried vector dimensions** | 30 million queried vector dimensions / month             | First 50 million queried vector dimensions / month included + $0.01 per million |
-| **Total stored vector dimensions**  | 5 million stored vector dimensions                       | First 10 million stored vector dimensions + $0.05 per 100 million               |
+|                                     | [Workers Free](/workers/platform/pricing/#workers) | [Workers Paid](/workers/platform/pricing/#workers)                              |
+| ----------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------- |
+| **Total queried vector dimensions** | 30 million queried vector dimensions / month       | First 50 million queried vector dimensions / month included + $0.01 per million |
+| **Total stored vector dimensions**  | 5 million stored vector dimensions                 | First 10 million stored vector dimensions + $0.05 per 100 million               |
 
 ### Calculating vector dimensions
 
diff --git a/src/content/partials/version-management/create-environment-situation.mdx b/src/content/partials/version-management/create-environment-situation.mdx
index 63f1307158b6f24..f6971602bd7ee8d 100644
--- a/src/content/partials/version-management/create-environment-situation.mdx
+++ b/src/content/partials/version-management/create-environment-situation.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Based on your organization's needs, you may need to create additional environments to test and roll out changes.
diff --git a/src/content/partials/version-management/edit-version.mdx b/src/content/partials/version-management/edit-version.mdx
index 385307cecb41c36..39944dba67d8e50 100644
--- a/src/content/partials/version-management/edit-version.mdx
+++ b/src/content/partials/version-management/edit-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,12 +10,12 @@ To change between different versions of your zone:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and a domain that has version management. The Global Configuration of your domain will load.
 3. Go to the product or feature you wish to modify.
-   * **If the product or feature is available for versioning**: The last version you were working on will load.
-   * **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
+   - **If the product or feature is available for versioning**: The last version you were working on will load.
+   - **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
 4. Ensure that the configuration or version displayed in the domain summary bar is the one you would like to work on. If not, select the version in the domain summary bar to open the version switcher.
 
 :::note
diff --git a/src/content/partials/version-management/enable-default-creation.mdx b/src/content/partials/version-management/enable-default-creation.mdx
index e4ea2ec7726c964..8e98769c2ae8675 100644
--- a/src/content/partials/version-management/enable-default-creation.mdx
+++ b/src/content/partials/version-management/enable-default-creation.mdx
@@ -1,19 +1,16 @@
 ---
 {}
-
 ---
 
 Once you [enable](/version-management/how-to/enable/) Version Management, Cloudflare will automatically create:
 
-* **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
-* **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
+- **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
+- **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
 
 :::caution[Important]
 
-
 Any changes made to the **Global Configuration** will immediately apply to your zone and all versions of your zone, affecting live traffic.
 
-
 :::
 
 On the Environments page, you can create default environments for **Production**, **Staging**, and **Development**.
diff --git a/src/content/partials/version-management/enable-versioning.mdx b/src/content/partials/version-management/enable-versioning.mdx
index 0602c8e8c03f543..12ef04c2c918b0e 100644
--- a/src/content/partials/version-management/enable-versioning.mdx
+++ b/src/content/partials/version-management/enable-versioning.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -11,7 +10,7 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
@@ -19,8 +18,6 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 :::note
 
-
 If you cannot enable Version Management, make sure your zone, account, and user meet the [requirements](/version-management/#requirements).
 
-
 :::
diff --git a/src/content/partials/version-management/environment-defaults.mdx b/src/content/partials/version-management/environment-defaults.mdx
index 896a639507362a4..572b0f7b00346e2 100644
--- a/src/content/partials/version-management/environment-defaults.mdx
+++ b/src/content/partials/version-management/environment-defaults.mdx
@@ -1,8 +1,7 @@
 ---
 {}
-
 ---
 
-* **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
-* **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
-* **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
+- **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
+- **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
+- **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
diff --git a/src/content/partials/version-management/environment-definition.mdx b/src/content/partials/version-management/environment-definition.mdx
index 8219f760421603b..378169d4dcb3cba 100644
--- a/src/content/partials/version-management/environment-definition.mdx
+++ b/src/content/partials/version-management/environment-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 An environment is a place to test different versions of your zone configurations.
diff --git a/src/content/partials/version-management/production-read-only-default.mdx b/src/content/partials/version-management/production-read-only-default.mdx
index 309f5eee6b6b858..9f1294d9a8e859c 100644
--- a/src/content/partials/version-management/production-read-only-default.mdx
+++ b/src/content/partials/version-management/production-read-only-default.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 **Production** is a read-only environment by default. This means that any version associated with **Production** also becomes read-only. This configuration prevents another member of your account from accidentally editing the version associated with your live traffic. You can change this configuration by editing the environment.
diff --git a/src/content/partials/version-management/promote-version.mdx b/src/content/partials/version-management/promote-version.mdx
index 9fa55abd7e19289..953f69ab8ea0963 100644
--- a/src/content/partials/version-management/promote-version.mdx
+++ b/src/content/partials/version-management/promote-version.mdx
@@ -1,16 +1,14 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
 
-
 To promote a version:
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/test-version.mdx b/src/content/partials/version-management/test-version.mdx
index 30f9c66058586c5..26ffc6023ca8be6 100644
--- a/src/content/partials/version-management/test-version.mdx
+++ b/src/content/partials/version-management/test-version.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
@@ -9,7 +8,7 @@ Once you have made changes to a version, apply that version to your lowest-ranke
 
 1. Log in to the Cloudflare dashboard.
 
-    <DashButton url="/?to=/:account/home" />
+   <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/version-definition.mdx b/src/content/partials/version-management/version-definition.mdx
index 32f24171ac0cc3f..23ed20a7ece8e28 100644
--- a/src/content/partials/version-management/version-definition.mdx
+++ b/src/content/partials/version-management/version-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A version is a collection of configurations related to your zone, such as WAF custom rules and [other optimization configurations](/version-management/reference/available-configurations/).
diff --git a/src/content/partials/waf/api-create-ruleset-with-rule.mdx b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
index 04b31a71d329c75..18ec3b89654dcc2 100644
--- a/src/content/partials/waf/api-create-ruleset-with-rule.mdx
+++ b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To define a specific position for the new rule, include a `position` object in the request body according to the guidelines in [Change the order of a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/#change-the-order-of-a-rule-in-a-ruleset).
diff --git a/src/content/partials/waf/list-advantages.mdx b/src/content/partials/waf/list-advantages.mdx
index d5fed7a8acd3fbc..d6d8663d04e3c6e 100644
--- a/src/content/partials/waf/list-advantages.mdx
+++ b/src/content/partials/waf/list-advantages.mdx
@@ -1,11 +1,10 @@
 ---
 {}
-
 ---
 
-* When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
-* When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
-* Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
+- When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
+- When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
+- Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
 
 When you update the content of a list, any rules that use the list are automatically updated, so you can make a single change to your list rather than modify rules individually.
 
diff --git a/src/content/partials/waf/managed-lists.mdx b/src/content/partials/waf/managed-lists.mdx
index 8b6a68a42f9fb86..aebc0ae400a11c4 100644
--- a/src/content/partials/waf/managed-lists.mdx
+++ b/src/content/partials/waf/managed-lists.mdx
@@ -6,8 +6,8 @@
 | ----------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
 | Cloudflare Open Proxies                         | `cf.open_proxies`   | IP addresses of known open HTTP and SOCKS proxy endpoints, which are frequently used to launch attacks and hide attackers identity. |
 | Cloudflare Anonymizers                          | `cf.anonymizer`     | IP addresses of known anonymizers (Open SOCKS Proxies, VPNs, and TOR nodes).                                                        |
-| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers. |
+| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers.                                                                                                  |
 | Cloudflare Malware                              | `cf.malware`        | IP addresses of known sources of malware.                                                                                           |
 | Cloudflare Botnets, Command and Control Servers | `cf.botnetcc`       | IP addresses of known botnet command-and-control servers.                                                                           |
 
-<br />
\ No newline at end of file
+<br />
diff --git a/src/content/partials/waf/open-ports-blocked-traffic.mdx b/src/content/partials/waf/open-ports-blocked-traffic.mdx
index 98358a33d289ffd..e360487eafc6582 100644
--- a/src/content/partials/waf/open-ports-blocked-traffic.mdx
+++ b/src/content/partials/waf/open-ports-blocked-traffic.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Due to the nature of Cloudflare's anycast network, ports other than `80` and `443` will be open so that Cloudflare can serve traffic for other customers on these ports. In general, Cloudflare makes available several different products on [Cloudflare IPs](https://www.cloudflare.com/ips), so you can expect tools like Netcat and security scanners to report these non-standard ports as open in specific conditions. If you have questions on security compliance, review [Cloudflare's certifications and compliance resources](https://www.cloudflare.com/en-gb/trust-hub/compliance-resources/) and contact your Cloudflare enterprise account manager for more information.
diff --git a/src/content/partials/waf/rate-limiting-best-practices.mdx b/src/content/partials/waf/rate-limiting-best-practices.mdx
index 5f059b73120f923..0ef94060427faa0 100644
--- a/src/content/partials/waf/rate-limiting-best-practices.mdx
+++ b/src/content/partials/waf/rate-limiting-best-practices.mdx
@@ -1,10 +1,9 @@
 ---
 {}
-
 ---
 
-* [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
-* [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
-* [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
-* [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
-* [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
+- [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
+- [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
+- [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
+- [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
+- [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
diff --git a/src/content/partials/waf/rate-limiting-rule-parameters.mdx b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
index 00a4d92d21e6462..ecbeba6002d94e2 100644
--- a/src/content/partials/waf/rate-limiting-rule-parameters.mdx
+++ b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
@@ -1,15 +1,14 @@
 ---
 {}
-
 ---
 
-* An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
-* An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
+- An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
+- An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
 
 Besides these two parameters, rate limiting rules require the following additional parameters:
 
-* **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
-* **Period**: The period of time to consider (in seconds) when evaluating the rate.
-* **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
-* **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
-* **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
+- **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
+- **Period**: The period of time to consider (in seconds) when evaluating the rate.
+- **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
+- **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
+- **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
diff --git a/src/content/partials/waf/rules-next-steps-table.mdx b/src/content/partials/waf/rules-next-steps-table.mdx
index 8f12446af3318fa..b2513ef838112da 100644
--- a/src/content/partials/waf/rules-next-steps-table.mdx
+++ b/src/content/partials/waf/rules-next-steps-table.mdx
@@ -6,9 +6,9 @@ params:
 
 import { Markdown } from "~/components";
 
-| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                     |
+| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                       |
 | Update a rule             | <p>Use the [Update a zone ruleset rule](/api/resources/rulesets/methods/update/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Update a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/).</p> |
 | Delete a rule             | <p>Use the [Delete a zone ruleset rule](/api/resources/rulesets/methods/delete/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Delete a rule in a ruleset](/ruleset-engine/rulesets-api/delete-rule/).</p> |
 
diff --git a/src/content/partials/waiting-room/change-queueing-method.mdx b/src/content/partials/waiting-room/change-queueing-method.mdx
index 3ff0fa35e97cda9..3a7226abca98756 100644
--- a/src/content/partials/waiting-room/change-queueing-method.mdx
+++ b/src/content/partials/waiting-room/change-queueing-method.mdx
@@ -1,17 +1,14 @@
 ---
 {}
-
 ---
 
 Though you can change your [queueing method](/waiting-room/reference/queueing-methods/), it may affect users if your waiting room is actively queueing:
 
-* **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
-* **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
+- **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
+- **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
 
 :::note
 
-
 If you change the queueing method from FIFO > Random > FIFO, users will be ordered by their original entry time.
 
-
 :::
diff --git a/src/content/partials/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/queue-all.mdx
index f8625465ac3beeb..fe401b22131a2d6 100644
--- a/src/content/partials/waiting-room/queue-all.mdx
+++ b/src/content/partials/waiting-room/queue-all.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To queue all visitors prior to a time-based offering, set up a pre-queue as part of a [waiting room event](/waiting-room/additional-options/create-events/#create-an-event-from-the-dashboard).
diff --git a/src/content/partials/waiting-room/queue-some.mdx b/src/content/partials/waiting-room/queue-some.mdx
index a2ae7dd6d08055a..373a1bf37d6b081 100644
--- a/src/content/partials/waiting-room/queue-some.mdx
+++ b/src/content/partials/waiting-room/queue-some.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 To queue visitors only when necessary:
diff --git a/src/content/partials/warp-client/modes-options.mdx b/src/content/partials/warp-client/modes-options.mdx
index 9582cee987393f3..2965f0ed7c28f20 100644
--- a/src/content/partials/warp-client/modes-options.mdx
+++ b/src/content/partials/warp-client/modes-options.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## WARP modes
@@ -23,11 +22,11 @@ Beyond the two modes of operation, the WARP app lets you configure additional op
 
 The following is a list of options you can configure in the **Connection** tab:
 
-* **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
-* **DNS Protocol**: The available options depend on the WARP mode you have enabled:
-  * **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
-  * **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
-  * **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
-* **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
+- **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
+- **DNS Protocol**: The available options depend on the WARP mode you have enabled:
+  - **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
+  - **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
+  - **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
+- **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
 
 For the **Advanced** options, refer to [Exclude or include network traffic with WARP](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/) for more information.
diff --git a/src/content/partials/web-analytics/web-analytics-definition.mdx b/src/content/partials/web-analytics/web-analytics-definition.mdx
index 1e5015687b288cc..1b6186550086a2c 100644
--- a/src/content/partials/web-analytics/web-analytics-definition.mdx
+++ b/src/content/partials/web-analytics/web-analytics-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Web Analytics provides free, privacy-first analytics for your website without changing your DNS or using Cloudflare’s proxy. Cloudflare Web Analytics helps you understand the performance of your web pages as experienced by your site visitors.
diff --git a/src/content/partials/web-analytics/web-analytics-notifications.mdx b/src/content/partials/web-analytics/web-analytics-notifications.mdx
index 6c43aff254d6a41..b0d9f16da41095b 100644
--- a/src/content/partials/web-analytics/web-analytics-notifications.mdx
+++ b/src/content/partials/web-analytics/web-analytics-notifications.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Web Analytics uses Cloudflare's Notification service. When enabled, Web Analytics sends you a weekly report with aggregate visits, page views and median page load time for all your sites, so you can monitor their performance.
diff --git a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
index 083546fd2a119b7..859414aab8041e6 100644
--- a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
+++ b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
index e713539e0af17a5..f57d62227d76b86 100644
--- a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
+++ b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 For Cloudflare to automatically add the JavaScript snippet, your pages need to have valid HTML.
@@ -20,9 +19,7 @@ For Web Analytics to correctly insert the JavaScript snippet, you would need val
 		<title>Title</title>
 	</head>
 	<body>
-
 		<p>Hello world.</p>
-
 	</body>
 </html>
 ```
diff --git a/src/content/partials/web3/cloudflare-settings.mdx b/src/content/partials/web3/cloudflare-settings.mdx
index 652075c6ca43719..c557eb6be68904f 100644
--- a/src/content/partials/web3/cloudflare-settings.mdx
+++ b/src/content/partials/web3/cloudflare-settings.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Once your gateway becomes [active](/web3/reference/gateway-status/), you can customize the Cloudflare settings associated with your hostname.
diff --git a/src/content/partials/web3/create-gateway-api.mdx b/src/content/partials/web3/create-gateway-api.mdx
index e1952e8378a32e6..8b00c7b740ad9b5 100644
--- a/src/content/partials/web3/create-gateway-api.mdx
+++ b/src/content/partials/web3/create-gateway-api.mdx
@@ -1,12 +1,11 @@
 ---
 {}
-
 ---
 
 To create a gateway using the API, send a [`POST`](/api/resources/web3/subresources/hostnames/methods/create/) request that includes the following parameters:
 
-* `name`: The hostname that will point to the target gateway via a `CNAME` record.
-* `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
+- `name`: The hostname that will point to the target gateway via a `CNAME` record.
+- `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
 
 If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
@@ -27,18 +26,18 @@ The response contains the complete definition of the new gateway.
 
 ```json title="Response"
 {
-  "success": true,
-  "errors": [],
-  "messages": [],
-  "result": {
-    "id": "<WEB3_GATEWAY_ID>",
-    "name": "gateway.example.com",
-    "description": "This is my IPFS gateway.",
-    "status": "active",
-    "target": "ipfs",
-    "dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
-    "created_on": "<CREATED_ON_DATE>",
-    "modified_on": "<MODIFIED_ON_DATE>"
-  }
+	"success": true,
+	"errors": [],
+	"messages": [],
+	"result": {
+		"id": "<WEB3_GATEWAY_ID>",
+		"name": "gateway.example.com",
+		"description": "This is my IPFS gateway.",
+		"status": "active",
+		"target": "ipfs",
+		"dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
+		"created_on": "<CREATED_ON_DATE>",
+		"modified_on": "<MODIFIED_ON_DATE>"
+	}
 }
 ```
diff --git a/src/content/partials/web3/pricing-page-reference.mdx b/src/content/partials/web3/pricing-page-reference.mdx
index 28fa234c7caadd1..80deb4fcdfdd040 100644
--- a/src/content/partials/web3/pricing-page-reference.mdx
+++ b/src/content/partials/web3/pricing-page-reference.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
-
 For more pricing details, refer to the [Web3 product page](https://www.cloudflare.com/application-services/products/web3/).
 
-
 :::
diff --git a/src/content/partials/workers-ai/custom_requirements.mdx b/src/content/partials/workers-ai/custom_requirements.mdx
index 8a34dddf8cb8d82..dfdd8c4a50439f7 100644
--- a/src/content/partials/workers-ai/custom_requirements.mdx
+++ b/src/content/partials/workers-ai/custom_requirements.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Custom requirements]
 
-
 If you have custom requirements like private custom models or higher limits, complete the [Custom Requirements Form](https://forms.gle/axnnpGDb6xrmR31T6). Cloudflare will contact you with next steps.
 
-
 :::
diff --git a/src/content/partials/workers-ai/file_issues.mdx b/src/content/partials/workers-ai/file_issues.mdx
index 3f30780c51c35ed..0e250e4dcc7c3b7 100644
--- a/src/content/partials/workers-ai/file_issues.mdx
+++ b/src/content/partials/workers-ai/file_issues.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::caution[Workers AI is now Generally Available]
 
-
 To report bugs or give feedback, go to the [#workers-ai Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
-
 :::
diff --git a/src/content/partials/workers-ai/openai-compatibility.mdx b/src/content/partials/workers-ai/openai-compatibility.mdx
index 64bc69da90146c0..e245b363ffe1571 100644
--- a/src/content/partials/workers-ai/openai-compatibility.mdx
+++ b/src/content/partials/workers-ai/openai-compatibility.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Workers AI supports OpenAI compatible endpoints for [text generation](/workers-ai/models/) (`/v1/chat/completions`) and [text embedding models](/workers-ai/models/) (`/v1/embeddings`). This allows you to use the same code as you would for your OpenAI commands, but swap in Workers AI easily.
diff --git a/src/content/partials/workers-vpc/create-tunnel-steps.mdx b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
index 9c0aef59ee08b46..4ec8b8731f765c2 100644
--- a/src/content/partials/workers-vpc/create-tunnel-steps.mdx
+++ b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
@@ -1,7 +1,7 @@
 ---
 {}
-
 ---
+
 import { Steps } from "~/components";
 
 <Steps>
diff --git a/src/content/partials/workers-vpc/required-roles.mdx b/src/content/partials/workers-vpc/required-roles.mdx
index 0af2217c4362e96..be0cad6ee37c062 100644
--- a/src/content/partials/workers-vpc/required-roles.mdx
+++ b/src/content/partials/workers-vpc/required-roles.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Workers VPC uses the following account roles:
diff --git a/src/content/partials/workers/ai-local-usage-charges.mdx b/src/content/partials/workers/ai-local-usage-charges.mdx
index 0747f627b173468..392a77552fc2ac9 100644
--- a/src/content/partials/workers/ai-local-usage-charges.mdx
+++ b/src/content/partials/workers/ai-local-usage-charges.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Workers AI local development usage charges]
 
-
 Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
 
-
 :::
diff --git a/src/content/partials/workers/c3-definition.mdx b/src/content/partials/workers/c3-definition.mdx
index 5cad05a047d4f02..06920a6667d56af 100644
--- a/src/content/partials/workers/c3-definition.mdx
+++ b/src/content/partials/workers/c3-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 [C3 (create-cloudflare-cli)](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare) is a command-line tool designed to help you set up and deploy new applications to Cloudflare. In addition to speed, it leverages officially developed templates for Workers and framework-specific setup guides to ensure each new application that you set up follows Cloudflare and any third-party best practices for deployment on the Cloudflare network.
diff --git a/src/content/partials/workers/compute-per-request.mdx b/src/content/partials/workers/compute-per-request.mdx
index 78671c444b721be..3114c34331ad0a5 100644
--- a/src/content/partials/workers/compute-per-request.mdx
+++ b/src/content/partials/workers/compute-per-request.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { TabItem, Tabs } from "~/components"
+import { TabItem, Tabs } from "~/components";
 
 Most Workers are a variation on the default Workers flow:
 
diff --git a/src/content/partials/workers/content_and_contentoptions.mdx b/src/content/partials/workers/content_and_contentoptions.mdx
index 0cd4835706f96a9..d033ded8e7aef53 100644
--- a/src/content/partials/workers/content_and_contentoptions.mdx
+++ b/src/content/partials/workers/content_and_contentoptions.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Content and ContentOptions]
 
-
 Refer to [Global types](/workers/runtime-apis/html-rewriter/#global-types) for more information on `Content` and `ContentOptions`.
 
-
 :::
diff --git a/src/content/partials/workers/dash-creation-next-steps.mdx b/src/content/partials/workers/dash-creation-next-steps.mdx
index 3a4659d03dc4f7e..7e62d21c0a45c4d 100644
--- a/src/content/partials/workers/dash-creation-next-steps.mdx
+++ b/src/content/partials/workers/dash-creation-next-steps.mdx
@@ -13,6 +13,7 @@ Once you have created your Worker script, you can edit and deploy your Worker us
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
+
 2. Select your application.
 3. Select **Edit Code**.
 
diff --git a/src/content/partials/workers/env_and_secrets.mdx b/src/content/partials/workers/env_and_secrets.mdx
index 7efe87d33bc8f1b..60002bb1713e2d1 100644
--- a/src/content/partials/workers/env_and_secrets.mdx
+++ b/src/content/partials/workers/env_and_secrets.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Compare secrets and environment variables
diff --git a/src/content/partials/workers/envvar-example.mdx b/src/content/partials/workers/envvar-example.mdx
index a3680630114446c..1a778eee6e6cefa 100644
--- a/src/content/partials/workers/envvar-example.mdx
+++ b/src/content/partials/workers/envvar-example.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/workers/fetch-html-example-js.mdx b/src/content/partials/workers/fetch-html-example-js.mdx
index 4e19efbae720a72..132f5b1a1063882 100644
--- a/src/content/partials/workers/fetch-html-example-js.mdx
+++ b/src/content/partials/workers/fetch-html-example-js.mdx
@@ -1,17 +1,16 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    /**
-     * Replace `remote` with the host you wish to send requests to
-     */
-    const remote = "https://example.com";
+	async fetch(request) {
+		/**
+		 * Replace `remote` with the host you wish to send requests to
+		 */
+		const remote = "https://example.com";
 
-    return await fetch(remote, request);
-  },
+		return await fetch(remote, request);
+	},
 };
 ```
diff --git a/src/content/partials/workers/get-started-dash.mdx b/src/content/partials/workers/get-started-dash.mdx
index 63f3c464720f5e4..c04cc67a0123925 100644
--- a/src/content/partials/workers/get-started-dash.mdx
+++ b/src/content/partials/workers/get-started-dash.mdx
@@ -1,10 +1,11 @@
 ---
 {}
-
 ---
+
 import { DashButton } from "~/components";
 
 To create your first Worker using the Cloudflare dashboard:
+
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/partials/workers/isolate-cpu-flexibility.mdx b/src/content/partials/workers/isolate-cpu-flexibility.mdx
index 2b2c293912bb364..e8cd1b510fbfbe6 100644
--- a/src/content/partials/workers/isolate-cpu-flexibility.mdx
+++ b/src/content/partials/workers/isolate-cpu-flexibility.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Each [isolate](/workers/reference/how-workers-works/#isolates) has some built-in flexibility to allow for cases where your Worker infrequently runs over the configured limit. If your Worker starts hitting the limit consistently, its execution will be terminated according to the limit configured.
diff --git a/src/content/partials/workers/isolate-description.mdx b/src/content/partials/workers/isolate-description.mdx
index 48b5a2edfba0141..a70b5337ab358ab 100644
--- a/src/content/partials/workers/isolate-description.mdx
+++ b/src/content/partials/workers/isolate-description.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 A single instance of the runtime can run hundreds or thousands of isolates, seamlessly switching between them. Each isolate's memory is completely isolated, so each piece of code is protected from other untrusted or user-written code on the runtime. Isolates are also designed to start very quickly. Instead of creating a virtual machine for each function, an isolate is created within an existing environment. This model eliminates the cold starts of the virtual machine model.
diff --git a/src/content/partials/workers/limits_increase.mdx b/src/content/partials/workers/limits_increase.mdx
index e5fa0351f7a8510..fd226c8f5cbf150 100644
--- a/src/content/partials/workers/limits_increase.mdx
+++ b/src/content/partials/workers/limits_increase.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Need a higher limit?]
 
-
 To request an adjustment to a limit, complete the [Limit Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). If the limit can be increased, Cloudflare will contact you with next steps.
 
-
 :::
diff --git a/src/content/partials/workers/nodejs-compat-howto.mdx b/src/content/partials/workers/nodejs-compat-howto.mdx
index 2dee652a3cb15d3..40e11bbb98811e6 100644
--- a/src/content/partials/workers/nodejs-compat-howto.mdx
+++ b/src/content/partials/workers/nodejs-compat-howto.mdx
@@ -1,11 +1,9 @@
 ---
 {}
-
 ---
 
 :::note
 
 To enable built-in Node.js APIs and polyfills, add the nodejs_compat compatibility flag to your [Wrangler configuration file](/workers/wrangler/configuration/). This also enables nodejs_compat_v2 as long as your compatibility date is 2024-09-23 or later. [Learn more about the Node.js compatibility flag and v2](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
 
-
 :::
diff --git a/src/content/partials/workers/playground-callout.mdx b/src/content/partials/workers/playground-callout.mdx
index 571ac3076e049f8..c854466893a08ef 100644
--- a/src/content/partials/workers/playground-callout.mdx
+++ b/src/content/partials/workers/playground-callout.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Try the Playground]
 
-
 The quickest way to experiment with Cloudflare Workers is in the [Playground](https://workers.cloudflare.com/playground). The Playground does not require any setup. It is an instant way to preview and test a Worker directly in the browser.
 
-
 :::
diff --git a/src/content/partials/workers/prereqs.mdx b/src/content/partials/workers/prereqs.mdx
index 70c0d166cb8f710..3d041a42f4203a5 100644
--- a/src/content/partials/workers/prereqs.mdx
+++ b/src/content/partials/workers/prereqs.mdx
@@ -1,13 +1,15 @@
 ---
 {}
-
 ---
 
-import { Details } from "~/components"
+import { Details } from "~/components";
 
 1. Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up/workers-and-pages).
 2. Install [`Node.js`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
 
 <Details header="Node.js version manager">
-Use a Node version manager like [Volta](https://volta.sh/) or [nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed later in this guide, requires a Node version of `16.17.0` or later.
+	Use a Node version manager like [Volta](https://volta.sh/) or
+	[nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change
+	Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed
+	later in this guide, requires a Node version of `16.17.0` or later.
 </Details>
diff --git a/src/content/partials/workers/redirect-example-js.mdx b/src/content/partials/workers/redirect-example-js.mdx
index b5b219d970896c9..9b764fa66e236ce 100644
--- a/src/content/partials/workers/redirect-example-js.mdx
+++ b/src/content/partials/workers/redirect-example-js.mdx
@@ -1,14 +1,13 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const destinationURL = "https://example.com";
-    const statusCode = 301;
-    return Response.redirect(destinationURL, statusCode);
-  },
+	async fetch(request) {
+		const destinationURL = "https://example.com";
+		const statusCode = 301;
+		return Response.redirect(destinationURL, statusCode);
+	},
 };
 ```
diff --git a/src/content/partials/workers/remote-binding-note.mdx b/src/content/partials/workers/remote-binding-note.mdx
index f05321bd7cd36e3..14a8b741425af69 100644
--- a/src/content/partials/workers/remote-binding-note.mdx
+++ b/src/content/partials/workers/remote-binding-note.mdx
@@ -6,4 +6,4 @@
 
 To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. Learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/workers/request-dot-clone-warning.mdx b/src/content/partials/workers/request-dot-clone-warning.mdx
index 5e9640d3f34d8d2..5371525c77f704e 100644
--- a/src/content/partials/workers/request-dot-clone-warning.mdx
+++ b/src/content/partials/workers/request-dot-clone-warning.mdx
@@ -9,4 +9,4 @@ The body of a [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request
 To avoid errors, create a clone of the Request object with `request.clone()` for each subsequent attempt to access a Request's body.
 Keep in mind that Workers have a [memory limit of 128 MB per Worker](/workers/platform/limits/#memory) and loading particularly large files into a Worker's memory multiple times may reach this limit. To ensure memory usage does not reach this limit, consider using [Streams](/workers/runtime-apis/streams/).
 
-:::
\ No newline at end of file
+:::
diff --git a/src/content/partials/workers/respond-another-site-example-js.mdx b/src/content/partials/workers/respond-another-site-example-js.mdx
index 05c6f264b81aa7f..1e55c7a658919ba 100644
--- a/src/content/partials/workers/respond-another-site-example-js.mdx
+++ b/src/content/partials/workers/respond-another-site-example-js.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    function MethodNotAllowed(request) {
-      return new Response(`Method ${request.method} not allowed.`, {
-        status: 405,
-        headers: {
-          Allow: "GET",
-        },
-      });
-    }
-    // Only GET requests work with this proxy.
-    if (request.method !== "GET") return MethodNotAllowed(request);
-    return fetch(`https://example.com`);
-  },
+	async fetch(request) {
+		function MethodNotAllowed(request) {
+			return new Response(`Method ${request.method} not allowed.`, {
+				status: 405,
+				headers: {
+					Allow: "GET",
+				},
+			});
+		}
+		// Only GET requests work with this proxy.
+		if (request.method !== "GET") return MethodNotAllowed(request);
+		return fetch(`https://example.com`);
+	},
 };
 ```
diff --git a/src/content/partials/workers/return-html-example-js.mdx b/src/content/partials/workers/return-html-example-js.mdx
index 24bed7993c20042..41b5a8db682bcdc 100644
--- a/src/content/partials/workers/return-html-example-js.mdx
+++ b/src/content/partials/workers/return-html-example-js.mdx
@@ -1,22 +1,21 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const html = `<!DOCTYPE html>
+	async fetch(request) {
+		const html = `<!DOCTYPE html>
 		<body>
 		  <h1>Hello World</h1>
 		  <p>This markup was generated by a Cloudflare Worker.</p>
 		</body>`;
 
-    return new Response(html, {
-      headers: {
-        "content-type": "text/html;charset=UTF-8",
-      },
-    });
-  },
+		return new Response(html, {
+			headers: {
+				"content-type": "text/html;charset=UTF-8",
+			},
+		});
+	},
 };
 ```
diff --git a/src/content/partials/workers/return-json-example-js.mdx b/src/content/partials/workers/return-json-example-js.mdx
index 5222c0a889a5073..e81939c499570ad 100644
--- a/src/content/partials/workers/return-json-example-js.mdx
+++ b/src/content/partials/workers/return-json-example-js.mdx
@@ -1,16 +1,15 @@
 ---
 {}
-
 ---
 
 ```js playground
 export default {
-  async fetch(request) {
-    const data = {
-      hello: "world",
-    };
+	async fetch(request) {
+		const data = {
+			hello: "world",
+		};
 
-    return Response.json(data);
-  },
+		return Response.json(data);
+	},
 };
 ```
diff --git a/src/content/partials/workers/service-binding-rpc-example.mdx b/src/content/partials/workers/service-binding-rpc-example.mdx
index 1f67ca0636f4dea..0e2f10a6dad4f77 100644
--- a/src/content/partials/workers/service-binding-rpc-example.mdx
+++ b/src/content/partials/workers/service-binding-rpc-example.mdx
@@ -77,7 +77,6 @@ Worker A can declare a [binding](/workers/runtime-apis/bindings) to Worker B:
 
 Making it possible for Worker A to call the `add()` method from Worker B:
 
-
 <Tabs syncKey="workersExamples">
 
 <TypeScriptExample omitTabs={true}>
diff --git a/src/content/partials/workers/storage-products-table.mdx b/src/content/partials/workers/storage-products-table.mdx
index 9b832c39da70b20..47d0a3281d70912 100644
--- a/src/content/partials/workers/storage-products-table.mdx
+++ b/src/content/partials/workers/storage-products-table.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-| Use-case | Product                                          | Ideal for                                                                                                               |
-| ------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
-| Key-value storage | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                             |
-| Object storage / blob storage | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.         |
-| Accelerate a Postgres or MySQL database | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                                            |
-| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage.  |
-| Lightweight SQL database | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                            |
-| Task processing, batching and messaging | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks. |
-| Vector search & embeddings queries | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.  |
-| Streaming ingestion | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying |
-| Time-series metrics | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL. |
\ No newline at end of file
+| Use-case                                  | Product                                          | Ideal for                                                                                                                                              |
+| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Key-value storage                         | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                                                            |
+| Object storage / blob storage             | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.                                        |
+| Accelerate a Postgres or MySQL database   | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                               |
+| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage. |
+| Lightweight SQL database                  | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                                                           |
+| Task processing, batching and messaging   | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks.                                                          |
+| Vector search & embeddings queries        | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.                           |
+| Streaming ingestion                       | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying                         |
+| Time-series metrics                       | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL.                                |
diff --git a/src/content/partials/workers/testing-pages-functions.mdx b/src/content/partials/workers/testing-pages-functions.mdx
index 568cbc85bd23a01..2d921130e88652f 100644
--- a/src/content/partials/workers/testing-pages-functions.mdx
+++ b/src/content/partials/workers/testing-pages-functions.mdx
@@ -1,12 +1,9 @@
 ---
 {}
-
 ---
 
 :::note[Pages Functions]
 
-
 The content described on this page is also applicable to [Pages Functions](/pages/functions/). Pages Functions are Cloudflare Workers and can be thought of synonymously with Workers in this context.
 
-
 :::
diff --git a/src/content/partials/workers/tutorials-before-you-start.mdx b/src/content/partials/workers/tutorials-before-you-start.mdx
index b33c0af2815ddef..bb2f002bb183c96 100644
--- a/src/content/partials/workers/tutorials-before-you-start.mdx
+++ b/src/content/partials/workers/tutorials-before-you-start.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 ## Before you start
diff --git a/src/content/partials/workers/workers_logs_pricing.mdx b/src/content/partials/workers/workers_logs_pricing.mdx
index 8772eec1debdf90..7e8c152265137aa 100644
--- a/src/content/partials/workers/workers_logs_pricing.mdx
+++ b/src/content/partials/workers/workers_logs_pricing.mdx
@@ -1,13 +1,12 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 Workers Logs is included in both the Free and Paid [Workers plans](/workers/platform/pricing/).
 
-|                    | Log Events Written                                                 | Retention  |
-| ------------------ | ------------------------------------------------------------------ | ---------- |
-| **Workers Free**   | 200,000 per day                                                    | 3 Days     |
-| **Workers Paid**   | 20 million included per month <br /> +$0.60 per additional million | 7 Days     |
+|                  | Log Events Written                                                 | Retention |
+| ---------------- | ------------------------------------------------------------------ | --------- |
+| **Workers Free** | 200,000 per day                                                    | 3 Days    |
+| **Workers Paid** | 20 million included per month <br /> +$0.60 per additional million | 7 Days    |
diff --git a/src/content/partials/workers/wrangler-commands/containers.mdx b/src/content/partials/workers/wrangler-commands/containers.mdx
index e04e280d72c1783..aa5f7677a4557ba 100644
--- a/src/content/partials/workers/wrangler-commands/containers.mdx
+++ b/src/content/partials/workers/wrangler-commands/containers.mdx
@@ -202,14 +202,14 @@ wrangler containers instances 12345678-abcd-1234-abcd-123456789abc --json
 
 ```json output
 [
-  {
-    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
-    "name": "worker-12",
-    "state": "running",
-    "location": "sfo06",
-    "version": 3,
-    "created": "2025-06-01T12:00:00Z"
-  }
+	{
+		"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+		"name": "worker-12",
+		"state": "running",
+		"location": "sfo06",
+		"version": 3,
+		"created": "2025-06-01T12:00:00Z"
+	}
 ]
 ```
 
diff --git a/src/content/partials/workers/wrangler-commands/r2-sql.mdx b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
index 17cd10b4c69f8c1..5c20b7b51c03454 100644
--- a/src/content/partials/workers/wrangler-commands/r2-sql.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
@@ -2,7 +2,14 @@
 {}
 ---
 
-import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand, WranglerNamespace } from "~/components";
+import {
+	Render,
+	AnchorHeading,
+	Type,
+	MetaInfo,
+	WranglerCommand,
+	WranglerNamespace,
+} from "~/components";
 
 :::note
 
@@ -10,4 +17,4 @@ R2 SQL is currently in open beta. Report R2 SQL bugs in [GitHub](https://github.
 
 :::
 
-<WranglerCommand command="r2 sql query" headingLevel={3} />
\ No newline at end of file
+<WranglerCommand command="r2 sql query" headingLevel={3} />
diff --git a/src/content/partials/workers/wrangler-commands/r2.mdx b/src/content/partials/workers/wrangler-commands/r2.mdx
index 3046ac2f72125bb..692fb87d223e3e1 100644
--- a/src/content/partials/workers/wrangler-commands/r2.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2.mdx
@@ -2,7 +2,13 @@
 {}
 ---
 
-import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand } from "~/components";
+import {
+	Render,
+	AnchorHeading,
+	Type,
+	MetaInfo,
+	WranglerCommand,
+} from "~/components";
 
 ## `r2 bucket`
 
@@ -13,21 +19,24 @@ Interact with buckets in an R2 store.
 The `r2 bucket` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 bucket create" headingLevel={3}/>
+<WranglerCommand command="r2 bucket create" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket info" headingLevel={3}/>
+<WranglerCommand command="r2 bucket info" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog disable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket catalog get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket catalog compaction enable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog compaction enable"
+	headingLevel={3}
+/>
 
 Examples:
 
@@ -39,7 +48,10 @@ npx wrangler r2 bucket catalog compaction enable my-bucket --token <TOKEN>
 npx wrangler r2 bucket catalog compaction enable my-bucket my-namespace my-table --target-size 256
 ```
 
-<WranglerCommand command="r2 bucket catalog compaction disable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog compaction disable"
+	headingLevel={3}
+/>
 
 Examples:
 
@@ -50,60 +62,66 @@ npx wrangler r2 bucket catalog compaction disable my-bucket
 # Disable table-level compaction
 npx wrangler r2 bucket catalog compaction disable my-bucket my-namespace my-table
 ```
-<WranglerCommand command="r2 bucket catalog snapshot-expiration enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog snapshot-expiration disable" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog snapshot-expiration enable"
+	headingLevel={3}
+/>
 
-<WranglerCommand command="r2 bucket cors set" headingLevel={3}/>
+<WranglerCommand
+	command="r2 bucket catalog snapshot-expiration disable"
+	headingLevel={3}
+/>
 
-<WranglerCommand command="r2 bucket cors delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket cors list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket cors list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket dev-url get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket dev-url get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain update" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain update" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket domain list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain get" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket domain list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock add" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock remove" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock add" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock remove" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket lock set" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification create" headingLevel={3}/>
+<WranglerCommand command="r2 bucket lock set" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification delete" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification create" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket notification list" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification delete" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy enable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket notification list" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy disable" headingLevel={3}/>
+<WranglerCommand command="r2 bucket sippy enable" headingLevel={3} />
 
-<WranglerCommand command="r2 bucket sippy get" headingLevel={3}/>
+<WranglerCommand command="r2 bucket sippy disable" headingLevel={3} />
 
+<WranglerCommand command="r2 bucket sippy get" headingLevel={3} />
 
 ## `r2 object`
 
@@ -114,8 +132,8 @@ Interact with R2 objects.
 The `r2 object` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 object get" headingLevel={3}/>
+<WranglerCommand command="r2 object get" headingLevel={3} />
 
-<WranglerCommand command="r2 object put" headingLevel={3}/>
+<WranglerCommand command="r2 object put" headingLevel={3} />
 
-<WranglerCommand command="r2 object delete" headingLevel={3}/>
\ No newline at end of file
+<WranglerCommand command="r2 object delete" headingLevel={3} />
diff --git a/src/content/partials/workflows/workflows-type-parameters.mdx b/src/content/partials/workflows/workflows-type-parameters.mdx
index 0ad91e5f88a4fcf..37e0134270468b8 100644
--- a/src/content/partials/workflows/workflows-type-parameters.mdx
+++ b/src/content/partials/workflows/workflows-type-parameters.mdx
@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 :::caution
 
diff --git a/src/content/partials/zaraz/zaraz-definition.mdx b/src/content/partials/zaraz/zaraz-definition.mdx
index b17ee4fa2792f6f..2b5e8f884cd31f7 100644
--- a/src/content/partials/zaraz/zaraz-definition.mdx
+++ b/src/content/partials/zaraz/zaraz-definition.mdx
@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 Cloudflare Zaraz gives you complete control over third-party tools and services for your website, and allows you to offload them to Cloudflare's edge, improving the speed and security of your website. With Cloudflare Zaraz you can load tools such as analytics tools, advertising pixels and scripts, chatbots, marketing automation tools, and more, in the most optimized way.
diff --git a/src/pages/agent-setup/index.astro b/src/pages/agent-setup/index.astro
index 9c6aa0f8bc91720..e5e4a7adc39235c 100644
--- a/src/pages/agent-setup/index.astro
+++ b/src/pages/agent-setup/index.astro
@@ -24,29 +24,59 @@ const props = {
 
 <StarlightPage {...props}>
 	<p class="agent-setup-lede">
-		Install an agent of your choice, connect Cloudflare <a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">Skills &nearr;</a> and <a href="https://blog.cloudflare.com/code-mode-mcp/" target="_blank" rel="noopener noreferrer">Code Mode API &nearr;</a> and <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific &nearr;</a> MCP servers, and start deploying to Cloudflare from your editor or terminal.
+		Install an agent of your choice, connect Cloudflare <a
+			href="https://github.com/cloudflare/skills"
+			target="_blank"
+			rel="noopener noreferrer">Skills &nearr;</a
+		> and <a
+			href="https://blog.cloudflare.com/code-mode-mcp/"
+			target="_blank"
+			rel="noopener noreferrer">Code Mode API &nearr;</a
+		> and <a
+			href="https://github.com/cloudflare/mcp-server-cloudflare"
+			target="_blank"
+			rel="noopener noreferrer">domain-specific &nearr;</a
+		> MCP servers, and start deploying to Cloudflare from your editor or terminal.
 	</p>
 
 	<div class="agent-setup-paths not-content">
 		<!-- Left: quick path -->
-		<div class="agent-setup-path agent-setup-path--quick" style="flex-basis: 60%;">
+		<div
+			class="agent-setup-path agent-setup-path--quick"
+			style="flex-basis: 60%;"
+		>
 			<p class="agent-setup-path-eyebrow">Quick setup</p>
 			<p class="agent-setup-path-title">Already have an agent?</p>
-			<p class="agent-setup-path-desc">Paste this into any AI coding agent to install Cloudflare agent tooling in one step.</p>
-			<PromptCopyBlock text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md" hideLabel />
+			<p class="agent-setup-path-desc">
+				Paste this into any AI coding agent to install Cloudflare agent tooling
+				in one step.
+			</p>
+			<PromptCopyBlock
+				text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md"
+				hideLabel
+			/>
 		</div>
 		<!-- Right: manual path -->
 		<div class="agent-setup-path agent-setup-path--manual">
 			<p class="agent-setup-path-eyebrow">Manual setup</p>
 			<p class="agent-setup-path-title">New to AI agents?</p>
-			<p class="agent-setup-path-desc">Pick an agent, follow step-by-step setup instructions, compare capabilities, and learn about the Cloudflare tools available to you.</p>
-			<a href="#pick-your-agent" class="agent-setup-path-cta">Browse agents &darr;</a>
+			<p class="agent-setup-path-desc">
+				Pick an agent, follow step-by-step setup instructions, compare
+				capabilities, and learn about the Cloudflare tools available to you.
+			</p>
+			<a href="#pick-your-agent" class="agent-setup-path-cta"
+				>Browse agents &darr;</a
+			>
 		</div>
 	</div>
 
 	<hr />
 
-	<div class="agent-setup-section-header" style="margin-top: 3.25rem;" id="pick-your-agent">
+	<div
+		class="agent-setup-section-header"
+		style="margin-top: 3.25rem;"
+		id="pick-your-agent"
+	>
 		<h2>Pick your agent</h2>
 		<p>Select an agent to get step-by-step setup instructions.</p>
 	</div>
@@ -108,10 +138,6 @@ const props = {
 		border-color: var(--color-cl1-gray-2);
 	}
 
-
-
-
-
 	.agent-setup-path-eyebrow {
 		font-size: 0.75rem;
 		font-weight: 700;
@@ -152,5 +178,4 @@ const props = {
 		text-decoration: underline;
 		text-underline-offset: 2px;
 	}
-
 </style>
diff --git a/src/pages/plans.astro b/src/pages/plans.astro
index 38f964ff6dac9d9..e46fb3945ae4d16 100644
--- a/src/pages/plans.astro
+++ b/src/pages/plans.astro
@@ -120,8 +120,8 @@ import { ProductFeatures } from "~/components";
 			<strong>Developer products</strong>: Refer to the <a
 				href="https://www.cloudflare.com/plans/developer-platform/"
 				>Developer Platform pricing page</a
-			> or individual <a href="/directory/">product docs</a> to learn more about
-			plans and pricing.
+			> or individual <a href="/directory/">product docs</a> to learn more about plans
+			and pricing.
 		</li>
 		<li>
 			<strong>Zero Trust products</strong>: Refer to the <a

From cba8e96338feff002c9ac1140a90cecfde6b14bd Mon Sep 17 00:00:00 2001
From: "ask-bonk[bot]" <ask-bonk[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 08:57:54 +0000
Subject: [PATCH 8/8] Reverted bad commit. 5 targeted edits done.

Co-authored-by: korinne <korinne@users.noreply.github.com>
---
 .agents/references/procedures.md              |   20 +-
 .agents/skills/dependabot-review/SKILL.md     |   18 +-
 .agents/skills/docs-review/SKILL.md           |   26 +-
 .agents/skills/eli5/SKILL.md                  |   45 +-
 .../internal-dns/index.eli5.mdx               |    1 -
 .../eli5/references/EXAMPLES_REFERENCE.md     |  517 ++++----
 .../eli5/references/content-type-guide.md     |  105 +-
 .../skills/eli5/references/pattern-library.md |  202 ++-
 .github/review-template.md                    |    3 +-
 .opencode/command/styleguide.md               |    1 -
 .windsurf/rules/general-rules.md              |    2 +-
 CONTRIBUTING.md                               |    3 +-
 MIGRATION.md                                  |    4 +-
 src/components/AutoconfigDiagram.astro        |  157 +--
 src/components/ComponentUsage.astro           |    3 +-
 src/components/FeatureTable.astro             |   44 +-
 src/components/LayerCard.astro                |    8 +-
 src/components/LlmsTxtDirective.astro         |    6 +-
 src/components/PagesBuildPresetsTable.astro   |   15 +-
 src/components/ProductReleaseNotes.astro      |    7 +-
 src/components/R2LocalUploadsdiagram.astro    |  404 ++----
 src/components/WranglerCommand.astro          |    2 +-
 src/components/WranglerConfig.astro           |    4 +-
 src/components/WranglerNamespace.astro        |    2 +-
 .../agent-setup/AgentComparison.astro         |   12 +-
 src/components/agent-setup/AgentHeader.astro  |    4 +-
 src/components/agent-setup/AgentPrimer.astro  |    6 +-
 .../agent-setup/BuildAgentsCallout.astro      |    4 +-
 .../agent-setup/CloudflareToolsBanner.astro   |   35 +-
 .../agent-setup/PlatformAccessSection.astro   |    7 +-
 src/components/ai-gateway/code-examples.astro |  329 ++---
 src/components/changelog/Pagination.astro     |    7 +-
 src/components/models/CopyableCode.astro      |   11 +-
 src/components/models/ModelDetailPage.astro   |  220 +---
 src/components/models/SchemaDisplay.astro     |   16 +-
 src/components/models/code/DeepgramFlux.astro |   15 +-
 .../OpenAIResponsesTextGenerationCode.astro   |    4 +-
 src/components/overrides/Page.astro           |    6 +-
 ...ss-Supports-Customer-Metadata-Boundary.mdx |    4 +-
 .../access/2025-08-26-mcp-server-portals.mdx  |    1 +
 ...-17-clientless-access-for-private-apps.mdx |    4 +-
 .../2025-12-22-agents-sdk-ai-sdk-v6.mdx       |   40 +-
 .../2026-04-15-agentlee-writeops-genui.mdx    |   14 +-
 .../ai-search/2025-09-19-autorag-metrics.mdx  |    2 +-
 .../2025-09-25-ai-search-more-models.mdx      |   31 +-
 ...add-extra-headers-for-website-crawling.mdx |    7 +-
 ...2026-04-16-ai-search-namespace-binding.mdx |    4 +-
 .../2025-10-01-confidence-intervals.mdx       |    8 +-
 .../2026-02-18-cfworker-server-timing.mdx     |    8 +-
 .../2026-03-09-vulnerability-scanner.mdx      |    4 +-
 .../2026-05-19-event-subscriptions.mdx        |   10 +-
 .../2024-09-05-cache-rules-templates.mdx      |    1 +
 .../2024-11-07-shard-cache-by-cache-key.mdx   |   16 +-
 ...-11-07-cache-keys-for-cloudflare-trace.mdx |   26 +-
 ...1-25-audit-logs-for-cache-purge-events.mdx |   44 +-
 .../cache/2026-03-24-cache-response-rules.mdx |    2 +-
 .../changelog/casb/2025-10-28-casb-roles.mdx  |    4 +-
 .../2025-08-29-warp-AI-diag-analyzer.mdx      |    1 +
 ...nabled-search-for-zero-trust-dashboard.mdx |    4 +-
 ...for-supported-cloudflare-one-resources.mdx |   10 +-
 .../cloudflare-one/new-applications-71825.mdx |    2 +-
 ...-01-27-configure-cloudflare-source-ips.mdx |    2 +-
 ...025-10-01-new-container-instance-types.mdx |    2 +-
 .../containers/2025-11-21-new-cpu-pricing.mdx |    6 +-
 ...02-25-higher-container-resource-limits.mdx |    2 +-
 .../2026-03-24-docker-hub-images.mdx          |    2 +-
 .../2026-04-05-regional-placement.mdx         |    8 +-
 ...4-13-sandbox-outbound-workers-tls-auth.mdx |    2 +-
 .../2026-05-12-ssh-enabled-by-default.mdx     |    2 +-
 .../dex/2025-11-12-dex-logpush-jobs.mdx       |    4 +-
 .../dex/2026-02-19-dex-supports-cmb-eu.mdx    |    1 +
 ...04-28-dex-internet-outage-notification.mdx |    2 +-
 .../dex/2026-04-28-dex-speed-test.mdx         |    3 +-
 .../dex/2026-04-29-dex-tests-to-auth.mdx      |    3 +-
 .../2025-04-14-account-level-dlp-settings.mdx |    1 -
 .../dlp/2025-07-17-document-matching.mdx      |    5 +-
 .../dlp/2025-08-25-ai-prompt-protection.mdx   |   12 +-
 ...25-har-file-detection-and-sanitization.mdx |    2 +-
 ...-04-14-cloudflare-api-token-detections.mdx |   16 +-
 .../dlp/2026-04-28-pii-record-profile.mdx     |    2 +-
 .../dns/2026-03-31-internal-dns-open-beta.mdx |    1 -
 .../dns/2026-04-28-enforce-dns-only.mdx       |    1 -
 ...2025-08-21-durable-objects-get-by-name.mdx |    8 +-
 ...2025-10-16-durable-objects-data-studio.mdx |    2 +-
 ...durable-objects-sqlite-storage-billing.mdx |    3 +-
 .../2026-03-15-durable-object-id-name.mdx     |   18 +-
 .../2025-07-21-subaddressing.mdx              |    2 +-
 .../2024-12-19-escalate-user-submissions.mdx  |    2 +-
 .../2025-10-16-on-demand-security-report.mdx  |    1 +
 ...adjustment-to-final-disposition-column.mdx |    3 +-
 ...25-12-03-submission-terminology-update.mdx |   11 +-
 ...anced-visibility-post-delivery-actions.mdx |    9 +-
 ...ed-accessibility-search-for-monitoring.mdx |   26 +-
 ...6-03-15-infinite-paging-investigations.mdx |   12 +-
 ...2026-04-06-dane-support-mx-deployments.mdx |   12 +-
 .../2026-04-07-triage-status-tracking.mdx     |    2 -
 ...5-06-cloudy-summaries-in-phishnet_o365.mdx |    1 -
 .../2025-06-23-user-groups-ga.mdx             |    4 +-
 .../2025-09-03-rate-limiting-improvement.mdx  |   21 +-
 ...two-factor-authentication-backup-codes.mdx |    3 +-
 .../2025-09-25-sign-in-with-github.mdx        |    3 +-
 .../fundamentals/2025-10-01-md-returned.mdx   |    2 +-
 .../2025-10-14-sso-self-service-ux.mdx        |    1 +
 .../fundamentals/2025-10-30-email-2FA.mdx     |    6 +-
 ...5-10-30-member-management-improvements.mdx |   14 +-
 .../2026-01-23-New-2FA-Experience.mdx         |    9 +-
 .../2026-02-12-markdown-for-agents.mdx        |    3 +-
 ...02-16-markdown-for-agents-improvements.mdx |    2 +-
 ...json-rfc9457-responses-for-1xxx-errors.mdx |    1 -
 ...-12-retry-after-header-for-1xxx-errors.mdx |   19 +-
 .../2026-03-17-scim-authentik-support.mdx     |    2 +-
 .../2026-03-18-scim-audit-logging.mdx         |    4 +-
 .../2026-04-06-organizations-public-beta.mdx  |    2 +-
 .../2026-04-10-secret-scanning-support.mdx    |    2 +-
 .../2026-04-14-oauth-consent-and-revoke.mdx   |   22 +-
 ...27-structured-responses-for-5xx-errors.mdx |    1 -
 .../2026-05-04-keyboard-shortcuts.mdx         |   54 +-
 ...025-07-24-HTTP-Inspection-on-all-ports.mdx |    4 +-
 ...-07-28-Spam-domain-category-introduced.mdx |   12 +-
 ...08-15-gemini-application-replaces-bard.mdx |    3 +-
 .../2025-10-10-new-domain-categories.mdx      |   10 +-
 ...-11-06-Applications-recategorised-plan.mdx |    6 +-
 ...02-27-new-protocol-detection-protocols.mdx |   14 +-
 .../Gateway-application-categories-added.mdx  |    4 +-
 ...4-hyperdrive-remote-database-local-dev.mdx |   14 +-
 src/content/changelog/images/heic-support.mdx |    1 -
 ...2025-08-22-kv-performance-improvements.mdx |    2 +
 .../2025-06-04-account-load-balancing-ui.mdx  |    3 +-
 .../2025-07-09-usage-tracking.mdx             |    2 +-
 .../2025-08-15-extended-retention.mdx         |    2 +-
 .../2025-09-03-log-headers-and-cookies.mdx    |    2 +
 .../2025-09-11-contextual-pivots.mdx          |    4 +-
 .../2025-09-11-new-results-table-view.mdx     |    4 +-
 .../2025-11-04-query-cancellation.mdx         |    2 +-
 .../2025-11-11-resize-sql-window.mdx          |    2 +-
 .../2025-11-13-fixed-custom-date.mdx          |    2 +-
 .../log-explorer/2025-11-13-new-datasets.mdx  |    5 +-
 .../2026-03-11-ingest-field-selection.mdx     |   20 +-
 .../logs/2024-10-08-new-gateway-fields.mdx    |    2 +-
 .../logs/2026-03-09-log-fields-updated.mdx    |    1 +
 ...26-04-20-pipelines-logpush-destination.mdx |    2 +-
 ...2026-04-21-logpush-subrequests-merging.mdx |    4 +-
 ...-03-24-interconnects-navigation-update.mdx |    2 +-
 .../pages/2025-05-30-pages-build-image-v3.mdx |    2 +-
 .../queues/2025-03-25-pause-purge-queues.mdx  |    8 +-
 .../2025-04-17-pull-consumer-limits.mdx       |    3 -
 .../2025-05-09-publish-to-queues-via-http.mdx |    2 +-
 .../queues/2025-08-19-event-subscriptions.mdx |   26 +-
 ...2025-09-25-announcing-r2-sql-open-beta.mdx |    2 +-
 ...ql-functions-expressions-complex-types.mdx |    1 +
 ...0-r2-sql-json-functions-explain-format.mdx |    2 -
 .../radar/2025-08-04-radar-ct-insights.mdx    |    2 +-
 .../radar/2025-09-29-radar-regional-data.mdx  |    2 +-
 .../radar/2026-02-25-radar-aspa-insights.mdx  |    2 +-
 .../2026-04-01-radar-routing-section.mdx      |    2 +-
 ...2026-05-28-realtimekit-track-recording.mdx |    2 +-
 .../2026-1-15-crowdstrike-score.mdx           |    1 -
 .../2025-10-30-tcp-rtt-and-tcp-fields.mdx     |    8 +-
 .../rules/2026-01-12-dma-metro-code-field.mdx |    4 +-
 .../rules/2026-01-20-array-map-functions.mdx  |   12 +-
 .../2026-01-27-body-buffering-settings.mdx    |   26 +-
 .../rules/2026-03-18-worker-timing-field.mdx  |    4 +-
 .../rules/2026-03-25-rfc9440-mtls-fields.mdx  |    2 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   12 +-
 ...20-cloudflare-typescript-v6.0.0-beta.1.mdx |   70 +-
 ...-02-13-cloudflare-python-v5.0.0-beta.1.mdx |   13 +-
 .../2025-07-18-brand-protection-api.mdx       |   14 +-
 .../2025-10-27-RFI-Tokens-in-Dash.mdx         |    2 +-
 ...protection-logo-dashboard-report-abuse.mdx |    4 +-
 ...Threat-Events-now-show-events-insights.mdx |    6 +-
 ...-01-14-Download-URL-Scanner-Report-PDF.mdx |    8 +-
 .../2026-02-19-threat-events-graphs.mdx       |    1 -
 ...026-02-23-Saved-views-in-threat-events.mdx |    5 +-
 .../2026-04-08-threat-events-notification.mdx |   20 +-
 .../2026-05-07-CSV-export-for-RFIs.mdx        |    1 -
 ...-12-URL-scanner-report-agent-readiness.mdx |   17 +-
 ...archive-and-audit-security-action-items.md |    5 +-
 .../2025-08-25-secrets-store-ai-gateway.mdx   |   20 +-
 ...07-22-media-transformations-audio-mode.mdx |    2 +-
 .../2026-04-06-redesigned-support-portal.mdx  |    1 -
 .../2026-04-28-direct-support-navigation.mdx  |    4 +-
 .../2025-02-03-terraform-v5-provider.mdx      |    6 +-
 .../2025-05-19-terraform-v5.5.0-provider.mdx  |   13 +-
 .../2025-06-17-terraform-v5.6.0-provider.mdx  |    3 +-
 .../2025-07-11-terraform-v5.7.0-provider.mdx  |    3 +-
 .../2025-08-01-terraform-v5.8.2-provider.mdx  |    6 +-
 .../2025-08-15-terraform-v5.8.4-provider.mdx  |    6 +-
 .../2025-08-29-terrform-v5.9-provider.mdx     |    3 +-
 .../2025-11-20-terraform-v5.13.0-provider.mdx |   63 +-
 .../2025-12-05-terraform-v5.14.0-provider.mdx |   22 +-
 .../2025-12-19-terraform-v5.15.0-provider.mdx |   36 +-
 .../2026-01-20-terraform-v5.16.0-provider.mdx |   55 +-
 .../2026-02-12-terraform-v5.17.0-provider.mdx |   91 +-
 .../2026-04-24-terraform-v5.19.0-provider.mdx |    1 -
 .../2026-04-24-tf-migrate-tool-released.mdx   |    6 +-
 .../tunnel/2025-07-15-udp-improvements.mdx    |    3 +-
 ...el-networks-list-endpoints-new-default.mdx |   28 +-
 .../2025-09-18-tunnel-hostname-routing.mdx    |    3 +-
 ...2026-01-15-warp-connector-ping-support.mdx |    2 +-
 .../changelog/waf/2025-07-14-waf-release.mdx  |    1 +
 .../changelog/waf/2025-07-21-emergency.mdx    |   30 +-
 .../changelog/waf/2025-07-28-waf-release.mdx  |   11 +-
 .../changelog/waf/2025-08-04-waf-release.mdx  |  207 ++-
 .../waf/2025-08-07-emergency-waf-release.mdx  |   75 +-
 .../changelog/waf/2025-08-11-waf-release.mdx  |  460 +++----
 .../changelog/waf/2025-08-18-waf-release.mdx  |  275 ++--
 .../changelog/waf/2025-08-25-waf-release.mdx  |   98 +-
 .../waf/2025-08-29-emergency-waf-release.mdx  |   72 +-
 .../changelog/waf/2025-09-01-waf-release.mdx  |   78 +-
 .../waf/2025-09-04-emergency-waf-release.mdx  |   95 +-
 .../changelog/waf/2025-09-08-waf-release.mdx  |  250 ++--
 .../changelog/waf/2025-09-15-waf-release.mdx  |  100 +-
 .../changelog/waf/2025-09-22-waf-release.mdx  |  221 ++--
 .../waf/2025-09-24-emergency-waf-release.mdx  |   52 +-
 .../changelog/waf/2025-09-26-waf-release.mdx  |  268 ++--
 .../waf/2025-09-28-emergency-waf-release.mdx  |   80 +-
 .../changelog/waf/2025-09-29-waf-release.mdx  |  135 +-
 .../changelog/waf/2025-10-03-waf-release.mdx  |  488 +++----
 .../changelog/waf/2025-10-06-waf-release.mdx  |  220 ++--
 .../waf/2025-10-07-emergency-waf-release.mdx  |   55 +-
 .../waf/2025-10-17-emergency-waf-release.mdx  |   82 +-
 .../changelog/waf/2025-10-20-waf-release.mdx  |   16 +-
 .../waf/2025-10-23-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-24-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-10-30-emergency-waf-release.mdx  |   48 +-
 .../waf/2025-11-05-emergency-waf-release.mdx  |   50 +-
 .../changelog/waf/2025-11-10-waf-release.mdx  |    4 +-
 .../changelog/waf/2025-11-17-waf-release.mdx  |    2 +-
 .../waf/2025-11-21-emergency-waf-release.mdx  |    2 +-
 .../changelog/waf/2025-11-24-waf-release.mdx  |   16 +-
 .../changelog/waf/2025-12-01-waf-release.mdx  |    9 +-
 .../waf/2025-12-02-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-03-emergency-waf-release.mdx  |    3 +-
 .../waf/2025-12-10-emergency-waf-release.mdx  |    2 +-
 .../waf/2025-12-11-emergency-waf-release.mdx  |   14 +-
 .../changelog/waf/2025-12-18-waf-release.mdx  |  225 ++--
 .../changelog/waf/2026-01-12-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-15-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-20-waf-release.mdx  |   57 +-
 .../changelog/waf/2026-01-26-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-02-02-waf-release.mdx  |   70 +-
 .../changelog/waf/2026-03-02-waf-release.mdx  |    7 +-
 .../waf/2026-03-12-emergency-waf-release.mdx  |    6 +-
 .../changelog/waf/2026-03-23-waf-release.mdx  |  104 +-
 .../changelog/waf/2026-03-30-waf-release.mdx  |  116 +-
 .../changelog/waf/2026-04-15-waf-release.mdx  |  144 +--
 .../changelog/waf/2026-04-21-waf-release.mdx  |  339 ++---
 .../changelog/waf/2026-04-27-waf-release.mdx  |  343 +++--
 .../waf/2026-05-07-emergency-waf-release.mdx  |   12 +-
 .../changelog/waf/2026-05-11-waf-release.mdx  |    9 +-
 .../waf/2026-05-15-emergency-waf-release.mdx  |   16 +-
 .../changelog/waf/2026-05-20-waf-release.mdx  |   12 +-
 .../2026-04-30-rum-navigation-types.mdx       |    4 +-
 .../2025-08-05-openai-open-models.mdx         |    5 +-
 .../workers-ai/2025-08-27-partner-models.mdx  |    3 +-
 .../workers-ai/2025-09-05-embeddinggemma.mdx  |    3 +-
 .../workers-vpc/2025-09-25-workers-vpc.mdx    |    4 +-
 ...-07-new-ways-to-get-started-on-workers.mdx |   12 +-
 .../workers/2025-03-25-higher-cpu-limits.mdx  |    2 +-
 ...2025-04-08-deploy-to-cloudflare-button.mdx |   18 +-
 .../workers/2025-04-09-qb-workers-logs-ga.mdx |    4 +-
 ...2025-04-22-python-worker-cron-triggers.mdx |    2 +-
 ...025-05-14-python-worker-durable-object.mdx |    2 +-
 .../workers/2025-06-05-open-next-size.mdx     |    2 +-
 .../2025-07-23-workers-preview-urls.mdx       |   12 +-
 .../2025-08-04-builds-increased-disk-size.mdx |    8 +-
 ...08-08-add-waituntil-cloudflare-workers.mdx |    2 +-
 ...port-long-branch-names-preview-aliases.mdx |    4 +-
 .../workers/2025-08-11-messagechannel.mdx     |   16 +-
 .../2025-08-14-new-python-handlers.mdx        |    2 +-
 ...workers-terraform-and-sdk-improvements.mdx |   39 +-
 .../2025-08-15-static-assets-redirect-url.mdx |    6 +-
 ...5-08-19-improved-wrangler-error-screen.mdx |    4 +-
 .../workers/2025-09-03-new-workers-api.mdx    |   86 +-
 .../2025-09-07-builds-increased-cpu-paid.mdx  |   17 +-
 ...2025-09-09-interactive-wrangler-assets.mdx |    5 +-
 ...025-09-10-built-with-cloudflare-button.mdx |    2 +-
 ...09-11-increased-version-rollback-limit.mdx |    9 +-
 .../2025-09-17-update-preview-url-setting.mdx |    6 +-
 .../2025-09-19-ratelimit-workers-ga.mdx       |    4 +-
 ...dev-multi-config-cross-command-support.mdx |   19 +-
 ...9-26-analytics-engine-sql-enhancements.mdx |   21 +-
 .../workers/2025-09-26-ctx-exports.md         |   16 +-
 .../workers/2025-10-09-assets-terraform.mdx   |   10 +-
 .../2025-10-09-workflows-terraform.mdx        |    8 +-
 ...025-10-23-preview-url-default-behavior.mdx |    7 +-
 ...-10-24-automatic-resource-provisioning.mdx |    2 +-
 .../workers/2025-10-30-builds-preview.mdx     |    8 +-
 .../2025-11-09-cloudflare-env-variable.mdx    |    1 -
 ...lytics-engine-further-sql-enhancements.mdx |   12 +-
 ...25-12-01-build-image-policies-dev-plat.mdx |    2 +-
 ...5-12-08-python-cold-start-improvements.mdx |   10 +-
 .../workers/2025-12-08-python-pywrangler.mdx  |    1 +
 .../2025-12-08-vite-optional-config.mdx       |    2 +-
 .../2025-12-08-vite-programmatic-config.mdx   |    2 +-
 .../2025-12-16-vitest-ctx-exports-support.mdx |   10 +-
 ...2025-12-19-tanstack-start-prerendering.mdx |   20 +-
 .../2026-02-15-workers-best-practices.mdx     |    1 -
 .../2026-03-27-rfc9440-mtls-fields.mdx        |   45 +-
 ...26-04-01-l4-transport-telemetry-fields.mdx |   34 +-
 ...026-05-06-react-nextjs-vulnerabilities.mdx |    2 +-
 .../2025-01-15-workflows-more-steps.mdx       |    6 +-
 .../workflows/2025-10-28-raising-limits.mdx   |    6 +-
 .../2026-03-23-local-dev-instance-methods.mdx |    2 +-
 .../2026-05-01-dynamic-workflows.mdx          |    6 +-
 .../compatibility-flags/allow-custom-ports.md |    1 -
 .../enable-nodejs-http-modules.md             |    8 +-
 .../enable-nodejs-http-server-modules.md      |    8 +-
 .../fetcher-no-get-put-delete.md              |    1 +
 .../compatibility-flags/js-weak-refs.md       |    3 +-
 .../new-url-parser-implementation.md          |    8 +-
 .../compatibility-flags/nodejs-compat.md      |   12 +-
 .../queue-consumer-no-wait-waituntil.md       |   29 +-
 .../queues-json-messages.md                   |    2 +-
 .../compatibility-flags/request-signal.md     |    2 +-
 .../streams-byob-reader-detaches-buffer.md    |   12 +-
 .../compatibility-flags/strict-crypto.md      |    1 -
 .../throw-on-unrecognized-import-assertion.md |    1 +
 .../compatibility-flags/to-string-tag.md      |    2 +-
 .../urlsearchparams-deletehasvalue.md         |    6 +-
 .../web-socket-auto-reply-to-close.md         |   38 +-
 .../web-socket-compression.md                 |    2 +-
 .../websocket-standard-binary-type.md         |    4 +-
 ...ws-preserve-non-retryable-error-message.md |   14 +-
 .../mpp/charge-for-http-content.mdx           |   10 +-
 .../agents/agentic-payments/x402/index.mdx    |    4 +-
 .../ai-crawl-control-with-bots.mdx            |    2 +-
 .../ai-crawl-control-with-waf.mdx             |   10 +-
 .../features/analyze-ai-traffic.mdx           |   22 +-
 .../features/manage-ai-crawlers.mdx           |   24 +-
 .../set-up-cloudflare-account.mdx             |    2 +-
 .../features/track-robots-txt.mdx             |   10 +-
 .../reference/redirects-for-ai-training.mdx   |   16 +-
 .../configuration/authentication.mdx          |    2 +-
 .../configuration/custom-providers.mdx        |   69 +-
 .../evaluations/add-human-feedback.mdx        |    1 -
 .../docs/ai-gateway/features/dlp/index.mdx    |   10 +-
 .../features/dynamic-routing/usage.mdx        |    3 +-
 .../integrations/aig-workers-ai-binding.mdx   |    2 +-
 src/content/docs/ai-gateway/mcp-server.mdx    |    2 +-
 .../observability/logging/index.mdx           |    6 +-
 .../docs/ai-gateway/reference/audit-logs.mdx  |   71 +-
 .../docs/ai-gateway/reference/limits.mdx      |   13 +-
 .../ai-gateway/tutorials/pruna-p-video.mdx    |   14 +-
 .../docs/ai-gateway/usage/chat-completion.mdx |    6 +-
 .../ai-gateway/usage/providers/anthropic.mdx  |   17 +-
 .../usage/providers/azureopenai.mdx           |   12 +-
 .../ai-gateway/usage/providers/baseten.mdx    |   40 +-
 .../ai-gateway/usage/providers/bedrock.mdx    |   10 +-
 .../docs/ai-gateway/usage/providers/fal.mdx   |   26 +-
 .../usage/providers/google-ai-studio.mdx      |   15 +-
 .../ai-gateway/usage/providers/ideogram.mdx   |   20 +-
 .../docs/ai-gateway/usage/rest-api.mdx        |   70 +-
 .../usage/websockets-api/non-realtime-api.mdx |    2 +-
 .../usage/websockets-api/realtime-api.mdx     |    2 +-
 .../docs/ai-search/api/instances/rest-api.mdx |    4 +-
 .../docs/ai-search/api/items/rest-api.mdx     |    4 +-
 .../ai-search/configuration/models/index.mdx  |    2 +
 src/content/docs/ai-search/how-to/nlweb.mdx   |   34 +-
 .../docs/ai-search/wrangler-commands.mdx      |    2 +-
 .../docs/ai/related-products/ai-gateway.mdx   |    2 +-
 .../account-analytics.mdx                     |   28 +-
 .../analytics-with-workers.mdx                |   10 +-
 .../account-and-zone-analytics/index.mdx      |    2 +-
 .../analytics/analytics-engine/grafana.mdx    |   12 +-
 .../docs/analytics/analytics-engine/index.mdx |   14 +-
 .../analytics/analytics-engine/limits.mdx     |    8 +-
 .../analytics/analytics-engine/pricing.mdx    |    2 +-
 .../analytics-engine/recipes/index.mdx        |    2 +-
 .../analytics/analytics-engine/sampling.mdx   |   62 +-
 .../analytics/analytics-engine/sql-api.mdx    |   10 +-
 .../sql-reference/aggregate-functions.mdx     |    2 +-
 .../sql-reference/bit-functions.mdx           |    2 +-
 .../sql-reference/date-time-functions.mdx     |    2 +-
 .../sql-reference/encoding-functions.mdx      |    2 +-
 .../analytics-engine/sql-reference/index.mdx  |    2 +-
 .../sql-reference/mathematical-functions.mdx  |    2 +-
 .../sql-reference/string-functions.mdx        |    2 +-
 .../type-conversion-functions.mdx             |    2 +-
 .../analytics-engine/worker-querying.mdx      |    1 +
 .../analytics-integrations/datadog.mdx        |    1 +
 .../analytics-integrations/index.mdx          |    2 +-
 .../analytics-integrations/prometheus.mdx     |   75 +-
 .../docs/analytics/custom-dashboards.mdx      |   38 +-
 .../docs/analytics/faq/about-analytics.mdx    |   16 +-
 src/content/docs/analytics/faq/index.mdx      |    2 +-
 src/content/docs/analytics/faq/other-faqs.mdx |   12 +-
 src/content/docs/analytics/faq/wae-faqs.mdx   |    9 +-
 .../docs/analytics/graphql-api/errors.mdx     |   64 +-
 .../features/confidence-intervals.mdx         |  102 +-
 .../graphql-api/features/discovery/index.mdx  |    1 +
 .../analytics/graphql-api/features/index.mdx  |    2 +-
 .../authentication/graphql-client-headers.mdx |    6 +-
 .../getting-started/authentication/index.mdx  |   52 +-
 .../getting-started/compose-graphql-query.mdx |   15 +
 .../getting-started/execute-graphql-query.mdx |    4 +-
 .../explore-graphql-schema.mdx                |   17 +-
 .../graphql-api/getting-started/index.mdx     |   20 +-
 .../docs/analytics/graphql-api/limits.mdx     |   18 +-
 .../docs/analytics/graphql-api/mcp-server.mdx |    2 +-
 .../graphql-api/migration-guides/index.mdx    |    4 +-
 .../network-analytics-v2/schema-map.mdx       |    1 +
 .../docs/analytics/graphql-api/sampling.mdx   |    4 +
 .../tutorials/end-customer-analytics.mdx      |  218 ++--
 .../analytics/graphql-api/tutorials/index.mdx |    2 +-
 .../querying-access-login-events.mdx          |   72 +-
 .../tutorials/querying-email-routing.mdx      |  352 ++---
 ...c-transit-endpoint-healthcheck-results.mdx |    5 +-
 ...gic-transit-tunnel-bandwidth-analytics.mdx |    8 +-
 ...gic-transit-tunnel-healthcheck-results.mdx |    5 +-
 src/content/docs/analytics/index.mdx          |   36 +-
 .../network-analytics/configure/index.mdx     |    2 +-
 .../configure/share-export.mdx                |    2 +-
 .../configure/time-range.mdx                  |    2 +-
 .../analytics/network-analytics/index.mdx     |   12 +-
 .../network-analytics/reference/index.mdx     |    2 +-
 .../network-analytics/understand/index.mdx    |    2 +-
 src/content/docs/analytics/sampling.mdx       |   23 +-
 .../docs/analytics/types-of-analytics.mdx     |   27 +-
 src/content/docs/api-shield/api-gateway.mdx   |    1 +
 src/content/docs/api-shield/glossary.mdx      |    3 +-
 src/content/docs/api-shield/index.mdx         |   30 +-
 .../management-and-monitoring/index.mdx       |    5 +-
 .../session-identifiers.mdx                   |    4 +-
 src/content/docs/api-shield/plans.mdx         |   15 +-
 .../reference/classic-schema-validation.mdx   |   14 +-
 .../docs/api-shield/reference/index.mdx       |    5 +-
 .../docs/api-shield/reference/terraform.mdx   |   11 +-
 .../security/graphql-protection/index.mdx     |    1 +
 .../docs/api-shield/security/index.mdx        |   45 +-
 .../security/jwt-validation/jwt-worker.mdx    |    2 +-
 .../jwt-validation/transform-rules.mdx        |    4 +-
 .../docs/api-shield/security/mtls/byo-ca.mdx  |    1 +
 .../docs/api-shield/security/mtls/index.mdx   |    1 +
 .../security/sequence-analytics.mdx           |    3 +-
 .../security/sequence-mitigation/api.mdx      |   23 +-
 .../sequence-mitigation/custom-rules.mdx      |   21 +-
 .../security/sequence-mitigation/index.mdx    |    8 +-
 .../security/volumetric-abuse-detection.mdx   |   11 +-
 .../docs/argo-smart-routing/analytics.mdx     |    9 +-
 .../argo-smart-routing/argo-for-packets.mdx   |    1 +
 src/content/docs/artifacts/api/errors.mdx     |   28 +-
 .../docs/artifacts/api/git-protocol.mdx       |    6 +-
 .../docs/artifacts/concepts/repositories.mdx  |   10 +-
 .../docs/artifacts/examples/git-client.mdx    |    5 +-
 .../docs/artifacts/guides/authentication.mdx  |   18 +-
 .../artifacts/guides/event-subscriptions.mdx  |    1 -
 .../docs/artifacts/platform/limits.mdx        |    4 +-
 .../docs/artifacts/platform/pricing.mdx       |    8 +-
 .../about/index.mdx                           |    1 +
 .../about/plugin-compatibility.mdx            |   50 +-
 .../about/test-current-speed.mdx              |    1 +
 .../get-started/change-nameservers.mdx        |    2 +
 .../get-started/index.mdx                     |    3 +-
 .../reference/cache-device-type.mdx           |    8 +-
 .../reference/index.mdx                       |    3 +-
 .../reference/page-rule-integration.mdx       |   17 +-
 .../reference/query-parameters.mdx            |   80 +-
 .../reference/subdomain-subdirectories.mdx    |    6 +-
 .../troubleshooting/index.mdx                 |   15 +-
 .../get-started/create-billing-profile.mdx    |    4 +-
 .../get-started/update-billing-info.mdx       |   22 +-
 .../docs/billing/manage/billable-usage.mdx    |   15 +-
 .../docs/billing/manage/budget-alerts.mdx     |   22 +-
 .../billing/manage/cancel-subscription.mdx    |    6 +-
 src/content/docs/billing/manage/invoices.mdx  |   26 +-
 .../docs/billing/manage/optimize-costs.mdx    |   48 +-
 .../manage/pay-invoices-overdue-balances.mdx  |    7 +-
 .../instant-bank-payments-link.mdx            |    6 +-
 .../docs/billing/threshold-billing.mdx        |    8 +-
 .../billing/troubleshoot/error-reference.mdx  |   24 +-
 .../resolve-cannot-remove-payment-method.mdx  |   37 +-
 ...ve-you-cannot-modify-this-subscription.mdx |   12 +-
 .../troubleshoot/troubleshoot-invoices.mdx    |    2 +-
 .../understand/billing-permissions.mdx        |   26 +-
 .../billing/understand/billing-policy.mdx     |   18 +-
 .../billing/understand/how-charges-accrue.mdx |   72 +-
 .../billing/understand/preview-services.mdx   |    2 +-
 .../understand/usage-based-billing.mdx        |   36 +-
 .../docs/bots/account-abuse-protection.mdx    |   75 +-
 .../block-ai-bots.mdx                         |    4 +-
 .../custom-rules.mdx                          |   22 +-
 .../detection-ids/additional-detections.mdx   |    7 +-
 .../bots/additional-configurations/index.mdx  |    5 +-
 .../ja3-ja4-fingerprint/index.mdx             |   81 +-
 .../signals-intelligence.mdx                  |    2 +-
 .../javascript-detections.mdx                 |    2 +-
 src/content/docs/bots/concepts/bot-tags.mdx   |    3 +-
 src/content/docs/bots/concepts/bot/index.mdx  |    2 +-
 .../bots/concepts/bot/signed-agents/index.mdx |    3 +-
 .../concepts/bot/signed-agents/policy.mdx     |    7 +-
 .../concepts/bot/verified-bots/policy.mdx     |    7 +-
 src/content/docs/bots/concepts/index.mdx      |    3 +-
 src/content/docs/bots/get-started/index.mdx   |    3 +-
 src/content/docs/bots/glossary.mdx            |    3 +-
 .../docs/bots/plans/bm-subscription.mdx       |   22 +-
 src/content/docs/bots/reference/alerts.mdx    |    9 +-
 .../reference/bot-management-variables.mdx    |   12 +-
 .../bots/reference/bot-verification/index.mdx |    5 +-
 .../bot-verification/ip-validation.mdx        |    9 +-
 src/content/docs/bots/reference/index.mdx     |    3 +-
 .../reference/machine-learning-models.mdx     |    5 +-
 .../docs/bots/reference/sample-terms.mdx      |    6 +-
 .../troubleshooting/bot-management-skips.mdx  |    3 +-
 .../bots/troubleshooting/false-positives.mdx  |    3 +-
 .../docs/bots/troubleshooting/index.mdx       |    4 +-
 .../docs/bots/workers-templates/index.mdx     |    3 +-
 .../docs/browser-run/features/index.mdx       |    2 +-
 .../docs/browser-run/how-to/deploy-worker.mdx |    2 +-
 src/content/docs/browser-run/mcp-server.mdx   |    2 +-
 .../quick-actions/api-reference.mdx           |    2 +-
 .../reference/browser-close-reasons.mdx       |   54 +-
 src/content/docs/byoip/address-maps/setup.mdx |   26 +-
 src/content/docs/byoip/changelog.mdx          |    2 +-
 src/content/docs/byoip/concepts/index.mdx     |    2 +-
 .../byoip/concepts/prefix-delegations.mdx     |    1 +
 src/content/docs/byoip/glossary.mdx           |    2 +-
 .../docs/byoip/route-leak-detection.mdx       |    3 +-
 .../docs/byoip/service-bindings/index.mdx     |    3 +-
 .../docs/byoip/troubleshooting/index.mdx      |    9 +-
 .../advanced-configuration/cache-reserve.mdx  |    9 +-
 .../advanced-configuration/crawler-hints.mdx  |    9 +-
 .../advanced-configuration/early-hints.mdx    |   21 +-
 .../cache/advanced-configuration/index.mdx    |    3 +-
 .../query-string-sort.mdx                     |   32 +-
 .../serve-tailored-content.mdx                |  158 +--
 .../vary-for-images.mdx                       |   74 +-
 .../cache-security/avoid-web-poisoning.mdx    |   18 +-
 .../cache-security/cache-deception-armor.mdx  |    6 +-
 .../docs/cache/cache-security/cors.mdx        |   11 +-
 .../docs/cache/cache-security/index.mdx       |    3 +-
 .../docs/cache/concepts/cache-behavior.mdx    |   10 +-
 .../docs/cache/concepts/cache-responses.mdx   |    9 +-
 .../docs/cache/concepts/cdn-cache-control.mdx |  178 +--
 .../docs/cache/concepts/customize-cache.mdx   |   13 +-
 .../cache/concepts/default-cache-behavior.mdx |   44 +-
 src/content/docs/cache/concepts/index.mdx     |    3 +-
 .../cache/concepts/retention-vs-freshness.mdx |    5 +-
 .../docs/cache/concepts/revalidation.mdx      |    1 +
 src/content/docs/cache/get-started.mdx        |   58 +-
 src/content/docs/cache/glossary.mdx           |    3 +-
 .../docs/cache/how-to/always-online.mdx       |    5 +-
 src/content/docs/cache/how-to/cache-keys.mdx  |   72 +-
 .../cache-response-rules/create-dashboard.mdx |    4 +-
 .../how-to/cache-rules/examples/index.mdx     |    4 +-
 .../docs/cache/how-to/cache-rules/order.mdx   |    3 +-
 .../cache-rules/page-rules-migration.mdx      |    4 +-
 .../how-to/configure-cache-status-code.mdx    |   14 +-
 .../how-to/edge-browser-cache-ttl/index.mdx   |   14 +-
 .../set-browser-ttl.mdx                       |    7 +-
 src/content/docs/cache/how-to/index.mdx       |    3 +-
 .../how-to/purge-cache/purge-by-hostname.mdx  |    9 +-
 .../purge-cache/purge-by-single-file.mdx      |    2 +-
 .../how-to/purge-cache/purge-by-tags.mdx      |   26 +-
 .../how-to/purge-cache/purge-cache-key.mdx    |   72 +-
 .../how-to/purge-cache/purge-everything.mdx   |    3 +-
 .../purge-cache/purge-varied-images.mdx       |    1 +
 .../purge-cache/purge-zone-versions.mdx       |   81 +-
 .../how-to/purge-cache/purge_by_prefix.mdx    |   39 +-
 .../docs/cache/how-to/set-caching-levels.mdx  |    9 +-
 .../interaction-cloudflare-products/index.mdx |    5 +-
 .../interaction-cloudflare-products/r2.mdx    |    1 +
 .../waf-snippets.mdx                          |    2 +-
 .../workers-cache-rules.mdx                   |    9 +-
 .../workers.mdx                               |    3 +-
 .../performance-review/cache-analytics.mdx    |    5 +-
 .../performance-review/cache-performance.mdx  |    5 +-
 .../docs/cache/performance-review/index.mdx   |    3 +-
 src/content/docs/cache/plans.mdx              |    5 +-
 .../reference/cdn-reference-architecture.mdx  |    1 +
 .../docs/cache/reference/development-mode.mdx |    5 +-
 src/content/docs/cache/reference/index.mdx    |    3 +-
 .../cache/troubleshooting/always-online.mdx   |    3 +
 .../docs/cache/troubleshooting/index.mdx      |    3 +-
 .../concepts/global-acceleration.mdx          |   14 +-
 .../reference/available-products.mdx          |    2 +-
 .../client-ip-geolocation/about/index.mdx     |    4 +-
 .../docs/client-ip-geolocation/faq/index.mdx  |    2 +
 .../client-ip-geolocation/get-started.mdx     |   16 +-
 .../docs/client-ip-geolocation/index.mdx      |   14 +-
 .../additional-configuration.mdx              |    2 +-
 .../challenge-pages/detect-response.mdx       |    2 +-
 .../challenge-types/challenge-pages/index.mdx |    2 +-
 .../challenge-pages/resolve-challenge.mdx     |    2 +-
 .../challenge-types/index.mdx                 |    6 +-
 .../challenge-types/turnstile.mdx             |   12 +-
 .../cloudflare-challenges/concepts/index.mdx  |    4 +-
 .../docs/cloudflare-challenges/index.mdx      |    3 +-
 .../cloudflare-challenges/reference/index.mdx |    6 +-
 .../reference/supported-browsers.mdx          |   38 +-
 .../reference/supported-languages.mdx         |   44 +-
 .../challenge-solve-issues.mdx                |    5 +-
 .../hostname-validation/backoff-schedule.mdx  |    5 +-
 .../hostname-validation/error-codes.mdx       |    1 +
 .../hostname-validation/pre-validation.mdx    |   59 +-
 .../migrating-custom-hostnames.mdx            |    2 +-
 .../hostname-analytics.mdx                    |   16 +-
 .../performance/argo-for-saas.mdx             |    1 +
 .../performance/cache-for-saas.mdx            |    1 +
 .../performance/early-hints-for-saas.mdx      |   66 +-
 .../cloudflare-for-saas/performance/index.mdx |    9 +-
 .../reference/certificate-authorities.mdx     |    1 +
 .../reference/certificate-statuses.mdx        |    1 +
 .../reference/dcv-validation-backoff.mdx      |    1 +
 .../reference/hostname-priority.mdx           |    1 +
 .../reference/status-codes/custom-csrs.mdx    |   59 +-
 .../status-codes/custom-hostnames.mdx         |  123 +-
 .../reference/token-validity-periods.mdx      |    8 +-
 .../reference/versioning.mdx                  |   24 +-
 .../saas-customers/index.mdx                  |    3 +-
 .../saas-customers/product-compatibility.mdx  |    4 +-
 .../provider-guides/webflow.mdx               |    6 +-
 .../certificate-statuses.mdx                  |    1 +
 .../uploading-certificates.mdx                |    5 +-
 .../validate-certificates/delegated-dcv.mdx   |    5 +-
 .../validate-certificates/troubleshooting.mdx |   19 +-
 .../webhook-definitions.mdx                   |  755 ++++++-----
 .../cloudflare-for-saas/security/index.mdx    |   11 +-
 .../security/waf-for-saas/index.mdx           |   48 +-
 .../regional-services-for-saas.mdx            |    1 +
 .../advanced-settings/worker-as-origin.mdx    |    6 +-
 .../configuration/bindings.mdx                |    5 -
 .../configuration/observability.mdx           |    2 +-
 .../reference/limits.mdx                      |    2 +-
 .../reference/platform-examples.mdx           |    2 +-
 .../reference/worker-isolation.mdx            |   21 +-
 .../best-practices/minimal-ruleset.mdx        |   23 +-
 .../cloudflare-network-firewall/index.mdx     |    4 +-
 .../packet-captures/collect-pcaps.mdx         |    2 +-
 .../packet-captures/pcaps-bucket-setup.mdx    |    4 +-
 .../diagnose-traffic-decisions.mdx            |    8 +-
 .../access-controls/access-settings/index.mdx |    1 +
 .../require-access-protection.mdx             |   10 +-
 .../access-settings/session-management.mdx    |    1 -
 .../access-controls/ai-controls/index.mdx     |    1 +
 .../ai-controls/mcp-portals.mdx               |   16 +-
 .../application-token.mdx                     |   78 +-
 .../http-apps/authorization-cookie/cors.mdx   |    7 +-
 .../applications/http-apps/managed-oauth.mdx  |   14 +-
 .../http-apps/saas-apps/generic-oidc-saas.mdx |   11 +-
 .../saas-apps/grafana-cloud-saas-oidc.mdx     |    2 +-
 .../http-apps/saas-apps/grafana-saas-oidc.mdx |    2 +-
 .../http-apps/saas-apps/index.mdx             |    3 +-
 .../non-http/browser-rendering.mdx            |    9 +-
 .../arbitrary-tcp.mdx                         |    4 +-
 .../automatic-cloudflared-authentication.mdx  |    2 +-
 .../non-http/legacy-private-network-app.mdx   |    5 +-
 .../non-http/self-hosted-private-app.mdx      |   76 +-
 .../access-controls/event-subscriptions.mdx   |    2 +-
 .../access-controls/policies/app-paths.mdx    |   17 +-
 .../access-controls/policies/index.mdx        |   46 +-
 .../policies/policy-management.mdx            |   29 +-
 .../require-purpose-justification.mdx         |    1 +
 .../policies/temporary-auth.mdx               |    8 +-
 .../service-credentials/index.mdx             |    1 +
 .../service-credentials/service-tokens.mdx    |    4 +-
 .../docs/cloudflare-one/account-limits.mdx    |   19 +-
 .../docs/cloudflare-one/changelog/tunnel.mdx  |    5 +-
 .../data-classification/index.mdx             |   12 +-
 .../configure-detection-entries.mdx           |   20 +-
 .../predefined-detection-entries.mdx          |  296 ++---
 .../dlp-profiles/predefined-profiles.mdx      |   15 +-
 .../email-security/investigation/index.mdx    |    4 +-
 .../investigation/search-email.mdx            |    4 +-
 .../email-security/reference/index.mdx        |    4 +-
 .../reference/regional-processing.mdx         |    2 +-
 .../email-security/settings/auto-moves.mdx    |    4 +-
 .../detection-settings/best-practices.mdx     |    6 +-
 .../settings/detection-settings/index.mdx     |    4 +-
 .../settings/domain-management/domain.mdx     |    2 +-
 .../settings/domain-management/index.mdx      |    4 +-
 .../email-security/settings/index.mdx         |    4 +-
 .../phish-submissions/phishnet-365.mdx        |    2 +-
 .../phishnet-google-workspace.mdx             |    2 +-
 .../submission-addresses.mdx                  |    2 +-
 .../email-security/setup/index.mdx            |   18 +-
 .../email-security/setup/manage-domains.mdx   |    2 +-
 .../bcc-setup/gmail-bcc-setup/index.mdx       |    5 +-
 .../bcc-journaling/bcc-setup/index.mdx        |    5 +-
 .../bcc-journaling/index.mdx                  |    2 +-
 .../bcc-journaling/journaling-setup/index.mdx |    5 +-
 .../journaling-setup/m365-journaling.mdx      |    3 +-
 .../journaling-setup/manual-add.mdx           |    1 +
 .../setup/post-delivery-deployment/index.mdx  |    4 +-
 .../pre-delivery-deployment/egress-ips.mdx    |    2 +-
 .../setup/pre-delivery-deployment/index.mdx   |    6 +-
 .../partner-domain-tls.mdx                    |    2 +-
 .../prerequisites/index.mdx                   |    6 +-
 .../use-cases/index.mdx                       |    5 +-
 .../email-security/submissions/index.mdx      |    2 +-
 .../submissions/invalid-submissions.mdx       |    2 +-
 .../docs/cloudflare-one/faq/devices-faq.mdx   |   11 +-
 .../insights/analytics-overview.mdx           |    2 +-
 .../insights/analytics/ai-security.mdx        |   26 +-
 .../insights/analytics/application-access.mdx |   36 +-
 .../insights/dex/mcp-server.mdx               |    3 +-
 .../insights/dex/monitoring.mdx               |   10 +-
 .../cloudflare-one/insights/dex/rules.mdx     |    2 +-
 .../insights/dex/tests/index.mdx              |    6 +-
 .../docs/cloudflare-one/insights/index.mdx    |   18 +-
 .../dashboard-logs/admin-activity-logs.mdx    |   24 +-
 .../dashboard-logs/gateway-logs/index.mdx     |   63 +-
 .../insights/logs/dashboard-logs/index.mdx    |    2 +-
 .../logs/dashboard-logs/posture-logs.mdx      |    2 +-
 .../insights/logs/logpush/index.mdx           |   32 +-
 .../diagnostics/buckets.mdx                   |    4 +-
 .../network-visibility/diagnostics/index.mdx  |    5 +-
 .../integrations/cloud-and-saas/anthropic.mdx |   22 +-
 .../microsoft-365/m365-copilot-fedramp.mdx    |    2 +-
 .../microsoft-365/m365-copilot.mdx            |    2 +-
 .../identity-providers/aws-saml.mdx           |    2 +-
 .../identity-providers/cloudflare.mdx         |    4 +-
 .../identity-providers/facebook-login.mdx     |    8 +-
 .../identity-providers/github.mdx             |    4 +-
 .../integrations/identity-providers/index.mdx |    1 +
 .../integrations/identity-providers/okta.mdx  |    4 +-
 .../identity-providers/pingone-saml.mdx       |    1 +
 .../identity-providers/signed_authn.mdx       |    2 +
 .../integrations/service-providers/index.mdx  |    4 +-
 .../networks/connectivity-options.mdx         |   22 +-
 .../connectors/cloudflare-mesh/routes.mdx     |    1 -
 .../configure-tunnels/cipher-suites.mdx       |   10 +-
 .../configure-tunnels/index.mdx               |    2 +-
 .../configure-tunnels/origin-parameters.mdx   |   16 +-
 .../remote-tunnel-permissions.mdx             |  126 +-
 .../configure-tunnels/run-parameters.mdx      |   28 +-
 .../system-requirements.mdx                   |    5 +-
 .../tunnel-with-firewall.mdx                  |   19 +-
 .../deployment-guides/index.mdx               |    2 +-
 .../deployment-guides/terraform.mdx           |    1 +
 .../tunnel-useful-commands.mdx                |   14 +-
 .../downloads/copyrights.mdx                  |   57 +-
 .../cloudflare-tunnel/downloads/license.mdx   |    1 +
 .../get-started/create-remote-tunnel-api.mdx  |  117 +-
 .../get-started/create-remote-tunnel.mdx      |    6 +-
 .../cloudflare-tunnel/get-started/index.mdx   |    3 +-
 .../connectors/cloudflare-tunnel/index.mdx    |    4 +-
 .../monitor-tunnels/index.mdx                 |    3 +-
 .../monitor-tunnels/notifications.mdx         |    3 +-
 .../private-net/cloudflared/connect-cidr.mdx  |   14 +-
 .../private-net/cloudflared/index.mdx         |    3 +-
 .../private-net/cloudflared/private-dns.mdx   |   23 +-
 .../routing-to-tunnel/dns.mdx                 |   13 +-
 .../routing-to-tunnel/protocols.mdx           |   14 +-
 .../public-load-balancers.mdx                 |   41 +-
 .../troubleshoot-tunnels/common-errors.mdx    |    1 +
 .../troubleshoot-tunnels/diag-logs.mdx        |   59 +-
 .../troubleshoot-tunnels/index.mdx            |    2 +-
 .../cloudflare-tunnel/use-cases/index.mdx     |    9 +-
 .../cloudflare-tunnel/use-cases/rdp/index.mdx |    2 +-
 .../use-cases/rdp/rdp-device-client.mdx       |    2 +-
 .../use-cases/vnc-browser-rendering.mdx       |  214 ++--
 .../cloudflare-wan/analytics/index.mdx        |   23 +-
 .../analytics/netflow-analytics.mdx           |    9 +-
 .../analytics/network-analytics.mdx           |    5 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 .../analytics/site-analytics.mdx              |   16 +-
 .../configure-hardware-appliance/index.mdx    |   84 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/configure-virtual-appliance.mdx |   80 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |   11 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../maintenance/deactivate-appliance.mdx      |    1 +
 .../appliance/maintenance/heartbeat.mdx       |    1 +
 .../appliance/maintenance/index.mdx           |    3 +-
 .../maintenance/interrupt-service-window.mdx  |    1 +
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   18 +-
 .../application-based-policies/index.mdx      |   14 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    5 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   14 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../configuration/appliance/reference.mdx     |   33 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../check-tunnel-health-dashboard.mdx         |   11 +-
 .../configure-tunnel-health-alerts.mdx        |    6 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |   12 +-
 .../update-tunnel-health-checks-frequency.mdx |    3 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   34 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   45 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |   11 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../third-party/alibaba-cloud.mdx             |   19 +-
 .../third-party/aruba-edgeconnect.mdx         |   15 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   22 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   22 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    5 +-
 .../third-party/cisco-meraki-static.mdx       |   30 +-
 .../configuration/third-party/fitelnet.mdx    |   19 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   16 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   19 +-
 .../configuration/third-party/oracle.mdx      |   16 +-
 .../configuration/third-party/palo-alto.mdx   |   19 +-
 .../configuration/third-party/pfsense.mdx     |   19 +-
 .../configuration/third-party/sonicwall.mdx   |   22 +-
 .../third-party/sophos-firewall.mdx           |   22 +-
 .../configuration/third-party/strongswan.mdx  |   13 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   13 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../connectors/cloudflare-wan/get-started.mdx |   21 +-
 .../connectors/cloudflare-wan/index.mdx       |   20 +-
 .../cloudflare-wan/legal/3rdparty.mdx         |    1 +
 .../connectors/cloudflare-wan/legal/index.mdx |    3 +-
 .../cloudflare-wan/network-interconnect.mdx   |   17 +-
 .../connectors/cloudflare-wan/on-ramps.mdx    |   20 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    3 +-
 .../reference/device-compatibility.mdx        |   76 +-
 .../reference/gre-ipsec-tunnels.mdx           |   10 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |   10 +-
 .../cloudflare-wan/reference/index.mdx        |    3 +-
 .../cloudflare-wan/reference/mtu-mss.mdx      |    2 +-
 .../reference/traffic-steering.mdx            |   28 +-
 .../reference/tunnel-health-checks.mdx        |   12 +-
 .../connectors/cloudflare-wan/security.mdx    |    9 +-
 .../troubleshooting/connectivity.mdx          |   15 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   17 +-
 .../troubleshooting/routing-and-bgp.mdx       |   24 +-
 .../troubleshooting/tunnel-health.mdx         |   33 +-
 .../cloudflare-wan/wan-transformation.mdx     |   12 +-
 .../zero-trust/cloudflare-gateway.mdx         |   45 +-
 .../zero-trust/cloudflare-one-client.mdx      |   24 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   15 +-
 .../cloudflare-wan/zero-trust/index.mdx       |    1 +
 .../zero-trust/security-services.mdx          |    9 +-
 .../connectors/granular-permissions.mdx       |    2 +-
 .../networks/connectors/index.mdx             |    3 +-
 .../networks/routes/add-routes.mdx            |   20 +-
 .../networks/routes/reserved-ips.mdx          |    4 +-
 .../networks/virtual-networks.mdx             |   12 +-
 .../accessibility.mdx                         |    2 +-
 .../remote-browser-isolation/index.mdx        |    2 +
 .../known-limitations.mdx                     |    5 +-
 .../network-dependencies.mdx                  |    4 +-
 .../remote-browser-isolation/setup/index.mdx  |   14 +-
 .../custom-pages/gateway-block-page.mdx       |    2 +-
 .../custom-pages/index.mdx                    |    2 +-
 .../client-checks/antivirus.mdx               |   31 +-
 .../client-checks/application-check.mdx       |    4 +-
 .../client-checks/file-check.mdx              |    3 +-
 .../posture-checks/client-checks/firewall.mdx |   11 +-
 .../posture-checks/client-checks/index.mdx    |   41 +-
 .../client-checks/os-version.mdx              |    3 +-
 .../client-checks/require-warp.mdx            |    2 +-
 .../reusable-components/tags.mdx              |    1 +
 .../configure/modes/index.mdx                 |    4 +-
 .../troubleshooting/common-issues.mdx         |   15 -
 .../troubleshooting/connectivity-status.mdx   |   36 +-
 .../troubleshooting/diagnostic-logs.mdx       |  184 +--
 .../devices/device-registration.mdx           |   35 +-
 .../devices/user-side-certificates/index.mdx  |   10 +-
 .../manual-deployment.mdx                     |  218 ++--
 .../team-and-resources/users/risk-score.mdx   |   19 +-
 .../team-and-resources/users/scim.mdx         |    3 +-
 .../team-and-resources/users/users.mdx        |   10 +-
 .../traffic-policies/global-policies.mdx      |   18 +-
 .../network-policies/protocol-detection.mdx   |   18 +-
 .../best-practices/magic-transit-egress.mdx   |    6 +-
 .../tiered-policies/index.mdx                 |   12 +-
 .../tiered-policies/tenant-api.mdx            |    1 +
 .../cloudflare-one/troubleshooting/access.mdx |    2 +-
 .../troubleshooting/browser-isolation.mdx     |    2 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    2 +-
 .../troubleshooting/contact-support.mdx       |    4 -
 .../cloudflare-one/troubleshooting/dex.mdx    |    2 +-
 .../troubleshooting/email-security.mdx        |    2 +-
 .../troubleshooting/gateway.mdx               |    2 +-
 .../cloudflare-one/troubleshooting/tunnel.mdx |   33 +-
 .../troubleshooting/wan/connectivity.mdx      |   17 +-
 .../troubleshooting/wan/index.mdx             |    2 +-
 .../troubleshooting/wan/ipsec.mdx             |   19 +-
 .../troubleshooting/wan/routing-bgp.mdx       |   26 +-
 .../troubleshooting/wan/tunnel-health.mdx     |   35 +-
 .../troubleshooting/warp-client.mdx           |    2 +-
 .../tutorials/entra-id-risky-users.mdx        |   40 +-
 .../docs/cloudflare-wan/analytics/index.mdx   |    7 +-
 .../analytics/netflow-analytics.mdx           |    5 +-
 .../analytics/network-analytics.mdx           |    7 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    6 +-
 .../analytics/query-tunnel-health.mdx         |    9 +-
 .../analytics/site-analytics.mdx              |   19 +-
 src/content/docs/cloudflare-wan/changelog.mdx |    7 +-
 .../configure-hardware-appliance/index.mdx    |   79 +-
 .../sfp-port-information.mdx                  |    4 +-
 .../appliance/device-metrics.mdx              |    3 +-
 .../configuration/appliance/index.mdx         |    9 +-
 .../maintenance/activate-appliance.mdx        |    9 +-
 .../appliance/maintenance/index.mdx           |    5 +-
 .../maintenance/register-appliance.mdx        |    2 +-
 .../maintenance/remove-appliances.mdx         |    2 +-
 .../breakout-traffic.mdx                      |   27 +-
 .../prioritized-traffic.mdx                   |   14 +-
 .../network-options/dhcp/dhcp-options.mdx     |   42 +-
 .../network-options/dhcp/dhcp-relay.mdx       |    8 +-
 .../network-options/dhcp/dhcp-server.mdx      |    7 +-
 .../dhcp/dhcp-static-address-reservation.mdx  |    8 +-
 .../appliance/network-options/index.mdx       |    5 +-
 .../network-options/link-aggregation.mdx      |   14 +-
 .../appliance/network-options/nat-subnet.mdx  |   15 +-
 .../network-options/network-segmentation.mdx  |   11 +-
 .../network-options/routed-subnets.mdx        |   18 +-
 .../appliance/troubleshooting.mdx             |    9 +-
 .../common-settings/custom-ike-id-ipsec.mdx   |    5 +-
 .../configuration/common-settings/sites.mdx   |    8 +-
 .../configure-cloudflare-source-ips.mdx       |   13 +-
 .../configuration/how-to/configure-routes.mdx |   25 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   32 +-
 .../configuration/how-to/index.mdx            |    5 +-
 .../configuration/how-to/traceroute.mdx       |    7 +-
 .../cloudflare-wan/configuration/index.mdx    |    3 +-
 .../configuration/multi-cloud-networking.mdx  |    3 +-
 .../third-party/alibaba-cloud.mdx             |   20 +-
 .../configuration/third-party/aws.mdx         |   17 +-
 .../third-party/azure/azure-virtual-wan.mdx   |   21 +-
 .../third-party/azure/azure-vpn-gateway.mdx   |   21 +-
 .../configuration/third-party/azure/index.mdx |    4 +-
 .../third-party/cisco-ios-xe.mdx              |    6 +-
 .../third-party/cisco-meraki-static.mdx       |   21 +-
 .../configuration/third-party/fitelnet.mdx    |   20 +-
 .../configuration/third-party/fortinet.mdx    |   25 +-
 .../configuration/third-party/google.mdx      |   17 +-
 .../configuration/third-party/index.mdx       |    5 +-
 .../configuration/third-party/juniper.mdx     |   18 +-
 .../configuration/third-party/oracle.mdx      |   17 +-
 .../configuration/third-party/palo-alto.mdx   |   18 +-
 .../configuration/third-party/pfsense.mdx     |   20 +-
 .../configuration/third-party/sonicwall.mdx   |   23 +-
 .../third-party/sophos-firewall.mdx           |   23 +-
 .../configuration/third-party/strongswan.mdx  |   14 +-
 .../configuration/third-party/ubiquiti.mdx    |   10 +-
 .../configuration/third-party/velocloud.mdx   |   14 +-
 .../configuration/third-party/viptela.mdx     |   19 +-
 .../configuration/third-party/vyos.mdx        |    4 +-
 .../configuration/third-party/yamaha.mdx      |   16 +-
 .../docs/cloudflare-wan/get-started.mdx       |   11 +-
 src/content/docs/cloudflare-wan/glossary.mdx  |    3 +-
 src/content/docs/cloudflare-wan/index.mdx     |    5 +-
 .../docs/cloudflare-wan/legal/3rdparty.mdx    |    3 +-
 .../docs/cloudflare-wan/legal/index.mdx       |    5 +-
 .../cloudflare-wan/network-interconnect.mdx   |   16 +-
 src/content/docs/cloudflare-wan/on-ramps.mdx  |    4 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/bandwidth-measurement.mdx       |    4 +-
 .../reference/device-compatibility.mdx        |   58 +-
 .../reference/gre-ipsec-tunnels.mdx           |    4 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/cloudflare-wan/reference/index.mdx   |    5 +-
 .../docs/cloudflare-wan/reference/mtu-mss.mdx |    6 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    9 +-
 .../reference/virtual-networks.mdx            |    9 +-
 src/content/docs/cloudflare-wan/security.mdx  |    8 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../cloudflare-wan/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   10 +-
 .../troubleshooting/routing-and-bgp.mdx       |   22 +-
 .../troubleshooting/tunnel-health.mdx         |   30 +-
 .../zero-trust/cloudflare-tunnel.mdx          |   12 +-
 .../zero-trust/connectivity-options.mdx       |   19 +-
 .../docs/cloudflare-wan/zero-trust/index.mdx  |    4 +-
 .../docs/constellation/platform/index.mdx     |    2 +-
 src/content/docs/containers/examples/cron.mdx |   41 +-
 .../examples/durable-object-interface.mdx     |    1 +
 .../docs/containers/examples/index.mdx        |    1 +
 .../containers/platform-details/placement.mdx |    8 +-
 src/content/docs/containers/pricing.mdx       |    2 +-
 src/content/docs/containers/ssh.mdx           |    2 +-
 .../d1/best-practices/local-development.mdx   |    2 +
 .../docs/d1/best-practices/query-d1.mdx       |   50 +-
 .../d1/best-practices/remote-development.mdx  |   15 +-
 .../docs/d1/best-practices/retry-queries.mdx  |   26 +-
 .../d1/best-practices/use-d1-from-pages.mdx   |    2 +-
 .../docs/d1/best-practices/use-indexes.mdx    |   26 +-
 .../docs/d1/configuration/environments.mdx    |   60 +-
 src/content/docs/d1/get-started.mdx           |   12 +-
 src/content/docs/d1/observability/billing.mdx |    4 +-
 src/content/docs/d1/platform/limits.mdx       |   34 +-
 .../docs/d1/reference/community-projects.mdx  |   40 +-
 .../docs/d1/reference/data-security.mdx       |    6 +-
 src/content/docs/d1/reference/faq.mdx         |    4 +-
 .../docs/d1/reference/generated-columns.mdx   |   24 +-
 src/content/docs/d1/reference/glossary.mdx    |    2 +-
 src/content/docs/d1/reference/migrations.mdx  |    6 +-
 src/content/docs/d1/sql-api/foreign-keys.mdx  |   28 +-
 src/content/docs/d1/sql-api/query-json.mdx    |   82 +-
 .../tutorials/build-an-api-to-access-d1.mdx   |    8 +-
 .../docs/d1/tutorials/d1-and-prisma-orm.mdx   |    2 +-
 .../docs/data-localization/compatibility.mdx  |   68 +-
 .../data-localization/geo-key-manager.mdx     |    5 +-
 .../docs/ddos-protection/about/components.mdx |    3 +-
 .../about/how-ddos-protection-works.mdx       |   17 +-
 .../docs/ddos-protection/about/index.mdx      |    5 +-
 .../api/dns-protection/index.mdx              |   17 +-
 .../api/dns-protection/json-objects.mdx       |   21 +-
 .../advanced-ddos-systems/api/index.mdx       |    3 +-
 .../programmable-flow-protection/examples.mdx |  209 +--
 .../programmable-flow-protection/index.mdx    |   37 +-
 .../json-objects.mdx                          |   61 +-
 .../api/tcp-protection/examples.mdx           |  217 ++--
 .../api/tcp-protection/index.mdx              |  103 +-
 .../api/tcp-protection/json-objects.mdx       |   51 +-
 .../how-to/add-prefix.mdx                     |    6 +-
 .../how-to/exclude-prefix.mdx                 |    5 +-
 .../advanced-ddos-systems/how-to/index.mdx    |    5 +-
 .../advanced-ddos-systems/index.mdx           |    4 +-
 .../advanced-ddos-systems/overview/index.mdx  |   16 +-
 .../overview/programmable-flow-protection.mdx |   92 +-
 .../advanced-ddos-systems/troubleshooting.mdx |   13 +-
 .../ddos-protection/best-practices/index.mdx  |    3 +-
 .../best-practices/proactive-defense.mdx      |    4 +-
 .../best-practices/third-party.mdx            |    2 +-
 .../ddos-protection/botnet-threat-feed.mdx    |   58 +-
 .../docs/ddos-protection/get-started.mdx      |    3 +-
 .../managed-rulesets/http/index.mdx           |    2 +-
 .../managed-rulesets/index.mdx                |    1 +
 .../managed-rulesets/network/index.mdx        |    2 +-
 .../network-overrides/override-examples.mdx   |   12 +-
 .../docs/ddos-protection/reference/alerts.mdx |    2 +-
 .../docs/ddos-protection/reference/index.mdx  |    3 +-
 .../docs/ddos-protection/reference/logs.mdx   |    3 +-
 .../reference/simulate-ddos-attack.mdx        |    3 +-
 src/content/docs/dmarc-management/enable.mdx  |    3 +-
 .../dmarc-management/security-records.mdx     |    2 +-
 .../docs/dmarc-management/statistics.mdx      |    1 +
 .../docs/dns/additional-options/index.mdx     |    2 +-
 src/content/docs/dns/changelog.mdx            |    8 +-
 .../docs/dns/cname-flattening/index.mdx       |    2 +-
 .../set-up-cname-flattening.mdx               |    8 +-
 .../random-prefix-attacks/setup.mdx           |   11 +-
 src/content/docs/dns/dnssec/dnssec-states.mdx |   13 +-
 src/content/docs/dns/dnssec/enable-nsec3.mdx  |    4 +-
 src/content/docs/dns/dnssec/index.mdx         |   19 +-
 .../dns/dnssec/multi-signer-dnssec/about.mdx  |    4 +-
 .../dns/dnssec/multi-signer-dnssec/setup.mdx  |    2 +-
 .../dnssec/validation-and-key-management.mdx  |    8 +-
 .../docs/dns/foundation-dns/dnssec-keys.mdx   |    3 +-
 src/content/docs/dns/foundation-dns/index.mdx |   23 +-
 src/content/docs/dns/glossary.mdx             |    2 +-
 .../docs/dns/internal-dns/analytics.mdx       |    2 +-
 .../how-to/create-subdomain.mdx               |    3 +-
 .../how-to/email-records.mdx                  |   15 +-
 .../dns/manage-dns-records/how-to/index.mdx   |    3 +-
 .../how-to/managing-dynamic-ip-addresses.mdx  |    3 +-
 .../how-to/round-robin-dns.mdx                |    1 +
 .../how-to/subdomains-outside-cloudflare.mdx  |   17 +-
 .../manage-dns-records/reference/index.mdx    |    3 +-
 .../reference/record-attributes.mdx           |   17 +-
 .../dns/manage-dns-records/reference/ttl.mdx  |    3 +-
 .../troubleshooting/exposed-ip-address.mdx    |    3 +-
 .../troubleshooting/index.mdx                 |    5 +-
 .../dns/nameservers/advanced-nameservers.mdx  |    1 +
 .../zone-custom-nameservers.mdx               |    1 -
 .../docs/dns/private-origins/index.mdx        |    3 +-
 .../docs/dns/reference/all-features.mdx       |    3 +-
 .../dns/reference/analytics-mcp-server.mdx    |    3 +-
 .../docs/dns/reference/best-practices.mdx     |    3 +-
 .../docs/dns/reference/domain-connect.mdx     |   18 +-
 src/content/docs/dns/reference/index.mdx      |    2 +-
 .../recommended-third-party-tools.mdx         |    9 +-
 .../docs/dns/troubleshooting/email-issues.mdx |   12 +-
 .../docs/dns/troubleshooting/index.mdx        |    9 +-
 .../conversions/convert-full-to-secondary.mdx |   34 +-
 .../conversions/convert-partial-to-full.mdx   |    2 +-
 .../dns/zone-setups/conversions/index.mdx     |    2 +-
 .../docs/dns/zone-setups/full-setup/index.mdx |    2 +-
 .../partial-setup/dns-resolution.mdx          |    7 +-
 .../dns/zone-setups/partial-setup/setup.mdx   |   11 +-
 .../zone-setups/reference/domain-status.mdx   |   10 +-
 .../docs/dns/zone-setups/reference/index.mdx  |    3 +-
 .../subdomain-setup/move-to-new-account.mdx   |    1 +
 .../zone-setups/subdomain-setup/rollback.mdx  |    5 +-
 .../subdomain-setup/setup/parent-on-full.mdx  |    3 +
 .../setup/parent-on-partial.mdx               |    3 +-
 .../dns/zone-setups/troubleshooting/index.mdx |    3 +-
 .../cloudflare-as-primary/index.mdx           |    2 +-
 .../transfer-criteria.mdx                     |    3 +-
 .../cloudflare-as-secondary/alerts.mdx        |    3 +-
 .../cloudflare-as-secondary/index.mdx         |    4 +-
 .../cloudflare-as-secondary/proxy-traffic.mdx |    2 +-
 .../docs/durable-objects/api/alarms.mdx       |   77 +-
 .../api/legacy-kv-storage-api.mdx             |   13 +-
 .../api/sqlite-storage-api.mdx                |   24 +-
 .../access-durable-objects-storage.mdx        |    3 -
 .../concepts/durable-object-lifecycle.mdx     |    2 +-
 .../docs/durable-objects/examples/agents.mdx  |    2 +-
 .../docs/durable-objects/examples/index.mdx   |    5 +-
 .../examples/websocket-server.mdx             |    8 +-
 .../observability/data-studio.mdx             |    2 +-
 .../durable-objects/platform/known-issues.mdx |    2 +-
 .../docs/durable-objects/platform/limits.mdx  |    1 +
 .../reference/data-location.mdx               |   16 +-
 .../reference/data-security.mdx               |    6 +-
 .../reference/environments.mdx                |    7 +-
 .../docs/durable-objects/reference/faq.mdx    |    6 +-
 .../durable-objects/reference/glossary.mdx    |    2 +-
 .../reference/in-memory-state.mdx             |   30 +-
 .../docs/durable-objects/video-tutorials.mdx  |   12 +-
 .../docs/dynamic-workers/usage/bindings.mdx   |  140 +-
 .../email-workers/local-development.mdx       |   95 +-
 .../email-workers/reply-email-workers.mdx     |   60 +-
 .../email-routing/get-started/audit-logs.mdx  |    8 +-
 .../docs/email-routing/get-started/index.mdx  |    2 +-
 .../docs/email-routing/graphql-example.mdx    |    2 +-
 src/content/docs/email-routing/limits.mdx     |    2 +-
 src/content/docs/email-routing/postmaster.mdx |    3 +-
 .../setup/email-routing-dns-records.mdx       |    8 +-
 .../docs/email-routing/setup/index.mdx        |    2 +-
 .../email-routing/troubleshooting/index.mdx   |    2 +-
 .../email-security/account-setup/index.mdx    |    2 +-
 .../gsuite-bcc-setup/create-project-gcp.mdx   |    4 +-
 .../deployment/inline/reference/index.mdx     |    2 +-
 .../deployment/inline/setup/index.mdx         |    2 +-
 .../domains-and-routing/alert-webhooks.mdx    |   10 +-
 .../domains-and-routing/index.mdx             |    2 +-
 .../email-policies/index.mdx                  |    2 +-
 .../enhanced-detections/index.mdx             |    2 +-
 .../email-configuration/lists/index.mdx       |    2 +-
 .../migrate-to-email-security.mdx             |   26 +-
 .../docs/email-security/reference/index.mdx   |    2 +-
 src/content/docs/email-service/api/index.mdx  |    2 +-
 .../api/route-emails/email-handler.mdx        |    2 +-
 .../email-service/api/route-emails/index.mdx  |    2 +-
 .../api/send-emails/rest-api.mdx              |   52 +-
 .../api/send-emails/workers-api.mdx           |   40 +-
 .../docs/email-service/concepts/index.mdx     |    2 +-
 .../email-service/configuration/index.mdx     |    2 +-
 .../email-routing/hard-bounce-handling.mdx    |  241 ++--
 .../examples/email-routing/spam-filtering.mdx |   33 +-
 .../email-service/get-started/send-emails.mdx |   34 +-
 .../email-service/local-development/index.mdx |    2 +-
 .../local-development/routing.mdx             |   44 +-
 .../docs/email-service/platform/index.mdx     |    2 +-
 .../docs/email-service/platform/pricing.mdx   |    8 +-
 .../docs/email-service/reference/index.mdx    |    5 +-
 .../email-service/reference/postmaster.mdx    |    1 +
 .../docs/firewall/api/cf-filters/delete.mdx   |   38 +-
 .../docs/firewall/api/cf-filters/get.mdx      |  100 +-
 .../docs/firewall/api/cf-filters/post.mdx     |   68 +-
 .../docs/firewall/api/cf-filters/put.mdx      |   52 +-
 .../firewall/api/cf-filters/validation.mdx    |   34 +-
 .../api/cf-filters/what-is-a-filter.mdx       |   10 +-
 .../firewall/api/cf-firewall-rules/get.mdx    |  160 +--
 .../firewall/api/cf-firewall-rules/post.mdx   |  116 +-
 .../cf-firewall-rules/order-priority.mdx      |    1 +
 .../account-security/cloudflare-access.mdx    |    4 +-
 .../account/account-security/index.mdx        |    2 +-
 .../leaked-password-notifications.mdx         |    2 +
 .../manage-active-sessions.mdx                |    2 +-
 .../account/account-security/zone-holds.mdx   |    4 +-
 .../fundamentals/account/create-account.mdx   |   11 +-
 .../account/find-account-and-zone-ids.mdx     |   12 +-
 .../docs/fundamentals/account/index.mdx       |    2 +-
 .../api/how-to/control-api-access.mdx         |    6 +-
 .../api/how-to/create-via-api.mdx             |   32 +-
 .../api/how-to/restrict-tokens.mdx            |    7 +-
 src/content/docs/fundamentals/api/index.mdx   |    2 +-
 .../docs/fundamentals/api/reference/index.mdx |    2 +-
 .../fundamentals/api/reference/limits.mdx     |    6 +-
 .../docs/fundamentals/api/troubleshooting.mdx |   18 +-
 .../concepts/how-cloudflare-works.mdx         |    8 +-
 .../docs/fundamentals/concepts/index.mdx      |    2 +-
 .../concepts/traffic-flow-cloudflare.mdx      |   22 +-
 src/content/docs/fundamentals/index.mdx       |    4 +-
 .../fundamentals/manage-domains/add-site.mdx  |   11 +-
 .../manage-domains/domain-version.mdx         |   12 +-
 .../manage-domains/move-domain.mdx            |    2 +
 .../manage-domains/pause-cloudflare.mdx       |    4 +-
 .../fundamentals/manage-members/index.mdx     |    2 +-
 .../fundamentals/manage-members/policies.mdx  |    5 +-
 .../fundamentals/manage-members/roles.mdx     |    2 +-
 .../fundamentals/manage-members/scope.mdx     |   52 +-
 .../manage-members/user-groups.mdx            |   23 +-
 .../docs/fundamentals/new-features/index.mdx  |    4 +-
 .../organizations/limitations.mdx             |    4 +-
 .../docs/fundamentals/organizations/setup.mdx |   16 +-
 .../fundamentals/performance/improve-seo.mdx  |   16 +-
 .../docs/fundamentals/performance/index.mdx   |    2 +-
 .../fundamentals/performance/test-speed.mdx   |   16 +-
 .../fundamentals/reference/best-practices.mdx |    6 +-
 .../reference/cdn-cgi-endpoint.mdx            |   12 +-
 .../reference/cloudflare-ray-id.mdx           |    3 +-
 .../reference/connection-limits.mdx           |   22 +-
 .../reference/cryptographic-personhood.mdx    |   44 +-
 .../docs/fundamentals/reference/glossary.mdx  |    2 +-
 .../reference/google-analytics.mdx            |    4 +
 .../docs/fundamentals/reference/index.mdx     |    2 +-
 .../scim-virtual-groups-migration.mdx         |   17 +-
 .../docs/fundamentals/reference/partners.mdx  |    2 +-
 .../delivering-videos-with-cloudflare.mdx     |   18 +-
 .../reference/policies-compliances/index.mdx  |    2 +-
 .../docs/fundamentals/reference/redirects.mdx |    2 +-
 .../report-abuse/abuse-report-obligations.mdx |    6 +-
 .../report-abuse/complaint-types.mdx          |   26 +-
 .../reference/report-abuse/index.mdx          |    8 +-
 .../reference/report-abuse/submit-report.mdx  |   12 +-
 .../sdk-ecosystem-support-policy.mdx          |   14 +-
 .../reference/tcp-connections.mdx             |    4 +-
 .../reference/troubleshooting.mdx             |   44 +-
 .../docs/fundamentals/security/index.mdx      |    2 +-
 .../docs/fundamentals/security/pci-scans.mdx  |    6 +-
 .../security/under-ddos-attack.mdx            |    8 +-
 .../docs/fundamentals/user-profiles/2fa.mdx   |   34 +-
 .../user-profiles/account-recovery.mdx        |   10 +-
 .../change-password-or-email.mdx              |    2 +-
 .../user-profiles/customize-account.mdx       |    6 +-
 .../user-profiles/delete-account.mdx          |    5 +-
 .../docs/fundamentals/user-profiles/login.mdx |    7 +-
 .../multi-factor-email-authentication.mdx     |    6 +-
 .../user-profiles/verify-email-address.mdx    |    6 +-
 src/content/docs/google-tag-gateway/index.mdx |    6 +-
 .../concepts/health-checks-regions.mdx        |    1 +
 .../docs/health-checks/concepts/index.mdx     |    3 +-
 .../health-checks/health-checks-analytics.mdx |    3 +-
 .../how-to/health-checks-notifications.mdx    |    5 +-
 .../docs/health-checks/how-to/index.mdx       |    3 +-
 .../health-checks/how-to/zone-lockdown.mdx    |    3 +-
 .../drizzle-orm.mdx                           |    4 +-
 .../prisma-postgres.mdx                       |   15 +-
 .../postgres-database-providers/supabase.mdx  |    2 +-
 .../observability/troubleshooting.mdx         |   78 +-
 .../docs/hyperdrive/platform/limits.mdx       |   28 +-
 .../hyperdrive/platform/storage-options.mdx   |    2 +-
 .../reference/wrangler-commands.mdx           |    2 +-
 .../docs/hyperdrive/tutorials/index.mdx       |    2 +-
 ...rverless-timeseries-api-with-timescale.mdx |    2 +-
 .../optimization/make-responsive-images.mdx   |   17 +-
 .../optimization/transformations/flows.mdx    |   19 +-
 .../optimization/transformations/overview.mdx |    3 +-
 .../docs/key-transparency/api/epochs.mdx      |    2 +-
 .../docs/key-transparency/api/index.mdx       |    4 +-
 .../docs/key-transparency/api/namespaces.mdx  |    8 +-
 .../docs/kv/api/delete-key-value-pairs.mdx    |   37 +-
 src/content/docs/kv/concepts/kv-bindings.mdx  |   32 +-
 .../docs/kv/concepts/kv-namespaces.mdx        |   17 +-
 src/content/docs/kv/get-started.mdx           |   15 +-
 src/content/docs/kv/glossary.mdx              |    2 +-
 src/content/docs/kv/observability/index.mdx   |    2 +-
 .../kv/observability/metrics-analytics.mdx    |    1 -
 src/content/docs/kv/platform/pricing.mdx      |    2 +-
 .../docs/kv/reference/data-security.mdx       |    6 +-
 .../docs/kv/reference/environments.mdx        |    2 +
 src/content/docs/kv/reference/kv-commands.mdx |    4 +-
 .../account-security/audit-logs.mdx           |    2 +-
 .../account-security/index.mdx                |    6 +-
 .../review-active-sessions.mdx                |    2 +-
 .../account-security/review-audit-logs.mdx    |    2 +-
 .../account-security/set-up-2fa.mdx           |    4 +-
 .../browser-integrity.mdx                     |    2 +-
 .../default-traffic-security/ddos.mdx         |    4 +-
 .../default-traffic-security/dnssec.mdx       |    2 +-
 .../default-traffic-security/index.mdx        |    2 +-
 .../default-traffic-security/mtls.mdx         |    2 +-
 .../application-security/firewall/index.mdx   |    4 +-
 .../lists/configuration.mdx                   |    2 +-
 .../application-security/lists/features.mdx   |    2 +-
 .../application-security/lists/index.mdx      |    8 +-
 .../application-security/lists/use-cases.mdx  |    2 +-
 .../rate-limiting/configurations.mdx          |   16 +-
 .../rate-limiting/features.mdx                |    2 +-
 .../rate-limiting/index.mdx                   |    4 +-
 .../rate-limiting/use-cases.mdx               |    2 +-
 .../security-center/brand-protection.mdx      |    2 +-
 .../security-center/index.mdx                 |    6 +-
 .../access-application/index.mdx              |    8 +-
 .../advanced-workflows/index.mdx              |    8 +-
 .../alternative-onramps/clientless-rbi.mdx    |    6 +-
 .../alternative-onramps/index.mdx             |    4 +-
 .../clientless-access/concepts/index.mdx      |    2 +-
 .../concepts/what-is-clientless-access.mdx    |    2 +-
 .../best-practices.mdx                        |    6 +-
 .../create-tunnel.mdx                         |   11 +-
 .../connect-private-applications/index.mdx    |    4 +-
 .../customize-ux/app-launcher.mdx             |    2 +-
 .../customize-ux/block-page.mdx               |    2 +-
 .../customize-ux/bookmarks.mdx                |    2 +-
 .../clientless-access/customize-ux/index.mdx  |    8 +-
 .../customize-ux/login-page.mdx               |    2 +-
 .../clientless-access/customize-ux/tags.mdx   |    2 +-
 .../clientless-access/initial-setup/index.mdx |    8 +-
 .../migrate-applications/best-practices.mdx   |   14 +-
 .../migrate-applications/index.mdx            |    6 +-
 .../migrate-applications/integrated-sso.mdx   |   12 +-
 .../clientless-access/terraform/index.mdx     |    2 +-
 .../create-zero-trust-org.mdx                 |    2 +-
 .../cybersafe/account-creation/index.mdx      |    6 +-
 .../cybersafe/concepts/index.mdx              |    8 +-
 .../concepts/what-is-dns-filtering.mdx        |   18 +-
 .../gateway-verify-local-connectivity.mdx     |    8 +-
 .../advertise-prefixes.mdx                    |    2 +-
 .../data-center-protection/concepts/index.mdx |    2 +-
 .../data-center-protection/configure-ddos.mdx |   14 +-
 .../configure-routes.mdx                      |   18 +-
 .../configure-tunnels.mdx                     |   29 +-
 .../configure-tunnels-routes/index.mdx        |    2 +-
 .../enable-notifications.mdx                  |    5 +-
 .../data-center-protection/get-started.mdx    |    8 +-
 .../run-pre-flight-checks.mdx                 |    1 -
 .../dns-best-practices/concepts/index.mdx     |    8 +-
 .../dns-best-practices/concepts/phase-1.mdx   |   52 +-
 .../dns-best-practices/concepts/phase-2.mdx   |   42 +-
 .../dns-best-practices/concepts/phase-3.mdx   |   31 +-
 .../dns-best-practices/concepts/phase-4.mdx   |   38 +-
 .../concepts/summary-considerations.mdx       |   20 +-
 .../holistic-ai-security/appendix/index.mdx   |    1 +
 .../holistic-ai-security/concepts/index.mdx   |    1 +
 .../holistic-ai-security/concepts/mcp.mdx     |    1 +
 .../concepts/shadow-ai.mdx                    |    1 +
 .../get-started/additional-setup.mdx          |    2 +-
 .../get-started/define-ai-risk-tolerance.mdx  |    1 -
 .../get-started/index.mdx                     |    2 +-
 .../monitor-ai-use/index.mdx                  |    1 +
 .../monitor-prompts-responses.mdx             |    3 +-
 .../monitor-ai-use/review-inline-ai-use.mdx   |    3 +-
 .../load-balancing/concepts/health-checks.mdx |    2 +-
 .../load-balancing/concepts/index.mdx         |    8 +-
 .../concepts/load-balancer-components.mdx     |   12 +-
 .../load-balancing/concepts/routing.mdx       |    8 +-
 .../load-balancing/planning/custom-rules.mdx  |    2 +-
 .../load-balancing/planning/index.mdx         |    8 +-
 .../planning/multiple-zones.mdx               |    2 +
 .../planning/origin-steering-policies.mdx     |    6 +-
 .../planning/session-affinity.mdx             |    2 +-
 .../planning/traffic-steering.mdx             |    4 +-
 .../planning/types-load-balancers.mdx         |   16 +-
 .../setup/check-pool-health.mdx               |    2 +-
 .../setup/hostname-preparation.mdx            |    8 +-
 .../load-balancing/setup/index.mdx            |   14 +-
 .../load-balancing/setup/next-steps.mdx       |    2 +-
 .../setup/production-traffic.mdx              |    2 +-
 .../mtls/concepts/mtls-cloudflare.mdx         |   12 +-
 .../mtls/mtls-implementation/index.mdx        |    2 +-
 .../advanced/improve-analytics.mdx            |    2 +-
 .../prevent-ddos-attacks/advanced/index.mdx   |    8 +-
 .../prevent-ddos-attacks/baseline/index.mdx   |    6 +-
 .../baseline/proxy-dns-records.mdx            |    2 +-
 .../baseline/set-up-alerts.mdx                |    2 +-
 .../baseline/tls-versions.mdx                 |    4 +-
 .../prevent-ddos-attacks/concepts/index.mdx   |    4 +-
 .../replace-vpn/build-policies/index.mdx      |    8 +-
 .../build-policies/policy-design.mdx          |   10 +-
 .../build-policies/session-timeouts.mdx       |    2 +-
 .../test-your-first-application.mdx           |    7 +-
 .../replace-vpn/concepts/index.mdx            |    6 +-
 .../concepts/what-is-cloudflare.mdx           |    2 +-
 .../connect-private-network/cloudflared.mdx   |   19 +-
 .../connection-methods.mdx                    |   22 +-
 .../connect-private-network/index.mdx         |    6 +-
 .../overlapping-ips.mdx                       |    2 +-
 .../tunnel-capacity.mdx                       |    2 +-
 .../replace-vpn/get-started/prerequisites.mdx |    8 +-
 .../replace-vpn/troubleshooting/index.mdx     |    4 +-
 .../troubleshoot-private-networks.mdx         |    2 +-
 .../build-dns-policies/index.mdx              |    6 +-
 .../build-egress-policies/index.mdx           |    8 +-
 .../build-http-policies/index.mdx             |    8 +-
 .../concepts/index.mdx                        |    4 +-
 .../choose-on-ramp.mdx                        |   12 +-
 .../initial-setup/prerequisites.mdx           |    4 +-
 .../secure-saas-applications/index.mdx        |    6 +-
 .../sso-front-door.mdx                        |   10 +-
 .../understand-policies/index.mdx             |    6 +-
 .../understand-policies/indicator-feeds.mdx   |    4 +-
 .../order-of-enforcement.mdx                  |    2 +-
 .../secure-your-email/concepts/index.mdx      |    2 +-
 .../protect-from-phishing-attacks.mdx         |    2 +-
 .../concepts/what-is-cloudflare.mdx           |    4 +-
 .../concepts/what-is-email-security.mdx       |    2 +-
 .../concepts/what-is-phishing-attack.mdx      |    2 +-
 .../active-directory-sync.mdx                 |    2 +-
 .../configure-email-security/audit-logs.mdx   |    3 +-
 .../impersonation-registry.mdx                |    2 +-
 .../configure-email-security/index.mdx        |    2 +-
 .../configure-email-security/report-phish.mdx |    2 +-
 .../enable-auto-moves/index.mdx               |    2 +-
 .../get-started/deployment-models.mdx         |    4 +-
 .../get-started/prerequisites.mdx             |    2 +-
 .../recommended-deployment-model.mdx          |    2 +-
 .../get-started/setup-google-workspace.mdx    |    2 +-
 .../get-started/setup-ms-graph-api.mdx        |    4 +-
 .../monitor-your-inbox/phish-submissions.mdx  |    2 +-
 .../surge-readiness/concepts/index.mdx        |   12 +-
 .../surge-readiness/performance/analytics.mdx |    4 +-
 .../surge-readiness/performance/caching.mdx   |   22 +-
 .../surge-readiness/performance/index.mdx     |    2 +-
 .../surge-readiness/performance/logs.mdx      |    7 +-
 .../security/block-agents-lock-zones.mdx      |    1 +
 .../security/confirm-account-security.mdx     |    2 +-
 .../security/control-domain-access.mdx        |   12 +-
 .../surge-readiness/security/enable-iaum.mdx  |    4 +-
 .../surge-readiness/security/index.mdx        |    2 +-
 .../surge-readiness/support/index.mdx         |    2 +-
 .../surge-readiness/support/resources.mdx     |   15 +-
 .../workers/concepts/cloudflare-intro.mdx     |   30 +-
 .../learning-paths/workers/concepts/index.mdx |    6 +-
 .../workers/concepts/serverless-computing.mdx |    6 +-
 .../learning-paths/workers/devplat/index.mdx  |    4 +-
 .../workers/devplat/intro-to-devplat.mdx      |    2 +-
 .../workers/get-started/c3-and-wrangler.mdx   |    8 +-
 .../workers/get-started/first-application.mdx |   23 +-
 .../workers/get-started/index.mdx             |    6 +-
 .../additional-dns-records.mdx                |    5 +-
 .../additional-options/cloudflare-tunnel.mdx  |    1 +
 .../additional-options/index.mdx              |   13 +-
 .../load-balancing-china.mdx                  |    1 +
 .../load-balancing-rules/expressions.mdx      |   13 +-
 .../override-http-host-headers.mdx            |   30 +-
 .../pagerduty-integration.mdx                 |    1 +
 .../planned-maintenance.mdx                   |   12 +-
 .../docs/load-balancing/api-reference.mdx     |    1 +
 .../get-started/enable-load-balancing.mdx     |    3 +-
 .../docs/load-balancing/get-started/index.mdx |    5 +-
 .../load-balancers/common-configurations.mdx  |    7 +-
 .../docs/load-balancing/monitors/index.mdx    |    4 +-
 .../monitors/monitor-groups.mdx               |    1 +
 .../private-network/cloudflare-wan.mdx        |    6 +-
 .../reference-architecture-external-link.mdx  |    1 +
 .../docs/load-balancing/reference/index.mdx   |    3 +-
 .../load-balancing/reference/limitations.mdx  |   15 +-
 .../reference/migration-guides/index.mdx      |    3 +-
 .../troubleshooting/common-error-codes.mdx    |   53 +-
 .../load-balancing/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/load-balancing-faq.mdx    |   37 +-
 .../understand-basics/adaptive-routing.mdx    |    3 +-
 .../understand-basics/index.mdx               |    3 +-
 .../traffic-steering/index.mdx                |    1 +
 .../hash-origin-steering.mdx                  |    4 +
 .../least-outstanding-requests-pools.mdx      |    7 +-
 .../random-origin-steering.mdx                |    1 +
 .../steering-policies/dynamic-steering.mdx    |    1 +
 .../steering-policies/index.mdx               |    1 -
 .../least-outstanding-requests.mdx            |    3 +-
 .../steering-policies/proximity-steering.mdx  |    9 +-
 .../steering-policies/standard-options.mdx    |    1 +
 src/content/docs/log-explorer/api.mdx         |    6 +-
 src/content/docs/log-explorer/changelog.mdx   |    2 +-
 .../docs/log-explorer/example-queries.mdx     |    2 +-
 src/content/docs/log-explorer/index.mdx       |   42 +-
 .../docs/logs/auditlogs-mcp-server.mdx        |    2 +-
 .../docs/logs/changelog/audit-logs.mdx        |    2 +-
 src/content/docs/logs/changelog/index.mdx     |    2 +-
 src/content/docs/logs/changelog/logs.mdx      |    2 +
 .../docs/logs/faq/common-calculations.mdx     |    2 +
 src/content/docs/logs/faq/general-faq.mdx     |    3 +
 src/content/docs/logs/faq/instant-logs.mdx    |    3 +
 src/content/docs/logs/faq/logpull-api.mdx     |    5 +
 .../docs/logs/faq/worker-subrequests.mdx      |   14 +-
 src/content/docs/logs/glossary.mdx            |    2 +-
 src/content/docs/logs/logpull/index.mdx       |    4 +-
 .../docs/logs/logpull/requesting-logs.mdx     |   22 +-
 .../logs/logpull/understanding-the-basics.mdx |   24 +-
 src/content/docs/logs/logpush-mcp-server.mdx  |    2 +-
 .../examples/example-logpush-python.mdx       |    2 +
 .../docs/logs/logpush/examples/index.mdx      |    2 +-
 src/content/docs/logs/logpush/index.mdx       |    4 +-
 .../docs/logs/logpush/logpush-health.mdx      |   72 +-
 .../logpush/logpush-job/api-configuration.mdx |  140 +-
 .../logpush-job/datasets/account/index.mdx    |    2 +-
 .../logs/logpush/logpush-job/datasets/cmb.mdx |    4 +-
 .../logpush/logpush-job/datasets/index.mdx    |   16 +-
 .../logpush-job/datasets/zone/dns_logs.md     |    2 +-
 .../logpush-job/datasets/zone/index.mdx       |    2 +-
 .../logpush/logpush-job/edge-log-delivery.mdx |    3 +-
 .../enable-destinations/aws-s3.mdx            |    6 +-
 .../logpush-job/enable-destinations/azure.mdx |    1 -
 .../enable-destinations/egress-ip.mdx         |   26 +-
 .../enable-destinations/elastic.mdx           |   33 +-
 .../google-cloud-storage.mdx                  |    6 +-
 .../enable-destinations/ibm-qradar.mdx        |  150 +--
 .../enable-destinations/kinesis.mdx           |    2 +-
 .../third-party/exabeam.mdx                   |    2 +-
 .../third-party/sekoia.mdx                    |    2 +-
 .../third-party/taegis.mdx                    |    2 +-
 .../docs/logs/logpush/logpush-job/filters.mdx |    5 +-
 .../docs/logs/logpush/logpush-job/index.mdx   |    2 +-
 .../logpush-ownership-challenge.mdx           |   22 +-
 .../2023-02-01-security-fields-updates.mdx    |   66 +-
 .../logs/reference/change-notices/index.mdx   |    2 +-
 .../logs/reference/clientrequestsource.mdx    |    3 +
 src/content/docs/logs/reference/index.mdx     |    2 +-
 .../docs/logs/reference/security-fields.mdx   |    8 +-
 .../docs/logs/reference/waf-fields.mdx        |    8 +-
 src/content/docs/magic-transit/about.mdx      |    3 +-
 src/content/docs/magic-transit/alerts.mdx     |    3 +-
 .../docs/magic-transit/analytics/index.mdx    |    9 +-
 .../analytics/network-analytics.mdx           |    6 +-
 .../analytics/packet-captures.mdx             |    1 +
 .../analytics/query-bandwidth.mdx             |    5 +-
 .../analytics/query-tunnel-health.mdx         |    8 +-
 src/content/docs/magic-transit/changelog.mdx  |    5 +-
 .../docs/magic-transit/cloudflare-ips.mdx     |   17 +-
 .../docs/magic-transit/get-started.mdx        |    8 +-
 src/content/docs/magic-transit/glossary.mdx   |    3 +-
 .../how-to/advertise-prefixes.mdx             |   56 +-
 .../magic-transit/how-to/configure-routes.mdx |   18 +-
 .../how-to/configure-tunnel-endpoints.mdx     |   28 +-
 .../how-to/enable-magic-roles.mdx             |    2 +-
 .../docs/magic-transit/how-to/index.mdx       |    5 +-
 .../how-to/safely-withdraw-byoip-prefix.mdx   |    7 +-
 .../docs/magic-transit/network-flow.mdx       |    5 +-
 .../check-tunnel-health-dashboard.mdx         |   12 +-
 .../configure-tunnel-health-alerts.mdx        |    5 +-
 .../magic-transit/network-health/index.mdx    |   16 +-
 .../run-endpoint-health-checks.mdx            |   75 +-
 .../update-tunnel-health-checks-frequency.mdx |    7 +-
 .../magic-transit/network-interconnect.mdx    |    2 +-
 src/content/docs/magic-transit/on-demand.mdx  |    1 +
 .../docs/magic-transit/partners/index.mdx     |    5 +-
 .../reference/anti-replay-protection.mdx      |    3 +-
 .../reference/gre-ipsec-tunnels.mdx           |    3 +-
 ...dflare-calculates-tunnel-health-alerts.mdx |    9 +-
 .../docs/magic-transit/reference/index.mdx    |    5 +-
 .../docs/magic-transit/reference/mtu-mss.mdx  |    4 +-
 .../reference/traffic-steering.mdx            |    3 +-
 .../reference/tunnel-health-checks.mdx        |    5 +-
 .../troubleshooting/connectivity.mdx          |    5 +-
 .../magic-transit/troubleshooting/index.mdx   |    2 +-
 .../troubleshooting/ipsec-troubleshoot.mdx    |   12 +-
 .../troubleshooting/routing-and-bgp.mdx       |   21 +-
 .../troubleshooting/tunnel-health.mdx         |   29 +-
 src/content/docs/moq/feature-matrix.mdx       |  121 +-
 src/content/docs/moq/index.mdx                |   15 +-
 .../docs/multi-cloud-networking/changelog.mdx |    5 +-
 .../multi-cloud-networking/cloud-on-ramps.mdx |   11 +-
 .../multi-cloud-networking/get-started.mdx    |   74 +-
 .../manage-resources.mdx                      |    7 +-
 .../docs/multi-cloud-networking/reference.mdx |    1 +
 .../network-error-logging/get-started.mdx     |    3 +-
 .../docs/network-error-logging/how-to.mdx     |   11 +-
 .../docs/network-error-logging/index.mdx      |   45 +-
 src/content/docs/network-flow/api.mdx         |    5 +-
 src/content/docs/network-flow/changelog.mdx   |    5 +-
 .../docs/network-flow/cloud-flow-logs.mdx     |    2 +-
 src/content/docs/network-flow/faq.mdx         |    4 +-
 src/content/docs/network-flow/get-started.mdx |    2 +-
 src/content/docs/network-flow/glossary.mdx    |    3 +-
 .../magic-transit-integration.mdx             |    5 +-
 .../docs/network-flow/network-flow-free.mdx   |    2 +-
 .../docs/network-flow/routers/index.mdx       |    5 +-
 .../routers/netflow-ipfix-config.mdx          |    3 +-
 .../routers/recommended-sampling-rate.mdx     |    3 +-
 .../network-flow/routers/sflow-config.mdx     |    5 +-
 .../routers/supported-routers.mdx             |    5 +-
 src/content/docs/network-flow/rules/index.mdx |    1 +
 .../network-flow/rules/rule-notifications.mdx |    2 +-
 .../network-flow/rules/s-flow-ddos-attack.mdx |    2 +-
 .../network-flow/rules/static-threshold.mdx   |    2 +-
 .../tutorials/ddos-testing-guide.mdx          |    2 +-
 .../tutorials/encrypt-network-flow-data.mdx   |    5 +-
 .../tutorials/graphql-analytics.mdx           |    2 +-
 .../docs/network-flow/tutorials/index.mdx     |    5 +-
 .../docs/network-interconnect/changelog.mdx   |    5 +-
 .../docs/network-interconnect/get-started.mdx |   49 +-
 .../docs/network-interconnect/index.mdx       |   38 +-
 .../monitoring-and-alerts.mdx                 |   10 +-
 .../operational-guidance.mdx                  |    2 +-
 src/content/docs/network/index.mdx            |   36 +-
 src/content/docs/network/websockets.mdx       |    1 +
 .../get-started/configure-pagerduty.mdx       |   14 +-
 .../docs/notifications/get-started/index.mdx  |   27 +-
 src/content/docs/notifications/index.mdx      |    5 +-
 .../notifications/notification-available.mdx  |    2 +-
 .../notifications/notification-history.mdx    |    2 +-
 .../docs/notifications/reference/index.mdx    |    2 +-
 .../reference/traffic-alerts.mdx              |    2 +-
 src/content/docs/pages/configuration/api.mdx  |    1 -
 .../pages/configuration/build-caching.mdx     |   18 +-
 .../docs/pages/configuration/build-image.mdx  |    6 +-
 .../docs/pages/configuration/deploy-hooks.mdx |    1 -
 .../deploy-a-vite3-project.mdx                |    1 -
 .../docs/pages/functions/api-reference.mdx    |    8 +
 src/content/docs/pages/functions/bindings.mdx |   22 +-
 .../pages/functions/examples/ab-testing.mdx   |    1 +
 .../pages/functions/examples/cors-headers.mdx |    1 +
 .../docs/pages/functions/examples/index.mdx   |    1 +
 src/content/docs/pages/functions/metrics.mdx  |    1 -
 .../functions/plugins/community-plugins.mdx   |    1 +
 src/content/docs/pages/get-started/c3.mdx     |   23 +
 .../docs/pages/get-started/direct-upload.mdx  |    2 +-
 .../pages/get-started/git-integration.mdx     |    1 +
 src/content/docs/pages/get-started/index.mdx  |    1 +
 .../pages/how-to/add-custom-http-headers.mdx  |    1 +
 .../pages/how-to/build-commands-branches.mdx  |    2 +-
 .../pages/how-to/custom-branch-aliases.mdx    |    2 +-
 .../docs/pages/how-to/enable-zaraz.mdx        |    1 +
 src/content/docs/pages/how-to/index.mdx       |    2 +
 .../pages/how-to/npm-private-registry.mdx     |    1 +
 .../how-to/preview-with-cloudflare-tunnel.mdx |    1 +
 .../refactor-a-worker-to-pages-functions.mdx  |    1 +
 ...ect-upload-with-continuous-integration.mdx |    4 +-
 .../use-worker-for-ab-testing-in-pages.mdx    |    2 +-
 .../docs/pages/how-to/web-analytics.mdx       |    2 +-
 src/content/docs/pages/migrations/index.mdx   |    2 +
 src/content/docs/pages/platform/index.mdx     |    1 +
 .../docs/pages/platform/known-issues.mdx      |    3 +-
 src/content/docs/pages/platform/limits.mdx    |    7 +-
 .../add-a-react-form-with-formspree.mdx       |    2 +-
 .../build-a-blog-using-nuxt-and-sanity.mdx    |    1 -
 .../pipelines/reference/wrangler-commands.mdx |    3 +-
 .../docs/pipelines/sinks/manage-sinks.mdx     |    2 +-
 .../sql-reference/scalar-functions/string.mdx |    1 +
 .../docs/privacy-gateway/get-started.mdx      |   32 +-
 .../docs/privacy-gateway/reference/index.mdx  |    2 +-
 .../docs/privacy-gateway/reference/legal.mdx  |    4 +-
 .../privacy-gateway/reference/metrics.mdx     |  132 +-
 .../reference/product-compatibility.mdx       |    6 +-
 .../privacy-proxy/concepts/authentication.mdx |   12 +-
 .../concepts/deployment-models.mdx            |   26 +-
 .../privacy-proxy/concepts/geolocation.mdx    |   12 +-
 .../privacy-proxy/concepts/how-it-works.mdx   |   17 +-
 .../docs/privacy-proxy/get-started.mdx        |    2 +-
 .../privacy-proxy/reference/http-headers.mdx  |   32 +-
 .../privacy-proxy/reference/proxy-status.mdx  |   52 +-
 src/content/docs/pulumi/tutorial/index.mdx    |    3 +
 .../queues/configuration/configure-queues.mdx |   82 +-
 .../configuration/consumer-concurrency.mdx    |    2 +-
 .../docs/queues/configuration/index.mdx       |    2 +-
 .../queues/configuration/javascript-apis.mdx  |  243 ++--
 .../configuration/local-development.mdx       |    7 +-
 .../docs/queues/configuration/pause-purge.mdx |    6 -
 .../docs/queues/event-subscriptions/index.mdx |    4 +-
 .../manage-event-subscriptions.mdx            |    8 +-
 .../examples/publish-to-a-queue-via-http.mdx  |    1 +
 .../publish-to-a-queue-via-workers.mdx        |    5 +-
 .../queues/examples/send-errors-to-r2.mdx     |   50 +-
 .../examples/send-messages-from-dash.mdx      |    6 +-
 .../use-queues-with-durable-objects.mdx       |   68 +-
 src/content/docs/queues/glossary.mdx          |    2 +-
 .../docs/queues/observability/index.mdx       |    2 +-
 .../docs/queues/observability/metrics.mdx     |    8 +-
 src/content/docs/queues/platform/index.mdx    |    2 +-
 src/content/docs/queues/platform/limits.mdx   |   57 +-
 src/content/docs/queues/platform/pricing.mdx  |    9 +-
 .../queues/reference/delivery-guarantees.mdx  |    6 +-
 .../docs/queues/reference/error-codes.mdx     |   52 +-
 .../queues/reference/how-queues-works.mdx     |  148 +--
 src/content/docs/queues/reference/index.mdx   |    2 +-
 .../reference/limitations-best-practices.mdx  |   68 +-
 .../r2-sql/reference/wrangler-commands.mdx    |    2 +-
 .../docs/r2-sql/sql-reference/index.mdx       |   18 +-
 src/content/docs/r2/api/error-codes.mdx       |   88 +-
 src/content/docs/r2/api/index.mdx             |    2 +-
 src/content/docs/r2/api/s3/extensions.mdx     |   18 +-
 src/content/docs/r2/api/s3/presigned-urls.mdx |   11 +-
 .../docs/r2/api/s3/temporary-credentials.mdx  |   54 +-
 .../r2/api/workers/workers-api-reference.mdx  |   78 +-
 .../docs/r2/api/workers/workers-api-usage.mdx |    1 -
 src/content/docs/r2/buckets/bucket-locks.mdx  |    3 -
 src/content/docs/r2/buckets/cors.mdx          |   45 +-
 .../docs/r2/buckets/delete-buckets.mdx        |   26 +-
 .../docs/r2/buckets/event-notifications.mdx   |   33 +-
 src/content/docs/r2/buckets/index.mdx         |    2 +-
 .../docs/r2/buckets/object-lifecycles.mdx     |    2 -
 .../docs/r2/buckets/storage-classes.mdx       |   32 +-
 src/content/docs/r2/data-migration/index.mdx  |    2 +-
 .../data-migration/migration-strategies.mdx   |    2 +-
 src/content/docs/r2/data-migration/sippy.mdx  |   18 +-
 .../docs/r2/data-migration/super-slurper.mdx  |    7 +-
 .../examples/authenticate-r2-auth-tokens.mdx  |    2 +-
 .../authenticate-r2-temp-credentials.mdx      |  174 +--
 .../docs/r2/examples/aws/aws-sdk-js-v3.mdx    |   19 +-
 .../docs/r2/examples/aws/aws-sdk-js.mdx       |   25 +-
 .../docs/r2/examples/aws/aws-sdk-kotlin.mdx   |    1 +
 .../docs/r2/examples/aws/aws4fetch.mdx        |   15 +-
 src/content/docs/r2/examples/aws/boto3.mdx    |   15 +-
 .../docs/r2/examples/aws/custom-header.mdx    |   95 +-
 src/content/docs/r2/examples/cache-api.mdx    |  109 +-
 src/content/docs/r2/examples/terraform.mdx    |    7 +-
 src/content/docs/r2/get-started/cli.mdx       |    9 +-
 src/content/docs/r2/get-started/index.mdx     |    1 -
 src/content/docs/r2/get-started/s3.mdx        |    9 +-
 .../docs/r2/get-started/workers-api.mdx       |    2 +-
 .../docs/r2/objects/delete-objects.mdx        |   19 +-
 .../docs/r2/objects/download-objects.mdx      |    3 +-
 src/content/docs/r2/objects/index.mdx         |    4 +-
 src/content/docs/r2/platform/audit-logs.mdx   |   59 +-
 .../docs/r2/platform/metrics-analytics.mdx    |    7 +-
 .../docs/r2/platform/troubleshooting.mdx      |    5 +-
 src/content/docs/r2/pricing.mdx               |   52 +-
 src/content/docs/r2/r2-sql.mdx                |    2 +-
 .../docs/r2/reference/data-location.mdx       |    2 -
 .../docs/r2/reference/data-security.mdx       |    2 +
 src/content/docs/r2/reference/durability.mdx  |   10 +-
 .../r2/reference/unicode-interoperability.mdx |    6 +-
 .../docs/r2/tutorials/cloudflare-access.mdx   |    2 +-
 src/content/docs/r2/tutorials/mastodon.mdx    |    3 +-
 src/content/docs/r2/tutorials/postman.mdx     |   12 +-
 src/content/docs/r2/video-tutorials.mdx       |   10 +-
 src/content/docs/radar/concepts/index.mdx     |    2 +-
 .../docs/radar/concepts/normalization.mdx     |    2 +-
 .../radar/get-started/configure-alerts.mdx    |    2 +-
 src/content/docs/radar/get-started/embed.mdx  |    4 +-
 src/content/docs/radar/get-started/index.mdx  |    2 +-
 .../radar/get-started/making-comparisons.mdx  |   78 +-
 .../investigate/application-layer-attacks.mdx |   84 +-
 src/content/docs/radar/investigate/dns.mdx    |   26 +-
 .../investigate/domain-ranking-datasets.mdx   |   37 +-
 .../docs/radar/investigate/http-requests.mdx  |   76 +-
 src/content/docs/radar/investigate/index.mdx  |    2 +-
 .../docs/radar/investigate/netflows.mdx       |   18 +-
 .../investigate/network-layer-attacks.mdx     |   86 +-
 .../docs/radar/investigate/outages.mdx        |   14 +-
 .../docs/radar/investigate/url-scanner.mdx    |   88 +-
 src/content/docs/radar/mcp-server.mdx         |    2 +-
 src/content/docs/radar/reference/index.mdx    |    2 +-
 .../reference/quarterly-ddos-reports.mdx      |    6 +-
 .../randomness-beacon/about/background.mdx    |    2 +-
 .../docs/randomness-beacon/about/future.mdx   |    6 +-
 .../cryptographic-background/index.mdx        |    6 +-
 .../randomness-generation.mdx                 |    6 +-
 .../cryptographic-background/setup-phase.mdx  |    4 +-
 src/content/docs/realtime/agents/index.mdx    |    4 +-
 .../docs/realtime/realtimekit/ai/index.mdx    |    2 +-
 .../docs/realtime/realtimekit/ai/summary.mdx  |   69 +-
 .../realtime/realtimekit/ai/transcription.mdx |    2 +-
 .../realtimekit/core/api-reference/RTKAi.md   |   40 +-
 .../realtimekit/core/api-reference/RTKChat.md |  329 +++--
 .../api-reference/RTKConnectedMeetings.md     |   81 +-
 .../core/api-reference/RTKLivestream.md       |   46 +-
 .../realtimekit/core/api-reference/RTKMeta.md |   68 +-
 .../core/api-reference/RTKParticipant.md      |  188 ++-
 .../core/api-reference/RTKParticipantMap.md   |   56 +-
 .../core/api-reference/RTKParticipants.md     |  240 ++--
 .../api-reference/RTKPermissionsPreset.md     |  143 +--
 .../realtimekit/core/api-reference/RTKPip.md  |   72 +-
 .../core/api-reference/RTKPlugin.md           |  122 +-
 .../core/api-reference/RTKPlugins.md          |   21 +-
 .../core/api-reference/RTKPolls.md            |   33 +-
 .../core/api-reference/RTKRecording.md        |   20 +-
 .../realtimekit/core/api-reference/RTKSelf.md |  109 +-
 .../core/api-reference/RTKSelfMedia.md        |   77 +-
 .../core/api-reference/RTKStage.md            |   63 +-
 .../core/api-reference/RTKStore.md            |  167 ++-
 .../core/api-reference/RTKThemePreset.md      |   89 +-
 .../core/api-reference/RealtimeKitClient.md   |  129 +-
 .../realtime/realtimekit/legal/3rdparty.mdx   |   99 +-
 .../recording-guide/add-watermark.mdx         |   20 +-
 .../recording-guide/configure-codecs.mdx      |    6 +-
 .../realtimekit/recording-guide/index.mdx     |    2 +-
 .../recording-guide/monitor-status.mdx        |   12 +-
 .../ui-kit/api-reference/angular/index.mdx    |    2 +-
 .../api-reference/angular/rtk-ai-toggle.mdx   |   24 +-
 .../angular/rtk-ai-transcriptions.mdx         |   16 +-
 .../ui-kit/api-reference/angular/rtk-ai.mdx   |   26 +-
 .../api-reference/angular/rtk-audio-grid.mdx  |   27 +-
 .../api-reference/angular/rtk-audio-tile.mdx  |   27 +-
 .../angular/rtk-audio-visualizer.mdx          |   29 +-
 .../api-reference/angular/rtk-avatar.mdx      |   22 +-
 .../angular/rtk-breakout-room-manager.mdx     |   33 +-
 .../rtk-breakout-room-participants.mdx        |   25 +-
 .../angular/rtk-breakout-rooms-manager.mdx    |   18 +-
 .../angular/rtk-breakout-rooms-toggle.mdx     |   27 +-
 .../angular/rtk-broadcast-message-modal.mdx   |   18 +-
 .../api-reference/angular/rtk-button.mdx      |   23 +-
 .../angular/rtk-camera-selector.mdx           |   40 +-
 .../angular/rtk-camera-toggle.mdx             |   21 +-
 .../angular/rtk-caption-toggle.mdx            |   25 +-
 .../angular/rtk-chat-composer-ui.mdx          |   25 +-
 .../angular/rtk-chat-composer-view.mdx        |   35 +-
 .../api-reference/angular/rtk-chat-header.mdx |    4 +-
 .../angular/rtk-chat-message.mdx              |   45 +-
 .../rtk-chat-messages-ui-paginated.mdx        |   23 +-
 .../angular/rtk-chat-messages-ui.mdx          |   27 +-
 .../angular/rtk-chat-search-results.mdx       |   23 +-
 .../angular/rtk-chat-selector-ui.mdx          |   25 +-
 .../angular/rtk-chat-selector.mdx             |   25 +-
 .../api-reference/angular/rtk-chat-toggle.mdx |   37 +-
 .../ui-kit/api-reference/angular/rtk-chat.mdx |   23 +-
 .../api-reference/angular/rtk-clock.mdx       |   17 +-
 .../angular/rtk-confirmation-modal.mdx        |   18 +-
 .../angular/rtk-controlbar-button.mdx         |   29 +-
 .../api-reference/angular/rtk-controlbar.mdx  |   27 +-
 .../api-reference/angular/rtk-counter.mdx     |   22 +-
 .../angular/rtk-debugger-audio.mdx            |   21 +-
 .../angular/rtk-debugger-screenshare.mdx      |   20 +-
 .../angular/rtk-debugger-system.mdx           |   21 +-
 .../angular/rtk-debugger-toggle.mdx           |   23 +-
 .../angular/rtk-debugger-video.mdx            |   21 +-
 .../api-reference/angular/rtk-debugger.mdx    |   21 +-
 .../angular/rtk-dialog-manager.mdx            |   36 +-
 .../api-reference/angular/rtk-dialog.mdx      |   31 +-
 .../angular/rtk-emoji-picker-button.mdx       |   16 +-
 .../angular/rtk-emoji-picker.mdx              |   16 +-
 .../angular/rtk-ended-screen.mdx              |   23 +-
 .../angular/rtk-file-dropzone.mdx             |   16 +-
 .../angular/rtk-file-message-view.mdx         |   19 +-
 .../angular/rtk-file-message.mdx              |   25 +-
 .../angular/rtk-file-picker-button.mdx        |   23 +-
 .../angular/rtk-fullscreen-toggle.mdx         |   25 +-
 .../angular/rtk-grid-pagination.mdx           |   27 +-
 .../ui-kit/api-reference/angular/rtk-grid.mdx |   34 +-
 .../api-reference/angular/rtk-header.mdx      |   28 +-
 .../ui-kit/api-reference/angular/rtk-icon.mdx |   18 +-
 .../api-reference/angular/rtk-idle-screen.mdx |   20 +-
 .../angular/rtk-image-message-view.mdx        |   16 +-
 .../angular/rtk-image-message.mdx             |   25 +-
 .../angular/rtk-image-viewer.mdx              |   19 +-
 .../angular/rtk-information-tooltip.mdx       |   11 +-
 .../api-reference/angular/rtk-join-stage.mdx  |   25 +-
 .../angular/rtk-leave-button.mdx              |   19 +-
 .../angular/rtk-leave-meeting.mdx             |   20 +-
 .../angular/rtk-livestream-indicator.mdx      |   18 +-
 .../angular/rtk-livestream-player.mdx         |   19 +-
 .../angular/rtk-livestream-toggle.mdx         |   21 +-
 .../ui-kit/api-reference/angular/rtk-logo.mdx |   19 +-
 .../angular/rtk-markdown-view.mdx             |   15 +-
 .../angular/rtk-meeting-title.mdx             |   16 +-
 .../api-reference/angular/rtk-meeting.mdx     |   43 +-
 .../api-reference/angular/rtk-menu-item.mdx   |   18 +-
 .../api-reference/angular/rtk-menu-list.mdx   |   16 +-
 .../ui-kit/api-reference/angular/rtk-menu.mdx |   22 +-
 .../angular/rtk-message-list-view.mdx         |   25 +-
 .../angular/rtk-message-view.mdx              |   39 +-
 .../api-reference/angular/rtk-mic-toggle.mdx  |   21 +-
 .../angular/rtk-microphone-selector.mdx       |   40 +-
 .../api-reference/angular/rtk-mixed-grid.mdx  |   40 +-
 .../api-reference/angular/rtk-more-toggle.mdx |   29 +-
 .../angular/rtk-mute-all-button.mdx           |   21 +-
 .../angular/rtk-mute-all-confirmation.mdx     |   18 +-
 .../api-reference/angular/rtk-name-tag.mdx    |   27 +-
 .../angular/rtk-network-indicator.mdx         |   23 +-
 .../angular/rtk-notification.mdx              |   25 +-
 .../angular/rtk-notifications.mdx             |   27 +-
 .../angular/rtk-overlay-modal.mdx             |   18 +-
 .../angular/rtk-paginated-list.mdx            |   33 +-
 .../angular/rtk-participant-count.mdx         |   19 +-
 .../angular/rtk-participant-setup.mdx         |   31 +-
 .../angular/rtk-participant-tile.mdx          |   37 +-
 .../api-reference/angular/rtk-participant.mdx |   31 +-
 .../angular/rtk-participants-audio.mdx        |   19 +-
 .../angular/rtk-participants-stage-list.mdx   |   33 +-
 .../angular/rtk-participants-stage-queue.mdx  |   25 +-
 .../angular/rtk-participants-toggle.mdx       |   35 +-
 .../angular/rtk-participants-viewer-list.mdx  |   29 +-
 .../angular/rtk-participants-waiting-list.mdx |   25 +-
 .../angular/rtk-participants.mdx              |   29 +-
 .../angular/rtk-permissions-message.mdx       |   20 +-
 .../angular/rtk-pinned-message-selector.mdx   |   16 +-
 .../api-reference/angular/rtk-pip-toggle.mdx  |   25 +-
 .../api-reference/angular/rtk-plugin-main.mdx |   19 +-
 .../angular/rtk-plugins-toggle.mdx            |   35 +-
 .../api-reference/angular/rtk-plugins.mdx     |   23 +-
 .../api-reference/angular/rtk-poll-form.mdx   |   15 +-
 .../ui-kit/api-reference/angular/rtk-poll.mdx |   23 +-
 .../angular/rtk-polls-toggle.mdx              |   37 +-
 .../api-reference/angular/rtk-polls.mdx       |   23 +-
 .../angular/rtk-recording-indicator.mdx       |   20 +-
 .../angular/rtk-recording-toggle.mdx          |   29 +-
 .../angular/rtk-screen-share-toggle.mdx       |   23 +-
 .../angular/rtk-screenshare-view.mdx          |   35 +-
 .../angular/rtk-settings-audio.mdx            |   38 +-
 .../angular/rtk-settings-toggle.mdx           |   32 +-
 .../angular/rtk-settings-video.mdx            |   38 +-
 .../api-reference/angular/rtk-settings.mdx    |   23 +-
 .../angular/rtk-setup-screen.mdx              |   25 +-
 .../api-reference/angular/rtk-sidebar-ui.mdx  |   29 +-
 .../api-reference/angular/rtk-sidebar.mdx     |   33 +-
 .../api-reference/angular/rtk-simple-grid.mdx |   29 +-
 .../angular/rtk-speaker-selector.mdx          |   42 +-
 .../api-reference/angular/rtk-spinner.mdx     |   14 +-
 .../angular/rtk-spotlight-grid.mdx            |   42 +-
 .../angular/rtk-spotlight-indicator.mdx       |   18 +-
 .../angular/rtk-stage-toggle.mdx              |   23 +-
 .../api-reference/angular/rtk-stage.mdx       |   17 +-
 .../api-reference/angular/rtk-switch.mdx      |   22 +-
 .../api-reference/angular/rtk-tab-bar.mdx     |   29 +-
 .../angular/rtk-text-composer-view.mdx        |   31 +-
 .../angular/rtk-text-message-view.mdx         |   14 +-
 .../angular/rtk-text-message.mdx              |   25 +-
 .../api-reference/angular/rtk-tooltip.mdx     |   28 +-
 .../api-reference/angular/rtk-transcript.mdx  |   19 +-
 .../api-reference/angular/rtk-transcripts.mdx |   22 +-
 .../api-reference/angular/rtk-ui-provider.mdx |   27 +-
 .../angular/rtk-viewer-count.mdx              |   19 +-
 .../rtk-virtualized-participant-list.mdx      |   23 +-
 .../angular/rtk-waiting-screen.mdx            |   18 +-
 .../ui-kit/api-reference/core/index.mdx       |    2 +-
 .../core/rtk-ai-transcriptions.mdx            |   21 +-
 .../ui-kit/api-reference/core/rtk-ai.mdx      |   28 +-
 .../api-reference/core/rtk-audio-grid.mdx     |   31 +-
 .../api-reference/core/rtk-audio-tile.mdx     |   31 +-
 .../core/rtk-audio-visualizer.mdx             |   33 +-
 .../ui-kit/api-reference/core/rtk-avatar.mdx  |   26 +-
 .../core/rtk-breakout-room-manager.mdx        |   37 +-
 .../core/rtk-breakout-room-participants.mdx   |   31 +-
 .../core/rtk-breakout-rooms-manager.mdx       |   21 +-
 .../core/rtk-breakout-rooms-toggle.mdx        |   30 +-
 .../core/rtk-broadcast-message-modal.mdx      |   21 +-
 .../ui-kit/api-reference/core/rtk-button.mdx  |   27 +-
 .../core/rtk-camera-selector.mdx              |   41 +-
 .../core/rtk-chat-composer-ui.mdx             |   28 +-
 .../core/rtk-chat-composer-view.mdx           |   37 +-
 .../api-reference/core/rtk-chat-header.mdx    |    4 +-
 .../api-reference/core/rtk-chat-message.mdx   |   51 +-
 .../core/rtk-chat-messages-ui-paginated.mdx   |   24 +-
 .../core/rtk-chat-messages-ui.mdx             |   30 +-
 .../core/rtk-chat-search-results.mdx          |   24 +-
 .../core/rtk-chat-selector-ui.mdx             |   26 +-
 .../api-reference/core/rtk-chat-selector.mdx  |   28 +-
 .../ui-kit/api-reference/core/rtk-chat.mdx    |   26 +-
 .../ui-kit/api-reference/core/rtk-clock.mdx   |   20 +-
 .../core/rtk-confirmation-modal.mdx           |   21 +-
 .../core/rtk-controlbar-button.mdx            |   34 +-
 .../api-reference/core/rtk-controlbar.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-counter.mdx |   26 +-
 .../api-reference/core/rtk-debugger-audio.mdx |   24 +-
 .../core/rtk-debugger-screenshare.mdx         |   24 +-
 .../core/rtk-debugger-system.mdx              |   24 +-
 .../api-reference/core/rtk-debugger-video.mdx |   24 +-
 .../api-reference/core/rtk-debugger.mdx       |   24 +-
 .../api-reference/core/rtk-dialog-manager.mdx |   39 +-
 .../ui-kit/api-reference/core/rtk-dialog.mdx  |   35 +-
 .../core/rtk-draft-attachment-view.mdx        |   19 +-
 .../core/rtk-emoji-picker-button.mdx          |   19 +-
 .../api-reference/core/rtk-emoji-picker.mdx   |   19 +-
 .../api-reference/core/rtk-ended-screen.mdx   |   26 +-
 .../api-reference/core/rtk-file-dropzone.mdx  |   18 +-
 .../core/rtk-file-message-view.mdx            |   23 +-
 .../api-reference/core/rtk-file-message.mdx   |   27 +-
 .../core/rtk-file-picker-button.mdx           |   24 +-
 .../core/rtk-grid-pagination.mdx              |   28 +-
 .../ui-kit/api-reference/core/rtk-grid.mdx    |   37 +-
 .../ui-kit/api-reference/core/rtk-header.mdx  |   32 +-
 .../ui-kit/api-reference/core/rtk-icon.mdx    |   21 +-
 .../api-reference/core/rtk-idle-screen.mdx    |   23 +-
 .../core/rtk-image-message-view.mdx           |   19 +-
 .../api-reference/core/rtk-image-message.mdx  |   27 +-
 .../api-reference/core/rtk-image-viewer.mdx   |   21 +-
 .../core/rtk-information-tooltip.mdx          |   15 +-
 .../api-reference/core/rtk-join-stage.mdx     |   28 +-
 .../api-reference/core/rtk-leave-meeting.mdx  |   23 +-
 .../core/rtk-livestream-indicator.mdx         |   22 +-
 .../core/rtk-livestream-player.mdx            |   22 +-
 .../ui-kit/api-reference/core/rtk-logo.mdx    |   22 +-
 .../api-reference/core/rtk-markdown-view.mdx  |   18 +-
 .../api-reference/core/rtk-meeting-title.mdx  |   19 +-
 .../ui-kit/api-reference/core/rtk-meeting.mdx |   45 +-
 .../api-reference/core/rtk-menu-item.mdx      |   21 +-
 .../api-reference/core/rtk-menu-list.mdx      |   18 +-
 .../ui-kit/api-reference/core/rtk-menu.mdx    |   24 +-
 .../core/rtk-message-list-view.mdx            |   27 +-
 .../api-reference/core/rtk-message-view.mdx   |   43 +-
 .../core/rtk-microphone-selector.mdx          |   41 +-
 .../api-reference/core/rtk-mixed-grid.mdx     |   43 +-
 .../api-reference/core/rtk-more-toggle.mdx    |   32 +-
 .../core/rtk-mute-all-confirmation.mdx        |   21 +-
 .../api-reference/core/rtk-name-tag.mdx       |   31 +-
 .../core/rtk-network-indicator.mdx            |   27 +-
 .../api-reference/core/rtk-notification.mdx   |   28 +-
 .../api-reference/core/rtk-notifications.mdx  |   30 +-
 .../api-reference/core/rtk-overlay-modal.mdx  |   21 +-
 .../api-reference/core/rtk-paginated-list.mdx |   36 +-
 .../core/rtk-participant-count.mdx            |   22 +-
 .../core/rtk-participant-setup.mdx            |   33 +-
 .../core/rtk-participant-tile.mdx             |   37 +-
 .../api-reference/core/rtk-participant.mdx    |   33 +-
 .../core/rtk-participants-audio.mdx           |   21 +-
 .../core/rtk-participants-stage-list.mdx      |   36 +-
 .../core/rtk-participants-stage-queue.mdx     |   26 +-
 .../core/rtk-participants-viewer-list.mdx     |   32 +-
 .../core/rtk-participants-waiting-list.mdx    |   26 +-
 .../api-reference/core/rtk-participants.mdx   |   30 +-
 .../core/rtk-permissions-message.mdx          |   23 +-
 .../core/rtk-pinned-message-selector.mdx      |   19 +-
 .../api-reference/core/rtk-plugin-main.mdx    |   21 +-
 .../ui-kit/api-reference/core/rtk-plugins.mdx |   26 +-
 .../api-reference/core/rtk-poll-form.mdx      |   17 +-
 .../ui-kit/api-reference/core/rtk-poll.mdx    |   25 +-
 .../ui-kit/api-reference/core/rtk-polls.mdx   |   26 +-
 .../core/rtk-recording-indicator.mdx          |   24 +-
 .../core/rtk-recording-toggle.mdx             |   34 +-
 .../core/rtk-screenshare-view.mdx             |   35 +-
 .../api-reference/core/rtk-settings-audio.mdx |   41 +-
 .../api-reference/core/rtk-settings-video.mdx |   41 +-
 .../api-reference/core/rtk-settings.mdx       |   26 +-
 .../api-reference/core/rtk-setup-screen.mdx   |   28 +-
 .../api-reference/core/rtk-sidebar-ui.mdx     |   32 +-
 .../ui-kit/api-reference/core/rtk-sidebar.mdx |   35 +-
 .../api-reference/core/rtk-simple-grid.mdx    |   34 +-
 .../core/rtk-speaker-selector.mdx             |   43 +-
 .../ui-kit/api-reference/core/rtk-spinner.mdx |   17 +-
 .../api-reference/core/rtk-spotlight-grid.mdx |   46 +-
 .../core/rtk-spotlight-indicator.mdx          |   22 +-
 .../ui-kit/api-reference/core/rtk-stage.mdx   |   19 +-
 .../ui-kit/api-reference/core/rtk-switch.mdx  |   27 +-
 .../ui-kit/api-reference/core/rtk-tab-bar.mdx |   31 +-
 .../core/rtk-text-composer-view.mdx           |   33 +-
 .../core/rtk-text-message-view.mdx            |   18 +-
 .../api-reference/core/rtk-text-message.mdx   |   27 +-
 .../ui-kit/api-reference/core/rtk-tooltip.mdx |   31 +-
 .../api-reference/core/rtk-transcript.mdx     |   22 +-
 .../api-reference/core/rtk-transcripts.mdx    |   25 +-
 .../api-reference/core/rtk-ui-provider.mdx    |   31 +-
 .../api-reference/core/rtk-viewer-count.mdx   |   22 +-
 .../core/rtk-virtualized-participant-list.mdx |   25 +-
 .../api-reference/core/rtk-waiting-screen.mdx |   21 +-
 .../react-native/RtkMenuItem.mdx              |   10 +-
 .../ui-kit/api-reference/react/RtkAi.mdx      |   34 +-
 .../api-reference/react/RtkAiToggle.mdx       |   32 +-
 .../react/RtkAiTranscriptions.mdx             |   25 +-
 .../api-reference/react/RtkAudioGrid.mdx      |   36 +-
 .../api-reference/react/RtkAudioTile.mdx      |   40 +-
 .../react/RtkAudioVisualizer.mdx              |   42 +-
 .../ui-kit/api-reference/react/RtkAvatar.mdx  |   30 +-
 .../react/RtkBreakoutRoomManager.mdx          |   46 +-
 .../react/RtkBreakoutRoomParticipants.mdx     |   38 +-
 .../react/RtkBreakoutRoomsManager.mdx         |   26 +-
 .../react/RtkBreakoutRoomsToggle.mdx          |   40 +-
 .../react/RtkBroadcastMessageModal.mdx        |   26 +-
 .../ui-kit/api-reference/react/RtkButton.mdx  |   32 +-
 .../api-reference/react/RtkCameraSelector.mdx |   53 +-
 .../api-reference/react/RtkCameraToggle.mdx   |   30 +-
 .../api-reference/react/RtkCaptionToggle.mdx  |   34 +-
 .../ui-kit/api-reference/react/RtkChat.mdx    |   31 +-
 .../api-reference/react/RtkChatComposerUi.mdx |   38 +-
 .../react/RtkChatComposerView.mdx             |   48 +-
 .../api-reference/react/RtkChatHeader.mdx     |    8 +-
 .../api-reference/react/RtkChatMessage.mdx    |   54 +-
 .../api-reference/react/RtkChatMessagesUi.mdx |   40 +-
 .../react/RtkChatMessagesUiPaginated.mdx      |   36 +-
 .../react/RtkChatSearchResults.mdx            |   36 +-
 .../api-reference/react/RtkChatSelector.mdx   |   33 +-
 .../api-reference/react/RtkChatSelectorUi.mdx |   38 +-
 .../api-reference/react/RtkChatToggle.mdx     |   46 +-
 .../ui-kit/api-reference/react/RtkClock.mdx   |   25 +-
 .../react/RtkConfirmationModal.mdx            |   26 +-
 .../api-reference/react/RtkControlbar.mdx     |   36 +-
 .../react/RtkControlbarButton.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkCounter.mdx |   30 +-
 .../api-reference/react/RtkDebugger.mdx       |   29 +-
 .../api-reference/react/RtkDebuggerAudio.mdx  |   29 +-
 .../react/RtkDebuggerScreenshare.mdx          |   29 +-
 .../api-reference/react/RtkDebuggerSystem.mdx |   29 +-
 .../api-reference/react/RtkDebuggerToggle.mdx |   32 +-
 .../api-reference/react/RtkDebuggerVideo.mdx  |   29 +-
 .../ui-kit/api-reference/react/RtkDialog.mdx  |   44 +-
 .../api-reference/react/RtkDialogManager.mdx  |   44 +-
 .../react/RtkDraftAttachmentView.mdx          |   24 +-
 .../api-reference/react/RtkEmojiPicker.mdx    |   24 +-
 .../react/RtkEmojiPickerButton.mdx            |   24 +-
 .../api-reference/react/RtkEndedScreen.mdx    |   31 +-
 .../api-reference/react/RtkFileDropzone.mdx   |   24 +-
 .../api-reference/react/RtkFileMessage.mdx    |   34 +-
 .../react/RtkFileMessageView.mdx              |   28 +-
 .../react/RtkFilePickerButton.mdx             |   36 +-
 .../react/RtkFullscreenToggle.mdx             |   40 +-
 .../ui-kit/api-reference/react/RtkGrid.mdx    |   42 +-
 .../api-reference/react/RtkGridPagination.mdx |   40 +-
 .../ui-kit/api-reference/react/RtkHeader.mdx  |   36 +-
 .../ui-kit/api-reference/react/RtkIcon.mdx    |   26 +-
 .../api-reference/react/RtkIdleScreen.mdx     |   28 +-
 .../api-reference/react/RtkImageMessage.mdx   |   36 +-
 .../react/RtkImageMessageView.mdx             |   24 +-
 .../api-reference/react/RtkImageViewer.mdx    |   27 +-
 .../react/RtkInformationTooltip.mdx           |   20 +-
 .../api-reference/react/RtkJoinStage.mdx      |   36 +-
 .../api-reference/react/RtkLeaveButton.mdx    |   27 +-
 .../api-reference/react/RtkLeaveMeeting.mdx   |   28 +-
 .../react/RtkLivestreamIndicator.mdx          |   27 +-
 .../react/RtkLivestreamPlayer.mdx             |   27 +-
 .../react/RtkLivestreamToggle.mdx             |   30 +-
 .../ui-kit/api-reference/react/RtkLogo.mdx    |   27 +-
 .../api-reference/react/RtkMarkdownView.mdx   |   23 +-
 .../ui-kit/api-reference/react/RtkMeeting.mdx |   56 +-
 .../api-reference/react/RtkMeetingTitle.mdx   |   24 +-
 .../ui-kit/api-reference/react/RtkMenu.mdx    |   30 +-
 .../api-reference/react/RtkMenuItem.mdx       |   27 +-
 .../api-reference/react/RtkMenuList.mdx       |   24 +-
 .../api-reference/react/RtkMessageView.mdx    |   50 +-
 .../api-reference/react/RtkMicToggle.mdx      |   30 +-
 .../react/RtkMicrophoneSelector.mdx           |   53 +-
 .../api-reference/react/RtkMixedGrid.mdx      |   48 +-
 .../api-reference/react/RtkMoreToggle.mdx     |   37 +-
 .../api-reference/react/RtkMuteAllButton.mdx  |   30 +-
 .../react/RtkMuteAllConfirmation.mdx          |   26 +-
 .../ui-kit/api-reference/react/RtkNameTag.mdx |   40 +-
 .../react/RtkNetworkIndicator.mdx             |   36 +-
 .../api-reference/react/RtkNotification.mdx   |   36 +-
 .../api-reference/react/RtkNotifications.mdx  |   35 +-
 .../api-reference/react/RtkOverlayModal.mdx   |   26 +-
 .../api-reference/react/RtkPaginatedList.mdx  |   46 +-
 .../api-reference/react/RtkParticipant.mdx    |   44 +-
 .../react/RtkParticipantCount.mdx             |   27 +-
 .../api-reference/react/RtkParticipants.mdx   |   42 +-
 .../react/RtkParticipantsAudio.mdx            |   32 +-
 .../react/RtkParticipantsStageList.mdx        |   46 +-
 .../react/RtkParticipantsStageQueue.mdx       |   38 +-
 .../react/RtkParticipantsToggle.mdx           |   44 +-
 .../react/RtkParticipantsViewerList.mdx       |   42 +-
 .../react/RtkParticipantsWaitingList.mdx      |   38 +-
 .../react/RtkPermissionsMessage.mdx           |   28 +-
 .../react/RtkPinnedMessageSelector.mdx        |   24 +-
 .../api-reference/react/RtkPipToggle.mdx      |   34 +-
 .../api-reference/react/RtkPluginMain.mdx     |   27 +-
 .../ui-kit/api-reference/react/RtkPlugins.mdx |   31 +-
 .../api-reference/react/RtkPluginsToggle.mdx  |   44 +-
 .../ui-kit/api-reference/react/RtkPoll.mdx    |   34 +-
 .../api-reference/react/RtkPollForm.mdx       |   23 +-
 .../ui-kit/api-reference/react/RtkPolls.mdx   |   31 +-
 .../api-reference/react/RtkPollsToggle.mdx    |   46 +-
 .../react/RtkRecordingIndicator.mdx           |   29 +-
 .../react/RtkRecordingToggle.mdx              |   38 +-
 .../react/RtkScreenShareToggle.mdx            |   32 +-
 .../api-reference/react/RtkSettings.mdx       |   31 +-
 .../api-reference/react/RtkSettingsAudio.mdx  |   46 +-
 .../api-reference/react/RtkSettingsToggle.mdx |   40 +-
 .../api-reference/react/RtkSettingsVideo.mdx  |   46 +-
 .../api-reference/react/RtkSetupScreen.mdx    |   33 +-
 .../ui-kit/api-reference/react/RtkSidebar.mdx |   46 +-
 .../api-reference/react/RtkSidebarUi.mdx      |   42 +-
 .../api-reference/react/RtkSimpleGrid.mdx     |   38 +-
 .../react/RtkSpeakerSelector.mdx              |   55 +-
 .../ui-kit/api-reference/react/RtkSpinner.mdx |   22 +-
 .../api-reference/react/RtkSpotlightGrid.mdx  |   51 +-
 .../react/RtkSpotlightIndicator.mdx           |   27 +-
 .../ui-kit/api-reference/react/RtkStage.mdx   |   25 +-
 .../api-reference/react/RtkStageToggle.mdx    |   32 +-
 .../ui-kit/api-reference/react/RtkSwitch.mdx  |   30 +-
 .../ui-kit/api-reference/react/RtkTabBar.mdx  |   38 +-
 .../api-reference/react/RtkTextMessage.mdx    |   34 +-
 .../react/RtkTextMessageView.mdx              |   23 +-
 .../ui-kit/api-reference/react/RtkTooltip.mdx |   36 +-
 .../api-reference/react/RtkTranscript.mdx     |   27 +-
 .../api-reference/react/RtkTranscripts.mdx    |   30 +-
 .../api-reference/react/RtkUiProvider.mdx     |   40 +-
 .../api-reference/react/RtkViewerCount.mdx    |   27 +-
 .../react/RtkVirtualizedParticipantList.mdx   |   36 +-
 .../api-reference/react/RtkWaitingScreen.mdx  |   26 +-
 .../ui-kit/api-reference/react/index.mdx      |    2 +-
 .../docs/realtime/sfu/calls-vs-sfus.mdx       |    7 +-
 src/content/docs/realtime/sfu/changelog.mdx   |    2 +-
 .../docs/realtime/sfu/datachannels.mdx        |    2 +-
 src/content/docs/realtime/sfu/get-started.mdx |    6 +-
 src/content/docs/realtime/sfu/limits.mdx      |   33 +-
 .../sfu/media-transport-adapters/index.mdx    |    1 -
 .../websocket-adapter.mdx                     |   25 +-
 .../docs/realtime/sfu/sessions-tracks.mdx     |   20 +-
 .../docs/realtime/turn/custom-domains.mdx     |   10 +-
 .../realtime/turn/generate-credentials.mdx    |   35 +-
 .../docs/realtime/turn/replacing-existing.mdx |   20 +-
 src/content/docs/realtime/turn/rfc-matrix.mdx |   30 +-
 .../architectures/sase.mdx                    |   18 +-
 .../architectures/security.mdx                |    2 +-
 .../designing-ztna-access-policies.mdx        |   18 +-
 ...nefits-to-saas-providers-end-customers.mdx |   16 +-
 .../diagrams/ai/index.mdx                     |    2 +-
 .../diagrams/content-delivery/index.mdx       |    2 +-
 ...uring-connected-transportation-systems.mdx |   17 +-
 .../diagrams/network/index.mdx                |    2 +-
 .../diagrams/sase/index.mdx                   |    2 +-
 .../diagrams/security/index.mdx               |    2 +-
 .../serverless/fullstack-application.mdx      |   27 +-
 .../diagrams/serverless/index.mdx             |    2 +-
 .../serverless/programmable-platforms.mdx     |    1 +
 .../diagrams/storage/index.mdx                |    2 +-
 .../implementation-guides/index.mdx           |    2 +-
 .../zero-trust/index.mdx                      |    2 +-
 .../domain-contact-updates.mdx                |   26 +-
 .../account-options/domain-management.mdx     |   18 +-
 .../account-options/icloud-domains.mdx        |   24 +-
 .../docs/registrar/account-options/index.mdx  |    2 +-
 .../inter-account-transfer.mdx                |   31 +-
 .../account-options/renew-domains.mdx         |   22 +-
 .../transfer-out-from-cloudflare.mdx          |   12 +-
 .../account-options/whois-redaction.mdx       |    4 +-
 .../registrar/custom-domain-protection.mdx    |    6 +-
 .../docs/registrar/get-started/index.mdx      |    2 +-
 .../registrar/get-started/register-domain.mdx |   15 +-
 .../top-level-domains/uk-domains.mdx          |   12 +-
 src/content/docs/registrar/whoisrequests.mdx  |    4 +-
 .../docs/resource-tagging/get-started.mdx     |   14 +-
 .../docs/resource-tagging/how-to/index.mdx    |    2 +-
 .../resource-tagging/how-to/manage-tags.mdx   |    6 +-
 .../reference/error-codes.mdx                 |   26 +-
 .../docs/resource-tagging/reference/index.mdx |    2 +-
 .../resource-tagging/reference/limits.mdx     |   37 +-
 .../reference/resource-types.mdx              |   80 +-
 .../docs/rules/normalization/settings.mdx     |    4 +-
 .../docs/rules/snippets/when-to-use.mdx       |    2 +-
 .../managed-transforms/reference.mdx          |    1 +
 .../docs/ruleset-engine/about/index.mdx       |    9 +-
 ...ink-override-ddos-l34-rule-sensitivity.mdx |    1 +
 .../ruleset-engine/rulesets-api/endpoints.mdx |  405 +++---
 src/content/docs/sandbox/bridge/http-api.mdx  |  148 +--
 .../docs/sandbox/concepts/containers.mdx      |   23 +-
 .../docs/sandbox/concepts/preview-urls.mdx    |    6 +-
 .../docs/sandbox/concepts/sandboxes.mdx       |    4 +-
 .../docs/sandbox/concepts/security.mdx        |   65 +-
 .../docs/sandbox/concepts/sessions.mdx        |   77 +-
 .../configuration/environment-variables.mdx   |   32 +-
 .../docs/sandbox/configuration/transport.mdx  |    5 +-
 .../sandbox/guides/production-deployment.mdx  |    9 +-
 src/content/docs/sandbox/platform/pricing.mdx |    2 -
 .../sandbox/tutorials/ai-code-executor.mdx    |   76 +-
 .../tutorials/analyze-data-with-ai.mdx        |   29 +-
 .../tutorials/automated-testing-pipeline.mdx  |  116 +-
 .../tutorials/claude-managed-agents.mdx       |   29 +-
 .../sandbox/tutorials/code-review-bot.mdx     |    4 +-
 src/content/docs/secrets-store/audit-logs.mdx |    2 +-
 src/content/docs/secrets-store/index.mdx      |    3 +-
 .../secrets-store/integrations/ai-gateway.mdx |    2 +-
 .../docs/secrets-store/integrations/index.mdx |    2 +-
 .../secrets-store/manage-secrets/how-to.mdx   |    2 +-
 .../secrets-store/manage-secrets/index.mdx    |    2 +-
 .../docs/security-center/brand-protection.mdx |    2 +-
 .../docs/security-center/changelog.mdx        |   10 +-
 .../cloudforce-one/cloudforce-one.mdx         |    1 +
 .../cloudforce-one/open-port-scanning.mdx     |  170 ++-
 .../investigate/change-categorization.mdx     |    1 +
 .../security-center/investigate/index.mdx     |    1 +
 .../investigate/investigate-threats.mdx       |    5 +-
 .../investigate/scan-limits.mdx               |    4 +
 src/content/docs/security/overview.mdx        |   43 +-
 .../docs/smart-shield/concepts/index.mdx      |    2 +-
 .../smart-shield/concepts/network-diagram.mdx |    2 +-
 .../docs/smart-shield/configuration/argo.mdx  |    2 +-
 .../configuration/cache-reserve/analytics.mdx |    6 +-
 .../configuration/cache-reserve/index.mdx     |    2 +-
 .../cache-reserve/operations.mdx              |    5 +-
 .../how-it-works/connection-forwarding.mdx    |    6 +-
 .../how-it-works/index.mdx                    |    2 +-
 .../dedicated-egress-ips/index.mdx            |    8 +-
 .../dedicated-egress-ips/ips-utilization.mdx  |  202 +--
 .../dedicated-egress-ips/other-products.mdx   |    2 +-
 .../configuration/health-checks/analytics.mdx |    5 +-
 .../configuration/health-checks/index.mdx     |    2 +-
 .../configuration/health-checks/setup.mdx     |    4 +-
 .../health-checks/zone-lockdown.mdx           |    2 +-
 .../docs/smart-shield/configuration/index.mdx |    2 +-
 .../configuration/regional-tiered-cache.mdx   |    2 +-
 .../configuration/smart-tiered-cache.mdx      |    2 +-
 src/content/docs/spectrum/about/byoip.mdx     |   75 +-
 .../docs/spectrum/about/ddos-for-spectrum.mdx |    1 +
 src/content/docs/spectrum/about/ftp.mdx       |   16 +-
 src/content/docs/spectrum/about/index.mdx     |    3 +-
 src/content/docs/spectrum/about/static-ip.mdx |   46 +-
 src/content/docs/spectrum/glossary.mdx        |    3 +-
 .../spectrum/how-to/enable-proxy-protocol.mdx |    3 +
 src/content/docs/spectrum/how-to/index.mdx    |    3 +-
 .../docs/spectrum/protocols-per-plan.mdx      |    3 +-
 .../docs/spectrum/reference/analytics.mdx     |   46 +-
 src/content/docs/spectrum/reference/index.mdx |    3 +-
 .../spectrum/reference/layer-7-analytics.mdx  |    4 +-
 src/content/docs/spectrum/reference/logs.mdx  |    3 +
 .../spectrum/reference/settings-by-plan.mdx   |   14 +-
 src/content/docs/speed/aim.mdx                |   33 +-
 src/content/docs/speed/glossary.mdx           |    3 +-
 .../docs/speed/observatory/dashboard.mdx      |   11 +-
 .../docs/speed/observatory/rum-beacon.mdx     |   46 +-
 .../docs/speed/observatory/run-speed-test.mdx |   21 +-
 .../docs/speed/observatory/test-results.mdx   |   23 +-
 .../docs/speed/optimization/content/apo.mdx   |    1 +
 .../optimization/content/compression.mdx      |    6 +-
 .../optimization/content/early-hints.mdx      |    1 +
 .../content/fonts/troubleshooting.mdx         |    5 +-
 .../docs/speed/optimization/content/index.mdx |    3 +-
 .../rocket-loader/ignore-javascripts.mdx      |   10 +-
 .../content/shared-dictionaries.mdx           |    8 +-
 .../optimization/content/smart-hints.mdx      |    1 +
 .../optimization/content/speed-brain.mdx      |    9 +-
 .../content/troubleshooting/index.mdx         |    3 +-
 .../optimization/images/image-resizing.mdx    |    1 +
 .../docs/speed/optimization/images/index.mdx  |    3 +-
 .../docs/speed/optimization/images/polish.mdx |    1 +
 .../images/troubleshooting/index.mdx          |    3 +-
 .../multiple-optimizations.mdx                |    1 +
 .../images/troubleshooting/polish.mdx         |    1 +
 .../troubleshooting-missing-images.mdx        |    6 +-
 src/content/docs/speed/optimization/index.mdx |    3 +-
 .../docs/speed/optimization/measurement.mdx   |    1 +
 .../speed/optimization/protocol/http2.mdx     |    4 +-
 .../speed/optimization/protocol/index.mdx     |    3 +-
 ...hanced-http2-prioritization-ios-safari.mdx |    3 +
 .../protocol/troubleshooting/index.mdx        |    3 +-
 .../speed/optimization/recommendations.mdx    |    1 +
 src/content/docs/speed/smart-shield.mdx       |    3 +-
 src/content/docs/speed/troubleshooting.mdx    |   11 +-
 src/content/docs/ssl/changelog.mdx            |    4 +-
 .../forward-a-client-certificate.mdx          |    2 +-
 .../revoke-client-certificate.mdx             |    3 +
 src/content/docs/ssl/concepts.mdx             |    6 +-
 .../customize-cipher-suites/index.mdx         |    8 +-
 .../cipher-suites/supported-cipher-suites.mdx |   50 +-
 .../additional-options/index.mdx              |    3 +-
 .../additional-options/minimum-tls.mdx        |   22 +-
 .../additional-options/tls-13.mdx             |    9 +-
 .../api-commands.mdx                          |   14 +-
 .../manage-certificates.mdx                   |    8 +-
 .../edge-certificates/backup-certificates.mdx |    3 +-
 .../ssl/edge-certificates/caa-records.mdx     |    1 +
 .../bundling-methodologies.mdx                |    3 +-
 .../custom-certificates/renewing.mdx          |    3 +-
 .../docs/ssl/edge-certificates/ech.mdx        |    4 +-
 .../geokey-manager/supported-options.mdx      |    4 +-
 .../docs/ssl/edge-certificates/index.mdx      |    2 +-
 .../edge-certificates/staging-environment.mdx |   23 +-
 .../universal-ssl/alerts.mdx                  |    8 +-
 .../universal-ssl/disable-universal-ssl.mdx   |    2 +
 .../universal-ssl/troubleshooting.mdx         |    8 +-
 .../ssl/keyless-ssl/configuration/index.mdx   |    3 +-
 src/content/docs/ssl/keyless-ssl/glossary.mdx |    1 +
 .../azure-managed-hsm.mdx                     |    1 +
 .../fortanix-dsm.mdx                          |    2 +-
 .../hardware-security-modules/index.mdx       |    7 +-
 .../reference/high-availability.mdx           |    1 +
 .../docs/ssl/keyless-ssl/reference/index.mdx  |    3 +-
 .../reference/keyless-delegation.mdx          |    1 +
 .../ssl/keyless-ssl/reference/metrics.mdx     |  184 +--
 .../reference/scaling-and-benchmarking.mdx    |    5 +-
 .../keyless-ssl/upgrading-your-key-server.mdx |    3 +
 .../set-up/global.mdx                         |    5 +-
 .../set-up/index.mdx                          |    5 +-
 .../origin-configuration/cipher-suites.mdx    |   28 +-
 .../docs/ssl/origin-configuration/index.mdx   |    3 +-
 .../origin-ca/troubleshooting.mdx             |    2 +-
 .../origin-configuration/ssl-modes/full.mdx   |    6 +-
 .../origin-configuration/ssl-modes/index.mdx  |    2 +-
 .../ssl-modes/ssl-only-origin-pull.mdx        |    7 +-
 .../docs/ssl/reference/all-features.mdx       |    5 +-
 .../ssl/reference/browser-compatibility.mdx   |    9 +-
 .../certificate-and-hostname-priority.mdx     |   17 +-
 .../ssl/reference/certificate-authorities.mdx |    2 +-
 .../ssl/reference/certificate-pinning.mdx     |    1 +
 .../cloudflare-and-cve-2019-1559.mdx          |    7 +-
 .../compliance-and-vulnerabilities.mdx        |   42 +-
 src/content/docs/ssl/reference/index.mdx      |    3 +-
 .../migration-guides/entrust-distrust.mdx     |   15 +-
 .../ssl/reference/migration-guides/index.mdx  |    3 +-
 src/content/docs/ssl/reference/protocols.mdx  |   18 +-
 src/content/docs/ssl/saas.mdx                 |    1 +
 .../troubleshooting/general-ssl-errors.mdx    |    2 +-
 .../docs/ssl/troubleshooting/index.mdx        |   10 +-
 .../troubleshooting/mixed-content-errors.mdx  |   19 +-
 .../version-cipher-mismatch.mdx               |    6 +-
 .../stream/edit-videos/adding-captions.mdx    |   91 +-
 .../edit-videos/player-enhancements.mdx       |   16 +-
 src/content/docs/stream/examples/dash-js.mdx  |    1 +
 src/content/docs/stream/examples/hls-js.mdx   |    5 +-
 src/content/docs/stream/examples/index.mdx    |    1 +
 .../examples/obs-from-scratch/index.mdx       |    1 +
 .../docs/stream/examples/rtmps_playback.mdx   |    3 +-
 .../docs/stream/examples/srt_playback.mdx     |    3 +-
 .../docs/stream/examples/stream-player.mdx    |   13 +-
 src/content/docs/stream/examples/video-js.mdx |    3 +-
 src/content/docs/stream/examples/vidstack.mdx |   15 +-
 .../fetching-bulk-analytics.mdx               |    1 -
 .../docs/stream/getting-analytics/index.mdx   |   11 +-
 .../getting-analytics/live-viewer-count.mdx   |    1 +
 .../stream/manage-video-library/index.mdx     |    1 +
 .../stream/manage-video-library/searching.mdx |    1 +
 src/content/docs/stream/stream-api.mdx        |    1 +
 .../stream/stream-live/custom-domains.mdx     |    3 +-
 .../download-stream-live-videos.mdx           |    4 +-
 .../docs/stream/stream-live/dvr-for-live.mdx  |   16 +-
 src/content/docs/stream/stream-live/index.mdx |    7 +-
 .../stream-live/live-instant-clipping.mdx     |   91 +-
 .../docs/stream/stream-live/simulcasting.mdx  |   40 +-
 .../stream/stream-live/start-stream-live.mdx  |    1 -
 .../stream/stream-live/troubleshooting.mdx    |   73 +-
 .../docs/stream/stream-live/webhooks.mdx      |   64 +-
 .../docs/stream/transform-videos/bindings.mdx |   36 +-
 .../docs/stream/transform-videos/index.mdx    |    4 +-
 .../docs/stream/uploading-videos/index.mdx    |   14 +-
 .../stream/uploading-videos/player-api.mdx    |  227 ++--
 .../uploading-videos/resumable-uploads.mdx    |    6 +
 .../uploading-videos/upload-via-link.mdx      |   80 +-
 .../viewing-videos/displaying-thumbnails.mdx  |   56 +-
 .../using-the-player-api.mdx                  |  260 ++--
 .../api-content-types/deprecated-apis.mdx     |    4 +-
 .../api-content-types/endpoints.mdx           |   18 +-
 .../api-content-types/index.mdx               |    2 +-
 .../api-content-types/parameters.mdx          |    2 +-
 .../guidelines-for-curl-commands.mdx          |   50 +-
 .../style-guide/components/anchor-heading.mdx |   11 +-
 .../components/available-notifications.mdx    |   15 +-
 .../style-guide/components/description.mdx    |    8 +-
 .../docs/style-guide/components/example.mdx   |   18 +-
 .../style-guide/components/feature-table.mdx  |    4 +-
 .../docs/style-guide/components/feature.mdx   |    8 +-
 .../components/glossary-definition.mdx        |   12 +-
 .../components/glossary-tooltip.mdx           |   12 +-
 .../docs/style-guide/components/glossary.mdx  |   12 +-
 .../style-guide/components/inline-badge.mdx   |   35 +-
 .../style-guide/components/link-cards.mdx     |   24 +-
 .../style-guide/components/list-tutorials.mdx |    2 +-
 .../components/package-managers.mdx           |    4 +-
 .../components/pages-build-preset.mdx         |    4 +-
 .../docs/style-guide/components/plan.mdx      |    5 +-
 .../components/product-availability-text.mdx  |    8 +-
 .../components/product-features.mdx           |    5 +-
 .../components/related-product.mdx            |    7 +-
 .../docs/style-guide/components/rule-id.mdx   |    4 +-
 .../docs/style-guide/components/steps.mdx     |    2 +-
 .../components/subtract-ip-calculator.mdx     |    6 +-
 .../components/type-highlighting.mdx          |    2 +-
 .../docs/style-guide/components/usage.mdx     |    2 +-
 .../components/wrangler-namespace.mdx         |    2 +-
 .../docs/style-guide/components/youtube.mdx   |    6 +-
 .../docs/style-guide/contributions.mdx        |   78 +-
 .../component-attributes/dynamic-lists.mdx    |    8 +-
 .../component-attributes/examples.mdx         |    8 +-
 .../component-attributes/glossary-entry.mdx   |   10 +
 .../component-attributes/index.mdx            |    2 +-
 .../intended-audience.mdx                     |   14 +-
 .../component-attributes/links.mdx            |   18 +-
 .../mathematical-operations.mdx               |    6 +-
 .../component-attributes/next-steps.mdx       |    6 +-
 .../notes-tips-warnings.mdx                   |    8 +-
 .../information-architecture.mdx              |   14 +-
 .../code-conventions-and-format.mdx           |   62 +-
 .../formatting/dates-and-times.mdx            |    6 +-
 .../formatting/external-references.mdx        |    6 +-
 .../formatting/file-types-and-extensions.mdx  |   12 +-
 .../docs/style-guide/formatting/index.mdx     |    2 +-
 .../style-guide/formatting/keyboard-keys.mdx  |   24 +-
 .../notes-and-other-notation-types.mdx        |    1 -
 .../numbers-and-units-of-measurement.mdx      |   18 +-
 .../product-name-and-pluralization.mdx        |    4 +-
 .../formatting/structure/index.mdx            |    2 +-
 .../formatting/structure/lists.mdx            |   79 +-
 .../formatting/structure/tables.mdx           |   79 +-
 .../docs/style-guide/frontmatter/sidebar.mdx  |    4 +-
 .../docs/style-guide/grammar/index.mdx        |    2 +-
 .../grammar/parts-of-speech/abbreviations.mdx |   46 +-
 .../grammar/parts-of-speech/acronyms.mdx      |    8 +-
 .../parts-of-speech/capitalization.mdx        |  160 +--
 .../parts-of-speech/compound-words.mdx        |   53 +-
 .../grammar/parts-of-speech/contractions.mdx  |    2 +-
 .../grammar/parts-of-speech/index.mdx         |    2 +-
 .../parts-of-speech/nouns-and-pronouns.mdx    |    2 +-
 .../grammar/parts-of-speech/possessives.mdx   |    2 +-
 .../grammar/parts-of-speech/prepositions.mdx  |    2 +-
 .../punctuation-marks-and-symbols/commas.mdx  |    2 +-
 .../punctuation-marks-and-symbols/dashes.mdx  |   16 +-
 .../punctuation-marks-and-symbols/index.mdx   |    2 +-
 .../docs/style-guide/how-we-docs/our-site.mdx |    1 +
 .../docs/style-guide/how-we-docs/reviews.mdx  |   21 +-
 .../support/contacting-cloudflare-support.mdx |   46 +-
 src/content/docs/support/index.mdx            |    2 +-
 ...ress-plugin-automatic-cache-management.mdx |   16 +-
 ...-enable-http2-server-push-in-wordpress.mdx |    6 +-
 ...tent-management-systems-like-wordpress.mdx |   38 +-
 .../content-management-system-cms/index.mdx   |    2 +-
 ...dpress-in-cloudflares-wordpress-plugin.mdx |   26 +-
 .../forum-software/index.mdx                  |    2 +-
 ...-various-forums-vbulletin-xenforo-mybb.mdx |   10 +-
 .../support/third-party-software/index.mdx    |    2 +-
 .../third-party-software/others/index.mdx     |    2 +-
 ...ess-costs-between-azure-and-cloudflare.mdx |    8 +-
 .../cannot-locate-dashboard-account.mdx       |    8 +-
 ...-information-for-troubleshooting-sites.mdx |   26 +-
 .../geographic-traffic-routing.mdx            |    2 +-
 .../general-troubleshooting/index.mdx         |    2 +-
 .../not-receiving-cloudflare-emails.mdx       |   14 +-
 .../service-disruption.mdx                    |    8 +-
 .../third-party-load-balancers.mdx            |   12 +-
 .../troubleshooting-crawl-errors.mdx          |   40 +-
 .../4xx-client-error/error-400.mdx            |    2 +-
 .../4xx-client-error/error-401.mdx            |    2 +-
 .../4xx-client-error/error-406.mdx            |    2 +-
 .../4xx-client-error/error-407.mdx            |    2 +-
 .../4xx-client-error/error-408.mdx            |    2 +-
 .../4xx-client-error/error-409.mdx            |    2 +-
 .../4xx-client-error/error-410.mdx            |    2 +-
 .../4xx-client-error/error-411.mdx            |    2 +-
 .../4xx-client-error/error-412.mdx            |    2 +-
 .../4xx-client-error/error-413.mdx            |    2 +-
 .../4xx-client-error/error-414.mdx            |    2 +-
 .../4xx-client-error/error-416.mdx            |    2 +-
 .../4xx-client-error/error-417.mdx            |    2 +-
 .../4xx-client-error/error-429.mdx            |    1 +
 .../4xx-client-error/error-451.mdx            |    2 +-
 .../4xx-client-error/index.mdx                |    4 +-
 .../cloudflare-10xxx-errors/error-10028.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10043.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10044.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10045.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10046.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10047.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10048.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10049.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10050.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10051.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10052.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10055.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10056.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10058.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10059.mdx   |    2 +-
 .../cloudflare-10xxx-errors/error-10060.mdx   |    2 +-
 .../cloudflare-10xxx-errors/index.md          |    2 +-
 .../cloudflare-1xxx-errors/error-1000.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1002.mdx     |    4 +-
 .../cloudflare-1xxx-errors/error-1004.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1009.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1014.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1035.mdx     |    2 +-
 .../cloudflare-1xxx-errors/error-1040.mdx     |    1 +
 .../cloudflare-1xxx-errors/error-1102.mdx     |    1 +
 .../cloudflare-1xxx-errors/index.mdx          |    4 +
 .../cloudflare-5xx-errors/error-501.mdx       |    2 +-
 .../cloudflare-5xx-errors/error-503.mdx       |    9 +-
 .../cloudflare-5xx-errors/error-520.mdx       |    1 +
 .../cloudflare-5xx-errors/error-522.mdx       |    4 +-
 .../cloudflare-5xx-errors/error-524.mdx       |    5 +-
 .../cloudflare-5xx-errors/error-525.mdx       |    2 +-
 .../cloudflare-5xx-errors/index.mdx           |    6 +-
 .../cloudflare-error-headers.mdx              |   11 +-
 .../http-status-codes/index.mdx               |    2 +-
 .../docs/support/troubleshooting/index.mdx    |    2 +-
 .../restoring-visitor-ips/index.mdx           |    2 +-
 .../restoring-original-visitor-ips.mdx        |    5 +-
 src/content/docs/tenant/how-to/index.mdx      |    2 +-
 src/content/docs/tenant/index.mdx             |    8 +-
 src/content/docs/tenant/reference/index.mdx   |    2 +-
 .../advanced-topics/best-practices.mdx        |    2 +
 .../terraform/how-to/create-partial-zone.mdx  |    3 +-
 .../how-to/create-secondary-zone.mdx          |    4 +-
 .../authentication-error-dns-records.mdx      |    2 +-
 src/content/docs/terraform/tutorial/index.mdx |   36 +-
 src/content/docs/time-services/index.mdx      |    2 +-
 .../docs/time-services/roughtime/index.mdx    |    2 +-
 .../docs/time-services/roughtime/recipes.mdx  |   32 +-
 src/content/docs/time-services/tos.mdx        |    2 +-
 .../tunnel/advanced/origin-parameters.mdx     |   16 +-
 .../docs/tunnel/advanced/run-parameters.mdx   |   24 +-
 src/content/docs/tunnel/changelog.mdx         |    5 +-
 .../tunnel/deployment-guides/terraform.mdx    |    1 +
 .../tunnel/downloads/system-requirements.mdx  |    7 +-
 src/content/docs/tunnel/troubleshooting.mdx   |    1 -
 .../hostname-management/any-hostname.mdx      |   69 +-
 .../hostname-management/index.mdx             |    5 +-
 .../hostname-management/pre-clearance.mdx     |   17 +-
 .../additional-configuration/index.mdx        |    3 +-
 .../pre-clearance-support.mdx                 |    3 +-
 .../docs/turnstile/concepts/challenges.mdx    |    1 +
 src/content/docs/turnstile/concepts/index.mdx |    5 +-
 .../turnstile/extensions/google-firebase.mdx  |   35 +-
 .../docs/turnstile/extensions/index.mdx       |    3 +-
 .../turnstile/extensions/pages-plugin.mdx     |    1 +
 .../turnstile/extensions/waiting-room.mdx     |    1 +
 .../get-started/widget-management/api.mdx     |   61 +-
 .../get-started/widget-management/index.mdx   |    4 +-
 .../widget-management/terraform.mdx           |   10 +-
 .../docs/turnstile/migration/hcaptcha.mdx     |    2 +-
 .../docs/turnstile/reference/index.mdx        |    3 +-
 .../reference/supported-browsers.mdx          |    1 +
 .../reference/supported-languages.mdx         |    1 +
 .../reference/turnstile-privacy-addendum.mdx  |    1 +
 .../challenge-solve-issues.mdx                |    1 +
 .../client-side-errors/index.mdx              |  137 +-
 .../docs/turnstile/troubleshooting/index.mdx  |    3 +-
 .../troubleshooting/rotate-secret-key.mdx     |    3 +-
 .../turnstile/troubleshooting/testing.mdx     |   67 +-
 .../turnstile/turnstile-analytics/index.mdx   |    5 +-
 .../excluding-turnstile-from-e2e-tests.mdx    |   54 +-
 .../fraud-detection-with-ephemeral-ids.mdx    |    4 +-
 ...ating-turnstile-waf-and-bot-management.mdx |    8 +-
 .../docs/use-cases/e-commerce/performance.mdx |    2 +-
 .../encrypt-all-keep-site-secure.mdx          |   27 +-
 .../protect-sensitive-forms-fraud-abuse.mdx   |   77 +-
 .../stop-account-takeover-attacks.mdx         |   42 +-
 .../solutions/stop-malicious-bots.mdx         |    9 +-
 .../docs/use-cases/web-apps/performance.mdx   |    3 +-
 .../docs/vectorize/best-practices/index.mdx   |    2 +-
 .../vectorize/best-practices/list-vectors.mdx |    3 +-
 src/content/docs/vectorize/demos.mdx          |   11 +-
 .../docs/vectorize/examples/agents.mdx        |    2 +-
 src/content/docs/vectorize/examples/index.mdx |    2 +-
 .../docs/vectorize/get-started/index.mdx      |    2 +-
 src/content/docs/vectorize/platform/index.mdx |    2 +-
 .../docs/vectorize/reference/index.mdx        |    2 +-
 src/content/docs/version-management/about.mdx |    6 +-
 .../how-to/compare-versions.mdx               |    2 +-
 .../how-to/environments.mdx                   |   33 +-
 .../docs/version-management/how-to/index.mdx  |    4 +-
 .../version-management/how-to/versions.mdx    |    4 +-
 .../reference/available-configurations.mdx    |   14 +-
 .../version-management/reference/index.mdx    |    4 +-
 .../reference/read-only-environments.mdx      |    7 +-
 .../waf/custom-rules/create-dashboard.mdx     |    1 +
 .../use-cases/sequence-custom-rules.mdx       |    2 +-
 src/content/docs/waf/glossary.mdx             |    3 +-
 src/content/docs/waf/managed-rules/index.mdx  |    1 +
 src/content/docs/waf/tools/index.mdx          |    1 +
 src/content/docs/waf/tools/privacy-pass.mdx   |    9 +-
 src/content/docs/waf/troubleshooting/faq.mdx  |    1 -
 src/content/docs/waiting-room/about.mdx       |    6 +-
 .../additional-options/create-events.mdx      |   33 +-
 .../waiting-room/additional-options/index.mdx |    3 +-
 .../additional-options/ssl-for-saas.mdx       |    1 +
 .../waiting-room-rules/index.mdx              |    3 +-
 .../docs/waiting-room/api-reference.mdx       |    1 +
 src/content/docs/waiting-room/glossary.mdx    |    3 +-
 .../how-to/control-user-session.mdx           |    8 +-
 .../how-to/edit-delete-waiting-room.mdx       |   41 +-
 .../docs/waiting-room/how-to/index.mdx        |    3 +-
 .../waiting-room/how-to/json-response.mdx     |    2 +
 .../how-to/monitor-waiting-room.mdx           |   45 +-
 .../how-to/place-waiting-room.mdx             |    5 +-
 .../how-to/waiting-room-dashboard.mdx         |    3 +-
 src/content/docs/waiting-room/plans.mdx       |    3 +-
 .../reference/configuration-settings.mdx      |   11 +-
 .../docs/waiting-room/reference/index.mdx     |    3 +-
 .../reference/waiting-room-api.mdx            |   21 +-
 .../reference/waiting-room-cookie.mdx         |   12 +-
 .../docs/waiting-room/troubleshooting.mdx     |   50 +-
 .../docs/warp-client/get-started/linux.mdx    |   21 +-
 .../docs/warp-client/known-issues-and-faq.mdx |    8 +-
 .../docs/warp-client/legal/3rdparty.mdx       | 1139 ++++++++++-------
 src/content/docs/warp-client/legal/index.mdx  |    7 +-
 src/content/docs/warp-client/privacy.mdx      |    1 +
 .../configuration-options/filters.mdx         |    3 +-
 .../configuration-options/index.mdx           |    3 +-
 .../data-metrics/core-web-vitals.mdx          |    5 +-
 .../data-origin-and-collection.mdx            |    2 +-
 .../web-analytics/data-metrics/dimensions.mdx |   21 +-
 .../data-metrics/high-level-metrics.mdx       |    9 +-
 .../docs/web-analytics/data-metrics/index.mdx |    3 +-
 .../data-metrics/page-load-time-summary.mdx   |    1 +
 src/content/docs/web-analytics/faq.mdx        |   14 +-
 .../web-analytics/get-started/rum-beacon.mdx  |    3 +-
 .../get-started/web-analytics-spa.mdx         |   10 +-
 src/content/docs/web-analytics/limits.mdx     |    1 +
 src/content/docs/web3/about.mdx               |    2 +-
 src/content/docs/web3/api-reference.mdx       |    1 +
 .../web3/ethereum-gateway/concepts/index.mdx  |    3 +-
 .../web3/ethereum-gateway/reference/index.mdx |    3 +-
 .../reference/kill-switches.mdx               |    7 +-
 .../reference/rinkeby-deprecation.mdx         |   57 +-
 .../reference/supported-networks.mdx          |    1 +
 src/content/docs/web3/how-to/index.mdx        |    3 +-
 .../docs/web3/how-to/use-ipfs-gateway.mdx     |    1 +
 .../web3/ipfs-gateway/concepts/dnslink.mdx    |    1 +
 .../docs/web3/ipfs-gateway/concepts/index.mdx |    3 +-
 .../reference/automated-deployment.mdx        |    7 +-
 .../web3/ipfs-gateway/reference/index.mdx     |    3 +-
 .../peering-with-content-providers.mdx        |  129 +-
 .../reference/updating-for-ipfs.mdx           |    7 +-
 .../web3/ipfs-gateway/troubleshooting.mdx     |    1 +
 .../web3/reference/gateway-dns-records.mdx    |    5 +-
 .../docs/web3/reference/gateway-status.mdx    |    1 +
 src/content/docs/web3/reference/index.mdx     |    3 +-
 .../docs/web3/reference/migration-guide.mdx   |    3 +-
 src/content/docs/workers-ai/agents.mdx        |   13 +-
 src/content/docs/workers-ai/api-reference.mdx |    1 +
 .../workers-ai/configuration/bindings.mdx     |   26 +-
 .../configuration/hugging-face-chat-ui.mdx    |   34 +-
 .../embedded/examples/fetch.mdx               |   36 +-
 .../function-calling/embedded/examples/kv.mdx |    1 -
 .../embedded/examples/openapi.mdx             |   22 +-
 .../function-calling/embedded/index.mdx       |    4 +-
 .../docs/workers-ai/get-started/dashboard.mdx |    5 +-
 .../docs/workers-ai/get-started/index.mdx     |    4 +-
 .../docs/workers-ai/get-started/rest-api.mdx  |    3 +-
 src/content/docs/workers-ai/guides/agents.mdx |    2 +-
 ...generation-using-deepseek-coder-models.mdx |   18 +-
 ...choose-the-right-text-generation-model.mdx |   72 +-
 .../docs/workers-ai/platform/data-usage.mdx   |    8 +-
 .../docs/workers-ai/platform/pricing.mdx      |   62 +-
 .../docs/workers-vpc/configuration/index.mdx  |    2 +-
 .../configuration/vpc-services/terraform.mdx  |    1 -
 .../docs/workers-vpc/examples/private-api.mdx |    4 +-
 .../examples/private-s3-bucket.mdx            |    4 +-
 .../route-across-private-services.mdx         |   15 +-
 .../workers/ci-cd/builds/automatic-prs.mdx    |    1 -
 .../workers/ci-cd/builds/build-caching.mdx    |   18 +-
 .../docs/workers/ci-cd/builds/build-image.mdx |    5 +-
 .../workers/ci-cd/builds/configuration.mdx    |   12 +-
 .../docs/workers/ci-cd/builds/index.mdx       |   10 +-
 .../ci-cd/builds/limits-and-pricing.mdx       |   24 +-
 .../workers/ci-cd/builds/troubleshoot.mdx     |    1 -
 .../ci-cd/external-cicd/github-actions.mdx    |    2 -
 .../ci-cd/external-cicd/gitlab-cicd.mdx       |    1 -
 .../configuration/integrations/index.mdx      |   22 +-
 .../configuration/routing/custom-domains.mdx  |   36 +-
 .../workers/configuration/routing/routes.mdx  |   14 +-
 .../sites/start-from-existing.mdx             |   36 +-
 .../sites/start-from-scratch.mdx              |   50 +-
 .../configuration/sites/start-from-worker.mdx |   20 +-
 .../versions-and-deployments/index.mdx        |    2 +-
 .../version-overrides.mdx                     |   24 +-
 .../configuration/workers-with-page-rules.mdx |   50 +-
 .../third-party-integrations/supabase.mdx     |    4 +-
 .../third-party-integrations/turso.mdx        |    6 +-
 .../third-party-integrations/upstash.mdx      |    3 +-
 .../third-party-integrations/xata.mdx         |    1 +
 .../development-testing/multi-workers.mdx     |   44 +-
 .../workers/development-testing/testing.mdx   |    2 +-
 .../development-testing/vite-plugin.mdx       |    2 +-
 .../docs/workers/examples/103-early-hints.mdx |    2 +-
 .../docs/workers/examples/ab-testing.mdx      |    1 +
 .../accessing-the-cloudflare-object.mdx       |    1 +
 .../workers/examples/aggregate-requests.mdx   |    1 +
 .../docs/workers/examples/alter-headers.mdx   |    1 +
 .../workers/examples/auth-with-headers.mdx    |    1 +
 .../docs/workers/examples/basic-auth.mdx      |    1 +
 .../docs/workers/examples/block-on-tls.mdx    |    1 +
 .../workers/examples/bulk-origin-proxy.mdx    |    1 +
 .../docs/workers/examples/bulk-redirects.mdx  |    1 +
 .../docs/workers/examples/cache-api.mdx       |    1 +
 .../workers/examples/cache-post-request.mdx   |    1 +
 .../docs/workers/examples/cache-tags.mdx      |    1 +
 .../workers/examples/cache-using-fetch.mdx    |    5 +-
 .../workers/examples/conditional-response.mdx |    1 +
 .../workers/examples/cors-header-proxy.mdx    |    2 +
 .../examples/country-code-redirect.mdx        |    1 +
 .../workers/examples/data-loss-prevention.mdx |    1 +
 .../docs/workers/examples/debugging-logs.mdx  |    1 +
 .../workers/examples/extract-cookie-value.mdx |    1 +
 .../docs/workers/examples/fetch-json.mdx      |    1 +
 .../examples/geolocation-app-weather.mdx      |    1 +
 .../examples/geolocation-custom-styling.mdx   |    1 +
 .../examples/geolocation-hello-world.mdx      |    1 +
 .../workers/examples/hot-link-protection.mdx  |    1 +
 .../examples/modify-request-property.mdx      |    1 +
 .../docs/workers/examples/modify-response.mdx |    1 +
 .../examples/multiple-cron-triggers.mdx       |    1 +
 .../workers/examples/openai-sdk-streaming.mdx |    1 +
 .../docs/workers/examples/post-json.mdx       |    1 +
 .../protect-against-timing-attacks.mdx        |    1 +
 .../docs/workers/examples/read-post.mdx       |    1 +
 .../docs/workers/examples/return-html.mdx     |    1 +
 .../docs/workers/examples/rewrite-links.mdx   |    1 +
 .../workers/examples/signing-requests.mdx     |    1 +
 .../examples/turnstile-html-rewriter.mdx      |    1 +
 .../docs/workers/examples/websockets.mdx      |    4 +-
 .../framework-guides/ai-and-agents/index.mdx  |   13 +-
 .../workers/framework-guides/apis/index.mdx   |    9 +-
 .../docs/workers/framework-guides/index.mdx   |    9 +-
 .../framework-guides/mobile-apps/expo.mdx     |    2 +-
 .../framework-guides/mobile-apps/index.mdx    |    9 +-
 .../framework-guides/web-apps/astro.mdx       |   24 +-
 .../framework-guides/web-apps/index.mdx       |    9 +-
 .../web-apps/more-web-frameworks/analog.mdx   |   18 +-
 .../web-apps/more-web-frameworks/angular.mdx  |    6 +-
 .../more-web-frameworks/docusaurus.mdx        |    2 +
 .../web-apps/more-web-frameworks/hono.mdx     |    2 +
 .../web-apps/more-web-frameworks/index.mdx    |    2 +-
 .../web-apps/more-web-frameworks/nuxt.mdx     |   18 +-
 .../web-apps/more-web-frameworks/solid.mdx    |   18 +-
 .../web-apps/more-web-frameworks/waku.mdx     |   14 +-
 .../framework-guides/web-apps/nextjs.mdx      |   48 +-
 .../framework-guides/web-apps/redwoodsdk.mdx  |    2 +-
 .../framework-guides/web-apps/sveltekit.mdx   |   24 +-
 .../framework-guides/web-apps/vike.mdx        |   32 +-
 .../workers/framework-guides/web-apps/vue.mdx |   24 +-
 .../docs/workers/get-started/dashboard.mdx    |   11 +-
 .../docs/workers/get-started/quickstarts.mdx  |    1 +
 .../workers/languages/javascript/index.mdx    |   13 +-
 .../docs/workers/observability/errors.mdx     |   58 +-
 .../exporting-opentelemetry-data/axiom.mdx    |   22 +-
 .../grafana-cloud.mdx                         |   31 +-
 .../honeycomb.mdx                             |    8 +-
 .../exporting-opentelemetry-data/index.mdx    |   32 +-
 .../exporting-opentelemetry-data/posthog.mdx  |   47 +-
 .../exporting-opentelemetry-data/sentry.mdx   |   29 +-
 .../workers/observability/logs/logpush.mdx    |   91 +-
 .../observability/logs/real-time-logs.mdx     |    1 -
 .../observability/logs/workers-logs.mdx       |    6 +-
 .../observability/metrics-and-analytics.mdx   |    1 -
 .../workers/observability/source-maps.mdx     |   15 +-
 src/content/docs/workers/platform/betas.mdx   |   10 +-
 .../platform/built-with-cloudflare.mdx        |    2 +-
 .../changelog/historical-changelog.mdx        |  448 +++----
 .../docs/workers/platform/changelog/index.mdx |    2 +-
 .../docs/workers/platform/known-issues.mdx    |   10 +-
 src/content/docs/workers/platform/pricing.mdx |    6 +-
 .../workers/reference/how-the-cache-works.mdx |    4 +
 .../workers/reference/how-workers-works.mdx   |   16 +-
 .../docs/workers/reference/protocols.mdx      |   14 +-
 .../docs/workers/reference/security-model.mdx |    6 +-
 .../workers/runtime-apis/bindings/index.mdx   |   55 +-
 .../runtime-apis/bindings/rate-limit.mdx      |   54 +-
 .../bindings/service-bindings/http.mdx        |   22 +-
 .../workers/runtime-apis/bindings/stream.mdx  |    1 +
 .../bindings/version-metadata.mdx             |    2 +-
 .../docs/workers/runtime-apis/cache.mdx       |  105 +-
 .../docs/workers/runtime-apis/console.mdx     |   44 +-
 .../docs/workers/runtime-apis/encoding.mdx    |   44 +-
 .../docs/workers/runtime-apis/eventsource.mdx |   75 +-
 .../workers/runtime-apis/handlers/fetch.mdx   |   27 +-
 .../workers/runtime-apis/handlers/index.mdx   |    4 +-
 .../workers/runtime-apis/handlers/tail.mdx    |  227 ++--
 .../docs/workers/runtime-apis/headers.mdx     |   19 +-
 .../workers/runtime-apis/messagechannel.mdx   |   16 +-
 .../docs/workers/runtime-apis/nodejs/util.mdx |    6 +-
 .../docs/workers/runtime-apis/performance.mdx |    2 +-
 .../runtime-apis/rpc/error-handling.mdx       |    6 +-
 .../runtime-apis/rpc/reserved-methods.mdx     |   14 +-
 .../runtime-apis/streams/readablestream.mdx   |   44 +-
 .../streams/readablestreambyobreader.mdx      |   39 +-
 .../streams/readablestreamdefaultreader.mdx   |   36 +-
 .../runtime-apis/streams/transformstream.mdx  |   77 +-
 .../runtime-apis/streams/writablestream.mdx   |   35 +-
 .../streams/writablestreamdefaultwriter.mdx   |   58 +-
 .../docs/workers/runtime-apis/tcp-sockets.mdx |  183 +--
 .../docs/workers/runtime-apis/web-crypto.mdx  |  425 ++++--
 .../runtime-apis/webassembly/index.mdx        |   16 +-
 .../docs/workers/runtime-apis/websockets.mdx  |  177 ++-
 .../routing/full-stack-application.mdx        |    5 +-
 .../testing/miniflare/storage/cache.md        |    4 +-
 .../testing/vitest-integration/recipes.mdx    |    2 +-
 .../docs/workers/vite-plugin/tutorial.mdx     |    1 -
 src/content/docs/workers/wrangler/api.mdx     |   52 +-
 .../docs/workers/wrangler/commands/r2.mdx     |    1 +
 .../docs/workers/wrangler/configuration.mdx   |   46 +-
 .../docs/workers/wrangler/custom-builds.mdx   |   15 +-
 .../docs/workers/wrangler/deprecations.mdx    |  122 +-
 .../wrangler/migration/update-v2-to-v3.mdx    |    2 +
 .../v1-to-v2/wrangler-legacy/commands.mdx     |    8 +-
 src/content/docs/workflows/build/index.mdx    |    2 +-
 .../docs/workflows/build/test-workflows.mdx   |    2 +-
 .../docs/workflows/examples/agents.mdx        |    2 +-
 .../docs/workflows/examples/backup-d1.mdx     |    1 +
 .../docs/workflows/examples/send-invoices.mdx |    1 +
 .../docs/workflows/examples/twilio.mdx        |    1 +
 .../workflows/examples/wait-for-event.mdx     |   13 +-
 .../docs/workflows/observability/index.mdx    |    4 +-
 .../docs/workflows/python/bindings.mdx        |    2 +-
 .../docs/workflows/reference/changelog.mdx    |    4 +-
 .../docs/workflows/reference/glossary.mdx     |    2 +-
 .../docs/workflows/reference/index.mdx        |    2 +-
 .../docs/workflows/reference/pricing.mdx      |   26 +-
 .../workflows/reference/wrangler-commands.mdx |    4 +-
 src/content/docs/workflows/videos.mdx         |   10 +-
 .../advanced/datalayer-compatibility.mdx      |   11 +-
 .../zaraz/advanced/domains-not-proxied.mdx    |    1 +
 .../zaraz/advanced/google-consent-mode.mdx    |   27 +-
 .../docs/zaraz/advanced/import-export.mdx     |    9 +-
 src/content/docs/zaraz/advanced/index.mdx     |    3 +-
 .../load-custom-managed-component.mdx         |    3 +-
 .../docs/zaraz/advanced/load-selectively.mdx  |    3 +
 .../zaraz/advanced/load-zaraz-manually.mdx    |   15 +-
 .../docs/zaraz/advanced/using-jsonata.mdx     |   37 +-
 .../docs/zaraz/consent-management/api.mdx     |  182 ++-
 .../zaraz/consent-management/custom-css.mdx   |    4 +-
 .../enable-consent-management.mdx             |    9 +-
 .../consent-management/iab-tcf-compliance.mdx |    4 +-
 .../docs/zaraz/consent-management/index.mdx   |   27 +-
 .../custom-actions/additional-fields.mdx      |    7 +-
 .../zaraz/custom-actions/create-action.mdx    |    3 +-
 .../zaraz/custom-actions/create-trigger.mdx   |    3 +-
 .../custom-actions/edit-tools-and-actions.mdx |   15 +-
 .../zaraz/custom-actions/edit-triggers.mdx    |    7 +-
 src/content/docs/zaraz/embeds.mdx             |    9 +-
 src/content/docs/zaraz/get-started.mdx        |    3 +-
 src/content/docs/zaraz/history/index.mdx      |    3 +-
 src/content/docs/zaraz/history/versions.mdx   |   16 +-
 src/content/docs/zaraz/http-events-api.mdx    |   98 +-
 src/content/docs/zaraz/monitoring/index.mdx   |    5 +-
 src/content/docs/zaraz/pricing-info.mdx       |    7 +-
 src/content/docs/zaraz/reference/context.mdx  |    9 +
 src/content/docs/zaraz/reference/index.mdx    |    3 +-
 .../zaraz/reference/properties-reference.mdx  |   84 +-
 src/content/docs/zaraz/reference/settings.mdx |   18 +-
 .../docs/zaraz/reference/supported-tools.mdx  |    1 +
 .../docs/zaraz/variables/create-variables.mdx |    3 +-
 .../docs/zaraz/variables/edit-variables.mdx   |    7 +-
 src/content/docs/zaraz/variables/index.mdx    |    3 +-
 .../docs/zaraz/variables/worker-variables.mdx |  100 +-
 src/content/docs/zaraz/web-api/debug-mode.mdx |    6 +-
 src/content/docs/zaraz/web-api/ecommerce.mdx  |    3 +-
 src/content/docs/zaraz/web-api/index.mdx      |    3 +-
 src/content/docs/zaraz/web-api/set.mdx        |   21 +-
 .../partials/1.1.1.1/captive-portals.mdx      |    2 +-
 src/content/partials/agents/unique-agents.mdx |    3 +-
 .../ai-crawl-control/plan-comparison.mdx      |   11 +-
 .../ai-gateway/analytics-dashboard.mdx        |    1 +
 src/content/partials/ai-gateway/logging.mdx   |    1 -
 .../ai-gateway/universal-gateway-example.mdx  |    1 +
 .../partials/ai-search/rest-api-auth.mdx      |    2 +-
 .../customer_metadata_boundary_error.mdx      |    5 +-
 .../network-analytics-requirements.mdx        |    7 +-
 .../network-analytics-v1-deprecation.mdx      |    1 +
 .../partials/api-shield/label-methodology.mdx |    9 +-
 .../api-shield/mtls-api-shield-support.mdx    |    1 +
 .../partials/api-shield/mtls-create-rule.mdx  |    5 +-
 .../partials/api-shield/rate-limit-user.mdx   |    1 +
 .../required-session-identifiers.mdx          |    1 +
 .../sequence-mitigation-availability.mdx      |    3 +-
 .../api-shield/session-identifiers.mdx        |    5 +-
 .../partials/billing/two-payment-methods.mdx  |    1 +
 .../bots/about-plan-considerations.mdx        |    5 +-
 .../partials/bots/analytics-features.mdx      |    1 +
 .../partials/bots/bfm-change-notice.mdx       |    1 +
 .../partials/bots/bm-analytics-features.mdx   |    9 +-
 .../bots/bot-settings-vs-custom-rules.mdx     |   18 +-
 src/content/partials/bots/bots-ad.mdx         |    1 +
 src/content/partials/bots/bots-cookie.mdx     |    3 +-
 src/content/partials/bots/bots-heuristics.mdx |    3 +-
 src/content/partials/bots/bots-jsd.mdx        |    1 +
 src/content/partials/bots/bots-ml.mdx         |    5 +-
 .../partials/bots/buttons-plan-pages.mdx      |   16 +-
 .../content-security-policy-limitation.mdx    |    5 +-
 .../partials/bots/disable-cf-bm-cookie.mdx    |    1 +
 .../partials/bots/endpoint-label-warning.mdx  |    7 +-
 src/content/partials/bots/execution-order.mdx |    2 +-
 src/content/partials/bots/flexible-sbfm.mdx   |    3 +-
 src/content/partials/bots/ja3-ja4-null.mdx    |    3 +-
 .../partials/bots/jsd-availability.mdx        |    3 +-
 .../partials/bots/plan-get-started.mdx        |    1 +
 src/content/partials/bots/plan-intro.mdx      |    1 +
 src/content/partials/bots/sequence-rules.mdx  |    7 +-
 .../bots/signals-intelligence-and-ja4.mdx     |    7 +-
 src/content/partials/bots/verified-bots.mdx   |    1 +
 .../improve-blurry-screenshot-resolution.mdx  |   15 +-
 .../partials/byoip/cloudflare-asn-callout.mdx |    2 +-
 src/content/partials/byoip/loa.mdx            |    2 +-
 .../byoip/validate-prefix-endpoint.mdx        |    1 +
 .../cache/cache-reserve-billing-note.mdx      |    3 +
 .../cache/cache-reserve-eligibility.mdx       |    2 +-
 .../partials/cache/cache-reserve-intro.mdx    |    2 +-
 .../partials/cache/cache-reserve-limits.mdx   |    2 +-
 .../cache/cache-reserve-operations.mdx        |    2 +-
 src/content/partials/cache/edge-ttl.mdx       |    2 +-
 .../partials/cache/regional-tiered-cache.mdx  |    2 +-
 .../partials/cache/smart-tiered-cache.mdx     |    2 +-
 .../cf-clearance-cookie.mdx                   |    3 +-
 .../create-challenge-page.mdx                 |    5 +-
 .../apex-proxying-process.mdx                 |    3 +
 .../cname-target-process.mdx                  |    1 +
 .../create-custom-hostname-api.mdx            |    6 +-
 .../create-custom-hostname-limitations.mdx    |    7 +-
 .../create-custom-hostname.mdx                |   13 +-
 .../custom-origin-server-definition.mdx       |    5 +-
 .../delete-custom-hostname-dash.mdx           |    1 +
 .../get-started-initial-setup-preamble.mdx    |    1 +
 .../get-started-per-hostname.mdx              |    5 +-
 .../get-started-prereqs.mdx                   |    7 +-
 .../get-started-service-continuation.mdx      |    1 +
 .../http-dcv-situation.mdx                    |    5 +-
 .../issue-certs-preamble.mdx                  |    1 +
 .../provider-guide-compatibility.mdx          |    7 +-
 .../provider-guide-zone-hold.mdx              |    2 +-
 .../regional-services.mdx                     |    1 +
 .../saas-customer-churn.mdx                   |    1 +
 .../same-name-as-zone.mdx                     |    3 +-
 .../ssl-for-saas-create-hostname.mdx          |    1 +
 .../ssl-for-saas-definition.mdx               |    1 +
 .../ssl-for-saas-plan-limitation.mdx          |    3 +
 .../ssl-for-saas-validate-patch.mdx           |    1 +
 .../txt-dcv-situation.mdx                     |    1 +
 .../txt-validation_api.mdx                    |   83 +-
 .../txt-validation_dashboard.mdx              |    1 +
 .../txt-validation_post.mdx                   |    3 +
 .../txt-validation_preamble.mdx               |    1 +
 .../update-dcv-method.mdx                     |    1 +
 .../wildcard-hostname-reqs.mdx                |    1 +
 .../access/access-block-page.mdx              |    7 +-
 .../cloudflare-one/access/add-mtls-cert.mdx   |   21 +-
 .../cloudflare-one/access/add-target.mdx      |   17 +-
 .../cloudflare-one/access/app-launcher.mdx    |    4 +-
 .../cloudflare-one/access/bookmarks.mdx       |    3 +-
 .../access/create-service-token.mdx           |    3 +-
 .../access/enable-scim-on-dashboard.mdx       |   14 +-
 .../access/entra-id-terraform.mdx             |    1 +
 .../cloudflare-one/access/idp-integration.mdx |    4 +-
 .../access/isolation-prereqs.mdx              |    1 +
 .../access/saas-apps/miro-sso.mdx             |    5 +-
 .../access/saas-apps/saas-sessions.mdx        |    2 +-
 .../access/saas-apps/salesforce-sso.mdx       |    1 +
 .../access/scim-requires-login.mdx            |    2 +-
 .../access/secure-tunnel-with-access.mdx      |    1 +
 .../self-hosted-app/advanced-settings.mdx     |    1 +
 .../browser-rendering-policies.mdx            |    3 +-
 .../self-hosted-app/generic-public-app.mdx    |   25 +-
 .../self-hosted-app/product-compatibility.mdx |    8 +-
 .../access/self-hosted-app/ssh-sessions.mdx   |    2 +-
 .../access/session-duration.mdx               |    1 +
 .../access/short-lived-certs-intro.mdx        |    4 +-
 .../partials/cloudflare-one/access/tags.mdx   |    1 +
 .../access/verify-scim-provisioning.mdx       |    2 +-
 .../partials/cloudflare-one/aws-resolver.mdx  |    3 +-
 .../casb/casb-dlp-integrations.mdx            |    1 +
 .../casb/microsoft/m365-copilot-findings.mdx  |    2 +-
 .../cloudflare-one/choose-team-name.mdx       |    1 +
 .../clientless-browser-isolation.mdx          |    3 +-
 .../dex/notifications-intro.mdx               |    2 +-
 .../partials/cloudflare-one/dex/pcaps-run.mdx |    2 +-
 ...-use-case-1-3-create-quarantine-policy.mdx |    8 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 ...ase-configure-quarantine-notifications.mdx |    1 +
 .../deployment/set-up-mx-inline-step.mdx      |    3 +-
 .../dispositions-and-attributes.mdx           |   10 +-
 .../email-security/domain-information.mdx     |   20 +-
 .../email-security/enable-logs.mdx            |    3 +-
 .../onboarding-prerequisites.mdx              |    3 +-
 .../cloudflare-one/gateway/add-logo-image.mdx |    1 +
 .../gateway/debugging-policies.mdx            |    1 +
 .../gateway/egress-selector-cgnat-ips.mdx     |    3 +-
 .../gateway/egress-selector-onramps.mdx       |   14 +-
 .../gateway/egress-selector-split-tunnels.mdx |    4 +-
 .../gateway/enable-tls-decryption.mdx         |    2 +-
 .../policies/do-not-inspect-applications.mdx  |    3 +-
 .../policies/egress-destination-ip.mdx        |    1 +
 ...trict-access-to-private-networks-allow.mdx |    8 +-
 ...trict-access-to-private-networks-block.mdx |    2 +-
 ...estrict-access-to-private-networks-dns.mdx |    8 +-
 .../gateway/resolver-policies-intro.mdx       |    1 +
 .../gateway/selectors/category-options.mdx    |    1 +
 .../gateway/selectors/destination-country.mdx |    7 +-
 .../gateway/selectors/device-posture.mdx      |    1 +
 .../gateway/selectors/dns-resolver-ip.mdx     |    1 +
 .../gateway/selectors/doh-subdomain.mdx       |    1 +
 .../gateway/selectors/oidc-claims.mdx         |    4 +-
 .../gateway/selectors/protocol.mdx            |    1 +
 .../gateway/selectors/query-record-type.mdx   |    1 +
 .../gateway/selectors/security-categories.mdx |    1 +
 .../gateway/selectors/source-country-dns.mdx  |    7 +-
 .../gateway/selectors/source-country-http.mdx |    7 +-
 .../gateway/selectors/source-country.mdx      |    7 +-
 .../gateway/selectors/source-ip-dns.mdx       |    1 +
 .../gateway/selectors/source-ip-resolver.mdx  |    1 +
 .../gateway/selectors/user-email.mdx          |    4 +-
 .../gateway/selectors/user-group-email.mdx    |    6 +-
 .../gateway/selectors/user-group-ids.mdx      |    6 +-
 .../gateway/selectors/user-group-names.mdx    |    6 +-
 .../gateway/selectors/user-name.mdx           |    6 +-
 .../gateway/selectors/users-dns.mdx           |   16 +-
 .../gateway/selectors/users-http.mdx          |   16 +-
 .../gateway/selectors/users.mdx               |   13 +-
 .../partials/cloudflare-one/gateway/value.mdx |    4 +-
 .../posture/configure-posture-check.mdx       |    3 +-
 .../posture/prereqs-warp-is-deployed.mdx      |    1 +
 .../cloudflare-one/ssh/decrypt-ssh-log.mdx    |    8 +-
 .../cloudflare-one/ssh/public-key.mdx         |    6 +-
 .../cloudflare-one/ssh/restart-server.mdx     |    2 +-
 .../cloudflare-one/ssh/ssh-proxy-ca-note.mdx  |    3 +-
 .../cloudflare-one/ssh/ssh-proxy-ca.mdx       |    2 +-
 .../cloudflare-one/ssh/upload-ssh-key.mdx     |    2 +-
 .../terraform/cloudflare-resources.mdx        |  312 ++---
 .../terraform/gcp-resources.mdx               |  170 +--
 .../cloudflare-one/terraform/providers-v5.mdx |    2 +-
 .../cloudflare-one/terraform/providers.mdx    |   76 +-
 .../troubleshooting/browser-isolation.mdx     |   18 +-
 .../cloudflare-one/troubleshooting/casb.mdx   |    4 -
 .../cloudflare-one/troubleshooting/dex.mdx    |    3 -
 .../troubleshooting/email-security.mdx        |   23 +-
 .../troubleshooting/gateway.mdx               |   13 +-
 .../cloudflare-one/tunnel/1033-error.mdx      |    3 +-
 .../tunnel/account-scoped-roles.mdx           |    5 +-
 .../tunnel/add-published-application.mdx      |   13 +-
 .../cloudflared-replicas-diagram.mdx          |    1 +
 .../load-balancer-tcp-monitors.mdx            |    7 +-
 .../availability/tunnel-capacity-baseline.mdx |    7 +-
 .../availability/tunnel-capacity-intro.mdx    |    1 +
 .../tunnel/catch-all-policy.mdx               |    1 +
 .../tunnel/cgnat-split-tunnels.mdx            |    1 +
 .../cloudflare-one/tunnel/create-tunnel.mdx   |    3 +-
 .../deployment-guides/cloud-create-tunnel.mdx |    3 +-
 .../deployment-guides/cloud-private-ip.mdx    |   22 +-
 .../cloud-public-hostname.mdx                 |    1 +
 .../tunnel/diagnostics/docker.mdx             |   33 +-
 .../tunnel/diagnostics/tunnel-diag-file.mdx   |   24 +-
 .../tunnel/dns-cloudflare-settings.mdx        |    1 +
 .../tunnel/dns-records-intro.mdx              |    1 +
 .../cloudflare-one/tunnel/grpc-support.mdx    |    1 +
 .../tunnel/hostname-format-restrictions.mdx   |   21 +-
 .../tunnel/install-and-run-tunnel.mdx         |    3 +-
 .../locally-managed/tunnel-permissions.mdx    |   20 +-
 .../tunnel/logs/filter-logs.mdx               |    8 +-
 .../tunnel/logs/view-logs-dashboard.mdx       |    1 +
 .../tunnel/logs/view-logs-on-server.mdx       |    1 +
 .../tunnel/metrics/cloudflared.mdx            |    2 +-
 .../tunnel/origin-parameters.mdx              |    4 +-
 .../cloudflare-one/tunnel/package-manager.mdx |    3 +-
 .../cloudflare-one/tunnel/protocols-table.mdx |   26 +-
 .../cloudflare-one/tunnel/run-parameters.mdx  |    6 +-
 .../cloudflare-one/tunnel/tunnel-status.mdx   |   12 +-
 .../tunnel/warp-cli-target-list.mdx           |    2 +-
 .../tunnel/warp-to-tunnel-route-ips.mdx       |   66 +-
 .../warp/client-notification-lag.mdx          |    3 +-
 .../warp/client-orchestration-ips.mdx         |    1 +
 .../warp/device-enrollment-mtls.mdx           |    7 +-
 .../warp/enroll-ios-android.mdx               |    3 +-
 .../cloudflare-one/warp/ldf-best-practice.mdx |    2 +-
 .../warp/managed-networks-sha-256.mdx         |    2 +-
 .../cloudflare-one/warp/manually-reauth.mdx   |    2 +-
 .../cloudflare-one/warp/mdm-policy-file.mdx   |    9 +-
 .../cloudflare-one/warp/os-version-semver.mdx |    3 +-
 .../warp/sha-256-fingerprint.mdx              |    2 +-
 .../warp/support-ticket-best-practices.mdx    |    4 +-
 .../warp/system-requirements/linux.mdx        |   19 +-
 .../warp/system-requirements/macOS.mdx        |   19 +-
 .../warp/system-requirements/windows.mdx      |   19 +-
 .../cloudflare-one/warp/vpn-ip-traffic.mdx    |   10 +-
 .../cloudflare-one/warp/warp-modes.mdx        |    4 +-
 .../partials/containers/instance-types.mdx    |    4 +-
 .../d1/d1-do-supported-sqlite-extensions.mdx  |    4 +-
 .../partials/d1/generate-d1-api-token.mdx     |    2 +-
 .../advanced-ddos/dns-protection-intro.mdx    |    2 +-
 .../advanced-ddos/dns-setup.mdx               |    2 +-
 .../mt-advanced-ddos-systems-onboarding.mdx   |    2 +-
 .../advanced-ddos/tcp-protection-intro.mdx    |    2 +-
 .../advanced-ddos/tcp-setup.mdx               |    2 +-
 .../alerts-and-reports-independent.mdx        |    1 +
 .../ddos-protection/allowlist-ip-spoofing.mdx |    5 +-
 .../ddos-protection/atp-filter-definition.mdx |    3 +-
 .../atp-filters-rules-precedence.mdx          |    1 +
 .../ddos-protection/create-notification.mdx   |    1 +
 .../ddos-protection/ddos-attack-coverage.mdx  |   15 +-
 .../log-and-monitor-behavior-link.mdx         |    2 +-
 .../managed-rulesets/create-override.mdx      |    4 +-
 .../managed-rulesets/evaluation-behavior.mdx  |    5 +-
 .../read-only-rules-description.mdx           |    1 +
 .../managed-rulesets/read-only-rules-note.mdx |    1 +
 .../sensitivity-level-reference.mdx           |   17 +-
 .../test-rules-description.mdx                |    1 +
 .../ddos-protection/override-example.mdx      |   25 +-
 .../ddos-protection/override-logic.mdx        |    7 +-
 .../dmarc-management/domain-spoofing.mdx      |    2 +
 .../partials/dns/a-aaaa-definition.mdx        |    1 +
 src/content/partials/dns/acns-tcns-byoip.mdx  |    3 +-
 .../partials/dns/acns-tcns-conditions.mdx     |    7 +-
 src/content/partials/dns/acns-tcns-intro.mdx  |    3 +-
 .../partials/dns/aname-alias-callout.mdx      |    3 +-
 .../partials/dns/api-field-definitions.mdx    |    1 +
 src/content/partials/dns/cname-definition.mdx |    1 +
 .../partials/dns/cname-flattening-callout.mdx |    1 +
 .../conversion-subdomain-setup-callout.mdx    |    3 +-
 .../partials/dns/dns-errors-ts-action.mdx     |    3 +-
 .../partials/dns/dns-errors-ts-intro.mdx      |    5 +-
 .../partials/dns/dns-nxdomain-warning.mdx     |    5 +-
 src/content/partials/dns/dns-record-steps.mdx |   10 +-
 src/content/partials/dns/dns-scan-intro.mdx   |    1 +
 src/content/partials/dns/dns-scan-note.mdx    |    2 +-
 src/content/partials/dns/dnssec-auto-add.mdx  |    3 +
 .../partials/dns/dnssec-cloudflare-steps.mdx  |    1 +
 .../partials/dns/dnssec-definition.mdx        |    1 +
 .../partials/dns/dnssec-enabled-migration.mdx |    3 +
 .../partials/dns/dnssec-registrar-steps.mdx   |    5 +-
 .../partials/dns/export-dns-records.mdx       |    1 +
 .../partials/dns/internal-dns-beta-note.mdx   |    1 +
 .../dns/internal-dns-view-conditions.mdx      |    4 +-
 .../dns/internal-reference-zone-api.mdx       |   15 +-
 .../dns/internal-reference-zone-intro.mdx     |   11 +-
 .../dns/internal-zones-conditions.mdx         |    4 +-
 .../partials/dns/linked-peers-limit.mdx       |    1 +
 .../partials/dns/minimize-downtime-tip.mdx    |    3 +-
 .../dns/mix-proxied-and-unproxied.mdx         |    3 +
 .../partials/dns/nameserver-preamble.mdx      |    1 +
 .../dns/nameservers-registrar-callout.mdx     |    1 +
 .../partials/dns/ns-advanced-vs-custom.mdx    |    1 +
 .../partials/dns/ns-set-omission-callout.mdx  |    1 +
 src/content/partials/dns/ns-static-ips.mdx    |    3 +-
 .../partials/dns/ns-update-providers.mdx      |   71 +-
 src/content/partials/dns/onboard-warning.mdx  |    1 +
 .../partials/dns/partial-setup-definition.mdx |    3 +-
 .../dns/random-prefix-attack-definition.mdx   |    1 +
 .../partials/dns/records-name-field.mdx       |    8 +-
 .../partials/dns/recover-deleted-domain.mdx   |    1 +
 .../dns/secondary-conversion-unlink.mdx       |    3 +-
 .../partials/dns/secondary-dns-override.mdx   |    1 +
 .../partials/dns/ssltls-subdomains.mdx        |    1 +
 .../partials/dns/subdomain-customization.mdx  |    1 +
 .../partials/dns/third-party-caveat.mdx       |    5 +-
 src/content/partials/dns/tsig-create-api.mdx  |    1 +
 src/content/partials/dns/tsig-create-dash.mdx |    7 +-
 src/content/partials/dns/tsig-definition.mdx  |    3 +-
 src/content/partials/dns/tsig-name-match.mdx  |    1 +
 .../partials/dns/why-disable-dnssec.mdx       |    1 +
 .../partials/dns/zone-defaults-exceptions.mdx |    1 +
 .../partials/dns/zone-file-size-limit.mdx     |    1 +
 .../durable-objects/api-async-kv-legacy.mdx   |    4 +-
 .../durable-objects/api-storage-alarms.mdx    |    2 +-
 .../api-storage-other-methods.mdx             |    2 +-
 .../partials/durable-objects/api-sync-kv.mdx  |    2 +-
 .../do-faq-metrics-and-analytics.mdx          |    4 +-
 .../durable-objects/do-plans-note.mdx         |    2 +-
 .../durable-objects/durable-objects-sql.mdx   |  122 +-
 .../durable-objects/recommend-sqlite-do.mdx   |    2 +-
 .../what-are-durable-objects.mdx              |    2 +-
 .../email-routing-definition.mdx              |    1 +
 .../email-routing/enable-create-worker.mdx    |    1 +
 .../send-emails-workers-intro.mdx             |    3 +-
 .../partials/email-routing/types-bindings.mdx |    1 +
 .../partials/email-security/add-user.mdx      |    3 +-
 .../email-security/auto-retraction.mdx        |   18 +-
 .../bec-directory-guide-compromise-list.mdx   |    1 +
 .../bec-directory-guide-secondary-email.mdx   |    1 +
 .../email-security/contact-support.mdx        |    3 +-
 .../bcc-table-geographic-locations.mdx        |   11 +-
 .../deployment/mx-deployment-values.mdx       |    1 +
 .../deployment/mx-geographic-locations.mdx    |   19 +-
 .../email-security/deployment/o365-gcc.mdx    |    1 +
 ...-use-case-1-3-create-quarantine-policy.mdx |    6 +-
 ...-use-case-2-4-create-quarantine-policy.mdx |   11 +-
 .../o365-use-case-configure-domain.mdx        |   15 +-
 .../o365-use-case-transport-rules.mdx         |   41 +-
 .../deployment/setup-api-overview.mdx         |   21 +-
 .../deployment/setup-inline-overview.mdx      |   13 +-
 .../deployment/setup-overview.mdx             |    1 +
 .../email-security-description.mdx            |    3 +-
 .../email-security/outbound-email.mdx         |    1 +
 .../email-security/rename-area1-to-ces.mdx    |    1 +
 .../partials/email-security/search.mdx        |    9 +-
 .../email-security/service-addresses.mdx      |    1 +
 .../email-security/sso-enforcement.mdx        |    9 +-
 .../account-audit-logs-definition.mdx         |    3 +
 .../account-manage-active-sessions.mdx        |    3 +
 .../account-member-manage-limitation.mdx      |    1 +
 .../fundamentals/api-change-api-key.mdx       |    3 +-
 .../fundamentals/api-combine-filters.mdx      |    9 +-
 .../fundamentals/api-filter-operators.mdx     |   22 +-
 .../partials/fundamentals/api-rate-limits.mdx |   16 +-
 .../partials/fundamentals/api-using-api.mdx   |    3 +
 .../partials/fundamentals/audit-log-api.mdx   |    1 +
 .../create-account-best-practices.mdx         |    1 +
 .../cybersafe-cipa-subcategories.mdx          |   55 +-
 .../fundamentals/cybersafe-configuration.mdx  |    1 +
 .../fundamentals/cybersafe-description.mdx    |    1 +
 .../fundamentals/cybersafe-requirements.mdx   |    1 +
 .../cybersafe-school-eligibility.mdx          |    5 +-
 .../fundamentals/idp-group-deprecation.mdx    |    5 +
 .../fundamentals/lists-import-notes.mdx       |    7 +-
 .../fundamentals/new-token-warning.mdx        |    3 +
 .../fundamentals/pseudo-ipv4-warning.mdx      |    1 +
 .../fundamentals/revoke-active-sessions.mdx   |    3 +-
 .../fundamentals/ubb-recommendation.mdx       |   12 +-
 .../fundamentals/user-permissions-table.mdx   |   19 +-
 .../partials/fundamentals/user-profiles.mdx   |    3 +-
 .../partials/fundamentals/view-audit-log.mdx  |    3 +
 .../fundamentals/what-is-cloudflare.mdx       |    3 +-
 .../zero-downtime-failover-retry-on-error.mdx |    1 +
 .../hyperdrive/create-hyperdrive-binding.mdx  |    7 +-
 .../hyperdrive/create-hyperdrive-config.mdx   |    9 +-
 .../partials/hyperdrive/pooling-mode.mdx      |    1 +
 .../use-postgres-js-to-make-query.mdx         |    2 +-
 .../learning-paths/cache-basic-diagram.mdx    |    1 +
 .../learning-paths/cache-optimization.mdx     |    7 +-
 ...-network-overview-additional-resources.mdx |    3 +-
 .../china-network-overview-navigation.mdx     |   27 +-
 .../cloudflare-tunnels-origin-description.mdx |    7 +-
 .../ddos-definition-and-diagram.mdx           |    3 +-
 .../learning-paths/email-record-origin-ip.mdx |    1 +
 .../learning-paths/r2-series-navigation.mdx   |   55 +-
 .../learning-paths/sase-series-navigation.mdx |   64 +-
 .../learning-paths/warp-series-navigation.mdx |   25 +-
 .../workflows-series-navigation.mdx           |   35 +-
 .../zero-trust/blocklist-restricted-users.mdx |    3 +-
 .../blocklist-security-categories.mdx         |    1 +
 .../configure-device-agent-description.mdx    |    1 +
 .../configure-device-agent-objectives.mdx     |    9 +-
 .../zero-trust/configure-idp.mdx              |    3 +-
 .../zero-trust/connect-devices-objectives.mdx |    7 +-
 .../learning-paths/zero-trust/create-list.mdx |    3 +-
 .../device-enrollment-permissions.mdx         |    3 +-
 .../zero-trust/email-dispositions.mdx         |   15 +-
 .../zero-trust/enable-proxy-intro.mdx         |    1 +
 .../zero-trust/initial-setup-objectives.mdx   |    7 +-
 .../zero-trust/install-agent.mdx              |   26 +-
 .../learning-paths/zero-trust/mdm.mdx         |    3 +-
 .../zero-trust/split-tunnel-settings.mdx      |    7 +-
 .../validate-traffic-in-gateway.mdx           |    9 +-
 .../components-knowledge-callout.mdx          |    1 +
 .../custom-rules-definition.mdx               |    1 +
 .../dns-load-balancing-benefits.mdx           |    1 +
 .../dns-load-balancing-definition.mdx         |    1 +
 .../dns-load-balancing-limitations.mdx        |   15 +-
 .../endpoints-introduction-callout.mdx        |    1 +
 .../load-balancing/fallback-pools.mdx         |    1 +
 .../load-balancing/health-check-diagram.mdx   |    1 +
 .../load-balancing/health-check-regions.mdx   |    1 +
 .../layer-4-load-balancing-definition.mdx     |    3 +
 .../layer-7-load-balancing-benefits.mdx       |   15 +-
 .../layer-7-load-balancing-definition.mdx     |    1 +
 .../load-balancer-create-api.mdx              |  149 +--
 .../load-balancing/load-balancer-create.mdx   |   53 +-
 .../load-balancer-definition.mdx              |    1 +
 .../load-balancing/load-balancing-diagram.mdx |    1 +
 .../load-balancing/monitor-create-api.mdx     |  105 +-
 .../load-balancing/monitor-create.mdx         |    3 +-
 .../monitor-health-check-regions-options.mdx  |    5 +-
 .../load-balancing/monitor-prepare-server.mdx |    3 +
 .../load-balancing/monitor-settings-basic.mdx |   11 +-
 .../monitor-settings-consecutive.mdx          |    3 +
 .../origin-steering-definition.mdx            |    7 +-
 .../origin-steering-policies.mdx              |    1 +
 .../origin-steering-weights-definition.mdx    |    1 +
 .../origin-steering-weights-limitations.mdx   |    1 +
 .../partials/load-balancing/pool-create.mdx   |   31 +-
 .../load-balancing/pool-health-threshold.mdx  |    3 +-
 .../load-balancing/region-mapping.mdx         |    1 +
 .../route-production-traffic.mdx              |    7 +-
 .../session-affinity-by-cookie-process.mdx    |    5 +-
 .../session-affinity-definition.mdx           |    1 +
 .../spectrum-lb-limitations.mdx               |    5 +-
 .../load-balancing/test-domain-setup.mdx      |    1 +
 .../traffic-steering-definition.mdx           |    1 +
 .../unexpected-health-statuses.mdx            |    5 +-
 .../unhealthy-pool-traffic-distribution.mdx   |   10 +-
 .../partials/logs/check-log-retention.mdx     |    1 +
 .../partials/logs/disable-log-retention.mdx   |    1 +
 .../partials/logs/enable-log-retention.mdx    |    1 +
 .../partials/logs/enable-logpush-job.mdx      |    5 +-
 .../partials/logs/enable-read-permissions.mdx |    1 +
 .../partials/logs/filtering-limitations.mdx   |    1 +
 .../account-id-api-key.mdx                    |   20 +-
 .../analytics/set-thresholds-site-health.mdx  |    2 +-
 .../analytics/site-analytics.mdx              |   43 +-
 .../cloudflare-one-connectivity-options.mdx   |   35 +-
 .../cloudflare-wan/custom-ike-id-ipsec.mdx    |   13 +-
 .../cloudflare-wan/get-started.mdx            |   12 +-
 .../cloudflare-wan/load-balancing.mdx         |    2 +-
 .../reference/device-compatibility.mdx        |   60 +-
 .../cloudflare-wan/security-filters.mdx       |    2 +-
 .../cloudflare-wan/third-party/aws.mdx        |    4 +-
 .../third-party/azure-virtual-wan.mdx         |   18 +-
 .../cloudflare-wan/third-party/fitelnet.mdx   |    1 +
 .../cloudflare-wan/third-party/fortinet.mdx   |    2 +
 .../cloudflare-wan/third-party/juniper.mdx    |  218 ++--
 .../cloudflare-wan/third-party/oracle.mdx     |   59 +-
 .../cloudflare-wan/third-party/palo-alto.mdx  |  194 +--
 .../third-party/sophos-firewall.mdx           |    1 +
 .../cloudflare-wan/third-party/velocloud.mdx  |    8 +-
 .../cloudflare-wan/third-party/viptela.mdx    |   36 +-
 .../cloudflare-wan/third-party/yamaha.mdx     |   24 +-
 .../cloudflare-wan/wan-transformation.mdx     |   24 +-
 .../cloudflare-wan/zero-trust/gateway.mdx     |   11 +-
 .../cloudflare-wan/zero-trust/overview.mdx    |    6 +-
 .../zero-trust/security-services.mdx          |   35 +-
 .../cloudflare-wan/zero-trust/tunnel.mdx      |   24 +-
 .../cloudflare-wan/zero-trust/warp.mdx        |    9 +-
 .../cni-product-use-cases.mdx                 |   15 +-
 .../query-magic-transit-bandwidth-graphql.mdx |    3 +-
 ...y-magic-transit-endpoint-health-checks.mdx |  126 +-
 .../query-magic-transit-health-checks.mdx     |    2 +-
 .../ipsec-logs-troubleshooting.mdx            |    8 +-
 .../magic-transit/advertise-prefixes.mdx      |    3 +-
 .../magic-transit/cloudflare-ips.mdx          |    8 +-
 .../mtu-mss/mss-clamping-gre.mdx              |    2 +
 .../mtu-mss/mss-clamping-ipsec.mdx            |    2 +
 .../safely-withdraw-byoip-prefix.mdx          |    8 +-
 .../networking-services/magic-user-role.mdx   |    2 +-
 .../mconn/device-metrics.mdx                  |  106 +-
 .../mconn/licence-keys.mdx                    |    4 +-
 .../mconn/maintenance/activate-connectors.mdx |    2 +-
 .../maintenance/deactivate-connector.mdx      |   42 +-
 .../mconn/maintenance/default-password.mdx    |    2 +-
 .../mconn/maintenance/edit-basic-info.mdx     |   39 +-
 .../maintenance/edit-network-settings.mdx     |   46 +-
 .../mconn/maintenance/edit-sites.mdx          |   34 +-
 .../maintenance/edit-traffic-steering.mdx     |   40 +-
 .../mconn/maintenance/heartbeat.mdx           |   45 +-
 .../maintenance/interrupt-service-window.mdx  |   47 +-
 .../register-hardware-appliance.mdx           |   37 +-
 .../mconn/maintenance/remove-connectors.mdx   |   75 +-
 .../mconn/mconn-reference.mdx                 |   17 +-
 .../breakout-prioritized.mdx                  |  262 ++--
 .../app-aware-policies/netflow.mdx            |   19 +-
 .../app-aware-policies/overview.mdx           |    5 +-
 .../mconn/network-options/dhcp/dhcp-relay.mdx |    9 +-
 .../network-options/dhcp/dhcp-server.mdx      |    9 +-
 .../mconn/network-options/nat-subnet.mdx      |    1 +
 .../network-options/network-segmentation.mdx  |    9 +-
 .../mconn/network-options/routed-subnets.mdx  |    2 +-
 .../networking-services/mconn/overview.mdx    |    2 +-
 .../mconn/troubleshooting/troubleshooting.mdx |   33 +-
 .../mconn/vlan-tagging.mdx                    |    2 +-
 .../mconn/wan-two-tunnels.mdx                 |    2 +-
 .../mnm-auto-advertisement-notifications.mdx  |    2 +-
 .../mnm-magic-transit-integration.mdx         |   10 +-
 .../partials/networking-services/mnm/faqs.mdx |    2 +-
 .../mnm/routers/sflow-config.mdx              |    2 +-
 .../mnm/rules/dynamic-threshold.mdx           |   16 +-
 .../mnm/rules/overview.mdx                    |    2 +-
 .../mnm/rules/rule-notifications.mdx          |   21 +-
 .../mnm/rules/s-flow-ddos-attack.mdx          |   16 +-
 .../mnm/rules/static-threshold.mdx            |   32 +-
 .../mnm/tutorials/graphql-analytics.mdx       |    1 +
 ...-vendor-guidelines-mss-settings-origin.mdx |    6 +-
 .../reference/longest-prefix-match.mdx        |    2 +-
 .../traffic-steering-region-codes.mdx         |   22 +-
 .../reference/tunnel-health-checks.mdx        |   23 +-
 .../routing/anycast-warning.mdx               |    2 +-
 .../routing/bgp-config-steps.mdx              |   18 +-
 .../configure-cloudflare-source-ips.mdx       |    2 -
 .../routing/mcn-cloudflare-wan-on-ramps.mdx   |   18 +-
 .../networking-services/sites/sites-brief.mdx |    2 +-
 .../networking-services/sites/sites.mdx       |  156 ++-
 .../troubleshoot-connectivity.mdx             |   17 +-
 .../check-tunnel-healthchecks-dash.mdx        |  121 +-
 .../health-checks-compatible-cmb-eu.mdx       |    2 +-
 .../magic-tunnel-health-alerts.mdx            |   33 +-
 .../tunnel-health/mconn-heartbeat-health.mdx  |    2 +-
 .../troubleshoot-tunnel-health.mdx            |  146 +--
 .../virtual-networks-concept.mdx              |   39 +-
 .../partials/notifications/get-started.mdx    |    1 +
 src/content/partials/pages/c3-adapter.mdx     |    3 +
 .../pages/c3-run-command-no-directory.mdx     |    7 +-
 .../pages/cli-precedence-over-file.mdx        |    3 +
 .../partials/pages/custom-domain-steps.mdx    |    1 -
 .../pages/deploy-to-pages-steps-no-preset.mdx |    1 -
 .../deploy-to-pages-steps-with-preset.mdx     |    1 -
 src/content/partials/pages/do-note.mdx        |    1 +
 .../pages/framework-guides/create-gh-repo.mdx |    1 +
 .../create-github-repository-prefix.mdx       |    1 +
 .../framework-guides/git-integration.mdx      |    3 +-
 .../pages/framework-guides/learn-more.mdx     |    3 +-
 .../pages/get-started-git-connect-pages.mdx   |    5 +-
 .../pages/get-started-git-manage-site.mdx     |   11 +-
 .../pages/git-integration-warning.mdx         |    3 +
 .../partials/pages/prod-branch-update.mdx     |    1 +
 .../pages/tutorials-before-you-start.mdx      |    1 +
 .../partials/pages/web-analytics-setup.mdx    |    2 +-
 src/content/partials/queues/enable-queues.mdx |    2 +-
 .../event-subscriptions/access-events.mdx     |   58 +-
 .../event-subscriptions/artifacts-events.mdx  |  366 +++---
 .../queues/event-subscriptions/kv-events.mdx  |   56 +-
 .../queues/event-subscriptions/r2-events.mdx  |   60 +-
 .../super-slurper-events.mdx                  |  202 +--
 .../event-subscriptions/vectorize-events.mdx  |   62 +-
 .../event-subscriptions/workers-ai-events.mdx |   90 +-
 .../workers-builds-events.mdx                 |  264 ++--
 .../event-subscriptions/workflows-events.mdx  |  180 +--
 .../partials/r2/custom-domain-steps.mdx       |    1 -
 .../partials/r2/link-to-workers-r2-api.mdx    |    2 +-
 .../partials/r2/migrator-etag-caveat.mdx      |    3 +-
 .../common/create-your-own-ui-examples.mdx    |    5 +-
 .../common/default-meeting-examples.mdx       |    5 +-
 .../web/breakout-room-close-breakout.mdx      |   13 +-
 .../web/breakout-room-creation-sdk-api.mdx    |   17 +-
 .../breakout-room-fetch-meetings-sdk-api.mdx  |   14 +-
 .../breakout-room-handle-breakout-events.mdx  |   11 +-
 ...breakout-room-move-participant-sdk-api.mdx |   19 +-
 ...t-room-move-preset-participant-sdk-api.mdx |   15 +-
 .../web/breakout-room-permission-check.mdx    |   16 +-
 .../realtimekit/web/language-pack-json.mdx    |  822 ++++++------
 .../description-of-design-guides.mdx          |    1 +
 ...scription-of-ref-architecture-diagrams.mdx |    1 +
 .../description-of-ref-architectures.mdx      |    1 +
 .../what-is-cloudflare-link.mdx               |    3 +-
 .../partials/registrar/email-verification.mdx |    3 +
 .../partials/registrar/enable-dnssec.mdx      |    3 +-
 .../registrar/icann-unverified-email.mdx      |    3 +-
 .../partials/registrar/requirements.mdx       |    1 +
 .../partials/registrar/restrictions.mdx       |   12 +-
 .../partials/registrar/verify-dnssec.mdx      |    1 +
 .../configuration-rule-link-to-examples.mdx   |    1 +
 .../rules/configuration-rule-promotion.mdx    |    3 +
 .../partials/rules/error-pages-list.mdx       |    1 +
 .../partials/rules/page-rules-migration.mdx   |    1 +
 .../rules/rules-creation-workflow.mdx         |    1 +
 .../partials/rules/rules-templates.mdx        |    6 +-
 .../rules/terraform-additional-resources.mdx  |    5 +-
 .../rules/transform/header-valid-names.mdx    |    5 +-
 .../rules/transform/header-valid-values.mdx   |    5 +-
 .../ruleset-engine/max-expression-length.mdx  |    1 +
 .../ruleset-engine/rule-position-values.mdx   |    7 +-
 .../brand-protection-alerts.mdx               |    1 +
 .../brand-protection-definition.mdx           |    3 +-
 .../security-center/scan-frequency.mdx        |    3 +-
 .../security-center/scan-properties.mdx       |    9 +-
 .../security-insights-definition.mdx          |    1 +
 .../partials/smart-shield/argo-analytics.mdx  |    2 +-
 .../partials/smart-shield/argo-intro.mdx      |    2 +-
 .../concurrent-connections-explainer.mdx      |    2 +-
 .../smart-shield/dcei-pool-requirements.mdx   |    2 +-
 .../smart-shield/health-checks-analytics.mdx  |    2 +-
 .../smart-shield/health-checks-intro.mdx      |    2 +-
 .../smart-shield/health-checks-regions.mdx    |    4 +-
 .../smart-shield/smart-shield-callout.mdx     |    2 +-
 .../partials/smart-shield/zone-lockdown.mdx   |    2 +-
 .../spectrum-with-load-balancer-api.mdx       |   63 +-
 .../spectrum-with-load-balancer-dash.mdx      |    3 +-
 .../partials/speed/rocket-loader-csp.mdx      |    3 +-
 src/content/partials/speed/user-agents.mdx    |   10 +-
 .../ssl/acm-ca-hostnames-conditions.mdx       |    1 +
 src/content/partials/ssl/acm-definition.mdx   |    1 +
 .../partials/ssl/acm-validate-cert.mdx        |    5 +-
 .../ssl/aop-per-hostname-upload-cert.mdx      |    3 +-
 .../partials/ssl/caa-records-added-by-cf.mdx  |    3 +-
 .../partials/ssl/caa-records-definition.mdx   |    1 +
 .../ssl/change-encryption-mode-api.mdx        |    1 +
 .../ssl/change-encryption-mode-dash.mdx       |    1 +
 .../ssl/cipher-suites-api-linkout.mdx         |    3 +-
 .../partials/ssl/cipher-suites-definition.mdx |    1 +
 .../ssl/cipher-suites-saas-linkout.mdx        |    3 +-
 .../ssl/ciphers-api-general-notes.mdx         |    2 +-
 .../partials/ssl/cname-cert-verification.mdx  |    1 +
 src/content/partials/ssl/csr-definition.mdx   |    1 +
 .../partials/ssl/custom-cert-ciphers.mdx      |    7 +-
 .../ssl/custom-cert-openssl-commands.mdx      |    1 +
 .../ssl/custom-certificates-definition.mdx    |    1 +
 .../custom-origin-trust-store-definition.mdx  |    1 +
 .../partials/ssl/dcv-certificate-renewal.mdx  |    9 +-
 .../partials/ssl/dcv-conflicting-records.mdx  |    3 +-
 src/content/partials/ssl/dcv-definition.mdx   |    1 +
 .../ssl/dcv-invalid-token-situations.mdx      |    1 +
 .../partials/ssl/dcv-path-security.mdx        |    1 +
 .../partials/ssl/dcv-renewal-fallback.mdx     |    1 +
 .../partials/ssl/dcv-validate-patch.mdx       |    1 +
 .../ssl/encryption-mode-definition.mdx        |    1 +
 .../ssl/enforce-https-recommendation.mdx      |    1 +
 .../partials/ssl/error-rate-limiting.mdx      |    1 +
 .../ssl/generic-validation-process.mdx        |    1 +
 .../partials/ssl/geokey-manager-v1.mdx        |    1 +
 .../ssl/get-started-additional-features.mdx   |    7 +-
 .../ssl/http-cname-validation-process.mdx     |    1 +
 .../partials/ssl/http-to-txt-schedule.mdx     |    3 +-
 .../partials/ssl/keyless-ssl-definition.mdx   |    1 +
 .../partials/ssl/keyless-tunnel-setup.mdx     |    1 +
 .../partials/ssl/keyless-upload-preamble.mdx  |    1 +
 .../partials/ssl/origin-ca-pause-error.mdx    |    3 +-
 .../ssl/partial-zone-acm-dcv-nonwildcard.mdx  |    8 +-
 .../ssl/partial-zone-acm-dcv-wildcard.mdx     |    5 +-
 src/content/partials/ssl/ssl-mode-errors.mdx  |    1 +
 src/content/partials/ssl/ssl-mode-no-aop.mdx  |    1 +
 .../ssl/ssl-recommender-post-setup.mdx        |    3 +-
 .../partials/ssl/ssl-recommender-prereqs.mdx  |    7 +-
 src/content/partials/ssl/test-tls-version.mdx |    3 +-
 .../ssl/tls-1.3-cipher-limitations.mdx        |    1 +
 .../ssl/total-tls-character-limitation.mdx    |    3 +-
 .../partials/ssl/txt-validation-api.mdx       |   53 +-
 .../partials/ssl/txt-validation-dashboard.mdx |    1 +
 .../ssl/txt-validation-definition.mdx         |    1 +
 .../partials/ssl/txt-validation-preamble.mdx  |    1 +
 .../ssl/universal-ssl-enable-full.mdx         |    1 +
 .../partials/ssl/universal-ssl-validity.mdx   |    3 +-
 .../ssl/ussl-limitations-solutions.mdx        |    7 +-
 .../partials/ssl/ussl-limitations-table.mdx   |    1 +
 .../partials/ssl/validation-level-note.mdx    |    1 +
 .../stream/android_playback_code_snippet.mdx  |    1 +
 .../stream/chromecast_limitations.mdx         |    1 +
 .../stream/ios_playback_code_snippet.mdx      |    1 +
 src/content/partials/stream/prereqs.mdx       |    3 +
 .../prereqs_first_start_live_streaming.mdx    |    3 +
 .../partials/stream/srt-supported-modes.mdx   |    3 +
 .../directory-listing-definition.mdx          |    2 +-
 src/content/partials/style-guide/icons.mdx    |    2 +-
 .../style-guide/public-stats-definition.mdx   |    2 +-
 .../partials/style-guide/tab-guidance.mdx     |    4 +-
 .../partials/style-guide/table-guidelines.mdx |    2 +-
 src/content/partials/support/2fa-enable.mdx   |    1 +
 src/content/partials/support/2fa-overview.mdx |    1 +
 .../partials/tenant/account-definition.mdx    |    1 +
 .../tenant/account-details-preamble.mdx       |    1 +
 .../partials/tenant/account-details.mdx       |   23 +-
 .../partials/tenant/account-preamble.mdx      |    1 +
 .../partials/tenant/create-account-api.mdx    |   70 +-
 .../partials/tenant/create-account-dash.mdx   |    1 +
 .../tenant/create-account-subscription.mdx    |   20 +-
 .../tenant/create-zone-subscription.mdx       |   24 +-
 .../partials/tenant/resource-definition.mdx   |    1 +
 .../tenant/tenant-admin-definition.mdx        |    1 +
 .../partials/tenant/tenant-definition.mdx     |    1 +
 .../tenant/tenant-details-preamble.mdx        |    1 +
 .../partials/tenant/tenant-details.mdx        |    5 +
 .../partials/tenant/user-definition.mdx       |    1 +
 .../partials/terraform/create-r2-buckets.mdx  |    1 +
 .../terraform/find-ids-managed-rulesets.mdx   |    5 +-
 src/content/partials/terraform/find-ids.mdx   |    5 +-
 .../import-delete-existing-rulesets.mdx       |    5 +-
 .../partials/terraform/v4-code-snippets.mdx   |    3 +-
 .../partials/terraform/v5-code-snippets.mdx   |    1 +
 .../partials/time-services/ntp-definition.mdx |    1 +
 .../partials/turnstile/challenge-behavior.mdx |    1 +
 .../partials/turnstile/privacy-policy.mdx     |    2 +-
 .../partials/turnstile/proxied-hostnames.mdx  |    1 +
 .../turnstile/security-requirements.mdx       |    2 +
 .../partials/turnstile/siteverify-warning.mdx |    1 +
 src/content/partials/turnstile/siteverify.mdx |    3 +-
 .../partials/turnstile/test-secret-key.mdx    |    3 +-
 .../partials/turnstile/test-sitekey.mdx       |    3 +-
 .../turnstile/troubleshooting-steps.mdx       |   21 +-
 .../partials/turnstile/widget-components.mdx  |   11 +-
 .../partials/vectorize/vectorize-ga.mdx       |    3 +
 .../partials/vectorize/vectorize-pricing.mdx  |    8 +-
 .../create-environment-situation.mdx          |    1 +
 .../version-management/edit-version.mdx       |    7 +-
 .../enable-default-creation.mdx               |    7 +-
 .../version-management/enable-versioning.mdx  |    5 +-
 .../environment-defaults.mdx                  |    7 +-
 .../environment-definition.mdx                |    1 +
 .../production-read-only-default.mdx          |    1 +
 .../version-management/promote-version.mdx    |    4 +-
 .../version-management/test-version.mdx       |    3 +-
 .../version-management/version-definition.mdx |    1 +
 .../waf/api-create-ruleset-with-rule.mdx      |    1 +
 src/content/partials/waf/list-advantages.mdx  |    7 +-
 src/content/partials/waf/managed-lists.mdx    |    4 +-
 .../waf/open-ports-blocked-traffic.mdx        |    1 +
 .../waf/rate-limiting-best-practices.mdx      |   11 +-
 .../waf/rate-limiting-rule-parameters.mdx     |   15 +-
 .../partials/waf/rules-next-steps-table.mdx   |    6 +-
 .../waiting-room/change-queueing-method.mdx   |    7 +-
 .../partials/waiting-room/queue-all.mdx       |    1 +
 .../partials/waiting-room/queue-some.mdx      |    1 +
 .../partials/warp-client/modes-options.mdx    |   13 +-
 .../web-analytics-definition.mdx              |    1 +
 .../web-analytics-notifications.mdx           |    1 +
 .../web-analytics-proxied-setup.mdx           |    1 +
 .../web-analytics-troubleshooting.mdx         |    3 +
 .../partials/web3/cloudflare-settings.mdx     |    1 +
 .../partials/web3/create-gateway-api.mdx      |   31 +-
 .../partials/web3/pricing-page-reference.mdx  |    3 +
 .../workers-ai/custom_requirements.mdx        |    3 +
 .../partials/workers-ai/file_issues.mdx       |    3 +
 .../workers-ai/openai-compatibility.mdx       |    1 +
 .../workers-vpc/create-tunnel-steps.mdx       |    2 +-
 .../partials/workers-vpc/required-roles.mdx   |    1 +
 .../workers/ai-local-usage-charges.mdx        |    3 +
 .../partials/workers/c3-definition.mdx        |    1 +
 .../partials/workers/compute-per-request.mdx  |    3 +-
 .../workers/content_and_contentoptions.mdx    |    3 +
 .../workers/dash-creation-next-steps.mdx      |    1 -
 .../partials/workers/env_and_secrets.mdx      |    1 +
 .../partials/workers/envvar-example.mdx       |    1 +
 .../workers/fetch-html-example-js.mdx         |   15 +-
 .../partials/workers/get-started-dash.mdx     |    3 +-
 .../workers/isolate-cpu-flexibility.mdx       |    1 +
 .../partials/workers/isolate-description.mdx  |    1 +
 .../partials/workers/limits_increase.mdx      |    3 +
 .../partials/workers/nodejs-compat-howto.mdx  |    2 +
 .../partials/workers/playground-callout.mdx   |    3 +
 src/content/partials/workers/prereqs.mdx      |    8 +-
 .../partials/workers/redirect-example-js.mdx  |   11 +-
 .../partials/workers/remote-binding-note.mdx  |    2 +-
 .../workers/request-dot-clone-warning.mdx     |    2 +-
 .../respond-another-site-example-js.mdx       |   27 +-
 .../workers/return-html-example-js.mdx        |   17 +-
 .../workers/return-json-example-js.mdx        |   13 +-
 .../workers/service-binding-rpc-example.mdx   |    1 +
 .../workers/storage-products-table.mdx        |   22 +-
 .../workers/testing-pages-functions.mdx       |    3 +
 .../workers/tutorials-before-you-start.mdx    |    1 +
 .../partials/workers/workers_logs_pricing.mdx |   11 +-
 .../workers/wrangler-commands/containers.mdx  |   16 +-
 .../workers/wrangler-commands/r2-sql.mdx      |   11 +-
 .../partials/workers/wrangler-commands/r2.mdx |   98 +-
 .../workflows/workflows-type-parameters.mdx   |    3 +-
 .../partials/zaraz/zaraz-definition.mdx       |    1 +
 src/pages/agent-setup/index.astro             |   49 +-
 src/pages/plans.astro                         |    4 +-
 3654 files changed, 34085 insertions(+), 33812 deletions(-)

diff --git a/.agents/references/procedures.md b/.agents/references/procedures.md
index 04454ac541394b5..b335d124dc55fb0 100644
--- a/.agents/references/procedures.md
+++ b/.agents/references/procedures.md
@@ -11,7 +11,10 @@ Wrap all multi-step procedures in the `Steps` component:
 ```mdx
 import { Steps } from "~/components";
 
-<Steps>1. Step one 2. Step two</Steps>
+<Steps>
+1. Step one
+2. Step two
+</Steps>
 ```
 
 Single-step procedures: fold the step into the introductory sentence rather than making a one-item list.
@@ -23,17 +26,14 @@ Sub-steps use lowercase letters (a, b, c). Sub-sub-steps use lowercase Roman num
 ## Writing rules
 
 **Order**: state location before action, purpose before action.
-
 - "In the **DNS** section, select **Add record**." (location → action)
 - "To delete the rule, select **Delete**." (purpose → action)
 
 **First step**: consolidate login and navigation. Do not make "Log in" its own step if the next step is navigating somewhere.
-
 - "Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **DNS** > **Records**."
 - Write "log in to" (three words), not "log into".
 
 **Optional steps**: prefix with `(Optional)` as the first word.
-
 - "(Optional) Enter a description for the rule."
 
 **Enter key**: if the user must press **Enter** after a step, include it in that step.
@@ -62,10 +62,10 @@ Provide a screenshot when the UI element is genuinely hard to locate without one
 
 ## Terminology in procedures
 
-| Use                | Not              |
-| ------------------ | ---------------- |
-| select             | click            |
-| go to              | navigate to      |
+| Use | Not |
+| --- | --- |
+| select | click |
+| go to | navigate to |
 | turn on / turn off | enable / disable |
-| log in to          | log into         |
-| (Optional)         | Optional:        |
+| log in to | log into |
+| (Optional) | Optional: |
diff --git a/.agents/skills/dependabot-review/SKILL.md b/.agents/skills/dependabot-review/SKILL.md
index 1b684c642fe06e3..9ad186440519dd9 100644
--- a/.agents/skills/dependabot-review/SKILL.md
+++ b/.agents/skills/dependabot-review/SKILL.md
@@ -62,7 +62,7 @@ grep -r "require(['\"]<package>['\"]" src/ worker/ bin/ -l
 grep '"<package>"' package.json
 
 # If transitive, who pulls it in?
-node -e "const lock = require('./pnpm-lock.yaml'); ..."
+node -e "const lock = require('./pnpm-lock.yaml'); ..." 
 # or just:
 grep -A2 '"<package>"' pnpm-lock.yaml | grep -v "^--$" | head -20
 ```
@@ -79,7 +79,6 @@ grep -r "<method_name>\|<export_name>" src/ worker/ bin/ --include="*.ts" --incl
 ```
 
 For Astro/MDX source files under `src/content/docs/`, map them to their route:
-
 - `src/content/docs/workers/get-started/index.mdx` → `/workers/get-started/`
 - `src/content/docs/pages/platform/limits.mdx` → `/pages/platform/limits/`
 
@@ -89,13 +88,13 @@ If more than ~5 files use the changed API, list a representative sample (pick th
 
 Rate the probability that this bump causes a **visible change to the docs site**:
 
-| Rating       | Meaning                                                                                       |
-| ------------ | --------------------------------------------------------------------------------------------- |
-| **None**     | Package not used directly; transitive only; or only internal/type changes                     |
-| **Very Low** | Direct dependency, but changed APIs are not called in this repo                               |
-| **Low**      | Changed APIs are called, but only in build tooling (not runtime or content rendering)         |
-| **Medium**   | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
-| **High**     | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior       |
+| Rating | Meaning |
+|--------|---------|
+| **None** | Package not used directly; transitive only; or only internal/type changes |
+| **Very Low** | Direct dependency, but changed APIs are not called in this repo |
+| **Low** | Changed APIs are called, but only in build tooling (not runtime or content rendering) |
+| **Medium** | Changed APIs affect content rendering (Astro components, MDX processing, syntax highlighting) |
+| **High** | Changed APIs affect output seen by users — rendered HTML, search index, Worker behavior |
 
 For **security fixes**: note what the vulnerability affects and whether our usage is in the vulnerable code path.
 
@@ -143,6 +142,5 @@ For grouped PRs (non-major group), the PR body lists each package separately. Pr
 ### Packages with no public changelog
 
 If a package has no changelog and the upstream repo is private or unavailable:
-
 1. Check npm for version diff: `npm diff <package>@<old> <package>@<new>`
 2. If that also fails, note it explicitly and rate impact conservatively based on usage alone.
diff --git a/.agents/skills/docs-review/SKILL.md b/.agents/skills/docs-review/SKILL.md
index 7ba37ceae99136b..4f37fbdb5b612a6 100644
--- a/.agents/skills/docs-review/SKILL.md
+++ b/.agents/skills/docs-review/SKILL.md
@@ -150,19 +150,19 @@ Read full files for context — code that looks wrong in a diff may be correct i
 
 See `.agents/references/style-guide.md` for the full rules. Quick reference:
 
-| Rule                     | Detail                                                                                            |
-| ------------------------ | ------------------------------------------------------------------------------------------------- |
-| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                       |
-| Component imports        | Every component used must be imported from `~/components`                                         |
-| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                           |
-| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                  |
-| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                  |
-| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                       |
-| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs |
-| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                      |
-| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc. |
-| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                  |
-| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover |
+| Rule                     | Detail                                                                                               |
+| ------------------------ | ---------------------------------------------------------------------------------------------------- |
+| Unescaped MDX characters | `{`, `}`, `<`, `>` in prose must be escaped or in backticks                                          |
+| Component imports        | Every component used must be imported from `~/components`                                            |
+| Workers code             | Must use `TypeScriptExample`, not bare `js`/`ts` fences                                              |
+| Config blocks            | Must use `WranglerConfig` with TOML input; use `$today` for `compatibility_date`                     |
+| Package install commands | Must use `PackageManagers`, not bare `sh` fences                                                     |
+| Code block languages     | Lowercase, from the supported set — see `.agents/references/style-guide.md`                          |
+| Internal links           | Root-relative paths, trailing slash, no file extensions, no full `developers.cloudflare.com` URLs    |
+| Frontmatter              | `title` and `description` required; `pcx_content_type` must be a valid value                         |
+| Writing style            | See `.agents/references/style-guide.md` — covers voice, contractions, terminology, headings, etc.    |
+| Code correctness         | For type checking, API usage, and binding patterns, load the `code-review` skill                     |
+| Accuracy                 | Claims must be substantiated — link to sources of truth, do not re-explain what other pages cover    |
 
 ### 3. Assess What to Flag
 
diff --git a/.agents/skills/eli5/SKILL.md b/.agents/skills/eli5/SKILL.md
index 3158464814dc939..47c5f5e78f0cc91 100644
--- a/.agents/skills/eli5/SKILL.md
+++ b/.agents/skills/eli5/SKILL.md
@@ -67,7 +67,7 @@ Use this skill for content that targets a broad or mixed audience — not every
 
 - **Developer-focused API and SDK references** (e.g. Workers, D1, R2, Durable Objects, KV) — the audience is developers who are expected to know programming concepts, database terminology, and API conventions
 - **Code-heavy tutorials targeting developers** — readers self-select into these and already have the prerequisite knowledge
-- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon _is_ the content
+- **Configuration references with purely technical audiences** — parameter tables, CLI references, and schema docs where jargon *is* the content
 
 **Use your judgment for everything else.** Ask: "Would a reasonable reader of this page already know these terms?" If yes, this skill adds little value. On the other hand, if the following are true, this skill could provide significant value.
 
@@ -105,13 +105,13 @@ I read the file, detect sections, analyze organization, and identify the content
 
 After detection, I ask you to confirm the content type. Different types require different strategies:
 
-| Type      | Strategy                                         |
-| --------- | ------------------------------------------------ |
-| Overview  | Problem → Solution → Benefit                     |
-| Concept   | Analogy → Plain explanation → Technical details  |
-| How To    | Context → Multi-path steps (Dashboard + API)     |
+| Type | Strategy |
+|------|----------|
+| Overview | Problem → Solution → Benefit |
+| Concept | Analogy → Plain explanation → Technical details |
+| How To | Context → Multi-path steps (Dashboard + API) |
 | Reference | Use-case organization with two-tier descriptions |
-| Tutorial  | Progressive complexity with code explanations    |
+| Tutorial | Progressive complexity with code explanations |
 
 **3. Apply Enhancement Constraints**
 
@@ -225,7 +225,7 @@ These are the highest-risk categories when documentation has been simplified. Pr
 
 1. **Simplified mechanism descriptions** — Any "how it works" explanation added during simplification that was not in the original. These carry the highest risk: a plausible-sounding explanation that describes the wrong mechanism is worse than the original jargon. Verify the actual mechanism against the source docs in this repository.
 
-2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies _where_ crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
+2. **Misleading nuance** — Statements that are not outright wrong but flatten important nuance, creating a wrong mental model. Example: "Cloudflare generates a `robots.txt` file that instructs AI crawlers to stay away from your content" is misleading — `robots.txt` is a per-path allow/disallow mechanism, not a blanket block. The sentence omits that it specifies *where* crawlers may and may not go. Flag any statement where the simplification loses a meaningful distinction.
 
 3. **Net-new claims** — Any explanation, context, or framing added during simplification that was not present in the original document. Every piece of new information requires a citation. If the original said "zones pair with resolver policies" and the simplification adds "based on source IP, user identity, or domain," verify that all three of those selectors are actually supported.
 
@@ -249,12 +249,12 @@ These are the highest-risk categories when documentation has been simplified. Pr
    - **low** — Claim is minor or widely accepted common knowledge.
 5. **Report** — Present findings in this format:
 
-| #   | Claim (exact text)                                  | Source                                                                                          | Status                   |
-| --- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------ |
-| 1   | "Workers KV supports keys up to 512 bytes"          | `src/content/docs/kv/api/write-key-value-pairs.mdx`                                             | ✅ sourced               |
-| 2   | "Latency is under 50 ms globally"                   | —                                                                                               | ❌ unsourced (high)      |
-| 3   | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
-| 4   | "zones pair with resolver policies"                 | present in original — `path/to/file.mdx:34`                                                     | ✅ sourced (original)    |
+| # | Claim (exact text) | Source | Status |
+|---|---|---|---|
+| 1 | "Workers KV supports keys up to 512 bytes" | `src/content/docs/kv/api/write-key-value-pairs.mdx` | ✅ sourced |
+| 2 | "Latency is under 50 ms globally" | — | ❌ unsourced (high) |
+| 3 | "instructs crawlers to stay away from your content" | `src/content/docs/bots/robots-txt.mdx` — source says per-path allow/disallow, not blanket block | ⚠️ misleading (critical) |
+| 4 | "zones pair with resolver policies" | present in original — `path/to/file.mdx:34` | ✅ sourced (original) |
 
 ### Rules
 
@@ -397,12 +397,10 @@ Produce output following this template exactly. All sections are required.
 ## Simplification Overview
 
 **What was confusing:**
-
 - [Issue pattern 1]
 - [Issue pattern 2]
 
 **Approach taken:**
-
 - [Strategy 1]
 - [Strategy 2]
 
@@ -411,17 +409,14 @@ Produce output following this template exactly. All sections are required.
 ## Section: [Original Heading]
 
 ### Original Content
-
 [Exact text from source, preserved]
 
 ### Issues Identified
-
 **Jargon:** [terms and why problematic]
 **Assumptions:** [unstated prerequisites]
 **Unclear Logic:** [structural issues]
 
 ### Simplified Version
-
 **In Plain Language:** [One-sentence distillation]
 **What It Is:** [2-3 paragraphs building from basics]
 **Why It Matters:** [Benefits and value]
@@ -439,9 +434,9 @@ Produce output following this template exactly. All sections are required.
 
 ## Terminology Index
 
-| Term   | Line          | Defined? | Suggested Action                                                        |
-| ------ | ------------- | -------- | ----------------------------------------------------------------------- |
-| [term] | [line number] | Yes/No   | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
+| Term | Line | Defined? | Suggested Action |
+| ---- | ---- | -------- | ---------------- |
+| [term] | [line number] | Yes/No | Add glossary tooltip / Add cross-link to [page] / Add inline definition |
 
 ---
 
@@ -454,9 +449,9 @@ Produce output following this template exactly. All sections are required.
 
 Line-numbered recommendations for further improvements:
 
-| Line(s) | Current Approach | Suggested Enhancement | Why                             | Priority        |
-| ------- | ---------------- | --------------------- | ------------------------------- | --------------- |
-| [lines] | [what exists]    | [what to change]      | [why it improves accessibility] | High/Medium/Low |
+| Line(s) | Current Approach | Suggested Enhancement | Why | Priority |
+| ------- | ---------------- | --------------------- | --- | -------- |
+| [lines] | [what exists] | [what to change] | [why it improves accessibility] | High/Medium/Low |
 ```
 
 ## References
diff --git a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
index a81b5834b7aae6c..6d9e9f57671e88a 100644
--- a/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
+++ b/.agents/skills/eli5/recommendations/internal-dns/index.eli5.mdx
@@ -193,7 +193,6 @@ For detailed step-by-step setup instructions, see the [Get started guide](/dns/i
 This overview was enhanced with inline context explaining when you'd use Internal DNS, step-by-step query flow showing how views work, and three detailed use case examples with real-world scenarios. Added explanations of key concepts (views, zone referencing, privacy model) and a "Getting started" checklist.
 
 **What was added:**
-
 - Opening context: When to use Internal DNS with concrete example (lines 34-36)
 - Architecture explanations: On-ramp options, why zones are private (lines 42-44, 48-50)
 - Views explanation: Why views matter and how they enable customization (lines 73-75)
diff --git a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
index 4d1539a961ee745..742a86dc6ee14df 100644
--- a/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
+++ b/.agents/skills/eli5/references/EXAMPLES_REFERENCE.md
@@ -26,7 +26,6 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Purpose:** Help users quickly understand what a product/feature is and decide if they need it.
 
 **Required Elements:**
-
 - Opening benefit statement (what problem this solves)
 - Problem/Solution/Benefit structure
 - "Perfect for" self-identification section
@@ -34,7 +33,6 @@ Once content type is detected and validated, I apply type-specific simplificatio
 - Technical architecture separated to bottom
 
 **Analysis Focus:**
-
 - Does opening paragraph answer "what" and "why"?
 - Are features explained with benefits, not just descriptions?
 - Is there a clear call-to-action?
@@ -51,36 +49,32 @@ Once content type is detected and validated, I apply type-specific simplificatio
 **Pattern Example:**
 
 ❌ **Before (Technical-first):**
-
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8
-isolates for serverless code execution with sub-millisecond cold
+Product X is a distributed edge computing platform utilizing V8 
+isolates for serverless code execution with sub-millisecond cold 
 start performance.
 
 Features:
-
 - Global anycast network deployment
 - Automatic scaling and load distribution
 - Pay-per-request pricing model
 ```
 
 ✅ **After (Benefit-first):**
-
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds,
+Run code worldwide without managing servers. Deploy in seconds, 
 scale automatically, pay only for what you use.
 
 **What problem it solves:**
-Maintaining global infrastructure is expensive and complex. Product X
-runs your code in 300+ cities automatically, handling all the
+Maintaining global infrastructure is expensive and complex. Product X 
+runs your code in 300+ cities automatically, handling all the 
 infrastructure for you.
 
 **Perfect for:**
-
 - Applications needing fast global performance
 - Teams wanting to skip server management
 - Projects with variable traffic (scale from zero to millions)
@@ -89,7 +83,7 @@ infrastructure for you.
 
 ---
 
-**For technical users:** Built on V8 isolates with global anycast
+**For technical users:** Built on V8 isolates with global anycast 
 deployment. [Architecture details →]
 ```
 
@@ -100,7 +94,6 @@ deployment. [Architecture details →]
 **Purpose:** Build understanding of WHY something works the way it does.
 
 **Required Elements:**
-
 - Opening analogy or visual (accessible to all)
 - Plain language definition
 - "Why it matters" business value
@@ -109,7 +102,6 @@ deployment. [Architecture details →]
 - Technical details for advanced users (separated)
 
 **Analysis Focus:**
-
 - Is there an analogy early in the content?
 - Does it explain WHY before HOW?
 - Are use cases concrete and realistic?
@@ -126,51 +118,47 @@ deployment. [Architecture details →]
 **Pattern Example:**
 
 ❌ **Before (Technical-only):**
-
 ```markdown
 ## Rate Limiting
 
-Rate limiting implements token bucket algorithms to control request
-throughput based on configurable parameters including burst size and
+Rate limiting implements token bucket algorithms to control request 
+throughput based on configurable parameters including burst size and 
 refill rate. Requests exceeding limits receive 429 status codes.
 ```
 
 ✅ **After (Layered explanation):**
-
 ```markdown
 ## Rate Limiting
 
-**Think of it like:** A nightclub with maximum capacity. Even if
-1,000 people want to enter at once, you only let a controlled number
+**Think of it like:** A nightclub with maximum capacity. Even if 
+1,000 people want to enter at once, you only let a controlled number 
 in at a time to keep things manageable.
 
 **What it is:**
-Rate limiting controls how many requests can hit your website in a
-given time period. Without it, a sudden spike—whether from real
+Rate limiting controls how many requests can hit your website in a 
+given time period. Without it, a sudden spike—whether from real 
 users or attackers—could overwhelm your server.
 
 **Why you need it:**
-
 - Prevents DDoS attacks from taking your site down
 - Stops bots from scraping your content
 - Ensures fair usage across all users
 - Keeps infrastructure costs predictable
 
 **How it works:**
-You set a rule like "100 requests per minute per IP address." When
-someone exceeds this limit, we block additional requests until the
+You set a rule like "100 requests per minute per IP address." When 
+someone exceeds this limit, we block additional requests until the 
 time window resets.
 
 **Real scenarios:**
-
 - E-commerce site during Black Friday preventing bot purchases
 - API preventing scraping of product catalog
 - Forum preventing spam post flooding
 
 ---
 
-**For technical users:** Implements token bucket algorithm with
-configurable burst size and refill rates. Returns 429 status with
+**For technical users:** Implements token bucket algorithm with 
+configurable burst size and refill rates. Returns 429 status with 
 Retry-After header. [Implementation details →]
 ```
 
@@ -181,7 +169,6 @@ Retry-After header. [Implementation details →]
 **Purpose:** Help users successfully accomplish specific tasks.
 
 **Required Elements:**
-
 - Context (what this accomplishes, why you'd do it)
 - Prerequisites listed upfront
 - Expected outcome stated
@@ -192,7 +179,6 @@ Retry-After header. [Implementation details →]
 - Common issues and troubleshooting
 
 **Analysis Focus:**
-
 - Is context provided before steps?
 - Are prerequisites clearly stated?
 - Is there both a Dashboard and API path?
@@ -211,7 +197,6 @@ Retry-After header. [Implementation details →]
 **Pattern Example:**
 
 ❌ **Before (Steps-only):**
-
 ```markdown
 ## Enable Feature
 
@@ -222,17 +207,16 @@ Retry-After header. [Implementation details →]
 ```
 
 ✅ **After (Contextual multi-path):**
-
-````markdown
+```markdown
 ## Enable Feature
 
-**What this does:** Protects your site from [specific threat] by
+**What this does:** Protects your site from [specific threat] by 
 [specific mechanism].
 
 **Time required:** ~2 minutes  
 **Prerequisites:** Admin access to your account
 
-**What happens:** After enabling, all incoming requests will be
+**What happens:** After enabling, all incoming requests will be 
 [specific behavior]. You'll see results in Analytics within 5 minutes.
 
 ### Via Dashboard
@@ -243,7 +227,7 @@ Retry-After header. [Implementation details →]
 4. Find **Feature Name** and toggle it **On**
 5. Click **Save Changes**
 
-💡 **Note:** Changes take effect immediately, but analytics may take
+💡 **Note:** Changes take effect immediately, but analytics may take 
 5 minutes to update.
 
 ### Via API
@@ -256,17 +240,15 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_enabled": true}'
 ```
-````
 
 **Response:**
-
 ```json
 {
-	"success": true,
-	"result": {
-		"feature_enabled": true,
-		"updated_at": "2026-02-09T10:30:00Z"
-	}
+  "success": true,
+  "result": {
+    "feature_enabled": true,
+    "updated_at": "2026-02-09T10:30:00Z"
+  }
 }
 ```
 
@@ -284,10 +266,9 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 ## Troubleshooting
 
 **Problem:** Feature doesn't seem to be active  
-**Solution:** Clear your browser cache and wait 5 minutes for
+**Solution:** Clear your browser cache and wait 5 minutes for 
 propagation. Still not working? Check that [prerequisite].
-
-````
+```
 
 ---
 
@@ -323,20 +304,19 @@ propagation. Still not working? Check that [prerequisite].
 ```markdown
 ## Cache Headers
 
-**Cache-Control:** Controls caching. Values: public, private,
+**Cache-Control:** Controls caching. Values: public, private, 
 no-cache, max-age=seconds
 
 **Expires:** HTTP date for expiration
 
 **Pragma:** Legacy directive. Value: no-cache
-````
+```
 
 ✅ **After (Use-case organized with examples):**
-
-````markdown
+```markdown
 ## Cache Headers Reference
 
-**When to use:** Control how long content stays cached and who can
+**When to use:** Control how long content stays cached and who can 
 cache it.
 
 ### Common Scenarios
@@ -355,19 +335,17 @@ cache it.
 
 **What it does:** Caches content for 1 year before checking for updates
 
-**When to use:** Files that never change, like `logo-v2.png` or
+**When to use:** Files that never change, like `logo-v2.png` or 
 `style.abc123.css` with version hash in filename
 
 **Technical spec:** Integer, seconds. Range: 0-31536000 (1 year max)
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
-````
 
-**Result:** First visitor downloads the file. For the next year, all
+**Result:** First visitor downloads the file. For the next year, all 
 visitors get the cached version with zero origin requests.
 
 ---
@@ -376,18 +354,17 @@ visitors get the cached version with zero origin requests.
 
 **What it does:** Tells browsers this file will literally never change
 
-**When to use:** Combine with `max-age` for versioned assets
+**When to use:** Combine with `max-age` for versioned assets 
 (filename includes hash/version number)
 
 **Technical spec:** No value. Presence activates directive.
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
 
-**Result:** Browsers won't revalidate even on refresh. Perfect for
+**Result:** Browsers won't revalidate even on refresh. Perfect for 
 `style.abc123.css` where hash changes when content changes.
 
 ---
@@ -398,18 +375,17 @@ Cache-Control: public, max-age=31536000, immutable
 
 **What it does:** Caches content for 1 hour
 
-**When to use:** Content that updates occasionally but doesn't need
+**When to use:** Content that updates occasionally but doesn't need 
 to be real-time, like blog posts or product pages
 
 **Technical spec:** Integer, seconds
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=3600
 ```
 
-**Result:** Content stays cached for 1 hour. After expiration, next
+**Result:** Content stays cached for 1 hour. After expiration, next 
 request checks origin for updates.
 
 ---
@@ -418,18 +394,17 @@ request checks origin for updates.
 
 **What it does:** Always check with origin before using cached version
 
-**When to use:** Content that changes frequently but can still be
+**When to use:** Content that changes frequently but can still be 
 cached briefly (shopping cart, personalized pages)
 
 **Technical spec:** No value. Presence activates.
 
 **Example:**
-
 ```http
 Cache-Control: no-cache
 ```
 
-**Result:** Every request checks origin via If-Modified-Since or
+**Result:** Every request checks origin via If-Modified-Since or 
 ETag. If nothing changed, serves cached version (304 response).
 
 ---
@@ -440,21 +415,19 @@ ETag. If nothing changed, serves cached version (304 response).
 
 **What it does:** Prevents any caching
 
-**When to use:** Sensitive data (account info, payment details) or
+**When to use:** Sensitive data (account info, payment details) or 
 highly dynamic content (real-time scores, live chat)
 
 **Technical spec:** Combine both directives
 
 **Example:**
-
 ```http
 Cache-Control: private, no-store
 ```
 
-**Result:** Every request fetches fresh from origin. Nothing cached
+**Result:** Every request fetches fresh from origin. Nothing cached 
 anywhere.
-
-````
+```
 
 ---
 
@@ -500,9 +473,8 @@ const handler = async (req) => {
   return new Response('Hello')
 }
 addEventListener('fetch', e => e.respondWith(handler(e.request)))
-````
-
-````
+```
+```
 
 ✅ **After (Explained progression):**
 ```markdown
@@ -510,14 +482,14 @@ addEventListener('fetch', e => e.respondWith(handler(e.request)))
 
 ### What You'll Build
 
-A working URL shortener that redirects short links to long URLs,
+A working URL shortener that redirects short links to long URLs, 
 stores mappings, and tracks click analytics.
 
 **Live example:** `short.example.com/github` → `github.com/cloudflare`
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience with
+Developers comfortable with JavaScript. No prior experience with 
 Workers needed, but you should understand:
 - HTTP requests and responses
 - JSON data format
@@ -538,7 +510,7 @@ Workers needed, but you should understand:
 
 ## Step 1: Create Your First Worker
 
-Let's start with the absolute minimum—a Worker that responds to
+Let's start with the absolute minimum—a Worker that responds to 
 requests:
 
 ```javascript
@@ -554,7 +526,7 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-````
+```
 
 **What this code does:**
 
@@ -578,15 +550,15 @@ Now let's make it recognize short codes in the URL:
 
 ```javascript
 async function handleRequest(request) {
-	// Extract the pathname from the URL
-	// Example: https://short.example.com/github → "/github"
-	const url = new URL(request.url);
-	const shortCode = url.pathname.slice(1); // Remove leading "/"
-
-	// For now, just echo back the short code
-	return new Response(`You requested: ${shortCode}`, {
-		headers: { "content-type": "text/plain" },
-	});
+  // Extract the pathname from the URL
+  // Example: https://short.example.com/github → "/github"
+  const url = new URL(request.url)
+  const shortCode = url.pathname.slice(1) // Remove leading "/"
+  
+  // For now, just echo back the short code
+  return new Response(`You requested: ${shortCode}`, {
+    headers: { 'content-type': 'text/plain' }
+  })
 }
 ```
 
@@ -618,15 +590,15 @@ Now we can detect what short code someone's requesting...
 
 **Cause:** Your Worker is doing too much computation in a single request
 
-**Solution:** Workers have a 50ms CPU time limit. Move heavy processing
+**Solution:** Workers have a 50ms CPU time limit. Move heavy processing 
 to background tasks or use Durable Objects for longer operations.
 
 **Problem:** "KV data not updating"
 
-**Cause:** KV is eventually consistent and may take 60 seconds to
+**Cause:** KV is eventually consistent and may take 60 seconds to 
 propagate globally
 
-**Solution:** For testing, add a cache-busting parameter (`?v=2`) or
+**Solution:** For testing, add a cache-busting parameter (`?v=2`) or 
 wait 60 seconds between writes and reads.
 
 ---
@@ -636,24 +608,20 @@ wait 60 seconds between writes and reads.
 Want to take this further? Here are some ideas:
 
 **Add Click Analytics** (Medium difficulty)
-
 - Store click count in KV
 - Increment on each redirect
 - Create stats endpoint
 
 **Custom Short Codes** (Easy)
-
 - Let users choose their short code
 - Check if code is already taken
 - Return error if unavailable
 
 **Expiring Links** (Medium)
-
 - Store expiration timestamp
 - Check before redirecting
 - Return 404 if expired
-
-````
+```
 
 ---
 
@@ -674,7 +642,7 @@ Want to take this further? Here are some ideas:
 - Not: "Webhooks, which are HTTP callbacks, send notifications containing event data to your specified endpoint when certain events occur on the platform."
 
 ✅ **Active voice** over passive
-- "The system sends a notification"
+- "The system sends a notification" 
 - Not: "A notification is sent by the system"
 
 ✅ **Concrete nouns** over abstract
@@ -695,12 +663,11 @@ Want to take this further? Here are some ideas:
 
 **Always define on first use:**
 ```markdown
-An API (Application Programming Interface) defines how programs
+An API (Application Programming Interface) defines how programs 
 can request and exchange data...
-````
+```
 
 **Expand acronyms:**
-
 ```markdown
 CDN (Content Delivery Network)
 CI/CD (Continuous Integration/Continuous Deployment)
@@ -708,10 +675,9 @@ HMAC (Hash-based Message Authentication Code)
 ```
 
 **Provide context for technical terms:**
-
 ```markdown
 Not: "Configure the webhook endpoint."
-But: "A webhook endpoint is the URL where we'll send notifications.
+But: "A webhook endpoint is the URL where we'll send notifications. 
 Configure it to point to your server."
 ```
 
@@ -730,16 +696,16 @@ Configure it to point to your server."
 
 ```markdown
 **Think of It Like:**
-An API is like a restaurant menu. The menu shows you what dishes
-are available (endpoints), what customizations you can request
-(parameters like "no onions" or "extra spicy"), and what you'll
-receive (the response - your meal). You don't need to know how the
-kitchen operates or what cooking techniques they use. You just order
+An API is like a restaurant menu. The menu shows you what dishes 
+are available (endpoints), what customizations you can request 
+(parameters like "no onions" or "extra spicy"), and what you'll 
+receive (the response - your meal). You don't need to know how the 
+kitchen operates or what cooking techniques they use. You just order 
 from the menu, and the kitchen handles the rest.
 
 **Where this breaks down:**
-Unlike a restaurant where you wait for your food, API responses are
-usually near-instantaneous. Also, APIs can fail (kitchen is out of
+Unlike a restaurant where you wait for your food, API responses are 
+usually near-instantaneous. Also, APIs can fail (kitchen is out of 
 ingredients), requiring error handling.
 ```
 
@@ -747,15 +713,15 @@ ingredients), requiring error handling.
 
 ```markdown
 **Think of It Like:**
-Caching is like a library's reserve desk. Popular books are kept at
-the front desk for quick access instead of requiring a trip to the
-stacks. The first person requesting a book triggers the librarian to
-fetch it from the stacks, but then it stays at the reserve desk so
+Caching is like a library's reserve desk. Popular books are kept at 
+the front desk for quick access instead of requiring a trip to the 
+stacks. The first person requesting a book triggers the librarian to 
+fetch it from the stacks, but then it stays at the reserve desk so 
 subsequent readers can grab it immediately.
 
 **Where this breaks down:**
-Caches expire (books eventually return to the stacks), and cache
-invalidation (deciding when to return books) is more complex than
+Caches expire (books eventually return to the stacks), and cache 
+invalidation (deciding when to return books) is more complex than 
 the metaphor suggests.
 ```
 
@@ -763,15 +729,15 @@ the metaphor suggests.
 
 ```markdown
 **Think of It Like:**
-Load balancing is like grocery store checkout lanes. Instead of
-everyone lining up at a single register (which would create a huge
-wait), customers are distributed across multiple lanes. If one lane
-gets too long or a register breaks down, the store can redirect
+Load balancing is like grocery store checkout lanes. Instead of 
+everyone lining up at a single register (which would create a huge 
+wait), customers are distributed across multiple lanes. If one lane 
+gets too long or a register breaks down, the store can redirect 
 people to other lanes.
 
 **Where this breaks down:**
-Load balancers are more intelligent than checkout lane selection—they
-know which servers are healthy, how busy they are, and can route
+Load balancers are more intelligent than checkout lane selection—they 
+know which servers are healthy, how busy they are, and can route 
 based on sophisticated algorithms.
 ```
 
@@ -779,14 +745,14 @@ based on sophisticated algorithms.
 
 ```markdown
 **Think of It Like:**
-A webhook is like a doorbell notification. Instead of constantly
-checking your front door to see if someone arrived (polling), the
-doorbell alerts you the moment someone presses it (push notification).
+A webhook is like a doorbell notification. Instead of constantly 
+checking your front door to see if someone arrived (polling), the 
+doorbell alerts you the moment someone presses it (push notification). 
 You only respond when there's actually something to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have some latency due to
-network transmission. Also, webhooks can fail if your server is down
+Doorbells are instantaneous, while webhooks have some latency due to 
+network transmission. Also, webhooks can fail if your server is down 
 (like a broken doorbell).
 ```
 
@@ -794,15 +760,15 @@ network transmission. Also, webhooks can fail if your server is down
 
 ```markdown
 **Think of It Like:**
-Authentication is like a building security badge system. You present
-your badge (credentials) when entering. The system verifies you are
-who you claim to be (authentication), then checks what floors you're
-allowed to access (authorization). Different badges have different
+Authentication is like a building security badge system. You present 
+your badge (credentials) when entering. The system verifies you are 
+who you claim to be (authentication), then checks what floors you're 
+allowed to access (authorization). Different badges have different 
 access levels.
 
 **Where this breaks down:**
-Digital authentication often uses time-limited tokens (like a badge
-that expires), and can verify identity through multiple methods
+Digital authentication often uses time-limited tokens (like a badge 
+that expires), and can verify identity through multiple methods 
 (password + fingerprint), which isn't common with physical badges.
 ```
 
@@ -810,15 +776,15 @@ that expires), and can verify identity through multiple methods
 
 ```markdown
 **Think of It Like:**
-Rate limiting is like freeway on-ramp metering lights. Instead of
-letting everyone merge at once (causing congestion), the lights
-control how many cars enter per minute. This keeps traffic flowing
-smoothly on the main freeway. If you arrive too fast, you wait at
+Rate limiting is like freeway on-ramp metering lights. Instead of 
+letting everyone merge at once (causing congestion), the lights 
+control how many cars enter per minute. This keeps traffic flowing 
+smoothly on the main freeway. If you arrive too fast, you wait at 
 the red light.
 
 **Where this breaks down:**
-Rate limits are often user-specific (you get your own limit), not
-shared like a metering light. Also, rate limits reset on schedules
+Rate limits are often user-specific (you get your own limit), not 
+shared like a metering light. Also, rate limits reset on schedules 
 (every hour, every day), unlike continuous traffic flow.
 ```
 
@@ -826,14 +792,14 @@ shared like a metering light. Also, rate limits reset on schedules
 
 ```markdown
 **Think of It Like:**
-A database index is like the index at the back of a textbook. Instead
-of reading every page to find mentions of "webhooks," you check the
-index, which tells you exactly which pages to look at. The index
+A database index is like the index at the back of a textbook. Instead 
+of reading every page to find mentions of "webhooks," you check the 
+index, which tells you exactly which pages to look at. The index 
 takes up extra space, but makes searching dramatically faster.
 
 **Where this breaks down:**
-Database indexes need updating when data changes (like keeping a
-book index current as you add pages), and choosing which fields to
+Database indexes need updating when data changes (like keeping a 
+book index current as you add pages), and choosing which fields to 
 index involves tradeoffs between search speed and write speed.
 ```
 
@@ -841,16 +807,16 @@ index involves tradeoffs between search speed and write speed.
 
 ```markdown
 **Think of It Like:**
-A CDN (Content Delivery Network) is like having local warehouses
-instead of shipping everything from one central warehouse. When
-someone in California orders a product, it ships from the California
-warehouse (faster delivery). When someone in New York orders, it
+A CDN (Content Delivery Network) is like having local warehouses 
+instead of shipping everything from one central warehouse. When 
+someone in California orders a product, it ships from the California 
+warehouse (faster delivery). When someone in New York orders, it 
 ships from New York. Same product, closer source.
 
 **Where this breaks down:**
-Unlike physical warehouses with unique inventory, CDNs store copies
-of the same content in many locations. Updates need to propagate to
-all locations (cache invalidation), which has no physical warehouse
+Unlike physical warehouses with unique inventory, CDNs store copies 
+of the same content in many locations. Updates need to propagate to 
+all locations (cache invalidation), which has no physical warehouse 
 equivalent.
 ```
 
@@ -858,17 +824,17 @@ equivalent.
 
 ```markdown
 **Think of It Like:**
-Software containers are like shipping containers. Before shipping
-containers existed, moving goods required different methods for
-different types of cargo. Shipping containers standardized this—put
-anything inside a standard container, and it can go on any ship,
-truck, or train. Software containers work the same way: package your
+Software containers are like shipping containers. Before shipping 
+containers existed, moving goods required different methods for 
+different types of cargo. Shipping containers standardized this—put 
+anything inside a standard container, and it can go on any ship, 
+truck, or train. Software containers work the same way: package your 
 application and its dependencies, and it runs anywhere.
 
 **Where this breaks down:**
-Shipping containers physically isolate cargo, while software
-containers share the same operating system kernel. Also, you can run
-thousands of software containers on one machine, unlike physical
+Shipping containers physically isolate cargo, while software 
+containers share the same operating system kernel. Also, you can run 
+thousands of software containers on one machine, unlike physical 
 containers.
 ```
 
@@ -877,15 +843,15 @@ containers.
 ```markdown
 **Think of It Like:**
 Environment variables are like your application's settings panel—
-configuration values that change behavior without modifying code.
-Just like you might set your phone to dark mode or adjust notification
-preferences, environment variables let you configure database URLs,
+configuration values that change behavior without modifying code. 
+Just like you might set your phone to dark mode or adjust notification 
+preferences, environment variables let you configure database URLs, 
 API keys, or feature flags without rewriting your application.
 
 **Where this breaks down:**
-Environment variables are usually set before the application starts
-(not changed while running), and they're text-based rather than UI
-toggles. They're also specific to each deployment environment (dev,
+Environment variables are usually set before the application starts 
+(not changed while running), and they're text-based rather than UI 
+toggles. They're also specific to each deployment environment (dev, 
 staging, production).
 ```
 
@@ -904,26 +870,22 @@ When you encounter a concept not in this library, create a new metaphor by:
 **Always structure content in this order:**
 
 **1. The Problem (Why)**
-
 ```markdown
-When building applications, you often need to know when something
-happens on another platform—like when a payment completes, a file
-finishes uploading, or a deployment succeeds. Constantly checking
+When building applications, you often need to know when something 
+happens on another platform—like when a payment completes, a file 
+finishes uploading, or a deployment succeeds. Constantly checking 
 for updates (polling) wastes resources and creates delays.
 ```
 
 **2. The Solution (What)**
-
 ```markdown
-Webhooks solve this by pushing notifications to you. When an event
+Webhooks solve this by pushing notifications to you. When an event 
 happens, we immediately send a message to your server with the details.
 ```
 
 **3. The Value (Why It Matters)**
-
 ```markdown
 This means:
-
 - Your application responds in real-time instead of polling
 - You save resources (no constant checking)
 - Users get faster updates
@@ -931,10 +893,8 @@ This means:
 ```
 
 **4. The Use Cases (When)**
-
 ```markdown
 Common scenarios:
-
 - Triggering workflows when deployments complete
 - Updating your database when content changes
 - Sending notifications when payments are processed
@@ -942,10 +902,8 @@ Common scenarios:
 ```
 
 **5. The Implementation (How)**
-
 ```markdown
 To set up a webhook:
-
 1. Create an endpoint URL where we'll send notifications
 2. Configure which events you want to receive
 3. Verify requests are from us (using signatures)
@@ -987,7 +945,7 @@ Focus on outcomes, when to involve technical help, business impact
 
 **Example in Practice:**
 
-````markdown
+```markdown
 ## Webhook Signature Verification
 
 ---
@@ -1012,13 +970,11 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## 📋 Simplification Overview
 
 **What was confusing:**
-
 - [Pattern 1 - e.g., Heavy acronym use without expansion]
 - [Pattern 2 - e.g., Assumed understanding of HTTP protocols]
 - [Pattern 3 - e.g., Jumped to implementation without explaining purpose]
 
 **Approach taken:**
-
 - [Strategy 1 - e.g., Added one-sentence summaries for each concept]
 - [Strategy 2 - e.g., Expanded all acronyms on first use]
 - [Strategy 3 - e.g., Added "Why this matters" to each section]
@@ -1029,11 +985,9 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 ## Section: [Original Heading]
 
 ### 📄 Original Content
-```
-````
 
+```
 [Exact text from source, formatting preserved]
-
 ```
 
 ### ⚠️ Issues Identified
@@ -1052,21 +1006,21 @@ When I simplify documentation, I create a `.eli5.md` file with this structure:
 
 ### ✨ Simplified Version
 
-**In Plain Language:**
+**In Plain Language:**  
 [One crisp sentence capturing the essence without jargon]
 
-**What It Is:**
-[2-3 paragraphs building understanding from basics. Define terms.
+**What It Is:**  
+[2-3 paragraphs building understanding from basics. Define terms. 
 Explain concepts. Build progressively. No jargon assumed.]
 
-**Why It Matters:**
+**Why It Matters:**  
 [Value proposition and concrete benefits]
 
 - **Benefit 1:** [Specific, concrete impact]
 - **Benefit 2:** [Specific, concrete impact]
 - **Benefit 3:** [Specific, concrete impact]
 
-**When You'd Use This:**
+**When You'd Use This:**  
 
 - **Scenario 1:** [Realistic use case with context]
   - Example: "When building a chat application that needs real-time message delivery..."
@@ -1077,23 +1031,23 @@ Explain concepts. Build progressively. No jargon assumed.]
 - **Scenario 3:** [Realistic use case with context]
   - Example: "When triggering post-deployment tasks like cache clearing..."
 
-**Think of It Like:**
+**Think of It Like:**  
 [Tech-adjacent metaphor with detailed explanation]
 
 [Full metaphor explanation, making connections explicit]
 
-**Where this metaphor breaks down:**
+**Where this metaphor breaks down:**  
 [Acknowledge limitations honestly]
 
-**Common Pitfalls:**
+**Common Pitfalls:**  
 
-- **Pitfall:** [What people commonly misunderstand]
+- **Pitfall:** [What people commonly misunderstand]  
   **Reality:** [Correction with explanation]
 
-- **Pitfall:** [Common mistake]
+- **Pitfall:** [Common mistake]  
   **Reality:** [How it actually works]
 
-**Related Concepts:**
+**Related Concepts:**  
 [Connections to things readers might already know]
 
 - "If you've used [familiar concept], this works similarly..."
@@ -1170,7 +1124,6 @@ After the main simplification and summary, I include a **"Suggestions for Enhanc
 **Format:**
 
 Each suggestion includes:
-
 - **Line reference:** Specific location in the original document
 - **Section name:** What part of the doc this applies to
 - **Current approach:** What's there now
@@ -1180,9 +1133,11 @@ Each suggestion includes:
 
 **Example:**
 
-````markdown
+```markdown
 ---
+
 ## 📝 Suggestions for Enhancement
+
 ---
 
 ## 4. Suggestions for Enhancement
@@ -1199,13 +1154,11 @@ These suggestions show where additional patterns could improve accessibility:
 **Suggested enhancement:** Add API path for technical users who prefer code
 
 **Why this helps:**
-
 - Serves both UI users and developers with their preferred method
 - Technical users can automate the process via API
 - Provides complete coverage for mixed audiences
 
 **Implementation:**
-
 ```markdown
 ### Via API
 
@@ -1214,18 +1167,18 @@ These suggestions show where additional patterns could improve accessibility:
 
 \`\`\`bash
 curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/always_use_https" \\
--H "Authorization: Bearer {token}" \\
--d '{"value":"on"}'
+  -H "Authorization: Bearer {token}" \\
+  -d '{"value":"on"}'
 \`\`\`
 
 **Response:**
 \`\`\`json
 {
-"success": true,
-"result": {
-"id": "always_use_https",
-"value": "on"
-}
+  "success": true,
+  "result": {
+    "id": "always_use_https",
+    "value": "on"
+  }
 }
 \`\`\`
 
@@ -1242,7 +1195,6 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 **Suggested enhancement:** Move advanced technical details to collapsible section
 
 **Why this helps:**
-
 - Beginners get the simple explanation without being overwhelmed
 - Experts can expand for full technical depth
 - Maintains clear progressive disclosure
@@ -1250,17 +1202,15 @@ curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/alw
 
 **Implementation:**
 \`\`\`markdown
-
 ## How TLS Encryption Works
 
-Your connection is encrypted using industry-standard TLS 1.3 protocol,
+Your connection is encrypted using industry-standard TLS 1.3 protocol, 
 ensuring no one can intercept your data in transit.
 
 <details>
 <summary>For technical users: Cipher suite details</summary>
 
 We support TLS 1.3 with modern AEAD cipher suites including:
-
 - TLS_AES_128_GCM_SHA256
 - TLS_AES_256_GCM_SHA384
 - TLS_CHACHA20_POLY1305_SHA256
@@ -1280,7 +1230,6 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 **Suggested enhancement:** Call out recommended default for most users
 
 **Why this helps:**
-
 - Reduces decision paralysis for uncertain users
 - Provides a safe starting point
 - Guides users toward best security practices
@@ -1288,23 +1237,22 @@ Perfect forward secrecy via X25519 key exchange. [Full TLS configuration →]
 
 **Implementation:**
 \`\`\`markdown
-
 ### Encryption Modes
 
 **Recommended for most sites:** Full (Strict)
 
-Provides maximum security by validating your origin server's
-certificate. This is the best option if your server has a valid SSL
+Provides maximum security by validating your origin server's 
+certificate. This is the best option if your server has a valid SSL 
 certificate installed.
 
 #### Other Options
 
 - **Off:** No encryption (Not recommended - only use for testing)
-- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your
+- **Flexible:** Encrypts visitor-to-Cloudflare only (Use if your 
   server doesn't have SSL)
 - **Full:** Encrypts entire path but doesn't validate certificate
 - **Full (Strict):** Maximum security with certificate validation ✅
-  \`\`\`
+\`\`\`
 
 ---
 
@@ -1316,7 +1264,6 @@ certificate installed.
 **Suggested enhancement:** Add realistic use case showing feature in action
 
 **Why this helps:**
-
 - Makes abstract benefits concrete and relatable
 - Helps users visualize how they'd use this
 - Provides "aha moment" of recognition
@@ -1328,21 +1275,19 @@ certificate installed.
 Prevents attackers from overwhelming your site with fake traffic.
 
 **Real scenario:**
-An e-commerce site during Black Friday gets hit by bots trying to
-buy limited inventory. DDoS protection automatically filters out
-the bot traffic, letting real customers complete their purchases
+An e-commerce site during Black Friday gets hit by bots trying to 
+buy limited inventory. DDoS protection automatically filters out 
+the bot traffic, letting real customers complete their purchases 
 while the attack is absorbed across Cloudflare's network.
 
-Without protection, the site would crash within minutes, losing
+Without protection, the site would crash within minutes, losing 
 thousands in sales.
 \`\`\`
 ```
-````
 
 **When to include suggestions:**
 
 Include this section when:
-
 - Multi-path opportunities exist (Dashboard + API)
 - Technical details could be collapsed
 - Missing recommended defaults
@@ -1353,7 +1298,6 @@ Include this section when:
 **Placement:**
 
 The Suggestions section appears:
-
 - After the "Summary & Recommendations" section
 - Before the "Next Steps" section
 - Clearly separated with heading and explanation
@@ -1391,7 +1335,7 @@ Before finalizing any simplified content, verify:
 ❌ "Clearly, this requires..."  
 ❌ "As everyone knows..."  
 ❌ "It's easy to..."  
-❌ "All you have to do is..."
+❌ "All you have to do is..."  
 
 **Use these respectful alternatives:**
 
@@ -1400,38 +1344,34 @@ Before finalizing any simplified content, verify:
 ✅ "This requires..."  
 ✅ "Here's how this works..."  
 ✅ "This involves..."  
-✅ "The process is..."
+✅ "The process is..."  
 
 ### Accuracy Is Non-Negotiable
 
 **Good simplification:**
-
 ```markdown
-Webhooks send HTTP POST requests to your endpoint URL whenever
-specified events occur. Think of it as a notification system where
+Webhooks send HTTP POST requests to your endpoint URL whenever 
+specified events occur. Think of it as a notification system where 
 we call your server instead of you constantly checking ours.
 ```
-
-_Accurate, clear, uses metaphor effectively_
+*Accurate, clear, uses metaphor effectively*
 
 **Bad simplification:**
-
 ```markdown
 Webhooks let programs talk to each other.
 ```
-
-_Too vague, loses important details, not actually helpful_
+*Too vague, loses important details, not actually helpful*
 
 **When complex accuracy is needed:**
 
 Use progressive disclosure:
 
 ```markdown
-**Simplified:** Rate limiting controls how many requests you can
+**Simplified:** Rate limiting controls how many requests you can 
 make in a time period, like 100 requests per minute.
 
-**More precisely:** Rate limits apply per API key and reset on a
-sliding window. If you hit the limit, you'll receive a 429 status
+**More precisely:** Rate limits apply per API key and reset on a 
+sliding window. If you hit the limit, you'll receive a 429 status 
 code with a Retry-After header indicating when you can try again.
 ```
 
@@ -1440,7 +1380,6 @@ code with a Retry-After header indicating when you can try again.
 #### API Documentation
 
 Focus on:
-
 - What the endpoint does (purpose)
 - When you'd use it (scenarios)
 - What you send (parameters explained)
@@ -1449,7 +1388,6 @@ Focus on:
 - Error handling (what can go wrong)
 
 **Add value through:**
-
 - Explaining parameter purposes, not just types
 - Showing realistic request/response examples
 - Clarifying common misunderstandings
@@ -1458,7 +1396,6 @@ Focus on:
 #### Architecture Documentation
 
 Focus on:
-
 - Problem being solved
 - Why this approach was chosen
 - Tradeoffs made (what was gained/lost)
@@ -1466,7 +1403,6 @@ Focus on:
 - Alternatives considered
 
 **Add value through:**
-
 - Explaining decision rationale
 - Making tradeoffs explicit
 - Providing context for choices
@@ -1475,14 +1411,12 @@ Focus on:
 #### Code Documentation
 
 Focus on:
-
 - What the code accomplishes
 - Why it's structured this way
 - Key concepts or patterns used
 - What to watch out for
 
 **Add value through:**
-
 - Plain-language "reading guides"
 - Explaining non-obvious choices
 - Clarifying complex logic
@@ -1520,25 +1454,22 @@ Focus on:
 ## 📋 Simplification Overview
 
 **What was done well:**
-
 - Clear section headings with logical flow
 - Terms defined on first use
 - Good use of examples
 - "Why" explained before "how"
 
 **Minor improvements suggested:**
-
 - Could add a tech-adjacent metaphor for [concept]
 - Section 3 could benefit from a concrete use case
 - Consider adding "common pitfalls" to section 5
 
 **Overall assessment:**
-This documentation is already quite accessible. The suggestions above
+This documentation is already quite accessible. The suggestions above 
 are minor enhancements rather than necessary corrections.
 ```
 
 **Avoid:**
-
 - Adding unnecessary verbosity
 - Creating problems that don't exist
 - Over-explaining clear content
@@ -1554,7 +1485,6 @@ are minor enhancements rather than necessary corrections.
    - Preserve necessary complexity
 
 2. **Layer explanations**
-
    ```markdown
    **High-level:** [What it accomplishes]
    **How it works:** [Simplified mechanism]
@@ -1581,8 +1511,7 @@ are minor enhancements rather than necessary corrections.
    - Preserve technical correctness
 
 2. **Add explanatory context**
-
-   ````markdown
+   ```markdown
    **What this code does:**
    [Plain-language explanation]
 
@@ -1590,17 +1519,12 @@ are minor enhancements rather than necessary corrections.
    [Architectural rationale]
 
    **Key points to understand:**
-
    - [Important concept 1]
    - [Important concept 2]
 
    ```python
    [Original code, unchanged]
    ```
-   ````
-
-   ```
-
    ```
 
 3. **Create "reading guides"**
@@ -1617,10 +1541,9 @@ are minor enhancements rather than necessary corrections.
    - Leave component code unchanged
 
 2. **Explain component purpose**
-
    ```markdown
    **What this component does:**
-   The <CodeBlock> component displays syntax-highlighted code with
+   The <CodeBlock> component displays syntax-highlighted code with 
    copy functionality, making it easier for readers to use the examples.
    ```
 
@@ -1631,7 +1554,7 @@ are minor enhancements rather than necessary corrections.
 
 ## Future Enhancements
 
-_Documented for future implementation_
+*Documented for future implementation*
 
 ### Planned Features
 
@@ -1644,21 +1567,19 @@ Support for code files with inline documentation:
 def process_webhook(payload, signature):
     """
     Processes incoming webhook notifications.
-
+    
     Verifies signature, parses payload, triggers handlers.
     """
     # Implementation...
 ```
 
 **Planned behavior:**
-
 - Extract docstrings and comments
 - Simplify technical language in comments
 - Add explanatory prose for complex logic
 - Generate "code walkthrough" guides
 
 **Supported formats:**
-
 - `.js`, `.ts`, `.tsx` (JavaScript/TypeScript)
 - `.py` (Python)
 - `.go` (Go)
@@ -1684,7 +1605,6 @@ Quantitative analysis:
 - **Context gap analysis** - Identify missing "why" and "when" statements
 
 **Auto-prioritization:**
-
 - Sort sections by complexity
 - Focus on highest-value simplifications
 - Generate complexity reports
@@ -1726,65 +1646,63 @@ Returns a `webhook` object.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-Set up automatic notifications that we'll send to your server whenever
+Set up automatic notifications that we'll send to your server whenever 
 specific events occur.
 
 **What It Is:**
-A webhook subscription tells our system to notify your application
-when certain events happen (like a deployment completing or content
-being published). Instead of your application constantly checking for
+A webhook subscription tells our system to notify your application 
+when certain events happen (like a deployment completing or content 
+being published). Instead of your application constantly checking for 
 updates (polling), we push notifications to you the moment events occur.
 
 **Why It Matters:**
-
 - **Real-time updates** - Your application responds immediately
 - **Resource efficiency** - No wasted API calls checking for changes
 - **Reliability** - You never miss an event
 - **Automation** - Trigger workflows automatically
 
 **When You'd Use This:**
-
 - **Deployment notifications:** Trigger post-deployment tasks when builds complete
 - **Content synchronization:** Update your CMS when content changes
 - **Monitoring:** Alert your team when errors occur
 - **Integration:** Connect multiple systems to respond to events
 
 **Think of It Like:**
-A webhook is like setting up a doorbell notification on your phone.
-Instead of constantly checking your front door camera to see if someone
-arrived (polling), the doorbell alerts you the moment someone presses
-it (push notification). You only respond when there's actually something
+A webhook is like setting up a doorbell notification on your phone. 
+Instead of constantly checking your front door camera to see if someone 
+arrived (polling), the doorbell alerts you the moment someone presses 
+it (push notification). You only respond when there's actually something 
 to respond to.
 
 **Where this breaks down:**
-Doorbells are instantaneous, while webhooks have small delays due to
-network transmission. Also, webhooks can fail if your server is down
+Doorbells are instantaneous, while webhooks have small delays due to 
+network transmission. Also, webhooks can fail if your server is down 
 (like a broken doorbell), so you need retry logic.
 
 **Parameters Explained:**
 
-- **`endpoint`** - The URL where we'll send notifications (your server's
+- **`endpoint`** - The URL where we'll send notifications (your server's 
   address that listens for webhook events). Must use HTTPS for security.
 
-- **`events`** - Which events you want to receive (like `deployment.succeeded`
+- **`events`** - Which events you want to receive (like `deployment.succeeded` 
   or `content.published`). You choose only the events you care about.
 
-- **`secret`** - Optional security key for verifying notifications actually
+- **`secret`** - Optional security key for verifying notifications actually 
   come from us. We use this to create a signature you can verify.
 
 **Common Pitfalls:**
 
 - **Pitfall:** Thinking webhooks are 100% reliable  
-  **Reality:** Network issues or server downtime can cause missed notifications.
+  **Reality:** Network issues or server downtime can cause missed notifications. 
   Implement retry logic and consider periodic polling as a backup.
 
 - **Pitfall:** Not verifying signatures  
-  **Reality:** Without signature verification, attackers could send fake
+  **Reality:** Without signature verification, attackers could send fake 
   webhooks to trigger unauthorized actions.
 
 **Related Concepts:**
-If you've used RSS feeds, webhooks work similarly—both push updates to
-you. The difference is webhooks are programmable and work with any type
+If you've used RSS feeds, webhooks work similarly—both push updates to 
+you. The difference is webhooks are programmable and work with any type 
 of event, not just content updates.
 ```
 
@@ -1795,8 +1713,8 @@ of event, not just content updates.
 ```markdown
 ## Edge Deployment Architecture
 
-We've implemented a globally distributed edge architecture utilizing
-V8 isolates for multi-tenant execution with microsecond cold starts
+We've implemented a globally distributed edge architecture utilizing 
+V8 isolates for multi-tenant execution with microsecond cold starts 
 and automatic geographic distribution.
 ```
 
@@ -1806,42 +1724,40 @@ and automatic geographic distribution.
 ### ✨ Simplified Version
 
 **In Plain Language:**
-We run your code on servers located around the world, close to your
+We run your code on servers located around the world, close to your 
 users, making responses nearly instant regardless of where users are.
 
 **What It Is:**
-Traditional servers run in specific data centers—if your server is in
-Virginia and your user is in Singapore, every request travels across
-the world and back (adding hundreds of milliseconds). Our edge
-architecture runs your code on servers in hundreds of cities worldwide,
+Traditional servers run in specific data centers—if your server is in 
+Virginia and your user is in Singapore, every request travels across 
+the world and back (adding hundreds of milliseconds). Our edge 
+architecture runs your code on servers in hundreds of cities worldwide, 
 so requests are handled by the nearest server.
 
 **Why It Matters:**
-
 - **Speed:** Users get responses in 10-50ms instead of 200-500ms
 - **Reliability:** If one location fails, others continue serving traffic
 - **Scale:** Handles traffic spikes automatically across all locations
 - **Simplicity:** You deploy once; we handle global distribution
 
 **When You'd Use This:**
-
 - **Global applications:** Users are distributed worldwide
 - **API endpoints:** Need fast response times everywhere
 - **Dynamic content:** Content that can't be cached must still be fast
 - **High availability:** Can't afford regional outages
 
 **Think of It Like:**
-Instead of one central warehouse shipping products nationwide (slow
-delivery to distant customers), you have local warehouses in every major
-city. When someone orders, it ships from their nearest warehouse. Same
+Instead of one central warehouse shipping products nationwide (slow 
+delivery to distant customers), you have local warehouses in every major 
+city. When someone orders, it ships from their nearest warehouse. Same 
 product, faster delivery, handled automatically.
 
 **The Technical Approach:**
 
-We use "V8 isolates"—lightweight execution environments that start in
-microseconds (thousandths of a millisecond). Traditional "serverless"
-functions use containers that take 50-500ms to start. Isolates are
-fast enough that we don't need to keep them warm; they start on-demand
+We use "V8 isolates"—lightweight execution environments that start in 
+microseconds (thousandths of a millisecond). Traditional "serverless" 
+functions use containers that take 50-500ms to start. Isolates are 
+fast enough that we don't need to keep them warm; they start on-demand 
 for each request.
 
 **Why this architecture:**
@@ -1852,12 +1768,11 @@ We evaluated three approaches:
 3. **Isolate-based edge:** Global + fast (our choice)
 
 **Tradeoff made:**
-Isolates have some limitations compared to full containers (no arbitrary
-system libraries, limited execution time). We accepted these constraints
+Isolates have some limitations compared to full containers (no arbitrary 
+system libraries, limited execution time). We accepted these constraints 
 for the massive speed improvement.
 
 **Common Pitfalls:**
-
 - **Pitfall:** Assuming it works like traditional servers  
   **Reality:** Stateless execution—no persistent local storage, no background jobs
 
@@ -1865,22 +1780,20 @@ for the massive speed improvement.
   **Reality:** Implements web standards, not full Node.js APIs
 
 **Related Concepts:**
-If you've used CDNs (Content Delivery Networks), this is similar but
-for code execution, not just static files. Like a CDN distributes
+If you've used CDNs (Content Delivery Networks), this is similar but 
+for code execution, not just static files. Like a CDN distributes 
 content globally, we distribute code execution globally.
 ```
 
 ## Remember
 
 **Your mission:**
-
 - Make technical concepts accessible
 - Maintain technical accuracy
 - Respect reader intelligence
 - Focus on understanding
 
 **Always include:**
-
 - One-sentence plain language summary
 - Clear "why" and "when" explanations
 - Tech-adjacent metaphor with limitations
@@ -1888,28 +1801,25 @@ content globally, we distribute code execution globally.
 - Use cases grounding abstract concepts
 
 **Quality standards:**
-
 - Technical accuracy is non-negotiable
 - Metaphors must clarify, not confuse
 - Tone must be professional and respectful
 - No condescending language ever
 
 **Process:**
-
 1. Ask which sections to focus on
 2. Identify specific issues (jargon, assumptions, logic, context)
 3. Generate complete before/after comparison
 4. Prompt for next steps
 
 **Output:**
-
 - Create `.eli5.md` file in same directory
 - Include all required elements per section
 - Provide actionable recommendations
 - Offer clear next-step options
 
 **Philosophy:**
-Technical expertise should never be a barrier to understanding. Every
+Technical expertise should never be a barrier to understanding. Every 
 person deserves clear, accurate, respectful documentation.
 
 ---
@@ -1921,3 +1831,4 @@ person deserves clear, accurate, respectful documentation.
 **License:** MIT  
 **Version:** 1.0  
 **Last Updated:** February 2026
+
diff --git a/.agents/skills/eli5/references/content-type-guide.md b/.agents/skills/eli5/references/content-type-guide.md
index 1454cfea7242833..85d544a7c071296 100644
--- a/.agents/skills/eli5/references/content-type-guide.md
+++ b/.agents/skills/eli5/references/content-type-guide.md
@@ -7,7 +7,6 @@ Operational guide for detecting and simplifying different documentation types.
 ## Purpose
 
 This guide provides:
-
 - **Detection criteria** for identifying content types
 - **Required elements** checklist for each type
 - **Simplification patterns** specific to each type
@@ -22,7 +21,6 @@ This guide provides:
 For each content type below, the enhancement patterns are designed to ADD MINIMAL CONTEXT AND EXAMPLES, not restructure or massively expand.
 
 **Universal constraints:**
-
 - Maximum 1-2 examples per major concept
 - Each example: 5-15 lines
 - Inline "why" explanations: 1-2 sentences
@@ -33,7 +31,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Minimal testing guidance (3-5 commands for tutorials)
 
 **When patterns below suggest "Add [section]":**
-
 - Interpret as "enhance inline" not "create separate major section"
 - Keep additions brief and integrated
 - Target 1.5-2x expansion, not 5-10x
@@ -42,13 +39,13 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 ## Content Type Overview
 
-| Type          | Purpose                             | Key Pattern                  | Example                  |
-| ------------- | ----------------------------------- | ---------------------------- | ------------------------ |
-| **Overview**  | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages    |
-| **Concept**   | Build understanding of "why"        | Analogy → Plain → Technical  | "What is rate limiting?" |
-| **How To**    | Enable task completion              | Context → Multi-path steps   | "Enable HTTPS"           |
-| **Reference** | Provide comprehensive specs         | Use-case organization        | API parameters, headers  |
-| **Tutorial**  | Teach through application           | Build → Enhance → Polish     | "Build a URL shortener"  |
+| Type | Purpose | Key Pattern | Example |
+|------|---------|-------------|---------|
+| **Overview** | Help users decide if they need this | Problem → Solution → Benefit | Product landing pages |
+| **Concept** | Build understanding of "why" | Analogy → Plain → Technical | "What is rate limiting?" |
+| **How To** | Enable task completion | Context → Multi-path steps | "Enable HTTPS" |
+| **Reference** | Provide comprehensive specs | Use-case organization | API parameters, headers |
+| **Tutorial** | Teach through application | Build → Enhance → Polish | "Build a URL shortener" |
 
 ---
 
@@ -57,7 +54,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 ### Detection Criteria
 
 **Look for:**
-
 - Product/feature name in title or H1
 - Feature lists or capability descriptions
 - "What is [Product]" sections
@@ -66,7 +62,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Lack of step-by-step instructions
 
 **Confidence signals:**
-
 - Multiple features described briefly
 - High-level product description
 - Links to detailed documentation
@@ -74,7 +69,6 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 - Pricing or plan information
 
 **Example titles:**
-
 - "Cloudflare Workers"
 - "Introduction to Gateway"
 - "What is Workers KV?"
@@ -83,7 +77,7 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 
 - [ ] Opening benefit statement (what problem solved)
 - [ ] Problem/Solution/Benefit structure
-- [ ] "Perfect for" self-identification section
+- [ ] "Perfect for" self-identification section  
 - [ ] Clear call-to-action ("Get started" link)
 - [ ] Feature descriptions with benefits (not just specs)
 - [ ] Technical architecture separated/collapsed
@@ -93,14 +87,12 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Target: 1.5-2x original length**
 
 **Minimal additions:**
-
 1. **Add 2-4 sentence problem statement** (if completely missing) at document start
 2. **Add 1-2 use case examples inline** (5-10 lines each) showing who benefits
 3. **Add inline "why"** (1 sentence) when introducing features
 4. **Define jargon on first use** (brief inline definition)
 
 **Structure to preserve:**
-
 - Keep original opening and headings
 - Don't reorganize sections
 - Don't move architecture (just add brief intro if it leads)
@@ -108,46 +100,41 @@ For each content type below, the enhancement patterns are designed to ADD MINIMA
 **Example enhancement:**
 
 Original (8 lines):
-
 ```markdown
 # Internal DNS
 
 Manage DNS records for your private network.
 
-Internal DNS zones pair with Gateway resolver policies to control
+Internal DNS zones pair with Gateway resolver policies to control 
 DNS query responses.
 
 ## Features
-
 - Create internal zones
 - Configure views
 - Link to Gateway
 ```
 
 Enhanced (15 lines - 1.9x):
-
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS
+Manage DNS records for your private network without running your own DNS 
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS query
+Internal DNS zones pair with Gateway resolver policies to control DNS query 
 responses based on context (source IP, user identity, domain).
 
-**Example use case:** A multi-region company creates separate views for London
-and SF offices. Users query the same hostname (api.company.internal) but get
+**Example use case:** A multi-region company creates separate views for London 
+and SF offices. Users query the same hostname (api.company.internal) but get 
 different IP addresses based on location.
 
 ## Features
-
 - Create internal zones - Private namespaces accessible only via Gateway
 - Configure views - Logical groupings that route different users to different resources
 - Link to Gateway - Resolver policies determine which view to use
 ```
 
 What was added:
-
 - 1 sentence "why" (without running own servers)
 - Brief context for zones (source IP, user identity)
 - 1 example (3 lines)
@@ -169,7 +156,6 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
-
 - "What is..." or "Understanding..." titles
 - Explanatory content (not procedural)
 - "How it works" sections
@@ -178,7 +164,6 @@ What was added:
 - Analogies or metaphors (sometimes)
 
 **Confidence signals:**
-
 - Explains mechanisms, not steps
 - Educational tone
 - Links to related concepts
@@ -186,7 +171,6 @@ What was added:
 - Multiple explanation approaches
 
 **Example titles:**
-
 - "Understanding Rate Limiting"
 - "How Caching Works"
 - "What is Edge Computing?"
@@ -204,7 +188,6 @@ What was added:
 ### Simplification Pattern
 
 **Structure:**
-
 ```markdown
 # [Concept Name]
 
@@ -213,7 +196,6 @@ What was added:
 **What it is:** [Plain English definition without jargon]
 
 **Why you need it:**
-
 - [Benefit 1]
 - [Benefit 2]
 - [Benefit 3]
@@ -221,7 +203,6 @@ What was added:
 **How it works:** [Simplified technical explanation]
 
 **Real scenarios:**
-
 - [Use case 1 with context]
 - [Use case 2 with context]
 - [Use case 3 with context]
@@ -247,7 +228,6 @@ What was added:
 ### Detection Criteria
 
 **Look for:**
-
 - Action verbs in titles (Configure, Enable, Create, Set up)
 - Numbered steps or procedures
 - "Prerequisites" sections
@@ -256,7 +236,6 @@ What was added:
 - Command examples or code blocks
 
 **Confidence signals:**
-
 - Clear sequential structure
 - Specific actionable steps
 - Tool/UI references
@@ -264,7 +243,6 @@ What was added:
 - Troubleshooting sections
 
 **Example titles:**
-
 - "Enable Always Use HTTPS"
 - "Configure DNS Settings"
 - "Create a Worker"
@@ -287,7 +265,6 @@ What was added:
 **For how-to guides, preserve existing steps and add minimal context:**
 
 **Minimal additions:**
-
 1. **Add 1-2 sentence "what this accomplishes"** at top (if missing)
 2. **Add inline "why"** (1 sentence) for non-obvious steps
 3. **Add 1 example** showing when you'd use this (3-5 lines)
@@ -295,7 +272,6 @@ What was added:
 5. **Add 1-2 troubleshooting notes** for critical failures only
 
 **Preserve:**
-
 - Original step numbering and flow
 - Existing Dashboard/API paths (don't create new ones)
 - All screenshots and UI elements
@@ -304,7 +280,6 @@ What was added:
 **Example enhancement:**
 
 Original (12 lines):
-
 ```markdown
 # Create a DNS View
 
@@ -322,11 +297,10 @@ Use the create view endpoint with zone IDs.
 ```
 
 Enhanced (20 lines - 1.67x):
-
 ```markdown
 # Create a DNS View
 
-Create a logical grouping of zones that determines which DNS records users see.
+Create a logical grouping of zones that determines which DNS records users see. 
 Useful for multi-region setups or environment separation.
 
 **Example:** Create "London View" and "SF View" to route users to nearest datacenter.
@@ -353,7 +327,6 @@ curl -X POST /api/views -d '{"name": "London View", "zone_ids": ["id1", "id2"]}'
 ```
 
 What was added:
-
 - 2-sentence purpose statement (2 lines)
 - 1 example (1 line)
 - Inline context for 2 steps (2 lines)
@@ -363,13 +336,11 @@ What was added:
 - Total: 8 lines added to 12 original = 20 lines (1.67x) ✅
 
 **What was NOT added:**
-
 - Comprehensive troubleshooting section
 - Multiple examples
 - Separate "Understanding Views" section
 - Extensive testing procedures
-
-````
+```
 
 ### Common Issues to Fix
 
@@ -443,7 +414,7 @@ What was added:
 **Example:**
 ```[language]
 [Realistic usage example]
-````
+```
 
 **Result:** [What happens when this is used]
 
@@ -452,8 +423,7 @@ What was added:
 ### [Next Option]
 
 [Same structure...]
-
-````
+```
 
 ### Common Issues to Fix
 
@@ -543,25 +513,24 @@ Add records to the zone.
 curl -X POST https://api.cloudflare.com/zones/ID/dns_records \\
   -d '{"type": "A", "name": "app", "content": "192.168.1.100"}'
 \`\`\`
-````
+```
 
 Enhanced (35 lines - 1.75x):
-
 ```markdown
 ## Step 1: Create the zone
 
-Create an internal zone that will contain your DNS records. This zone is only
+Create an internal zone that will contain your DNS records. This zone is only 
 accessible via Gateway (not public DNS).
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones \\
--d '{
-"name": "company.internal", # Your internal domain
-"type": "internal" # Marks as internal-only
-}'
+  -d '{
+    "name": "company.internal",  # Your internal domain
+    "type": "internal"             # Marks as internal-only
+  }'
 \`\`\`
 
-**Example use:** A company creates company.internal for all internal apps
+**Example use:** A company creates company.internal for all internal apps 
 (app.company.internal, api.company.internal, db.company.internal).
 
 ## Step 2: Add DNS records
@@ -570,27 +539,24 @@ Add records mapping hostnames to private IPs.
 
 \`\`\`bash
 curl -X POST https://api.cloudflare.com/zones/ZONE_ID/dns_records \\
--d '{
-"type": "A", # Address record
-"name": "app.company.internal", # Full hostname
-"content": "192.168.1.100" # Private IP
-}'
+  -d '{
+    "type": "A",                           # Address record
+    "name": "app.company.internal",        # Full hostname
+    "content": "192.168.1.100"             # Private IP
+  }'
 \`\`\`
 
-**Test:**
+**Test:** 
 \`\`\`bash
 nslookup app.company.internal
-
 # Expected: Returns 192.168.1.100
-
 \`\`\`
 
-**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP
+**If it doesn't resolve:** Device must use Gateway as DNS resolver. Check WARP 
 connection or DNS settings.
 ```
 
 What was added:
-
 - Brief "why" for each step (1 sentence)
 - Inline code comments (3-4 comments)
 - 1 example showing usage (2 lines)
@@ -599,7 +565,6 @@ What was added:
 - Total: 15 lines added to 20 original = 35 lines (1.75x) ✅
 
 **What was NOT added:**
-
 - Separate "What you'll build" section
 - Multiple examples
 - Comprehensive troubleshooting section
@@ -649,19 +614,16 @@ What was added:
 Sometimes documentation combines types:
 
 ### Overview + How To
-
 **Pattern:** Product intro followed by quick start steps  
 **Approach:** Treat first section as Overview, steps as How To  
 **Example:** "Workers Overview" with "Deploy Your First Worker" steps
 
 ### Concept + Reference
-
 **Pattern:** Conceptual explanation followed by parameter reference  
 **Approach:** Layer explanation first, reference at bottom  
 **Example:** "Understanding Caching" + "Cache Headers Reference"
 
 ### Tutorial + Reference
-
 **Pattern:** Build project + API reference at end  
 **Approach:** Keep tutorial progressive, move reference to appendix  
 **Example:** "Build URL Shortener" + "Workers API Reference"
@@ -673,7 +635,6 @@ Sometimes documentation combines types:
 ## Quick Reference Cards
 
 ### Overview Page Card
-
 ```
 ✓ Opens with benefit statement
 ✓ Problem/Solution structure
@@ -683,7 +644,6 @@ Sometimes documentation combines types:
 ```
 
 ### Concept Page Card
-
 ```
 ✓ Analogy in first paragraph
 ✓ Plain definition
@@ -693,7 +653,6 @@ Sometimes documentation combines types:
 ```
 
 ### How To Page Card
-
 ```
 ✓ Context before steps
 ✓ Prerequisites listed
@@ -703,7 +662,6 @@ Sometimes documentation combines types:
 ```
 
 ### Reference Page Card
-
 ```
 ✓ Opening context
 ✓ Use-case organized
@@ -713,7 +671,6 @@ Sometimes documentation combines types:
 ```
 
 ### Tutorial Page Card
-
 ```
 ✓ "What you'll build"
 ✓ Prerequisites + time
diff --git a/.agents/skills/eli5/references/pattern-library.md b/.agents/skills/eli5/references/pattern-library.md
index f7ebb468915de2c..3d7b91b310a8918 100644
--- a/.agents/skills/eli5/references/pattern-library.md
+++ b/.agents/skills/eli5/references/pattern-library.md
@@ -7,7 +7,6 @@ A reference collection of reusable before/after patterns for simplifying technic
 ## Purpose
 
 This library provides:
-
 - **Reusable patterns** for common simplification scenarios
 - **Jargon → Plain English** translations
 - **Before/after examples** demonstrating transformations
@@ -20,7 +19,6 @@ This library provides:
 **All patterns below demonstrate minimal, integrated enhancements (1.5-2x growth)**
 
 When applying these patterns:
-
 - ✅ Add inline, not as separate major sections
 - ✅ Integrate with existing content flow
 - ✅ Keep examples brief (5-15 lines each, max 1-2 examples)
@@ -34,7 +32,6 @@ When applying these patterns:
 When a pattern shows "Add [section]" → Interpret as "add brief inline content" not "create major new section"
 
 **Example:**
-
 - Pattern says: "Add use case example"
 - **Correct:** Add 5-10 line example inline with concept
 - **Incorrect:** Create separate "Use Case Examples" section with 4 detailed scenarios
@@ -47,23 +44,23 @@ When a pattern shows "Add [section]" → Interpret as "add brief inline content"
 
 Common technical terms and their accessible alternatives:
 
-| Technical Term   | Plain English             | Context Example                                                      |
-| ---------------- | ------------------------- | -------------------------------------------------------------------- |
-| **Implement**    | Set up, turn on, use      | "Set up two-factor authentication" not "Implement 2FA"               |
-| **Utilize**      | Use                       | "Use the API" not "Utilize the API"                                  |
-| **Leverage**     | Use, take advantage of    | "Take advantage of caching" not "Leverage caching capabilities"      |
-| **Execute**      | Run                       | "Run the command" not "Execute the command"                          |
-| **Instantiate**  | Create                    | "Create a new Worker" not "Instantiate a Worker"                     |
-| **Terminate**    | Stop, end                 | "Stop the process" not "Terminate the process"                       |
-| **Subsequently** | Then, next                | "Then, configure the settings" not "Subsequently, configure"         |
-| **Optimal**      | Best                      | "Best performance" not "Optimal performance"                         |
-| **Facilitate**   | Help, enable              | "This helps you deploy faster" not "Facilitates rapid deployment"    |
-| **Invoke**       | Call, trigger             | "Call the function" not "Invoke the function"                        |
-| **Provision**    | Set up, create            | "Set up your server" not "Provision infrastructure"                  |
-| **Egress**       | Outgoing data             | "Data leaving your network" not "Egress traffic"                     |
-| **Ingress**      | Incoming data             | "Data entering your network" not "Ingress traffic"                   |
-| **Anycast**      | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
-| **Propagation**  | Spreading, updating       | "Changes spread globally" not "Configuration propagates"             |
+| Technical Term | Plain English | Context Example |
+|----------------|---------------|-----------------|
+| **Implement** | Set up, turn on, use | "Set up two-factor authentication" not "Implement 2FA" |
+| **Utilize** | Use | "Use the API" not "Utilize the API" |
+| **Leverage** | Use, take advantage of | "Take advantage of caching" not "Leverage caching capabilities" |
+| **Execute** | Run | "Run the command" not "Execute the command" |
+| **Instantiate** | Create | "Create a new Worker" not "Instantiate a Worker" |
+| **Terminate** | Stop, end | "Stop the process" not "Terminate the process" |
+| **Subsequently** | Then, next | "Then, configure the settings" not "Subsequently, configure" |
+| **Optimal** | Best | "Best performance" not "Optimal performance" |
+| **Facilitate** | Help, enable | "This helps you deploy faster" not "Facilitates rapid deployment" |
+| **Invoke** | Call, trigger | "Call the function" not "Invoke the function" |
+| **Provision** | Set up, create | "Set up your server" not "Provision infrastructure" |
+| **Egress** | Outgoing data | "Data leaving your network" not "Egress traffic" |
+| **Ingress** | Incoming data | "Data entering your network" not "Ingress traffic" |
+| **Anycast** | Routing to nearest server | "Automatically routes to the nearest location" not "Anycast routing" |
+| **Propagation** | Spreading, updating | "Changes spread globally" not "Configuration propagates" |
 
 ---
 
@@ -74,7 +71,6 @@ Common technical terms and their accessible alternatives:
 ### Example: Internal DNS Documentation
 
 **Before (Original - 15 lines):**
-
 ```markdown
 # Internal DNS
 
@@ -87,7 +83,6 @@ Internal DNS zones pair with Gateway resolver policies.
 Use the dashboard or API to create an internal zone.
 
 ### Dashboard
-
 1. Navigate to Internal DNS
 2. Click Create Zone
 3. Enter zone name
@@ -95,27 +90,25 @@ Use the dashboard or API to create an internal zone.
 ```
 
 **After (Enhanced - 26 lines, 1.73x growth):**
-
 ```markdown
 # Internal DNS
 
-Manage DNS records for your private network without running your own DNS
+Manage DNS records for your private network without running your own DNS 
 servers. This simplifies operations and integrates with Cloudflare Gateway.
 
-Internal DNS zones pair with Gateway resolver policies to control DNS
+Internal DNS zones pair with Gateway resolver policies to control DNS 
 responses based on source IP, user identity, or domain.
 
-**Example use case:** A multi-region company creates views for London and SF.
-Users query api.company.internal but get different IPs based on location
+**Example use case:** A multi-region company creates views for London and SF. 
+Users query api.company.internal but get different IPs based on location 
 (London users → 10.0.1.100, SF users → 10.0.2.100).
 
 ## Create a Zone
 
-Create an internal zone that will contain your DNS records. Zones are only
+Create an internal zone that will contain your DNS records. Zones are only 
 accessible via Gateway (not public DNS).
 
 ### Dashboard
-
 1. Navigate to Internal DNS → Zones
 2. Click **Create Zone**
 3. Enter zone name (e.g., company.internal)
@@ -125,9 +118,8 @@ accessible via Gateway (not public DNS).
 ```
 
 **What was added:**
-
 - 1 sentence explaining "why" (without running own servers) - 1 line
-- Brief context for resolver policies (source IP, user identity) - 1 line
+- Brief context for resolver policies (source IP, user identity) - 1 line  
 - 1 concrete example (3 lines)
 - Brief zone explanation (2 lines)
 - Inline step context (1 line each for 2 steps) - 2 lines
@@ -135,7 +127,6 @@ accessible via Gateway (not public DNS).
 - **Total added: 11 lines to 15 original = 26 lines (1.73x)** ✅
 
 **What was NOT added:**
-
 - No "What Problem Does Internal DNS Solve?" section
 - No "How It Works (Conceptual)" section before content
 - No diagram annotations
@@ -145,7 +136,6 @@ accessible via Gateway (not public DNS).
 - No separate "Understanding Zones" section
 
 **Why this works:**
-
 - Preserves original structure completely
 - Adds context inline where readers need it
 - Provides 1 concrete example for grounding
@@ -161,37 +151,33 @@ accessible via Gateway (not public DNS).
 ### Overview Pages
 
 **Before (Technical-first):**
-
 ```markdown
 ## Product X
 
-Product X is a distributed edge computing platform utilizing V8 isolates
-for low-latency serverless code execution with sub-millisecond cold start
+Product X is a distributed edge computing platform utilizing V8 isolates 
+for low-latency serverless code execution with sub-millisecond cold start 
 performance and global anycast deployment.
 ```
 
 **After (Benefit-first):**
-
 ```markdown
 ## Product X
 
-Run code worldwide without managing servers. Deploy in seconds, scale
+Run code worldwide without managing servers. Deploy in seconds, scale 
 automatically, and pay only for what you use.
 
-**What problem it solves:** Maintaining global infrastructure is expensive
+**What problem it solves:** Maintaining global infrastructure is expensive 
 and complex. Product X runs your code in 300+ cities automatically.
 
 **Perfect for:**
-
 - Applications needing fast global performance
-- Teams wanting to skip server management
+- Teams wanting to skip server management  
 - Projects with variable traffic
 
 [Get started →]
 ```
 
 **Why this works:**
-
 - Opens with clear user value
 - Problem framing creates relevance
 - "Perfect for" helps self-identification
@@ -204,39 +190,35 @@ and complex. Product X runs your code in 300+ cities automatically.
 ### Concept Pages
 
 **Before (Abstract):**
-
 ```markdown
 ## Caching
 
-Caching stores frequently accessed data in high-speed storage layers to
-reduce origin server load and improve response times through data locality
+Caching stores frequently accessed data in high-speed storage layers to 
+reduce origin server load and improve response times through data locality 
 optimization.
 ```
 
 **After (Concrete):**
-
 ```markdown
 ## Caching
 
-**Think of it like:** A library's reserve desk. Popular books stay at the
+**Think of it like:** A library's reserve desk. Popular books stay at the 
 front desk for quick access instead of requiring trips to the distant stacks.
 
-**What it is:** Caching keeps copies of your frequently accessed files
-(images, CSS, JavaScript) close to users, so they load instantly instead of
+**What it is:** Caching keeps copies of your frequently accessed files 
+(images, CSS, JavaScript) close to users, so they load instantly instead of 
 being fetched from your origin server every time.
 
 **Why it matters:**
-
 - Pages load 10x faster (50ms vs 500ms)
 - Reduces server costs (fewer origin requests)
 - Handles traffic spikes (serves from cache, not origin)
 
-**When to use:** Any content that doesn't change constantly—images, stylesheets,
+**When to use:** Any content that doesn't change constantly—images, stylesheets, 
 blog posts, product pages.
 ```
 
 **Why this works:**
-
 - Analogy creates immediate mental model
 - Plain language explanation builds understanding
 - Benefits are concrete and measurable
@@ -249,7 +231,6 @@ blog posts, product pages.
 ### How To Pages
 
 **Before (Steps-only):**
-
 ```markdown
 ## Enable Feature X
 
@@ -260,8 +241,7 @@ blog posts, product pages.
 ```
 
 **After (Contextual multi-path):**
-
-````markdown
+```markdown
 ## Enable Feature X
 
 **What this does:** Protects your site from [specific threat] by [mechanism].
@@ -277,7 +257,7 @@ blog posts, product pages.
 4. Find **Feature X** and toggle it **On**
 5. Click **Save Changes** at the bottom
 
-💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes
+💡 **Note:** Changes take effect immediately. Check Analytics in 5 minutes 
 to see it working.
 
 ### Via API
@@ -290,14 +270,12 @@ curl -X PATCH "https://api.example.com/v1/settings" \
   -H "Authorization: Bearer YOUR_TOKEN" \
   -d '{"feature_x_enabled": true}'
 ```
-````
 
 **Response:**
-
 ```json
 {
-	"success": true,
-	"result": { "feature_x_enabled": true }
+  "success": true,
+  "result": {"feature_x_enabled": true}
 }
 ```
 
@@ -309,8 +287,7 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 2. Check browser DevTools → Network tab
 3. Look for [specific indicator]
 4. You should see [expected result]
-
-````
+```
 
 **Why this works:**
 - Context explains purpose before steps
@@ -333,16 +310,15 @@ curl -X PATCH "https://api.example.com/v1/settings" \
 **Content-Type:** MIME type. Examples: text/html, application/json
 
 **Expires:** Cache expiration date. Format: HTTP-date
-````
+```
 
 **After (Use-case organized):**
-
-````markdown
+```markdown
 ## Headers by Purpose
 
 ### Controlling Cache Behavior
 
-**When to use:** Make your site faster by controlling what gets cached and
+**When to use:** Make your site faster by controlling what gets cached and 
 for how long.
 
 #### Long-Term Caching (Static Assets)
@@ -351,17 +327,15 @@ for how long.
 
 **What it does:** Caches content for 1 year
 
-**When to use:** Files that never change, like `logo-v2.png` or
+**When to use:** Files that never change, like `logo-v2.png` or 
 `style.abc123.css` with version hash in filename
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=31536000, immutable
 ```
-````
 
-**Result:** First visitor downloads. Next year, everyone gets the cached
+**Result:** First visitor downloads. Next year, everyone gets the cached 
 version instantly.
 
 ---
@@ -375,7 +349,6 @@ version instantly.
 **When to use:** Content that updates occasionally—blog posts, product pages
 
 **Example:**
-
 ```http
 Cache-Control: public, max-age=3600
 ```
@@ -389,8 +362,7 @@ Cache-Control: public, max-age=3600
 **When to use:** Tell browsers what type of content they're receiving.
 
 [Continue pattern...]
-
-````
+```
 
 **Why this works:**
 - Organized by task, not alphabet
@@ -417,9 +389,8 @@ async function handleRequest(request) {
   const url = new URL(request.url)
   return new Response('Hello')
 }
-````
-
-````
+```
+```
 
 **After (Explained progression):**
 ```markdown
@@ -433,7 +404,7 @@ A working [specific thing] that [specific capability].
 
 ### Who This Is For
 
-Developers comfortable with JavaScript. No prior experience needed with
+Developers comfortable with JavaScript. No prior experience needed with 
 [platform], but you should understand HTTP requests and JSON.
 
 ### Time: 30 minutes
@@ -457,16 +428,14 @@ async function handleRequest(request) {
     headers: { 'content-type': 'text/plain' }
   })
 }
-````
+```
 
 **What this code does:**
-
 - **Line 2:** Listens for HTTP requests to your Worker
-- **Line 4:** Calls `handleRequest` to process each request
+- **Line 4:** Calls `handleRequest` to process each request  
 - **Line 8-12:** Returns a simple text response
 
 **Test it:**
-
 1. Deploy this code
 2. Visit your Worker's URL
 3. You should see: "Hello! It works!"
@@ -476,8 +445,7 @@ Great! Your Worker is running. Now let's add real functionality...
 ## Step 2: Parse URLs
 
 [Continue building progressively with explanations...]
-
-````
+```
 
 **Why this works:**
 - Sets clear expectations upfront
@@ -497,13 +465,11 @@ Features:
 - Global anycast network
 - Automatic scaling
 - Pay-per-request pricing
-````
+```
 
 **After:**
-
 ```markdown
 **What you get:**
-
 - **Fast everywhere:** Code runs in 300+ cities, close to every user
 - **Auto-scaling:** Handles 10 requests or 10 million without configuration
 - **Cost-efficient:** Pay only when code runs, not for idle servers
@@ -512,29 +478,27 @@ Features:
 ### Transform 2: Jargon Explanation → Layered Understanding
 
 **Before:**
-
 ```markdown
-DDoS mitigation employs anycast architecture to distribute volumetric attacks
-across our edge network, utilizing L3/L4 packet inspection and L7 behavioral
+DDoS mitigation employs anycast architecture to distribute volumetric attacks 
+across our edge network, utilizing L3/L4 packet inspection and L7 behavioral 
 analysis.
 ```
 
 **After:**
-
 ```markdown
 **In plain language:** Stops attackers from overwhelming your site with fake traffic.
 
-**How it protects you:** We have 300+ data centers. When an attack hits, we
-spread it across all locations—like opening thousands of doors instead of one.
+**How it protects you:** We have 300+ data centers. When an attack hits, we 
+spread it across all locations—like opening thousands of doors instead of one. 
 We also identify and block fake visitors before they reach your site.
 
-**What happens:** Your real visitors get through normally while attack traffic
+**What happens:** Your real visitors get through normally while attack traffic 
 is filtered out automatically.
 
 <details>
 <summary>For technical users</summary>
 
-Anycast distributes L3/L4 volumetric attacks across the network. L7 protection
+Anycast distributes L3/L4 volumetric attacks across the network. L7 protection 
 uses JS challenges and behavioral fingerprinting. [Architecture details →]
 
 </details>
@@ -543,24 +507,21 @@ uses JS challenges and behavioral fingerprinting. [Architecture details →]
 ### Transform 3: Assumed Knowledge → Explicit Prerequisites
 
 **Before:**
-
 ```markdown
 Configure your A record to point to the anycast IP.
 ```
 
 **After:**
-
 ```markdown
 Update your DNS A record to point to Cloudflare's IP address.
 
-**What's an A record?** It's the DNS entry that tells the internet where your
+**What's an A record?** It's the DNS entry that tells the internet where your 
 website lives (like an address in a phone book).
 
-**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap,
+**Where to find it:** In your domain registrar's DNS settings (GoDaddy, Namecheap, 
 etc.). Look for "DNS Management" or "DNS Settings."
 
-**What to enter:**
-
+**What to enter:** 
 - Type: A
 - Name: @ (means your root domain)
 - Value: 192.0.2.1 (our IP address)
@@ -571,12 +532,10 @@ etc.). Look for "DNS Management" or "DNS Settings."
 ## Metaphor Templates
 
 ### Template: API Explanation
-
 ```markdown
 **Think of it like:** [Familiar interface concept]
 
 An API is like a restaurant menu. It shows you:
-
 - What's available to order (endpoints)
 - What details you need to provide (parameters: "no onions, extra cheese")
 - What you'll get back (response: your meal)
@@ -584,12 +543,11 @@ An API is like a restaurant menu. It shows you:
 
 You don't need to know how the kitchen works. Just order from the menu.
 
-**Where this breaks down:** Unlike restaurants where you wait, API responses
+**Where this breaks down:** Unlike restaurants where you wait, API responses 
 are usually instant. Also, APIs can return errors if your "order" is invalid.
 ```
 
 ### Template: Security Feature Explanation
-
 ```markdown
 **The threat:** [What attackers do]
 
@@ -601,26 +559,22 @@ Think of it like [security analogy]:
 [Concrete comparison that shows the protection model]
 
 **What happens automatically:**
-
 - [Protection 1]
 - [Protection 2]
 
 **What you control:**
-
 - [Setting 1]
 - [Setting 2]
 ```
 
 ### Template: Infrastructure Concept
-
 ```markdown
 **What it is:** [One-sentence plain English definition]
 
-**Real-world comparison:**
+**Real-world comparison:** 
 [Physical/familiar tech analog that maps 1:1 to key concepts]
 
 **Why it matters:**
-
 - [Benefit 1 with measurable impact]
 - [Benefit 2 with measurable impact]
 
@@ -636,25 +590,24 @@ Think of it like [security analogy]:
 
 ### When You See → Do This
 
-| **Original**                 | **Transform To**                                         |
-| ---------------------------- | -------------------------------------------------------- |
-| Technical architecture first | Problem → Solution → Benefit                             |
-| Abstract concept             | Analogy → Plain explanation → Technical                  |
-| Steps without context        | Context → Prerequisites → Multi-path steps               |
-| Alphabetical reference       | Use-case groups → Two-tier descriptions                  |
-| Unexplained code             | What you'll build → Progressive steps → Explained blocks |
-| Feature list                 | Problem/solution pairs with benefits                     |
-| Jargon without definition    | Define inline or use plain alternative                   |
-| Missing "why"                | Add value proposition upfront                            |
-| No use cases                 | Add 3-5 realistic scenarios                              |
-| Assumes knowledge            | State prerequisites explicitly                           |
+| **Original** | **Transform To** |
+|--------------|------------------|
+| Technical architecture first | Problem → Solution → Benefit |
+| Abstract concept | Analogy → Plain explanation → Technical |
+| Steps without context | Context → Prerequisites → Multi-path steps |
+| Alphabetical reference | Use-case groups → Two-tier descriptions |
+| Unexplained code | What you'll build → Progressive steps → Explained blocks |
+| Feature list | Problem/solution pairs with benefits |
+| Jargon without definition | Define inline or use plain alternative |
+| Missing "why" | Add value proposition upfront |
+| No use cases | Add 3-5 realistic scenarios |
+| Assumes knowledge | State prerequisites explicitly |
 
 ---
 
 ## Best Practices Summary
 
 ### Do:
-
 ✅ Lead with benefits and problems solved  
 ✅ Use tech-adjacent metaphors with stated limitations  
 ✅ Provide both Dashboard and API paths  
@@ -662,10 +615,9 @@ Think of it like [security analogy]:
 ✅ Explain every code block  
 ✅ State prerequisites before steps  
 ✅ Include verification/testing sections  
-✅ Add "For technical users" collapsible sections
+✅ Add "For technical users" collapsible sections  
 
 ### Don't:
-
 ❌ Start with technical architecture  
 ❌ Use condescending language ("simply," "just," "obviously")  
 ❌ Assume prior knowledge without stating it  
@@ -673,7 +625,7 @@ Think of it like [security analogy]:
 ❌ Organize specs alphabetically without context  
 ❌ Drop code without explanation  
 ❌ Skip the "why" to get to "how" faster  
-❌ Sacrifice accuracy for brevity
+❌ Sacrifice accuracy for brevity  
 
 ---
 
diff --git a/.github/review-template.md b/.github/review-template.md
index 4aee0df6e1cf7ed..0e56cc03451cac7 100644
--- a/.github/review-template.md
+++ b/.github/review-template.md
@@ -1,9 +1,8 @@
 ## Author self-review
 
 I've reviewed my PR for the following:
-
 - [ ] Metadata in the frontmatter, including `pcx_content_type` and - for tutorials - `updated: YYYY-MM-DD`.
 - [ ] PCX content strategy overall.
 - [ ] PCX style guidelines (product names, capitalization, etc.).
 - [ ] Needed redirects (if deleting any existing pages).
-- [ ] Code blocks && other formatting issues (bolding, italics, lists).
+- [ ] Code blocks && other formatting issues (bolding, italics, lists).
\ No newline at end of file
diff --git a/.opencode/command/styleguide.md b/.opencode/command/styleguide.md
index fbacc3b8e40c886..085e070750f199c 100644
--- a/.opencode/command/styleguide.md
+++ b/.opencode/command/styleguide.md
@@ -49,7 +49,6 @@ Look at all the unstaged changes to markdown (.md, .mdx) files, pull out the lin
 ## Output Format
 
 For each issue found, report:
-
 - The problematic text (quote it)
 - Which rule it violates
 - A suggested fix
diff --git a/.windsurf/rules/general-rules.md b/.windsurf/rules/general-rules.md
index 7efe2f90487c8d4..e563c09c965c3cf 100644
--- a/.windsurf/rules/general-rules.md
+++ b/.windsurf/rules/general-rules.md
@@ -61,4 +61,4 @@ This code would only be rendered if the page has a magicWord variable set to "ha
 - Replace `sh` blocks using `npm commands` with our [`PackageManagers` component](https://developers.cloudflare.com/style-guide/components/package-managers/).
 - Replace in-text mentions of Cloudflare's number of data centers, network capacity, or network peers with our [`PublicStats` component](https://developers.cloudflare.com/style-guide/components/public-stats/).
 - Replace `toml` or `json` code blocks with [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/#sample-wrangler-configuration) information with our [`WranglerConfig` component](https://developers.cloudflare.com/style-guide/components/wrangler-config/).
-- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
+- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 198fa9cdc3bf951..7d3e71c75126c9f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,10 +1,9 @@
 # Contributing to Cloudflare's developer documentation
 
 Everyone, including those who are not part of the Cloudflare organization, are encouraged to contribute.
-
 - If you are not a Cloudflare employee, learn how to contribute in the [contribution page](https://developers.cloudflare.com/style-guide/contributions/) of the Cloudflare Style Guide.
 - If you are a Cloudflare employee, reach out via our Developer Docs space in Google chat.
 
 Consult the [Cloudflare Style Guide](https://developers.cloudflare.com/style-guide/) on everything from grammar, to formatting, to frontmatter requirements. Browse our [components](/style-guide/components/) to add additional formatting.
 
-Thank you for helping us to maintain quality documentation.
+Thank you for helping us to maintain quality documentation.
\ No newline at end of file
diff --git a/MIGRATION.md b/MIGRATION.md
index 4ac50851fe0e52b..622c020aee16f4d 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -18,7 +18,7 @@
 ## High-risk items and unknowns
 
 | Item                                                  | Risk   | Status                                                        |
-| ----------------------------------------------------- | ------ | ------------------------------------------------------------- |
+|-------------------------------------------------------|--------|---------------------------------------------------------------|
 | **`Page.astro` Vite alias**                           | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`patch-package` hunks against Starlight internals** | HIGH   | Unknown — We're coupled to low-level private implementation   |
 | **`starlight-links-validator` Zod 4 incompatibility** | HIGH   | Confirmed broken upstream                                     |
@@ -42,7 +42,7 @@ Targets are determined by [withastro/docs#13230].
 That is the north star.
 
 | Package                        | Current  | Target                                                 |
-| ------------------------------ | -------- | ------------------------------------------------------ |
+| ------------------------------ | -------- |--------------------------------------------------------|
 | `astro`                        | `5.13.7` | `6.0.0-beta.8`                                         |
 | `@astrojs/starlight`           | `0.36.0` | `https://pkg.pr.new/@astrojs/starlight@3644`           |
 | `@astrojs/starlight-docsearch` | `0.6.0`  | `https://pkg.pr.new/@astrojs/starlight-docsearch@3644` |
diff --git a/src/components/AutoconfigDiagram.astro b/src/components/AutoconfigDiagram.astro
index bc843cdd921273a..dafb15f5e6c8c24 100644
--- a/src/components/AutoconfigDiagram.astro
+++ b/src/components/AutoconfigDiagram.astro
@@ -21,15 +21,10 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon">
 						<slot name="icon">
-							<svg
-								viewBox="0 0 24 24"
-								fill="none"
-								stroke="currentColor"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</slot>
 					</div>
@@ -48,17 +43,15 @@ const { framework, configs } = Astro.props;
 				<div class="config-box">
 					<span class="config-title">Generated configuration</span>
 					<div class="config-items">
-						{
-							configs.map((config, i) => (
-								<div class="config-item" data-config-index={i}>
-									<div class="config-file">{config.file}</div>
-									<div class="config-detail">
-										<span class="config-label">{config.label}:</span>
-										<span class="config-value">{config.value}</span>
-									</div>
+						{configs.map((config, i) => (
+							<div class="config-item" data-config-index={i}>
+								<div class="config-file">{config.file}</div>
+								<div class="config-detail">
+									<span class="config-label">{config.label}:</span>
+									<span class="config-value">{config.value}</span>
 								</div>
-							))
-						}
+							</div>
+						))}
 					</div>
 				</div>
 			</div>
@@ -71,12 +64,8 @@ const { framework, configs } = Astro.props;
 				<div class="node-card">
 					<div class="node-icon workers-icon">
 						<svg viewBox="0 0 24 24" fill="none">
-							<path
-								d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z"
-								fill="#F6821F"></path>
-							<path
-								d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z"
-								fill="#FBAD41"></path>
+							<path d="M16.934 8.638l-5.669-3.14a2.91 2.91 0 00-2.82.027l-5.248 3.14A2.873 2.873 0 002 11.296V16.5c0 1.063.59 2.04 1.537 2.543l5.669 3.14a2.91 2.91 0 002.82-.027l5.248-3.14A2.873 2.873 0 0018.5 16.5v-5.204c0-1.063-.59-2.04-1.566-2.658z" fill="#F6821F"/>
+							<path d="M16.934 8.638a2.873 2.873 0 011.566 2.543v5.204c0 1.063-.59 2.04-1.537 2.543L11.714 22l-1.49-7.34 6.71-5.022z" fill="#FBAD41"/>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -90,9 +79,7 @@ const { framework, configs } = Astro.props;
 		<!-- Status indicator -->
 		<div class="status-indicator">
 			<div class="status-dot"></div>
-			<span class="status-text"
-				>Wrangler handles configuration automatically</span
-			>
+			<span class="status-text">Wrangler handles configuration automatically</span>
 		</div>
 	</div>
 </autoconfig-diagram>
@@ -144,9 +131,7 @@ const { framework, configs } = Astro.props;
 		padding: 0.75rem 1rem;
 		border: 1px solid rgb(229 229 229);
 		min-width: 120px;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -338,8 +323,7 @@ const { framework, configs } = Astro.props;
 
 	.config-file {
 		font-size: 0.625rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		color: rgb(115 115 115);
 		margin-bottom: 0.125rem;
 	}
@@ -350,8 +334,7 @@ const { framework, configs } = Astro.props;
 
 	.config-detail {
 		font-size: 0.6875rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 	}
 
 	.config-label {
@@ -410,13 +393,8 @@ const { framework, configs } = Astro.props;
 	}
 
 	@keyframes pulse {
-		0%,
-		100% {
-			opacity: 1;
-		}
-		50% {
-			opacity: 0.5;
-		}
+		0%, 100% { opacity: 1; }
+		50% { opacity: 0.5; }
 	}
 
 	.status-text {
@@ -437,10 +415,10 @@ const { framework, configs } = Astro.props;
 <script>
 	class AutoconfigDiagram extends HTMLElement {
 		private isRunning = false;
-		private framework = "";
+		private framework = '';
 
 		connectedCallback() {
-			this.framework = this.dataset.framework || "";
+			this.framework = this.dataset.framework || '';
 			// Auto-start after a short delay
 			setTimeout(() => this.run(), 500);
 		}
@@ -449,90 +427,87 @@ const { framework, configs } = Astro.props;
 			if (this.isRunning) return;
 			this.isRunning = true;
 
-			const statusIndicator = this.querySelector(".status-indicator");
-			const statusText = this.querySelector(".status-text");
+			const statusIndicator = this.querySelector('.status-indicator');
+			const statusText = this.querySelector('.status-text');
 
 			// Reset state
 			this.resetState();
 
 			// Update status
-			statusIndicator?.classList.add("running");
-			if (statusText)
-				statusText.textContent = `Detecting ${this.framework} project...`;
+			statusIndicator?.classList.add('running');
+			if (statusText) statusText.textContent = `Detecting ${this.framework} project...`;
 
 			await this.delay(900);
 
 			// Step 1: Framework detected
-			const frameworkNode = this.querySelector(".framework-node");
-			frameworkNode?.classList.add("active");
+			const frameworkNode = this.querySelector('.framework-node');
+			frameworkNode?.classList.add('active');
 			if (statusText) statusText.textContent = `${this.framework} detected`;
 
 			await this.delay(1200);
 
 			// Step 2: First connector
-			const connectors = this.querySelectorAll(".connector");
-			connectors[0]?.classList.add("active");
+			const connectors = this.querySelectorAll('.connector');
+			connectors[0]?.classList.add('active');
 
 			await this.delay(600);
 
 			// Step 3: Config section
-			const configSection = this.querySelector(".config-section");
-			configSection?.classList.add("active");
-			if (statusText) statusText.textContent = "Generating configuration...";
+			const configSection = this.querySelector('.config-section');
+			configSection?.classList.add('active');
+			if (statusText) statusText.textContent = 'Generating configuration...';
 
 			await this.delay(600);
 
 			// Show config items one by one
-			const configItems = this.querySelectorAll(".config-item");
+			const configItems = this.querySelectorAll('.config-item');
 			for (let i = 0; i < configItems.length; i++) {
 				const item = configItems[i];
-				item.classList.add("visible", "active");
-
+				item.classList.add('visible', 'active');
+				
 				// Get the config value for status
-				const valueEl = item.querySelector(".config-value");
-				const labelEl = item.querySelector(".config-label");
+				const valueEl = item.querySelector('.config-value');
+				const labelEl = item.querySelector('.config-label');
 				if (valueEl && labelEl) {
-					const label = labelEl.textContent?.replace(":", "") || "";
-					const value = valueEl.textContent || "";
-					if (statusText)
-						statusText.textContent = `Setting ${label} → ${value}`;
+					const label = labelEl.textContent?.replace(':', '') || '';
+					const value = valueEl.textContent || '';
+					if (statusText) statusText.textContent = `Setting ${label} → ${value}`;
 				}
 
 				await this.delay(1400);
-				item.classList.remove("active");
+				item.classList.remove('active');
 			}
 
 			await this.delay(500);
 
 			// Step 4: Second connector
-			connectors[1]?.classList.add("active");
-			if (statusText) statusText.textContent = "Deploying to Workers...";
+			connectors[1]?.classList.add('active');
+			if (statusText) statusText.textContent = 'Deploying to Workers...';
 
 			await this.delay(900);
 
 			// Step 5: Workers node
-			const workersNode = this.querySelector(".workers-node");
-			workersNode?.classList.add("active");
+			const workersNode = this.querySelector('.workers-node');
+			workersNode?.classList.add('active');
 
 			await this.delay(600);
 
 			// Complete - keep orange theme
-			frameworkNode?.classList.remove("active");
-			frameworkNode?.classList.add("connected");
-			configSection?.classList.remove("active");
-			configSection?.classList.add("connected");
-			connectors.forEach((c) => {
-				c.classList.remove("active");
-				c.classList.add("connected");
+			frameworkNode?.classList.remove('active');
+			frameworkNode?.classList.add('connected');
+			configSection?.classList.remove('active');
+			configSection?.classList.add('connected');
+			connectors.forEach(c => {
+				c.classList.remove('active');
+				c.classList.add('connected');
 			});
-			configItems.forEach((item) => item.classList.add("visible"));
-			workersNode?.classList.remove("active");
-			workersNode?.classList.add("connected");
+			configItems.forEach(item => item.classList.add('visible'));
+			workersNode?.classList.remove('active');
+			workersNode?.classList.add('connected');
 
-			statusIndicator?.classList.remove("running");
-			statusIndicator?.classList.add("complete");
-			if (statusText)
-				statusText.textContent = "Deployed to Cloudflare Workers!";
+			statusIndicator?.classList.remove('running');
+			statusIndicator?.classList.add('complete');
+			if (statusText) statusText.textContent = 'Deployed to Cloudflare Workers!';
 
 			this.isRunning = false;
 
@@ -543,18 +518,18 @@ const { framework, configs } = Astro.props;
 
 		private resetState() {
 			// Remove all state classes
-			this.querySelectorAll(".active, .connected, .visible").forEach((el) => {
-				el.classList.remove("active", "connected", "visible");
+			this.querySelectorAll('.active, .connected, .visible').forEach(el => {
+				el.classList.remove('active', 'connected', 'visible');
 			});
-
-			const statusIndicator = this.querySelector(".status-indicator");
-			statusIndicator?.classList.remove("running", "complete");
+			
+			const statusIndicator = this.querySelector('.status-indicator');
+			statusIndicator?.classList.remove('running', 'complete');
 		}
 
 		private delay(ms: number): Promise<void> {
-			return new Promise((resolve) => setTimeout(resolve, ms));
+			return new Promise(resolve => setTimeout(resolve, ms));
 		}
 	}
 
-	customElements.define("autoconfig-diagram", AutoconfigDiagram);
+	customElements.define('autoconfig-diagram', AutoconfigDiagram);
 </script>
diff --git a/src/components/ComponentUsage.astro b/src/components/ComponentUsage.astro
index 66ee88e6d14b810..4a3bf2d7677a098 100644
--- a/src/components/ComponentUsage.astro
+++ b/src/components/ComponentUsage.astro
@@ -18,8 +18,7 @@ const usage = await getComponentsUsage(component);
 
 <>
 	<p>
-		The <code>{component}</code> component is used <code>{usage.count}</code> times
-		on{" "}
+		The <code>{component}</code> component is used <code>{usage.count}</code> times on{" "}
 		<code>{usage.pages.size}</code> pages.
 	</p>
 	<Details header={`See all examples of pages that use ${component}`}>
diff --git a/src/components/FeatureTable.astro b/src/components/FeatureTable.astro
index e9dd6c485730d49..8af0f2ee817b163 100644
--- a/src/components/FeatureTable.astro
+++ b/src/components/FeatureTable.astro
@@ -34,44 +34,12 @@ const markdown = (content: any) => {
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-			></th>
-			{
-				hasFree && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Free
-					</th>
-				)
-			}
-			{
-				hasPro && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Pro
-					</th>
-				)
-			}
-			{
-				hasBiz && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Business
-					</th>
-				)
-			}
-			{
-				hasEnt && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						Enterprise
-					</th>
-				)
-			}
-			{
-				hasEntPlus && (
-					<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">
-						{plan.ent_plus}
-					</th>
-				)
-			}
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"></th>
+			{hasFree && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Free</th>}
+			{hasPro && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Pro</th>}
+			{hasBiz && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Business</th>}
+			{hasEnt && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Enterprise</th>}
+			{hasEntPlus && <th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">{plan.ent_plus}</th>}
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/LayerCard.astro b/src/components/LayerCard.astro
index 52528db54e544c5..f809ad95620577b 100644
--- a/src/components/LayerCard.astro
+++ b/src/components/LayerCard.astro
@@ -8,17 +8,17 @@ const { header = "Next Steps", href } = Astro.props;
 ---
 
 <div
-	class="bg-cl1-gray-9 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1 flex w-full flex-col overflow-hidden rounded-lg text-base ring-1"
+	class="flex w-full flex-col overflow-hidden rounded-lg bg-cl1-gray-9 text-base ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-0 dark:ring-cl1-gray-1"
 >
 	<div
-		class="bg-cl1-gray-9 text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7 -my-2 flex items-center justify-between gap-2 p-4 text-base font-medium"
+		class="-my-2 flex items-center justify-between gap-2 bg-cl1-gray-9 p-4 text-base font-medium text-cl1-gray-4 dark:bg-cl1-gray-1 dark:text-cl1-gray-7"
 	>
 		<div>{header}</div>
 		{
 			href && (
 				<a
 					href={href}
-					class="text-cl1-gray-0 hover:bg-cl1-gray-8 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3 flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent no-underline focus-visible:outline focus-visible:outline-1"
+					class="flex size-[1.625rem] shrink-0 cursor-pointer items-center justify-center rounded-md bg-transparent text-cl1-gray-0 no-underline hover:bg-cl1-gray-8 focus-visible:outline focus-visible:outline-1 focus-visible:outline-cl1-gray-8 dark:text-cl1-gray-7 dark:hover:bg-cl1-gray-2 dark:focus-visible:outline-cl1-gray-3"
 					aria-label={`Go to ${header.toLowerCase()}`}
 				>
 					<svg
@@ -35,7 +35,7 @@ const { header = "Next Steps", href } = Astro.props;
 		}
 	</div>
 	<div
-		class="bg-cl1-white ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2 relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg p-4 pr-3 ring-1"
+		class="relative mt-0 flex flex-col gap-2 overflow-hidden rounded-lg bg-cl1-white p-4 pr-3 ring-1 ring-cl1-gray-8 dark:bg-cl1-gray-2 dark:ring-cl1-gray-2"
 	>
 		<slot />
 	</div>
diff --git a/src/components/LlmsTxtDirective.astro b/src/components/LlmsTxtDirective.astro
index 87d72771289a198..f9ea644e578be8b 100644
--- a/src/components/LlmsTxtDirective.astro
+++ b/src/components/LlmsTxtDirective.astro
@@ -11,9 +11,9 @@ const llmsTxt = productPrefix
 ---
 
 <blockquote class="llms-txt-directive" aria-hidden="true">
-	Documentation Index<br />
-	Fetch the complete documentation index at: {llmsTxt}<br />
-	Use this file to discover all available pages before exploring further.
+Documentation Index<br/>
+Fetch the complete documentation index at: {llmsTxt}<br/>
+Use this file to discover all available pages before exploring further.
 </blockquote>
 
 <style>
diff --git a/src/components/PagesBuildPresetsTable.astro b/src/components/PagesBuildPresetsTable.astro
index 6383eeb9e7e6adc..93b77d7c42a275a 100644
--- a/src/components/PagesBuildPresetsTable.astro
+++ b/src/components/PagesBuildPresetsTable.astro
@@ -14,18 +14,9 @@ const entries = Object.values(presets);
 <table class="not-content w-full text-left text-[var(--sl-color-text)]">
 	<thead>
 		<tr>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Framework/tool</th
-			>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Build command</th
-			>
-			<th
-				class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold"
-				>Build directory</th
-			>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Framework/tool</th>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build command</th>
+			<th class="border-b border-[color:var(--color-table-fill)] bg-[var(--color-table-base)] px-4 py-3 text-[0.8125rem] font-semibold">Build directory</th>
 		</tr>
 	</thead>
 	<tbody>
diff --git a/src/components/ProductReleaseNotes.astro b/src/components/ProductReleaseNotes.astro
index 5cf7314aeee4f17..df5a3cc1ee2cd47 100644
--- a/src/components/ProductReleaseNotes.astro
+++ b/src/components/ProductReleaseNotes.astro
@@ -15,7 +15,9 @@ if (!page) {
 	);
 }
 
-if (!page.data.release_notes_file_name) {
+if (
+	!page.data.release_notes_file_name
+) {
 	throw new Error(
 		`[ProductReleaseNotes] ${Astro.params.slug} does not have a 'release_notes_file_name' frontmatter property.`,
 	);
@@ -30,7 +32,8 @@ if (
 	);
 }
 
-const name = page.data.release_notes_file_name?.[0];
+const name =
+	page.data.release_notes_file_name?.[0];
 
 let releaseNotes;
 
diff --git a/src/components/R2LocalUploadsdiagram.astro b/src/components/R2LocalUploadsdiagram.astro
index 067f6f1892e41e6..6d717c9406d70af 100644
--- a/src/components/R2LocalUploadsdiagram.astro
+++ b/src/components/R2LocalUploadsdiagram.astro
@@ -1,49 +1,32 @@
 ---
 interface Props {
-	mode?: "without" | "with" | "comparison";
+	mode?: 'without' | 'with' | 'comparison';
 	autoPlay?: boolean;
 	loop?: boolean;
 }
 
-const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
+const { mode = 'comparison', autoPlay = true, loop = true } = Astro.props;
 ---
 
-<r2-local-uploads-diagram
-	data-mode={mode}
-	data-autoplay={autoPlay}
-	data-loop={loop}
->
+<r2-local-uploads-diagram data-mode={mode} data-autoplay={autoPlay} data-loop={loop}>
 	<div class="diagram-wrapper">
-		{
-			mode === "comparison" && (
-				<div class="toggle-container">
-					<span class="toggle-label" id="local-uploads-label">
-						Local uploads
-					</span>
-					<label class="toggle-switch" aria-labelledby="local-uploads-label">
-						<input
-							type="checkbox"
-							class="toggle-input"
-							aria-labelledby="local-uploads-label"
-						/>
-						<span class="toggle-slider" />
-					</label>
-				</div>
-			)
-		}
+		{mode === 'comparison' && (
+			<div class="toggle-container">
+				<span class="toggle-label" id="local-uploads-label">Local uploads</span>
+				<label class="toggle-switch" aria-labelledby="local-uploads-label">
+					<input type="checkbox" class="toggle-input" aria-labelledby="local-uploads-label" />
+					<span class="toggle-slider"></span>
+				</label>
+			</div>
+		)}
 		<div class="diagram-container">
 			<!-- Client node -->
 			<div class="flow-node" data-step="1">
 				<div class="node-card">
 					<div class="node-badge">
-						<svg
-							fill="none"
-							stroke="currentColor"
-							viewBox="0 0 24 24"
-							stroke-width="2"
-						>
-							<rect x="3" y="4" width="18" height="12" rx="2"></rect>
-							<path d="M7 20h10M12 16v4"></path>
+						<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+							<rect x="3" y="4" width="18" height="12" rx="2"/>
+							<path d="M7 20h10M12 16v4"/>
 						</svg>
 					</div>
 					<div class="node-info">
@@ -63,15 +46,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				<div class="group-content edge-single">
 					<div class="bucket-component gateway-node-without">
 						<div class="component-icon gateway">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -83,74 +61,21 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			<div class="split-area without-local-uploads" data-connector="2-bucket">
 				<svg class="split-svg" viewBox="0 0 320 100" preserveAspectRatio="none">
 					<!-- Stem from node above -->
-					<line
-						class="split-line stem data-path"
-						x1="160"
-						y1="0"
-						x2="160"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line stem data-path" x1="160" y1="0" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Horizontal bar - left half (metadata) -->
-					<line
-						class="split-line horizontal-left metadata-path"
-						x1="85"
-						y1="20"
-						x2="160"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line horizontal-left metadata-path" x1="85" y1="20" x2="160" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Horizontal bar - right half (object data) -->
-					<line
-						class="split-line horizontal-right data-path"
-						x1="160"
-						y1="20"
-						x2="235"
-						y2="20"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line horizontal-right data-path" x1="160" y1="20" x2="235" y2="20" stroke="currentColor" stroke-width="2"/>
 					<!-- Left branch (metadata) -->
-					<line
-						class="split-line left-branch-top metadata-path"
-						x1="85"
-						y1="20"
-						x2="85"
-						y2="50"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line left-branch-top metadata-path" x1="85" y1="20" x2="85" y2="50" stroke="currentColor" stroke-width="2"/>
 					<!-- Right branch (object data) -->
-					<line
-						class="split-line right-branch-top data-path"
-						x1="235"
-						y1="20"
-						x2="235"
-						y2="50"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line right-branch-top data-path" x1="235" y1="20" x2="235" y2="50" stroke="currentColor" stroke-width="2"/>
 					<!-- Labels positioned on the lines -->
-					<text x="85" y="67" text-anchor="middle" class="svg-label"
-						>Object metadata</text
-					>
-					<text x="235" y="67" text-anchor="middle" class="svg-label"
-						>Object data</text
-					>
+					<text x="85" y="67" text-anchor="middle" class="svg-label">Object metadata</text>
+					<text x="235" y="67" text-anchor="middle" class="svg-label">Object data</text>
 					<!-- Continue lines to bucket -->
-					<line
-						class="split-line left-branch-bottom metadata-path"
-						x1="85"
-						y1="72"
-						x2="85"
-						y2="100"
-						stroke="currentColor"
-						stroke-width="2"></line>
-					<line
-						class="split-line right-branch-bottom data-path"
-						x1="235"
-						y1="72"
-						x2="235"
-						y2="100"
-						stroke="currentColor"
-						stroke-width="2"></line>
+					<line class="split-line left-branch-bottom metadata-path" x1="85" y1="72" x2="85" y2="100" stroke="currentColor" stroke-width="2"/>
+					<line class="split-line right-branch-bottom data-path" x1="235" y1="72" x2="235" y2="100" stroke="currentColor" stroke-width="2"/>
 				</svg>
 			</div>
 
@@ -162,15 +87,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<!-- R2 Gateway Worker -->
 					<div class="bucket-component gateway-node-local">
 						<div class="component-icon gateway">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<path d="M12 2L2 7l10 5 10-5-10-5z"></path>
-								<path d="M2 17l10 5 10-5"></path>
-								<path d="M2 12l10 5 10-5"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<path d="M12 2L2 7l10 5 10-5-10-5z"/>
+								<path d="M2 17l10 5 10-5"/>
+								<path d="M2 12l10 5 10-5"/>
 							</svg>
 						</div>
 						<span class="component-name">R2 Gateway Worker</span>
@@ -180,15 +100,10 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<!-- Local Object Data Infra -->
 					<div class="bucket-component local-storage-node">
 						<div class="component-icon storage">
-							<svg
-								fill="none"
-								stroke="currentColor"
-								viewBox="0 0 24 24"
-								stroke-width="2"
-							>
-								<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
-								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
-								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
+							<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+								<ellipse cx="12" cy="6" rx="8" ry="3"/>
+								<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
+								<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
 							</svg>
 						</div>
 						<span class="component-name">Object Data Infra</span>
@@ -197,10 +112,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			</div>
 
 			<!-- WITH local uploads: Two lines down to bucket -->
-			<div
-				class="local-split-columns with-local-uploads hidden"
-				data-connector="local-split"
-			>
+			<div class="local-split-columns with-local-uploads hidden" data-connector="local-split">
 				<div class="split-col left-col">
 					<div class="v-connector meta-line"></div>
 					<div class="split-label-row">
@@ -212,8 +124,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<div class="v-connector replication-line"></div>
 					<div class="split-label-row">
 						<svg class="progress-ring" viewBox="0 0 20 20">
-							<circle class="progress-ring-bg" cx="10" cy="10" r="8"></circle>
-							<circle class="progress-ring-fill" cx="10" cy="10" r="8"></circle>
+							<circle class="progress-ring-bg" cx="10" cy="10" r="8" />
+							<circle class="progress-ring-fill" cx="10" cy="10" r="8" />
 						</svg>
 						<span class="split-col-label replication">Object data</span>
 					</div>
@@ -229,31 +141,19 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 					<div class="group-content">
 						<div class="bucket-component" data-component="metadata">
 							<div class="component-icon">
-								<svg
-									fill="none"
-									stroke="currentColor"
-									viewBox="0 0 24 24"
-									stroke-width="2"
-								>
-									<circle cx="12" cy="12" r="10"></circle>
-									<path
-										d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"
-									></path>
+								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+									<circle cx="12" cy="12" r="10"/>
+									<path d="M2 12h20M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"/>
 								</svg>
 							</div>
 							<span class="component-name">Metadata Service</span>
 						</div>
 						<div class="bucket-component" data-component="object-data">
 							<div class="component-icon">
-								<svg
-									fill="none"
-									stroke="currentColor"
-									viewBox="0 0 24 24"
-									stroke-width="2"
-								>
-									<ellipse cx="12" cy="6" rx="8" ry="3"></ellipse>
-									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"></path>
-									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"></path>
+								<svg fill="none" stroke="currentColor" viewBox="0 0 24 24" stroke-width="2">
+									<ellipse cx="12" cy="6" rx="8" ry="3"/>
+									<path d="M4 6v4c0 1.66 3.58 3 8 3s8-1.34 8-3V6"/>
+									<path d="M4 10v4c0 1.66 3.58 3 8 3s8-1.34 8-3v-4"/>
 								</svg>
 							</div>
 							<span class="component-name">Object Data Infra</span>
@@ -264,15 +164,9 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		</div>
 		<!-- Status indicator -->
 		<div class="status-indicator">
-			<svg
-				class="status-check"
-				viewBox="0 0 24 24"
-				fill="none"
-				stroke="currentColor"
-				stroke-width="2.5"
-			>
-				<circle cx="12" cy="12" r="10" class="status-circle"></circle>
-				<path d="M8 12l3 3 5-5" class="status-checkmark"></path>
+			<svg class="status-check" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.5">
+				<circle cx="12" cy="12" r="10" class="status-circle" />
+				<path d="M8 12l3 3 5-5" class="status-checkmark" />
 			</svg>
 			<span class="status-text">Data is uploaded and accessible</span>
 		</div>
@@ -376,6 +270,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		width: 100%;
 	}
 
+
+
 	/* Vertical connector line between nodes */
 	.connector {
 		width: 2px;
@@ -407,9 +303,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		border: 1px solid rgb(229 229 229);
 		width: 220px;
 		margin: 0 !important;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .node-card {
@@ -472,8 +366,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 
 	.node-name {
 		font-size: 0.8125rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 	}
@@ -642,9 +535,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		padding: 0.5rem;
 		margin: 0 !important;
 		box-sizing: border-box;
-		transition:
-			border-color 0.3s ease,
-			box-shadow 0.3s ease;
+		transition: border-color 0.3s ease, box-shadow 0.3s ease;
 	}
 
 	:root[data-theme="dark"] .bucket-component {
@@ -680,8 +571,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 
 	.component-name {
 		font-size: 0.625rem;
-		font-family:
-			ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
+		font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
 		font-weight: 500;
 		color: rgb(23 23 23);
 		text-align: center;
@@ -764,6 +654,8 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		color: rgb(249 115 22);
 	}
 
+
+
 	/* Note text under component name */
 	.component-note {
 		font-size: 0.5rem;
@@ -991,50 +883,42 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 		private playTimeout: number | null = null;
 
 		connectedCallback() {
-			this.loop = this.dataset.loop === "true";
-
-			const toggleInput = this.querySelector(
-				".toggle-input",
-			) as HTMLInputElement;
+			this.loop = this.dataset.loop === 'true';
+			
+			const toggleInput = this.querySelector('.toggle-input') as HTMLInputElement;
 			if (toggleInput) {
-				toggleInput.addEventListener("change", () => {
+				toggleInput.addEventListener('change', () => {
 					this.localUploadsEnabled = toggleInput.checked;
-					this.setMode(toggleInput.checked ? "with" : "without");
+					this.setMode(toggleInput.checked ? 'with' : 'without');
 					this.resetAnimation();
-					if (this.dataset.autoplay === "true") {
-						this.playTimeout = setTimeout(
-							() => this.play(),
-							500,
-						) as unknown as number;
+					if (this.dataset.autoplay === 'true') {
+						this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
 					}
 				});
 			}
 
-			if (this.dataset.autoplay === "true") {
-				this.playTimeout = setTimeout(
-					() => this.play(),
-					500,
-				) as unknown as number;
+			if (this.dataset.autoplay === 'true') {
+				this.playTimeout = setTimeout(() => this.play(), 500) as unknown as number;
 			}
 		}
 
-		private setMode(mode: "without" | "with") {
-			const withoutElements = this.querySelectorAll(".without-local-uploads");
-			const withElements = this.querySelectorAll(".with-local-uploads");
+		private setMode(mode: 'without' | 'with') {
+			const withoutElements = this.querySelectorAll('.without-local-uploads');
+			const withElements = this.querySelectorAll('.with-local-uploads');
 
-			if (mode === "without") {
-				withoutElements.forEach((el) => el.classList.remove("hidden"));
-				withElements.forEach((el) => el.classList.add("hidden"));
+			if (mode === 'without') {
+				withoutElements.forEach(el => el.classList.remove('hidden'));
+				withElements.forEach(el => el.classList.add('hidden'));
 			} else {
-				withoutElements.forEach((el) => el.classList.add("hidden"));
-				withElements.forEach((el) => el.classList.remove("hidden"));
+				withoutElements.forEach(el => el.classList.add('hidden'));
+				withElements.forEach(el => el.classList.remove('hidden'));
 			}
 		}
 
 		private resetAnimation() {
 			this.currentStep = 0;
 			this.isPlaying = false;
-
+			
 			// Clear any pending timeouts
 			if (this.stepTimeout !== null) {
 				clearTimeout(this.stepTimeout);
@@ -1044,20 +928,12 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				clearTimeout(this.playTimeout);
 				this.playTimeout = null;
 			}
-
+			
 			// Remove all active and animating states
-			this.querySelectorAll(".active").forEach((el) =>
-				el.classList.remove("active"),
-			);
-			this.querySelectorAll(".animating").forEach((el) =>
-				el.classList.remove("animating"),
-			);
-			this.querySelectorAll(".data-animating").forEach((el) =>
-				el.classList.remove("data-animating"),
-			);
-			this.querySelectorAll(".metadata-active").forEach((el) =>
-				el.classList.remove("metadata-active"),
-			);
+			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
+			this.querySelectorAll('.animating').forEach(el => el.classList.remove('animating'));
+			this.querySelectorAll('.data-animating').forEach(el => el.classList.remove('data-animating'));
+			this.querySelectorAll('.metadata-active').forEach(el => el.classList.remove('metadata-active'));
 		}
 
 		private play() {
@@ -1077,10 +953,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 				if (this.loop) {
 					// Reset and restart
 					this.resetAnimation();
-					this.playTimeout = setTimeout(
-						() => this.play(),
-						1000,
-					) as unknown as number;
+					this.playTimeout = setTimeout(() => this.play(), 1000) as unknown as number;
 				} else {
 					this.isPlaying = false;
 				}
@@ -1088,7 +961,7 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			}
 
 			this.updateDiagram();
-
+			
 			// Duration for each step
 			let duration = 1200;
 			if (!this.localUploadsEnabled && this.currentStep === 4) {
@@ -1100,17 +973,12 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			} else if (this.localUploadsEnabled && this.currentStep === 9) {
 				duration = 2500; // Linger on final step with status indicator
 			}
-			this.stepTimeout = setTimeout(
-				() => this.advanceStep(),
-				duration,
-			) as unknown as number;
+			this.stepTimeout = setTimeout(() => this.advanceStep(), duration) as unknown as number;
 		}
 
 		private updateDiagram() {
 			// Remove all active states first
-			this.querySelectorAll(".active").forEach((el) =>
-				el.classList.remove("active"),
-			);
+			this.querySelectorAll('.active').forEach(el => el.classList.remove('active'));
 
 			if (this.localUploadsEnabled) {
 				this.updateWithLocalUploads();
@@ -1123,53 +991,49 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client node lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add("active");
+				clientNode?.classList.add('active');
 			}
 
 			// Step 2: Connector from client to EDGE lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add("active");
+				connector1?.classList.add('active');
 			}
 
 			// Step 3: EDGE box border + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector(".region-box.without-local-uploads");
-				const gatewayNode = this.querySelector(".gateway-node-without");
-				edgeBox?.classList.add("active");
-				gatewayNode?.classList.add("active");
+				const edgeBox = this.querySelector('.region-box.without-local-uploads');
+				const gatewayNode = this.querySelector('.gateway-node-without');
+				edgeBox?.classList.add('active');
+				gatewayNode?.classList.add('active');
 			}
 
 			// Step 4: Object data line starts animating
 			if (this.currentStep >= 4) {
-				const splitArea = this.querySelector(".split-area");
-				splitArea?.classList.add("data-animating");
+				const splitArea = this.querySelector('.split-area');
+				splitArea?.classList.add('data-animating');
 			}
 
 			// Step 5: Object Data Infra lights up
 			if (this.currentStep >= 5) {
-				const objectDataComponent = this.querySelector(
-					'[data-component="object-data"]',
-				);
-				objectDataComponent?.classList.add("active");
+				const objectDataComponent = this.querySelector('[data-component="object-data"]');
+				objectDataComponent?.classList.add('active');
 			}
 
 			// Step 6: Object metadata line lights up
 			if (this.currentStep >= 6) {
-				const splitArea = this.querySelector(".split-area");
-				splitArea?.classList.add("metadata-active");
+				const splitArea = this.querySelector('.split-area');
+				splitArea?.classList.add('metadata-active');
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector(".bucket-group");
-				const metadataComponent = this.querySelector(
-					'[data-component="metadata"]',
-				);
-				const statusIndicator = this.querySelector(".status-indicator");
-				bucketGroup?.classList.add("active");
-				metadataComponent?.classList.add("active");
-				statusIndicator?.classList.add("active");
+				const bucketGroup = this.querySelector('.bucket-group');
+				const metadataComponent = this.querySelector('[data-component="metadata"]');
+				const statusIndicator = this.querySelector('.status-indicator');
+				bucketGroup?.classList.add('active');
+				metadataComponent?.classList.add('active');
+				statusIndicator?.classList.add('active');
 			}
 		}
 
@@ -1177,83 +1041,75 @@ const { mode = "comparison", autoPlay = true, loop = true } = Astro.props;
 			// Step 1: Client lights up
 			if (this.currentStep >= 1) {
 				const clientNode = this.querySelector('[data-step="1"].flow-node');
-				clientNode?.classList.add("active");
+				clientNode?.classList.add('active');
 			}
 
 			// Step 2: Connector (client -> edge) lights up
 			if (this.currentStep >= 2) {
 				const connector1 = this.querySelector('[data-connector="1-2"]');
-				connector1?.classList.add("active");
+				connector1?.classList.add('active');
 			}
 
 			// Step 3: EDGE box + R2 Gateway Worker lights up
 			if (this.currentStep >= 3) {
-				const edgeBox = this.querySelector(".region-box.with-local-uploads");
-				const gatewayNode = this.querySelector(".gateway-node-local");
-				edgeBox?.classList.add("active");
-				gatewayNode?.classList.add("active");
+				const edgeBox = this.querySelector('.region-box.with-local-uploads');
+				const gatewayNode = this.querySelector('.gateway-node-local');
+				edgeBox?.classList.add('active');
+				gatewayNode?.classList.add('active');
 			}
 
 			// Step 4: Line from Gateway to Object Data Infra (edge)
 			if (this.currentStep >= 4) {
-				const regionLine = this.querySelector(".region-line");
-				regionLine?.classList.add("active");
+				const regionLine = this.querySelector('.region-line');
+				regionLine?.classList.add('active');
 			}
 
 			// Step 5: Object Data Infra (edge) lights up
 			if (this.currentStep >= 5) {
-				const localStorageNode = this.querySelector(".local-storage-node");
-				localStorageNode?.classList.add("active");
+				const localStorageNode = this.querySelector('.local-storage-node');
+				localStorageNode?.classList.add('active');
 			}
 
 			// Step 6: Line from Gateway to Metadata Service
 			if (this.currentStep >= 6) {
-				const metadataLines = this.querySelectorAll(
-					".left-col .v-connector.meta-line",
-				);
-				metadataLines.forEach((el) => el.classList.add("active"));
+				const metadataLines = this.querySelectorAll('.left-col .v-connector.meta-line');
+				metadataLines.forEach(el => el.classList.add('active'));
 			}
 
 			// Step 7: Metadata Service + YOUR BUCKET border + status indicator lights up
 			if (this.currentStep >= 7) {
-				const bucketGroup = this.querySelector(".bucket-group");
-				const metadataComponent = this.querySelector(
-					'[data-component="metadata"]',
-				);
-				const statusIndicator = this.querySelector(".status-indicator");
-				bucketGroup?.classList.add("active");
-				metadataComponent?.classList.add("active");
-				statusIndicator?.classList.add("active");
+				const bucketGroup = this.querySelector('.bucket-group');
+				const metadataComponent = this.querySelector('[data-component="metadata"]');
+				const statusIndicator = this.querySelector('.status-indicator');
+				bucketGroup?.classList.add('active');
+				metadataComponent?.classList.add('active');
+				statusIndicator?.classList.add('active');
 			}
 
 			// Step 8: Purple replication line animates downward + progress ring fills
 			if (this.currentStep >= 8) {
-				const replicationLines = this.querySelectorAll(
-					".right-col .v-connector.replication-line",
-				);
-				const progressRing = this.querySelector(".progress-ring");
+				const replicationLines = this.querySelectorAll('.right-col .v-connector.replication-line');
+				const progressRing = this.querySelector('.progress-ring');
 				// Force animation restart by removing class, triggering reflow, then adding class
-				replicationLines.forEach((el) => {
-					el.classList.remove("animating");
+				replicationLines.forEach(el => {
+					el.classList.remove('animating');
 					void (el as HTMLElement).offsetWidth; // Trigger reflow
-					el.classList.add("animating");
+					el.classList.add('animating');
 				});
 				if (progressRing) {
-					progressRing.classList.remove("animating");
+					progressRing.classList.remove('animating');
 					void (progressRing as HTMLElement).offsetWidth; // Trigger reflow
-					progressRing.classList.add("animating");
+					progressRing.classList.add('animating');
 				}
 			}
 
 			// Step 9: Object Data Infra (bucket) lights up
 			if (this.currentStep >= 9) {
-				const objectDataComponent = this.querySelector(
-					'[data-component="object-data"]',
-				);
-				objectDataComponent?.classList.add("active");
+				const objectDataComponent = this.querySelector('[data-component="object-data"]');
+				objectDataComponent?.classList.add('active');
 			}
 		}
 	}
 
-	customElements.define("r2-local-uploads-diagram", R2LocalUploadsDiagram);
+	customElements.define('r2-local-uploads-diagram', R2LocalUploadsDiagram);
 </script>
diff --git a/src/components/WranglerCommand.astro b/src/components/WranglerCommand.astro
index 9effdfbbbc05806..560f0f0a3b9fc1d 100644
--- a/src/components/WranglerCommand.astro
+++ b/src/components/WranglerCommand.astro
@@ -29,7 +29,7 @@ const experimental = definition.metadata.status === "experimental";
 // CED-191 some commands are present but marked as "hidden" and shouldn't be shown
 if (definition.metadata.hidden) {
 	throw new Error(
-		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`,
+		`[WranglerCommand] "${command}" is marked as hidden. If you want to publish, fix upstream in workers-sdk repo.`
 	);
 }
 
diff --git a/src/components/WranglerConfig.astro b/src/components/WranglerConfig.astro
index 6635f78fddc1700..cf7cdd0bca5b008 100644
--- a/src/components/WranglerConfig.astro
+++ b/src/components/WranglerConfig.astro
@@ -19,7 +19,7 @@ const copy = html.querySelector("div.copy > button");
 
 if (!copy) {
 	throw new Error(
-		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`,
+		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`
 	);
 }
 
@@ -27,7 +27,7 @@ let code = copy.attributes["data-code"];
 
 if (!code) {
 	throw new Error(
-		`[WranglerConfig] Unable to find data-code attribute on copy button.`,
+		`[WranglerConfig] Unable to find data-code attribute on copy button.`
 	);
 }
 
diff --git a/src/components/WranglerNamespace.astro b/src/components/WranglerNamespace.astro
index 52fc4b766b79934..26f4136c098904f 100644
--- a/src/components/WranglerNamespace.astro
+++ b/src/components/WranglerNamespace.astro
@@ -41,7 +41,7 @@ flattenSubtree(node.subtree);
 	definitions.map((definition) => {
 		if (definition.type !== "command") {
 			throw new Error(
-				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`,
+				`[WranglerNamespace] Expected "command" but got "${definition.type}" for "${definition.command}"`
 			);
 		}
 		return (
diff --git a/src/components/agent-setup/AgentComparison.astro b/src/components/agent-setup/AgentComparison.astro
index 58cd4d4ce361218..5d6382aa20f657f 100644
--- a/src/components/agent-setup/AgentComparison.astro
+++ b/src/components/agent-setup/AgentComparison.astro
@@ -122,9 +122,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.pricing_model ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.pricing_model.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.pricing_model] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.pricing_model] ?? ""}
 									>
 										{capabilityLabels[
 											agent.pricing_model as keyof typeof capabilityLabels
@@ -138,9 +136,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.model_flexibility ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.model_flexibility.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.model_flexibility] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.model_flexibility] ?? ""}
 									>
 										{capabilityLabels[
 											agent.model_flexibility as keyof typeof capabilityLabels
@@ -154,9 +150,7 @@ const dashIcon = `<svg width="16" height="16" viewBox="0 0 16 16" fill="none" cl
 								{agent.context_approach ? (
 									<span
 										class={`agent-setup-badge agent-token-badge agent-token-badge--${agent.context_approach.replace("_", "-")}`}
-										data-agent-tooltip={
-											capabilityTooltips[agent.context_approach] ?? ""
-										}
+										data-agent-tooltip={capabilityTooltips[agent.context_approach] ?? ""}
 									>
 										{capabilityLabels[
 											agent.context_approach as keyof typeof capabilityLabels
diff --git a/src/components/agent-setup/AgentHeader.astro b/src/components/agent-setup/AgentHeader.astro
index 71bf483f8e9d0e3..65d087ccb59bd27 100644
--- a/src/components/agent-setup/AgentHeader.astro
+++ b/src/components/agent-setup/AgentHeader.astro
@@ -20,7 +20,9 @@ const { slug } = Astro.props;
 const agent = AGENTS.find((a) => a.slug === slug);
 
 if (!agent) {
-	throw new Error(`[AgentHeader] No agent found for slug="${slug}"`);
+	throw new Error(
+		`[AgentHeader] No agent found for slug="${slug}"`,
+	);
 }
 
 const externalLinks = [
diff --git a/src/components/agent-setup/AgentPrimer.astro b/src/components/agent-setup/AgentPrimer.astro
index ebcdc78adfe7adf..35186f18fb15f25 100644
--- a/src/components/agent-setup/AgentPrimer.astro
+++ b/src/components/agent-setup/AgentPrimer.astro
@@ -179,10 +179,8 @@
 				</div>
 				<p>
 					Which foundation models you can use. <strong>Locked</strong>
-					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your
-					Own Key) lets you bring your own API key. <strong
-						>Multi-provider</strong
-					>
+					supports only the vendor's own models. <strong>BYOK</strong> (Bring Your Own Key) lets you bring
+					your own API key. <strong>Multi-provider</strong>
 					supports several providers out of the box.
 				</p>
 			</div>
diff --git a/src/components/agent-setup/BuildAgentsCallout.astro b/src/components/agent-setup/BuildAgentsCallout.astro
index 6b69a6fa5d1d523..94869f042602215 100644
--- a/src/components/agent-setup/BuildAgentsCallout.astro
+++ b/src/components/agent-setup/BuildAgentsCallout.astro
@@ -8,8 +8,8 @@
 	<div class="agent-build-callout-header">
 		<span class="agent-build-callout-eyebrow">Also worth knowing</span>
 		<p class="agent-build-callout-lede">
-			Cloudflare is not just a deploy target for agents, it is a full stack for
-			building your own.
+			Cloudflare is not just a deploy target for agents, it is a full
+			stack for building your own.
 		</p>
 	</div>
 
diff --git a/src/components/agent-setup/CloudflareToolsBanner.astro b/src/components/agent-setup/CloudflareToolsBanner.astro
index 0545d11317e00e4..5ed10cc064b9b55 100644
--- a/src/components/agent-setup/CloudflareToolsBanner.astro
+++ b/src/components/agent-setup/CloudflareToolsBanner.astro
@@ -5,48 +5,27 @@
 
 <div class="cf-banner not-content">
 	<div class="cf-banner-items">
+
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">Skills</p>
-			<p class="cf-banner-item-desc">
-				Reusable prompt packages that teach agents about Cloudflare products and
-				APIs.
-			</p>
+			<p class="cf-banner-item-desc">Reusable prompt packages that teach agents about Cloudflare products and APIs.</p>
 			<div class="cf-banner-item-links">
-				<a
-					href="https://github.com/cloudflare/skills"
-					target="_blank"
-					rel="noopener noreferrer">cloudflare/skills &nearr;</a
-				>
+				<a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">cloudflare/skills &nearr;</a>
 			</div>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">MCP</p>
-			<p class="cf-banner-item-desc">
-				Connect agents to your Cloudflare account. Two flavors: <a
-					href="https://github.com/cloudflare/mcp"
-					target="_blank"
-					rel="noopener noreferrer">Code Mode &nearr;</a
-				> for broad API coverage across all products, or <a
-					href="https://github.com/cloudflare/mcp-server-cloudflare"
-					target="_blank"
-					rel="noopener noreferrer">domain-specific servers &nearr;</a
-				> for purpose-built tools within one product area.
-			</p>
+			<p class="cf-banner-item-desc">Connect agents to your Cloudflare account. Two flavors: <a href="https://github.com/cloudflare/mcp" target="_blank" rel="noopener noreferrer">Code Mode &nearr;</a> for broad API coverage across all products, or <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific servers &nearr;</a> for purpose-built tools within one product area.</p>
 		</div>
 
 		<div class="cf-banner-item">
 			<p class="cf-banner-item-title">CLI</p>
 			<p class="cf-banner-item-desc">
-				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers,
-				KV, D1, R2, and more.
-				<a
-					href="https://blog.cloudflare.com/cf-cli-local-explorer/"
-					target="_blank"
-					rel="noopener noreferrer">cf CLI &nearr;</a
-				> is a next-generation CLI covering every Cloudflare product — in technical
-				preview.
+				<a href="/workers/wrangler/">Wrangler</a> for deploying and managing Workers, KV, D1, R2, and more.
+				<a href="https://blog.cloudflare.com/cf-cli-local-explorer/" target="_blank" rel="noopener noreferrer">cf CLI &nearr;</a> is a next-generation CLI covering every Cloudflare product — in technical preview.
 			</p>
 		</div>
+
 	</div>
 </div>
diff --git a/src/components/agent-setup/PlatformAccessSection.astro b/src/components/agent-setup/PlatformAccessSection.astro
index a913296e1aae07b..ca1c8625b1bbfae 100644
--- a/src/components/agent-setup/PlatformAccessSection.astro
+++ b/src/components/agent-setup/PlatformAccessSection.astro
@@ -32,10 +32,9 @@ import SkillsList from "./SkillsList.astro";
 		</p>
 		<p>
 			MCP servers provide typed tools to call into Cloudflare at runtime. There
-			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/"
-				>Code Mode</a
-			> — a single server that covers the entire Cloudflare API (2,500+ endpoints
-			in ~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
+			are two options: <a href="https://blog.cloudflare.com/code-mode-mcp/">Code Mode</a> —
+			a single server that covers the entire Cloudflare API (2,500+ endpoints in
+			~1,000 tokens) — or a set of focused, domain-specific servers hosted in the{
 				" "
 			}
 			<a
diff --git a/src/components/ai-gateway/code-examples.astro b/src/components/ai-gateway/code-examples.astro
index 91687d405b07449..5d48bb635cfa819 100644
--- a/src/components/ai-gateway/code-examples.astro
+++ b/src/components/ai-gateway/code-examples.astro
@@ -1,245 +1,112 @@
 ---
-import {
-	CodeExample,
-	CodeSelector,
-	modelOptions,
-	code,
-	aiSDKUnifiedCode,
-	aiSDKNativeCode,
-	curlCode,
-} from "./code-example-selector";
+import { CodeExample, CodeSelector, modelOptions, code, aiSDKUnifiedCode, aiSDKNativeCode, curlCode } from "./code-example-selector";
 import { Code } from "~/components";
 import { z } from "astro/zod";
 
+
 const props = z.object({
 	forceClient: z.string().optional(),
-	forceAPI: z.string().optional(),
+    forceAPI: z.string().optional(),
 });
 
 const { forceClient, forceAPI } = props.parse(Astro.props);
 ---
-
 <style>
-	.aig-code-example-container {
-		background-color: var(--color-gray-200);
-		border-color: var(--color-neutral-300);
-		border-radius: 0.675rem;
-		border-bottom-left-radius: 0.85rem;
-		border-bottom-right-radius: 0.85rem;
-		--selector-bg-color: var(--color-white);
-		--selector-border-color: var(--color-neutral-300);
-		--selector-text-color: var(--color-gray-900);
-		--ec-brdRad: 0.675rem;
-		--ec-brdCol: var(--color-neutral-300);
-		&:where([data-theme="dark"], [data-theme="dark"] *) {
-			background-color: var(--color-neutral-900);
-			border-color: var(--color-neutral-700);
-			--selector-bg-color: var(--color-neutral-700);
-			--selector-border-color: var(--color-neutral-800);
-			--selector-text-color: var(--color-gray-100);
-			--ec-brdCol: var(--color-neutral-700);
-		}
-	}
+    .aig-code-example-container {
+        background-color: var(--color-gray-200);
+        border-color: var(--color-neutral-300);
+        border-radius: 0.675rem;
+        border-bottom-left-radius: 0.85rem;
+        border-bottom-right-radius: 0.85rem;
+        --selector-bg-color: var(--color-white);
+        --selector-border-color: var(--color-neutral-300);
+        --selector-text-color: var(--color-gray-900);
+        --ec-brdRad: 0.675rem;
+        --ec-brdCol: var(--color-neutral-300);
+        &:where([data-theme=dark], [data-theme=dark] *) {
+            background-color: var(--color-neutral-900);
+            border-color: var(--color-neutral-700);
+            --selector-bg-color: var(--color-neutral-700);
+            --selector-border-color: var(--color-neutral-800);
+            --selector-text-color: var(--color-gray-100);
+            --ec-brdCol: var(--color-neutral-700);
+        }
+    }
 </style>
-<div class="aig-code-example-container border">
-	<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
-	{
-		(!forceClient || forceClient === "openai-js") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="openai-js"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={code
-							.replace("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("    {headerauth}\n", "")}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "openai-js") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="openai-js"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={code
-							.replace("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("{cf_api_token}", "{" + option.provider + "_api_token}")
-							.replace(
-								"    {headerauth}\n",
-								'  defaultHeaders: {\n      // if gateway is authenticated\n      "cf-aig-authorization": `Bearer {cf_api_token}`, \n  },\n',
-							)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKUnifiedCode
-							.replaceAll("{provider}", option.provider)
-							.replaceAll("{apikey}", "")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKUnifiedCode
-							.replaceAll("{provider}", option.provider)
-							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
+<div class="border aig-code-example-container">
+<CodeSelector client:load forceClient={forceClient} forceApiType={forceAPI} />
+{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript" title="" code={code
+        .replace("{provider}", option.provider)
+        .replace("{model}", option.model)
+        .replace("    {headerauth}\n","")}
+         />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "openai-js") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="openai-js" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript" title="" code={code
+        .replace("{provider}", option.provider)
+        .replace("{model}", option.model)
+        .replace("{cf_api_token}", "{" + option.provider + "_api_token}")
+        .replace("    {headerauth}\n","  defaultHeaders: {\n      // if gateway is authenticated\n      \"cf-aig-authorization\": `Bearer {cf_api_token}`, \n  },\n")}
+         />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
+            .replaceAll("{provider}", option.provider)
+            .replaceAll("{apikey}", "")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKUnifiedCode
+            .replaceAll("{provider}", option.provider)
+            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
 
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="stored"
-					apiType="native"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKNativeCode
-							.replaceAll("{provider}", option.aiSDK.provider)
-							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-							.replaceAll("{apikey}", "")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "aisdk") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="aisdk"
-					keyType="in-request"
-					apiType="native"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						lang="javascript"
-						title=""
-						code={aiSDKNativeCode
-							.replaceAll("{provider}", option.aiSDK.provider)
-							.replaceAll("{providerFactory}", option.aiSDK.providerFactory)
-							.replaceAll("{providerUsage}", option.aiSDK.providerUsage)
-							.replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
-							.replace("{model}", option.model)}
-					/>
-				</CodeExample>
-			))
-	}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="stored" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKNativeCode
+            .replaceAll("{provider}", option.aiSDK.provider)
+            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+            .replaceAll("{apikey}", "")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "aisdk") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="aisdk" keyType="in-request" apiType="native" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code lang="javascript"  title="" code={aiSDKNativeCode
+            .replaceAll("{provider}", option.aiSDK.provider)
+            .replaceAll("{providerFactory}", option.aiSDK.providerFactory)
+            .replaceAll("{providerUsage}", option.aiSDK.providerUsage)
+            .replaceAll("{apikey}", "{ apiKey: '{API_KEY}' }")
+            .replace("{model}", option.model)} />
+    </CodeExample>
+))}
 
-	{
-		(!forceClient || forceClient === "curl") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="curl"
-					keyType="stored"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						title=""
-						lang="curl"
-						code={curlCode
-							.replaceAll("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace("{headerauth}\n", "")}
-					/>
-				</CodeExample>
-			))
-	}
-	{
-		(!forceClient || forceClient === "curl") &&
-			modelOptions.map((option) => (
-				<CodeExample
-					client:load
-					provider={option.provider}
-					clientType="curl"
-					keyType="in-request"
-					apiType="unified"
-					forceClientType={forceClient}
-					forceApiType={forceAPI}
-				>
-					<Code
-						title=""
-						lang="curl"
-						code={curlCode
-							.replaceAll("{provider}", option.provider)
-							.replace("{model}", option.model)
-							.replace(
-								"{headerauth}\n",
-								"  --header 'Authorization: Bearer {" +
-									option.provider +
-									"_api_token}' \\\n",
-							)}
-					/>
-				</CodeExample>
-			))
-	}
-</div>
+{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="curl" keyType="stored" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code title="" lang="curl" code={curlCode
+            .replaceAll("{provider}", option.provider)
+            .replace("{model}", option.model)
+            .replace("{headerauth}\n","")}
+             />
+    </CodeExample>
+))}
+{(!forceClient || forceClient === "curl") && modelOptions.map((option) => (
+    <CodeExample client:load provider={option.provider} clientType="curl" keyType="in-request" apiType="unified" forceClientType={forceClient} forceApiType={forceAPI}>
+        <Code title="" lang="curl" code={curlCode
+            .replaceAll("{provider}", option.provider)
+            .replace("{model}", option.model)
+            .replace("{headerauth}\n","  --header 'Authorization: Bearer {" + option.provider + "_api_token}' \\\n")} />
+    </CodeExample>
+))}
+</div>
\ No newline at end of file
diff --git a/src/components/changelog/Pagination.astro b/src/components/changelog/Pagination.astro
index 633f1407b109d74..33e8d73fe0001bd 100644
--- a/src/components/changelog/Pagination.astro
+++ b/src/components/changelog/Pagination.astro
@@ -52,10 +52,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 
 {
 	lastPage > 1 && (
-		<nav
-			class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2"
-			aria-label="Pagination"
-		>
+		<nav class="pagination mt-8 flex flex-wrap items-center justify-between gap-y-2" aria-label="Pagination">
 			{prevUrl ? (
 				<a href={prevUrl} class="pagination-btn no-underline">
 					← Prev
@@ -67,7 +64,7 @@ const nextUrl = currentPage < lastPage ? pageUrl(currentPage + 1) : null;
 			<div class="pagination-pages flex items-center gap-1">
 				{items.map((item) =>
 					item === null ? (
-						<span class="text-sl-color-gray-3 flex h-9 items-center justify-center px-2 text-sm">
+						<span class="flex h-9 items-center justify-center px-2 text-sm text-sl-color-gray-3">
 							…
 						</span>
 					) : item === currentPage ? (
diff --git a/src/components/models/CopyableCode.astro b/src/components/models/CopyableCode.astro
index 0b17ed3299291d7..cf13027f562709e 100644
--- a/src/components/models/CopyableCode.astro
+++ b/src/components/models/CopyableCode.astro
@@ -8,7 +8,12 @@ const { text, label = "Copy" } = Astro.props;
 ---
 
 <copyable-code data-text={text}>
-	<button type="button" title={label} aria-label={label} class="copy-button">
+	<button
+		type="button"
+		title={label}
+		aria-label={label}
+		class="copy-button"
+	>
 		<code>{text}</code>
 		<svg
 			xmlns="http://www.w3.org/2000/svg"
@@ -38,9 +43,7 @@ const { text, label = "Copy" } = Astro.props;
 		border: 1px solid var(--sl-color-gray-5);
 		background: transparent;
 		cursor: pointer;
-		transition:
-			border-color 0.15s,
-			background-color 0.15s;
+		transition: border-color 0.15s, background-color 0.15s;
 	}
 
 	.copy-button:hover {
diff --git a/src/components/models/ModelDetailPage.astro b/src/components/models/ModelDetailPage.astro
index 1019e2aa09c5ec0..f24f3a3540c7658 100644
--- a/src/components/models/ModelDetailPage.astro
+++ b/src/components/models/ModelDetailPage.astro
@@ -188,9 +188,7 @@ const starlightPageProps = {
 			? { depth: 2, slug: "Examples", text: "Examples" }
 			: false,
 		hasSchema ? { depth: 2, slug: "Parameters", text: "Parameters" } : false,
-		hasSchema
-			? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" }
-			: false,
+		hasSchema ? { depth: 2, slug: "API-Schemas", text: "API Schemas (Raw)" } : false,
 	].filter((v) => Boolean(v)) as MarkdownHeading[],
 	hideTitle: true,
 } as StarlightPageProps;
@@ -426,114 +424,22 @@ const starlightPageProps = {
 					{model.apiModes.flatMap((mode) => [
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">
-									{mode.name}
-								</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
 								<span class="ml-2 text-gray-500 dark:text-gray-400">Input</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/${mode.id}-input.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-										<polyline points="15 3 21 3 21 9" />
-										<line x1="10" y1="14" x2="21" y2="3" />
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/${mode.id}-input.json`}
-									download={`${mode.id}-input.json`}
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-										<polyline points="7 10 12 15 17 10" />
-										<line x1="12" y1="15" x2="12" y2="3" />
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/${mode.id}-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/${mode.id}-input.json`} download={`${mode.id}-input.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>,
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
 							<span class="text-sm">
-								<span class="font-medium text-gray-900 dark:text-gray-100">
-									{mode.name}
-								</span>
-								<span class="ml-2 text-gray-500 dark:text-gray-400">
-									Output
-								</span>
+								<span class="font-medium text-gray-900 dark:text-gray-100">{mode.name}</span>
+								<span class="ml-2 text-gray-500 dark:text-gray-400">Output</span>
 							</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/${mode.id}-output.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-										<polyline points="15 3 21 3 21 9" />
-										<line x1="10" y1="14" x2="21" y2="3" />
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/${mode.id}-output.json`}
-									download={`${mode.id}-output.json`}
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-										<polyline points="7 10 12 15 17 10" />
-										<line x1="12" y1="15" x2="12" y2="3" />
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/${mode.id}-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/${mode.id}-output.json`} download={`${mode.id}-output.json`} title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>,
 					])}
@@ -577,115 +483,17 @@ const starlightPageProps = {
 					<h2 id="API-Schemas">API Schemas (Raw)</h2>
 					<div class="not-content grid grid-cols-1 gap-2 sm:grid-cols-2">
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
-								Input
-							</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Input</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/schema-input.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-											<polyline points="15 3 21 3 21 9" />
-											<line x1="10" y1="14" x2="21" y2="3" />
-										</>
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/schema-input.json`}
-									download="schema-input.json"
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-											<polyline points="7 10 12 15 17 10" />
-											<line x1="12" y1="15" x2="12" y2="3" />
-										</>
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/schema-input.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/schema-input.json`} download="schema-input.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>
 						<div class="flex items-center justify-between rounded-lg border border-gray-200 px-4 py-1.5 dark:border-gray-700">
-							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">
-								Output
-							</span>
+							<span class="text-sm font-medium text-gray-900 dark:text-gray-100">Output</span>
 							<span class="flex items-center gap-1">
-								<a
-									href={`${schemaBasePath}/schema-output.json`}
-									target="_blank"
-									rel="noopener noreferrer"
-									title="Open"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6" />
-											<polyline points="15 3 21 3 21 9" />
-											<line x1="10" y1="14" x2="21" y2="3" />
-										</>
-									</svg>
-								</a>
-								<a
-									href={`${schemaBasePath}/schema-output.json`}
-									download="schema-output.json"
-									title="Download"
-									class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"
-								>
-									<svg
-										xmlns="http://www.w3.org/2000/svg"
-										width="14"
-										height="14"
-										viewBox="0 0 24 24"
-										fill="none"
-										stroke="currentColor"
-										stroke-width="2"
-										stroke-linecap="round"
-										stroke-linejoin="round"
-									>
-										<>
-											<path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4" />
-											<polyline points="7 10 12 15 17 10" />
-											<line x1="12" y1="15" x2="12" y2="3" />
-										</>
-									</svg>
-								</a>
+								<a href={`${schemaBasePath}/schema-output.json`} target="_blank" rel="noopener noreferrer" title="Open" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"/><polyline points="15 3 21 3 21 9"/><line x1="10" y1="14" x2="21" y2="3"/></svg></a>
+								<a href={`${schemaBasePath}/schema-output.json`} download="schema-output.json" title="Download" class="flex h-7 w-7 items-center justify-center rounded text-gray-400 no-underline hover:bg-gray-100 hover:text-gray-600 dark:hover:bg-gray-800 dark:hover:text-gray-300"><svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 15v4a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2v-4"/><polyline points="7 10 12 15 17 10"/><line x1="12" y1="15" x2="12" y2="3"/></svg></a>
 							</span>
 						</div>
 					</div>
diff --git a/src/components/models/SchemaDisplay.astro b/src/components/models/SchemaDisplay.astro
index e87bb767e12aced..6dcb17aa8c69d0f 100644
--- a/src/components/models/SchemaDisplay.astro
+++ b/src/components/models/SchemaDisplay.astro
@@ -196,10 +196,11 @@ function collectRows(
 			(reg.annotations?.description as string | undefined) ??
 			nullableChildDescription;
 		// Check both validations and fragment for enum (different schema parsers put it in different places)
-		const enumValues = (
-			(reg.validations?.enum as unknown[]) ??
-			((reg.fragment as Record<string, unknown>)?.enum as unknown[])
-		)?.map(String);
+		const enumValues =
+			((reg.validations?.enum as unknown[]) ??
+				((reg.fragment as Record<string, unknown>)?.enum as unknown[]))?.map(
+				String,
+			);
 
 		// Collect all metadata from fragment and validations
 		const metadata: Record<string, string | number | boolean> = {};
@@ -428,12 +429,7 @@ const variantRows =
 				No parameters defined.
 			</p>
 		) : (
-			<SchemaTreeView
-				rows={rows}
-				schemaId={schemaId}
-				hideRequired={hideRequired}
-				client:visible
-			/>
+			<SchemaTreeView rows={rows} schemaId={schemaId} hideRequired={hideRequired} client:visible />
 		)
 	}
 </div>
diff --git a/src/components/models/code/DeepgramFlux.astro b/src/components/models/code/DeepgramFlux.astro
index 119317163ac8ede..c5c957d047b01e8 100644
--- a/src/components/models/code/DeepgramFlux.astro
+++ b/src/components/models/code/DeepgramFlux.astro
@@ -73,13 +73,11 @@ function generateRandomAudio() {
   return buffer;
 }
 `;
+
 ---
 
 <>
-	<Details
-		header="Step 1: Create a Worker that establishes a WebSocket connection"
-		open
-	>
+	<Details header="Step 1: Create a Worker that establishes a WebSocket connection" open>
 		<Code code={worker} lang="ts" />
 	</Details>
 
@@ -87,10 +85,7 @@ function generateRandomAudio() {
 		<Code code={deployWorker} lang="sh" />
 	</Details>
 
-	<Details
-		header="Step 3: Write a client script to connect to your Worker and send audio"
-		open
-	>
-		<Code code={clientScript} lang="js" />
-	</Details>
+  <Details header="Step 3: Write a client script to connect to your Worker and send audio" open>
+    <Code code={clientScript} lang="js" />
+  </Details>
 </>
diff --git a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
index ac2d801c62fdeb2..e1f4ce5d0ae4e09 100644
--- a/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
+++ b/src/components/models/code/OpenAIResponsesTextGenerationCode.astro
@@ -76,8 +76,8 @@ curl https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/v1/
 		</li>
 		<li>
 			<strong>Workers AI Run</strong> (<code>/ai/run</code>) - Dynamic format
-			detection, accepts Chat Completions (<code>messages</code>), legacy
-			Completions (<code>prompt</code>), or Responses API (<code>input</code>)
+			detection, accepts Chat Completions (<code>messages</code>), legacy Completions
+			(<code>prompt</code>), or Responses API (<code>input</code>)
 		</li>
 		<li>
 			<strong>Chat Completions</strong> (<code>/v1/chat/completions</code>) -
diff --git a/src/components/overrides/Page.astro b/src/components/overrides/Page.astro
index e0ba5423f7dfb20..193c0458f2d2a57 100644
--- a/src/components/overrides/Page.astro
+++ b/src/components/overrides/Page.astro
@@ -12,11 +12,9 @@ const html = await Astro.slots.render("default");
 // Agent-setup pages use `template: splash` (to avoid sidebar group lookup) but
 // still need a right-hand ToC. Splash pages have props.toc === undefined, so we
 // bootstrap the object here before calling generateTableOfContents.
-const isAgentSetup =
-	props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
+const isAgentSetup = props.id.startsWith("agent-setup/") && props.id !== "agent-setup/index";
 if (isAgentSetup) {
-	if (!props.toc)
-		props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
+	if (!props.toc) props.toc = { minHeadingLevel: 2, maxHeadingLevel: 3, items: [] };
 	props.hideBreadcrumbs = true;
 	props.hideTitle = true;
 }
diff --git a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
index d03cecd7bab8754..c7f5ea93bac1254 100644
--- a/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
+++ b/src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx
@@ -1,12 +1,12 @@
 ---
 title: Cloudflare Access Logging supports the Customer Metadata Boundary (CMB)
-description: Access logs will now respect the CMB.
+description: Access logs will now respect the CMB. 
 date: 2025-08-14
 products:
   - access
 ---
 
-Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration.
+Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration. 
 
 :::note
 For EU CMB customers, the logs will not be stored by Access and will appear as empty in the dashboard. EU CMB customers should utilize [Logpush](/logs/logpush/) to retain their Access logging, if desired.
diff --git a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
index cd95cf8fdd1edba..a82bbcbeee550b8 100644
--- a/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
+++ b/src/content/changelog/access/2025-08-26-mcp-server-portals.mdx
@@ -15,3 +15,4 @@ An [MCP server portal](/cloudflare-one/access-controls/ai-controls/mcp-portals/)
 - **Observability**: Once the user's AI agent is connected to the portal, Cloudflare Access logs the individual requests made using the tools in the portal.
 
 This is available in an open beta for all customers across all plans! For more information check out our [blog](https://blog.cloudflare.com/zero-trust-mcp-server-portals/) for this release.
+
diff --git a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
index 91a89f79924c5c2..675b9236a2b9f3d 100644
--- a/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
+++ b/src/content/changelog/access/2026-02-17-clientless-access-for-private-apps.mdx
@@ -12,4 +12,6 @@ A new **Allow clientless access** setting makes it easier to connect users witho
 
 Previously, to provide clientless access to a private hostname or IP without a [published application](/cloudflare-one/networks/routes/add-routes/#add-a-published-application-route), you had to create a separate [bookmark application](/cloudflare-one/access-controls/applications/bookmarks/) pointing to a prefixed [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) URL (for example, `https://<your-teamname>.cloudflareaccess.com/browser/https://10.0.0.1/`). This bookmark was visible to all users in the App Launcher, regardless of whether they had access to the underlying application.
 
-Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
+Now, you can manage clientless access directly within your [private self-hosted application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). When  **Allow clientless access** is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) to open the link.
+
+
diff --git a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
index 8524d2348de427d..e3dde55074d43c6 100644
--- a/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
+++ b/src/content/changelog/agents/2025-12-22-agents-sdk-ai-sdk-v6.mdx
@@ -33,13 +33,13 @@ const tools = {
 	getWeather: tool({
 		description: "Get weather for a city",
 		inputSchema: z.object({ city: z.string() }),
-		execute: async ({ city }) => fetchWeather(city),
+		execute: async ({ city }) => fetchWeather(city)
 	}),
 
 	// Client-executed tool (no execute = client handles via onToolCall)
 	getLocation: tool({
 		description: "Get user location from browser",
-		inputSchema: z.object({}),
+		inputSchema: z.object({})
 		// No execute function
 	}),
 
@@ -48,8 +48,8 @@ const tools = {
 		description: "Process a payment",
 		inputSchema: z.object({ amount: z.number() }),
 		needsApproval: async ({ amount }) => amount > 100,
-		execute: async ({ amount }) => charge(amount),
-	}),
+		execute: async ({ amount }) => charge(amount)
+	})
 };
 ```
 
@@ -70,11 +70,11 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 				toolCallId: toolCall.toolCallId,
 				output: {
 					lat: position.coords.latitude,
-					lng: position.coords.longitude,
-				},
+					lng: position.coords.longitude
+				}
 			});
 		}
-	},
+	}
 });
 ```
 
@@ -97,9 +97,9 @@ const { messages, sendMessage, addToolOutput } = useAgentChat({
 		// Handle client-side tool execution
 		await addToolOutput({
 			toolCallId: toolCall.toolCallId,
-			output: { result: "success" },
+			output: { result: "success" }
 		});
-	},
+	}
 });
 ```
 
@@ -112,12 +112,12 @@ const paymentTool = tool({
 	description: "Process a payment",
 	inputSchema: z.object({
 		amount: z.number(),
-		recipient: z.string(),
+		recipient: z.string()
 	}),
 	needsApproval: async ({ amount }) => amount > 1000,
 	execute: async ({ amount, recipient }) => {
 		return await processPayment(amount, recipient);
-	},
+	}
 });
 ```
 
@@ -138,7 +138,7 @@ const pendingToolCallConfirmation = messages.some((m) =>
 if (pendingToolCallConfirmation) {
 	await addToolOutput({
 		toolCallId: part.toolCallId,
-		output: "User approved the action",
+		output: "User approved the action"
 	});
 }
 ```
@@ -158,7 +158,7 @@ import { convertToModelMessages } from "ai";
 
 const result = streamText({
 	messages: await convertToModelMessages(this.messages),
-	model: openai("gpt-4o"),
+	model: openai("gpt-4o")
 });
 ```
 
@@ -182,14 +182,14 @@ const result = await generateObject({
 	mode: "json",
 	model,
 	schema,
-	prompt,
+	prompt
 });
 
 // After (v6)
 const result = await generateObject({
 	model,
 	schema,
-	prompt,
+	prompt
 });
 ```
 
@@ -203,10 +203,10 @@ import { generateText, Output, stepCountIs } from "ai";
 const { output } = await generateText({
 	model: openai("gpt-4"),
 	output: Output.object({
-		schema: z.object({ name: z.string() }),
+		schema: z.object({ name: z.string() })
 	}),
 	stopWhen: stepCountIs(2),
-	prompt: "Generate a name",
+	prompt: "Generate a name"
 });
 ```
 
@@ -282,11 +282,11 @@ import { createAIGateway } from "ai-gateway-provider";
 const model = createAIGateway({
 	gatewayUrl: "https://gateway.ai.cloudflare.com/v1/your-account-id/gateway",
 	headers: {
-		Authorization: `Bearer ${env.AI_GATEWAY_TOKEN}`,
-	},
+		"Authorization": `Bearer ${env.AI_GATEWAY_TOKEN}`
+	}
 })({
 	provider: "openai",
-	model: "gpt-4o",
+	model: "gpt-4o"
 });
 ```
 
diff --git a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
index af9c6cd51586110..c47df65f32e38d4 100644
--- a/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
+++ b/src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx
@@ -10,25 +10,25 @@ We are excited to announce two major capability upgrades for **Agent Lee**, the
 
 ### Take action with Write Operations
 
-Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.
+Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. 
 
 To ensure security and accuracy, every write operation requires **explicit user approval**. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select **Confirm**, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.
 
 **Example requests:**
+* *"Add an A record for blog.example.com pointing to 192.0.2.10."*
+* *"Enable Always Use HTTPS on my zone."*
+* *"Set the SSL mode for example.com to Full (strict)."*
 
-- _"Add an A record for blog.example.com pointing to 192.0.2.10."_
-- _"Enable Always Use HTTPS on my zone."_
-- _"Set the SSL mode for example.com to Full (strict)."_
 
 ### Visualize data with Generative UI
 
 Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features **Generative UI**, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry.
 
 **Example requests:**
+* *"Show me a chart of my traffic over the last 7 days."*
+* *"What does my error rate look like for the past 24 hours?"*
+* *"Graph my cache hit rate for example.com this week."*
 
-- _"Show me a chart of my traffic over the last 7 days."_
-- _"What does my error rate look like for the past 24 hours?"_
-- _"Graph my cache hit rate for example.com this week."_
 
 ---
 
diff --git a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
index 6142d6dbab74b1a..70d67fd32103d74 100644
--- a/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
+++ b/src/content/changelog/ai-search/2025-09-19-autorag-metrics.mdx
@@ -16,4 +16,4 @@ You can find these metrics within each AutoRAG instance:
 - Search breakdown: Compare usage between `ai-search` and `search` endpoints.
 - Top file retrievals: Identify which files are most frequently retrieved in a given period.
 
-Try it today in [AutoRAG](/ai-search/get-started/).
+Try it today in [AutoRAG](/ai-search/get-started/).
\ No newline at end of file
diff --git a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
index 37bf0f628f7a6a7..1eff4229721c7bd 100644
--- a/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
+++ b/src/content/changelog/ai-search/2025-09-25-ai-search-more-models.mdx
@@ -13,9 +13,9 @@ With AI Search you can now use models from different providers like OpenAI and A
 To use AI Search with other [model providers](/ai-search/configuration/models/):
 
 1. **Add provider keys to AI Gateway**
-   1. Go to AI > AI Gateway in the dashboard.
-   2. Select or create an AI gateway.
-   3. In Provider Keys, choose your provider, click Add, and enter the key.
+    1. Go to AI > AI Gateway in the dashboard.
+    2. Select or create an AI gateway.
+    3. In Provider Keys, choose your provider, click Add, and enter the key.
 2. **Connect a gateway to AI Search**: When creating a new AI Search, select the AI Gateway with your provider keys. For an existing AI Search, go to Settings and switch to a gateway that has your keys under Resources.
 3. **Select models**: Embedding models are only available to be changed when creating a new AI Search. Generation model can be selected when creating a new AI Search and can be changed at any time in Settings.
 
@@ -23,18 +23,19 @@ Once configured, your AI Search instance will be able to reference models availa
 
 ```javascript
 export default {
-	async fetch(request, env) {
-		// Query your AI Search instance with a natural language question to an OpenAI model
-		const result = await env.AI.autorag("my-ai-search").aiSearch({
-			query: "What's new for Cloudflare Birthday Week?",
-			model: "openai/gpt-5",
-		});
-
-		// Return only the generated answer as plain text
-		return new Response(result.response, {
-			headers: { "Content-Type": "text/plain" },
-		});
-	},
+  async fetch(request, env) {
+    
+    // Query your AI Search instance with a natural language question to an OpenAI model
+    const result = await env.AI.autorag("my-ai-search").aiSearch({
+      query: "What's new for Cloudflare Birthday Week?",
+      model: "openai/gpt-5"
+    });
+
+    // Return only the generated answer as plain text
+    return new Response(result.response, {
+      headers: { "Content-Type": "text/plain" },
+    });
+  },
 };
 ```
 
diff --git a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
index 561919395ce174d..5a9abdb9296fae3 100644
--- a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
+++ b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx
@@ -10,8 +10,7 @@ date: 2025-11-19
 
 Previously, AI Search could only crawl publicly accessible pages, leaving knowledge bases, documentation, and other protected content out of your search results. With custom headers support, you can now include authentication credentials that allow the crawler to access this protected content.
 
-This is particularly useful for indexing content like:
-
+This is particularly useful for indexing content like: 
 - **Internal documentation** behind corporate login systems
 - **Premium content** that requires users to provide access to unlock
 - **Sites protected by Cloudflare Access** using service tokens
@@ -27,6 +26,6 @@ CF-Access-Client-Id: your-token-id.access
 CF-Access-Client-Secret: your-token-secret
 ```
 
-The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked.
+The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked. 
 
-Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
+Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
\ No newline at end of file
diff --git a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
index 105ae21f43fe4fd..a54b6cddfff6e9a 100644
--- a/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
+++ b/src/content/changelog/ai-search/2026-04-16-ai-search-namespace-binding.mdx
@@ -7,13 +7,13 @@ date: 2026-04-16T12:00:00Z
 publish_future_dated_entry: true
 ---
 
-New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away.
+New [AI Search](/ai-search/) instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away. 
 
 Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call.
 
 ## Built-in storage and vector index
 
-All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first.
+All new instances now comes with built-in storage which allows you to upload files directly to it using the [Items API](/ai-search/api/items/workers-binding/) or the dashboard. No R2 buckets to set up, no external data sources to connect first. 
 
 ```ts
 const instance = env.AI_SEARCH.get("my-instance");
diff --git a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
index 420f30e5265e339..e8c0c6621a0467f 100644
--- a/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
+++ b/src/content/changelog/analytics/2025-10-01-confidence-intervals.mdx
@@ -3,12 +3,12 @@ title: New Confidence Intervals in GraphQL Analytics API
 description: Confidence intervals are now supported in the GraphQL Analytics API to show statistical ranges for sampled data results
 date: 2025-10-01
 ---
-
-The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty.
+ 
+The GraphQL Analytics API now supports confidence intervals for `sum` and `count` fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty. 
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`).
+- **Usage**: The confidence `level` must be provided as a decimal between 0 and 1 (e.g. `0.90`, `0.95`, `0.99`). 
 - **Default**: If no confidence level is specified, no intervals are returned.
 
-For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/).
+For examples and more details, see the [GraphQL Analytics API documentation](/analytics/graphql-api/features/confidence-intervals/). 
diff --git a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
index 91c0a2dc9d56063..6194d159eaef0a2 100644
--- a/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
+++ b/src/content/changelog/analytics/2026-02-18-cfworker-server-timing.mdx
@@ -8,10 +8,10 @@ The Server-Timing header now includes a new `cfWorker` metric that measures time
 
 Previously, Worker execution time was included in the `edge` metric, making it harder to identify true edge performance. The new `cfWorker` metric provides this visibility:
 
-| Metric     | Description                                                                           |
-| ---------- | ------------------------------------------------------------------------------------- |
-| `edge`     | Total time spent on the Cloudflare edge, including Worker execution                   |
-| `origin`   | Time spent fetching from the origin server                                            |
+| Metric | Description |
+| --- | --- |
+| `edge` | Total time spent on the Cloudflare edge, including Worker execution |
+| `origin` | Time spent fetching from the origin server |
 | `cfWorker` | Time spent in Worker execution, including subrequests but excluding origin fetch time |
 
 ### Example response
diff --git a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
index 32a3c52bdfbfc7f..1b6ce51e1eb4bfd 100644
--- a/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
+++ b/src/content/changelog/api-shield/2026-03-09-vulnerability-scanner.mdx
@@ -10,8 +10,8 @@ Cloudflare is launching the [Open Beta of the **Web and API Vulnerability Scanne
 
 The initial release focuses on detecting Broken Object Level Authorization (BOLA) vulnerabilities by building API call graphs to simulate attacker and owner contexts, then testing these contexts by sending real HTTP requests to your APIs.
 
-The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release.
+The scanner is now available via the Cloudflare API. To scan, set up your target environment, owner and attacker credentials, and upload your OpenAPI file with response schemas. The scanner will be available in the Cloudflare dashboard in a future release. 
 
 **Access**: This feature is only available to API Shield subscribers via the Cloudflare API. We hope you will use the API for programmatic integration into your CI/CD pipelines and security dashboards.
 
-**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
+**Documentation**: Refer to the [developer documentation](/api-shield/security/vulnerability-scanner/) to start scanning your endpoints today.
\ No newline at end of file
diff --git a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
index 8f0e0c75c5a3682..968d7e9e61a7325 100644
--- a/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
+++ b/src/content/changelog/artifacts/2026-05-19-event-subscriptions.mdx
@@ -12,13 +12,13 @@ You can now receive [event notifications](/queues/event-subscriptions/) for [Art
 
 This allows you to:
 
-- Run custom workflows when a repository is created or imported
-- Kick off a build and deploy a change when an agent pushes to a repo
-- Trigger a review agent on every push
+* Run custom workflows when a repository is created or imported
+* Kick off a build and deploy a change when an agent pushes to a repo
+* Trigger a review agent on every push
 
 Available events include:
 
-- **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
-- **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
+* **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported`
+* **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched`
 
 To learn more, refer to [Artifacts documentation](/artifacts/guides/event-subscriptions/).
diff --git a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
index 18f7b35d1cbd348..d613bad87530e49 100644
--- a/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
+++ b/src/content/changelog/cache/2024-09-05-cache-rules-templates.mdx
@@ -27,3 +27,4 @@ You can now create optimized cache rules instantly with **one-click templates**,
 ## Get started
 
 To get started, go to [**Rules > Templates**](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) in the dashboard. For more information, refer to the [Cache Rules documentation](/cache/how-to/cache-rules/).
+
diff --git a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
index 803a3785a4f7930..13727aa33125d77 100644
--- a/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
+++ b/src/content/changelog/cache/2024-11-07-shard-cache-by-cache-key.mdx
@@ -26,14 +26,14 @@ When configuring [custom cache keys](/cache/how-to/cache-keys/), you can now inc
 
 ```json
 {
-	"cache_key": {
-		"custom_key": {
-			"header": {
-				"include": ["accept-language", "user-agent"],
-				"check_presence": ["referer"]
-			}
-		}
-	}
+  "cache_key": {
+    "custom_key": {
+      "header": {
+        "include": ["accept-language", "user-agent"],
+        "check_presence": ["referer"]
+      }
+    }
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
index a9d29c3c2cfc2b5..3f346c5807413c8 100644
--- a/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
+++ b/src/content/changelog/cache/2025-11-07-cache-keys-for-cloudflare-trace.mdx
@@ -20,19 +20,19 @@ The Trace response includes the cache key in the `cache` object:
 
 ```json
 {
-	"step_name": "request",
-	"type": "cache",
-	"matched": true,
-	"public_name": "Cache Parameters",
-	"cache": {
-		"key": {
-			"zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
-			"scheme": "https",
-			"host": "example.com",
-			"uri": "/images/hero.jpg"
-		},
-		"key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
-	}
+  "step_name": "request",
+  "type": "cache",
+  "matched": true,
+  "public_name": "Cache Parameters",
+  "cache": {
+    "key": {
+      "zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
+      "scheme": "https",
+      "host": "example.com",
+      "uri": "/images/hero.jpg"
+    },
+    "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
index 3f7c005146bb17a..814ebc40610e652 100644
--- a/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
+++ b/src/content/changelog/cache/2025-11-25-audit-logs-for-cache-purge-events.mdx
@@ -20,28 +20,28 @@ The detailed audit payload is visible within the Cloudflare Dashboard (under **M
 
 ```json
 {
-	"action": {
-		"result": "success",
-		"type": "create"
-	},
-	"actor": {
-		"id": "1234567890abcdef",
-		"email": "user@example.com",
-		"type": "user"
-	},
-	"resource": {
-		"product": "purge_cache",
-		"request": {
-			"files": [
-				"https://example.com/images/logo.png",
-				"https://example.com/css/styles.css"
-			]
-		}
-	},
-	"zone": {
-		"id": "023e105f4ecef8ad9ca31a8372d0c353",
-		"name": "example.com"
-	}
+  "action": {
+    "result": "success",
+    "type": "create"
+  },
+  "actor": {
+    "id": "1234567890abcdef",
+    "email": "user@example.com",
+    "type": "user"
+  },
+  "resource": {
+    "product": "purge_cache",
+    "request": {
+      "files": [
+        "https://example.com/images/logo.png",
+        "https://example.com/css/styles.css"
+      ]
+    }
+  },
+  "zone": {
+    "id": "023e105f4ecef8ad9ca31a8372d0c353",
+    "name": "example.com"
+  }
 }
 ```
 
diff --git a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
index 220ad070c02db00..f8b1270d926561c 100644
--- a/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
+++ b/src/content/changelog/cache/2026-03-24-cache-response-rules.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-24
 ---
 
-You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses _before_ they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
+You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses *before* they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach.
 
 ## What changed
 
diff --git a/src/content/changelog/casb/2025-10-28-casb-roles.mdx b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
index 45bf12202502ff5..0eba434bfd0c136 100644
--- a/src/content/changelog/casb/2025-10-28-casb-roles.mdx
+++ b/src/content/changelog/casb/2025-10-28-casb-roles.mdx
@@ -8,8 +8,8 @@ date: 2025-10-28
 
 Cloudflare CASB (Cloud Access Security Broker) now supports two new granular roles to provide more precise access control for your security teams:
 
-- **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
-- **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
+* **Cloudflare CASB Read:** Provides read-only access to view CASB findings and dashboards. This role is ideal for security analysts, compliance auditors, or team members who need visibility without modification rights.
+* **Cloudflare CASB:** Provides full administrative access to configure and manage all aspects of the CASB product.
 
 These new roles help you better enforce the principle of least privilege. You can now grant specific members access to CASB security findings without assigning them broader permissions, such as the **Super Administrator** or **Administrator** roles.
 
diff --git a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
index 8293deadac922ee..06fb9e1526fa249 100644
--- a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
+++ b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx
@@ -5,3 +5,4 @@ date: 2025-08-29
 ---
 
 We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client.
+
diff --git a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
index 40a2ecfb6928699..ae69ba66324f32d 100644
--- a/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
+++ b/src/content/changelog/cloudflare-one/2025-09-16-new-ai-enabled-search-for-zero-trust-dashboard.mdx
@@ -9,9 +9,9 @@ products:
 Zero Trust Dashboard has a brand new, AI-powered search functionality. You can search your account by resources (applications, policies, device profiles, settings, etc.), pages, products, and more.
 
 ![Example search results in the Zero Trust dashboard](~/assets/images/changelog/cloudflare-one/searchexample.png)
-
+  
 **Ask Cloudy** — You can also ask Cloudy, our AI agent, questions about Cloudflare Zero Trust. Cloudy is trained on our developer documentation and implementation guides, so it can tell you how to configure functionality, best practices, and can make recommendations.
 
 Cloudy can then stay open with you as you move between pages to build configuration or answer more questions.
 
-**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
+**Find Recents** — Recent searches and Cloudy questions also have a new tab under Zero Trust Overview.
\ No newline at end of file
diff --git a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
index b0f6e01371820c0..d4b4b3081b4aa3a 100644
--- a/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
+++ b/src/content/changelog/cloudflare-one/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources.mdx
@@ -8,10 +8,10 @@ products:
 
 You can now duplicate specific Cloudflare One resources with a single click from the dashboard.
 
-Initially supported resources:
 
-- Access Applications
-- Access Policies
-- Gateway Policies
+Initially supported resources:
+* Access Applications
+* Access Policies
+* Gateway Policies
 
-To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
+To try this out, simply click on the overflow menu (⋮) from the resource table and click <i>Duplicate</i>. We will continue to add the Duplicate action for resources throughout 2026.
\ No newline at end of file
diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
index 1cbf0a71d44db2b..3732caa81147c83 100644
--- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx
+++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx
@@ -7,7 +7,7 @@ product: Gateway
 
 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications.
 
-33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security.
+33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. 
 
 To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**.
 
diff --git a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
index 9be106dafc193cc..03fb76c0a537bc1 100644
--- a/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
+++ b/src/content/changelog/cloudflare-wan/2026-01-27-configure-cloudflare-source-ips.mdx
@@ -23,4 +23,4 @@ Key details:
 
 Configuring Cloudflare source IPs requires Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
 
-For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
+For configuration details, refer to [Configure Cloudflare source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/).
\ No newline at end of file
diff --git a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
index a42523b426c282c..32af30f28627705 100644
--- a/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
+++ b/src/content/changelog/containers/2025-10-01-new-container-instance-types.mdx
@@ -9,7 +9,7 @@ date: 2025-10-01
 New instance types provide up to 4 vCPU, 12 GiB of memory, and 20 GB of disk per container instance.
 
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------- | ----- |
+| ------------- | ---- | ------  | ----  |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
diff --git a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
index 1d4d4ea196130e1..3a6f1aa9ae491fc 100644
--- a/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
+++ b/src/content/changelog/containers/2025-11-21-new-cpu-pricing.mdx
@@ -15,15 +15,15 @@ This means that you now pay less for Containers and Sandboxes.
 Imagine running the `standard-2` instance type for one hour, which can use up to 1 vCPU,
 but on average you use only 20% of your CPU capacity.
 
-CPU-time is priced at _$0.00002 per vCPU-second_.
+CPU-time is priced at *$0.00002 per vCPU-second*.
 
 Previously, you would be charged for the CPU allocated to the instance multiplied by the time it was active, in this case 1 hour.
 
-CPU cost would have been: **$0.072** — 1 vCPU _ 3600 seconds _ $0.00002
+CPU cost would have been: **$0.072** — 1 vCPU * 3600 seconds * $0.00002
 
 Now, since you are only using 20% of your CPU capacity, your CPU cost is cut to 20% of the previous amount.
 
-CPU cost is now: **$0.0144** — 1 vCPU _ 3600 seconds _ $0.00002 \* 20% utilization
+CPU cost is now: **$0.0144** — 1 vCPU * 3600 seconds * $0.00002 * 20% utilization
 
 This can significantly reduce costs for Containers and Sandboxes.
 
diff --git a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
index baf0295247c3495..242d66f2e0cf6e2 100644
--- a/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
+++ b/src/content/changelog/containers/2026-02-25-higher-container-resource-limits.mdx
@@ -16,4 +16,4 @@ You can now run more [Containers](/containers/) concurrently with significantly
 
 This 15x increase enables larger-scale workloads on Containers. You can now run 15,000 instances of the `lite` instance type, 6,000 instances of `basic`, over 1,500 instances of `standard-1`, or over 1,000 instances of `standard-2` concurrently.
 
-Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
+Refer to [Limits](/containers/platform-details/limits/) for more details on the available instance types and limits.
\ No newline at end of file
diff --git a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
index d9a25a5bf08676f..cb2468f841ffe89 100644
--- a/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
+++ b/src/content/changelog/containers/2026-03-24-docker-hub-images.mdx
@@ -27,4 +27,4 @@ Containers now support [Docker Hub](https://hub.docker.com/) images. You can use
 
 Containers also support private Docker Hub images. To configure credentials, refer to [Use private Docker Hub images](/containers/platform-details/image-management/#use-private-docker-hub-images).
 
-For more information, refer to [Image management](/containers/platform-details/image-management/).
+For more information, refer to [Image management](/containers/platform-details/image-management/).
\ No newline at end of file
diff --git a/src/content/changelog/containers/2026-04-05-regional-placement.mdx b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
index bb35775f82b0c78..2871fa894eff6a3 100644
--- a/src/content/changelog/containers/2026-04-05-regional-placement.mdx
+++ b/src/content/changelog/containers/2026-04-05-regional-placement.mdx
@@ -8,10 +8,10 @@ date: 2026-04-05
 
 You can now specify placement constraints to control where your [Containers](/containers/) run.
 
-| Constraint     | Values                         | Use case              |
-| -------------- | ------------------------------ | --------------------- |
-| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR` | Geographic placement  |
-| `jurisdiction` | `eu`, `fedramp`                | Compliance boundaries |
+| Constraint     | Values                                  | Use case                          |
+| -------------- | --------------------------------------- | --------------------------------- |
+| `regions`      | `ENAM`, `WNAM`, `EEUR`, `WEUR`          | Geographic placement              |
+| `jurisdiction` | `eu`, `fedramp`                         | Compliance boundaries             |
 
 Use `regions` to limit placement to specific geographic areas. Use `jurisdiction` to restrict containers to compliance boundaries — `eu` maps to European regions (EEUR, WEUR) and `fedramp` maps to North American regions (ENAM, WNAM).
 
diff --git a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
index 169bb898b975965..4b8f807edcebfbe 100644
--- a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
+++ b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx
@@ -74,7 +74,7 @@ Define named outbound handlers then apply or remove them at runtime using `setOu
 export class MySandbox extends Sandbox {}
 
 MySandbox.outboundHandlers = {
-	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext) => {
+	allowHosts: async (req: Request, env: Env, ctx: OutboundHandlerContext ) => {
 		const url = new URL(req.url);
 		if (ctx.params.allowedHostnames.includes(url.hostname)) {
 			return fetch(req);
diff --git a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
index 9b7229b637259e4..797ef3ce255a866 100644
--- a/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
+++ b/src/content/changelog/containers/2026-05-12-ssh-enabled-by-default.mdx
@@ -51,4 +51,4 @@ To disable SSH, set `ssh.enabled` to `false` in your Container configuration:
 
 </WranglerConfig>
 
-For more information, refer to the [SSH documentation](/containers/ssh/).
+For more information, refer to the [SSH documentation](/containers/ssh/).
\ No newline at end of file
diff --git a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
index 076405a6f32954f..7a8ddd2b404d6c1 100644
--- a/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
+++ b/src/content/changelog/dex/2025-11-12-dex-logpush-jobs.mdx
@@ -6,7 +6,7 @@ date: 2025-11-12
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into WARP device metrics, connectivity, and network performance across your Cloudflare SASE deployment.
 
-We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience.
+We've released four new WARP and DEX device data sets that can be exported via [Cloudflare Logpush](/cloudflare-one/insights/logs/logpush/). These Logpush data sets can be exported to R2, a cloud bucket, or a SIEM to build a customized logging and analytics experience. 
 
 1. [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)
 2. [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)
@@ -15,4 +15,4 @@ We've released four new WARP and DEX device data sets that can be exported via [
 
 To create a new DEX or WARP Logpush job, customers can go to the account level of the Cloudflare dashboard > Analytics & Logs > Logpush to get started.
 
-![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
+![DEX logpush job creation dashboard](~/assets/images/changelog/dex/dex_logpush_datasets.png)
\ No newline at end of file
diff --git a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
index eaa2318c8339332..25a72ef1269d528 100644
--- a/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
+++ b/src/content/changelog/dex/2026-02-19-dex-supports-cmb-eu.mdx
@@ -2,6 +2,7 @@
 title: DEX Supports EU Customer Metadata Boundary
 description: Digital Experience Monitoring now fully supports the EU Customer Metadata Boundary
 date: 2026-02-19
+
 ---
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into [WARP](/warp-client/) device connectivity and performance to any internal or external application.
diff --git a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
index 5dabd4aeb835f4e..df5d41b9f6f8634 100644
--- a/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-internet-outage-notification.mdx
@@ -9,4 +9,4 @@ date: 2026-04-28
 This Internet outage and traffic anomaly data is pulled from [Cloudflare Radar](https://radar.cloudflare.com/). All Internet outage and traffic anomaly observations can be viewed in the [Radar Outage Center](https://radar.cloudflare.com/outage-center).
 
 ![Digital Experience Monitoring dashboard notification for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_ux_notification.png)
-![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
+![Digital Experience Monitoring dashboard analytics for Internet outage impacting Cloudflare One Client devices](~/assets/images/changelog/dex/dex_radar_analytics.png)
\ No newline at end of file
diff --git a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
index a85263a713f6a1e..37b7e2b2737abdf 100644
--- a/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
+++ b/src/content/changelog/dex/2026-04-28-dex-speed-test.mdx
@@ -4,10 +4,9 @@ description: Customers can run speed tests from the Cloudflare One Client to Clo
 date: 2026-04-28
 ---
 
-IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge.
+IT teams can now remotely run speed tests from the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to Cloudflare's network edge. 
 
 Each speed test includes the following metrics:
-
 - Internet speed: download and upload throughput
 - Latency: download, upload, unloaded latency, and jitter
 - Network quality score: video streaming, webchat/real-time communication (RTC)
diff --git a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
index 6af9120fe4e08ee..abfb872fa28d368 100644
--- a/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
+++ b/src/content/changelog/dex/2026-04-29-dex-tests-to-auth.mdx
@@ -4,10 +4,9 @@ description: Digital experience now supports testing applications with authentic
 date: 2026-04-29
 ---
 
-[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/).
+[Digital experience tests](/cloudflare-one/insights/dex/tests/) now support testing applications protected by Cloudflare Access or third-party authentication. All authentication secrets are managed via [Cloudflare Secret Store](/secrets-store/). 
 
 Digital experience tests also have enhanced configuration options including:
-
 - New HTTP methods (DELETE, PATCH, POST, PUT)
 - Secret Store headers, custom plain text headers, and custom request bodies
 - Advanced settings: follow redirects, response bodies, response headers, and allow untrusted certificates
diff --git a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
index 608405c5701e920..73705ab18a430b6 100644
--- a/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
+++ b/src/content/changelog/dlp/2025-04-14-account-level-dlp-settings.mdx
@@ -9,7 +9,6 @@ date: 2026-04-14T12:00:00Z
 **Account-level DLP settings are now available** in Cloudflare One. You can now configure advanced DLP settings at the account level, including OCR, AI context analysis, and payload masking. This provides consistent enforcement across all DLP profiles and simplifies configuration management.
 
 Key changes:
-
 - **Consistent enforcement**: Settings configured at the account level apply to all DLP profiles
 - **Simplified migration**: Settings enabled on any profile are automatically migrated to account level
 - **Deprecation notice**: Profile-level advanced settings will be deprecated in a future release
diff --git a/src/content/changelog/dlp/2025-07-17-document-matching.mdx b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
index 16c90b0f67b6ee1..7d3ef70acea78af 100644
--- a/src/content/changelog/dlp/2025-07-17-document-matching.mdx
+++ b/src/content/changelog/dlp/2025-07-17-document-matching.mdx
@@ -15,9 +15,10 @@ You can now create [document-based](/cloudflare-one/data-loss-prevention/detecti
 - **Granular control with similarity percentage:** Define a minimum similarity percentage (0-100%) that a document must meet to trigger a detection, reducing false positives.
 
 - **Comprehensive coverage:** Apply these document-based detection entries in:
-  - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
 
-  - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
+    - **Gateway policies:** To inspect network traffic for sensitive documents as they are uploaded or shared.
+
+    - **CASB (Cloud Access Security Broker):** To scan files stored in cloud applications for sensitive documents at rest.
 
 - **Identify sensitive data:** This new detection entry type is ideal for identifying sensitive data within completed forms, templates, or even small snippets of a larger document, helping you prevent data exfiltration and ensure compliance.
 
diff --git a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
index 17cdc9544eb17e9..21f93780d77fd28 100644
--- a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
+++ b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx
@@ -24,14 +24,14 @@ To help you apply these topics quickly, we have also released five new predefine
 
 3. **Granular Guardrails**
 
-   You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
+    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) to individual AI applications (for example, `ChatGPT`) and specific user actions (for example, `SendPrompt`) to block sensitive prompts.
 
-   ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
 
-4. **Full Prompt Logging**
+ 4. **Full Prompt Logging**
+   
+    To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by ```conversation_id```, allowing you to reconstruct the full context of an interaction that led to a policy violation.
 
-   To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by `conversation_id`, allowing you to reconstruct the full context of an interaction that led to a policy violation.
-
-   ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
 
 AI prompt protection is now available in open beta. To learn more about it, read the [blog](https://blog.cloudflare.com/ai-prompt-protection/#closing-the-loop-logging) or refer to [AI prompt topics](/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics).
diff --git a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
index d8e05425862ab77..5c12da589a2636c 100644
--- a/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
+++ b/src/content/changelog/dlp/2026-03-25-har-file-detection-and-sanitization.mdx
@@ -11,7 +11,7 @@ Gateway now includes a predefined DLP profile called **Unsanitized HAR** that de
 
 ## How to configure a HAR file policy
 
-In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
+In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to  **Zero Trust** >  **Traffic policies** > **Firewall Policies** > **HTTP** and create a new HTTP policy using the **DLP Profile** selector:
 
 | Selector    | Operator | Value             | Action |
 | ----------- | -------- | ----------------- | ------ |
diff --git a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
index 649f291806b1ee8..7326522ab2e356e 100644
--- a/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
+++ b/src/content/changelog/dlp/2026-04-14-cloudflare-api-token-detections.mdx
@@ -7,11 +7,11 @@ products: [dlp]
 
 The **Credentials and Secrets** DLP profile now includes three new predefined entries for detecting Cloudflare API credentials:
 
-| Entry name                         | Token prefix | Detects                   |
-| ---------------------------------- | ------------ | ------------------------- |
-| Cloudflare User API Key            | `cfk_`       | User-scoped API keys      |
-| Cloudflare User API Token          | `cfut_`      | User-scoped API tokens    |
-| Cloudflare Account Owned API Token | `cfat_`      | Account-scoped API tokens |
+| Entry name | Token prefix | Detects |
+| --- | --- | --- |
+| Cloudflare User API Key | `cfk_` | User-scoped API keys |
+| Cloudflare User API Token | `cfut_` | User-scoped API tokens |
+| Cloudflare Account Owned API Token | `cfat_` | Account-scoped API tokens |
 
 These detections target the new [Cloudflare API credential format](/fundamentals/api/get-started/token-formats/), which uses a structured prefix and a CRC32 checksum suffix. The identifiable prefix makes it possible to detect leaked credentials with high confidence and low false positive rates — no surrounding context such as `Authorization: Bearer` headers is required.
 
@@ -26,9 +26,9 @@ Credentials generated before this format change will not be matched by these ent
 
 Example policy:
 
-| Selector    | Operator | Value                     | Action |
-| ----------- | -------- | ------------------------- | ------ |
-| DLP Profile | in       | _Credentials and Secrets_ | Block  |
+| Selector | Operator | Value | Action |
+| --- | --- | --- | --- |
+| DLP Profile | in | _Credentials and Secrets_ | Block |
 
 You can also enable individual entries to scope detection to specific credential types — for example, enabling **Account Owned API Token** detection without enabling **User API Key** detection.
 
diff --git a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
index 64134f5ef20859c..a4a744c06468c98 100644
--- a/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
+++ b/src/content/changelog/dlp/2026-04-28-pii-record-profile.mdx
@@ -2,7 +2,7 @@
 title: Detect PII records with a new predefined DLP profile
 description: A new predefined DLP profile detects records that contain multiple types of personal data, reducing false positives from isolated matches.
 date: 2026-04-28
-products:
+products: 
   - dlp
 ---
 
diff --git a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
index fda8a201e4ce67f..483aed6201b6f66 100644
--- a/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
+++ b/src/content/changelog/dns/2026-03-31-internal-dns-open-beta.mdx
@@ -7,7 +7,6 @@ date: 2026-03-31
 Internal DNS is now in open beta.
 
 ## Who can use it?
-
 Internal DNS is bundled as a part of Cloudflare Gateway and is now available to every Enterprise customer with one of the following subscriptions:
 
 - Cloudflare Zero Trust Enterprise
diff --git a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
index e9117eeb36fbf71..ada68f5dc86c767 100644
--- a/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
+++ b/src/content/changelog/dns/2026-04-28-enforce-dns-only.mdx
@@ -3,7 +3,6 @@ title: Account-level enforce DNS-only
 description: Bypass Cloudflare's reverse proxy for all zones in your account with a single API call.
 date: 2026-04-28
 ---
-
 import { DashButton } from "~/components";
 
 You can now disable Cloudflare's reverse proxy across all zones in your account simultaneously using the new `enforce_dns_only` setting. When enabled, Cloudflare responds to DNS queries for all proxied records with your origin IP addresses instead of Cloudflare's anycast IPs.
diff --git a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
index eb2897fd7f98f7b..e03702fa3be2931 100644
--- a/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
+++ b/src/content/changelog/durable-objects/2025-08-21-durable-objects-get-by-name.mdx
@@ -10,11 +10,11 @@ date: 2025-08-21
 You can now create a client (a [Durable Object stub](/durable-objects/api/stub/)) to a Durable Object with the new `getByName` method, removing the need to convert Durable Object names to IDs and then create a stub.
 
 ```js
-// Before: (1) translate name to ID then (2) get a client
+// Before: (1) translate name to ID then (2) get a client 
 const objectId = env.MY_DURABLE_OBJECT.idFromName("foo"); // or .newUniqueId()
-const stub = env.MY_DURABLE_OBJECT.get(objectId);
+const stub = env.MY_DURABLE_OBJECT.get(objectId); 
 
-// Now: retrieve client to Durable Object directly via its name
+// Now: retrieve client to Durable Object directly via its name 
 const stub = env.MY_DURABLE_OBJECT.getByName("foo");
 
 // Use client to send request to the remote Durable Object
@@ -23,4 +23,4 @@ const rpcResponse = await stub.sayHello();
 
 Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together. You can have billions of Durable Objects, providing isolation between application tenants.
 
-To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
+To learn more, visit the Durable Objects [API Documentation](/durable-objects/api/namespace/#getbyname) or the [getting started guide](/durable-objects/get-started/).
\ No newline at end of file
diff --git a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
index b0b6b6b70c779bb..10b3c5b7270cdbe 100644
--- a/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
+++ b/src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx
@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
 
 ![Screenshot of Durable Objects Data Studio](~/assets/images/workers/changelog/do-data-studio.png)
 
-You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.
+You can now view and write to each Durable Object's storage using a UI editor on the Cloudflare dashboard. Only Durable Objects using [SQLite storage](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class) can use Data Studio.  
 
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
diff --git a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
index ab0bc29c8091916..7d4b1c1963247eb 100644
--- a/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
+++ b/src/content/changelog/durable-objects/2025-12-12-durable-objects-sqlite-storage-billing.mdx
@@ -9,10 +9,9 @@ date: 2025-12-12
 
 import { DashButton } from "~/components";
 
-Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier).
+Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). 
 
 To view your SQLite storage usage, go to the **Durable Objects** page
-
 <DashButton url="/?to=/:account/workers/durable-objects" />
 
 If you do not want to incur costs, please take action such as optimizing queries or deleting unnecessary stored data in order to reduce your SQLite storage usage ahead of the January 7th target. Only usage on and after the billing target date will incur charges.
diff --git a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
index 01b6f70aebb1c1f..c3a7dd97977d0d4 100644
--- a/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
+++ b/src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
@@ -15,19 +15,19 @@ This is especially useful for [alarms](/durable-objects/api/alarms/), where ther
 import { DurableObject } from "cloudflare:workers";
 
 export class ChatRoom extends DurableObject {
-	async getRoomName() {
-		// ctx.id.name returns the name passed to getByName() or idFromName()
-		return this.ctx.id.name;
-	}
+  async getRoomName() {
+    // ctx.id.name returns the name passed to getByName() or idFromName()
+    return this.ctx.id.name;
+  }
 }
 
 // Worker
 export default {
-	async fetch(request, env) {
-		const stub = env.CHAT_ROOM.getByName("general");
-		const roomName = await stub.getRoomName();
-		return new Response(`Welcome to ${roomName}!`);
-	},
+  async fetch(request, env) {
+    const stub = env.CHAT_ROOM.getByName("general");
+    const roomName = await stub.getRoomName();
+    return new Response(`Welcome to ${roomName}!`);
+  },
 };
 ```
 
diff --git a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
index 7bbf5100d38aea3..d4933092b676b0e 100644
--- a/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
+++ b/src/content/changelog/email-routing/2025-07-21-subaddressing.mdx
@@ -12,4 +12,4 @@ Customers can use this feature to dynamically add context to their emails, such
 
 ![Subaddressing](~/assets/images/changelog/email-routing/subaddressing.png)
 
-Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
+Check our [Developer Docs](/email-routing/setup/email-routing-addresses/#subaddressing) to learn on to enable subaddressing in Email Routing.
\ No newline at end of file
diff --git a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
index 7ac05e0429ad659..2a643465f298e14 100644
--- a/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
+++ b/src/content/changelog/email-security-cf1/2024-12-19-escalate-user-submissions.mdx
@@ -16,4 +16,4 @@ This feature is available across these Email security packages:
 
 - **Advantage**
 - **Enterprise**
-- **Enterprise + PhishGuard**
+- **Enterprise + PhishGuard**
\ No newline at end of file
diff --git a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
index 24afb396ce499bc..7e74cf7136cb225 100644
--- a/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
+++ b/src/content/changelog/email-security-cf1/2025-10-16-on-demand-security-report.mdx
@@ -13,6 +13,7 @@ These reports offer several key benefits:
 - **Configuration Transparency:** Gain a clear view of your policy, submission, and domain configurations to ensure optimal setup.
 - **Account Takeover Risks:** Get a snapshot of your M365 risky users (requires a Microsoft Entra ID P2 license and [M365 SaaS integration](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/microsoft-365/)).
 
+
 To get started, refer to [Download a security report](/cloudflare-one/email-security/monitoring/download-report/#download-a-security-report).
 ![Report](~/assets/images/changelog/email-security/report.png)
 
diff --git a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
index cbb47a69c0949ea..47d73e8920e5d3c 100644
--- a/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
+++ b/src/content/changelog/email-security-cf1/2025-11-18-temporary-adjustment-to-final-disposition-column.mdx
@@ -6,7 +6,8 @@ date: 2025-11-18
 
 # Adjustment to Final Disposition column
 
-## The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
+The **Final Disposition** column in **Submissions** > **Team Submissions** tab is changing for non-Phishguard customers.
+---
 
 ### What's Changing
 
diff --git a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
index 92b39dac688afa0..b8d67579c27c156 100644
--- a/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
+++ b/src/content/changelog/email-security-cf1/2025-12-03-submission-terminology-update.mdx
@@ -1,6 +1,6 @@
 ---
 title: Reclassifications to Submissions
-description: Submission terminology update to reflect outcomes
+description: Submission terminology update to reflect outcomes 
 date: 2025-12-03T21:11:33Z
 ---
 
@@ -10,8 +10,7 @@ Submissions are leveraged to tune future variants of campaigns. To respect data
 
 ![nav_example](~/assets/images/changelog/email-security/reclassification-submission.png)
 
-This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Advantage** 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
index e12c5cc1bef0386..b38737ac382f6db 100644
--- a/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
+++ b/src/content/changelog/email-security-cf1/2026-01-12-enhanced-visibility-post-delivery-actions.mdx
@@ -4,7 +4,7 @@ description: Additional post delivery action log details for failures
 date: 2026-01-12T11:15:33Z
 ---
 
-The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field.
+The Action Log now provides enriched data for post-delivery actions to improve troubleshooting. In addition to success confirmations, failed actions now display the targeted Destination folder and a specific failure reason within the Activity field. 
 
 :::note
 Error messages will vary depending on whether you are using Google Workspace or Microsoft 365.
@@ -14,7 +14,6 @@ Error messages will vary depending on whether you are using Google Workspace or
 
 This update allows you to see the full lifecycle of a failed action. For instance, if an administrator tries to move an email that has already been deleted or moved manually, the log will now show the multiple retry attempts and the specific destination error.
 
-This applies to all Email Security packages:
-
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
index fdf3bbd3fac9920..2b9c5533289c542 100644
--- a/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
+++ b/src/content/changelog/email-security-cf1/2026-02-02-improved-accessibility-search-for-monitoring.mdx
@@ -6,17 +6,17 @@ date: 2026-02-02T11:05:33Z
 
 We have updated the Monitoring page to provide a more streamlined and insightful experience for administrators, improving both data visualization and dashboard accessibility.
 
-- **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis.
-  ![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
-- **Improved Accessibility & Usability**:
-  _ **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation.
-  _ **Actionable UI**: All available actions are now accessible via dedicated buttons. \* **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions.
-  ![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
-- **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
-  ![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
+* **Enhanced Visual Layout**: Optimized contrast and the introduction of stacked bar charts for clearer data visualization and trend analysis. 
+![visual-example](~/assets/images/changelog/email-security/monitoring-bar-charts.png)
+* **Improved Accessibility & Usability**: 
+    * **Widget Search**: Added search functionality to multiple widgets, including Policies, Submitters, and Impersonation. 
+    * **Actionable UI**: All available actions are now accessible via dedicated buttons. 
+    * **State Indicators**: Improved UI states to clearly communicate loading, empty datasets, and error conditions. 
+![buttons-example](~/assets/images/changelog/email-security/monitoring-buttons.png)
+* **Granular Data Breakdowns**: New views for dispositions by month, malicious email details, link actions, and impersonations.
+![monthly-example](~/assets/images/changelog/email-security/monitoring-monthly-dispositions.png)
 
-This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+This applies to all Email Security packages: 
+-   **Advantage** 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
diff --git a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
index 40ee34a930aa4d0..6d9695bd7a66d3e 100644
--- a/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
+++ b/src/content/changelog/email-security-cf1/2026-03-15-infinite-paging-investigations.mdx
@@ -10,12 +10,12 @@ In the dashboard, infinite paging is now supported in the Investigations view. T
 
 For high-volume use cases, we recommend:
 
-- **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
-- **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
-- **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
+-   **[Logpush](/cloudflare-one/insights/logs/logpush/email-security-logs/) to a SIEM** for full-fidelity datasets and long-term retention.
+-   **SOAR playbooks** against the async bulk action API for large-scale remediation. Bulk actions initiated from the dashboard remain capped at 1,000 messages per action.
+-   **The Investigations API** for report exports larger than 1,000 results, which is the dashboard download cap.
 
 This applies to all Email Security packages:
 
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+-   **Advantage**
+-   **Enterprise**
+-   **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
index cf4ab36e568d60c..a69648a508bacbf 100644
--- a/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-06-dane-support-mx-deployments.mdx
@@ -3,14 +3,12 @@ title: DANE Support for MX Deployments
 description: DNSSEC-backed TLSA records now available on regional MX hostnames for verified encrypted email delivery
 date: 2026-04-06T09:00:00Z
 ---
-
 Cloudflare Email Security now supports DANE (DNS-based Authentication of Named Entities) for MX deployments. This enhancement strengthens email transport security by enabling DNSSEC-backed certificate verification for our regional MX records.
 
-- Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
-- DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
+* Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
+* DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.
 
 This applies to all Email Security packages:
-
-- **Advantage**
-- **Enterprise**
-- **Enterprise + PhishGuard**
+-   **Advantage**
+-   **Enterprise**
+-   **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
index eab1731927d760e..3019f6e986513d4 100644
--- a/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
+++ b/src/content/changelog/email-security-cf1/2026-04-07-triage-status-tracking.mdx
@@ -5,14 +5,12 @@ date: 2026-04-07 09:00:00 UTC
 ---
 
 Cloudflare Email security now supports **Triage Status Tracking for User Submissions**. This enhancement gives SOC teams a streamlined way to track, manage, and prioritize user-submitted emails directly within the Cloudflare One dashboard.
-
 - The User Submissions table now includes a **Status** column with three states: **Unreviewed** (new submissions awaiting triage), **Reviewed** (submissions assessed by the SOC team), and **Escalated** (submissions escalated to team submissions for further investigation). Analysts can quickly update statuses and filter the table to focus on what needs attention.
 - SOC teams can now organize their triage workflows, avoid duplicate reviews, and make sure critical threats get escalated for deeper investigation—bringing order to the chaos of high-volume submission management.
 
 Triage Status Tracking is **automatically available** for all Email security customers using the user submissions feature. No additional configuration is required; customers just need to make sure user submissions are being sent to their user submission aliases.
 
 This applies to all Email security packages:
-
 - **Advantage**
 - **Enterprise**
 - **Enterprise + PhishGuard**
diff --git a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
index 8447a0ad8b9c7aa..558c35e1449d8c7 100644
--- a/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
+++ b/src/content/changelog/email-security-cf1/2026-05-06-cloudy-summaries-in-phishnet_o365.mdx
@@ -3,7 +3,6 @@ title: Cloudy Summaries in PhishNet O365
 description: Cloudy email summaries are now available in PhishNet for Office 365 environments.
 date: 2026-05-06T18:15:13Z
 ---
-
 PhishNet users can now access **Cloudy summaries** directly within the email investigation experience. When reviewing a message in PhishNet, users will see an AI-generated summary that provides additional context and key details about the email.
 
 These summaries help users quickly understand the nature of a message without needing to manually parse through headers, body content, and detection signals. Cloudy surfaces the most relevant information so users can make faster, more informed decisions about suspicious emails.
diff --git a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
index 55a9de27459f439..a5377b7e567f220 100644
--- a/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
+++ b/src/content/changelog/fundamentals/2025-06-23-user-groups-ga.mdx
@@ -14,11 +14,11 @@ We're announcing the GA of **User Groups for Cloudflare Dashboard** and **System
 
 **SCIM User Groups [GA]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.
 
-**Stability & Scale**:
+**Stability & Scale**: 
 These features have undergone extensive testing during the Public Beta period and are now ready for production use across enterprises of all sizes.
 
 :::note
-SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
+SCIM Virtual Groups  (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025. SCIM Virtual Groups end-of-life will take effect on December 2, 2025. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.
 :::
 
 For more info:
diff --git a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
index 3bf99528e750d6f..78ffc7cb93ea799 100644
--- a/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
+++ b/src/content/changelog/fundamentals/2025-09-03-rate-limiting-improvement.mdx
@@ -1,38 +1,31 @@
 ---
 title: Introducing new headers for rate limiting on Cloudflare's API
-description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code.
+description: Cloudflare's API handles rate limiting automatically in the SDKs and how to respond appropriately in your code. 
 products:
   - fundamentals
 date: 2025-09-03
 ---
+Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available. 
 
-Cloudflare's API now supports rate limiting headers using the pattern developed by the [IETF draft on rate limiting](https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html). This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available.
+Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this. 
 
-Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this.
-
-As always, if you need any help with rate limits, please contact Support.
+As always, if you need any help with rate limits, please contact Support. 
 
 ### Changes
-
 #### New Headers
 
 **Headers that are always returned:**
-
 - `Ratelimit`: List of service limit items, composed of the limit name, the remaining quota (`r`) and the time next window resets (`t`). For example: `"default";r=50;t=30`
 - `Ratelimit-Policy`: List of quota policy items, composed of the policy name, the total quota (`q`) and the time window the quota applies to (`w`). For example: `"burst";q=100;w=60`
 
 **Returned only when a rate limit has been reached (error code: 429):**
-
 - Retry-After: Number of Seconds until more capacity is available, rounded up
 
 #### SDK Back offs
-
-- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached.
+- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached. 
 
 ### GraphQL and Edge APIs
-
-These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL.
+These new headers and back offs are only available for Cloudflare REST APIs, and will not affect GraphQL. 
 
 ### For more information
-
-- [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
+* [Rate limits at Cloudflare](https://developers.cloudflare.com/fundamentals/api/reference/limits/)
diff --git a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
index 2d4cd4c94696926..f3c21ce51683451 100644
--- a/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
+++ b/src/content/changelog/fundamentals/2025-09-08-reminders-about-two-factor-authentication-backup-codes.mdx
@@ -6,8 +6,7 @@ products:
 date: 2025-09-08
 ---
 
-Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future.
+Two-factor authentication is the best way to help protect your account from account takeovers, but if you lose your second factor, you could be locked out of your account. Lock outs are one of the top reasons customers contact Cloudflare support, and our policies often don't allow us to bypass two-factor authentication for customers that are locked out. Today we are releasing an improvement where Cloudflare will periodically remind you to securely save your backup codes so you don't get locked out in the future. 
 
 ## For more information
-
 - [Two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
index 7132df4e0c21e5a..7cdd79523b47438 100644
--- a/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
+++ b/src/content/changelog/fundamentals/2025-09-25-sign-in-with-github.mdx
@@ -6,8 +6,7 @@ products:
 date: 2025-09-25
 ---
 
-Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address.
+Cloudflare has launched sign in with GitHub as a log in option. This feature is available to all users with a verified email address who are not using SSO. To use it, simply click on the `Sign in with GitHub` button on the dashboard login page. You will be logged in with your primary GitHub email address. 
 
 ## For more information
-
 - [Log in to Cloudflare](/fundamentals/user-profiles/login/)
diff --git a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
index a55ff67b07c1c01..ef6b79ccba485df 100644
--- a/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
+++ b/src/content/changelog/fundamentals/2025-10-01-md-returned.mdx
@@ -12,4 +12,4 @@ Users can now specify that they want to retrieve Cloudflare documentation as mar
 curl https://developers.cloudflare.com/workers/ -H 'Accept: text/markdown'  -v
 ```
 
-If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
+If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example [here](https://github.com/cloudflare/cloudflare-docs/pull/25493).
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
index 4d7ebf5cd529a99..c9763acda83fa9f 100644
--- a/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
+++ b/src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx
@@ -15,3 +15,4 @@ Today, we are launching a new user experience which allows users to manage their
 ## For more information
 
 - [Cloudflare dashboard SSO](/fundamentals/manage-members/dashboard-sso/)
+
diff --git a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
index 07fdea6b5a065fe..206794e93f44faa 100644
--- a/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
@@ -4,15 +4,15 @@ description: Cloudflare now offers email two-factor authentication to protect yo
 date: 2025-10-30
 ---
 
-Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support.
+Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support. 
 
-Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already.
+Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already. 
 
 You can now enable email 2FA on the Cloudflare dashboard:
 
 1. Go to **Profile** at the top right corner.
 2. Select **Authentication**.
-3. Under **Two-Factor Authentication**, select **Set up**.
+3. Under **Two-Factor Authentication**, select **Set up**.  
 
 ## Sign-in security best practices
 
diff --git a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
index 612e193af27fb2f..b8e0027220e35a2 100644
--- a/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
+++ b/src/content/changelog/fundamentals/2025-10-30-member-management-improvements.mdx
@@ -1,5 +1,5 @@
 ---
-title: Revamped Member Management UI
+title: Revamped Member Management UI 
 description: Simplifying the management of users, groups, and permissions within Cloudflare.
 products:
   - fundamentals
@@ -8,6 +8,7 @@ date: 2025-10-30
 
 As Cloudflare's platform has grown, so has the need for precise, role-based access control. We’ve redesigned the Member Management experience in the Dashboard to help administrators more easily discover, assign, and refine permissions for specific principals.
 
+
 ### What's New
 
 **Refreshed member invite flow**
@@ -16,10 +17,10 @@ We overhauled the Invite Members UI to simplify inviting users and assigning per
 
 ![Updated Invite Flow UX](~/assets/images/changelog/fundamentals/2025-10-30-invite-experience.gif)
 
-**Refreshed Members Overview Page**
 
+**Refreshed Members Overview Page**
+ 
 We've updated the Members Overview Page to clearly display:
-
 - Member 2FA status
 - Which members hold Super Admin privileges
 - API access settings per member
@@ -29,11 +30,12 @@ We've updated the Members Overview Page to clearly display:
 
 **New Member Permission Policies Details View**
 
-We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have.
+We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have. 
 
 ![Updated Permission Policies Details Screen](~/assets/images/changelog/fundamentals/2025-10-30-permission-policies-screen.gif)
 
-**Improved Member Permission Workflow**
+
+**Improved Member Permission Workflow** 
 
 We redesigned the permission management experience to make it faster and easier for administrators to review roles and grant access.
 
@@ -41,4 +43,4 @@ We redesigned the permission management experience to make it faster and easier
 
 **Account-scoped Policies Restrictions Relaxed**
 
-Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions.
+Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions. 
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
index c83d90c5c82e0db..4809af309b7fae0 100644
--- a/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
+++ b/src/content/changelog/fundamentals/2026-01-23-New-2FA-Experience.mdx
@@ -6,10 +6,9 @@ date: 2026-01-23
 
 ![Screenshot of new 2FA enrollment experience](~/assets/images/changelog/fundamentals/2026-01-23-2fa-interstitial.png)
 
-In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers.
+In an effort to improve overall user security, users without 2FA will be prompted upon login to enroll in email 2FA. This will improve user security posture while minimizing friction. Users without email 2FA enabled will see a prompt to secure their account with additional factors upon logging in. Enrolling in 2FA remains optional, but strongly encouraged as it is the best way to prevent account takeovers. 
 
-We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works.
+We also made changes to existing 2FA screens to improve the user experience. Now we have distinct experiences for each 2FA factor type, reflective of the way that factor works. 
 
-## For more information
-
-- [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
+## For more information 
+* [Configure Email Two Factor Authentication](/fundamentals/user-profiles/2fa/#configure-email-two-factor-authentication)
diff --git a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
index 0bd7606af0188e8..e00305d994595e1 100644
--- a/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
+++ b/src/content/changelog/fundamentals/2026-02-12-markdown-for-agents.mdx
@@ -8,6 +8,7 @@ date: 2026-02-12
 
 Cloudflare's network now supports real-time content conversion at the source, for enabled zones using [content negotiation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation) headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for `text/markdown` in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
 
+
 Here is a curl example with the `Accept` negotiation header requesting this page from our developer documentation:
 
 ```bash
@@ -38,4 +39,4 @@ ultimately resulting in better results while minimizing token waste.
 ...
 ```
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) and our [blog announcement](https://blog.cloudflare.com/markdown-for-agents/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
index 69a7003183ac4a6..33a3ae22e6230f3 100644
--- a/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
+++ b/src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx
@@ -16,4 +16,4 @@ This release adds the following improvements:
 
 If you haven’t enabled automatic Markdown conversion yet, visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section of the Cloudflare dashboard and enable **Markdown for Agents**.
 
-Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
index 5ba8aed4decf5c8..e6ad76ed4ec43a0 100644
--- a/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-11-json-rfc9457-responses-for-1xxx-errors.mdx
@@ -57,6 +57,5 @@ curl -s --compressed -H "Accept: application/problem+json" -A "TestAgent/1.0" -H
 ```
 
 References:
-
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
index 7635eb13215cd99..aa790c1bc84902b 100644
--- a/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-03-12-retry-after-header-for-1xxx-errors.mdx
@@ -12,15 +12,15 @@ Cloudflare-generated 1xxx error responses now include a standard `Retry-After` H
 
 Seven retryable error codes now emit `Retry-After`:
 
-| Error code | Retry-After (seconds) | Error name                  |
-| ---------- | --------------------- | --------------------------- |
-| 1004       | 120                   | DNS resolution error        |
-| 1005       | 120                   | Banned zone                 |
-| 1015       | 30                    | Rate limited                |
-| 1033       | 120                   | Argo Tunnel error           |
-| 1038       | 60                    | HTTP headers limit exceeded |
-| 1200       | 60                    | Cache connection limit      |
-| 1205       | 5                     | Too many redirects          |
+| Error code | Retry-After (seconds) | Error name |
+|---|---|---|
+| 1004 | 120 | DNS resolution error |
+| 1005 | 120 | Banned zone |
+| 1015 | 30 | Rate limited |
+| 1033 | 120 | Argo Tunnel error |
+| 1038 | 60 | HTTP headers limit exceeded |
+| 1200 | 60 | Cache connection limit |
+| 1205 | 5 | Too many redirects |
 
 The header value matches the existing `retry_after` body field in JSON and Markdown responses.
 
@@ -39,6 +39,5 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
-
 - [RFC 9110 section 10.2.3 - Retry-After](https://www.rfc-editor.org/rfc/rfc9110#section-10.2.3)
 - [Cloudflare 1xxx error documentation](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
index c0c1a7659fedd48..92f5a45e27a8c57 100644
--- a/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
+++ b/src/content/changelog/fundamentals/2026-03-17-scim-authentik-support.mdx
@@ -6,7 +6,7 @@ products:
 date: 2026-03-18
 ---
 
-Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers.
+Cloudflare dashboard SCIM provisioning now supports [Authentik](https://goauthentik.io/) as an identity provider, joining Okta and Microsoft Entra ID as explicitly supported providers. 
 
 Customers can now sync users and group information from Authentik to Cloudflare, apply Permission Policies to those groups, and manage the lifecycle of users & groups directly from your Authentik Identity Provider.
 
diff --git a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
index 48fa5bd55c357ee..115c15516aecbda 100644
--- a/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
+++ b/src/content/changelog/fundamentals/2026-03-18-scim-audit-logging.mdx
@@ -17,9 +17,9 @@ Cloudflare dashboard SCIM provisioning operations are now captured in [Audit Log
 | Create SCIM User  | User provisioned from IdP               |
 | Replace SCIM User | User fully replaced (PUT)               |
 | Update SCIM User  | User attributes modified (PATCH)        |
-| Delete SCIM User  | Member deprovisioned                    |
+| Delete SCIM User  | Member deprovisioned                      |
 | Create SCIM Group | Group provisioned from IdP              |
 | Update SCIM Group | Group membership or attributes modified |
-| Delete SCIM Group | Group deprovisioned                     |
+| Delete SCIM Group | Group deprovisioned                           |
 
 For more details, refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/).
diff --git a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
index 99e5c7faac36b0e..66f075b8044732c 100644
--- a/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
+++ b/src/content/changelog/fundamentals/2026-04-06-organizations-public-beta.mdx
@@ -18,7 +18,7 @@ We're announcing the public beta of **Organizations** for enterprise customers,
 
 **Centralized Account Management**: At launch, every Organization member has the Organization Super Admin role. Organization Super Admins can invite other users and manage any child account under the Organization implicitly.
 **Shared policies**: Share [WAF](/waf/custom-rules/) or [Gateway](/cloudflare-one/traffic-policies/tiered-policies/organizations/) policies across multiple accounts within your Organization to simplify centralized policy management.
-**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year.
+**Implicit access**: Members of an Organization automatically receive Super Administrator permissions across child accounts, removing the need for explicit membership on each account. Additional Org-level roles will be available over the course of the year. 
 
 **Unified analytics**: View, filter, and download aggregate HTTP analytics across all Organization child accounts from a single dashboard for centralized visibility into traffic patterns and security events.
 
diff --git a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
index 6df437b0b5fe8f2..4fb052b1583582b 100644
--- a/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
+++ b/src/content/changelog/fundamentals/2026-04-10-secret-scanning-support.mdx
@@ -1,6 +1,6 @@
 ---
 title: API tokens now detectable by secret scanning tools
-description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code.
+description: Cloudflare API tokens include identifiable patterns for automated leak detection in repositories and code. 
 date: 2026-04-10
 ---
 
diff --git a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
index b21e3e867f40139..ea662602678945a 100644
--- a/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
+++ b/src/content/changelog/fundamentals/2026-04-14-oauth-consent-and-revoke.mdx
@@ -5,45 +5,29 @@ products:
   - fundamentals
 date: 2026-04-14
 ---
-
 OAuth allows third-party applications to access your Cloudflare account on your behalf — like when Wrangler deploys Workers or when monitoring tools read your analytics. You now have **granular control** over which accounts these applications can access, plus the ability to revoke access anytime.
-
 ## What's new
-
 ### Choose which accounts to authorize
-
 When authorizing an OAuth application, you can now **select specific accounts** instead of granting access to all your accounts:
-
 - **Account-by-account selection** — Choose exactly which accounts the application can access
 - **"All accounts" option** — Still available for trusted tools like Wrangler
-  This gives you precise control who can access your data.
-
+This gives you precise control who can access your data.
 ### Clear consent screens
-
 The OAuth consent screen now shows:
-
 - **What the application can access** — Explicit list of permissions being requested
-- **Who created the application** — Application owner and contact information
+- **Who created the application** — Application owner and contact information  
 - **Which accounts you're authorizing** — Checkboxes for account selection
-
 ### Revoke access anytime
-
 Manage authorized OAuth applications from your profile:
-
 - **See all connected apps** — View every OAuth application with access to your accounts
 - **Review permissions and scope** — Check what each application can do and which accounts it can access
 - **Revoke instantly** — Remove access with one click when you no longer need it
-  To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
-
+To manage your OAuth applications, navigate to **Profile** > **Access Management** > **[Connected Applications](https://dash.cloudflare.com/profile/access-management/authorization)**.
 ## Why this matters
-
 These updates give you:
-
 - **Granular control** — Authorize apps per-account instead of all-or-nothing
 - **Transparency** — Know exactly what you're authorizing before you consent
 - **Security** — Limit blast radius by restricting access to only necessary accounts
 - **Easy cleanup** — Revoke access when applications are no longer needed
-
 ## Learn more
-
 Read more about these improvements in our blog post: [Improving the OAuth consent experience](https://blog.cloudflare.com/improved-developer-security/#improving-the-oauth-consent-experience).
diff --git a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
index 02073d22df3580c..0bd7547904452c2 100644
--- a/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
+++ b/src/content/changelog/fundamentals/2026-04-27-structured-responses-for-5xx-errors.mdx
@@ -50,6 +50,5 @@ curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAge
 ```
 
 References:
-
 - [RFC 9457 — Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457)
 - [Cloudflare 5xx error documentation](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/)
diff --git a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
index 2babbbfb86081cd..521711f9c22d54b 100644
--- a/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
+++ b/src/content/changelog/fundamentals/2026-05-04-keyboard-shortcuts.mdx
@@ -11,34 +11,34 @@ You can now navigate, switch context, and take common actions in the Cloudflare
 
 ## Navigate
 
-| Shortcut      | Action                                                 |
-| ------------- | ------------------------------------------------------ |
-| `g h`         | Go to Home                                             |
-| `g a`         | Go to account overview                                 |
-| `g z`         | Go to zone overview                                    |
-| `g p`         | Go to your profile                                     |
-| `g w`         | Go to Workers & Pages                                  |
-| `g o`         | Go to Zero Trust                                       |
-| `g b`         | Go to billing                                          |
+| Shortcut | Action |
+| --- | --- |
+| `g h` | Go to Home |
+| `g a` | Go to account overview |
+| `g z` | Go to zone overview |
+| `g p` | Go to your profile |
+| `g w` | Go to Workers & Pages |
+| `g o` | Go to Zero Trust |
+| `g b` | Go to billing |
 | `g 1` – `g 5` | Go to a recent or pinned item (by position in sidebar) |
-| `t →`         | Move to the next tab                                   |
-| `t ←`         | Move to the previous tab                               |
-| `p →`         | Move to the next page of a table                       |
-| `p ←`         | Move to the previous page of a table                   |
+| `t →` | Move to the next tab |
+| `t ←` | Move to the previous tab |
+| `p →` | Move to the next page of a table |
+| `p ←` | Move to the previous page of a table |
 
 ## Take action
 
-| Shortcut | Action                               |
-| -------- | ------------------------------------ |
-| `/`      | Open quick search                    |
-| `?`      | Show keyboard shortcuts              |
-| `s a`    | Switch account                       |
-| `s z`    | Switch zone                          |
-| `s .`    | Star or unstar the current zone      |
-| `p .`    | Pin or unpin the current page        |
-| `t s`    | Toggle the sidebar open or closed    |
-| `t m`    | Expand or collapse all sidebar menus |
-| `t a`    | Toggle Ask AI sidebar                |
-| `d .`    | Toggle dark mode                     |
-| `c u`    | Copy the current URL                 |
-| `c d`    | Copy a deep link URL                 |
+| Shortcut | Action |
+| --- | --- |
+| `/` | Open quick search |
+| `?` | Show keyboard shortcuts |
+| `s a` | Switch account |
+| `s z` | Switch zone |
+| `s .` | Star or unstar the current zone |
+| `p .` | Pin or unpin the current page |
+| `t s` | Toggle the sidebar open or closed |
+| `t m` | Expand or collapse all sidebar menus |
+| `t a` | Toggle Ask AI sidebar |
+| `d .` | Toggle dark mode |
+| `c u` | Copy the current URL |
+| `c d` | Copy a deep link URL |
diff --git a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
index ae01229a4717c46..6d777cba0965f65 100644
--- a/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
+++ b/src/content/changelog/gateway/2025-07-24-HTTP-Inspection-on-all-ports.mdx
@@ -7,9 +7,9 @@ hidden: false
 date: 2025-07-24
 ---
 
-[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more.
+[Gateway](/cloudflare-one/traffic-policies/) can now apply [HTTP filtering](/cloudflare-one/traffic-policies/http-policies/) to all proxied HTTP requests, not just traffic on standard HTTP (`80`) and HTTPS (`443`) ports. This means all requests can now be filtered by [A/V scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/), [file sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/#data-in-transit), and more. 
 
-You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing _Inspect on all ports_.
+You can turn this [setting](/cloudflare-one/traffic-policies/network-policies/protocol-detection/#inspect-on-all-ports) on by going to **Settings** > **Network** > **Firewall** and choosing  _Inspect on all ports_.
 
 ![HTTP Inspection on all ports setting](~/assets/images/gateway/Gateway-Inspection-all-ports.png)
 
diff --git a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
index 85d54d9085242a7..99deeee7c9cf019 100644
--- a/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
+++ b/src/content/changelog/gateway/2025-07-28-Spam-domain-category-introduced.mdx
@@ -3,13 +3,15 @@ title: Scam domain category introduced under Security Threats
 description: You can now create policies specifically targeting the Scam content
 date: 2025-07-28
 ---
-
+ 
 We have introduced a new Security Threat category called **Scam**. Relevant domains are marked with the Scam category. Scam typically refers to fraudulent websites and schemes designed to trick victims into giving away money or personal information.
-
+ 
 **New category added**
 
-| Parent ID | Parent Name      | Category ID | Category Name |
-| --------- | ---------------- | ----------- | ------------- |
-| 21        | Security Threats | 191         | Scam          |
+
+| Parent ID | Parent Name           | Category ID | Category Name                 |
+| --------- | --------------------- | ----------- | ----------------------------- |
+| 21        | Security Threats      | 191          | Scam                |
+
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
index e4f36b80ddf1cbf..295f092f251e8cc 100644
--- a/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
+++ b/src/content/changelog/gateway/2025-08-15-gemini-application-replaces-bard.mdx
@@ -3,9 +3,8 @@ title: Google Bard Application replaced by Gemini
 description: The Google Bard application has been fully replaced with Gemini
 date: 2025-07-22
 ---
-
 The **Google Bard** application (ID: 1198) has been deprecated and fully removed from the system. It has been replaced by the **Gemini** application (ID: 1340).
-Any existing Gateway policies that reference the old Google Bard application will no longer function.
+Any existing Gateway policies that reference the old Google Bard application will no longer function. 
 To ensure your policies continue to work as intended, you should update them to use the new Gemini application.
 We recommend replacing all instances of the deprecated Bard application with the new Gemini application in your Gateway policies.
 For more information about application policies, please see the [Cloudflare Gateway documentation](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
index 450c765b4b0e122..0583881ed95d8cb 100644
--- a/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
+++ b/src/content/changelog/gateway/2025-10-10-new-domain-categories.mdx
@@ -8,10 +8,10 @@ We have added three new domain categories under the Technology parent category,
 
 **New categories added**
 
-| Parent ID | Parent Name | Category ID | Category Name       |
-| --------- | ----------- | ----------- | ------------------- |
-| 26        | Technology  | 194         | Keep Awake Software |
-| 26        | Technology  | 192         | Remote Access       |
-| 26        | Technology  | 193         | Shareware/Freeware  |
+| Parent ID | Parent Name           | Category ID | Category Name                 |
+| --------- | --------------------- | ----------- | ----------------------------- |
+| 26        | Technology            | 194         | Keep Awake Software           |
+| 26        | Technology            | 192         | Remote Access                 |
+| 26        | Technology            | 193         | Shareware/Freeware            |
 
 Refer to [Gateway domain categories](/cloudflare-one/traffic-policies/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
index 0d4496f7a95d1af..6ae683bd7093044 100644
--- a/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
+++ b/src/content/changelog/gateway/2025-11-06-Applications-recategorised-plan.mdx
@@ -4,15 +4,14 @@ description: We are preparing to remap some existing applications to better refl
 date: 2025-11-06
 ---
 
-We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28).
+We have previously added new application categories to better reflect their content and improve HTTP traffic management: refer to [Changelog](/cloudflare-one/changelog/gateway/#2025-10-28). 
 While the new categories are live now, we want to ensure you have ample time to review and adjust any existing rules you have configured against old categories.
 The remapping of existing applications into these new categories will be completed by January 30, 2026.
 This timeline allows you a dedicated period to:
-
 - Review the new category structure.
 - Identify any policies you have that target the older categories.
 - Adjust your rules to reference the new, more precise categories before the old mappings change.
-  Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
+Once the applications have been fully remapped by January 30, 2026, you might observe some changes in the traffic being mitigated or allowed by your existing policies. We encourage you to use the intervening time to prepare for a smooth transition.
 
 **Applications being remappedd**
 | Application Name | Existing Category | New Category |
@@ -77,4 +76,5 @@ This timeline allows you a dedicated period to:
 | DHL Express | Shopping | Business |
 | UPS | Shopping | Business |
 
+
 For more information on creating HTTP policies, refer to [Applications and app types](/cloudflare-one/traffic-policies/application-app-types/).
diff --git a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
index 25d0dbe1436d1fa..f20f7a3b16f224a 100644
--- a/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
+++ b/src/content/changelog/gateway/2026-02-27-new-protocol-detection-protocols.mdx
@@ -10,13 +10,13 @@ Gateway [Protocol Detection](/cloudflare-one/traffic-policies/network-policies/p
 
 | Protocol     | Notes                                              |
 | ------------ | -------------------------------------------------- |
-| IMAP         | Internet Message Access Protocol — email retrieval |
-| POP3         | Post Office Protocol v3 — email retrieval          |
-| SMTP         | Simple Mail Transfer Protocol — email sending      |
-| MYSQL        | MySQL database wire protocol                       |
-| RSYNC-DAEMON | rsync daemon protocol                              |
-| LDAP         | Lightweight Directory Access Protocol              |
-| NTP          | Network Time Protocol                              |
+| IMAP         | Internet Message Access Protocol — email retrieval  |
+| POP3         | Post Office Protocol v3 — email retrieval           |
+| SMTP         | Simple Mail Transfer Protocol — email sending       |
+| MYSQL        | MySQL database wire protocol                        |
+| RSYNC-DAEMON | rsync daemon protocol                               |
+| LDAP         | Lightweight Directory Access Protocol               |
+| NTP          | Network Time Protocol                               |
 
 These protocols join the existing set of detected protocols (HTTP, HTTP2, SSH, TLS, DCERPC, MQTT, and TPKT) and can be used with the _Detected Protocol_ selector in [Network policies](/cloudflare-one/traffic-policies/network-policies/) to identify and filter traffic based on the application-layer protocol, without relying on port-based identification.
 
diff --git a/src/content/changelog/gateway/Gateway-application-categories-added.mdx b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
index 2f049a7fb324a63..ec9c5e87eb92aa4 100644
--- a/src/content/changelog/gateway/Gateway-application-categories-added.mdx
+++ b/src/content/changelog/gateway/Gateway-application-categories-added.mdx
@@ -4,7 +4,7 @@ description: Manage outbound traffic with more granular application categories
 date: 2025-10-28
 ---
 
-To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product.
+To give you precision and flexibility while creating policies to block unwanted traffic, we are introducing new, more granular application categories in the Gateway product. 
 
 We have added the following categories to provide more precise organization and allow for finer-grained policy creation, designed around how users interact with different types of applications:
 
@@ -18,7 +18,7 @@ We have added the following categories to provide more precise organization and
 - Photography & Graphic Design
 - Travel
 
-The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories.
+The new categories are live now, but we are providing a transition period for existing applications to be fully remapped to these new categories. 
 
 The full remapping will be completed by January 30, 2026.
 
diff --git a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
index 05c67dbc7fb82e7..3266a97d34dcdcb 100644
--- a/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
+++ b/src/content/changelog/hyperdrive/2025-12-04-hyperdrive-remote-database-local-dev.mdx
@@ -13,13 +13,13 @@ The `localConnectionString` field and `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_ST
 
 ```jsonc
 {
-	"hyperdrive": [
-		{
-			"binding": "HYPERDRIVE",
-			"id": "your-hyperdrive-id",
-			"localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require",
-		},
-	],
+  "hyperdrive": [
+    {
+      "binding": "HYPERDRIVE",
+      "id": "your-hyperdrive-id",
+      "localConnectionString": "postgres://user:password@remote-host.example.com:5432/database?sslmode=require"
+    }
+  ]
 }
 ```
 
diff --git a/src/content/changelog/images/heic-support.mdx b/src/content/changelog/images/heic-support.mdx
index 3baf6ce9372089c..8e5f655340c4c12 100644
--- a/src/content/changelog/images/heic-support.mdx
+++ b/src/content/changelog/images/heic-support.mdx
@@ -3,7 +3,6 @@ title: HEIC support in Cloudflare Images
 description: You can use Images to ingest HEIC images
 date: 2025-07-08
 ---
-
 You can use Images to ingest HEIC images and serve them in supported output formats like AVIF, WebP, JPEG, and PNG.
 
 When inputting a HEIC image, dimension and sizing limits may still apply. Refer to our documentation to see limits for [uploading to Images](/images/storage/upload-images/methods/) or [transforming a remote image](/images/optimization/transformations/overview/).
diff --git a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
index 6cf9d6cc44b1683..8124fd2d6475783 100644
--- a/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
+++ b/src/content/changelog/kv/2025-08-22-kv-performance-improvements.mdx
@@ -16,3 +16,5 @@ The new hybrid architecture delivers substantial latency reductions throughout E
 
 - **p95 latency**: Reduced from ~150ms to ~50ms (67% decrease)
 - **p99 latency**: Reduced from ~350ms to ~250ms (29% decrease)
+
+
diff --git a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
index d1a8fedd27fa065..41b68f6e7a4c23d 100644
--- a/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
+++ b/src/content/changelog/load-balancing/2025-06-04-account-load-balancing-ui.mdx
@@ -5,7 +5,6 @@ date: 2025-06-04
 ---
 
 We've made two large changes to load balancing:
-
 - Redesigned the user interface, now centralized at the **account level**.
 - Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot.
 
@@ -16,11 +15,13 @@ This update streamlines how you manage load balancers across multiple zones and
 **Key Enhancements:**
 
 - **Account-Level UI Consolidation:**
+
   - **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level.
 
   - **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution.
 
 - **Private Network Load Balancing:**
+
   - **Secure Internal Application Access:** Create [**Private Load Balancers**](/load-balancing/private-network/) to distribute traffic to applications hosted within your private network, ensuring they are not exposed to the public Internet.
 
   - **WARP & Magic WAN Integration:** Effortlessly direct internal traffic from users connected via Cloudflare WARP or through your Magic WAN infrastructure to the appropriate internal endpoint pools.
diff --git a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
index 62de99fae3dc892..3a0234e53c4e96e 100644
--- a/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
+++ b/src/content/changelog/log-explorer/2025-07-09-usage-tracking.mdx
@@ -6,4 +6,4 @@ date: 2025-07-09
 
 [Log Explorer](/log-explorer/) customers can now monitor their data ingestion volume to keep track of their billing. Monthly usage is displayed at the top of the [Log Search](/log-explorer/log-search/) and [Manage Datasets](/log-explorer/manage-datasets/) screens in Log Explorer.
 
-![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
+![Ingested data](src/assets/images/changelog/log-explorer/ingested-data.png)
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
index c384730c331df3f..02585abcdaa5285 100644
--- a/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
+++ b/src/content/changelog/log-explorer/2025-08-15-extended-retention.mdx
@@ -6,4 +6,4 @@ date: 2025-08-15
 
 Customers can now rely on Log Explorer to meet their log retention compliance requirements.
 
-Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
+Contract customers can choose to store their logs in Log Explorer for up to two years, at an additional cost of $0.10 per GB per month. Customers interested in this feature can contact their account team to have it added to their contract.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
index bd9895c6bf2de02..c1d5c1454d91cdf 100644
--- a/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
+++ b/src/content/changelog/log-explorer/2025-09-03-log-headers-and-cookies.mdx
@@ -11,3 +11,5 @@ Create a custom field to log desired header or cookie values into the `http_requ
 ![Edit Custom fields](src/assets/images/changelog/log-explorer/edit-custom-fields.png)
 
 For more details, refer to [Headers and cookies](/log-explorer/log-search/#headers-and-cookies).
+
+
diff --git a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
index a75aa1ccc71be40..794a2ac99ef2c6c 100644
--- a/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-contextual-pivots.mdx
@@ -4,7 +4,7 @@ description: Log Search now lets you pivot directly to related Cloudflare tools
 date: 2025-09-11
 ---
 
-Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation.
+Directly from [Log Search](/log-explorer/log-search/) results, customers can pivot to other parts of the Cloudflare dashboard to immediately take action as a result of their investigation. 
 
 From the `http_requests` or `fw_events` dataset results, right click on an IP Address or JA3 Fingerprint to pivot to the Investigate portal to lookup the reputation of an IP address or JA3 fingerprint.
 
@@ -14,6 +14,6 @@ Easily learn about error codes by linking directly to our documentation from the
 
 ![View documentation](src/assets/images/changelog/log-explorer/view-documentation.png)
 
-From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy.
+From the `gateway_http` dataset, click on a **policyid** to link directly to the Zero Trust dashboard to review or make changes to a specific Gateway policy. 
 
 ![View policy](src/assets/images/changelog/log-explorer/policyid.png)
diff --git a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
index 9747dcb5ea70714..915ab5b7a8c0a8a 100644
--- a/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
+++ b/src/content/changelog/log-explorer/2025-09-11-new-results-table-view.mdx
@@ -9,6 +9,6 @@ The results table view of **Log Search** has been updated with additional functi
 - Remove/add columns.
 - Resize columns.
 - Sort columns.
-- Copy values from any field.
+- Copy values from any field. 
 
-![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
+![New results table view](src/assets/images/changelog/log-explorer/new-table.png)
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
index 7fc5df7c52c3f95..8a5f4b9954eb85f 100644
--- a/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
+++ b/src/content/changelog/log-explorer/2025-11-04-query-cancellation.mdx
@@ -6,4 +6,4 @@ date: 2025-11-04
 
 We're excited to announce that Log Explorer users can now cancel queries that are currently running.
 
-This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
+This new feature addresses a common pain point: waiting for a long, unintended, or misconfigured query to complete before you can submit a new, correct one. With query cancellation, you can immediately stop the execution of any undesirable query, allowing you to quickly craft and submit a new query, significantly improving your investigative workflow and productivity within Log Explorer.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
index 4abf8c6cf36fdee..6808c2b7ad9372e 100644
--- a/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
+++ b/src/content/changelog/log-explorer/2025-11-11-resize-sql-window.mdx
@@ -8,4 +8,4 @@ We're excited to announce a quality-of-life improvement for Log Explorer users.
 
 Previously, if you were writing a long custom SQL query, the fixed-size window required excessive scrolling to view the full query. This update allows you to easily drag the bottom edge of the query window to make it taller. This means you can view your entire custom query at once, improving the efficiency and experience of writing and debugging complex queries.
 
-To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
+To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/).
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
index 20d9cb72a336e55..012bc9566a75154 100644
--- a/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-fixed-custom-date.mdx
@@ -6,4 +6,4 @@ date: 2025-11-13
 
 We've resolved a bug in Log Explorer that caused inconsistencies between the custom SQL date field filters and the date picker dropdown. Previously, users attempting to filter logs based on a custom date field via a SQL query sometimes encountered unexpected results or mismatching dates when using the interactive date picker.
 
-This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
+This fix ensures that the custom SQL date field filters now align correctly with the selection made in the date picker dropdown, providing a reliable and predictable filtering experience for your log data. This is particularly important for users creating custom log views based on time-sensitive fields.
\ No newline at end of file
diff --git a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
index b3d870198ed0514..eaa4f6d50ecf078 100644
--- a/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
+++ b/src/content/changelog/log-explorer/2025-11-13-new-datasets.mdx
@@ -18,6 +18,7 @@ The newly supported datasets include:
 - `Spectrum_events`
 - `Zaraz_events`
 
+
 ## Account Level
 
 - `Audit Logs`
@@ -30,8 +31,9 @@ The newly supported datasets include:
 - `Sinkhole HTTP`
 - `ipsec_logs`
 
+
 :::note
-`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying.
+`Auditlog` and `Auditlog_v2` datasets require `audit-log.read` permission for querying. 
 
 The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` role for querying.
 :::
@@ -41,3 +43,4 @@ The `biso_user_actions` dataset requires either the `Super Admin` or `ZT PII` ro
 You can now use Log Explorer to query and filter with each of these datasets. For example, you can identify an IP address exhibiting suspicious behavior in the `FW_event` logs, and then instantly pivot to the `Network Analytics` logs or `Access` logs to see its network-level traffic profile or if it bypassed a corporate policy.
 
 To learn more and get started, refer to the [Log Explorer documentation](/log-explorer/) and the [Cloudflare Logs documentation](/logs/).
+
diff --git a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
index 866a7fd1ae4efd5..305f5dc7bb195af 100644
--- a/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
+++ b/src/content/changelog/log-explorer/2026-03-11-ingest-field-selection.mdx
@@ -21,16 +21,16 @@ When configuring a dataset via the dashboard or API, you can define a specific s
 
 ```json
 {
-	"dataset": "firewall_events",
-	"enabled": true,
-	"fields": [
-		"Timestamp",
-		"ClientRequestHost",
-		"ClientIP",
-		"Action",
-		"EdgeResponseStatus",
-		"OriginResponseStatus"
-	]
+  "dataset": "firewall_events",
+  "enabled": true,
+  "fields": [
+    "Timestamp",
+    "ClientRequestHost",
+    "ClientIP",
+    "Action",
+    "EdgeResponseStatus",
+    "OriginResponseStatus"
+  ]
 }
 ```
 
diff --git a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
index 67a64c6fcf983b4..5c89e845304dd52 100644
--- a/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
+++ b/src/content/changelog/logs/2024-10-08-new-gateway-fields.mdx
@@ -8,4 +8,4 @@ Cloudflare has introduced new fields to two Gateway-related datasets in Cloudfla
 
 - **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`.
 
-- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
+- **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`.
\ No newline at end of file
diff --git a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
index e21ad4b2e7c9787..05e75fb1d124a1b 100644
--- a/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
+++ b/src/content/changelog/logs/2026-03-09-log-fields-updated.mdx
@@ -24,3 +24,4 @@ Cloudflare has added new fields across multiple [Logpush datasets](/logs/logpush
 - **Zero Trust Network Session Logs**: `SNI`.
 
 For the complete field definitions for each dataset, refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/).
+
diff --git a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
index f5a502289149705..0bcd5c49fa1c601 100644
--- a/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
+++ b/src/content/changelog/logs/2026-04-20-pipelines-logpush-destination.mdx
@@ -31,4 +31,4 @@ Pipelines SQL supports string functions, regex, hashing, JSON extraction, timest
 
 ## Get started
 
-To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
+To configure Pipelines as a Logpush destination, refer to [Enable Cloudflare Pipelines](/logs/logpush/logpush-job/enable-destinations/pipelines/).
\ No newline at end of file
diff --git a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
index 322bbb2f1f6d38d..451556a3ef70408 100644
--- a/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
+++ b/src/content/changelog/logs/2026-04-21-logpush-subrequests-merging.mdx
@@ -7,15 +7,13 @@ date: 2026-04-21
 When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request. With subrequest merging enabled, subrequest data is embedded as a nested array field on the parent log record instead.
 
 ### What's new
-
 - New subrequest_merging field on Logpush jobs — Set "merge_subrequests": true when creating or updating an http_requests Logpush job to enable the feature.
 - New Subrequests log field — When subrequest merging is enabled, a Subrequests field (`array\<object\>`) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.
 
 ### Limitations
-
 - Applies to the http_requests (zone-scoped) dataset only.
 - A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.
 - Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.
 - Subrequests that do not qualify appear as separate log entries — no data is lost.
 - Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.
-- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
+- For more information, refer to [Subrequests](/logs/logpush/logpush-job/subrequests/).
\ No newline at end of file
diff --git a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
index 3e32c36dcd09c10..7513b6b2b18466c 100644
--- a/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
+++ b/src/content/changelog/network-interconnect/2026-03-24-interconnects-navigation-update.mdx
@@ -6,4 +6,4 @@ date: 2026-03-24
 
 The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** > **Interconnects**.
 
-Your existing configurations and functionality remain the same.
+Your existing configurations and functionality remain the same.
\ No newline at end of file
diff --git a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
index 5bbd423dd5f10bf..e11320f25ae558b 100644
--- a/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
+++ b/src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx
@@ -12,4 +12,4 @@ If you are creating a new Pages project, the new V3 build image that includes No
 
 Note that you can always specify a particular version of Node.js or other built-in dependencies by [setting an environment variable](/pages/configuration/build-image/#override-default-versions).
 
-For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
+For more, refer to the [developer docs for Cloudflare Pages builds](/pages/configuration/build-image)
\ No newline at end of file
diff --git a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
index c3385ca2e92c7dd..21d1fa8ffb558fc 100644
--- a/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
+++ b/src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx
@@ -8,12 +8,11 @@ date: 2025-03-27 12:00:00 UTC
 
 [Queues](/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:
 
-- Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
-- You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
-- Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
+* Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
+* You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
+* Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
 
 To pause a queue using [Wrangler](/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.
-
 ```bash title="Pause and resume a queue"
 $ wrangler queues pause-delivery my-queue
 Pausing message delivery for queue my-queue.
@@ -25,7 +24,6 @@ Resumed message delivery for queue my-queue.
 ```
 
 Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:
-
 ```bash title="Purge a queue"
 $ wrangler queues purge my-queue
 ✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue
diff --git a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
index f3d5e6d4def673d..f8a980ffedaf040 100644
--- a/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
+++ b/src/content/changelog/queues/2025-04-17-pull-consumer-limits.mdx
@@ -11,16 +11,13 @@ date: 2025-04-17 12:00:00 UTC
 Pull consumers allow you to consume messages over HTTP from any environment—including outside of [Cloudflare Workers](/workers). They’re also useful when you need fine-grained control over how quickly messages are consumed.
 
 To setup a new queue with a pull based consumer using [Wrangler](/workers/wrangler/), run:
-
 ```sh title="Create a queue with a pull based consumer"
 npx wrangler queues create my-queue
 npx wrangler queues consumer http add my-queue
 ```
-
 You can also configure a pull consumer using the [REST API](/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.
 
 Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:
-
 ```bash title="Pull messages from a queue"
 curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" \
 --header "Authorization: Bearer ${API_TOKEN}" \
diff --git a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
index 7cec3511f215302..c7afb7767b23bb4 100644
--- a/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
+++ b/src/content/changelog/queues/2025-05-09-publish-to-queues-via-http.mdx
@@ -19,4 +19,4 @@ curl "https://api.cloudflare.com/client/v4/accounts/<account_id>/queues/<queue_i
 
 You can also use our [SDKs](/fundamentals/api/reference/sdks/) for TypeScript, Python, and Go.
 
-To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
+To get started with HTTP publishing, check out our [step-by-step example](/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](/api/resources/queues/subresources/messages/methods/push/).
\ No newline at end of file
diff --git a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
index 2ad33c340181762..cd3df4c25c12a32 100644
--- a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
+++ b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx
@@ -22,21 +22,21 @@ An event is a structured record of something happening in your Cloudflare accoun
 
 ```json title="Example R2 bucket created event"
 {
-	"type": "cf.r2.bucket.created",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"location": "WNAM"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventTimestamp": "2025-07-28T10:30:00Z"
-	}
+  "type": "cf.r2.bucket.created",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "location": "WNAM"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventTimestamp": "2025-07-28T10:30:00Z"
+  }
 }
 ```
 
 Current [event sources](/queues/event-subscriptions/events-schemas/) include [R2](/r2/), [Workers KV](/kv/), [Workers AI](/workers-ai/), [Workers Builds](/workers/ci-cd/builds/), [Vectorize](/vectorize/), [Super Slurper](/r2/data-migration/super-slurper/), and [Workflows](/workflows/). More sources and events are on the way.
 
-For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
+For more information on event subscriptions, available events, and how to get started, refer to our [documentation](/queues/event-subscriptions/).
\ No newline at end of file
diff --git a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
index 965d8f2e1ebbc40..4e3338c452ffb31 100644
--- a/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
+++ b/src/content/changelog/r2-sql/2025-09-25-announcing-r2-sql-open-beta.mdx
@@ -7,7 +7,7 @@ products:
 hidden: false
 ---
 
-import { LinkCard } from "~/components";
+import { LinkCard} from "~/components";
 
 Today, we're launching the **open beta** for [R2 SQL](/r2-sql/): A serverless, distributed query engine that can efficiently analyze petabytes of data in [Apache Iceberg](https://iceberg.apache.org/) tables managed by [R2 Data Catalog](/r2/data-catalog).
 
diff --git a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
index 55b2b18066b5d26..6ebf2f9f66bcf2e 100644
--- a/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
+++ b/src/content/changelog/r2-sql/2026-03-23-expanded-sql-functions-expressions-complex-types.mdx
@@ -8,6 +8,7 @@ date: 2026-03-23
 
 [R2 SQL](/r2-sql/) now supports an expanded SQL grammar so you can write richer analytical queries without exporting data. This release adds CASE expressions, column aliases, arithmetic in clauses, 163 scalar functions, 33 aggregate functions, EXPLAIN, Common Table Expressions (CTEs),and full struct/array/map access. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying [Apache Iceberg](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](/r2/data-catalog/). This page documents the supported SQL syntax.
 
+
 ## Highlights
 
 - **Column aliases** — `SELECT col AS alias` now works in all clauses
diff --git a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
index 8be0bd3a266e62c..f6fc972ca48a3f5 100644
--- a/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
+++ b/src/content/changelog/r2-sql/2026-04-20-r2-sql-json-functions-explain-format.mdx
@@ -20,7 +20,6 @@ SELECT
 FROM my_namespace.sales_data
 WHERE json_contains(doc, 'email')
 ```
-
 For a full list of available functions, refer to [JSON functions](/r2-sql/sql-reference/scalar-functions/#json-functions).
 
 `EXPLAIN FORMAT JSON` returns query execution plans as structured JSON for programmatic analysis and observability integrations:
@@ -67,7 +66,6 @@ npx wrangler r2 sql query "${WAREHOUSE}" "EXPLAIN FORMAT JSON SELECT * FROM logp
 │ }                                    │
 └──────────────────────────────────────┘
 ```
-
 For more details, refer to [EXPLAIN](/r2-sql/sql-reference/#explain).
 
 Unpartitioned Iceberg tables can now be queried directly, which is useful for smaller datasets or data without natural time dimensions. For tables with more than 1000 files, partitioning is still recommended for better performance.
diff --git a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
index 73516e563584422..3a0934b0df07041 100644
--- a/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
+++ b/src/content/changelog/radar/2025-08-04-radar-ct-insights.mdx
@@ -35,4 +35,4 @@ For the `summary` and `timeseries_groups` endpoints, the following dimensions ar
 - `tld`: Top-level domain for DNS names found in certificates SANs
 - `validation_level`: [Validation level](https://www.cloudflare.com/learning/ssl/types-of-ssl-certificates/)
 
-Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
+Check out the new Certificate Transparency insights in the [new Radar page](https://radar.cloudflare.com/certificate-transparency).
\ No newline at end of file
diff --git a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
index 702f6495af2db32..2204d6097ae38bf 100644
--- a/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
+++ b/src/content/changelog/radar/2025-09-29-radar-regional-data.mdx
@@ -18,4 +18,4 @@ All `summary` and `timeseries_groups` endpoints in [`HTTP`](/api/resources/radar
 
 A new filter `geoId` was also added to all endpoints in [`HTTP`](/api/resources/radar/subresources/http/) and [`NetFlows`](/api/resources/radar/subresources/netflows/), allowing filtering by a specific administrative division.
 
-Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
+Check out the new Regional traffic insights on a country specific traffic page [new Radar page](https://radar.cloudflare.com/traffic/pt).
\ No newline at end of file
diff --git a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
index 1da325fa4aeeaef..3058add7fdc87a1 100644
--- a/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
+++ b/src/content/changelog/radar/2026-02-25-radar-aspa-insights.mdx
@@ -34,4 +34,4 @@ On AS routing pages, the connectivity table now includes checkmarks for ASPA-ver
 
 ![Screenshot of the ASPA changes timeline on an AS routing page](~/assets/images/radar/aspa-asn-timeline.png)
 
-Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
+Check out the [Radar routing page](https://radar.cloudflare.com/routing) to explore the data.
\ No newline at end of file
diff --git a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
index 190b32137ec4b34..b2c0e9bbf120e31 100644
--- a/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
+++ b/src/content/changelog/radar/2026-04-01-radar-routing-section.mdx
@@ -34,4 +34,4 @@ The [IP address space](https://radar.cloudflare.com/routing) chart now displays
 
 ![Screenshot of the IPv4 and IPv6 combined IP space chart](~/assets/images/radar/combined-ipv4-ipv6-space.png)
 
-Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
+Check out the [Radar routing section](https://radar.cloudflare.com/routing) to explore the data, and stay tuned for more routing insights coming soon.
\ No newline at end of file
diff --git a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
index 9ab71e94e48955a..0ccd16da2716380 100644
--- a/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
+++ b/src/content/changelog/realtime/2026-05-28-realtimekit-track-recording.mdx
@@ -28,7 +28,7 @@ To pass `user_ids` for selective track recording, use the following minimum SDK
 - Android Core or iOS Core: version `2.0.0` or later
 - Android UI Kit or iOS UI Kit: version `1.1.0` or later
 
-[RealtimeKit](/realtime/realtimekit/) provides SDKs and UI components so that you can build your own meeting experience on Cloudflare's [global WebRTC infrastructure](https://toxicitymax-rtk-track-recording.preview.developers.cloudflare.com/realtime/#realtime-sfu). Teams today build products ranging from telehealth to education on RealtimeKit for global audiences. You can get started today with our [Quickstart](/realtime/realtimekit/quickstart/) or take a look at our [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
+[RealtimeKit](/realtime/realtimekit/) provides SDKs and UI components so that you can build your own meeting experience on Cloudflare's [global WebRTC infrastructure](/realtime/#realtime-sfu). Teams today build products ranging from telehealth to education on RealtimeKit for global audiences. You can get started today with our [Quickstart](/realtime/realtimekit/quickstart/) or take a look at our [Cloudflare Meet repo](https://github.com/cloudflare/meet) as a reference.
 
 - [Track recording docs](/realtime/realtimekit/recording-guide/track-recording/)
 - [RealtimeKit Quickstart](/realtime/realtimekit/quickstart/)
diff --git a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
index 4bdd9ba554b4731..a57aa1f4b10d63e 100644
--- a/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
+++ b/src/content/changelog/risk-score/2026-1-15-crowdstrike-score.mdx
@@ -10,7 +10,6 @@ Administrators can now automatically escalate the risk score of a user if their
 
 New risk behaviors
 The following risk scoring behaviors are now available:
-
 - CrowdStrike low device score: Automatically increases a user's risk score when the connected device reports a "Low" score from CrowdStrike.
 - CrowdStrike medium device score: Automatically increases a user's risk score when the connected device reports a "Medium" score from CrowdStrike.
 
diff --git a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
index 1ade4db9cf454f6..629804f5f46a6f4 100644
--- a/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
+++ b/src/content/changelog/rules/2025-10-30-tcp-rtt-and-tcp-fields.mdx
@@ -12,10 +12,10 @@ Cloudflare now provides two new request fields in the Ruleset engine that let yo
 
 ### New fields
 
-| Field                            | Type    | Description                                                                                                                                                          |
-| -------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.edge.client_tcp`             | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC.                                                        |
-| `cf.timings.client_tcp_rtt_msec` | Number  | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
+| Field | Type | Description |
+| --- | --- | --- |
+| `cf.edge.client_tcp` | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC. |
+| `cf.timings.client_tcp_rtt_msec` | Number | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
 
 Example filter expression:
 
diff --git a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
index 21cdd6b6e931809..97bc5ce82abd556 100644
--- a/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
+++ b/src/content/changelog/rules/2026-01-12-dma-metro-code-field.mdx
@@ -10,8 +10,8 @@ You can use this field to build rules that target traffic based on geographic ma
 
 ### Field details
 
-| Field               | Type           | Description                                                                                                                   |
-| ------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `ip.src.metro_code` | String \| null | The metro code (DMA) of the incoming request's IP address. Returns the designated market area code for the client's location. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
index 598cf65b45365a7..9fa9ac345fef774 100644
--- a/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
+++ b/src/content/changelog/rules/2026-01-20-array-map-functions.mdx
@@ -12,12 +12,12 @@ Cloudflare Rulesets now include new functions that enable advanced expression lo
 
 ### New functions
 
-| Function                   | Description                                                                   |
-| -------------------------- | ----------------------------------------------------------------------------- |
-| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter.       |
-| `join(array, delimiter)`   | Joins an array of strings into a single string using the specified delimiter. |
-| `has_key(map, key)`        | Returns `true` if the specified key exists in the map.                        |
-| `has_value(map, value)`    | Returns `true` if the specified value exists in the map.                      |
+| Function | Description |
+| --- | --- |
+| `split(source, delimiter)` | Splits a string into an array of strings using the specified delimiter. |
+| `join(array, delimiter)` | Joins an array of strings into a single string using the specified delimiter. |
+| `has_key(map, key)` | Returns `true` if the specified key exists in the map. |
+| `has_value(map, value)` | Returns `true` if the specified value exists in the map. |
 
 ---
 
diff --git a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
index 5dcd031a6e4ba0b..9e980cd5968d3b0 100644
--- a/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
+++ b/src/content/changelog/rules/2026-01-27-body-buffering-settings.mdx
@@ -10,20 +10,20 @@ You can now control how Cloudflare buffers HTTP request and response bodies usin
 
 Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:
 
-| Mode                   | Behavior                                                                                                      |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Mode | Behavior |
+| --- | --- |
 | **Standard** (default) | Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management. |
-| **Full**               | Buffers the entire request body before sending to origin.                                                     |
-| **None**               | No buffering — the request body streams directly to origin without inspection.                                |
+| **Full** | Buffers the entire request body before sending to origin. |
+| **None** | No buffering — the request body streams directly to origin without inspection. |
 
 ### Response body buffering
 
 Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:
 
-| Mode                   | Behavior                                                                            |
-| ---------------------- | ----------------------------------------------------------------------------------- |
-| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality.     |
-| **None**               | No buffering — the response body streams directly to the client without inspection. |
+| Mode | Behavior |
+| --- | --- |
+| **Standard** (default) | Cloudflare can inspect a prefix of the response body for enabled functionality. |
+| **None** | No buffering — the response body streams directly to the client without inspection. |
 
 :::caution
 Setting body buffering to **None** may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.
@@ -33,11 +33,11 @@ Setting body buffering to **None** may break security functionality that require
 
 ```json
 {
-	"action": "set_config",
-	"action_parameters": {
-		"request_body_buffering": "standard",
-		"response_body_buffering": "none"
-	}
+  "action": "set_config",
+  "action_parameters": {
+    "request_body_buffering": "standard",
+    "response_body_buffering": "none"
+  }
 }
 ```
 
diff --git a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
index 04fd03621cb1999..52e81f07114dcef 100644
--- a/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
+++ b/src/content/changelog/rules/2026-03-18-worker-timing-field.mdx
@@ -10,8 +10,8 @@ You can use this field to identify slow Worker executions, detect performance re
 
 ### Field details
 
-| Field                    | Type    | Description                                                                                         |
-| ------------------------ | ------- | --------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `cf.timings.worker_msec` | Integer | The time spent executing a Cloudflare Worker in milliseconds. Returns `0` if no Worker was invoked. |
 
 Example filter expression:
diff --git a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
index c2584a81e336dae..f2a0c12b6257543 100644
--- a/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/rules/2026-03-25-rfc9440-mtls-fields.mdx
@@ -43,6 +43,6 @@ You should ensure that `Client-Cert` and `Client-Cert-Chain` headers received by
 
 - **If you use WAF custom rules to block requests with invalid mTLS connections:** The transform rule is sufficient. For all requests that reach your origin server, the rule will overwrite any existing `Client-Cert` and `Client-Cert-Chain` headers.
 - **If you do not enforce mTLS at the WAF:** Add another transform rule that removes any incoming `Client-Cert` and `Client-Cert-Chain` headers from all requests (use expression `true`), ordered before the rule above. This ensures your origin server cannot receive client-supplied values for these HTTP headers.
-  :::
+:::
 
 For more information, refer to [Mutual TLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/), [Request Header Transform Rules](/rules/transform/request-header-modification/), and the [fields reference](/ruleset-engine/rules-language/fields/reference/).
diff --git a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
index 92228ab4dd7a5fd..2954caaf3ad34d3 100644
--- a/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/rules/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,10 +10,10 @@ Previously, QUIC RTT and delivery rate data was only available via the `Server-T
 
 ### New fields
 
-| Field                             | Type    | Description                                                                                                                                                               |
-| --------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Field | Type | Description |
+| --- | --- | --- |
 | `cf.timings.client_quic_rtt_msec` | Integer | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only populated for QUIC (HTTP/3) connections. Returns `0` for TCP connections. |
-| `cf.edge.l4.delivery_rate`        | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request.             |
+| `cf.edge.l4.delivery_rate` | Integer | The most recent data delivery rate estimate for the client connection, in bytes per second. Returns `0` when L4 statistics are not available for the request. |
 
 ### Example: Route slow connections to a lightweight origin
 
@@ -27,9 +27,9 @@ cf.timings.client_tcp_rtt_msec > 200 or cf.timings.client_quic_rtt_msec > 200
 
 **Header modifications:**
 
-| Operation | Header name      | Value  |
-| --------- | ---------------- | ------ |
-| Set       | `X-High-Latency` | `true` |
+| Operation | Header name | Value |
+| --- | --- | --- |
+| Set | `X-High-Latency` | `true` |
 
 ### Example: Match low-bandwidth connections
 
diff --git a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
index 89121e503ad9af2..9ee69fcc0ccb9c9 100644
--- a/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-01-20-cloudflare-typescript-v6.0.0-beta.1.mdx
@@ -21,7 +21,6 @@ Please ensure you read through the list of changes below before moving to this v
 ### Breaking Changes
 
 #### Addressing - Parameter Requirements Changed
-
 - `BGPPrefixCreateParams.cidr`: optional → **required**
 - `PrefixCreateParams.asn`: `number | null` → `number`
 - `PrefixCreateParams.loa_document_id`: required → **optional**
@@ -29,26 +28,21 @@ Please ensure you read through the list of changes below before moving to this v
 - `ServiceBindingCreateParams.service_id`: optional → **required**
 
 #### API Gateway
-
 - `ConfigurationUpdateResponse` removed
 - `PublicSchema` → `OldPublicSchema`
 - `SchemaUpload` → `UserSchemaCreateResponse`
 - `ConfigurationUpdateParams.properties` removed; use `normalize`
 
 #### CloudforceOne - Response Type Changes
-
 - `ThreatEventBulkCreateResponse`: `number` → complex object with counts and errors
 
 #### D1 Database - Query Parameters
-
 - `DatabaseQueryParams`: simple interface → union type (`D1SingleQuery | MultipleQueries`)
 - `DatabaseRawParams`: same change
 - Supports batch queries via `batch` array
 
 #### DNS Records - Type Renames (21 types)
-
 All record type interfaces renamed from `*Record` to short names:
-
 - `RecordResponse.ARecord` → `RecordResponse.A`
 - `RecordResponse.AAAARecord` → `RecordResponse.AAAA`
 - `RecordResponse.CNAMERecord` → `RecordResponse.CNAME`
@@ -72,64 +66,52 @@ All record type interfaces renamed from `*Record` to short names:
 - `RecordResponse.OpenpgpkeyRecord` → `RecordResponse.Openpgpkey`
 
 #### IAM Resource Groups
-
 - `ResourceGroupCreateResponse.scope`: optional single → **required array**
 - `ResourceGroupCreateResponse.id`: optional → **required**
 
 #### Origin CA Certificates - Parameter Requirements Changed
-
 - `OriginCACertificateCreateParams.csr`: optional → **required**
 - `OriginCACertificateCreateParams.hostnames`: optional → **required**
 - `OriginCACertificateCreateParams.request_type`: optional → **required**
 
 #### Pages
-
 - Renamed: `DeploymentsSinglePage` → `DeploymentListResponsesV4PagePaginationArray`
 - Domain response fields: many optional → **required**
 
 #### Pipelines - v0 to v1 Migration
-
 - Entire v0 API deprecated; use v1 methods (`createV1`, `listV1`, etc.)
 - New sub-resources: `Sinks`, `Streams`
 
 #### R2
-
 - `EventNotificationUpdateParams.rules`: optional → **required**
 - Super Slurper: `bucket`, `secret` now required in source params
 
 #### Radar
-
 - `dataSource`: `string` → typed enum (23 values)
 - `eventType`: `string` → typed enum (6 values)
 - V2 methods require `dimension` parameter (breaking signature change)
 
 #### Resource Sharing
-
 - Removed: `status_message` field from all recipient response types
 
 #### Schema Validation
-
 - Consolidated `SchemaCreateResponse`, `SchemaListResponse`, `SchemaEditResponse`, `SchemaGetResponse` → `PublicSchema`
 - Renamed: `SchemaListResponsesV4PagePaginationArray` → `PublicSchemasV4PagePaginationArray`
 
 #### Spectrum
-
 - Renamed union members: `AppListResponse.UnionMember0` → `SpectrumConfigAppConfig`
 - Renamed union members: `AppListResponse.UnionMember1` → `SpectrumConfigPaygoAppConfig`
 
 #### Workers
-
 - Removed: `WorkersBindingKindTailConsumer` type (all occurrences)
 - Renamed: `ScriptsSinglePage` → `ScriptListResponsesSinglePage`
 - Removed: `DeploymentsSinglePage`
 
 #### Zero-Trust DLP
-
 - `datasets.create()`, `update()`, `get()` return types changed
 - `PredefinedGetResponse` union members renamed to `UnionMember0-5`
 
 #### Zero-Trust Tunnels
-
 - Removed: `CloudflaredCreateResponse`, `CloudflaredListResponse`, `CloudflaredDeleteResponse`, `CloudflaredEditResponse`, `CloudflaredGetResponse`
 - Removed: `CloudflaredListResponsesV4PagePaginationArray`
 
@@ -138,30 +120,25 @@ All record type interfaces renamed from `*Record` to short names:
 ### Features
 
 #### Abuse Reports (`client.abuseReports`)
-
 - **Reports**: `create`, `list`, `get`
 - **Mitigations**: sub-resource for abuse mitigations
 
 #### AI Search (`client.aisearch`)
-
 - **Instances**: `create`, `update`, `list`, `delete`, `read`, `stats`
 - **Items**: `list`, `get`
 - **Jobs**: `create`, `list`, `get`, `logs`
 - **Tokens**: `create`, `update`, `list`, `delete`, `read`
 
 #### Connectivity (`client.connectivity`)
-
 - **Directory Services**: `create`, `update`, `list`, `delete`, `get`
 - Supports IPv4, IPv6, dual-stack, and hostname configurations
 
 #### Organizations (`client.organizations`)
-
 - **Organizations**: `create`, `update`, `list`, `delete`, `get`
 - **OrganizationProfile**: `update`, `get`
 - Hierarchical organization support with parent/child relationships
 
 #### R2 Data Catalog (`client.r2DataCatalog`)
-
 - **Catalog**: `list`, `enable`, `disable`, `get`
 - **Credentials**: `create`
 - **MaintenanceConfigs**: `update`, `get`
@@ -170,7 +147,6 @@ All record type interfaces renamed from `*Record` to short names:
 - Apache Iceberg integration
 
 #### Realtime Kit (`client.realtimeKit`)
-
 - **Apps**: `get`, `post`
 - **Meetings**: `create`, `get`, participant management
 - **Livestreams**: 10+ methods for streaming
@@ -181,66 +157,52 @@ All record type interfaces renamed from `*Record` to short names:
 - **Analytics**: organization analytics
 
 #### Token Validation (`client.tokenValidation`)
-
 - **Configuration**: `create`, `list`, `delete`, `edit`, `get`
 - **Credentials**: `update`
 - **Rules**: `create`, `list`, `delete`, `bulkCreate`, `bulkEdit`, `edit`, `get`
 - JWT validation with RS256/384/512, PS256/384/512, ES256, ES384
 
 #### Alerting Silences (`client.alerting.silences`)
-
 - `create`, `update`, `list`, `delete`, `get`
 
 #### IAM SSO (`client.iam.sso`)
-
 - `create`, `update`, `list`, `delete`, `get`, `beginVerification`
 
 #### Pipelines v1 (`client.pipelines`)
-
 - **Sinks**: `create`, `list`, `delete`, `get`
 - **Streams**: `create`, `update`, `list`, `delete`, `get`
 
 #### Zero-Trust AI Controls / MCP (`client.zeroTrust.access.aiControls.mcp`)
-
 - **Portals**: `create`, `update`, `list`, `delete`, `read`
 - **Servers**: `create`, `update`, `list`, `delete`, `read`, `sync`
 
 #### Accounts
-
 - `managed_by` field with `parent_org_id`, `parent_org_name`
 
 #### Addressing LOA Documents
-
 - `auto_generated` field on `LOADocumentCreateResponse`
 
 #### Addressing Prefixes
-
 - `delegate_loa_creation`, `irr_validation_state`, `ownership_validation_state`, `ownership_validation_token`, `rpki_validation_state`
 
 #### AI
-
 - Added `toMarkdown.supported()` method to get all supported conversion formats
 
 #### AI Gateway
-
 - `zdr` field added to all responses and params
 
 #### Alerting
-
 - New alert type: `abuse_report_alert`
 - `type` field added to PolicyFilter
 
 #### Browser Rendering
-
 - `ContentCreateParams`: refined to discriminated union (`Variant0 | Variant1`)
 - Split into URL-based and HTML-based parameter variants for better type safety
 
 #### Client Certificates
-
 - `reactivate` parameter in edit
 
 #### CloudforceOne
-
 - `ThreatEventCreateParams.indicatorType`: required → optional
 - `hasChildren` field added to all threat event response types
 - `datasetIds` query parameter on `AttackerListParams`, `CategoryListParams`, `TargetIndustryListParams`
@@ -251,69 +213,56 @@ All record type interfaces renamed from `*Record` to short names:
 - `createdAt`, `datasetId` fields on `ThreatEventEditParams`
 
 #### Content Scanning
-
 - Added `create()`, `update()`, `get()` methods
 
 #### Custom Pages
-
 - New page types: `basic_challenge`, `under_attack`, `waf_challenge`
 
 #### D1
-
 - `served_by_colo` - colo that handled query
 - `jurisdiction` - `'eu' | 'fedramp'`
 - **Time Travel** (`client.d1.database.timeTravel`): `getBookmark()`, `restore()` - point-in-time recovery
 
 #### Email Security
-
 - New fields on `InvestigateListResponse`/`InvestigateGetResponse`: `envelope_from`, `envelope_to`, `postfix_id_outbound`, `replyto`
 - New detection classification: `'outbound_ndr'`
 - Enhanced `Finding` interface with `attachment`, `detection`, `field`, `portion`, `reason`, `score`
 - Added `cursor` query parameter to `InvestigateListParams`
 
 #### Gateway Lists
-
 - New list types: `CATEGORY`, `LOCATION`, `DEVICE`
 
 #### Intel
-
 - New issue type: `'configuration_suggestion'`
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Leaked Credential Checks
-
 - Added `detections.get()` method
 
 #### Logpush
-
 - New datasets: `dex_application_tests`, `dex_device_state_events`, `ipsec_logs`, `warp_config_changes`, `warp_toggle_changes`
 
 #### Load Balancers
-
 - `Monitor.port`: `number` → `number | null`
 - `Pool.load_shedding`: `LoadShedding` → `LoadShedding | null`
 - `Pool.origin_steering`: `OriginSteering` → `OriginSteering | null`
 
 #### Magic Transit
-
 - `license_key` field on connectors
 - `provision_license` parameter for auto-provisioning
 - IPSec: `custom_remote_identities` with FQDN support
 - Snapshots: Bond interface, `probed_mtu` field
 
 #### Pages
-
 - New response types: `ProjectCreateResponse`, `ProjectListResponse`, `ProjectEditResponse`, `ProjectGetResponse`
 - Deployment methods return specific response types instead of generic `Deployment`
 
 #### Queues
-
 - Added `subscriptions.get()` method
 - Enhanced `SubscriptionGetResponse` with typed event source interfaces
 - New event source types: Images, KV, R2, Vectorize, Workers AI, Workers Builds, Workflows
 
 #### R2
-
 - Sippy: new provider `s3` (S3-compatible endpoints)
 - Sippy: `bucketUrl` field for S3-compatible sources
 - Super Slurper: `keys` field on source response schemas (specify specific keys to migrate)
@@ -321,41 +270,32 @@ All record type interfaces renamed from `*Record` to short names:
 - Super Slurper: `region` field on S3 source params
 
 #### Radar
-
 - Added `geolocations.list()`, `geolocations.get()` methods
 - Added V2 dimension-based methods (`summaryV2`, `timeseriesGroupsV2`) to radar sub-resources
 
 #### Resource Sharing
-
 - Added `terminal` boolean field to Resource Error interfaces
 
 #### Rules
-
 - Added `id` field to `ItemDeleteParams.Item`
 
 #### Rulesets
-
 - New buffering fields on `SetConfigRule`: `request_body_buffering`, `response_body_buffering`
 
 #### Secrets Store
-
 - New scopes: `'dex'`, `'access'` (in addition to `'workers'`, `'ai_gateway'`)
 
 #### SSL Certificate Packs
-
 - Response types now proper interfaces (was `unknown`)
 - Fields now required: `id`, `certificates`, `hosts`, `status`, `type`
 
 #### Security Center
-
 - `payload` field: `unknown` → typed `Payload` interface with `detection_method`, `zone_tag`
 
 #### Shared Types
-
 - Added: `CloudflareTunnelsV4PagePaginationArray` pagination class
 
 #### Workers
-
 - Added `subdomains.delete()` method
 - `Worker.references` - track external dependencies (domains, Durable Objects, queues)
 - `Worker.startup_time_ms` - startup timing
@@ -366,44 +306,36 @@ All record type interfaces renamed from `*Record` to short names:
 - Telemetry: `traces` field, `$containers` event info, `durableObjectId`, `transactionName`, `abr_level` fields
 
 #### Workers for Platforms
-
 - `ScriptUpdateResponse`: new fields `entry_point`, `observability`, `tag`, `tags`
 - `placement` field now union of 4 variants (smart mode, region, hostname, host)
 - `tags`, `tail_consumers` now nullable
 - `TagUpdateParams.body` now accepts `null`
 
 #### Workflows
-
 - `instance_retention`: `unknown` → typed `InstanceRetention` interface with `error_retention`, `success_retention`
 - New status option: `'restart'` added to `StatusEditParams.status`
 
 #### Zero-Trust Devices
-
 - External emergency disconnect settings (4 new fields)
 - `antivirus` device posture check type
 - `os_version_extra` documentation improvements
 
 #### Zones
-
 - New response types: `SubscriptionCreateResponse`, `SubscriptionUpdateResponse`, `SubscriptionGetResponse`
 
 #### Zero-Trust Access Applications
-
 - New `ApplicationType` values: `'mcp'`, `'mcp_portal'`, `'proxy_endpoint'`
 - New destination type: `ViaMcpServerPortalDestination` for MCP server access
 
 #### Zero-Trust Gateway
-
 - Added `rules.listTenant()` method
 
 #### Zero-Trust Gateway - Proxy Endpoints
-
 - `ProxyEndpoint`: interface → discriminated union (`ZeroTrustGatewayProxyEndpointIP | ZeroTrustGatewayProxyEndpointIdentity`)
 - `ProxyEndpointCreateParams`: interface → union type
 - Added `kind` field: `'ip' | 'identity'`
 
 #### Zero-Trust Tunnels
-
 - `WARPConnector*Response`: union type → interface
 
 ---
@@ -439,4 +371,4 @@ All record type interfaces renamed from `*Record` to short names:
 - Added deprecation notices with migration paths
 - **api_gateway:** deprecate API Shield Schema Validation resources ([8a4b20f](https://github.com/cloudflare/cloudflare-typescript/commit/8a4b20f7a572422f74179fbdb4f1c4fb555e3e40))
 - Improved JSDoc examples across all resources
-- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
+- **workers:** expose subdomain delete documentation ([4f7cc1f](https://github.com/cloudflare/cloudflare-typescript/commit/4f7cc1f2b8861a5b8abc193d287f78264a425062))
\ No newline at end of file
diff --git a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
index 7b6922947ee7f2c..4637fe2ecd6fe2e 100644
--- a/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
+++ b/src/content/changelog/sdk/2026-02-13-cloudflare-python-v5.0.0-beta.1.mdx
@@ -98,57 +98,46 @@ will help you understand any down or upstream issues it may cause to your enviro
 ### New Endpoints (Existing Resources)
 
 #### `acm.totaltls`
-
 - `edit()`
 - `update()`
 
 #### `cloudforceone.threatevents`
-
 - `list()`
 
 #### `contentscanning`
-
 - `create()`
 - `get()`
 - `update()`
 
 #### `dns.records`
-
 - `scan_list()`
 - `scan_review()`
 - `scan_trigger()`
 
 #### `intel.indicatorfeeds`
-
 - `create()`
 - `delete()`
 - `list()`
 
 #### `leakedcredentialchecks.detections`
-
 - `get()`
 
 #### `queues.consumers`
-
 - `list()`
 
 #### `radar.ai`
-
 - `summary()`
 - `timeseries()`
 - `timeseries_groups()`
 
 #### `radar.bgp`
-
 - `changes()`
 - `snapshot()`
 
 #### `workers.subdomains`
-
 - `delete()`
 
 #### `zerotrust.networks`
-
 - `create()`
 - `delete()`
 - `edit()`
@@ -175,4 +164,4 @@ will help you understand any down or upstream issues it may cause to your enviro
 - **Discriminated unions**: Correctly handle nested discriminated unions in response parsing
 - **Extra field types**: Parse extra field types correctly
 - **Empty metadata**: Ignore empty metadata fields during parsing
-- **Singularization rules**: Update resource name singularization rules for better consistency
+- **Singularization rules**: Update resource name singularization rules for better consistency
\ No newline at end of file
diff --git a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
index 01d745a7853300f..80b92a2e38719b4 100644
--- a/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
+++ b/src/content/changelog/security-center/2025-07-18-brand-protection-api.mdx
@@ -1,16 +1,16 @@
+
 ---
 title: New APIs for Brand Protection setup
 description: You can now use the Brand Protection API endpoints to manage your Brand Protection queries
 date: 2025-07-18
 ---
-
+ 
 The Brand Protection API is now available, allowing users to create new queries and delete existing ones, fetch matches and more!
-
+ 
 What you can do:
-
-- **create new string or logo query**
-- **delete string or logo queries**
-- **download matches for both logo and string queries**
-- **read matches for both logo and string queries**
+- **create new string or logo query** 
+- **delete string or logo queries** 
+- **download matches for both logo and string queries** 
+- **read matches for both logo and string queries** 
 
 Ready to start? Check out the [Brand Protection API](/api/resources/brand_protection/) in our documentation.
diff --git a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
index 58288565e961039..a8da24443aa2244 100644
--- a/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
+++ b/src/content/changelog/security-center/2025-10-27-RFI-Tokens-in-Dash.mdx
@@ -4,7 +4,7 @@ description: The Requests for Information (RFI) dashboard now shows the number o
 date: 2025-10-27
 ---
 
-The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted.
+The Requests for Information (RFI) dashboard now shows users the number of tokens used by each submitted RFI to better understand usage of tokens and how they relate to each request submitted. 
 
 ![Cloudforce One RFI tokens](~/assets/images/changelog/security-center/2025-10-24RFITokens.png)
 
diff --git a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
index 07257c943d54312..5c14e85f93430d3 100644
--- a/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
+++ b/src/content/changelog/security-center/2025-10-31-brand-protection-logo-dashboard-report-abuse.mdx
@@ -1,9 +1,9 @@
 ---
 title: Report logo misuse to Cloudflare directly from the Brand Protection dashboard
-description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network
+description: You can now use the Brand Protection logo dashboard to report abuse on the Cloudflare network 
 date: 2025-10-31
 ---
 
 The Brand Protection logo query dashboard now allows you to use the **Report to Cloudflare** button to submit an Abuse report directly from the Brand Protection logo queries dashboard. While you could previously report new domains that were impersonating your brand before, now you can do the same for websites found to be using your logo without your permission. The abuse reports will be prefilled and you will only need to validate a few fields before you can click the submit button, after which our team process your request.
 
-Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/).
+Ready to start? Check out the [Brand Protection docs](/security-center/brand-protection/). 
diff --git a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
index fcd53972aec849f..9f9d5dd72cde73f 100644
--- a/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
+++ b/src/content/changelog/security-center/2025-11-21-Threat-Events-now-show-events-insights.mdx
@@ -4,7 +4,7 @@ description: Threat events users can now access threat insights curated by our t
 date: 2025-11-21
 ---
 
-The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity.
-Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.
+The threat events platform now has threat insights available for some relevant parent events. Threat intelligence analyst users can access these insights for their threat hunting activity. 
+Insights are also highlighted in the Cloudflare dashboard by a small `lightning icon` and the insights can refer to multiple, connected events, potentially part of the same attack or campaign and associated with the same threat actor.  
 
-For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events).
+For more information, refer to [Analyze threat events](/security-center/cloudforce-one/#analyze-threat-events). 
diff --git a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
index f6b64dc1ba68722..1dad1d621eb3f74 100644
--- a/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
+++ b/src/content/changelog/security-center/2026-01-14-Download-URL-Scanner-Report-PDF.mdx
@@ -9,13 +9,13 @@ This update streamlines how security analysts can share findings with stakeholde
 
 **Key Benefits:**
 
-- Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
-- Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
+* Consolidate scan results, including screenshots, security signatures, and metadata, into a single, portable document
+* Easily share professional-grade summaries with non-technical stakeholders or legal teams for faster incident response
 
 **What’s new:**
 
-- **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
-- **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
+* **PDF Export Button:** A new download option is available in the URL Scanner results page within the Cloudflare dashboard
+* **Unified Documentation:** Access all scan details—from high-level summaries to specific security flags—in one offline-friendly file
 
 To get started with the URL Scanner and explore our reporting capabilities, visit the [URL Scanner API documentation](https://developers.cloudflare.com/api/resources/url_scanner/).
 
diff --git a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
index eff63f778930ece..e0dd22e2c84e189 100644
--- a/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
+++ b/src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx
@@ -3,7 +3,6 @@ title: Cloudforce One Threat events graphs are now visible in the dashboard
 description: Trace attack flows with Sankey diagrams and analyze dataset distribution over time
 date: 2026-02-19
 ---
-
 We have introduced dynamic visualizations to the Threat Events dashboard to help you better understand the threat landscape and identify emerging patterns at a glance.
 
 What's new:
diff --git a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
index 4a28f773e0eeeac..5260cc6ad7bf605 100644
--- a/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
+++ b/src/content/changelog/security-center/2026-02-23-Saved-views-in-threat-events.mdx
@@ -9,8 +9,7 @@ date: 2026-02-23
 ## Why this matters
 
 Threat intelligence is most effective when it is personalized. Previously, analysts had to manually re-apply complex filters (like combining specific industry datasets with geographic origins) every time they logged in. This update provides material value by:
-
-- Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
-- Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
+* Analysts can now jump straight into "Known Ransomware Infrastructure" or "Retail Sector Targets" views with a single click, eliminating repetitive setup tasks
+* Teams can ensure everyone is looking at the same data subsets by using standardized saved views, reducing the risk of missing critical patterns due to inconsistent filtering.
 
 Cloudforce One subscribers can start saving their custom views now in [Application Security > Threat Intelligence > Threat Events](https://dash.cloudflare.com/?to=/:account/security-center/threat-intelligence/threat-events).
diff --git a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
index 14c2ac824145ccc..14417dfa3c757dd 100644
--- a/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
+++ b/src/content/changelog/security-center/2026-04-08-threat-events-notification.mdx
@@ -3,25 +3,25 @@ title: Real-time alerts and daily digests for Threat Events
 description: You can now subscribe to automated notifications for your saved views in Threat Events
 date: 2026-04-08
 ---
-
+ 
 You can now automate your threat monitoring by setting up custom alerts in your saved views. Instead of manually checking the dashboard for updates, you can subscribe to notifications that trigger whenever new data matches your specific filter sets, like new activity associated to a particular threat actor or spikes in activity within your industry.
-
+ 
 ### Stay ahead of emerging threats
-
+ 
 By linking your saved views to the Cloudflare Notifications Center, you can ensure the right information reaches your team at the right time.
-
+ 
 - **Immediate Alerts**: receive real-time notifications the moment a critical event is detected that matches your saved criteria. This is essential for high-priority monitoring, such as tracking active campaigns from specific APT groups.
-
+ 
 - **Daily Digests**: opt for a summarized report delivered once a day. This is ideal for maintaining situational awareness of broader trends, like regional activity shifts or industry-wide threat landscapes, without cluttering your inbox.
-
+ 
 ![Threat Events notifications](~/assets/images/changelog/security-center/threat-events-notifications.png)
-
+ 
 ### How to get started
-
+ 
 To set up an alert, go to **Application Security** > **Threat Intelligence** > **Threat Events**. From there:
-
+ 
 1. Choose your datasets and apply your desired filters and select **Save View** (or select an existing one).
 2. Open the **Manage Saved Views** menu.
 3. Select **Add Alert** next to your chosen view to configure your notification preferences in the Cloudflare dashboard.
-
+ 
 For more technical details on configuring notifications, refer to the [Threat Events documentation](/security-center/cloudforce-one/).
diff --git a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
index 51425d471206a97..6ab0a8267691e14 100644
--- a/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
+++ b/src/content/changelog/security-center/2026-05-07-CSV-export-for-RFIs.mdx
@@ -7,7 +7,6 @@ date: 2026-05-07
 You can now export your Requests for Information (RFI) history to a **CSV document** and customize your dashboard view by choosing how many RFI records to load per page.
 
 ### Why this matters
-
 These quality-of-life updates focus on data portability and dashboard performance, allowing power users to manage high volumes of requests more efficiently:
 
 - The new **CSV export** allows you to move RFI data into external tools for custom reporting, internal auditing, or cross-referencing with other security projects without manual data entry
diff --git a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
index 3045c86a164b8bf..7728d2033ec5df9 100644
--- a/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
+++ b/src/content/changelog/security-center/2026-05-12-URL-scanner-report-agent-readiness.mdx
@@ -9,19 +9,18 @@ We’ve added a new **Agent Readiness** tab to URL Scanner reports accessible vi
 The Internet is shifting from a human-read web to a machine-read web. AI agents now browse, interact with, and even perform transactions on websites. If a site isn't "agent-ready," these bots may consume excessive bandwidth, fail to find critical information, or be unable to navigate your services efficiently.
 
 This update provides material value by breaking down readiness into six actionable categories:
-
-- **Basic Web Presence**
+- **Basic Web Presence** 
 - **Discoverability**
-- **Content Accessibility**
-- **Bot Access Control**
-- **Protocol Discovery**
-- **Commerce**
+- **Content Accessibility** 
+- **Bot Access Control** 
+- **Protocol Discovery** 
+- **Commerce** 
 
 ## Accessing the report
 
-You can view these scores for any scanned URL directly in the dashboard or via our API.
+You can view these scores for any scanned URL directly in the dashboard or via our API. 
 
-- **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
-- **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
+* **Dashboard:** Go to **Protect & Connect > Application Security > Investigate**. After running a scan, select the **Agent Readiness** tab in the report.
+* **API:** Use the [URL Scanner API](https://developers.cloudflare.com/radar/investigate/url-scanner/) to programmatically retrieve these scores for your infrastructure.
 
 To learn more about the methodology behind these scores, refer to the [blogpost](https://blog.cloudflare.com/agent-readiness/).
diff --git a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
index 632429a872e1c7c..f32ba78cbd7337b 100644
--- a/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
+++ b/src/content/changelog/security-overview/2026-04-27-archive-and-audit-security-action-items.md
@@ -12,7 +12,7 @@ Introducing enhanced archiving capabilities for security action items within the
 
 ### Why this matters
 
-Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored.
+Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored. 
 
 With these new archiving options—**False Positive**, **Accept Risk**, and **Other**—you can now suppress items indefinitely with required rationale text for risk-based decisions. This ensures that your team remains focused on critical, actionable vulnerabilities while preserving institutional knowledge for audits.
 
@@ -36,5 +36,4 @@ To review the history and rationale of a specific archived issue at the account
 ```bash
 curl "[https://api.cloudflare.com/client/v4/accounts/](https://api.cloudflare.com/client/v4/accounts/){account_id}/insights/{insight_id}/audit-log" \
      -H "Authorization: Bearer <API_TOKEN>" \
-     -H "Content-Type: application/json"
-```
+     -H "Content-Type: application/json"
\ No newline at end of file
diff --git a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
index 52e1ce7305a8c77..d1f9b23ef4c3974 100644
--- a/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
+++ b/src/content/changelog/ssl/2025-08-25-secrets-store-ai-gateway.mdx
@@ -7,7 +7,7 @@ description: Cloudflare Secrets Store is now integrated with AI Gateway, allowin
 date: 2025-08-25T11:00:00Z
 ---
 
-import { Card, Render, Details } from "~/components";
+import { Card, Render, Details } from "~/components"
 
 Cloudflare Secrets Store is now integrated with AI Gateway, allowing you to store, manage, and deploy your AI provider keys in a secure and seamless configuration through [Bring Your Own Key](https://developers.cloudflare.com/ai-gateway/configuration/bring-your-own-keys/). Instead of passing your AI provider keys directly in every request header, you can centrally manage each key with Secrets Store and deploy in your gateway configuration using only a reference, rather than passing the value in plain text.
 
@@ -25,24 +25,24 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthro
  --header 'anthropic-version: 2023-06-01' \
  --header 'Content-Type: application/json' \
  --data  '{"model": "claude-3-opus-20240229", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}'
-```
+ ```
 
-Or, using Javascript:
+ Or, using Javascript:
 
-```
-import Anthropic from '@anthropic-ai/sdk';
+ ```
+ import Anthropic from '@anthropic-ai/sdk';
 
 
 const anthropic = new Anthropic({
- apiKey: "ANTHROPIC_KEY_1",
- baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
+  apiKey: "ANTHROPIC_KEY_1",
+  baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",
 });
 
 
 const message = await anthropic.messages.create({
- model: 'claude-3-opus-20240229',
- messages: [{role: "user", content: "What is Cloudflare?"}],
- max_tokens: 1024
+  model: 'claude-3-opus-20240229',
+  messages: [{role: "user", content: "What is Cloudflare?"}],
+  max_tokens: 1024
 });
 ```
 
diff --git a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
index d6f34e72b9e8ed7..c7b16b6e1a681b2 100644
--- a/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
+++ b/src/content/changelog/stream/2025-07-22-media-transformations-audio-mode.mdx
@@ -10,7 +10,7 @@ an M4A file to use in downstream workflows like [AI inference](/workers-ai/), co
 
 For example,
 
-```text title="Example URL"
+``` text title="Example URL"
 https://example.com/cdn-cgi/media/<OPTIONS>/<SOURCE-VIDEO>
 https://example.com/cdn-cgi/media/mode=audio,time=3s,duration=60s/<input video with diction>
 ```
diff --git a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
index 817c2e0c7c81e19..a2a4201f278c795 100644
--- a/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
+++ b/src/content/changelog/support/2026-04-06-redesigned-support-portal.mdx
@@ -3,7 +3,6 @@ title: Redesigned Support Portal for faster, personalized help
 description: A streamlined Support Portal featuring AI-driven ticket routing and a simplified interface for all Cloudflare customers.
 date: 2026-04-07
 ---
-
 ## Redesigned "Get Help" Portal for faster, personalized help
 
 Cloudflare has officially launched a redesigned "Get Help" Support Portal to eliminate friction and get you to a resolution faster. Previously, navigating support meant clicking through multiple tiles, categorizing your own technical issues across 50+ conditional fields, and translating your problem into Cloudflare's internal taxonomy.
diff --git a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
index 906dc74af3ffc2b..0fe7d0c34250fb2 100644
--- a/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
+++ b/src/content/changelog/support/2026-04-28-direct-support-navigation.mdx
@@ -12,7 +12,7 @@ This change ensures that when you need help, you spend less time navigating the
 
 ### What changed?
 
-- **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
-- **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
+* **Previous behavior**: Selecting **? Support** opened a dropdown menu with various links (Help Center, Cloudflare Community, etc.).
+* **New behavior**: Selecting **Support** immediately redirects your current tab to the Support Portal.
 
 To learn more about the resources available to you, refer to the [Cloudflare Support documentation](https://developers.cloudflare.com/support/contacting-cloudflare-support/).
diff --git a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
index 70650f4bcd04ef7..d128e3253f5acb2 100644
--- a/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
+++ b/src/content/changelog/terraform/2025-02-03-terraform-v5-provider.mdx
@@ -5,7 +5,6 @@ products:
   - fundamentals
 date: 2025-02-03
 ---
-
 ![Screenshot of Terraform defining a Zone](~/assets/images/changelog/2024-02-03-terraform-v5-screenshot.png)
 
 Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure.
@@ -13,6 +12,5 @@ Cloudflare's v5 Terraform Provider is now generally available. With this release
 The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach.
 
 For more info
-
-- [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
+* [Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
+* [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
index 692eda375b40aaa..d8df928767923fd 100644
--- a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx
@@ -11,12 +11,12 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 ### Changes
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
-  - `cloudflare_zero_trust_gateway_policy`
-  - `cloudflare_zero_trust_access_application`
-  - `cloudflare_zero_trust_tunnel_cloudflared_route`
-  - `cloudflare_zone_setting`
-  - `cloudflare_ruleset`
-  - `cloudflare_page_rule`
+	- `cloudflare_zero_trust_gateway_policy`
+	- `cloudflare_zero_trust_access_application`
+	- `cloudflare_zero_trust_tunnel_cloudflared_route`
+	- `cloudflare_zone_setting`
+	- `cloudflare_ruleset`
+	- `cloudflare_page_rule`
 - Zone settings can be re-applied without client errors
 - Page rules conversion errors are fixed
 - Failure to apply changes to `cloudflare_zero_trust_tunnel_cloudflared_route`
@@ -25,7 +25,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.5.0) in GitHub.
 
 ### Issues Closed
-
 - [#5304: Importing cloudflare_zero_trust_gateway_policy invalid attribute filter value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5304)
 - [#5303: cloudflare_page_rule import does not set values for all of the fields in terraform state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5303)
 - [#5178: cloudflare_page_rule Page rule creation with redirect fails](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5178)
diff --git a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
index ce7ec83f1e68809..88d70bea95929e7 100644
--- a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx
@@ -17,7 +17,7 @@ eye on this changelog for more information about upcoming releases.
 
 - Broad fixes across resources with recurring diffs, including, but not limited to:
   - `cloudflare_zero_trust_access_identity_provider`
-  - `cloudflare_zone`
+	- `cloudflare_zone`
 - `cloudflare_page_rules` runtime panic when setting `cache_level` to `cache_ttl_by_status`
 - Failure to serialize requests in `cloudflare_zero_trust_tunnel_cloudflared_config`
 - Undocumented field 'priority' on `zone_lockdown` resource
@@ -33,7 +33,6 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.6.0) in GitHub.
 
 ### Issues Closed
-
 - [#5098: 500 Server Error on updating 'zero_trust_tunnel_cloudflared_virtual_network' Terraform resource](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5098)
 - [#5148: cloudflare_user_agent_blocking_rule doesn’t actually support user agents](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5148)
 - [#5472: cloudflare_zone showing changes in plan after following upgrade steps](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5472)
diff --git a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
index e637557cb1938b2..aaabc9c53996ef2 100644
--- a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx
@@ -11,7 +11,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases.
 
 ### Changes
-
 - Addressed permanent diff bug on Cloudflare Tunnel config
 - State is now saved correctly for Zero Trust Access applications
 - Exact match is now working as expected within `data.cloudflare_zero_trust_access_applications`
@@ -25,7 +24,6 @@ For a more detailed look at all of the changes, see the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.7.0) in GitHub.
 
 ### Issues Closed
-
 - [#5563: cloudflare_logpull_retention is missing import](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5563)
 - [#5608: cloudflare_zero_trust_access_policy in 5.5.0 provider gives error upon apply unexpected new value: .app_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1)](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5608)
 - [#5612: data.cloudflare_zero_trust_access_applications does not exact match](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5612)
@@ -34,6 +32,7 @@ For a more detailed look at all of the changes, see the
 - [#5565: Running Terraform with the cloudflare_zero_trust_access_policy resource results in updates on every apply, even when no changes are made - breaks idempotency](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5565)
 - [#5529: cloudflare_zero_trust_access_application: self hosted applications with private ips require public domain ](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5529)
 
+
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
index ce5660cdb8f4833..280ce29c2aebb63 100644
--- a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx
@@ -11,7 +11,6 @@ Earlier this year, we announced the launch of the new [Terraform v5 Provider](/c
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_custom_pages`
   - `cloudflare_page_rule`
@@ -19,14 +18,13 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
   - `cloudflare_argo_tiered_caching`
 - Addressed chronic drift issues in `cloudflare_logpush_job`, `cloudflare_zero_trust_dns_location`, `cloudflare_ruleset` & `cloudflare_api_token`
 - `cloudflare_zone_subscription` returns expected values `rate_plan.id` from former versions
-- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate
-- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy`
+- `cloudflare_workers_script` can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate 
+- Ability to configure `add_headers` under `cloudflare_zero_trust_gateway_policy` 
 - Other bug fixes
 
 For a more detailed look at all of the changes, see the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.2) in GitHub.
 
 ### Issues Closed
-
 - [#5666: cloudflare_ruleset example lists id which is a read-only field](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5666)
 - [#5578: cloudflare_logpush_job plan always suggests changes](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5578)
 - [#5552: 5.4.0: Since provider update, existing cloudflare_list_item would be recreated "created" state](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5552)
diff --git a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
index 62ed2ed4b454317..32201f4ca38d484 100644
--- a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx
@@ -6,14 +6,13 @@ products:
 date: 2025-08-15
 ---
 
-Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability.
+Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. 
 
-One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests.
+One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests. 
 
 Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_argo_smart_routing`
   - `cloudflare_bot_management`
@@ -41,7 +40,6 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 For a more detailed look at all of the changes, refer to the [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.4) in GitHub.
 
 ### Issues Closed
-
 - [#5017: 'Uncaught Error: No such module' using cloudflare_snippets](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5017)
 - [#5701: cloudflare_workers_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5701)
 - [#5640: cloudflare_argo_smart_routing importing doesn't read the actual value](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5640)
diff --git a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
index e89ea7fd1f359cd..f25c1bc414c9f19 100644
--- a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
+++ b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx
@@ -13,7 +13,6 @@ Thank you for continuing to raise issues. We triage them weekly and they help ma
 This release includes a new resource, `cloudflare_snippet`, which replaces `cloudflare_snippets`. `cloudflare_snippet` is now considered deprecated but can still be used. Please utilize `cloudflare_snippet` as soon as possible.
 
 ### Changes
-
 - Resources stabilized:
   - `cloudflare_zone_setting`
   - `cloudflare_worker_script`
@@ -29,7 +28,6 @@ For a more detailed look at all of the changes, refer to the
 [changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.9.0) in GitHub.
 
 ### Issues Closed
-
 - [#5921: In cloudflare_ruleset removing an existing rule causes recreation of later rules](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5921)
 - [#5904: cloudflare_zero_trust_access_application is not idempotent](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5904)
 - [#5898: (cloudflare_workers_script) Durable Object migrations not applied](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5898)
@@ -49,6 +47,7 @@ For a more detailed look at all of the changes, refer to the
 - [#5727: cloudflare_ruleset http_request_cache_settings bypass mismatch between dashboard and terraform](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5727)
 - [#5700: cloudflare_account_member invalid type 'string' for field 'roles'](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5700)
 
+
 If you have an unaddressed issue with the provider, we encourage you to check the [open issues](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new issue if one does not already exist for what you are experiencing.
 
 ### Upgrading
diff --git a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
index ac788bb9e06272c..3886135203e9e03 100644
--- a/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-11-20-terraform-v5.13.0-provider.mdx
@@ -6,56 +6,55 @@ products:
 date: 2025-11-20
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.13 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
-This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more.
+This release includes new features, new resources and data sources, bug fixes, updates to our Developer Documentation, and more. 
 
 ### Breaking Change
-
 Please be aware that there are breaking changes for the `cloudflare_api_token` and `cloudflare_account_token` resources. These changes eliminate configuration drift caused by policy ordering differences in the Cloudflare API.
 
 For more specific information about the changes or the actions required, please see the [detailed Repository changelog](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.13.0).
 
+
 ### Features
 
-- **New resources and data sources added**
-  - cloudflare_connectivity_directory
-  - cloudflare_sso_connector
-  - cloudflare_universal_ssl_setting
-- **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
-- **docs:** make docs explicit when a resource does not have import support
-- **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
-- **worker_version:** add content_base64 support
-- **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
-- **workers_script_subdomains:** add import support ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
-- **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
-- **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
+* **New resources and data sources added** 
+	* cloudflare_connectivity_directory
+	* cloudflare_sso_connector
+	* cloudflare_universal_ssl_setting
+* **api_token+account_tokens:** state upgrader and schema bump ([#6472](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6472))
+* **docs:** make docs explicit when a resource does not have import support 
+* **magic_transit_connector:** support self-serve license key ([#6398](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6398))
+* **worker_version:** add content_base64 support
+* **worker_version:** boolean support for run_worker_first ([#6407](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6407))
+* **workers_script_subdomains:** add import support  ([#6375](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6375))
+* **zero_trust_access_application:** add proxy_endpoint for ZT Access Application ([#6453](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6453))
+* **zero_trust_dlp_predefined_profile:** Switch DLP Predefined Profile endpoints, introduce enabled_entries attribute
+
 
 ### Bug Fixes
 
-- **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
-- allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
-- **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
-- **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
-- **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
-- **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
-- **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181))
-- **workers_kv:** multipart request ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
-- **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386))
-- **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383))
-- **workers_script:** allow config.run_worker_first to accept list input
-- **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
-- **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
-- **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
-- **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
+* **account_token:** token policy order and nested resources ([#6440](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6440))
+* allow r2_bucket_event_notification to be applied twice without failing ([#6419](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6419))
+* **cloudflare_worker+cloudflare_worker_version:** import for the resources ([#6357](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6357))
+* **dns_record:** inconsistent apply error ([#6452](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6452))
+* **pages_domain:** resource tests ([#6338](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6338))
+* **pages_project:** unintended resource state drift ([#6377](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6377))
+* **queue_consumer:** id population ([#6181](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6181)) 
+* **workers_kv:** multipart request  ([#6367](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6367))
+* **workers_kv:** updating workers metadata attribute to be read from endpoint ([#6386](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6386)) 
+* **workers_script_subdomain:** add note to cloudflare_workers_script_subdomain about redundancy with cloudflare_worker ([#6383](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6383)) 
+* **workers_script:** allow config.run_worker_first to accept list input 
+* **zero_trust_device_custom_profile_local_domain_fallback:** drift issues ([#6365](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6365))
+* **zero_trust_device_custom_profile:** resolve drift issues ([#6364](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6364))
+* **zero_trust_dex_test:** correct configurability for 'targeted' attribute to fix drift
+* **zero_trust_tunnel_cloudflared_config:** remove warp_routing from cloudflared_config ([#6471](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6471))
 
 ### Upgrading
-
 We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized. We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more info
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
index 9cff570347406b9..a33c746b8592808 100644
--- a/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-05-terraform-v5.14.0-provider.mdx
@@ -6,7 +6,7 @@ products:
 date: 2025-12-05
 ---
 
-Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.
+Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.14 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) - we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5. 
 
 Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.
 
@@ -14,7 +14,7 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Deprecation notice
 
-Resource affected: `api_shield_discovery_operation`
+Resource affected: `api_shield_discovery_operation` 
 
 Cloudflare continuously discovers and updates API endpoints and web assets of your web applications. To improve the maintainability of these dynamic resources, we are working on reducing the need to actively engage with discovered operations.
 
@@ -26,23 +26,21 @@ The corresponding public API endpoint of [discovered operations](https://develop
 
 ### Bug fixes
 
-- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488))
+- **account_members**: Makes member policies a set ([#6488](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6488)) 
 - **pages_project**: Ensures non empty refresh plans ([#6515](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6515))
-- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512))
-- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521))
-- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489))
-- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504))
-- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503))
+- **R2**: Improves sweeper ([#6512](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6512)) 
+- **workers_kv**: Ignores value import state for verify ([#6521](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6521)) 
+- **workers_script**: No longer treats the migrations attribute as WriteOnly ([#6489](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6489)) 
+- **workers_script**: Resolves resource drift when worker has unmanaged secret ([#6504](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6504)) 
+- **zero_trust_device_posture_rule**: Preserves input.version and other fields ([#6500](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6500)) and ([#6503](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6503)) 
 - **zero_trust_dlp_custom_profile**: Adds sweepers for `dlp_custom_profile`
 - **zone_subscription|account_subscription**: Adds `partners_ent` as valid enum for `rate_plan.id` ([#6505](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6505))
-- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487))
-- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510))
+- **zone**: Ensures datasource model schema parity ([#6487](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6487)) 
+- **subscription**: Updates import signature to accept account_id/subscription_id to import account subscription ([#6510](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6510)) 
 
 ### Upgrade to newer version
-
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)
diff --git a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
index 6c0f1f7bf13a718..017d74955cda99c 100644
--- a/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
+++ b/src/content/changelog/terraform/2025-12-19-terraform-v5.15.0-provider.mdx
@@ -14,31 +14,29 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-- **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
-- **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
-- **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
-- **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
-- **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
-- **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+* **ai_search:** Add AI Search endpoints ([6f02adb](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
+* **certificate_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
+* **worker_version:** Support `startup_time_ms` ([286ab55](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
+* **zero_trust_dlp_custom_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_integration_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_dlp_predefined_entry:** Support `upload_status` ([7dc0fe3](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
+* **zero_trust_gateway_policy:** Support `forensic_copy` ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
+* **zero_trust_list:** Support additional types (category, location, device) ([5741fd0](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
 
 ### Bug fixes
 
-- **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
-- **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
-- **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
-- **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
-- **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
-- **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
-- **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
+* **access_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
+* **cloudflare_pages_project:** Addressing drift issues ([6edffcf](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
+* **cloudflare_worker:** Can be cleanly imported ([4859b52](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
+* **cloudflare_worker:** Ensure clean imports ([5b525bc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
+* **list_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
+* **zero_trust_access_application:** Remove all conditions from sweeper ([3197f1a](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
+* **spectrum_application:** Map missing fields during spectrum resource import ([#6495](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))
 
 ### Upgrade to newer version
-
 We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
-- [Documentation on using Terraform with Cloudflare](/terraform/)
+- [Documentation on using Terraform with Cloudflare](/terraform/)
\ No newline at end of file
diff --git a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
index fc887b15fcfba63..00374611ed967d8 100644
--- a/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-01-20-terraform-v5.16.0-provider.mdx
@@ -16,42 +16,41 @@ This release includes bug fixes, the stabilization of even more popular resource
 
 ### Features
 
-- **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
-- **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
-- **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
-- **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
-- **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
-- **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
-- **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
-- **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
-- **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
-- **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
-- **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
-- **ruleset:** add request body buffering support
-- **ruleset:** enhance ruleset data source with additional configuration options
-- **workers_script:** add observability logs attributes to list data source model
-- **workers_script:** enhance list data source schema with additional configuration options
+* **custom_pages:** add "waf_challenge" as new supported error page type identifier in both resource and data source schemas
+* **list:** enhance CIDR validator to check for normalized CIDR notation requiring network address for IPv4 and IPv6
+* **magic_wan_gre_tunnel:** add automatic_return_routing attribute for automatic routing control
+* **magic_wan_gre_tunnel:** add BGP configuration support with new BGP model attribute
+* **magic_wan_gre_tunnel:** add bgp_status computed attribute for BGP connection status information
+* **magic_wan_gre_tunnel:** enhance schema with BGP-related attributes and validators
+* **magic_wan_ipsec_tunnel:** add automatic_return_routing attribute for automatic routing control
+* **magic_wan_ipsec_tunnel:** add BGP configuration support with new BGP model attribute
+* **magic_wan_ipsec_tunnel:** add bgp_status computed attribute for BGP connection status information
+* **magic_wan_ipsec_tunnel:** add custom_remote_identities attribute for custom identity configuration
+* **magic_wan_ipsec_tunnel:** enhance schema with BGP and identity-related attributes
+* **ruleset:** add request body buffering support
+* **ruleset:** enhance ruleset data source with additional configuration options
+* **workers_script:** add observability logs attributes to list data source model
+* **workers_script:** enhance list data source schema with additional configuration options
 
 ### Bug Fixes
 
-- **account_member**: fix resource importability issues
-- **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
-- **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
-- **workers_kv:** handle special characters correctly in URL encoding
+* **account_member**: fix resource importability issues
+* **dns_record:** remove unnecessary fmt.Sprintf wrapper around LoadTestCase call in test configuration helper function
+* **load_balancer:** fix session_affinity_ttl type expectations to match Float64 in initial creation and Int64 after migration
+* **workers_kv:** handle special characters correctly in URL encoding
 
 ### Documentation
 
-- **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
-- **api_shield:** add resource-level description for API Shield management of auth ID characteristics
-- **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
-- **api_shield:** specify JSONPath expression format for JWT claim locations
-- **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
-- **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
-- **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
-- **hyperdrive_config:** update port description to clarify defaults for different database types
+* **account_subscription:** update schema description for rate_plan.sets attribute to clarify it returns an array of strings
+* **api_shield:** add resource-level description for API Shield management of auth ID characteristics
+* **api_shield:** enhance auth_id_characteristics.name attribute description to include JWT token configuration format requirements
+* **api_shield:** specify JSONPath expression format for JWT claim locations
+* **hyperdrive_config:** add description attribute to name attribute explaining its purpose in dashboard and API identification
+* **hyperdrive_config:** apply description improvements across resource, data source, and list data source schemas
+* **hyperdrive_config:** improve schema descriptions for cache settings to clarify default values
+* **hyperdrive_config:** update port description to clarify defaults for different database types
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
index 76242fbae5f2ce1..d8dedb4bea9275a 100644
--- a/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-02-12-terraform-v5.17.0-provider.mdx
@@ -28,61 +28,60 @@ help us build products that reflect your needs.
 
 ### Features
 
-- **ai_search_instance:** add data source for querying AI Search instances
-- **ai_search_token:** add data source for querying AI Search tokens
-- **account:** add support for tenant unit management with new `unit` field
-- **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
-- **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
-- **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
-- **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
-- **workers_kv:** add `value` field to data source to retrieve KV values directly
-- **workers_script:** add `script` field to data source to retrieve script content
-- **workers_script:** add support for `simple` rate limit binding
-- **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
-- **workers_script:** add `placement_mode` and `placement_status` computed fields
-- **zero_trust_dex_test:** add data source with filter support for finding specific tests
-- **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
+* **ai_search_instance:** add data source for querying AI Search instances
+* **ai_search_token:** add data source for querying AI Search tokens
+* **account:** add support for tenant unit management with new `unit` field
+* **account:** add automatic mapping from `managed_by.parent_org_id` to `unit.id`
+* **authenticated_origin_pulls_certificate:** add data source for querying authenticated origin pull certificates
+* **authenticated_origin_pulls_hostname_certificate:** add data source for querying hostname-specific authenticated origin pull certificates
+* **authenticated_origin_pulls_settings:** add data source for querying authenticated origin pull settings
+* **workers_kv:** add `value` field to data source to retrieve KV values directly
+* **workers_script:** add `script` field to data source to retrieve script content
+* **workers_script:** add support for `simple` rate limit binding
+* **workers_script:** add support for targeted placement mode with `placement.target` array for specifying placement targets (region, hostname, host)
+* **workers_script:** add `placement_mode` and `placement_status` computed fields
+* **zero_trust_dex_test:** add data source with filter support for finding specific tests
+* **zero_trust_dlp_predefined_profile:** add `enabled_entries` field for flexible entry management
 
 ### Bug Fixes
 
-- **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
-- **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
-- **authenticated_origin_pulls:** handle array response and implement full lifecycle
-- **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
-- **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
-- **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
-- **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
-- **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
-- **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
-- **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
-- **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
-- **mtls_certificates:** fix resource and test
-- **pages_project:** revert build_config to computed optional
-- **stream_key:** use correct `account_id` field instead of `id` in API calls
-- **total_tls:** use upsert pattern for singleton zone setting
-- **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
-- **workers_script:** add support for placement mode/status
-- **zero_trust_access_application:** update v4 version on migration tests
-- **zero_trust_device_posture_rule:** update tests to match API
-- **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
-- **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
-- **zero_trust_organization:** fix plan issues
+* **account:** map `managed_by.parent_org_id` to `unit.id` in unmarshall and add acceptance tests
+* **authenticated_origin_pulls_certificate:** add certificate normalization to prevent drift
+* **authenticated_origin_pulls:** handle array response and implement full lifecycle
+* **authenticated_origin_pulls_hostname_certificate:** fix resource and tests
+* **cloudforce_one_request_message:** use correct `request_id` field instead of `id` in API calls
+* **dns_zone_transfers_incoming:** use correct `zone_id` field instead of `id` in API calls
+* **dns_zone_transfers_outgoing:** use correct `zone_id` field instead of `id` in API calls
+* **email_routing_settings:** use correct `zone_id` field instead of `id` in API calls
+* **hyperdrive_config:** add proper handling for write-only fields to prevent state drift
+* **hyperdrive_config:** add normalization for empty `mtls` objects to prevent unnecessary diffs
+* **magic_network_monitoring_rule:** use correct `account_id` field instead of `id` in API calls
+* **mtls_certificates:** fix resource and test
+* **pages_project:** revert build_config to computed optional
+* **stream_key:** use correct `account_id` field instead of `id` in API calls
+* **total_tls:** use upsert pattern for singleton zone setting
+* **waiting_room_rules:** use correct `waiting_room_id` field instead of `id` in API calls
+* **workers_script:** add support for placement mode/status
+* **zero_trust_access_application:** update v4 version on migration tests
+* **zero_trust_device_posture_rule:** update tests to match API
+* **zero_trust_dlp_integration_entry:** use correct `entry_id` field instead of `id` in API calls
+* **zero_trust_dlp_predefined_entry:** use correct `entry_id` field instead of `id` in API calls
+* **zero_trust_organization:** fix plan issues
 
 ### Chores
 
-- add state upgraders to 95+ resources to lay the foundation for replacing Grit
+* add state upgraders to 95+ resources to lay the foundation for replacing Grit
   (still under active development)
-- **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
-- **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
-- **dns_record:** add state migration handler for SDKv2 to Framework conversion
-- **leaked_credential_check:** add import functionality and tests
-- **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
-- **pages_project:** add state migration handlers
-- **tiered_cache:** add state migration handlers
-- **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
+* **certificate_pack:** add state migration handler for SDKv2 to Framework conversion
+* **custom_hostname_fallback_origin:** add comprehensive lifecycle test and migration support
+* **dns_record:** add state migration handler for SDKv2 to Framework conversion
+* **leaked_credential_check:** add import functionality and tests
+* **load_balancer_pool:** add state migration handler with detection for v4 vs v5 format
+* **pages_project:** add state migration handlers
+* **tiered_cache:** add state migration handlers
+* **zero_trust_dlp_predefined_profile:** deprecate `entries` field in favor of `enabled_entries`
 
 ### For more information
-
 - [Terraform Provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
 - [Documentation on using Terraform with Cloudflare](/terraform/)
 - [List of stabilized resources](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)
diff --git a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
index c9633450d6adb47..6681382c7d1ae98 100644
--- a/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
+++ b/src/content/changelog/terraform/2026-04-24-terraform-v5.19.0-provider.mdx
@@ -32,7 +32,6 @@ Terraform Provider v5.19.0 introduces 14 new resources spanning AI Gateway, Pipe
 ### V4 to V5 Migration State Upgraders
 
 State upgraders added for seamless migration from v4 to v5 for the following resources:
-
 - account
 - account_member
 - account_token
diff --git a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
index 1acd6e85a6a432f..4aa693f7bd56a44 100644
--- a/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
+++ b/src/content/changelog/terraform/2026-04-24-tf-migrate-tool-released.mdx
@@ -6,11 +6,11 @@ products:
   - terraform
 ---
 
-We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5.
+We're excited to announce **tf-migrate**, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5. 
 
 ## v5 is stable and ready for production
 
-**Terraform Provider v5 is stable and actively receiving updates.** We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
+**Terraform Provider v5 is stable and actively receiving updates.**  We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.
 
 Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool we're providing to the community — ensuring the best possible migration experience.
 
@@ -24,7 +24,7 @@ Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool w
 - **Cross-file reference updates** – Automatically finds and updates all references to renamed resources across your entire configuration
 - **Dry-run mode** – Preview all changes before applying them to ensure safety
 
-Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest.
+Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest. 
 
 ## Supported resources
 
diff --git a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
index 968781b659c1aca..d669da557298f32 100644
--- a/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
+++ b/src/content/changelog/tunnel/2025-07-15-udp-improvements.mdx
@@ -14,8 +14,7 @@ Your real-time applications running over [Cloudflare Tunnel](/cloudflare-one/net
 This is a foundational improvement to Cloudflare Tunnel, delivered automatically to all customers. There are no settings to configure — your UDP traffic is already flowing faster and more reliably.
 
 **What’s new:**
-
 - **Faster UDP performance**: We've significantly reduced the latency for establishing new UDP sessions, making applications like private DNS much more responsive.
 - **Greater reliability for mixed traffic**: UDP packets are no longer affected by heavy TCP traffic, preventing timeouts and connection drops for your real-time services.
 
-Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
+Learn more about running [TCP or UDP applications](/reference-architecture/architectures/sase/#connecting-applications) and [private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) through [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
index e857486e0668872..4ed43b589b89d2e 100644
--- a/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
+++ b/src/content/changelog/tunnel/2025-09-02-tunnel-networks-list-endpoints-new-default.mdx
@@ -13,22 +13,22 @@ Starting **December 1, 2025**, list endpoints for the [Cloudflare Tunnel API](/a
 No action is required if you already explicitly set `is_deleted=false` or if you only need to list active resources.
 
 This change affects the following API endpoints:
-
-- List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
-- List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
-- List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
-- List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
-- List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
-- List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
+* List all tunnels: [`GET /accounts/{account_id}/tunnels`](/api/resources/zero_trust/subresources/tunnels/methods/list/)
+* List [Cloudflare Tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/): [`GET /accounts/{account_id}/cfd_tunnel`](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/list/)
+* List [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [`GET /accounts/{account_id}/warp_connector`](/api/resources/zero_trust/subresources/tunnels/subresources/warp_connector/methods/list/)
+* List tunnel routes: [`GET /accounts/{account_id}/teamnet/routes`](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/list/)
+* List subnets: [`GET /accounts/{account_id}/zerotrust/subnets`](/api/resources/zero_trust/subresources/networks/subresources/subnets/methods/list/)
+* List virtual networks: [`GET /accounts/{account_id}/teamnet/virtual_networks`](/api/resources/zero_trust/subresources/networks/subresources/virtual_networks/methods/list/)
 
 ## What is changing?
 
 The default behavior of the `is_deleted` query parameter will be updated.
 
-| Scenario                          | Previous behavior (before December 1, 2025)                                | New behavior (from December 1, 2025)                                  |
-| :-------------------------------- | :------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
+| Scenario | Previous behavior (before December 1, 2025) | New behavior (from December 1, 2025) |
+| :--- | :--- | :--- |
 | `is_deleted` parameter is omitted | Returns **active & deleted** tunnels, routes, subnets and virtual networks | Returns **only active** tunnels, routes, subnets and virtual networks |
 
+
 ## Action required
 
 If you need to retrieve deleted (or all) resources, please update your API calls to explicitly include the `is_deleted` parameter before **December 1, 2025**.
@@ -48,11 +48,9 @@ curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/virtual_
 Following this change, retrieving a complete list of both active and deleted resources will require two separate API calls: one to get active items (by omitting the parameter or using `is_deleted=false`) and one to get deleted items (`is_deleted=true`).
 
 ## Why we’re making this change
-
 This update is based on user feedback and aims to:
+* **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
+* **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
+* **Improve performance:** For most users, the default query result will now be smaller and more relevant.
 
-- **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
-- **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
-- **Improve performance:** For most users, the default query result will now be smaller and more relevant.
-
-To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
+To learn more, please visit the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/) and [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/) documentation.
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
index bc751a65e2b32ff..947de730982905f 100644
--- a/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
+++ b/src/content/changelog/tunnel/2025-09-18-tunnel-hostname-routing.mdx
@@ -16,7 +16,6 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 ![Hostname-based routing in Cloudflare Tunnel](~/assets/images/changelog/cloudflare-one/tunnel-hostname-routing.webp)
 
 **What’s new:**
-
 - **Hostname & Domain Routing**: Create routes for individual hostnames (e.g., `payroll.acme.local`) or entire domains (e.g., `*.acme.local`) and direct their traffic to a specific Tunnel.
 - **Simplified Zero Trust Policies**: Build resilient policies in Cloudflare Access and Gateway using stable hostnames, making it dramatically easier to apply per-resource authorization for your private applications.
 - **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
@@ -24,4 +23,4 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 
 Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) or [public hostname](/cloudflare-one/traffic-policies/egress-policies/egress-cloudflared/) route.
 
-Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
+Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).
\ No newline at end of file
diff --git a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
index 35c45b7766d212a..b4bdbe1014ee162 100644
--- a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
+++ b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx
@@ -13,4 +13,4 @@ You can now `ping` the WARP Connector host directly on its LAN IP address immedi
 
 Starting with [version 2025.10.186.0](/changelog/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability.
 
-Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
+Learn more about deploying [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/).
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-07-14-waf-release.mdx b/src/content/changelog/waf/2025-07-14-waf-release.mdx
index 3657b790de4b853..27ee5690579c07e 100644
--- a/src/content/changelog/waf/2025-07-14-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-14-waf-release.mdx
@@ -13,6 +13,7 @@ This week’s vulnerability analysis highlights emerging web application threats
 - XSS – Attribute Overloading: A novel cross-site scripting technique where attackers abuse custom or non-standard HTML attributes to smuggle payloads into the DOM. These payloads evade traditional sanitization logic, especially in frameworks that loosely validate attributes or trust unknown tokens.
 - XSS – onToggle Event Abuse: Exploits the lesser-used onToggle event (triggered by elements like `<details>`) to execute arbitrary JavaScript when users interact with UI elements. This vector is often overlooked by static analyzers and can be embedded in seemingly benign components.
 
+
 **Impact**
 
 These vulnerabilities target both user-facing components and back-end databases, introducing potential vectors for credential theft, session hijacking, or full data exfiltration. The XSS variants bypass conventional filters through overlooked HTML behaviors, while the obfuscated SQLi enables attackers to stealthily probe back-end logic, making them especially difficult to detect and block.
diff --git a/src/content/changelog/waf/2025-07-21-emergency.mdx b/src/content/changelog/waf/2025-07-21-emergency.mdx
index 190744a1169aa10..ce9154530bc73e3 100644
--- a/src/content/changelog/waf/2025-07-21-emergency.mdx
+++ b/src/content/changelog/waf/2025-07-21-emergency.mdx
@@ -29,30 +29,30 @@ Together, these vulnerabilities significantly weaken the security posture of on-
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
+       <tbody>
+ 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
-				<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
+					<RuleID id="34dac2b38b904163bc587cc32168f6f0" />
 			</td>
 			<td>100817</td>
 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53770</td>
 			<td>N/A</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
-		</tr>
-		<tr>
+ 		</tr>
+ 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d21f327516a145bc9d1b05678de656c4" />
-			</td>
-			<td>100818</td>
-			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
+ 			<td>
+ 					<RuleID id="d21f327516a145bc9d1b05678de656c4" />
+ 			</td>
+ 			<td>100818</td>
+ 			<td>Microsoft SharePoint - Deserialization - CVE:CVE-2025-53771</td>
+ 			<td>N/A</td>
+ 			<td>Block</td>
+ 			<td>This is a New Detection</td>
 		</tr>
-	</tbody>
+  </tbody>
 </table>
 
-For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
+For more details, also refer to [our blog](https://blog.cloudflare.com/cloudflare-protects-against-critical-sharepoint-vulnerability-cve-2025-53770/).
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-07-28-waf-release.mdx b/src/content/changelog/waf/2025-07-28-waf-release.mdx
index c04a253ad3d3a3e..3374f46caf0c044 100644
--- a/src/content/changelog/waf/2025-07-28-waf-release.mdx
+++ b/src/content/changelog/waf/2025-07-28-waf-release.mdx
@@ -8,6 +8,7 @@ import { RuleID } from "~/components";
 
 This week’s update spotlights several vulnerabilities across Apache Tomcat, MongoDB, and Fortinet FortiWeb. Several flaws related with a memory leak in Apache Tomcat can lead to a denial-of-service attack. Additionally, a code injection flaw in MongoDB's Mongoose library allows attackers to bypass security controls to access restricted data.
 
+
 **Key Findings**
 
 - Fortinet FortiWeb (CVE-2025-25257): An improper neutralization of special elements used in a SQL command vulnerability in Fortinet FortiWeb versions allows an unauthenticated attacker to execute unauthorized SQL code or commands.
@@ -72,9 +73,7 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="f9e01e28c5d6499cac66364b4b6a5bb1" />
 			</td>
 			<td>100815</td>
-			<td>
-				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
-			</td>
+			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -85,12 +84,10 @@ These vulnerabilities target user-facing components, web application servers, an
 				<RuleID id="700d4fcc7b1f481a80cbeee5688f8e79" />
 			</td>
 			<td>100816</td>
-			<td>
-				MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061
-			</td>
+			<td>MongoDB - Remote Code Execution - CVE:CVE-2024-53900, CVE:CVE-2025-23061</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-04-waf-release.mdx b/src/content/changelog/waf/2025-08-04-waf-release.mdx
index b0e648fc90a3a62..f8f5bc852842740 100644
--- a/src/content/changelog/waf/2025-08-04-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-04-waf-release.mdx
@@ -35,110 +35,105 @@ The Grafana cross-site scripting (XSS) flaw can be used to hijack authenticated
 Meanwhile, the information disclosure flaw in WordPress core provides attackers with valid user emails, fueling targeted phishing campaigns that aim to secure the same account access achievable through the other exploits.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b8ab4644f8044f3485441ee052f30a13" />
-			</td>
-			<td>100535A</td>
-			<td>
-				Sitecore - Dangerous File Upload - CVE:CVE-2025-34510,
-				CVE:CVE-2025-34511
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
-			</td>
-			<td>100535</td>
-			<td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
-			</td>
-			<td>100543</td>
-			<td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
-			</td>
-			<td>100545</td>
-			<td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="28108d25f1cf470c8e7648938f634977" />
-			</td>
-			<td>100820</td>
-			<td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
-			</td>
-			<td>100821</td>
-			<td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
-			</td>
-			<td>100822</td>
-			<td>
-				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="69d43d704b0641898141a4300bf1b661" />
-			</td>
-			<td>100823</td>
-			<td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b8ab4644f8044f3485441ee052f30a13" />
+      </td>
+      <td>100535A</td>
+      <td>Sitecore - Dangerous File Upload - CVE:CVE-2025-34510, CVE:CVE-2025-34511</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="06d1fe0bd6e44d868e6b910b5045a97f" />
+      </td>
+      <td>100535</td>
+      <td>Sitecore - Information Disclosure - CVE:CVE-2025-34509</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f71ce87ea6e54eab999223df579cd3e0" />
+      </td>
+      <td>100543</td>
+      <td>Grafana - Directory Traversal - CVE:CVE-2025-4123</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="bba3d37891a440fb8bc95b970cbd9abc" />
+      </td>
+      <td>100545</td>
+      <td>WordPress - Information Disclosure - CVE:CVE-2023-5561</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="28108d25f1cf470c8e7648938f634977" />
+      </td>
+      <td>100820</td>
+      <td>CentOS WebPanel - Remote Code Execution - CVE:CVE-2025-48703</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9d69c796a61444a3aca33dc282ae64c1" />
+      </td>
+      <td>100821</td>
+      <td>LaRecipe - SSTI - CVE:CVE-2025-53833</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />
+      </td>
+      <td>100822</td>
+      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="69d43d704b0641898141a4300bf1b661" />
+      </td>
+      <td>100823</td>
+      <td>WordPress:Theme:Motors - Privilege Escalation - CVE:CVE-2025-4322</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
index e9deb9cfadebeca..e7e5dad628ec2f1 100644
--- a/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-07-emergency-waf-release.mdx
@@ -23,42 +23,39 @@ Adobe AEM’s remote code execution vulnerability enables attackers to run arbit
 These findings reinforce the urgency of updating to the patched versions — Squid 6.4 and Adobe AEM 6.5.24 or later — and reviewing configurations to prevent exploitation.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
-			</td>
-			<td>100844</td>
-			<td>
-				Adobe Experience Manager Forms - Remote Code Execution -
-				CVE:CVE-2025-54253
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
-			</td>
-			<td>100840</td>
-			<td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f61ed7c1e7e24c3380289e41ef7e015b" />
+      </td>
+      <td>100844</td>
+      <td>Adobe Experience Manager Forms - Remote Code Execution - CVE:CVE-2025-54253</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e76e65f5a3aa43f49e0684a6baec057a" />
+      </td>
+      <td>100840</td>
+      <td>Squid - Buffer Overflow - CVE:CVE-2025-54574</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-11-waf-release.mdx b/src/content/changelog/waf/2025-08-11-waf-release.mdx
index 74a303e3d74c2fb..62764e4b09840a6 100644
--- a/src/content/changelog/waf/2025-08-11-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-11-waf-release.mdx
@@ -8,21 +8,26 @@ import { RuleID } from "~/components";
 
 This week's update focuses on a wide range of enterprise software, from network infrastructure and security platforms to content management systems and development frameworks. Flaws include unsafe deserialization, OS command injection, SSRF, authentication bypass, and arbitrary file upload — many of which allow unauthenticated remote code execution. Notable risks include Cisco Identity Services Engine and Ivanti EPMM, where successful exploitation could grant attackers full administrative control of core network infrastructure and popular web services such as WordPress, SharePoint, and Ingress-Nginx, where security bypasses and arbitrary file uploads could lead to complete site or server compromise.
 
+
 **Key Findings**
 
 - Cisco Identity Services Engine (CVE-2025-20281): Insufficient input validation in a specific API of Cisco Identity Services Engine (ISE) and ISE-PIC allows an unauthenticated, remote attacker to execute arbitrary code with root privileges on an affected device.
 
 - Wazuh Server (CVE-2025-24016): An unsafe deserialization vulnerability in Wazuh Server (versions 4.4.0 to 4.9.0) allows for remote code execution and privilege escalation. By injecting unsanitized data, an attacker can trigger an exception to execute arbitrary code on the server.
 
+
 - CrushFTP (CVE-2025-54309): A flaw in AS2 validation within CrushFTP allows remote attackers to gain administrative access via HTTPS on systems not using the DMZ proxy feature. This flaw can lead to unauthorized file access and potential system compromise.
 
+
 - Kentico Xperience CMS (CVE-2025-2747, CVE-2025-2748): Vulnerabilities in Kentico Xperience CMS could enable cross-site scripting (XSS), allowing attackers to inject malicious scripts into web pages. Additionally, a flaw could allow unauthenticated attackers to bypass the Staging Sync Server's authentication, potentially leading to administrative control over the CMS.
 
+
 - Node.js (CVE-2025-27210): An incomplete fix for a previous vulnerability (CVE-2025-23084) in Node.js affects the `path.join()` API method on Windows systems. The vulnerability can be triggered using reserved Windows device names such as `CON`, `PRN`, or `AUX`.
 
-- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847):
-  This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
-  (Note: CVE-2025-34085 has been rejected as a duplicate.)
+- WordPress:Plugin:Simple File List (CVE-2025-34085, CVE-2020-36847): 
+This vulnerability in the Simple File List plugin for WordPress allows an unauthenticated remote attacker to upload arbitrary files to a vulnerable site. This can be exploited to achieve remote code execution on the server.<br/>
+(Note: CVE-2025-34085 has been rejected as a duplicate.)
+
 
 - GeoServer (CVE-2024-29198): A Server-Side Request Forgery (SSRF) vulnerability exists in GeoServer's Demo request endpoint, which can be exploited where the Proxy Base URL has not been configured.
 
@@ -32,239 +37,240 @@ This week's update focuses on a wide range of enterprise software, from network
 
 - Manager-IO (CVE-2025-54122): A critical unauthenticated full read Server-Side Request Forgery (SSRF) vulnerability is present in the proxy handler of both Manager Desktop and Server editions up to version 25.7.18.2519. This allows an unauthenticated attacker to bypass network isolation and access internal services.
 
-- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller.
+- Ingress-Nginx (CVE-2025-1974): A vulnerability in the Ingress-Nginx controller for Kubernetes allows an attacker to bypass access control rules. An unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. 
 
 - PaperCut NG/MF (CVE-2023-2533): A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PaperCut NG/MF. Under specific conditions, an attacker could exploit this to alter security settings or execute arbitrary code if they can deceive an administrator with an active login session into clicking a malicious link.
 
 - SonicWall SMA (CVE-2025-40598): This vulnerability could allow an unauthenticated attacker to bypass security controls. This allows a remote, unauthenticated attacker to potentially execute arbitrary JavaScript code.
 
-- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
+- WordPress (CVE-2025-5394): The "Alone – Charity Multipurpose Non-profit WordPress Theme" for WordPress  is vulnerable to arbitrary file uploads. A missing capability check allows unauthenticated attackers to upload ZIP files containing webshells disguised as plugins, leading to remote code execution.
+
 
 **Impact**
 
 These vulnerabilities span a broad range of enterprise technologies, including network access control systems, monitoring platforms, web servers, CMS platforms, cloud services, and collaboration tools. Exploitation techniques range from remote code execution and command injection to authentication bypass, SQL injection, path traversal, and configuration weaknesses.
 
-A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers.
+A critical flaw in perimeter devices like Ivanti EPMM or SonicWall SMA could allow an unauthenticated attacker to gain remote code execution, completely breaching the primary network defense. A separate vulnerability within Cisco's Identity Services Engine could then be exploited to bypass network segmentation, granting an attacker widespread internal access. Insecure deserialization issues in platforms like Wazuh Server and CrushFTP could then be used to run malicious payloads or steal sensitive files from administrative consoles. Weaknesses in web delivery controllers like Ingress-Nginx or popular content management systems such as WordPress, SharePoint, and Kentico Xperience create vectors to bypass security controls, exfiltrate confidential data, or fully compromise servers. 
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ec6480c81253494b947d891e51bc8df1" />
-			</td>
-			<td>100538</td>
-			<td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
-			</td>
-			<td>100548</td>
-			<td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
-			</td>
-			<td>100550</td>
-			<td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e1369c5d629f4f10a14141381dca5738" />
-			</td>
-			<td>100562</td>
-			<td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
-			</td>
-			<td>100565</td>
-			<td>
-				Cisco Identity Services Engine - Remote Code Execution -
-				CVE:CVE-2025-20281
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed759f7e44184fa398ef71785d8102e1" />
-			</td>
-			<td>100567</td>
-			<td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="71b8e7b646f94d79873213cd99105c43" />
-			</td>
-			<td>100569</td>
-			<td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
-			</td>
-			<td>100571</td>
-			<td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
-			</td>
-			<td>100573</td>
-			<td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
-			</td>
-			<td>100806</td>
-			<td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
-			</td>
-			<td>100824</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3638baed75924604987b86d874920ace" />
-			</td>
-			<td>100824A</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
-			</td>
-			<td>100825</td>
-			<td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
-			</td>
-			<td>100826</td>
-			<td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
-			</td>
-			<td>100827</td>
-			<td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54dd826f578c483196ce852b6f1c2d12" />
-			</td>
-			<td>100828</td>
-			<td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a2867f7456c14213a94509a40341fccc" />
-			</td>
-			<td>100829</td>
-			<td>
-				WordPress:Plugin:Simple File List - Remote Code Execution -
-				CVE:CVE-2025-34085
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4cdb0e792d1a428a897526624cefeeda" />
-			</td>
-			<td>100829A</td>
-			<td>
-				WordPress:Plugin:Simple File List - Remote Code Execution -
-				CVE:CVE-2025-34085 - 2
-			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ec6480c81253494b947d891e51bc8df1" />
+      </td>
+      <td>100538</td>
+      <td>GeoServer - SSRF - CVE:CVE-2024-29198</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b8cb07170b5e4c2b989119cac9e0b290" />
+      </td>
+      <td>100548</td>
+      <td>Ivanti EPMM - Remote Code Execution - CVE:CVE-2025-6771</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b3524bf5f5174b65bc892122ad93cda8" />
+      </td>
+      <td>100550</td>
+      <td>Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38018</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e1369c5d629f4f10a14141381dca5738" />
+      </td>
+      <td>100562</td>
+      <td>Manager-IO - SSRF - CVE:CVE-2025-54122</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="136f67e2b6a84f15ab9a82a52e9137e1" />
+      </td>
+      <td>100565</td>
+      <td>
+        Cisco Identity Services Engine - Remote Code Execution -
+        CVE:CVE-2025-20281
+      </td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed759f7e44184fa398ef71785d8102e1" />
+      </td>
+      <td>100567</td>
+      <td>Ingress-Nginx - Remote Code Execution - CVE:CVE-2025-1974</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="71b8e7b646f94d79873213cd99105c43" />
+      </td>
+      <td>100569</td>
+      <td>PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2450bfbb0cfb4804b109d1c42c81dc88" />
+      </td>
+      <td>100571</td>
+      <td>SonicWall SMA - XSS - CVE:CVE-2025-40598</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8ce1903b67e24205a93f5fe6926c96d4" />
+      </td>
+      <td>100573</td>
+      <td>WordPress - Dangerous File Upload - CVE:CVE-2025-5394</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7fdb3c7bc7b74703aeef4ab240ec2fda" />
+      </td>   
+      <td>100806</td>      
+      <td>Wazuh Server - Remote Code Execution - CVE:CVE-2025-24016</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="fe088163f51f4928a3c8d91e2401fa3b" />
+      </td>
+      <td>100824</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3638baed75924604987b86d874920ace" />
+      </td>
+      <td>100824A</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 2</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="dda4f95b3a3e4ebb9e194aa5c7e63549" />
+      </td>
+      <td>100825</td>
+      <td>AMI MegaRAC - Auth Bypass - CVE:CVE-2024-54085</td>
+      <td>Log</td>
+      <td>Block</td> 
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7dc07014cefa4ce9adf21da7b79037e6" />
+      </td>
+      <td>100826</td>
+      <td>Kentico Xperience CMS - Auth Bypass - CVE:CVE-2025-2747</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7c7a0a37e79a4949ba840c9acaf261aa" />
+      </td>
+      <td>100827</td>
+      <td>Kentico Xperience CMS - XSS - CVE:CVE-2025-2748</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="54dd826f578c483196ce852b6f1c2d12" />
+      </td>
+      <td>100828</td>
+      <td>Node.js - Directory Traversal - CVE:CVE-2025-27210</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a2867f7456c14213a94509a40341fccc" />
+      </td>
+      <td>100829</td>
+      <td>
+        WordPress:Plugin:Simple File List - Remote Code Execution -
+        CVE:CVE-2025-34085
+      </td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4cdb0e792d1a428a897526624cefeeda" />
+      </td>
+      <td>100829A</td>
+      <td>
+        WordPress:Plugin:Simple File List - Remote Code Execution -
+        CVE:CVE-2025-34085 - 2
+      </td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-18-waf-release.mdx b/src/content/changelog/waf/2025-08-18-waf-release.mdx
index 8f05b2eb924b63f..78b79350ea882e6 100644
--- a/src/content/changelog/waf/2025-08-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-18-waf-release.mdx
@@ -31,143 +31,138 @@ This week, a series of critical vulnerabilities were discovered impacting core e
 These vulnerabilities affect core infrastructure, from network security appliances like SonicWall to data platforms such as Apache Druid and ML frameworks like BentoML. The code execution and deserialization flaws are particularly severe, offering deep system access that allows attackers to steal data, disrupt services, and establish a foothold for broader intrusions. Simultaneously, SSRF and XXE vulnerabilities undermine network boundaries, exposing sensitive internal data and creating pathways for lateral movement. Beyond data-centric threats, flaws in edge devices like the Tenda router introduce the tangible risk of operational disruption, highlighting a multi-faceted threat to the security and stability of key enterprise systems.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
-			</td>
-			<td>100574</td>
-			<td>
-				SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819,
-				CVE:CVE-2025-32820, CVE:CVE-2025-32821
-			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
-			</td>
-			<td>100576</td>
-			<td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d62935357ff846d9adefb58108ac45b3" />
-			</td>
-			<td>100585</td>
-			<td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
-			</td>
-			<td>100834</td>
-			<td>
-				Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1474121b01ba40629f8246f8022ab542" />
-			</td>
-			<td>100835</td>
-			<td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
-			</td>
-			<td>100837</td>
-			<td>SQLi - OOB</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
-			</td>
-			<td>100841</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="40fd793035c947c5ac75add1739180d2" />
-			</td>
-			<td>100841A</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
-			</td>
-			<td>100841B</td>
-			<td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
-			</td>
-			<td>100845</td>
-			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
-			</td>
-			<td>100845A</td>
-			<td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="326ebb56d46a4c269bb699d3418d9a3b" />
+      </td>
+      <td>100574</td>
+      <td>SonicWall SMA - Remote Code Execution - CVE:CVE-2025-32819, CVE:CVE-2025-32820, CVE:CVE-2025-32821</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="69f4f161dec04aca8a73a3231e6fefdb" />
+      </td>
+      <td>100576</td>
+      <td>Ms-Swift Project - Remote Code Execution - CVE:CVE-2025-50460</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d62935357ff846d9adefb58108ac45b3" />
+      </td>
+      <td>100585</td>
+      <td>Apache Druid - Remote Code Execution - CVE:CVE-2023-25194</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4f6148a760804bf8ad8ebccfe4855472" />
+      </td>
+      <td>100834</td>
+      <td>Tenda AC8v4 - Auth Bypass - CVE:CVE-2025-51087, CVE:CVE-2025-51088</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="1474121b01ba40629f8246f8022ab542" />
+      </td>
+      <td>100835</td>
+      <td>Open WebUI - SSRF - CVE:CVE-2024-7959</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="96abffdb7e224ce69ddf89eb6339f132" />
+      </td>
+      <td>100837</td>
+      <td>SQLi - OOB</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a0b20ec638d14800a1d6827cb83d2625" />
+      </td>
+      <td>100841</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="40fd793035c947c5ac75add1739180d2" />
+      </td>
+      <td>100841A</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="08dcb20b9acf47e3880a0b886ab910c2" />
+      </td>
+      <td>100841B</td>
+      <td>BentoML - SSRF - CVE:CVE-2025-54381 - 3</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="309cfb7eeb42482e9ad896f12197ec51" />
+      </td>
+      <td>100845</td>
+      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6e039776c2d6418ab6e8f05196f34ce3" />
+      </td>
+      <td>100845A</td>
+      <td>Adobe Experience Manager Forms - XSS - CVE:CVE-2025-54254 - 2</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-08-25-waf-release.mdx b/src/content/changelog/waf/2025-08-25-waf-release.mdx
index 42c73f310668c3c..f78810c3fd8e64b 100644
--- a/src/content/changelog/waf/2025-08-25-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-25-waf-release.mdx
@@ -21,56 +21,50 @@ This week, critical vulnerabilities were disclosed that impact widely used open-
 These vulnerabilities pose severe risks to enterprise environments and open-source ecosystems. Remote code execution enables attackers to gain deep system access, steal data, disrupt services, and establish persistent footholds for broader intrusions. Given the widespread deployment of Apache HTTP Server and Laravel in production systems, timely patching and mitigation are critical.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c550282a0f7343ca887bdab528050359" />
-			</td>
-			<td>100822_BETA</td>
-			<td>
-				WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>
-				This was merged in to the original rule "WordPress:Plugin:WPBookit -
-				Remote Code Execution - CVE:CVE-2025-6058" (ID:{" "}
-				<RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
-			</td>
-			<td>100831</td>
-			<td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
-			</td>
-			<td>100846</td>
-			<td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c550282a0f7343ca887bdab528050359" />
+      </td>
+      <td>100822_BETA</td>
+      <td>WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This was merged in to the original rule "WordPress:Plugin:WPBookit - Remote Code Execution - CVE:CVE-2025-6058" (ID: <RuleID id="9b5c5e13d2ca4253a89769f2194f7b2d" />)</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="456b1e8f827b4ed89fb4a54b3bdcdbad" />
+      </td>
+      <td>100831</td>
+      <td>Apache HTTP Server - Code Execution - CVE:CVE-2024-38474</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7dcc01e1dd074e42a26c8ca002eaac5b" />
+      </td>
+      <td>100846</td>
+      <td>Laravel - Remote Code Execution - CVE:CVE-2024-55661</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
index 0d6fc5ee3b10133..e11552cfbac77e9 100644
--- a/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-08-29-emergency-waf-release.mdx
@@ -21,39 +21,39 @@ This week, new critical vulnerabilities were disclosed in Next.js’s image opti
 Exploitation could expose sensitive files, leak user or backend data, and undermine application trust. Given Next.js’s wide use, immediate patching and cache hardening are strongly advised.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
-			</td>
-			<td>100613</td>
-			<td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
-			</td>
-			<td>100616</td>
-			<td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ea55f8aac44246cc9b827eea9ff4bfe3" />
+      </td>
+      <td>100613</td>
+      <td>Next.js - Dangerous File Download - CVE:CVE-2025-55173</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e2b2d77a79cc4a76bf7ba53d69b9ea7d" />
+      </td>
+      <td>100616</td>
+      <td>Next.js - Information Disclosure - CVE:CVE-2025-57752</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-01-waf-release.mdx b/src/content/changelog/waf/2025-09-01-waf-release.mdx
index 88aa80a7543ddf4..5470b675623f1e5 100644
--- a/src/content/changelog/waf/2025-09-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-01-waf-release.mdx
@@ -10,48 +10,50 @@ import { RuleID } from "~/components";
 
 This week, a critical vulnerability was disclosed in Fortinet FortiWeb (versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and versions 7.0.10 and below), linked to improper parameter handling that could allow unauthorized access.
 
+
 **Key Findings**
 
-- Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
+* Fortinet FortiWeb (CVE-2025-52970): A vulnerability may allow an unauthenticated remote attacker with access to non-public information to log in as any existing user on the device via a specially crafted request.
 
 **Impact**
 
-Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended.
+Exploitation could allow an unauthenticated attacker to impersonate any existing user on the device, potentially enabling them to modify system settings or exfiltrate sensitive information, posing a serious security risk. Upgrading to the latest vendor-released version is strongly recommended. 
+
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="636b145a49a84946b990d4fac49b7cf8" />
-			</td>
-			<td>100586</td>
-			<td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
-			</td>
-			<td>100136C</td>
-			<td>XSS - JavaScript - Headers and Body</td>
-			<td>N/A</td>
-			<td>N/A</td>
-			<td>Rule metadata description refined. Detection unchanged.</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="636b145a49a84946b990d4fac49b7cf8" />
+      </td>
+      <td>100586</td>
+      <td>Fortinet FortiWeb - Auth Bypass - CVE:CVE-2025-52970</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b5ef1ace353841a0856b5e07790c9dde" />
+      </td>
+      <td>100136C</td>
+      <td>XSS - JavaScript - Headers and Body</td>
+      <td>N/A</td>
+      <td>N/A</td>
+      <td>Rule metadata description refined. Detection unchanged.</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
index 5855b853f30db8a..385a50fe802115e 100644
--- a/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-04-emergency-waf-release.mdx
@@ -12,7 +12,6 @@ This week, new critical vulnerabilities were disclosed in Sitecore’s Sitecore
 These flaws are caused by unsafe data deserialization and code reflection, leaving affected systems at high risk of exploitation.
 
 **Key Findings**
-
 - CVE-2025-53690: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53691: Remote Code Execution through Insecure Deserialization
 - CVE-2025-53693: HTML Cache Poisoning through Unsafe Reflections
@@ -22,50 +21,50 @@ These flaws are caused by unsafe data deserialization and code reflection, leavi
 Exploitation could allow attackers to execute arbitrary code remotely on the affected system and conduct cache poisoning attacks, potentially leading to further compromise. Applying the latest vendor-released solution without delay is strongly recommended.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
-			</td>
-			<td>100878</td>
-			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-			</td>
-			<td>100631</td>
-			<td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed94c7ce5301411a94a21a096c410240" />
-			</td>
-			<td>100879</td>
-			<td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="588edc74df1f4609b3c2f7ef0ee2c15e" />
+      </td>
+      <td>100878</td>
+      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53691</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d1bd7563e6254db48ce703807c5b669c" />
+      </td>
+      <td>100631</td>
+      <td>Sitecore - Cache Poisoning - CVE:CVE-2025-53693</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed94c7ce5301411a94a21a096c410240" />
+      </td>
+      <td>100879</td>
+      <td>Sitecore - Remote Code Execution - CVE:CVE-2025-53690</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-08-waf-release.mdx b/src/content/changelog/waf/2025-09-08-waf-release.mdx
index ccc94cccb99a6c9..1784243e8d5d2af 100644
--- a/src/content/changelog/waf/2025-09-08-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-08-waf-release.mdx
@@ -6,21 +6,21 @@ date: 2025-09-08
 
 import { RuleID } from "~/components";
 
-**This week's update**
+**This week's update** 
 
 This week’s focus highlights newly disclosed vulnerabilities in web frameworks, enterprise applications, and widely deployed CMS plugins. The vulnerabilities include SSRF, authentication bypass, arbitrary file upload, and remote code execution (RCE), exposing organizations to high-impact risks such as unauthorized access, system compromise, and potential data exposure. In addition, security rule enhancements have been deployed to cover general command injection and server-side injection attacks, further strengthening protections.
 
 **Key Findings**
 
-- Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
+* Next.js (CVE-2025-57822): Improper handling of redirects in custom middleware can lead to server-side request forgery (SSRF) when user-supplied headers are forwarded. Attackers could exploit this to access internal services or cloud metadata endpoints. The issue has been resolved in versions 14.2.32 and 15.4.7. Developers using custom middleware should upgrade and verify proper redirect handling in `next()` calls.
 
-- ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
+* ScriptCase (CVE-2025-47227, CVE-2025-47228): In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), two vulnerabilities allow attackers to reset admin accounts and execute system commands, potentially leading to full compromise of affected deployments.
 
-- Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
+* Sar2HTML (CVE-2025-34030): In Sar2HTML version 3.2.2 and earlier, insufficient input sanitization of the plot parameter allows remote, unauthenticated attackers to execute arbitrary system commands. Exploitation could compromise the underlying server and its data.
 
-- Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
+* Zhiyuan OA (CVE-2025-34040): An arbitrary file upload vulnerability exists in the Zhiyuan OA platform. Improper validation in the `wpsAssistServlet` interface allows unauthenticated attackers to upload crafted files via path traversal, which can be executed on the web server, leading to remote code execution.
 
-- WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
+* WordPress:Plugin:InfiniteWP Client (CVE-2020-8772): A vulnerability in the InfiniteWP Client plugin allows attackers to perform restricted actions and gain administrative control of connected WordPress sites.
 
 **Impact**
 
@@ -29,128 +29,116 @@ These vulnerabilities could allow attackers to gain unauthorized access, execute
 Administrators are strongly advised to apply vendor patches immediately, remove unsupported software, and review authentication and access controls to mitigate these risks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
-			</td>
-			<td>100007D</td>
-			<td>Command Injection - Common Attack Commands Args</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "Command Injection -
-				Common Attack Commands" (ID:{" "}
-				<RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers
-				only.
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cd528243d6824f7ab56182988230a75b" />
-			</td>
-			<td>100617</td>
-			<td>Next.js - SSRF - CVE:CVE-2025-57822</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
-			</td>
-			<td>100659_BETA</td>
-			<td>Common Payloads for Server-Side Template Injection - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Common Payloads for
-				Server-Side Template Injection" (ID:{" "}
-				<RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
-			</td>
-			<td>100824B</td>
-			<td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
-			</td>
-			<td>100848</td>
-			<td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
-			</td>
-			<td>100849</td>
-			<td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e7464139fd3e44938b56716bef971afd" />
-			</td>
-			<td>100872</td>
-			<td>
-				WordPress:Plugin:InfiniteWP Client - Missing Authorization -
-				CVE:CVE-2020-8772
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
-			</td>
-			<td>100873</td>
-			<td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
-			</td>
-			<td>100875</td>
-			<td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7c5812a31fd94996b3299f7e963d7afc" />
+      </td>
+      <td>100007D</td>
+      <td>Command Injection - Common Attack Commands Args</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "Command Injection - Common Attack Commands" (ID: <RuleID id="89557ce9b26e4d4dbf29e90c28345b9b" />) for New WAF customers only.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cd528243d6824f7ab56182988230a75b" />
+      </td>      
+      <td>100617</td>
+      <td>Next.js - SSRF - CVE:CVE-2025-57822</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="503b337dac5c409d8f833a6ba22dabf1" />
+      </td>
+      <td>100659_BETA</td>
+      <td>Common Payloads for Server-Side Template Injection - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "Common Payloads for Server-Side Template Injection" (ID: <RuleID id="21c7a963e1b749e7b1753238a28a42c4" />)</td>
+    </tr>    
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6d24266148f24f5e9fa487f8b416b7ca" />
+      </td>
+      <td>100824B</td>
+      <td>CrushFTP - Remote Code Execution - CVE:CVE-2025-54309 - 3</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>    
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="154b217c43d04f11a13aeff05db1fa6b" />
+      </td>
+      <td>100848</td>
+      <td>ScriptCase - Auth Bypass - CVE:CVE-2025-47227</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cad6f1c8c6d44ef59929e6532c62d330" />
+      </td>
+      <td>100849</td>
+      <td>ScriptCase - Command Injection - CVE:CVE-2025-47228</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e7464139fd3e44938b56716bef971afd" />
+      </td>
+      <td>100872</td>
+      <td>WordPress:Plugin:InfiniteWP Client - Missing Authorization - CVE:CVE-2020-8772</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0181ebb2cc234f2d863412e1bab19b0b" />
+      </td>
+      <td>100873</td>
+      <td>Sar2HTML - Command Injection - CVE:CVE-2025-34030</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="34d5c7c7b08b40eaad5b2bb3f24c0fbe" />
+      </td>
+      <td>100875</td>
+      <td>Zhiyuan OA - Remote Code Execution - CVE:CVE-2025-34040</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>    
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-15-waf-release.mdx b/src/content/changelog/waf/2025-09-15-waf-release.mdx
index 56e8dbc6e1051d7..d6bb571fc9be330 100644
--- a/src/content/changelog/waf/2025-09-15-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-15-waf-release.mdx
@@ -12,11 +12,11 @@ This week's focus highlights newly disclosed vulnerabilities in DevOps tooling,
 
 **Key Findings**
 
-- Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
+* Argo CD (CVE-2025-55190): Exposure of sensitive information could allow attackers to access credential data stored in configurations, potentially leading to compromise of Kubernetes workloads and secrets.
 
-- DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
+* DataEase (CVE-2025-57773): Insufficient input validation enables JNDI injection and insecure deserialization, resulting in remote code execution (RCE). Successful exploitation grants attackers control over the application server.
 
-- Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
+* Sitecore (CVE-2025-53694): A sensitive information disclosure flaw allows unauthorized access to confidential information stored in Sitecore deployments, raising the risk of data breaches and privilege escalation.
 
 **Impact**
 
@@ -25,50 +25,50 @@ These vulnerabilities expose organizations to serious risks, including credentia
 Administrators are strongly advised to apply vendor patches immediately, rotate exposed credentials, and review access controls to mitigate these risks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
-			</td>
-			<td>100646</td>
-			<td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
-			</td>
-			<td>100874</td>
-			<td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
-			</td>
-			<td>100880</td>
-			<td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="199cce9ab21e40bcb535f01b2ee2085f" />
+      </td>
+      <td>100646</td>
+      <td>Argo CD - Information Disclosure - CVE:CVE-2025-55190s</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e513bb21b6a44f9cbfcd2462f5e20788" />
+      </td>
+      <td>100874</td>
+      <td>DataEase - JNDI injection - CVE:CVE-2025-57773</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="be097f5a71a04f27aa87b60d005a12fd" />
+      </td>
+      <td>100880</td>
+      <td>Sitecore - Information Disclosure - CVE:CVE-2025-53694</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-22-waf-release.mdx b/src/content/changelog/waf/2025-09-22-waf-release.mdx
index 054a8348718a766..fd3fff204e42727 100644
--- a/src/content/changelog/waf/2025-09-22-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-22-waf-release.mdx
@@ -10,125 +10,124 @@ This week emphasizes two critical vendor-specific vulnerabilities: a full elevat
 
 **Key Findings**
 
-- Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges.
 
-- Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind).
+* Azure (CVE-2025-54914): Vulnerability in Azure Networking allowing elevation of privileges. 
 
-- Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
+* Skyvern (CVE-2025-49619): Skyvern ≤ 0.1.85 has a server-side template injection (SSTI) vulnerability in its Prompt field (workflow blocks) via Jinja2. Authenticated users with low privileges can get remote code execution (blind). 
+
+* Generic SQLi / SSRF improvements: Expanded rule coverage to detect obfuscated SQL injection patterns and SSRF across host, local, and cloud contexts.
 
 **Impact**
 
 These vulnerabilities allow attackers to escalate privileges or execute code under conditions where previously they could not:
 
-- Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components.
+* Azure CVE-2025-54914 enables an attacker from the network with no credentials to gain high-level access within Azure Networking; could lead to full compromise of networking components. 
+
+* Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components. 
 
-- Skyvern CVE-2025-49619 allows authenticated users with minimal privilege to exploit SSTI for remote code execution, undermining isolation of workflow components.
+* The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
-- The improvements for SQLi and SSRF reduce risk from common injection and request-based attacks.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
-			</td>
-			<td>100146</td>
-			<td>SSRF - Host - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
-			</td>
-			<td>100146B</td>
-			<td>SSRF - Local - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
-			</td>
-			<td>100146C</td>
-			<td>SSRF - Cloud - 2</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="78c856218f2d40f4b5988c8c956c1961" />
-			</td>
-			<td>100714</td>
-			<td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
-			</td>
-			<td>100758</td>
-			<td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
-			</td>
-			<td>100773</td>
-			<td>Next.js - SSRF</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
-			</td>
-			<td>100774</td>
-			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
-			</td>
-			<td>100800_BETA</td>
-			<td>SQLi - Obfuscated Boolean - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule (ID:{" "}
-				<RuleID id="7663ea44178441a0b3205c145563445f" />)
-			</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c36a425ae0c94789a9bc34f06a135cbf" />
+      </td>
+      <td>100146</td>
+      <td>SSRF - Host - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="dfa84b0aed5a4b45b953a36a57035abf" />
+      </td>
+      <td>100146B</td>
+      <td>SSRF - Local - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="276073e60c7a4b4d91faba1fbbe18d50" />
+      </td>
+      <td>100146C</td>
+      <td>SSRF - Cloud - 2</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="78c856218f2d40f4b5988c8c956c1961" />
+      </td>
+      <td>100714</td>
+      <td>Azure - Auth Bypass - CVE:CVE-2025-54914</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9f1c8d4cbf3848dbb940771bc5ced231" />
+      </td>
+      <td>100758</td>
+      <td>Skyvern - Remote Code Execution - CVE:CVE-2025-49619</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6be7e7829f3b43c688e1ac4284a619a1" />
+      </td>
+      <td>100773</td>
+      <td>Next.js - SSRF</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0cc3f50216bf4b448210bcc3983ff2dd" />
+      </td>
+      <td>100774</td>
+      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="53bfaeb311a049e3877fa15c0380a1a6" />
+      </td>
+      <td>100800_BETA</td>
+      <td>SQLi - Obfuscated Boolean - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule (ID: <RuleID id="7663ea44178441a0b3205c145563445f" />)</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
index 05259d94a3946ba..2a09bf015de4913 100644
--- a/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-24-emergency-waf-release.mdx
@@ -10,35 +10,35 @@ This week highlights a critical vendor-specific vulnerability: a deserialization
 
 **Key Findings**
 
-- GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
+* GoAnywhere MFT (CVE-2025-10035): Deserialization vulnerability in the License Servlet that allows attackers with a forged license response signature to deserialize arbitrary objects, potentially resulting in command injection.
 
 **Impact**
 
 GoAnywhere MFT (CVE-2025-10035): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
-			</td>
-			<td>100787</td>
-			<td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8fe242c7c0d64d689f4fc9a1e08b39f3" />
+      </td>
+      <td>100787</td>
+      <td>Fortra GoAnywhere - Auth Bypass - CVE:CVE-2025-10035</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-26-waf-release.mdx b/src/content/changelog/waf/2025-09-26-waf-release.mdx
index aeb564538854fe1..b7e0125e8fa0a1a 100644
--- a/src/content/changelog/waf/2025-09-26-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-26-waf-release.mdx
@@ -11,138 +11,138 @@ import { RuleID } from "~/components";
 This update introduces 11 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
-			</td>
-			<td>100859A</td>
-			<td>SQLi - UNION - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
-			</td>
-			<td>100889</td>
-			<td>Command Injection - Generic 9</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c15ca8e8290f485287037665f2be3ddf" />
-			</td>
-			<td>100890</td>
-			<td>Information Disclosure - Common Files - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="56669615f2984c2cac8c608980a252a8" />
-			</td>
-			<td>100891</td>
-			<td>Anomaly:URL - Relative Paths</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c41789fb6370431d809567d17e7d3865" />
-			</td>
-			<td>100894</td>
-			<td>XSS - Inline Function</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
-			</td>
-			<td>100895</td>
-			<td>XSS - DOM</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab8277e3f432400bbd9403dd42978e38" />
-			</td>
-			<td>100896</td>
-			<td>SQLi - MSSQL Length Enumeration</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-			</td>
-			<td>100897</td>
-			<td>Generic Rules - Code Injection - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4375dc90c7af4c55908f6b95c1686741" />
-			</td>
-			<td>100898</td>
-			<td>SQLi - Evasion</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
-			</td>
-			<td>100899</td>
-			<td>SQLi - Probing 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2c20b5e8684043f48620ff77b4026c88" />
-			</td>
-			<td>100900</td>
-			<td>SQLi - Probing</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
+      </td>
+      <td>100859A</td>
+      <td>SQLi - UNION - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="91d9cf56355b4ab88481b2fd4de80468" />
+      </td>
+      <td>100889</td>
+      <td>Command Injection - Generic 9</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c15ca8e8290f485287037665f2be3ddf" />
+      </td>
+      <td>100890</td>
+      <td>Information Disclosure - Common Files - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="56669615f2984c2cac8c608980a252a8" />
+      </td>
+      <td>100891</td>
+      <td>Anomaly:URL - Relative Paths</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c41789fb6370431d809567d17e7d3865" />
+      </td>
+      <td>100894</td>
+      <td>XSS - Inline Function</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b995d0b930604fa6b8d9b2a13792565c" />
+      </td>
+      <td>100895</td>
+      <td>XSS - DOM</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab8277e3f432400bbd9403dd42978e38" />
+      </td>
+      <td>100896</td>
+      <td>SQLi - MSSQL Length Enumeration</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+      </td>
+      <td>100897</td>
+      <td>Generic Rules - Code Injection - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4375dc90c7af4c55908f6b95c1686741" />
+      </td>
+      <td>100898</td>
+      <td>SQLi - Evasion</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="945c5aa9f45141dd872d7ec920999be0" />
+      </td>
+      <td>100899</td>
+      <td>SQLi - Probing 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2c20b5e8684043f48620ff77b4026c88" />
+      </td>
+      <td>100900</td>
+      <td>SQLi - Probing</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
index 73bca3b78f919ec..93fe72102454c07 100644
--- a/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-28-emergency-waf-release.mdx
@@ -10,52 +10,46 @@ This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CV
 
 **Key Findings**
 
-- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
 Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
-			</td>
-			<td>100788</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="51de6ce6596a40eb8200452ad30f768e" />
-			</td>
-			<td>100788A</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a1bef4ada0b146d2862cad439ee0ab84" />
+      </td>
+      <td>100788</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="51de6ce6596a40eb8200452ad30f768e" />
+      </td>
+      <td>100788A</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-09-29-waf-release.mdx b/src/content/changelog/waf/2025-09-29-waf-release.mdx
index e4a7094b34030a4..b48fadd2caabecb 100644
--- a/src/content/changelog/waf/2025-09-29-waf-release.mdx
+++ b/src/content/changelog/waf/2025-09-29-waf-release.mdx
@@ -10,85 +10,82 @@ This week highlights four important vendor- and component-specific issues: an au
 
 **Key Findings**
 
-- SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
+* SimpleHelp (CVE-2024-57727): Authentication bypass in SimpleHelp that can allow unauthorized access to management interfaces or sessions.
 
-- Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
+* Flowise Cloud (CVE-2025-58434): Information-disclosure vulnerability in Flowise Cloud that may expose sensitive configuration or user data to unauthenticated or low-privileged actors.
 
-- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
+* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF in the Ditty WordPress plugin enabling server-side requests that could reach internal services or cloud metadata endpoints.
 
-- Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
+* Vite (CVE-2025-30208): Directory-traversal vulnerability in Vite allowing access to filesystem paths outside the intended web root.
 
 **Impact**
 
 These vulnerabilities allow attackers to gain access, escalate privileges, or execute actions that were previously unavailable:
 
-- SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
+* SimpleHelp (CVE-2024-57727): An authentication bypass that can let unauthenticated attackers access management interfaces or hijack sessions — enabling lateral movement, credential theft, or privilege escalation within affected environments.
 
-- Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
+* Flowise Cloud (CVE-2025-58434): Information-disclosure flaw that can expose sensitive configuration, tokens, or user data; leaked secrets may be chained into account takeover or privileged access to backend services.
 
-- WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
+* WordPress:Plugin: Ditty (CVE-2025-8085): SSRF that enables server-side requests to internal services or cloud metadata endpoints, potentially allowing attackers to retrieve credentials or reach otherwise inaccessible infrastructure, leading to privilege escalation or cloud resource compromise.
 
-- Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
+* Vite (CVE-2025-30208): Directory-traversal vulnerability that can expose filesystem contents outside the web root (configuration files, keys, source code), which attackers can use to escalate privileges or further compromise systems.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6fe90532af50427484a5275c8c2e30fb" />
-			</td>
-			<td>100717</td>
-			<td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged to 100717 in legacy WAF and{" "}
-				<RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
-			</td>
-			<td>100775</td>
-			<td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
-			</td>
-			<td>100881</td>
-			<td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
-			</td>
-			<td>100887</td>
-			<td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6fe90532af50427484a5275c8c2e30fb" />
+      </td>
+      <td>100717</td>
+      <td>SimpleHelp - Auth Bypass - CVE:CVE-2024-57727</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged to 100717 in legacy WAF and <RuleID id="498fcd81a62a4b5ca943e2de958094d3" /> in new WAF</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="013ef5de3f074fd5a43cdd70d58b886b" />
+      </td>
+      <td>100775</td>
+      <td>Flowise Cloud - Information Disclosure - CVE:CVE-2025-58434</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="68fc5c086ccb4b40a35a63b19bce1ff4" />
+      </td>
+      <td>100881</td>
+      <td>WordPress:Plugin:Ditty - SSRF - CVE:CVE-2025-8085</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9e1a56e6b3bc49b187bf6e35ddc329dd" />
+      </td>
+      <td>100887</td>
+      <td>Vite - Directory Traversal - CVE:CVE-2025-30208</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-03-waf-release.mdx b/src/content/changelog/waf/2025-10-03-waf-release.mdx
index f868e1edd121f98..c01420c6f44b5c8 100644
--- a/src/content/changelog/waf/2025-10-03-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-03-waf-release.mdx
@@ -11,248 +11,248 @@ import { RuleID } from "~/components";
 This update introduces 21 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
-			</td>
-			<td>100902</td>
-			<td>Generic Rules - Command Execution - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c3079865ce9a41368657026b514aeeb8" />
-			</td>
-			<td>100908</td>
-			<td>Generic Rules - Command Execution - 3</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
-			</td>
-			<td>100910</td>
-			<td>Generic Rules - Command Execution - 4</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
-			</td>
-			<td>100915</td>
-			<td>Generic Rules - Command Execution - 5</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
-			</td>
-			<td>100899</td>
-			<td>Generic Rules - Content-Type Abuse</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="233364f656ff42b8acc41dcd7996012f" />
-			</td>
-			<td>100914</td>
-			<td>Generic Rules - Content-Type Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1aa695281c954513be3d003b93209312" />
-			</td>
-			<td>100911</td>
-			<td>Generic Rules - Cookie Header Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
-			</td>
-			<td>100905</td>
-			<td>Generic Rules - NoSQL Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
-			</td>
-			<td>100913</td>
-			<td>Generic Rules - NoSQL Injection - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
-			</td>
-			<td>100907</td>
-			<td>Generic Rules - Parameter Pollution</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
-			</td>
-			<td>100906</td>
-			<td>Generic Rules - PHP Object Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ed5190bfbe1b45a6a645126334c88168" />
-			</td>
-			<td>100904</td>
-			<td>Generic Rules - Prototype Pollution</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
-			</td>
-			<td>100897</td>
-			<td>Generic Rules - Prototype Pollution 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
-			</td>
-			<td>100903</td>
-			<td>Generic Rules - Reverse Shell</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
-			</td>
-			<td>100909</td>
-			<td>Generic Rules - Reverse Shell - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="475d090baead467c88dfabbb565c78b0" />
-			</td>
-			<td>100898</td>
-			<td>Generic Rules - SSJI NoSQL</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f4c7f98934264c9c937eec1212b837a0" />
-			</td>
-			<td>100896</td>
-			<td>Generic Rules - SSRF</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="efd01b814d144e90b36522b311c4fb00" />
-			</td>
-			<td>100895</td>
-			<td>Generic Rules - Template Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="00a9a0d663da4add95b863abd3ed0123" />
-			</td>
-			<td>100895A</td>
-			<td>Generic Rules - Template Injection - 2</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
-			</td>
-			<td>100912</td>
-			<td>Generic Rules - XXE</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
-			</td>
-			<td>100900</td>
-			<td>Relative Paths - Anomaly Headers</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0d02c2fb14eb4cec9c2e2b58d61fac74" />
+      </td>
+      <td>100902</td>
+      <td>Generic Rules - Command Execution - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c3079865ce9a41368657026b514aeeb8" />
+      </td>
+      <td>100908</td>
+      <td>Generic Rules - Command Execution - 3</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="107ae2922b654bb28df7ca978d46a6f4" />
+      </td>
+      <td>100910</td>
+      <td>Generic Rules - Command Execution - 4</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="68bdb75ae6d24e139a83e5731bd0a329" />
+      </td>
+      <td>100915</td>
+      <td>Generic Rules - Command Execution - 5</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ea04bb580f7d400386c7dc1d5e51450a" />
+      </td>
+      <td>100899</td>
+      <td>Generic Rules - Content-Type Abuse</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="233364f656ff42b8acc41dcd7996012f" />
+      </td>
+      <td>100914</td>
+      <td>Generic Rules - Content-Type Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="1aa695281c954513be3d003b93209312" />
+      </td>
+      <td>100911</td>
+      <td>Generic Rules - Cookie Header Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d9f9e4f5bf11489da52dccb40f373b3f" />
+      </td>
+      <td>100905</td>
+      <td>Generic Rules - NoSQL Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5a1897b714e044a887c0f3f078a0ed04" />
+      </td>
+      <td>100913</td>
+      <td>Generic Rules - NoSQL Injection - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4d6fd28df4f1494e95e70d2c5d649624" />
+      </td>
+      <td>100907</td>
+      <td>Generic Rules - Parameter Pollution</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="61181e3af5304f7396c7d01cfd1c674e" />
+      </td>
+      <td>100906</td>
+      <td>Generic Rules - PHP Object Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ed5190bfbe1b45a6a645126334c88168" />
+      </td>
+      <td>100904</td>
+      <td>Generic Rules - Prototype Pollution</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3ec33bc5ac77495a9f55020e3ab43f7e" />
+      </td>
+      <td>100897</td>
+      <td>Generic Rules - Prototype Pollution 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="c6d752c4909e4b7e8eff6c780d94ee22" />
+      </td>
+      <td>100903</td>
+      <td>Generic Rules - Reverse Shell</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="caf37e7800bb4635bcc2eefcd5add8e3" />
+      </td>
+      <td>100909</td>
+      <td>Generic Rules - Reverse Shell - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="475d090baead467c88dfabbb565c78b0" />
+      </td>
+      <td>100898</td>
+      <td>Generic Rules - SSJI NoSQL</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="f4c7f98934264c9c937eec1212b837a0" />
+      </td>
+      <td>100896</td>
+      <td>Generic Rules - SSRF</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="efd01b814d144e90b36522b311c4fb00" />
+      </td>
+      <td>100895</td>
+      <td>Generic Rules - Template Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="00a9a0d663da4add95b863abd3ed0123" />
+      </td>
+      <td>100895A</td>
+      <td>Generic Rules - Template Injection - 2</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="e58c0fffee4f4374bd37f2577501a1d9" />
+      </td>
+      <td>100912</td>
+      <td>Generic Rules - XXE</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab09ba8d00eb4cdbb7a6a65ddc55cdb6" />
+      </td>
+      <td>100900</td>
+      <td>Relative Paths - Anomaly Headers</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-06-waf-release.mdx b/src/content/changelog/waf/2025-10-06-waf-release.mdx
index 89c8ea1bc8db134..d4f1efa95c7512e 100644
--- a/src/content/changelog/waf/2025-10-06-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-06-waf-release.mdx
@@ -10,124 +10,122 @@ This week’s highlights prioritise an emergency Oracle E-Business Suite RCE rul
 
 **Key Findings**
 
-- New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
+* New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.
 
-- Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
+* Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (`cleanTcs`, `killProcesses`, `cleanIptables`) are vulnerable to OS command injection.
 
-- Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
+* Form-Data (CVE-2025-7783): Attackers who can observe `Math.random()` outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.
 
-- Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
+* Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.
 
 **Impact**
 
-- CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced.
+* CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced. 
 
-- CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
+* CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).
 
-- CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
+* CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
-			</td>
-			<td>100882</td>
-			<td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
-			</td>
-			<td>100883</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a2591ba5befa4815a6861aefef859a04" />
-			</td>
-			<td>100884</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
-			</td>
-			<td>100886</td>
-			<td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="90514c7810694b188f56979826a4074c" />
-			</td>
-			<td>100888</td>
-			<td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
-			</td>
-			<td>100916</td>
-			<td>
-				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="badc687a3ba3420a844220b129aa43c3" />
-			</td>
-			<td>100917</td>
-			<td>Generic Rules - SQLi - Inline Comment Injection</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="28fa27511f29428899ceb5a273c10b6f" />
-			</td>
-			<td>100918</td>
-			<td>Generic Rules - SQLi - Information Disclosure</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
-</table>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0c9bf31ab6fa41fc8f12daaf8650f52f" />
+      </td>
+      <td>100882</td>
+      <td>Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5d459ed434ed446c9580c73c2b8c3680" />
+      </td>
+      <td>100883</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59359</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a2591ba5befa4815a6861aefef859a04" />
+      </td>
+      <td>100884</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59361</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="05eea4fabf6f4cf3aac1094b961f26a7" />
+      </td>
+      <td>100886</td>
+      <td>Form-Data - Parameter Pollution - CVE:CVE-2025-7783</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="90514c7810694b188f56979826a4074c" />
+      </td>
+      <td>100888</td>
+      <td>Chaos Mesh - Command Injection - CVE:CVE-2025-59360</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="42fbc8c09ec84578b9633ffc31101b2f" />
+      </td>
+      <td>100916</td>
+      <td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="badc687a3ba3420a844220b129aa43c3" />
+      </td>
+      <td>100917</td>
+      <td>Generic Rules - SQLi - Inline Comment Injection</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="28fa27511f29428899ceb5a273c10b6f" />
+      </td>
+      <td>100918</td>
+      <td>Generic Rules - SQLi - Information Disclosure</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a New Detection</td>
+    </tr>                    
+  </tbody>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
index 724fe2ad9d9bcae..fa9d65c7613c3e3 100644
--- a/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-07-emergency-waf-release.mdx
@@ -7,9 +7,9 @@ date: 2025-10-07
 import { RuleID } from "~/components";
 
 This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CVE-2025-20333, CVE-2025-20362). This flaw stems from improper input validation in HTTP(S) requests. An authenticated VPN user could send crafted requests to execute code as root, potentially compromising the device.
-The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection.
+The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection. 
 
-- Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
+* Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.
 
 **Impact**
 
@@ -17,31 +17,28 @@ Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables att
 Administrators are strongly advised to apply vendor updates immediately.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
-			</td>
-			<td>100788B</td>
-			<td>
-				Cisco Secure Firewall Adaptive Security Appliance - Remote Code
-				Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363
-			</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="12f808a5315441688f3b7c8a3a4d1bd6" />
+      </td>
+      <td>100788B</td>
+      <td>Cisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
index fc5674015901639..3001df61385c0d0 100644
--- a/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-17-emergency-waf-release.mdx
@@ -47,9 +47,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="72f0ff933fb0492eb71cda50589f2a1d" />
-			</td>
+			<td><RuleID id="72f0ff933fb0492eb71cda50589f2a1d" /></td>
 			<td>N/A</td>
 			<td>Anomaly:Header - name - CR, LF</td>
 			<td>N/A</td>
@@ -58,9 +56,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5d0377e4435f467488614170132fab7e" />
-			</td>
+			<td><RuleID id="5d0377e4435f467488614170132fab7e" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Body</td>
 			<td>N/A</td>
@@ -69,9 +65,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54e32f7f802c4a699182e8921a027008" />
-			</td>
+			<td><RuleID id="54e32f7f802c4a699182e8921a027008" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - Header</td>
 			<td>N/A</td>
@@ -80,9 +74,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" />
-			</td>
+			<td><RuleID id="7cbda8dbafbc465d9b64a8f2958d0486" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - Reverse Shell - URI</td>
 			<td>N/A</td>
@@ -91,9 +83,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b9f3420674cf481da32333dc8e0cf7ad" />
-			</td>
+			<td><RuleID id="b9f3420674cf481da32333dc8e0cf7ad" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - XXE - Body</td>
 			<td>N/A</td>
@@ -102,9 +92,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ad55483512f0440b81426acdbf8aab5e" />
-			</td>
+			<td><RuleID id="ad55483512f0440b81426acdbf8aab5e" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Common Patterns - Header URI</td>
 			<td>N/A</td>
@@ -113,9 +101,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="849c0618d1674f1c92ba6f9b2e466337" />
-			</td>
+			<td><RuleID id="849c0618d1674f1c92ba6f9b2e466337" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - Sleep Function - Header URI</td>
 			<td>N/A</td>
@@ -124,9 +110,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" />
-			</td>
+			<td><RuleID id="1b4db4c4bd0649c095c27c6cb686ab47" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - String Function - Header URI</td>
 			<td>N/A</td>
@@ -135,9 +119,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fa2055b84af94ba4b925f834b0633709" />
-			</td>
+			<td><RuleID id="fa2055b84af94ba4b925f834b0633709" /></td>
 			<td>N/A</td>
 			<td>Generic Rules - SQLi - WaitFor Function - Header URI</td>
 			<td>N/A</td>
@@ -146,9 +128,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="158177dec2504acdba1f2da201a076eb" />
-			</td>
+			<td><RuleID id="158177dec2504acdba1f2da201a076eb" /></td>
 			<td>N/A</td>
 			<td>SSRF - Local - Beta</td>
 			<td>N/A</td>
@@ -157,9 +137,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" />
-			</td>
+			<td><RuleID id="98bfd6bb46074d5b8d1c4b39743a63ec" /></td>
 			<td>N/A</td>
 			<td>SSRF - Local - 2 - Beta</td>
 			<td>N/A</td>
@@ -168,9 +146,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" />
-			</td>
+			<td><RuleID id="54e1733b10da4a599e06c6fbc2e84e2d" /></td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - Beta</td>
 			<td>N/A</td>
@@ -179,9 +155,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" />
-			</td>
+			<td><RuleID id="ecd26d61a75e46f6a4449a06ab8af26f" /></td>
 			<td>N/A</td>
 			<td>SSRF - Cloud - 2 - Beta</td>
 			<td>N/A</td>
@@ -190,9 +164,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c16f4e133c4541f293142d02e6e8dc5b" />
-			</td>
+			<td><RuleID id="c16f4e133c4541f293142d02e6e8dc5b" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - URI</td>
 			<td>N/A</td>
@@ -201,9 +173,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f4fd9904e7624666b8c49cd62550d794" />
-			</td>
+			<td><RuleID id="f4fd9904e7624666b8c49cd62550d794" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Header</td>
 			<td>N/A</td>
@@ -212,9 +182,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5c0875604f774c36a4f9b69c659d12a6" />
-			</td>
+			<td><RuleID id="5c0875604f774c36a4f9b69c659d12a6" /></td>
 			<td>N/A</td>
 			<td>SSTI - Arithmetic Probe - Body</td>
 			<td>N/A</td>
@@ -223,9 +191,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />
-			</td>
+			<td><RuleID id="fae6fa37ae9249d58628e54b1a3e521e" /></td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -234,9 +200,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9c02e585db34440da620eb668f76bd74" />
-			</td>
+			<td><RuleID id="9c02e585db34440da620eb668f76bd74" /></td>
 			<td>N/A</td>
 			<td>PHP Wrapper Injection</td>
 			<td>N/A</td>
@@ -245,9 +209,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb67fe56a84747b8b64277dc091e296d" />
-			</td>
+			<td><RuleID id="cb67fe56a84747b8b64277dc091e296d" /></td>
 			<td>N/A</td>
 			<td>HTTP parameter pollution</td>
 			<td>N/A</td>
@@ -256,9 +218,7 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="443b54d984944cd69043805ee34214ef" />
-			</td>
+			<td><RuleID id="443b54d984944cd69043805ee34214ef" /></td>
 			<td>N/A</td>
 			<td>Prototype Pollution - Common Payloads - Beta</td>
 			<td>N/A</td>
@@ -266,4 +226,4 @@ Prototype Pollution and HTTP parameter pollution rules address emerging JavaScri
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-20-waf-release.mdx b/src/content/changelog/waf/2025-10-20-waf-release.mdx
index 3768829710eb921..b566732da2e8dad 100644
--- a/src/content/changelog/waf/2025-10-20-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-20-waf-release.mdx
@@ -10,7 +10,7 @@ This week’s update introduces an enhanced rule that expands detection coverage
 
 **Key Findings**
 
-New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
+New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block  unauthenticated attacker's network access via HTTP to compromise Oracle Concurrent Processing. If successfully exploited, this vulnerability may result in remote code execution.
 
 **Impact**
 
@@ -38,21 +38,15 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unau
 			<td>Remote Code Execution - Common Bash Bypass - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Remote Code Execution -
-				Common Bash Bypass" (ID:{" "}
-				<RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)
-			</td>
-		</tr>
+			<td>This rule is merged into the original rule "Remote Code Execution - Common Bash Bypass" (ID: <RuleID id="f8238867ed3e4d3a9a7b731a50cec478" />)</td>
+		</tr>         
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="185b5df42d1e44e0aeb8f8b8a1118614" />
 			</td>
 			<td>100916A</td>
-			<td>
-				Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2
-			</td>
+			<td>Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882 - 2</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a New Detection</td>
@@ -69,4 +63,4 @@ New WAF rule deployed for Oracle E-Business Suite (CVE-2025-61882) to block unau
 			<td>This is a New Detection</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
index eff22509bb0f005..968037a9f6bf67c 100644
--- a/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-23-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ This vulnerability allows unauthenticated attackers to take over customer accoun
 Adobe Commerce (CVE-2025-54236): Exploitation may allow attackers to hijack sessions, execute arbitrary commands, steal data, and disrupt storefronts, resulting in confidentiality and integrity risks for merchants. Administrators are strongly encouraged to apply vendor patches without delay.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
-			</td>
-			<td>N/A</td>
-			<td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6e04fa2b9eb34fb088034d3fc6ef59a1" />
+      </td>
+      <td>N/A</td>
+      <td>Adobe Commerce - Remote Code Execution - CVE:CVE-2025-54236</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
index ffa6cd0f4a1e7e6..4deb26e943c3254 100644
--- a/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-24-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The vulnerability allows unauthenticated attackers to potentially achieve remote
 Successful exploitation of CVE-2025-59287 could enable attackers to hijack sessions, execute arbitrary commands, exfiltrate sensitive data, and disrupt storefront operations. These actions pose significant confidentiality and integrity risks to affected environments. Administrators should apply vendor patches immediately to mitigate exposure.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
-			</td>
-			<td>N/A</td>
-			<td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5eaeb5ea6e5a4bce867eb3ffbd72ba08" />
+      </td>
+      <td>N/A</td>
+      <td>Windows Server - Deserialization - CVE:CVE-2025-59287</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
index a3359450691e99c..48b39ac6c7cfe22 100644
--- a/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-10-30-emergency-waf-release.mdx
@@ -17,28 +17,28 @@ The flaw is easily exploitable and allows an unauthenticated attacker with netwo
 Successful exploitation of CVE-2025-61884 may result in unauthorized access to critical business data or full exposure of information accessible through Oracle Configurator. Administrators are strongly advised to apply vendor's patches and recommended mitigations to reduce this exposure.
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
-			</td>
-			<td>N/A</td>
-			<td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2749f13f8cb34a3dbd49c8c48827402f" />
+      </td>
+      <td>N/A</td>
+      <td>Oracle E-Business Suite - SSRF - CVE:CVE-2025-61884</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
index 65a2c278f87407e..c9584fd1902891f 100644
--- a/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-05-emergency-waf-release.mdx
@@ -14,31 +14,31 @@ The Metro Development Server exposes an HTTP endpoint that is vulnerable to OS c
 
 **Impact**
 
-Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk.
+Successful exploitation of CVE-2025-11953 may result in remote command execution on developer workstations or CI/build agents, leading to credential and secret exposure, source tampering, and potential lateral movement into internal networks. Administrators and developers are strongly advised to apply the vendor's patches and restrict Metro’s network exposure to reduce this risk. 
 
 <table style="width: 100%">
-	<thead>
-		<tr>
-			<th>Ruleset</th>
-			<th>Rule ID</th>
-			<th>Legacy Rule ID</th>
-			<th>Description</th>
-			<th>Previous Action</th>
-			<th>New Action</th>
-			<th>Comments</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
-			</td>
-			<td>N/A</td>
-			<td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a New Detection</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Ruleset</th>
+      <th>Rule ID</th>
+      <th>Legacy Rule ID</th>
+      <th>Description</th>
+      <th>Previous Action</th>
+      <th>New Action</th>
+      <th>Comments</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="db6b9e1ac1494971ae8c70aac8e30c5b" />
+      </td>
+      <td>N/A</td>
+      <td>React Native Metro - Command Injection - CVE:CVE-2025-11953</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a New Detection</td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-10-waf-release.mdx b/src/content/changelog/waf/2025-11-10-waf-release.mdx
index 6f0e60f36daadeb..c442f86894866c0 100644
--- a/src/content/changelog/waf/2025-11-10-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-10-waf-release.mdx
@@ -39,7 +39,7 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>    
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -61,6 +61,6 @@ Exploitation may allow attackers to change internal logic or cause unexpected be
 			<td>Log</td>
 			<td>Disabled</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>        
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-11-17-waf-release.mdx b/src/content/changelog/waf/2025-11-17-waf-release.mdx
index f34a07d31022e1b..38a33ac01a0985b 100644
--- a/src/content/changelog/waf/2025-11-17-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-17-waf-release.mdx
@@ -63,4 +63,4 @@ This vulnerability allows unauthenticated attackers to gain privileged access to
 			<td>Rule metadata description refined. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
index 92ca15cf695904c..668d5120066318a 100644
--- a/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-21-emergency-waf-release.mdx
@@ -41,4 +41,4 @@ Oracle Identity Manager (CVE-2025-61757): Exploitation could allow an unauthenti
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-11-24-waf-release.mdx b/src/content/changelog/waf/2025-11-24-waf-release.mdx
index b7949e4310a105d..40fe7147867f34d 100644
--- a/src/content/changelog/waf/2025-11-24-waf-release.mdx
+++ b/src/content/changelog/waf/2025-11-24-waf-release.mdx
@@ -35,9 +35,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 				<RuleID id="b957ace6e9844bf29244401c4e2e1a2e" />
 			</td>
 			<td>N/A</td>
-			<td>
-				FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446
-			</td>
+			<td>FortiWeb - Authentication Bypass via CGIINFO Header - CVE:CVE-2025-64446</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
@@ -51,11 +49,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - Body - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>
-				This rule has been merged into the original rule "PHP Wrapper Injection
-				- Body" (ID:
-				<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)
-			</td>
+			<td>This rule has been merged into the original rule "PHP Wrapper Injection - Body" (ID:<RuleID id="fae6fa37ae9249d58628e54b1a3e521e" />)</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -66,11 +60,7 @@ This vulnerability enables an unauthenticated attacker to bypass access controls
 			<td>PHP Wrapper Injection - URI - Beta</td>
 			<td>Log</td>
 			<td>Disabled</td>
-			<td>
-				This rule has been merged into the original rule "PHP Wrapper Injection
-				- URI" (ID:
-				<RuleID id="9c02e585db34440da620eb668f76bd74" />)
-			</td>
+			<td>This rule has been merged into the original rule "PHP Wrapper Injection - URI" (ID:<RuleID id="9c02e585db34440da620eb668f76bd74" />)</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-01-waf-release.mdx b/src/content/changelog/waf/2025-12-01-waf-release.mdx
index bb91b0b857039b3..5c9725909eb48b5 100644
--- a/src/content/changelog/waf/2025-12-01-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-01-waf-release.mdx
@@ -39,7 +39,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection</td>
-		</tr>
+		</tr>    
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
@@ -49,10 +49,7 @@ If exploited, the vulnerability enables full remote command execution on the und
 			<td>XSS - JS Context Escape - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "XSS - JS Context Escape"
-				(ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)
-			</td>
-		</tr>
+			<td>This rule is merged into the original rule "XSS - JS Context Escape" (ID: <RuleID id="c1ad1bc37caa4cbeb104f44f7a3769d3" />)</td>
+		</tr>  
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
index ff06da00aab5c68..1cdc563f6d10a45 100644
--- a/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-02-emergency-waf-release.mdx
@@ -52,4 +52,4 @@ New WAF rule deployed for RCE Generic Framework to block malicious POST requests
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
index e22e9674a2f7a29..317f93bc2050154 100644
--- a/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-03-emergency-waf-release.mdx
@@ -15,7 +15,6 @@ Rule description updated to reference React – RCE – CVE-2025-55182 while ret
 **Impact**
 
 Improved classification and traceability with no change to coverage against remote code execution attempts.
-
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -52,4 +51,4 @@ Improved classification and traceability with no change to coverage against remo
 			<td>Rule metadata description changed. Detection unchanged.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
index 25b82374c113154..3c6833f7416480d 100644
--- a/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-10-emergency-waf-release.mdx
@@ -85,4 +85,4 @@ These updates strengthen protection against React RCE exploitation attempts and
 			<td>This is a new detection.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
index 35ce57a85250982..18c75f46429d216 100644
--- a/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-11-emergency-waf-release.mdx
@@ -38,9 +38,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This was labeled as Generic - Server Function Source Code Exposure.
-			</td>
+			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Free Ruleset</td>
@@ -51,9 +49,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - Leaking Server Functions - CVE:CVE-2025-55183</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>
-				This was labeled as Generic - Server Function Source Code Exposure.
-			</td>
+			<td>This was labeled as Generic - Server Function Source Code Exposure.</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -64,9 +60,7 @@ These updates strengthen protection for server-function abuse techniques (CVE-20
 			<td>React - DoS - CVE:CVE-2025-55184</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>
-				This was labeled as Generic – Server Function Resource Exhaustion.
-			</td>
+			<td>This was labeled as Generic – Server Function Resource Exhaustion.</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2025-12-18-waf-release.mdx b/src/content/changelog/waf/2025-12-18-waf-release.mdx
index 1e89c7251d32210..161f57af1c49b1b 100644
--- a/src/content/changelog/waf/2025-12-18-waf-release.mdx
+++ b/src/content/changelog/waf/2025-12-18-waf-release.mdx
@@ -12,6 +12,10 @@ This week's release focuses on improvements to existing detections to enhance co
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
+
+
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,124 +28,105 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
-			</td>
-			<td>N/A</td>
-			<td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Atlassian Confluence - Code
-				Injection - CVE:CVE-2021-26084" (ID:{" "}
-				<RuleID id="e8c550810618437c953cf3a969e0b97a" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="9108ddb347b3497e9f9351640d9206e3" />
-			</td>
-			<td>N/A</td>
-			<td>PostgreSQL - SQLi - Copy - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "PostgreSQL - SQLi - COPY"
-				(ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - Body</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - Header</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6df040f716194070a242967cfd181fb3" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Command Execution - URI</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Tautology - URI - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Tautology - URI" (ID:{" "}
-				<RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - WaitFor Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - WaitFor Function"
-				(ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="80690005fef342e0ad6bc9af596c741e" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - AND/OR Digit Operator
-				Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Equation 2 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Equation" (ID:{" "}
-				<RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6429f7386b1546cf9dfce631be5ec20c" />
+      </td>
+      <td>N/A</td>
+      <td>Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "Atlassian Confluence - Code Injection - CVE:CVE-2021-26084" (ID: <RuleID id="e8c550810618437c953cf3a969e0b97a" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="9108ddb347b3497e9f9351640d9206e3" />
+      </td>
+      <td>N/A</td>
+      <td>PostgreSQL - SQLi - Copy - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "PostgreSQL - SQLi - COPY" (ID: <RuleID id="705a6b5569d5472596910e3ce7265a4e" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="cb687d73cc954092b58b90b00cd00ba7" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - Body</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="bf30657ffa2a424cbf6570dbcd679ad4" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - Header</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="6df040f716194070a242967cfd181fb3" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Command Execution - URI</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="39a4fdc37be948709fa7492e7a95bc3a" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Tautology - URI - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Tautology - URI" (ID: <RuleID id="4c580ea1b5174183b7f5e940b3de2e0a" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="810e0ffe1dd84e67b159129b432ac90d" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - WaitFor Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - WaitFor Function" (ID: <RuleID id="b16fe708799441dea3049a99d5faba59" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="80690005fef342e0ad6bc9af596c741e" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - AND/OR Digit Operator Digit 2 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit" (ID: <RuleID id="98e7e08ae64247e2801ca4b388d80772" />)</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="eaf11ab80b0d491cbb7186f303b2f3fe" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Equation 2 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Equation" (ID: <RuleID id="133c6f83cdf14509a4ca6b82a72a6b3a" />)</td>
+    </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-12-waf-release.mdx b/src/content/changelog/waf/2026-01-12-waf-release.mdx
index 4c5e3ce6f9668d0..f98c0a337960ed6 100644
--- a/src/content/changelog/waf/2026-01-12-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-12-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-12
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="72963b917ef74697b5bde02f48a1841a" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT"
-				(ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Benchmark Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Benchmark Function"
-				(ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="72963b917ef74697b5bde02f48a1841a" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT" (ID: <RuleID id="0f41a593c8fe42c38a26f709252d3934" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Benchmark Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Benchmark Function" (ID: <RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-15-waf-release.mdx b/src/content/changelog/waf/2026-01-15-waf-release.mdx
index 884dea72d886e11..63c93358717c0b5 100644
--- a/src/content/changelog/waf/2026-01-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-15-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-15
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - String Function" (ID:{" "}
-				<RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Sub Query - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Sub Query" (ID:{" "}
-				<RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="eb3f44c07266448b9fa54ee7ad7dad3e" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - String Function - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - String Function" (ID: <RuleID id="63e03eecddfc4b3fb0cad587d32b798c" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="adf076af09b2484ca9e7881f9e553ad3" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Sub Query - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Sub Query" (ID: <RuleID id="6ec5ecf52c094330aff99a38743e66b1" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-20-waf-release.mdx b/src/content/changelog/waf/2026-01-20-waf-release.mdx
index 1b7ca4114286eb1..0da1e57c513f3ef 100644
--- a/src/content/changelog/waf/2026-01-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-20-waf-release.mdx
@@ -6,12 +6,13 @@ date: 2026-01-20
 
 import { RuleID } from "~/components";
 
-This week's release focuses on improvements to existing detections to enhance coverage.
+This week's release focuses on improvements to existing detections to enhance coverage. 
 
 **Key Findings**
 
 - Existing rule enhancements have been deployed to improve detection resilience against SQL injection.
 
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,34 +25,28 @@ This week's release focuses on improvements to existing detections to enhance co
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comment - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Comment" (ID:{" "}
-				<RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "SQLi - Comparison" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="a291bd530fa346d18cc1ce5a68d90c8f" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Comment - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule is merged into the original rule "SQLi - Comment" (ID: <RuleID id="42c424998d2a42c9808ab49c6d8d8fe4" />)</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="da289f9e692e4f5397d915fbfaa045cf" />
+      </td>
+      <td>N/A</td>
+      <td>SQLi - Comparison - Beta</td>
+      <td>Log</td>
+      <td>Block</td>      
+      <td>This rule is merged into the original rule "SQLi - Comparison" (ID: <RuleID id="8166da327a614849bfa29317e7907480" />)</td>
+   </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-01-26-waf-release.mdx b/src/content/changelog/waf/2026-01-26-waf-release.mdx
index 030699a9d584923..cfb420d9e2809ad 100644
--- a/src/content/changelog/waf/2026-01-26-waf-release.mdx
+++ b/src/content/changelog/waf/2026-01-26-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for denial-of-service attempts t
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="aaede80b4d414dc89c443cea61680354" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="930020d567684f19b05fb35b349edbc6" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
-			<td>N/A</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="aaede80b4d414dc89c443cea61680354" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 1</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3e93c9faaafa447c83a525f2dcdffcf8" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 2</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="930020d567684f19b05fb35b349edbc6" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 3</td>
+      <td>N/A</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-02-02-waf-release.mdx b/src/content/changelog/waf/2026-02-02-waf-release.mdx
index cb989e8324478d9..00ed3826f072eeb 100644
--- a/src/content/changelog/waf/2026-02-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-02-02-waf-release.mdx
@@ -25,39 +25,39 @@ This week’s release introduces new detections for CVE-2025-64459 and CVE-2025-
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7a47683eacce4abd870ab2c630698ff3" />
-			</td>
-			<td>N/A</td>
-			<td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
-			</td>
-			<td>N/A</td>
-			<td>Django SQLI - CVE:CVE-2025-64459</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8f0d5c98bd24460a9305a1558d667511" />
-			</td>
-			<td>N/A</td>
-			<td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
-			<td>Block</td>
-			<td>Block</td>
-			<td>Rule metadata description refined. Detection unchanged.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7a47683eacce4abd870ab2c630698ff3" />
+      </td>
+      <td>N/A</td>
+      <td>XWiki - Remote Code Execution - CVE:CVE-2025-24893 2</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ad5c52f6ca334ef4a844e5e5da8ba7e6" />
+      </td>
+      <td>N/A</td>
+      <td>Django SQLI - CVE:CVE-2025-64459</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+  </tr>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="8f0d5c98bd24460a9305a1558d667511" />
+      </td>
+      <td>N/A</td>
+      <td>NoSQL, MongoDB - SQLi - Comparison - 2</td>
+      <td>Block</td>
+      <td>Block</td>
+      <td>Rule metadata description refined. Detection unchanged.</td>
+  </tr>
+  </tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-02-waf-release.mdx b/src/content/changelog/waf/2026-03-02-waf-release.mdx
index 34e9cc77d392db9..5e417a5421f9c40 100644
--- a/src/content/changelog/waf/2026-03-02-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-02-waf-release.mdx
@@ -8,6 +8,7 @@ import { RuleID } from "~/components";
 
 This week's release introduces new detections for vulnerabilities in SmarterTools SmarterMail (CVE-2025-52691 and CVE-2026-23760), alongside improvements to an existing Command Injection (nslookup) detection to enhance coverage.
 
+
 **Key Findings**
 
 - CVE-2025-52691: SmarterTools SmarterMail mail server is vulnerable to Arbitrary File Upload, allowing an unauthenticated attacker to upload files to any location on the mail server, potentially enabling remote code execution.
@@ -61,10 +62,8 @@ Successful exploitation of these SmarterMail vulnerabilities could lead to full
 			<td>Command Injection - Nslookup - Beta</td>
 			<td>Log</td>
 			<td>Block</td>
-			<td>
-				This rule is merged into the original rule "Command Injection -
-				Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)
-			</td>
+			<td>This rule is merged into the original rule "Command Injection - Nslookup" (ID: <RuleID id="f4a310393c564d50bd585601b090ba9a" />)</td>
 		</tr>
+          
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
index 82b11cdd62ca859..37ee704eb668c95 100644
--- a/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-12-emergency-waf-release.mdx
@@ -36,13 +36,11 @@ Successful exploitation of Ivanti EPMM vulnerability allows unauthenticated remo
 				<RuleID id="5ae86a9bda0c41dbb905132f796ea2f6" />
 			</td>
 			<td>N/A</td>
-			<td>
-				Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340
-			</td>
+			<td>Ivanti EPMM - Code Injection - CVE:CVE-2026-1281 CVE:CVE-2026-1340</td>
 			<td>Log</td>
 			<td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr> 
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
 			<td>
diff --git a/src/content/changelog/waf/2026-03-23-waf-release.mdx b/src/content/changelog/waf/2026-03-23-waf-release.mdx
index ca8664ddf6e1b0f..4b55ee8e500a59b 100644
--- a/src/content/changelog/waf/2026-03-23-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-23-waf-release.mdx
@@ -12,6 +12,10 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
+
+
+
 <table style="width: 100%">
 	<thead>
 		<tr>
@@ -24,58 +28,50 @@ This week's release focuses on new improvements to enhance coverage.
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - URI Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - Header Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="155bb67d1061479e995a38510677175f" />
-			</td>
-			<td>N/A</td>
-			<td>Command Injection - Generic 9 - Body Vector</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
-			</td>
-			<td>N/A</td>
-			<td>
-				PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File
-				Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "PHP, vBulletin, jQuery
-				File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206,
-				CVE:CVE-2019-17132" (ID:{" "}
-				<RuleID id="0f2da91cec674eb58006929e824b817c" />)
-			</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="54ad0465c30d4cd2ac7a707197321c6c" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - URI Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="b31c34a7b29b4aaf9be6883d1eb7a999" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - Header Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="155bb67d1061479e995a38510677175f" />
+      </td>
+      <td>N/A</td>
+      <td>Command Injection - Generic 9 - Body Vector</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="55fb1c76f0304f6a9d935d03479da68f" />
+      </td>
+      <td>N/A</td>
+      <td>PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta)</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132" (ID: <RuleID id="0f2da91cec674eb58006929e824b817c" />)</td>
+    </tr>
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-03-30-waf-release.mdx b/src/content/changelog/waf/2026-03-30-waf-release.mdx
index 7bb86d5b78461dc..1bf0c23738bd886 100644
--- a/src/content/changelog/waf/2026-03-30-waf-release.mdx
+++ b/src/content/changelog/waf/2026-03-30-waf-release.mdx
@@ -30,63 +30,61 @@ Successful exploitation of the Fortinet and Magento vulnerabilities could allow
 			<th>Comments</th>
 		</tr>
 	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4f7d513cea424c2a853881982f7f95e9" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - Body</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="60d023f3be414d379428add3319731a4" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - Header - Form</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
-			</td>
-			<td>N/A</td>
-			<td>Generic Rules - Parameter Pollution - URI</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="ab8a96ed13034d56a81a79e570a36147" />
-			</td>
-			<td>N/A</td>
-			<td>Magento 2 - Unrestricted file upload</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+    <tbody>
+	<tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="4f7d513cea424c2a853881982f7f95e9" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - Body</td>
+      <td>Log</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+   </tr>
+   <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="60d023f3be414d379428add3319731a4" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - Header - Form</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+   </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="2dde02d792ad41ec8fd65c2bdef262dd" />
+      </td>
+      <td>N/A</td>
+      <td>Generic Rules - Parameter Pollution - URI</td>
+      <td>Log</td>
+      <td>Disabled</td>      
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="ab8a96ed13034d56a81a79e570a36147" />
+      </td>
+      <td>N/A</td>
+      <td>Magento 2 - Unrestricted file upload</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0a13a38dd81c44688950444e2ffcca9f" />
+      </td>
+      <td>N/A</td>
+      <td>Fortinet FortiCloud SSO - Authentication Bypass - CVE:CVE-2025-59718</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>    
+  </tbody>    
 </table>
diff --git a/src/content/changelog/waf/2026-04-15-waf-release.mdx b/src/content/changelog/waf/2026-04-15-waf-release.mdx
index 8027bd3284ff60d..48b63b279a71a7e 100644
--- a/src/content/changelog/waf/2026-04-15-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-15-waf-release.mdx
@@ -21,7 +21,7 @@ This week's release introduces a new detection for a critical Remote Code Execut
 Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code, gain administrative control over network management infrastructure, or trigger server-side resource exhaustion. Administrators are strongly encouraged to apply official vendor updates.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -31,81 +31,73 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
-			</td>
-			<td>N/A</td>
-			<td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
-			</td>
-			<td>N/A</td>
-			<td>
-				Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057
-			</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
-			</td>
-			<td>N/A</td>
-			<td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This rule has been merged into the original rule "React Server - DOS -
-				CVE:CVE-2026-23864 - 1" (ID:{" "}
-				<RuleID id="aaede80b4d414dc89c443cea61680354" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
-			</td>
-			<td>N/A</td>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7767165cda1841b8b6e5abb7aef9415b" />
+      </td>
+      <td>N/A</td>
+      <td>Cisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="3dd0b2b6f45c4bc08e49bf27ee7be621" />
+      </td>
+      <td>N/A</td>
+      <td>FortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>   
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="0e3a6828906c4b24bad318a9c953a72b" />
+      </td>
+      <td>N/A</td>
+      <td>Mesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection.</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="d95aa5410d1b4e98bf7a59d150c08f6f" />
+      </td>
+      <td>N/A</td>
+      <td>React Server - DOS - CVE:CVE-2026-23864 - 1 - Beta</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This rule has been merged into the original rule "React Server - DOS - CVE:CVE-2026-23864 - 1" (ID: <RuleID id="aaede80b4d414dc89c443cea61680354" />)</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
+      </td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI (beta)</td>
+      <td>N/A</td>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
+      <td>
+        <RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
+      </td>
+      <td>N/A</td>
+      <td>XSS, HTML Injection - Embed Tag  - URI (beta)</td>
 			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
-			</td>
-			<td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag - URI (beta)</td>
-			<td>N/A</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+      <td>Disabled</td>
+      <td>This is a new detection.</td>
+    </tr>
+</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-21-waf-release.mdx b/src/content/changelog/waf/2026-04-21-waf-release.mdx
index 5a538a69976bfd7..d31b75ad221a27b 100644
--- a/src/content/changelog/waf/2026-04-21-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-21-waf-release.mdx
@@ -23,7 +23,7 @@ Successful exploitation of these vulnerabilities could allow unauthenticated att
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -33,266 +33,285 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="ff8df24181aa4573a81be531ee159e2e" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Command Injection - Generic 8 - uri</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. Previous description was "Command Injection -
-				Generic 8 - uri - Beta"
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+      <td>This is a new detection. Previous description was "Command Injection - Generic 8 - uri - Beta"</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9429b63c137247faadeb8a29a15308cf" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Command Injection - Generic 8 - body - Beta</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Command Injection - Generic 8 - body" (ID:{" "}
-				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />
-				). The rule previously known as "Command Injection - Generic 8" is now
-				renamed to "Command Injection - Generic 8 - body".
+				<RuleID id="5b3ce84c099040c6a25cee2d413592e2" />). The rule previously known as "Command Injection - Generic 8" is now renamed to "Command Injection - Generic 8 - body".
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>		
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="85aaf5db9e0c4237b87e837e958047ed" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
+      <td>Log</td>
+      <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"MySQL - SQLi - Executable Comment - Body" (ID:{" "}
-				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously
-				known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL -
-				SQLi - Executable Comment - Body".
+				<RuleID id="8629bb58defe4193ab4d493c7bd2d8fa" />) The rule previously known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL - SQLi - Executable Comment - Body".
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d19cd574c4644952881a6f3a582cc559" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="407f9ec8a17348dfba3b9450a16639d3" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>MySQL - SQLi - Executable Comment - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d07e6dbf15664b99b37b0d2544f24211" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Magento 2 - Unrestricted file upload - 2</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>     
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="26ef21cb197b44fc8a98b7cebf170a17" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>Apache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr> 
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7f7bc3d28a8e43bf97bd15d68c2ac1a7" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
+      <td>Log</td>
+      <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Sleep Function" (ID:{" "}
 				<RuleID id="2c333735f7b24566b17cb64ef77e8d54" />)
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3872e5638bdf4bf0943a80394dacaeb8" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>   
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="bebce8fadfa94ccab09eb74fed4c9ece" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Sleep Function - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7a40eed5a8654a50a2598a821dfa64df" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - uri</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="15c6b2ce033949b2a1a9f9454c62e2e7" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - header</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="fc9d800b7a724181af8d5650aab28ea1" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing - body</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Probing" (ID: <RuleID id="2c20b5e8684043f48620ff77b4026c88" />)
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+    <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="945c5aa9f45141dd872d7ec920999be0" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - Probing 2 </td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This rule had duplicate detection logic and has been deprecated.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This rule had duplicate detection logic and has been deprecated.
+			</td>
+    </tr> 
+    <tr>
+	      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="f1771273700342758e73cf16d7aa0008" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - UNION in MSSQL - Body</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
 			<td>
-				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL"
-				(ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains
-				updated rule logic.
+				This rule has been renamed to differentiate from "SQLi - UNION in MSSQL" (ID: <RuleID id="ef7db598c7654c729d9db56fee5e35fd" />) and contains updated rule logic.
 			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr> 
+    <tr> 
+	      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="3ffd242b4ba242ca965022d3a67d8561" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>SQLi - UNION - 3</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This rule had duplicate detection logic and has been deprecated.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This rule had duplicate detection logic and has been deprecated.
+			</td>
+    </tr> 
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="5e69d599ad634c81abe36a5f0af34bba" />
 			</td>
-			<td>N/A</td>
-			<td>XSS, HTML Injection - Embed Tag - URI</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>N/A</td>
+			<td>XSS, HTML Injection - Embed Tag  - URI</td>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2635275641bf44d4bad6a2e170282f38" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Embed Tag - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Block</td>
+			<td>
+				This is a new detection.
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="b3d033ea9f364574b0a2ec4223f4d718" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
+			<td>XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers</td>
+      <td>Log</td>
+      <td>Disabled</td>
 			<td>
-				XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers
+				This is a new detection. 
 			</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="76c37816ef5c4997ab2080a36978def1" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - Headers</td>
-			<td>Log</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+      <td>Log</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>  
+      <tr>
+      <td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="7d6757e8a28f4853a72b4ce6ebd81645" />
 			</td>
-			<td>N/A</td>
+      <td>N/A</td>
 			<td>XSS, HTML Injection - Link Tag - URI</td>
-			<td>Disabled</td>
-			<td>Disabled</td>
-			<td>This is a new detection.</td>
-		</tr>
-	</tbody>
+      <td>Disabled</td>
+      <td>Disabled</td>
+			<td>
+				This is a new detection. 
+			</td>
+    </tr>           
+</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-04-27-waf-release.mdx b/src/content/changelog/waf/2026-04-27-waf-release.mdx
index cff93d4886276d7..0693afdefc19da2 100644
--- a/src/content/changelog/waf/2026-04-27-waf-release.mdx
+++ b/src/content/changelog/waf/2026-04-27-waf-release.mdx
@@ -12,12 +12,14 @@ This week's release focuses on new improvements to enhance coverage.
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
+
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +29,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,198 +39,188 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
-				This is a new detection. This rule is merged into the original rule
+				This is a new detection.  This rule is merged into the original rule
 				"PostgreSQL - SQLi - COPY - Body (ID:{" "}
-				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />
-				). The rule previously known as "PostgreSQL - SQLi - COPY" is now
-				renamed to "PostgreSQL - SQLi - COPY - Body".
+				<RuleID id="705a6b5569d5472596910e3ce7265a4e" />). The rule previously known as "PostgreSQL - SQLi - COPY" is now renamed to "PostgreSQL - SQLi - COPY - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="71d133c374d94559aa9fdf042903de89" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9f1b1b7fd28a401b9d5c172d1036cfa6" />
 			</td>
 			<td>N/A</td>
 			<td>PostgreSQL - SQLi - COPY - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>  
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="8e40416659334b8ba789365755ff389e" />
 			</td>
-			<td>N/A</td>
+   			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR MAKE_SET/ELT - Body" (ID:{" "}
-				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />
-				). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now
-				renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
+				<RuleID id="0f41a593c8fe42c38a26f709252d3934" />). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="1e0d4372ee1e41b9804b2d5c346487f9" />
 			</td>
-			<td>N/A</td>
+   			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d2c961a164a64cf6b871c9511ac6ceca" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR MAKE_SET/ELT - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="4dacc0e6f32d4c5da3c2293edd471337" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Common Patterns - Body" (ID:{" "}
-				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />
-				). The rule previously known as "SQLi - Common Patterns" is now renamed
-				to "SQLi - Common Patterns - Body".
+				<RuleID id="98f746d07a6d48ab9dae669acb5d0b9b" />). The rule previously known as "SQLi - Common Patterns" is now renamed to "SQLi - Common Patterns - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="53a374379f2e41e9934791c1975c07b7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="9efedebfc371443f9fe7308605b1b06b" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Common Patterns - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="d53a791496d64700870334f4dd0ba3c7" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Equation - Body" (ID:{" "}
-				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />
-				). The rule previously known as "SQLi - Equation" is now renamed to
-				"SQLi - Equation - Body".
+				<RuleID id="e7691e1e4f4d4769909f3df6c2eb3e7f" />). The rule previously known as "SQLi - Equation" is now renamed to "SQLi - Equation - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46efbd3496e64c3f902ad33d3d1c2384" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="46b937649a424b7ead90f6d0e1149ea6" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Equation - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="04d9182545f54ba8a4fa29fe205adbb0" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - AND/OR Digit Operator Digit - Body" (ID:{" "}
-				<RuleID id="762dd334ed0b4273816e3ff13893c564" />
-				). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is
-				now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
+				<RuleID id="762dd334ed0b4273816e3ff13893c564" />). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is now renamed to "SQLi - AND/OR Digit Operator Digit - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="a24e7c15503948bc8766481aad2abbaa" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - AND/OR Digit Operator Digit - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="a24e7c15503948bc8766481aad2abbaa" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - AND/OR Digit Operator Digit - Headers</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+        </tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="0c55eb362df64f92a85aa46753acbc0d" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - AND/OR Digit Operator Digit - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="18c9879b7e184c559d23c1652b45a97d" />
-			</td>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="18c9879b7e184c559d23c1652b45a97d" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Beta</td>
 			<td>Log</td>
@@ -236,24 +228,22 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Benchmark Function - Body" (ID:{" "}
-				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />
-				). The rule previously known as "SQLi - Benchmark Function" is now
-				renamed to "SQLi - Benchmark Function - Body".
+				<RuleID id="ac4e9ebfb43a4f3998f6072d2ebc44ad" />). The rule previously known as "SQLi - Benchmark Function" is now renamed to "SQLi - Benchmark Function - Body".
 			</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="2adbc36c52324efcb4681b829889aadc" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Benchmark Function - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>		
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="69564af3bc54406080deed72491b28e9" />
 			</td>
@@ -264,7 +254,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>This is a new detection.</td>
 		</tr>
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="94b1646f0b0b46ec9b96f7742aa649de" />
 			</td>
@@ -275,166 +265,151 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - Comparison - Body" (ID:{" "}
-				<RuleID id="8166da327a614849bfa29317e7907480" />
-				). The rule previously known as "SQLi - Comparison" is now renamed to
-				"SQLi - Comparison - Body".
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="455ce87681bd4200bf53456c39e3e013" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - Headers</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
+				<RuleID id="8166da327a614849bfa29317e7907480" />). The rule previously known as "SQLi - Comparison" is now renamed to "SQLi - Comparison - Body".
+			</td>
+		</tr>
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="455ce87681bd4200bf53456c39e3e013" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - Comparison - Headers</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+		</tr>	
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="8152816062ed47f69be0f907f4bdb492" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - Comparison - URI</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection.</td>
+		</tr>
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - String Concatenation - Body - Beta</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection. This rule is merged into the original rule "SQLi - String Concatenation - Headers" (ID:{" "}
+				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />).The rule previously known as "SQLi - String Concatenation - Headers" is now renamed to "SQLi - String Concatenation - Body". </td>
+		</tr>	
+        <tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="8152816062ed47f69be0f907f4bdb492" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - Comparison - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>This is a new detection.</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="d5afd403a0544248b829fe5da1ff3b34" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Concatenation - Body - Beta</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. This rule is merged into the original rule
-				"SQLi - String Concatenation - Headers" (ID:{" "}
-				<RuleID id="3b0c61407d0b4f7d87e516472116d2fe" />
-				).The rule previously known as "SQLi - String Concatenation - Headers"
-				is now renamed to "SQLi - String Concatenation - Body".{" "}
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
-			</td>
-			<td>N/A</td>
+            <td>
+                <RuleID id="cb0ec290ee454138abe18b750d0e6c3b" />
+            </td>
+            <td>N/A</td>
 			<td>SQLi - String Concatenation - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection.(Former Id was{" "}
-				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)
-			</td>
-		</tr>
+            <td>Block</td>
+			<td>This is a new detection.(Former Id was{" "}
+				<RuleID id="380099df2bb2469c91ebbb7b846d1940" />)</td>
+		</tr>		
+		<tr>
+        	<td>Cloudflare Managed Ruleset</td>
+            <td>
+                <RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
+            </td>
+            <td>N/A</td>
+            <td>SQLi - String Concatenation - URI</td>
+            <td>Log</td>
+            <td>Block</td>
+            <td>This is a new detection. (Former Id was{" "}
+				<RuleID id="bd19397228404b85aa3797238fae8c84" />)</td>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="c46d9097c9ef419aa4d9f10626cc211f" />
-			</td>
-			<td>N/A</td>
-			<td>SQLi - String Concatenation - URI</td>
-			<td>Log</td>
-			<td>Block</td>
-			<td>
-				This is a new detection. (Former Id was{" "}
-				<RuleID id="bd19397228404b85aa3797238fae8c84" />)
-			</td>
-		</tr>
-		<tr>
-			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
-			</td>
-			<td>N/A</td>
+            <td>
+                <RuleID id="6542d36980cf4018b4d5e2bfeacc78ab" />
+            </td>
+            <td>N/A</td>
 			<td>SQLi - SELECT Expression - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - SELECT Expression - Body" (ID:{" "}
-				<RuleID id="00da180570d34b5bae2121acd0023a36" />
-				). The rule previously known as "SQLi - SELECT Expression" is now
-				renamed to "SQLi - SELECT Expression - Body".
+				<RuleID id="00da180570d34b5bae2121acd0023a36" />). The rule previously known as "SQLi - SELECT Expression" is now renamed to "SQLi - SELECT Expression - Body".
 			</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="4073f7b575ff45dfb7621b43630bb223" />
-			</td>
+            <td>
+                <RuleID id="4073f7b575ff45dfb7621b43630bb223" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
-			</td>
+            <td>
+                <RuleID id="2721e3184d50466ea637e9afdcd6efb5" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - SELECT Expression - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
-			</td>
+            <td>
+                <RuleID id="7ecca84c08aa4aad9b5a7bda18c47cea" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Beta</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"SQLi - ORD and ASCII- Body" (ID:{" "}
-				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />
-				). The rule previously known as "SQLi - ORD and ASCII" is now renamed to
-				"SQLi - ORD and ASCII- Body".
+				<RuleID id="2fc38b34a9d744d2a3cbcc41d0d207f9" />). The rule previously known as "SQLi - ORD and ASCII" is now renamed to "SQLi - ORD and ASCII- Body".
 			</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
-			</td>
+            <td>
+                <RuleID id="f6d10e10c9514eb49dcc2122bdb1618f" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - URI</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
-			<td>
-				<RuleID id="60704f5c5513425c94cf77031d0906b6" />
-			</td>
+            <td>
+                <RuleID id="60704f5c5513425c94cf77031d0906b6" />
+            </td>
 			<td>N/A</td>
 			<td>SQLi - ORD and ASCII - Headers</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>	
 		<tr>
-			<td>Cloudflare Managed Ruleset</td>
+        	<td>Cloudflare Managed Ruleset</td>
 			<td>
 				<RuleID id="700613b191d3479ea2782b4e9fe4eff5" />
 			</td>
 			<td>N/A</td>
 			<td>SQLi - Destructive Operations</td>
 			<td>Log</td>
-			<td>Block</td>
+            <td>Block</td>
 			<td>This is a new detection.</td>
-		</tr>
+		</tr>					
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
index a13aa934882650b..8e8330ad016a2e7 100644
--- a/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-07-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows unauthenticated attackers to bypass middleware or
 We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to Next.js 15.5.16 or 16.2.5 (or later) immediat
 				<RuleID id="1de95bf6d6374e1099854278e77e4a53" />
 			</td>
 			<td>N/A</td>
-			<td>
-				Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575
-			</td>
+			<td>Next.js - Middleware Bypass via Invalid RSC Header - CVE:CVE-2026-44575</td>
 			<td>N/A</td>
 			<td>Disabled</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-11-waf-release.mdx b/src/content/changelog/waf/2026-05-11-waf-release.mdx
index ab5ae2ac0485b0a..043c71508d1a2ef 100644
--- a/src/content/changelog/waf/2026-05-11-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-11-waf-release.mdx
@@ -10,12 +10,14 @@ import { RuleID } from "~/components";
 
 - Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
 
+
 **Continuous Rule Improvements**
 
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
+
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +27,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -39,8 +41,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>
 				This is a new detection. This rule is merged into the original rule
 				"Remote Code Execution - Java Deserialization" (ID:{" "}
-				<RuleID id="36b0532eb3c941449afed2d3744305c4" />
-				).
+				<RuleID id="36b0532eb3c941449afed2d3744305c4" />).
 			</td>
 		</tr>
 	</tbody>
diff --git a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
index 044ad5768701d6e..6699189c3e6941d 100644
--- a/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-15-emergency-waf-release.mdx
@@ -17,7 +17,7 @@ Successful exploitation allows remote attackers to trigger a heap buffer overflo
 We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to address the underlying vulnerability. If you cannot upgrade immediately, avoid `rewrite` directives with `?` in the replacement string followed by `set` or `if` referencing capture groups.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -27,7 +27,7 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -35,12 +35,12 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 				<RuleID id="2013e3e58efe4b79a26e214f7e52be73" />
 			</td>
 			<td>N/A</td>
-			<td>
-				nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945
-			</td>
+			<td>nginx - Remote Code Execution - Buffer Overread - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -51,7 +51,9 @@ We strongly recommend upgrading to nginx 1.30.1 (or later) immediately to addres
 			<td>nginx - Remote Code Execution - Heap Spray - CVE:CVE-2026-42945</td>
 			<td>N/A</td>
 			<td>Block</td>
-			<td>This is a new detection.</td>
+			<td>
+				This is a new detection.
+			</td>
 		</tr>
 	</tbody>
 </table>
diff --git a/src/content/changelog/waf/2026-05-20-waf-release.mdx b/src/content/changelog/waf/2026-05-20-waf-release.mdx
index e26381409165dae..f6bd07a5a23d740 100644
--- a/src/content/changelog/waf/2026-05-20-waf-release.mdx
+++ b/src/content/changelog/waf/2026-05-20-waf-release.mdx
@@ -15,7 +15,7 @@ import { RuleID } from "~/components";
 We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.
 
 <table style="width: 100%">
-	<thead>
+  <thead>
 		<tr>
 			<th>Ruleset</th>
 			<th>Rule ID</th>
@@ -25,7 +25,7 @@ We are continuously refining our managed rules to provide more resilient protect
 			<th>New Action</th>
 			<th>Comments</th>
 		</tr>
-	</thead>
+  </thead>
 	<tbody>
 		<tr>
 			<td>Cloudflare Managed Ruleset</td>
@@ -37,11 +37,9 @@ We are continuously refining our managed rules to provide more resilient protect
 			<td>N/A</td>
 			<td>Block</td>
 			<td>
-				This rule is merged into the original rule "Sitecore - Cache Poisoning -
-				CVE:CVE-2025-53693" (ID:{" "}
-				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />
-				).
+				This rule is merged into the original rule "Sitecore - Cache Poisoning - CVE:CVE-2025-53693" (ID:{" "}
+				<RuleID id="d1bd7563e6254db48ce703807c5b669c" />).
 			</td>
 		</tr>
 	</tbody>
-</table>
+</table>
\ No newline at end of file
diff --git a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
index e6847cc885baddb..c086c1b5689e944 100644
--- a/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
+++ b/src/content/changelog/web-analytics/2026-04-30-rum-navigation-types.mdx
@@ -22,8 +22,8 @@ For more information, refer to [Navigation Types](/web-analytics/data-metrics/di
 
 ### Key benefits
 
-- **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
-- **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
+* **Monitor Cache Effectiveness:** See how often your site is served from the HTTP cache or bfcache.
+* **Identify Performance Bottlenecks:** Filter by the different types to understand performance opportunity of improving browser cache hit ratio.
 
 ### Analyze navigation types in the Cloudflare dashboard
 
diff --git a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
index 023c0a2b71c0c0c..1dbfdc154f12e70 100644
--- a/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-05-openai-open-models.mdx
@@ -13,14 +13,13 @@ Get started with the new models at `@cf/openai/gpt-oss-120b` and `@cf/openai/gpt
 Check out the [blog](https://blog.cloudflare.com/openai-gpt-oss-on-workers-ai) for more details about the new models, and the [`gpt-oss-120b`](/workers-ai/models/gpt-oss-120b) and [`gpt-oss-20b`](/workers-ai/models/gpt-oss-20b) model pages for more information about pricing and context windows.
 
 ## Responses API
-
 If you call the model through:
-
 - Workers Binding, it will accept/return Responses API – `env.AI.run(“@cf/openai/gpt-oss-120b”)`
 - REST API on `/run` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/run/@cf/openai/gpt-oss-120b`
 - REST API on new `/responses` endpoint, it will accept/return Responses API – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses`
 - REST API for OpenAI Compatible endpoint, it will return Chat Completions (coming soon) – `https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/chat/completions`
 
+
 ```
 curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses \
   -H "Content-Type: application/json" \
@@ -40,9 +39,7 @@ curl https://api.cloudflare.com/client/v4/accounts/<account_id>/ai/v1/responses
 ```
 
 ## Code Interpreter
-
 The model is natively trained to support stateful code execution, and we've implemented support for this feature using our [Sandbox SDK](https://github.com/cloudflare/sandbox-sdk) and [Containers](https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/). Cloudflare's Developer Platform is uniquely positioned to support this feature, so we're very excited to bring our products together to support this new use case.
 
 ## Web Search (coming soon)
-
 We are working to implement Web Search for the model, where users can bring their own Exa API Key so the model can browse the Internet.
diff --git a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
index 4a63321c26bcb30..21359bd2975b689 100644
--- a/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
+++ b/src/content/changelog/workers-ai/2025-08-27-partner-models.mdx
@@ -11,7 +11,6 @@ New state-of-the-art models have landed on Workers AI! This time, we're introduc
 As well, we're introuding a new turn detection model that enables you to detect when someone is done speaking — useful for building voice agents!
 
 Read the [blog](https://blog.cloudflare.com/workers-ai-partner-models) for more details and check out some of the new models on our platform:
-
 - [`@cf/deepgram/aura-1`](/workers-ai/models/aura-1) is a text-to-speech model that allows you to input text and have it come to life in a customizable voice
 - [`@cf/deepgram/nova-3`](/workers-ai/models/nova-3) is speech-to-text model that transcribes multilingual audio at a blazingly fast speed
 - [`@cf/pipecat-ai/smart-turn-v2`](/workers-ai/models/smart-turn-v2) helps you detect when someone is done speaking
@@ -55,4 +54,4 @@ async def text_to_speech():
 
 if __name__ == "__main__":
     asyncio.run(text_to_speech())
-```
+```
\ No newline at end of file
diff --git a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
index f19b116401280e9..27cdbf6ba1773e1 100644
--- a/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
+++ b/src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx
@@ -12,10 +12,9 @@ We're excited to be a launch partner alongside [Google](https://developers.googl
 Now you can leverage EmbeddingGemma directly through AI Search for your RAG pipelines. EmbeddingGemma's multilingual capabilities make it perfect for global applications that need to understand and retrieve content across different languages with exceptional accuracy.
 
 To use EmbeddingGemma for your AI Search projects:
-
 1. Go to **Create** in the [AI Search dashboard](https://dash.cloudflare.com/?to=/:account/ai/ai-search)
 2. Follow the setup flow for your new RAG instance
 3. In the **Generate Index** step, open up **More embedding models** and select `@cf/google/embeddinggemma-300m` as your embedding model
 4. Complete the setup to create an AI Search
 
-Try it out and let us know what you think!
+Try it out and let us know what you think!
\ No newline at end of file
diff --git a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
index 0f6f06d216ab8ea..479a67c4a458f78 100644
--- a/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
+++ b/src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx
@@ -17,9 +17,7 @@ export default {
 		// Perform application logic in Workers here
 
 		// Sample call to an internal API running on ECS in AWS using the binding
-		const response = await env.AWS_VPC_ECS_API.fetch(
-			"https://internal-host.example.com",
-		);
+		const response = await env.AWS_VPC_ECS_API.fetch("https://internal-host.example.com");
 
 		// Additional application logic in Workers
 		return new Response();
diff --git a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
index cd1650bd65edb75..ad672d1184483df 100644
--- a/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
+++ b/src/content/changelog/workers/2025-02-07-new-ways-to-get-started-on-workers.mdx
@@ -8,13 +8,13 @@ date: 2025-02-07 00:00:00 UTC
 
 ![Import repo or choose template](~/assets/images/workers/choose-template-import-repo.png)
 
-You can now create a Worker by:
+You can now create a Worker by: 
+* **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker. 
+* **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker. 
 
-- **Importing a Git repository**: Choose an existing Git repo on your GitHub/GitLab account and set up [Workers Builds](/workers/ci-cd/builds/configuration/) to deploy your Worker.
-- **Deploying a template with Git**: Choose from a brand new selection of production ready [examples](https://github.com/cloudflare/templates) to help you get started with popular frameworks like [Astro](https://astro.build/), [Remix](https://remix.run/) and [Next](https://nextjs.org/) or build stateful applications with Cloudflare resources like [D1 databases](/d1/), [Workers AI](/workers-ai/) or [Durable Objects](/durable-objects/)! When you're ready to deploy, Cloudflare will set up your project by cloning the template to your GitHub/GitLab account, provisioning any required [resources](/workers/runtime-apis/bindings/) and deploying your Worker.
-
-With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker.
+With every push to your chosen branch, Cloudflare will automatically build and deploy your Worker. 
 
 To get started, go to the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create).
 
-These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9).
+These new features are available today in the Cloudflare dashboard to a subset of Cloudflare customers, and will be coming to all customers in the next few weeks. Don't see it in your dashboard, but want early access? Add your Cloudflare Account ID to [this form](https://forms.gle/U1qhkF2snNJDGJJa9). 
+
diff --git a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
index 5b44d0f80ee3d23..f651164ee14bfd0 100644
--- a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
+++ b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
@@ -47,4 +47,4 @@ CPU time was limited.
 For more information on the updates limits, see the documentation on [Wrangler configuration for `cpu_ms`](/workers/wrangler/configuration/#limits)
 and on [Workers CPU time limits](/workers/platform/limits/#cpu-time).
 
-For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
+For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
index 2b8b4d848965a55..d24d77883df382f 100644
--- a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx
@@ -1,28 +1,28 @@
 ---
 title: Deploy a Workers application in seconds with one-click
-description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project.
+description: You can now add a Deploy to Cloudflare button to your repository's README to help other developers set up and deploy your project. 
 products:
   - workers
 date: 2025-04-08 00:00:00 UTC
 ---
-
-You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project!
+You can now add a [Deploy to Cloudflare](/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project! 
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/saas-admin-template)
 
-The Deploy to Cloudflare button:
 
-1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing.
-2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment.
+The Deploy to Cloudflare button: 
+1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
+2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 
-To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL:
+
+To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL: 
 
 ```md
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=<YOUR_GIT_REPO_URL>)
 ```
 
-Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers.
+Check out our [documentation](/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers. 
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
index a03418408567548..b0b15c17427b454 100644
--- a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
+++ b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -7,7 +7,7 @@ date: 2025-04-09
 hidden: false
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig } from "~/components"
 
 The [Workers Observability dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](/workers/observability/logs/workers-logs).
 
@@ -16,7 +16,6 @@ The **Overview** tab shows logs from all your Workers in one place. The **Invoca
 ![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png)
 
 The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:
-
 - Which paths are experiencing the most 5XX errors?
 - What is the wall time distribution by status code for my Worker?
 - What are the slowest requests, and where are they coming from?
@@ -31,7 +30,6 @@ The Query Builder can use any field that you store in your logs as a key to visu
 [Workers Logs](/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.
 
 We've introduced a number of changes during our beta period, including:
-
 - Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
 - Performance improvements to ensure no adverse impact
 - Public [API endpoints](https://developers.cloudflare.com/api/resources/workers/subresources/observability/) for broader consumption
diff --git a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
index b452371c6b814cf..9361cb8dd0b783c 100644
--- a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
+++ b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
@@ -52,4 +52,4 @@ npx wrangler dev --test-scheduled
 curl "http://localhost:8787/cdn-cgi/handler/scheduled?cron=*+*+*+*+*"
 ```
 
-Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
+Consult the [Workers Cron Triggers page](/workers/configuration/cron-triggers/) for full details on cron triggers in Workers.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
index 66b3abe85c67f76..1adf754ef15b998 100644
--- a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
+++ b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
@@ -84,4 +84,4 @@ Then test your new Durable Object locally by running `wrangler dev`:
 npx wrangler dev
 ```
 
-Consult the [Durable Objects documentation](/durable-objects/) for more details.
+Consult the [Durable Objects documentation](/durable-objects/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-06-05-open-next-size.mdx b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
index f812ab669e4ae81..dc09195d36386df 100644
--- a/src/content/changelog/workers/2025-06-05-open-next-size.mdx
+++ b/src/content/changelog/workers/2025-06-05-open-next-size.mdx
@@ -15,4 +15,4 @@ This means that users will now see a decrease from 14 to 8MiB (2.3 to 1.6MiB gzi
 Users only need to update to the latest version of `@opennextjs/cloudflare` to automatically benefit from these improvements.
 
 Note that we published [CVE-2005-6087](https://github.com/opennextjs/opennextjs-cloudflare/security/advisories/GHSA-rvpw-p7vw-wj3m) for a SSRF vulnerability in the `@opennextjs/cloudflare` package.
-The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one.
+The vulnerability has been fixed from `@opennextjs/cloudflare` v1.3.0 onwards. Please update to any version after this one. 
diff --git a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
index 09e28a32e4a37af..cdfb5847ef6dfaf 100644
--- a/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
+++ b/src/content/changelog/workers/2025-07-23-workers-preview-urls.mdx
@@ -17,8 +17,8 @@ These preview URLs are named after your branch and are posted as a comment to ea
 
 Each comment includes **two preview URLs** as shown above:
 
-- **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
-- **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
+* **Commit Preview URL**: Unique to the specific version/commit (e.g., `<version-prefix>-<worker-name>.<subdomain>.workers.dev`)
+* **Branch Preview URL**: A stable alias based on the branch name (e.g., `<branch-name>-<worker-name>.<subdomain>.workers.dev`)
 
 ## How it works
 
@@ -39,7 +39,7 @@ wrangler versions upload --preview-alias staging
 
 ## Limitations while in beta
 
-- Only available on the **workers.dev** subdomain (custom domains not yet supported)
-- Requires **Wrangler v4.21.0+**
-- Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
-- Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
+* Only available on the **workers.dev** subdomain (custom domains not yet supported)
+* Requires **Wrangler v4.21.0+**
+* Preview URLs are not generated for Workers that use [Durable Objects](/durable-objects/)
+* Not yet supported for [Workers for Platforms](/cloudflare-for-platforms/workers-for-platforms/)
diff --git a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
index 62563705d8ffbf1..69b92f1517e3f97 100644
--- a/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
+++ b/src/content/changelog/workers/2025-08-04-builds-increased-disk-size.mdx
@@ -1,17 +1,15 @@
 ---
 title: Increased disk space for Workers Builds
-description:
-  Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
+description: Increased the available disk space for Workers Builds from 8 GB to 20 GB for all plans during the ongoing open beta.
   - workers
 date: 2025-08-04T01:00:00Z
 ---
-
-As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans.
+As part of the ongoing open beta for [Workers Builds](/workers/ci-cd/builds/), we’ve increased the available disk space for builds from **8 GB** to **20 GB** for both Free and Paid plans. 
 
 This provides more space for larger projects, dependencies, and build artifacts while improving overall build reliability.
 
 | Metric     | Free Plan | Paid Plans |
-| ---------- | --------- | ---------- |
+|------------|-----------|------------|
 | Disk Space | 20 GB     | 20 GB      |
 
 All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including CPU, memory, build minutes, and timeout remain unchanged.
diff --git a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
index 38902472bf8ef79..ec55122dca6b4e3 100644
--- a/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
+++ b/src/content/changelog/workers/2025-08-08-add-waituntil-cloudflare-workers.mdx
@@ -40,7 +40,7 @@ export default {
 		// Background task that should complete even after response is sent
 		cleanupTempData(env.KV_NAMESPACE);
 		return new Response("Hello, World!");
-	},
+	}
 };
 
 function cleanupTempData(kvNamespace) {
diff --git a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
index ac79e16b37b4196..4b869cc6a72861c 100644
--- a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
+++ b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx
@@ -19,7 +19,7 @@ Now, Cloudflare automatically truncates long branch names and appends a unique h
 - **Hash generation**: The hash is derived from the full branch name to ensure uniqueness
 - **Stable URLs**: The same branch always generates the same hash across all commits
 
-## Requirements and compatibility
+## Requirements and compatibility 
 
 - **Wrangler 4.30.0 or later**: This feature requires updating to wrangler@4.30.0+
-- **No configuration needed**: Works automatically with existing preview URL setups
+- **No configuration needed**: Works automatically with existing preview URL setups
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-08-11-messagechannel.mdx b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
index c6fc102f02133c4..b73740d15413afb 100644
--- a/src/content/changelog/workers/2025-08-11-messagechannel.mdx
+++ b/src/content/changelog/workers/2025-08-11-messagechannel.mdx
@@ -17,10 +17,10 @@ using the `no_expose_global_message_channel` compatibility flag.
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log("Received message:", event.data);
+	console.log('Received message:', event.data);
 };
 
-port2.postMessage("Hello from port2!");
+port2.postMessage('Hello from port2!');
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -29,13 +29,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-- Transfer lists are currently not supported. This means that you will not be able to transfer
+* Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-  are errors serializing or deserializing the message data. Instead, the error will be thrown when
-  the `postMessage` method is called on the sending port.
-- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+	are errors serializing or deserializing the message data. Instead, the error will be thrown when
+	the `postMessage` method is called on the sending port.
+* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
index 63d4feab2b544fb..c3da28c859aaa68 100644
--- a/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
+++ b/src/content/changelog/workers/2025-08-14-new-python-handlers.mdx
@@ -34,4 +34,4 @@ To keep using the old-style handlers, you can specify the `disable_python_no_glo
 
 </WranglerConfig>
 
-Consult the [Python Workers documentation](/workers/languages/python/) for more details.
+Consult the [Python Workers documentation](/workers/languages/python/) for more details.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
index 0665a23c274b592..71100f87446e32c 100644
--- a/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
+++ b/src/content/changelog/workers/2025-08-14-workers-terraform-and-sdk-improvements.mdx
@@ -90,16 +90,20 @@ const scriptContent = `
   };
 `;
 
-client.workers.scripts.versions.create("my-worker", {
-	account_id: "123456789",
-	metadata: {
-		main_module: "my-worker.mjs",
-	},
-	files: [
-		await toFile(Buffer.from(scriptContent), "my-worker.mjs", {
-			type: "application/javascript+module",
-		}),
-	],
+client.workers.scripts.versions.create('my-worker', {
+  account_id: '123456789',
+  metadata: {
+    main_module: 'my-worker.mjs',
+  },
+  files: [
+    await toFile(
+      Buffer.from(scriptContent),
+      'my-worker.mjs',
+      {
+        type: "application/javascript+module",
+      }
+    )
+  ]
 });
 ```
 
@@ -111,20 +115,19 @@ Previously when creating a KV value like this:
 
 ```js
 await cf.kv.namespaces.values.update("my-kv-namespace", "key1", {
-	account_id: "123456789",
-	metadata: "my metadata",
-	value: JSON.stringify({
-		hello: "world",
-	}),
+  account_id: "123456789",
+  metadata: "my metadata",
+  value: JSON.stringify({
+    hello: "world"
+  })
 });
 ```
 
 ...and recalling it in your Worker like this:
-
 ```ts
-const value = await c.env.KV.get<{ hello: string }>("key1", "json");
+const value = await c.env.KV.get<{hello: string}>("key1", "json");
 ```
 
-You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}`
+You'd get back this: `{metadata:'my metadata', value:"{'hello':'world'}"}` instead of the correct value of `{hello: 'world'}` 
 
 This is fixed in cloudflare-typescript 4.5.0 and will be fixed in cloudflare-python 4.4.0.
diff --git a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
index edafaed88b57a69..26a69c93645b1c1 100644
--- a/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
+++ b/src/content/changelog/workers/2025-08-15-static-assets-redirect-url.mdx
@@ -1,9 +1,9 @@
 ---
-title: "Workers Static Assets: Corrected handling of double slashes in redirect rule paths"
+title: 'Workers Static Assets: Corrected handling of double slashes in redirect rule paths'
 description: Corrected handling of double slashes in redirect rule paths
 date: 2025-08-15
 ---
-
-[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed.
+ 
+[Static Assets](/workers/static-assets/): Fixed a bug in how [redirect rules](https://developers.cloudflare.com/workers/static-assets/redirects/) defined in your Worker's `_redirects` file are processed. 
 
 If you're serving Static Assets with a `_redirects` file containing a rule like `/ja/* /:splat`, paths with double slashes were previously misinterpreted as external URLs. For example, visiting `/ja//example.com` would incorrectly redirect to `https://example.com` instead of `/example.com` on your domain. This has been fixed and double slashes now correctly resolve as local paths. Note: [Cloudflare Pages](/pages/) was not affected by this issue.
diff --git a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
index bf358c54fd5a98d..607ca9dbee7a667 100644
--- a/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
+++ b/src/content/changelog/workers/2025-08-19-improved-wrangler-error-screen.mdx
@@ -10,8 +10,8 @@ Wrangler's error screen has received several improvements to enhance your debugg
 
 The error screen now features a refreshed design thanks to [youch](https://www.npmjs.com/package/youch), with support for both light and dark themes, improved source map resolution logic that handles missing source files more reliably, and better error cause display.
 
-| Before                                                                             | After (Light)                                                                                        | After (Dark)                                                                                       |
-| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Before | After (Light) | After (Dark) |
+|--------|---------------|--------------|
 | ![Old error screen](../../../assets/images/workers/changelog/old-error-screen.png) | ![New light theme error screen](../../../assets/images/workers/changelog/new-error-screen-light.png) | ![New dark theme error screen](../../../assets/images/workers/changelog/new-error-screen-dark.png) |
 
 Try it out now with `npx wrangler@latest dev` in your Workers project.
diff --git a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
index 383e128922da73e..d5f72b78d505a8f 100644
--- a/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
+++ b/src/content/changelog/workers/2025-09-03-new-workers-api.mdx
@@ -3,23 +3,22 @@ title: A new, simpler REST API for Cloudflare Workers (Beta)
 description: Simpler Workers API, SDK methods, and Terraform resources for directly managing Workers, Versions, and Deployments
 date: 2025-09-04
 ---
-
-You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
+You can now manage [**Workers**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployments**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).
 
 This new API is supported in the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) and the [Cloudflare Typescript SDK](https://github.com/cloudflare/cloudflare-typescript), allowing platform teams to manage a Worker's infrastructure in Terraform, while development teams handle code deployments from a separate repository or workflow. We also designed this API with AI agents in mind, as a clear, predictable structure is essential for them to reliably build, test, and deploy applications.
 
 ### Try it out
-
 - [**New beta API endpoints**](/api/resources/workers/subresources/beta/)
 - [**Cloudflare TypeScript SDK v5.0.0**](https://github.com/cloudflare/cloudflare-typescript)
 - [**Cloudflare Go SDK v6.0.0**](https://github.com/cloudflare/cloudflare-go)
 - [**Terraform provider v5.9.0**](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs): [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) , [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version), and [`cloudflare_workers_deployments`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_deployment) resources.
 - See full examples in our [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 
-## Before: Eight+ endpoints with mixed responsibilities
 
+## Before: Eight+ endpoints with mixed responsibilities
 ![**Before**](~/assets/images/workers/platform/api-before.png)
 
+
 The existing API was originally designed for simple, one-shot script uploads:
 
 ```sh
@@ -41,17 +40,15 @@ This API worked for creating a basic Worker, uploading all of its code, and depl
 
 - **Several endpoints implicitly created deployments**: Simple updates like adding a secret or changing a script's content would implicitly create a new version and immediately deploy it.
 
-- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities. This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
+- **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities.  This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
 
 - **Scripts used names as primary identifiers**: This meant simple renames could turn into a risky migration, requiring you to create a brand new Worker and update every reference. If you were using Terraform, this could inadvertently destroy your Worker altogether.
 
 ## After: Three resources with clear boundaries
-
 ![**After**](~/assets/images/workers/platform/api-after.png)
-The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](</api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)>), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
+The new API introduces cleaner resource management with three core resources: [**Worker**](/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](/api/resources/workers/subresources/beta/subresources/workers/models/worker/#(schema)), and [**Deployment**](/api/resources/workers/subresources/scripts/subresources/content/methods/update/).
 
 All endpoints now use simple JSON payloads, with script content embedded as `base64`-encoded strings -- a more consistent and reliable approach than the previous `multipart/form-data` format.
-
 - **Worker**: The parent resource representing your application. It has a stable UUID and holds persistent settings like `name`, `tags`, and `logpush`. You can now create a Worker to establish its identity and settings **before** any code is uploaded.
 
 - **Version**: An immutable snapshot of your code and its specific configuration, like bindings and `compatibility_date`. Creating a new version is a safe action that doesn't affect live traffic.
@@ -69,52 +66,44 @@ All endpoints now use simple JSON payloads, with script content embedded as `bas
 Workers are now standalone resources that can be created and configured without any code. Platform teams can provision Workers with the right settings, then hand them off to development teams for implementation.
 
 #### Example: Typescript SDK
-
 ```ts
 // Step 1: Platform team creates the Worker resource (no code needed)
 const worker = await client.workers.beta.workers.create({
-	name: "payment-service",
-	account_id: "...",
-	observability: {
-		enabled: true,
-	},
+  name: "payment-service",
+  account_id: "...",
+  observability: {
+    enabled: true,
+  },
 });
 
 // Step 2: Development team adds code and creates a version later
 const version = await client.workers.beta.workers.versions.create(worker.id, {
-	account_id: "...",
-	main_module: "worker.js",
-	compatibility_date: "$today",
-	bindings: [
-		/*...*/
-	],
-	modules: [
-		{
-			name: "worker.js",
-			content_type: "application/javascript+module",
-			content_base64: Buffer.from(scriptContent).toString("base64"),
-		},
-	],
+  account_id: "...",
+  main_module: "worker.js",
+  compatibility_date: "$today",
+  bindings: [ /*...*/ ],
+  modules: [
+    {
+      name: "worker.js",
+      content_type: "application/javascript+module",
+      content_base64: Buffer.from(scriptContent).toString("base64"),
+    },
+  ],
 });
 
 // Step 3: Deploy explicitly when ready
-const deployment = await client.workers.scripts.deployments.create(
-	worker.name,
-	{
-		account_id: "...",
-		strategy: "percentage",
-		versions: [
-			{
-				percentage: 100,
-				version_id: version.id,
-			},
-		],
-	},
-);
-```
-
+const deployment = await client.workers.scripts.deployments.create(worker.name, {
+  account_id: "...",
+  strategy: "percentage",
+  versions: [
+    {
+      percentage: 100,
+      version_id: version.id,
+    },
+  ],
+});
+````
 #### Example: Terraform
-
 If you use Terraform, you can now declare the Worker in your Terraform configuration and manage configuration outside of Terraform in your Worker's [`wrangler.jsonc` file](/workers/wrangler/configuration/) and deploy code changes using [Wrangler](/workers/wrangler/).
 
 ```tf
@@ -160,7 +149,6 @@ POST /workers/scripts/{script_name}/deployments
 ```
 
 ### Settings are clearly organized by scope
-
 Configuration is now logically divided: [**Worker settings**](/api/resources/workers/subresources/beta/subresources/workers/) (like `name` and `tags`) persist across all versions, while [**Version settings**](/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) (like `bindings` and `compatibility_date`) are specific to each code snapshot.
 
 ```sh
@@ -192,15 +180,13 @@ The `/workers/workers/` path now supports addressing a Worker by both its immuta
 GET /workers/workers/29494978e03748669e8effb243cf2515  # UUID (stable for automation)
 GET /workers/workers/payment-service                  # Name (convenient for humans)
 ```
-
 This dual approach means:
+  - Developers can use readable names for debugging.
+  - Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
+  - Terraform can rename Workers without destroying and recreating them.
 
-- Developers can use readable names for debugging.
-- Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
-- Terraform can rename Workers without destroying and recreating them.
 
 ## Learn more
-
 - [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 - [API documentation](/api/resources/workers/subresources/beta/)
 - [Versions and Deployments overview](/workers/configuration/versions-and-deployments/)
@@ -209,4 +195,4 @@ This dual approach means:
 
 - The pre-existing Workers REST API remains fully supported. Once the new API exits beta, we'll provide a migration timeline with ample notice and comprehensive migration guides.
 - Existing Terraform resources and SDK methods will continue to be fully supported through the current major version.
-- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
+- While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
index 08db5550e9f1847..8226df15cb8f922 100644
--- a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
+++ b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx
@@ -1,22 +1,19 @@
 ---
 title: Increased vCPU for Workers Builds on paid plans
-description:
-  Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
+description: Increased the available vCPU for Workers Builds from 2 to 4 vCPUs for paid plans, improving build performance and parallel processing capabilities.
   - workers
 date: 2025-09-18
 ---
-
-We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.
+We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.  
 
 These changes continue our focus on making [Workers Builds](/workers/ci-cd/builds/) faster and more reliable.
 
-| Metric | Free Plan | Paid Plans |
-| ------ | --------- | ---------- |
-| CPU    | 2 vCPU    | **4 vCPU** |
+| Metric     | Free Plan | Paid Plans |
+|------------|-----------|------------|
+| CPU |  2 vCPU  |  **4 vCPU**  |
 
 ## Performance Improvements
-
-- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs
+- **Fast build times**: Even single-threaded workloads benefit from having more vCPUs 
 - **2x faster multi-threaded builds**: Tools like [esbuild](https://esbuild.github.io/) and [webpack](https://webpack.js.org/) can now utilize additional cores, delivering near-linear performance scaling
 
-All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
+All other [build limits](/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
index 52947b26e2a263c..ca46348805446ca 100644
--- a/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
+++ b/src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.mdx
@@ -11,13 +11,11 @@ Deploying static site to Workers is now easier. When you run `wrangler deploy [d
 ## Before and after
 
 **Before:** Required remembering multiple flags and parameters
-
 ```bash
 wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project
 ```
 
 **After:** Simple directory deployment with guided setup
-
 ```bash
 wrangler deploy dist
 # Interactive prompts handle the rest as shown in the example flow below
@@ -26,14 +24,12 @@ wrangler deploy dist
 ## What's new
 
 **Interactive prompts for missing configuration:**
-
 - Wrangler detects when you're trying to deploy a directory of static assets
 - Prompts you to confirm the deployment type
 - Asks for a project name (with smart defaults)
 - Automatically sets the compatibility date to today
 
 **Automatic configuration generation:**
-
 - Creates a `wrangler.jsonc` file with your deployment settings
 - Stores your choices for future deployments
 - Eliminates the need to remember complex command-line flags
@@ -64,3 +60,4 @@ wrangler deploy
 ## Requirements
 
 - You must use Wrangler version 4.24.4 or later in order to use this feature
+
diff --git a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
index 8dc771049e2038d..50813da8dd6bb74 100644
--- a/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
+++ b/src/content/changelog/workers/2025-09-10-built-with-cloudflare-button.mdx
@@ -10,4 +10,4 @@ We've updated our "Built with Cloudflare" button to make it easier to share that
 
 ![Built with Cloudflare](https://workers.cloudflare.com/built-with-cloudflare.svg)
 
-Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
+Check out the [documentation](/workers/platform/built-with-cloudflare) for usage information.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
index b36f8560a42c020..ad92d184dcdbf29 100644
--- a/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
+++ b/src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx
@@ -5,15 +5,14 @@ products:
   - workers
 date: 2025-09-11
 ---
-
 The number of recent versions available for a Worker rollback has been increased from 10 to 100.
 
-This allows you to:
+This allows you to: 
 
-- Promote any of the 100 most recent versions to be the active deployment.
+* Promote any of the 100 most recent versions to be the active deployment. 
 
-- Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
 
 You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/general/#rollback)
 
-Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/).
+Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 
diff --git a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
index 36d8857e5b5101a..b43c774dfedb8db 100644
--- a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
+++ b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx
@@ -1,15 +1,13 @@
 ---
 title: Preview URLs now default to opt-in
-description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in.
+description: We performed a one-time update to disable preview URLs on Workers with workers.dev disabled to require an explicit opt-in. 
 date: 2025-09-17
 ---
-
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers.
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
 
 ## One-Time Update for Workers with workers.dev Disabled
-
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
 
 Because preview URLs were historically enabled by default, users who had intentionally disabled their workers.dev route may not have realized their Worker was still accessible at a separate preview URL. This update was performed to ensure that using a preview URL is always an intentional, opt-in choice.
diff --git a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
index 2e03e6d00a562e1..f4d8ebd421fb775 100644
--- a/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
+++ b/src/content/changelog/workers/2025-09-19-ratelimit-workers-ga.mdx
@@ -5,8 +5,8 @@ products:
   - workers
 date: 2025-09-19
 ---
-
-[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA).
+ 
+[Rate Limiting within Cloudflare Workers](/workers/runtime-apis/bindings/rate-limit/) is now Generally Available (GA). 
 
 The `ratelimit` binding is now stable and recommended for all production workloads. Existing deployments using the unsafe binding will continue to function to allow for a smooth transition.
 
diff --git a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
index ae4a4020187a762..0af736a78a816cc 100644
--- a/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
+++ b/src/content/changelog/workers/2025-09-23-wrangler-dev-multi-config-cross-command-support.mdx
@@ -13,6 +13,7 @@ wrangler dev --config ./web/wrangler.jsonc --config ./api/wrangler.jsonc
 ```
 
 Previously, if you ran the command above and then also ran wrangler dev for a different Worker, the Workers running in separate wrangler dev sessions could not communicate with each other. This prevented you from being able to use [Service Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) and [Tail Workers](https://developers.cloudflare.com/workers/observability/logs/tail-workers/) in local development, when running separate wrangler dev sessions.
+	
 Now, the following works as expected:
 
 ```sh
@@ -27,17 +28,17 @@ These Workers can now communicate with each other across separate dev commands,
 
 ```js title="./api/src/index.ts"
 export default {
-	async fetch(request, env) {
-		// This service binding call now works across dev commands
-		const authorized = await env.AUTH.isAuthorized(request);
+  async fetch(request, env) {
+    // This service binding call now works across dev commands
+    const authorized = await env.AUTH.isAuthorized(request);
 
-		if (!authorized) {
-			return new Response("Unauthorized", { status: 401 });
-		}
+    if (!authorized) {
+      return new Response('Unauthorized', { status: 401 });
+    }
 
-		return new Response("Hello from API Worker!", { status: 200 });
-	},
+    return new Response('Hello from API Worker!', { status: 200 });
+  },
 };
 ```
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
+Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
index efbdbc961f780a8..811b7c54cb413df 100644
--- a/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-09-26-analytics-engine-sql-enhancements.mdx
@@ -1,19 +1,17 @@
 ---
 title: Workers Analytics Engine adds supports for new SQL functions
-description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions!
+description: Workers Analytics Engine now supports additional SQL functions including new mathematical operations, aggregate functions, and bit functions! 
 date: 2025-10-02
 products:
   - workers-analytics-engine
 ---
-
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
-
 - `argMin()` - Returns the value associated with the minimum in a group
 - `argMax()` - Returns the value associated with the maximum in a group
 - `topK()` - Returns an array of the most frequent values in a group
@@ -22,7 +20,6 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `last_value()` - Returns the last value in an ordered set of values within a partition
 
 [**New bit functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/bit-functions/)
-
 - `bitAnd()` - Returns the bitwise AND of two expressions
 - `bitCount()` - Returns the number of bits set to one in the binary representation of a number
 - `bitHammingDistance()` - Returns the number of bits that differ between two numbers
@@ -36,28 +33,24 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `bitXor()` - Returns the bitwise exclusive-or of two expressions
 
 [**New mathematical functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/mathematical-functions/)
-
 - `abs()` - Returns the absolute value of a number
 - `log()` - Computes the natural logarithm of a number
-- `round()` - Rounds a number to a specified number of decimal places
+- `round()` - Rounds a number to a specified number of decimal places  
 - `ceil()` - Rounds a number up to the nearest integer
 - `floor()` - Rounds a number down to the nearest integer
 - `pow()` - Returns a number raised to the power of another number
 
 [**New string functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/string-functions/)
-
 - `lowerUTF8()` - Converts a string to lowercase using UTF-8 encoding
 - `upperUTF8()` - Converts a string to uppercase using UTF-8 encoding
 
 [**New encoding functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/encoding-functions/)
-
 - `hex()` - Converts a number to its hexadecimal representation
-- `bin()` - Converts a string to its binary representation
+- `bin()` - Converts a string to its binary representation 
 
 [**New type conversion functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/type-conversion-functions/)
-
 - `toUInt8()` - Converts any numeric expression, or expression resulting in a string representation of a decimal, into an unsigned 8 bit integer
 
-## Ready to get started?
 
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
+## Ready to get started? 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
diff --git a/src/content/changelog/workers/2025-09-26-ctx-exports.md b/src/content/changelog/workers/2025-09-26-ctx-exports.md
index 19bcc4be7d98ad5..ca40c83e6442e7d 100644
--- a/src/content/changelog/workers/2025-09-26-ctx-exports.md
+++ b/src/content/changelog/workers/2025-09-26-ctx-exports.md
@@ -12,17 +12,17 @@ Example:
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class Greeter extends WorkerEntrypoint {
-	greet(name) {
-		return `Hello, ${name}!`;
-	}
+  greet(name) {
+    return `Hello, ${name}!`;
+  }
 }
 
 export default {
-	async fetch(request, env, ctx) {
-		let greeting = await ctx.exports.Greeter.greet("World");
-		return new Response(greeting);
-	},
-};
+  async fetch(request, env, ctx) {
+    let greeting = await ctx.exports.Greeter.greet("World")
+    return new Response(greeting);
+  }
+}
 ```
 
 At present, you must use [the `enable_ctx_exports` compatibility flag](/workers/configuration/compatibility-flags#enable-ctxexports) to enable this API, though it will be on by default in the future.
diff --git a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
index 7ae62260c3c8ae4..374f4f9426567ed 100644
--- a/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-assets-terraform.mdx
@@ -5,8 +5,7 @@ products:
   - workers
 date: 2025-10-09
 ---
-
-import { Code } from "astro-expressive-code/components";
+import { Code } from 'astro-expressive-code/components';
 
 You can now upload Workers with [static assets](/workers/static-assets/) (like HTML, CSS, JavaScript, images) with the [Cloudflare Terraform provider v5.11.0](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), making it even easier to deploy and manage full-stack apps with IaC.
 
@@ -16,12 +15,14 @@ You can now upload Workers with [static assets](/workers/static-assets/) (like H
 
 You can get started today with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs), using either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), or the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+
 ## Examples
 
 #### With `cloudflare_workers_script`
 
 Here's how you can use the existing [`cloudflare_workers_script`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_script) resource to upload your Worker code and assets in one shot.
 
+
 ```hcl
 resource "cloudflare_workers_script" "my_app" {
   account_id  = var.account_id
@@ -81,11 +82,10 @@ resource "cloudflare_workers_deployment" "my_app_deployment" {
 ```
 
 ## What's changed
+Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for *only* those changed files.
 
-Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for _only_ those changed files.
 
 ## Try it out
-
-- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
+-  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs)
 - You can use either the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script) to upload your Worker code and assets in one resource.
 - Or you can use the new beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version) (along with the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment)) resources to more granularly control the lifecycle of each Worker resource.
diff --git a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
index 8305f662b5ae806..a48ee31b4bd8245 100644
--- a/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
+++ b/src/content/changelog/workers/2025-10-09-workflows-terraform.mdx
@@ -20,9 +20,9 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 # Examples
-
 Here are full examples of how to configure `cloudflare_workflow` in Terraform, using the existing [`cloudflare_workers_script` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers_script), and the beta [`cloudflare_worker_version` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker_version).
 
+
 #### With `cloudflare_workflow` and `cloudflare_workers_script`
 
 ```hcl
@@ -44,10 +44,11 @@ resource "cloudflare_workflow" "workflow" {
 
 ```
 
-#### With `cloudflare_workflow`, and the new beta resources
 
+#### With `cloudflare_workflow`, and the new beta resources
 You can more granularly control the lifecycle of each Worker resource using the beta [`cloudflare_worker_version`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/worker_version) resource, alongside the [`cloudflare_worker`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) and [`cloudflare_workers_deployment`](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs/resources/workers_deployment) resources.
 
+
 ```hcl
 
 resource "cloudflare_worker" "workflow_worker" {
@@ -88,5 +89,4 @@ resource "cloudflare_workflow" "my_workflow" {
 ```
 
 ## Try it out
-
-- Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
+-  Get started with [the Cloudflare Terraform provider (v5.11.0)](https://registry.terraform.io/providers/cloudflare/cloudflare/5.11.0/docs) and the new [`cloudflare_workflow` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workflow).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
index 60b2deb83ab1bbe..7e4144ec5e29a50 100644
--- a/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
+++ b/src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx
@@ -3,23 +3,20 @@ title: Workers Preview URL default behavior now matches your workers.dev setting
 description: If a Workers Preview URL setting is not explicitly configured, its default behavior will now match the setting of the workers.dev subdomain.
 date: 2025-10-23
 ---
-
 We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/configuration/previews/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
 
 This change is intended to provide a more intuitive and secure experience by aligning your preview URL's default state with your `workers.dev` configuration to prevent cases where a preview URL might remain public even after you disabled your `workers.dev` route.
 
 **What this means for you:**
-
 - **If neither setting is configured:** both the workers.dev route and the preview URL will default to enabled
 - **If your workers.dev route is enabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to enabled
 - **If your workers.dev route is disabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to disabled
 
-You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file).
+You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file). 
 
 **Wrangler Version Behavior**
 
 The default behavior depends on the version of Wrangler you are using. This new logic applies to the latest version. Here is a summary of the behavior across different versions:
-
 - **Before v4.34.0:** Preview URLs defaulted to enabled, regardless of the workers.dev setting.
 - **v4.34.0 up to (but not including) v4.44.0:** Preview URLs defaulted to disabled, regardless of the workers.dev setting.
 - **v4.44.0 or later:** Preview URLs now default to matching your workers.dev setting.
@@ -30,7 +27,7 @@ In July, [we introduced preview URLs to Workers](/changelog/2025-07-23-workers-p
 
 To address this, we made a [one-time update](/changelog/2025-09-17-update-preview-url-setting/) to disable preview URLs on existing Workers that had their workers.dev route disabled and changed the default behavior to be disabled for all new deployments where a preview URL setting was not explicitly configured.
 
-While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience.
+While this change helped secure many customers, it was disruptive for customers who keep their `workers.dev` route enabled and actively use the preview functionality, as it now required them to explicitly enable preview URLs on every redeployment.This new, more intuitive behavior ensures that your preview URL settings align with your `workers.dev` configuration by default, providing a more secure and predictable experience. 
 
 **Securing access to `workers.dev` and preview URL endpoints**
 
diff --git a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
index a4a42cacd6469f1..8d5b16c36bd1a5c 100644
--- a/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
+++ b/src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx
@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
 
 Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
 
-Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag.
+Automatic provisioning is launching as an open beta, and we'd love to hear your feedback to help us make improvements! It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag. 
 
 To use this feature, update to wrangler@4.45.0 and add bindings to your config file _without_ resource IDs e.g.:
 
diff --git a/src/content/changelog/workers/2025-10-30-builds-preview.mdx b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
index b18b3bf98b7469f..6d384a223acd212 100644
--- a/src/content/changelog/workers/2025-10-30-builds-preview.mdx
+++ b/src/content/changelog/workers/2025-10-30-builds-preview.mdx
@@ -10,8 +10,8 @@ You can now access [preview URLs](/workers/configuration/previews/) directly fro
 
 ![preview button](src/assets/images/changelog/workers/builds-preview-button.png)
 
-**What's new**
 
-- A **Preview** button now appears in the top-right corner of the build details page for successful builds
-- Click it to instantly open the latest preview URL
-- Matches the same experience you're familiar with from Pages
+**What's new**
+* A **Preview** button now appears in the top-right corner of the build details page for successful builds
+* Click it to instantly open the latest preview URL
+* Matches the same experience you're familiar with from Pages
diff --git a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
index 3d8cbe449a7111e..f405d7512be43a7 100644
--- a/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
+++ b/src/content/changelog/workers/2025-11-09-cloudflare-env-variable.mdx
@@ -11,7 +11,6 @@ Wrangler now supports using the `CLOUDFLARE_ENV` [environment variable](/workers
 ## What's new
 
 **Environment selection via environment variable:**
-
 - Set `CLOUDFLARE_ENV` to specify which environment to use for Wrangler commands
 - Works with all Wrangler commands that support the `--env` flag
 - The `--env` command line argument takes precedence over the `CLOUDFLARE_ENV` environment variable
diff --git a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
index cbf3d01a00ba625..aa66f983da252d7 100644
--- a/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
+++ b/src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx
@@ -5,21 +5,18 @@ date: 2025-11-12
 products:
   - workers-analytics-engine
 ---
-
 You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
 
-Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
 
-Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
 
 [**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
-
 - `countIf()` - count the number of rows which satisfy a provided condition
 - `sumIf()` - calculate a sum from rows which satisfy a provided condition
 - `avgIf()` - calculate an average from rows which satisfy a provided condition
 
 [**New date and time functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/date-time-functions/)
-
 - `toYear()`
 - `toMonth()`
 - `toDayOfMonth()`
@@ -39,6 +36,5 @@ Today, we've expanded Workers Analytics Engine's SQL capabilities with several n
 - `today()`
 - `toYYYYMM()`
 
-## Ready to get started?
-
-Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/).
+## Ready to get started? 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 
diff --git a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
index 8a813cefea8b895..1151c4807768e2e 100644
--- a/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
+++ b/src/content/changelog/workers/2025-12-01-build-image-policies-dev-plat.mdx
@@ -12,4 +12,4 @@ We've published build image policies for [Workers Builds](/workers/ci-cd/builds/
 - **Major version updates**: Before preinstalled software reaches end-of-life, we update to the next stable LTS version with 3 months’ notice.
 - **Build image version deprecation (Pages only)**: We provide 6 months’ notice before deprecation. Projects on v1 or v2 will be automatically moved to v3 on their specified deprecation dates.
 
-To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
+To prepare for updates, monitor the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
index f8224767a58f981..073712734586f32 100644
--- a/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-cold-start-improvements.mdx
@@ -17,11 +17,11 @@ We set up a benchmark that imports common packages ([httpx](https://www.python-h
 [fastapi](https://fastapi.tiangolo.com/) and [pydantic](https://docs.pydantic.dev/latest/))
 to see how Python Workers stack up against other platforms:
 
-| Platform                  | Mean Cold Start (ms) |
-| ------------------------- | -------------------- |
-| Cloudflare Python Workers | 1027                 |
-| AWS Lambda                | 2502                 |
-| Google Cloud Run          | 3069                 |
+| Platform | Mean Cold Start (ms) |
+|----------|----------------------|
+| Cloudflare Python Workers | 1027 |
+| AWS Lambda | 2502 |
+| Google Cloud Run | 3069 |
 
 These benchmarks run continuously. You can view the results and the methodology on our [benchmark page](https://cold.edgeworker.net).
 
diff --git a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
index 6889ac1e31e515b..47424c741ce45c1 100644
--- a/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
+++ b/src/content/changelog/workers/2025-12-08-python-pywrangler.mdx
@@ -37,4 +37,5 @@ uv run pywrangler deploy
 
 Pywrangler automatically downloads and vendors the necessary packages for your Worker, and these packages are bundled with the Worker when you deploy.
 
+
 Consult the [Python packages documentation](/workers/languages/python/packages/) for full details on Pywrangler and Python package management in Workers.
diff --git a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
index 46b90006bdbbd44..2890f89b49db4ef 100644
--- a/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-optional-config.mdx
@@ -8,4 +8,4 @@ date: 2025-12-08
 
 When using the [Cloudflare Vite plugin](/workers/vite-plugin/) to build and deploy Workers, a Wrangler configuration file is now optional for assets-only (static) sites. If no `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` file is found, the plugin generates sensible defaults for an assets-only site. The `name` is based on the `package.json` or the project directory name, and the `compatibility_date` uses the latest date supported by your installed Miniflare version.
 
-This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
+This allows easier setup for static sites using Vite. Note that SPAs will still need to [set `assets.not_found_handling` to `single-page-application`](https://developers.cloudflare.com/workers/static-assets/routing/single-page-application/) in order to function correctly.
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
index 7be9426da4e23de..b18355b4e98ed59 100644
--- a/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
+++ b/src/content/changelog/workers/2025-12-08-vite-programmatic-config.mdx
@@ -103,4 +103,4 @@ export default defineConfig({
 });
 ```
 
-For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
+For more details and examples, see [Programmatic configuration](/workers/vite-plugin/reference/programmatic-configuration/).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
index c171a822bbc5fa6..64b1e78e3c965cc 100644
--- a/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
+++ b/src/content/changelog/workers/2025-12-16-vitest-ctx-exports-support.mdx
@@ -15,9 +15,9 @@ import { createExecutionContext } from "cloudflare:test";
 import { it, expect } from "vitest";
 
 it("can access ctx.exports", async () => {
-	const ctx = createExecutionContext();
-	const result = await ctx.exports.MyEntryPoint.myMethod();
-	expect(result).toBe("expected value");
+  const ctx = createExecutionContext();
+  const result = await ctx.exports.MyEntryPoint.myMethod();
+  expect(result).toBe("expected value");
 });
 ```
 
@@ -28,8 +28,8 @@ import { exports } from "cloudflare:workers";
 import { it, expect } from "vitest";
 
 it("can access imported exports", async () => {
-	const result = await exports.MyEntryPoint.myMethod();
-	expect(result).toBe("expected value");
+  const result = await exports.MyEntryPoint.myMethod();
+  expect(result).toBe("expected value");
 });
 ```
 
diff --git a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
index 7f91b0a340dd8fd..2a6b5bff0742249 100644
--- a/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
+++ b/src/content/changelog/workers/2025-12-19-tanstack-start-prerendering.mdx
@@ -6,8 +6,8 @@ products:
 date: 2025-12-19
 ---
 
-[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables
-and bindings, and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
+[TanStack Start](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables 
+and bindings,  and serve them as [static assets](/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:
 
 ```ts title="vite.config.ts"
 import { defineConfig } from "vite";
@@ -15,14 +15,14 @@ import { cloudflare } from "@cloudflare/vite-plugin";
 import { tanstackStart } from "@tanstack/react-start/plugin/vite";
 
 export default defineConfig({
-	plugins: [
-		cloudflare({ viteEnvironment: { name: "ssr" } }),
-		tanstackStart({
-			prerender: {
-				enabled: true,
-			},
-		}),
-	],
+  plugins: [
+    cloudflare({ viteEnvironment: { name: "ssr" } }),
+    tanstackStart({
+      prerender: {
+        enabled: true,
+      },
+    }),
+  ],
 });
 ```
 
diff --git a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
index f027c8fd04d6f0d..c28886f2273eb0a 100644
--- a/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
+++ b/src/content/changelog/workers/2026-02-15-workers-best-practices.mdx
@@ -26,7 +26,6 @@ Key guidance includes:
 ```
 
 </WranglerConfig>
-
 - **Generate binding types with `wrangler types`** — Never hand-write your `Env` interface. Let Wrangler generate it from your actual configuration to catch mismatches at compile time.
 - **Stream request and response bodies** — Avoid buffering large payloads in memory. Use `TransformStream` and `pipeTo` to stay within the 128 MB memory limit and improve time-to-first-byte.
 - **Use bindings, not REST APIs** — Bindings to KV, R2, D1, Queues, and other Cloudflare services are direct, in-process references with no network hop and no authentication overhead.
diff --git a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
index 7e14d709a1a753e..c153f96598e79c4 100644
--- a/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
+++ b/src/content/changelog/workers/2026-03-27-rfc9440-mtls-fields.mdx
@@ -8,36 +8,31 @@ Four new fields are now available on `request.cf.tlsClientAuth` in Workers for r
 
 ### New fields
 
-| Field                      | Type    | Description                                                                                                                                          |
-| -------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `certRFC9440`              | String  | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented.                                       |
-| `certRFC9440TooLarge`      | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`.                                                                    |
-| `certChainRFC9440`         | String  | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
-| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`.                                                             |
+| Field | Type | Description |
+| --- | --- | --- |
+| `certRFC9440` | String | The client leaf certificate in RFC 9440 format (`:base64-DER:`). Empty if no client certificate was presented. |
+| `certRFC9440TooLarge` | Boolean | `true` if the leaf certificate exceeded 10 KB and was omitted from `certRFC9440`. |
+| `certChainRFC9440` | String | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediates were sent or if the chain exceeded 16 KB. |
+| `certChainRFC9440TooLarge` | Boolean | `true` if the intermediate chain exceeded 16 KB and was omitted from `certChainRFC9440`. |
 
 ### Example: forwarding client certificate headers to your origin
 
 ```js
 export default {
-	async fetch(request) {
-		const tls = request.cf.tlsClientAuth;
-
-		// Only forward if cert was verified and chain is complete
-		if (
-			!tls ||
-			!tls.certVerified ||
-			tls.certRevoked ||
-			tls.certChainRFC9440TooLarge
-		) {
-			return new Response("Unauthorized", { status: 401 });
-		}
-
-		const headers = new Headers(request.headers);
-		headers.set("Client-Cert", tls.certRFC9440);
-		headers.set("Client-Cert-Chain", tls.certChainRFC9440);
-
-		return fetch(new Request(request, { headers }));
-	},
+  async fetch(request) {
+    const tls = request.cf.tlsClientAuth;
+
+    // Only forward if cert was verified and chain is complete
+    if (!tls || !tls.certVerified || tls.certRevoked || tls.certChainRFC9440TooLarge) {
+      return new Response("Unauthorized", { status: 401 });
+    }
+
+    const headers = new Headers(request.headers);
+    headers.set("Client-Cert", tls.certRFC9440);
+    headers.set("Client-Cert-Chain", tls.certChainRFC9440);
+
+    return fetch(new Request(request, { headers }));
+  },
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
index c311cbdd393dadd..1a9e3164168578c 100644
--- a/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
+++ b/src/content/changelog/workers/2026-04-01-l4-transport-telemetry-fields.mdx
@@ -10,33 +10,31 @@ Previously, this telemetry was only available via the `Server-Timing: cfL4` resp
 
 ### New properties
 
-| Property        | Type                | Description                                                                                                                                                                  |
-| --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `clientTcpRtt`  | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`.              |
-| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`.                    |
-| `edgeL4`        | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
+| Property | Type | Description |
+| --- | --- | --- |
+| `clientTcpRtt` | number \| undefined | The smoothed TCP round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for TCP connections (HTTP/1, HTTP/2). For example, `22`. |
+| `clientQuicRtt` | number \| undefined | The smoothed QUIC round-trip time (RTT) between Cloudflare and the client in milliseconds. Only present for QUIC connections (HTTP/3). For example, `42`. |
+| `edgeL4` | Object \| undefined | Layer 4 transport statistics. Contains `deliveryRate` (number) — the most recent data delivery rate estimate for the connection, in bytes per second. For example, `123456`. |
 
 ### Example: Log connection quality metrics
 
 ```js
 export default {
-	async fetch(request) {
-		const cf = request.cf;
+  async fetch(request) {
+    const cf = request.cf;
 
-		const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
-		const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
-		const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
+    const rtt = cf.clientTcpRtt ?? cf.clientQuicRtt ?? 0;
+    const deliveryRate = cf.edgeL4?.deliveryRate ?? 0;
+    const transport = cf.clientTcpRtt ? "TCP" : "QUIC";
 
-		console.log(
-			`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`,
-		);
+    console.log(`Transport: ${transport}, RTT: ${rtt}ms, Delivery rate: ${deliveryRate} B/s`);
 
-		const headers = new Headers(request.headers);
-		headers.set("X-Client-RTT", String(rtt));
-		headers.set("X-Delivery-Rate", String(deliveryRate));
+    const headers = new Headers(request.headers);
+    headers.set("X-Client-RTT", String(rtt));
+    headers.set("X-Delivery-Rate", String(deliveryRate));
 
-		return fetch(new Request(request, { headers }));
-	},
+    return fetch(new Request(request, { headers }));
+  },
 };
 ```
 
diff --git a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
index ffd136835ae4bc4..47a711a702b2fba 100644
--- a/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
+++ b/src/content/changelog/workers/2026-05-06-react-nextjs-vulnerabilities.mdx
@@ -9,7 +9,7 @@ date: 2026-05-07 12:00:00 UTC
 
 Multiple security vulnerabilities were disclosed by the React team and Vercel affecting React Server Components and Next.js. These include denial of service, middleware and proxy bypass, server-side request forgery, cross-site scripting, and cache poisoning issues across a range of severity levels.
 
-**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`).
+**We strongly recommend updating your application and its dependencies immediately.** Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`). 
 
 ## WAF protections
 
diff --git a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
index 7f215858ca21722..48963056126296d 100644
--- a/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
+++ b/src/content/changelog/workflows/2025-01-15-workflows-more-steps.mdx
@@ -10,8 +10,8 @@ date: 2025-01-15
 
 We've also added:
 
-- `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
-- Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
-- Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
+* `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
+* Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
+* Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
 
 We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks.
diff --git a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
index 4f047f473ce8ee4..dbd052de60e2fc7 100644
--- a/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
+++ b/src/content/changelog/workflows/2025-10-28-raising-limits.mdx
@@ -9,9 +9,9 @@ date: 2025-10-31
 
 We've raised the [Cloudflare Workflows](/workflows/) account-level limits for all accounts on the [Workers paid plan](/workers/platform/pricing/):
 
-- **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
-- **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
+* **Instance creation rate** increased from 100 workflow instances per 10 seconds to 100 instances per second
+* **Concurrency limit** increased from 4,500 to 10,000 workflow instances per account
 
-These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/).
+These increases mean you can create new instances up to 10x faster, and have more workflow instances concurrently executing. To learn more and get started with Workflows, refer to [the getting started guide](/workflows/get-started/guide/). 
 
 If your application requires a higher limit, fill out the [Limit Increase Request Form](/workers/platform/limits/) or contact your account team. Please refer to [Workflows pricing](/workflows/reference/pricing/) for more information.
diff --git a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
index e29d175b6b83ba6..90eef81c9251ce0 100644
--- a/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
+++ b/src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx
@@ -20,4 +20,4 @@ await instance.pause(); // pauses a running workflow instance
 await instance.resume(); // resumes a paused instance
 await instance.restart(); // restarts the instance from the beginning
 await instance.terminate(); // terminates the instance immediately
-```
+```
\ No newline at end of file
diff --git a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
index 93eb46096142460..4afac919aa7d970 100644
--- a/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
+++ b/src/content/changelog/workflows/2026-05-01-dynamic-workflows.mdx
@@ -7,15 +7,15 @@ products:
 date: 2026-05-01
 ---
 
-You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime.
+You can now use [`@cloudflare/dynamic-workflows`](https://github.com/cloudflare/dynamic-workflows) to run a [Workflow](/workflows/) inside a [Dynamic Worker](/dynamic-workers/), ensuring durable execution for code that is loaded at runtime. 
 
 The Worker Loader loads Dynamic Workers on demand, which previously made durability challenging. Even within a Dynamic Worker, a Workflow might sleep for hours or days between steps, and by the time it resumes, the original Dynamic Worker code would no longer be in memory.
 
-The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens.
+The library solves this by tagging each Workflow instance with metadata that identifies which Dynamic Worker to load — for example, a tenant ID — then reloading the matching Dynamic Worker through the Worker Loader whenever a Workflow awakens. 
 
 Because Dynamic Workers are created on-demand, you do not have to register each Workflow up front or manage them individually. Load the Workflow code in the Dynamic Worker when it is needed, and the Workflows engine handles persistence and retries behind the scenes. Your Workflow code itself is unaffected by the routing and behaves as normal.
 
-This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with:
+This unlocks patterns where the Workflow code itself is dynamic. For example, this is useful with: 
 
 - **SaaS platforms** where each tenant defines their own automation, such as onboarding sequences, approval chains, or billing retry logic.
 - **AI agent frameworks** where agents generate and execute multi-step plans at runtime, surviving restarts and waiting for human approval between tool calls.
diff --git a/src/content/compatibility-flags/allow-custom-ports.md b/src/content/compatibility-flags/allow-custom-ports.md
index 537127433070005..4a9cf4a9b5f6932 100644
--- a/src/content/compatibility-flags/allow-custom-ports.md
+++ b/src/content/compatibility-flags/allow-custom-ports.md
@@ -22,7 +22,6 @@ For example:
 ```js
 const response = await fetch("https://example.com:8000");
 ```
-
 With allow_custom_ports the above example would fetch `https://example.com:8000` rather than
 `https://example.com:443`.
 
diff --git a/src/content/compatibility-flags/enable-nodejs-http-modules.md b/src/content/compatibility-flags/enable-nodejs-http-modules.md
index 2bfccf48ee0d939..b28f784408c15f9 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-modules.md
@@ -21,10 +21,10 @@ This enables compatibility with Node.js libraries and existing code that
 use the standard node:http and node:https APIs for making HTTP requests.
 The available functionality includes:
 
-- `http.request()` and `https.request()` for making HTTP/HTTPS requests
-- `http.get()` and `https.get()` for making GET requests
-- Request and response objects with standard Node.js APIs
-- Support for standard HTTP methods, headers, and options
+* `http.request()` and `https.request()` for making HTTP/HTTPS requests
+* `http.get()` and `https.get()` for making GET requests
+* Request and response objects with standard Node.js APIs
+* Support for standard HTTP methods, headers, and options
 
 See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html)
 for more details about the Node.js APIs.
diff --git a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
index b4b92da33a8f73b..1e31b6a8b5508a4 100644
--- a/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
+++ b/src/content/compatibility-flags/enable-nodejs-http-server-modules.md
@@ -20,9 +20,9 @@ server modules.
 This enables compatibility with Node.js libraries and existing code that
 use the standard Node.js HTTP server APIs. The available functionality includes:
 
-- `http.createServer()` for creating HTTP servers
-- `http.Server` class for server instances
-- `http.ServerResponse` for handling server responses
+* `http.createServer()` for creating HTTP servers
+* `http.Server` class for server instances
+* `http.ServerResponse` for handling server responses
 
 This flag must be used in combination with the `enable_nodejs_http_modules` flag
 to enable full features of `node:http`.
@@ -30,4 +30,4 @@ to enable full features of `node:http`.
 This flag is automatically enabled for Workers using
 a compatibility date of 2025-09-01 or later when `nodejs_compat` is enabled.
 
-See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/http.html) for more details about the Node.js HTTP APIs.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/fetcher-no-get-put-delete.md b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
index dcf2a945b94649b..d38f2d504089ae8 100644
--- a/src/content/compatibility-flags/fetcher-no-get-put-delete.md
+++ b/src/content/compatibility-flags/fetcher-no-get-put-delete.md
@@ -18,3 +18,4 @@ Historically, API objects that had such a `fetch()` method also had methods `get
 These methods were a very early idea from many years ago, but were never actually documented, and therefore rarely (if ever) used. Enabling the `fetcher_no_get_put_delete`, or setting a compatibility date on or after `2024-03-26` disables these methods for your Worker.
 
 This change paves a future path for you to be able to define your own custom methods using these names. Without this change, you would be unable to define your own `get`, `put`, and `delete` methods, since they would conflict with these built-in helper methods.
+
diff --git a/src/content/compatibility-flags/js-weak-refs.md b/src/content/compatibility-flags/js-weak-refs.md
index 061ea4e608cd187..718f8818a545c01 100644
--- a/src/content/compatibility-flags/js-weak-refs.md
+++ b/src/content/compatibility-flags/js-weak-refs.md
@@ -12,7 +12,6 @@ disable_flag: "disable_weak_ref"
 ---
 
 Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry) and [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef) built-ins.
-
 - `FinalizationRegistry` allows you to register a cleanup callback that runs after an object has been garbage-collected.
 - `WeakRef` creates a weak reference to an object, allowing it to be garbage-collected if no other strong references exist.
 
@@ -22,4 +21,4 @@ Enables the use of [`FinalizationRegistry`](https://developer.mozilla.org/en-US/
 
 :::caution
 These APIs are fundamentally non-deterministic. The timing and execution of garbage collection are unpredictable, and you **should not rely on them for essential program logic**. Additionally, cleanup callbacks registered with `FinalizationRegistry` may **never be executed**, including but not limited to cases where garbage collection is not triggered, or your Worker gets evicted.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/compatibility-flags/new-url-parser-implementation.md b/src/content/compatibility-flags/new-url-parser-implementation.md
index 9ec8017e42ea670..55b21a5be67018c 100644
--- a/src/content/compatibility-flags/new-url-parser-implementation.md
+++ b/src/content/compatibility-flags/new-url-parser-implementation.md
@@ -13,17 +13,17 @@ disable_flag: "url_original"
 
 The original implementation of the [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) API in Workers was not fully compliant with the [WHATWG URL Standard](https://url.spec.whatwg.org/), differing in several ways, including:
 
-- The original implementation collapsed sequences of multiple slashes into a single slash:
+* The original implementation collapsed sequences of multiple slashes into a single slash:
 
   `new URL("https://example.com/a//b").toString() === "https://example.com/a/b"`
 
-- The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
+* The original implementation would throw `"TypeError: Invalid URL string."` if it encountered invalid percent-encoded escape sequences, like `https://example.com/a%%b`.
 
-- The original implementation would percent-encode or percent-decode certain content differently:
+* The original implementation would percent-encode or percent-decode certain content differently:
 
   `new URL("https://example.com/a%40b?c d%20e?f").toString() === "https://example.com/a@b?c+d+e%3Ff"`
 
-- The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
+* The original implementation lacked more recently implemented `URL` features, like [`URL.canParse()`](https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static).
 
 Set the compatibility date of your Worker to a date after `2022-10-31` or enable the `url_standard` compatibility flag to opt-in the fully spec compliant `URL` API implementation.
 
diff --git a/src/content/compatibility-flags/nodejs-compat.md b/src/content/compatibility-flags/nodejs-compat.md
index 6eb72d18070e7de..80bfc4fec1b0734 100644
--- a/src/content/compatibility-flags/nodejs-compat.md
+++ b/src/content/compatibility-flags/nodejs-compat.md
@@ -14,12 +14,12 @@ Enables [Node.js APIs](/workers/runtime-apis/nodejs/) in the Workers Runtime.
 
 Note that some Node.js APIs are only enabled if your Worker's compatibility date is set to on or after the following dates:
 
-| Node.js API                                                                                                                    | Enabled after |
-| ------------------------------------------------------------------------------------------------------------------------------ | ------------- |
-| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)                                 | `2025-09-01`  |
-| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules) | `2025-08-15`  |
-| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)                                 | `2025-04-01`  |
-| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)       | `2024-12-02`  |
+| Node.js API | Enabled after  |
+|---|---|
+| [`http.server`](/workers/configuration/compatibility-flags/#enable-nodejs-http-server-modules)  | `2025-09-01`  |
+| [`node:http`, `node:https`](/workers/configuration/compatibility-flags/#enable-availability-of-nodehttp-and-nodehttps-modules)  | `2025-08-15`  |
+| [`process.env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv)  | `2025-04-01`  |
+| [Disable Top-level Await in `require()`](/workers/configuration/compatibility-flags/#disable-top-level-await-in-require)  | `2024-12-02`  |
 
 When enabling `nodejs_compat`, we recommend using the latest version of [Wrangler CLI](/workers/wrangler/), and the latest compatiblity date, in order to maximize compatibility. Some older versions of Wrangler inject additional polyfills that are no longer neccessary, as they are provided by the Workers runtime, if your Worker is using a more recent compatibility date.
 
diff --git a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
index 458d6f154b4f789..82a917d18ac5162 100644
--- a/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
+++ b/src/content/compatibility-flags/queue-consumer-no-wait-waituntil.md
@@ -13,29 +13,26 @@ enable_flag: "queue_consumer_no_wait_for_wait_until"
 By default, [Queues](/queues/) Consumer Workers acknowledge messages only after promises passed to [`ctx.waitUntil()`](/workers/runtime-apis/context) have resolved. This behavior can cause queue consumers which utilize `ctx.waitUntil()` to process messages slowly. The default behavior is documented in the [Queues Consumer Configuration Guide](/queues/configuration/javascript-apis#consumer).
 
 This Consumer Worker is an example of a Worker which utilizes `ctx.waitUntil()`. Under the default behavior, this consumer Worker will only acknowledge a batch of messages after the sleep function has resolved.
-
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		// omitted
-	},
-
-	async queue(batch, env, ctx) {
-		console.log(
-			`received batch of ${batch.messages.length} messages to queue ${batch.queue}`,
-		);
-		for (let i = 0; i < batch.messages.length; ++i) {
-			console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
-		}
-		ctx.waitUntil(sleep(30 * 1000));
-	},
+  async fetch(request, env, ctx) {
+    // omitted
+  },
+
+  async queue(batch, env, ctx) {
+    console.log(`received batch of ${batch.messages.length} messages to queue ${batch.queue}`);
+    for (let i = 0; i < batch.messages.length; ++i) {
+      console.log(`message #${i}: ${JSON.stringify(batch.messages[i])}`);
+    }
+    ctx.waitUntil(sleep(30 * 1000));
+  }
 };
 
 function sleep(ms) {
-	return new Promise((resolve) => setTimeout(resolve, ms));
+  return new Promise(resolve => setTimeout(resolve, ms));
 }
 ```
 
 If the `queue_consumer_no_wait_for_wait_until` flag is enabled, Queues consumers will no longer wait for promises passed to `ctx.waitUntil()` to resolve before acknowledging messages. This can improve the performance of queue consumers which utilize `ctx.waitUntil()`. With the flag enabled, in the above example, the consumer Worker will acknowledge the batch without waiting for the sleep function to resolve.
 
-Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
+Using this flag will not affect the behavior of `ctx.waitUntil()`. `ctx.waitUntil()` will continue to extend the lifetime of your consumer Worker to continue to work even after the batch of messages has been acknowledged.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/queues-json-messages.md b/src/content/compatibility-flags/queues-json-messages.md
index 468e5bc0c452ce5..ed871f0ed83b10b 100644
--- a/src/content/compatibility-flags/queues-json-messages.md
+++ b/src/content/compatibility-flags/queues-json-messages.md
@@ -11,4 +11,4 @@ enable_flag: "queues_json_messages"
 disable_flag: "no_queues_json_messages"
 ---
 
-With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
+With the `queues_json_messages` flag set, Queue bindings will serialize values passed to `send()` or `sendBatch()` into JSON format by default (when no specific `contentType` is provided).
\ No newline at end of file
diff --git a/src/content/compatibility-flags/request-signal.md b/src/content/compatibility-flags/request-signal.md
index 75a494da250906c..e60e43e66403e2f 100644
--- a/src/content/compatibility-flags/request-signal.md
+++ b/src/content/compatibility-flags/request-signal.md
@@ -5,4 +5,4 @@ enable_flag: "enable_request_signal"
 disable_flag: "disable_request_signal"
 ---
 
-When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
+When you use the `enable_request_signal` compatibility flag, you can attach an event listener to [`Request`](/workers/runtime-apis/request/) objects, using the [`signal` property](https://developer.mozilla.org/en-US/docs/Web/API/Request/signal). This allows you to perform tasks when the request to your Worker is canceled by the client.
\ No newline at end of file
diff --git a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
index 3cdf43761777395..994a6a724e2f465 100644
--- a/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
+++ b/src/content/compatibility-flags/streams-byob-reader-detaches-buffer.md
@@ -20,12 +20,12 @@ User code should never try to reuse an `ArrayBuffer` that has been passed into a
 let reader = readable.getReader({ mode: "byob" });
 let arrayBufferView = new Uint8Array(4096);
 while (true) {
-	let result = await reader.read(arrayBufferView);
-	if (result.done) break;
-	// Optionally something with `result` here.
-	// Re-use the same memory for the next `read()` by creating
-	// a new Uint8Array backed by the result's ArrayBuffer.
-	arrayBufferView = new Uint8Array(result.value.buffer);
+  let result = await reader.read(arrayBufferView);
+  if (result.done) break;
+  // Optionally something with `result` here.
+  // Re-use the same memory for the next `read()` by creating
+  // a new Uint8Array backed by the result's ArrayBuffer.
+  arrayBufferView = new Uint8Array(result.value.buffer);
 }
 ```
 
diff --git a/src/content/compatibility-flags/strict-crypto.md b/src/content/compatibility-flags/strict-crypto.md
index 17274d7e485ef60..91a77815dd82fde 100644
--- a/src/content/compatibility-flags/strict-crypto.md
+++ b/src/content/compatibility-flags/strict-crypto.md
@@ -14,7 +14,6 @@ disable_flag: "no_strict_crypto_checks"
 ---
 
 Perform additional error checking in the Web Crypto API to conform with the specification and reject possibly unsafe key parameters:
-
 - For RSA key generation, key sizes are required to be multiples of 128 bits as boringssl may otherwise truncate the key.
 - The size of imported RSA keys must be at least 256 bits and at most 16384 bits, as with newly generated keys.
 - The public exponent for imported RSA keys is restricted to the commonly used values `[3, 17, 37, 65537]`.
diff --git a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
index 3b380e857412453..15ea7891dc4fcad 100644
--- a/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
+++ b/src/content/compatibility-flags/throw-on-unrecognized-import-assertion.md
@@ -19,3 +19,4 @@ attribute is encountered that is not recognized.
 
 When the `ignore_unrecognized_import_assertion` flag is set, Workers will
 ignore unrecognized import attributes.
+
diff --git a/src/content/compatibility-flags/to-string-tag.md b/src/content/compatibility-flags/to-string-tag.md
index 6fc298a87c182de..1de8e533db3f8bb 100644
--- a/src/content/compatibility-flags/to-string-tag.md
+++ b/src/content/compatibility-flags/to-string-tag.md
@@ -13,5 +13,5 @@ disable_flag: "do_not_set_tostring_tag"
 
 A change was made to set the Symbol.toStringTag on all Workers API objects
 in order to fix several spec compliance bugs. Unfortunately,
-this change was more breaking than anticipated. The `do_not_set_tostring_tag` compat
+this change was more breaking than anticipated. The `do_not_set_tostring_tag`  compat
 flag restores the original behavior with compatibility dates of 2024-09-26 or earlier.
diff --git a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
index b94637375b11410..ff6e300d56a8451 100644
--- a/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
+++ b/src/content/compatibility-flags/urlsearchparams-deletehasvalue.md
@@ -21,7 +21,7 @@ For an example of how this change could break existing code, consider code that
 ```js
 const usp = new URLSearchParams();
 // ...
-["abc", "xyz"].forEach(usp.delete.bind(usp));
+['abc', 'xyz'].forEach(usp.delete.bind(usp));
 ```
 
 The `forEach()` automatically passes multiple parameters to the function that is passed in. Prior to the addition of the new standard parameters, these extra arguments would have been ignored.
@@ -31,5 +31,5 @@ Now, however, the additional arguments have meaning and change the behavior of t
 ```js
 const usp = new URLSearchParams();
 // ...
-["abc", "xyz"].forEach((key) => usp.delete(key));
-```
+['abc', 'xyz'].forEach((key) => usp.delete(key));
+```
\ No newline at end of file
diff --git a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
index 5a0f4a50358133e..be603aaba1a62ba 100644
--- a/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
+++ b/src/content/compatibility-flags/web-socket-auto-reply-to-close.md
@@ -19,16 +19,12 @@ Previously, receiving a server-initiated Close frame left the WebSocket in `CLOS
 const [client, server] = Object.values(new WebSocketPair());
 server.accept();
 
-server.addEventListener(
-	"close",
-	(event) => {
-		// readyState is already CLOSED — no need to call server.close().
-		console.log(server.readyState); // WebSocket.CLOSED
-		console.log(event.code); // 1000
-		console.log(event.wasClean); // true
-	},
-	{ once: true },
-);
+server.addEventListener("close", (event) => {
+  // readyState is already CLOSED — no need to call server.close().
+  console.log(server.readyState); // WebSocket.CLOSED
+  console.log(event.code); // 1000
+  console.log(event.wasClean); // true
+}, { once: true });
 ```
 
 If you do still call `close()` inside the handler, the call is silently ignored. This means existing code that manually replies to Close frames will not break when you update your compatibility date.
@@ -41,18 +37,14 @@ const [client, server] = Object.values(new WebSocketPair());
 // Opt into half-open mode for proxying
 server.accept({ allowHalfOpen: true });
 
-server.addEventListener(
-	"close",
-	(event) => {
-		// With allowHalfOpen true, readyState is still CLOSING here,
-		// giving you time to coordinate the close on the other side.
-		console.log(server.readyState); // WebSocket.CLOSING
+server.addEventListener("close", (event) => {
+  // With allowHalfOpen true, readyState is still CLOSING here,
+  // giving you time to coordinate the close on the other side.
+  console.log(server.readyState); // WebSocket.CLOSING
 
-		// Manually close when ready.
-		server.close(1000, "done");
-	},
-	{ once: true },
-);
+  // Manually close when ready.
+  server.close(1000, "done");
+}, { once: true });
 ```
 
 Note that there is no corresponding option to the `WebSocket` constructor. WebSockets constructed with `new WebSocket` will always auto-reply to closes after this flag takes effect. WebSockets constructed this way are automatically "accepted", so there is no opportunity to pass the option to `accept()`. If you are creating a WebSocket with `new WebSocket`, but you need half-open behavior, you will need to switch to using `fetch()` instead.
@@ -63,10 +55,10 @@ let ws = new WebSocket("wss://example.com");
 
 // But you can do this instead:
 let resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { "Upgrade": "websocket" }
 });
 if (!resp.webSocket) {
-	throw new Error("WebSocket handshake not accepted");
+  throw new Error("WebSocket handshake not accepted");
 }
 let ws = resp.webSocket;
 ws.accept({ allowHalfOpen: true });
diff --git a/src/content/compatibility-flags/web-socket-compression.md b/src/content/compatibility-flags/web-socket-compression.md
index 9949b65656e428f..c73d329ee01a83e 100644
--- a/src/content/compatibility-flags/web-socket-compression.md
+++ b/src/content/compatibility-flags/web-socket-compression.md
@@ -15,4 +15,4 @@ The Workers runtime did not support WebSocket compression when the initial WebSo
 
 If the flag is present, the Workers runtime is capable of using WebSocket Compression on both inbound and outbound WebSocket connections.
 
-Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
+Like browsers, calling `new WebSocket(url)` in a Worker will automatically set the `Sec-WebSocket-Extensions: permessage-deflate` header. If you are using the non-standard `fetch()` API to obtain a WebSocket, you can include the `Sec-WebSocket-Extensions` header with value `permessage-deflate` and include any of the compression parameters defined in [RFC-7692](https://datatracker.ietf.org/doc/html/rfc7692#section-7).
\ No newline at end of file
diff --git a/src/content/compatibility-flags/websocket-standard-binary-type.md b/src/content/compatibility-flags/websocket-standard-binary-type.md
index 6e389dad36862eb..81e8b8883ea49f5 100644
--- a/src/content/compatibility-flags/websocket-standard-binary-type.md
+++ b/src/content/compatibility-flags/websocket-standard-binary-type.md
@@ -17,7 +17,7 @@ The `binaryType` property itself is available on every `WebSocket` regardless of
 
 ```js
 const resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -26,7 +26,7 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-	// event.data is an ArrayBuffer for binary frames.
+  // event.data is an ArrayBuffer for binary frames.
 });
 ```
 
diff --git a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
index e0b79d3a85a05ed..9d993472b94bcb7 100644
--- a/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
+++ b/src/content/compatibility-flags/workflows-preserve-non-retryable-error-message.md
@@ -19,13 +19,13 @@ Previously, throwing a `NonRetryableError` with a custom message would result in
 import { WorkflowEntrypoint, NonRetryableError } from "cloudflare:workers";
 
 export class MyWorkflow extends WorkflowEntrypoint {
-	async run(event, step) {
-		await step.do("my-step", async () => {
-			throw new NonRetryableError("custom error message");
-			// Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
-			// With this flag: error.message === "custom error message"
-		});
-	}
+  async run(event, step) {
+    await step.do("my-step", async () => {
+      throw new NonRetryableError("custom error message");
+      // Without this flag: error.message === "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"
+      // With this flag: error.message === "custom error message"
+    });
+  }
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
index 39b0c719c6a6edd..17806e9fea110e3 100644
--- a/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
+++ b/src/content/docs/agents/agentic-payments/mpp/charge-for-http-content.mdx
@@ -34,10 +34,10 @@ Define protected routes in `wrangler.jsonc`:
 			{
 				"pattern": "/premium/*",
 				"amount": "0.01",
-				"description": "Access to premium content for 1 hour",
-			},
-		],
-	},
+				"description": "Access to premium content for 1 hour"
+			}
+		]
+	}
 }
 ```
 
@@ -55,7 +55,7 @@ With [Bot Management](/bots/), the proxy can charge crawlers while keeping the s
 	"amount": "0.25",
 	"description": "Content access for 1 hour",
 	"bot_score_threshold": 30,
-	"except_detection_ids": [120623194, 117479730],
+	"except_detection_ids": [120623194, 117479730]
 }
 ```
 
diff --git a/src/content/docs/agents/agentic-payments/x402/index.mdx b/src/content/docs/agents/agentic-payments/x402/index.mdx
index bc12467db9b9995..4ae0cb18581f35d 100644
--- a/src/content/docs/agents/agentic-payments/x402/index.mdx
+++ b/src/content/docs/agents/agentic-payments/x402/index.mdx
@@ -45,8 +45,8 @@ The facilitator does not hold funds. It verifies and broadcasts the client's pre
 
 x402 uses payment **schemes** to define how a payment is constructed and settled on a given network.
 
-| Scheme                                                                                           | Networks                                 | Description                                                                                                                       |
-| ------------------------------------------------------------------------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Scheme                                                                                    | Networks                                 | Description                                                                                                                       |
+| ----------------------------------------------------------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | [`exact`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact.md) | EVM, Solana, Aptos, Stellar, Hedera, Sui | Transfers a fixed token amount — typically [ERC-20](https://eips.ethereum.org/EIPS/eip-20) USDC on EVM — to the merchant address. |
 | [`upto`](https://github.com/x402-foundation/x402/blob/main/specs/schemes/upto/scheme_upto.md)    | EVM                                      | Authorizes a maximum amount; the actual charge is determined at settlement time based on resource consumption.                    |
 
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
index a766be9a51e7892..25135f65b7f3f89 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-bots.mdx
@@ -38,4 +38,4 @@ You may have both of the following enabled:
 - A selection of AI crawlers to be charged through AI Crawl Control's pay per crawl
 - Bot configuration option to [Block AI Bots](/bots/get-started/bot-fight-mode/#block-ai-bots).
 
-Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
+Since pay per crawl happens after bot solutions, you need to first turn off **Block AI Bots** to ensure pay per crawl works as intended.
\ No newline at end of file
diff --git a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
index 57d1c103c3178a0..8e8f5e9661c32ef 100644
--- a/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
+++ b/src/content/docs/ai-crawl-control/configuration/ai-crawl-control-with-waf.mdx
@@ -9,14 +9,7 @@ products:
   - ai-crawl-control
 ---
 
-import {
-	GlossaryTooltip,
-	Example,
-	Steps,
-	Tabs,
-	TabItem,
-	DashButton,
-} from "~/components";
+import { GlossaryTooltip, Example, Steps, Tabs, TabItem, DashButton } from "~/components";
 
 AI Crawl Control works alongside other Cloudflare products, such as Cloudflare [Web Application Firewall (WAF)](/waf/). WAF checks incoming web and API requests, and filters undesired traffic based on rules. [WAF custom rules](/waf/custom-rules/) allow you to perform certain actions such as enforcing <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip>.
 
@@ -139,3 +132,4 @@ Any additions you make are preserved when you subsequently update crawler action
 :::caution
 Changes made directly to the WAF rule are not reflected back in the AI Crawl Control dashboard. Use the **Crawlers** tab as your primary interface, and reserve direct WAF edits for cases where the dashboard does not cover your requirements.
 :::
+
diff --git a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
index 8ed8a785d4df4d8..62af2e2d1d983dc 100644
--- a/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
+++ b/src/content/docs/ai-crawl-control/features/analyze-ai-traffic.mdx
@@ -65,12 +65,12 @@ Visualize crawler activity patterns over the selected time period. Use the view
 
 You can group the data by different dimensions:
 
-| Dimension    | Description                                                                             |
-| ------------ | --------------------------------------------------------------------------------------- |
-| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).     |
-| **Category** | Analyze crawlers by their purpose or type.                                              |
-| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site. |
-| **Host**     | Break down activity across multiple subdomains.                                         |
+| Dimension    | Description                                                                              |
+| ------------ | ---------------------------------------------------------------------------------------- |
+| **Crawler**  | Track activity from individual AI crawlers (such as GPTBot, ClaudeBot, Bytespider).      |
+| **Category** | Analyze crawlers by their purpose or type.                                               |
+| **Operator** | Discover which companies (such as OpenAI, Anthropic, ByteDance) are crawling your site.  |
+| **Host**     | Break down activity across multiple subdomains.                                          |
 
 :::note
 The Data transfer view shows `edgeResponseBytes`. Some crawlers may show higher data transfer per request than others, depending on the content they request.
@@ -93,11 +93,11 @@ The **Content Format** chart shows what content types AI systems request versus
 
 The chart includes three views:
 
-| View              | Description                                                                       |
-| ----------------- | --------------------------------------------------------------------------------- |
-| **Comparison**    | A grouped bar chart comparing requested content types versus served content types |
-| **Request Type**  | Breakdown of requests by Accept header                                            |
-| **Response Type** | Breakdown of responses by Content-Type header                                     |
+| View          | Description                                                                 |
+| ------------- | --------------------------------------------------------------------------- |
+| **Comparison** | A grouped bar chart comparing requested content types versus served content types |
+| **Request Type** | Breakdown of requests by Accept header                                      |
+| **Response Type** | Breakdown of responses by Content-Type header                              |
 
 ### Top referrers
 
diff --git a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
index 2892e1f8c9c5aa7..37400acba85f698 100644
--- a/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
+++ b/src/content/docs/ai-crawl-control/features/manage-ai-crawlers.mdx
@@ -8,15 +8,7 @@ products:
   - ai-crawl-control
 ---
 
-import {
-	Steps,
-	GlossaryTooltip,
-	Tabs,
-	TabItem,
-	Example,
-	Plan,
-	DashButton,
-} from "~/components";
+import { Steps, GlossaryTooltip, Tabs, TabItem, Example, Plan, DashButton } from "~/components";
 
 AI Crawl Control enables you to take specific action for each AI crawler.
 
@@ -33,13 +25,13 @@ To manage AI crawlers:
 
 The **Crawlers** tab displays a table of AI crawlers that are requesting access to your content, and how they interact with your pages. The table provides the following information.
 
-| Column                | Details                                                                                                                                                                                 |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                               |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                       |
-| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control. |
-| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                            |
-| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).             |
+| Column                | Details                                                                                                                                                                                    |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Crawler               | The name of the AI crawler and the operator that owns it.                                                                                                                                  |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                                          |
+| Requests              | The total number of allowed and unsuccessful requests, with trend chart. Unsuccessful requests may come from any rule or response error, not just the block action in AI Crawl Control.    |
+| Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                                               |
+| Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-crawl-control/features/manage-ai-crawlers/#take-action-for-each-ai-crawler).                |
 
 :::note[Quality of AI crawler detection]
 On the free plan, AI Crawl Control identifies AI crawlers based on their [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent). This enables AI Crawl Control to detect well-known, self-identifying AI crawlers.
diff --git a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
index 175f3072a93187a..8fbf42ce0120ba3 100644
--- a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
+++ b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/set-up-cloudflare-account.mdx
@@ -29,4 +29,4 @@ Pay per crawl is currently in closed beta.
 To find out how to join the beta program, reach out to us at [Pay per crawl signup](http://www.cloudflare.com/paypercrawl-signup/), or contact your account executive if you are an existing Enterprise customer.
 
 To learn more about pay per crawl, refer to Cloudflare blog: [Introducing pay per crawl: enabling content owners to charge AI crawlers for access](https://blog.cloudflare.com/introducing-pay-per-crawl/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
index 6673c210889beae..f406e702ce30ed6 100644
--- a/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
+++ b/src/content/docs/ai-crawl-control/features/track-robots-txt.mdx
@@ -42,12 +42,12 @@ The values in all tables and metrics will update according to your filters.
 
 The **Robots.txt availability** table shows the historical request frequency and health status of `robots.txt` files across your hostnames over the selected time frame.
 
-| Column          | Description                                                                                                                                                                                                                       |
-| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                 |
+| Column          | Description                                                                                                                                                                                                                    |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Path            | The specific hostname's `robots.txt` file being requested. Paths are listed from the most requested to the least.                                                                                                                      |
 | Requests        | The total number of requests made to this path. Requests are broken down into:<br/>- **Successful:** HTTP status codes below 400 (including **200 OK** and redirects).<br/>- **Unsuccessful:** HTTP status codes of 400 or above. |
-| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                          |
-| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                             |
+| Status          | The HTTP status code from pinging the `robots.txt` file.                                                                                                                                                                       |
+| Content Signals | An indicator showing whether the `robots.txt` file contains [Content Signals](https://contentsignals.org/), directives for usage in AI training, search, or AI input.                                                          |
 
 From this table, you can take the following actions:
 
diff --git a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
index d285d0714cd426d..1122f0a6d7d639e 100644
--- a/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
+++ b/src/content/docs/ai-crawl-control/reference/redirects-for-ai-training.mdx
@@ -156,12 +156,12 @@ The feature parses the `<link rel="canonical">` tag from the `<head>` section of
 ```html
 <!DOCTYPE html>
 <html>
-	<head>
-		<link rel="canonical" href="https://example.com/current-version" />
-	</head>
-	<body>
-		<!-- Page content -->
-	</body>
+<head>
+  <link rel="canonical" href="https://example.com/current-version">
+</head>
+<body>
+  <!-- Page content -->
+</body>
 </html>
 ```
 
@@ -169,10 +169,10 @@ Both absolute and relative URLs are supported:
 
 ```html
 <!-- Absolute URL -->
-<link rel="canonical" href="https://example.com/page" />
+<link rel="canonical" href="https://example.com/page">
 
 <!-- Relative URL (resolved against request URL) -->
-<link rel="canonical" href="/current-page" />
+<link rel="canonical" href="/current-page">
 ```
 
 ### Interaction with other redirect features
diff --git a/src/content/docs/ai-gateway/configuration/authentication.mdx b/src/content/docs/ai-gateway/configuration/authentication.mdx
index e848745b780263d..780ade1a3e222cc 100644
--- a/src/content/docs/ai-gateway/configuration/authentication.mdx
+++ b/src/content/docs/ai-gateway/configuration/authentication.mdx
@@ -66,7 +66,7 @@ const openai = createOpenAI({
 
 :::note
 When an AI Gateway is accessed from a Cloudflare Worker using a **binding**, the `cf-aig-authorization` header does not need to be manually included.  
-Requests made through bindings are **pre-authenticated** within the associated Cloudflare account.
+Requests made through bindings are **pre-authenticated** within the associated Cloudflare account. 
 :::
 
 The following table outlines gateway behavior based on the authentication settings and header status:
diff --git a/src/content/docs/ai-gateway/configuration/custom-providers.mdx b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
index 0bc6f1543a3b8fe..6da29fa5366081a 100644
--- a/src/content/docs/ai-gateway/configuration/custom-providers.mdx
+++ b/src/content/docs/ai-gateway/configuration/custom-providers.mdx
@@ -373,12 +373,12 @@ Everything after `custom-{slug}/` in your request URL is appended directly to th
 
 ### Choosing between Unified API and provider-specific endpoint
 
-|                                 | Unified API (`/compat`)                           | Provider-specific endpoint                |
-| ------------------------------- | ------------------------------------------------- | ----------------------------------------- |
-| **Best for**                    | Providers with OpenAI-compatible APIs             | Providers with any API structure          |
-| **Request format**              | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
-| **Path control**                | Fixed to `/compat/chat/completions`               | Full control over the upstream path       |
-| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}`       | URL path: `/custom-{slug}/{path}`         |
+| | Unified API (`/compat`) | Provider-specific endpoint |
+|---|---|---|
+| **Best for** | Providers with OpenAI-compatible APIs | Providers with any API structure |
+| **Request format** | Must follow the OpenAI `/chat/completions` schema | Uses the provider's native request format |
+| **Path control** | Fixed to `/compat/chat/completions` | Full control over the upstream path |
+| **How to specify the provider** | `model` field: `custom-{slug}/{model-name}` | URL path: `/custom-{slug}/{path}` |
 
 Use the **Unified API** when your custom provider accepts the OpenAI-compatible `/chat/completions` request format. This is the simplest option and works well with OpenAI SDKs.
 
@@ -425,12 +425,10 @@ The following examples show how to configure `base_url` and construct request UR
 Many providers follow the OpenAI convention of hosting their API at `{domain}/v1/chat/completions`.
 
 **Configuration:**
-
 - `slug`: `my-openai-compat`
 - `base_url`: `https://api.example-provider.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-openai-compat/v1/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -450,7 +448,6 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-my-op
 | Upstream URL | `https://api.example-provider.com/v1/chat/completions` |
 
 Since this provider is OpenAI-compatible, you could also use the Unified API:
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -466,12 +463,10 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/
 Some providers use API paths that don't follow the `/v1/` convention. For example, a provider whose chat endpoint is at `https://api.custom-ai.com/api/coding/paas/v4/chat/completions`.
 
 **Configuration:**
-
 - `slug`: `custom-ai`
 - `base_url`: `https://api.custom-ai.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-custom-ai/api/coding/paas/v4/chat/completions \
   -H "Authorization: Bearer $PROVIDER_API_KEY" \
@@ -499,12 +494,10 @@ For providers with non-standard paths, you must use the provider-specific endpoi
 If you host your own model behind a reverse proxy or on a platform that adds a path prefix, include only the fixed prefix portion in `base_url` if all your endpoints share it. Otherwise, keep `base_url` as just the domain.
 
 **Configuration (domain-only `base_url`):**
-
 - `slug`: `internal-llm`
 - `base_url`: `https://ml.internal.example.com`
 
 **Provider-specific endpoint:**
-
 ```bash
 curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-internal-llm/serving/models/my-model:predict \
   -H "Authorization: Bearer $INTERNAL_API_KEY" \
@@ -527,12 +520,10 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/custom-inter
 When using the OpenAI SDK to connect to a custom provider through AI Gateway, set the SDK's `base_url` to the gateway's provider-specific endpoint path (up to and including the API version prefix that your provider expects).
 
 **Configuration:**
-
 - `slug`: `alt-provider`
 - `base_url`: `https://api.alt-provider.com`
 
 **Python (OpenAI SDK):**
-
 ```python title="Using OpenAI SDK with a custom provider"
 from openai import OpenAI
 
@@ -568,14 +559,14 @@ response = client.chat.completions.create(
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1003,
-			"message": "A custom provider with this slug already exists",
-			"path": ["body", "slug"]
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1003,
+      "message": "A custom provider with this slug already exists",
+      "path": ["body", "slug"]
+    }
+  ]
 }
 ```
 
@@ -585,13 +576,13 @@ Each custom provider slug must be unique within your account. Choose a different
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1004,
-			"message": "Custom Provider not found"
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1004,
+      "message": "Custom Provider not found"
+    }
+  ]
 }
 ```
 
@@ -601,14 +592,14 @@ The specified provider ID does not exist or you don't have access to it. Verify
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 1002,
-			"message": "base_url must be a valid HTTPS URL starting with https://",
-			"path": ["body", "base_url"]
-		}
-	]
+  "success": false,
+  "errors": [
+    {
+      "code": 1002,
+      "message": "base_url must be a valid HTTPS URL starting with https://",
+      "path": ["body", "base_url"]
+    }
+  ]
 }
 ```
 
@@ -645,4 +636,4 @@ If you receive a 404 from the upstream provider, the most common cause is an inc
 - [BYOK (Store Keys)](/ai-gateway/configuration/bring-your-own-keys/)
 - [Dynamic routing](/ai-gateway/features/dynamic-routing/)
 - [Caching](/ai-gateway/features/caching/)
-- [Rate limiting](/ai-gateway/features/rate-limiting/)
+- [Rate limiting](/ai-gateway/features/rate-limiting/)
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
index 591a2b78db5305d..1583cae3d3cb063 100644
--- a/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
+++ b/src/content/docs/ai-gateway/evaluations/add-human-feedback.mdx
@@ -8,7 +8,6 @@ sidebar:
 products:
   - ai-gateway
 ---
-
 import { DashButton } from "~/components";
 
 Human feedback is a valuable metric to assess the performance of your AI models. By incorporating human feedback, you can gain deeper insights into how the model's responses are perceived and how well it performs from a user-centric perspective. This feedback can then be used in evaluations to calculate performance metrics, driving optimization and ultimately enhancing the reliability, accuracy, and efficiency of your AI application.
diff --git a/src/content/docs/ai-gateway/features/dlp/index.mdx b/src/content/docs/ai-gateway/features/dlp/index.mdx
index 1a2da0f59706eda..fed23035a215241 100644
--- a/src/content/docs/ai-gateway/features/dlp/index.mdx
+++ b/src/content/docs/ai-gateway/features/dlp/index.mdx
@@ -59,11 +59,11 @@ Because of this buffering:
 
 DLP scanning runs after a cache miss, when AI Gateway forwards the request to the provider and receives a response. The following table describes how each DLP outcome affects caching:
 
-| DLP outcome        | Response cached | Behavior                                                                                                                                                                  |
-| ------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pass (no findings) | Yes             | The response is cached normally according to your gateway cache settings.                                                                                                 |
-| Flag               | Yes             | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
-| Block              | No              | The provider response is discarded and replaced with a DLP error response (status `400`).                                                                                 |
+| DLP outcome | Response cached | Behavior |
+| --- | --- | --- |
+| Pass (no findings) | Yes | The response is cached normally according to your gateway cache settings. |
+| Flag | Yes | The response is cached normally. DLP findings are attached to the `cf-aig-dlp` response header and recorded in logs, but the original response is returned to the client. |
+| Block | No | The provider response is discarded and replaced with a DLP error response (status `400`). |
 
 **Cache hits skip DLP scanning.** When a subsequent identical request matches a cached response, AI Gateway serves it directly from cache without re-running DLP. This is safe because only responses that already passed DLP (or were flagged, not blocked) are cached. However, if you update your DLP policies after a response has been cached, the cached response is not re-evaluated. It continues to be served until the cache TTL expires.
 
diff --git a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
index fc4d9ee983694c4..72c2fa37068d4d0 100644
--- a/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
+++ b/src/content/docs/ai-gateway/features/dynamic-routing/usage.mdx
@@ -92,7 +92,8 @@ export default {
 
 ## Response Metadata
 
-The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers
+The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers 
 
 - `cf-aig-model` - The model used
 - `cf-aig-provider` - The slug of provider used
+
diff --git a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
index 04c450d92911bd4..d03c6eb9622ec7d 100644
--- a/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
+++ b/src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx
@@ -124,7 +124,7 @@ You will be prompted to log in after you run `wrangler dev`. When you run `npx w
 
 ```json
 {
-	"response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
+  "response": "A fascinating question!\n\nThe phrase \"Hello, World!\" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming.\n\nIn the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \"Hello, World!\" because it was a simple and recognizable message that would illustrate how a program could print text to the screen.\n\nThe exact code was written in the 5th edition of Kernighan and Ritchie's book \"The C Programming Language,\" published in 1988. The code, literally known as \"Hello, World!\" is as follows:\n\n    main()\n    {\n      printf(\"Hello, World!\");\n    }\n\nThis code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console.\n\nThe phrase \"Hello, World!\" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education.\n\nSincerely, I'm glad I could help clarify the origin of this iconic phrase for you!"
 }
 ```
 
diff --git a/src/content/docs/ai-gateway/mcp-server.mdx b/src/content/docs/ai-gateway/mcp-server.mdx
index 5d7ff3bfddb2e49..9cb472e8825884a 100644
--- a/src/content/docs/ai-gateway/mcp-server.mdx
+++ b/src/content/docs/ai-gateway/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - ai-gateway
----
+---
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/observability/logging/index.mdx b/src/content/docs/ai-gateway/observability/logging/index.mdx
index 1ee3a267485ed02..cfcd1cab3d1200c 100644
--- a/src/content/docs/ai-gateway/observability/logging/index.mdx
+++ b/src/content/docs/ai-gateway/observability/logging/index.mdx
@@ -55,9 +55,9 @@ The `cf-aig-collect-log-payload` header allows you to control whether the raw re
 
 This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completion data.
 
-| Header value | Behavior                                                               |
-| ------------ | ---------------------------------------------------------------------- |
-| `true`       | Request and response payloads are stored.                              |
+| Header value | Behavior |
+| ------------ | -------- |
+| `true`       | Request and response payloads are stored. |
 | `false`      | Payload storage is skipped. Metadata-only log entries are still saved. |
 
 In the example below, we use `cf-aig-collect-log-payload` to skip storing the request and response bodies while keeping the metadata log.
diff --git a/src/content/docs/ai-gateway/reference/audit-logs.mdx b/src/content/docs/ai-gateway/reference/audit-logs.mdx
index 250b377c6c517ee..0cfe7251d9d7c8a 100644
--- a/src/content/docs/ai-gateway/reference/audit-logs.mdx
+++ b/src/content/docs/ai-gateway/reference/audit-logs.mdx
@@ -5,7 +5,6 @@ pcx_content_type: concept
 products:
   - ai-gateway
 ---
-
 import { DashButton } from "~/components";
 
 [Audit logs](/fundamentals/account/account-security/review-audit-logs/) provide a comprehensive summary of changes made within your Cloudflare account, including those made to gateways in AI Gateway. This functionality is available on all plan types, free of charge, and is enabled by default.
@@ -14,7 +13,7 @@ import { DashButton } from "~/components";
 
 To view audit logs for AI Gateway, in the Cloudflare dashboard, go to the **Audit logs** page.
 
-<DashButton url="/?to=/:account/audit-log" />
+  <DashButton url="/?to=/:account/audit-log" />
 
 For more information on how to access and use audit logs, refer to [review audit logs documentation](/fundamentals/account/account-security/review-audit-logs/).
 
@@ -34,39 +33,39 @@ Below is an example of an audit log entry showing the creation of a new gateway:
 
 ```json
 {
-	"action": {
-		"info": "gateway created",
-		"result": true,
-		"type": "create"
-	},
-	"actor": {
-		"email": "<ACTOR_EMAIL>",
-		"id": "3f7b730e625b975bc1231234cfbec091",
-		"ip": "fe32:43ed:12b5:526::1d2:13",
-		"type": "user"
-	},
-	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-	"interface": "UI",
-	"metadata": {},
-	"newValue": "",
-	"newValueJson": {
-		"cache_invalidate_on_update": false,
-		"cache_ttl": 0,
-		"collect_logs": true,
-		"id": "test",
-		"rate_limiting_interval": 0,
-		"rate_limiting_limit": 0,
-		"rate_limiting_technique": "fixed"
-	},
-	"oldValue": "",
-	"oldValueJson": {},
-	"owner": {
-		"id": "1234d848c0b9e484dfc37ec392b5fa8a"
-	},
-	"resource": {
-		"id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
-		"type": "ai_gateway.gateway"
-	},
-	"when": "2024-07-17T14:06:11.425Z"
+ "action": {
+     "info": "gateway created",
+     "result": true,
+     "type": "create"
+ },
+ "actor": {
+     "email": "<ACTOR_EMAIL>",
+     "id": "3f7b730e625b975bc1231234cfbec091",
+     "ip": "fe32:43ed:12b5:526::1d2:13",
+     "type": "user"
+ },
+ "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+ "interface": "UI",
+ "metadata": {},
+ "newValue": "",
+ "newValueJson": {
+     "cache_invalidate_on_update": false,
+     "cache_ttl": 0,
+     "collect_logs": true,
+     "id": "test",
+     "rate_limiting_interval": 0,
+     "rate_limiting_limit": 0,
+     "rate_limiting_technique": "fixed"
+ },
+ "oldValue": "",
+ "oldValueJson": {},
+ "owner": {
+     "id": "1234d848c0b9e484dfc37ec392b5fa8a"
+ },
+ "resource": {
+     "id": "89303df8-1234-4cfa-a0f8-0bd848e831ca",
+     "type": "ai_gateway.gateway"
+ },
+ "when": "2024-07-17T14:06:11.425Z"
 }
 ```
diff --git a/src/content/docs/ai-gateway/reference/limits.mdx b/src/content/docs/ai-gateway/reference/limits.mdx
index 8b130857ad0477c..5c0459bc75ae5e7 100644
--- a/src/content/docs/ai-gateway/reference/limits.mdx
+++ b/src/content/docs/ai-gateway/reference/limits.mdx
@@ -33,14 +33,11 @@ The following limits apply to gateway configurations, logs, and related features
 <sup>1</sup> When you reach the log storage limit for a gateway, you can
 configure your gateway to either automatically delete the oldest logs to make
 room for new ones, or stop saving new logs. You can also use
-[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to external
-storage. Refer to [Automatic log
-deletion](/ai-gateway/observability/logging/#automatic-log-deletion) for more
-details.
-
-<sup>2</sup> On the free plan, the log storage limit applies to total logs
-across all gateways in your account. Same auto-delete or stop-saving behavior as
-<sup>1</sup>.
+[Logpush](/ai-gateway/observability/logging/logpush/) to export logs to
+external storage. Refer to [Automatic log deletion](/ai-gateway/observability/logging/#automatic-log-deletion)
+for more details.
+
+<sup>2</sup> On the free plan, the log storage limit applies to total logs across all gateways in your account. Same auto-delete or stop-saving behavior as <sup>1</sup>.
 
 <sup>3</sup> Logs larger than 10 MB will not be stored.
 
diff --git a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
index d55b0392378c965..9f0277bdd3a1ac7 100644
--- a/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
+++ b/src/content/docs/ai-gateway/tutorials/pruna-p-video.mdx
@@ -106,12 +106,12 @@ The response includes a prediction `id`:
 
 ```json
 {
-	"id": "xyz789...",
-	"status": "starting",
-	"urls": {
-		"get": "https://api.replicate.com/v1/predictions/xyz789...",
-		"cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
-	}
+  "id": "xyz789...",
+  "status": "starting",
+  "urls": {
+    "get": "https://api.replicate.com/v1/predictions/xyz789...",
+    "cancel": "https://api.replicate.com/v1/predictions/xyz789.../cancel"
+  }
 }
 ```
 
@@ -127,7 +127,7 @@ Keep polling until `status` is `succeeded` (or `failed`). When complete, the `ou
 
 ## Next steps
 
-From here you can:
+From here you can: 
 
 - Use [logging](/ai-gateway/observability/logging/) to monitor requests and debug issues.
 - Set up [rate limiting](/ai-gateway/features/rate-limiting/) to control usage.
diff --git a/src/content/docs/ai-gateway/usage/chat-completion.mdx b/src/content/docs/ai-gateway/usage/chat-completion.mdx
index c1dbd0f663fb740..1280237dc0187bb 100644
--- a/src/content/docs/ai-gateway/usage/chat-completion.mdx
+++ b/src/content/docs/ai-gateway/usage/chat-completion.mdx
@@ -11,7 +11,11 @@ products:
   - ai-gateway
 ---
 
-import { Details, Tabs, TabItem } from "~/components";
+import {
+	Details,
+  Tabs,
+  TabItem
+} from "~/components";
 import CodeSnippets from "~/components/ai-gateway/code-examples.astro";
 
 :::caution[Deprecated]
diff --git a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
index aa1ad566a1a3a37..7c7d8622dd1be29 100644
--- a/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/anthropic.mdx
@@ -11,7 +11,6 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 [Anthropic](https://www.anthropic.com/) helps build reliable, interpretable, and steerable AI systems.
 
 ## Endpoint
-
 **Base URL**
 
 ```txt
@@ -125,18 +124,17 @@ import Anthropic from "@anthropic-ai/sdk";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic`;
 
 const anthropic = new Anthropic({
-baseURL,
-defaultHeaders: {
-Authorization: `Bearer {cf_api_token}`,
-},
+	baseURL,
+	defaultHeaders: {
+		Authorization: `Bearer {cf_api_token}`,
+	},
 });
 
 const message = await anthropic.messages.create({
-model: "claude-sonnet-4-5",
-messages: [{ role: "user", content: "What is Cloudflare?" }],
-max_tokens: 1024,
+	model: "claude-sonnet-4-5",
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
+	max_tokens: 1024,
 });
-
 ```
 </Details>
 
@@ -153,4 +151,3 @@ max_tokens: 1024,
     }}
 
 />
-```
diff --git a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
index 33bc4a3a7827002..bbda8d88dad78df 100644
--- a/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/azureopenai.mdx
@@ -52,14 +52,14 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{
 import { AzureOpenAI } from "openai";
 
 const azure_openai = new AzureOpenAI({
-	apiKey: "{azure_api_key}",
-	baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
-	apiVersion: "2023-05-15",
-	defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
+  apiKey: "{azure_api_key}",
+  baseURL: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/`,
+  apiVersion: "2023-05-15",
+  defaultHeaders: { "cf-aig-authorization": "{cf-api-token}" }, // if authenticated
 });
 
 const result = await azure_openai.chat.completions.create({
-	model: "{deployment_name}",
-	messages: [{ role: "user", content: "Hello" }],
+  model: '{deployment_name}',
+  messages: [{ role: "user", content: "Hello" }],
 });
 ```
diff --git a/src/content/docs/ai-gateway/usage/providers/baseten.mdx b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
index 54c26a43777ba18..24877ce82f34716 100644
--- a/src/content/docs/ai-gateway/usage/providers/baseten.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/baseten.mdx
@@ -57,31 +57,31 @@ const gatewayId = "{gateway_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const openai = new OpenAI({
-	apiKey,
-	baseURL,
+  apiKey,
+  baseURL,
 });
 
 const model = "openai/gpt-oss-120b";
 const messages = [{ role: "user", content: "What is Cloudflare?" }];
 
 const chatCompletion = await openai.chat.completions.create({
-	model,
-	messages,
+  model,
+  messages,
 });
 
 console.log(chatCompletion);
 ```
 
 <Render
-	file="chat-completions-providers"
-	product="ai-gateway"
-	params={{
-		name: "Baseten",
-		jsonexample: `
+  file="chat-completions-providers"
+  product="ai-gateway"
+  params={{
+    name: "Baseten",
+    jsonexample: `
 {
   "model": "baseten/{model}"
-}`,
-	}}
+}`
+  }}
 />
 
 ## Model-specific endpoints
@@ -110,15 +110,15 @@ const modelId = "{model_id}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/baseten`;
 
 const response = await fetch(`${baseURL}/model/${modelId}`, {
-	method: "POST",
-	headers: {
-		Authorization: `Bearer ${basetenApiToken}`,
-		"Content-Type": "application/json",
-	},
-	body: JSON.stringify({
-		prompt: "What is Cloudflare?",
-		max_tokens: 100,
-	}),
+  method: "POST",
+  headers: {
+    "Authorization": `Bearer ${basetenApiToken}`,
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify({
+    prompt: "What is Cloudflare?",
+    max_tokens: 100,
+  }),
 });
 
 const result = await response.json();
diff --git a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
index bb8f30200a44e93..1f2df28b2813847 100644
--- a/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/bedrock.mdx
@@ -43,10 +43,10 @@ AI Gateway handles this complexity for you. When you store your AWS credentials
 
 ### Authentication methods comparison
 
-| Method                  | `cf-aig-authorization` header | `Authorization` header | Signing                              |
-| ----------------------- | ----------------------------- | ---------------------- | ------------------------------------ |
-| **BYOK (Recommended)**  | `Bearer {CF_AIG_TOKEN}`       | Not needed             | Gateway signs automatically          |
-| **Client-side signing** | `Bearer {CF_AIG_TOKEN}`       | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
+| Method | `cf-aig-authorization` header | `Authorization` header | Signing |
+| --- | --- | --- | --- |
+| **BYOK (Recommended)** | `Bearer {CF_AIG_TOKEN}` | Not needed | Gateway signs automatically |
+| **Client-side signing** | `Bearer {CF_AIG_TOKEN}` | Pre-signed AWS headers | You sign with `aws4fetch` or AWS SDK |
 
 :::caution[Do not confuse the headers]
 `cf-aig-authorization` authenticates your request to AI Gateway. When using BYOK, you do not need to include any AWS authorization headers because AI Gateway signs the request for you.
@@ -227,3 +227,5 @@ const response = await client.chat.completions.create({
 
 console.log(response.choices[0].message.content);
 ```
+
+
diff --git a/src/content/docs/ai-gateway/usage/providers/fal.mdx b/src/content/docs/ai-gateway/usage/providers/fal.mdx
index 057d6dda7144ddc..3e67996cbae3c2d 100644
--- a/src/content/docs/ai-gateway/usage/providers/fal.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/fal.mdx
@@ -78,23 +78,21 @@ The `x-fal-target-url` format is compliant with the Fal SDKs, so AI Gateway can
 import { fal } from "@fal-ai/client";
 
 fal.config({
-	credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
-	proxyUrl:
-		"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal",
+  credentials: "{fal_ai_token}", // OR pass a cloudflare api token if using BYOK on AI Gateway
+  proxyUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal"
 });
 
 const result = await fal.subscribe("fal-ai/bytedance/seedream/v4/edit", {
-	input: {
-		prompt:
-			"Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
-		image_urls: [
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
-			"https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png",
-		],
-	},
+  "input": {
+    "prompt": "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.",
+    "image_urls": [
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png",
+      "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png"
+    ]
+  }
 });
 
 console.log(result.data.images[0]);
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
index 29e542bf31fb4d9..7d986484bd9371b 100644
--- a/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/google-ai-studio.mdx
@@ -17,7 +17,6 @@ import { Render, Details, Tabs, TabItem } from "~/components";
 ```txt
 https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio
 ```
-
 Then you can append the endpoint you want to hit, for example: `v1/models/{model}:{generative_ai_rest_resource}`
 
 So your final URL will come together as: `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio/v1/models/{model}:{generative_ai_rest_resource}`.
@@ -137,19 +136,18 @@ console.log(response.text);
 import { GoogleGenAI } from "@google/genai";
 
 const ai = new GoogleGenAI({
-apiKey: "{cf_aig_token}",
-httpOptions: {
-baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
-}
+  apiKey: "{cf_aig_token}",
+  httpOptions: {
+	  baseUrl: `https://gateway.ai.cloudflare.com/v1/${account_id}/${gateway_name}/google-ai-studio`,
+  }
 });
 
 const response = await ai.models.generateContent({
-model: "gemini-2.5-flash",
-contents: "What is Cloudflare?",
+  model: "gemini-2.5-flash",
+  contents: "What is Cloudflare?",
 });
 
 console.log(response.text);
-
 ```
 </Details>
 
@@ -166,4 +164,3 @@ console.log(response.text);
     }}
 
 />
-```
diff --git a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
index e9213598bdda79c..bc019d9a71628b5 100644
--- a/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
+++ b/src/content/docs/ai-gateway/usage/providers/ideogram.mdx
@@ -48,17 +48,17 @@ const ideogramApiKey = "{ideogram_api_key}";
 const baseURL = `https://gateway.ai.cloudflare.com/v1/${accountId}/${gatewayId}/ideogram`;
 
 const response = await fetch(`${baseURL}/v1/ideogram-v3/generate`, {
-	method: "POST",
-	headers: {
-		"Api-Key": ideogramApiKey,
-		"Content-Type": "application/json",
-	},
-	body: JSON.stringify({
-		prompt: "A serene landscape with mountains and a lake at sunset",
-		model: "V_3",
-	}),
+  method: "POST",
+  headers: {
+    "Api-Key": ideogramApiKey,
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify({
+    prompt: "A serene landscape with mountains and a lake at sunset",
+    model: "V_3",
+  }),
 });
 
 const result = await response.json();
 console.log(result);
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/ai-gateway/usage/rest-api.mdx b/src/content/docs/ai-gateway/usage/rest-api.mdx
index e2275bfa7e32b91..7dd750f9b04aca9 100644
--- a/src/content/docs/ai-gateway/usage/rest-api.mdx
+++ b/src/content/docs/ai-gateway/usage/rest-api.mdx
@@ -18,12 +18,12 @@ No provider SDKs or API keys are needed. Authentication and billing are handled
 
 Four endpoints are available, each suited to different use cases:
 
-| Endpoint                       | Format                         | Use case                                         |
-| ------------------------------ | ------------------------------ | ------------------------------------------------ |
-| `POST /ai/run`                 | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
-| `POST /ai/v1/chat/completions` | OpenAI chat completions        | LLMs — OpenAI SDK compatible                     |
-| `POST /ai/v1/responses`        | OpenAI Responses API           | Agentic workflows — OpenAI SDK compatible        |
-| `POST /ai/v1/messages`         | Anthropic Messages API         | LLMs — Anthropic SDK compatible                  |
+| Endpoint | Format | Use case |
+| -------- | ------ | -------- |
+| `POST /ai/run` | Envelope with `model`, `input` | All models and modalities (LLM, image, TTS, ASR) |
+| `POST /ai/v1/chat/completions` | OpenAI chat completions | LLMs — OpenAI SDK compatible |
+| `POST /ai/v1/responses` | OpenAI Responses API | Agentic workflows — OpenAI SDK compatible |
+| `POST /ai/v1/messages` | Anthropic Messages API | LLMs — Anthropic SDK compatible |
 
 ## Authentication
 
@@ -140,13 +140,13 @@ Point the OpenAI SDK `baseURL` at the Cloudflare API:
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.chat.completions.create({
-	model: "openai/gpt-4.1",
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
+  model: "openai/gpt-4.1",
+  messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -158,13 +158,13 @@ Uses the OpenAI Responses API format for agentic workflows. Compatible with the
 import OpenAI from "openai";
 
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const response = await openai.responses.create({
-	model: "openai/gpt-4.1",
-	input: "What is Cloudflare?",
+  model: "openai/gpt-4.1",
+  input: "What is Cloudflare?",
 });
 ```
 
@@ -194,14 +194,14 @@ Point the Anthropic SDK `baseURL` at the Cloudflare API:
 import Anthropic from "@anthropic-ai/sdk";
 
 const anthropic = new Anthropic({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
 });
 
 const message = await anthropic.messages.create({
-	model: "anthropic/claude-sonnet-4-5",
-	max_tokens: 512,
-	messages: [{ role: "user", content: "What is Cloudflare?" }],
+  model: "anthropic/claude-sonnet-4-5",
+  max_tokens: 512,
+  messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 ```
 
@@ -229,11 +229,11 @@ With the OpenAI SDK, set the header via `defaultHeaders`:
 
 ```javascript
 const openai = new OpenAI({
-	apiKey: CLOUDFLARE_API_TOKEN,
-	baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
-	defaultHeaders: {
-		"cf-aig-gateway-id": "my-gateway",
-	},
+  apiKey: CLOUDFLARE_API_TOKEN,
+  baseURL: `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/ai/v1`,
+  defaultHeaders: {
+    "cf-aig-gateway-id": "my-gateway",
+  },
 });
 ```
 
@@ -243,17 +243,17 @@ All AI Gateway features configured on that gateway — caching, rate limiting, g
 
 Use `cf-aig-*` headers to control AI Gateway behavior on a per-request basis:
 
-| Header                   | Type        | Description                                             |
-| ------------------------ | ----------- | ------------------------------------------------------- |
-| `cf-aig-skip-cache`      | boolean     | Skip the cache for this request.                        |
-| `cf-aig-cache-ttl`       | number      | Cache TTL in seconds.                                   |
-| `cf-aig-cache-key`       | string      | Custom cache key.                                       |
-| `cf-aig-collect-log`     | boolean     | Turn logging on or off for this request.                |
-| `cf-aig-request-timeout` | number      | Request timeout in milliseconds.                        |
-| `cf-aig-max-attempts`    | number      | Retry attempts (max 5).                                 |
-| `cf-aig-retry-delay`     | number      | Retry delay in milliseconds (max 5000).                 |
-| `cf-aig-backoff`         | string      | Backoff method: `constant`, `linear`, or `exponential`. |
-| `cf-aig-metadata`        | JSON string | Custom metadata to attach to the log entry.             |
+| Header | Type | Description |
+| ------ | ---- | ----------- |
+| `cf-aig-skip-cache` | boolean | Skip the cache for this request. |
+| `cf-aig-cache-ttl` | number | Cache TTL in seconds. |
+| `cf-aig-cache-key` | string | Custom cache key. |
+| `cf-aig-collect-log` | boolean | Turn logging on or off for this request. |
+| `cf-aig-request-timeout` | number | Request timeout in milliseconds. |
+| `cf-aig-max-attempts` | number | Retry attempts (max 5). |
+| `cf-aig-retry-delay` | number | Retry delay in milliseconds (max 5000). |
+| `cf-aig-backoff` | string | Backoff method: `constant`, `linear`, or `exponential`. |
+| `cf-aig-metadata` | JSON string | Custom metadata to attach to the log entry. |
 
 For more details on these options, refer to [Request handling](/ai-gateway/configuration/request-handling/) and [Caching](/ai-gateway/features/caching/).
 
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
index dd9b384084acdcf..bfc911e09f973c8 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/non-realtime-api.mdx
@@ -55,7 +55,7 @@ ws.on("open", () => {
 			},
 		}),
 	);
-});
+})
 
 ws.on("message", (message) => {
 	console.log(message.toString());
diff --git a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
index f444cff4c7a73ef..57c34339587a994 100644
--- a/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
+++ b/src/content/docs/ai-gateway/usage/websockets-api/realtime-api.mdx
@@ -272,7 +272,7 @@ let isPlayingAudio = false;
 const rl = readline.createInterface({
 	input: process.stdin,
 	output: process.stdout,
-	prompt: 'Enter text to speak (or "quit" to exit): ',
+	prompt: "Enter text to speak (or \"quit\" to exit): ",
 });
 
 ws.onopen = () => {
diff --git a/src/content/docs/ai-search/api/instances/rest-api.mdx b/src/content/docs/ai-search/api/instances/rest-api.mdx
index 37757fbb0ff5362..178f1c9d6c69011 100644
--- a/src/content/docs/ai-search/api/instances/rest-api.mdx
+++ b/src/content/docs/ai-search/api/instances/rest-api.mdx
@@ -20,8 +20,8 @@ Use the AI Search REST API to manage instances and sync jobs over HTTP.
 
 AI Search APIs are available at two base paths:
 
-| Path                                                                     | Description                                                                 |
-| ------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
+| Path                                                                 | Description                                                                 |
+| -------------------------------------------------------------------- | --------------------------------------------------------------------------- |
 | `/accounts/{account_id}/ai-search/instances/{id}`                        | Operates on a specific instance                                             |
 | `/accounts/{account_id}/ai-search/namespaces/{namespace}/instances/{id}` | Operates on instances within a [namespace](/ai-search/concepts/namespaces/) |
 
diff --git a/src/content/docs/ai-search/api/items/rest-api.mdx b/src/content/docs/ai-search/api/items/rest-api.mdx
index 08634485801ed10..f23b4dd83703914 100644
--- a/src/content/docs/ai-search/api/items/rest-api.mdx
+++ b/src/content/docs/ai-search/api/items/rest-api.mdx
@@ -35,8 +35,8 @@ The available operations are the same for both paths. For the namespace-scoped A
 
 Upload, list, get, delete, and download items within an instance. For the full specification, refer to the [Items API reference](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/).
 
-| Operation                                                                                                                | Method   | Description                    |
-| ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------ |
+| Operation                                                                                                            | Method   | Description                    |
+| -------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------ |
 | [Upload](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/upload/)     | `POST`   | Upload a document for indexing |
 | [List](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/list/)         | `GET`    | List all items in an instance  |
 | [Get](/api/resources/ai_search/subresources/namespaces/subresources/instances/subresources/items/methods/get/)           | `GET`    | Get item info by ID            |
diff --git a/src/content/docs/ai-search/configuration/models/index.mdx b/src/content/docs/ai-search/configuration/models/index.mdx
index 42a76abb29e721b..c406d789f32edfa 100644
--- a/src/content/docs/ai-search/configuration/models/index.mdx
+++ b/src/content/docs/ai-search/configuration/models/index.mdx
@@ -28,10 +28,12 @@ To use AI Search with other model providers:
 
 1. Add provider keys to [AI Gateway](/ai-gateway/configuration/bring-your-own-keys/).
 2. Connect the gateway to AI Search.
+
    - When creating a new AI Search, select the AI Gateway with your provider keys.
    - For an existing AI Search, go to **Settings** and switch to a gateway that has your keys under **Resources**.
 
 3. Select models
+
    - Embedding model: Only available to be changed when creating a new AI Search.
    - Generation model: Can be selected when creating a new AI Search and can be changed at any time in **Settings**.
 
diff --git a/src/content/docs/ai-search/how-to/nlweb.mdx b/src/content/docs/ai-search/how-to/nlweb.mdx
index eb36852ae5534f6..25d61bcba3c3cb7 100644
--- a/src/content/docs/ai-search/how-to/nlweb.mdx
+++ b/src/content/docs/ai-search/how-to/nlweb.mdx
@@ -67,23 +67,23 @@ You can use the embeddable snippet to add a search UI directly into your website
 
 ```html
 <!-- Add css on head -->
-<link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css" />
-<link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css" />
-
-<!-- Add container on body -->
-<div id="docs-search-container"></div>
-
-<!-- Include JavaScript -->
-<script type="module">
-	import { NLWebDropdownChat } from "https://ask.example.com/nlweb-dropdown-chat.js";
-
-	const chat = new NLWebDropdownChat({
-		containerId: "docs-search-container",
-		site: "https://ask.example.com",
-		placeholder: "Search for docs...",
-		endpoint: "https://ask.example.com",
-	});
-</script>
+    <link rel="stylesheet" href="https://ask.example.com/nlweb-dropdown-chat.css">
+    <link rel="stylesheet" href="https://ask.example.com/common-chat-styles.css">
+
+    <!-- Add container on body -->
+    <div id="docs-search-container"></div>
+
+    <!-- Include JavaScript -->
+    <script type="module">
+      import { NLWebDropdownChat } from 'https://ask.example.com/nlweb-dropdown-chat.js';
+
+      const chat = new NLWebDropdownChat({
+        containerId: 'docs-search-container',
+        site: 'https://ask.example.com',
+        placeholder: 'Search for docs...',
+        endpoint: 'https://ask.example.com'
+      });
+    </script>
 ```
 
 This lets you serve conversational AI search directly from your own domain, with control over how people and agents access your content.
diff --git a/src/content/docs/ai-search/wrangler-commands.mdx b/src/content/docs/ai-search/wrangler-commands.mdx
index 916b781370d0e81..f8e1fa53538eca8 100644
--- a/src/content/docs/ai-search/wrangler-commands.mdx
+++ b/src/content/docs/ai-search/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { WranglerNamespace, WranglerCommand } from "~/components";
 
-<WranglerNamespace namespace="ai-search" />
+<WranglerNamespace namespace="ai-search" />
\ No newline at end of file
diff --git a/src/content/docs/ai/related-products/ai-gateway.mdx b/src/content/docs/ai/related-products/ai-gateway.mdx
index 75063087b321b29..c868d2c8ec2fd75 100644
--- a/src/content/docs/ai/related-products/ai-gateway.mdx
+++ b/src/content/docs/ai/related-products/ai-gateway.mdx
@@ -6,5 +6,5 @@ sidebar:
 external_link: /ai-gateway/
 products:
   - ai
-  - ai-gateway
+  - ai-gateway  
 ---
diff --git a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
index c5d95a03c76c5d4..0d4aaf4a63bca3e 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/account-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - analytics
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Cloudflare account analytics lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
@@ -18,29 +18,29 @@ Cloudflare account analytics lets you access a wide range of aggregated metrics
 For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
 :::
 
----
+***
 
 ## View your account analytics
 
 To view metrics for your site, in the Cloudflare dashboard, go to the **Account Analytics** page.
 
-<DashButton url="/?to=/:account/analytics" />
+   <DashButton url="/?to=/:account/analytics" />
 
-Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to _Review your account metrics_ below.
+Once it loads, the Account Analytics app displays a collection of categorized charts with aggregated metrics for your account. To understand the various metrics available, refer to *Review your account metrics* below.
 
----
+***
 
 ## Review your account metrics
 
 This section outlines the aggregated metrics under each category. Before reviewing your metrics, let's define a couple of concepts used in some panels:
 
-- _Rate_ -  Reflects the ratio between the amount for a specific data category and the total.
-- _Bandwidth_ - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
+* *Rate* -  Reflects the ratio between the amount for a specific data category and the total.
+* *Bandwidth* - Refers to the number of bytes sent from the Cloudflare edge network to the requesting client.
 
 Also, note that:
 
-- To filter metrics for a specific time period, use the dropdown in the top right.
-- Most metrics are grouped into panels representing different aspects of the underlying data.
+* To filter metrics for a specific time period, use the dropdown in the top right.
+* Most metrics are grouped into panels representing different aspects of the underlying data.
 
 ### Summary of metrics
 
@@ -52,21 +52,21 @@ These charts aggregate data for HTTP traffic, and include:
 
 ![Chart showing last week's data for HTTP traffic](~/assets/images/support/hc-dash-account-analytics-map.png)
 
-- Spark lines for _Requests_, _Bandwidth_, _Page views_, and _Visitors_ (_Unique IPs)_
-- An interactive map that breaks down the number of requests by country
-- A table combining numerical and spark line data, sorted by total number of requests per country
+* Spark lines for *Requests*, *Bandwidth*, *Page views*, and *Visitors* (*Unique IPs)*
+* An interactive map that breaks down the number of requests by country
+* A table combining numerical and spark line data, sorted by total number of requests per country
 
 #### Security
 
 ![Panel displaying lines highlighting encryption metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_security_panel.png)
 
-This panel features spark lines highlighting various encryption metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous period.
+This panel features spark lines highlighting various encryption metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous period.
 
 #### Cache
 
 ![Panel displaying lines for caching metrics: requests, requests rate, bandwidth, and bandwidth rate](~/assets/images/support/hc-dash-account-analytics_cache_card.png)
 
-This panel features spark lines for various caching metrics, including: _requests_, _requests rate_, _bandwidth_, and _bandwidth rate_.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected _Last week_ as your time period, the previous period refers to the _week_ before.
+This panel features spark lines for various caching metrics, including: *requests*, *requests rate*, *bandwidth*, and *bandwidth rate*.  These also include a comparative percentage change based on the previous equivalent period.  For example, if you selected *Last week* as your time period, the previous period refers to the *week* before.
 
 #### Errors
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
index 84e856b537c7e3a..76dccf882a47092 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
@@ -13,7 +13,7 @@ Learn how Cloudflare analytics tracks requests made by [Cloudflare Workers](/wor
 
 With a no-op Worker (a Worker that simply proxies traffic by passing on the original client request to the origin and proxying the response) running on a particular route, the request to the origin is counted as a 'subrequest', separate from initial client to edge request. Thus, unless the Worker responds with a static response and never hits an origin, the eyeball → edge request, and edge → origin request will each be counted separately towards the request or bandwidth count in Analytics. Subrequests are not included in the **Requests** or **Bandwidth** graphs of the Cloudflare **Analytics** app.
 
----
+***
 
 ## Zone analytics
 
@@ -21,20 +21,20 @@ In the dashboard, the numbers in zone analytics reflect visitor traffic. That is
 
 Similarly, the bandwidth is counted based on the bandwidth that is sent to the client, and status codes reflect the status codes that were served back to the client (so if a subrequest received a 500, but you respond with a 200, a 200 will be shown in the status codes breakdown).
 
----
+***
 
 ## Worker analytics
 
 For a breakdown of subrequest traffic (origin facing traffic), you may go to the Cloudflare **Analytics** app and select the **Workers** tab. Under the **Workers** tab, below the Service Workers panel, are a **Subrequests** breakdown by count, **Bandwidth** and **Status Codes**. This will help you spot and debug errors at your origin (such as spikes in 500s), and identify your cache-hit ratio to help you understand traffic going to your origin.
 
----
+***
 
 ## FAQ
 
 **Why do I not have any analytics for Workers?**
 
-- If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
-- If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
+* If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
+* If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
 
 **Will this impact billing?** 
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/index.mdx b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
index 2aeb75e8f6f6dc4..54e99ae3cb5ec74 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/index.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Visit the following pages to learn more about account and zone analytics:
 
diff --git a/src/content/docs/analytics/analytics-engine/grafana.mdx b/src/content/docs/analytics/analytics-engine/grafana.mdx
index 96310e19e31d8cc..e6af88fd7a7a901 100644
--- a/src/content/docs/analytics/analytics-engine/grafana.mdx
+++ b/src/content/docs/analytics/analytics-engine/grafana.mdx
@@ -20,10 +20,10 @@ We recommend the use of the [Altinity plugin for Clickhouse](https://grafana.com
 
 Configure the plugin as follows:
 
-- URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
-- Leave all auth settings off.
-- Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
-- No other options need to be set.
+* URL: `https://api.cloudflare.com/client/v4/accounts/<account_id>/analytics_engine/sql`. Replace `<account_id>` with your 32 character account ID (available in the Cloudflare dashboard).
+* Leave all auth settings off.
+* Add a custom header with a name of `Authorization` and value set to `Bearer <token>`. Replace `<token>` with suitable API token string (refer to the [SQL API docs](/analytics/analytics-engine/sql-api/#authentication) for more information on this).
+* No other options need to be set.
 
 ## Querying timeseries data
 
@@ -35,8 +35,8 @@ SELECT
     blob1 AS label,
     SUM(_sample_interval * double1) / SUM(_sample_interval) AS average_metric
 FROM dataset_name
-WHERE
-    timestamp <= NOW()
+WHERE 
+    timestamp <= NOW() 
     AND timestamp > NOW() - INTERVAL '1' DAY
 GROUP BY blob1, t
 ORDER BY t
diff --git a/src/content/docs/analytics/analytics-engine/index.mdx b/src/content/docs/analytics/analytics-engine/index.mdx
index ddee07f45c1808c..2eae0d36b0eab7d 100644
--- a/src/content/docs/analytics/analytics-engine/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/index.mdx
@@ -8,17 +8,15 @@ products:
   - workers-analytics-engine
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 Workers Analytics Engine provides unlimited-cardinality analytics at scale, via [a built-in API](/analytics/analytics-engine/get-started/) to write data points from Workers, and a [SQL API](/analytics/analytics-engine/sql-api/) to query that data.
 
 You can use Workers Analytics Engine to:
 
-- Expose custom analytics to your own customers
-- Build usage-based billing systems
-- Understand the health of your service on a per-customer or per-user basis
-- Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
+* Expose custom analytics to your own customers
+* Build usage-based billing systems
+* Understand the health of your service on a per-customer or per-user basis
+* Add instrumentation to frequently called code paths, without impacting performance or overwhelming external analytics systems with events
 
-<LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">
-	Get started
-</LinkButton>
+ <LinkButton variant="primary" href="/analytics/analytics-engine/get-started/">Get started</LinkButton>
diff --git a/src/content/docs/analytics/analytics-engine/limits.mdx b/src/content/docs/analytics/analytics-engine/limits.mdx
index d4eb97a73b95fcb..293093c33e3343b 100644
--- a/src/content/docs/analytics/analytics-engine/limits.mdx
+++ b/src/content/docs/analytics/analytics-engine/limits.mdx
@@ -13,10 +13,10 @@ products:
 
 The following limits apply to Workers Analytics Engine:
 
-- Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
-- The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
-- Each index must not be more than 96 bytes.
-- You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
+* Analytics Engine will accept up to twenty blobs, twenty doubles, and one index per call to `writeDataPoint`.
+* The total size of all blobs in a request must not exceed **16 KB**. The 16 KB size limit for the blobs field applies to **each individual data point**, regardless of how many are included in a single request using writeDataPoints().
+* Each index must not be more than 96 bytes.
+* You can write a maximum of 250 data points per Worker invocation (client HTTP request). Each call to `writeDataPoint` counts towards this limit.
 
 ## Data retention
 
diff --git a/src/content/docs/analytics/analytics-engine/pricing.mdx b/src/content/docs/analytics/analytics-engine/pricing.mdx
index bef373bc86ebf85..059f55deae8360d 100644
--- a/src/content/docs/analytics/analytics-engine/pricing.mdx
+++ b/src/content/docs/analytics/analytics-engine/pricing.mdx
@@ -23,7 +23,7 @@ Workers Analytics Engine is priced based on two metrics — data points written
 
 Currently, you will not be billed for your use of Workers Analytics Engine. Pricing information here is shared in advance, so that you can estimate what your costs will be once Cloudflare starts billing for usage in the coming months.
 
-If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing.
+If you are an Enterprise customer, contact your account team for information about Workers Analytics Engine pricing and billing. 
 :::
 
 ### Data points written
diff --git a/src/content/docs/analytics/analytics-engine/recipes/index.mdx b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
index 17c5d1b314b065e..f0a1bab71954b46 100644
--- a/src/content/docs/analytics/analytics-engine/recipes/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/recipes/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Example implementations of common use cases for Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sampling.mdx b/src/content/docs/analytics/analytics-engine/sampling.mdx
index bc8b75c9cac7e72..c358eadeb8f377c 100644
--- a/src/content/docs/analytics/analytics-engine/sampling.mdx
+++ b/src/content/docs/analytics/analytics-engine/sampling.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>).
+Workers Analytics Engine offers the ability to write an extensive amount of data and retrieve it quickly, at minimal or no cost. To facilitate writing large amounts of data at a reasonable cost, Workers Analytics Engine employs weighted adaptive [sampling](https://en.wikipedia.org/wiki/Sampling_\(statistics\)).
 
 When utilizing sampling, you do not need every single data point to answer questions about a dataset. For a sufficiently large dataset, the [necessary sample size](https://select-statistics.co.uk/blog/importance-effect-sample-size/) does not depend on the size of the original population. Necessary sample size depends on the variance of your measure, the size of the subgroups you analyze, and how accurate your estimate must be.
 
@@ -24,11 +24,11 @@ At a high level, the way sampling works is:
 
 In the following sections, you will learn:
 
-- [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
-- [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
-- [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
-- [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
-- [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
+* [How sampling works](/analytics/analytics-engine/sampling/#how-sampling-works).
+* [How to read sampled data](/analytics/analytics-engine/sampling/#how-to-read-sampled-data).
+* [How is data sampled](/analytics/analytics-engine/sampling/#how-is-data-sampled).
+* [How Adaptive Bit Rate Sampling works](/analytics/analytics-engine/sampling/#adaptive-bit-rate-sampling-at-read-time).
+* [How to pick your index such that your data is sampled in a usable way](/analytics/analytics-engine/sampling/#how-to-select-an-index).
 
 ## How sampling works
 
@@ -44,15 +44,15 @@ The key point is that the map's quality does not solely depend on the resolution
 
 There are similarities between the how a mapping services handles resolution and Cloudflare Analytics delivers analytics using adaptive samples:
 
-- **How data is stored**:
-  - **Mapping service**: Imagery stored at different resolutions.
-  - **Cloudflare Analytics**: Events stored at different sample rates.
-- **How data is displayed to user**:
-  - **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
-  - **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
-- **How a resolution is selected**:
-  - **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
-  - **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
+* **How data is stored**:
+  * **Mapping service**: Imagery stored at different resolutions.
+  * **Cloudflare Analytics**: Events stored at different sample rates.
+* **How data is displayed to user**:
+  * **Mapping service**: The total number of pixels is \~constant for a given screen size, regardless of the area selected.
+  * **Cloudflare Analytics**: A similar number of events are read for each query, regardless of the size of the dataset or length of time selected.
+* **How a resolution is selected**:
+  * **Mapping service**: The area represented by each pixel will depend on the size of the map being rendered. In a more zoomed out map, each pixel will represent a larger area.
+  * **Cloudflare Analytics**: The sample interval of each event in the result depends on the size of the underlying dataset and length of time selected. For a query over a large dataset or long length of time, each sampled event may stand in for many similar events.
 
 ## How to read sampled data
 
@@ -87,11 +87,11 @@ If we took a [simple random sample](https://en.wikipedia.org/wiki/Simple_random_
 
 ![The same graphic as above, but now based on a 1% sample of the data.](~/assets/images/analytics/sample-data.png)
 
-Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](<https://en.wikipedia.org/wiki/Quantization_(signal_processing)>) and may even be rounded to 0 entirely.
+Notice that the larger bars look more or less unchanged, and yet they are still quite accurate. But as you analyze smaller customers, results get [quantized](https://en.wikipedia.org/wiki/Quantization_\(signal_processing\)) and may even be rounded to 0 entirely.
 
 This shows that while a one percent (1%) or even smaller sample of a large population may be sufficient, we may need to store a larger proportion of events for a small population to get accurate results.
 
-We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`. But if you write lots of data points to a single index value, we will start to sample.
+We do this through a technique called equitable sampling. This means that we will equalize the number of events we store for each unique index value. For relatively uncommon index values, we may write all of the data points that we get via `writeDataPoint()`.  But if you write lots of data points to a single index value, we will start to sample.
 
 Here is the same distribution, but now with (a simulation of) equitable sampling applied:
 
@@ -117,23 +117,23 @@ In order to get accurate results with sampled data, select an appropriate value
 
 The index has the following properties, which are important to consider when choosing an index:
 
-- Get accurate summary statistics about your entire dataset, across all index values.
-- Get an accurate count of the number of unique values of your index.
-- Get accurate summary statistics (for example, count, sum) within a particular index value.
-- See the `Top N` values of specific fields that are not in your index.
-- Filter on most fields.
-- Run other aggregations like quantiles.
+* Get accurate summary statistics about your entire dataset, across all index values.
+* Get an accurate count of the number of unique values of your index.
+* Get accurate summary statistics (for example, count, sum) within a particular index value.
+* See the `Top N` values of specific fields that are not in your index.
+* Filter on most fields.
+* Run other aggregations like quantiles.
 
 Some limitations and trade-offs to consider are:
 
-- You may not be able to get accurate unique counts of fields that are not in your index.
-  - For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
-- You may not be able to observe very rare values of fields not in the index.
-  - For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
-- You may not be able to run accurate queries across multiple indices at once.
-  - For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
-- There is no guarantee you can retrieve any one individual record.
-- You cannot necessarily reconstruct exact sequences of events.
+* You may not be able to get accurate unique counts of fields that are not in your index.
+  * For example, if you index on `hostname`, you may not be able to count the number of unique URLs.
+* You may not be able to observe very rare values of fields not in the index.
+  * For example, a particular URL for a hostname, if you index on host and have millions of unique URLs.
+* You may not be able to run accurate queries across multiple indices at once.
+  * For example, you may only be able to query for one host at a time (or all of them) and expect accurate results.
+* There is no guarantee you can retrieve any one individual record.
+* You cannot necessarily reconstruct exact sequences of events.
 
 It is not recommended to write a unique index value on every row (like a UUID) for most use cases. While this will make it possible to retrieve individual data points very quickly, it will slow down most queries for aggregations and time series.
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-api.mdx b/src/content/docs/analytics/analytics-engine/sql-api.mdx
index 1801c7d93dbaf1a..55cfccf8e90d48f 100644
--- a/src/content/docs/analytics/analytics-engine/sql-api.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-api.mdx
@@ -25,10 +25,10 @@ Use the dashboard to create a token with permission to read analytics data on yo
 2. Select **Create Token**.
 3. Select **Create Custom Token**.
 4. Complete the **Create Custom Token** form as follows:
-   - Give your token a descriptive name.
-   - For **Permissions** select _Account_ | _Account Analytics_ | _Read_
-   - Optionally configure account and IP restrictions and TTL.
-   - Submit and confirm the form to create the token.
+   * Give your token a descriptive name.
+   * For **Permissions** select *Account* | *Account Analytics* | *Read*
+   * Optionally configure account and IP restrictions and TTL.
+   * Submit and confirm the form to create the token.
 5. Make a note of the token string.
 
 ## Querying the API
@@ -63,7 +63,7 @@ The table will have the following columns:
 | ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | dataset                      | string   | This column will contain the dataset name in every row.                                                                                                                                                                                              |
 | timestamp                    | DateTime | The timestamp at which the event was logged in your worker.                                                                                                                                                                                          |
-| \_sample_interval            | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
+| \_sample\_interval           | integer  | In case that the data has been sampled, this column indicates what the sample rate is for this row (that is, how many rows of the original data are represented by this row). Refer to the [sampling](#sampling) section below for more information. |
 | index1                       | string   | The index value that was logged with the event. The value in this column is used as the key for sampling.                                                                                                                                            |
 | blob1<br/>...<br/>blob20     | string   | The blob values that were logged with the event.                                                                                                                                                                                                     |
 | double1<br/>...<br/>double20 | double   | The double values that were logged with the event.                                                                                                                                                                                                   |
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
index 62e8e01ba6ec69f..4d1827c650f3567 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## count
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
index 9a64750c492178a..f8d061a0f4b5635 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/bit-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## bitAnd <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
index 46e2141c8ef25e0..9db9dac5fb7d21a 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/date-time-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## formatDateTime
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
index 016f68450f83fef..851779802af43f3 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/encoding-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## bin <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
index e8a324356d02009..ebe0124792308e4 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Reference documentation describing the SQL supported by Workers Analytics Engine:
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
index 97035f5a95abd0e..ba40ae26a6009c2 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/mathematical-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## intDiv
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
index 40411492466534f..9a4b8089ef3d6c5 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/string-functions.mdx
@@ -12,7 +12,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## length
 
diff --git a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
index 1ddf69b03623497..f87f1a7eb19e146 100644
--- a/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
+++ b/src/content/docs/analytics/analytics-engine/sql-reference/type-conversion-functions.mdx
@@ -11,7 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
-import { Badge } from "~/components";
+import { Badge } from "~/components"
 
 ## toUInt8 <Badge text="New" variant="tip" size="small" />
 
diff --git a/src/content/docs/analytics/analytics-engine/worker-querying.mdx b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
index 0a8521edc362e68..81c7b08511cf5ca 100644
--- a/src/content/docs/analytics/analytics-engine/worker-querying.mdx
+++ b/src/content/docs/analytics/analytics-engine/worker-querying.mdx
@@ -11,6 +11,7 @@ products:
   - workers-analytics-engine
 ---
 
+
 import { WranglerConfig } from "~/components";
 
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
diff --git a/src/content/docs/analytics/analytics-integrations/datadog.mdx b/src/content/docs/analytics/analytics-integrations/datadog.mdx
index 07af42f65157723..579cc03b68a207a 100644
--- a/src/content/docs/analytics/analytics-integrations/datadog.mdx
+++ b/src/content/docs/analytics/analytics-integrations/datadog.mdx
@@ -36,6 +36,7 @@ To install the Cloudflare App for Datadog:
 4. Click the **Cloudflare** tile to begin the installation.
 
 5. Next, click **Configuration** and then complete the following:
+
    - **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
 
    - **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
diff --git a/src/content/docs/analytics/analytics-integrations/index.mdx b/src/content/docs/analytics/analytics-integrations/index.mdx
index f97ccae2ade7ad9..12212b2b3fbc24f 100644
--- a/src/content/docs/analytics/analytics-integrations/index.mdx
+++ b/src/content/docs/analytics/analytics-integrations/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare Enterprise customers can use Cloudflare integrations with their preferred analytics provider and configure ready-to-use Cloudflare Dashboards. Most analytics integrations are built on Cloudflare Logs by using Logpush with either Amazon S3 bucket or GCP Storage bucket.
 
diff --git a/src/content/docs/analytics/analytics-integrations/prometheus.mdx b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
index bcee11a6e7f26eb..10a355c84e93b3d 100644
--- a/src/content/docs/analytics/analytics-integrations/prometheus.mdx
+++ b/src/content/docs/analytics/analytics-integrations/prometheus.mdx
@@ -59,16 +59,16 @@ Create a Cloudflare API token with the following permissions:
 
 [Create token with pre-filled permissions](https://dash.cloudflare.com/profile/api-tokens?permissionGroupKeys=%5B%7B%22key%22%3A%22analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_analytics%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22workers_scripts%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22ssl_and_certificates%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22firewall_services%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22load_balancers%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22account_logs%22%2C%22type%22%3A%22read%22%7D%2C%7B%22key%22%3A%22magic_transit%22%2C%22type%22%3A%22read%22%7D%5D&name=Cloudflare%20Prometheus%20Exporter)
 
-| Permission                  | Access | Required |
-| --------------------------- | ------ | -------- |
-| Zone > Analytics            | Read   | Yes      |
-| Account > Account Analytics | Read   | Yes      |
-| Account > Workers Scripts   | Read   | Yes      |
-| Zone > SSL and Certificates | Read   | Optional |
-| Zone > Firewall Services    | Read   | Optional |
-| Zone > Load Balancers       | Read   | Optional |
-| Account > Logs              | Read   | Optional |
-| Account > Magic Transit     | Read   | Optional |
+| Permission | Access | Required |
+|---|---|---|
+| Zone > Analytics | Read | Yes |
+| Account > Account Analytics | Read | Yes |
+| Account > Workers Scripts | Read | Yes |
+| Zone > SSL and Certificates | Read | Optional |
+| Zone > Firewall Services | Read | Optional |
+| Zone > Load Balancers | Read | Optional |
+| Account > Logs | Read | Optional |
+| Account > Magic Transit | Read | Optional |
 
 ## Task 3 - Configure Prometheus
 
@@ -76,11 +76,11 @@ Add the exporter as a scrape target in your Prometheus configuration:
 
 ```yaml
 scrape_configs:
-  - job_name: "cloudflare"
+  - job_name: 'cloudflare'
     scrape_interval: 60s
     scrape_timeout: 30s
     static_configs:
-      - targets: ["your-worker.your-subdomain.workers.dev"]
+      - targets: ['your-worker.your-subdomain.workers.dev']
 ```
 
 ### With Basic Auth
@@ -89,14 +89,14 @@ If you configured Basic Auth on the exporter, update your Prometheus configurati
 
 ```yaml
 scrape_configs:
-  - job_name: "cloudflare"
+  - job_name: 'cloudflare'
     scrape_interval: 60s
     scrape_timeout: 30s
     basic_auth:
-      username: "your-username"
-      password: "your-password"
+      username: 'your-username'
+      password: 'your-password'
     static_configs:
-      - targets: ["your-worker.your-subdomain.workers.dev"]
+      - targets: ['your-worker.your-subdomain.workers.dev']
 ```
 
 ## Configuration
@@ -105,32 +105,32 @@ Configuration is resolved in order: **KV overrides** > **environment variables**
 
 Set environment variables in `wrangler.jsonc` or via `wrangler secret put`:
 
-| Variable                          | Default    | Description                                           |
-| --------------------------------- | ---------- | ----------------------------------------------------- |
-| `CLOUDFLARE_API_TOKEN`            | -          | Cloudflare API token (secret)                         |
-| `SCRAPE_DELAY_SECONDS`            | `300`      | Delay before fetching metrics (data propagation)      |
-| `TIME_WINDOW_SECONDS`             | `60`       | Query time window                                     |
-| `METRIC_REFRESH_INTERVAL_SECONDS` | `60`       | Background refresh interval                           |
-| `CF_ACCOUNTS`                     | -          | Comma-separated account IDs to include (default: all) |
-| `CF_ZONES`                        | -          | Comma-separated zone IDs to include (default: all)    |
-| `METRICS_DENYLIST`                | -          | Comma-separated list of metrics to exclude            |
-| `EXCLUDE_HOST`                    | `false`    | Exclude host labels from metrics                      |
-| `METRICS_PATH`                    | `/metrics` | Custom path for metrics endpoint                      |
-| `BASIC_AUTH_USER`                 | -          | Username for Basic Auth (secret)                      |
-| `BASIC_AUTH_PASSWORD`             | -          | Password for Basic Auth (secret)                      |
+| Variable | Default | Description |
+|---|---|---|
+| `CLOUDFLARE_API_TOKEN` | - | Cloudflare API token (secret) |
+| `SCRAPE_DELAY_SECONDS` | `300` | Delay before fetching metrics (data propagation) |
+| `TIME_WINDOW_SECONDS` | `60` | Query time window |
+| `METRIC_REFRESH_INTERVAL_SECONDS` | `60` | Background refresh interval |
+| `CF_ACCOUNTS` | - | Comma-separated account IDs to include (default: all) |
+| `CF_ZONES` | - | Comma-separated zone IDs to include (default: all) |
+| `METRICS_DENYLIST` | - | Comma-separated list of metrics to exclude |
+| `EXCLUDE_HOST` | `false` | Exclude host labels from metrics |
+| `METRICS_PATH` | `/metrics` | Custom path for metrics endpoint |
+| `BASIC_AUTH_USER` | - | Username for Basic Auth (secret) |
+| `BASIC_AUTH_PASSWORD` | - | Password for Basic Auth (secret) |
 
 For a full list of configuration options, refer to the [exporter README](https://github.com/cloudflare/cloudflare-prometheus-exporter#configuration).
 
 ## Endpoints
 
-| Path           | Method | Description                             |
-| -------------- | ------ | --------------------------------------- |
-| `/`            | GET    | Landing page                            |
-| `/metrics`     | GET    | Prometheus metrics                      |
-| `/health`      | GET    | Health check                            |
-| `/config`      | GET    | Get all runtime config                  |
-| `/config/:key` | PUT    | Set a config override (persisted in KV) |
-| `/config/:key` | DELETE | Reset a config key to its default       |
+| Path | Method | Description |
+|---|---|---|
+| `/` | GET | Landing page |
+| `/metrics` | GET | Prometheus metrics |
+| `/health` | GET | Health check |
+| `/config` | GET | Get all runtime config |
+| `/config/:key` | PUT | Set a config override (persisted in KV) |
+| `/config/:key` | DELETE | Reset a config key to its default |
 
 ## Available metrics
 
@@ -160,7 +160,6 @@ For a complete list of metrics with types and labels, refer to the [exporter REA
 Zones on Cloudflare's Free plan do not have access to the GraphQL Analytics API. The exporter automatically detects and skips free tier zones for metrics that require this API.
 
 Free tier zones still export:
-
 - `cloudflare_zone_certificate_validation_status` (SSL certificates)
 - `cloudflare_zone_lb_origin_weight` (Load balancer weights, if configured)
 
diff --git a/src/content/docs/analytics/custom-dashboards.mdx b/src/content/docs/analytics/custom-dashboards.mdx
index 11fc76cc324f367..49b08e4bdd64804 100644
--- a/src/content/docs/analytics/custom-dashboards.mdx
+++ b/src/content/docs/analytics/custom-dashboards.mdx
@@ -28,10 +28,10 @@ Investigate incidents so that when something goes wrong, you can create focused
 
 Custom Dashboards are available to all Cloudflare customers.
 
-| Customer type            | Dashboard limit      |
-| ------------------------ | -------------------- |
-| All Cloudflare customers | Up to 25 dashboards  |
-| Log Explorer customers   | Up to 100 dashboards |
+| Customer type | Dashboard limit |
+|---------------|-----------------|
+| All Cloudflare customers | Up to 25 dashboards |
+| Log Explorer customers | Up to 100 dashboards |
 
 ## Get started
 
@@ -39,13 +39,13 @@ Custom Dashboards are available to all Cloudflare customers.
 
 Templates are the fastest way to get value from Custom Dashboards. Each template is designed around a specific use case and includes pre-configured charts that surface the most relevant metrics.
 
-| Template                   | Use case                                                                                                                                 |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| **Bot monitoring**         | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors              |
-| **API Security**           | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns                           |
-| **Account takeover**       | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
-| **API Performance**        | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain   |
-| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time  |
+| Template | Use case |
+|----------|----------|
+| **Bot monitoring** | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors |
+| **API Security** | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns |
+| **Account takeover** | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
+| **API Performance** | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain |
+| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time |
 
 After selecting a template, you can customize it by adding, removing, or modifying charts to fit your specific needs.
 
@@ -81,15 +81,15 @@ For precise control, configure each element of your chart:
 
 Choose the visualization that best fits your data:
 
-| Chart type     | Best for                                                                                 |
-| -------------- | ---------------------------------------------------------------------------------------- |
+| Chart type | Best for |
+|------------|----------|
 | **Timeseries** | Trends and patterns over time — traffic spikes, latency changes, error rate fluctuations |
-| **Bar**        | Comparing values across categories — requests by country, errors by status code          |
-| **Donut**      | Understanding proportions — cache hit ratio, traffic distribution by content type        |
-| **Map**        | Geographic patterns — where your traffic originates, regional performance differences    |
-| **Stat**       | Single important numbers — total requests today, current error rate, p99 latency         |
-| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion                          |
-| **Top N**      | Rankings — busiest endpoints, most blocked IPs, top user agents                          |
+| **Bar** | Comparing values across categories — requests by country, errors by status code |
+| **Donut** | Understanding proportions — cache hit ratio, traffic distribution by content type |
+| **Map** | Geographic patterns — where your traffic originates, regional performance differences |
+| **Stat** | Single important numbers — total requests today, current error rate, p99 latency |
+| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion |
+| **Top N** | Rankings — busiest endpoints, most blocked IPs, top user agents |
 
 #### Example: Build a security overview chart
 
diff --git a/src/content/docs/analytics/faq/about-analytics.mdx b/src/content/docs/analytics/faq/about-analytics.mdx
index 53d5f449641933e..027f8a07eb32e94 100644
--- a/src/content/docs/analytics/faq/about-analytics.mdx
+++ b/src/content/docs/analytics/faq/about-analytics.mdx
@@ -23,10 +23,10 @@ Refer to [Types of analytics](/analytics/types-of-analytics/) for more informati
 
 The underlying datasets that Cloudflare Analytics captures and processes share the following characteristics:
 
-- All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
-- Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
-- Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
-- In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
+* All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
+* Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
+* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
+* In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](/network/ip-geolocation/).
 
 ## Apparent data discrepancies
 
@@ -42,10 +42,10 @@ Finally, it is likely that unique visitor data from the Cloudflare Analytics app
 
 You may not be seeing metrics on Cloudflare Analytics for the following reasons:
 
-- You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
-- If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
-- If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
-- Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
+* You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
+* If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
+* If you signed up through a Cloudflare [hosting partner option](https://www.cloudflare.com/partners/), something might not be configured correctly. Contact the hosting partner for support.
+* Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow `cloudflare.com` on it.
 
 :::note
 Activations through a hosting partner works via a [CNAME setup](/dns/zone-setups/partial-setup/) on the `www` record. If most of your traffic actually goes to `domain.com`, [forward your traffic](/rules/url-forwarding/bulk-redirects/) from `domain.com` to `www.domain.com`.
diff --git a/src/content/docs/analytics/faq/index.mdx b/src/content/docs/analytics/faq/index.mdx
index 555fcdc07a3795f..c7d87c530a29c24 100644
--- a/src/content/docs/analytics/faq/index.mdx
+++ b/src/content/docs/analytics/faq/index.mdx
@@ -10,7 +10,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Visit the following pages for commonly asked questions:
 
diff --git a/src/content/docs/analytics/faq/other-faqs.mdx b/src/content/docs/analytics/faq/other-faqs.mdx
index 86adb232c817e4d..4e9145ab25ee9ae 100644
--- a/src/content/docs/analytics/faq/other-faqs.mdx
+++ b/src/content/docs/analytics/faq/other-faqs.mdx
@@ -15,8 +15,10 @@ There is a number of different types of traffic which may originate from **CLOUD
 
 Some sources of traffic from ASN13335 include:
 
-- [Workers subrequests](/workers/runtime-apis/fetch/)
-- [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
-- [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
-- [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
-- Other Cloudflare features like [Health Checks](/health-checks/)
+* [Workers subrequests](/workers/runtime-apis/fetch/)
+* [WARP](/warp-client/known-issues-and-faq/#does-warp-reveal-my-ip-address-to-websites-i-visit)
+* [iCloud Private Relay](https://blog.cloudflare.com/icloud-private-relay/) (For reference, iCloud Private Relay’s egress IP addresses are available in this [CSV form](https://mask-api.icloud.com/egress-ip-ranges.csv))
+* [Cloudflare Privacy Proxy](https://blog.cloudflare.com/building-privacy-into-internet-standards-and-how-to-make-your-app-more-private-today/)
+* Other Cloudflare features like [Health Checks](/health-checks/)
+
+
diff --git a/src/content/docs/analytics/faq/wae-faqs.mdx b/src/content/docs/analytics/faq/wae-faqs.mdx
index b88ec97467a6ce7..3693060a2bb2ab8 100644
--- a/src/content/docs/analytics/faq/wae-faqs.mdx
+++ b/src/content/docs/analytics/faq/wae-faqs.mdx
@@ -23,24 +23,29 @@ On the other hand, if you pick a good index that aligns with how you read the da
 
 ### What if I need to index on multiple values?
 
+
 It is possible to concatenate multiple values in your index field. So if you want to index on user ID and hostname, you can write, for example `"$userID:$hostname"` into your index field.
 
 Note that, based on your query pattern, it may make sense to write the same dataset with different indices. It is a common misconception that one should avoid "double-writing" data.
 
 Thanks to sampling, the cost of writing data multiple times can be relatively low. However, reading data inefficiently can result in significant expenses or low-quality results due to sampling.
 
+
 ### How do I know if my data is sampled?
 
 You can use the `_sample_interval` field — again, note that this does not tell you if the results are accurate.
 
 You can tell when data is sampled at read time because sample intervals will be multiples of powers of 10, for example `20` or `700`. There is no hard and fast rule for when sampling starts at read time, but in practice reading longer periods (or more index values) will result in a higher sample interval.
 
+
 ### Why is data missing?
 
+
 Sampling is based largely on the choice of index, as well as other factors like the time range queried and number of indices read. If you are reading from a larger index over a longer time period, and have filtered to a relatively small subgroup within that index, it may not be present due to sampling.
 
 If you need to read accurate results for that subgroup, we suggest that you add that field to your index (refer to [What if I need to index on multiple values](/analytics/faq/wae-faqs/#what-if-i-need-to-index-on-multiple-values)).
 
+
 ### Can I trust sampled data? Are my results accurate?
 
 Sampled data is highly reliable, particularly when a carefully selected index is used.
@@ -51,7 +56,7 @@ In the near future, we plan to expose the [margin of error](https://en.wikipedia
 
 ### How are bursts handled?
 
-Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time. The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
+Equitable sampling exists both to normalize differences between groups, and also to handle large spikes of traffic to a given index. Equalization happens every few seconds; if you are writing many events very close in time, then it is expected that they will be sampled at write time.  The sample interval for a given index will vary from moment to moment, based on the current rate of data being written.
 
 ### How much traffic will trigger sampling?
 
@@ -60,3 +65,5 @@ There is no fixed rule determining when sampling will be triggered.
 We have observed that for workloads like our global CDN, which distribute load around our network, each index value needs about 100 data points per second before sampling is noticeable at all.
 
 Depending on your workload and how you use Workers Analytics Engine, sampling may start at a higher or lower threshold than this. For example, if you are writing out many data points from a single worker execution, it is more likely that your data will be sampled.
+
+
diff --git a/src/content/docs/analytics/graphql-api/errors.mdx b/src/content/docs/analytics/graphql-api/errors.mdx
index aeead71c606fc32..b40d61df3dca927 100644
--- a/src/content/docs/analytics/graphql-api/errors.mdx
+++ b/src/content/docs/analytics/graphql-api/errors.mdx
@@ -13,24 +13,24 @@ The GraphQL Analytics API is a RESTful API based on HTTPS requests and JSON resp
 
 All responses contain an `errors` array, which will be `null` if there are no errors, and include at least one error object if there was an error. Non-null error objects will contain the following fields:
 
-- `message`: a string describing the error.
-- `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
-- `timestamp`: UTC datetime when the error occurred.
+* `message`: a string describing the error.
+* `path`: the nodes associated with the error, starting from the root. Note that the number included in the path array, for example, `0` or `1`, specifies to which zone the error applies; `0` indicates the first zone in the list (or only zone, if only one is being queried).
+* `timestamp`: UTC datetime when the error occurred.
 
 ## Example
 
 ```json
 {
-	"data": null,
-	"errors": [
-		{
-			"message": "cannot request data older than 2678400s",
-			"path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
-			"extensions": {
-				"timestamp": "2019-12-09T21:27:19.195060142Z"
-			}
-		}
-	]
+  "data": null,
+  "errors": [
+    {
+      "message": "cannot request data older than 2678400s",
+      "path": ["viewer", "zones", "0", "firewallEventsAdaptiveGroups"],
+      "extensions": {
+        "timestamp": "2019-12-09T21:27:19.195060142Z"
+      }
+    }
+  ]
 }
 ```
 
@@ -40,8 +40,8 @@ All responses contain an `errors` array, which will be `null` if there are no er
 
 Sample error messages:
 
-- `unable to execute query, please try again later` (HTTP `503`)
-- `too many queries in progress, please try again later` (HTTP `503`)
+* `unable to execute query, please try again later` (HTTP `503`)
+* `too many queries in progress, please try again later` (HTTP `503`)
 
 These messages indicate a temporary server-side issue. The first message typically means the upstream database is unreachable or returned an error. The second message means the server has reached its maximum number of concurrent queries.
 
@@ -51,10 +51,10 @@ Retry the request after a short delay. If the error persists, check the [Cloudfl
 
 Sample error messages:
 
-- `cannot request data older than...` (HTTP `400`)
-- `number of fields can't be more than...` (HTTP `400`)
-- `limit must be positive number and not greater than...` (HTTP `400`)
-- `query time range is too large...` (HTTP `400`)
+* `cannot request data older than...` (HTTP `400`)
+* `number of fields can't be more than...` (HTTP `400`)
+* `limit must be positive number and not greater than...` (HTTP `400`)
+* `query time range is too large...` (HTTP `400`)
 
 These messages indicate that the query exceeds what is allowed for the particular dataset under the current [plan](https://www.cloudflare.com/plans/), and an upgrade should be considered. Refer to [Node limits](/analytics/graphql-api/limits/#node-limits-and-availability) for details.
 
@@ -62,11 +62,11 @@ These messages indicate that the query exceeds what is allowed for the particula
 
 Sample error messages:
 
-- `error parsing args...` (HTTP `400`)
-- `scalar fields must have no selections` (HTTP `400`)
-- `object field must have selections` (HTTP `400`)
-- `unknown field...` (HTTP `400`)
-- `query contains error, please review it and retry` (HTTP `400`)
+* `error parsing args...` (HTTP `400`)
+* `scalar fields must have no selections` (HTTP `400`)
+* `object field must have selections` (HTTP `400`)
+* `unknown field...` (HTTP `400`)
+* `query contains error, please review it and retry` (HTTP `400`)
 
 These messages indicate that the query cannot be processed because it is malformed. Check the query syntax against the [GraphQL schema](/analytics/graphql-api/getting-started/explore-graphql-schema/) and correct the invalid fields or structure.
 
@@ -74,9 +74,9 @@ These messages indicate that the query cannot be processed because it is malform
 
 Sample error messages:
 
-- `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
-- `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
-- `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
+* `rate limiter budget depleted, try again after 5 minutes` (HTTP `429`)
+* `in combination, your request queries too many nodes, zones and accounts` (HTTP `429`)
+* `query consumed excessive resources, please try running smaller queries which consume fewer resources` (HTTP `429`)
 
 These messages indicate the query exceeded rate or resource limits. Reduce the query complexity, the number of zones or accounts per request, or wait before retrying. Refer to the [Limits](/analytics/graphql-api/limits/) section for more details about rate limits.
 
@@ -84,10 +84,10 @@ These messages indicate the query exceeded rate or resource limits. Reduce the q
 
 Sample error messages:
 
-- `Unauthorized` (HTTP `401`)
-- `not authorized for that account` (HTTP `403`)
-- `zones [...] are not authorized` (HTTP `403`)
-- `does not have access to the path...` (HTTP `403`)
+* `Unauthorized` (HTTP `401`)
+* `not authorized for that account` (HTTP `403`)
+* `zones [...] are not authorized` (HTTP `403`)
+* `does not have access to the path...` (HTTP `403`)
 
 An `Unauthorized` response means the API token or bearer token is missing, expired, or invalid. Verify that you are passing a valid token in the `Authorization` header.
 
@@ -97,6 +97,6 @@ A `403` response means the token does not have the required permissions for the
 
 Sample error message:
 
-- `Internal server error` (HTTP `500`)
+* `Internal server error` (HTTP `500`)
 
 This is a generic error indicating an unexpected failure. If it persists, contact [Cloudflare Support](https://support.cloudflare.com/) with the full request and response, including the `Ray-ID` header from the HTTP response.
diff --git a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
index 4900a64e4e2b8ff..2def716afc95aff 100644
--- a/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
+++ b/src/content/docs/analytics/graphql-api/features/confidence-intervals.mdx
@@ -9,14 +9,14 @@ products:
   - graphql-api
 ---
 
-Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time.
+Confidence intervals help assess accuracy and quantify uncertainty in results from sampled datasets. When querying sum or count fields on adaptive datasets, you can request a confidence interval to understand the possible range around an estimate. For example, specifying a confidence level of `0.95` returns the estimate, along with the range of values that likely contains the true value 95% of the time. 
 
 ## Availability
 
 - **Supported datasets**: Adaptive (sampled) datasets only.
 - **Supported fields**: All `sum` and `count` fields.
-- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`).
-- **Default**: If no confidence level is specified, intervals are not returned.
+- **Usage**: Confidence `level` must be provided as a decimal between 0 and 1 (for example,`0.90`, `0.95`, `0.99`). 
+- **Default**: If no confidence level is specified, intervals are not returned. 
 
 ## Usage example
 
@@ -28,35 +28,35 @@ To request a confidence interval, use the `confidence(level: X)` argument in you
 
 ```graphql graphql-api-explorer title="A GraphQL query"
 query SingleDatasetWithConfidence($zoneTag: string, $start: Time, $end: Time) {
-	viewer {
-		zones(filter: { zoneTag: $zoneTag }) {
-			firewallEventsAdaptiveGroups(
-				filter: { datetime_gt: $start, datetime_lt: $end }
-				limit: 1000
-			) {
-				count
-				avg {
-					sampleInterval
-				}
-				confidence(level: 0.95) {
-					count {
-						estimate
-						lower
-						upper
-						sampleSize
-					}
-				}
-			}
-		}
-	}
+  viewer {
+    zones(filter: {zoneTag: $zoneTag}) {
+      firewallEventsAdaptiveGroups(
+        filter: {datetime_gt: $start, datetime_lt: $end}
+        limit: 1000
+      ) {
+        count
+        avg {
+          sampleInterval
+        }
+        confidence(level: 0.95) {
+          count {
+            estimate
+            lower
+            upper
+            sampleSize
+          }
+        }
+      }
+    }
+  }
 }
 ```
 
 ### Response
 
-The response includes the following values:
+The response includes the following values: 
 
-- `estimate`: The estimated value, based on sampled data.
+- `estimate`: The estimated value, based on sampled data. 
 - `lower`: The lower bound of the confidence interval.
 - `sampleSize`: The number of sampled data points used to calculate the estimate.
 - `upper`: The upper bound of the confidence interval.
@@ -65,30 +65,30 @@ In this example, the interpretation of the response is that, based on a sample o
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"firewallEventsAdaptiveGroups": [
-						{
-							"avg": {
-								"sampleInterval": 1.0720277625205972
-							},
-							"confidence": {
-								"count": {
-									"estimate": 42939,
-									"lower": 42673.44115335711,
-									"sampleSize": 40054,
-									"upper": 43204.55884664289
-								}
-							},
-							"count": 42939
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "firewallEventsAdaptiveGroups": [
+            {
+              "avg": {
+                "sampleInterval": 1.0720277625205972
+              },
+              "confidence": {
+                "count": {
+                  "estimate": 42939,
+                  "lower": 42673.44115335711,
+                  "sampleSize": 40054,
+                  "upper": 43204.55884664289
+                }
+              },
+              "count": 42939
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
diff --git a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
index d7db4d153f586f2..74c6b40c78266f7 100644
--- a/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/discovery/index.mdx
@@ -13,4 +13,5 @@ GraphQL API supports [introspection][1] to explore nodes and provides a way to
 retrieve the user's [limits][2] for every node.
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
+
 [2]: /analytics/graphql-api/features/discovery/settings/
diff --git a/src/content/docs/analytics/graphql-api/features/index.mdx b/src/content/docs/analytics/graphql-api/features/index.mdx
index 39fea17f29b3b37..7b85fab58b64d62 100644
--- a/src/content/docs/analytics/graphql-api/features/index.mdx
+++ b/src/content/docs/analytics/graphql-api/features/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The GraphQL Analytics API offers the following features:
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
index c6a25630a2aedd7..0e458b325ede871 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/graphql-client-headers.mdx
@@ -17,13 +17,13 @@ products:
    ![Editing HTTP Headers Window](~/assets/images/analytics/GraphiQL-edit-http-headers-window.png)
 
 3. Select **Add Header** to configure authentication. You can use Cloudflare Analytics API token authentication (recommended) or Cloudflare API key authentication.
-   - **Token authentication**:
+   * **Token authentication**:
 
      Enter **Authorization** in the **Header Name** field, and enter `Bearer {your-analytics-token}` in the **Header value** field, then select **Save**.
 
      ![Editing HTTP Headers](~/assets/images/analytics/GraphiQL-edit-http-headers-token.png)
 
-   - **Key authentication**:
+   * **Key authentication**:
 
      Enter `X-AUTH-EMAIL` in the **Header name** field and your email address registered with Cloudflare in the **Header value** field, and select **Save**.<br/>
 
@@ -36,8 +36,10 @@ products:
 
 :::note[Note]
 
+
 The right-side response pane is empty when you enter your information correctly. An error displays when there are problems with your header credentials.
 
+
 :::
 
 Now that you have configured authentication, you are ready to run queries using GraphiQL.
diff --git a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
index 1e96ffce7142c4b..ed75b1965e7c919 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/authentication/index.mdx
@@ -15,40 +15,30 @@ To secure access to your GraphQL Analytics data, use a Cloudflare API key or tok
 
 This table outlines the differences between Cloudflare API keys and tokens:
 
+
+
 <table>
-	<thead>
-		<tr>
-			<th>Authentication Method</th>
-			<th>Description</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>
-				<a href="/fundamentals/api/get-started/create-token/">API Tokens</a>
-			</td>
-			<td>
-				Cloudflare recommends API Tokens as the preferred way to interact with
-				Cloudflare APIs. You can configure the scope of tokens to limit access
-				to account and zone resources, and you can define the Cloudflare APIs to
-				which the token authorizes access.
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/fundamentals/api/get-started/keys/">API Keys</a>
-			</td>
-			<td>
-				<p>
-					Unique to each Cloudflare user and used only for authentication. API
-					keys do not authorize access to accounts or zones.
-				</p>
-				<p>Use the Global API Key for authentication.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+      <tr>
+          <th>Authentication Method</th>
+          <th>Description</th>
+      </tr>
+  </thead>
+  <tbody>
+      <tr>
+        <td><a href='/fundamentals/api/get-started/create-token/'>API Tokens</a></td>
+        <td>Cloudflare recommends API Tokens as the preferred way to interact with Cloudflare APIs. You can configure the scope of tokens to limit access to account and zone resources, and you can define the Cloudflare APIs to which the token authorizes access.</td>
+      </tr>
+      <tr>
+        <td><a href='/fundamentals/api/get-started/keys/'>API Keys</a></td>
+        <td><p>Unique to each Cloudflare user and used only for authentication. API keys do not authorize access to accounts or zones.</p>
+        <p>Use the Global API Key for authentication.</p></td>
+      </tr>
+  </tbody>
 </table>
 
+
+
 To create and configure GraphQL Analytics API tokens, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
 
 To find and retrieve API keys, as well as edit HTTP headers for authentication in GraphiQL, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
diff --git a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
index 4494649d7315149..1839c3f0876e56b 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
@@ -28,11 +28,13 @@ Click on the editing pane of GraphiQL and add this base query, replacing
 
 :::note[Note]
 
+
 To find the zone's tag, log in to your Cloudflare account and select the site for
 which you want to obtain the tag. In the Cloudflare dashboard **Overview** page,
 scroll to the **API** section in the right sidebar, which displays your zone and
 account tags.
 
+
 :::
 
 To assist query building, the GraphiQL client has word completion. Insert your
@@ -126,16 +128,29 @@ This example query uses the `zoneTag` query variable to represent the zone ID:
 ![Example of GraphiQL query variables][14]
 
 [1]: /analytics/graphql-api/getting-started/querying-basics/
+
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
+
 [3]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
+
 [4]: ~/assets/images/analytics/graphiql-base-query.png
+
 [5]: ~/assets/images/analytics/graphiql-word-completion.png
+
 [6]: ~/assets/images/analytics/graphiql-set-up-base-query.png
+
 [7]: ~/assets/images/analytics/graphiql-parameters.png
+
 [8]: ~/assets/images/analytics/graphiql-filter-fields.png
+
 [9]: ~/assets/images/analytics/graphiql-filter-values.png
+
 [10]: ~/assets/images/analytics/graphiql-set-up-base-query.png
+
 [11]: ~/assets/images/analytics/graphiql-return-fields.png
+
 [12]: ~/assets/images/analytics/graphiql-query-return-field-values.png
+
 [13]: ~/assets/images/analytics/create-query-fw-data-set-play.png
+
 [14]: ~/assets/images/analytics/graphiql-query-variables.png
diff --git a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
index b1eeb322c398cb7..ab3680fa9a78abb 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/execute-graphql-query.mdx
@@ -24,8 +24,8 @@ query:
 
 ```json title="A payload structure for GraphQL API"
 {
-	"query": "{viewer { ... }}",
-	"variables": {}
+  "query": "{viewer { ... }}",
+  "variables": {}
 }
 ```
 
diff --git a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
index e77cba62457a8e1..0d2d0e248a08cf0 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/explore-graphql-schema.mdx
@@ -79,7 +79,7 @@ query.
 
 For example, `zones` can take a filter of `ZoneFilter_InputObject` type as an
 argument. To view the fields available to filter, select
-**ZoneFilter_InputObject**.
+**ZoneFilter\_InputObject**.
 
 ## Find the datasets available for a zone
 
@@ -122,18 +122,33 @@ The list of fields displays:
 For more information on using GraphiQL, please visit this [guide][16].
 
 [1]: /analytics/graphql-api/features/discovery/introspection/
+
 [2]: https://github.com/graphql/graphiql/tree/main/packages/graphiql#readme
+
 [3]: https://altairgraphql.dev/#download
+
 [4]: /analytics/graphql-api/getting-started/authentication/graphql-client-headers/
+
 [5]: ~/assets/images/analytics/graphiql-docs-link.png
+
 [6]: ~/assets/images/analytics/graphiql-doc-explorer.png
+
 [7]: ~/assets/images/analytics/graphiql-doc-explorer-query-mutations.png
+
 [8]: ~/assets/images/analytics/graphiql-doc-explorer-view-cost.png
+
 [9]: ~/assets/images/analytics/graphiql-doc-explorer-viewer-fields.png
+
 [10]: ~/assets/images/analytics/graphiql-doc-explorer-zones.png
+
 [11]: ~/assets/images/analytics/graphiql-doc-explorer-zone-fields.png
+
 [12]: ~/assets/images/analytics/graphiql-doc-explorer-find-firewall.png
+
 [13]: ~/assets/images/analytics/graphiql-doc-explorer-firewallevents-definition.png
+
 [14]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-type-definition.png
+
 [15]: ~/assets/images/analytics/graphiql-doc-explorer-firewall-fields.png
+
 [16]: /analytics/graphql-api/getting-started/compose-graphql-query/
diff --git a/src/content/docs/analytics/graphql-api/getting-started/index.mdx b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
index 6b82273dfd942ef..2ba6111561b125e 100644
--- a/src/content/docs/analytics/graphql-api/getting-started/index.mdx
+++ b/src/content/docs/analytics/graphql-api/getting-started/index.mdx
@@ -9,19 +9,19 @@ products:
   - graphql-api
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Use these articles to get started with the Cloudflare GraphQL API:
 
-- [Authentication][1] - walks you through the options and the steps required to
+* [Authentication][1] - walks you through the options and the steps required to
   set up your access to Cloudflare API successfully,
-- [Querying basics][2] - brings simple query examples for you to start exploring
+* [Querying basics][2] - brings simple query examples for you to start exploring
   the GraphQL API,
-- [Introspect the GraphQL schema][3] - explains how-to surf the schema with
+* [Introspect the GraphQL schema][3] - explains how-to surf the schema with
   GraphQL client,
-- [Create a query in a GraphQL client][4] - describes how to build and run a
+* [Create a query in a GraphQL client][4] - describes how to build and run a
   query against the Cloudflare GraphQL API in the GraphQL clients,
-- [Use curl to query the GraphQL API][5] - walks you through running a query
+* [Use curl to query the GraphQL API][5] - walks you through running a query
   against the Cloudflare GraphQL API from the command line.
 
 For examples of how to build your own GraphQL Analytics dashboard and query
@@ -29,13 +29,17 @@ specific information, such as Firewall and Workers events, please refer to
 [Tutorials][6].
 
 :::note[Data unavailability: Customer Metadata Boundary configuration]
-
-<Render file="customer_metadata_boundary_error" product="analytics" />
+ <Render file="customer_metadata_boundary_error" product="analytics" /> 
 :::
 
 [1]: /analytics/graphql-api/getting-started/authentication/
+
 [2]: /analytics/graphql-api/getting-started/querying-basics/
+
 [3]: /analytics/graphql-api/getting-started/explore-graphql-schema/
+
 [4]: /analytics/graphql-api/getting-started/compose-graphql-query/
+
 [5]: /analytics/graphql-api/getting-started/execute-graphql-query/
+
 [6]: /analytics/graphql-api/tutorials/
diff --git a/src/content/docs/analytics/graphql-api/limits.mdx b/src/content/docs/analytics/graphql-api/limits.mdx
index 41bac079ca31cd6..5adcc44092add47 100644
--- a/src/content/docs/analytics/graphql-api/limits.mdx
+++ b/src/content/docs/analytics/graphql-api/limits.mdx
@@ -19,16 +19,16 @@ plans.
 To support this variety of products, Cloudflare GraphQL API has three layers of
 limits:
 
-- global limits
-- user limits
-- node (dataset) limits
+* global limits
+* user limits
+* node (dataset) limits
 
 ## Global limits
 
 These limits are applied to every query for every plan:
 
-- A zone-scoped query can include up to **10 zones**
-- An account-scoped query can include only **1 account**
+* A zone-scoped query can include up to **10 zones**
+* An account-scoped query can include only **1 account**
 
 Additionally, there is a limited number of queries you can make per request. The total number of queries in a request is equal to the number of zone/account scopes, multiplied by the number of nodes to which they are applied.
 
@@ -46,10 +46,10 @@ the Cloudflare API](/fundamentals/api/reference/limits/).
 
 Each data node has its limits, such as:
 
-- how far back in time can data be requested,
-- the maximum time period (in seconds) that can be requested in one query,
-- the maximum number of fields that can be requested in one query,
-- the maximum number of records that can be returned in one query.
+* how far back in time can data be requested,
+* the maximum time period (in seconds) that can be requested in one query,
+* the maximum number of fields that can be requested in one query,
+* the maximum number of records that can be returned in one query.
 
 Node limits are tied to requested `zoneTag` or `accountTag`. Higher plans have
 access to a greater selection of datasets or fields, and can query over broader historical
diff --git a/src/content/docs/analytics/graphql-api/mcp-server.mdx b/src/content/docs/analytics/graphql-api/mcp-server.mdx
index 79aea053b1121fa..be3bc98608dc365 100644
--- a/src/content/docs/analytics/graphql-api/mcp-server.mdx
+++ b/src/content/docs/analytics/graphql-api/mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the GraphQL Analytics MCP server.
 products:
   - analytics
   - graphql-api
----
+---
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
index a0cd2058706d926..4255d116dd9db69 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/index.mdx
@@ -17,8 +17,8 @@ If you are currently using the deprecated `httpRequests1mByColoGroups` or `httpR
 
 If you are currently using the Zone Analytics API, the following guide will help you migrate your queries to the new GraphQL Analytics API:
 
-- [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
-- [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
+* [Zone Analytics to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics/)
+* [Zone Analytics Colos Endpoint to GraphQL Analytics](/analytics/graphql-api/migration-guides/zone-analytics-colos/)
 
 ## Network Analytics migrations
 
diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
index cfec218853327ed..f6c3398fe285308 100644
--- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
+++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/schema-map.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: reference
 title: NAv1 to NAv2 schema map
 sidebar:
diff --git a/src/content/docs/analytics/graphql-api/sampling.mdx b/src/content/docs/analytics/graphql-api/sampling.mdx
index 2dcf4bdf7261ff2..ce5299faa9407b8 100644
--- a/src/content/docs/analytics/graphql-api/sampling.mdx
+++ b/src/content/docs/analytics/graphql-api/sampling.mdx
@@ -38,11 +38,15 @@ Cloudflare almost always uses **adaptive sampling**, which means the sample rate
 
 The following data nodes are based on fixed sampling, where the sample rate does not vary:
 
+
+
 | Data set                                                                                                                                       |   Rate | Notes                                                                                                                                                                                                |
 | :--------------------------------------------------------------------------------------------------------------------------------------------- | -----: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Firewall Rules Preview<br /><p><b>Nodes:</b><br />`firewallRulePreviewGroups`</p>                                                              |     1% | Use with caution. A 1% sample rate does not provide accurate estimates for datasets smaller than a certain threshold, a scenario the Cloudflare dashboard calls out explicitly but the API does not. |
 | Network Analytics<br /><p><b>Nodes:</b><br />`ipFlows1mGroups`<br />`ipFlows1hGroups`<br />`ipFlows1dGroups`<br />`ipFlows1mAttacksGroups`</p> | 0.012% | Sampling rate is in terms of packet count (1 of every 8,192 packets).                                                                                                                                |
 
+
+
 ## Access to raw data
 
 Because sampling is primarily adaptive and automatically adjusts to provide an accurate estimate, the sampling rate cannot be directly controlled. Enterprise customers have access to raw data via Cloudflare Logs.
diff --git a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
index b7bf522c3840234..c74285316775d50 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/end-customer-analytics.mdx
@@ -54,107 +54,107 @@ The returned results will be in JSON format (as requested), so piping the output
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"httpRequestsAdaptiveGroups": [
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-21T10:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19849385,
-								"visits": 4383
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-21T06:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20607204,
-								"visits": 4375
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-26T05:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20170839,
-								"visits": 4519
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-23T08:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20141860,
-								"visits": 4448
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-25T15:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 21070367,
-								"visits": 4469
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-28T08:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19200774,
-								"visits": 4345
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-26T02:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20758067,
-								"visits": 4502
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-20T19:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 22127811,
-								"visits": 4443
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-27T15:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 20480644,
-								"visits": 4268
-							}
-						},
-						{
-							"dimensions": {
-								"datetimeHour": "2022-07-27T17:00:00Z"
-							},
-							"sum": {
-								"edgeResponseBytes": 19885704,
-								"visits": 4287
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "httpRequestsAdaptiveGroups": [
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-21T10:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19849385,
+                "visits": 4383
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-21T06:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20607204,
+                "visits": 4375
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-26T05:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20170839,
+                "visits": 4519
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-23T08:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20141860,
+                "visits": 4448
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-25T15:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 21070367,
+                "visits": 4469
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-28T08:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19200774,
+                "visits": 4345
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-26T02:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20758067,
+                "visits": 4502
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-20T19:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 22127811,
+                "visits": 4443
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-27T15:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 20480644,
+                "visits": 4268
+              }
+            },
+            {
+              "dimensions": {
+                "datetimeHour": "2022-07-27T17:00:00Z"
+              },
+              "sum": {
+                "edgeResponseBytes": 19885704,
+                "visits": 4287
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
@@ -162,13 +162,13 @@ The returned results will be in JSON format (as requested), so piping the output
 
 We are going to use the GraphQL Analytics API to query the top 10 consuming URLs from a zone, helping you identify the URLs with the highest resource usage. Here are some configuration instructions:
 
-- To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
-- Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
-- Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
-- To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
-  - `CURRENTDATE=$(gdate -u +'%FT%TZ')`
-  - `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
-- For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
+* To filter on a specific hostname, add the line `"clientRequestHTTPHost": "'$2'"` below `"requestSource"`."
+* Replace `API_TOKEN` with your generated API token using the `Read all resources` permissions. The script will only access zones available to the token's creator.
+* Pass the zone ID (`zoneTag`) as a parameter `ARG=$1`.
+* To calculate the current date and the date from 30 days ago, use `gdate` on Mac:
+  * `CURRENTDATE=$(gdate -u +'%FT%TZ')`
+  * `OLDDATE=$(gdate -d '-30 days' -u +'%FT%TZ')`.
+* For specific dates within the last 30 days, set `CURRENTDATE` and `OLDDATE` variables in the format `"YYYY-MM-DDTHH:MM:SSZ"`.
 
 ### API call
 
@@ -196,4 +196,4 @@ https://api.cloudflare.com/client/v4/graphql \
 }' | jq -r 'try .data.viewer.zones[].topPaths[] | "\"\(.dimensions.metric)\": \(.sum.edgeResponseBytes)"' | sort
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/index.mdx b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
index ebcfb6d0cf8b7b2..baf7496c1ef4723 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/index.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/index.mdx
@@ -11,7 +11,7 @@ products:
   - graphql-api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The following resources will help you start exploring your data and creating analytics dashboards:
 
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
index 7f0e232f641a485..4fbbc812304c501 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx
@@ -15,9 +15,9 @@ The following API call will request logs for a single Access login event and out
 
 You will need to insert your `<CLOUDFLARE_ACCOUNT_TAG>`, your API credentials in `<API_TOKEN>`[^1], and substitute your own values for the following variables:
 
-- `rayID`: A unique identifier assigned to the authentication request.
-- `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
-- `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
+* `rayID`: A unique identifier assigned to the authentication request.
+* `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022).
+* `datetimeEnd`: The latest event time to query. Be sure to specify a time range that includes the login event you are querying.
 
 ## API Call
 
@@ -65,47 +65,47 @@ https://api.cloudflare.com/client/v4/graphql \
 
 :::note
 
-Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`.
+Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/features/filtering/) by any other field in the query such as `userUuid` or `deviceId`. 
 :::
 
 ## Response
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"accounts": [
-				{
-					"accessLoginRequestsAdaptiveGroups": [
-						{
-							"dimensions": {
-								"approvingPolicyId": "",
-								"cfRayId": "744927037ce06d68",
-								"country": "US",
-								"datetime": "2022-09-02T20:56:27Z",
-								"deviceId": "",
-								"hasExistingJWT": 0,
-								"hasGatewayEnabled": 0,
-								"hasWarpEnabled": 0,
-								"identityProvider": "nonidentity",
-								"ipAddress": "2a09:bac0:15::814:7b37",
-								"isSuccessfulLogin": 0,
-								"mtlsCertSerialId": "",
-								"mtlsCommonName": "",
-								"mtlsStatus": "NONE",
-								"serviceTokenId": "",
-								"userUuid": ""
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "accounts": [
+        {
+          "accessLoginRequestsAdaptiveGroups": [
+            {
+              "dimensions": {
+                "approvingPolicyId": "",
+                "cfRayId": "744927037ce06d68",
+                "country": "US",
+                "datetime": "2022-09-02T20:56:27Z",
+                "deviceId": "",
+                "hasExistingJWT": 0,
+                "hasGatewayEnabled": 0,
+                "hasWarpEnabled": 0,
+                "identityProvider": "nonidentity",
+                "ipAddress": "2a09:bac0:15::814:7b37",
+                "isSuccessfulLogin": 0,
+                "mtlsCertSerialId": "",
+                "mtlsCommonName": "",
+                "mtlsStatus": "NONE",
+                "serviceTokenId": "",
+                "userUuid": ""
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
 You can compare the query results to your Access policies to understand why a user was blocked. For example, if your application requires a valid mTLS certificate, Access blocked the request shown above because `mtlsStatus`, `mtlsCommonName`, and `mtlsCertSerialId` are empty.
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
index 3e8f9dde667b2df..ccd12acea299f70 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx
@@ -65,74 +65,74 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"emailRoutingAdaptive": [
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:51:25Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "John <john@email.example.com>",
-							"id": "AfWyaZ7V1TAH",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "How are you doing?",
-							"to": "me@example.com"
-						},
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:30:00Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "eBay <ebay@ebay.co.uk>",
-							"id": "aYPegrIfLWia",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "New offers",
-							"to": "me@example.com"
-						},
-						{
-							"action": "forward",
-							"arc": "none",
-							"datetime": "2026-01-19T10:29:59Z",
-							"dkim": "pass",
-							"dmarc": "pass",
-							"errorDetail": "",
-							"from": "Notification <notifications@example.com>",
-							"id": "nWIl9gs95mY3",
-							"isNDR": 0,
-							"isSpam": 0,
-							"messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
-							"spamScore": 0,
-							"spamThreshold": 5,
-							"spf": "pass",
-							"status": "delivered",
-							"subject": "You're over quota",
-							"to": "me@example.com"
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "emailRoutingAdaptive": [
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:51:25Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "John <john@email.example.com>",
+              "id": "AfWyaZ7V1TAH",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<9e6574f1-97f8-4060-ad62-c54b6408ac3f@local>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "How are you doing?",
+              "to": "me@example.com"
+            },
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:30:00Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "eBay <ebay@ebay.co.uk>",
+              "id": "aYPegrIfLWia",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<1A513C40-F2CD808A928-029BBE999993-0000000000FA8855@starship>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "New offers",
+              "to": "me@example.com"
+            },
+            {
+              "action": "forward",
+              "arc": "none",
+              "datetime": "2026-01-19T10:29:59Z",
+              "dkim": "pass",
+              "dmarc": "pass",
+              "errorDetail": "",
+              "from": "Notification <notifications@example.com>",
+              "id": "nWIl9gs95mY3",
+              "isNDR": 0,
+              "isSpam": 0,
+              "messageId": "<0AB8F1C3-3015EDF2980-019BBE9B58F2-0000000000FA7C4D@local>",
+              "spamScore": 0,
+              "spamThreshold": 5,
+              "spf": "pass",
+              "status": "delivered",
+              "subject": "You're over quota",
+              "to": "me@example.com"
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
@@ -176,114 +176,114 @@ The results returned will be in JSON (as requested):
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"zones": [
-				{
-					"emailRoutingAdaptiveGroups": [
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T11:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T12:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T13:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T14:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T15:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T16:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T17:00:00Z"
-							}
-						},
-						{
-							"count": 3,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T18:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-18T22:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T01:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T02:00:00Z"
-							}
-						},
-						{
-							"count": 4,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T05:00:00Z"
-							}
-						},
-						{
-							"count": 1,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T08:00:00Z"
-							}
-						},
-						{
-							"count": 5,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T09:00:00Z"
-							}
-						},
-						{
-							"count": 6,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T10:00:00Z"
-							}
-						},
-						{
-							"count": 2,
-							"dimensions": {
-								"datetimeHour": "2026-01-19T11:00:00Z"
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "zones": [
+        {
+          "emailRoutingAdaptiveGroups": [
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T11:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T12:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T13:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T14:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T15:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T16:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T17:00:00Z"
+              }
+            },
+            {
+              "count": 3,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T18:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-18T22:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T01:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T02:00:00Z"
+              }
+            },
+            {
+              "count": 4,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T05:00:00Z"
+              }
+            },
+            {
+              "count": 1,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T08:00:00Z"
+              }
+            },
+            {
+              "count": 5,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T09:00:00Z"
+              }
+            },
+            {
+              "count": 6,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T10:00:00Z"
+              }
+            },
+            {
+              "count": 2,
+              "dimensions": {
+                "datetimeHour": "2026-01-19T11:00:00Z"
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
-[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
+[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions.
\ No newline at end of file
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
index 3d4c56d42ef286d..deab15ea91ace34 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-endpoint-healthcheck-results.mdx
@@ -9,9 +9,8 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-endpoint-health-checks"
+<Render file="graphql/query-magic-transit-endpoint-health-checks"
 	product="networking-services"
 />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
index 0c1fc135106eaa8..727a62e37b0ac21 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx
@@ -9,10 +9,8 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
-	params={{ productName: "Magic Transit or Cloudflare WAN" }}
-/>
+	params={{ productName: "Magic Transit or Cloudflare WAN" }} />
diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
index 7e2d5a042de9744..3ed3c1e2b7fce50 100644
--- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
+++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx
@@ -9,10 +9,9 @@ products:
   - magic-transit
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
 	params={{ productName: "Magic Transit or Cloudflare WAN" }}
 />
diff --git a/src/content/docs/analytics/index.mdx b/src/content/docs/analytics/index.mdx
index 7f6b64667dccaec..8c9eca78825e740 100644
--- a/src/content/docs/analytics/index.mdx
+++ b/src/content/docs/analytics/index.mdx
@@ -11,52 +11,38 @@ products:
   - analytics
 ---
 
-import { Feature, RelatedProduct } from "~/components";
+import { Feature, RelatedProduct } from "~/components"
 
 Cloudflare visualizes the metadata collected by our products in the Cloudflare dashboard. Refer to [Types of analytics](/analytics/types-of-analytics/) for more information about the various types of analytics and where they exist in the dashboard.
 
----
+***
 
 ## Features
 
 <Feature header="Workers Analytics Engine" href="/analytics/analytics-engine/">
-	Send unlimited-cardinality data from your Worker to a time-series database.
-	Query it with SQL.
+Send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL. 
 </Feature>
 
-<Feature
-	header="Account and zone analytics"
-	href="/analytics/account-and-zone-analytics/"
->
-	Provides details about the requests and traffic related to your Cloudflare
-	accounts and zones.
+<Feature header="Account and zone analytics" href="/analytics/account-and-zone-analytics/">
+Provides details about the requests and traffic related to your Cloudflare accounts and zones. 
 </Feature>
 
-<Feature
-	header="Cloudflare Network Analytics"
-	href="/analytics/network-analytics/"
->
-	Provides near real-time visibility into network and transport-layer traffic
-	patterns and DDoS attacks.
+<Feature header="Cloudflare Network Analytics" href="/analytics/network-analytics/">
+Provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. 
 </Feature>
 
 <Feature header="GraphQL Analytics API" href="/analytics/graphql-api/">
-	Provides all of your performance, security, and reliability data from one
-	endpoint. Select exactly what you need, from one metric for a domain to
-	multiple metrics aggregated for your account.
+Provides all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account. 
 </Feature>
 
----
+***
 
 ## Related products
 
 <RelatedProduct header="Workers" href="/workers/" product="workers">
-	Cloudflare Workers allows developers to build serverless applications and
-	deploy instantly across the globe for exceptional performance, reliability,
-	and scale.
+Cloudflare Workers allows developers to build serverless applications and deploy instantly across the globe for exceptional performance, reliability, and scale. 
 </RelatedProduct>
 
 <RelatedProduct header="Logs" href="/logs/" product="logs">
-	Detailed logs that contain metadata generated by Cloudflare products helpful
-	for debugging, identifying configuration adjustments, and creating analytics.
+Detailed logs that contain metadata generated by Cloudflare products helpful for debugging, identifying configuration adjustments, and creating analytics. 
 </RelatedProduct>
diff --git a/src/content/docs/analytics/network-analytics/configure/index.mdx b/src/content/docs/analytics/network-analytics/configure/index.mdx
index 16e7bfa95e54afc..960840cbc5deb03 100644
--- a/src/content/docs/analytics/network-analytics/configure/index.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/network-analytics/configure/share-export.mdx b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
index 4f80063b389f3a8..ebfbca66506210a 100644
--- a/src/content/docs/analytics/network-analytics/configure/share-export.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/share-export.mdx
@@ -11,7 +11,7 @@ products:
   - analytics
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 ## Share Network Analytics filters
 
diff --git a/src/content/docs/analytics/network-analytics/configure/time-range.mdx b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
index 4cad33741de7676..f22f93aa5d6e373 100644
--- a/src/content/docs/analytics/network-analytics/configure/time-range.mdx
+++ b/src/content/docs/analytics/network-analytics/configure/time-range.mdx
@@ -17,7 +17,7 @@ Use the timeframe drop-down list to change the time range over which Network Ana
 
 In the Network Analytics dashboard, the range of historical data you can query is 112 days.
 
-When you select _Previous 30 minutes_, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A _Live_ notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
+When you select *Previous 30 minutes*, the **Network Analytics** card will show the data from the last 30 minutes, refreshing every 20 seconds. A *Live* notification appears next to the statistic drop-down list to let you know that the view keeps updating automatically:
 
 ![Timeframe drop-down with Previous 30 minutes selected.](~/assets/images/analytics/network-analytics/timeframe-selector.png)
 
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
index 72d38cdbd6e45a7..e8908c5bbfc3b1e 100644
--- a/src/content/docs/analytics/network-analytics/index.mdx
+++ b/src/content/docs/analytics/network-analytics/index.mdx
@@ -12,7 +12,7 @@ products:
   - analytics
 ---
 
-import { InlineBadge, Render } from "~/components";
+import { InlineBadge, Render } from "~/components"
 
 Cloudflare Network Analytics (version 2) provides near real-time visibility into network and transport-layer traffic patterns and DDoS attacks. Network Analytics visualizes packet and bit-level data, the same data available via the Network Analytics dataset of the GraphQL Analytics API.
 
@@ -22,12 +22,12 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
 
 ## Remarks
 
-- The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
+* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
 
-- The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
+* The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
 
 ## Related resources
 
-- [Cloudflare GraphQL API](/analytics/graphql-api/)
-- [Cloudflare Logpush](/logs/logpush/)
-- [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
+* [Cloudflare GraphQL API](/analytics/graphql-api/)
+* [Cloudflare Logpush](/logs/logpush/)
+* [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
\ No newline at end of file
diff --git a/src/content/docs/analytics/network-analytics/reference/index.mdx b/src/content/docs/analytics/network-analytics/reference/index.mdx
index 50a9131063634e7..bfaf9377cbe9497 100644
--- a/src/content/docs/analytics/network-analytics/reference/index.mdx
+++ b/src/content/docs/analytics/network-analytics/reference/index.mdx
@@ -13,7 +13,7 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review reference information about Cloudflare Network Analytics:
 
diff --git a/src/content/docs/analytics/network-analytics/understand/index.mdx b/src/content/docs/analytics/network-analytics/understand/index.mdx
index 6bbfaed1b7957b3..364ff4458dc64da 100644
--- a/src/content/docs/analytics/network-analytics/understand/index.mdx
+++ b/src/content/docs/analytics/network-analytics/understand/index.mdx
@@ -13,6 +13,6 @@ products:
   - analytics
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/analytics/sampling.mdx b/src/content/docs/analytics/sampling.mdx
index 964b7405a3d5f1a..815514bf77937e5 100644
--- a/src/content/docs/analytics/sampling.mdx
+++ b/src/content/docs/analytics/sampling.mdx
@@ -8,7 +8,7 @@ products:
   - analytics
 ---
 
-[Sampling](<https://en.wikipedia.org/wiki/Sampling_(statistics)>) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
+[Sampling](https://en.wikipedia.org/wiki/Sampling_(statistics)) is a technique used in analytics to analyze a subset of data rather than processing every individual data point. In Cloudflare Analytics, sampling ensures efficient performance and scalability while maintaining high accuracy and reliability. This document provides a comprehensive overview of how sampling works, why it is used, and its impact on analytics across different Cloudflare tools.
 
 ## How sampling works
 
@@ -20,17 +20,17 @@ To make this possible, data is stored at multiple resolutions (100%, 10%, 1%), e
 
 Cloudflare's data pipeline handles [over 700 million events per second](https://blog.cloudflare.com/how-we-make-sense-of-too-much-data) (and growing) across its global network. Processing and storing all this data in real-time would be prohibitively expensive and time-consuming. By leveraging carefully designed sampling methods, Cloudflare Analytics delivers accurate and actionable data, balancing precision with performance.
 
-Sampling enables:
+Sampling enables: 
 
 - **Scalability**: Reduces the volume of data processed without compromising insights.
 - **Performance**: Speeds up query execution for analytics.
 - **Cost-Efficiency**: Minimizes resource usage and storage needs.
 
-## Can I trust sampled data?
+## Can I trust sampled data? 
 
 Sampled data is highly reliable, and can provide insights that are as dependable as those derived from full datasets. Cloudflare designs sampling techniques to ensure we capture the essential characteristics of the entire dataset, delivering results you can trust.
 
-Sampling is an approach similarly used in other domains, for instance:
+Sampling is an approach similarly used in other domains, for instance: 
 
 - Google Maps: Just as online maps display lower-resolution images when zoomed out and higher-resolution images when zoomed in — keeping the total number of pixels relatively constant — Cloudflare Analytics dynamically adjusts sampling rates to efficiently provide insights, ensuring queries return consistent and accurate results regardless of dataset size.
 
@@ -44,26 +44,23 @@ In the near future, we plan to expose confidence intervals along with query resu
 
 ## Additional considerations
 
-**When sampling occurs**
-
+**When sampling occurs** 
 - Sampling is typically applied to very high-traffic datasets where full data analysis would be impractical.
 - For smaller datasets, full data analysis is often performed without sampling.
 
-**Sampling rates**
-
+**Sampling rates** 
 - Sampling rates vary depending on the dataset and product.
 - Cloudflare ensures that sampling rates are consistent within a single dataset to maintain accuracy across queries.
 
-**Impact on metrics**
-
+**Impact on metrics** 
 - While sampling reduces the volume of processed data, aggregated metrics like totals, averages, and percentiles are extrapolated based on the sample size. This ensures the reported metrics represent the entire dataset accurately.
 
 **Limitations**
-
-- Sampling may not capture extremely rare events with very low occurrence rates.
+- Sampling may not capture extremely rare events with very low occurrence rates. 
 
 **Sampling in analytics interfaces**
-
 - GraphQL API: Sampling metadata is included in the query response. For more information, refer to the sampling [GraphQL Analytics API](/analytics/graphql-api/sampling/) documentation.
 - Workers Analytics Engine: For more information, refer to the [Workers Analytics Engine](/analytics/analytics-engine/sampling/) documentation.
 - Dashboard Analytics: Displays an icon with the sampled percentage of data, if sampled data was used for the visualization.
+
+
diff --git a/src/content/docs/analytics/types-of-analytics.mdx b/src/content/docs/analytics/types-of-analytics.mdx
index 9b13d4d6e16b1d5..3754f8a0ce803d1 100644
--- a/src/content/docs/analytics/types-of-analytics.mdx
+++ b/src/content/docs/analytics/types-of-analytics.mdx
@@ -40,24 +40,25 @@ Access aggregated traffic, security, and performance metrics for each domain pro
 
 Data available under the **Analytics & Logs** section includes:
 
-- **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
-- **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
-- **Performance** - Origin Performance, Bandwidth Saved.
-- **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
-- **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
-- **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
-- **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
+* **HTTP Traffic** - Requests, Data transfer, Page views, Visits, and API requests.
+* **Security** - Total Threats, Top Crawlers/Bots, Rate Limiting, Total Threats Stopped.
+* **Performance** - Origin Performance, Bandwidth Saved.
+* **Edge Reachability** - [Last mile insights](/network-error-logging/) for Enterprise customers.
+* **Workers** - [Detailed information](/workers/observability/metrics-and-analytics/) related to your Workers per zone, and Workers KV per account.
+* **Logs** - [Detailed logs](/logs/) of the metadata generated by Cloudflare products for Enterprise customers.
+* **Instant logs** - [Live stream of traffic](/logs/instant-logs/) for your domain. Enterprise customers can access this live stream from the Cloudflare dashboard or from a command-line interface (CLI).
 
 ## Product analytics
 
 Beyond the analytics provided for your properties, you can also access analytics related to specific products:
 
-- [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
-- [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
-- [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
-- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
-- [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
-- [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
+* [Bot Analytics](/bots/bot-analytics/) - Shows which requests are associated with known bots, likely automated traffic, likely human traffic, and more.
+* [Cache Analytics](/cache/performance-review/cache-analytics/) - Insights to that help determine if resources are missing from cache, expired, or ineligible for caching.
+* [DNS Analytics](/dns/additional-options/analytics/) - Provides insights about DNS queries to your zone.
+* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) - Features metrics to help gain insights into traffic load balancer steering decisions.
+* [Security Events](/waf/analytics/security-events/) - Highlights attack and mitigation metrics detected by the Cloudflare WAF and HTTP DDoS protection systems.
+* [Security Analytics](/waf/analytics/security-analytics/) - Displays information about all incoming HTTP requests, including those not affected by security measures (for example, from the WAF and DDoS protection systems).
+
 
 ## GraphQL APIs
 
diff --git a/src/content/docs/api-shield/api-gateway.mdx b/src/content/docs/api-shield/api-gateway.mdx
index 159a13ee168f6ba..7eb6722be62e2c5 100644
--- a/src/content/docs/api-shield/api-gateway.mdx
+++ b/src/content/docs/api-shield/api-gateway.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 7
+
 ---
 
 Cloudflare API Shield provides API security, management tools, and integration with the Cloudflare Developer Platform for building new APIs.
diff --git a/src/content/docs/api-shield/glossary.mdx b/src/content/docs/api-shield/glossary.mdx
index 8cec6bbf2bf209c..f3d2e75924932cd 100644
--- a/src/content/docs/api-shield/glossary.mdx
+++ b/src/content/docs/api-shield/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 9
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's API Shield documentation.
 
diff --git a/src/content/docs/api-shield/index.mdx b/src/content/docs/api-shield/index.mdx
index f95940e11bfbf9e..17d437901096fc5 100644
--- a/src/content/docs/api-shield/index.mdx
+++ b/src/content/docs/api-shield/index.mdx
@@ -11,15 +11,11 @@ head:
     content: Overview
 ---
 
-import {
-	Description,
-	Feature,
-	Plan,
-	RelatedProduct,
-	Render,
-} from "~/components";
+import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
 
-<Description>Identify and address your API vulnerabilities.</Description>
+<Description>
+Identify and address your API vulnerabilities.
+</Description>
 
 <Plan type="ent-add-on" />
 
@@ -41,14 +37,11 @@ Refer to the [Get started](/api-shield/get-started/) guide to set up API Shield.
 ## Features
 
 <Feature header="Security features" href="/api-shield/security/">
-	Secure your APIs using API Shield's security features.
+Secure your APIs using API Shield's security features.
 </Feature>
 
-<Feature
-	header="Management, monitoring, and more"
-	href="/api-shield/management-and-monitoring/"
->
-	Monitor the health of your API endpoints.
+<Feature header="Management, monitoring, and more" href="/api-shield/management-and-monitoring/">
+Monitor the health of your API endpoints.
 </Feature>
 
 ## Availability
@@ -63,11 +56,6 @@ API Shield currently does not work for JDCloud customers.
 
 ## Related products
 
-<RelatedProduct
-	header="DDoS Protection"
-	href="/ddos-protection/"
-	product="ddos-protection"
->
-	Cloudflare DDoS protection secures websites, applications, and entire networks
-	while ensuring the performance of legitimate traffic is not compromised.
+<RelatedProduct header="DDoS Protection" href="/ddos-protection/" product="ddos-protection">
+Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised.
 </RelatedProduct>
diff --git a/src/content/docs/api-shield/management-and-monitoring/index.mdx b/src/content/docs/api-shield/management-and-monitoring/index.mdx
index 166b939d9e38c8e..182cc0cab64e27c 100644
--- a/src/content/docs/api-shield/management-and-monitoring/index.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/index.mdx
@@ -6,10 +6,11 @@ products:
   - api-shield
 sidebar:
   order: 5
-  group:
+  group: 
     hideIndex: true
+
 ---
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
index 34134ffed50f975..7139806c6c0866c 100644
--- a/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
+++ b/src/content/docs/api-shield/management-and-monitoring/session-identifiers.mdx
@@ -6,14 +6,14 @@ products:
 title: Session identifiers
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="session-identifiers" product="api-shield" />
 
 :::note
-
 <Render file="required-session-identifiers" product="api-shield" />
 :::
 
diff --git a/src/content/docs/api-shield/plans.mdx b/src/content/docs/api-shield/plans.mdx
index e54a67a1da3c703..7cba5403983b3bc 100644
--- a/src/content/docs/api-shield/plans.mdx
+++ b/src/content/docs/api-shield/plans.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 3
+
 ---
 
 Free, Pro, Business, and Enterprise customers without an API Shield subscription can access [Endpoint Management](/api-shield/management-and-monitoring/) and [Schema validation](/api-shield/security/schema-validation/), but no other [API Shield](/api-shield/) features.
@@ -14,10 +15,10 @@ To subscribe to API Shield, upgrade to an Enterprise plan and contact your accou
 
 Limits to endpoints apply to Endpoint Management and Schema validation. Refer to the table below for limits based on your zone plan.
 
-| Plan type                         | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action      |
-| --------------------------------- | --------------- | ---------------- | -------------------------- | ---------------- |
-| **Free**                          | 100             | 5                | 200 kB                     | `Block` only     |
-| **Pro**                           | 250             | 5                | 500 kB                     | `Block` only     |
-| **Business**                      | 500             | 10               | 2 MB                       | `Block` only     |
-| **Enterprise without API Shield** | 500             | 10               | 5 MB                       | `Log` or `Block` |
-| **Enterprise with API Shield**    | 10,000          | 10+              | 10+ MB                     | `Log` or `Block` |
+| Plan type | Saved endpoints | Uploaded schemas | Total uploaded schema size | Rule action |
+| --- | --- | --- | --- | --- |
+| **Free** | 100 | 5 | 200 kB | `Block` only |
+| **Pro** | 250 | 5 | 500 kB | `Block` only |
+| **Business** | 500 | 10 | 2 MB | `Block` only |
+| **Enterprise without API Shield** | 500 | 10 | 5 MB | `Log` or `Block` |
+| **Enterprise with API Shield** | 10,000 | 10+ | 10+ MB | `Log` or `Block` |
\ No newline at end of file
diff --git a/src/content/docs/api-shield/reference/classic-schema-validation.mdx b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
index 4fefbda61645691..7e5925a84e6068a 100644
--- a/src/content/docs/api-shield/reference/classic-schema-validation.mdx
+++ b/src/content/docs/api-shield/reference/classic-schema-validation.mdx
@@ -12,9 +12,10 @@ sidebar:
     text: Deprecated
   order: 1
   label: Classic Schema validation
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 :::caution[Deprecation notice]
 Classic Schema validation has been deprecated.
@@ -40,11 +41,14 @@ To configure Schema validation in the Cloudflare dashboard:
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Select **Security** > **API Shield**.
 3. Go to **Schema validation** and select **Add schema**.
-4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the _Hostname_ field — equal to `api.example.com` — and a check for the _URI Path_ field using a regular expression — matching the regex `^/v1`.
-   :::caution[Important]
+4. Enter a descriptive name for your policy and optionally edit the expression to trigger Schema validation. For example, if your API is available at `http://api.example.com/v1`, include a check for the *Hostname* field — equal to `api.example.com` — and a check for the *URI Path* field using a regular expression — matching the regex `^/v1`.
+:::caution[Important]
 
-To validate the hostname, you must include the _Hostname_ field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
-::: 5. Select **Next**. 6. Upload your schema file. 7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
+To validate the hostname, you must include the *Hostname* field explicitly in the rule, even if the hostname value is in the schema file. Any hostname value present in the schema file will be ignored.
+:::
+5. Select **Next**.
+6. Upload your schema file.
+7. Select **Save** to validate the content of the schema file and deploy the Schema validation rule. If you get a validation error, ensure that you are using one of the [supported file formats](/api-shield/security/schema-validation/#specifications) and that each endpoint and method pair has a unique operation ID.
 
 After deploying your API Shield rule, Cloudflare displays a summary of all <GlossaryTooltip term="API endpoint">API endpoints</GlossaryTooltip> organized by their protection level and actions that will occur for non-compliant and unprotected requests.
 
diff --git a/src/content/docs/api-shield/reference/index.mdx b/src/content/docs/api-shield/reference/index.mdx
index e0fb94f82c8316e..d51edc253455ed3 100644
--- a/src/content/docs/api-shield/reference/index.mdx
+++ b/src/content/docs/api-shield/reference/index.mdx
@@ -6,11 +6,12 @@ products:
   - api-shield
 sidebar:
   order: 6
-  group:
+  group: 
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about API Shield:
 
diff --git a/src/content/docs/api-shield/reference/terraform.mdx b/src/content/docs/api-shield/reference/terraform.mdx
index 8e5c5b8d6c3be74..823b0b64274405a 100644
--- a/src/content/docs/api-shield/reference/terraform.mdx
+++ b/src/content/docs/api-shield/reference/terraform.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 tags:
   - Terraform
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Get started with API Shield using Terraform from the examples below. For more information on how to use Terraform with Cloudflare, refer to the [Terraform documentation](/terraform/).
 
@@ -61,7 +62,7 @@ resource "cloudflare_api_shield_operation" "get_image" {
   host     = "example.com"
   endpoint = "/api/images/{var1}"
 }
-
+ 
 resource "cloudflare_api_shield_operation" "post_image" {
   zone_id  = var.zone_id
   method   = "POST"
@@ -74,7 +75,7 @@ resource "cloudflare_api_shield_operation" "post_image" {
 
 :::note
 
-It is required to configure Endpoint Management if you want to set up Schema validation using Terraform.
+It is required to configure Endpoint Management if you want to set up Schema validation using Terraform. 
 :::
 
 Refer to the example configuration below to manage [Schema validation](/api-shield/security/schema-validation/api/) on your zone.
@@ -89,13 +90,13 @@ resource "cloudflare_schema_validation_schemas" "example_schema" {
   source             = file("./schemas/example-schema.yaml")
   validation_enabled = true
 }
-
+ 
 # Block all requests that violate schema by default
 resource "cloudflare_schema_validation_settings" "zone_level_settings" {
   zone_id                              = var.zone_id
   validation_default_mitigation_action = "block"
 }
-
+ 
 # For endpoint post_image - only log requests that violate schema
 resource "cloudflare_schema_validation_operation_settings" "post_image_log_only" {
   zone_id           = var.zone_id
diff --git a/src/content/docs/api-shield/security/graphql-protection/index.mdx b/src/content/docs/api-shield/security/graphql-protection/index.mdx
index 6d8f7feb449ca0d..c8c4dfc16b03dd8 100644
--- a/src/content/docs/api-shield/security/graphql-protection/index.mdx
+++ b/src/content/docs/api-shield/security/graphql-protection/index.mdx
@@ -6,6 +6,7 @@ products:
   - api-shield
 sidebar:
   order: 5
+
 ---
 
 GraphQL is a query language for APIs. In addition to protecting RESTful APIs, Cloudflare can also protect GraphQL APIs.
diff --git a/src/content/docs/api-shield/security/index.mdx b/src/content/docs/api-shield/security/index.mdx
index 63dde51928c06d0..36a3a3e4120f463 100644
--- a/src/content/docs/api-shield/security/index.mdx
+++ b/src/content/docs/api-shield/security/index.mdx
@@ -6,19 +6,22 @@ products:
   - api-shield
 sidebar:
   order: 4
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
+
 
 Cloudflare offers the following features to help secure your APIs:
 
-| Discovery & management                                                                        | Posture management                                                                 | Runtime protection                                                   |
-| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
-| [API Discovery](/api-shield/security/api-discovery/)                                          | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/)     | [Schema validation](/api-shield/security/schema-validation/)         |
-| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/)             | [JWT validation](/api-shield/security/jwt-validation/)               |
-| [Sequence Analytics](/api-shield/security/sequence-analytics/)                                | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/)     |
-|                                                                                               | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels)  | [Mutual TLS (mTLS)](/api-shield/security/mtls/)                      |
-|                                                                                               | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/)               | [GraphQL query protection](/api-shield/security/graphql-protection/) |
+| Discovery & management | Posture management | Runtime protection |
+| --- | --- | --- |
+| [API Discovery](/api-shield/security/api-discovery/) | [Volumetric Abuse Detection](/api-shield/security/volumetric-abuse-detection/) | [Schema validation](/api-shield/security/schema-validation/) |
+| [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/) | [Authentication Posture](/api-shield/security/authentication-posture/) | [JWT validation](/api-shield/security/jwt-validation/) |
+| [Sequence Analytics](/api-shield/security/sequence-analytics/) | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/) | [Sequence mitigation](/api-shield/security/sequence-mitigation/) |
+| | [Risk labels](/api-shield/management-and-monitoring/endpoint-labels/#risk-labels) | [Mutual TLS (mTLS)](/api-shield/security/mtls/) |
+| | [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) | [GraphQL query protection](/api-shield/security/graphql-protection/) |
+
 
 ## Example Cloudflare solutions
 
@@ -26,23 +29,29 @@ Cloudflare API Shield, together with other Cloudflare products, helps protect yo
 
 The following table maps each OWASP vulnerability to the Cloudflare features that address it:
 
-| OWASP issue                                     | Example Cloudflare solution                                                                                                                                                                                                             |
-| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| OWASP issue                                     | Example Cloudflare solution                                                                                                                            |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Broken Object Level Authorization               | [BOLA vulnerability detection](/api-shield/security/bola-vulnerability-detection/), [Sequence mitigation], [Schema validation], [JWT validation], [Rate Limiting], [Vulnerability Scanner](/api-shield/security/vulnerability-scanner/) |
 | Broken Authentication                           | [Authentication Posture](/api-shield/security/authentication-posture/), [mTLS](/api-shield/security/mtls/), [JWT validation], [Exposed Credential Checks](/waf/managed-rules/check-for-exposed-credentials/), [Bot Management](/bots/)  |
-| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
-| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                    |
-| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                                                                                                   |
-| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                                                                                                     |
-| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                                                                                                        |
-| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                                                                                                             |
-| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                                                                                                    |
-| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                                                                                                   |
+| Broken Object Property Level Authorization      | [Schema validation], [JWT validation]                                                                                                                  |
+| Unrestricted Resource Consumption               | [Rate Limiting], [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                   |
+| Broken Function Level Authorization             | [Schema validation], [JWT validation]                                                                                                                  |
+| Unrestricted Access to Sensitive Business Flows | [Sequence mitigation], [Bot Management], [GraphQL Query Protection]                                                                                    |
+| Server Side Request Forgery                     | [Schema validation], [WAF managed rules], [WAF custom rules](/waf/custom-rules/)                                                                       |
+| Security Misconfiguration                       | [Sequence mitigation], [Schema validation], [WAF managed rules], [GraphQL Query Protection]                                                            |
+| Improper Inventory Management                   | [Discovery](/api-shield/security/api-discovery/), [Schema learning](/api-shield/management-and-monitoring/#endpoint-schema-learning)                   |
+| Unsafe Consumption of APIs                      | [JWT validation], [WAF managed rules]                                                                                                                  |
 
 [Schema validation]: /api-shield/security/schema-validation/
+
 [Sequence mitigation]: /api-shield/security/sequence-mitigation/
+
 [JWT validation]: /api-shield/security/jwt-validation/
+
 [GraphQL Query Protection]: /api-shield/security/graphql-protection/
+
 [Bot management]: /bots/
+
 [Rate limiting]: /waf/rate-limiting-rules/
+
 [WAF managed rules]: /waf/managed-rules/
diff --git a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
index e37fc920b98921f..412e2ee5573001d 100644
--- a/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/jwt-worker.mdx
@@ -14,7 +14,7 @@ tags:
   - JavaScript
 ---
 
-import { Steps } from "~/components";
+import { Steps } from "~/components"
 
 Use a Worker to automatically keep your identity provider’s latest public key in the JWT validation configuration.
 
diff --git a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
index 69906adc1b47b63..102b9af7bb9bb5e 100644
--- a/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
+++ b/src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx
@@ -13,7 +13,7 @@ tags:
   - JSON web token (JWT)
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 You can forward information from a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) to the origin in a header by creating [Transform Rules](/rules/transform/) using claims that Cloudflare has verified via the JSON Web Token.
 
@@ -44,4 +44,4 @@ As an example, to send the `x-send-jwt-claim-user` request header to the origin,
     lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
     ```
     `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT validation and `claim_name` is the JWT claim you want to add to the header.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/mtls/byo-ca.mdx b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
index 90b2c59cd2ff56e..2430485da76550a 100644
--- a/src/content/docs/api-shield/security/mtls/byo-ca.mdx
+++ b/src/content/docs/api-shield/security/mtls/byo-ca.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/client-certificates/byo-ca/
 sidebar:
   order: 3
+
 ---
diff --git a/src/content/docs/api-shield/security/mtls/index.mdx b/src/content/docs/api-shield/security/mtls/index.mdx
index c7984dc34ab21f2..6652a44adef3c34 100644
--- a/src/content/docs/api-shield/security/mtls/index.mdx
+++ b/src/content/docs/api-shield/security/mtls/index.mdx
@@ -8,6 +8,7 @@ sidebar:
   order: 7
 tags:
   - mTLS
+
 ---
 
 import { GlossaryDefinition, Render } from "~/components";
diff --git a/src/content/docs/api-shield/security/sequence-analytics.mdx b/src/content/docs/api-shield/security/sequence-analytics.mdx
index c70bf1c1ef13f37..34a24e55bdceb85 100644
--- a/src/content/docs/api-shield/security/sequence-analytics.mdx
+++ b/src/content/docs/api-shield/security/sequence-analytics.mdx
@@ -6,9 +6,10 @@ products:
 title: Sequence Analytics
 sidebar:
   order: 3
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Sequence Analytics tracks the order of API endpoint requests over time, allowing you to discover how users interact with your API. Sequence Analytics groups and highlights important user journeys (sequences) across your API. You can enforce preferred sequences using [Sequence mitigation](/api-shield/security/sequence-mitigation/).
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
index 33320b54ef171ed..c3bf0a409084cde 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/api.mdx
@@ -10,23 +10,24 @@ sidebar:
 head:
   - tag: title
     content: Configure sequence mitigation via the API
+
 ---
 
 Configuring sequence mitigation via the API consists of building a rule object by choosing the sequence and setting the type of rule and its action.
 
 ```json title="Example of a rule object"
 {
-	"id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
-	"title": "<RULE_TITLE>",
-	"kind": "allow",
-	"action": "block",
-	"sequence": [
-		"0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
-		"b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
-	],
-	"priority": 0,
-	"last_updated": "2023-07-24T12:06:51.796286Z",
-	"created_at": "2023-07-24T12:06:51.796286Z"
+    "id": "d4909253-390f-4956-89fd-92a5b0cd86d8",
+    "title": "<RULE_TITLE>",
+    "kind": "allow",
+    "action": "block",
+    "sequence": [
+     "0d9bf70c-92e1-4bb3-9411-34a3bcc59003",
+     "b704ab4d-5be0-46e0-9875-b2b3d1ab42f9"
+    ],
+    "priority": 0,
+    "last_updated": "2023-07-24T12:06:51.796286Z",
+    "created_at": "2023-07-24T12:06:51.796286Z"
 }
 ```
 
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
index 5d43aabef5e991b..08a2a8da0c12da5 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx
@@ -7,14 +7,14 @@ products:
 sidebar:
   order: 4
   label: Custom rules
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
 
 These rules are similar to [cookie sequence rules](/bots/additional-configurations/sequence-rules/) but have a different set of prerequisites:
-
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.
 - Because they require session identifiers, they can only be used on traffic that can be clearly attributed to individual users through session identifiers (authenticated traffic).
 - Because Cloudflare stores the user state in memory and not in a cookie, a session's sequence lifetime is limited to 10 minutes.
@@ -25,7 +25,6 @@ Rules built using these custom rules are similar to the sequence rules that can
 ## Availability
 
 :::note
-
 <Render file="sequence-mitigation-availability" product="api-shield" />
 :::
 
@@ -42,30 +41,30 @@ Each saved endpoint will have an endpoint ID visible in its details page in Endp
 The visitor must wait more than 2 seconds after requesting endpoint `aaaaaaaa` before requesting endpoint `bbbbbbbb`:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and
+cf.sequence.current_op eq "bbbbbbbb" and 
 cf.sequence.msec_since_op["aaaaaaaa"] ge 2000
 ```
 
 The visitor must request endpoints `aaaaaaaa`, then `bbbbbbbb`, then `cccccccc` in that exact order:
 
 ```txt
-cf.sequence.current_op eq "cccccccc" and
-cf.sequence.previous_ops[0] == "bbbbbbbb" and
+cf.sequence.current_op eq "cccccccc" and 
+cf.sequence.previous_ops[0] == "bbbbbbbb" and 
 cf.sequence.previous_ops[1] == "aaaaaaaa"
 ```
 
 The visitor must request endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, but endpoint `aaaaaaaa` can be anywhere in the previous 10 requests:
 
 ```txt
-cf.sequence.current_op eq "bbbbbbbb" and
+cf.sequence.current_op eq "bbbbbbbb" and 
 any(cf.sequence.previous_ops[*] == "aaaaaaaa")
 ```
 
 The visitor must request either endpoint `aaaaaaaa` before endpoint `bbbbbbbb`, or endpoint `cccccccc` before endpoint `bbbbbbbb`:
 
 ```txt
-(cf.sequence.current_op eq "bbbbbbbb" and
-any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or
-(cf.sequence.current_op eq "bbbbbbbb" and
+(cf.sequence.current_op eq "bbbbbbbb" and 
+any(cf.sequence.previous_ops[*] == "aaaaaaaa")) or 
+(cf.sequence.current_op eq "bbbbbbbb" and 
 any(cf.sequence.previous_ops[*] == "cccccccc"))
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
index 7672a8fafa6039f..184e0fe3410c88c 100644
--- a/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
+++ b/src/content/docs/api-shield/security/sequence-mitigation/index.mdx
@@ -6,9 +6,10 @@ products:
   - api-shield
 sidebar:
   order: 4
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 Sequence mitigation allows you to enforce request patterns for authenticated clients communicating with your API.
 
@@ -29,7 +30,7 @@ Using sequence mitigation, you can enforce that request pattern with two new seq
 
 :::note
 
-You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/).
+You can create sequence mitigation rules for a sequence even if the sequence is not listed in [Sequence Analytics](/api-shield/security/sequence-analytics/). 
 :::
 
 ## Process
@@ -53,6 +54,7 @@ A negative security model may be useful if you see abusive behavior that is outs
 
 For example, if there was an authorization bug that allowed users to iterate through other users' profiles that contain account numbers via `GET /api/v1/users/{var1}/profile` and then a user tries to make fraudulent funds transfers, you could create a rule to block or log the sequence `GET /api/v1/users/{var1}/profile` to `POST /api/v1/transferFunds`.
 
+
 ## Limitations
 
 ### Endpoint Management
@@ -85,4 +87,4 @@ For example, if you create a rule requiring one endpoint to be requested before
 
 ## Availability
 
-<Render file="sequence-mitigation-availability" product="api-shield" />
+<Render file="sequence-mitigation-availability" product="api-shield" />
\ No newline at end of file
diff --git a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
index 4b6e8f08729bae2..ac20b0d38774fb5 100644
--- a/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
+++ b/src/content/docs/api-shield/security/volumetric-abuse-detection.mdx
@@ -6,9 +6,10 @@ products:
 title: Volumetric Abuse Detection
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components";
+import { GlossaryTooltip, Steps, Render, APIRequest } from "~/components"
 
 Cloudflare Volumetric Abuse Detection generates per-endpoint, per-session rate limit recommendations that adjust automatically as your traffic patterns change.
 
@@ -26,7 +27,7 @@ Volumetric Abuse Detection rate limits are a way to prevent blatant volumetric a
 
 Volumetric Abuse Detection analyzes your API's individual session traffic statistics to recommend per-endpoint, per-session rate limits.
 
-To access your endpoints:
+To access your endpoints: 
 
 Old dashboard: **Security** > **API Shield** > **Endpoint Management**
 
@@ -46,7 +47,7 @@ Thresholds are suggested only for endpoints that satisfy all of the following re
 
 After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in the Cloudflare dashboard.
 
-### Rate limiting recommendation calculation
+### Rate limiting recommendation calculation 
 
 Select an endpoint row in **Endpoints** to view its rate limit recommendation. The detail view shows the overall recommended value and percentile-based values (p50, p90, p99).
 
@@ -72,8 +73,8 @@ Refer to the [Rules documentation](/waf/rate-limiting-rules/create-zone-dashboar
 [Rate limit recommendations are available via the API](/api/resources/api_gateway/subresources/operations/methods/get/) if you would like to dynamically update rate limits over time.
 
 <APIRequest
-	path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
-	method="GET"
+  path="/zones/{zone_id}/api_gateway/operations/{operation_id}"
+  method="GET"
 />
 
 ## Special cases
diff --git a/src/content/docs/argo-smart-routing/analytics.mdx b/src/content/docs/argo-smart-routing/analytics.mdx
index 8ba08d6be3c3f77..73046eae32ef933 100644
--- a/src/content/docs/argo-smart-routing/analytics.mdx
+++ b/src/content/docs/argo-smart-routing/analytics.mdx
@@ -22,15 +22,18 @@ You can access Argo analytics for your domain in the [Cloudflare dashboard](http
 
 :::note
 
+
 Detailed performance data within **Origin Performance (Argo)** will only display if Argo has routed at least 500 origin requests within the last 48 hours.
 
+
 :::
 
 ## Types of analytics
 
 The dashboard displays two different views for performance data:
 
-- **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
+* **Origin Response Time**: A histogram shows response time from your origin to the Cloudflare network. The blue bars show time-to-first-byte (TTFB) without Argo, while the orange bars show TTFB where Argo found a Smart Route.
+
+* **Geography**: A map shows the improvement in response time at each Cloudflare data center.
 
-- **Geography**: A map shows the improvement in response time at each Cloudflare data center.
-  - A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
+  * A negative value indicates that requests from that location would not have benefited from Argo Smart Routing, so instead would have been routed directly.
diff --git a/src/content/docs/argo-smart-routing/argo-for-packets.mdx b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
index b2e857fe5dca3da..8d4a1b15407b0ce 100644
--- a/src/content/docs/argo-smart-routing/argo-for-packets.mdx
+++ b/src/content/docs/argo-smart-routing/argo-for-packets.mdx
@@ -6,6 +6,7 @@ products:
   - argo-smart-routing
 sidebar:
   order: 4
+
 ---
 
 Argo for Packets optimizes IP layer network routing for Cloudflare network services products, including [Magic Transit](/magic-transit/), [Cloudflare WAN](/cloudflare-wan/) (formerly Magic WAN), and [Cloudflare for Offices](https://blog.cloudflare.com/cloudflare-for-offices/).
diff --git a/src/content/docs/artifacts/api/errors.mdx b/src/content/docs/artifacts/api/errors.mdx
index 467365dbf5b37c7..7545813cd7cbfa2 100644
--- a/src/content/docs/artifacts/api/errors.mdx
+++ b/src/content/docs/artifacts/api/errors.mdx
@@ -15,17 +15,17 @@ This is a list of Artifacts errors.
 
 ## Error codes
 
-| Name                   | Code  | Description                                                               |
-| ---------------------- | ----- | ------------------------------------------------------------------------- |
-| `ALREADY_EXISTS`       | 10201 | The target repository already exists in the namespace.                    |
-| `NOT_FOUND`            | 10200 | The repository or remote resource does not exist.                         |
-| `IMPORT_IN_PROGRESS`   | 10302 | The repository is still being imported and is not yet available.          |
-| `FORK_IN_PROGRESS`     | 10303 | The repository is still being forked and is not yet available.            |
-| `INVALID_INPUT`        | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
-| `INVALID_REPO_NAME`    | 10101 | The repository name does not meet naming requirements.                    |
-| `INVALID_TTL`          | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds).       |
-| `INVALID_URL`          | 10104 | The source URL does not point to a valid git repository.                  |
-| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication.                            |
-| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached.                               |
-| `MEMORY_LIMIT`         | 10402 | The operation exceeds service memory limits.                              |
-| `INTERNAL_ERROR`       | 10400 | An unexpected internal error occurred.                                    |
+| Name | Code | Description |
+|------|------|-------------|
+| `ALREADY_EXISTS` | 10201 | The target repository already exists in the namespace. |
+| `NOT_FOUND` | 10200 | The repository or remote resource does not exist. |
+| `IMPORT_IN_PROGRESS` | 10302 | The repository is still being imported and is not yet available. |
+| `FORK_IN_PROGRESS` | 10303 | The repository is still being forked and is not yet available. |
+| `INVALID_INPUT` | 10100 | A request parameter is missing, malformed, or outside the accepted range. |
+| `INVALID_REPO_NAME` | 10101 | The repository name does not meet naming requirements. |
+| `INVALID_TTL` | 10103 | The token TTL is outside the allowed range (60–31,536,000 seconds). |
+| `INVALID_URL` | 10104 | The source URL does not point to a valid git repository. |
+| `REMOTE_AUTH_REQUIRED` | 10106 | The remote repository requires authentication. |
+| `UPSTREAM_UNAVAILABLE` | 10401 | The remote git server could not be reached. |
+| `MEMORY_LIMIT` | 10402 | The operation exceeds service memory limits. |
+| `INTERNAL_ERROR` | 10400 | An unexpected internal error occurred. |
diff --git a/src/content/docs/artifacts/api/git-protocol.mdx b/src/content/docs/artifacts/api/git-protocol.mdx
index df3348a7a33e084..0b2fe497d2755c8 100644
--- a/src/content/docs/artifacts/api/git-protocol.mdx
+++ b/src/content/docs/artifacts/api/git-protocol.mdx
@@ -20,10 +20,10 @@ Use the returned repo `remote` with a regular Git client for `clone`, `fetch`, `
 
 Git routes accept repo access tokens in two forms:
 
-| Format                             | Details                                                                                                                              | Example                                                                                                      |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
+| Format                             | Details                                                                                                                               | Example                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
 | Bearer token in `http.extraHeader` | Recommended for local workflows. Use the full token string returned by the control plane and keep credentials out of the remote URL. | `git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone` |
-| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`                  |
+| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<ACCOUNT_ID>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`               |
 
 ### Token format
 
diff --git a/src/content/docs/artifacts/concepts/repositories.mdx b/src/content/docs/artifacts/concepts/repositories.mdx
index c00cad8531dd358..026597faaae63d4 100644
--- a/src/content/docs/artifacts/concepts/repositories.mdx
+++ b/src/content/docs/artifacts/concepts/repositories.mdx
@@ -30,11 +30,11 @@ Each repository is isolated from other repositories. Tokens, lifecycle, refs, an
 
 Artifacts exposes the same repository through three interfaces:
 
-| Interface       | What you use it for                                                                | What it returns                                                        |
-| --------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker         | Repository metadata, repository handles, and repo-scoped token results |
-| REST API        | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results    |
-| Git protocol    | Clone, fetch, pull, and push repository contents                                   | Standard Git behavior over HTTPS                                       |
+| Interface | What you use it for | What it returns |
+| --- | --- | --- |
+| Workers binding | Create, list, import, inspect, fork, delete, and mint tokens from a Worker | Repository metadata, repository handles, and repo-scoped token results |
+| REST API | Create, list, import, inspect, fork, delete, and mint tokens from external systems | Cloudflare API responses with repository metadata and token results |
+| Git protocol | Clone, fetch, pull, and push repository contents | Standard Git behavior over HTTPS |
 
 These interfaces point to the same repository.
 
diff --git a/src/content/docs/artifacts/examples/git-client.mdx b/src/content/docs/artifacts/examples/git-client.mdx
index 10a023272838435..a297d94fb81bf26 100644
--- a/src/content/docs/artifacts/examples/git-client.mdx
+++ b/src/content/docs/artifacts/examples/git-client.mdx
@@ -11,11 +11,10 @@ products:
 You can use a standard Git client to interact with Artifacts repos. This example walks through clone, but the same approach works for fetch, pull, push, and any other Git operation.
 
 To do this, you need to:
-
 - Fetch the repo's remote URL from the REST API
 - Mint a short-lived token scoped to that repo
 
-Once you have the remote URL and token, you can use them to run Git commands against the repo.
+Once you have the remote URL and token, you can use them to run Git commands against the repo. 
 
 This example assumes the repo already exists and that you have a [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 
@@ -50,13 +49,11 @@ ARTIFACTS_TOKEN=$(printf '%s' "$TOKEN_JSON" | jq -r '.result.plaintext')
 # Clone the repo
 git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone
 ```
-
 You now have a standard Git checkout in `./artifacts-clone`.
 
 This flow is useful when another system owns repo discovery or access control, but your local tooling still expects a normal git remote.
 
 ### Authentication
-
 Treat `ARTIFACTS_TOKEN` as a secret. Keep it out of logs, and prefer `http.extraHeader` over saving credentials in a remote URL.
 
 If you need a self-contained remote URL for a short-lived workflow, extract the token secret and build the authenticated remote only for that command:
diff --git a/src/content/docs/artifacts/guides/authentication.mdx b/src/content/docs/artifacts/guides/authentication.mdx
index b700afb4e8e3481..ac4559e2184b237 100644
--- a/src/content/docs/artifacts/guides/authentication.mdx
+++ b/src/content/docs/artifacts/guides/authentication.mdx
@@ -16,11 +16,11 @@ Review [Namespaces](/artifacts/concepts/namespaces/) first, then use one namespa
 
 ## Compare auth methods
 
-| Interface       | Authenticate with                                   | Permissions or scopes                                                                   | Use for                                |
-| --------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------- |
-| Workers binding | Configured `artifacts` binding                      | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`.           | Worker code that calls `env.ARTIFACTS` |
-| REST API        | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests            |
-| Git protocol    | Repo-scoped Artifacts token                         | `read` for clone, fetch, and pull. `write` for push.                                    | Standard Git over HTTPS                |
+| Interface | Authenticate with | Permissions or scopes | Use for |
+| --- | --- | --- | --- |
+| Workers binding | Configured `artifacts` binding | Wrangler auth is only for local Wrangler commands such as `dev` and `deploy`. | Worker code that calls `env.ARTIFACTS` |
+| REST API | Cloudflare API token in `Authorization: Bearer ...` | **Artifacts** > **Read** for read routes and **Artifacts** > **Edit** for write routes. | Control-plane HTTP requests |
+| Git protocol | Repo-scoped Artifacts token | `read` for clone, fetch, and pull. `write` for push. | Standard Git over HTTPS |
 
 Cloudflare API tokens authenticate control-plane access. Repo-scoped Artifacts tokens authenticate Git access.
 
@@ -79,10 +79,10 @@ curl --request POST "$ARTIFACTS_BASE_URL/repos" \
 
 Git uses repo-scoped Artifacts tokens, not Cloudflare API tokens. Mint these tokens from the Workers binding or the REST API, then use them with the repo `remote` URL.
 
-| Token scope | Allowed commands                                 |
-| ----------- | ------------------------------------------------ |
-| `read`      | `git clone`, `git fetch`, `git pull`             |
-| `write`     | `git clone`, `git fetch`, `git pull`, `git push` |
+| Token scope | Allowed commands |
+| --- | --- |
+| `read` | `git clone`, `git fetch`, `git pull` |
+| `write` | `git clone`, `git fetch`, `git pull`, `git push` |
 
 Use the exact repo `remote` value returned by the Workers binding or REST API:
 
diff --git a/src/content/docs/artifacts/guides/event-subscriptions.mdx b/src/content/docs/artifacts/guides/event-subscriptions.mdx
index 08ff7f6771fca2b..8b1184706241f3d 100644
--- a/src/content/docs/artifacts/guides/event-subscriptions.mdx
+++ b/src/content/docs/artifacts/guides/event-subscriptions.mdx
@@ -13,7 +13,6 @@ import { Render } from "~/components";
 Artifacts emits structured events for repository lifecycle changes — creates, deletes, forks, imports, pushes, clones, fetches, and token changes. By subscribing to these events through [event subscriptions](/queues/event-subscriptions/), you can consume them from a Worker to build commit-driven automation.
 
 For example:
-
 - Run custom workflows when a repository is created or imported
 - Kick off a build and deploy a change when an agent pushes to a repo
 - Trigger a review agent on every push
diff --git a/src/content/docs/artifacts/platform/limits.mdx b/src/content/docs/artifacts/platform/limits.mdx
index b328482a34c0687..75154c57881d70c 100644
--- a/src/content/docs/artifacts/platform/limits.mdx
+++ b/src/content/docs/artifacts/platform/limits.mdx
@@ -15,9 +15,9 @@ These limits cover naming rules, storage, and request rates for control-plane an
 | Feature                        | Limit                                                                                              |
 | ------------------------------ | -------------------------------------------------------------------------------------------------- |
 | Control-plane request rate     | 2,000 requests per 10 seconds per Artifacts namespace                                              |
-| Git request rate, per artifact | 2,000 requests per 10 seconds per artifact                                                         |
+| Git request rate, per artifact     | 2,000 requests per 10 seconds per artifact                                                             |
 | Maximum storage per repository | 10 GB                                                                                              |
 | Maximum storage per account    | 1 TB (can be raised on request)                                                                    |
-| Maximum number of repositories | Unlimited                                                                                          |
+| Maximum number of repositories | Unlimited                                 |
 | Maximum number of namespaces   | Unlimited                                                                                          |
 | Namespace and repo names       | Start with a letter or digit. Remaining characters may include letters, digits, `.`, `_`, and `-`. |
diff --git a/src/content/docs/artifacts/platform/pricing.mdx b/src/content/docs/artifacts/platform/pricing.mdx
index 6986d8c6160294c..8cca99c4745119f 100644
--- a/src/content/docs/artifacts/platform/pricing.mdx
+++ b/src/content/docs/artifacts/platform/pricing.mdx
@@ -15,10 +15,10 @@ Artifacts pricing is billed on two dimensions:
 
 ## Artifacts pricing
 
-| Unit                          | Workers Free | Workers Paid                                                   |
-| ----------------------------- | ------------ | -------------------------------------------------------------- |
-| Operations (1,000 operations) | Unavailable  | First 10,000 per month + $0.15 per additional 1,000 operations |
-| Storage (GB-mo)               | Unavailable  | First 1 GB per month + $0.50 per additional GB-mo              |
+| Unit                          | Workers Free | Workers Paid |
+| ----------------------------- | ------------ | ------------ |
+| Operations (1,000 operations) | Unavailable | First 10,000 per month + $0.15 per additional 1,000 operations |
+| Storage (GB-mo)               | Unavailable | First 1 GB per month + $0.50 per additional GB-mo |
 
 ## Storage usage
 
diff --git a/src/content/docs/automatic-platform-optimization/about/index.mdx b/src/content/docs/automatic-platform-optimization/about/index.mdx
index 8e08942f6c504ec..8a627ee1adac90b 100644
--- a/src/content/docs/automatic-platform-optimization/about/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/index.mdx
@@ -6,6 +6,7 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 2
+
 ---
 
 With Automatic Platform Optimization (APO), Cloudflare serves your entire site from our edge network, ensuring customers see improved performance when visiting your site. Cloudflare typically only caches static content, but with APO, we can also cache dynamic content — like HTML — to serve the entire site from the cache. This process removes round trips from the origin to drastically improve time to first byte (TTFB) along with other site performance metrics. In addition to caching dynamic content, APO caches third-party scripts to further reduce the number of requests that leave Cloudflare's edge network.
diff --git a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
index c63c3dc4fdccb0f..3b36da43020bcd5 100644
--- a/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/plugin-compatibility.mdx
@@ -16,33 +16,35 @@ For questions about a specific plugin not shown in the list, create a thread in
 
 :::note
 
+
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
+
 :::
 
 ## Compatible plugins
 
-- [NitroPack](https://nitropack.io/)
-- [FlyingPress](https://flyingpress.com/)
-- [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
-- [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
-- [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
-- [WooCommerce](https://wordpress.org/plugins/woocommerce/)
-- [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
-- [Object Cache Pro](https://objectcache.pro)
-- [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
-- [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
-- [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
-- [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
-- [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
-- [WPTouch](https://wordpress.org/plugins/wptouch/)
-- [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
-- [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
-- [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
-- [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
-- [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
-- [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
-- [WPML](https://wpml.org/)
-- [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
-- [Imunify360](https://docs.imunify360.com/features/#webshield)
-- [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
+* [NitroPack](https://nitropack.io/)
+* [FlyingPress](https://flyingpress.com/)
+* [WP Rocket](https://community.cloudflare.com/t/cloudflares-apo-with-wp-rockets-minified-css/225906/3?u=yevgen) **version 3.8.6 or later**
+* [BigCommerce](https://wordpress.org/plugins/bigcommerce/)
+* [Easy Digital Downloads](https://wordpress.org/plugins/easy-digital-downloads/)
+* [WooCommerce](https://wordpress.org/plugins/woocommerce/)
+* [Redis Object Cache](https://wordpress.org/plugins/redis-cache/)
+* [Object Cache Pro](https://objectcache.pro)
+* [YITH WooCommerce Wishlist](https://wordpress.org/plugins/yith-woocommerce-wishlist/)
+* [WP EasyCart](https://wordpress.org/plugins/wp-easycart/)
+* [Ecwid Ecommerce Shopping Cart](https://wordpress.org/plugins/ecwid-shopping-cart/)
+* [WP ECommerce](https://wordpress.org/plugins/wp-e-commerce/)
+* [Bookly](https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/)
+* [WPTouch](https://wordpress.org/plugins/wptouch/)
+* [Mobile Detect](https://wordpress.org/plugins/tinywp-mobile-detect/)
+* [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/)
+* [WP-Mobilizer](https://wordpress.org/plugins/wp-mobilizer/)
+* [Any Mobile Theme Switcher](https://wordpress.org/plugins/any-mobile-theme-switcher/)
+* [Easy Social Share Buttons](https://codecanyon.net/item/easy-social-share-buttons-for-wordpress/6394476)
+* [Jetpack (Mobile Theme)](https://wordpress.org/plugins/jetpack/)
+* [WPML](https://wpml.org/)
+* [Hummingbird](https://wordpress.org/plugins/hummingbird-performance/)
+* [Imunify360](https://docs.imunify360.com/features/#webshield)
+* [Perfmatters](https://perfmatters.io/docs/cloudflare-wordpress-settings/)
diff --git a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
index e4df722b4bb5ebb..05c85a5ea866629 100644
--- a/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
+++ b/src/content/docs/automatic-platform-optimization/about/test-current-speed.mdx
@@ -6,6 +6,7 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 3
+
 ---
 
 Before you begin using APO, we recommend testing your current site speed. Your site speed results give your website a letter grade and performance rating.
diff --git a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
index 422ecb4f5989b1b..e2ba71bfc3a0ea6 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/change-nameservers.mdx
@@ -33,6 +33,8 @@ We recommend keeping this browser tab or window open and opening a new tab or wi
 
 :::note
 
+
 You may be prompted to confirm the nameserver change with your domain registrar. Confirm or continue after making the update.
 
+
 :::
diff --git a/src/content/docs/automatic-platform-optimization/get-started/index.mdx b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
index 1ec49c17ce68232..27e95e4ce57100a 100644
--- a/src/content/docs/automatic-platform-optimization/get-started/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/get-started/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with APO
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Before you configure APO for your WordPress site, complete the following tasks.
 
diff --git a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
index 710c8af46eb1aa8..a8148c2c7bbb2e6 100644
--- a/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/cache-device-type.mdx
@@ -12,9 +12,9 @@ sidebar:
 
 APO cache by device type provides all of the same benefits of Cloudflare's cache while targeting visitors with content appropriate to their device. Cloudflare evaluates the `User-Agent` header in the HTTP request to identify the device type. Cloudflare then identifies each device type with a case insensitive match to the regex below:
 
-- **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
-- **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
-- **Desktop**: Everything else not matched above.
+* **Mobile**: `(?:phone|windows\s+phone|ipod|blackberry|(?:android|bb\d+|meego|silk|googlebot) .+? mobile|palm|windows\s+ce|opera mini|avantgo|mobilesafari|docomo|kaios)`
+* **Tablet**: `(?:ipad|playbook|(?:android|bb\d+|meego|silk)(?! .+? mobile))`
+* **Desktop**: Everything else not matched above.
 
 To enable caching by device type, enable the setting from the Cloudflare dashboard's APO card or from the WordPress plugin version 4.4.0 or later.
 
@@ -22,8 +22,10 @@ Once enabled, Cloudflare sends a `CF-Device-Type` HTTP header to your origin wit
 
 :::note
 
+
 Changing Cache By Device Type setting will invalidate Cache.
 
+
 :::
 
 The Cloudflare for WordPress plugin automatically purges all cache variations for updated pages.
diff --git a/src/content/docs/automatic-platform-optimization/reference/index.mdx b/src/content/docs/automatic-platform-optimization/reference/index.mdx
index 14a92784439d41f..d3e472301ede3ee 100644
--- a/src/content/docs/automatic-platform-optimization/reference/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/index.mdx
@@ -6,8 +6,9 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 10
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
index c1f33213a954200..80a3a268e1f1395 100644
--- a/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/page-rule-integration.mdx
@@ -6,20 +6,21 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 12
+
 ---
 
 The following Page Rules can control APO. Any changes to caching via Page Rules require purging the cache for the changes to take effect.
 
 :::caution
 
-Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability.
+Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO due to their enhanced configurability. 
 :::
 
-- **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
+* **Cache Level: Bypass** — APO bypasses pages with response header `cf-apo-via: origin,page-rules`
 
-- **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
+* **Cache Level: Ignore Query String** — APO ignores all query strings when serving from Cache.
 
-- **Cache Level: Cache Everything** — APO caches pages with all query strings.
+* **Cache Level: Cache Everything** — APO caches pages with all query strings.
 
   :::caution
 
@@ -27,10 +28,10 @@ Consider using [Cache Rules](/cache/how-to/cache-rules/) instead to control APO
 
   :::
 
-- **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
+* **Bypass Cache on Cookie (Business and Enterprise plans only)** — APO applies custom bypass cookies in addition to the default list.
 
-- **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
+* **Edge Cache TTL** — APO applies custom Edge TTL instead of 30 days. This page rule is helpful for pages that can generate CAPTCHAs or nonces.
 
-- **Browser Cache TTL** — APO applies custom Browser TTL.
+* **Browser Cache TTL** — APO applies custom Browser TTL.
 
-- `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
+* `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` – Enables users to have detailed control over cache TTLs without using a page rule. For more information on the `CDN-Cache-Control` and `Cloudflare-CDN-Cache-Control` headers, refer to [CDN-Cache-Control](/cache/concepts/cache-control/).
diff --git a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
index 4c26f989a9835bb..d49a44137e07c34 100644
--- a/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/query-parameters.mdx
@@ -16,46 +16,46 @@ To add a query parameter to our allowlist, [create a post in the community](http
 
 APO serves cached content as long as the query parameters in the URL are one of the following:
 
-- `ref`
-- `utm_source`
-- `utm_medium`
-- `utm_campaign`
-- `utm_term`
-- `utm_content`
-- `utm_expid`
-- `fbclid`
-- `fb_action_ids`
-- `fb_action_types`
-- `fb_source`
-- `mc_cid`
-- `mc_eid`
-- `gclid`
-- `dclid`
-- `_ga`
-- `campaignid`
-- `adgroupid`
-- `_ke`
-- `cn-reloaded`
-- `age-verified`
-- `ao_noptimize`
-- `usqp`
-- `mkt_tok`
-- `epik`
-- `ck_subscriber_id`
+* `ref`
+* `utm_source`
+* `utm_medium`
+* `utm_campaign`
+* `utm_term`
+* `utm_content`
+* `utm_expid`
+* `fbclid`
+* `fb_action_ids`
+* `fb_action_types`
+* `fb_source`
+* `mc_cid`
+* `mc_eid`
+* `gclid`
+* `dclid`
+* `_ga`
+* `campaignid`
+* `adgroupid`
+* `_ke`
+* `cn-reloaded`
+* `age-verified`
+* `ao_noptimize`
+* `usqp`
+* `mkt_tok`
+* `epik`
+* `ck_subscriber_id`
 
 ## Cookies prefixes that always bypass cache
 
-- `wp-`
-- `wordpress`
-- `comment_`
-- `woocommerce_`
-- `xf_`
-- `edd_`
-- `jetpack`
-- `yith_wcwl_session_`
-- `yith_wrvp_`
-- `wpsc_`
-- `ecwid`
-- `ec_`
-- `bookly_`
-- `bookly`
+* `wp-`
+* `wordpress`
+* `comment_`
+* `woocommerce_`
+* `xf_`
+* `edd_`
+* `jetpack`
+* `yith_wcwl_session_`
+* `yith_wrvp_`
+* `wpsc_`
+* `ecwid`
+* `ec_`
+* `bookly_`
+* `bookly`
diff --git a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
index c14b25e62e38c9f..c3ac27a754ccf4a 100644
--- a/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
+++ b/src/content/docs/automatic-platform-optimization/reference/subdomain-subdirectories.mdx
@@ -46,10 +46,10 @@ export default {
 		const originalResponse = await fetch(request);
 
 		// Response properties are immutable. To change them, construct a new Response object.
-		const response = new Response(originalResponse.body, originalResponse);
+    const response = new Response(originalResponse.body, originalResponse);
 
-		// Response headers can be modified through the headers `set` method.
-		response.headers.set("cf-edge-cache", "no-cache");
+    // Response headers can be modified through the headers `set` method.
+    response.headers.set("cf-edge-cache", "no-cache");
 
 		return response;
 	},
diff --git a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
index f680125ba5c4689..4f41ab6c0987264 100644
--- a/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
+++ b/src/content/docs/automatic-platform-optimization/troubleshooting/index.mdx
@@ -6,25 +6,28 @@ products:
   - automatic-platform-optimization
 sidebar:
   order: 15
+
 ---
 
 ## WordPress plugin is undetected on Cloudflare dashboard
 
 The WordPress plugin may go undetected on your Cloudflare dashboard for a few reasons.
 
-- Versions older than 3.8.2 of the WordPress plugin are installed.
-  - **Solution:** Install version 4.4.0 of the WordPress plugin.
-- Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
-  - **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
-- WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
-  - **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
+* Versions older than 3.8.2 of the WordPress plugin are installed.
+  * **Solution:** Install version 4.4.0 of the WordPress plugin.
+* Version 3.8.2 of the plugin is installed but existing cache plugins return stale responses, for example, without `cf-edge-cache` header.
+  * **Solution:** Enable APO from the WordPress plugin and purge the cache in the existing cache plugins.
+* WordPress only runs on a subdomain, but WordPress and the WordPress plugin check against the apex domain.
+  * **Solution:** For additional information, see [Subdomains and subdirectories](/automatic-platform-optimization/reference/subdomain-subdirectories/)
 
 If your Cloudflare dashboard cannot detect the WordPress plugin after trying the solutions above, ensure you completed all of the steps listed in [Activate the Cloudflare WordPress plugin](/automatic-platform-optimization/get-started/activate-cf-wp-plugin/).
 
 :::note
 
+
 The Cloudflare APO WordPress plugin does not support multisite WordPress installation.
 
+
 :::
 
 ## WordPress returns stale content
diff --git a/src/content/docs/billing/get-started/create-billing-profile.mdx b/src/content/docs/billing/get-started/create-billing-profile.mdx
index 278be4c84fffc13..db1ff0eccc710d9 100644
--- a/src/content/docs/billing/get-started/create-billing-profile.mdx
+++ b/src/content/docs/billing/get-started/create-billing-profile.mdx
@@ -20,7 +20,7 @@ Customers on an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/co
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**. If no payment method is on file, the dialog opens automatically.
@@ -57,7 +57,7 @@ Optionally, add an additional payment method. Cloudflare automatically retries t
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method**.
diff --git a/src/content/docs/billing/get-started/update-billing-info.mdx b/src/content/docs/billing/get-started/update-billing-info.mdx
index 14d3c82fae104fa..103bc694b8df894 100644
--- a/src/content/docs/billing/get-started/update-billing-info.mdx
+++ b/src/content/docs/billing/get-started/update-billing-info.mdx
@@ -20,7 +20,7 @@ If Cloudflare is unable to process your payment, review [Troubleshooting failed
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Add Payment Method** to add a new method, or **Edit** next to an existing one.
@@ -55,7 +55,7 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Subscriptions** page and open the **Payment methods** panel.
 3. Select **Delete** next to the payment method you want to remove.
@@ -65,9 +65,9 @@ You cannot delete a payment method if a payment fails or if there is an outstand
 
 Two address fields exist on your account:
 
-| Field                              | Where it is used                                                                                                       |
-| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| **Billing profile address**        | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening.                             |
+| Field | Where it is used |
+| --- | --- |
+| **Billing profile address** | Appears as **Bill to** on every invoice. Used for tax calculation and sanctions screening. |
 | **Payment method billing address** | Captured when you add a payment method. Used by the card issuer to authorize each charge. Does not appear on invoices. |
 
 Updating the billing profile address applies to invoices issued after the change. Past invoices keep the address that was on file when they were issued. Updating the billing profile address does not change the address stored on existing payment methods.
@@ -76,7 +76,7 @@ To update the billing profile address:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit** and enter your information.
 3. Review the suggested address in the pop-up window. If the information is correct, select **Confirm**.
@@ -91,7 +91,7 @@ Your billing email address is particularly important if you have [opted into ema
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to **Invoices and documents**.
 3. From **Billing email preference**, select **Change email address**.
@@ -101,13 +101,13 @@ Your billing email address is particularly important if you have [opted into ema
 
 If you added a payment method but did not include a Tax ID, VAT or GST number, you can add or change the Tax ID, VAT or GST number associated with the payment method afterwards.
 
-:::note
+:::note 
 You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, enter your VAT or GST number.
@@ -115,13 +115,13 @@ You cannot apply a VAT or GST number to past invoices. Adding a VAT or GST numbe
 
 ## Remove a Tax ID, VAT, or GST number
 
-:::note
+:::note 
 You cannot remove a VAT or GST number from past invoices. Removing a VAT or GST number will only apply to future invoices issued in the account.
 :::
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. From **Billing Address**, select **Edit**.
 3. In the **VAT/GST** field, delete the VAT or GST number.
diff --git a/src/content/docs/billing/manage/billable-usage.mdx b/src/content/docs/billing/manage/billable-usage.mdx
index 3136309de54ce9b..936144271be0638 100644
--- a/src/content/docs/billing/manage/billable-usage.mdx
+++ b/src/content/docs/billing/manage/billable-usage.mdx
@@ -40,12 +40,12 @@ Hover over any bar to see the per-product cost breakdown for that day.
 
 Below the chart, a sortable table breaks down usage by product for the full billing period.
 
-| Column             | Description                                                                                                                                              |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Product**        | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
-| **Total usage**    | Total metered usage for the billing period, including any free-tier allowance.                                                                           |
-| **Billable usage** | Usage that exceeds the free tier and will be charged.                                                                                                    |
-| **Usage cost**     | Cumulative cost for the product in the selected billing period.                                                                                          |
+| Column | Description |
+| --- | --- |
+| **Product** | The Cloudflare product or service generating the usage charge. Products with a free tier show the included allowance (for example, "First 1M included"). |
+| **Total usage** | Total metered usage for the billing period, including any free-tier allowance. |
+| **Billable usage** | Usage that exceeds the free tier and will be charged. |
+| **Usage cost** | Cumulative cost for the product in the selected billing period. |
 
 Use the **product filter** at the top of the page to narrow the chart and table to specific products.
 
@@ -62,6 +62,8 @@ The dashboard reads from the same data source that generates your monthly invoic
 - Costs reflect the published rate card for your account.
 - The total usage cost shown at the end of a completed billing period matches the usage overage charges on the corresponding invoice.
 
+
+
 ## Set up budget alerts
 
 To get notified when your spend crosses a dollar threshold, you can create budget alerts directly from the dashboard. For detailed instructions, refer to [Budget alerts](/billing/manage/budget-alerts/).
@@ -71,3 +73,4 @@ To get notified when your spend crosses a dollar threshold, you can create budge
 - [Budget alerts](/billing/manage/budget-alerts/) — Get notified when spend crosses a threshold
 - [Usage-based billing](/billing/understand/usage-based-billing/) — Which products use metered billing
 - [How charges accrue](/billing/understand/how-charges-accrue/) — How a request generates charges across products
+
diff --git a/src/content/docs/billing/manage/budget-alerts.mdx b/src/content/docs/billing/manage/budget-alerts.mdx
index c5cf2ff7f15fc1c..0fb4fdd9330e059 100644
--- a/src/content/docs/billing/manage/budget-alerts.mdx
+++ b/src/content/docs/billing/manage/budget-alerts.mdx
@@ -28,12 +28,12 @@ Budget alerts are available to Pay-as-you-go accounts only. Enterprise contract
 5. Select **Create budget alert**.
 6. Configure the alert:
 
-   | Field                      | Description                                                                                                                                                           |
-   | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-   | **Alert name**             | A descriptive name for the alert (for example, "R2 spend warning").                                                                                                   |
-   | **Description**            | _(Optional)_ A note about when this alert should fire.                                                                                                                |
+   | Field | Description |
+   | --- | --- |
+   | **Alert name** | A descriptive name for the alert (for example, "R2 spend warning"). |
+   | **Description** | *(Optional)* A note about when this alert should fire. |
    | **Budget threshold (USD)** | The dollar amount that triggers the alert. When your cumulative usage-based spend for the current billing period crosses this value, Cloudflare sends a notification. |
-   | **Email recipients**       | One or more email addresses to notify. Select **Add email** to add additional recipients.                                                                             |
+   | **Email recipients** | One or more email addresses to notify. Select **Add email** to add additional recipients. |
 
 7. Select **Save**.
 
@@ -54,12 +54,12 @@ From there you can edit or delete existing alerts.
 
 Cloudflare offers two types of spend monitoring:
 
-| Feature            | Budget alerts                                   | Usage notifications                                       |
-| ------------------ | ----------------------------------------------- | --------------------------------------------------------- |
-| **Scope**          | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
-| **Threshold**      | Dollar amount                                   | Product-specific metric (bytes, requests, minutes)        |
-| **Setup location** | **Billing** > **Billable Usage**                | **Notifications**                                         |
-| **Best for**       | Overall cost management                         | Monitoring a single product                               |
+| Feature | Budget alerts | Usage notifications |
+| --- | --- | --- |
+| **Scope** | Account-wide, all usage-based products combined | Per-product (for example, Argo bytes or Workers requests) |
+| **Threshold** | Dollar amount | Product-specific metric (bytes, requests, minutes) |
+| **Setup location** | **Billing** > **Billable Usage** | **Notifications** |
+| **Best for** | Overall cost management | Monitoring a single product |
 
 For per-product usage notifications, refer to [Usage-based billing](/billing/understand/usage-based-billing/#usage-based-billing-notifications).
 
diff --git a/src/content/docs/billing/manage/cancel-subscription.mdx b/src/content/docs/billing/manage/cancel-subscription.mdx
index 5fdf55b5596082d..c80dba8a8bcf6e3 100644
--- a/src/content/docs/billing/manage/cancel-subscription.mdx
+++ b/src/content/docs/billing/manage/cancel-subscription.mdx
@@ -32,17 +32,17 @@ To disable a subscription:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Select the feature you want to disable under **Active Subscriptions** (Free or Pro customers) or **Plan Extensions** (Enterprise customers).
-4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing _Disable_ from a drop-down list.
+4. Follow the instructions to disable the feature. Each feature has a different process which could include toggling a switch, clicking a button, or choosing *Disable* from a drop-down list.
 
 ## Step 2: Cancel the subscription in your billing profile
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Subscriptions**.
 3. Find the subscription you want to disable and select **Cancel**.
diff --git a/src/content/docs/billing/manage/invoices.mdx b/src/content/docs/billing/manage/invoices.mdx
index 43d7879767a806f..ba940ef55e961bd 100644
--- a/src/content/docs/billing/manage/invoices.mdx
+++ b/src/content/docs/billing/manage/invoices.mdx
@@ -12,10 +12,10 @@ import { DashButton } from "~/components";
 
 You will receive an invoice in the **Billing** section of your Cloudflare account when you:
 
-- Change your Cloudflare plan type.
-- Upgrade or downgrade to or from a paid plan.
-- Add a new domain to a Cloudflare account.
-- Enable or renew a subscription or add-on service.
+* Change your Cloudflare plan type.
+* Upgrade or downgrade to or from a paid plan.
+* Add a new domain to a Cloudflare account.
+* Enable or renew a subscription or add-on service.
 
 For any historical invoices not included in the **Billing** section, [contact Cloudflare support](/support/contacting-cloudflare-support/).
 
@@ -29,25 +29,25 @@ To enable Cloudflare invoice emails which are sent when you add or remove subscr
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
-
-2. Select **Invoices & Documents**.
-3. From **Billing email preferences**, toggle the notification switch to **On**.
+    <DashButton url="/?to=/:account/billing" />
+    
+3. Select **Invoices & Documents**.
+4. From **Billing email preferences**, toggle the notification switch to **On**.
 
 After you enable email invoices, you will receive invoices via email:
 
-- Within one business day of initial set-up.
-- Every month at the end of your billing period.
-- Within one business day for all new purchases.
+* Within one business day of initial set-up.
+* Every month at the end of your billing period.
+* Within one business day for all new purchases.
 
 ## Download invoice
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices & Documents**.
-3. Find the invoice you want to download and select the icon next to the invoice number.
+4. Find the invoice you want to download and select the icon next to the invoice number.
 
 :::note
 Invoices cannot be regenerated after they are issued. Any pending billing updates or changes will appear in the next month's invoice.
diff --git a/src/content/docs/billing/manage/optimize-costs.mdx b/src/content/docs/billing/manage/optimize-costs.mdx
index f4d34d4f201f6a3..1ebb06ae5ce6d13 100644
--- a/src/content/docs/billing/manage/optimize-costs.mdx
+++ b/src/content/docs/billing/manage/optimize-costs.mdx
@@ -10,10 +10,10 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 ## General strategies
 
-| Strategy                                                                                              | Impact                                                      |
-| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early               | Prevents surprise invoices across all products              |
-| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives            |
+| Strategy | Impact |
+|---|---|
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | Prevents surprise invoices across all products |
+| Review the [billable usage dashboard](/billing/manage/billable-usage/) weekly to identify cost trends | Catches runaway costs before the invoice arrives |
 | Understand [how charges accrue](/billing/understand/how-charges-accrue/) across the request lifecycle | Identifies which stage of a request generates the most cost |
 
 ## Per-product optimization
@@ -22,42 +22,42 @@ Reducing usage-based charges starts with understanding where your consumption co
 
 Cached responses are the cheapest path through Cloudflare. Every cache hit avoids origin fetch costs, Argo routing charges, and Workers execution.
 
-| Strategy                                                                                                              | What it reduces                                                              |
-| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                                     | Argo data transfer, Workers invocations, origin load                         |
+| Strategy | What it reduces |
+|---|---|
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
 | Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content that is accessed infrequently | Origin fetches — keeps content cached even when it would normally be evicted |
-| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls                                              | Origin bandwidth and Argo transfer between Cloudflare data centers           |
-| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default                           | Overall cache hit ratio                                                      |
+| Use [tiered caching](/cache/how-to/tiered-cache/) to reduce origin pulls | Origin bandwidth and Argo transfer between Cloudflare data centers |
+| Configure [cache rules](/cache/how-to/cache-rules/) to cache more static content by default | Overall cache hit ratio |
 
 ### Workers & Durable Objects
 
-| Strategy                                                                                                                                                                       | What it reduces                                                                 |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
-| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush                                                                             | Logpush-enabled Workers requests and Logpush data transfer                      |
+| Strategy | What it reduces |
+|---|---|
+| Use [Workers Logs](/workers/observability/logs/workers-logs/) for log retention instead of Logpush | Logpush-enabled Workers requests and Logpush data transfer |
 | Use the [WebSocket Hibernation API](/durable-objects/best-practices/websockets/#durable-objects-hibernation-websocket-api) for Durable Objects with idle WebSocket connections | Duration (GB-s) charges — billing pauses while the Durable Object is hibernated |
 
 ### R2
 
-| Strategy                                                                                                                | What it reduces                              |
-| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
-| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data              |
-| Batch R2 operations where possible instead of per-object reads                                                          | Class B operation count                      |
-| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers           | Workers invocations and CPU time             |
-| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache            | Class B reads — cached objects do not hit R2 |
+| Strategy | What it reduces |
+|---|---|
+| Use [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to the Infrequent Access storage class | Storage costs for archival data |
+| Batch R2 operations where possible instead of per-object reads | Class B operation count |
+| Use [presigned URLs](/r2/api/s3/presigned-urls/) for direct client access instead of proxying through Workers | Workers invocations and CPU time |
+| Enable [Cache-Control headers on R2 objects](/r2/buckets/public-buckets/) to leverage Cloudflare's CDN cache | Class B reads — cached objects do not hit R2 |
 
 ### Stream and Images
 
-| Strategy                                                                                                                           | What it reduces                                  |
-| ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
-| Set appropriate cache headers on Stream embed pages                                                                                | Repeated Stream delivery minutes                 |
+| Strategy | What it reduces |
+|---|---|
+| Set appropriate cache headers on Stream embed pages | Repeated Stream delivery minutes |
 | Use [Image Resizing URL format](/images/optimization/features/) with width/height parameters to serve appropriately sized variants | Transformation count — sized variants are cached |
 
 ### Load Balancing
 
-| Strategy                                                                                      | What it reduces                        |
-| --------------------------------------------------------------------------------------------- | -------------------------------------- |
+| Strategy | What it reduces |
+|---|---|
 | Set health check intervals to the longest acceptable value for your availability requirements | DNS queries to load-balanced hostnames |
-| Use fewer health check regions where regional redundancy is not critical                      | Health check frequency multiplier      |
+| Use fewer health check regions where regional redundancy is not critical | Health check frequency multiplier |
 
 ## Monitor and alert
 
diff --git a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
index e55450f95a43eb4..2b082f37ba9f84f 100644
--- a/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
+++ b/src/content/docs/billing/manage/pay-invoices-overdue-balances.mdx
@@ -12,6 +12,7 @@ import { DashButton } from "~/components";
 
 If automatic payment retries fail and you do not pay manually, your account accrues an overdue balance. While the balance is unpaid, you cannot purchase products, upgrade subscriptions, or update your billing profile. Attempts to do so return an error:
 
+
 **"You cannot add or modify subscriptions or services until the outstanding balance is paid."**
 
 To pay, select **Pay Now** from the **Billing** page in the Cloudflare dashboard. You can pay the entire balance in one transaction or [pay individual invoices](#manually-pay-invoices) separately.
@@ -22,7 +23,7 @@ When an outstanding balance is due, a new invoice will be created in your accoun
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select the most recent invoice - the amount shown should match your outstanding balance
@@ -39,7 +40,7 @@ To pay the total outstanding balance:
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Go to the **Pay overdue balances** section.
 3. Select **Pay now** next to the balance you want to pay.
@@ -52,7 +53,7 @@ If an automatic subscription renewal payment fails, Cloudflare automatically ret
 
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
-   <DashButton url="/?to=/:account/billing" />
+    <DashButton url="/?to=/:account/billing" />
 
 2. Select **Invoices and documents**.
 3. Select **Pay now** next to the invoice you want to pay.
diff --git a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
index 181362bc0ffcd63..f4e3aa40ed248b0 100644
--- a/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
+++ b/src/content/docs/billing/payment-methods/instant-bank-payments-link.mdx
@@ -33,9 +33,9 @@ Instant Bank Payments via Link is available to US-based self-serve accounts acro
 
 Bank-based Link payments appear in your billing history with these identifiers:
 
-| Field            | Value  |
-| ---------------- | ------ |
-| Payment method   | `link` |
+| Field | Value |
+| --- | --- |
+| Payment method | `link` |
 | Last four digits | `0000` |
 
 Card-based Link payments display your card's last four digits, distinguishing them from bank payments.
diff --git a/src/content/docs/billing/threshold-billing.mdx b/src/content/docs/billing/threshold-billing.mdx
index 856ef82e55f97e7..0c72335ac0c6b0a 100644
--- a/src/content/docs/billing/threshold-billing.mdx
+++ b/src/content/docs/billing/threshold-billing.mdx
@@ -27,11 +27,11 @@ You will never be double-charged. The threshold invoice and end-of-cycle invoice
 
 ### Example
 
-| Event                                       | Charge                                             |
-| ------------------------------------------- | -------------------------------------------------- |
-| Combined usage reaches threshold mid-cycle  | Threshold invoice charged (for example, $127.50)   |
+| Event | Charge |
+| --- | --- |
+| Combined usage reaches threshold mid-cycle | Threshold invoice charged (for example, $127.50) |
 | End of billing cycle (total usage was $180) | End-of-cycle invoice charged (for example, $52.50) |
-| **Total charged**                           | **$180**                                           |
+| **Total charged** | **$180** |
 
 ## Products subject to threshold billing
 
diff --git a/src/content/docs/billing/troubleshoot/error-reference.mdx b/src/content/docs/billing/troubleshoot/error-reference.mdx
index ea345499f66f805..e2fbd524b5852d0 100644
--- a/src/content/docs/billing/troubleshoot/error-reference.mdx
+++ b/src/content/docs/billing/troubleshoot/error-reference.mdx
@@ -12,21 +12,21 @@ Use the table below to find common billing error messages, understand what they
 
 ## Error messages
 
-| Error message                                                                               | Cause                                                                                 | Solution                                                                                                                                                                                     |
-| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance.                                                   | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/).                                                                                                               |
-| "The payment has failed. Please contact your bank or use a different payment method."       | Your payment method was declined by your bank.                                        | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                             |
-| "Payment error: authorization failed"                                                       | Your bank declined the transaction, or 3DS authentication was not completed.          | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/).                                                          |
-| "This zone cannot be upgraded"                                                              | The account or a previous owner of the domain has an outstanding balance.             | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
-| "There is a problem with your billing profile"                                              | Same as "this zone cannot be upgraded" — an unpaid balance exists.                    | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours.                                                                                             |
-| "You cannot modify this subscription since it is currently scheduled to be cancelled"       | You are trying to change a subscription that already has a pending cancellation.      | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/).     |
-| "You can't remove this payment method while it's linked to active subscriptions."           | You are trying to delete a payment method that is still tied to paid services.        | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).    |
-| "You can't remove a payment method while there are transactions in progress."               | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/).                       |
+| Error message | Cause | Solution |
+|---|---|---|
+| "You cannot add or modify subscriptions or services until the outstanding balance is paid." | Your account has an unpaid balance. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/). |
+| "The payment has failed. Please contact your bank or use a different payment method." | Your payment method was declined by your bank. | Check your card details and bank balance, then retry. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
+| "Payment error: authorization failed" | Your bank declined the transaction, or 3DS authentication was not completed. | Contact your bank and retry the payment. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
+| "This zone cannot be upgraded" | The account or a previous owner of the domain has an outstanding balance. | Pay the balance on all accounts you have access to, wait 24 hours, then retry. Refer to [Resolve the zone cannot be upgraded error](/billing/troubleshoot/resolve-zone-cannot-be-upgraded/). |
+| "There is a problem with your billing profile" | Same as "this zone cannot be upgraded" — an unpaid balance exists. | [Pay the outstanding balance](/billing/manage/pay-invoices-overdue-balances/) and wait 24 hours. |
+| "You cannot modify this subscription since it is currently scheduled to be cancelled" | You are trying to change a subscription that already has a pending cancellation. | Cancel the pending downgrade first, then make your change. Refer to [Resolve "you cannot modify this subscription"](/billing/troubleshoot/resolve-you-cannot-modify-this-subscription/). |
+| "You can't remove this payment method while it's linked to active subscriptions." | You are trying to delete a payment method that is still tied to paid services. | Cancel all paid subscriptions first, or add a replacement payment method. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
+| "You can't remove a payment method while there are transactions in progress." | A usage-based charge is pending, or a Registrar renewal is scheduled within 24 hours. | Wait for pending transactions to complete, then retry. Refer to [Resolve "cannot remove payment method"](/billing/troubleshoot/resolve-cannot-remove-payment-method/). |
 
 ## Email notifications
 
-| Email subject                              | What it means                                                                            | What to do                                                                                                                                                                      |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Email subject | What it means | What to do |
+|---|---|---|
 | "We couldn't process your renewal payment" | A recurring subscription charge failed. Cloudflare will retry up to 5 times over 5 days. | Update your payment method or manually pay the invoice before the grace period ends. Refer to [Resolve a payment failure](/billing/troubleshoot/troubleshoot-failed-payments/). |
 
 ## Still stuck?
diff --git a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
index 8cbc680da963f94..276892b5ec3390d 100644
--- a/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-cannot-remove-payment-method.mdx
@@ -10,14 +10,13 @@ products:
 
 When attempting to remove a payment method, you may see one of the following error messages:
 
-- "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
-- "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
+* "You can't remove this payment method while it's linked to active subscriptions. Go to Billing to manage subscriptions."
+* "You can't remove a payment method while there are transactions in progress. Make sure all transactions are completed and all subscriptions are cancelled."
 
 ## Causes
-
-- You still have active paid subscriptions
-- You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
-- You have an upcoming Registrar domain registration renewal within the next 24 hours
+* You still have active paid subscriptions
+* You have cancelled your paid subscriptions, but a usage-based charge is still scheduled
+* You have an upcoming Registrar domain registration renewal within the next 24 hours
 
 ## Solutions
 
@@ -37,19 +36,19 @@ Repeat this for all active paid subscriptions before attempting to remove the pa
 
 If you have cancelled all paid subscriptions, any usage-based products cancelled within the last 30 days may still generate charges. Your payment method must remain on file until those charges are processed. If you recently cancelled any of the following products, wait 30 days before removing your payment method:
 
-- Images
-- Stream
-- Workers
-- Argo
-- Spectrum
-- R2
-- Cache Reserve
-- Load Balancing
-- Rate Limiting
-- Log Explorer
-- Zero Trust
-- Vectorize
-- Analytics
+* Images
+* Stream
+* Workers
+* Argo
+* Spectrum
+* R2
+* Cache Reserve
+* Load Balancing
+* Rate Limiting
+* Log Explorer
+* Zero Trust
+* Vectorize
+* Analytics
 
 After the next monthly invoice is generated, you can remove the payment method.
 
diff --git a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
index eb388902186d5ac..b43d3e71c65fec6 100644
--- a/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
+++ b/src/content/docs/billing/troubleshoot/resolve-you-cannot-modify-this-subscription.mdx
@@ -10,19 +10,16 @@ products:
 
 When attempting to cancel or modify a subscription, you may see the following error message:
 
-- "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
+* "This subscription is scheduled to be cancelled at the end of the billing period. To make changes or purchase more, please click 'Cancel Downgrade' on the Subscriptions page."
 
 ## Causes
-
-- You are attempting to cancel a subscription which you have already requested cancellation for
-- You are attempting to upgrade a subscription for which a cancellation is already scheduled
+* You are attempting to cancel a subscription which you have already requested cancellation for
+* You are attempting to upgrade a subscription for which a cancellation is already scheduled
 
 ## Solutions
-
 If you intended to cancel a subscription, the cancellation is already scheduled. Your subscription ends at the close of the current billing period. Refer to the section below to find the exact date.
 
 ### When will my subscription be cancelled?
-
 After requesting cancellation, the subscriptions page shows the end date under "Ending On".
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
@@ -34,7 +31,6 @@ After requesting cancellation, the subscriptions page shows the end date under "
 If you previously cancelled the subscription and have changed your decision, you need to cancel the downgrade.
 
 ### Can I receive a refund for my cancelled subscription?
-
 No refund will be issued for a cancelled subscription - instead, your subscription will remain active until the end of the current billing period.
 
 If you do not wish to pay for the coming billing period, then you should cancel your subscription no later than on the last day of the billing period. You can discover this date by visiting the **Subscriptions** page and checking the renew date, for example “RENEWS ON Aug 29, 2025”.
@@ -59,4 +55,4 @@ If the cancellation hasn’t taken effect yet, you can click **Cancel Downgrade*
 
 - [Cancel subscriptions](/billing/manage/cancel-subscription/) — How cancellations work
 - [Billing policy](/billing/understand/billing-policy/) — Refund policy and billing terms
-- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
+- [Error reference](/billing/troubleshoot/error-reference/) — Look up other billing error messages
\ No newline at end of file
diff --git a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
index 32e60e707eb83a6..aba89709e47d926 100644
--- a/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
+++ b/src/content/docs/billing/troubleshoot/troubleshoot-invoices.mdx
@@ -34,4 +34,4 @@ You may have to wait up to one billing period for updates to appear in your Clou
 
 - [Invoices](/billing/manage/invoices/) — Download and manage invoices
 - [How Cloudflare billing works](/billing/understand/how-billing-works/) — How to read your invoice
-- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
+- [Update billing information](/billing/get-started/update-billing-info/) — Change your billing email
\ No newline at end of file
diff --git a/src/content/docs/billing/understand/billing-permissions.mdx b/src/content/docs/billing/understand/billing-permissions.mdx
index 90f8f01686d0a1a..f0a656bc1f33ea6 100644
--- a/src/content/docs/billing/understand/billing-permissions.mdx
+++ b/src/content/docs/billing/understand/billing-permissions.mdx
@@ -10,19 +10,19 @@ Access to billing features in the Cloudflare dashboard depends on the role assig
 
 ## Roles and billing capabilities
 
-| Action                             | Super Administrator | Administrator | Billing |
-| ---------------------------------- | ------------------- | ------------- | ------- |
-| View invoices and billing history  | Yes                 | Yes           | Yes     |
-| Download invoice PDFs              | Yes                 | Yes           | Yes     |
-| View billable usage dashboard      | Yes                 | Yes           | Yes     |
-| Pay an outstanding balance         | Yes                 | No            | Yes     |
-| Add or update payment methods      | Yes                 | No            | Yes     |
-| Change billing address             | Yes                 | No            | Yes     |
-| Change billing email               | Yes                 | No            | Yes     |
-| Set up budget alerts               | Yes                 | Yes           | Yes     |
-| Change or cancel subscriptions     | Yes                 | Yes           | No      |
-| Upgrade or downgrade a domain plan | Yes                 | Yes           | No      |
-| Manage account members and roles   | Yes                 | No            | No      |
+| Action | Super Administrator | Administrator | Billing |
+|---|---|---|---|
+| View invoices and billing history | Yes | Yes | Yes |
+| Download invoice PDFs | Yes | Yes | Yes |
+| View billable usage dashboard | Yes | Yes | Yes |
+| Pay an outstanding balance | Yes | No | Yes |
+| Add or update payment methods | Yes | No | Yes |
+| Change billing address | Yes | No | Yes |
+| Change billing email | Yes | No | Yes |
+| Set up budget alerts | Yes | Yes | Yes |
+| Change or cancel subscriptions | Yes | Yes | No |
+| Upgrade or downgrade a domain plan | Yes | Yes | No |
+| Manage account members and roles | Yes | No | No |
 
 :::note
 The Billing role can view and pay but cannot change subscriptions or plans. To both manage subscriptions and handle payments, a user needs the Super Administrator role.
diff --git a/src/content/docs/billing/understand/billing-policy.mdx b/src/content/docs/billing/understand/billing-policy.mdx
index b980bae02a464c9..14a33c5e72ce247 100644
--- a/src/content/docs/billing/understand/billing-policy.mdx
+++ b/src/content/docs/billing/understand/billing-policy.mdx
@@ -81,15 +81,15 @@ Enterprise account owners receive invoices directly from the Cloudflare accounti
 
 Cloudflare accepts the following payment methods:
 
-- Visa
-- Mastercard
-- American Express
-- Discover
-- PayPal
-- Apple Pay
-- Google Pay
-- Stripe Link
-- UnionPay
+* Visa
+* Mastercard
+* American Express
+* Discover
+* PayPal
+* Apple Pay
+* Google Pay
+* Stripe Link
+* UnionPay
 
 :::note
 Enterprise customers can use ACH payments for Cloudflare plans and subscriptions.
diff --git a/src/content/docs/billing/understand/how-charges-accrue.mdx b/src/content/docs/billing/understand/how-charges-accrue.mdx
index d13bbe22d007ff3..44a3bbcf2906350 100644
--- a/src/content/docs/billing/understand/how-charges-accrue.mdx
+++ b/src/content/docs/billing/understand/how-charges-accrue.mdx
@@ -26,17 +26,17 @@ Consider a visitor loading a page on a Pro domain that uses Workers, R2, Argo Sm
 
 The visitor's browser resolves the domain. This DNS query is handled by Cloudflare's authoritative DNS.
 
-| Resource    | Billing impact                                                                                                                                 |
-| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | DNS queries | Included in all plans at no extra charge. If you use Load Balancing, DNS queries to load-balanced hostnames are metered (first 500K included). |
 
 ### 2. Edge request and TLS
 
 The request arrives at the nearest Cloudflare data center. Cloudflare terminates TLS and processes the request.
 
-| Resource | Billing impact                                                                              |
-| -------- | ------------------------------------------------------------------------------------------- |
-| TLS/SSL  | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
+| Resource | Billing impact |
+|---|---|
+| TLS/SSL | Included in all plans. Advanced Certificate Manager and SSL for SaaS have separate pricing. |
 
 ### 3. Cache lookup
 
@@ -44,9 +44,9 @@ Cloudflare checks whether a cached response exists for this request.
 
 **Cache hit** — the response is served directly from the edge. No origin fetch occurs. This is the cheapest path.
 
-| Resource            | Billing impact                                                                                                                                                                                      |
-| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bandwidth           | Included in all plans. Cloudflare does not charge for bandwidth.                                                                                                                                    |
+| Resource | Billing impact |
+|---|---|
+| Bandwidth | Included in all plans. Cloudflare does not charge for bandwidth. |
 | Cache Reserve reads | If Cache Reserve is enabled and the asset is served from tiered cache storage, reads are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 **Cache miss** — the request must be forwarded to the origin. Continue to step 4.
@@ -55,53 +55,53 @@ Cloudflare checks whether a cached response exists for this request.
 
 If Argo is enabled, Cloudflare routes the request through the fastest path across its network to your origin.
 
-| Resource           | Billing impact                                                                                                                                             |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Argo data transfer | Metered per GB transferred between Cloudflare and your origin. First 1 GB included. Refer to [Argo Smart Routing](/argo-smart-routing/) for current rates. |
 
 ### 5. Workers execution (if configured)
 
 If a Worker is bound to the route, it executes before or instead of fetching from the origin.
 
-| Resource                | Billing impact                                                                                                                                    |
-| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Worker requests         | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
-| Worker CPU time         | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates.        |
-| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates.   |
+| Resource | Billing impact |
+|---|---|
+| Worker requests | Metered per invocation. Workers Paid plan includes 10 million requests. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Worker CPU time | Metered per millisecond of CPU time. 30 million CPU-ms included. Refer to [Workers pricing](/workers/platform/pricing/) for current rates. |
+| Workers KV reads/writes | If the Worker reads from or writes to KV, each operation is metered separately. Refer to [KV pricing](/kv/platform/pricing/) for current rates. |
 
 ### 6. Origin fetch and response
 
 If the Worker or cache miss triggers an origin fetch, Cloudflare retrieves the response from your origin server.
 
-| Resource  | Billing impact                                                                   |
-| --------- | -------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Bandwidth | No charge for data transfer between Cloudflare and your origin (no egress fees). |
 
 ### 7. R2 storage operations (if used)
 
 If the Worker or origin logic reads from or writes to R2, each operation is metered.
 
-| Resource                       | Billing impact                                                                     |
-| ------------------------------ | ---------------------------------------------------------------------------------- |
-| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.   |
-| R2 Class B operations (reads)  | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates.  |
-| R2 storage                     | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
-| R2 data egress                 | Free. Cloudflare does not charge for R2 egress.                                    |
+| Resource | Billing impact |
+|---|---|
+| R2 Class A operations (writes) | First 1 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 Class B operations (reads) | First 10 million included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 storage | First 10 GB-month included. Refer to [R2 pricing](/r2/pricing/) for current rates. |
+| R2 data egress | Free. Cloudflare does not charge for R2 egress. |
 
 ### 8. Cache write (miss path)
 
 After fetching from the origin, Cloudflare caches the response at the edge for future requests.
 
-| Resource             | Billing impact                                                                                                                                     |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Resource | Billing impact |
+|---|---|
 | Cache Reserve writes | If Cache Reserve is enabled, writes are metered. Refer to [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) for current rates. |
 
 ### 9. Image Resizing (if configured)
 
 If the request triggers Image Resizing (via URL parameters or a Worker), the transformation is metered.
 
-| Resource              | Billing impact                                                                                                                       |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| Resource | Billing impact |
+|---|---|
 | Image transformations | First 50,000 included on the Business plan, then metered per request. Refer to [Images pricing](/images/pricing/) for current rates. |
 
 ### 10. Response delivered
@@ -116,15 +116,15 @@ The key takeaway: **cached responses are the cheapest path**. Every cache hit av
 
 ## Cost optimization strategies
 
-| Strategy                                                                            | Products affected               | Impact                                                            |
-| ----------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------- |
-| Maximize cache hit ratio with appropriate Cache-Control headers                     | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs               |
-| Use Cache Reserve for long-tail content                                             | Cache, origin                   | Medium — reduces origin fetches for infrequently accessed content |
-| Set appropriate TTLs to avoid unnecessary revalidation                              | Cache, Argo                     | Medium — reduces origin round-trips                               |
-| Use Workers Smart Placement to run Workers closer to your data                      | Workers CPU time                | Medium — reduces execution time for data-dependent Workers        |
-| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage                      | Medium — reduces storage costs for archival data                  |
-| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/)  | All usage-based products        | High — visibility is the first step to optimization               |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes   | All usage-based products        | High — prevents surprise invoices                                 |
+| Strategy | Products affected | Impact |
+|---|---|---|
+| Maximize cache hit ratio with appropriate Cache-Control headers | Argo, Workers, origin bandwidth | High — every cache hit eliminates origin-side costs |
+| Use Cache Reserve for long-tail content | Cache, origin | Medium — reduces origin fetches for infrequently accessed content |
+| Set appropriate TTLs to avoid unnecessary revalidation | Cache, Argo | Medium — reduces origin round-trips |
+| Use Workers Smart Placement to run Workers closer to your data | Workers CPU time | Medium — reduces execution time for data-dependent Workers |
+| Use R2 lifecycle rules to move infrequently accessed data to Infrequent Access tier | R2 storage | Medium — reduces storage costs for archival data |
+| Monitor usage with the [billable usage dashboard](/billing/manage/billable-usage/) | All usage-based products | High — visibility is the first step to optimization |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes | All usage-based products | High — prevents surprise invoices |
 
 ## Related resources
 
diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx
index 4b7d658484684f6..0be6d9d6118dc30 100644
--- a/src/content/docs/billing/understand/preview-services.mdx
+++ b/src/content/docs/billing/understand/preview-services.mdx
@@ -29,7 +29,7 @@ To enable a preview service, use the **Dashboard link** in the following table.
 | Load Balancing                     | [Load Balancing dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing)          | [Load Balancing docs](/load-balancing/)                                    | [Load Balancing community](https://community.cloudflare.com/tag/loadbalancing) |
 | Advanced Rate Limiting             | [Rate Limiting dashboard](https://dash.cloudflare.com/?to=/:account/:zone/security/waf/rate-limiting-rules) | [Rate Limiting docs](/waf/rate-limiting-rules/)                            | [Rate Limiting community](https://community.cloudflare.com/c/security/6)       |
 | Stream                             | [Stream dashboard](https://dash.cloudflare.com/?to=/:account/stream)                                        | [Stream docs](/stream/)                                                    | [Stream community](https://community.cloudflare.com/tag/cloudflarestream)      |
-| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)             | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
+| Waiting Room                       | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms)        | [Waiting Room docs](/waiting-room/)                                        | [Waiting Room community](https://community.cloudflare.com/)                    |
 | Web3                               | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3)                                      | [Web3 docs](/web3/)                                                        | [Web3 discord](https://discord.cloudflare.com)                                 |
 | Workers                            | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers)                                      | [Workers docs](/workers/)                                                  | [Workers discord](https://discord.com/invite/cloudflaredev)                    |
 | Zero Trust                         | [Zero Trust dashboard](https://one.dash.cloudflare.com/)                                                    | [Zero Trust docs](/cloudflare-one/)                                        | [Zero Trust community](https://community.cloudflare.com/c/security/access/51)  |
diff --git a/src/content/docs/billing/understand/usage-based-billing.mdx b/src/content/docs/billing/understand/usage-based-billing.mdx
index c3270b67c1b766d..2e7cc4c49963e48 100644
--- a/src/content/docs/billing/understand/usage-based-billing.mdx
+++ b/src/content/docs/billing/understand/usage-based-billing.mdx
@@ -24,29 +24,29 @@ The following products bill based on consumption. Each product includes a free t
 
 For current overage rates, refer to the [Cloudflare plans page](https://www.cloudflare.com/plans/) or each product's pricing page linked below. Rates may change — the links below are always up to date.
 
-| Product                                                       | Billable metric                | Free tier (included)                   | Pricing details                                                       |
-| ------------------------------------------------------------- | ------------------------------ | -------------------------------------- | --------------------------------------------------------------------- |
-| [Workers](/workers/platform/pricing/)                         | Requests, CPU time             | 10M requests, 30M CPU-ms               | [Workers pricing](/workers/platform/pricing/)                         |
-| [R2](/r2/pricing/)                                            | Storage, operations            | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/)                                            |
-| [Argo Smart Routing](/argo-smart-routing/)                    | Data transfer (GB)             | First 1 GB                             | [Argo pricing](/argo-smart-routing/)                                  |
-| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage         | None                                   | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
-| [Load Balancing](/load-balancing/)                            | DNS queries                    | First 500K                             | [Load Balancing](/load-balancing/)                                    |
-| [Stream](/stream/pricing/)                                    | Minutes stored, minutes viewed | Varies by plan                         | [Stream pricing](/stream/pricing/)                                    |
-| [Images](/images/pricing/)                                    | Transformations, storage       | Varies by plan                         | [Images pricing](/images/pricing/)                                    |
-| [Spectrum](/spectrum/)                                        | Data transfer (GB)             | None                                   | [Spectrum](/spectrum/)                                                |
+| Product | Billable metric | Free tier (included) | Pricing details |
+|---|---|---|---|
+| [Workers](/workers/platform/pricing/) | Requests, CPU time | 10M requests, 30M CPU-ms | [Workers pricing](/workers/platform/pricing/) |
+| [R2](/r2/pricing/) | Storage, operations | 10 GB storage, 1M Class A, 10M Class B | [R2 pricing](/r2/pricing/) |
+| [Argo Smart Routing](/argo-smart-routing/) | Data transfer (GB) | First 1 GB | [Argo pricing](/argo-smart-routing/) |
+| [Cache Reserve](/cache/advanced-configuration/cache-reserve/) | Reads, writes, storage | None | [Cache Reserve pricing](/cache/advanced-configuration/cache-reserve/) |
+| [Load Balancing](/load-balancing/) | DNS queries | First 500K | [Load Balancing](/load-balancing/) |
+| [Stream](/stream/pricing/) | Minutes stored, minutes viewed | Varies by plan | [Stream pricing](/stream/pricing/) |
+| [Images](/images/pricing/) | Transformations, storage | Varies by plan | [Images pricing](/images/pricing/) |
+| [Spectrum](/spectrum/) | Data transfer (GB) | None | [Spectrum](/spectrum/) |
 
 ## Optimize usage-based costs
 
 Reducing usage-based charges starts with understanding where your consumption comes from. Use the [billable usage dashboard](/billing/manage/billable-usage/) to identify which products are driving costs, then apply the strategies below.
 
-| Strategy                                                                                                 | What it reduces                                      |
-| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
-| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers                        | Argo data transfer, Workers invocations, origin load |
-| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content                  | Origin fetches for infrequently accessed assets      |
-| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs                                     |
-| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers                  | Workers CPU time                                     |
-| Batch R2 operations where possible instead of per-object reads                                           | R2 Class B operation count                           |
-| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early                  | All products — prevents surprise invoices            |
+| Strategy | What it reduces |
+|---|---|
+| Increase cache hit ratio with longer TTLs and appropriate `Cache-Control` headers | Argo data transfer, Workers invocations, origin load |
+| Use [Cache Reserve](/cache/advanced-configuration/cache-reserve/) for long-tail content | Origin fetches for infrequently accessed assets |
+| Set up [R2 lifecycle rules](/r2/buckets/object-lifecycles/) to transition cold data to Infrequent Access | R2 storage costs |
+| Use [Workers Smart Placement](/workers/configuration/placement/) for data-heavy Workers | Workers CPU time |
+| Batch R2 operations where possible instead of per-object reads | R2 Class B operation count |
+| Set up [budget alerts](/billing/manage/budget-alerts/) to catch unexpected spikes early | All products — prevents surprise invoices |
 
 For a detailed walkthrough of how a single request generates charges across multiple products, refer to [How charges accrue](/billing/understand/how-charges-accrue/).
 
diff --git a/src/content/docs/bots/account-abuse-protection.mdx b/src/content/docs/bots/account-abuse-protection.mdx
index e54a667206310fc..ddd1362d953258a 100644
--- a/src/content/docs/bots/account-abuse-protection.mdx
+++ b/src/content/docs/bots/account-abuse-protection.mdx
@@ -12,15 +12,16 @@ sidebar:
   badge:
     text: Early Access
     variant: note
+
 ---
 
-import { Render, Description, DashButton, Steps } from "~/components";
+import { Render, Description, DashButton, Steps } from "~/components"
 
 <Description>
-	Identify and mitigate attacks on your customer and user accounts.
+Identify and mitigate attacks on your customer and user accounts.
 </Description>
 
-Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems.
+Account abuse — bulk account creation and account takeover attacks — can cause financial losses and erode user trust. Fraud detection allows you to detect and mitigate these attacks among your traffic. You can use fraud signals to [update or create new rules](/waf/custom-rules/) for suspicious account activity, or pass signals to your origin to integrate into authentication and authorization systems. 
 
 ## Availability
 
@@ -37,15 +38,15 @@ Contact your Cloudflare account team to request access.
 User ID is a cryptographically hashed, per-zone identifier that customers can use in [Security Analytics](/waf/analytics/security-analytics/), [Security Rules](/waf/custom-rules/), and [Managed Transforms](/rules/transform/managed-transforms/reference/). Hashed User IDs are created by encrypting the primary credentials your users provide, converting them into opaque identifiers unique to your zone. This allows traffic analysis while protecting user privacy. With access to hashed User ID, website owners can:
 
 - Review which users have the most activity on your website.
-- Find the details on a specific user's characteristics and activity patterns.
-- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.
-- Combine fields to see when accounts are being targeted with leaked credentials.
+- Find the details on a specific user's characteristics and activity patterns.  
+- Mitigate traffic based on the user, such as blocking a user with historically suspicious activity.  
+- Combine fields to see when accounts are being targeted with leaked credentials.  
 - Manage network patterns or signals associated with specific users.
 
 :::note[Data privacy]
-User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications.
+User profiling was created with privacy in mind. Its design and engineering align with our privacy and compliance programs and contain technical controls that protect the privacy of users. Hashed User IDs are created by encrypting the primary credentials your users use to access your applications. 
 
-Other Cloudflare customers cannot access your user profiles. They are unique to your zone.
+Other Cloudflare customers cannot access your user profiles. They are unique to your zone. 
 :::
 
 User ID is an opt-in feature that can be enabled in Security Settings.
@@ -64,13 +65,13 @@ To enable, edit, or disable the setting:
 
 ### Ephemeral IDs
 
-Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection.
+Customers using Cloudflare [Turnstile](/turnstile/) can utilize ephemeral IDs for Fraud detection. 
 
 Refer to [Fraud detection with ephemeral IDs](/turnstile/tutorials/fraud-detection-with-ephemeral-ids/) for more information.
 
 ### Account takeover detections
 
-Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks.
+Cloudflare Bot Management includes dedicated detection IDs for account takeover attacks. 
 
 Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/) for more information.
 
@@ -84,25 +85,25 @@ Account takeover (ATO) detections are not available for accounts using the [Data
 
 ### Prerequisites
 
-Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior.
+Fraud detection requires the following configurations and settings to be enabled to properly identify suspicious behavior. 
 
 #### Security Settings
 
-- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections.
+- User ID: Cloudflare encrypts or hashes your user IDs to better understand typical user traffic patterns across your applications. Enabling Cloudflare to create hashed user ID mappings to your users will allow you to receive account takeover and bulk account creation detections. 
 
-#### Eligible traffic
+#### Eligible traffic 
 
-Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations.
+Cloudflare automatically identifies certain login and sign up traffic on your applications and runs these detections without any additional configurations. 
 
 - Sign-ups: Cloudflare automatically monitors traffic on endpoints that match common sign up endpoints.
 - Login: Cloudflare automatically monitors traffic on endpoints that match common login endpoints.
 
 Verify that your endpoints are properly labeled to ensure Cloudflare can detect and monitor them correctly.
 
-<Render
-	file="endpoint-label-warning"
-	product="bots"
-	params={{ one: "or sign up" }}
+<Render 
+  file="endpoint-label-warning" 
+  product="bots"
+  params={{ one: "or sign up" }} 
 />
 
 :::tip[Enhanced with leaked credential detections]
@@ -113,43 +114,43 @@ Cloudflare also recommends enabling [Leaked credentials detection](/waf/detectio
 
 ### Detections
 
-Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints.
+Fraud detections focus on account abuse attacks such as account takeover, bulk account creation, and credential quality. These detections run on all eligible traffic and can be used across [Cloudflare Rules](/rules/) to log, challenge, and/or block requests to your sign up and login endpoints. 
 
 #### Account creation
 
-Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure.
+Disposable Email Checks detect when users sign up with throwaway email addresses commonly used for promotion abuse and fake account creation. These disposable email services allow attackers to create thousands of unique accounts without maintaining real infrastructure. 
 
-You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email.
+You can use the following binary field as you build rules to enforce security preferences, choosing to block all disposable emails outright, or issue a [challenge](/cloudflare-challenges/challenge-types/) to anyone attempting to create an account with a disposable email. 
 
 #### Suspicious emails
 
-Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections.
+Cloudflare analyzes the components of an email used during sign up to help identify suspicious patterns. Refer to [prerequisites](#prerequisites) to ensure your traffic is eligible for detections. 
 
-Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching.
+Cloudflare does not store email addresses during this analysis. All detections processed without any storage or caching. 
 
-| Detection tag                         | Description                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services.                                                                                                                                                                                                                                                                            |
-| `cf.fraud.email_risk`                 | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
+| Detection tag | Description |
+| --- | --- |
+| `cf.fraud_detection.disposable_email` | Identifies emails with domains that are commonly found in lists of temporary or disposable email services. |
+| `cf.fraud.email_risk` | Analyzes the randomness (entropy) of characters in an email username and top level domain. For example, `a8xk2m9p@example.com` has high entropy (very random characters), while `john.smith@example.com` has low entropy (recognizable pattern). <br />High risk emails indicate high entropy, while medium and low risk emails indicate less randomness in the string of characters. |
 
----
+--- 
 
 ### Mitigations
 
-The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic.
+The following Fraud detection fields can be used in Security Rules to help identify and mitigate suspicious traffic. 
 
 #### Security Rules
 
 The following fields can be used in new and existing Security Rules.
 
-| Field                                  | Description                                                                                        | Values                                                                                                                                                                                                                                                              |
-| -------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False`                                                                                                                                                                                                                                                   |
-| `cf.fraud.email_risk`                  | Measures risk of email based on randomness of characters in the username and domain.               | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
+| Field | Description | Values |
+| --- | --- | --- |
+| `cf.fraud_detection.disposable_domain` | Flags whether a domain for a given email is included in a known list of temporary email providers. | `True` or `False` |
+| `cf.fraud.email_risk` | Measures risk of email based on randomness of characters in the username and domain. | `Low` represents low risk due to reduced randomness and simple emails. <br />`Medium` represents medium risk based on larger strings with slightly more randomness. <br />`High` represents high risk based on larger and random character strings. <br />`Unknown` |
 
 #### Other rules
 
-You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin.
+You can use Fraud detection data in Request Header [Transform Rules](/rules/transform/managed-transforms/) to pass information down to the origin. 
 
 #### LogPush
 
@@ -159,12 +160,12 @@ You can add Fraud detection fields to existing or new [LogPush](/logs/logpush/)
 
 ## Analytics
 
-You can find Fraud data and detections in Security Analytics, where you can see top User IDs.
+You can find Fraud data and detections in Security Analytics, where you can see top User IDs. 
 
 <DashButton url="/?to=/:account/:zone/security/analytics" />
 
-Fraud fields can be used as filters to identify suspicious patterns in your traffic.
+Fraud fields can be used as filters to identify suspicious patterns in your traffic. 
 
-The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers.
+The hashed User ID field within Security Analytics also provides Fraud customers with data that can help review detections and patterns per individual users rather than requests. You can review user level aggregations for IPs and IP counts, event types (login or sign up), locations, devices, and browsers. 
 
 A user level profile also provides a quick way to review the latest events associated with a user so that you can identify any anomalies and create a custom rule to log, block, or challenge that user.
diff --git a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
index b666e3479ba08d7..61260abf06b336f 100644
--- a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
+++ b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx
@@ -12,7 +12,7 @@ sidebar:
   label: Block AI Bots
 ---
 
-import { Render, Steps, DashButton } from "~/components";
+import { Render, Steps, DashButton } from "~/components"
 
 :::note[Block AI bots availability]
 The **Block AI bots** feature is only available in the new [application security dashboard](/security/).
@@ -35,4 +35,4 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
   5. Select **Save** to save your configuration.
 </Steps>
 
-To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
+To block individual AI crawlers (rather than blocking all crawlers), use [AI Crawl Control](/ai-crawl-control/).
\ No newline at end of file
diff --git a/src/content/docs/bots/additional-configurations/custom-rules.mdx b/src/content/docs/bots/additional-configurations/custom-rules.mdx
index fca74fa82b41d73..287bace657d036c 100644
--- a/src/content/docs/bots/additional-configurations/custom-rules.mdx
+++ b/src/content/docs/bots/additional-configurations/custom-rules.mdx
@@ -16,17 +16,17 @@ Bot protection on Cloudflare works through two complementary mechanisms: built-i
 
 The following features are configured through toggles and dropdowns in [Security Settings](/security/settings/). They do not require you to write any rule expressions.
 
-| Feature                                                                                | What it does                                                                                       | Availability                  |
-| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- |
-| [Block AI bots](/bots/additional-configurations/block-ai-bots/)                        | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans                     |
-| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/)                          | Feeds non-compliant AI crawlers into a maze of generated content                                   | All plans                     |
-| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/)              | Prepends AI crawler disallow directives to your `robots.txt`                                       | All plans                     |
-| Super Bot Fight Mode > **Definitely automated**                                        | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1                    | Pro, Business, Enterprise     |
-| Super Bot Fight Mode > **Likely automated**                                            | Blocks or challenges traffic with a bot score of 2-29                                              | Business, Enterprise          |
-| [Verified bots](/bots/concepts/bot/verified-bots/)                                     | Managed category of high-trust bots (Googlebot, Bingbot, and others)                               | Pro, Business, Enterprise     |
-| [Static resource protection](/bots/additional-configurations/static-resources/)        | Extends bot actions to cover static file types                                                     | Pro, Business, Enterprise     |
-| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/)              | Allows WordPress loopback requests through bot protection                                          | Pro, Business, Enterprise     |
-| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript                    | All plans (automatic on Free) |
+| Feature | What it does | Availability |
+| --- | --- | --- |
+| [Block AI bots](/bots/additional-configurations/block-ai-bots/) | Blocks AI crawlers (GPTBot, ClaudeBot, Bytespider, and others) using an auto-updating managed rule | All plans |
+| [AI Labyrinth](/bots/additional-configurations/ai-labyrinth/) | Feeds non-compliant AI crawlers into a maze of generated content | All plans |
+| [Managed robots.txt](/bots/additional-configurations/managed-robots-txt/) | Prepends AI crawler disallow directives to your `robots.txt` | All plans |
+| Super Bot Fight Mode > **Definitely automated** | Blocks or challenges traffic with a [bot score](/bots/concepts/bot-score/) of 1 | Pro, Business, Enterprise |
+| Super Bot Fight Mode > **Likely automated** | Blocks or challenges traffic with a bot score of 2-29 | Business, Enterprise |
+| [Verified bots](/bots/concepts/bot/verified-bots/) | Managed category of high-trust bots (Googlebot, Bingbot, and others) | Pro, Business, Enterprise |
+| [Static resource protection](/bots/additional-configurations/static-resources/) | Extends bot actions to cover static file types | Pro, Business, Enterprise |
+| [Optimize for WordPress](/bots/troubleshooting/wordpress-loopback-issue/) | Allows WordPress loopback requests through bot protection | Pro, Business, Enterprise |
+| [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) | Injects a lightweight script to identify clients that cannot execute JavaScript | All plans (automatic on Free) |
 
 Bot settings update automatically as Cloudflare identifies new bot signatures and AI crawlers, while custom rules require manual updates. They do not count toward your [custom rule limits](/waf/custom-rules/#availability), and apply uniformly across your domain without the risk of expression errors.
 
diff --git a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
index d36b1802e907d09..ce92bacfafafb92 100644
--- a/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/detection-ids/additional-detections.mdx
@@ -12,6 +12,7 @@ Cloudflare bot detection includes additional signals to catch different kinds of
 
 Bot management customers automatically benefit from the residential proxy detection improvement below, which lowers the [bot score](/bots/concepts/bot-score/) for matched requests. Using the detection ID in [custom rules](/waf/custom-rules/) provides even more visibility and control over mitigating residential proxy traffic.
 
-| <div style="width:100px">Detection ID</div> | Description                                                                                                                                                                                                                                                                               |
-| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `50331651`                                  | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
+
+| <div style="width:100px">Detection ID</div> | Description                              |
+| ------------------------------------------ | ---------------------------------------- |
+| `50331651`                                 | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
diff --git a/src/content/docs/bots/additional-configurations/index.mdx b/src/content/docs/bots/additional-configurations/index.mdx
index bc876caf734e5e0..0768d508f998fd1 100644
--- a/src/content/docs/bots/additional-configurations/index.mdx
+++ b/src/content/docs/bots/additional-configurations/index.mdx
@@ -11,10 +11,11 @@ sidebar:
 head:
   - tag: title
     content: Additional Bots configurations
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on additional bot management configurations:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
index f8af19b5b7de7b0..b575e485e4d47b1 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 1
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 [**JA3**](https://github.com/salesforce/ja3) and [**JA4**](https://github.com/FoxIO-LLC/ja4) **fingerprints** identify TLS clients based on how they initiate connections. Each client type (browser, bot, or application) has distinct connection characteristics, so the resulting fingerprint acts as a stable identifier across different destination IPs, ports, and certificates.
 
@@ -16,62 +17,64 @@ JA4 improves on JA3 by sorting ClientHello extensions, which reduces the number
 
 :::note
 
-JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management.
+JA3 and JA4 fingerprints are only available to Enterprise customers who have purchased Bot Management. 
 :::
 
 <Render file="signals-intelligence-and-ja4" product="bots" />
 
 ```json
+
 {
-	"ja4Signals": {
-		"h2h3_ratio_1h": 0.98826485872269,
-		"heuristic_ratio_1h": 7.288895722013e-5,
-		"reqs_quantile_1h": 0.99905741214752,
-		"uas_rank_1h": 901,
-		"browser_ratio_1h": 0.93640440702438,
-		"paths_rank_1h": 655,
-		"reqs_rank_1h": 850,
-		"cache_ratio_1h": 0.18918327987194,
-		"ips_rank_1h": 662,
-		"ips_quantile_1h": 0.99926590919495
-	},
-	"jaSignalsParsed": {
-		"ratios": {
-			"h2h3_ratio_1h": 0.98826485872269,
-			"heuristic_ratio_1h": 7.288895722013e-5,
-			"browser_ratio_1h": 0.93640440702438,
-			"cache_ratio_1h": 0.18918327987194
-		},
-		"ranks": {
-			"uas_rank_1h": 901,
-			"paths_rank_1h": 655,
-			"reqs_rank_1h": 850,
-			"ips_rank_1h": 662
-		},
-		"quantiles": {
-			"reqs_quantile_1h": 0.99905741214752,
-			"ips_quantile_1h": 0.99926590919495
-		}
-	}
+  "ja4Signals": {
+    "h2h3_ratio_1h": 0.98826485872269,
+    "heuristic_ratio_1h": 7.288895722013e-05,
+    "reqs_quantile_1h": 0.99905741214752,
+    "uas_rank_1h": 901,
+    "browser_ratio_1h": 0.93640440702438,
+    "paths_rank_1h": 655,
+    "reqs_rank_1h": 850,
+    "cache_ratio_1h": 0.18918327987194,
+    "ips_rank_1h": 662,
+    "ips_quantile_1h": 0.99926590919495
+  },
+  "jaSignalsParsed": {
+    "ratios": {
+      "h2h3_ratio_1h": 0.98826485872269,
+      "heuristic_ratio_1h": 7.288895722013e-05,
+      "browser_ratio_1h": 0.93640440702438,
+      "cache_ratio_1h": 0.18918327987194
+    },
+    "ranks": {
+      "uas_rank_1h": 901,
+      "paths_rank_1h": 655,
+      "reqs_rank_1h": 850,
+      "ips_rank_1h": 662
+    },
+    "quantiles": {
+      "reqs_quantile_1h": 0.99905741214752,
+      "ips_quantile_1h": 0.99926590919495
+    }
+  }
 }
+
 ```
 
 When JA4 Signals are missing, the output appears as follows:
 
 ```json output title="Missing JA4 signals output"
 {
-	"ja4Signals": {},
-	"jaSignalsParsed": {
-		"ratios": {},
-		"ranks": {},
-		"quantiles": {}
-	}
+  "ja4Signals": {},
+  "jaSignalsParsed": {
+    "ratios": {},
+    "ranks": {},
+    "quantiles": {}
+  }
 }
 ```
 
 :::note
 
-This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/).
+This sample was generated using [Workers' Cloudflare Object script](/workers/examples/accessing-the-cloudflare-object/). 
 :::
 
 <Render file="ja3-ja4-null" product="bots" />
diff --git a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
index 23baf713cc11a7c..2a86d9d70cbc989 100644
--- a/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
+++ b/src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Bot Management customers can view aggregate intelligence data for each [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/) based on traffic across the Cloudflare network. Use this data to understand why a request received a specific bot score or to feed into your own machine learning models running in [Cloudflare Workers](/workers/) or at your origin.
 
diff --git a/src/content/docs/bots/additional-configurations/javascript-detections.mdx b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
index e3c29b9383911ff..69e80bc8893eef4 100644
--- a/src/content/docs/bots/additional-configurations/javascript-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/javascript-detections.mdx
@@ -7,4 +7,4 @@ products:
 external_link: /cloudflare-challenges/challenge-types/javascript-detections/
 sidebar:
   order: 3
----
+---
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot-tags.mdx b/src/content/docs/bots/concepts/bot-tags.mdx
index f498c1ebd7862df..ce7772981cc0afe 100644
--- a/src/content/docs/bots/concepts/bot-tags.mdx
+++ b/src/content/docs/bots/concepts/bot-tags.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 3
+
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip } from "~/components"
 
 <GlossaryTooltip term="bot tags">Bot tags</GlossaryTooltip> provide more detail about *why* Cloudflare assigned a <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/">bot score</GlossaryTooltip> to a request.
 
diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx
index 8135d2506798f9c..79b102ed14105a3 100644
--- a/src/content/docs/bots/concepts/bot/index.mdx
+++ b/src/content/docs/bots/concepts/bot/index.mdx
@@ -29,7 +29,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni
 <Render file="verified-bots" product="bots" />
 
 :::note
-The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability).
+The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability). 
 :::
 
 ## AI bots
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
index 51b8af2d0e34705..79b4ca637337d88 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx
@@ -9,6 +9,7 @@ sidebar:
 learning_center:
   title: What is a bot?
   link: https://www.cloudflare.com/learning/bots/what-is-a-bot/
+
 ---
 
 A signed agent is a bot controlled by an end user and verified through [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) cryptographic signatures.
@@ -32,4 +33,4 @@ Once Cloudflare approves a signed agent, it should appear on [Cloudflare Radar's
 
 ## Verification method
 
-The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
+The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
index 7012c9a37f3a779..4b3a2e13bca22e5 100644
--- a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx
@@ -5,8 +5,9 @@ description: Requirements an agent must meet to be listed as a Cloudflare signed
 products:
   - bots
 sidebar:
-  order: 3
-  label: Policy
+    order: 3
+    label: Policy
+
 ---
 
 In order to be listed by Cloudflare as a signed agent, your agent must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
@@ -63,4 +64,4 @@ If any of the requirements to validate are breached, a service will be removed f
 The following are examples of breaches of policy:
 
 - The service has vulnerabilities that have not been patched.
-- The disclosed purpose of the service does not reflect on the traffic.
+- The disclosed purpose of the service does not reflect on the traffic.
\ No newline at end of file
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
index 35f535378a55bd9..0a353f6982931b7 100644
--- a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
+++ b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
@@ -5,11 +5,12 @@ description: Requirements a bot must meet to be listed as a Cloudflare verified
 products:
   - bots
 sidebar:
-  order: 5
-  label: Policy
+    order: 5
+    label: Policy
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors.
 
diff --git a/src/content/docs/bots/concepts/index.mdx b/src/content/docs/bots/concepts/index.mdx
index 6c7d7f72e402af2..24071d2b6d12abd 100644
--- a/src/content/docs/bots/concepts/index.mdx
+++ b/src/content/docs/bots/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on bot concepts:
 
diff --git a/src/content/docs/bots/get-started/index.mdx b/src/content/docs/bots/get-started/index.mdx
index e3dd198f6f0fb99..4082e3406e6058c 100644
--- a/src/content/docs/bots/get-started/index.mdx
+++ b/src/content/docs/bots/get-started/index.mdx
@@ -12,9 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with Cloudflare bot solutions
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to get started with Cloudflare's bot solutions based on your plan type:
 
diff --git a/src/content/docs/bots/glossary.mdx b/src/content/docs/bots/glossary.mdx
index 51cd6fdaf56a98f..0fbbfcdccbc2f94 100644
--- a/src/content/docs/bots/glossary.mdx
+++ b/src/content/docs/bots/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 10
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Bots documentation.
 
diff --git a/src/content/docs/bots/plans/bm-subscription.mdx b/src/content/docs/bots/plans/bm-subscription.mdx
index c0946617758e924..3d5517526b98383 100644
--- a/src/content/docs/bots/plans/bm-subscription.mdx
+++ b/src/content/docs/bots/plans/bm-subscription.mdx
@@ -105,17 +105,17 @@ Zones that have [Enterprise Bot Management](/bots/get-started/bot-management/) e
 
 Bot Management customers have both bot settings (configured in **Security Settings**) and the ability to create custom rules using bot score fields. Start with the bot settings for baseline protection, then add custom rules only when you need additional control.
 
-| Feature                                         | Handled by bot settings | When to use custom rules instead                                                                  |
-| ----------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
-| Block or challenge definitely automated traffic | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
-| Block or challenge likely automated traffic     | No                      | Path-specific rules, custom thresholds, or combining with other fields                            |
-| Allow or block verified bots                    | No                      | Granular control by verified bot category                                                         |
-| Block AI crawlers                               | Yes                     | Target individual AI crawlers using detection IDs                                                 |
-| Protect static resources                        | No                      | Exclude static resources from specific rules                                                      |
-| Optimize for WordPress                          | No                      | No                                                                                                |
-| Forward bot data to origin                      | No                      | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/)                          |
-| Detection ID targeting                          | No                      | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/)                       |
-| JA3/JA4 fingerprint rules                       | No                      | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
+| Feature | Handled by bot settings | When to use custom rules instead |
+| --- | --- | --- |
+| Block or challenge definitely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
+| Block or challenge likely automated traffic | No | Path-specific rules, custom thresholds, or combining with other fields |
+| Allow or block verified bots | No | Granular control by verified bot category |
+| Block AI crawlers | Yes | Target individual AI crawlers using detection IDs |
+| Protect static resources | No | Exclude static resources from specific rules |
+| Optimize for WordPress | No | No |
+| Forward bot data to origin | No | Use [Transform Rules](/rules/transform/) or [Snippets](/rules/snippets/) |
+| Detection ID targeting | No | Use `cf.bot_management.detection_ids` in [custom rules](/waf/custom-rules/) |
+| JA3/JA4 fingerprint rules | No | Use `cf.bot_management.ja3_hash` or `cf.bot_management.ja4` in [custom rules](/waf/custom-rules/) |
 
 For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
 
diff --git a/src/content/docs/bots/reference/alerts.mdx b/src/content/docs/bots/reference/alerts.mdx
index 039399e05dda310..76c74e5d486644c 100644
--- a/src/content/docs/bots/reference/alerts.mdx
+++ b/src/content/docs/bots/reference/alerts.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 4
+
 ---
 
-import { AvailableNotifications, Steps, DashButton } from "~/components";
+import { AvailableNotifications, Steps, DashButton } from "~/components"
 
 Bot alerts inform you when Cloudflare detects spikes in your traffic with any of the following characteristics:
 
@@ -16,7 +17,7 @@ Bot alerts inform you when Cloudflare detects spikes in your traffic with any of
 - An increase in traffic on available dimensions in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 - Filters of your choosing in [Set up a bot detection alert](#set-up-a-bot-detection-alert).
 
----
+--- 
 
 ## Alert types
 
@@ -72,5 +73,5 @@ You can also choose to group by the following dimensions so that they can be ale
 - Bot Detection IDs
 
 :::note
-Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/).
-:::
+Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/). 
+:::
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/bot-management-variables.mdx b/src/content/docs/bots/reference/bot-management-variables.mdx
index 388e76e2a3c7d80..8b78f19b39ba24e 100644
--- a/src/content/docs/bots/reference/bot-management-variables.mdx
+++ b/src/content/docs/bots/reference/bot-management-variables.mdx
@@ -6,21 +6,21 @@ products:
   - bots
 sidebar:
   order: 2
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Ruleset Engine fields
 
 Bot Management provides access to several [new variables](/ruleset-engine/rules-language/fields/reference/?field-category=Bots) within the expression builder of Ruleset Engine-based products such as [WAF custom rules](/waf/custom-rules/).
 
 - **Bot Score** (`cf.bot_management.score`): An integer between 1-99 that indicates [Cloudflare's level of certainty](/bots/concepts/bot-score/) that a request comes from a bot.
-- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot.
-
-  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service.
-
+- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot. 
+  
+  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service. 
+  
   We also use additional validation methods, including checking ASN blocks and public lists. If these methods are unavailable, Cloudflare utilizes internal data and machine learning to identify and verify legitimate IP addresses from good bots. Most customers choose to [allow this traffic](/ruleset-engine/rules-language/fields/reference/cf.bot_management.verified_bot/).
-
 - **Serves Static Resource** (`cf.bot_management.static_resource`): An identifier that matches [file extensions](/bots/additional-configurations/static-resources/) for many types of static resources. Use this variable if you send emails that retrieve static images.
 - **ja3Hash** (`cf.bot_management.ja3_hash`) and **ja4** (`cf.bot_management.ja4`): A [**JA3/JA4 fingerprint**](/bots/additional-configurations/ja3-ja4-fingerprint/) helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
 - **Bot Detection IDs** (`cf.bot_management.detection_ids`): List of IDs that correlate to the Bot Management heuristic detections made on a request (you can have multiple heuristic detections on the same request).
diff --git a/src/content/docs/bots/reference/bot-verification/index.mdx b/src/content/docs/bots/reference/bot-verification/index.mdx
index ea311232d0c71de..c074fd2973d2c84 100644
--- a/src/content/docs/bots/reference/bot-verification/index.mdx
+++ b/src/content/docs/bots/reference/bot-verification/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 1
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's validation methods for [Verified](/bots/concepts/bot/verified-bots/) and [Signed](/bots/concepts/bot/signed-agents/) bots.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
index e21b0eabee315f3..9d65f3cb32d07cf 100644
--- a/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
+++ b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx
@@ -5,11 +5,12 @@ description: Verify bot identity by matching request IP addresses against publis
 products:
   - bots
 sidebar:
-  order: 3
-  label: IP validation
+    order: 3
+    label: IP validation
+
 ---
 
-import { GlossaryTooltip, Steps } from "~/components";
+import { GlossaryTooltip, Steps } from "~/components"
 
 The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. IP validation is only used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/).
 
@@ -56,4 +57,4 @@ Generic user-agents include:
 - `node-fetch`
 - `okhttp`
 - `python-requests`
-- `uTorrent`
+- `uTorrent`
\ No newline at end of file
diff --git a/src/content/docs/bots/reference/index.mdx b/src/content/docs/bots/reference/index.mdx
index f157689e81141cc..d98d7d7b81bce95 100644
--- a/src/content/docs/bots/reference/index.mdx
+++ b/src/content/docs/bots/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's bot solutions:
 
diff --git a/src/content/docs/bots/reference/machine-learning-models.mdx b/src/content/docs/bots/reference/machine-learning-models.mdx
index bdaac08a260b29c..49af33d0da4309d 100644
--- a/src/content/docs/bots/reference/machine-learning-models.mdx
+++ b/src/content/docs/bots/reference/machine-learning-models.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
 tags:
   - AI
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Enable auto-updates to the Machine Learning models
 
@@ -38,4 +39,4 @@ By not updating to the latest version, you will be using a Machine Learning mode
 | v6      | Significantly improved scoring for native Android application traffic. <br/><br/>Improved scoring on the newest versions of Chromium browsers.                                                                                              | Q1 2022     |
 | v7      | Increased recognition of distributed botnets. <br/><br/>Improved HTTP/3 scoring.                                                                                                                                                            | Q1 2024     |
 | v8      | Improved detection of residential proxies. <br/><br/>Increased weight on network level traffic characteristics.                                                                                                                             | Q2 2024     |
-| v9      | Improved model consistency and model efficacy against randomization attack techniques                                                                                                                                                       | Q2 2025     |
+| v9      | Improved model consistency and model efficacy against randomization attack techniques | Q2 2025     |
diff --git a/src/content/docs/bots/reference/sample-terms.mdx b/src/content/docs/bots/reference/sample-terms.mdx
index 2ba93ce64ee1935..3c05cc2e80dd3e8 100644
--- a/src/content/docs/bots/reference/sample-terms.mdx
+++ b/src/content/docs/bots/reference/sample-terms.mdx
@@ -8,6 +8,7 @@ sidebar:
   order: 5
 tags:
   - AI
+
 ---
 
 Cloudflare recommends that customers consider updating their Terms of Service to address bots specifically related to Artificial Intelligence (AI) training and data scraping. The text below provides an informational example of the kind of language that could be added to a website's terms of use.
@@ -18,7 +19,8 @@ Cloudflare recommends that customers consider updating their Terms of Service to
 
 :::caution[Disclaimer]
 
-This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome.
+This language is provided for informational purposes only. It does not constitute legal advice, nor does it guarantee any specific outcome. 
 
-This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file.
+This is an illustrative example of language that can be included in a website's terms to put AI providers on notice that they are not authorized to use automated means to scrape content from your website for purposes of training or otherwise contributing to their AI models or systems, unless you have expressly permitted them to do so in your `robots.txt` file. 
 :::
+
diff --git a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
index b8453361111ca0c..363aa1c84d09636 100644
--- a/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
+++ b/src/content/docs/bots/troubleshooting/bot-management-skips.mdx
@@ -6,9 +6,10 @@ products:
   - bots
 sidebar:
   order: 1
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/additional-configurations/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
 
diff --git a/src/content/docs/bots/troubleshooting/false-positives.mdx b/src/content/docs/bots/troubleshooting/false-positives.mdx
index 7d7dadcae903c10..377e7ac13199bff 100644
--- a/src/content/docs/bots/troubleshooting/false-positives.mdx
+++ b/src/content/docs/bots/troubleshooting/false-positives.mdx
@@ -7,6 +7,7 @@ products:
 sidebar:
   order: 3
   label: False positives
+
 ---
 
 import { Render } from "~/components";
@@ -24,4 +25,4 @@ You cannot bypass or skip Bot Fight Mode using the _Skip_ action in WAF custom r
 
 Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.
 
-If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
+If you encounter persistent false positives, you can [disable the feature in the Cloudflare dashboard](/bots/get-started/bot-fight-mode/#disable-bot-fight-mode).
\ No newline at end of file
diff --git a/src/content/docs/bots/troubleshooting/index.mdx b/src/content/docs/bots/troubleshooting/index.mdx
index 821d9ed42c52b76..b1e6d5b78a345c4 100644
--- a/src/content/docs/bots/troubleshooting/index.mdx
+++ b/src/content/docs/bots/troubleshooting/index.mdx
@@ -12,10 +12,12 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot issues with Bots
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to troubleshoot issues with Cloudflare's bot solutions:
 
 <DirectoryListing />
+
diff --git a/src/content/docs/bots/workers-templates/index.mdx b/src/content/docs/bots/workers-templates/index.mdx
index 6bf57e8cbfb768f..aae030a3a8b29b2 100644
--- a/src/content/docs/bots/workers-templates/index.mdx
+++ b/src/content/docs/bots/workers-templates/index.mdx
@@ -12,9 +12,10 @@ sidebar:
 head:
   - tag: title
     content: Workers templates
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the templates below to integrate Bot Management with [Cloudflare Workers](/workers/):
 
diff --git a/src/content/docs/browser-run/features/index.mdx b/src/content/docs/browser-run/features/index.mdx
index 8f79040189134a4..6ef34df2029deea 100644
--- a/src/content/docs/browser-run/features/index.mdx
+++ b/src/content/docs/browser-run/features/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/browser-run/how-to/deploy-worker.mdx b/src/content/docs/browser-run/how-to/deploy-worker.mdx
index d15deee8a1e1894..808b712441c47df 100644
--- a/src/content/docs/browser-run/how-to/deploy-worker.mdx
+++ b/src/content/docs/browser-run/how-to/deploy-worker.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 1
 products:
   - browser-run
-  - workers
+  - workers 
 ---
 
 import {
diff --git a/src/content/docs/browser-run/mcp-server.mdx b/src/content/docs/browser-run/mcp-server.mdx
index a79dc14dcabbbb1..3d7ba05eaeadd22 100644
--- a/src/content/docs/browser-run/mcp-server.mdx
+++ b/src/content/docs/browser-run/mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 90
 products:
   - browser-run
----
+---
\ No newline at end of file
diff --git a/src/content/docs/browser-run/quick-actions/api-reference.mdx b/src/content/docs/browser-run/quick-actions/api-reference.mdx
index dc44d9a5ba8d2e4..15e3e787ca1f282 100644
--- a/src/content/docs/browser-run/quick-actions/api-reference.mdx
+++ b/src/content/docs/browser-run/quick-actions/api-reference.mdx
@@ -4,7 +4,7 @@ title: Reference
 description: View the complete Browser Run Quick Actions API reference for all available endpoints and parameters.
 external_link: /api/resources/browser_rendering/
 sidebar:
-  order: 15
+ order: 15
 products:
   - browser-run
 ---
diff --git a/src/content/docs/browser-run/reference/browser-close-reasons.mdx b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
index cfb411b73a356c1..3fe11accbc5a78a 100644
--- a/src/content/docs/browser-run/reference/browser-close-reasons.mdx
+++ b/src/content/docs/browser-run/reference/browser-close-reasons.mdx
@@ -24,13 +24,13 @@ Browser Run sessions are billed based on [usage](/browser-run/pricing/). We do n
 
 ## Close reasons
 
-| Reason               | Description                                                                                                                                                                                                                                                                        |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Normal closure**   | Your code called `browser.close()` and the session ended normally. No action needed.                                                                                                                                                                                               |
-| **Browser idle**     | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
-| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks.                               |
-| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block.                                                    |
-| **Session evicted**  | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic.                                                                            |
+| Reason | Description |
+| --- | --- |
+| **Normal closure** | Your code called `browser.close()` and the session ended normally. No action needed. |
+| **Browser idle** | The session received no commands for the configured inactivity timeout (60 seconds by default, up to 10 minutes with [`keep_alive`](/browser-run/puppeteer/#keep-alive)). To prevent idle closures, send commands within the inactivity window or increase the `keep_alive` value. |
+| **Chromium crashed** | The Chromium instance inside the session crashed, often because the page consumed too much memory (large DOMs, heavy JavaScript, or many concurrent pages). Try reducing page complexity, closing unused pages, or breaking work into smaller tasks. |
+| **Connection error** | The connection between the client and Browser Run was interrupted. This can be caused by network issues, your Worker reaching its CPU time limit, or a WebSocket disconnection. Retry the operation with a `try...catch` block. |
+| **Session evicted** | Browser Run recycled the session due to infrastructure maintenance or a new release deployment. This is not caused by your code. Retry the operation with a `try...catch` block and reconnection logic. |
 
 ## Handling unexpected closures
 
@@ -38,18 +38,18 @@ Sessions can close at any time due to infrastructure events, network issues, or
 
 ```js
 async function runBrowser(env) {
-	let browser;
-	try {
-		browser = await puppeteer.launch(env.MYBROWSER);
-		const page = await browser.newPage();
-		await page.goto("https://example.com");
-		// Your browser automation logic
-	} catch (error) {
-		console.error("Browser session ended unexpectedly:", error.message);
-		// Retry or return an error response
-	} finally {
-		await browser?.close();
-	}
+  let browser;
+  try {
+    browser = await puppeteer.launch(env.MYBROWSER);
+    const page = await browser.newPage();
+    await page.goto("https://example.com");
+    // Your browser automation logic
+  } catch (error) {
+    console.error("Browser session ended unexpectedly:", error.message);
+    // Retry or return an error response
+  } finally {
+    await browser?.close();
+  }
 }
 ```
 
@@ -57,13 +57,13 @@ For long-running or critical workflows, consider adding retry logic:
 
 ```js
 async function runWithRetry(env, maxRetries = 3) {
-	for (let attempt = 1; attempt <= maxRetries; attempt++) {
-		try {
-			return await runBrowser(env);
-		} catch (error) {
-			if (attempt === maxRetries) throw error;
-			console.log(`Attempt ${attempt} failed, retrying...`);
-		}
-	}
+  for (let attempt = 1; attempt <= maxRetries; attempt++) {
+    try {
+      return await runBrowser(env);
+    } catch (error) {
+      if (attempt === maxRetries) throw error;
+      console.log(`Attempt ${attempt} failed, retrying...`);
+    }
+  }
 }
 ```
diff --git a/src/content/docs/byoip/address-maps/setup.mdx b/src/content/docs/byoip/address-maps/setup.mdx
index 4ded8d833123a77..9e80f9aa794cc37 100644
--- a/src/content/docs/byoip/address-maps/setup.mdx
+++ b/src/content/docs/byoip/address-maps/setup.mdx
@@ -11,13 +11,7 @@ sidebar:
   label: Setup
 ---
 
-import {
-	GlossaryTooltip,
-	APIRequest,
-	DashButton,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { GlossaryTooltip, APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 Consider the sections below to learn how to set up address maps.
 
@@ -126,13 +120,13 @@ Default SNI for Spectrum can only be created via API using the [Create Address M
 Do not include any membership in your command. Your API command should resemble the following:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/address_maps"
-	method="POST"
-	json={{
-		description: "default_sni",
-		default_sni: "sni.example.com",
-		enabled: false,
-		ips: ["192.0.0.1"],
-		memberships: [],
+  path="/accounts/{account_id}/addressing/address_maps"
+  method="POST"
+  json={{
+		"description": "default_sni",
+		"default_sni": "sni.example.com",
+		"enabled": false,
+		"ips": ["192.0.0.1"],
+		"memberships": [],
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/byoip/changelog.mdx b/src/content/docs/byoip/changelog.mdx
index bee100a7b07c3bc..389731c7bfc427f 100644
--- a/src/content/docs/byoip/changelog.mdx
+++ b/src/content/docs/byoip/changelog.mdx
@@ -14,4 +14,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/byoip.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductReleaseNotes />
+<ProductReleaseNotes />
\ No newline at end of file
diff --git a/src/content/docs/byoip/concepts/index.mdx b/src/content/docs/byoip/concepts/index.mdx
index 7a7f4b5b8de1b6d..646653a0d44f0e6 100644
--- a/src/content/docs/byoip/concepts/index.mdx
+++ b/src/content/docs/byoip/concepts/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the topics below for more information about concepts related to BYOIP.
 
diff --git a/src/content/docs/byoip/concepts/prefix-delegations.mdx b/src/content/docs/byoip/concepts/prefix-delegations.mdx
index 2c7fa214ed734aa..65ddd820ea83124 100644
--- a/src/content/docs/byoip/concepts/prefix-delegations.mdx
+++ b/src/content/docs/byoip/concepts/prefix-delegations.mdx
@@ -10,6 +10,7 @@ sidebar:
 
 Prefix delegations allow a prefix owner (Account A) to grant another Cloudflare account (Account B) permission to use all or part of their BYOIP prefix. The original prefix remains managed by Account A, but Account B can use the delegated IPs with CDN services (including Cloudflare for SaaS) or Spectrum. Refer to [service bindings](/byoip/service-bindings/) for more information on the services an IP can be bound to.
 
+
 ## CDN
 
 CDN delegations allow you to use the IP(s) with [Address Maps](/byoip/address-maps/) or [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) customers.
diff --git a/src/content/docs/byoip/glossary.mdx b/src/content/docs/byoip/glossary.mdx
index 21eb58070060e3a..8b3f72c3e98e200 100644
--- a/src/content/docs/byoip/glossary.mdx
+++ b/src/content/docs/byoip/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 12
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's BYOIP documentation.
 
diff --git a/src/content/docs/byoip/route-leak-detection.mdx b/src/content/docs/byoip/route-leak-detection.mdx
index b42d00458f0abed..7b25fea18deee8c 100644
--- a/src/content/docs/byoip/route-leak-detection.mdx
+++ b/src/content/docs/byoip/route-leak-detection.mdx
@@ -6,9 +6,10 @@ products:
   - byoip
 sidebar:
   order: 8
+
 ---
 
-import { AvailableNotifications, DashButton } from "~/components";
+import { AvailableNotifications, DashButton } from "~/components"
 
 Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
 
diff --git a/src/content/docs/byoip/service-bindings/index.mdx b/src/content/docs/byoip/service-bindings/index.mdx
index 51ae83d822bc673..0078224d0428db2 100644
--- a/src/content/docs/byoip/service-bindings/index.mdx
+++ b/src/content/docs/byoip/service-bindings/index.mdx
@@ -79,5 +79,4 @@ When adding a service binding for a given IP address, it must be either a CDN se
 <DirectoryListing />
 
 [^1]: Layer 7 HTTP-based
-
-[^2]: Layer 4 or Layer 7 HTTP with custom ports
+[^2]: Layer 4 or Layer 7 HTTP with custom ports
\ No newline at end of file
diff --git a/src/content/docs/byoip/troubleshooting/index.mdx b/src/content/docs/byoip/troubleshooting/index.mdx
index b83821670151137..c3c66603d15744f 100644
--- a/src/content/docs/byoip/troubleshooting/index.mdx
+++ b/src/content/docs/byoip/troubleshooting/index.mdx
@@ -36,12 +36,13 @@ Instead, you can use Address Maps to set a default SNI for IPs on your account o
 
 When onboarding BYOIP prefixes via the API, you may encounter the following errors:
 
-| Error code                      | Meaning                                                                                                     | Resolution                                                                                                                                                                                                                                                                             |
-| ------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Error code | Meaning | Resolution |
+|---|---|---|
 | `prefix_not_valid_and_approved` | The prefix has not passed IRR validation, RPKI validation, and ownership verification (or manual approval). | Verify all three validation steps have completed. If one or more are failing, check prefix registration with your Regional Internet Registry (RIR) and your RPKI ROA configuration. If validation is passing but you are still seeing this error, contact support for manual approval. |
-| `incomplete_bgp_deployment`     | Cannot create a BGP prefix without a default edge service binding configured.                               | Configure a default edge service binding before creating BGP prefixes.                                                                                                                                                                                                                 |
-| `advertise_state_locked`        | Cannot create a BGP prefix — the default edge service binding is still deploying.                           | Wait for the edge service binding deployment to complete, then retry.                                                                                                                                                                                                                  |
+| `incomplete_bgp_deployment` | Cannot create a BGP prefix without a default edge service binding configured. | Configure a default edge service binding before creating BGP prefixes. |
+| `advertise_state_locked` | Cannot create a BGP prefix — the default edge service binding is still deploying. | Wait for the edge service binding deployment to complete, then retry. |
 
 :::note
 Self-serve BYOIP onboarding is not supported when BYOIP is used as a Magic Transit on-ramp configuration. For more information, refer to [Magic Transit with CDN](/byoip/service-bindings/magic-transit-with-cdn/).
 :::
+
diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
index 4e48745c1d36d41..5bd9e4060218ead 100644
--- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
+++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
@@ -105,7 +105,10 @@ For example:
 
 ### Operations
 
-<Render file="cache-reserve-operations" product="cache" />
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>
 
 ## Cache Reserve billing examples
 
@@ -149,10 +152,10 @@ Cache Reserve is designed for use with [Tiered Cache](/cache/how-to/tiered-cache
 ## Cache Reserve Analytics
 
 <Render
-	file="cache-reserve-analytics"
+  file="cache-reserve-analytics"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
diff --git a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
index e94802d8e09921e..22a7ef8c9ba65a7 100644
--- a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
@@ -4,9 +4,10 @@ description: Signal search engine crawlers when content changes with IndexNow.
 products:
   - cache
 title: Crawler Hints
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Crawler Hints uses Cloudflare cache signals to tell search engines when your content has likely changed, so they crawl your site at the right time instead of guessing.
 
@@ -40,6 +41,6 @@ After enabling Crawler Hints, Cloudflare will begin sending hints to search engi
 
 When enabled, Crawler Hints is a global setting for your entire website. You can stop a specific page from being indexed by either:
 
-- Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
-- Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
-- Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
+* Having the origin server send through the header `X-Robots-Tag: noindex` on any pages that should not be indexed.
+* Including `<meta name="robots" content="noindex, nofollow" />` in the HTML of any pages that should not be indexed.
+* Creating a [Response header Transform Rule](/rules/transform/response-header-modification/) in Cloudflare to add the `X-Robots-Tag: noindex` header instead of doing it from the origin server.
diff --git a/src/content/docs/cache/advanced-configuration/early-hints.mdx b/src/content/docs/cache/advanced-configuration/early-hints.mdx
index cc491452932a8a8..0dbc92752839ea9 100644
--- a/src/content/docs/cache/advanced-configuration/early-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/early-hints.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Preload assets with 103 Early Hints to speed up page loads.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 When a browser requests a page, the origin server takes time to prepare the full response. Early Hints uses this wait time to send the browser a preliminary `103` response containing `Link` headers that tell the browser which assets it will need. The browser can start loading those assets before the full response arrives, which speeds up page loads.
 
@@ -14,8 +15,10 @@ Early Hints is defined in [RFC 8297](https://httpwg.org/specs/rfc8297.html) as a
 
 :::note[Note]
 
+
 Early Hints is currently only supported over HTTP/2 and HTTP/3.
 
+
 :::
 
 For more information about Early Hints, refer to the [Cloudflare](https://blog.cloudflare.com/early-hints) and [Google Chrome](https://developer.chrome.com/en/blog/early-hints/) blogs.
@@ -37,14 +40,16 @@ For more information about Early Hints, refer to the [Cloudflare](https://blog.c
 
 Early Hints are only generated and cached:
 
-- For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
-- On 200, 301, or 302 response return codes
-- When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
+* For URIs with `.html`, `.htm`, or `.php` file extensions, or no file extension
+* On 200, 301, or 302 response return codes
+* When the response contains [link headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link) with preconnect or preload rel types, such as `Link: </img/preloaded.png>; rel=preload`
 
 :::note
 
+
 Early Hints cache entries are keyed by request URI and ignore query strings.
 
+
 :::
 
 ## Emit Early Hints
@@ -55,7 +60,7 @@ Currently, only certain browser versions will take action to preload or preconne
 
 Additionally, keep the following in mind:
 
-- Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
-- Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
-- Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
-- You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
+* Early Hints responses may be emitted before reaching the origin server or Worker. When Early Hints is enabled and pages on your site require authentication, unauthenticated visitors may receive a 103 response. The 103 response would contain cached Link headers and be sent before a 403 Forbidden response from your origin.
+* Early Hints may be emitted less frequently on requests where the content is cacheable. Cloudflare CDN is more likely to retrieve a response header before the asynchronous Early Hints lookup finishes if the response has been cached. Cloudflare will not send a 103 response if the main response header is already available.
+* Cloudflare currently disables Early Hints on some User-Agents, for example, select search crawler bots that show incompatibility with 1xx responses.
+* You may see an influx of `504` responses with the `RequestSource` of `earlyHintsCache` in Cloudflare Logs when Early Hints is enabled, which is expected and benign. Requests from `earlyHintsCache` are internal subrequests for cached Early Hints, and they are neither end user requests, nor do they go to your origin. Their response status only indicates whether there are cached Early Hints for the request URI (`200` on cache HIT, `504` on cache MISS). These requests are already filtered out in other views, such as Cache Analytics. To filter out these requests or to filter requests by end users of your website only, please refer to [Filter end users](/analytics/graphql-api/features/filtering/#filter-end-users).
diff --git a/src/content/docs/cache/advanced-configuration/index.mdx b/src/content/docs/cache/advanced-configuration/index.mdx
index 12fa7c03f59e222..9efd5cc15381ed7 100644
--- a/src/content/docs/cache/advanced-configuration/index.mdx
+++ b/src/content/docs/cache/advanced-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
index 05e6363b11a6dad..0b41b69eb776303 100644
--- a/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
+++ b/src/content/docs/cache/advanced-configuration/query-string-sort.mdx
@@ -9,14 +9,14 @@ tags:
   - WordPress
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 **Query String Sort** increases cache-hit rates by first sorting query strings into a consistent order before checking the Cloudflare cache.
 
 By default, Cloudflare’s cache treats resources as distinct if their URL query strings are in a different order. For instance, these resources are cached separately:
 
-- `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
-- `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
+* `/video/48088296?title=0&byline=0&portrait=0&color=51a516`
+* `/video/48088296?byline=0&color=51a516&portrait=0&title=0`
 
 Query String Sort changes this behavior. If two query strings exist with the same name, the URL is sorted by the parameter value. For example:
 
@@ -30,7 +30,7 @@ would be sorted to:
 
 <FeatureTable id="cache.query_string_sort" />
 
----
+***
 
 ## Enable Query String Sort
 
@@ -41,7 +41,7 @@ To enable Query String Sort:
 3. Go to **Caching** > **Configuration**.
 4. For **Enable Query String Sort**, switch the toggle to **On**.
 
----
+***
 
 ## Unexpected behavior with WordPress admin pages
 
@@ -49,17 +49,19 @@ When a site or an application requires exact query string ordering, enabling Que
 
 For example in the WordPress admin UI, you might notice any of the following behaviors:
 
-- No media appear in the Media Library
-- Inability to customize the site via **Appearance** > **Customize**
-- Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
-- Inability to edit menus in **Appearance** > **Menus**
+* No media appear in the Media Library
+* Inability to customize the site via **Appearance** > **Customize**
+* Inability to drag any widget to a sidebar in **Appearance** > **Widgets**
+* Inability to edit menus in **Appearance** > **Menus**
 
 To understand why this happens, note that WordPress [concatenates JavaScript files](https://developer.wordpress.org/advanced-administration/wordpress/wp-config/#disable-javascript-concatenation) to speed up the administration interface. The way WordPress implements this involves multiple occurrences of `load[]` parameters in the query string, where the order of those parameters is crucial.
 
 :::note
 
+
 Note that more recent versions of WordPress may not experience this issue, as a patch has been implemented in WordPress since 2019. The patch can be found at [WordPress Core Trac Changeset 45456](https://core.trac.wordpress.org/changeset/45456).
 
+
 :::
 
 ### Identify the problem
@@ -98,15 +100,15 @@ For example, you might have an image resizing endpoint or a search form, where t
 
 To minimize problems, consider:
 
-- Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
-- Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
-- Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
+* Disabling **Query String Sort** for the site if you’re sure that this feature does not add value to any part of your site. Cloudflare disables this option by default in the **Caching** app.
+* Use Cache Rules to enable **Query String Sort** (set **Cache key** > **Sort query string**: `On`) for URLs where preserving the query string parameter order is not important.
+* Alternatively, use Cache Rules to disable **Query String Sort** for URLs where a specific parameter order is required. For example, set **Cache key** > **Sort query string**: `Off` for URI paths starting with `/wp-admin/load-scripts.php`, or for any URLs with similar requirements.
 
 To learn more about Cache Rules, visit [Cache Rules](/cache/how-to/cache-rules/).
 
----
+***
 
 ## Related resources
 
-- [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
-- [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
+* [Increasing Cache Hit Rates with Query String Sort](https://blog.cloudflare.com/increasing-cache-hit-rates-with-query-string-sort/)
+* [Best Practice: Caching Everything While Ignoring Query Strings](/cache/how-to/cache-rules/examples/cache-everything-ignore-query-strings/)
diff --git a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
index 4f0f14a99828213..8d6b138d7f117d2 100644
--- a/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
+++ b/src/content/docs/cache/advanced-configuration/serve-tailored-content.mdx
@@ -42,8 +42,8 @@ In this example, you run an e-commerce site and want to display prices in the lo
    - **Operator:** `equals`
    - **Value:** `Canada`
 6. Under **Then...**
-   - for **Path**, select **Preserve**.
-   - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
+    - for **Path**, select **Preserve**.
+    - for **Query**, select **Rewrite to**: **Dynamic** `loc=ca`
 7. Select **Save**.
 
 Now, requests from Canada to `/products/item` will be transformed to `/products/item?loc=ca` before reaching your origin or the cache, creating a distinct cache entry.
@@ -65,14 +65,14 @@ To enable this feature, create a _variants rule_ using the API. This rule maps f
 For example, the following API call tells Cloudflare that for `.jpeg` and `.jpg` files, your origin can serve `image/webp` and `image/avif` variants:
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp", "image/avif"],
-			jpg: ["image/webp", "image/avif"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp", "image/avif"],
+      jpg: ["image/webp", "image/avif"]
+    }
+  }}
 />
 
 After creating the rule, Cloudflare will create distinct cache entries for each image variant, improving performance for users with modern browsers.
@@ -100,27 +100,26 @@ In this example, you run an A/B test controlled by a cookie named `ab-test` (wit
 const CACHE_DURATION = 30 * 24 * 60 * 60; // 30 days
 
 export default {
-	async fetch(request) {
-		// Construct a new URL for the cache key based on the A/B cookie
-		const abCookie =
-			request.headers.get("Cookie")?.match(/ab-test=([^;]+)/)?.[1] || "control";
-		const url = new URL(request.url);
-		url.pathname = `/ab-test/${abCookie}${url.pathname}`;
-
-		const cacheKey = new Request(url, request);
-		const cache = caches.default;
-
-		let response = await cache.match(cacheKey);
-		if (!response) {
-			// If not in cache, fetch from origin
-			response = await fetch(request);
-			response = new Response(response.body, response);
-			response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
-			// Put the response into cache with the custom key
-			await cache.put(cacheKey, response.clone());
-		}
-		return response;
-	},
+  async fetch(request) {
+    // Construct a new URL for the cache key based on the A/B cookie
+    const abCookie = request.headers.get('Cookie')?.match(/ab-test=([^;]+)/)?.[1] || 'control';
+    const url = new URL(request.url);
+    url.pathname = `/ab-test/${abCookie}${url.pathname}`;
+
+    const cacheKey = new Request(url, request);
+    const cache = caches.default;
+
+    let response = await cache.match(cacheKey);
+    if (!response) {
+      // If not in cache, fetch from origin
+      response = await fetch(request);
+      response = new Response(response.body, response);
+      response.headers.set("Cache-Control", `s-maxage=${CACHE_DURATION}`);
+      // Put the response into cache with the custom key
+      await cache.put(cacheKey, response.clone());
+    }
+    return response;
+  },
 };
 ```
 
@@ -152,13 +151,13 @@ If your origin serves different content types (for example, `application/json` v
    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
-3. Enter rule name, such as `Vary by Accept Header`.
+3. Enter  rule name, such as `Vary by Accept Header`.
 4. Set the condition for the rule to apply (for example, a specific hostname or path).
 5. Under **Cache key**, select **Use custom key**.
 6. Select **Add new**.
-   - **Type**: `Header`
-   - **Name**: `Accept`
-   - **Value**: Add each `value`, or leave empty for all.
+    - **Type**: `Header`
+    - **Name**: `Accept`
+    - **Value**: Add each `value`, or leave empty for all.
 7. Select **Deploy**.
 
 This configuration creates separate cache entries based on the `Accept` header value, respecting your API's content negotiation.
@@ -177,28 +176,28 @@ This Worker detects whether a visitor is on a mobile or desktop device and creat
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		const userAgent = request.headers.get("User-Agent") || "";
-		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
+  async fetch(request, env, ctx) {
+    const userAgent = request.headers.get('User-Agent') || '';
+    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
 
-		// Create a new URL for the cache key that includes the device type
-		const url = new URL(request.url);
-		url.pathname = `/${deviceType}${url.pathname}`;
+    // Create a new URL for the cache key that includes the device type
+    const url = new URL(request.url);
+    url.pathname = `/${deviceType}${url.pathname}`;
 
-		const cacheKey = new Request(url, request);
-		const cache = caches.default;
+    const cacheKey = new Request(url, request);
+    const cache = caches.default;
 
-		let response = await cache.match(cacheKey);
+    let response = await cache.match(cacheKey);
 
-		if (!response) {
-			console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
-			response = await fetch(request);
-			let responseToCache = response.clone();
-			ctx.waitUntil(cache.put(cacheKey, responseToCache));
-		}
+    if (!response) {
+      console.log(`Cache miss for ${deviceType} device. Fetching from origin.`);
+      response = await fetch(request);
+      let responseToCache = response.clone();
+      ctx.waitUntil(cache.put(cacheKey, responseToCache));
+    }
 
-		return response;
-	},
+    return response;
+  },
 };
 ```
 
@@ -212,28 +211,28 @@ This Worker detects if a visitor is on a mobile device or a desktop and creates
 
 ```js
 export default {
-	async fetch(request) {
-		// 1. Determine the device type from the User-Agent header
-		const userAgent = request.headers.get("User-Agent") || "";
-		const deviceType = userAgent.includes("Mobile") ? "mobile" : "desktop";
-
-		// 2. Create a custom cache key by appending the device type to the URL
-		const customCacheKey = `${request.url}-${deviceType}`;
-
-		// 3. Fetch the response. Cloudflare's cache automatically uses the
-		//    customCacheKey for cache operations (match, put).
-		const response = await fetch(request, {
-			cf: {
-				cacheKey: customCacheKey,
-			},
-		});
-
-		// Optionally, you can modify the response before returning it
-		// For example, add a header to indicate which cache key was used
-		const newResponse = new Response(response.body, response);
-		newResponse.headers.set("X-Cache-Key", customCacheKey);
-		return newResponse;
-	},
+  async fetch(request) {
+    // 1. Determine the device type from the User-Agent header
+    const userAgent = request.headers.get('User-Agent') || '';
+    const deviceType = userAgent.includes('Mobile') ? 'mobile' : 'desktop';
+
+    // 2. Create a custom cache key by appending the device type to the URL
+    const customCacheKey = `${request.url}-${deviceType}`;
+
+    // 3. Fetch the response. Cloudflare's cache automatically uses the
+    //    customCacheKey for cache operations (match, put).
+    const response = await fetch(request, {
+      cf: {
+        cacheKey: customCacheKey,
+      },
+    });
+
+    // Optionally, you can modify the response before returning it
+    // For example, add a header to indicate which cache key was used
+    const newResponse = new Response(response.body, response);
+    newResponse.headers.set("X-Cache-Key", customCacheKey);
+    return newResponse;
+  },
 };
 ```
 
@@ -257,11 +256,11 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 3. Enter a name, such as `Vary by RSC Header`.
 4. In **If incoming requests match**, select **Custom filter expression**.
 5. Under **When incoming requests match**, manually edit the expression so that it checks for the presence of the `RSC` header:
-   - `has_key(http.request.headers, "rsc")`
+    - `has_key(http.request.headers, "rsc")`
 
 6. Under **Then**:
-   - For **Path**, select **Preserve**.
-   - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
+    - For **Path**, select **Preserve**.
+    - For **Query**, select **Rewrite to**, select **Static**: `_rsc=1`.
 
 7. Select **Save**.
 
@@ -270,7 +269,8 @@ The simplest solution is to create a [Transform Rule](/rules/transform/) that ch
 Alternatively, use [Snippets](/rules/snippets/) or [Custom Cache Keys](/cache/how-to/cache-keys) to add the `RSC` header directly to the cache key without modifying the visible URL. This provides a cleaner URL but requires more advanced configuration.
 
 :::note[Availability]
-
 - Snippets: Pro, Business, Enterprise
 - Custom Cache Keys: Enterprise only
-  :::
+:::
+
+
diff --git a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
index 1209ddf6440e3ee..ab7ed953aa09229 100644
--- a/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
+++ b/src/content/docs/cache/advanced-configuration/vary-for-images.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Serve images in the best format for each visitor browser.
 products:
   - cache
+
 ---
 
-import { Details, FeatureTable, APIRequest } from "~/components";
+import { Details, FeatureTable, APIRequest } from "~/components"
 
 The `Vary` HTTP response header tells Cloudflare that an origin can serve different versions of the same resource depending on the request headers. For images, this allows your origin to serve modern formats like WebP or AVIF to browsers that support them, while continuing to serve JPEG or PNG to others.
 
@@ -24,19 +25,20 @@ Vary for images is available for Pro, Business, and Enterprise customers.
 
 You can use vary for images on the file extensions below if the origin server sends the `Vary: Accept` response header. If the origin server sends `Vary: Accept` but does not serve the set variant, the response is not cached and displays `BYPASS` in the cache status in the response header. Additionally, the list of variant types the origin serves for each extension must be configured so that Cloudflare decides which variant to serve without contacting the origin server.
 
+
 <Details header="File extensions enabled for varying">
-	<ul>
-		<li>.avif</li>
-		<li>.bmp</li>
-		<li>.gif</li>
-		<li>.jpg</li>
-		<li>.jpeg</li>
-		<li>.jp2</li>
-		<li>.png</li>
-		<li>.tif</li>
-		<li>.tiff</li>
-		<li>.webp</li>
-	</ul>
+  <ul>
+    <li>.avif</li>
+    <li>.bmp</li>
+    <li>.gif</li>
+    <li>.jpg</li>
+    <li>.jpeg</li>
+    <li>.jp2</li>
+    <li>.png</li>
+    <li>.tif</li>
+    <li>.tiff</li>
+    <li>.webp</li>
+  </ul>
 </Details>
 
 ## Enable vary for images
@@ -46,40 +48,46 @@ Vary for Images is enabled through Cloudflare's API by creating a variants rule.
 ### Create a variants rule
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp", "image/avif"],
-			jpg: ["image/webp", "image/avif"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp", "image/avif"],
+      jpg: ["image/webp", "image/avif"]
+    }
+  }}
 />
 
 ### Modify to only allow WebP variants
 
 <APIRequest
-	path="/zones/{zone_id}/cache/variants"
-	method="PATCH"
-	json={{
-		value: {
-			jpeg: ["image/webp"],
-			jpg: ["image/webp"],
-		},
-	}}
+  path="/zones/{zone_id}/cache/variants"
+  method="PATCH"
+  json={{
+    value: {
+      jpeg: ["image/webp"],
+      jpg: ["image/webp"]
+    }
+  }}
 />
 
 ### Delete the rule
 
-<APIRequest path="/zones/{zone_id}/cache/variants" method="DELETE" />
+<APIRequest
+  path="/zones/{zone_id}/cache/variants"
+  method="DELETE"
+/>
 
 ### Get the rule
 
-<APIRequest path="/zones/{zone_id}/cache/variants" method="GET" />
+<APIRequest
+  path="/zones/{zone_id}/cache/variants"
+  method="GET"
+/>
 
 To learn more about purging varied images, refer to [Purge varied images](/cache/how-to/purge-cache/purge-varied-images/).
 
 ## Limitations
 
-- For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
-- Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
+* For Vary for images to work, your image URLs must include the file extension in the path and not the query string. For example the URL `https://example.com/image.jpg` is compatible but `https://example.com/index.php?file=image.jpg` is not compatible.
+* Your origin must return an image type matching the file extension in the URL when a HTTP client sends no `Accept` header, or an `Accept: */*` header. Otherwise, you will see `CF-Cache-Status: BYPASS` in the HTTP response headers.
diff --git a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
index f115a63a6b91c56..3978e79c7e9bb20 100644
--- a/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
+++ b/src/content/docs/cache/cache-security/avoid-web-poisoning.mdx
@@ -19,22 +19,22 @@ A Content Delivery Network (CDN) like Cloudflare relies on cache keys to compare
 
 To deepen your understanding of the risks and vulnerabilities associated with cache poisoning, consult the following resources:
 
-- [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
-- [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
+* [Practical Web Cache Poisoning](https://portswigger.net/blog/practical-web-cache-poisoning)
+* [How Cloudflare protects customers from cache poisoning](https://blog.cloudflare.com/cache-poisoning-protection/)
 
 ## Only cache files that are truly static
 
 Review the caching configuration for your origin web server and ensure you are caching files that are static and do not depend on user input in any way. To learn more about Cloudflare caching, review:
 
-- [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
-- [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
+* [Which file extensions does Cloudflare cache for static content?](/cache/concepts/default-cache-behavior/)
+* [How Do I Tell Cloudflare What to Cache?](/cache/how-to/cache-rules/)
 
 ## Do not trust data in HTTP headers
 
 Attackers can exploit HTTP headers to inject malicious content into cached responses. For example, if your application reflects an untrusted header value in the response body, an attacker could use this to perform cross-site scripting (XSS) through the cache. To reduce this risk:
 
-- Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
-- Do not include untrusted header values in your response body.
+* Do not rely on values in HTTP headers if they are not part of your [cache key](/cache/how-to/cache-keys/).
+* Do not include untrusted header values in your response body.
 
 ## Do not trust GET request bodies
 
@@ -44,6 +44,6 @@ Cloudflare caches contents of GET request bodies, but they are not included in t
 
 To keep informed about Internet security threats, Cloudflare recommends that you monitor web security advisories on a regular basis. Some of the more popular advisories include:
 
-- [Drupal Security Advisories](https://www.drupal.org/security)
-- [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
-- [Laminas Security Advisories](https://getlaminas.org/security/advisories)
+* [Drupal Security Advisories](https://www.drupal.org/security)
+* [Symfony Security Advisories](https://symfony.com/blog/category/security-advisories)
+* [Laminas Security Advisories](https://getlaminas.org/security/advisories)
diff --git a/src/content/docs/cache/cache-security/cache-deception-armor.mdx b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
index 2b41dc71ac0ea52..a008458a9255072 100644
--- a/src/content/docs/cache/cache-security/cache-deception-armor.mdx
+++ b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
@@ -24,9 +24,9 @@ In the newsfeed example above, if `http://www.example.com/newsfeed` is a script
 
 ### Exceptions
 
-- If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
-- Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
-- Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
+* If the returned `Content-Type` is `application/octet-stream`, the extension does not matter because that is typically a signal to instruct the browser to save the asset instead of to display it.
+* Cloudflare allows `.jpg` to be served as `image/webp` or `.gif` as `video/webm` and other cases that are unlikely to be attacks.
+* Keep in mind that Cache Deception Armor depends upon [Origin Cache Control](/cache/concepts/cache-control/). A `Cache-Control` header from the origin, or an [Edge Cache TTL Cache Rule](/cache/how-to/cache-rules/settings/#edge-ttl) may override the protection.
 
 ## Enable Cache Deception Armor
 
diff --git a/src/content/docs/cache/cache-security/cors.mdx b/src/content/docs/cache/cache-security/cors.mdx
index 3f70fe69412f798..5f1e357e312c2fe 100644
--- a/src/content/docs/cache/cache-security/cors.mdx
+++ b/src/content/docs/cache/cache-security/cors.mdx
@@ -12,8 +12,8 @@ A cross-origin request occurs when a webpage on one origin (for example, `a.exam
 
 Cloudflare supports CORS by:
 
-- Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
-- Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
+* Identifying cached assets based on the `Host` Header, `Origin` Header, URL path, and query. This allows different resources to use the same `Host` header but different `Origin` headers.
+* Passing `Access-Control-Allow-Origin` headers from the origin server to the browser.
 
 The `Access-Control-Allow-Origin` header lets a server specify rules for sharing its resources with external origins. A server may respond with different `Access-Control-Allow-Origin` values depending on the `Origin` header in the request. These headers are often present on [cacheable content](/cache/concepts/default-cache-behavior/).
 
@@ -21,9 +21,9 @@ The `Access-Control-Allow-Origin` header lets a server specify rules for sharing
 
 If you add or change CORS configuration at your origin web server, purging the Cloudflare cache by URL does not update the CORS headers. Force Cloudflare to retrieve the new CORS headers via one of the following options:
 
-- Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
-- Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
-- Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
+* Change the filename or URL to bypass cache to instruct Cloudflare to retrieve the latest CORS headers.
+* Use the [single-file purge API](/api/resources/cache/methods/purge/#purge-cached-content-by-url) to specify the appropriate CORS headers along with the purge request.
+* Update the resource’s last-modified time at your origin web server. Then, complete a [full purge](/cache/how-to/purge-cache/purge-everything/) to retrieve the latest version of your assets including updated CORS headers.
 
 ## Add or change CORS headers on Cloudflare
 
@@ -32,3 +32,4 @@ You can use one of following methods to set CORS headers using Cloudflare produc
 - Use a [Worker](/workers/): Refer to [CORS header proxy](/workers/examples/cors-header-proxy/) for an example.
 - Configure a [Snippet](/rules/snippets/): Refer to [Define CORS headers](/rules/snippets/examples/define-cors-headers/) for an example.
 - Use [Transform Rules](/rules/transform/): Refer to [Add a wildcard CORS response header](/rules/transform/examples/add-cors-header/) for an example.
+
diff --git a/src/content/docs/cache/cache-security/index.mdx b/src/content/docs/cache/cache-security/index.mdx
index 3287619c54fa92c..6f753ca961b67d0 100644
--- a/src/content/docs/cache/cache-security/index.mdx
+++ b/src/content/docs/cache/cache-security/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following content to learn more about cache security.
 
diff --git a/src/content/docs/cache/concepts/cache-behavior.mdx b/src/content/docs/cache/concepts/cache-behavior.mdx
index ca4b43ee981b90a..212cd5cec8fe30f 100644
--- a/src/content/docs/cache/concepts/cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/cache-behavior.mdx
@@ -11,8 +11,8 @@ tags:
 
 This page describes how Cloudflare's cache system behaves in interaction with:
 
-- `HEAD` requests
-- `Set-Cookie` response headers
+* `HEAD` requests
+* `Set-Cookie` response headers
 
 ## Interaction of `HEAD` requests with Cache
 
@@ -24,8 +24,8 @@ When you make a `HEAD` request for a cacheable resource and Cloudflare does not
 
 For non-cacheable requests, `Set-Cookie` is always preserved. For cacheable requests, there are three possible behaviors:
 
-- `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
+* `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
 
-- `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
+* `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.
 
-- `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
+* `Set-Cookie` is returned from origin, the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules, and edge cache TTL is explicitly set using either the "Ignore cache-control header and use this TTL" or "Status code TTL" setting. In this case, Cloudflare removes the `Set-Cookie` and the asset is cached.
diff --git a/src/content/docs/cache/concepts/cache-responses.mdx b/src/content/docs/cache/concepts/cache-responses.mdx
index 20f1007625c6956..a1f3935e1f26ba9 100644
--- a/src/content/docs/cache/concepts/cache-responses.mdx
+++ b/src/content/docs/cache/concepts/cache-responses.mdx
@@ -7,6 +7,7 @@ products:
 head:
   - tag: title
     content: Cloudflare cache responses
+
 ---
 
 The `CF-Cache-Status` header output indicates whether a resource is cached or not. To investigate cache responses returned by this header, use services like [Redbot](https://redbot.org/), [webpagetest.org](http://www.webpagetest.org/), or a visual tool like [Cloudflare Optics plugin](https://chromewebstore.google.com/detail/cloudflare-optics/mdjgbjnbdnhneejmmaabmccfehigbjbe).
@@ -31,13 +32,13 @@ The resource was not found in Cloudflare's cache and was served from the origin
 
 Cloudflare generated a response that denotes the asset is not eligible for caching. This may have happened because:
 
-- A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
+* A Worker generated a response without sending any subrequests. In this case, the response did not come from cache, so the cache status will be `none/unknown`.
 
-- A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
+* A Worker request made a subrequest (`fetch`). In this case, the subrequest will be logged with a cache status, while the main request will be logged with `none/unknown` status (the main request did not hit cache, since Workers sits in front of cache).
 
-- A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
+* A WAF custom rule was triggered to block a request. The response will come from the Cloudflare global network before it hits cache. Since there is no cache status, Cloudflare will log as `none/unknown`.
 
-- A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
+* A [redirect rule](/rules/url-forwarding/) or [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) caused the global network to respond with a redirect to another asset/URL. This redirect response happens before the request reaches cache, so the cache status is `none/unknown`.
 
 ## EXPIRED
 
diff --git a/src/content/docs/cache/concepts/cdn-cache-control.mdx b/src/content/docs/cache/concepts/cdn-cache-control.mdx
index ae3401ebbb3fa3b..81e86ba54273c84 100644
--- a/src/content/docs/cache/concepts/cdn-cache-control.mdx
+++ b/src/content/docs/cache/concepts/cdn-cache-control.mdx
@@ -18,11 +18,11 @@ If a [Cache Response Rule](/cache/how-to/cache-response-rules/) sets `Cache-Cont
 
 When no Cache Response Rule applies, an origin can:
 
-- Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
+* Return the `CDN-Cache-Control` response header which Cloudflare evaluates to make caching decisions. `Cache-Control`, if also returned by the origin, is proxied as is and does not affect caching decisions made by Cloudflare. Additionally, `CDN-Cache-Control` is proxied downstream in case there are other CDNs between Cloudflare and the browser.
 
-- Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
+* Return the `Cloudflare-CDN-Cache-Control` response header. This results in the same behavior as the origin returning `CDN-Cache-Control` except Cloudflare does not proxy `Cloudflare-CDN-Cache-Control` downstream because it’s a header only used to control Cloudflare. This option is beneficial if you want only Cloudflare to have a different caching behavior while all other downstream servers rely on `Cache-Control` or if you do not want Cloudflare to proxy the `CDN-Cache-Control` header downstream.
 
-- Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
+* Return both `Cloudflare-CDN-Cache-Control` and `CDN-Cache-Control` response headers. In this case, Cloudflare only looks at `Cloudflare-CDN-Cache-Control` when making caching decisions because it is the most specific version of `CDN-Cache-Control` and proxies `CDN-Cache-Control` downstream. Only forwarding `CDN-Cache-Control` in this situation is beneficial if you want Cloudflare to have a different caching behavior than other CDNs downstream.
 
 Additionally, surrogates will not honor `Cache-Control` headers in the response from an origin. For example, if the `Surrogate-Control` header is present within the response, Cloudflare ignores any `Cache-Control` directives, even if the `Surrogate-Control` header does not contain directives.
 
@@ -52,61 +52,61 @@ Use `CDN-Cache-Control` when you want to manage cached asset’s TTLs separately
 
 Headers:
 
-- `Cache-Control: max-age=14400, s-maxage=84000`
-- `Cloudflare-CDN-Cache-Control: max-age=24400`
-- `CDN-Cache-Control: max-age=18000`
+* `Cache-Control: max-age=14400, s-maxage=84000`
+* `Cloudflare-CDN-Cache-Control: max-age=24400`
+* `CDN-Cache-Control: max-age=18000`
 
 Cache behavior:
 
 <table>
-	<tbody>
-		<th colspan="5" rowspan="1">
-			Caches
-		</th>
-		<th colspan="5" rowspan="1">
-			Cache TTL (seconds)
-		</th>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Origin Server Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				14400
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Network Shared Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				84000
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Cloudflare Edge
-			</td>
-			<td colspan="5" rowspan="1">
-				24400
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Other CDNs
-			</td>
-			<td colspan="5" rowspan="1">
-				18000
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Browser Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				14400
-			</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <th colspan="5" rowspan="1">
+      Caches
+    </th>
+    <th colspan="5" rowspan="1">
+      Cache TTL (seconds)
+    </th>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Origin Server Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        14400
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Network Shared Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        84000
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Cloudflare Edge
+      </td>
+      <td colspan="5" rowspan="1">
+        24400
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Other CDNs
+      </td>
+      <td colspan="5" rowspan="1">
+        18000
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Browser Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        14400
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ### Specify when to serve stale content
@@ -115,43 +115,43 @@ Use `CDN-Cache-Control` headers in conjunction with `Cache-Control` headers to s
 
 Headers:
 
-- `Cache-Control: stale-if-error=400`
-- `Cloudflare-CDN-Cache-Control: stale-if-error=60`
-- `CDN-Cache-Control: stale-if-error=200`
+* `Cache-Control: stale-if-error=400`
+* `Cloudflare-CDN-Cache-Control: stale-if-error=60`
+* `CDN-Cache-Control: stale-if-error=200`
 
 Behavior in response to [5XX error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/):
 
 <table>
-	<tbody>
-		<th colspan="5" rowspan="1">
-			Caches
-		</th>
-		<th colspan="5" rowspan="1">
-			Stale served (seconds) in response to error
-		</th>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Origin Cache Layer/Network Cache/Browser Cache
-			</td>
-			<td colspan="5" rowspan="1">
-				400 (if it assumes the directive applies)
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Cloudflare Edge
-			</td>
-			<td colspan="5" rowspan="1">
-				60
-			</td>
-		</tr>
-		<tr>
-			<td colspan="5" rowspan="1">
-				Other CDN
-			</td>
-			<td colspan="5" rowspan="1">
-				200
-			</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <th colspan="5" rowspan="1">
+      Caches
+    </th>
+    <th colspan="5" rowspan="1">
+      Stale served (seconds) in response to error
+    </th>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Origin Cache Layer/Network Cache/Browser Cache
+      </td>
+      <td colspan="5" rowspan="1">
+        400 (if it assumes the directive applies)
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Cloudflare Edge
+      </td>
+      <td colspan="5" rowspan="1">
+        60
+      </td>
+    </tr>
+    <tr>
+      <td colspan="5" rowspan="1">
+        Other CDN
+      </td>
+      <td colspan="5" rowspan="1">
+        200
+      </td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/docs/cache/concepts/customize-cache.mdx b/src/content/docs/cache/concepts/customize-cache.mdx
index 1a9047525da3655..c4f49110ea13c65 100644
--- a/src/content/docs/cache/concepts/customize-cache.mdx
+++ b/src/content/docs/cache/concepts/customize-cache.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: Methods for customizing cache behavior with rules, Workers, and headers.
 products:
   - cache
+
 ---
 
 Some possible combinations of origin web server settings and Cloudflare [Cache Rules](/cache/how-to/cache-rules/) include:
@@ -12,21 +13,21 @@ Some possible combinations of origin web server settings and Cloudflare [Cache R
 
 For example, create a `/static/` subdirectory at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
-- Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Path starts with "/static"`
+* Using the Expression Editor: `(http.host contains "example.com" and starts_with(http.request.uri.path, "/static"))`
 
 ## Append a unique file extension to static pages
 
 For example, create a `.shtml` file extension for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
-- Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Path ends with ".shtml"`
+* Using the Expression Editor: `(http.host contains "example.com" and ends_with(http.request.uri.path, ".shtml"))`
 
 ## Add a query string to a resource’s URL to mark the content as static
 
 For example, add a `static=true` query string for resources at your origin web server and a Cache Everything Cache Rule matching the following expression:
 
-- Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
-- Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
+* Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
+* Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
 
 Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a Cache-Control header of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.
diff --git a/src/content/docs/cache/concepts/default-cache-behavior.mdx b/src/content/docs/cache/concepts/default-cache-behavior.mdx
index 6749f5b82907cf1..0f9a375df7316c6 100644
--- a/src/content/docs/cache/concepts/default-cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/default-cache-behavior.mdx
@@ -7,24 +7,20 @@ products:
 head:
   - tag: title
     content: Default Cache Behavior
+
 ---
 
-import {
-	FeatureTable,
-	GlossaryTooltip,
-	Render,
-	DashButton,
-} from "~/components";
+import { FeatureTable, GlossaryTooltip, Render, DashButton } from "~/components"
 
 Cloudflare respects the origin web server’s cache headers in the following order unless an [Edge Cache TTL cache rule](/cache/how-to/cache-rules/settings/#edge-ttl) overrides the headers. Refer to the [Edge TTL](/cache/how-to/configure-cache-status-code/#edge-ttl) section for details on default TTL behavior.
 
-- Cloudflare **does not** cache the resource when:
-  - The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
-  - The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
-  - The HTTP request method is anything other than a `GET`.
-- Cloudflare **does** cache the resource when:
-  - The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
-  - The `Expires` header is set to a future date.
+* Cloudflare **does not** cache the resource when:
+  * The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
+  * The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
+  * The HTTP request method is anything other than a `GET`.
+* Cloudflare **does** cache the resource when:
+  * The `Cache-Control` header is set to `public` and `max-age` is greater than 0.
+  * The `Expires` header is set to a future date.
 
 :::note
 Cloudflare does cache the resource even if there is no `Cache-Control` header based on [status codes](/cache/how-to/configure-cache-status-code/#edge-ttl).
@@ -40,8 +36,8 @@ When [Origin Cache Control](/cache/concepts/cache-control/) is enabled on an Ent
 
 Clients can send range requests to be served from the cache using the `Range` header. Note that:
 
-- If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
-- If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
+ - If the origin response includes a `Content-Length` header, then the specified byte range will be returned with an [HTTP 206](/support/troubleshooting/http-status-codes/2xx-success/#206-partial-content) response.
+ - If the origin response does not include the `Content-Length` header, the cache will return the full content with an HTTP 200 response.
 
 ## Request collapsing
 
@@ -68,10 +64,10 @@ Cloudflare only caches based on file extension and not by MIME type. The Cloudfl
 To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/) to create a rule to cache everything.
 
 <Render
-	file="edge-ttl"
+  file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
@@ -79,14 +75,14 @@ To cache additional content, refer to [Cache Rules](/cache/how-to/cache-rules/)
 
 Cloudflare’s CDN provides several cache customization options:
 
-- Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
+* Caching behavior for individual URLs via [Cache Rules](/cache/how-to/cache-rules/)
 
-<DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+ <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
-- Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
-- Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
+* Customize caching with [Cloudflare Workers](/workers/reference/how-the-cache-works/)
+* Adjust caching level, cache TTL, and more in the Caching page in the Cloudflare dashboard:
 
-<DashButton url="/?to=/:account/:zone/caching/configuration" />
+ <DashButton url="/?to=/:account/:zone/caching/configuration" />
 
 ### Upload limits
 
@@ -100,8 +96,8 @@ If you require a larger upload, you can group requests into smaller chunks, uplo
 
 Cloudflare cacheable file limits:
 
-- Free, Pro and Business customers have a limit of 512 MB.
-- For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
+* Free, Pro and Business customers have a limit of 512 MB.
+* For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
 
 ## When does Cloudflare cache successfully?
 
diff --git a/src/content/docs/cache/concepts/index.mdx b/src/content/docs/cache/concepts/index.mdx
index c39bdbe713dbf77..9d7aa540158df71 100644
--- a/src/content/docs/cache/concepts/index.mdx
+++ b/src/content/docs/cache/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+    
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts and components of Cloudflare Cache.
 
diff --git a/src/content/docs/cache/concepts/retention-vs-freshness.mdx b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
index 86ee2ef5d7736c5..1148870b16f91ca 100644
--- a/src/content/docs/cache/concepts/retention-vs-freshness.mdx
+++ b/src/content/docs/cache/concepts/retention-vs-freshness.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: How cache retention and TTL freshness differ in Cloudflare.
 products:
   - cache
+
 ---
 
 In the context of Cloudflare CDN (Content Delivery Network), retention and freshness refer to two separate but related concepts. For an object in cache, freshness is how long it should be considered valid without consulting its source, while retention refers to how long it stays in cache before being removed.
@@ -18,8 +19,8 @@ Cloudflare uses a Least Recently Used (LRU) algorithm to decide which objects to
 
 Freshness, also known as Time to Live (TTL), determines how long a cache can use an object without checking with the origin again. For example, if an object has a TTL of five minutes, the cache serves it directly for five minutes after first receiving it. After five minutes, Cloudflare must check with the origin to confirm the object is still valid before serving it again. There are a few ways to configure TTLs for resources served through Cloudflare's CDN:
 
-- Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
+* Include [Origin Cache Control](/cache/concepts/cache-control/) or [CDN Cache Control](/cache/concepts/cache-control/) directives, like `max-age` or `s-maxage`, in the origin cache-control response header.
 
-- Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
+* Use [Cache Rules](/cache/how-to/cache-rules/) or [Workers](/cache/interaction-cloudflare-products/workers/).
 
 If an object in cache is no longer fresh, Cloudflare revalidates it with the origin. When [`stale-while-revalidate`](/cache/concepts/cache-control/#revalidation) is set, revalidation happens asynchronously at expiry — visitors continue to be served from cache while Cloudflare fetches a fresh copy in the background. Without this directive, incoming requests wait for the origin to respond before receiving content. The origin can either confirm the cached object is still valid (refreshing its TTL) or return a new version to replace it. Refer to [Revalidation](/cache/concepts/revalidation/) for details.
diff --git a/src/content/docs/cache/concepts/revalidation.mdx b/src/content/docs/cache/concepts/revalidation.mdx
index f289dc2c55c0ce6..be6792de1f48057 100644
--- a/src/content/docs/cache/concepts/revalidation.mdx
+++ b/src/content/docs/cache/concepts/revalidation.mdx
@@ -4,6 +4,7 @@ pcx_content_type: concept
 description: How Cloudflare revalidates stale cached content with your origin.
 products:
   - cache
+
 ---
 
 ## Stale-while-revalidate
diff --git a/src/content/docs/cache/get-started.mdx b/src/content/docs/cache/get-started.mdx
index 485414c218db17e..ab1be9257230ee3 100644
--- a/src/content/docs/cache/get-started.mdx
+++ b/src/content/docs/cache/get-started.mdx
@@ -13,7 +13,7 @@ head:
     content: Get started with Cache
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare speeds up your website by caching content across globally distributed data centers.
 
@@ -21,12 +21,12 @@ Content can be static or dynamic. Static content — such as images, CSS, and Ja
 
 Cloudflare caches static content based on the following factors:
 
-- [Caching levels](/cache/how-to/set-caching-levels/)
-- [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
-- Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
-- [Origin cache-control headers](/cache/concepts/cache-control/)
-- Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
-- Cache rules that bypass cache on cookie
+* [Caching levels](/cache/how-to/set-caching-levels/)
+* [File extension](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+* Presence of [query strings](/cache/advanced-configuration/query-string-sort/)
+* [Origin cache-control headers](/cache/concepts/cache-control/)
+* Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
+* Cache rules that bypass cache on cookie
 
 Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, or content hosted on [DNS-only (unproxied)](/dns/proxy-status/) DNS records.
 
@@ -34,35 +34,35 @@ Cloudflare only caches resources within the Cloudflare data center that serve th
 
 Discover the benefits of caching with Cloudflare's CDN and understand the default cache behavior.
 
-- [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
-- [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
-- [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
+* [Understand what is a CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
+* [Understand default cache behavior](/cache/concepts/default-cache-behavior/)
+* [Understand the default file types Cloudflare caches](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
 
 ## Make more resources cacheable
 
 Configure your settings to cache static HTML or cache anonymous page views of dynamic content.
 
-- [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
-- [Specify which resources to cache](/cache/concepts/customize-cache/)
-- [Understand Origin Cache Control](/cache/concepts/cache-control/)
-- [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
+* [Customize Caching with Cache Rules](/cache/how-to/cache-rules/)
+* [Specify which resources to cache](/cache/concepts/customize-cache/)
+* [Understand Origin Cache Control](/cache/concepts/cache-control/)
+* [Cache by device type (Enterprise only)](/cache/how-to/cache-rules/examples/cache-device-type/)
 
 ## Improve cache HIT rates
 
 Include or exclude query strings, optimize cache keys, or enable [Tiered Cache](/cache/how-to/tiered-cache/) to improve HIT rates and reduce traffic to your origin.
 
-- [Choose a cache level](/cache/how-to/set-caching-levels/)
-- [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
-- [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
-- [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
+* [Choose a cache level](/cache/how-to/set-caching-levels/)
+* [Enable Tiered Cache with Argo](/cache/how-to/tiered-cache/#enable-tiered-cache)
+* [Configure custom cache keys (Enterprise only)](/cache/how-to/cache-keys/)
+* [Enable Prefetch URLs (Enterprise only)](/speed/optimization/content/prefetch-urls/)
 
 ## Secure your cache configuration
 
 Control resources a client is allowed to load and set access permissions to allow different origins to access your origin's resources. Protect your site from web cache deception attacks while still caching static assets.
 
-- [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
-- [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
-- [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
+* [Avoid web cache poisoning attacks](/cache/cache-security/avoid-web-poisoning/)
+* [Configure Cross-Origin Resource Sharing (CORS)](/cache/cache-security/cors/)
+* [Enable Cache Deception Armor](/cache/cache-security/cache-deception-armor/#enable-cache-deception-armor)
 
 ## Features that alter cached content
 
@@ -70,16 +70,16 @@ Some Cloudflare features modify your HTML or cached objects at the edge to enabl
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. Cloudflare removes the changes when you disable the feature and purge the cache.
 These alterations only affect cached copies at Cloudflare's edge and do not change your original source files. The changes are removed if the feature is disabled and the cache is purged.
 
-- [Rocket Loader](/speed/optimization/content/rocket-loader/)
-- [Polish](/images/polish/)
-- [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
-- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
-- [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
+* [Rocket Loader](/speed/optimization/content/rocket-loader/)
+* [Polish](/images/polish/)
+* [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)
+* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/)
+* [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/)
 
 ## Troubleshoot
 
 Resolve common caching concerns.
 
-- [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
-- [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
-- [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
+* [Learn about Cloudflare's cache response statuses](/cache/concepts/cache-responses/)
+* [Investigate Cloudflare's cache response with cURL](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#troubleshoot-requests-with-curl)
+* [Diagnose Always Online issues](/cache/troubleshooting/always-online/)
diff --git a/src/content/docs/cache/glossary.mdx b/src/content/docs/cache/glossary.mdx
index ae52887a0324745..93414f59d8d1137 100644
--- a/src/content/docs/cache/glossary.mdx
+++ b/src/content/docs/cache/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Cache documentation.
 products:
   - cache
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Cache documentation.
 
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
index 26540e1b1bc9dfc..5e0cffeecb60098 100644
--- a/src/content/docs/cache/how-to/always-online.mdx
+++ b/src/content/docs/cache/how-to/always-online.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Serve cached pages when your origin server is unavailable.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Cloudflare’s Always Online feature is now integrated with the [Internet Archive](https://archive.org/) so that visitors can access a portion of your website even when your origin server is unreachable and a Cloudflare-cached version is unavailable. When your origin is unreachable, Always Online checks Cloudflare’s cache for a stale or expired version of your website. If a version does not exist, Cloudflare goes to the Internet Archive to fetch and serve static portions of your website.
 
@@ -45,8 +46,10 @@ Here is how to enable Always Online in the dashboard:
 
 :::note[Note]
 
+
 When turning on Always Online, you are also enabling the Internet Archive integration.
 
+
 :::
 
 Refer to [Always Online](/cache/troubleshooting/always-online/) for best practices, limitations, and FAQs.
diff --git a/src/content/docs/cache/how-to/cache-keys.mdx b/src/content/docs/cache/how-to/cache-keys.mdx
index 8afbd280f376234..59b3e1e4cd98538 100644
--- a/src/content/docs/cache/how-to/cache-keys.mdx
+++ b/src/content/docs/cache/how-to/cache-keys.mdx
@@ -14,16 +14,16 @@ head:
     content: Cache Keys
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.
 
 A default cache key includes:
 
 1. Full URL:
-   - scheme - could be HTTP or HTTPS.
-   - host - for example, `www.cloudflare.com`
-   - URI with query string - for example, `/logo.jpg?utm_source=newsletter`
+   * scheme - could be HTTP or HTTPS.
+   * host - for example, `www.cloudflare.com`
+   * URI with query string - for example, `/logo.jpg?utm_source=newsletter`
 2. Origin header sent by client (for CORS support).
 3. `x-http-method-override`, `x-http-method`, and `x-method-override` headers.
 4. `x-forwarded-host`, `x-host`, `x-forwarded-scheme` (unless http or https), `x-original-url`, `x-rewrite-url`, and `forwarded` headers.
@@ -51,8 +51,8 @@ When [URL normalization](/rules/normalization/) is enabled, we recommend also en
 
 There are a couple of common reasons to change the Cache Key Template. You might change the Cache Key Template to:
 
-- Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
-- Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
+* Fragment the cache so one URL is stored in multiple files. For example, to store different files based on a specific query string in the URL.
+* Consolidate the cache so different HTTP requests are stored in the same file. For example, to remove the Origin header added to Cloudflare Cache Keys by default.
 
 ### Impact of SSL settings on Cache behavior
 
@@ -90,9 +90,9 @@ If you include the query string foo in a URL like `https://www.example.com/?foo=
 
 #### Usage notes
 
-- To include all query string parameters (the default behavior), use include: `"\*"`
-- To ignore query strings, use exclude: `"\*"`
-- To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
+* To include all query string parameters (the default behavior), use include: `"\*"`
+* To ignore query strings, use exclude: `"\*"`
+* To include most query string parameters but exclude a few, use the exclude field which assumes the other query string parameters are included.
 
 ### Headers
 
@@ -102,13 +102,13 @@ When you include a header, the header value is included in the Cache Key. For ex
 
 In the **Include headers and selected values** section, you can add header names and their values to the cache key. For custom headers, values are optional, but for the following restricted headers, you must include one to 10 specific values:
 
-- `accept`
-- `accept-charset`
-- `accept-encoding`
-- `accept-datetime`
-- `accept-language`
-- `referer`
-- `user-agent`
+  * `accept`
+  * `accept-charset`
+  * `accept-encoding`
+  * `accept-datetime`
+  * `accept-language`
+  * `referer`
+  * `user-agent`
 
 To check for the presence of a header without including its actual value, use the **Check presence of** option.
 
@@ -116,28 +116,28 @@ Currently, you can only exclude the `Origin` header. The `Origin` header is alwa
 
 Additionally, you cannot include the following headers:
 
-- Headers that re-implement cache or proxy features
-  - `connection`
-  - `content-length`
-  - `cache-control`
-  - `if-match`
-  - `if-modified-since`
-  - `if-none-match`
-  - `if-unmodified-since`
-  - `range`
-  - `upgrade`
-- Headers that are covered by other Cache Key features
-  - `cookie`
-  - `host`
-- Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
-- Headers that are already included in the custom Cache Key template, for example, `origin`
+* Headers that re-implement cache or proxy features
+  * `connection`
+  * `content-length`
+  * `cache-control`
+  * `if-match`
+  * `if-modified-since`
+  * `if-none-match`
+  * `if-unmodified-since`
+  * `range`
+  * `upgrade`
+* Headers that are covered by other Cache Key features
+  * `cookie`
+  * `host`
+* Headers that are specific to Cloudflare and prefixed with `cf-`, for example, `cf-ray`
+* Headers that are already included in the custom Cache Key template, for example, `origin`
 
 ### Host
 
 Host determines which host header to include in the Cache Key.
 
-- If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
-- If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
+* If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
+* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
 
 ### Cookie
 
@@ -151,9 +151,9 @@ You cannot include cookies specific to Cloudflare. Cloudflare cookies are prefix
 
 User feature fields add features about the end-user (client) into the Cache Key.
 
-- `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
-- `geo` includes the client’s country, derived from the IP address
-- `lang` includes the first language code contained in the `Accept-Language` header sent by the client
+* `device_type` classifies a request as `mobile`, `desktop`, or `tablet` based on the User Agent
+* `geo` includes the client’s country, derived from the IP address
+* `lang` includes the first language code contained in the `Accept-Language` header sent by the client
 
 ## Availability
 
diff --git a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
index 7c75c81a407e301..f8032d4bd1be12e 100644
--- a/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
+++ b/src/content/docs/cache/how-to/cache-response-rules/create-dashboard.mdx
@@ -30,6 +30,7 @@ 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 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:
@@ -42,8 +43,7 @@ import { Render, DashButton } from "~/components";
    - **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**.
 
-<Render file="rules-creation-dash-dns-popup" product="rules" />
+   <Render file="rules-creation-dash-dns-popup" product="rules" />
diff --git a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
index 24434a23533ec9f..ba3e5a14e0342aa 100644
--- a/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: false
 pcx_content_type: navigation
 description: Example cache rule configurations for common use cases.
@@ -7,9 +8,10 @@ products:
 title: Examples
 sidebar:
   order: 8
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In the following sections, you can find common cache rules examples.
 
diff --git a/src/content/docs/cache/how-to/cache-rules/order.mdx b/src/content/docs/cache/how-to/cache-rules/order.mdx
index 5810d731d8608f8..40377bc15fa1145 100644
--- a/src/content/docs/cache/how-to/cache-rules/order.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/order.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Order and priority
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cache rules affect requests differently from Page Rules. This is how they are applied:
 
diff --git a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
index b1875b3767c20c3..6541177a91b6aa8 100644
--- a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx
@@ -13,7 +13,7 @@ head:
     content: Migration from Page Rules
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 If you are migrating from Page Rules, there is a behavior change between Page Rules and Cache Rules.
 
@@ -64,8 +64,10 @@ If you prefer, you can select **Edit expression** and paste the following expres
 
 :::note[Note]
 
+
 Remember to create the rules in the specified order: first, the `bypass everything` rule, and then the `cache all default cacheable file extensions` rule.
 
 ![Rules order](~/assets/images/cache/rule-order.png)
 
+
 :::
diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
index c30d541d4d833c7..2c71df51f6c0e94 100644
--- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx
+++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
@@ -8,7 +8,7 @@ tags:
   - REST API
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin.
 
@@ -19,10 +19,10 @@ Setting cache TTL based on response status overrides the [default cache behavior
 The maximum caching limit for Free, Pro, and Business customers is 512 MB per file, and the maximum caching limit for Enterprise customers is 5 GB per file. If you need to raise the limits, contact your Customer Success Manager.
 
 <Render
-	file="edge-ttl"
+  file="edge-ttl"
 	product="cache"
 	params={{
-		conditional: "dedicated-cache-tile",
+		conditional: "dedicated-cache-tile"
 	}}
 />
 
@@ -79,9 +79,9 @@ curl --request PUT \
 
 Provide a JSON object containing status codes and their corresponding TTLs. Each key-value pair in the cache TTL by status cache rule has the following syntax:
 
-- `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
-- `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
-- `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
+* `status_code`: An integer value such as 200 or 500. `status_code` matches the exact status code from the origin web server. Valid status codes are between 100-999.
+* `status_code_range`: Integer values for `from` and `to`. `status_code_range` matches any status code from the origin web server within the specified range.
+* `value`: An integer value that defines the duration an asset is valid in seconds or one of the following strings: `no-store` (equivalent to `-1`), `no-cache` (equivalent to `0`).
 
 ## Set cache TTL by response status via a Cloudflare Worker
 
@@ -98,4 +98,4 @@ The **cacheTtlByStatus** option is a version of the **cacheTtl** feature that de
 
 For example, if a user specifies a TTL of one hour for status `200` and 0 seconds (cache and always revalidate) for status `304`, the asset will be cached for 1 hour. After it expires, we revalidate with the origin. If the origin returns a `304`, each subsequent request will trigger revalidation. If the origin continues to return `304`, this cycle will persist.
 
-This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
+This behavior is likely undesirable unless the user has a specific use case. Therefore, users should ensure that the TTL for `304` matches the TTL for `200` unless they intentionally require this behavior.
\ No newline at end of file
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
index c26df5fd963f037..9bd8eb61f1eeb6f 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/index.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: Configure edge and browser cache TTL for your resources.
 products:
   - cache
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 ## Edge Cache TTL
 
@@ -20,16 +21,17 @@ For more information on how to set up Edge Cache TTL, refer to [Cache rules](/ca
 
 The Browser Cache TTL sets the expiration for resources cached in a visitor’s browser. By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers but overrides those headers if:
 
-- The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
-- The origin web server does not send a `Cache-Control` or an `Expires` header.
+* The value of the `Expires` or `Cache-Control` header from the origin web server is less than the Browser Cache TTL Cloudflare setting.
+* The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a cache rule, Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
 :::note[Note]
 
-- Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
-- If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
-- Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.
+
+* Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.
+* If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.
+* Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser. 
   :::
 
 <FeatureTable id="cache.browser_cache_ttl" />
diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
index bed629ee6ba70c8..fcaf35844aa8d00 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 3
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,8 +15,8 @@ Specify a time for a visitor’s Browser Cache TTL to accelerate the page load f
 
 By default, Cloudflare honors the cache expiration set in your `Expires` and `Cache-Control` headers. Cloudflare overrides any `Cache-Control` or `Expires` headers with values set via the **Browser Cache TTL** option under **Caching** on your dashboard if:
 
-- The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
-- The origin web server does not send a `Cache-Control` or an `Expires` header.
+* The value of the `Cache-Control` header from the origin web server is less than the **Browser Cache TTL** setting. This means that **Browser cache TTL** value needs to be higher than origin `max-age`.
+* The origin web server does not send a `Cache-Control` or an `Expires` header.
 
 Unless specifically set in a [Cache Rule](/cache/how-to/cache-rules/), Cloudflare does not override or insert `Cache-Control` headers if you set **Browser Cache TTL** to **Respect Existing Headers**.
 
@@ -25,8 +26,10 @@ Nevertheless, the value you set via Cache Rule will be ignored if `Cache-Control
 
 :::note[Note]
 
+
 If you modify cached assets, the new asset is not displayed to repeat visitors before the Browser Cache TTL duration. [Purging Cloudflare’s cache](/cache/how-to/purge-cache/) does not affect assets cached in a visitor’s browser.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Caching** page.
diff --git a/src/content/docs/cache/how-to/index.mdx b/src/content/docs/cache/how-to/index.mdx
index 9bb4c1c487aacad..80c1f5c0266452d 100644
--- a/src/content/docs/cache/how-to/index.mdx
+++ b/src/content/docs/cache/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn how to complete different configuration options to customize your cache behavior.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
index f33d3c2f25167fd..eccbbdee17432d8 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 4
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Purging by hostname means that all assets at URLs with a host that matches one of the provided values will be instantly purged from the cache.
 
@@ -19,9 +20,9 @@ Purging by hostname means that all assets at URLs with a host that matches one o
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Hostname**.
 4. Follow the syntax instructions:
-   - One hostname per line.
-   - Separated by commas.
-   - You can purge up to 30 hostnames at a time.
+   * One hostname per line.
+   * Separated by commas.
+   * You can purge up to 30 hostnames at a time.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
index 20267fbc6318106..1eba5da16e5ee10 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 With purge by single-file, cached resources are instantly removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific Cloudflare data center that served the request.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
index 0b305a3f14ae32d..0531322accc993e 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 3
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more.
 
@@ -22,8 +23,10 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 
 :::caution[Warning]
 
+
 Be careful when purging. A cache MISS can cause execution delays by requiring a fetch from your origin server.
 
+
 :::
 
 ## Add Cache-Tag HTTP response headers
@@ -32,19 +35,19 @@ You add cache-tags to your web content in `Cache-Tag` HTTP response headers to a
 
 When your content reaches our edge network, Cloudflare:
 
-- Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
-- Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
-- Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
+* Removes the `Cache-Tag` HTTP header before sending the response to your website visitor or passing the response to a [Worker](/workers/). Your end users or Worker never see `Cache-Tag` HTTP headers on your Cloudflare-enabled website.
+* Removes whitespaces from the header and any before and after cache-tag names: `tag1`, `tag2` and `tag1,tag2` are considered the same.
+* Removes all repeated and trailing commas before applying cache-tags: `tag1,,,tag2` and `tag1,tag2` are considered the same.
 
 ## A few things to remember
 
-- A single HTTP response can have more than one `Cache-Tag` HTTP header field.
-- The minimum length of a cache-tag is one byte.
-- Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
-- For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
-- The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
-- Spaces are not allowed in cache-tags.
-- Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
+* A single HTTP response can have more than one `Cache-Tag` HTTP header field.
+* The minimum length of a cache-tag is one byte.
+* Individual tags do not have a maximum length, but the aggregate `Cache-Tag` HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
+* For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
+* The `Cache-Tag` HTTP header must only contain printable ASCII encoded characters.
+* Spaces are not allowed in cache-tags.
+* Case is not sensitive. For example, `Tag1` and `tag1` are considered the same.
 
 ## Purge using cache-tags
 
@@ -59,6 +62,7 @@ When your content reaches our edge network, Cloudflare:
 
 For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
 
+
 ## Resulting cache status
 
 Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests.
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
index d251d69477368b4..831850a380c6d9f 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-cache-key.mdx
@@ -25,18 +25,18 @@ For a Cache Key based on device type, purge the asset by passing the `CF-Device-
 Refer to the example API request below to instantly purge all mobile assets on the root webpage.
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"CF-Device-Type": "mobile",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "CF-Device-Type": "mobile"
+        }
+      }
+    ]
+  }}
 />
 
 ## Purge by geo
@@ -44,18 +44,18 @@ Refer to the example API request below to instantly purge all mobile assets on t
 Instantly purge resources for a location-based Cache Key by specifying the two-letter country code. Spain is used in the example below.
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"CF-IPCountry": "ES",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "CF-IPCountry": "ES"
+        }
+      }
+    ]
+  }}
 />
 
 ## Purge by language
@@ -63,16 +63,16 @@ Instantly purge resources for a location-based Cache Key by specifying the two-l
 For a Cache Key based on language, purge the asset by passing the `accept-language` header. Refer to the example API request below to instantly purge all assets in Chinese (PRC).
 
 <APIRequest
-	path="/zones/{zone_id}/purge_cache"
-	method="POST"
-	json={{
-		files: [
-			{
-				url: "http://my.website.com/",
-				headers: {
-					"accept-language": "zh-CN",
-				},
-			},
-		],
-	}}
+  path="/zones/{zone_id}/purge_cache"
+  method="POST"
+  json={{
+    files: [
+      {
+        url: "http://my.website.com/",
+        headers: {
+          "accept-language": "zh-CN"
+        }
+      }
+    ]
+  }}
 />
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
index 42378f5e362023e..1253a3d847f6bfb 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
@@ -6,9 +6,10 @@ products:
   - cache
 sidebar:
   order: 2
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 To maintain optimal site performance, Cloudflare strongly recommends using single-file (by URL) purging instead of a complete cache purge.
 
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
index f2953ab487936d9..2da37b5840f703d 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-varied-images.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 7
+
 ---
 
 Purging varied images instantly purges all content variants for that URL. This behavior occurs so that if an image changes, you can easily update the cache with a single purge request instead of trying to determine the potential number of out-of-date variants. The behavior is true regardless of [purge type](/cache/how-to/purge-cache/) used, such as [single file](/cache/how-to/purge-cache/purge-by-single-file/), [tag](/cache/how-to/purge-cache/purge-by-tags/), or [hostname](/cache/how-to/purge-cache/purge-by-hostname/).
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
index 837b8a1faf20235..06f0af7f6b98cd4 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-zone-versions.mdx
@@ -6,6 +6,7 @@ products:
   - cache
 sidebar:
   order: 8
+
 ---
 
 To purge zone versions via the Cloudflare API, follow these steps:
@@ -22,44 +23,44 @@ This API call will return a JSON response similar to the example below:
 
 ```json
 {
-	"result": {
-		"environments": [
-			{
-				"name": "Production",
-				"ref": "12abcd3e45f678940a573f51834a54",
-				"version": 0,
-				"expression": "(cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"before": "5d41402abc4b2a76b9719d911017c"
-				}
-			},
-			{
-				"name": "Staging",
-				"ref": "5d41402abc4b2a76b9719d911017c",
-				"version": 0,
-				"expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"before": "49f0bad299687c62334182178bfd",
-					"after": "12abcd3e45f678940a573f51834a54"
-				}
-			},
-			{
-				"name": "Development",
-				"ref": "49f0bad299687c62334182178bfd",
-				"version": 0,
-				"expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
-				"locked_on_deployment": false,
-				"position": {
-					"after": "5d41402abc4b2a76b9719d911017c"
-				}
-			}
-		]
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "environments": [
+      {
+        "name": "Production",
+        "ref": "12abcd3e45f678940a573f51834a54",
+        "version": 0,
+        "expression": "(cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "before": "5d41402abc4b2a76b9719d911017c"
+        }
+      },
+      {
+        "name": "Staging",
+        "ref": "5d41402abc4b2a76b9719d911017c",
+        "version": 0,
+        "expression": "((cf.edge.server_ip in {1.2.3.4 5.6.7.8})) and (cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "before": "49f0bad299687c62334182178bfd",
+          "after": "12abcd3e45f678940a573f51834a54"
+        }
+      },
+      {
+        "name": "Development",
+        "ref": "49f0bad299687c62334182178bfd",
+        "version": 0,
+        "expression": "((any(http.request.cookies[\"development\"][*] eq \"true\"))) and (cf.zone.name eq \"example.com\")",
+        "locked_on_deployment": false,
+        "position": {
+          "after": "5d41402abc4b2a76b9719d911017c"
+        }
+      }
+    ]
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -75,7 +76,7 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/purge_cache/
 
 To purge non-production environments, you must use a new `purge_cache` endpoint and specify the environment you would like to purge.
 
-To purge the Staging environment from the example above, send a request to the following endpoint:
+To purge the Staging environment from the example above, send a request to the following endpoint: 
 
 ```bash
 https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/5d41402abc4b2a76b9719d911017c/purge_cache/
@@ -89,4 +90,4 @@ https://api.cloudflare.com/client/v4/zones/<zone_id>/environments/49f0bad299687c
 
 :::note
 When purging everything for a non-production cache environment, all files for that specific cache environment will be purged. However, when purging everything for the production environment, all files will be purged across all environments.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
index 38922ec63e70388..315411bd1db2ac1 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx
@@ -6,23 +6,24 @@ products:
   - cache
 sidebar:
   order: 5
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 You can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
 
-- `www.example.com`
-- `www.example.com/foo`
-- `www.example.com/foo/bar`
-- `www.example.com/foo/bar/baz`
-- `www.example.com/foo/bar/baz/qux.jpg`
+* `www.example.com`
+* `www.example.com/foo`
+* `www.example.com/foo/bar`
+* `www.example.com/foo/bar/baz`
+* `www.example.com/foo/bar/baz/qux.jpg`
 
 Purging by prefix is useful in different scenarios, such as:
 
-- Purging everything within a directory.
-- Increasing control over cached objects in a path.
-- Simplifying the number of purge calls sent.
+* Purging everything within a directory.
+* Increasing control over cached objects in a path.
+* Simplifying the number of purge calls sent.
 
 1. In the Cloudflare dashboard, go to the **Configuration** page.
 
@@ -31,8 +32,8 @@ Purging by prefix is useful in different scenarios, such as:
 2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
 3. Under **Purge by**, select **Prefix**.
 4. Follow the syntax instructions.
-   - One prefix per line.
-   - Maximum 30 prefixes per API call.
+   * One prefix per line.
+   * Maximum 30 prefixes per API call.
 5. Enter the appropriate value(s) in the text field using the format shown in the example.
 6. Select **Purge**.
 
@@ -40,8 +41,10 @@ For information on rate limits, refer to the [Availability and limits](/cache/ho
 
 :::caution[Warning]
 
+
 If you have a [Transform Rule](/rules/transform/) in place that is modifying part of a URL path, you must use the post-transformed (origin) URL when performing a prefix purge so that purge can take effect.
 
+
 :::
 
 ## Resulting cache status
@@ -55,19 +58,21 @@ Depending on whether the upper tier has the resource or not, and whether the end
 
 There are several limitations regarding purge by prefix:
 
-- Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
-- Purge requests are limited to 30 prefixes per request.
-- [Purge rate-limits apply](/api/resources/cache/methods/purge/).
-- URI query strings & fragments cannot purge by prefix:
-  - `www.example.com/foo?a=b` (query string)
-  - `www.example.com/foo#bar` (fragment)
+* Path separators are limited to 31 for a prefix `(example.com/a/b/c/d/e/f/g/h/i/j/k/l/m…)`.
+* Purge requests are limited to 30 prefixes per request.
+* [Purge rate-limits apply](/api/resources/cache/methods/purge/).
+* URI query strings & fragments cannot purge by prefix:
+  * `www.example.com/foo?a=b` (query string)
+  * `www.example.com/foo#bar` (fragment)
 
 :::caution[Warning]
 
+
 Because purge by prefix purges a directory, any URI for a resource within the purged directory is purged regardless of query string or fragment (though fragments are not generally sent by browsers). Purge by prefix rules do not accept fragments and query strings.
 
 Example: If you purge `foo.com/bar`, any asset that starts with `foo.com/bar` will be purged, for example, `foo.com/bar/baz`, `foo.com/bar?good=bad`, etc. and purging `foo.com/bar?good=bad` itself will not work.
 
+
 :::
 
 ## Purge by prefix normalization
diff --git a/src/content/docs/cache/how-to/set-caching-levels.mdx b/src/content/docs/cache/how-to/set-caching-levels.mdx
index 84cb1614461925d..4d6a0dee4f74ba7 100644
--- a/src/content/docs/cache/how-to/set-caching-levels.mdx
+++ b/src/content/docs/cache/how-to/set-caching-levels.mdx
@@ -7,20 +7,23 @@ products:
 head:
   - tag: title
     content: Caching levels
+
 ---
 
 Caching levels determine how much of your website’s static content Cloudflare should cache. Cloudflare’s CDN caches static content according to the levels below.
 
-- **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
-- **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
-- **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
+* **No Query String**: Delivers resources from cache when there is no query string. Example URL: `example.com/pic.jpg`
+* **Ignore Query String**: Delivers the same resource to everyone independent of the query string. Example URL: `example.com/pic.jpg?ignore=this-query-string`
+* **Standard (Default)**: Delivers a different resource each time the query string changes. Example URL: `example.com/pic.jpg?with=query`
 
 You can adjust the caching level from the dashboard under **Caching** > **Configuration** > **Caching level**.
 
 :::note[Note]
 
+
 Ignore Query String only disregards the query string for static file extensions. For example, Cloudflare serves the `style.css` resource to requests for either `style.css?this` or `style.css?that`.
 
+
 :::
 
 ## API Caching level values
diff --git a/src/content/docs/cache/interaction-cloudflare-products/index.mdx b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
index 842985c69a31adc..449a56ed4e7345c 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/index.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+    
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare caches content at data centers close to your visitors so your origin server handles fewer requests. The pages below explain how caching works when you also use Workers, R2 storage, or WAF security rules, and what to watch out for when combining them.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
index 11c3946c910d777..ed54947bc4e5f34 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/r2.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Enable cache in an R2 bucket
+
 ---
 
 By default, R2 buckets are private. To serve R2 objects through Cloudflare's cache, you need to attach a domain name you control — called a [Custom Domain](/r2/buckets/public-buckets/#custom-domains) — to the bucket. This creates a public URL backed by Cloudflare's network, so requests for your stored files go through Cloudflare's cache instead of hitting R2 directly every time.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
index 5f5d22b02dd934b..fb6bf25720d358f 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/waf-snippets.mdx
@@ -23,7 +23,7 @@ accTitle: Connections with Cloudflare
 A[User's request] --> B[WAF] --> C[Cache] --> D[R2]
 ```
 
-<br />
+<br/>
 
 ## Presigned URLs
 
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
index a7765d2c345f3a1..390f1369a9cee75 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: How Workers interact with Cache Rules
+
 ---
 
 When you use both [Cache Rules](/cache/how-to/cache-rules/) and [Workers](/workers/) on the same request, the Worker's cache settings take priority — but only when the required [compatibility flags](#compatibility-flags) are enabled.
@@ -38,10 +39,10 @@ These flags must be enabled to allow Workers scripts to override Cache Rules. If
 
 A Worker's [compatibility date](/workers/configuration/compatibility-dates/) determines which flags are active by default. When you set a compatibility date, all flags with an enable date on or before that date are automatically turned on.
 
-| Flag                                                     | Enabled by default                           | Prerequisite                      |
-| -------------------------------------------------------- | -------------------------------------------- | --------------------------------- |
-| `request_cf_overrides_cache_rules` (Fetch API)           | Compatibility dates on or after `2025-04-02` | None                              |
-| `cache_api_compat_flags`                                 | Compatibility dates on or after `2025-04-19` | None                              |
+| Flag | Enabled by default | Prerequisite |
+| --- | --- | --- |
+| `request_cf_overrides_cache_rules` (Fetch API) | Compatibility dates on or after `2025-04-02` | None |
+| `cache_api_compat_flags` | Compatibility dates on or after `2025-04-19` | None |
 | `cache_api_request_cf_overrides_cache_rules` (Cache API) | Compatibility dates on or after `2025-05-19` | Requires `cache_api_compat_flags` |
 
 The Cache API has an extra requirement: `cache_api_compat_flags` must be enabled for any compatibility flags to take effect on the Cache API. Without it, the Cache API ignores all compatibility flags, even ones you explicitly list in your configuration.
diff --git a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
index 91df57a65ed0396..0b90c7883ab5180 100644
--- a/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
+++ b/src/content/docs/cache/interaction-cloudflare-products/workers.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Customize cache behavior with Workers
+
 ---
 
 You can use [Workers](/workers/) to customize cache behavior on Cloudflare's network. Workers run as middleware in the request lifecycle — a single Worker handles both the request and response phases. When a request arrives, it hits the Worker before the cache is checked. The Worker can modify the incoming request (for example, rewrite the URL or add headers), then call `fetch()` to continue the request through the cache. When the response comes back — whether from cache or from the origin server — the Worker can also modify the response before it is sent to the visitor.
@@ -45,4 +46,4 @@ Workers offer two ways to interact with the cache. Use `fetch()` when your Worke
 
 - **Cache API**: Allows you to programmatically store, retrieve, and delete responses in Cloudflare's cache using `caches.default` or `caches.open()`. Unlike `fetch()`, the Cache API only operates on the cache in the data center handling the current request — it does not interact with Tiered Cache. Use the Cache API when you need to cache responses that did not come from an origin. For more details, refer to [Using the Cache API](/workers/examples/cache-api/).
 
-To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
+To understand more about how Cache and Workers interact, refer to [Cache in Workers](/workers/reference/how-the-cache-works/).
\ No newline at end of file
diff --git a/src/content/docs/cache/performance-review/cache-analytics.mdx b/src/content/docs/cache/performance-review/cache-analytics.mdx
index 6db30fa95015ec1..5e225c6a89340c7 100644
--- a/src/content/docs/cache/performance-review/cache-analytics.mdx
+++ b/src/content/docs/cache/performance-review/cache-analytics.mdx
@@ -4,9 +4,10 @@ pcx_content_type: concept
 description: View cache hit rates and bandwidth savings in Cache Analytics.
 products:
   - cache
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Cache Analytics shows how much of your site's traffic is served from Cloudflare's cache versus your origin server. When content is served from cache, visitors get faster page loads and your origin web server handles less traffic. Use Cache Analytics to identify resources that are [missing from cache](/cache/concepts/cache-responses/#miss), [expired](/cache/concepts/cache-responses/#expired) (cached copy is outdated), or [ineligible for caching](/cache/concepts/cache-responses/#noneunknown) (not eligible for caching). You can filter by hostname, review the top URLs that miss cache, and query up to three days of data.
 
@@ -18,7 +19,7 @@ Cache Analytics shows how much of your site's traffic is served from Cloudflare'
 
 In the Cloudflare dashboard, go to the **Caching** page.
 
-<DashButton url="/?to=/:account/:zone/caching" />
+   <DashButton url="/?to=/:account/:zone/caching" />
 
 ## Requests vs Data Transfer
 
diff --git a/src/content/docs/cache/performance-review/cache-performance.mdx b/src/content/docs/cache/performance-review/cache-performance.mdx
index 9e4e9ebc7569a11..528344752e6ef3d 100644
--- a/src/content/docs/cache/performance-review/cache-performance.mdx
+++ b/src/content/docs/cache/performance-review/cache-performance.mdx
@@ -24,6 +24,7 @@ Depending on the [cache status](/cache/concepts/cache-responses/) you receive, y
 Use [Cache Analytics](/cache/performance-review/cache-analytics/) to identify cache performance issues. The following examples show how to filter for common problems and resolve them.
 
 - Not caching HTML.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Dynamic**.
   - Resolution: Set a Cloudflare Cache Rule to [cache dynamic content](/cache/how-to/cache-rules/examples/cache-everything/).
 
@@ -34,12 +35,14 @@ This option caches all HTML regardless of the presence of dynamic content (conte
 - Checking for the presence of a cookie.
 - Excluding requests that match known dynamic content file paths.
 - Excluding requests with dynamic content extensions (or no extension).
-  :::
+:::
 
 - Short cache expiration TTL.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Revalidated**.
   - Resolution: [Increase Cloudflare's Edge Cache TTL via a Cache Rule](/cache/how-to/cache-rules/examples/edge-ttl/).
 
 - Need to enable Tiered Cache or custom cache key.
+
   - Identify the issue: Select **Add filter** and select **Cache status equals Miss**.
   - Resolution: [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) or [create a custom cache key](/cache/how-to/cache-rules/examples/custom-cache-key/).
diff --git a/src/content/docs/cache/performance-review/index.mdx b/src/content/docs/cache/performance-review/index.mdx
index b2b00f57fe7dfb6..62a5b788d098027 100644
--- a/src/content/docs/cache/performance-review/index.mdx
+++ b/src/content/docs/cache/performance-review/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 8
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use Cache Analytics to understand how effectively Cloudflare caches your content, and apply optimization techniques to improve your cache hit ratio and reduce origin server load.
 
diff --git a/src/content/docs/cache/plans.mdx b/src/content/docs/cache/plans.mdx
index a4543e9bf53afe7..e8f54313de37f9f 100644
--- a/src/content/docs/cache/plans.mdx
+++ b/src/content/docs/cache/plans.mdx
@@ -10,12 +10,13 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="cache" />
+<ProductFeatures id="cache" />
\ No newline at end of file
diff --git a/src/content/docs/cache/reference/cdn-reference-architecture.mdx b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
index 145f83c1cb84f3c..4681ed5552d3aa6 100644
--- a/src/content/docs/cache/reference/cdn-reference-architecture.mdx
+++ b/src/content/docs/cache/reference/cdn-reference-architecture.mdx
@@ -5,4 +5,5 @@ products:
   - cache
 title: CDN Reference Architecture
 external_link: /reference-architecture/architectures/cdn/
+
 ---
diff --git a/src/content/docs/cache/reference/development-mode.mdx b/src/content/docs/cache/reference/development-mode.mdx
index 417c841881601c5..c6f9d879d1f7baf 100644
--- a/src/content/docs/cache/reference/development-mode.mdx
+++ b/src/content/docs/cache/reference/development-mode.mdx
@@ -4,15 +4,16 @@ pcx_content_type: how-to
 description: Bypass the cache temporarily with Development Mode.
 products:
   - cache
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their [cacheable content](/cache/concepts/default-cache-behavior/#default-cached-file-extensions) like images, CSS, or JavaScript.
 
 :::note
 
-To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache).
+To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/cache/how-to/cache-rules/settings/#bypass-cache). 
 :::
 
 ## Enable Development Mode
diff --git a/src/content/docs/cache/reference/index.mdx b/src/content/docs/cache/reference/index.mdx
index fa4c9cb8953cc15..57aa94f03cf5680 100644
--- a/src/content/docs/cache/reference/index.mdx
+++ b/src/content/docs/cache/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the reference content to learn more about specific caching functionality.
 
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx
index bd25e5e49df3439..c5011e04ae13af4 100644
--- a/src/content/docs/cache/troubleshooting/always-online.mdx
+++ b/src/content/docs/cache/troubleshooting/always-online.mdx
@@ -36,13 +36,16 @@ Always Online does not trigger for HTTP response codes such as [404](/support/tr
 ## Frequently asked questions
 
 1. How can I know if a page has been crawled?
+
    - You can go to the [Internet Archive](https://web.archive.org/) and search for the page URL to see if it has been crawled or not.
    - You can also check this via the [Internet Archive Availability API](https://archive.org/help/wayback_api.php).
 
 2. Why were not pages x, y, and z crawled?
+
    - Since Cloudflare only requests to crawl the most popular pages on the site, it is possible that there will be missing pages. If you really want to archive a page, then you can visit the [Internet Archive](https://web.archive.org/save) save page and ask them to crawl a particular page.
 
 3. What IP addresses do we need to allowlist to make sure crawling works?
+
    - IP Range: `207.241.224.0/20` and `208.70.24.0/21`. Note that this ip range belongs to Internet Archive and NOT Cloudflare, since it is the Internet Archive that does the crawling.
 
 4. What user agent should the origin expect to see?
diff --git a/src/content/docs/cache/troubleshooting/index.mdx b/src/content/docs/cache/troubleshooting/index.mdx
index 43a1ccb36799ea9..6d019d87491a048 100644
--- a/src/content/docs/cache/troubleshooting/index.mdx
+++ b/src/content/docs/cache/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The following topics are useful for troubleshooting Cache issues.
 
diff --git a/src/content/docs/china-network/concepts/global-acceleration.mdx b/src/content/docs/china-network/concepts/global-acceleration.mdx
index 65a11d18c9950e0..d5cf13877556bdc 100644
--- a/src/content/docs/china-network/concepts/global-acceleration.mdx
+++ b/src/content/docs/china-network/concepts/global-acceleration.mdx
@@ -30,14 +30,14 @@ Organizations that serve content or connect employees in Mainland China face con
 
 Global Acceleration can support the following scenarios:
 
-| Service                                                                                 | Scenario                                                                                           |
-| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Service                                                                                 | Scenario                                                            |
+| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
 | [CDN Global Acceleration](#cdn-global-acceleration)                                     | Improved performance for dynamic content (API responses, personalized pages) on China Network CDN. |
-| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                                                      |
-| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                                                             |
-| [ICP](#icp-services)                                                                    | China Network prerequisite.                                                                        |
-| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                                                      |
-| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China.                  |
+| [Cloudflare One Client Global Acceleration](#cloudflare-one-client-global-acceleration) | Cloudflare One Client used in Mainland China.                       |
+| [Cloudflare WAN Global Acceleration](#cloudflare-wan-global-acceleration)               | Cloudflare WAN used in Mainland China.                              |
+| [ICP](#icp-services)                                                                    | China Network prerequisite.                                         |
+| [MLPS](#mlps-services)                                                                  | China cybersecurity compliance certification.                       |
+| [Travel SIM](#travel-sim)                                                               | Temporary Cloudflare One Client access for employees traveling to Mainland China. |
 
 ## CDN Global Acceleration
 
diff --git a/src/content/docs/china-network/reference/available-products.mdx b/src/content/docs/china-network/reference/available-products.mdx
index 0ae2911eaa5b486..f5ba030c4d27bda 100644
--- a/src/content/docs/china-network/reference/available-products.mdx
+++ b/src/content/docs/china-network/reference/available-products.mdx
@@ -37,7 +37,7 @@ The following products and features are available on the Cloudflare China Networ
 | [R2](/r2/)[^3]                                                            | Object storage for all your data.                                                                                                                  |
 | [Assets](/workers/static-assets/)                                         | Upload static assets (HTML, CSS, images and other files) as part of your Worker — Cloudflare will handle caching and serving them to web browsers. |
 | [Environment variables](/workers/configuration/environment-variables/)    | Attach text strings or JSON values to your Worker.                                                                                                 |
-| [Images](/images/optimization/transformations/bindings/)[^4]              | Store, transform, optimize, and deliver images at scale.                                                                                           |
+| [Images](/images/optimization/transformations/bindings/)[^4]                          | Store, transform, optimize, and deliver images at scale.                                                                                           |
 | [mTLS](/workers/runtime-apis/bindings/mtls/)                              | Securely connect to backend servers over [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).                        |
 | [Rate Limiting](/workers/runtime-apis/bindings/rate-limit/)               | Define rate limits and write code around them in your Worker.                                                                                      |
 | [Secrets](/workers/configuration/secrets/)                                | Attach encrypted text values to your Worker.                                                                                                       |
diff --git a/src/content/docs/client-ip-geolocation/about/index.mdx b/src/content/docs/client-ip-geolocation/about/index.mdx
index eeb0a5dfa94995f..28a8f360c648938 100644
--- a/src/content/docs/client-ip-geolocation/about/index.mdx
+++ b/src/content/docs/client-ip-geolocation/about/index.mdx
@@ -10,8 +10,10 @@ description: Learn how Cloudflare Firewall Rules work.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 Cloudflare Client IP Geolocation helps you understand where in the world a given client is located, even if their true client IP address is obscured by Cloudflare's proxy systems. We offer this service to ensure customers have high-quality experiences interacting with origins that rely on geolocation — such as mapping providers — and origin operators can deliver the right content to the right users. Ensuring origins know where clients are located avoids problems associated with traditional VPNs that obscure a consumer’s geolocation and allow circumvention of geographic restrictions on content.
@@ -28,7 +30,7 @@ If a VPN user tries to use an interposed VPN or proxy system that attempts to hi
 
 ## Technical explanation
 
-We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like _MaxMind_, _IP 2 Location_, and _Neustar_.
+We map our egress IP addresses for our forward-proxy offerings to specific geolocations and continuously share this information with major geolocation database providers like *MaxMind*, *IP 2 Location*, and *Neustar*.
 
 When Cloudflare receives an inbound request from a WARP or 1.1.1.1 user, we first geolocate the IP address that made the connection to Cloudflare. Then, we select an egress IP that maps to the client geolocation. We then discard Client IP information to preserve user privacy but return their true geographic location.
 
diff --git a/src/content/docs/client-ip-geolocation/faq/index.mdx b/src/content/docs/client-ip-geolocation/faq/index.mdx
index 85a00673fec5ea2..c7687b23fc2d865 100644
--- a/src/content/docs/client-ip-geolocation/faq/index.mdx
+++ b/src/content/docs/client-ip-geolocation/faq/index.mdx
@@ -10,8 +10,10 @@ description: Answers to common questions.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 ## Website operators
diff --git a/src/content/docs/client-ip-geolocation/get-started.mdx b/src/content/docs/client-ip-geolocation/get-started.mdx
index f6115e8f83f2b6f..7bfddd2706bc177 100644
--- a/src/content/docs/client-ip-geolocation/get-started.mdx
+++ b/src/content/docs/client-ip-geolocation/get-started.mdx
@@ -10,16 +10,18 @@ description: Set up Client IP Geolocation for your network.
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 There are several things you can do to best handle traffic from Cloudflare VPN and forward-proxy users:
 
-- **Origin operators**:
-  - Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
-  - To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
-- **Geolocation data providers**:
-  - Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
-- **Users of WARP and 1.1.1.1**:
-  - Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
+* **Origin operators**:
+  * Do not block IP addresses associated with our VPN and proxy products (see the [About section](/client-ip-geolocation/about/) for more details)
+  * To get even more accurate geolocation data, ensure your origin is [reachable via IPv6](/client-ip-geolocation/faq/)
+* **Geolocation data providers**:
+  * Regularly pull updated geolocation data from the [Cloudflare API](https://api.cloudflare.com/local-ip-ranges.csv)
+* **Users of WARP and 1.1.1.1**:
+  * Review the [FAQs](/client-ip-geolocation/faq/#cloudflare-vpn-users) and [About section](/client-ip-geolocation/about/) to learn exactly how, how much, and why we share geolocation data
diff --git a/src/content/docs/client-ip-geolocation/index.mdx b/src/content/docs/client-ip-geolocation/index.mdx
index bd7c326b3032781..5464f9a0cb448ee 100644
--- a/src/content/docs/client-ip-geolocation/index.mdx
+++ b/src/content/docs/client-ip-geolocation/index.mdx
@@ -11,27 +11,27 @@ products:
 description: Add geolocation data for clients behind Cloudflare proxies.
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 :::note
 
+
 Client IP Geolocation is currently in closed Beta testing.
 
+
 :::
 
 Cloudflare designed [Cloudflare WARP](/warp-client/) and [1.1.1.1](/1.1.1.1/) to make Internet browsing more private and secure. These applications encrypt last-mile connections and make it more difficult for others to use client IP addresses in user fingerprinting.
 
 However, unlike legacy VPN applications, we never designed WARP or 1.1.1.1 to hide user locations or allow users to misrepresent their true geographic location. As a web property operator, you can use **Client IP Geolocation** to map Cloudflare egress IP addresses to specific geolocations.
 
-<LinkButton variant="primary" href="/client-ip-geolocation/get-started/">
-	Get started
-</LinkButton>
-<LinkButton variant="secondary" href="/client-ip-geolocation/about/">
-	Learn more
-</LinkButton>
+ <LinkButton variant="primary" href="/client-ip-geolocation/get-started/">Get started</LinkButton> <LinkButton variant="secondary" href="/client-ip-geolocation/about/">Learn more</LinkButton>
+
 
 :::note
 
+
 Client IP Geolocation is different from the [Cloudflare IP Geolocation setting](/network/ip-geolocation/), which helps you capture country codes for visitors.
 
+
 :::
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
index e8e7c1e8e6a9464..c3af18280364b77 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/additional-configuration.mdx
@@ -214,4 +214,4 @@ The custom error token provides diagnostic information or specific functionality
     </html>
   ```
   </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
index a5b7daf4949db75..82759d6a2395e0b 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/detect-response.mdx
@@ -29,4 +29,4 @@ fetch("/my-api-endpoint").then((response) => {
 		// Process response as usual
 	}
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
index 6c07e3d158b50d9..bc5eb92be6854f4 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx
@@ -56,4 +56,4 @@ To ensure your API calls are protected without breaking single-page applications
 
 By enabling Pre-clearance, the Turnstile widget issues a persistent clearance cookie (`cf_clearance`) upon successful human verification on an initial HTML page. This cookie pre-clears the visitor to interact with sensitive API endpoints secured by WAF rules, allowing you to deploy granular security without forcing a disruptive Challenge Page response.
 
-For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
+For implementation details, refer to the [guidance on Pre-clearance for Turnstile](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
index 9f1f938bab49aa4..ca4edef555c115d 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/resolve-challenge.mdx
@@ -19,4 +19,4 @@ When observing a Cloudflare Challenge page, a visitor could:
 
 :::note
 Visitors must enable JavaScript and cookies on their browser to be able to pass any type of Challenge.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
index e0f3d123a4bb4d7..5ccae5620b19ca2 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on available challenge types:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
index 5c15a8df1753eff..3a4bd64156f9af5 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx
@@ -16,7 +16,7 @@ Turnstile differs from Challenges Pages in that the challenge does not pause the
 
 In most cases, nothing further is required from the visitor. However, if necessary, Turnstile may display a simple checkbox that the visitor must click to proceed.
 
-After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions.
+After the challenge passes, Turnstile issues a clearance token to the visitor that must be validated via the [Siteverify API](/turnstile/get-started/server-side-validation/) before completing a sensitive action like login, sign up, or other form submissions. 
 
 <Render file="siteverify-warning" product="turnstile" />
 
@@ -26,18 +26,20 @@ While there are three types of widgets that you can choose to implement on your
 
 - **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a challenge based on the signals gathered from the visitor's browser and presents an interaction only if it detects potentially automated traffic.
 
-- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity.
+- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity. 
 
 - **Invisible**: The widget is completely invisible to the visitor, but the challenge still runs in the background.
 
   :::note[Link to Cloudflare's Turnstile Privacy Policy]
-
-  <Render file="privacy-policy" product="turnstile" />
+  <Render
+    file="privacy-policy"
+    product="turnstile"
+  />
   :::
 
 ## Implementation
 
-When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey.
+When you create a widget for your website or application via the Cloudflare dashboard, you will receive a sitekey. 
 
 The sitekey is used with [client-side rendering](/turnstile/get-started/client-side-rendering/#implicitly-render-the-turnstile-widget) by adding it to the `<div>` container placeholder. You will then place that `<div>` code snippet where you want to add the widget to your site page or form.
 
diff --git a/src/content/docs/cloudflare-challenges/concepts/index.mdx b/src/content/docs/cloudflare-challenges/concepts/index.mdx
index 181b5dfde7eb724..8587e3ba1d8f3f0 100644
--- a/src/content/docs/cloudflare-challenges/concepts/index.mdx
+++ b/src/content/docs/cloudflare-challenges/concepts/index.mdx
@@ -7,11 +7,11 @@ products:
 sidebar:
   order: 2
   label: About
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on how challenges work:
 
diff --git a/src/content/docs/cloudflare-challenges/index.mdx b/src/content/docs/cloudflare-challenges/index.mdx
index 08083dc2ca79e13..b1612b44767b991 100644
--- a/src/content/docs/cloudflare-challenges/index.mdx
+++ b/src/content/docs/cloudflare-challenges/index.mdx
@@ -11,8 +11,7 @@ sidebar:
 import { Render, Description, Plan, RelatedProduct } from "~/components";
 
 <Description>
-	Challenges are security mechanisms used by Cloudflare to verify whether a
-	visitor to your site is a real human and not a bot or automated script.
+	Challenges are security mechanisms used by Cloudflare to verify whether a visitor to your site is a real human and not a bot or automated script.
 </Description>
 
 When a Challenge is issued, Cloudflare asks the browser to perform a series of checks that help confirm the visitor's legitimacy. This process involves evaluating client-side signals (data gathered from the visitor's browser environment) or asking a visitor to take minimal action such as checking a box or selecting a button.
diff --git a/src/content/docs/cloudflare-challenges/reference/index.mdx b/src/content/docs/cloudflare-challenges/reference/index.mdx
index fe3f9e06287d1c6..3c0a6f05993d737 100644
--- a/src/content/docs/cloudflare-challenges/reference/index.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/index.mdx
@@ -6,12 +6,12 @@ products:
   - cloudflare-challenges
 sidebar:
   order: 3
-  group:
+  group: 
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Cloudflare Challenges:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
index d5d5ad31165401a..a8b394b4c4b0410 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx
@@ -8,43 +8,45 @@ sidebar:
   order: 4
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
-Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge.
+Cloudflare can challenge your visitors in various ways. They can be challenged by [Challenge Pages](/cloudflare-challenges/challenge-types/challenge-pages/), [Turnstile](/turnstile/), or by [JavaScript Detections (JSD) in Bot Management](/cloudflare-challenges/challenge-types/javascript-detections/). This document lays out the supported browsers across all of these challenge methods. When your website or application presents a challenge, your visitors receive either a Non-interactive or an Interactive Challenge. 
 
-Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of.
+Cloudflare is committed to ensuring our challenges work with as many browsers as possible, but there are limitations that you should be aware of. 
 
 ## Overview
 
-Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis.
+Cloudflare Challenges are designed to be compatible with any desktop and mobile browser. If your visitors are using an up-to-date version of a browser listed below, they will receive and be able to solve challenges without any issues. The following is a non-exclusive list of browsers supported by Cloudflare Challenges. Browsers not listed on this list are supported on a best-effort basis. 
 
 ### Supported browsers
 
 The following browsers are officially supported and tested.
 
 <Details header="Google Chrome (desktop and mobile)">
-	- Current version and two previous major versions - Chromium-based browsers
-	and Chromium-based browsers that track the current Chrome stable version
-	:::caution Beta, Dev, Canary, Nightly, or other unreleased builds are not
-	officially supported. :::
+  - Current version and two previous major versions
+  - Chromium-based browsers and Chromium-based browsers that track the current Chrome stable version
+  
+  :::caution
+  Beta, Dev, Canary, Nightly, or other unreleased builds are not officially supported.
+  :::
 </Details>
 
 <Details header="Mozilla Firefox">
-	- Current version and two previous major versions - Extended Support Release
-	(ESR) versions are supported
+  - Current version and two previous major versions
+  - Extended Support Release (ESR) versions are supported
 </Details>
 
 <Details header="Safari">
-	- Current version and two previous major versions - iOS Safari on current iOS
-	version and two previous major versions
+  - Current version and two previous major versions
+  - iOS Safari on current iOS version and two previous major versions
 </Details>
 
 <Details header="Microsoft Edge">
-	- Current version and two previous major versions
-</Details>
+  - Current version and two previous major versions
+  </Details>
 
 <Details header="Samsung Internet Browser">
-	- Current version and two previous major versions
+  - Current version and two previous major versions
 </Details>
 
 ### Limited browser support
@@ -79,19 +81,19 @@ Browser extensions can interfere with challenges in several ways.
 - Browser automation tools are often detected as potential bots and may cause challenge failures.
 
 :::note
-If challenges consistently fail, try temporarily disabling extensions and reload the page.
+If challenges consistently fail, try temporarily disabling extensions and reload the page. 
 :::
 
 ### Device emulation and developer tools
 
 Challenges are designed to distinguish between real human users and automated traffic. When device emulation is enabled (such as through browser developer tools), it can trigger bot detection mechanisms.
 
-- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices.
+- Mobile device emulation in desktop browsers often uses distinctive characteristics that differ from real mobile devices. 
 - Developer tools may modify browser behavior or expose debugging information that changes how challenges operate.
 - Automation frameworks like Selenium, Puppeteer, or Playwright are specifically detected as non-human traffic.
 
 :::note
-For developers testing applications, we recommend using real devices rather than emulated environments when possible.
+For developers testing applications, we recommend using real devices rather than emulated environments when possible. 
 
 If you must use emulation, be aware that challenges may be more difficult to pass, and do not reflect the real experience on mobile devices.
 :::
diff --git a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
index c9c87ed0b0cddc3..3b3282d4adca332 100644
--- a/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/supported-languages.mdx
@@ -12,30 +12,30 @@ sidebar:
 
 ## Multi-language support
 
-Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface.
+Cloudflare Challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface. 
 
-For language support specific to Challenge Pages, refer to the table below.
+For language support specific to Challenge Pages, refer to the table below. 
 
-| Language                      | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
-| ----------------------------- | ----------------------------- | ----------------------------- |
-| Arabic (Egypt)                | `ar-eg`                       | `ar`                          |
-| Chinese (Simplified, China)   | `zh-cn`                       | `zh`                          |
-| Chinese (Traditional, Taiwan) | `zh-tw`                       | --                            |
-| Dutch (Netherlands)           | `nl-nl`                       | `nl`                          |
-| English (United States)       | `en-us`                       | `en`                          |
-| French (France)               | `fr-fr`                       | `fr`                          |
-| German (Germany)              | `de-de`                       | `de`                          |
-| Indonesian (Indonesia)        | `id-id`                       | `id`                          |
-| Italian (Italy)               | `it-it`                       | `it`                          |
-| Japanese (Japan)              | `ja-jp`                       | `ja`                          |
-| Korean (Korea)                | `ko-kr`                       | `ko`                          |
-| Persian                       | --                            | `fa`                          |
-| Polish (Poland)               | `pl-pl`                       | `pl`                          |
-| Portuguese (Brazil)           | `pt-br`                       | `pt`                          |
-| Russian (Russia)              | `ru-ru`                       | `ru`                          |
-| Spanish (Spain)               | `es-es`                       | `es`                          |
-| Turkish (Turkey)              | `tr-tr`                       | `tr`                          |
+| Language                         | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
+| -------------------------------- | ----------------------------- | ----------------------------- |
+| Arabic (Egypt)                   | `ar-eg`                       | `ar`                          |
+| Chinese (Simplified, China)      | `zh-cn`                       | `zh`                          |
+| Chinese (Traditional, Taiwan)    | `zh-tw`                       | --                            |
+| Dutch (Netherlands)              | `nl-nl`                       | `nl`                          |
+| English (United States)          | `en-us`                       | `en`                          |
+| French (France)                  | `fr-fr`                       | `fr`                          |
+| German (Germany)                 | `de-de`                       | `de`                          |
+| Indonesian (Indonesia)           | `id-id`                       | `id`                          |
+| Italian (Italy)                  | `it-it`                       | `it`                          |
+| Japanese (Japan)                 | `ja-jp`                       | `ja`                          |
+| Korean (Korea)                   | `ko-kr`                       | `ko`                          |
+| Persian                          |  --                           | `fa`
+| Polish (Poland)                  | `pl-pl`                       | `pl`                          |
+| Portuguese (Brazil)              | `pt-br`                       | `pt`                          |
+| Russian (Russia)                 | `ru-ru`                       | `ru`                          |
+| Spanish (Spain)                  | `es-es`                       | `es`                          |
+| Turkish (Turkey)                 | `tr-tr`                       | `tr`                          |
 
 ### Turnstile language support
 
-For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
+For language support specific to Turnstile, refer to the [Turnstile documentation](/turnstile/reference/supported-languages/).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
index 0403f66ba3ed126..d9da862f3207f6c 100644
--- a/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/cloudflare-challenges/troubleshooting/challenge-solve-issues.mdx
@@ -8,9 +8,10 @@ tags:
   - Debugging
 sidebar:
   order: 2
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Challenge loops
 
@@ -34,6 +35,6 @@ Ensure your browser is updated to the latest version to maintain compatibility.
 
 Follow the steps below to ensure that your environment is properly configured.
 
-<Render file="troubleshooting-steps" product="turnstile" />
+<Render file="troubleshooting-steps" product="turnstile"/>
 
 If none of the above resolves your issue, contact the website administrator with the [error code](/turnstile/troubleshooting/client-side-errors/error-codes/) and Ray ID or submit a [feedback report](/turnstile/troubleshooting/feedback-reports/) through the Turnstile widget by selecting **Submit Feedback**.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
index 7ff0b1bb50a2ea4..360ff1b151ff9d5 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx
@@ -9,19 +9,20 @@ sidebar:
 head:
   - tag: title
     content: Backoff schedule | Hostname validation
+
 ---
 
 After you create a custom hostname, Cloudflare has to [validate that hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/).
 
 Attempts to validate a Custom Hostname are distributed over seven days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
 
-- For the first 10 attempts:
+* For the first 10 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.05, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
 ```
 
-- For the remaining 65 attempts:
+* For the remaining 65 attempts:
 
 ```txt
 now() + min((floor(60 * pow(1.15, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
index e53e217ee14dd51..3583929fa75cde3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/error-codes.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Error codes - Custom Hostname Validation
+
 ---
 
 When you [validate a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/), you might encounter the following error codes.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
index 12b2229cd3ba429..4e23151ad107b4f 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/pre-validation.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Pre-validation methods - Custom Hostname Validation
+
 ---
 
 Pre-validation methods help verify domain ownership before your customer's traffic is proxying through Cloudflare.
@@ -29,8 +30,10 @@ TXT validation is when your customer adds a `TXT` record to their authoritative
 
 :::note
 
+
 If your customer cannot update their authoritative DNS, you could also use [HTTP validation](#http-tokens).
 
+
 :::
 
 To set up `TXT` validation:
@@ -39,23 +42,21 @@ To set up `TXT` validation:
 
    ```json null {11-12}
    {
-   	"result": [
-   		{
-   			"id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
-   			"hostname": "app.example.com",
-   			// ...
-   			"status": "pending",
-   			"verification_errors": [
-   				"custom hostname does not CNAME to this zone."
-   			],
-   			"ownership_verification": {
-   				"type": "txt",
-   				"name": "_cf-custom-hostname.app.example.com",
-   				"value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
-   			},
-   			"created_at": "2020-03-04T19:04:02.705068Z"
-   		}
-   	]
+   "result": [
+       {
+       "id": "3537a672-e4d8-4d89-aab9-26cb622918a1",
+       "hostname": "app.example.com",
+       // ...
+       "status": "pending",
+       "verification_errors": ["custom hostname does not CNAME to this zone."],
+       "ownership_verification": {
+           "type": "txt",
+           "name": "_cf-custom-hostname.app.example.com",
+           "value": "0e2d5a7f-1548-4f27-8c05-b577cb14f4ec"
+       },
+       "created_at": "2020-03-04T19:04:02.705068Z"
+       }
+   ]
    }
    ```
 
@@ -81,18 +82,18 @@ To get and use the `ownership_verification` record:
 
    ```json title="Example response (truncated)" {8-9}
    {
-   	"result": [
-   		{
-   			"id": "24c8c68e-bec2-49b6-868e-f06373780630",
-   			"hostname": "app.example.com",
-   			// ...
-   			"ownership_verification_http": {
-   				"http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
-   				"http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
-   			},
-   			"created_at": "2020-03-04T20:06:04.117122Z"
-   		}
-   	]
+     "result": [
+       {
+         "id": "24c8c68e-bec2-49b6-868e-f06373780630",
+         "hostname": "app.example.com",
+         // ...
+         "ownership_verification_http": {
+             "http_url": "http://app.example.com/.well-known/cf-custom-hostname-challenge/24c8c68e-bec2-49b6-868e-f06373780630",
+             "http_body": "48b409f6-c886-406b-8cbc-0fbf59983555"
+         },
+         "created_at": "2020-03-04T20:06:04.117122Z"
+       }
+     ]
    }
    ```
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
index 4cc01d36fb14628..37075f00034342b 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/migrating-custom-hostnames.mdx
@@ -15,7 +15,7 @@ description: Learn how to move hostnames between different zones.
 
 As a SaaS provider, you may want, or have, multiple zones to manage hostnames. Each zone can have different configurations or origins, as well as correlate to varying products. You might shift custom hostnames between zones to enable or disable certain features. Cloudflare allows migration within the same account through the steps below:
 
----
+***
 
 ## CNAME
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
index 3c056f32553e457..9623b2a72514ec3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
@@ -11,7 +11,7 @@ sidebar:
   order: 7
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can use custom hostname analytics for two general purposes: exploring how your customers use your product and sharing the benefits provided by Cloudflare with your customers.
 
@@ -19,17 +19,19 @@ These analytics include **Site Analytics**, **Bot Analytics**, **Cache Analytics
 
 :::note
 
+
 The plan of your Cloudflare for SaaS application determines the analytics available for your custom hostnames.
 
+
 :::
 
 ## Explore customer usage
 
 Use custom hostname analytics to help your organization with billing and infrastructure decisions, answering questions like:
 
-- "How many total requests is your service getting?"
-- "Is one customer transferring significantly more data than the others?"
-- "How many global customers do you have and where are they distributed?"
+* "How many total requests is your service getting?"
+* "Is one customer transferring significantly more data than the others?"
+* "How many global customers do you have and where are they distributed?"
 
 If you see one customer is using more data than another, you might increase their bill. If requests are increasing in a certain geographic region, you might want to increase the origin servers in that region.
 
@@ -39,9 +41,9 @@ To access custom hostname analytics, either [use the dashboard](/analytics/faq/a
 
 With custom hostname analytics, you can also share site information with your customers, including data about:
 
-- How many pageviews their site is receiving.
-- Whether their site has a large percentage of bot traffic.
-- How fast their site is.
+* How many pageviews their site is receiving.
+* Whether their site has a large percentage of bot traffic.
+* How fast their site is.
 
 Build custom dashboards to share this information by specifying an individual custom hostname in `clientRequestHTTPHost` field of [any dataset](/analytics/graphql-api/features/data-sets/) that includes this field.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
index 5e86134809b77f7..55fbfb5650d6322 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas.mdx
@@ -6,6 +6,7 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Argo Smart Routing uses real-time global network information to route traffic on the fastest possible path across the Internet. Regardless of geographic location, this allows Cloudflare to optimize routing to make it faster, more reliable, and more secure. As a SaaS provider, you may want to emphasize the quickest traffic delivery for your end customers. To do so, [enable Argo Smart Routing](/argo-smart-routing/get-started/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
index 9b9a27e309eb3ba..16b0b87aaa5f035 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas.mdx
@@ -6,6 +6,7 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Cloudflare makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers. Content can be either static or dynamic: static content is “cacheable” or eligible for caching, and dynamic content is “uncacheable” or ineligible for caching. The cached copies of content are stored physically closer to users, optimized to be fast, and do not require recomputing.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
index 74ec34298a49532..439f92b92dc27a1 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx
@@ -12,13 +12,13 @@ import { APIRequest } from "~/components";
 
 [Early Hints](/cache/advanced-configuration/early-hints/) allows the browser to begin loading resources while the origin server is compiling the full response. This improves webpage’s loading speed for the end user. As a SaaS provider, you may prioritize speed for some of your custom hostnames. Using custom metadata, you can [enable Early Hints](/cache/advanced-configuration/early-hints/#enable-early-hints) per custom hostname.
 
----
+***
 
 ## Prerequisites
 
 Before you can employ Early Hints for SaaS, you need to create a custom hostname. Review [Get Started with Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) if you have not already done so.
 
----
+***
 
 ## Enable Early Hints per custom hostname via the API
 
@@ -29,51 +29,51 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
 3. If you are [creating a new custom hostname](/api/resources/custom_hostnames/methods/create/), make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames"
-	method="POST"
-	json={{
-		hostname: "<CUSTOM_HOSTNAME>",
-		ssl: {
-			method: "http",
-			type: "dv",
-			settings: {
-				http2: "on",
-				min_tls_version: "1.2",
-				tls_1_3: "on",
-				early_hints: "on",
+  path="/zones/{zone_id}/custom_hostnames"
+  method="POST"
+  json={{
+		"hostname": "<CUSTOM_HOSTNAME>",
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on",
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				},
+				"bundle_method": "ubiquitous",
+				"wildcard": false
 			},
-			bundle_method: "ubiquitous",
-			wildcard: false,
-		},
 	}}
 />
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames"
-	method="GET"
-	parameters={{
-		hostname: "{hostname}",
+  path="/zones/{zone_id}/custom_hostnames"
+  method="GET"
+  parameters={{
+		hostname:"{hostname}"
 	}}
 />
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
 <APIRequest
-	path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
-	method="PATCH"
-	json={{
-		ssl: {
-			method: "http",
-			type: "dv",
-			settings: {
-				http2: "on", // Note: These settings will be set to default if not included when updating early hints
-				min_tls_version: "1.2",
-				tls_1_3: "on",
-				early_hints: "on",
+  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+  method="PATCH"
+  json={{
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on", // Note: These settings will be set to default if not included when updating early hints
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				}
 			},
-		},
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
index 1f00c930036f700..599383a86465771 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/index.mdx
@@ -6,11 +6,12 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
+
 ---
 
 Cloudflare for SaaS allows you to deliver the best performance to your end customers by helping enable you to reduce latency through:
 
-- [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
-- [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
-- [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
-- By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
+* [Argo Smart Routing for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/argo-for-saas/) calculates and optimizes the fastest path for requests to travel to your origin.
+* [Early Hints for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas/) provides faster loading speeds for individual custom hostnames by allowing the browser to begin loading responses while the origin server is compiling the full response.
+* [Cache for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/performance/cache-for-saas/) makes customer websites faster by storing a copy of the website’s content on the servers of our globally distributed data centers.
+* By using Cloudflare for SaaS, your customers automatically inherit the benefits of Cloudflare's vast [anycast network](https://www.cloudflare.com/network/).
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
index 8e173849b2eee87..beee8c46e86d55c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-authorities.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-authorities/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
index 0914ddfc956673d..66293af0636f89f 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/certificate-statuses.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
index aaeb2fc1941b5f1..2e40b6f99d15771 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/dcv-validation-backoff.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
index b13a64d43827f6c..c6b4665a4571939 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/hostname-priority.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-and-hostname-priority/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
index 8f572172a0a7569..6b92b6171e4f460 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Custom Certificate Signing Requests
+
 ---
 
 ## Success codes
@@ -22,33 +23,33 @@ head:
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                 |
-| ---------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                       |
-| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                          |
-| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                      |
-| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                                      |
-| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                                   |
-| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                               |
-| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                                |
-| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                               |
-| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                                      |
-| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&\*()=+{}[]                                                                                                                                                   |
-| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                 |
-| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                   |
-| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                                 |
-| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                           |
-| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                                     |
-| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                    |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                           |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                       |
-| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                    |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                        |
+| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                              |
+| 400              | 1401           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                 |
+| 400              | 1402           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                             |
+| 400              | 1405           | Country field is required. Check your input and try again.                                                                                                                                                                                                                                                                           |
+| 400              | 1406           | State field is required. Check your input and try again.                                                                                                                                                                                                                                                                             |
+| 400              | 1407           | Locality field is required. Check your input and try again.                                                                                                                                                                                                                                                                          |
+| 400              | 1408           | Organization field is required. Check your input and try again.                                                                                                                                                                                                                                                                      |
+| 400              | 1409           | Common Name field is required. Check your input and try again.                                                                                                                                                                                                                                                                       |
+| 400              | 1410           | The specified Common Name is too long. Maximum allowed length is %d characters. Check your input and try again.                                                                                                                                                                                                                      |
+| 400              | 1411           | At least one subject alternative name (SAN) is required. Check your input and try again.                                                                                                                                                                                                                                             |
+| 400              | 1412           | Invalid subject alternative name(s) (SAN). SANs have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~`!@#$%^&*()=+{}[]                                                                                                                                       |
+| 400              | 1413           | Subject Alternative Names (SANs) with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                        |
+| 400              | 1414           | Reserved top domain subject alternative names (SAN), such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                          |
+| 400              | 1415           | Unable to parse subject alternative name(s) (SAN) - :reason. Check your input and try again. Reasons: publicsuffix: cannot derive eTLD+1 for domain %q; publicsuffix: invalid public suffix %q for domain %q;                                                                                                                        |
+| 400              | 1416           | Subject Alternative Names (SANs) ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                  |
+| 400              | 1417           | Invalid key type. Only 'rsa2048' or 'p256v1' is accepted. Check your input and try again.                                                                                                                                                                                                                                            |
+| 400              | 1418           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                        |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                       |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                            |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                       |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                           |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                  |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                              |
+| 403              | 1403           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you.                   |
 | 403              | 1404           | Access to generating CSRs has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will contact you. |
-| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                 |
-| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                           |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                         |
+| 404              | 1419           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                        |
+| 409              | 1420           | The custom CSR is associated with an active certificate pack. You will need to delete all associated active certificate packs before you can delete the custom CSR.                                                                                                                                                                  |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
index fc889f9bb826a89..e55d19e7fac4ad4 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
@@ -9,10 +9,11 @@ sidebar:
 head:
   - tag: title
     content: Status codes - Custom hostnames
----
 
 ---
 
+***
+
 ## Success codes
 
 | Endpoint                                                  | Method | Code         |
@@ -23,66 +24,66 @@ head:
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | DELETE | 200 OK       |
 | `/v4/zones/:zone_id/custom_hostnames/:custom_hostname_id` | PATCH  | 202 Accepted |
 
----
+***
 
 ## Error codes
 
-| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                 |
-| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                          |
-| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                      |
-| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                |
-| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                  |
-| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                        |
-| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                           |
-| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                 |
-| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                |
-| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                          |
-| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                           |
-| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                     |
-| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                           |
-| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
-| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
-| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                    |
-| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                               |
-| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                           |
-| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                   |
-| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
-| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                 |
-| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                           |
-| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
-| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                 |
-| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                            |
-| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                            |
-| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                            |
-| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                       |
-| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                               |
-| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                      |
-| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                  |
-| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                     |
-| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                       |
-| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                             |
-| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                 |
-| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                           |
-| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                    |
-| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                 |
-| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
-| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                |
-| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                    |
-| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                           |
-| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                       |
-| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                               |
-| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                          |
-| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
-| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                             |
-| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                              |
-| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                         |
+| HTTP Status Code | API Error Code | Error Message                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400              | 1400           | Unable to decode the JSON request body. Check your input and try again.                                                                                                                                                                                                                                                                                                                                        |
+| 400              | 1401           | Unable to encode the Custom Metadata as JSON. Check your input and try again.                                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1402           | Zone ID is required. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                           |
+| 400              | 1403           | The request has no Authorization header. Check your input and try again.                                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1407           | Invalid custom hostname. Custom hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                                 |
+| 400              | 1408           | Custom hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1409           | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                                   |
+| 400              | 1410           | Unable to parse custom hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain` <br/> publicsuffix: invalid public suffix `:suffix` for domain `:domain`                                                                                                                                                                         |
+| 400              | 1411           | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                            |
+| 400              | 1412           | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. <br/> **Note:** <br/> This message is only presented to customers who have opted out of wildcard support for custom metadata.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1415           | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                                                 |
+| 400              | 1416           | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                           |
+| 400              | 1417           | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again.                                                                                                                                                                                                                                                            |
+| 400              | 1418           | Unable to parse custom origin hostname - `:reason`. Check your input and try again. <br/> **Reasons:** <br/> publicsuffix: cannot derive eTLD+1 for domain `:domain`<br/> publicsuffix: invalid public suffix`:suffix`for domain`:domain`                                                                                                                                                                      |
+| 400              | 1419           | Custom origin hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again.                                                                                                                                                                                                                                                                                     |
+| 400              | 1420           | Wildcard custom origin hostnames are not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1421           | The custom origin hostname you specified does not exist on Cloudflare as a DNS record (A, AAAA or CNAME) in your zone:`:zone\_tag`. Check your input and try again.                                                                                                                                                                                                                                            |
+| 400              | 1422           | Invalid `http2`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                        |
+| 400              | 1423           | Invalid`tls\_1\_2\_only`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                               |
+| 400              | 1424           | Invalid`tls\_1\_3`setting. Only 'on' or 'off' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                     |
+| 400              | 1425           | Invalid`min\_tls\_version`setting. Only '1.0','1.1','1.2' or '1.3' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                |
+| 400              | 1426           | The certificate that you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                            |
+| 400              | 1427           | The certificate that you uploaded is empty. Check your input and try again.                                                                                                                                                                                                                                                                                                                                    |
+| 400              | 1428           | The private key you uploaded cannot be parsed. Check your input and try again.                                                                                                                                                                                                                                                                                                                                 |
+| 400              | 1429           | The private key you uploaded does not match the certificate. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1430           | The custom CSR ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                                  |
+| 404              | 1431           | The custom CSR was not found.                                                                                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1432           | The validation method is not supported. Only`http`, `email`, or `txt` are accepted. Check your input and try again.                                                                                                                                                                                                                                                                                            |
+| 400              | 1433           | The validation type is not supported. Only 'dv' is accepted. Check your input and try again.                                                                                                                                                                                                                                                                                                                   |
+| 400              | 1434           | The SSL attribute is invalid. Refer to the API documentation, check your input and try again.                                                                                                                                                                                                                                                                                                                  |
+| 400              | 1435           | The custom hostname ID is invalid. Check your input and try again.                                                                                                                                                                                                                                                                                                                                             |
+| 404              | 1436           | The custom hostname was not found.                                                                                                                                                                                                                                                                                                                                                                             |
+| 400              | 1437           | Invalid hostname.contain query parameter. The hostname.contain query parameter has to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as \`\`\~\`!@#$%^&\*()=+{}\[]\\                                                                                                                                                                             |
+| 400              | 1438           | Cannot specify other filter parameters in addition to `id`. Only one must be specified. Check your input and try again.                                                                                                                                                                                                                                                                                        |
+| 409              | 1439           | Modifying the custom hostname is not supported. Check your input and try again.                                                                                                                                                                                                                                                                                                                                |
+| 400              | 1440           | Both validation type and validation method are required. Check your input and try again.                                                                                                                                                                                                                                                                                                                       |
+| 400              | 1441           | The certificate that you uploaded is having trouble bundling against the public trust store. Check your input and try again.                                                                                                                                                                                                                                                                                   |
+| 400              | 1442           | Invalid `ciphers` setting. Refer to the documentation for the list of accepted cipher suites. Check your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1443           | Cipher suite selection is not supported for a minimum TLS version of 1.3. Check your input and try again.                                                                                                                                                                                                                                                                                                      |
+| 400              | 1444           | The certificate chain that you uploaded has multiple leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                        |
+| 400              | 1445           | The certificate chain that you uploaded has no leaf certificates. Check your input and try again.                                                                                                                                                                                                                                                                                                              |
+| 400              | 1446           | The certificate that you uploaded does not include the custom hostname - `:custom_hostname`. Review your input and try again.                                                                                                                                                                                                                                                                                  |
+| 400              | 1447           | The certificate that you uploaded does not use a supported signature algorithm. Only SHA-256/ECDSA, SHA-256/RSA, and SHA-1/RSA signature algorithms are supported. Review your input and try again.                                                                                                                                                                                                            |
+| 400              | 1448           | Custom hostnames with wildcards are not supported for certificates managed by Cloudflare. Review your input and try again.                                                                                                                                                                                                                                                                                     |
+| 400              | 1449           | The request input `bundle_method` must be one of: ubiquitous, optimal, force.                                                                                                                                                                                                                                                                                                                                  |
+| 401              | 1000           | Unable to extract bearer token                                                                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1001           | Unable to parse JWT token                                                                                                                                                                                                                                                                                                                                                                                      |
+| 401              | 1002           | Bad JWT header                                                                                                                                                                                                                                                                                                                                                                                                 |
+| 401              | 1003           | Failed to verify JWT token                                                                                                                                                                                                                                                                                                                                                                                     |
+| 401              | 1004           | Failed to get claims from JWT token                                                                                                                                                                                                                                                                                                                                                                            |
+| 401              | 1005           | JWT token does not have required claims                                                                                                                                                                                                                                                                                                                                                                        |
+| 403              | 1404           | No quota has been allocated for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                |
+| 403              | 1405           | Quota exceeded. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                                                                                           |
+| 403              | 1413           | No [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) access has been allocated for this zone. If you are already a paid  customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you. |
+| 403              | 1414           | Access to setting a custom origin server has not been granted for this zone. If you are already a paid Cloudflare for SaaS customer, contact your Customer Success Manager for additional provisioning. If you are not yet enrolled, [fill out this contact form](https://www.cloudflare.com/plans/enterprise/contact/) and our sales team will reach out to you.                                              |
+| 409              | 1406           | Duplicate custom hostname found.                                                                                                                                                                                                                                                                                                                                                                               |
+| 500              | 1500           | Internal Server Error                                                                                                                                                                                                                                                                                                                                                                                          |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
index 7ecb44f98f46429..51109dbc3c37bd3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 4
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When you perform [TXT](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/) domain control validation, you will need to share these tokens with your customers.
 
@@ -18,9 +19,8 @@ However, these tokens expire after a certain amount of time, depending on your c
 | --------------------- | -------------- |
 | Let's Encrypt         | 7 days         |
 | Google Trust Services | 14 days        |
-| SSL.com               | 14 days        |
+| SSL.com | 14 days        |
 
 :::caution
-
-<Render file="dcv-invalid-token-situations" product="ssl" />
+ <Render file="dcv-invalid-token-situations" product="ssl" />
 :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
index b13acdc07c26874..916488e61763006 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx
@@ -32,13 +32,13 @@ Using a [TXT](#dns-txt-record) or [HTTP](#http-token) validation method helps yo
 
 #### DNS TXT Record
 
-When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
+When creating a Custom Hostname with the TXT method through the [API](/api/resources/custom_hostnames/methods/create/), a TXT ownership\_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
 
 #### HTTP Token
 
-When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
+When creating a Custom Hostname with the HTTP through the [API](/api/resources/custom_hostnames/methods/create/), an HTTP ownership\_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
 
-Cloudflare sends GET requests to the http_url using `User-Agent: Cloudflare Custom Hostname Verification`.
+Cloudflare sends GET requests to the http\_url using `User-Agent: Cloudflare Custom Hostname Verification`.
 
 If you validated a hostname that is not proxying traffic through Cloudflare, the Custom Hostname will be marked as **Active** in the Cloudflare SSL/TLS app when the HTTP token is verified (under the **Custom Hostnames** tab).
 
@@ -73,8 +73,10 @@ Once the migration has been started for your zone(s), Cloudflare will require ev
 
 :::note
 
+
 You can revert the migration at any time.
 
+
 :::
 
 ### Before the migration
@@ -83,15 +85,15 @@ Before your migration, you should:
 
 1. To test validation methods, set up a test zone and ask your account team to enable SSL for SaaS v2.
 2. Wait for your account team to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
-   - `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
-   - `test_active`: Passed CNAME verification
-   - `test_active_apex`: Passed Apex Proxy verification
-   - `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
-   - `test_failed`: Failed hostname verification 25 times
+   * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
+   * `test_active`: Passed CNAME verification
+   * `test_active_apex`: Passed Apex Proxy verification
+   * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your account team to verify banned custom hostnames and proceed with the migration.
+   * `test_failed`: Failed hostname verification 25 times
 3. Review the results of our pre-migration tool (run by your account team) using one of the following methods:
-   - Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
-   - Via a CSV file (provided by your account team)
-   - Via the Cloudflare dashboard:
+   * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
+   * Via a CSV file (provided by your account team)
+   * Via the Cloudflare dashboard:
      ![Review SSL migration status in the dashboard](~/assets/images/cloudflare-for-platforms/ssl-migration-status.png)
 4. Approve the migration. Your account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
index 2264ad62fa3dbc5..edf8ce49e980942 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Resources for SaaS customers
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare partners with many [SaaS providers](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/) to extend our performance and security benefits to your website.
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
index 63c9a0ce28c29a6..0681efe793946a6 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility.mdx
@@ -30,12 +30,12 @@ This is not an exhaustive list of Cloudflare products and features.
 | [China Network](/china-network/)                                                                    | No            | No                 |                                                                                                                                                                                                                                                                                                                                                                   |
 | [DNS](/dns/)                                                                                        | Yes\*         | Yes                | As a SaaS customer, do not remove the records related to your Cloudflare for SaaS setup.<br/><br/>Otherwise, your traffic will begin routing away from your SaaS provider.                                                                                                                                                                                        |
 | [HTTP/2 prioritization](https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/) | Yes           | Yes\*              | This feature must be enabled on the customer zone to function.                                                                                                                                                                                                                                                                                                    |
-| [Image resizing](/images/optimization/transformations/overview/)                                    | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Image resizing](/images/optimization/transformations/overview/)                                                         | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | IPv6                                                                                                | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [IPv6 Compatibility](/network/ipv6-compatibility/)                                                  | Yes           | Yes\*              | If the customer zone has **IPv6 Compatibility** enabled, generally the SaaS zone should as well.<br/><br/>If not, make sure the SaaS zone enables [Pseudo IPv4](/network/pseudo-ipv4/).                                                                                                                                                                           |
 | [Load Balancing](/load-balancing/)                                                                  | No            | Yes                | Customer zones can still use Load Balancing for non-O2O traffic.                                                                                                                                                                                                                                                                                                  |
 | [Page Rules](/rules/page-rules/)                                                                    | Yes\*         | Yes                | Page Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                                |
-| [Origin Rules](/rules/origin-rules/)                                                                | No            | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
+| [Origin Rules](/rules/origin-rules/)                                                                | No           | Yes                |                                                                                                                                                                                                                                       |
 | [Client-side security](/client-side-security/) (formerly Page Shield)                               | Yes           | Yes                |                                                                                                                                                                                                                                                                                                                                                                   |
 | [Polish](/images/polish/)                                                                           | Yes\*         | Yes                | Polish only runs on cached assets. If the customer zone is bypassing cache for SaaS zone destined traffic, then images optimized by Polish will not be loaded from origin.                                                                                                                                                                                        |
 | [Rate Limiting](/waf/rate-limiting-rules/)                                                          | Yes\*         | Yes                | Rate Limiting rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website.                                                                                                                                                                                                                                       |
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
index cff52354c33fa79..8f5c695a4ed8b46 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx
@@ -31,9 +31,9 @@ Webflow customers can enable O2O on any Cloudflare zone plan.
 
 To enable O2O for a specific hostname within a Cloudflare Zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with your Webflow site name as the target. Webflow's domain addition setup will walk you through other validation steps.
 
-| Type    | Name            | Target            | Proxy status |
-| ------- | --------------- | ----------------- | ------------ |
-| `CNAME` | `<YOUR_DOMAIN>` | `cdn.webflow.com` | Proxied      |
+| Type    | Name                 | Target                | Proxy status |
+| ------- | -------------------- | --------------------- | ------------ |
+| `CNAME` | `<YOUR_DOMAIN>`      | `cdn.webflow.com`     | Proxied      |
 
 ## Zone hold
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
index 38885b976200c1e..5f503f70abb253c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/certificate-statuses.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /ssl/reference/certificate-statuses/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
index 335795eba693675..541ee92bd1ce3a3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Manage custom certificates
+
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs } from "~/components"
 
 Learn how to manage custom certificates for your Cloudflare for SaaS custom hostnames. For use cases and limitations, refer to [custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/).
 
@@ -85,7 +86,7 @@ To replace a single custom certificate within a certificate pack that contains t
 
 You can only replace an RSA certificate with another RSA certificate, or an ECDSA certificate with another ECDSA certificate.
 
----
+***
 
 ## Move to a Cloudflare certificate
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
index 3b173935c952ce9..4a1ffdb4234511d 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx
@@ -11,15 +11,16 @@ sidebar:
 head:
   - tag: title
     content: Delegated domain control validation (DCV)
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Delegated DCV allows SaaS providers to delegate the DCV process to Cloudflare.
 
 DCV Delegation requires your customers to place a one-time record at their authoritative DNS that allows Cloudflare to auto-renew all future certificate orders, so that there is no manual intervention from you or your customers at the time of the renewal.
 
----
+***
 
 ## Setup
 
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
index e4cb716dca2b5d4..60f518c1628966e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting | Certificate validation
+
 ---
 
 ## High-risk domains
@@ -19,7 +20,7 @@ Occasionally, a domain will be flagged as “high risk” by Cloudflare’s CA p
 
 If a domain is flagged by the CA, you need to contact Support before validation can finish. The API call will return indicating the failure, along with a link to where the ticket can be filed.
 
----
+***
 
 ## Certificate Authority Authorization (CAA) records
 
@@ -43,26 +44,26 @@ In some cases, the validation may be prevented because your hostname points to a
 
 In this case you would need to either select a Certificate Authority whose CAA records are present at the target, or review the configuration with the service provider that owns the target.
 
----
+***
 
 ## Time outs
 
 If a certificate issuance times out, the error message will indicate where the timeout occurred:
 
-- Timed Out (Initializing)
-- Timed Out (Validation)
-- Timed Out (Issuance)
-- Timed Out (Deployment)
-- Timed Out (Deletion)
+* Timed Out (Initializing)
+* Timed Out (Validation)
+* Timed Out (Issuance)
+* Timed Out (Deployment)
+* Timed Out (Deletion)
 
 To fix this error, send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) through the API or select **Refresh** for the specific custom hostname in the dashboard. If using the API, make sure that the `--data` field contains an `ssl` object with the same `method` and `type` as the original request.
 
 If these return an error, delete and recreate the custom hostname.
 
----
+***
 
 ## Immediate validation checks
 
 You can send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) to request an immediate validation check on any certificate. The PATCH data should include the same `ssl` object as the original request.
 
----
+***
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
index 7ac9fd652e89438..3545c355b84844b 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/webhook-definitions.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 5
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 When you [create a webhook notification](/notifications/get-started/configure-webhooks/) for **SSL for SaaS Custom Hostnames**, you may want to automate responses to specific events (certificate issuance, failed validation, etc.).
 
@@ -26,38 +26,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.validation.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.validation.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -67,49 +67,49 @@ Cloudflare sends this alert each time a certificate remains in a `pending_valida
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.validation.failed",
-			"created_at": "2018-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_validation",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "blog.example.com reported as potential risk: google_safe_browsing"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.validation.failed",
+      "created_at": "2018-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_validation",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "blog.example.com reported as potential risk: google_safe_browsing"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate issuance
 
@@ -121,38 +121,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_val
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.issuance.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.issuance.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -162,49 +162,49 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.issuance.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "caa_error: blog.example.com"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.issuance.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "caa_error: blog.example.com"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate deployment
 
@@ -216,38 +216,38 @@ Cloudflare sends this alert when certificates move from a status of `pending_dep
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deployment.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "active",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deployment.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "active",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -257,42 +257,42 @@ Cloudflare sends this alert each time a certificate remains in a status of `pend
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deployment.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deployment.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate deletion
 
@@ -302,34 +302,34 @@ Cloudflare sends this alert when certificates move from a status of `pending_del
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deletion.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "deleted"
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deletion.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "deleted"
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -339,38 +339,38 @@ Cloudflare sends this alert each time a certificate remains in status of `pendin
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.deletion.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deletion"
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.deletion.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deletion"
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
----
+***
 
 ## Certificate renewal
 
@@ -382,43 +382,43 @@ The actions that you need to perform to renew certificates depend on your [valid
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"status": "active",
-			"hosts": ["blog.example.com"],
-			"issuer": "DigiCertInc",
-			"serial_number": "1001172778337169491",
-			"signature": "ECDSAWithSHA256",
-			"uploaded_on": "2021-11-17T04:33:54.561747Z",
-			"expires_on": "2022-11-21T12:00:00Z",
-			"custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.upcoming_certificate_expiration_notification",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "status": "active",
+      "hosts": ["blog.example.com"],
+      "issuer": "DigiCertInc",
+      "serial_number": "1001172778337169491",
+      "signature": "ECDSAWithSHA256",
+      "uploaded_on": "2021-11-17T04:33:54.561747Z",
+      "expires_on": "2022-11-21T12:00:00Z",
+      "custom_csr_id": "7b163417-1d2b-4c84-a38a-2fb7a0cd7752",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -428,38 +428,38 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.succeeded",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_deployment",
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.succeeded",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_deployment",
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -469,45 +469,45 @@ Cloudflare sends this alert when certificates move from a status of `active` to
 
 ```json
 {
-	"metadata": {
-		"event": {
-			"id": "<<WEBHOOK_ID>",
-			"type": "ssl.custom_hostname_certificate.renewal.failed",
-			"created_at": "2022-02-09T00:03:28.385080Z"
-		},
-		"account": {
-			"id": "<<ACCOUNT_ID>"
-		},
-		"zone": {
-			"id": "<<ZONE_ID>"
-		}
-	},
-	"data": {
-		"id": "<<CUSTOM_HOSTNAME_ID>",
-		"hostname": "blog.com",
-		"ssl": {
-			"id": "<<CERTIFICATE_ID>",
-			"type": "dv",
-			"method": "cname",
-			"status": "pending_issuance",
-			"cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
-			"cname_target": "dcv.digicert.com",
-			"validation_errors": [
-				{
-					"message": "caa_error: blog.example.com"
-				}
-			],
-			"settings": {
-				"min_tls_version": "1.2",
-				"http2": "on"
-			}
-		},
-		"custom_metadata": {
-			"key1": "value1",
-			"key2": "value2"
-		},
-		"custom_origin_server": "0001.blog.com"
-	}
+  "metadata": {
+    "event": {
+      "id": "<<WEBHOOK_ID>",
+      "type": "ssl.custom_hostname_certificate.renewal.failed",
+      "created_at": "2022-02-09T00:03:28.385080Z"
+    },
+    "account": {
+      "id": "<<ACCOUNT_ID>"
+    },
+    "zone": {
+      "id": "<<ZONE_ID>"
+    }
+  },
+  "data": {
+    "id": "<<CUSTOM_HOSTNAME_ID>",
+    "hostname": "blog.com",
+    "ssl": {
+      "id": "<<CERTIFICATE_ID>",
+      "type": "dv",
+      "method": "cname",
+      "status": "pending_issuance",
+      "cname": "_ca3-64ce913ebfe74edeb2e8813e3928e359.app.example2.com",
+      "cname_target": "dcv.digicert.com",
+      "validation_errors": [
+        {
+          "message": "caa_error: blog.example.com"
+        }
+      ],
+      "settings": {
+        "min_tls_version": "1.2",
+        "http2": "on"
+      }
+    },
+    "custom_metadata": {
+      "key1": "value1",
+      "key2": "value2"
+    },
+    "custom_origin_server": "0001.blog.com"
+  }
 }
 ```
 
@@ -521,9 +521,6 @@ This behavior is because each custom hostname can only have one certificate atta
 
 You can configure alerts to receive notifications for changes in your custom hostname certificates.
 
-<AvailableNotifications
-	product="SSL/TLS"
-	notificationFilter="SSL for SaaS Custom Hostnames Alert"
-/>
+<AvailableNotifications product="SSL/TLS" notificationFilter="SSL for SaaS Custom Hostnames Alert" />
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
index dad31a4c49f6b78..79e692861ae83d3 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/index.mdx
@@ -6,12 +6,13 @@ products:
   - cloudflare-for-saas
 sidebar:
   order: 3
+
 ---
 
 Cloudflare for SaaS provides increased security per custom hostname through:
 
-- [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
-  - [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
-  - [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
-- Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
-- Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
+* [Certificate management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/)
+  * [Issue certificates through Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/)
+  * [Upload your own certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)
+* Control your traffic's level of encryption with [TLS settings](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/)
+* Create and deploy WAF custom rules, rate limiting rules, and managed rulesets using [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/)
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
index 8c044e098c1a507..a9b88bc6d3f027e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx
@@ -9,7 +9,7 @@ sidebar:
   label: Setup
 ---
 
-import { DashButton, APIRequest } from "~/components";
+import { DashButton, APIRequest, } from "~/components";
 
 [Web Application Firewall (WAF)](/waf/) allows you to create additional security measures through Cloudflare. As a SaaS provider, you can link custom rules, rate limiting rules, and managed rules to your custom hostnames. This provides more control to keep your domains safe from malicious traffic.
 
@@ -74,38 +74,40 @@ This assigns custom metadata to your custom hostname so that it has a security t
 2. Build your rules either [through the dashboard](/waf/custom-rules/create-dashboard/) or via the API. An example rate limiting rule, corresponding to `"security_level"` low, is shown below as an API call.
 
 <APIRequest
-	path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
-	method="PUT"
-	json={{
-		rules: [
+  path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
+  method="PUT"
+  json={{
+		"rules": [
 			{
-				action: "block",
-				ratelimit: {
-					characteristics: ["cf.colo.id", "ip.src"],
-					period: 10,
-					requests_per_period: 2,
-					mitigation_timeout: 60,
+				"action": "block",
+				"ratelimit": {
+					"characteristics": [
+						"cf.colo.id",
+						"ip.src"
+					],
+					"period": 10,
+					"requests_per_period": 2,
+					"mitigation_timeout": 60
 				},
-				expression:
-					'lookup_json_string(cf.hostname.metadata, "security_level") eq "low" and http.request.uri contains "login"',
-			},
-		],
+				"expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
+			}
+		]
 	}}
 	parameters={{
-		ruleset_phase: "http_ratelimit",
+		ruleset_phase: "http_ratelimit"
 	}}
 />
 
 To build rules through the dashboard:
 
-1.  In the Cloudflare dashboard, go to the **WAF** page.
+1. In the Cloudflare dashboard, go to the **WAF** page.
 
-        <DashButton url="/?to=/:account/application-security/waf" />
+		<DashButton url="/?to=/:account/application-security/waf" />
 
-2.  Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
+2. Follow the instructions on the dashboard specific to custom rules, rate limiting rules, or managed rules, depending on your security goal.
 
-3.  Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
+3. Once the rule is active, you should see it under the applicable tab (custom rules, rate limiting, or managed rules).
 
-    :::caution
-    This API call will replace any existing rate limiting rules in the zone.
-    :::
+   :::caution
+   This API call will replace any existing rate limiting rules in the zone.
+   :::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
index 44166be7219fb59..5f74db1bcc4eac2 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /data-localization/how-to/cloudflare-for-saas/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
index e385caf0bc3f783..b3bba3fd7a2c5ea 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
@@ -55,9 +55,9 @@ You do not need to add individual Worker routes for each custom hostname. The wi
 
      For example, if your zone is `saasprovider.com` and you want `api.saasprovider.com` to bypass the Worker, create an additional route `api.saasprovider.com/*` with no Worker assigned. More specific routes take precedence over wildcard routes.
 
-   - **Route only custom hostname traffic to the Worker**:
-   - **Route**: `vanity.customer.com`
-   - **Worker**: Select the Worker used for your SaaS application.
+    - **Route only custom hostname traffic to the Worker**:
+     - **Route**: `vanity.customer.com`
+     - **Worker**: Select the Worker used for your SaaS application.
 
 5. Click **Save**.
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
index 7c32801c1a98fdd..b5e1b4537b932f3 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/bindings.mdx
@@ -9,13 +9,11 @@ sidebar:
 products:
   - cloudflare-for-platforms
 ---
-
 import { Aside } from "@astrojs/starlight/components";
 
 When you deploy User Workers through Workers for Platforms, you can attach [bindings](/workers/runtime-apis/bindings/) to give them access to resources like [KV namespaces](/kv/), [D1 databases](/d1/), [R2 buckets](/r2/), and more. This enables your end customers to build more powerful applications without you having to build the infrastructure components yourself.
 
 With bindings, each of your users can have their own:
-
 - [KV namespace](/kv/) that they can use to store and retrieve data
 - [R2 bucket](/r2/) that they can use to store files and assets
 - [Analytics Engine](/analytics/analytics-engine/) dataset that they can use to collect observability data
@@ -28,11 +26,9 @@ Each User Worker can only access the bindings that are explicitly attached to it
 ![Resource Isolation Model](~/assets/images/reference-architecture/programmable-platforms/programmable-platforms-5.svg "Resource Isolation Model")
 
 ## Adding a KV Namespace to a User Worker
-
 This example walks through how to create a [KV namespace](/kv/) and attach it to a User Worker. The same process can be used to attach to other [bindings](/workers/runtime-apis/bindings/).
 
 ### 1. Create a KV namespace
-
 Create a KV namespace using the [Cloudflare API](/api/resources/kv/subresources/namespaces/methods/bulk_update/).
 
 ### 2. Attach the KV namespace to the User Worker
@@ -62,7 +58,6 @@ curl -X PUT \
   }' \
   -F 'worker.js=@/path/to/worker.js'
 ```
-
 Now, the User Worker has can access the `USER_KV` binding through the `env` argument using `env.USER_DATA.get()`, `env.USER_DATA.put()`, and other KV methods.
 
 Note: If you plan to add new bindings to the Worker, use the `keep_bindings` parameter to ensure existing bindings are preserved while adding new ones.
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
index 9cdf87f9fd91826..6a9982c4fc08bc4 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx
@@ -31,7 +31,7 @@ A [Tail Worker](/workers/observability/logs/tail-workers/) receives information
 
 Use [Tail Workers](/workers/observability/logs/tail-workers/) instead of Logpush if you want granular control over formatting before logs are sent to their destination to receive [diagnostics channel events](/workers/runtime-apis/nodejs/diagnostics-channel), or if you want logs delivered in real-time.
 
-Adding a Tail Worker to your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
+Adding a Tail Worker to  your dispatch Worker collects logs for both the dispatch Worker and for any user Workers in the dispatch namespace. Logs are automatically collected for all new Workers added to a dispatch namespace. To enable logging for an individual user Worker rather than an entire dispatch namespace, add the [Tail Worker configuration](/workers/observability/logs/tail-workers/#configure-tail-workers) directly to the user Worker.
 
 ## Analytics
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
index a5d3d76bafe414b..b5f72ee55754ce1 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-for-platforms
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Script limits
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
index c7998ff2541bb30..4ed59262b2ebb15 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/platform-examples.mdx
@@ -18,7 +18,7 @@ import {
 	ResourcesBySelector,
 } from "~/components";
 
-The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically.
+The following examples show how to use Cloudflare's REST API and TypeScript SDK to deploy and manage Workers programmatically. 
 
 ### Prerequisites
 
diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
index 4842b92536a2d6c..378810ebff4dd3e 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/worker-isolation.mdx
@@ -18,11 +18,11 @@ In untrusted mode:
 - Each Worker has an isolated cache, when using the [Cache API](/workers/runtime-apis/cache/) or when making subrequests using `fetch()`, which egress via [Cloudflare's cache](/cache/)
 - [`caches.default`](/workers/reference/how-the-cache-works/#cache-api) is disabled for all Workers in the namespace
 
-This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access.
+This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access. 
 
 ### Trusted Mode
 
-If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code.
+If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code. 
 
 In trusted mode:
 
@@ -31,10 +31,9 @@ In trusted mode:
 
 :::note
 In trusted mode, Workers can potentially access cached responses from other Workers in the namespace. Only enable this if you control all Worker code or have appropriate cache key isolation strategies.
-:::
+::: 
 
 To convert a namespace from untrusted to trusted:
-
 ```bash
 curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace_name}" \
   -H "Authorization: Bearer {api_token}" \
@@ -43,16 +42,14 @@ curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/
     "name": "{namespace_name}",
     "trusted_workers": true
   }'
-```
+  ```
 
-If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it.
+If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it. 
 
 ### Maintaining cache isolation in trusted mode
-
-If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys.
+If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
 
 ## Related Resources
-
-- [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
-- [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
-- [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
+* [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/reference/limits) - Understanding script and API limits
+* [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers
+* [Request cf object](/workers/runtime-apis/request/#the-cf-property-requestcf) - Details on the cf object properties
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
index c2bc163fbb4b639..1d4db0fb3f37d82 100644
--- a/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
+++ b/src/content/docs/cloudflare-network-firewall/best-practices/minimal-ruleset.mdx
@@ -12,6 +12,7 @@ sidebar:
 head:
   - tag: title
     content: Minimal suggested ruleset
+
 ---
 
 The suggested minimal ruleset blocks some known common vectors for DDoS attacks and permits all other ESP, TCP, UDP, GRE and ICMP traffic.
@@ -65,17 +66,17 @@ The information below covers traffic type, how the port is used, and reasons for
 
 The list below is a common list of traffic types you should also consider blocking or restricting inbound.
 
-- SFTP, TFTP
-- SSH, Telnet
-- RDP
-- RCP
-- SMCP
-- NTP
-  - Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
-- MS-SQL
-  - Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
-- HTTP and HTTPS
-  - If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
+* SFTP, TFTP
+* SSH, Telnet
+* RDP
+* RCP
+* SMCP
+* NTP
+  * Common vector for reflection attacks. Consider using [Cloudflare Gateway](/web3/), [1.1.1.1's DNS over HTTPS (DoH)](/1.1.1.1/), or an internal DNS service if possible. Consider restricting your firewall rules to only allow the source and destination of DNS traffic.
+* MS-SQL
+  * Common vector and [increasingly used as vector for DDoS attacks](https://blog.cloudflare.com/ddos-attack-trends-for-2021-q4/). Block if unused or consider restricting only to the required source IP addresses.
+* HTTP and HTTPS
+  * If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
 
 If relevant to your environment, consider blocking based on geolocation data, which blocks traffic based on the country or user when an end user's IP address is registered in the geolocation database.
 
diff --git a/src/content/docs/cloudflare-network-firewall/index.mdx b/src/content/docs/cloudflare-network-firewall/index.mdx
index f546e7f0e9b2faa..f5c445fd27e1de4 100644
--- a/src/content/docs/cloudflare-network-firewall/index.mdx
+++ b/src/content/docs/cloudflare-network-firewall/index.mdx
@@ -20,8 +20,8 @@ import {
 } from "~/components";
 
 <Description>
-	Filter and block unwanted traffic at Cloudflare's global network, before it
-	reaches your infrastructure.
+	Filter and block unwanted traffic at Cloudflare's global network,
+	before it reaches your infrastructure.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
index 53c0015446461f2..70c21d97f76d65a 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/collect-pcaps.mdx
@@ -304,4 +304,4 @@ Due to the nature of Cloudflare network, your traffic may traverse various physi
 
 - Multiple PCAP Files: A single full PCAP capture may produce many small PCAP files, as a capture is taken for each physical server your traffic traverses in a Cloudflare location.
   - You can get more granular by applying packet-specific filters like protocol, port (and more) to target the traffic you need.
-- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
+- Merging for Analysis: To view the traffic as a single flow, you can use a tool like mergecap to combine the individual files into one larger file for analysis in Wireshark. Refer to the [Wireshark mergecap documentation](https://www.wireshark.org/docs/wsug_html_chunked/AppToolsmergecap.html) for instructions.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
index 2ee588985ab4a4f..6f7330a2abce626 100644
--- a/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
+++ b/src/content/docs/cloudflare-network-firewall/packet-captures/pcaps-bucket-setup.mdx
@@ -174,7 +174,7 @@ To start collecting packet captures with R2, you first need to configure it prop
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-   <DashButton url="/?to=/:account/r2/overview" />
+	<DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -218,4 +218,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
index 1833bff8925d2c5..190cc5e6da18dfa 100644
--- a/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
+++ b/src/content/docs/cloudflare-network-firewall/troubleshooting/diagnose-traffic-decisions.mdx
@@ -21,9 +21,9 @@ Traffic passing through Cloudflare's network is evaluated by several independent
 Each system operates independently. Traffic blocked by an earlier system never reaches later systems for evaluation.
 
 :::caution
-Creating an allow rule in Network Firewall does **not** bypass DDoS
-protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
-rules, you must configure bypasses in those systems separately.
+	Creating an allow rule in Network Firewall does **not** bypass DDoS
+	protection. If traffic is blocked by Advanced TCP Protection or DDoS managed
+	rules, you must configure bypasses in those systems separately.
 :::
 
 To diagnose blocked traffic, use [Network Analytics](/analytics/network-analytics/) to identify which system is blocking the traffic and why. If Network Analytics does not provide enough information, you can use packet captures for deeper analysis.
@@ -99,4 +99,4 @@ If you cannot identify the issue from Network Analytics, use [packet captures](/
 - [Network Analytics](/analytics/network-analytics/)
 - [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/)
 - [Network Firewall rule configuration](/cloudflare-network-firewall/how-to/add-policies/)
-- [Packet captures](/cloudflare-network-firewall/packet-captures/)
+- [Packet captures](/cloudflare-network-firewall/packet-captures/)
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
index 3b09b3e2ad4da6e..24eaf60c6cf1b66 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
index 69fc5cb5e2e1111..db274e1c338cdc3 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/require-access-protection.mdx
@@ -7,7 +7,7 @@ title: Require Access protection
 sidebar:
   order: 3
 tags:
-  - Security
+- Security
 ---
 
 Cloudflare Access allows you to require Access protection for all hostnames in your account. When this setting is turned on, traffic to any hostname without a matching [Access application](/cloudflare-one/access-controls/applications/) is automatically blocked.
@@ -23,13 +23,13 @@ Turning on Access protection blocks traffic to any hostname that does not have a
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and go to **Zero Trust** > **Access controls** > **Access settings**.
 2. Turn on **Block traffic to all domains in this account**. You will see a dialog confirming you understand the scope of this change. Select **Confirm**.
 
-   Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
+	Traffic to all hostnames in the account is now blocked unless an Access application exists for the hostname.
 
 3. (Optional) Under **Hostnames to Exempt**, select specific domains to exempt from the **Block traffic to all domains in this account** setting. Traffic to exempted hostnames is allowed even if no Access application exists.
 
-   :::note
-   Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
-   :::
+	:::note
+	Cloudflare recommends limiting exemptions to hostnames that host only public-facing content. Internal applications should have an Access application configured.
+	:::
 
 ## Allow traffic to a hostname
 
diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
index d74a4f8adf061e0..d5cc04f026c092a 100644
--- a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx
@@ -100,7 +100,6 @@ Users who match a policy configured with a _Same as application session timeout_
 When [Authenticate with Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/#configure-client-sessions-in-access) is enabled for an Access application, the Cloudflare One Client session duration takes precedence over all other session durations (application, policy, and global). As long as the Cloudflare One Client session is valid and the user is running the Cloudflare One Client, the user will not be prompted to re-authenticate with the IdP — even if the global session has expired.
 
 ### MFA session duration
-
 If you use [independent multi-factor authentication (MFA)](/cloudflare-one/access-controls/access-settings/independent-mfa/), the MFA session duration determines how long a user can log in to Cloudflare Access without being prompted for MFA. The MFA session is independent of the global, policy, and application session durations. When logging in to an Access app with [MFA enabled](/cloudflare-one/access-controls/policies/mfa-requirements/#configure-independent-mfa-for-an-application), users must complete an MFA challenge if their last MFA authentication falls outside the configured session duration. After authenticating with their identity provider, users are prompted for MFA. The [`CF_Device` cookie](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#cf_device) ensures both authentication steps occur on the same device. MFA session durations do not affect how long a user has access to the application (that is controlled by the [application token](#session-durations)).
 
 ### Order of enforcement
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
index f387963685b0849..603b94d330906d6 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
index f4dd978b1db79a4..cfff5ab05a7f8ee 100644
--- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
@@ -179,9 +179,9 @@ You can assign aliases to tools to give them clearer names in the portal. Aliase
 
 Aliases can be set at two levels:
 
-| Level            | Field          | Scope                                                                                   |
-| ---------------- | -------------- | --------------------------------------------------------------------------------------- |
-| **Server-level** | `alias`        | Applies to the tool across all portals that include this server                         |
+| Level | Field | Scope |
+| ----- | ----- | ----- |
+| **Server-level** | `alias` | Applies to the tool across all portals that include this server |
 | **Portal-level** | `portal_alias` | Applies only within this specific portal and takes priority over the server-level alias |
 
 When a tool has multiple names configured, the portal uses the following priority order: `portal_alias` > `server_alias` > `alias` > original tool name.
@@ -245,11 +245,11 @@ Unlike the dashboard, the API does not automatically create a DNS record for you
 
 The `auth_type` field accepts the following values:
 
-| Value             | Description                                                                                                                                          |
-| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `oauth`           | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
-| `bearer`          | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`.                                                   |
-| `unauthenticated` | The server does not require authentication.                                                                                                          |
+| Value | Description |
+| ----- | ----------- |
+| `oauth` | The server requires OAuth authentication. After creating the server, you will need to authenticate via the dashboard to establish admin credentials. |
+| `bearer` | The server uses a static bearer token for authentication. Provide the token in `auth_credentials`. |
+| `unauthenticated` | The server does not require authentication. |
 
 ### Force sync an MCP server
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
index 8b12f3259058db0..b342006708c137a 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token.mdx
@@ -57,18 +57,18 @@ The payload contains the actual claim and user information to pass to the applic
 }
 ```
 
-| Field          | Description                                                                                                                                                                                                                                                                                               |
-| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                |
-| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                           |
-| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                                       |
-| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                                         |
-| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                                     |
-| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                                     |
-| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                                 |
-| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                            |
+| Field          | Description                                                                                                                                                                                                                                                                                     |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| aud            | [Application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application.                                                                                                                                                    |
+| email          | The email address of the authenticated user, verified by the identity provider.                                                                                                                                                                                                                 |
+| exp            | The expiration timestamp for the token (Unix time).                                                                                                                                                                                                                                             |
+| iat            | The issuance timestamp for the token (Unix time).                                                                                                                                                                                                                                               |
+| nbf            | The not-before timestamp for the token (Unix time), used to check if the token was received before it should be used.                                                                                                                                                                           |
+| iss            | The Cloudflare Access domain URL for the application.                                                                                                                                                                                                                                           |
+| type           | The type of Access token (`app` for application token or `org` for global session token).                                                                                                                                                                                                       |
+| identity_nonce | A cache key used to get the [user's identity](#user-identity).                                                                                                                                                                                                                                  |
 | sub            | The ID of the user. This value is unique to an email address per account. The user would get a different `sub` if they are [removed](/cloudflare-one/team-and-resources/users/seat-management/#remove-a-user) and re-added to your Zero Trust organization, or if they log into a different organization. |
-| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                            |
+| country        | The country where the user authenticated from.                                                                                                                                                                                                                                                  |
 
 #### Custom SAML attributes and OIDC claims
 
@@ -86,26 +86,26 @@ curl -H 'cookie: CF_Authorization=<user-token>' https://<your-team-name>.cloudfl
 
 Access will return a JSON structure containing the following data:
 
-| Field                | Description                                                                                |
-| -------------------- | ------------------------------------------------------------------------------------------ |
-| email                | The email address of the user.                                                             |
-| idp                  | Data from your identity provider.                                                          |
-| geo                  | The country where the user authenticated from.                                             |
-| user_uuid            | The ID of the user.                                                                        |
-| devicePosture        | The device posture attributes.                                                             |
-| account_id           | The account ID for your organization.                                                      |
-| iat                  | The timestamp indicating when the user logged in.                                          |
-| ip                   | The IP address of the user.                                                                |
-| auth_status          | The status if authenticating with mTLS.                                                    |
-| common_name          | The common name on the mTLS client certificate.                                            |
-| service_token_id     | The Client ID of the service token used for authentication.                                |
-| service_token_status | True if authentication was through a service token instead of an IdP.                      |
-| is_warp              | True if the user enabled WARP.                                                             |
-| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team. |
-| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team.      |
-| device_id            | The ID of the device used for authentication.                                              |
-| version              | The version of the `get-identity` object.                                                  |
-| device_sessions      | A list of all sessions initiated by the user.                                              |
+| Field                | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| email                | The email address of the user.                                              |
+| idp                  | Data from your identity provider.                                           |
+| geo                  | The country where the user authenticated from.                              |
+| user_uuid            | The ID of the user.                                                         |
+| devicePosture        | The device posture attributes.                                              |
+| account_id           | The account ID for your organization.                                       |
+| iat                  | The timestamp indicating when the user logged in.                           |
+| ip                   | The IP address of the user.                                                 |
+| auth_status          | The status if authenticating with mTLS.                                     |
+| common_name          | The common name on the mTLS client certificate.                             |
+| service_token_id     | The Client ID of the service token used for authentication.                 |
+| service_token_status | True if authentication was through a service token instead of an IdP.       |
+| is_warp              | True if the user enabled WARP.                                              |
+| is_gateway           | True if the user enabled the Cloudflare One Client and authenticated to a Zero Trust team.       |
+| gateway_account_id   | An ID generated by the Cloudflare One Client when authenticated to a Zero Trust team. |
+| device_id            | The ID of the device used for authentication.                               |
+| version              | The version of the `get-identity` object.                                   |
+| device_sessions      | A list of all sessions initiated by the user.                               |
 
 ### Service token authentication
 
@@ -121,15 +121,15 @@ Access will return a JSON structure containing the following data:
 }
 ```
 
-| Field       | Description                                                                                                                                                                    |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| type        | The type of Access token (`app` for application token or `org` for global session token).                                                                                      |
+| Field       | Description                                                                                                                                      |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| type        | The type of Access token (`app` for application token or `org` for global session token).                                                        |
 | aud         | The [application audience (AUD) tag](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/#get-your-aud-tag) of the Access application. |
-| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                                               |
-| iss         | The Cloudflare Access domain URL for the application.                                                                                                                          |
-| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                                                    |
-| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                                                 |
-| sub         | Contains an empty string when authentication was through a service token.                                                                                                      |
+| exp         | The expiration timestamp of the JWT (Unix time).                                                                                                 |
+| iss         | The Cloudflare Access domain URL for the application.                                                                                            |
+| common_name | The Client ID of the service token (`CF-Access-Client-Id`).                                                                                      |
+| iat         | The issuance timestamp of the JWT (Unix time).                                                                                                   |
+| sub         | Contains an empty string when authentication was through a service token.                                                                        |
 
 ## Signature
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
index 3917b42fff99c6f..6ac256251bea1e9 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx
@@ -197,10 +197,7 @@ export default {
 		const newRequest = new Request(url.toString(), request);
 
 		newRequest.headers.set("cf-access-client-id", env.CF_ACCESS_CLIENT_ID);
-		newRequest.headers.set(
-			"cf-access-client-secret",
-			env.CF_ACCESS_CLIENT_SECRET,
-		);
+		newRequest.headers.set("cf-access-client-secret", env.CF_ACCESS_CLIENT_SECRET);
 		try {
 			const response = await fetch(newRequest);
 
@@ -230,7 +227,7 @@ npx wrangler deploy
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
+	<DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select your newly created Worker.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
index 03576d37f7ff815..5b1182c9666a6e2 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/managed-oauth.mdx
@@ -188,13 +188,13 @@ The authorization flow proceeds as follows:
 
 Both managed OAuth and [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) allow non-browser clients to authenticate with Access-protected applications, but they serve different use cases:
 
-|                           | Managed OAuth                                                                    | Service tokens                                                                                  |
-| ------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| **Authentication model**  | User-based — the end user logs in through their identity provider                | Machine-based — a shared secret authenticates the service itself                                |
-| **Best for**              | Interactive CLI tools, AI agents, SDKs where a human initiates the request       | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication             |
-| **User identity**         | Access knows which user made the request                                         | No user identity — requests are attributed to the service token                                 |
-| **Policy enforcement**    | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
-| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials  | Requires distributing and rotating Client ID and Client Secret                                  |
+| | Managed OAuth | Service tokens |
+| --- | --- | --- |
+| **Authentication model** | User-based — the end user logs in through their identity provider | Machine-based — a shared secret authenticates the service itself |
+| **Best for** | Interactive CLI tools, AI agents, SDKs where a human initiates the request | Fully automated systems, cron jobs, CI/CD pipelines, server-to-server communication |
+| **User identity** | Access knows which user made the request | No user identity — requests are attributed to the service token |
+| **Policy enforcement** | Can use identity-based policies (for example, require specific groups or emails) | Requires a [Service Auth](/cloudflare-one/access-controls/policies/#service-auth) policy action |
+| **Credential management** | No shared secrets to distribute — users authenticate with their own credentials | Requires distributing and rotating Client ID and Client Secret |
 
 Use managed OAuth when you want non-browser clients to authenticate users the same way a browser would — the user logs in once, and the client receives an OAuth token to make requests on their behalf.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
index cadc87d1fda6ab5..52fef67da2246a1 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx
@@ -59,15 +59,12 @@ Some SaaS applications provide the Redirect URL after you [configure the SSO pro
 
 11. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-12. <Render
-    	file="access/access-choose-idps"
-    	product="cloudflare-one"
-    	params={{ appType: "saas" }}
-    />
+12. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "saas" }}/>
 
 13. (Optional) Go to **Additional settings** to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
-    - <Render file="access/access-block-page" product="cloudflare-one" />
+
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/). If **Show application in App Launcher** is enabled, then you must enter an **App Launcher URL**. The App Launcher URL is provided by the SaaS application. It may match the base URL portion of **Redirect URL** (`https://<INSTANCE-NAME>.example-app.com`) but could be a different value.
+	- <Render file="access/access-block-page" product="cloudflare-one" />
 
 14. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
index cee76077b2de270..c554be332b64448 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-  - SSO
+- SSO
 ---
 
 This guide covers how to configure [Grafana Cloud](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/authorization/#configure-oauth-20-with-generic-oauth) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
index c343d9ad68ce913..b7a904dc94c5681 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx
@@ -8,7 +8,7 @@ reviewed: 2024-07-18
 sidebar:
   order: 14
 tags:
-  - SSO
+- SSO
 ---
 
 This guide covers how to configure [Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) as an OIDC application in Cloudflare One.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
index 01dc8bf2c1ccd20..3118fcac0cec9c2 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/index.mdx
@@ -6,9 +6,10 @@ products:
 title: SaaS applications
 sidebar:
   order: 1
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare Access allows you to add an additional authentication layer to your SaaS applications. When you integrate a SaaS application with Access, users log in to the application with Cloudflare as the Single Sign-On provider. The user is then redirected to the configured identity providers for that application and are only granted access if they pass your Access policies.
 
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
index 2cfa346e15fc6c3..ae83f5143d310dc 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx
@@ -7,8 +7,8 @@ title: Browser-rendered terminal
 sidebar:
   order: 3
 tags:
-  - SSH
-  - RDP
+- SSH
+- RDP
 ---
 
 import { Render } from "~/components";
@@ -31,10 +31,7 @@ To turn on browser rendering for an SSH or VNC application:
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/). Select **Configure**.
 3. Turn on **Allow access through browser-based RDP, SSH, or VNC sessions**, then select _SSH_ or _VNC_.
-   <Render
-   	file="access/self-hosted-app/browser-rendering-policies"
-   	product="cloudflare-one"
-   />
+	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
 4. Select **Save**.
 
 When users authenticate and visit the URL of the application, Cloudflare will render a terminal in their browser.
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
index 203505a89c9fa0e..e0badb2c31fe6c0 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp.mdx
@@ -7,8 +7,8 @@ title: Arbitrary TCP
 sidebar:
   order: 11
 tags:
-  - TCP
-  - SSH
+- TCP
+- SSH
 ---
 
 Cloudflare Access provides a mechanism for end users to authenticate with their single sign-on (SSO) provider and connect to resources over arbitrary TCP without being on a virtual private network (VPN).
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
index 242e714857c5c7a..0e09be8ca535069 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx
@@ -7,7 +7,7 @@ title: Enable automatic cloudflared authentication
 sidebar:
   order: 2
 tags:
-  - Authentication
+- Authentication
 ---
 
 When users connect to an Access application through `cloudflared`, the browser prompts them to allow access by displaying this page:
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
index 7b753f951aa5916..2f0c700b0197311 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
   label: Private network applications (legacy)
 tags:
-  - Private networks
+- Private networks
 ---
 
 :::caution
@@ -35,6 +35,7 @@ Existing **Private Network** applications continue to function and can still be
 7. Select **Next**. You will see two auto-generated Gateway Network policies: one that allows access to the destination IP and another that blocks access.
 
 8. Modify the policies to include additional identity-based conditions. For example:
+
    - **Policy 1**
 
      | Selector       | Operator      | Value            | Logic | Action |
@@ -52,4 +53,4 @@ Existing **Private Network** applications continue to function and can still be
 
 9. Select **Add application**.
 
-Your application will appear on the **Applications** page.
+Your application will appear on the **Applications** page.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
index 4b7341a9ec0afcb..00a20e37e19d6cb 100644
--- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app.mdx
@@ -11,7 +11,7 @@ sidebar:
   label: Add a self-hosted private application
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip, } from "~/components";
 
 You can configure a self-hosted Access application to manage access to specific IPs or hostnames on your private network.
 
@@ -28,59 +28,54 @@ This feature replaces the legacy [private network app type](/cloudflare-one/acce
 
 ## Add your application to Access
 
-1.  In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
-2.  Select **Create new application**.
+2. Select **Create new application**.
 
-3.  Select **Self-hosted and private**.
+3. Select **Self-hosted and private**.
 
-4.  To add an application using its private IP: 1. Select **Add private IP**. 2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`). 3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+4.  To add an application using its private IP:
+		1. Select **Add private IP**.
+		2. In **IP address**, enter the private IP or CIDR range that represents the application (for example, `10.0.0.1` or `172.16.0.0/12`).
+		3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-        	Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
+			Comma-separated lists of ports (such as `80, 443`) are not supported. To add multiple ports for a specific IP, you can select **Add private IP** and repeat the IP address with the other port. Alternatively, create a new Access application for the other port.
 
-5.  To add an application using its private hostname:
-    1. Select **Add private hostname**.
-    2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
-    3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
+5. To add an application using its private hostname:
+	1. Select **Add private hostname**.
+	2. In **Hostname**, enter the private hostname of the application (for example, `wiki.internal.local`). You can use [wildcards](/cloudflare-one/access-controls/policies/app-paths/) with private hostnames to protect multiple parts of an application that share a root path.
+	3. In **Port**, enter a single port or a port range used by your application (for example, `22` or `8000-8099`).
 
-    :::note
-    - **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
-    - **Non-HTTPS applications**: Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
+	:::note
+	- **HTTPS applications**: Private hostnames explicitly set to port `443` (not including port ranges such as `441-444`) must have a valid Server Name Indicator (SNI).
+	- **Non-HTTPS applications**:  Private hostnames on non-`443` ports do not require a valid SNI value will be assigned an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip>  in the CGNAT space. Ensure that the following IP addresses are not blocked by any firewalls or excluded from Gateway traffic:
 
-      <Render
-      	file="gateway/egress-selector-cgnat-ips"
-      	product="cloudflare-one"
-      />
+		<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one"/>
 
-      For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
+		For more details on private hostname routing, refer to [Connect a private hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/#prerequisites)
 
 6.  <Render file="access/add-access-policies" product="cloudflare-one" />
-7.  <Render
-    	file="access/access-choose-idps"
-    	product="cloudflare-one"
-    	params={{ appType: "private" }}
-    />
+7.  <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "private" }}/>
 
-8.  <Render file="access/configure-independent-mfa" product="cloudflare-one" />
+8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
-9.  <Render file="access/session-duration" product="cloudflare-one" />
+9. <Render file="access/session-duration" product="cloudflare-one" />
 
-    If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
+   If the application is non-HTTPS or you do not have TLS decryption turned on, the session is tracked by the Cloudflare One Client per application.
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-    - **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
 
-      :::note
-      Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
-      :::
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	- **Allow clientless access**: Allow users to access this private hostname or IP without the Cloudflare One Client. Users who pass your Access policies will see a tile in their App Launcher which points to a prefixed URL such as `https://<your-teamname>.cloudflareaccess.com/browser/https://wiki.internal.local/`. The link will route traffic to the application through [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/). This setting is useful for users on unmanaged devices or contractors who cannot install a device client.
+
+		:::note
+		Ensure your [remote browser permissions](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) allow users of this application to open Clientless Web Isolation links.
+		:::
+
+	- <Render file="access/access-block-page" product="cloudflare-one" />
+	- The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
+		<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
 
-    - <Render file="access/access-block-page" product="cloudflare-one" />
-    - The following settings only apply to private hostnames and require [Gateway TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/):
-      <Render
-      	file="access/self-hosted-app/advanced-settings"
-      	product="cloudflare-one"
-      />
 
 11. Select **Create**.
 
@@ -118,11 +113,8 @@ An Access application defined by a private hostname takes precedence over an Acc
 
 ### Browser Isolation is not compatible with apps on non-`443` ports
 
-<Render
-	file="access/self-hosted-app/browser-isolation-non-443"
-	product="cloudflare-one"
-/>
+<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
 
 ### Google Chrome restricts access to private hostnames
 
-<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one" />
+<Render file="gateway/egress-selector-chrome-issue" product="cloudflare-one"/>
diff --git a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
index 2de16fa32411bf7..3dfe9164a038ef3 100644
--- a/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/event-subscriptions.mdx
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Available Access events
 
-<Render file="event-subscriptions/access-events" product="queues" />
+<Render file="event-subscriptions/access-events" product="queues" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
index 899ed27993f86f3..1c0b4d46c3a4704 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/app-paths.mdx
@@ -6,6 +6,7 @@ products:
 title: Application paths
 sidebar:
   order: 5
+
 ---
 
 Application paths define the URLs protected by an Access policy. When adding a self-hosted application to Access, you can choose to protect the entire website by entering its apex domain, or alternatively, protect specific subdomains and paths.
@@ -26,9 +27,9 @@ When you create an application for a specific subdomain or path, you can use ast
 
 A wildcard in the **Subdomain** field only matches that specific subdomain level. It does not cover the apex domain or multiple levels of the subdomain. If you want to cover multiple subdomain levels, you can use multiple wildcards.
 
-| Application     | Covers                                       | Does not cover                            |
-| --------------- | -------------------------------------------- | ----------------------------------------- |
-| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com` |
+| Application     | Covers                                       | Does not cover |
+| --------------- | -------------------------------------------- | -------------- |
+| `*.example.com` | `alpha.example.com` <br/> `beta.example.com` | `example.com` <br/> `foo.bar.example.com`  |
 
 #### Match all paths of an apex domain
 
@@ -42,9 +43,9 @@ To protect an apex domain and all of the paths under it, leave the **Path** fiel
 
 Using a wildcard in the **Subdomain** field does not cover the parent subdomain nor the apex domain.
 
-| Application          | Covers                                                 | Does not cover                         |
-| -------------------- | ------------------------------------------------------ | -------------------------------------- |
-| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com` <br/> `example.com` |
+| Application          | Covers                                                 | Does not cover                          |
+| -------------------- | ------------------------------------------------------ | --------------------------------------- |
+| `*.test.example.com` | `alpha.test.example.com` <br/> `beta.test.example.com` | `test.example.com`  <br/> `example.com` |
 
 #### Partially match subdomains
 
@@ -72,8 +73,8 @@ Using a wildcard in the middle of the **Path** field covers multiple segments of
 
 ### Limitations
 
-- At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
-- At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
+* At most one wildcard in between each dot in the **Subdomain**. For example, `foo*bar*baz.example.com` is not allowed.
+* At most one wildcard in between each slash in the **Path**. For example, `example.com/foo*bar*baz` is not allowed.
 
 ## Subdomain setups
 
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
index e08ee885d64e235..c8ec944860e8d4b 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/index.mdx
@@ -145,29 +145,29 @@ When you add a rule to your Cloudflare Access policy, you will be asked to speci
 
 Non-identity attributes are polled continuously, meaning they are evaluated with each new HTTP request for changes during the [user session](/cloudflare-one/access-controls/access-settings/session-management/). If you have configured [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/), you can force a user to re-attest all attributes with Access whenever you revoke the user in the IdP or update their IdP group membership.
 
-| Selector                  | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
-| Emails                    | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Emails ending in          | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
-| External Evaluation       | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
-| IP ranges                 | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
-| Country                   | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
-| Everyone                  | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
-| Common Name               | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
-| Valid Certificate         | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Service Token             | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
-| Any Access Service Token  | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
-| User Risk Score           | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
-| Linked App Token          | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                      | ✅               | ✅                               | ❌                       |
-| Login Methods             | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
-| Authentication Method     | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
-| Identity provider group   | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
-| SAML Group                | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
-| OIDC Claim                | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
-| Device posture            | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
-| Warp                      | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
-| Gateway                   | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
-| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                               | ✅               | ❌                               | ✅                       |
+| Selector                 | Description                                                                                                                                                                                                                                                                                                                              | Checked at login | Checked continuously<sup>1</sup> | Identity-based selector? |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | ------------------------ |
+| Emails                   | `you@company.com`                                                                                                                                                                                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Emails ending in         | `@company.com`                                                                                                                                                                                                                                                                                                                           | ✅               | ❌                               | ✅                       |
+| External Evaluation      | Allows or denies access based on [custom logic](/cloudflare-one/access-controls/policies/external-evaluation/) in an external API.                                                                                                                                                                                                       | ✅               | ❌                               | ✅                       |
+| IP ranges                | `192.168.100.1/24` (supports IPv4/IPv6 addresses and CIDR ranges)                                                                                                                                                                                                                                                                        | ✅               | ✅                               | ❌                       |
+| Country                  | Uses the IP address to determine country.                                                                                                                                                                                                                                                                                                | ✅               | ✅                               | ❌                       |
+| Everyone                 | Allows, denies, or bypasses access to everyone.                                                                                                                                                                                                                                                                                          | ✅               | ❌                               | ❌                       |
+| Common Name              | The request will need to present a valid certificate with an expected common name.                                                                                                                                                                                                                                                       | ✅               | ✅                               | ❌                       |
+| Valid Certificate        | The request will need to present any valid client certificate.                                                                                                                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Service Token            | The request will need to present the correct service token headers configured for the specific application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                                           | ✅               | ✅                               | ❌                       |
+| Any Access Service Token | The request will need to present the headers for any [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) created for this account. Requires the [Service Auth](#service-auth) action.                                                                                                                   | ✅               | ✅                               | ❌                       |
+| User Risk Score          | The user's current [risk score](/cloudflare-one/team-and-resources/users/risk-score/) (Low, Medium, or High). Acts as a threshold — users with a score at or below the specified level pass the check. This selector only displays for Enterprise plans.                                                                                 | ✅               | ✅                               | ✅                       |
+| Linked App Token         | Checks for a valid [OAuth access token](/cloudflare-one/access-controls/applications/linked-app-token/) issued to a specific Access application. Requires the [Service Auth](#service-auth) action.                                                                                                                                                   | ✅               | ✅                               | ❌                       |
+| Login Methods            | Checks the identity provider used at the time of login.                                                                                                                                                                                                                                                                                  | ✅               | ❌                               | ✅                       |
+| Authentication Method    | Checks the [multi-factor authentication](/cloudflare-one/access-controls/policies/mfa-requirements/#identity-provider-based-mfa) method used by the user, if supported by the identity provider. To enforce MFA independently of your IdP, refer to [independent MFA](/cloudflare-one/access-controls/access-settings/independent-mfa/). | ✅               | ❌                               | ✅                       |
+| Identity provider group  | Checks the user groups configured with your identity provider (IdP). This selector only displays if you use Microsoft Entra ID, GitHub, Google, Okta, or an IdP that provisions groups with [SCIM](/cloudflare-one/team-and-resources/users/scim/).                                                                                      | ✅               | ❌                               | ✅                       |
+| SAML Group               | Checks a SAML attribute name / value pair. This selector only displays if you use a [generic SAML](/cloudflare-one/integrations/identity-providers/generic-saml/) identity provider.                                                                                                                                                     | ✅               | ❌                               | ✅                       |
+| OIDC Claim               | Checks an OIDC claim name / value pair. This selector only displays if you use a [generic OIDC](/cloudflare-one/integrations/identity-providers/generic-oidc/) identity provider.                                                                                                                                                        | ✅               | ❌                               | ✅                       |
+| Device posture           | Checks device posture signals from the Cloudflare One Client or a third-party service provider. This selector only displays after you create a [device posture check](/cloudflare-one/reusable-components/posture-checks/).                                                                                                              | ✅               | ✅                               | ❌                       |
+| Warp                     | Checks that the device is connected to the Cloudflare One Client, including the consumer version. This selector only displays after you enable the [WARP posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/).                                                                                 | ✅               | ✅                               | ❌                       |
+| Gateway                  | Checks that the device is connected to your Zero Trust instance through the Cloudflare One Client. This selector only displays after you enable the [Gateway posture check](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/).                                                                          | ✅               | ✅                               | ❌                       |
+| Cloudflare Account Member | Checks that the user is a member of a specific Cloudflare account. If no account ID is specified, defaults to the current account. This selector only displays if you use the [Cloudflare](/cloudflare-one/integrations/identity-providers/cloudflare/) identity provider.                                                                | ✅               | ❌                               | ✅                       |
 
 <sup>1</sup> For SaaS applications, Access can only enforce policies at the time
 of initial sign on and when reissuing the SaaS session. Once the user has
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
index 11eeaa22045b223..7213c910db20077 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/policy-management.mdx
@@ -54,7 +54,7 @@ To delete a reusable Access policy:
 
 ## Test your policies
 
-You can test your Access policies against all existing user identities in your Zero Trust organization. For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
+You can test your Access policies against all existing user identities in your Zero Trust organization.  For the policy tester to work, users must have logged into the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) or any other Access application at some point in time.
 
 Cloudflare will use the most recent device that was authenticated with Access to test your policies.
 
@@ -76,22 +76,25 @@ You can test your Access application policies against your user population befor
 
 To test if users have access to an application:
 
-1.  In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
-2.  Locate the application you want to test and select **Configure**.
-3.  Go to **Policies** > **Policy tester**.
-4.  To test all active users in your organization, select **Test policies**.
+1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
+2. Locate the application you want to test and select **Configure**.
+3. Go to **Policies** > **Policy tester**.
+4. To test all active users in your organization, select **Test policies**.
 
-        The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
+		The policy tester reports the percentage of users who are allowed or denied access to this application based on all configured policies. You can expand the test results to view a list of allowed or blocked users.
 
-5.  To perform a detailed test on a single user:
+5. To perform a detailed test on a single user:
 
-    a. If you made any changes to your policies, first save the application.
+	a. If you made any changes to your policies, first save the application.
 
-    b. Select **testing a single user**.
+	b. Select **testing a single user**.
 
-    c. Enter their email address and select **Test policies**.
+	c. Enter their email address and select **Test policies**.
 
-    The single user test results will show: - Whether the user is allowed or denied access to this application based on all configured policies. - The user's identity from their most recent Access login attempt. - Whether the user matches individual Allow, Block, or Bypass policies.
+	The single user test results will show:
+		- Whether the user is allowed or denied access to this application based on all configured policies.
+		- The user's identity from their most recent Access login attempt.
+		- Whether the user matches individual Allow, Block, or Bypass policies.
 
 ## Legacy policies
 
@@ -111,8 +114,8 @@ To migrate legacy policies to reusable policies:
 You can use the API to convert a legacy policy into a reusable policy. To convert a legacy policy, make a `PUT` request with an empty request body:
 
 <APIRequest
-	path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
-	method="PUT"
+  path="/accounts/{account_id}/access/apps/{app_id}/policies/{policy_id}/make_reusable"
+  method="PUT"
 />
 
 The policy is now removed from the applications endpoint (`/access/apps/$APP_ID/policies`) and managed using the [reusable policies endpoints](/api/resources/zero_trust/subresources/access/subresources/policies/)(`/access/policies/$POLICY_ID`).
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
index 3759f0ffb3db29b..ef3c106a4c83c56 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Require purpose justification after login
+
 ---
 
 Cloudflare Access allows security and IT teams to present users with a purpose justification screen directly after they log in to an Access application. This allows organizations to audit not only for who is accessing their resources, but also for why they are requesting access.
diff --git a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
index a3fccad67a5f5e6..3c320499e0997ac 100644
--- a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx
@@ -7,7 +7,7 @@ title: Temporary authentication
 sidebar:
   order: 11
 tags:
-  - Authentication
+- Authentication
 ---
 
 With Cloudflare Access, you can require that users obtain approval before they can access a specific self-hosted application or SaaS application. The administrator will receive an email notification to approve or deny the request. Unlike a typical Allow policy, the user will have to request access at the end of each session. This allows you to define the users who should have persistent access and those who must request temporary access.
@@ -20,9 +20,9 @@ With Cloudflare Access, you can require that users obtain approval before they c
 4. Under **Additional settings**, turn on [**Purpose justification**](/cloudflare-one/access-controls/policies/require-purpose-justification/).
 5. Turn on **Temporary authentication**.
 6. Enter the **Email addresses of the approvers**.
-   :::note
-   Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
-   :::
+	:::note
+	Your approvers must be authenticated by Access. If they do not have an active session, Access will verify their identity against your [App Launcher Access policy](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	:::
 7. Save the policy.
 
 Temporary authentication is now enabled for users who match this policy. You can optionally add a second **Allow** policy for users who should have persistent access. Be sure the policy order is set to allow persistent users through.
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
index a9f7713dccc5a33..7ff124cd8eb6d90 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/index.mdx
@@ -13,3 +13,4 @@ sidebar:
 import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
+
diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
index 28d4336eca249b9..64603599f027224 100644
--- a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
+++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx
@@ -7,8 +7,8 @@ title: Service tokens
 sidebar:
   order: 6
 tags:
-  - JSON web token (JWT)
-  - Authentication
+- JSON web token (JWT)
+- Authentication
 ---
 
 import {
diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index 2b66eb6b6433481..e29b38b2b415178 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -62,19 +62,19 @@ This page lists the default account limits for rules, applications, fields, and
 
 ## Cloudflare Tunnel
 
-| Feature                                            | Limit                               |
-| -------------------------------------------------- | ----------------------------------- |
-| `cloudflared` tunnels per account                  | 1,000                               |
+| Feature                                            | Limit |
+| -------------------------------------------------- | ----- |
+| `cloudflared` tunnels per account                  | 1,000 |
 | Routes (CIDR routes + Hostname routes) per account | 1,000 (shared with Cloudflare Mesh) |
-| Active `cloudflared` replicas per tunnel           | 25                                  |
-| Virtual networks per account                       | 1,000                               |
+| Active `cloudflared` replicas per tunnel           | 25    |
+| Virtual networks per account                       | 1,000 |
 
 ## Cloudflare Mesh
 
-| Feature                          | Limit                                 |
-| -------------------------------- | ------------------------------------- |
-| Mesh nodes per account           | 50                                    |
-| Routes (CIDR routes) per account | 1,000 (shared with Cloudflare Tunnel) |
+| Feature                                            | Limit |
+| -------------------------------------------------- | ----- |
+| Mesh nodes per account                             | 50    |
+| Routes (CIDR routes) per account                   | 1,000 (shared with Cloudflare Tunnel) |
 
 ## Digital Experience Monitoring (DEX)
 
@@ -106,7 +106,6 @@ This page lists the default account limits for rules, applications, fields, and
 | Gateway API policy expression | 140,000         |
 
 ## Cloudflare One Client
-
 | Feature                                                                    | Limit  |
 | -------------------------------------------------------------------------- | ------ |
 | Characters per device profile expression                                   | 10,000 |
diff --git a/src/content/docs/cloudflare-one/changelog/tunnel.mdx b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
index 5c1f6285b4348a4..7d4677d85c9b423 100644
--- a/src/content/docs/cloudflare-one/changelog/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/changelog/tunnel.mdx
@@ -13,7 +13,10 @@ import { ProductChangelog, Render } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
+<ProductChangelog
+	product="tunnel"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
 
 ## 2024-10-17
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
index 508f0cb7179a5a0..64994724c683773 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/data-classification/index.mdx
@@ -29,13 +29,13 @@ Templates provide Cloudflare-managed starting points for sensitivity schemas and
 
 Data Classification works alongside detection entries and DLP profiles.
 
-| Component         | What it does                                                                                                            |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| Component | What it does |
+| --- | --- |
 | Detection entries | Detect specific content such as patterns, datasets, document fingerprints, AI prompt topics, and predefined detections. |
-| Labels            | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content.        |
-| Templates         | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups.                                 |
-| Data classes      | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags.      |
-| DLP profiles      | Apply detection and classification logic to DLP scanning and enforcement workflows.                                     |
+| Labels | Define sensitivity schemas, sensitivity levels, data tag groups, and data tags used to describe matched content. |
+| Templates | Provide Cloudflare-managed starting points for sensitivity schemas and data tag groups. |
+| Data classes | Build reusable classification rules from detection entries, other data classes, sensitivity levels, and data tags. |
+| DLP profiles | Apply detection and classification logic to DLP scanning and enforcement workflows. |
 
 In general, detection entries help identify sensitive content. Data Classification helps organize and label that content so administrators can identify its severity, understand where it exists, and apply it consistently. DLP profiles then apply that logic to scanning and enforcement workflows.
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
index 2e931248090f21d..76a268ab8c5fbda 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries.mdx
@@ -182,16 +182,16 @@ Your new document entry will replace the original document entry. If your file u
 
 DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
 
-| Detection entry                       | Description                                                                                       |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| Content: PII                          | Prompt contains personal information such as names, SSNs, or email addresses.                     |
-| Content: Credentials and Secrets      | Prompt contains API keys, passwords, or other sensitive credentials.                              |
-| Content: Source Code                  | Prompt contains actual source code, code snippets, or proprietary algorithms.                     |
-| Content: Customer Data                | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
-| Content: Financial Information        | Prompt contains financial numbers or confidential business data.                                  |
-| Intent: PII                           | Prompt requests specific personal information about individuals.                                  |
-| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities.                      |
-| Intent: Jailbreak                     | Prompt attempts to circumvent AI security policies.                                               |
+| Detection entry | Description |
+| --- | --- |
+| Content: PII | Prompt contains personal information such as names, SSNs, or email addresses. |
+| Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials. |
+| Content: Source Code | Prompt contains actual source code, code snippets, or proprietary algorithms. |
+| Content: Customer Data | Prompt contains customer names, projects, business activities, or confidential customer contexts. |
+| Content: Financial Information | Prompt contains financial numbers or confidential business data. |
+| Intent: PII | Prompt requests specific personal information about individuals. |
+| Intent: Code Abuse and Malicious Code | Prompt requests malicious code for attacks, exploits, or harmful activities. |
+| Intent: Jailbreak | Prompt attempts to circumvent AI security policies. |
 
 Each detection entry is categorized as either **Content** or **Intent**:
 
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
index e948a705b784d4a..ccd073189323e6d 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries/predefined-detection-entries.mdx
@@ -14,151 +14,151 @@ Predefined detection entries are Cloudflare-managed detections for specific type
 
 You can add any predefined detection entry directly to a custom [DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/#build-a-custom-profile) or [data class](/cloudflare-one/data-loss-prevention/data-classification/build-a-data-class/). Use the following reference to review all predefined detection entries currently supported by Cloudflare DLP.
 
-| Detection entry                                      | Description                                                                                                                                                                  |
-| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| AI Prompt Content: Credentials and Secrets           | Prompt contains API keys, passwords, or other sensitive credentials                                                                                                          |
-| AI Prompt Content: Customer data                     | Prompt contains customer names, projects, business activities, or confidential customer contexts                                                                             |
-| AI Prompt Content: Financial Information             | Prompt contains actual financial numbers or confidential business data                                                                                                       |
-| AI Prompt Content: PII                               | Prompt contains personal information (names, SSNs, emails, etc.)                                                                                                             |
-| AI Prompt Content: Source code                       | Prompt contains source code, code snippets, or proprietary algorithms                                                                                                        |
-| AI Prompt Intent: Code Abuse and Malicious Code      | Malicious code or attempts to exploit vulnerabilities                                                                                                                        |
-| AI Prompt Intent: Jailbreak                          | Prompt attempts to circumvent security policies                                                                                                                              |
-| AI Prompt Intent: PII                                | Prompt requests specific personal information about individuals                                                                                                              |
-| Amazon AWS Access Key ID                             | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`.                                                                                                             |
-| Amazon AWS Secret Access Key                         | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`.                                                                                           |
-| American Express Card Number                         | Detects American Express credit card numbers such as "378282246310005".                                                                                                      |
-| American Express Text                                | Detects mentions of the American Express brand name such as "American Express".                                                                                              |
-| AU Passport Number                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
-| Australia Address                                    | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000".                                                                        |
-| Australia Business (ABN)                             | Detects Australian Business Numbers (ABN) such as "51 824 753 556".                                                                                                          |
-| Australia Company (ACN)                              | Detects Australian Company Numbers (ACN) such as "001 000 004".                                                                                                              |
-| Australia Medicare                                   | Detects Australian Medicare card numbers such as "2000000006".                                                                                                               |
-| Australia Passport                                   | Detects Australian passport numbers such as "L1234567".                                                                                                                      |
-| Australia Tax File Number                            | Detects Australian Tax File Numbers (TFN) such as "85 655 734".                                                                                                              |
-| Austria SSN (SV-Nummer)                              | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180".                                                                                                  |
-| Austria Tax ID                                       | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789".                                                                                            |
-| Austria VAT (UID)                                    | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678".                                                                                                             |
-| Belgium Tax ID (NN)                                  | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61".                                                                          |
-| Belgium VAT                                          | Detects Belgian VAT numbers such as "BE0000000097".                                                                                                                          |
-| Bitcoin Wallet                                       | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2".                                                                                               |
-| Brazil CNPJ                                          | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81".                                                                                   |
-| Brazil CPF (Tax ID)                                  | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25".                                                                                       |
-| Bulgaria Uniform Civil (EGN)                         | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007".                                                                                                          |
-| C                                                    | Detects C source code.                                                                                                                                                       |
-| C#                                                   | Detects C# source code.                                                                                                                                                      |
-| C++                                                  | Detects C++ source code.                                                                                                                                                     |
-| Canada Bank Account Number                           | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567".                                                                         |
-| Canada Health Number                                 | Detects Canadian provincial health card numbers such as "1234-567-897".                                                                                                      |
-| Canada Passport                                      | Detects Canadian passport numbers such as "AB123456".                                                                                                                        |
-| Canada PHIN (Manitoba)                               | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009".                                                                                          |
-| Canada Physical Address                              | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1".                                                                                |
-| Canada Social Insurance Number                       | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474".                                                                                                       |
-| Chile National ID (RUT)                              | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5".                                                                         |
-| China ID Card                                        | Detects Chinese resident identity card numbers such as "11010519491231002X".                                                                                                 |
-| Cloudflare Account Owned API Token                   | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`.                                                                                        |
-| Cloudflare User API Key                              | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`.                                                                                                               |
-| Cloudflare User API Token                            | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`.                                                                                                          |
-| Croatia Personal ID (OIB)                            | Detects Croatian personal identification numbers (OIB) such as "10000000005".                                                                                                |
-| Denmark Tax (CPR)                                    | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008".                                                                                           |
-| Diners Club Card Number                              | Detects Diners Club credit card numbers such as "30121690374838".                                                                                                            |
-| Discord Webhook                                      | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`.                                                                                        |
-| Email Address                                        | Detects email addresses such as "test@example.com".                                                                                                                          |
-| Ethereum Wallet                                      | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F".                                                                                      |
-| EU Passport                                          | Detects EU member state passport numbers such as "AB1234567".                                                                                                                |
-| FDA Active Ingredients                               | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB".                                                                                                   |
-| FDA Drug Names                                       | Detects FDA-registered drug names such as "ABACAVIR".                                                                                                                        |
-| Finland Tax ID                                       | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y".                                                                                        |
-| France CNI (National ID)                             | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901".                                                                            |
-| France Passport                                      | Detects French passport numbers such as "12AB34567".                                                                                                                         |
-| France Social Security Number                        | Detects French social security (INSEE) numbers such as "145081849670637".                                                                                                    |
-| France Tax ID (SPI)                                  | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123".                                                                                       |
-| France VAT                                           | Detects French VAT numbers such as "FR12000000000".                                                                                                                          |
-| Full Name                                            | Detects personal full names.                                                                                                                                                 |
-| Generic CVV Card Number                              | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033".                                                                          |
-| Germany Tax ID                                       | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005".                                                                               |
-| Germany VAT                                          | Detects German VAT numbers (USt-IdNr) such as "DE100000003".                                                                                                                 |
-| GitHub PAT                                           | Detects GitHub personal access tokens such as a token beginning with `ghp_`.                                                                                                 |
-| Go                                                   | Detects Go source code.                                                                                                                                                      |
-| Google GCP API Key                                   | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`.                                                                                                              |
-| Greece Tax (AFM)                                     | Detects Greek tax identification numbers (AFM) such as "100000003".                                                                                                          |
-| Haskell                                              | Detects Haskell source code.                                                                                                                                                 |
-| Hong Kong Identity Card Number                       | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)".                                                                                                         |
-| Hungary Tax                                          | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008".                                                                                        |
-| IBAN                                                 | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59".                                                                                     |
-| ICD-10 FY2023 Short Description                      | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified".                                                                                          |
-| ICD-11 Short Description                             | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS".                                                                                                    |
-| India Aadhaar                                        | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124".                                                                                             |
-| India GST (GSTIN)                                    | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5".                                                                              |
-| India PAN Card                                       | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F".                                                                                         |
-| India Voter ID                                       | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567".                                                                                                                 |
-| Indonesia Identity Card Number                       | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011".                                                                                               |
-| Indonesia Tax (NPWP)                                 | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345".                                                                                    |
-| Ireland Tax (PPS)                                    | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA".                                                                                                     |
-| Ireland VAT                                          | Detects Ireland VAT numbers such as "IE1234567T".                                                                                                                            |
-| Italy Fiscal Code                                    | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z".                                                                                                    |
-| Japan Address                                        | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001".                                                                                   |
-| Japan My Number (Corp)                               | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002".                                                                                      |
-| Japan My Number (Person)                             | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005".                                                                                      |
-| Japan Names (Kanji)                                  | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎".                                                                            |
-| Japan Passport                                       | Detects Japanese passport numbers such as "TZ1234567".                                                                                                                       |
-| Java                                                 | Detects Java source code.                                                                                                                                                    |
-| JavaScript                                           | Detects JavaScript source code.                                                                                                                                              |
-| Korea Resident Number (RRN)                          | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567".                                                                                           |
-| Lua                                                  | Detects Lua source code.                                                                                                                                                     |
-| Luxembourg Tax                                       | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345".                                                                                      |
-| Luxembourg VAT                                       | Detects Luxembourg VAT numbers such as "LU10000053".                                                                                                                         |
-| Malaysian National Identity Card Number              | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354".                                                                                           |
-| Mastercard Card Number                               | Detects Mastercard credit card numbers such as "5252 5971 4219 4116".                                                                                                        |
-| Mastercard Text                                      | Detects mentions of the Mastercard brand name such as "Mastercard".                                                                                                          |
-| Microsoft Azure Client Secret                        | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`.                                                                                                      |
-| MX CLABE (Bank)                                      | Detects Mexican CLABE bank account numbers such as "032180000118359719".                                                                                                     |
-| MX CURP                                              | Detects Mexican CURP codes such as "GOMC850515HJCRRR05".                                                                                                                     |
-| Netherlands BSN                                      | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782".                                                                                       |
-| Netherlands VAT                                      | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01".                                                                                                             |
-| NPM Token                                            | Detects npm registry access tokens such as a token beginning with `npm_`.                                                                                                    |
-| NZ NHI Number                                        | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016".                                                                                                   |
-| NZ Tax (IRD)                                         | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850".                                                                                        |
-| OpenAI API Key                                       | Detects OpenAI API keys such as a key beginning with `sk-proj-`.                                                                                                             |
-| Peru Tax (RUC)                                       | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001".                                                                                                |
-| Peru Unique ID (DNI)                                 | Detects Peruvian national identity numbers (DNI) such as "12345678".                                                                                                         |
-| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1".                                                                                        |
-| Poland National ID (PESEL)                           | Detects Polish national identification numbers (PESEL) such as "85051500006".                                                                                                |
-| Poland REGON                                         | Detects Polish National Business Registry numbers (REGON) such as "100000008".                                                                                               |
-| Poland Tax (NIP)                                     | Detects Polish tax identification numbers (NIP) such as "123-456-32-18".                                                                                                     |
-| Portugal Tax (NIF)                                   | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002".                                                                            |
-| PyPI Token                                           | Detects PyPI package upload tokens such as a token beginning with `pypi-`.                                                                                                   |
-| Python                                               | Detects Python source code.                                                                                                                                                  |
-| R                                                    | Detects R source code.                                                                                                                                                       |
-| Rust                                                 | Detects Rust source code.                                                                                                                                                    |
-| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H".                                                                                                        |
-| Slack API Token                                      | Detects Slack API tokens such as a token beginning with `xoxb-`.                                                                                                             |
-| Slack Webhook                                        | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`.                                                                                 |
-| Spain DNI/NIF                                        | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z".                                                                                                     |
-| Spain SSN                                            | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890".                                                                                           |
-| Spain Tax (CIF)                                      | Detects Spanish corporate tax identification codes (CIF) such as "A58818501".                                                                                                |
-| SSH Private Key                                      | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----".                                                                                              |
-| Stripe Granular Restricted Key                       | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`.                                                                                        |
-| Stripe Standard Secret Key                           | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`.                                                                                            |
-| Sweden Tax                                           | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874".                                                                                              |
-| SWIFT                                                | Detects SWIFT/BIC business identifier codes such as "PMFAUS66".                                                                                                              |
-| Swift                                                | Detects Swift source code.                                                                                                                                                   |
-| Taiwan National Identification Number                | Detects Taiwan national identification numbers such as "W171845961".                                                                                                         |
-| Thai Identity Card Number                            | Detects Thai national identity card numbers such as "4-8547-01245-28-9".                                                                                                     |
-| UAE Passport                                         | Detects United Arab Emirates passport numbers such as "A1234567".                                                                                                            |
-| Union Pay Card Number                                | Detects UnionPay credit card numbers such as "6250941006528599".                                                                                                             |
-| Union Pay Text                                       | Detects mentions of the UnionPay brand name such as "Union Pay".                                                                                                             |
-| United Kingdom National Insurance Number             | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C".                                                                                                        |
-| United Kingdom NHS Number                            | Detects UK NHS patient identification numbers such as "485-585-0454".                                                                                                        |
-| United States ABA Routing Number                     | Detects US ABA bank routing numbers such as "021000021".                                                                                                                     |
-| United States SSN Numeric Detection                  | Detects US Social Security Numbers such as "123-45-6789".                                                                                                                    |
-| United States SSN Text                               | Detects mentions of "SSN" or "social security" as a keyword, such as "social security".                                                                                      |
-| Unsanitized HAR File                                 | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
-| Uruguay ID (CI)                                      | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8".                                                                                     |
-| US Driver's License Number                           | Detects US driver's license numbers such as "CA License: A1234567".                                                                                                          |
-| US Individual Tax Identification Number (ITIN)       | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678".                                                                                          |
-| US Mailing Address                                   | Detects US mailing addresses such as "100 First St, Chicago, IL 60601".                                                                                                      |
-| US Passport Number                                   | Detects US passport numbers such as "A12345678".                                                                                                                             |
-| US Phone Number                                      | Detects US phone numbers such as "555-555-5555".                                                                                                                             |
-| US Physical Address                                  | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601".                                                                               |
-| Visa Card Number                                     | Detects Visa credit card numbers such as "4111 1111 1111 1111".                                                                                                              |
-| Visa Text                                            | Detects mentions of the Visa brand name such as "Visa".                                                                                                                      |
+| Detection entry | Description |
+| --- | --- |
+| AI Prompt Content: Credentials and Secrets | Prompt contains API keys, passwords, or other sensitive credentials |
+| AI Prompt Content: Customer data | Prompt contains customer names, projects, business activities, or confidential customer contexts |
+| AI Prompt Content: Financial Information | Prompt contains actual financial numbers or confidential business data |
+| AI Prompt Content: PII | Prompt contains personal information (names, SSNs, emails, etc.) |
+| AI Prompt Content: Source code | Prompt contains source code, code snippets, or proprietary algorithms |
+| AI Prompt Intent: Code Abuse and Malicious Code | Malicious code or attempts to exploit vulnerabilities |
+| AI Prompt Intent: Jailbreak | Prompt attempts to circumvent security policies |
+| AI Prompt Intent: PII | Prompt requests specific personal information about individuals |
+| Amazon AWS Access Key ID | Detects Amazon AWS access key IDs such as `AKIA<ACCESS_KEY_ID>`. |
+| Amazon AWS Secret Access Key | Detects potential Amazon AWS secret access keys such as `<AWS_SECRET_ACCESS_KEY>`. |
+| American Express Card Number | Detects American Express credit card numbers such as "378282246310005". |
+| American Express Text | Detects mentions of the American Express brand name such as "American Express". |
+| AU Passport Number | Detects Australian passport numbers such as "L1234567". |
+| Australia Address | Detects Australian street addresses with state and postcode such as "100 George St, Sydney NSW 2000". |
+| Australia Business (ABN) | Detects Australian Business Numbers (ABN) such as "51 824 753 556". |
+| Australia Company (ACN) | Detects Australian Company Numbers (ACN) such as "001 000 004". |
+| Australia Medicare | Detects Australian Medicare card numbers such as "2000000006". |
+| Australia Passport | Detects Australian passport numbers such as "L1234567". |
+| Australia Tax File Number | Detects Australian Tax File Numbers (TFN) such as "85 655 734". |
+| Austria SSN (SV-Nummer) | Detects Austrian social security numbers (SV-Nummer) such as "1018 010180". |
+| Austria Tax ID | Detects Austrian tax identification numbers (Steuernummer) such as "12 345/6789". |
+| Austria VAT (UID) | Detects Austrian VAT numbers (UID-Nummer) such as "ATU12345678". |
+| Belgium Tax ID (NN) | Detects Belgian national numbers (Numéro National / Rijksregisternummer) such as "85.07.30-000.61". |
+| Belgium VAT | Detects Belgian VAT numbers such as "BE0000000097". |
+| Bitcoin Wallet | Detects Bitcoin wallet addresses such as "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2". |
+| Brazil CNPJ | Detects Brazilian corporate taxpayer registry numbers (CNPJ) such as "11.222.333/0001-81". |
+| Brazil CPF (Tax ID) | Detects Brazilian individual taxpayer registry numbers (CPF) such as "529.982.247-25". |
+| Bulgaria Uniform Civil (EGN) | Detects Bulgarian Uniform Civil Numbers (EGN) such as "2405500007". |
+| C | Detects C source code. |
+| C# | Detects C# source code. |
+| C++ | Detects C++ source code. |
+| Canada Bank Account Number | Detects Canadian bank account numbers (institution + transit + account) such as "12345-678 1234567". |
+| Canada Health Number | Detects Canadian provincial health card numbers such as "1234-567-897". |
+| Canada Passport | Detects Canadian passport numbers such as "AB123456". |
+| Canada PHIN (Manitoba) | Detects Manitoba Personal Health Identification Numbers (PHIN) such as "100000009". |
+| Canada Physical Address | Detects Canadian street addresses with postal code such as "100 Main St, Ottawa, ON K1A 0B1". |
+| Canada Social Insurance Number | Detects Canadian Social Insurance Numbers (SIN) such as "114 905 474". |
+| Chile National ID (RUT) | Detects Chilean national identification numbers (RUT / Rol Único Tributario) such as "12.345.678-5". |
+| China ID Card | Detects Chinese resident identity card numbers such as "11010519491231002X". |
+| Cloudflare Account Owned API Token | Detects Cloudflare account-owned API tokens such as `cfat_<ACCOUNT_OWNED_API_TOKEN>`. |
+| Cloudflare User API Key | Detects Cloudflare user API keys such as `cfk_<USER_API_KEY>`. |
+| Cloudflare User API Token | Detects Cloudflare user API tokens such as `cfut_<USER_API_TOKEN>`. |
+| Croatia Personal ID (OIB) | Detects Croatian personal identification numbers (OIB) such as "10000000005". |
+| Denmark Tax (CPR) | Detects Danish personal identification numbers (CPR-nummer) such as "010180-0008". |
+| Diners Club Card Number | Detects Diners Club credit card numbers such as "30121690374838". |
+| Discord Webhook | Detects Discord webhook URLs such as a webhook URL under `discord.com/api/webhooks/`. |
+| Email Address | Detects email addresses such as "test@example.com". |
+| Ethereum Wallet | Detects Ethereum wallet addresses such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F". |
+| EU Passport | Detects EU member state passport numbers such as "AB1234567". |
+| FDA Active Ingredients | Detects FDA-registered drug active ingredient names such as "ABEMACICLIB". |
+| FDA Drug Names | Detects FDA-registered drug names such as "ABACAVIR". |
+| Finland Tax ID | Detects Finnish personal identity codes (Henkilötunnus / HETU) such as "311280-888Y". |
+| France CNI (National ID) | Detects French national identity card numbers (Carte nationale d'identité) such as "12345678901". |
+| France Passport | Detects French passport numbers such as "12AB34567". |
+| France Social Security Number | Detects French social security (INSEE) numbers such as "145081849670637". |
+| France Tax ID (SPI) | Detects French tax identification numbers (Numéro fiscal SPI) such as "1234567890123". |
+| France VAT | Detects French VAT numbers such as "FR12000000000". |
+| Full Name | Detects personal full names. |
+| Generic CVV Card Number | Detects credit card CVV/CVC verification codes in context of the "cvv" keyword, such as "cvv: 033". |
+| Germany Tax ID | Detects German tax identification numbers (Steueridentifikationsnummer) such as "10000000005". |
+| Germany VAT | Detects German VAT numbers (USt-IdNr) such as "DE100000003". |
+| GitHub PAT | Detects GitHub personal access tokens such as a token beginning with `ghp_`. |
+| Go | Detects Go source code. |
+| Google GCP API Key | Detects Google Cloud Platform API keys such as `AIza<API_KEY>`. |
+| Greece Tax (AFM) | Detects Greek tax identification numbers (AFM) such as "100000003". |
+| Haskell | Detects Haskell source code. |
+| Hong Kong Identity Card Number | Detects Hong Kong identity card (HKID) numbers such as "F543210(A)". |
+| Hungary Tax | Detects Hungarian tax identification numbers (Adóazonosító jel) such as "8000000008". |
+| IBAN | Detects International Bank Account Numbers (IBAN) such as "GB94 BARC 1020 1530 0934 59". |
+| ICD-10 FY2023 Short Description | Detects ICD-10 FY2023 medical diagnosis terms such as "Typhoid fever, unspecified". |
+| ICD-11 Short Description | Detects ICD-11 medical diagnosis terms such as "ABDOMINAL ACTINOMYCOSIS". |
+| India Aadhaar | Detects Indian Aadhaar national identification numbers such as "2345 6789 0124". |
+| India GST (GSTIN) | Detects Indian Goods and Services Tax identification numbers (GSTIN) such as "22AAAAA0000A1Z5". |
+| India PAN Card | Detects Indian Permanent Account Number (PAN) card identifiers such as "ABCDE1234F". |
+| India Voter ID | Detects Indian Voter ID (EPIC) numbers such as "ABC1234567". |
+| Indonesia Identity Card Number | Detects Indonesian identity card (KTP/NIK) numbers such as "3203012503770011". |
+| Indonesia Tax (NPWP) | Detects Indonesian taxpayer identification numbers (NPWP) such as "12.345.678.9-012.345". |
+| Ireland Tax (PPS) | Detects Irish Personal Public Service numbers (PPS) such as "1234567FA". |
+| Ireland VAT | Detects Ireland VAT numbers such as "IE1234567T". |
+| Italy Fiscal Code | Detects Italian fiscal codes (Codice Fiscale) such as "BNZVCN32S10E573Z". |
+| Japan Address | Detects Japanese postal addresses identified by a postal code marker such as "〒100-0001". |
+| Japan My Number (Corp) | Detects Japanese corporate My Number identifiers (Hojin Bango) such as "7000012050002". |
+| Japan My Number (Person) | Detects Japanese individual My Number identifiers (Kojin Bango) such as "100000000005". |
+| Japan Names (Kanji) | Detects Japanese personal names written in kanji and labeled in context such as "氏名: 田中太郎". |
+| Japan Passport | Detects Japanese passport numbers such as "TZ1234567". |
+| Java | Detects Java source code. |
+| JavaScript | Detects JavaScript source code. |
+| Korea Resident Number (RRN) | Detects South Korean Resident Registration Numbers (RRN) such as "850515-1234567". |
+| Lua | Detects Lua source code. |
+| Luxembourg Tax | Detects Luxembourg national identification numbers (Matricule) such as "1985010112345". |
+| Luxembourg VAT | Detects Luxembourg VAT numbers such as "LU10000053". |
+| Malaysian National Identity Card Number | Detects Malaysian national identity card (MyKad) numbers such as "560224-10-8354". |
+| Mastercard Card Number | Detects Mastercard credit card numbers such as "5252 5971 4219 4116". |
+| Mastercard Text | Detects mentions of the Mastercard brand name such as "Mastercard". |
+| Microsoft Azure Client Secret | Detects Microsoft Azure client secrets such as `<AZURE_CLIENT_SECRET>`. |
+| MX CLABE (Bank) | Detects Mexican CLABE bank account numbers such as "032180000118359719". |
+| MX CURP | Detects Mexican CURP codes such as "GOMC850515HJCRRR05". |
+| Netherlands BSN | Detects Dutch citizen service numbers (Burgerservicenummer / BSN) such as "123456782". |
+| Netherlands VAT | Detects Dutch VAT numbers (Btw-nummer) such as "NL123456782B01". |
+| NPM Token | Detects npm registry access tokens such as a token beginning with `npm_`. |
+| NZ NHI Number | Detects New Zealand National Health Index (NHI) numbers such as "ZZZ0016". |
+| NZ Tax (IRD) | Detects New Zealand Inland Revenue Department (IRD) tax numbers such as "49-091-850". |
+| OpenAI API Key | Detects OpenAI API keys such as a key beginning with `sk-proj-`. |
+| Peru Tax (RUC) | Detects Peruvian taxpayer identification numbers (RUC) such as "20000000001". |
+| Peru Unique ID (DNI) | Detects Peruvian national identity numbers (DNI) such as "12345678". |
+| Philippines Unified Multi-Purpose ID Identity Number | Detects Philippines Unified Multi-Purpose ID (UMID) numbers such as "2460-1501400-1". |
+| Poland National ID (PESEL) | Detects Polish national identification numbers (PESEL) such as "85051500006". |
+| Poland REGON | Detects Polish National Business Registry numbers (REGON) such as "100000008". |
+| Poland Tax (NIP) | Detects Polish tax identification numbers (NIP) such as "123-456-32-18". |
+| Portugal Tax (NIF) | Detects Portuguese tax identification numbers (NIF / Número de Contribuinte) such as "100000002". |
+| PyPI Token | Detects PyPI package upload tokens such as a token beginning with `pypi-`. |
+| Python | Detects Python source code. |
+| R | Detects R source code. |
+| Rust | Detects Rust source code. |
+| Singapore National Registration Identity Card Number | Detects Singapore NRIC/FIN identity card numbers such as "S6792120H". |
+| Slack API Token | Detects Slack API tokens such as a token beginning with `xoxb-`. |
+| Slack Webhook | Detects Slack incoming webhook URLs such as a webhook URL under `hooks.slack.com/services/`. |
+| Spain DNI/NIF | Detects Spanish national identity numbers (DNI/NIF) such as "12345678Z". |
+| Spain SSN | Detects Spanish Social Security affiliation numbers (NAF) such as "28 1234567890". |
+| Spain Tax (CIF) | Detects Spanish corporate tax identification codes (CIF) such as "A58818501". |
+| SSH Private Key | Detects SSH private key material such as "-----BEGIN OPENSSH PRIVATE KEY-----". |
+| Stripe Granular Restricted Key | Detects Stripe live-mode restricted API keys such as a key beginning with `rk_live_`. |
+| Stripe Standard Secret Key | Detects Stripe live-mode secret API keys such as a key beginning with `sk_live_`. |
+| Sweden Tax | Detects Swedish personal identity numbers (Personnummer) such as "811228-9874". |
+| SWIFT | Detects SWIFT/BIC business identifier codes such as "PMFAUS66". |
+| Swift | Detects Swift source code. |
+| Taiwan National Identification Number | Detects Taiwan national identification numbers such as "W171845961". |
+| Thai Identity Card Number | Detects Thai national identity card numbers such as "4-8547-01245-28-9". |
+| UAE Passport | Detects United Arab Emirates passport numbers such as "A1234567". |
+| Union Pay Card Number | Detects UnionPay credit card numbers such as "6250941006528599". |
+| Union Pay Text | Detects mentions of the UnionPay brand name such as "Union Pay". |
+| United Kingdom National Insurance Number | Detects UK National Insurance Numbers (NINO) such as "OC 66 31 85 C". |
+| United Kingdom NHS Number | Detects UK NHS patient identification numbers such as "485-585-0454". |
+| United States ABA Routing Number | Detects US ABA bank routing numbers such as "021000021". |
+| United States SSN Numeric Detection | Detects US Social Security Numbers such as "123-45-6789". |
+| United States SSN Text | Detects mentions of "SSN" or "social security" as a keyword, such as "social security". |
+| Unsanitized HAR File | Detects HAR (HTTP Archive) files that may contain unsanitized authentication tokens or session data, such as a HAR file containing `Authorization: Bearer <USER_API_TOKEN>`. |
+| Uruguay ID (CI) | Detects Uruguayan national identity numbers (Cédula de Identidad) such as "1.234.500-8". |
+| US Driver's License Number | Detects US driver's license numbers such as "CA License: A1234567". |
+| US Individual Tax Identification Number (ITIN) | Detects US Individual Taxpayer Identification Numbers (ITIN) such as "934-78-5678". |
+| US Mailing Address | Detects US mailing addresses such as "100 First St, Chicago, IL 60601". |
+| US Passport Number | Detects US passport numbers such as "A12345678". |
+| US Phone Number | Detects US phone numbers such as "555-555-5555". |
+| US Physical Address | Detects US street addresses with state and ZIP code such as "100 First St, Chicago, IL 60601". |
+| Visa Card Number | Detects Visa credit card numbers such as "4111 1111 1111 1111". |
+| Visa Text | Detects mentions of the Visa brand name such as "Visa". |
diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
index abd3ab310d2558c..96398de8d42e757 100644
--- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
+++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles.mdx
@@ -37,10 +37,10 @@ The following secrets are validated with regex.
 
 The following Cloudflare API credentials are validated algorithmically using a checksum. Only credentials generated after [Cloudflare's token format update](/fundamentals/api/get-started/token-formats/) will be matched by these entries.
 
-| Detection entry                    | Format                                                                         |
-| ---------------------------------- | ------------------------------------------------------------------------------ |
-| Cloudflare User API Key            | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum  |
-| Cloudflare User API Token          | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Detection entry | Format |
+| --- | --- |
+| Cloudflare User API Key | `cfk_` followed by 40 alphanumeric characters and an 8-character hex checksum |
+| Cloudflare User API Token | `cfut_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 | Cloudflare Account Owned API Token | `cfat_` followed by 40 alphanumeric characters and an 8-character hex checksum |
 
 ## Financial Information
@@ -52,6 +52,7 @@ The following Cloudflare API credentials are validated algorithmically using a c
 
 Credit card numbers begin with a six or eight-digit Issuer Identification Number (IIN) and are followed by up to 23 additional digits. Card verification values (CVVs) are not validated.
 
+
 In the table below, entries use one of three validation methods. [Luhn's algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is a checksum formula used to verify credit card numbers. Entries validated "with checksum" use an arithmetic check specific to that number format. Entries validated "with regex" match a known text pattern without performing a mathematical check.
 
 | Detection entry                  | Notes                                                                             |
@@ -73,9 +74,9 @@ In the table below, entries use one of three validation methods. [Luhn's algorit
 
 The **Unsanitized HAR** predefined profile detects HTTP Archive (HAR) files in traffic that have not been processed by Cloudflare's HAR sanitizer. HAR files frequently contain sensitive data such as session cookies, authorization headers, and other credentials.
 
-| Detection entry      | Notes                                                                                                                                                              |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Unsanitized HAR file | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
+| Detection entry       | Notes                                                                                                                           |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| Unsanitized HAR file  | Detects HAR files that do not carry a Cloudflare sanitized marker. Files processed by the Cloudflare HAR sanitizer and unmodified since will not match this entry. |
 
 You can use this profile in a Gateway HTTP policy to block HAR file uploads or redirect users to `https://har-sanitizer.pages.dev/` to sanitize the file before uploading. For more information, refer to [common DLP policies](/cloudflare-one/data-loss-prevention/dlp-policies/common-policies/).
 
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
index 1df5ea81ecd5b67..2ec67b8a7f2d86d 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
index 4b180d527caeea5..014c621a7fcbb9e 100644
--- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
+++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx
@@ -166,9 +166,9 @@ Email security displays the following details:
 
 #### Cloudy summaries
 
-The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted.
+The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. 
 
-Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values).
+Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). 
 
 **View all signatures** allows you to view all the detections that triggered on the email, including detections that did not determine the final disposition.
 
diff --git a/src/content/docs/cloudflare-one/email-security/reference/index.mdx b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
index 554e42af73200ca..ed22d9cc45c63d0 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
index f29fd4a0c946be4..e72de496842e22a 100644
--- a/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
+++ b/src/content/docs/cloudflare-one/email-security/reference/regional-processing.mdx
@@ -19,4 +19,4 @@ Currently, you can process emails in the following regions:
 - US
 - Germany
 - India
-- Australia
+- Australia
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
index 67304fed00d84ff..04516541176d46d 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx
@@ -21,8 +21,8 @@ To configure auto-move events:
 5. Under **Auto-moves**, select **Configure**.
 6. For each disposition (malicious, spam, bulk, suspicious, spoof), choose what happens to matching emails:
    - **Soft delete - user recoverable**: Moves the message to the user's **Recoverable Items - Deleted** folder. The user can still find and restore the message. This option is only available for Microsoft 365 customers. Refer to [Microsoft 365 Exchange data deletion](https://learn.microsoft.com/en-us/compliance/assurance/assurance-exchange-online-data-deletion) for more information.
-   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it.
+   - **Hard delete - admin recoverable**: Removes the message from the user's inbox entirely. Only an administrator can recover it. 
    - **Move to trash**: Moves the message to the user's trash or deleted items folder. This option is only available for Google Workspace users.
    - **Move to junk**: Moves the message to the user's junk or spam folder.
    - **No action**: Leaves the message where it is. Email security still records the disposition, but does not move the message.
-7. Select **Save**.
+7. Select **Save**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
index 447a71c6bb9e4af..d4eaee4d21f7a1b 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx
@@ -10,11 +10,11 @@ sidebar:
 
 This guide describes how to configure detection settings to mitigate impersonation risks while ensuring legitimate delivery.
 
-Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address.
+Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address. 
 
 For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to mitigate delivery disruptions.
 
-To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific. In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
+To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific.  In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain.
 
 ## Policy selection criteria
 
@@ -36,4 +36,4 @@ Example use cases:
 
 - Prioritize static IPs: Use known and owned, static IP addresses for relay servers. Avoid [ephemeral IP addresses](https://docs.cloud.google.com/vpc/docs/ip-addresses#ephemeral_and_static_ip_addresses) as their transient nature can lead to policy degradation.
 - Enforce Sender Verification: Always have **Sender Verification (Recommended)** enabled in the Cloudflare dashboard. It validates the originating system's email authentication records (namely [SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), and [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) against the domain to ensure authenticity.
-- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
+- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
index efaa4f6b773fcca..8481b73230a9b54 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
index 7c3b68ba2333939..fffa7bf2fdd3e28 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/domain.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="email-security/domain-information" product="cloudflare-one" />
+<Render file="email-security/domain-information" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
index 9a9a590d97573b0..4a962408af45bb5 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/domain-management/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
index b5fed567bea01e0..0365a23705fb682 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
index d3771d0098d4bb0..03b7792d24ac057 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx
@@ -21,4 +21,4 @@ To set up PhishNet Microsoft 365:
 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**.
 4. Select **Upload custom apps**.
 5. Choose **Provide link to manifest file** and paste the URL you copied from the Cloudflare One dashboard.
-6. Verify and complete the wizard.
+6. Verify and complete the wizard.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
index 0d1522a54efcba7..414eff1eb5c872e 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace.mdx
@@ -27,4 +27,4 @@ You have now successfully installed Cloudflare PhishNet.
 1. In your Gmail web client, open the message you would like to flag as either spam or phish.
 2. Select the PhishNet logo on the side panel.
 3. Under **Select Submission Type**, select **Spam** or **Phish**.
-4. Select **Submit Report**.
+4. Select **Submit Report**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
index 4190cae0904f56e..9e049608ac65e75 100644
--- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
+++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx
@@ -15,4 +15,4 @@ To view the destination addresses of user and team submissions:
 3. Select **Settings**.
 4. Go to **Phish submission** > **Submission addresses** > **View**.
 
-The dashboard will display **User submission addresses** and **Team submission addresses**.
+The dashboard will display **User submission addresses** and **Team submission addresses**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
index 43e57d4a1c293fa..c65b4336fa5ad20 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/index.mdx
@@ -15,24 +15,24 @@ import { Markdown } from "~/components";
 
 Before you start the onboarding process, you will have to:
 
-1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline.
+1. Choose a deployment path: Email security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/post-delivery-deployment/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/pre-delivery-deployment/) for MX/Inline. 
 2. Learn about dispositions, impersonation registry, and submissions.
 3. Know the steps to configure your email environment correctly.
 
 The following table compares features available across API, BCC/Journaling and MX/Inline:
 
-| Feature             | Microsoft 365                                       | Google Workspace                  | Others (On-prem/Cloud)                                   |
-| ------------------- | --------------------------------------------------- | --------------------------------- | -------------------------------------------------------- |
-| Deployment type     | API and MX                                          | BCC and MX                        | MX only                                                  |
-| API integration     | Microsoft Graph API                                 | BCC only                          | None                                                     |
-| BCC/Journaling      | Uses a Journal Rule in the Microsoft Purview portal | Uses BCC rules                    | Uses journaling                                          |
-| Inline/MX Mode      | MX records point to Cloudflare                      | MX records point to Cloudflare    | MX records point to Cloudflare                           |
-| Message remediation | Auto-moves through Read/Write API                   | Auto-moves through Read/Write API | Messages can be blocked, quarantined, or modified inline |
+| Feature             	| Microsoft 365                                       	| Google Workspace                  	| Others (On-prem/Cloud)                                   	|
+|---------------------	|-----------------------------------------------------	|-----------------------------------	|----------------------------------------------------------	|
+| Deployment type     	| API and MX                                          	| BCC and MX                        	| MX only                                                  	|
+| API integration     	| Microsoft Graph API                                 	| BCC only                          	| None                                                     	|
+| BCC/Journaling      	| Uses a Journal Rule in the Microsoft Purview portal 	| Uses BCC rules                    	| Uses journaling                                          	|
+| Inline/MX Mode      	| MX records point to Cloudflare                      	| MX records point to Cloudflare    	| MX records point to Cloudflare                           	|
+| Message remediation 	| Auto-moves through Read/Write API                   	| Auto-moves through Read/Write API 	| Messages can be blocked, quarantined, or modified inline 	|
 
 Note that:
 
 - All email providers support MX/Inline deployment.
-- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
+- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or  post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/).
 - Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/).
 
 ## 1. Choose a deployment
diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
index 61054ee69b7887b..5c704f3a770261e 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx
@@ -43,4 +43,4 @@ To stop scanning domains:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**.
-4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
+4. Select **Stop scanning** again to stop Cloudflare from scanning your domain.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
index f61e4bcb70cd12f..43b90fbe16e9a31 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
index 8bb78df403639c3..57f5aa4227abd1d 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
index ad3849aad352d63..327257b4eb0b5e5 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/index.mdx
@@ -11,4 +11,4 @@ sidebar:
 BCC/Journaling deployment is a post-delivery type of deployment. Cloudflare analyzes emails after they reach the user's inbox. Every time you receive an email, your email provider will send a blind copy to Cloudflare for an analysis.
 
 - Choose [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/) if your email provider is Gmail.
-- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
+- Choose [Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/) if your email provider is Microsoft 365.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
index 776f45cf8537714..943a2e42ca67928 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
index ac23a96bd6a598d..8ff736556bdbdba 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx
@@ -95,6 +95,7 @@ To verift that your domain has been added successfully and that your emails are
 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**.
 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**.
 
+
 ## Next steps
 
-<Render file="email-security/enable-logs" product="cloudflare-one" />
+<Render file="email-security/enable-logs" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
index 6e14bc7bb3cbd1b..4c636aa1972e3b4 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx
@@ -22,6 +22,7 @@ To use Email security, you will need to have:
 	product="cloudflare-one"
 />
 
+
 ## Manually add domains
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
index e5945fa7ffe219b..f15a938e8733a92 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/index.mdx
@@ -11,6 +11,6 @@ sidebar:
 next: false
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
index be6fcfaa82de80d..34f65be10df2f54 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
@@ -16,7 +16,7 @@ Add all of the following addresses to your mail provider's IP allowlist.
 
 Microsoft 365 does not support IPv6 addresses or the following IPv4 ranges:
 
-- `104.30.32.0/19`
+- `104.30.32.0/19` 
 - `134.195.26.0/23`
 
 If you use Microsoft 365, use the individual `/24` blocks (256 addresses each) listed in [Microsoft 365 `/24` addresses](#microsoft-365-24-addresses) instead.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
index fce333e04ebd1b6..53963c84381f2fe 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx
@@ -10,6 +10,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
index 2bcd30388647a00..d33970c173669e0 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx
@@ -27,4 +27,4 @@ To set up a partner domain:
 
 To edit a partner domain, select the three dots > **Edit**.
 
-To delete a partner domain, select the three dots > **Delete**.
+To delete a partner domain, select the three dots > **Delete**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
index a1e35434d0580f7..35bc8f11bdcdad3 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/index.mdx
@@ -10,6 +10,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
index 4c76d96d35736ed..7f5428d95fbf8ef 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/use-cases/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
index e04482e75dcf67e..14e7f12e83a674d 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx
@@ -52,4 +52,4 @@ To view submissions:
 3. Choose from the following submission types:
    - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions.
    - [**User submissions**](/cloudflare-one/email-security/submissions/user-submissions/): View emails your users submitted for submissions.
-   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
+   - [**Invalid submissions**](/cloudflare-one/email-security/submissions/invalid-submissions/): View submissions that could not be processed.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
index 87a9a602b6c10cb..aff37d96e27156f 100644
--- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
+++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx
@@ -36,4 +36,4 @@ To enable Invalid submission email notifications:
 
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
-3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
+3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/faq/devices-faq.mdx b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
index 86a6908deaaf164..d37af87433794e5 100644
--- a/src/content/docs/cloudflare-one/faq/devices-faq.mdx
+++ b/src/content/docs/cloudflare-one/faq/devices-faq.mdx
@@ -7,6 +7,7 @@ sidebar:
   order: 6
 head: []
 description: Review frequently asked questions about devices in Cloudflare Zero Trust.
+
 ---
 
 [❮ Back to FAQ](/cloudflare-one/faq/)
@@ -19,8 +20,8 @@ As the Cloudflare One Client has replaced WinDivert with WinTun architecture, al
 
 As our [Network Map](https://www.cloudflare.com/en-gb/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the data center (colo) you are connecting to isn't necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-- Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
-- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+* Sometimes your nearest colo may be undergoing maintenance or having problems. Check the [Cloudflare Status page](https://www.cloudflarestatus.com/) for system status.
+* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
 
 ## Why is my public IP address sometimes visible?
 
@@ -49,8 +50,8 @@ An [OS firewall rule](/cloudflare-one/team-and-resources/devices/cloudflare-one-
 
 If your private network is [exposed via Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/):
 
-- Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
-- Verify that the user is allowed through by your Access and Gateway policies.
-- Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
+* Verify that the Cloudflare One Client is [properly configured](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#device-configuration) on the device.
+* Verify that the user is allowed through by your Access and Gateway policies.
+* Verify that the [local LAN settings](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/#router-configuration) for the device do not overlap with the CIDR range of your private network.
 
 When contacting Cloudflare support, ensure that you include [Cloudflare One Client debug logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/) for your device. These logs will help Cloudflare support understand the overall architecture of your machine and networks.
diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
index f1c5be808fd91bf..94280945992ed4c 100644
--- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx
@@ -133,4 +133,4 @@ In **Gateway insights**, you can view a report on your Gateway firewall policies
 In **CASB**, you can review instances of security issues — such as misconfigurations, unauthorized user activity, and shadow IT — found in your SaaS integrations by [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).
 
 - Integrations by number of findings
-- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
+- [DLP](/cloudflare-one/data-loss-prevention/) findings by profile name
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
index 3ab91476f6fa6d1..2295744544866ab 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/ai-security.mdx
@@ -24,19 +24,19 @@ To view the AI security report dashboard:
 
 To populate the AI security report dashboard, you must have:
 
-- [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
-- User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
-- [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
+* [Cloudflare Gateway](/cloudflare-one/traffic-policies/) enabled to inspect outbound HTTP and DNS traffic.
+* User traffic to SaaS AI applications (for example, ChatGPT or Gemini) sent through Cloudflare Gateway.
+* [Model Context Protocol (MCP) servers](/cloudflare-one/access-controls/ai-controls/) behind [Cloudflare Access](/cloudflare-one/access-controls/) policies.
 
 ## Available insights
 
 The AI security report dashboard includes the following panels and metrics:
 
-- [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
-- [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
-- [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
-- [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
-- [Access login events to MCP servers](#access-login-events-to-mcp-servers)
+* [Top 5 visited AI applications by user count](#top-5-visited-ai-applications-by-user-count)
+* [Statuses applied to AI applications by application count](#statuses-applied-to-ai-applications-by-application-count)
+* [Data uploaded to Artificial Intelligence applications by status](#data-uploaded-to-artificial-intelligence-applications-by-status)
+* [MCP servers behind Access over time](#mcp-servers-behind-access-over-time)
+* [Access login events to MCP servers](#access-login-events-to-mcp-servers)
 
 ### Top 5 visited AI applications by user count
 
@@ -50,10 +50,10 @@ Use this chart to monitor adoption trends and detect new or unauthorized AI tool
 Reports the total number of AI applications identified and their review statuses.  
 Statuses include:
 
-- Unreviewed — Applications not yet evaluated by administrators.
-- In Review — Applications currently under review for approval.
-- Unapproved — Applications that are restricted or blocked.
-- Approved — Applications explicitly permitted for organizational use.
+* Unreviewed — Applications not yet evaluated by administrators.  
+* In Review — Applications currently under review for approval.  
+* Unapproved — Applications that are restricted or blocked.  
+* Approved — Applications explicitly permitted for organizational use.
 
 ### Data uploaded to Artificial Intelligence applications by status
 
@@ -66,4 +66,4 @@ Displays the number of Model Context Protocol (MCP) servers protected by [Cloudf
 
 ### Access login events to MCP servers
 
-Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
+Reports the number of login events to MCP servers protected by Access policies. Use this panel to identify unusual login patterns, such as spikes in access from unexpected users.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
index 7a066e04802a46a..475a4c3d35c46ac 100644
--- a/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
+++ b/src/content/docs/cloudflare-one/insights/analytics/application-access.mdx
@@ -29,20 +29,20 @@ To view the Application Access Report dashboard:
 
 To populate the Application Access Report dashboard, you must have:
 
-- At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
-- Users authenticating to these applications through Cloudflare Access.
+* At least one [Access application](/cloudflare-one/access-controls/applications/) configured in your account.
+* Users authenticating to these applications through Cloudflare Access.
 
 ## Available insights
 
 The Application Access Report dashboard includes the following panels and metrics:
 
-- [Summary of Access activity](#summary-of-access-activity)
-- [Access events](#access-events)
-- [Access decisions by event count](#access-decisions-by-event-count)
-- [Access applications by event count](#access-applications-by-event-count)
-- [Access events by type](#access-events-by-type)
-- [Top counts of event details](#top-counts-of-event-details)
-- [Access admin metrics](#access-admin-metrics)
+* [Summary of Access activity](#summary-of-access-activity)
+* [Access events](#access-events)
+* [Access decisions by event count](#access-decisions-by-event-count)
+* [Access applications by event count](#access-applications-by-event-count)
+* [Access events by type](#access-events-by-type)
+* [Top counts of event details](#top-counts-of-event-details)
+* [Access admin metrics](#access-admin-metrics)
 
 ### Summary of Access activity
 
@@ -55,7 +55,7 @@ You can use this graph to review user authentication activity and detect unusual
 
 ### Access decisions by event count
 
-Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).
+Displays the total number of Access decisions made, grouped by outcome (for example, **Granted** or **Denied**).  
 
 ### Access applications by event count
 
@@ -71,11 +71,11 @@ This panel helps administrators understand how users are authenticating across a
 
 Lists the most common Access event attributes, including:
 
-- Application name — Displays the top accessed applications.
-- Identity provider — Shows which identity providers (IdPs) were most used.
-- Users — Lists top users by number of login events.
-- Countries — Displays top countries where users logged in.
-- IP addresses — Lists the top source IPs associated with login events.
+* Application name — Displays the top accessed applications.
+* Identity provider — Shows which identity providers (IdPs) were most used.
+* Users — Lists top users by number of login events.
+* Countries — Displays top countries where users logged in.
+* IP addresses — Lists the top source IPs associated with login events.
 
 These insights help administrators identify usage patterns and trends.
 
@@ -83,7 +83,7 @@ These insights help administrators identify usage patterns and trends.
 
 Provides a summary of Access configurations made by admin in your organization, including:
 
-- Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
-- Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
+* Applications configured — Total number of Access-protected applications, broken down by type (for example, Self-hosted, SaaS, RDP, SSH, Private network, and [Cloudflare Dashboard SSO](/fundamentals/manage-members/dashboard-sso/)).
+* Policies configured — Total number of Access policies, grouped by [policy action](/cloudflare-one/access-controls/policies/#actions) (for example, Allow, Block, Bypass, or Service Auth).
 
-This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
+This section helps administrators audit their Access setup and verify that expected resources and policies are in place.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
index cc397c6684cbb8e..7768588f1179831 100644
--- a/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/mcp-server.mdx
@@ -7,4 +7,5 @@ title: MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dex-analysis
 sidebar:
   order: 90
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
index 1309beff1282a3f..056e13ea2ec0cca 100644
--- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx
@@ -35,12 +35,12 @@ To view analytics on a per-device level, go to [Device monitoring](/cloudflare-o
 
 - **Connectivity status**: Percentage of devices in a given Cloudflare One Client state.
 
-  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                                                         |
-  | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                               |
-  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                                |
+  | Status       | Description                                                                                                                                                                                                                                                                                                                                                                               |
+  | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+  | Connected    | The Cloudflare One Client has successfully established a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                                          |
+  | Disconnected | The Cloudflare One Client has been intentionally or unintentionally disconnected from the Cloudflare global network.                                                                                                                                                                                                                                                                                           |
   | Paused       | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [admin override code](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes). Paused clients will [auto-connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) after a timeout period. |
-  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                                 |
+  | Connecting   | The Cloudflare One Client is pending connection, but is actively trying to establish a connection to the Cloudflare global network.                                                                                                                                                                                                                                                                            |
 
 - **Mode**: [Client mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) deployed on the device.
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
index 7336bc04cde6cad..0823f895e22fb5c 100644
--- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx
@@ -42,7 +42,7 @@ Review the available selectors and their scope in the following list.
 | **Operating system version** | For specifying an operating system version (use Operator `in`) or versions (use Operator `is`).                                   |
 | **Managed network**          | For specifying users accessing the network from the office (managed network) compared to those accessing remotely.                |
 | **SAML attributes**          | For specifying a value from the [SAML Attribute Assertion](/cloudflare-one/traffic-policies/identity-selectors/#saml-attributes). |
-| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                 |
+| **Colos**                    | For specifying a Cloudflare data center (colocation) that users are connected to.                                                          |
 
 ## Add a rule to a test
 
diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
index d09f0e887f56c41..15a13b2b8c484f9 100644
--- a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx
@@ -20,8 +20,4 @@ To control which users or groups run a test, use [DEX rules](/cloudflare-one/ins
 
 ## Export DEX application test logs
 
-<Render
-	file="dex/logpush-export"
-	product="cloudflare-one"
-	params={{ applicationTests: true }}
-/>
+<Render file="dex/logpush-export" product="cloudflare-one" params={{ applicationTests: true }} />
diff --git a/src/content/docs/cloudflare-one/insights/index.mdx b/src/content/docs/cloudflare-one/insights/index.mdx
index 53baf5cb249a412..84559d3b901bfca 100644
--- a/src/content/docs/cloudflare-one/insights/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/index.mdx
@@ -40,16 +40,18 @@ If your device is experiencing connectivity issues, Cloudflare recommends starti
 
 1. Use [Analytics Dashboards](/cloudflare-one/insights/analytics/) to understand trends and for visualizations of your log data.
 
-   Administrators typically start with Analytics Dashboards because they offer:
-   - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
-   - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
+    Administrators typically start with Analytics Dashboards because they offer:
+
+    - A high-level view of activity across your products, like Access, or security use cases, such as AI and shadow IT.
+    - Visibility into trends, provided through time-series graphs, to track the evolution of key metrics (such as [DNS queries](/cloudflare-one/insights/analytics/gateway/#dns-query-analytics), [network sessions](/cloudflare-one/insights/analytics/gateway/#network-session-analytics), [HTTP requests](/cloudflare-one/insights/analytics/gateway/#http-request-analytics), and [CASB posture/content findings](/cloudflare-one/insights/analytics/data-analytics/)) over time.
 
 2. Use [Logs](/cloudflare-one/insights/logs/) as needed for event-level verification.
 
-   Use Logs when you need to:
-   - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
-   - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
-   - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
+    Use Logs when you need to:
+
+    - Investigate a specific event; for example, a user's [failed authentication attempt](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/) when trying to log in to an application.
+    - Validate identity or device details; for example, confirming which user made the request, how they authenticated, and whether their device met required [posture conditions](/cloudflare-one/insights/logs/dashboard-logs/posture-logs/).
+    - Confirm policy matches; for example, verifying which [specific rule](/cloudflare-one/access-controls/policies/#rule-types) allowed, blocked, or challenged a user's request and why it was applied.
 
 ### User-reported issues
 
@@ -57,4 +59,4 @@ Users may report problems like slow or failing connections to internal apps.
 
 1. Start with [Analytics Dashboards](/cloudflare-one/insights/analytics/) to review whether the issue impacts others.
 2. Check [Logs](/cloudflare-one/insights/logs/) for failed authentication attempts, blocked requests, or unexpected policy matches.
-3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
+3. Use [DEX](/cloudflare-one/insights/dex/) to diagnose device- or network-level causes with [synthetic tests](/cloudflare-one/insights/dex/tests/) and [device monitoring](/cloudflare-one/insights/dex/monitoring/).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
index 0761b8662b76208..304fa8f96f03164 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx
@@ -16,18 +16,18 @@ To view admin activity logs, log in to the [Cloudflare dashboard](https://dash.c
 
 ## Explanation of the fields
 
-| Field           | Description                                      | Example Value                                                                          |
-| --------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------- |
-| Email           | User who performed the action                    | josephli@cloudflare.com                                                                |
-| Product         | Cloudflare product being modified                | Tunnel                                                                                 |
-| Resource        | Specific resource type within the product        | Route                                                                                  |
-| Event           | Action performed (Create, Update, Delete)        | Create                                                                                 |
-| Date            | Timestamp of when the action occurred            | April 30, 2026 • 12:19 AM                                                              |
-| User IP Address | IP address of the user who made the change       | 2a09:bac6:6447:523::83:30                                                              |
-| Interface       | How the change was initiated                     | API                                                                                    |
-| Audit record    | Unique identifier for the audit log entry        | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                                   |
-| Old value       | Previous configuration state (empty for creates) | {}                                                                                     |
-| New value       | New configuration state after the change         | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
+| Field           | Description                                           | Example Value                                                                      |
+| ----------------| ------------------------------------------------------| -----------------------------------------------------------------------------------|
+| Email           | User who performed the action                         | josephli@cloudflare.com                                                            |
+| Product         | Cloudflare product being modified                     | Tunnel                                                                             |
+| Resource        | Specific resource type within the product             | Route                                                                              |
+| Event           | Action performed (Create, Update, Delete)             | Create                                                                             |
+| Date            | Timestamp of when the action occurred                 | April 30, 2026 • 12:19 AM                                                          |
+| User IP Address | IP address of the user who made the change            | 2a09:bac6:6447:523::83:30                                                          |
+| Interface       | How the change was initiated                          | API                                                                                |
+| Audit record    | Unique identifier for the audit log entry             | caf1a547-17cc-484a-b4ce-5d3b32771a8f                                               |
+| Old value       | Previous configuration state (empty for creates)      | {}                                                                                 |
+| New value       | New configuration state after the change              | JSON object with fields like comment, network, tun_type, tunnel_id, virtual_network_id |
 
 ## Export admin activity logs
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
index 32b6c971303f04d..b2a31ec6e175c94 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx
@@ -30,18 +30,17 @@ To view Gateway activity logs:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Choose a type of Gateway log:
-   - **DNS query logs**
-   - **Network logs**
-   - **HTTP request logs**
-     :::note[Log viewer (beta)]
-     Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
-     :::
+	- **DNS query logs**
+	- **Network logs**
+	- **HTTP request logs**
+	:::note[Log viewer (beta)]
+	Gateway logs use an updated log viewer with enhanced filtering capabilities. To switch to the classic view, select **Return to old logs**.
+	:::
 3. (Optional) Filter the logs that display in the log viewer. You can filter logs by their timestamp and event details (such as host, URL, user email, policy action, and more).
 
-   :::tip
-   Querying for fewer fields improves log loading performance.
-   :::
-
+	:::tip
+	Querying for fewer fields improves log loading performance.
+	:::
 4. Select an individual timestamp to investigate the event in more detail.
 
 ## Selective logging
@@ -62,16 +61,16 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Basic information
 
-| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                                       |
-| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Field                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Query name**        | Name of the domain that was queried.                                                                                                                                                                                                                                                                                                                                                                                             |
+| **Query ID**          | UUID of the query assigned by Cloudflare.                                                                                                                                                                                                                                                                                                                                                                                        |
 | **Email**             | Email address of the user who registered the Cloudflare One Client where traffic originated from. If a non-identity on-ramp (such as a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)) or machine-level authentication (such as a [service token](/cloudflare-one/access-controls/service-credentials/service-tokens/)) was used, this value will be `non_identity@<team-domain>.cloudflareaccess.com`. |
-| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                                |
-| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                            |
-| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                                     |
-| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                                     |
-| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| **Action**            | The [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) Gateway applied to the query (such as Allow or Block).                                                                                                                                                                                                                                                                                                      |
+| **Time**              | Date and time of the DNS query.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| **Resolver decision** | The reason why Gateway applied a particular **Action** to the request. Refer to the [list of resolver decisions](#resolver-decisions).                                                                                                                                                                                                                                                                                           |
+| **Resolved IPs**      | Resolved IP addresses in the response.                                                                                                                                                                                                                                                                                                                                                                                           |
+| **CNAMEs**            | `CNAME` records in the query.                                                                                                                                                                                                                                                                                                                                                                                                    |
 
 #### Configuration information
 
@@ -86,14 +85,14 @@ These settings only apply to logs displayed in Cloudflare One. Logpush data is u
 
 #### Identities
 
-| Field                  | Description                                                                                                                                                                                                                  |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                                                                                                        |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**              | Email address of the user who registered the Cloudflare One Client where traffic originated from.                                                                                                                            |
-| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                                        |
+| **User ID**            | UUID of the user. Each unique email address in your organization will have a UUID associated with it.                                                                                                              |
 | **Registration ID**    | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered for a particular email. The same physical device may have multiple registration IDs.           |
 | **Device name**        | Display name of the device returned by the operating system to the Cloudflare One Client. Typically this is the hostname of a device. Not all devices will have a device name. Device names are not guaranteed to be unique. |
 | **Device ID**          | UUID of the device connected with the Cloudflare One Client. Each physical device in your organization will have a UUID.                                                                                                     |
-| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                          |
+| **Last authenticated** | Date and time the user last authenticated their Zero Trust session.                                                                                                                                                |
 
 #### DNS query details
 
@@ -183,14 +182,14 @@ To log failed connections, use [network session logs](/logs/logpush/logpush-job/
 
 #### Identities
 
-| Field                  | Description                                                                                     |
-| ---------------------- | ----------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                           |
+| ---------------------- | ------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user sending the packet. This is generated by the Cloudflare One Client.   |
 | **User ID**            | ID of the user sending the packet. This is generated by the Cloudflare One Client.              |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.           |
-| **Device name**        | Name of the device that sent the packet.                                                        |
+| **Device name**        | Name of the device that sent the packet.                                              |
 | **Device ID**          | ID of the physical device that sent the packet. This is generated by the Cloudflare One Client. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                      |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                            |
 
 #### Network query details
 
@@ -229,7 +228,7 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 | Field                        | Description                                                                                                                                                                                                                                                                                                                              |
 | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Host**                     | Hostname in the HTTP header for the HTTP request. Gateway will log the SNI in this field if it responded to the request with a Do Not Inspect action. If Gateway does not receive the SNI, this field will be empty.                                                                                                                     |
-| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                     |
+| **Email**                    | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                                                                                                                                                                                                                               |
 | **Action**                   | The Gateway [Action](/cloudflare-one/traffic-policies/dns-policies/#actions) taken based on the first rule that matched (such as Allow or Block).                                                                                                                                                                                        |
 | **Request ID**               | Unique ID of the request.                                                                                                                                                                                                                                                                                                                |
 | **Time**                     | Date and time of the HTTP request.                                                                                                                                                                                                                                                                                                       |
@@ -253,14 +252,14 @@ Gateway does not log HTTP bodies. The exception is error requests: when an HTTP
 
 #### Identities
 
-| Field                  | Description                                                                                                                             |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Field                  | Description                                                                                                                   |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **Email**              | Email address of the user who made the HTTP request. This is generated by the Cloudflare One Client.                                    |
 | **User ID**            | ID of the user who made the request. This is generated by the Cloudflare One Client.                                                    |
 | **Registration ID**    | ID of the user's device registration. This is generated by the Cloudflare One Client.                                                   |
-| **Device name**        | Name of the device that made the request.                                                                                               |
+| **Device name**        | Name of the device that made the request.                                                                                     |
 | **Device ID**          | ID of the physical device that made the request. This is generated by the Cloudflare One Client on the device that created the request. |
-| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                              |
+| **Last authenticated** | Date and time the user last authenticated with Zero Trust.                                                                    |
 
 #### HTTP query details
 
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
index 5a3e6717195a05e..bc1f6d84f202733 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx
@@ -15,6 +15,6 @@ import { DirectoryListing } from "~/components";
 
 The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment.
 
-<DirectoryListing button={true} />
+<DirectoryListing button={true}/>
 
 For additional datasets and long-term log storage, refer to [Logpush](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
index ec364aac8147715..9a69bac2bfb4fe7 100644
--- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx
@@ -33,7 +33,7 @@ Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/
 | Field               | Description                                                                                                                                                                                                                    |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Email**           | Email used to register the device with Zero Trust.                                                                                                                                                                             |
-| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                                |
+| **User ID**         | Unique identifier (UUID) of the user who registered the device.                                                                                                                                                    |
 | **Registration ID** | UUID of the user's Cloudflare One Client registration. A unique registration ID is generated each time a device is registered. The same physical device may have multiple registration IDs if multiple users share the device. |
 
 ### Posture details
diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
index 0d6bfb37f1273e2..375008abd658fd5 100644
--- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx
@@ -38,23 +38,23 @@ For more information on supported destinations, refer to [Enable destinations](/
 
 Logpush supports all [dashboard logs](/cloudflare-one/insights/logs/dashboard-logs/) as well as additional datasets not available in the Cloudflare One dashboard. Refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/) for a list of all available fields.
 
-| Dataset                                                                                                    | Description                                                                                                                                                            |
-| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                                  |
-| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                                        |
-| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                              |
-| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                                           |
-| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                                   |
-| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                                |
-| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                                        |
-| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                                            |
-| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                                          |
-| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                                        |
-| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                                   |
-| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/)               |
+| Dataset                                                                                                    | Description                                                                                                                                              |
+| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Access Requests](/logs/logpush/logpush-job/datasets/account/access_requests/)                             | HTTP requests to sites protected by Cloudflare Access                                                                                                    |
+| [Audit Logs](/logs/logpush/logpush-job/datasets/account/audit_logs/)                                       | Authentication events through Cloudflare Access                                                                                                          |
+| [Browser Isolation User Actions](/logs/logpush/logpush-job/datasets/account/biso_user_actions/)            | Data transfer actions performed by a user in the remote browser, such as copy, paste, and download events                                                |
+| [CASB Findings](/logs/logpush/logpush-job/datasets/account/casb_findings/)                                 | Security issues detected by Cloudflare's Cloud Access Security Broker (CASB)                                                                             |
+| [Device Posture Results](/logs/logpush/logpush-job/datasets/account/device_posture_results/)               | Device posture status from the Cloudflare One Client                                                                                                     |
+| [DEX Application Tests](/logs/logpush/logpush-job/datasets/account/dex_application_tests/)                 | Digital Experience Monitoring (DEX) automated connectivity check results from the Cloudflare One Client                                                   |
+| [DEX Device State Events](/logs/logpush/logpush-job/datasets/account/dex_device_state_events/)             | Digital Experience Monitoring (DEX) device event data like connectivity, CPU usage, and Disk I/O from the Cloudflare One Client                          |
+| [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/)                                     | DNS queries inspected by Cloudflare Gateway                                                                                                              |
+| [Gateway HTTP](/logs/logpush/logpush-job/datasets/account/gateway_http/)                                   | HTTP requests inspected by Cloudflare Gateway                                                                                                            |
+| [Gateway Network](/logs/logpush/logpush-job/datasets/account/gateway_network/)                             | Network packets inspected by Cloudflare Gateway                                                                                                          |
+| [MCP Portal Logs](/logs/logpush/logpush-job/datasets/account/mcp_portal_logs/)                             | Requests made through [MCP server portals](/cloudflare-one/access-controls/ai-controls/mcp-portals/)                                                     |
+| [SSH Logs](/logs/logpush/logpush-job/datasets/account/ssh_logs/)                                           | SSH command logs for [Access for Infrastructure targets](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) |
 | [WARP Config Changes](/logs/logpush/logpush-job/datasets/account/warp_config_changes/)                     | Event logs that Cloudflare generates whenever a device changes [profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) |
-| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                                     |
-| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                                  |
+| [WARP Toggle Events](/logs/logpush/logpush-job/datasets/account/warp_toggle_changes/)                      | Event logs that Cloudflare generates whenever a device toggles the Cloudflare One Client on or off                                                       |
+| [Zero Trust Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Network session logs for all traffic proxied through Cloudflare Gateway across all supported on-ramps                                                    |
 
 ## Verify regional map application
 
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
index cc0006a02875a8c..b326012ef5deb96 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx
@@ -176,7 +176,7 @@ When you validate an R2 bucket, exclude the `access-key-id` and `secret-access-k
 
 1. In the Cloudflare dashboard, go to the **R2** page.
 
-   <DashButton url="/?to=/:account/r2/overview" />
+	<DashButton url="/?to=/:account/r2/overview" />
 
 2. Select **Create bucket**.
 3. Give your bucket a name > **Create bucket**.
@@ -220,4 +220,4 @@ The [response](/api/resources/magic_transit/subresources/pcaps/subresources/owne
 
 ### Validate bucket ownership
 
-Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
+Refer to the [Validate a bucket](#validate-a-bucket) API instructions for more details on the entire process to [validate your R2 bucket](/api/resources/magic_transit/subresources/pcaps/subresources/ownership/methods/validate/). When specifying the R2 destination for this validation, exclude the secret and access keys from the URL.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
index 26abc473b6c624b..f8b03fb96ce715a 100644
--- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
+++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/index.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-one
 sidebar:
   order: 1
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Packet captures allow you to record raw network traffic data passing through Cloudflare's network so you can inspect it offline in tools like Wireshark. This is useful for diagnosing connectivity issues, verifying firewall rules, or investigating unexpected traffic patterns.
 
@@ -34,4 +35,4 @@ Full packet captures will collect new traffic sent to Cloudflare's network after
 
 Refer to the articles in this section to learn how to use packet captures.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
index 62b2709c8e9fc6c..abe3862c5a9b050 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/anthropic.mdx
@@ -78,14 +78,14 @@ Flag organization access issues to help enforce best practices.
 
 <Render file="casb/data-loss-prevention" product="cloudflare-one" />
 
-| Finding type                                                     | Severity |
-| ---------------------------------------------------------------- | -------- |
-| Anthropic: Downloadable File with DLP Profile match              | High     |
-| Anthropic: Claude Chat User Prompt with DLP Profile match        | High     |
-| Anthropic: Claude Chat Assistant Response with DLP Profile match | High     |
-| Anthropic: Claude Chat Uploaded File with DLP Profile match      | High     |
-| Anthropic: Claude Chat Generated File with DLP Profile match     | High     |
-| Anthropic: Claude Project File with DLP Profile match            | High     |
-| Anthropic: Claude Project Document with DLP Profile match        | High     |
-| Anthropic: Claude Chat Artifact with DLP Profile match           | High     |
-| Anthropic: Claude Project Instructions with DLP Profile match    | High     |
+| Finding type                                                  | Severity |
+| ------------------------------------------------------------- | -------- |
+| Anthropic: Downloadable File with DLP Profile match           | High     |
+| Anthropic: Claude Chat User Prompt with DLP Profile match     | High     |
+| Anthropic: Claude Chat Assistant Response with DLP Profile match | High  |
+| Anthropic: Claude Chat Uploaded File with DLP Profile match   | High     |
+| Anthropic: Claude Chat Generated File with DLP Profile match  | High     |
+| Anthropic: Claude Project File with DLP Profile match         | High     |
+| Anthropic: Claude Project Document with DLP Profile match     | High     |
+| Anthropic: Claude Chat Artifact with DLP Profile match        | High     |
+| Anthropic: Claude Project Instructions with DLP Profile match | High     |
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
index 9b59aa70fcbddaa..a4f8fc32d81828a 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot-fedramp.mdx
@@ -30,4 +30,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot-fedramp",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
index b3db2aa1d185051..6c36357bcb412de 100644
--- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
+++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot.mdx
@@ -22,4 +22,4 @@ import { Render } from "~/components";
 		environmentName: "Microsoft 365 account",
 		slugifiedName: "microsoft-365/copilot",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
index e82f7aac39559b8..9e0e96c4c48ecff 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx
@@ -60,7 +60,7 @@ https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
 | `name`         | `${user:name}`       |
 | `surName`      | `${user:familyName}` |
 
-| `givenName` | `${user:givenName}` |
+| `givenName`    | `${user:givenName}`  |
 
 ![Configuring attribute statements in IAM Identity Center](~/assets/images/cloudflare-one/identity/aws/aws-saml-attributes.png)
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
index d01bcec09cbb731..b11fbe6575bd942 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/cloudflare.mdx
@@ -46,8 +46,8 @@ Make a `POST` request to the [Identity Providers](/api/resources/zero_trust/subr
 
 ## Configuration options
 
-| Option                          | Description                                                                                                                                                                  | Default  |
-| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| Option | Description | Default |
+| --- | --- | --- |
 | **Restrict to account members** | When enabled, only users who are members of your Cloudflare account can authenticate. When disabled, any Cloudflare user can authenticate (subject to your Access policies). | Disabled |
 
 ## Use Cloudflare account membership in policies
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
index c9d7965c3fd2706..f15160944863211 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/facebook-login.mdx
@@ -12,7 +12,7 @@ import { Render } from "~/components";
 
 Use these steps to set up Facebook as your identity provider.
 
-1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one.
+1. Go to [developers.facebook.com](https://developers.facebook.com/). Create a Developer account if you do not have one. 
 
 2. Select **Create App** at the top-right. The **Create an app** card displays.
 
@@ -42,7 +42,7 @@ Use these steps to set up Facebook as your identity provider.
 
 15. Select **Settings**, and ensure that **Use Strict Mode for redirect URIs** slider is set to **Yes**.
 
-16. In the **Valid OAuth Redirect URIs** field, enter the following URL:
+15. In the **Valid OAuth Redirect URIs** field, enter the following URL:
 
     ```txt
     https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
@@ -50,7 +50,7 @@ Use these steps to set up Facebook as your identity provider.
 
     <Render file="find-team-name" product="cloudflare-one" />
 
-17. Select **Save Changes**.
+16. Select **Save Changes**.
 
 To test that your connection is working, follow the steps on [SSO Integration](/cloudflare-one/integrations/identity-providers/#test-idps-in-cloudflare-one).
 
@@ -65,4 +65,4 @@ To test that your connection is working, follow the steps on [SSO Integration](/
 	"type": "facebook",
 	"name": "my example idp"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
index 583bae2a4359175..8ffadf28cdfd7c6 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx
@@ -55,8 +55,8 @@ To configure GitHub access in both GitHub and Cloudflare One:
 14. Select **Save**.
 
 15. Select **Finish setup** to launch a GitHub authorization page. You will be asked to grant the following permissions to Cloudflare Access:
-    - Organizations and teams (read-only)
-    - Email addresses (read-only)
+	- Organizations and teams (read-only)
+	- Email addresses (read-only)
 
 16. Select **Authorize**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
index e8868c73cbac521..643ef76b062e609 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx
@@ -10,6 +10,7 @@ tags:
 
 import { Render } from "~/components";
 
+
 Cloudflare One integrates with your organization's identity provider to apply Cloudflare One and Secure Web Gateway policies. If you work with partners, contractors, or other organizations, you can integrate multiple identity providers simultaneously.
 
 As an alternative to configuring an identity provider, Cloudflare One can send a [one-time PIN (OTP)](/cloudflare-one/integrations/identity-providers/one-time-pin/) to approved email addresses. No configuration needed — simply add a user's email address to an [Access policy](/cloudflare-one/access-controls/policies/) and to the group that allows your team to reach the application. You can simultaneously configure an OTP and an identity provider to allow users to use their own authentication method.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
index 88472d050f21f91..2ef2f3ad811f160 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx
@@ -78,13 +78,13 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
 
    ![Configuring the Groups claim filter in Okta](~/assets/images/cloudflare-one/identity/okta/okta-2.png)
 
+
 9. Set **Groups claim filter** to _Matches regex_ and its value to `.*`.
 
 :::note[Token claim expressions]
-
 - Groups managed outside of Okta (for example, Microsoft Entra ID or Google groups) may require different regex values. For more information, refer to the Okta documentation on [Groups Claims](https://support.okta.com/help/s/article/Why-isnt-my-Groups-claim-returning-Active-Directory-groups) and [OpenID Connect Claims](https://support.okta.com/help/s/article/Can-we-retrieve-both-Active-Directory-and-Okta-groups-in-OpenID-Connect-claims).
 - To configure more complex expressions, refer to Okta's [token claims documentation](https://help.okta.com/okta_help.htm?type=oie&locale=en&id=federated-claims-overview).
-  :::
+:::
 
 10. In the **General** tab, copy the **Client ID** and **Client secret**.
 
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
index 9d30c743f2b37e0..6e57a4c17621c6c 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx
@@ -46,6 +46,7 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C
    | `givenName`           | Given Name     |
    | `surName`             | Family Name    |
 
+
    These [SAML attributes](/cloudflare-one/integrations/identity-providers/generic-saml/#saml-attributes) tell Cloudflare Access who the user is.
 
 9. Set the application to **Active**.
diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
index 698b9665695a37d..1dfbd4cc2c93d21 100644
--- a/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
+++ b/src/content/docs/cloudflare-one/integrations/identity-providers/signed_authn.mdx
@@ -37,10 +37,12 @@ To set up Signed AuthN requests:
    Ensure that your IdP validation uses the most recent certificate. Cloudflare Access routinely rotates the public key as a security measure.
 
    Cloudflare Access uses a certificate that includes the following 2 distinguished name fields:
+
    - **Issuer Distinguished Name** - `CN=cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
    - **Subject Distinguished Name** - `CN=*.cloudflareaccess.com, C=US, ST=Texas, L=Austin, O=Cloudflare`
 
    Most IdP configurations require 3 components to enforce AuthN signature verification:
+
    - **Certificate issuer [distinguished name (DN)](https://knowledge.digicert.com/generalinformation/INFO1745.html)**
    - **Certificate subject distinguished name**
    - **Public certificate**
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
index 470285aa6aaa407..164e679ec887af6 100644
--- a/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
+++ b/src/content/docs/cloudflare-one/integrations/service-providers/index.mdx
@@ -18,8 +18,8 @@ Service-to-service integrations allow the Cloudflare One Client to get device po
 
 ## Supported operating systems
 
-| Device posture check                                                                    | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| --------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
+| Device posture check                                                                        | macOS | Windows | Linux | iOS | Android/ChromeOS |
+| ------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
 | [Custom integration](/cloudflare-one/integrations/service-providers/custom/)            | ✅    | ✅      | ✅    | ✅  | ✅               |
 | [Crowdstrike](/cloudflare-one/integrations/service-providers/crowdstrike/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
 | [Kolide](/cloudflare-one/integrations/service-providers/kolide/)                        | ✅    | ✅      | ✅    | ❌  | ❌               |
diff --git a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
index ff02d7946387387..e973af0760d4ab3 100644
--- a/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectivity-options.mdx
@@ -11,17 +11,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-one-connectivity-options"
-	product="networking-services"
-	params={{
-		unifiedRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-	}}
+  file="cloudflare-one-connectivity-options"
+  product="networking-services"
+  params={{
+    unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+    connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliances/",
+    cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+    onRampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
index c69c567e9be0058..7e26c4da5a75875 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-mesh/routes.mdx
@@ -37,7 +37,6 @@ flowchart LR
   node --> db
   node --> printer
 ```
-
 ## Manage routes
 
 Use CIDR routes to forward traffic from your mesh node to devices on your local network.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
index 98f1c0ce87d79e1..4d20096eb33e2fd 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
@@ -15,8 +15,8 @@ Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`,
 
 The following table lists the cipher suites supported by `cloudflared`:
 
-| Protocol support            | Cipher suites                                                                                                                                                                                                                                                                              |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| TLS 1.3 only                | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256`                                                                                                                                                                                                 |
-| TLS 1.2 only                | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
-| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`                                                                                                                     |
+| Protocol support | Cipher suites |
+|------------------|----------------|
+| TLS 1.3 only | `TLS_AES_128_GCM_SHA256`<br />`TLS_AES_256_GCM_SHA384`<br />`TLS_CHACHA20_POLY1305_SHA256` |
+| TLS 1.2 only | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`<br />`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`<br />`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`<br />`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
+| Up to and including TLS 1.2 | `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`<br />`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA` |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
index e0edd83ad74e895..f60f0eecf786013 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 3
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing  } from "~/components";
 
 After [creating your Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/), you can configure various aspects of how `cloudflared` runs and connects your infrastructure to Cloudflare's network. This section covers advanced configuration options to optimize tunnel performance, security, and availability.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
index 19d5f191ab29920..b6e4ec71f36882d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters.mdx
@@ -13,13 +13,11 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/origin-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-		validatingJwtURL:
-			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
-	}}
+  file="tunnel/origin-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
index f6088ef1050edb8..3b9c067dddd114d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
@@ -65,70 +65,70 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-   <Tabs syncKey="dashPlusAPI">
-   	<TabItem label="Dashboard">
-   	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
-   	2. Select a `cloudflared` tunnel and select **Edit**.
-   	3. Select **Refresh token**.
-   	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
-   
-   	</TabItem>
-   	<TabItem label="API">
-   		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
-   
-   				```sh
-   				openssl rand -base64 32
-   				```
-   
-   				```sh output
-   				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
-   				```
-   
-   	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
-   
-   			<APIRequest
-   				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-   				method="PATCH"
-   				json={{
-   					name: "Example tunnel",
-   					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
-   				}}
-   			/>
-   
-   			```sh output {18}
-   			{
-   				"success": true,
-   				"errors": [],
-   				"messages": [],
-   				"result": {
-   					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
-   					"account_tag": "699d98642c564d2e855e9661899b7252",
-   					"created_at": "2024-12-04T22:03:26.291225Z",
-   					"deleted_at": null,
-   					"name": "Example tunnel",
-   					"connections": [],
-   					"conns_active_at": null,
-   					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
-   					"tun_type": "cfd_tunnel",
-   					"metadata": {},
-   					"status": "inactive",
-   					"remote_config": true,
-   					"token": "eyJhIjoiNWFiNGU5Z..."
-   				}
-   			}
-   			```
-   
-   	3.  Copy the `token` value shown in the output.
-   
-   	</TabItem>
-   	</Tabs>
-
-   After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
+	<Tabs syncKey="dashPlusAPI">
+	<TabItem label="Dashboard">
+	1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
+	2. Select a `cloudflared` tunnel and select **Edit**.
+	3. Select **Refresh token**.
+	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+
+	</TabItem>
+	<TabItem label="API">
+		1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
+
+				```sh
+				openssl rand -base64 32
+				```
+
+				```sh output
+				AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
+				```
+
+	2.  Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
+
+			<APIRequest
+				path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+				method="PATCH"
+				json={{
+					name: "Example tunnel",
+					tunnel_secret: "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=",
+				}}
+			/>
+
+			```sh output {18}
+			{
+				"success": true,
+				"errors": [],
+				"messages": [],
+				"result": {
+					"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
+					"account_tag": "699d98642c564d2e855e9661899b7252",
+					"created_at": "2024-12-04T22:03:26.291225Z",
+					"deleted_at": null,
+					"name": "Example tunnel",
+					"connections": [],
+					"conns_active_at": null,
+					"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
+					"tun_type": "cfd_tunnel",
+					"metadata": {},
+					"status": "inactive",
+					"remote_config": true,
+					"token": "eyJhIjoiNWFiNGU5Z..."
+				}
+			}
+			```
+
+	3.  Copy the `token` value shown in the output.
+
+	</TabItem>
+	</Tabs>
+
+	After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
 2. On half of your `cloudflared` replicas, reinstall the `cloudflared` service with the new token. For example, on a Linux host:
 
    ```sh
-    sudo cloudflared service uninstall
+	 sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
@@ -140,9 +140,9 @@ To rotate a tunnel token:
 
    While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
-4. Wait 10 minutes for traffic to route through the new connectors.
+5. Wait 10 minutes for traffic to route through the new connectors.
 
-5. Repeat steps 2, 3, and 4 for the second half of the replicas.
+6. Repeat steps 2, 3, and 4 for the second half of the replicas.
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
@@ -163,7 +163,7 @@ If your tunnel token is compromised, we recommend taking the following steps:
 3. On each `cloudflared` replica, update `cloudflared` to use the new token. For example, on a Linux host:
 
    ```sh
-    sudo cloudflared service uninstall
+	 sudo cloudflared service uninstall
    sudo cloudflared service install <NEW_TOKEN>
    ```
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
index c545b148afb32c3..6840e8a166897b2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters.mdx
@@ -14,21 +14,15 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/run-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		usageMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		tunnelWithFirewallURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
-		tunnelPermissionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
-		createRemoteTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
-		faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/",
-	}}
+  file="tunnel/run-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    usageMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    tunnelWithFirewallURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#region-us",
+    tunnelPermissionsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-permissions/",
+    createRemoteTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/",
+    faqURL: "/cloudflare-one/faq/cloudflare-tunnels-faq/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
index 81564acce0df5df..0a7cbccf1dcbcbc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements.mdx
@@ -32,10 +32,7 @@ When `cloudflared` receives a request from a device, it uses the ports on the ho
 - `cloudflared` should be deployed on a dedicated host machine. This model is typically appropriate, but there may be serverless or clustered workflows where a dedicated host is not possible.
 - The host machine should allocate 50,000 ports to be available for use by the `cloudflared` service. The remaining ports are reserved for system administrative processes.
 
-<Render
-	file="tunnel/availability/port-configuration"
-	product="cloudflare-one"
-/>
+<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
 
 ### Private DNS
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
index 73321967dcd5876..5954dd3c2bbff27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx
@@ -35,29 +35,22 @@ Ensure port `7844` is allowed for both TCP and UDP protocols (for `http2` and `q
 <Render file="tunnel/firewall/required-ports" product="cloudflare-one" />
 
 #### SNI-enforcing firewalls
-
 <Render file="tunnel/firewall/sni-hostnames" product="cloudflare-one" />
 
 ### Region US
 
 <Render
-	file="tunnel/firewall/us-region-ports"
-	product="cloudflare-one"
-	params={{
-		regionURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region",
-	}}
+  file="tunnel/firewall/us-region-ports"
+  product="cloudflare-one"
+  params={{ regionURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#region" }}
 />
 
 ### Region FedRAMP High
 
 <Render
-	file="tunnel/firewall/fedramp-high-ports"
-	product="cloudflare-one"
-	params={{
-		tunnelTokenURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/",
-	}}
+  file="tunnel/firewall/fedramp-high-ports"
+  product="cloudflare-one"
+  params={{ tunnelTokenURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions/" }}
 />
 
 ### Optional
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
index a02784740a89917..57b31886ddd0a26 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Deploy Cloudflare Tunnel in your environment — from cloud VMs to Kubernetes clusters, with Infrastructure as Code support.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
index 2e42733bf93cb6e..1c27eaad46459cc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
@@ -86,6 +86,7 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
+
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
index 6dad6b29b8df2dc..60b688f0c55e95a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/tunnel-useful-commands.mdx
@@ -31,12 +31,12 @@ import { Render } from "~/components";
 
 ## Manage private networks
 
-| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Command                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `cloudflared tunnel route ip add <IP/CIDR> <NAME or UUID>` | Adds any network route space (represented as a CIDR) to your routing table. That network space becomes reachable for requests egressing from a user's machine as long as it is using the Cloudflare One Client and is enrolled in the same account that is running the tunnel chosen here. Further, those requests will be proxied to the specified tunnel, and reach an IP in the given CIDR, as long as that IP is reachable from the tunnel. To assign the IP route to a specific [Virtual Network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/), use the `--vnet` option. |
-| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `cloudflared tunnel route ip show` (or `list`)             | Shows your organization's private routing table. You can use additional flags to filter the results.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | `cloudflared tunnel route ip delete`                       | Deletes the row for a given CIDR from your routing table. That portion of your network will no longer be reachable by the Cloudflare One Client.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `cloudflared tunnel route ip get <IP/CIDR>`                | Checks which row of the routing table will be used to proxy a given IP. This helps check and validate your configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `cloudflared tunnel vnet add <NAME or UUID>`               | Creates a Virtual Network to which IP routes can be assigned. To make this Virtual Network the default for your Zero Trust organization, use the `-d` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `cloudflared tunnel vnet delete <NAME or UUID>`            | Deletes the Virtual Network with the given name or UUID. Before you can delete a Virtual Network, you must first delete all IP routes assigned to the Virtual Network.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `cloudflared tunnel vnet list`                             | Displays all active Virtual Networks, the default Virtual Network, and their creation times.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
index 75fdb3581cab640..e79d92232542499 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/copyrights.mdx
@@ -7,10 +7,11 @@ sidebar:
   order: 102
 head: []
 description: View associated copyrights.
----
 
 ---
 
+***
+
 [https://github.com/BurntSushi/toml](https://github.com/BurntSushi/toml)
 
 The MIT License (MIT)
@@ -35,7 +36,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/Sirupsen/logrus](https://github.com/Sirupsen/logrus)
 
@@ -61,7 +62,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/beorn7/perks/](https://github.com/beorn7/perks/)
 
@@ -86,7 +87,7 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
----
+***
 
 [https://github.com/certifi/gocertifi](https://github.com/certifi/gocertifi)
 
@@ -94,7 +95,7 @@ This Source Code Form is subject to the terms of the Mozilla Public License,
 v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain
 one at [http://mozilla.org/MPL/2.0/](http://mozilla.org/MPL/2.0/).
 
----
+***
 
 [https://github.com/coreos/go-oidc/](https://github.com/coreos/go-oidc/)
 [https://github.com/coreos/go-systemd/](https://github.com/coreos/go-systemd/)
@@ -305,7 +306,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/facebookgo/grace](https://github.com/facebookgo/grace)
 
@@ -318,14 +319,14 @@ Copyright (c) 2015, Facebook, Inc. All rights reserved.
 Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 
-- Redistributions of source code must retain the above copyright notice, this
+* Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-- Redistributions in binary form must reproduce the above copyright notice,
+* Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-- Neither the name Facebook nor the names of its contributors may be used to
+* Neither the name Facebook nor the names of its contributors may be used to
   endorse or promote products derived from this software without specific
   prior written permission.
 
@@ -340,7 +341,7 @@ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/getsentry/raven-go](https://github.com/getsentry/raven-go)
 
@@ -351,13 +352,13 @@ Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
 met:
 
-- Redistributions of source code must retain the above copyright
+* Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
-- Redistributions in binary form must reproduce the above
+* Redistributions in binary form must reproduce the above
   copyright notice, this list of conditions and the following disclaimer
   in the documentation and/or other materials provided with the
   distribution.
-- Neither the name of Apollic Software, LLC nor the names of its
+* Neither the name of Apollic Software, LLC nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 
@@ -373,7 +374,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/glycerine/rbtree](https://github.com/glycerine/rbtree)
 
@@ -397,7 +398,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/golang/protobuf](https://github.com/golang/protobuf)
 
@@ -433,7 +434,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
 [https://github.com/lib/pq](https://github.com/lib/pq)
 
@@ -446,9 +447,9 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
----
+***
 
-[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\_protobuf\_extensions/pbutil)
+[https://godoc.org/github.com/matttproud/golang\\\_protobuf\\\_extensions/pbutil](https://godoc.org/github.com/matttproud/golang\\_protobuf\\_extensions/pbutil)
 
 ```
                              Apache License
@@ -658,7 +659,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/mitchellh/go-homedir](https://github.com/mitchellh/go-homedir)
 
@@ -684,7 +685,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 
----
+***
 
 [https://github.com/pkg/errors](https://github.com/pkg/errors)
 
@@ -694,10 +695,10 @@ All rights reserved.
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
 
-- Redistributions of source code must retain the above copyright notice, this
+* Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-- Redistributions in binary form must reproduce the above copyright notice,
+* Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
@@ -712,10 +713,10 @@ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
----
+***
 
-[https://github.com/prometheus/client_golang](https://github.com/prometheus/client_golang)
-[https://github.com/prometheus/client_model](https://github.com/prometheus/client_model)
+[https://github.com/prometheus/client\_golang](https://github.com/prometheus/client_golang)
+[https://github.com/prometheus/client\_model](https://github.com/prometheus/client_model)
 [https://github.com/prometheus/common](https://github.com/prometheus/common)
 [https://github.com/prometheus/procfs](https://github.com/prometheus/procfs)
 
@@ -927,7 +928,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://github.com/urfave/cli](https://github.com/urfave/cli)
 
@@ -953,7 +954,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
----
+***
 
 [https://github.com/go-yaml/yaml](https://github.com/go-yaml/yaml)
 
@@ -1165,7 +1166,7 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 
----
+***
 
 [https://zombiezen.com/go/capnproto2](https://zombiezen.com/go/capnproto2)
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
index 6299a916a068aac..c3079b110404278 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/license.mdx
@@ -6,6 +6,7 @@ products:
 title: License
 sidebar:
   order: 51
+
 ---
 
 Apache License
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
index 1004578cbdb1b59..e880dc05a8955b9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api.mdx
@@ -30,12 +30,12 @@ Follow this guide to set up a Cloudflare Tunnel using the API.
 Make a `POST` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/create/) endpoint:
 
 <APIRequest
-	path="/accounts/{account_id}/cfd_tunnel"
-	method="POST"
-	json={{
-		name: "api-tunnel",
-		config_src: "cloudflare",
-	}}
+  path="/accounts/{account_id}/cfd_tunnel"
+  method="POST"
+  json={{
+    name: "api-tunnel",
+    config_src: "cloudflare",
+  }}
 />
 
 ```sh output
@@ -80,47 +80,46 @@ Before you publish an application through your tunnel, you must:
 
 Follow these steps to publish an application to the Internet. If you are looking to connect a private resource, skip to the [Connect a network](#3b-connect-a-network) section.
 
-1.  Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
-
-        <APIRequest
-        	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
-        	method="PUT"
-        	json={{
-        		config: {
-        			ingress: [
-        				{
-        					hostname: "app.example.com",
-        					service: "http://localhost:8001",
-        					originRequest: {},
-        				},
-        				{
-        					service: "http_status:404",
-        				},
-        			],
-        		},
-        	}}
-        />
-
-    :::note
-    If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-    :::
-
-    Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
-
-2.  [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
-
-        <APIRequest
-        	path="/zones/{zone_id}/dns_records"
-        	method="POST"
-        	json={{
-        		type: "CNAME",
-        		proxied: true,
-        		name: "app.example.com",
-        		content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
-        	}}
-        />
-
-    This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
+1. Make a [`PUT` request](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/update/) to route your [local service URL](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) to a public hostname. For example,
+
+		<APIRequest
+			path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}/configurations"
+			method="PUT"
+			json={{
+				config: {
+					ingress: [
+						{
+							hostname: "app.example.com",
+							service: "http://localhost:8001",
+							originRequest: {},
+						},
+						{
+							service: "http_status:404",
+						},
+					],
+				},
+			}}
+		/>
+   :::note
+   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+   :::
+
+   Your ingress rules must include a catch-all rule at the end. In this example, `cloudflared` will respond with a 404 status code when the request does not match any of the previous hostnames.
+
+2. [Create a DNS record](/api/resources/dns/subresources/records/methods/create/) for your application:
+
+		<APIRequest
+			path="/zones/{zone_id}/dns_records"
+			method="POST"
+			json={{
+				type: "CNAME",
+				proxied: true,
+				name: "app.example.com",
+				content: "c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com",
+			}}
+		/>
+
+   This DNS record allows Cloudflare to proxy `app.example.com` traffic to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`).
 
 This application will be publicly available on the Internet once you [run the tunnel](#4-install-and-run-the-tunnel). To allow or block specific users, [create an Access application](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/).
 
@@ -129,13 +128,13 @@ This application will be publicly available on the Internet once you [run the tu
 To connect a private network through your tunnel, [add a tunnel route](/api/resources/zero_trust/subresources/networks/subresources/routes/methods/create/):
 
 <APIRequest
-	path="/accounts/{account_id}/teamnet/routes"
-	method="POST"
-	json={{
-		network: "172.16.0.0/16",
-		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-		comment: "Example private network route",
-	}}
+  path="/accounts/{account_id}/teamnet/routes"
+  method="POST"
+  json={{
+    network: "172.16.0.0/16",
+    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+    comment: "Example private network route",
+  }}
 />
 
 `cloudflared` can now route traffic to these destination IPs. To configure Zero Trust policies and connect as a user, refer to [Connect private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/).
@@ -151,11 +150,11 @@ Install `cloudflared` on your server and run the tunnel using the `token` value
 To check if the tunnel is serving traffic:
 
 <APIRequest
-	path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
-	method="GET"
-	parameters={{
-		tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
-	}}
+  path="/accounts/{account_id}/cfd_tunnel/{tunnel_id}"
+  method="GET"
+  parameters={{
+    tunnel_id: "c1744f8b-faa1-48a4-9e5c-02ac921467fa",
+  }}
 />
 
 ```sh output
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
index 18e2da263fc28c1..87b44a017b40937 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
@@ -18,11 +18,7 @@ Follow this step-by-step guide to create your first [remotely-managed tunnel](/c
 
 ## 1. Create a tunnel
 
-<Stream
-	id="4b75ad2aa58700602e94b148827687a2"
-	title="How to set up Cloudflare Tunnel"
-	thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png"
-/>
+<Stream id="4b75ad2aa58700602e94b148827687a2" title="How to set up Cloudflare Tunnel" thumbnail="https://pub-d9bf66e086fb4b639107aa52105b49dd.r2.dev/tunnel%204_%20set%20up%20tunnel.png" />
 
 <Render file="tunnel/create-tunnel" product="cloudflare-one" />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
index 2482ef654c8cfb8..ca65ff18a9887ff 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Set up your first tunnel
+
 ---
 
-import { DirectoryListing, GlossaryTooltip } from "~/components";
+import { DirectoryListing, GlossaryTooltip } from "~/components"
 
 To create and manage tunnels, you will need to install and authenticate <GlossaryTooltip term="cloudflared"><code>cloudflared</code></GlossaryTooltip> on your origin server. `cloudflared` is what connects your server to Cloudflare's global network.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
index 6dda076ed46e587..017e02c4b363879 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/index.mdx
@@ -13,8 +13,8 @@ tags:
 
 import { Render, Stream } from "~/components";
 
-:::note[Looking to expose public applications?]
-This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel).
+:::note[Looking to expose public applications?] 
+This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to the [Cloudflare Tunnel documentation](/tunnel). 
 :::
 
 Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (`cloudflared`) creates [outbound-only connections](#outbound-only-connections) to Cloudflare's global network. Cloudflare Tunnel can connect HTTP web servers, [SSH servers](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/), [remote desktops](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/), and other protocols safely to Cloudflare. This way, your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
index d346bec2114ef0d..25b86d04e55286d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Monitor tunnels
 sidebar:
   order: 9
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
index 90b446cff03deba..a23a3c04da466a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications.mdx
@@ -6,9 +6,10 @@ products:
 title: Notifications
 sidebar:
   order: 1
+
 ---
 
-import { AvailableNotifications } from "~/components";
+import { AvailableNotifications } from "~/components"
 
 Administrators can receive an alert when Cloudflare Tunnels in an account change their health or deployment status. Notifications can be delivered via email, webhook, and third-party services.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
index e80b571a1bbc009..b2dd6df9595c190 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr.mdx
@@ -24,9 +24,9 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 4. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/) for this tunnel route. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
 
-   :::note
-   To create a new virtual network, select **Manage virtual networks**.
-   :::
+	:::note
+	To create a new virtual network, select **Manage virtual networks**.
+	:::
 
 ## 2. Set up the client
 
@@ -34,11 +34,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ## 3. Route private network IPs through the Cloudflare One Client
 
-<Render
-	file="tunnel/warp-to-tunnel-route-ips"
-	product="cloudflare-one"
-	params={{ one: "private network" }}
-/>
+<Render file="tunnel/warp-to-tunnel-route-ips" product="cloudflare-one" params={{ one: "private network"}}/>
 
 ## 4. (Recommended) Filter network traffic with Gateway
 
@@ -50,7 +46,7 @@ To connect your infrastructure with Cloudflare Tunnel:
 
 ### Zero Trust policies
 
-<Render file="tunnel/catch-all-policy" product="cloudflare-one" />
+<Render file="tunnel/catch-all-policy" product="cloudflare-one"/>
 
 If you have applications clearly defined by IPs or hostnames, we recommend [creating an Access application](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) and managing user access alongside your SaaS and other web apps. Alternatively, if you prefer to secure a private network using a traditional firewall model, you can build Gateway network and DNS policies for IP ranges and domains.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
index 03dd3b5c2c280f9..9322c427b9241f5 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/index.mdx
@@ -18,6 +18,5 @@ On the client side, end users connect to Cloudflare's global network using the C
 ![Diagram displaying connections between a device, Cloudflare, and a private network.](~/assets/images/cloudflare-one/connections/private-ips-diagram.png)
 
 To enable remote access to your private network, refer to the following guides:
-
 - [**Connect a private hostname**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/): Route network traffic to an internal application using its hostname.
-- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
+- [**Connect an IP/CIDR**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/): Route traffic to an internal IP address or CIDR range.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
index f4e9849be0a0224..180ab16892b1bcf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
@@ -10,7 +10,7 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 By default, all DNS requests on the user device are resolved by Cloudflare's [public DNS resolver](/1.1.1.1/) except for common top level domains used for local resolution (such as `localhost`). You can connect an internal DNS resolver to Cloudflare and use it to resolve non-publicly routed domains.
 
@@ -18,23 +18,24 @@ By default, all DNS requests on the user device are resolved by Cloudflare's [pu
 
 To resolve private DNS queries:
 
-1.  [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
+1. [Connect your private network](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/) with Cloudflare Tunnel.
 
-2.  Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
+2. Under **Networks** > **Routes**, verify that the IP address of your internal DNS resolver is included in the tunnel.
 
-        :::note
+		:::note
 
-        Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
+		Ensure that **Split Tunnels** are configured to [include traffic to private IPs and hostnames](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-the-cloudflare-one-client).
 
-        :::
+		:::
 
-3.  Route specific DNS queries to your internal DNS resolver using one of the following options:
-    - [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
-    - Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
+3. Route specific DNS queries to your internal DNS resolver using one of the following options:
 
-4.  [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
+	- [Create a Local Domain Fallback entry](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) that points to the internal DNS resolver. For example, you can instruct the Cloudflare One Client to resolve all requests for `myorg.privatecorp` through an internal resolver at `10.0.0.25` rather than attempting to resolve this publicly.
+	- Alternatively, [create a resolver policy](/cloudflare-one/traffic-policies/resolver-policies/#create-a-resolver-policy) that points to the internal DNS resolver. <Render file="gateway/resolver-policies-intro" product="cloudflare-one"/>
 
-5.  Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
+4. [Enable the Gateway proxy](/cloudflare-one/traffic-policies/proxy/#turn-on-the-gateway-proxy) for TCP and UDP.
+
+5. Finally, ensure that your tunnel uses QUIC as the default [transport protocol](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol). This will enable `cloudflared` to proxy UDP-based traffic which is required in most cases to resolve DNS queries.
 
 The Cloudflare One Client will now send DNS queries to your internal DNS resolver for resolution. To learn more, refer to [How the Cloudflare One Client handles DNS requests](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/#how-the-warp-client-handles-dns-requests).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
index 99d934881a0f10d..98430c7fdc1b90a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns.mdx
@@ -17,14 +17,13 @@ import { Render } from "~/components";
 ## Create a DNS record
 
 <Render
-	file="tunnel/dns-records-create"
-	product="cloudflare-one"
-	params={{
-		certPemURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem",
-	}}
+  file="tunnel/dns-records-create"
+  product="cloudflare-one"
+  params={{
+    certPemURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/local-tunnel-terms/#certpem"
+  }}
 />
 
 ## Cloudflare settings
 
-<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
+<Render file="tunnel/dns-cloudflare-settings" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
index f658fb166750775..17cb132130adfc8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols.mdx
@@ -15,12 +15,10 @@ import { Render } from "~/components";
 When you [add a published application route](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application) to a Cloudflare Tunnel, you are instructing Cloudflare to proxy requests for your public hostname to a service running privately behind `cloudflared`.
 
 <Render
-	file="tunnel/protocols-table"
-	product="cloudflare-one"
-	params={{
-		disableTlsVerificationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
-		locallyManagedTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications",
-	}}
+  file="tunnel/protocols-table"
+  product="cloudflare-one"
+  params={{
+    disableTlsVerificationURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/#notlsverify",
+    locallyManagedTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-published-applications"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
index cbb16832f033141..05468c98e98ec02 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
@@ -25,14 +25,12 @@ When you add a [published application route](/cloudflare-one/networks/connectors
 ### Create a load balancer
 
 <Render
-	file="tunnel/availability/load-balancer-create"
-	product="cloudflare-one"
-	params={{
-		publishedAppRouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-		tunnelIdLocation:
-			"the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**",
-	}}
+  file="tunnel/availability/load-balancer-create"
+  product="cloudflare-one"
+  params={{
+    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
+    tunnelIdLocation: "the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**"
+  }}
 />
 
 Refer to the [Load Balancing documentation](/load-balancing/) for more details on load balancer settings and configurations.
@@ -81,7 +79,6 @@ graph LR
 ```
 
 As shown in the diagram, a typical setup includes:
-
 - A dedicated Cloudflare Tunnel per data center.
 - One load balancer pool per tunnel. The load balancer hostname is set to the user-facing application hostname (`app.example.com`).
 - One load balancer endpoint per pool. The endpoint host header is set to the `cloudflared` published application hostname (`server1.example.com`)
@@ -149,12 +146,12 @@ Here is an example of what your DNS records will look like before and after sett
 | CNAME | app1 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app2 | `<UUID_1>.cfargotunnel.com` |
 | CNAME | app1 | `<UUID_2>.cfargotunnel.com` |
-| CNAME | app2 | `<UUID_2>.cfargotunnel.com` |
+| CNAME | app2 | `<UUID_2>.cfargotunnel.com`  |
 
 **After**:
 | Type | Name | Content |
 | ---- | ---- | ------- |
-| LB | `lb.example.com` | n/a |
+| LB   | `lb.example.com` | n/a |
 | CNAME | app1 | `lb.example.com` |
 | CNAME | app2 | `lb.example.com` |
 
@@ -163,12 +160,11 @@ Here is an example of what your DNS records will look like before and after sett
 ### Monitors and TCP tunnel origins
 
 <Render
-	file="tunnel/availability/load-balancer-tcp-monitors"
-	product="cloudflare-one"
-	params={{
-		publishedAppRouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application",
-	}}
+  file="tunnel/availability/load-balancer-tcp-monitors"
+  product="cloudflare-one"
+  params={{
+    publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application"
+  }}
 />
 
 ### Session affinity and replicas
@@ -178,10 +174,9 @@ The load balancer does not distinguish between [replicas](/cloudflare-one/networ
 ### Local connection preference
 
 <Render
-	file="tunnel/availability/load-balancer-local-connection"
-	product="cloudflare-one"
-	params={{
-		replicasURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/",
-	}}
+  file="tunnel/availability/load-balancer-local-connection"
+  product="cloudflare-one"
+  params={{
+    replicasURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
index ee3c9509de79961..d9c0787deeffdfa 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
@@ -74,4 +74,5 @@ If you see an error with the title `This site can't provide a secure connection`
 
 If you added a [multi-level subdomain](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-connect-an-application) as Cloudflare's Universal certificate will not cover the public hostname by default.
 
+
 For more information on Tunnel errors, view your [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) or [contact Cloudflare Support](/support/contacting-cloudflare-support/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
index 0c3a0e8a6720af6..04c3693aabbaeb1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs.mdx
@@ -28,53 +28,44 @@ The steps for getting diagnostic logs depend on your `cloudflared` deployment en
 These instructions apply to remotely-managed and locally-managed tunnels running directly on the host machine.
 
 <Render
-	file="tunnel/diagnostics/host-environment"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/host-environment"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#configure-the-metrics-server-address"
+  }}
 />
 
 ### Docker
 
 <Render
-	file="tunnel/diagnostics/docker"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		defaultMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/docker"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
+  }}
 />
 
 ### Kubernetes
 
 <Render
-	file="tunnel/diagnostics/kubernetes"
-	product="cloudflare-one"
-	params={{
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
-		defaultMetricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address",
-	}}
+  file="tunnel/diagnostics/kubernetes"
+  product="cloudflare-one"
+  params={{
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/",
+    defaultMetricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#default-metrics-server-address"
+  }}
 />
 
 ## cloudflared-diag files
 
 <Render
-	file="tunnel/diagnostics/tunnel-diag-file"
-	product="cloudflare-one"
-	params={{
-		runParametersURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
-		logsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-		metricsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
-		loglevelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server",
-	}}
+  file="tunnel/diagnostics/tunnel-diag-file"
+  product="cloudflare-one"
+  params={{
+    runParametersURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/",
+    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+    metricsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/#available-metrics",
+    loglevelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
index 61105e303be197e..281adab55837939 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 10
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore resources to help you resolve issues with Cloudflare Tunnel connectivity and configuration.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
index 19b86f3981d6630..465c95783571898 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/index.mdx
@@ -7,11 +7,12 @@ title: Use cases
 hidden: false
 sidebar:
   order: 4
+
 ---
 
 Cloudflare Tunnel creates a secure, outbound-only connection between your services and Cloudflare by deploying a lightweight connector in your environment. Here is how to use tunnels with some specific services:
 
-- [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
-- [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
-- [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
-- [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
+* [SSH](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/)
+* [RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/)
+* [SMB](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/)
+* [gRPC](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/grpc/)
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
index 8ae62963190d27f..c39aca829aac5a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/index.mdx
@@ -17,4 +17,4 @@ Cloudflare offers three ways to secure RDP:
 
 - [Browser-based RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser/)
 - [RDP with Cloudflare One Client](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client/)
-- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
+- [RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/)
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
index e9787ea4da56ea5..7830923733b5e59 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-device-client.mdx
@@ -57,7 +57,7 @@ By default, Internet Explorer will be installed and configured in [Enhanced Secu
 
 <Render file="tunnel/connect-private-network" product="cloudflare-one" />
 
-3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the **Internal IP** of the VM instance.
+3. In the **CIDR** tab for the tunnel, enter the private IP or CIDR address of your server. In GCP, the server IP is the  **Internal IP** of the VM instance.
 
 4. (Optional) [Set up Zero Trust policies](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#4-recommended-filter-network-traffic-with-gateway) to fine-tune access to your server.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
index de8d6a6065a81b3..dfb0e2feed3b4db 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx
@@ -31,159 +31,160 @@ There are a number of different VNC server versions, deployments, and instances.
 
 For demonstration purposes, we will create a TightVNC server on an Ubuntu virtual machine (VM) hosted in Google Cloud Project (GCP). We will configure the VNC server to run XFCE, a lightweight desktop environment suitable for remote access. If you already have a VNC server installed, you can skip this step and [go to Step 2](#2-connect-the-server-to-cloudflare).
 
-1.  Open a terminal window for your Ubuntu VM.
+1. Open a terminal window for your Ubuntu VM.
 
-2.  Install XFCE and TightVNC by running the following command:
+2. Install XFCE and TightVNC by running the following command:
 
-        ```sh
-        sudo apt update
-        sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
+		```sh
+		sudo apt update
+		sudo apt install xfce4 xfce4-goodies dbus-x11 tightvncserver -y
 
-        ```
+		```
 
-        This command installs the desktop, some helpful utilities, and the VNC server software.
+		This command installs the desktop, some helpful utilities, and the VNC server software.
 
-3.  To initialize the VNC server:
-    1. Create a VNC server instance:
+3. To initialize the VNC server:
 
-       ```sh
-       vncserver
-       ```
+	1. Create a VNC server instance:
 
-    2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
+		```sh
+		vncserver
+		```
 
-       TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
+	2. You will be prompted to set a password. This password will be used to connect to your VNC server. It is limited to 8 characters.
 
-    3. You will be asked if you want to create a view-only password. You can press `n` for no.
+		TightVNC will now create configuration files and start a VNC session on display `:1` (which uses port `5901`).
 
-    4. Kill this initial session so that you can edit its configuration:
+	3. You will be asked if you want to create a view-only password. You can press `n` for no.
 
-       ```sh
-       vncserver -kill :1
-       ```
+	4. Kill this initial session so that you can edit its configuration:
 
-4.  Configure VNC to launch the XFCE desktop:
-    1. Create a VNC configuration directory if it is missing:
+		```sh
+		vncserver -kill :1
+		```
+4. Configure VNC to launch the XFCE desktop:
 
-    ```sh
-    mkdir -p ~/.vnc
-    ```
+	1. Create a VNC configuration directory if it is missing:
 
-    2. Open the `xstartup` file using a text editor. For example,
+	```sh
+	mkdir -p ~/.vnc
+	```
 
-    ```sh
-    vim ~/.vnc/xstartup
-    ```
+	2. Open the `xstartup` file using a text editor. For example,
 
-    3. Update the file to the following configuration:
+	```sh
+	vim ~/.vnc/xstartup
+	```
 
-    ```bash
-    #!/bin/sh
-    unset SESSION_MANAGER
-    unset DBUS_SESSION_BUS_ADDRESS
-    startxfce4
-    ```
+	3. Update the file to the following configuration:
 
-    4. Make the file executable:
+	```bash
+	#!/bin/sh
+	unset SESSION_MANAGER
+	unset DBUS_SESSION_BUS_ADDRESS
+	startxfce4
+	```
 
-    ```sh
-    chmod +x ~/.vnc/xstartup
-    ```
+	4. Make the file executable:
 
-5.  Start the VNC server again:
+	```sh
+	chmod +x ~/.vnc/xstartup
+	```
 
-    ```sh
-    vncserver -localhost :1
-    ```
+5. Start the VNC server again:
+	```sh
+	vncserver -localhost :1
+	```
 
-    The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
+	The `-localhost` flag ensures the VNC server only listens for connections from the VM itself, not from the public Internet. Your VNC server is now running on port `5901`, but it is only accessible from `localhost` (`127.0.0.1`) inside the VM.
 
-6.  (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
-    1. Open a terminal on the client machine.
+6. (Recommended) Test the VNC server with an existing VNC client to verify any missing packages or configuration changes. For example, to test a VNC server hosted on GCP:
 
-    2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
+	1. Open a terminal on the client machine.
 
-       ```sh
-       gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
-       ```
+	2. Connect to the VNC server over SSH, forwarding your local port `5901` to the VNC server's listening port:
 
-    3. Open your preferred VNC viewer application.
+		```sh
+		gcloud compute ssh [YOUR_VM_NAME] --zone=[YOUR_ZONE] -- -L 5901:localhost:5901
+		```
 
-    4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
+	3. Open your preferred VNC viewer application.
 
-    You should see the Ubuntu VM desktop.
+	4. In the VNC viewer, connect to the address `localhost:5901` and enter your VNC server password.
 
-7.  (Optional) Configure the VNC server to start on boot:
-    1. Find the full path to the `vncserver` command:
+	You should see the Ubuntu VM desktop.
 
-       ```sh
-       which vncserver
-       ```
+7. (Optional) Configure the VNC server to start on boot:
 
-       ```sh output
-       /usr/bin/vncserver
-       ```
+	1. Find the full path to the `vncserver` command:
 
-    2. Create a new service configuration file:
+		```sh
+		which vncserver
+		```
+		```sh output
+		/usr/bin/vncserver
+		```
+	2. Create a new service configuration file:
 
-    ```sh
-    sudo vim /etc/systemd/system/vncserver@.service
-    ```
+	```sh
+	sudo vim /etc/systemd/system/vncserver@.service
+	```
 
-    3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
+	3. Copy and paste the following content. Replace `[YOUR_USERNAME]` with the VNC server user. If needed, update `/usr/bin/vncserver` to your `vncserver` path.
 
-       ```toml
-       [Unit]
-       Description=Start TightVNC server at startup
-       After=syslog.target network.target
+		```toml
+		[Unit]
+		Description=Start TightVNC server at startup
+		After=syslog.target network.target
 
-       [Service]
-       Type=forking
-       User=[YOUR_USERNAME]
-       WorkingDirectory=/home/[YOUR_USERNAME]
+		[Service]
+		Type=forking
+		User=[YOUR_USERNAME]
+		WorkingDirectory=/home/[YOUR_USERNAME]
 
-       PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
+		PIDFile=/home/[YOUR_USERNAME]/.vnc/%H:%i.pid
 
-       ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
-       ExecStart=/usr/bin/vncserver -localhost :%i
-       ExecStop=/usr/bin/vncserver -kill :%i
+		ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1
+		ExecStart=/usr/bin/vncserver -localhost :%i
+		ExecStop=/usr/bin/vncserver -kill :%i
 
-       [Install]
-       WantedBy=multi-user.target
-       ```
+		[Install]
+		WantedBy=multi-user.target
+		```
 
-       4. Reload `systemd` to read in the new service file:
+		4. Reload `systemd` to read in the new service file:
 
-       ```sh
-       sudo systemctl daemon-reload
-       ```
+		```sh
+		sudo systemctl daemon-reload
+		```
 
-       5. Enable the service to start at boot:
+		5. Enable the service to start at boot:
 
-       ```sh
-       sudo systemctl enable vncserver@1.service
-       ```
+		```sh
+		sudo systemctl enable vncserver@1.service
+		```
 
-       The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
-       6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
+		The `1` variable configures the VNC service to use display `:1` (which runs on port `5901`).
 
-       ```sh
-       sudo loginctl enable-linger [YOUR_USERNAME]
-       ```
+		6. By default, `systemd` user services only run when that user is logged in. To allow your VNC service to start on boot (before you log in), enable user linger for your user:
 
-       7. Start the service:
+		```sh
+		sudo loginctl enable-linger [YOUR_USERNAME]
+		```
 
-       ```sh
-       sudo systemctl start vncserver@1.service
-       ```
+		7. Start the service:
 
-       8. Check its status:
+		```sh
+		sudo systemctl start vncserver@1.service
+		```
 
-       ```sh
-       sudo systemctl status vncserver@1.service
-       ```
+		8. Check its status:
 
-       The VNC server will now start automatically every time the VM boots.
+		```sh
+		sudo systemctl status vncserver@1.service
+		```
+
+		The VNC server will now start automatically every time the VM boots.
 
 ## 2. Connect the server to Cloudflare
 
@@ -197,7 +198,7 @@ For demonstration purposes, we will create a TightVNC server on an Ubuntu virtua
 
 5. For **Service**, select _TCP_ and enter `localhost:<5901>`. If the VNC server is on a different machine from where you installed the tunnel, enter `<SERVER_IP>:5901`.
 
-   Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
+	Replace `5901` with your VNC server's listening port. To determine your VNC listening port, run `sudo ss -lnpt` and look for `vnc` in the list of processes.
 
 6. Save the route.
 
@@ -219,10 +220,7 @@ Create a Cloudflare Access application that users can access through their brows
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-   <Render
-   	file="access/self-hosted-app/browser-rendering-policies"
-   	product="cloudflare-one"
-   />
+	<Render file="access/self-hosted-app/browser-rendering-policies" product="cloudflare-one" />
 
 7. Select **Create**.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
index 7f5b8371def9c4d..621709d181b4715 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/index.mdx
@@ -6,8 +6,7 @@ products:
 sidebar:
   order: 10
 head: []
-description:
-  Use Cloudflare WAN's different analytic options for an overview of the
+description: Use Cloudflare WAN's different analytic options for an overview of the
   performance of your sites, or to troubleshoot potential issues.
 tags:
   - Analytics
@@ -17,21 +16,15 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		networkAnalyticsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		traceRoutes:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
-		graphQlTunnelBandwidthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/",
-	}}
+		networkAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		traceRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/traceroutes/",
+		graphQlTunnelBandwidthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		siteAnalyticsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics/"
+		 }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
index f685696ff741fda..d3c2fff924b3af7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -15,11 +15,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/netflow"
-	product="networking-services"
-	params={{
-		breakoutTrafficURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
-	}}
-/>
+<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" params={{ breakoutTrafficURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/" }} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
index 81bc27fef3b688e..4694b2188d10e76 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics.mdx
@@ -15,10 +15,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN",
+		magicWord: "CF1 Cloudflare WAN"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
index 0a93283b55966af..c7a0918e9e4281f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
index 12fc47ede0c7643..761d5ad3c83ef95 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -12,10 +12,9 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
index a7cdd1152a38d1e..6c2c604b49fd3c4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -12,10 +12,8 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }}
-/>
+	params={{ productName: "Cloudflare WAN" }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
index 294f9511dcdaaa2..9a1e57ebda7c9dd 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/analytics/site-analytics.mdx
@@ -13,21 +13,18 @@ tags:
   - Analytics
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions:
-			"Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions: "Refer to [Set up a site](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "CF1 Cloudflare WAN",
 		networkOverviewPageName: "Network visibility",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
-	}}
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
+		}}
 />
 
 ### Set thresholds for site health
@@ -37,7 +34,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index e5c5a9d02461bc1..e934890d0601507 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,59 +11,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "hardware",
-		productName: "Cloudflare One Appliance",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "CF1 Cloudflare WAN",
-		sfpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-		wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-		lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
-		noConnectorShows:
-			"You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage: "The Connector is shipped to you deactivated",
-		hardSoftConn:
-			"You need to deploy two Connectors in your premises before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		referenceInformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "hardware",
+	productName: "Cloudflare One Appliance",
+	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "CF1 Cloudflare WAN",
+	sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+	wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+	lan: "refers to the physical Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/) for more information on the hardware supported.",
+	noConnectorShows: "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.",
+	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "The Connector is shipped to you deactivated",
+	hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+  maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index 7d8436c9226ce40..e8ca4f7240d425e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,8 +4,10 @@ description: Reference information for SFP+ port information in Zero Trust netwo
 products:
   - cloudflare-one
 title: SFP+ port information
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info" product="networking-services" />
+<Render file="mconn/sfp-port-info"
+	product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
index 5299a10b9e18f37..6a1b94bdb249832 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance.mdx
@@ -10,56 +10,34 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "virtual",
-		productName: "Cloudflare One Appliance",
-		productNameVirtual: "Virtual Appliance",
-		maintenanceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "CF1 Cloudflare WAN",
-		wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
-		lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
-		noConnectorShows:
-			"For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage: "Virtual Appliance is deactivated after you install it",
-		hardSoftConn:
-			"You need to install two Virtual Appliances before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
-		referenceInformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "virtual",
+	productName: "Cloudflare One Appliance",
+	productNameVirtual: "Virtual Appliance",
+	maintenanceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "CF1 Cloudflare WAN",
+	wan: "needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
+	lan: "needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
+	noConnectorShows: "For a Virtual Appliance to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Appliance Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
+	networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "Virtual Appliance is deactivated after you install it",
+	hardSoftConn: "You need to install two Virtual Appliances before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/",
+  referenceInformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
index c0051513debf6e3..ffd0a4c4b645784 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/",
+		troubleshootingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
index cb114ce2b99fa6c..fb436734ed7d217 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,12 +15,9 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Virtual Appliance",
-		virtualUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
+		virtualUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index c7cbae7c3ceabbf..ac563378234270b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -14,9 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-	}}
-/>
+		hardwareConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+		}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
index 6bcfc54764da629..35e5bf0f59c7313 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/deactivate-appliance.mdx
@@ -6,6 +6,7 @@ products:
 title: Deactivate Connector
 sidebar:
   order: 8
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
index 490ed326c212d3f..f2b21ce17eccf65 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat.mdx
@@ -6,6 +6,7 @@ products:
 title: Heartbeat
 sidebar:
   order: 9
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 630305e6d60c767..922634423e75753 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
index 056b0ca5a650163..c7b5151598427ee 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window.mdx
@@ -6,6 +6,7 @@ title: Interrupt window
 description: Learn how to set up when Connector can update its systems.
 sidebar:
   order: 10
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 98554bc18b3cf72..3949eb19c151c2e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -15,5 +15,5 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-	}}
+		}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 3a9310c33020487..b7f774b674a7b81 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,16 +9,12 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "breakout",
-		featureName: "Breakout traffic",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		whatHappensApp:
-			"will now go directly to the Internet and bypass Cloudflare's filtering",
-		dashName: "CF1 Cloudflare WAN",
-	}}
-/>
+	magicWord: "breakout",
+	featureName: "Breakout traffic",
+	trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
+	dashName: "CF1 Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
index 0468257e119128d..b12153e883b952b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx
@@ -4,16 +4,14 @@ description: How Application-aware policies works in Zero Trust networking.
 products:
   - cloudflare-one
 title: Application-aware policies
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/app-aware-policies/overview"
+<Render file="mconn/network-options/app-aware-policies/overview"
 	product="networking-services"
 	params={{
-		gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
-		appTypesGatewayURL:
-			"/cloudflare-one/policies/gateway/application-app-types/",
-	}}
-/>
+	gatewayPoliciesURL: "/cloudflare-one/policies/gateway/",
+	appTypesGatewayURL: "/cloudflare-one/policies/gateway/application-app-types/"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index 5aac85459c295d4..4067d211b871836 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,13 +9,11 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "prioritized",
-		featureName: "Prioritized traffic",
-		whatHappensApp: "is now processed first by Connector",
-		dashName: "CF1 Cloudflare WAN",
-	}}
-/>
+	magicWord: "prioritized",
+	featureName: "Prioritized traffic",
+	whatHappensApp: "is now processed first by Connector",
+	dashName: "CF1 Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index fb14bed9a02c912..2c0fe51a6772f0b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,13 +8,11 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-relay"
+<Render file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni:
-			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
+		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
 	}}
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 54ddbc7c233c16a..c8a992aa8ac61b7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,10 +8,9 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-server"
+<Render file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index 525082ff11a2ee0..a3ba4bd0341904e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,11 +8,9 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
index d3bb4e7b3f2a648..bda0220b0ebbf27 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index bfd8e592fdc15f9..b6dc835b4894396 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,15 +8,11 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/link-aggregation"
+<Render file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 5405768ac68156c..1ccd87afb778419 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,17 +4,14 @@ products:
   - cloudflare-one
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Connector to  re-use address spaces locally.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/nat-subnet"
+<Render file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+	hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+  virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index b5133cb7577975e..43b9ee7508fbdd0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,16 +6,12 @@ title: Network segmentation
 description: Define policies to define if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/network-segmentation"
+<Render file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index 00ebfc4681edb6c..741b251ec5b73f3 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,19 +4,15 @@ products:
   - cloudflare-one
 title: Routed subnets
 description: Learn how to configure routed subnets on a Connector, including setting static routes and next-hop addresses for complex LAN setups.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/routed-subnets"
+<Render file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+		netSubnetURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
index be5fdb923289884..63e642f8fee211d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/reference.mdx
@@ -16,28 +16,17 @@ import { Render } from "~/components";
 	params={{
 		dashName: "CF1 Cloudflare WAN",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		hardConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-		haSetupURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
-		ecmpRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		multipleWansURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
-		sfpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+		hardConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		haSetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-high-availability-configuration",
+		ecmpRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+		multipleWansURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-wan",
+		sfpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
 		vlanIdURL: "#vlan-id",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		hcFrequencyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		dhcpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
-		routedSubnetsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		networkSegmentationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		hcFrequencyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		dhcpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/dhcp/",
+		routedSubnetsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+		networkSegmentationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/network-segmentation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index bec67a3bb4ce2d5..3806aad41029a92 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -17,11 +17,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "CF1 Cloudflare WAN",
-		activateURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		activateURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
index 854c24e84e725b5..5c087c6432ea87f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx
@@ -16,14 +16,12 @@ import { Render } from "~/components";
 	params={{
 		dashInfo:
 			"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
-		graphQL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
+		graphQL: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/query-tunnel-health/",
 		notificationsPath:
 			"[notifications wizard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		magicWord: "CF1 Cloudflare WAN",
+		networkAnalytics: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		magicWord: "CF1 Cloudflare WAN"
 	}}
 />
 
@@ -41,8 +39,7 @@ import { Render } from "~/components";
 	file="tunnel-health/mconn-heartbeat-health"
 	product="networking-services"
 	params={{
-		heartbeatURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		heartbeatURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
index 5c56ccb5ff6fcbf..3b09a3fa29ff311 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts.mdx
@@ -18,9 +18,7 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		magicTunnelHealthCheckCalculation:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/",
-		networkAnalyticsPath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		healthChecks:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsPath: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		healthChecks: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index 33927b2f361233a..4a5d426468f3433 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -12,7 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/custom-ike-id-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
index e3d0145968a7905..066c118ccf4222d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,14 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		greIpsecTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		greIpsecTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
index d1d59be9414d68b..f9858038dbd480e 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx
@@ -16,8 +16,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		productName: "Cloudflare WAN",
-		healthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		healthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		addTunnelsPath:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index ca3e788d025bd8b..26d6f25b6a74b55 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,11 +13,10 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-	file="routing/configure-cloudflare-source-ips"
-	product="networking-services"
-	params={{
-		unifiedRoutingLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/",
-	}}
+  file="routing/configure-cloudflare-source-ips"
+  product="networking-services"
+  params={{
+    unifiedRoutingLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    connectivityOptionsLink: "/cloudflare-one/networks/connectivity-options/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
index 334a23c9167b3af..2fd957397c1f902 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -6,37 +6,29 @@ products:
 sidebar:
   order: 2
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		trafficSteeringPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		trafficSteeringPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		addTunnelsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table",
+		routingTableName: "Cloudflare Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index d615ab646878dd7..1f5ce39957c3508 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -12,41 +12,26 @@ tags:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayPagePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		cniLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		tunnelHealthChecksPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		tunnelsAndEncapsulationPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayPagePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		cniLink: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		updateHCFrequencyPage: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		tunnelHealthChecksPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		sitesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
+		tunnelHealthDash: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		sitesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/sites/",
+		configureARRURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
index 8d38559e9f784a5..478096429eb0edf 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
index 006aa7559219809..91c321110a4e9fa 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -15,11 +15,8 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
index 7cfe5c8a32d1f27..ee5e8e31b67dd5d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index c44c422d412e3e9..2e3362c2297a304 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/alibaba-cloud"
-	product="networking-services"
-	params={{
-		ipSecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/alibaba-cloud"
+  product="networking-services"
+  params={{
+    ipSecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
index 53f7609c41d4c0e..47bdff355de0e2a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect.mdx
@@ -10,13 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aruba-edgeconnect"
-	product="networking-services"
-	params={{
-		tunnelHealthCheckUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+<Render file="cloudflare-wan/third-party/aruba-edgeconnect"
+  product="networking-services"
+  params={{
+		tunnelHealthCheckUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		magicFirewallUrl: "/cloudflare-network-firewall/",
-		gatewayUrl: "/cloudflare-one/traffic-policies/",
-	}}
-/>
+		gatewayUrl: "/cloudflare-one/traffic-policies/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
index 4dde9787ebca0b6..dd27825eb60ed8a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws.mdx
@@ -6,17 +6,14 @@ products:
 title: Amazon AWS Transit Gateway
 tags:
   - AWS
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aws"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/aws"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index b02d849640387d0..6e4f1a3573cbf12 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-virtual-wan"
-	product="networking-services"
-	params={{
-		tunnelHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		ipsecTunnelUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		cloudflareDocumentationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-virtual-wan"
+  product="networking-services"
+  params={{
+  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  cloudflareDocumentationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index e3af7916ddaaf15..6308449fc485359 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-vpn-gateway"
-	product="networking-services"
-	params={{
-		ipsecTunnelUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		staticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		tunnelHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
+  product="networking-services"
+  params={{
+  ipsecTunnelUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  staticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  tunnelHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
index 61a653693d0b777..3692dd21b4e45ca 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index df5158c103fe80f..26cd14b751b3d81 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -10,7 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-ios-xe"
-	product="networking-services"
+<Render file="cloudflare-wan/third-party/cisco-ios-xe"
+  product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index b752d4f85dab6f7..2bf5636cbdce15a 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -10,25 +10,15 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
-		trafficSteeringUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		paloAltoGuideUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+		antiReplayProtectionUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+		unifiedRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		supportedConfigParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		paloAltoGuideUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+		configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+	}} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 0da4cb37c63d84d..4af42ab35a2bc43 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fitelnet"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		typeId_ipv4_addrUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fitelnet"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    typeId_ipv4_addrUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
index e71cf29b9f07669..3869ebd7e5a01ea 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -10,19 +10,12 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fortinet"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		equalCostMultipathRoutingEcmpUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fortinet"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    equalCostMultipathRoutingEcmpUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
index e8e6fe1d8fc944a..e35533f9aa61fae 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google.mdx
@@ -12,13 +12,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/google"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/google"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
index 88548b31947b629..28c8eb38103e3a7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
index f3b4d51ebae092c..9041812a55d647d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,15 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/juniper"
-	product="networking-services"
-	params={{
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/juniper"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
index 4fe095992306cb0..544a2fd71e1b10b 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -10,13 +10,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/oracle"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/oracle"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
index d3a02cd42315066..74648ea559442b1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,15 +13,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/palo-alto"
-	product="networking-services"
-	params={{
-		mssClampingUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/palo-alto"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
index 8beb36669a01a5a..5c7329f8bb2a15d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -11,15 +11,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/pfsense"
-	product="networking-services"
-	params={{
-		configureTwoIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		staticRouteUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/pfsense"
+  product="networking-services"
+  params={{
+    configureTwoIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    staticRouteUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
index e2236e3c62ec88c..681705328bc2479 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sonicwall"
-	product="networking-services"
-	params={{
-		ipsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		creatingYourIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createYourStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sonicwall"
+  product="networking-services"
+  params={{
+    ipsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    creatingYourIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createYourStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index afc7910dc9d12af..b2a4c4249e87375 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -10,17 +10,11 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sophos-firewall"
-	product="networking-services"
-	params={{
-		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		ikeIdUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sophos-firewall"
+  product="networking-services"
+  params={{
+    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    ikeIdUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
index bb005e68632169a..ceba0f994025298 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -11,11 +11,8 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/strongswan"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/strongswan"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 9a96fafe0bfa4ab..a97b5659741e9d7 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -11,9 +11,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-wan/third-party/ubiquiti"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-	}}
+  file="cloudflare-wan/third-party/ubiquiti"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
index 736fbd873bbdd38..f944858befeffef 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -10,11 +10,8 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/velocloud"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/velocloud"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
index c7dc2d9c75ba0a6..1d4fe3f1866abf4 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -11,15 +11,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/viptela"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		ciscoIosXeUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/viptela"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
index e79d26181aeb494..75be63a9bfe72a6 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -10,4 +10,6 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
+<Render file="cloudflare-wan/third-party/vyos"
+  product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
index b2355afb2d6994d..77d9af6a973237c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -10,13 +10,9 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/yamaha"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/yamaha"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
index 8cf6de52ad11759..f8e8f7694c90053 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/get-started.mdx
@@ -16,19 +16,12 @@ import { Render } from "~/components";
 	params={{
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		configureConnectorUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		configureMwanManually:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		greReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		mtuReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		configureConnectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		configureMwanManually: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ipsecReferenceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		mtuReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
index c804130785b3a29..8aac7ee6d2a4275 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/index.mdx
@@ -20,19 +20,13 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		connectorName: "Cloudflare One Appliance",
 		connectorCta: "Use Cloudflare One Appliance",
-		getStartedUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		connectorUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		zeroTrustUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
-		wanTransformationUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/",
+		connectorUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		bgpRoutesUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		wanTransformationUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		virtualNetworksUrl: "/cloudflare-one/networks/virtual-networks/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
index c54c3b324cf1b28..a8d18b418df7a40 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/3rdparty.mdx
@@ -5,6 +5,7 @@ pcx_content_type: reference
 description: Reference information for Third party licenses in Zero Trust networking.
 products:
   - cloudflare-one
+
 ---
 
 import text from "./3rdparty.txt?raw";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
index 653b31922480265..70f7ed48d19fc64 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/legal/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 12
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
index 475873e33440e3a..b6c275104b79281 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect.mdx
@@ -13,21 +13,14 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="magic-cni"
-	product="networking-services"
-	params={{ magicWord: "Cloudflare WAN" }}
-/>
+<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
index 506e7260402fd54..0e0944033ed0838 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps.mdx
@@ -17,17 +17,11 @@ import { Render } from "~/components";
 		magicWord: "CF1 Cloudflare WAN",
 		productNameWAN: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
-		connectorURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		thirdPartyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
-		cniURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		connectorURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		thirdPartyURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/",
+		cniURL: "/cloudflare-one/networks/connectors/cloudflare-wan/network-interconnect/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		thirdPartyIntegrationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
index bdb55cdaa44ca58..f827135b0192839 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -5,8 +5,7 @@ products:
 title: Anti-replay protection
 tags:
   - IPsec
-description:
-  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
index 32b8afa7e6f4527..6a168b9730c3943 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cloudflareTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
index a51b28317cfdf42..4fa1452c2f1d01c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/device-compatibility.mdx
@@ -12,53 +12,29 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/reference/device-compatibility"
-	product="networking-services"
-	params={{
-		supportedConfigurationParametersUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		arubaEdgeconnectUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-		ciscoIosXeUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-		ciscoMerakiStaticUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-		ciscoSdWanUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
-		fortinetUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
-		fitelnetUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
-		juniperUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
-		paloAltoUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
-		pfsenseUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
-		sonicwallUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
-		sophosFirewallUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
-		strongswanUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
-		ubiquitiUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
-		velocloudUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
-		vyosUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
-		yamahaUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
-		alibabaCloudUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-		awsUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
-		azureUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
-		googleUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
-		oracleUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/",
-	}}
-/>
+<Render file="cloudflare-wan/reference/device-compatibility"
+  product="networking-services"
+  params={{
+    supportedConfigurationParametersUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    arubaEdgeconnectUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+    ciscoIosXeUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+    ciscoMerakiStaticUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+    ciscoSdWanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/viptela/",
+    fortinetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet/",
+    fitelnetUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fitelnet/",
+    juniperUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/juniper/",
+    paloAltoUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/palo-alto/",
+    pfsenseUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/pfsense/",
+    sonicwallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sonicwall/",
+    sophosFirewallUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/sophos-firewall/",
+    strongswanUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/strongswan/",
+    ubiquitiUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/ubiquiti/",
+    velocloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/velocloud/",
+    vyosUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/vyos/",
+    yamahaUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/yamaha/",
+    alibabaCloudUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+    awsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/aws/",
+    azureUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/azure/",
+    googleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/google/",
+    oracleUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/oracle/"
+  }} />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 32c6047307e94c8..e48aacf091b3898 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -19,18 +19,14 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		mssURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		productURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		mssURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		productURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index c08c54539b5b3b6..f4b1ec66d7f87c2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,13 +8,9 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination",
-	}}
+	params={{ tunnelStatePath: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#tunnel-state-determination"	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
index 936eef5bb11c21b..c9bbdad031b4e3d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
index a6693ef9af219d6..dad3b9a5d8d8777 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
+		productName: "Cloudflare WAN"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
index c5d20719e86eb64..354bdbd705088a9 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering.mdx
@@ -17,30 +17,22 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
+  	magicWord: "CF1 Cloudflare WAN",
+  	productName: "Cloudflare WAN",
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		cfTunnelURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
-		greIpsecReferenceURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		createStaticRoute:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		editStaticRoute:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
-		setupBgpPeering:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
-		legacyHCs:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
-		tunnelHCsPage:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+  	greIpsecReferenceURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/",
+  	createStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  	editStaticRoute: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#edit-a-static-route",
+  	setupBgpPeering: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
 		sourceIPsURL:
 			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/",
 		virtualNetworkName: "Cloudflare Virtual Network",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
index f8b615e6070db55..276bc867f82dcd8 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -18,16 +18,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "CF1 Cloudflare WAN",
-		addTunnels:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
-		staticRoutes:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		staticRoutes: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelEndpoints: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
index eace55f088f5192..d122736e9eeaedc 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/security.mdx
@@ -9,15 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="cloudflare-wan/security-filters"
+<Render file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		gatewayURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
index e5bc049482c1740..2eb4a9483c2622f 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,15 +17,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
index fb5782e5fef4adf..1e718eb8e9c31ce 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index 23dbe5aa1465d70..3f0cd1c1f120d63 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -10,19 +10,14 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index dd1b594c265542e..41ea7fb74a080e1 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -13,18 +13,14 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
index fca3b17df568c35..49a3d8aef991d65 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -14,24 +14,17 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
index 0dcfa150778deae..a1fce7bc5634d3c 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation.mdx
@@ -17,15 +17,11 @@ import { Render } from "~/components";
 	file="cloudflare-wan/wan-transformation"
 	product="networking-services"
 	params={{
-		getStartedUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
+		getStartedUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/",
 		connectivityOptionsUrl: "/cloudflare-one/networks/connectivity-options/",
 		onRampsUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		zeroTrustUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
-		applianceUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
-		secureWanTrafficUrl:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
+		zeroTrustUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/",
+		applianceUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/",
+		secureWanTrafficUrl: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
index c39636c40320181..37ab275a843c03d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway.mdx
@@ -18,36 +18,21 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		warpURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfAutoCertificatesURL:
-			"/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
-		cfManualCertificatesURL:
-			"/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
-		decryptTlsURL:
-			"/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
-		doNotInspectURL:
-			"/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
-		warpChecksURL:
-			"/cloudflare-one/reusable-components/posture-checks/client-checks/",
-		osVersionChecks:
-			"/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
-		mwanOnrampsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
-		gatewayResolverPoliciesURL:
-			"/cloudflare-one/traffic-policies/resolver-policies/",
-		gatewayInternalDnsURL:
-			"/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
+		warpURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client/",
+		cfAutoCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/",
+		cfManualCertificatesURL: "/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/",
+		decryptTlsURL: "/cloudflare-one/traffic-policies/http-policies/tls-decryption/",
+		doNotInspectURL: "/cloudflare-one/traffic-policies/http-policies/#do-not-inspect",
+		warpChecksURL: "/cloudflare-one/reusable-components/posture-checks/client-checks/",
+		osVersionChecks: "/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/",
+		mwanOnrampsURL: "/cloudflare-one/networks/connectors/cloudflare-wan/on-ramps/",
+		gatewayResolverPoliciesURL: "/cloudflare-one/traffic-policies/resolver-policies/",
+		gatewayInternalDnsURL: "/cloudflare-one/traffic-policies/resolver-policies/#internal-dns",
 		egressPoliciesURL: "/cloudflare-one/traffic-policies/egress-policies/",
-		gatewayLogsURL:
-			"/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
-		tcpMssClampingURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
-		ikeURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		gatewayLogsURL: "/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/#http-logs",
+		tcpMssClampingURL: "/cloudflare-one/networks/connectors/cloudflare-wan/get-started/#set-maximum-segment-size",
+		ikeURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
index a6aa06e27222024..021d27ca4f6f08d 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-one-client.mdx
@@ -18,23 +18,15 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/warp"
 	product="networking-services"
 	params={{
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		setupZeroTrustAccountURL:
-			"/cloudflare-one/setup/#2-create-a-zero-trust-organization",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		setupZeroTrustAccountURL: "/cloudflare-one/setup/#2-create-a-zero-trust-organization",
 		ztDashPath: "My Team > Devices",
-		splitTunnelsURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
-		warpDeploymentURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
-		warpIngressIpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
+		splitTunnelsURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/",
+		warpDeploymentURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/",
+		warpIngressIpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip",
 		mwanConnectorName: "Cloudflare One Appliance",
-		domainFallbackURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		domainFallbackURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/#add-a-domain",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index 0d372fbdcc0d99f..d1ca77abe7c8a72 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -15,15 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		greIpsecURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/traceroute/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
index 510e6bd01921e87..86daf36cc1a9660 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/index.mdx
@@ -9,6 +9,7 @@ head:
   - tag: title
     content: Cloudflare One integration tutorials
 description: Learn how to integrate Cloudflare WAN with other Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
index a634aba89cca3ac..1bcbcba64603e90 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/security-services.mdx
@@ -16,11 +16,8 @@ import { Render } from "~/components";
 	file="cloudflare-wan/zero-trust/security-services"
 	product="networking-services"
 	params={{
-		networkFirewallURL:
-			"/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
-		gatewaySetupURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
-		wanTransformationURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
+		networkFirewallURL: "/cloudflare-one/traffic-policies/packet-filtering/network-firewall-overview/",
+		gatewaySetupURL: "/cloudflare-one/networks/connectors/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		wanTransformationURL: "/cloudflare-one/networks/connectors/cloudflare-wan/wan-transformation/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
index 21c15ec9d2d739b..1db111952cb9cd0 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/granular-permissions.mdx
@@ -8,7 +8,7 @@ products:
   - cloudflare-one
 ---
 
-import { Steps } from "~/components";
+import { Steps } from '~/components';
 
 You can scope Cloudflare member permissions to individual [Cloudflare Tunnel](/tunnel/) instances and [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) nodes, instead of granting account-wide access to every Tunnel and Mesh node. This enables least-privilege delegation for private networking operations — for example, letting a support operator stream logs from a single Tunnel without exposing the rest of your account.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
index 7c6fe57320f8f26..24eaa0394bc62b2 100644
--- a/src/content/docs/cloudflare-one/networks/connectors/index.mdx
+++ b/src/content/docs/cloudflare-one/networks/connectors/index.mdx
@@ -10,6 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
+
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
index 189b65dec009c19..8bfca8fb0871aec 100644
--- a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx
@@ -29,9 +29,9 @@ To add a CIDR route:
 3. In **CIDR**, enter the IP address or CIDR range that you wish to route through the tunnel (for example, `10.0.0.1` or `10.0.0.0/24`). This can be a private or public IP.
 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare.
 5. (Optional) Under **Additional settings**, select a [virtual network](/cloudflare-one/networks/virtual-networks/) for this tunnel route. A virtual network is a private routing domain that provides routing isolation within your account. This step is only needed if the route's IP/CIDR range overlaps with another route in your account. If you do not select a virtual network, the IP route will be assigned to the `default` network.
-   :::note
-   Virtual networks are only supported for `cloudflared` tunnels.
-   :::
+		:::note
+		Virtual networks are only supported for `cloudflared` tunnels.
+		:::
 6. Select **Create**.
 
 Cloudflare will now route requests to your private network. However, the route does not automatically capture traffic from end users. To enable client-side connectivity, refer to the [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/) or
@@ -61,10 +61,9 @@ Published application routes expose applications to the Internet via a domain th
 
 :::note[Prerequisites]
 Before you publish an application, ensure you have:
-
 - [Created a Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) using `cloudflared`.
 - [Added a website to Cloudflare](/fundamentals/manage-domains/add-site/).
-  :::
+:::
 
 To add a published application route to an existing tunnel:
 
@@ -75,13 +74,13 @@ To add a published application route to an existing tunnel:
 3. Go to the **Published application routes** tab and select **Add a published application route**.
 
 4. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
+	:::note
+	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+	:::
 
 5. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example:
-   - **Type**: _HTTP_
-   - **URL**: `localhost:8000`
+	- **Type**: _HTTP_
+	- **URL**: `localhost:8000`
 
 6. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
@@ -92,3 +91,4 @@ Anyone on the Internet can now access the application at the specified hostname.
 ## Add a WAN route
 
 WAN routes define the IP network segments (such as `10.0.0.0/24`) that are reachable via a GRE or IPsec tunnel. To add a WAN route, refer to the [WAN Connectors documentation](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/).
+
diff --git a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
index 308de57b07e7f48..90e480866276de9 100644
--- a/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
+++ b/src/content/docs/cloudflare-one/networks/routes/reserved-ips.mdx
@@ -23,14 +23,14 @@ When planning your private network addressing and configuring [Split Tunnel](/cl
 | ------------------------------------------------------------- | ---------------- | ------------ |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `100.64.0.0/12`  | Yes          |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `100.80.0.0/16`  | No           |
-| [Device IPs](#device-ips)                                     | `100.96.0.0/12`  | Yes          |
+| [Device IPs](#device-ips)                           | `100.96.0.0/12`  | Yes          |
 | [Private Load Balancer IPs](#private-load-balancer-ips)       | `100.112.0.0/16` | Yes          |
 
 ## IPv6 ranges
 
 | Name                                                          | Default CIDR               | Configurable |
 | ------------------------------------------------------------- | -------------------------- | ------------ |
-| [Device IPs](#device-ips)                                     | `2606:4700:0cf1:1000::/64` | No           |
+| [Device IPs](#device-ips)                           | `2606:4700:0cf1:1000::/64` | No           |
 | [Gateway initial resolved IPs](#gateway-initial-resolved-ips) | `2606:4700:0cf1:4000::/64` | No           |
 | [Cloudflare source IPs](#cloudflare-source-ips)               | `2606:4700:0cf1:5000::/64` | No           |
 
diff --git a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
index be5f7bea46c3b41..6a8f6c283d0c8b1 100644
--- a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx
@@ -17,15 +17,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare One",
-		tunnelConfigURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		trafficSteeringURL:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		configureRoutesURL: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+		trafficSteeringURL: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/",
+		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
index c3ff67b1fdb0308..0749407053febed 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/accessibility.mdx
@@ -24,4 +24,4 @@ Alternatively, to use a keyboard shortcut, press `CTRL + ALT + Z`.
 
 ## Languages
 
-The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
+The isolated browser supports keyboard inputs in all languages. Users can use their native keyboard to type in languages that use diacritics (for example, `á` or `ç`) or character-based scripts (for example, Chinese, Japanese, or Korean).
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
index 3ad4acc8218df86..c608dbdef4888a2 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/index.mdx
@@ -12,6 +12,7 @@ tags:
 
 import { Render } from "~/components";
 
+
 :::note
 Remote browser isolation is available as an add-on to Zero Trust Pay-as-you-go and Enterprise plans.
 :::
@@ -29,3 +30,4 @@ Cloudflare Browser Isolation is a security product. In order to serve transparen
 ## Troubleshooting
 
 For help resolving common issues with Browser Isolation, refer to [Troubleshoot Browser Isolation](/cloudflare-one/remote-browser-isolation/troubleshooting/).
+
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
index e7f230098916d61..b4040d192dbbf47 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/known-limitations.mdx
@@ -83,7 +83,4 @@ You no longer need to isolate both the Identity Provider (IdP) and Service Provi
 
 ## Browser Isolation is not compatible with private apps on non-`443` ports
 
-<Render
-	file="access/self-hosted-app/browser-isolation-non-443"
-	product="cloudflare-one"
-/>
+<Render file="access/self-hosted-app/browser-isolation-non-443" product="cloudflare-one"/>
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
index 21df1128ff02665..a74778b93fcbd01 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/network-dependencies.mdx
@@ -34,8 +34,8 @@ Browser Isolation uses WebRTC (a real-time communication protocol) for low-laten
 
 In order to pass WebRTC traffic, the remoting client must be able to connect to the following IP addresses:
 
-| IP range                                                                                                           | Port range    | Protocol |
-| ------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
+| IP range                                                                 | Port range    | Protocol |
+| ------------------------------------------------------------------------ | ------------- | -------- |
 | IPv4: `162.159.201.10 - 162.159.201.255` <br/> IPv4: `172.64.73.0 - 172.64.73.255` <br/> IPv6: `2606:4700:f2::/48` | 10000 - 59999 | UDP      |
 
 Each remote browser instance is randomly assigned a port, and the port that a user is allocated to will change often and without notice.
diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
index 9e910279a1fe9a8..c45a25eaf8d13b8 100644
--- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
+++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx
@@ -15,13 +15,13 @@ Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudfl
 
 Setup instructions vary depending on how you want to connect your devices to Cloudflare. Refer to the links below to view the setup guide for each deployment option.
 
-| Connection                                                                                                | Mode         | Description                                                                                                                                       |
-| --------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                                          |
-| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                                                  |
-| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).     |
-| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network). |
-| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`.                              |
+| Connection                                                                                                | Mode         | Description                                                                                                          |
+| --------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
+| [Traffic and DNS mode](/cloudflare-one/traffic-policies/get-started/http/)                                | In-line      | Apply identity-based HTTP policies to traffic proxied through the Cloudflare One Client.                                       |
+| [Access](/cloudflare-one/access-controls/policies/isolate-application/)                                   | In-line      | Apply identity-based HTTP policies to Access applications that are rendered in a remote browser.                     |
+| [Gateway proxy endpoint](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                    | In-line      | Apply non-identity HTTP policies to traffic forwarded to a [proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                           |
+| [Cloudflare WAN](/cloudflare-one/remote-browser-isolation/setup/non-identity/)                            | In-line      | Apply non-identity HTTP policies to traffic connected through a GRE or IPsec tunnel (site-to-site encrypted connections to Cloudflare's network).                                 |
+| [Clientless remote browser](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) | Prefixed URL | Render web pages in a remote browser when users go to `https://<your-team-name>.cloudflareaccess.com/browser/<URL>`. |
 
 **In-line** mode means traffic is inspected as it flows through Gateway — users browse to websites using normal URLs, not a special Cloudflare prefix. Some in-line methods require device or network configuration, such as installing the Cloudflare One Client or configuring a PAC file. **Prefixed URL** mode requires users to visit a Cloudflare-hosted URL that wraps the target website.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
index 318f06a6fc92ed4..f0ab810ee252406 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx
@@ -79,7 +79,7 @@ You can add a Mailto link to your custom block page, which allows users to direc
 | Source IP    | The public source IP of the user device.                                                                                                                                                                                    |
 | Account ID   | The Cloudflare account associated with the block policy.                                                                                                                                                                    |
 | User ID      | The ID of the user who visited the page. Currently, User IDs are not surfaced in the dashboard and can only be viewed by calling the [API](/api/resources/zero_trust/subresources/access/subresources/users/methods/list/). |
-| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                 |
+| Device ID    | The ID of the device that visited the page. This is generated by the Cloudflare One Client.                                                                                                                                           |
 | Block Reason | Your policy-specific block message.                                                                                                                                                                                         |
 
 ## Configure policy block behavior
diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
index 96799f2d3e915f6..c7cde6525fc3b70 100644
--- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
index ccfd4fb9efc2beb..1b02eaa266e0cf7 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx
@@ -49,23 +49,24 @@ You can use the following commands to validate if the posture check is working a
 1. Open a PowerShell window.
 2. List all installed antivirus products registered with Windows Security Center:
 
-   ```powershell
-   Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
-   ```
-
-   ```powershell output
-   <redacted>
-   displayName              : Windows Defender
-   instanceGuid             : {00000000-0000-0000-0000-000000000000}
-   pathToSignedProductExe   : windowsdefender://
-   pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
-   productState             : 397568
-   timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
-   PSComputerName           : ENDPOINT-01
-   ```
+	```powershell
+	Get-WmiObject -Namespace "root\SecurityCenter2" -ClassName "AntiVirusProduct"
+	```
+
+	```powershell output
+	<redacted>
+	displayName              : Windows Defender
+	instanceGuid             : {00000000-0000-0000-0000-000000000000}
+	pathToSignedProductExe   : windowsdefender://
+	pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe
+	productState             : 397568
+	timestamp                : Fri, 09 Jan 2026 12:00:00 GMT
+	PSComputerName           : ENDPOINT-01
+	```
 
 3. Microsoft does not support decoding the `productState` from the `SecurityCenter2` namespace. To verify that an antivirus product is active, open the [Windows Security app](https://support.microsoft.com/en-us/windows/stay-protected-with-the-windows-security-app-2ae0363d-0ada-c064-8b56-6a39afb6a963). The **Virus & threat protection** panel should say `No action needed` with a green checkmark.
 
-   To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
+	To determine which antivirus product is running, select **Virus & threat protection** > **Manage providers**. You will see the name of the antivirus product (for example, `Windows Defender Antivirus`) and its current state.
 
 4. If you configured a maximum antivirus signature age in your posture check, compare the `timestamp` in the PowerShell output against the current system time. If the difference exceeds the configured number of days, the posture check will fail.
+
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
index 6e24b6094c78b8c..daec64a910742b5 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx
@@ -38,12 +38,12 @@ The Application Check device posture attribute checks that a specific applicatio
    2. **Operating system**: Select your operating system.
    3. **Application path**: Enter the file path for the executable that will be running (for example, `C:\Program Files\myfolder\myfile.exe`).
 
-      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
+		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
 
    :::note
    - Be sure to enter the binary file path, not the application launch path. When checking for an application on macOS, a common mistake is to enter `/Applications/ApplicationName.app`. This will not work as `ApplicationName.app` is a folder. The executable file that will be running is located within the folder, for example `ApplicationName.app/Contents/MacOS/ApplicationName`.
    - Some applications change their file path after an update. Ensure that the application is always in a stable location or use environment variables.
-     :::
+	 :::
 
 5. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint of the publishing certificate](#determine-the-signing-thumbprint) used to sign the binary. Adding this information will enable the check to ensure that the application was signed by the expected software developer.
 6. **SHA-256 (optional)**: Enter the [SHA-256 value](#determine-the-sha-256-value) of the binary. This is used to ensure the integrity of the binary file on the device.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
index d0a1f568446a035..bcf50cd88967c96 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx
@@ -38,8 +38,7 @@ The File Check device posture attribute checks for the presence of a file on a d
    2. **Operating system**: Select your operating system.
    3. **File Path**: Enter a file path (for example, `c:\my folder\myfile.exe`).
 
-      <Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
-
+		<Render file="posture/env-vars-in-file-paths" product="cloudflare-one" />
    4. **Signing certificate thumbprint (recommended)**: Enter the [thumbprint](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-signing-thumbprint) of the publishing certificate used to sign the file. Adding this information will enable the check to ensure that the file was signed by the expected software developer.
    5. **SHA-256 (optional)**: Enter the [SHA-256 value](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/#determine-the-sha-256-value) of the file. This is used to ensure the integrity of the file on the device.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
index b580c8ae61cbeb2..1d1d08a80225a0d 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx
@@ -36,13 +36,12 @@ The Firewall device posture attribute ensures that a firewall is running on a de
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Configure **Enable firewall check** based on your desired security policy:
-   - **Enabled**: (Recommended) The posture check passes only if the firewall is running.
-   - **Disabled**: The posture check passes only if the firewall is turned off.
-
-   :::note
-   The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
-   :::
+	- **Enabled**: (Recommended) The posture check passes only if the firewall is running.
+	- **Disabled**: The posture check passes only if the firewall is turned off.
 
+	:::note
+	The **Enable firewall check** toggle does not turn the posture check on or off; rather, the toggle determines whether the Cloudflare One Client looks for an active or inactive firewall.
+	:::
 7. Select **Save**.
 
 Next, go to **Insights** > **Logs** > **Posture logs** and verify that the firewall check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
index 00d1b33264aa55e..1ceee1540f5307e 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/index.mdx
@@ -6,32 +6,33 @@ products:
 title: Cloudflare One Client checks
 sidebar:
   order: 1
+
 ---
 
 These device posture checks are performed by the [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/). To use this feature, you must [deploy the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) to your devices and enable the desired posture checks.
 
 ## Supported Client modes
 
-- Traffic and DNS mode
-- Traffic only mode
-- Posture only mode
+* Traffic and DNS mode
+* Traffic only mode
+* Posture only mode
 
 ## Supported operating systems
 
-| Device posture check                                                                                       | macOS | Windows | Linux | iOS | Android/ChromeOS |
-| ---------------------------------------------------------------------------------------------------------- | ----- | ------- | ----- | --- | ---------------- |
-| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)                   | ❌    | ✅      | ❌    | ❌  | ❌               |
-| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌    | ❌      | ❌    | ✅  | ✅               |
-| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌    | ✅      | ❌    | ❌  | ❌               |
-| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅    | ✅      | ❌    | ❌  | ❌               |
-| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅    | ✅      | ✅    | ✅  | ✅               |
-| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅    | ✅      | ✅    | ❌  | ❌               |
-| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                | ✅    | ✅      | ✅    | ❌  | ❌               |
+| Device posture check                                                                          | macOS | Windows | Linux       | iOS | Android/ChromeOS |
+| --------------------------------------------------------------------------------------------- | ----- | ------- | ----------- | --- | ---------------- |
+| [Antivirus](/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
+| [Application check](/cloudflare-one/reusable-components/posture-checks/client-checks/application-check/)   | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Carbon Black](/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black/)             | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Client certificate](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Device serial numbers](/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device/)     | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Device UUID](/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid/)               | ❌     | ❌       | ❌           | ✅   | ✅                |
+| [Disk encryption](/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption/)       | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Domain joined](/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined/)           | ❌     | ✅       | ❌           | ❌   | ❌                |
+| [File check](/cloudflare-one/reusable-components/posture-checks/client-checks/file-check/)                 | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Firewall](/cloudflare-one/reusable-components/posture-checks/client-checks/firewall/)                     | ✅     | ✅       | ❌           | ❌   | ❌                |
+| [OS version](/cloudflare-one/reusable-components/posture-checks/client-checks/os-version/)                 | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)       | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [Require WARP](/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp/)             | ✅     | ✅       | ✅           | ✅   | ✅                |
+| [SentinelOne](/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one/)              | ✅     | ✅       | ✅           | ❌   | ❌                |
+| [Tanium (legacy)](/cloudflare-one/reusable-components/posture-checks/client-checks/tanium/)                          | ✅    | ✅      | ✅    | ❌  | ❌  |
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
index 92e23f910d1ba59..e30d916ac2409c1 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx
@@ -36,7 +36,7 @@ The OS Version device posture attribute checks whether the version of a device's
 
 5.  (Optional) Configure additional OS-specific fields:
 
-<Tabs>
+		<Tabs>
 		<TabItem label="Windows">
 		To check that Windows devices have required security patches and features installed, include an Update Build Revision (UBR) number in the OS version check.
 		- **Update Build Revision**: Enter the Windows UBR you want devices to match (for example, `3803`). The UBR is the fourth part of the full Windows version number (for example, in `10.0.19045.3803`, the UBR is `3803`).
@@ -77,7 +77,6 @@ Operating systems display version numbers in different ways. This section covers
 ### Windows
 
 Windows version numbers consist of four parts: `Major.Minor.Build.UBR`. For example, `10.0.19045.3803` where:
-
 - `10.0` is the **Version** (Major.Minor)
 - `19045` is the **Build** number
 - `3803` is the **UBR** (Update Build Revision)
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
index 14c460754260543..fe3b97910a59def 100644
--- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx
@@ -37,7 +37,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru
 ## 1. Enable the WARP check
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Traffic settings**.
-2. Ensure that \*Allow Secure Web Gateway to proxy traffic\*\* is enabled.
+2. Ensure that *Allow Secure Web Gateway to proxy traffic** is enabled.
 3. Go to **Reusable components** > **Posture checks**.
 4. In **Cloudflare One Client checks**, select **Add a check**.
 5. Select **WARP**, then select **Save**.
diff --git a/src/content/docs/cloudflare-one/reusable-components/tags.mdx b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
index 9cf337c0f0573e9..affffb57c1a52f9 100644
--- a/src/content/docs/cloudflare-one/reusable-components/tags.mdx
+++ b/src/content/docs/cloudflare-one/reusable-components/tags.mdx
@@ -11,3 +11,4 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="access/tags" product="cloudflare-one" />
+
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
index be1e46ccc11fec2..06e26a64c28ed43 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx
@@ -109,8 +109,8 @@ Use when you only want to enforce [Cloudflare One Client device posture checks](
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                          | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                   | Best for                                         | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | Full security with all filtering capabilities    | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | DNS filtering without routing device traffic     | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | Traffic routing with existing DNS infrastructure | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
index 7042d96a25bd81b..3ddfb9848c66291 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/common-issues.mdx
@@ -19,7 +19,6 @@ This section covers the most common issues you might encounter as you deploy the
 ## Connectivity and registration
 
 ### Stuck on "Disconnected" or frequent flapping
-
 If the Cloudflare One Client is stuck in the `Disconnected` state or frequently changes between `Connected` and `Disconnected`, this indicates that the client cannot establish a connection to Cloudflare's global network.
 
 In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/), `daemon.log` will typically show one or more of the following errors:
@@ -28,75 +27,61 @@ In your [client diagnostic logs](/cloudflare-one/team-and-resources/devices/clou
 - Connectivity checks timing out for `connectivity.cloudflareclient.com`.
 
 **Common causes**:
-
 - **Firewall blocks**: A local or network firewall is blocking the [required IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 - **VPN interference**: A third-party VPN is fighting for control over the routing table or DNS. Refer to the [VPN compatibility guide](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/vpn/).
 - **ISP blocks**: Your country or ISP may be explicitly blocking client traffic.
 
 ### Registration error (Authentication Expired)
-
 When registering the client, you may see `Authentication Expired` or `Registration error. Please try again later`.
 
 **Common causes**:
-
 - **System clock out of sync**: Your computer system clock must be properly synced via NTP. If your clock is off by more than 20 seconds, the authentication token (JWT) will be invalid.
 - **Prompt timeout**: You must complete the registration in your browser and return to the client within one minute of the prompt.
 
 ### (Linux) DNS connectivity check failed
-
 This error often means that `systemd-resolved` is not allowing the client to resolve DNS requests. In `daemon.log`, you will see `DNS connectivity check failed to resolve host="warp-svc."`.
 
 **Solution**:
-
 1. Add `ResolveUnicastSingleLabel=yes` to `/etc/systemd/resolved.conf`.
 2. Ensure no other DNS servers are explicitly configured in that file.
 3. Restart the service: `sudo systemctl restart systemd-resolved.service`.
 
 ### (Mac/Linux) Invalid character in resolv.conf
-
 The client cannot parse `resolv.conf` files containing invalid characters like `!@#$%^&*()<>?` in `search` directives. Remove these characters to restore service.
 
 ## Browser and certificate issues
 
 ### "Your connection is not private" or untrusted warnings
-
 Advanced security features require the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) to be trusted on the device.
 
 - **Chrome/Edge**: These browsers cache certificates. If you installed the certificate while the browser was running, you must restart the browser.
 - **Root certificate expiry**: The default Cloudflare root certificate expired on February 2, 2025. If you are seeing errors, [generate and activate a new certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) in the dashboard.
 
 ### 2025 Certificate migration
-
 Starting with version 2024.12.554.0, the client can automatically install new certificates as soon as they are **Available** in the dashboard. For older versions, certificates had to be marked **In-Use** first. Ensure **Install CA to system certificate store** is enabled in your [Device settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).
 
 ## Windows-specific issues
 
 ### Windows shows "No Internet access"
-
 This is often a cosmetic error with Windows Network Connectivity Status Indicator (NCSI). Apps like Outlook or JumpCloud may refuse to connect because of this status.
 
 **Solution**:
 Configure NCSI to detect the client's local DNS proxy and use active probing by setting these registry keys to `1`:
-
 - `HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS`
 - `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\EnableActiveProbing`
 
 ### Setup Wizard ends prematurely
-
 This usually indicates a missing dependency, such as .NET Framework `4.7.2` or later. Legacy systems (like Windows 10 Enterprise 1607) may require a manual update of the [.NET Framework Runtime](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net472).
 
 ## Other environment issues
 
 ### WSL2 connectivity
-
 If WSL2 loses connectivity, check your [split tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). The IP range used by WSL to communicate with the host may be accidentally included in the tunnel. Exclude the WSL network range to restore connectivity.
 
 ### SMTP port 25 blocked
-
 By default, the client blocks outgoing traffic on port `25` to prevent spam. Use port `587` or `465` for encrypted email, or contact your account team to request an unblock.
 
 ### Admin override codes expired
-
 [Admin override codes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-admin-override-codes) are time-sensitive and adhere to fixed-hour blocks. A code generated at 9:30 AM with a 1-hour timeout will expire at 10:00 AM because its validity is counted within the 9:00 AM-10:00 AM window.
 
 ---
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
index 57570302af9994e..41e24ebbe3edf84 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/connectivity-status.mdx
@@ -16,22 +16,22 @@ The Cloudflare One Client (formerly WARP) GUI displays the following status mess
 
 To print status messages to the console, run the `warp-cli -l status` command before connecting the client.
 
-| Status message                       | Description                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                                              |
-| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                                                        |
-| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                                                     |
-| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                                                       |
-| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                                          |
-| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                                                 |
+| Status message                       | Description                                                                                                                                                                                                                                                                        |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Verifying connection settings        | Initializes connection components based on your [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/).                                                                                                                           |
+| Validating network                   | Validates Ethernet and/or Wi-Fi network connectivity.                                                                                                                                                                                                                              |
+| Initializing IP connection           | Checks for IPv4 and IPv6 connectivity to Cloudflare using the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555).                                                                                                                                           |
+| Establishing a connection            | Connects to the endpoint discovered by Happy Eyeballs.                                                                                                                                                                                                                             |
+| Building a Tunnel                    | Creates a [virtual network interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#virtual-interface) on the operating system for the WARP tunnel.                                                                              |
+| Configuring the firewall             | Configures the system firewall to allow WARP tunnel traffic.                                                                                                                                                                                                                       |
 | Setting up your routing table        | Updates the [system routing table](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#routing-table) based on your [Split Tunnel rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). |
-| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                            |
-| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                                             |
-| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                                          |
-| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                                   |
-| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                                            |
-| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                                                 |
-| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                                      |
-| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                                           |
-| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                                     |
-| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                                              |
+| Configuring your firewall rules      | Configures the [system firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) based on your Split Tunnel rules.                                                                                                |
+| Checking connectivity to DNS         | Checks connectivity to the DNS endpoint (`<account-id>.cloudflare-gateway.com`).                                                                                                                                                                                                   |
+| Setting local endpoint communication | Configures local DNS proxy sockets.                                                                                                                                                                                                                                                |
+| Configuring local DNS proxy          | Creates a [local DNS proxy](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#dns-traffic) for DNS resolution.                                                                                                                       |
+| Applying DNS settings                | Sets the local DNS proxy as the default DNS server on the device.                                                                                                                                                                                                                  |
+| Configuring forward proxy            | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Configures the SOCKS proxy.                                                                                                                              |
+| Confirming Tunnel connection         | Checks connectivity to [destinations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks) inside and outside of the WARP tunnel.                                                                                                             |
+| Validating DNS configuration         | Verifies that DNS requests are answered by WARP's local DNS proxy.                                                                                                                                                                                                                 |
+| Verifying SOCKS proxy configuration  | (Only in [Local proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode)) Verifies the SOCKS proxy configuration.                                                                                                                  |
+| Ensuring MTLS identity               | (Only in [Posture only mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only/)) Installs a client certificate for mTLS authentication.                                                                                           |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
index 2bff092a3e7064e..1a48f5bece5c008 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs.mdx
@@ -59,82 +59,82 @@ You can collect client diagnostic logs remotely from the Zero Trust dashboard by
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                                   |
-| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                            |
-| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                              |
-| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                           |
-| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                        |
-| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                 |
-| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                                   |
-| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                                |
-| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                          |
-| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                         |
-| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                            |
-| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                                    |
-| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                              |
-| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                                     |
-| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                                    |
-| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                            |
-| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                            |
-| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                                 |
-| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                                |
+| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                            |
+| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `.qlog`                                                                                             | QLog files used to debug MASQUE connection issues.                                                                                                                                                                                                                                                                                                     |
+| `.pcap`                                                                                             | Packet capture (PCAP) files manually generated using `warp-cli debug pcap` commands, or automatically generated via [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                         |
+| `.etl`                                                                                              | Windows-only trace files generated by [extra debug logging](#extra-debug-logging), containing packet captures, `netsh` TCPIP traces, and Windows Filtering Platform (WFP) captures.                                                                                                                                                                                                 |
+| `.xml`                                                                                              | Windows-only WFP trace files generated by [extra debug logging](#extra-debug-logging).                                                                                                                                                                                                                                                                     |
+| `alternate-networks-check.txt`                                                                      | Connectivity status for each [managed network](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks/).                                                                                                                                                                                                                      |
+| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                            |
+| `bound-dns-ports.txt`                                                                               | Active processes on port `53`.                                                                                                                                                                                                                                                                                                                         |
+| `captive-portal-hotspot-detect.txt`                                                                 | HTTP response of `captive.apple.com`                                                                                                                                                                                                                                                                                                                   |
+| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#connectivity-checks). Can be used to determine whether traffic is routing through the WARP tunnel.                                                                                                   |
+| `*-checks-*.txt`                                                                                    | One-shot connectivity checks that run when [extra debug logging](#extra-debug-logging) is first enabled. These contain the same information as `connectivity.txt`.                                                                                                                                                                                                                 |
+| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** is enabled in the Cloudflare One Client.                                                                                                                                                                                                                                                             |
+| `daemon.log`                                                                                        | Detailed log of all actions performed by the Cloudflare One Client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                       |
+| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                              |
+| `dex.log`                                                                                           | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution.                                                                                                                                                                                                                                                                             |
+| `dhcp-lease-plists.txt`                                                                             | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease.                                                                                                                                                                                                                                                     |
+| `dhcp-lease.txt`                                                                                    | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux).                                                                                                                                                                                                                                                                                     |
+| `dig.txt`                                                                                           | DNS lookup query output for `cloudflare.com` and `apple.com`.                                                                                                                                                                                                                                                                                          |
+| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by the Cloudflare One Client, generated every two minutes.                                                                                                                                                                                                                                         |
 | `dns-check.txt`                                                                                     | Verifies that the Cloudflare One Client DNS servers are set as system default. For [operating modes](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) where DNS filtering is enabled, this file contains the IPs of the local DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                       |
-| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                                  |
-| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                       |
-| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                           |
-| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                                 |
-| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                            |
-| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                           |
-| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                                   |
-| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                               |
-| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                               |
-| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                                  |
-| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                             |
-| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                                   |
-| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                         |
-| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                        |
-| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                        |
-| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                           |
-| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                             |
-| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                              |
-| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
-| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                          |
-| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                            |
-| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                                 |
-| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                                              |
-| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                    |
-| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                                     |
-| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                                  |
-| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                                   |
-| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                                   |
-| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                                 |
-| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                               |
-| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                                   |
-| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                                   |
-| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                                     |
-| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                                     |
-| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                              |
-| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                       |
-| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                  |
-| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                        |
-| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                       |
-| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                               |
-| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                          |
-| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                          |
-| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                             |
-| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                                           |
-| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                         |
-| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                                     |
-| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                                      |
-| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                              |
-| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                         |
+| `dynamic.log`                                                                                       | Reserved for use by Cloudflare Support.                                                                                                                                                                                                                                                                                                                |
+| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                           |
+| `firewall-pfctl-all.txt`                                                                            | Packet filter (pf) firewall configuration (macOS only).                                                                                                                                                                                                                                                                                                |
+| `firewall-rules.txt`                                                                                | The [system firewall rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#system-firewall) configured by the Cloudflare One Client.                                                                                                                                                                  |
+| `gui-launcher.log`                                                                                  | macOS console log showing application launch.                                                                                                                                                                                                                                                                                                          |
+| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                                     |
+| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                                    |
+| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                            |
+| `installed_applications.txt`                                                                        | List of installed applications.                                                                                                                                                                                                                                                                                                                        |
+| `installed_cert.pem`                                                                                | [Root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) installed on the system.                                                                                                                                                                                                                                        |
+| `installer.log` <br/> `msi-installer.log`                                                           | MSI or PKG installation log.                                                                                                                                                                                                                                                                                                                           |
+| `InstallHistory.plist` <br/> `macos_installer.log`                                                  | macOS software installation logs.                                                                                                                                                                                                                                                                                                                      |
+| `ipc.log`                                                                                           | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon.                                                                                                                                                                                                            |
+| `kernel-modules.txt`                                                                                | List of loaded kernel modules (macOS and Linux) or drivers (Windows).                                                                                                                                                                                                                                                                                  |
+| `launchd-dumpstate.txt`                                                                             | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies.                                                                                                                                                                                                                                                 |
+| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`                                        | [Managed deployment parameters](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                                  |
+| `lsb-release.txt`                                                                                   | Output from the `lsb_release` command (Linux only).                                                                                                                                                                                                                                                                                                    |
+| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                                      |
+| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                                       |
+| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
+| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                                   |
+| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                                     |
+| `route.txt`                                                                                         | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration.                                                                                          |
+| `route-change.log`                                                                                  | Changes to the IP routing table.                                                                                                                                                                                                                                                                                                            |
+| `scutil-dns.txt`                                                                                    | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                             |
+| `scutil-networkinfo.txt`                                                                            | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows).                                                                                                                                                                                                                                              |
+| `scutil-proxy.txt`                                                                                  | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                           |
+| `snapshots-collection.log`                                                                          | Logs generated when collecting `snapshots/*.log`. Used to debug why the Cloudflare One Client failed to collect a snapshot.                                                                                                                                                                                                                            |
+| `snapshots/*.log`                                                                                   | Diagnostics generated when an error occurs.                                                                                                                                                                                                                                                                                                            |
+| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                                          |
+| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                                        |
+| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                            |
+| `system-extension-diagnostics.txt`                                                                  | Status and health of loaded system extensions (macOS only).                                                                                                                                                                                                                                                                                            |
+| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                              |
+| `System.evtx`                                                                                       | Windows system event log.                                                                                                                                                                                                                                                                                                                              |
+| `taskdump.log`                                                                                      | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks.                                                                                                                                                                                                       |
+| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                                |
+| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                            |
+| `*-traceroute-*.txt`                                                                                | One-shot traceroute to Tunnel edge connection IPs, Device API endpoint hostname and IPs, and DNS resolver hostname and IPs; started when [extra debug logging](#extra-debug-logging) is first enabled.                                                                                                                                                             |
+| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                                |
+| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                                        |
+| `version.txt`                                                                                       | [Cloudflare One Client version](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) installed on the device.                                                                                                                                                                                                                               |
+| `warp-account.txt`                                                                                  | Cloudflare One Client device enrollment information.                                                                                                                                                                                                                                                                                                   |
+| `warp-bus-metrics.txt`                                                                              | Metrics for the internal message bus framework used by the Cloudflare One Client.                                                                                                                                                                                                                                                                      |
+| `warp-device-posture.txt`                                                                           | Current [device posture](/cloudflare-one/reusable-components/posture-checks/client-checks/) status.                                                                                                                                                                                                                                               |
+| `warp-dex-data.txt`                                                                                 | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses.                                                                                                                                                                                                                                                  |
+| `warp-dns-fallbacks.txt`                                                                            | List of default DNS fallbacks used by the WARP DNS proxy.                                                                                                                                                                                                                                                                                              |
+| `warp-dns-lock.json`                                                                                | Default DNS providers and network interface information.                                                                                                                                                                                                                                                                                               |
+| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                                       |
+| `warp-network.txt`                                                                                  | Network settings on the device detected by the Cloudflare One Client.                                                                                                                                                                                                                                                                                  |
 | `warp-settings.txt`                                                                                 | [Cloudflare One Client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/) applied to the device.                                                                                                                                                                                                                 |
-| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                                     |
-| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                               |
-| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                               |
-| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                                      |
+| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                              |
+| `warp-status.txt`                                                                                   | Status of the Cloudflare One Client connection (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                        |
+| `wdutil-info.txt`                                                                                   | Wi-Fi diagnostics (macOS only).                                                                                                                                                                                                                                                                                                                        |
+| `xpc-launchd.log`                                                                                   | Most recent log file for the `launchd` process on macOS.                                                                                                                                                                                                                                                                                               |
 
 #### Multiple versions of the same log
 
@@ -161,14 +161,14 @@ This enables a few more logging features:
 - DNS logs for [service modes with DNS filtering](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/)
 - One-shot connectivity checks (same information as `connectivity.txt`, collected when extra debug logging starts rather than when `warp-diag` runs)
 - One-shot traceroutes to:
-  - DNS resolver IPs
-  - DNS resolver hostname
-  - Device API endpoint IPs
-  - Device API endpoint hostname
-  - Tunnel edge connection IPs
+	- DNS resolver IPs
+	- DNS resolver hostname
+	- Device API endpoint IPs
+	- Device API endpoint hostname
+	- Tunnel edge connection IPs
 - On Windows, if you are an administrator:
-  - [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
-  - [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
+	- [`netsh` trace](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-trace) with the `Microsoft-Windows-TCPIP` provider
+	- [WFP capture](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-wfp)
 
 If extra debug logging is enabled, the command `warp-cli debug extra reconnect` forces the tunnel connection to restart.
 This can be useful for collecting log information if the tunnel connection fails.
@@ -246,19 +246,19 @@ The following log files are available for iOS, Android, and ChromeOS devices.
 
 #### iOS
 
-| Name                 | Description                                                                                                                                                                                 |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Extension logs**   | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
-| **Application logs** | Logs from the iOS app process, including GUI events, setting changes, and API calls.                                                                                                        |
-| **Qlogs**            | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID.                                                    |
+| Name                                    | Description           |
+| --------------------------------------- | ------------------------------------ |
+| **Extension logs**                          | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                   |
+| **Application logs**                        | Logs from the iOS app process, including GUI events, setting changes, and API calls.                         |
+| **Qlogs**                                  | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. Archive contains up to 10 `.sqlog` files named by connection ID. |
 
 #### Android/ChromeOS
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| Name                      | Description                                                                                                                                                                                 |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `unhandled_exception.log` | Captures errors in the Android application layer that were not caught and could have crashed the app.                                                                                       |
-| `console.log`             | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes.                                                |
-| `native_tunnel.log`       | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file. |
-| `<connection_id>.sqlog`   | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections.                                                                                                                     |
+| Name             | Description                           |
+| ---------------- | ---------------------------------------------------- |
+| `unhandled_exception.log`   | Captures errors in the Android application layer that were not caught and could have crashed the app.                                |
+| `console.log` | Logs from the Android application layer, including VPN service events, API calls, failed DNS queries, GUI interactions, and setting changes. |
+| `native_tunnel.log`  | Logs from the core VPN tunnel service, including connection state changes and packet flow operations between the device and Cloudflare's network. Similar to the desktop `daemon.log` file.                        |
+| `<connection_id>.sqlog`    | QUIC protocol event logs used to debug MASQUE/HTTP3 tunnel connections. |
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
index 80e66ab48ee8d61..e4307d464bc1c09 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx
@@ -20,13 +20,13 @@ A single physical device can have [multiple device registrations](/cloudflare-on
 
 ## Key concepts
 
-| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                   |
-| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                         |
-| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                             |
-| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                  |
-| Device registration                                                                  | An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
-| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                       |
+| Concept                                                                              | Definition                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [User](/cloudflare-one/team-and-resources/users/seat-management/#manage-users)       | A person whose identity is verified through your identity provider (IdP) and who can enroll devices in your Zero Trust organization.                                                                                                                                                                                                                                            |
+| [Seat](/cloudflare-one/team-and-resources/users/seat-management/)                    | A billable unit consumed when a user authenticates to your Zero Trust organization. Each user occupies one seat regardless of how many devices they enroll. Service tokens do not consume seats.                                                                                                                                                                                |
+| [Service token](/cloudflare-one/access-controls/service-credentials/service-tokens/) | Credentials used by automated systems to authenticate against your Cloudflare One policies.                                                                                                                                                                                                                                                                             |
+| Device registration                                                                  |  An individual session of the Cloudflare One Client on a physical device, with its own public key, [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), and [virtual IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) (one IPv4 and one IPv6). |
+| [Session](/cloudflare-one/access-controls/access-settings/session-management/)       | A time-limited JSON Web Token (JWT) that controls how long a user can access an Access application before re-authenticating. Unlike sessions, a device registration is persistent — it does not expire and exists until you delete it.                                                                                                                                                                |
 
 ## Review device registration status
 
@@ -102,20 +102,20 @@ If the user or service token can successfully re-authenticate, a new device regi
 
 Registrations can have the following statuses:
 
-| Status      | Description                                                                                                  |
-| ----------- | ------------------------------------------------------------------------------------------------------------ |
-| **Active**  | Registered and able to connect via the Cloudflare One Client. This is the expected operational state.        |
+| Status | Description |
+| --- | --- |
+| **Active** | Registered and able to connect via the Cloudflare One Client. This is the expected operational state. |
 | **Revoked** | The registration's public key is invalidated. Revocation does not release the assigned virtual IP addresses. |
 
 ## Manage device registrations
 
 The following table summarizes the actions available for managing device registrations and devices. For all actions, if the user or service token can still re-authenticate, a new registration will be created automatically. To permanently remove access, refer to [Device management](#device-management).
 
-| Action                                                 | What it does                                                                                             | Virtual IPs released? | When to use                                                                                  |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------- |
-| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                   | You want to fully remove a user's enrollment from a device and free up the virtual IP.       |
-| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                    | You want to temporarily block a device from connecting but preserve the registration record. |
-| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes                   | You want to fully remove a device and all associated registrations.                          |
+| Action                                                 | What it does                                                                                             | Virtual IPs released?                                  | When to use                                                                                                                                                                                  |
+| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Delete a registration](#delete-a-device-registration) | Permanently removes a single device registration and its configuration.                                  | Yes                                                    | You want to fully remove a user's enrollment from a device and free up the virtual IP.                                                                                                       |
+| [Revoke a registration](#revoke-a-device-registration) | Invalidates the registration's public key, blocking it from connecting. The registration record remains. | No                                                     | You want to temporarily block a device from connecting but preserve the registration record. |
+| [Delete a device](#delete-a-device)                    | Removes the physical device record and all its associated registrations.                                 | Yes | You want to fully remove a device and all associated registrations.                                                                                                                 |
 
 ### Delete a device registration
 
@@ -213,9 +213,8 @@ To block a service token from re-authenticating, you must either:
 
 1. Delete the enrollment policy associated with the token, or modify the enrollment policy to no longer include the token (by removing its specific Include rule).
 2. (Optional) [Delete the service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).
-   <br /> You cannot use this service token to create new registrations.
-   <br /> You cannot delete a service token while it is attached to a device
-   enrollment policy.
+      <br/> You cannot use this service token to create new registrations.
+      <br/> You cannot delete a service token while it is attached to a device enrollment policy.
 3. Delete the service token [device registration](/cloudflare-one/team-and-resources/devices/device-registration/#delete-a-device-registration).
 4. (Optional) To fully decommission a device, [remove user access](/cloudflare-one/team-and-resources/devices/device-registration/#remove-user-access), if any exists. Devices with existing registrations will remain connected to Cloudflare until those specific device registrations are manually deleted.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
index 8e70dfe2c679456..55005c37db7e2b8 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx
@@ -26,12 +26,12 @@ Review how this change impacts certificate propagation to your end-user devices
 
 Zero Trust will indicate if a certificate is ready for use in inspection based on its deployment status:
 
-| Deployment status    | Description                                                                                                                                                                |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                             |
-| Pending              | The certificate is being activated or deactivated for use.                                                                                                                 |
+| Deployment status    | Description                                                                                                                                                      |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Inactive             | The certificate has been generated by or uploaded to Cloudflare but is not deployed across the global network.                                                   |
+| Pending              | The certificate is being activated or deactivated for use.                                                                                                       |
 | Available            | The certificate is deployed across the Cloudflare global network and ready to be turned on. The Cloudflare One Client will install the certificate on your users' devices. |
-| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                             |
+| Available and In-Use | The certificate is turned on. Gateway will use the certificate for inspection.                                                                                   |
 
 ## Generate a Cloudflare root certificate
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
index 8d64d7b39cd4c59..08917bf7ed0f8f9 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx
@@ -754,115 +754,115 @@ To install a certificate for use in a Docker container:
 4. Add the certificate to your Docker image:
 
    <Tabs> <TabItem label="During build process">
-   
-      To add the certificate to your Dockerfile to install it during the build process:
-      1. Add the certificate install directions to your Dockerfile. For example:
-   
-         ```docker title="Red Hat-based images"
-         FROM registry.access.redhat.com/ubi9/ubi:latest
-         # Or FROM centos:7 or FROM fedora:38
-   
-         # Install necessary certificates package
-         RUN dnf install -y ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
-         RUN update-ca-trust extract
-         ```
-   
-         ```docker title="Debian-based images"
-         FROM debian:12
-         # Or FROM ubuntu:22.04
-   
-         # Install necessary certificates package
-         RUN apt-get update && apt-get install -y ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-         RUN update-ca-certificates
-         ```
-   
-         ```docker title="Alpine-based images"
-         FROM alpine:3.18
-   
-         # Install necessary certificates package
-         RUN apk add --no-cache ca-certificates
-   
-         # Copy and add Cloudflare root certificate
-         COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
-         RUN update-ca-certificates
-         ```
-   
-      2. Build the Docker image:
-   
-         ```sh
-         docker build -t <your-container-name> .
-         ```
-   
-      3. Verify the certificate was installed:
-   
-         ```sh title="Red Hat-based images"
-         docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-         ```
-   
-         ```sh title="Debian and Alpine-based images"
-         docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
-         ```
-   
-      </TabItem>
-   
-      <TabItem label="During runtime">
-   
-      To add the certificate to your Docker Compose file to install it during runtime:
-      1. Add the certificate install directions to your `docker-compose.yml` file. For example:
-   
-         ```yaml title="Red Hat-based containers"
-         version: '3'
-         services:
-         	redhat-app:
-         		image: registry.access.redhat.com/ubi9/ubi:latest
-          		volumes:
-          			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
-          		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
-         ```
-   
-         ```yaml title="Debian-based containers"
-         version: '3'
-         services:
-         	debian-app:
-         		image: debian:12
-          		volumes:
-          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
-          		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
-         ```
-   
-         ```yaml title="Alpine-based containers"
-         version: '3'
-         services:
-         	alpine-app:
-         		image: alpine:3.18
-          		volumes:
-          			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
-          		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
-         ```
-   
-      2. Run the container:
-   
-         ```sh
-         docker-compose up
-         ```
-   
-      3. Verify the certificate was installed:
-   
-         ```sh title="Red Hat-based containers"
-         docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
-         ```
-   
-         ```sh title="Debian and Alpine-based containers"
-         docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
-         ```
-   
-      </TabItem> </Tabs>
+
+   To add the certificate to your Dockerfile to install it during the build process:
+   1. Add the certificate install directions to your Dockerfile. For example:
+
+      ```docker title="Red Hat-based images"
+      FROM registry.access.redhat.com/ubi9/ubi:latest
+      # Or FROM centos:7 or FROM fedora:38
+
+      # Install necessary certificates package
+      RUN dnf install -y ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /etc/pki/ca-trust/source/anchors/certificate.crt
+      RUN update-ca-trust extract
+      ```
+
+      ```docker title="Debian-based images"
+      FROM debian:12
+      # Or FROM ubuntu:22.04
+
+      # Install necessary certificates package
+      RUN apt-get update && apt-get install -y ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+      RUN update-ca-certificates
+      ```
+
+      ```docker title="Alpine-based images"
+      FROM alpine:3.18
+
+      # Install necessary certificates package
+      RUN apk add --no-cache ca-certificates
+
+      # Copy and add Cloudflare root certificate
+      COPY certs/certificate.pem /usr/local/share/ca-certificates/certificate.crt
+      RUN update-ca-certificates
+      ```
+
+   2. Build the Docker image:
+
+      ```sh
+      docker build -t <your-container-name> .
+      ```
+
+   3. Verify the certificate was installed:
+
+      ```sh title="Red Hat-based images"
+      docker run --rm your-image-name sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+      ```
+
+      ```sh title="Debian and Alpine-based images"
+      docker run --rm your-image-name sh -c "cat /etc/ssl/certs/certificate.pem"
+      ```
+
+   </TabItem>
+
+   <TabItem label="During runtime">
+
+   To add the certificate to your Docker Compose file to install it during runtime:
+   1. Add the certificate install directions to your `docker-compose.yml` file. For example:
+
+      ```yaml title="Red Hat-based containers"
+      version: '3'
+      services:
+      	redhat-app:
+      		image: registry.access.redhat.com/ubi9/ubi:latest
+       		volumes:
+       			- certs/certificate.pem:/etc/pki/ca-trust/source/anchors/certificate.pem
+       		entrypoint: /bin/sh -c "dnf install -y ca-certificates && update-ca-trust extract && app start"
+      ```
+
+      ```yaml title="Debian-based containers"
+      version: '3'
+      services:
+      	debian-app:
+      		image: debian:12
+       		volumes:
+       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.crt
+       		entrypoint: /bin/sh -c "apt-get update && apt-get install -y ca-certificates && update-ca-certificates && app start"
+      ```
+
+      ```yaml title="Alpine-based containers"
+      version: '3'
+      services:
+      	alpine-app:
+      		image: alpine:3.18
+       		volumes:
+       			- certs/certificate.pem:/usr/local/share/ca-certificates/certificate.pem
+       		entrypoint: /bin/sh -c "apk add --no-cache ca-certificates && update-ca-certificates && app start"
+      ```
+
+   2. Run the container:
+
+      ```sh
+      docker-compose up
+      ```
+
+   3. Verify the certificate was installed:
+
+      ```sh title="Red Hat-based containers"
+      docker exec -it <container-name> sh -c "cat /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | grep Cloudflare"
+      ```
+
+      ```sh title="Debian and Alpine-based containers"
+      docker exec -it <container-name> sh -c "cat /etc/ssl/certs/ca-certificates.crt | grep Cloudflare"
+      ```
+
+   </TabItem> </Tabs>
 
 ### Command-line tools
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
index 442499bd33c48ff..5ec0ab6973dad12 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx
@@ -61,17 +61,16 @@ While the Okta integration is turned on, Cloudflare One will send any user risk
 ## Predefined risk behaviors
 
 By default, all predefined behaviors are disabled. When a behavior is enabled, Cloudflare One will continuously evaluate all users within the organization for the behavior. You can [change the risk level](#change-risk-behavior-risk-levels) for predefined behaviors if the default assignment does not suit your environment.
-| Risk behavior | Requirements | Description | Evaluation timing |
+| Risk behavior                         | Requirements                                                                                                | Description                                                                                                                                                                                                            | Evaluation timing |
 | -------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
-| Impossible travel | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/) | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
-| High number of DLP policies triggered | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/) | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/). | Evaluated per-request in milliseconds. |
-| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
+| Impossible travel                      | [A configured Access application](/cloudflare-one/access-controls/applications/http-apps/)                                            | User has a successful login from two different locations that they could not have traveled between in that period of time. Matches will appear in your [Access authentication logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/). | Evaluated at each authentication and session-refresh event. |
+| High number of DLP policies triggered  | [A configured DLP profile](/cloudflare-one/data-loss-prevention/dlp-profiles/)                     | User has created a high number of DLP policy matches within a narrow frame of time. Matches will appear in your [Gateway activity logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/).                                  | Evaluated per-request in milliseconds. |
+| SentinelOne threat detected on machine | [SentinelOne service provider integration](/cloudflare-one/integrations/service-providers/sentinelone/) | SentinelOne returns one or more configured [device posture attributes](/cloudflare-one/integrations/service-providers/sentinelone/#device-posture-attributes) for a user.                                          | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with SentinelOne's API rate limits. |
 | CrowdStrike Low ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 0-50 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information.| Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | CrowdStrike Medium ZTA security score| [CrowdStrike integration](/cloudflare-one/integrations/service-providers/crowdstrike/)| A user's device reports a score between 50-79 for any CrowdStrike Zero Trust Assessment attribute (OS Score, Overall Score, or Sensor Config score). Refer to [CrowdStrike device posture attributes](/cloudflare-one/integrations/service-providers/crowdstrike/#device-posture-attributes) for more information. | Ingested via service-to-service API. Frequency is administrator-configurable during device posture setup to align with CrowdStrike's API rate limits. |
 | Interaction with Malicious File | [Gateway AV scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/) or [File sandboxing](/cloudflare-one/traffic-policies/http-policies/file-sandboxing/) | User uploads or downloads a file flagged as malicious by Gateway's AV scanner or file sandboxing. Risk is elevated even if the file is blocked. | Evaluated per-request in milliseconds. |
-| Suspicious Security Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
-
+| Suspicious Security Domain Visited  | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as a security risk or security threat. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
+| High Risk Domain Visited | [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/)    | User visits a domain categorized as questionable content, violence, or CIPA. Refer to [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for the full list. Risk is elevated even if the traffic is blocked. | Evaluated per-request in milliseconds. |
 ## Manage risk behaviors
 
 To toggle risk behaviors, go to **Risk score** > **Risk behaviors**.
@@ -93,9 +92,9 @@ You can change the risk level for a behavior at any time.
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Teams & Resources**.
 2. Go to **Users**.
 3. Select **Risk score** > **Risk behaviors**.
-4. Select the risk behavior you want to modify.
-5. In the drop-down menu, choose your desired risk level.
-6. Select **Save**.
+2. Select the risk behavior you want to modify.
+3. In the drop-down menu, choose your desired risk level.
+4. Select **Save**.
 
 ## Use risk scores in Access policies
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
index 2ce86cab7d6270b..c8ace201fdac273 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/scim.mdx
@@ -8,9 +8,10 @@ tags:
   - SCIM
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers to synchronize user identity information with cloud applications and services. After configuring SCIM, user identities that you create, edit, or delete in the identity provider are automatically updated across all supported applications. This makes it easier for IT admins to onboard new users, update their groups and permissions, and revoke access in the event of an employee termination or security breach.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
index 2f4b39bfbcd969d..1cf937a40bfe8b7 100644
--- a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
+++ b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 4
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 User logs show a list of all users who have authenticated to Cloudflare One. For each user who has logged in, you can view their enrolled devices, login history, seat usage, and identity used for policy enforcement.
 
@@ -20,7 +20,7 @@ This page lists all users who have registered the Cloudflare One Client or authe
 
 ### Available logs
 
-- **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
-- **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
-- **Devices**: Devices registered to the user via the Cloudflare One Client.
-- **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
+* **User Registry identity**: Select the user's name to view their last seen identity. This identity is used to evaluate Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/). A refresh occurs when the user re-authenticates the device client, logs into an Access application, or has their IdP group membership updated via <GlossaryTooltip term="SCIM" link="/cloudflare-one/team-and-resources/users/scim/">SCIM provisioning</GlossaryTooltip>. To track how the user's identity has changed over time, go to the **Audit logs** tab.
+* **Session identities**: The user's active sessions, the identity used to authenticate each session, and when each session will [expire](/cloudflare-one/access-controls/access-settings/session-management/).
+* **Devices**: Devices registered to the user via the Cloudflare One Client.
+* **Recent activities**: The user's five most recent Access login attempts. For more details, refer to your [authentication audit logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs).
diff --git a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
index f788aa791bdb0b6..64308a2ccb340c0 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/global-policies.mdx
@@ -38,8 +38,8 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 | Resolve nel.cloudflare.com through 1.1.1.1                                                | `00000001-0034-45a0-8333-f339451fba46` | `nel.cloudflare.com`                                                                                                                                      | resolve |
 | Allow DNS queries for api.cloudflare.com domain                                           | `00000001-5eea-4932-8dd5-8e1ec9770396` | `api.cloudflare.com`                                                                                                                                      | allow   |
 | Resolve api.cloudflare.com through 1.1.1.1                                                | `00000001-4f0c-4f86-9b96-5d26123a194b` | `api.cloudflare.com`                                                                                                                                      | resolve |
-| Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                                 | allow   |
-| Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                                 | resolve |
+| Allow DNS queries for one.dash.cloudflare.com domain                                    | `00000001-0f75-48a9-b3e1-925a974d2b65` | `one.dash.cloudflare.com`                                                                                                                               | allow   |
+| Resolve one.dash.cloudflare.com through 1.1.1.1                                         | `00000001-3d84-41a6-bc84-3014685c0d81` | `one.dash.cloudflare.com`                                                                                                                               | resolve |
 | Allow DNS queries for one.dash.cloudflare.com domain                                      | `00000001-a9fd-40de-a662-51d3a3ae0ad8` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | allow   |
 | Resolve one.dash.cloudflare.com through 1.1.1.1                                           | `00000001-70f2-4eea-b711-201bca434ed4` | `one.dash.cloudflare.com` and `one.dash.fed.cloudflare.com`                                                                                               | resolve |
 | Allow DNS queries for dash.cloudflare.com domain                                          | `00000001-0c2a-4b31-8606-3e5a1d87c1bf` | `dash.cloudflare.com` and `dash.fed.cloudflare.com`                                                                                                       | allow   |
@@ -59,14 +59,14 @@ Gateway enforces global DNS and resolver policies before any other policies. Thi
 
 ## Network proxy policies
 
-| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                  | Action | Description                                                                                                                                                   |
-| --------------------------------------------------- | -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                 | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
-| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows Zero Trust client.                                                                                                                                     |
-| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                          | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
+| Name                                                | ID                                     | Criteria | Value                                                                                                                                                                                                                                                                                                                                                                                                    | Action | Description                                                                                                                                                   |
+| --------------------------------------------------- | -------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Allow CF Network Error Logging L4                   | `00000001-e4af-4b82-8f8c-c79c1d5d212e` | Hostname | `*.nel.cloudflare.com`                                                                                                                                                                                                                                                                                                                                                                                   | allow  | Allows SNI domains for Cloudflare One Client registration.                                                                                                    |
+| Allow CF Client                                     | `00000001-8c3d-4e27-a01b-af8418000077` | Hostname | `*.cloudflareclient.com` and `*.fed.cloudflareclient.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows Zero Trust client.                                                                                                                                     |
+| Allow Gateway Proxy PAC                             | `00000001-776e-438d-9856-987d7053762b` | Hostname | `*.cloudflare-gateway.com` and `*.fed.cloudflare-gateway.com`                                                                                                                                                                                                                                                                                                                                            | allow  | Allows Gateway proxy with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/).                                                       |
 | Allow Zero Trust Services                           | `00000001-e1e8-421b-a0fe-895397489f28` | Hostname | `one.dash.cloudflare.com`, `help.teams.cloudflare.com`, `blocked.teams.cloudflare.com`, `blocked.teams.fed.cloudflare.com`, `api.cloudflare.com`, `api.fed.cloudflare.com`, `cloudflarestatus.com`, `www.cloudflarestatus.com`, `one.dash.cloudflare.com`, `one.dash.fed.cloudflare.com`, `help.one.cloudflare.com`, `dash.cloudflare.com`, `dash.fed.cloudflare.com`, and `developers.cloudflare.com` | allow  | Allows Cloudflare Zero Trust services.                                                                                                                        |
-| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                              | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
-| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                              | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
+| Allow Access Apps L4                                | `00000001-daa2-41e2-8a88-698af4066951` | Hostname | `*.cloudflareaccess.com` and `*.fed.cloudflareaccess.com`                                                                                                                                                                                                                                                                                                                                                | allow  | Allows [Cloudflare Access](/cloudflare-one/access-controls/policies/) applications.                                                                           |
+| Allow HTTP requests to browser-rendered Access Apps | `00000001-1f93-4476-8f92-9aa4407d1c5f` | Hostname | `*.zero-trust-apps.cfdata.org`, `*.zero-trust-apps-staging.cfdata.org`, `*.zero-trust-apps.fed.cfdata.org`, or `*.zero-trust-apps-staging.fed.cfdata.org`                                                                                                                                                                                                                                                | allow  | Allows Cloudflare Access terminal applications [rendered in a browser](/cloudflare-one/access-controls/applications/non-http/browser-rendering/#ssh-and-vnc). |
 
 ## HTTP inspection policies
 
diff --git a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
index 2df964a6c3a878e..84848c8086de50c 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/network-policies/protocol-detection.mdx
@@ -50,15 +50,15 @@ To use HTTP policies to filter all HTTPS traffic on all ports when using a defau
 
 Gateway supports detection and filtering of the following protocols:
 
-| Protocol     | Notes                                                                                        |
-| ------------ | -------------------------------------------------------------------------------------------- |
-| HTTP         | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
-| HTTP2        | Hypertext Transfer Protocol Version 2.                                                       |
-| SSH          | Secure Shell Protocol — remote login and command execution.                                  |
-| TLS          | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
-| DCERPC       | Distributed Computing Environment / Remote Procedure Call.                                   |
-| MQTT         | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
-| TPKT         | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
+| Protocol                                                          | Notes                                                                                        |
+| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| HTTP                                                              | Hypertext Transfer Protocol (HTTP/1.1).                                                      |
+| HTTP2                                                             | Hypertext Transfer Protocol Version 2.                                                       |
+| SSH                                                               | Secure Shell Protocol — remote login and command execution.                                  |
+| TLS                                                               | Transport Layer Security. Gateway detects TLS versions 1.1 through 1.3 with the _TLS_ value. |
+| DCERPC                                                            | Distributed Computing Environment / Remote Procedure Call.                                   |
+| MQTT                                                              | Message Queuing Telemetry Transport — lightweight IoT messaging protocol.                    |
+| TPKT                                                              | TPKT commonly initiates RDP sessions, so you can use it to identify and filter RDP traffic.  |
 | IMAP         | Internet Message Access Protocol — email retrieval.                                          |
 | POP3         | Post Office Protocol v3 — email retrieval.                                                   |
 | SMTP         | Simple Mail Transfer Protocol — email sending.                                               |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
index da83a0d0f8b94ed..61657d39a175ca7 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/packet-filtering/best-practices/magic-transit-egress.mdx
@@ -17,7 +17,7 @@ For Magic Transit egress traffic, consider the following:
 - Network Firewall rules apply to both Magic Transit ingress and egress traffic passing through Cloudflare.
 - If you have a "default drop" catchall rule (a final rule that blocks all traffic not matched by earlier rules) for ingress traffic, you must add an earlier rule to permit traffic sourced from your Magic Transit prefix with the destination as **any** to allow outbound egress traffic.
 
-  For example, place the following allow rule before any default-drop catchall rule:
+   For example, place the following allow rule before any default-drop catchall rule:
 
-  **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
-  **Action**: Allow
+   **Match**: `ip.src in {<YOUR_MAGIC_TRANSIT_PREFIX>}` <br/>
+   **Action**: Allow
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
index 7ad5f83b0ccb97c..353d64288db846e 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/index.mdx
@@ -22,9 +22,9 @@ There are two approaches for setting up tiered policies, depending on your deplo
 ## Organizations vs. Tenant API
 
 | Feature                    | [Cloudflare Organizations](/cloudflare-one/traffic-policies/tiered-policies/organizations/) | [Tenant API](/cloudflare-one/traffic-policies/tiered-policies/tenant-api/) |
-| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                   |
-| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                    |
-| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                |
-| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                   |
-| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                            |
+| -------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
+| **Supported policy types** | DNS, Network, HTTP, Resolver                                                                | DNS only                                                                         |
+| **Account model**          | Source / Recipient accounts                                                                 | Parent / Child accounts                                                          |
+| **Shareable settings**     | Block pages, extended email matching                                                        | Block pages                                                                      |
+| **Setup**                  | Dashboard (self-serve)                                                                      | API-only                                                                         |
+| **Availability**           | Enterprise (beta)                                                                           | Enterprise (GA)                                                                  |
diff --git a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
index 558bcf16daff10b..61dee092052c3ac 100644
--- a/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
+++ b/src/content/docs/cloudflare-one/traffic-policies/tiered-policies/tenant-api.mdx
@@ -21,6 +21,7 @@ The Tenant API platform only supports [DNS policies](/cloudflare-one/traffic-pol
 
 For more information, refer to the [Cloudflare Zero Trust for managed service providers](https://blog.cloudflare.com/gateway-managed-service-provider/) blog post.
 
+
 ## Get started
 
 To set up the Tenant API, refer to [Get started](/tenant/get-started/). Once you have provisioned and configured your customer's Cloudflare accounts, you can create [DNS policies](/cloudflare-one/traffic-policies/dns-policies/).
diff --git a/src/content/docs/cloudflare-one/troubleshooting/access.mdx b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
index b8ece1182ed0454..b6396e705f97636 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/access.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/access.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Access troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/access-controls/troubleshooting/">
-	Full Access troubleshooting guide ❯
+  Full Access troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
index e4cf3238d0cd8bd..c31dd68373abe7a 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Browser Isolation documentation.
 
 <LinkButton href="/cloudflare-one/remote-browser-isolation/troubleshooting/">
-	Browser Isolation troubleshooting ❯
+  Browser Isolation troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
index 72cda8b9e748c03..064db32c9b01121 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/casb.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full CASB documentation.
 
 <LinkButton href="/cloudflare-one/integrations/cloud-and-saas/troubleshooting/">
-	CASB troubleshooting ❯
+  CASB troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
index a15cd8ee067f5b5..304a4016752f5ba 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/contact-support.mdx
@@ -32,15 +32,12 @@ For all issues, please include:
 Depending on the product, providing diagnostic files is critical for a technical investigation.
 
 ### Cloudflare One Client (WARP)
-
 If the issue involves the Cloudflare One Client, run the `warp-diag` command on the affected device and attach the resulting `.zip` file to your case. For more information, refer to [Diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/).
 
 ### Cloudflare Tunnel
-
 If the issue involves Cloudflare Tunnel, run the `cloudflared tunnel diag` command and provide the generated report. For more information, refer to [Tunnel diagnostic logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs/).
 
 ### Access and Gateway
-
 For issues related to authentication loops, blocked websites, or policy enforcement:
 
 - **HAR file**: Provide a [HAR file](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file) captured while reproducing the issue.
@@ -49,7 +46,6 @@ For issues related to authentication loops, blocked websites, or policy enforcem
 - **Request ID**: For Gateway issues, you can find the `request_id` (HTTP logs) or `query_id` (DNS logs) in your [Gateway logs](/cloudflare-one/traffic-policies/troubleshooting/).
 
 ### Digital Experience Monitoring (DEX)
-
 For issues with DEX tests or device monitoring, provide a [remote capture](/cloudflare-one/insights/dex/diagnostics/client-packet-capture/) from the Zero Trust dashboard.
 
 ---
diff --git a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
index 8c96f5ab4305ba3..731999d5fb8036d 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/dex.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full DEX documentation.
 
 <LinkButton href="/cloudflare-one/insights/dex/troubleshooting/">
-	DEX troubleshooting ❯
+  DEX troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
index 690763e57e48c08..c84e1260e343735 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/email-security.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Email Security documentation.
 
 <LinkButton href="/cloudflare-one/email-security/troubleshooting/">
-	Email Security troubleshooting ❯
+  Email Security troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
index 0d5841ea8bb17d1..e38ab6f5acae44e 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/gateway.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Gateway troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/traffic-policies/troubleshooting/">
-	Full Gateway troubleshooting guide ❯
+  Full Gateway troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
index eb881c4c7e9300a..1d692f0aa4341e2 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/tunnel.mdx
@@ -12,25 +12,18 @@ import { Render, LinkButton } from "~/components";
 
 Explore common issues and solutions for Cloudflare Tunnel.
 
-<Render
-	file="tunnel/common-errors"
-	product="cloudflare-one"
-	params={{
-		logsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
-		protocolURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
-		configFileURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
-		originServerNameURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		caPoolURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		noTLSVerifyURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
-		ulimitsURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/",
-	}}
+<Render 
+  file="tunnel/common-errors" 
+  product="cloudflare-one" 
+  params={{
+    logsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/",
+    protocolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/",
+    configFileURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/",
+    originServerNameURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    caPoolURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    noTLSVerifyURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/",
+    ulimitsURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/availability/ulimits/"
+  }} 
 />
 
 ---
@@ -40,5 +33,5 @@ Explore common issues and solutions for Cloudflare Tunnel.
 For more information, refer to the full Tunnel troubleshooting guide.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/">
-	Full Tunnel troubleshooting guide ❯
+  Full Tunnel troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
index 4012b24a1e816aa..82128a0306e3847 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/connectivity.mdx
@@ -15,16 +15,11 @@ import { Render, LinkButton } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		routingBgpLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		routingBgpLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/",
+		checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+		networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
 
@@ -35,5 +30,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/connectivity/">
-	Full connectivity troubleshooting guide ❯
+  Full connectivity troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
index 7cbca452e33919a..0c2b64583258ccf 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/index.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 32
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore resources to help you resolve issues with Cloudflare WAN (formerly Magic WAN) connectivity, routing, and tunnel health.
 
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
index 2787fccd3b01cf7..2499d5ff7d77041 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/ipsec.mdx
@@ -8,20 +8,15 @@ sidebar:
   order: 33
 ---
 
-import { Render, LinkButton } from "~/components";
+import { Render, LinkButton } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/",
+		supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+		tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+		mtuMssLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
 
@@ -32,5 +27,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/ipsec-troubleshoot/">
-	Full IPsec troubleshooting guide ❯
+  Full IPsec troubleshooting guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
index 732752846b608d7..6766ee8164db987 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/routing-bgp.mdx
@@ -11,20 +11,16 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "CF1 Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "CF1 Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
 
 ---
@@ -34,5 +30,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/routing-and-bgp/">
-	Full routing and BGP guide ❯
+  Full routing and BGP guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
index b2a3db82e0e9e8d..4ed284bd72ee49e 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/wan/tunnel-health.mdx
@@ -11,26 +11,19 @@ sidebar:
 import { Render, LinkButton } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-one/networks/connectors/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-one/networks/connectors/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
 
 ---
@@ -40,5 +33,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare WAN documentation.
 
 <LinkButton href="/cloudflare-one/networks/connectors/cloudflare-wan/troubleshooting/tunnel-health/">
-	Full tunnel health guide ❯
+  Full tunnel health guide ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
index a5fe18d5dcf8599..4511789b45bde5c 100644
--- a/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
+++ b/src/content/docs/cloudflare-one/troubleshooting/warp-client.mdx
@@ -19,5 +19,5 @@ import { Render, LinkButton } from "~/components";
 For more information, refer to the full Cloudflare One Client documentation.
 
 <LinkButton href="/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/">
-	Cloudflare One Client troubleshooting ❯
+  Cloudflare One Client troubleshooting ❯
 </LinkButton>
diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
index 8758982fe37aa85..fbfa9dc10b86312 100644
--- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
+++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx
@@ -91,26 +91,26 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
    - `<CLIENT_ID>`: your Entra ID **Application (client) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-      	"$schema": "./node_modules/wrangler/config-schema.json",
-      	"name": "risky-users",
-      	"compatibility_date": "$today",
-      	"main": "src/index.js",
-      	"workers_dev": false,
-      	"account_id": "<ACCOUNT-ID>",
-      	"vars": {
-      		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
-      		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
-      	},
-      	"triggers": {
-      		"crons": ["* * * * *"],
-      	},
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+   	"$schema": "./node_modules/wrangler/config-schema.json",
+   	"name": "risky-users",
+   	"compatibility_date": "$today",
+   	"main": "src/index.js",
+   	"workers_dev": false,
+   	"account_id": "<ACCOUNT-ID>",
+   	"vars": {
+   		"AZURE_AD_TENANT_ID": "<TENANT-ID>",
+   		"AZURE_AD_CLIENT_ID": "<CLIENT-ID>",
+   	},
+   	"triggers": {
+   		"crons": ["* * * * *"],
+   	},
+   }
+   ```
+
+   </WranglerConfig>
 
 :::note
 
diff --git a/src/content/docs/cloudflare-wan/analytics/index.mdx b/src/content/docs/cloudflare-wan/analytics/index.mdx
index 8730a735f15a9f2..7591d777198e731 100644
--- a/src/content/docs/cloudflare-wan/analytics/index.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/index.mdx
@@ -12,8 +12,7 @@ import { Render } from "~/components";
 
 Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance and troubleshoot issues.
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
@@ -22,6 +21,6 @@ Use Cloudflare WAN (formerly Magic WAN) analytics to monitor site performance an
 		traceRoutes: "/cloudflare-wan/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/cloudflare-wan/analytics/query-bandwidth/",
 		graphQlTunnelHealthURL: "/cloudflare-wan/analytics/query-tunnel-health/",
-		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/",
+		siteAnalyticsURL: "/cloudflare-wan/analytics/site-analytics/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
index d02a87f11d097c0..c961a9e26011107 100644
--- a/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/netflow-analytics.mdx
@@ -17,7 +17,6 @@ import { Render } from "~/components";
 	file="mconn/network-options/app-aware-policies/netflow"
 	product="networking-services"
 	params={{
-		breakoutTrafficURL:
-			"/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/",
+		breakoutTrafficURL: "/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
index 3694ed5590489c3..adb2d9fc1ad3f0a 100644
--- a/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/network-analytics.mdx
@@ -13,10 +13,9 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Cloudflare WAN",
+		magicWord: "Cloudflare WAN"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
index 34889d808b65f54..84a4a80f0ea9f2d 100644
--- a/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
index 7ec650366209348..f62f8a3cac1ad1a 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-bandwidth.mdx
@@ -6,12 +6,12 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel bandwidth analytics with GraphQL
 sidebar:
   order: 6
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Cloudflare WAN" }}
 />
diff --git a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
index 2c6eea69fb48cbe..8c71bfa0ecc6910 100644
--- a/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/query-tunnel-health.mdx
@@ -6,12 +6,11 @@ products:
 title: Querying Cloudflare WAN IPsec/GRE tunnel health check results with GraphQL
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Cloudflare WAN" }}
-/>
+	params={{ productName: "Cloudflare WAN" }} />
diff --git a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
index a3c3c203418a701..8a916f198158f40 100644
--- a/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
+++ b/src/content/docs/cloudflare-wan/analytics/site-analytics.mdx
@@ -9,23 +9,21 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare WAN network overview
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions:
-			"Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		instructions: "Refer to [Set up a site](/cloudflare-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
 		magicWord: "Cloudflare WAN",
 		networkOverviewPageName: "Network overview",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
-		setGeoCoordinatesURL:
-			"/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates",
-	}}
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		setGeoCoordinatesURL: "/cloudflare-wan/configuration/common-settings/sites/#set-geographic-coordinates"
+		}}
 />
 
 ### Set thresholds for site health
@@ -35,7 +33,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/changelog.mdx b/src/content/docs/cloudflare-wan/changelog.mdx
index dab8b24716303bb..5e8580b361df863 100644
--- a/src/content/docs/cloudflare-wan/changelog.mdx
+++ b/src/content/docs/cloudflare-wan/changelog.mdx
@@ -12,10 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/cloudflare-wan/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="cloudflare-wan"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="cloudflare-wan" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2025-02-14
 
@@ -81,4 +78,4 @@ Customers using Gateway to filter traffic to Magic WAN destinations will now see
 
 **Network segmentation**
 
-You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
+You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
index 6e7bcd9b792dfd6..1ae5d831a62d218 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/index.mdx
@@ -11,54 +11,35 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/configure-connectors"
+<Render file="mconn/configure-connectors"
 	product="networking-services"
 	params={{
-		magicWord: "hardware",
-		productName: "Cloudflare One Appliance",
-		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-		dashName: "Cloudflare WAN",
-		sfpURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
-		wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-		lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
-		noConnectorShows:
-			"You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
-		networkSegmentationURL:
-			"/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
-		dhcpServerURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
-		dhcpRelayURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
-		reserveIpAddressesURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
-		shippedLanguage:
-			"The Cloudflare One Appliance is shipped to you deactivated",
-		hardSoftConn:
-			"You need to deploy two Appliances in your premises before you can set up a site in high availability.",
-		hcConfigsURL:
-			"/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
-		ipsecTunnelsRefURL:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
-		healthCheckFrequencyURL:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
-		routedSubnetsURL:
-			"/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
-		interruptWindowURL:
-			"/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
-		tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
-		wanSettingsURL:
-			"/cloudflare-wan/configuration/appliance/reference/#wan-settings",
-		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		networkOptionsURL:
-			"/cloudflare-wan/configuration/appliance/network-options/",
-		maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
-		referenceInformationURL:
-			"/cloudflare-wan/configuration/appliance/reference/",
-		troubleshootingURL:
-			"/cloudflare-wan/configuration/appliance/troubleshooting/",
-	}}
-/>
+	magicWord: "hardware",
+	productName: "Cloudflare One Appliance",
+	maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+	dashName: "Cloudflare WAN",
+	sfpURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/",
+	wan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+	lan: "refers to the physical Cloudflare One Appliance Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Appliance. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on hardware support, refer to [SFP+ port information](/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information/).",
+	noConnectorShows: "You need to have bought an Appliance already for it to appear here. Refer to [Prerequisites](#prerequisites) if no Appliance appears in this list.",
+	networkSegmentationURL: "/cloudflare-wan/configuration/appliance/network-options/network-segmentation/",
+	dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation/",
+	shippedLanguage: "The Cloudflare One Appliance is shipped to you deactivated",
+	hardSoftConn: "You need to deploy two Appliances in your premises before you can set up a site in high availability.",
+	hcConfigsURL: "/cloudflare-wan/configuration/appliance/reference/#high-availability-configurations",
+	ipsecTunnelsRefURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+	vlanIdURL: "/cloudflare-wan/configuration/appliance/reference/#vlan-id",
+	healthCheckFrequencyURL: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+	routedSubnetsURL: "/cloudflare-wan/configuration/appliance/network-options/routed-subnets/",
+	interruptWindowURL: "/cloudflare-wan/configuration/appliance/maintenance/interrupt-service-window/",
+	tunnelHealthChecksURL: "/cloudflare-wan/reference/tunnel-health-checks/",
+	wanSettingsURL: "/cloudflare-wan/configuration/appliance/reference/#wan-settings",
+	sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
+	networkOptionsURL: "/cloudflare-wan/configuration/appliance/network-options/",
+  maintenanceURL: "/cloudflare-wan/configuration/appliance/maintenance/",
+  referenceInformationURL: "/cloudflare-wan/configuration/appliance/reference/",
+  troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
index b3fa278d08bae29..71ca26721aa0603 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/configure-hardware-appliance/sfp-port-information.mdx
@@ -4,8 +4,10 @@ description: SFP+ port specifications for the hardware Appliance.
 products:
   - cloudflare-wan
 title: SFP+ port information
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mconn/sfp-port-info" product="networking-services" />
+<Render file="mconn/sfp-port-info"
+	product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
index 8f201a38e5455a4..c37e1581eefa1cb 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/device-metrics.mdx
@@ -14,7 +14,6 @@ import { Render } from "~/components";
 	file="mconn/device-metrics"
 	product="networking-services"
 	params={{
-		troubleshootingURL:
-			"/cloudflare-wan/configuration/appliance/troubleshooting/",
+		troubleshootingURL: "/cloudflare-wan/configuration/appliance/troubleshooting/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
index ffbd3902d481e2e..2de202a6c0d9a45 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/index.mdx
@@ -15,12 +15,9 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		hardwareProductName: "Cloudflare One Appliance",
-		ipsecRefUrl:
-			"/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
-		hardwareUrl:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		ipsecRefUrl: "/cloudflare-wan/configuration/appliance/reference/#security-and-other-information",
+		hardwareUrl: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
 		virtualProductName: "Cloudflare One Virtual Appliance",
-		virtualUrl:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		virtualUrl: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
index 75d2c374e500dc1..f2cfc7422c36ccd 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/activate-appliance.mdx
@@ -12,9 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/activate-connectors"
 	product="networking-services"
 	params={{
-		hardwareConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
-	}}
-/>
+		hardwareConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#activate-appliance",
+		}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
index 2b74af67e463be6..d4cbc5987d03273 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
index 967aa8ccb663c13..071ef98749d5405 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/register-appliance.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/register-hardware-appliance"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)",
+		dashName: "Cloudflare WAN (formerly Magic WAN)"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
index 5b789f4f9046d5d..b53cd5b9f9965c3 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/maintenance/remove-appliances.mdx
@@ -12,6 +12,6 @@ import { Render } from "~/components";
 	file="mconn/maintenance/remove-connectors"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN (formerly Magic WAN)",
+		dashName: "Cloudflare WAN (formerly Magic WAN)"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
index 46c95fb5d790192..9bdf18008a25f54 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/breakout-traffic.mdx
@@ -9,18 +9,15 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "breakout",
-		featureName: "Breakout traffic",
-		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		whatHappensApp:
-			"will now go directly to the Internet and bypass Cloudflare's filtering",
-		dashName: "Cloudflare WAN",
-	}}
-/>
+	magicWord: "breakout",
+	featureName: "Breakout traffic",
+	trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
+	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
+	dashName: "Cloudflare WAN",
+	}} />
 
 ## Breakout by source
 
@@ -30,11 +27,11 @@ Source-based breakout is configured via the API and Terraform.
 
 ### Match criteria
 
-| Criterion              | Behavior                                                                                                            |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Source LAN interface   | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
-| Source CIDR / IP range | All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
+| Criterion             | Behavior                                                                                          |
+| --------------------- | ------------------------------------------------------------------------------------------------- |
+| Source LAN interface  | All traffic originating on the selected LAN is broken out. Any VLAN attached to that LAN is included automatically. |
+| Source CIDR / IP range| All traffic with a source IP in the specified range is broken out. Accepts a single IP, a range, or a CIDR block.   |
 
 The same criteria can be used to mark traffic as **prioritized** instead of broken out. Refer to [Prioritized traffic](/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic/) for details.
 
-Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
+Source-based and destination-based (managed app or custom app) rules can co-exist on the same appliance and are evaluated independently. If a flow matches both a source-based breakout rule and a destination-based breakout rule, the appliance breaks it out.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
index dce54b18e5ae528..709867b882cbf6b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/application-based-policies/prioritized-traffic.mdx
@@ -9,13 +9,11 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/app-aware-policies/breakout-prioritized"
+<Render file="mconn/network-options/app-aware-policies/breakout-prioritized"
 	product="networking-services"
 	params={{
-		magicWord: "prioritized",
-		featureName: "Prioritized traffic",
-		whatHappensApp: "is now processed first by Connector",
-		dashName: "Cloudflare WAN",
-	}}
-/>
+	magicWord: "prioritized",
+	featureName: "Prioritized traffic",
+	whatHappensApp: "is now processed first by Connector",
+	dashName: "Cloudflare WAN",
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
index cdde5b9bfd22fea..1625f2d8f072527 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-options.mdx
@@ -20,35 +20,35 @@ DHCP options are configured via the API and Terraform.
 
 Each option is defined by three fields:
 
-| Field           | Description                                         | Example               |
-| --------------- | --------------------------------------------------- | --------------------- |
-| `option_number` | The DHCP option code (1–254).                       | `67`                  |
-| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                |
-| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0` |
+| Field           | Description                                         | Example                |
+| --------------- | --------------------------------------------------- | ---------------------- |
+| `option_number` | The DHCP option code (1–254).                       | `67`                   |
+| `type`          | The value encoding: `text`, `integer`, `hex`, `ip`. | `text`                 |
+| `value`         | The option value, encoded per `type`.               | `boot/x64/pxelinux.0`  |
 
 ### Value type encoding
 
-| Type      | Format                                                     | Example value         |
-| --------- | ---------------------------------------------------------- | --------------------- |
-| `ip`      | A dotted-quad IPv4 address.                                | `10.20.30.40`         |
-| `integer` | A decimal integer.                                         | `0`                   |
-| `text`    | A UTF-8 string.                                            | `boot/x64/pxelinux.0` |
-| `hex`     | A colon-separated sequence of bytes, used for sub-options. | `01:04:aa:bb:cc`      |
+| Type      | Format                                                      | Example value                 |
+| --------- | ----------------------------------------------------------- | ----------------------------- |
+| `ip`      | A dotted-quad IPv4 address.                                 | `10.20.30.40`                 |
+| `integer` | A decimal integer.                                          | `0`                           |
+| `text`    | A UTF-8 string.                                             | `boot/x64/pxelinux.0`         |
+| `hex`     | A colon-separated sequence of bytes, used for sub-options.  | `01:04:aa:bb:cc`              |
 
 ## Common PXE / iPXE options
 
 The most frequently used options for PXE / iPXE boot are:
 
-| Option | Type           | Purpose                                                                     |
-| ------ | -------------- | --------------------------------------------------------------------------- |
-| 60     | `text`         | Vendor class identifier (typically `PXEClient`).                            |
-| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                               |
-| 67     | `text`         | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).          |
-| 43     | `hex`          | Vendor-specific information; sub-option layout is vendor-defined.           |
-| 175    | `hex`          | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more). |
-| 209    | `text`         | iPXE configuration file URI.                                                |
-| 210    | `text`         | iPXE configuration file path prefix.                                        |
-| 211    | `text`         | iPXE configuration file path.                                               |
+| Option | Type    | Purpose                                                                              |
+| ------ | ------- | ------------------------------------------------------------------------------------ |
+| 60     | `text`  | Vendor class identifier (typically `PXEClient`).                                     |
+| 66     | `ip` or `text` | TFTP server name or IP address (boot server).                                |
+| 67     | `text`  | Bootfile name to load (for example `ipxe.pxe` or `undionly.kpxe`).                   |
+| 43     | `hex`   | Vendor-specific information; sub-option layout is vendor-defined.                    |
+| 175    | `hex`   | iPXE-specific encapsulated options (HTTP/HTTPS boot, iSCSI, DNS, and more).          |
+| 209    | `text`  | iPXE configuration file URI.                                                         |
+| 210    | `text`  | iPXE configuration file path prefix.                                                 |
+| 211    | `text`  | iPXE configuration file path.                                                        |
 
 For a complete list of standard DHCP option codes, refer to the [IANA BOOTP/DHCP parameters registry](https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml).
 
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
index 46f826cc1ad4c6b..7a2bc1beac7de02 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-relay.mdx
@@ -8,13 +8,11 @@ title: DHCP relay
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-relay"
+<Render file="mconn/network-options/dhcp/dhcp-relay"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
-		cfVsCoreDashNamingMwanCni:
-			"Cloudflare WAN IPsec/GRE tunnel or a CNI connection",
+		cfVsCoreDashNamingMwanCni: "Cloudflare WAN IPsec/GRE tunnel or a CNI connection"
 	}}
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
index 6577eeb5272f5ce..2d895e9f31c584b 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server.mdx
@@ -8,10 +8,9 @@ title: DHCP server
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-server"
+<Render file="mconn/network-options/dhcp/dhcp-server"
 	product="networking-services"
 	params={{
-		dashName: "Cloudflare WAN",
+		dashName: "Cloudflare WAN"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
index f5fed31c4c5855e..5c0bcbed619c268 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -8,11 +8,9 @@ title: DHCP static address reservation
 
 import { Render } from "~/components";
 
-<Render
-	file="mconn/network-options/dhcp/dhcp-static-address-reservation"
+<Render file="mconn/network-options/dhcp/dhcp-static-address-reservation"
 	product="networking-services"
 	params={{
-		dhcpServerURL:
-			"/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
+		dhcpServerURL: "/cloudflare-wan/configuration/appliance/network-options/dhcp/dhcp-server/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
index a9f4fad888935fe..b651bbe1b01b881 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
index 2cbcd17985e02d7..3eab8ea9a7bb2bf 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/link-aggregation.mdx
@@ -8,15 +8,11 @@ sidebar:
   badge: Beta
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/link-aggregation"
+<Render file="mconn/network-options/link-aggregation"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
-	}}
-/>
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
index 8f1cbe1ed9a4b20..007bef4f404e26e 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/nat-subnet.mdx
@@ -4,17 +4,14 @@ products:
   - cloudflare-wan
 title: Enable NAT for a subnet
 description: Enable static NAT for subnets in Cloudflare One Appliance to re-use address spaces locally.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/nat-subnet"
+<Render file="mconn/network-options/nat-subnet"
 	product="networking-services"
 	params={{
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+	hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+  virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
index 822619f84e0b5cf..32603d94e6a92ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/network-segmentation.mdx
@@ -6,16 +6,13 @@ title: Network segmentation
 description: Define policies to determine if traffic should flow between your LANs without leaving your local premises, or if traffic should be forwarded to Cloudflare for additional security configurations.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/network-segmentation"
+<Render file="mconn/network-options/network-segmentation"
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/",
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
index caa93793bc8278e..a7d739e9540ba6a 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/network-options/routed-subnets.mdx
@@ -4,19 +4,15 @@ products:
   - cloudflare-wan
 title: Routed subnets
 description: Learn how to configure routed subnets on a Cloudflare One Appliance, including setting static routes and next-hop addresses for complex LAN setups.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="mconn/network-options/routed-subnets"
+<Render file="mconn/network-options/routed-subnets"
 	product="networking-services"
 	params={{
-		netSubnetURL:
-			"/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
-		hardConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
-		virtualConnectorURL:
-			"/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
-	}}
-/>
+		netSubnetURL: "/cloudflare-wan/configuration/appliance/network-options/nat-subnet/",
+		hardConnectorURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#create-a-lan",
+		virtualConnectorURL: "/cloudflare-wan/configuration/appliance/configure-virtual-appliance/#create-a-lan",
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
index 17809b37e6377e7..0190821520209fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/appliance/troubleshooting.mdx
@@ -15,11 +15,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		dashName: "Cloudflare WAN (formerly Magic WAN)",
-		activateURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
-		firewallURL:
-			"/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
-		heartbeatURL:
-			"/cloudflare-wan/configuration/appliance/maintenance/heartbeat/",
+		activateURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#activate-appliance",
+		firewallURL: "/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#firewall-settings-required",
+		heartbeatURL: "/cloudflare-wan/configuration/appliance/maintenance/heartbeat/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
index bdbd8aaf1e5dec4..eca36e5f7e8eb4b 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/custom-ike-id-ipsec.mdx
@@ -10,7 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/custom-ike-id-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/custom-ike-id-ipsec" product="networking-services" />
diff --git a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
index b4d9501da0d4693..5e0399f52cb9889 100644
--- a/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/common-settings/sites.mdx
@@ -15,12 +15,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		greIpsecTunnelsURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		connectorURL: "/cloudflare-wan/configuration/appliance/",
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		connectorName: "Cloudflare One Appliance",
-		magicTunnelHcsURL:
-			"/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/",
+		magicTunnelHcsURL: "/cloudflare-wan/configuration/common-settings/configure-tunnel-health-alerts/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
index 0432393f1f1c0ca..9a7d3b257246a34 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips.mdx
@@ -13,11 +13,10 @@ description: Configure the Cloudflare source IP range used when you receive traf
 import { Render } from "~/components";
 
 <Render
-	file="routing/configure-cloudflare-source-ips"
-	product="networking-services"
-	params={{
-		unifiedRoutingLink:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/",
-	}}
+  file="routing/configure-cloudflare-source-ips"
+  product="networking-services"
+  params={{
+    unifiedRoutingLink: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    connectivityOptionsLink: "/cloudflare-wan/zero-trust/connectivity-options/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
index e5b02b3a5366e73..8335fb6e9cf3559 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-routes.mdx
@@ -7,9 +7,10 @@ sidebar:
   order: 2
 head: []
 description: Cloudflare WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through CNI with Dataplane v2, you also have access to BGP peering (beta). Learn how to configure routing.
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -18,23 +19,17 @@ import { Render } from "~/components";
 		magicWord: "Cloudflare WAN",
 		trafficSteeringPage: "/cloudflare-wan/reference/traffic-steering/",
 		productName: "Cloudflare WAN",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		routePrioritization: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/cloudflare-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: " ",
 		productGatewayOrEgress: "Cloudflare WAN with Gateway",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		addTunnelsURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		unifiedRoutingModeURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		arrReferenceURL:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		addTunnelsURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		unifiedRoutingModeURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		arrReferenceURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		virtualNetworkName: "Cloudflare Virtual Network",
-		routingTableName: "Cloudflare Virtual Network routing table",
+		routingTableName: "Cloudflare Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
index 9fb7c93867e3747..41b3800804ce8c9 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints.mdx
@@ -11,36 +11,26 @@ description: Learn how to configure IPsec or GRE tunnels for Cloudflare WAN.
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
 		ipRange: "(this address space is also a link-local address)",
 		productName: "Cloudflare WAN",
-		tunnelsAndEncapsulationPagePath:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/cloudflare-wan/reference/anti-replay-protection/",
 		cniLink: "/cloudflare-wan/network-interconnect/",
-		updateHCFrequencyPage:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/cloudflare-wan/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "bidirectional",
-		tunnelHealthDash:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Cloudflare WAN this option defaults to bidirectional",
-		configureRoutesURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		tunnelHealthDash: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Cloudflare WAN this option defaults to bidirectional",
+		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
 		sitesURL: "/cloudflare-wan/configuration/common-settings/sites/",
-		configureARRURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
-		unifiedRoutingURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/cloudflare-wan/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/",
+		configureARRURL: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/cloudflare-wan/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/cloudflare-wan/troubleshooting/ipsec-troubleshoot/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
index 9e7d62f8d1aeab1..4a554e27b3969b6 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
index 38b42c7e4dd0350..ac5910dadeb36ca 100644
--- a/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/how-to/traceroute.mdx
@@ -16,9 +16,8 @@ import { Render } from "~/components";
 	file="routing/traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/index.mdx b/src/content/docs/cloudflare-wan/configuration/index.mdx
index 5ddfb172a16c533..13702b827029038 100644
--- a/src/content/docs/cloudflare-wan/configuration/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
index 4a444cbdbff83f9..76af852c660c808 100644
--- a/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/multi-cloud-networking.mdx
@@ -17,7 +17,6 @@ import { Render } from "~/components";
 	file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
 	params={{
-		mwanAccount:
-			"Have a Multi-Cloud Networking account. Contact your account team to learn more.",
+		mwanAccount: "Have a Multi-Cloud Networking account. Contact your account team to learn more.",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
index ff1a38a9ff1a28e..bb10e2869c1ee67 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/alibaba-cloud.mdx
@@ -4,19 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Alibaba Cloud VPN Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/alibaba-cloud"
-	product="networking-services"
-	params={{
-		ipSecTunnelsUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/alibaba-cloud"
+  product="networking-services"
+  params={{
+    ipSecTunnelsUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
index 58ce92bd34520fd..f9028eefecd609a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/aws.mdx
@@ -4,17 +4,14 @@ description: Connect Amazon AWS Transit Gateway to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Amazon AWS Transit Gateway
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/aws"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/aws"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
index a76d15bdf214c1a..f041179a7d471bc 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-virtual-wan.mdx
@@ -8,16 +8,11 @@ title: Microsoft Azure Virtual WAN
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-virtual-wan"
-	product="networking-services"
-	params={{
-		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-		ipsecTunnelUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		cloudflareDocumentationUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-virtual-wan"
+  product="networking-services"
+  params={{
+  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
+  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  cloudflareDocumentationUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
index f424bafbae91997..79e3ab4a2c3e78e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/azure-vpn-gateway.mdx
@@ -8,16 +8,11 @@ title: Microsoft Azure VPN Gateway
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/azure-vpn-gateway"
-	product="networking-services"
-	params={{
-		ipsecTunnelUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		tunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		staticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/azure-vpn-gateway"
+  product="networking-services"
+  params={{
+  ipsecTunnelUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+  tunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+  staticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+  tunnelHealthChecksUrl: "/cloudflare-wan/reference/tunnel-health-checks/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
index 2cc5b0788919598..be31f60acc7149a 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/azure/index.mdx
@@ -9,8 +9,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Microsoft Azure integration guides currently available:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
index 8831ea12bbf6ea5..cba0f106bf12657 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-ios-xe.mdx
@@ -4,11 +4,11 @@ description: Connect Cisco IOS XE to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Cisco IOS XE
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-ios-xe"
-	product="networking-services"
+<Render file="cloudflare-wan/third-party/cisco-ios-xe"
+  product="networking-services"
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
index 4191b38bc630e29..896e02c855659fd 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/cisco-meraki-static.mdx
@@ -8,22 +8,15 @@ title: Cisco Meraki MX (static routing)
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/cisco-meraki-static"
+<Render file="cloudflare-wan/third-party/cisco-meraki-static"
 	product="networking-services"
 	params={{
-		antiReplayProtectionUrl:
-			"/cloudflare-wan/reference/anti-replay-protection/",
+		antiReplayProtectionUrl: "/cloudflare-wan/reference/anti-replay-protection/",
 		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		unifiedRoutingUrl:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		automaticReturnRoutingUrl:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		unifiedRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+		automaticReturnRoutingUrl: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
 		trafficSteeringUrl: "/cloudflare-wan/reference/traffic-steering/",
-		supportedConfigParametersUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedConfigParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		paloAltoGuideUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+		configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+	}} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
index 4ab6dfd8b7b76e9..e28d8ba4847ab6f 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fitelnet.mdx
@@ -4,19 +4,15 @@ description: Connect Furukawa Electric FITELnet to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Furukawa Electric FITELnet
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fitelnet"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		typeId_ipv4_addrUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fitelnet"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    typeId_ipv4_addrUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
index cf11763d0a341ab..5a12895743cb66e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx
@@ -8,19 +8,12 @@ title: Fortinet
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/fortinet"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		equalCostMultipathRoutingEcmpUrl:
-			"/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/fortinet"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    equalCostMultipathRoutingEcmpUrl: "/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
index 2ae56b6dbe49b81..6f89300b8494e05 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/google.mdx
@@ -4,17 +4,14 @@ description: Connect Google Cloud VPN to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Google Cloud VPN
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/google"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/google"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
index c73eca34c84c602..f6e508d000a5d0d 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Third-party integration tutorials
 description: Learn how to integrate Cloudflare WAN with third-party products.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
index 85e683e79c81b16..3818804b0252018 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/juniper.mdx
@@ -10,14 +10,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/juniper"
-	product="networking-services"
-	params={{
-		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/juniper"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
index 1f2ddeaeeefca8f..78849f6cad28825 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/oracle.mdx
@@ -4,17 +4,14 @@ description: Connect Oracle Cloud to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: Oracle Cloud
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/oracle"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createAStaticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/oracle"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createAStaticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
index a95d9f3fabecc02..110c15959491f36 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/palo-alto.mdx
@@ -13,14 +13,10 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/palo-alto"
-	product="networking-services"
-	params={{
-		mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/palo-alto"
+  product="networking-services"
+  params={{
+    mssClampingUrl: "/cloudflare-wan/reference/mtu-mss/#mss-clamping",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
index 862ad0f4b4e8284..d86dc81c4715843 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/pfsense.mdx
@@ -5,19 +5,15 @@ products:
   - cloudflare-wan
 title: pfSense
 reviewed: 2024-06-20
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/pfsense"
-	product="networking-services"
-	params={{
-		configureTwoIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		staticRouteUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/pfsense"
+  product="networking-services"
+  params={{
+    configureTwoIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    staticRouteUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
index 536b6c9ff0ab552..26a76c80f25db4e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sonicwall.mdx
@@ -4,21 +4,16 @@ pcx_content_type: integration-guide
 description: Connect SonicWall to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sonicwall"
-	product="networking-services"
-	params={{
-		ipsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		creatingYourIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		createYourStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sonicwall"
+  product="networking-services"
+  params={{
+    ipsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    creatingYourIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    createYourStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
index 1d3ab31ab967c03..b6d0e9a1f52a074 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/sophos-firewall.mdx
@@ -4,21 +4,16 @@ pcx_content_type: integration-guide
 description: Connect Sophos Firewall to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/sophos-firewall"
-	product="networking-services"
-	params={{
-		genericRoutingEncapsulationGreOrIpsecTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		ikeIdUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		checkTunnelHealthInTheDashboardUrl:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/sophos-firewall"
+  product="networking-services"
+  params={{
+    genericRoutingEncapsulationGreOrIpsecTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    ikeIdUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-ike-id-formats",
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    checkTunnelHealthInTheDashboardUrl: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
index bac9233cb7a5f21..fc4d45f5469a352 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/strongswan.mdx
@@ -4,15 +4,13 @@ description: Connect strongSwan to Cloudflare WAN.
 products:
   - cloudflare-wan
 title: strongSwan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/strongswan"
-	product="networking-services"
-	params={{
-		bidirectionalHealthChecksUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/strongswan"
+  product="networking-services"
+  params={{
+    bidirectionalHealthChecksUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
index 5f49238ade5259c..868c273f24c50f6 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/ubiquiti.mdx
@@ -9,9 +9,9 @@ title: Ubiquiti
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-wan/third-party/ubiquiti"
-	product="networking-services"
-	params={{
-		magicWord: "Cloudflare WAN",
-	}}
+  file="cloudflare-wan/third-party/ubiquiti"
+  product="networking-services"
+  params={{
+    magicWord: "Cloudflare WAN",
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
index 03266a7985edc32..fc2441a6857269e 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/velocloud.mdx
@@ -4,15 +4,13 @@ pcx_content_type: integration-guide
 description: Connect Velocloud to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/velocloud"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/velocloud"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
index cbcaa056c559724..b6b97c01cebaf9d 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/viptela.mdx
@@ -4,18 +4,15 @@ pcx_content_type: integration-guide
 description: Connect Cisco SD-WAN to Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/viptela"
-	product="networking-services"
-	params={{
-		configureTunnelEndpointsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
-		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/viptela"
+  product="networking-services"
+  params={{
+    configureTunnelEndpointsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#create-a-static-route",
+    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
index da8b1fef607c6af..0ccbceefbb7c339 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/vyos.mdx
@@ -8,4 +8,6 @@ title: VyOS
 
 import { Render } from "~/components";
 
-<Render file="cloudflare-wan/third-party/vyos" product="networking-services" />
+<Render file="cloudflare-wan/third-party/vyos"
+  product="networking-services"
+/>
diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
index 3e0e9e8caca4dee..c117c2a4435efd5 100644
--- a/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
+++ b/src/content/docs/cloudflare-wan/configuration/third-party/yamaha.mdx
@@ -8,13 +8,9 @@ title: Yamaha RTX Router
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/third-party/yamaha"
-	product="networking-services"
-	params={{
-		addTunnelsUrl:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		configureStaticRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-	}}
-/>
+<Render file="cloudflare-wan/third-party/yamaha"
+  product="networking-services"
+  params={{
+    addTunnelsUrl: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+    configureStaticRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/get-started.mdx b/src/content/docs/cloudflare-wan/get-started.mdx
index 50110e083ff7170..b2f98f780c0e192 100644
--- a/src/content/docs/cloudflare-wan/get-started.mdx
+++ b/src/content/docs/cloudflare-wan/get-started.mdx
@@ -17,14 +17,11 @@ import { Render } from "~/components";
 		productNameManual: "Cloudflare WAN",
 		productNameConnector: "Cloudflare One Appliance",
 		configureConnectorUrl: "/cloudflare-wan/configuration/appliance/",
-		configureMwanManually:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		configureMwanManually: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
 		greReferenceURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		ipsecReferenceUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
-		ipsecReferenceConfigParams:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		ipsecReferenceUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+		ipsecReferenceConfigParams: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		mtuReferenceURL: "/cloudflare-wan/reference/mtu-mss/",
-		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
+		wanTransformationUrl: "/cloudflare-wan/wan-transformation/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/glossary.mdx b/src/content/docs/cloudflare-wan/glossary.mdx
index 5b50582a0620f31..9707d04db10e16a 100644
--- a/src/content/docs/cloudflare-wan/glossary.mdx
+++ b/src/content/docs/cloudflare-wan/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - cloudflare-wan
 sidebar:
   order: 14
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare WAN (formerly Magic WAN) documentation.
 
diff --git a/src/content/docs/cloudflare-wan/index.mdx b/src/content/docs/cloudflare-wan/index.mdx
index 9a0cea6bca082c4..5eac1897c216694 100644
--- a/src/content/docs/cloudflare-wan/index.mdx
+++ b/src/content/docs/cloudflare-wan/index.mdx
@@ -27,9 +27,8 @@ import { Render } from "~/components";
 		connectorUrl: "/cloudflare-wan/configuration/appliance/",
 		thirdPartyUrl: "/cloudflare-wan/configuration/third-party/",
 		zeroTrustUrl: "/cloudflare-wan/zero-trust/",
-		bgpRoutesUrl:
-			"/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
+		bgpRoutesUrl: "/cloudflare-wan/configuration/how-to/configure-routes/#configure-bgp-routes",
 		wanTransformationUrl: "/cloudflare-wan/wan-transformation/",
-		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/",
+		virtualNetworksUrl: "/cloudflare-wan/reference/virtual-networks/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
index 9d694953eaa9562..de5decbd83487cb 100644
--- a/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
+++ b/src/content/docs/cloudflare-wan/legal/3rdparty.mdx
@@ -5,9 +5,10 @@ pcx_content_type: reference
 description: Third-party licenses used in Cloudflare WAN.
 products:
   - cloudflare-wan
+
 ---
 
 import text from "./3rdparty.txt?raw";
 import { Markdown } from "~/components";
 
-<Markdown text={text} inline={false} />
+<Markdown text={text} inline={false} />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/legal/index.mdx b/src/content/docs/cloudflare-wan/legal/index.mdx
index 907e5abf6f28688..e2e9dc5f914a078 100644
--- a/src/content/docs/cloudflare-wan/legal/index.mdx
+++ b/src/content/docs/cloudflare-wan/legal/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 12
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/network-interconnect.mdx b/src/content/docs/cloudflare-wan/network-interconnect.mdx
index 86be9e7f16b6297..2f3024d241fa36f 100644
--- a/src/content/docs/cloudflare-wan/network-interconnect.mdx
+++ b/src/content/docs/cloudflare-wan/network-interconnect.mdx
@@ -13,20 +13,14 @@ head:
 
 import { Render } from "~/components";
 
-<Render
-	file="magic-cni"
-	product="networking-services"
-	params={{ magicWord: "Cloudflare WAN" }}
-/>
+<Render file="magic-cni" product="networking-services" params={{ magicWord: "Cloudflare WAN" }} />
 
 <Render
 	file="traceroute"
 	product="networking-services"
 	params={{
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
-		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/on-ramps.mdx b/src/content/docs/cloudflare-wan/on-ramps.mdx
index 32fdec0f6eabfab..86da6b248ebe042 100644
--- a/src/content/docs/cloudflare-wan/on-ramps.mdx
+++ b/src/content/docs/cloudflare-wan/on-ramps.mdx
@@ -22,6 +22,6 @@ import { Render } from "~/components";
 		cniURL: "/cloudflare-wan/network-interconnect/",
 		cfTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
 		warpURL: "/cloudflare-wan/zero-trust/cloudflare-one-client/",
-		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/",
+		thirdPartyIntegrationURL: "/cloudflare-wan/configuration/third-party/"
 	}}
-/>
+	/>
diff --git a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
index 9ed3368c2c98be2..a081ee8130d1870 100644
--- a/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
+++ b/src/content/docs/cloudflare-wan/reference/anti-replay-protection.mdx
@@ -4,8 +4,7 @@ products:
   - cloudflare-wan
 title: Anti-replay protection
 head: []
-description:
-  If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
+description: If you use Cloudflare WAN and anycast IPsec tunnels, you will need to
   disable anti-replay protection. Review the information here to learn more.
 sidebar:
   order: 1
diff --git a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
index cc92b6c823ab972..fbec0cd8573df1d 100644
--- a/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
+++ b/src/content/docs/cloudflare-wan/reference/bandwidth-measurement.mdx
@@ -14,6 +14,6 @@ import { Render } from "~/components";
 	file="cloudflare-wan/reference/bandwidth-measurement"
 	product="networking-services"
 	params={{
-		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/",
+		cloudflareTunnelURL: "/cloudflare-wan/zero-trust/cloudflare-tunnel/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
index dbcdf9a17252a75..a504caad9990939 100644
--- a/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/docs/cloudflare-wan/reference/device-compatibility.mdx
@@ -10,35 +10,29 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render
-	file="cloudflare-wan/reference/device-compatibility"
-	product="networking-services"
-	params={{
-		supportedConfigurationParametersUrl:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		arubaEdgeconnectUrl:
-			"/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
-		ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
-		ciscoMerakiStaticUrl:
-			"/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
-		ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
-		fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
-		fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
-		juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
-		paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
-		pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
-		sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
-		sophosFirewallUrl:
-			"/cloudflare-wan/configuration/third-party/sophos-firewall/",
-		strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
-		ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
-		velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
-		vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
-		yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
-		alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
-		awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
-		azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
-		googleUrl: "/cloudflare-wan/configuration/third-party/google/",
-		oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/",
-	}}
-/>
+<Render file="cloudflare-wan/reference/device-compatibility"
+  product="networking-services"
+  params={{
+    supportedConfigurationParametersUrl: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    arubaEdgeconnectUrl: "/cloudflare-wan/configuration/third-party/aruba-edgeconnect/",
+    ciscoIosXeUrl: "/cloudflare-wan/configuration/third-party/cisco-ios-xe/",
+    ciscoMerakiStaticUrl: "/cloudflare-wan/configuration/third-party/cisco-meraki-static/",
+    ciscoSdWanUrl: "/cloudflare-wan/configuration/third-party/viptela/",
+    fortinetUrl: "/cloudflare-wan/configuration/third-party/fortinet/",
+    fitelnetUrl: "/cloudflare-wan/configuration/third-party/fitelnet/",
+    juniperUrl: "/cloudflare-wan/configuration/third-party/juniper/",
+    paloAltoUrl: "/cloudflare-wan/configuration/third-party/palo-alto/",
+    pfsenseUrl: "/cloudflare-wan/configuration/third-party/pfsense/",
+    sonicwallUrl: "/cloudflare-wan/configuration/third-party/sonicwall/",
+    sophosFirewallUrl: "/cloudflare-wan/configuration/third-party/sophos-firewall/",
+    strongswanUrl: "/cloudflare-wan/configuration/third-party/strongswan/",
+    ubiquitiUrl: "/cloudflare-wan/configuration/third-party/ubiquiti/",
+    velocloudUrl: "/cloudflare-wan/configuration/third-party/velocloud/",
+    vyosUrl: "/cloudflare-wan/configuration/third-party/vyos/",
+    yamahaUrl: "/cloudflare-wan/configuration/third-party/yamaha/",
+    alibabaCloudUrl: "/cloudflare-wan/configuration/third-party/alibaba-cloud/",
+    awsUrl: "/cloudflare-wan/configuration/third-party/aws/",
+    azureUrl: "/cloudflare-wan/configuration/third-party/azure/",
+    googleUrl: "/cloudflare-wan/configuration/third-party/google/",
+    oracleUrl: "/cloudflare-wan/configuration/third-party/oracle/"
+  }} />
diff --git a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
index 6cf088b347f6d36..68d4b4a66826115 100644
--- a/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/cloudflare-wan/reference/gre-ipsec-tunnels.mdx
@@ -20,14 +20,12 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		mssURL: "/cloudflare-wan/get-started/#set-maximum-segment-size",
 		productURL: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/cloudflare-wan/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/cloudflare-wan/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index 0251f5066fd362c..6a4cb0f5b700132 100644
--- a/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,12 +8,9 @@ sidebar:
   order: 8
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down",
-	}}
+	params={{ tunnelStatePath: "/cloudflare-wan/reference/tunnel-health-checks/#down" }}
 />
diff --git a/src/content/docs/cloudflare-wan/reference/index.mdx b/src/content/docs/cloudflare-wan/reference/index.mdx
index 1de78f741d45c97..ae239f4ddfc37af 100644
--- a/src/content/docs/cloudflare-wan/reference/index.mdx
+++ b/src/content/docs/cloudflare-wan/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
index 433a4d677c2c8b1..c0e144ba5def202 100644
--- a/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
+++ b/src/content/docs/cloudflare-wan/reference/mtu-mss.mdx
@@ -16,6 +16,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN",
-	}}
-/>
+		productName: "Cloudflare WAN"
+		}}
+/>
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
index 9d1d78aca887206..5f34c73baea554a 100644
--- a/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
+++ b/src/content/docs/cloudflare-wan/reference/traffic-steering.mdx
@@ -23,8 +23,7 @@ import { Render } from "~/components";
 		routingTableName: "Cloudflare Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
index af8dd8496a2775f..98d45cc88d50519 100644
--- a/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/tunnel-health-checks.mdx
@@ -17,15 +17,12 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Cloudflare WAN",
-		addTunnels:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
+		addTunnels: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels",
+		changeHealthCheckRate: "/cloudflare-wan/configuration/common-settings/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Cloudflare WAN",
 		staticRoutes: "/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelEndpoints:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
index 7a88bf96e8c4a54..cb97c92d8e4803d 100644
--- a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
+++ b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx
@@ -15,14 +15,11 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		tunnelConfigURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
+		tunnelConfigURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/",
 		addRoutesURL: "/cloudflare-one/networks/routes/add-routes/",
-		configureRoutesURL:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
+		configureRoutesURL: "/cloudflare-wan/configuration/how-to/configure-routes/",
 		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/",
-		privateNetworksURL:
-			"/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
+		privateNetworksURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/",
 		routesURL: "/cloudflare-one/networks/routes/",
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/security.mdx b/src/content/docs/cloudflare-wan/security.mdx
index 8a6e3df9eaad074..20d951ee8b334c0 100644
--- a/src/content/docs/cloudflare-wan/security.mdx
+++ b/src/content/docs/cloudflare-wan/security.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable security filters
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="cloudflare-wan/security-filters"
+<Render file="cloudflare-wan/security-filters"
 	product="networking-services"
 	params={{
-		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/",
+		gatewayURL: "/cloudflare-wan/zero-trust/cloudflare-gateway/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
index 220b98e58c0e0a5..a190ec5d61db5ed 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/connectivity.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 		productName: "Cloudflare WAN",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
 		routingBgpLink: "/cloudflare-wan/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+		checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
index 5d7bf235ac3cb37..905787c40bc06f3 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 13
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
index dc1236e65423f20..274a58ce5258d51 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/ipsec-troubleshoot.mdx
@@ -8,16 +8,14 @@ sidebar:
   order: 1
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
 		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/",
+		mtuMssLink: "/cloudflare-wan/reference/mtu-mss/"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
index a43339acccd25e2..ed25cd90faf8949 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/routing-and-bgp.mdx
@@ -11,16 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "Cloudflare WAN",
-		productName: "Cloudflare WAN",
-		trafficSteeringLink:
-			"/cloudflare-wan/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink:
-			"/cloudflare-wan/configuration/how-to/configure-routes/",
-		tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "Cloudflare WAN",
+    productName: "Cloudflare WAN",
+    trafficSteeringLink: "/cloudflare-wan/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/cloudflare-wan/configuration/how-to/configure-routes/",
+    tunnelHealthLink: "/cloudflare-wan/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
index 485d6bb04a1e428..807fee1aad43dc6 100644
--- a/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/cloudflare-wan/troubleshooting/tunnel-health.mdx
@@ -11,21 +11,17 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Cloudflare WAN",
-		healthCheckDefault: "_Bidirectional_",
-		tunnelsConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
-		antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
-		tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
-		configureTunnelsLink:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Cloudflare WAN",
+    healthCheckDefault: "_Bidirectional_",
+    tunnelsConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/",
+    antiReplayLink: "/cloudflare-wan/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/cloudflare-wan/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/cloudflare-wan/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/cloudflare-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
index 095f4976ce553d9..ad22094662587ee 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/cloudflare-tunnel.mdx
@@ -13,14 +13,10 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		gatewayURL: "/cloudflare-one/traffic-policies/",
-		greIpsecURL:
-			"/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
-		warpURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		greIpsecURL: "/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/",
+		warpURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		tracerouteURL: "/cloudflare-wan/configuration/how-to/traceroute/",
-		trafficSteeringURL:
-			"/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
-		arrURL:
-			"/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta",
+		trafficSteeringURL: "/cloudflare-wan/reference/traffic-steering/#route-evaluation-with-zero-trust-connections",
+		arrURL: "/cloudflare-wan/reference/traffic-steering/#automatic-return-routing-beta"
 	}}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
index 566bc65d5095477..7a6e010f13f8f63 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/connectivity-options.mdx
@@ -11,14 +11,13 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="cloudflare-one-connectivity-options"
-	product="networking-services"
-	params={{
-		unifiedRoutingURL:
-			"/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
-		greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
-		connectorURL: "/cloudflare-wan/configuration/appliance/",
-		cniURL: "/cloudflare-wan/network-interconnect/",
-		onRampsURL: "/cloudflare-wan/on-ramps/",
-	}}
+  file="cloudflare-one-connectivity-options"
+  product="networking-services"
+  params={{
+    unifiedRoutingURL: "/cloudflare-wan/reference/traffic-steering/#unified-routing-mode-beta",
+    greIpsecURL: "/cloudflare-wan/reference/gre-ipsec-tunnels/",
+    connectorURL: "/cloudflare-wan/configuration/appliance/",
+    cniURL: "/cloudflare-wan/network-interconnect/",
+    onRampsURL: "/cloudflare-wan/on-ramps/"
+  }}
 />
diff --git a/src/content/docs/cloudflare-wan/zero-trust/index.mdx b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
index 52b072c14394b76..039a590ad02f2f0 100644
--- a/src/content/docs/cloudflare-wan/zero-trust/index.mdx
+++ b/src/content/docs/cloudflare-wan/zero-trust/index.mdx
@@ -8,9 +8,9 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare One integration tutorials
-description:
-  Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
+description: Learn how to integrate Cloudflare WAN (formerly Magic WAN) with other Cloudflare
   Cloudflare One products, such as Cloudflare Gateway and the Cloudflare One Client.
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/constellation/platform/index.mdx b/src/content/docs/constellation/platform/index.mdx
index 1b6cdafb1ff1640..8d627d53915bd45 100644
--- a/src/content/docs/constellation/platform/index.mdx
+++ b/src/content/docs/constellation/platform/index.mdx
@@ -7,6 +7,6 @@ products:
   - constellation
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/containers/examples/cron.mdx b/src/content/docs/containers/examples/cron.mdx
index fa89b747782586a..beb5c71d036990a 100644
--- a/src/content/docs/containers/examples/cron.mdx
+++ b/src/content/docs/containers/examples/cron.mdx
@@ -57,37 +57,32 @@ Use a cron expression in your Wrangler config to specify the schedule:
 Then in your Worker, call your Container from the "scheduled" handler:
 
 ```ts
-import { Container, getContainer } from "@cloudflare/containers";
+import { Container, getContainer } from '@cloudflare/containers';
 
 export class CronContainer extends Container {
-	sleepAfter = "10s";
+  sleepAfter = '10s';
 
-	override onStart() {
-		console.log("Starting container");
-	}
+  override onStart() {
+    console.log('Starting container');
+  }
 
-	override onStop() {
-		console.log("Container stopped");
-	}
+  override onStop() {
+    console.log('Container stopped');
+  }
 }
 
 export default {
-	async fetch(): Promise<Response> {
-		return new Response(
-			"This Worker runs a cron job to execute a container on a schedule.",
-		);
-	},
+  async fetch(): Promise<Response> {
+    return new Response("This Worker runs a cron job to execute a container on a schedule.");
+  },
 
-	async scheduled(
-		_controller: any,
-		env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> },
-	) {
-		let container = getContainer(env.CRON_CONTAINER);
-		await container.start({
-			envVars: {
+  async scheduled(_controller: any, env: { CRON_CONTAINER: DurableObjectNamespace<CronContainer> }) {
+    let container = getContainer(env.CRON_CONTAINER);
+    await container.start({
+      envVars: {
 				MESSAGE: "Start Time: " + new Date().toISOString(),
-			},
-		});
-	},
+      }
+    })
+  },
 };
 ```
diff --git a/src/content/docs/containers/examples/durable-object-interface.mdx b/src/content/docs/containers/examples/durable-object-interface.mdx
index d54c84506542fc7..f957451fa12358b 100644
--- a/src/content/docs/containers/examples/durable-object-interface.mdx
+++ b/src/content/docs/containers/examples/durable-object-interface.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Various examples calling Containers directly from Durable Objects
 pcx_content_type: example
 title: Using Durable Objects Directly
diff --git a/src/content/docs/containers/examples/index.mdx b/src/content/docs/containers/examples/index.mdx
index 5cf608f97ac0ecc..eb6ca3b44e7d6f7 100644
--- a/src/content/docs/containers/examples/index.mdx
+++ b/src/content/docs/containers/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: false
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/containers/platform-details/placement.mdx b/src/content/docs/containers/platform-details/placement.mdx
index 67d5a76095272fe..bcb40145e1c38a1 100644
--- a/src/content/docs/containers/platform-details/placement.mdx
+++ b/src/content/docs/containers/platform-details/placement.mdx
@@ -34,10 +34,10 @@ Limited capacity regions (ME, OC, AFR) cannot be used exclusively. Include at le
 
 Use the `jurisdiction` constraint to restrict containers to compliance boundaries:
 
-| Jurisdiction | Regions    | Use case          |
-| ------------ | ---------- | ----------------- |
-| `eu`         | EEUR, WEUR | EU data residency |
-| `fedramp`    | ENAM, WNAM | FedRAMP regions   |
+| Jurisdiction | Regions    | Use case           |
+| ------------ | ---------- | ------------------ |
+| `eu`         | EEUR, WEUR | EU data residency  |
+| `fedramp`    | ENAM, WNAM | FedRAMP regions    |
 
 When you specify both `jurisdiction` and `regions`, the regions must be valid for that jurisdiction. For example, specifying `jurisdiction: "eu"` with `regions: ["ENAM"]` is invalid.
 
diff --git a/src/content/docs/containers/pricing.mdx b/src/content/docs/containers/pricing.mdx
index 504db4e7c197e95..a26fc07ae355276 100644
--- a/src/content/docs/containers/pricing.mdx
+++ b/src/content/docs/containers/pricing.mdx
@@ -22,7 +22,7 @@ Containers are billed for every 10ms that they are actively running at the follo
 
 You only pay for what you use — charges start when a request is sent to the container or when it is manually started. Charges stop after the container instance goes to sleep, which can happen automatically after a timeout. This makes it easy to scale to zero, and allows you to get high utilization even with bursty traffic.
 
-Memory and disk usage are based on the _provisioned resources_ for the instance type you select, while CPU usage is based on _active usage_ only.
+Memory and disk usage are based on the *provisioned resources* for the instance type you select, while CPU usage is based on *active usage* only.
 
 #### Instance Types
 
diff --git a/src/content/docs/containers/ssh.mdx b/src/content/docs/containers/ssh.mdx
index bc91bd0cdc3968d..fab40ae97a43594 100644
--- a/src/content/docs/containers/ssh.mdx
+++ b/src/content/docs/containers/ssh.mdx
@@ -58,4 +58,4 @@ wrangler containers ssh <INSTANCE_ID>
 
 ## Process visibility
 
-Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
+Without the [`containers_pid_namespace`](/workers/configuration/compatibility-flags/#use-an-isolated-pid-namespace-for-containers) compatibility flag, all processes inside the VM are visible when you connect to your Container through SSH. This flag is turned on by default for Workers with a [compatibility date](/workers/configuration/compatibility-dates/) of `2026-04-01` or later.
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/local-development.mdx b/src/content/docs/d1/best-practices/local-development.mdx
index a225fec2f2d3b74..f6f28cdf1259255 100644
--- a/src/content/docs/d1/best-practices/local-development.mdx
+++ b/src/content/docs/d1/best-practices/local-development.mdx
@@ -137,6 +137,8 @@ Users of wrangler `2.x` must use the `--persist` flag: previous versions of wran
 
 You can use Miniflare's [support for D1](https://miniflare.dev/storage/d1) to create D1 databases you can use for testing:
 
+
+
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/d1/best-practices/query-d1.mdx b/src/content/docs/d1/best-practices/query-d1.mdx
index 6f4eddbd73c830b..74e5a405162b2c2 100644
--- a/src/content/docs/d1/best-practices/query-d1.mdx
+++ b/src/content/docs/d1/best-practices/query-d1.mdx
@@ -52,16 +52,15 @@ Given the following JSON object (`type:blob`) in a column named `sensor_reading`
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
-
 ```sql
 -- Extract the temperature value
 SELECT json_extract(sensor_reading, '$.measurement.temp_f')-- returns "77.4" as TEXT
@@ -81,24 +80,22 @@ This requires you to:
 
 ```js title="index.js"
 export default {
-	async fetch(request, env) {
-		const { pathname } = new URL(request.url);
-		const companyName1 = `Bs Beverages`;
-		const companyName2 = `Around the Horn`;
-		const stmt = env.DB.prepare(
-			`SELECT * FROM Customers WHERE CompanyName = ?`,
-		);
-
-		if (pathname === `/RUN`) {
-			const returnValue = await stmt.bind(companyName1).run();
-			return Response.json(returnValue);
-		}
-
-		return new Response(
-			`Welcome to the D1 API Playground!
+    async fetch(request, env) {
+        const {pathname} = new URL(request.url);
+        const companyName1 = `Bs Beverages`;
+        const companyName2 = `Around the Horn`;
+        const stmt = env.DB.prepare(`SELECT * FROM Customers WHERE CompanyName = ?`);
+
+        if (pathname === `/RUN`) {
+            const returnValue = await stmt.bind(companyName1).run();
+            return Response.json(returnValue);
+        }
+
+        return new Response(
+            `Welcome to the D1 API Playground!
 						\nChange the URL to test the various methods inside your index.js file.`,
-		);
-	},
+        );
+    },
 };
 ```
 
@@ -117,7 +114,6 @@ You can use Wrangler commands to query a D1 database. Note that Wrangler command
 ```sh
 npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ```
-
 ```sh output
 🌀 Mapping SQL input into an array of statements
 🌀 Executing on local database production-db-backend (<DATABASE_ID>) from .wrangler/state/v3/d1:
@@ -132,4 +128,4 @@ npx wrangler d1 execute prod-d1-tutorial --command="SELECT * FROM Customers"
 ├────────────┼─────────────────────┼───────────────────┤
 │ 13         │ Bs Beverages        │ Random Name       │
 └────────────┴─────────────────────┴───────────────────┘
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/remote-development.mdx b/src/content/docs/d1/best-practices/remote-development.mdx
index 4efe9586181686f..40be666bf1fb1f5 100644
--- a/src/content/docs/d1/best-practices/remote-development.mdx
+++ b/src/content/docs/d1/best-practices/remote-development.mdx
@@ -17,16 +17,17 @@ D1 supports remote development using the [dashboard playground](/workers/playgro
 
 :::note
 
+
 This guide assumes you have previously created a Worker, and a D1 database.
 
 Users new to D1 and/or Cloudflare Workers should read the [D1 tutorial](/d1/get-started/) to install `wrangler` and deploy their first database.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select an existing Worker.
 3. Go to the **Bindings** tab.
 4. Select **Add binding**.
@@ -43,14 +44,14 @@ Use the following Worker script to verify that the Worker has access to the boun
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		const res = await env.DB.prepare("SELECT 1;").run();
-		return new Response(JSON.stringify(res, null, 2));
-	},
+  async fetch(request, env, ctx) {
+    const res = await env.DB.prepare("SELECT 1;").run();
+    return new Response(JSON.stringify(res, null, 2));
+  },
 };
 ```
 
 ## Related resources
 
-- Learn [how to debug D1](/d1/observability/debug-d1/).
-- Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
+* Learn [how to debug D1](/d1/observability/debug-d1/).
+* Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
diff --git a/src/content/docs/d1/best-practices/retry-queries.mdx b/src/content/docs/d1/best-practices/retry-queries.mdx
index 0dafe17addbbd3c..02bc218ed30d67e 100644
--- a/src/content/docs/d1/best-practices/retry-queries.mdx
+++ b/src/content/docs/d1/best-practices/retry-queries.mdx
@@ -27,20 +27,20 @@ You can use libraries abstracting that already like [`@cloudflare/actors`](https
 import { tryWhile } from "@cloudflare/actors";
 
 function queryD1Example(d1: D1Database, sql: string) {
-	return await tryWhile(async () => {
-		return await d1.prepare(sql).run();
-	}, shouldRetry);
+  return await tryWhile(async () => {
+    return await d1.prepare(sql).run();
+  }, shouldRetry);
 }
 
 function shouldRetry(err: unknown, nextAttempt: number) {
-	const errMsg = String(err);
-	const isRetryableError =
-		errMsg.includes("Network connection lost") ||
-		errMsg.includes("storage caused object to be reset") ||
-		errMsg.includes("reset because its code was updated");
-	if (nextAttempt <= 5 && isRetryableError) {
-		return true;
-	}
-	return false;
+  const errMsg = String(err);
+  const isRetryableError =
+    errMsg.includes("Network connection lost") ||
+    errMsg.includes("storage caused object to be reset") ||
+    errMsg.includes("reset because its code was updated");
+  if (nextAttempt <= 5 && isRetryableError) {
+    return true;
+  }
+  return false;
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
index 5ba46a35c327eba..cf575cec298ffee 100644
--- a/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
+++ b/src/content/docs/d1/best-practices/use-d1-from-pages.mdx
@@ -7,5 +7,5 @@ sidebar:
   order: 11
 products:
   - d1
-  - pages
+  - pages  
 ---
diff --git a/src/content/docs/d1/best-practices/use-indexes.mdx b/src/content/docs/d1/best-practices/use-indexes.mdx
index b363212f5718cc1..dc25d04079a3170 100644
--- a/src/content/docs/d1/best-practices/use-indexes.mdx
+++ b/src/content/docs/d1/best-practices/use-indexes.mdx
@@ -16,9 +16,9 @@ Indexes enable D1 to improve query performance over the indexed columns for comm
 
 Indexes are useful:
 
-- When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
-- For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
-- In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
+* When you want to improve the read performance over columns that are regularly used in predicates - for example, a `WHERE email_address = ?` or `WHERE user_id = 'a793b483-df87-43a8-a057-e5286d3537c5'` - email addresses, usernames, user IDs and/or dates are good choices for columns to index in typical web applications or services.
+* For enforcing uniqueness constraints on a column or columns - for example, an email address or user ID via the `CREATE UNIQUE INDEX`.
+* In cases where you query over multiple columns together - `(customer_id, transaction_date)`.
 
 Indexes are automatically updated when the table and column(s) they reference are inserted, updated or deleted. You do not need to manually update an index after you write to the table it references.
 
@@ -114,7 +114,7 @@ Using an index can reduce the number of rows read by a query. Use the `meta` obj
 
 ## Multi-column indexes
 
-For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either _all_ of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
+For a multi-column index (an index that specifies multiple columns), queries will only use the index if they specify either *all* of the columns, or a subset of the columns provided all columns to the "left" are also within the query.
 
 Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions(customer_id, transaction_date)`, the following table shows when the index is used (or not):
 
@@ -126,16 +126,16 @@ Given an index of `CREATE INDEX idx_customer_id_transaction_date ON transactions
 
 Notes:
 
-- If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
-- With the same index, a query that uses only `transaction_date` and `shipping_status` would _not_ use the index, as you have not used `customer_id` (the leftmost column) in the query.
+* If you created an index over three columns instead — `customer_id`, `transaction_date` and `shipping_status` — a query that uses both `customer_id` and `transaction_date` would use the index, as you are including all columns "to the left".
+* With the same index, a query that uses only `transaction_date` and `shipping_status` would *not* use the index, as you have not used `customer_id` (the leftmost column) in the query.
 
 ## Partial indexes
 
 Partial indexes are indexes over a subset of rows in a table. Partial indexes are defined by the use of a `WHERE` clause when creating the index. A partial index can be useful to omit certain rows, such as those where values are `NULL` or where rows with a specific value are present across queries.
 
-- A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
-- This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
-- Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
+* A concrete example of a partial index would be on a table with a `order_status INTEGER` column, where `6` might represent `"order complete"` in your application code.
+* This would allow queries against orders that are yet to be fulfilled, shipped or are in-progress, which are likely to be some of the most common users (users checking their order status).
+* Partial indexes also keep the index from growing unbounded over time. The index does not need to keep a row for every completed order, and completed orders are likely to be queried far fewer times than in-progress orders.
 
 A partial index that filters out completed orders from the index would resemble the following:
 
@@ -153,7 +153,7 @@ Use `DROP INDEX` to remove an index. Dropped indexes cannot be restored.
 
 Take note of the following considerations when creating indexes:
 
-- Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
-- You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
-- Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
-- Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
+* Indexes are not always a free performance boost. You should create indexes only on columns that reflect your most-queried columns. Indexes themselves need to be maintained. When you write to an indexed column, the database needs to write to the table and the index. The performance benefit of an index and reduction in rows read will, in nearly all cases, offset this additional write.
+* You cannot create indexes that reference other tables or use non-deterministic functions, since the index would not be stable.
+* Indexes cannot be updated. To add or remove a column from an index, [remove](#remove-indexes) the index and then [create a new index](#create-an-index) with the new columns.
+* Indexes contribute to the overall storage required by your database: an index is effectively a table itself.
diff --git a/src/content/docs/d1/configuration/environments.mdx b/src/content/docs/d1/configuration/environments.mdx
index 9211ae269c77fa0..d006e54c8c8878d 100644
--- a/src/content/docs/d1/configuration/environments.mdx
+++ b/src/content/docs/d1/configuration/environments.mdx
@@ -78,20 +78,22 @@ Therefore, the above binding is equivalent to:
 
 ```json
 {
-	"production": {
-		"d1_databases": [
-			{
-				"binding": "DB",
-				"database_name": "DATABASE_NAME",
-				"database_id": "DATABASE_ID"
-			}
-		]
-	}
+  "production": {
+    "d1_databases": [
+      {
+        "binding": "DB",
+        "database_name": "DATABASE_NAME",
+        "database_id": "DATABASE_ID"
+      }
+    ]
+  }
 }
 ```
 
 ### Example
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -125,25 +127,25 @@ The above is equivalent to the following structure in JSON:
 
 ```json
 {
-	"env": {
-		"production": {
-			"d1_databases": [
-				{
-					"binding": "BINDING_NAME_2",
-					"database_id": "UUID_2",
-					"database_name": "DATABASE_NAME_2"
-				}
-			]
-		},
-		"staging": {
-			"d1_databases": [
-				{
-					"binding": "BINDING_NAME_1",
-					"database_id": "UUID_1",
-					"database_name": "DATABASE_NAME_1"
-				}
-			]
-		}
-	}
+  "env": {
+    "production": {
+      "d1_databases": [
+        {
+          "binding": "BINDING_NAME_2",
+          "database_id": "UUID_2",
+          "database_name": "DATABASE_NAME_2"
+        }
+      ]
+    },
+    "staging": {
+      "d1_databases": [
+        {
+          "binding": "BINDING_NAME_1",
+          "database_id": "UUID_1",
+          "database_name": "DATABASE_NAME_1"
+        }
+      ]
+    }
+  }
 }
 ```
diff --git a/src/content/docs/d1/get-started.mdx b/src/content/docs/d1/get-started.mdx
index 5d22a0fe3363f7c..c5ee956264ad848 100644
--- a/src/content/docs/d1/get-started.mdx
+++ b/src/content/docs/d1/get-started.mdx
@@ -9,17 +9,7 @@ products:
   - d1
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	FileTree,
-	Tabs,
-	TabItem,
-	TypeScriptExample,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, PackageManagers, Steps, FileTree, Tabs, TabItem, TypeScriptExample, WranglerConfig, DashButton } from "~/components";
 
 This guide instructs you through:
 
diff --git a/src/content/docs/d1/observability/billing.mdx b/src/content/docs/d1/observability/billing.mdx
index 1a4a8d3fffc9712..31ef2103ba9196a 100644
--- a/src/content/docs/d1/observability/billing.mdx
+++ b/src/content/docs/d1/observability/billing.mdx
@@ -21,7 +21,6 @@ Total account billable usage analytics for D1 are available in the Cloudflare da
 1. In the Cloudflare dashboard, go to the **Billing** page.
 
    <DashButton url="/?to=/:account/billing" />
-
 2. Go to **Billable Usage**.
 
 From here you can view charts of your account's D1 usage on a daily or month-to-date timeframe.
@@ -33,6 +32,5 @@ Note that billable usage history is stored for a maximum of 30 days.
 Usage-based billing notifications are available within the [Cloudflare dashboard](https://dash.cloudflare.com) for users looking to monitor their total account usage.
 
 Notifications on the following metrics are available:
-
 - Rows Read
-- Rows Written
+- Rows Written
\ No newline at end of file
diff --git a/src/content/docs/d1/platform/limits.mdx b/src/content/docs/d1/platform/limits.mdx
index 21cb95db52dfab3..4c61da8679fd68e 100644
--- a/src/content/docs/d1/platform/limits.mdx
+++ b/src/content/docs/d1/platform/limits.mdx
@@ -10,24 +10,24 @@ products:
 
 import { Render } from "~/components";
 
-| Feature                                                                                         | Limit                                             |
-| ----------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| Databases per account                                                                           | 50,000 (Workers Paid) [^1] / 10 (Free)            |
-| Maximum database size                                                                           | 10 GB (Workers Paid) / 500 MB (Free)              |
-| Maximum storage per account                                                                     | 1 TB (Workers Paid) [^2] / 5 GB (Free)            |
-| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                     | 30 days (Workers Paid) / 7 days (Free)            |
-| Maximum Time Travel restore operations                                                          | 10 restores per 10 minutes (per database)         |
+| Feature                                                                                                             | Limit                                             |
+| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| Databases per account                                                                                               | 50,000 (Workers Paid) [^1] / 10 (Free)            |
+| Maximum database size                                                                                               | 10 GB (Workers Paid) / 500 MB (Free)              |
+| Maximum storage per account                                                                                         | 1 TB (Workers Paid) [^2] / 5 GB (Free)             |
+| [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                                         | 30 days (Workers Paid) / 7 days (Free)            |
+| Maximum Time Travel restore operations                                                                              | 10 restores per 10 minutes (per database)          |
 | Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#subrequests)) | 1000 (Workers Paid) / 50 (Free)                   |
-| Maximum number of columns per table                                                             | 100                                               |
-| Maximum number of rows per table                                                                | Unlimited (excluding per-database storage limits) |
-| Maximum string, `BLOB` or table row size                                                        | 2,000,000 bytes (2 MB)                            |
-| Maximum SQL statement length                                                                    | 100,000 bytes (100 KB)                            |
-| Maximum bound parameters per query                                                              | 100                                               |
-| Maximum arguments per SQL function                                                              | 32                                                |
-| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                        | 50 bytes                                          |
-| Maximum bindings per Workers script                                                             | Approximately 5,000 [^3]                          |
-| Maximum SQL query duration                                                                      | 30 seconds [^4]                                   |
-| Maximum file import (`d1 execute`) size                                                         | 5 GB [^5]                                         |
+| Maximum number of columns per table                                                                                 | 100                                               |
+| Maximum number of rows per table                                                                                    | Unlimited (excluding per-database storage limits) |
+| Maximum string, `BLOB` or table row size                                                                            | 2,000,000 bytes (2 MB)                            |
+| Maximum SQL statement length                                                                                        | 100,000 bytes (100 KB)                            |
+| Maximum bound parameters per query                                                                                  | 100                                               |
+| Maximum arguments per SQL function                                                                                  | 32                                                |
+| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                                            | 50 bytes                                          |
+| Maximum bindings per Workers script                                                                                 | Approximately 5,000 [^3]                          |
+| Maximum SQL query duration                                                                                          | 30 seconds [^4]                                   |
+| Maximum file import (`d1 execute`) size                                                                             | 5 GB [^5]                                         |
 
 :::note[Batch limits]
 Limits for individual queries (listed above) apply to each individual statement contained within a batch statement. For example, the maximum SQL statement length of 100 KB applies to each statement inside a `db.batch()`.
diff --git a/src/content/docs/d1/reference/community-projects.mdx b/src/content/docs/d1/reference/community-projects.mdx
index 2974e7452d65edb..a095bb554ffe1f5 100644
--- a/src/content/docs/d1/reference/community-projects.mdx
+++ b/src/content/docs/d1/reference/community-projects.mdx
@@ -12,8 +12,10 @@ Members of the Cloudflare developer community and broader developer ecosystem ha
 
 :::note
 
+
 Community projects are not maintained by the Cloudflare D1 team. They are managed and updated by the project authors.
 
+
 :::
 
 ## Projects
@@ -35,57 +37,57 @@ knex-cloudflare-d1 is the Cloudflare D1 dialect for Knex.js. Note that this is n
 
 [Prisma ORM](https://www.prisma.io/orm) is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to its intuitive data model, automated migrations, type-safety and auto-completion.
 
-- [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
-- [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
+* [Tutorial](/d1/tutorials/d1-and-prisma-orm/)
+* [Docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare#d1)
 
 ### D1 adapter for Kysely ORM
 
 Kysely is a type-safe and autocompletion-friendly typescript SQL query builder. With this adapter you can interact with D1 with the familiar Kysely interface.
 
-- [Kysely GitHub](https://github.com/koskimas/kysely)
-- [D1 adapter](https://github.com/aidenwallis/kysely-d1)
+* [Kysely GitHub](https://github.com/koskimas/kysely)
+* [D1 adapter](https://github.com/aidenwallis/kysely-d1)
 
 ### feathers-kysely
 
 The `feathers-kysely` database adapter follows the FeathersJS Query Syntax standard and works with any framework. It is built on the D1 adapter for Kysely and supports passing queries directly from client applications. Since the FeathersJS query syntax is a subset of MongoDB's syntax, this is a great tool for MongoDB users to use Cloudflare D1 without previous SQL experience.
 
-- [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
-- [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
+* [feathers-kysely on npm](https://www.npmjs.com/package/feathers-kysely)
+* [feathers-kysely on GitHub](https://github.com/marshallswain/feathers-kysely)
 
 ### Drizzle ORM
 
 Drizzle is a headless TypeScript ORM with a head which runs on Node, Bun and Deno. Drizzle ORM lives on the Edge and it is a JavaScript ORM too. It comes with a drizzle-kit CLI companion for automatic SQL migrations generation. Drizzle automatically generates your D1 schema based on types you define in TypeScript, and exposes an API that allows you to query your database directly.
 
-- [Docs](https://orm.drizzle.team/docs)
-- [GitHub](https://github.com/drizzle-team/drizzle-orm)
-- [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
+* [Docs](https://orm.drizzle.team/docs)
+* [GitHub](https://github.com/drizzle-team/drizzle-orm)
+* [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
 
 ### workers-qb
 
 `workers-qb` is a zero-dependency query builder that provides a simple standardized interface while keeping the benefits and speed of using raw queries over a traditional ORM. While not intended to provide ORM-like functionality, `workers-qb` makes it easier to interact with your database from code for direct SQL access.
 
-- [GitHub](https://github.com/G4brym/workers-qb)
-- [Documentation](https://workers-qb.massadas.com/)
+* [GitHub](https://github.com/G4brym/workers-qb)
+* [Documentation](https://workers-qb.massadas.com/)
 
 ### d1-console
 
 Instead of running the `wrangler d1 execute` command in your terminal every time you want to interact with your database, you can interact with D1 from within the `d1-console`. Created by a Discord Community Champion, this gives the benefit of executing multi-line queries, obtaining command history, and viewing a cleanly formatted table output.
 
-- [GitHub](https://github.com/isaac-mcfadyen/d1-console)
+* [GitHub](https://github.com/isaac-mcfadyen/d1-console)
 
 ### L1
 
 `L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
 
-- [GitHub](https://github.com/renoki-co/l1)
-- [Packagist](https://packagist.org/packages/renoki-co/l1)
+* [GitHub](https://github.com/renoki-co/l1)
+* [Packagist](https://packagist.org/packages/renoki-co/l1)
 
 ### Staff Directory - a D1-based demo
 
 Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/honox), and [Cloudflare Pages](/pages/). It uses D1 to store employee data, and is an example of a full-stack application built on top of D1.
 
-- [GitHub](https://github.com/lauragift21/staff-directory)
-- [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
+* [GitHub](https://github.com/lauragift21/staff-directory)
+* [D1 functionality](https://github.com/lauragift21/staff-directory/blob/main/app/db.ts)
 
 ### NuxtHub
 
@@ -93,9 +95,9 @@ Staff Directory is a demo project using D1, [HonoX](https://github.com/honojs/ho
 
 `NuxtHub` also provides a way to use your remote D1 database in development using the `npx nuxt dev --remote` command.
 
-- [GitHub](https://github.com/nuxt-hub/core)
-- [Documentation](https://hub.nuxt.com)
-- [Example](https://github.com/Atinux/nuxt-todos-edge)
+* [GitHub](https://github.com/nuxt-hub/core)
+* [Documentation](https://hub.nuxt.com)
+* [Example](https://github.com/Atinux/nuxt-todos-edge)
 
 ## Feedback
 
diff --git a/src/content/docs/d1/reference/data-security.mdx b/src/content/docs/d1/reference/data-security.mdx
index ab79357a7114750..810de22ec7f45ea 100644
--- a/src/content/docs/d1/reference/data-security.mdx
+++ b/src/content/docs/d1/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of D1, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/d1/reference/faq.mdx b/src/content/docs/d1/reference/faq.mdx
index e86017db8b829fa..112c665dd4004ad 100644
--- a/src/content/docs/d1/reference/faq.mdx
+++ b/src/content/docs/d1/reference/faq.mdx
@@ -12,8 +12,8 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="faq-pricing" product="d1" />
+<Render file="faq-pricing" product="d1"/>
 
 ## Limits
 
-<Render file="faq-limits" product="d1" />
+<Render file="faq-limits" product="d1"/>
\ No newline at end of file
diff --git a/src/content/docs/d1/reference/generated-columns.mdx b/src/content/docs/d1/reference/generated-columns.mdx
index ccadcdb1b12d227..5d116b3321076a7 100644
--- a/src/content/docs/d1/reference/generated-columns.mdx
+++ b/src/content/docs/d1/reference/generated-columns.mdx
@@ -18,8 +18,8 @@ Generated columns can also have [indexes defined](/d1/best-practices/use-indexes
 
 There are two types of generated columns:
 
-- `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
-- `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
+* `VIRTUAL` (default): the column is generated when read. This has the benefit of not consuming storage, but can increase compute time (and thus reduce query performance), especially for larger queries.
+* `STORED`: the column is generated when the row is written. The column takes up storage space just as a regular column would, but the column does not need to be generated on every read, which can improve read query performance.
 
 When omitted from a generated column expression, generated columns default to the `VIRTUAL` type. The `STORED` type is recommended when the generated column is compute intensive. For example, when parsing large JSON structures.
 
@@ -40,13 +40,13 @@ As a concrete example, to automatically extract the `location` value from the fo
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
 
@@ -100,6 +100,6 @@ ADD COLUMN expires_at AS (date(timestamp, '+30 days'));
 
 ## Additional considerations
 
-- Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
-- Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
-- Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
+* Tables must have at least one non-generated column. You cannot define a table with only generated column(s).
+* Expressions can only reference other columns in the same table and row, and must only use [deterministic functions](https://www.sqlite.org/deterministic.html). Functions like `random()`, sub-queries or aggregation functions cannot be used to define a generated column.
+* Columns added to an existing table via `ALTER TABLE ... ADD COLUMN` must be `VIRTUAL`. You cannot add a `STORED` column to an existing table.
diff --git a/src/content/docs/d1/reference/glossary.mdx b/src/content/docs/d1/reference/glossary.mdx
index 87e1a98504fae41..5fe0afff9a376e2 100644
--- a/src/content/docs/d1/reference/glossary.mdx
+++ b/src/content/docs/d1/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - d1
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's D1 documentation.
 
diff --git a/src/content/docs/d1/reference/migrations.mdx b/src/content/docs/d1/reference/migrations.mdx
index 20dc9869915cbc2..50d3292c20ea584 100644
--- a/src/content/docs/d1/reference/migrations.mdx
+++ b/src/content/docs/d1/reference/migrations.mdx
@@ -16,9 +16,9 @@ Database migrations are a way of versioning your database. Each migration is sto
 
 Currently, the migrations system aims to be simple yet effective. With the current implementation, you can:
 
-- [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
-- [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
-- [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
+* [Create](/workers/wrangler/commands/d1/#d1-migrations-create) an empty migration file.
+* [List](/workers/wrangler/commands/d1/#d1-migrations-list) unapplied migrations.
+* [Apply](/workers/wrangler/commands/d1/#d1-migrations-apply) remaining migrations.
 
 Every migration file in the `migrations` folder has a specified version number in the filename. Files are listed in sequential order. Every migration file is an SQL file where you can specify queries to be run.
 
diff --git a/src/content/docs/d1/sql-api/foreign-keys.mdx b/src/content/docs/d1/sql-api/foreign-keys.mdx
index fdc9e715186ae46..1c38b8d8d995ec3 100644
--- a/src/content/docs/d1/sql-api/foreign-keys.mdx
+++ b/src/content/docs/d1/sql-api/foreign-keys.mdx
@@ -47,13 +47,13 @@ A foreign key relationship can be defined when creating a table via `CREATE TABL
 
 To illustrate this with an example based on an e-commerce website with two tables:
 
-- A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
-- An `orders` table that maps an order back to a `user_id` in the user table.
+* A `users` table that defines common properties about a user account, including a unique `user_id` identifier.
+* An `orders` table that maps an order back to a `user_id` in the user table.
 
 This mapping is defined as `FOREIGN KEY`, which ensures that:
 
-- You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
-- `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
+* You cannot delete a row from the `users` table that would violate the foreign key constraint. This means that you cannot end up with orders that do not have a valid user to map back to.
+* `orders` are always defined against a valid `user_id`, mitigating the risk of creating orders that refer to invalid (or non-existent) users.
 
 ```sql
 CREATE TABLE users (
@@ -77,22 +77,22 @@ You can define multiple foreign key relationships per-table, and foreign key def
 
 ## Foreign key actions
 
-You can define _actions_ as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining _actions_ makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
+You can define *actions* as part of your foreign key definitions to either limit or propagate changes to a parent row (`REFERENCES table(column)`). Defining *actions* makes using foreign key constraints in your application easier to reason about, and help either clean up related data or prevent data from being islanded.
 
 There are five actions you can set when defining the `ON UPDATE` and/or `ON DELETE` clauses as part of a foreign key relationship. You can also define different actions for `ON UPDATE` and `ON DELETE` depending on your requirements.
 
-- `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
-- `RESTRICT` - A parent key cannot be updated or deleted when _any_ child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
-- `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
-- `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
-- `NO ACTION` - Take no action.
+* `CASCADE` - Updating or deleting a parent key deletes all child keys (rows) associated to it.
+* `RESTRICT` - A parent key cannot be updated or deleted when *any* child key refers to it. Unlike the default foreign key enforcement, relationships with `RESTRICT` applied return errors immediately, and not at the end of the transaction.
+* `SET DEFAULT` - Set the child column(s) referred to by the foreign key definition to the `DEFAULT` value defined in the schema. If no `DEFAULT` is set on the child columns, you cannot use this action.
+* `SET NULL` - Set the child column(s) referred to by the foreign key definition to SQL `NULL`.
+* `NO ACTION` - Take no action.
 
 :::caution[CASCADE usage]
 
 Although `CASCADE` can be the desired behavior in some cases, deleting child rows across tables can have undesirable effects and/or result in unintended side effects for your users.
 :::
 
-In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that _other_ users can no longer look up or refer to scores that were still valid.
+In the following example, deleting a user from the `users` table will delete all related rows in the `scores` table as you have defined `ON DELETE CASCADE`. Delete all related rows in the `scores` table if you do not want to retain the scores for any users you have deleted entirely. This might mean that *other* users can no longer look up or refer to scores that were still valid.
 
 ```sql
 CREATE TABLE users (
@@ -111,6 +111,6 @@ CREATE TABLE scores (
 
 ## Next Steps
 
-- Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
-- Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
-- Understand how [database migrations work](/d1/reference/migrations/) with D1.
+* Read the SQLite [`FOREIGN KEY`](https://www.sqlite.org/foreignkeys.html) documentation.
+* Learn how to [use the D1 Workers Binding API](/d1/worker-api/) from within a Worker.
+* Understand how [database migrations work](/d1/reference/migrations/) with D1.
diff --git a/src/content/docs/d1/sql-api/query-json.mdx b/src/content/docs/d1/sql-api/query-json.mdx
index 82c65b749bd3e7f..9b44068ab62c958 100644
--- a/src/content/docs/d1/sql-api/query-json.mdx
+++ b/src/content/docs/d1/sql-api/query-json.mdx
@@ -12,10 +12,10 @@ products:
 
 D1 has built-in support for querying and parsing JSON data stored within a database. This enables you to:
 
-- [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
-- Insert and/or replace values within an object or array.
-- [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
-- Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
+* [Query paths](#extract-values) within a stored JSON object - for example, extracting the value of named key or array index directly, which is especially useful with larger JSON objects.
+* Insert and/or replace values within an object or array.
+* [Expand the contents of a JSON object](#expand-arrays-for-in-queries) or array into multiple rows - for example, for use as part of a `WHERE ... IN` predicate.
+* Create [generated columns](/d1/reference/generated-columns/) that are automatically populated with values from JSON objects you insert.
 
 One of the biggest benefits to parsing JSON within D1 directly is that it can directly reduce the number of round-trips (queries) to your database. It reduces the cases where you have to read a JSON object into your application (1), parse it, and then write it back (2).
 
@@ -25,18 +25,18 @@ This allows you to more precisely query over data and reduce the result set your
 
 JSON data is stored as a `TEXT` column in D1. JSON types follow the same [type conversion rules](/d1/worker-api/#type-conversion) as D1 in general, including:
 
-- A JSON null is treated as a D1 `NULL`.
-- A JSON number is treated as an `INTEGER` or `REAL`.
-- Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
-- Object and array values as `TEXT`.
+* A JSON null is treated as a D1 `NULL`.
+* A JSON number is treated as an `INTEGER` or `REAL`.
+* Booleans are treated as `INTEGER` values: `true` as `1` and `false` as `0`.
+* Object and array values as `TEXT`.
 
 ## Supported functions
 
 The following table outlines the JSON functions built into D1 and example usage.
 
-- The `json` argument placeholder can be a JSON object, array, string, number or a null value.
-- The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
-- The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
+* The `json` argument placeholder can be a JSON object, array, string, number or a null value.
+* The `value` argument accepts string literals (only) and treats input as a string, even if it is well-formed JSON. The exception to this rule is when nesting `json_*` functions: the outer (wrapping) function will interpret the inner (wrapped) functions return value as JSON.
+* The `path` argument accepts path-style traversal syntax - for example, `$` to refer to the top-level object/array, `$.key1.key2` to refer to a nested object, and `$.key[2]` to index into an array.
 
 | Function                                                    | Description                                                                                                                                                    | Example                                                                                   |
 | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
@@ -53,7 +53,7 @@ The following table outlines the JSON functions built into D1 and example usage.
 | `json_replace(json, path, value)`                           | Insert a value at the given path. Overwrites an existing value, but does not create a new key if it doesn't exist.                                             |                                                                                           |
 | `json_set(json, path, value)`                               | Insert a value at the given path. Overwrites an existing value.                                                                                                |                                                                                           |
 | `json_type(json)` - `json_type(json, path)`                 | Return the type of the provided value or value at the specified path. Returns one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`. | `json_type('{"temperatures":[73.6, 77.8, 80.2]}', '$.temperatures')` returns `array`      |
-| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                   |
+| `json_valid(json)`                                          | Returns 0 (false) for invalid JSON, and 1 (true) for valid JSON.                                                                                               | `json_valid({invalid:json})`returns`0\`                                                  |
 | `json_quote(value)`                                         | Converts the provided SQL value into its JSON representation.                                                                                                  | `json_quote('[1, 2, 3]')` returns `[1,2,3]`                                               |
 | `json_group_array(value)`                                   | Returns the provided value(s) as a JSON array.                                                                                                                 |                                                                                           |
 | `json_each(value)` - `json_each(value, path)`               | Returns each element within the object as an individual row. It will only traverse the top-level object.                                                       |                                                                                           |
@@ -102,9 +102,9 @@ Refer to [Generated columns](/d1/reference/generated-columns/) to learn more abo
 
 There are three ways to extract a value from a JSON object in D1:
 
-- The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
-- The `->` operator, which returns a JSON representation of the value.
-- The `->>` operator, which returns an SQL representation of the value.
+* The `json_extract()` function - for example, `json_extract(text_column_containing_json, '$.path.to.value)`.
+* The `->` operator, which returns a JSON representation of the value.
+* The `->>` operator, which returns an SQL representation of the value.
 
 The `->` and `->>` operators functions both operate similarly to the same operators in PostgreSQL and MySQL/MariaDB.
 
@@ -112,13 +112,13 @@ Given the following JSON object in a column named `sensor_reading`, you can extr
 
 ```json
 {
-	"measurement": {
-		"temp_f": "77.4",
-		"aqi": [21, 42, 58],
-		"o3": [18, 500],
-		"wind_mph": "13",
-		"location": "US-NY"
-	}
+    "measurement": {
+        "temp_f": "77.4",
+        "aqi": [21, 42, 58],
+        "o3": [18, 500],
+        "wind_mph": "13",
+        "location": "US-NY"
+    }
 }
 ```
 
@@ -148,12 +148,8 @@ For example, given the following JSON object stored in a column called `login_hi
 
 ```json
 {
-	"user_id": "abc12345",
-	"previous_logins": [
-		"2023-03-31T21:07:14-05:00",
-		"2023-03-28T08:21:02-05:00",
-		"2023-03-28T05:52:11-05:00"
-	]
+    "user_id": "abc12345",
+    "previous_logins": ["2023-03-31T21:07:14-05:00", "2023-03-28T08:21:02-05:00", "2023-03-28T05:52:11-05:00"]
 }
 ```
 
@@ -168,13 +164,7 @@ You can also use `json_array_length` as a predicate in a more complex query - fo
 You can insert a value into an existing JSON object or array using `json_insert()`. For example, if you have a `TEXT` column called `login_history` in a `users` table containing the following object:
 
 ```json
-{
-	"history": [
-		"2023-05-13T15:13:02+00:00",
-		"2023-05-14T07:11:22+00:00",
-		"2023-05-15T15:03:51+00:00"
-	]
-}
+{"history": ["2023-05-13T15:13:02+00:00", "2023-05-14T07:11:22+00:00", "2023-05-15T15:03:51+00:00"]}
 ```
 
 To add a new timestamp to the `history` array within our `login_history` column, write a query resembling the following:
@@ -207,11 +197,11 @@ This would extract only the `value` column from the table returned by `json_each
 
 `json_each` effectively returns a table with multiple columns, with the most relevant being:
 
-- `key` - the key (or index).
-- `value` - the literal value of each element parsed by `json_each`.
-- `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
-- `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
-- `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
+* `key` - the key (or index).
+* `value` - the literal value of each element parsed by `json_each`.
+* `type` - the type of the value: one of `null`, `true`, `false`, `integer`, `real`, `text`, `array`, or `object`.
+* `fullkey` - the full path to the element: e.g. `$[1]` for the second element in an array, or `$.path.to.key` for a nested object.
+* `path` - the top-level path - `$` as the path for an element with a `fullkey` of `$[0]`.
 
 In this example, `SELECT * FROM json_each('[183183, 13913, 94944]')` would return a table resembling the below:
 
@@ -225,12 +215,12 @@ key|value|type|id|fullkey|path
 You can use `json_each` with [D1 Workers Binding API](/d1/worker-api/) in a Worker by creating a statement and using `JSON.stringify` to pass an array as a [bound parameter](/d1/worker-api/d1-database/#guidance):
 
 ```ts
-const stmt = context.env.DB.prepare(
-	"UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))",
-);
-const resp = await stmt
-	.bind("2023-05-16T11:24:08+00:00", JSON.stringify([183183, 13913, 94944]))
-	.run();
+const stmt = context.env.DB
+    .prepare("UPDATE users SET last_audited = ? WHERE id IN (SELECT value FROM json_each(?1))")
+const resp = await stmt.bind(
+    "2023-05-16T11:24:08+00:00",
+    JSON.stringify([183183, 13913, 94944])
+    ).run()
 ```
 
 This would only update rows in your `users` table where the `id` matches one of the three provided.
diff --git a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
index 2a203c8cb9975a9..986d25d5413005e 100644
--- a/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
+++ b/src/content/docs/d1/tutorials/build-an-api-to-access-d1.mdx
@@ -12,13 +12,7 @@ description: >-
   This tutorial shows how to create an API that allows you to securely run queries against a D1 database. The API can be used to customize access controls and/or limit what tables can be queried.
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	Details,
-	WranglerConfig,
-} from "~/components";
+import { Render, PackageManagers, Steps, Details, WranglerConfig } from "~/components";
 
 In this tutorial, you will learn how to create an API that allows you to securely run queries against a D1 database.
 
diff --git a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
index 64bb7a1593def46..3ae7982d8bf2cca 100644
--- a/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
+++ b/src/content/docs/d1/tutorials/d1-and-prisma-orm.mdx
@@ -230,7 +230,7 @@ npx prisma migrate diff --from-empty --to-schema-datamodel ./prisma/schema.prism
 
 </TabItem>
 </Tabs>
-
+ 
 This stores a SQL statement to create a new `User` table in your migration file from before, here is what it looks like:
 
 <GitHubCode
diff --git a/src/content/docs/data-localization/compatibility.mdx b/src/content/docs/data-localization/compatibility.mdx
index 724dbfd2c9587c6..472524c6f61c822 100644
--- a/src/content/docs/data-localization/compatibility.mdx
+++ b/src/content/docs/data-localization/compatibility.mdx
@@ -29,19 +29,19 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                                    | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------ | --------------- | ----------------- | -------------------------- |
 | Caching/CDN                                | ✅              | ✅                | ✅                         |
-| Cache Reserve                              | ⚫️              | 🚧                | ✅ [^29]                   |
-| DNS                                        | ⚫️              | 🚧 [^33]          | ✅                         |
-| HTTP/3 (with QUIC)                         | ⚫️              | ✘                 | ⚫️                         |
+| Cache Reserve                              | ⚫️             | 🚧                | ✅ [^29]                   |
+| DNS                                        | ⚫️             | 🚧 [^33]          | ✅                         |
+| HTTP/3 (with QUIC)                         | ⚫️             | ✘                 | ⚫️                        |
 | Image Resizing                             | ✅              | ✅ [^6]           | 🚧 [^1]                    |
 | Load Balancing                             | ✅              | ✅                | 🚧 [^1]                    |
-| Network Error Logging (NEL)                | ⚫️              | ⚫️                | ✘                          |
+| Network Error Logging (NEL)                | ⚫️             | ⚫️               | ✘                          |
 | Onion Routing                              | ✘               | ✘                 | ✘                          |
 | O2O                                        | ✘               | ✘                 | ✘                          |
 | Stream Delivery                            | ✅              | ✅                | ✅                         |
 | Tiered Caching                             | ✅              | 🚧 [^2]           | 🚧 [^30]                   |
 | Trace                                      | ✘               | ✘                 | ✘                          |
-| Waiting Room                               | ⚫️              | ✅                | ✅                         |
-| Web Analytics / Real User Monitoring (RUM) | ⚫️              | ⚫️                | ✘ [^43]                    |
+| Waiting Room                               | ⚫️             | ✅                | ✅                         |
+| Web Analytics / Real User Monitoring (RUM) | ⚫️             | ⚫️               | ✘ [^43]                    |
 | Zaraz                                      | ✅              | ✅                | ✅                         |
 
 ---
@@ -50,18 +50,18 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------------------- | --------------- | ----------------- | -------------------------- |
-| Advanced Certificate Manager                | ⚫️              | ⚫️                | ⚫️                         |
+| Advanced Certificate Manager                | ⚫️             | ⚫️               | ⚫️                        |
 | Advanced DDoS Protection                    | ✅              | ✅                | 🚧 [^3]                    |
 | API Shield                                  | ✅              | ✅                | 🚧 [^4]                    |
 | Bot Management                              | ✅              | ✅                | ✅                         |
 | Client-side security (formerly Page Shield) | ✅              | ✅                | ✅                         |
-| DNS Firewall                                | ⚫️              | ⚫️                | ✅                         |
+| DNS Firewall                                | ⚫️             | ⚫️               | ✅                         |
 | Rate Limiting                               | ✅              | ✅                | ✅ [^37]                   |
 | SSL                                         | ✅              | ✅                | ✅                         |
 | Cloudflare for SaaS                         | ✘               | ✅                | ✅                         |
-| Turnstile                                   | ⚫️              | ✘                 | ✅ [^38]                   |
+| Turnstile                                   | ⚫️             | ✘                 | ✅ [^38]                   |
 | WAF/L7 Firewall                             | ✅              | ✅                | ✅                         |
-| DMARC Management                            | ⚫️              | ⚫️                | ✅                         |
+| DMARC Management                            | ⚫️             | ⚫️               | ✅                         |
 
 ---
 
@@ -69,24 +69,24 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product                        | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------------------------ | --------------- | ----------------- | -------------------------- |
-| Cloudflare Images              | ⚫️              | ✅ [^36]          | 🚧 [^35]                   |
+| Cloudflare Images              | ⚫️             | ✅ [^36]          | 🚧 [^35]                   |
 | AI Gateway                     | ✘               | ✘                 | 🚧 [^39]                   |
 | AI Search                      | ✘ [^46]         | ✘ [^47]           | 🚧 [^48]                   |
 | AI Security for Apps           | ✘               | ✘                 | ✘                          |
 | Cloudflare Pages               | ✅ [^11]        | ✅ [^11]          | 🚧 [^1]                    |
-| Cloudflare D1                  | ⚫️              | ⚫️                | 🚧 [^40]                   |
-| Durable Objects                | ⚫️              | ✅ [^7]           | 🚧 [^1]                    |
-| Email Routing                  | ⚫️              | ⚫️                | ✅                         |
+| Cloudflare D1                  | ⚫️             | ⚫️               | 🚧 [^40]                   |
+| Durable Objects                | ⚫️             | ✅ [^7]           | 🚧 [^1]                    |
+| Email Routing                  | ⚫️             | ⚫️               | ✅                         |
 | Remote MCP Server              | ✅ [^44]        | ✅ [^45]          | 🚧 [^1]                    |
 | R2                             | ✅ [^27]        | ✅ [^8]           | ✅ [^28]                   |
-| Smart Placement                | ⚫️              | ✘                 | ✘                          |
-| Stream                         | ⚫️              | ✘                 | 🚧 [^1]                    |
-| Vectorize                      | ⚫️              | ✘                 | ✘                          |
+| Smart Placement                | ⚫️             | ✘                 | ✘                          |
+| Stream                         | ⚫️             | ✘                 | 🚧 [^1]                    |
+| Vectorize                      | ⚫️             | ✘                 | ✘                          |
 | Workers (deployed on a Zone)   | ✅              | ✅                | 🚧 [^41]                   |
-| Workers AI                     | ⚫️              | ✘                 | ✅                         |
-| Workers KV                     | ⚫️              | ✘                 | ✅ [^34]                   |
+| Workers AI                     | ⚫️             | ✘                 | ✅                         |
+| Workers KV                     | ⚫️             | ✘                 | ✅ [^34]                   |
 | Workers.dev                    | ✘               | ✘                 | ✘                          |
-| Workers Analytics Engine (WAE) | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Workers Analytics Engine (WAE) | ⚫️             | ⚫️               | 🚧 [^1]                    |
 
 ---
 
@@ -95,11 +95,11 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product                     | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------------- | --------------- | ----------------- | -------------------------- |
 | Argo Smart Routing          | ✅              | ✘ [^9]            | ✘ [^10]                    |
-| Static IP/BYOIP             | ⚫️              | ✅ [^26]          | ⚫️                         |
-| Cloudflare Network Firewall | ⚫️              | ⚫️                | ✅                         |
-| Network Flow                | ⚫️              | ⚫️                | 🚧 [^1]                    |
-| Magic Transit               | ⚫️              | ⚫️                | ✅ [^3]                    |
-| Cloudflare WAN              | ⚫️              | ⚫️                | ✅                         |
+| Static IP/BYOIP             | ⚫️             | ✅ [^26]          | ⚫️                        |
+| Cloudflare Network Firewall | ⚫️             | ⚫️               | ✅                         |
+| Network Flow                | ⚫️             | ⚫️               | 🚧 [^1]                    |
+| Magic Transit               | ⚫️             | ⚫️               | ✅ [^3]                    |
+| Cloudflare WAN              | ⚫️             | ⚫️               | ✅                         |
 | Spectrum                    | ✅              | ✅ [^42]          | ✅                         |
 
 ---
@@ -108,9 +108,9 @@ The tables below show whether each Cloudflare product is compatible with each DL
 
 | Product      | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ------------ | --------------- | ----------------- | -------------------------- |
-| Logpull      | ⚫️              | ⚫️                | 🚧 [^12]                   |
-| Logpush      | ⚫️              | ✅                | 🚧 [^13]                   |
-| Log Explorer | ⚫️              | ⚫️                | ✘ [^23]                    |
+| Logpull      | ⚫️             | ⚫️               | 🚧 [^12]                   |
+| Logpush      | ⚫️             | ✅                | 🚧 [^13]                   |
+| Log Explorer | ⚫️             | ⚫️               | ✘ [^23]                    |
 
 ---
 
@@ -119,13 +119,13 @@ The tables below show whether each Cloudflare product is compatible with each DL
 | Product               | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | --------------------- | --------------- | ----------------- | -------------------------- |
 | Access                | 🚧 [^14]        | 🚧 [^15]          | ✅ [^16]                   |
-| Browser Isolation     | ⚫️              | 🚧 [^17]          | ✅                         |
-| CASB                  | ⚫️              | ⚫️                | ✘                          |
-| Cloudflare Tunnel     | ⚫️              | 🚧 [^18]          | ⚫️                         |
-| Digital Experience    | ⚫️              | ⚫️                | 🚧 [^49]                   |
-| DLP                   | ⚫️ [^19]        | ⚫️ [^19]          | 🚧 [^31]                   |
+| Browser Isolation     | ⚫️             | 🚧 [^17]          | ✅                         |
+| CASB                  | ⚫️             | ⚫️               | ✘                          |
+| Cloudflare Tunnel     | ⚫️             | 🚧 [^18]          | ⚫️                        |
+| Digital Experience    | ⚫️             | ⚫️               | 🚧 [^49]                   |
+| DLP                   | ⚫️ [^19]       | ⚫️ [^19]         | 🚧 [^31]                   |
 | Gateway               | 🚧 [^20]        | 🚧 [^21]          | 🚧 [^22]                   |
-| Cloudflare One Client | ⚫️              | ⚫️                | 🚧 [^1]                    |
+| Cloudflare One Client | ⚫️             | ⚫️               | 🚧 [^1]                    |
 
 [^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
 
diff --git a/src/content/docs/data-localization/geo-key-manager.mdx b/src/content/docs/data-localization/geo-key-manager.mdx
index 510eb40b49191a5..6bafbbf4ad50e68 100644
--- a/src/content/docs/data-localization/geo-key-manager.mdx
+++ b/src/content/docs/data-localization/geo-key-manager.mdx
@@ -9,6 +9,7 @@ tags:
   - Compliance
 sidebar:
   order: 4
+
 ---
 
 Geo Key Manager offers enhanced control over the storage location of your private SSL/TLS keys — the cryptographic keys that Cloudflare uses to decrypt your HTTPS traffic. By restricting where these keys are stored, you can ensure compliance with regional data regulations and security requirements.
@@ -23,7 +24,7 @@ Geo Key Manager was restricted to the US, EU, and high-security data centers, bu
 
 The following diagram shows what happens when an end user connects to a Cloudflare data center that does not hold your private key. Because TLS termination requires the private key, the local data center must request a temporary session key (a short-lived symmetric encryption key) from a data center in an authorized region. Once the session key is established, the local data center can decrypt traffic for the remainder of the connection without contacting the key-holding data center again. This extra step adds latency on the first request, which can be as much as a second if the key-holding data center is geographically distant.
 
-<br />
+<br/>
 
 ```mermaid
 sequenceDiagram
@@ -40,6 +41,6 @@ sequenceDiagram
     User-->>CloudflarePoP: Subsequent requests use the Session Key
 ```
 
-<br />
+<br/>
 
 For detailed information on setup and supported options, refer to [Geo Key Manager documentation](/ssl/edge-certificates/geokey-manager/).
diff --git a/src/content/docs/ddos-protection/about/components.mdx b/src/content/docs/ddos-protection/about/components.mdx
index 9161b6dd7d87b5a..fdad5713c8a928e 100644
--- a/src/content/docs/ddos-protection/about/components.mdx
+++ b/src/content/docs/ddos-protection/about/components.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 ![Diagram with the main components providing protection against DDoS attacks at Cloudflare](~/assets/images/ddos-protection/ddos-diagram.png)
 
diff --git a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
index 921203e498c7fda..2be132500131a7d 100644
--- a/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
+++ b/src/content/docs/ddos-protection/about/how-ddos-protection-works.mdx
@@ -9,9 +9,10 @@ sidebar:
 learning_center:
   title: What is a DDoS attack?
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To detect and mitigate <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attacks</GlossaryTooltip>, Cloudflare's autonomous edge and centralized DDoS systems analyze traffic samples out of path, which allows Cloudflare to asynchronously detect DDoS attacks without causing latency or impacting performance.
 
@@ -30,13 +31,13 @@ You can set an override expression for the [HTTP DDoS Attack Protection](/ddos-p
 
 Once attack traffic matches a rule, Cloudflare's systems will track that traffic and generate a real-time signature to surgically match against the attack pattern and mitigate the attack without impacting legitimate traffic. The rules are able to generate different signatures based on various properties of the attacks and the signal strength of each attribute. For example, if the attack is distributed — that is, originating from many source IPs — then the source IP field will not serve as a strong indicator, and the rule will not choose the source IP field as part of the attack signature. Once generated, the fingerprint is propagated as a mitigation rule to the most optimal location on the Cloudflare global network for cost-efficient mitigation. These mitigation rules are ephemeral and will expire shortly after the attack has ended, which happens when no additional traffic has been matched to the rule.
 
-| Actions               | Description                                                                                             |
-| --------------------- | ------------------------------------------------------------------------------------------------------- |
-| Block                 | Matching requests are denied access to the site.                                                        |
-| Managed Challenge     | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
-| Interactive Challenge | The client that made the request must pass an interactive Challenge.                                    |
-| Log                   | Records matching requests in the Cloudflare Logs.                                                       |
-| Use rule defaults     | Uses the default action that is pre-defined for each rule.                                              |
+| Actions | Description |
+| --- | --- |
+| Block | Matching requests are denied access to the site. |
+| Managed Challenge | Depending on the characteristics of a request, Cloudflare will choose an appropriate type of challenge. |
+| Interactive Challenge | The client that made the request must pass an interactive Challenge. |
+| Log | Records matching requests in the Cloudflare Logs. |
+| Use rule defaults | Uses the default action that is pre-defined for each rule. |
 
 ## Thresholds
 
diff --git a/src/content/docs/ddos-protection/about/index.mdx b/src/content/docs/ddos-protection/about/index.mdx
index c294dbc5482978b..65805b05908aecd 100644
--- a/src/content/docs/ddos-protection/about/index.mdx
+++ b/src/content/docs/ddos-protection/about/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: About Cloudflare DDoS protection
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare provides unmetered and unlimited <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">distributed denial-of-service (DDoS)</GlossaryTooltip> protection at layers 3, 4, and 7 to all customers on all plans and services.
 
@@ -19,4 +20,4 @@ The protection is enabled by Cloudflare's [Autonomous DDoS Protection Edge](/ddo
 
 The Autonomous Edge includes multiple dynamic mitigation rules exposed as [managed rulesets](/ddos-protection/managed-rulesets/), which provide comprehensive protection against a variety of DDoS attacks across layers 3/4 and layer 7 of the OSI model.
 
-[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
+[Adaptive DDoS Protection](/ddos-protection/managed-rulesets/adaptive-protection/) also learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4. Your Internet properties can be secured from sophisticated TCP and DNS DDoS attacks using [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) that leverages stateful inspection and traffic profiling.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
index 011867f5ba98440..80a1257af1beb09 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/index.mdx
@@ -10,6 +10,7 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced DNS Protection via API
+
 ---
 
 Use the [Cloudflare API](/api/) to configure Advanced DNS Protection via API.
@@ -28,11 +29,11 @@ The `{account_id}` argument is the [account ID](/fundamentals/account/find-accou
 
 The following table summarizes the available operations.
 
-| Operation                       | Verb + Endpoint                                                                                                                                                               |
-| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List DNS protection rules       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account.                                 |
-| Add a DNS protection rule       | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account.                                      |
-| Get a DNS protection rule       | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
-| Update a DNS protection rule    | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account.              |
-| Delete a DNS protection rule    | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account.           |
-| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account.                   |
+| Operation | Verb + Endpoint |
+| --- | --- |
+| List DNS protection rules | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Fetches all DNS protection rules in the account. |
+| Add a DNS protection rule | <p>`POST accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Adds a DNS protection rule to the account. |
+| Get a DNS protection rule | <p>`GET accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Fetches the details of an existing DNS protection rule in the account. |
+| Update a DNS protection rule | <p>`PATCH accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Updates an existing DNS protection rule in the account. |
+| Delete a DNS protection rule | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules/{rule_id}`</p>Deletes an existing DNS protection rule from the account. |
+| Delete all DNS protection rules | <p>`DELETE accounts/{account_id}/magic/advanced_dns_protection/configs/dns_protection/rules`</p>Deletes all existing DNS protection rules from the account. |
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
index 803a3e818448f83..1c556c9c56533bc 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/dns-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
+
 ---
 
 # JSON object
@@ -19,15 +20,15 @@ This page contains an example of the DNS protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"mode": "monitoring",
-	"profile_sensitivity": "medium",
-	"rate_sensitivity": "medium",
-	"burst_sensitivity": "medium",
-	"created_on": "2023-10-01T13:10:38.762503+01:00",
-	"modified_on": "2023-10-01T13:10:38.762503+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "mode": "monitoring",
+  "profile_sensitivity": "medium",
+  "rate_sensitivity": "medium",
+  "burst_sensitivity": "medium",
+  "created_on": "2023-10-01T13:10:38.762503+01:00",
+  "modified_on": "2023-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -39,4 +40,4 @@ The `profile_sensitivity` field value must be one of `low` (default), `medium`,
 
 The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`, `medium`, or `high`.
 
-For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
+For more information on the rule settings, refer to [Rule settings](/ddos-protection/advanced-ddos-systems/concepts/#rule-settings).
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
index 52ffefc830a024b..703796d727a36f1 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Configure Advanced TCP Protection and Advanced DNS Protection via the API
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages to configure Advanced TCP Protection and Advanced DNS Protection via the API.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
index 2783ca32b25243f..75c5ed4d2392138 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/examples.mdx
@@ -8,6 +8,7 @@ tags:
   - REST API
 sidebar:
   order: 2
+
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/#endpoints).
@@ -23,18 +24,18 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<PROGRAM_ID>",
-			"name": "rate-limiter",
-			"status": "success",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<PROGRAM_ID>",
+      "name": "rate-limiter",
+      "status": "success",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -51,16 +52,16 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<PROGRAM_ID>",
-		"name": "program",
-		"status": "success",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<PROGRAM_ID>",
+    "name": "program",
+    "status": "success",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -68,15 +69,15 @@ If the program fails compilation or verification, the API returns a detailed err
 
 ```json title="Example error response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"code": 1001,
-			"message": "Program verification failed: invalid memory access at line 42"
-		}
-	],
-	"messages": []
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "code": 1001,
+      "message": "Program verification failed: invalid memory access at line 42"
+    }
+  ],
+  "messages": []
 }
 ```
 
@@ -94,16 +95,16 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<PROGRAM_ID>",
-		"name": "program",
-		"status": "success",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<PROGRAM_ID>",
+    "name": "program",
+    "status": "success",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -119,10 +120,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": null,
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -137,21 +138,21 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID>",
-			"program_id": "<PROGRAM_ID>",
-			"scope": "global",
-			"name": "global",
-			"mode": "enabled",
-			"expression": "",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<RULE_ID>",
+      "program_id": "<PROGRAM_ID>",
+      "scope": "global",
+      "name": "global",
+      "mode": "enabled",
+      "expression": "",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -173,19 +174,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "global",
-		"name": "global",
-		"mode": "monitoring",
-		"expression": "",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "global",
+    "name": "global",
+    "mode": "monitoring",
+    "expression": "",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -210,19 +211,19 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "enabled",
-		"expression": "ip.dst in { 192.0.2.0/24 }",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "enabled",
+    "expression": "ip.dst in { 192.0.2.0/24 }",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -244,19 +245,19 @@ curl --request PATCH \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"program_id": "<PROGRAM_ID>",
-		"scope": "global",
-		"name": "global",
-		"mode": "enabled",
-		"expression": "",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "program_id": "<PROGRAM_ID>",
+    "scope": "global",
+    "name": "global",
+    "mode": "enabled",
+    "expression": "",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -274,10 +275,10 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": null,
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -298,7 +299,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/programma
 The output PCAP file contains the same packets as the input file, but with annotations on each packet.
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
index 5a3cb4ee6ba3756..e9ea67979faf416 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/index.mdx
@@ -12,6 +12,7 @@ sidebar:
 head:
   - tag: title
     content: Configure Programmable Flow Protection via API
+
 ---
 
 Use the [Cloudflare API](/api/) to configure Programmable Flow Protection.
@@ -32,30 +33,30 @@ The tables in the following sections summarize the available operations.
 
 ### Program operations
 
-| Operation           | Method and endpoint / Description                                                                                                                       |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List programs       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
-| Upload a program    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account.                            |
-| Get a program       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program.          |
-| Update a program    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program.                       |
-| Delete a program    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account.     |
-| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account.                |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List programs | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Fetches all Programmable Flow Protection programs in the account. |
+| Upload a program | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Uploads a new program to the account. |
+| Get a program | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Fetches the details of an existing program. |
+| Update a program | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Updates an existing program. |
+| Delete a program | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}`</p>Deletes an existing program from the account. |
+| Delete all programs | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/programs`</p>Deletes all existing programs from the account. |
 
 ### Rule operations
 
-| Operation        | Method and endpoint / Description                                                                                                                 |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List rules       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
-| Create a rule    | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account.                            |
-| Get a rule       | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule.             |
-| Update a rule    | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account.           |
-| Delete a rule    | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account.        |
-| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account.                |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List rules | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Fetches all Programmable Flow Protection rules in the account. |
+| Create a rule | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Creates a new rule in the account. |
+| Get a rule | <p>`GET accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Fetches the details of an existing rule. |
+| Update a rule | <p>`PATCH accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Updates an existing rule in the account. |
+| Delete a rule | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules/{rule_id}`</p>Deletes an existing rule from the account. |
+| Delete all rules | <p>`DELETE accounts/{account_id}/magic/programmable_flow_protection/configs/rules`</p>Deletes all existing rules from the account. |
 
 ### Debug operations
 
-| Operation       | Method and endpoint / Description                                                                                                                                                                |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation | Method and endpoint / Description |
+| --- | --- |
 | Debug with PCAP | <p>`POST accounts/{account_id}/magic/programmable_flow_protection/configs/programs/{program_id}/pcap`</p>Runs a program against a PCAP file and returns an annotated PCAP with program verdicts. |
 
 ## Pagination
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
index 7857e0cab2af7ad..f0fffca40457798 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/programmable-flow-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Programmable Flow Protection API - JSON objects
+
 ---
 
 This page contains examples of the JSON objects used in the Programmable Flow Protection API.
@@ -19,47 +20,47 @@ This page contains examples of the JSON objects used in the Programmable Flow Pr
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"name": "rate-limiter",
-	"status": "success",
-	"created_on": "2024-01-01T13:06:04.721954+01:00",
-	"modified_on": "2024-01-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "name": "rate-limiter",
+  "status": "success",
+  "created_on": "2024-01-01T13:06:04.721954+01:00",
+  "modified_on": "2024-01-01T13:06:04.721954+01:00"
 }
 ```
 
-| Field         | Description                                                                                                                                             |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`          | Unique identifier for the program.                                                                                                                      |
-| `name`        | Name of the program, derived from the uploaded filename.                                                                                                |
-| `status`      | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
-| `created_on`  | Timestamp when the program was created.                                                                                                                 |
-| `modified_on` | Timestamp when the program was last modified.                                                                                                           |
+| Field | Description |
+| --- | --- |
+| `id` | Unique identifier for the program. |
+| `name` | Name of the program, derived from the uploaded filename. |
+| `status` | Compilation and verification status. One of `success` or `failed`. Programs with `failed` status are automatically deleted after 30 days of inactivity. |
+| `created_on` | Timestamp when the program was created. |
+| `modified_on` | Timestamp when the program was last modified. |
 
 ## Rule
 
 ```json
 {
-	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-	"program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"mode": "enabled",
-	"expression": "ip.dst in { 192.0.2.0/24 }",
-	"created_on": "2024-01-01T13:10:38.762503+01:00",
-	"modified_on": "2024-01-01T13:10:38.762503+01:00"
+  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+  "program_id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "mode": "enabled",
+  "expression": "ip.dst in { 192.0.2.0/24 }",
+  "created_on": "2024-01-01T13:10:38.762503+01:00",
+  "modified_on": "2024-01-01T13:10:38.762503+01:00"
 }
 ```
 
-| Field         | Description                                                                                                                       |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `id`          | Unique identifier for the rule.                                                                                                   |
-| `program_id`  | The ID of the program this rule executes.                                                                                         |
-| `scope`       | The scope of the rule. Must be one of `global`, `region`, or `datacenter`.                                                        |
-| `name`        | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code.                 |
-| `mode`        | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`.                                                             |
-| `expression`  | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
-| `created_on`  | Timestamp when the rule was created.                                                                                              |
-| `modified_on` | Timestamp when the rule was last modified.                                                                                        |
+| Field | Description |
+| --- | --- |
+| `id` | Unique identifier for the rule. |
+| `program_id` | The ID of the program this rule executes. |
+| `scope` | The scope of the rule. Must be one of `global`, `region`, or `datacenter`. |
+| `name` | For `global` scope, use `global`. For `region` or `datacenter` scope, provide the region code or datacenter code. |
+| `mode` | The rule mode. Must be one of `enabled`, `disabled`, or `monitoring`. |
+| `expression` | A [Rules language expression](/ruleset-engine/rules-language/expressions/) to filter which packets the rule applies to. Optional. |
+| `created_on` | Timestamp when the rule was created. |
+| `modified_on` | Timestamp when the rule was last modified. |
 
 ### Scope
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
index c8ce427c16455cb..8e87b35dd014b57 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/examples.mdx
@@ -8,6 +8,7 @@ tags:
   - REST API
 sidebar:
   order: 2
+
 ---
 
 The following sections contain example requests for common API calls. For a list of available API endpoints, refer to [Endpoints](/ddos-protection/advanced-ddos-systems/api/tcp-protection/#endpoints).
@@ -23,12 +24,12 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json title="Example response"
 {
-	"result": {
-		"enabled": false
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "enabled": false
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -57,16 +58,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"prefix": "203.0.113/24",
-			"comment": "My prefix",
-			"excluded": false
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "prefix": "203.0.113/24",
+      "comment": "My prefix",
+      "excluded": false
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -94,27 +95,27 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<PREFIX_1_ID>",
-			"prefix": "192.0.2.0/24",
-			"excluded": false,
-			"comment": "Game ranges",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		},
-		{
-			"id": "<PREFIX_2_ID>",
-			"prefix": "192.0.2.2/26",
-			"excluded": true,
-			"comment": "Range for a specific game",
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<PREFIX_1_ID>",
+      "prefix": "192.0.2.0/24",
+      "excluded": false,
+      "comment": "Game ranges",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    },
+    {
+      "id": "<PREFIX_2_ID>",
+      "prefix": "192.0.2.2/26",
+      "excluded": true,
+      "comment": "Range for a specific game",
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -129,19 +130,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<ALLOWLIST_PREFIX_ID>",
-			"prefix": "192.0.2.127",
-			"comment": "Single IP address in allowlist",
-			"enabled": true,
-			"created_on": "<TIMESTAMP>",
-			"modified_on": "<TIMESTAMP>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<ALLOWLIST_PREFIX_ID>",
+      "prefix": "192.0.2.127",
+      "comment": "Single IP address in allowlist",
+      "enabled": true,
+      "created_on": "<TIMESTAMP>",
+      "modified_on": "<TIMESTAMP>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -162,17 +163,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<ALLOWLIST_PREFIX_1_ID>",
-		"prefix": "203.0.113.0/26",
-		"comment": "Partner range",
-		"enabled": true,
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<ALLOWLIST_PREFIX_1_ID>",
+    "prefix": "203.0.113.0/26",
+    "comment": "Partner range",
+    "enabled": true,
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -195,19 +196,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<SYN_FLOOD_RULE_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "monitoring",
-		"rate_sensitivity": "medium",
-		"burst_sensitivity": "medium",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<SYN_FLOOD_RULE_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "monitoring",
+    "rate_sensitivity": "medium",
+    "burst_sensitivity": "medium",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -232,19 +233,19 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<OOS_TCP_RULE_ID>",
-		"scope": "region",
-		"name": "WEUR",
-		"mode": "monitoring",
-		"rate_sensitivity": "low",
-		"burst_sensitivity": "low",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<OOS_TCP_RULE_ID>",
+    "scope": "region",
+    "name": "WEUR",
+    "mode": "monitoring",
+    "rate_sensitivity": "low",
+    "burst_sensitivity": "low",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -266,16 +267,16 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<SYN_FLOOD_FILTER_ID>",
-		"expression": "ip.dst in { 192.0.2.0/24 }",
-		"mode": "monitoring",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<SYN_FLOOD_FILTER_ID>",
+    "expression": "ip.dst in { 192.0.2.0/24 }",
+    "mode": "monitoring",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -297,17 +298,17 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/advanced_t
 
 ```json output
 {
-	"result": {
-		"id": "<OOS_TCP_FILTER_ID>",
-		"expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
-		"mode": "disabled",
-		"created_on": "<TIMESTAMP>",
-		"modified_on": "<TIMESTAMP>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<OOS_TCP_FILTER_ID>",
+    "expression": "ip.dst in { 203.0.113.0/24 } and tcp.dstport in { 8000..8081 }",
+    "mode": "disabled",
+    "created_on": "<TIMESTAMP>",
+    "modified_on": "<TIMESTAMP>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
-Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
+Refer to [JSON objects](/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects/) for more information on the fields in the JSON body.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
index 5af3cfacb95b70f..54d00d15660f858 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/index.mdx
@@ -12,6 +12,7 @@ head:
     content: Configure Advanced TCP Protection via API
 tags:
   - TCP
+
 ---
 
 You can configure Advanced TCP Protection using the Advanced TCP Protection API.
@@ -36,81 +37,81 @@ The tables in the following sections summarize the available operations.
 
 ### General operations
 
-| Operation                             | Method and endpoint / Description                                                                                                                                   |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Get Advanced TCP Protection status    | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| Get Advanced TCP Protection status | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Gets the global Advanced TCP Protection status (enabled or disabled). |
 | Update Advanced TCP Protection status | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_protection_status`</p>Enables or disables Advanced TCP Protection.                        |
 
 ### Prefix operations
 
-| Operation            | Method and endpoint / Description                                                                                                                             |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List prefixes        | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account.                 |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Fetches all Advanced TCP Protection prefixes in the account. |
 | Add prefixes in bulk | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/bulk`</p>Adds prefixes in bulk to the account (up to 300 prefixes per request). |
-| Get a prefix         | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix.                       |
-| Update a prefix      | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix.                                    |
-| Delete a prefix      | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix.                                   |
-| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account.                           |
+| Get a prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Fetches the details of an existing prefix. |
+| Update a prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Updates an existing prefix. |
+| Delete a prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes/{prefix_id}`</p>Deletes an existing prefix. |
+| Delete all prefixes  | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/prefixes`</p>Deletes all existing prefixes from the account. |
 
 ### Allowlist operations
 
-| Operation                       | Method and endpoint / Description                                                                                                                            |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List allowlisted prefixes       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
-| Add an allowlisted prefix       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
-| Get an allowlisted prefix       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
-| Update an allowlisted prefix    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist.              |
-| Delete an allowlisted prefix    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist.           |
-| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist.                       |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List allowlisted prefixes | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Fetches all prefixes in the account allowlist.                             |
+| Add an allowlisted prefix | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Adds a prefix to the allowlist.                                           |
+| Get an allowlisted prefix | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Fetches the details of an existing prefix in the allowlist. |
+| Update an allowlisted prefix | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Updates an existing prefix in the allowlist. |
+| Delete an allowlisted prefix | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist/{allowlist_id}`</p>Deletes an existing prefix from the allowlist. |
+| Delete all allowlisted prefixes | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/allowlist`</p>Deletes all existing prefixes from the allowlist. |
 
 ### SYN Flood Protection operations
 
 #### Rules
 
-| Operation                  | Method and endpoint / Description                                                                                                                                        |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List SYN flood rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account.                                 |
-| Add a SYN flood rule       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account.                                      |
-| Get a SYN flood rule       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
-| Update a SYN flood rule    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account.              |
-| Delete a SYN flood rule    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account.           |
-| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account.                   |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List SYN flood rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Fetches all SYN flood rules in the account. |
+| Add a SYN flood rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Adds a SYN flood rule to the account. |
+| Get a SYN flood rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Fetches the details of an existing SYN flood rule in the account. |
+| Update a SYN flood rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Updates an existing SYN flood rule in the account. |
+| Delete a SYN flood rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules/{rule_id}`</p>Deletes an existing SYN flood rule from the account. |
+| Delete all SYN flood rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/rules`</p>Deletes all existing SYN flood rules from the account. |
 
 #### Filters
 
-| Operation                    | Method and endpoint / Description                                                                                                                                              |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List SYN flood filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account.                                   |
-| Add a SYN flood filter       | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account.                                        |
-| Get a SYN flood filter       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
-| Update a SYN flood filter    | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account.              |
-| Delete a SYN flood filter    | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account.           |
-| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account.                     |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List SYN flood filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Fetches all SYN flood filters in the account. |
+| Add a SYN flood filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Adds a SYN flood filter to the account. |
+| Get a SYN flood filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Fetches the details of an existing SYN flood filter in the account. |
+| Update a SYN flood filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Updates an existing SYN flood filter in the account. |
+| Delete a SYN flood filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters/{filter_id}`</p>Deletes an existing SYN flood filter from the account. |
+| Delete all SYN flood filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/syn_protection/filters`</p>Deletes all existing SYN flood filters from the account. |
 
 ### Out-of-state TCP Protection operations
 
 #### Rules
 
-| Operation                         | Method and endpoint / Description                                                                                                                                                    |
-| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List out-of-state TCP rules       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account.                                 |
-| Add an out-of-state TCP rule      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account.                                     |
-| Get an out-of-state TCP rule      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
-| Update an out-of-state TCP rule   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account.              |
-| Delete an out-of-state TCP rule   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account.           |
-| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account.                   |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List out-of-state TCP rules | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Fetches all out-of-state TCP rules in the account. |
+| Add an out-of-state TCP rule | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Adds an out-of-state TCP rule to the account. |
+| Get an out-of-state TCP rule | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Fetches the details of an existing out-of-state TCP rule in the account. |
+| Update an out-of-state TCP rule | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Updates an existing out-of-state TCP rule in the account. |
+| Delete an out-of-state TCP rule | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules/{rule_id}`</p>Deletes an existing out-of-state TCP rule from the account. |
+| Delete all out-of-state TCP rules | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/rules`</p>Deletes all existing out-of-state TCP rules from the account. |
 
 #### Filters
 
-| Operation                           | Method and endpoint / Description                                                                                                                                                          |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| List out-of-state TCP filters       | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account.                                   |
-| Add an out-of-state TCP filter      | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account.                                       |
-| Get an out-of-state TCP filter      | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
-| Update an out-of-state TCP filter   | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account.              |
-| Delete an out-of-state TCP filter   | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account.           |
-| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account.                     |
+| Operation | Method and endpoint / Description |
+| --- | --- |
+| List out-of-state TCP filters | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Fetches all out-of-state TCP filters in the account. |
+| Add an out-of-state TCP filter | <p>`POST accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Adds an out-of-state TCP filter to the account. |
+| Get an out-of-state TCP filter | <p>`GET accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Fetches the details of an existing out-of-state TCP filter in the account. |
+| Update an out-of-state TCP filter | <p>`PATCH accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Updates an existing out-of-state TCP filter in the account. |
+| Delete an out-of-state TCP filter | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters/{filter_id}`</p>Deletes an existing out-of-state TCP filter from the account. |
+| Delete all out-of-state TCP filters | <p>`DELETE accounts/{account_id}/magic/advanced_tcp_protection/configs/tcp_flow_protection/filters`</p>Deletes all existing out-of-state TCP filters from the account. |
 
 ## Pagination
 
-The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
+The API operations that return a list of items use pagination. For more information on the available pagination query parameters, refer to [Pagination](/fundamentals/api/how-to/make-api-calls/#pagination).
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
index 1368cbecbe0cfe8..b2186e3c55edc9b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/api/tcp-protection/json-objects.mdx
@@ -11,6 +11,7 @@ sidebar:
 head:
   - tag: title
     content: Advanced TCP Protection API - JSON objects
+
 ---
 
 This page contains an example of the TCP protection rule JSON object used in the API.
@@ -19,12 +20,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"prefix": "192.0.2.0/24",
-	"comment": "Game ranges",
-	"excluded": false,
-	"created_on": "2022-01-01T13:06:04.721954+01:00",
-	"modified_on": "2022-01-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "prefix": "192.0.2.0/24",
+  "comment": "Game ranges",
+  "excluded": false,
+  "created_on": "2022-01-01T13:06:04.721954+01:00",
+  "modified_on": "2022-01-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -32,12 +33,12 @@ This page contains an example of the TCP protection rule JSON object used in the
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"prefix": "192.0.2.0/24",
-	"comment": "Game ranges",
-	"enabled": true,
-	"created_on": "2021-10-01T13:06:04.721954+01:00",
-	"modified_on": "2021-10-01T13:06:04.721954+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "prefix": "192.0.2.0/24",
+  "comment": "Game ranges",
+  "enabled": true,
+  "created_on": "2021-10-01T13:06:04.721954+01:00",
+  "modified_on": "2021-10-01T13:06:04.721954+01:00"
 }
 ```
 
@@ -47,13 +48,13 @@ The `prefix` field can contain an IP address or a CIDR range.
 
 ```json
 {
-	"id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
-	"scope": "region",
-	"name": "WEUR",
-	"rate_sensitivity": "medium",
-	"burst_sensitivity": "medium",
-	"created_on": "2021-10-01T13:10:38.762503+01:00",
-	"modified_on": "2021-10-01T13:10:38.762503+01:00"
+  "id": "31c70c65-9f81-4669-94ed-1e1e041e7b06",
+  "scope": "region",
+  "name": "WEUR",
+  "rate_sensitivity": "medium",
+  "burst_sensitivity": "medium",
+  "created_on": "2021-10-01T13:10:38.762503+01:00",
+  "modified_on": "2021-10-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -65,11 +66,11 @@ The `rate_sensitivity` and `burst_sensitivity` field values must be one of `low`
 
 ```json
 {
-	"id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
-	"expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
-	"mode": "enabled",
-	"created_on": "2022-11-01T13:10:38.762503+01:00",
-	"modified_on": "2022-11-01T13:10:38.762503+01:00"
+  "id": "20b99eb6-8b48-48dd-a5b9-a995a0843b57",
+  "expression": "ip.dst in { 192.0.2.0/24 203.0.113.0/24 } and tcp.dstport in { 80 443 10000..65535 }",
+  "mode": "enabled",
+  "created_on": "2022-11-01T13:10:38.762503+01:00",
+  "modified_on": "2022-11-01T13:10:38.762503+01:00"
 }
 ```
 
@@ -85,4 +86,4 @@ The `expression` field is a [Rules language expression](/ruleset-engine/rules-la
 Expressions of SYN flood protection and out-of-state TCP protection filters do not currently support functions.
 :::
 
-The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
+The `mode` value must be one of `enabled`, `disabled`, or `monitoring`.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
index e542bce53c6b4fa..7906194f1a69e0b 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
@@ -9,9 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Add a prefix to Advanced DDoS Protection
----
 
-import { Steps, DashButton } from "~/components";
+---
+import { Steps, DashButton } from "~/components"
 
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
@@ -28,4 +28,4 @@ To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to
 :::note[Note]
 
 The **Add existing prefix** list will not display leased prefixes, but you can add them manually in the Cloudflare dashboard or [using the API](/ddos-protection/advanced-ddos-systems/api/). You cannot add [delegated prefixes](/byoip/concepts/prefix-delegations/) to Advanced TCP Protection.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
index 405eeb35a0dab05..df2d627092922fe 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 5
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
@@ -25,4 +26,4 @@ To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 :::note
 
 Prefixes or subsets added as _Excluded_ will not be protected by Advanced TCP Protection.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
index 87c03f48746ed33..19ab785b897da72 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: How-to guides
 description: How-to guides for configuring Advanced TCP Protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
index fe36b285e12bed7..7ee74065ee74642 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/index.mdx
@@ -8,9 +8,11 @@ sidebar:
   group:
     hideIndex: true
   order: 6
+
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on Cloudflare's Advanced DDoS systems:
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
index bedd9eaac204c3e..495f1aa4c759f15 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
@@ -39,20 +39,20 @@ Once thresholds are configured, the Advanced DDoS Protection systems have been i
 
 Automatic thresholds for Cloudflare's Advanced DDoS Protection system optimizes the detection and mitigation of DDoS attacks by automatically calculating appropriate traffic thresholds for each system for each customer account. This system applies to Advanced TCP Protection (specifically SYN Flood Protection and Out-of-State TCP Flood Protection) and Advanced DNS Protection.
 
-Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds.
+Make sure that you have properly onboarded to the Advanced DDoS Protection system to benefit from automatic thresholds. 
 
 #### Process
 
-The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below.
+The automatic threshold system calculates thresholds every 10 minutes for both new and existing Magic Transit accounts, provided they meet the requirements outlined in the process below. 
 
 - The `flowtrackd` account was created within the past 7 to 10 days.
 - The account has at least one configured global threshold (rate and burst). This can be a threshold that was automatically provisioned by the system or manually provisioned by Cloudflare.
 
 These checks are performed independently for SYN Flood Protection, Out-of-State TCP Flood Protection, and Advanced DNS Protection. The criteria does not require the presence of any rules to be configured. Accounts initially provisioned by the automatic system will have default thresholds. Otherwise, thresholds may be unconfigured if they are not set by Cloudflare.
 
-After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic.
+After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic. 
 
-Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst.
+Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst. 
 
 Thresholds are derived using the 95th percentile (P95) of observed traffic over the preceding seven days:
 
@@ -60,9 +60,9 @@ Thresholds are derived using the 95th percentile (P95) of observed traffic over
 - Out-of-State TCP Flood Protection: Based on all other TCP flag traffic.
 - Advanced DNS Protection: Based on DNS over UDP traffic.
 
-While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance.
+While the calculation typically occurs automatically after seven days, Cloudflare can force an earlier calculation if you want to enable the system in protective mode in advance. 
 
-The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team.
+The automatic threshold calculation system does not differentiate between legitimate and attack traffic. If you are onboarded or experience attacks during the seven day observation period, the calculated thresholds may be inaccurate, depending on the attack's size, duration, and frequency relative to legitimate traffic. In such cases, Cloudflare will likely need to trigger a recalculation. Future improvements will allow you to run a recalculation without the assistance of your Cloudflare account team. 
 
 #### Implementation
 
@@ -70,7 +70,7 @@ You should enable the automatically provisioned rules. Initially, these rules wi
 
 #### Recalculation
 
-Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration.
+Automatic thresholds are calculated only once. Cloudflare can manually trigger a recalculation. Adding, approving, removing, delegating, advertising, or withdrawing prefixes after initial onboarding does not automatically re-trigger the calculation. It is recommended to move the relevant systems to Monitor mode before making changes that impact traffic levels and requesting a recalculation from Cloudflare. Future improvements will take these events into consideration. 
 
 #### Overrides
 
@@ -82,7 +82,7 @@ If you are actively under attack and diverting traffic to Cloudflare, the automa
 
 #### Limitations
 
-Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated.
+Customers currently do not have visibility into the calculated thresholds or an indication of whether thresholds have been configured. Future improvements aim to indicate when thresholds have been configured and when they were last updated. 
 
 The auto-threshold calculation component currently runs only in PDX. Therefore, this feature is not compatible if you have enabled Data Localization Services (DLS) and are located outside of the US, such as EU CMB. Future improvements will address this limitation.
 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
index 8e7eeb417b2d7c0..5c86d3ba72f115a 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection.mdx
@@ -60,7 +60,7 @@ The Programmable Flow Protection system supports the [Data Localization suite](/
 :::caution[Beta functionality limitations]
 
 For more information on beta services, refer to section 2.6 in the [Enterprise Terms of Service](https://www.cloudflare.com/enterpriseterms/).
-:::
+  :::
 
 ### Write a basic program
 
@@ -210,7 +210,6 @@ The steps below write a sample program that drops all User Datagram Protocol (UD
 </Steps>
 
 For reference, the example below is the basic program in its entirety:
-
 ```c
 #define CF_EBPF_HELPER_V0
 
@@ -270,6 +269,7 @@ cf_ebpf_main(void *state)
 }
 ```
 
+
 ### Write a complex program: challenge-based response
 
 The example program below implements a UDP-based challenge-response mechanism using helper functions to maintain state between packets from the same source IP. This is useful for mitigating DDoS attacks by requiring clients to prove they can receive and respond to challenges before allowing their traffic through.
@@ -644,12 +644,12 @@ For reference, the example below is the rate limiting program in its entirety:
 #define RATE_LIMIT 100         // Maximum packets allowed per window
 #define WINDOW_SECONDS 60      // Time window in seconds
 
-// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the
+// The source IP table holds a mapping from source IP -> custom u64. We will make the custom u64 value in the 
 // table hold a timestamp and a counter to accomplish a ratelimit.
-//
-// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted.
+// 
+// NOTE: the source IP table is effectively a LRU cache. If it is full, old values will be evicted. 
 // Values are also garbage collected from the table every 1hr.
-//
+// 
 // The macros below pack the timestamp (upper 32 bits) and counter (lower 32 bits) into 64-bit data
 // into a value that we can store into the source IP table.
 #define PACK_STATE(ts, count) (((uint64_t)(ts) << 32) | ((uint64_t)(count) & 0xFFFFFFFF))
@@ -727,15 +727,14 @@ If an incoming packet's source IP is blocklisted in the source IP state table, t
 
 The source IP state table stores state keyed by source IP address. Each entry contains:
 
-| Field     | Type  | Description                                                                                      |
-| --------- | ----- | ------------------------------------------------------------------------------------------------ |
-| Status    | Enum  | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
-| User data | `u64` | A user-defined value you can set for any purpose.                                                |
+| Field | Type | Description |
+| --- | --- | --- |
+| Status | Enum | The status of the source IP: `None` (0), `Challenged` (1), `Verified` (2), or `Blocklisted` (3). |
+| User data | `u64` | A user-defined value you can set for any purpose. |
 
 The default maximum capacity is 1,000 entries.
 
 Use the following helper functions to interact with this table:
-
 - `get_src_ip_status` — Retrieve the status of the current packet's source IP.
 - `set_src_ip_status` — Set the status of the current packet's source IP.
 - `get_src_ip_data` — Retrieve the user data for the current packet's source IP.
@@ -748,7 +747,6 @@ The flow state table stores state keyed by the 4-tuple: source IP, source port,
 The default maximum capacity is 10,000 entries.
 
 Use the following helper functions to interact with this table:
-
 - `get_flow_data` — Retrieve the user data for the current flow.
 - `set_flow_data` — Store user data for the current flow.
 
@@ -770,32 +768,32 @@ Helper functions may be removed or changed. New helper functions may be introduc
 
 The table below provides a list of currently supported helper functions:
 
-| Function name               | Function signature                                                                          | Description                                                                                                                                                                                                                             |
-| --------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `rand`                      | `uint64_t rand(void)`                                                                       | Generates a random unsigned integer.                                                                                                                                                                                                    |
-| `timestamp`                 | `uint64_t timestamp(void)`                                                                  | Returns the current timestamp.                                                                                                                                                                                                          |
-| `hash_md5`                  | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)`                                  | Computes MD5 hash of the source buffer and stores result in destination buffer.                                                                                                                                                         |
-| `hash_sha256`               | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-256 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
-| `hash_sha512`               | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)`                               | Computes SHA-512 hash of the source buffer and stores result in destination buffer.                                                                                                                                                     |
-| `hash_crc32`                | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)`                                | Computes CRC32 hash of the source buffer and stores result in destination buffer.                                                                                                                                                       |
-| `hmac_sha256`               | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
-| `hmac_sha512`               | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer.                                                                                                                                     |
-| `set_challenge`             | `int set_challenge(uint8_t *src, size_t src_len)`                                           | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset.                                                                                                                                                 |
-| `get_src_ip_status`         | `uint64_t get_src_ip_status(void)`                                                          | Retrieves the status value associated with the source IP address from the state table.                                                                                                                                                  |
-| `set_src_ip_status`         | `int set_src_ip_status(uint64_t status)`                                                    | Sets the status value associated with the source IP address in the state table.                                                                                                                                                         |
-| `get_src_ip_data`           | `int get_src_ip_data(uint8_t *dst, size_t dst_len)`                                         | Retrieves custom data associated with the source IP address from the state table.                                                                                                                                                       |
-| `set_src_ip_data`           | `int set_src_ip_data(uint8_t *src, size_t src_len)`                                         | Stores custom data associated with the source IP address in the state table.                                                                                                                                                            |
-| `get_flow_data`             | `int get_flow_data(uint8_t *dst, size_t dst_len)`                                           | Retrieves custom data associated with the current flow from the state table.                                                                                                                                                            |
-| `set_flow_data`             | `int set_flow_data(uint8_t *src, size_t src_len)`                                           | Stores custom data associated with the current flow in the state table.                                                                                                                                                                 |
-| `entropy`                   | `double entropy(uint8_t *src, size_t src_len)`                                              | Calculates the entropy of the source buffer.                                                                                                                                                                                            |
-| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)`                                                  | Sets a custom tag for network analytics reporting. Defaults to `0` if not set.                                                                                                                                                          |
-| `ntohs`                     | `uint16_t ntohs(uint16_t netshort)`                                                         | Converts a 16-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htons`                     | `uint16_t htons(uint16_t hostshort)`                                                        | Converts a 16-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `ntohl`                     | `uint32_t ntohl(uint32_t netlong)`                                                          | Converts a 32-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htonl`                     | `uint32_t htonl(uint32_t hostlong)`                                                         | Converts a 32-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `ntohll`                    | `uint64_t ntohll(uint64_t netlonglong)`                                                     | Converts a 64-bit integer from network byte order to host byte order.                                                                                                                                                                   |
-| `htonll`                    | `uint64_t htonll(uint64_t hostlonglong)`                                                    | Converts a 64-bit integer from host byte order to network byte order.                                                                                                                                                                   |
-| `parse_packet_data`         | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)`   | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
+| Function name       | Function signature                                                               | Description                                                                                                                                                                                                                             |
+| ------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rand`      | `uint64_t rand(void)`                                                                           | Generates a random unsigned integer.                                                                                                                                                                                                    |
+| `timestamp` | `uint64_t timestamp(void)` | Returns the current timestamp. |
+| `hash_md5` | `int hash_md5(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes MD5 hash of the source buffer and stores result in destination buffer. |
+| `hash_sha256` | `int hash_sha256(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-256 hash of the source buffer and stores result in destination buffer. |
+| `hash_sha512` | `int hash_sha512(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes SHA-512 hash of the source buffer and stores result in destination buffer. |
+| `hash_crc32` | `int hash_crc32(uint8_t *src, size_t src_len, uint8_t *dst)` | Computes CRC32 hash of the source buffer and stores result in destination buffer. |
+| `hmac_sha256` | `int hmac_sha256(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA256 of the message using the provided key and stores result in destination buffer. |
+| `hmac_sha512` | `int hmac_sha512(uint8_t *key, size_t key_len, uint8_t *msg, size_t msg_len, uint8_t *dst)` | Computes HMAC-SHA512 of the message using the provided key and stores result in destination buffer. |
+| `set_challenge` | `int set_challenge(uint8_t *src, size_t src_len)` | Sets challenge data for the current packet. If src_len is 0, challenge buffer is reset. |
+| `get_src_ip_status` | `uint64_t get_src_ip_status(void)` | Retrieves the status value associated with the source IP address from the state table. |
+| `set_src_ip_status` | `int set_src_ip_status(uint64_t status)` | Sets the status value associated with the source IP address in the state table. |
+| `get_src_ip_data` | `int get_src_ip_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the source IP address from the state table. |
+| `set_src_ip_data` | `int set_src_ip_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the source IP address in the state table. |
+| `get_flow_data` | `int get_flow_data(uint8_t *dst, size_t dst_len)` | Retrieves custom data associated with the current flow from the state table. |
+| `set_flow_data` | `int set_flow_data(uint8_t *src, size_t src_len)` | Stores custom data associated with the current flow in the state table. |
+| `entropy` | `double entropy(uint8_t *src, size_t src_len)` | Calculates the entropy of the source buffer. |
+| `set_network_analytics_tag` | `int set_network_analytics_tag(Tag value)` | Sets a custom tag for network analytics reporting. Defaults to `0` if not set. |
+| `ntohs` | `uint16_t ntohs(uint16_t netshort)` | Converts a 16-bit integer from network byte order to host byte order. |
+| `htons` | `uint16_t htons(uint16_t hostshort)` | Converts a 16-bit integer from host byte order to network byte order. |
+| `ntohl` | `uint32_t ntohl(uint32_t netlong)` | Converts a 32-bit integer from network byte order to host byte order. |
+| `htonl` | `uint32_t htonl(uint32_t hostlong)` | Converts a 32-bit integer from host byte order to network byte order. |
+| `ntohll` | `uint64_t ntohll(uint64_t netlonglong)` | Converts a 64-bit integer from network byte order to host byte order. |
+| `htonll` | `uint64_t htonll(uint64_t hostlonglong)` | Converts a 64-bit integer from host byte order to network byte order. |
+| `parse_packet_data` | `int parse_packet_data(cf_ebpf_generic_ctx, cf_ebpf_packet_data, cf_ebpf_parsed_headers)` | Use input `cf_ebpf_generic_ctx` and `cf_ebpf_packet_data` to generate valid `cf_ebpf_parsed_headers`.<br />Upon success, `cf_ebpf_parsed_headers` will contain valid IP and UDP headers.<br />Returns `0` on success or `1` on failure. |
 
 ---
 
@@ -807,7 +805,7 @@ With the exception of `rand`, `timestamp`, `ntohs`, `htons`, `ntohl`, `htonl`, `
 
 To upload a program, navigate to Networking > L3/4 DDoS protection > Advanced Protection in the Cloudflare dashboard. Then select the tab titled Programmable Flow Protection.
 
-Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code.
+Under **Programs**, click the button "Upload new program." This will prompt you to select a file to upload with your `C` source code. 
 
 The Cloudflare API will receive the source code in the `C` file, compile it into BPF bytecode, and run the verifier against it.
 
@@ -815,11 +813,12 @@ If compilation or verification fails, the API will return a detailed error messa
 
 If compilation and verification succeeds, Cloudflare will store the source code and object file to the account and return the program ID.
 
+
 ### Update a program
 
 During the development process, you may find it useful to update the same program (identified by the same program ID) instead of repeatedly creating new programs as new resources.
 
-To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code.
+To update the program, select the three dots next to your program. Then, select **Overwrite**. This will prompt you to choose a file to upload as your `C` source code. 
 
 :::note
 It is possible to update and overwrite a program that is currently in use by one or more rules. When doing so, you will be warned that the program is currently active and will be overwritten. However, if an active program is being updated with a program that either does not compile or can not be verified, the update will fail and the old program will continue to be in use.
@@ -833,7 +832,7 @@ A link icon next to the program name indicates that the program is currently in
 
 ### Delete a program
 
-To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**.
+To delete a program, select the three dots next to the program that you wish to delete. Then, select **Delete**. 
 
 Note that you will not be able to delete a program that is referenced in an active Rule.
 
@@ -888,11 +887,10 @@ curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/programmab
 
 The Packet Comment annotation may contain:
 
-- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`
+- Program return value: `CF_EBPF_PASS` or `CF_EBPF_DROP`  
 - `Ignored`: if the incoming packet is not UDP
 - `Analytics tag`: the custom network analytics tag set by the program on this packet, if any
 - `Challenge packet`: the challenge packet emitted from the program back to the client, if any
-
 ---
 
 ## Safe program and rule deployment best practices
@@ -1013,7 +1011,7 @@ struct cf_ebpf_parsed_headers {
    uint8_t        *data_end;
 };
 
-/*
+/* 
 * IPv4 header, used as field of cf_ebpf_parsed_headers */
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ip.h#L87
 */
@@ -1036,10 +1034,10 @@ struct iphdr {
     uint32_t daddr;
 };
 
-/*
+/* 
 * IPv6 header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/ipv6.h#L118
-*/
+*/ 
 struct ipv6hdr {
 #if defined(__BYTE_ORDER__) && __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
     uint8_t  version:4,
@@ -1056,7 +1054,7 @@ struct ipv6hdr {
     uint8_t  daddr[16];
 };
 
-/*
+/* 
 * UDP header, used as field of cf_ebpf_parsed_headers
 * source: https://github.com/torvalds/linux/blob/a7423e6ea2f8f6f453de79213c26f7a36c86d9a2/include/uapi/linux/udp.h#L23
 */
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
index 05220d120fb6f68..36422e1fcf667c9 100644
--- a/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
+++ b/src/content/docs/ddos-protection/advanced-ddos-systems/troubleshooting.mdx
@@ -19,7 +19,6 @@ Always transition from Monitoring mode to Mitigation (Enabled) mode. Do not swit
 When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Protection begins a learning period to observe existing connection state. Long-lived connections that pre-date this learning period may be dropped because they have no state in the tracker.
 
 **Recommended procedure:**
-
 1. Set to **Monitoring** mode for at least 4 hours (longer if your network has long-lived connections).
 2. Review the Monitoring mode logs in [Network Analytics](/analytics/network-analytics/) to confirm legitimate traffic patterns.
 3. Switch to **Mitigation (Enabled)** mode.
@@ -28,12 +27,12 @@ When you switch directly from Disabled to Mitigation (Enabled), Advanced TCP Pro
 
 Check the **Mitigation reason** field in the **Advanced TCP Protection** tab of [Network Analytics](/analytics/network-analytics/) and use the reason to identify the cause:
 
-| Mitigation reason                | Likely cause                                                                              | Action                                                                                                  |
-| -------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
-| **Not found**                    | Learning period was incomplete, or long-lived connections pre-date ATP activation         | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled)                                |
-| **Unexpected**                   | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
-| **Out of sequence**              | Packet reordering or packet loss in the network path                                      | Increase burst sensitivity threshold for the affected colo                                              |
-| Drops during traffic spikes only | Burst sensitivity threshold too low                                                       | Increase burst sensitivity (keep rate sensitivity the same)                                             |
+| Mitigation reason | Likely cause | Action |
+|---|---|---|
+| **Not found** | Learning period was incomplete, or long-lived connections pre-date ATP activation | Set to Monitoring mode for 4+ hours, then switch to Mitigation (Enabled) |
+| **Unexpected** | ECMP rehashing — packets from the same flow arriving at different Cloudflare data centers | Set to Monitoring mode; increase burst sensitivity threshold for affected colos; escalate if persistent |
+| **Out of sequence** | Packet reordering or packet loss in the network path | Increase burst sensitivity threshold for the affected colo |
+| Drops during traffic spikes only | Burst sensitivity threshold too low | Increase burst sensitivity (keep rate sensitivity the same) |
 
 **Threshold tuning:** Adjust burst sensitivity before rate sensitivity. Burst sensitivity handles momentary spikes; rate sensitivity controls sustained packet rates.
 
diff --git a/src/content/docs/ddos-protection/best-practices/index.mdx b/src/content/docs/ddos-protection/best-practices/index.mdx
index d5e1f5b2afacde1..c90d2aafc0fd31d 100644
--- a/src/content/docs/ddos-protection/best-practices/index.mdx
+++ b/src/content/docs/ddos-protection/best-practices/index.mdx
@@ -9,9 +9,10 @@ sidebar:
     hideIndex: true
 head: []
 description: Learn about best practices for configuring Cloudflare's DDoS protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information on DDoS protection best practices:
 
diff --git a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
index 07721304f2cfb3c..4be4546f04f6fa5 100644
--- a/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
+++ b/src/content/docs/ddos-protection/best-practices/proactive-defense.mdx
@@ -11,7 +11,7 @@ tags:
   - Caching
 ---
 
-import { GlossaryTooltip, Steps } from "~/components";
+import { GlossaryTooltip, Steps } from "~/components"
 
 Cloudflare's network automatically mitigates large <GlossaryTooltip term="distributed denial-of-service (DDoS) attack" link="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/">DDoS attacks</GlossaryTooltip>, but these attacks can still affect your application.
 
@@ -35,4 +35,4 @@ In addition to the steps for all customers, Cloudflare Enterprise customers subs
 
 ## Magic Transit customers
 
-In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
+In addition to the steps for all customers, Cloudflare Magic Transit customers should ensure that the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), and [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) are enabled and that their configurations are optimized.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/best-practices/third-party.mdx b/src/content/docs/ddos-protection/best-practices/third-party.mdx
index f7d646f767015f2..5e4e9065879bfc6 100644
--- a/src/content/docs/ddos-protection/best-practices/third-party.mdx
+++ b/src/content/docs/ddos-protection/best-practices/third-party.mdx
@@ -25,7 +25,7 @@ Therefore, it is recommended that you **use the [Cloudflare CDN](/cache/)**, whi
 - You perform DDoS filtering in the first point of contact from the Internet, which is a recommended best practice.
 
 :::caution[L3/4 DDoS mitigation accuracy]
-Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation.
+Using a third-party WAF or CDN service in front of Cloudflare can negatively impact the accuracy of L3/4 DDoS mitigation. 
 
 When traffic is proxied through another vendor, the vendor's IP addresses are available to Cloudflare's network-layer protection systems rather than the true client IP addresses. This lack of visibility into the original source can lead to less effective automated mitigation and potential false positives.
 :::
diff --git a/src/content/docs/ddos-protection/botnet-threat-feed.mdx b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
index 8058f8d886012b1..ba3a7ca8409be2e 100644
--- a/src/content/docs/ddos-protection/botnet-threat-feed.mdx
+++ b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
@@ -14,9 +14,9 @@ learning_center:
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-botnet/
 tags:
   - REST API
----
 
-import { Steps, APIRequest, DashButton } from "~/components";
+---
+import { Steps, APIRequest, DashButton } from "~/components"
 
 The Cloudflare DDoS Botnet Threat Feed is a threat intelligence feed for service providers (SPs) such as hosting providers and Internet service providers (ISPs) that provides information about their own IP addresses that have participated in HTTP DDoS attacks as observed from Cloudflare's global network. The feed aims to help service providers stop the abuse and reduce DDoS attacks originating from within their networks.
 
@@ -85,7 +85,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
 - The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
 - Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
 - When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
-  :::
+:::
 
 To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:
 
@@ -103,23 +103,23 @@ Retrieves all the data in the botnet tracking database for a given ASN (currentl
 The provided `{asn}` must be affiliated with your account.
 
 <APIRequest
-	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
-	method="GET"
+  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/full_report"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"cidr": "127.0.0.1/32",
-			"date": "1970-01-01T00:00:00Z",
-			"offense_count": 10000
-		}
-		// ... other entries ...
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "cidr": "127.0.0.1/32",
+      "date": "1970-01-01T00:00:00Z",
+      "offense_count": 10000
+    },
+    // ... other entries ...
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -135,22 +135,22 @@ The provided `{asn}` must be affiliated with your account.
 `{date}` must be an ISO 8601-formatted date: `YYYY-MM-DD`. If no date is specified, the API responds with the data from the day before.
 
 <APIRequest
-	path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
-	method="GET"
+  path="/accounts/{account_id}/botnet_feed/asn/{asn_id}/day_report"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"cidr": "127.0.0.1/32",
-			"date": "2024-05-05T00:00:00Z",
-			"offense_count": 10000
-		}
-		// ... other entries ...
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "cidr": "127.0.0.1/32",
+      "date": "2024-05-05T00:00:00Z",
+      "offense_count": 10000
+    },
+    // ... other entries ...
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
index 294386d75a7913f..23e89367c6df2b1 100644
--- a/src/content/docs/ddos-protection/get-started.mdx
+++ b/src/content/docs/ddos-protection/get-started.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 3
+
 ---
 
-import { Steps } from "~/components";
+import { Steps } from "~/components"
 
 ## Free, Pro, and Business plans
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
index da3c36e2cef5dc2..d811b5a27be035b 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
@@ -55,7 +55,7 @@ Cloudflare HTTP DDoS Protection can also initiate mitigation based on the origin
 This rule is available for zones on any plan.
 :::
 
-While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules:
+While Cloudflare's network is built to automatically monitor and mitigate large DDoS attacks, Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules: 
 
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by configuring the HTTP DDoS Attack Protection managed ruleset.
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
index d30b1f397074ef2..aa5cf2850cf749b 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/index.mdx
@@ -6,6 +6,7 @@ products:
   - ddos-protection
 sidebar:
   order: 5
+
 ---
 
 The DDoS Attack Protection managed rulesets provide comprehensive protection against a [variety of DDoS attacks](/ddos-protection/about/attack-coverage/) across L3/4 (network layer) and L7 (application layer) of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/).
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
index ec4a3407ca3c976..08ab036ae1868dc 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/index.mdx
@@ -54,7 +54,7 @@ While you can manually override a rule from `Log` to `Block`, consider the follo
 
 - The default action of a rule is decided during the testing period. Cloudflare may set its default action to **DDoS Dynamic**, which may use rate-limiting or a multi-step mitigation combination based on traffic factors. By applying a manual `Block` override, you prevent your configuration from automatically inheriting the more nuanced DDoS Dynamic action once it is released.
 
-If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action.
+If you choose to override a testing rule to mitigate an active attack, Cloudflare recommends reviewing that override periodically to see if the rule has been promoted to a permanent default action. 
 
 ## Availability
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
index 526d496f44f19d3..679aaba3f002a27 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/network/network-overrides/override-examples.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Override examples for Network-layer DDoS Attack Protection
+
 ---
 
-import { Details, GlossaryTooltip, DashButton } from "~/components";
+import { Details, GlossaryTooltip, DashButton } from "~/components"
 
 ## Use cases
 
@@ -35,12 +36,11 @@ To avoid disruptions during initial deployment, you can create a _Log_ only –
 
 1. In the Cloudflare dashboard, go to the **Security rules** page.
 
-   <DashButton url="/?to=/:account/:zone/security/security-rules" />
-
+    <DashButton url="/?to=/:account/:zone/security/security-rules" />
 2. Go to the **DDoS protection** tab.
 3. On **HTTP DDoS attack protection**, select **Create override**.
 4. Set the **Scope** to _Apply to all incoming requests_.
 5. Under **Ruleset configuration**:
-   - Set the **Ruleset action** to _Log_.
-   - Set the **Ruleset sensitivity** to _Essentially Off_.
-6. Select **Save**.
+    - Set the **Ruleset action** to _Log_.
+    - Set the **Ruleset sensitivity** to _Essentially Off_. 
+6. Select **Save**. 
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/reference/alerts.mdx b/src/content/docs/ddos-protection/reference/alerts.mdx
index 2d58a70a27086ca..02ded106c58f5b9 100644
--- a/src/content/docs/ddos-protection/reference/alerts.mdx
+++ b/src/content/docs/ddos-protection/reference/alerts.mdx
@@ -108,4 +108,4 @@ To investigate a possibly ongoing attack, select **View Dashboard**. To go to th
 - In some cases, HTTP DDoS attack alerts will reference the attacked zone name instead of the attacked hostname. This occurs when the attack signature does not include information on the attacked hostname because it is not a strong indicator for identifying attack requests. For more information on attack signatures, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
 - DDoS alerts are currently only available for DDoS attacks detected and mitigated by the [DDoS managed rulesets](/ddos-protection/managed-rulesets/). Alerts are not yet available for DDoS attacks detected and mitigated by the [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/), the [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/), or the [Programmable Flow Protection](/ddos-protection/advanced-ddos-systems/overview/programmable-flow-protection/) system.
 - You will not receive duplicate DDoS alerts within the same one-hour time frame.
-- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
+- If you configure more than one alert type for the same kind of attack (for example, both an HTTP DDoS Attack Alert and an Advanced HTTP DDoS Attack Alert) you may get more than one notification when an attack occurs. To avoid receiving duplicate notifications, delete one of the configured alerts.
\ No newline at end of file
diff --git a/src/content/docs/ddos-protection/reference/index.mdx b/src/content/docs/ddos-protection/reference/index.mdx
index 3ae60ce4bd017c0..1ffe418f0eceaf3 100644
--- a/src/content/docs/ddos-protection/reference/index.mdx
+++ b/src/content/docs/ddos-protection/reference/index.mdx
@@ -9,9 +9,10 @@ sidebar:
     hideIndex: true
 head: []
 description: Reference information for Cloudflare's DDoS protection.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Cloudflare DDoS protection:
 
diff --git a/src/content/docs/ddos-protection/reference/logs.mdx b/src/content/docs/ddos-protection/reference/logs.mdx
index 1bbc798b5e49584..f0d23899c38c060 100644
--- a/src/content/docs/ddos-protection/reference/logs.mdx
+++ b/src/content/docs/ddos-protection/reference/logs.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: DDoS logs
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Retrieve HTTP events using [Cloudflare Logs](/logs/) to integrate them into your <GlossaryTooltip term="SIEM">SIEM systems</GlossaryTooltip>.
 
diff --git a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
index 20dba8ba991db4e..187dff380ea2545 100644
--- a/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
+++ b/src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
@@ -6,9 +6,10 @@ products:
   - ddos-protection
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 After onboarding to Cloudflare, you may want to simulate DDoS attacks against your Internet properties to test the protection, [reporting](/ddos-protection/reference/reports/), and [alerting](/ddos-protection/reference/alerts/) mechanisms. Follow the guidelines in this section to simulate a DDoS attack.
 
diff --git a/src/content/docs/dmarc-management/enable.mdx b/src/content/docs/dmarc-management/enable.mdx
index c38ef8ef703db1d..1eeb169d8368e0c 100644
--- a/src/content/docs/dmarc-management/enable.mdx
+++ b/src/content/docs/dmarc-management/enable.mdx
@@ -10,6 +10,7 @@ sidebar:
     text: Beta
 tags:
   - DNS
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -29,4 +30,4 @@ To enable DMARC Management:
    - If no DMARC record is found, Cloudflare will automatically invite you to add one that you can edit later. Select **Add** to continue.
    - If a DMARC record is found in your zone, Cloudflare will add another `rua` (Reporting URI for Aggregate data) entry to it. The `rua` tag specifies the URI (typically a `mailto:` address) where aggregate DMARC reports are sent. This additional entry uses a Cloudflare email address so that Cloudflare can receive and process DMARC reports on your behalf. Select **Next** to continue.
 
-DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
+DMARC Management (beta) is now active. However, it may take up to 24 hours to receive your first DMARC report and to display this information in DMARC Management.
\ No newline at end of file
diff --git a/src/content/docs/dmarc-management/security-records.mdx b/src/content/docs/dmarc-management/security-records.mdx
index df2912e19e4d6cc..2ec513fecf908f2 100644
--- a/src/content/docs/dmarc-management/security-records.mdx
+++ b/src/content/docs/dmarc-management/security-records.mdx
@@ -29,4 +29,4 @@ To set up email security records:
 
 ## Edit or delete records
 
-Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
+Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for more information.
\ No newline at end of file
diff --git a/src/content/docs/dmarc-management/statistics.mdx b/src/content/docs/dmarc-management/statistics.mdx
index b9186d28b90635d..58a5e6ea804a49b 100644
--- a/src/content/docs/dmarc-management/statistics.mdx
+++ b/src/content/docs/dmarc-management/statistics.mdx
@@ -11,6 +11,7 @@ head:
     content: Review DMARC statistics
 tags:
   - DNS
+
 ---
 
 DMARC Management (beta) allows you to review whether emails sent on your behalf passed or failed DMARC, SPF, and DKIM authentication checks.
diff --git a/src/content/docs/dns/additional-options/index.mdx b/src/content/docs/dns/additional-options/index.mdx
index 2c2a6572e2ac236..66b93896ae59062 100644
--- a/src/content/docs/dns/additional-options/index.mdx
+++ b/src/content/docs/dns/additional-options/index.mdx
@@ -10,7 +10,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Beyond [setting up your zone](/dns/zone-setups/) and [updating your DNS records](/dns/manage-dns-records/), you may want to customize the following settings in Cloudflare DNS:
 
diff --git a/src/content/docs/dns/changelog.mdx b/src/content/docs/dns/changelog.mdx
index 3c688d1cb2da69d..b1163dea5558b84 100644
--- a/src/content/docs/dns/changelog.mdx
+++ b/src/content/docs/dns/changelog.mdx
@@ -12,7 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelogs/dns/. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="dns" />
+<ProductChangelog product="dns"/>
 
 ## 2025-01-27
 
@@ -26,11 +26,11 @@ Records returned by the API will no longer contain the `zone_id` and `zone_name`
 
 When creating [TXT records](/dns/manage-dns-records/reference/dns-record-types/#txt) via the dashboard you will now find:
 
-- Field validation errors if double quotes `"` are added inconsistently.
-- Automatically quoted TXT content upon save if no quotes exist in the record content field.
+* Field validation errors if double quotes `"` are added inconsistently.
+* Automatically quoted TXT content upon save if no quotes exist in the record content field.
 
 ## 2024-10-07
 
 **API support for per-record CNAME flattening**
 
-Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
+Paid zones now have the option to flatten specific CNAME records. When using the API, specify the setting `cname_flatten` as `true` or `false`. Refer to the [documentation](/dns/cname-flattening/set-up-cname-flattening/#per-record) for details.
\ No newline at end of file
diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx
index 521021c63c3011d..918f0fcc6932086 100644
--- a/src/content/docs/dns/cname-flattening/index.mdx
+++ b/src/content/docs/dns/cname-flattening/index.mdx
@@ -31,4 +31,4 @@ For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), re
 
 - CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
 - CNAME to a different Cloudflare account is prohibited and will result in [Error 1014: CNAME Cross-User Banned](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/)
-- <Render file="cname-flattening-callout" product="dns" />
+- <Render file="cname-flattening-callout" product="dns" />
\ No newline at end of file
diff --git a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
index 22b36e298b9f3bf..675a692b4527d82 100644
--- a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
+++ b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx
@@ -11,13 +11,7 @@ head:
     content: Set up CNAME flattening
 ---
 
-import {
-	Render,
-	TabItem,
-	Tabs,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components";
 
 :::note
 
diff --git a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
index c961134f600f565..3b579df96996538 100644
--- a/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
+++ b/src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Protect against random prefix attacks
+
 ---
 
 import { APIRequest } from "~/components";
@@ -22,10 +23,10 @@ In order to enable automatic mitigation of [random prefix attacks](/dns/dns-fire
    	path="/accounts/{account_id}/dns_firewall/{dns_firewall_id}"
    	method="PATCH"
    	json={{
-   		attack_mitigation: {
-   			enabled: true,
-   			only_when_upstream_unhealthy: true,
-   		},
+      "attack_mitigation": {
+        "enabled": true,
+        "only_when_upstream_unhealthy": true,
+      }
    	}}
    />
 
@@ -33,6 +34,8 @@ Once you receive a `200` success response from the API, queries identified as be
 
 :::note
 
+
 If you do not specify otherwise in your API call, Cloudflare automatically sets the `"only_when_upstream_unhealthy"` parameter to true, which means that Cloudflare will only mitigate attacks when we detect that the upstream is unresponsive (possibly as a result of an attack). This setting can also be changed via the API, using a request similar to the ones shown above.
 
+
 :::
diff --git a/src/content/docs/dns/dnssec/dnssec-states.mdx b/src/content/docs/dns/dnssec/dnssec-states.mdx
index 381c0a152b40f23..5b40526a38a6545 100644
--- a/src/content/docs/dns/dnssec/dnssec-states.mdx
+++ b/src/content/docs/dns/dnssec/dnssec-states.mdx
@@ -6,16 +6,17 @@ products:
 title: DNSSEC states
 sidebar:
   order: 4
+
 ---
 
 This page describes different DNSSEC states and how they relate to the responses you get from the [DNSSEC details API endpoint](/api/resources/dns/subresources/dnssec/methods/get/).
 
-| State            | API response                                                     | Description                                                                                                                                                                                 |
-| ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                                   |
-| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                           |
-| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                                      |
-| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                                  |
+| State            | API response                                                     | Description                                                                                                                                                                       |
+| ---------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pending          | `"status":"pending"`<br /> `"modified_on":<TIME_STAMP>`          | DNSSEC has been enabled but the Cloudflare DS record has not been added at the registrar.                                                                                         |
+| Active           | `"status":"active"`<br /> `"modified_on":<TIME_STAMP>`           | DNSSEC has been enabled and the Cloudflare DS record is present at the registrar.                                                                                                 |
+| Pending-disabled | `"status":"pending-disabled"`<br /> `"modified_on":<TIME_STAMP>` | DNSSEC has been disabled but the Cloudflare DS record is still added at the registrar.                                                                                            |
+| Disabled         | `"status":"disabled"`<br /> `"modified_on":<TIME_STAMP>`         | DNSSEC has been disabled and the Cloudflare DS record has been removed from the registrar.                                                                                        |
 | Deleted          | `"status":"disabled"`<br /> `"modified_on": null`                | DNSSEC has never been enabled for the zone or DNSSEC has been disabled and then deleted using the [Delete DNSSEC records endpoint](/api/resources/dns/subresources/dnssec/methods/delete/). |
 
 :::caution
diff --git a/src/content/docs/dns/dnssec/enable-nsec3.mdx b/src/content/docs/dns/dnssec/enable-nsec3.mdx
index adc9d72f7a3971a..710497fda89108a 100644
--- a/src/content/docs/dns/dnssec/enable-nsec3.mdx
+++ b/src/content/docs/dns/dnssec/enable-nsec3.mdx
@@ -22,8 +22,8 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met
 	path="/zones/{zone_id}/dnssec"
 	method="PATCH"
 	json={{
-		dnssec_use_nsec3: true,
-		status: "active",
+		"dnssec_use_nsec3": true,
+		"status": "active"
 	}}
 />
 
diff --git a/src/content/docs/dns/dnssec/index.mdx b/src/content/docs/dns/dnssec/index.mdx
index d58d3d633a1fcfb..a4f8af210e23313 100644
--- a/src/content/docs/dns/dnssec/index.mdx
+++ b/src/content/docs/dns/dnssec/index.mdx
@@ -6,13 +6,14 @@ products:
 title: DNSSEC
 sidebar:
   order: 8
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="dnssec-definition" product="dns" />
 
----
+***
 
 ## Disable DNSSEC
 
@@ -20,7 +21,7 @@ import { Render } from "~/components";
 
 <Render file="dnssec-enabled-migration" product="dns" />
 
----
+***
 
 ## Enable DNSSEC
 
@@ -36,7 +37,7 @@ When you enable DNSSEC, Cloudflare signs your zone, publishes your public signin
 
 <Render file="dnssec-auto-add" product="dns" />
 
----
+***
 
 ## Other DNSSEC setup options
 
@@ -44,14 +45,14 @@ If you are using Cloudflare as your Secondary DNS provider and want to configure
 
 If you want to set up DNSSEC on a subdomain zone, refer to [Subdomain DNSSEC](/dns/zone-setups/subdomain-setup/dnssec/).
 
----
+***
 
 ## Limitations
 
 If your registrar does not support DNSSEC with Cloudflare's preferred cipher choice (Algorithm 13), you have several options:
 
-- Contact your registrar to ask for DNSSEC with modern encryption.
-- Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
-- File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
+* Contact your registrar to ask for DNSSEC with modern encryption.
+* Transfer your domain to a different registrar that supports DNSSEC with Algorithm 13
+* File a [complaint with ICANN](https://www.icann.org/compliance/complaint), citing your registrar's lack of compliance.
 
-If your top-level domain does not support DNSSEC with Algorithm 13 (also known as _ECDSA Curve P-256 with SHA-256_), [contact that top-level domain](https://www.iana.org/domains/root/db).
+If your top-level domain does not support DNSSEC with Algorithm 13 (also known as *ECDSA Curve P-256 with SHA-256*), [contact that top-level domain](https://www.iana.org/domains/root/db).
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
index 1fd48842270e6c8..dea0d2d6371ecdd 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/about.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: About multi-signer DNSSEC
+
 ---
 
 Multi-signer DNSSEC consists of two models that allow different authoritative DNS providers to serve the same zone and have DNSSEC enabled at the same time.
@@ -19,6 +20,7 @@ You can [set up multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/) usi
 
 ## How it works
 
+
 :::note
 This is a simplified explanation to give you context and clarify what is involved in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/setup/). For technical details refer to [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html). To read more about DNSSEC, refer to [How DNSSEC works](https://www.cloudflare.com/dns/dnssec/how-dnssec-works/).
 :::
@@ -93,4 +95,4 @@ Multi-signer DNSSEC involves coordinating cryptographic keys across multiple pro
 1. Verify that both providers have each other's ZSKs in their DNSKEY RRsets.
 2. Confirm that both DS records are present at the registrar.
 3. Use DNSSEC validation tools to test resolution from both providers.
-4. Monitor for validation errors during the transition period.
+4. Monitor for validation errors during the transition period.
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
index b2c476f53cf14a9..99825944a7ae3ae 100644
--- a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
+++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx
@@ -173,4 +173,4 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
 
 1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
 
-2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
+2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.
\ No newline at end of file
diff --git a/src/content/docs/dns/dnssec/validation-and-key-management.mdx b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
index 307aec3cbfdc7e4..83711e5a34916e7 100644
--- a/src/content/docs/dns/dnssec/validation-and-key-management.mdx
+++ b/src/content/docs/dns/dnssec/validation-and-key-management.mdx
@@ -30,9 +30,9 @@ This is why you cannot simply keep your existing DS record when migrating to Clo
 
 When you enable DNSSEC, Cloudflare automatically publishes **CDS** (Child Delegation Signer) and **CDNSKEY** (Child DNSKEY) records in your zone. These records automate the chain of trust management between your domain and the Top-Level Domain registry.
 
-| Record      | Purpose                | Contents                                                                           |
-| ----------- | ---------------------- | ---------------------------------------------------------------------------------- |
-| **CDS**     | High-level instruction | A hashed version of the public key (same data as a DS record)                      |
+| Record | Purpose | Contents |
+| --- | --- | --- |
+| **CDS** | High-level instruction | A hashed version of the public key (same data as a DS record) |
 | **CDNSKEY** | Public key instruction | The full public Key Signing Key (KSK) for the parent to generate its own DS record |
 
 Registrars that support [RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html) periodically scan your domain for these records and automatically update the DS record at the registry level. This eliminates manual DS record management and ensures seamless key rollovers.
@@ -46,4 +46,4 @@ Not all registrars support automatic CDS/CDNSKEY scanning. If your registrar doe
 ## DNSKEY flags
 
 - **ZSKs (Zone Signing Keys)**: flag `256`
-- **KSKs (Key Signing Keys)**: flag `257`
+- **KSKs (Key Signing Keys)**: flag `257`
\ No newline at end of file
diff --git a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
index 37222616afae066..266d6dcc5a7d28d 100644
--- a/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
+++ b/src/content/docs/dns/foundation-dns/dnssec-keys.mdx
@@ -6,6 +6,7 @@ products:
 title: DNSSEC keys
 sidebar:
   order: 5
+
 ---
 
 With [Foundation DNS](/dns/foundation-dns/), you can request that the ZSK/KSK pair that is used for [DNSSEC](/dns/dnssec/) is unique to your Cloudflare account. To opt in to this feature, contact your account team.
@@ -16,4 +17,4 @@ All zones within your Cloudflare account - regardless of using [standard](/dns/n
 
 For more background information, refer to [How DNSSEC works](https://www.cloudflare.com/learning/dns/dnssec/how-dnssec-works/).
 
-For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
+For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/).
\ No newline at end of file
diff --git a/src/content/docs/dns/foundation-dns/index.mdx b/src/content/docs/dns/foundation-dns/index.mdx
index bb4381b3a49156f..0c60c2a7c820aca 100644
--- a/src/content/docs/dns/foundation-dns/index.mdx
+++ b/src/content/docs/dns/foundation-dns/index.mdx
@@ -6,21 +6,22 @@ products:
 title: Foundation DNS
 sidebar:
   order: 4
+
 ---
 
 Foundation DNS is the Cloudflare DNS offering for enterprise customers.
 
 With Foundation DNS, you get access to increased reliability, security, and insights. Features include the following:
 
-- [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
-  - Strategically distributed IPs to enhance resiliency
-  - Reduced exposure to incidents or software regression
-  - More consistent nameserver assignment
-- [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
-- Additional DNS settings, including:
-  - [Zone defaults](/dns/additional-options/dns-zone-defaults/)
-  - [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
-  - Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
+* [Advanced nameservers](/dns/foundation-dns/advanced-nameservers/) that provide:
+  * Strategically distributed IPs to enhance resiliency
+  * Reduced exposure to incidents or software regression
+  * More consistent nameserver assignment
+* [DNSSEC keys](/dns/foundation-dns/dnssec-keys/) unique to your account
+* Additional DNS settings, including:
+  * [Zone defaults](/dns/additional-options/dns-zone-defaults/)
+  * [Account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/)
+  * Custom [SOA record](/dns/manage-dns-records/reference/dns-record-types/#soa) and [Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl)
 
 ## Availability
 
@@ -32,5 +33,5 @@ Both advanced nameservers and unique ZSK/KSK are opt-in configurations. Refer to
 
 ## Related resources
 
-- [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
-- [Product page](https://www.cloudflare.com/dns/foundation-dns/)
+* [Release blog post](https://blog.cloudflare.com/foundation-dns-launch)
+* [Product page](https://www.cloudflare.com/dns/foundation-dns/)
diff --git a/src/content/docs/dns/glossary.mdx b/src/content/docs/dns/glossary.mdx
index 6b99f261ae66987..c7e9390c51ff273 100644
--- a/src/content/docs/dns/glossary.mdx
+++ b/src/content/docs/dns/glossary.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 30
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's DNS documentation.
 
diff --git a/src/content/docs/dns/internal-dns/analytics.mdx b/src/content/docs/dns/internal-dns/analytics.mdx
index b1608c69e81f1a0..af54b9d66ef1e04 100644
--- a/src/content/docs/dns/internal-dns/analytics.mdx
+++ b/src/content/docs/dns/internal-dns/analytics.mdx
@@ -28,4 +28,4 @@ The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to c
 
 Leverage Logpush jobs for [Gateway DNS](/logs/logpush/logpush-job/datasets/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation.
 
-You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
+You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
index 304c2d379c31eef..115c06fb29de7c0 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/create-subdomain.mdx
@@ -6,9 +6,10 @@ products:
 title: Create subdomain records
 sidebar:
   order: 4
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="create-subdomain-record" product="dns" />
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
index 6cfa20495a46cc1..bcaca8ad13ed17d 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/email-records.mdx
@@ -6,23 +6,24 @@ products:
 title: Set up email records
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 There are three reasons to set up email records for your domain:
 
-- To make sure your domain can [receive email](#receive-email).
-- To make sure your domain can [send and receive email](#send-and-receive-email).
-- To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
+* To make sure your domain can [receive email](#receive-email).
+* To make sure your domain can [send and receive email](#send-and-receive-email).
+* To prevent other email senders from [spoofing your domain](#prevent-domain-spoofing).
 
 The exact values for your DNS mail records depend on your email provider. If you have issues, review the [Troubleshooting](/dns/troubleshooting/email-issues/) and contact your email service provider to confirm your DNS records are correct.
 
----
+***
 
 <Render file="add-mx-records" product="dns" />
 
----
+***
 
 ## Prevent domain spoofing
 
@@ -34,4 +35,4 @@ Refer to [Security records](/dmarc-management/security-records/) to learn how to
 
 ## Proxy SMTP traffic
 
-By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
+By default, Cloudflare does not proxy email traffic on port 25 (SMTP). You can only proxy outgoing email if you have [Spectrum](/spectrum/) configured for [SMTP](/spectrum/reference/configuration-options/#smtp).
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/index.mdx b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
index 8ec9e0fc39b8c4d..f0d1c4dd9c45127 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/index.mdx
@@ -11,9 +11,10 @@ head:
   - tag: title
     content: DNS records - How to
 description: Learn how to use Cloudflare DNS to manage your DNS records.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following resources for more information about creating and maintaining DNS records:
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
index 44177c0cbae3d1a..e8f26982405820e 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses.mdx
@@ -6,6 +6,7 @@ products:
 title: Dynamically update DNS records
 sidebar:
   order: 13
+
 ---
 
 Most Internet service providers and some hosting providers dynamically update their customer's IP addresses. If this situation applies to you, you need an automated solution to dynamically update your DNS records in Cloudflare.
@@ -16,4 +17,4 @@ Create a script to monitor IP address changes and then have that script push cha
 
 ## ddclient
 
-[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
+[ddclient](https://github.com/ddclient/ddclient) is a third-party Perl client used to update dynamic DNS entries for accounts on various DNS providers.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
index 980e98757c3145e..9768ac45ceeda63 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
@@ -6,6 +6,7 @@ products:
 title: Round-robin DNS
 sidebar:
   order: 18
+
 ---
 
 To randomly distribute traffic across multiple servers, set up multiple DNS `A` or `AAAA` records for the same hostname.
diff --git a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
index 886b037b118a29a..d21e31b5faedd36 100644
--- a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
+++ b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx
@@ -7,9 +7,10 @@ source: https://support.cloudflare.com/hc/en-us/articles/360021357131-Delegating
 title: Delegate subdomains
 sidebar:
   order: 20
+
 ---
 
-import { FeatureTable, DashButton, Render } from "~/components";
+import { FeatureTable, DashButton, Render } from "~/components"
 
 Subdomain delegation allows different individuals, teams, or organizations to manage different subdomains of a site.
 
@@ -29,7 +30,7 @@ Cloudflare's CDN and security services are not applied to delegated subdomains.
 
 <FeatureTable id="dns.subdomain_delegation" />
 
----
+***
 
 ## Delegate a subdomain (outgoing)
 
@@ -42,12 +43,12 @@ To delegate a subdomain such as `blog.example.com`, tell DNS resolvers where to
    <DashButton url="/?to=/:account/:zone/dns/records" />
 
 4. Create `NS` records for the subdomain. For example:
-   - `blog.example.com NS ns1.externalhost.com`
-   - `blog.example.com NS ns2.externalhost.com`
-   - `blog.example.com NS ns3.externalhost.com`
-     :::note
-     The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
-     :::
+   * `blog.example.com NS ns1.externalhost.com`
+   * `blog.example.com NS ns2.externalhost.com`
+   * `blog.example.com NS ns3.externalhost.com`
+   :::note
+   The `A` records for the subdomain are only required as glue records for nameservers that are located in the subdomain of the current zone that is being delegated.
+   :::
 5. (Optional) If the delegated nameserver has DNSSEC enabled, [add the `DS` record](/dns/dnssec/#1-activate-dnssec-in-cloudflare) in Cloudflare.
 
 ### Limits
diff --git a/src/content/docs/dns/manage-dns-records/reference/index.mdx b/src/content/docs/dns/manage-dns-records/reference/index.mdx
index 1bbba02e42aadf2..435c9bbea21f1f9 100644
--- a/src/content/docs/dns/manage-dns-records/reference/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/index.mdx
@@ -11,8 +11,9 @@ head:
   - tag: title
     content: Reference — DNS records
 description: Check information about record types, status and additional options.
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
index 67e4399d03b9c75..99740688e33b318 100644
--- a/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/record-attributes.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: DNS record comments and tags
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 Use DNS record comments and tags to categorize and clarify the purpose of DNS records within Cloudflare.
 
@@ -19,17 +20,19 @@ Comments provide a unique descriptions for specific records, whereas tags group
 
 These attributes are particularly useful when:
 
-- Multiple teams are managing DNS records within the same zone.
-- Your zone contains a large number of DNS records.
-- You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
+* Multiple teams are managing DNS records within the same zone.
+* Your zone contains a large number of DNS records.
+* You want to filter your DNS records based on matching attributes (for example, when they are managed by the same team or used for the same application).
 
 :::note
 
+
 The information in record attributes will not impact DNS record resolution or propagation timing and is only meant for your private reference. This information is only visible to [members](/fundamentals/manage-members/manage/) of your Cloudflare account and is not visible publicly.
 
+
 :::
 
----
+***
 
 ## Availability
 
@@ -43,7 +46,7 @@ Comments and tags are only supported for [primary zones (full setup)](/dns/zone-
 
 <FeatureTable id="dns.record_tags" />
 
----
+***
 
 ## Add or edit record attributes
 
@@ -53,7 +56,7 @@ You can also add or edit attributes by [exporting and re-importing](/dns/manage-
 
 When exporting and importing, special tags starting by `cf-` allow you to control specific Cloudflare configurations. On export, these tags are automatically added to reflect the current configuration for each record on your zone. Refer to [reserved cf- tags](/dns/manage-dns-records/how-to/import-and-export/#reserved-cf--tags) for details.
 
----
+***
 
 ## Reference
 
diff --git a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
index 3f25313a41b3cd5..41114679b9e211e 100644
--- a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx
@@ -6,6 +6,7 @@ products:
 title: Time to Live (TTL)
 sidebar:
   order: 3
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -32,4 +33,4 @@ A TTL of **Auto** is set to 300 seconds (five minutes).
 
 ## Nameserver TTL
 
-[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
+[Nameserver TTL](/dns/nameservers/nameserver-options/#nameserver-ttl) is a separate feature and only affects Cloudflare nameservers and custom nameservers. For other [NS records](/dns/manage-dns-records/reference/dns-record-types/#ns) on your DNS records table, TTL is controlled by their respective TTL fields.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
index 4df29d02c4d8f19..2abc708b8e738ad 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/exposed-ip-address.mdx
@@ -29,6 +29,7 @@ When your zone has DNS records that are not proxied, the **DNS Records** page di
 
 `Proxying is required for most security and performance features. Set your DNS records to proxied by clicking "Edit" in the table below, to benefit from DDoS protection, security rules, caching, and more.`
 
+
 Individual DNS records may also display warnings. The specific message depends on whether the record can be proxied.
 
 ---
@@ -50,4 +51,4 @@ When a DNS-only record points to the same origin server as a proxied record, a `
 To mitigate this risk:
 
 - Analyze the impact of hosting multiple services on the same origin server in cases when you cannot avoid having DNS-only records.
-- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
+- Proxy all records that share the same origin IP address as your apex domain and can be safely proxied through Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
index 6dc331f5f84f29c..104ad57575d8b7f 100644
--- a/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/troubleshooting/index.mdx
@@ -11,10 +11,11 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS records
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
 
-- [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
+* [Delete all DNS records](/dns/zone-setups/troubleshooting/delete-all-records/)
diff --git a/src/content/docs/dns/nameservers/advanced-nameservers.mdx b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
index e545226613700b5..6138cff878b675f 100644
--- a/src/content/docs/dns/nameservers/advanced-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/advanced-nameservers.mdx
@@ -7,4 +7,5 @@ title: Advanced nameservers
 external_link: /dns/foundation-dns/advanced-nameservers/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
index d6fd863c76c52cf..c9268ed929c445c 100644
--- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
+++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx
@@ -56,7 +56,6 @@ The next step depends on whether you are using [Cloudflare Registrar](/registrar
 
 - If you are using Cloudflare Registrar for your domain, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to add the custom nameservers and IP addresses as glue records to the domain.
 - If you are not using Cloudflare Registrar for your domain, add the zone custom nameservers at your registrar as your authoritative nameservers and as glue (A and AAAA) records ([RFC 1912](https://www.rfc-editor.org/rfc/rfc1912.html)). If you do not add these records, DNS lookups for your domain will fail.
-
 ### Secondary zones
 
 If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), you can still set up zone custom nameservers. After following the [steps above](/dns/nameservers/custom-nameservers/zone-custom-nameservers/#primary-zones-full-setup) to create zone custom nameservers, do the following:
diff --git a/src/content/docs/dns/private-origins/index.mdx b/src/content/docs/dns/private-origins/index.mdx
index 49be787e2f6008e..8398f269855ab93 100644
--- a/src/content/docs/dns/private-origins/index.mdx
+++ b/src/content/docs/dns/private-origins/index.mdx
@@ -23,8 +23,7 @@ import {
 } from "~/components";
 
 <Description>
-	Proxy HTTP/HTTPS traffic from public hostnames to origins in your private
-	network.
+Proxy HTTP/HTTPS traffic from public hostnames to origins in your private network.
 </Description>
 
 <Plan type="enterprise" />
diff --git a/src/content/docs/dns/reference/all-features.mdx b/src/content/docs/dns/reference/all-features.mdx
index 8ef860d82833097..9186a4860de7efa 100644
--- a/src/content/docs/dns/reference/all-features.mdx
+++ b/src/content/docs/dns/reference/all-features.mdx
@@ -7,9 +7,10 @@ sidebar:
   order: 4
 head: []
 description: Review information on all Cloudflare DNS features and their availability.
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
diff --git a/src/content/docs/dns/reference/analytics-mcp-server.mdx b/src/content/docs/dns/reference/analytics-mcp-server.mdx
index 6d120789cebde25..de1faf7d51e1b2b 100644
--- a/src/content/docs/dns/reference/analytics-mcp-server.mdx
+++ b/src/content/docs/dns/reference/analytics-mcp-server.mdx
@@ -7,4 +7,5 @@ title: Analytics MCP server
 external_link: https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/dns-analytics
 sidebar:
   order: 90
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/best-practices.mdx b/src/content/docs/dns/reference/best-practices.mdx
index 9ef1525a0d2fb08..c4fe1210a6d1a7e 100644
--- a/src/content/docs/dns/reference/best-practices.mdx
+++ b/src/content/docs/dns/reference/best-practices.mdx
@@ -7,4 +7,5 @@ title: Migrate DNS from BIND
 external_link: /learning-paths/dns-best-practices/concepts/
 sidebar:
   order: 4
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/domain-connect.mdx b/src/content/docs/dns/reference/domain-connect.mdx
index fa4d6d8026995b0..06e2489b08294a7 100644
--- a/src/content/docs/dns/reference/domain-connect.mdx
+++ b/src/content/docs/dns/reference/domain-connect.mdx
@@ -23,8 +23,8 @@ In practice, this means that when a user that owns `example.com` and has Cloudfl
 
 ### Before you begin
 
-- Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
-- Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
+* Note that Cloudflare only supports the [Domain Connect synchronous flow](https://www.domainconnect.org/getting-started/).
+* Domain Connect templates and tools are published on GitHub, so you must have a GitHub account and be familiar with [GitHub forks and pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks).
 
 ### 1. Add templates to the repository
 
@@ -32,12 +32,12 @@ Domain Connect templates are published and maintained on a GitHub repository.
 
 1. Create a fork of the [templates repository](https://github.com/Domain-Connect/Templates).
 2. Add your template. You can create a copy of one of the existing templates and edit it according to your needs.
-   - Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
-     :::note
-     Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
-     :::
-   - If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
-   - You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
+   * Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
+	 :::note
+	 Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
+	 :::
+   * If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
+   * You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
 3. Make sure you follow the naming format defined by Domain Connect: `<providerId>.<serviceId>.json`.
 
 :::note[Tip]
@@ -155,4 +155,4 @@ The most common issues after template onboarding are validation errors, typicall
 
 You can fix these by republishing the signature, using tools such as the one provided by [Domain Connect](https://exampleservice.domainconnect.org/sig). Additionally, you can test signature validation with this [public key debug tool](https://github.com/kerolasa/dc-debug-pubkey).
 
-[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
+[^1]: A domain that can be queried for `TXT` records containing a public key to verify your digital signature. Refer to [digitally signed requests](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#digitally-sign-requests) for details.
\ No newline at end of file
diff --git a/src/content/docs/dns/reference/index.mdx b/src/content/docs/dns/reference/index.mdx
index 51f81d1b1b3aeac..e12d2e5c169f815 100644
--- a/src/content/docs/dns/reference/index.mdx
+++ b/src/content/docs/dns/reference/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/reference/recommended-third-party-tools.mdx b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
index 61e3bd775e91b13..3382d1ddc811487 100644
--- a/src/content/docs/dns/reference/recommended-third-party-tools.mdx
+++ b/src/content/docs/dns/reference/recommended-third-party-tools.mdx
@@ -7,14 +7,15 @@ sidebar:
   order: 3
 head: []
 description: List of recommended third-party tools for DNS testing and troubleshooting.
+
 ---
 
 You can use the third-party tools listed below to test and troubleshoot DNS settings.
 
-- [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
+* [DNSViz](https://dnsviz.net): A web-based tool for visualizing the status of a DNS zone to understand and troubleshoot the deployment of DNS Security Extensions (DNSSEC).
 
-- [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
+* [Dig Web Interface](https://digwebinterface.com): An online DNS lookup tool based on the command line interface `dig`. Users can skip the process of entering commands with complicated parameters in the terminal by entering the same information in this web tool and getting the same results.
 
-- [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
+* [dns.google](https://dns.google): A web-based tool, similar to Dig Web Interface, where users can get DNS responses for specific queries.
 
-- [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
+* [Mess with DNS](https://messwithdns.net): An educational resource that encourages users to experiment with DNS records by providing users with a domain where they are free to play around and break things during the learning process.
diff --git a/src/content/docs/dns/troubleshooting/email-issues.mdx b/src/content/docs/dns/troubleshooting/email-issues.mdx
index 291bb8f2240fef4..417ecfa92fdf7e1 100644
--- a/src/content/docs/dns/troubleshooting/email-issues.mdx
+++ b/src/content/docs/dns/troubleshooting/email-issues.mdx
@@ -85,12 +85,12 @@ If you are not sure whether the DNS content itself is correct, compare it with t
 
 Common examples include:
 
-| Provider         | MX records                                                                                                                                                                           | SPF record                                       |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
-| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all`            |
-| Microsoft 365    | `<your-domain>.mail.protection.outlook.com` (priority `0`)                                                                                                                           | `v=spf1 include:spf.protection.outlook.com -all` |
-| iCloud Mail      | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`)                                                                                                                    | `v=spf1 include:icloud.com ~all`                 |
-| Mailgun          | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`)                                                                                                                              | `v=spf1 include:mailgun.org ~all`                |
+| Provider | MX records | SPF record |
+| --- | --- | --- |
+| Google Workspace | `ASPMX.L.GOOGLE.COM` (priority `1`), `ALT1.ASPMX.L.GOOGLE.COM` and `ALT2.ASPMX.L.GOOGLE.COM` (priority `5`), `ALT3.ASPMX.L.GOOGLE.COM` and `ALT4.ASPMX.L.GOOGLE.COM` (priority `10`) | `v=spf1 include:_spf.google.com ~all` |
+| Microsoft 365 | `<your-domain>.mail.protection.outlook.com` (priority `0`) | `v=spf1 include:spf.protection.outlook.com -all` |
+| iCloud Mail | `mx01.mail.icloud.com` and `mx02.mail.icloud.com` (priority `10`) | `v=spf1 include:icloud.com ~all` |
+| Mailgun | `mxa.mailgun.org` and `mxb.mailgun.org` (priority `10`) | `v=spf1 include:mailgun.org ~all` |
 
 Always confirm the exact values with your provider before making changes.
 
diff --git a/src/content/docs/dns/troubleshooting/index.mdx b/src/content/docs/dns/troubleshooting/index.mdx
index b616c9d14356e9f..2ad611b0f95694a 100644
--- a/src/content/docs/dns/troubleshooting/index.mdx
+++ b/src/content/docs/dns/troubleshooting/index.mdx
@@ -9,13 +9,8 @@ sidebar:
   label: Full resources list
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 The following topics are useful for troubleshooting DNS issues.
 
-<ResourcesBySelector
-	directory="dns"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="dns" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
index 1b87486546a0e69..96a01af7dd298db 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx
@@ -11,13 +11,7 @@ description: >-
   If you initially configured a full setup you can later convert your zone to use incoming zone transfers (Cloudflare as secondary).
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
 
 If you initially configured a [primary setup (full)](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/).
 
@@ -43,14 +37,14 @@ Follow the steps below to achieve this conversion.
    <Render file="tsig-definition" product="dns" />
 
    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
-   
-      <Render file="tsig-create-dash" product="dns" />
-   
-      </TabItem> <TabItem label="API">
-   
-      <Render file="tsig-create-api" product="dns" />
-   
-      </TabItem> </Tabs>
+
+   <Render file="tsig-create-dash" product="dns" />
+
+   </TabItem> <TabItem label="API">
+
+   <Render file="tsig-create-api" product="dns" />
+
+   </TabItem> </Tabs>
 
 3. Create a peer server.
 
@@ -64,8 +58,8 @@ Follow the steps below to achieve this conversion.
    <DashButton url="/?to=/:account/:zone/dns/settings" />
 
 3. Select **Manage linked peers** under **DNS Zone Transfers**.
-4. Link the peer server you created in the previous steps and select **Save**.
-5. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
-6. Confirm the DNS records are transferring as expected.
-7. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
-8. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
+3. Link the peer server you created in the previous steps and select **Save**.
+4. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**.
+5. Confirm the DNS records are transferring as expected.
+6. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**.
+7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers.
diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
index 6c458149ea4d45b..f25552f8df2c42b 100644
--- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx
@@ -66,7 +66,7 @@ If you are counting on Universal SSL certificates to cover your website or appli
 :::
 
 Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page
-and add the DS record to your registrar.
+ and add the DS record to your registrar.
 
 Once all the DNS TTLs expire, all your DNS queries will be answered by the Cloudflare global network.
 
diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx
index 42226cfb7ad094d..04bc2c37ce4a3a5 100644
--- a/src/content/docs/dns/zone-setups/conversions/index.mdx
+++ b/src/content/docs/dns/zone-setups/conversions/index.mdx
@@ -15,4 +15,4 @@ import { DirectoryListing } from "~/components";
 
 You can perform the following DNS setup conversions:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/full-setup/index.mdx b/src/content/docs/dns/zone-setups/full-setup/index.mdx
index f92648b37069542..6a5717e76167fdf 100644
--- a/src/content/docs/dns/zone-setups/full-setup/index.mdx
+++ b/src/content/docs/dns/zone-setups/full-setup/index.mdx
@@ -19,4 +19,4 @@ For this to work, you must go through a few steps that involve not only Cloudfla
 
 ## Availability
 
-<FeatureTable id="dns.full_setup" />
+<FeatureTable id="dns.full_setup" />
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
index 1697f7240a301ac..45952ff6ebee99e 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: DNS resolution in partial zones
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 When you have a partial zone (<GlossaryTooltip term="CNAME setup" link="/dns/zone-setups/partial-setup/">CNAME setup</GlossaryTooltip>), Cloudflare handles DNS records a bit differently from primary zones (full setup) in order to internally resolve the origin server where proxied HTTP requests are sent to.
 
@@ -61,7 +62,7 @@ When you avoid this situation - meaning you do not have the **target** of the CN
       end
 ```
 
----
+***
 
 ## Records pointing to a partial zone within the same account
 
@@ -114,4 +115,4 @@ If such setup is in place, the subdomain (`www.partialzone.com` in this example)
       subgraph Authoritative DNS
       C
       end
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
index 627350007665712..0afa82eb5bc7ecb 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
@@ -13,15 +13,7 @@ description: >-
   A CNAME setup (also known as partial) allows you to use Cloudflare's reverse proxy while maintaining your primary and authoritative DNS provider.
 ---
 
-import {
-	Details,
-	Render,
-	GlossaryTooltip,
-	Steps,
-	Tabs,
-	TabItem,
-	APIRequest,
-} from "~/components";
+import { Details, Render, GlossaryTooltip, Steps, Tabs, TabItem, APIRequest } from "~/components";
 
 <Render file="partial-setup-definition" product="dns" />
 
@@ -48,6 +40,7 @@ A CNAME setup (partial) is only available to customers on a Business or Enterpri
 
 ## 1. Convert your zone and review DNS records
 
+
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 :::caution[Make sure you have the correct plan]
diff --git a/src/content/docs/dns/zone-setups/reference/domain-status.mdx b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
index 9541eaa1de5c4f2..2d26b5684dba1b2 100644
--- a/src/content/docs/dns/zone-setups/reference/domain-status.mdx
+++ b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
@@ -69,11 +69,11 @@ After you add your domain, Cloudflare performs checks on a schedule to confirm y
 
 The activation check behavior depends on your zone setup:
 
-| Zone setup                                                                                                                                                                                                                      | Activation requirement                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                      | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
-| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/) | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.           |
-| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                        | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                       |
+| Zone setup                                                                                                                                                                                                                          | Activation requirement                                                                                                                            |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) without [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns)                                                                                           | At the registrar (or parent zone), only the assigned Cloudflare nameservers must be listed. Any nameservers from other DNS providers cause failure. |
+| [Primary setup (full)](/dns/zone-setups/full-setup/) with [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns) enabled, or [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)      | At the registrar (or parent zone), the assigned Cloudflare nameservers must be present. Nameservers from other DNS providers are allowed.         |
+| [CNAME setup (partial)](/dns/zone-setups/partial-setup/)                                                                                                                                                                             | The verification TXT record must be present on your authoritative DNS provider. Nameservers at the registrar are not changed.                     |
 
 ### Expected behavior for different plans
 
diff --git a/src/content/docs/dns/zone-setups/reference/index.mdx b/src/content/docs/dns/zone-setups/reference/index.mdx
index 6185d7acd7149ea..a6c71ff65f2b7a8 100644
--- a/src/content/docs/dns/zone-setups/reference/index.mdx
+++ b/src/content/docs/dns/zone-setups/reference/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Reference — DNS zone setups
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
index 363f7e2bbee2c84..58cb7e6b8986b33 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/move-to-new-account.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Migrate subdomain to a new account
+
 ---
 
 When using a [subdomain setup](/dns/zone-setups/subdomain-setup/), you can have your subdomain as a separate zone within the same account as the parent domain or within a different account.
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
index 1a8c8cfae71d112..7523187ca70b247 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx
@@ -9,14 +9,15 @@ sidebar:
 head:
   - tag: title
     content: Rollback subdomain setup
+
 ---
 
 Refer to the following process to understand how you can rollback a [subdomain setup](/dns/zone-setups/subdomain-setup/) and recreate the corresponding subdomain DNS records in an existing parent zone within Cloudflare.
 
 ## Before you begin
 
-- This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
-- In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
+* This guide assumes both your child domain (`blog.example.com`) and its parent domain (`example.com`) are in Cloudflare.
+* In the child zone, review and [export](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records.
 
 :::caution[Important]
 
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
index 8cbfcf5e76c38b0..ed7910947587eae 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx
@@ -9,14 +9,17 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on full setup
+
 ---
 
 When the parent zone is using a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
 :::note
 
+
 The following steps are similar if your Cloudflare parent zone is in a secondary setup, with the only difference that you will use your external primary DNS provider to make any necessary adjustments to DNS records.
 
+
 :::
 
 ## Subdomain does not exist
diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
index 0ae18341ccfb5ac..46a0cf3ae1e1d99 100644
--- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
+++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Set up a child zone in Cloudflare with parent on partial setup
+
 ---
 
-import { Details, TabItem, Tabs } from "~/components";
+import { Details, TabItem, Tabs } from "~/components"
 
 When the parent zone is using a [CNAME setup (partial)](/dns/zone-setups/partial-setup/)[^2], the steps to set up your child zone depend on whether the subdomain already exists in the parent domain.
 
diff --git a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
index 485e9d9090a0bfb..d7b45d34cc6ea33 100644
--- a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
+++ b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting — DNS setups
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
index 6c1cdba3b2785b7..ee6a63ef200265e 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/index.mdx
@@ -17,7 +17,7 @@ When you [make edits](/dns/manage-dns-records/how-to/create-dns-records/) to Clo
 
 ## How to
 
-- [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
+* [Set up outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
index 284707a6b0416f1..854dcfad6b2831a 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/transfer-criteria.mdx
@@ -10,6 +10,7 @@ sidebar:
 
 Consider the sections below to understand the expected behaviors, depending on DNS record type and proxied status.
 
+
 ## Proxied records
 
 For each [proxied DNS record](/dns/proxy-status/) in your zone, Cloudflare will transfer out two `A` and two `AAAA` records.
@@ -41,4 +42,4 @@ The following records are not transferred out when you use Cloudflare as primary
 
 :::note
 Proxied Load Balancing records are transferred as explained in [Proxied records](#proxied-records).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
index f5191d5c420f6ce..bfd1df6c824f6a5 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/alerts.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Secondary DNS
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your secondary DNS.
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
index 2bb69c6bc3e6288..463cb6408c5cbb2 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/index.mdx
@@ -23,8 +23,8 @@ B & C <--DNS lookups--> D[Resolver] <--DNS lookups--> E((User))
 
 ## How to
 
-- [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
-- Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
+* [Set up incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/)
+* Proxy traffic through Cloudflare with [Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/)
 
 ## Availability
 
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
index b8a0e6712109252..a21202b1749130a 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx
@@ -81,4 +81,4 @@ Once you create a CNAME record at the apex, existing A or AAAA records on the zo
 
 ## Verify that your records are proxied
 
-Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
+Query DNS at your assigned Secondary DNS nameserver to confirm the DNS response Cloudflare returns. Records proxied by Cloudflare return [Cloudflare IPs](https://www.cloudflare.com/ips/).
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/api/alarms.mdx b/src/content/docs/durable-objects/api/alarms.mdx
index fa9a03af7538bea..4d576fbe8cd6cb3 100644
--- a/src/content/docs/durable-objects/api/alarms.mdx
+++ b/src/content/docs/durable-objects/api/alarms.mdx
@@ -38,42 +38,42 @@ Although each Durable Object can only have one alarm set at a time, you can mana
 import { DurableObject } from "cloudflare:workers";
 
 export class AgentServer extends DurableObject {
-	// Schedule a one-time or recurring event
-	async scheduleEvent(id, runAt, repeatMs = null) {
-		await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
-		const currentAlarm = await this.ctx.storage.getAlarm();
-		if (!currentAlarm || runAt < currentAlarm) {
-			await this.ctx.storage.setAlarm(runAt);
-		}
-	}
-
-	async alarm() {
-		const now = Date.now();
-		const events = await this.ctx.storage.list({ prefix: "event:" });
-		let nextAlarm = null;
-
-		for (const [key, event] of events) {
-			if (event.runAt <= now) {
-				await this.processEvent(event);
-				if (event.repeatMs) {
-					event.runAt = now + event.repeatMs;
-					await this.ctx.storage.put(key, event);
-				} else {
-					await this.ctx.storage.delete(key);
-				}
-			}
-			// Track the next event time
-			if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
-				nextAlarm = event.runAt;
-			}
-		}
-
-		if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
-	}
-
-	async processEvent(event) {
-		// Your event handling logic here
-	}
+  // Schedule a one-time or recurring event
+  async scheduleEvent(id, runAt, repeatMs = null) {
+    await this.ctx.storage.put(`event:${id}`, { id, runAt, repeatMs });
+    const currentAlarm = await this.ctx.storage.getAlarm();
+    if (!currentAlarm || runAt < currentAlarm) {
+      await this.ctx.storage.setAlarm(runAt);
+    }
+  }
+
+  async alarm() {
+    const now = Date.now();
+    const events = await this.ctx.storage.list({ prefix: "event:" });
+    let nextAlarm = null;
+
+    for (const [key, event] of events) {
+      if (event.runAt <= now) {
+        await this.processEvent(event);
+        if (event.repeatMs) {
+          event.runAt = now + event.repeatMs;
+          await this.ctx.storage.put(key, event);
+        } else {
+          await this.ctx.storage.delete(key);
+        }
+      }
+      // Track the next event time
+      if (event.runAt > now && (!nextAlarm || event.runAt < nextAlarm)) {
+        nextAlarm = event.runAt;
+      }
+    }
+
+    if (nextAlarm) await this.ctx.storage.setAlarm(nextAlarm);
+  }
+
+  async processEvent(event) {
+    // Your event handling logic here
+  }
 }
 ```
 
@@ -82,6 +82,7 @@ export class AgentServer extends DurableObject {
 ### `getAlarm`
 
 - <code>getAlarm()</code>: <Type text="number | null" />
+
   - If there is an alarm set, then return the currently set alarm time as the number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
   - If `getAlarm` is called while an [`alarm`](/durable-objects/api/alarms/#alarm) is already running, it returns `null` unless `setAlarm` has also been called since the alarm handler started running.
@@ -89,6 +90,7 @@ export class AgentServer extends DurableObject {
 ### `setAlarm`
 
 - <code> setAlarm(scheduledTimeMs <Type text="number" />) </code>: <Type text="void" />
+
   - Set the time for the alarm to run. Specify the time as the number of milliseconds elapsed since the UNIX epoch.
   - If you call `setAlarm` when there is already one scheduled, it will override the existing alarm.
 
@@ -101,6 +103,7 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `deleteAlarm`
 
 - `deleteAlarm()`: <Type text='void' />
+
   - Unset the alarm if there is a currently set alarm.
 
   - Calling `deleteAlarm()` inside the `alarm()` handler may prevent retries on a best-effort basis, but is not guaranteed.
@@ -110,9 +113,11 @@ This is due to the fact that, if the Durable Object wakes up after being inactiv
 ### `alarm`
 
 - <code>alarm(alarmInfo <Type text="Object" />)</code>: <Type text="void" />
+
   - Called by the system when a scheduled alarm time is reached.
 
   - The optional parameter `alarmInfo` object has two properties:
+
     - `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
     - `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
 
diff --git a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
index c41b19cc99bc69c..541d4b55aeebebd 100644
--- a/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/legacy-kv-storage-api.mdx
@@ -8,16 +8,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	GlossaryTooltip,
-	TypeScriptExample,
-	Details,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
 
 :::note
 This page documents the storage API for legacy KV-backed Durable Objects.
@@ -92,6 +83,6 @@ KV-backed Durable Objects provide KV API methods which are asynchronous.
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
index 70afb0cebace527..2e6c605ca634618 100644
--- a/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
+++ b/src/content/docs/durable-objects/api/sqlite-storage-api.mdx
@@ -8,16 +8,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	GlossaryTooltip,
-	TypeScriptExample,
-	Details,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { Render, Type, MetaInfo, GlossaryTooltip, TypeScriptExample, Details, Tabs, TabItem } from "~/components";
 
 :::note
 This page documents the storage API for the newer SQLite-backed Durable Objects.
@@ -145,11 +136,7 @@ class MyDurableObject(DurableObject):
 - When writing data, every row update of an index counts as an additional row. However, indexes may be beneficial for read-heavy use cases. Refer to [Index for SQLite Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#indexes-in-sqlite).
 - Writing data to [SQLite virtual tables](https://www.sqlite.org/vtab.html) also counts towards rows written.
 
-<Render
-	file="d1-do-supported-sqlite-extensions"
-	product="d1"
-	params={{ product: "Durable Objects support" }}
-/>
+<Render file="d1-do-supported-sqlite-extensions" product="d1" params={{ product: "Durable Objects support" }}/>
 
 ### `exec`
 
@@ -174,10 +161,7 @@ Always consume the cursor fully before yielding the event loop. Call `.toArray()
 ```ts
 // ✅ Safe: cursor is fully consumed before any await
 const rows = this.ctx.storage.sql.exec("SELECT * FROM users").toArray();
-const result = await fetch("https://example.com", {
-	method: "POST",
-	body: JSON.stringify(rows),
-});
+const result = await fetch("https://example.com", { method: "POST", body: JSON.stringify(rows) });
 ```
 
 ```ts
@@ -367,6 +351,6 @@ ctx.storage.onNextSessionRestoreBookmark(bookmark)
 
 ## Related resources
 
-- [Durable Objects: Easy, Fast, Correct Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
+- [Durable Objects: Easy, Fast, Correct  Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/)
 - [Zero-latency SQLite storage in every Durable Object blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)
 - [WebSockets API](/durable-objects/best-practices/websockets/)
diff --git a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
index 28b40fdda357f9f..cbcc52ad9c8be68 100644
--- a/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
+++ b/src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx
@@ -11,13 +11,10 @@ products:
 import { Render, GlossaryTooltip, WranglerConfig } from "~/components";
 
 <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> are a
-
 powerful compute API that provides a compute with storage building block. Each
 Durable Object has its own private, transactional, and strongly consistent
 storage. Durable Objects
-
 <GlossaryTooltip term="Storage API">Storage API</GlossaryTooltip> provides
-
 access to a Durable Object's attached storage.
 
 A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
diff --git a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
index 163f0a7cc9d2cb5..1f90f81aa40a253 100644
--- a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
+++ b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
@@ -82,7 +82,7 @@ Durable Objects will occasionally shut down and objects are restarted, which wil
 
 When a Durable Object is shut down, the object instance is automatically restarted and new requests are routed to the new instance. In-flight requests are handled as follows:
 
-- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage. If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
+- **HTTP & RPC requests**: In-flight requests are allowed to finish if they do not access a Durable Object's storage.  If a request attempts to access a Durable Object's storage, it will be stopped immediately and return an error to maintain Durable Objects global uniqueness property. When the Worker runtime system is being updated, in-flight requests have up to 30 seconds to complete.
 - **WebSocket connections**: WebSocket requests are terminated automatically during shutdown. This is so that the new instance can take over the connection as soon as possible.
 - **Other invocations (email, cron)**: Other invocations are treated similarly to HTTP requests.
 
diff --git a/src/content/docs/durable-objects/examples/agents.mdx b/src/content/docs/durable-objects/examples/agents.mdx
index 822795f49b71103..0a633feca9fcda1 100644
--- a/src/content/docs/durable-objects/examples/agents.mdx
+++ b/src/content/docs/durable-objects/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - durable-objects
----
+---
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/examples/index.mdx b/src/content/docs/durable-objects/examples/index.mdx
index 3c4df69e31c31d3..a885b12632c278f 100644
--- a/src/content/docs/durable-objects/examples/index.mdx
+++ b/src/content/docs/durable-objects/examples/index.mdx
@@ -14,7 +14,4 @@ import { ResourcesBySelector, GlossaryTooltip } from "~/components";
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Durable Objects.
 
-<ResourcesBySelector
-	types={["example"]}
-	directory="durable-objects/examples/"
-/>
+<ResourcesBySelector types={["example"]} directory="durable-objects/examples/" />
diff --git a/src/content/docs/durable-objects/examples/websocket-server.mdx b/src/content/docs/durable-objects/examples/websocket-server.mdx
index 24b3a890045da9a..6c9fed4be7d126e 100644
--- a/src/content/docs/durable-objects/examples/websocket-server.mdx
+++ b/src/content/docs/durable-objects/examples/websocket-server.mdx
@@ -12,13 +12,7 @@ products:
   - durable-objects
 ---
 
-import {
-	TabItem,
-	Tabs,
-	GlossaryTooltip,
-	WranglerConfig,
-	TypeScriptExample,
-} from "~/components";
+import { TabItem, Tabs, GlossaryTooltip, WranglerConfig, TypeScriptExample } from "~/components";
 
 This example shows how to build a WebSocket server using <GlossaryTooltip term="Durable Object">Durable Objects</GlossaryTooltip> and Workers. The example exposes an endpoint to create a new WebSocket connection. This WebSocket connection echos any message while including the total number of WebSocket connections currently established. For more information, refer to [Use Durable Objects with WebSockets](/durable-objects/best-practices/websockets/).
 
diff --git a/src/content/docs/durable-objects/observability/data-studio.mdx b/src/content/docs/durable-objects/observability/data-studio.mdx
index 39fe7cf43e104b3..847423a93b479a1 100644
--- a/src/content/docs/durable-objects/observability/data-studio.mdx
+++ b/src/content/docs/durable-objects/observability/data-studio.mdx
@@ -40,4 +40,4 @@ You need to have at least the `Workers Platform Admin` [role](/fundamentals/mana
 
 All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/) for your security and compliance needs.
 
-- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
+- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/platform/known-issues.mdx b/src/content/docs/durable-objects/platform/known-issues.mdx
index 8d63e009732811e..a590711f8bcb13e 100644
--- a/src/content/docs/durable-objects/platform/known-issues.mdx
+++ b/src/content/docs/durable-objects/platform/known-issues.mdx
@@ -38,4 +38,4 @@ The Workers editor in the [Cloudflare dashboard](https://dash.cloudflare.com/) a
 
 Currently, when developing locally (using `npx wrangler dev`), Durable Object [alarm methods](/durable-objects/api/alarms) may fail after a hot reload (if you edit the code while the code is running locally).
 
-To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
+To avoid this issue, when using Durable Object alarms, close and restart your `wrangler dev` command after editing your code.
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx
index 26f4a596ac0219e..ef53c2fd80d3d9c 100644
--- a/src/content/docs/durable-objects/platform/limits.mdx
+++ b/src/content/docs/durable-objects/platform/limits.mdx
@@ -77,3 +77,4 @@ For Durable Object classes with [SQLite storage](/durable-objects/api/sqlite-sto
 <Render file="do-faq-limits" product="durable-objects" />
 
 <Render file="wall-time-limits" product="workers" />
+
diff --git a/src/content/docs/durable-objects/reference/data-location.mdx b/src/content/docs/durable-objects/reference/data-location.mdx
index 9465de9ade8d4de..4f4ced530d3685f 100644
--- a/src/content/docs/durable-objects/reference/data-location.mdx
+++ b/src/content/docs/durable-objects/reference/data-location.mdx
@@ -58,9 +58,9 @@ Note that it is also possible to specify a jurisdiction by creating an individua
 
 ### Supported locations
 
-| Parameter | Location                       |
-| --------- | ------------------------------ |
-| eu        | The European Union             |
+| Parameter | Location                     |
+| --------- | ---------------------------- |
+| eu        | The European Union           |
 | fedramp   | FedRAMP-compliant data centers |
 
 ## Provide a location hint
@@ -102,14 +102,10 @@ Hints are a best effort and not a guarantee. Unlike with jurisdictions, Durable
 | afr       | Africa <sup>2</sup>        |
 | me        | Middle East <sup>2</sup>   |
 
-<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the
-future.
+<sup>1</sup> Dynamic relocation of existing Durable Objects is planned for the future.
 
-<sup>2</sup> Durable Objects currently do not spawn in this location. Instead,
-the Durable Object will spawn in a nearby location which does support Durable
-Objects. For example, Durable Objects hinted to South America spawn in Eastern
-North America instead.
+<sup>2</sup> Durable Objects currently do not spawn in this location. Instead, the Durable Object will spawn in a nearby location which does support Durable Objects. For example, Durable Objects hinted to South America spawn in Eastern North America instead.
 
 ## Additional resources
 
-- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
+- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/data-security.mdx b/src/content/docs/durable-objects/reference/data-security.mdx
index d410809c1239ec7..e91b874429d9483 100644
--- a/src/content/docs/durable-objects/reference/data-security.mdx
+++ b/src/content/docs/durable-objects/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of Durable Objects, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/durable-objects/reference/environments.mdx b/src/content/docs/durable-objects/reference/environments.mdx
index ac38518bf59f293..21a1b30c3e2981f 100644
--- a/src/content/docs/durable-objects/reference/environments.mdx
+++ b/src/content/docs/durable-objects/reference/environments.mdx
@@ -43,6 +43,8 @@ Durable Object bindings are not inherited. For example, you can define an enviro
 
 Because Wrangler appends the [environment name](/workers/wrangler/environments/) to the top-level name when publishing, for a Worker named `worker-name` the above example is equivalent to:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -69,6 +71,8 @@ Because Wrangler appends the [environment name](/workers/wrangler/environments/)
 
 If you want an environment-specific binding that accesses the same Objects as the top-level binding, specify the top-level Worker code name explicitly using `script_name`:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -114,10 +118,9 @@ To start remote development:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select an existing Worker.
 3. Select the **Edit code** icon located on the upper-right of the screen.
 
 :::caution
 Remote development is only available for KV-backed Durable Objects. SQLite-backed Durable Objects do not support remote development.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/faq.mdx b/src/content/docs/durable-objects/reference/faq.mdx
index 84262a5b52de7b9..2cff6f2d62e279c 100644
--- a/src/content/docs/durable-objects/reference/faq.mdx
+++ b/src/content/docs/durable-objects/reference/faq.mdx
@@ -12,12 +12,12 @@ import { Render } from "~/components";
 
 ## Pricing
 
-<Render file="do-faq-pricing" product="durable-objects" />
+<Render file="do-faq-pricing" product="durable-objects"/>
 
 ## Limits
 
-<Render file="do-faq-limits" product="durable-objects" />
+<Render file="do-faq-limits" product="durable-objects"/>
 
 ## Metrics and analytics
 
-<Render file="do-faq-metrics-and-analytics" product="durable-objects" />
+<Render file="do-faq-metrics-and-analytics" product="durable-objects"/>
\ No newline at end of file
diff --git a/src/content/docs/durable-objects/reference/glossary.mdx b/src/content/docs/durable-objects/reference/glossary.mdx
index 1e9b3d062d8832e..b95a0d5b0e6b08d 100644
--- a/src/content/docs/durable-objects/reference/glossary.mdx
+++ b/src/content/docs/durable-objects/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - durable-objects
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Durable Objects documentation.
 
diff --git a/src/content/docs/durable-objects/reference/in-memory-state.mdx b/src/content/docs/durable-objects/reference/in-memory-state.mdx
index 7ef26232dd22b2b..772169b848b90bd 100644
--- a/src/content/docs/durable-objects/reference/in-memory-state.mdx
+++ b/src/content/docs/durable-objects/reference/in-memory-state.mdx
@@ -20,21 +20,21 @@ A common pattern is to initialize a Durable Object from [persistent storage](/du
 import { DurableObject } from "cloudflare:workers";
 
 export class Counter extends DurableObject {
-	constructor(ctx, env) {
-		super(ctx, env);
-		// `blockConcurrencyWhile()` ensures no requests are delivered until
-		// initialization completes.
-		this.ctx.blockConcurrencyWhile(async () => {
-			let stored = await this.ctx.storage.get("value");
-			// After initialization, future reads do not need to access storage.
-			this.value = stored || 0;
-		});
-	}
-
-	// Handle HTTP requests from clients.
-	async fetch(request) {
-		// use this.value rather than storage
-	}
+  constructor(ctx, env) {
+    super(ctx, env);
+    // `blockConcurrencyWhile()` ensures no requests are delivered until
+    // initialization completes.
+    this.ctx.blockConcurrencyWhile(async () => {
+      let stored = await this.ctx.storage.get("value");
+      // After initialization, future reads do not need to access storage.
+      this.value = stored || 0;
+    });
+  }
+
+  // Handle HTTP requests from clients.
+  async fetch(request) {
+    // use this.value rather than storage
+  }
 }
 ```
 
diff --git a/src/content/docs/durable-objects/video-tutorials.mdx b/src/content/docs/durable-objects/video-tutorials.mdx
index 4390949faf52bc7..4af3068247492a4 100644
--- a/src/content/docs/durable-objects/video-tutorials.mdx
+++ b/src/content/docs/durable-objects/video-tutorials.mdx
@@ -11,9 +11,11 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Introduction to Durable Objects"
-		description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
-		href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
-	/>
+    <LinkCard
+        title="Introduction to Durable Objects"
+        description="Dive into a hands-on Durable Objects project and learn how to build stateful apps using serverless architecture"
+        href="/learning-paths/durable-objects-course/series/introduction-to-series-1/"
+    />
 </CardGrid>
+
+
diff --git a/src/content/docs/dynamic-workers/usage/bindings.mdx b/src/content/docs/dynamic-workers/usage/bindings.mdx
index 2970ac1c09b9962..5fed51bc8b0efe7 100644
--- a/src/content/docs/dynamic-workers/usage/bindings.mdx
+++ b/src/content/docs/dynamic-workers/usage/bindings.mdx
@@ -10,7 +10,7 @@ products:
 
 import { WranglerConfig } from "~/components";
 
-Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use.
+Bindings let you control what a Dynamic Worker can access. When you create a Dynamic Worker, you decide exactly what resources and operations it can use. 
 
 This allows you to:
 
@@ -21,8 +21,7 @@ This allows you to:
 ## Custom Bindings with Dynamic Workers
 
 With custom bindings, you:
-
-- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer.
+- **Define the binding implementation in your loader Worker**: You create a class with methods. Because this runs in your loader Worker, that's where you can add authentication, logging, scope access per customer. 
 - **Pass it to the Dynamic Worker as a binding**: It just calls methods like `this.env.CHAT_ROOM.post("Hello!")` without knowing anything about the implementation behind it.
 
 ### How it works
@@ -30,65 +29,54 @@ With custom bindings, you:
 #### Step 1: Define the binding
 
 To create a custom binding, your loader Worker needs to implement a [`WorkerEntrypoint` class](/workers/runtime-apis/bindings/service-bindings/rpc#the-workerentrypoint-class) and export it. The methods you define on this class are the methods the Dynamic Worker will be able to call.
-
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint {
-	async post(text: string): Promise<void> {
-		// Your implementation here
-	}
+  async post(text: string): Promise<void> {
+    // Your implementation here
+  }
 }
 ```
-
 #### Step 2: Pass it to the Dynamic Worker
-
-Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`.
+Your loader Worker will then create an instance of the exported class, called a stub, and pass it into the Dynamic Worker's `env`. 
 
 ```ts
 let chatRoom = ctx.exports.ChatRoom({ props: { roomName: "#bot-chat" } });
 
 let worker = env.LOADER.load({
-	env: { CHAT_ROOM: chatRoom },
-	// ...
+  env: { CHAT_ROOM: chatRoom },
+  // ...
 });
 ```
 
-From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call:
-
+From the Dynamic Worker's perspective, `CHAT_ROOM` just looks like a regular binding with methods it can call: 
 ```ts
 // Inside the Dynamic Worker
 await this.env.CHAT_ROOM.post("Hello!");
 ```
-
 #### Step 3: Customize per user with props
-
-One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user.
+One class can serve many different Dynamic Workers. Instead of defining a separate class for each user, you pass in `props` when creating the stub, which contains information specific to that user. 
 
 ```ts
 // Same class, different props per user
-let aliceRoom = ctx.exports.ChatRoom({
-	props: { roomName: "#alice", apiKey: ALICE_KEY },
-});
-let bobRoom = ctx.exports.ChatRoom({
-	props: { roomName: "#bob", apiKey: BOB_KEY },
-});
+let aliceRoom = ctx.exports.ChatRoom({ props: { roomName: "#alice", apiKey: ALICE_KEY } });
+let bobRoom   = ctx.exports.ChatRoom({ props: { roomName: "#bob", apiKey: BOB_KEY } });
 ```
 
 When the Dynamic Worker calls a method on the binding, it's actually making a call back to your loader Worker, that's where the method runs. Inside that method, you can read the `props` via [`this.ctx.props`](/workers/runtime-apis/context#props). Only the loader Worker has access to the props, the Dynamic Worker never sees them.
 
 ```ts
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-	async post(text: string): Promise<void> {
-		// Props are set when the stub is created — the Dynamic Worker never sees them
-		let roomName = this.ctx.props.roomName;
-		await postToChat(roomName, text);
-	}
+  async post(text: string): Promise<void> {
+    // Props are set when the stub is created — the Dynamic Worker never sees them
+    let roomName = this.ctx.props.roomName;
+    await postToChat(roomName, text);
+  }
 }
 ```
 
 ### Example: Chat room agent
-
 Here's a complete example putting it all together. Say you're building a platform where AI agents can post to chat rooms. Each agent should only be able to post to its assigned room and it should never see the API key used to authenticate.
 
 You define a `ChatRoom` class in your parent Worker. This class has a `post` method, the only method the Dynamic Worker can call on this binding. Inside this class, you control which room the message goes to, which API key is used, and what name is attached to the message.
@@ -97,46 +85,44 @@ You define a `ChatRoom` class in your parent Worker. This class has a `post` met
 import { WorkerEntrypoint } from "cloudflare:workers";
 
 export class ChatRoom extends WorkerEntrypoint<Cloudflare.Env, ChatRoomProps> {
-	async post(text: string): Promise<void> {
-		let { apiKey, botName, roomName } = this.ctx.props;
+  async post(text: string): Promise<void> {
+    let { apiKey, botName, roomName } = this.ctx.props;
 
-		// Prefix the message with the bot's name.
-		text = `[${botName}]: ${text}`;
+    // Prefix the message with the bot's name.
+    text = `[${botName}]: ${text}`;
 
-		// Send it to the chat service.
-		await postToChat(apiKey, roomName, text);
-	}
+    // Send it to the chat service.
+    await postToChat(apiKey, roomName, text);
+  }
 }
 
 type ChatRoomProps = {
-	apiKey: string;
-	roomName: string;
-	botName: string;
+  apiKey: string;
+  roomName: string;
+  botName: string;
 };
 ```
-
 You export one `ChatRoom` class, but each stub you create can have different `props` — a different room name, a different API key, a different bot name. The `props` are set when you create the stub, and the Dynamic Worker never sees them.
 
 Now pass it to a Dynamic Worker:
-
 ```ts
 // Create a stub scoped to a specific room.
 let chatRoom = ctx.exports.ChatRoom({
-	props: {
-		apiKey,
-		roomName: "#bot-chat",
-		botName: "Robo",
-	},
+  props: {
+    apiKey,
+    roomName: "#bot-chat",
+    botName: "Robo",
+  },
 });
 
 let worker = env.LOADER.load({
-	env: {
-		CHAT_ROOM: chatRoom,
-	},
-	compatibilityDate: "$today",
-	mainModule: "index.js",
-	modules: {
-		"index.js": `
+  env: {
+    CHAT_ROOM: chatRoom,
+  },
+  compatibilityDate: "$today",
+  mainModule: "index.js",
+  modules: {
+    "index.js": `
       export class Agent extends WorkerEntrypoint {
         async run() {
           // This is all the Dynamic Worker sees.
@@ -144,14 +130,13 @@ let worker = env.LOADER.load({
         }
       }
     `,
-	},
-	globalOutbound: null,
+  },
+  globalOutbound: null,
 });
 
 return worker.getEntrypoint("Agent").run();
 ```
-
-The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages.
+The agent just calls `this.env.CHAT_ROOM.post("Hello!")`. It has no way to post to a different room, see or use the API key, or change the bot name attached to its messages. 
 
 ### Tip: Tell your agent about the types
 
@@ -161,52 +146,45 @@ Make sure your `WorkerEntrypoint` class extends the TypeScript type so the decla
 
 ## Passing normal Workers bindings
 
-To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose.
+To pass resources like a [KV](/kv/) namespace or [R2](/r2/) bucket to a Dynamic Worker, you need to bind the resource to your loader Worker and create a custom binding that wraps it. You can scope access per customer by prefixing keys and defining only the methods you want to expose. 
 
 ### Example: Scoping a KV namespace per customer
 
 First, bind the KV namespace to your loader Worker. Then in your loader Worker, export a class that uses the KV binding and defines the methods Dynamic Workers can call:
-
 ```ts
 import { WorkerEntrypoint } from "cloudflare:workers";
 
-export class MyStorage extends WorkerEntrypoint<
-	Cloudflare.Env,
-	MyStorageProps
-> {
-	// Export this class from your loader Worker
-	// The Dynamic Worker will be able to call get() and put()
-	async get(key: string): Promise<string | null> {
-		// Prefix the key so this customer can only access their own data
-		return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
-	}
-
-	async put(key: string, value: string): Promise<void> {
-		await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
-	}
+export class MyStorage extends WorkerEntrypoint<Cloudflare.Env, MyStorageProps> {
+  // Export this class from your loader Worker
+  // The Dynamic Worker will be able to call get() and put()
+  async get(key: string): Promise<string | null> {
+    // Prefix the key so this customer can only access their own data
+    return this.env.MY_KV.get(`${this.ctx.props.prefix}:${key}`);
+  }
+
+  async put(key: string, value: string): Promise<void> {
+    await this.env.MY_KV.put(`${this.ctx.props.prefix}:${key}`, value);
+  }
 }
 
 type MyStorageProps = {
-	prefix: string;
+  prefix: string;
 };
 ```
-
 Then pass it to the Dynamic Worker with a customer-specific prefix:
-
 ```ts
 // Create a stub scoped to this customer's prefix
 let storage = ctx.exports.MyStorage({
-	props: { prefix: `customer-${customerId}` },
+  props: { prefix: `customer-${customerId}` },
 });
 
 let worker = env.LOADER.load({
-	env: { STORAGE: storage },
-	// ...
+  env: { STORAGE: storage },
+  // ...
 });
 ```
 
 The Dynamic Worker just uses it like any other binding:
-
 ```ts
 // Inside the Dynamic Worker, it just sees STORAGE with get and put
 let value = await this.env.STORAGE.get("settings");
@@ -219,7 +197,7 @@ For persistent storage that lives with each Dynamic Worker, see [Durable Object
 
 ## Capability-based Sandboxing
 
-Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it. If it hasn't received a stub for something, it can't access it.
+Custom bindings follow a capability-based security model — a Dynamic Worker can only access what you explicitly give it.  If it hasn't received a stub for something, it can't access it. 
 
 This is powered by Workers RPC, also known as [Cap'n Web](https://github.com/cloudflare/capnweb), an RPC system designed to pass object references across security boundaries. When a Dynamic Worker receives a stub, it can call that object's methods and each call is an RPC back to the original object in your loader Worker. Stubs have no global identifier and cannot be forged, the only way to obtain one is to receive it.
 
diff --git a/src/content/docs/email-routing/email-workers/local-development.mdx b/src/content/docs/email-routing/email-workers/local-development.mdx
index ab7767665ecebf0..7764c919d997f0d 100644
--- a/src/content/docs/email-routing/email-workers/local-development.mdx
+++ b/src/content/docs/email-routing/email-workers/local-development.mdx
@@ -41,7 +41,7 @@ You can now test receiving, replying, and sending emails in your local environme
 Consider this example Email Worker script that uses the open source [`postal-mime`](https://www.npmjs.com/package/postal-mime) email parser:
 
 ```ts
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
 	async email(message, env, ctx) {
@@ -79,31 +79,31 @@ This is what you get in the console:
 
 ```json
 {
-	"headers": [
-		{
-			"key": "received",
-			"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
-		},
-		{ "key": "from", "value": "\"John\" <sender@example.com>" },
-		{ "key": "reply-to", "value": "sender@example.com" },
-		{ "key": "to", "value": "recipient@example.com" },
-		{ "key": "subject", "value": "Testing Email Workers Local Dev" },
-		{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
-		{ "key": "x-mailer", "value": "Curl" },
-		{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
-		{
-			"key": "message-id",
-			"value": "<6114391943504294873000@ZSH-GHOSTTY>"
-		}
-	],
-	"from": { "address": "sender@example.com", "name": "John" },
-	"to": [{ "address": "recipient@example.com", "name": "" }],
-	"replyTo": [{ "address": "sender@example.com", "name": "" }],
-	"subject": "Testing Email Workers Local Dev",
-	"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
-	"date": "2024-08-27T15:49:44.000Z",
-	"html": "Hi there\n",
-	"attachments": []
+  headers: [
+    {
+      key: 'received',
+      value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
+    },
+    { key: 'from', value: '"John" <sender@example.com>' },
+    { key: 'reply-to', value: 'sender@example.com' },
+    { key: 'to', value: 'recipient@example.com' },
+    { key: 'subject', value: 'Testing Email Workers Local Dev' },
+    { key: 'content-type', value: 'text/html; charset="windows-1252"' },
+    { key: 'x-mailer', value: 'Curl' },
+    { key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
+    {
+      key: 'message-id',
+      value: '<6114391943504294873000@ZSH-GHOSTTY>'
+    }
+  ],
+  from: { address: 'sender@example.com', name: 'John' },
+  to: [ { address: 'recipient@example.com', name: '' } ],
+  replyTo: [ { address: 'sender@example.com', name: '' } ],
+  subject: 'Testing Email Workers Local Dev',
+  messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
+  date: '2024-08-27T15:49:44.000Z',
+  html: 'Hi there\n',
+  attachments: []
 }
 ```
 
@@ -113,27 +113,23 @@ Wrangler can also simulate sending emails locally. Consider this example Email W
 
 ```ts
 import { EmailMessage } from "cloudflare:email";
-import { createMimeMessage } from "mimetext";
+import { createMimeMessage } from 'mimetext';
 
 export default {
 	async fetch(request, env, ctx) {
 		const msg = createMimeMessage();
-		msg.setSender({ name: "Sending email test", addr: "sender@example.com" });
-		msg.setRecipient("recipient@example.com");
-		msg.setSubject("An email generated in a worker");
+		msg.setSender({ name: 'Sending email test', addr: 'sender@example.com' });
+		msg.setRecipient('recipient@example.com');
+		msg.setSubject('An email generated in a worker');
 		msg.addMessage({
-			contentType: "text/plain",
+			contentType: 'text/plain',
 			data: `Congratulations, you just sent an email from a worker.`,
 		});
 
-		var message = new EmailMessage(
-			"sender@example.com",
-			"recipient@example.com",
-			msg.asRaw(),
-		);
+		var message = new EmailMessage('sender@example.com', 'recipient@example.com', msg.asRaw());
 		await env.EMAIL.send(message);
 		return Response.json({ ok: true });
-	},
+	}
 };
 ```
 
@@ -167,9 +163,9 @@ Congratulations, you just sent an email from a worker.
 Likewise, [`EmailMessage`](/email-routing/email-workers/runtime-api/#emailmessage-definition)'s `forward()` and `reply()` methods are also simulated locally. Consider this Worker that receives an email, parses it, replies to the sender, and forwards the original message to one your verified recipient addresses:
 
 ```ts
-import * as PostalMime from "postal-mime";
-import { createMimeMessage } from "mimetext";
-import { EmailMessage } from "cloudflare:email";
+import * as PostalMime from 'postal-mime';
+import { createMimeMessage } from 'mimetext';
+import { EmailMessage } from 'cloudflare:email';
 
 export default {
 	async email(message, env: any, ctx: any) {
@@ -183,23 +179,16 @@ export default {
 
 		// creates reply message
 		const msg = createMimeMessage();
-		msg.setSender({
-			name: "Thank you for your contact",
-			addr: "sender@example.com",
-		});
+		msg.setSender({ name: 'Thank you for your contact', addr: 'sender@example.com' });
 		msg.setRecipient(message.from);
-		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-		msg.setSubject("An email generated in a worker");
+		msg.setHeader('In-Reply-To', message.headers.get('Message-ID'));
+		msg.setSubject('An email generated in a worker');
 		msg.addMessage({
-			contentType: "text/plain",
+			contentType: 'text/plain',
 			data: `This is an automated reply. We received you email with the subject "${email.subject}", and will handle it as soon as possible.`,
 		});
 
-		const replyMessage = new EmailMessage(
-			"sender@example.com",
-			message.from,
-			msg.asRaw(),
-		);
+		const replyMessage = new EmailMessage('sender@example.com', message.from, msg.asRaw());
 
 		await message.reply(replyMessage);
 		await message.forward("recipient@example.com");
@@ -216,4 +205,4 @@ Run `npx wrangler dev` and use curl to `POST` the same message from the [Receive
   /var/folders/33/pn86qymd0w50htvsjp93rys40000gn/T/miniflare-381a79d7efa4e991607b30a079f6b17d/files/email/a1db7ebb-ccb4-45ef-b315-df49c6d820c0.eml
 [wrangler:inf] Email handler forwarded message with
   rcptTo: recipient@example.com
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
index 9b1bca4d651c33d..abe2ab9e1917b97 100644
--- a/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
+++ b/src/content/docs/email-routing/email-workers/reply-email-workers.mdx
@@ -17,39 +17,37 @@ import { EmailMessage } from "cloudflare:email";
 import { createMimeMessage } from "mimetext";
 
 export default {
-	async email(message, env, ctx) {
-		const ticket = createTicket(message);
-
-		const msg = createMimeMessage();
-		msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
-		msg.setSender({
-			name: "Thank you for your contact",
-			addr: "<SENDER>@example.com",
-		});
-		msg.setRecipient(message.from);
-		msg.setSubject("Email Routing Auto-reply");
-		msg.addMessage({
-			contentType: "text/plain",
-			data: `We got your message, your ticket number is ${ticket.id}`,
-		});
-
-		const replyMessage = new EmailMessage(
-			"<SENDER>@example.com",
-			message.from,
-			msg.asRaw(),
-		);
-
-		await message.reply(replyMessage);
-	},
-};
+  async email(message, env, ctx) {
+
+    const ticket = createTicket(message);
+
+    const msg = createMimeMessage();
+    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
+    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
+    msg.setRecipient(message.from);
+    msg.setSubject("Email Routing Auto-reply");
+    msg.addMessage({
+      contentType: 'text/plain',
+      data: `We got your message, your ticket number is ${ ticket.id }`
+    });
+
+    const replyMessage = new EmailMessage(
+      "<SENDER>@example.com",
+      message.from,
+      msg.asRaw()
+    );
+
+    await message.reply(replyMessage);
+  }
+}
 ```
 
 To mitigate security risks and abuse, replying to incoming emails has a few requirements and limits:
 
-- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
-- The email can only be replied to once in the same `EmailMessage` event.
-- The recipient in the reply must match the incoming sender.
-- The outgoing sender domain must match the same domain that received the email.
-- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
+* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
+* The email can only be replied to once in the same `EmailMessage` event.
+* The recipient in the reply must match the incoming sender.
+* The outgoing sender domain must match the same domain that received the email.
+* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
 
-If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
+If these and other internal conditions are not met, `reply()` will fail with an exception. Otherwise, you can freely compose your reply message, send it back to the original sender, and receive subsequent replies multiple times.
\ No newline at end of file
diff --git a/src/content/docs/email-routing/get-started/audit-logs.mdx b/src/content/docs/email-routing/get-started/audit-logs.mdx
index ecd9b2792350842..ea56a04e458c21b 100644
--- a/src/content/docs/email-routing/get-started/audit-logs.mdx
+++ b/src/content/docs/email-routing/get-started/audit-logs.mdx
@@ -13,9 +13,9 @@ products:
 
 Audit logs for Email Routing are available in the [Cloudflare dashboard](https://dash.cloudflare.com/?account=audit-log). The following changes to Email Routing will be displayed:
 
-- Add/edit Rule
-- Add address
-- Address change status
-- Enable/disable/unlock zone
+* Add/edit Rule
+* Add address
+* Address change status
+* Enable/disable/unlock zone
 
 Refer to [Review audit logs](/fundamentals/account/account-security/review-audit-logs/) for more information.
diff --git a/src/content/docs/email-routing/get-started/index.mdx b/src/content/docs/email-routing/get-started/index.mdx
index 4f3a50117f3555f..79651ecf8525c75 100644
--- a/src/content/docs/email-routing/get-started/index.mdx
+++ b/src/content/docs/email-routing/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 To enable Email Routing, start by creating a custom email address linked to a destination address or Email Worker. This forms an **email rule**. You can enable or disable rules from the Cloudflare dashboard. Refer to [Enable Email Routing](/email-routing/get-started/enable-email-routing) for more details.
 
diff --git a/src/content/docs/email-routing/graphql-example.mdx b/src/content/docs/email-routing/graphql-example.mdx
index 01e88cb7c926f54..1026c732af09d68 100644
--- a/src/content/docs/email-routing/graphql-example.mdx
+++ b/src/content/docs/email-routing/graphql-example.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 10
 products:
   - email-routing
----
+---
\ No newline at end of file
diff --git a/src/content/docs/email-routing/limits.mdx b/src/content/docs/email-routing/limits.mdx
index 7ba2a9378e24cab..aa0c9137f7e93b4 100644
--- a/src/content/docs/email-routing/limits.mdx
+++ b/src/content/docs/email-routing/limits.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Email Workers size limits
 
diff --git a/src/content/docs/email-routing/postmaster.mdx b/src/content/docs/email-routing/postmaster.mdx
index 5024a5fca40679d..f2e0afee4304d44 100644
--- a/src/content/docs/email-routing/postmaster.mdx
+++ b/src/content/docs/email-routing/postmaster.mdx
@@ -223,6 +223,7 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
+
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
@@ -235,4 +236,4 @@ Email Routing does not support sending or replying from your Cloudflare domain.
 
 ### "`.`" is treated as a normal character for custom addresses
 
-The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
+The `.` character, which performs special actions in email providers like Gmail, is treated as a normal character on custom addresses.
\ No newline at end of file
diff --git a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
index d5a45e53b881844..5b19f941bc3973c 100644
--- a/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
+++ b/src/content/docs/email-routing/setup/email-routing-dns-records.mdx
@@ -17,8 +17,8 @@ You can check the status of your DNS records in the **Settings** section of Emai
 
 Check the status of your account's DNS records in the **Email DNS records** card:
 
-- **Email DNS records configured** - DNS records are properly configured.
-- **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
+* **Email DNS records configured** - DNS records are properly configured.
+* **Email DNS records misconfigured** - There is a problem with your accounts DNS records. Select **Enable Email Routing** to [start troubleshooting problems](/email-routing/troubleshooting/).
 
 ### Start disabling
 
@@ -36,8 +36,8 @@ Select **View DNS records** for a list of the required `MX` and sender policy fr
 
 If you are having trouble with your account's DNS records, refer to the [Troubleshooting](/email-routing/troubleshooting/) section.
 
-## \_dc-mx DNS responses
+## _dc-mx DNS responses
 
 If you see a DNS response with a `_dc-mx` prefix (for example, `_dc-mx.a1b2c3d4e5f6.example.com`), Cloudflare inserted it automatically. This response appears when your `MX` record points to a hostname that is [proxied](/dns/proxy-status/) through Cloudflare. The `_dc-mx` target itself resolves directly to your origin IP address so that mail traffic bypasses the proxy and reaches your mail server.
 
-For more information, refer to [\_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
+For more information, refer to [_dc-mx and dc-##### subdomains](/dns/manage-dns-records/troubleshooting/unexpected-dns-records/#dc--and-_dc-mx-subdomains).
diff --git a/src/content/docs/email-routing/setup/index.mdx b/src/content/docs/email-routing/setup/index.mdx
index a985b31913d2240..9e8e6168e7d9d3d 100644
--- a/src/content/docs/email-routing/setup/index.mdx
+++ b/src/content/docs/email-routing/setup/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-routing/troubleshooting/index.mdx b/src/content/docs/email-routing/troubleshooting/index.mdx
index 320a435287a9f78..6049ae5a1dbf1b6 100644
--- a/src/content/docs/email-routing/troubleshooting/index.mdx
+++ b/src/content/docs/email-routing/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-routing
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Email Routing warns you when your DNS records are not properly configured. In Email Routing's **Overview** page, you will see a message explaining what type of problem your account's DNS records have.
 
diff --git a/src/content/docs/email-security/account-setup/index.mdx b/src/content/docs/email-security/account-setup/index.mdx
index 115b19e40df6b41..58b9191302f4924 100644
--- a/src/content/docs/email-security/account-setup/index.mdx
+++ b/src/content/docs/email-security/account-setup/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
index 74464f58cb9a20e..1a386467767d7a5 100644
--- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
+++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/create-project-gcp.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 1. Log in to the [Google Cloud Console](https://console.cloud.google.com/welcome/new). From the dashboard, select **CREATE OR SELECT PROJECT**.
 2. Provide the details for the new project, and select **CREATE** to start your new project.
@@ -19,4 +19,4 @@ import { Render } from "~/components";
 
 ## Next steps
 
-Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
+Now that you have created a project on Google Cloud Console, you need to [create a service account](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/) on Google Cloud Console.
\ No newline at end of file
diff --git a/src/content/docs/email-security/deployment/inline/reference/index.mdx b/src/content/docs/email-security/deployment/inline/reference/index.mdx
index d967052afafa9a8..3acddcd2503e68e 100644
--- a/src/content/docs/email-security/deployment/inline/reference/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/deployment/inline/setup/index.mdx b/src/content/docs/email-security/deployment/inline/setup/index.mdx
index 7944841692ccc8f..9d77a311b1def17 100644
--- a/src/content/docs/email-security/deployment/inline/setup/index.mdx
+++ b/src/content/docs/email-security/deployment/inline/setup/index.mdx
@@ -11,7 +11,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For help getting started with an [inline setup](/email-security/deployment/inline/), refer to the following guides:
 
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
index 1d64d9275d3103e..b36be50d7f74394 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/alert-webhooks.mdx
@@ -15,11 +15,11 @@ Alert Webhooks allow you to connect external services to Email security, includi
 - Slack
 - Email addresses
 - <GlossaryTooltip
-    	term="SIEM"
-    	link="/email-security/reporting/siem-integration/"
-    >
-    	SIEM
-    </GlossaryTooltip>
+  	term="SIEM"
+  	link="/email-security/reporting/siem-integration/"
+  >
+  	SIEM
+  </GlossaryTooltip>
 - Microsoft Teams
 
 ## Create an alert webhook
diff --git a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
index bcf17ca94340495..064f16bbe246605 100644
--- a/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
+++ b/src/content/docs/email-security/email-configuration/domains-and-routing/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/email-policies/index.mdx b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
index f02050d417bebf4..970060f35bca548 100644
--- a/src/content/docs/email-security/email-configuration/email-policies/index.mdx
+++ b/src/content/docs/email-security/email-configuration/email-policies/index.mdx
@@ -8,7 +8,7 @@ products:
   - email-security
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 <Render file="contact-support" product="email-security" />
 
diff --git a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
index 57eafdbc713f614..cf276be7c979d2c 100644
--- a/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
+++ b/src/content/docs/email-security/email-configuration/enhanced-detections/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/email-configuration/lists/index.mdx b/src/content/docs/email-security/email-configuration/lists/index.mdx
index 309b6ba3c5e4a88..fb788ae5a7833ef 100644
--- a/src/content/docs/email-security/email-configuration/lists/index.mdx
+++ b/src/content/docs/email-security/email-configuration/lists/index.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx
index 1f577dece7e60c7..0f8848970f558ed 100644
--- a/src/content/docs/email-security/migrate-to-email-security.mdx
+++ b/src/content/docs/email-security/migrate-to-email-security.mdx
@@ -45,15 +45,15 @@ To invite users in Zero Trust Email security:
 
 Once you have added new account members, you will have to assign each member an [Email security role](/cloudflare-one/roles-permissions/#email-security-roles).
 
-| Area 1              | Email security                                                            | Description                                                                                                                                                                                                                  |
-| ------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Area 1              | Email security                                                            | Description                                                                                                                                                                                             |
+| ------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | N/A                 | Cloudflare Zero Trust                                                     | Can edit Cloudflare [Zero Trust](/cloudflare-one/). Has administrator access to all Zero Trust products including Access, Gateway, the Cloudflare One Client, Tunnel, Browser Isolation, CASB, DLP, DEX, and Email security. |
-| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                                      |
-| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                                      |
-| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                                               |
-| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                                             |
-| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                                                    |
-| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                                                   |
+| Super Admin         | Email security Analyst + Email security Configuration Admin = Super Admin | Has full access to all admin features in Email security                                                                                                                                                 |
+| Configuration Admin | Email security Configuration Admin                                        | Has administrator access. Cannot take actions on emails, or read emails                                                                                                                                 |
+| SOC Analyst         | Email security Analyst                                                    | Has analyst access. Can take action on emails and read emails.                                                                                                                                          |
+| Viewer              | Email security Reporting                                                  | Can read metrics                                                                                                                                                                                        |
+| N/A                 | Cloudflare Zero Trust PII                                                 | Can read PII in Zero Trust (this includes Email security)                                                                                                                                               |
+| N/A                 | Email security Policy Admin                                               | Can read all settings, but only write allow policies, trusted domains, and blocked senders                                                                                                              |
 
 ## Create webhooks
 
@@ -142,12 +142,12 @@ This table displays the difference in terminology used when creating policies:
 
 This table displays the difference in terminology used when finding emails whose disposition is incorrect:
 
-| Area 1                                                                                                                                                                                   | Email security                                                                                       |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| Area 1                                                                                                                                                                                   | Email security                                                                           |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
 | Report [false negative](/email-security/email-configuration/phish-submissions/#false-negatives)/[false positive](/email-security/email-configuration/phish-submissions/#false-positives) | [Submit messages for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) |
-| N/A                                                                                                                                                                                      | Escalate user submissions                                                                            |
-| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)                     |
-| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)                     |
+| N/A                                                                                                                                                                                      | Escalate user submissions                                                                |
+| [Team submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [Team submissions](/cloudflare-one/email-security/submissions/team-submissions/)         |
+| [User submission](/email-security/email-configuration/phish-submissions/#how-to-submit-phish)                                                                                            | [User submissions](/cloudflare-one/email-security/submissions/user-submissions/)         |
 
 ## Business Email Compromise
 
diff --git a/src/content/docs/email-security/reference/index.mdx b/src/content/docs/email-security/reference/index.mdx
index c38a16a0de9f080..9f7509bd9cf9280 100644
--- a/src/content/docs/email-security/reference/index.mdx
+++ b/src/content/docs/email-security/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - email-security
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/email-service/api/index.mdx b/src/content/docs/email-service/api/index.mdx
index d03187150053624..44e78505396a107 100644
--- a/src/content/docs/email-service/api/index.mdx
+++ b/src/content/docs/email-service/api/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/api/route-emails/email-handler.mdx b/src/content/docs/email-service/api/route-emails/email-handler.mdx
index 4de6233a27266e7..a5e96e60aafc443 100644
--- a/src/content/docs/email-service/api/route-emails/email-handler.mdx
+++ b/src/content/docs/email-service/api/route-emails/email-handler.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 1
 products:
   - email-service
-  - workers
+  - workers 
 ---
 
 import { Tabs, TabItem } from "~/components";
diff --git a/src/content/docs/email-service/api/route-emails/index.mdx b/src/content/docs/email-service/api/route-emails/index.mdx
index 1d26611cdc87d0d..5d7f8f3f10cb0db 100644
--- a/src/content/docs/email-service/api/route-emails/index.mdx
+++ b/src/content/docs/email-service/api/route-emails/index.mdx
@@ -14,4 +14,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/api/send-emails/rest-api.mdx b/src/content/docs/email-service/api/send-emails/rest-api.mdx
index 91cbd43aa37da94..7435885f3824271 100644
--- a/src/content/docs/email-service/api/send-emails/rest-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/rest-api.mdx
@@ -135,14 +135,14 @@ A successful response returns the delivery status for each recipient:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"delivered": ["recipient@example.com"],
-		"permanent_bounces": [],
-		"queued": []
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "delivered": ["recipient@example.com"],
+    "permanent_bounces": [],
+    "queued": []
+  }
 }
 ```
 
@@ -156,29 +156,29 @@ The REST API returns standard Cloudflare API error responses. A failed request r
 
 ```json
 {
-	"success": false,
-	"errors": [
-		{
-			"code": 10001,
-			"message": "email.sending.error.invalid_request_schema"
-		}
-	],
-	"messages": [],
-	"result": null
+  "success": false,
+  "errors": [
+    {
+      "code": 10001,
+      "message": "email.sending.error.invalid_request_schema"
+    }
+  ],
+  "messages": [],
+  "result": null
 }
 ```
 
 Common REST API error codes:
 
-| HTTP Status | Code  | Message                                       | Description                            |
-| ----------- | ----- | --------------------------------------------- | -------------------------------------- |
-| 400         | 10001 | `email.sending.error.invalid_request_schema`  | Invalid request format                 |
-| 400         | 10200 | `email.sending.error.email.invalid`           | Invalid email content                  |
-| 400         | 10201 | `email.sending.error.email.no_content_length` | Missing content length                 |
-| 400         | 10202 | `email.sending.error.email.too_big`           | Email exceeds size limit               |
-| 403         | 10203 | `email.sending.error.email.sending_disabled`  | Sending disabled for this zone/account |
-| 429         | 10004 | `email.sending.error.throttled`               | Rate limit exceeded                    |
-| 500         | 10002 | `email.sending.error.internal_server`         | Internal server error                  |
+| HTTP Status | Code | Message | Description |
+| ----------- | ---- | ------- | ----------- |
+| 400 | 10001 | `email.sending.error.invalid_request_schema` | Invalid request format |
+| 400 | 10200 | `email.sending.error.email.invalid` | Invalid email content |
+| 400 | 10201 | `email.sending.error.email.no_content_length` | Missing content length |
+| 400 | 10202 | `email.sending.error.email.too_big` | Email exceeds size limit |
+| 403 | 10203 | `email.sending.error.email.sending_disabled` | Sending disabled for this zone/account |
+| 429 | 10004 | `email.sending.error.throttled` | Rate limit exceeded |
+| 500 | 10002 | `email.sending.error.internal_server` | Internal server error |
 
 :::note[Workers binding vs REST API errors]
 The REST API returns standard Cloudflare API numeric error codes, while the [Workers binding](/email-service/api/send-emails/workers-api/) throws errors with string codes (for example, `E_SENDER_NOT_VERIFIED`). Refer to the [Workers API error codes table](/email-service/api/send-emails/workers-api/#error-codes) for the string error codes.
diff --git a/src/content/docs/email-service/api/send-emails/workers-api.mdx b/src/content/docs/email-service/api/send-emails/workers-api.mdx
index ad7de8aa161ea02..83244ea4c0e7dbb 100644
--- a/src/content/docs/email-service/api/send-emails/workers-api.mdx
+++ b/src/content/docs/email-service/api/send-emails/workers-api.mdx
@@ -235,27 +235,27 @@ export default {
 
 The following error codes may be returned when sending emails:
 
-| Error Code                      | Description                             | Common Causes                                                                              |
-| ------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------ |
-| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data                              |
-| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                                                  |
-| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                                                        |
-| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                                                  |
-| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`                                   |
-| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam                                  |
-| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                                                      |
-| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                                                     |
-| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection                                          |
-| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                                                 |
-| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                                                |
-| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                                                      |
+| Error Code                      | Description                             | Common Causes                                                 |
+| ------------------------------- | --------------------------------------- | ------------------------------------------------------------- |
+| `E_VALIDATION_ERROR`            | Validation error in the payload         | Invalid email format, missing required fields, malformed data |
+| `E_FIELD_MISSING`               | Required field is missing               | Missing `to`, `from`, or `subject` fields                     |
+| `E_TOO_MANY_RECIPIENTS`         | Too many recipients in to/cc/bcc arrays | Combined recipients exceed 50 limit                           |
+| `E_SENDER_NOT_VERIFIED`         | Sender domain not verified              | Attempting to send from unverified domain                     |
+| `E_RECIPIENT_NOT_ALLOWED`       | Recipient not in allowed list           | Recipient address not in `allowed_destination_addresses`      |
+| `E_RECIPIENT_SUPPRESSED`        | Recipient is on suppression list        | Email address has bounced or reported your emails as spam     |
+| `E_SENDER_DOMAIN_NOT_AVAILABLE` | Domain not available for sending        | Domain not onboarded to Email Service                         |
+| `E_CONTENT_TOO_LARGE`           | Email content exceeds size limit        | Total message size exceeds the maximum                        |
+| `E_DELIVERY_FAILED`             | Could not deliver the email             | SMTP delivery failure, recipient server rejection             |
+| `E_RATE_LIMIT_EXCEEDED`         | Rate limit exceeded                     | Sending rate limit reached                                    |
+| `E_DAILY_LIMIT_EXCEEDED`        | Daily limit exceeded                    | Daily sending quota reached                                   |
+| `E_INTERNAL_SERVER_ERROR`       | Internal service error                  | Email Service temporarily unavailable                         |
 | `E_HEADER_NOT_ALLOWED`          | Header not allowed                      | Header is platform-controlled or not on the [whitelist](/email-service/reference/headers/) |
-| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field                                 |
-| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                                                |
-| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                                             |
-| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                                               |
-| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                                                    |
-| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers                                            |
+| `E_HEADER_USE_API_FIELD`        | Must use API field                      | Header like `From` must be set via the dedicated API field    |
+| `E_HEADER_VALUE_INVALID`        | Header value invalid                    | Malformed value, empty, or incorrect format                   |
+| `E_HEADER_VALUE_TOO_LONG`       | Header value too long                   | Value exceeds 2,048 byte limit                                |
+| `E_HEADER_NAME_INVALID`         | Header name invalid                     | Invalid characters or exceeds 100 byte limit                  |
+| `E_HEADERS_TOO_LARGE`           | Headers payload too large               | Total custom headers exceed 16 KB limit                       |
+| `E_HEADERS_TOO_MANY`            | Too many headers                        | More than 20 whitelisted (non-X) custom headers               |
 
 ## Legacy `EmailMessage` API
 
diff --git a/src/content/docs/email-service/concepts/index.mdx b/src/content/docs/email-service/concepts/index.mdx
index 20dd8baf3869d18..6dacc309b767a1c 100644
--- a/src/content/docs/email-service/concepts/index.mdx
+++ b/src/content/docs/email-service/concepts/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/configuration/index.mdx b/src/content/docs/email-service/configuration/index.mdx
index d8ae4416f025c07..d7381d7a1565017 100644
--- a/src/content/docs/email-service/configuration/index.mdx
+++ b/src/content/docs/email-service/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
index 7b743963157b998..be8214fb629d3e3 100644
--- a/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
+++ b/src/content/docs/email-service/examples/email-routing/hard-bounce-handling.mdx
@@ -44,145 +44,138 @@ id = "your-kv-namespace-id"
 ## Hard bounce detection
 
 ```javascript
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
-	async email(message, env, ctx) {
-		// Parse the raw email message
-		const parser = new PostalMime.default();
-		const rawEmail = new Response(message.raw);
-		const email = await parser.parse(await rawEmail.arrayBuffer());
-
-		// Check if this is a bounce notification
-		if (isBounceNotification(email)) {
-			const bounceInfo = await parseBounceInfo(email);
-
-			if (bounceInfo.type === "hard") {
-				await handleHardBounce(bounceInfo, env);
-				console.log(
-					`Hard bounce processed for: ${bounceInfo.originalRecipient}`,
-				);
-				return;
-			}
-		}
-
-		// Forward non-bounce emails normally
-		await message.forward("admin@yourdomain.com");
-	},
+  async email(message, env, ctx) {
+    // Parse the raw email message
+    const parser = new PostalMime.default();
+    const rawEmail = new Response(message.raw);
+    const email = await parser.parse(await rawEmail.arrayBuffer());
+
+    // Check if this is a bounce notification
+    if (isBounceNotification(email)) {
+      const bounceInfo = await parseBounceInfo(email);
+
+      if (bounceInfo.type === 'hard') {
+        await handleHardBounce(bounceInfo, env);
+        console.log(`Hard bounce processed for: ${bounceInfo.originalRecipient}`);
+        return;
+      }
+    }
+
+    // Forward non-bounce emails normally
+    await message.forward('admin@yourdomain.com');
+  },
 };
 
 function isBounceNotification(email) {
-	// Check common bounce indicators
-	const subject = email.subject?.toLowerCase() || "";
-	const fromAddress = email.from?.address?.toLowerCase() || "";
-
-	// Common bounce indicators
-	const bounceSubjects = [
-		"mail delivery failed",
-		"undelivered mail returned to sender",
-		"delivery status notification",
-		"returned mail",
-		"mail system error",
-	];
-
-	const bounceFromPatterns = [
-		"mailer-daemon",
-		"mail-daemon",
-		"postmaster",
-		"noreply",
-		"bounce",
-	];
-
-	return (
-		bounceSubjects.some((phrase) => subject.includes(phrase)) ||
-		bounceFromPatterns.some((pattern) => fromAddress.includes(pattern))
-	);
+  // Check common bounce indicators
+  const subject = email.subject?.toLowerCase() || '';
+  const fromAddress = email.from?.address?.toLowerCase() || '';
+
+  // Common bounce indicators
+  const bounceSubjects = [
+    'mail delivery failed',
+    'undelivered mail returned to sender',
+    'delivery status notification',
+    'returned mail',
+    'mail system error'
+  ];
+
+  const bounceFromPatterns = [
+    'mailer-daemon',
+    'mail-daemon',
+    'postmaster',
+    'noreply',
+    'bounce'
+  ];
+
+  return bounceSubjects.some(phrase => subject.includes(phrase)) ||
+         bounceFromPatterns.some(pattern => fromAddress.includes(pattern));
 }
 
 async function parseBounceInfo(email) {
-	const text = email.text || "";
-	const html = email.html || "";
-	const content = text + " " + html;
-
-	// Extract original recipient email
-	const recipientMatch =
-		content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
-		content.match(/([^\s<]+@[^\s>]+)/);
-
-	const originalRecipient = recipientMatch ? recipientMatch[1] : null;
-
-	// Determine bounce type based on content
-	const hardBounceIndicators = [
-		"user unknown",
-		"no such user",
-		"invalid recipient",
-		"recipient address rejected",
-		"mailbox unavailable",
-		"domain not found",
-		"5.1.1", // SMTP error code for bad destination mailbox
-		"5.1.2", // SMTP error code for bad destination system
-		"5.4.1", // SMTP error code for no answer from host
-	];
-
-	const isHardBounce = hardBounceIndicators.some((indicator) =>
-		content.toLowerCase().includes(indicator.toLowerCase()),
-	);
-
-	return {
-		type: isHardBounce ? "hard" : "soft",
-		originalRecipient,
-		reason: extractBounceReason(content),
-		timestamp: new Date().toISOString(),
-	};
+  const text = email.text || '';
+  const html = email.html || '';
+  const content = text + ' ' + html;
+
+  // Extract original recipient email
+  const recipientMatch = content.match(/(?:to|for|recipient):\s*([^\s<]+@[^\s>]+)/i) ||
+                        content.match(/([^\s<]+@[^\s>]+)/);
+
+  const originalRecipient = recipientMatch ? recipientMatch[1] : null;
+
+  // Determine bounce type based on content
+  const hardBounceIndicators = [
+    'user unknown',
+    'no such user',
+    'invalid recipient',
+    'recipient address rejected',
+    'mailbox unavailable',
+    'domain not found',
+    '5.1.1', // SMTP error code for bad destination mailbox
+    '5.1.2', // SMTP error code for bad destination system
+    '5.4.1', // SMTP error code for no answer from host
+  ];
+
+  const isHardBounce = hardBounceIndicators.some(indicator =>
+    content.toLowerCase().includes(indicator.toLowerCase())
+  );
+
+  return {
+    type: isHardBounce ? 'hard' : 'soft',
+    originalRecipient,
+    reason: extractBounceReason(content),
+    timestamp: new Date().toISOString()
+  };
 }
 
 function extractBounceReason(content) {
-	// Extract the specific error message
-	const reasonPatterns = [
-		/diagnostic[- ]code:\s*(.+)/i,
-		/reason:\s*(.+)/i,
-		/error:\s*(.+)/i,
-		/(5\.\d+\.\d+[^.\n]*)/i,
-	];
-
-	for (const pattern of reasonPatterns) {
-		const match = content.match(pattern);
-		if (match) {
-			return match[1].trim().split("\n")[0]; // Take first line only
-		}
-	}
-
-	return "Unknown bounce reason";
+  // Extract the specific error message
+  const reasonPatterns = [
+    /diagnostic[- ]code:\s*(.+)/i,
+    /reason:\s*(.+)/i,
+    /error:\s*(.+)/i,
+    /(5\.\d+\.\d+[^.\n]*)/i
+  ];
+
+  for (const pattern of reasonPatterns) {
+    const match = content.match(pattern);
+    if (match) {
+      return match[1].trim().split('\n')[0]; // Take first line only
+    }
+  }
+
+  return 'Unknown bounce reason';
 }
 
 async function handleHardBounce(bounceInfo, env) {
-	if (!bounceInfo.originalRecipient) {
-		console.log("Could not extract original recipient from bounce");
-		return;
-	}
-
-	// Add to suppression list in KV
-	await env.SUPPRESSION_LIST.put(
-		bounceInfo.originalRecipient,
-		JSON.stringify({
-			type: "hard_bounce",
-			reason: bounceInfo.reason,
-			timestamp: bounceInfo.timestamp,
-			status: "suppressed",
-		}),
-		{
-			metadata: {
-				bounceType: "hard",
-				addedDate: bounceInfo.timestamp,
-			},
-		},
-	);
-
-	console.log(
-		`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`,
-	);
+  if (!bounceInfo.originalRecipient) {
+    console.log('Could not extract original recipient from bounce');
+    return;
+  }
+
+  // Add to suppression list in KV
+  await env.SUPPRESSION_LIST.put(
+    bounceInfo.originalRecipient,
+    JSON.stringify({
+      type: 'hard_bounce',
+      reason: bounceInfo.reason,
+      timestamp: bounceInfo.timestamp,
+      status: 'suppressed'
+    }),
+    {
+      metadata: {
+        bounceType: 'hard',
+        addedDate: bounceInfo.timestamp
+      }
+    }
+  );
+
+  console.log(`Added ${bounceInfo.originalRecipient} to suppression list: ${bounceInfo.reason}`);
 }
-```
+````
 
 ## Testing hard bounce handling
 
diff --git a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
index 4f7199cce0ef4f7..a7a6a6f31405fa0 100644
--- a/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
+++ b/src/content/docs/email-service/examples/email-routing/spam-filtering.mdx
@@ -40,7 +40,7 @@ class SimpleSpamFilter implements SpamFilter {
 		"winner",
 		"congratulations",
 		"inheritance",
-		"lottery",
+		"lottery"
 	];
 
 	private trustedDomains = ["company.com", "trusted-partner.com", "vendor.net"];
@@ -83,10 +83,7 @@ class SimpleSpamFilter implements SpamFilter {
 		}
 
 		// Check for suspicious sender patterns
-		if (
-			sender.includes("noreply") &&
-			subject.toLowerCase().includes("urgent")
-		) {
+		if (sender.includes("noreply") && subject.toLowerCase().includes("urgent")) {
 			score += 2;
 			reasons.push("Suspicious noreply + urgent combination");
 		}
@@ -104,33 +101,31 @@ const spamFilter = new SimpleSpamFilter();
 export default {
 	async email(message, env, ctx): Promise<void> {
 		const startTime = Date.now();
-
+		
 		// Check for spam
 		const spamCheck = await spamFilter.checkSpam(message);
 
 		// Track spam check metrics
 		env.EMAIL_ANALYTICS?.writeDataPoint({
 			blobs: [
-				"spam_check_completed",
+				'spam_check_completed',
 				message.from,
 				message.to,
-				spamCheck.isSpam ? "spam" : "legitimate",
+				spamCheck.isSpam ? 'spam' : 'legitimate'
 			],
 			doubles: [
 				1, // Count
 				spamCheck.score,
-				Date.now() - startTime,
+				Date.now() - startTime
 			],
 			indexes: [
 				`spam_detected:${spamCheck.isSpam}`,
-				`score_range:${getScoreRange(spamCheck.score)}`,
-			],
+				`score_range:${getScoreRange(spamCheck.score)}`
+			]
 		});
 
 		if (spamCheck.isSpam) {
-			console.log(
-				`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`,
-			);
+			console.log(`🚫 Rejected spam email from ${message.from}: ${spamCheck.reasons.join(", ")}`);
 			message.setReject(`Message rejected: ${spamCheck.reasons[0]}`);
 			return;
 		}
@@ -146,13 +141,13 @@ export default {
 };
 
 function getScoreRange(score: number): string {
-	if (score < 0) return "trusted";
-	if (score === 0) return "neutral";
-	if (score === 1) return "suspicious";
-	return "spam";
+	if (score < 0) return 'trusted';
+	if (score === 0) return 'neutral';
+	if (score === 1) return 'suspicious';
+	return 'spam';
 }
 ```
 
 ## Advanced spam detection with AI
 
-For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
+For more sophisticated spam detection, you can enhance the basic filter using [Workers AI](/workers-ai) to analyze email content with machine learning models. This approach can identify subtle spam patterns that keyword-based filters might miss.
\ No newline at end of file
diff --git a/src/content/docs/email-service/get-started/send-emails.mdx b/src/content/docs/email-service/get-started/send-emails.mdx
index cb5765ac4807d02..14f5fccbd0ab3f5 100644
--- a/src/content/docs/email-service/get-started/send-emails.mdx
+++ b/src/content/docs/email-service/get-started/send-emails.mdx
@@ -54,14 +54,14 @@ A successful response includes the delivery status for each recipient:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"delivered": ["recipient@example.com"],
-		"permanent_bounces": [],
-		"queued": []
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "delivered": ["recipient@example.com"],
+    "permanent_bounces": [],
+    "queued": []
+  }
 }
 ```
 
@@ -84,14 +84,14 @@ If you are building on Cloudflare Workers, you can use the Workers binding for n
 2.  Add the email binding to your Wrangler configuration file:
 
     <WranglerConfig>
-    
-        ```toml
-        [[send_email]]
-        name = "EMAIL"
-        remote = true
-        ```
-    
-        </WranglerConfig>
+
+    ```toml
+    [[send_email]]
+    name = "EMAIL"
+    remote = true
+    ```
+
+    </WranglerConfig>
 
 3.  Create your Worker code in `src/index.ts`:
 
@@ -147,4 +147,4 @@ Now that you can send emails, explore advanced features:
 
 - **[Route incoming emails](/email-service/get-started/route-emails/)** - Process emails sent to your domain
 - **[API reference](/email-service/api/send-emails/)** - Complete API documentation
-- **[Examples](/email-service/examples/)** - Real-world implementation patterns
+- **[Examples](/email-service/examples/)** - Real-world implementation patterns
\ No newline at end of file
diff --git a/src/content/docs/email-service/local-development/index.mdx b/src/content/docs/email-service/local-development/index.mdx
index 90f0be957d8c338..9b9df2443a3e182 100644
--- a/src/content/docs/email-service/local-development/index.mdx
+++ b/src/content/docs/email-service/local-development/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Test and develop your email applications locally using Wrangler before deploying to production.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/local-development/routing.mdx b/src/content/docs/email-service/local-development/routing.mdx
index 50adb9e89ffd9e6..caf0d02137925c7 100644
--- a/src/content/docs/email-service/local-development/routing.mdx
+++ b/src/content/docs/email-service/local-development/routing.mdx
@@ -35,30 +35,30 @@ name = "EMAIL"
 ## Basic routing worker
 
 ```javascript
-import * as PostalMime from "postal-mime";
+import * as PostalMime from 'postal-mime';
 
 export default {
-	async email(message, env, ctx) {
-		// Parse the raw email message
-		const parser = new PostalMime.default();
-		const rawEmail = new Response(message.raw);
-		const email = await parser.parse(await rawEmail.arrayBuffer());
-
-		console.log("Received email:", {
-			from: message.from,
-			to: message.to,
-			subject: email.subject,
-			text: email.text,
-			html: email.html,
-		});
-
-		// Route based on recipient
-		if (message.to.includes("support@")) {
-			await message.forward("support-team@company.com");
-		} else {
-			await message.forward("general@company.com");
-		}
-	},
+  async email(message, env, ctx) {
+    // Parse the raw email message
+    const parser = new PostalMime.default();
+    const rawEmail = new Response(message.raw);
+    const email = await parser.parse(await rawEmail.arrayBuffer());
+
+    console.log('Received email:', {
+      from: message.from,
+      to: message.to,
+      subject: email.subject,
+      text: email.text,
+      html: email.html
+    });
+
+    // Route based on recipient
+    if (message.to.includes('support@')) {
+      await message.forward('support-team@company.com');
+    } else {
+      await message.forward('general@company.com');
+    }
+  },
 };
 ```
 
diff --git a/src/content/docs/email-service/platform/index.mdx b/src/content/docs/email-service/platform/index.mdx
index c4e599e6b17ffc9..56789154dfe88e9 100644
--- a/src/content/docs/email-service/platform/index.mdx
+++ b/src/content/docs/email-service/platform/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/platform/pricing.mdx b/src/content/docs/email-service/platform/pricing.mdx
index 4dfa8f6a7c2c0c2..914f0b2cf37e5a8 100644
--- a/src/content/docs/email-service/platform/pricing.mdx
+++ b/src/content/docs/email-service/platform/pricing.mdx
@@ -14,9 +14,9 @@ Cloudflare Email Service pricing is based on your Cloudflare plan and email usag
 
 Email Routing is available on both the Workers Free and Workers Paid plans. Email Sending is only available on the Workers Paid plan.
 
-|                                     | Workers Free  | Workers Paid                                          |
-| ----------------------------------- | ------------- | ----------------------------------------------------- |
-| **Outbound emails (Email Sending)** | Not available | 3,000 included per month, then $0.35 per 1,000 emails |
-| **Inbound emails (Email Routing)**  | Unlimited     | Unlimited                                             |
+|                                                         | Workers Free     | Workers Paid     |
+| ------------------------------------------------------- | ---------------- | ---------------- |
+| **Outbound emails (Email Sending)**                     | Not available    | 3,000 included per month, then $0.35 per 1,000 emails |
+| **Inbound emails (Email Routing)**                      | Unlimited        | Unlimited        |
 
 Email Routing Workers is billed according to [Workers pricing](/workers/platform/pricing/).
diff --git a/src/content/docs/email-service/reference/index.mdx b/src/content/docs/email-service/reference/index.mdx
index 667dce89f146995..fb104b8db015bee 100644
--- a/src/content/docs/email-service/reference/index.mdx
+++ b/src/content/docs/email-service/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
     hideIndex: true
 products:
   - email-service
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/email-service/reference/postmaster.mdx b/src/content/docs/email-service/reference/postmaster.mdx
index 329745da9935650..e5f357aa33574bd 100644
--- a/src/content/docs/email-service/reference/postmaster.mdx
+++ b/src/content/docs/email-service/reference/postmaster.mdx
@@ -164,6 +164,7 @@ This means that you can have email addresses with an internationalized domain, b
 
 ### Non-delivery reports (NDRs)
 
+
 Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
 
 ### Restrictive DMARC policies can make forwarded emails fail
diff --git a/src/content/docs/firewall/api/cf-filters/delete.mdx b/src/content/docs/firewall/api/cf-filters/delete.mdx
index 3d3ea8b45311d7f..b6c9144e5c5757d 100644
--- a/src/content/docs/firewall/api/cf-filters/delete.mdx
+++ b/src/content/docs/firewall/api/cf-filters/delete.mdx
@@ -24,17 +24,17 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>"
-		},
-		{
-			"id": "<FILTER_ID_2>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID_1>"
+    },
+    {
+      "id": "<FILTER_ID_2>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -51,13 +51,13 @@ curl --request DELETE \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID>"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID>"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/get.mdx b/src/content/docs/firewall/api/cf-filters/get.mdx
index f60ae9c7c41a342..c4c4d34c089e8f4 100644
--- a/src/content/docs/firewall/api/cf-filters/get.mdx
+++ b/src/content/docs/firewall/api/cf-filters/get.mdx
@@ -23,47 +23,47 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>",
-			"paused": false,
-			"description": "Login from office",
-			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "Login",
-			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_3>",
-			"paused": false,
-			"description": "not /api",
-			"expression": "not http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_4>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_5>",
-			"paused": false,
-			"expression": "ip.src eq 93.184.216.0"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result_info": {
-		"page": 1,
-		"per_page": 25,
-		"count": 5,
-		"total_count": 5,
-		"total_pages": 1
-	}
+  "result": [
+    {
+      "id": "<FILTER_ID_1>",
+      "paused": false,
+      "description": "Login from office",
+      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "Login",
+      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_3>",
+      "paused": false,
+      "description": "not /api",
+      "expression": "not http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_4>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_5>",
+      "paused": false,
+      "expression": "ip.src eq 93.184.216.0"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result_info": {
+    "page": 1,
+    "per_page": 25,
+    "count": 5,
+    "total_count": 5,
+    "total_pages": 1
+  }
 }
 ```
 
@@ -79,14 +79,14 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters/{filter_id}"
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<FILTER_ID>",
-		"paused": false,
-		"description": "Login from office",
-		"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<FILTER_ID>",
+    "paused": false,
+    "description": "Login from office",
+    "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/post.mdx b/src/content/docs/firewall/api/cf-filters/post.mdx
index 966cc67d408dcfc..ec20a4e1f410ada 100644
--- a/src/content/docs/firewall/api/cf-filters/post.mdx
+++ b/src/content/docs/firewall/api/cf-filters/post.mdx
@@ -43,39 +43,39 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/filters" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID_1>",
-			"paused": false,
-			"expression": "ip.src eq 93.184.216.0"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_3>",
-			"paused": false,
-			"description": "not /api",
-			"expression": "not http.request.uri.path matches \"^/api/.*$\""
-		},
-		{
-			"id": "<FILTER_ID_4>",
-			"paused": false,
-			"description": "Login",
-			"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		},
-		{
-			"id": "<FILTER_ID_5>",
-			"paused": false,
-			"description": "Login from office",
-			"expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID_1>",
+      "paused": false,
+      "expression": "ip.src eq 93.184.216.0"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_3>",
+      "paused": false,
+      "description": "not /api",
+      "expression": "not http.request.uri.path matches \"^/api/.*$\""
+    },
+    {
+      "id": "<FILTER_ID_4>",
+      "paused": false,
+      "description": "Login",
+      "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    },
+    {
+      "id": "<FILTER_ID_5>",
+      "paused": false,
+      "description": "Login from office",
+      "expression": "ip.src eq 93.184.216.0 and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/put.mdx b/src/content/docs/firewall/api/cf-filters/put.mdx
index a0412eac414fc43..4a08764ea671787 100644
--- a/src/content/docs/firewall/api/cf-filters/put.mdx
+++ b/src/content/docs/firewall/api/cf-filters/put.mdx
@@ -38,23 +38,23 @@ curl --request PUT \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<FILTER_ID>",
-			"paused": false,
-			"description": "IP of example.org",
-			"expression": "ip.src eq 93.184.216.0"
-		},
-		{
-			"id": "<FILTER_ID_2>",
-			"paused": false,
-			"description": "/api",
-			"expression": "http.request.uri.path matches \"^/api/.*$\""
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<FILTER_ID>",
+      "paused": false,
+      "description": "IP of example.org",
+      "expression": "ip.src eq 93.184.216.0"
+    },
+    {
+      "id": "<FILTER_ID_2>",
+      "paused": false,
+      "description": "/api",
+      "expression": "http.request.uri.path matches \"^/api/.*$\""
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -78,14 +78,14 @@ curl --request PUT \
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<FILTER_ID>",
-		"paused": false,
-		"description": "Login from office",
-		"expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<FILTER_ID>",
+    "paused": false,
+    "description": "Login from office",
+    "expression": "ip.src in {2400:cb00::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-filters/validation.mdx b/src/content/docs/firewall/api/cf-filters/validation.mdx
index 191219397a1902a..42402810e50cc29 100644
--- a/src/content/docs/firewall/api/cf-filters/validation.mdx
+++ b/src/content/docs/firewall/api/cf-filters/validation.mdx
@@ -10,6 +10,8 @@ description: Validate firewall rule expressions via the API.
 
 The Cloudflare Filters API supports an endpoint for validating expressions.
 
+
+
 ## Examples
 
 ### Validate expression via query string
@@ -22,14 +24,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr?expression=ip.s
 
 ```json title="Response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
-		}
-	],
-	"messages": null
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "message": "Filter parsing error:\n`ip.src==34`\n          ^^ couldn't parse address in network: invalid IP address syntax\n"
+    }
+  ],
+  "messages": null
 }
 ```
 
@@ -55,14 +57,14 @@ curl "https://api.cloudflare.com/client/v4/filters/validate-expr" \
 
 ```json title="Response"
 {
-	"result": null,
-	"success": false,
-	"errors": [
-		{
-			"message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
-		}
-	],
-	"messages": null
+  "result": null,
+  "success": false,
+  "errors": [
+    {
+      "message": "Filter parsing error:\n`ip.src in {2400:cb00::/32 2405:8100::/2000 2c0f:f248::/32 2a06:98c0::/29}`\n                                        ^^^^ number too large to fit in target type while parsing with radix 10\n"
+    }
+  ],
+  "messages": null
 }
 ```
 
diff --git a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
index c396807b1630fa8..493daca2fecd16a 100644
--- a/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
+++ b/src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx
@@ -24,9 +24,9 @@ A filter object typically looks like the following:
 
 ```json
 {
-	"id": "<FILTER_ID>",
-	"expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
-	"description": "WordPress login paths via the login page or mobile RPC endpoint"
+  "id": "<FILTER_ID>",
+  "expression": "(http.request.uri.path ~ \"^.*wp-login.php$\" or http.request.uri.path ~ \"^.*xmlrpc.php$\") and ip.src ne 93.184.216.34",
+  "description": "WordPress login paths via the login page or mobile RPC endpoint"
 }
 ```
 
@@ -38,8 +38,8 @@ The expression specified in this example filter is:
 
 This filter expression has a `(this or that) and not this` structure designed to:
 
-- Capture two WordPress paths that may be subject to brute force password attacks, and
-- Exclude traffic that comes from the IP address `93.184.216.34`.
+* Capture two WordPress paths that may be subject to brute force password attacks, and
+* Exclude traffic that comes from the IP address `93.184.216.34`.
 
 Imagine that this is an IP for your office. This expression demonstrates a filter that might be used (in a firewall rule) to block access to the WordPress login when accessed outside the office network.
 
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
index 75c661f0deb8cc4..fa662e947375338 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/get.mdx
@@ -23,70 +23,70 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID_1>",
-			"paused": false,
-			"description": "allow API traffic without challenge",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_1>",
-				"expression": "http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "/api"
-			}
-		},
-		{
-			"id": "<RULE_ID_2>",
-			"paused": false,
-			"description": "do not challenge login from office",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_2>",
-				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login from office"
-			}
-		},
-		{
-			"id": "<RULE_ID_3>",
-			"paused": false,
-			"description": "challenge login",
-			"action": "challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_3>",
-				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login"
-			}
-		},
-		{
-			"id": "<RULE_ID_4>",
-			"paused": false,
-			"description": "Non-interactive challenge site",
-			"action": "js_challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_4>",
-				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "not /api"
-			}
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result_info": {
-		"page": 1,
-		"per_page": 25,
-		"count": 4,
-		"total_count": 4,
-		"total_pages": 1
-	}
+  "result": [
+    {
+      "id": "<RULE_ID_1>",
+      "paused": false,
+      "description": "allow API traffic without challenge",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_1>",
+        "expression": "http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "/api"
+      }
+    },
+    {
+      "id": "<RULE_ID_2>",
+      "paused": false,
+      "description": "do not challenge login from office",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_2>",
+        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login from office"
+      }
+    },
+    {
+      "id": "<RULE_ID_3>",
+      "paused": false,
+      "description": "challenge login",
+      "action": "challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_3>",
+        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login"
+      }
+    },
+    {
+      "id": "<RULE_ID_4>",
+      "paused": false,
+      "description": "Non-interactive challenge site",
+      "action": "js_challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_4>",
+        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "not /api"
+      }
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result_info": {
+    "page": 1,
+    "per_page": 25,
+    "count": 4,
+    "total_count": 4,
+    "total_pages": 1
+  }
 }
 ```
 
@@ -102,21 +102,21 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules/{rule_
 
 ```json title="Response"
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"paused": false,
-		"description": "do not challenge login from office",
-		"action": "allow",
-		"priority": null,
-		"filter": {
-			"id": "<FILTER_ID>",
-			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-			"paused": false,
-			"description": "Login from office"
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "paused": false,
+    "description": "do not challenge login from office",
+    "action": "allow",
+    "priority": null,
+    "filter": {
+      "id": "<FILTER_ID>",
+      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+      "paused": false,
+      "description": "Login from office"
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
index 3c5f3df30b5c373..b3ec7601d83b43b 100644
--- a/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
+++ b/src/content/docs/firewall/api/cf-firewall-rules/post.mdx
@@ -15,8 +15,10 @@ This example creates several firewall rules using a single API call.
 
 :::note
 
+
 To create a firewall rule you need a [filter](/firewall/api/cf-filters/what-is-a-filter/) identifier (`id`). If you have not created a filter yet, refer to the [Cloudflare Filters API documentation](/firewall/api/cf-filters/).
 
+
 :::
 
 ```bash title="Request"
@@ -58,62 +60,62 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/rules" \
 
 ```json title="Response"
 {
-	"result": [
-		{
-			"id": "<RULE_ID_1>",
-			"paused": false,
-			"description": "Do not challenge login from office",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_1>",
-				"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login from office"
-			}
-		},
-		{
-			"id": "<RULE_ID_2>",
-			"paused": false,
-			"description": "Challenge login",
-			"action": "challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_2>",
-				"expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-				"paused": false,
-				"description": "Login"
-			}
-		},
-		{
-			"id": "<RULE_ID_3>",
-			"paused": false,
-			"description": "Non-interactive challenge site",
-			"action": "js_challenge",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_3>",
-				"expression": "not http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "not /api"
-			}
-		},
-		{
-			"id": "<RULE_ID_4>",
-			"paused": false,
-			"description": "Allow API traffic without challenge",
-			"action": "allow",
-			"priority": null,
-			"filter": {
-				"id": "<FILTER_ID_4>",
-				"expression": "http.request.uri.path matches \"^/api/.*$\"",
-				"paused": false,
-				"description": "/api"
-			}
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "id": "<RULE_ID_1>",
+      "paused": false,
+      "description": "Do not challenge login from office",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_1>",
+        "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login from office"
+      }
+    },
+    {
+      "id": "<RULE_ID_2>",
+      "paused": false,
+      "description": "Challenge login",
+      "action": "challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_2>",
+        "expression": "(http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+        "paused": false,
+        "description": "Login"
+      }
+    },
+    {
+      "id": "<RULE_ID_3>",
+      "paused": false,
+      "description": "Non-interactive challenge site",
+      "action": "js_challenge",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_3>",
+        "expression": "not http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "not /api"
+      }
+    },
+    {
+      "id": "<RULE_ID_4>",
+      "paused": false,
+      "description": "Allow API traffic without challenge",
+      "action": "allow",
+      "priority": null,
+      "filter": {
+        "id": "<FILTER_ID_4>",
+        "expression": "http.request.uri.path matches \"^/api/.*$\"",
+        "paused": false,
+        "description": "/api"
+      }
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
index 3136c338ab132ce..0d5982f433847fe 100644
--- a/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
+++ b/src/content/docs/firewall/cf-firewall-rules/order-priority.mdx
@@ -73,6 +73,7 @@ While your priority numbering scheme can be arbitrary, keep the following in min
 - **Rules without a priority number are evaluated last**, in order of their action precedence. For example, a rule with the _Log_ action is evaluated before a rule that has the _Block_ action. For more on action precedence, refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/).
 - **Avoid using the number `1` as a priority** to make rule order modification easier in the future.
 - **Consider grouping ranges of priority numbers into categories** that have some meaning for your deployment. Here are some examples:
+
   - 5000-9999: Trusted IP addresses
   - 10000-19999: Blocking rules for bad crawlers
   - 20000-29999: Blocking rules for abusive users/spam
diff --git a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
index 1fb0715951d644a..94c7ab99e5aa858 100644
--- a/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
+++ b/src/content/docs/fundamentals/account/account-security/cloudflare-access.mdx
@@ -21,7 +21,7 @@ To enable editing access by your Account Team:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page. (You must be logged in as a **Super Administrator**).
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Editing Permission**, switch the toggle to **On**.
 3. Select a duration.
@@ -29,6 +29,8 @@ To enable editing access by your Account Team:
 
 :::note
 
+
 In an emergency, Cloudflare Support can override your **Editing Permissions** and make updates to your account, but your Super Administrator will receive an email and the action will be recorded in your [Audit Logs](/fundamentals/account/account-security/review-audit-logs/) with an **Action** of **Break glass**.
 
+
 :::
diff --git a/src/content/docs/fundamentals/account/account-security/index.mdx b/src/content/docs/fundamentals/account/account-security/index.mdx
index 774bf0f5dba2826..62434c63a9879ee 100644
--- a/src/content/docs/fundamentals/account/account-security/index.mdx
+++ b/src/content/docs/fundamentals/account/account-security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
index 3f045d04d65881c..44b877f610b9365 100644
--- a/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
+++ b/src/content/docs/fundamentals/account/account-security/leaked-password-notifications.mdx
@@ -14,10 +14,12 @@ Refer to the [blog post](https://blog.cloudflare.com/helping-keep-customers-safe
 
 :::note[Note]
 
+
 Cloudflare does not have additional information about the specific breach or Internet service that potentially lost your password.
 
 Popular online tools such as [Have I Been Pwned](https://haveibeenpwned.com/) can help you better understand where your external accounts were attacked. If you reused this password in other systems, it is recommended that you reset it in those as well.
 
+
 :::
 
 If your password is found in a data breach, we will email you information on how to reset your password and prompt you to do so in the Cloudflare dashboard.
diff --git a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
index be25f61733a7a37..bacbe900335ef0a 100644
--- a/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
+++ b/src/content/docs/fundamentals/account/account-security/manage-active-sessions.mdx
@@ -18,7 +18,7 @@ To view the active sessions associated with your email address:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 
diff --git a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
index f93945373a085e6..9e379c53fec4c81 100644
--- a/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
+++ b/src/content/docs/fundamentals/account/account-security/zone-holds.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 Zone holds prevent other teams in your organization from adding zones that are already active in another account.
 
@@ -24,7 +24,7 @@ Zone holds are enabled by default for all Enterprise zones.
 
 When you enable a zone hold, no one else can [add your zone](/fundamentals/manage-domains/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
 
-_The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed._
+*The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed.*
 
 To enable a zone hold:
 
diff --git a/src/content/docs/fundamentals/account/create-account.mdx b/src/content/docs/fundamentals/account/create-account.mdx
index e93d05d94fd8d52..cc509b79ec43b6f 100644
--- a/src/content/docs/fundamentals/account/create-account.mdx
+++ b/src/content/docs/fundamentals/account/create-account.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
 
 To create a Cloudflare account:
 
@@ -29,7 +29,7 @@ To change your account name:
 
 1. In the Cloudflare dashboard, go to the **Configurations** page.
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Account Name**, select **Change Name**.
 3. Enter a new account name.
@@ -37,13 +37,13 @@ To change your account name:
 
 ## Best practices
 
-<Render file="create-account-best-practices" product="fundamentals" />
+<Render file="create-account-best-practices" product="fundamentals" /> 
 
-Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain.
+Refer to [Account and domain management best practices](/fundamentals/reference/best-practices/) for a detailed list of ways to protect your account and domain. 
 
 Once you [set up an account](/fundamentals/account/), you have several ways to interact with Cloudflare.
 
-## Interact with Cloudflare
+## Interact with Cloudflare 
 
 If you prefer working without code, you can manage your account and domain settings through the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
@@ -62,3 +62,4 @@ For those who prefer to interact with Cloudflare programmatically, you can use s
 | [cloudflare-go](https://github.com/cloudflare/cloudflare-go)                           | [README](https://github.com/cloudflare/cloudflare-go#readme)         | The official Go library for the Cloudflare API.                                |
 | [cloudflare-typescript](https://github.com/cloudflare/cloudflare-typescript)           | [README](https://github.com/cloudflare/cloudflare-typescript#readme) | The official TypeScript library for the Cloudflare API.                        |
 | [cloudflare-python](https://github.com/cloudflare/cloudflare-python)                   | [README](https://github.com/cloudflare/cloudflare-python#readme)     | The official Python library for the Cloudflare API.                            |
+
diff --git a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
index 535d145aa95d13f..d942475ab7e6765 100644
--- a/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
+++ b/src/content/docs/fundamentals/account/find-account-and-zone-ids.mdx
@@ -16,10 +16,10 @@ Once you [set up a new account](/fundamentals/account/) and [add your domain](/f
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button at the end of the account row.
-   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
+![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/overview-account-id.png)
 
 3. Select **Copy account ID**.
 
@@ -29,17 +29,17 @@ To copy the account ID when you only have one account:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and locate your account.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select the menu button next to your account name.
 3. From the list that appears, select **Copy account ID**.
-   ![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
+![Screenshot of the Overview page with the API section highlighted](~/assets/images/fundamentals/get-started/single-account-id.png)
 
 ## Copy your Zone ID
 
 1. In the Cloudflare dashboard, go to the **Account** home and locate your account.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. From the **Overview** page for your account, locate the **API** section towards the bottom of the page.
 
@@ -53,7 +53,7 @@ You can also find your account ID from the **Workers & Pages** section of your a
 
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
+    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. The **Account details** section contains your **Account ID**.
 3. To copy the Account ID, select **Click to copy**.
diff --git a/src/content/docs/fundamentals/account/index.mdx b/src/content/docs/fundamentals/account/index.mdx
index ed12e22c5045241..78335a849e9c2ba 100644
--- a/src/content/docs/fundamentals/account/index.mdx
+++ b/src/content/docs/fundamentals/account/index.mdx
@@ -10,7 +10,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 If you need help setting up a new Cloudflare account, refer to the following resources:
 
diff --git a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
index 692fcea9aa69c90..90ef1f2f6f50643 100644
--- a/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
+++ b/src/content/docs/fundamentals/api/how-to/control-api-access.mdx
@@ -21,7 +21,7 @@ To restrict the API access for the entire account:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Locate the **Enable API Access** section and then update the setting.
 
@@ -29,14 +29,16 @@ To restrict the API access for the entire account:
 
 :::note
 
+
 Member-level settings will override the account-level setting. If a specific member has API access enabled whereas the account has the access disabled, that member can still call APIs related to the Enterprise account.
 
+
 :::
 
 To restrict the API access for a specific member:
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Click on the member to expand and choose the intended **API Access**. If `Account Default`, then it follows the account level setting.
diff --git a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
index 8f1f58e538d2e66..f58ab298b5d15c4 100644
--- a/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
+++ b/src/content/docs/fundamentals/api/how-to/create-via-api.mdx
@@ -114,20 +114,24 @@ To fetch all available permission groups and their IDs, use the [List permission
 
 ```json output
 {
-	"result": [
-		{
-			"id": "19637fbb73d242c0a92845d8db0b95b1",
-			"name": "AI Crawl Control Read",
-			"description": "Grants access to reading AI Crawl Control",
-			"scopes": ["com.cloudflare.api.account.zone"]
-		},
-		{
-			"id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
-			"name": "AI Crawl Control Write",
-			"description": "Grants access to reading and editing AI Crawl Control",
-			"scopes": ["com.cloudflare.api.account.zone"]
-		}
-		// (...)
+  "result": [
+    {
+      "id": "19637fbb73d242c0a92845d8db0b95b1",
+      "name": "AI Crawl Control Read",
+      "description": "Grants access to reading AI Crawl Control",
+      "scopes": [
+        "com.cloudflare.api.account.zone"
+      ]
+    },
+    {
+      "id": "1ba6ab4cacdb454b913bbb93e1b8cb8c",
+      "name": "AI Crawl Control Write",
+      "description": "Grants access to reading and editing AI Crawl Control",
+      "scopes": [
+        "com.cloudflare.api.account.zone"
+      ]
+    },
+    // (...)
 	]
 }
 ```
diff --git a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
index 487d294ea4ff9cf..d084a748cb05a70 100644
--- a/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
+++ b/src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
@@ -11,8 +11,8 @@ products:
 
 API tokens can be restricted at runtime in two ways:
 
-- [Client IP address range filtering](#client-ip-address-range-filtering)
-- [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
+* [Client IP address range filtering](#client-ip-address-range-filtering)
+* [Time To Live (TTL) constraints](#time-to-live-ttl-constraints)
 
 ## Client IP address range filtering
 
@@ -26,14 +26,17 @@ Client IP address range filtering is not applied to the [Verify Token](https://d
 
 :::
 
+
 ## Time to live (TTL) constraints
 
 By default, tokens do not expire and are long lived. Defining a TTL sets when a token starts being valid and when a token is no longer valid. This is often referred to as `notBefore` and `notAfter`. Setting these timestamps limits the lifetime of the token to the defined period. Not setting the start date or `notBefore` means the token is active as soon as it is created. Not setting the end date or `notAfter` means the token does not expire.
 
 :::note
 
+
 Dates selected are defined as 00:00 UTC of that day. For finer grained time selection, use the [API](/fundamentals/api/).
 
+
 :::
 
 ![Time to Live selection calendar](~/assets/images/fundamentals/api/ttl.png)
diff --git a/src/content/docs/fundamentals/api/index.mdx b/src/content/docs/fundamentals/api/index.mdx
index 5c920d17b99595e..fc2b5ca4dd7c1ca 100644
--- a/src/content/docs/fundamentals/api/index.mdx
+++ b/src/content/docs/fundamentals/api/index.mdx
@@ -11,7 +11,7 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use the following resources to learn more about Cloudflare's REST API:
 
diff --git a/src/content/docs/fundamentals/api/reference/index.mdx b/src/content/docs/fundamentals/api/reference/index.mdx
index 51171664a4e68eb..2b69ab6e04041ec 100644
--- a/src/content/docs/fundamentals/api/reference/index.mdx
+++ b/src/content/docs/fundamentals/api/reference/index.mdx
@@ -11,6 +11,6 @@ products:
   - api
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/api/reference/limits.mdx b/src/content/docs/fundamentals/api/reference/limits.mdx
index af4f24a26742004..056310a63a2cf5e 100644
--- a/src/content/docs/fundamentals/api/reference/limits.mdx
+++ b/src/content/docs/fundamentals/api/reference/limits.mdx
@@ -11,11 +11,7 @@ products:
 
 import { Render } from "~/components";
 
-<Render
-	file="api-rate-limits"
-	product="fundamentals"
-	params={{ showHeading: true }}
-/>
+<Render file="api-rate-limits" product="fundamentals"  params={{showHeading: true}} />
 
 ## Rate limiting headers
 
diff --git a/src/content/docs/fundamentals/api/troubleshooting.mdx b/src/content/docs/fundamentals/api/troubleshooting.mdx
index 442eb608d3525d0..f1b15f7ee9bdbf6 100644
--- a/src/content/docs/fundamentals/api/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/api/troubleshooting.mdx
@@ -23,15 +23,15 @@ curl "https://api.cloudflare.com/client/v4/user/tokens/verify" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "f267e341f3dd4697bd3b9f71dd96247f",
-		"status": "active",
-		"not_before": "2018-07-01T05:20:00Z",
-		"expires_on": "2020-01-01T00:00:00Z"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "f267e341f3dd4697bd3b9f71dd96247f",
+    "status": "active",
+    "not_before": "2018-07-01T05:20:00Z",
+    "expires_on": "2020-01-01T00:00:00Z"
+  }
 }
 ```
 
diff --git a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
index 7bb8ee6aba29a4d..fc8a96817900340 100644
--- a/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
+++ b/src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx
@@ -8,15 +8,11 @@ products:
   - fundamentals
 ---
 
-import { Stream, GlossaryTooltip } from "~/components";
+import { Stream, GlossaryTooltip } from "~/components"
 
 To optimize your website or web application, Cloudflare provides [DNS](https://www.cloudflare.com/learning/dns/what-is-dns/) and [CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) services, so we can [reverse proxy](https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/) the web traffic to and from your domain.
 
-<Stream
-	id="980c8494f2403b95473d2ed687b4f402"
-	title="How Cloudflare DNS works for your domain"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public"
-/>
+<Stream id="980c8494f2403b95473d2ed687b4f402" title="How Cloudflare DNS works for your domain" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/fe425a25-66e7-4975-f4e3-32822987e000/public" />
 
 ## DNS explained
 
diff --git a/src/content/docs/fundamentals/concepts/index.mdx b/src/content/docs/fundamentals/concepts/index.mdx
index 52496a8fd9b8022..6a64b49f7e2d8a3 100644
--- a/src/content/docs/fundamentals/concepts/index.mdx
+++ b/src/content/docs/fundamentals/concepts/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
index ffb08d179a6080f..31af11a5ba634c1 100644
--- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
+++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx
@@ -10,7 +10,7 @@ products:
 
 Internet traffic is made up of people, services, and agents requesting online resources from wherever they are hosted. Your resources may be publicly available, like a website or application that anyone on the Internet can access. Or your resources may be privately available, like an internal app or network that only your employees and partners should be able to access.
 
-Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.
+Both public and private resources can be connected to the Cloudflare network to ensure only good actors can access what they are supposed to be able to access with high performance.  
 
 For example, you may not always want the direct traffic because it can come from malicious sources, like hackers, or in the form of [DDoS attacks](https://www.cloudflare.com/learning/ddos/ddos-attack-tools/how-to-ddos/). Additionally, depending on the location where the request originated, you want to ensure the traffic is [routed through the most efficient and fastest path](/argo-smart-routing/).
 
@@ -36,18 +36,18 @@ One example of on-ramping traffic to Cloudflare is updating your public website
 
 However, maybe you need to protect a private application that is not directly available on the Internet. In this scenario, you can:
 
-- Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
-- For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
+* Connect your private application to Cloudflare using [secure tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), and use a [device agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) to connect as a user.
+* For users already connected to a private company network, connect the entire network to Cloudflare using secure tunnels, and any request from a user device will access the private application through those tunnels.
 
 With these options, any request from a user device can access internal private applications via the secure private tunnels.
 
 Refer to the list below for products you can use to on-ramp traffic to Cloudflare.
 
-- [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
-- [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
-- [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
-- [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
-- The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
+* [Anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) uses Anycast IP addressing to route traffic to the nearest Cloudflare data center. Selective routing allows an Anycast network to be resilient in the face of high traffic volume, network congestion, and[ DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
+* [DNS-based](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) traffic resolves domains onboarded to [Cloudflare's CDN](/fundamentals/concepts/how-cloudflare-works/). Cloudflare's DNS directs traffic to Cloudflare's global network of servers instead of a website's origin server.
+* [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address so that your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
+* [Magic Transit](/magic-transit/about/) offers DDoS protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks by accepting IP packets destined for your network, processing them, and outputting the packets to your origin infrastructure.
+* The [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) securely and privately sends traffic from corporate devices to Cloudflare's global network while also applying advanced Zero Trust policies that check for a device's health before it connects to corporate applications.
 
 ### Off-ramp traffic from Cloudflare
 
@@ -61,6 +61,6 @@ You can also utilize [caching](/cache/) to help with performance. Instead of off
 
 Refer to the list below for products you can use to off-ramp traffic from Cloudflare.
 
-- [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
-- [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
-- [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
+* [Argo Smart Routing](/argo-smart-routing/) detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
+* [Cache](/cache/) works with cached content to avoid off-ramping to origin servers and instead serving directly from Cloudflare's global network.
+* [Regional services](/data-localization/regional-services/) lets you choose which subset of data centers decrypt and service HTTPS traffic, which can help customers who have to meet regional compliance or have preferences for maintaining regional control over their data.
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/index.mdx b/src/content/docs/fundamentals/index.mdx
index 6da0f6862aab3d2..4fbceb5e645cec0 100644
--- a/src/content/docs/fundamentals/index.mdx
+++ b/src/content/docs/fundamentals/index.mdx
@@ -24,6 +24,6 @@ Refer to the list below for additional Cloudflare resources.
 - [Cloudflare blog](https://blog.cloudflare.com)
 - [Cloudflare's Go library](https://github.com/cloudflare/cloudflare-go)
 - [Cloudflare system status](https://www.cloudflarestatus.com/)
-- [Cloudflare Radar](https://radar.cloudflare.com)
-- [Cloudflare TV](https://cloudflare.tv/schedule)
+- [Cloudflare Radar](https://radar.cloudflare.com) 
+- [Cloudflare TV](https://cloudflare.tv/schedule) 
 - [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
diff --git a/src/content/docs/fundamentals/manage-domains/add-site.mdx b/src/content/docs/fundamentals/manage-domains/add-site.mdx
index e089a041cbe43bc..081c4aeb68c902e 100644
--- a/src/content/docs/fundamentals/manage-domains/add-site.mdx
+++ b/src/content/docs/fundamentals/manage-domains/add-site.mdx
@@ -7,13 +7,7 @@ products:
   - fundamentals
 ---
 
-import {
-	DashButton,
-	GlossaryTooltip,
-	Render,
-	Stream,
-	Details,
-} from "~/components";
+import { DashButton, GlossaryTooltip, Render, Stream, Details } from "~/components";
 
 After you onboard your domain, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
 
@@ -83,7 +77,6 @@ If you encounter unexpected results when changing your nameservers, refer to the
 ## Further options
 
 ### Other DNS setups
-
 - To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/).
 - To use one or more DNS providers, refer to [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
 - Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
@@ -96,4 +89,4 @@ If you encounter unexpected results when changing your nameservers, refer to the
 
 [^2]: Enterprise customers can onboard these using [Subdomain setup](/dns/zone-setups/subdomain-setup/).
 
-[^3]: A security feature that protects DNS records from spoofing
+[^3]: A security feature that protects DNS records from spoofing
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/manage-domains/domain-version.mdx b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
index 80c3dfce25a53ae..124534a2bf1c4e0 100644
--- a/src/content/docs/fundamentals/manage-domains/domain-version.mdx
+++ b/src/content/docs/fundamentals/manage-domains/domain-version.mdx
@@ -8,25 +8,28 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 [Version Management](/version-management/) is available for Enterprise customers and allows you to safely test, deploy, and roll back changes to your zone configurations.
 
+
 ## Enable versioning
 
+
 <Render file="enable-versioning" product="version-management" />
 
+
 ## (Optional) Create additional environments
 
 <Render file="enable-default-creation" product="version-management" />
 
 These environments each serve a specific purpose and are accessed differently: <Render file="environment-defaults" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" />
-<br />
+<Render file="create-environment-situation" product="version-management" /> <br/>
 
 For more details, refer to [Create environment](/version-management/how-to/environments/#create-environment).
 
+
 ## Update configurations
 
 <Render file="edit-version" product="version-management" />
@@ -37,6 +40,7 @@ For more details, refer to [Create environment](/version-management/how-to/envir
 
 ## Promote version
 
+
 Next, [promote](/version-management/how-to/environments/#change-environment-version) your version through your different environments.
 
 <Render file="promote-version" product="version-management" />
@@ -46,3 +50,5 @@ After promoting to each environment, test the new version in your new environmen
 ## Repeat
 
 For new changes to your zone, [create a new version](/version-management/how-to/versions/#create-version) and repeat this process.
+
+
diff --git a/src/content/docs/fundamentals/manage-domains/move-domain.mdx b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
index 554db841218b10c..adb048fe514eab7 100644
--- a/src/content/docs/fundamentals/manage-domains/move-domain.mdx
+++ b/src/content/docs/fundamentals/manage-domains/move-domain.mdx
@@ -30,11 +30,13 @@ To transfer a domain from one Cloudflare account to another, you will need:
 
 :::caution
 
+
 Before transferring an active Cloudflare domain to another Cloudflare account, you must remove any [DNSSEC configurations](/dns/dnssec/) and [add-ons or subscriptions](/billing/manage/cancel-subscription/).
 
 We also recommend [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records of your zone while it is in the previous account. Then, you can [import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the correct DNS records into the new account.
 If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
+
 :::
 
 If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](#issue-new-certificates) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
diff --git a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
index 8887da35f668294..1ac459d5abe6896 100644
--- a/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
+++ b/src/content/docs/fundamentals/manage-domains/pause-cloudflare.mdx
@@ -12,7 +12,7 @@ To troubleshoot your site, you can pause Cloudflare globally. This will send tra
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and domain.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Within **Overview**, choose **Advanced Actions** > **Pause Cloudflare on Site**.
 
@@ -22,7 +22,7 @@ The process of pausing Cloudflare takes five minutes or less. This approach is p
 Disabling a zone does not impact Spectrum applications.
 :::
 
----
+***
 
 ## Alternatives to global pause
 
diff --git a/src/content/docs/fundamentals/manage-members/index.mdx b/src/content/docs/fundamentals/manage-members/index.mdx
index 349b6e8ec38dafd..854f89c1e4e7eca 100644
--- a/src/content/docs/fundamentals/manage-members/index.mdx
+++ b/src/content/docs/fundamentals/manage-members/index.mdx
@@ -12,7 +12,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 On any Cloudflare account, you can collaborate by adding members to your account and assigning them access via one or several policies.
 
diff --git a/src/content/docs/fundamentals/manage-members/policies.mdx b/src/content/docs/fundamentals/manage-members/policies.mdx
index 36f550450d46ae3..6ca9aafa9521ce1 100644
--- a/src/content/docs/fundamentals/manage-members/policies.mdx
+++ b/src/content/docs/fundamentals/manage-members/policies.mdx
@@ -27,8 +27,8 @@ For example, you may want to assign multiple policies and use scopes to control
 
 A set of standard API endpoints is present on every account that allow access to your members, which has recently been enhanced by a list of `resourceGroups` and `PermissionGroups`.
 
-- A `resourceGroup` is a unique identifier for the scope for which a policy applies.
-- A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
+* A `resourceGroup` is a unique identifier for the scope for which a policy applies.
+* A `permissionGroup` is a unique identifier for the set of roles that are assigned to a given policy.
 
 Refer to the [API documentation](/api/) for more information.
 
@@ -44,3 +44,4 @@ To understand a member’s full access, check both the **Members** and **User Gr
 
 Cloudflare is actively working on improvements to consolidate this view in a future update.
 :::
+
diff --git a/src/content/docs/fundamentals/manage-members/roles.mdx b/src/content/docs/fundamentals/manage-members/roles.mdx
index e6e4019dccc01f9..c7a01704fb29721 100644
--- a/src/content/docs/fundamentals/manage-members/roles.mdx
+++ b/src/content/docs/fundamentals/manage-members/roles.mdx
@@ -28,7 +28,7 @@ Account-scoped roles apply across an entire Cloudflare account, and through all
 | Application Security Reports Read                            | Can read Application Security Reports.                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audit Logs Viewer                                            | Can view [Audit Logs](/fundamentals/account/account-security/review-audit-logs/).                                                                                                                                                                                                                                                                                                                                                 |
 | Bot Management (Account-Wide)                                | Can edit [Bot Management](/bots/plans/bm-subscription/) (including [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/)) configurations for all domains in account.                                                                                                                                                                                                                                                    |
-| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                          |
+| Billing                                                      | Can edit the account's [billing profile](/billing/get-started/create-billing-profile/) and subscriptions                                                                                                                                                                                                                                                                                                                                      |
 | Cache Purge                                                  | Can purge the edge cache and allows the reading of zone settings.                                                                                                                                                                                                                                                                                                                                                                 |
 | Cloudflare Access                                            | Can edit [Cloudflare Access](/cloudflare-one/access-controls/policies/) and [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/).                                                                                                                                                                                                                                                                          |
 | Cloudflare CASB                                              | Can edit [Cloudflare CASB](/cloudflare-one/cloud-and-saas-findings/).                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/src/content/docs/fundamentals/manage-members/scope.mdx b/src/content/docs/fundamentals/manage-members/scope.mdx
index e75d47dafac71c1..ecfacf62744dfa0 100644
--- a/src/content/docs/fundamentals/manage-members/scope.mdx
+++ b/src/content/docs/fundamentals/manage-members/scope.mdx
@@ -19,7 +19,7 @@ To allow for flexible combinations of access to users, Cloudflare currently has
 - **Domain groups:** Use when you have related domains that share the same access needs, for example, all production domains.
 - **Specific resources:** Use when access should be limited to individual resources.
 
----
+***
 
 ## Choose the scope of roles
 
@@ -33,13 +33,15 @@ If you want the member to have a policy that applies across your account, use th
 
 | Field    | Value         |
 | -------- | ------------- |
-| Operator | _Include_     |
-| Type     | _All domains_ |
+| Operator | *Include*     |
+| Type     | *All domains* |
 
 :::note
 
+
 You can only assign [account-scoped roles](/fundamentals/manage-members/roles/#account-scoped-roles) as part of these types of policies
 
+
 :::
 
 ### Specific domains
@@ -48,9 +50,9 @@ If you want the member to have a policy that applies to a specific domain, use t
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | _Include_           |
-| Type     | _A specific domain_ |
-| Name     | _A specific domain_ |
+| Operator | *Include*           |
+| Type     | *A specific domain* |
+| Name     | *A specific domain* |
 
 ### Domain groups
 
@@ -62,10 +64,11 @@ To create a domain group:
 
 1. In the Cloudflare dashboard, go to the **Settings** > **Lists** page. (You must be logged in as a **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/)).
 
-   <DashButton url="/?to=/:account/configurations" />
+    <DashButton url="/?to=/:account/configurations" />
 
 2. For **Domain Group Manager**, select **Create**.
 3. Create your domain group:
+
    1. Select the domains to include.
    2. Add a **Name**.
    3. Select **Create**.
@@ -78,40 +81,43 @@ To assign a member permissions to a domain group, use the following combination
 
 | Field    | Value           |
 | -------- | --------------- |
-| Operator | _Include_       |
-| Type     | _Domain Group_  |
-| Name     | _Example Group_ |
+| Operator | *Include*       |
+| Type     | *Domain Group*  |
+| Name     | *Example Group* |
 
 :::note
 
+
 With Domain Groups, you can only assign [domain-scoped roles](/fundamentals/manage-members/roles/#domain-scoped-roles) to these members.
 
+
 :::
 
+
 ### Specific resources
 
 If you want the member to have a policy that applies to a specific resource, use the following combination of fields.
 
 | Field    | Value               |
 | -------- | ------------------- |
-| Operator | _Include_           |
-| Type     | _Granular_          |
-| Product  | _Product Name_      |
-| Resource | _Specific Resource_ |
+| Operator | *Include*           |
+| Type     | *Granular* |
+| Product  | *Product Name* |
+| Resource  | *Specific Resource* |
 
 #### Available scopes
 
 You can assign the following resource-specific scopes to members:
 
-| Scope                                       | Description                                                                                                                                       |
-| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Individual Access applications              | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                            |
-| Individual Access identity providers (IdPs) | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                     |
-| Individual Access policies                  | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                     |
-| Individual Access service tokens            | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                    |
-| Individual Access infrastructure targets    | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/). |
-| Individual Cloudflare Tunnel instances      | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                         |
-| Individual Cloudflare Mesh nodes            | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                   |
+| Scope                                     | Description                                                                                                                                              |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Individual Access applications               | Grant access to manage a specific [Access application](/cloudflare-one/access-controls/applications/).                                                   |
+| Individual Access identity providers (IdPs)  | Grant access to manage a specific [Cloudflare One identity provider (IdP)](/cloudflare-one/integrations/identity-providers/).                                    |
+| Individual Access policies                   | Grant access to manage a specific [Access policy](/cloudflare-one/access-controls/policies/).                                                            |
+| Individual Access service tokens             | Grant access to manage a specific [Access service token](/cloudflare-one/access-controls/service-credentials/service-tokens/).                           |
+| Individual Access infrastructure targets     | Grant access to manage a specific [Access for Infrastructure target](/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/).        |
+| Individual Cloudflare Tunnel instances       | Grant access to manage a specific [Cloudflare Tunnel](/tunnel/) instance.                                                                                |
+| Individual Cloudflare Mesh nodes             | Grant access to manage a specific [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) node.                                          |
 
 :::note
 When using scopes for specific resources, you can only assign [resource-scoped roles](/fundamentals/manage-members/roles/#resource-scoped-roles) to these members.
diff --git a/src/content/docs/fundamentals/manage-members/user-groups.mdx b/src/content/docs/fundamentals/manage-members/user-groups.mdx
index ac0ff7d261fe721..6ac8ab7b5b960bc 100644
--- a/src/content/docs/fundamentals/manage-members/user-groups.mdx
+++ b/src/content/docs/fundamentals/manage-members/user-groups.mdx
@@ -10,9 +10,9 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Tabs, TabItem } from "~/components";
+import { DashButton, Tabs, TabItem } from '~/components';
 
-User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of.
+User Groups are a collection of [account members](/fundamentals/manage-members/) that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group receiving all permissions of the roles assigned to the User Group. If users also have individually assigned permissions, then their effective permissions are the union of all of their individual permissions, plus the permissions for all of the User Groups they are a member of. 
 
 :::note
 User Group permissions are inherited by each member of the group but are not currently reflected in the role field on the **Members** page. To view a member’s full set of permissions, check both:
@@ -23,21 +23,21 @@ User Group permissions are inherited by each member of the group but are not cur
 Cloudflare is actively working on improving this experience to make inherited and direct permissions easier to view.
 :::
 
-## Create a User Group manually
+## Create a User Group manually 
 
 1. In the Cloudflare dashboard, go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Select the **Groups** tab.
 3. Select **Create a Group** and enter a name and description for your new group.
 4. Select **Create group** to confirm your changes. The **Group members** tab displays.
-5. Select **Add members**.
+5. Select **Add members**. 
 6. Select the relevant members you want to include in the group and select **Add to Group**.
 
 ### Assign a Permission Policy
 
-With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group.
+With your Group created, you can now add a [Permission Policy](/fundamentals/manage-members/policies/) to your Group. 
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -86,23 +86,24 @@ PAYLOAD
 
 ## Create a User Group with SCIM
 
-Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account.
+Customers with the SCIM integration configured can sync User Groups from an upstream identity provider to Cloudflare. Cloudflare's SCIM integration requires one external application per account. 
+
 
 :::note
 If you use the [Cloudflare dashboard SCIM integration](/fundamentals/account/account-security/scim-setup/), you can sync Groups from an upstream Identity Provider. This allows you to centralize user and group management at your identity provider.
 
 Note that when managing User Groups via SCIM:
-
-- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API.
+- You cannot change the name, members, or delete the group manually from the Cloudflare dashboard or API. 
 - The integration requires one external SCIM application per Cloudflare account.
 - Cloudflare does not currently support updating user profile fields (`firstName`, `lastName`, or `email`) via SCIM. If those attributes change in your IdP, they will not be updated in Cloudflare. These values are only set during initial provisioning.
-  :::
+:::
+
 
 To set up a user group with SCIM, refer to the [Provisioning with SCIM guide](/fundamentals/account/account-security/scim-setup/).
 
 ### Set up permissions for User Groups
 
-After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it.
+After a user group is created either manually in Cloudflare dashboard or through SCIM integration the final step is to attach permissions to it. 
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/docs/fundamentals/new-features/index.mdx b/src/content/docs/fundamentals/new-features/index.mdx
index 00ba70c15225ddb..8f052702ba7fe7e 100644
--- a/src/content/docs/fundamentals/new-features/index.mdx
+++ b/src/content/docs/fundamentals/new-features/index.mdx
@@ -10,8 +10,8 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare offers several RSS feeds to help you consume content programmatically.
 
-<DirectoryListing />
+<DirectoryListing/>
diff --git a/src/content/docs/fundamentals/organizations/limitations.mdx b/src/content/docs/fundamentals/organizations/limitations.mdx
index 037c78efb4df0b2..732b548986c8775 100644
--- a/src/content/docs/fundamentals/organizations/limitations.mdx
+++ b/src/content/docs/fundamentals/organizations/limitations.mdx
@@ -14,7 +14,7 @@ The following limitations apply during the public beta.
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Organization creation   | You must be a Super Administrator of an Enterprise account to create an Organization.                                                                                                       |
 | Adding accounts         | Once you've created an Organization, accounts of any plan type can be added. You must have Super Administrator access to the account, and it cannot already belong to another Organization. |
-| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                              |
+| Account and zone limits | Each organization supports up to 500 accounts and 5,000 zones.                                                                                                                                |
 | Roles                   | Organization Super Administrator is the only role available during the beta. Additional roles will be available in a future release.                                                        |
-| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                                              |
+| Organization deletion   | To delete an Organization, use the [API](/api/resources/organizations/methods/delete). Dashboard support is not yet available.                                       |
 | Account removal         | Self-service account removal is not yet available. To remove an account from your Organization, contact [Cloudflare Support](/support/contacting-cloudflare-support/).                      |
diff --git a/src/content/docs/fundamentals/organizations/setup.mdx b/src/content/docs/fundamentals/organizations/setup.mdx
index cb9c27ffabafa59..3cb26686125e379 100644
--- a/src/content/docs/fundamentals/organizations/setup.mdx
+++ b/src/content/docs/fundamentals/organizations/setup.mdx
@@ -101,11 +101,11 @@ You can manage Organizations using the [Cloudflare Terraform provider](https://r
 
 You may encounter the following errors during the setup flow. Please see below for more information on how to resolve these.
 
-| Error                                                                                                                                                | Description                                                                                                                                                                                                              |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Organization management is only available on the Enterprise plan at this time.                                                                       | You are not a member of any Enterprise accounts.                                                                                                                                                                         |
-| You need a super admin role on an enterprise account to create an Organization.                                                                      | You are not a Super Administrator of an Enterprise account.                                                                                                                                                              |
-| One or more of your enterprise accounts is already part of an Organization.                                                                          | You may not create another organization because your accounts are already in an organization.                                                                                                                            |
-| You have reached the maximum number of organizations.                                                                                                | You may not create another organization because you already have one.                                                                                                                                                    |
-| An Organization has already been created for accounts associated with your company. Please contact your company administrator.                       | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
-| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it. | This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data.                  |
+| Error | Description |
+| --- | --- |
+| Organization management is only available on the Enterprise plan at this time. | You are not a member of any Enterprise accounts. |
+| You need a super admin role on an enterprise account to create an Organization. | You are not a Super Administrator of an Enterprise account. |
+| One or more of your enterprise accounts is already part of an Organization. | You may not create another organization because your accounts are already in an organization. |
+| You have reached the maximum number of organizations. | You may not create another organization because you already have one. |
+| An Organization has already been created for accounts associated with your company. Please contact your company administrator. | We limit every company to one Organization for all business units. Please work with other Cloudflare administrators at your company who may have set up an Organization already to be invited to join that Organization. |
+| You are not eligible to create an Organization because we think there's a problem. Please contact Cloudflare support and we will help you create it.| This is a rare error which may indicate an issue with the internal metadata for one or more of your accounts. Before you can set up an Organization, Cloudflare needs to investigate the internal data. |
diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx
index aa834449efa4ed4..297c524991656ee 100644
--- a/src/content/docs/fundamentals/performance/improve-seo.mdx
+++ b/src/content/docs/fundamentals/performance/improve-seo.mdx
@@ -12,8 +12,10 @@ In practice, SEO is primarily about quality content, user experience, and not ma
 
 :::note[Tip:]
 
+
 For general guidelines around SEO, refer to [Google's recommendations](https://developers.google.com/search/docs/advanced/guidelines/overview).
 
+
 :::
 
 ## SEO improvements with Cloudflare
@@ -45,9 +47,9 @@ Depending on your domain's security settings, you might accidentally block searc
 
 If you notice SEO issues, make sure your:
 
-- [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
-- [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
-- [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
+* [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
+* [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
+* [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
 
 If you still notice issues with search engine crawlers, refer to our [Troubleshooting guide](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/).
 
@@ -55,7 +57,7 @@ If you still notice issues with search engine crawlers, refer to our [Troublesho
 
 The following characteristics do not affect your domain's SEO:
 
-- **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
-- **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
-- **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
-- **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
+* **Changing your nameservers**: Using Cloudflare's nameservers does not affect your domain's SEO.
+* **Server location**: According to Google, [server location](http://www.seroundtable.com/seo-geo-location-server-google-17468.html) is not important for SEO.
+* **Sites sharing IP addresses**: Search engines do not generally penalize domains using shared IP addresses unless several of these sites are malicious or spammy.
+* **Cloudflare caching**: When Cloudflare caches your content, it actually speeds up content delivery and only improves SEO. Our caching does not create duplicate content, rewrite URLs, or create additional subdomains.
diff --git a/src/content/docs/fundamentals/performance/index.mdx b/src/content/docs/fundamentals/performance/index.mdx
index 8c00c87f68d593b..4fa36b844e2eec8 100644
--- a/src/content/docs/fundamentals/performance/index.mdx
+++ b/src/content/docs/fundamentals/performance/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/performance/test-speed.mdx b/src/content/docs/fundamentals/performance/test-speed.mdx
index 246a968ab7ae1c4..12ea8823571be55 100644
--- a/src/content/docs/fundamentals/performance/test-speed.mdx
+++ b/src/content/docs/fundamentals/performance/test-speed.mdx
@@ -8,7 +8,7 @@ products:
 
 Cloudflare offers several tools to test the speed of your website, as well as the speed of your Internet connection.
 
----
+***
 
 ## Test website speed
 
@@ -24,11 +24,11 @@ If you experience any issues, make sure you are not blocking specific [user agen
 
 If your domain is not yet active on Cloudflare or you want to measure the before and after improvements of using Cloudflare, Cloudflare recommends using the following third-party tools:
 
-- [PageGym](https://pagegym.com/)
-- [GTmetrix](https://gtmetrix.com/)
-- [DebugBear](https://www.debugbear.com/test/website-speed)
-- [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
-- [WebPageTest](https://www.webpagetest.org/)
+* [PageGym](https://pagegym.com/)
+* [GTmetrix](https://gtmetrix.com/)
+* [DebugBear](https://www.debugbear.com/test/website-speed)
+* [Lighthouse](https://developer.chrome.com/docs/lighthouse/)
+* [WebPageTest](https://www.webpagetest.org/)
 
 If you use these third-party tools, you should do the following to test website speed:
 
@@ -46,11 +46,13 @@ Based on the results of these speed tests, you may want to explore other ways to
 
 :::note
 
+
 Cloudflare does not consider Time to First Byte (TTFB) the most important measure of page load speed. If you are concerned about a slower TTFB while using Cloudflare, refer to our blog post about [Cloudflare and TTFB](http://blog.cloudflare.com/ttfb-time-to-first-byte-considered-meaningles/).
 
+
 :::
 
----
+***
 
 ## Test Internet speed
 
diff --git a/src/content/docs/fundamentals/reference/best-practices.mdx b/src/content/docs/fundamentals/reference/best-practices.mdx
index 6d8aa19d844e6f7..a237a1d635c541d 100644
--- a/src/content/docs/fundamentals/reference/best-practices.mdx
+++ b/src/content/docs/fundamentals/reference/best-practices.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account.
+More and more of our lives revolve around our online presence and maintaining access to our various online accounts, such as social media, banking, personal, and business accounts. These accounts are critical to remaining connected with our loved ones and business. As such, ensuring a level of continuity with these services is critical. Below is a list of important items to help ensure you are able to maintain access or delegate access to your Cloudflare account in the event that you are unable to manage your account. 
 
 You can lose access to your account and or domain for several reasons: Death, divorce, disgruntled employee, or simply missing an email notification.
 
@@ -19,7 +19,7 @@ To help prevent loss of access:
 
 ## Relationships, partnerships, and business ventures
 
-Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active.
+Ensuring equal access with your partner, spouse, or your business partner is important to ensuring your account or domain names remain active. 
 
 If you have a domain name or a portfolio of domain names for your business, ensuring you have a strict organization policy when it comes to vendor account creation or domain name registration is critical. The steps below will ensure your organization is the owner of the account and or domain names:
 
@@ -37,4 +37,4 @@ Most if not all online services have automated billing processes that will attem
 
 ## Deceased account holder or registrant
 
-While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you.
+While often overlooked, an important part of having an online presence is ensuring continuity in the event of an unexpected accident or incapacitation of the account holder. Create clear instructions for domain or account management in the event the account holder is unable to administer the account. If you learn no instructions are available on how to access the account of the deceased, Cloudflare may be able to assist you. 
diff --git a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
index 070a9aa8b37e5a3..f040e11a6251600 100644
--- a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
+++ b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx
@@ -12,12 +12,12 @@ This endpoint is managed and served by Cloudflare. It cannot be modified or cust
 
 A few examples include (but are not limited to):
 
-- [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
-- [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
-- [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
-- [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
-- [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
-- [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
+* [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
+* [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
+* [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
+* [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
+* [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
+* [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.
 
 ## Recommended exclusions
 
diff --git a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
index e99011bb53a7c81..dd7a00e47dce594 100644
--- a/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
+++ b/src/content/docs/fundamentals/reference/cloudflare-ray-id.mdx
@@ -13,6 +13,7 @@ Ray IDs are particularly useful when evaluating Security Events for patterns or
 Ray IDs are added as a [request header, cf-ray](/fundamentals/reference/http-headers/#cf-ray), to the connection from Cloudflare to the origin web server.
 As such the Ray IDs can be found using the Developer Tools in your browser or using curl with the `-v` option to show the headers.
 
+
 :::caution
 Ray IDs are not guaranteed to be unique for every request. In some situations, different requests may have the same Ray ID.
 :::
@@ -33,7 +34,7 @@ Please note that Security Events may use sampled data to improve performance. If
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer allows you to [build queries](/log-explorer/log-search/) for filtering specific Ray IDs.
 
diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
index 4d7916b94c2550d..5a3fae1ade1c6bd 100644
--- a/src/content/docs/fundamentals/reference/connection-limits.mdx
+++ b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), there are often two established [TCP connections](/fundamentals/reference/tcp-connections/): the first is between the requesting client to Cloudflare and the second is between Cloudflare and the origin server. Each connection has their own set of TCP and HTTP limits, which are documented below.
 
@@ -24,16 +24,16 @@ When HTTP/HTTPS traffic is [proxied through Cloudflare](/fundamentals/concepts/h
 If you are using [Cloudflare tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/), refer to [Origin configuration](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) to view or modify your connection settings.
 :::
 
-| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                          | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits)        |
-| ----------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/) | No                                                                                    |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) | No                                                                                    |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/) |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) | No                                                                                    |
-| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                  | Yes                                                                                   |
-| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                 | No                                                                                    |
+| Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
+| ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 19              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 120             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | [Yes, for Enterprise zones](/api/resources/zones/subresources/settings/methods/edit/)                       |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | No                                                                             |
+| HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
+| <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
 
 ## Configurable limits
 
diff --git a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
index d4c1619380433f2..d1039a6ef7988a6 100644
--- a/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
+++ b/src/content/docs/fundamentals/reference/cryptographic-personhood.mdx
@@ -32,11 +32,11 @@ Yes, Cloudflare does collect a limited amount of data about your key. We store t
 
 Some self-signed keys and keys from certain manufacturers have been found to [not meet this requirement](https://www.chromium.org/security-keys) and should be avoided if you are minimizing your online privacy risk.
 
----
+***
 
 For more details on how we set up Cryptographic Attestation of Personhood, refer to the [introductory blog post](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/).
 
----
+***
 
 ## What devices are and are not allowed?
 
@@ -44,21 +44,21 @@ For more details on how we set up Cryptographic Attestation of Personhood, refer
 
 CAP supports a wide variety of hardware authenticators:
 
-- **Roaming (cross-platform) authenticators**:
-  - _Supported_: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
-  - _Examples_: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
-- **Platform authenticators:**
-  - _Examples_: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
+* **Roaming (cross-platform) authenticators**:
+  * *Supported*: All security keys found in the [FIDO Metadata Service 3.0](https://fidoalliance.org/metadata/), unless they have been revoked for security reasons.
+  * *Examples*: YubiKeys, HyperFIDO keys, Thetis FIDO U2F keys
+* **Platform authenticators:**
+  * *Examples*: Apple Touch ID and Face ID on iOS mobile devices and macOS laptops; Android mobile devices with fingerprint readers; Windows Hello
 
 ### Known limitations
 
 Most combinations of of web browsers and WebAuthn-capable authenticators will work, but there are some known compatibility issues with WebAuthn attestation that may prevent CAP from working successfully:
 
-- **Basic CAP**:
-  - _macOS desktop_: For TouchID, browser must be Safari
-  - _Android_: Browser must be Chrome
-- **CAP with Zero-Knowledge Proof**:
-  - _Apple platform authenticators_ (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
+* **Basic CAP**:
+  * *macOS desktop*: For TouchID, browser must be Safari
+  * *Android*: Browser must be Chrome
+* **CAP with Zero-Knowledge Proof**:
+  * *Apple platform authenticators* (e.g., iPhone with Touch ID/Face ID) are incompatible with the [zero-knowledge proof system](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/). If this fails, you will immediately be redirected to basic CAP route without having to take any further action. Since Apple uses a privacy-preserving [Apple Anonymous Attestation](https://www.w3.org/TR/webauthn/#sctn-apple-anonymous-attestation) to show that an authenticator is valid while blocking tracking, this method maintains a high standard of privacy.
 
 We are updating this list as the ecosystem evolves and as we continue to test different combinations.
 
@@ -74,16 +74,16 @@ If you do not have the necessary hardware (such as a Yubikey), you can still sol
 
 ## What are the common error codes and what do they mean?
 
-- **Unsupported_att_fmt**:
-  - _Cause_: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use _Firefox_ and select the option to "anonymise your key".
-  - _Solution:_ If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
-- **Unsupported_issuer**:
-  - _Cause_: Your key is currently not supported.
-  - _Solution_: Use a [supported key](#allowed-devices).
+* **Unsupported\_att\_fmt**:
+  * *Cause*: Your authenticator is using an unsupported attestation format (combination of browser and key). Also occurs when you use *Firefox* and select the option to "anonymise your key".
+  * *Solution:* If this error occurs during [zero-knowledge version of CAP](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/), you will automatically be redirected to the basic CAP flow. If basic CAP fails, try a different combination of supported hardware device and browser or opt for a CAPTCHA.
+* **Unsupported\_issuer**:
+  * *Cause*: Your key is currently not supported.
+  * *Solution*: Use a [supported key](#allowed-devices).
 
 ## Related resources
 
-- [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
-- [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
-- [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
-- [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
+* [https://cloudflarechallenge.com](https://cloudflarechallenge.com/) (demo site)
+* [Introducing Cryptographic Attestation of Personhood](https://blog.cloudflare.com/introducing-cryptographic-attestation-of-personhood/) (blog)
+* [Expanding Crypotgraphic Attestation of Personhood](https://blog.cloudflare.com/cap-expands-support/) (blog)
+* [Introducing Zero-Knowledge Proofs](https://blog.cloudflare.com/introducing-zero-knowledge-proofs-for-private-web-attestation-with-cross-multi-vendor-hardware/) (blog)
diff --git a/src/content/docs/fundamentals/reference/glossary.mdx b/src/content/docs/fundamentals/reference/glossary.mdx
index 0656993c5d88b81..32fb01bd11d1fa6 100644
--- a/src/content/docs/fundamentals/reference/glossary.mdx
+++ b/src/content/docs/fundamentals/reference/glossary.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's documentation.
 
diff --git a/src/content/docs/fundamentals/reference/google-analytics.mdx b/src/content/docs/fundamentals/reference/google-analytics.mdx
index 1e67ecfa7422f9b..2f936dae6e12865 100644
--- a/src/content/docs/fundamentals/reference/google-analytics.mdx
+++ b/src/content/docs/fundamentals/reference/google-analytics.mdx
@@ -19,8 +19,10 @@ Cloudflare only affects analytics tools that read logs directly from your web se
 
 :::note
 
+
 To troubleshoot potential issues with Google Analytics, refer to [Common GA setup mistakes](https://support.google.com/analytics/answer/1009683).
 
+
 :::
 
 ## Zaraz
@@ -29,6 +31,8 @@ As an alternative to the standard setup of Google Analytics with tag/snippet, Cl
 
 :::note
 
+
 Details about features of Google Analytics that are unavailable with Zaraz can be found in [Zaraz FAQ](/zaraz/faq/#tools)
 
+
 :::
diff --git a/src/content/docs/fundamentals/reference/index.mdx b/src/content/docs/fundamentals/reference/index.mdx
index e239c0c053a0085..edf24d7ad793faf 100644
--- a/src/content/docs/fundamentals/reference/index.mdx
+++ b/src/content/docs/fundamentals/reference/index.mdx
@@ -13,6 +13,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
index 1587fb70d0d1b81..15fcb26bc9607e2 100644
--- a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
+++ b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx
@@ -10,15 +10,14 @@ products:
   - fundamentals
 ---
 
-Cloudflare's first iteration of SCIM integration introduced a concept called _Virtual Groups_, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.
-
-While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:
+Cloudflare's first iteration of SCIM integration introduced a concept called *Virtual Groups*, typically identified by the pattern `CF-<accountID>-<Role Name>` in your IdP. Virtual Groups were an early implementation of group-based access control: they acted as placeholders created automatically by SCIM to map IdP groups to account memberships.  
 
+While customers could add or remove members from these groups within their IdP, Virtual Groups had important limitations:  
 - They could not be renamed or deleted in the IdP.
 - They could not be managed within Cloudflare.
 - Functionally, managing a Virtual Group was equivalent to syncing users and editing each member’s policies individually.
 
-With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.
+With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**.  
 
 If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtual Group from your IdP to Cloudflare, no action is needed.
 
@@ -33,7 +32,9 @@ If you have never synced a group linked to a `CF-<accountID>-<Role Name>` Virtua
 
 ## More resources
 
-- [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)
-- [User Groups documentation](/fundamentals/manage-members/user-groups/)
-- [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)
-- [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)
+* [User Groups changelog](/changelog/2025-06-02-user-groups-beta/)  
+* [User Groups documentation](/fundamentals/manage-members/user-groups/)  
+* [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token)  
+* [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/)  
+
+
diff --git a/src/content/docs/fundamentals/reference/partners.mdx b/src/content/docs/fundamentals/reference/partners.mdx
index a066448644a58cd..5e6be4d2e93fd82 100644
--- a/src/content/docs/fundamentals/reference/partners.mdx
+++ b/src/content/docs/fundamentals/reference/partners.mdx
@@ -9,7 +9,7 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 [Cloudflare Technology Partners](https://www.cloudflare.com/partners/technology-partners/) offer purpose-built integrations with our products, providing expanded functionality for our users. Learn how to configure these integrations with our tutorials and how-to guides.
 
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
index 106282e9575100c..7e65a2e16b6a01a 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
@@ -17,7 +17,7 @@ Unfortunately, while most people respect these limitations and understand they e
 
 The following are some recommendations for using Cloudflare's services based on what may have brought you to this page.
 
----
+***
 
 ## I'm a website operator and my content was redirected for Terms of Service violations
 
@@ -25,9 +25,9 @@ If you are on a Free, Pro, or Business Plan and your application appears to be s
 
 ## Options for web admins to remove redirects
 
-- **Serve redirected content from a grey-clouded sub-domain**
+* **Serve redirected content from a grey-clouded sub-domain**
 
-- **Serve redirected content from a paid service as outlined below**
+* **Serve redirected content from a paid service as outlined below**
 
 ## Delivering videos with Cloudflare using paid products
 
@@ -43,14 +43,14 @@ To get started with Stream, visit **Stream** from your Dashboard or [sign up](ht
 
 [Stream Delivery](https://www.cloudflare.com/products/stream-delivery/) offers caching and delivery of video content through Cloudflare data centers around the globe. This CDN feature is only available on the Cloudflare Enterprise Plan. Please [contact sales](https://www.cloudflare.com/products/stream-delivery/#) if you'd like to explore this option.
 
----
+***
 
 ## Getting information on the content you are delivering
 
 If you need more information about the content your zone is serving (for example, content type), you can use the following tools:
 
-- Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
-- Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
+* Cache Analytics users: Open the **Caching tab** on the Dashboard to filter by content type and identify the type of traffic you are transferring.
+* Users without Cache Analytics: Open the **Analytics tab** on the Dashboard and select the **Performance** section for information about the content you are serving.
 
 ![Cache Analytics - Identify type of traffic being transferred](~/assets/images/support/traffic-types.png)
 
@@ -58,6 +58,6 @@ If you need more information about the content your zone is serving (for example
 
 If you have additional questions about redirection (e.g. if you believe your content was redirected in error and have supporting evidence), file a [support ticket](https://dash.cloudflare.com/redirect?account=support) and include the following information:
 
-- Name of your domain
-- Description of the problem
-- Description of the content you're serving through Cloudflare's network
+* Name of your domain
+* Description of the problem
+* Description of the content you're serving through Cloudflare's network
diff --git a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
index a0e6c30419d4e4c..1187f88b49dbde0 100644
--- a/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
+++ b/src/content/docs/fundamentals/reference/policies-compliances/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/reference/redirects.mdx b/src/content/docs/fundamentals/reference/redirects.mdx
index faf74ce66f949a6..cd7ef6cc592e166 100644
--- a/src/content/docs/fundamentals/reference/redirects.mdx
+++ b/src/content/docs/fundamentals/reference/redirects.mdx
@@ -6,7 +6,7 @@ products:
   - fundamentals
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare offers a variety of ways to perform <GlossaryTooltip term="redirect">URL redirects</GlossaryTooltip>, which tell a visitor's browser that the location of a page has been changed.
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
index 3a4e6c9b913f065..c5e1d5484357c60 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/abuse-report-obligations.mdx
@@ -18,6 +18,6 @@ Our Trust & Safety team sends abuse reports to the domain owner or the abuse poi
 
 To assist with timely resolution and avoid potential service interruptions:
 
-- Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
-- Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
-- Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
+* Confirm that the [abuse contact email address](/fundamentals/account/account-security/abuse-contact/) associated with your account is actively managed and monitored for potential abuse report notifications.
+* Consider using a mailing list email address that goes to multiple people or teams within your organization instead of the email address for an individual person.
+* Respond to any abuse report notification within 24 hours. In your response, include any information that you believe will be relevant to Cloudflare in its assessment of the abuse report. Failure to respond in a timely manner or to address the concerns in the abuse report may result in the removal or blocking of reported content, websites, or apps and suspension or termination of Cloudflare services for the associated account.
diff --git a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
index 5c3cff418dfa842..b216ceff2722d04 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/complaint-types.mdx
@@ -13,31 +13,31 @@ products:
 
 Use Cloudflare's [online abuse form](https://abuse.cloudflare.com/) to report different types of abuse.
 
----
+***
 
 ## DMCA complaints
 
 Valid [Digital Millennium Copyright Act (DMCA)](https://www.copyright.gov/dmca/) complaints must provide all of the following details:
 
-- A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
-- Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
-- Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
-- Your contact information, including your address, telephone number, and email address.
-- A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
-- A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
+* A physical or electronic signature (typing your full name is valid) of the copyright owner or a person authorized to act on their behalf.
+* Identification of the infringed copyright (for example, a link to your original work or clear description of the materials allegedly infringed upon).
+* Identification of the infringing material and information reasonably sufficient to allow Cloudflare to locate the material on the infringing website (for example, a [link to the site](/fundamentals/reference/report-abuse/provide-specific-urls/) where the infringed copyrighted material appears).
+* Your contact information, including your address, telephone number, and email address.
+* A statement that you believe, in good faith, that the use of the material in the manner asserted is not authorized by the copyright owner, its agent, or the law.
+* A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner.
 
----
+***
 
 ## Phishing
 
 Valid phishing reports must provide all of the following details:
 
-- The domain in question.
-- The specific link to the phishing page.
+* The domain in question.
+* The specific link to the phishing page.
 
 After Cloudflare confirms existence of the phishing page, Cloudflare provides a warning page to visitors accessing the phishing link. Cloudflare also notifies the site owner to clean the malicious files from their origin web server.
 
----
+***
 
 ## Trademark infringement
 
@@ -45,7 +45,7 @@ Cloudflare only acknowledges abuse reports from trademark holders or their legal
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
----
+***
 
 ## Malware sites
 
@@ -53,7 +53,7 @@ Legitimate reports of malware URLs are blocked from loading via Cloudflare.
 
 For more details about what information is required, refer to [our abuse form](https://abuse.cloudflare.com/).
 
----
+***
 
 ## Child exploitation material
 
diff --git a/src/content/docs/fundamentals/reference/report-abuse/index.mdx b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
index 211b1f859b80956..1607f978b92b9c9 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/index.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/index.mdx
@@ -19,7 +19,7 @@ When it comes to reports of abuse on websites that use our services, our ability
 
 ## Resources
 
-- [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
-- [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
-- [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
-- [Submit abuse report](https://www.cloudflare.com/abuse/form)
+* [Read abuse policy](https://www.cloudflare.com/trust-hub/abuse-approach/)
+* [Review complaint types](/fundamentals/reference/report-abuse/complaint-types/)
+* [Providing specific URLs](/fundamentals/reference/report-abuse/provide-specific-urls/)
+* [Submit abuse report](https://www.cloudflare.com/abuse/form)
diff --git a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
index 3da4ad19a0ab288..bd36756a9df63e7 100644
--- a/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
+++ b/src/content/docs/fundamentals/reference/report-abuse/submit-report.mdx
@@ -19,10 +19,8 @@ Cloudflare offers three ways for you to submit an abuse report:
 - Public form: Refer to [Submit an Abuse Report](https://abuse.cloudflare.com/) to learn more.
 - The Cloudflare dashboard, on the **Abuse reports** page.
 
-  <DashButton url="/?to=/:account/abuse-reports" />
-  Optionally, filter the reports based on date, report status, report type, and
-  domain.
-
+    <DashButton url="/?to=/:account/abuse-reports" />
+  Optionally, filter the reports based on date, report status, report type, and domain.
 - The Cloudflare API: Use the [Abuse Reports API](/api/resources/abuse_reports/) to submit an abuse report.
 
 ## View submitted reports
@@ -31,7 +29,7 @@ Users with Admin, Super Admin, or Trust & Safety roles can view any abuse report
 
 1. In the Cloudflare dashboard, go to the **Abuse reports** page.
 
-   <DashButton url="/?to=/:account/abuse-reports" />
+    <DashButton url="/?to=/:account/abuse-reports" />
 
 2. Optionally, filter the reports based on date, report status, report type, and domain.
 
@@ -39,6 +37,6 @@ If there was a mitigation against your website due to the abuse allegation, you
 
 ## Receive notifications
 
-You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites.
+You can enable abuse notifications for your account to configure email, webhook, or PagerDuty alerts about new abuse reports against your websites. 
 
-For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
+For help setting up alerts, refer to [Configure Cloudflare notifications](/notifications/get-started/).
\ No newline at end of file
diff --git a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
index 31a4b85d98924b4..1b46a73b2f45f59 100644
--- a/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
+++ b/src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx
@@ -21,7 +21,7 @@ These lifecycle stages may be referred to in different terms across Cloudflare p
 
 ### Early access
 
-During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
+During this stage, Cloudflare makes SDK changes available that we are seeking feedback on prior to releasing for general usage. Early access will  often include warning labels or caveats on functionality that is subject to change without notice. In general, early access SDKs are not suitable for production systems unless explicitly mentioned.
 
 ### Active support
 
@@ -41,13 +41,13 @@ While Cloudflare cannot provide support for all older versions of our libraries
 
 The SDK ecosystem follows semantic versioning, which defines versions as follows:
 
-- MAJOR version when there are backward-incompatible changes made.
-- MINOR version when functionality is added in a backward compatible-manner.
-- PATCH version for backward-compatible bug fixes (without any improvements).
+* MAJOR version when there are backward-incompatible changes made.
+* MINOR version when functionality is added in a backward compatible-manner.
+* PATCH version for backward-compatible bug fixes (without any improvements).
 
 :::caution
 
-As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases _may_ contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
+As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases *may* contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
 
 If this is not suitable for your use case, pin to a known good version or use the previous major version of the library.
 :::
@@ -62,5 +62,5 @@ Alongside the automatic migration approach, we provide documentation on the chan
 
 ## Related resources
 
-- [Semantic versioning definitions](https://semver.org/)
-- [Cloudflare's Terraform documentation](/terraform/)
+* [Semantic versioning definitions](https://semver.org/)
+* [Cloudflare's Terraform documentation](/terraform/)
diff --git a/src/content/docs/fundamentals/reference/tcp-connections.mdx b/src/content/docs/fundamentals/reference/tcp-connections.mdx
index 7662f578f5197a6..2a10e61edd13149 100644
--- a/src/content/docs/fundamentals/reference/tcp-connections.mdx
+++ b/src/content/docs/fundamentals/reference/tcp-connections.mdx
@@ -18,7 +18,7 @@ accTitle: Connections with Cloudflare
 A[Visitor] <-- Connection --> B[Cloudflare global network] <-- Connection --> C[Origin server]
 ```
 
-<br />
+<br/>
 
 User traffic is routed to the nearest Cloudflare data center based on the shortest [Border Gateway Protocol](https://www.cloudflare.com/learning/security/glossary/what-is-bgp/) (BGP) path, thanks to [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) routing. Cloudflare then processes the request. In case a request is not served from Cloudflare’s data centers, Cloudflare will open a connection to the origin server to forward the request.
 
@@ -36,8 +36,10 @@ For connections to users, Cloudflare has a default idle timeout of 400 seconds.
 
 :::note
 
+
 Be aware that even if there are keep-alives, Cloudflare cannot guarantee to keep a connection, since besides idleness, there are other reasons, like capacity balancing, data center maintenance or node restarts that can cause disconnections. Having this in mind, applications should be structured to handle disconnections gracefully.
 
+
 :::
 
 TCP connection settings between the user and Cloudflare, and between Cloudflare and Origin can be customized for Enterprise customers. Reach out to your account team for more details.
diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx
index 7f18e62f0b0f805..b9e4589f7feeebc 100644
--- a/src/content/docs/fundamentals/reference/troubleshooting.mdx
+++ b/src/content/docs/fundamentals/reference/troubleshooting.mdx
@@ -15,42 +15,42 @@ When you [set up Cloudflare](/fundamentals/account/), you may experience the fol
 
 ## Error messages
 
-- [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
-- [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
-- [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
-- [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
-- [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
-- [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
-- [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
-- [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
+* [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/)
+* [`525` or `526` errors](/ssl/troubleshooting/too-many-redirects/)
+* [Cannot add DNS records with the same name](/dns/manage-dns-records/troubleshooting/records-with-same-name/)
+* [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH` or `SSL_ERROR_NO_CYPHER_OVERLAP`](/ssl/troubleshooting/version-cipher-mismatch/)
+* [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/)
+* [Record exposing origin server IP address](/dns/manage-dns-records/troubleshooting/exposed-ip-address/)
+* [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/)
+* [SSL errors in appear in my browser](/ssl/troubleshooting/general-ssl-errors/)
 
 ## Behavior
 
-- [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
-- [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
-- [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
-- [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
-- [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
-- [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
-- [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
+* [Why are Cloudflare's IPs in my origin web server logs?](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/)
+* [Is Cloudflare attacking me?](#is-cloudflare-attacking-me)
+* [Cannot add domain to Cloudflare](/dns/zone-setups/troubleshooting/cannot-add-domain/)
+* [My domain’s email stopped working](/dns/troubleshooting/email-issues/)
+* [Why is my site served over HTTP instead of HTTPS?](/ssl/edge-certificates/encrypt-visitor-traffic/)
+* [SSL is not working for my second-level subdomain, such as `dev.www.example.com`](/ssl/troubleshooting/general-ssl-errors/#only-some-of-your-subdomains-return-ssl-errors)
+* [Why was my domain deleted from Cloudflare?](/dns/zone-setups/troubleshooting/domain-deleted/)
 
 ## Cloudflare
 
-- [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
-- [Contact Cloudflare support](/support/contacting-cloudflare-support/)
-- [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
+* [Gather information to troubleshoot site issues](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/)
+* [Contact Cloudflare support](/support/contacting-cloudflare-support/)
+* [Manage email notifications](/fundamentals/user-profiles/customize-account/#notifications)
 
 ## General resources
 
-- [DNS FAQ](/dns/faq/)
-- [SSL/TLS FAQ](/ssl/faq/)
+* [DNS FAQ](/dns/faq/)
+* [SSL/TLS FAQ](/ssl/faq/)
 
 ## Is Cloudflare attacking me
 
 Two common scenarios falsely lead to the perception that Cloudflare is attacking your site:
 
-- Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
-- The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
+* Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
+* The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
 
 Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare's network.
 
diff --git a/src/content/docs/fundamentals/security/index.mdx b/src/content/docs/fundamentals/security/index.mdx
index 6998badd02eba4c..530676a405630c9 100644
--- a/src/content/docs/fundamentals/security/index.mdx
+++ b/src/content/docs/fundamentals/security/index.mdx
@@ -10,6 +10,6 @@ products:
   - fundamentals
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/fundamentals/security/pci-scans.mdx b/src/content/docs/fundamentals/security/pci-scans.mdx
index 267a0d3f3e9bc55..6d67add60af9062 100644
--- a/src/content/docs/fundamentals/security/pci-scans.mdx
+++ b/src/content/docs/fundamentals/security/pci-scans.mdx
@@ -11,8 +11,10 @@ products:
 
 :::note
 
+
 Cloudflare is PCI certified as a Data Processor. Refer to [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities) and Cloudflare's PCI DSS Responsibility Matrix for more information.
 
+
 :::
 
 PCI scanners are tools used to identify security weaknesses. When a business undergoes a compliance audit, PCI scan results are used for compliance verification.
@@ -37,7 +39,7 @@ However, customers can easily block all unwanted traffic to these ports by using
 
 You can find all our public compliance resources in the following pages:
 
-- [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
-- [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
+* [Certifications and compliance resources](https://www.cloudflare.com/trust-hub/compliance-resources/)
+* [Compliance documentation](/fundamentals/reference/policies-compliances/compliance-docs/)
 
 You can access Compliance documents in the Cloudflare dashboard by selecting your account where you are a Super Administrator and then navigating to **Support** > **Compliance Documents**.
diff --git a/src/content/docs/fundamentals/security/under-ddos-attack.mdx b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
index 2b0568e28ce011d..fec2c129035f0eb 100644
--- a/src/content/docs/fundamentals/security/under-ddos-attack.mdx
+++ b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
@@ -7,7 +7,7 @@ products:
   - fundamentals
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="ddos-definition-and-diagram" product="learning-paths" />
 
@@ -15,9 +15,9 @@ import { Render } from "~/components";
 
 Common signs that you are under DDoS attack include:
 
-- Your site is offline or slow to respond to requests.
-- Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
-- Strange requests appear in your origin web server logs that do not match normal visitor behavior.
+* Your site is offline or slow to respond to requests.
+* Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
+* Strange requests appear in your origin web server logs that do not match normal visitor behavior.
 
 :::note
 
diff --git a/src/content/docs/fundamentals/user-profiles/2fa.mdx b/src/content/docs/fundamentals/user-profiles/2fa.mdx
index 62092f62c5e8c8f..57dc48b28cb5962 100644
--- a/src/content/docs/fundamentals/user-profiles/2fa.mdx
+++ b/src/content/docs/fundamentals/user-profiles/2fa.mdx
@@ -6,10 +6,12 @@ products:
   - fundamentals
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
+
 
 <Render file="2fa-enable" product="support" />
 
+
 ## Configure security key authentication for two-factor Cloudflare login
 
 :::caution
@@ -109,7 +111,7 @@ Regenerating your backup codes will invalidate your previous codes.
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Authentication**.
@@ -127,17 +129,17 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. Select **Profile**.
 3. Select the **Authentication**.
    - To remove your security key:
-     1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
-     2. Select **Delete**.
-     3. Enter your Cloudflare password, then select **Remove**.
+      1. Select **Edit** in the **Security Key Authentication** card. A drop-down menu shows more details about your security key.
+      2. Select **Delete**.
+      3. Enter your Cloudflare password, then select **Remove**.
    - To remove your TOTP mobile application authentication:
-     1. Select **Delete method** in the **Mobile App Authentication** card.
-     2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
+      1. Select **Delete method** in the **Mobile App Authentication** card.
+      2. Enter your Cloudflare password, authenticator application code, or a recovery code, then select **Disable**.
 
 ![how to disable your TOTP mobile application authentication.](https://developerdocsgifs.cloudflaretraining.com/resampled_5fps_disable_mobile_auth_v2_final.gif)
 
@@ -145,18 +147,18 @@ If you are not the Super Administrator of an organization with **2FA Enforcement
 
 If you lose access to a mobile device, security key, or authentication code, you can solve these issues by using a backup code or retrieving a backup code from your preferred authentication app.
 
-Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid&hl=en&oco=0).
+Refer to Google's documentation to [transfer Google Authenticator codes from one Android device to another](https://support.google.com/accounts/answer/1066447?co=GENIE.Platform%3DAndroid\&hl=en\&oco=0).
 
 When setting up 2FA, you should have saved your backup codes in a secure location. To restore lost access using a Cloudflare backup code:
 
 1. Retrieve the backup code from where you stored it.
 2. Go to the [Cloudflare login page](https://dash.cloudflare.com/login), enter your username and password and select **Log in**.
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 3. You should see a page titled **Two-Factor Authentication**
-   - If it has a text box, enter one of your backup codes and select **Log in**.
-   - If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
+   * If it has a text box, enter one of your backup codes and select **Log in**.
+   * If instead you see "Insert your security key and touch it", cancel any prompts from your browser that appear and select **try another authentication method or backup code**. Proceed to enter one of your backup codes and select **Log in**.
 
 :::note
 
@@ -165,7 +167,7 @@ Once you use a backup code, it becomes invalid.
 
 ## Related resources
 
-- [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en&ref_topic=2954345&co=GENIE.Platform%3DiOS&oco=0)
-- [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
-- [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
-- [Account recovery](/fundamentals/user-profiles/account-recovery/)
+* [Google Authentication documentation](https://support.google.com/accounts/answer/1066447?hl=en\&ref_topic=2954345\&co=GENIE.Platform%3DiOS\&oco=0)
+* [YubiKey documentation](https://www.yubico.com/works-with-yubikey/catalog/cloudflare/)
+* [Set up multi-user accounts on Cloudflare](/fundamentals/manage-members/)
+* [Account recovery](/fundamentals/user-profiles/account-recovery/)
diff --git a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
index 05298913d04f3cd..31d166bcf9914c5 100644
--- a/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
+++ b/src/content/docs/fundamentals/user-profiles/account-recovery.mdx
@@ -12,7 +12,7 @@ If you do not have access to your 2FA account or backup codes and cannot current
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 
-   <DashButton url="/?to=/:account/home" />
+      <DashButton url="/?to=/:account/home" />
 
 2. On the **Two-Factor Authentication** page, select **Try recovery** on **Lost all 2FA devices and backup codes?**.
 3. Select **Begin recovery**.
@@ -24,8 +24,8 @@ If you see **Device verified**, you will receive an email within 3-5 days with i
 
 If you see **Device verification failed**, you may be able to try again considering the following:
 
-- If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
-- Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
-- You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
+   * If you clear your cookies often or are logging in from a different IP address, you have wiped Cloudflare's memory of your device and will need to use a different device to verify.
+   * Your browser may be set to clear cookies on exit or after browser or OS upgrades. This interferes with the device verification process.
+   * You may be using anti-malware or other software that automatically clears your browser cookies and makes your device unregognizable by Cloudflare's Dashboard.
 
-If you are still unable to verify your device, follow the instructions to _Request manual verification_ on the **Device verification failed** page.
+If you are still unable to verify your device, follow the instructions to *Request manual verification* on the **Device verification failed** page.
diff --git a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
index 7e8b24b3c6504bf..f848ead54c25ce4 100644
--- a/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
+++ b/src/content/docs/fundamentals/user-profiles/change-password-or-email.mdx
@@ -62,7 +62,7 @@ If you forget the email address associated with your application:
 
 ## Forgot your password
 
-You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option.
+You must be logged out of the Cloudflare dashboard to view the **Forgot your password?** option. 
 
 If you forget the password associated with your email address:
 
diff --git a/src/content/docs/fundamentals/user-profiles/customize-account.mdx b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
index c7b80fefce89a7c..e2069315ad718cd 100644
--- a/src/content/docs/fundamentals/user-profiles/customize-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/customize-account.mdx
@@ -35,9 +35,9 @@ Adjust how the Cloudflare dashboard appears on your device.
 
 2. Go to **Profile**.
 3. From **Settings** > **Dashboard appearance**, choose a value:
-   - **Dark**: Defaults to darker colors.
-   - **Light**: Defaults to lighter colors.
-   - **Use system setting**: Defaults to the option used on your device.
+   * **Dark**: Defaults to darker colors.
+   * **Light**: Defaults to lighter colors.
+   * **Use system setting**: Defaults to the option used on your device.
 
 Your dashboard display will update to the new appearance setting automatically.
 
diff --git a/src/content/docs/fundamentals/user-profiles/delete-account.mdx b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
index 09b79d815f25fa7..94289a564a45da4 100644
--- a/src/content/docs/fundamentals/user-profiles/delete-account.mdx
+++ b/src/content/docs/fundamentals/user-profiles/delete-account.mdx
@@ -28,7 +28,7 @@ Before Cloudflare can cancel your account and delete your personal information,
 - [Disable auto-renew for your Registrar domain(s)](/registrar/account-options/renew-domains#set-up-automatic-renewals)
 - If you are using a Cloudflare [CNAME setup](/dns/zone-setups/partial-setup/), [update your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) at your DNS provider to point to your website IPs or hostnames instead of Cloudflare.
 - [Delete payment information](/billing/get-started/update-billing-info/#delete-a-payment-method)
-- (_Optional_) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
+- (*Optional*) [Download a copy of your invoices](/billing/manage/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
 
 ## Delete your Cloudflare account
 
@@ -49,7 +49,7 @@ All domains, subscriptions, and billing information on your account will be remo
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **My Profile**.
 3. Select **Delete this user**.
@@ -61,3 +61,4 @@ All domains, subscriptions, and billing information on your account will be remo
 Cloudflare will purge your personal information within a year of a deletion request unless required to retain it for legal obligations (such as ongoing abuse investigations or pending litigation). Refer to the [Cloudflare Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/) for further information about the deletion of personal information following the cancellation of your account.
 
 :::
+
diff --git a/src/content/docs/fundamentals/user-profiles/login.mdx b/src/content/docs/fundamentals/user-profiles/login.mdx
index 9152dcc59e82381..e81d66c7afbac91 100644
--- a/src/content/docs/fundamentals/user-profiles/login.mdx
+++ b/src/content/docs/fundamentals/user-profiles/login.mdx
@@ -27,7 +27,6 @@ Enter your email address and password.
 If your admin has enabled [enabled SSO](/fundamentals/manage-members/dashboard-sso/), enter your email address.
 
 ### Social login
-
 Social login allows you to sign in with a trusted 3rd party sign in service such as Apple, Google, or GitHub. Social login is only available for accounts with a verified email address, or accounts that signed up via social login initially. If you have additionally configured two-factor authentication on your account, that will be presented in addition to any login and two-factor authentication provided by the social login provider.
 
 :::note
@@ -44,11 +43,12 @@ To set a password, go to [Forgot Password](https://dash.cloudflare.com/forgot-pa
 You will receive an email with instructions to set your password. Once created, use your email and the new password to log in.
 :::
 
+
 #### Sign in with Apple
 
-- **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
+* **Same Cloudflare account email as Apple ID**: You can sign in with either your email and password or sign in with Apple.
 
-- **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
+* **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.
 
 If you chose to share your email when creating a Cloudflare account with Apple ID and want to set a password and obtain an API key, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) login page and select **Forgot your password?** to trigger a password reset email.
 
@@ -73,3 +73,4 @@ If you created your Cloudflare account using Apple Relay and decide to change yo
 - Sign in with GitHub uses the [Primary email address](https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address) which is set on your GitHub account. If you change your primary email address in GitHub, you will not be able to log into your Cloudflare account using GitHub social login.
 
 - If you select **Sign in with GitHub** with an email that does not already have a Cloudflare account associated with it, Cloudflare will create a new account and allow you to sign in using **Sign in with GitHub** option moving forward.
+
diff --git a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
index 8dfe5802aeb8a3b..ce1ca48798a83bb 100644
--- a/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
+++ b/src/content/docs/fundamentals/user-profiles/multi-factor-email-authentication.mdx
@@ -25,14 +25,14 @@ Email MFA can only be disabled by enabling [two-factor authentication](/fundamen
 
 ## Troubleshoot MFA
 
-Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from _[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)_\_**.**\_
+Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from *[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)*\_**.**\_
 
 Other times, emails are rejected by the recipient email service. Cloudflare will try again it will flag your email address after several attempts and no further emails will be sent.
 
 If you still do not receive an email after ensuring your email service is not flagging Cloudflare, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
 
----
+***
 
 ## Related resources
 
-- [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
+* [Secure user access with two-factor authentication](/fundamentals/user-profiles/2fa/)
diff --git a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
index 430a7d78421a34a..b3fc9378ed0e2b3 100644
--- a/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
+++ b/src/content/docs/fundamentals/user-profiles/verify-email-address.mdx
@@ -34,7 +34,7 @@ If you cannot find your verification email or your email has expired, request an
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified).
@@ -47,11 +47,11 @@ To check your verification:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile**.
 3. For **Email Address**, your email address will have `(verified)` added after it.
 
 If your email is still not verified, try clicking the verification link in a different browser or a private window.
 
-If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
+If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.
\ No newline at end of file
diff --git a/src/content/docs/google-tag-gateway/index.mdx b/src/content/docs/google-tag-gateway/index.mdx
index 313bd3117c71010..df04561d2b6e7ba 100644
--- a/src/content/docs/google-tag-gateway/index.mdx
+++ b/src/content/docs/google-tag-gateway/index.mdx
@@ -8,8 +8,8 @@ sidebar:
   order: 1
 tags:
   - Google
----
 
+---
 import { DashButton } from "~/components";
 
 Google tag gateway for advertisers allows website owners using Cloudflare as a CDN to get the most out of ad measurement tools with just a few clicks. It allows you to deploy Google scripts using your own domain, enhancing data privacy and improving signal measurement recovery. Unlike standard setups where tags are requested from a Google domain, Google tag gateway for advertisers loads the tag from your domain and sends measurement events to your domain, where they are forwarded to Google.
@@ -25,7 +25,6 @@ Google tag gateway for advertisers is free to use. Requests routed through the g
 Site owners can enable this feature in one of two ways: through the Google tag console, or through the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/tag-management/google-tag-gateway).
 
 ### Configure in Google Tag Manager
-
 The fastest way to set up Google tag gateway for advertisers is in Google Tag Manager. [Follow the steps in Google's Help Center](https://support.google.com/analytics/answer/16061641).
 
 ### Configure in the Cloudflare dashboard
@@ -44,7 +43,7 @@ Your Cloudflare dashboard user must have one of the following [Account Roles](/f
 ![Google tag gateway for advertisers configuration](~/assets/images/google-tag-gateway/google-tag-configuration.png)
 
 4. Add your Google tag ID and the path on your website reserved for the Google tag.
-   The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
+The [Google tag ID](https://support.google.com/analytics/answer/9539598?hl=en) can be found in the Google Tag Experience dashboard. The measurement path is an unused path on your site that will load Google Tag Manager and all subsequent measurement requests.
 
 ![Add to ID and path](~/assets/images/google-tag-gateway/google-tag-id-path.png)
 
@@ -63,7 +62,6 @@ If you need different tag behavior for specific subdomains (for example, only fi
 This approach lets you maintain a single zone-wide Google tag gateway configuration while still customizing tag behavior per subdomain.
 
 ## Related resources
-
 - [Google Developer Docs: Set up Google tag gateway for advertisers](https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide?setup=auto)
 - [Google Help Center: Set up Google tag gateway for advertisers in the Google tag with Cloudflare](https://support.google.com/tagmanager/answer/16061406)
 - [Google Help Center: Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare](https://support.google.com/analytics/answer/16061641)
diff --git a/src/content/docs/health-checks/concepts/health-checks-regions.mdx b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
index 65a3eecbc16b25f..2cafe5f8e78ba1a 100644
--- a/src/content/docs/health-checks/concepts/health-checks-regions.mdx
+++ b/src/content/docs/health-checks/concepts/health-checks-regions.mdx
@@ -6,6 +6,7 @@ products:
   - health-checks
 sidebar:
   order: 4
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/health-checks/concepts/index.mdx b/src/content/docs/health-checks/concepts/index.mdx
index 4bf31c3559d964a..63214119f1c7c7c 100644
--- a/src/content/docs/health-checks/concepts/index.mdx
+++ b/src/content/docs/health-checks/concepts/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts involved in Cloudflare Health Checks.
 
diff --git a/src/content/docs/health-checks/health-checks-analytics.mdx b/src/content/docs/health-checks/health-checks-analytics.mdx
index 532c92b0c481ca8..0270a58b2a3f59a 100644
--- a/src/content/docs/health-checks/health-checks-analytics.mdx
+++ b/src/content/docs/health-checks/health-checks-analytics.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
 tags:
   - Analytics
+
 ---
 
-import { AvailableNotifications, Render, DashButton } from "~/components";
+import { AvailableNotifications, Render, DashButton } from "~/components"
 
 <Render file="smart-shield-callout" product="smart-shield" />
 
diff --git a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
index 7f000b24d42b7cc..6ac6065ecb7a80e 100644
--- a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
+++ b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
@@ -6,9 +6,10 @@ products:
   - health-checks
 sidebar:
   order: 9
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 You can [configure notification emails](/health-checks/how-to/health-checks-notifications/#configure-notifications) to be alerted when the Health Check detects that there is a change in the status of your origin server. Cloudflare will send you an email within seconds so you can take the necessary action before customers are impacted.
 
@@ -30,10 +31,12 @@ The email provides information to determine what caused the health status change
 
 :::note
 
+
 A notification is only sent after a change of status in the majority of all selected region(s).
 
 For a single region, this will be 2 of 3 data centers. With 13 regions selected, this will be 7 of 13 regions.
 
+
 :::
 
 See [common error codes](/health-checks/health-checks-analytics/#common-error-codes) for more information regarding the cause of any changes to your Health Check.
diff --git a/src/content/docs/health-checks/how-to/index.mdx b/src/content/docs/health-checks/how-to/index.mdx
index db9952b5952d517..0ee79dad8ccb82c 100644
--- a/src/content/docs/health-checks/how-to/index.mdx
+++ b/src/content/docs/health-checks/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 See the following pages for more information about standalone Health Checks:
 
diff --git a/src/content/docs/health-checks/how-to/zone-lockdown.mdx b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
index a4478cdeee2a61a..591c602337a1232 100644
--- a/src/content/docs/health-checks/how-to/zone-lockdown.mdx
+++ b/src/content/docs/health-checks/how-to/zone-lockdown.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Zone lockdown migration guide
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
+<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
index 2062eeebed2f06a..c65b5e2f272d5e2 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/drizzle-orm.mdx
@@ -34,7 +34,7 @@ npm i -D drizzle-kit tsx @types/node
 
 Add the required Node.js compatibility flags and Hyperdrive binding to your `wrangler.jsonc` file:
 
-<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive" />
+<Render file="hyperdrive-node-compatibility-requirement" product="hyperdrive"/>
 
 ## 2. Configure Drizzle
 
@@ -75,7 +75,7 @@ import { users } from "./db/schema";
 
 export interface Env {
 	HYPERDRIVE: Hyperdrive;
-}
+  }
 
 export default {
 	async fetch(request, env, ctx): Promise<Response> {
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
index 2d0266f83dce9cd..e193a5b10a6b006 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/prisma-postgres.mdx
@@ -25,13 +25,12 @@ You can connect Hyperdrive to any existing Prisma Postgres database by using you
 2. Select **Connect to your database** > **Any client**.
 3. Select **Generate database credentials**. Copy the connection string for your Prisma Postgres database.
 4. Edit the connection string to make it compatible with Hyperdrive.
-
-- Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
-- The final string will look like:
-
-````txt ins="database_name"
-postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
- ```
+  - Add the database name after the port. You may remove any query parameters, such as `?sslmode=require`.
+  - The final string will look like:
+  
+   ```txt ins="database_name"
+   postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
+    ```   
 
 :::note
 
@@ -39,7 +38,7 @@ An alternative to the Prisma Data Platform is to use the [`create-db`](https://w
 
 ```bash
 npx create-db@latest
-````
+```
 
 :::
 
diff --git a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
index 72797b0b520501a..9c1996a98116a4a 100644
--- a/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
+++ b/src/content/docs/hyperdrive/examples/connect-to-postgres/postgres-database-providers/supabase.mdx
@@ -32,7 +32,7 @@ With a database user, password, database endpoint (hostname and port) and databa
 
 :::note
 
-When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers.
+When connecting to Supabase from Hyperdrive, you should use the **Direct connection** connection string rather than the pooled connection strings. Hyperdrive will perform pooling of connections to ensure optimal access from Workers. 
 
 :::
 
diff --git a/src/content/docs/hyperdrive/observability/troubleshooting.mdx b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
index 1c6ad7bce772665..4ef6f14661763a2 100644
--- a/src/content/docs/hyperdrive/observability/troubleshooting.mdx
+++ b/src/content/docs/hyperdrive/observability/troubleshooting.mdx
@@ -32,10 +32,10 @@ Hyperdrive will also issue an empty test query, a `;` in PostgreSQL, to validate
 
 Hyperdrive may also emit `Failed to connect to the provided database` when it fails to connect to the database when attempting to create a Hyperdrive configuration. This is possible when the TLS (SSL) certificates are misconfigured. Here is a non-exhaustive table of potential failure to connect errors:
 
-| Error message                                 | Details                                                                                                                                                                                               | Recommended fixes                                                                                                                                                     |
-| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Server return error and closed connection.    | This message occurs when you attempt to connect to a database that has client certificate verification enabled.                                                                                       | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
-| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database.                                      |
+| Error message | Details               | Recommended fixes |
+| ---------- | -------------------- | --------------------- |
+| Server return error and closed connection. | This message occurs when you attempt to connect to a database that has client certificate verification enabled. | Ensure you are configuring your Hyperdrive with [client certificates](/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) if your database requires them. |
+| TLS handshake failed: cert validation failed. | This message occurs when Hyperdrive has been configured with server CA certificates and is indicating that the certificate provided by the server has not been signed by the expected CA certificate. | Ensure you are using the expected the correct CA certificate for Hyperdrive, or ensure you are connecting to the right database. |
 
 ## Connection errors
 
@@ -46,14 +46,16 @@ Hyperdrive errors that do not map 1:1 with an error message code [documented by
 
 Hyperdrive may also encounter `ErrorResponse` wire protocol messages sent by your database. Hyperdrive will pass these errors through unchanged when possible.
 
+
+
 ### Hyperdrive specific errors
 
-| Error Message                                                           | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
-| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Internal error.`                                                       | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                    |
-| `Failed to acquire a connection from the pool.`                         | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
-| `Server connection attempt failed: connection_refused`                  | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
-| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases.                            | Remove prepared statements from your MySQL queries.                                                                                                                                                                                                                                            |
+| Error Message                                          | Details                                                                                         | Recommended fixes                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Internal error.`                                      | Something is broken on our side.                                                                | Check for an ongoing incident affecting Hyperdrive, and [contact Cloudflare Support](/support/contacting-cloudflare-support/). Retrying the query is appropriate, if it makes sense for your usage pattern.                                                                                                                               |
+| `Failed to acquire a connection from the pool.`        | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender.            |
+| `Server connection attempt failed: connection_refused` | Hyperdrive is unable to create new connections to your origin database.                         | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
+| `Hyperdrive does not currently support MySQL COM_STMT_PREPARE messages` | Hyperdrive does not support prepared statements for MySQL databases. | Remove prepared statements from your MySQL queries. |
 
 ### Node errors
 
@@ -73,8 +75,8 @@ If your queries are not being cached despite Hyperdrive having caching enabled,
 
 ### Driver errors
 
-| Error Message                                              | Details                                                                                                                                              | Recommended fixes                                                                                                                                                                               |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | `Code generation from strings disallowed for this context` | The database driver you are using is attempting to use the `eval()` command, which is unsupported on Cloudflare Workers (common in `mysql2` driver). | Configure the database driver to not use `eval()`. See how to [configure `mysql2` to disable the usage of `eval()`](/hyperdrive/examples/connect-to-mysql/mysql-drivers-and-libraries/mysql2/). |
 
 ### Stale connection and I/O context errors
@@ -83,46 +85,46 @@ These errors occur when a database client or connection is created in the global
 
 #### Workers runtime errors
 
-| Error Message                                                                                                                                                                                                                  | Details                                                                                                                     | Recommended fixes                                                                                                                                                             |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.`                                           | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function.                                                                                      |
-| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request.                         | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope.` | Your Worker is attempting to open a database connection or perform I/O during script startup, outside of a request handler. | Move the database client creation into your `fetch`, `queue`, or other handler function. |
+| `Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.` | A database connection or client created during one request is being reused in a subsequent request. | Create a new database client on every request instead of caching it in a global variable. Hyperdrive's connection pooling already eliminates the connection startup overhead. |
 
 #### node-postgres (`pg`) errors
 
-| Error Message                                                    | Details                                                                                                                                         | Recommended fixes                                                                                                                         |
-| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| `Connection terminated`                                          | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request.                                     | Create a new `Client` inside your handler instead of reusing one from a prior request.                                                    |
-| `Connection terminated unexpectedly`                             | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request.                                                                              |
-| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests).                                                 | Create a new `Client` inside your handler. Do not store clients in global variables.                                                      |
-| `Client was closed and is not queryable`                         | A query was attempted on a client whose `.end()` method was already called.                                                                     | Create a new `Client` inside your handler instead of reusing one.                                                                         |
-| `Cannot use a pool after calling end on the pool`                | `pool.connect()` was called on a `Pool` instance that has already been ended.                                                                   | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
-| `Client has already been connected. You cannot reuse a client.`  | `client.connect()` was called on a client that was already connected in a previous invocation.                                                  | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected.                                            |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Connection terminated` | The client's `.end()` method was called, or the connection was cleaned up at the end of a previous request. | Create a new `Client` inside your handler instead of reusing one from a prior request. |
+| `Connection terminated unexpectedly` | The underlying connection was dropped without an explicit `.end()` call — for example, when a previous request's context was garbage collected. | Create a new `Client` inside your handler for every request. |
+| `Client has encountered a connection error and is not queryable` | A socket-level error occurred on the connection (common when reusing a client across requests). | Create a new `Client` inside your handler. Do not store clients in global variables. |
+| `Client was closed and is not queryable` | A query was attempted on a client whose `.end()` method was already called. | Create a new `Client` inside your handler instead of reusing one. |
+| `Cannot use a pool after calling end on the pool` | `pool.connect()` was called on a `Pool` instance that has already been ended. | Do not use `new Pool()` in the global scope. Create a `new Client()` inside your handler — Hyperdrive handles connection pooling for you. |
+| `Client has already been connected. You cannot reuse a client.` | `client.connect()` was called on a client that was already connected in a previous invocation. | Create a new `Client` per request. node-postgres clients cannot be reconnected once connected. |
 
 #### Postgres.js (`postgres`) errors
 
 Postgres.js error messages include the error code and the target host. The `code` property on the error object contains the error code.
 
-| Error Message                              | Details                                                                                                                                                                                 | Recommended fixes                                                                                                                           |
-| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `write CONNECTION_ENDED <host>:<port>`     | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`.                                              | Create a new `postgres()` instance inside your handler.                                                                                     |
-| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request.                                                                   |
-| `write CONNECTION_CLOSED <host>:<port>`    | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`.                                                                        | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `write CONNECTION_ENDED <host>:<port>` | A query was attempted after `sql.end()` was called, or the connection was cleaned up from a prior request. Error code: `CONNECTION_ENDED`. | Create a new `postgres()` instance inside your handler. |
+| `write CONNECTION_DESTROYED <host>:<port>` | The connection was forcefully terminated — for example, during `sql.end({ timeout })` expiration, or because the connection was already terminated. Error code: `CONNECTION_DESTROYED`. | Create a new `postgres()` instance inside your handler for every request. |
+| `write CONNECTION_CLOSED <host>:<port>` | The underlying socket was closed unexpectedly while queries were still pending. Error code: `CONNECTION_CLOSED`. | Create a new `postgres()` instance inside your handler. If this occurs within a single request, check for network issues or query timeouts. |
 
 #### mysql2 errors
 
-| Error Message                                              | Details                                                                                                                           | Recommended fixes                                                                                                                          |
-| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error.                                  | Create a new connection inside your handler instead of reusing one from global scope.                                                      |
-| `Connection lost: The server closed the connection.`       | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request.                                                                             |
-| `Pool is closed.`                                          | `pool.getConnection()` was called on a pool that has already been closed.                                                         | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Can't add new command when connection is in closed state` | A query was attempted on a connection that has already been closed or encountered a fatal error. | Create a new connection inside your handler instead of reusing one from global scope. |
+| `Connection lost: The server closed the connection.` | The underlying socket was closed by the server or was garbage collected between requests. Error code: `PROTOCOL_CONNECTION_LOST`. | Create a new connection inside your handler for every request. |
+| `Pool is closed.` | `pool.getConnection()` was called on a pool that has already been closed. | Do not use `createPool()` in the global scope. Create a new `createConnection()` inside your handler — Hyperdrive handles pooling for you. |
 
 #### mysql errors
 
-| Error Message                                                   | Details                                                                                                                                   | Recommended fixes                                                                            |
-| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| `Cannot enqueue Query after fatal error.`                       | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`.        | Create a new connection inside your handler instead of reusing one from global scope.        |
-| `Cannot enqueue Query after invoking quit.`                     | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`.                               | Create a new connection inside your handler for every request.                               |
+| Error Message                                    | Details                                                                                                               | Recommended fixes                                                                                                            |
+| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Cannot enqueue Query after fatal error.` | A query was attempted on a connection that previously encountered a fatal error. Error code: `PROTOCOL_ENQUEUE_AFTER_FATAL_ERROR`. | Create a new connection inside your handler instead of reusing one from global scope. |
+| `Cannot enqueue Query after invoking quit.` | A query was attempted on a connection after `.end()` was called. Error code: `PROTOCOL_ENQUEUE_AFTER_QUIT`. | Create a new connection inside your handler for every request. |
 | `Cannot enqueue Handshake after already enqueuing a Handshake.` | `.connect()` was called on a connection that was already connected in a previous request. Error code: `PROTOCOL_ENQUEUE_HANDSHAKE_TWICE`. | Create a new connection per request. mysql connections cannot be reconnected once connected. |
 
 ### Improve performance
diff --git a/src/content/docs/hyperdrive/platform/limits.mdx b/src/content/docs/hyperdrive/platform/limits.mdx
index 312468a7fe964d7..76f3f59ff4ae007 100644
--- a/src/content/docs/hyperdrive/platform/limits.mdx
+++ b/src/content/docs/hyperdrive/platform/limits.mdx
@@ -14,10 +14,10 @@ The following limits apply to Hyperdrive configurations, connections, and querie
 
 These limits apply when creating or updating Hyperdrive configurations.
 
-| Limit                             | Free                  | Paid                  |
-| --------------------------------- | --------------------- | --------------------- |
-| Maximum configured databases      | 10 per account        | 25 per account        |
-| Maximum username length [^1]      | 63 characters (bytes) | 63 characters (bytes) |
+| Limit                          | Free                  | Paid                  |
+| ------------------------------ | --------------------- | --------------------- |
+| Maximum configured databases   | 10 per account        | 25 per account        |
+| Maximum username length [^1]   | 63 characters (bytes) | 63 characters (bytes) |
 | Maximum database name length [^1] | 63 characters (bytes) | 63 characters (bytes) |
 
 [^1]: This is a limit enforced by PostgreSQL. Some database providers may enforce smaller limits.
@@ -26,10 +26,10 @@ These limits apply when creating or updating Hyperdrive configurations.
 
 These limits apply to connections between Hyperdrive and your origin database.
 
-| Limit                                                        | Free            | Paid             |
-| ------------------------------------------------------------ | --------------- | ---------------- |
-| Initial connection timeout                                   | 15 seconds      | 15 seconds       |
-| Idle connection timeout                                      | 10 minutes      | 10 minutes       |
+| Limit                              | Free                     | Paid                      |
+| ---------------------------------- | ------------------------ | ------------------------- |
+| Initial connection timeout         | 15 seconds               | 15 seconds                |
+| Idle connection timeout            | 10 minutes               | 10 minutes                |
 | Maximum origin database connections (per configuration) [^2] | ~20 connections | ~100 connections |
 
 Hyperdrive does not limit the number of concurrent client connections from your Workers. However, Hyperdrive limits connections to your origin database because most hosted databases have connection limits.
@@ -40,9 +40,9 @@ Hyperdrive does not limit the number of concurrent client connections from your
 
 When Hyperdrive cannot acquire a connection to your origin database, you may see one of the following errors:
 
-| Error message                                          | Cause                                                                                                                                                           |
-| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Failed to acquire a connection from the pool.`        | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause.                           |
+| Error message | Cause |
+| ------------- | ----- |
+| `Failed to acquire a connection from the pool.` | The connection pool is exhausted because connections are held open too long. Long-running queries or transactions are a common cause. |
 | `Server connection attempt failed: connection_refused` | Your origin database is rejecting connections. This can occur when a firewall blocks Hyperdrive, or when your database provider's connection limit is exceeded. |
 
 For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdrive/observability/troubleshooting/).
@@ -51,10 +51,10 @@ For a complete list of error codes, refer to [Troubleshoot and debug](/hyperdriv
 
 These limits apply to queries sent through Hyperdrive.
 
-| Limit                              | Free       | Paid       |
-| ---------------------------------- | ---------- | ---------- |
+| Limit                              | Free      | Paid      |
+| ---------------------------------- | --------- | --------- |
 | Maximum query (statement) duration | 60 seconds | 60 seconds |
-| Maximum cached query response size | 50 MB      | 50 MB      |
+| Maximum cached query response size | 50 MB     | 50 MB     |
 
 Queries exceeding the maximum duration are terminated. Query responses larger than 50 MB are not cached but are still returned to your Worker.
 
diff --git a/src/content/docs/hyperdrive/platform/storage-options.mdx b/src/content/docs/hyperdrive/platform/storage-options.mdx
index e47f0bee278b20d..15e4357c49ab353 100644
--- a/src/content/docs/hyperdrive/platform/storage-options.mdx
+++ b/src/content/docs/hyperdrive/platform/storage-options.mdx
@@ -9,5 +9,5 @@ products:
   - hyperdrive
   - kv
   - r2
-  - d1
+  - d1 
 ---
diff --git a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
index 634a4a834452673..79d2a4c9a8334f6 100644
--- a/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
+++ b/src/content/docs/hyperdrive/reference/wrangler-commands.mdx
@@ -12,4 +12,4 @@ import { WranglerNamespace } from "~/components";
 
 The following [Wrangler commands](/workers/wrangler/) apply to Hyperdrive.
 
-<WranglerNamespace namespace="hyperdrive" />
+<WranglerNamespace namespace="hyperdrive" />
\ No newline at end of file
diff --git a/src/content/docs/hyperdrive/tutorials/index.mdx b/src/content/docs/hyperdrive/tutorials/index.mdx
index 20365d245d2b967..303882afc56a048 100644
--- a/src/content/docs/hyperdrive/tutorials/index.mdx
+++ b/src/content/docs/hyperdrive/tutorials/index.mdx
@@ -10,7 +10,7 @@ products:
   - workers
 ---
 
-import { GlossaryTooltip, ListTutorials } from "~/components";
+import { GlossaryTooltip, ListTutorials } from "~/components"
 
 View <GlossaryTooltip term="tutorial">tutorials</GlossaryTooltip> to help you get started with Hyperdrive.
 
diff --git a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
index 83a5d692b9d5e21..b9f564b90204b67 100644
--- a/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
+++ b/src/content/docs/hyperdrive/tutorials/serverless-timeseries-api-with-timescale.mdx
@@ -3,7 +3,7 @@ reviewed: 2023-10-30
 difficulty: Beginner
 pcx_content_type: tutorial
 title: Create a serverless, globally distributed time-series API with Timescale
-products: [workers]
+products:	[workers]
 tags:
   - PostgreSQL
   - TypeScript
diff --git a/src/content/docs/images/optimization/make-responsive-images.mdx b/src/content/docs/images/optimization/make-responsive-images.mdx
index 951c3590cc0ae6e..a0dcd9f7f0c9726 100644
--- a/src/content/docs/images/optimization/make-responsive-images.mdx
+++ b/src/content/docs/images/optimization/make-responsive-images.mdx
@@ -68,7 +68,12 @@ The browser evaluates screen size, pixel density, and network conditions, then s
 The snippet below shows how `srcset` can be used within an `<img>` tag to serve one of two possible sizes, depending on the user's device pixel ratio:
 
 ```html
-<img src="portrait-800w.jpg" srcset="portrait-1600.jpg 2x" />
+<img
+	src="portrait-800w.jpg"
+	srcset="
+		portrait-1600.jpg 2x,
+	"
+/>
 ```
 
 Instead of pre-generating each size, use Images to point every `srcset` entry at the same source image with a different `width` parameter and pixel density descriptor (for example, `2x`). Once the browser selects the right width for the user's device pixel ratio, Cloudflare dynamically generates the resized version on request:
@@ -159,11 +164,11 @@ The default breakpoints for client hints are: `320`, `768`, `960`, and `1200` pi
 The following table shows the widths that Cloudflare will pick based on the default breakpoints. If the detected viewport width exceeds the largest breakpoint, the image is served at that largest breakpoint.
 
 | Detected viewport width | Served image width |
-| ----------------------- | ------------------ |
-| 280px                   | 320px              |
-| 500px                   | 768px              |
-| 960px                   | 960px              |
-| 1500px                  | 1200px             |
+| ---------- | ------------- |
+| 280px          | 320px         |
+| 500px          | 768px         |
+| 960px          | 960px         |
+| 1500px          | 1200px        |
 
 You can override the default breakpoints using the [`wbreakpoints`](/images/optimization/features/#width) sub-parameter, which accepts positive integers separated by semicolons.
 
diff --git a/src/content/docs/images/optimization/transformations/flows.mdx b/src/content/docs/images/optimization/transformations/flows.mdx
index c9d36c389aba1ca..90b4c423f905e10 100644
--- a/src/content/docs/images/optimization/transformations/flows.mdx
+++ b/src/content/docs/images/optimization/transformations/flows.mdx
@@ -6,12 +6,10 @@ sidebar:
   products:
     - images
 ---
-
 import { Description, Render } from "~/components";
 
 <Description>
-	Define automated rules to optimize remote images without writing any code or
-	changing your existing URLs.
+	Define automated rules to optimize remote images without writing any code or changing your existing URLs.
 </Description>
 
 Flows let you automatically apply image optimization to requests on your zone.
@@ -34,7 +32,6 @@ Currently, Cloudflare supports flows for Fastly Image Optimizer. When enabled, C
 A **custom flow** lets you define your own conditions and actions for image optimization.
 
 This is well-suited for situations where you want to optimize your images broadly and consistently, such as:
-
 - **Automatic format conversion** — Transcode all images to modern formats like AVIF or WebP across your entire site.
 - **Responsive sizing** — Automatically resize images based on each user's device.
 - **Directory-based optimization** — Enforce a consistent size for all images in a particular path, such as 100x100 for images where the path contains `/thumbnail`.
@@ -44,19 +41,16 @@ This is well-suited for situations where you want to optimize your images broadl
 Before setting up a flow, make sure that transformations are turned on for your zone under **Images** > **Transformations** in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/images/transformations).
 
 When an image is requested on your zone, Cloudflare checks to see whether the request matches the conditions for any of your configured flows:
-
 - Flows are evaluated from top to bottom in the order that they appear in the dashboard.
 - If a request matches more than one flow, only the first matching flow will run.
 - If no flow matches, then the request passes through to your origin unmodified.
 - To control priority, you can reorder flows in the dashboard.
 
 If the request matches a flow's conditions, then Cloudflare rewrites the URL to pass through the Images service with the specified parameters:
-
 - A custom flow triggers only on requests for [supported image extensions](/images/get-started/limits/). HTML pages, CSS files, and other non-images are never affected.
 - A provider flow evaluates requests based on provider-specific optimization parameters. For example, a Fastly provider flow triggers only when the request contains parameters like `?width`, `?height`, or `?fit`. Cloudflare will ignore any unrecognized parameters.
 
 In your request lifecycle, flows are evaluated after standard HTTP [redirect rules](/rules/url-forwarding/):
-
 - Any existing URL rewrites or redirect rules will be applied before Images evaluates the request, which may affect matching behavior.
 - Flows include built-in loop prevention. If the request is already coming from the Images service, then the flow will not re-trigger on that subrequest.
 
@@ -65,7 +59,6 @@ In your request lifecycle, flows are evaluated after standard HTTP [redirect rul
 Currently, Cloudflare supports flows to handle migrations from Fastly Image Optimizer.
 
 To add a provider flow:
-
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Images** > **Transformations** and select your zone.
 3. Select the **Automation** tab, then select **Add provider flow**.
@@ -129,11 +122,11 @@ Cloudflare determines the optimal width using either [client hints](/images/opti
 
 You can fine-tune the `width=auto` behavior with the following sub-parameters:
 
-| Sub-parameter  | Description                                                                   | Default            |
-| -------------- | ----------------------------------------------------------------------------- | ------------------ |
-| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints)                  | `320;768;960;1200` |
-| `wmobile`      | Override default width, in pixels, for mobile devices (user-agent detection)  | `768`              |
-| `wdesktop`     | Override default width, in pixels, for desktop devices (user-agent detection) | `1200`             |
+| Sub-parameter | Description | Default |
+| --- | --- | --- |
+| `wbreakpoints` | Override default breakpoint widths, in pixels (client hints) | `320;768;960;1200` |
+| `wmobile` | Override default width, in pixels, for mobile devices (user-agent detection) | `768` |
+| `wdesktop` | Override default width, in pixels, for desktop devices (user-agent detection) | `1200` |
 
 To learn how `width=auto` works, refer to our guide on [serving responsive images](/images/optimization/make-responsive-images/).
 
diff --git a/src/content/docs/images/optimization/transformations/overview.mdx b/src/content/docs/images/optimization/transformations/overview.mdx
index 7de24256a768de1..d623c6694db1f47 100644
--- a/src/content/docs/images/optimization/transformations/overview.mdx
+++ b/src/content/docs/images/optimization/transformations/overview.mdx
@@ -11,8 +11,7 @@ products:
 import { Description, Render } from "~/components";
 
 <Description>
-	Transformations are requests to optimize and manipulate remote images that are
-	stored outside of Images.
+	Transformations are requests to optimize and manipulate remote images that are stored outside of Images.
 </Description>
 
 When you ship applications on Cloudflare, you can use Images to automatically optimize and cache your images from any origin.
diff --git a/src/content/docs/key-transparency/api/epochs.mdx b/src/content/docs/key-transparency/api/epochs.mdx
index 6aa0c01a45d12dd..d9a24544386e49e 100644
--- a/src/content/docs/key-transparency/api/epochs.mdx
+++ b/src/content/docs/key-transparency/api/epochs.mdx
@@ -49,7 +49,7 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}/audit
 - If `root` is defined for the namespace, the first epoch must match it (number and digest).
 - Epochs must be increasing. Second epoch is 2, third is 3, etc.
 - Epochs must have a unique digest or it will be rejected.
-- Epochs cannot be republished.
+- Epochs cannot be republished. 
 - Digest must be a 32 byte string hex encoded (length 64).
 
 If a namespace is disabled, you receive the following error:
diff --git a/src/content/docs/key-transparency/api/index.mdx b/src/content/docs/key-transparency/api/index.mdx
index 64b24fdf3146f9d..c390a1774ee252d 100644
--- a/src/content/docs/key-transparency/api/index.mdx
+++ b/src/content/docs/key-transparency/api/index.mdx
@@ -10,6 +10,6 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/key-transparency/api/namespaces.mdx b/src/content/docs/key-transparency/api/namespaces.mdx
index 055e97b897823f2..3e42e5b0a09d29b 100644
--- a/src/content/docs/key-transparency/api/namespaces.mdx
+++ b/src/content/docs/key-transparency/api/namespaces.mdx
@@ -20,8 +20,8 @@ The following fields are required when making a `POST` request:
 - `name`
 - `public`
 - `root`
-- `signature_version`:
-  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor
+- `signature_version`: 
+  - 0x0001 for [Protobuf serialisation](https://github.com/cloudflare/plexi/blob/main/plexi_core/src/proto/specs/types.proto) Ed25519 signature from the Auditor 
   - 0x0002 for [bincode serialisation](https://github.com/bincode-org/bincode/blob/trunk/docs/spec.md) E25519 serialisation by the Auditor
 
 The `log_directory` field is optional. If set, Cloudflare will use it to fetch audit proofs and validate them.
@@ -49,7 +49,6 @@ curl 'https://plexi.key-transparency.cloudflare.com/namespaces' \
 ```
 
 After publishing the first epoch, `status` will show `Online`. Possible statuses include:
-
 - `Online`
 - `Initialization`
 - `Disabled`
@@ -74,6 +73,7 @@ If a log state has been corrupted, lost, or needs to be sharded to be maintainab
 
 This API is authenticated via [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/).
 
+
 ```sh
 curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespace}' \
         	-H 'Content-Type: application/json' \
@@ -89,4 +89,4 @@ curl -X PATCH 'https://plexi.key-transparency.cloudflare.com/namespaces/{namespa
   "audits_uri": "/namespaces/your.new.log.com/audits",
   "signature_version": 1
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/kv/api/delete-key-value-pairs.mdx b/src/content/docs/kv/api/delete-key-value-pairs.mdx
index e8173282815e34f..f4275b10c635eef 100644
--- a/src/content/docs/kv/api/delete-key-value-pairs.mdx
+++ b/src/content/docs/kv/api/delete-key-value-pairs.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
@@ -22,24 +22,25 @@ An example of deleting a key-value pair from within a Worker:
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		try {
-			await env.NAMESPACE.delete("first-key");
-
-			return new Response("Successful delete", {
-				status: 200,
-			});
-		} catch (e) {
-			return new Response(e.message, { status: 500 });
-		}
-	},
+  async fetch(request, env, ctx) {
+    try {
+      await env.NAMESPACE.delete("first-key");
+
+      return new Response("Successful delete", {
+        status: 200
+      });
+    }
+    catch (e)
+    {
+      return new Response(e.message, {status: 500});
+    }
+  },
 };
 ```
 
 ## Reference
 
 The following method is provided to delete from KV:
-
 - [delete()](#delete-method)
 
 ### `delete()` method
@@ -52,13 +53,14 @@ env.NAMESPACE.delete(key);
 
 #### Parameters
 
-- `key`: `string`
-  - The key to associate with the value.
+* `key`: `string`
+  * The key to associate with the value.
 
 #### Response
 
-- `response`: `Promise<void>`
-  - A `Promise` that resolves if the delete is successful.
+* `response`: `Promise<void>`
+  * A `Promise` that resolves if the delete is successful.
+
 
 This method returns a promise that you should `await` on to verify successful deletion. Calling `delete()` on a non-existing key is returned as a successful delete.
 
@@ -73,5 +75,4 @@ Delete more than one key-value pair at a time with Wrangler or [via the REST API
 The bulk REST API can accept up to 10,000 KV pairs at once. Bulk writes are not supported using the [KV binding](/kv/concepts/kv-bindings/).
 
 ## Other methods to access KV
-
 You can also [delete key-value pairs from the command line with Wrangler](/kv/reference/kv-commands/#kv-namespace-delete) or [with the REST API](/api/resources/kv/subresources/namespaces/subresources/values/methods/delete/).
diff --git a/src/content/docs/kv/concepts/kv-bindings.mdx b/src/content/docs/kv/concepts/kv-bindings.mdx
index 1710c1db27c0aad..025824dc80e64ab 100644
--- a/src/content/docs/kv/concepts/kv-bindings.mdx
+++ b/src/content/docs/kv/concepts/kv-bindings.mdx
@@ -52,14 +52,14 @@ With this, the deployed Worker will have a `TODO` field in their environment obj
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		// Get the value for the "to-do:123" key
-		// NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
-		let value = await env.TODO.get("to-do:123");
-
-		// Return the value, as is, for the Response
-		return new Response(value);
-	},
+  async fetch(request, env, ctx) {
+    // Get the value for the "to-do:123" key
+    // NOTE: Relies on the `TODO` KV binding that maps to the "My Tasks" namespace.
+    let value = await env.TODO.get("to-do:123");
+
+    // Return the value, as is, for the Response
+    return new Response(value);
+  },
 };
 ```
 
@@ -97,13 +97,13 @@ An example might look like:
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-	constructor(ctx, env) {
-		super(ctx, env);
-	}
-
-	async fetch(request) {
-		const valueFromKV = await this.env.NAMESPACE.get("someKey");
-		return new Response(valueFromKV);
-	}
+  constructor(ctx, env) {
+    super(ctx, env);
+  }
+
+  async fetch(request) {
+    const valueFromKV = await this.env.NAMESPACE.get("someKey");
+    return new Response(valueFromKV);
+  }
 }
 ```
diff --git a/src/content/docs/kv/concepts/kv-namespaces.mdx b/src/content/docs/kv/concepts/kv-namespaces.mdx
index 0919c833f8ab666..7867efd8d6aaab6 100644
--- a/src/content/docs/kv/concepts/kv-namespaces.mdx
+++ b/src/content/docs/kv/concepts/kv-namespaces.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - kv
 ---
-
 import { Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 A KV namespace is a key-value database replicated to Cloudflare’s global network.
@@ -24,14 +23,17 @@ KV namespace IDs are public and bound to your account.
 
 To bind KV namespaces to your Worker, assign an array of the below object to the `kv_namespaces` key.
 
-- `binding` <Type text="string" /> <MetaInfo text="required" />
-  - The binding name used to refer to the KV namespace.
+* `binding` <Type text="string" /> <MetaInfo text="required" />
+
+  * The binding name used to refer to the KV namespace.
+
+* `id` <Type text="string" /> <MetaInfo text="required" />
 
-- `id` <Type text="string" /> <MetaInfo text="required" />
-  - The ID of the KV namespace.
+  * The ID of the KV namespace.
 
-- `preview_id` <Type text="string" /> <MetaInfo text="optional" />
-  - The ID of the KV namespace used during `wrangler dev`.
+* `preview_id` <Type text="string" /> <MetaInfo text="optional" />
+
+  * The ID of the KV namespace used during `wrangler dev`.
 
 Example:
 
@@ -57,7 +59,6 @@ To bind the namespace to your Worker in the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your **Worker**.
 3. Select **Settings** > **Bindings**.
 4. Select **Add**.
diff --git a/src/content/docs/kv/get-started.mdx b/src/content/docs/kv/get-started.mdx
index 2940849e4bb17a3..1087ab11b86e2ce 100644
--- a/src/content/docs/kv/get-started.mdx
+++ b/src/content/docs/kv/get-started.mdx
@@ -3,7 +3,7 @@ title: Getting started
 description: Create a KV namespace, write key-value pairs, and read data from Workers KV using Wrangler or the dashboard.
 pcx_content_type: get-started
 summary: |
-  Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
+    Create a basic key-value store which stores the notification configuration of all users in an application, where each user may have `enabled` or `disabled` notifications.
 reviewed: 2025-05-19
 sidebar:
   order: 2
@@ -11,18 +11,7 @@ products:
   - kv
 ---
 
-import {
-	Render,
-	PackageManagers,
-	Steps,
-	FileTree,
-	Details,
-	Tabs,
-	TabItem,
-	WranglerConfig,
-	GitHubCode,
-	DashButton,
-} from "~/components";
+import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem, WranglerConfig, GitHubCode, DashButton } from "~/components";
 
 Workers KV provides low-latency, high-throughput global storage to your [Cloudflare Workers](/workers/) applications. Workers KV is ideal for storing user configuration data, routing data, A/B testing configurations and authentication tokens, and is well suited for read-heavy workloads.
 
diff --git a/src/content/docs/kv/glossary.mdx b/src/content/docs/kv/glossary.mdx
index fca60dffa616ae9..6b9c8f69e63c1a2 100644
--- a/src/content/docs/kv/glossary.mdx
+++ b/src/content/docs/kv/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's KV documentation.
 
diff --git a/src/content/docs/kv/observability/index.mdx b/src/content/docs/kv/observability/index.mdx
index 8f1670df25b7b57..9f1c8fd90be7853 100644
--- a/src/content/docs/kv/observability/index.mdx
+++ b/src/content/docs/kv/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - kv
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/kv/observability/metrics-analytics.mdx b/src/content/docs/kv/observability/metrics-analytics.mdx
index 01ac3d93bddf26b..c341d12aa8f4c3c 100644
--- a/src/content/docs/kv/observability/metrics-analytics.mdx
+++ b/src/content/docs/kv/observability/metrics-analytics.mdx
@@ -32,7 +32,6 @@ Per-namespace analytics for KV are available in the Cloudflare dashboard. To vie
 1. In the Cloudflare dashboard, go to the **Workers KV** page.
 
    <DashButton url="/?to=/:account/workers/kv/namespaces" />
-
 2. Select an existing namespace.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/kv/platform/pricing.mdx b/src/content/docs/kv/platform/pricing.mdx
index e52462c5d821622..2fbcd27b1c0dc52 100644
--- a/src/content/docs/kv/platform/pricing.mdx
+++ b/src/content/docs/kv/platform/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - kv
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="kv_pricing" product="workers" />
 
diff --git a/src/content/docs/kv/reference/data-security.mdx b/src/content/docs/kv/reference/data-security.mdx
index 5c00ce589165eee..56ffef1944f609a 100644
--- a/src/content/docs/kv/reference/data-security.mdx
+++ b/src/content/docs/kv/reference/data-security.mdx
@@ -10,9 +10,9 @@ products:
 
 This page details the data security properties of KV, including:
 
-- Encryption-at-rest (EAR).
-- Encryption-in-transit (EIT).
-- Cloudflare's compliance certifications.
+* Encryption-at-rest (EAR).
+* Encryption-in-transit (EIT).
+* Cloudflare's compliance certifications.
 
 ## Encryption at Rest
 
diff --git a/src/content/docs/kv/reference/environments.mdx b/src/content/docs/kv/reference/environments.mdx
index dc41508ef498dcf..ef1e9305aea8aa3 100644
--- a/src/content/docs/kv/reference/environments.mdx
+++ b/src/content/docs/kv/reference/environments.mdx
@@ -68,6 +68,8 @@ Specifying an environment with the optional `--env` flag allows you to publish W
 
 For example, you could use separate staging and production KV namespaces for KV data in your Wrangler file:
 
+
+
 <WranglerConfig>
 
 ```jsonc
diff --git a/src/content/docs/kv/reference/kv-commands.mdx b/src/content/docs/kv/reference/kv-commands.mdx
index fe72655a36d9f3d..431cd3c20f17a6f 100644
--- a/src/content/docs/kv/reference/kv-commands.mdx
+++ b/src/content/docs/kv/reference/kv-commands.mdx
@@ -8,9 +8,9 @@ products:
   - kv
 ---
 
-import { Render } from "~/components";
+import {Render} from "~/components"
 
-<Render file="wrangler-commands/kv" product="workers" />
+<Render file="wrangler-commands/kv" product="workers"/>
 
 ## Deprecations
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
index 390d7d7727dc08f..e12e1fb27bbc69d 100644
--- a/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/audit-logs.mdx
@@ -5,7 +5,7 @@ pcx_content_type: overview
 sidebar:
   order: 5
   label: Audit Logs - v2
-  badge:
+  badge: 
     text: Beta
 description: Use the updated Audit Logs v2 interface.
 products:
diff --git a/src/content/docs/learning-paths/application-security/account-security/index.mdx b/src/content/docs/learning-paths/application-security/account-security/index.mdx
index 8bd856a5fcab2d3..cb51b549f91cf51 100644
--- a/src/content/docs/learning-paths/application-security/account-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/index.mdx
@@ -18,6 +18,6 @@ Make sure your account's security basics are configured properly.
 
 By the end of this module, you will be able to:
 
-- Secure your account
-- Understand and configure the most common settings for Cloudflare's Application Security Products
-- Explore advanced security products such as Bot Management and API Protection
+* Secure your account
+* Understand and configure the most common settings for Cloudflare's Application Security Products
+* Explore advanced security products such as Bot Management and API Protection
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
index 040aa06f0220922..7b0bddc7ba7917f 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-active-sessions.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="account-manage-active-sessions" product="fundamentals" />
 
diff --git a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
index f58aa925b394692..808ba2c05ca7dad 100644
--- a/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/review-audit-logs.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 :::note
 Audit Logs version 2 is available in beta. Refer to the [Audit Logs v2 documentation](/fundamentals/account/account-security/audit-logs/) for more details.
diff --git a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
index f7846d7a368fa45..29a6b9e44022824 100644
--- a/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
+++ b/src/content/docs/learning-paths/application-security/account-security/set-up-2fa.mdx
@@ -12,11 +12,11 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="2fa-overview" product="support" />
 
----
+***
 
 ## Enable 2FA
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
index d9d1cae9beaab73..2f7bec4ece18e95 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/browser-integrity.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="bic-description" product="waf" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
index 33a0732d1aa3a3e..6358ef403930629 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/ddos.mdx
@@ -12,10 +12,10 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare automatically detects and mitigates DDoS attacks using its [Autonomous Edge](/ddos-protection/about/components/#autonomous-edge), which is always-on. `Advanced` protections are reserved for Magic Transit customers.
 
 <Render file="ddos-attack-coverage" product="ddos-protection" />
 
-Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/) to dive deeper into this subject.
+Refer to the learning path [Prevent DDoS attacks](/learning-paths/prevent-ddos-attacks/concepts/)  to dive deeper into this subject.
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
index 636464957d64e91..d3c76bce71f7ce2 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/dnssec.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="dnssec-definition" product="dns" />
 
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
index 5432c5e8c039ee4..f9c577f4d3368d9 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/index.mdx
@@ -18,4 +18,4 @@ As soon as you onboard your domain to Cloudflare, you are automatically protecte
 
 By the end of this module, you will be able to:
 
-- Understand the most common security controls your applications will have access to
+* Understand the most common security controls your applications will have access to
diff --git a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
index 3d460f58056b631..a68ec976eb10fae 100644
--- a/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
+++ b/src/content/docs/learning-paths/application-security/default-traffic-security/mtls.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Mutual TLS (mTLS) authentication uses client certificates to ensure traffic between client and server is bidirectionally secure and trusted. mTLS also allows requests that do not authenticate via an identity provider — such as Internet-of-things (IoT) devices — to demonstrate they can reach a given resource.
 
diff --git a/src/content/docs/learning-paths/application-security/firewall/index.mdx b/src/content/docs/learning-paths/application-security/firewall/index.mdx
index 78fffa803dc49c0..6ee96f14dba91e6 100644
--- a/src/content/docs/learning-paths/application-security/firewall/index.mdx
+++ b/src/content/docs/learning-paths/application-security/firewall/index.mdx
@@ -18,5 +18,5 @@ Cloudflare's Web Application Firewall (WAF) is used to protect websites from a w
 
 By the end of this module, you will be able to:
 
-- Understand the different WAF components that Cloudflare offers
-- Understand the main features within each WAF offering
+* Understand the different WAF components that Cloudflare offers
+* Understand the main features within each WAF offering
diff --git a/src/content/docs/learning-paths/application-security/lists/configuration.mdx b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
index de13360e165d887..0a7cc2639adf13f 100644
--- a/src/content/docs/learning-paths/application-security/lists/configuration.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/configuration.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Both Custom and Managed Lists are located in the account settings. Refer to [Features by plan type](/learning-paths/application-security/lists/features/) for more information on plan eligibility.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/features.mdx b/src/content/docs/learning-paths/application-security/lists/features.mdx
index 4ea1c31ecbdd63e..96704045ef785d4 100644
--- a/src/content/docs/learning-paths/application-security/lists/features.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { FeatureTable, Render } from "~/components";
+import { FeatureTable, Render } from "~/components"
 
 List availability varies according to the list type and your Cloudflare plan and subscriptions.
 
diff --git a/src/content/docs/learning-paths/application-security/lists/index.mdx b/src/content/docs/learning-paths/application-security/lists/index.mdx
index 852a5c8744856ab..5278a33aaa568ba 100644
--- a/src/content/docs/learning-paths/application-security/lists/index.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/index.mdx
@@ -14,12 +14,12 @@ products:
 
 Cloudflare Lists is a WAF feature that enables administrators to groups identifiers together, such as IPs, hostnames or ASNs, and reference the list by other Cloudflare products such as [Custom rules](/waf/custom-rules/). Cloudflare currently supports the following types of lists:
 
-- [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
-- [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
+* [Custom Lists](/waf/tools/lists/custom-lists/): Includes custom IP lists, hostname lists, and ASN lists.
+* [Managed Lists](/waf/tools/lists/managed-lists/): Lists managed and updated by Cloudflare, such as Managed IP Lists.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Understand all the options Cloudflare's Lists products offer
-- Understand the advanced configurations provided to you with a paid offering
+* Understand all the options Cloudflare's Lists products offer
+* Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
index 9823a3c2fca778d..b14eddd109c6d34 100644
--- a/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/lists/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
index 21914e63f80aefc..ceee8008c0ec64e 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/configurations.mdx
@@ -14,14 +14,14 @@ products:
 
 Let's step through an example. If your `/create-account` page is being attacked, you will create a rule to limit the amount of requests, per `counting characteristic`, that you feel comfortable permitting through to your origin.
 
-The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, _after_ 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
+The rule below is being created on the `free` plan, which limits configuration options. The rule will trigger if the URI path matches `/create-account`, from the same IP address, *after* 5 requests and within a 10 second window, [within each Cloudflare datacenter](/waf/rate-limiting-rules/request-rate/), globally.
 
----
+***
 
 ![rate-limiting-create-account-endpoint](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint.png)
 ![rate-limiting-create-account-endpoint-block](~/assets/images/waf/rate-limiting-rules/rl-create-account-endpoint-block.png)
 
----
+***
 
 ## Advanced configuration
 
@@ -29,14 +29,14 @@ In the previous module, we reviewed the various configurations available per pla
 
 The rule below is being created on the `enterprise` plan, so we are no longer limited to default configurations.
 
-- The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
-- Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
-- Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
-- Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
+* The rule will also limit the number of requests to `/create-account`, but will only trigger against `POST` requests. In the basic example, even requests with the `GET` method will increment the counter.
+* Requests that do not have a [client certificate (mTLS)](/ssl/client-certificates/), will increment the counter.
+* Requests will be counted using the [IP with NAT support](/waf/rate-limiting-rules/parameters/#use-cases-of-ip-with-nat-support) characteristic.
+* Within a 1 minute period, for each counted entity, if the number of requests exceeds 10, then the user will be presented with a [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge) for a custom duration of 1 day.
 
 ![rate-limiting-advanced-config-1](~/assets/images/waf/rate-limiting-rules/rl-advanced-config.png)
 
----
+***
 
 ## Best practices
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
index 606b48b86302118..21aa7c300cdb961 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/features.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Rate limiting is composed of the following parameters:
 
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
index 45270f5ec40f21e..75a9a0e25347d72 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/index.mdx
@@ -18,5 +18,5 @@ Rate Limiting mitigates excessive request rates for specific URLs or for an enti
 
 By the end of this module, you will be able to:
 
-- Understand all the options Cloudflare's Rate Limiting product offers
-- Understand the advanced configurations provided to you with a paid offering
+* Understand all the options Cloudflare's Rate Limiting product offers
+* Understand the advanced configurations provided to you with a paid offering
diff --git a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
index 81787364edb5b8b..7eb7c2accedce4b 100644
--- a/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
+++ b/src/content/docs/learning-paths/application-security/rate-limiting/use-cases.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The most common uses cases are:
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
index 2533b2fabe4489e..06d7cf0e3aa85f1 100644
--- a/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/brand-protection.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="brand-protection-definition" product="security-center" />
 
diff --git a/src/content/docs/learning-paths/application-security/security-center/index.mdx b/src/content/docs/learning-paths/application-security/security-center/index.mdx
index 443cd3864fd9da6..3c114e0c0f9d8d6 100644
--- a/src/content/docs/learning-paths/application-security/security-center/index.mdx
+++ b/src/content/docs/learning-paths/application-security/security-center/index.mdx
@@ -12,7 +12,7 @@ products:
   - security-center
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="security-center-definition" product="security-center" />
 
@@ -20,5 +20,5 @@ import { Render } from "~/components";
 
 By the end of this module, you will be able to:
 
-- Understand the primary Security Center features such as Security Insights and Brand Protection
-- Review and manage security risks at the account level, encompassing all of your domains in one unified view
+* Understand the primary Security Center features such as Security Insights and Brand Protection
+* Review and manage security risks at the account level, encompassing all of your domains in one unified view
diff --git a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
index 9ce422510bb4427..54e046c2db79eed 100644
--- a/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/access-application/index.mdx
@@ -16,7 +16,7 @@ Now that you have [connected your private applications](/learning-paths/clientle
 
 By the end of this module, you will be able to:
 
-- Add your application to Cloudflare Access.
-- Create an Access policy.
-- Design reusable policies.
-- Design a domain structure for your applications.
+* Add your application to Cloudflare Access.
+* Create an Access policy.
+* Design reusable policies.
+* Design a domain structure for your applications.
diff --git a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
index 5450985227dcb8e..38a2051d7e24d98 100644
--- a/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/advanced-workflows/index.mdx
@@ -16,7 +16,7 @@ Configure advanced Access policies to meet the specific requirements of your app
 
 By the end of this module, you will be able to:
 
-- Check identity-based attributes that are not directly supported by the Access policy builder.
-- Deliver sensitive web applications in an isolated browser.
-- Apply Gateway HTTP policies without a device client.
-- Connect to applications using their private hostnames without a device client.
+* Check identity-based attributes that are not directly supported by the Access policy builder.
+* Deliver sensitive web applications in an isolated browser.
+* Apply Gateway HTTP policies without a device client.
+* Connect to applications using their private hostnames without a device client.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
index ba3876cbb069c62..700dfb2c429be48 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/clientless-rbi.mdx
@@ -27,6 +27,6 @@ To configure Clientless Web Isolation to augment clientless access, refer to [th
 
 ## Best practices
 
-- For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
-- If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
-- You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
+* For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
+* If you already deployed the Cloudflare One Client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
+* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
diff --git a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
index 3d6978794492877..236369d2c8ea5d8 100644
--- a/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/alternative-onramps/index.mdx
@@ -10,10 +10,10 @@ products:
   - cloudflare-one
 ---
 
-As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access. However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
+As discussed in the previous modules, almost everything you do with the Cloudflare reverse proxy requires [adding a site](/learning-paths/clientless-access/initial-setup/add-site/) to Cloudflare. That public DNS record (or its subdomains) becomes the domain on which your users access your private applications. This method is exceptionally secure and transparent; each domain and subdomain has access to the Cloudflare web security portfolio, are inherently DDoS protected, and receive an obfuscated origin IP. For these reasons, using a [public hostname on Cloudflare](/learning-paths/clientless-access/connect-private-applications/) is the recommended method to onboard applications for clientless user access.  However, there may be times in which a public DNS record cannot be created, or other situations that prevent administrators from using this method.
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Connect to private web applications using their private hostnames.
+* Connect to private web applications using their private hostnames.
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
index 96467fa3ad74ab3..1c76266d3e00159 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/index.mdx
@@ -16,4 +16,4 @@ Review the concepts behind clientless access.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose and benefits of clientless access.
+- Understand the purpose and benefits of clientless access.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
index 9b3e4a2a40a5b80..446f1e1c72913e7 100644
--- a/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
+++ b/src/content/docs/learning-paths/clientless-access/concepts/what-is-clientless-access.mdx
@@ -12,7 +12,7 @@ products:
 
 Clientless access is a deployment option of a [Zero Trust Network Access (ZTNA)](https://www.cloudflare.com/learning/access-management/what-is-ztna/) service that provides secure access to internal applications without requiring end users to install any software. Users access corporate resources like intranet web apps, SSH terminals, and Windows servers through RDP from their web browser. Clientless access is commonly used to provide internal, [least-privilege access](https://www.cloudflare.com/learning/access-management/principle-of-least-privilege/) to users on unmanaged devices. Users may include third-party contractors, suppliers, and partners, or employees using personal mobile phones as part of an organization's bring-your-own-device (BYOD) policy.
 
-IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as preventing uploads/downloads or copy/paste, or incorporating DLP policies.
+IT/security admins can decide how users authenticate, whether through their corporate identity provider, social media accounts, a PIN sent to their email, strong MFA, or a combination of options. Admins can also add inline services like Remote Browser Isolation (RBI) and Data Loss Prevention (DLP) to help prevent data exfiltration from unmanaged devices, still through a clientless implementation. Isolated apps can enforce broad data controls through the browser, such as  preventing uploads/downloads or copy/paste, or incorporating DLP policies.
 
 ## Alternatives to clientless access
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
index 7eb4c09d0ecbf01..7015fc5b6c802b5 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/best-practices.mdx
@@ -20,9 +20,9 @@ For an additional point of availability, add a [`cloudflared` replica](/cloudfla
 
 To make your applications easier to manage, standardize the public hostnames that you publish your applications on. Here are a few examples of how customers manage their public hostnames:
 
-- Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
-- If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
-- Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
+* Delegate a subdomain of your primary public website to use for internal applications (for example, `tools.dev.customer.com`).
+* If your internal DNS infrastructure is available for public use, register your internal primary DNS record on Cloudflare and use this domain for your public hostname routes. This allows you to present applications on identical private and public hostnames.
+* Specify some sort of internal logic that generates hostnames based on the type of tool you are connecting. For example, if you have a set of applications in a US-East datacenter allocated explicitly for production resources, you could create subdomains of `tools.us-east.prod.ztproject.com`.
 
 ## Disable TLS verification
 
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
index 9c6cbcd138686f2..3120d43f30efdce 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To enable clientless access to your applications, you will need to create a Cloudflare Tunnel that publishes applications to a domain on Cloudflare. A published application creates a public DNS record that routes traffic to a specific address, protocol, and port associated with a private application. For example, you can define a public hostname (`mywebapp.example.com`) to provide access to a web server running on `https://localhost:8080`. When a user goes to `mywebapp.example.com` in their browser, their request will first route to a Cloudflare data center where it is inspected against your configured security policies. Cloudflare will then forward validated requests down your tunnel to the web server.
 
@@ -32,8 +32,9 @@ All users on the Internet can now connect to this application via its public hos
 
 If the tunnel is disconnected:
 
-- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+
 
 :::
 
@@ -41,5 +42,5 @@ If the tunnel is disconnected:
 
 For more control over how traffic routes through your tunnel, refer to the following links:
 
-- [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
-- [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
+* [DNS records](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/)
+* [Load balancer](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers/)
diff --git a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
index 4f9337b3961247c..fe443c8a8e5c306 100644
--- a/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/connect-private-applications/index.mdx
@@ -16,5 +16,5 @@ Cloudflare Tunnel allows you to securely connect your applications to Cloudflare
 
 By the end of this module, you will be able to:
 
-- Create a Cloudflare Tunnel.
-- Publish your application via a public hostname.
+* Create a Cloudflare Tunnel.
+* Publish your application via a public hostname.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
index a14fda563a6432d..49e6a3bcf50f75b 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/app-launcher.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/app-launcher" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
index 3de4f9ba2ef5141..3f202ae036ff2e9 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/block-page.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/block-page" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
index 6a740a977e9de4c..23e9d4431ca5719 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/bookmarks.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/bookmarks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
index 01df3d80b023dd8..681cb50fbfb8882 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/index.mdx
@@ -16,7 +16,7 @@ Cloudflare Access offers several ways to customize the look and feel of the user
 
 By the end of this module, you will be able to:
 
-- Configure the App Launcher so that users can open all applications from single dashboard.
-- Add bookmarks to the App Launcher for applications that are not behind Access.
-- Customize the Access login page with your organization's branding.
-- Display custom block pages when a user is blocked by your Access policies.
+* Configure the App Launcher so that users can open all applications from single dashboard.
+* Add bookmarks to the App Launcher for applications that are not behind Access.
+* Customize the Access login page with your organization's branding.
+* Display custom block pages when a user is blocked by your Access policies.
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
index b04f07439a4c9c8..0784ac3db460bb8 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/login-page.mdx
@@ -10,7 +10,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The Access login page is where users select their identity provider (IdP) or One-Time PIN prior to accessing the application. Customers who only use one IdP usually enable **Apply instant authentication** for their applications, which redirects end users directly to the SSO login page. If you are using multiple IdPs, we recommend customizing the Access login page to match your branding and minimize user confusion.
 
diff --git a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
index 65bd38ce4da91e9..6b8b7f8ee3ace2f 100644
--- a/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
+++ b/src/content/docs/learning-paths/clientless-access/customize-ux/tags.mdx
@@ -10,6 +10,6 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="access/tags" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
index 0348346f1053ba1..bf6be752e98fce7 100644
--- a/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/initial-setup/index.mdx
@@ -18,7 +18,7 @@ If you need to deliver access to non-browser based applications, refer to our co
 
 By the end of this module, you will be able to:
 
-- Set up a Cloudflare account.
-- Add your domain to Cloudflare.
-- Create a Zero Trust organization to manage applications and policies.
-- Configure an identity provider (IdP) for user authentication.
+* Set up a Cloudflare account.
+* Add your domain to Cloudflare.
+* Create a Zero Trust organization to manage applications and policies.
+* Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
index f519cc3082b5669..238af10cab095cb 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/best-practices.mdx
@@ -12,10 +12,10 @@ products:
 
 Most customers have a heterogeneous private application portfolio; some are home-built, some are internal managed services, some have SSO integrations available, and some rely on HTML or other forms of authentication. With that in mind, we recommend that you mix-and-match [onboarding solutions](/learning-paths/clientless-access/migrate-applications/integrated-sso/#potential-solutions) to fit the needs of each individual application. As shown in the table below, you can bucket applications into a series of stack-ranked categories that prioritize ease of implementation and total organizational impact.
 
-| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                         | Outcome                                                                                                                                                                                                                                                  |
-| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                 |
-| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                         |
-| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                 |
-| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.          | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
-| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                             | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                 |
+| Application type                                                                                     | Recommendation                                                                                                                                                                                                                                                                                                                                             | Outcome                                                                                                                                                                                                                                                      |
+| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Private web apps without integrated SSO                                                              | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Users access applications on new domains delegated to Cloudflare and instantly apply SSO through Cloudflare integration.                                                                                                                                     |
+| Private web apps with integrated SSO                                                                 | **If SSO configuration is possible:** [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> **If SSO configuration is not possible:** Present applications on existing internal domains with identical external domains delegated to Cloudflare | Users access internal web services on the same or new domains from Cloudflare. If configured, the SSO provider transparently redirects users from internal domains to Cloudflare authoritative external domains.                                             |
+| New critical internal applications being developed                                                   | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution)                                                                                                                                                                                                 | Developers can programmatically generate (or be given) new public hostnames on Cloudflare to represent the redirects for their application in SAML or OIDC integrations.                                                                                     |
+| New microservices being developed                                                                    | [Present applications exclusively on Cloudflare domains.](/learning-paths/clientless-access/migrate-applications/integrated-sso/#recommended-solution) <br/> Optionally, [consume the Access JWT](/learning-paths/clientless-access/migrate-applications/consume-jwt/#consume-the-cloudflare-jwt) as authentication in internal applications.      | Developers can inject the JWT authorization mechanism directly into the codebase of their application and [use Terraform](/learning-paths/clientless-access/terraform/) to automatically build Cloudflare hostnames and policies for their applications. |
+| Internal API endpoints (including internal applications with dependencies on external/internal APIs) | Present internal APIs on Cloudflare domains, and build Access policies that accept [service tokens](/cloudflare-one/access-controls/service-credentials/service-tokens/) alongside user-oriented policies.                                                                                                                                                                            | Automated systems can authenticate via a [service token in the request header](/cloudflare-one/access-controls/service-credentials/service-tokens/#connect-your-service-to-access), while end users continue to login through their IdP.                                                |
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
index 9221ff52404a5f0..87fd2e5aafa3f63 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/index.mdx
@@ -21,6 +21,6 @@ The remaining modules (Modules 6-9) discuss special considerations and setup opt
 
 By the end of this module, you will be able to:
 
-- Manage applications that are directly integrated with an identity provider.
-- Pass user information from Cloudflare Access to your application.
-- Review best practices for onboarding different types of internal applications.
+* Manage applications that are directly integrated with an identity provider.
+* Pass user information from Cloudflare Access to your application.
+* Review best practices for onboarding different types of internal applications.
diff --git a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
index 237820c4e1c9ca7..05491e91bbf7537 100644
--- a/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
+++ b/src/content/docs/learning-paths/clientless-access/migrate-applications/integrated-sso.mdx
@@ -31,12 +31,12 @@ app.internal.com")
 
 If your applications use integrated SSO, there are a number of different paths you can take to onboard your applications to Cloudflare Access.
 
-| Solution                                                                                                                   | Steps required                                                                                                      | Pros                                                                                                                                                                        | Cons                                                                                                                     |
-| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                            | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                         | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
-| Present applications on existing internal domains with identical external domains delegated to Cloudflare                  | Add domains to Cloudflare that match internal domains                                                               | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
-| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li>  | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
-| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                   | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/) | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
+| Solution                                                                                                                       | Steps required                                                                                                     | Pros                                                                                                                                                                        | Cons                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| [Present applications exclusively on Cloudflare domains](#recommended-solution)                                                | Change SSO ACS URL to the Cloudflare Tunnel public hostname                                                        | <li> Increased security posture </li> <li> No changes to application code</li> <li> No changes to internal DNS design </li>                                                 | Hard cutover event when ACS URL changes from internal to external domain                                                 |
+| Present applications on existing internal domains with identical external domains delegated to Cloudflare                      | Add domains to Cloudflare that match internal domains                                                              | <li> No changes to SSO ACS URL </li> <li> No change for end users </li>                                                                                                     | <li> Requires careful management of internal and external domains </li> <li> Requires changing internal DNS design </li> |
+| [Consume the Cloudflare JWT in internal applications](/learning-paths/clientless-access/migrate-applications/consume-jwt/) | <li> Remove integrated SSO </li> <li> Update application to accept the Cloudflare JWT for user authorization </li> | <li> Reduced authentication burden for end users </li> <li> No changes to internal DNS design </li> <li> Instantly secure applications without direct SSO integration </li> | <li> Requires changing application code </li> <li> Hard cutover event when application updates </li>                     |
+| Use Cloudflare as the direct SSO integration, which then calls your IdP of choice (Okta, OneLogin, etc.)                       | Swap existing SSO provider for [Access for SaaS](/cloudflare-one/access-controls/applications/http-apps/saas-apps/)           | <li> Increased flexibility for changing IdPs </li> <li> Ability to use multiple IdPs simultaneously </li>                                                                   | <li> Hard cutover event for IdP changes </li> <li> No SCIM provisioning for application </li>                            |
 
 ## Recommended solution
 
diff --git a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
index 596225f3171052b..7412e5a55b1652c 100644
--- a/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
+++ b/src/content/docs/learning-paths/clientless-access/terraform/index.mdx
@@ -16,4 +16,4 @@ Integrate Cloudflare Access into your private application development pipeline.
 
 By the end of this module, you will be able to:
 
-- Publish internal applications to Cloudflare using Terraform.
+* Publish internal applications to Cloudflare using Terraform.
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
index 1e092ce574856b2..69453ef2d875700 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/create-zero-trust-org.mdx
@@ -11,7 +11,7 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To set up a Zero Trust organization:
 
diff --git a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
index c0853f8ed750a7f..721649155e70883 100644
--- a/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/account-creation/index.mdx
@@ -16,6 +16,6 @@ Get started by creating a Cloudflare account and initializing the Zero Trust and
 
 By the end of this module, you will have:
 
-- Created a Cloudflare account.
-- Initialized the Zero Trust dashboard.
-- Initialized the Area 1 dashboard.
+* Created a Cloudflare account.
+* Initialized the Zero Trust dashboard.
+* Initialized the Area 1 dashboard.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
index c6dc2bacee257d2..098f42bdf6a93f6 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/index.mdx
@@ -16,7 +16,7 @@ Learn the technical concepts behind Project Cybersafe Schools.
 
 By the end of this module, you will be able to:
 
-- Understand the purpose of the Children’s Internet Protection Act (CIPA).
-- Describe the life of a DNS request.
-- Explain how DNS filtering works to control which websites users can access.
-- Understand the benefits of protecting your email inbox.
+* Understand the purpose of the Children’s Internet Protection Act (CIPA).
+* Describe the life of a DNS request.
+* Explain how DNS filtering works to control which websites users can access.
+* Understand the benefits of protecting your email inbox.
diff --git a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
index c7e8ff61a49fecf..af663840fbd1be0 100644
--- a/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
+++ b/src/content/docs/learning-paths/cybersafe/concepts/what-is-dns-filtering.mdx
@@ -16,9 +16,9 @@ DNS filtering is a technique to block access to websites or online content. DNS
 
 DNS filtering is commonly used to:
 
-- Protect school data from phishing, ransomware, and malware.
-- Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
-- Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
+* Protect school data from phishing, ransomware, and malware.
+* Block websites that go against school acceptable use policy, such as adult content, gambling, and piracy.
+* Restrict access to websites that may impact student productivity, such as gaming, social media, and video streaming.
 
 ## How DNS filtering works
 
@@ -52,17 +52,17 @@ DNS filtering only applies to the hostname — `subdomain.domain.tld`. You canno
 
 Secure Web Gateways (SWGs) offer a greater set of capabilities, including:
 
-- [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
-- L4 firewalls to block ports and protocols
-- Antivirus scanning
-- [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
-- [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
+* [URL filtering](https://www.cloudflare.com/learning/access-management/what-is-url-filtering/) to block specific paths and queries
+* L4 firewalls to block ports and protocols
+* Antivirus scanning
+* [Data loss prevention](https://www.cloudflare.com/learning/access-management/what-is-dlp/)
+* [Browser isolation](https://www.cloudflare.com/learning/access-management/what-is-browser-isolation/)
 
 However, this can make SWGs more complex to deploy. Therefore, many organizations will start with DNS filtering as an initial layer of defense against Internet threats.
 
 ## Related resources
 
-- For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
+* For more background information on DNS filtering, refer to our [Learning Center](https://www.cloudflare.com/learning/access-management/what-is-dns-filtering/).
 
 ## Next steps
 
diff --git a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
index c3c1b8bad4a14a0..75e5801177a4b47 100644
--- a/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
+++ b/src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-verify-local-connectivity.mdx
@@ -10,12 +10,8 @@ products:
   - cloudflare-one
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To verify that your DNS traffic is sent to Gateway:
 
-<Render
-	file="gateway/verify-connectivity"
-	product="cloudflare-one"
-	params={{ one: "DNS", two: "queries" }}
-/>
+<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
diff --git a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
index eb3666dd5133b61..b47b3a80514a788 100644
--- a/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/advertise-prefixes.mdx
@@ -11,4 +11,4 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="magic-transit/advertise-prefixes" product="networking-services" />
+<Render file="magic-transit/advertise-prefixes"	product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
index 49959caa851cad4..6d99098e5ffbd39 100644
--- a/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/concepts/index.mdx
@@ -14,6 +14,6 @@ Learn core concepts about Magic Transit and its functionality, in order to prote
 ## Objectives
 
 By the end of this module you will be able to:
-
 - Understand what Magic Transit is
 - Why you should use it to protect your IP network
+
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
index a62c27d80ec53ce..96178b835574113 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-ddos.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare DDoS protection automatically detects and mitigates Distributed Denial of Service (DDoS) attacks using its Autonomous Edge. Magic Transit customers have access to additional features, such as:
 
@@ -26,10 +26,7 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/tcp-protection-intro" product="ddos-protection" />
 
-<Render
-	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
-	product="ddos-protection"
-/>
+<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
 
 #### Setup
 
@@ -39,11 +36,8 @@ Cloudflare DDoS protection automatically detects and mitigates Distributed Denia
 
 <Render file="advanced-ddos/dns-protection-intro" product="ddos-protection" />
 
-<Render
-	file="advanced-ddos/mt-advanced-ddos-systems-onboarding"
-	product="ddos-protection"
-/>
+<Render file="advanced-ddos/mt-advanced-ddos-systems-onboarding" product="ddos-protection" />
 
 #### Setup
 
-<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
+<Render file="advanced-ddos/dns-setup" product="ddos-protection" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
index 51c5f4f2f692123..482c2b215ae173f 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx
@@ -9,7 +9,7 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -19,16 +19,12 @@ import { Render } from "~/components";
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT:
-			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table",
+		routingTableName: "Magic Transit Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
index bd53e3d65b54e92..4c93f4789229aab 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
@@ -11,31 +11,22 @@ products:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
-	}}
-/>
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
+	}} />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
index b98f8551ad40475..6f1888d2fbbff7e 100644
--- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/index.mdx
@@ -14,6 +14,6 @@ In this unit you will learn how to set up tunnels and routes to steer traffic.
 ## Objectives
 
 By the end of this module you will be able to:
-
 - Create tunnels on both the Cloudflare side and your router side to connect to your infrastructure.
 - Configure static routes or dynamic routes with BGP peering to steer your traffic via next-hop from Cloudflare's global network to your connected networks.
+
diff --git a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
index 40adf54d7baae5f..1efb22a01b5feef 100644
--- a/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/enable-notifications.mdx
@@ -17,8 +17,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation:
-			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
@@ -33,4 +32,4 @@ Cloudflare also recommends that you enable the following account notifications f
 - (Optional) Advanced Layer 3/4 DDoS Attack Alert
 - (Optional) Cloudflare status - Maintenance Notification (in case you want to be alerted regarding maintenance in specific Cloudflare data centers).
 
-Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
+Refer to [Cloudflare Notifications](/notifications/) for more information on how to enable these notifications.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/get-started.mdx b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
index 16b63ff273ced89..58e23aba7e9451b 100644
--- a/src/content/docs/learning-paths/data-center-protection/get-started.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/get-started.mdx
@@ -9,10 +9,6 @@ products:
   - ddos-protection
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/get-started"
-	product="networking-services"
-	params={{ magicWord: "Learning Path" }}
-/>
+<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Learning Path" }} />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
index 88f72d32072ad16..7d6e4bdd8b5ba93 100644
--- a/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/run-pre-flight-checks.mdx
@@ -10,7 +10,6 @@ products:
 ---
 
 After setting up your Magic Transit product, Cloudflare validates:
-
 - Tunnel connectivity
 - Tunnel and endpoint [health checks](/magic-transit/reference/tunnel-health-checks/#types-of-health-checks)
 - Letter of Agency (LOA)
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
index efe4d0f80aa7a93..4b7ab7651839800 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/index.mdx
@@ -14,7 +14,7 @@ Migrating your DNS from an on-premises BIND solution to a cloud-based provider l
 
 By the end of this module, you will be able to:
 
-- Plan and take inventory of your DNS migration.
-- Prepare for the migration with minimal downtime.
-- Learn how to make the actual switch to Cloudflare.
-- Verify and stabilize after your migration.
+* Plan and take inventory of your DNS migration.
+* Prepare for the migration with minimal downtime.
+* Learn how to make the actual switch to Cloudflare.
+* Verify and stabilize after your migration.
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
index ac9f126e6cfb046..05eae75787849b0 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-1.mdx
@@ -12,55 +12,55 @@ Detailed planning is the cornerstone of a successful DNS migration.
 
 ## 1. Understand your current BIND setup
 
-1. Identify all DNS zones currently hosted on your BIND servers.
-2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.
-3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.
-   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.
+1. Identify all DNS zones currently hosted on your BIND servers.  
+2. Review all DNS records within each zone. Remove stale or unnecessary records and verify the accuracy of existing records.  
+3. BIND views (split DNS): If you use BIND views to provide different DNS responses to internal versus external resolvers, Cloudflare authoritative DNS does not replicate per-client views directly.  
+   - Continue to use an internal DNS resolver (for example, BIND, Active Directory, or another internal resolver) for internal-only names, while using Cloudflare authoritative DNS for public zones.  
    - For policy-based internal DNS, consider Cloudflare Zero Trust features such as DNS policies and Internal DNS (Beta). For more details, refer to [Cloudflare DNS](/dns/) and [Internal DNS](/dns/internal-dns/).
-4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:
-   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.
-   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.
-   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:
-     - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)
-     - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)
+4. BIND ACLs (access control lists): If you use ACLs in BIND to restrict which clients can query your authoritative DNS or perform zone transfers, plan how these controls will change:  
+   - **Authoritative DNS queries:** Cloudflare authoritative DNS nameservers are reachable on the public Internet and do not support per-resolver ACLs for standard DNS queries.  
+   - **HTTP and application access:** To restrict or filter HTTP(S) traffic to your applications, use Cloudflare security features such as the [Web Application Firewall (WAF)](/waf/) and other Application Security products. These operate at the HTTP layer, not at the DNS query layer.  
+   - Zone transfers (AXFR/IXFR): If you use AXFR/IXFR with BIND today, review Cloudflare’s zone transfer setups:  
+      - [Cloudflare as primary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-primary/)  
+      - [Cloudflare as secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/)  
 
-     These setups document how to restrict which IP addresses can perform zone transfers.
+      These setups document how to restrict which IP addresses can perform zone transfers.
 
-5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.
+5. Dependencies: Identify any applications or services critically dependent on specific DNS behaviors of your BIND setup.  
 
 ## 2. Define scope and objectives
 
-Clearly list all domain names to be migrated and define success criteria for the migration.
+Clearly list all domain names to be migrated and define success criteria for the migration.  
 
 ## 3. Cloudflare account and familiarization
 
-1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.
-2. Familiarize yourself with the Cloudflare DNS dashboard and its features.
+1. [Create your Cloudflare account](/fundamentals/account/create-account/) if you have not already.  
+2. Familiarize yourself with the Cloudflare DNS dashboard and its features.  
 3. Consider the different [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) you can manage on Cloudflare and how they map from BIND.
 
 ## 4. DNSSEC strategy (critical)
 
-Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.
+Determine if DNSSEC is currently enabled for your zones on BIND and at your domain registrar.  
 
-Cloudflare supports two main migration approaches when DNSSEC is enabled:
+Cloudflare supports two main migration approaches when DNSSEC is enabled: 
 
-- Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.
-- Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+   - Option 1 (recommended for most migrations): [Disable DNSSEC at your registrar](/dns/dnssec/#disable-dnssec) before changing nameservers. After the migration to Cloudflare is complete and stable, re-enable DNSSEC through the Cloudflare dashboard.  
+   - Option 2 (advanced): Perform an active migration using [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/setup/), where both providers sign the zone during the transition. This requires careful key management but allows you to migrate without disabling DNSSEC. For more information, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).  
 
-**Disable-and-re-enable approach (safer for most teams):**
+**Disable-and-re-enable approach (safer for most teams):**  
 
-1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.
-2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.
+1. Log in to your registrar and remove the DS records associated with your on-prem BIND DNSSEC keys for each domain.  
+2. Plan to switch nameservers only after resolvers are no longer expecting the old DNSSEC chain.  
 
-\*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.
+*DS record TTL: If DNSSEC is active, note the Time To Live (TTL) of your DS records at the parent zone (managed by your registrar). This will determine how long you need to wait after removing DS records. As a rule of thumb, wait at least one full DS TTL and preferably up to 1.5 times the TTL before changing nameservers.  
 
 For more information about DNSSEC on Cloudflare, refer to [DNSSEC](/dns/dnssec/).
 
 ## 5. Choose migration window
 
-Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.
+Select a period of low traffic and activity to minimize potential impact and inform stakeholders of the planned window.  
 
 ## 6. Develop communication and rollback plan
 
-- Communication: Plan how to communicate with stakeholders before, during, and after the migration.
-- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
+- Communication: Plan how to communicate with stakeholders before, during, and after the migration.  
+- Rollback Plan: Document steps to revert to your BIND servers if major issues arise. This primarily involves changing nameservers back at the registrar and potentially re-adding old DS records if DNSSEC was involved.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
index b3b2d045d7021ec..f53af665ca87cfd 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-2.mdx
@@ -14,49 +14,49 @@ Careful preparation will minimize downtime and issues during the cutover.
 
 ## 1. Reduce DNS record TTLs (Time To Live)
 
-At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).
+At least 24-48 hours (or longer, ideally matching your longest current TTLs) before your planned migration window, lower the TTLs for all critical records in your BIND zone files. A common short TTL for migration is 300 seconds (5 minutes).  
 
-This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.
+This ensures that DNS resolvers worldwide will cache your old records for a shorter period, allowing changes to propagate more quickly when you switch to Cloudflare.  
 
-- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).
+- SOA Record: Also consider lowering the `MINIMUM` field in your SOA record, which dictates the TTL to be used for negative responses ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308.html#section-4)).  
 
 ## 2. Export zone files from BIND
 
-Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.
+Obtain a clean and current export of your zone files from your BIND servers in standard BIND format and ensure these files are complete and accurate.  
 
 ## 3. Add domains to Cloudflare
 
-1. Log in to your Cloudflare dashboard.
+1. Log in to your Cloudflare dashboard.  
 
    <DashButton url="/?to=/:account/home" />
 
-2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.
+2. Add each domain you intend to migrate. Cloudflare will attempt to scan for existing DNS records.  
 
 ## 4. Import DNS Records into Cloudflare
 
-Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.
-
-<DashButton url="/?to=/:account/home" />
+Use Cloudflare's **Import and Export** feature (under **DNS** > **Records**) to upload your BIND zone files.  
+   
+   <DashButton url="/?to=/:account/home" />
 
-- Verification (Crucial):
-  - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.
-  - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.
-  - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).
-- Proxy status (orange vs grey cloud):
-  - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.
-  - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).
-  - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
+- Verification (Crucial): 
+   - After import, meticulously compare the records in Cloudflare with your BIND zone files or a `dig` output of your current zone.  
+   - Pay close attention to `MX` records, `SRV` records, `TXT` records (especially for `SPF`, `DKIM`, `DMARC`), and any complex `CNAME` configurations.  
+   - Ensure FQDNs (Fully Qualified Domain Names) are correctly formatted (Cloudflare usually handles the trailing dot correctly on import, but verify).  
+- Proxy status (orange vs grey cloud):  
+   - For `A`, `AAAA`, and `CNAME` records that point to HTTP or HTTPS services you want to proxy through Cloudflare (for example, websites and APIs), you can enable the orange cloud to use Cloudflare CDN and security features.  
+   - Some services and ports are not supported behind the proxy, and certain record types (for example, `MX` targets and many non-HTTP services) must remain **DNS only**. For a detailed list, refer to [Proxy status and limitations](/dns/proxy-status/limitations/).  
+   - Recommendation for initial migration: To isolate the DNS migration from potential proxy-related issues, consider setting all records to **DNS only** (grey cloud) initially. After you confirm that DNS resolution is working correctly, enable the proxy (orange cloud) for specific HTTP(S) records and test again.
 
 ## 5. DNSSEC preparation (if currently enabled)
 
-Complete this step before you change your nameservers at the registrar.
+Complete this step before you change your nameservers at the registrar.  
 
 :::note
 
-For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy, refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
+For more detailed guidance, refer to [DNSSEC](/dns/dnssec/). If during [Phase 1](/learning-paths/dns-best-practices/concepts/phase-1/#4-dnssec-strategy-critical) you have opted for a multi-signer DNSSEC strategy,  refer to [Migrate an existing zone with DNSSEC enabled](/dns/dnssec/dnssec-active-migration/).
 
 :::
 
-- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.
+- **Action at registrar:** Log in to your domain registrar and delete the existing DS records associated with your on-prem BIND DNSSEC keys for each domain.  
 - **Wait for DS TTL:** Wait at least the full DS record TTL published at the parent zone, and preferably up to 1.5 times that TTL, before you change nameservers. This ensures that validating resolvers stop expecting the old DNSSEC chain. The typical TTL duration for DS records is set to +24 hours (86,400 seconds).
-- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.
+- **Impact of incorrect timing:** If you change nameservers while resolvers still expect the old DS record, DNSSEC validation will fail and your domain may become unreachable for validating resolvers.  
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
index 1decb20de5cda62..7307e676b28660a 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-3.mdx
@@ -12,29 +12,30 @@ Phase 3 is when you make the actual switch to Cloudflare.
 
 ## 1. Final verification
 
-Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.
+Complete one last check of all DNS records in your Cloudflare dashboard for accuracy and ensure your BIND servers are still operational as a fallback if needed.  
 
 ## 2. Update nameservers at your registrar
 
-1.  Log in to your domain registrar's control panel for each domain.
-2.  Navigate to the section for managing nameservers.
-3.  Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.
-4.  Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).
-5.  Save the changes.
+   1. Log in to your domain registrar's control panel for each domain.  
+   2. Navigate to the section for managing nameservers.  
+   3. Replace your current on-prem BIND nameserver entries with your Cloudflare nameservers.  
+   4. Add the Cloudflare nameservers assigned to your domain (Cloudflare will provide at least two).  
+   5. Save the changes.  
 
 ## 3. Monitor propagation
 
-- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).
-- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.
-  - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)
-  - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
-  - `whois yourdomain.com`
-  - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
-  You are looking for the Cloudflare nameservers to be reported consistently.
+- DNS nameserver changes can take time to propagate globally, typically anywhere from a few minutes to 48 hours (though often much faster due to lowered TTLs).  
+- Use the commands exemplified below, replacing `yourdomain.com` by your actual domain.  
+   - `dig yourdomain.com NS @8.8.8.8` (query Google's DNS)  
+   - `dig yourdomain.com NS @1.1.1.1` (query Cloudflare's DNS)
+   - `whois yourdomain.com`
+   - `dig yourdomain.com @tld.nameserver.com` (`tld.nameserver.com` is the nameserver of your domain's TLD. You can find this information by querying it as `dig com ns +short` where `.com` is the example.)
+   
+   You are looking for the Cloudflare nameservers to be reported consistently. 
 
 ## 4. Initial testing
 
 Once propagation appears to be widespread, perform basic resolution tests for critical records (for example, your website's `A` record and any `MX` records, if you had them set up).
 
-- `dig yourdomain.com A +short`
-- `dig yourdomain.com MX +short`
+- `dig yourdomain.com A +short`  
+- `dig yourdomain.com MX +short`
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
index e08e73b597e57b0..e1f0d1f96eb1bac 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/phase-4.mdx
@@ -14,49 +14,47 @@ After the cutover, verify and stabilize.
 
 ## 1. Thorough testing and validation
 
-1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.
-2. Test from different networks and geographical locations if possible.
-3. Monitor application logs for any DNS-related errors.
+1. Test all services that rely on DNS: websites, email (sending and receiving), VPNs, APIs, etc.  
+2. Test from different networks and geographical locations if possible.  
+3. Monitor application logs for any DNS-related errors.  
 
 ## 2. Enable DNSSEC in Cloudflare (if disabled earlier)
 
 Enable DNSSEC only after you are confident that DNS is resolving correctly through Cloudflare and that nameserver changes have fully propagated. In practice, plan for at least one full DS TTL after you add new DS records at the registrar.
 
-**Action in Cloudflare:**
+**Action in Cloudflare:**  
+   1. In the Cloudflare dashboard, go to your zone's **DNS Settings**.  
 
-1.  In the Cloudflare dashboard, go to your zone's **DNS Settings**.
+      <DashButton url="/?to=/:account/:zone/dns/settings" />
 
-    <DashButton url="/?to=/:account/:zone/dns/settings" />
-
-2.  Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details.
-
-**Action at registrar:**
-
-1.  Log in to your domain registrar.
-2.  Navigate to the DNSSEC management section for your domain.
-3.  Add the `DS` record details provided by Cloudflare.
+   2. Select **Enable DNSSEC**. Cloudflare will sign your zone and generate `DNSKEY` and `DS` record details. 
+ 
+**Action at registrar:**  
+   1. Log in to your domain registrar.  
+   2. Navigate to the DNSSEC management section for your domain.  
+   3. Add the `DS` record details provided by Cloudflare.  
 
 After adding the `DS` record, allow time for propagation and then validate your configuration with tools such as [DNSViz](https://dnsviz.net) or [Verisign's DNSSEC debugger](https://dnssec-debugger.verisignlabs.com/). For more information, refer to [DNSSEC](/dns/dnssec/).
 
-:::note
-If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
-:::
+   :::note
+    If your domain uses Cloudflare Registrar, some DNSSEC steps can be simplified or automated. Refer to [Enable DNSSEC with Cloudflare Registrar](/registrar/get-started/enable-dnssec/) for registrar-specific instructions.
+   :::
 
 ## 3. Adjust TTLs in Cloudflare
 
-After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).
+After the migration is stable and DNSSEC is active (if used), increase the TTLs for your DNS records from the short values used during the migration to more standard values (for example, 3600 seconds for frequently changing records or 86400 seconds for very stable records).  
 
 Higher TTLs improve resolver cache efficiency and can reduce latency by allowing recursive resolvers to reuse cached answers for longer, at the cost of slower propagation when you make changes.
 
 ## 4. Review and enable Cloudflare proxy features
 
-If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.
+If you initially set records to **DNS Only** (grey cloud), now is a good time to enable Cloudflare's proxy (orange cloud) for HTTP/S records (`A`, `AAAA`, `CNAME`) to leverage [CDN](/cache/), [WAF](/waf/), and other security and performance features. Test thoroughly after enabling proxying.  
 
 ## 5. Decommission On-Prem BIND servers
 
 Only after a significant stabilization period (for example, several days to a week after full propagation and successful testing) and when you are fully confident in the Cloudflare setup, decommission the on-premise BIND servers.
 
-Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.
+Ensure no resolvers are still pointing to the old BIND servers. This is especially important for internal resolvers, if they were not addressed separately.   
 
 ## 6. Update internal documentation and monitoring
 
diff --git a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
index 5d966db6e4f2e51..8e23617d11caed2 100644
--- a/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
+++ b/src/content/docs/learning-paths/dns-best-practices/concepts/summary-considerations.mdx
@@ -8,15 +8,15 @@ products:
   - dns
 ---
 
-- Plan meticulously: Do not rush the planning and preparation phases.
-- Communicate clearly: Keep stakeholders informed.
-- Lower TTLs in advance: This is crucial for a faster cutover.
-- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.
-- Verify, verify, verify: Double-check record imports and functionality at each stage.
-- Test thoroughly: From multiple locations and for all critical services.
-- Have a rollback plan: Know how to revert if necessary.
-- Migrate during low traffic: Minimize potential user impact.
-- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.
+- Plan meticulously: Do not rush the planning and preparation phases.  
+- Communicate clearly: Keep stakeholders informed.  
+- Lower TTLs in advance: This is crucial for a faster cutover.  
+- Disable DNSSEC before NS change (safest): Remove DS records at the registrar well before changing nameservers, then re-enable DNSSEC via Cloudflare.  
+- Verify, verify, verify: Double-check record imports and functionality at each stage.  
+- Test thoroughly: From multiple locations and for all critical services.  
+- Have a rollback plan: Know how to revert if necessary.  
+- Migrate during low traffic: Minimize potential user impact.  
+- Address BIND Views/ACLs: Understand how Cloudflare will handle or replace this functionality.  
 - Take advantage of Cloudflare features: Once stable, explore and implement Cloudflare's security and performance enhancements.
 
-By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
+By following these best practices, you can significantly increase the likelihood of a smooth and successful migration from your on-prem BIND DNS to Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
index a1bed2340a8f735..13c9e675861f17d 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/appendix/index.mdx
@@ -12,3 +12,4 @@ products:
   - dlp
   - casb
 ---
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
index 776126418ebd729..4f342e9997e31ea 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/index.mdx
@@ -20,3 +20,4 @@ The goal of this learning path is to provide Cloudflare One users with the strat
 - Monitor AI usage: Utilize Cloudflare One's tools, such as the Shadow IT dashboard and API CASB integrations, to gain visibility into both sanctioned and unsanctioned AI application usage.
 - Build security policies: Create granular security policies using Cloudflare Gateway to control AI usage, prevent data loss with DLP, and manage user behavior through actions like blocking or redirecting.
 - Secure sanctioned models: Apply Zero Trust principles to sanctioned AI models and internal services like Model Context Protocol (MCP) servers to ensure secure access and protect sensitive data from being exposed.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
index 29330ef6e90787c..c8811b8737b69c2 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/mcp.mdx
@@ -22,3 +22,4 @@ MCP uses a client-server architecture where an AI agent acts as the client and s
 ## What are the security concerns with MCP?
 
 MCP doesn't have native authentication, authorization, or encryption. Because it functions similarly to an API, many of the same security considerations apply. If developers do not proactively implement security measures like Transport Layer Security (TLS) and rate limiting, MCP servers can be vulnerable to attacks, data leaks, and unauthorized access. Organizations must ensure that they validate inputs and protect confidential data to secure their MCP implementations.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
index 97b3651ba7daa5d..1d18a0ebba41b16 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/concepts/shadow-ai.mdx
@@ -18,3 +18,4 @@ Shadow AI is the use of any AI tool or application by employees without the form
 Since it may not be feasible to eliminate all instances of shadow AI, organizations can manage the risks by taking a balanced approach. First, it is essential to foster collaboration and open communication between IT and other departments to understand why employees are using these tools. Next, implement guardrails by developing a flexible governance framework with clear guidelines on which types of AI systems can be used and how sensitive information should be handled. Finally, monitor AI usage with network tools to track what is being used and educate employees on the risks of unauthorized AI.
 
 To combat the risks associated with shadow AI, Cloudflare's API-driven CASB integrates with SaaS applications and cloud environments to scan for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
index 2f4c30d5cb527a1..f98c47c842d9d81 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/additional-setup.mdx
@@ -16,4 +16,4 @@ To use the recommended AI security solutions in this learning path, you will nee
 
 :::note
 If you are new to securing your Internet traffic, refer to [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/) to get started and then return to this learning path to continue securing your organizations.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
index 7b68b9d51991f49..67b07408d9070cd 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx
@@ -17,7 +17,6 @@ Before you can secure AI, you need to understand your organization's goals and c
 The level of risk you are willing to accept will determine how quickly you need to act and how deeply you need to implement security measures. Your specific concerns will then guide the exact security approaches you take to monitor and control AI usage.
 
 To begin, consider these questions to help shape your strategy:
-
 - Sanctioned versus shadow AI: Are your employees already using approved AI services, or are you primarily concerned with shadow AI — unapproved applications that may pose a risk? Note: Some approved vendors may offer embedded AI functionality. Consider whether those AI services are a risk, too.
 - Data sensitivity: What types of sensitive data do you currently monitor, classify, and protect? This will help you identify what you need to safeguard when employees interact with AI. If you have not determined this yet, refer to [Define your sensitive data](/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention/#define-your-sensitive-data) to learn more.
 - Encouraging user behavior: Do you want to encourage or limit user engagement with AI? How much do you expect your employees to use AI in a controlled, sanctioned way?
diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
index d466618622bbdb9..b5caf20d92a283f 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/index.mdx
@@ -16,4 +16,4 @@ Businesses are eager to realize the potential boosts to productivity and efficie
 
 IT and security leaders are often asked to address risks and deal with increasing challenges like the use of shadow AI before they have an AI security strategy.
 
-Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively.
+Cloudflare One offers a diverse, comprehensive set of solutions to secure your applications, workforce, and data from emerging generative AI threats. This learning path will provide a path to securely adopt AI use cases within your organization. It includes recommendations and strategies to monitor AI usage, protect against shadow AI, safeguard your sensitive data, and manage Model Context Protocol (MCP) servers effectively. 
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
index 5edae280f6bbf30..48c3654da15b283 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/index.mdx
@@ -17,3 +17,4 @@ Monitoring AI usage is one of the first steps in assessing holistic risk. Cloudf
 After you begin to understand your organization's AI usage, you should develop a balanced perspective on what constitutes sanctioned use of a tool. A good practice is to review applications in phases and then apply security policies based on those phases. For example, you can apply different security policies to applications that are considered approved, unapproved, unreviewed, or in review until they pass your corporate security standards and data privacy reviews.
 
 This section will detail options for assessing and understanding that risk by using inline (client) and out-of-band (API CASB) based methods.
+
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
index 18a65bd00076557..38cfd98df28c2ac 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/monitor-prompts-responses.mdx
@@ -13,11 +13,10 @@ products:
 ---
 
 When you enable [TLS decryption](/cloudflare-one/traffic-policies/http-policies/tls-decryption/#turn-on-tls-decryption), you can review the prompts and responses for supported AI applications. This allows you to understand three key things about AI application usage:
-
 - The sanctioned and unsanctioned AI tools your users are engaging with.
 - How they are interacting with them.
 - What information they are sharing.
 
 ![Log entry for a prompt detected using AI prompt protection.](~/assets/images/learning-paths/holistic-ai-security/gateway-prompt-log.png)
 
-You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
+You can use this in conjunction with [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect sensitive data potentially being used in prompts, with or without explicitly blocking the action. You can use DLP to log AI prompt topics by turning on [Capture generative AI prompt content in logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#turn-on-ai-prompt-content-logging-for-a-dlp-policy) for the policy.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
index aacf8456e79fe1c..c60e183df9211b9 100644
--- a/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
+++ b/src/content/docs/learning-paths/holistic-ai-security/monitor-ai-use/review-inline-ai-use.mdx
@@ -20,6 +20,7 @@ To review how your organization uses AI apps, start with the Cloudflare [Shadow
 
 ![Shadow IT dashboard showing utilization of application statuses (Approved, Unapproved, In Review, Unreviewed).](~/assets/images/learning-paths/holistic-ai-security/shadowit-dashboard-ai-apps.png)
 
-This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as _Approved_. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
+This approach is most relevant for applications that your organization has not yet sanctioned. For example, if your business uses Google Workspace and its primary AI tool is Gemini, you would likely mark Gemini as *Approved*. While you can configure more specific data loss policies later, you can also target approved applications with greater specificity to detect risks unique to your organization.
 
 ![The App Library filtered to show some of the supported Artificial Intelligence applications.](~/assets/images/learning-paths/holistic-ai-security/ai-app-type-app-library.png)
+
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
index da4bbe2960c586f..9d1796cbc8e77a5 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/health-checks.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { GlossaryDefinition, Render } from "~/components";
+import { GlossaryDefinition, Render } from "~/components"
 
 There's more to a load balancer than just distributing traffic, however.
 
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
index 7369a7445edbd8d..2a58f062dc5eeeb 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/index.mdx
@@ -14,7 +14,7 @@ Learn the concepts behind load balancing, whether you are using Cloudflare or an
 
 By the end of this module, you will be able to:
 
-- Explain what load balancing is.
-- Describe the differences between load balancers, pools, and servers.
-- Explain what pool health is and how it affects load balancer traffic.
-- List the different ways your traffic can be routed.
+* Explain what load balancing is.
+* Describe the differences between load balancers, pools, and servers.
+* Explain what pool health is and how it affects load balancer traffic.
+* List the different ways your traffic can be routed.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
index e132195e0f7fb3a..7dd7ff6d269783a 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/load-balancer-components.mdx
@@ -8,13 +8,13 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 At it's most basic, load balancing is made up of three components:
 
-- **Pools**: Which contain one or more endpoints.
-- **Endpoints**: Which respond to individual requests.
-- **A load balancer**: Which decides which traffic goes to each pool.
+* **Pools**: Which contain one or more endpoints.
+* **Endpoints**: Which respond to individual requests.
+* **A load balancer**: Which decides which traffic goes to each pool.
 
 ## How it works
 
@@ -22,7 +22,7 @@ Normally, requests to your application would go to individual servers directly.
 
 With a load balancer, requests first go through the load balancer. Your load balancer then routes requests to specific pools.
 
-<Render file="load-balancing-diagram" product="load-balancing" /> <br />
+<Render file="load-balancing-diagram" product="load-balancing" /> <br/>
 
 Within each pool, requests then go to individual endpoints. And that endpoint is what responds to the request.
 
@@ -37,6 +37,6 @@ Within each pool, requests then go to individual endpoints. And that endpoint is
       end
 ```
 
-<br />
+<br/>
 
 This progression of load balancer --> pool --> endpoint is the core part of how a load balancer works.
diff --git a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
index d8019a91c1cf983..b5cf54d4113227f 100644
--- a/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
+++ b/src/content/docs/learning-paths/load-balancing/concepts/routing.mdx
@@ -8,11 +8,11 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Before, we covered how requests move from load balancers to pools and then from pools to individual servers.
 
-What we did not mention, however, was _how_ the load balancer and pools make those decisions.
+What we did not mention, however, was *how* the load balancer and pools make those decisions.
 
 This is a concept known as routing.
 
@@ -60,5 +60,5 @@ Often, load balancers have a special pool known as the **Fallback Pool**, which
 
 Finally, specific settings can also affect the ways a load balancer distributes traffic, such as:
 
-- Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
-- Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
+* Routing based on [specific aspects](/load-balancing/additional-options/load-balancing-rules/) of the request.
+* Sending all requests from a [specific end user](/load-balancing/understand-basics/session-affinity/) to the same server, preserving information about their user session like items in a shopping cart.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
index cc8e287532908ff..6337e5cf7172cd6 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/custom-rules.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="custom-rules-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/index.mdx b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
index 370f197fbab2a2d..eeee73027d3ca18 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/index.mdx
@@ -14,7 +14,7 @@ Explore the configuration choices available for your Cloudflare load balancer.
 
 By the end of this module, you will be able to:
 
-- Describe the difference between load balancing at different layers of the network stack.
-- Identify when a load balancer should utilize session affinity.
-- Describe the different policies for endpoint steering and traffic steering.
-- List the different options available to monitor server health.
+* Describe the difference between load balancing at different layers of the network stack.
+* Identify when a load balancer should utilize session affinity.
+* Describe the different policies for endpoint steering and traffic steering.
+* List the different options available to monitor server health.
diff --git a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
index 820f34fada45575..34aa1d6847c2ece 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/multiple-zones.mdx
@@ -20,8 +20,10 @@ If you want to share a load balancing configuration across multiple hostnames, y
 
 :::note
 
+
 You could also achieve the same goal or create more advanced routing decisions by setting up DNS Overrides within [Origin Rules](/rules/origin-rules/) on each hostname that override the hostname to `lb.example.com`.
 
+
 :::
 
 ## Unique configurations
diff --git a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
index b430e5865cbd6a6..d03dbb9b4796bd1 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/origin-steering-policies.mdx
@@ -8,17 +8,17 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="origin-steering-definition" product="load-balancing" />
 
----
+***
 
 ## Policies
 
 <Render file="origin-steering-policies" product="load-balancing" />
 
----
+***
 
 ## Weights
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
index 70a7b3e021585fc..dd99e87ee3c3d01 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/session-affinity.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="session-affinity-definition" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
index 3b370b1ed392b31..9ced34523117fe9 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/traffic-steering.mdx
@@ -8,8 +8,8 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
-<Render file="traffic-steering-definition" product="load-balancing" /> <br />
+<Render file="traffic-steering-definition" product="load-balancing" /> <br/>
 
 <DirectoryListing folder="load-balancing/understand-basics/traffic-steering/steering-policies" />
diff --git a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
index 1b2a9ce5c84006d..a1fbbb640bf00cb 100644
--- a/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
+++ b/src/content/docs/learning-paths/load-balancing/planning/types-load-balancers.mdx
@@ -8,15 +8,15 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 With Cloudflare, you can choose between three types of load balancers:
 
-- [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
-- [DNS-only](#dns-only-load-balancing)
-- [Layer 4 (TCP)](#layer-4-load-balancing)
+* [Layer 7 (HTTP/HTTPS)](#layer-7-load-balancing) (most common)
+* [DNS-only](#dns-only-load-balancing)
+* [Layer 4 (TCP)](#layer-4-load-balancing)
 
----
+***
 
 ## Layer 7 load balancing
 
@@ -26,7 +26,7 @@ With Cloudflare, you can choose between three types of load balancers:
 
 <Render file="layer-7-load-balancing-benefits" product="load-balancing" />
 
----
+***
 
 ## DNS-only load balancing
 
@@ -34,13 +34,13 @@ With Cloudflare, you can choose between three types of load balancers:
 
 ### Benefits
 
-<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br />
+<Render file="dns-load-balancing-benefits" product="load-balancing" /> <br/>
 
 ### Limitations
 
 <Render file="dns-load-balancing-limitations" product="load-balancing" />
 
----
+***
 
 ## Layer 4 load balancing
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
index a34dcbf56c1a141..e44453449357179 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/check-pool-health.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="confirm-pool-health" product="load-balancing" />
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
index 54cf2a41d9f5d89..f963bd4a1cc3aee 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/hostname-preparation.mdx
@@ -10,8 +10,8 @@ products:
 
 Before setting up anything related to your load balancer, make sure you test that production hostnames meet the following criteria:
 
-- Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
-- Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
+* Based on the [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records, they will receive the intended amount of traffic.
+* Each hostname is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 
 After confirming each of these conditions are met, you can proceed with setting up your load balancer.
 
@@ -19,5 +19,5 @@ After confirming each of these conditions are met, you can proceed with setting
 
 Depending on your preferences and infrastructure, you might route traffic to your load balancer in different ways:
 
-- For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
-- However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
+* For most customers, it's simpler to create the load balancer on the hostname directly (`www.example.com`).
+* However, you could also create the load balancer on another hostname (`lb.example.com`) and then route traffic using a `CNAME` record on `test.example.com` that points to `lb.example.com`.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/index.mdx b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
index 2f7ceb3e5cd7744..20b76253146a2fe 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/index.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/index.mdx
@@ -14,13 +14,13 @@ Create a load balancer that monitors endpoint health and intelligently routes tr
 
 By the end of this module, you will be able to:
 
-- Configure a monitor and health checks.
-- Create a pool.
-- Create a load balancer.
-- Analyze traffic patterns.
+* Configure a monitor and health checks.
+* Create a pool.
+* Create a load balancer.
+* Analyze traffic patterns.
 
 ## Prerequisites
 
-- Multiple endpoints, either physical or cloud-based.
-- Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
-- Two hostnames, one for test traffic and the other for production traffic.
+* Multiple endpoints, either physical or cloud-based.
+* Access to Load Balancing, available as an [add-on](/load-balancing/get-started/enable-load-balancing/) for any type of account.
+* Two hostnames, one for test traffic and the other for production traffic.
diff --git a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
index 5cb5b8556548c35..7dea7a8b054a166 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/next-steps.mdx
@@ -8,7 +8,7 @@ products:
   - load-balancing
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Your load balancer should be receiving production traffic (and you can confirm this by reviewing the [analytics](/load-balancing/reference/load-balancing-analytics/)).
 
diff --git a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
index 5f6e8812e2b018b..f2dda24cae894f0 100644
--- a/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
+++ b/src/content/docs/learning-paths/load-balancing/setup/production-traffic.mdx
@@ -8,6 +8,6 @@ products:
   - load-balancing
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="route-production-traffic" product="load-balancing" />
diff --git a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
index a9014dbe620e151..158ed1dbb6f5b89 100644
--- a/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
+++ b/src/content/docs/learning-paths/mtls/concepts/mtls-cloudflare.mdx
@@ -20,10 +20,10 @@ Some common mTLS use cases are:
 
 There are two main ways to use mTLS at Cloudflare, either by using the Application Security offering (optionally including [API Shield](/api-shield/)) or [Cloudflare Access](/cloudflare-one/access-controls/policies/). Below is a non-exhaustive overview table of their differences:
 
-| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Feature                                                               | Application Security (Client Certificate \+ WAF)                                                                                                                                                                                                                                                                                  | Cloudflare Access (mTLS)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mainly used for                                                       | External Authentication (that is, APIs)                                                                                                                                                                                                                                                                                           | Internal Authentication (that is, employees)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Availability                                                          | By default, 100 Client Certificates per Zone are included for free. For more certificates or [API Shield features](/api-shield/), contact your account team.                                                                                                                                                                      | Zero Trust Enterprise only feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| [Certificate Authority (CA)](/ssl/concepts/#certificate-authority-ca) | Cloudflare-managed or customer-uploaded (BYO CA). There's a soft-limit of up to [five customer-uploaded CAs](/ssl/client-certificates/byo-ca/#availability).                                                                                                                                                                      | Customer-uploaded only (BYO CA). There's a soft-limit of up to [50 CAs](/cloudflare-one/account-limits/#access).                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | Client Certificate Details                                            | Forwarded to the origin server via [Cloudflare API](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-api), [Cloudflare Workers](/ssl/client-certificates/forward-a-client-certificate/#cloudflare-workers), and [Managed Transforms](/ssl/client-certificates/forward-a-client-certificate/#managed-transforms). | Forwarded to the origin server via [Cloudflare API](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-api), [Cloudflare Workers](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#cloudflare-workers), and [Managed Transforms](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#managed-transforms). Client Certificate headers and [Cf-Access-Jwt-Assertion](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/) JWT header can be forwarded to the origin server. |
-| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Client Certificates Revocation                                        | Use the WAF [Custom Rules](/waf/custom-rules/) to check for [_cf.tls_client_auth.cert_revoked_](/ssl/client-certificates/revoke-client-certificate/), which only applies to Cloudflare-managed CA. <br /><br /> For BYO CAs, it would be the same approach as with Cloudflare Access.                                             | Generate a [Certificate Revocation List (CRL)](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#create-a-crl) and enforce the revocation in a Cloudflare Worker.                                                                                                                                                                                                                                                                                                                                                                                         |
diff --git a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
index 4bc6231c21b5a96..93042dd1fa01f4d 100644
--- a/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
+++ b/src/content/docs/learning-paths/mtls/mtls-implementation/index.mdx
@@ -26,4 +26,4 @@ mTLS user authentication is included with Cloudflare Access and depends on the n
 
 ## Option 3: mTLS Service Authentication
 
-The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
+The hostnames are used to look up the certificates and verify their authenticity. Once the connection is established, all data transmitted between the hosts is encrypted, ensuring that it cannot be intercepted and read by third parties. Here the main driver is the number of hostnames.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
index c481f87de2d65a0..16c8ccf32ad86d5 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 Cloudflare provides analytics for [security events](/waf/analytics/security-events/), [traffic patterns](/analytics/account-and-zone-analytics/zone-analytics/), and more according to the level of your zone's plan.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
index 05f03d0f144275e..a4da185bc6f5065 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/index.mdx
@@ -15,7 +15,7 @@ Learn how to customize and augment Cloudflare’s DDoS protection.
 
 By the end of this module, you will be able to:
 
-- Audit DNS records to prevent accidental IP address exposures.
-- Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
-- Augment Cloudflare's default analytics to examine attacks in more detail.
-- Evaluate different ways to restrict external connections to your origin server.
+* Audit DNS records to prevent accidental IP address exposures.
+* Optimize caching and security to reduce incoming traffic (whether malicious or legitimate).
+* Augment Cloudflare's default analytics to examine attacks in more detail.
+* Evaluate different ways to restrict external connections to your origin server.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
index c2f9d500ff25ee7..c37bbf8ec26a7db 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/index.mdx
@@ -15,6 +15,6 @@ Get world-class DDoS protection with a few simple steps.
 
 By the end of this module, you will be able to:
 
-- List the built-in DDoS protection measures provided by Cloudflare.
-- Implement a few, simple customizations to improve DDoS protection.
-- Set up DDoS-related notifications.
+* List the built-in DDoS protection measures provided by Cloudflare.
+* Implement a few, simple customizations to improve DDoS protection.
+* Set up DDoS-related notifications.
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
index 882b2ac86f7af63..d464cb2979e60be 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/proxy-dns-records.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 The first - and often easiest - step of DDoS protection is making sure your DNS records are [proxied](/dns/proxy-status/) through Cloudflare.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
index 504b661aeade97c..52946023a5865ab 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/set-up-alerts.mdx
@@ -9,7 +9,7 @@ products:
   - waf
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Another part of preparing for DDoS attacks is knowing when your application is being attacked.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
index 2dde4bb728e4cad..315ae18c24d496c 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/baseline/tls-versions.mdx
@@ -13,8 +13,8 @@ In some circumstances - specifically when an application allows client-initiated
 
 When you use an SSL/TLS certificate issued by Cloudflare[^1], you can reduce the impact of this vulnerability by:
 
-- Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
-- Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
+* Updating the [Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) accepted by your application.
+* Allowing [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/).
 
 [^1]: Meaning either [Universal](/ssl/edge-certificates/universal-ssl/) or [Advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates.
 
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
index 5d276a7499bc51b..cfb31f718c1afba 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/concepts/index.mdx
@@ -15,5 +15,5 @@ Learn the concepts behind DDoS attacks and protection, whether you are using Clo
 
 By the end of this module, you will be able to:
 
-- Explain what a DDoS attack is and how it could affect your application.
-- List the common ways to prevent DDoS attacks.
+* Explain what a DDoS attack is and how it could affect your application.
+* List the common ways to prevent DDoS attacks.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
index 55992a486b4f980..bc327a66a03d394 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/index.mdx
@@ -18,7 +18,7 @@ With Cloudflare Zero Trust, you can apply granular security policies to all traf
 
 By the end of this module, you will be able to:
 
-- Create Zero Trust policies to secure access to your private network.
-- Enforce Cloudflare One Client session timeouts.
-- Display custom block messages.
-- Discover Shadow IT within your private network.
+* Create Zero Trust policies to secure access to your private network.
+* Enforce Cloudflare One Client session timeouts.
+* Display custom block messages.
+* Discover Shadow IT within your private network.
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
index 78c93a432dea818..29387c50590e5a7 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/policy-design.mdx
@@ -17,11 +17,11 @@ Most policy building for private network access happens within the Gateway DNS a
 
 Before building your policies, it is helpful to ask yourself a few questions:
 
-- Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
-- Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
-- Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
-- Do you have sources of truth for identity and device posture that will be used in policies?
-- Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
+* Should all users and services be able to reach all connected subnets? Are there explicit exceptions?
+* Do all applications live within a primary network range, and are they defined by static or dynamic hosts and IP addresses?
+* Are there DevOps workflows that rely on completely ephemeral IPs or subdomains?
+* Do you have sources of truth for identity and device posture that will be used in policies?
+* Do you plan to immediately implement a default-deny model? In other words, will you block all users except for those who match an explicit Allow policy?
 
 ## Prepare to build policies
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
index a78d1ef69ea07de..943c9627d37f792 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/session-timeouts.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Most legacy VPNs have a global timeout setting that requires end users to log in every X hours or resets VPN profiles at a certain frequency. By doing continuous identity evaluation, a Zero Trust security model eliminates the need for most of the user-interrupting workflows triggered by session timeouts. However, there can still be valid reasons to want users to reauthenticate, either on a recurring basis or to access specific, highly-sensitive or regulated internal services.
 
diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
index 43ea4220994ee40..10077edc657d785 100644
--- a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx
@@ -43,13 +43,11 @@ Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build
 [Logs](/cloudflare-one/insights/logs/) provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment.
 
 To review traffic activity for applications protected by Access:
-
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **Access authentication logs**.
 3. Review the [per-request logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#per-request-logs) for your application.
 
 To review traffic activity in the [Gateway logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/):
-
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**.
 2. Select **HTTP request logs**, **Network logs**, or **DNS query logs** depending on your investigation scope.
 
@@ -100,8 +98,7 @@ To create a device connectivity anomaly notification:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
-
+    <DashButton url="/?to=/:account/notifications" />
 2. Select **Add**.
 3. Find **Product** DEX and **Alert type** Device connectivity anomaly, and choose **Select**.
 4. Name the notification.
@@ -119,4 +116,4 @@ Once your policies are live, you can use [DEX tests](/learning-paths/replace-vpn
 
 To learn how to use Logs, Analytics, and DEX together during real-world situations, like onboarding, daily monitoring, and troubleshooting, refer to [Insights](/cloudflare-one/insights/) for more example use cases.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
index e227e835a77f69b..f21582fa384073e 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/index.mdx
@@ -17,6 +17,6 @@ Concepts explain the basic ideas behind how Cloudflare Zero Trust works.
 
 By the end of this module, you will be able to:
 
-- Explain how Cloudflare works.
-- Describe the purpose of a VPN.
-- Understand the benefits of switching to a Zero Trust architecture.
+* Explain how Cloudflare works.
+* Describe the purpose of a VPN.
+* Understand the benefits of switching to a Zero Trust architecture.
diff --git a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
index 92bfa07cbd99ff5..9d605a12bcca0b2 100644
--- a/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/concepts/what-is-cloudflare.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="what-is-cloudflare" product="fundamentals" />
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
index 7a46245dacacf0c..62f98d74710996a 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/cloudflared.mdx
@@ -12,7 +12,7 @@ products:
   - gateway
 ---
 
-import { Render, Tabs, TabItem } from "~/components";
+import { Render, Tabs, TabItem } from "~/components"
 
 Cloudflare Tunnel is an outbound-only daemon service that can run on nearly any host machine and proxies local traffic once validated from the Cloudflare network. User traffic initiated from the Cloudflare One Client onramps to Cloudflare, passes down your Cloudflare Tunnel connections, and terminates automatically in your local network. Traffic reaching your internal applications or services will carry the local source IP address of the host machine running the `cloudflared` daemon.
 
@@ -73,16 +73,17 @@ All internal applications and services in this IP range are now connected to Clo
 
 If the tunnel is disconnected:
 
-- Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
-- Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+* Ensure that your on-premise or cloud firewall allows egress traffic on the [required ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation).
+* Ensure that the `cloudflared` host machine can connect to your internal applications and services. Verify that the host has the proper security group memberships and that no firewalls will block traffic between the host and the target services.
+
 
 :::
 
 ## Best practices
 
-- Segregate production and staging traffic among different Cloudflare tunnels.
-- Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
-- Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
-- [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
-- [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
-- [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
+* Segregate production and staging traffic among different Cloudflare tunnels.
+* Add a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) to another host machine for an additional point of availability.
+* Distribute access to critical services (for example, private DNS, Active Directory, and other critical systems) across different tunnels for blast-radius reduction in the event of a server-side outage.
+* [Enable notifications](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/notifications/) in the Cloudflare dashboard to monitor tunnel health.
+* [Monitor performance metrics](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/metrics/) to identify potential bottlenecks.
+* [Update `cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared/) regularly.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
index 9ff188f45e603dd..d36ecb80dd109d4 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/connection-methods.mdx
@@ -33,17 +33,17 @@ There are [multiple ways](/reference-architecture/architectures/sase/#connecting
 
 ## Comparison table
 
-|                       | Cloudflare Mesh                                                        | Cloudflare Tunnel                                                                                                                                                                                                                                   |
-| --------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bidirectional traffic | ✅                                                                     | ❌                                                                                                                                                                                                                                                  |
-| High availability     | ✅ (active-passive)                                                    | ✅ (active-active replicas)                                                                                                                                                                                                                         |
-| Source IP of request  | Virtual IP of requesting device                                        | `cloudflared` host machine                                                                                                                                                                                                                          |
-| Host machine          | Linux (amd64, arm64)                                                   | Linux, macOS, Windows                                                                                                                                                                                                                               |
-| IPv4                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
-| IPv6                  | ✅                                                                     | ✅                                                                                                                                                                                                                                                  |
-| OSI layer             | L3                                                                     | L7                                                                                                                                                                                                                                                  |
-| Protocol              | MASQUE                                                                 | QUIC or HTTP/2                                                                                                                                                                                                                                      |
-| Protocols proxied     | TCP, UDP, ICMP                                                         | HTTP/S, TCP, SSH, RDP, SMB                                                                                                                                                                                                                          |
+|                       | Cloudflare Mesh                 | Cloudflare Tunnel           |
+| --------------------- | ------------------------------- | --------------------------- |
+| Bidirectional traffic | ✅                              | ❌                          |
+| High availability     | ✅ (active-passive)             | ✅ (active-active replicas) |
+| Source IP of request  | Virtual IP of requesting device | `cloudflared` host machine  |
+| Host machine          | Linux (amd64, arm64)            | Linux, macOS, Windows       |
+| IPv4                  | ✅                              | ✅                          |
+| IPv6                  | ✅                              | ✅                          |
+| OSI layer             | L3                              | L7                          |
+| Protocol              | MASQUE                          | QUIC or HTTP/2              |
+| Protocols proxied     | TCP, UDP, ICMP                  | HTTP/S, TCP, SSH, RDP, SMB  |
 | Connection handling   | End-to-end — preserves long-lived TCP connections across the full path | Proxied — TCP connections are terminated and re-established at Cloudflare, which can interrupt long-lived sessions (for example, SAP transactions, database replication streams, or persistent RDP sessions may drop when `cloudflared` reconnects) |
 
 ## Recommendation
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
index 73d7ed1fcc063fd..8dfc2d8f3e258e1 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/index.mdx
@@ -17,6 +17,6 @@ This module covers how to connect your private network services and applications
 
 By the end of this module, you will be able to:
 
-- Create a Cloudflare Tunnel.
-- Configure private network routes for your tunnel.
-- Understand how to size and scale your tunnel.
+* Create a Cloudflare Tunnel.
+* Configure private network routes for your tunnel.
+* Understand how to size and scale your tunnel.
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
index 536d489c6b31be9..c6b1493e5165c97 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/overlapping-ips.mdx
@@ -10,7 +10,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="tunnel/virtual-networks-intro" product="cloudflare-one" />
 
diff --git a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
index 061277556b36313..91c1e173b09527c 100644
--- a/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/connect-private-network/tunnel-capacity.mdx
@@ -11,7 +11,7 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Now that you have a Cloudflare Tunnel up and running, evaluate whether `cloudflared` has enough system resources to handle the expected volume of requests from end users. <Render file="tunnel/availability/tunnel-capacity-intro" product="cloudflare-one" />
 If you have exhausted the ports on a single machine, you will need to add additional servers running `cloudflared`.
diff --git a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
index b7e1bbfc5ccef53..9add3ff07321ee9 100644
--- a/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/get-started/prerequisites.mdx
@@ -13,7 +13,7 @@ products:
 
 To make the most of this learning path, make sure that you have the following:
 
-- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-- A private network with applications or services that are available locally or via a VPN.
-- A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
-- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
+* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+* A private network with applications or services that are available locally or via a VPN.
+* A [host server](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#recommendations) on the private network that can run the lightweight Cloudflare Tunnel daemon process.
+* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh. This is only needed for server-initiated traffic flows such as Microsoft SCCM, Active Directory (AD) updates, and DevOps workflows that require server-initiated connections.
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
index 1b88fb9f8b8b920..a516b09d3f257d6 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/index.mdx
@@ -19,7 +19,7 @@ Learn how to troubleshoot your ZTNA deployment.
 
 By the end of this module, you will be able to:
 
-- Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
-- Fix the most common causes of connectivity issues.
+* Investigate why users cannot connect to private network applications behind Cloudflare Tunnel.
+* Fix the most common causes of connectivity issues.
 
 <Render file="warp/troubleshooting-guide-reference" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
index 4a8c12e1c07aa82..e4c61751d31b4a3 100644
--- a/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
+++ b/src/content/docs/learning-paths/replace-vpn/troubleshooting/troubleshoot-private-networks.mdx
@@ -11,6 +11,6 @@ products:
   - gateway
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="tunnel/troubleshoot-private-networks" product="cloudflare-one" />
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
index d83c0f50abab201..fa82b98809cbb10 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/index.mdx
@@ -18,6 +18,6 @@ DNS security is an important, wide-reaching, and early action in the lifecycle o
 
 By the end of this module, you will be able to:
 
-- Create your first Gateway DNS policy.
-- Build an allow or block list for use in firewall policies.
-- Onboard networks to Gateway to filter DNS queries.
+* Create your first Gateway DNS policy.
+* Build an allow or block list for use in firewall policies.
+* Onboard networks to Gateway to filter DNS queries.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
index 3264f26eb9ea844..3a42196c4090ecc 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/index.mdx
@@ -16,16 +16,18 @@ Now that you have created firewall policies to secure your organization, you can
 
 :::note
 
+
 The following module requires [egress policies](/cloudflare-one/traffic-policies/egress-policies/), a feature only available on Enterprise plans. If you are not an Enterprise user, you can skip ahead to [Secure SaaS applications](/learning-paths/secure-internet-traffic/secure-saas-applications/).
 
 For more information on egress policies, contact your account team.
 
+
 :::
 
 ## Objectives
 
 By the end of this module, you will be able to:
 
-- Understand when your organization may need source IP anchoring.
-- Create egress policies to make use of dedicated egress IPs.
-- Follow best practices for deploying egress IPs.
+* Understand when your organization may need source IP anchoring.
+* Create egress policies to make use of dedicated egress IPs.
+* Follow best practices for deploying egress IPs.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
index 486ba1b10c7e8c0..b67afebdb19655c 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/index.mdx
@@ -18,7 +18,7 @@ After securing your organization's DNS queries and network level traffic, you ca
 
 By the end of this module, you will be able to:
 
-- Understand how and when to use TLS inspection to decrypt HTTPS traffic.
-- Configure and enable Data Loss Prevention to protect your organization's sensitive data.
-- Protect user endpoints with Browser Isolation.
-- Add recommended HTTP security policies.
+* Understand how and when to use TLS inspection to decrypt HTTPS traffic.
+* Configure and enable Data Loss Prevention to protect your organization's sensitive data.
+* Protect user endpoints with Browser Isolation.
+* Add recommended HTTP security policies.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
index 8d4115bd0b7fde1..71711da35cc0387 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/concepts/index.mdx
@@ -18,5 +18,5 @@ Learn the core concepts of using Cloudflare Zero Trust functionality to provide
 
 By the end of this module, you will be able to:
 
-- Understand what products and features Cloudflare offers.
-- Describe how Cloudflare implements Internet traffic and SaaS app security.
+* Understand what products and features Cloudflare offers.
+* Describe how Cloudflare implements Internet traffic and SaaS app security.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
index a22224d4e229731..319216b4c04291b 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/connect-devices-networks/choose-on-ramp.mdx
@@ -36,12 +36,12 @@ Cloudflare supports filtering HTTP/S traffic sent via a PAC file on a user devic
 
 Cloudflare Browser Isolation runs a headless, Chromium-based browser for your users to accomplish their secure browsing needs. It can be activated via an Access application, a Gateway policy, or by using link-based isolation (reverse proxy). In this model, your users can connect from any device to a proxy website to browse the Internet while applying all your Gateway HTTP policies and inspection requirements.
 
-|                                                                                                 | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
-| ----------------------------------------------------------------------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
-| Supported OS                                                                                    | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
-| Configurable via MDM                                                                            | Yes                                  | Yes            | N/A                                   |
-| Gateway policy types supported                                                                  | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
-| Identity-based policies supported                                                               | Yes                                  | No             | Yes                                   |
+|                                   | Cloudflare One Client                | PAC Files      | Clientless Browser Isolation          |
+| --------------------------------- | ------------------------------------ | -------------- | ------------------------------------- |
+| Supported OS                      | macOS, Windows, Linux, iOS, Android  | All desktop OS | All OS (with HTML5 compliant browser) |
+| Configurable via MDM              | Yes                                  | Yes            | N/A                                   |
+| Gateway policy types supported    | DNS, Network, HTTP, Resolver, Egress | HTTP           | DNS, Network, HTTP, Resolver, Egress  |
+| Identity-based policies supported | Yes                                  | No             | Yes                                   |
 | [Network Session Logs](/logs/logpush/logpush-job/datasets/account/zero_trust_network_sessions/) | Yes                                  | Yes            | Yes                                   |
 
 ## Network on-ramps
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
index 0317f717c9237be..14f947c033c85f7 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/initial-setup/prerequisites.mdx
@@ -14,5 +14,5 @@ products:
 
 To make the most of securing your Internet traffic and SaaS apps, make sure that you have the following:
 
-- A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
-- (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
+* A device that can run [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/), Cloudflare's endpoint agent.
+* (Optional) A [Linux host server](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#linux) on the private network that can run Cloudflare Mesh, a software agent similar to the Cloudflare One Client.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
index e67e85f67da54d6..1dcb52b2c614a63 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/index.mdx
@@ -18,6 +18,6 @@ Now that you have deployed dedicated egress IPs and created egress policies to a
 
 By the end of this module, you will be able to:
 
-- Secure your SaaS applications by integrating them with Cloudflare CASB.
-- Control access to your SSO front door.
-- Layer multiple security methods for protecting SaaS apps.
+* Secure your SaaS applications by integrating them with Cloudflare CASB.
+* Control access to your SSO front door.
+* Layer multiple security methods for protecting SaaS apps.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
index 92db03a4e2e98a1..52d73e8318fb87d 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx
@@ -18,10 +18,10 @@ products:
 
 Access for SaaS integrates directly with your SaaS app using standard protocols (such as SAML) to become the primary enforcement point for user access. Access calls your identity provider (IdP) of choice and uses additional security signals about your users and devices to make policy decisions. Benefits of Access for SaaS include:
 
-- A streamlined experience for users on both managed and unmanaged devices.
-- Application of baseline policies requiring specific concepts such as device posture and endpoint control.
-- Distinct access methodology for contractors.
-- Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
+* A streamlined experience for users on both managed and unmanaged devices.
+* Application of baseline policies requiring specific concepts such as device posture and endpoint control.
+* Distinct access methodology for contractors.
+* Flexibility to configure multiple SSO vendors simultaneously, freely switch between SSO vendors, and reduce reliance on a single vendor.
 
 ### SSO integrations
 
@@ -29,8 +29,10 @@ You can pair Access for SaaS with the [App Launcher](/cloudflare-one/access-cont
 
 :::note[SCIM provisioning limitation]
 
+
 Access for SaaS supports SCIM passthrough in an API-only closed beta. If you require SCIM passthrough, contact your account team.
 
+
 :::
 
 ## Configure your SSO provider
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
index 3e738d411947195..4028b6ad5e95765 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/index.mdx
@@ -22,6 +22,6 @@ This guide will provide you with a baseline of recommended policies to build and
 
 By the end of this module, you will be able to:
 
-- Understand the order Gateway enforces policies for filtering traffic.
-- Create reusable lists for Gateway policies.
-- Subscribe to indicator feeds for advanced threat intelligence.
+* Understand the order Gateway enforces policies for filtering traffic.
+* Create reusable lists for Gateway policies.
+* Subscribe to indicator feeds for advanced threat intelligence.
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
index 288ad4bd4f9c714..d37b3443e21db00 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/indicator-feeds.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When building DNS, network, or HTTP policies to block malicious activity for your organization, you can use external indicator feeds supplied by Cloudflare and other third-party providers.
 
@@ -20,4 +20,4 @@ When building DNS, network, or HTTP policies to block malicious activity for you
 
 <Render file="indicator-feeds-overview" product="security-center" />
 
-To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
+To subscribe to an indicator feed, contact your account team. For more information, refer to [Custom Indicator Feeds](/security-center/indicator-feeds/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
index 075efbb8570f006..4613217ef45c558 100644
--- a/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
+++ b/src/content/docs/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement.mdx
@@ -12,7 +12,7 @@ products:
   - browser-isolation
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Gateway follows a specific order of enforcement as traffic travels through the Cloudflare global network to the Internet:
 
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
index 779c314e0307099..094d430d9789447 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/index.mdx
@@ -16,4 +16,4 @@ By the end of this module, you will be able to:
 
 - Explain how Cloudflare works.
 - Describe what Email security is.
-- Understand how Cloudflare prevents email-based phishing attacks.
+- Understand how Cloudflare prevents email-based phishing attacks.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
index a81f77056268cbd..325d8d4fbe5e300 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/protect-from-phishing-attacks.mdx
@@ -16,4 +16,4 @@ As organizations continue to adopt Microsoft 365 and Google Workspace to enhance
 
 Analysts agree that consolidating capabilities to minimize overlapping functionality is helping organizations reduce cost and complexity. However, they also advise organizations to carefully assess native features to ensure they satisfy all use cases. As Microsoft and Google continue to build out its essential email security features, the growing overlap with SEGs has given organizations an opportunity to streamline security operations by leveraging capabilities already included in their E3 or E5 license.
 
-This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
+This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
index 6810419da647886..606e29d7f67ce79 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-cloudflare.mdx
@@ -8,6 +8,6 @@ products:
   - email-security
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="what-is-cloudflare" product="fundamentals" />
+<Render file="what-is-cloudflare" product="fundamentals" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
index e751db0ccb39b91..972a75f3e69fb82 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-email-security.mdx
@@ -10,4 +10,4 @@ products:
 
 Despite email's importance as a communication method, security and privacy were not built into the [The Simple Mail Transfer Protocol (SMTP) protocol](https://www.cloudflare.com/learning/email-security/what-is-smtp/). As a result, email is a major attack vector.
 
-Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
+Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
index 2476b73b8cb70b2..1134bd825289830 100644
--- a/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/concepts/what-is-phishing-attack.mdx
@@ -12,4 +12,4 @@ products:
 
 Phishing attackers disguise themselves as a reputable source. With an enticing or seemingly urgent request, an attacker lures the victim into providing information, just as a person uses bait while fishing.
 
-Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
+Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
index 09e0b06afb41ca9..a017783809f59cb 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx
@@ -49,4 +49,4 @@ In addition, Email security allows you to:
 
 - [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry).
 - [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry).
-- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
+- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
index 8df6912430c831b..665a142ede96132 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/audit-logs.mdx
@@ -21,6 +21,7 @@ To enable audit logs:
 2. Select your storage destination.
 3. Select the three dots > **Edit**.
 4. Under **Configure logpush job**:
+
    - **Job name**: Enter the job name, if it is not already prepopulated.
    - **If logs match** > Select **Filtered logs**:
      - **Field**: Choose `ResourceType`.
@@ -29,4 +30,4 @@ To enable audit logs:
 
 5. Select **Submit**.
 
-You can now view logs via the Cloudflare dashboard.
+You can now view logs via the Cloudflare dashboard.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
index fbbb6474283ca81..0378058f8d87ec6 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx
@@ -30,4 +30,4 @@ To add a user to the impersonation registry:
      - **Add users or groups**: Choose the users or groups you want to register.
 6. Select **Save**.
 
-For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
+For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users).
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
index 2e7a4d8bfb7cbe7..461cbd6dbd19774 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/index.mdx
@@ -10,4 +10,4 @@ products:
 
 With Email security, there is limited manual configuration and tuning. The Active Directory sync, allow policies, and additional detections are important to consider when you set up Email security.
 
-In this module, you will configure your email environment.
+In this module, you will configure your email environment.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
index ba4ad5c0c65ba4a..3cc5f8cd3fe2d8c 100644
--- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx
@@ -33,4 +33,4 @@ To set up PhishNet for Google Workspace:
 1. Log in to the Google Workspace Marketplace using an administrator account.
 2. Select **Admin install** to install Cloudflare PhishNet.
 
-Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
+Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
index 6efc9e48a5b5f2c..34c5572c1d9bd7f 100644
--- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/index.mdx
@@ -16,4 +16,4 @@ Ensure you have completed the previous modules before enabling auto-moves.
 
 Auto-move events are events where emails are automatically moved to different inboxes based on the disposition assigned to them by Email security.
 
-When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
+When you set up auto-moves, you can move messages manually or set up automatic moves to send messages matching certain [dispositions](/learning-paths/secure-your-email/enable-auto-moves/email-dispositions/) to specific folders within a user's mailbox.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
index 20822f04cf3be59..a5209b5455fedb9 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/deployment-models.mdx
@@ -20,8 +20,8 @@ If you are a Google Workspace user, you can enable Email security via [BCC setup
 
 ![Google Workspace BCC deployment diagram](~/assets/email-security/Gmail_Deployment_BCC.png)
 
-With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection.
+With MX/Inline, Email security scans your email before they land in your inbox, giving you the highest level of protection. 
 
 ![Microsoft 365 and Google Workspace MX/Inline](~/assets/email-security/Email_security_Deployment_Inline.png)
 
-Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
+Refer to [Before you begin](/cloudflare-one/email-security/setup/) for a comprehensive comparison of each deployment method, and [Understanding Email Security Deployments](/reference-architecture/architectures/email-security-deployments/) to learn about each deployment method.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
index ddf2e2a40c90def..16e8a6a9cc6b7f5 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/prerequisites.mdx
@@ -8,4 +8,4 @@ products:
   - email-security
 ---
 
-To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account.
+To make the most of this learning path, make sure you have access to Microsoft 365 or Gmail account. 
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
index 891d3080a754f62..a83c5051a08616c 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/recommended-deployment-model.mdx
@@ -16,4 +16,4 @@ The API deployment with Email security offers:
 - Agentless deployment for Microsoft 365.
 - Office 365 directory integration to retrieve user and group information and prevent user impersonation.
 
-![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
+![Microsoft 365 API deployment diagram](~/assets/email-security/M365_API_Deployment_Graph.png)
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
index 3743a5c02f2a30e..28bf9247f9c6975 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx
@@ -11,4 +11,4 @@ products:
 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**.
-4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
+4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
index 1c65ac9d9434a5c..447dea2119c80ba 100644
--- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx
@@ -12,7 +12,7 @@ products:
 2. Select **Email security** > **Settings**.
 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**.
 4. Enable **Microsoft Integration**:
-   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration.
+   1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. 
    2. **Name integration**: Add your integration name, then select **Continue**.
    3. **Authorize integration**:
       - Select **Authorize**. Selecting **Authorize** will take you to the Microsoft Sign in page where you will have to enter your email address.
@@ -20,4 +20,4 @@ products:
       - After selecting **Next**, the system will show a dialog box with a list of requested permissions. Select **Accept** to authorize Email security. Upon authorization, you will be redirected to a page where you can review details and enroll integration.
    4. **Review details**: Review your integration details, then:
       - Select **Complete Email security set up** where you will be able to connect your domains and configure auto-moves.
-      - Select **Continue to Email security**.
+      - Select **Continue to Email security**.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
index 40565ed07e17558..e5a57972d2a82f0 100644
--- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
+++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx
@@ -17,4 +17,4 @@ There are two different ways to [submit a phish](/cloudflare-one/email-security/
   - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you.
 - Admin submission:
   - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address.
-  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
+  - Within the Email security dashboard, Phish submissions will allow you to have a full understanding of what reclassification has been made and what the outcomes of those submissions are.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
index 47bf090845f40be..3432b43cd002658 100644
--- a/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/concepts/index.mdx
@@ -20,15 +20,15 @@ To learn more about our service offerings, refer to [Customer Success offerings]
 
 For the security and protection of your account, be sure to register all account users.
 
-1. In the Cloudflare dashboard, go to the **Manage Account** > **Members** page.
+1. In the Cloudflare dashboard, go to the  **Manage Account** > **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+    <DashButton url="/?to=/:account/members" />
 
 2. Select more than one Super Administrator to ensure appropriate access when needed.
 
 :::note
 
-Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users.
+Refer to [Manage members](/fundamentals/manage-members/) to learn how to review and update registered account users. 
 
 :::
 
@@ -50,7 +50,7 @@ We strongly advise against credential-sharing which can jeopardize the trust and
   Certificates managed by Cloudflare are auto-renewed.
   :::
 - Review your Operational and Disaster recovery preparedness
-  - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
-  - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
+    - Enable Load Balancing with smart cache strategies: Use [Cloudflare Load Balancing](/reference-architecture/architectures/load-balancing) to distribute traffic across multiple healthy origins, and increase cache-hit ratios by leveraging [custom cache rules](/cache/performance-review/cache-analytics) and [edge compute](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) (e.g., Cloudflare Workers) to offload origin traffic during high-demand periods.
+    - Configure failover pools and back up DNS with a playbook: Set up [Cloudflare Load Balancer failover pools](/reference-architecture/architectures/load-balancing) to automatically redirect traffic to healthy origins if one fails. Export DNS records for safekeeping and prepare a clear [incident response plan](https://www.cloudflare.com/learning/performance/preventing-downtime) that includes steps for re-routing or recovery.
 - Review and update your current users' access
-- Check your domain registry validity
+- Check your domain registry validity
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
index d58062e1f6e2e72..11fe9044b199b1c 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/analytics.mdx
@@ -14,14 +14,16 @@ products:
 
 Use the [Workers Analytics Engine](/analytics/analytics-engine/) to send unlimited-cardinality data from your Worker to a time-series database. Query it with SQL.
 
+
 ## Account and zone analytics
 
 Use [Account and zone analytics](/analytics/account-and-zone-analytics/) to provide details about the requests and traffic related to your Cloudflare accounts and zones.
 
+
 ## Cloudflare Network Analytics
 
 Use [Cloudflare Network Analytics](/analytics/network-analytics/) to provide near real-time visibility into network and transport-layer traffic patterns and DDoS attacks.
 
 ## GraphQL Analytics API
 
-Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
+Use the [GraphQL Analytics API](/analytics/graphql-api/) to provide\ all of your performance, security, and reliability data from one endpoint. Select exactly what you need, from one metric for a domain to multiple metrics aggregated for your account.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
index 7be8e912c96ed9a..d594e17850fe651 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/caching.mdx
@@ -16,21 +16,26 @@ import { DashButton } from "~/components";
 
 By default, Cloudflare [caches static content](/cache/concepts/default-cache-behavior/) such as images, CSS, and JavaScript. However, you can extend Cloudflare caching to work with HTML by creating custom [Cache Rules](/cache/how-to/cache-rules/).
 
+
 ### Cache more requests
 
-1. In the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page.
+1. In  the Cloudflare dashboard, go to the **Caching** > **Cache Rules** page. 
 
-   <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
+    <DashButton url="/?to=/:account/:zone/caching/cache-rules" />
 
 2. Select **Create rule**.
 3. For When incoming requests match, enter either your entire website or a specific path on your application, based on the Hostname or URI Path. Refer to the [available fields](/cache/how-to/cache-rules/settings/#fields).
 4. For Cache eligibility, define how these requests should be cached and for how long. Refer to the available [cache eligibility settings](/cache/how-to/cache-rules/settings/#eligible-for-cache-settings).
 5. You can then monitor the effectiveness of your cache settings using [Cache Analytics](/cache/performance-review/cache-analytics/) and update your configuration according to our [Cache performance guide](/cache/performance-review/cache-performance/).
 
+
 ### Advanced cache optimizations
 
-- [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
-- [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
+
+
+* [Custom Cache Keys](/cache/how-to/cache-keys/) allows you to precisely set the cacheability setting for any resource.
+* [Origin Cache Control](/cache/concepts/cache-control/) can be used to let the Cache-Control headers tell Cloudflare how to handle content from the origin server.
+
 
 ## Tiered Cache
 
@@ -40,6 +45,7 @@ It works by dividing Cloudflare's data centers into a hierarchy of lower-tiers a
 
 Refer to [Enable Tiered Cache](/cache/how-to/tiered-cache/#enable-tiered-cache) to get started.
 
+
 ### Cache Reserve
 
 [Cache Reserve](/cache/advanced-configuration/cache-reserve/) is a large, persistent data store implemented on top of [R2](/r2/).
@@ -48,32 +54,38 @@ With a single click in the dashboard, your cacheable content will be written to
 
 This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
 
+
 ## Cloudflare Waiting Room
 
 [Cloudflare Waiting Room](/waiting-room/) allows you to route excess users of your website to a customized waiting room, helping preserve customer experience and protect origin servers from being overwhelmed with requests.
 
+
 ## Use Cloudflare IP addresses
 
 Take action to prevent attacks to your application during peak season by configuring your firewall to only accept traffic from Cloudflare IP addresses. By only allowing [Cloudflare IPs](https://www.cloudflare.com/ips), you can prevent attackers from bypassing Cloudflare and sending requests directly to your origin.
 
 Refer to [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) for more information.
 
+
 ## Monitor traffic
 
 You can use the Cloudflare dashboard to closely monitor the traffic on your domain and fine-tune your cache and security settings accordingly.
 
+
 ### Zone and Account analytics
 
 [Cloudflare zone analytics](/analytics/account-and-zone-analytics/zone-analytics/) gives you access to a wide range of metrics, collected at the website or domain level.
 
 [Cloudflare account analytics](/analytics/account-and-zone-analytics/account-analytics/) lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
 
+
 ### Security Analytics and Security Events
 
 [Security Analytics](/waf/analytics/security-analytics/) displays information about all incoming HTTP requests for your domain, including requests not handled by Cloudflare security products.
 
 You can also use the [Security Events](/waf/analytics/security-events/) to review mitigated requests and tailor your security configurations.
 
+
 ### Cache Analytics
 
-You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
+You can use [Cache Analytics](/cache/performance-review/cache-analytics/) to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
index 2655eccdda8256f..63efb8a1e0f3aef 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
index 6434accda802398..46f719837ac8da1 100644
--- a/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/performance/logs.mdx
@@ -14,14 +14,17 @@ products:
 
 Use [Logpush](/logs/logpush/) to push your request or event logs to your cloud service provider using Logpush, which can be configured via the Cloudflare dashboard or API.
 
+
 ## Instant Logs
 
 Use [Instant Logs](/logs/instant-logs/) to view HTTP request logs instantly in the Cloudflare dashboard or the CLI.
 
+
 ## Logs Engine
 
-Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.
+Use the [Logs Engine](/logs/r2-log-retrieval/) to store your logs in R2 and query them directly.  
+
 
 ## Log Explorer
 
-Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
+Use the [Log Explorer](/log-explorer/) to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API. 
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
index 075b1e688bd6801..07a1c32748a4a4b 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/block-agents-lock-zones.mdx
@@ -10,6 +10,7 @@ products:
   - ddos-protection
 ---
 
+
 [User Agent (UA) Blocking](/waf/tools/user-agent-blocking/) rules match against specific User-Agent request headers sent by the browser or application accessing your site. UA rules are applied against the entire domain, and after a rule is triggered, you can decide which action to take against the visitor.
 
 Actions:
diff --git a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
index c0d4fe2c9a50ebe..8a5b929f561880a 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/confirm-account-security.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Review the list below for guidance on securing your account.
 
-<DirectoryListing folder="fundamentals/account/account-security" />
+<DirectoryListing folder="fundamentals/account/account-security" />
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
index 8508360fa7d7ac7..9fb487a7190ccfd 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/control-domain-access.mdx
@@ -14,10 +14,13 @@ products:
 
 IP Access Rules can be applied based on:
 
-- IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
-- IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
-- ASN
-- Country or the Tor network
+
+
+* IPv4 address or range: Specified in CIDR notation as `/16` or `/24`
+* IPv6 address or range: Specified in CIDR notation as `/32`, `/48`, `/64`
+* ASN
+* Country or the Tor network
+
 
 :::note
 
@@ -31,3 +34,4 @@ Actions:
 - Non-Interactive Challenge: Visitors will be shown a non-interactive challenge before allowed access.
 - Interactive Challenge: Visitors will be shown an interactive challenge before allowed access.
 - Allowlist: Ensures that an IP address will never be blocked from accessing your site. This supersedes any Cloudflare security profile.
+
diff --git a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
index 2436739e7c61285..1c28bd66975b7dd 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/enable-iaum.mdx
@@ -1,7 +1,7 @@
 ---
 title: What to do when under attack
 pcx_content_type: overview
-sidebar:
+sidebar: 
   order: 9
 description: Respond to active DDoS attacks.
 products:
@@ -16,12 +16,14 @@ If you are under attack and have this feature enabled during the attack, visitor
 
 Refer to [I'm Under Attack Mode](https://developers.cloudflare.com/fundamentals/reference/under-attack-mode/) for more information.
 
+
 ## Change Access Control List (ACL)
 
 An ACL refers to rules that are applied to port numbers or IP addresses that are available on a host permitting use of the service. When you only allow Cloudflare IPs, you eliminate threats attempting to attack your origin IP range.
 
 Refer to [Cloudflare IP Ranges](https://www.cloudflare.com/ips) for more information.
 
+
 ## Change Origin IPs and update Cloudflare DNS records
 
 If your origin is still being attacked, consider moving your Origin IPs and updating your Cloudflare DNS records.
diff --git a/src/content/docs/learning-paths/surge-readiness/security/index.mdx b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
index 4e47eb5f69bf264..cd4191d21fbf2c9 100644
--- a/src/content/docs/learning-paths/surge-readiness/security/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/security/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/support/index.mdx b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
index 289654ff24ecd81..38e3bfb1f22fb97 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/index.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/index.mdx
@@ -10,4 +10,4 @@ products:
   - waf
   - cache
   - ddos-protection
----
+---
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
index 0ce3a91e3055cfd..1ae293e1c4a56e6 100644
--- a/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
+++ b/src/content/docs/learning-paths/surge-readiness/support/resources.mdx
@@ -10,14 +10,15 @@ products:
   - ddos-protection
 ---
 
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
-| Support type                                      | Resource                                                                                     |
-| ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| Self-serve questions                              | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals          |
-| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team                                                     |
-| Non-critical production issues (reactive)         | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
-| Critical issues such as attacks (reactive)        | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)       |
+
+| Support type | Resource |
+| ------------ | -------- |
+| Self-serve questions | https://support.cloudflare.com <br/> https://developers.cloudflare.com/fundamentals |
+| Strategic guidance and best practices (proactive) | Reach out to your dedicated account team |
+| Non-critical production issues (reactive) | - [Support portal](https://dash.cloudflare.com/?to=/:account/support) <br/> - Dashboard chat |
+| Critical issues such as attacks (reactive) | - Call the 24/7 Emergency Support line - www.cloudflare.com/ecp/support (global lines)| 
 
 :::note
 For security reasons, Cloudflare Support only assists individuals whose email addresses are validated against the list of registered account contacts. Review and update all contacts accordingly in your Cloudflare Dashboard. For more information, refer to [Manage members](/fundamentals/manage-members/).
diff --git a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
index 898e3bb0f7ac8ed..2865a6b3e04b8af 100644
--- a/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/cloudflare-intro.mdx
@@ -24,13 +24,13 @@ If your application is built on Cloudflare, then Cloudflare would act as the ori
 
 An example tech stack for an application built on Cloudflare would look like:
 
-- [Domain Registrar](/registrar/) to buy a new your domain.
-- [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
-- [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
-- [Storage resources](/workers/platform/storage-options/) to persist different types of data.
-- [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
-- [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
-- [AI](/use-cases/ai/) to run machine learning models.
+* [Domain Registrar](/registrar/) to buy a new your domain.
+* [Cloudflare Pages](/pages/) to configure and deploy a front-end site.
+* [Cloudflare Workers](/workers/) or [Pages Functions](/pages/functions/) (which are Workers under the hood) to add dynamic functionality to your site.
+* [Storage resources](/workers/platform/storage-options/) to persist different types of data.
+* [Application security (DDoS protection, WAF, and more)](https://www.cloudflare.com/application-services/products/#security-services) to secure your site.
+* [Application performance (CDN, Load Balancing, and more)](https://www.cloudflare.com/application-services/products/#performance-services) to customize and enhance your site's performance.
+* [AI](/use-cases/ai/) to run machine learning models.
 
 And more depending on your use case.
 
@@ -42,11 +42,11 @@ When you add your application to Cloudflare, Cloudflare's global network of serv
 
 After you add your application to [Cloudflare](/fundamentals/concepts/how-cloudflare-works/), you can:
 
-- Use Workers to augment the application by deploying code.
-- Add storage resources available on the Developer Platform.
-- Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
-- Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
-- Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
+* Use Workers to augment the application by deploying code.
+* Add storage resources available on the Developer Platform.
+* Enhance your application's performance by speeding up content delivery and user experience ([CDN](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)).
+* Protect your website from malicious activity ([DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) by configuring the [Web Application Firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)).
+* Route traffic ([Load balancing](/load-balancing/), [Waiting Room](/waiting-room/)).
 
 And more depending on your use case.
 
@@ -54,8 +54,8 @@ And more depending on your use case.
 
 By reading this page, you have:
 
-- Learned the scale of Cloudflare's global network.
-- Explored the product offering to know what Cloudflare can offer for users like you.
-- Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
+* Learned the scale of Cloudflare's global network.
+* Explored the product offering to know what Cloudflare can offer for users like you.
+* Reviewed how you can build your applications with Cloudflare and Cloudflare Workers.
 
 In the next section, you will be introduced to the fundamentals of serverless computing, the concept behind Cloudflare Workers.
diff --git a/src/content/docs/learning-paths/workers/concepts/index.mdx b/src/content/docs/learning-paths/workers/concepts/index.mdx
index 9837915441175e0..e293a2f1d9d87d7 100644
--- a/src/content/docs/learning-paths/workers/concepts/index.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/index.mdx
@@ -16,6 +16,6 @@ Learn the concepts behind what makes Cloudflare Workers reliable, scalable and f
 
 By the end of this module, you will learn:
 
-- What Cloudflare is.
-- The difference between serverless computing and cloud computing paradigms.
-- How Workers works.
+* What Cloudflare is.
+* The difference between serverless computing and cloud computing paradigms.
+* How Workers works.
diff --git a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
index c9f1788b07d3213..1fd5f921d05c1ed 100644
--- a/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
+++ b/src/content/docs/learning-paths/workers/concepts/serverless-computing.mdx
@@ -40,8 +40,8 @@ Developers and organizations using serverless computing are billed on a usage mo
 
 By reading this page, you have:
 
-- Been introduced to the serverless computing concept that is behind Cloudflare Workers.
-- Reviewed the differences between legacy on-premise and cloud computing infrastructure.
-- Analyzed the key differences between the cloud computing and serverless computing paradigms.
+* Been introduced to the serverless computing concept that is behind Cloudflare Workers.
+* Reviewed the differences between legacy on-premise and cloud computing infrastructure.
+* Analyzed the key differences between the cloud computing and serverless computing paradigms.
 
 In the next section, you will learn about what makes Workers, a serverless computing platform that is part of the larger Cloudflare Developer Platform, unique in its architecture from other serverless computing providers.
diff --git a/src/content/docs/learning-paths/workers/devplat/index.mdx b/src/content/docs/learning-paths/workers/devplat/index.mdx
index 365fd4fa0f8d551..f792c7ba4cbfda3 100644
--- a/src/content/docs/learning-paths/workers/devplat/index.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/index.mdx
@@ -16,5 +16,5 @@ The Cloudflare Developer Platform allows you to build full-stack applications wi
 
 By the end of this module, you will learn:
 
-- Cloudflare Developer Platform's product offering.
-- What storage options are available to your Worker.
+* Cloudflare Developer Platform's product offering.
+* What storage options are available to your Worker.
diff --git a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
index 5a516cca6e30fc3..20e6536f1ef0349 100644
--- a/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
+++ b/src/content/docs/learning-paths/workers/devplat/intro-to-devplat.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { Render, YouTube } from "~/components";
+import { Render, YouTube } from "~/components"
 
 The [Cloudflare Developer Platform](https://www.cloudflare.com/developer-platform/products/) offers various services to empower developers to build full-stack applications, including: [compute](https://www.cloudflare.com/developer-platform/products/#compute), [storage](https://www.cloudflare.com/developer-platform/products/#storage), [web development, image optimization, video streaming](https://www.cloudflare.com/developer-platform/products/#webdev) and [AI](https://ai.cloudflare.com/).
 
diff --git a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
index 491c0bb0dc6773c..4783f290410f89f 100644
--- a/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/c3-and-wrangler.mdx
@@ -18,8 +18,8 @@ You can build and develop your Worker on the Cloudflare dashboard, without needi
 
 The Cloudflare Developer Platform ecosystem has two command-line interfaces (CLI):
 
-- C3: To create new projects.
-- Wrangler: To build and deploy your projects.
+* C3: To create new projects.
+* Wrangler: To build and deploy your projects.
 
 ## C3
 
@@ -45,7 +45,7 @@ Cloudflare recommends choosing and using one [source of truth](/workers/wrangler
 
 By reading this page, you have learned:
 
-- How to use C3 to create new Workers and Pages projects.
-- How to use Wrangler to develop, configure, and delete your projects.
+* How to use C3 to create new Workers and Pages projects.
+* How to use Wrangler to develop, configure, and delete your projects.
 
 In the next section, you will learn more about the Cloudflare dashboard before moving on to deploy your first Worker.
diff --git a/src/content/docs/learning-paths/workers/get-started/first-application.mdx b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
index 5797be4e53286d6..422ae8875a66d14 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-application.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
@@ -9,7 +9,6 @@ description: Build an AI application with Hono.
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 ## Build an AI application with Hono and Workers
@@ -18,21 +17,21 @@ If you have already created your first Worker and want to learn what more you ca
 
 In this course, you will:
 
-- Deploy your first Worker.
-- Develop your application locally.
-- Add the Hono framework to your project.
-- Integrate Workers AI into your project.
+* Deploy your first Worker.
+* Develop your application locally.
+* Add the Hono framework to your project.
+* Integrate Workers AI into your project.
 
 <div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
+    <iframe
+        src="https://customer-1mwganm1ma0xgnmj.cloudflarestream.com/7cb5528acbea8502c810781e1970b453/iframe?preload=true&letterboxColor=transparent"
+        style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+        allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+        allowfullscreen="true">
+    </iframe>
 </div>
 
-<br />
+<br/>
 
 Find [the video on YouTube](https://youtu.be/H7Qe96fqg1M?si=GVkdGLrmb1faiHma) and explore other Cloudflare Workers tutorials.
 
diff --git a/src/content/docs/learning-paths/workers/get-started/index.mdx b/src/content/docs/learning-paths/workers/get-started/index.mdx
index a25e920d7e95452..39b04e54f6794eb 100644
--- a/src/content/docs/learning-paths/workers/get-started/index.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/index.mdx
@@ -14,6 +14,6 @@ Deploy your first Worker to the Cloudflare global network by
 
 By the end of this module, you will learn:
 
-- The difference between C3 (`create-cloudflare` CLI) and Wrangler.
-- How to use the Cloudflare dashboard to manage your Workers.
-- How to create and deploy your first Worker.
+* The difference between C3 (`create-cloudflare` CLI) and Wrangler.
+* How to use the Cloudflare dashboard to manage your Workers.
+* How to create and deploy your first Worker.
diff --git a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
index a01215316a0f040..cc182b7d7c81178 100644
--- a/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
+++ b/src/content/docs/load-balancing/additional-options/additional-dns-records.mdx
@@ -7,6 +7,7 @@ products:
 head:
   - tag: title
     content: Load balance additional DNS records
+
 ---
 
 In addition to load balancing between DNS records used for IP resolution — `A`, `AAAA`, and `CNAME` records — Enterprise customers can also load balance between **MX** and **SRV** records.
@@ -16,7 +17,7 @@ In addition to load balancing between DNS records used for IP resolution — `A`
 To load balance between multiple mail servers:
 
 1. Make sure you have the [required DNS records](/dns/manage-dns-records/how-to/email-records/#send-and-receive-email) for your mail servers.
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _SMTP_.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *SMTP*.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your mail servers and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. Since it will forward SMTP traffic, the load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
 
@@ -25,6 +26,6 @@ To load balance between multiple mail servers:
 To load balance between different **SRV** records, which contain significantly more information than many other DNS records:
 
 1. [Create your SRV records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records).
-2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of _UDP-ICMP_ or _TCP_.
+2. [Create a monitor](/load-balancing/monitors/create-monitor/) with a **Type** of *UDP-ICMP* or *TCP*.
 3. [Create a pool](/load-balancing/pools/create-pool/) with your various SRV records and attach the newly created monitor.
 4. [Create a load balancer](/load-balancing/load-balancers/create-load-balancer/) that includes your newly created pools. This load balancer should be [unproxied (DNS-only)](/load-balancing/understand-basics/proxy-modes/#dns-only-load-balancing).
diff --git a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
index 826228781b9546b..26703586383732d 100644
--- a/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
+++ b/src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Route traffic through a Cloudflare Tunnel
+
 ---
 
 Cloudflare Tunnel (formerly Argo Tunnel) establishes a secure outbound connection which runs in your infrastructure to connect the applications and machines to Cloudflare.
diff --git a/src/content/docs/load-balancing/additional-options/index.mdx b/src/content/docs/load-balancing/additional-options/index.mdx
index 67bfe4b67c3ffd3..fa8021c02caae66 100644
--- a/src/content/docs/load-balancing/additional-options/index.mdx
+++ b/src/content/docs/load-balancing/additional-options/index.mdx
@@ -6,21 +6,22 @@ products:
 title: Additional configuration
 sidebar:
   order: 49
+
 ---
 
 Beyond [creating a simple load balancer](/load-balancing/load-balancers/create-load-balancer/), you may want to further customize how your load balancer routes traffic or integrate your load balancer with other Cloudflare products.
 
 ## Customize load balancer behavior
 
-- Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
-- Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
-- Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
+* Route traffic according to characteristics of each request by [creating custom rules](/load-balancing/additional-options/load-balancing-rules/)
+* Protect at-risk endpoints from reaching failover by [setting up load shedding](/load-balancing/additional-options/load-shedding/)
+* Take endpoints out of rotation for [planned maintenance](/load-balancing/additional-options/planned-maintenance/)
 
 ## Integrate with other Cloudflare products
 
-- Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
-- Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
+* Bring load balancing to your TCP or UDP applications with [Cloudflare Spectrum](/load-balancing/additional-options/spectrum/)
+* Further secure endpoint access with [Cloudflare Tunnel](/load-balancing/additional-options/cloudflare-tunnel/)
 
 ## Integrate with 3rd parties
 
-- Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
+* Increase visibility by [sending health monitor notifications to PagerDuty](/load-balancing/additional-options/pagerduty-integration/)
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
index e0591ff2cfa42ea..ce90921b4f41919 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-china.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Balancing with the China Network
 sidebar:
   order: 15
+
 ---
 
 ## Prerequisites
diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
index ef52ac1aafb7236..3fa85bff4993517 100644
--- a/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
+++ b/src/content/docs/load-balancing/additional-options/load-balancing-rules/expressions.mdx
@@ -9,15 +9,16 @@ sidebar:
 head:
   - tag: title
     content: Load Balancing expressions
+
 ---
 
 [Load Balancing rules](/load-balancing/additional-options/load-balancing-rules/) use two kinds of expressions:
 
-- [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (_equals_ or _less than_, for example).
+* [Simple expressions](#simple-expressions) compare a value from an HTTP request to a value defined in the expression. A simple expression is identified by the presence of a **comparison operator** (*equals* or *less than*, for example).
 
-- [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (_and_, _or_, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
+* [Compound expressions](#compound-expressions) combine two or more simple expressions into a single expression. Compound expression contains a **logical operator** (*and*, *or*, for example). With compound expressions you can tailor rules to specific use cases with a high degree of accuracy and precision.
 
----
+***
 
 ## Simple expressions
 
@@ -43,11 +44,11 @@ In general, simple expressions use this pattern:
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
----
+***
 
 ## Compound expressions
 
-A compound expression uses a **logical operator** (_and_, _or_, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
+A compound expression uses a **logical operator** (*and*, *or*, for example) to combine two or more expressions. Compound expressions allow you to build complex statements within a single expression.
 
 The example expression below returns true when both the HTTP request URI path contains `/content` and the query string contains `webserver`:
 
@@ -66,7 +67,7 @@ A compound expression can be an operand of a logical operator. This allows multi
 
 For more details, refer to [Supported fields and operators](/load-balancing/additional-options/load-balancing-rules/reference/).
 
----
+***
 
 ## Working with expressions
 
diff --git a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
index ec4cd87db9d1d86..135607380a8e453 100644
--- a/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
+++ b/src/content/docs/load-balancing/additional-options/override-http-host-headers.mdx
@@ -6,16 +6,19 @@ products:
 title: Override HTTP Host headers
 sidebar:
   order: 16
+
 ---
 
 When your application needs specialized routing (`CNAME` setup or custom hosts like Heroku), you can customize the `Host` header used in health monitors on a per-endpoint or per-monitor level.
 
 :::caution[Important]
 
+
 If you set a header override on an individual endpoint, it will take precedence over a header override set on a monitor.
 
 Also, if you configure an [Origin Rule](/rules/origin-rules/) that overrides the hostname and set up a header override in your Load Balancer configuration, the Load Balancer configuration will take precedence over the Origin Rule hostname override.
 
+
 :::
 
 ## Per endpoint Host header override
@@ -24,13 +27,13 @@ To balance traffic across multiple hosts, add `Host` headers to individual endpo
 
 For example, you might have a pool with endpoints hosted in multiple AppEngine projects or Amazon S3 buckets. You also might want to set up specific failover endpoints within a pool.
 
-Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic _without_ a `Host` header override.
+Since these examples require specific hostnames per endpoint, your load balancer will not properly route traffic *without* a `Host` header override.
 
 If you need an endpoint `Host` header override, add it when [creating](/load-balancing/pools/create-pool/) or editing a pool. For security reasons, this header must meet one of the following criteria:
 
-- Is a subdomain of a zone associated with this account
-- Matches the endpoint address
-- Publicly resolves to the endpoint address
+* Is a subdomain of a zone associated with this account
+* Matches the endpoint address
+* Publicly resolves to the endpoint address
 
 ## Host header prioritization
 
@@ -38,16 +41,19 @@ If you set a header override on an individual endpoint, it will take precedence
 
 For example, you might have a load balancer for `www.example.com` with the following setup:
 
-- Pools:
-  - Pool 1:
-    - Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
-    - Endpoint 2
+* Pools:
+
+  * Pool 1:
+
+    * Endpoint 1 (`Host` header set to `lb-app-a.example.com`)
+    * Endpoint 2
+
+  * Pool 2:
 
-  - Pool 2:
-    - Endpoint 3
-    - Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
+    * Endpoint 3
+    * Endpoint 4 (`Host` header set to `lb-app-b.example.com`)
 
-- Monitor (`Host` header set to `www.example.com`)
+* Monitor (`Host` header set to `www.example.com`)
 
 In this scenario, health monitor requests for **Endpoint 1** would use `lb-app-a.example.com`, health monitor requests for **Endpoint 4** would use `lb-app-b.example.com`, and all other health monitor requests would default to `www.example.com`. For more information on updating your custom host configuration to be compatible with Cloudflare, see [Configure Cloudflare and Heroku over HTTPS](/support/third-party-software/others/configure-cloudflare-and-heroku-over-https/).
 
diff --git a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
index f9d25700c2ef3e6..800fefee9fab77d 100644
--- a/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
+++ b/src/content/docs/load-balancing/additional-options/pagerduty-integration.mdx
@@ -6,6 +6,7 @@ products:
 title: Integrate with PagerDuty
 sidebar:
   order: 41
+
 ---
 
 To integrate Cloudflare health monitor notifications with PagerDuty, follow the steps outlined in PagerDuty’s [Email Integration Guide](https://www.pagerduty.com/docs/guides/email-integration-guide/). If you do not have a PagerDuty account, you will first need to set that up.
diff --git a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
index 934c8b9eaad2618..44d8e5917088c19 100644
--- a/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
+++ b/src/content/docs/load-balancing/additional-options/planned-maintenance.mdx
@@ -18,8 +18,10 @@ To direct traffic away from your endpoint immediately, [adjust settings on the p
 
 :::note
 
+
 If you want to divert traffic from an endpoint to prevent it from becoming unhealthy, use [Load Shedding](/load-balancing/additional-options/load-shedding/) instead.
 
+
 :::
 
 ## Before you begin
@@ -32,8 +34,10 @@ If a pool falls below its **Health Threshold**, it will be considered **Unhealth
 
 :::note
 
+
 Endpoint drain is only available for [proxied load balancers (orange-clouded)](/load-balancing/understand-basics/proxy-modes/).
 
+
 :::
 
 With [session-based load balancing](/load-balancing/understand-basics/session-affinity/), it is important to direct all requests from a particular end user to a specific endpoint. Otherwise, information about the user session — such as items in their shopping cart — may be lost and lead to negative business outcomes.
@@ -59,10 +63,10 @@ To remove an endpoint from rotation while still preserving session continuity, s
 To direct traffic away from an endpoint immediately:
 
 1. Do one of the following actions:
-   - On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
-   - On the pool, disable the endpoint.
-   - On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
+   * On the endpoint's [monitor](/load-balancing/monitors/), update the monitor settings so the endpoint will fail health monitor requests, such as putting an incorrect value for the **Response Body** or **Response Code**.
+   * On the pool, disable the endpoint.
+   * On the pool, set the [endpoint weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to `0` (though traffic may still reach the endpoint if it is included in multiple pools).
 2. Monitor [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/) to make sure no requests are reaching the pool.
-   - If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
+   * If you are using [DNS-only load balancing (gray-clouded)](/load-balancing/understand-basics/proxy-modes/), changes may be delayed due to DNS resolver caching.
 3. Perform your required maintenance or upgrades.
 4. Undo the changes you made in **Step 1**.
diff --git a/src/content/docs/load-balancing/api-reference.mdx b/src/content/docs/load-balancing/api-reference.mdx
index 5fcef7600b948c2..beaae8039b92f86 100644
--- a/src/content/docs/load-balancing/api-reference.mdx
+++ b/src/content/docs/load-balancing/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/load_balancers/methods/get/
 sidebar:
   order: 152
+
 ---
diff --git a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
index 290ae83ee3bfbe9..2d257351a66f0cf 100644
--- a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
+++ b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx
@@ -9,9 +9,10 @@ head:
   - tag: title
     content: Enable Load Balancing
 description: Learn how to enable load balancing.
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Load balancing is an add-on for your account, meaning your account needs a [billing profile](/billing/get-started/create-billing-profile/).
 
diff --git a/src/content/docs/load-balancing/get-started/index.mdx b/src/content/docs/load-balancing/get-started/index.mdx
index 42931ed740f8d8a..718f24899007689 100644
--- a/src/content/docs/load-balancing/get-started/index.mdx
+++ b/src/content/docs/load-balancing/get-started/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Get started
 sidebar:
   order: 1
+
 ---
 
 Get started with load balancing in one of two ways:
 
-- [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
-- [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
+* [Quickstart](/load-balancing/get-started/quickstart/): Get up and running quickly with Load Balancing.
+* [Learning path](/learning-paths/load-balancing/concepts/): Check an in-depth walkthrough for how to plan and set up a load balancer.
diff --git a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
index 9e97aeac3cc0923..47be390136f8260 100644
--- a/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
+++ b/src/content/docs/load-balancing/load-balancers/common-configurations.mdx
@@ -6,6 +6,7 @@ products:
 title: Common configurations
 sidebar:
   order: 6
+
 ---
 
 Consider the following sections to understand how to achieve some commonly used load balancer configurations.
@@ -38,11 +39,13 @@ This setup speeds up overall requests, but is more vulnerable to planned or unpl
 
 To set up a load balancer with **active-active failover**, either:
 
-- Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
-- Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
+* Create a load balancer with a single pool (`primary`) with multiple endpoints (`endpoint-1` and `endpoint-2`) and set the same [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) for each endpoint.
+* Create a load balancer with two pools (`primary` and `secondary`) and — for [**Traffic Steering**](/load-balancing/understand-basics/traffic-steering/steering-policies/) — select any option except for **Off**.
 
 :::note
 
+
 For more background reading on server failover and common configurations, refer to [our Learning Center](https://www.cloudflare.com/learning/performance/what-is-server-failover/).
 
+
 :::
diff --git a/src/content/docs/load-balancing/monitors/index.mdx b/src/content/docs/load-balancing/monitors/index.mdx
index 1e9332fef2a2c18..4f3257567e10daf 100644
--- a/src/content/docs/load-balancing/monitors/index.mdx
+++ b/src/content/docs/load-balancing/monitors/index.mdx
@@ -86,6 +86,6 @@ The following table summarizes the different types of monitors available in Clou
 | ------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | HTTP/HTTPS   | Public and private | Used for HTTP and HTTPS endpoints with specific protocol attributes.                                                                                                                       | The probe is configured with settings and success criteria such as Method, Simulate Zone, Follow Redirects, Request Headers, and Response Body. The probe then evaluates the configured success criteria using the HTTP protocol. Throughout the configured timeout period, the TCP connection is kept active using [keep-alives](/fundamentals/reference/tcp-connections/#tcp-connections-and-keep-alives), even if no response is received. | Success is based on meeting the configured HTTP success criteria. No response within the configured timeout and retries is considered unhealthy.   |
 | TCP          | Public and private | Checks TCP connectivity by attempting to open a connection to the endpoint.                                                                                                                | The monitor sends a TCP SYN message to the specified port. A successful health check requires receiving a SYN/ACK message to establish the connection. The connection is closed by sending a FIN or RST packet, or by receiving a FIN packet from the endpoint.                                                                                                                                                                               | Failure to establish a TCP connection within the configured timeout and retries is considered unhealthy.                                           |
-| ICMP Ping    | Public and Tunnel  | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
-| UDP-ICMP     | Public and Tunnel  | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
+| ICMP Ping    | Public and Tunnel | Confirms basic Layer 3 (L3) connectivity to the endpoint using ICMP. The endpoints need to be allowed to reply to ICMP packets and any intervening networking equipment must support ICMP. | The monitor sends an ICMP/ICMPv6 echo request (ping) and expects an ICMP/ICMPv6 echo reply from the endpoint.                                                                                                                                                                                                                                                                                                                                 | The endpoint must reply to the ICMP ping within the configured timeout and retries to be considered healthy.                                       |
+| UDP-ICMP     | Public and Tunnel | UDP-ICMP monitor works by sending a UDP probe packet after ICMP Ping monitor completes as healthy.                                                                                         | After receiving a successful ICMP reply, the monitor sends a UDP probe packet to the endpoint. If no ICMP Port Unreachable message is received, the endpoint is considered healthy.                                                                                                                                                                                                                                                           | If the monitor receives an ICMP Port Unreachable message within the configured timeout and retries, the endpoint is considered unhealthy.          |
 | SMTP         | Public             | Verifies SMTP availability at the application layer.                                                                                                                                       | The monitor establishes a TCP connection and sends an SMTP HELO command. It expects a reply with code 250. The monitor then sends an SMTP QUIT command, expecting a reply with code 221. At the end of each interval, the TCP connection is closed by sending a TCP FIN packet.                                                                                                                                                               | The endpoint must respond with correct SMTP codes (250 for HELO, 221 for QUIT) within the configured timeout and retries to be considered healthy. |
diff --git a/src/content/docs/load-balancing/monitors/monitor-groups.mdx b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
index c9523c593355ecb..50904c9a7de3215 100644
--- a/src/content/docs/load-balancing/monitors/monitor-groups.mdx
+++ b/src/content/docs/load-balancing/monitors/monitor-groups.mdx
@@ -6,6 +6,7 @@ products:
 title: Monitor Groups
 sidebar:
   order: 48
+
 ---
 
 Group multiple health monitors together to create sophisticated health checks for your applications, ensuring more intelligent and resilient traffic steering.
diff --git a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
index 3d3b8c26fad9827..db0595b89b0b6ef 100644
--- a/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
+++ b/src/content/docs/load-balancing/private-network/cloudflare-wan.mdx
@@ -33,10 +33,8 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to
 1. Go to **Load Balancing** at the account level and select **Create a Load Balancer**.
 2. Select **Private Load Balancer**.
 3. On the next step you can choose to associate this load balancer with either:
-
-- A CGNAT IP from the Cloudflare range or
-- A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
-
+ - A CGNAT IP from the Cloudflare range or
+ - A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918).
 4. Add a descriptive name to identify your Load Balancer.
 5. Proceed through the setup.
 
diff --git a/src/content/docs/load-balancing/reference-architecture-external-link.mdx b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
index 0183c3d39e2e8f3..09dbce736aec377 100644
--- a/src/content/docs/load-balancing/reference-architecture-external-link.mdx
+++ b/src/content/docs/load-balancing/reference-architecture-external-link.mdx
@@ -7,4 +7,5 @@ title: Reference architecture
 external_link: /reference-architecture/architectures/load-balancing/
 sidebar:
   order: 150
+
 ---
diff --git a/src/content/docs/load-balancing/reference/index.mdx b/src/content/docs/load-balancing/reference/index.mdx
index e6f4d8d2d6c3b20..ec8770d1780404a 100644
--- a/src/content/docs/load-balancing/reference/index.mdx
+++ b/src/content/docs/load-balancing/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 50
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 See the following pages for more information about Cloudflare Load Balancing:
 
diff --git a/src/content/docs/load-balancing/reference/limitations.mdx b/src/content/docs/load-balancing/reference/limitations.mdx
index c46c0f6c8a12462..5bde030458bc22e 100644
--- a/src/content/docs/load-balancing/reference/limitations.mdx
+++ b/src/content/docs/load-balancing/reference/limitations.mdx
@@ -6,12 +6,13 @@ products:
 title: Limitations
 sidebar:
   order: 48
+
 ---
 
-| Name              | Non-Enterprise           | Enterprise               |
-| ----------------- | ------------------------ | ------------------------ |
-| Load balancers    | 20                       | custom                   |
-| Monitor intervals | 15s (min), 3600s (max)   | 10s (min), 3600s (max)   |
-| Monitors          | 1.5x the number of pools | 1.5x the number of pools |
-| Endpoints         | 20                       | custom                   |
-| Pools             | 20                       | custom                   |
+ Name | Non-Enterprise | Enterprise |
+ --- | --- | --- |
+ Load balancers | 20 | custom |
+ Monitor intervals | 15s (min), 3600s (max) | 10s (min), 3600s (max) |
+ Monitors | 1.5x the number of pools | 1.5x the number of pools |
+ Endpoints | 20 | custom |
+ Pools | 20 | custom |
diff --git a/src/content/docs/load-balancing/reference/migration-guides/index.mdx b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
index f1e1ae6e2a682da..aecc03630e37bc8 100644
--- a/src/content/docs/load-balancing/reference/migration-guides/index.mdx
+++ b/src/content/docs/load-balancing/reference/migration-guides/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
index 9f0e7e87097a25c..ede4a1cdcb502e9 100644
--- a/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/common-error-codes.mdx
@@ -6,6 +6,7 @@ products:
 title: Common error codes
 sidebar:
   order: 51
+
 ---
 
 The Cloudflare Load Balancing API adds global health to each pool and endpoint. It also gives you a view into what our network sees at a wider level. Cloudflare uses a quorum system to determine pool and endpoint health status. The quorum is taken from PoPs responsible for running health monitor requests in a region, and the majority result is used.
@@ -22,7 +23,7 @@ If a health monitor request fails, the breakdown will include the reason.
 
 Common troubleshooting causes and solutions are listed below.
 
----
+***
 
 ## TCP connection failed
 
@@ -34,7 +35,7 @@ Our health monitor requests failed to establish a TCP connection to your endpoin
 
 This typically occurs when there is a network failure between Cloudflare and your endpoint, and/or a firewall refused to allow our connection. Ensure your network and firewall configurations are not interfering with load balancing traffic.
 
----
+***
 
 ## HTTP timeout occurred
 
@@ -46,7 +47,7 @@ The endpoint failed to return an HTTP response within the timeout configured. Th
 
 We recommend increasing the HTTP response timeout to allow the endpoint to respond.
 
----
+***
 
 ## Response code mismatch error
 
@@ -66,7 +67,7 @@ You may also see this issue if you have a monitor configured to use HTTP connect
 
 Either change your Cloudflare monitor configuration to use HTTPS, or set the value of `follow_redirect` to `true` so that we can resolve the correct status code.
 
----
+***
 
 ## Response body mismatch error
 
@@ -74,13 +75,13 @@ Either change your Cloudflare monitor configuration to use HTTPS, or set the val
 
 The response body returns from your endpoint and does not include the (case-insensitive) value of `expected_body` configured in your monitor.
 
-Note that we only read the first 10 KB of the response. If you return a larger response, and the expected_body is not in the first 10 KB, the health monitor request will fail.
+Note that we only read the first 10 KB of the response. If you return a larger response, and the expected\_body is not in the first 10 KB, the health monitor request will fail.
 
 ### Solution
 
-Ensure the expected_body is in the first 10 KB of the response body.
+Ensure the expected\_body is in the first 10 KB of the response body.
 
----
+***
 
 ## TLS untrusted certificate error
 
@@ -92,7 +93,7 @@ The certificate is not trusted by a public Certificate Authority (CA).
 
 If you're using a self-signed certificate, we recommend either using a publicly trusted certificate or setting the `allow_insecure` property on your monitor to `true`.
 
----
+***
 
 ## TLS name mismatch error
 
@@ -104,7 +105,7 @@ Our health monitor (client) was not able to match a name on the server certifica
 
 Use the List Monitors command to confirm that the `header` value set in the Cloudflare monitor is correct and the Update Monitors command to make any necessary changes.
 
----
+***
 
 ## TLS protocol error
 
@@ -116,7 +117,7 @@ This error can occur if you’re using an older version of TLS or your endpoint
 
 Ensure that your endpoint supports TLS 1.0 or greater and is configured for HTTPS.
 
----
+***
 
 ## TLS unrecognized name error
 
@@ -128,7 +129,7 @@ The server did not recognize the name provided by the client. When a host header
 
 Set the host header in your monitor object.
 
----
+***
 
 ## No route to host error
 
@@ -140,7 +141,7 @@ The IP address cannot be reached from our network. Common causes are ISP or host
 
 Make sure IP is accurate, and if it is check if there is an ISP or hosting provider network issue.
 
----
+***
 
 ## Exceeded quota error
 
@@ -154,10 +155,10 @@ If you're using the **Cloudflare API**, you will receive an error message.
 
 ### Solution
 
-- Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
-- Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
+* Enterprise customers who need to create more objects (load balancers, pools, endpoints, or monitors) should reach out to their account team to discuss this issue.
+* Self-service customers can upgrade their Load Balancing subscription with more endpoints to increase load balancing capacity.
 
----
+***
 
 ## TCP Timeout
 
@@ -169,7 +170,7 @@ Data transmission was not acknowledged and retransmit of data did not succeed.
 
 Confirm whether the SYN-ACK for the handshake takes place at your endpoint and [contact Cloudflare Support](/support/contacting-cloudflare-support/).
 
----
+***
 
 ## TLS Handshake Failure
 
@@ -181,7 +182,7 @@ Indicates that the browser's connection to the web server is not secure.
 
 Change wifi networks, connect to a wired network, or verify the network connection is stable.
 
----
+***
 
 ## Network Unreachable
 
@@ -193,7 +194,7 @@ Cloudflare cannot connect to the endpoint due to network unavailability. This is
 
 Check either the IP entered for the endpoint in Cloudflare's Load Balancer configuration or the IP returned via DNS for the endpoint hostname.
 
----
+***
 
 ## HTTP Invalid Response
 
@@ -205,7 +206,7 @@ Usually caused by an HTTP 502 error or bad gateway.
 
 Ensure the endpoint responds to requests and that no applications have crashed or are under high load.
 
----
+***
 
 ## DNS Unknown Host
 
@@ -217,7 +218,7 @@ The endpoint hostname does not exist.
 
 Confirm the endpoint resolves to an IP address.
 
----
+***
 
 ## Connection Reset by Peer
 
@@ -229,7 +230,7 @@ A network error occurred while the client received data from the endpoint.
 
 Confirm whether the endpoint is experiencing a high amount of traffic or an error.
 
----
+***
 
 ## Monitor Config Error
 
@@ -241,7 +242,7 @@ There was a configuration error in the monitor and no checks are run against the
 
 Review your monitor configuration to ensure it matches an expected request to your endpoint.
 
----
+***
 
 ## DNS Internal
 
@@ -253,7 +254,7 @@ The endpoint's hostname resolves to an internal or orange-clouded IP address. No
 
 Cloudflare does not allow use of an endpoint hostname that is proxied by Cloudflare.
 
----
+***
 
 ## Load Balancing Not Enabled
 
@@ -265,7 +266,7 @@ Load Balancing is not enabled for your account or zone.
 
 For Enterprise customers, reach out to your Cloudflare Account Team. Free, Pro, and Business customers should [Enable Load Balancing](/load-balancing/get-started/enable-load-balancing/).
 
----
+***
 
 ## Validation failed error
 
@@ -277,7 +278,7 @@ You will receive an error if you try to set the host header value while configur
 
 Cloudflare now restricts configured [endpoint host headers](/load-balancing/additional-options/override-http-host-headers/) to fully qualified domain names (FQDNs) that are immediate subdomains of a zone associated with the account. For example, this host header would be the same zone as the load balancer itself, but pools may be used across multiple Load balancers.
 
----
+***
 
 ## Object referenced by other objects
 
@@ -289,7 +290,7 @@ You will receive this error when you attempt to delete a pool that is referenced
 
 Remove the pool from the load balancer's geo steering configuration. If your load balancer no longer uses geo steering, you will need to [re-enable geo steering](/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering/) and then remove the pool.
 
----
+***
 
 ## Other Failure
 
diff --git a/src/content/docs/load-balancing/troubleshooting/index.mdx b/src/content/docs/load-balancing/troubleshooting/index.mdx
index 2a9154394f0dda7..ab1582dd07df552 100644
--- a/src/content/docs/load-balancing/troubleshooting/index.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 151
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more guidance related to common issues with load balancers, refer to the following resources:
 
diff --git a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
index 49722335e1400f4..f9b35fca372872e 100644
--- a/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
+++ b/src/content/docs/load-balancing/troubleshooting/load-balancing-faq.mdx
@@ -4,6 +4,7 @@ description: Answers to common Load Balancing questions.
 products:
   - load-balancing
 title: FAQs
+
 ---
 
 ## Overview
@@ -16,7 +17,7 @@ Are you trying to turn on Load Balancing? [Enable Load
 Balancing](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing).
 :::
 
----
+***
 
 ## Why is my origin receiving so many health monitor requests?
 
@@ -34,7 +35,7 @@ To reduce traffic, reduce the number of selected regions or choose an option bes
 
 If you have a low interval for your health monitor requests, you may increase the traffic sent to your endpoints.
 
----
+***
 
 ## Why is my endpoint or pool considered unhealthy?
 
@@ -42,15 +43,15 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 If you know that your endpoint is healthy but load balancing is reporting it as unhealthy, check the following settings on the [monitor](/load-balancing/monitors):
 
-- Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
-- Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
-- If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
-- If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
-- Try increasing the **Timeout** value.
-- Review the **Host Header** for the health monitor.
-- If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
+* Perform a `curl` request against the configured endpoint. Make sure the response you are seeing matches your settings for the monitor.
+* Ensure your firewall or web server does not block or rate limit [our health monitors](/fundamentals/reference/cloudflare-site-crawling/#specific-products) and accepts requests from [Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
+* If you are looking for a specific value in the **Response Body**, make sure that value is relatively static and within the first 10 KB of the HTML page.
+* If your endpoint responds with a `301` or `302` status code, make sure **Follow Redirects** is selected.
+* Try increasing the **Timeout** value.
+* Review the **Host Header** for the health monitor.
+* If you are using [Authenticated Origin Pulls (mTLS)](/ssl/origin-configuration/authenticated-origin-pull/), [Argo Smart Routing](/argo-smart-routing/), [Bring your own CA (mTLS)](/ssl/client-certificates/byo-ca/), [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), or require [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/), make sure that you entered a zone value for **Simulate Zone** corresponding to the zone with these features configured.
 
----
+***
 
 ## Why does my load balancer route traffic to a secondary pool when the primary pool is still healthy?
 
@@ -58,7 +59,7 @@ You occasionally might see traffic routed away from a pool if a health monitor r
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
----
+***
 
 ## What happens when a pool or endpoint becomes unhealthy?
 
@@ -76,7 +77,7 @@ To avoid these scenarios:
 
 To learn more about how endpoints and pools become unhealthy, refer to [Endpoint and pool health](/load-balancing/understand-basics/health-details).
 
----
+***
 
 ## What is the difference between Load Balancing and Health Checks?
 
@@ -84,7 +85,7 @@ To learn more about how endpoints and pools become unhealthy, refer to [Endpoint
 
 [Cloudflare Health Checks](/health-checks/) are identical to monitors within a load balancer, but only meant for probing server health (and not distributing traffic).
 
----
+***
 
 ## Why do I see different numbers of requests in Load Balancing Analytics?
 
@@ -92,16 +93,16 @@ You may see different numbers of requests when reviewing [Load Balancing Analyti
 
 Load balancing **requests** are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds. This built-in caching is often the cause of an discrepancies.
 
----
+***
 
 ## I'm seeing a specific error code for my load balancer or monitor.
 
 For a list of specific error codes and next steps, refer to [Load Balancing Troubleshooting](/load-balancing/troubleshooting).
 
----
+***
 
 ## Related resources
 
-- [Endpoint and pool health](/load-balancing/understand-basics/health-details)
-- [Monitors](/load-balancing/monitors)
-- [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
+* [Endpoint and pool health](/load-balancing/understand-basics/health-details)
+* [Monitors](/load-balancing/monitors)
+* [Load Balancing Analytics](/load-balancing/reference/load-balancing-analytics/)
diff --git a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
index 0d58152b129b64d..5932d2fa80bf195 100644
--- a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
+++ b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx
@@ -6,9 +6,10 @@ products:
 title: Adaptive routing
 sidebar:
   order: 18
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Adaptive routing controls features that modify the routing of requests to pools and endpoints in response to dynamic conditions, such as during the interval between active health monitoring requests. <Render file="zero-downtime-failover-retry-on-error" product="fundamentals" />
 
diff --git a/src/content/docs/load-balancing/understand-basics/index.mdx b/src/content/docs/load-balancing/understand-basics/index.mdx
index 792addac1391985..c85c1403d1845cf 100644
--- a/src/content/docs/load-balancing/understand-basics/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 2
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review the following topics to learn more about the basic concepts and components involved in Cloudflare Load Balancing.
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
index 923d4f04f8cf0f3..fdba031ab13f323 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/index.mdx
@@ -6,6 +6,7 @@ products:
 title: Traffic steering
 sidebar:
   order: 4
+
 ---
 
 When requests come to your load balancer, it distributes them across your pools and endpoints according to three factors:
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
index 4cdb38526cfe80e..0c4c24f3ea88b14 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/hash-origin-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Hash steering
+
 ---
 
 **Hash steering** guides Cloudflare to send requests to endpoints based on a combination of [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) and previous requests from that IP address. Ensures requests from the same IP address will hit the same endpoint, but actual traffic distribution may differ from endpoint weights.
@@ -22,3 +23,6 @@ When a request originates from a browser, it lacks an `x-forwarded-for` header,
 ### Workaround
 
 To ensure Hash Steering works correctly when using a Worker in front of a Load Balancer, manually set the `x-forwarded-for` header in the Worker to the client's original IP address. By manually setting `x-forwarded-for` to `CF-Connecting-IP`, Hash Steering will function as expected, ensuring traffic consistency for end users.
+
+
+
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
index 02a10b15022975c..c51194139beb164 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/least-outstanding-requests-pools.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Endpoint-level steering
+
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to endpoints that currently have the lowest number of outstanding requests.
@@ -21,9 +22,9 @@ Least Outstanding Requests steering is best to use if your endpoints are easily
 
 ```json title="Pools"
 {
-	"origin_steering": {
-		"policy": "least_outstanding_requests"
-	}
+  "origin_steering": {
+    "policy": "least_outstanding_requests"
+  }
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
index 537f0a763c9de2a..80045c618e6408a 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/origin-level-steering/random-origin-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Random steering
+
 ---
 
 **Random steering** sends requests to endpoints purely based on [endpoint weights](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights). Distributes traffic more accurately, but may cause requests from the same IP to hit different endpoints.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
index f64ceb698d2ba17..666b471d0af1334 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Dynamic steering
+
 ---
 
 **Dynamic steering** uses health monitor data to identify the fastest pool for a given Cloudflare Region or data center.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
index 944941d3224b8ce..4ad16dc07656f19 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx
@@ -20,7 +20,6 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components";
 ## EDNS Client Subnet (ECS) support
 
 <GlossaryTooltip term="EDNS Client Subnet (ECS)"> EDNS Client Subnet (ECS) </GlossaryTooltip> support provides customers with more control over location-based steering during
-
 gray-clouded DNS resolutions and can be used for proximity or geo (country) steering.
 
 Customers can configure their load balancer using the `location_strategy` parameter, which includes the properties `prefer_ecs` and `mode`.
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
index b6cd01080f74721..a52ce97da3eb882 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/least-outstanding-requests.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Least Outstanding Requests steering - Steering policies
+
 ---
 
 **Least Outstanding Requests steering** allows you to route traffic to pools that currently have the lowest number of outstanding requests.
@@ -21,7 +22,7 @@ Least Outstanding Requests steering is best to use if your pools are easily over
 
 ```json title="Load Balancers"
 {
-	"steering_policy": "least_outstanding_requests"
+  "steering_policy": "least_outstanding_requests"
 }
 ```
 
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
index b5922711d2d91b3..2b5fbd7114d502e 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Proximity steering
+
 ---
 
 **Proximity steering** routes visitors or internal services to the closest physical data center.
@@ -17,19 +18,21 @@ To use proximity steering on a load balancer, you first need to add GPS coordina
 
 ## When to add proximity steering
 
-- For new pools, add GPS coordinates when you create a pool.
-- For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
+* For new pools, add GPS coordinates when you create a pool.
+* For existing pools, add GPS coordinates when [managing pools](/load-balancing/pools/create-pool/#edit-a-pool) or in the **Add Traffic steering** step of [creating a load balancer](/load-balancing/load-balancers/create-load-balancer/).
 
 ## How to add proximity steering
 
 To add coordinates when creating or editing a pool:
 
-1. Click the _Configure coordinates for Proximity Steering_ dropdown.
+1. Click the *Configure coordinates for Proximity Steering* dropdown.
 2. Enter the latitude and longitude or drag a marker on the map.
 3. Select **Save**.
 
 :::caution[Warning:]
 
+
 For accurate proximity steering, add GPS coordinates to all pools within the same load balancer.
 
+
 :::
diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
index 4cb1a555bf452a2..22d271801178c9b 100644
--- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
+++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Standard traffic steering policies
+
 ---
 
 **Standard steering** policies include **Off - Failover** and **Random**.
diff --git a/src/content/docs/log-explorer/api.mdx b/src/content/docs/log-explorer/api.mdx
index 6bdcc752a5d4156..305c470002dd3d8 100644
--- a/src/content/docs/log-explorer/api.mdx
+++ b/src/content/docs/log-explorer/api.mdx
@@ -8,7 +8,7 @@ products:
   - log-explorer
 ---
 
-Configuration and Log searches are also available via a public API.
+Configuration and Log searches are also available via a public API. 
 
 ## Authentication
 
@@ -18,7 +18,7 @@ For detailed information on permissions required for each Log Explorer feature,
 
 ## Query data
 
-Log Explorer includes a SQL API for submitting queries.
+Log Explorer includes a SQL API for submitting queries. 
 
 For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
 
@@ -77,4 +77,4 @@ This command returns the following request details:
 	"errors": [],
 	"messages": []
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/log-explorer/changelog.mdx b/src/content/docs/log-explorer/changelog.mdx
index 707f755e2c52edd..2f97c532c5ac0e6 100644
--- a/src/content/docs/log-explorer/changelog.mdx
+++ b/src/content/docs/log-explorer/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="log-explorer" />
+<ProductChangelog product="log-explorer" />
\ No newline at end of file
diff --git a/src/content/docs/log-explorer/example-queries.mdx b/src/content/docs/log-explorer/example-queries.mdx
index 265a16759a71279..3d9b6d9cb490e20 100644
--- a/src/content/docs/log-explorer/example-queries.mdx
+++ b/src/content/docs/log-explorer/example-queries.mdx
@@ -131,5 +131,5 @@ FROM http_requests
 WHERE {{ timeFilter }}
 GROUP BY ClientRequestPath
 ORDER BY avg_ttfb DESC
-LIMIT 10
+LIMIT 10 
 ```
diff --git a/src/content/docs/log-explorer/index.mdx b/src/content/docs/log-explorer/index.mdx
index 8d7a69052b79578..89e85b9513fb688 100644
--- a/src/content/docs/log-explorer/index.mdx
+++ b/src/content/docs/log-explorer/index.mdx
@@ -8,16 +8,15 @@ products:
   - log-explorer
 ---
 
-import { Description, Feature, RelatedProduct } from "~/components";
+import { Description, Feature, RelatedProduct } from "~/components"
 
 <Description>
-	Store and explore your Cloudflare logs directly within the Cloudflare
-	dashboard or API.
+Store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
 </Description>
 
 Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third-party tools.
 
-Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include:
+Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include: 
 
 - **Reduced cost and complexity**: Drastically reduce the expense and operational overhead associated with forwarding, storing, and analyzing terabytes of log data in external tools.
 - **Faster detection and triage**: Access Cloudflare-native logs directly, eliminating cumbersome data pipelines and the ingest lags that delay critical security insights.
@@ -28,14 +27,14 @@ Contract customers can choose to store their logs in Log Explorer for up to two
 
 ## Permissions
 
-Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards.
-
-| Feature                     | Required Permission | Description                             |
-| --------------------------- | ------------------- | --------------------------------------- |
-| **Manage datasets**         | `Logs Edit`         | Add, enable, or disable datasets.       |
-| **Log Search**              | `Logs Read`         | Query logs in the dashboard or via API. |
-| **Log Search (save query)** | `Logs Write`        | Save log search queries.                |
-| **Custom dashboards**       | `Analytics Read`    | Create and view custom dashboards.      |
+Access to Log Explorer features is controlled through specific permissions. Each permission grants users the ability to perform certain actions, such as querying logs, managing datasets, or creating dashboards. 
+ 
+| Feature | Required Permission | Description |
+|----------|--------------------|--------------|
+| **Manage datasets** | `Logs Edit` | Add, enable, or disable datasets. |
+| **Log Search** | `Logs Read` | Query logs in the dashboard or via API. |
+| **Log Search (save query)** | `Logs Write` | Save log search queries. |
+| **Custom dashboards** | `Analytics Read` | Create and view custom dashboards. |
 
 These permissions apply across both the dashboard and the API, and must be granted at either the account or zone level depending on which datasets you need to access.
 
@@ -44,30 +43,27 @@ Authentication with the API can be done via an API token or API key with an emai
 ## Features
 
 <Feature header="Log Search" href="/log-explorer/log-search/">
-	Explore your Cloudflare logs directly within the Cloudflare dashboard or
-	[API](/log-explorer/api/).
+Explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
 </Feature>
 
 <Feature header="Custom dashboards" href="/log-explorer/custom-dashboards/">
-	Design customized views for tracking application security, performance, and
-	usage metrics.
+Design customized views for tracking application security, performance, and usage metrics.
 </Feature>
 
 <Feature header="Manage datasets" href="/log-explorer/manage-datasets/">
-	Manage the data you want to store within Log Explorer.
+Manage the data you want to store within Log Explorer. 
 </Feature>
 
-<Feature header="API" href="/log-explorer/api/">
-	Manage configuration and perform queries via the API.
+<Feature header="API" href= "/log-explorer/api/">
+Manage configuration and perform queries via the API.
 </Feature>
 
 ## Related products
 
 <RelatedProduct header="Logpush" href="/logs/" product="logs">
-	Forward Cloudflare logs to third-party tools for debugging, identifying
-	configuration adjustments, and creating analytics dashboards.
+Forward Cloudflare logs to third-party tools for debugging, identifying configuration adjustments, and creating analytics dashboards.
 </RelatedProduct>
 
 <RelatedProduct header="Analytics" href="/analytics/" product="analytics">
-	Visualize the metadata collected by our products in the Cloudflare dashboard.
-</RelatedProduct>
+Visualize the metadata collected by our products in the Cloudflare dashboard.
+</RelatedProduct>
\ No newline at end of file
diff --git a/src/content/docs/logs/auditlogs-mcp-server.mdx b/src/content/docs/logs/auditlogs-mcp-server.mdx
index 36c461b0633126a..c0a8f2dd81e60e2 100644
--- a/src/content/docs/logs/auditlogs-mcp-server.mdx
+++ b/src/content/docs/logs/auditlogs-mcp-server.mdx
@@ -8,4 +8,4 @@ description: Access the Audit Logs MCP server on GitHub.
 products:
   - logs
   - audit-logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/audit-logs.mdx b/src/content/docs/logs/changelog/audit-logs.mdx
index 2e97637e3f86291..146a75efedab424 100644
--- a/src/content/docs/logs/changelog/audit-logs.mdx
+++ b/src/content/docs/logs/changelog/audit-logs.mdx
@@ -12,4 +12,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
-<ProductChangelog product="audit-logs" />
+<ProductChangelog product="audit-logs" />
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/index.mdx b/src/content/docs/logs/changelog/index.mdx
index 771bbd8160cd93c..337ffa7afa5c1cb 100644
--- a/src/content/docs/logs/changelog/index.mdx
+++ b/src/content/docs/logs/changelog/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: View recent changes to Cloudflare Logs.
 products:
   - logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/changelog/logs.mdx b/src/content/docs/logs/changelog/logs.mdx
index 7f30b4e52b1ad87..69133c374ad154f 100644
--- a/src/content/docs/logs/changelog/logs.mdx
+++ b/src/content/docs/logs/changelog/logs.mdx
@@ -13,3 +13,5 @@ import { ProductChangelog } from "~/components";
 {/* <!-- Actual content lives in /src/content/changelog/logs. Update the file there for new entries to appear here. */}
 
 <ProductChangelog product="logs" />
+
+
diff --git a/src/content/docs/logs/faq/common-calculations.mdx b/src/content/docs/logs/faq/common-calculations.mdx
index 0252af63297f09c..97fe1a4a59bed1f 100644
--- a/src/content/docs/logs/faq/common-calculations.mdx
+++ b/src/content/docs/logs/faq/common-calculations.mdx
@@ -20,3 +20,5 @@ The best way to calculate bytes served by the origin is to use the `CacheRespons
 ### How do I calculate bandwidth usage for my zone?
 
 Bandwidth (or data transfer) can be calculated by adding the `EdgeResponseBytes` field in HTTP request logs. There are some types of requests that are not factored into bandwidth calculations. In order to only include relevant requests in calculations, add the filter `ClientRequestSource = 'eyeball'`.
+
+
diff --git a/src/content/docs/logs/faq/general-faq.mdx b/src/content/docs/logs/faq/general-faq.mdx
index 0be1d8058566c6f..dc0077117908e87 100644
--- a/src/content/docs/logs/faq/general-faq.mdx
+++ b/src/content/docs/logs/faq/general-faq.mdx
@@ -32,6 +32,7 @@ Yes. The time period for which you pull or receive logs is based on our processi
 
 Not at this time. Talk to your Cloudflare account team or [Cloudflare Support](/support/contacting-cloudflare-support/) if you are interested in other formats and we will consider them for the future.
 
+
 ### Is it possible to track cache purge requests in the logs?
 
 Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/audit-logs/).
@@ -40,3 +41,5 @@ Yes, since Nov 25, 2025 [Audit Log v2](/fundamentals/account/account-security/au
 
 Requests are logged only after they successfully reach our proxy.
 It means that requests failing during the TCP or TLS handshake between the client and the Cloudflare proxy will not be available in the logs.
+
+
diff --git a/src/content/docs/logs/faq/instant-logs.mdx b/src/content/docs/logs/faq/instant-logs.mdx
index 1ec7a24289b2ae0..b2c23c3ee7e6a1c 100644
--- a/src/content/docs/logs/faq/instant-logs.mdx
+++ b/src/content/docs/logs/faq/instant-logs.mdx
@@ -14,6 +14,7 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
+
 ### I am getting an HTTP 301 when attempting to connect to my WebSocket. What can I do?
 
 Make sure you are using the `wss://` protocol when connecting to your WebSocket.
@@ -33,3 +34,5 @@ Finally, make sure the destination is proxied through Cloudflare (also known as
 ### I am getting an error fetching my data. How can I solve this?
 
 Make sure you have the correct permissions. To use Instant Logs you need Super Administrator, Administrator, Log Share, or Log Share Reader permissions.
+
+
diff --git a/src/content/docs/logs/faq/logpull-api.mdx b/src/content/docs/logs/faq/logpull-api.mdx
index 04a52d4ae5aeb26..28623ba05c80d58 100644
--- a/src/content/docs/logs/faq/logpull-api.mdx
+++ b/src/content/docs/logs/faq/logpull-api.mdx
@@ -12,12 +12,17 @@ products:
 
 [❮ Back to FAQ](/logs/faq/)
 
+
 ### How long are logs retained?
 
 Cloudflare makes logs available for at least three days and up to seven days. If you need your logs for a longer time period, download and store them locally.
 
+
 ### I am asking for logs for the time window of 16:10-16:13. However, the timestamps in the logs show requests that are before this time period. Why does that happen?
 
+
 When you make a call for the time period of 16:10-16:13, you are actually asking for the logs that were received and processed by our system during that time (hence the endpoint name, `logs/received`). The received time is the time the logs are written to disk. There is some delay between the time the request hits the Cloudflare edge and the time it is received and processed. The **request time** is what you see in the log itself: **EdgeStartTimestamp** and **EdgeEndTimestamp** tell you when the edge started and stopped processing the request.
 
 The advantage of basing the responses on the **time received** rather than the request or edge time is not needing to worry about late-arriving logs. As long as you are calling our API for continuous time segments, you will always get all of your logs without making duplicate calls. If we based the response on request time, you could never be sure that all the logs for that request time had been processed.
+
+
diff --git a/src/content/docs/logs/faq/worker-subrequests.mdx b/src/content/docs/logs/faq/worker-subrequests.mdx
index d1652e3ff63fadd..3d51ed73a21100d 100644
--- a/src/content/docs/logs/faq/worker-subrequests.mdx
+++ b/src/content/docs/logs/faq/worker-subrequests.mdx
@@ -19,10 +19,10 @@ Because the initial log entry only covers the request from the client to the Wor
 
 ### What the two log entries represent
 
-| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                                      |
-| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------------------------- |
+| Log entry         | Typical `ClientRequestSource` value | What it represents                     | Origin fields                    |
+| ----------------- | ----------------------------------- | -------------------------------------- | -------------------------------- |
 | Initial request   | `eyeball`                           | End-user request to the Worker         | `OriginResponseStatus` is `0`, `OriginIP` is empty |
-| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                   |
+| Worker subrequest | `edgeWorkerFetch`                   | Worker `fetch()` request to the origin | Set when the origin is contacted                    |
 
 Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for the full list of possible `ClientRequestSource` values.
 
@@ -30,10 +30,10 @@ Refer to [ClientRequestSource field](/logs/reference/clientrequestsource/) for t
 
 Each log entry has its own `RayID`. The Worker subrequest also includes `ParentRayID`, which is the `RayID` of the request that triggered it — its immediate parent.
 
-| Field         | Initial request                            | Worker subrequest                        |
-| ------------- | ------------------------------------------ | ---------------------------------------- |
-| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest     |
-| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it |
+| Field         | Initial request                            | Worker subrequest                          |
+| ------------- | ------------------------------------------ | ------------------------------------------ |
+| `RayID`       | Unique request ID for the end-user request | Unique request ID for the subrequest       |
+| `ParentRayID` | Empty                                      | `RayID` of the request that triggered it   |
 
 To correlate the two records:
 
diff --git a/src/content/docs/logs/glossary.mdx b/src/content/docs/logs/glossary.mdx
index 986f0dca8ab17e7..5996605fa39a008 100644
--- a/src/content/docs/logs/glossary.mdx
+++ b/src/content/docs/logs/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - logs
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Logs documentation.
 
diff --git a/src/content/docs/logs/logpull/index.mdx b/src/content/docs/logs/logpull/index.mdx
index 3629ad283b4166f..b22aea276e0eb94 100644
--- a/src/content/docs/logs/logpull/index.mdx
+++ b/src/content/docs/logs/logpull/index.mdx
@@ -8,14 +8,16 @@ products:
   - logs
 ---
 
-import { DirectoryListing, FeatureTable } from "~/components";
+import { DirectoryListing, FeatureTable } from "~/components"
 
 Cloudflare Logpull is a REST API for consuming request logs over HTTP. These logs contain data related to the connecting client, the request path through the Cloudflare network, and the response from the origin web server. This data is useful for enriching existing logs on an origin server. Logpull is available to customers on the Enterprise plan.
 
 :::caution
 
+
 Logpull is considered a legacy feature and we recommend using [Logpush](/logs/logpush/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
 
+
 :::
 
 Review the following content to learn more about Logpull.
diff --git a/src/content/docs/logs/logpull/requesting-logs.mdx b/src/content/docs/logs/logpull/requesting-logs.mdx
index 685501c9631c889..c7443bca08d6d5c 100644
--- a/src/content/docs/logs/logpull/requesting-logs.mdx
+++ b/src/content/docs/logs/logpull/requesting-logs.mdx
@@ -12,20 +12,20 @@ products:
 
 The three endpoints supported by the Logpull API are:
 
-- `GET /logs/received` - returns HTTP request log data based on the parameters specified
-- `GET /logs/received/fields` - returns the list of all available log fields
-- `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
+* `GET /logs/received` - returns HTTP request log data based on the parameters specified
+* `GET /logs/received/fields` - returns the list of all available log fields
+* `GET /logs/rayids/{ray_id}` - returns HTTP request log data matching `{ray_id}`
 
 ## Required authentication headers
 
 The following headers are required for all endpoint calls:
 
-- `X-Auth-Email` - the Cloudflare account email address associated with the domain
-- `X-Auth-Key` - the Cloudflare API key
+* `X-Auth-Email` - the Cloudflare account email address associated with the domain
+* `X-Auth-Key` - the Cloudflare API key
 
 Alternatively, API tokens with Logs Read permissions can also be used for authentication:
 
-- `Authorization: Bearer <API_TOKEN>`
+* `Authorization: Bearer <API_TOKEN>`
 
 ## Parameters
 
@@ -45,9 +45,11 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}?[&fiel
 
 The following table describes the parameters available:
 
+
+
 | Parameter      | Description                                                                                                                                                                                                                                                                                                                          | Applies to                                | Required |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | -------- |
-| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p> | /logs/received                            | Yes      |
+| start          | <p>- Inclusive</p> <p>- Timestamp formatted as `UNIX` (UTC by definition), `UNIX Nano`, or `rfc3339`. To specify `rfc3339` time zone in URL query parameters, the URL needs to be encoded, like this `start=2024-08-07T07:00:00%2B08:00&end=2024-08-07T07:01:00%2B08:00`. </p> <p>- Must be no more than 7 days earlier than now</p>                                                                                                                                                 | /logs/received                            | Yes      |
 | end            | <p>- Exclusive</p> <p>- Same format as <em>start</em></p> <p>- Must be at least 1 minute earlier than now and later than <em>start</em></p>                                                                                                                                                                                          | /logs/received                            | Yes      |
 | count          | <p>- Return up to that many records</p> <p>- Do not include if returning all records</p> <p>- Results are not sorted; therefore, different data for repeated requests is likely</p> <p></p> <p>- Applies to number of total records returned, not number of sampled records</p>                                                      | /logs/received                            | No       |
 | sample         | <p>- Return only a sample of records</p> <p>- Do not include if returning all records</p> <p>- Value can range from `0.0` (exclusive) to `1.0` (inclusive)</p> <p>- `sample=0.1` means return 10% (1 in 10) of all records</p> <p>- Results are random; therefore, different numbers of results for repeated requests are likely</p> | /logs/received                            | No       |
@@ -55,14 +57,18 @@ The following table describes the parameters available:
 | timestamps     | <p>- Format in which timestamp fields will be returned</p> <p>- Value options are: `unixnano` (default), `unix`, `rfc3339`</p> <p>- Timestamps returned as integers for `unix` and `unixnano` and as strings for `rfc3339`</p>                                                                                                       | <p>/logs/received</p> <p>/logs/rayids</p> | No       |
 | CVE-2021-44228 | <p>- Optional redaction for [CVE-2021-44228](https://www.cve.org/CVERecord?id=CVE-2021-44228). This option will replace every occurrence of the string `${` with `x{`.</p> <p> For example: `CVE-2021-44228=true` </p>                                                                                                               | <p>/logs/received</p>                     | No       |
 
+
+
 :::note[Note]
 
+
 The maximum time range from **start** to **end** cannot exceed 1 hour. Because **start** is inclusive and **end** is exclusive, to get all the data for every minute, starting at 10AM, the proper values are:
 
 `start=2018-05-15T10:00:00Z&end=2018-05-15T10:01:00Z`, then `start=2018-05-15T10:01:00Z&end=2018-05-15T10:02:00Z` and so on.
 
 The overlap will be handled correctly.
 
+
 :::
 
 ## Example API requests using cURL
@@ -85,8 +91,10 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/rayids/{ray_id}}
 
 :::note[Note]
 
+
 The IATA code returned as part of the **RayID** does not need to included in the request. For example, if you have a **RayID** such as `49ddb3e70e665831-DFW`, only include `49ddb3e70e665831` in your request.
 
+
 :::
 
 ## Fields
diff --git a/src/content/docs/logs/logpull/understanding-the-basics.mdx b/src/content/docs/logs/logpull/understanding-the-basics.mdx
index bdd4d1622f13746..0464c6ff3cdf093 100644
--- a/src/content/docs/logs/logpull/understanding-the-basics.mdx
+++ b/src/content/docs/logs/logpull/understanding-the-basics.mdx
@@ -10,7 +10,7 @@ products:
 
 ## Access pattern
 
-The basic access pattern is _give me all the logs for zone Z for minute M_ where the minute _M_ refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
+The basic access pattern is *give me all the logs for zone Z for minute M* where the minute *M* refers to the time the log entries were written to disk in Cloudflare's log aggregation system.
 
 To start, try running your query every minute. If responses are too small, go up to 5 minutes as this will be appropriate for most zones. If the responses are too large, try going down to 15 seconds.
 
@@ -24,7 +24,7 @@ Because our log processing system ingests data in batches, most zones with less
 
 The `logs/received` API endpoint exposes data by time received, which is the time the event was written to disk in the Cloudflare Logs aggregation system.
 
-Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from _rsyslog_ (albeit in chunks).
+Ordering by log aggregation time instead of log generation time results in lower (faster) log pipeline latency and deterministic log pulls. Functionally, it is similar to tailing a log file or reading from *rsyslog* (albeit in chunks).
 
 This means that to obtain logs for a given time range, you can issue one call for each consecutive minute (or other time range). Because log lines are batched by time received and made available, there is no late arriving data. A response for a given minute will never change. You do not have to repeatedly poll a given time range to receive logs as they converge on our aggregation system.
 
@@ -32,7 +32,7 @@ This means that to obtain logs for a given time range, you can issue one call fo
 
 The Logpull API returns data in NDJSON format, whereby each log line is a valid JSON object. Major analysis tools like Google BigQuery and AWS Kinesis require this format.
 
-To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into _jq_ using the _slurp_ (or simply _s_) flag:
+To turn the resulting log data into a JSON array with one array element per log line, you can use the `jq` tool. Essentially, you pipe the API response into *jq* using the *slurp* (or simply *s*) flag:
 
 `<API request data> | jq -s`
 
@@ -42,15 +42,15 @@ The following is a sample log with default fields:
 
 ```json
 {
-	"ClientIP": "89.163.242.206",
-	"ClientRequestHost": "www.theburritobot.com",
-	"ClientRequestMethod": "GET",
-	"ClientRequestURI": "/static/img/testimonial-hipster.png",
-	"EdgeEndTimestamp": 1506702504461999900,
-	"EdgeResponseBytes": 69045,
-	"EdgeResponseStatus": 200,
-	"EdgeStartTimestamp": 1506702504433000200,
-	"RayID": "3a6050bcbe121a87"
+  "ClientIP": "89.163.242.206",
+  "ClientRequestHost": "www.theburritobot.com",
+  "ClientRequestMethod": "GET",
+  "ClientRequestURI": "/static/img/testimonial-hipster.png",
+  "EdgeEndTimestamp": 1506702504461999900,
+  "EdgeResponseBytes": 69045,
+  "EdgeResponseStatus": 200,
+  "EdgeStartTimestamp": 1506702504433000200,
+  "RayID": "3a6050bcbe121a87"
 }
 ```
 
diff --git a/src/content/docs/logs/logpush-mcp-server.mdx b/src/content/docs/logs/logpush-mcp-server.mdx
index 66fb1c45f2e2f73..606c4e683714467 100644
--- a/src/content/docs/logs/logpush-mcp-server.mdx
+++ b/src/content/docs/logs/logpush-mcp-server.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Access the Logpush MCP server on GitHub.
 products:
   - logs
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
index fd2d2d005e6d33d..4ab48625e439d06 100644
--- a/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
+++ b/src/content/docs/logs/logpush/examples/example-logpush-python.mdx
@@ -12,8 +12,10 @@ You can manage your Cloudflare Logpush service using Python. In the script below
 
 :::note
 
+
 The examples below are for zone-scoped datasets. Account-scoped datasets should use `<ACCOUNT_ID>` instead of `<ZONE_ID>`.
 
+
 :::
 
 ```python
diff --git a/src/content/docs/logs/logpush/examples/index.mdx b/src/content/docs/logs/logpush/examples/index.mdx
index 17da91fca9f2307..d593b40a49fe8db 100644
--- a/src/content/docs/logs/logpush/examples/index.mdx
+++ b/src/content/docs/logs/logpush/examples/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/index.mdx b/src/content/docs/logs/logpush/index.mdx
index e93944723bd2eb9..c97ab2846f221ff 100644
--- a/src/content/docs/logs/logpush/index.mdx
+++ b/src/content/docs/logs/logpush/index.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { FeatureTable, LinkButton } from "~/components";
+import { FeatureTable, LinkButton } from "~/components"
 
 Logpush delivers logs in batches as quickly as possible, with no minimum batch size, potentially delivering files more than once per minute. This capability enables Cloudflare to provide information almost in real time, in smaller file sizes.
 
@@ -57,6 +57,8 @@ There is currently a max limit of **4 Logpush jobs per zone**. Trying to create
 
 :::note
 
+
 Users without an Enterprise plan can still access [Workers Trace Events Logpush](/workers/observability/logs/logpush/) by subscribing to the [Workers Paid](/workers/platform/pricing/) plan.
 
+
 :::
diff --git a/src/content/docs/logs/logpush/logpush-health.mdx b/src/content/docs/logs/logpush/logpush-health.mdx
index 9f31536d4532a8a..10604407f89dd20 100644
--- a/src/content/docs/logs/logpush/logpush-health.mdx
+++ b/src/content/docs/logs/logpush/logpush-health.mdx
@@ -20,17 +20,17 @@ Health notifications work alongside the Health Dashboard to provide both real-ti
 
 ## Access Health Dashboards
 
-1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.
-2. Go to the **Health** tab.
-3. Select the job you want to analyze.
-4. Specify the time range you want to review.
-5. _(Optional)_ From the **Jobs** tab, locate the job you want to analyze.
-6. Hover over the **Job Health (24h)** column for that job and select **View Health**.
+1. In the **Cloudflare dashboard**, go to the **Logpush** page at either the account or domain (zone) level.  
+2. Go to the **Health** tab.  
+3. Select the job you want to analyze.  
+4. Specify the time range you want to review.  
+5. *(Optional)* From the **Jobs** tab, locate the job you want to analyze.  
+6. Hover over the **Job Health (24h)** column for that job and select **View Health**.  
 7. You will be redirected to the **Health** tab, where you can select the desired time range for analysis.
 
 ### Data availability and API access
 
-- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.
+- The **Health Dashboard** displays up to **30 days** of health metrics for each Logpush job in the Cloudflare dashboard.  
 - The raw health metrics can be queried via the `logpushHealthAdaptiveGroups` dataset in the GraphQL API.
 - You can explore or test queries using the [Cloudflare GraphQL Explorer](https://graphql.cloudflare.com/explorer).
 
@@ -62,7 +62,7 @@ Indicates that all upload attempts for a batch were exhausted without success. W
 
 ## Health dashboard flow
 
-The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.
+The **Logpush Health Dashboard** provides two complementary views that help you monitor and troubleshoot log delivery: **Upload Health** and **Upload Reliability**.  
 
 Each view highlights a different aspect of job performance — what was delivered and how reliably it was delivered.
 
@@ -72,23 +72,23 @@ Each view highlights a different aspect of job performance — what was delivere
 
 #### Charts and metrics
 
-- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.
-  - **Successful Uploads** - Total number of batches successfully uploaded.
-  - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
+- **Batch Upload Success vs. Failure**: Displays the number of batches that were successfully uploaded versus those that failed.  
+    - **Successful Uploads** - Total number of batches successfully uploaded.  
+    - **Failed Uploads** - Total number of batches that failed to upload due to connection or destination issues.
 
-- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.
-  - **Uploaded Log Lines** - Total number of log lines successfully delivered.
-  - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
+- **Log Lines Uploaded**: Tracks the total number of log lines successfully uploaded to your destination.  
+    - **Uploaded Log Lines** - Total number of log lines successfully delivered.  
+    - **Dropped Log Lines** - Total number of log lines that could not be delivered after all retry attempts.
 
-- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.
-  - **Uncompressed Data (raw)** - Total size of log data before compression.
-  - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
+- **Data Volume**: Shows the total volume of log data uploaded (in bytes), both compressed and uncompressed.  
+    - **Uncompressed Data (raw)** - Total size of log data before compression.  
+    - **Compressed Data (uploaded)** - Total size of log data after compression, representing the actual bytes transmitted.
 
 #### When to use
 
 Start here to assess overall data delivery health:
 
-- High upload success and stable data volume indicate a healthy Logpush job.
+- High upload success and stable data volume indicate a healthy Logpush job.  
 - Drops, spikes, or failed uploads suggest delivery issues — proceed to **Upload Reliability** to investigate root causes.
 
 ### Upload Reliability
@@ -97,37 +97,37 @@ Upload Reliability helps you identify factors affecting reliability, stability,
 
 #### Charts and metrics
 
-- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.
-  - **Success Rate** - Percentage of batches successfully uploaded.
-  - **Successful Uploads** - Total number of batches successfully completed.
+- **Uploaded Logs by Status Code** Shows the number of batches that were successful, failed, or retried, categorized by status code.  
+    - **Success Rate** - Percentage of batches successfully uploaded.  
+    - **Successful Uploads** - Total number of batches successfully completed.
 
-- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.
-  - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.
-  - **Average Upload Duration** - Average time taken to upload logs after they are generated.
+- **Upload Duration**: Shows the average time taken to complete each batch upload, broken down by status code.  
+    - **Destination Availability** - How often Cloudflare successfully connected to your destination and completed uploads.  
+    - **Average Upload Duration** - Average time taken to upload logs after they are generated.
 
-- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.
-  - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
+- **Retry Attempts**: Displays the number of retries made after failed uploads, broken down by status code.  
+    - **Retry Attempts** - Total number of upload attempts made after previous failures (includes the first failed attempt).
 
 #### When to use
 
 Use this view to troubleshoot reliability issues:
 
-- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.
+- High latency, frequent retries, or low destination availability indicate potential instability in the destination endpoint or network.  
 - Combine with **Upload Health** metrics to correlate delivery success with underlying reliability patterns.
 
 ## Troubleshooting guide
 
 The Logpush Health Dashboards help you monitor the status, reliability, and performance of your Logpush jobs. Use this guide to interpret each chart, identify the root cause of anomalies, and take corrective action.
 
-| Chart name                                  | Symptom                                       | What it means                                                                                                                                 | Possible causes                                                                                                                                                                                                       | Recommended actions                                                                                                                                                                                                                           |
-| ------------------------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Batch Upload Success vs Failure**         | Failed uploads                                | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/> - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
-| **Log Lines Uploaded**                      | Dropped log lines or reduced delivery volume  | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches.                                                 | - Spike in failed uploads. <br/> - Destination ingestion limits or partial uploads.                                                                                                                                   | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/> - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes.                                               |
-| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume                | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches.                                       | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits.                                                                                                         | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries.                                                                                             |
-| **Uploaded Logs by Status Code**            | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries.                                                                                     | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination.                                                                                                   | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size.                                                                                         |
-| **Retry Attempts**                          | Frequent retry activity                       | Uploads are repeatedly failing and retried multiple times.                                                                                    | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination.                                                                                                    | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review.                                                             |
-| **Avg. Upload Duration**                    | Long upload times                             | Uploads are taking longer than expected, indicating latency or oversized batches.                                                             | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays.                                                                                                 | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings.                                                                                        |
-| **Destination Availability**                | Low or unstable availability                  | Cloudflare cannot consistently connect to your destination.                                                                                   | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare.                                                                                           | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings.                                                                             |
+| Chart name | Symptom | What it means | Possible causes | Recommended actions |
+|-----------------|-------------|-------------------|----------------------|--------------------------|
+| **Batch Upload Success vs Failure** | Failed uploads | Cloudflare could not deliver batches after all retry attempts. These batches are marked as **failed**, and all log lines in them are dropped. | - Destination endpoint unavailable or rejecting connections (expired credentials, downtime). <br/> - Uploads timing out due to large batch sizes or network latency. <br/> - Destination throttling or rate limiting. | - Verify destination credentials and endpoint health. <br/> - Reduce batch size in the Logpush job configuration. <br/>  - Ensure the destination can handle the expected upload rate. <br/> - Contact Cloudflare Support if failures persist. |
+| **Log Lines Uploaded** | Dropped log lines or reduced delivery volume | Fewer logs are being delivered than expected, often due to failed uploads or dropped batches. | - Spike in failed uploads. <br/>  - Destination ingestion limits or partial uploads. | - Compare **Log Lines Uploaded** and **Data Volume** charts for dips. <br/>  - Check destination for ingestion errors or rate limiting. <br/> - Review recent Logpush job configuration changes. |
+| **Data Volume (Compressed & Uncompressed)** | Unexpected drop in data volume | Delivered data volume is lower than expected, suggesting compression inefficiencies or dropped batches. | - Failed uploads or incomplete deliveries. <br/> - Destination rejecting uploads due to size or quota limits. | - Review compression settings and batch size. <br/> - Verify destination storage capacity. <br/> - Check for spikes in failed uploads or retries. |
+| **Uploaded Logs by Status Code** | High number of retries or failed status codes | Uploads fail on the first attempt but succeed on retries. | - Temporary destination downtime or throttling. <br/> - Network instability between Cloudflare and the destination. | - Review retry and failure distribution by status code. <br/> - Compare with **Destination Availability** for correlation. <br/> - Reduce batch size. |
+| **Retry Attempts** | Frequent retry activity | Uploads are repeatedly failing and retried multiple times. | - Destination instability or transient errors. <br/> - High latency or slow acknowledgements from the destination. | - Verify destination uptime and ingestion rate. <br/> - Ensure destination is not throttling requests. <br/> - Occasional retries are expected; persistent spikes require review. |
+| **Avg. Upload Duration** | Long upload times | Uploads are taking longer than expected, indicating latency or oversized batches. | - Large batches or uncompressed payloads. <br/> - Network or regional latency. <br/> - Destination processing delays. | - Review **Avg. Upload Duration** trends. <br/> - Reduce batch size for faster uploads. <br/> - Verify destination throughput and rate limit settings. |
+| **Destination Availability** | Low or unstable availability | Cloudflare cannot consistently connect to your destination. | - Destination downtime, DNS errors, or authentication issues. <br/> - Firewall or network restrictions blocking Cloudflare. | - Check **Destination Availability** for dips. <br/> - Confirm destination credentials and endpoint uptime. <br/> - Review allowlists or network access settings. |
 
 ## Understanding retry behavior
 
diff --git a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
index d7b7dd78507d62e..6a98f17905433ca 100644
--- a/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/api-configuration.mdx
@@ -18,19 +18,19 @@ You can locate `{zone_id}` and `{account_id}` arguments based on the [Find zone
 The `{job_id}` argument is numeric, like 123456.
 The `{dataset_id}` argument indicates the log category (such as `http_requests` or `audit_logs`).
 
-| Operation | Description                                 | API                                                                                            |
+| Operation | Description                                 | API                                                                                                                                                                                              |
 | --------- | ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                      |
-| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
-| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                        |
-| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)   |
+| `POST`    | Create job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/create/)                                             |
+| `GET`     | Retrieve job details                        | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)                                     |
+| `GET`     | Retrieve all jobs for all datasets          | [Documentation](/api/resources/logpush/subresources/jobs/methods/list/)                                                 |
+| `GET`     | Retrieve all jobs for a dataset             | [Documentation](/api/resources/logpush/subresources/datasets/subresources/jobs/methods/get/)        |
 | `GET`     | Retrieve all available fields for a dataset | [Documentation](/api/resources/logpush/subresources/datasets/subresources/fields/methods/get/) |
-| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                      |
-| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                      |
-| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/)             |
-| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
-| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)               |
-| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                  |
+| `PUT`     | Update job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/update/)                                      |
+| `DELETE`  | Delete job                                  | [Documentation](/api/resources/logpush/subresources/jobs/methods/delete/)                           |
+| `POST`    | Check whether destination exists            | [Documentation](/api/resources/logpush/subresources/validate/methods/destination/) |
+| `POST`    | Get ownership challenge                     | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                                      |
+| `POST`    | Validate ownership challenge                | [Documentation](/api/resources/logpush/subresources/ownership/methods/validate/)                      |
+| `POST`    | Validate log options                        | [Documentation](/api/resources/logpush/subresources/validate/methods/origin/)                           |
 
 For concrete examples, refer to the tutorials in [Logpush examples](/logs/logpush/examples/).
 
@@ -47,25 +47,25 @@ Before creating a new job, ownership of the destination must be proven.
 To issue an ownership challenge token to your destination:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/ownership"
-	method="POST"
-	json={{
-		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-	}}
+  path="/zones/{zone_id}/logpush/ownership"
+  method="POST"
+  json={{
+    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+  }}
 />
 
 A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path, if appropriate for your destination):
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"valid": true,
-		"message": "",
-		"filename": "<PATH_TO_CHALLENGE_FILE>.txt"
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "valid": true,
+    "message": "",
+    "filename": "<PATH_TO_CHALLENGE_FILE>.txt"
+  },
+  "success": true
 }
 ```
 
@@ -138,23 +138,23 @@ For more information on the value for your cloud storage provider, consult the f
 To check if a destination is already in use:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/validate/destination/exists"
-	method="POST"
-	json={{
-		destination_conf: "s3://foo",
-	}}
+  path="/zones/{zone_id}/logpush/validate/destination/exists"
+  method="POST"
+  json={{
+    destination_conf: "s3://foo",
+  }}
 />
 
 Response
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"exists": false
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "exists": false
+  },
+  "success": true
 }
 ```
 
@@ -173,28 +173,28 @@ The kind parameter cannot be used to update existing Logpush jobs. You can only
 :::
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/jobs"
-	method="POST"
-	json={{
-		name: "<DOMAIN_NAME>",
-		destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
-		dataset: "http_requests",
-		output_options: {
-			field_names: [
-				"ClientIP",
-				"ClientRequestHost",
-				"ClientRequestMethod",
-				" ClientRequestURI",
-				"EdgeEndTimestamp",
-				"EdgeResponseBytes",
-				"EdgeResponseStatus",
-				"EdgeStartTimestamp",
+  path="/zones/{zone_id}/logpush/jobs"
+  method="POST"
+  json={{
+    name: "<DOMAIN_NAME>",
+    destination_conf: "s3://<BUCKET_PATH>?region=us-west-2",
+    dataset: "http_requests",
+    output_options: {
+      field_names: [
+        "ClientIP",
+        "ClientRequestHost",
+        "ClientRequestMethod",
+        " ClientRequestURI",
+        "EdgeEndTimestamp",
+        "EdgeResponseBytes",
+        "EdgeResponseStatus",
+        "EdgeStartTimestamp",
 				"RayID",
-			],
+      ],
 			timestamp_format: "rfc3339",
-		},
+    },
 		kind: "edge",
-	}}
+  }}
 />
 
 ## Options
@@ -205,7 +205,7 @@ If you are still using logpull_options, here are the options that you can custom
 
 1. **Fields** (optional): Refer to [Datasets](/logs/logpush/logpush-job/datasets/) for the currently available fields. The list of fields is also accessible directly from the API: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields`. Default fields: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/{dataset_id}/fields/default`.
 2. **Timestamp format** (optional): The format in which timestamp fields will be returned. Value options: `unixnano` (nanoseconds unit - default), `unix` (seconds unit), `rfc3339` (seconds unit).
-3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`. To enable it, set `"CVE-2021-44228": true`.
+3. **Redaction for CVE-2021-44228** (optional): This option will replace every occurrence of `${` with `x{`.  To enable it, set `"CVE-2021-44228": true`.
 
 :::note[Note]
 
@@ -215,26 +215,26 @@ The **CVE-2021-44228** parameter can only be set through the API at this time. U
 To check if the selected **logpull_options** are valid:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/validate/origin"
-	method="POST"
-	json={{
+  path="/zones/{zone_id}/logpush/validate/origin"
+  method="POST"
+  json={{
 		logpull_options:
 			"fields=RayID,ClientIP,EdgeStartTimestamp&timestamps=rfc3339&CVE-2021-44228=true",
 		dataset: "http_requests",
-	}}
+  }}
 />
 
 Response
 
 ```json
 {
-	"errors": [],
-	"messages": [],
-	"result": {
-		"valid": true,
-		"message": ""
-	},
-	"success": true
+  "errors": [],
+  "messages": [],
+  "result": {
+    "valid": true,
+    "message": ""
+  },
+  "success": true
 }
 ```
 
@@ -280,10 +280,10 @@ When customer-configured sampling is applied, the `SampleInterval` field value i
 
 These parameters control the size of each upload batch — not how quickly data is delivered. Use them to prevent overloading your destination with uploads that are too large or too small.
 
-| Parameter                     | Description                                                               | Default               |
-| ----------------------------- | ------------------------------------------------------------------------- | --------------------- |
-| `max_upload_bytes`            | Maximum uncompressed file size of a batch of logs.                        | Varies by destination |
-| `max_upload_records`          | Maximum number of log lines per batch.                                    | 100,000               |
+| Parameter | Description | Default |
+| --- | --- | --- |
+| `max_upload_bytes` | Maximum uncompressed file size of a batch of logs. | Varies by destination |
+| `max_upload_records` | Maximum number of log lines per batch. | 100,000 |
 | `max_upload_interval_seconds` | Maximum time-span of log data per batch (used during catch-up scenarios). | Varies by destination |
 
 :::note
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
index a9bd442099c837b..618a7f86d3a5d55 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/account/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
index 452263a6cac1017..2068e23086295d9 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/cmb.mdx
@@ -1,8 +1,8 @@
 ---
 pcx_content_type: reference
-title: CMB support by dataset
+title: CMB support by dataset 
 external_link: /data-localization/metadata-boundary/logpush-datasets/
 description: Learn about cmb support by dataset  in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
index d57a162728ea19b..64c4408ce21b874 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/index.mdx
@@ -12,25 +12,25 @@ products:
 
 The datasets below describe the fields available by log category:
 
-- [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
-- [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
+* [Zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/)
+* [Account-scoped datasets](/logs/logpush/logpush-job/datasets/account/)
 
 ## API
 
 The list of fields can also be accessed directly from the API using the following endpoints:
 
-- For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
+* For zone-scoped datasets: `https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/datasets/<DATASET>/fields`
 
-- For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
+* For account-scoped datasets: `https://api.cloudflare.com/client/v4/accounts/{account_id}/logpush/datasets/<DATASET>/fields`
 
 The `<DATASET>` argument indicates the log category. For example, `http_requests`, `spectrum_events`, `firewall_events`, `nel_reports`, or `dns_logs`.
 
 ## Availability
 
-- The availability of Logpush dataset fields depends on your subscription plan.
-- Zone-scoped HTTP requests are available in both Logpush and Logpull.
-- [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
-- All other datasets are only available through Logpush.
+* The availability of Logpush dataset fields depends on your subscription plan.
+* Zone-scoped HTTP requests are available in both Logpush and Logpull.
+* [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
+* All other datasets are only available through Logpush.
 
 ## Deprecation
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
index 3916cd8f337d26e..f21b39be05e2657 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/dns_logs.md
@@ -49,7 +49,7 @@ Whether the response was cached or not.
 
 Type: `int`
 
-Integer value of response code. For more information refer to [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
+Integer value of response code. For more information refer to  [Response code](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6).
 
 ## SourceIP
 
diff --git a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
index d9de685d205d4d0..b44ea90a6fa6a98 100644
--- a/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/datasets/zone/index.mdx
@@ -10,6 +10,6 @@ products:
   - logpush
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
index 12b4d2e27bc5489..6b8090800495242 100644
--- a/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/edge-log-delivery.mdx
@@ -8,8 +8,9 @@ products:
   - logpush
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
 Edge Log Delivery allows customers to send logs directly from Cloudflare’s edge to their destination of choice. You can configure the maximum interval for your log batches between 30 seconds and five minutes. However, you cannot specify a minimum interval for log batches, meaning that log files may be sent in shorter intervals than the maximum specified. Compared to Logpush, Edge Log Delivery sends logs with lower latency, more frequently, and in smaller batches.
 
 Edge Log Delivery is only available for HTTP request logs. Refer to the [API configuration](/logs/logpush/logpush-job/api-configuration/#kind) page for steps on how to configure a job to use Edge Log Delivery.
+
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
index e9823d82ca24e5c..65b671327acdea2 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx
@@ -42,9 +42,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
index 437fe5b4f67cf0f..301c4bcbaf9e976 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx
@@ -79,7 +79,6 @@ signedResourceTypes must be Object only (srt=o)
 ```
 
 To resolve this error, regenerate your SAS token using [Storage Explorer](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer) with the correct permissions:
-
 - Service: Blob-only (`ss=b`)
 - Resource type: Object-only (`srt=o`)
 - Permissions: Write-only
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
index bfc9e8b76c9f8f2..bde5e5a6cadf67d 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdx
@@ -40,23 +40,22 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 1. Register or use an existing zone for the dedicated egress IPs pool.
 2. Contact your account team to get the ID for your dedicated egress IPs pool.
 3. Make a `PATCH` request to the [Edit Zone Setting](/api/resources/zones/subresources/settings/methods/edit/) endpoint:
-
-- Specify `aegis` as the setting ID in the URL.
-- In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
+  - Specify `aegis` as the setting ID in the URL.
+  - In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
 
 <APIRequest
-	path="/zones/{zone_id}/settings/{setting_id}"
-	method="PATCH"
-	json={{
-		id: "aegis",
-		value: {
-			enabled: true,
-			pool_id: "<YOUR_EGRESS_POOL_ID>",
-		},
+  path="/zones/{zone_id}/settings/{setting_id}"
+  method="PATCH"
+  json={{
+		  "id": "aegis",
+			"value": {
+				"enabled": true,
+				"pool_id": "<YOUR_EGRESS_POOL_ID>",
+				},
 	}}
 	parameters={{
-		setting_id: "aegis",
-	}}
+    setting_id: "aegis",
+  }}
 />
 
 ## 3. Proxy zone setup
@@ -67,6 +66,7 @@ The following example shows how to set up logpush and Dedicated CDN Egress IPs t
 
 2. If needed, configure [origin rules](/rules/origin-rules/) to specify a custom port. This is useful if your destination only accepts traffic on a non standard port, for example `12345`. You can configure `logpush.yourdestinationendpoint.com` (without specifying a port, as Cloudflare by default only proxies traffic on HTTP/HTTPS ports) to proxy to `yourdestinationendpoint.com:12345`.
 
+
 ## 4. Configure Logpush
 
 1. Create a Logpush job with the following details:
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
index 271f74a01e3f258..037278d7af513e7 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/elastic.mdx
@@ -11,20 +11,22 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Push your Cloudflare logs to Elastic for instant visibility and insights. Enabling this integration with Elastic comes with a predefined dashboard to view all of your Cloudflare observability and security data with ease.
 
 The Cloudflare Logpush integration can be used in three different modes to collect data:
 
-- **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
-- **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
-- **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
+* **HTTP Endpoint mode** - Cloudflare pushes logs directly to an HTTP endpoint hosted by your Elastic Agent.
+* **AWS S3 polling mode** - Cloudflare writes data to S3, and the Elastic Agent polls the S3 bucket by listing its contents and reading new files.
+* **AWS S3 SQS mode** - Cloudflare writes data to S3, S3 pushes a new object notification to SQS, the Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.
 
 :::note[Note]
 
+
 Elastic recommends the AWS S3 SQS mode.
 
+
 :::
 
 ## Enable Logpush Job in Cloudflare
@@ -42,18 +44,17 @@ Add the same custom header along with its value on both sides for additional sec
 For example, while creating a job along with a header and value for a particular dataset:
 
 <APIRequest
-	path="/zones/{zone_id}/logpush/jobs"
-	method="POST"
-	json={{
-		name: "<PUBLIC_DOMAIN>",
-		destination_conf:
-			"https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
-		dataset: "http_requests",
-		output_options: {
-			field_names: ["RayID", "EdgeStartTimestamp"],
-			timestamp_format: "rfc3339",
-		},
-	}}
+  path="/zones/{zone_id}/logpush/jobs"
+  method="POST"
+  json={{
+    name: "<PUBLIC_DOMAIN>",
+    destination_conf: "https://<PUBLIC_DOMAIN>:<PUBLIC_PORT>?header_<SECRET_HEADER>=<SECRET_VALUE>",
+    dataset: "http_requests",
+    output_options: {
+      field_names: ["RayID", "EdgeStartTimestamp"],
+      timestamp_format: "rfc3339"
+    }
+  }}
 />
 
 ## Enable the Integration in Elastic
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
index 79d92a490df72b5..559b432c8b43b4e 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx
@@ -39,9 +39,9 @@ When you are done entering the destination details, select **Continue**.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
 9. In **Advanced Options**, you can:
-   - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
-   - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
-   - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
+    - Choose the format of timestamp fields in your logs (`RFC3339` (default), `Unix`, or `UnixNano`).
+    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
+    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
index bc517b5783e0a01..54b030d14362706 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-qradar.mdx
@@ -8,7 +8,7 @@ products:
   - logpush
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 To configure a QRadar/Cloudflare integration you have the option to use one of the following methods:
 
@@ -22,113 +22,57 @@ To send Cloudflare logs to QRadar you need to create a [Logpush job to HTTP endp
 ### Cloudflare Firewall events
 
 <APIRequest
-	method="POST"
-	path="/zones/{zone_id}/logpush/jobs"
-	json={{
-		name: "<NAME>",
-		output_options: {
-			field_names: [
-				"Action",
-				"ClientIP",
-				"ClientASN",
-				"ClientASNDescription",
-				"ClientCountry",
-				"ClientIPClass",
-				"ClientRefererHost",
-				"ClientRefererPath",
-				"ClientRefererQuery",
-				"ClientRefererScheme",
-				"ClientRequestHost",
-				"ClientRequestMethod",
-				"ClientRequestPath",
-				"ClientRequestProtocol",
-				"ClientRequestQuery",
-				"ClientRequestScheme",
-				"ClientRequestUserAgent",
-				"EdgeColoCode",
-				"EdgeResponseStatus",
-				"Kind",
-				"MatchIndex",
-				"Metadata",
-				"OriginResponseStatus",
-				"OriginatorRayID",
-				"RayID",
-				"RuleID",
-				"Source",
-				"Datetime",
-			],
-			timestamp_format: "rfc3339",
-		},
-		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-		max_upload_bytes: 5000000,
-		max_upload_records: 1000,
-		dataset: "firewall_events",
-		enabled: true,
-	}}
+  method="POST"
+  path="/zones/{zone_id}/logpush/jobs"
+  json={{
+    name: "<NAME>",
+    output_options: {
+      field_names: [
+        "Action", "ClientIP", "ClientASN", "ClientASNDescription", "ClientCountry", "ClientIPClass",
+        "ClientRefererHost", "ClientRefererPath", "ClientRefererQuery", "ClientRefererScheme",
+        "ClientRequestHost", "ClientRequestMethod", "ClientRequestPath", "ClientRequestProtocol",
+        "ClientRequestQuery", "ClientRequestScheme", "ClientRequestUserAgent", "EdgeColoCode",
+        "EdgeResponseStatus", "Kind", "MatchIndex", "Metadata", "OriginResponseStatus",
+        "OriginatorRayID", "RayID", "RuleID", "Source", "Datetime"
+      ],
+      timestamp_format: "rfc3339"
+    },
+    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+    max_upload_bytes: 5000000,
+    max_upload_records: 1000,
+    dataset: "firewall_events",
+    enabled: true
+  }}
 />
 
+
 ### Cloudflare HTTP events
 
 <APIRequest
-	method="POST"
-	path="/zones/{zone_id}/logpush/jobs"
-	json={{
-		name: "<NAME>",
-		output_options: {
-			field_names: [
-				"ClientRequestMethod",
-				"EdgeResponseStatus",
-				"ClientIP",
-				"ClientSrcPort",
-				"CacheCacheStatus",
-				"ClientCountry",
-				"ClientDeviceType",
-				"ClientIPClass",
-				"ClientMTLSAuthCertFingerprint",
-				"ClientMTLSAuthStatus",
-				"ClientRegionCode",
-				"ClientRequestBytes",
-				"ClientRequestHost",
-				"ClientRequestPath",
-				"ClientRequestProtocol",
-				"ClientRequestReferer",
-				"ClientRequestScheme",
-				"ClientRequestSource",
-				"ClientRequestURI",
-				"ClientRequestUserAgent",
-				"ClientSSLCipher",
-				"ClientSSLProtocol",
-				"ClientXRequestedWith",
-				"EdgeEndTimestamp",
-				"EdgeRequestHost",
-				"EdgeResponseBodyBytes",
-				"EdgeResponseBytes",
-				"EdgeServerIP",
-				"EdgeStartTimestamp",
-				"SecurityActions",
-				"SecurityRuleIDs",
-				"SecuritySources",
-				"OriginIP",
-				"OriginResponseStatus",
-				"OriginSSLProtocol",
-				"ParentRayID",
-				"RayID",
-				"SecurityAction",
-				"WAFAttackScore",
-				"SecurityRuleID",
-				"SecurityRuleDescription",
-				"WAFSQLiAttackScore",
-				"WAFXSSAttackScore",
-				"EdgeStartTimestamp",
-			],
-			timestamp_format: "rfc3339",
-		},
-		destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
-		max_upload_bytes: 5000000,
-		max_upload_records: 1000,
-		dataset: "http_requests",
-		enabled: true,
-	}}
+  method="POST"
+  path="/zones/{zone_id}/logpush/jobs"
+  json={{
+    name: "<NAME>",
+    output_options: {
+      field_names: [
+        "ClientRequestMethod", "EdgeResponseStatus", "ClientIP", "ClientSrcPort", "CacheCacheStatus",
+        "ClientCountry", "ClientDeviceType", "ClientIPClass", "ClientMTLSAuthCertFingerprint", "ClientMTLSAuthStatus",
+        "ClientRegionCode", "ClientRequestBytes", "ClientRequestHost", "ClientRequestPath", "ClientRequestProtocol",
+        "ClientRequestReferer", "ClientRequestScheme", "ClientRequestSource", "ClientRequestURI", "ClientRequestUserAgent",
+        "ClientSSLCipher", "ClientSSLProtocol", "ClientXRequestedWith", "EdgeEndTimestamp", "EdgeRequestHost",
+        "EdgeResponseBodyBytes", "EdgeResponseBytes", "EdgeServerIP", "EdgeStartTimestamp", "SecurityActions",
+        "SecurityRuleIDs", "SecuritySources", "OriginIP", "OriginResponseStatus", "OriginSSLProtocol", "ParentRayID",
+        "RayID", "SecurityAction", "WAFAttackScore", "SecurityRuleID", "SecurityRuleDescription", "WAFSQLiAttackScore",
+        "WAFXSSAttackScore", "EdgeStartTimestamp"
+      ],
+      timestamp_format: "rfc3339"
+    },
+    destination_conf: "<QRADAR_URL>:<LOG_SOURCE_PORT>",
+    max_upload_bytes: 5000000,
+    max_upload_records: 1000,
+    dataset: "http_requests",
+    enabled: true
+  }}
 />
 
 Cloudflare checks the accessibility of the IP address, port, and validates the certificate of the HTTP Receive log source. If all parameters are valid, a Logpush is created, and starts to send events to HTTP Receiver log source.
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
index e30073dde0691a1..c9e507400e4736f 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx
@@ -79,7 +79,7 @@ When configuring your Logpush job using IAM Access Keys, ensure that the IAM use
 kinesis://<STREAM_NAME>?region=<AWS_REGION>&access-key-id=<AWS_ACCESS_KEY_ID>&secret-access-key=<AWS_SECRET_ACCESS_KEY>
 ```
 
-### IAM Access Key example
+### IAM Access Key example 
 
 ```bash
 $ curl https://api.cloudflare.com/client/v4/zones/$ZONE_TAG/logpush/jobs \
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
index c8e74bd58ce5b1c..b5a8ad2efe5d08a 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/exabeam.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about exabeam in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
index e035c9cab36b111..ebd93fd74f3fe4e 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/sekoia.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about sekoia in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
index 9b27ff95df6e41f..33a79b6922e260b 100644
--- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/third-party/taegis.mdx
@@ -7,4 +7,4 @@ sidebar:
 description: Learn about taegis in Cloudflare Logs.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/filters.mdx b/src/content/docs/logs/logpush/logpush-job/filters.mdx
index 70fd97b0bc41bcc..e3d0dec59462d05 100644
--- a/src/content/docs/logs/logpush/logpush-job/filters.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/filters.mdx
@@ -100,11 +100,12 @@ Here is an example request using cURL via API:
 To set filters through the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
-
+ 
    For account: <DashButton url="/?to=/:account/logs" />
-
+ 
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
+
 2. Select the dataset you want to push to a storage service. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
 3. Below **Select data fields**, in the **Filter** section, you can set up your filters.
 4. You need to select a [dataset field](/logs/logpush/logpush-job/datasets/), an [Operator](/logs/logpush/logpush-job/filters/#logical-operators), and a **Value**.
diff --git a/src/content/docs/logs/logpush/logpush-job/index.mdx b/src/content/docs/logs/logpush/logpush-job/index.mdx
index 9f631a5d38edfd0..552977e3e38e2b6 100644
--- a/src/content/docs/logs/logpush/logpush-job/index.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/index.mdx
@@ -8,4 +8,4 @@ sidebar:
 description: Configure and manage Logpush job settings.
 products:
   - logpush
----
+---
\ No newline at end of file
diff --git a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
index 0c4922d8910409d..69caff8184b218b 100644
--- a/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
+++ b/src/content/docs/logs/logpush/logpush-job/logpush-ownership-challenge.mdx
@@ -70,17 +70,17 @@ Your bucket's IAM/access controls and Cloudflare account security are the primar
 
 ## Which destinations require an ownership challenge?
 
-| Destination           | Ownership challenge required       |
-| --------------------- | ---------------------------------- |
-| AWS S3                | Yes (or use access key/secret key) |
-| Google Cloud Storage  | Yes                                |
-| Azure Blob Storage    | Yes                                |
-| Sumo Logic            | Yes                                |
-| S3-compatible storage | No                                 |
-| HTTP endpoints        | No                                 |
-| Datadog               | No                                 |
-| Splunk                | No                                 |
-| New Relic             | No                                 |
+| Destination | Ownership challenge required |
+| --- | --- |
+| AWS S3 | Yes (or use access key/secret key) |
+| Google Cloud Storage | Yes |
+| Azure Blob Storage | Yes |
+| Sumo Logic | Yes |
+| S3-compatible storage | No |
+| HTTP endpoints | No |
+| Datadog | No |
+| Splunk | No |
+| New Relic | No |
 
 For destinations that do not require an ownership challenge, Cloudflare uses alternative authentication methods such as API keys or tokens.
 
diff --git a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
index b69e56fe07a33a4..090c84dab4fef92 100644
--- a/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
+++ b/src/content/docs/logs/reference/change-notices/2023-02-01-security-fields-updates.mdx
@@ -9,12 +9,12 @@ products:
   - logs
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components";
+import { GlossaryTooltip, DashButton } from "~/components"
 
 Cloudflare will deploy some updates to security-related fields in Cloudflare Logs. These updates will affect the following datasets:
 
-- [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
-- [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
+* [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/)
+* [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/)
 
 ## Timeline
 
@@ -26,18 +26,18 @@ For the log fields being added, Cloudflare will gradually start adding them to l
 
 For the log fields being renamed, Cloudflare will:
 
-- **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
-- **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
+* **Add new fields** with the same data as the fields that will be removed on phase 2 (described in this document as old fields). These new fields will become gradually available. Refer to the next sections for details.
+* **Announce the deprecation of the old fields.** Cloudflare will remove these fields from logs datasets on August 1, 2023.
 
 For the log fields being removed, Cloudflare is announcing them as deprecated. Their removal from logs datasets will occur on August 1, 2023.
 
 In addition to these Cloudflare Logs changes, Cloudflare will also add new security-related fields to the following [GraphQL datasets](/analytics/graphql-api/features/data-sets/):
 
-- `httpRequestsAdaptive `
-- `httpRequestsAdaptiveGroups`
-- `firewallEventsAdaptive`
-- `firewallEventsAdaptiveGroups`
-- `firewallEventsAdaptiveByTimeGroups`
+* `httpRequestsAdaptive `
+* `httpRequestsAdaptiveGroups`
+* `firewallEventsAdaptive`
+* `firewallEventsAdaptiveGroups`
+* `firewallEventsAdaptiveByTimeGroups`
 
 ### Phase 2 (August 1, 2023)
 
@@ -49,23 +49,27 @@ For the log fields being removed, Cloudflare will also remove them from the Clou
 
 The following concepts are used below in the reviewed field descriptions:
 
-- **Terminating action:** One of the following actions:
-  - `block`
-  - `js_challenge`
-  - `managed_challenge`
-  - `challenge` (_Interactive Challenge_)
+* **Terminating action:** One of the following actions:
+
+  * `block`
+  * `js_challenge`
+  * `managed_challenge`
+  * `challenge` (*Interactive Challenge*)
 
 For more information on these actions, refer to the [Actions](/ruleset-engine/rules-language/actions/) reference in the Rules language documentation.
 
-- **Security rule:** One of the following rule types:
-  - [WAF managed rule](/waf/managed-rules/)
-  - [WAF custom rule](/waf/custom-rules/)
-  - [WAF rate limiting rule](/waf/rate-limiting-rules/)
+* **Security rule:** One of the following rule types:
+
+  * [WAF managed rule](/waf/managed-rules/)
+  * [WAF custom rule](/waf/custom-rules/)
+  * [WAF rate limiting rule](/waf/rate-limiting-rules/)
 
 ## HTTP Requests dataset changes
 
 The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) dataset according to the two-phase strategy outlined in the [timeline](#timeline):
 
+
+
 | New field name            | Type         | Description                                                                        | Old field name<br/>(deprecated on Aug 1, 2023) |
 | ------------------------- | ------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------- |
 | `SecurityRuleID`          | String       | Rule ID of the security rule that triggered a terminating action, if any.          | `WAFRuleID`                                    |
@@ -75,8 +79,12 @@ The following fields will be renamed in the [HTTP Requests](/logs/logpush/logpus
 | `SecurityActions`         | String Array | Array of actions that Cloudflare security products performed on the request.       | `FirewallMatchesActions`                       |
 | `SecuritySources`         | String Array | Array of Cloudflare security products that matched the request.                    | `FirewallMatchesSources`                       |
 
+
+
 The following fields are now deprecated and they will be removed from the HTTP Requests dataset on August 1, 2023:
 
+
+
 | Deprecated field name | Notes                                                                 |
 | --------------------- | --------------------------------------------------------------------- |
 | `WAFProfile`          | Used in the previous version of WAF managed rules (now deprecated).   |
@@ -84,30 +92,44 @@ The following fields are now deprecated and they will be removed from the HTTP R
 | `EdgeRateLimitID`     | Used in the previous version of rate limiting rules (now deprecated). |
 | `SecurityLevel`       | N/A                                                                   |
 
+
+
 ## Firewall Events dataset changes
 
 The following fields will be added to the [Firewall Events](/logs/logpush/logpush-job/datasets/zone/firewall_events/) dataset:
 
+
+
 | Field name    | Type   | Description                                                        |
 | ------------- | ------ | ------------------------------------------------------------------ |
 | `Description` | String | The description of the rule triggered by the request.              |
 | `Ref`         | String | The user-defined identifier for the rule triggered by the request. |
 
+
+
 ## Changes to GraphQL datasets
 
 Cloudflare will add the following fields to the `httpRequestsAdaptive `and `httpRequestsAdaptiveGroups `datasets:
 
+
+
 | Field name       | Type   | Description                                                              |
 | ---------------- | ------ | ------------------------------------------------------------------------ |
 | `securityAction` | String | Action of the security rule that triggered a terminating action, if any. |
 | `securitySource` | String | Source of the security rule that triggered a terminating action, if any. |
 
+
+
 Cloudflare will also add the following field to the `firewallEventsAdaptive`, `firewallEventsAdaptiveGroups`, and `firewallEventsAdaptiveByTimeGroups` datasets:
 
+
+
 | Field name    | Type   | Description                                           |
 | ------------- | ------ | ----------------------------------------------------- |
 | `description` | String | The description of the rule triggered by the request. |
 
+
+
 These new fields will become gradually available.
 
 For more information on the available datasets, refer to [GraphQL datasets](/analytics/graphql-api/features/data-sets/).
@@ -121,8 +143,8 @@ After updating Logpush jobs, you may need to update external filters or reports
 ### Update Logpush job in the dashboard
 
 1. In the Cloudflare dashboard, go to the **Logpush** page.
-
-   <DashButton url="/?to=/:account/:zone/analytics/logs" />
+ 
+    <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Select **Edit** next to the Logpush job you wish to edit.
 3. Under **Select data fields**, update the fields in your job. The new security log fields are available under **General**.
@@ -130,7 +152,7 @@ After updating Logpush jobs, you may need to update external filters or reports
 
 ### Update Logpush job via API
 
-Follow the instructions in [Update output_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
+Follow the instructions in [Update output\_options](/logs/logpush/examples/example-logpush-curl/#optional---update-output_options) to update the fields in the Logpush job.
 
 ### Update Logpush job via Terraform
 
diff --git a/src/content/docs/logs/reference/change-notices/index.mdx b/src/content/docs/logs/reference/change-notices/index.mdx
index 9457944fa3b5f78..73f10f158563f08 100644
--- a/src/content/docs/logs/reference/change-notices/index.mdx
+++ b/src/content/docs/logs/reference/change-notices/index.mdx
@@ -11,6 +11,6 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/logs/reference/clientrequestsource.mdx b/src/content/docs/logs/reference/clientrequestsource.mdx
index 13558a727481adb..142639187d95beb 100644
--- a/src/content/docs/logs/reference/clientrequestsource.mdx
+++ b/src/content/docs/logs/reference/clientrequestsource.mdx
@@ -11,6 +11,8 @@ products:
 
 The possible values for the `ClientRequestSource` field are the following:
 
+
+
 | Value | Request source     | Description                                                                                                                             |
 | ----- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
 | `0`   | unknown            | Should never happen.                                                                                                                    |
@@ -26,3 +28,4 @@ The possible values for the `ClientRequestSource` field are the following:
 | `10`  | sslDetector        | A request made by Cloudflare's [SSL Detector system](https://blog.cloudflare.com/ssl-tls-recommender/).                                 |
 | `11`  | earlyHintsCache    | An [Early Hint request](https://blog.cloudflare.com/early-hints/).                                                                      |
 | `12`  | inBrowserChallenge | An end user request caused by a Cloudflare security product (Challenges, JavaScript Detections). These requests never reach the origin. |
+
diff --git a/src/content/docs/logs/reference/index.mdx b/src/content/docs/logs/reference/index.mdx
index 31fafb51510ff9a..2dee7feaa4467ed 100644
--- a/src/content/docs/logs/reference/index.mdx
+++ b/src/content/docs/logs/reference/index.mdx
@@ -9,7 +9,7 @@ products:
   - logs
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 These reference resources are useful for gaining a more in-depth understanding of the terminology and status codes that are part of the Cloudflare Logs data. This information is especially important when integrating your data with third-party tools:
 
diff --git a/src/content/docs/logs/reference/security-fields.mdx b/src/content/docs/logs/reference/security-fields.mdx
index af844e299e4e427..c1dfac2c6154b28 100644
--- a/src/content/docs/logs/reference/security-fields.mdx
+++ b/src/content/docs/logs/reference/security-fields.mdx
@@ -13,6 +13,8 @@ The Security fields contain rules to block requests that contain specific types
 
 ## SecurityActions
 
+
+
 | Value                                  | Action         | Description                                                                                                                                                |
 | -------------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `unknown`                              | Unknown        | Take no other action.                                                                                                                                      |
@@ -25,15 +27,19 @@ The Security fields contain rules to block requests that contain specific types
 | `challengeSolved`                      | Allow          | Allow once interactive challenge solved.                                                                                                                   |
 | `challengeBypassed`                    | Allow          | Interactive challenge is not issued again because the visitor had previously passed an interactive challenge and a valid `cf_clearance` cookie is present. |
 | `jschallengeSolved`                    | Allow          | Allow once non-interactive challenge solved.                                                                                                               |
-| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                 |
+| `jschallengeBypassed`                  | Allow          | Non-interactive challenge not issued because the visitor had previously passed a non-interactive or interactive challenge.                                  |
 | `bypass`                               | Allow          | Bypass all subsequent firewall rules.                                                                                                                      |
 | `managedChallenge`                     | Challenge Drop | Issue managed challenge.                                                                                                                                   |
 | `managedChallengeNonInteractiveSolved` | Allow          | Allow once the managed challenge is solved via non-interactive interstitial page.                                                                          |
 | `managedChallengeInteractiveSolved`    | Allow          | Allow once the managed challenged is solved via interactive interstitial page.                                                                             |
 | `managedChallengeBypassed`             | Allow          | Challenge was not presented because visitor had clearance from previous challenge.                                                                         |
 
+
+
 ## SecuritySources
 
+
+
 | Value             | Description                                                                                                      |
 | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
 | `unknown`         | Used if an event is received from a new source but the logging system has not been updated.                      |
diff --git a/src/content/docs/logs/reference/waf-fields.mdx b/src/content/docs/logs/reference/waf-fields.mdx
index e53ba194338c1b2..421f434955eb3f0 100644
--- a/src/content/docs/logs/reference/waf-fields.mdx
+++ b/src/content/docs/logs/reference/waf-fields.mdx
@@ -13,6 +13,8 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 
 ## WAF Action
 
+
+
 | Value                                      | Action          | Description                                  |
 | ------------------------------------------ | --------------- | -------------------------------------------- |
 | <span style="font-weight: 400;">`0`</span> | Unknown         | Take no other action.                        |
@@ -22,9 +24,11 @@ The Web Application Firewall (WAF) contains rules managed by Cloudflare to block
 | <span style="font-weight: 400;">`4`</span> | Challenge Drop  | Unused.                                      |
 | <span style="font-weight: 400;">`5`</span> | Log             | Take no action other than logging the event. |
 
+
+
 ## Deprecated fields for internal Cloudflare use
 
 The values of these fields are subject to change by Cloudflare at any time and are irrelevant for customer data analysis:
 
-- WAFFlags
-- WAFMatchedVar
+* WAFFlags
+* WAFMatchedVar
diff --git a/src/content/docs/magic-transit/about.mdx b/src/content/docs/magic-transit/about.mdx
index dc0086ba6a2fe2a..d24ff959ee90edf 100644
--- a/src/content/docs/magic-transit/about.mdx
+++ b/src/content/docs/magic-transit/about.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: About Magic Transit
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Magic Transit is a network security and performance solution that offers Distributed Denial of Service ([DDoS](/ddos-protection/)) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 
diff --git a/src/content/docs/magic-transit/alerts.mdx b/src/content/docs/magic-transit/alerts.mdx
index f8cadf60286d59c..c0c7de7a4836d78 100644
--- a/src/content/docs/magic-transit/alerts.mdx
+++ b/src/content/docs/magic-transit/alerts.mdx
@@ -6,9 +6,10 @@ products:
   - magic-transit
 sidebar:
   order: 14
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your network.
 
diff --git a/src/content/docs/magic-transit/analytics/index.mdx b/src/content/docs/magic-transit/analytics/index.mdx
index dfe4e5e0295bb7b..04ca8e61b7d11ce 100644
--- a/src/content/docs/magic-transit/analytics/index.mdx
+++ b/src/content/docs/magic-transit/analytics/index.mdx
@@ -13,14 +13,13 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/overview"
+<Render file="analytics/overview"
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
 		traceRoutes: "/magic-transit/analytics/traceroutes/",
 		graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
-		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/",
-	}}
-/>
+		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
+		 }}
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/analytics/network-analytics.mdx b/src/content/docs/magic-transit/analytics/network-analytics.mdx
index c872539c3620160..14e7c6f5b8cbfd3 100644
--- a/src/content/docs/magic-transit/analytics/network-analytics.mdx
+++ b/src/content/docs/magic-transit/analytics/network-analytics.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit Network Analytics
+
 ---
 
 import { Render } from "~/components";
 
-<Render
-	file="analytics/network-analytics"
+<Render file="analytics/network-analytics"
 	product="networking-services"
 	params={{
-		magicWord: "Magic Transit",
+		magicWord: "Magic Transit"
 	}}
 />
diff --git a/src/content/docs/magic-transit/analytics/packet-captures.mdx b/src/content/docs/magic-transit/analytics/packet-captures.mdx
index 8ef49043b64053d..0dd8a83c52fb2da 100644
--- a/src/content/docs/magic-transit/analytics/packet-captures.mdx
+++ b/src/content/docs/magic-transit/analytics/packet-captures.mdx
@@ -7,4 +7,5 @@ title: Packet captures
 external_link: /cloudflare-network-firewall/packet-captures/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
index 6f46709874eb1bc..e20b8573ade07d3 100644
--- a/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
+++ b/src/content/docs/magic-transit/analytics/query-bandwidth.mdx
@@ -11,10 +11,9 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-bandwidth-graphql"
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
 	product="networking-services"
 	params={{ productName: "Magic Transit" }}
 />
diff --git a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
index 347e8ce8854d5cd..ec044cf25d36e9c 100644
--- a/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
+++ b/src/content/docs/magic-transit/analytics/query-tunnel-health.mdx
@@ -11,10 +11,8 @@ tags:
   - Shell
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="graphql/query-magic-transit-health-checks"
+<Render file="graphql/query-magic-transit-health-checks"
 	product="networking-services"
-	params={{ productName: "Magic Transit" }}
-/>
+	params={{ productName: "Magic Transit" }} />
diff --git a/src/content/docs/magic-transit/changelog.mdx b/src/content/docs/magic-transit/changelog.mdx
index f3d81cf0accb7be..df426867ae71afe 100644
--- a/src/content/docs/magic-transit/changelog.mdx
+++ b/src/content/docs/magic-transit/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/magic-transit/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="magic-transit"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="magic-transit" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/magic-transit/cloudflare-ips.mdx b/src/content/docs/magic-transit/cloudflare-ips.mdx
index 9812bcc56adb708..4ee1316b242c1ab 100644
--- a/src/content/docs/magic-transit/cloudflare-ips.mdx
+++ b/src/content/docs/magic-transit/cloudflare-ips.mdx
@@ -8,26 +8,23 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="magic-transit/cloudflare-ips"
 	product="networking-services"
 	params={{
 		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		mtLpStaticRoute:
-			"/magic-transit/how-to/configure-routes/#configure-static-routes",
-		mtLpBgpPeering:
-			"/magic-transit/how-to/configure-routes/#configure-bgp-routes",
-	}}
-/>
+		mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
+		mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
+		}} />
 
 ## Check your Cloudflare IPs
 
 <Render
-	file="check-leased-ips"
+  file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "Anycast IPs for Magic Transit",
+		product: "Anycast IPs for Magic Transit"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/get-started.mdx b/src/content/docs/magic-transit/get-started.mdx
index 8efc46ed319d06b..eec224e8dbadd55 100644
--- a/src/content/docs/magic-transit/get-started.mdx
+++ b/src/content/docs/magic-transit/get-started.mdx
@@ -10,10 +10,6 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/get-started"
-	product="networking-services"
-	params={{ magicWord: "Magic Transit" }}
-/>
+<Render file="magic-transit/get-started" product="networking-services" params={{ magicWord: "Magic Transit" }} />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/glossary.mdx b/src/content/docs/magic-transit/glossary.mdx
index 089812e9c6ecd3e..b14631d9375bd84 100644
--- a/src/content/docs/magic-transit/glossary.mdx
+++ b/src/content/docs/magic-transit/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Magic Transit documentation.
 products:
   - magic-transit
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Magic Transit documentation.
 
diff --git a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
index e8f018925c30330..ec7bc738458e71d 100644
--- a/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
+++ b/src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
@@ -8,15 +8,7 @@ sidebar:
   order: 5
 ---
 
-import {
-	APIRequest,
-	DashButton,
-	Details,
-	GlossaryTooltip,
-	Render,
-	Tabs,
-	TabItem,
-} from "~/components";
+import { APIRequest, DashButton, Details, GlossaryTooltip, Render, Tabs, TabItem } from "~/components"
 
 ## Onboard prefixes
 
@@ -75,11 +67,11 @@ You should only use one control method per prefix at any given time. Mixing mult
 Create a [POST request](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/create/) to add a BGP prefix. For example:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
-	method="POST"
-	json={{
-		cidr: "192.0.2.0/24",
-	}}
+  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes"
+  method="POST"
+  json={{
+    "cidr": "192.0.2.0/24"
+  }}
 />
 
 ### Advertise or withdraw a BGP prefix
@@ -125,7 +117,7 @@ Refer to [Safely withdraw a BYOIP prefix](#safely-withdraw-a-byoip-prefix) for m
 
 ### Delete an IP prefix
 
-You can only delete a prefix with an _Unapproved_ status. To delete prefixes with a different status, contact your administrator or account manager.
+You can only delete a prefix with an *Unapproved* status. To delete prefixes with a different status, contact your administrator or account manager.
 
 1. Go to the **Routes** page.
 
@@ -145,11 +137,11 @@ BGP has different mechanisms to control route priorities which are set by the pe
 Refer to the following example for how to prepend AS13335 three times to a BGP prefix:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-	method="PATCH"
-	json={{
-		asn_prepend_count: 3,
-	}}
+path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+method="PATCH"
+json={{
+	"asn_prepend_count": 3
+}}
 />
 
 AS prepending helps you gracefully transition traffic between network providers. By adding prepends to Cloudflare's advertisement, you make the route through Cloudflare less preferred for some Internet network providers. This allows you to simultaneously advertise the same prefix from an alternate provider with a shorter, more desirable `AS_PATH`. Advertising from both providers at once provides a smoother traffic migration and minimizes packet loss during a change of provider.
@@ -163,6 +155,8 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
 - **Introduce new provider**: You begin advertising the same prefix from your alternate provider with a standard (shorter) `AS_PATH`.
 - **Final state**: External networks now receive two advertisements: the prepended route through Cloudflare and the non-prepended route through your new provider. The external network will select a path based on its BGP policy rules.
 
+
+
 :::caution
 Cloudflare's internal network enforces local preference for traffic delivery to Magic Transit, even if a more specific or shorter path route is available on the public Internet. Withdraw the prefix from Cloudflare to avoid delivery of Cloudflare-sourced traffic over Magic Transit. This preference is local to our internal network and does not impact the route decision process of other networks.
 
@@ -171,32 +165,27 @@ For example, if you have a CDN zone with a Magic Transit-protected origin that i
 
 ## Safely withdraw a BYOIP prefix
 
-<Render
-	file="magic-transit/safely-withdraw-byoip-prefix"
-	product="networking-services"
-/>
+<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
 
 ## BGP control to Magic Transit Virtual Network routing table
 
 ### Automatically announce and withdraw anycast-based Magic BGP routes
 
 If you use CNI with Dataplane v2, GRE or IPsec tunnels, you can:
-
 - Automatically withdraw your prefixes from Cloudflare's global edge infrastructure when you withdraw all matching BGP learned prefixes from the Magic Transit Virtual Network routing table.
 - Automatically advertise your prefixes through Cloudflare's global edge infrastructure when you have at least one matching BGP learned prefix in the Magic Transit Virtual Network routing table.
 
 To enable automatic global announcement and withdrawal, enable this feature on the BGP prefix using the [Addressing API](/api/resources/addressing/subresources/prefixes/subresources/bgp_prefixes/methods/edit/). For example:
 
 <APIRequest
-	path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
-	method="PATCH"
-	json={{
-		auto_advertise_withdraw: true,
-	}}
+  path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bgp/prefixes/{bgp_prefix_id}"
+  method="PATCH"
+  json={{
+    "auto_advertise_withdraw": true
+  }}
 />
 
 Once you configure this for a BGP prefix, Cloudflare applies the following logic:
-
 - If there are no BGP routes in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare withdraws the BGP prefix.
 - If there is at least one BGP route in the Magic Transit Virtual Network routing table exactly matching the BGP prefix, Cloudflare announces the BGP prefix.
 
@@ -327,10 +316,7 @@ If you use CNI with Dataplane v2, GRE or IPsec tunnels to on-ramp your network t
 
 Magic Transit supports both static routing and BGP to steer traffic from Cloudflare's network to your configured off-ramps (GRE tunnels, IPsec tunnels, or CNI). Cloudflare does not currently support advertisement of routes for traffic engineering purposes. As a best practice to reduce last-hop latency, consider scoping your routes regionally.
 
-<Render
-	file="reference/traffic-steering-region-codes"
-	product="networking-services"
-/>
+<Render file="reference/traffic-steering-region-codes" product="networking-services" />
 
 The default setting for static route regions is **All Regions**. Configure scoping for your traffic in the **Region code** section when [adding](/magic-transit/how-to/configure-routes/#create-a-static-route) or [editing](/magic-transit/how-to/configure-routes/#edit-a-static-route) a static route.
 
diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx
index 0dfce207230821b..c3053044b8b28e3 100644
--- a/src/content/docs/magic-transit/how-to/configure-routes.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx
@@ -11,7 +11,7 @@ tags:
   - IPsec
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="routing/configure-routes"
@@ -21,16 +21,12 @@ import { Render } from "~/components";
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		routePrioritization:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		chooseWeights:
-			"/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
-		publicAsnMT:
-			"[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
 		productGatewayOrEgress: "Magic Transit with Egress",
-		unifiedRoutingModeURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		unifiedRoutingModeURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		virtualNetworkName: "Magic Transit Virtual Network",
-		routingTableName: "Magic Transit Virtual Network routing table",
+		routingTableName: "Magic Transit Virtual Network routing table"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
index ab317378e353ddc..af1eee331945798 100644
--- a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
@@ -14,31 +14,23 @@ tags:
 
 import { Render } from "~/components";
 
-<Render
-	file="routing/configure-tunnels"
+<Render file="routing/configure-tunnels"
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/",
-		ciphersPagePath:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
-		updateHCFrequencyPage:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		biVsUniHealthCheckDefaults:
-			"For Magic Transit this option defaults to unidirectional",
+		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
-		unifiedRoutingURL:
-			"/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
-		troubleshootTunnelHealthURL:
-			"/magic-transit/troubleshooting/tunnel-health/",
-		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/",
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
+		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
+		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
index 7910debecdaac0e..ccf843678ccbee2 100644
--- a/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
+++ b/src/content/docs/magic-transit/how-to/enable-magic-roles.mdx
@@ -7,6 +7,6 @@ head: []
 description: You can determine which users have, or do not have, configuration edit access for Magic products.
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="magic-user-role" product="networking-services" />
diff --git a/src/content/docs/magic-transit/how-to/index.mdx b/src/content/docs/magic-transit/how-to/index.mdx
index a80f260452a9bd5..962bded34f466cd 100644
--- a/src/content/docs/magic-transit/how-to/index.mdx
+++ b/src/content/docs/magic-transit/how-to/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
index 95d51e29e27e30d..b08bce6faedffc0 100644
--- a/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/docs/magic-transit/how-to/safely-withdraw-byoip-prefix.mdx
@@ -8,9 +8,6 @@ sidebar:
   order: 6
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="magic-transit/safely-withdraw-byoip-prefix"
-	product="networking-services"
-/>
+<Render file="magic-transit/safely-withdraw-byoip-prefix" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-flow.mdx b/src/content/docs/magic-transit/network-flow.mdx
index d77808bebde34fe..9af74ab7d1573b5 100644
--- a/src/content/docs/magic-transit/network-flow.mdx
+++ b/src/content/docs/magic-transit/network-flow.mdx
@@ -6,15 +6,16 @@ products:
   - magic-transit
 sidebar:
   order: 10
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
 	}}
 />
diff --git a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
index 7218ba148af08d2..99ee9ad379632a8 100644
--- a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
+++ b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
@@ -14,13 +14,11 @@ import { Render } from "~/components";
 	file="tunnel-health/check-tunnel-healthchecks-dash"
 	product="networking-services"
 	params={{
-		dashInfo:
-			"The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
+		dashInfo: "The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",
 		graphQL: "/magic-transit/analytics/query-tunnel-health/",
-		notificationsPath:
-			"[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
+		notificationsPath: "[notifications wizard](/magic-transit/network-health/configure-tunnel-health-alerts/)",
 		packetCaptures: "/cloudflare-network-firewall/packet-captures/",
-		networkAnalytics: "/magic-transit/analytics/network-analytics/",
+		networkAnalytics: "/magic-transit/analytics/network-analytics/"
 	}}
 />
 
@@ -28,7 +26,7 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
 />
 
@@ -36,4 +34,4 @@ import { Render } from "~/components";
 
 If you received a tunnel health alert but are unsure whether it affects your traffic, refer to [Troubleshoot connectivity](/magic-transit/troubleshooting/connectivity/) to determine whether the alert is relevant.
 
-If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
+If your tunnels show as unhealthy or degraded, refer to [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) for common issues and solutions.
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
index 32dcf34acba8937..d606ec4dcd288b1 100644
--- a/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/network-health/configure-tunnel-health-alerts.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation:
-			"/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/index.mdx b/src/content/docs/magic-transit/network-health/index.mdx
index ac18e64e89dac4c..909456bebc21630 100644
--- a/src/content/docs/magic-transit/network-health/index.mdx
+++ b/src/content/docs/magic-transit/network-health/index.mdx
@@ -8,23 +8,23 @@ sidebar:
   order: 6
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Magic Transit uses health check probes to determine the status of tunnels. Cloudflare uses this information to steer traffic through the best available route and warn you about potential issues with a tunnel. Service-level indicators (SLIs) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [How Cloudflare calculates tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts/) for more information about SLIs and SLOs.
 
 There are two types of health checks available: endpoint and tunnel health checks.
 
-- Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
+ - Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Endpoint probes flow over available tunnels to provide a broad picture of Internet health and do not inform tunnel selection or steering logic.
 
-  Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
+	Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
 
-  During onboarding, you specify IP addresses to configure endpoint health checks.
+	During onboarding, you specify IP addresses to configure endpoint health checks.
 
 - Tunnel health checks monitor the status of the tunnels that route traffic from Cloudflare to your origin network. Magic Transit relies on health checks to steer traffic to the best available routes.
 
-  During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
+	During onboarding, you specify the tunnel endpoints or tunnel health check targets that the tunnel probes from Cloudflare's global network will monitor.
 
-  You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
+	You can access tunnel health check results through the API. Cloudflare aggregates these results from individual health check results on Cloudflare servers.
 
 Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/) for a deep dive into the different types of health checks, what they do, and how they work.
 
@@ -32,10 +32,10 @@ Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/)
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
 />
 
 Refer to the following pages for details on how to use the various network health checks available.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
index 3fedb7f8c2cb1a3..b734e7357208bff 100644
--- a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
+++ b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
@@ -14,7 +14,7 @@ tags:
   - ICMP
 ---
 
-import { CURL, Render, DashButton } from "~/components";
+import { CURL, Render, DashButton } from '~/components';
 
 Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
 
@@ -43,35 +43,32 @@ Refer to the [API documentation](/api/resources/diagnostics/subresources/endpoin
 <Render file="account-id-api-key" product="networking-services" />
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-	method="POST"
-	json={{
-		check_type: "icmp",
-		endpoint: "8.31.160.1",
-		name: "Datacenter 1 - primary",
-	}}
+  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+  method="POST"
+  json={{
+    "check_type": "icmp",
+    "endpoint": "8.31.160.1",
+    "name": "Datacenter 1 - primary"
+  }}
 />
 
 ```json output
 {
-	"result": {
-		"id": "<HEALTH_CHECK_ID>",
-		"check_type": "icmp",
-		"endpoint": "8.31.160.1",
-		"name": "Datacenter 1 - primary"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+    "result": {
+        "id": "<HEALTH_CHECK_ID>",
+        "check_type": "icmp",
+        "endpoint": "8.31.160.1",
+        "name": "Datacenter 1 - primary"
+    },
+    "success": true,
+    "errors": [],
+    "messages": []
 }
 ```
 
 ## Query endpoint health checks with GraphQL
 
-<Render
-	file="graphql/query-magic-transit-endpoint-health-checks"
-	product="networking-services"
-/>
+<Render file="graphql/query-magic-transit-endpoint-health-checks" product="networking-services" />
 
 ## Configure alerts for endpoint health checks
 
@@ -80,23 +77,23 @@ You can set up alerts to be notified when the state of your endpoint's health is
 1. Make a `GET` request to get a list of IDs for all of the endpoint health checks configured:
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
-	method="GET"
+  url="https://api.cloudflare.com/client/v4/accounts/account_id/diagnostics/endpoint-healthcheck"
+  method="GET"
 />
 
 ```json output
 {
-	"result": [
-		{
-			"id": "<HEALTH_CHECK_ID>",
-			"check_type": "icmp",
-			"endpoint": "8.31.160.1",
-			"name": "Datacenter 1 - primary"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+    "result": [
+        {
+            "id": "<HEALTH_CHECK_ID>",
+            "check_type": "icmp",
+            "endpoint": "8.31.160.1",
+            "name": "Datacenter 1 - primary"
+        }
+    ],
+    "success": true,
+    "errors": [],
+    "messages": []
 }
 ```
 
@@ -106,13 +103,13 @@ You can set up alerts to be notified when the state of your endpoint's health is
 <DashButton url="/?to=/:account/notifications" />
 
 4. Select **Add**.
-5. From the drop-down menu, select _Magic Transit_.
+5. From the drop-down menu, select *Magic Transit*.
 6. Select **Magic Endpoint Health Check Alert**.
 7. Provide a name for your new notification and optionally provide a description.
-8. In the _Service Level Objective (SLO)_ drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
-   - **High** - 99%
-   - **Medium** - 98%
-   - **Low** - 97%
+8. In the *Service Level Objective (SLO)* drop-down menu, select the SLO threshold for your notification. The SLO defines the percentage of endpoint health checks that must pass. If the number of passing endpoint health checks falls below the SLO, Cloudflare generates an alert:
+	- **High** - 99%
+	- **Medium** - 98%
+	- **Low** - 97%
 9. In the drop-down menu below SLOs, select the `id` value that matches the `id` you got through the API in step 1. This `id` should match the endpoint health check you want to get notifications for.
 10. Select your preferred notification method (such as email or webhooks).
 11. Select **Save**.
diff --git a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
index cc01a8092fae660..5abf823c7864447 100644
--- a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks-frequency.mdx
@@ -17,8 +17,7 @@ import { Render } from "~/components";
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",
-		addTunnelsPath:
-			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		addTunnelsPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels"
 	}}
 />
 
@@ -26,6 +25,6 @@ import { Render } from "~/components";
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
+		productName: "Magic Transit"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/network-interconnect.mdx b/src/content/docs/magic-transit/network-interconnect.mdx
index d9cb97232b3510b..44619ba947f13ef 100644
--- a/src/content/docs/magic-transit/network-interconnect.mdx
+++ b/src/content/docs/magic-transit/network-interconnect.mdx
@@ -13,4 +13,4 @@ head:
 
 import { Render } from "~/components";
 
-<Render file="magic-cni" product="networking-services" />
+<Render file="magic-cni" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/on-demand.mdx b/src/content/docs/magic-transit/on-demand.mdx
index 75c387b34768ef6..019f50728fcda3c 100644
--- a/src/content/docs/magic-transit/on-demand.mdx
+++ b/src/content/docs/magic-transit/on-demand.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Magic Transit on-demand
+
 ---
 
 If you have access to the Magic Transit on-demand option, you can [configure prefix advertisement](/byoip/concepts/dynamic-advertisement/best-practices/#configure-dynamic-advertisement) from the **IP Prefixes** page in your Cloudflare account home or through the [Cloudflare API](/api/resources/addressing/subresources/prefixes/subresources/advertisement_status/methods/edit/).
diff --git a/src/content/docs/magic-transit/partners/index.mdx b/src/content/docs/magic-transit/partners/index.mdx
index 6ee348692df331a..bfd05db0b774788 100644
--- a/src/content/docs/magic-transit/partners/index.mdx
+++ b/src/content/docs/magic-transit/partners/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 15
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
index 535769eb632525c..7bc128098d8f68c 100644
--- a/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
+++ b/src/content/docs/magic-transit/reference/anti-replay-protection.mdx
@@ -18,8 +18,7 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic Transit",
-		productPath:
-			"/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
+		productPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
index dc972d88c678590..6b1bfa5d9f79f7f 100644
--- a/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
+++ b/src/content/docs/magic-transit/reference/gre-ipsec-tunnels.mdx
@@ -22,13 +22,12 @@ import { Render } from "~/components";
 		mssURL: "/magic-transit/get-started/#set-maximum-segment-size",
 		productURL: "/magic-transit/reference/anti-replay-protection/",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		magicWord: "Magic Transit",
+		magicWord: "Magic Transit"
 	}}
 />
 
 ## Troubleshooting
 
 For help resolving tunnel issues:
-
 - [Troubleshoot tunnel health](/magic-transit/troubleshooting/tunnel-health/) - Diagnose and fix health check failures
 - [Troubleshoot with IPsec logs](/magic-transit/troubleshooting/ipsec-troubleshoot/) - Use Logpush to analyze IPsec handshake issues
diff --git a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
index f9fbf42cffa7459..1fba89abfb6a2f8 100644
--- a/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
+++ b/src/content/docs/magic-transit/reference/how-cloudflare-calculates-tunnel-health-alerts.mdx
@@ -8,12 +8,9 @@ sidebar:
   order: 9
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="reference/magic-tunnels-slos"
+<Render file="reference/magic-tunnels-slos"
 	product="networking-services"
-	params={{
-		tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down",
-	}}
+	params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#down" }}
 />
diff --git a/src/content/docs/magic-transit/reference/index.mdx b/src/content/docs/magic-transit/reference/index.mdx
index fe0a8581aa501bb..19ff0a30a962cbc 100644
--- a/src/content/docs/magic-transit/reference/index.mdx
+++ b/src/content/docs/magic-transit/reference/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 16
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/magic-transit/reference/mtu-mss.mdx b/src/content/docs/magic-transit/reference/mtu-mss.mdx
index c35b312d04d675d..aea2b11b3a8ca3a 100644
--- a/src/content/docs/magic-transit/reference/mtu-mss.mdx
+++ b/src/content/docs/magic-transit/reference/mtu-mss.mdx
@@ -20,6 +20,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
-		productName: "Magic Transit",
-	}}
+		productName: "Magic Transit"
+		}}
 />
diff --git a/src/content/docs/magic-transit/reference/traffic-steering.mdx b/src/content/docs/magic-transit/reference/traffic-steering.mdx
index 3864fa3d06c3f68..6343ed66f6690f6 100644
--- a/src/content/docs/magic-transit/reference/traffic-steering.mdx
+++ b/src/content/docs/magic-transit/reference/traffic-steering.mdx
@@ -22,8 +22,7 @@ import { Render } from "~/components";
 		routingTableName: "Magic Transit Virtual Network routing table",
 		mFirewallName: "Cloudflare Network Firewall",
 		mFirewallURL: "/cloudflare-network-firewall/",
-		warpClientURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
+		warpClientURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/",
 		remoteBrowserURL: "/cloudflare-one/remote-browser-isolation/",
 		accessURL: "/cloudflare-one/access-controls/policies/",
 		gatewayURL: "/cloudflare-one/traffic-policies/",
diff --git a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
index 9f4b6435299ad5a..cc8c425a16b925c 100644
--- a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
+++ b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
@@ -20,12 +20,11 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		addTunnels: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels",
-		changeHealthCheckRate:
-			"/magic-transit/network-health/update-tunnel-health-checks-frequency/",
+		changeHealthCheckRate: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
 		staticRoutes: "/magic-transit/how-to/configure-routes/",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/"
 	}}
 />
 
diff --git a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
index bc19d9e2ed3a087..ff5293328e0537b 100644
--- a/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/connectivity.mdx
@@ -17,9 +17,8 @@ import { Render } from "~/components";
 		productName: "Magic Transit",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
 		routingBgpLink: "/magic-transit/troubleshooting/routing-and-bgp/",
-		checkHealthDashLink:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
+		checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
 		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
 	}}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/index.mdx b/src/content/docs/magic-transit/troubleshooting/index.mdx
index 24dc284181dfdf0..6487eea738df77b 100644
--- a/src/content/docs/magic-transit/troubleshooting/index.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/index.mdx
@@ -12,6 +12,6 @@ tags:
   - Debugging
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
index 3ad6b0cbb6091ce..bacfef32c5f77a3 100644
--- a/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/ipsec-troubleshoot.mdx
@@ -12,17 +12,15 @@ tags:
   - Logging
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="ipsec-logs-troubleshooting"
+<Render file="ipsec-logs-troubleshooting"
 	product="networking-services"
 	params={{
-		supportedIpsecConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+		supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
 		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		mtuMssLink: "/magic-transit/reference/mtu-mss/",
+		mtuMssLink: "/magic-transit/reference/mtu-mss/"
 	}}
 />
 
@@ -31,7 +29,6 @@ import { Render } from "~/components";
 Some customer routers cannot fully disable IPsec anti-replay protection, which is required for optimal Magic Transit operation (packet reordering at the Cloudflare edge can otherwise trigger false drops).
 
 **If your router does not support disabling anti-replay:**
-
 1. Check whether your router supports configuring a **replay window size**. Setting this to `0` is equivalent to disabling anti-replay protection.
 2. If neither disabling anti-replay nor setting the window size to `0` is supported, **the router cannot be used as a Magic Transit IPsec on-ramp**. Consider using a GRE tunnel or Cloudflare Network Interconnect (CNI) instead.
 
@@ -44,3 +41,4 @@ If your ISP is blocking these response packets, health checks will fail even whe
 **Symptom:** Health checks fail but application traffic flows normally through the tunnel.
 
 **Resolution:** Switch to bidirectional health checks, which send both the probe and the response through the tunnel. Bidirectional health checks require egress traffic to be turned on for your Magic Transit configuration. For more information, refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/).
+
diff --git a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
index 43b9bb867569e75..d207cbb1af0bab8 100644
--- a/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/routing-and-bgp.mdx
@@ -11,15 +11,14 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="troubleshoot-routing-bgp"
-	product="networking-services"
-	params={{
-		magicWord: "Magic Transit",
-		productName: "Magic Transit",
-		trafficSteeringLink:
-			"/magic-transit/reference/traffic-steering/#route-prioritization",
-		configureRoutesLink: "/magic-transit/how-to/configure-routes/",
-		tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-	}}
+  file="troubleshoot-routing-bgp"
+  product="networking-services"
+  params={{
+    magicWord: "Magic Transit",
+    productName: "Magic Transit",
+    trafficSteeringLink: "/magic-transit/reference/traffic-steering/#route-prioritization",
+    configureRoutesLink: "/magic-transit/how-to/configure-routes/",
+    tunnelHealthLink: "/magic-transit/troubleshooting/tunnel-health/",
+    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/"
+  }}
 />
diff --git a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
index 747fc6d131cd7b6..1f0887e6040a0f8 100644
--- a/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
+++ b/src/content/docs/magic-transit/troubleshooting/tunnel-health.mdx
@@ -14,20 +14,17 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/troubleshoot-tunnel-health"
-	product="networking-services"
-	params={{
-		productName: "Magic Transit",
-		healthCheckDefault: "_Unidirectional_ (direct server return)",
-		tunnelsConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-		checkHealthDashLink:
-			"/magic-transit/network-health/check-tunnel-health-dashboard/",
-		antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
-		tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
-		configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
-		networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
-		supportedIpsecConfigLink:
-			"/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
-	}}
+  file="tunnel-health/troubleshoot-tunnel-health"
+  product="networking-services"
+  params={{
+    productName: "Magic Transit",
+    healthCheckDefault: "_Unidirectional_ (direct server return)",
+    tunnelsConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
+    checkHealthDashLink: "/magic-transit/network-health/check-tunnel-health-dashboard/",
+    antiReplayLink: "/magic-transit/reference/anti-replay-protection/",
+    tunnelHealthChecksLink: "/magic-transit/reference/tunnel-health-checks/",
+    configureTunnelsLink: "/magic-transit/how-to/configure-tunnel-endpoints/",
+    networkAnalyticsLink: "/magic-transit/analytics/network-analytics/",
+    supportedIpsecConfigLink: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters"
+  }}
 />
diff --git a/src/content/docs/moq/feature-matrix.mdx b/src/content/docs/moq/feature-matrix.mdx
index 92148c292bc4988..200715e6e3a4ba2 100644
--- a/src/content/docs/moq/feature-matrix.mdx
+++ b/src/content/docs/moq/feature-matrix.mdx
@@ -3,80 +3,81 @@ pcx_content_type: get-started
 title: MoQ Feature Matrix
 sidebar:
   order: 18
+
 ---
 
 ## Draft-14 Messages
 
 ### Supported
 
-| Message                            | Support | Relevant specification                                                                           |
-| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_CANCEL           | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_OK               | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_ERROR            | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_OK                         | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE                  | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_NAMESPACE_DONE             | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_DONE                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_OK                    | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_CANCEL | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_NAMESPACE_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_DONE | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_OK | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ### Unsupported
 
-| Message                   | Support | Relevant specification                                                                           |
-| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| GOAWAY                    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| MAX_REQUEST_ID            | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| REQUESTS_BLOCKED          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| PUBLISH_ERROR             | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH                     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_OK                  | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_ERROR               | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| TRACK_STATUS_ERROR        | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE       | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_OK    | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| SUBSCRIBE_NAMESPACE_ERROR | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
-| UNSUBSCRIBE_NAMESPACE     | No      | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| GOAWAY | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| MAX_REQUEST_ID | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| REQUESTS_BLOCKED | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| PUBLISH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| FETCH_CANCEL | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| TRACK_STATUS_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_OK | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| SUBSCRIBE_NAMESPACE_ERROR | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
+| UNSUBSCRIBE_NAMESPACE | No | [draft-ietf-moq-transport-14](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-14) |
 
 ## Draft-07 Messages
 
 ### Supported
 
-| Message                            | Support | Relevant specification                                                                           |
-| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| ANNOUNCE_OK                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_ERROR                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE_CANCEL                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE                          | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE                        | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS_REQUEST               | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| ANNOUNCE                           | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNANNOUNCE                         | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_OK                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ERROR                    | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_DONE                     | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| MAX_SUBSCRIBE_ID                   | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| TRACK_STATUS                       | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SETUP_MESSAGES (client and server) | ✅      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| ANNOUNCE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE_CANCEL | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS_REQUEST | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| ANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNANNOUNCE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_OK | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ERROR | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_DONE | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| MAX_SUBSCRIBE_ID | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| TRACK_STATUS | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SETUP_MESSAGES (client and server) | ✅ | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
 
 ### Unsupported
 
-| Message                   | Support | Relevant specification                                                                           |
-| ------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
-| SUBSCRIBE_UPDATE          | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| GOAWAY                    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES       | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_OK    | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| SUBSCRIBE_ANNOUNCES_ERROR | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| UNSUBSCRIBE_ANNOUNCES     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH                     | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_OK                  | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_ERROR               | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
-| FETCH_CANCEL              | No      | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| Message | Support | Relevant specification |
+| ------- | ------- | ---------------------- |
+| SUBSCRIBE_UPDATE | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| GOAWAY | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| SUBSCRIBE_ANNOUNCES_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| UNSUBSCRIBE_ANNOUNCES | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_OK | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_ERROR | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
+| FETCH_CANCEL | No | [draft-ietf-moq-transport-07](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) |
diff --git a/src/content/docs/moq/index.mdx b/src/content/docs/moq/index.mdx
index d02f8400089cf48..838ca1c7516741e 100644
--- a/src/content/docs/moq/index.mdx
+++ b/src/content/docs/moq/index.mdx
@@ -22,7 +22,7 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Frequently Asked Questions
 
-- What about Safari?
+* What about Safari?
 
   Safari does not yet have fully functional WebTransport support. Apple never publicly commits to timelines for new features like this. However, Apple has indicated their [intent to support WebTransport](https://github.com/WebKit/standards-positions/issues/18#issuecomment-1495890122). An Apple employee is even a co-author of the [WebTransport over HTTP/3](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/) draft. Since Safari 18.4 (2025-03-31), an early (not yet fully functional) implementation of the WebTransport API has been available for testing behind a developer-mode / advanced settings feature flag (including on iOS).
 
@@ -30,12 +30,12 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
 
 ## Known Issues
 
-- Extra Subgroup header field
-
-  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits.
+* Extra Subgroup header field
 
+  The current implementation includes a `subscribe_id` field in Subgroup Headers which [`draft-ietf-moq-transport-07`](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-07) omits. 
+  
   In section 7.3.1, `draft-ietf-moq-transport-07` [specifies](https://www.ietf.org/archive/id/draft-ietf-moq-transport-07.html#section-7.3.1):
-
+  
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Track Alias (i),
@@ -44,9 +44,8 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-
+  
   Whereas our implementation expects and produces:
-
   ```txt
   STREAM_HEADER_SUBGROUP Message {
     Subscribe ID (i),
@@ -56,5 +55,5 @@ For the most up-to-date documentation on the protocol, please visit the IETF wor
     Publisher Priority (8),
   }
   ```
-
+  
   This was erroroneously left over from a previous draft version and will be fixed in a future release. Thank you to [@yuki-uchida](https://github.com/yuki-uchida) for reporting.
diff --git a/src/content/docs/multi-cloud-networking/changelog.mdx b/src/content/docs/multi-cloud-networking/changelog.mdx
index 4bbf7ded14ca757..4374533a030deb1 100644
--- a/src/content/docs/multi-cloud-networking/changelog.mdx
+++ b/src/content/docs/multi-cloud-networking/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/multi-cloud-networking/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="multi-cloud-networking"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="multi-cloud-networking" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-11-21
 
diff --git a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
index d20a8425820479e..d388a38c069f08b 100644
--- a/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
+++ b/src/content/docs/multi-cloud-networking/cloud-on-ramps.mdx
@@ -6,15 +6,12 @@ products:
 title: Cloud on-ramps
 sidebar:
   order: 3
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render
-	file="routing/mcn-cloudflare-wan-on-ramps"
+<Render file="routing/mcn-cloudflare-wan-on-ramps"
 	product="networking-services"
-	params={{
-		mwanAccount:
-			"Have a Cloudflare WAN account. Contact your account team to learn more.",
-	}}
+	params={{ mwanAccount: "Have a Cloudflare WAN account. Contact your account team to learn more." }}
 />
diff --git a/src/content/docs/multi-cloud-networking/get-started.mdx b/src/content/docs/multi-cloud-networking/get-started.mdx
index ef3448467003242..04c91b1108e2aa5 100644
--- a/src/content/docs/multi-cloud-networking/get-started.mdx
+++ b/src/content/docs/multi-cloud-networking/get-started.mdx
@@ -25,7 +25,7 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 1. Go to the **Cloud integrations (beta)** page.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **AWS integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -38,29 +38,29 @@ Once Cloudflare has the credentials required to access your cloud environments,
 
 ```json
 {
-	"Version": "2012-10-17",
-	"Statement": [
-		{
-			"Effect": "Allow",
-			"Action": [
-				"ec2:AcceptTransitGatewayPeeringAttachment",
-				"ec2:CreateTransitGatewayPeeringAttachment",
-				"ec2:DeleteTransitGatewayPeeringAttachment",
-				"ec2:DescribeRegions",
-				"ec2:DescribeTransitGatewayPeeringAttachments",
-				"ec2:RejectTransitGatewayPeeringAttachment",
-				"ec2:GetManagedPrefixListEntries",
-				"ec2:CreateManagedPrefixList",
-				"ec2:ModifyManagedPrefixList",
-				"ec2:DeleteManagedPrefixList",
-				"ec2:CreateTransitGatewayPrefixListReference",
-				"ec2:DeleteTransitGatewayPrefixListReference",
-				"ec2:GetTransitGatewayPrefixListReferences",
-				"ec2:ModifyTransitGatewayPrefixListReference"
-			],
-			"Resource": "*"
-		}
-	]
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "ec2:AcceptTransitGatewayPeeringAttachment",
+                "ec2:CreateTransitGatewayPeeringAttachment",
+                "ec2:DeleteTransitGatewayPeeringAttachment",
+                "ec2:DescribeRegions",
+                "ec2:DescribeTransitGatewayPeeringAttachments",
+                "ec2:RejectTransitGatewayPeeringAttachment",
+                "ec2:GetManagedPrefixListEntries",
+                "ec2:CreateManagedPrefixList",
+                "ec2:ModifyManagedPrefixList",
+                "ec2:DeleteManagedPrefixList",
+                "ec2:CreateTransitGatewayPrefixListReference",
+                "ec2:DeleteTransitGatewayPrefixListReference",
+                "ec2:GetTransitGatewayPrefixListReferences",
+                "ec2:ModifyTransitGatewayPrefixListReference"
+            ],
+            "Resource": "*"
+        }
+    ]
 }
 ```
 
@@ -69,15 +69,15 @@ Once Cloudflare has the credentials required to access your cloud environments,
 1. Create an [AWS role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html) with the following settings:
    - **Trusted entity type**: Select **Custom trust policy**, and paste the custom trust policy returned by the Cloudflare dashboard.
    - **Permissions**: Add the IAM policy you created in the previous step, along with these AWS-managed policies:
-     - `NetworkAdministrator`
-     - `AmazonEC2ReadOnlyAccess`
-     - `AmazonVPCReadOnlyAccess`
-     - `IAMReadOnlyAccess`
+      - `NetworkAdministrator`
+      - `AmazonEC2ReadOnlyAccess`
+      - `AmazonVPCReadOnlyAccess`
+      - `IAMReadOnlyAccess`
    - **ARN**: Copy the ARN for your newly created user.
 
    :::note
-   The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-   :::
+	 The trust policy may take several minutes to propagate to all regions. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+	 :::
 
 2. Select **I authorize Cloudflare to access my AWS account.**
 3. Select **Authorize**.
@@ -92,7 +92,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Azure integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -115,8 +115,8 @@ Multi-Cloud Networking does not support personal Microsoft accounts. Sign in usi
 6. In **Verify account ownership**, [add the tags displayed in the Cloudflare dashboard](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources-portal).
 
    :::note
-   The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
-   :::
+	 The tags may take several minutes to propagate and become readable to Cloudflare. It usually takes less than four minutes, but can sometimes take longer. You may have to retry the **Authorize** button while the propagation takes effect.
+	 :::
 
 7. Select **I authorize Cloudflare to access my Azure account.** If your account does not have administrator privileges, you may need to pass this link to an account that has administrator privileges.
 8. Select **Authorize**.
@@ -131,7 +131,7 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. In the Cloudflare dashboard, go to **Cloud integrations (beta)**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select **Add** > **Google integration**.
 3. Give a descriptive name to your integration. Optionally, you can also add a description for it.
@@ -142,8 +142,8 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 1. Create a new [GCP service account](https://cloud.google.com/iam/docs/service-accounts-create) in your **Google account** > **GCP Console** > **IAM & Admin** > **Service Accounts**.
 2. Grant the new service account these roles:
-   - `Compute Network Admin`
-   - `Compute Viewer`
+	- `Compute Network Admin`
+	- `Compute Viewer`
 3. Under **IAM & Admin** > **Service Accounts**, select the service account you just created, and navigate to the **Permissions** tab.
 4. Grant the **Service Account Token Creator** role to our bot account to allow it to impersonate this service account. Learn how to grant a specific role [in Google's documentation](https://cloud.google.com/iam/docs/manage-access-service-accounts#grant-single-role):
    - `mcn-integrations-bot-prod@mcn-gcp-01.iam.gserviceaccount.com`
@@ -163,4 +163,4 @@ The first discovery of resources may not succeed in all regions while the IAM po
 
 - [Set up Cloudflare WAN](/multi-cloud-networking/cloud-on-ramps/) as an on-ramp to your cloud.
 - [Manage resources](/multi-cloud-networking/manage-resources/) found by Multi-Cloud Networking.
-- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
+- [Edit](/multi-cloud-networking/manage-resources/#edit-cloud-integrations) cloud integrations.
\ No newline at end of file
diff --git a/src/content/docs/multi-cloud-networking/manage-resources.mdx b/src/content/docs/multi-cloud-networking/manage-resources.mdx
index b9eb3e0bc385769..4307d7b9da2de5c 100644
--- a/src/content/docs/multi-cloud-networking/manage-resources.mdx
+++ b/src/content/docs/multi-cloud-networking/manage-resources.mdx
@@ -6,6 +6,7 @@ products:
 title: Manage resources
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,7 +19,7 @@ To browse the resources in your catalog:
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select a resource to inspect its details.
@@ -29,7 +30,7 @@ You can change which cloud account the integration is linked to or delete the in
 
 1. Go to **Cloud integrations**.
 
-   <DashButton url="/?to=/:account/mcn/integrations" />
+	<DashButton url="/?to=/:account/mcn/integrations" />
 
 2. Select your integration > **Edit**.
 3. In **Linked account details**, select **Link integration to a different cloud account**.
@@ -42,7 +43,7 @@ You can download a JSON file containing metadata and configuration for all your
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud resources**, select **Download catalog**.
diff --git a/src/content/docs/multi-cloud-networking/reference.mdx b/src/content/docs/multi-cloud-networking/reference.mdx
index 16d0b78776c4c47..8c37c24b0eabb74 100644
--- a/src/content/docs/multi-cloud-networking/reference.mdx
+++ b/src/content/docs/multi-cloud-networking/reference.mdx
@@ -6,6 +6,7 @@ products:
 title: Reference
 sidebar:
   order: 5
+
 ---
 
 Refer to this page for details about how Cloudflare orchestrates VPN connectivity to your cloud networks.
diff --git a/src/content/docs/network-error-logging/get-started.mdx b/src/content/docs/network-error-logging/get-started.mdx
index 2b07fd6d29a8e84..e211ba22e5e901a 100644
--- a/src/content/docs/network-error-logging/get-started.mdx
+++ b/src/content/docs/network-error-logging/get-started.mdx
@@ -6,6 +6,7 @@ products:
   - network-error-logging
 tags:
   - Logging
+
 ---
 
 import { DashButton } from "~/components";
@@ -16,7 +17,7 @@ To enable Network Error Logging for Free and Pro zones:
 
 1. In the Cloudflare dashboard, go to the **Account home** page.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **Network** and locate **Network Error Logging Monitoring**.
 3. Select the toggle to enable Network Error Logging.
diff --git a/src/content/docs/network-error-logging/how-to.mdx b/src/content/docs/network-error-logging/how-to.mdx
index 74f33f4e7eeadff..6aac695c1d00025 100644
--- a/src/content/docs/network-error-logging/how-to.mdx
+++ b/src/content/docs/network-error-logging/how-to.mdx
@@ -11,20 +11,21 @@ head:
 description: NEL reports show you why a request failed, the country a request
   failed from, and last mile network a request failed from, and the likely
   intended Cloudflare data center.
+
 ---
 
 import { DashButton } from "~/components";
 
 Use NEL reports to view information such as:
 
-- Why a request failed
-- The country a request failed from
-- The last mile network a request failed from
-- The Cloudflare data center the request was most likely meant for
+* Why a request failed
+* The country a request failed from
+* The last mile network a request failed from
+* The Cloudflare data center the request was most likely meant for
 
 1. Log in to your Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select **Analytics & Logs** > **Edge Reachability**.
 
diff --git a/src/content/docs/network-error-logging/index.mdx b/src/content/docs/network-error-logging/index.mdx
index 9f1acd04e344ba5..b712cac7782fb54 100644
--- a/src/content/docs/network-error-logging/index.mdx
+++ b/src/content/docs/network-error-logging/index.mdx
@@ -34,21 +34,21 @@ A sample Network Error Report payload appears as follows:
 
 ```json
 {
-	"age": 20,
-	"type": "network-error",
-	"url": "https://example.com/previous-page",
-	"body": {
-		"elapsed_time": 18,
-		"method": "POST",
-		"phase": "dns",
-		"protocol": "http/1.1",
-		"referrer": "https://example.com/previous-page",
-		"sampling_fraction": 1,
-		"server_ip": "",
-		"status_code": 0,
-		"type": "dns.name_not_resolved",
-		"url": "https://example-host.com/"
-	}
+  "age": 20,
+  "type": "network-error",
+  "url": "https://example.com/previous-page",
+  "body": {
+    "elapsed_time": 18,
+    "method": "POST",
+    "phase": "dns",
+    "protocol": "http/1.1",
+    "referrer": "https://example.com/previous-page",
+    "sampling_fraction": 1,
+    "server_ip": "",
+    "status_code": 0,
+    "type": "dns.name_not_resolved",
+    "url": "https://example-host.com/"
+  }
 }
 ```
 
@@ -56,9 +56,9 @@ A sample Network Error Report payload appears as follows:
 
 Cloudflare uses geolocation lookups to extract the following information from every client IP in a NEL report:
 
-- Client ASN
-- Client country
-- Client metro area
+* Client ASN
+* Client country
+* Client metro area
 
 Cloudflare uses internal lookups to associate the above data with a customer domain and customer account.
 
@@ -67,10 +67,9 @@ Cloudflare does not store any PII or user-specific data, and any IP data is only
 The client IP address is only stored in volatile memory for the lifetime of the request to Cloudflare’s NEL endpoint (order of milliseconds) and is dropped immediately after the request completes. Cloudflare does not log the client IP address anywhere in the Network Error Logging pipeline.
 
 NEL reports contain information about the end user's network conditions, which could be considered sensitive. Cloudflare takes privacy seriously and has implemented the following safeguards:
-
-- Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
-- Reports do not contain personally identifiable information (PII).
-- Customers can opt out of having their end users consume the NEL headers using one of the following methods:
+* Reports are sent to Cloudflare's infrastructure and are not shared with third parties.
+* Reports do not contain personally identifiable information (PII).
+* Customers can opt out of having their end users consume the NEL headers using one of the following methods:
   1. **Self-service (Zone setting)** — Use the dashboard toggle or API (`PATCH /zones/{zone_id}/settings/nel`) to disable NEL for your zone. This can be re-enabled by any zone administrator at any time.
   2. **Permanent opt-out via Support** — Contact Cloudflare support to have the `nel___enable` feature flag disabled at the product level. This prevents NEL from being enabled on your zone entirely and cannot be reversed by zone administrators.
-     For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
+For Free and Pro plans, the dashboard toggle is typically sufficient. Enterprise customers with strict privacy requirements may prefer the permanent support-level opt-out.
diff --git a/src/content/docs/network-flow/api.mdx b/src/content/docs/network-flow/api.mdx
index 86093e48a9529bf..abedf0335eb08a4 100644
--- a/src/content/docs/network-flow/api.mdx
+++ b/src/content/docs/network-flow/api.mdx
@@ -6,8 +6,9 @@ products:
   - network-flow
 sidebar:
   order: 9
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="mnm/api" product="networking-services" />
+<Render file="mnm/api" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/changelog.mdx b/src/content/docs/network-flow/changelog.mdx
index c0a384cb7ba3378..b94beaa04726a51 100644
--- a/src/content/docs/network-flow/changelog.mdx
+++ b/src/content/docs/network-flow/changelog.mdx
@@ -13,7 +13,4 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-flow/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="network-flow"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="network-flow" hideEntry="2024-06-16-cloudflare-one"/>
diff --git a/src/content/docs/network-flow/cloud-flow-logs.mdx b/src/content/docs/network-flow/cloud-flow-logs.mdx
index 1f7b9357b839a4c..b3b71aa0230d535 100644
--- a/src/content/docs/network-flow/cloud-flow-logs.mdx
+++ b/src/content/docs/network-flow/cloud-flow-logs.mdx
@@ -16,4 +16,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/cloud-flow-logs" product="networking-services" />
+<Render file="mnm/cloud-flow-logs" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/faq.mdx b/src/content/docs/network-flow/faq.mdx
index 7f18175619785c3..83e76018f873f71 100644
--- a/src/content/docs/network-flow/faq.mdx
+++ b/src/content/docs/network-flow/faq.mdx
@@ -11,6 +11,6 @@ sidebar:
   order: 11
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="mnm/faqs" product="networking-services" />
+<Render file="mnm/faqs" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/get-started.mdx b/src/content/docs/network-flow/get-started.mdx
index 4c52c7365d5e149..8129f8e3bb7ce5a 100644
--- a/src/content/docs/network-flow/get-started.mdx
+++ b/src/content/docs/network-flow/get-started.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/get-started" product="networking-services" />
+<Render file="mnm/get-started" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/glossary.mdx b/src/content/docs/network-flow/glossary.mdx
index 3000aa1c392cf88..560fd3884273263 100644
--- a/src/content/docs/network-flow/glossary.mdx
+++ b/src/content/docs/network-flow/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - network-flow
 sidebar:
   order: 10
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Network Flow (formerly Magic Network Monitoring) documentation.
 
diff --git a/src/content/docs/network-flow/magic-transit-integration.mdx b/src/content/docs/network-flow/magic-transit-integration.mdx
index 0b4ac3859f62b97..8defa83ac2a41fc 100644
--- a/src/content/docs/network-flow/magic-transit-integration.mdx
+++ b/src/content/docs/network-flow/magic-transit-integration.mdx
@@ -8,15 +8,16 @@ tags:
   - Integration
 sidebar:
   order: 7
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render
 	file="mnm-magic-transit-integration"
 	product="networking-services"
 	params={{
 		productName: "Network Flow",
-		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement",
+		rulesAutoAdvertiseURL: "/network-flow/rules/#rule-auto-advertisement"
 	}}
 />
diff --git a/src/content/docs/network-flow/network-flow-free.mdx b/src/content/docs/network-flow/network-flow-free.mdx
index 645bf56f6cb3a17..ca7198f7f03d8fe 100644
--- a/src/content/docs/network-flow/network-flow-free.mdx
+++ b/src/content/docs/network-flow/network-flow-free.mdx
@@ -11,6 +11,6 @@ head:
     content: Network Flow free version
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="mnm/network-flow-free" product="networking-services" />
diff --git a/src/content/docs/network-flow/routers/index.mdx b/src/content/docs/network-flow/routers/index.mdx
index 476c0017b240362..dc7bb414eb48ca9 100644
--- a/src/content/docs/network-flow/routers/index.mdx
+++ b/src/content/docs/network-flow/routers/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
index 58e65c53add4e60..3d1f2222d0b7878 100644
--- a/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
+++ b/src/content/docs/network-flow/routers/netflow-ipfix-config.mdx
@@ -11,8 +11,9 @@ sidebar:
 head: []
 description: A step-by-step configuration guide for exporting NetFlow or IPFIX
   data to Cloudflare's network.
+
 ---
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
+<Render file="mnm/routers/netflow-ipfix-config" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
index b8cd99b68ae977e..82158fe7ad97cf0 100644
--- a/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
+++ b/src/content/docs/network-flow/routers/recommended-sampling-rate.mdx
@@ -9,6 +9,7 @@ sidebar:
   order: 2
 head: []
 description: The best sampling rate recommendations for your network's traffic volume.
+
 ---
 
 import { Render } from "~/components";
@@ -16,4 +17,4 @@ import { Render } from "~/components";
 <Render
 	file="mnm/routers/recommended-sampling-rate"
 	product="networking-services"
-/>
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/sflow-config.mdx b/src/content/docs/network-flow/routers/sflow-config.mdx
index 5b7ba843d316df0..ee37c4c868a8ac4 100644
--- a/src/content/docs/network-flow/routers/sflow-config.mdx
+++ b/src/content/docs/network-flow/routers/sflow-config.mdx
@@ -14,4 +14,7 @@ description: A step-by-step configuration guide for exporting sFlow data to
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/sflow-config" product="networking-services" />
+<Render
+	file="mnm/routers/sflow-config"
+	product="networking-services"
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/routers/supported-routers.mdx b/src/content/docs/network-flow/routers/supported-routers.mdx
index 410865594728185..45a57d81dc9d9a9 100644
--- a/src/content/docs/network-flow/routers/supported-routers.mdx
+++ b/src/content/docs/network-flow/routers/supported-routers.mdx
@@ -13,4 +13,7 @@ description: A list of open source, NetFlow, and sFlow routers.
 
 import { Render } from "~/components";
 
-<Render file="mnm/routers/supported-routers" product="networking-services" />
+<Render
+	file="mnm/routers/supported-routers"
+	product="networking-services"
+	/>
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/index.mdx b/src/content/docs/network-flow/rules/index.mdx
index ff541e592e5802a..ef9d83a02553c40 100644
--- a/src/content/docs/network-flow/rules/index.mdx
+++ b/src/content/docs/network-flow/rules/index.mdx
@@ -14,3 +14,4 @@ sidebar:
 import { Render } from "~/components";
 
 <Render file="mnm/rules/overview" product="networking-services" />
+
diff --git a/src/content/docs/network-flow/rules/rule-notifications.mdx b/src/content/docs/network-flow/rules/rule-notifications.mdx
index cfc447c89cb41dd..0f85c34f0e1fd3d 100644
--- a/src/content/docs/network-flow/rules/rule-notifications.mdx
+++ b/src/content/docs/network-flow/rules/rule-notifications.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/rule-notifications" product="networking-services" />
+<Render file="mnm/rules/rule-notifications" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
index 34d38296b6570d4..9dfff3f061f5c5d 100644
--- a/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
+++ b/src/content/docs/network-flow/rules/s-flow-ddos-attack.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
+<Render file="mnm/rules/s-flow-ddos-attack" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/rules/static-threshold.mdx b/src/content/docs/network-flow/rules/static-threshold.mdx
index fa5fca21e7cef6f..172ca611aa68db2 100644
--- a/src/content/docs/network-flow/rules/static-threshold.mdx
+++ b/src/content/docs/network-flow/rules/static-threshold.mdx
@@ -10,4 +10,4 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="mnm/rules/static-threshold" product="networking-services" />
+<Render file="mnm/rules/static-threshold" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
index d43167ed7936fd7..0b0bb68e1ebbc8d 100644
--- a/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
+++ b/src/content/docs/network-flow/tutorials/ddos-testing-guide.mdx
@@ -15,4 +15,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
+<Render file="mnm/tutorials/ddos-testing-guide" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
index 8b86d643dd5ade2..f7562708d10bd0d 100644
--- a/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
+++ b/src/content/docs/network-flow/tutorials/encrypt-network-flow-data.mdx
@@ -19,7 +19,4 @@ description: >-
 
 import { Render } from "~/components";
 
-<Render
-	file="mnm/tutorials/encrypt-network-flow-data"
-	product="networking-services"
-/>
+<Render file="mnm/tutorials/encrypt-network-flow-data" product="networking-services" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
index 26f062040cac4f3..00c00c094490f32 100644
--- a/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
+++ b/src/content/docs/network-flow/tutorials/graphql-analytics.mdx
@@ -20,4 +20,4 @@ import { Render } from "~/components";
 
 <Render file="mnm/tutorials/graphql-analytics" product="networking-services" />
 
-<Render file="case-sensitivity-note" product="analytics" />
+<Render file="case-sensitivity-note" product="analytics" />
\ No newline at end of file
diff --git a/src/content/docs/network-flow/tutorials/index.mdx b/src/content/docs/network-flow/tutorials/index.mdx
index a13ee6bc966bfd7..8fae75e32ca4f24 100644
--- a/src/content/docs/network-flow/tutorials/index.mdx
+++ b/src/content/docs/network-flow/tutorials/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/network-interconnect/changelog.mdx b/src/content/docs/network-interconnect/changelog.mdx
index 64c3877fd409947..5b15e2c668e23f3 100644
--- a/src/content/docs/network-interconnect/changelog.mdx
+++ b/src/content/docs/network-interconnect/changelog.mdx
@@ -13,10 +13,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/changelog/network-interconnect/. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductChangelog
-	product="network-interconnect"
-	hideEntry="2024-06-16-cloudflare-one"
-/>
+<ProductChangelog product="network-interconnect" hideEntry="2024-06-16-cloudflare-one"/>
 
 ## 2024-10-01
 
diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx
index daba42777661fd5..16c0b376aa76fb9 100644
--- a/src/content/docs/network-interconnect/get-started.mdx
+++ b/src/content/docs/network-interconnect/get-started.mdx
@@ -11,7 +11,7 @@ tags:
   - GCP
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 :::note[BGP architecture and resiliency]
 CNI supports BGP peering with the Cloudflare Virtual Network routing table. BGP over CNI is in closed beta and is not currently available to new customers. If you are interested in BGP peering over CNI, contact your account team.
@@ -26,7 +26,7 @@ For detailed information about BGP architecture, Edge Resiliency Mode, and route
 Your Cloudflare account team determines CNI eligibility and port availability. Notably:
 
 - CNI ports are currently offered at no charge to Enterprise customers.
-  - Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
+	- Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy](https://www.cloudflare.com/peering-policy/).
 - CNI is available at select Cloudflare data centers:
   - The type of Dataplane offered in that location will determine specifications of the supported connection, such as the MTU.
   - The diversity offered in the location will vary.
@@ -43,37 +43,36 @@ To peer with Cloudflare, advertise prefixes with a prefix length of `/24` or sho
 ## Technical specifications
 
 - **Supported port types**:
-  - **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
-  - **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
+	- **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber).
+	- **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported.
 - **Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection.
 - **IP addressing:** All CNI connections and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare.
 - **VLAN support:**
-  - **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
-  - **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
+	- **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag.
+	- **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported.
 - **MTU considerations:**
-  - **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
-  - **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
+	- **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress).
+	- **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement.
 - **Bidirectional Forwarding Detection (BFD):**
-  - **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
-  - **Dataplane v2**: Not yet supported.
+	- **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks.
+	- **Dataplane v2**: Not yet supported.
 - **Link Aggregation Control Protocol (LACP)**:
-  - **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
-  - **Dataplane v2**: Not yet supported. Use ECMP instead.
+	- **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare.
+	- **Dataplane v2**: Not yet supported. Use ECMP instead.
 
 ## Performance characteristics
 
 The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration.
 
-| Direction (use case)                            | 10G Circuit                                                                                     | 100G Circuit                                                                                    |
-| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| From Cloudflare to Customer (all use cases)     | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
-| From Customer to Cloudflare (peering use case)  | Up to 10 Gbps                                                                                   | Up to 100 Gbps                                                                                  |
-| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection |
+| Direction (use case) | 10G Circuit | 100G Circuit |
+|----------------------|-------------|--------------|
+| From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps |
+| From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI <br /> **v2**: Up to 1 Gbps per CNI connection  |
 
 ## Service expectations
 
 Consider the following service levels when planning your deployment:
-
 - **No Formal SLA**:
   - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms).
   - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel.
@@ -99,8 +98,8 @@ The process of provisioning a CNI typically takes two to four weeks, depending o
 1. **Submit request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process.
 2. **Review configuration**: For the v1 Dataplane, the Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document. For the v2 Dataplane, this step is not necessary.
 3. **Order connection**:
-   - For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
-   - For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
+	- For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator.
+	- For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal.
 4. **Configure network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document.
 5. **Test and verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and, if applicable, verify that the BGP session can be established.
 6. Enable tunnel health checks for [Magic Transit](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) and/or [Cloudflare WAN](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#add-tunnels).
@@ -143,7 +142,7 @@ To connect to AWS Direct Connect:
 
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select **Create an interconnect**.
 3. Under **Cloud Interconnect**, select **Create new**.
@@ -163,5 +162,9 @@ You can now select **View interconnects** for a list of all interconnects on you
 
 After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect:
 
-- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP: - Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths. - Note that routes advertised by BGP from GCP Cloud Router will be ignored.
-- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router: - Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes). - Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
+- To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP:
+		- Add [static routes](/cloudflare-wan/configuration/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](/cloudflare-wan/configuration/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths.
+		- Note that routes advertised by BGP from GCP Cloud Router will be ignored.
+- To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router:
+		- Add [custom learned routes to Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes).
+		- Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over.
diff --git a/src/content/docs/network-interconnect/index.mdx b/src/content/docs/network-interconnect/index.mdx
index 9b63e926dc454eb..80bde6dd95d9bb1 100644
--- a/src/content/docs/network-interconnect/index.mdx
+++ b/src/content/docs/network-interconnect/index.mdx
@@ -11,10 +11,10 @@ head:
     content: Overview
 ---
 
-import { Description, Plan, RelatedProduct, Render } from "~/components";
+import { Description, Plan, RelatedProduct, Render } from "~/components"
 
 <Description>
-	Connect your network infrastructure directly to Cloudflare
+Connect your network infrastructure directly to Cloudflare
 </Description>
 
 <Plan type="enterprise" />
@@ -24,7 +24,6 @@ Cloudflare Network Interconnect (CNI) allows you to connect your network infrast
 ## Benefits
 
 Enterprises use CNI to achieve:
-
 - **Enhanced Performance**: Gain lower latency and more consistent network throughput.
 - **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet.
 
@@ -32,16 +31,15 @@ Enterprises use CNI to achieve:
 
 Choose the connection type for your infrastructure and operational needs.
 
-|                    | Direct Interconnect                                                                                                     | Partner Interconnect                                                                                       | Cloud Interconnect                                                                                                                              |
-| ------------------ | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Port type**      | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners.            | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare.             |
-| **Operations**     | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment.                    | Your partner manages the connection logistics, often through a software-defined networking portal.         | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
-| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability.                     | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services.                                    |
+| | Direct Interconnect | Partner Interconnect | Cloud Interconnect |
+| --- | --- | --- | --- |
+| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare. |
+| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
+| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. |
 
 ## Dataplane
 
 Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection:
-
 - **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports Generic Routing Encapsulation (GRE) tunnels for connecting with the Cloudflare Virtual Network, with optional GRE-less delivery for Magic Transit Direct Server Return.
 - **Dataplane v2**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte Maximum Transmission Unit (MTU) bidirectionally.
 
@@ -57,25 +55,15 @@ To protect against a single point of failure, it is critical to design your CNI
 
 Refer to [Service Expectations](/network-interconnect/get-started/#service-expectations) for more information.
 
----
+***
 
 ## Related products
 
-<RelatedProduct
-	header="Magic Transit"
-	href="/magic-transit/"
-	product="magic-transit"
->
-	Magic Transit is a network security and performance solution that offers
-	Distributed Denial of Service (DDoS) protection, traffic acceleration, and
-	more for on-premise, cloud-hosted, and hybrid networks.
+<RelatedProduct header="Magic Transit" href="/magic-transit/" product="magic-transit">
+Magic Transit is a network security and performance solution that offers Distributed Denial of Service (DDoS) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks.
 </RelatedProduct>
 
-<RelatedProduct
-	header="Cloudflare WAN"
-	href="/cloudflare-wan/"
-	product="cloudflare-wan"
->
-	Improve security and performance for your entire corporate network, reducing
-	cost and operation complexity.
+<RelatedProduct header="Cloudflare WAN" href="/cloudflare-wan/" product="cloudflare-wan">
+Improve security and performance for your entire corporate network, reducing cost and operation complexity.
 </RelatedProduct>
+
diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
index 1b73b9485ee8d93..861b447fcad7132 100644
--- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
+++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx
@@ -8,7 +8,7 @@ sidebar:
   order: 5
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 ## Monitoring
 
@@ -22,18 +22,17 @@ The Status column displays three statuses:
 - **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
 - **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The **Pending** status will disappear after the customer completes the cross-connect and status moves to **Active**.
 
+
 ## Alerts (v1 dataplane only)
 
 You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
 
 **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only.
-
 - You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections.
 - You will be notified if the details of a scheduled maintenance change or if it is canceled.
 - For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments.
 
 **Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network.
-
 - You will be warned about potentially disruptive maintenance at the PoP level.
 - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these.
 - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits.
@@ -44,7 +43,7 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
+	<DashButton url="/?to=/:account/notifications" />
 
 2. Select **Add**.
 3. From the product drop-down menu, select _Cloudflare Network Interconnect_.
@@ -56,10 +55,9 @@ You can configure notifications for upcoming CNI maintenance events using the No
 ### Enable Cloudflare Status Maintenance Notification
 
 First, identify the PoP code for your CNI circuit:
-
 1. In the Cloudflare dashboard, go to **Interconnects**.
 
-   <DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
+	<DashButton url="/?to=/:account/magic-networks/connections/cni-tunnels" />
 
 2. Select the CNI you want to enable notifications for.
 3. In the menu that appears, note the Data Center code (for example, `gru-b`).
diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx
index 2cf09f24173e915..a94aa4bae85717a 100644
--- a/src/content/docs/network-interconnect/operational-guidance.mdx
+++ b/src/content/docs/network-interconnect/operational-guidance.mdx
@@ -52,4 +52,4 @@ If no system-wide problems are reported, gather the following information before
 - **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
 - **Physical Layer**: Light levels of the CNI link (if applicable).
 - **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
-- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
+- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
\ No newline at end of file
diff --git a/src/content/docs/network/index.mdx b/src/content/docs/network/index.mdx
index e9f9e837d33f580..e6d3e05e3d5a401 100644
--- a/src/content/docs/network/index.mdx
+++ b/src/content/docs/network/index.mdx
@@ -11,48 +11,38 @@ products:
   - network
 ---
 
-import { Description, Feature, Plan, RelatedProduct } from "~/components";
+import { Description, Feature, Plan, RelatedProduct } from "~/components"
 
-<Description>Manage network settings for your website.</Description>
+<Description>
+Manage network settings for your website.
+</Description>
 
 <Plan type="all" />
 
----
+***
 
 ## Features
 
 <Feature header="IP Geolocation" href="/network/ip-geolocation/">
-	Include the country code of the visitor location with all requests to your
-	website.
+Include the country code of the visitor location with all requests to your website.
 </Feature>
 
 <Feature header="IPv6 Compatibility" href="/network/ipv6-compatibility/">
-	Enable IPv6 support and gateway.
+Enable IPv6 support and gateway.
 </Feature>
 
 <Feature header="WebSockets" href="/network/websockets/">
-	Allow WebSockets connections to your origin server.
+Allow WebSockets connections to your origin server.
 </Feature>
 
----
+***
 
 ## Related products
 
-<RelatedProduct
-	header="China Network"
-	href="/china-network/"
-	product="china-network"
->
-	The Cloudflare China Network is a package of selected Cloudflare’s performance
-	and security products running on data centers located in mainland China and
-	operated by Cloudflare’s partner JD Cloud.
+<RelatedProduct header="China Network" href="/china-network/" product="china-network">
+The Cloudflare China Network is a package of selected Cloudflare’s performance and security products running on data centers located in mainland China and operated by Cloudflare’s partner JD Cloud.
 </RelatedProduct>
 
-<RelatedProduct
-	header="Managed Transforms"
-	href="/rules/transform/managed-transforms/"
-	product="rules"
->
-	Managed Transforms allow you to perform common adjustments to HTTP request and
-	response headers with the click of a button.
+<RelatedProduct header="Managed Transforms" href="/rules/transform/managed-transforms/" product="rules">
+Managed Transforms allow you to perform common adjustments to HTTP request and response headers with the click of a button.
 </RelatedProduct>
diff --git a/src/content/docs/network/websockets.mdx b/src/content/docs/network/websockets.mdx
index dbb08884e375a08..77ff14da6b28963 100644
--- a/src/content/docs/network/websockets.mdx
+++ b/src/content/docs/network/websockets.mdx
@@ -89,3 +89,4 @@ Cloudflare will close a WebSocket connection when no data is transmitted in eith
 ### Session affinity for load-balanced WebSocket origins
 
 If your WebSocket origin is behind a Cloudflare Load Balancer, turn on **Session affinity** to ensure all requests from the same client are routed to the same origin server. Without session affinity, a WebSocket reconnect may land on a different origin that does not have the session state.
+
diff --git a/src/content/docs/notifications/get-started/configure-pagerduty.mdx b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
index a4e84b32aedd7cb..fef6662b17543be 100644
--- a/src/content/docs/notifications/get-started/configure-pagerduty.mdx
+++ b/src/content/docs/notifications/get-started/configure-pagerduty.mdx
@@ -12,7 +12,7 @@ import { DashButton } from "~/components";
 
 :::note
 
-This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/).
+This feature is only available if your account has at least one zone on a Business or higher plan. For more information, refer to our [plans](https://www.cloudflare.com/plans/). 
 :::
 
 Cloudflare’s Notification service supports routing notifications to PagerDuty. By sending notifications to PagerDuty you can leverage the same service definitions and escalation paths that you would for other third-party services that you connect to PagerDuty.
@@ -23,15 +23,14 @@ To use PagerDuty as a connected service, you must [sign up for a PagerDuty accou
 
 :::note
 
-According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner.
+According to PagerDuty, you will need an account with the following permissions to add a connected service: User, Admin, Manager, Global Admin, or Account Owner. 
 :::
 
 ## Connect PagerDuty to a Cloudflare account
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **Connect**.
 4. Log in to your [PagerDuty account](https://www.pagerduty.com/) to connect it to your Cloudflare account.
@@ -49,9 +48,8 @@ Disconnecting PagerDuty will disable any notifications being sent to PagerDuty w
 If other delivery destinations were selected, then those notifications will still be routed as configured.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Go to **Destinations**.
 3. In the **Connected notification services** card, select **View** on the PagerDuty service you want to disconnect.
 4. Select **Disconnect** > **Confirm**.
diff --git a/src/content/docs/notifications/get-started/index.mdx b/src/content/docs/notifications/get-started/index.mdx
index 04bb4821e3116e6..4e0d0a3fba2ffc8 100644
--- a/src/content/docs/notifications/get-started/index.mdx
+++ b/src/content/docs/notifications/get-started/index.mdx
@@ -36,9 +36,8 @@ This guide will help you create, edit, test, or delete notifications using the C
 You can create a notification via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Select **Add**.
 3. On the notification you want to create, choose **Select**.
 4. Name the notification.
@@ -46,7 +45,7 @@ You can create a notification via the Cloudflare dashboard.
 
 :::note
 
-Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks.
+Professional and Business plans will have access to more notifications and PagerDuty. Accounts with a paid service will additionally have access to webhooks. 
 :::
 
 6. (Optional) Specify any additional options for the notification, if required. For example, some notifications require that you select one or more domains or services.
@@ -59,9 +58,8 @@ The browser will navigate back to the list of notifications, where the new notif
 You can edit existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to modify, select **Edit**.
 3. Make your changes as needed and select **Save**.
 
@@ -72,9 +70,8 @@ The browser will navigate back to the list of notifications.
 You can delete or disable existing Notifications via the Cloudflare dashboard.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to disable, select the **Enabled** toggle. To delete it, select **Delete**.
 
 ### Mute a notification
@@ -82,9 +79,8 @@ You can delete or disable existing Notifications via the Cloudflare dashboard.
 You can temporarily mute a notification to stop receiving alerts for a set period of time. Muted notifications create a silence that automatically expires after the specified duration.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. On the notification that you want to mute, select **Mute**.
 3. Select a duration preset (**1h**, **12h**, or **24h**), or set a custom time range using the **Start Time** and **End Time** fields.
 4. Select **Save**.
@@ -99,9 +95,8 @@ While a notification is muted, alerts that would have triggered it are suppresse
 You can view, edit, or delete existing silences from the **Silences** tab.
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
-
-   <DashButton url="/?to=/:account/notifications" />
-
+  
+    <DashButton url="/?to=/:account/notifications" />
 2. Select the **Silences** tab.
 3. To create a new silence, select **Add**. To modify an existing silence, select **Edit**. To remove a silence before it expires, select **Delete**.
 
diff --git a/src/content/docs/notifications/index.mdx b/src/content/docs/notifications/index.mdx
index 829b5519eba15c2..a1d547bdecee617 100644
--- a/src/content/docs/notifications/index.mdx
+++ b/src/content/docs/notifications/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: overview
 title: Notifications
 sidebar:
@@ -8,7 +9,7 @@ products:
 description: Configure alerts for your Cloudflare account.
 ---
 
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
 <Plan type="all" />
 
@@ -28,4 +29,4 @@ The availability of delivery methods like PagerDuty and webhooks in Free or Prof
 
 - PagerDuty is available in zones on a Free/Professional plan if your Cloudflare account has at least one zone in a Business plan (or higher).
 - Webhooks are available in zones on a Free plan if your Cloudflare account has at least one zone in a Professional plan (or higher).
-  :::
+:::
diff --git a/src/content/docs/notifications/notification-available.mdx b/src/content/docs/notifications/notification-available.mdx
index b41697b971f7c3d..6712c3aee831957 100644
--- a/src/content/docs/notifications/notification-available.mdx
+++ b/src/content/docs/notifications/notification-available.mdx
@@ -8,7 +8,7 @@ products:
 description: Browse available notification types by product.
 ---
 
-import { AvailableNotifications } from "~/components";
+import { AvailableNotifications } from "~/components"
 
 Available Notifications depend on your Cloudflare plan. Cloudflare offers a variety of Notifications for our products and services, such as [Billing](/billing/), [Denial of Service protection](/ddos-protection/), [Magic Transit](/magic-transit/), and [SSL/TLS](/ssl/).
 
diff --git a/src/content/docs/notifications/notification-history.mdx b/src/content/docs/notifications/notification-history.mdx
index 4bbc04b274ecd9b..57b80f9b1bd7402 100644
--- a/src/content/docs/notifications/notification-history.mdx
+++ b/src/content/docs/notifications/notification-history.mdx
@@ -32,5 +32,5 @@ Notification History is available on all plans. The amount of history clients ha
 
 :::note
 
-Customers will not be able to access Notification History from before 2021-10-11.
+Customers will not be able to access Notification History from before 2021-10-11. 
 :::
diff --git a/src/content/docs/notifications/reference/index.mdx b/src/content/docs/notifications/reference/index.mdx
index 6d7a07ae02df9e1..38d8d2becb9beec 100644
--- a/src/content/docs/notifications/reference/index.mdx
+++ b/src/content/docs/notifications/reference/index.mdx
@@ -10,7 +10,7 @@ products:
 description: Reference information for Cloudflare Notifications.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Notifications:
 
diff --git a/src/content/docs/notifications/reference/traffic-alerts.mdx b/src/content/docs/notifications/reference/traffic-alerts.mdx
index 42527aee765f7ca..9741d0e2d2dcc30 100644
--- a/src/content/docs/notifications/reference/traffic-alerts.mdx
+++ b/src/content/docs/notifications/reference/traffic-alerts.mdx
@@ -28,7 +28,7 @@ This approach does not work as well for low traffic zones. If there are not many
 
 ### Service-level objective recommendations
 
-SLOs determine the sensitivity of an alert. For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
+SLOs determine the sensitivity of an alert.  For example, if you want to be alerted on all spikes in 5xx errors, you should select high sensitivity. If you want to be alerted on only large spikes, you should select a lower sensitivity.
 
 Your traffic levels impact the accuracy of high sensitivity alerts. High sensitivity alerts are not recommended for zones with low traffic since the Error Rate alert will likely alert on every 5xx error. However, If you have a zone that has very high traffic (hundreds of millions of requests per day), High Sensitivity SLOs are recommended.
 
diff --git a/src/content/docs/pages/configuration/api.mdx b/src/content/docs/pages/configuration/api.mdx
index d813c97fe6c9adf..5f49f4fd6a70543 100644
--- a/src/content/docs/pages/configuration/api.mdx
+++ b/src/content/docs/pages/configuration/api.mdx
@@ -19,7 +19,6 @@ To create an API token:
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
-
 2. Select **Create Token**.
 3. You can go to **Edit Cloudflare Workers** template > **Use template** or go to **Create Custom Token** > **Get started**. If you create a custom token, you will need to make sure to add the **Cloudflare Pages** permission with **Edit** access.
 
diff --git a/src/content/docs/pages/configuration/build-caching.mdx b/src/content/docs/pages/configuration/build-caching.mdx
index 436cc3e60e5c6d3..3cd918887d0b276 100644
--- a/src/content/docs/pages/configuration/build-caching.mdx
+++ b/src/content/docs/pages/configuration/build-caching.mdx
@@ -37,15 +37,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                            |
-| ---------- | --------------------------------------------- |
-| Astro      | `node_modules/.astro`                         |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
-| Eleventy   | `.cache`                                      |
-| Gatsby     | `.cache`, `public`                            |
-| Next.js    | `.next/cache`                                 |
-| Nuxt       | `node_modules/.cache/nuxt`                    |
-| SvelteKit  | `node_modules/.cache/imagetools`              |
+| Framework  | Directories cached                                          |
+| ---------- | ----------------------------------------------------------- |
+| Astro      | `node_modules/.astro`                                       |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
+| Eleventy   | `.cache`                                                    |
+| Gatsby     | `.cache`, `public`                                          |
+| Next.js    | `.next/cache`                                               |
+| Nuxt       | `node_modules/.cache/nuxt`                                  |
+| SvelteKit  | `node_modules/.cache/imagetools`                            |
 
 ### Limits
 
diff --git a/src/content/docs/pages/configuration/build-image.mdx b/src/content/docs/pages/configuration/build-image.mdx
index e4596187251d055..d2c7006afebcc61 100644
--- a/src/content/docs/pages/configuration/build-image.mdx
+++ b/src/content/docs/pages/configuration/build-image.mdx
@@ -88,7 +88,6 @@ To migrate to this new version, configure your Pages project settings in the das
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Deployments** > **All deployments** > and select the latest version.
 
@@ -110,6 +109,7 @@ Cloudflare Pages builds are run in a [gVisor](https://gvisor.dev/docs/) containe
 
 <PagesBuildEnvironment />
 
+
 ## Build Image Policy
 
 ### Build Image Version Deprecation
@@ -131,7 +131,6 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
-
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -141,7 +140,6 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
-
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
 - **Plan for migration** when you receive update notices
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/pages/configuration/build-image/#override-default-versions)
\ No newline at end of file
diff --git a/src/content/docs/pages/configuration/deploy-hooks.mdx b/src/content/docs/pages/configuration/deploy-hooks.mdx
index b40eb6d48f435bb..66418eb9f810990 100644
--- a/src/content/docs/pages/configuration/deploy-hooks.mdx
+++ b/src/content/docs/pages/configuration/deploy-hooks.mdx
@@ -19,7 +19,6 @@ To create a Deploy Hook:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Builds** and select **Add deploy hook** to start configuration.
 
diff --git a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
index 46e064b4a0d8063..377ecb62654d209 100644
--- a/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
+++ b/src/content/docs/pages/framework-guides/deploy-a-vite3-project.mdx
@@ -68,7 +68,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Import from an existing Git repository**.
 3. Select your new GitHub repository.
 4. In the **Set up builds and deployments**, set `npm run build` as the **Build command**, and `dist` as the **Build output directory**.
diff --git a/src/content/docs/pages/functions/api-reference.mdx b/src/content/docs/pages/functions/api-reference.mdx
index 9a521a8c592d30b..e15d8a9a4aa0a15 100644
--- a/src/content/docs/pages/functions/api-reference.mdx
+++ b/src/content/docs/pages/functions/api-reference.mdx
@@ -18,27 +18,35 @@ The following methods can be used to configure your Pages Function.
 The `onRequest` method will be called unless a more specific `onRequestVerb` method is exported. For example, if both `onRequest` and `onRequestGet` are exported, only `onRequestGet` will be called for `GET` requests.
 
 - <code>onRequest(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all requests no matter what the request method is, as long as no specific request verb (like one of the methods below) is exported.
 
 - <code>onRequestGet(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `GET` requests.
 
 - <code>onRequestPost(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `POST` requests.
 
 - <code>onRequestPatch(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `PATCH` requests.
 
 - <code>onRequestPut(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `PUT` requests.
 
 - <code>onRequestDelete(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `DELETE` requests.
 
 - <code>onRequestHead(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `HEAD` requests.
 
 - <code>onRequestOptions(context[EventContext](#eventcontext))</code> Response | Promise\<Response>
+
   - This function will be invoked on all `OPTIONS` requests.
 
 ### `env.ASSETS.fetch()`
diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx
index 4b1016b85d127f3..b6f53b59192f9eb 100644
--- a/src/content/docs/pages/functions/bindings.mdx
+++ b/src/content/docs/pages/functions/bindings.mdx
@@ -14,13 +14,7 @@ products:
   - durable-objects
 ---
 
-import {
-	Render,
-	TabItem,
-	Tabs,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, TabItem, Tabs, WranglerConfig, DashButton } from "~/components";
 
 A [binding](/workers/runtime-apis/bindings/) enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like [KV](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2](/r2/), and [D1](/d1/). You can set bindings for both production and preview environments.
 
@@ -43,7 +37,6 @@ To configure a KV namespace binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **KV namespace**.
 4. Give your binding a name under **Variable name**.
@@ -104,7 +97,6 @@ To configure a Durable Object binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Durable Object**.
 4. Give your binding a name under **Variable name**.
@@ -169,7 +161,6 @@ To configure a R2 bucket binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **R2 bucket**.
 4. Give your binding a name under **Variable name**.
@@ -242,7 +233,6 @@ To configure a D1 database binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add**> **D1 database bindings**.
 4. Give your binding a name under **Variable name**.
@@ -319,13 +309,12 @@ To configure a Vectorize index binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 3. Select your Pages project > **Settings**.
 4. Go to **Bindings** > **Add** > **Vectorize index**.
 5. Give your binding a name under **Variable name**.
 6. Under **Vectorize index**, select your desired Vectorize index.
-7. Redeploy your project for the binding to take effect.
+8. Redeploy your project for the binding to take effect.
 
 ### Use Vectorize index bindings
 
@@ -460,7 +449,6 @@ To configure a Workers AI binding via the Cloudflare dashboard:
 1. Go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings**.
 3. Select your Pages environment > **Bindings** > **Add** > **Workers AI**.
 4. Give your binding a name under **Variable name**.
@@ -534,7 +522,6 @@ To configure a Service binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Service binding**.
 4. Give your binding a name under **Variable name**.
@@ -599,7 +586,6 @@ To configure a queue producer binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Queue**.
 4. Give your binding a name under **Variable name**.
@@ -676,7 +662,6 @@ To configure a Hyperdrive binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Hyperdrive**.
 4. Give your binding a name under **Variable name**.
@@ -750,7 +735,6 @@ To configure an Analytics Engine binding via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Bindings** > **Add** > **Analytics engine**.
 4. Give your binding a name under **Variable name**.
@@ -812,7 +796,6 @@ To configure an environment variable via the Cloudflare dashboard:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add** .
 4. After setting a variable name and value, select **Save**.
@@ -871,7 +854,6 @@ To add secrets to your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Variables and Secrets** > **Add**.
 4. Set a variable name and value.
diff --git a/src/content/docs/pages/functions/examples/ab-testing.mdx b/src/content/docs/pages/functions/examples/ab-testing.mdx
index 125a99e100cd193..96d45b37cd3e0f8 100644
--- a/src/content/docs/pages/functions/examples/ab-testing.mdx
+++ b/src/content/docs/pages/functions/examples/ab-testing.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up an A/B test by controlling what page is served based on cookies.
   This version supports passing the request through to test and control on the
   origin.
diff --git a/src/content/docs/pages/functions/examples/cors-headers.mdx b/src/content/docs/pages/functions/examples/cors-headers.mdx
index 48c58ea881e153c..0011928013bbd10 100644
--- a/src/content/docs/pages/functions/examples/cors-headers.mdx
+++ b/src/content/docs/pages/functions/examples/cors-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: A Pages Functions for appending CORS headers.
 tags:
   - Headers
diff --git a/src/content/docs/pages/functions/examples/index.mdx b/src/content/docs/pages/functions/examples/index.mdx
index a7ae43643a007ce..26f22f52cf8ceca 100644
--- a/src/content/docs/pages/functions/examples/index.mdx
+++ b/src/content/docs/pages/functions/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: Examples
 description: Code examples for common Pages Functions use cases.
diff --git a/src/content/docs/pages/functions/metrics.mdx b/src/content/docs/pages/functions/metrics.mdx
index 802ad2e19dd4a42..12b285087c355a7 100644
--- a/src/content/docs/pages/functions/metrics.mdx
+++ b/src/content/docs/pages/functions/metrics.mdx
@@ -19,7 +19,6 @@ Functions metrics aggregate request data for an individual Pages project. To vie
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. In your Pages project, select **Functions Metrics**.
 
diff --git a/src/content/docs/pages/functions/plugins/community-plugins.mdx b/src/content/docs/pages/functions/plugins/community-plugins.mdx
index 69d5080b51c5b6f..164f24737e7be5c 100644
--- a/src/content/docs/pages/functions/plugins/community-plugins.mdx
+++ b/src/content/docs/pages/functions/plugins/community-plugins.mdx
@@ -17,6 +17,7 @@ The following are some of the community-maintained Pages Plugins. If you have cr
 - [proxyflare-for-pages](https://github.com/flaregun-net/proxyflare-for-pages)
 
   Move traffic around your Cloudflare Pages domain with ease. Proxyflare is a reverse-proxy that enables you to:
+
   - Port forward, redirect, and reroute HTTP and websocket traffic anywhere on the Internet.
   - Mount an entire website on a subpath (for example, `mysite.com/docs`) on your apex domain.
   - Serve static text (like `robots.txt` and other structured metadata) from any endpoint.
diff --git a/src/content/docs/pages/get-started/c3.mdx b/src/content/docs/pages/get-started/c3.mdx
index c88153d094feefa..68c5c783012edad 100644
--- a/src/content/docs/pages/get-started/c3.mdx
+++ b/src/content/docs/pages/get-started/c3.mdx
@@ -10,6 +10,7 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 products:
   - pages
+
 ---
 
 import {
@@ -84,24 +85,30 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
 />
 
 - `DIRECTORY` <Type text="string" /> <MetaInfo text="optional" />
+
   - The directory where the application should be created. The name of the application is taken from the directory name.
 
 - `NESTED ARGS..` <Type text="string[]" /> <MetaInfo text="optional" />
+
   - CLI arguments to pass to eventual third party CLIs C3 might invoke (in the case of full-stack applications).
 
 - `--category` <Type text="string" /> <MetaInfo text="optional" />
+
   - The kind of templates that should be created.
 
   - The possible values for this option are:
+
     - `hello-world`: Hello World example
     - `web-framework`: Framework Starter
     - `demo`: Application Starter
     - `remote-template`: Template from a GitHub repo
 
 - `--type` <Type text="string" /> <MetaInfo text="optional" />
+
   - The type of application that should be created.
 
   - The possible values for this option are:
+
     - `hello-world`: A basic "Hello World" Cloudflare Worker.
     - `hello-world-durable-object`: A [Durable Object](/durable-objects/) and a Worker to communicate with it.
     - `common`: A Cloudflare Worker which implements a common example of routing/proxying functionalities.
@@ -111,9 +118,11 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `pre-existing`: Fetch a Worker initialized from the Cloudflare dashboard.
 
 - `--framework` <Type text="string" /> <MetaInfo text="optional" />
+
   - The type of framework to use to create a web application (when using this option, `--type` is ignored).
 
   - The possible values for this option are:
+
     - `angular`
     - `astro`
     - `docusaurus`
@@ -130,9 +139,11 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     - `vue`
 
 - `--template` <Type text="string" /> <MetaInfo text="optional" />
+
   - Create a new project via an external template hosted in a git repository
 
   - The value for this option may be specified as any of the following:
+
     - `user/repo`
     - `git@github.com:user/repo`
     - `https://github.com/user/repo`
@@ -145,6 +156,7 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the `degit` [docs](https://github.com/Rich-Harris/degit) for more details.
 
     At a minimum, templates must contain the following:
+
     - `package.json`
     - [Wrangler configuration file](/pages/functions/wrangler-configuration/)
     - `src/` containing a worker script referenced from the Wrangler configuration file
@@ -152,40 +164,51 @@ This is the full format of a C3 invocation alongside the possible CLI arguments:
     See the [templates folder](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare/templates) of this repo for more examples.
 
 - `--deploy` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Deploy your application after it has been created.
 
 - `--lang` <Type text="string" /> <MetaInfo text="(default: ts) optional" />
+
   - The programming language of the template.
 
   - The possible values for this option are:
+
     - `ts`
     - `js`
     - `python`
 
 - `--ts` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Use TypeScript in your application. Deprecated. Use `--lang=ts` instead.
 
 - `--git` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Initialize a local git repository for your application.
 
 - `--open` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Open with your browser the deployed application (this option is ignored if the application is not deployed).
 
 - `--existing-script` <Type text="string" /> <MetaInfo text="optional" />
+
   - The name of an existing Cloudflare Workers script to clone locally. When using this option, `--type` is coerced to `pre-existing`.
 
   - When `--existing-script` is specified, `deploy` will be ignored.
 
 - `-y`, `--accept-defaults` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Use all the default C3 options each can also be overridden by specifying it.
 
 - `--auto-update` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
+
   - Automatically uses the latest version of C3.
 
 - `-v`, `--version` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Show version number.
 
 - `-h`, `--help` <Type text="boolean" /> <MetaInfo text="optional" />
+
   - Show a help message.
 
 :::note
diff --git a/src/content/docs/pages/get-started/direct-upload.mdx b/src/content/docs/pages/get-started/direct-upload.mdx
index f1f5228ef2053d0..9f7252898b5ddba 100644
--- a/src/content/docs/pages/get-started/direct-upload.mdx
+++ b/src/content/docs/pages/get-started/direct-upload.mdx
@@ -8,6 +8,7 @@ description: Upload your prebuilt assets to Pages and deploy them via the
   Wrangler CLI or the Cloudflare dashboard.
 products:
   - pages
+
 ---
 
 import { Render, DashButton } from "~/components";
@@ -127,7 +128,6 @@ To deploy with drag and drop:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Get started** > **Drag and drop your files**.
 3. Enter your project name in the provided field and drag and drop your assets.
 4. Select **Deploy site**.
diff --git a/src/content/docs/pages/get-started/git-integration.mdx b/src/content/docs/pages/get-started/git-integration.mdx
index 5ac8218965fb505..3b6cb58789596cb 100644
--- a/src/content/docs/pages/get-started/git-integration.mdx
+++ b/src/content/docs/pages/get-started/git-integration.mdx
@@ -7,6 +7,7 @@ head:
 description: Connect your Git provider to Pages.
 products:
   - pages
+
 ---
 
 import { Details, Render } from "~/components";
diff --git a/src/content/docs/pages/get-started/index.mdx b/src/content/docs/pages/get-started/index.mdx
index e76af4b0b86da8a..328bd28a8396d9c 100644
--- a/src/content/docs/pages/get-started/index.mdx
+++ b/src/content/docs/pages/get-started/index.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 2
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/add-custom-http-headers.mdx b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
index 7dedb62c0645ef1..3402e5e5a66d4e5 100644
--- a/src/content/docs/pages/how-to/add-custom-http-headers.mdx
+++ b/src/content/docs/pages/how-to/add-custom-http-headers.mdx
@@ -5,6 +5,7 @@ description: Customize HTTP headers on Cloudflare Pages using a Workers function
 products:
   - pages
   - workers
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/docs/pages/how-to/build-commands-branches.mdx b/src/content/docs/pages/how-to/build-commands-branches.mdx
index d91423afb902d99..46ab3dfafb2d1a1 100644
--- a/src/content/docs/pages/how-to/build-commands-branches.mdx
+++ b/src/content/docs/pages/how-to/build-commands-branches.mdx
@@ -5,6 +5,7 @@ title: Set build commands per branch
 description: Run different build commands on specific branches in your Cloudflare Pages project.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -45,7 +46,6 @@ To put your changes into effect:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
 4. Update the **Build command** field value to `bash build.sh` and select **Save**.
diff --git a/src/content/docs/pages/how-to/custom-branch-aliases.mdx b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
index 818ca533a5bf852..a50f4c6b38fe0a3 100644
--- a/src/content/docs/pages/how-to/custom-branch-aliases.mdx
+++ b/src/content/docs/pages/how-to/custom-branch-aliases.mdx
@@ -4,6 +4,7 @@ title: Add a custom domain to a branch
 description: Point a custom domain to a specific branch deployment of your Cloudflare Pages project.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -31,7 +32,6 @@ To do this:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Select **Custom domains** > **Setup a custom domain**.
 4. Input the domain you would like to use, such as `staging.example.com`
diff --git a/src/content/docs/pages/how-to/enable-zaraz.mdx b/src/content/docs/pages/how-to/enable-zaraz.mdx
index 20a3092b435873c..a421e08bb06a094 100644
--- a/src/content/docs/pages/how-to/enable-zaraz.mdx
+++ b/src/content/docs/pages/how-to/enable-zaraz.mdx
@@ -4,6 +4,7 @@ title: Enable Zaraz
 description: Set up Zaraz on your Cloudflare Pages project using a custom domain.
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/index.mdx b/src/content/docs/pages/how-to/index.mdx
index 3da369ff33b9913..d2707643d72ee16 100644
--- a/src/content/docs/pages/how-to/index.mdx
+++ b/src/content/docs/pages/how-to/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: How to
 description: Step-by-step guides for common Cloudflare Pages tasks and configurations.
@@ -8,6 +9,7 @@ sidebar:
     hideIndex: true
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/how-to/npm-private-registry.mdx b/src/content/docs/pages/how-to/npm-private-registry.mdx
index a03e59ef22f9dc3..95889b262b4dd84 100644
--- a/src/content/docs/pages/how-to/npm-private-registry.mdx
+++ b/src/content/docs/pages/how-to/npm-private-registry.mdx
@@ -4,6 +4,7 @@ title: Install private packages
 description: Use custom npm registries and private dependencies in your Cloudflare Pages builds.
 products:
   - pages
+
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
index 76183d80849d09f..8780a611c5c465c 100644
--- a/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
+++ b/src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx
@@ -5,6 +5,7 @@ description: Use Cloudflare Tunnel to share locally running Pages projects over
 products:
   - pages
   - tunnel
+
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) runs a lightweight daemon (`cloudflared`) in your infrastructure that establishes outbound connections (Tunnels) between your origin web server and the Cloudflare global network. In practical terms, you can use Cloudflare Tunnel to allow remote access to services running on your local machine. It is an alternative to popular tools like [Ngrok](https://ngrok.com), and provides free, long-running tunnels via the [TryCloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/trycloudflare/) service.
diff --git a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
index 4349352400a31e5..e70f762274f2772 100644
--- a/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
+++ b/src/content/docs/pages/how-to/refactor-a-worker-to-pages-functions.mdx
@@ -6,6 +6,7 @@ sidebar:
   hidden: true
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
index 5526154ba6650bd..1770a4c1621da73 100644
--- a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
+++ b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx
@@ -4,6 +4,7 @@ title: Use Direct Upload with continuous integration
 description: Deploy prebuilt assets to Cloudflare Pages using Wrangler in your CI/CD pipeline.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -28,7 +29,6 @@ To generate an API token:
 1. In the Cloudflare dashboard, go to the **API Tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
-
 2. Select **Create Token**.
 3. Under **Custom Token**, select **Get started**.
 4. Name your API Token in the **Token name** field.
@@ -43,7 +43,7 @@ Now that you have created your API token, you can use it to push your project fr
 
 To find your account ID, go to the **Zone Overview** page in the Cloudflare dashboard.
 
-<DashButton url="/?to=/:account/:zone/" />
+   <DashButton url="/?to=/:account/:zone/" />
 
 Find your account ID in the **API** section on the right-hand side menu.
 
diff --git a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
index 8e750ac70df0a77..2d7fb92626a856d 100644
--- a/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
+++ b/src/content/docs/pages/how-to/use-worker-for-ab-testing-in-pages.mdx
@@ -4,6 +4,7 @@ title: Use Pages Functions for A/B testing
 description: Implement A/B testing in Cloudflare Pages using Pages Functions and cookies.
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -161,5 +162,4 @@ After you have deployed your application, review your middleware Function:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings** > **Functions** > **Configuration**.
diff --git a/src/content/docs/pages/how-to/web-analytics.mdx b/src/content/docs/pages/how-to/web-analytics.mdx
index 80cab7cc7a0ebda..723b5241d55c0e2 100644
--- a/src/content/docs/pages/how-to/web-analytics.mdx
+++ b/src/content/docs/pages/how-to/web-analytics.mdx
@@ -4,6 +4,7 @@ title: Enable Web Analytics
 description: Set up Cloudflare Web Analytics on your Pages project with one-click configuration.
 products:
   - pages
+
 ---
 
 import { Render, DashButton } from "~/components";
@@ -23,7 +24,6 @@ To view the metrics associated with your Pages project:
 1. In the Cloudflare dashboard, go to the **Web Analytics** page.
 
    <DashButton url="/?to=/:account/web-analytics" />
-
 2. Select the analytics associated with your Pages project.
 
 For more details about how to use Web Analytics, refer to the [Web Analytics documentation](/web-analytics/data-metrics/).
diff --git a/src/content/docs/pages/migrations/index.mdx b/src/content/docs/pages/migrations/index.mdx
index 462426a9667eb83..dfac1294f41d646 100644
--- a/src/content/docs/pages/migrations/index.mdx
+++ b/src/content/docs/pages/migrations/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: navigation
 title: Migration guides
 description: Migrate your existing site from another platform to Cloudflare Pages.
@@ -7,6 +8,7 @@ sidebar:
   order: 4
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/index.mdx b/src/content/docs/pages/platform/index.mdx
index 925be7f4266e12b..1a133b13acfc655 100644
--- a/src/content/docs/pages/platform/index.mdx
+++ b/src/content/docs/pages/platform/index.mdx
@@ -8,6 +8,7 @@ sidebar:
     hideIndex: true
 products:
   - pages
+
 ---
 
 import { DirectoryListing } from "~/components";
diff --git a/src/content/docs/pages/platform/known-issues.mdx b/src/content/docs/pages/platform/known-issues.mdx
index 3a0b439ae2c0327..cd105ebacb7fa5e 100644
--- a/src/content/docs/pages/platform/known-issues.mdx
+++ b/src/content/docs/pages/platform/known-issues.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 4
 products:
   - pages
+
 ---
 
 import { DashButton } from "~/components";
@@ -39,6 +40,7 @@ Here are some known bugs and issues with Cloudflare Pages:
 ## Custom Domains
 
 - It is currently not possible to add a custom domain with
+
   - a wildcard, for example, `*.domain.com`.
   - a Worker already routed on that domain.
 
@@ -65,7 +67,6 @@ If you would like to enable [Cloudflare Access](https://www.cloudflare.com/teams
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Settings** > **Enable access policy**.
 4. Select **Manage** on the Access policy created for your preview deployments.
diff --git a/src/content/docs/pages/platform/limits.mdx b/src/content/docs/pages/platform/limits.mdx
index 372373843e2b19a..dd994f7de3cd191 100644
--- a/src/content/docs/pages/platform/limits.mdx
+++ b/src/content/docs/pages/platform/limits.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 1
 products:
   - pages
+
 ---
 
 import { Render } from "~/components";
@@ -17,10 +18,10 @@ Below are limits observed by the Cloudflare Free plan. For more details on remov
 ## Builds
 
 Each time you push new code to your Git repository, Pages will build and deploy your site. Build limits depend on your plan:
-| | Free | Pro | Business |
+|                  | Free              | Pro                 | Business             |
 | ---------------- | ----------------- | ------------------- | -------------------- |
-| Builds | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
-| Builds per month | 500 | 5,000 | 20,000 |
+| Builds           | 1 build at a time | 5 concurrent builds | 20 concurrent builds |
+| Builds per month | 500               | 5,000               | 20,000               |
 
 Builds will timeout after 20 minutes. Concurrent builds are counted per account.
 
diff --git a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
index 499da32c9d96168..880fe3088aafd05 100644
--- a/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
+++ b/src/content/docs/pages/tutorials/add-a-react-form-with-formspree.mdx
@@ -114,7 +114,7 @@ import ContactForm from "./ContactForm";
 Then insert the form into the page as a react component:
 
 ```jsx
-<ContactForm />;
+<ContactForm />
 ```
 
 For example, you can update your `src/App.js` file to add the form:
diff --git a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
index 413e037121afc72..d8a492d5d29124e 100644
--- a/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
+++ b/src/content/docs/pages/tutorials/build-a-blog-using-nuxt-and-sanity.mdx
@@ -365,7 +365,6 @@ After you have pushed your project to GitHub, deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Import an existing Git repository**.
 3. Select the new GitHub repository that you created and select **Begin setup**.
 4. In the **Set up builds and deployments** section, under **Build settings** > **Framework preset**, choose _Nuxt_. Pages will set the correct fields for you automatically.
diff --git a/src/content/docs/pipelines/reference/wrangler-commands.mdx b/src/content/docs/pipelines/reference/wrangler-commands.mdx
index 154b40b6ccb4976..655d91f87e8a583 100644
--- a/src/content/docs/pipelines/reference/wrangler-commands.mdx
+++ b/src/content/docs/pipelines/reference/wrangler-commands.mdx
@@ -10,4 +10,5 @@ products:
 
 import { WranglerNamespace } from "~/components";
 
-<WranglerNamespace namespace="pipelines" />
+<WranglerNamespace namespace="pipelines"/>
+
diff --git a/src/content/docs/pipelines/sinks/manage-sinks.mdx b/src/content/docs/pipelines/sinks/manage-sinks.mdx
index 5f4d14b28b01f0a..7623ca305f5c3e1 100644
--- a/src/content/docs/pipelines/sinks/manage-sinks.mdx
+++ b/src/content/docs/pipelines/sinks/manage-sinks.mdx
@@ -101,4 +101,4 @@ Deleting a sink stops all data writes to that destination.
 ## Limitations
 
 - Sinks cannot be modified after creation. To change sink configuration, you must delete and recreate the sink.
-- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
+- The R2 Data Catalog Sink does not currently support writing to R2 buckets into a different jurisdiction.
\ No newline at end of file
diff --git a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
index da91b792332d4d5..b47c9b02de9b990 100644
--- a/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
+++ b/src/content/docs/pipelines/sql-reference/scalar-functions/string.mdx
@@ -521,6 +521,7 @@ uuid()
 Returns the string which is replaced by another string from the specified position and specified count length.
 For example, `overlay('Txxxxas' placing 'hom' from 2 for 4) → Thomas`
 
+
 ```
 overlay(str PLACING substr FROM pos [FOR count])
 ```
diff --git a/src/content/docs/privacy-gateway/get-started.mdx b/src/content/docs/privacy-gateway/get-started.mdx
index 05973978d5a98cd..41f956ba77f1276 100644
--- a/src/content/docs/privacy-gateway/get-started.mdx
+++ b/src/content/docs/privacy-gateway/get-started.mdx
@@ -14,13 +14,13 @@ Privacy Gateway implementation consists of three main parts:
 2. Client configuration (operated by you).
 3. Connection to a Privacy Gateway Relay Server (operated by Cloudflare).
 
----
+***
 
 ## Before you begin
 
 Privacy Gateway is currently in closed beta. If you are interested, [contact us](https://www.cloudflare.com/lp/privacy-edge/).
 
----
+***
 
 ## Step 1 - Configure your server
 
@@ -34,13 +34,13 @@ Applications can also implement this functionality themselves. Details about [pu
 
 Use the following resources for help with server configuration:
 
-- **Go**:
-  - [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
-  - [Gateway library](https://github.com/chris-wood/ohttp-go)
-- **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
-- **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
+* **Go**:
+  * [Sample gateway server](https://github.com/cloudflare/privacy-gateway-server-go)
+  * [Gateway library](https://github.com/chris-wood/ohttp-go)
+* **Rust**: [Gateway library](https://github.com/martinthomson/ohttp/tree/main/ohttp-server)
+* **JavaScript / TypeScript**: [Gateway library](https://github.com/chris-wood/ohttp-js)
 
----
+***
 
 ## Step 2 - Configure your client
 
@@ -52,21 +52,21 @@ Additionally, app developers need to [configure the client](#resources-1) to fet
 
 Use the following resources for help with client configuration:
 
-- **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
-- **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
-- **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
+* **Objective C**: [Sample application](https://github.com/cloudflare/privacy-gateway-client-demo)
+* **Rust**: [Client library](https://github.com/martinthomson/ohttp/tree/main/ohttp-client)
+* **JavaScript / TypeScript**: [Client library](https://github.com/chris-wood/ohttp-js)
 
----
+***
 
 ## Step 3 - Review your application
 
 After you have configured your client and server, review your application to make sure you are only sending intended data to Cloudflare and the application backend. In particular, application data should not contain anything unique to an end-user, as this would invalidate the benefits that OHTTP provides.
 
-- Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
-- Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
-- Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
+* Applications should scrub identifying user data from requests forwarded through the Privacy Gateway. This includes, for example, names, email addresses, phone numbers, etc.
+* Applications should encourage users to disable crash reporting when using Privacy Gateway. Crash reports can contain sensitive user information and data, including email addresses.
+* Where possible, application data should be encrypted on the client device with a key known only to the client. For example, iOS generally has good support for [client-side encryption (and key synchronization via the KeyChain)](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys). Android likely has similar features available.
 
----
+***
 
 ## Step 4 - Relay requests through Cloudflare
 
diff --git a/src/content/docs/privacy-gateway/reference/index.mdx b/src/content/docs/privacy-gateway/reference/index.mdx
index bdcb0f1f7729beb..50d23832e8505f7 100644
--- a/src/content/docs/privacy-gateway/reference/index.mdx
+++ b/src/content/docs/privacy-gateway/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - privacy-gateway
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/privacy-gateway/reference/legal.mdx b/src/content/docs/privacy-gateway/reference/legal.mdx
index 8f68db4684d0d76..22928aac224e0f6 100644
--- a/src/content/docs/privacy-gateway/reference/legal.mdx
+++ b/src/content/docs/privacy-gateway/reference/legal.mdx
@@ -24,5 +24,5 @@ Cloudflare retains the Privacy Gateway Logs information for the most recent quar
 
 ## What Privacy Gateway customers see
 
-- The application content of requests.
-- The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
+* The application content of requests.
+* The IP address and associated metadata of the Cloudflare Privacy Gateway server the request came from.
diff --git a/src/content/docs/privacy-gateway/reference/metrics.mdx b/src/content/docs/privacy-gateway/reference/metrics.mdx
index 6a0751366ca483b..f40cb4d6ffbc6ee 100644
--- a/src/content/docs/privacy-gateway/reference/metrics.mdx
+++ b/src/content/docs/privacy-gateway/reference/metrics.mdx
@@ -10,8 +10,8 @@ products:
 
 Privacy Gateway now supports enhanced monitoring through our GraphQL API, providing detailed insights into your gateway traffic and performance. To access these metrics, ensure you have:
 
-- A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
-- An API token with Analytics Read permissions.
+* A relay gateway proxy implementation where Cloudflare acts as the oblivious relay party.
+* An API token with Analytics Read permissions.
   We offer two GraphQL nodes to retrieve metrics: `ohttpMetricsAdaptive` and `ohttpMetricsAdaptiveGroups`. The first node provides comprehensive request data, while the second facilitates grouped analytics.
 
 ## ohttpMetricsAdaptive
@@ -20,27 +20,33 @@ The `ohttpMetricsAdaptive` node is designed for detailed insights into individua
 
 ### Key Arguments
 
-- `filter` required
-  - Apply filters to narrow down your data set. `accountTag` is a required filter.
-- `limit` optional
-  - Specify the maximum number of records to return.
-- `orderBy` optional
-  - Choose how to sort your data, with options for various dimensions and metrics.
+
+
+* `filter` required
+  * Apply filters to narrow down your data set. `accountTag` is a required filter.
+* `limit`  optional
+  * Specify the maximum number of records to return.
+* `orderBy` optional
+  * Choose how to sort your data, with options for various dimensions and metrics.
+
 
 ### Available Fields
 
-- `bytesToClient` int optional
-  - The number of bytes returned to the client.
-- `bytesToGateway` int optional
-  - Total bytes received from the client.
-- `colo` string optional
-  - Airport code of the Cloudflare data center that served the request.
-- `datetime` Time optional
-  - The date and time when the event was recorded.
-- `gatewayStatusCode` int optional
-  - Status code returned by the gateway.
-- `relayStatusCode` int optional
-  - Status code returned by the relay.
+
+
+* `bytesToClient` int optional
+  * The number of bytes returned to the client.
+* `bytesToGateway` int optional
+  * Total bytes received from the client.
+* `colo` string optional
+  * Airport code of the Cloudflare data center that served the request.
+* `datetime` Time optional
+  * The date and time when the event was recorded.
+* `gatewayStatusCode` int optional
+  * Status code returned by the gateway.
+* `relayStatusCode` int optional
+  * Status code returned by the relay.
+
 
 This node is useful for a granular view of traffic, helping you identify patterns, performance issues, or anomalies in your data flow.
 
@@ -50,56 +56,66 @@ The `ohttpMetricsAdaptiveGroups` node allows for aggregated analysis of OHTTP re
 
 ### Key Arguments
 
-- `filter` required
-  - Apply filters to narrow down your data set. `accountTag` is a required filter.
-- `limit` optional
-  - Specify the maximum number of records to return.
-- `orderBy` optional
-  - Choose how to sort your data, with options for various dimensions and metrics.
+
+
+* `filter` required
+  * Apply filters to narrow down your data set. `accountTag` is a required filter.
+* `limit`  optional
+  * Specify the maximum number of records to return.
+* `orderBy` optional
+  * Choose how to sort your data, with options for various dimensions and metrics.
+
 
 ### Available Fields
 
-- `count` int optional
-  - The number of records that meet the criteria.
-- `dimensions` optional
-  - Specifies the grouping dimensions for your data.
-- `sum` optional
-  - Aggregated totals for various metrics, per dimension.
+
+
+* `count` int optional
+  * The number of records that meet the criteria.
+* `dimensions` optional
+  * Specifies the grouping dimensions for your data.
+* `sum` optional
+  * Aggregated totals for various metrics, per dimension.
+
 
 **Dimensions**
 
 You can group your metrics by various dimensions to get a more segmented view of your data:
 
-- `colo` string optional
-  - The airport code of the Cloudflare data center.
-- `date` Date optional
-  - The date of OHTTP request metrics.
-- `datetimeFifteenMinutes` Time optional
-  - Timestamp truncated to fifteen minutes.
-- `datetimeFiveMinutes` Time optional
-  - Timestamp truncated to five minutes.
-- `datetimeHour` Time optional
-  - Timestamp truncated to the hour.
-- `datetimeMinute` Time optional
-  - Timestamp truncated to the minute.
-- `endpoint` string optional
-  - The appId that generated traffic.
-- `gatewayStatusCode` int optional
-  - Status code returned by the gateway.
-- `relayStatusCode` int optional
-  - Status code returned by the relay.
+
+* `colo` string optional
+  * The airport code of the Cloudflare data center.
+* `date` Date optional
+  * The date of OHTTP request metrics.
+* `datetimeFifteenMinutes` Time optional
+  * Timestamp truncated to fifteen minutes.
+* `datetimeFiveMinutes` Time optional
+  * Timestamp truncated to five minutes.
+* `datetimeHour` Time optional
+  * Timestamp truncated to the hour.
+* `datetimeMinute` Time optional
+  * Timestamp truncated to the minute.
+* `endpoint` string optional
+  * The appId that generated traffic.
+* `gatewayStatusCode` int optional
+  * Status code returned by the gateway.
+* `relayStatusCode` int optional
+  * Status code returned by the relay.
+
 
 **Sum Fields**
 
 Sum fields offer a cumulative view of various metrics over your selected time period:
 
-- `bytesToClient` int optional
-  - Total bytes sent from the gateway to the client.
-- `bytesToGateway` int optional
-  - Total bytes from the client to the gateway.
-- `clientRequestErrors` int optional
-  - Total number of client request errors.
-- `gatewayResponseErrors` int optional
-  - Total number of gateway response errors.
+
+* `bytesToClient` int optional
+  * Total bytes sent from the gateway to the client.
+* `bytesToGateway` int optional
+  * Total bytes from the client to the gateway.
+* `clientRequestErrors` int optional
+  * Total number of client request errors.
+* `gatewayResponseErrors` int optional
+  * Total number of gateway response errors.
+
 
 Utilize the ohttpMetricsAdaptiveGroups node to gain comprehensive, aggregated insights into your traffic patterns, helping you optimize performance and user experience.
diff --git a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
index e319b9824e7ef2c..f6f435416d2e986 100644
--- a/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
+++ b/src/content/docs/privacy-gateway/reference/product-compatibility.mdx
@@ -12,6 +12,6 @@ When [using Privacy Gateway](/privacy-gateway/get-started/), the majority of Clo
 
 However, the following products are not compatible:
 
-- [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
-- [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
-- [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
+* [API Shield](/api-shield/): [Schema Validation](/api-shield/security/schema-validation/) and [API discovery](/api-shield/security/api-discovery/) are not possible since Cloudflare cannot see the request URLs.
+* [Cache](/cache/): Caching of application content is no longer possible since each between client and gateway is end-to-end encrypted.
+* [WAF](/waf/): Rules implemented based on request content are not supported since Cloudflare cannot see the request or response content.
diff --git a/src/content/docs/privacy-proxy/concepts/authentication.mdx b/src/content/docs/privacy-proxy/concepts/authentication.mdx
index 344ac01c3d65a39..5adead0bc45a818 100644
--- a/src/content/docs/privacy-proxy/concepts/authentication.mdx
+++ b/src/content/docs/privacy-proxy/concepts/authentication.mdx
@@ -14,11 +14,11 @@ Privacy Proxy requires clients to authenticate before proxying traffic. This pag
 
 Privacy Proxy supports three authentication methods:
 
-| Method               | Use case                  | Privacy level |
-| -------------------- | ------------------------- | ------------- |
-| Pre-shared key (PSK) | Proof of concept, testing | Lower         |
-| Privacy Pass tokens  | Client to server          | High          |
-| mTLS                 | Server to server          | Higher        |
+| Method | Use case | Privacy level |
+| -------- | ---------- | --------------- |
+| Pre-shared key (PSK) | Proof of concept, testing | Lower |
+| Privacy Pass tokens | Client to server | High |
+| mTLS | Server to server | Higher |
 
 ---
 
@@ -166,7 +166,7 @@ Proxy A (which you operate) authenticates users. Common methods include:
 - Privacy Pass tokens issued by your infrastructure
 - Client certificates (mTLS)
 
-### Proxy A to Proxy B
+### Proxy A to Proxy B 
 
 Proxy B authenticates itself to Proxy A using TLS. Depending on your configuration, this can use:
 
diff --git a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
index dfe5168ada7b9a2..72190396733d8b8 100644
--- a/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
+++ b/src/content/docs/privacy-proxy/concepts/deployment-models.mdx
@@ -65,12 +65,12 @@ In a double-hop deployment, you operate the first proxy (Proxy A), and Cloudflar
 
 The double-hop architecture ensures:
 
-| Information        | Proxy A (you) | Proxy B (Cloudflare) |
-| ------------------ | ------------- | -------------------- |
-| Client IP address  | Yes           | No                   |
-| User account       | Yes           | No                   |
-| Destination server | Encrypted     | Yes                  |
-| Request content    | Encrypted     | Encrypted            |
+| Information | Proxy A (you) | Proxy B (Cloudflare) |
+| ------------- | --------------- | ---------------------- |
+| Client IP address | Yes | No |
+| User account | Yes | No |
+| Destination server | Encrypted | Yes |
+| Request content | Encrypted | Encrypted |
 
 Proxy A knows who the user is but cannot see where they are going (the destination is encrypted). Proxy B knows the destination but not who is making the request. Neither party has the complete picture.
 
@@ -90,13 +90,13 @@ Double-hop deployment works well when:
 
 ## Comparison
 
-| Aspect                 | Single-hop                        | Double-hop                 |
-| ---------------------- | --------------------------------- | -------------------------- |
-| Infrastructure         | Cloudflare only                   | You + Cloudflare           |
-| Privacy separation     | Proxy sees identity + destination | Split across two parties   |
-| Operational complexity | Lower                             | Higher                     |
-| Authentication         | Cloudflare-managed                | You manage first-hop auth  |
-| Use case               | Browser VPNs, simple privacy      | Maximum privacy separation |
+| Aspect | Single-hop | Double-hop |
+| -------- | ------------ | ------------ |
+| Infrastructure | Cloudflare only | You + Cloudflare |
+| Privacy separation | Proxy sees identity + destination | Split across two parties |
+| Operational complexity | Lower | Higher |
+| Authentication | Cloudflare-managed | You manage first-hop auth |
+| Use case | Browser VPNs, simple privacy | Maximum privacy separation |
 
 ---
 
diff --git a/src/content/docs/privacy-proxy/concepts/geolocation.mdx b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
index 2c60dc4cbde92c0..987c5e96e5514ab 100644
--- a/src/content/docs/privacy-proxy/concepts/geolocation.mdx
+++ b/src/content/docs/privacy-proxy/concepts/geolocation.mdx
@@ -30,12 +30,12 @@ Privacy Proxy uses geohashes to preserve location without revealing precise coor
 A [geohash](https://en.wikipedia.org/wiki/Geohash) is a compact representation of latitude and longitude. Geohashes use a hierarchical encoding where longer strings represent more precise locations:
 
 | Geohash length | Approximate area |
-| -------------- | ---------------- |
-| 1 character    | ~5,000 km        |
-| 2 characters   | ~1,250 km        |
-| 3 characters   | ~150 km          |
-| 4 characters   | ~40 km           |
-| 5 characters   | ~5 km            |
+| ---------------- | ------------------ |
+| 1 character | ~5,000 km |
+| 2 characters | ~1,250 km |
+| 3 characters | ~150 km |
+| 4 characters | ~40 km |
+| 5 characters | ~5 km |
 
 Privacy Proxy uses reduced-precision geohashes (typically four to five characters) to locate users to a city or region without pinpointing their exact location.
 
diff --git a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
index 6d1b3146f38fc82..3c4634922f9757c 100644
--- a/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
+++ b/src/content/docs/privacy-proxy/concepts/how-it-works.mdx
@@ -35,14 +35,15 @@ Privacy Proxy uses the MASQUE protocol suite to create encrypted tunnels between
 
 Throughout this process, the proxy learns the destination but not the content. The destination learns the egress IP address but not the client's real IP.
 
+
 ## MASQUE protocols
 
 [MASQUE](https://datatracker.ietf.org/wg/masque/about/) (Multiplexed Application Substrate over QUIC Encryption) defines methods for proxying traffic over HTTP. Privacy Proxy supports two MASQUE methods:
 
-| Method       | Transport | Use case                                   |
-| ------------ | --------- | ------------------------------------------ |
-| HTTP CONNECT | TCP       | Traditional HTTPS traffic                  |
-| CONNECT-UDP  | UDP       | QUIC-based traffic, real-time applications |
+| Method | Transport | Use case |
+| -------- | ----------- | ---------- |
+| HTTP CONNECT | TCP | Traditional HTTPS traffic |
+| CONNECT-UDP | UDP | QUIC-based traffic, real-time applications |
 
 Both methods create encrypted tunnels where the proxy forwards traffic without inspecting the content. The proxy sees only the destination hostname and port, not the actual requests, paths, or data exchanged.
 
@@ -54,11 +55,11 @@ For a technical deep dive into how these protocols work, refer to our [blog post
 
 Privacy Proxy creates a privacy boundary between user identity and user activity:
 
-| Information                         | Who knows it                                                  |
-| ----------------------------------- | ------------------------------------------------------------- |
+| Information | Who knows it |
+| ------------- | -------------- |
 | User identity (IP address, account) | Authentication service, first-hop proxy (if using double-hop) |
-| Destination server                  | Privacy Proxy, destination server                             |
-| Request content                     | Client, destination server only                               |
+| Destination server | Privacy Proxy, destination server |
+| Request content | Client, destination server only |
 
 The proxy authenticates users to verify they have permission to use the service, but authentication happens separately from proxying. Once authenticated, the proxy forwards traffic without linking individual requests to specific users.
 
diff --git a/src/content/docs/privacy-proxy/get-started.mdx b/src/content/docs/privacy-proxy/get-started.mdx
index 951b12a8ad7876e..f07aa967b04f5d0 100644
--- a/src/content/docs/privacy-proxy/get-started.mdx
+++ b/src/content/docs/privacy-proxy/get-started.mdx
@@ -37,7 +37,7 @@ curl -v \
   https://example.com
 ```
 
-### Use Chaussette
+### Use Chaussette 
 
 [Chaussette](/privacy-proxy/reference/client-libraries/#chaussette) is a local SOCKS5 proxy that handles authentication and forwards requests to Privacy Proxy.
 
diff --git a/src/content/docs/privacy-proxy/reference/http-headers.mdx b/src/content/docs/privacy-proxy/reference/http-headers.mdx
index da3750df07b72b9..39788fd3a51a37b 100644
--- a/src/content/docs/privacy-proxy/reference/http-headers.mdx
+++ b/src/content/docs/privacy-proxy/reference/http-headers.mdx
@@ -30,10 +30,10 @@ Privacy Pass token format:
 Proxy-Authorization: PrivateToken token=<base64-encoded-token>
 ```
 
-| Parameter                | Description                               |
-| ------------------------ | ----------------------------------------- |
-| `<key>`                  | The pre-shared key provided by Cloudflare |
-| `<base64-encoded-token>` | A base64-encoded Privacy Pass token       |
+| Parameter | Description |
+| ----------- | ------------- |
+| `<key>` | The pre-shared key provided by Cloudflare |
+| `<base64-encoded-token>` | A base64-encoded Privacy Pass token |
 
 ### GraphQL Analytics API request headers
 
@@ -47,10 +47,10 @@ Specifies the client's geographic location for egress IP selection. Optional but
 sec-ch-geohash: <geohash>-<country_code>
 ```
 
-| Parameter        | Description                                                                          |
-| ---------------- | ------------------------------------------------------------------------------------ |
-| `<geohash>`      | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
-| `<country_code>` | ISO 3166-1 alpha-2 country code                                                      |
+| Parameter | Description |
+| ----------- | ------------- |
+| `<geohash>` | A [geohash](https://en.wikipedia.org/wiki/Geohash) string (typically 4-8 characters) |
+| `<country_code>` | ISO 3166-1 alpha-2 country code |
 
 ```http title="Example"
 sec-ch-geohash: u4pruydqqvj-GB
@@ -72,8 +72,8 @@ Provides timing information about proxy processing. This is part of the [OpenTel
 Server-Timing: proxy;dur=<milliseconds>
 ```
 
-| Parameter        | Description                                             |
-| ---------------- | ------------------------------------------------------- |
+| Parameter | Description |
+| ----------- | ------------- |
 | `<milliseconds>` | Processing time in milliseconds introduced by the proxy |
 
 ```http title="Example"
@@ -99,9 +99,9 @@ sec-ch-geohash: 9q8yy-US
 
 The proxy responds with a status code indicating success or failure:
 
-| Status                    | Meaning                          |
-| ------------------------- | -------------------------------- |
-| `200 OK`                  | Tunnel established successfully  |
-| `403 Forbidden`           | Authentication failed            |
-| `502 Bad Gateway`         | Could not connect to destination |
-| `503 Service Unavailable` | Proxy temporarily unavailable    |
+| Status | Meaning |
+| -------- | --------- |
+| `200 OK` | Tunnel established successfully |
+| `403 Forbidden` | Authentication failed |
+| `502 Bad Gateway` | Could not connect to destination |
+| `503 Service Unavailable` | Proxy temporarily unavailable |
diff --git a/src/content/docs/privacy-proxy/reference/proxy-status.mdx b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
index 3cd177c2306ccca..8a0a873a9b6ca6f 100644
--- a/src/content/docs/privacy-proxy/reference/proxy-status.mdx
+++ b/src/content/docs/privacy-proxy/reference/proxy-status.mdx
@@ -16,29 +16,29 @@ The `proxyStatus` dimension provides proxy-level error classification. This fiel
 
 ## `proxyStatus` values
 
-| Value                       | Description                                                                                          |
-| --------------------------- | ---------------------------------------------------------------------------------------------------- |
-| `dns_error`                 | The proxy encountered a DNS error when resolving the next hop hostname.                              |
-| `dns_timeout`               | The proxy timed out while resolving the next hop hostname.                                           |
-| `destination_not_found`     | The proxy cannot determine the appropriate next hop for this request.                                |
-| `destination_unavailable`   | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
-| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address.                          |
-| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address.                                            |
-| `connection_refused`        | The proxy's connection to the next hop was refused.                                                  |
-| `connection_terminated`     | The proxy's connection to the next hop was closed before any response was received.                  |
-| `connection_timeout`        | The proxy's attempt to open a connection to the next hop timed out.                                  |
-| `connection_read_timeout`   | The proxy was expecting data on a connection but received none within the configured time limit.     |
-| `connection_write_timeout`  | The proxy was attempting to write data to a connection but was unable to.                            |
-| `connection_limit_reached`  | The proxy's configured connection limit to the next hop has been exceeded.                           |
-| `source_addr_in_use`        | The proxy cannot assign a source address when connecting to the next hop.                            |
-| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure).           |
-| `tls_protocol_error`        | The proxy encountered a TLS error when communicating with the next hop.                              |
-| `tls_certificate_error`     | The proxy encountered an error verifying the certificate presented by the next hop.                  |
-| `http_request_error`        | The proxy is generating a client (4xx) response on the origin's behalf.                              |
-| `http_upgrade_failed`       | The HTTP Upgrade between the proxy and the next hop failed.                                          |
-| `http_request_denied`       | The proxy rejected the HTTP request based on its configuration or policy.                            |
-| `proxy_internal_error`      | The proxy encountered an internal error unrelated to the origin.                                     |
-| `proxy_loop_detected`       | The proxy tried to forward the request to itself.                                                    |
-| `http_protocol_error`       | The proxy encountered an HTTP protocol error when communicating with the next hop.                   |
-| `http_response_incomplete`  | The proxy received an incomplete response from the next hop.                                         |
-| `rate_limited`              | The client has reached the maximum number of connections per second to a single origin.              |
+| Value | Description |
+| --- | --- |
+| `dns_error` | The proxy encountered a DNS error when resolving the next hop hostname. |
+| `dns_timeout` | The proxy timed out while resolving the next hop hostname. |
+| `destination_not_found` | The proxy cannot determine the appropriate next hop for this request. |
+| `destination_unavailable` | The proxy considers the next hop unavailable (for example, recent failures or health check is down). |
+| `destination_ip_prohibited` | The proxy is configured to prohibit connections to the next hop IP address. |
+| `destination_ip_unroutable` | The proxy cannot find a route to the next hop IP address. |
+| `connection_refused` | The proxy's connection to the next hop was refused. |
+| `connection_terminated` | The proxy's connection to the next hop was closed before any response was received. |
+| `connection_timeout` | The proxy's attempt to open a connection to the next hop timed out. |
+| `connection_read_timeout` | The proxy was expecting data on a connection but received none within the configured time limit. |
+| `connection_write_timeout` | The proxy was attempting to write data to a connection but was unable to. |
+| `connection_limit_reached` | The proxy's configured connection limit to the next hop has been exceeded. |
+| `source_addr_in_use` | The proxy cannot assign a source address when connecting to the next hop. |
+| `source_addr_not_available` | The proxy cannot assign a source address (bind failure or source host resolution failure). |
+| `tls_protocol_error` | The proxy encountered a TLS error when communicating with the next hop. |
+| `tls_certificate_error` | The proxy encountered an error verifying the certificate presented by the next hop. |
+| `http_request_error` | The proxy is generating a client (4xx) response on the origin's behalf. |
+| `http_upgrade_failed` | The HTTP Upgrade between the proxy and the next hop failed. |
+| `http_request_denied` | The proxy rejected the HTTP request based on its configuration or policy. |
+| `proxy_internal_error` | The proxy encountered an internal error unrelated to the origin. |
+| `proxy_loop_detected` | The proxy tried to forward the request to itself. |
+| `http_protocol_error` | The proxy encountered an HTTP protocol error when communicating with the next hop. |
+| `http_response_incomplete` | The proxy received an incomplete response from the next hop. |
+| `rate_limited` | The client has reached the maximum number of connections per second to a single origin. |
diff --git a/src/content/docs/pulumi/tutorial/index.mdx b/src/content/docs/pulumi/tutorial/index.mdx
index 2d5a00e48f838d0..a221bc981254072 100644
--- a/src/content/docs/pulumi/tutorial/index.mdx
+++ b/src/content/docs/pulumi/tutorial/index.mdx
@@ -12,16 +12,19 @@ products:
 Before you begin, make sure you [install Pulumi](/pulumi/installing/).
 
 1. [Add a Site](/pulumi/tutorial/add-site/)
+
    - Bring your existing site under Cloudflare with Pulumi IaC.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Zone and DNS records.
 
 2. [Manage secrets](/pulumi/tutorial/manage-secrets/)
+
    - Develop Workers securely with Pulumi ESC and Wrangler.
    - Introduction to the ESC CLI and the Wrangler CLI.
    - Manage Cloudflare credentials, Worker secrets, and `.dev.vars`.
 
 3. [Deploy a Worker](/pulumi/tutorial/hello-world/)
+
    - Brief introduction to deploying a Cloudflare Workers application with Pulumi.
    - Introduction of `pulumi new`, `up`, and `destroy`.
    - Cloudflare resources defined: Worker script, Worker route, and DNS record.
diff --git a/src/content/docs/queues/configuration/configure-queues.mdx b/src/content/docs/queues/configuration/configure-queues.mdx
index cec7b05be692f5a..67aaf22fcf32e57 100644
--- a/src/content/docs/queues/configuration/configure-queues.mdx
+++ b/src/content/docs/queues/configuration/configure-queues.mdx
@@ -15,33 +15,35 @@ import { WranglerConfig, Type } from "~/components";
 
 Cloudflare Queues can be configured using [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Cloudflare's Developer Platform, which includes [Workers](/workers/), [R2](/r2/), and other developer products.
 
+
 Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
 
 Use the options below to configure your queue.
 
 :::note
 
+
 Below are options for queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
 
+
 :::
 
 ## Queue configuration
-
 The following queue level settings can be configured using Wrangler:
 
 ```sh
 npx wrangler queues update <QUEUE-NAME> --delivery-delay-secs 60 --message-retention-period-secs 3000
 ```
 
-- `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
-  - How long a published message is delayed for, before it is delivered to consumers.
-  - Must be between 0 and 86400 (24 hours).
-  - Defaults to 0.
+* `--delivery-delay-secs` <Type text="number" /> <Type text="optional" />
+	* How long a published message is delayed for, before it is delivered to consumers.
+	* Must be between 0 and 86400 (24 hours).
+	* Defaults to 0.
 
-- `--message-retention-period-secs` <Type text="number" /> <Type text="optional" />
-  - How long messages are retained on the Queue.
-  - Defaults to 345600 (4 days).
-  - Must be between 60 and 1209600 (14 days)
+* `--message-retention-period-secs`  <Type text="number" /> <Type text="optional" />
+	* How long messages are retained on the Queue.
+	* Defaults to 345600 (4 days).
+	* Must be between 60 and 1209600 (14 days)
 
 ## Producer Worker configuration
 
@@ -66,16 +68,24 @@ To produce to a queue, set up a binding in your Wrangler file. These options sho
 
 </WranglerConfig>
 
-- <code>queue</code> <Type text="string" />
-  - The name of the queue.
 
-- <code>binding</code> <Type text="string" />
-  - The name of the binding, which is a JavaScript variable.
+
+* <code>queue</code> <Type text="string" />
+
+  * The name of the queue.
+
+* <code>binding</code> <Type text="string" />
+
+  * The name of the binding, which is a JavaScript variable.
+
+
 
 ## Consumer Worker Configuration
 
 To consume messages from one or more queues, set up a binding in your Wrangler file. These options should be used when a Worker wants to receive messages from a queue.
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -98,29 +108,39 @@ To consume messages from one or more queues, set up a binding in your Wrangler f
 
 Refer to [Limits](/queues/platform/limits) to review the maximum values for each of these options.
 
-- <code>queue</code> <Type text="string" />
-  - The name of the queue.
 
-- <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of messages allowed in each batch.
-  - Defaults to `10` messages.
 
-- <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of seconds to wait until a batch is full.
-  - Defaults to `5` seconds.
+* <code>queue</code> <Type text="string" />
+
+  * The name of the queue.
+
+* <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of messages allowed in each batch.
+  * Defaults to `10` messages.
+
+* <code>max\_batch\_timeout</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of seconds to wait until a batch is full.
+  * Defaults to `5` seconds.
+
+* <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
+
+  * The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
+  * Defaults to `3` retries.
+
+* <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
+
+  * The name of another queue to send a message if it fails processing at least `max_retries` times.
+  * If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
+  * If there is no queue with the specified name, it will be created automatically.
+
+* <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
 
-- <code>max\_retries</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of retries for a message, if it fails or [`retryAll()`](/queues/configuration/javascript-apis/#messagebatch) is invoked.
-  - Defaults to `3` retries.
+  * The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
+  * Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
-- <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
-  - The name of another queue to send a message if it fails processing at least `max_retries` times.
-  - If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
-  - If there is no queue with the specified name, it will be created automatically.
 
-- <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />
-  - The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
-  - Refer to [Consumer concurrency](/queues/configuration/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
 
 ## Pull-based
 
diff --git a/src/content/docs/queues/configuration/consumer-concurrency.mdx b/src/content/docs/queues/configuration/consumer-concurrency.mdx
index 503b8d2fdba5fa2..072aa3381bd5001 100644
--- a/src/content/docs/queues/configuration/consumer-concurrency.mdx
+++ b/src/content/docs/queues/configuration/consumer-concurrency.mdx
@@ -71,7 +71,7 @@ To configure the concurrency settings for your consumer Worker from the dashboar
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select your queue > **Settings**.
 3. Select **Edit Consumer** under Consumer details.
diff --git a/src/content/docs/queues/configuration/index.mdx b/src/content/docs/queues/configuration/index.mdx
index bc7e0d0237bb4c5..fb230019e4a5916 100644
--- a/src/content/docs/queues/configuration/index.mdx
+++ b/src/content/docs/queues/configuration/index.mdx
@@ -8,6 +8,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/configuration/javascript-apis.mdx b/src/content/docs/queues/configuration/javascript-apis.mdx
index a948c75c6c39862..9a34dca675084e9 100644
--- a/src/content/docs/queues/configuration/javascript-apis.mdx
+++ b/src/content/docs/queues/configuration/javascript-apis.mdx
@@ -94,27 +94,30 @@ A binding that allows a producer to send messages to a Queue.
 
 ```ts
 interface Queue<Body = unknown> {
-	send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
-	sendBatch(
-		messages: Iterable<MessageSendRequest<Body>>,
-		options?: QueueSendBatchOptions,
-	): Promise<QueueSendResult>;
-	metrics(): Promise<QueueMetrics>;
+  send(body: Body, options?: QueueSendOptions): Promise<QueueSendResult>;
+  sendBatch(messages: Iterable<MessageSendRequest<Body>>, options?: QueueSendBatchOptions): Promise<QueueSendResult>;
+  metrics(): Promise<QueueMetrics>;
 }
 ```
 
-- `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
-  - Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
-  - When the promise resolves, the message is confirmed to be written to disk.
-  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
 
-- `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
-  - Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
-  - The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
-  - When the promise resolves, the messages are confirmed to be written to disk.
 
-- `metrics()` <Type text="Promise<QueueMetrics>" />
-  - Returns realtime [QueueMetrics](#queuemetrics) for the queue.
+* `send(body: unknown, options?: {contentType?: QueuesContentType })` <Type text="Promise<QueueSendResult>" />
+
+  * Sends a message to the Queue. The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+  * When the promise resolves, the message is confirmed to be written to disk.
+  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+
+* `sendBatch(messages: Iterable<MessageSendRequest<unknown>>, options?: QueueSendBatchOptions)` <Type text="Promise<QueueSendBatchResult>" />
+
+  * Sends a batch of messages to the Queue. Each item in the provided [Iterable](https://www.typescriptlang.org/docs/handbook/iterators-and-generators.html) must be supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types). A batch can contain up to 100 messages, though items are limited to 128 KB each, and the total size of the array cannot exceed 256 KB.
+  * The optional `options` parameter can be used to apply settings (such as `delaySeconds`) to all messages in the batch. See [QueueSendBatchOptions](#queuesendbatchoptions).
+  * When the promise resolves, the messages are confirmed to be written to disk.
+
+* `metrics()` <Type text="Promise<QueueMetrics>" />
+
+  * Returns realtime [QueueMetrics](#queuemetrics) for the queue.
+
 
 ### `MessageSendRequest`
 
@@ -122,44 +125,54 @@ A wrapper type used for sending message batches.
 
 ```ts
 interface MessageSendRequest<Body = unknown> {
-	body: Body;
-	contentType?: QueueContentType;
-	delaySeconds?: number;
+  body: Body;
+  contentType?: QueueContentType;
+  delaySeconds?: number;
 }
 ```
 
-- <code>body</code> <Type text="unknown" />
-  - The body of the message.
-  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
 
-- <code>contentType</code> <Type text="QueueContentType" />
-  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  - See [QueuesContentType](#queuescontenttype) for possible values.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be an integer between 0 and 86400 (24 hours).
+* <code>body</code> <Type text="unknown" />
+
+  * The body of the message.
+  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+
+* <code>contentType</code> <Type text="QueueContentType" />
+
+  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  * See [QueuesContentType](#queuescontenttype) for possible values.
+
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be an integer between 0 and 86400 (24 hours).
+
+
 
 ### `QueueSendOptions`
 
 Optional configuration that applies when sending a message to a queue.
 
-- <code>contentType</code> <Type text="QueuesContentType" />
-  - The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
-  - As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
-  - See [QueuesContentType](#queuescontenttype) for possible values.
+* <code>contentType</code> <Type text="QueuesContentType" />
+
+  * The explicit content type of a message so it can be previewed correctly with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature. Optional argument.
+  * As of now, this option is for internal use. In the future, `contentType` will be used by alternative consumer types to explicitly mark messages as serialized so they can be consumed in the desired type.
+  * See [QueuesContentType](#queuescontenttype) for possible values.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be an integer between 0 and 86400 (24 hours). Setting this value to zero will explicitly prevent the message from being delayed, even if there is a global (default) delay at the queue level.
 
 ### `QueueSendBatchOptions`
 
 Optional configuration that applies when sending a batch of messages to a queue.
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be a positive integer.
+* <code>delaySeconds</code> <Type text="number" />
+
+  * The number of seconds to [delay messages](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be a positive integer.
 
 ### `QueuesContentType`
 
@@ -170,15 +183,17 @@ A union type containing valid message content types.
 type QueuesContentType = "text" | "bytes" | "json" | "v8";
 ```
 
-- Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
-- Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
-- Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
-- Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+* Use `"json"` to send a JavaScript object that can be JSON-serialized. This content type can be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com). The `json` content type is the default.
+* Use `"text"` to send a `String`. This content type can be previewed with the [List messages from the dashboard](/queues/examples/list-messages-from-dash/) feature.
+* Use `"bytes"` to send an `ArrayBuffer`. This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
+* Use `"v8"` to send a JavaScript object that cannot be JSON-serialized but is supported by [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) (for example `Date` and `Map`). This content type cannot be previewed from the [Cloudflare dashboard](https://dash.cloudflare.com) and will display as Base64-encoded.
 
 :::note
 
+
 The default content type for Queues changed to `json` (from `v8`) to improve compatibility with pull-based consumers for any Workers with a [compatibility date](/workers/configuration/compatibility-flags/#queues-send-messages-in-json-format) after `2024-03-18`.
 
+
 :::
 
 If you specify an invalid content type, or if your specified content type does not match the message content's type, the send operation will fail with an error.
@@ -195,11 +210,15 @@ interface QueueSendResult {
 }
 ```
 
-- <code>metadata</code> <Type text="object" />
-  - Contains metadata about the queue after the send operation.
 
-- <code>metadata.metrics</code> <Type text="QueueMetrics" />
-  - Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
+
+* <code>metadata</code> <Type text="object" />
+
+  * Contains metadata about the queue after the send operation.
+
+* <code>metadata.metrics</code> <Type text="QueueMetrics" />
+
+  * Realtime metrics for the queue. See [QueueMetrics](#queuemetrics).
 
 ### `QueueMetrics`
 
@@ -213,14 +232,19 @@ interface QueueMetrics {
 }
 ```
 
-- <code>backlogCount</code> <Type text="number" />
-  - The number of messages currently in the queue.
 
-- <code>backlogBytes</code> <Type text="number" />
-  - The total size of messages in the queue, in bytes.
 
-- <code>oldestMessageTimestamp</code> <Type text="number" />
-  - The timestamp (in milliseconds since epoch) of the oldest message in the queue.
+* <code>backlogCount</code> <Type text="number" />
+
+  * The number of messages currently in the queue.
+
+* <code>backlogBytes</code> <Type text="number" />
+
+  * The total size of messages in the queue, in bytes.
+
+* <code>oldestMessageTimestamp</code> <Type text="number" />
+
+  * The timestamp (in milliseconds since epoch) of the oldest message in the queue.
 
 ## Consumer
 
@@ -238,8 +262,10 @@ If the `queue()` function throws, or the promise returned by it or any of the pr
 
 :::note
 
+
 `waitUntil()` is the only supported method to run tasks (such as logging or metrics calls) that resolve after a queue handler has completed. Promises that have not resolved by the time the queue handler returns may not complete and will not block completion of execution.
 
+
 :::
 
 <Tabs syncKey="workersExamples">
@@ -278,19 +304,19 @@ You can type queue messages with `Queue<T>` on the producer and `ExportedHandler
 
 ```ts
 type MyMessage = {
-	id: string;
+  id: string;
 };
 
 interface Env {
-	MY_QUEUE: Queue<MyMessage>;
+  MY_QUEUE: Queue<MyMessage>;
 }
 
 export default {
-	async queue(batch) {
-		for (const message of batch.messages) {
-			console.log(message.body.id);
-		}
-	},
+  async queue(batch) {
+    for (const message of batch.messages) {
+      console.log(message.body.id);
+    }
+  },
 } satisfies ExportedHandler<Env, MyMessage>;
 ```
 
@@ -299,7 +325,7 @@ For primitive messages, use `Queue<number>` or `satisfies ExportedHandler<Env, n
 Or alternatively, a queue consumer can be written using the (deprecated) service worker syntax:
 
 ```js
-addEventListener("queue", (event) => {
+addEventListener('queue', (event) => {
 	event.waitUntil(handleMessages(event));
 });
 ```
@@ -308,8 +334,10 @@ In service worker syntax, `event` provides the same fields and methods as `Messa
 
 :::note
 
+
 When performing asynchronous tasks in your queue handler that iterates through messages, use an asynchronous version of iterating through your messages. For example, `for (const m of batch.messages)`or `await Promise.all(batch.messages.map(work))` allow for waiting for the results of asynchronous calls. `batch.messages.forEach()` does not.
 
+
 :::
 
 ### `MessageBatch`
@@ -318,25 +346,34 @@ A batch of messages that are sent to a consumer Worker.
 
 ```ts
 interface MessageBatch<Body = unknown> {
-	readonly queue: string;
-	readonly messages: readonly Message<Body>[];
-	ackAll(): void;
-	retryAll(options?: QueueRetryOptions): void;
+  readonly queue: string;
+  readonly messages: readonly Message<Body>[];
+  ackAll(): void;
+  retryAll(options?: QueueRetryOptions): void;
 }
 ```
 
-- <code>queue</code> <Type text="string" />
-  - The name of the Queue that belongs to this batch.
 
-- <code>messages</code> <Type text="Message[]" />
-  - An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
 
-- <code>ackAll()</code> <Type text="void" />
-  - Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+* <code>queue</code> <Type text="string" />
+
+  * The name of the Queue that belongs to this batch.
+
+* <code>messages</code> <Type text="Message[]" />
+
+  * An array of messages in the batch. Ordering of messages is best effort -- not guaranteed to be exactly the same as the order in which they were published.
+
+* <code>ackAll()</code> <Type text="void" />
+
+
+  * Marks every message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+
+* <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
+
+  * Marks every message to be retried in the next batch.
+  * Supports an optional `options` object.
+
 
-- <code>retryAll(options?: QueueRetryOptions)</code> <Type text="void" />
-  - Marks every message to be retried in the next batch.
-  - Supports an optional `options` object.
 
 ### `Message`
 
@@ -344,34 +381,44 @@ A message that is sent to a consumer Worker.
 
 ```ts
 interface Message<Body = unknown> {
-	readonly id: string;
-	readonly timestamp: Date;
-	readonly body: Body;
+  readonly id: string;
+  readonly timestamp: Date;
+  readonly body: Body;
 	readonly attempts: number;
-	ack(): void;
-	retry(options?: QueueRetryOptions): void;
+  ack(): void;
+  retry(options?: QueueRetryOptions): void;
 }
 ```
 
-- <code>id</code> <Type text="string" />
-  - A unique, system-generated ID for the message.
 
-- <code>timestamp</code> <Type text="Date" />
-  - A timestamp when the message was sent.
 
-- <code>body</code> <Type text="unknown" />
-  - The body of the message.
-  - The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+* <code>id</code> <Type text="string" />
+
+  * A unique, system-generated ID for the message.
+
+* <code>timestamp</code> <Type text="Date" />
+
+  * A timestamp when the message was sent.
+
+* <code>body</code> <Type text="unknown" />
+
+  * The body of the message.
+  * The body can be any type supported by the [structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types), as long as its size is less than 128 KB.
+
+* <code>attempts</code> <Type text="number" />
+
+	* The number of times the consumer has attempted to process this message. Starts at 1.
+
+* <code>ack()</code> <Type text="void" />
+
+  * Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
+
+* <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
 
-- <code>attempts</code> <Type text="number" />
-  - The number of times the consumer has attempted to process this message. Starts at 1.
+  * Marks a message to be retried in the next batch.
+  * Supports an optional `options` object.
 
-- <code>ack()</code> <Type text="void" />
-  - Marks a message as successfully delivered, regardless of whether your `queue()` consumer handler returns successfully or not.
 
-- <code>retry(options?: QueueRetryOptions)</code> <Type text="void" />
-  - Marks a message to be retried in the next batch.
-  - Supports an optional `options` object.
 
 ### `QueueRetryOptions`
 
@@ -379,13 +426,13 @@ Optional configuration when marking a message or a batch of messages for retry.
 
 ```ts
 interface QueueRetryOptions {
-	delaySeconds?: number;
+  delaySeconds?: number;
 }
 ```
 
-- <code>delaySeconds</code> <Type text="number" />
-  - The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
-  - Must be a positive integer.
+* <code>delaySeconds</code> <Type text="number" />
 
-- When the promise resolves, the messages are written to disk.
-  - Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
+  * The number of seconds to [delay a message](/queues/configuration/batching-retries/) for within the queue, before it can be delivered to a consumer.
+  * Must be a positive integer.
+* When the promise resolves, the messages are written to disk.
+  * Returns a [QueueSendResult](#queuesendresult) containing realtime metrics about the queue.
diff --git a/src/content/docs/queues/configuration/local-development.mdx b/src/content/docs/queues/configuration/local-development.mdx
index 557fb80e5c067c5..69ba57856a90286 100644
--- a/src/content/docs/queues/configuration/local-development.mdx
+++ b/src/content/docs/queues/configuration/local-development.mdx
@@ -23,7 +23,6 @@ To develop locally with Queues, you will need:
 ## Start a local development session
 
 Open your terminal and run the following commands to start a local development session:
-
 ```sh
 npx wrangler@latest dev
 ```
@@ -41,15 +40,13 @@ Local development sessions create a standalone, local-only environment that mirr
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/general/#dev) to learn more about how to configure a local development session.
 
 ## Separating producer & consumer Workers
-
 Wrangler supports running multiple Workers simultaneously with a single command. If your architecture separates the producer and consumer into distinct Workers, you can use this functionality to test the entire message flow locally.
 
 :::caution
 Support for running multiple Workers at once with one Wrangler command is experimental, and subject to change as we work on the experience. If you run into bugs or have any feedback, [open an issue on the workers-sdk repository](https://github.com/cloudflare/workers-sdk/issues/new)
 :::
 
-For example, if your project has the following directory structure:
-
+For example, if your project has the following directory structure: 
 ```
 producer-worker/
 ├── wrangler.jsonc
@@ -60,7 +57,6 @@ producer-worker/
 ```
 
 You can start development servers for both workers with the following command:
-
 ```sh
 npx wrangler@latest dev -c wrangler.jsonc -c consumer-worker/wrangler.jsonc --persist-to .wrangler/state
 ```
@@ -71,5 +67,4 @@ When the producer Worker sends messages to the queue, the consumer Worker will a
 :::
 
 ## Known Issues
-
 - Queues does not support Wrangler remote mode (`wrangler dev --remote`).
diff --git a/src/content/docs/queues/configuration/pause-purge.mdx b/src/content/docs/queues/configuration/pause-purge.mdx
index aa3e793a9a0dc2e..0ca72cdbb02b121 100644
--- a/src/content/docs/queues/configuration/pause-purge.mdx
+++ b/src/content/docs/queues/configuration/pause-purge.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - queues
 ---
-
 import { WranglerConfig, Type, MetaInfo } from "~/components";
 
 ## Pause Delivery
@@ -39,11 +38,9 @@ $ npx wrangler queues resume-delivery <QUEUE-NAME>
   - The name of the queue for which delivery should be resumed.
 
 ### What happens to HTTP Pull consumers with a paused queue?
-
 When a queue is paused, messages cannot be pulled by an [HTTP pull based consumer](/queues/configuration/pull-consumers). Requests to pull messages will receive a `409` response, along with an error message stating `queue_delivery_paused`.
 
 ## Purge queue
-
 Purging a queue permanently deletes any messages currently stored in the Queue. Purging is useful while developing a new application, especially to clear out any test data. It can also be useful in production to handle scenarios when a batch of bad messages have been sent to a Queue.
 
 Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the queue.
@@ -53,9 +50,7 @@ Purging a queue is an irreversible operation. Make sure to use this operation ca
 :::
 
 ### Purge queue using Wrangler
-
 The following command will purge messages from your queue. You will be prompted to enter the queue name to confirm the operation.
-
 ```sh
 $ npx wrangler queues purge <QUEUE-NAME>
 
@@ -63,5 +58,4 @@ This operation will permanently delete all the messages in Queue <QUEUE-NAME>. T
 ```
 
 ### Does purging a Queue affect my bill?
-
 Purging a queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.
diff --git a/src/content/docs/queues/event-subscriptions/index.mdx b/src/content/docs/queues/event-subscriptions/index.mdx
index 8d7a0aa847de518..7fea1b1b89a7a1d 100644
--- a/src/content/docs/queues/event-subscriptions/index.mdx
+++ b/src/content/docs/queues/event-subscriptions/index.mdx
@@ -12,7 +12,7 @@ products:
   - workers
 ---
 
-import { LinkCard } from "~/components";
+import { LinkCard } from "~/components"
 
 Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products (e.g., [KV](/kv/), [Workers AI](/workers-ai), [Workers](/workers)) can publish structured events to a queue, which you can then consume with Workers or [HTTP pull consumers](/queues/configuration/pull-consumers/) to build custom workflows, integrations, or logic.
 
@@ -34,4 +34,4 @@ An event is a structured record of something happening in your Cloudflare accoun
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event types and their corresponding data schemas."
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
index d7dc089f45b0751..aa2f5a7998b8f6d 100644
--- a/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
+++ b/src/content/docs/queues/event-subscriptions/manage-event-subscriptions.mdx
@@ -8,7 +8,11 @@ sidebar:
   order: 1
 ---
 
-import { Steps, LinkCard, DashButton } from "~/components";
+import {
+	Steps,
+	LinkCard,
+	DashButton,
+} from "~/components";
 
 Learn how to:
 
@@ -98,4 +102,4 @@ npx wrangler queues subscription delete <queue-name> --id <subscription-id>
 	title="Events & schemas"
 	href="/queues/event-subscriptions/events-schemas/"
 	description="Explore available event sources and types that you can subscribe to."
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
index 4875bc7d1174f24..58bc8f327afbbc5 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-http.mdx
@@ -22,6 +22,7 @@ This allows you to write to a Queue from any service or programming language tha
 - A [queue created](/queues/get-started/#3-create-a-queue) via the [Cloudflare dashboard](https://dash.cloudflare.com) or the [wrangler CLI](/workers/wrangler/install-and-update/).
 - A Cloudflare API token with the `Queues Edit` permission.
 
+
 ### 1. Send a test message
 
 To make sure you successfully authenticate and write a message to your queue, use `curl` on the command line:
diff --git a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
index fb595d622adf56c..45926ceeb6e587d 100644
--- a/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
+++ b/src/content/docs/queues/examples/publish-to-a-queue-via-workers.mdx
@@ -66,10 +66,7 @@ export default {
 			messages = await req.json();
 		} catch {
 			// Return a HTTP 400 (Bad Request) if the payload isn't JSON
-			return Response.json(
-				{ error: "payload not valid JSON" },
-				{ status: 400 },
-			);
+			return Response.json({ error: "payload not valid JSON" }, { status: 400 });
 		}
 
 		// Publish to the Queue
diff --git a/src/content/docs/queues/examples/send-errors-to-r2.mdx b/src/content/docs/queues/examples/send-errors-to-r2.mdx
index 0ff30d559be40f2..ba6649a7b277a6a 100644
--- a/src/content/docs/queues/examples/send-errors-to-r2.mdx
+++ b/src/content/docs/queues/examples/send-errors-to-r2.mdx
@@ -63,33 +63,33 @@ interface Env {
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			return doRequest(req);
-		} catch (e) {
-			const error: ErrorMessage = {
-				message: e instanceof Error ? e.message : String(e),
-				stack: e instanceof Error ? e.stack : undefined,
-			};
-			await env.ERROR_QUEUE.send(error);
-			return new Response(error.message, { status: 500 });
-		}
-	},
-	async queue(batch, env, ctx): Promise<void> {
-		let file = "";
-		for (const message of batch.messages) {
-			const error = message.body;
-			file += error.stack ?? error.message;
-			file += "\r\n";
-		}
-		await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      return doRequest(req);
+    } catch (e) {
+      const error: ErrorMessage = {
+        message: e instanceof Error ? e.message : String(e),
+        stack: e instanceof Error ? e.stack : undefined,
+      };
+      await env.ERROR_QUEUE.send(error);
+      return new Response(error.message, { status: 500 });
+    }
+  },
+  async queue(batch, env, ctx): Promise<void> {
+    let file = "";
+    for (const message of batch.messages) {
+      const error = message.body;
+      file += error.stack ?? error.message;
+      file += "\r\n";
+    }
+    await env.ERROR_BUCKET.put(`errors/${Date.now()}.log`, file);
+  },
 } satisfies ExportedHandler<Env, ErrorMessage>;
 
 function doRequest(request: Request): Response {
-	if (Math.random() > 0.5) {
-		return new Response("Success!");
-	}
-	throw new Error("Failed!");
+  if (Math.random() > 0.5) {
+    return new Response("Success!");
+  }
+  throw new Error("Failed!");
 }
 ```
diff --git a/src/content/docs/queues/examples/send-messages-from-dash.mdx b/src/content/docs/queues/examples/send-messages-from-dash.mdx
index 1a2b6cc2f1b7455..6d384b6b6bd668a 100644
--- a/src/content/docs/queues/examples/send-messages-from-dash.mdx
+++ b/src/content/docs/queues/examples/send-messages-from-dash.mdx
@@ -22,14 +22,14 @@ To send messages from the dashboard:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select the queue to send a message to.
 3. Select the **Messages** tab.
 4. Select **Send**.
 5. Choose your message **Content Type**: _Text_ or _JSON_.
-6. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
-7. Select **Send**.
+5. Enter your message. Alternatively, drag a file over the textbox to upload a file as a message.
+6. Select **Send**.
 
 Your message will be sent to the queue.
 
diff --git a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
index 4803ac4d16c217c..481b9a11fe9e225 100644
--- a/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
+++ b/src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
@@ -73,45 +73,45 @@ Extending the `DurableObject` base class makes your `Env` available on `this.env
 import { DurableObject } from "cloudflare:workers";
 
 interface Env {
-	YOUR_QUEUE: Queue;
-	YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
+  YOUR_QUEUE: Queue;
+  YOUR_DO_CLASS: DurableObjectNamespace<YourDurableObject>;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		// Assume each Durable Object is mapped to a userId in a query parameter
-		// In a production application, this will be a userId defined by your application
-		// that you validate (and/or authenticate) first.
-		const url = new URL(req.url);
-		const userIdParam = url.searchParams.get("userId");
-
-		if (userIdParam) {
-			// Get a stub that allows you to call that Durable Object
-			const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
-
-			// Pass the request to that Durable Object and await the response
-			// This invokes the constructor once on your Durable Object class (defined further down)
-			// on the first initialization, and the fetch method on each request.
-			// We pass the original Request to the Durable Object's fetch method
-			const response = await durableObjectStub.fetch(req);
-
-			// This would return "wrote to queue", but you could return any response.
-			return response;
-		}
-		return new Response("userId must be provided", { status: 400 });
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    // Assume each Durable Object is mapped to a userId in a query parameter
+    // In a production application, this will be a userId defined by your application
+    // that you validate (and/or authenticate) first.
+    const url = new URL(req.url);
+    const userIdParam = url.searchParams.get("userId");
+
+    if (userIdParam) {
+      // Get a stub that allows you to call that Durable Object
+      const durableObjectStub = env.YOUR_DO_CLASS.getByName(userIdParam);
+
+      // Pass the request to that Durable Object and await the response
+      // This invokes the constructor once on your Durable Object class (defined further down)
+      // on the first initialization, and the fetch method on each request.
+      // We pass the original Request to the Durable Object's fetch method
+      const response = await durableObjectStub.fetch(req);
+
+      // This would return "wrote to queue", but you could return any response.
+      return response;
+    }
+    return new Response("userId must be provided", { status: 400 });
+  },
 } satisfies ExportedHandler<Env>;
 
 export class YourDurableObject extends DurableObject<Env> {
-	async fetch(req: Request): Promise<Response> {
-		// Error handling elided for brevity.
-		// Publish to your queue
-		await this.env.YOUR_QUEUE.send({
-			id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
-			// Write any other properties to your queue
-		});
-
-		return new Response("wrote to queue");
-	}
+  async fetch(req: Request): Promise<Response> {
+    // Error handling elided for brevity.
+    // Publish to your queue
+    await this.env.YOUR_QUEUE.send({
+      id: this.ctx.id.toString(), // Write the ID of the Durable Object to your queue
+      // Write any other properties to your queue
+    });
+
+    return new Response("wrote to queue");
+  }
 }
 ```
diff --git a/src/content/docs/queues/glossary.mdx b/src/content/docs/queues/glossary.mdx
index 4bb72d0ab69bbf6..845aecc4bdd10b3 100644
--- a/src/content/docs/queues/glossary.mdx
+++ b/src/content/docs/queues/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - queues
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Queues documentation.
 
diff --git a/src/content/docs/queues/observability/index.mdx b/src/content/docs/queues/observability/index.mdx
index 7becde1ad32ae99..c9ebe21e8103fb1 100644
--- a/src/content/docs/queues/observability/index.mdx
+++ b/src/content/docs/queues/observability/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/observability/metrics.mdx b/src/content/docs/queues/observability/metrics.mdx
index 39c918a48ff366b..e003fb8ca5507e5 100644
--- a/src/content/docs/queues/observability/metrics.mdx
+++ b/src/content/docs/queues/observability/metrics.mdx
@@ -74,10 +74,10 @@ The `queueMessageOperationsAdaptiveGroups` dataset provides the following dimens
 
 You can access realtime backlog metrics via the [Queues REST API](/api/resources/queues/) and [JavaScript API](/queues/configuration/javascript-apis/). These metrics provide point-in-time values rather than aggregated data.
 
-| Metric                   | Field Name                    | Description                                                    |
-| ------------------------ | ----------------------------- | -------------------------------------------------------------- |
-| Backlog count            | `backlog_count`               | Number of messages currently in the queue                      |
-| Backlog bytes            | `backlog_bytes`               | Total size of messages in the queue, in bytes                  |
+| Metric                   | Field Name                 | Description                                                    |
+| ------------------------ | -------------------------- | -------------------------------------------------------------- |
+| Backlog count            | `backlog_count`            | Number of messages currently in the queue                      |
+| Backlog bytes            | `backlog_bytes`            | Total size of messages in the queue, in bytes                  |
 | Oldest message timestamp | `oldest_message_timestamp_ms` | Timestamp (in milliseconds) of the oldest message in the queue |
 
 To retrieve these metrics via the REST API, use the metrics endpoint (`/accounts/{account_id}/queues/{queue_id}/metrics`).
diff --git a/src/content/docs/queues/platform/index.mdx b/src/content/docs/queues/platform/index.mdx
index db2ed89685726c9..a227085598b92e9 100644
--- a/src/content/docs/queues/platform/index.mdx
+++ b/src/content/docs/queues/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/queues/platform/limits.mdx b/src/content/docs/queues/platform/limits.mdx
index 7da1292c246a72b..4ca7f09527545a6 100644
--- a/src/content/docs/queues/platform/limits.mdx
+++ b/src/content/docs/queues/platform/limits.mdx
@@ -8,49 +8,42 @@ products:
   - queues
 ---
 
-import { Render, WranglerConfig } from "~/components";
+import { Render, WranglerConfig } from "~/components"
 
 :::caution
 The following limits apply to both Workers Paid and Workers Free plans with the exception of **Message Retention**, which is non-configurable at 24 hours for the Workers Free plan.
 :::
 
-| Feature                                                 | Limit                                                                                             |
-| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| Queues                                                  | 10,000 per account                                                                                |
-| Message size                                            | 128 KB <sup>1</sup>                                                                               |
-| Message retries                                         | 100                                                                                               |
-| Maximum consumer batch size                             | 100 messages                                                                                      |
-| Maximum messages per `sendBatch` call                   | 100 (or 256KB in total)                                                                           |
-| Maximum Batch wait time                                 | 60 seconds                                                                                        |
-| Per-queue message throughput                            | 5,000 messages per second <sup>2</sup>                                                            |
-| Message retention period <sup>3</sup>                   | [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration).        |
-| Per-queue backlog size <sup>4</sup>                     | 25GB                                                                                              |
-| Concurrent consumer invocations                         | 250 <sup>push-based only</sup>                                                                    |
-| Consumer duration (wall clock time)                     | 15 minutes <sup>5</sup>                                                                           |
-| [Consumer CPU time](/workers/platform/limits/#cpu-time) | [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) |
-| `visibilityTimeout` (pull-based queues)                 | 12 hours                                                                                          |
-| `delaySeconds` (when sending or retrying)               | 24 hours                                                                                          |
-
-<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100
-bytes of internal metadata that counts towards total message limits.
-
-<sup>2</sup> Exceeding the maximum message throughput will cause the `send()`
-and `sendBatch()` methods to throw an exception with a `Too Many Requests` error
-until your producer falls below the limit.
-
-<sup>3</sup> Messages in a queue that reach the maximum message retention are
-deleted from the queue. Queues does not delete messages in the same queue that
-have not reached this limit.
-
-<sup>4</sup> Individual queues that reach this limit will receive a `Storage
-Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
+| Feature                                       									| Limit                                                         |
+| ----------------------------------------------------------------| ------------------------------------------------------------- |
+| Queues                                        									| 10,000 per account								                            |
+| Message size                                  									| 128 KB <sup>1</sup>                                           |
+| Message retries                               									| 100                                                           |
+| Maximum consumer batch size                   									| 100 messages 								                                  |
+| Maximum messages per `sendBatch` call         									| 100 (or 256KB in total)                                       |
+| Maximum Batch wait time                       									| 60 seconds                                                    |
+| Per-queue message throughput    																| 5,000 messages per second <sup>2</sup>                        |
+| Message retention period <sup>3</sup>         									| [Configurable up to 14 days](/queues/configuration/configure-queues/#queue-configuration). |
+| Per-queue backlog size <sup>4</sup>           									| 25GB                                                          |
+| Concurrent consumer invocations               									| 250 <sup>push-based only</sup>                                |
+| Consumer duration (wall clock time) 														| 15 minutes <sup>5</sup>                                       |
+| [Consumer CPU time](/workers/platform/limits/#cpu-time)| [Configurable to 5 minutes](/queues/platform/limits/#increasing-queue-consumer-worker-cpu-limits) 							|
+| `visibilityTimeout` (pull-based queues)       									| 12 hours                                                      |
+| `delaySeconds` (when sending or retrying)     									| 24 hours                                                      |
+
+<sup>1</sup> 1 KB is measured as 1000 bytes. Messages can include up to \~100 bytes of internal metadata that counts towards total message limits.
+
+<sup>2</sup> Exceeding the maximum message throughput will cause the `send()` and `sendBatch()` methods to throw an exception with a `Too Many Requests` error until your producer falls below the limit.
+
+<sup>3</sup> Messages in a queue that reach the maximum message retention are deleted from the queue. Queues does not delete messages in the same queue that have not reached this limit.
+
+<sup>4</sup> Individual queues that reach this limit will receive a `Storage Limit Exceeded` error when calling `send()` or `sendBatch()` on the queue.
 
 <sup>5</sup> Refer to [Workers limits](/workers/platform/limits/#cpu-time).
 
 <Render file="limits_increase" product="workers" />
 
 ### Increasing Queue Consumer Worker CPU Limits
-
 [Queue consumer Workers](/queues/reference/how-queues-works/#consumers) are Worker scripts, and share the same [per invocation CPU limits](/workers/platform/limits/#account-plan-limits) as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O.
 
 By default, the maximum CPU time per consumer Worker invocation is set to 30 seconds, but can be increased by setting `limits.cpu_ms` in your Wrangler configuration:
diff --git a/src/content/docs/queues/platform/pricing.mdx b/src/content/docs/queues/platform/pricing.mdx
index 0a2d005b5559044..f8336c97f5b08a3 100644
--- a/src/content/docs/queues/platform/pricing.mdx
+++ b/src/content/docs/queues/platform/pricing.mdx
@@ -11,7 +11,7 @@ products:
   - queues
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="queues_pricing" product="workers" />
 
@@ -19,16 +19,23 @@ import { Render } from "~/components";
 
 If an application writes, reads and deletes (consumes) one million messages a day (in a 30 day month), and each message is less than 64 KB in size, the estimated bill for the month would be:
 
+
+
 |                     | Total Usage           | Free Usage | Billed Usage | Price      |
 | ------------------- | --------------------- | ---------- | ------------ | ---------- |
 | Standard operations | 3 \* 30 \* 1,000,000  | 1,000,000  | 89,000,000   | $35.60     |
 |                     | (write, read, delete) |            |              |            |
 | **TOTAL**           |                       |            |              | **$35.60** |
 
+
+
 An application that writes, reads and deletes (consumes) 100 million \~127 KB messages (each message counts as two 64 KB chunks) per month would have an estimated bill resembling the following:
 
+
+
 |                     | Total Usage                  | Free Usage | Billed Usage | Price       |
 | ------------------- | ---------------------------- | ---------- | ------------ | ----------- |
 | Standard operations | 2 \* 3 \* 100 \* 1,000,000   | 1,000,000  | 599,000,000  | $239.60     |
 |                     | (2x ops for > 64KB messages) |            |              |             |
 | **TOTAL**           |                              |            |              | **$239.60** |
+
diff --git a/src/content/docs/queues/reference/delivery-guarantees.mdx b/src/content/docs/queues/reference/delivery-guarantees.mdx
index bd589fd8317c267..1f78e3276a09305 100644
--- a/src/content/docs/queues/reference/delivery-guarantees.mdx
+++ b/src/content/docs/queues/reference/delivery-guarantees.mdx
@@ -12,8 +12,8 @@ Delivery guarantees define how strongly a messaging system enforces the delivery
 
 As you make stronger guarantees about message delivery, the system needs to perform more checks and acknowledgments to ensure that messages are delivered, or maintain state to ensure a message is only delivered the specified number of times. This increases the latency of the system and reduces the overall throughput of the system. Each message may require an additional internal acknowledgements, and an equivalent number of additional roundtrips, before it can be considered delivered.
 
-- **Queues provides _at least once_ delivery by default** in order to optimize for reliability.
-- This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
-- For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
+* **Queues provides *at least once* delivery by default** in order to optimize for reliability.
+* This means that messages are guaranteed to be delivered at least once, and in rare occasions, may be delivered more than once.
+* For the majority of applications, this is the right balance between not losing any messages and minimizing end-to-end latency, as exactly once delivery incurs additional overheads in any messaging system.
 
 In cases where processing the same message more than once would introduce unintended behaviour, generating a unique ID when writing the message to the queue and using that as the primary key on database inserts and/or as an idempotency key to de-duplicate the message after processing. For example, using this idempotency key as the ID in an upstream email API or payment API will allow those services to reject the duplicate on your behalf, without you having to carry additional state in your application.
diff --git a/src/content/docs/queues/reference/error-codes.mdx b/src/content/docs/queues/reference/error-codes.mdx
index 94d502fd00435b6..1a227b114e29bfe 100644
--- a/src/content/docs/queues/reference/error-codes.mdx
+++ b/src/content/docs/queues/reference/error-codes.mdx
@@ -17,7 +17,7 @@ For the [JavaScript APIs](/queues/configuration/javascript-apis/), Queues operat
 ```js
 try {
 	await env.MY_QUEUE.send("message", { delaySeconds: 999999 });
-	return new Response("Sent message to the queue");
+    return new Response("Sent message to the queue");
 } catch (error) {
 	console.error(error);
 	return new Response("Failed to send message to the queue", { status: 500 });
@@ -28,18 +28,20 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ```json
 {
-	"errors": [
-		{
-			"code": 7003,
-			"message": "No route for the URI",
-			"documentation_url": "documentation_url",
-			"source": {
-				"pointer": "pointer"
-			}
-		}
-	],
-	"messages": ["string"],
-	"success": true
+  "errors": [
+    {
+      "code": 7003,
+      "message": "No route for the URI",
+      "documentation_url": "documentation_url",
+      "source": {
+        "pointer": "pointer"
+      }
+    }
+  ],
+  "messages": [
+    "string"
+  ],
+  "success": true
 }
 ```
 
@@ -47,19 +49,19 @@ For the [Cloudflare API via HTTP](/api/resources/queues/subresources/messages/),
 
 ### Client side errors
 
-| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                           |
-| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                           |
-| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                |
-| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                 |
-| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                           |
-| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                       |
+| Error Code | Error                    | Details                                                                    | Recommended actions                                                                                                                                                                                                       |
+| ---------- | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10104      | QueueNotFound            | Queue does not exist                                                       | Check for existence of `queue_id` in [List Queues endpoint](/api/resources/queues/)                                                                                                                                       |
+| 10106      | Unauthorized             | Unauthorized request                                                       | Ensure that current user has permission to push to that queue.                                                                                                                                                            |
+| 10107      | QueueIDMalformed         | The queue ID in the request URL is not a valid queue identifier            | Ensure that `queue_id` contains only alphanumeric characters.                                                                                                                                                             |
+| 10201      | ClientDisconnected       | Client disconnected during request processing                              | Consider increasing timeout and retry message send.                                                                                                                                                                       |
+| 10202      | BatchDelayInvalid        | Invalid batch delay                                                        | Ensure that `batch_delay` is within 1 and 86400 seconds                                                                                                                                                                   |
 | 10203      | MessageMetadataInvalid   | Invalid message metadata (includes invalid content type and invalid delay) | Ensure `contentType` is one of `text`, `bytes`, `json`, or `v8`. Ensure the message delay does not exceed the [maximum of 24 hours](/queues/platform/limits/) |
-| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                               |
-| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                 |
-| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                          |
-| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                             |
-| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                    |
+| 10204      | MessageSizeOutOfBounds   | Message size out of bounds                                                 | Ensure that message size is within 0 and 128 KB                                                                                                                                                                           |
+| 10205      | BatchSizeOutOfBounds     | Batch size out of bounds                                                   | Ensure that batch size is within 0 and 256 KB                                                                                                                                                                             |
+| 10206      | BatchCountOutOfBounds    | Batch count out of bounds                                                  | Ensure that batch count is within 0 and 100 messages                                                                                                                                                                      |
+| 10207      | JSONRequestBodyInvalid   | Request JSON body does not match expected schema                           | Ensure that JSON body matches the expected schema                                                                                                                                                                         |
+| 10208      | JSONRequestBodyMalformed | Request body is not valid JSON                                             | [REST API](/api/resources/queues/methods/create/) request body is not valid. Look at error message for additional details.                                                                                                                                         |
 
 ### 429 type errors
 
diff --git a/src/content/docs/queues/reference/how-queues-works.mdx b/src/content/docs/queues/reference/how-queues-works.mdx
index 807d34b52e91d6c..efc649900122fdd 100644
--- a/src/content/docs/queues/reference/how-queues-works.mdx
+++ b/src/content/docs/queues/reference/how-queues-works.mdx
@@ -29,9 +29,9 @@ Queues does not guarantee that messages will be delivered to a consumer in the s
 
 Developers can create multiple queues. Creating multiple queues can be useful to:
 
-- Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
-- Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
-- Configure different batching strategies for each consumer connected to a queue.
+* Separate different use-cases and processing requirements: for example, a logging queue vs. a password reset queue.
+* Horizontally scale your overall throughput (messages per second) by using multiple queues to scale out.
+* Configure different batching strategies for each consumer connected to a queue.
 
 For most applications, a single producer Worker per queue, with a single consumer Worker consuming messages from that queue allows you to logically separate the processing for each of your queues.
 
@@ -43,29 +43,31 @@ For example, if we bound a queue named `my-first-queue` to a binding of `MY_FIRS
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		const message = {
-			url: req.url,
-			method: req.method,
-			headers: Object.fromEntries(req.headers),
-		};
-
-		await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
-		return new Response("Sent!");
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    const message = {
+      url: req.url,
+      method: req.method,
+      headers: Object.fromEntries(req.headers),
+    };
+
+    await env.MY_FIRST_QUEUE.send(message); // This will throw an exception if the send fails for any reason
+    return new Response("Sent!");
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
 :::note
 
+
 You can also use [`context.waitUntil()`](/workers/runtime-apis/context/#waituntil) to send the message without blocking the response.
 
 Note that because `waitUntil()` is non-blocking, any errors raised from the `send()` or `sendBatch()` methods on a queue will be implicitly ignored.
 
+
 :::
 
 A queue can have multiple producer Workers. For example, you may have multiple producer Workers writing events or logs to a shared queue based on incoming HTTP requests from users. There is no limit to the total number of producer Workers that can write to a single queue.
@@ -80,25 +82,25 @@ To explicitly set the content type or specify an alternative content type, pass
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		const message = {
-			url: req.url,
-			method: req.method,
-			headers: Object.fromEntries(req.headers),
-		};
-		try {
-			await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
-			return new Response("Sent!");
-		} catch (e) {
-			// Catch cases where send fails, including due to a mismatched content type
-			const msg = e instanceof Error ? e.message : "Unknown error";
-			return Response.json({ error: msg }, { status: 500 });
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    const message = {
+      url: req.url,
+      method: req.method,
+      headers: Object.fromEntries(req.headers),
+    };
+    try {
+      await env.MY_FIRST_QUEUE.send(message, { contentType: "json" }); // "json" is the default
+      return new Response("Sent!");
+    } catch (e) {
+      // Catch cases where send fails, including due to a mismatched content type
+      const msg = e instanceof Error ? e.message : "Unknown error";
+      return Response.json({ error: msg }, { status: 500 });
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -106,21 +108,21 @@ To only accept simple strings when writing to a queue, set `{ contentType: "text
 
 ```ts
 interface Env {
-	readonly MY_FIRST_QUEUE: Queue;
+  readonly MY_FIRST_QUEUE: Queue;
 }
 
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			// This will throw an exception (error) if you pass a non-string to the queue,
-			// such as a native JavaScript object or ArrayBuffer.
-			await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
-			return new Response("Sent!");
-		} catch (e) {
-			const msg = e instanceof Error ? e.message : "Unknown error";
-			return Response.json({ error: msg }, { status: 500 });
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      // This will throw an exception (error) if you pass a non-string to the queue,
+      // such as a native JavaScript object or ArrayBuffer.
+      await env.MY_FIRST_QUEUE.send("hello there", { contentType: "text" }); // explicitly set 'text'
+      return new Response("Sent!");
+    } catch (e) {
+      const msg = e instanceof Error ? e.message : "Unknown error";
+      return Response.json({ error: msg }, { status: 500 });
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -137,22 +139,22 @@ A queue can only have one type of consumer configured.
 
 ### Create a consumer Worker
 
-A consumer is the term for a client that is subscribing to or _consuming_ messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
+A consumer is the term for a client that is subscribing to or *consuming* messages from a queue. In its most basic form, a consumer is defined by creating a `queue` handler in a Worker:
 
 ```ts
 interface Env {
-	// Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
+  // Add your bindings here, e.g. KV namespaces, R2 buckets, D1 databases
 }
 
 export default {
-	async queue(batch, env, ctx): Promise<void> {
-		// Do something with messages in the batch
-		// i.e. write to R2 storage, D1 database, or POST to an external API
-		for (const msg of batch.messages) {
-			// Process each message
-			console.log(msg.body);
-		}
-	},
+  async queue(batch, env, ctx): Promise<void> {
+    // Do something with messages in the batch
+    // i.e. write to R2 storage, D1 database, or POST to an external API
+    for (const msg of batch.messages) {
+      // Process each message
+      console.log(msg.body);
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -180,40 +182,42 @@ Importantly, each queue can only have one active consumer. This allows Cloudflar
 
 :::note[Best practice]
 
+
 Configure a single consumer per queue. This both logically separates your queues, and ensures that errors (failures) in processing messages from one queue do not impact your other queues.
 
+
 :::
 
 Notably, you can use the same consumer with multiple queues. The queue handler that defines your consumer Worker will be invoked by the queues it is connected to.
 
-- The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
-- This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
+* The `MessageBatch` that is passed to your `queue` handler includes a `queue` property with the name of the queue the batch was read from.
+* This can reduce the amount of code you need to write, and allow you to process messages based on the name of your queues.
 
 For example, a consumer configured to consume messages from multiple queues would resemble the following:
 
 ```ts
 interface Env {
-	// Add your bindings here
+  // Add your bindings here
 }
 
 export default {
-	async queue(batch, env, ctx): Promise<void> {
-		// MessageBatch has a `queue` property we can switch on
-		switch (batch.queue) {
-			case "log-queue":
-				// Write the batch to R2
-				break;
-			case "debug-queue":
-				// Write the message to the console or to another queue
-				break;
-			case "email-reset":
-				// Trigger a password reset email via an external API
-				break;
-			default:
-				// Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
-				break;
-		}
-	},
+  async queue(batch, env, ctx): Promise<void> {
+    // MessageBatch has a `queue` property we can switch on
+    switch (batch.queue) {
+      case "log-queue":
+        // Write the batch to R2
+        break;
+      case "debug-queue":
+        // Write the message to the console or to another queue
+        break;
+      case "email-reset":
+        // Trigger a password reset email via an external API
+        break;
+      default:
+        // Handle messages we haven't mentioned explicitly (write a log, push to a DLQ)
+        break;
+    }
+  },
 } satisfies ExportedHandler<Env>;
 ```
 
diff --git a/src/content/docs/queues/reference/index.mdx b/src/content/docs/queues/reference/index.mdx
index a4b4b60c39f76b3..5470c10d9bcf385 100644
--- a/src/content/docs/queues/reference/index.mdx
+++ b/src/content/docs/queues/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - queues
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
index 1f5af0257e338e5..ca3746a34a661dd 100644
--- a/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
+++ b/src/content/docs/r2-sql/reference/limitations-best-practices.mdx
@@ -27,15 +27,15 @@ This page summarizes supported features, limitations, and best practices.
 | 173 scalar functions                                    | Yes       | Math, string, datetime, regex, crypto, array, map, struct, JSON              |
 | 33 aggregate functions                                  | Yes       | Basic, approximate, statistical, bitwise, boolean, positional                |
 | Approximate aggregates                                  | Yes       | `approx_distinct`, `approx_median`, `approx_percentile_cont`, `approx_top_k` |
-| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions              |
+| Struct / Array / Map column types                       | Yes       | Bracket notation, `get_field()`, array functions, map functions           |
 | CTEs (`WITH ... AS`)                                    | Yes       | Can reference different tables and include JOINs                             |
 | JOINs (INNER, LEFT, RIGHT, FULL OUTER, CROSS)           | Yes       | All standard join types                                                      |
-| Implicit joins (comma FROM)                             | Yes       |                                                                              |
-| Subqueries (`IN`, `NOT IN`)                             | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
-| Subqueries (`EXISTS`, `NOT EXISTS`)                     | Yes       | semi-join and anti-join patterns                                             |
-| Scalar subqueries                                       | Yes       | In SELECT, WHERE, HAVING                                                     |
-| Derived tables (FROM subqueries)                        | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
-| Self-joins                                              | Yes       | Same table with different aliases                                            |
+| Implicit joins (comma FROM)                              | Yes       |                                                                              |
+| Subqueries (`IN`, `NOT IN`)                              | Yes       | `NOT IN` not supported on nullable columns — use `NOT EXISTS` instead        |
+| Subqueries (`EXISTS`, `NOT EXISTS`)                      | Yes       | semi-join and anti-join patterns                                             |
+| Scalar subqueries                                        | Yes       | In SELECT, WHERE, HAVING                                                     |
+| Derived tables (FROM subqueries)                         | Yes       | Can be nested and joined. `LATERAL` derived tables not supported.            |
+| Self-joins                                               | Yes       | Same table with different aliases                                            |
 | Window functions (`OVER`)                               | No        |                                                                              |
 | `SELECT DISTINCT`                                       | No        | Use `approx_distinct`                                                        |
 | `OFFSET`                                                | No        |                                                                              |
@@ -49,44 +49,44 @@ For the full SQL syntax, refer to the [SQL reference](/r2-sql/sql-reference/).
 
 ## Unsupported SQL features
 
-| Feature                                                                       | Error                                                   |
-| :---------------------------------------------------------------------------- | :------------------------------------------------------ |
-| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported` |
-| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`   |
-| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                            |
-| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`   |
-| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                    |
-| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                    |
-| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                           |
-| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                           |
-| Nested (parenthesized) joins                                                  | Not supported                                           |
-| `LATERAL` derived tables                                                      | Not supported                                           |
-| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                           |
+| Feature                                                                       | Error                                                    |
+| :---------------------------------------------------------------------------- | :------------------------------------------------------- |
+| `SELECT DISTINCT`                                                             | `unsupported feature: SELECT DISTINCT is not supported`  |
+| `OFFSET`                                                                      | `unsupported feature: OFFSET clause is not supported`    |
+| `UNION` / `INTERSECT` / `EXCEPT`                                              | Set operations not supported                             |
+| Window functions (`OVER`)                                                     | `unsupported feature: window functions (OVER clause)`    |
+| `INSERT` / `UPDATE` / `DELETE`                                                | `only read-only queries are allowed`                     |
+| `CREATE` / `DROP` / `ALTER`                                                   | `only read-only queries are allowed`                     |
+| `UNNEST` / `PIVOT` / `UNPIVOT`                                                | Not supported                                            |
+| Wildcard modifiers (`ILIKE`, `EXCLUDE`, `EXCEPT`, `REPLACE`, `RENAME` on `*`) | Not supported                                            |
+| Nested (parenthesized) joins                                                  | Not supported                                            |
+| `LATERAL` derived tables                                                      | Not supported                                            |
+| `LATERAL VIEW` / `QUALIFY`                                                    | Not supported                                            |
 
 ---
 
 ## Unsupported expression patterns
 
-| Pattern                               | Alternative                                                                                       |
-| :------------------------------------ | :------------------------------------------------------------------------------------------------ |
-| `func(DISTINCT ...)` on any aggregate | Use `approx_distinct` for counting                                                                |
-| `PERCENTILE_CONT` / `PERCENTILE_DISC` | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
-| `MEDIAN`                              | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
-| `ARRAY_AGG`                           | No alternative (unsupported for memory safety)                                                    |
-| `STRING_AGG`                          | No alternative (unsupported for memory safety)                                                    |
-| `NOT IN` subquery on nullable columns | Use `NOT EXISTS` with a correlated subquery instead                                               |
+| Pattern                                                 | Alternative                                                                                       |
+| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------ |
+| `func(DISTINCT ...)` on any aggregate                   | Use `approx_distinct` for counting                                                                |
+| `PERCENTILE_CONT` / `PERCENTILE_DISC`                   | Use [`approx_percentile_cont`](/r2-sql/sql-reference/aggregate-functions/#approx_percentile_cont) |
+| `MEDIAN`                                                | Use [`approx_median`](/r2-sql/sql-reference/aggregate-functions/#approx_median)                   |
+| `ARRAY_AGG`                                             | No alternative (unsupported for memory safety)                                                    |
+| `STRING_AGG`                                            | No alternative (unsupported for memory safety)                                                    |
+| `NOT IN` subquery on nullable columns                   | Use `NOT EXISTS` with a correlated subquery instead                                               |
 
 ---
 
 ## Runtime constraints
 
-| Constraint                           | Details                                                                                                                                                                                    |
-| :----------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Constraint                           | Details                                                                                               |
+| :----------------------------------- | :---------------------------------------------------------------------------------------------------- |
 | Multi-table queries                  | JOINs, subqueries (IN, EXISTS, scalar, derived tables), and multi-table CTEs are supported. Performance depends on intermediate result size; use WHERE filters to manage join selectivity. |
-| Partitioned and unpartitioned tables | Both partitioned and unpartitioned Iceberg tables are supported.                                                                                                                           |
-| Parquet format only                  | No CSV, JSON, or other formats.                                                                                                                                                            |
-| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                                                                                                       |
-| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                                                                                                            |
+| Partitioned and unpartitioned tables  | Both partitioned and unpartitioned Iceberg tables are supported.                                       |
+| Parquet format only                  | No CSV, JSON, or other formats.                                                                       |
+| Read-only                            | R2 SQL is a query engine, not a database. No writes.                                                  |
+| `now()` / `current_time()` precision | Quantized to 10ms boundaries and forced to UTC.                                                       |
 
 ---
 
diff --git a/src/content/docs/r2-sql/reference/wrangler-commands.mdx b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
index f9765698d06f77d..26a591c683434f5 100644
--- a/src/content/docs/r2-sql/reference/wrangler-commands.mdx
+++ b/src/content/docs/r2-sql/reference/wrangler-commands.mdx
@@ -10,4 +10,4 @@ products:
 
 import { Render, Type, MetaInfo } from "~/components";
 
-<Render file="wrangler-commands/r2-sql" product="workers" />
+<Render file="wrangler-commands/r2-sql" product="workers" />
\ No newline at end of file
diff --git a/src/content/docs/r2-sql/sql-reference/index.mdx b/src/content/docs/r2-sql/sql-reference/index.mdx
index 58ed3641062a224..70227b97d4db20a 100644
--- a/src/content/docs/r2-sql/sql-reference/index.mdx
+++ b/src/content/docs/r2-sql/sql-reference/index.mdx
@@ -194,14 +194,14 @@ R2 SQL supports joining multiple Iceberg tables in a single query. All join type
 
 ### Supported join types
 
-| Join type        | Syntax                            | Description                                                        |
-| :--------------- | :-------------------------------- | :----------------------------------------------------------------- |
-| Inner join       | `INNER JOIN ... ON`               | Returns rows that match in both tables                             |
-| Left outer join  | `LEFT JOIN ... ON`                | Returns all rows from the left table, NULLs for non-matching right |
-| Right outer join | `RIGHT JOIN ... ON`               | Returns all rows from the right table, NULLs for non-matching left |
-| Full outer join  | `FULL OUTER JOIN ... ON`          | Returns all rows from both tables, NULLs where no match            |
-| Cross join       | `CROSS JOIN`                      | Cartesian product of both tables                                   |
-| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id` | Comma-separated tables with join condition in `WHERE`              |
+| Join type        | Syntax                              | Description                                                        |
+| :--------------- | :---------------------------------- | :----------------------------------------------------------------- |
+| Inner join       | `INNER JOIN ... ON`                 | Returns rows that match in both tables                             |
+| Left outer join  | `LEFT JOIN ... ON`                  | Returns all rows from the left table, NULLs for non-matching right |
+| Right outer join | `RIGHT JOIN ... ON`                 | Returns all rows from the right table, NULLs for non-matching left |
+| Full outer join  | `FULL OUTER JOIN ... ON`            | Returns all rows from both tables, NULLs where no match            |
+| Cross join       | `CROSS JOIN`                        | Cartesian product of both tables                                   |
+| Implicit join    | `FROM t1, t2 WHERE t1.id = t2.id`  | Comma-separated tables with join condition in `WHERE`              |
 
 ### Syntax
 
@@ -264,7 +264,6 @@ SELECT * FROM (t1 JOIN t2 ON t1.id = t2.id) JOIN t3 ON t2.id = t3.id
 -- Supported
 SELECT * FROM t1 JOIN t2 ON t1.id = t2.id JOIN t3 ON t2.id = t3.id
 ```
-
 :::
 
 ### Best practices for joins
@@ -359,7 +358,6 @@ WHERE NOT EXISTS (
 )
 LIMIT 20
 ```
-
 :::
 
 ### `EXISTS` / `NOT EXISTS` subqueries
diff --git a/src/content/docs/r2/api/error-codes.mdx b/src/content/docs/r2/api/error-codes.mdx
index 27e9cbdf09979fb..49ec6f7e7bff0ec 100644
--- a/src/content/docs/r2/api/error-codes.mdx
+++ b/src/content/docs/r2/api/error-codes.mdx
@@ -16,10 +16,10 @@ For the **Workers API**, R2 operations throw exceptions that you can catch. The
 
 ```js
 try {
-	await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
+  await env.MY_BUCKET.put("my-key", data, { customMetadata: largeMetadata });
 } catch (error) {
-	console.error(error.message);
-	// "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
+  console.error(error.message);
+  // "put: Your metadata headers exceed the maximum allowed metadata size. (10012)"
 }
 ```
 
@@ -37,59 +37,59 @@ For the **S3-compatible API**, errors are returned as XML in the response body:
 
 ### Authentication and authorization errors
 
-| Error Code | S3 Code               | HTTP Status | Details                                                | Recommended Fix                                                                                         |
-| ---------- | --------------------- | ----------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
-| 10002      | Unauthorized          | 401         | Missing or invalid authentication credentials.         | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired.    |
-| 10003      | AccessDenied          | 403         | Insufficient permissions for the requested operation.  | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
-| 10018      | ExpiredRequest        | 400         | Presigned URL or request signature has expired.        | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature.                                |
-| 10035      | SignatureDoesNotMatch | 403         | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues.                            |
-| 10042      | NotEntitled           | 403         | Account not entitled to this feature.                  | Ensure your account has an [R2 subscription](/r2/pricing/).                                             |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10002 | Unauthorized | 401 | Missing or invalid authentication credentials. | Verify your [API token](/r2/api/tokens/) or access key credentials are correct and have not expired. |
+| 10003 | AccessDenied | 403 | Insufficient permissions for the requested operation. | Check that your [API token](/r2/api/tokens/) has the required permissions for the bucket and operation. |
+| 10018 | ExpiredRequest | 400 | Presigned URL or request signature has expired. | Regenerate the [presigned URL](/r2/api/s3/presigned-urls/) or signature. |
+| 10035 | SignatureDoesNotMatch | 403 | Request signature does not match calculated signature. | Verify your secret key and signing algorithm. Check for URL encoding issues. |
+| 10042 | NotEntitled | 403 | Account not entitled to this feature. | Ensure your account has an [R2 subscription](/r2/pricing/). |
 
 ### Bucket errors
 
-| Error Code | S3 Code           | HTTP Status | Details                                                     | Recommended Fix                                                                                       |
-| ---------- | ----------------- | ----------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| 10005      | InvalidBucketName | 400         | Bucket name does not meet naming requirements.              | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric.     |
-| 10006      | NoSuchBucket      | 404         | The specified bucket does not exist.                        | Verify the bucket name is correct and the bucket exists in your account.                              |
-| 10008      | BucketNotEmpty    | 409         | Cannot delete bucket that contains objects.                 | Delete all objects in the bucket before deleting the bucket.                                          |
-| 10009      | TooManyBuckets    | 400         | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
-| 10073      | BucketConflict    | 409         | Bucket name already exists.                                 | Choose a different bucket name. Bucket names must be unique within your account.                      |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10005 | InvalidBucketName | 400 | Bucket name does not meet naming requirements. | Bucket names must be 3-63 chars, lowercase alphanumeric and hyphens, start/end with alphanumeric. |
+| 10006 | NoSuchBucket | 404 | The specified bucket does not exist. | Verify the bucket name is correct and the bucket exists in your account. |
+| 10008 | BucketNotEmpty | 409 | Cannot delete bucket that contains objects. | Delete all objects in the bucket before deleting the bucket. |
+| 10009 | TooManyBuckets | 400 | Account bucket limit exceeded (default: 1,000,000 buckets). | Request a limit increase via the [Limits Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). |
+| 10073 | BucketConflict | 409 | Bucket name already exists. | Choose a different bucket name. Bucket names must be unique within your account. |
 
 ### Object errors
 
-| Error Code | S3 Code                    | HTTP Status | Details                                                                                                                                                         | Recommended Fix                                                                                                                   |
-| ---------- | -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| 10007      | NoSuchKey                  | 404         | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted.                                                             |
-| 10020      | InvalidObjectName          | 400         | Object key contains invalid characters or is too long.                                                                                                          | Use valid UTF-8 characters. Maximum key length is 1024 bytes.                                                                     |
-| 100100     | EntityTooLarge             | 400         | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart).                                                                                     | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
-| 10012      | MetadataTooLarge           | 400         | Custom metadata exceeds the 8,192 byte limit.                                                                                                                   | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata.                                                |
-| 10069      | ObjectLockedByBucketPolicy | 403         | Object is protected by a bucket lock rule and cannot be modified or deleted.                                                                                    | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/).                                      |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10007 | NoSuchKey | 404 | The specified object key does not exist. For the [Workers API](/r2/api/workers/workers-api-reference/), `get()` and `head()` return `null` instead of throwing. | Verify the object key is correct and the object has not been deleted. |
+| 10020 | InvalidObjectName | 400 | Object key contains invalid characters or is too long. | Use valid UTF-8 characters. Maximum key length is 1024 bytes. |
+| 100100 | EntityTooLarge | 400 | Object exceeds maximum size (5 GiB for single upload, 5 TiB for multipart). | Use [multipart upload](/r2/objects/upload-objects/#multipart-upload) for objects larger than 5 GiB. Maximum object size is 5 TiB. |
+| 10012 | MetadataTooLarge | 400 | Custom metadata exceeds the 8,192 byte limit. | Reduce custom metadata size. Maximum is 8,192 bytes total for all custom metadata. |
+| 10069 | ObjectLockedByBucketPolicy | 403 | Object is protected by a bucket lock rule and cannot be modified or deleted. | Wait for the retention period to expire. Refer to [bucket locks](/r2/buckets/bucket-locks/). |
 
 ### Upload and request errors
 
-| Error Code | S3 Code              | HTTP Status | Details                                                                           | Recommended Fix                                                                                                                                                                     |
-| ---------- | -------------------- | ----------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10033      | MissingContentLength | 411         | `Content-Length` header required but missing.                                     | Include the `Content-Length` header in PUT/POST requests.                                                                                                                           |
-| 10013      | IncompleteBody       | 400         | Request body terminated before expected `Content-Length`.                         | Ensure the full request body is sent. Check for network interruptions or client timeouts.                                                                                           |
-| 10014      | InvalidDigest        | 400         | Checksum header format is malformed.                                              | Ensure checksums are properly encoded (base64 for SHA/CRC checksums).                                                                                                               |
-| 10037      | BadDigest            | 400         | Provided checksum does not match the uploaded content.                            | Verify data integrity and retry the upload.                                                                                                                                         |
-| 10039      | InvalidRange         | 416         | Requested byte range is not satisfiable.                                          | Ensure the range start is less than object size. Check `Range` header format.                                                                                                       |
-| 10031      | PreconditionFailed   | 412         | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10033 | MissingContentLength | 411 | `Content-Length` header required but missing. | Include the `Content-Length` header in PUT/POST requests. |
+| 10013 | IncompleteBody | 400 | Request body terminated before expected `Content-Length`. | Ensure the full request body is sent. Check for network interruptions or client timeouts. |
+| 10014 | InvalidDigest | 400 | Checksum header format is malformed. | Ensure checksums are properly encoded (base64 for SHA/CRC checksums). |
+| 10037 | BadDigest | 400 | Provided checksum does not match the uploaded content. | Verify data integrity and retry the upload. |
+| 10039 | InvalidRange | 416 | Requested byte range is not satisfiable. | Ensure the range start is less than object size. Check `Range` header format. |
+| 10031 | PreconditionFailed | 412 | Conditional headers (`If-Match`, `If-Unmodified-Since`, etc.) were not satisfied. | Object's ETag or modification time does not match your condition. Refetch and retry. Refer to [conditional operations](/r2/api/s3/extensions/#conditional-operations-in-putobject). |
 
 ### Multipart upload errors
 
-| Error Code | S3 Code        | HTTP Status | Details                                                                 | Recommended Fix                                                                                                                                               |
-| ---------- | -------------- | ----------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 10011      | EntityTooSmall | 400         | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB.                                                                                                         |
-| 10024      | NoSuchUpload   | 404         | Multipart upload does not exist or was aborted.                         | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
-| 10025      | InvalidPart    | 400         | One or more parts could not be found when completing the upload.        | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`.                                                                 |
-| 10048      | InvalidPart    | 400         | All non-trailing parts must have the same size.                         | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads.                                                  |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10011 | EntityTooSmall | 400 | Multipart part is below minimum size (5 MiB), except for the last part. | Ensure each part (except the last) is at least 5 MiB. |
+| 10024 | NoSuchUpload | 404 | Multipart upload does not exist or was aborted. | Verify the `uploadId` is correct. By default, incomplete multipart uploads expire after 7 days. Refer to [object lifecycles](/r2/buckets/object-lifecycles/). |
+| 10025 | InvalidPart | 400 | One or more parts could not be found when completing the upload. | Verify each part was uploaded successfully and use the exact ETag returned from `UploadPart`. |
+| 10048 | InvalidPart | 400 | All non-trailing parts must have the same size. | Ensure all parts except the last have identical sizes. R2 requires uniform part sizes for multipart uploads. |
 
 ### Service errors
 
-| Error Code | S3 Code            | HTTP Status | Details                                                                                                                   | Recommended Fix                                                                                                   |
-| ---------- | ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| 10001      | InternalError      | 500         | An internal error occurred.                                                                                               | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
-| 10043      | ServiceUnavailable | 503         | Service is temporarily unavailable.                                                                                       | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com).                      |
-| 10054      | ClientDisconnect   | 400         | Client disconnected before request completed.                                                                             | Check network connectivity and retry.                                                                             |
-| 10058      | TooManyRequests    | 429         | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/).               |
+| Error Code | S3 Code | HTTP Status | Details | Recommended Fix |
+|------------|------|-------------|---------|-----------------|
+| 10001 | InternalError | 500 | An internal error occurred. | Retry the request. If persistent, check [Cloudflare Status](https://www.cloudflarestatus.com) or contact support. |
+| 10043 | ServiceUnavailable | 503 | Service is temporarily unavailable. | Retry with exponential backoff. Check [Cloudflare Status](https://www.cloudflarestatus.com). |
+| 10054 | ClientDisconnect | 400 | Client disconnected before request completed. | Check network connectivity and retry. |
+| 10058 | TooManyRequests | 429 | Rate limit exceeded. Often caused by multiple concurrent requests to the same object key (limit: 1 write/second per key). | Check if multiple clients are accessing the same object key. See [R2 limits](/r2/platform/limits/). |
diff --git a/src/content/docs/r2/api/index.mdx b/src/content/docs/r2/api/index.mdx
index c7113b1969a8c64..ea9d2d32f1163c9 100644
--- a/src/content/docs/r2/api/index.mdx
+++ b/src/content/docs/r2/api/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 R2 provides three API surfaces for interacting with your data:
 
diff --git a/src/content/docs/r2/api/s3/extensions.mdx b/src/content/docs/r2/api/s3/extensions.mdx
index 3d837887f7d5b66..79016396a6a9091 100644
--- a/src/content/docs/r2/api/s3/extensions.mdx
+++ b/src/content/docs/r2/api/s3/extensions.mdx
@@ -16,11 +16,13 @@ HTTP header names and values may only contain ASCII characters, which is a small
 
 :::caution[Metadata variance]
 
-Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted.
+Be mindful when using both Workers and S3 API endpoints to access the same data. If the R2 metadata keys contain Unicode, they are stripped when accessed through the S3 API and the `x-amz-missing-meta` header is set to the number of keys that were omitted. 
 :::
 
 These headers map to the `httpMetadata` field in the [R2 bindings](/workers/runtime-apis/bindings/):
 
+
+
 | HTTP Header           | Property Name                     |
 | --------------------- | --------------------------------- |
 | `Content-Encoding`    | `httpMetadata.contentEncoding`    |
@@ -71,6 +73,8 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 `ListBuckets` supports all the same search parameters as `ListObjectsV2` in R2 because some customers may have more than 1,000 buckets. Because tooling, like existing S3 libraries, may not expose a way to set these search parameters, these values may also be sent in via headers. Values in headers take precedence over the search parameters.
 
+
+
 | Search parameter     | HTTP Header             | Meaning                                                           |
 | -------------------- | ----------------------- | ----------------------------------------------------------------- |
 | `prefix`             | `cf-prefix`             | Show buckets with this prefix only.                               |
@@ -81,6 +85,8 @@ The `x-amz-metadata-directive` allows a `MERGE` value, in addition to the standa
 
 The XML response contains a `NextContinuationToken` and `IsTruncated` elements as appropriate. Since these may not be accessible from existing S3 APIs, these are also available in response headers:
 
+
+
 | XML Response Element    | HTTP Response Header         | Meaning                                                                                        |
 | ----------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------- |
 | `IsTruncated`           | `cf-is-truncated`            | This is set to `true` if the list of buckets returned is not all the buckets on the account.   |
@@ -95,15 +101,15 @@ The XML response contains a `NextContinuationToken` and `IsTruncated` elements a
 
 :::note
 
-This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81).
+This feature is currently in beta. If you have feedback, reach out to us on the [Cloudflare Developer Discord](https://discord.cloudflare.com) in the #r2-storage channel or open a thread on the [Community Forum](https://community.cloudflare.com/c/developers/storage/81). 
 :::
 
 `CopyObject` already supports conditions that relate to the source object through the `x-amz-copy-source-if-...` headers as part of our compliance with the S3 API. In addition to this, R2 supports an R2 specific set of headers that allow the `CopyObject` operation to be conditional on the target object:
 
-- `cf-copy-destination-if-match`
-- `cf-copy-destination-if-none-match`
-- `cf-copy-destination-if-modified-since`
-- `cf-copy-destination-if-unmodified-since`
+* `cf-copy-destination-if-match`
+* `cf-copy-destination-if-none-match`
+* `cf-copy-destination-if-modified-since`
+* `cf-copy-destination-if-unmodified-since`
 
 These headers work akin to the similarly named conditional headers supported on `PutObject`. When the preceding state of the destination object to does not match the specified conditions the `CopyObject` operation will be rejected with a `412 PreconditionFailed` error code.
 
diff --git a/src/content/docs/r2/api/s3/presigned-urls.mdx b/src/content/docs/r2/api/s3/presigned-urls.mdx
index bda593cdc55a82e..4b4c1fc51449c91 100644
--- a/src/content/docs/r2/api/s3/presigned-urls.mdx
+++ b/src/content/docs/r2/api/s3/presigned-urls.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { Tabs, TabItem, LinkCard } from "~/components";
+import {Tabs, TabItem, LinkCard } from "~/components";
 
 Presigned URLs are an [S3 concept](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) for granting temporary access to objects without exposing your API credentials. A presigned URL includes signature parameters in the URL itself, authorizing anyone with the URL to perform a specific operation (like `GetObject` or `PutObject`) on a specific object until the URL expires.
 
@@ -24,10 +24,10 @@ Presigned URLs are generated client-side with no communication with R2, requirin
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern                                                    | Grants                                                                                                         | Good for                                                                                                                   |
-| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Presigned URLs (this page)                                 | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
-| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
+| Pattern | Grants | Good for |
+| --- | --- | --- |
+| Presigned URLs (this page) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| [Temporary credentials](/r2/api/s3/temporary-credentials/) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
 
 ## Generate a presigned URL
 
@@ -136,7 +136,6 @@ aws s3 presign --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com \
 </Tabs>
 
 For complete examples and additional operations, refer to the SDK-specific documentation:
-
 - [AWS SDK for JavaScript](/r2/examples/aws/aws-sdk-js-v3/#generate-presigned-urls)
 - [AWS SDK for Python (Boto3)](/r2/examples/aws/boto3/#generate-presigned-urls)
 - [AWS CLI](/r2/examples/aws/aws-cli/#generate-presigned-urls)
diff --git a/src/content/docs/r2/api/s3/temporary-credentials.mdx b/src/content/docs/r2/api/s3/temporary-credentials.mdx
index 42a48a5428e8ec4..eabe88c5d475d9f 100644
--- a/src/content/docs/r2/api/s3/temporary-credentials.mdx
+++ b/src/content/docs/r2/api/s3/temporary-credentials.mdx
@@ -16,10 +16,10 @@ Use temporary credentials to delegate access without issuing a long-lived token.
 
 R2 supports two patterns for time-limited access. They overlap but have different trade-offs:
 
-| Pattern                                      | Grants                                                                                                         | Good for                                                                                                                   |
-| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Temporary credentials (this page)            | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session                            |
-| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object                                                                       | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
+| Pattern | Grants | Good for |
+| --- | --- | --- |
+| Temporary credentials (this page) | Multiple S3 operations, scoped to a bucket and a set of permitted operations, and optionally to specific paths | Callers that use a standard S3 client or SDK to perform multiple operations in a scoped session |
+| [Presigned URLs](/r2/api/s3/presigned-urls/) | A single S3 operation on a single object | Granting direct HTTP access to a single object without an S3 client, such as a browser upload or a shareable download link |
 
 ## Generate temporary credentials
 
@@ -108,11 +108,11 @@ For example, `actions: ["GetObject", "HeadObject"]` grants read of individual ob
 
 Valid actions:
 
-| Category  | Actions                                                                                                               |
-| --------- | --------------------------------------------------------------------------------------------------------------------- |
-| Read      | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
-| Write     | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject`                                                            |
-| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload`            |
+| Category | Actions |
+| --- | --- |
+| Read | `HeadObject`, `GetObject`, `GetBucketLocation`, `ListObjectsV1`, `ListObjectsV2`, `ListMultipartUploads`, `ListParts` |
+| Write | `PutObject`, `DeleteObject`, `DeleteObjects`, `CopyObject` |
+| Multipart | `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `AbortMultipartUpload`, `CompleteMultipartUpload` |
 
 ### Paths
 
@@ -122,8 +122,8 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-	"prefixes": ["uploads/user-123/"],
-	"objects": ["shared/manifest.json"],
+  "prefixes": ["uploads/user-123/"],
+  "objects": ["shared/manifest.json"]
 }
 ```
 
@@ -131,10 +131,10 @@ Restrict access to specific prefixes or objects within the bucket. Omit these fi
 
 ```jsonc
 {
-	"paths": {
-		"prefixPaths": ["uploads/user-123/"],
-		"objectPaths": ["shared/manifest.json"],
-	},
+  "paths": {
+    "prefixPaths": ["uploads/user-123/"],
+    "objectPaths": ["shared/manifest.json"]
+  }
 }
 ```
 
@@ -205,25 +205,25 @@ Treat temporary credentials as bearer tokens. Anyone in possession of all three
 ## Related resources
 
 <LinkCard
-	title="Authenticate against R2 with temporary credentials"
-	href="/r2/examples/authenticate-r2-temp-credentials/"
-	description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
+  title="Authenticate against R2 with temporary credentials"
+  href="/r2/examples/authenticate-r2-temp-credentials/"
+  description="End-to-end examples for both the Temporary Credentials API and local JWT signing."
 />
 
 <LinkCard
-	title="Presigned URLs"
-	href="/r2/api/s3/presigned-urls/"
-	description="Grant single-operation access to a specific object without issuing credentials."
+  title="Presigned URLs"
+  href="/r2/api/s3/presigned-urls/"
+  description="Grant single-operation access to a specific object without issuing credentials."
 />
 
 <LinkCard
-	title="R2 API tokens"
-	href="/r2/api/tokens/"
-	description="Create the parent token that temporary credentials derive from."
+  title="R2 API tokens"
+  href="/r2/api/tokens/"
+  description="Create the parent token that temporary credentials derive from."
 />
 
 <LinkCard
-	title="Error codes"
-	href="/r2/api/error-codes/"
-	description="Authentication and authorization error codes returned by R2."
+  title="Error codes"
+  href="/r2/api/error-codes/"
+  description="Authentication and authorization error codes returned by R2."
 />
diff --git a/src/content/docs/r2/api/workers/workers-api-reference.mdx b/src/content/docs/r2/api/workers/workers-api-reference.mdx
index d60ffa3b2d79709..b7489165a08ccee 100644
--- a/src/content/docs/r2/api/workers/workers-api-reference.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-reference.mdx
@@ -103,33 +103,40 @@ class Default(WorkerEntrypoint):
 </Tabs>
 
 - `head` <Type text="(key: string): Promise<R2Object | null>" />
+
   - Retrieves the `R2Object` for the given key containing only object metadata, if the key exists, and `null` if the key does not exist.
 
 - `get` <Type text="(key: string, options?: R2GetOptions): Promise<R2ObjectBody | R2Object | null>" />
+
   - Retrieves the `R2ObjectBody` for the given key containing object metadata and the object body as a <code>ReadableStream</code>, if the key exists, and `null` if the key does not exist.
   - In the event that a precondition specified in <code>options</code> fails, <code>get()</code> returns an <code>R2Object</code> with <code>body</code> undefined.
 
 - `put` <Type text="(key: string, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | null | Blob, options?: R2PutOptions): Promise<R2Object | null>" />
+
   - Stores the given <code>value</code> and metadata under the associated <code>key</code>. Once the write succeeds, returns an `R2Object` containing metadata about the stored Object.
   - In the event that a precondition specified in <code>options</code> fails, <code>put()</code> returns `null`, and the object will not be stored.
   - R2 writes are strongly consistent. Once the Promise resolves, all subsequent read operations will see this key value pair globally.
 
 - `delete` <Type text="(key: string | string[]): Promise<void>" />
+
   - Deletes the given <code>values</code> and metadata under the associated <code>keys</code>. Once the delete succeeds, returns <code>void</code>.
   - R2 deletes are strongly consistent. Once the Promise resolves, all subsequent read operations will no longer see the provided key value pairs globally.
   - Up to 1000 keys may be deleted per call.
 
 - `list` <Type text="(options?: R2ListOptions): Promise<R2Objects>" />
-  - Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
-  - The returned list of objects is ordered lexicographically.
-  - Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
-  - To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
+
+  * Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
+  * The returned list of objects is ordered lexicographically.
+  * Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
+  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
 
 * `createMultipartUpload` <Type text="(key: string, options?: R2MultipartOptions): Promise<R2MultipartUpload>" />
+
   - Creates a multipart upload.
   - Returns Promise which resolves to an `R2MultipartUpload` object representing the newly created multipart upload. Once the multipart upload has been created, the multipart upload can be immediately interacted with globally, either through the Workers API, or through the S3 API.
 
 - `resumeMultipartUpload` <Type text="(key: string, uploadId: string): R2MultipartUpload" />
+
   - Returns an object representing a multipart upload with the given key and uploadId.
   - The resumeMultipartUpload operation does not perform any checks to ensure the validity of the uploadId, nor does it verify the existence of a corresponding active multipart upload. This is done to minimize latency before being able to call subsequent operations on the `R2MultipartUpload` object.
 
@@ -138,12 +145,15 @@ class Default(WorkerEntrypoint):
 `R2Object` is created when you `PUT` an object into an R2 bucket. `R2Object` represents the metadata of an object based on the information provided by the uploader. Every object that you `PUT` into an R2 bucket will have an `R2Object` created.
 
 - `key` <Type text="string" />
+
   - The object's key.
 
 - `version` <Type text="string" />
+
   - Random unique string associated with a specific upload of a key.
 
 - `size` <Type text="number" />
+
   - Size of the object in bytes.
 
 - `etag` <Type text="string" />
@@ -156,30 +166,39 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 - The etag associated with the object upload.
 
 - `httpEtag` <Type text="string" />
+
   - The object's etag, in quotes so as to be returned as a header.
 
 - `uploaded` <Type text="Date" />
+
   - A Date object representing the time the object was uploaded.
 
 - `httpMetadata` <Type text="R2HTTPMetadata" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" />
+
   - A map of custom, user-defined metadata associated with the object.
 
 - `range` <Type text="R2Range" />
+
   - A `R2Range` object containing the returned range of the object.
 
 - `checksums` <Type text="R2Checksums" />
+
   - A `R2Checksums` object containing the stored checksums of the object. Refer to [checksums](#checksums).
 
 - `writeHttpMetadata` <Type text="(headers: Headers): void" />
+
   - Retrieves the `httpMetadata` from the `R2Object` and applies their corresponding HTTP headers to the `Headers` input object. Refer to [HTTP Metadata](#http-metadata).
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
+
   - The storage class associated with the object. Refer to [Storage Classes](#storage-class).
 
 - `ssecKeyMd5` <Type text="string" />
+
   - Hex-encoded MD5 hash of the [SSE-C](/r2/examples/ssec) key used for encryption (if one was provided). Hash can be used to identify which key is needed to decrypt object.
 
 ## `R2ObjectBody` definition
@@ -187,21 +206,27 @@ Cloudflare recommends using the `httpEtag` field when returning an etag in a res
 `R2ObjectBody` represents an object's metadata combined with its body. It is returned when you `GET` an object from an R2 bucket. The full list of keys for `R2ObjectBody` includes the list below and all keys inherited from [`R2Object`](#r2object-definition).
 
 - `body` <Type text="ReadableStream" />
+
   - The object's value.
 
 - `bodyUsed` <Type text="boolean" />
+
   - Whether the object's value has been consumed or not.
 
 - `arrayBuffer` <Type text="(): Promise<ArrayBuffer>" />
+
   - Returns a Promise that resolves to an `ArrayBuffer` containing the object's value.
 
 - `text` <Type text="(): Promise<string>" />
+
   - Returns a Promise that resolves to an string containing the object's value.
 
 - `json` <Type text="<T>() : Promise<T>" />
+
   - Returns a Promise that resolves to the given object containing the object's value.
 
 - `blob` <Type text="(): Promise<Blob>" />
+
   - Returns a Promise that resolves to a binary Blob containing the object's value.
 
 ## `R2MultipartUpload` definition
@@ -219,19 +244,24 @@ A multipart upload can be completed or aborted at any time, either through the S
 :::
 
 - `key` <Type text="string" />
+
   - The `key` for the multipart upload.
 
 - `uploadId` <Type text="string" />
+
   - The `uploadId` for the multipart upload.
 
 - `uploadPart` <Type text="(partNumber: number, value: ReadableStream | ArrayBuffer | ArrayBufferView | string | Blob, options?: R2MultipartOptions): Promise<R2UploadedPart>" />
+
   - Uploads a single part with the specified part number to this multipart upload. Each part must be uniform in size with an exception for the final part which can be smaller.
   - Returns an `R2UploadedPart` object containing the `etag` and `partNumber`. These `R2UploadedPart` objects are required when completing the multipart upload.
 
 - `abort` <Type text="(): Promise<void>" />
+
   - Aborts the multipart upload. Returns a Promise that resolves when the upload has been successfully aborted.
 
 - `complete` <Type text="(uploadedParts: R2UploadedPart[]): Promise<R2Object>" />
+
   - Completes the multipart upload with the given parts.
   - Returns a Promise that resolves when the complete operation has finished. Once this happens, the object is immediately accessible globally by any subsequent read operation.
 
@@ -240,12 +270,15 @@ A multipart upload can be completed or aborted at any time, either through the S
 ### R2GetOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
+
   - Specifies that the object should only be returned given satisfaction of certain conditions in the `R2Conditional` or in the conditional Headers. Refer to [Conditional operations](#conditional-operations).
 
 - `range` <Type text="R2Range" />
+
   - Specifies that only a specific length (from an optional offset) or suffix of bytes from the object should be returned. Refer to [Ranged reads](#ranged-reads).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 #### Ranged reads
@@ -259,23 +292,29 @@ There are 3 variations of arguments that can be used in a range:
 - A suffix.
 
 - `offset` <Type text="number" />
+
   - The byte to begin returning data from, inclusive.
 
 - `length` <Type text="number" />
+
   - The number of bytes to return. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 - `suffix` <Type text="number" />
+
   - The number of bytes to return from the end of the file, starting from the last byte. If more bytes are requested than exist in the object, fewer bytes than this number may be returned.
 
 ### R2PutOptions
 
 - `onlyIf` <Type text="R2Conditional | Headers" />
+
   - Specifies that the object should only be stored given satisfaction of certain conditions in the `R2Conditional`. Refer to [Conditional operations](#conditional-operations).
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
+
   - A map of custom, user-defined metadata that will be stored with the object.
 
 :::note
@@ -285,57 +324,73 @@ Only a single hashing algorithm can be specified at once.
 :::
 
 - `md5` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A md5 hash to use to check the received object's integrity.
 
 - `sha1` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-1 hash to use to check the received object's integrity.
 
 - `sha256` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-256 hash to use to check the received object's integrity.
 
 - `sha384` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-384 hash to use to check the received object's integrity.
 
 - `sha512` <Type text="ArrayBuffer | string" /> <MetaInfo text="optional" />
+
   - A SHA-512 hash to use to check the received object's integrity.
 
 - `storageClass` <Type text="'Standard' | 'InfrequentAccess'" />
+
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2MultipartOptions
 
 - `httpMetadata` <Type text="R2HTTPMetadata | Headers" /> <MetaInfo text="optional" />
+
   - Various HTTP headers associated with the object. Refer to [HTTP Metadata](#http-metadata).
 
 - `customMetadata` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
+
   - A map of custom, user-defined metadata that will be stored with the object.
 
 - `storageClass` <Type text="string" />
+
   - Sets the storage class of the object if provided. Otherwise, the object will be stored in the default storage class associated with the bucket. Refer to [Storage Classes](#storage-class).
 
 - `ssecKey` <Type text="ArrayBuffer | string" />
+
   - Specifies a key to be used for [SSE-C](/r2/examples/ssec). Key must be 32 bytes in length, in the form of a hex-encoded string or an ArrayBuffer.
 
 ### R2ListOptions
 
 - `limit` <Type text="number" /> <MetaInfo text="optional" />
+
   - The number of results to return. Defaults to `1000`, with a maximum of `1000`.
 
   - If `include` is set, you may receive fewer than `limit` results in your response to accommodate metadata.
 
 - `prefix` <Type text="string" /> <MetaInfo text="optional" />
+
   - The prefix to match keys against. Keys will only be returned if they start with given prefix.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
+
   - An opaque token that indicates where to continue listing objects from. A cursor can be retrieved from a previous list operation.
 
 - `delimiter` <Type text="string" /> <MetaInfo text="optional" />
+
   - The character to use when grouping keys.
 
 - `include` <Type text="Array<string>" /> <MetaInfo text="optional" />
+
   - Can include `httpMetadata` and/or `customMetadata`. If included, items returned by the list will include the specified metadata.
 
   - Note that there is a limit on the total amount of data that a single `list` operation can return. If you request data, you may receive fewer than `limit` results in your response to accommodate metadata.
@@ -380,15 +435,19 @@ while (truncated) {
 An object containing an `R2Object` array, returned by `BUCKET_BINDING.list()`.
 
 - `objects` <Type text="Array<R2Object>" />
+
   - An array of objects matching the `list` request.
 
 - `truncated` boolean
+
   - If true, indicates there are more results to be retrieved for the current `list` request.
 
 - `cursor` <Type text="string" /> <MetaInfo text="optional" />
+
   - A token that can be passed to future `list` calls to resume listing from that point. Only present if truncated is true.
 
 - `delimitedPrefixes` <Type text="Array<string>" />
+
   - If a delimiter has been specified, contains all prefixes between the specified prefix and the next occurrence of the delimiter.
 
   - For example, if no prefix is provided and the delimiter is '/', `foo/bar/baz` would return `foo` as a delimited prefix. If `foo/` was passed as a prefix with the same structure and delimiter, `foo/bar` would be returned as a delimited prefix.
@@ -400,15 +459,19 @@ You can pass an `R2Conditional` object to `R2GetOptions` and `R2PutOptions`. If
 If the condition check for `put()` fails, `null` will be returned instead of the `R2Object`.
 
 - `etagMatches` <Type text="string" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object's etag matches the given string.
 
 - `etagDoesNotMatch` <Type text="string" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object's etag does not match the given string.
 
 - `uploadedBefore` <Type text="Date" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object was uploaded before the given date.
 
 - `uploadedAfter` <Type text="Date" /> <MetaInfo text="optional" />
+
   - Performs the operation if the object was uploaded after the given date.
 
 Alternatively, you can pass a `Headers` object containing conditional headers to `R2GetOptions` and `R2PutOptions`. For information on these conditional headers, refer to [the MDN docs on conditional requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditional_requests#conditional_headers). All conditional headers aside from `If-Range` are supported.
@@ -436,18 +499,23 @@ Generally, these fields match the HTTP metadata passed when the object was creat
 If a checksum was provided when using the `put()` binding, it will be available on the returned object under the `checksums` property. The MD5 checksum will be included by default for non-multipart objects.
 
 - `md5` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The MD5 checksum of the object.
 
 - `sha1` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-1 checksum of the object.
 
 - `sha256` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-256 checksum of the object.
 
 - `sha384` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-384 checksum of the object.
 
 - `sha512` <Type text="ArrayBuffer" /> <MetaInfo text="optional" />
+
   - The SHA-512 checksum of the object.
 
 ### `R2UploadedPart`
@@ -455,9 +523,11 @@ If a checksum was provided when using the `put()` binding, it will be available
 An `R2UploadedPart` object represents a part that has been uploaded. `R2UploadedPart` objects are returned from `uploadPart` operations and must be passed to `completeMultipartUpload` operations.
 
 - `partNumber` <Type text="number" />
+
   - The number of the part.
 
 - `etag` <Type text="string" />
+
   - The `etag` of the part.
 
 ### Storage Class
diff --git a/src/content/docs/r2/api/workers/workers-api-usage.mdx b/src/content/docs/r2/api/workers/workers-api-usage.mdx
index 3201040184b441e..6cfb3742ecf0dbe 100644
--- a/src/content/docs/r2/api/workers/workers-api-usage.mdx
+++ b/src/content/docs/r2/api/workers/workers-api-usage.mdx
@@ -251,7 +251,6 @@ class Default(WorkerEntrypoint):
 ```
 </TabItem>
 </Tabs>
-
 <Render file="request-dot-clone-warning" product="workers" />
 
 ## 5. Bucket access and privacy
diff --git a/src/content/docs/r2/buckets/bucket-locks.mdx b/src/content/docs/r2/buckets/bucket-locks.mdx
index d7bcec562a81685..464a1623fef1b18 100644
--- a/src/content/docs/r2/buckets/bucket-locks.mdx
+++ b/src/content/docs/r2/buckets/bucket-locks.mdx
@@ -22,7 +22,6 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Select **Add rule** and enter the rule name, prefix, and retention period.
@@ -98,7 +97,6 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 
@@ -121,7 +119,6 @@ For more information on required parameters and examples of how to get bucket lo
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you would like to add bucket lock rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Bucket lock rules** card.
 4. Locate the rule you want to remove, select the `...` icon next to it, and then select **Delete**.
diff --git a/src/content/docs/r2/buckets/cors.mdx b/src/content/docs/r2/buckets/cors.mdx
index e377d4c3587d41b..509574538198e4b 100644
--- a/src/content/docs/r2/buckets/cors.mdx
+++ b/src/content/docs/r2/buckets/cors.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) is a standardized method that prevents domain X from accessing the resources of domain Y. It does so by using special headers in HTTP responses from domain Y, that allow your browser to verify that domain Y permits domain X to access these resources.
 
@@ -56,13 +56,13 @@ The following example allows browser-based uploads from `https://example.com` wi
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -83,7 +83,6 @@ If you set a CORS policy on a bucket that is already serving traffic using a cus
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. Select **Settings**.
 4. Under **CORS Policy**, select **Add CORS policy**.
@@ -100,14 +99,14 @@ You can configure CORS rules using the [Wrangler CLI](/r2/reference/wrangler-com
 
 ```json title="cors.json"
 {
-	"rules": [
-		{
-			"allowed": {
-				"origins": ["https://example.com"],
-				"methods": ["GET"]
-			}
-		}
-	]
+  "rules": [
+    {
+      "allowed": {
+        "origins": ["https://example.com"],
+        "methods": ["GET"]
+      }
+    }
+  ]
 }
 ```
 
@@ -127,13 +126,13 @@ npx wrangler r2 bucket cors list <BUCKET_NAME>
 
 The following fields in an R2 CORS policy map to HTTP response headers. These response headers are only returned when the incoming HTTP request is a valid CORS request.
 
-| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                                     | Example                                                                                                                                                                                                                              |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                    | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
-| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                                   | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
-| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                          | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
+| Field Name       | Description                                                                                                                                                                                                                                                                                                                                                           | Example                                                                                                                                                                                                                              |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `AllowedOrigins` | Specifies the value for the `Access-Control-Allow-Origin` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                          | If a website at `www.test.com` needs to access resources (e.g. fonts, scripts) on a [custom domain](/r2/buckets/public-buckets/#custom-domains) of `static.example.com`, you would set `https://www.test.com` as an `AllowedOrigin`. |
+| `AllowedMethods` | Specifies the value for the `Access-Control-Allow-Methods` header R2 sets when requesting objects in a bucket from a browser.                                                                                                                                                                                                                                         | `GET`, `POST`, `PUT`                                                                                                                                                                                                                 |
+| `AllowedHeaders` | Specifies the value for the `Access-Control-Allow-Headers` header R2 sets when requesting objects in this bucket from a browser.Cross-origin requests that include custom headers (e.g. `x-user-id`) should specify these headers as `AllowedHeaders`.                                                                                                                | `x-requested-by`, `User-Agent`                                                                                                                                                                                                       |
 | `ExposeHeaders`  | Specifies the headers that can be exposed back, and accessed by, the JavaScript making the cross-origin request. If you need to access headers beyond the [safelisted response headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers#examples), such as `Content-Encoding` or `cf-cache-status`, you must specify it here. | `Content-Encoding`, `cf-cache-status`, `Date`                                                                                                                                                                                        |
-| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                                   | `3600`                                                                                                                                                                                                                               |
+| `MaxAgeSeconds`  | Specifies the amount of time (in seconds) browsers are allowed to cache CORS preflight responses. Browsers may limit this to 2 hours or less, even if the maximum value (86400) is specified.                                                                                                                                                                         | `3600`                                                                                                                                                                                                                               |
 
 ## Example
 
diff --git a/src/content/docs/r2/buckets/delete-buckets.mdx b/src/content/docs/r2/buckets/delete-buckets.mdx
index 71cdbc593f9c6e8..cae21c981e67944 100644
--- a/src/content/docs/r2/buckets/delete-buckets.mdx
+++ b/src/content/docs/r2/buckets/delete-buckets.mdx
@@ -27,7 +27,6 @@ The dashboard provides an **Empty Bucket** action that handles this for you, reg
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you want to empty.
 3. Go to the **Settings** tab.
 4. Scroll to the **Empty Bucket** section.
@@ -87,7 +86,6 @@ You can delete a bucket in various ways.
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you want to delete.
 3. Go to the **Settings** tab.
 4. Scroll to the **Delete Bucket** section. If the bucket is not empty, select **Empty Bucket** first to clear all objects.
@@ -131,25 +129,25 @@ curl -X DELETE "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/r2/bu
 ## Related resources
 
 <LinkCard
-	title="Delete objects"
-	href="/r2/objects/delete-objects/"
-	description="Delete individual objects or folders from an R2 bucket."
+  title="Delete objects"
+  href="/r2/objects/delete-objects/"
+  description="Delete individual objects or folders from an R2 bucket."
 />
 
 <LinkCard
-	title="Bucket locks"
-	href="/r2/buckets/bucket-locks/"
-	description="Prevent accidental deletion by setting retention policies on objects."
+  title="Bucket locks"
+  href="/r2/buckets/bucket-locks/"
+  description="Prevent accidental deletion by setting retention policies on objects."
 />
 
 <LinkCard
-	title="Object lifecycles"
-	href="/r2/buckets/object-lifecycles/"
-	description="Automatically expire objects after a specified period instead of emptying manually."
+  title="Object lifecycles"
+  href="/r2/buckets/object-lifecycles/"
+  description="Automatically expire objects after a specified period instead of emptying manually."
 />
 
 <LinkCard
-	title="Create buckets"
-	href="/r2/buckets/create-buckets/"
-	description="Create a new R2 bucket after deleting an existing one."
+  title="Create buckets"
+  href="/r2/buckets/create-buckets/"
+  description="Create a new R2 bucket after deleting an existing one."
 />
diff --git a/src/content/docs/r2/buckets/event-notifications.mdx b/src/content/docs/r2/buckets/event-notifications.mdx
index e910f9b896e6223..b0fe30eb775ad6f 100644
--- a/src/content/docs/r2/buckets/event-notifications.mdx
+++ b/src/content/docs/r2/buckets/event-notifications.mdx
@@ -26,7 +26,6 @@ Before getting started, you will need:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select the bucket you'd like to add an event notification rule to.
 3. Switch to the **Settings** tab, then scroll down to the **Event notifications** card.
 4. Select **Add notification** and choose the queue you'd like to receive notifications and the [type of events](/r2/buckets/event-notifications/#event-types) that will trigger them.
@@ -67,10 +66,10 @@ Event notification rules determine the [event types](/r2/buckets/event-notificat
 
 ## Event types
 
-| Event type      | Description                                                                 | Trigger actions                                                                      |
-| --------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| Event type | Description | Trigger actions |
+|------------|-------------|----------------|
 | `object-create` | Triggered when new objects are created or existing objects are overwritten. | <ul><li>`PutObject`</li><li>`CopyObject`</li><li>`CompleteMultipartUpload`</li></ul> |
-| `object-delete` | Triggered when an object is explicitly removed from the bucket.             | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul>                         |
+| `object-delete` | Triggered when an object is explicitly removed from the bucket. | <ul><li>`DeleteObject`</li><li>`LifecycleDeletion`</li></ul> |
 
 ## Message format
 
@@ -96,19 +95,19 @@ Queue consumers receive notifications as [Messages](/queues/configuration/javasc
 
 ### Properties
 
-| Property            | Type   | Description                                                                                                                                              |
-| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `account`           | String | The Cloudflare account ID that the event is associated with.                                                                                             |
-| `action`            | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
-| `bucket`            | String | The name of the bucket where the event occurred.                                                                                                         |
-| `object`            | Object | A nested object containing details about the object involved in the event.                                                                               |
-| `object.key`        | String | The key (or name) of the object within the bucket.                                                                                                       |
-| `object.size`       | Number | The size of the object in bytes. Note: not present for object-delete events.                                                                             |
-| `object.eTag`       | String | The entity tag (eTag) of the object. Note: not present for object-delete events.                                                                         |
-| `eventTime`         | String | The time when the action that triggered the event occurred.                                                                                              |
-| `copySource`        | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`.                         |
-| `copySource.bucket` | String | The bucket that contained the source object.                                                                                                             |
-| `copySource.object` | String | The name of the source object.                                                                                                                           |
+| Property | Type | Description |
+|----------|------|-------------|
+| `account` | String | The Cloudflare account ID that the event is associated with. |
+| `action` | String | The type of action that triggered the event notification. Example actions include: `PutObject`, `CopyObject`, `CompleteMultipartUpload`, `DeleteObject`. |
+| `bucket` | String | The name of the bucket where the event occurred. |
+| `object` | Object | A nested object containing details about the object involved in the event. |
+| `object.key` | String | The key (or name) of the object within the bucket. |
+| `object.size` | Number | The size of the object in bytes. Note: not present for object-delete events. |
+| `object.eTag` | String | The entity tag (eTag) of the object. Note: not present for object-delete events. |
+| `eventTime` | String | The time when the action that triggered the event occurred. |
+| `copySource` | Object | A nested object containing details about the source of a copied object. Note: only present for events triggered by `CopyObject`. |
+| `copySource.bucket` | String | The bucket that contained the source object. |
+| `copySource.object` | String | The name of the source object. |
 
 ## Notes
 
diff --git a/src/content/docs/r2/buckets/index.mdx b/src/content/docs/r2/buckets/index.mdx
index 56bda3ed5e0d4ce..6b32cf898b1518c 100644
--- a/src/content/docs/r2/buckets/index.mdx
+++ b/src/content/docs/r2/buckets/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 With object storage, all of your objects are stored in buckets. Buckets do not contain folders that group the individual files, but instead, buckets have a flat structure which simplifies the way you access and retrieve the objects in your bucket.
 
diff --git a/src/content/docs/r2/buckets/object-lifecycles.mdx b/src/content/docs/r2/buckets/object-lifecycles.mdx
index 0eaef01b4fefed0..8aa7719e17e7b1a 100644
--- a/src/content/docs/r2/buckets/object-lifecycles.mdx
+++ b/src/content/docs/r2/buckets/object-lifecycles.mdx
@@ -35,7 +35,6 @@ When you create an object lifecycle rule, you can specify which prefix you would
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object Lifecycle Rules**, select **Add rule**.
@@ -187,7 +186,6 @@ console.log(
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Locate and select your bucket from the list.
 3. From the bucket page, select **Settings**.
 4. Under **Object lifecycle rules**, select the rules you would like to delete.
diff --git a/src/content/docs/r2/buckets/storage-classes.mdx b/src/content/docs/r2/buckets/storage-classes.mdx
index 329e212d619b99e..d26bd2b34d5a359 100644
--- a/src/content/docs/r2/buckets/storage-classes.mdx
+++ b/src/content/docs/r2/buckets/storage-classes.mdx
@@ -6,22 +6,22 @@ products:
   - r2
 ---
 
-import { Badge, Tabs, TabItem } from "~/components";
+import { Badge, Tabs, TabItem } from "~/components"
 
 Storage classes allow you to trade off between the cost of storage and the cost of accessing data. Every object stored in R2 has an associated storage class.
 
 All storage classes share the following characteristics:
 
-- Compatible with Workers API, S3 API, and public buckets.
-- 99.999999999% (eleven 9s) of annual durability.
-- No minimum object size.
+* Compatible with Workers API, S3 API, and public buckets.
+* 99.999999999% (eleven 9s) of annual durability.
+* No minimum object size.
 
 ## Available storage classes
 
-| Storage class     | Minimum storage duration | Data retrieval fees (processing) | Egress fees (data transfer to Internet) |
-| ----------------- | ------------------------ | -------------------------------- | --------------------------------------- |
-| Standard          | None                     | None                             | None                                    |
-| Infrequent Access | 30 days                  | Yes                              | None                                    |
+| Storage class                  | Minimum storage duration  | Data retrieval fees (processing) | Egress fees (data transfer to Internet)  |
+|--------------------------------|---------------------------|----------------------------------|------------------------------------------|
+| Standard                       | None                      | None                             | None                                     |
+| Infrequent Access              | 30 days                   | Yes                              | None                                     |
 
 For more information on how storage classes impact pricing, refer to [Pricing](/r2/pricing/).
 
@@ -31,11 +31,11 @@ Standard storage is designed for data that is accessed frequently. This is the d
 
 #### Example use cases
 
-- Website and application data
-- Media content (e.g., images, video)
-- Storing large datasets for analysis and processing
-- AI training data
-- Other workloads involving frequently accessed data
+* Website and application data
+* Media content (e.g., images, video)
+* Storing large datasets for analysis and processing
+* AI training data
+* Other workloads involving frequently accessed data
 
 ### Infrequent Access storage
 
@@ -47,9 +47,9 @@ For objects stored in Infrequent Access storage, you will be charged for the obj
 
 #### Example use cases
 
-- Long-term data archiving (for example, logs and historical records needed for compliance)
-- Data backup and disaster recovery
-- Long tail user-generated content
+* Long-term data archiving (for example, logs and historical records needed for compliance)
+* Data backup and disaster recovery
+* Long tail user-generated content
 
 ## Set default storage class for buckets
 
diff --git a/src/content/docs/r2/data-migration/index.mdx b/src/content/docs/r2/data-migration/index.mdx
index 1fc637f6979b11a..05a1dabde3c991d 100644
--- a/src/content/docs/r2/data-migration/index.mdx
+++ b/src/content/docs/r2/data-migration/index.mdx
@@ -58,4 +58,4 @@ Quickly and easily migrate data from other cloud providers to R2. Explore each o
 	</tbody>
 </table>
 
-For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
+For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
\ No newline at end of file
diff --git a/src/content/docs/r2/data-migration/migration-strategies.mdx b/src/content/docs/r2/data-migration/migration-strategies.mdx
index 484528cc3c1eabc..9771c0a5eb95eb3 100644
--- a/src/content/docs/r2/data-migration/migration-strategies.mdx
+++ b/src/content/docs/r2/data-migration/migration-strategies.mdx
@@ -60,4 +60,4 @@ You can create separate jobs with prefixes such as:
 - `/photos/2024` to migrate all 2024 files
 - `/photos/202` to migrate all files from 2023 and 2024
 
-Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
+Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.
\ No newline at end of file
diff --git a/src/content/docs/r2/data-migration/sippy.mdx b/src/content/docs/r2/data-migration/sippy.mdx
index 5715798fe2b8a77..66ef2a76b92a898 100644
--- a/src/content/docs/r2/data-migration/sippy.mdx
+++ b/src/content/docs/r2/data-migration/sippy.mdx
@@ -85,10 +85,10 @@ If your bucket is setup with [jurisdictional restrictions](/r2/reference/data-lo
 
 When enabled, Sippy exposes metrics that help you understand the progress of your ongoing migrations.
 
-| Metric                   | Description                                                                                                                                                    |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Metric | Description |
+|--------|-------------|
 | Requests served by Sippy | The percentage of overall requests served by R2 over a period of time. A higher percentage indicates that fewer requests need to be made to the source bucket. |
-| Data migrated by Sippy   | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes.                                                 |
+| Data migrated by Sippy | The amount of data that has been copied from the source bucket to R2 over a period of time. Reported in bytes. |
 
 To view current and historical metrics:
 
@@ -138,12 +138,12 @@ Cloudflare currently supports copying data from the following cloud object stora
 
 When Sippy is enabled, it changes the behavior of certain actions on your R2 bucket across [Workers](/r2/api/workers/), [S3 API](/r2/api/s3/), and [public buckets](/r2/buckets/public-buckets/).
 
-| Action       | New behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| GetObject    | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
-| HeadObject   | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| PutObject    | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Action | New behavior |
+|--------|-------------|
+| GetObject | Calls to GetObject will first attempt to retrieve the object from your R2 bucket. If the object is not present, the object will be served from the source storage bucket and simultaneously uploaded to the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>Modifications to objects in the source bucket will not be reflected in R2 after the initial copy. Once an object is stored in R2, it will not be re-retrieved and updated.</li><li>Only user-defined metadata that is prefixed by `x-amz-meta-` in the HTTP response will be migrated. Remaining metadata will be omitted.</li><li>For larger objects (greater than 199 MiB), multiple GET requests may be required to fully copy the object to R2.</li><li>If there are multiple simultaneous GET requests for an object which has not yet been fully copied to R2, Sippy may fetch the object from the source storage bucket multiple times to serve those requests.</li></ul> |
+| HeadObject | Behaves similarly to GetObject, but only retrieves object metadata. Will not copy objects to the requested R2 bucket. |
+| PutObject | No change to behavior. Calls to PutObject will add objects to the requested R2 bucket. |
+| DeleteObject | No change to behavior. Calls to DeleteObject will delete objects in the requested R2 bucket.<br/><br/>Additional considerations:<ul><li>If deletes to objects in R2 are not also made in the source storage bucket, subsequent GetObject requests will result in objects being retrieved from the source bucket and copied to R2.</li></ul> |
 
 Actions not listed above have no change in behavior. For more information, refer to [Workers API reference](/r2/api/workers/workers-api-reference/) or [S3 API compatibility](/r2/api/s3/api/).
 
diff --git a/src/content/docs/r2/data-migration/super-slurper.mdx b/src/content/docs/r2/data-migration/super-slurper.mdx
index 9788052b63d58ac..584c6edca51ca0f 100644
--- a/src/content/docs/r2/data-migration/super-slurper.mdx
+++ b/src/content/docs/r2/data-migration/super-slurper.mdx
@@ -32,7 +32,6 @@ For migration use cases that do not meet the above criteria, we recommend using
 1. In the Cloudflare dashboard, go to the **R2 data migration** page.
 
    <DashButton url="/?to=/:account/r2/slurper" />
-
 2. Select **Migrate files**.
 3. Select the source cloud storage provider that you will be migrating data from.
 4. Enter your source bucket name and associated credentials and select **Next**.
@@ -137,11 +136,7 @@ You can now use this JSON key file when enabling Super Slurper.
 
 ### ETags
 
-<Render
-	file="migrator-etag-caveat"
-	params={{ one: "Super Slurper" }}
-	product="r2"
-/>
+<Render file="migrator-etag-caveat" params={{ one: "Super Slurper" }} product="r2" />
 
 ### Archive storage classes
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
index d603be9a7e32e27..a4c2c23cbae798d 100644
--- a/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-auth-tokens.mdx
@@ -7,7 +7,7 @@ products:
   - r2
 ---
 
-import { PackageManagers, Tabs, TabItem } from "~/components";
+import { PackageManagers, Tabs, TabItem } from '~/components';
 
 The following example shows how to authenticate against R2 using the S3 API and an API token.
 
diff --git a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
index 0d2a8e4861600f8..76b0c32d6744f0f 100644
--- a/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
+++ b/src/content/docs/r2/examples/authenticate-r2-temp-credentials.mdx
@@ -40,14 +40,14 @@ The response wraps the credentials in a `result` object:
 
 ```json
 {
-	"result": {
-		"accessKeyId": "<accessKeyId>",
-		"secretAccessKey": "<secretAccessKey>",
-		"sessionToken": "<sessionToken>"
-	},
-	"errors": [],
-	"messages": [],
-	"success": true
+  "result": {
+    "accessKeyId": "<accessKeyId>",
+    "secretAccessKey": "<secretAccessKey>",
+    "sessionToken": "<sessionToken>"
+  },
+  "errors": [],
+  "messages": [],
+  "success": true
 }
 ```
 
@@ -63,77 +63,77 @@ The following helper signs a JWT with your parent secret access key and derives
 import { SignJWT } from "jose";
 
 type R2Scope =
-	| "object-read-only"
-	| "object-read-write"
-	| "admin-read-only"
-	| "admin-read-write";
+  | "object-read-only"
+  | "object-read-write"
+  | "admin-read-only"
+  | "admin-read-write";
 
 export interface TempCredentialOptions {
-	scope: R2Scope;
-	// Optional: narrow the credential to specific S3 operations.
-	actions?: string[];
-	// Time-to-live in seconds. Defaults to 1 hour.
-	ttlSeconds?: number;
-	// Optional: restrict access to specific prefixes or objects.
-	paths?: { prefixPaths?: string[]; objectPaths?: string[] };
+  scope: R2Scope;
+  // Optional: narrow the credential to specific S3 operations.
+  actions?: string[];
+  // Time-to-live in seconds. Defaults to 1 hour.
+  ttlSeconds?: number;
+  // Optional: restrict access to specific prefixes or objects.
+  paths?: { prefixPaths?: string[]; objectPaths?: string[] };
 }
 
 export async function createTempCredentials(
-	endpoint: string,
-	accountId: string,
-	parentAccessKeyId: string,
-	parentSecretAccessKey: string,
-	bucket: string,
-	opts: TempCredentialOptions,
+  endpoint: string,
+  accountId: string,
+  parentAccessKeyId: string,
+  parentSecretAccessKey: string,
+  bucket: string,
+  opts: TempCredentialOptions,
 ): Promise<{
-	accessKeyId: string;
-	secretAccessKey: string;
-	sessionToken: string;
+  accessKeyId: string;
+  secretAccessKey: string;
+  sessionToken: string;
 }> {
-	const ttl = opts.ttlSeconds ?? 3600;
-
-	const claims: Record<string, unknown> = {
-		bucket,
-		scope: opts.scope,
-	};
-
-	if (opts.actions !== undefined && opts.actions.length > 0) {
-		claims.actions = opts.actions;
-	}
-
-	if (opts.paths !== undefined) {
-		claims.paths = {
-			prefixPaths: opts.paths.prefixPaths ?? [],
-			objectPaths: opts.paths.objectPaths ?? [],
-		};
-	}
-
-	// Sign the JWT with the parent secret access key. R2 validates this signature.
-	const jwt = await new SignJWT(claims)
-		.setProtectedHeader({ alg: "HS256", typ: "JWT" })
-		.setSubject(accountId)
-		.setIssuer(parentAccessKeyId)
-		.setAudience(new URL(endpoint).host)
-		.setIssuedAt()
-		.setExpirationTime(`${ttl}s`)
-		.sign(new TextEncoder().encode(parentSecretAccessKey));
-
-	// The temporary secret access key is the SHA-256 hex digest of the signed JWT.
-	const digest = await crypto.subtle.digest(
-		"SHA-256",
-		new TextEncoder().encode(jwt),
-	);
-	const secretAccessKey = Array.from(new Uint8Array(digest))
-		.map((b) => b.toString(16).padStart(2, "0"))
-		.join("");
-
-	return {
-		// Reuse the parent access key ID as the temporary access key ID.
-		accessKeyId: parentAccessKeyId,
-		secretAccessKey,
-		// The session token is base64("jwt/" + signed JWT).
-		sessionToken: btoa(`jwt/${jwt}`),
-	};
+  const ttl = opts.ttlSeconds ?? 3600;
+
+  const claims: Record<string, unknown> = {
+    bucket,
+    scope: opts.scope,
+  };
+
+  if (opts.actions !== undefined && opts.actions.length > 0) {
+    claims.actions = opts.actions;
+  }
+
+  if (opts.paths !== undefined) {
+    claims.paths = {
+      prefixPaths: opts.paths.prefixPaths ?? [],
+      objectPaths: opts.paths.objectPaths ?? [],
+    };
+  }
+
+  // Sign the JWT with the parent secret access key. R2 validates this signature.
+  const jwt = await new SignJWT(claims)
+    .setProtectedHeader({ alg: "HS256", typ: "JWT" })
+    .setSubject(accountId)
+    .setIssuer(parentAccessKeyId)
+    .setAudience(new URL(endpoint).host)
+    .setIssuedAt()
+    .setExpirationTime(`${ttl}s`)
+    .sign(new TextEncoder().encode(parentSecretAccessKey));
+
+  // The temporary secret access key is the SHA-256 hex digest of the signed JWT.
+  const digest = await crypto.subtle.digest(
+    "SHA-256",
+    new TextEncoder().encode(jwt),
+  );
+  const secretAccessKey = Array.from(new Uint8Array(digest))
+    .map((b) => b.toString(16).padStart(2, "0"))
+    .join("");
+
+  return {
+    // Reuse the parent access key ID as the temporary access key ID.
+    accessKeyId: parentAccessKeyId,
+    secretAccessKey,
+    // The session token is base64("jwt/" + signed JWT).
+    sessionToken: btoa(`jwt/${jwt}`),
+  };
 }
 ```
 
@@ -145,17 +145,17 @@ import { createTempCredentials } from "./temp-credentials";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const creds = await createTempCredentials(
-	R2_URL,
-	ACCOUNT_ID,
-	PARENT_ACCESS_KEY_ID,
-	PARENT_SECRET_ACCESS_KEY,
-	"my-bucket",
-	{
-		scope: "object-read-only",
-		actions: ["GetObject", "HeadObject"],
-		ttlSeconds: 900,
-		paths: { prefixPaths: ["data/"] },
-	},
+  R2_URL,
+  ACCOUNT_ID,
+  PARENT_ACCESS_KEY_ID,
+  PARENT_SECRET_ACCESS_KEY,
+  "my-bucket",
+  {
+    scope: "object-read-only",
+    actions: ["GetObject", "HeadObject"],
+    ttlSeconds: 900,
+    paths: { prefixPaths: ["data/"] },
+  },
 );
 ```
 
@@ -169,10 +169,10 @@ import { AwsClient } from "aws4fetch";
 const R2_URL = `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`;
 
 const client = new AwsClient({
-	accessKeyId: ACCESS_KEY_ID,
-	secretAccessKey: SECRET_ACCESS_KEY,
-	sessionToken: SESSION_TOKEN,
-	service: "s3",
+  accessKeyId: ACCESS_KEY_ID,
+  secretAccessKey: SECRET_ACCESS_KEY,
+  sessionToken: SESSION_TOKEN,
+  service: "s3",
 });
 
 // Allowed: object under the data/ prefix.
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
index 1fb6ee02263c766..8c7b8736c9498a9 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js-v3.mdx
@@ -58,7 +58,9 @@ console.log(await S3.send(new ListBucketsCommand({})));
 //     }
 // }
 
-console.log(await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })));
+console.log(
+	await S3.send(new ListObjectsV2Command({ Bucket: "my-bucket" })),
+);
 // {
 //     '$metadata': {
 //       httpStatusCode: 200,
@@ -155,13 +157,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -180,6 +182,5 @@ const putUrl = await getSignedUrl(
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
index a7845d865d25f16..3143d3c15d33437 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-js.mdx
@@ -74,11 +74,11 @@ You can also generate presigned links that can be used to share public read or w
 ```ts
 // Use the expires property to determine how long the presigned link is valid.
 console.log(
-	await s3.getSignedUrlPromise("getObject", {
-		Bucket: "my-bucket",
-		Key: "dog.png",
-		Expires: 3600,
-	}),
+await s3.getSignedUrlPromise("getObject", {
+	Bucket: "my-bucket",
+	Key: "dog.png",
+	Expires: 3600,
+}),
 );
 // You can also create links for operations such as putObject to allow temporary write access to a specific key.
 // Specify ContentType to restrict uploads to a specific file type.
@@ -115,13 +115,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -137,6 +137,5 @@ const putUrl = await s3.getSignedUrlPromise("putObject", {
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
index ef0c34ebe76c4fc..e19b20b7d19fdd1 100644
--- a/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
+++ b/src/content/docs/r2/examples/aws/aws-sdk-kotlin.mdx
@@ -104,3 +104,4 @@ To download a file using the GET URL:
 ```bash
 curl -X GET "https://<your-presigned-get-url>" -o downloaded-file.txt
 ```
+
diff --git a/src/content/docs/r2/examples/aws/aws4fetch.mdx b/src/content/docs/r2/examples/aws/aws4fetch.mdx
index 51411a247aef736..6330b4a288944d3 100644
--- a/src/content/docs/r2/examples/aws/aws4fetch.mdx
+++ b/src/content/docs/r2/examples/aws/aws4fetch.mdx
@@ -144,13 +144,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -172,6 +172,5 @@ const putUrl = signedRequest.url.toString();
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/boto3.mdx b/src/content/docs/r2/examples/aws/boto3.mdx
index 9dce860b7a623d6..fe1fe466ad3d55c 100644
--- a/src/content/docs/r2/examples/aws/boto3.mdx
+++ b/src/content/docs/r2/examples/aws/boto3.mdx
@@ -118,13 +118,13 @@ When generating presigned URLs for uploads, you can limit abuse and misuse by:
 
 ```json
 [
-	{
-		"AllowedOrigins": ["https://example.com"],
-		"AllowedMethods": ["PUT"],
-		"AllowedHeaders": ["Content-Type"],
-		"ExposeHeaders": ["ETag"],
-		"MaxAgeSeconds": 3600
-	}
+  {
+    "AllowedOrigins": ["https://example.com"],
+    "AllowedMethods": ["PUT"],
+    "AllowedHeaders": ["Content-Type"],
+    "ExposeHeaders": ["ETag"],
+    "MaxAgeSeconds": 3600
+  }
 ]
 ```
 
@@ -145,6 +145,5 @@ put_url = s3.generate_presigned_url(
 ```
 
 When a client uses this presigned URL, they must:
-
 - Make the request from an allowed origin (enforced by CORS)
 - Include the `Content-Type: image/png` header (enforced by the signature)
diff --git a/src/content/docs/r2/examples/aws/custom-header.mdx b/src/content/docs/r2/examples/aws/custom-header.mdx
index 31c3e784bed5934..59695cb8019c958 100644
--- a/src/content/docs/r2/examples/aws/custom-header.mdx
+++ b/src/content/docs/r2/examples/aws/custom-header.mdx
@@ -45,32 +45,35 @@ print(response)
 `aws-sdk-js-v3` allows the customization of request behavior through the use of its [middleware stack](https://aws.amazon.com/blogs/developer/middleware-stack-modular-aws-sdk-js/). This example adds a middleware to the client which adds a header to every `PutObject` request being made.
 
 ```ts
-import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
+import {
+  PutObjectCommand,
+  S3Client,
+} from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-	region: "auto", // Required by SDK but not used by R2
-	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-	credentials: {
-		accessKeyId: ACCESS_KEY_ID,
-		secretAccessKey: SECRET_ACCESS_KEY,
-	},
+  region: "auto", // Required by SDK but not used by R2
+  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+  credentials: {
+    accessKeyId: ACCESS_KEY_ID,
+    secretAccessKey: SECRET_ACCESS_KEY,
+  },
 });
 
 client.middlewareStack.add(
-	(next, context) => async (args) => {
-		const r = args.request as RequestInit;
-		r.headers["cf-create-bucket-if-missing"] = "true";
+  (next, context) => async (args) => {
+      const r = args.request as RequestInit
+      r.headers["cf-create-bucket-if-missing"] = "true";
 
-		return await next(args);
-	},
-	{ step: "build", name: "customHeaders" },
-);
+      return await next(args)
+    },
+  { step: 'build', name: 'customHeaders' },
+)
 
 const command = new PutObjectCommand({
-	Bucket: "my_bucket",
-	Key: "my_key",
-	Body: "my_data",
+  Bucket: "my_bucket",
+  Key: "my_key",
+  Body: "my_data"
 });
 
 const response = await client.send(command);
@@ -124,40 +127,44 @@ print(response)
 Here we again configure the header we would like to set by creating a middleware, but this time we add the middleware to the request itself instead of to the whole client.
 
 ```ts
-import { PutObjectCommand, S3Client } from "@aws-sdk/client-s3";
+import {
+  PutObjectCommand,
+  S3Client,
+} from "@aws-sdk/client-s3";
 
 const client = new S3Client({
-	region: "auto", // Required by SDK but not used by R2
-	// Provide your Cloudflare account ID
-	endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
-	// Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
-	credentials: {
-		accessKeyId: ACCESS_KEY_ID,
-		secretAccessKey: SECRET_ACCESS_KEY,
-	},
+  region: "auto", // Required by SDK but not used by R2
+  // Provide your Cloudflare account ID
+  endpoint: `https://${ACCOUNT_ID}.r2.cloudflarestorage.com`,
+  // Retrieve your S3 API credentials for your R2 bucket via API tokens (see: https://developers.cloudflare.com/r2/api/tokens)
+  credentials: {
+    accessKeyId: ACCESS_KEY_ID,
+    secretAccessKey: SECRET_ACCESS_KEY,
+  },
 });
 
 const command = new PutObjectCommand({
-	Bucket: "my_bucket",
-	Key: "my_key",
-	Body: "my_data",
+  Bucket: "my_bucket",
+  Key: "my_key",
+  Body: "my_data"
 });
 
-const headers = { "If-Match": '"29d911f495d1ba7cb3a4d7d15e63236a"' };
+const headers = { 'If-Match': '"29d911f495d1ba7cb3a4d7d15e63236a"' }
 command.middlewareStack.add(
-	(next) => (args) => {
-		const r = args.request as RequestInit;
-
-		Object.entries(headers).forEach(
-			([k, v]: [key: string, value: string]): void => {
-				r.headers[k] = v;
-			},
-		);
-
-		return next(args);
-	},
-	{ step: "build", name: "customHeaders" },
-);
+  (next) =>
+    (args) => {
+      const r = args.request as RequestInit
+
+      Object.entries(headers).forEach(
+        ([k, v]: [key: string, value: string]): void => {
+          r.headers[k] = v
+        },
+      )
+
+      return next(args)
+    },
+  { step: 'build', name: 'customHeaders' },
+)
 const response = await client.send(command);
 
 console.log(response);
diff --git a/src/content/docs/r2/examples/cache-api.mdx b/src/content/docs/r2/examples/cache-api.mdx
index c5b5a3f0b9d2437..8b5d8ebd9354ccc 100644
--- a/src/content/docs/r2/examples/cache-api.mdx
+++ b/src/content/docs/r2/examples/cache-api.mdx
@@ -11,64 +11,67 @@ Use the [Cache API](/workers/runtime-apis/cache/) to store R2 objects in Cloudfl
 
 :::note
 
+
 You will need to [connect a custom domain](/workers/configuration/routing/custom-domains/) or [route](/workers/configuration/routing/routes/) to your Worker in order to use the Cache API. Cache API operations in the Cloudflare Workers dashboard editor, Playground previews, and any `*.workers.dev` deployments will have no impact.
 
+
 :::
 
 ```js
+
 export default {
-	async fetch(request, env, context) {
-		try {
-			const url = new URL(request.url);
-
-			// Construct the cache key from the cache URL
-			const cacheKey = new Request(url.toString(), request);
-			const cache = caches.default;
-
-			// Check whether the value is already available in the cache
-			// if not, you will need to fetch it from R2, and store it in the cache
-			// for future access
-			let response = await cache.match(cacheKey);
-
-			if (response) {
-				console.log(`Cache hit for: ${request.url}.`);
-				return response;
-			}
-
-			console.log(
-				`Response for request url: ${request.url} not present in cache. Fetching and caching request.`,
-			);
-
-			// If not in cache, get it from R2
-			const objectKey = url.pathname.slice(1);
-			const object = await env.MY_BUCKET.get(objectKey);
-			if (object === null) {
-				return new Response("Object Not Found", { status: 404 });
-			}
-
-			// Set the appropriate object headers
-			const headers = new Headers();
-			object.writeHttpMetadata(headers);
-			headers.set("etag", object.httpEtag);
-
-			// Cache API respects Cache-Control headers. Setting s-max-age to 10
-			// will limit the response to be in cache for 10 seconds max
-			// Any changes made to the response here will be reflected in the cached value
-			headers.append("Cache-Control", "s-maxage=10");
-
-			response = new Response(object.body, {
-				headers,
-			});
-
-			// Store the fetched response as cacheKey
-			// Use waitUntil so you can return the response without blocking on
-			// writing to cache
-			context.waitUntil(cache.put(cacheKey, response.clone()));
-
-			return response;
-		} catch (e) {
-			return new Response("Error thrown " + e.message);
-		}
-	},
+  async fetch(request, env, context) {
+    try {
+      const url = new URL(request.url);
+
+      // Construct the cache key from the cache URL
+      const cacheKey = new Request(url.toString(), request);
+      const cache = caches.default;
+
+      // Check whether the value is already available in the cache
+      // if not, you will need to fetch it from R2, and store it in the cache
+      // for future access
+      let response = await cache.match(cacheKey);
+
+      if (response) {
+        console.log(`Cache hit for: ${request.url}.`);
+        return response;
+      }
+
+      console.log(
+        `Response for request url: ${request.url} not present in cache. Fetching and caching request.`
+      );
+
+      // If not in cache, get it from R2
+      const objectKey = url.pathname.slice(1);
+      const object = await env.MY_BUCKET.get(objectKey);
+      if (object === null) {
+        return new Response('Object Not Found', { status: 404 });
+      }
+
+      // Set the appropriate object headers
+      const headers = new Headers();
+      object.writeHttpMetadata(headers);
+      headers.set('etag', object.httpEtag);
+
+      // Cache API respects Cache-Control headers. Setting s-max-age to 10
+      // will limit the response to be in cache for 10 seconds max
+      // Any changes made to the response here will be reflected in the cached value
+      headers.append('Cache-Control', 's-maxage=10');
+
+      response = new Response(object.body, {
+        headers,
+      });
+
+      // Store the fetched response as cacheKey
+      // Use waitUntil so you can return the response without blocking on
+      // writing to cache
+      context.waitUntil(cache.put(cacheKey, response.clone()));
+
+      return response;
+    } catch (e) {
+      return new Response('Error thrown ' + e.message);
+    }
+  },
 };
 ```
diff --git a/src/content/docs/r2/examples/terraform.mdx b/src/content/docs/r2/examples/terraform.mdx
index 6298b67ad2b5e29..70ba59913732088 100644
--- a/src/content/docs/r2/examples/terraform.mdx
+++ b/src/content/docs/r2/examples/terraform.mdx
@@ -7,17 +7,18 @@ products:
   - r2
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-<Render file="keys" product="r2" />
-<br />
+<Render file="keys" product="r2" /><br/>
 
 This example shows how to configure R2 with Terraform using the [Cloudflare provider](https://github.com/cloudflare/terraform-provider-cloudflare).
 
 :::note[Note for using AWS provider]
 
+
 When using the Cloudflare Terraform provider, you can only manage buckets. To configure items such as CORS and object lifecycles, you will need to use the [AWS Provider](/r2/examples/terraform-aws/).
 
+
 :::
 
 With [`terraform`](https://developer.hashicorp.com/terraform/downloads) installed, create `main.tf` and copy the content below replacing with your API Token.
diff --git a/src/content/docs/r2/get-started/cli.mdx b/src/content/docs/r2/get-started/cli.mdx
index 9d545d0ef4b0755..96eb679c9c1e3f1 100644
--- a/src/content/docs/r2/get-started/cli.mdx
+++ b/src/content/docs/r2/get-started/cli.mdx
@@ -8,14 +8,7 @@ products:
   - r2
 ---
 
-import {
-	PackageManagers,
-	LinkCard,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { PackageManagers, LinkCard, Render, Tabs, TabItem, Steps } from "~/components";
 
 Manage R2 buckets and objects directly from your terminal. Use CLI tools to automate tasks and manage objects.
 
diff --git a/src/content/docs/r2/get-started/index.mdx b/src/content/docs/r2/get-started/index.mdx
index dd498e4f6f5b795..f23578ee0cbb2f0 100644
--- a/src/content/docs/r2/get-started/index.mdx
+++ b/src/content/docs/r2/get-started/index.mdx
@@ -16,7 +16,6 @@ Cloudflare R2 Storage allows developers to store large amounts of unstructured d
 ## Before you begin
 
 You need a Cloudflare account with an R2 subscription. If you do not have one:
-
 1. Go to the [Cloudflare Dashboard](https://dash.cloudflare.com/).
 2. Select **Storage & databases > R2 > Overview**
 3. Complete the checkout flow to add an R2 subscription to your account.
diff --git a/src/content/docs/r2/get-started/s3.mdx b/src/content/docs/r2/get-started/s3.mdx
index 30f8f11008b2c09..d8f07cb88333887 100644
--- a/src/content/docs/r2/get-started/s3.mdx
+++ b/src/content/docs/r2/get-started/s3.mdx
@@ -8,14 +8,7 @@ products:
   - r2
 ---
 
-import {
-	LinkCard,
-	PackageManagers,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { LinkCard, PackageManagers, Render, Tabs, TabItem, Steps } from "~/components";
 
 R2 provides support for a [S3-compatible API](/r2/api/s3/api/), which means you can use any S3 SDK, library, or tool to interact with your buckets. If you have existing code that works with S3, you can use it with R2 by changing the endpoint URL.
 
diff --git a/src/content/docs/r2/get-started/workers-api.mdx b/src/content/docs/r2/get-started/workers-api.mdx
index 408785ea7255ff2..2fca2b0febc4696 100644
--- a/src/content/docs/r2/get-started/workers-api.mdx
+++ b/src/content/docs/r2/get-started/workers-api.mdx
@@ -15,7 +15,7 @@ import {
 	Render,
 	Tabs,
 	TabItem,
-	Steps,
+	Steps
 } from "~/components";
 
 [Workers](/workers/) let you run code at the edge. When you bind an R2 bucket to a Worker, you can read and write objects directly using the [Workers API](/r2/api/workers/workers-api-usage/).
diff --git a/src/content/docs/r2/objects/delete-objects.mdx b/src/content/docs/r2/objects/delete-objects.mdx
index 30dedcd5ba096ac..a890b14c861b46d 100644
--- a/src/content/docs/r2/objects/delete-objects.mdx
+++ b/src/content/docs/r2/objects/delete-objects.mdx
@@ -17,7 +17,6 @@ You can delete objects from R2 using the dashboard, Workers API, S3 API, or comm
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. (Optional) Select the **View prefixes as directories** checkbox to view prefixes grouped as [folders](/r2/objects/#prefixes-and-folders).
 4. Select the objects or folders you want to delete. You can select a mix of both in the same operation.
@@ -111,19 +110,19 @@ wrangler r2 object delete test-bucket/image.png
 ## Related resources
 
 <LinkCard
-	title="Delete buckets"
-	href="/r2/buckets/delete-buckets/"
-	description="Empty all objects from a bucket and permanently delete it."
+  title="Delete buckets"
+  href="/r2/buckets/delete-buckets/"
+  description="Empty all objects from a bucket and permanently delete it."
 />
 
 <LinkCard
-	title="Bucket locks"
-	href="/r2/buckets/bucket-locks/"
-	description="Protect objects from accidental deletion with retention policies."
+  title="Bucket locks"
+  href="/r2/buckets/bucket-locks/"
+  description="Protect objects from accidental deletion with retention policies."
 />
 
 <LinkCard
-	title="Object lifecycles"
-	href="/r2/buckets/object-lifecycles/"
-	description="Automatically expire objects after a specified period."
+  title="Object lifecycles"
+  href="/r2/buckets/object-lifecycles/"
+  description="Automatically expire objects after a specified period."
 />
diff --git a/src/content/docs/r2/objects/download-objects.mdx b/src/content/docs/r2/objects/download-objects.mdx
index 78ebe64fe9940ee..d060979a0b675d4 100644
--- a/src/content/docs/r2/objects/download-objects.mdx
+++ b/src/content/docs/r2/objects/download-objects.mdx
@@ -17,7 +17,6 @@ You can download objects from R2 using the dashboard, Workers API, S3 API, or co
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Locate the object you want to download.
 4. Select **...** for the object and click **Download**.
@@ -109,4 +108,4 @@ Use [Wrangler](/workers/wrangler/install-and-update/) to download objects. Run t
 wrangler r2 object get test-bucket/image.png
 ```
 
-The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
+The file will be downloaded into the current working directory. You can also use the `--file` flag to set a new name for the object as it is downloaded, and the `--pipe` flag to pipe the download to standard output (stdout).
\ No newline at end of file
diff --git a/src/content/docs/r2/objects/index.mdx b/src/content/docs/r2/objects/index.mdx
index 147e55a78a576d7..7cee8cf9e982a0c 100644
--- a/src/content/docs/r2/objects/index.mdx
+++ b/src/content/docs/r2/objects/index.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing, Render } from "~/components"
 
 Objects are individual files or data that you store in an R2 bucket. Each object is identified by its key, a string like `images/photo.png`.
 
@@ -22,4 +22,4 @@ The R2 dashboard groups objects that share a common prefix into folders when the
 
 <DirectoryListing />
 
-<Render file="link-to-workers-r2-api" product="r2" />
+<Render file="link-to-workers-r2-api" product="r2"/>
\ No newline at end of file
diff --git a/src/content/docs/r2/platform/audit-logs.mdx b/src/content/docs/r2/platform/audit-logs.mdx
index ca1e6d74b1b1059..56b604e8c1363a0 100644
--- a/src/content/docs/r2/platform/audit-logs.mdx
+++ b/src/content/docs/r2/platform/audit-logs.mdx
@@ -22,18 +22,18 @@ For more information on how to access and use audit logs, refer to [Review audit
 
 The following configuration actions are logged:
 
-| Operation                          | Description                                                          |
-| ---------------------------------- | -------------------------------------------------------------------- |
-| CreateBucket                       | Creation of a new bucket.                                            |
-| DeleteBucket                       | Deletion of an existing bucket.                                      |
-| AddCustomDomain                    | Addition of a custom domain to a bucket.                             |
-| RemoveCustomDomain                 | Removal of a custom domain from a bucket.                            |
-| ChangeBucketVisibility             | Change to the managed public access (`r2.dev`) settings of a bucket. |
-| PutBucketStorageClass              | Change to the default storage class of a bucket.                     |
-| PutBucketLifecycleConfiguration    | Change to the object lifecycle configuration of a bucket.            |
-| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket.         |
-| PutBucketCors                      | Change to the CORS configuration for a bucket.                       |
-| DeleteBucketCors                   | Deletion of the CORS configuration for a bucket.                     |
+| Operation | Description |
+|-----------|-------------|
+| CreateBucket | Creation of a new bucket. |
+| DeleteBucket | Deletion of an existing bucket. |
+| AddCustomDomain | Addition of a custom domain to a bucket. |
+| RemoveCustomDomain | Removal of a custom domain from a bucket. |
+| ChangeBucketVisibility | Change to the managed public access (`r2.dev`) settings of a bucket. |
+| PutBucketStorageClass | Change to the default storage class of a bucket. |
+| PutBucketLifecycleConfiguration | Change to the object lifecycle configuration of a bucket. |
+| DeleteBucketLifecycleConfiguration | Deletion of the object lifecycle configuration for a bucket. |
+| PutBucketCors | Change to the CORS configuration for a bucket. |
+| DeleteBucketCors | Deletion of the CORS configuration for a bucket. |
 
 :::note
 Logs for data access operations, such as `GetObject` and `PutObject`, are not included in audit logs. To log HTTP requests made to public R2 buckets, use the [HTTP requests](/logs/logpush/logpush-job/datasets/zone/http_requests/) Logpush dataset.
@@ -45,22 +45,23 @@ Below is an example of an audit log entry showing the creation of a new bucket:
 
 ```json
 {
-	"action": { "info": "CreateBucket", "result": true, "type": "create" },
-	"actor": {
-		"email": "<ACTOR_EMAIL>",
-		"id": "3f7b730e625b975bc1231234cfbec091",
-		"ip": "fe32:43ed:12b5:526::1d2:13",
-		"type": "user"
-	},
-	"id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
-	"interface": "API",
-	"metadata": { "zone_name": "r2.cloudflarestorage.com" },
-	"newValue": "",
-	"newValueJson": {},
-	"oldValue": "",
-	"oldValueJson": {},
-	"owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
-	"resource": { "id": "my-bucket", "type": "r2.bucket" },
-	"when": "2024-07-15T16:32:52.412Z"
+  "action": { "info": "CreateBucket", "result": true, "type": "create" },
+  "actor": {
+    "email": "<ACTOR_EMAIL>",
+    "id": "3f7b730e625b975bc1231234cfbec091",
+    "ip": "fe32:43ed:12b5:526::1d2:13",
+    "type": "user"
+  },
+  "id": "5eaeb6be-1234-406a-87ab-1971adc1234c",
+  "interface": "API",
+  "metadata": { "zone_name": "r2.cloudflarestorage.com" },
+  "newValue": "",
+  "newValueJson": {},
+  "oldValue": "",
+  "oldValueJson": {},
+  "owner": { "id": "1234d848c0b9e484dfc37ec392b5fa8a" },
+  "resource": { "id": "my-bucket", "type": "r2.bucket" },
+  "when": "2024-07-15T16:32:52.412Z"
 }
+
 ```
diff --git a/src/content/docs/r2/platform/metrics-analytics.mdx b/src/content/docs/r2/platform/metrics-analytics.mdx
index e28dc53a56af003..91288c6dcf21e47 100644
--- a/src/content/docs/r2/platform/metrics-analytics.mdx
+++ b/src/content/docs/r2/platform/metrics-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - r2
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 R2 exposes analytics that allow you to inspect the requests and storage of the buckets in your account.
 
@@ -16,8 +16,8 @@ The metrics displayed for a bucket in the [Cloudflare dashboard](https://dash.cl
 
 R2 currently has two datasets:
 
-| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                                  |
-| --------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------- |
+| <div style="width:100px">Dataset </div> | <div style="width:235px">GraphQL Dataset Name </div> | Description                                                          |
+| --------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- |
 | Operations                              | `r2OperationsAdaptiveGroups`                         | This dataset consists of the operations taken on a bucket within an account. |
 | Storage                                 | `r2StorageAdaptiveGroups`                            | This dataset consists of the storage of a bucket within an account.          |
 
@@ -58,7 +58,6 @@ Per-bucket analytics for R2 are available in the Cloudflare dashboard. To view c
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Select the **Metrics** tab.
 
diff --git a/src/content/docs/r2/platform/troubleshooting.mdx b/src/content/docs/r2/platform/troubleshooting.mdx
index 726ef97a385e92b..e42a38c8bff9748 100644
--- a/src/content/docs/r2/platform/troubleshooting.mdx
+++ b/src/content/docs/r2/platform/troubleshooting.mdx
@@ -21,7 +21,6 @@ If you do have a CORS issue, refer to [Resolving CORS issues](#if-it-is-actually
 1. Open developer tools on your browser.
 2. Go to the **Network** tab and find the failing request. You may need to reload the page, as requests are only logged after developer tools have been opened.
 3. Check the response headers for the following two headers:
-
 - `cf-cache-status`
 - `cf-mitigated`
 
@@ -65,7 +64,7 @@ If your users are directly uploading to the bucket (for example, using the S3 or
 
 ### Bucket sharding
 
-For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket. While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
+For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket.  While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.
 
 ## Objects named `This object is unnamed`
 
@@ -85,4 +84,4 @@ For example, uploading an object named `example/` into an R2 bucket will be disp
 <FileTree>
 - example
   - `This object is unnamed`
-</FileTree>
+</FileTree>
\ No newline at end of file
diff --git a/src/content/docs/r2/pricing.mdx b/src/content/docs/r2/pricing.mdx
index 6d420e4740d8b39..7c3d3a55663af73 100644
--- a/src/content/docs/r2/pricing.mdx
+++ b/src/content/docs/r2/pricing.mdx
@@ -27,13 +27,13 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 ## R2 pricing
 
-|                                    | Standard storage         | Infrequent Access storage |
-| ---------------------------------- | ------------------------ | ------------------------- |
-| Storage                            | $0.015 / GB-month        | $0.01 / GB-month          |
-| Class A Operations                 | $4.50 / million requests | $9.00 / million requests  |
-| Class B Operations                 | $0.36 / million requests | $0.90 / million requests  |
-| Data Retrieval (processing)        | None                     | $0.01 / GB                |
-| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                 |
+|                                    | Standard storage         | Infrequent Access storage                               |
+| ---------------------------------- | ------------------------ | ------------------------------------------------------- |
+| Storage                            | $0.015 / GB-month        | $0.01 / GB-month                                        |
+| Class A Operations                 | $4.50 / million requests | $9.00 / million requests                                |
+| Class B Operations                 | $0.36 / million requests | $0.90 / million requests                                |
+| Data Retrieval (processing)        | None                     | $0.01 / GB                                              |
+| Egress (data transfer to Internet) | Free [^1]                | Free [^1]                                               |
 
 :::caution[Billable unit rounding]
 Cloudflare rounds up your usage to the next billing unit.
@@ -43,7 +43,7 @@ For example:
 - If you have performed one million and one operations, you will be billed for two million operations.
 - If you have used 1.1 GB-month, you will be billed for 2 GB-month.
 - If you have retrieved data (for infrequent access storage) for 1.1 GB, you will be billed for 2 GB.
-  :::
+:::
 
 ### Free tier
 
@@ -92,10 +92,10 @@ Data retrieval fees apply when you access or retrieve data from the Infrequent A
 
 For objects stored in Infrequent Access storage, you will be charged for the object for the minimum storage duration even if the object was deleted, moved, or replaced before the specified duration.
 
-| Storage class             | Minimum storage duration |
-| ------------------------- | ------------------------ |
-| Standard storage          | None                     |
-| Infrequent Access storage | 30 days                  |
+| Storage class                                          | Minimum storage duration |
+| ------------------------------------------------------ | ------------------------ |
+| Standard storage                                       | None                     |
+| Infrequent Access storage                              | 30 days                  |
 
 ## R2 Data Catalog pricing
 
@@ -127,25 +127,25 @@ To learn about potential cost savings from using R2, refer to the [R2 pricing ca
 
 If a user writes 1,000 objects in R2 **Standard storage** for 1 month with an average size of 1 GB and reads each object 1,000 times during the month, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier    | Billable Quantity | Price      |
-| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ---------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85     |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00      |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00      |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | None              | $0.00      |
-| **TOTAL**                   |                                                               |              |                   | **$14.85** |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | 10 GB-months | 990 GB-months     | $14.85      |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | 1 million    | 0                 | $0.00       |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | 10 million   | 0                 | $0.00       |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA         | None              | $0.00       |
+| **TOTAL**                   |                                                               |              |                   | **$14.85**  |
 
 ### Infrequent access example
 
 If a user writes 1,000 objects in R2 Infrequent Access storage with an average size of 1 GB, stores them for 5 days, and then deletes them (delete operations are free), and during those 5 days each object is read 1,000 times, the estimated cost for the month would be:
 
-|                             | Usage                                                         | Free Tier | Billable Quantity | Price      |
-| --------------------------- | ------------------------------------------------------------- | --------- | ----------------- | ---------- |
-| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA        | 1,000 GB-months   | $10.00     |
-| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA        | 1,000             | $9.00      |
-| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA        | 1 million         | $0.90      |
-| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA        | 1,000 GB          | $10.00     |
-| **TOTAL**                   |                                                               |           |                   | **$29.90** |
+|                             | Usage                                                         | Free Tier    | Billable Quantity | Price       |
+| --------------------------- | ------------------------------------------------------------- | ------------ | ----------------- | ----------- |
+| Storage                     | (1,000 objects) \* (1 GB per object) = 1,000 GB-months        | NA           | 1,000 GB-months   | $10.00      |
+| Class A Operations          | (1,000 objects) \* (1 write per object) = 1,000 writes        | NA           | 1,000             | $9.00       |
+| Class B Operations          | (1,000 objects) \* (1,000 reads per object) = 1 million reads | NA           | 1 million         | $0.90       |
+| Data retrieval (processing) | (1,000 objects) \* (1 GB per object) = 1,000 GB               | NA           | 1,000 GB          | $10.00      |
+| **TOTAL**                   |                                                               |              |                   | **$29.90**  |
 
 Note that the minimal storage duration for infrequent access storage is 30 days, which means the billable quantity is 1,000 GB-months, rather than 167 GB-months.
 
diff --git a/src/content/docs/r2/r2-sql.mdx b/src/content/docs/r2/r2-sql.mdx
index 727a004053c732a..690e0b283548807 100644
--- a/src/content/docs/r2/r2-sql.mdx
+++ b/src/content/docs/r2/r2-sql.mdx
@@ -10,4 +10,4 @@ description: >-
   R2 SQL is a serverless SQL interface for Cloudflare R2, enabling querying and analyzing data.
 products:
   - r2
----
+---
\ No newline at end of file
diff --git a/src/content/docs/r2/reference/data-location.mdx b/src/content/docs/r2/reference/data-location.mdx
index a55ac28a3ebbc87..64607b3dbd621ac 100644
--- a/src/content/docs/r2/reference/data-location.mdx
+++ b/src/content/docs/r2/reference/data-location.mdx
@@ -29,7 +29,6 @@ You can choose to automatically create your bucket in the closest available regi
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, leave _None_ selected for automatic selection or choose a region from the list.
@@ -80,7 +79,6 @@ Use Jurisdictional Restrictions when you need to ensure data is stored and proce
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter a name for the bucket.
 4. Under **Location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
diff --git a/src/content/docs/r2/reference/data-security.mdx b/src/content/docs/r2/reference/data-security.mdx
index 96c66a58a3eb8df..15c1260d9648ae3 100644
--- a/src/content/docs/r2/reference/data-security.mdx
+++ b/src/content/docs/r2/reference/data-security.mdx
@@ -26,8 +26,10 @@ Access over plaintext HTTP (without TLS/SSL) can be disabled by connecting a [cu
 
 :::note
 
+
 R2 custom domains use Cloudflare for SaaS certificates and cannot be customized. Even if you have [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/), the advanced certificate will not be used due to [certificate prioritization](/ssl/reference/certificate-and-hostname-priority/).
 
+
 :::
 
 ## Compliance
diff --git a/src/content/docs/r2/reference/durability.mdx b/src/content/docs/r2/reference/durability.mdx
index 5d15f76865bd036..177e6ed4bd08d13 100644
--- a/src/content/docs/r2/reference/durability.mdx
+++ b/src/content/docs/r2/reference/durability.mdx
@@ -8,7 +8,7 @@ products:
   - r2
 ---
 
-R2 is designed to provide 99.999999999% (eleven 9s) of annual durability. This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
+R2 is designed to provide 99.999999999% (eleven 9s) of annual durability.  This means that if you store 10,000,000 objects on R2, you can expect to lose an object once every 10,000 years on average.
 
 ## How R2 achieves eleven-nines durability
 
@@ -22,7 +22,7 @@ R2's durability is built on multiple layers of redundancy and data protection:
 
 ### Considerations
 
-- Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
-- R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
-- Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
-- Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
+* Durability is not a guarantee of data availability. It is a measure of the likelihood of data loss.
+* R2 provides an availability [SLA of 99.9%](https://www.cloudflare.com/r2-service-level-agreement/)
+* Durability does not prevent intentional or accidental deletion of data. Use [bucket locks](/r2/buckets/bucket-locks/) and/or bucket-scoped [API tokens](/r2/api/tokens/) to limit access to data.
+* Durability is also distinct from [consistency](/r2/reference/consistency/), which describes how reads and writes are reflected in the system's state (e.g. eventual consistency vs. strong consistency).
diff --git a/src/content/docs/r2/reference/unicode-interoperability.mdx b/src/content/docs/r2/reference/unicode-interoperability.mdx
index 77796a1f1294a90..1543c6629fa5744 100644
--- a/src/content/docs/r2/reference/unicode-interoperability.mdx
+++ b/src/content/docs/r2/reference/unicode-interoperability.mdx
@@ -16,8 +16,8 @@ R2 preserves the encoding for display though. When you list the objects, you wil
 
 There are still some platform-specific differences to consider:
 
-- Windows and macOS filenames are case-insensitive while R2 and Linux are not.
-- Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
-- Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
+* Windows and macOS filenames are case-insensitive while R2 and Linux are not.
+* Windows console support for Unicode can be error-prone. Make sure to run `chcp 65001` before using command-line tools or use Cygwin if your object names appear to be incorrect.
+* Linux allows distinct files that are unicode-equivalent because filenames are byte streams. Unicode-equivalent filenames on Linux will point to the same R2 object.
 
 If it is important for you to be able to bypass the unicode equivalence and use byte-oriented key names, contact your Cloudflare account team.
diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx
index 1025cfea8f7c9bb..0c041c84fc44833 100644
--- a/src/content/docs/r2/tutorials/cloudflare-access.mdx
+++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx
@@ -49,7 +49,7 @@ To create an Access application for your R2 bucket:
    Ensure that your policies only allow the users within your organization that need access to this R2 bucket.
    :::
 
-5. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
+6. Follow the remaining [self-hosted application creation steps](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) to publish the application.
 
 ## 3. Connect a custom domain
 
diff --git a/src/content/docs/r2/tutorials/mastodon.mdx b/src/content/docs/r2/tutorials/mastodon.mdx
index dd7a6b339aace64..3a1bb7b0eae2ed8 100644
--- a/src/content/docs/r2/tutorials/mastodon.mdx
+++ b/src/content/docs/r2/tutorials/mastodon.mdx
@@ -23,8 +23,10 @@ Different from the default hostname of your Mastodon instance, object storage fo
 
 :::note
 
+
 If you move from R2 to another S3 compatible service later on, you can continue using the same hostname determined in this step. We do not recommend changing the hostname after the instance has been running to avoid breaking historical file references. In such a scenario, [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) can be used to instruct requests reaching the previous hostname to refer to the new hostname.
 
+
 :::
 
 ### 2. Create and set up an R2 bucket
@@ -32,7 +34,6 @@ If you move from R2 to another S3 compatible service later on, you can continue
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select **Create bucket**.
 3. Enter your bucket name and then select **Create bucket**. This name is internal when setting up your Mastodon instance and is not publicly accessible.
 4. Once the bucket is created, navigate to the **Settings** tab of this bucket and copy the value of **S3 API**.
diff --git a/src/content/docs/r2/tutorials/postman.mdx b/src/content/docs/r2/tutorials/postman.mdx
index 4bec7f80443cc16..2c8fbc313867b2b 100644
--- a/src/content/docs/r2/tutorials/postman.mdx
+++ b/src/content/docs/r2/tutorials/postman.mdx
@@ -11,7 +11,7 @@ products:
 
 import { DashButton } from "~/components";
 
-Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290) includes a complete list of operations supported by the platform.
+Postman is an API platform that makes interacting with APIs easier. This guide will explain how to use Postman to make authenticated R2 requests to create a bucket, upload a new object, and then retrieve the object. The R2 [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290) includes a complete list of operations supported by the platform.
 
 ## 1. Purchase R2
 
@@ -19,11 +19,11 @@ This guide assumes that you have made a Cloudflare account and purchased R2.
 
 ## 2. Explore R2 in Postman
 
-Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
+Explore R2's publicly available [Postman collection](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290). The collection is organized into a `Buckets` folder for bucket-level operations and an `Objects` folder for object-level operations. Operations in the `Objects > Upload` folder allow for adding new objects to R2.
 
 ## 3. Configure your R2 credentials
 
-In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
+In the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation), select the **Cloudflare R2** collection and navigate to the **Variables** tab. In **Variables**, you can set variables within the R2 collection. They will be used to authenticate and interact with the R2 platform. Remember to always select **Save** after updating a variable.
 
 To execute basic operations, you must set the `account-id`, `r2-access-key-id`, and `r2-secret-access-key` variables in the Postman dashboard > **Variables**.
 
@@ -32,9 +32,8 @@ To do this:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. In **R2**, under **Manage R2 API Tokens** on the right side of the dashboard, copy your Cloudflare account ID.
-3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation).
+3. Go back to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation).
 4. Set the **CURRENT VALUE** of `account-id` to your Cloudflare account ID and select **Save**.
 
 Next, generate an R2 API token:
@@ -42,7 +41,6 @@ Next, generate an R2 API token:
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. On the right hand sidebar, select **Manage R2 API Tokens**.
 3. Select **Create API token**.
 4. Name your token **Postman** by selecting the pencil icon next to the API name and grant it the **Edit** permission.
@@ -51,7 +49,7 @@ Guard this token and the **Access Key ID** and **Secret Access Key** closely. Yo
 
 After you have created your API token in the Cloudflare dashboard:
 
-1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share&creator=20913290&ctx=documentation) > **Variables**.
+1. Go to the [Postman dashboard](https://www.postman.com/cloudflare-r2/workspace/cloudflare-r2/collection/20913290-14ddd8d8-3212-490d-8647-88c9dc557659?action=share\&creator=20913290\&ctx=documentation) > **Variables**.
 2. Copy `Access Key ID` value from the Cloudflare dashboard and paste it into Postman’s `r2-access-key-id` variable value and select **Save**.
 3. Copy the `Secret Access Key` value from the Cloudflare dashboard and paste it into Postman’s `r2-secret-access-key` variable value and select **Save**.
 
diff --git a/src/content/docs/r2/video-tutorials.mdx b/src/content/docs/r2/video-tutorials.mdx
index f92a3914495462c..67585e1469ac91a 100644
--- a/src/content/docs/r2/video-tutorials.mdx
+++ b/src/content/docs/r2/video-tutorials.mdx
@@ -12,9 +12,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Introduction to R2"
-		description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
-		href="/learning-paths/r2-intro/series/r2-1/"
-	/>
+    <LinkCard
+        title="Introduction to R2"
+        description="Learn about Cloudflare R2, an object storage solution designed to handle your data and files efficiently. It is ideal for storing large media files, creating data lakes, or delivering web assets."
+        href="/learning-paths/r2-intro/series/r2-1/"
+    />
 </CardGrid>
diff --git a/src/content/docs/radar/concepts/index.mdx b/src/content/docs/radar/concepts/index.mdx
index e439f4733f5f884..e8c3c876f284ebb 100644
--- a/src/content/docs/radar/concepts/index.mdx
+++ b/src/content/docs/radar/concepts/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/concepts/normalization.mdx b/src/content/docs/radar/concepts/normalization.mdx
index 3a2a09e5b4ebd78..dbf55dfbe42a9f7 100644
--- a/src/content/docs/radar/concepts/normalization.mdx
+++ b/src/content/docs/radar/concepts/normalization.mdx
@@ -19,7 +19,7 @@ Refer to the `result.meta.normalization` property in the response to check which
 | `PERCENTAGE`            | Values represent percentages.                                                                                                                                                    |
 | `PERCENTAGE_CHANGE`     | Values represent a [percentage change](https://en.wikipedia.org/wiki/Relative_change_and_difference#Percentage_change) from a baseline period.                                   |
 | `OVERLAPPED_PERCENTAGE` | Values represent percentages that exceed 100% due to overlap.                                                                                                                    |
-| `MIN_MAX`               | Values have been normalized using [min-max](<https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_(min-max_normalization)>).                                                  |
+| `MIN_MAX`               | Values have been normalized using [min-max](https://en.wikipedia.org/wiki/Feature_scaling#Rescaling_\(min-max_normalization\)).                                                  |
 | `MIN0_MAX`              | Values have been normalized using min-max, but setting the minimum value to `0`. Equivalent to a proportion of the maximum value in the entire response, scaled between 0 and 1. |
 | `RAW_VALUES`            | Values are raw and have not been changed.                                                                                                                                        |
 
diff --git a/src/content/docs/radar/get-started/configure-alerts.mdx b/src/content/docs/radar/get-started/configure-alerts.mdx
index 64ad4396db7c424..6e7641992176d98 100644
--- a/src/content/docs/radar/get-started/configure-alerts.mdx
+++ b/src/content/docs/radar/get-started/configure-alerts.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications when Radar detects changes impacting countries, regions, or autonomous systems.
 
diff --git a/src/content/docs/radar/get-started/embed.mdx b/src/content/docs/radar/get-started/embed.mdx
index bf036cde8f960ad..249eccb402d8918 100644
--- a/src/content/docs/radar/get-started/embed.mdx
+++ b/src/content/docs/radar/get-started/embed.mdx
@@ -25,8 +25,8 @@ Charts supporting this feature will have a share icon next to its description.
 
 1. Select the Share icon next to the description of the chart you wish to share.
 2. Select between Fixed Time and Real Time.
-   - Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
-   - Fixed Time will always display a chart with only the currently visible data points.
+   * Real Time uses a “sliding window” based on the selected date range, and will display data points looking back over that duration from the current date/time.
+   * Fixed Time will always display a chart with only the currently visible data points.
 3. Select Copy Code and paste the code into your web page.
 
 **Note**: Your current selections, such as date range, location, autonomous system (ASN), and visible series, will be reflected in the shared chart.
diff --git a/src/content/docs/radar/get-started/index.mdx b/src/content/docs/radar/get-started/index.mdx
index 809a736dd35ebc9..1ce36868a710f4f 100644
--- a/src/content/docs/radar/get-started/index.mdx
+++ b/src/content/docs/radar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/radar/get-started/making-comparisons.mdx b/src/content/docs/radar/get-started/making-comparisons.mdx
index 984fcafb3a77490..9bffd560f9e690b 100644
--- a/src/content/docs/radar/get-started/making-comparisons.mdx
+++ b/src/content/docs/radar/get-started/making-comparisons.mdx
@@ -35,26 +35,26 @@ The response (shortened below for brevity) uses the provided `name` property to
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"us_data": {
-			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
-			"values": ["0.871752", "1"]
-		},
-		"pt_data": {
-			"timestamps": ["2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z"],
-			"values": ["0.020457", "0.012313"]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-10-26T17:00:00Z",
-				"endTime": "2022-11-02T17:00:00Z"
-			},
-			"aggInterval": "ONE_HOUR"
+  "success": true,
+  "errors": [],
+  "result": {
+    "us_data": {
+      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
+      "values": [ "0.871752", "1" ]
+    },
+    "pt_data": {
+      "timestamps": [ "2022-10-26T17:00:00Z", "2022-11-02T15:00:00Z" ],
+      "values": [ "0.020457", "0.012313" ]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-10-26T17:00:00Z",
+        "endTime": "2022-11-02T17:00:00Z"
+      },
+      "aggInterval": "ONE_HOUR",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -81,24 +81,14 @@ Now, in the `result` property, you should get something like this:
 
 ```json
 {
-	"this_week": {
-		"timestamps": [
-			"2022-10-27T13:00:00Z",
-			"2022-10-27T14:00:00Z",
-			"...",
-			"2022-11-03T12:00:00Z"
-		],
-		"values": ["0.794321", "1", "...", "0.718433"]
-	},
-	"previous_week": {
-		"timestamps": [
-			"2022-10-20T13:00:00Z",
-			"2022-10-20T14:00:00Z",
-			"...",
-			"2022-10-27T12:00:00Z"
-		],
-		"values": ["0.774392", "0.835071", "...", "0.720181"]
-	}
+  "this_week": {
+    "timestamps": [ "2022-10-27T13:00:00Z", "2022-10-27T14:00:00Z", "...", "2022-11-03T12:00:00Z" ],
+    "values": [ "0.794321", "1", "...", "0.718433"]
+  },
+  "previous_week": {
+    "timestamps": [ "2022-10-20T13:00:00Z", "2022-10-20T14:00:00Z", "...", "2022-10-27T12:00:00Z" ],
+    "values": [ "0.774392", "0.835071", "...", "0.720181"]
+  }
 }
 ```
 
@@ -128,21 +118,11 @@ The `result` property should return a response like this:
 ```json
 {
 	"tonga": {
-		"timestamps": [
-			"2022-10-15T02:00:00Z",
-			"2022-10-15T03:00:00Z",
-			"2022-10-15T04:00:00Z",
-			"2022-10-15T05:00:00Z"
-		],
+		"timestamps": ["2022-10-15T02:00:00Z", "2022-10-15T03:00:00Z", "2022-10-15T04:00:00Z", "2022-10-15T05:00:00Z"],
 		"values": ["1.0", "0.832473", "0.820083", "0.79408"]
 	},
 	"tonga_outage": {
-		"timestamps": [
-			"2022-01-15T02:00:00Z",
-			"2022-01-15T03:00:00Z",
-			"2022-01-15T04:00:00Z",
-			"2022-01-15T05:00:00Z"
-		],
+		"timestamps": ["2022-01-15T02:00:00Z", "2022-01-15T03:00:00Z", "2022-01-15T04:00:00Z", "2022-01-15T05:00:00Z"],
 		"values": ["0.354105", "0.357287", "0.181811", "0.044198"]
 	}
 }
diff --git a/src/content/docs/radar/investigate/application-layer-attacks.mdx b/src/content/docs/radar/investigate/application-layer-attacks.mdx
index 62b6591ff068b45..bef19dc325ce63d 100644
--- a/src/content/docs/radar/investigate/application-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/application-layer-attacks.mdx
@@ -40,27 +40,27 @@ From the abbreviated response below, we can conclude that distributed denial-of-
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks": {
-			"timestamps": ["2022-11-05T11:00:00Z", ".."],
-			"ddos": ["53.824302", "54.305823", ".."],
-			"waf": ["39.760956", "39.31228", ".."],
-			"ip_reputation": ["5.623487", "5.485468", ".."],
-			"access_rules": ["0.648368", "0.676456", ".."],
-			"bot_management": ["0.139733", "0.217155", ".."],
-			"api_shield": ["0.003154", "0.002819", ".."],
-			"data_loss_prevention": ["0.0", "0.0", ".."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-05T11:00:00Z",
-				"endTime": "2022-11-06T11:00:00Z"
-			}
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks": {
+      "timestamps": ["2022-11-05T11:00:00Z", ".."],
+      "ddos": ["53.824302", "54.305823",  ".."],
+      "waf": ["39.760956", "39.31228",  ".."],
+      "ip_reputation": ["5.623487", "5.485468",  ".."],
+      "access_rules": ["0.648368", "0.676456",  ".."],
+      "bot_management": ["0.139733", "0.217155",  ".."],
+      "api_shield": ["0.003154", "0.002819",  ".."],
+      "data_loss_prevention": ["0.0", "0.0",  ".."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-05T11:00:00Z",
+        "endTime": "2022-11-06T11:00:00Z"
+      },
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -79,9 +79,9 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"attacks_gb": {
 			"waf": "75.012138",
 			"ddos": "18.539149",
@@ -90,10 +90,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/summary?location
 			"bot_management": "0.131998",
 			"api_shield": "0.003178",
 			"data_loss_prevention": "0.0"
-		},
+  	},
 		"meta": {
 			// ...
-		}
+    }
 	}
 }
 ```
@@ -115,10 +115,10 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks_target": [
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks_target": [
 			{
 				"targetCountryName": "Belgium",
 				"targetCountryAlpha2": "BE",
@@ -150,14 +150,14 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer7/top/locations/ta
 				"rank": 5
 			}
 		],
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-05T12:00:00Z",
-				"endTime": "2022-11-06T12:00:00Z"
-			}
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-05T12:00:00Z",
+        "endTime": "2022-11-06T12:00:00Z"
+      },
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
@@ -178,9 +178,9 @@ A typical response will be similar to the following:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"originCountryName": "United States",
@@ -223,10 +223,10 @@ A typical response will be similar to the following:
 				"rank": 5
 			}
 		],
-		"meta": {
+    "meta": {
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/dns.mdx b/src/content/docs/radar/investigate/dns.mdx
index 837edba24ef5632..59db1f37eb09dbc 100644
--- a/src/content/docs/radar/investigate/dns.mdx
+++ b/src/content/docs/radar/investigate/dns.mdx
@@ -27,9 +27,9 @@ The response shows that most queries come from the United States and Brazil:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "US",
@@ -43,9 +43,9 @@ The response shows that most queries come from the United States and Brazil:
 			}
 		],
 		"meta": {
-			// ...
-		}
-	}
+      // ...
+    }
+  }
 }
 ```
 
@@ -60,9 +60,9 @@ Returns the following response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"top_0": [
 			{
 				"clientCountryAlpha2": "RU",
@@ -76,9 +76,9 @@ Returns the following response:
 			}
 		],
 		"meta": {
-			// ...
-		}
-	}
+      // ...
+    }
+  }
 }
 ```
 
@@ -86,7 +86,7 @@ As expected, most queries come from Russia.
 
 :::note
 
-Note that these examples return the total number of DNS queries from a location to a hostname, _out_ of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
+Note that these examples return the total number of DNS queries from a location to a hostname, *out* of the total DNS queries to a given hostname. In this sense, it is expected that locations with higher population numbers — like the United States — frequently appear in the top spots, even if the actual percentage is low.
 :::
 
 You can also provide multiple hostnames. Refer to [Get DNS top locations](/api/resources/radar/subresources/dns/subresources/top/methods/locations/) for more information. This is useful when the application you want to explore uses several hostnames to serve its content (like a hostname for the main website, another hostname dedicated to its API, etc.).
diff --git a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
index 26d9f65fea55f7d..9c025150aa46f67 100644
--- a/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
+++ b/src/content/docs/radar/investigate/domain-ranking-datasets.mdx
@@ -8,10 +8,10 @@ products:
   - radar
 ---
 
-Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/), Cloudflare's public DNS resolver. Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
+Cloudflare regularly generates a domain ranking based on DNS queries to [1.1.1.1](/1.1.1.1/),  Cloudflare's public DNS resolver.  Refer to the [blog post](https://blog.cloudflare.com/radar-domain-rankings/) for a deep dive. In short, Cloudflare generates two types of listings:
 
-- An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
-- An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
+* An ordered list of the top 100 most popular domains globally and per country. This includes the last 24 hours and is updated daily.
+* An unordered global most popular domains dataset, divided into buckets of the following number of domains: 200, 500, 1,000, 2,000, 5,000, 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000. It includes the last seven days and is updated weekly.
 
 ## List of endpoints
 
@@ -26,10 +26,10 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"top_0": [
+  "success": true,
+  "errors": [],
+  "result": {
+    "top_0": [
 			{
 				"rank": 1,
 				"domain": "google.com"
@@ -50,8 +50,8 @@ curl "https://api.cloudflare.com/client/v4/radar/ranking/top?name=top&limit=5" \
 				"rank": 5,
 				"domain": "apple.com"
 			}
-		]
-	},
+    ]
+  },
 	"meta": {
 		// ...
 	}
@@ -75,21 +75,24 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets?limit=10&datasetType=R
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"datasets": [
 			{
 				"id": 213,
 				"title": "Top 1000000 ranking domains",
 				"description": "Unordered top 1000000 from 2023-01-02 to 2023-01-09",
 				"type": "RANKING_BUCKET",
-				"tags": ["GLOBAL", "top_1000000"],
+				"tags": [
+					"GLOBAL",
+					"top_1000000"
+				],
 				"meta": {
 					"top": 1000000
 				},
 				"alias": "ranking_top_1000000"
-			}
+			},
 			// ...
 		]
 	}
@@ -111,9 +114,9 @@ curl "https://api.cloudflare.com/client/v4/radar/datasets/download" \
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"dataset": {
 			"url": "https://example.com/download"
 		}
diff --git a/src/content/docs/radar/investigate/http-requests.mdx b/src/content/docs/radar/investigate/http-requests.mdx
index f850973ae9af912..8fcdba8ef35ed24 100644
--- a/src/content/docs/radar/investigate/http-requests.mdx
+++ b/src/content/docs/radar/investigate/http-requests.mdx
@@ -19,9 +19,9 @@ Most of the charts in the [Adoption and Usage](https://radar.cloudflare.com/adop
 
 These endpoints can be broadly split into:
 
-- `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
-- `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
-- `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
+* `timeseries`: A time series of a group of metrics. For example, when looking at IP version, displays an IPv4 time series and an IPv6 time series.
+* `summary`: Displays a summary of a group of metrics over the specified time range. For example, IPv4 traffic percentage out of the total HTTP traffic during that time period.
+* `top`: A list of the top locations or [Autonomous Systems](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-an-autonomous-system/) (ASes) ranked by adoption of a specific metric. For example, top locations by mobile device traffic (like which locations have a higher percentage of mobile traffic out of the total traffic for that location).
 
 ## List of endpoints
 
@@ -40,29 +40,29 @@ Here is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"human": {
-			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-			"mobile": ["52.5532", "52.146628", ".."],
-			"desktop": ["47.394791", "47.800731", ".."],
-			"other": ["0.052009", "0.052642", ".."]
-		},
-		"bot": {
-			"timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
-			"desktop": ["83.833892", "84.017711", ".."],
-			"mobile": ["16.156748", "15.969936", ".."],
-			"other": ["0.00936", "0.012353", ".."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-03T13:00:00Z",
-				"endTime": "2022-11-04T13:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
-		}
-	}
+  "success": true,
+  "errors": [],
+  "result": {
+    "human": {
+      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+      "mobile": ["52.5532", "52.146628", ".."],
+      "desktop": ["47.394791", "47.800731", ".."],
+      "other": ["0.052009", "0.052642", ".."]
+    },
+    "bot": {
+      "timestamps": ["2022-11-03T13:00:00Z", "2022-11-03T14:00:00Z", ".."],
+      "desktop": ["83.833892", "84.017711", ".."],
+      "mobile": ["16.156748", "15.969936", ".."],
+      "other": ["0.00936", "0.012353", ".."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-03T13:00:00Z",
+        "endTime": "2022-11-04T13:00:00Z"
+      },
+      "normalization": "PERCENTAGE"
+    }
+  }
 }
 ```
 
@@ -90,9 +90,9 @@ Here is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"human": {
 			"mobile": "54.967243",
 			"desktop": "44.974006",
@@ -103,7 +103,7 @@ Here is the abbreviated response:
 			"mobile": "16.707455",
 			"other": "0.017093"
 		}
-	}
+  }
 }
 ```
 
@@ -122,9 +122,9 @@ This returns the following:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"human": {
 			"IPv4": "76.213647",
 			"IPv6": "23.786353"
@@ -133,7 +133,7 @@ This returns the following:
 			"IPv4": "91.492032",
 			"IPv6": "8.507968"
 		}
-	}
+  }
 }
 ```
 
@@ -156,9 +156,9 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"ipv6": [
 			{
 				"clientCountryAlpha2": "IN",
@@ -186,7 +186,7 @@ curl "https://api.cloudflare.com/client/v4/radar/http/top/locations/ip_version/I
 				"value": "39.1514"
 			}
 		]
-	}
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/index.mdx b/src/content/docs/radar/investigate/index.mdx
index 5c1a9cd5a898a6c..c377e8628eba30c 100644
--- a/src/content/docs/radar/investigate/index.mdx
+++ b/src/content/docs/radar/investigate/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Explore the different types of data available in Cloudflare Radar, from NetFlows (what feeds the [Internet Traffic Change](https://radar.cloudflare.com/) chart in Radar) to HTTP requests and DNS queries.
 
diff --git a/src/content/docs/radar/investigate/netflows.mdx b/src/content/docs/radar/investigate/netflows.mdx
index 3971efa9cabc498..1d7c85ee2290995 100644
--- a/src/content/docs/radar/investigate/netflows.mdx
+++ b/src/content/docs/radar/investigate/netflows.mdx
@@ -36,9 +36,9 @@ This is the abbreviated response:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS3243_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.565885", "0.586434", "..."]
@@ -64,9 +64,9 @@ The abbreviated response is:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
@@ -92,9 +92,9 @@ which would lead to a response like this:
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
+  "success": true,
+  "errors": [],
+  "result": {
 		"AS174_all": {
 			"timestamps": ["2022-11-08T14:00:00Z", "2022-11-08T15:00:00Z", "..."],
 			"values": ["0.917348", "1.0", "..."]
diff --git a/src/content/docs/radar/investigate/network-layer-attacks.mdx b/src/content/docs/radar/investigate/network-layer-attacks.mdx
index 56394fa33270271..edd685c50ae34f8 100644
--- a/src/content/docs/radar/investigate/network-layer-attacks.mdx
+++ b/src/content/docs/radar/investigate/network-layer-attacks.mdx
@@ -35,36 +35,36 @@ If we inspect the abbreviated response below, we can conclude that globally, at
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"global": {
-			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-			"udp": ["50.784034", "51.055221", "..."],
-			"tcp": ["49.213944", "48.943769", "..."],
-			"icmp": ["0.002023", "0.001009", "..."],
-			"gre": ["0.0", "0.0", "0.0", "..."]
-		},
-		"singapore": {
-			"timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
-			"tcp": ["79.605287", "83.943885", "..."],
-			"udp": ["20.394594", "16.056115", "..."],
-			"icmp": ["0.000119", "0.0", "..."],
-			"gre": ["0.0", "0.0", "..."]
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-06T13:00:00Z",
-				"endTime": "2022-11-07T13:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
+  "success": true,
+  "errors": [],
+  "result": {
+    "global": {
+      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+      "udp": ["50.784034", "51.055221", "..."],
+      "tcp": ["49.213944", "48.943769", "..."],
+      "icmp": ["0.002023", "0.001009", "..."],
+      "gre": ["0.0", "0.0", "0.0", "..."]
+    },
+    "singapore": {
+      "timestamps": ["2022-11-06T13:00:00Z", "2022-11-06T14:00:00Z", "..."],
+      "tcp": ["79.605287", "83.943885", "..."],
+      "udp": ["20.394594", "16.056115", "..."],
+      "icmp": ["0.000119", "0.0", "..."],
+      "gre": ["0.0", "0.0", "..."]
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-06T13:00:00Z",
+        "endTime": "2022-11-07T13:00:00Z"
+      },
+      "normalization": "PERCENTAGE",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
-We can also conclude that the distribution of network layer attacks coming from Singapore — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
+We can also conclude that the distribution of network layer attacks coming from Singapore  — or, more accurately, reaching Cloudflare's data center located in Singapore — differs quite a bit from the worldwide distribution. At those times, the distribution of network layer attacks clearly favors [TCP](https://www.cloudflare.com/learning/ddos/glossary/tcp-ip/).
 
 For more information refer to the [API reference](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) for this endpoint.
 
@@ -81,24 +81,24 @@ curl "https://api.cloudflare.com/client/v4/radar/attacks/layer3/summary?location
 
 ```json
 {
-	"success": true,
-	"errors": [],
-	"result": {
-		"attacks_ru": {
-			"udp": "86.682356",
-			"tcp": "11.928664",
-			"gre": "1.381015",
-			"icmp": "0.007965"
-		},
-		"meta": {
-			"dateRange": {
-				"startTime": "2022-11-06T15:00:00Z",
-				"endTime": "2022-11-07T15:00:00Z"
-			},
-			"normalization": "PERCENTAGE"
+  "success": true,
+  "errors": [],
+  "result": {
+    "attacks_ru": {
+      "udp": "86.682356",
+      "tcp": "11.928664",
+      "gre": "1.381015",
+      "icmp": "0.007965"
+    },
+    "meta": {
+      "dateRange": {
+        "startTime": "2022-11-06T15:00:00Z",
+        "endTime": "2022-11-07T15:00:00Z"
+      },
+      "normalization": "PERCENTAGE",
 			// ...
-		}
-	}
+    }
+  }
 }
 ```
 
diff --git a/src/content/docs/radar/investigate/outages.mdx b/src/content/docs/radar/investigate/outages.mdx
index 4627c42298d06d6..6d6f0d662f2a97e 100644
--- a/src/content/docs/radar/investigate/outages.mdx
+++ b/src/content/docs/radar/investigate/outages.mdx
@@ -12,13 +12,13 @@ products:
 
 Refer the [blog post](https://blog.cloudflare.com/announcing-cloudflare-radar-outage-center/) for more information but, in short, Radar provides the following information:
 
-- **Location**: Where was the outage?
-- **ASN**: What autonomous system experienced a disruption in connectivity?
-- **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
-- **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
-- **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
-- **Start time**: When did the outage start?
-- **End time**: When did the outage end?
+* **Location**: Where was the outage?
+* **ASN**: What autonomous system experienced a disruption in connectivity?
+* **Type**: How broad was the outage? Did connectivity fail nationwide, or at a sub-national level? Did just a single network provider have an outage?
+* **Scope**: If it was a sub-national/regional outage, what state or city was impacted? If it was a network-level outage, which one was it?
+* **Cause**: Insight into the likely cause of the outage, based on publicly available information. Historically, some outages have been government directed shutdowns, while others are caused by severe weather or natural disasters, or by infrastructure issues such as cable cuts, power outages, or filtering/blocking.
+* **Start time**: When did the outage start?
+* **End time**: When did the outage end?
 
 ## List of endpoints
 
diff --git a/src/content/docs/radar/investigate/url-scanner.mdx b/src/content/docs/radar/investigate/url-scanner.mdx
index ab5ce64f3fd1662..ec99e52a8ef0c7b 100644
--- a/src/content/docs/radar/investigate/url-scanner.mdx
+++ b/src/content/docs/radar/investigate/url-scanner.mdx
@@ -14,7 +14,7 @@ To better understand Internet usage around the world, use Cloudflare's URL Scann
 
 ## Use the API
 
-To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with _Account_ > _URL Scanner_ in the **Permissions** group, and select _Edit_ as the access level.
+To make your first URL scan using the API, you must obtain a URL Scanner specific [API token](/fundamentals/api/get-started/create-token/). Create a Custom Token with *Account* > *URL Scanner* in the **Permissions** group, and select *Edit* as the access level.
 
 Once you have the token, and you know your `account_id`, you are ready to make your first request to the API at `https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/`.
 
@@ -37,11 +37,11 @@ A successful response will have a status code of `200` and be similar to the fol
 
 ```json
 {
-	"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-	"api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
-	"visibility": "public",
-	"url": "https://www.example.com",
-	"message": "Submission successful"
+  "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+  "api": "https://api.cloudflare.com/client/v4/accounts/<accountId>/urlscanner/v2/result/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
+  "visibility": "public",
+  "url": "https://www.example.com",
+  "message": "Submission successful"
 }
 ```
 
@@ -56,9 +56,11 @@ Here's an example request body with some custom configuration options:
 ```json
 {
 	"url": "https://example.com",
-	"screenshotsResolutions": ["desktop", "mobile", "tablet"],
-	"customagent": "XXX-my-user-agent",
-	"referer": "example",
+	"screenshotsResolutions": [
+		"desktop", "mobile", "tablet"
+	],
+  "customagent": "XXX-my-user-agent",
+  "referer": "example",
 	"customHeaders": {
 		"Authorization": "xxx-token"
 	},
@@ -66,7 +68,7 @@ Here's an example request body with some custom configuration options:
 }
 ```
 
-Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In effect, only users with knowledge of the scan ID will be able to access it.
+Above, the visibility level is set as `Unlisted`, which means that the scan report won't be included in the [recent scans](https://radar.cloudflare.com/scan#recent-scans) list nor in search results. In  effect, only users with knowledge of the scan ID will be able to access it.
 
 There will also be three screenshots taken of the webpage, one per target device type. The [`User-Agent`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) will be set as "XXX-my-user-agent". Note that you can set any custom HTTP header, including [Authorization](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Authorization).
 
@@ -82,38 +84,38 @@ While the scan is in progress, the HTTP status code will be `404`; once it is fi
 
 The response will include, among others, the following top properties:
 
-- `task` - Information on the scan submission.
-- `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
-- `data.requests` - Request chains involved in the page load.
-- `data.cookies` - Cookies set by the page.
-- `data.globals` - Non-standard JavaScript global variables.
-- `data.console` - Console logs.
-- `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
-- `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
-- `lists.ips` - IPs contacted.
-- `lists.asns` - AS Numbers contacted.
-- `lists.domains` - Hostnames contacted, including `dns` record information.
-- `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
-- `lists.certificates` - TLS certificates of HTTP responses.
-- `verdicts` - Verdicts on malicious content.
+* `task` - Information on the scan submission.
+* `page` - Information pertaining to the primary response, for example IP address, ASN, server, and page redirect history.
+* `data.requests` - Request chains involved in the page load.
+* `data.cookies` - Cookies set by the page.
+* `data.globals` - Non-standard JavaScript global variables.
+* `data.console` - Console logs.
+* `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
+* `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geolocation information, and others.
+* `lists.ips` - IPs contacted.
+* `lists.asns` - AS Numbers contacted.
+* `lists.domains` - Hostnames contacted, including `dns` record information.
+* `lists.hashes` - Hashes of response bodies, of the main page HTML structure, screenshots, and favicons.
+* `lists.certificates` - TLS certificates of HTTP responses.
+* `verdicts` - Verdicts on malicious content.
 
 Some examples of more specific properties include:
 
-- `task.uuid` - ID of the scan.
-- `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
-- `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
-- `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
-- `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
-- `meta.processors.phishing` - What kind of phishing, if any, was detected.
-- `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
-- `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
-- `page.url` - URL of the primary request, after all HTTP redirects.
-- `page.country` - Country name from geolocation data associated with the main IP address contacted.
-- `page.history` - Main page history, including any HTTP redirects.
-- `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
-- `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
-- `page.favicon.hash` - MD5 hash of the favicon.
-- `verdicts.overall.malicious` - Whether the website was considered malicious _at the time of the scan_. Please check the remaining properties for each subsystem(s) for specific threats detected.
+* `task.uuid` - ID of the scan.
+* `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
+* `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
+* `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
+* `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
+* `meta.processors.phishing` - What kind of phishing, if any, was detected.
+* `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
+* `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
+* `page.url` - URL of the primary request, after all HTTP redirects.
+* `page.country` - Country name from geolocation data associated with the main IP address contacted.
+* `page.history` - Main page history, including any HTTP redirects.
+* `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
+* `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.
+* `page.favicon.hash` - MD5 hash of the favicon.
+* `verdicts.overall.malicious` - Whether the website was considered malicious *at the time of the scan*. Please check the remaining properties for each subsystem(s) for specific threats detected.
 
 The [Get URL Scan](/api/resources/url_scanner/subresources/scans/methods/get/) API endpoint documentation contains the full response schema.
 
@@ -130,6 +132,7 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/v2/s
 --header "Authorization: Bearer <API_TOKEN>"
 ```
 
+
 If, instead, you wanted to search for scans that made at least one request to the hostname `cdnjs.cloudflare.com`, for example sites that use a JavaScript library hosted at `cdnjs.cloudflare.com`, use the query parameter `hostname=cdnjs.cloudflare.com`:
 
 ```bash
@@ -150,13 +153,14 @@ Some other example queries:
 
 Go to [Search URL scans](/api/resources/url_scanner/subresources/scans/methods/list/) in the API documentation for the full list of available options.
 
+
 ### Security Center
 
 Alternatively, you can search in the Security Center:
 
 1. In the Cloudflare dashboard, go to the **Investigate** page.
 
-   <DashButton url="/?to=/:account/security-center/investigate" />
+	 <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your query and select **Search**.
 
@@ -172,7 +176,7 @@ To scan a URL based on your geographic location:
 2. Go to **Location** > Select which country to scan the URL from.
 3. Select **Scan now**.
 
-You can also use the [API](<https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20>) to scan a URL from a specific location.
+You can also use the [API](https://developers.cloudflare.com/api/resources/url_scanner/subresources/scans/methods/create/#(params)%20default%20%3E%20(param)%20account_id%20%3E%20) to scan a URL from a specific location.
 
 In Security Center, you can retrieve pre-filtered information by:
 
@@ -183,4 +187,4 @@ In Security Center, you can retrieve pre-filtered information by:
 - Identical ASN
 - Identical IP
 - Identical domain
-- Identical final URL (after all redirections)
+- Identical final URL (after all redirections)
\ No newline at end of file
diff --git a/src/content/docs/radar/mcp-server.mdx b/src/content/docs/radar/mcp-server.mdx
index 56303e7fd5ac8ad..ef902ec41e498a5 100644
--- a/src/content/docs/radar/mcp-server.mdx
+++ b/src/content/docs/radar/mcp-server.mdx
@@ -10,4 +10,4 @@ sidebar:
     variant: note
 products:
   - radar
----
+---
\ No newline at end of file
diff --git a/src/content/docs/radar/reference/index.mdx b/src/content/docs/radar/reference/index.mdx
index 1223e257fc2e24e..605b54567f61ed5 100644
--- a/src/content/docs/radar/reference/index.mdx
+++ b/src/content/docs/radar/reference/index.mdx
@@ -8,7 +8,7 @@ products:
   - radar
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Review reference information related to Cloudflare Radar:
 
diff --git a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
index d08ecc4c77e6915..7b84e9fcb6eff4b 100644
--- a/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
+++ b/src/content/docs/radar/reference/quarterly-ddos-reports.mdx
@@ -6,7 +6,7 @@ products:
   - radar
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Quarterly DDoS threat reports provide a comprehensive overview of <GlossaryTooltip term="distributed denial-of-service (DDoS) attack">DDoS attack</GlossaryTooltip> insights and trends over a three-month period.
 
@@ -14,7 +14,7 @@ Thanks to our vast network, Cloudflare provides insights on the evolving threat
 
 Find the latest quarterly DDoS threat reports in the [**Reports**](https://radar.cloudflare.com/reports) section of Cloudflare Radar.
 
----
+***
 
 ## Methodologies
 
@@ -58,7 +58,7 @@ To calculate the attack size, duration, attack vectors, and emerging threats, Cl
 
 However, in the **Network layer attack distribution** graph of the [**Security & Attacks**](https://radar.cloudflare.com/security-and-attacks) Radar page these trends are calculated by number of bytes instead. Since attacks may vary greatly in number of bytes from one another, this could lead to trends differing between the quarterly reports and the graph displayed in Cloudflare Radar.
 
----
+***
 
 ## Final remarks
 
diff --git a/src/content/docs/randomness-beacon/about/background.mdx b/src/content/docs/randomness-beacon/about/background.mdx
index 3985a768398b9d4..34ad6ab86602697 100644
--- a/src/content/docs/randomness-beacon/about/background.mdx
+++ b/src/content/docs/randomness-beacon/about/background.mdx
@@ -11,7 +11,7 @@ products:
 description: History and development of the drand project.
 ---
 
-Over the years, a generation of public randomness (often referred to as _common coins_) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
+Over the years, a generation of public randomness (often referred to as *common coins*) has attracted interest from the cryptography research community. Many distributed systems, including various consensus mechanisms, anonymity networks such as Tor, or blockchain systems, assume access to such public randomness. However, it remained a major unsolved issue to generate public randomness in a distributed, scalable, and robust way. Currently, there is no service deployed to produce this type of randomness. The only choice is a centralized, prototype-only randomness beacon run by [NIST](https://www.nist.gov/).
 
 Realizing this, [Ewa Syta](http://ewa.syta.us/) started a project on [Scalable Bias-Resistant Distributed Randomness](https://eprint.iacr.org/2016/1067) during her PhD studies under the supervision of [Michael J. Fischer](http://www.cs.yale.edu/homes/fischer/) and [Bryan Ford](https://bford.info/) at Yale University. After Bryan moved to EPFL in 2015, the new members of the DEDIS team at EPFL ([Nicolas Gailly](https://github.com/nikkolasg/), [Linus Gasser](https://people.epfl.ch/linus.gasser), [Philipp Jovanovic](https://jovanovic.io/), [Ismail Khoffi](https://ismailkhoffi.com/), [Eleftherios Kokoris Kogias](https://lefteriskk.github.io/)) joined the project and together published a research paper at the [2017 IEEE Symposium on Security and Privacy](https://ieeexplore.ieee.org/abstract/document/7958592).
 
diff --git a/src/content/docs/randomness-beacon/about/future.mdx b/src/content/docs/randomness-beacon/about/future.mdx
index 76c17926bf29159..486975f9356ffc8 100644
--- a/src/content/docs/randomness-beacon/about/future.mdx
+++ b/src/content/docs/randomness-beacon/about/future.mdx
@@ -15,10 +15,10 @@ As of spring 2020, the drand network is production-ready and can now be consider
 
 While the project has reached a mature state, we believe there are several ways for drand to continue to evolve.
 
-- We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
+* We would like to continue to see reliable partners join the network; the more participants in the network, the stronger the guarantees.
 
-- We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
+* We would like to investigate how to generate public randomness in a post-quantum secure way (like, through isogeny, lattice, and so on).
 
-- We would like to consider standardization of the core drand protocol.
+* We would like to consider standardization of the core drand protocol.
 
 We are proud to be a part of these efforts and hope to see even more adoption of drand in third-party applications and systems.
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
index 0678464a6ad4525..59049a2b40a28d4 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/index.mdx
@@ -12,11 +12,11 @@ drand is an efficient randomness beacon daemon that utilizes pairing-based crypt
 
 This is an overview of the cryptographic building blocks drand uses to generate publicly-verifiable, unbiasable, and unpredictable randomness in a distributed manner.
 
-The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are _n_ participants, out of which at most _f\<n_ are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of _t-f+1_ nodes work together to successfully execute cryptographic operations.
+The drand beacon has two phases: a setup phase and a beacon phase. Generally, we assume that there are *n* participants, out of which at most *f\<n* are malicious. drand relies heavily on threshold cryptography primitives, where (at minimum) a threshold of *t-f+1* nodes work together to successfully execute cryptographic operations.
 
-Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where _t-of-n_ participants are required to sign a transaction using a threshold signature scheme.
+Threshold cryptography has many applications as it avoids single points of failure. One application is cryptocurrency multi-sig wallets, where *t-of-n* participants are required to sign a transaction using a threshold signature scheme.
 
 :::note[Note]
 
-This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts.
+This document is intended for a general audience. No cryptographic background knowledge is required to understand these concepts. 
 :::
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
index c39777be50f168c..b3c4780456fd4fd 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/randomness-generation.mdx
@@ -16,11 +16,11 @@ First, we explain pairing-based cryptography (PBC), which has become quite popul
 
 Pairing-based cryptography is based on bilinear groups `(𝔾1,𝔾2,𝔾𝑡)`, where `𝔾1`, `𝔾2`, and `𝔾𝑡` are cyclic groups of prime order `𝑝` with generators `𝑔1`, `𝑔2`, and `𝑔𝑡`, respectively, and a pairing operation `𝑒:𝔾1×𝔾2→𝔾𝑡` with these properties:
 
-- **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
+* **Bilinearity:** `∀𝑎,𝑏∈ℤ∗𝑝,∀𝑃∈𝔾1,∀𝑄∈𝔾2,` we have `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏`
 
-- **Non-degeneracy:** `𝑒≠1`
+* **Non-degeneracy:** `𝑒≠1`
 
-- **Computability:** There exists an efficient algorithm to compute `𝑒`.
+* **Computability:** There exists an efficient algorithm to compute `𝑒`.
   drand currently uses the Barreto-Lynn-Scott curve BLS12-381.
 
 ## BLS Signatures
diff --git a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
index 27152a46a610de6..1931a7beb984bc1 100644
--- a/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
+++ b/src/content/docs/randomness-beacon/cryptographic-background/setup-phase.mdx
@@ -8,7 +8,7 @@ products:
 description: Learn about the distributed key generation phase.
 ---
 
-In the drand setup phase, you create a collective private and public key pair shared among _𝑛_ participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
+In the drand setup phase, you create a collective private and public key pair shared among *𝑛* participants. This is done through a `𝑡-of-𝑛` Distributed Key Generation (DKG) process and results in each participant receiving a copy of the collective public key plus a private key share of the collective private key — no individual node knows the collective **private** key. Each private key share can then be used to perform cryptographic threshold computations, such as generating threshold signatures, where at least `𝑡` contributions produced using the individual private key shares are required to successfully finish the collective operation.
 
 A DKG is performed in a fully distributed manner, avoiding any single points of failure. This is an overview of the different sub-components of the drand DKG implementation.
 
@@ -36,7 +36,7 @@ Note that you can use any subset of `𝑡-of-𝑛` shares to perform Lagrange in
 
 SSS scheme assumes that the dealer is honest, but this may not always hold in practice. A Verifiable Secret Sharing (VSS) scheme protects against malicious dealers by enabling participants to verify that their shares are consistent with those dealt to other nodes, ensuring that the shared secret can be correctly reconstructed later.
 
-drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A _cyclic group_ means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
+drand uses Feldman’s VSS scheme, an extension of SSS. Let `𝔾` denote a cyclic group of prime order `𝑝` in which computing discrete logarithms is intractable. A *cyclic group* means there exists a generator, `𝑔`, so that any element `𝑥∈𝔾` can be written as `𝑥=𝑔𝑎` for some `𝑎∈{0,…,𝑝−1}`.
 
 ### Share Distribution
 
diff --git a/src/content/docs/realtime/agents/index.mdx b/src/content/docs/realtime/agents/index.mdx
index 841ef041c51d3c4..251f1183eda51db 100644
--- a/src/content/docs/realtime/agents/index.mdx
+++ b/src/content/docs/realtime/agents/index.mdx
@@ -10,6 +10,6 @@ products:
   - realtime
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing/>
diff --git a/src/content/docs/realtime/realtimekit/ai/index.mdx b/src/content/docs/realtime/realtimekit/ai/index.mdx
index 0b4b56d2c3a2e40..69baea7896467dd 100644
--- a/src/content/docs/realtime/realtimekit/ai/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/index.mdx
@@ -17,7 +17,7 @@ RealtimeKit provides AI-powered features using Cloudflare's AI infrastructure to
 ## Available features
 
 | Feature                                                  | Description                                 |
-| -------------------------------------------------------- | ------------------------------------------- |
+| -------------------------------------------------------- | -----------------------------------------   |
 | [Transcription](/realtime/realtimekit/ai/transcription/) | Real-time and end-of-meeting speech-to-text |
 | [Summary](/realtime/realtimekit/ai/summary/)             | AI-generated meeting summaries              |
 
diff --git a/src/content/docs/realtime/realtimekit/ai/summary.mdx b/src/content/docs/realtime/realtimekit/ai/summary.mdx
index f541baa92f1c99c..47577ad2f26f95d 100644
--- a/src/content/docs/realtime/realtimekit/ai/summary.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/summary.mdx
@@ -20,44 +20,44 @@ Set `summarize_on_end: true` when [creating a meeting](/realtime/realtimekit/con
 
 ```json
 {
-	"title": "Product Review",
-	"ai_config": {
-		"transcription": {
-			"language": "en-US"
-		},
-		"summarization": {
-			"word_limit": 500,
-			"text_format": "markdown",
-			"summary_type": "team_meeting"
-		}
-	},
-	"summarize_on_end": true
+  "title": "Product Review",
+  "ai_config": {
+    "transcription": {
+      "language": "en-US"
+    },
+    "summarization": {
+      "word_limit": 500,
+      "text_format": "markdown",
+      "summary_type": "team_meeting"
+    }
+  },
+  "summarize_on_end": true
 }
 ```
 
 ## Configuration
 
-| Option         | Type   | Default      | Description                               |
-| -------------- | ------ | ------------ | ----------------------------------------- |
-| `word_limit`   | number | 300          | Summary length (150-1000 words)           |
-| `text_format`  | string | `plain_text` | Output format: `plain_text` or `markdown` |
-| `summary_type` | string | `general`    | Meeting context for tailored summaries    |
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `word_limit` | number | 300 | Summary length (150-1000 words) |
+| `text_format` | string | `plain_text` | Output format: `plain_text` or `markdown` |
+| `summary_type` | string | `general` | Meeting context for tailored summaries |
 
 ### Summary types
 
 Choose a type that matches your meeting for better results:
 
-| Type                 | Best for                     |
-| -------------------- | ---------------------------- |
-| `general`            | Any meeting (default)        |
-| `team_meeting`       | Regular team syncs           |
-| `daily_standup`      | Agile standups               |
-| `one_on_one_meeting` | 1:1 meetings                 |
-| `sales_call`         | Customer sales conversations |
-| `client_check_in`    | Client status updates        |
-| `interview`          | Job interviews               |
-| `lecture`            | Educational content          |
-| `code_review`        | Technical code reviews       |
+| Type | Best for |
+|------|----------|
+| `general` | Any meeting (default) |
+| `team_meeting` | Regular team syncs |
+| `daily_standup` | Agile standups |
+| `one_on_one_meeting` | 1:1 meetings |
+| `sales_call` | Customer sales conversations |
+| `client_check_in` | Client status updates |
+| `interview` | Job interviews |
+| `lecture` | Educational content |
+| `code_review` | Technical code reviews |
 
 ## Consume summaries
 
@@ -67,11 +67,11 @@ Configure `meeting.summary` event in [webhooks](/api/resources/realtime_kit/subr
 
 ```json
 {
-	"event": "meeting.summary",
-	"meetingId": "meeting-123",
-	"sessionId": "session-456",
-	"summaryDownloadUrl": "https://...",
-	"summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
+  "event": "meeting.summary",
+  "meetingId": "meeting-123",
+  "sessionId": "session-456",
+  "summaryDownloadUrl": "https://...",
+  "summaryDownloadUrlExpiry": "2024-08-14T10:15:30.000Z"
 }
 ```
 
@@ -103,19 +103,16 @@ With `text_format: "markdown"` and `summary_type: "team_meeting"`:
 ## Meeting Summary
 
 ### Key Discussion Points
-
 - Reviewed Q4 roadmap priorities
 - Discussed deployment timeline for v2.0
 - Identified blockers for the auth migration
 
 ### Action Items
-
 - @alice: Update design specs by Friday
 - @bob: Schedule security review
 - @charlie: Create migration runbook
 
 ### Decisions Made
-
 - Approved moving forward with Kubernetes migration
 - Delayed analytics dashboard to next sprint
 ```
diff --git a/src/content/docs/realtime/realtimekit/ai/transcription.mdx b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
index 0c3a1720bf0478a..fbedd591aeb9eb5 100644
--- a/src/content/docs/realtime/realtimekit/ai/transcription.mdx
+++ b/src/content/docs/realtime/realtimekit/ai/transcription.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 RealtimeKit provides two transcription modes powered by Cloudflare Workers AI:
 
 | Mode               | Model                                                                | Use Case                       |
-| ------------------ | -------------------------------------------------------------------- | ------------------------------ |
+| ----------------   | -------------------------------------------------------------------- | ------------------------------ |
 | **Real-time**      | [Deepgram Nova-3](/workers-ai/models/nova-3/)                        | Live captions during meeting   |
 | **End-of-meeting** | [Whisper Large v3 Turbo](/workers-ai/models/whisper-large-v3-turbo/) | Accurate offline transcription |
 
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
index f4de77a1ba6d15d..bfe857bd9ca8b92 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKAi.md
@@ -12,50 +12,48 @@ This module consists of the `ai` object which is used to interface with product'
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
 
-- [RTKAi](#module_RTKAi)
-  - _instance_
-    - [.telemetry](#module_RTKAi+telemetry)
-    - [.onTranscript(transcript)](#module_RTKAi+onTranscript)
-  - _static_
-    - [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
-    - [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
+
+* [RTKAi](#module_RTKAi)
+    * _instance_
+        * [.telemetry](#module_RTKAi+telemetry)
+        * [.onTranscript(transcript)](#module_RTKAi+onTranscript)
+    * _static_
+        * [.parseTranscript(transcriptData, [isPartialTranscript])](#module_RTKAi.parseTranscript)
+        * [.parseTranscripts(transcriptData)](#module_RTKAi.parseTranscripts)
 
 <a name="module_RTKAi+telemetry"></a>
 
 ### meeting.ai.telemetry
-
 **Kind**: instance property of [<code>RTKAi</code>](#module_RTKAi)  
 <a name="module_RTKAi+onTranscript"></a>
 
 ### meeting.ai.onTranscript(transcript)
+**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)  
 
-**Kind**: instance method of [<code>RTKAi</code>](#module_RTKAi)
-
-| Param      | Type                           | Description                                 |
-| ---------- | ------------------------------ | ------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | transcript | <code>TranscriptionData</code> | Transcript data received for a participant. |
 
 <a name="module_RTKAi.parseTranscript"></a>
 
 ### meeting.ai.parseTranscript(transcriptData, [isPartialTranscript])
-
 Parse a single line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param                 | Type                 | Default            | Description                       |
-| --------------------- | -------------------- | ------------------ | --------------------------------- |
-| transcriptData        | <code>string</code>  |                    | The transcript data to parse      |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| transcriptData | <code>string</code> |  | The transcript data to parse |
 | [isPartialTranscript] | <code>boolean</code> | <code>false</code> | Whether the transcript is partial |
 
 <a name="module_RTKAi.parseTranscripts"></a>
 
 ### meeting.ai.parseTranscripts(transcriptData)
-
 Parse a multi-line transcript
 
-**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)
+**Kind**: static method of [<code>RTKAi</code>](#module_RTKAi)  
 
-| Param          | Type                | Description                  |
-| -------------- | ------------------- | ---------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | transcriptData | <code>string</code> | The transcript data to parse |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
index c5262c512d5524e..f0dc2d5d09f31ea 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKChat.md
@@ -10,367 +10,340 @@ web_core_version: 1.2.4
 
 This is the chat module, which can be used to send and receive messages from the meeting.
 
-- [RTKChat](#module_RTKChat)
-  - [module.exports](#exp_module_RTKChat--module.exports) ⏏
-    - [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
-    - ~~[.messages](#module_RTKChat--module.exports+messages)~~
-    - [.telemetry](#module_RTKChat--module.exports+telemetry)
-    - [.pinned](#module_RTKChat--module.exports+pinned)
-    - [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
-    - [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
-    - [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
-    - [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
-    - [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
-    - [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
-    - [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
-    - [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
-    - [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
-    - [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
-    - [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
-    - [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
-    - [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
-    - [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
-    - [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
-    - [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
-    - ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
-    - ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
-    - [.pin(id)](#module_RTKChat--module.exports+pin)
-    - [.unpin(id)](#module_RTKChat--module.exports+unpin)
-    - [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
-    - [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
-    - [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
-    - ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
-    - ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
+
+* [RTKChat](#module_RTKChat)
+    * [module.exports](#exp_module_RTKChat--module.exports) ⏏
+        * [new module.exports(context, chatSocketHandler, self, participants)](#new_module_RTKChat--module.exports_new)
+        * ~~[.messages](#module_RTKChat--module.exports+messages)~~
+        * [.telemetry](#module_RTKChat--module.exports+telemetry)
+        * [.pinned](#module_RTKChat--module.exports+pinned)
+        * [.setMaxTextLimit(limit)](#module_RTKChat--module.exports+setMaxTextLimit)
+        * [.sendMessageInternal(message, [participantIds])](#module_RTKChat--module.exports+sendMessageInternal)
+        * [.sendTextMessageInternal(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessageInternal)
+        * [.sendImageMessageInternal(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessageInternal)
+        * [.sendFileMessageInternal(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessageInternal)
+        * [.updateRateLimits(num, period)](#module_RTKChat--module.exports+updateRateLimits)
+        * [.sendTextMessage(message, [peerIds])](#module_RTKChat--module.exports+sendTextMessage)
+        * [.sendCustomMessage(message, [peerIds])](#module_RTKChat--module.exports+sendCustomMessage)
+        * [.sendImageMessage(image, [peerIds])](#module_RTKChat--module.exports+sendImageMessage)
+        * [.sendFileMessage(file, [peerIds])](#module_RTKChat--module.exports+sendFileMessage)
+        * [.sendMessage(message, [participantIds])](#module_RTKChat--module.exports+sendMessage)
+        * [.editTextMessage(messageId, message)](#module_RTKChat--module.exports+editTextMessage)
+        * [.editImageMessage(messageId, image)](#module_RTKChat--module.exports+editImageMessage)
+        * [.editFileMessage(messageId, file)](#module_RTKChat--module.exports+editFileMessage)
+        * [.editMessage(messageId, message)](#module_RTKChat--module.exports+editMessage)
+        * [.deleteMessage(messageId)](#module_RTKChat--module.exports+deleteMessage)
+        * ~~[.getMessagesByUser(userId)](#module_RTKChat--module.exports+getMessagesByUser)~~
+        * ~~[.getMessagesByType(type)](#module_RTKChat--module.exports+getMessagesByType)~~
+        * [.pin(id)](#module_RTKChat--module.exports+pin)
+        * [.unpin(id)](#module_RTKChat--module.exports+unpin)
+        * [.fetchPublicMessages(options)](#module_RTKChat--module.exports+fetchPublicMessages)
+        * [.fetchPrivateMessages(options)](#module_RTKChat--module.exports+fetchPrivateMessages)
+        * [.fetchPinnedMessages(options)](#module_RTKChat--module.exports+fetchPinnedMessages)
+        * ~~[.getMessages(timeStamp, size, reversed, [offset])](#module_RTKChat--module.exports+getMessages)~~
+        * ~~[.searchMessages(query, [filters])](#module_RTKChat--module.exports+searchMessages)~~
 
 <a name="exp_module_RTKChat--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKChat--module.exports_new"></a>
 
 #### new module.exports(context, chatSocketHandler, self, participants)
 
-| Param             | Type                              |
-| ----------------- | --------------------------------- |
-| context           | <code>Context</code>              |
-| chatSocketHandler | <code>RTKChatSocketHandler</code> |
-| self              | <code>Self</code>                 |
-| participants      | <code>Participants</code>         |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| chatSocketHandler | <code>RTKChatSocketHandler</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
 
 <a name="module_RTKChat--module.exports+messages"></a>
 
 #### ~~module.exports.messages~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 <a name="module_RTKChat--module.exports+pinned"></a>
 
 #### module.exports.pinned
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 **Deprecated.**: This property is deprecated. Please use `fetchPinnedMessages()` instead.
 Returns an array of pinned messages.  
 <a name="module_RTKChat--module.exports+setMaxTextLimit"></a>
 
 #### module.exports.setMaxTextLimit(limit)
-
 Set the max character limit of a text message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                             |
-| ----- | ------------------- | --------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | limit | <code>number</code> | Max character limit for a text message. |
 
 <a name="module_RTKChat--module.exports+sendMessageInternal"></a>
 
 #### module.exports.sendMessageInternal(message, [participantIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param            | Type                              | Description                             |
-| ---------------- | --------------------------------- | --------------------------------------- |
-| message          | <code>MessagePayload</code>       | Message payload to send.                |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>MessagePayload</code> | Message payload to send. |
 | [participantIds] | <code>Array.&lt;string&gt;</code> | Participant ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendTextMessageInternal"></a>
 
 #### module.exports.sendTextMessageInternal(message, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                              | Description                      |
-| --------- | --------------------------------- | -------------------------------- |
-| message   | <code>string</code>               | Text message to send.            |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>string</code> | Text message to send. |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessageInternal"></a>
 
 #### module.exports.sendImageMessageInternal(image, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send.              |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | Image file to send. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessageInternal"></a>
 
 #### module.exports.sendFileMessageInternal(file, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | File to send.                    |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | File to send. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKChat--module.exports+sendTextMessage"></a>
 
 #### module.exports.sendTextMessage(message, [peerIds])
-
 Sends a chat text message to the room.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                              | Description                                |
-| --------- | --------------------------------- | ------------------------------------------ |
-| message   | <code>string</code>               | The message that must be sent to the room. |
-| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to.           |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>string</code> | The message that must be sent to the room. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendCustomMessage"></a>
 
 #### module.exports.sendCustomMessage(message, [peerIds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                              | Description                      |
-| --------- | --------------------------------- | -------------------------------- |
-| message   | <code>CustomMessagePayload</code> | Custom message payload.          |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>CustomMessagePayload</code> | Custom message payload. |
 | [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendImageMessage"></a>
 
 #### module.exports.sendImageMessage(image, [peerIds])
-
 Sends an image message to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent.    |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | The image that is to be sent. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendFileMessage"></a>
 
 #### module.exports.sendFileMessage(file, [peerIds])
-
 Sends a file to the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                                              | Description                      |
-| --------- | ------------------------------------------------- | -------------------------------- |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | A File object.                   |
-| [peerIds] | <code>Array.&lt;string&gt;</code>                 | Peer ids to send the message to. |
+| Param | Type | Description |
+| --- | --- | --- |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | A File object. |
+| [peerIds] | <code>Array.&lt;string&gt;</code> | Peer ids to send the message to. |
 
 <a name="module_RTKChat--module.exports+sendMessage"></a>
 
 #### module.exports.sendMessage(message, [participantIds])
-
 Sends a message to the meeting. This method can be used to send text, image,
 or file messages. The message type is determined by the key 'type' in `message`
 object.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param            | Type                              | Description                                              |
-| ---------------- | --------------------------------- | -------------------------------------------------------- |
-| message          | <code>MessagePayload</code>       | An object including the type and content of the message. |
-| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants.      |
+| Param | Type | Description |
+| --- | --- | --- |
+| message | <code>MessagePayload</code> | An object including the type and content of the message. |
+| [participantIds] | <code>Array.&lt;string&gt;</code> | An array including the userIds of the participants. |
 
 <a name="module_RTKChat--module.exports+editTextMessage"></a>
 
 #### module.exports.editTextMessage(messageId, message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                | Description                |
-| --------- | ------------------- | -------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | messageId | <code>string</code> | Id of the message to edit. |
-| message   | <code>string</code> | Updated text message.      |
+| message | <code>string</code> | Updated text message. |
 
 <a name="module_RTKChat--module.exports+editImageMessage"></a>
 
 #### module.exports.editImageMessage(messageId, image)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                |
-| --------- | ------------------------------------------------- | -------------------------- |
-| messageId | <code>string</code>                               | Id of the message to edit. |
-| image     | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file.        |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| image | <code>File</code> \| <code>ReactNativeFile</code> | Updated image file. |
 
 <a name="module_RTKChat--module.exports+editFileMessage"></a>
 
 #### module.exports.editFileMessage(messageId, file)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                                              | Description                |
-| --------- | ------------------------------------------------- | -------------------------- |
-| messageId | <code>string</code>                               | Id of the message to edit. |
-| file      | <code>File</code> \| <code>ReactNativeFile</code> | Updated file.              |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| file | <code>File</code> \| <code>ReactNativeFile</code> | Updated file. |
 
 <a name="module_RTKChat--module.exports+editMessage"></a>
 
 #### module.exports.editMessage(messageId, message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                        | Description                |
-| --------- | --------------------------- | -------------------------- |
-| messageId | <code>string</code>         | Id of the message to edit. |
-| message   | <code>MessagePayload</code> | Updated message payload.   |
+| Param | Type | Description |
+| --- | --- | --- |
+| messageId | <code>string</code> | Id of the message to edit. |
+| message | <code>MessagePayload</code> | Updated message payload. |
 
 <a name="module_RTKChat--module.exports+deleteMessage"></a>
 
 #### module.exports.deleteMessage(messageId)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
-
-| Param     | Type                | Description                  |
-| --------- | ------------------- | ---------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | messageId | <code>string</code> | Id of the message to delete. |
 
 <a name="module_RTKChat--module.exports+getMessagesByUser"></a>
 
 #### ~~module.exports.getMessagesByUser(userId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param  | Type                | Description                                    |
-| ------ | ------------------- | ---------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | userId | <code>string</code> | The user id of the user that sent the message. |
 
 <a name="module_RTKChat--module.exports+getMessagesByType"></a>
 
 #### ~~module.exports.getMessagesByType(type)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                                                                                                                                                                 | Description                                   |
-| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
-| type  | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
+| Param | Type | Description |
+| --- | --- | --- |
+| type | <code>&#x27;text&#x27;</code> \| <code>&#x27;image&#x27;</code> \| <code>&#x27;file&#x27;</code> \| <code>&#x27;custom&#x27;</code> \| <code>&#x27;poll&#x27;</code> | 'text', 'image', 'file', 'custom', or 'poll'. |
 
 <a name="module_RTKChat--module.exports+pin"></a>
 
 #### module.exports.pin(id)
-
 Pins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                    |
-| ----- | ------------------- | ------------------------------ |
-| id    | <code>string</code> | ID of the message to be pinned |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | ID of the message to be pinned |
 
 <a name="module_RTKChat--module.exports+unpin"></a>
 
 #### module.exports.unpin(id)
-
 Unpins a chat message
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param | Type                | Description                      |
-| ----- | ------------------- | -------------------------------- |
-| id    | <code>string</code> | ID of the message to be unpinned |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | ID of the message to be unpinned |
 
 <a name="module_RTKChat--module.exports+fetchPublicMessages"></a>
 
 #### module.exports.fetchPublicMessages(options)
-
 Fetches messages from the chat with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                             | Description                                                                                            |
-| ------- | -------------------------------- | ------------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching messages, including timestamp, limit, and direction for pagination. |
 
 <a name="module_RTKChat--module.exports+fetchPrivateMessages"></a>
 
 #### module.exports.fetchPrivateMessages(options)
-
 Fetches private messages between the current user and another participant with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                                     | Description                                                                                                                             |
-| ------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchPrivateMessagesOptions</code> | Configuration options for fetching private messages, including private RTKChat ID (User ID of the participant) and pagination settings. |
 
 <a name="module_RTKChat--module.exports+fetchPinnedMessages"></a>
 
 #### module.exports.fetchPinnedMessages(options)
-
 Fetches pinned messages with pagination.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param   | Type                             | Description                                                                                    |
-| ------- | -------------------------------- | ---------------------------------------------------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | options | <code>FetchMessageOptions</code> | Configuration options for fetching pinned messages, including timestamp, limit, and direction. |
 
 <a name="module_RTKChat--module.exports+getMessages"></a>
 
 #### ~~module.exports.getMessages(timeStamp, size, reversed, [offset])~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-| Param     | Type                 | Default        |
-| --------- | -------------------- | -------------- |
-| timeStamp | <code>number</code>  |                |
-| size      | <code>number</code>  |                |
-| reversed  | <code>boolean</code> |                |
-| [offset]  | <code>number</code>  | <code>0</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| timeStamp | <code>number</code> |  | 
+| size | <code>number</code> |  | 
+| reversed | <code>boolean</code> |  | 
+| [offset] | <code>number</code> | <code>0</code> | 
 
 <a name="module_RTKChat--module.exports+searchMessages"></a>
 
 #### ~~module.exports.searchMessages(query, [filters])~~
+***Deprecated***
 
-**_Deprecated_**
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKChat--module.exports)
+| Param | Type |
+| --- | --- |
+| query | <code>string</code> | 
+| [filters] | <code>SearchFilters</code> | 
 
-| Param     | Type                       |
-| --------- | -------------------------- |
-| query     | <code>string</code>        |
-| [filters] | <code>SearchFilters</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
index 05ce7315d3a789b..4f7519ff80810fe 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKConnectedMeetings.md
@@ -10,96 +10,91 @@ web_core_version: 1.2.4
 
 This consists of the methods to facilitate connected meetings
 
-- [RTKConnectedMeetings](#module_RTKConnectedMeetings)
-  - [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
-    - [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
-    - [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
-    - [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
-    - [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
-    - [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
-    - [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
-    - [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
+
+* [RTKConnectedMeetings](#module_RTKConnectedMeetings)
+    * [module.exports](#exp_module_RTKConnectedMeetings--module.exports) ⏏
+        * [new module.exports(context)](#new_module_RTKConnectedMeetings--module.exports_new)
+        * [.getRTKConnectedMeetings()](#module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings)
+        * [.createMeetings(request)](#module_RTKConnectedMeetings--module.exports+createMeetings)
+        * [.updateMeetings(request)](#module_RTKConnectedMeetings--module.exports+updateMeetings)
+        * [.deleteMeetings(meetingIds)](#module_RTKConnectedMeetings--module.exports+deleteMeetings)
+        * [.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)](#module_RTKConnectedMeetings--module.exports+moveParticipants)
+        * [.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)](#module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset)
 
 <a name="exp_module_RTKConnectedMeetings--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKConnectedMeetings--module.exports_new"></a>
 
 #### new module.exports(context)
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+getRTKConnectedMeetings"></a>
 
 #### module.exports.getRTKConnectedMeetings()
-
 get connected meeting state
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 <a name="module_RTKConnectedMeetings--module.exports+createMeetings"></a>
 
 #### module.exports.createMeetings(request)
-
 create connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param   | Type                                       |
-| ------- | ------------------------------------------ |
-| request | <code>Array.&lt;{title: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| request | <code>Array.&lt;{title: string}&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+updateMeetings"></a>
 
 #### module.exports.updateMeetings(request)
-
 update meeting title
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param   | Type                                                   |
-| ------- | ------------------------------------------------------ |
-| request | <code>Array.&lt;{id: string, title: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| request | <code>Array.&lt;{id: string, title: string}&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+deleteMeetings"></a>
 
 #### module.exports.deleteMeetings(meetingIds)
-
 delete connected meetings
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param      | Type                              |
-| ---------- | --------------------------------- |
-| meetingIds | <code>Array.&lt;string&gt;</code> |
+| Param | Type |
+| --- | --- |
+| meetingIds | <code>Array.&lt;string&gt;</code> | 
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipants"></a>
 
 #### module.exports.moveParticipants(sourceMeetingId, destinationMeetingId, participantIds)
-
 Trigger event to move participants
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
 
-| Param                | Type                              | Description                    |
-| -------------------- | --------------------------------- | ------------------------------ |
-| sourceMeetingId      | <code>string</code>               | id of source meeting           |
-| destinationMeetingId | <code>string</code>               | id of destination meeting      |
-| participantIds       | <code>Array.&lt;string&gt;</code> | list of id of the participants |
+| Param | Type | Description |
+| --- | --- | --- |
+| sourceMeetingId | <code>string</code> | id of source meeting |
+| destinationMeetingId | <code>string</code> | id of destination meeting |
+| participantIds | <code>Array.&lt;string&gt;</code> | list of id of the participants |
 
 <a name="module_RTKConnectedMeetings--module.exports+moveParticipantsWithCustomPreset"></a>
 
 #### module.exports.moveParticipantsWithCustomPreset(sourceMeetingId, destinationMeetingId, participants)
-
 Trigger event to move participants with custom preset
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKConnectedMeetings--module.exports)  
+
+| Param | Type | Description |
+| --- | --- | --- |
+| sourceMeetingId | <code>string</code> | id of source meeting |
+| destinationMeetingId | <code>string</code> | id of destination meeting |
+| participants | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |  |
 
-| Param                | Type                                                      | Description               |
-| -------------------- | --------------------------------------------------------- | ------------------------- |
-| sourceMeetingId      | <code>string</code>                                       | id of source meeting      |
-| destinationMeetingId | <code>string</code>                                       | id of destination meeting |
-| participants         | <code>Array.&lt;{id: string, presetId: string}&gt;</code> |                           |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
index 2706403d75acd35..4d2d4d56bab5c91 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md
@@ -11,59 +11,55 @@ web_core_version: 1.2.4
 The RTKLivestream module represents the state of the current livestream, and allows
 to start/stop live streams.
 
-- [RTKLivestream](#module_RTKLivestream)
-  - [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
-    - [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
-    - [.telemetry](#module_RTKLivestream--module.exports+telemetry)
-    - [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
-    - [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
-    - [.stop()](#module_RTKLivestream--module.exports+stop)
+
+* [RTKLivestream](#module_RTKLivestream)
+    * [module.exports](#exp_module_RTKLivestream--module.exports) ⏏
+        * [new module.exports(context, self)](#new_module_RTKLivestream--module.exports_new)
+        * [.telemetry](#module_RTKLivestream--module.exports+telemetry)
+        * [.setRTKLivestreamState(livestreamState)](#module_RTKLivestream--module.exports+setRTKLivestreamState)
+        * [.start([livestreamConfig])](#module_RTKLivestream--module.exports+start)
+        * [.stop()](#module_RTKLivestream--module.exports+stop)
 
 <a name="exp_module_RTKLivestream--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKLivestream--module.exports_new"></a>
 
 #### new module.exports(context, self)
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
-| self    | <code>Self</code>    |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
 
 <a name="module_RTKLivestream--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 <a name="module_RTKLivestream--module.exports+setRTKLivestreamState"></a>
 
 #### module.exports.setRTKLivestreamState(livestreamState)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
-
-| Param           | Type                            |
-| --------------- | ------------------------------- |
-| livestreamState | <code>RTKLivestreamState</code> |
+| Param | Type |
+| --- | --- |
+| livestreamState | <code>RTKLivestreamState</code> | 
 
 <a name="module_RTKLivestream--module.exports+start"></a>
 
 #### module.exports.start([livestreamConfig])
-
 Starts livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
 
-| Param              | Type                                  |
-| ------------------ | ------------------------------------- |
-| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> |
+| Param | Type |
+| --- | --- |
+| [livestreamConfig] | <code>StartRTKLivestreamConfig</code> | 
 
 <a name="module_RTKLivestream--module.exports+stop"></a>
 
 #### module.exports.stop()
-
 Stops livestreaming the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKLivestream--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
index 9752ca8616beba0..8a3447521dfd9b2 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKMeta.md
@@ -10,54 +10,51 @@ web_core_version: 1.2.4
 
 This consists of the metadata of the meeting, such as the room name and the title.
 
-- [RTKMeta](#module_RTKMeta)
-  - [module.exports](#exp_module_RTKMeta--module.exports) ⏏
-    - [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
-    - [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
-    - [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
-    - [.viewType](#module_RTKMeta--module.exports+viewType)
-    - [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
-    - [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
-    - [.sessionId](#module_RTKMeta--module.exports+sessionId)
-    - [.meetingId](#module_RTKMeta--module.exports+meetingId)
-    - [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
-    - [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
+
+* [RTKMeta](#module_RTKMeta)
+    * [module.exports](#exp_module_RTKMeta--module.exports) ⏏
+        * [new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)](#new_module_RTKMeta--module.exports_new)
+        * [.selfActiveTab](#module_RTKMeta--module.exports+selfActiveTab)
+        * [.broadcastTabChanges](#module_RTKMeta--module.exports+broadcastTabChanges)
+        * [.viewType](#module_RTKMeta--module.exports+viewType)
+        * [.meetingStartedTimestamp](#module_RTKMeta--module.exports+meetingStartedTimestamp)
+        * [.meetingTitle](#module_RTKMeta--module.exports+meetingTitle)
+        * [.sessionId](#module_RTKMeta--module.exports+sessionId)
+        * [.meetingId](#module_RTKMeta--module.exports+meetingId)
+        * [.setBroadcastTabChanges(broadcastTabChanges)](#module_RTKMeta--module.exports+setBroadcastTabChanges)
+        * [.setSelfActiveTab(spotlightTab, tabChangeSource)](#module_RTKMeta--module.exports+setSelfActiveTab)
 
 <a name="exp_module_RTKMeta--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKMeta--module.exports_new"></a>
 
 #### new module.exports(context, self, viewType, roomSocketHandler, meetingTitle)
 
-| Param             | Type                           |
-| ----------------- | ------------------------------ |
-| context           | <code>Context</code>           |
-| self              | <code>Self</code>              |
-| viewType          | <code>string</code>            |
-| roomSocketHandler | <code>RoomSocketHandler</code> |
-| meetingTitle      | <code>string</code>            |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| viewType | <code>string</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
+| meetingTitle | <code>string</code> | 
 
 <a name="module_RTKMeta--module.exports+selfActiveTab"></a>
 
 #### module.exports.selfActiveTab
-
 Represents the current active tab
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+broadcastTabChanges"></a>
 
 #### module.exports.broadcastTabChanges
-
 Represents whether current user is spotlighted
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+viewType"></a>
 
 #### module.exports.viewType
-
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -65,52 +62,47 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKMeta--module.exports+meetingStartedTimestamp"></a>
 
 #### module.exports.meetingStartedTimestamp
-
 The timestamp of the time when the meeting started.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingTitle"></a>
 
 #### module.exports.meetingTitle
-
 The title of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+sessionId"></a>
 
 #### module.exports.sessionId
-
 (Experimental) The sessionId this meeting object is part of.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+meetingId"></a>
 
 #### module.exports.meetingId
-
 The room name of the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 <a name="module_RTKMeta--module.exports+setBroadcastTabChanges"></a>
 
 #### module.exports.setBroadcastTabChanges(broadcastTabChanges)
-
 Sets current user as broadcasting tab changes
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
 
-| Param               | Type                 |
-| ------------------- | -------------------- |
-| broadcastTabChanges | <code>boolean</code> |
+| Param | Type |
+| --- | --- |
+| broadcastTabChanges | <code>boolean</code> | 
 
 <a name="module_RTKMeta--module.exports+setSelfActiveTab"></a>
 
 #### module.exports.setSelfActiveTab(spotlightTab, tabChangeSource)
-
 Sets current active tab for user
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKMeta--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| spotlightTab | <code>ActiveTab</code> | 
+| tabChangeSource | <code>TabChangeSource</code> | 
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| spotlightTab    | <code>ActiveTab</code>       |
-| tabChangeSource | <code>TabChangeSource</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
index 12a5b874df4f649..5ab88c872e965cd 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md
@@ -11,72 +11,68 @@ web_core_version: 1.2.4
 This module represents a single participant in the meeting.
 The participant object can be accessed from one of the participant lists
 present in the `meeting.participants` object. For example,
-
 ```ts
 const participant1 = meeting.participants.active.get(participantId);
 const participant2 = meeting.participants.joined.get(participantId);
 const participant3 = meeting.participants.active.toArray()[0];
-const participant4 = meeting.participants.active
-	.toArray()
-	.filter((p) => p.name === "John");
+const participant4 = meeting.participants.active.toArray().filter((p) => p.name === 'John');
 ```
 
-- [RTKParticipant](#module_RTKParticipant)
-  - [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
-    - [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
-    - [.id](#module_RTKParticipant--module.exports+id)
-    - [.userId](#module_RTKParticipant--module.exports+userId)
-    - [.name](#module_RTKParticipant--module.exports+name)
-    - [.picture](#module_RTKParticipant--module.exports+picture)
-    - [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
-    - ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
-    - [.device](#module_RTKParticipant--module.exports+device)
-    - [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
-    - [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
-    - [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
-    - [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
-    - [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
-    - [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
-    - [.producers](#module_RTKParticipant--module.exports+producers)
-    - [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
-    - [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
-    - [.presetName](#module_RTKParticipant--module.exports+presetName)
-    - [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
-    - [.telemetry](#module_RTKParticipant--module.exports+telemetry)
-    - [.isPinned](#module_RTKParticipant--module.exports+isPinned)
-    - [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
-    - [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
-    - [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
-    - [.pin()](#module_RTKParticipant--module.exports+pin)
-    - [.unpin()](#module_RTKParticipant--module.exports+unpin)
-    - [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
-    - [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
-    - [.kick()](#module_RTKParticipant--module.exports+kick)
-    - [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
-    - [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
-    - [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
-    - [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
+
+* [RTKParticipant](#module_RTKParticipant)
+    * [module.exports](#exp_module_RTKParticipant--module.exports) ⏏
+        * [new module.exports(context, participant, self, roomSocket)](#new_module_RTKParticipant--module.exports_new)
+        * [.id](#module_RTKParticipant--module.exports+id)
+        * [.userId](#module_RTKParticipant--module.exports+userId)
+        * [.name](#module_RTKParticipant--module.exports+name)
+        * [.picture](#module_RTKParticipant--module.exports+picture)
+        * [.customRTKParticipantId](#module_RTKParticipant--module.exports+customRTKParticipantId)
+        * ~~[.clientSpecificId](#module_RTKParticipant--module.exports+clientSpecificId)~~
+        * [.device](#module_RTKParticipant--module.exports+device)
+        * [.videoTrack](#module_RTKParticipant--module.exports+videoTrack)
+        * [.audioTrack](#module_RTKParticipant--module.exports+audioTrack)
+        * [.screenShareTracks](#module_RTKParticipant--module.exports+screenShareTracks)
+        * [.videoEnabled](#module_RTKParticipant--module.exports+videoEnabled)
+        * [.audioEnabled](#module_RTKParticipant--module.exports+audioEnabled)
+        * [.screenShareEnabled](#module_RTKParticipant--module.exports+screenShareEnabled)
+        * [.producers](#module_RTKParticipant--module.exports+producers)
+        * [.manualProducerConfig](#module_RTKParticipant--module.exports+manualProducerConfig)
+        * [.supportsRemoteControl](#module_RTKParticipant--module.exports+supportsRemoteControl)
+        * [.presetName](#module_RTKParticipant--module.exports+presetName)
+        * [.stageStatus](#module_RTKParticipant--module.exports+stageStatus)
+        * [.telemetry](#module_RTKParticipant--module.exports+telemetry)
+        * [.isPinned](#module_RTKParticipant--module.exports+isPinned)
+        * [.setVideoEnabled(videoEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setVideoEnabled)
+        * [.setAudioEnabled(audioEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setAudioEnabled)
+        * [.setScreenShareEnabled(screenShareEnabled, [emitEvent])](#module_RTKParticipant--module.exports+setScreenShareEnabled)
+        * [.pin()](#module_RTKParticipant--module.exports+pin)
+        * [.unpin()](#module_RTKParticipant--module.exports+unpin)
+        * [.setIsPinned(isPinned, [emitEvent])](#module_RTKParticipant--module.exports+setIsPinned)
+        * [.disableAudio()](#module_RTKParticipant--module.exports+disableAudio)
+        * [.kick()](#module_RTKParticipant--module.exports+kick)
+        * [.disableVideo()](#module_RTKParticipant--module.exports+disableVideo)
+        * [.registerVideoElement(videoElem)](#module_RTKParticipant--module.exports+registerVideoElement)
+        * [.deregisterVideoElement([videoElem])](#module_RTKParticipant--module.exports+deregisterVideoElement)
+        * [.updateVideo(e)](#module_RTKParticipant--module.exports+updateVideo)
 
 <a name="exp_module_RTKParticipant--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipant--module.exports_new"></a>
 
 #### new module.exports(context, participant, self, roomSocket)
 
-| Param       | Type                           |
-| ----------- | ------------------------------ |
-| context     | <code>Context</code>           |
-| participant | <code>IRTKParticipant</code>   |
-| self        | <code>Self</code>              |
-| roomSocket  | <code>RoomSocketHandler</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| participant | <code>IRTKParticipant</code> | 
+| self | <code>Self</code> | 
+| roomSocket | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKParticipant--module.exports+id"></a>
 
 #### module.exports.id
-
 The peer ID of the participant.
 The participants are indexed by this ID in the participant map.
 
@@ -84,171 +80,148 @@ The participants are indexed by this ID in the participant map.
 <a name="module_RTKParticipant--module.exports+userId"></a>
 
 #### module.exports.userId
-
 The user ID of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+name"></a>
 
 #### module.exports.name
-
 The name of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+picture"></a>
 
 #### module.exports.picture
-
 The picture of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+customRTKParticipantId"></a>
 
 #### module.exports.customRTKParticipantId
-
 The custom id of the participant set during Add RTKParticipant REST API
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+clientSpecificId"></a>
 
 #### ~~module.exports.clientSpecificId~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+device"></a>
 
 #### module.exports.device
-
 The device configuration of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoTrack"></a>
 
 #### module.exports.videoTrack
-
 The participant's video track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioTrack"></a>
 
 #### module.exports.audioTrack
-
 The participant's audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareTracks"></a>
 
 #### module.exports.screenShareTracks
-
 The participant's screenshare video and audio track.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+videoEnabled"></a>
 
 #### module.exports.videoEnabled
-
 This is true if the participant's video is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+audioEnabled"></a>
 
 #### module.exports.audioEnabled
-
 This is true if the participant's audio is enabled.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+screenShareEnabled"></a>
 
 #### module.exports.screenShareEnabled
-
 This is true if the participant is screensharing.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+producers"></a>
 
 #### module.exports.producers
-
 producers created by participant
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+manualProducerConfig"></a>
 
 #### module.exports.manualProducerConfig
-
 producer config passed during manual subscription
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+supportsRemoteControl"></a>
 
 #### module.exports.supportsRemoteControl
-
 This is true if the participant supports remote control.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+presetName"></a>
 
 #### module.exports.presetName
-
 The preset of the participant.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+stageStatus"></a>
 
 #### module.exports.stageStatus
-
 Denotes the participants's current stage status.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+isPinned"></a>
 
 #### module.exports.isPinned
-
 Returns true if the participant is pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 <a name="module_RTKParticipant--module.exports+setVideoEnabled"></a>
 
 #### module.exports.setVideoEnabled(videoEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param        | Type                 | Default           |
-| ------------ | -------------------- | ----------------- |
-| videoEnabled | <code>boolean</code> |                   |
-| [emitEvent]  | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| videoEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+setAudioEnabled"></a>
 
 #### module.exports.setAudioEnabled(audioEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param        | Type                 | Default           |
-| ------------ | -------------------- | ----------------- |
-| audioEnabled | <code>boolean</code> |                   |
-| [emitEvent]  | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| audioEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+setScreenShareEnabled"></a>
 
 #### module.exports.setScreenShareEnabled(screenShareEnabled, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param              | Type                 | Default           |
-| ------------------ | -------------------- | ----------------- |
-| screenShareEnabled | <code>boolean</code> |                   |
-| [emitEvent]        | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| screenShareEnabled | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+pin"></a>
 
 #### module.exports.pin()
-
 Returns `participant.id` if user has permission
 to pin participants.
 
@@ -256,7 +229,6 @@ to pin participants.
 <a name="module_RTKParticipant--module.exports+unpin"></a>
 
 #### module.exports.unpin()
-
 Returns `participant.id` if user has permission
 to unpin participants.
 
@@ -264,18 +236,16 @@ to unpin participants.
 <a name="module_RTKParticipant--module.exports+setIsPinned"></a>
 
 #### module.exports.setIsPinned(isPinned, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param       | Type                 | Default           |
-| ----------- | -------------------- | ----------------- |
-| isPinned    | <code>boolean</code> |                   |
-| [emitEvent] | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| isPinned | <code>boolean</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipant--module.exports+disableAudio"></a>
 
 #### module.exports.disableAudio()
-
 Disables audio for this participant.
 Requires the permission to disable participant audio.
 
@@ -283,7 +253,6 @@ Requires the permission to disable participant audio.
 <a name="module_RTKParticipant--module.exports+kick"></a>
 
 #### module.exports.kick()
-
 Kicks this participant from the meeting.
 Requires the permission to kick a participant.
 
@@ -291,7 +260,6 @@ Requires the permission to kick a participant.
 <a name="module_RTKParticipant--module.exports+disableVideo"></a>
 
 #### module.exports.disableVideo()
-
 Disables video for this participant.
 Requires the permission to disable video for a participant.
 
@@ -299,31 +267,29 @@ Requires the permission to disable video for a participant.
 <a name="module_RTKParticipant--module.exports+registerVideoElement"></a>
 
 #### module.exports.registerVideoElement(videoElem)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param     | Type                          |
-| --------- | ----------------------------- |
-| videoElem | <code>HTMLVideoElement</code> |
+| Param | Type |
+| --- | --- |
+| videoElem | <code>HTMLVideoElement</code> | 
 
 <a name="module_RTKParticipant--module.exports+deregisterVideoElement"></a>
 
 #### module.exports.deregisterVideoElement([videoElem])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
-
-| Param       | Type                          |
-| ----------- | ----------------------------- |
-| [videoElem] | <code>HTMLVideoElement</code> |
+| Param | Type |
+| --- | --- |
+| [videoElem] | <code>HTMLVideoElement</code> | 
 
 <a name="module_RTKParticipant--module.exports+updateVideo"></a>
 
 #### module.exports.updateVideo(e)
-
 Internal method, do not use
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipant--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| e | <code>HTMLVideoElement</code> | 
 
-| Param | Type                          |
-| ----- | ----------------------------- |
-| e     | <code>HTMLVideoElement</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
index c894fa0a1e8958c..f10720836d026ca 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md
@@ -14,57 +14,55 @@ For example, when a participant is added to this map, a `participantJoined` even
 emitted from the map. When a participant object emits an event `videoUpdate`, the map
 re-emits that event (provided the participant is present in the map).
 
-- [RTKParticipantMap](#module_RTKParticipantMap)
-  - [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
-    - [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
-    - [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
-    - [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
-    - [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
+
+* [RTKParticipantMap](#module_RTKParticipantMap)
+    * [module.exports](#exp_module_RTKParticipantMap--module.exports) ⏏
+        * [new module.exports(logger, [options])](#new_module_RTKParticipantMap--module.exports_new)
+        * [.add(participant, [emitEvent])](#module_RTKParticipantMap--module.exports+add)
+        * [.clear([emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+clear)
+        * [.delete(participantId, [emitEvent], [removeListeners])](#module_RTKParticipantMap--module.exports+delete)
 
 <a name="exp_module_RTKParticipantMap--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipantMap--module.exports_new"></a>
 
 #### new module.exports(logger, [options])
 
-| Param     | Type                   |
-| --------- | ---------------------- |
-| logger    | <code>Logger</code>    |
-| [options] | <code>MapEvents</code> |
+| Param | Type |
+| --- | --- |
+| logger | <code>Logger</code> | 
+| [options] | <code>MapEvents</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+add"></a>
 
 #### module.exports.add(participant, [emitEvent])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
-
-| Param       | Type                 | Default           |
-| ----------- | -------------------- | ----------------- |
-| participant | <code>T</code>       |                   |
-| [emitEvent] | <code>boolean</code> | <code>true</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| participant | <code>T</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+clear"></a>
 
 #### module.exports.clear([emitEvent], [removeListeners])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
-
-| Param             | Type                 | Default            |
-| ----------------- | -------------------- | ------------------ |
-| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
-| [removeListeners] | <code>boolean</code> | <code>false</code> |
+| Param | Type | Default |
+| --- | --- | --- |
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+| [removeListeners] | <code>boolean</code> | <code>false</code> | 
 
 <a name="module_RTKParticipantMap--module.exports+delete"></a>
 
 #### module.exports.delete(participantId, [emitEvent], [removeListeners])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipantMap--module.exports)
+| Param | Type | Default |
+| --- | --- | --- |
+| participantId | <code>string</code> |  | 
+| [emitEvent] | <code>boolean</code> | <code>true</code> | 
+| [removeListeners] | <code>boolean</code> | <code>false</code> | 
 
-| Param             | Type                 | Default            |
-| ----------------- | -------------------- | ------------------ |
-| participantId     | <code>string</code>  |                    |
-| [emitEvent]       | <code>boolean</code> | <code>true</code>  |
-| [removeListeners] | <code>boolean</code> | <code>false</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
index 85f7c46ef94b31e..6cc9cfa343f6be8 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipants.md
@@ -10,114 +10,106 @@ web_core_version: 1.2.4
 
 This module represents all the participants in the meeting (except the local user).
 It consists of 4 maps:
-
 - `joined`: A map of all participants that have joined the meeting.
 - `waitlisted`: A map of all participants that have been added to the waitlist.
 - `active`: A map of active participants who should be displayed in the meeting grid.
 - `pinned`: A map of pinned participants.
 
+
 * [RTKParticipants](#module_RTKParticipants)
-  - [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
-    - [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
-    - [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
-    - [.joined](#module_RTKParticipants--module.exports+joined)
-    - ~~[.active](#module_RTKParticipants--module.exports+active)~~
-    - [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
-    - [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
-    - [.pinned](#module_RTKParticipants--module.exports+pinned)
-    - [.all](#module_RTKParticipants--module.exports+all)
-    - [.pip](#module_RTKParticipants--module.exports+pip)
-    - [.telemetry](#module_RTKParticipants--module.exports+telemetry)
-    - [.viewMode](#module_RTKParticipants--module.exports+viewMode)
-    - [.currentPage](#module_RTKParticipants--module.exports+currentPage)
-    - [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
-    - [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
-    - [.count](#module_RTKParticipants--module.exports+count)
-    - [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
-    - [.pageCount](#module_RTKParticipants--module.exports+pageCount)
-    - [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
-    - [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
-    - [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
-    - [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
-    - [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
-    - [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
-    - [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
-    - [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
-    - [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
-    - [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
-    - ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
-    - ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
-    - ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
-    - [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
-    - [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
-    - [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
-    - [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
+    * [module.exports](#exp_module_RTKParticipants--module.exports) ⏏
+        * [new module.exports(context, self, roomSocketHandler)](#new_module_RTKParticipants--module.exports_new)
+        * [.waitlisted](#module_RTKParticipants--module.exports+waitlisted)
+        * [.joined](#module_RTKParticipants--module.exports+joined)
+        * ~~[.active](#module_RTKParticipants--module.exports+active)~~
+        * [.videoSubscribed](#module_RTKParticipants--module.exports+videoSubscribed)
+        * [.audioSubscribed](#module_RTKParticipants--module.exports+audioSubscribed)
+        * [.pinned](#module_RTKParticipants--module.exports+pinned)
+        * [.all](#module_RTKParticipants--module.exports+all)
+        * [.pip](#module_RTKParticipants--module.exports+pip)
+        * [.telemetry](#module_RTKParticipants--module.exports+telemetry)
+        * [.viewMode](#module_RTKParticipants--module.exports+viewMode)
+        * [.currentPage](#module_RTKParticipants--module.exports+currentPage)
+        * [.lastActiveSpeaker](#module_RTKParticipants--module.exports+lastActiveSpeaker)
+        * [.selectedPeers](#module_RTKParticipants--module.exports+selectedPeers)
+        * [.count](#module_RTKParticipants--module.exports+count)
+        * [.maxActiveRTKParticipantsCount](#module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount)
+        * [.pageCount](#module_RTKParticipants--module.exports+pageCount)
+        * [.setMaxActiveRTKParticipantsCount(limit)](#module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount)
+        * [.acceptWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+acceptWaitingRoomRequest)
+        * [.acceptAllWaitingRoomRequest(userIds)](#module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest)
+        * [.rejectWaitingRoomRequest(id)](#module_RTKParticipants--module.exports+rejectWaitingRoomRequest)
+        * [.setViewMode(viewMode)](#module_RTKParticipants--module.exports+setViewMode)
+        * [.subscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+subscribe)
+        * [.unsubscribe(peerIds, [kinds])](#module_RTKParticipants--module.exports+unsubscribe)
+        * [.setPage(page)](#module_RTKParticipants--module.exports+setPage)
+        * [.disableAllAudio(allowUnmute)](#module_RTKParticipants--module.exports+disableAllAudio)
+        * [.disableAllVideo()](#module_RTKParticipants--module.exports+disableAllVideo)
+        * ~~[.disableAudio(participantId)](#module_RTKParticipants--module.exports+disableAudio)~~
+        * ~~[.disableVideo(participantId)](#module_RTKParticipants--module.exports+disableVideo)~~
+        * ~~[.kick(participantId)](#module_RTKParticipants--module.exports+kick)~~
+        * [.kickAll()](#module_RTKParticipants--module.exports+kickAll)
+        * [.broadcastMessage(type, payload, target)](#module_RTKParticipants--module.exports+broadcastMessage)
+        * [.getAllJoinedPeers(searchQuery, limit, offset)](#module_RTKParticipants--module.exports+getAllJoinedPeers)
+        * [.getRTKParticipantsInMeetingPreJoin()](#module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin)
 
 <a name="exp_module_RTKParticipants--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKParticipants--module.exports_new"></a>
 
 #### new module.exports(context, self, roomSocketHandler)
-
 This constructs a new Participant object and maintains
 the maps of active/joined/waitlisted/pinned/selectedPeers maps.
 self : Self
 
-| Param             | Type                           |
-| ----------------- | ------------------------------ |
-| context           | <code>Context</code>           |
-| self              | <code>Self</code>              |
-| roomSocketHandler | <code>RoomSocketHandler</code> |
+
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKParticipants--module.exports+waitlisted"></a>
 
 #### module.exports.waitlisted
-
 Returns a list of participants waiting to join the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+joined"></a>
 
 #### module.exports.joined
-
 Returns a list of all participants in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+active"></a>
 
 #### ~~module.exports.active~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+videoSubscribed"></a>
 
 #### module.exports.videoSubscribed
-
 Returns a list of participants whose video streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+audioSubscribed"></a>
 
 #### module.exports.audioSubscribed
-
 Returns a list of participants whose audio streams are currently consumed.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+pinned"></a>
 
 #### module.exports.pinned
-
 Returns a list of participants who have been pinned.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+all"></a>
 
 #### module.exports.all
-
 Returns all added participants irrespective of whether they are currently
 in the meeting or not
 
@@ -125,19 +117,16 @@ in the meeting or not
 <a name="module_RTKParticipants--module.exports+pip"></a>
 
 #### module.exports.pip
-
 Return the controls for Picture-in-Picture
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+viewMode"></a>
 
 #### module.exports.viewMode
-
 Indicates whether the meeting is in 'ACTIVE_GRID' mode or 'PAGINATED' mode.
 
 In 'ACTIVE_GRID' mode, participants are populated in the participants.active map
@@ -152,7 +141,6 @@ changed by the user using setPage(page).
 <a name="module_RTKParticipants--module.exports+currentPage"></a>
 
 #### module.exports.currentPage
-
 This indicates the current page that has been set by the user in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -160,28 +148,24 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+lastActiveSpeaker"></a>
 
 #### module.exports.lastActiveSpeaker
-
 This stores the `participantId` of the last participant who spoke in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+selectedPeers"></a>
 
 #### module.exports.selectedPeers
-
 Keeps a list of all participants who have been present in the selected peers list.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+count"></a>
 
 #### module.exports.count
-
 Returns the number of participants who are joined in the meeting.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+maxActiveRTKParticipantsCount"></a>
 
 #### module.exports.maxActiveRTKParticipantsCount
-
 Returns the maximum number of participants that can be present in
 the active map.
 
@@ -189,7 +173,6 @@ the active map.
 <a name="module_RTKParticipants--module.exports+pageCount"></a>
 
 #### module.exports.pageCount
-
 Returns the number of pages that are available in the meeting in PAGINATED mode.
 If the meeting is in ACTIVE_GRID mode, this value will be 0.
 
@@ -197,204 +180,187 @@ If the meeting is in ACTIVE_GRID mode, this value will be 0.
 <a name="module_RTKParticipants--module.exports+setMaxActiveRTKParticipantsCount"></a>
 
 #### module.exports.setMaxActiveRTKParticipantsCount(limit)
-
 Updates the maximum number of participants that are populated in
 the active map.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description       |
-| ----- | ------------------- | ----------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | limit | <code>number</code> | Updated max limit |
 
 <a name="module_RTKParticipants--module.exports+acceptWaitingRoomRequest"></a>
 
 #### module.exports.acceptWaitingRoomRequest(id)
-
 Accepts requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                                     |
-| ----- | ------------------- | ----------------------------------------------- |
-| id    | <code>string</code> | peerId or userId of the waitlisted participant. |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | peerId or userId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+acceptAllWaitingRoomRequest"></a>
 
 #### module.exports.acceptAllWaitingRoomRequest(userIds)
-
 We need a new event for socket service events
 since if we send them all together, sequence of events
 can be unreliable
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param   | Type                              |
-| ------- | --------------------------------- |
-| userIds | <code>Array.&lt;string&gt;</code> |
+| Param | Type |
+| --- | --- |
+| userIds | <code>Array.&lt;string&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+rejectWaitingRoomRequest"></a>
 
 #### module.exports.rejectWaitingRoomRequest(id)
-
 Rejects requests from waitlisted participants if user
 has appropriate permissions.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                                  |
-| ----- | ------------------- | -------------------------------------------- |
-| id    | <code>string</code> | participantId of the waitlisted participant. |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | participantId of the waitlisted participant. |
 
 <a name="module_RTKParticipants--module.exports+setViewMode"></a>
 
 #### module.exports.setViewMode(viewMode)
-
 Sets the view mode of the meeting to either ACTIVE_GRID or PAGINATED.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param    | Type                  | Description                                          |
-| -------- | --------------------- | ---------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | viewMode | <code>ViewMode</code> | The mode in which the active map should be populated |
 
 <a name="module_RTKParticipants--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(peerIds, [kinds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
-
-| Param   | Type                                                                                                                          |
-| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
+| Param | Type |
+| --- | --- |
+| peerIds | <code>Array.&lt;string&gt;</code> | 
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(peerIds, [kinds])
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
-
-| Param   | Type                                                                                                                          |
-| ------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| peerIds | <code>Array.&lt;string&gt;</code>                                                                                             |
-| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> |
+| Param | Type |
+| --- | --- |
+| peerIds | <code>Array.&lt;string&gt;</code> | 
+| [kinds] | <code>Array.&lt;(&#x27;audio&#x27;\|&#x27;video&#x27;\|&#x27;screenshareAudio&#x27;\|&#x27;screenshareVideo&#x27;)&gt;</code> | 
 
 <a name="module_RTKParticipants--module.exports+setPage"></a>
 
 #### module.exports.setPage(page)
-
 Populates the active map with participants present in the page number
 indicated by the parameter `page` in PAGINATED mode.
 Does not do anything in ACTIVE_GRID mode.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param | Type                | Description                |
-| ----- | ------------------- | -------------------------- |
-| page  | <code>number</code> | The page number to be set. |
+| Param | Type | Description |
+| --- | --- | --- |
+| page | <code>number</code> | The page number to be set. |
 
 <a name="module_RTKParticipants--module.exports+disableAllAudio"></a>
 
 #### module.exports.disableAllAudio(allowUnmute)
-
 Disables audio for all participants in the meeting.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param       | Type                 | Description                                        |
-| ----------- | -------------------- | -------------------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | allowUnmute | <code>boolean</code> | Allow participants to unmute after they are muted. |
 
 <a name="module_RTKParticipants--module.exports+disableAllVideo"></a>
 
 #### module.exports.disableAllVideo()
-
 Disables video for all participants in the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+disableAudio"></a>
 
 #### ~~module.exports.disableAudio(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                    |
-| ------------- | ------------------- | ------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+disableVideo"></a>
 
 #### ~~module.exports.disableVideo(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                    |
-| ------------- | ------------------- | ------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be muted. |
 
 <a name="module_RTKParticipants--module.exports+kick"></a>
 
 #### ~~module.exports.kick(participantId)~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param         | Type                | Description                     |
-| ------------- | ------------------- | ------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | participantId | <code>string</code> | ID of participant to be kicked. |
 
 <a name="module_RTKParticipants--module.exports+kickAll"></a>
 
 #### module.exports.kickAll()
-
 Kicks all participants from the meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 <a name="module_RTKParticipants--module.exports+broadcastMessage"></a>
 
 #### module.exports.broadcastMessage(type, payload, target)
-
 Broadcasts the message to participants
 
 If no `target` is specified it is sent to all participants including `self`.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param   | Type                                 | Description                                                                                                                           |
-| ------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
-| type    | <code>string</code>                  |                                                                                                                                       |
-| payload | <code>BroadcastMessagePayload</code> |                                                                                                                                       |
-| target  | <code>BroadcastMessageTarget</code>  | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
+| Param | Type | Description |
+| --- | --- | --- |
+| type | <code>string</code> |  |
+| payload | <code>BroadcastMessagePayload</code> |  |
+| target | <code>BroadcastMessageTarget</code> | object containing a list of `participantIds` or object containing `presetName` - every user with that preset will be sent the message |
 
 <a name="module_RTKParticipants--module.exports+getAllJoinedPeers"></a>
 
 #### module.exports.getAllJoinedPeers(searchQuery, limit, offset)
-
 Returns all peers currently present in the room
 If you are in a group call, use `meeting.participants.joined`
 instead
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
 
-| Param       | Type                |
-| ----------- | ------------------- |
-| searchQuery | <code>string</code> |
-| limit       | <code>number</code> |
-| offset      | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| searchQuery | <code>string</code> | 
+| limit | <code>number</code> | 
+| offset | <code>number</code> | 
 
 <a name="module_RTKParticipants--module.exports+getRTKParticipantsInMeetingPreJoin"></a>
 
 #### module.exports.getRTKParticipantsInMeetingPreJoin()
-
 Returns all peers currently in the room, is a non paginated call
 and should only be used if you are in a non room joined state,
 if in a joined group call, use `meeting.participants.joined`
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKParticipants--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
index ac3f6c4b61d2b82..e8da972e0b7c931 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPermissionsPreset.md
@@ -10,52 +10,52 @@ web_core_version: 1.2.4
 
 The PermissionPreset class represents the meeting permissions for the current participant
 
-- [PermissionPreset](#module_PermissionPreset)
-  - _instance_
-    - [.stageEnabled](#module_PermissionPreset+stageEnabled)
-    - [.stageAccess](#module_PermissionPreset+stageAccess)
-    - [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
-    - [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
-    - [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
-    - [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
-    - [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
-    - [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
-    - [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
-    - [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
-    - [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
-    - [.kickParticipant](#module_PermissionPreset+kickParticipant)
-    - [.pinParticipant](#module_PermissionPreset+pinParticipant)
-    - [.canRecord](#module_PermissionPreset+canRecord)
-    - ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
-    - [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
-    - [.plugins](#module_PermissionPreset+plugins)
-    - [.polls](#module_PermissionPreset+polls)
-    - ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
-    - ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
-    - [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
-    - ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
-    - [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
-    - ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
-    - [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
-    - [.chatPublic](#module_PermissionPreset+chatPublic)
-    - [.chatPrivate](#module_PermissionPreset+chatPrivate)
-    - [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
-    - [.showParticipantList](#module_PermissionPreset+showParticipantList)
-    - ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
-    - [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
-    - ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
-    - ~~[.canPresent](#module_PermissionPreset+canPresent)~~
-    - ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
-    - ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
-    - [.canLivestream](#module_PermissionPreset+canLivestream)
-  - _static_
-    - [.fromResponse()](#module_PermissionPreset.fromResponse)
-    - [.default()](#module_PermissionPreset.default)
+
+* [PermissionPreset](#module_PermissionPreset)
+    * _instance_
+        * [.stageEnabled](#module_PermissionPreset+stageEnabled)
+        * [.stageAccess](#module_PermissionPreset+stageAccess)
+        * [.acceptWaitingRequests](#module_PermissionPreset+acceptWaitingRequests)
+        * [.requestProduceVideo](#module_PermissionPreset+requestProduceVideo)
+        * [.requestProduceAudio](#module_PermissionPreset+requestProduceAudio)
+        * [.requestProduceScreenshare](#module_PermissionPreset+requestProduceScreenshare)
+        * [.canAllowParticipantAudio](#module_PermissionPreset+canAllowParticipantAudio)
+        * [.canAllowParticipantScreensharing](#module_PermissionPreset+canAllowParticipantScreensharing)
+        * [.canAllowParticipantVideo](#module_PermissionPreset+canAllowParticipantVideo)
+        * [.canDisableParticipantAudio](#module_PermissionPreset+canDisableParticipantAudio)
+        * [.canDisableParticipantVideo](#module_PermissionPreset+canDisableParticipantVideo)
+        * [.kickParticipant](#module_PermissionPreset+kickParticipant)
+        * [.pinParticipant](#module_PermissionPreset+pinParticipant)
+        * [.canRecord](#module_PermissionPreset+canRecord)
+        * ~~[.waitingRoomType](#module_PermissionPreset+waitingRoomType)~~
+        * [.waitingRoomBehaviour](#module_PermissionPreset+waitingRoomBehaviour)
+        * [.plugins](#module_PermissionPreset+plugins)
+        * [.polls](#module_PermissionPreset+polls)
+        * ~~[.produceVideo](#module_PermissionPreset+produceVideo)~~
+        * ~~[.requestProduce](#module_PermissionPreset+requestProduce)~~
+        * [.canProduceVideo](#module_PermissionPreset+canProduceVideo)
+        * ~~[.produceScreenshare](#module_PermissionPreset+produceScreenshare)~~
+        * [.canProduceScreenshare](#module_PermissionPreset+canProduceScreenshare)
+        * ~~[.produceAudio](#module_PermissionPreset+produceAudio)~~
+        * [.canProduceAudio](#module_PermissionPreset+canProduceAudio)
+        * [.chatPublic](#module_PermissionPreset+chatPublic)
+        * [.chatPrivate](#module_PermissionPreset+chatPrivate)
+        * [.hiddenParticipant](#module_PermissionPreset+hiddenParticipant)
+        * [.showParticipantList](#module_PermissionPreset+showParticipantList)
+        * ~~[.canChangeParticipantRole](#module_PermissionPreset+canChangeParticipantRole)~~
+        * [.canChangeParticipantPermissions](#module_PermissionPreset+canChangeParticipantPermissions)
+        * ~~[.canChangeTheme](#module_PermissionPreset+canChangeTheme)~~
+        * ~~[.canPresent](#module_PermissionPreset+canPresent)~~
+        * ~~[.acceptPresentRequests](#module_PermissionPreset+acceptPresentRequests)~~
+        * ~~[.maxScreenShareCount](#module_PermissionPreset+maxScreenShareCount)~~
+        * [.canLivestream](#module_PermissionPreset+canLivestream)
+    * _static_
+        * [.fromResponse()](#module_PermissionPreset.fromResponse)
+        * [.default()](#module_PermissionPreset.default)
 
 <a name="module_PermissionPreset+stageEnabled"></a>
 
 ### meeting.self.permissions.stageEnabled
-
 The `stageEnabled` property returns a boolean value.
 If `true`, stage management is available for the participant.
 
@@ -63,7 +63,6 @@ If `true`, stage management is available for the participant.
 <a name="module_PermissionPreset+stageAccess"></a>
 
 ### meeting.self.permissions.stageAccess
-
 The `stageAccess` property dictates how a user interacts with the stage.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 
@@ -71,7 +70,6 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`;
 <a name="module_PermissionPreset+acceptWaitingRequests"></a>
 
 ### meeting.self.permissions.acceptWaitingRequests
-
 The `acceptWaitingRequests` returns boolean value.
 If `true`, participant can accept the request of waiting participant.
 
@@ -79,7 +77,6 @@ If `true`, participant can accept the request of waiting participant.
 <a name="module_PermissionPreset+requestProduceVideo"></a>
 
 ### meeting.self.permissions.requestProduceVideo
-
 The `requestProduceVideo` returns boolean value.
 If `true`, participant can send request to participants
 about producing video.
@@ -88,7 +85,6 @@ about producing video.
 <a name="module_PermissionPreset+requestProduceAudio"></a>
 
 ### meeting.self.permissions.requestProduceAudio
-
 The `requestProduceAudio` returns boolean value.
 If `true`, participant can send request to participants
 about producing audio.
@@ -97,7 +93,6 @@ about producing audio.
 <a name="module_PermissionPreset+requestProduceScreenshare"></a>
 
 ### meeting.self.permissions.requestProduceScreenshare
-
 The `requestProduceScreenshare` returns boolean value.
 If `true`, participant can send request to participants
 about sharing screen.
@@ -106,7 +101,6 @@ about sharing screen.
 <a name="module_PermissionPreset+canAllowParticipantAudio"></a>
 
 ### meeting.self.permissions.canAllowParticipantAudio
-
 The `canAllowParticipantAudio` returns boolean value.
 If `true`, participant can enable other participants` audio.
 
@@ -114,7 +108,6 @@ If `true`, participant can enable other participants` audio.
 <a name="module_PermissionPreset+canAllowParticipantScreensharing"></a>
 
 ### meeting.self.permissions.canAllowParticipantScreensharing
-
 The `canAllowParticipantScreensharing` returns boolean value.
 If `true`, participant can enable other participants` screen share.
 
@@ -122,7 +115,6 @@ If `true`, participant can enable other participants` screen share.
 <a name="module_PermissionPreset+canAllowParticipantVideo"></a>
 
 ### meeting.self.permissions.canAllowParticipantVideo
-
 The `canAllowParticipantVideo` returns boolean value.
 If `true`, participant can enable other participants` video.
 
@@ -130,21 +122,18 @@ If `true`, participant can enable other participants` video.
 <a name="module_PermissionPreset+canDisableParticipantAudio"></a>
 
 ### meeting.self.permissions.canDisableParticipantAudio
-
 If `true`, a participant can disable other participants` audio.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canDisableParticipantVideo"></a>
 
 ### meeting.self.permissions.canDisableParticipantVideo
-
 If `true`, a participant can disable other participants` video.
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+kickParticipant"></a>
 
 ### meeting.self.permissions.kickParticipant
-
 The `kickParticipant` returns boolean value.
 If `true`, participant can remove other participants from the meeting.
 
@@ -152,7 +141,6 @@ If `true`, participant can remove other participants from the meeting.
 <a name="module_PermissionPreset+pinParticipant"></a>
 
 ### meeting.self.permissions.pinParticipant
-
 The `pinParticipant` returns boolean value.
 If `true`, participant can pin a participant in the meeting.
 
@@ -160,7 +148,6 @@ If `true`, participant can pin a participant in the meeting.
 <a name="module_PermissionPreset+canRecord"></a>
 
 ### meeting.self.permissions.canRecord
-
 The `canRecord` returns boolean value.
 If `true`, participant can record the meeting.
 
@@ -168,14 +155,12 @@ If `true`, participant can record the meeting.
 <a name="module_PermissionPreset+waitingRoomType"></a>
 
 ### ~~meeting.self.permissions.waitingRoomType~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+waitingRoomBehaviour"></a>
 
 ### meeting.self.permissions.waitingRoomBehaviour
-
 The `waitingRoomType` returns string value.
 type of waiting room behavior
 possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
@@ -184,7 +169,6 @@ possible values are `SKIP`, `ON_PRIVILEGED_USER_ENTRY`, `SKIP_ON_ACCEPT`
 <a name="module_PermissionPreset+plugins"></a>
 
 ### meeting.self.permissions.plugins
-
 The `plugins` tells if the participant can act on plugins
 there are 2 permissions with boolean values, `canStart` and `canClose`.
 
@@ -192,7 +176,6 @@ there are 2 permissions with boolean values, `canStart` and `canClose`.
 <a name="module_PermissionPreset+polls"></a>
 
 ### meeting.self.permissions.polls
-
 The `polls` tells if the participant can use polls.
 There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewResults`
 
@@ -200,21 +183,18 @@ There are 3 permissions with boolean values, `canCreate`, `canVote`, `canViewRes
 <a name="module_PermissionPreset+produceVideo"></a>
 
 ### ~~meeting.self.permissions.produceVideo~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+requestProduce"></a>
 
 ### ~~meeting.self.permissions.requestProduce~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceVideo"></a>
 
 ### meeting.self.permissions.canProduceVideo
-
 The `canProduceVideo` shows permissions for enabling video.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -222,14 +202,12 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceScreenshare"></a>
 
 ### ~~meeting.self.permissions.produceScreenshare~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceScreenshare"></a>
 
 ### meeting.self.permissions.canProduceScreenshare
-
 The `canProduceScreenshare` shows permissions for sharing screen.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -237,14 +215,12 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+produceAudio"></a>
 
 ### ~~meeting.self.permissions.produceAudio~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canProduceAudio"></a>
 
 ### meeting.self.permissions.canProduceAudio
-
 The `canProduceAudio` shows permissions for enabling audio.
 There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 
@@ -252,7 +228,6 @@ There possible values are `ALLOWED`, `NOT_ALLOWED`, `CAN_REQUEST`
 <a name="module_PermissionPreset+chatPublic"></a>
 
 ### meeting.self.permissions.chatPublic
-
 The `chatPublic` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send chat
@@ -263,7 +238,6 @@ there are 4 permissions
 <a name="module_PermissionPreset+chatPrivate"></a>
 
 ### meeting.self.permissions.chatPrivate
-
 The `chatPrivate` shows permissions for public chat
 there are 4 permissions
 `canSend` - if true, the participant can send private chat
@@ -275,7 +249,6 @@ there are 4 permissions
 <a name="module_PermissionPreset+hiddenParticipant"></a>
 
 ### meeting.self.permissions.hiddenParticipant
-
 The `hiddenParticipant` returns boolean value.
 If `true`, participant is hidden.
 
@@ -283,7 +256,6 @@ If `true`, participant is hidden.
 <a name="module_PermissionPreset+showParticipantList"></a>
 
 ### meeting.self.permissions.showParticipantList
-
 The `showParticipantList` returns boolean value.
 If `true`, participant list can be shown to the participant.
 
@@ -291,14 +263,12 @@ If `true`, participant list can be shown to the participant.
 <a name="module_PermissionPreset+canChangeParticipantRole"></a>
 
 ### ~~meeting.self.permissions.canChangeParticipantRole~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canChangeParticipantPermissions"></a>
 
 ### meeting.self.permissions.canChangeParticipantPermissions
-
 The `canChangeParticipantPermissions` returns boolean value.
 If `true`, allow changing the participants' permissions.
 
@@ -306,47 +276,40 @@ If `true`, allow changing the participants' permissions.
 <a name="module_PermissionPreset+canChangeTheme"></a>
 
 ### ~~meeting.self.permissions.canChangeTheme~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canPresent"></a>
 
 ### ~~meeting.self.permissions.canPresent~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+acceptPresentRequests"></a>
 
 ### ~~meeting.self.permissions.acceptPresentRequests~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+maxScreenShareCount"></a>
 
 ### ~~meeting.self.permissions.maxScreenShareCount~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset+canLivestream"></a>
 
 ### meeting.self.permissions.canLivestream
-
 Livestream
 
 **Kind**: instance property of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 <a name="module_PermissionPreset.fromResponse"></a>
 
 ### meeting.self.permissions.fromResponse()
-
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
 **Deprecated.**: Use init()  
 <a name="module_PermissionPreset.default"></a>
 
 ### meeting.self.permissions.default()
-
 **Kind**: static method of [<code>PermissionPreset</code>](#module_PermissionPreset)  
-**Deprecated.**: Use init()
+**Deprecated.**: Use init()  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
index 6cb2dd696a9ff5f..72747a12f6bdcac 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md
@@ -46,76 +46,76 @@ Code from ui-kit. Same method used in the avatar component
 **Kind**: global function  
 <a name="_init"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param   | Type                 |
-| ------- | -------------------- |
-| context | <code>Context</code> |
-| self    | <code>Self</code>    |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
 
 <a name="init"></a>
 
 Initialize PiP and prepare sources
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param            | Type                |
-| ---------------- | ------------------- |
-| [options]        | <code>Object</code> |
-| [options.height] | <code>number</code> |
-| [options.width]  | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| [options] | <code>Object</code> | 
+| [options.height] | <code>number</code> | 
+| [options.width] | <code>number</code> | 
 
 <a name="disableSource"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                |
-| ------ | ------------------- |
-| source | <code>string</code> |
+| Param | Type |
+| --- | --- |
+| source | <code>string</code> | 
 
 <a name="addSource"></a>
 
 Add a video source from the participant grid
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param         | Type                          | Description                            |
-| ------------- | ----------------------------- | -------------------------------------- |
-| id            | <code>string</code>           | id for the source (ex. participant id) |
-| element       | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source  |
-| enabled       | <code>boolean</code>          | if source is enabled                   |
-| [displayText] | <code>string</code>           | two character display text             |
+| Param | Type | Description |
+| --- | --- | --- |
+| id | <code>string</code> | id for the source (ex. participant id) |
+| element | <code>HTMLVideoElement</code> | HTMLVideoElement for the video source |
+| enabled | <code>boolean</code> | if source is enabled |
+| [displayText] | <code>string</code> | two character display text |
 
 <a name="updateSource"></a>
 
 Update a video source
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                |
-| ------ | ------------------- |
-| id     | <code>string</code> |
-| source | <code>any</code>    |
+| Param | Type |
+| --- | --- |
+| id | <code>string</code> | 
+| source | <code>any</code> | 
 
 <a name="removeSource"></a>
 
 Remove the video source for the participant
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param | Description                            |
-| ----- | -------------------------------------- |
-| id    | id for the source (ex. participant id) |
+| Param | Description |
+| --- | --- |
+| id | id for the source (ex. participant id) |
 
 <a name="removePinnedSource"></a>
 
 Remove the pinned source
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param | Description                            |
-| ----- | -------------------------------------- |
-| id    | id for the source (ex. participant id) |
+| Param | Description |
+| --- | --- |
+| id | id for the source (ex. participant id) |
 
 <a name="removeAllSources"></a>
 
@@ -126,4 +126,4 @@ Remove all sources
 
 Enable PiP
 
-**Kind**: global function
+**Kind**: global function  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
index 1dc5407b42362d4..68d9b48f76fb51b 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugin.md
@@ -11,159 +11,145 @@ web_core_version: 1.2.4
 The RTKPlugin module represents a single plugin in the meeting.
 A plugin can be obtained from one of the plugin arrays in `meeting.plugins`.
 For example,
-
 ```ts
 const plugin1 = meeting.plugins.active.get(pluginId);
 const plugin2 = meeting.plugins.all.get(pluginId);
 ```
 
-- [RTKPlugin](#module_RTKPlugin)
-  - [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
-    - [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
-    - [.telemetry](#module_RTKPlugin--module.exports+telemetry)
-    - [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
-    - [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
-    - [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
-    - [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
-    - [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
-    - [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
-    - [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
-    - [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
-    - ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
-    - ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
-    - [.activate()](#module_RTKPlugin--module.exports+activate)
-    - [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
+
+* [RTKPlugin](#module_RTKPlugin)
+    * [module.exports](#exp_module_RTKPlugin--module.exports) ⏏
+        * [new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)](#new_module_RTKPlugin--module.exports_new)
+        * [.telemetry](#module_RTKPlugin--module.exports+telemetry)
+        * [.sendIframeEvent(message)](#module_RTKPlugin--module.exports+sendIframeEvent)
+        * [.handleIframeMessage(iframeMessage)](#module_RTKPlugin--module.exports+handleIframeMessage)
+        * [.sendData(payload)](#module_RTKPlugin--module.exports+sendData)
+        * [.removeRTKPluginView(viewId)](#module_RTKPlugin--module.exports+removeRTKPluginView)
+        * [.addRTKPluginView(iframe, viewId)](#module_RTKPlugin--module.exports+addRTKPluginView)
+        * [.setActive(active)](#module_RTKPlugin--module.exports+setActive)
+        * [.activateForSelf()](#module_RTKPlugin--module.exports+activateForSelf)
+        * [.deactivateForSelf()](#module_RTKPlugin--module.exports+deactivateForSelf)
+        * ~~[.enable()](#module_RTKPlugin--module.exports+enable)~~
+        * ~~[.disable()](#module_RTKPlugin--module.exports+disable)~~
+        * [.activate()](#module_RTKPlugin--module.exports+activate)
+        * [.deactivate()](#module_RTKPlugin--module.exports+deactivate)
 
 <a name="exp_module_RTKPlugin--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKPlugin--module.exports_new"></a>
 
 #### new module.exports(context, plugin, pluginSocketHandler, self, participants, chat, meetingTitle)
 
-| Param               | Type                                |
-| ------------------- | ----------------------------------- |
-| context             | <code>Context</code>                |
-| plugin              | <code>RTKPluginResponse</code>      |
-| pluginSocketHandler | <code>RTKPluginSocketHandler</code> |
-| self                | <code>Self</code>                   |
-| participants        | <code>Participants</code>           |
-| chat                | <code>Chat</code>                   |
-| meetingTitle        | <code>string</code>                 |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| plugin | <code>RTKPluginResponse</code> | 
+| pluginSocketHandler | <code>RTKPluginSocketHandler</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
+| chat | <code>Chat</code> | 
+| meetingTitle | <code>string</code> | 
 
 <a name="module_RTKPlugin--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+sendIframeEvent"></a>
 
 #### module.exports.sendIframeEvent(message)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param   | Type                                | Description                              |
-| ------- | ----------------------------------- | ---------------------------------------- |
+| Param | Type | Description |
+| --- | --- | --- |
 | message | <code>RTKPluginIframeMessage</code> | Socket message forwarded to this plugin. |
 
 <a name="module_RTKPlugin--module.exports+handleIframeMessage"></a>
 
 #### module.exports.handleIframeMessage(iframeMessage)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param         | Type                                |
-| ------------- | ----------------------------------- |
-| iframeMessage | <code>RTKPluginIframeMessage</code> |
+| Param | Type |
+| --- | --- |
+| iframeMessage | <code>RTKPluginIframeMessage</code> | 
 
 <a name="module_RTKPlugin--module.exports+sendData"></a>
 
 #### module.exports.sendData(payload)
-
 This method is used to send arbitrary data to the plugin.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param             | Type                         | Description                                                            |
-| ----------------- | ---------------------------- | ---------------------------------------------------------------------- |
-| payload           | <code>SendDataOptions</code> | The payload that you want to send inside the plugin.                   |
-| payload.eventName | <code>string</code>          | Name of the event. This is used to listen for the event in plugin SDK. |
-| payload.data      | <code>any</code>             | Data you wish to emit. It can assume any data type.                    |
+| Param | Type | Description |
+| --- | --- | --- |
+| payload | <code>SendDataOptions</code> | The payload that you want to send inside the plugin. |
+| payload.eventName | <code>string</code> | Name of the event. This is used to listen for the event in plugin SDK. |
+| payload.data | <code>any</code> | Data you wish to emit. It can assume any data type. |
 
 <a name="module_RTKPlugin--module.exports+removeRTKPluginView"></a>
 
 #### module.exports.removeRTKPluginView(viewId)
-
 This method is used for cleaning up event listeners attached to an iframe. It must
 be used before the iframe is removed from the DOM.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param  | Type                | Default                          | Description                                                        |
-| ------ | ------------------- | -------------------------------- | ------------------------------------------------------------------ |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
 | viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+addRTKPluginView"></a>
 
 #### module.exports.addRTKPluginView(iframe, viewId)
-
 This method adds the communication layer between the plugin inside the iframe
 and the core application (meeting object) in the main window.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-| Param  | Type                                                              | Default                          | Description                                                        |
-| ------ | ----------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------ |
-| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |                                  | Iframe element to display this plugin.                             |
-| viewId | <code>string</code>                                               | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| iframe | <code>HTMLIFrameElement</code> \| <code>ReactNativeWebView</code> |  | Iframe element to display this plugin. |
+| viewId | <code>string</code> | <code>&quot;default&quot;</code> | ID of the view corresponding to this iframe. Default is 'default'. |
 
 <a name="module_RTKPlugin--module.exports+setActive"></a>
 
 #### module.exports.setActive(active)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
-
-| Param  | Type                 |
-| ------ | -------------------- |
-| active | <code>boolean</code> |
+| Param | Type |
+| --- | --- |
+| active | <code>boolean</code> | 
 
 <a name="module_RTKPlugin--module.exports+activateForSelf"></a>
 
 #### module.exports.activateForSelf()
-
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivateForSelf"></a>
 
 #### module.exports.deactivateForSelf()
-
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+enable"></a>
 
 #### ~~module.exports.enable()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+disable"></a>
 
 #### ~~module.exports.disable()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+activate"></a>
 
 #### module.exports.activate()
-
 Activate this plugin for all participants.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
 <a name="module_RTKPlugin--module.exports+deactivate"></a>
 
 #### module.exports.deactivate()
-
 Deactivate this plugin for all participants.
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKPlugin--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
index ff22e5a74589e76..8ea2b9486986701 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md
@@ -9,40 +9,37 @@ web_core_version: 1.2.4
 <a name="module_RTKPlugins"></a>
 
 The RTKPlugins module consists of all the plugins in the meeting. It has 2 maps:
-
 - `all`: Consists of all the plugins in the meeting.
 - `active`: Consists of the plugins that are currently in use.
 
+
 * [RTKPlugins](#module_RTKPlugins)
-  - [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
-    - [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
-    - [.all](#module_RTKPlugins--module.exports+all)
-    - [.active](#module_RTKPlugins--module.exports+active)
+    * [module.exports](#exp_module_RTKPlugins--module.exports) ⏏
+        * [new module.exports(logger)](#new_module_RTKPlugins--module.exports_new)
+        * [.all](#module_RTKPlugins--module.exports+all)
+        * [.active](#module_RTKPlugins--module.exports+active)
 
 <a name="exp_module_RTKPlugins--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKPlugins--module.exports_new"></a>
 
 #### new module.exports(logger)
 
-| Param  | Type                |
-| ------ | ------------------- |
-| logger | <code>Logger</code> |
+| Param | Type |
+| --- | --- |
+| logger | <code>Logger</code> | 
 
 <a name="module_RTKPlugins--module.exports+all"></a>
 
 #### module.exports.all
-
 All plugins accessible by the current user.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
 <a name="module_RTKPlugins--module.exports+active"></a>
 
 #### module.exports.active
-
 All plugins that are currently enabled in the room.
 
-**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)
+**Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKPlugins--module.exports)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
index 25d6abf2a17b0fe..95f20dbb49fe688 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKPolls.md
@@ -10,42 +10,41 @@ web_core_version: 1.2.4
 
 The RTKPolls module consists of the polls that have been created in the meeting.
 
-- [RTKPolls](#module_RTKPolls)
-  - [.items](#module_RTKPolls+items)
-  - [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
-  - [.vote(pollId, index)](#module_RTKPolls+vote)
+
+* [RTKPolls](#module_RTKPolls)
+    * [.items](#module_RTKPolls+items)
+    * [.create(question, options, anonymous, hideVotes)](#module_RTKPolls+create)
+    * [.vote(pollId, index)](#module_RTKPolls+vote)
 
 <a name="module_RTKPolls+items"></a>
 
 ### meeting.polls.items
-
 An array of poll items.
 
 **Kind**: instance property of [<code>RTKPolls</code>](#module_RTKPolls)  
 <a name="module_RTKPolls+create"></a>
 
 ### meeting.polls.create(question, options, anonymous, hideVotes)
-
 Creates a poll in the meeting.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
 
-| Param     | Default            | Description                                |
-| --------- | ------------------ | ------------------------------------------ |
-| question  |                    | The question that is to be voted for.      |
-| options   |                    | The options of the poll.                   |
-| anonymous | <code>false</code> | If true, the poll votes are anonymous.     |
+| Param | Default | Description |
+| --- | --- | --- |
+| question |  | The question that is to be voted for. |
+| options |  | The options of the poll. |
+| anonymous | <code>false</code> | If true, the poll votes are anonymous. |
 | hideVotes | <code>false</code> | If true, the votes on the poll are hidden. |
 
 <a name="module_RTKPolls+vote"></a>
 
 ### meeting.polls.vote(pollId, index)
-
 Casts a vote on an existing poll.
 
-**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)
+**Kind**: instance method of [<code>RTKPolls</code>](#module_RTKPolls)  
 
-| Param  | Description                                |
-| ------ | ------------------------------------------ |
+| Param | Description |
+| --- | --- |
 | pollId | The ID of the poll that is to be voted on. |
-| index  | The index of the option.                   |
+| index | The index of the option. |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
index e63b1525fae136c..4b2dd3b6116b3dd 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKRecording.md
@@ -11,43 +11,39 @@ web_core_version: 1.2.4
 The RTKRecording module represents the state of the current recording, and allows
 to start/stop recordings and check if there's a recording in progress.
 
-- [RTKRecording](#module_RTKRecording)
-  - [.telemetry](#module_RTKRecording+telemetry)
-  - [.start()](#module_RTKRecording+start)
-  - [.stop()](#module_RTKRecording+stop)
-  - [.pause()](#module_RTKRecording+pause)
-  - [.resume()](#module_RTKRecording+resume)
+
+* [RTKRecording](#module_RTKRecording)
+    * [.telemetry](#module_RTKRecording+telemetry)
+    * [.start()](#module_RTKRecording+start)
+    * [.stop()](#module_RTKRecording+stop)
+    * [.pause()](#module_RTKRecording+pause)
+    * [.resume()](#module_RTKRecording+resume)
 
 <a name="module_RTKRecording+telemetry"></a>
 
 ### meeting.recording.telemetry
-
 **Kind**: instance property of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+start"></a>
 
 ### meeting.recording.start()
-
 Starts recording the meeting.
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+stop"></a>
 
 ### meeting.recording.stop()
-
 Stops all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+pause"></a>
 
 ### meeting.recording.pause()
-
 Pauses all recording currently in 'RECORDING' state
 
 **Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
 <a name="module_RTKRecording+resume"></a>
 
 ### meeting.recording.resume()
-
 Resumes all recording currently in 'PAUSED' state
 
-**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)
+**Kind**: instance method of [<code>RTKRecording</code>](#module_RTKRecording)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
index 1ad8cd81f058059..aa4a71840eac6b8 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelf.md
@@ -12,43 +12,42 @@ The RTKSelf module represents the current user, and allows to modify the state
 of the user in the meeting. The audio and video streams of the user can be retrieved from
 this module.
 
-- [RTKSelf](#module_RTKSelf)
-  - [.telemetry](#module_RTKSelf+telemetry)
-  - [.peerId](#module_RTKSelf+peerId)
-  - [.roomState](#module_RTKSelf+roomState)
-  - [.permissions](#module_RTKSelf+permissions)
-  - [.config](#module_RTKSelf+config)
-  - [.roomJoined](#module_RTKSelf+roomJoined)
-  - [.isPinned](#module_RTKSelf+isPinned)
-  - [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
-  - [.setName(name)](#module_RTKSelf+setName)
-  - [.setupTracks(options)](#module_RTKSelf+setupTracks)
-  - [.enableAudio()](#module_RTKSelf+enableAudio)
-  - [.enableVideo()](#module_RTKSelf+enableVideo)
-  - [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
-  - [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
-  - [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
-  - [.disableAudio()](#module_RTKSelf+disableAudio)
-  - [.disableVideo()](#module_RTKSelf+disableVideo)
-  - [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
-  - [.getAllDevices()](#module_RTKSelf+getAllDevices)
-  - [.setIsPinned()](#module_RTKSelf+setIsPinned)
-  - [.pin()](#module_RTKSelf+pin)
-  - [.unpin()](#module_RTKSelf+unpin)
-  - [.hide()](#module_RTKSelf+hide)
-  - [.show()](#module_RTKSelf+show)
-  - [.setDevice(device)](#module_RTKSelf+setDevice)
-  - [.updateVideo()](#module_RTKSelf+updateVideo)
+
+* [RTKSelf](#module_RTKSelf)
+    * [.telemetry](#module_RTKSelf+telemetry)
+    * [.peerId](#module_RTKSelf+peerId)
+    * [.roomState](#module_RTKSelf+roomState)
+    * [.permissions](#module_RTKSelf+permissions)
+    * [.config](#module_RTKSelf+config)
+    * [.roomJoined](#module_RTKSelf+roomJoined)
+    * [.isPinned](#module_RTKSelf+isPinned)
+    * [.cleanupEvents()](#module_RTKSelf+cleanupEvents)
+    * [.setName(name)](#module_RTKSelf+setName)
+    * [.setupTracks(options)](#module_RTKSelf+setupTracks)
+    * [.enableAudio()](#module_RTKSelf+enableAudio)
+    * [.enableVideo()](#module_RTKSelf+enableVideo)
+    * [.updateVideoConstraints()](#module_RTKSelf+updateVideoConstraints)
+    * [.enableScreenShare()](#module_RTKSelf+enableScreenShare)
+    * [.updateScreenshareConstraints()](#module_RTKSelf+updateScreenshareConstraints)
+    * [.disableAudio()](#module_RTKSelf+disableAudio)
+    * [.disableVideo()](#module_RTKSelf+disableVideo)
+    * [.disableScreenShare()](#module_RTKSelf+disableScreenShare)
+    * [.getAllDevices()](#module_RTKSelf+getAllDevices)
+    * [.setIsPinned()](#module_RTKSelf+setIsPinned)
+    * [.pin()](#module_RTKSelf+pin)
+    * [.unpin()](#module_RTKSelf+unpin)
+    * [.hide()](#module_RTKSelf+hide)
+    * [.show()](#module_RTKSelf+show)
+    * [.setDevice(device)](#module_RTKSelf+setDevice)
+    * [.updateVideo()](#module_RTKSelf+updateVideo)
 
 <a name="module_RTKSelf+telemetry"></a>
 
 ### meeting.self.telemetry
-
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+peerId"></a>
 
 ### meeting.self.peerId
-
 NOTE(ishita1805): Discussed with Ravindra, added a duplicate for consistency
 when using identifiers in Locker.
 We might want to look at deprecating the `id` sometime later.
@@ -57,7 +56,6 @@ We might want to look at deprecating the `id` sometime later.
 <a name="module_RTKSelf+roomState"></a>
 
 ### meeting.self.roomState
-
 Returns the current state of room
 init - Initial State
 joined - User is in the meeting
@@ -71,76 +69,67 @@ ended - The meeting was ended
 <a name="module_RTKSelf+permissions"></a>
 
 ### meeting.self.permissions
-
 Returns the current permission given to the user for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+config"></a>
 
 ### meeting.self.config
-
 Returns configuration for the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+roomJoined"></a>
 
 ### meeting.self.roomJoined
-
 Returns true if the local participant has joined the meeting.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+isPinned"></a>
 
 ### meeting.self.isPinned
-
 Returns true if the current user is pinned.
 
 **Kind**: instance property of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+cleanupEvents"></a>
 
 ### meeting.self.cleanupEvents()
-
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setName"></a>
 
 ### meeting.self.setName(name)
-
 The name of the user can be set by calling this method.
 This will get reflected to other participants ONLY if
 this method is called before the room is joined.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param | Type                | Description       |
-| ----- | ------------------- | ----------------- |
-| name  | <code>string</code> | Name of the user. |
+| Param | Type | Description |
+| --- | --- | --- |
+| name | <code>string</code> | Name of the user. |
 
 <a name="module_RTKSelf+setupTracks"></a>
 
 ### meeting.self.setupTracks(options)
-
 Sets up the local media tracks.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param                | Type                 | Description                                       |
-| -------------------- | -------------------- | ------------------------------------------------- |
-| options              | <code>Object</code>  | The audio and video options.                      |
-| [options.video]      | <code>boolean</code> | If true, the video stream is fetched.             |
-| [options.audio]      | <code>boolean</code> | If true, the audio stream is fetched.             |
+| Param | Type | Description |
+| --- | --- | --- |
+| options | <code>Object</code> | The audio and video options. |
+| [options.video] | <code>boolean</code> | If true, the video stream is fetched. |
+| [options.audio] | <code>boolean</code> | If true, the audio stream is fetched. |
 | [options.forceReset] | <code>boolean</code> | If true, force resets tracks before re-acquiring. |
 
 <a name="module_RTKSelf+enableAudio"></a>
 
 ### meeting.self.enableAudio()
-
 This method is used to unmute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+enableVideo"></a>
 
 ### meeting.self.enableVideo()
-
 This method is used to start streaming the local participant's video
 to the meeting.
 
@@ -148,7 +137,6 @@ to the meeting.
 <a name="module_RTKSelf+updateVideoConstraints"></a>
 
 ### meeting.self.updateVideoConstraints()
-
 This method is used to apply constraints to the current video
 stream.
 
@@ -156,7 +144,6 @@ stream.
 <a name="module_RTKSelf+enableScreenShare"></a>
 
 ### meeting.self.enableScreenShare()
-
 This method is used to start sharing the local participant's screen
 to the meeting.
 
@@ -164,7 +151,6 @@ to the meeting.
 <a name="module_RTKSelf+updateScreenshareConstraints"></a>
 
 ### meeting.self.updateScreenshareConstraints()
-
 This method is used to apply constraints to the current screenshare
 stream.
 
@@ -172,40 +158,34 @@ stream.
 <a name="module_RTKSelf+disableAudio"></a>
 
 ### meeting.self.disableAudio()
-
 This method is used to mute the local participant's audio.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableVideo"></a>
 
 ### meeting.self.disableVideo()
-
 This participant is used to disable the local participant's video.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+disableScreenShare"></a>
 
 ### meeting.self.disableScreenShare()
-
 This method is used to stop sharing the local participant's screen.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+getAllDevices"></a>
 
 ### meeting.self.getAllDevices()
-
 Returns all media devices accessible by the local participant.
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setIsPinned"></a>
 
 ### meeting.self.setIsPinned()
-
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+pin"></a>
 
 ### meeting.self.pin()
-
 Returns `self.id` if user has permission
 to pin participants.
 
@@ -213,7 +193,6 @@ to pin participants.
 <a name="module_RTKSelf+unpin"></a>
 
 ### meeting.self.unpin()
-
 Returns `self.id` if user has permission
 to unpin participants.
 
@@ -221,33 +200,29 @@ to unpin participants.
 <a name="module_RTKSelf+hide"></a>
 
 ### meeting.self.hide()
-
 Hide's user's tile in the UI (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+show"></a>
 
 ### meeting.self.show()
-
 Show's user's tile in the UI if hidden (locally)
 
 **Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 <a name="module_RTKSelf+setDevice"></a>
 
 ### meeting.self.setDevice(device)
-
 Change the current media device that is being used by the local participant.
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
 
-| Param  | Type                         | Description                                                                                      |
-| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
 
 <a name="module_RTKSelf+updateVideo"></a>
 
 ### meeting.self.updateVideo()
-
 Internal method, do not use
 
-**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)
+**Kind**: instance method of [<code>RTKSelf</code>](#module_RTKSelf)  
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
index be8f537561e76eb..9e2d6335663b878 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md
@@ -147,16 +147,16 @@ Returns true if screen share is enabled.
 **Kind**: global variable  
 <a name="init"></a>
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param                 | Type                          | Default            |
-| --------------------- | ----------------------------- | ------------------ |
-| options               | <code>Object</code>           |                    |
-| [options.video]       | <code>boolean</code>          |                    |
-| [options.audio]       | <code>boolean</code>          |                    |
-| [options.constraints] | <code>MediaConstraints</code> |                    |
-| [skipAwaits]          | <code>boolean</code>          | <code>false</code> |
-| [context]             | <code>Context</code>          | <code></code>      |
+| Param | Type | Default |
+| --- | --- | --- |
+| options | <code>Object</code> |  | 
+| [options.video] | <code>boolean</code> |  | 
+| [options.audio] | <code>boolean</code> |  | 
+| [options.constraints] | <code>MediaConstraints</code> |  | 
+| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
+| [context] | <code>Context</code> | <code></code> | 
 
 <a name="addAudioMiddleware"></a>
 
@@ -165,21 +165,21 @@ If there are more than 1 audio middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| audioMiddleware | <code>AudioMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| audioMiddleware | <code>AudioMiddleware</code> | 
 
 <a name="removeAudioMiddleware"></a>
 
 Removes the audio middleware, if it is there.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| audioMiddleware | <code>AudioMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| audioMiddleware | <code>AudioMiddleware</code> | 
 
 <a name="removeAllAudioMiddlewares"></a>
 
@@ -193,32 +193,32 @@ If there are more than 1 video middlewares,
 they will be executed in the sequence they were added in.
 If you want the sequence to be altered, please remove all previous middlewares and re-add.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| videoMiddleware | <code>VideoMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| videoMiddleware | <code>VideoMiddleware</code> | 
 
 <a name="setVideoMiddlewareGlobalConfig"></a>
 
 Sets global config to be used by video middlewares.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param                                 | Type                                     | Description                                                                                                                                                                                                                                                                                               |
-| ------------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| config                                | <code>VideoMiddlewareGlobalConfig</code> | config                                                                                                                                                                                                                                                                                                    |
-| config.disablePerFrameCanvasRendering | <code>boolean</code>                     | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas, it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
+| Param | Type | Description |
+| --- | --- | --- |
+| config | <code>VideoMiddlewareGlobalConfig</code> | config |
+| config.disablePerFrameCanvasRendering | <code>boolean</code> | If set to true, Instead of calling Middleware for every frame, Middleware will only be called once that too with empty canvas,  it is the responsibility of the middleware author to keep updating this canvas. `meeting.self.rawVideoTrack` can be used to retrieve video track for the periodic updates. |
 
 <a name="removeVideoMiddleware"></a>
 
 Removes the video middleware, if it is there.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param           | Type                         |
-| --------------- | ---------------------------- |
-| videoMiddleware | <code>VideoMiddleware</code> |
+| Param | Type |
+| --- | --- |
+| videoMiddleware | <code>VideoMiddleware</code> | 
 
 <a name="removeAllVideoMiddlewares"></a>
 
@@ -249,19 +249,20 @@ Returns the local participant's speaker devices.
 
 Returns the local participant's device, indexed by ID and kind.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param    | Type                                                                                                 | Description                                       |
-| -------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
-| deviceId | <code>string</code>                                                                                  | The ID of the device.                             |
-| kind     | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
+| Param | Type | Description |
+| --- | --- | --- |
+| deviceId | <code>string</code> | The ID of the device. |
+| kind | <code>&#x27;audio&#x27;</code> \| <code>&#x27;video&#x27;</code> \| <code>&#x27;speaker&#x27;</code> | The kind of the device: audio, video, or speaker. |
 
 <a name="setDevice"></a>
 
 Change the current media device that is being used by the local participant.
 
-**Kind**: global function
+**Kind**: global function  
 
-| Param  | Type                         | Description                                                                                      |
-| ------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
+| Param | Type | Description |
+| --- | --- | --- |
 | device | <code>MediaDeviceInfo</code> | The device that is to be used. A device of the same `kind` will be replaced. the primary stream. |
+
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
index 35bd0dcc153011f..787b7778e4ea72e 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStage.md
@@ -13,76 +13,70 @@ RTKStage refers to a virtual area, where participants stream are visible to othe
 When a participant is off stage, they are not producing media
 but only consuming media from participants who are on RTKStage
 
-- [RTKStage](#module_RTKStage)
-  - [module.exports](#exp_module_RTKStage--module.exports) ⏏
-    - [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
-    - [.telemetry](#module_RTKStage--module.exports+telemetry)
-    - [.peerId](#module_RTKStage--module.exports+peerId)
-    - [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
-    - [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
-    - [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
-    - [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
-    - [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
-    - [.join()](#module_RTKStage--module.exports+join)
-    - [.leave()](#module_RTKStage--module.exports+leave)
-    - [.kick(userIds)](#module_RTKStage--module.exports+kick)
+
+* [RTKStage](#module_RTKStage)
+    * [module.exports](#exp_module_RTKStage--module.exports) ⏏
+        * [new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)](#new_module_RTKStage--module.exports_new)
+        * [.telemetry](#module_RTKStage--module.exports+telemetry)
+        * [.peerId](#module_RTKStage--module.exports+peerId)
+        * [.getAccessRequests()](#module_RTKStage--module.exports+getAccessRequests)
+        * [.requestAccess()](#module_RTKStage--module.exports+requestAccess)
+        * [.cancelRequestAccess()](#module_RTKStage--module.exports+cancelRequestAccess)
+        * [.grantAccess()](#module_RTKStage--module.exports+grantAccess)
+        * [.denyAccess()](#module_RTKStage--module.exports+denyAccess)
+        * [.join()](#module_RTKStage--module.exports+join)
+        * [.leave()](#module_RTKStage--module.exports+leave)
+        * [.kick(userIds)](#module_RTKStage--module.exports+kick)
 
 <a name="exp_module_RTKStage--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKStage--module.exports_new"></a>
 
 #### new module.exports(context, self, participants, stageSocketHandler, roomSocketHandler)
 
-| Param              | Type                               |
-| ------------------ | ---------------------------------- |
-| context            | <code>Context</code>               |
-| self               | <code>Self</code>                  |
-| participants       | <code>Participants</code>          |
-| stageSocketHandler | <code>RTKStageSocketHandler</code> |
-| roomSocketHandler  | <code>RoomSocketHandler</code>     |
+| Param | Type |
+| --- | --- |
+| context | <code>Context</code> | 
+| self | <code>Self</code> | 
+| participants | <code>Participants</code> | 
+| stageSocketHandler | <code>RTKStageSocketHandler</code> | 
+| roomSocketHandler | <code>RoomSocketHandler</code> | 
 
 <a name="module_RTKStage--module.exports+telemetry"></a>
 
 #### module.exports.telemetry
-
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+peerId"></a>
 
 #### module.exports.peerId
-
 Returns the peerId of the current user
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+getAccessRequests"></a>
 
 #### module.exports.getAccessRequests()
-
 Method to fetch all RTKStage access requests from viewers
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+requestAccess"></a>
 
 #### module.exports.requestAccess()
-
 Method to send a request to privileged users to join the stage
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+cancelRequestAccess"></a>
 
 #### module.exports.cancelRequestAccess()
-
 Method to cancel a previous RTKStage join request
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
 <a name="module_RTKStage--module.exports+grantAccess"></a>
 
 #### module.exports.grantAccess()
-
 Method to grant access to RTKStage.
-This can be in response to a RTKStage Join request but it can be called on other users as well
+	This can be in response to a RTKStage Join request but it can be called on other users as well
 
 `permissions.acceptRTKStageRequests` privilege required
 
@@ -90,7 +84,6 @@ This can be in response to a RTKStage Join request but it can be called on other
 <a name="module_RTKStage--module.exports+denyAccess"></a>
 
 #### module.exports.denyAccess()
-
 Method to deny access to RTKStage.
 This should be called in response to a RTKStage Join request
 
@@ -98,7 +91,6 @@ This should be called in response to a RTKStage Join request
 <a name="module_RTKStage--module.exports+join"></a>
 
 #### module.exports.join()
-
 Method to join the stage
 Users either need to have the permission in the preset or must be accepted by a privileged
 user to call this method
@@ -107,7 +99,6 @@ user to call this method
 <a name="module_RTKStage--module.exports+leave"></a>
 
 #### module.exports.leave()
-
 Method to leave the stage
 Users must either be on the stage already or be accepted to join the stage
 to call this method
@@ -116,13 +107,13 @@ to call this method
 <a name="module_RTKStage--module.exports+kick"></a>
 
 #### module.exports.kick(userIds)
-
 Method to kick a user off the stage
 
 `permissions.acceptRTKStageRequests` privilege required
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStage--module.exports)  
+
+| Param | Type |
+| --- | --- |
+| userIds | <code>Array.&lt;string&gt;</code> | 
 
-| Param   | Type                              |
-| ------- | --------------------------------- |
-| userIds | <code>Array.&lt;string&gt;</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
index 51d98a4f1ebc2ea..c27dd5a9443bf19 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKStore.md
@@ -12,136 +12,127 @@ This module represents a single global store.
 The store can be accessed from the `meeting.stores` module.
 
 **Returns**: An instance of RTKStore.  
-**Example**
-
+**Example**  
 ```js
-const handRaiseRTKStore = meeting.stores.stores.get("handRaise");
+const handRaiseRTKStore = meeting.stores.stores.get('handRaise');
 ```
 
-- [RTKStore](#module_RTKStore) ⇒
-  - [module.exports](#exp_module_RTKStore--module.exports) ⏏
-    - [new module.exports(args)](#new_module_RTKStore--module.exports_new)
-    - [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
-    - [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
-    - [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
-    - [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
-    - [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
-    - [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
-    - [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
-    - [.populate(data)](#module_RTKStore--module.exports+populate)
+* [RTKStore](#module_RTKStore) ⇒
+    * [module.exports](#exp_module_RTKStore--module.exports) ⏏
+        * [new module.exports(args)](#new_module_RTKStore--module.exports_new)
+        * [.set(key, value, [sync], [emit])](#module_RTKStore--module.exports+set) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.bulkSet(data)](#module_RTKStore--module.exports+bulkSet) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.update(key, value, [sync])](#module_RTKStore--module.exports+update) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.delete(key, [sync], [emit])](#module_RTKStore--module.exports+delete) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.bulkDelete(data)](#module_RTKStore--module.exports+bulkDelete) ⇒ <code>Promise.&lt;void&gt;</code>
+        * [.get(key)](#module_RTKStore--module.exports+get) ⇒ <code>any</code>
+        * [.getAll()](#module_RTKStore--module.exports+getAll) ⇒ <code>RTKStoreData</code>
+        * [.updateRateLimits(num, period)](#module_RTKStore--module.exports+updateRateLimits)
+        * [.updateBulkRateLimits(num, period)](#module_RTKStore--module.exports+updateBulkRateLimits)
+        * [.subscribe(key, cb)](#module_RTKStore--module.exports+subscribe) ⇒ <code>void</code>
+        * [.unsubscribe(key, [cb])](#module_RTKStore--module.exports+unsubscribe) ⇒ <code>void</code>
+        * [.populate(data)](#module_RTKStore--module.exports+populate)
 
 <a name="exp_module_RTKStore--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKStore--module.exports_new"></a>
 
 #### new module.exports(args)
 
-| Param              | Type                             |
-| ------------------ | -------------------------------- |
-| args               | <code>Object</code>              |
-| args.name          | <code>string</code>              |
-| args.socketHandler | <code>PluginSocketHandler</code> |
-| args.meetingId     | <code>string</code>              |
+| Param | Type |
+| --- | --- |
+| args | <code>Object</code> | 
+| args.name | <code>string</code> | 
+| args.socketHandler | <code>PluginSocketHandler</code> | 
+| args.meetingId | <code>string</code> | 
 
 <a name="module_RTKStore--module.exports+set"></a>
 
 #### module.exports.set(key, value, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Sets a value in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default            | Description                             |
-| ------ | -------------------- | ------------------ | --------------------------------------- |
-| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
-| value  | <code>any</code>     |                    | Data to be set.                         |
-| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| value | <code>any</code> |  | Data to be set. |
+| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
 
 <a name="module_RTKStore--module.exports+bulkSet"></a>
 
 #### module.exports.bulkSet(data) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Sets multiple values in the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param | Type                                                   |
-| ----- | ------------------------------------------------------ |
-| data  | <code>Array.&lt;{key: string, payload: any}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| data | <code>Array.&lt;{key: string, payload: any}&gt;</code> | 
 
 <a name="module_RTKStore--module.exports+update"></a>
 
 #### module.exports.update(key, value, [sync]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Updates an already existing value in the store.
 If the value stored is `['a', 'b']`, the operation
 `store.update(key, ['c'])` will modify
 the value to `['a','b','c']`.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default           | Description                             |
-| ------ | -------------------- | ----------------- | --------------------------------------- |
-| key    | <code>string</code>  |                   | Unique identifier used to store value.  |
-| value  | <code>any</code>     |                   | Data to be updated.                     |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| value | <code>any</code> |  | Data to be updated. |
 | [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
 
 <a name="module_RTKStore--module.exports+delete"></a>
 
 #### module.exports.delete(key, [sync], [emit]) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Deletes a key value pair form the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param  | Type                 | Default            | Description                             |
-| ------ | -------------------- | ------------------ | --------------------------------------- |
-| key    | <code>string</code>  |                    | Unique identifier used to store value.  |
-| [sync] | <code>boolean</code> | <code>true</code>  | Whether to sync change to remote store. |
-| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers.   |
+| Param | Type | Default | Description |
+| --- | --- | --- | --- |
+| key | <code>string</code> |  | Unique identifier used to store value. |
+| [sync] | <code>boolean</code> | <code>true</code> | Whether to sync change to remote store. |
+| [emit] | <code>boolean</code> | <code>false</code> | Whether to emit to local subscribers. |
 
 <a name="module_RTKStore--module.exports+bulkDelete"></a>
 
 #### module.exports.bulkDelete(data) ⇒ <code>Promise.&lt;void&gt;</code>
-
 Deletes multiple values from the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.
+**Returns**: <code>Promise.&lt;void&gt;</code> - A promise.  
 
-| Param | Type                                     |
-| ----- | ---------------------------------------- |
-| data  | <code>Array.&lt;{key: string}&gt;</code> |
+| Param | Type |
+| --- | --- |
+| data | <code>Array.&lt;{key: string}&gt;</code> | 
 
 <a name="module_RTKStore--module.exports+get"></a>
 
 #### module.exports.get(key) ⇒ <code>any</code>
-
 Returns value for the given key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>any</code> - Value for the given key.
+**Returns**: <code>any</code> - Value for the given key.  
 
-| Param | Type                | Description                            |
-| ----- | ------------------- | -------------------------------------- |
-| key   | <code>string</code> | Unique identifier used to store value. |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
 
 <a name="module_RTKStore--module.exports+getAll"></a>
 
 #### module.exports.getAll() ⇒ <code>RTKStoreData</code>
-
 Returns the entire store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
@@ -149,59 +140,55 @@ Returns the entire store.
 <a name="module_RTKStore--module.exports+updateRateLimits"></a>
 
 #### module.exports.updateRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKStore--module.exports+updateBulkRateLimits"></a>
 
 #### module.exports.updateBulkRateLimits(num, period)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
-
-| Param  | Type                |
-| ------ | ------------------- |
-| num    | <code>number</code> |
-| period | <code>number</code> |
+| Param | Type |
+| --- | --- |
+| num | <code>number</code> | 
+| period | <code>number</code> | 
 
 <a name="module_RTKStore--module.exports+subscribe"></a>
 
 #### module.exports.subscribe(key, cb) ⇒ <code>void</code>
-
 Listens for data change on a store key.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void
+**Returns**: <code>void</code> - void  
 
-| Param | Type                  | Description                                                     |
-| ----- | --------------------- | --------------------------------------------------------------- |
-| key   | <code>string</code>   | Unique identifier used to store value.                          |
-| cb    | <code>function</code> | The callback function that gets executed when data is modified. |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
+| cb | <code>function</code> | The callback function that gets executed when data is modified. |
 
 <a name="module_RTKStore--module.exports+unsubscribe"></a>
 
 #### module.exports.unsubscribe(key, [cb]) ⇒ <code>void</code>
-
 Removes all listeners for a key on the store.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
-**Returns**: <code>void</code> - void
+**Returns**: <code>void</code> - void  
 
-| Param | Type                  | Description                            |
-| ----- | --------------------- | -------------------------------------- |
-| key   | <code>string</code>   | Unique identifier used to store value. |
-| [cb]  | <code>function</code> | Callback to be removed.                |
+| Param | Type | Description |
+| --- | --- | --- |
+| key | <code>string</code> | Unique identifier used to store value. |
+| [cb] | <code>function</code> | Callback to be removed. |
 
 <a name="module_RTKStore--module.exports+populate"></a>
 
 #### module.exports.populate(data)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)  
 
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RTKStore--module.exports)
+| Param | Type |
+| --- | --- |
+| data | <code>RTKStoreData</code> | 
 
-| Param | Type                      |
-| ----- | ------------------------- |
-| data  | <code>RTKStoreData</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
index e5a1e74b8e69bcf..88539296c8905b0 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RTKThemePreset.md
@@ -10,78 +10,72 @@ web_core_version: 1.2.4
 
 The RTKThemePreset class represents the meeting theme for the current participant
 
-- [RTKThemePreset](#module_RTKThemePreset)
-  - [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
-    - [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
-    - _instance_
-      - ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
-      - ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
-      - ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
-      - ~~[.header](#module_RTKThemePreset--module.exports+header)~~
-      - ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
-      - [.viewType](#module_RTKThemePreset--module.exports+viewType)
-      - [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
-      - [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
-      - [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
-      - ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
-      - [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
-    - _static_
-      - [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
-      - [.default()](#module_RTKThemePreset--module.exports.default)
-      - [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
+
+* [RTKThemePreset](#module_RTKThemePreset)
+    * [module.exports](#exp_module_RTKThemePreset--module.exports) ⏏
+        * [new module.exports(preset)](#new_module_RTKThemePreset--module.exports_new)
+        * _instance_
+            * ~~[.setupScreen](#module_RTKThemePreset--module.exports+setupScreen)~~
+            * ~~[.waitingRoom](#module_RTKThemePreset--module.exports+waitingRoom)~~
+            * ~~[.controlBar](#module_RTKThemePreset--module.exports+controlBar)~~
+            * ~~[.header](#module_RTKThemePreset--module.exports+header)~~
+            * ~~[.pipMode](#module_RTKThemePreset--module.exports+pipMode)~~
+            * [.viewType](#module_RTKThemePreset--module.exports+viewType)
+            * [.livestreamViewerQualities](#module_RTKThemePreset--module.exports+livestreamViewerQualities)
+            * [.maxVideoStreams](#module_RTKThemePreset--module.exports+maxVideoStreams)
+            * [.maxScreenShareCount](#module_RTKThemePreset--module.exports+maxScreenShareCount)
+            * ~~[.plugins](#module_RTKThemePreset--module.exports+plugins)~~
+            * [.disabledPlugins](#module_RTKThemePreset--module.exports+disabledPlugins)
+        * _static_
+            * [.fromResponse(preset)](#module_RTKThemePreset--module.exports.fromResponse)
+            * [.default()](#module_RTKThemePreset--module.exports.default)
+            * [.init([preset], [useDefault])](#module_RTKThemePreset--module.exports.init)
 
 <a name="exp_module_RTKThemePreset--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RTKThemePreset--module.exports_new"></a>
 
 #### new module.exports(preset)
 
-| Param  | Type                            |
-| ------ | ------------------------------- |
-| preset | <code>PresetV2CamelCased</code> |
+| Param | Type |
+| --- | --- |
+| preset | <code>PresetV2CamelCased</code> | 
 
 <a name="module_RTKThemePreset--module.exports+setupScreen"></a>
 
 #### ~~module.exports.setupScreen~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+waitingRoom"></a>
 
 #### ~~module.exports.waitingRoom~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+controlBar"></a>
 
 #### ~~module.exports.controlBar~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+header"></a>
 
 #### ~~module.exports.header~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+pipMode"></a>
 
 #### ~~module.exports.pipMode~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+viewType"></a>
 
 #### module.exports.viewType
-
 The `viewType` tells the type of the meeting
 possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 
@@ -89,7 +83,6 @@ possible values are: GROUP_CALL| LIVESTREAM | CHAT | AUDIO_ROOM
 <a name="module_RTKThemePreset--module.exports+livestreamViewerQualities"></a>
 
 #### module.exports.livestreamViewerQualities
-
 The `livestreamViewerQualities` specifies the allowed qualities of a stream,
 that can be viewed by a livestream viewer
 
@@ -97,7 +90,6 @@ that can be viewed by a livestream viewer
 <a name="module_RTKThemePreset--module.exports+maxVideoStreams"></a>
 
 #### module.exports.maxVideoStreams
-
 The `maxVideoStreams` contains the maximum video
 streams for mobile and desktop
 
@@ -105,7 +97,6 @@ streams for mobile and desktop
 <a name="module_RTKThemePreset--module.exports+maxScreenShareCount"></a>
 
 #### module.exports.maxScreenShareCount
-
 The `maxScreenShareCount` contains the maximum
 possible concurrent screen shares
 
@@ -113,41 +104,37 @@ possible concurrent screen shares
 <a name="module_RTKThemePreset--module.exports+plugins"></a>
 
 #### ~~module.exports.plugins~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports+disabledPlugins"></a>
 
 #### module.exports.disabledPlugins
-
 The `disabledPlugins` property returns id of all disabled plugins
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 <a name="module_RTKThemePreset--module.exports.fromResponse"></a>
 
 #### module.exports.fromResponse(preset)
-
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
-**Deprecated.**: Use init()
+**Deprecated.**: Use init()  
 
-| Param  | Type                            |
-| ------ | ------------------------------- |
-| preset | <code>PresetV2CamelCased</code> |
+| Param | Type |
+| --- | --- |
+| preset | <code>PresetV2CamelCased</code> | 
 
 <a name="module_RTKThemePreset--module.exports.default"></a>
 
 #### module.exports.default()
-
 **Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 **Deprecated.**: Use init()  
 <a name="module_RTKThemePreset--module.exports.init"></a>
 
 #### module.exports.init([preset], [useDefault])
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RTKThemePreset--module.exports)
+| Param | Type | Default |
+| --- | --- | --- |
+| [preset] | <code>PresetV2CamelCased</code> |  | 
+| [useDefault] | <code>boolean</code> | <code>true</code> | 
 
-| Param        | Type                            | Default           |
-| ------------ | ------------------------------- | ----------------- |
-| [preset]     | <code>PresetV2CamelCased</code> |                   |
-| [useDefault] | <code>boolean</code>            | <code>true</code> |
diff --git a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
index 31f2a68764c9ee9..1afafcb4fd4b751 100644
--- a/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
+++ b/src/content/docs/realtime/realtimekit/core/api-reference/RealtimeKitClient.md
@@ -13,46 +13,45 @@ An object of the RealtimeKitClient class can be created using
 `await RealtimeKitClient.init({ ... })`. Typically, an object of `RealtimeKitClient` is
 named `meeting`.
 
-- [RealtimeKitClient](#module_RealtimeKitClient)
-  - [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
-    - [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
-    - _instance_
-      - [.participants](#module_RealtimeKitClient--module.exports+participants)
-      - [.self](#module_RealtimeKitClient--module.exports+self)
-      - [.meta](#module_RealtimeKitClient--module.exports+meta)
-      - [.ai](#module_RealtimeKitClient--module.exports+ai)
-      - [.plugins](#module_RealtimeKitClient--module.exports+plugins)
-      - [.chat](#module_RealtimeKitClient--module.exports+chat)
-      - [.polls](#module_RealtimeKitClient--module.exports+polls)
-      - [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
-      - [.**internals**](#module_RealtimeKitClient--module.exports+__internals__)
-      - [.join()](#module_RealtimeKitClient--module.exports+join)
-      - [.leave()](#module_RealtimeKitClient--module.exports+leave)
-      - ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
-      - ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
-    - _static_
-      - [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
-      - [.init(options)](#module_RealtimeKitClient--module.exports.init)
-      - [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
+
+* [RealtimeKitClient](#module_RealtimeKitClient)
+    * [module.exports](#exp_module_RealtimeKitClient--module.exports) ⏏
+        * [new module.exports(context, controller)](#new_module_RealtimeKitClient--module.exports_new)
+        * _instance_
+            * [.participants](#module_RealtimeKitClient--module.exports+participants)
+            * [.self](#module_RealtimeKitClient--module.exports+self)
+            * [.meta](#module_RealtimeKitClient--module.exports+meta)
+            * [.ai](#module_RealtimeKitClient--module.exports+ai)
+            * [.plugins](#module_RealtimeKitClient--module.exports+plugins)
+            * [.chat](#module_RealtimeKitClient--module.exports+chat)
+            * [.polls](#module_RealtimeKitClient--module.exports+polls)
+            * [.connectedMeetings](#module_RealtimeKitClient--module.exports+connectedMeetings)
+            * [.__internals__](#module_RealtimeKitClient--module.exports+__internals__)
+            * [.join()](#module_RealtimeKitClient--module.exports+join)
+            * [.leave()](#module_RealtimeKitClient--module.exports+leave)
+            * ~~[.joinRoom()](#module_RealtimeKitClient--module.exports+joinRoom)~~
+            * ~~[.leaveRoom([state])](#module_RealtimeKitClient--module.exports+leaveRoom)~~
+        * _static_
+            * [.initMedia([options], [skipAwaits], [cachedUserDetails])](#module_RealtimeKitClient--module.exports.initMedia)
+            * [.init(options)](#module_RealtimeKitClient--module.exports.init)
+            * [.setupContext(peerId, options, meetingId, args)](#module_RealtimeKitClient--module.exports.setupContext)
 
 <a name="exp_module_RealtimeKitClient--module.exports"></a>
 
 ### module.exports ⏏
-
 **Kind**: Exported class  
 <a name="new_module_RealtimeKitClient--module.exports_new"></a>
 
 #### new module.exports(context, controller)
 
-| Param      | Type                    |
-| ---------- | ----------------------- |
-| context    | <code>IContext</code>   |
-| controller | <code>Controller</code> |
+| Param | Type |
+| --- | --- |
+| context | <code>IContext</code> | 
+| controller | <code>Controller</code> | 
 
 <a name="module_RealtimeKitClient--module.exports+participants"></a>
 
 #### module.exports.participants
-
 The `participants` object consists of 4 maps of participants,
 `waitlisted`, `joined`, `active`, `pinned`. The maps are indexed by
 `peerId`s, and the values are the corresponding participant objects.
@@ -61,7 +60,6 @@ The `participants` object consists of 4 maps of participants,
 <a name="module_RealtimeKitClient--module.exports+self"></a>
 
 #### module.exports.self
-
 The `self` object can be used to manipulate audio and video settings,
 and other configurations for the local participant. This exposes methods
 to enable and disable media tracks, share the user's screen, etc.
@@ -70,7 +68,6 @@ to enable and disable media tracks, share the user's screen, etc.
 <a name="module_RealtimeKitClient--module.exports+meta"></a>
 
 #### module.exports.meta
-
 The `room` object stores information about the current meeting, such
 as chat messages, polls, room name, etc.
 
@@ -78,7 +75,6 @@ as chat messages, polls, room name, etc.
 <a name="module_RealtimeKitClient--module.exports+ai"></a>
 
 #### module.exports.ai
-
 The `ai` object is used to interface with AI features.
 You can obtain the live meeting transcript and use other meeting AI
 features such as summary, and agenda using this object.
@@ -87,7 +83,6 @@ features such as summary, and agenda using this object.
 <a name="module_RealtimeKitClient--module.exports+plugins"></a>
 
 #### module.exports.plugins
-
 The `plugins` object stores information about the plugins available in
 the current meeting. It exposes methods to activate and deactivate them.
 
@@ -95,7 +90,6 @@ the current meeting. It exposes methods to activate and deactivate them.
 <a name="module_RealtimeKitClient--module.exports+chat"></a>
 
 #### module.exports.chat
-
 The chat object stores the chat messages that were sent in the meeting.
 This includes text messages, images, and files.
 
@@ -103,7 +97,6 @@ This includes text messages, images, and files.
 <a name="module_RealtimeKitClient--module.exports+polls"></a>
 
 #### module.exports.polls
-
 The polls object stores the polls that were initiated in the meeting.
 It exposes methods to create and vote on polls.
 
@@ -111,7 +104,6 @@ It exposes methods to create and vote on polls.
 <a name="module_RealtimeKitClient--module.exports+connectedMeetings"></a>
 
 #### module.exports.connectedMeetings
-
 The connectedMeetings object stores the connected meetings states.
 It exposes methods to create/read/update/delete methods for connected meetings.
 
@@ -119,17 +111,15 @@ It exposes methods to create/read/update/delete methods for connected meetings.
 <a name="module_RealtimeKitClient--module.exports+__internals__"></a>
 
 #### module.exports.\_\_internals\_\_
-
-The **internals** object exposes the internal tools & utilities such as features and logger
+The __internals__ object exposes the internal tools & utilities such as features and logger
 so that client can utilise the same to build their own feature based UI.
-Logger (**internals**.logger) can be used to send logs to servers
-to inform of issues, if any, proactively.
+Logger (__internals__.logger) can be used to send logs to servers
+	to inform  of issues, if any, proactively.
 
 **Kind**: instance property of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+join"></a>
 
 #### module.exports.join()
-
 The `join()` method can be used to join the meeting.
 A `roomJoined` event is emitted on `self` when the room
 is joined successfully.
@@ -138,70 +128,65 @@ is joined successfully.
 <a name="module_RealtimeKitClient--module.exports+leave"></a>
 
 #### module.exports.leave()
-
 The `leave()` method can be used to leave a meeting.
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+joinRoom"></a>
 
 #### ~~module.exports.joinRoom()~~
-
-**_Deprecated_**
+***Deprecated***
 
 **Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 <a name="module_RealtimeKitClient--module.exports+leaveRoom"></a>
 
 #### ~~module.exports.leaveRoom([state])~~
+***Deprecated***
 
-**_Deprecated_**
-
-**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+**Kind**: instance method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param   | Type                        |
-| ------- | --------------------------- |
-| [state] | <code>LeaveRoomState</code> |
+| Param | Type |
+| --- | --- |
+| [state] | <code>LeaveRoomState</code> | 
 
 <a name="module_RealtimeKitClient--module.exports.initMedia"></a>
 
 #### module.exports.initMedia([options], [skipAwaits], [cachedUserDetails])
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
-
-| Param                 | Type                           | Default            |
-| --------------------- | ------------------------------ | ------------------ |
-| [options]             | <code>Object</code>            |                    |
-| [options.video]       | <code>boolean</code>           |                    |
-| [options.audio]       | <code>boolean</code>           |                    |
-| [options.constraints] | <code>MediaConstraints</code>  |                    |
-| [skipAwaits]          | <code>boolean</code>           | <code>false</code> |
-| [cachedUserDetails]   | <code>CachedUserDetails</code> |                    |
+| Param | Type | Default |
+| --- | --- | --- |
+| [options] | <code>Object</code> |  | 
+| [options.video] | <code>boolean</code> |  | 
+| [options.audio] | <code>boolean</code> |  | 
+| [options.constraints] | <code>MediaConstraints</code> |  | 
+| [skipAwaits] | <code>boolean</code> | <code>false</code> | 
+| [cachedUserDetails] | <code>CachedUserDetails</code> |  | 
 
 <a name="module_RealtimeKitClient--module.exports.init"></a>
 
 #### module.exports.init(options)
-
 The `init` method can be used to instantiate the RealtimeKitClient class.
 This returns an instance of RealtimeKitClient, which can be used to perform
 actions on the meeting.
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-| Param             | Description                                     |
-| ----------------- | ----------------------------------------------- |
-| options           | The options object.                             |
+| Param | Description |
+| --- | --- |
+| options | The options object. |
 | options.authToken | The authorization token received using the API. |
-| options.baseURI   | The base URL of the API.                        |
-| options.defaults  | The default audio and video settings.           |
+| options.baseURI | The base URL of the API. |
+| options.defaults | The default audio and video settings. |
 
 <a name="module_RealtimeKitClient--module.exports.setupContext"></a>
 
 #### module.exports.setupContext(peerId, options, meetingId, args)
+**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)  
 
-**Kind**: static method of [<code>module.exports</code>](#exp_module_RealtimeKitClient--module.exports)
+| Param | Type |
+| --- | --- |
+| peerId | <code>string</code> | 
+| options | <code>RealtimeKitClientOptions</code> | 
+| meetingId | <code>string</code> | 
+| args | <code>any</code> | 
 
-| Param     | Type                                  |
-| --------- | ------------------------------------- |
-| peerId    | <code>string</code>                   |
-| options   | <code>RealtimeKitClientOptions</code> |
-| meetingId | <code>string</code>                   |
-| args      | <code>any</code>                      |
diff --git a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
index d9e3105165b252d..b94947abd5d3245 100644
--- a/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
+++ b/src/content/docs/realtime/realtimekit/legal/3rdparty.mdx
@@ -23,7 +23,6 @@ The following SDKs are collectively referred to as Web SDKs:
 - [`@cloudflare/realtimekit-virtual-background`](https://www.npmjs.com/package/@cloudflare/realtimekit-virtual-background)
 
 Overview of licenses:
-
 - Apache-2.0 (3)
 - ISC (1)
 - MIT (16)
@@ -814,12 +813,10 @@ Apache License
 ## RealtimeKit Android SDKs
 
 The following SDKs are collectively referred to as Android SDKs:
-
 - [`com.cloudflare.realtimekit:core-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-android)
 - [`com.cloudflare.realtimekit:ui-android`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/ui-android)
 
 Overview of licenses:
-
 - Apache-2.0 (24)
 
 ### Apache-2.0 (15 packages)
@@ -1935,13 +1932,11 @@ Apache License
 ## RealtimeKit iOS SDKs
 
 The following SDKs are collectively referred to as iOS SDKs:
-
 - [`RealtimeKit`](https://github.com/dyte-in/RealtimeKitCoreiOS)
 - [`RealtimeKitUI`](https://github.com/dyte-in/RealtimeKitUI)
 - [`RealtimeKit KMM Core`](https://central.sonatype.com/artifact/com.cloudflare.realtimekit/core-iosarm64)
 
 Overview of licenses:
-
 - Apache-2.0 (8)
 
 ### Apache-2.0 (4 packages)
@@ -2817,12 +2812,10 @@ Apache License
 ## RealtimeKit Flutter SDKs
 
 The following SDKs are collectively referred to as Flutter SDKs:
-
 - [`realtimekit_core`](https://pub.dev/packages/realtimekit_core)
 - [`realtimekit_ui`](https://pub.dev/packages/realtimekit_ui)
 
 Overview of licenses:
-
 - Apache-2.0 (1)
 - BSD-3-Clause (55)
 - MIT (10)
@@ -2855,7 +2848,7 @@ Used by:
 [watcher](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2014, the Dart project authors.
+Copyright 2014, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -2899,7 +2892,7 @@ Used by:
 [typed_data](https://github.com/dart-lang/core)
 
 ```
-Copyright 2015, the Dart project authors.
+Copyright 2015, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3174,7 +3167,7 @@ Used by:
 [term_glyph](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2017, the Dart project authors.
+Copyright 2017, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3212,7 +3205,7 @@ Used by:
 [package_config](https://github.com/dart-lang/tools)
 
 ```
-Copyright 2019, the Dart project authors.
+Copyright 2019, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3250,7 +3243,7 @@ Used by:
 [logging](https://github.com/dart-lang/core)
 
 ```
-Copyright 2013, the Dart project authors.
+Copyright 2013, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3288,7 +3281,7 @@ Used by:
 [test_core](https://github.com/dart-lang/test)
 
 ```
-Copyright 2018, the Dart project authors.
+Copyright 2018, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -3758,11 +3751,11 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ```
 
-### BSD-3-Clause (\_fe_analyzer_shared)
+### BSD-3-Clause (_fe_analyzer_shared)
 
 Used by:
 
-[\_fe_analyzer_shared](https://github.com/dart-lang/sdk)
+[_fe_analyzer_shared](https://github.com/dart-lang/sdk)
 
 ```
 Copyright 2019, the Dart project authors.
@@ -3930,7 +3923,7 @@ Used by:
 [web_socket_channel](https://github.com/dart-lang/http)
 
 ```
-Copyright 2016, the Dart project authors.
+Copyright 2016, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4001,7 +3994,7 @@ Used by:
 [web_socket](https://github.com/dart-lang/http)
 
 ```
-Copyright 2024, the Dart project authors.
+Copyright 2024, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4037,7 +4030,7 @@ Used by:
 [frontend_server_client](https://github.com/dart-lang/webdev)
 
 ```
-Copyright 2020, the Dart project authors.
+Copyright 2020, the Dart project authors. 
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are
@@ -4617,12 +4610,10 @@ THE SOFTWARE.
 ## RealtimeKit React Native SDKs
 
 The following SDKs are collectively referred to as React Native SDKs:
-
 - [`@cloudflare/realtimekit-react-native`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native)
 - [`@cloudflare/realtimekit-react-native-ui`](https://www.npmjs.com/package/@cloudflare/realtimekit-react-native-ui)
 
 Overview of licenses:
-
 - Apache-2.0 (3)
 - BSD-2-Clause (10)
 - BSD-3-Clause (3)
@@ -6705,25 +6696,25 @@ The MIT License
 
 Copyright (c) 2013 Dominic Tarr
 
-Permission is hereby granted, free of charge,
-to any person obtaining a copy of this software and
-associated documentation files (the "Software"), to
-deal in the Software without restriction, including
-without limitation the rights to use, copy, modify,
-merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom
-the Software is furnished to do so,
+Permission is hereby granted, free of charge, 
+to any person obtaining a copy of this software and 
+associated documentation files (the "Software"), to 
+deal in the Software without restriction, including 
+without limitation the rights to use, copy, modify, 
+merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom 
+the Software is furnished to do so, 
 subject to the following conditions:
 
-The above copyright notice and this permission notice
+The above copyright notice and this permission notice 
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -7700,25 +7691,25 @@ The MIT License
 
 Copyright (c) 2015 John Hiesey
 
-Permission is hereby granted, free of charge,
-to any person obtaining a copy of this software and
-associated documentation files (the "Software"), to
-deal in the Software without restriction, including
-without limitation the rights to use, copy, modify,
-merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom
-the Software is furnished to do so,
+Permission is hereby granted, free of charge, 
+to any person obtaining a copy of this software and 
+associated documentation files (the "Software"), to 
+deal in the Software without restriction, including 
+without limitation the rights to use, copy, modify, 
+merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom 
+the Software is furnished to do so, 
 subject to the following conditions:
 
-The above copyright notice and this permission notice
+The above copyright notice and this permission notice 
 shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
-ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, 
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 ```
 
@@ -8677,7 +8668,7 @@ Used by:
 ```
 The MIT License (MIT)
 
-Copyright (c) 2015
+Copyright (c) 2015 
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9206,7 +9197,7 @@ Used by:
 [convert-source-map](https://github.com/thlorenz/convert-source-map)
 
 ```
-Copyright 2013 Thorsten Lorenz.
+Copyright 2013 Thorsten Lorenz. 
 All rights reserved.
 
 Permission is hereby granted, free of charge, to any person
@@ -9556,7 +9547,7 @@ exhaustive, and do not form part of our licenses.
      such as asking that all changes be marked or described.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
-     for the public:
+     for the public: 
 	wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
@@ -10890,4 +10881,4 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
index 837b0108533d03f..3a3cdb4f8122af5 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/add-watermark.mdx
@@ -18,15 +18,15 @@ RealtimeKit's watermark feature enables you to include an image as a watermark i
 
 ```json
 {
-	"video_config": {
-		"watermark": {
-			"url": "https://test.io/images/client-logos-6.webp",
-			"position": "left top",
-			"size": {
-				"height": 20,
-				"width": 100
-			}
-		}
-	}
+  "video_config": {
+    "watermark": {
+      "url": "https://test.io/images/client-logos-6.webp",
+      "position": "left top",
+      "size": {
+        "height": 20,
+        "width": 100
+      }
+    }
+  }
 }
 ```
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
index f6ff1aa7a6b2ed3..e79a05b4153957e 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/configure-codecs.mdx
@@ -26,9 +26,9 @@ example:
 
 ```json
 {
-	"video_config": {
-		"codec": "H264"
-	}
+  "video_config": {
+    "codec": "H264"
+  }
 }
 ```
 
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
index 5fa72f9105b9299..a3e0e0c4865d6d0 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/index.mdx
@@ -19,7 +19,7 @@ Visit the following pages to learn more about recording meetings:
 
 RealtimeKit can record the audio and video of multiple users in a meeting, as well as interactions with RealtimeKit plugins, in a single file using composite recording mode. RealtimeKit can also record separate participant audio tracks using [track recording](/realtime/realtimekit/recording-guide/track-recording/).
 
-## How does RealtimeKit recording work?
+## How does composite recording work
 
 Composite recordings are powered by anonymous virtual bot users who join your
 meeting, record it, and then upload it to RealtimeKit's Cloudflare R2 bucket. For video files,
diff --git a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
index 81744c2746450cb..67da5cc041affca 100644
--- a/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
+++ b/src/content/docs/realtime/realtimekit/recording-guide/monitor-status.mdx
@@ -12,13 +12,13 @@ products:
 
 The recording of a meeting can have the following states:
 
-| Name      | Description                                                                                                                                                                                                                                                |
-| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                         |
-| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                             |
+| Name      | Description                                                                                                                                                                                                                                         |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| INVOKED   | Our backend servers have received the recording request, and the master is looking for a ready worker to assign the recording job.                                                                                                                  |
+| RECORDING | The meeting is currently being recorded by a worker; note that this will also hold true if the meeting is being live streamed.                                                                                                                      |
 | UPLOADING | The recording has been stopped and the file is being uploaded to the cloud storage. If you have not specified storage details, then the files will be uploaded only to RealtimeKit's server. Any RTMP and livestreaming link will also stop at this stage. |
-| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                            |
-| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                           |
+| UPLOADED  | The recording file upload is complete and the status webhook is also triggered.                                                                                                                                                                     |
+| ERRORED   | There was an irrecoverable error while recording the meeting and the file will not be available.                                                                                                                                                    |
 
 ## Fetching the state
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
index 740b8984d91accc..a530264178e2cd7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
index be354415f804c68..9022f7eef15914a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-ai-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,5 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-toggle [meeting]="meeting" size="md" variant="button"> </rtk-ai-toggle>
+<rtk-ai-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
+</rtk-ai-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
index 05bb2a1ea2666d2..36207327073578c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai-transcriptions.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-ai-transcriptions component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,6 +26,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai-transcriptions [initialTranscriptions]="[]" [meeting]="meeting">
+<rtk-ai-transcriptions
+ [initialTranscriptions]="[]"
+ [meeting]="meeting">
 </rtk-ai-transcriptions>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
index 8d64f23b0df3f0b..936d95be25b08c0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ai.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ai component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-ai [meeting]="meeting" size="md" [view]="aiview"> </rtk-ai>
+<rtk-ai
+ [meeting]="meeting"
+ size="md"
+ [view]="aiview">
+</rtk-ai>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
index 74fb58b92b23308..690fb5c0632fc17 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-grid.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-grid component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-grid
-	[config]="defaultUiConfig"
-	[hideSelf]="true"
-	[meeting]="meeting"
->
+ [config]="defaultUiConfig"
+ [hideSelf]="true"
+ [meeting]="meeting">
 </rtk-audio-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
index 9fa0eff7807d9be..dbb17aafd24724b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-tile.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-tile component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-audio-tile
-	[config]="defaultUiConfig"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [config]="defaultUiConfig"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-audio-tile>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
index cc99527e230b702..1622d030b9255cf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-audio-visualizer.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-audio-visualizer component (Angular Library)
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ Commonly used inside `rtk-name-tag`.
 ```html
 <!-- component.html -->
 <rtk-audio-visualizer
-	[hideMuted]="true"
-	[isScreenShare]="true"
-	[participant]="participant"
->
+ [hideMuted]="true"
+ [isScreenShare]="true"
+ [participant]="participant">
 </rtk-audio-visualizer>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
index 6bd382f5ba1c7b1..ff5a9ab19b357c0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-avatar.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-avatar component (Angular Library)
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ Avatar component which renders a participant's image or their initials.
 
 ```html
 <!-- component.html -->
-<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
+<rtk-avatar
+ participant="example"
+ size="md"
+ variant="circular">
+</rtk-avatar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
index 942b66a929beefc..b310482b33cdfe8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-manager.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-breakout-room-manager component (Angular Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-breakout-room-manager
-	[allowDelete]="true"
-	[assigningParticipants]="true"
-	[defaultExpanded]="true"
->
+ [allowDelete]="true"
+ [assigningParticipants]="true"
+ [defaultExpanded]="true">
 </rtk-breakout-room-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
index 8d2a38f304f03fd..2d1f1e58d56e53f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-room-participants.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-breakout-room-participants component (Angular
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-breakout-room-participants
-	[meeting]="meeting"
-	participantIds="example"
-	selectedParticipantIds="example"
->
+ [meeting]="meeting"
+ participantIds="example"
+ selectedParticipantIds="example">
 </rtk-breakout-room-participants>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
index 6b60a42d4f64b07..bbe7a129471cfef 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-manager.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-breakout-rooms-manager component (Angular Lib
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-breakout-rooms-manager [meeting]="meeting"> </rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager
+ [meeting]="meeting">
+</rtk-breakout-rooms-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
index e769d064ce27906..dab4a3a9ced6758 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-breakout-rooms-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-breakout-rooms-toggle component (Angular Libr
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ You need to pass the `meeting` object to it.
 ```html
 <!-- component.html -->
 <rtk-breakout-rooms-toggle
-	[iconPack]="defaultIconPack"
-	[meeting]="meeting"
-	size="md"
->
+ [iconPack]="defaultIconPack"
+ [meeting]="meeting"
+ size="md">
 </rtk-breakout-rooms-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
index a9399e40c4b7a2c..706f133335069c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-broadcast-message-modal.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-broadcast-message-modal component (Angular Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-broadcast-message-modal [meeting]="meeting"> </rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal
+ [meeting]="meeting">
+</rtk-broadcast-message-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
index 49d3ca7ffe6a357..ed08f480b320ab1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-button.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-button component (Angular Library)
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ A button that follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-button [disabled]="true" [kind]="buttonkind" [reverse]="true">
+<rtk-button
+ [disabled]="true"
+ [kind]="buttonkind"
+ [reverse]="true">
 </rtk-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
index 92270e3c97fe0e1..755404225238040 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-camera-selector component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -41,9 +39,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-camera-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-camera-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
index db38dc91c0aac70..00b9d2b1e4bdd06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-camera-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-camera-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles your camera.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ A button which toggles your camera.
 
 ```html
 <!-- component.html -->
-<rtk-camera-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-camera-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-camera-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
index 5dc17611c79b114..66da419d1dea460 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-caption-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-caption-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-caption-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-caption-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-caption-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
index b6ff46e4d62c8d9..ee2887a10f7e46a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat-composer-ui component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-composer-ui
-	[canSendFiles]="true"
-	[canSendTextMessage]="true"
-	size="md"
->
+ [canSendFiles]="true"
+ [canSendTextMessage]="true"
+ size="md">
 </rtk-chat-composer-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
index 3b98703d1ac78cb..407b10b43a4197f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-composer-view.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-chat-composer-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,9 +37,9 @@ A component which renders a chat composer
 ```html
 <!-- component.html -->
 <rtk-chat-composer-view
-	[canSendFiles]="true"
-	[canSendTextMessage]="true"
-	inputTextPlaceholder="example"
->
+ [canSendFiles]="true"
+ [canSendTextMessage]="true"
+ inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
index 18489ada36fdf99..400bbe3d46a8aaa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-header.mdx
@@ -5,10 +5,9 @@ description: API reference for rtk-chat-header component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
@@ -18,3 +17,4 @@ _No properties available._
 <!-- component.html -->
 <rtk-chat-header></rtk-chat-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
index 98cb5beca666769..de48d16b7b4d731 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-message.mdx
@@ -5,30 +5,29 @@ description: API reference for rtk-chat-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -43,6 +42,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-message [alignRight]="true" [canDelete]="true" [canEdit]="true">
+<rtk-chat-message
+ [alignRight]="true"
+ [canDelete]="true"
+ [canEdit]="true">
 </rtk-chat-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
index b42f6dc5f8f79eb..ce18aa44fb427c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui-paginated.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-chat-messages-ui-paginated component (Angular
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui-paginated
-	[meeting]="meeting"
-	[privateChatRecipient]="participant | null"
-	size="md"
->
+ [meeting]="meeting"
+ [privateChatRecipient]="participant | null"
+ size="md">
 </rtk-chat-messages-ui-paginated>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
index 5241b26b67f1ef7..30863c471104539 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-messages-ui.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-chat-messages-ui component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-messages-ui
-	[canPinMessages]="true"
-	[messages]="[]"
-	selectedGroup="example"
->
+ [canPinMessages]="true"
+ [messages]="[]"
+ selectedGroup="example">
 </rtk-chat-messages-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
index 674604a158dad2c..c523cd074c0f8b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-search-results.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-search-results component (Angular Librar
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-search-results
-	channelId="example"
-	[meeting]="meeting"
-	query="example"
->
+ channelId="example"
+ [meeting]="meeting"
+ query="example">
 </rtk-chat-search-results>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
index 784cf425f1ad9a0..0ab9edbe1fcae7c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector-ui.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-chat-selector-ui component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-chat-selector-ui
-	[groups]="[]"
-	selectedGroupId="example"
-	selfUserId="example"
->
+ [groups]="[]"
+ selectedGroupId="example"
+ selfUserId="example">
 </rtk-chat-selector-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
index ef6a41c79405f4a..e7e5178d7c5072b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-selector.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-selector component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-chat-selector [meeting]="meeting" size="md"> </rtk-chat-selector>
+<rtk-chat-selector
+ [meeting]="meeting"
+ size="md">
+</rtk-chat-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
index 942cba2a0f25e3c..1973396bb8401c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat-toggle.mdx
@@ -5,28 +5,23 @@ description: API reference for rtk-chat-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of chat.
-You need to pass the `meeting` object to it to see the unread messages count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "chat";
-}
-```
+ You need to pass the `meeting` object to it to see the unread messages count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'chat' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -41,6 +36,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-chat-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-chat-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-chat-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
index b968cfe975421fa..12504ff17633de3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-chat.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat component (Angular Library)
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 
 ```html
 <!-- component.html -->
-<rtk-chat [meeting]="meeting" size="md"> </rtk-chat>
+<rtk-chat
+ [meeting]="meeting"
+ size="md">
+</rtk-chat>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
index eea055224c112f4..fe930adaf1f7baf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-clock.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-clock component (Angular Library)
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ Shows the time elapsed in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-clock [meeting]="meeting" size="md"> </rtk-clock>
+<rtk-clock
+ [meeting]="meeting"
+ size="md">
+</rtk-clock>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
index cd3a2dc87b17a9f..9af1775bf822f6f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-confirmation-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-confirmation-modal component (Angular Library
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,8 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-confirmation-modal [meeting]="meeting"> </rtk-confirmation-modal>
+<rtk-confirmation-modal
+ [meeting]="meeting">
+</rtk-confirmation-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
index 85344ab73bbbe9e..52a23c6c3a7c14b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar-button.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-controlbar-button component (Angular Library)
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ A skeleton component used for composing custom controlbar buttons.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar-button [brandIcon]="true" [disabled]="true" icon="example">
+<rtk-controlbar-button
+ [brandIcon]="true"
+ [disabled]="true"
+ icon="example">
 </rtk-controlbar-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
index f06437464f138a2..e7d739a49130cb7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-controlbar.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-controlbar component (Angular Library)
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,6 +33,10 @@ Controlbar component provides you with various designs as variants.
 
 ```html
 <!-- component.html -->
-<rtk-controlbar [disableRender]="true" [meeting]="meeting" size="md">
+<rtk-controlbar
+ [disableRender]="true"
+ [meeting]="meeting"
+ size="md">
 </rtk-controlbar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
index 61d79e5a7230d1b..1dcbd9f1997daff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-counter.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-counter component (Angular Library)
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A number picker with increment and decrement buttons.
 
 ```html
 <!-- component.html -->
-<rtk-counter minValue="42" size="md" value="42"> </rtk-counter>
+<rtk-counter
+ minValue="42"
+ size="md"
+ value="42">
+</rtk-counter>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
index b878475ad72fa65..958771b9756d2be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-audio.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-audio component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-audio [meeting]="meeting" size="md"> </rtk-debugger-audio>
+<rtk-debugger-audio
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
index c78c0ff33fa40dd..d6002b9a6aecd84 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-screenshare.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-screenshare component (Angular Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,6 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-screenshare [meeting]="meeting" size="md">
+<rtk-debugger-screenshare
+ [meeting]="meeting"
+ size="md">
 </rtk-debugger-screenshare>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
index ea1d6d90d2b938e..60e7d5bb6289f9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-system.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-system component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-system [meeting]="meeting" size="md"> </rtk-debugger-system>
+<rtk-debugger-system
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-system>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
index 3e69cb73fef0b73..6c7e30bd9fcf7f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-debugger-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-debugger-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-debugger-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
index 2a84fafef9eb27b..d5210d91dc9db4d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger-video.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-video component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-debugger-video [meeting]="meeting" size="md"> </rtk-debugger-video>
+<rtk-debugger-video
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger-video>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
index f73efac1fa88dbf..40b74b2e1ab8c69 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-debugger.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-debugger component (Angular Library)
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,9 @@ A troubleshooting component to identify and fix any issues in the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-debugger [meeting]="meeting" size="md"> </rtk-debugger>
+<rtk-debugger
+ [meeting]="meeting"
+ size="md">
+</rtk-debugger>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
index db0a49fdc7627bc..c1de127979df06a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog-manager.mdx
@@ -5,26 +5,24 @@ description: API reference for rtk-dialog-manager component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -39,5 +37,9 @@ A component which handles all dialog elements in a component such as:
 
 ```html
 <!-- component.html -->
-<rtk-dialog-manager [meeting]="meeting" size="md"> </rtk-dialog-manager>
+<rtk-dialog-manager
+ [meeting]="meeting"
+ size="md">
+</rtk-dialog-manager>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
index 76e69151c16a283..9635ed56702713b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-dialog.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-dialog component (Angular Library)
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ A dialog component.
 ```html
 <!-- component.html -->
 <rtk-dialog
-	[disableEscapeKey]="true"
-	[hideCloseButton]="true"
-	[meeting]="meeting"
->
+ [disableEscapeKey]="true"
+ [hideCloseButton]="true"
+ [meeting]="meeting">
 </rtk-dialog>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
index 41ba93a5da182cd..a8934fc38c1e469 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker-button.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-emoji-picker-button component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker-button [isActive]="true"> </rtk-emoji-picker-button>
+<rtk-emoji-picker-button
+ [isActive]="true">
+</rtk-emoji-picker-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
index 01b94d697105b34..4247ddbd5c1ce10 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-emoji-picker.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-emoji-picker component (Angular Library)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A very simple emoji picker component.
 
 ```html
 <!-- component.html -->
-<rtk-emoji-picker [focusWhenOpened]="true"> </rtk-emoji-picker>
+<rtk-emoji-picker
+ [focusWhenOpened]="true">
+</rtk-emoji-picker>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
index b2ad7d8f8e7eea2..b354fa28a6845bf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ended-screen.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-ended-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ A screen which shows a meeting has ended.
 
 ```html
 <!-- component.html -->
-<rtk-ended-screen [meeting]="meeting" size="md"> </rtk-ended-screen>
+<rtk-ended-screen
+ [meeting]="meeting"
+ size="md">
+</rtk-ended-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
index 57ffa8f9039d89a..8344ce746896053 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-dropzone.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-file-dropzone component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-file-dropzone [hostEl]="htmlelement"> </rtk-file-dropzone>
+<rtk-file-dropzone
+ [hostEl]="htmlelement">
+</rtk-file-dropzone>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
index 858399c5abccaed..48e4cca9eee6790 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message-view.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-file-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ A component which renders a file message.
 
 ```html
 <!-- component.html -->
-<rtk-file-message-view name="example" size="42" url="example">
+<rtk-file-message-view
+ name="example"
+ size="42"
+ url="example">
 </rtk-file-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
index d32dd9edc995033..a19ab17f5b413c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-file-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders a file message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-file-message [isContinued]="true" [message]="filemessage" [now]="date">
+<rtk-file-message
+ [isContinued]="true"
+ [message]="filemessage"
+ [now]="date">
 </rtk-file-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
index 2470555e83eff13..4bda6955ac1042e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-file-picker-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-file-picker-button component (Angular Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-file-picker-button
-	filter="example"
-	[icon]="defaultIconPack"
-	label="example"
->
+ filter="example"
+ [icon]="defaultIconPack"
+ label="example">
 </rtk-file-picker-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
index 04544ab3ecc21c2..f1d002421e860d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-fullscreen-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-fullscreen-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles full screen mode for any
-existing `rtk-meeting` component in the DOM.
+ existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                  |
-| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
-| `size`          | `Size`              | ✅       | -                 | Size                         |
-| `states`        | `States`            | ✅       | -                 | States object                |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
-| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
-| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ existing `rtk-meeting` component in the DOM.
 
 ```html
 <!-- component.html -->
-<rtk-fullscreen-toggle size="md" [targetElement]="htmlelement" variant="button">
+<rtk-fullscreen-toggle
+ size="md"
+ [targetElement]="htmlelement"
+ variant="button">
 </rtk-fullscreen-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
index 04a546d6b3f89a5..535638be929e69a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid-pagination.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-grid-pagination component (Angular Library)
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ of active participants list. This is reflected in the `rtk-grid` component.
 ```html
 <!-- component.html -->
 <rtk-grid-pagination
-	[meeting]="meeting"
-	size="md"
-	[variant]="gridpaginationvariants"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="gridpaginationvariants">
 </rtk-grid-pagination>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
index 0c97b4b23ee5ea2..bd36da17a99fc2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-grid.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-grid component (Angular Library)
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,5 +36,10 @@ The main grid component which abstracts all the grid handling logic and renders
 
 ```html
 <!-- component.html -->
-<rtk-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-grid>
+<rtk-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
+</rtk-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
index c09018ff727582b..6308160dae44850 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-header.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-header component (Angular Library)
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,5 +33,10 @@ A component that houses all the header components.
 
 ```html
 <!-- component.html -->
-<rtk-header [disableRender]="true" [meeting]="meeting" size="md"> </rtk-header>
+<rtk-header
+ [disableRender]="true"
+ [meeting]="meeting"
+ size="md">
+</rtk-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
index fdb32d3739e666a..b78675a57bf3f47 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-icon.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-icon component (Angular Library)
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
@@ -29,5 +28,10 @@ An icon component which accepts an svg string and renders it.
 
 ```html
 <!-- component.html -->
-<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
+<rtk-icon
+ icon="example"
+ size="md"
+ variant="primary">
+</rtk-icon>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
index a5a0b562a10c71e..98bd3fd010f365a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-idle-screen.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-idle-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ i.e; when you are waiting for data about the meeting, specifically the `meeting`
 
 ```html
 <!-- component.html -->
-<rtk-idle-screen [meeting]="meeting"> </rtk-idle-screen>
+<rtk-idle-screen
+ [meeting]="meeting">
+</rtk-idle-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
index b6624557f5b530d..ae4305bd0b859b1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-image-message-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A component which renders an image message.
 
 ```html
 <!-- component.html -->
-<rtk-image-message-view url="example"> </rtk-image-message-view>
+<rtk-image-message-view
+ url="example">
+</rtk-image-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
index 57f711994dc6ea4..e61a9e43a995966 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-image-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders an image message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-message [isContinued]="true" [message]="imagemessage" [now]="date">
+<rtk-image-message
+ [isContinued]="true"
+ [message]="imagemessage"
+ [now]="date">
 </rtk-image-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
index a5c26ec0490046f..ce55f03e3a1012b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-image-viewer.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-image-viewer component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows an image sent via chat.
 
 ```html
 <!-- component.html -->
-<rtk-image-viewer [image]="imagemessage" size="md"> </rtk-image-viewer>
+<rtk-image-viewer
+ [image]="imagemessage"
+ size="md">
+</rtk-image-viewer>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
index 4a0ff811c795716..87a5a453715b10c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-information-tooltip.mdx
@@ -5,12 +5,11 @@ description: API reference for rtk-information-tooltip component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
@@ -25,6 +24,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-information-tooltip [iconPack]="defaultIconPack">
+<rtk-information-tooltip
+ [iconPack]="defaultIconPack">
 </rtk-information-tooltip>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
index 54215fd0fe361ad..877a7a5fef233c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-join-stage.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-join-stage component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-join-stage [dataConfig]="modaldataconfig" [meeting]="meeting" size="md">
+<rtk-join-stage
+ [dataConfig]="modaldataconfig"
+ [meeting]="meeting"
+ size="md">
 </rtk-join-stage>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
index 57d4746414928cd..28820eb49fe7d0e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-button.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-leave-button component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description |
-| ---------- | ------------------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size`              | ✅       | -                 | Size        |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A button which toggles visilibility of the leave confirmation dialog.
 
 ```html
 <!-- component.html -->
-<rtk-leave-button size="md" variant="button"> </rtk-leave-button>
+<rtk-leave-button
+ size="md"
+ variant="button">
+</rtk-leave-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
index 97cb75f991a2535..46d14fe211c640f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-leave-meeting.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-leave-meeting component (Angular Library)
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ end meeting for all, if you have the permission.
 
 ```html
 <!-- component.html -->
-<rtk-leave-meeting [meeting]="meeting"> </rtk-leave-meeting>
+<rtk-leave-meeting
+ [meeting]="meeting">
+</rtk-leave-meeting>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
index 5822982df0f5a65..04858c6a723e9f5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-indicator component (Angular Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-indicator [meeting]="meeting" size="md">
+<rtk-livestream-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-livestream-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
index 4aedae8a958db06..35b411555cd3561 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-player.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-player component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-player [meeting]="meeting" size="md"> </rtk-livestream-player>
+<rtk-livestream-player
+ [meeting]="meeting"
+ size="md">
+</rtk-livestream-player>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
index 43e52a53ecca76d..b965a5d73aa5a9c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-livestream-toggle.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-livestream-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -29,6 +28,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-livestream-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-livestream-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-livestream-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
index 8a910a96dda8544..c7422b474f26bde 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-logo.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-logo component (Angular Library)
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 
 ```html
 <!-- component.html -->
-<rtk-logo logoUrl="example" [meeting]="meeting"> </rtk-logo>
+<rtk-logo
+ logoUrl="example"
+ [meeting]="meeting">
+</rtk-logo>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
index b5b816456292b1a..a7f872c4122307b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-markdown-view.mdx
@@ -5,13 +5,12 @@ description: API reference for rtk-markdown-view component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
@@ -26,5 +25,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-markdown-view maxLength="42" text="example"> </rtk-markdown-view>
+<rtk-markdown-view
+ maxLength="42"
+ text="example">
+</rtk-markdown-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
index 6adbeb63b44a99a..31cbdb86d3736f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting-title.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-meeting-title component (Angular Library)
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ Displays the title of the meeting.
 
 ```html
 <!-- component.html -->
-<rtk-meeting-title [meeting]="meeting"> </rtk-meeting-title>
+<rtk-meeting-title
+ [meeting]="meeting">
+</rtk-meeting-title>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
index fb1306311adea67..f1727781860d6f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-meeting.mdx
@@ -5,28 +5,27 @@ description: API reference for rtk-meeting component (Angular Library)
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -42,9 +41,9 @@ dialogs and other smaller bits of managing the application.
 ```html
 <!-- component.html -->
 <rtk-meeting
-	[applyDesignSystem]="true"
-	[config]="defaultUiConfig"
-	[gridLayout]="gridlayout1"
->
+ [applyDesignSystem]="true"
+ [config]="defaultUiConfig"
+ [gridLayout]="gridlayout1">
 </rtk-meeting>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
index ec230b806744c2e..b640c6b002c812a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-item.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-menu-item component (Angular Library)
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,6 +29,9 @@ A menu item component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-item [menuVariant]="'primary' | 'secondary'" size="md">
+<rtk-menu-item
+ [menuVariant]="'primary' | 'secondary'"
+ size="md">
 </rtk-menu-item>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
index cc93e411c5ade5a..7637b0961658634 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-menu-list component (Angular Library)
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,8 @@ A menu list component.
 
 ```html
 <!-- component.html -->
-<rtk-menu-list [menuVariant]="'primary' | 'secondary'"> </rtk-menu-list>
+<rtk-menu-list
+ [menuVariant]="'primary' | 'secondary'">
+</rtk-menu-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
index 75bea868f269ae2..166ba3bed89a7cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-menu.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-menu component (Angular Library)
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A menu component.
 
 ```html
 <!-- component.html -->
-<rtk-menu offset="42" [placement]="placement" size="md"> </rtk-menu>
+<rtk-menu
+ offset="42"
+ [placement]="placement"
+ size="md">
+</rtk-menu>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
index c6e6a410829ecf7..3a2c6f64fdbcb64 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-list-view.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-message-list-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders list of messages.
 
 ## Properties
 
-| Property            | Type                                | Required | Default           | Description                                                                   |
-| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
-| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
-| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
-| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
-| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
-| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
-| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
+| `messages` | `Message[]` | ✅ | - | Messages to render |
+| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
+| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ A component which renders list of messages.
 ```html
 <!-- component.html -->
 <rtk-message-list-view
-	estimateItemSize="42"
-	[loadMore]="(lastmessage: message)"
-	[messages]="[]"
->
+ estimateItemSize="42"
+ [loadMore]="(lastmessage: message)"
+ [messages]="[]">
 </rtk-message-list-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
index cf2cd2949c924ba..b9ab493f273c95c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-message-view.mdx
@@ -5,25 +5,24 @@ description: API reference for rtk-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
@@ -38,6 +37,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-message-view [actions]="[]" authorName="example" avatarUrl="example">
+<rtk-message-view
+ [actions]="[]"
+ authorName="example"
+ avatarUrl="example">
 </rtk-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
index 2f9fa6aaf5f2e0e..a99b4422c32892b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mic-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-mic-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles your microphone.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ A button which toggles your microphone.
 
 ```html
 <!-- component.html -->
-<rtk-mic-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-mic-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-mic-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
index 1cd58cb2ab66302..e387ad7b10c0480 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-microphone-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-microphone-selector component (Angular Librar
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -41,9 +39,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-microphone-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-microphone-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
index bc1d583c35d077b..fce5f3ee1150759 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mixed-grid.mdx
@@ -5,27 +5,26 @@ description: API reference for rtk-mixed-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +39,10 @@ A grid component which handles screenshares, plugins and participants.
 
 ```html
 <!-- component.html -->
-<rtk-mixed-grid aspectRatio="example" gap="42" gridSize="md"> </rtk-mixed-grid>
+<rtk-mixed-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
+</rtk-mixed-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
index b6d4f9cd6a2fb91..da82abf95847f76 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-more-toggle.mdx
@@ -5,24 +5,20 @@ description: API reference for rtk-more-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,5 +33,8 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-more-toggle size="md"> </rtk-more-toggle>
+<rtk-more-toggle
+ size="md">
+</rtk-more-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
index e1a63a750b62c5d..267acdbbab6197c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-mute-all-button component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -29,6 +28,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-button [meeting]="meeting" size="md" variant="button">
+<rtk-mute-all-button
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-mute-all-button>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
index 406a2e94c9b8462..fd686e57c8f8e71 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-mute-all-confirmation.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-mute-all-confirmation component (Angular Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-mute-all-confirmation [meeting]="meeting"> </rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation
+ [meeting]="meeting">
+</rtk-mute-all-confirmation>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
index 4f21452d80b34f9..ab2fdfe0ef135b8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-name-tag.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-name-tag component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
@@ -34,9 +33,9 @@ A component which shows a participant's name.
 ```html
 <!-- component.html -->
 <rtk-name-tag
-	[isScreenShare]="true"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [isScreenShare]="true"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-name-tag>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
index 2776b79be409e22..7a1feeae085082d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-network-indicator.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-network-indicator component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-network-indicator
-	[isScreenShare]="true"
-	[meeting]="meeting"
-	[participant]="participant"
->
+ [isScreenShare]="true"
+ [meeting]="meeting"
+ [participant]="participant">
 </rtk-network-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
index 3125a0458248d60..4bb7b34755028e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notification.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-notification component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ You need to remove the element after you receive the
 
 ```html
 <!-- component.html -->
-<rtk-notification [notification]="notification" [paused]="true" size="md">
+<rtk-notification
+ [notification]="notification"
+ [paused]="true"
+ size="md">
 </rtk-notification>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
index 29874314310420f..7d3957e28575b5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-notifications.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-notifications component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -34,5 +33,9 @@ There are also certain limits which you can set as well.
 
 ```html
 <!-- component.html -->
-<rtk-notifications [meeting]="meeting" size="md"> </rtk-notifications>
+<rtk-notifications
+ [meeting]="meeting"
+ size="md">
+</rtk-notifications>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
index f7b0a744c973685..da6b60ff9959d29 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-overlay-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-overlay-modal component (Angular Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,8 @@ A confirmation modal.
 
 ```html
 <!-- component.html -->
-<rtk-overlay-modal [meeting]="meeting"> </rtk-overlay-modal>
+<rtk-overlay-modal
+ [meeting]="meeting">
+</rtk-overlay-modal>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
index 3a22d1b7e3c7e6a..a37ab406bfe13c8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-paginated-list.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-paginated-list component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-paginated-list
-	[autoScroll]="true"
-	[createNodes]="[]"
-	emptyListLabel="example"
->
+ [autoScroll]="true"
+ [createNodes]="[]"
+ emptyListLabel="example">
 </rtk-paginated-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
index dc709547d180829..a77302d526005b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participant-count component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-participant-count [meeting]="meeting" size="md"> </rtk-participant-count>
+<rtk-participant-count
+ [meeting]="meeting"
+ size="md">
+</rtk-participant-count>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
index 354d7029075e454..fbdb48390bc0073 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-setup.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-participant-setup component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,14 +33,14 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participant-setup
-	[isPreview]="true"
-	[nameTagPosition]="| 'bottom-left'
+ [isPreview]="true"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
     | 'top-center'"
-	[participant]="participant"
->
+ [participant]="participant">
 </rtk-participant-setup>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
index e4417402b7a4053..a87d31044667f2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant-tile.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-participant-tile component (Angular Library)
 products:
   - realtime
 ---
-
 A component which plays a participants video and allows for placement
-of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -38,14 +37,14 @@ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component
 ```html
 <!-- component.html -->
 <rtk-participant-tile
-	[isPreview]="true"
-	[meeting]="meeting"
-	[nameTagPosition]="| 'bottom-left'
+ [isPreview]="true"
+ [meeting]="meeting"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'"
->
+    | 'top-center'">
 </rtk-participant-tile>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
index 2cb75bb1541d4dc..1dda330a33b1b70 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participant.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-participant component (Angular Library)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ You can perform privileged actions on the participant too.
 ```html
 <!-- component.html -->
 <rtk-participant
-	[meeting]="meeting"
-	[participant]="participant"
-	[view]="participantviewmode"
->
+ [meeting]="meeting"
+ [participant]="participant"
+ [view]="participantviewmode">
 </rtk-participant>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
index f35effb4020a5a4..8d1dd8043548405 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-audio.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-audio component (Angular Library
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,8 +30,8 @@ A component which plays all the audio from participants and screenshares.
 ```html
 <!-- component.html -->
 <rtk-participants-audio
-	[meeting]="meeting"
-	[preloadedAudioElem]="htmlaudioelement"
->
+ [meeting]="meeting"
+ [preloadedAudioElem]="htmlaudioelement">
 </rtk-participants-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
index a0ad0b85a8677ae..805eb1630f5565d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-list.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-participants-stage-list component (Angular Li
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -37,9 +36,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-participants-stage-list
-	[hideHeader]="true"
-	[meeting]="meeting"
-	search="example"
->
+ [hideHeader]="true"
+ [meeting]="meeting"
+ search="example">
 </rtk-participants-stage-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
index 883999ff9c3ed7f..0963dbb1699ef78 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-stage-queue.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-stage-queue component (Angular L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-stage-queue
-	[meeting]="meeting"
-	size="md"
-	[view]="participantsviewmode"
->
+ [meeting]="meeting"
+ size="md"
+ [view]="participantsviewmode">
 </rtk-participants-stage-queue>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
index bb5751a926de3b4..dea0f244da4a0d5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-toggle.mdx
@@ -5,27 +5,22 @@ description: API reference for rtk-participants-toggle component (Angular Librar
 products:
   - realtime
 ---
-
 A button which toggles visibility of participants.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "participants";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'participants' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -40,6 +35,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-participants-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-participants-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-participants-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
index db2b020c8b88ab8..4ae0ae15cc28d5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-viewer-list.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-participants-viewer-list component (Angular L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-viewer-list
-	[hideHeader]="true"
-	[meeting]="meeting"
-	search="example"
->
+ [hideHeader]="true"
+ [meeting]="meeting"
+ search="example">
 </rtk-participants-viewer-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
index f31d8a204b73fd3..073a3e467d62514 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants-waiting-list.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-waiting-list component (Angular
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -31,9 +30,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-participants-waiting-list
-	[meeting]="meeting"
-	size="md"
-	[view]="participantsviewmode"
->
+ [meeting]="meeting"
+ size="md"
+ [view]="participantsviewmode">
 </rtk-participants-waiting-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
index b771206de02ce49..f1984d1798d8879 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-participants.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-participants component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,9 +34,9 @@ run privileged actions on each participant according to your permissions.
 ```html
 <!-- component.html -->
 <rtk-participants
-	[defaultParticipantsTabId]="participantstabid"
-	[meeting]="meeting"
-	size="md"
->
+ [defaultParticipantsTabId]="participantstabid"
+ [meeting]="meeting"
+ size="md">
 </rtk-participants>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
index 683752123d4ac43..dec4a8e63bdaed2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-permissions-message.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-permissions-message component (Angular Librar
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,8 @@ information.
 
 ```html
 <!-- component.html -->
-<rtk-permissions-message [meeting]="meeting"> </rtk-permissions-message>
+<rtk-permissions-message
+ [meeting]="meeting">
+</rtk-permissions-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
index 930b8fea7a6f96a..94aad79b50a76a9 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pinned-message-selector.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-pinned-message-selector component (Angular Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,5 +26,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pinned-message-selector [meeting]="meeting"> </rtk-pinned-message-selector>
+<rtk-pinned-message-selector
+ [meeting]="meeting">
+</rtk-pinned-message-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
index 3b85d1e48dc9a96..ff56f4f7c8fc58c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-pip-toggle.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-pip-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,6 +30,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-pip-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-pip-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-pip-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
index 8bc1fdc55db3407..2adc29e0fe4d37f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugin-main.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-plugin-main component (Angular Library)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which loads a plugin.
 
 ```html
 <!-- component.html -->
-<rtk-plugin-main [meeting]="meeting" [plugin]="rtkplugin"> </rtk-plugin-main>
+<rtk-plugin-main
+ [meeting]="meeting"
+ [plugin]="rtkplugin">
+</rtk-plugin-main>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
index 78da2d41fbb440d..1e55dfd168ff802 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins-toggle.mdx
@@ -5,27 +5,22 @@ description: API reference for rtk-plugins-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of plugins.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "plugins";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'plugins' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -40,6 +35,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-plugins-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-plugins-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-plugins-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
index 916242388b0671a..ef10daccef93a00 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-plugins.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-plugins component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ and ability to enable or disable plugins.
 
 ```html
 <!-- component.html -->
-<rtk-plugins [meeting]="meeting" size="md"> </rtk-plugins>
+<rtk-plugins
+ [meeting]="meeting"
+ size="md">
+</rtk-plugins>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
index 92e52060d4aa885..ed3e4b10df95868 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll-form.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-poll-form component (Angular Library)
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,9 @@ A component that lets you create a poll.
 
 ```html
 <!-- component.html -->
-<rtk-poll-form [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-poll-form>
+<rtk-poll-form
+ [iconPack]="defaultIconPack"
+ [t]="rtki18n">
+</rtk-poll-form>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
index ef928546a835336..9c50bc3106f4e74 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-poll.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-poll component (Angular Library)
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ Shows a poll where a user can vote.
 
 ```html
 <!-- component.html -->
-<rtk-poll [permissions]="rtkpermissionspreset" [poll]="poll" self="example">
+<rtk-poll
+ [permissions]="rtkpermissionspreset"
+ [poll]="poll"
+ self="example">
 </rtk-poll>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
index 4bc3fdff2d81dca..8ee05f66d6d0c1e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls-toggle.mdx
@@ -5,28 +5,23 @@ description: API reference for rtk-polls-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of polls.
-You need to pass the `meeting` object to it to see the unread polls count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "polls";
-}
-```
+ You need to pass the `meeting` object to it to see the unread polls count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'polls' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -41,6 +36,10 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-polls-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-polls-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-polls-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
index 32b89fad2be1ffb..0ccd3069c42b635 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-polls.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-polls component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ the ability to enable or disable them as per their permissions.
 
 ```html
 <!-- component.html -->
-<rtk-polls [meeting]="meeting" size="md"> </rtk-polls>
+<rtk-polls
+ [meeting]="meeting"
+ size="md">
+</rtk-polls>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
index 51f3ba8000a0d15..ad5090fddeb9402 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-indicator.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-recording-indicator component (Angular Librar
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,6 +30,9 @@ It will not render anything if no recording is taking place.
 
 ```html
 <!-- component.html -->
-<rtk-recording-indicator [meeting]="meeting" size="md">
+<rtk-recording-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-recording-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
index 47452de08e7ec1c..5bc2e14496eecf7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-recording-toggle.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-recording-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ who don't have the permission to record a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-recording-toggle [disabled]="true" [meeting]="meeting" size="md">
+<rtk-recording-toggle
+ [disabled]="true"
+ [meeting]="meeting"
+ size="md">
 </rtk-recording-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
index 00b6c6adc2aabc0..dec1ea51ccfddcc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screen-share-toggle.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-screen-share-toggle component (Angular Librar
 products:
   - realtime
 ---
-
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,6 +31,10 @@ A button which toggles your screenshare.
 
 ```html
 <!-- component.html -->
-<rtk-screen-share-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-screen-share-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-screen-share-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
index ab7da66afebf434..f678a4456bcdc0a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-screenshare-view.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-screenshare-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which plays a participant's screenshared video.
-It also allows for placement of other components similar to `rtk-participant-tile`.
-This component will not render anything if the participant hasn't start screensharing.
+ It also allows for placement of other components similar to `rtk-participant-tile`.
+ This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property               | Type                                                                                                                     | Required | Default           | Description             |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
-| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
-| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
-| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
-| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
-| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
-| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
-| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
-| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -37,14 +36,14 @@ This component will not render anything if the participant hasn't start screensh
 ```html
 <!-- component.html -->
 <rtk-screenshare-view
-	[hideFullScreenButton]="true"
-	[meeting]="meeting"
-	[nameTagPosition]="| 'bottom-left'
+ [hideFullScreenButton]="true"
+ [meeting]="meeting"
+ [nameTagPosition]="| 'bottom-left'
     | 'bottom-right'
     | 'bottom-center'
     | 'top-left'
     | 'top-right'
-    | 'top-center'"
->
+    | 'top-center'">
 </rtk-screenshare-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
index 066d024c27fab77..5818d8214fc8651 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-audio.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-audio component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +38,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 
 ```html
 <!-- component.html -->
-<rtk-settings-audio [meeting]="meeting" size="md"> </rtk-settings-audio>
+<rtk-settings-audio
+ [meeting]="meeting"
+ size="md">
+</rtk-settings-audio>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
index d003ef750b8f9f1..56af8d465416a8d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-toggle.mdx
@@ -5,25 +5,21 @@ description: API reference for rtk-settings-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of settings module.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSettings: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSettings: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description   |
-| ---------- | ------------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`              | ✅       | -                 | Size          |
-| `states`   | `States`            | ✅       | -                 | States object |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -38,5 +34,9 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 
 ```html
 <!-- component.html -->
-<rtk-settings-toggle size="md" variant="button"> </rtk-settings-toggle>
+<rtk-settings-toggle
+ size="md"
+ variant="button">
+</rtk-settings-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
index 381c51a0e2cf855..19b1a2ff5f132a7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings-video.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-video component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,5 +38,9 @@ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
 
 ```html
 <!-- component.html -->
-<rtk-settings-video [meeting]="meeting" size="md"> </rtk-settings-video>
+<rtk-settings-video
+ [meeting]="meeting"
+ size="md">
+</rtk-settings-video>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
index 9789b422d1f2837..339be6009cf2424 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-settings.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-settings component (Angular Library)
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,9 @@ as well as see your connection quality.
 
 ```html
 <!-- component.html -->
-<rtk-settings [meeting]="meeting" size="md"> </rtk-settings>
+<rtk-settings
+ [meeting]="meeting"
+ size="md">
+</rtk-settings>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
index 1406ce5ff38d369..d142bf62459ec14 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-setup-screen.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-setup-screen component (Angular Library)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,5 +32,9 @@ and media settings.
 
 ```html
 <!-- component.html -->
-<rtk-setup-screen [meeting]="meeting" size="md"> </rtk-setup-screen>
+<rtk-setup-screen
+ [meeting]="meeting"
+ size="md">
+</rtk-setup-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
index 94db2e01d33f007..8126edad79c871c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-sidebar-ui component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
@@ -33,9 +32,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-sidebar-ui
-	currentTab="example"
-	[focusCloseButton]="true"
-	[hideCloseAction]="true"
->
+ currentTab="example"
+ [focusCloseButton]="true"
+ [hideCloseAction]="true">
 </rtk-sidebar-ui>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
index 71e210674395a9d..bfd8e5e11b5177c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-sidebar.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-sidebar component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -37,9 +36,9 @@ you can customize which sections you want, and which section you want as the def
 ```html
 <!-- component.html -->
 <rtk-sidebar
-	[defaultSection]="rtksidebarsection"
-	[enabledSections]="[]"
-	[meeting]="meeting"
->
+ [defaultSection]="rtksidebarsection"
+ [enabledSections]="[]"
+ [meeting]="meeting">
 </rtk-sidebar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
index bf202dd85e47787..ea88ffe55f9f48e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-simple-grid.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-simple-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,6 +34,10 @@ A grid component which renders only the participants in a simple grid.
 
 ```html
 <!-- component.html -->
-<rtk-simple-grid aspectRatio="example" gap="42" [meeting]="meeting">
+<rtk-simple-grid
+ aspectRatio="example"
+ gap="42"
+ [meeting]="meeting">
 </rtk-simple-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
index 16628f891f7fa01..c19b21a731b3bcd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-speaker-selector.mdx
@@ -5,28 +5,26 @@ description: API reference for rtk-speaker-selector component (Angular Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -42,9 +40,9 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ```html
 <!-- component.html -->
 <rtk-speaker-selector
-	[meeting]="meeting"
-	size="md"
-	[variant]="'full' | 'inline'"
->
+ [meeting]="meeting"
+ size="md"
+ [variant]="'full' | 'inline'">
 </rtk-speaker-selector>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
index 47ea91cffa10d78..915451bf50a7527 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spinner.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spinner component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ A component which shows an animating spinner.
 
 ```html
 <!-- component.html -->
-<rtk-spinner size="md"> </rtk-spinner>
+<rtk-spinner
+ size="md">
+</rtk-spinner>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
index c3e3916f6cc12bb..f88cc7f531eac2c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-grid.mdx
@@ -5,29 +5,27 @@ description: API reference for rtk-spotlight-grid component (Angular Library)
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -42,6 +40,10 @@ You can customize the layout to a `column` view, by default is is `row`.
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-grid aspectRatio="example" gap="42" gridSize="md">
+<rtk-spotlight-grid
+ aspectRatio="example"
+ gap="42"
+ gridSize="md">
 </rtk-spotlight-grid>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
index ddb740d3af6b233..60b6debe69e9082 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-spotlight-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spotlight-indicator component (Angular Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-spotlight-indicator [meeting]="meeting" size="md">
+<rtk-spotlight-indicator
+ [meeting]="meeting"
+ size="md">
 </rtk-spotlight-indicator>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
index 27bcf1579495dbe..8e92fdc9598d17a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage-toggle.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-stage-toggle component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `states`   | `States1`           | ✅       | -                 | States         |
-| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -30,6 +29,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-stage-toggle [meeting]="meeting" size="md" variant="button">
+<rtk-stage-toggle
+ [meeting]="meeting"
+ size="md"
+ variant="button">
 </rtk-stage-toggle>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
index 0b94a4fd1566c92..ccffa6559353763 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-stage.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-stage component (Angular Library)
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,5 +28,9 @@ the `grid` and `sidebar` components.
 
 ```html
 <!-- component.html -->
-<rtk-stage [iconPack]="defaultIconPack" [t]="rtki18n"> </rtk-stage>
+<rtk-stage
+ [iconPack]="defaultIconPack"
+ [t]="rtki18n">
+</rtk-stage>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
index 75c781fb19e4ce2..f8993d18641c090 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-switch.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-switch component (Angular Library)
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,5 +30,10 @@ A switch component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-switch [checked]="true" [disabled]="true" [readonly]="true"> </rtk-switch>
+<rtk-switch
+ [checked]="true"
+ [disabled]="true"
+ [readonly]="true">
+</rtk-switch>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
index 339bfe235fceedb..1c8cf7cad9f42ff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tab-bar.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-tab-bar component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-tab-bar [activeTab]="tab" [layout]="gridlayout1" [meeting]="meeting">
+<rtk-tab-bar
+ [activeTab]="tab"
+ [layout]="gridlayout1"
+ [meeting]="meeting">
 </rtk-tab-bar>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
index b2a412cd7210059..cba219399b00342 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-composer-view.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-text-composer-view component (Angular Library
 products:
   - realtime
 ---
-
 A component which renders a text composer
 
 ## Properties
 
-| Property            | Type                              | Required | Default           | Description                                   |
-| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
-| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
-| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
-| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
-| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
-| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
-| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
-| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
-| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
-| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `placeholder` | `string` | ✅ | - | Placeholder text |
+| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
+| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `value` | `string` | ✅ | - | Default value for text input |
 
 ## Usage Examples
 
@@ -36,9 +35,9 @@ A component which renders a text composer
 ```html
 <!-- component.html -->
 <rtk-text-composer-view
-	[disabled]="true"
-	[keyDownHandler]="(e: keyboardevent)"
-	maxLength="42"
->
+ [disabled]="true"
+ [keyDownHandler]="(e: keyboardevent)"
+ maxLength="42">
 </rtk-text-composer-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
index 45ba2ef88c72b20..1ccf18977b7aa7d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message-view.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-text-message-view component (Angular Library)
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
@@ -28,6 +27,9 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message-view [isMarkdown]="true" text="example">
+<rtk-text-message-view
+ [isMarkdown]="true"
+ text="example">
 </rtk-text-message-view>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
index 230e3211e03b994..5060b6599375a57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-text-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-text-message component (Angular Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,6 +32,10 @@ A component which renders a text message from chat.
 
 ```html
 <!-- component.html -->
-<rtk-text-message [isContinued]="true" [message]="textmessage" [now]="date">
+<rtk-text-message
+ [isContinued]="true"
+ [message]="textmessage"
+ [now]="date">
 </rtk-text-message>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
index 371a6eec0e5bcf2..4e6f62691aef692 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-tooltip.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-tooltip component (Angular Library)
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
@@ -34,5 +33,10 @@ Tooltip component which follows RTK Design System.
 
 ```html
 <!-- component.html -->
-<rtk-tooltip delay="42" [disabled]="true" [kind]="tooltipkind"> </rtk-tooltip>
+<rtk-tooltip
+ delay="42"
+ [disabled]="true"
+ [kind]="tooltipkind">
+</rtk-tooltip>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
index 570133cd5d8d464..4f6fe2ff039b589 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcript.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-transcript component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ You need to remove the element after you receive the
 
 ```html
 <!-- component.html -->
-<rtk-transcript [t]="rtki18n" transcript="example"> </rtk-transcript>
+<rtk-transcript
+ [t]="rtki18n"
+ transcript="example">
+</rtk-transcript>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
index 578013baff0705a..4e6c1192fcba044 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-transcripts.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-transcripts component (Angular Library)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,5 +31,8 @@ There are also certain limits which you can set as well.
 
 ```html
 <!-- component.html -->
-<rtk-transcripts [meeting]="meeting"> </rtk-transcripts>
+<rtk-transcripts
+ [meeting]="meeting">
+</rtk-transcripts>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
index 8602181f2eb682c..0bfe8c1b9050c14 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-ui-provider.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ui-provider component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
@@ -32,9 +31,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-ui-provider
-	[config]="defaultUiConfig"
-	[mode]="meeting"
-	[showSetupScreen]="true"
->
+ [config]="defaultUiConfig"
+ [mode]="meeting"
+ [showSetupScreen]="true">
 </rtk-ui-provider>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
index f64a1ff20e41f82..bb61879c99d4f26 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-viewer-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-viewer-count component (Angular Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
@@ -30,5 +29,9 @@ A component which shows count of total joined participants in a meeting.
 
 ```html
 <!-- component.html -->
-<rtk-viewer-count [meeting]="meeting" variant="primary"> </rtk-viewer-count>
+<rtk-viewer-count
+ [meeting]="meeting"
+ variant="primary">
+</rtk-viewer-count>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
index 040843c9c08f95e..63be1a12b781fd2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-virtualized-participant-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-virtualized-participant-list component (Angul
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
@@ -30,9 +29,9 @@ products:
 ```html
 <!-- component.html -->
 <rtk-virtualized-participant-list
-	bufferedItemsCount="42"
-	[emptyListElement]="htmlelement"
-	itemHeight="42"
->
+ bufferedItemsCount="42"
+ [emptyListElement]="htmlelement"
+ itemHeight="42">
 </rtk-virtualized-participant-list>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
index ed0bda90edc56eb..46061d522a85431 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/angular/rtk-waiting-screen.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-waiting-screen component (Angular Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,5 +27,8 @@ products:
 
 ```html
 <!-- component.html -->
-<rtk-waiting-screen [meeting]="meeting"> </rtk-waiting-screen>
+<rtk-waiting-screen
+ [meeting]="meeting">
+</rtk-waiting-screen>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
index 8ef6d5dcdfadf48..7f6ea96d5eaefa0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
index 4a58db7ec3bb580..e270c77642b2c4a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai-transcriptions.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-ai-transcriptions component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,14 +24,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai-transcriptions> </rtk-ai-transcriptions>
+<rtk-ai-transcriptions>
+</rtk-ai-transcriptions>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ai-transcriptions");
+  const el = document.querySelector("rtk-ai-transcriptions");
 
-	el.initialTranscriptions = [];
-	el.meeting = meeting;
+  el.initialTranscriptions= [];
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
index a55ac07cacbbec6..970e391d75c32bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ai.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ai component (Web Components (HTML) Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-ai size="md"> </rtk-ai>
+<rtk-ai
+ size="md">
+</rtk-ai>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ai");
+  const el = document.querySelector("rtk-ai");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
index ac1e4eef81b052e..2d9130e9d8e4121 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-grid.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-grid> </rtk-audio-grid>
+<rtk-audio-grid>
+</rtk-audio-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-grid");
+  const el = document.querySelector("rtk-audio-grid");
 
-	el.config = defaultUiConfig;
-	el.hideSelf = true;
-	el.meeting = meeting;
+  el.config= defaultUiConfig
+  el.hideSelf= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
index 6b7d96a935dd7f4..8959b0dde236c5c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-tile.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-audio-tile component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-audio-tile> </rtk-audio-tile>
+<rtk-audio-tile>
+</rtk-audio-tile>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-tile");
+  const el = document.querySelector("rtk-audio-tile");
 
-	el.config = defaultUiConfig;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.config= defaultUiConfig
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
index 8ff29c76cd061be..813eab6b421006a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-audio-visualizer.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-audio-visualizer component (Web Components (H
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,15 +31,17 @@ Commonly used inside `rtk-name-tag`.
 ### With Properties
 
 ```html
-<rtk-audio-visualizer> </rtk-audio-visualizer>
+<rtk-audio-visualizer>
+</rtk-audio-visualizer>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-audio-visualizer");
+  const el = document.querySelector("rtk-audio-visualizer");
 
-	el.hideMuted = true;
-	el.isScreenShare = true;
-	el.participant = participant;
+  el.hideMuted= true;
+  el.isScreenShare= true;
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
index d3d2acf95812bd9..7f8b81f1043b96d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-avatar.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-avatar component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
@@ -29,13 +28,18 @@ Avatar component which renders a participant's image or their initials.
 ### With Properties
 
 ```html
-<rtk-avatar participant="example" size="md" variant="circular"> </rtk-avatar>
+<rtk-avatar
+ participant="example"
+ size="md"
+ variant="circular">
+</rtk-avatar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-avatar");
+  const el = document.querySelector("rtk-avatar");
 
-	el.participant = {};
+  el.participant= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
index 08565892ad5d286..0ffde64de310896 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-manager.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-breakout-room-manager component (Web Componen
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,15 +31,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-room-manager> </rtk-breakout-room-manager>
+<rtk-breakout-room-manager>
+</rtk-breakout-room-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-room-manager");
+  const el = document.querySelector("rtk-breakout-room-manager");
 
-	el.allowDelete = true;
-	el.assigningParticipants = true;
-	el.defaultExpanded = true;
+  el.allowDelete= true;
+  el.assigningParticipants= true;
+  el.defaultExpanded= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
index 90bf0a7a6599970..a27e85c3f7202e5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-room-participants.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-breakout-room-participants component (Web Com
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,18 +30,18 @@ run privileged actions on each participant according to your permissions.
 
 ```html
 <rtk-breakout-room-participants
-	participantIds="example"
-	selectedParticipantIds="example"
->
+ participantIds="example"
+ selectedParticipantIds="example">
 </rtk-breakout-room-participants>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-room-participants");
+  const el = document.querySelector("rtk-breakout-room-participants");
 
-	el.meeting = meeting;
-	el.participantIds = [];
-	el.selectedParticipantIds = [];
+  el.meeting= meeting
+  el.participantIds= [];
+  el.selectedParticipantIds= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
index 8186a41e5b921c7..4d3fe5430be46fe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-manager.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-breakout-rooms-manager component (Web Compone
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-manager> </rtk-breakout-rooms-manager>
+<rtk-breakout-rooms-manager>
+</rtk-breakout-rooms-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-rooms-manager");
+  const el = document.querySelector("rtk-breakout-rooms-manager");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
index 330651ce2800cee..12e8adafccffa1d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-breakout-rooms-toggle.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-breakout-rooms-toggle component (Web Componen
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,14 +30,17 @@ You need to pass the `meeting` object to it.
 ### With Properties
 
 ```html
-<rtk-breakout-rooms-toggle size="md"> </rtk-breakout-rooms-toggle>
+<rtk-breakout-rooms-toggle
+ size="md">
+</rtk-breakout-rooms-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-breakout-rooms-toggle");
+  const el = document.querySelector("rtk-breakout-rooms-toggle");
 
-	el.iconPack = defaultIconPack;
-	el.meeting = meeting;
+  el.iconPack= defaultIconPack
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
index 90a5bf9760e290c..c701b24f24c37b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-broadcast-message-modal.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-broadcast-message-modal component (Web Compon
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-broadcast-message-modal> </rtk-broadcast-message-modal>
+<rtk-broadcast-message-modal>
+</rtk-broadcast-message-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-broadcast-message-modal");
+  const el = document.querySelector("rtk-broadcast-message-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
index 2257bd8dc185484..190ce0bd634cebf 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-button.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-button component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
@@ -30,14 +29,16 @@ A button that follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-button> </rtk-button>
+<rtk-button>
+</rtk-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-button");
+  const el = document.querySelector("rtk-button");
 
-	el.disabled = true;
-	el.reverse = true;
+  el.disabled= true;
+  el.reverse= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
index 31e3f2482ecb54c..839aea969dea5f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-camera-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-camera-selector component (Web Components (HT
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-camera-selector size="md"> </rtk-camera-selector>
+<rtk-camera-selector
+ size="md">
+</rtk-camera-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-camera-selector");
+  const el = document.querySelector("rtk-camera-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
index 7726ca148fdf888..6062945d8cda350 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat-composer-ui component (Web Components (H
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-composer-ui size="md"> </rtk-chat-composer-ui>
+<rtk-chat-composer-ui
+ size="md">
+</rtk-chat-composer-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-composer-ui");
+  const el = document.querySelector("rtk-chat-composer-ui");
 
-	el.canSendFiles = true;
-	el.canSendTextMessage = true;
+  el.canSendFiles= true;
+  el.canSendTextMessage= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
index 6f24d73d4050be8..4f0b587d7e57cda 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-composer-view.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-chat-composer-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,15 +34,17 @@ A component which renders a chat composer
 ### With Properties
 
 ```html
-<rtk-chat-composer-view inputTextPlaceholder="example">
+<rtk-chat-composer-view
+ inputTextPlaceholder="example">
 </rtk-chat-composer-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-composer-view");
+  const el = document.querySelector("rtk-chat-composer-view");
 
-	el.canSendFiles = true;
-	el.canSendTextMessage = true;
+  el.canSendFiles= true;
+  el.canSendTextMessage= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
index d53fa58a0768116..00331fb11033be4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-header.mdx
@@ -5,10 +5,9 @@ description: API reference for rtk-chat-header component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
@@ -17,3 +16,4 @@ _No properties available._
 ```html
 <rtk-chat-header></rtk-chat-header>
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
index 67158b1da131121..b49edd649f06ee1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-message.mdx
@@ -5,30 +5,29 @@ description: API reference for rtk-chat-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -41,15 +40,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-message> </rtk-chat-message>
+<rtk-chat-message>
+</rtk-chat-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-message");
+  const el = document.querySelector("rtk-chat-message");
 
-	el.alignRight = true;
-	el.canDelete = true;
-	el.canEdit = true;
+  el.alignRight= true;
+  el.canDelete= true;
+  el.canEdit= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
index 9b334cb50256afd..1a1f8d1bb2a313f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui-paginated.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-chat-messages-ui-paginated component (Web Com
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui-paginated size="md"> </rtk-chat-messages-ui-paginated>
+<rtk-chat-messages-ui-paginated
+ size="md">
+</rtk-chat-messages-ui-paginated>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-messages-ui-paginated");
+  const el = document.querySelector("rtk-chat-messages-ui-paginated");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
index 91b79ea94878ffb..4315ce89d3ea880 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-messages-ui.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-chat-messages-ui component (Web Components (H
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,14 +30,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-messages-ui selectedGroup="example"> </rtk-chat-messages-ui>
+<rtk-chat-messages-ui
+ selectedGroup="example">
+</rtk-chat-messages-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-messages-ui");
+  const el = document.querySelector("rtk-chat-messages-ui");
 
-	el.canPinMessages = true;
-	el.messages = [];
+  el.canPinMessages= true;
+  el.messages= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
index fd7ba927fca8daa..12510bac6bda05a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-search-results.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-search-results component (Web Components
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,14 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-search-results channelId="example" query="example">
+<rtk-chat-search-results
+ channelId="example"
+ query="example">
 </rtk-chat-search-results>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-search-results");
+  const el = document.querySelector("rtk-chat-search-results");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
index 713fb73bd989f34..88fd33ff9a1e098 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector-ui.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-chat-selector-ui component (Web Components (H
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
@@ -28,14 +27,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector-ui selectedGroupId="example" selfUserId="example">
+<rtk-chat-selector-ui
+ selectedGroupId="example"
+ selfUserId="example">
 </rtk-chat-selector-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-selector-ui");
+  const el = document.querySelector("rtk-chat-selector-ui");
 
-	el.groups = [];
+  el.groups= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
index f41ed748ffb2bcf..35043d7c0f2796e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat-selector.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-chat-selector component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-chat-selector size="md"> </rtk-chat-selector>
+<rtk-chat-selector
+ size="md">
+</rtk-chat-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat-selector");
+  const el = document.querySelector("rtk-chat-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
index d296e1f85861da7..f1f46fa4254dfc0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-chat.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-chat component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ Fully featured chat component with image & file upload, emoji picker and auto-sc
 ### With Properties
 
 ```html
-<rtk-chat size="md"> </rtk-chat>
+<rtk-chat
+ size="md">
+</rtk-chat>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-chat");
+  const el = document.querySelector("rtk-chat");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
index f29acbd05520f7c..f4befa6dbda7af6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-clock.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-clock component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ Shows the time elapsed in a meeting.
 ### With Properties
 
 ```html
-<rtk-clock size="md"> </rtk-clock>
+<rtk-clock
+ size="md">
+</rtk-clock>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-clock");
+  const el = document.querySelector("rtk-clock");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
index 54bd7f2399df487..59a36b5e16679da 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-confirmation-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-confirmation-modal component (Web Components
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-confirmation-modal> </rtk-confirmation-modal>
+<rtk-confirmation-modal>
+</rtk-confirmation-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-confirmation-modal");
+  const el = document.querySelector("rtk-confirmation-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
index b63c726196d6d84..59c9be5f52f7987 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar-button.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-controlbar-button component (Web Components (
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ A skeleton component used for composing custom controlbar buttons.
 ### With Properties
 
 ```html
-<rtk-controlbar-button icon="example"> </rtk-controlbar-button>
+<rtk-controlbar-button
+ icon="example">
+</rtk-controlbar-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-controlbar-button");
+  const el = document.querySelector("rtk-controlbar-button");
 
-	el.brandIcon = true;
-	el.disabled = true;
+  el.brandIcon= true;
+  el.disabled= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
index 326a72bac0165d4..c303a5102cb22ac 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-controlbar.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-controlbar component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ Controlbar component provides you with various designs as variants.
 ### With Properties
 
 ```html
-<rtk-controlbar size="md"> </rtk-controlbar>
+<rtk-controlbar
+ size="md">
+</rtk-controlbar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-controlbar");
+  const el = document.querySelector("rtk-controlbar");
 
-	el.disableRender = true;
-	el.meeting = meeting;
+  el.disableRender= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
index 762c4d9d8d1cfc9..59bbbbf35837964 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-counter.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-counter component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
@@ -29,14 +28,17 @@ A number picker with increment and decrement buttons.
 ### With Properties
 
 ```html
-<rtk-counter size="md"> </rtk-counter>
+<rtk-counter
+ size="md">
+</rtk-counter>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-counter");
+  const el = document.querySelector("rtk-counter");
 
-	el.minValue = 42;
-	el.value = 42;
+  el.minValue= 42;
+  el.value= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
index 22f1b026cd01b82..8733f92d520e775 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-audio.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-audio component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-audio size="md"> </rtk-debugger-audio>
+<rtk-debugger-audio
+ size="md">
+</rtk-debugger-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-audio");
+  const el = document.querySelector("rtk-debugger-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
index 9435b3bec0238c6..f7f80fd287b5ef1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-screenshare.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-screenshare component (Web Component
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-screenshare size="md"> </rtk-debugger-screenshare>
+<rtk-debugger-screenshare
+ size="md">
+</rtk-debugger-screenshare>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-screenshare");
+  const el = document.querySelector("rtk-debugger-screenshare");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
index a80a0f3c3252295..a7cc1725cc28364 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-system.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-system component (Web Components (HT
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-system size="md"> </rtk-debugger-system>
+<rtk-debugger-system
+ size="md">
+</rtk-debugger-system>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-system");
+  const el = document.querySelector("rtk-debugger-system");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
index 9deac224fdf1a02..84a90649d07675a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger-video.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-debugger-video component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-debugger-video size="md"> </rtk-debugger-video>
+<rtk-debugger-video
+ size="md">
+</rtk-debugger-video>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger-video");
+  const el = document.querySelector("rtk-debugger-video");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
index 7d345ee443ecde8..a8141d499177b06 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-debugger.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-debugger component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ A troubleshooting component to identify and fix any issues in the meeting.
 ### With Properties
 
 ```html
-<rtk-debugger size="md"> </rtk-debugger>
+<rtk-debugger
+ size="md">
+</rtk-debugger>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-debugger");
+  const el = document.querySelector("rtk-debugger");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
index 3709d9d501cd38e..ba7f8b4cd15bf85 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog-manager.mdx
@@ -5,26 +5,24 @@ description: API reference for rtk-dialog-manager component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -37,13 +35,16 @@ A component which handles all dialog elements in a component such as:
 ### With Properties
 
 ```html
-<rtk-dialog-manager size="md"> </rtk-dialog-manager>
+<rtk-dialog-manager
+ size="md">
+</rtk-dialog-manager>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-dialog-manager");
+  const el = document.querySelector("rtk-dialog-manager");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
index d361f6b14ccdb8b..170ade6492a1274 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-dialog.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-dialog component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,15 +32,17 @@ A dialog component.
 ### With Properties
 
 ```html
-<rtk-dialog> </rtk-dialog>
+<rtk-dialog>
+</rtk-dialog>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-dialog");
+  const el = document.querySelector("rtk-dialog");
 
-	el.disableEscapeKey = true;
-	el.hideCloseButton = true;
-	el.meeting = meeting;
+  el.disableEscapeKey= true;
+  el.hideCloseButton= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
index 7060d45d649d00a..f21db9738750267 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-draft-attachment-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-draft-attachment-view component (Web Componen
 products:
   - realtime
 ---
-
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property     | Type                                                 | Required | Default           | Description           |
-| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
-| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
-| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ A component which renders the draft attachment to send
 ### With Properties
 
 ```html
-<rtk-draft-attachment-view> </rtk-draft-attachment-view>
+<rtk-draft-attachment-view>
+</rtk-draft-attachment-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-draft-attachment-view");
+  const el = document.querySelector("rtk-draft-attachment-view");
 
-	el.attachment = {};
+  el.attachment= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
index be00c3a6e33ad46..f67d8a0f096c864 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker-button.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-emoji-picker-button component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,13 +24,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-emoji-picker-button> </rtk-emoji-picker-button>
+<rtk-emoji-picker-button>
+</rtk-emoji-picker-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-emoji-picker-button");
+  const el = document.querySelector("rtk-emoji-picker-button");
 
-	el.isActive = true;
+  el.isActive= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
index 69aabd63c26f21f..a0876babb985962 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-emoji-picker.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-emoji-picker component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ A very simple emoji picker component.
 ### With Properties
 
 ```html
-<rtk-emoji-picker> </rtk-emoji-picker>
+<rtk-emoji-picker>
+</rtk-emoji-picker>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-emoji-picker");
+  const el = document.querySelector("rtk-emoji-picker");
 
-	el.focusWhenOpened = true;
+  el.focusWhenOpened= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
index e5388b1585fd982..6aa6297284ea709 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ended-screen.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-ended-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ A screen which shows a meeting has ended.
 ### With Properties
 
 ```html
-<rtk-ended-screen size="md"> </rtk-ended-screen>
+<rtk-ended-screen
+ size="md">
+</rtk-ended-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ended-screen");
+  const el = document.querySelector("rtk-ended-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
index fdf7e9e77e382ba..a9528f31a65a0cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-dropzone.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-file-dropzone component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,11 +24,14 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-dropzone> </rtk-file-dropzone>
+<rtk-file-dropzone>
+</rtk-file-dropzone>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-dropzone");
+  const el = document.querySelector("rtk-file-dropzone");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
index 083396274de8c83..1764939b1ca0276 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message-view.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-file-message-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
@@ -28,13 +27,17 @@ A component which renders a file message.
 ### With Properties
 
 ```html
-<rtk-file-message-view name="example" url="example"> </rtk-file-message-view>
+<rtk-file-message-view
+ name="example"
+ url="example">
+</rtk-file-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-message-view");
+  const el = document.querySelector("rtk-file-message-view");
 
-	el.size = 42;
+  el.size= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
index 936feef21b37fa9..811a6cce1a3b65e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-file-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders a file message from chat.
 ### With Properties
 
 ```html
-<rtk-file-message> </rtk-file-message>
+<rtk-file-message>
+</rtk-file-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-message");
+  const el = document.querySelector("rtk-file-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
index 851138e1627613b..54b3d5dd21d7da8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-file-picker-button.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-file-picker-button component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,14 +26,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-file-picker-button filter="example" label="example">
+<rtk-file-picker-button
+ filter="example"
+ label="example">
 </rtk-file-picker-button>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-file-picker-button");
+  const el = document.querySelector("rtk-file-picker-button");
 
-	el.icon = defaultIconPack;
+  el.icon= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
index d663d791207416c..f3865d72720b943 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid-pagination.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-grid-pagination component (Web Components (HT
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ of active participants list. This is reflected in the `rtk-grid` component.
 ### With Properties
 
 ```html
-<rtk-grid-pagination size="md"> </rtk-grid-pagination>
+<rtk-grid-pagination
+ size="md">
+</rtk-grid-pagination>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-grid-pagination");
+  const el = document.querySelector("rtk-grid-pagination");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
index 31eef43afae392f..cf79955eff09681 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-grid.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-grid component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,13 +34,17 @@ The main grid component which abstracts all the grid handling logic and renders
 ### With Properties
 
 ```html
-<rtk-grid aspectRatio="example" gridSize="md"> </rtk-grid>
+<rtk-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-grid");
+  const el = document.querySelector("rtk-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
index a89c57e5b374cc4..1fb6ec7f5c5a1b6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-header.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-header component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ A component that houses all the header components.
 ### With Properties
 
 ```html
-<rtk-header size="md"> </rtk-header>
+<rtk-header
+ size="md">
+</rtk-header>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-header");
+  const el = document.querySelector("rtk-header");
 
-	el.disableRender = true;
-	el.meeting = meeting;
+  el.disableRender= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
index 225e4d075df1fad..581f5e42555059a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-icon.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-icon component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
@@ -27,11 +26,17 @@ An icon component which accepts an svg string and renders it.
 ### With Properties
 
 ```html
-<rtk-icon icon="example" size="md" variant="primary"> </rtk-icon>
+<rtk-icon
+ icon="example"
+ size="md"
+ variant="primary">
+</rtk-icon>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-icon");
+  const el = document.querySelector("rtk-icon");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
index 54a72fdf6f17b5b..a2e6c178b6c1e82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-idle-screen.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-idle-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ i.e; when you are waiting for data about the meeting, specifically the `meeting`
 ### With Properties
 
 ```html
-<rtk-idle-screen> </rtk-idle-screen>
+<rtk-idle-screen>
+</rtk-idle-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-idle-screen");
+  const el = document.querySelector("rtk-idle-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
index 4faebe0ab376143..707341e71c859f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message-view.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-image-message-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
@@ -27,11 +26,15 @@ A component which renders an image message.
 ### With Properties
 
 ```html
-<rtk-image-message-view url="example"> </rtk-image-message-view>
+<rtk-image-message-view
+ url="example">
+</rtk-image-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-message-view");
+  const el = document.querySelector("rtk-image-message-view");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
index cb324944fd49d2c..76c23bbf2dfca99 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-image-message component (Web Components (HTML
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders an image message from chat.
 ### With Properties
 
 ```html
-<rtk-image-message> </rtk-image-message>
+<rtk-image-message>
+</rtk-image-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-message");
+  const el = document.querySelector("rtk-image-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
index b7e74691417c0f1..da7064e9253ab13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-image-viewer.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-image-viewer component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,11 +27,15 @@ A component which shows an image sent via chat.
 ### With Properties
 
 ```html
-<rtk-image-viewer size="md"> </rtk-image-viewer>
+<rtk-image-viewer
+ size="md">
+</rtk-image-viewer>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-image-viewer");
+  const el = document.querySelector("rtk-image-viewer");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
index f638b70c50e83d4..7950fc7f2bc101a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-information-tooltip.mdx
@@ -5,12 +5,11 @@ description: API reference for rtk-information-tooltip component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
@@ -23,13 +22,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-information-tooltip> </rtk-information-tooltip>
+<rtk-information-tooltip>
+</rtk-information-tooltip>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-information-tooltip");
+  const el = document.querySelector("rtk-information-tooltip");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
index 7cbac34216b6b9a..36d7fcfd41612fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-join-stage.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-join-stage component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-join-stage size="md"> </rtk-join-stage>
+<rtk-join-stage
+ size="md">
+</rtk-join-stage>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-join-stage");
+  const el = document.querySelector("rtk-join-stage");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
index 7953645ed11d440..60d83d6896b419b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-leave-meeting.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-leave-meeting component (Web Components (HTML
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ end meeting for all, if you have the permission.
 ### With Properties
 
 ```html
-<rtk-leave-meeting> </rtk-leave-meeting>
+<rtk-leave-meeting>
+</rtk-leave-meeting>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-leave-meeting");
+  const el = document.querySelector("rtk-leave-meeting");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
index 7089f2c65e4c3b4..67707911b550145 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-indicator component (Web Component
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-indicator size="md"> </rtk-livestream-indicator>
+<rtk-livestream-indicator
+ size="md">
+</rtk-livestream-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-livestream-indicator");
+  const el = document.querySelector("rtk-livestream-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
index 4d35b373ccbafc2..5e6da815b9a6c32 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-livestream-player.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-livestream-player component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-livestream-player size="md"> </rtk-livestream-player>
+<rtk-livestream-player
+ size="md">
+</rtk-livestream-player>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-livestream-player");
+  const el = document.querySelector("rtk-livestream-player");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
index cb8ff8473cd8a3e..f6713bd26d22ab2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-logo.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-logo component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which loads the logo from your config, or via the `logo-url` attribu
 ### With Properties
 
 ```html
-<rtk-logo logoUrl="example"> </rtk-logo>
+<rtk-logo
+ logoUrl="example">
+</rtk-logo>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-logo");
+  const el = document.querySelector("rtk-logo");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
index 811851e7e12e984..d1381ac73ca5828 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-markdown-view.mdx
@@ -5,13 +5,12 @@ description: API reference for rtk-markdown-view component (Web Components (HTML
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
@@ -24,13 +23,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-markdown-view text="example"> </rtk-markdown-view>
+<rtk-markdown-view
+ text="example">
+</rtk-markdown-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-markdown-view");
+  const el = document.querySelector("rtk-markdown-view");
 
-	el.maxLength = 42;
+  el.maxLength= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
index 55697cb504158d1..ba9885092147cbb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting-title.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-meeting-title component (Web Components (HTML
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ Displays the title of the meeting.
 ### With Properties
 
 ```html
-<rtk-meeting-title> </rtk-meeting-title>
+<rtk-meeting-title>
+</rtk-meeting-title>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-meeting-title");
+  const el = document.querySelector("rtk-meeting-title");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
index 753af9e783bf586..0a6abda1bfb826a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-meeting.mdx
@@ -5,28 +5,27 @@ description: API reference for rtk-meeting component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -39,14 +38,16 @@ dialogs and other smaller bits of managing the application.
 ### With Properties
 
 ```html
-<rtk-meeting> </rtk-meeting>
+<rtk-meeting>
+</rtk-meeting>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-meeting");
+  const el = document.querySelector("rtk-meeting");
 
-	el.applyDesignSystem = true;
-	el.config = defaultUiConfig;
+  el.applyDesignSystem= true;
+  el.config= defaultUiConfig
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
index c9fd4b7ff50b042..169675ff5a4498c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-item.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-menu-item component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,11 +27,15 @@ A menu item component.
 ### With Properties
 
 ```html
-<rtk-menu-item size="md"> </rtk-menu-item>
+<rtk-menu-item
+ size="md">
+</rtk-menu-item>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu-item");
+  const el = document.querySelector("rtk-menu-item");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
index 6735e67c1b647e8..88b9d8538638163 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-menu-list component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,11 +26,14 @@ A menu list component.
 ### With Properties
 
 ```html
-<rtk-menu-list> </rtk-menu-list>
+<rtk-menu-list>
+</rtk-menu-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu-list");
+  const el = document.querySelector("rtk-menu-list");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
index bb093d6585896ca..12ad508b8b32180 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-menu.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-menu component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ A menu component.
 ### With Properties
 
 ```html
-<rtk-menu size="md"> </rtk-menu>
+<rtk-menu
+ size="md">
+</rtk-menu>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-menu");
+  const el = document.querySelector("rtk-menu");
 
-	el.offset = 42;
+  el.offset= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
index f409f90de250597..cdb30bac0e60ed4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-list-view.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-message-list-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders list of messages.
 
 ## Properties
 
-| Property            | Type                                | Required | Default           | Description                                                                   |
-| ------------------- | ----------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------- |
-| `estimateItemSize`  | `number`                            | ✅       | -                 | Estimated height of an item                                                   |
-| `iconPack`          | `IconPack1`                         | ❌       | `defaultIconPack` | Icon pack                                                                     |
-| `loadMore`          | `(lastMessage: Message)`            | ✅       | -                 | Function to load more messages. Messages returned from this will be prepended |
-| `messages`          | `Message[]`                         | ✅       | -                 | Messages to render                                                            |
-| `renderer`          | `(message: Message, index: number)` | ✅       | -                 | Render function of the message                                                |
-| `visibleItemsCount` | `number`                            | ✅       | -                 | Maximum visible messages                                                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `estimateItemSize` | `number` | ✅ | - | Estimated height of an item |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `loadMore` | `(lastMessage: Message)` | ✅ | - | Function to load more messages. Messages returned from this will be prepended |
+| `messages` | `Message[]` | ✅ | - | Messages to render |
+| `renderer` | `(message: Message, index: number)` | ✅ | - | Render function of the message |
+| `visibleItemsCount` | `number` | ✅ | - | Maximum visible messages |
 
 ## Usage Examples
 
@@ -30,14 +29,16 @@ A component which renders list of messages.
 ### With Properties
 
 ```html
-<rtk-message-list-view> </rtk-message-list-view>
+<rtk-message-list-view>
+</rtk-message-list-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-message-list-view");
+  const el = document.querySelector("rtk-message-list-view");
 
-	el.estimateItemSize = 42;
-	el.messages = [];
+  el.estimateItemSize= 42;
+  el.messages= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
index 09def76b8fce5db..728e84fc9321401 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-message-view.mdx
@@ -5,25 +5,24 @@ description: API reference for rtk-message-view component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
@@ -36,13 +35,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-message-view authorName="example" avatarUrl="example"> </rtk-message-view>
+<rtk-message-view
+ authorName="example"
+ avatarUrl="example">
+</rtk-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-message-view");
+  const el = document.querySelector("rtk-message-view");
 
-	el.actions = [];
+  el.actions= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
index 0e2adb948d754a3..1565dc06501cfad 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-microphone-selector.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-microphone-selector component (Web Components
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-microphone-selector size="md"> </rtk-microphone-selector>
+<rtk-microphone-selector
+ size="md">
+</rtk-microphone-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-microphone-selector");
+  const el = document.querySelector("rtk-microphone-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
index 79ad17a23ebacab..d399d66944cd6fc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mixed-grid.mdx
@@ -5,27 +5,26 @@ description: API reference for rtk-mixed-grid component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +37,17 @@ A grid component which handles screenshares, plugins and participants.
 ### With Properties
 
 ```html
-<rtk-mixed-grid aspectRatio="example" gridSize="md"> </rtk-mixed-grid>
+<rtk-mixed-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-mixed-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-mixed-grid");
+  const el = document.querySelector("rtk-mixed-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
index 83ee618b019e4c1..43e569451c44e9b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-more-toggle.mdx
@@ -5,24 +5,20 @@ description: API reference for rtk-more-toggle component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -35,11 +31,15 @@ When clicked it emits a `rtkStateUpdate` event with the data:
 ### With Properties
 
 ```html
-<rtk-more-toggle size="md"> </rtk-more-toggle>
+<rtk-more-toggle
+ size="md">
+</rtk-more-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-more-toggle");
+  const el = document.querySelector("rtk-more-toggle");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
index 6bb1b8bdce29e58..8100fe45db00611 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-mute-all-confirmation.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-mute-all-confirmation component (Web Componen
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-mute-all-confirmation> </rtk-mute-all-confirmation>
+<rtk-mute-all-confirmation>
+</rtk-mute-all-confirmation>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-mute-all-confirmation");
+  const el = document.querySelector("rtk-mute-all-confirmation");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
index 14082b5393b2820..f6cee72609ed898 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-name-tag.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-name-tag component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
@@ -31,15 +30,17 @@ A component which shows a participant's name.
 ### With Properties
 
 ```html
-<rtk-name-tag> </rtk-name-tag>
+<rtk-name-tag>
+</rtk-name-tag>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-name-tag");
+  const el = document.querySelector("rtk-name-tag");
 
-	el.isScreenShare = true;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.isScreenShare= true;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
index b5241b2075c51f8..a87b7aea196b1a0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-network-indicator.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-network-indicator component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,15 +26,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-network-indicator> </rtk-network-indicator>
+<rtk-network-indicator>
+</rtk-network-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-network-indicator");
+  const el = document.querySelector("rtk-network-indicator");
 
-	el.isScreenShare = true;
-	el.meeting = meeting;
-	el.participant = participant;
+  el.isScreenShare= true;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
index 4573caf03b498f0..e175a377ba80f6e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notification.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-notification component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ You need to remove the element after you receive the
 ### With Properties
 
 ```html
-<rtk-notification size="md"> </rtk-notification>
+<rtk-notification
+ size="md">
+</rtk-notification>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-notification");
+  const el = document.querySelector("rtk-notification");
 
-	el.paused = true;
+  el.paused= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
index c914a13e3c8be1a..1854740c5dd7087 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-notifications.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-notifications component (Web Components (HTML
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,13 +31,16 @@ There are also certain limits which you can set as well.
 ### With Properties
 
 ```html
-<rtk-notifications size="md"> </rtk-notifications>
+<rtk-notifications
+ size="md">
+</rtk-notifications>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-notifications");
+  const el = document.querySelector("rtk-notifications");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
index 9364cd4626d354c..0cb6286a078603e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-overlay-modal.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-overlay-modal component (Web Components (HTML
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A confirmation modal.
 ### With Properties
 
 ```html
-<rtk-overlay-modal> </rtk-overlay-modal>
+<rtk-overlay-modal>
+</rtk-overlay-modal>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-overlay-modal");
+  const el = document.querySelector("rtk-overlay-modal");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
index 4cde117f427306e..ef79cf0de81f3f7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-paginated-list.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-paginated-list component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,14 +31,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-paginated-list emptyListLabel="example"> </rtk-paginated-list>
+<rtk-paginated-list
+ emptyListLabel="example">
+</rtk-paginated-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-paginated-list");
+  const el = document.querySelector("rtk-paginated-list");
 
-	el.autoScroll = true;
-	el.createNodes = [];
+  el.autoScroll= true;
+  el.createNodes= [];
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
index 7719882d3fb4be7..d62e21d5129aa82 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participant-count component (Web Components (
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-participant-count size="md"> </rtk-participant-count>
+<rtk-participant-count
+ size="md">
+</rtk-participant-count>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-count");
+  const el = document.querySelector("rtk-participant-count");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
index f6bd84e42574673..caf9dc47c1b7c3f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-setup.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-participant-setup component (Web Components (
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -31,14 +30,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participant-setup> </rtk-participant-setup>
+<rtk-participant-setup>
+</rtk-participant-setup>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-setup");
+  const el = document.querySelector("rtk-participant-setup");
 
-	el.isPreview = true;
-	el.participant = participant;
+  el.isPreview= true;
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
index 9a88d9c0a727ee0..4cab2f0eb1eca60 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant-tile.mdx
@@ -5,24 +5,23 @@ description: API reference for rtk-participant-tile component (Web Components (H
 products:
   - realtime
 ---
-
 A component which plays a participants video and allows for placement
-of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
+ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component.
 
 ## Properties
 
-| Property          | Type                                                                                                                     | Required | Default                 | Description                      |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------- | -------------------------------- |
-| `config`          | `UIConfig`                                                                                                               | ❌       | `createDefaultConfig()` | Config object                    |
-| `iconPack`        | `IconPack`                                                                                                               | ❌       | `defaultIconPack`       | Icon pack                        |
-| `isPreview`       | `boolean`                                                                                                                | ✅       | -                       | Whether tile is used for preview |
-| `meeting`         | `Meeting`                                                                                                                | ✅       | -                       | Meeting object                   |
-| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                       | Position of name tag             |
-| `participant`     | `Peer`                                                                                                                   | ✅       | -                       | Participant object               |
-| `size`            | `Size`                                                                                                                   | ✅       | -                       | Size                             |
-| `states`          | `States`                                                                                                                 | ✅       | -                       | States object                    |
-| `t`               | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`         | Language                         |
-| `variant`         | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isPreview` | `boolean` | ✅ | - | Whether tile is used for preview |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -35,14 +34,16 @@ of components like `rtk-name-tag`, `rtk-audio-visualizer` or any other component
 ### With Properties
 
 ```html
-<rtk-participant-tile> </rtk-participant-tile>
+<rtk-participant-tile>
+</rtk-participant-tile>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant-tile");
+  const el = document.querySelector("rtk-participant-tile");
 
-	el.isPreview = true;
-	el.meeting = meeting;
+  el.isPreview= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
index b353795e7b1d39f..bb8ac1dd6367703 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participant.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-participant component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
@@ -33,14 +32,16 @@ You can perform privileged actions on the participant too.
 ### With Properties
 
 ```html
-<rtk-participant> </rtk-participant>
+<rtk-participant>
+</rtk-participant>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participant");
+  const el = document.querySelector("rtk-participant");
 
-	el.meeting = meeting;
-	el.participant = participant;
+  el.meeting= meeting
+  el.participant= participant
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
index 60421301e0a2c48..1f8797c35adb77e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-audio.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-audio component (Web Components
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A component which plays all the audio from participants and screenshares.
 ### With Properties
 
 ```html
-<rtk-participants-audio> </rtk-participants-audio>
+<rtk-participants-audio>
+</rtk-participants-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-audio");
+  const el = document.querySelector("rtk-participants-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
index fd655a61d22ef33..01d0f27f271ce7e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-list.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-participants-stage-list component (Web Compon
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -34,14 +33,17 @@ run privileged actions on each participant according to your permissions.
 ### With Properties
 
 ```html
-<rtk-participants-stage-list search="example"> </rtk-participants-stage-list>
+<rtk-participants-stage-list
+ search="example">
+</rtk-participants-stage-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-stage-list");
+  const el = document.querySelector("rtk-participants-stage-list");
 
-	el.hideHeader = true;
-	el.meeting = meeting;
+  el.hideHeader= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
index 7032a7bf6eae0d8..963520bc7e53b54 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-stage-queue.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-stage-queue component (Web Compo
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-stage-queue size="md"> </rtk-participants-stage-queue>
+<rtk-participants-stage-queue
+ size="md">
+</rtk-participants-stage-queue>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-stage-queue");
+  const el = document.querySelector("rtk-participants-stage-queue");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
index a9ac8f17b8c789a..bb79d669d9e7c10 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-viewer-list.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-participants-viewer-list component (Web Compo
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-viewer-list search="example"> </rtk-participants-viewer-list>
+<rtk-participants-viewer-list
+ search="example">
+</rtk-participants-viewer-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-viewer-list");
+  const el = document.querySelector("rtk-participants-viewer-list");
 
-	el.hideHeader = true;
-	el.meeting = meeting;
+  el.hideHeader= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
index f2090258605a509..bb42583235f5ab8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants-waiting-list.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-participants-waiting-list component (Web Comp
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-participants-waiting-list size="md"> </rtk-participants-waiting-list>
+<rtk-participants-waiting-list
+ size="md">
+</rtk-participants-waiting-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants-waiting-list");
+  const el = document.querySelector("rtk-participants-waiting-list");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
index 746ec51d0d8660b..1ba0901c553c486 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-participants.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-participants component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -32,13 +31,16 @@ run privileged actions on each participant according to your permissions.
 ### With Properties
 
 ```html
-<rtk-participants size="md"> </rtk-participants>
+<rtk-participants
+ size="md">
+</rtk-participants>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-participants");
+  const el = document.querySelector("rtk-participants");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
index 150b3a750c1b030..57a566accadd160 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-permissions-message.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-permissions-message component (Web Components
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,15 @@ information.
 ### With Properties
 
 ```html
-<rtk-permissions-message> </rtk-permissions-message>
+<rtk-permissions-message>
+</rtk-permissions-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-permissions-message");
+  const el = document.querySelector("rtk-permissions-message");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
index 5d603b6e59daf8b..a125dffe72ae892 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-pinned-message-selector.mdx
@@ -5,14 +5,13 @@ description: API reference for rtk-pinned-message-selector component (Web Compon
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -25,13 +24,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-pinned-message-selector> </rtk-pinned-message-selector>
+<rtk-pinned-message-selector>
+</rtk-pinned-message-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-pinned-message-selector");
+  const el = document.querySelector("rtk-pinned-message-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
index 2d619085455442a..35331c64a8d6e7d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugin-main.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-plugin-main component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -28,13 +27,15 @@ A component which loads a plugin.
 ### With Properties
 
 ```html
-<rtk-plugin-main> </rtk-plugin-main>
+<rtk-plugin-main>
+</rtk-plugin-main>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-plugin-main");
+  const el = document.querySelector("rtk-plugin-main");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
index 6461be9451e19f9..162f337bb6592f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-plugins.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-plugins component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ and ability to enable or disable plugins.
 ### With Properties
 
 ```html
-<rtk-plugins size="md"> </rtk-plugins>
+<rtk-plugins
+ size="md">
+</rtk-plugins>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-plugins");
+  const el = document.querySelector("rtk-plugins");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
index 3e1e182ae6b3e03..0272f65d9b3b48e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll-form.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-poll-form component (Web Components (HTML) Li
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ A component that lets you create a poll.
 ### With Properties
 
 ```html
-<rtk-poll-form> </rtk-poll-form>
+<rtk-poll-form>
+</rtk-poll-form>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-poll-form");
+  const el = document.querySelector("rtk-poll-form");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
index 74d94c512226da3..c7c9985644e098f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-poll.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-poll component (Web Components (HTML) Library
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,11 +29,15 @@ Shows a poll where a user can vote.
 ### With Properties
 
 ```html
-<rtk-poll self="example"> </rtk-poll>
+<rtk-poll
+ self="example">
+</rtk-poll>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-poll");
+  const el = document.querySelector("rtk-poll");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
index 98f0ca7892e6576..bef8f30b7725c38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-polls.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-polls component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ the ability to enable or disable them as per their permissions.
 ### With Properties
 
 ```html
-<rtk-polls size="md"> </rtk-polls>
+<rtk-polls
+ size="md">
+</rtk-polls>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-polls");
+  const el = document.querySelector("rtk-polls");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
index 4d369e04d632069..d30318ecc55e3a5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-indicator.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-recording-indicator component (Web Components
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,13 +28,16 @@ It will not render anything if no recording is taking place.
 ### With Properties
 
 ```html
-<rtk-recording-indicator size="md"> </rtk-recording-indicator>
+<rtk-recording-indicator
+ size="md">
+</rtk-recording-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-recording-indicator");
+  const el = document.querySelector("rtk-recording-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
index a98b211032c1cbb..ec59e9f219e9f7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-recording-toggle.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-recording-toggle component (Web Components (H
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ who don't have the permission to record a meeting.
 ### With Properties
 
 ```html
-<rtk-recording-toggle size="md"> </rtk-recording-toggle>
+<rtk-recording-toggle
+ size="md">
+</rtk-recording-toggle>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-recording-toggle");
+  const el = document.querySelector("rtk-recording-toggle");
 
-	el.disabled = true;
-	el.meeting = meeting;
+  el.disabled= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
index 1f9320fd4015e72..a90c136dff9c22a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-screenshare-view.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-screenshare-view component (Web Components (H
 products:
   - realtime
 ---
-
 A component which plays a participant's screenshared video.
-It also allows for placement of other components similar to `rtk-participant-tile`.
-This component will not render anything if the participant hasn't start screensharing.
+ It also allows for placement of other components similar to `rtk-participant-tile`.
+ This component will not render anything if the participant hasn't start screensharing.
 
 ## Properties
 
-| Property               | Type                                                                                                                     | Required | Default           | Description             |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------- | ----------------------- |
-| `hideFullScreenButton` | `boolean`                                                                                                                | ✅       | -                 | Hide full screen button |
-| `iconPack`             | `IconPack`                                                                                                               | ❌       | `defaultIconPack` | Icon pack               |
-| `meeting`              | `Meeting`                                                                                                                | ✅       | -                 | Meeting object          |
-| `nameTagPosition`      | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅       | -                 | Position of name tag    |
-| `participant`          | `Peer`                                                                                                                   | ✅       | -                 | Participant object      |
-| `size`                 | `Size`                                                                                                                   | ✅       | -                 | Size                    |
-| `t`                    | `RtkI18n`                                                                                                                | ❌       | `useLanguage()`   | Language                |
-| `variant`              | `'solid' \| 'gradient'`                                                                                                  | ✅       | -                 | Variant                 |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideFullScreenButton` | `boolean` | ✅ | - | Hide full screen button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `nameTagPosition` | `\| 'bottom-left'     \| 'bottom-right'     \| 'bottom-center'     \| 'top-left'     \| 'top-right'     \| 'top-center'` | ✅ | - | Position of name tag |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'gradient'` | ✅ | - | Variant |
 
 ## Usage Examples
 
@@ -34,14 +33,16 @@ This component will not render anything if the participant hasn't start screensh
 ### With Properties
 
 ```html
-<rtk-screenshare-view> </rtk-screenshare-view>
+<rtk-screenshare-view>
+</rtk-screenshare-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-screenshare-view");
+  const el = document.querySelector("rtk-screenshare-view");
 
-	el.hideFullScreenButton = true;
-	el.meeting = meeting;
+  el.hideFullScreenButton= true;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
index eb030d8fd7c3939..be7787328820925 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-audio.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-audio component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-settings-audio size="md"> </rtk-settings-audio>
+<rtk-settings-audio
+ size="md">
+</rtk-settings-audio>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings-audio");
+  const el = document.querySelector("rtk-settings-audio");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
index 90b1ddf72d04d58..523484ecbd3ff73 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings-video.mdx
@@ -5,27 +5,25 @@ description: API reference for rtk-settings-video component (Web Components (HTM
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -38,13 +36,16 @@ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
 ### With Properties
 
 ```html
-<rtk-settings-video size="md"> </rtk-settings-video>
+<rtk-settings-video
+ size="md">
+</rtk-settings-video>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings-video");
+  const el = document.querySelector("rtk-settings-video");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
index 5dd39a1a89173b9..4dd3286895b7a97 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-settings.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-settings component (Web Components (HTML) Lib
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,16 @@ as well as see your connection quality.
 ### With Properties
 
 ```html
-<rtk-settings size="md"> </rtk-settings>
+<rtk-settings
+ size="md">
+</rtk-settings>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-settings");
+  const el = document.querySelector("rtk-settings");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
index 2f276604dd912f8..622524c4fd4f8c8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-setup-screen.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-setup-screen component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,16 @@ and media settings.
 ### With Properties
 
 ```html
-<rtk-setup-screen size="md"> </rtk-setup-screen>
+<rtk-setup-screen
+ size="md">
+</rtk-setup-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-setup-screen");
+  const el = document.querySelector("rtk-setup-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
index 8902143e96624a4..f7ebcc96c331885 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar-ui.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-sidebar-ui component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
@@ -30,14 +29,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-sidebar-ui currentTab="example"> </rtk-sidebar-ui>
+<rtk-sidebar-ui
+ currentTab="example">
+</rtk-sidebar-ui>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-sidebar-ui");
+  const el = document.querySelector("rtk-sidebar-ui");
 
-	el.focusCloseButton = true;
-	el.hideCloseAction = true;
+  el.focusCloseButton= true;
+  el.hideCloseAction= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
index a22797273800cff..d03131c5d572243 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-sidebar.mdx
@@ -5,23 +5,22 @@ description: API reference for rtk-sidebar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
@@ -34,14 +33,16 @@ you can customize which sections you want, and which section you want as the def
 ### With Properties
 
 ```html
-<rtk-sidebar> </rtk-sidebar>
+<rtk-sidebar>
+</rtk-sidebar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-sidebar");
+  const el = document.querySelector("rtk-sidebar");
 
-	el.enabledSections = [];
-	el.meeting = meeting;
+  el.enabledSections= [];
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
index 1614ba1605368b3..222b8ffafe1e97e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-simple-grid.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-simple-grid component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -33,14 +32,17 @@ A grid component which renders only the participants in a simple grid.
 ### With Properties
 
 ```html
-<rtk-simple-grid aspectRatio="example"> </rtk-simple-grid>
+<rtk-simple-grid
+ aspectRatio="example">
+</rtk-simple-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-simple-grid");
+  const el = document.querySelector("rtk-simple-grid");
 
-	el.gap = 42;
-	el.meeting = meeting;
+  el.gap= 42;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
index ee3244f04afe45c..1c3c4ff1ad54559 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-speaker-selector.mdx
@@ -5,28 +5,26 @@ description: API reference for rtk-speaker-selector component (Web Components (H
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
@@ -39,13 +37,16 @@ Emits `rtkStateUpdate` event with data for muting notification sounds:
 ### With Properties
 
 ```html
-<rtk-speaker-selector size="md"> </rtk-speaker-selector>
+<rtk-speaker-selector
+ size="md">
+</rtk-speaker-selector>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-speaker-selector");
+  const el = document.querySelector("rtk-speaker-selector");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
index 729aa072d8e8358..1b2a10a9aa431a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spinner.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spinner component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
@@ -26,11 +25,15 @@ A component which shows an animating spinner.
 ### With Properties
 
 ```html
-<rtk-spinner size="md"> </rtk-spinner>
+<rtk-spinner
+ size="md">
+</rtk-spinner>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spinner");
+  const el = document.querySelector("rtk-spinner");
+
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
index 0aba1ad132414cc..feaee337d8349f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-grid.mdx
@@ -5,29 +5,27 @@ description: API reference for rtk-spotlight-grid component (Web Components (HTM
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -40,13 +38,17 @@ You can customize the layout to a `column` view, by default is is `row`.
 ### With Properties
 
 ```html
-<rtk-spotlight-grid aspectRatio="example" gridSize="md"> </rtk-spotlight-grid>
+<rtk-spotlight-grid
+ aspectRatio="example"
+ gridSize="md">
+</rtk-spotlight-grid>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spotlight-grid");
+  const el = document.querySelector("rtk-spotlight-grid");
 
-	el.gap = 42;
+  el.gap= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
index db3971dcecc6fba..fb0fcf76dbe0835 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-spotlight-indicator.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-spotlight-indicator component (Web Components
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-spotlight-indicator size="md"> </rtk-spotlight-indicator>
+<rtk-spotlight-indicator
+ size="md">
+</rtk-spotlight-indicator>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-spotlight-indicator");
+  const el = document.querySelector("rtk-spotlight-indicator");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
index 99bc88ba74ef425..0f37d1d696ab3f4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-stage.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-stage component (Web Components (HTML) Librar
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -27,13 +26,15 @@ the `grid` and `sidebar` components.
 ### With Properties
 
 ```html
-<rtk-stage> </rtk-stage>
+<rtk-stage>
+</rtk-stage>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-stage");
+  const el = document.querySelector("rtk-stage");
 
-	el.iconPack = defaultIconPack;
+  el.iconPack= defaultIconPack
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
index cd5071fb1a445d1..899e19c8037f8c5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-switch.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-switch component (Web Components (HTML) Libra
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ A switch component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-switch> </rtk-switch>
+<rtk-switch>
+</rtk-switch>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-switch");
+  const el = document.querySelector("rtk-switch");
 
-	el.checked = true;
-	el.disabled = true;
-	el.readonly = true;
+  el.checked= true;
+  el.disabled= true;
+  el.readonly= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
index 0eb2929868dce57..37b7c05e987b351 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tab-bar.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-tab-bar component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-tab-bar> </rtk-tab-bar>
+<rtk-tab-bar>
+</rtk-tab-bar>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-tab-bar");
+  const el = document.querySelector("rtk-tab-bar");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
index 22603bbe1ca64f7..47adf5034bc93ca 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-composer-view.mdx
@@ -5,22 +5,21 @@ description: API reference for rtk-text-composer-view component (Web Components
 products:
   - realtime
 ---
-
 A component which renders a text composer
 
 ## Properties
 
-| Property            | Type                              | Required | Default           | Description                                   |
-| ------------------- | --------------------------------- | -------- | ----------------- | --------------------------------------------- |
-| `disabled`          | `boolean`                         | ✅       | -                 | Disable the text input (default = false)      |
-| `iconPack`          | `IconPack1`                       | ❌       | `defaultIconPack` | Icon pack                                     |
-| `keyDownHandler`    | `(e: KeyboardEvent)`              | ✅       | -                 | Keydown event handler function                |
-| `maxLength`         | `number`                          | ✅       | -                 | Max length for text input                     |
-| `placeholder`       | `string`                          | ✅       | -                 | Placeholder text                              |
-| `rateLimitBreached` | `boolean`                         | ✅       | -                 | Boolean to indicate if rate limit is breached |
-| `setText`           | `(text: string, focus?: boolean)` | ❌       | -                 | Sets value of the text input                  |
-| `t`                 | `RtkI18n1`                        | ❌       | `useLanguage()`   | Language                                      |
-| `value`             | `string`                          | ✅       | -                 | Default value for text input                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the text input (default = false) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `keyDownHandler` | `(e: KeyboardEvent)` | ✅ | - | Keydown event handler function |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `placeholder` | `string` | ✅ | - | Placeholder text |
+| `rateLimitBreached` | `boolean` | ✅ | - | Boolean to indicate if rate limit is breached |
+| `setText` | `(text: string, focus?: boolean)` | ❌ | - | Sets value of the text input |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `value` | `string` | ✅ | - | Default value for text input |
 
 ## Usage Examples
 
@@ -33,14 +32,16 @@ A component which renders a text composer
 ### With Properties
 
 ```html
-<rtk-text-composer-view> </rtk-text-composer-view>
+<rtk-text-composer-view>
+</rtk-text-composer-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-composer-view");
+  const el = document.querySelector("rtk-text-composer-view");
 
-	el.disabled = true;
-	el.maxLength = 42;
+  el.disabled= true;
+  el.maxLength= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
index c7802ea87ac4cbc..4e15cd5f1fcdb7f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message-view.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-text-message-view component (Web Components (
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
@@ -26,13 +25,16 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message-view text="example"> </rtk-text-message-view>
+<rtk-text-message-view
+ text="example">
+</rtk-text-message-view>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-message-view");
+  const el = document.querySelector("rtk-text-message-view");
 
-	el.isMarkdown = true;
+  el.isMarkdown= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
index db080a025087bed..6163072c5b51c71 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-text-message.mdx
@@ -5,20 +5,19 @@ description: API reference for rtk-text-message component (Web Components (HTML)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -31,13 +30,15 @@ A component which renders a text message from chat.
 ### With Properties
 
 ```html
-<rtk-text-message> </rtk-text-message>
+<rtk-text-message>
+</rtk-text-message>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-text-message");
+  const el = document.querySelector("rtk-text-message");
 
-	el.isContinued = true;
+  el.isContinued= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
index ff346f3104717b1..6e38e8bb3887731 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-tooltip.mdx
@@ -5,21 +5,20 @@ description: API reference for rtk-tooltip component (Web Components (HTML) Libr
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
@@ -32,14 +31,16 @@ Tooltip component which follows RTK Design System.
 ### With Properties
 
 ```html
-<rtk-tooltip> </rtk-tooltip>
+<rtk-tooltip>
+</rtk-tooltip>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-tooltip");
+  const el = document.querySelector("rtk-tooltip");
 
-	el.delay = 42;
-	el.disabled = true;
+  el.delay= 42;
+  el.disabled= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
index 5ed0883121e7db1..f0631ca86b905bd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcript.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-transcript component (Web Components (HTML) L
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ You need to remove the element after you receive the
 ### With Properties
 
 ```html
-<rtk-transcript transcript="example"> </rtk-transcript>
+<rtk-transcript
+ transcript="example">
+</rtk-transcript>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-transcript");
+  const el = document.querySelector("rtk-transcript");
 
-	el.transcript = {};
+  el.transcript= {};
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
index c734652bd0fbcd1..f75a986f1cfd9de 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-transcripts.mdx
@@ -5,19 +5,18 @@ description: API reference for rtk-transcripts component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -30,13 +29,15 @@ There are also certain limits which you can set as well.
 ### With Properties
 
 ```html
-<rtk-transcripts> </rtk-transcripts>
+<rtk-transcripts>
+</rtk-transcripts>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-transcripts");
+  const el = document.querySelector("rtk-transcripts");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
index 3387ed120b39d4e..041148907fcb623 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-ui-provider.mdx
@@ -5,18 +5,17 @@ description: API reference for rtk-ui-provider component (Web Components (HTML)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
@@ -29,15 +28,17 @@ products:
 ### With Properties
 
 ```html
-<rtk-ui-provider> </rtk-ui-provider>
+<rtk-ui-provider>
+</rtk-ui-provider>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-ui-provider");
+  const el = document.querySelector("rtk-ui-provider");
 
-	el.config = defaultUiConfig;
-	el.mode = meeting;
-	el.showSetupScreen = true;
+  el.config= defaultUiConfig
+  el.mode= meeting
+  el.showSetupScreen= true;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
index 42c4225721997e0..4d041852272b5c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-viewer-count.mdx
@@ -5,17 +5,16 @@ description: API reference for rtk-viewer-count component (Web Components (HTML)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
@@ -28,13 +27,16 @@ A component which shows count of total joined participants in a meeting.
 ### With Properties
 
 ```html
-<rtk-viewer-count variant="primary"> </rtk-viewer-count>
+<rtk-viewer-count
+ variant="primary">
+</rtk-viewer-count>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-viewer-count");
+  const el = document.querySelector("rtk-viewer-count");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
index d551b47a44c6b52..9856cd393b4f8d3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-virtualized-participant-list.mdx
@@ -5,16 +5,15 @@ description: API reference for rtk-virtualized-participant-list component (Web C
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
@@ -27,14 +26,16 @@ products:
 ### With Properties
 
 ```html
-<rtk-virtualized-participant-list> </rtk-virtualized-participant-list>
+<rtk-virtualized-participant-list>
+</rtk-virtualized-participant-list>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-virtualized-participant-list");
+  const el = document.querySelector("rtk-virtualized-participant-list");
 
-	el.bufferedItemsCount = 42;
-	el.itemHeight = 42;
+  el.bufferedItemsCount= 42;
+  el.itemHeight= 42;
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
index f65c231d33c3ab5..5486f52a36737c7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/core/rtk-waiting-screen.mdx
@@ -5,15 +5,14 @@ description: API reference for rtk-waiting-screen component (Web Components (HTM
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
@@ -26,13 +25,15 @@ products:
 ### With Properties
 
 ```html
-<rtk-waiting-screen> </rtk-waiting-screen>
+<rtk-waiting-screen>
+</rtk-waiting-screen>
 ```
 
+
 ```html
 <script>
-	const el = document.querySelector("rtk-waiting-screen");
+  const el = document.querySelector("rtk-waiting-screen");
 
-	el.meeting = meeting;
+  el.meeting= meeting
 </script>
 ```
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
index 248a49136afe991..301d8b7d3bff009 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react-native/RtkMenuItem.mdx
@@ -10,11 +10,11 @@ A pressable menu item within a menu.
 
 ## Properties
 
-| Property   | Type                           | Required | Default | Description            |
-| ---------- | ------------------------------ | -------- | ------- | ---------------------- |
-| `children` | `ReactNode`                    | ✅       | -       | Menu item content      |
-| `onClick`  | `(ev) => {}`                   | ❌       | -       | Press handler callback |
-| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'` | ❌       | -       | Size variant           |
+| Property   | Type                                  | Required | Default | Description            |
+| ---------- | ------------------------------------- | -------- | ------- | ---------------------- |
+| `children` | `ReactNode`                           | ✅       | -       | Menu item content      |
+| `onClick`  | `(ev) => {}` | ❌       | -       | Press handler callback |
+| `size`     | `'lg' \| 'md' \| 'sm' \| 'xl'`        | ❌       | -       | Size variant           |
 
 ## Usage Examples
 
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
index 422840190bc663c..0ec727fad6c4379 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAi.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkAi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
-| `view`     | `AIView`   | ✅       | -                       | View type      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `AIView` | ✅ | - | View type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAi } from "@cloudflare/realtimekit-react-ui";
+import { RtkAi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAi />;
+  return <RtkAi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAi } from "@cloudflare/realtimekit-react-ui";
+import { RtkAi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAi meeting={meeting} size="md" view={aiview} />;
+  return (
+    <RtkAi
+      meeting={meeting}
+      size="md"
+      view={aiview}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
index 396561410fcfa72..8545071a098a60f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkAiToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiToggle />;
+  return <RtkAiToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkAiToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
index 676a14f2675ae81..ef4f69f64146916 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAiTranscriptions.mdx
@@ -5,33 +5,38 @@ description: API reference for RtkAiTranscriptions component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type           | Required | Default         | Description            |
-| ----------------------- | -------------- | -------- | --------------- | ---------------------- |
-| `initialTranscriptions` | `Transcript[]` | ✅       | -               | Initial transcriptions |
-| `meeting`               | `Meeting`      | ✅       | -               | Meeting object         |
-| `t`                     | `RtkI18n`      | ❌       | `useLanguage()` | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `initialTranscriptions` | `Transcript[]` | ✅ | - | Initial transcriptions |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiTranscriptions />;
+  return <RtkAiTranscriptions />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAiTranscriptions } from "@cloudflare/realtimekit-react-ui";
+import { RtkAiTranscriptions } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAiTranscriptions initialTranscriptions={[]} meeting={meeting} />;
+  return (
+    <RtkAiTranscriptions
+      initialTranscriptions={[]}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
index 75ece5db8d70097..5a8f8fedf34406a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioGrid.mdx
@@ -5,39 +5,43 @@ description: API reference for RtkAudioGrid component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description                      |
-| ---------- | ----------- | -------- | ----------------- | -------------------------------- |
-| `config`   | `UIConfig1` | ✅       | -                 | Config                           |
-| `hideSelf` | `boolean`   | ✅       | -                 | Whether to hide self in the grid |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon Pack                        |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting                          |
-| `size`     | `Size1`     | ✅       | -                 | Size                             |
-| `states`   | `States1`   | ✅       | -                 | States                           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `hideSelf` | `boolean` | ✅ | - | Whether to hide self in the grid |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioGrid />;
+  return <RtkAudioGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioGrid config={defaultUiConfig} hideSelf={true} meeting={meeting} />
-	);
+  return (
+    <RtkAudioGrid
+      config={defaultUiConfig}
+      hideSelf={true}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
index 5c8a03c08f715b6..71a65e966b788a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioTile.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkAudioTile component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property      | Type        | Required | Default           | Description        |
-| ------------- | ----------- | -------- | ----------------- | ------------------ |
-| `config`      | `UIConfig`  | ✅       | -                 | Config             |
-| `iconPack`    | `IconPack1` | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`     | `Meeting`   | ✅       | -                 | Meeting            |
-| `participant` | `Peer`      | ✅       | -                 | Participant object |
-| `size`        | `Size`      | ✅       | -                 | Size               |
-| `states`      | `States1`   | ✅       | -                 | States             |
-| `t`           | `RtkI18n1`  | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioTile />;
+  return <RtkAudioTile />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioTile } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioTile } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioTile
-			config={defaultUiConfig}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkAudioTile
+      config={defaultUiConfig}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
index 33a40cf994b8247..9f5b3941640b98a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAudioVisualizer.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkAudioVisualizer component (React Library)
 products:
   - realtime
 ---
-
 An audio visualizer component which visualizes a participants audio.
-Commonly used inside `rtk-name-tag`.
+ Commonly used inside `rtk-name-tag`.
 
 ## Properties
 
-| Property        | Type                     | Required | Default           | Description                                                                                   |
-| --------------- | ------------------------ | -------- | ----------------- | --------------------------------------------------------------------------------------------- |
-| `hideMuted`     | `boolean`                | ✅       | -                 | Hide the visualizer if audio is muted                                                         |
-| `iconPack`      | `IconPack`               | ❌       | `defaultIconPack` | Icon pack                                                                                     |
-| `isScreenShare` | `boolean`                | ✅       | -                 | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
-| `participant`   | `Peer`                   | ✅       | -                 | Participant object                                                                            |
-| `size`          | `Size`                   | ✅       | -                 | Size                                                                                          |
-| `t`             | `RtkI18n`                | ❌       | `useLanguage()`   | Language                                                                                      |
-| `variant`       | `AudioVisualizerVariant` | ✅       | -                 | Variant                                                                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hideMuted` | `boolean` | ✅ | - | Hide the visualizer if audio is muted |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Audio visualizer for screensharing, it will use screenShareTracks.audio instead of audioTrack |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AudioVisualizerVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAudioVisualizer />;
+  return <RtkAudioVisualizer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAudioVisualizer } from "@cloudflare/realtimekit-react-ui";
+import { RtkAudioVisualizer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkAudioVisualizer
-			hideMuted={true}
-			isScreenShare={true}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkAudioVisualizer
+      hideMuted={true}
+      isScreenShare={true}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
index b48ab891f56912c..0e6ffdb430de443 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkAvatar.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkAvatar component (React Library)
 products:
   - realtime
 ---
-
 Avatar component which renders a participant's image or their initials.
 
 ## Properties
 
-| Property      | Type                                                                 | Required | Default           | Description        |
-| ------------- | -------------------------------------------------------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`                                                           | ❌       | `defaultIconPack` | Icon pack          |
-| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅       | -                 | Participant object |
-| `size`        | `Size`                                                               | ✅       | -                 | Size               |
-| `t`           | `RtkI18n`                                                            | ❌       | `useLanguage()`   | Language           |
-| `variant`     | `AvatarVariant`                                                      | ✅       | -                 | Avatar type        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `participant` | `Peer \| WaitlistedParticipant \| { name: string; picture: string }` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `AvatarVariant` | ✅ | - | Avatar type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
+import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAvatar />;
+  return <RtkAvatar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkAvatar } from "@cloudflare/realtimekit-react-ui";
+import { RtkAvatar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkAvatar participant="example" size="md" variant="circular" />;
+  return (
+    <RtkAvatar
+      participant="example"
+      size="md"
+      variant="circular"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
index a8884efc78197e3..487dc6287788cc7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomManager.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkBreakoutRoomManager component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property                | Type                 | Required | Default           | Description                      |
-| ----------------------- | -------------------- | -------- | ----------------- | -------------------------------- |
-| `allowDelete`           | `boolean`            | ✅       | -                 | allow room delete                |
-| `assigningParticipants` | `boolean`            | ✅       | -                 | Enable updating participants     |
-| `defaultExpanded`       | `boolean`            | ✅       | -                 | display expanded card by default |
-| `iconPack`              | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                        |
-| `isDragMode`            | `boolean`            | ✅       | -                 | Drag mode                        |
-| `meeting`               | `Meeting`            | ✅       | -                 | Meeting object                   |
-| `mode`                  | `'edit' \| 'create'` | ✅       | -                 | Mode in which selector is used   |
-| `room`                  | `DraftMeeting`       | ✅       | -                 | Connected Room Config Object     |
-| `states`                | `States`             | ✅       | -                 | States object                    |
-| `t`                     | `RtkI18n`            | ❌       | `useLanguage()`   | Language                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `allowDelete` | `boolean` | ✅ | - | allow room delete |
+| `assigningParticipants` | `boolean` | ✅ | - | Enable updating participants |
+| `defaultExpanded` | `boolean` | ✅ | - | display expanded card by default |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isDragMode` | `boolean` | ✅ | - | Drag mode |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `'edit' \| 'create'` | ✅ | - | Mode in which selector is used |
+| `room` | `DraftMeeting` | ✅ | - | Connected Room Config Object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomManager />;
+  return <RtkBreakoutRoomManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomManager
-			allowDelete={true}
-			assigningParticipants={true}
-			defaultExpanded={true}
-		/>
-	);
+  return (
+    <RtkBreakoutRoomManager
+      allowDelete={true}
+      assigningParticipants={true}
+      defaultExpanded={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
index 2004a147afe14a6..fb2341581602302 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomParticipants.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkBreakoutRoomParticipants component (React Libr
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                 | Type       | Required | Default           | Description           |
-| ------------------------ | ---------- | -------- | ----------------- | --------------------- |
-| `iconPack`               | `IconPack` | ❌       | `defaultIconPack` | Icon pack             |
-| `meeting`                | `Meeting`  | ✅       | -                 | Meeting object        |
-| `participantIds`         | `string[]` | ✅       | -                 | Participant ids       |
-| `selectedParticipantIds` | `string[]` | ✅       | -                 | selected participants |
-| `t`                      | `RtkI18n`  | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participantIds` | `string[]` | ✅ | - | Participant ids |
+| `selectedParticipantIds` | `string[]` | ✅ | - | selected participants |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomParticipants />;
+  return <RtkBreakoutRoomParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomParticipants
-			meeting={meeting}
-			participantIds="example"
-			selectedParticipantIds="example"
-		/>
-	);
+  return (
+    <RtkBreakoutRoomParticipants
+      meeting={meeting}
+      participantIds="example"
+      selectedParticipantIds="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
index dcbcea2d4770056..50f3260dcf7a651 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsManager.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkBreakoutRoomsManager component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsManager />;
+  return <RtkBreakoutRoomsManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsManager meeting={meeting} />;
+  return (
+    <RtkBreakoutRoomsManager
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
index 437ddd1710ebf57..380c96f9f1541ef 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBreakoutRoomsToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkBreakoutRoomsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of breakout rooms.
-You need to pass the `meeting` object to it.
+ You need to pass the `meeting` object to it.
 
 ## Properties
 
-| Property   | Type                | Required | Default | Description    |
-| ---------- | ------------------- | -------- | ------- | -------------- |
-| `iconPack` | `IconPack`          | ✅       | -       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -       | Meeting object |
-| `size`     | `Size`              | ✅       | -       | Size           |
-| `states`   | `States`            | ✅       | -       | States object  |
-| `t`        | `RtkI18n`           | ✅       | -       | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ✅ | - | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ✅ | - | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBreakoutRoomsToggle />;
+  return <RtkBreakoutRoomsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBreakoutRoomsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkBreakoutRoomsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkBreakoutRoomsToggle
-			iconPack={defaultIconPack}
-			meeting={meeting}
-			size="md"
-		/>
-	);
+  return (
+    <RtkBreakoutRoomsToggle
+      iconPack={defaultIconPack}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
index 2117f12536528dd..856b11cff1b3d13 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkBroadcastMessageModal.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkBroadcastMessageModal component (React Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States1`  | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBroadcastMessageModal />;
+  return <RtkBroadcastMessageModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkBroadcastMessageModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkBroadcastMessageModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkBroadcastMessageModal meeting={meeting} />;
+  return (
+    <RtkBroadcastMessageModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
index 4662a4cb4703613..5be7a8515fbc268 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkButton.mdx
@@ -5,38 +5,44 @@ description: API reference for RtkButton component (React Library)
 products:
   - realtime
 ---
-
 A button that follows RTK Design System.
 
 ## Properties
 
-| Property   | Type                        | Required | Default | Description                          |
-| ---------- | --------------------------- | -------- | ------- | ------------------------------------ |
-| `disabled` | `boolean`                   | ✅       | -       | Where the button is disabled or not  |
-| `kind`     | `ButtonKind`                | ✅       | -       | Button type                          |
-| `reverse`  | `boolean`                   | ✅       | -       | Whether to reverse order of children |
-| `size`     | `Size`                      | ✅       | -       | Size                                 |
-| `type`     | `HTMLButtonElement['type']` | ✅       | -       | Button type                          |
-| `variant`  | `ButtonVariant`             | ✅       | -       | Button variant                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Where the button is disabled or not |
+| `kind` | `ButtonKind` | ✅ | - | Button type |
+| `reverse` | `boolean` | ✅ | - | Whether to reverse order of children |
+| `size` | `Size` | ✅ | - | Size |
+| `type` | `HTMLButtonElement['type']` | ✅ | - | Button type |
+| `variant` | `ButtonVariant` | ✅ | - | Button variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkButton />;
+  return <RtkButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkButton disabled={true} kind={buttonkind} reverse={true} />;
+  return (
+    <RtkButton
+      disabled={true}
+      kind={buttonkind}
+      reverse={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
index 5bd7f5725ed45f5..5964ca5795dff5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraSelector.mdx
@@ -5,52 +5,51 @@ description: API reference for RtkCameraSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraSelector />;
+  return <RtkCameraSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkCameraSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkCameraSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
index ef0f7be9cbd784b..f32d538b0d242cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCameraToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCameraToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your camera.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraToggle />;
+  return <RtkCameraToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCameraToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCameraToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCameraToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkCameraToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
index ccb44bea4849232..4e5a7b0e9ae81e2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCaptionToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCaptionToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCaptionToggle />;
+  return <RtkCaptionToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCaptionToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkCaptionToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCaptionToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkCaptionToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
index 88044716a737a05..08109cd1a6900d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChat.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkChat component (React Library)
 products:
   - realtime
 ---
-
 Fully featured chat component with image & file upload, emoji picker and auto-scroll.
 
 ## Properties
 
-| Property    | Type        | Required | Default                 | Description    |
-| ----------- | ----------- | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`      | ✅       | -                       | Size           |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChat } from "@cloudflare/realtimekit-react-ui";
+import { RtkChat } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChat />;
+  return <RtkChat />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChat } from "@cloudflare/realtimekit-react-ui";
+import { RtkChat } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChat meeting={meeting} size="md" />;
+  return (
+    <RtkChat
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
index f71eb84400228a3..3c8a6961bebc260 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkChatComposerUi component (React Library)
 products:
   - realtime
 ---
-
 @deprecated . This component is deprecated, please use rtk-chat-composer-view instead.
 
 ## Properties
 
-| Property             | Type                                                                                                    | Required | Default           | Description                         |
-| -------------------- | ------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ----------------------------------- |
-| `canSendFiles`       | `boolean`                                                                                               | ✅       | -                 | Whether user can send file messages |
-| `canSendTextMessage` | `boolean`                                                                                               | ✅       | -                 | Whether user can send text messages |
-| `iconPack`           | `IconPack1`                                                                                             | ❌       | `defaultIconPack` | Icon pack                           |
-| `prefill`            | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌       | -                 | prefill the composer                |
-| `size`               | `Size1`                                                                                                 | ✅       | -                 | Size                                |
-| `t`                  | `RtkI18n`                                                                                               | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `prefill` | `{     suggestedReplies?: string[];     editMessage?: TextMessage;     replyMessage?: TextMessage;   }` | ❌ | - | prefill the composer |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatComposerUi />;
+  return <RtkChatComposerUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatComposerUi
-			canSendFiles={true}
-			canSendTextMessage={true}
-			size="md"
-		/>
-	);
+  return (
+    <RtkChatComposerUi
+      canSendFiles={true}
+      canSendTextMessage={true}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
index 3f5eabaf3bbce7c..2ebfa2b0d2a24e3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView.mdx
@@ -5,49 +5,49 @@ description: API reference for RtkChatComposerView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a chat composer
 
 ## Properties
 
-| Property               | Type                                          | Required | Default           | Description                             |
-| ---------------------- | --------------------------------------------- | -------- | ----------------- | --------------------------------------- |
-| `canSendFiles`         | `boolean`                                     | ✅       | -                 | Whether user can send file messages     |
-| `canSendTextMessage`   | `boolean`                                     | ✅       | -                 | Whether user can send text messages     |
-| `iconPack`             | `IconPack1`                                   | ❌       | `defaultIconPack` | Icon pack                               |
-| `inputTextPlaceholder` | `string`                                      | ✅       | -                 | Placeholder for text input              |
-| `isEditing`            | `boolean`                                     | ✅       | -                 | Sets composer to edit mode              |
-| `maxLength`            | `number`                                      | ✅       | -                 | Max length for text input               |
-| `message`              | `string`                                      | ✅       | -                 | Message to be pre-populated             |
-| `quotedMessage`        | `string`                                      | ✅       | -                 | Quote message to be displayed           |
-| `rateLimits`           | `{ period: number; maxInvocations: number; }` | ✅       | -                 | Rate limits                             |
-| `storageKey`           | `string`                                      | ✅       | -                 | Key for storing message in localStorage |
-| `t`                    | `RtkI18n1`                                    | ❌       | `useLanguage()`   | Language                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canSendFiles` | `boolean` | ✅ | - | Whether user can send file messages |
+| `canSendTextMessage` | `boolean` | ✅ | - | Whether user can send text messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `inputTextPlaceholder` | `string` | ✅ | - | Placeholder for text input |
+| `isEditing` | `boolean` | ✅ | - | Sets composer to edit mode |
+| `maxLength` | `number` | ✅ | - | Max length for text input |
+| `message` | `string` | ✅ | - | Message to be pre-populated |
+| `quotedMessage` | `string` | ✅ | - | Quote message to be displayed |
+| `rateLimits` | `{ period: number; maxInvocations: number; }` | ✅ | - | Rate limits |
+| `storageKey` | `string` | ✅ | - | Key for storing message in localStorage |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatComposerView />;
+  return <RtkChatComposerView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatComposerView } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatComposerView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatComposerView
-			canSendFiles={true}
-			canSendTextMessage={true}
-			inputTextPlaceholder="example"
-		/>
-	);
+  return (
+    <RtkChatComposerView
+      canSendFiles={true}
+      canSendTextMessage={true}
+      inputTextPlaceholder="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
index 172ac6463eae729..b8d221aa00d5d75 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatHeader.mdx
@@ -5,19 +5,19 @@ description: API reference for RtkChatHeader component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-_No properties available._
+*No properties available.*
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatHeader />;
+  return <RtkChatHeader />;
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
index 06b7622778baee0..62095db66fa56ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessage.mdx
@@ -5,49 +5,55 @@ description: API reference for RtkChatMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-message` is deprecated and will be removed soon. Use `rtk-message-view` instead.
 
 ## Properties
 
-| Property               | Type          | Required | Default           | Description                            |
-| ---------------------- | ------------- | -------- | ----------------- | -------------------------------------- |
-| `alignRight`           | `boolean`     | ✅       | -                 | aligns message to right                |
-| `canDelete`            | `boolean`     | ✅       | -                 | can delete message                     |
-| `canEdit`              | `boolean`     | ✅       | -                 | can edit message                       |
-| `canPin`               | `boolean`     | ✅       | -                 | can pin this message                   |
-| `canReply`             | `boolean`     | ✅       | -                 | can quote reply this message           |
-| `child`                | `HTMLElement` | ✅       | -                 | Child                                  |
-| `disableControls`      | `boolean`     | ✅       | -                 | disables controls                      |
-| `hideAvatar`           | `boolean`     | ✅       | -                 | hides avatar                           |
-| `iconPack`             | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                              |
-| `isContinued`          | `boolean`     | ✅       | -                 | is continued                           |
-| `isSelf`               | `boolean`     | ✅       | -                 | if sender is self                      |
-| `isUnread`             | `boolean`     | ✅       | -                 | is unread                              |
-| `leftAlign`            | `boolean`     | ✅       | -                 | Whether to left align the chat bubbles |
-| `message`              | `Message`     | ✅       | -                 | message item                           |
-| `senderDisplayPicture` | `string`      | ✅       | -                 | sender display picture url             |
-| `size`                 | `Size`        | ✅       | -                 | Size                                   |
-| `t`                    | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `alignRight` | `boolean` | ✅ | - | aligns message to right |
+| `canDelete` | `boolean` | ✅ | - | can delete message |
+| `canEdit` | `boolean` | ✅ | - | can edit message |
+| `canPin` | `boolean` | ✅ | - | can pin this message |
+| `canReply` | `boolean` | ✅ | - | can quote reply this message |
+| `child` | `HTMLElement` | ✅ | - | Child |
+| `disableControls` | `boolean` | ✅ | - | disables controls |
+| `hideAvatar` | `boolean` | ✅ | - | hides avatar |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | is continued |
+| `isSelf` | `boolean` | ✅ | - | if sender is self |
+| `isUnread` | `boolean` | ✅ | - | is unread |
+| `leftAlign` | `boolean` | ✅ | - | Whether to left align the chat bubbles |
+| `message` | `Message` | ✅ | - | message item |
+| `senderDisplayPicture` | `string` | ✅ | - | sender display picture url |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessage />;
+  return <RtkChatMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessage alignRight={true} canDelete={true} canEdit={true} />;
+  return (
+    <RtkChatMessage
+      alignRight={true}
+      canDelete={true}
+      canEdit={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
index 24dfa75d1e264c5..39be829497f47dc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUi.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkChatMessagesUi component (React Library)
 products:
   - realtime
 ---
-
 @deprecated Use `rtk-chat-messages-ui-paginated` instead.
 
 ## Properties
 
-| Property         | Type        | Required | Default           | Description                         |
-| ---------------- | ----------- | -------- | ----------------- | ----------------------------------- |
-| `canPinMessages` | `boolean`   | ✅       | -                 | Can current user pin/unpin messages |
-| `iconPack`       | `IconPack1` | ❌       | `defaultIconPack` | Icon pack                           |
-| `messages`       | `Chat[]`    | ✅       | -                 | Chat Messages                       |
-| `selectedGroup`  | `string`    | ✅       | -                 | Selected group key                  |
-| `selfUserId`     | `string`    | ✅       | -                 | User ID of self user                |
-| `size`           | `Size1`     | ✅       | -                 | Size                                |
-| `t`              | `RtkI18n`   | ❌       | `useLanguage()`   | Language                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `canPinMessages` | `boolean` | ✅ | - | Can current user pin/unpin messages |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `messages` | `Chat[]` | ✅ | - | Chat Messages |
+| `selectedGroup` | `string` | ✅ | - | Selected group key |
+| `selfUserId` | `string` | ✅ | - | User ID of self user |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessagesUi />;
+  return <RtkChatMessagesUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatMessagesUi
-			canPinMessages={true}
-			messages={[]}
-			selectedGroup="example"
-		/>
-	);
+  return (
+    <RtkChatMessagesUi
+      canPinMessages={true}
+      messages={[]}
+      selectedGroup="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
index 5891af64b276945..2050ab5a26bc247 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkChatMessagesUiPaginated component (React Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property               | Type                  | Required | Default           | Description                                                                                      |
-| ---------------------- | --------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------ |
-| `iconPack`             | `IconPack`            | ❌       | `defaultIconPack` | Icon pack                                                                                        |
-| `meeting`              | `Meeting`             | ✅       | -                 | Meeting object                                                                                   |
-| `privateChatRecipient` | `Participant \| null` | ✅       | -                 | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
-| `size`                 | `Size`                | ✅       | -                 | Size                                                                                             |
-| `t`                    | `RtkI18n`             | ❌       | `useLanguage()`   | Language                                                                                         |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `privateChatRecipient` | `Participant \| null` | ✅ | - | Selected recipient for private chat; when unset, messages are loaded for public chat (Everyone). |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatMessagesUiPaginated />;
+  return <RtkChatMessagesUiPaginated />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatMessagesUiPaginated } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatMessagesUiPaginated } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatMessagesUiPaginated
-			meeting={meeting}
-			privateChatRecipient={participant | null}
-			size="md"
-		/>
-	);
+  return (
+    <RtkChatMessagesUiPaginated
+      meeting={meeting}
+      privateChatRecipient={participant | null}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
index 7b498cd1db28fe1..8218e3a1de98dcc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSearchResults.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkChatSearchResults component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-chat-search-results` is deprecated and will be removed soon. Use `rtk-chat-messages-ui-paginated` instead. -
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description    |
-| ----------- | ----------- | -------- | ----------------- | -------------- |
-| `channelId` | `string`    | ✅       | -                 | Channel id     |
-| `iconPack`  | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`   | `Meeting`   | ✅       | -                 | Meeting object |
-| `query`     | `string`    | ✅       | -                 | Search query   |
-| `t`         | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `channelId` | `string` | ✅ | - | Channel id |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `query` | `string` | ✅ | - | Search query |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSearchResults />;
+  return <RtkChatSearchResults />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSearchResults } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSearchResults } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatSearchResults
-			channelId="example"
-			meeting={meeting}
-			query="example"
-		/>
-	);
+  return (
+    <RtkChatSearchResults
+      channelId="example"
+      meeting={meeting}
+      query="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
index 377f279bef2cd5e..d57247e25b7d5f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkChatSelector component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type         | Required | Default                 | Description    |
-| ----------- | ------------ | -------- | ----------------------- | -------------- |
-| `config`    | `UIConfig1`  | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack`  | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`   | `Meeting`    | ✅       | -                       | Meeting object |
-| `overrides` | `Overrides1` | ❌       | `defaultOverrides`      | UI Overrides   |
-| `size`      | `Size`       | ✅       | -                       | Size           |
-| `states`    | `States1`    | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`    | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Overrides |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelector />;
+  return <RtkChatSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelector meeting={meeting} size="md" />;
+  return (
+    <RtkChatSelector
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
index 883fee41a51d0de..780c0f8d5ddc863 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelectorUi.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkChatSelectorUi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type                     | Required | Default           | Description          |
-| ----------------- | ------------------------ | -------- | ----------------- | -------------------- |
-| `groups`          | `ChatGroup[]`            | ✅       | -                 | Participants         |
-| `iconPack`        | `IconPack1`              | ❌       | `defaultIconPack` | Icon pack            |
-| `selectedGroupId` | `string`                 | ✅       | -                 | Selected participant |
-| `selfUserId`      | `string`                 | ✅       | -                 | Self User ID         |
-| `t`               | `RtkI18n`                | ❌       | `useLanguage()`   | Language             |
-| `unreadCounts`    | `Record<string, number>` | ✅       | -                 | Unread counts        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `groups` | `ChatGroup[]` | ✅ | - | Participants |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `selectedGroupId` | `string` | ✅ | - | Selected participant |
+| `selfUserId` | `string` | ✅ | - | Self User ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `unreadCounts` | `Record<string, number>` | ✅ | - | Unread counts |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatSelectorUi />;
+  return <RtkChatSelectorUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatSelectorUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatSelectorUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkChatSelectorUi
-			groups={[]}
-			selectedGroupId="example"
-			selfUserId="example"
-		/>
-	);
+  return (
+    <RtkChatSelectorUi
+      groups={[]}
+      selectedGroupId="example"
+      selfUserId="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
index 23fa8dea93d070a..93bb6e482beaa63 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkChatToggle.mdx
@@ -5,47 +5,49 @@ description: API reference for RtkChatToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of chat.
-You need to pass the `meeting` object to it to see the unread messages count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "chat";
-}
-```
+ You need to pass the `meeting` object to it to see the unread messages count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'chat' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatToggle />;
+  return <RtkChatToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkChatToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkChatToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkChatToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkChatToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
index 6671c8edffa9090..5b51f5833c33a3f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkClock.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkClock component (React Library)
 products:
   - realtime
 ---
-
 Shows the time elapsed in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkClock } from "@cloudflare/realtimekit-react-ui";
+import { RtkClock } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkClock />;
+  return <RtkClock />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkClock } from "@cloudflare/realtimekit-react-ui";
+import { RtkClock } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkClock meeting={meeting} size="md" />;
+  return (
+    <RtkClock
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
index 31eb8135db4c518..03354726cb31f89 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkConfirmationModal.mdx
@@ -5,36 +5,40 @@ description: API reference for RtkConfirmationModal component (React Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkConfirmationModal />;
+  return <RtkConfirmationModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkConfirmationModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkConfirmationModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkConfirmationModal meeting={meeting} />;
+  return (
+    <RtkConfirmationModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
index 70878abe0db3e5a..23812e3db206ab2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbar.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkControlbar component (React Library)
 products:
   - realtime
 ---
-
 Controlbar component provides you with various designs as variants.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbar />;
+  return <RtkControlbar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbar } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbar disableRender={true} meeting={meeting} size="md" />;
+  return (
+    <RtkControlbar
+      disableRender={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
index d9027e6aa0875b4..d0e6e508caf9480 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkControlbarButton.mdx
@@ -5,43 +5,47 @@ description: API reference for RtkControlbarButton component (React Library)
 products:
   - realtime
 ---
-
 A skeleton component used for composing custom controlbar buttons.
 
 ## Properties
 
-| Property      | Type                 | Required | Default           | Description                                                    |
-| ------------- | -------------------- | -------- | ----------------- | -------------------------------------------------------------- |
-| `brandIcon`   | `boolean`            | ✅       | -                 | Whether icon requires brand color                              |
-| `disabled`    | `boolean`            | ✅       | -                 | Whether button is disabled                                     |
-| `icon`        | `string`             | ✅       | -                 | Icon                                                           |
-| `iconPack`    | `IconPack`           | ❌       | `defaultIconPack` | Icon pack                                                      |
-| `isLoading`   | `boolean`            | ✅       | -                 | Loading state Ignores current icon and shows a spinner if true |
-| `label`       | `string`             | ✅       | -                 | Label of button                                                |
-| `showWarning` | `boolean`            | ✅       | -                 | Whether to show warning icon                                   |
-| `size`        | `Size`               | ✅       | -                 | Size                                                           |
-| `variant`     | `ControlBarVariant1` | ✅       | -                 | Variant                                                        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `brandIcon` | `boolean` | ✅ | - | Whether icon requires brand color |
+| `disabled` | `boolean` | ✅ | - | Whether button is disabled |
+| `icon` | `string` | ✅ | - | Icon |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isLoading` | `boolean` | ✅ | - | Loading state Ignores current icon and shows a spinner if true |
+| `label` | `string` | ✅ | - | Label of button |
+| `showWarning` | `boolean` | ✅ | - | Whether to show warning icon |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `ControlBarVariant1` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkControlbarButton />;
+  return <RtkControlbarButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkControlbarButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkControlbarButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkControlbarButton brandIcon={true} disabled={true} icon="example" />
-	);
+  return (
+    <RtkControlbarButton
+      brandIcon={true}
+      disabled={true}
+      icon="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
index 2f691f8771858ee..7b619a1539d261f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkCounter.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkCounter component (React Library)
 products:
   - realtime
 ---
-
 A number picker with increment and decrement buttons.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description   |
-| ---------- | ----------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack     |
-| `minValue` | `number`    | ✅       | -                 | Minimum value |
-| `size`     | `Size1`     | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language      |
-| `value`    | `number`    | ✅       | -                 | Initial value |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `minValue` | `number` | ✅ | - | Minimum value |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `value` | `number` | ✅ | - | Initial value |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
+import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCounter />;
+  return <RtkCounter />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkCounter } from "@cloudflare/realtimekit-react-ui";
+import { RtkCounter } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkCounter minValue={42} size="md" value={42} />;
+  return (
+    <RtkCounter
+      minValue={42}
+      size="md"
+      value={42}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
index e50a8ecb11348d8..f053eb720bed15d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebugger.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkDebugger component (React Library)
 products:
   - realtime
 ---
-
 A troubleshooting component to identify and fix any issues in the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebugger />;
+  return <RtkDebugger />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebugger } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebugger } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebugger meeting={meeting} size="md" />;
+  return (
+    <RtkDebugger
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
index e3b258be377ed38..7dc5d08497e8bd7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerAudio.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerAudio component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerAudio />;
+  return <RtkDebuggerAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerAudio meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerAudio
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
index 62053832f219996..84e96a1f71fb63a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerScreenshare.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerScreenshare component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerScreenshare />;
+  return <RtkDebuggerScreenshare />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerScreenshare } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerScreenshare } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerScreenshare meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerScreenshare
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
index fa2fc78d58a6309..351882399cc12df 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerSystem.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerSystem component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerSystem />;
+  return <RtkDebuggerSystem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerSystem } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerSystem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerSystem meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerSystem
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
index 5e693f7e36fb65e..a31dd78c42d4145 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkDebuggerToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerToggle />;
+  return <RtkDebuggerToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkDebuggerToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
index f5819d9caac23ff..c74f2cb9062572f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDebuggerVideo.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkDebuggerVideo component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `states`   | `States1`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerVideo />;
+  return <RtkDebuggerVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDebuggerVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkDebuggerVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDebuggerVideo meeting={meeting} size="md" />;
+  return (
+    <RtkDebuggerVideo
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
index 46fbf93818f24f8..fe104ba37211c2a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialog.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkDialog component (React Library)
 products:
   - realtime
 ---
-
 A dialog component.
 
 ## Properties
 
-| Property           | Type       | Required | Default                 | Description                            |
-| ------------------ | ---------- | -------- | ----------------------- | -------------------------------------- |
-| `config`           | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                              |
-| `disableEscapeKey` | `boolean`  | ✅       | -                       | Whether Escape key can close the modal |
-| `hideCloseButton`  | `boolean`  | ✅       | -                       | Whether to show the close button       |
-| `iconPack`         | `IconPack` | ❌       | `defaultIconPack`       | Icon pack                              |
-| `meeting`          | `Meeting`  | ✅       | -                       | Meeting object                         |
-| `open`             | `boolean`  | ✅       | -                       | Whether a dialog is open or not        |
-| `size`             | `Size`     | ✅       | -                       | Size                                   |
-| `states`           | `States`   | ✅       | -                       | States object                          |
-| `t`                | `RtkI18n`  | ❌       | `useLanguage()`         | Language                               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `disableEscapeKey` | `boolean` | ✅ | - | Whether Escape key can close the modal |
+| `hideCloseButton` | `boolean` | ✅ | - | Whether to show the close button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `open` | `boolean` | ✅ | - | Whether a dialog is open or not |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialog />;
+  return <RtkDialog />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialog } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialog } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkDialog
-			disableEscapeKey={true}
-			hideCloseButton={true}
-			meeting={meeting}
-		/>
-	);
+  return (
+    <RtkDialog
+      disableEscapeKey={true}
+      hideCloseButton={true}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
index 736b239555dd6c7..61ee80cd7643468 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDialogManager.mdx
@@ -5,45 +5,49 @@ description: API reference for RtkDialogManager component (React Library)
 products:
   - realtime
 ---
-
 A component which handles all dialog elements in a component such as:
-
-- rtk-settings
-- rtk-leave-meeting
-- rtk-permissions-message
-- rtk-image-viewer
-- rtk-breakout-rooms-manager
-  This components depends on the values from `states` object.
+ - rtk-settings
+ - rtk-leave-meeting
+ - rtk-permissions-message
+ - rtk-image-viewer
+ - rtk-breakout-rooms-manager
+ This components depends on the values from `states` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialogManager />;
+  return <RtkDialogManager />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDialogManager } from "@cloudflare/realtimekit-react-ui";
+import { RtkDialogManager } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDialogManager meeting={meeting} size="md" />;
+  return (
+    <RtkDialogManager
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
index 90c0d95b4208a0a..a5285022bbe30c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkDraftAttachmentView.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkDraftAttachmentView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders the draft attachment to send
 
 ## Properties
 
-| Property     | Type                                                 | Required | Default           | Description           |
-| ------------ | ---------------------------------------------------- | -------- | ----------------- | --------------------- |
-| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅       | -                 | Attachment to display |
-| `iconPack`   | `IconPack1`                                          | ❌       | `defaultIconPack` | Icon pack             |
-| `t`          | `RtkI18n1`                                           | ❌       | `useLanguage()`   | Language              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `attachment` | `{     type: 'image' \| 'file';     file: File;   }` | ✅ | - | Attachment to display |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
+import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDraftAttachmentView />;
+  return <RtkDraftAttachmentView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkDraftAttachmentView } from "@cloudflare/realtimekit-react-ui";
+import { RtkDraftAttachmentView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkDraftAttachmentView attachment={{}} />;
+  return (
+    <RtkDraftAttachmentView
+      attachment={{}}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
index 8a0e1b654ee40a0..c43046ea84826be 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPicker.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkEmojiPicker component (React Library)
 products:
   - realtime
 ---
-
 A very simple emoji picker component.
 
 ## Properties
 
-| Property          | Type       | Required | Default           | Description                               |
-| ----------------- | ---------- | -------- | ----------------- | ----------------------------------------- |
-| `focusWhenOpened` | `boolean`  | ✅       | -                 | Controls whether or not to focus on mount |
-| `iconPack`        | `IconPack` | ❌       | `defaultIconPack` | Icon pack                                 |
-| `t`               | `RtkI18n`  | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `focusWhenOpened` | `boolean` | ✅ | - | Controls whether or not to focus on mount |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPicker />;
+  return <RtkEmojiPicker />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPicker } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPicker } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPicker focusWhenOpened={true} />;
+  return (
+    <RtkEmojiPicker
+      focusWhenOpened={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
index dd15556f86ad2a2..fb41c2305bae5b8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEmojiPickerButton.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkEmojiPickerButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description            |
-| ---------- | ----------- | -------- | ----------------- | ---------------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack              |
-| `isActive` | `boolean`   | ✅       | -                 | Active state indicator |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language               |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isActive` | `boolean` | ✅ | - | Active state indicator |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPickerButton />;
+  return <RtkEmojiPickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEmojiPickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkEmojiPickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEmojiPickerButton isActive={true} />;
+  return (
+    <RtkEmojiPickerButton
+      isActive={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
index 9e06d6de13b10ac..f5d34bcb49b8d47 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkEndedScreen.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkEndedScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen which shows a meeting has ended.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Global states |
-| `size`     | `Size`     | ✅       | -                       | Size          |
-| `states`   | `States`   | ✅       | -                       | Global states |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Global states |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | Global states |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEndedScreen />;
+  return <RtkEndedScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkEndedScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkEndedScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkEndedScreen meeting={meeting} size="md" />;
+  return (
+    <RtkEndedScreen
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
index d000f71a09a18c4..249558fdf892cff 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileDropzone.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkFileDropzone component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type          | Required | Default           | Description                                 |
-| ---------- | ------------- | -------- | ----------------- | ------------------------------------------- |
-| `hostEl`   | `HTMLElement` | ✅       | -                 | Host element on which drop events to attach |
-| `iconPack` | `IconPack1`   | ❌       | `defaultIconPack` | Icon pack                                   |
-| `t`        | `RtkI18n1`    | ❌       | `useLanguage()`   | Language                                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `hostEl` | `HTMLElement` | ✅ | - | Host element on which drop events to attach |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileDropzone />;
+  return <RtkFileDropzone />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileDropzone } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileDropzone } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileDropzone hostEl={htmlelement} />;
+  return (
+    <RtkFileDropzone
+      hostEl={htmlelement}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
index 0d763747bc4f21b..160e6d45a1c3e0d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessage.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkFileMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-file-message` is deprecated and will be removed soon. Use `rtk-file-message-view` instead.
-A component which renders a file message from chat.
+ A component which renders a file message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `FileMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `FileMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessage />;
+  return <RtkFileMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessage isContinued={true} message={filemessage} now={date} />;
+  return (
+    <RtkFileMessage
+      isContinued={true}
+      message={filemessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
index 64098e714003e5e..baf330586b09a46 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFileMessageView.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkFileMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a file message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `name`     | `string`    | ✅       | -                 | Name of the file |
-| `size`     | `number`    | ✅       | -                 | Size of the file |
-| `url`      | `string`    | ✅       | -                 | Url of the file  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `name` | `string` | ✅ | - | Name of the file |
+| `size` | `number` | ✅ | - | Size of the file |
+| `url` | `string` | ✅ | - | Url of the file |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessageView />;
+  return <RtkFileMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFileMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkFileMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFileMessageView name="example" size={42} url="example" />;
+  return (
+    <RtkFileMessageView
+      name="example"
+      size={42}
+      url="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
index f495c13464a820e..7695557d4ce9b2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFilePickerButton.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkFilePickerButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type              | Required | Default           | Description                               |
-| ---------- | ----------------- | -------- | ----------------- | ----------------------------------------- |
-| `filter`   | `string`          | ✅       | -                 | File type filter to open file picker with |
-| `icon`     | `keyof IconPack1` | ✅       | -                 | Icon                                      |
-| `iconPack` | `IconPack1`       | ❌       | `defaultIconPack` | Icon pack                                 |
-| `label`    | `string`          | ✅       | -                 | Label for tooltip                         |
-| `t`        | `RtkI18n1`        | ❌       | `useLanguage()`   | Language                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `filter` | `string` | ✅ | - | File type filter to open file picker with |
+| `icon` | `keyof IconPack1` | ✅ | - | Icon |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `label` | `string` | ✅ | - | Label for tooltip |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFilePickerButton />;
+  return <RtkFilePickerButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFilePickerButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkFilePickerButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkFilePickerButton
-			filter="example"
-			icon={defaultIconPack}
-			label="example"
-		/>
-	);
+  return (
+    <RtkFilePickerButton
+      filter="example"
+      icon={defaultIconPack}
+      label="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
index 0abc92d640e427b..4dfd50432f2e792 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkFullscreenToggle.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkFullscreenToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles full screen mode for any
-existing `rtk-meeting` component in the DOM.
+ existing `rtk-meeting` component in the DOM.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                  |
-| --------------- | ------------------- | -------- | ----------------- | ---------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                    |
-| `size`          | `Size`              | ✅       | -                 | Size                         |
-| `states`        | `States`            | ✅       | -                 | States object                |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                     |
-| `targetElement` | `HTMLElement`       | ✅       | -                 | Target Element to fullscreen |
-| `variant`       | `ControlBarVariant` | ✅       | -                 | Variant                      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `targetElement` | `HTMLElement` | ✅ | - | Target Element to fullscreen |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkFullscreenToggle />;
+  return <RtkFullscreenToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkFullscreenToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkFullscreenToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkFullscreenToggle
-			size="md"
-			targetElement={htmlelement}
-			variant="button"
-		/>
-	);
+  return (
+    <RtkFullscreenToggle
+      size="md"
+      targetElement={htmlelement}
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
index f927f0f83579df1..ba09d23bb59421f 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGrid.mdx
@@ -5,43 +5,49 @@ description: API reference for RtkGrid component (React Library)
 products:
   - realtime
 ---
-
 The main grid component which abstracts all the grid handling logic and renders it for you.
 
 ## Properties
 
-| Property      | Type         | Required | Default                 | Description                          |
-| ------------- | ------------ | -------- | ----------------------- | ------------------------------------ |
-| `aspectRatio` | `string`     | ✅       | -                       | The aspect ratio of each participant |
-| `config`      | `UIConfig`   | ❌       | `createDefaultConfig()` | Config object                        |
-| `gap`         | `number`     | ✅       | -                       | Gap between participants             |
-| `gridSize`    | `GridSize`   | ✅       | -                       | Grid size                            |
-| `iconPack`    | `IconPack`   | ❌       | `defaultIconPack`       | Icon pack                            |
-| `layout`      | `GridLayout` | ✅       | -                       | Grid Layout                          |
-| `meeting`     | `Meeting`    | ✅       | -                       | Meeting object                       |
-| `overrides`   | `any`        | ✅       | -                       | @deprecated                          |
-| `size`        | `Size`       | ✅       | -                       | Size                                 |
-| `states`      | `States`     | ✅       | -                       | States                               |
-| `t`           | `RtkI18n`    | ❌       | `useLanguage()`         | Language                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | The aspect ratio of each participant |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `gap` | `number` | ✅ | - | Gap between participants |
+| `gridSize` | `GridSize` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `layout` | `GridLayout` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `overrides` | `any` | ✅ | - | @deprecated |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGrid />;
+  return <RtkGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
index 2ec869ec68a635d..5f237bf642f2544 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkGridPagination.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkGridPagination component (React Library)
 products:
   - realtime
 ---
-
 A component which allows you to change current page and view mode
-of active participants list. This is reflected in the `rtk-grid` component.
+ of active participants list. This is reflected in the `rtk-grid` component.
 
 ## Properties
 
-| Property   | Type                     | Required | Default           | Description    |
-| ---------- | ------------------------ | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`               | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`                | ✅       | -                 | Meeting object |
-| `size`     | `Size`                   | ✅       | -                 | Size Prop      |
-| `states`   | `States`                 | ✅       | -                 | States         |
-| `t`        | `RtkI18n`                | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `GridPaginationVariants` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size Prop |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `GridPaginationVariants` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
+import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkGridPagination />;
+  return <RtkGridPagination />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkGridPagination } from "@cloudflare/realtimekit-react-ui";
+import { RtkGridPagination } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkGridPagination
-			meeting={meeting}
-			size="md"
-			variant={gridpaginationvariants}
-		/>
-	);
+  return (
+    <RtkGridPagination
+      meeting={meeting}
+      size="md"
+      variant={gridpaginationvariants}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
index ae22b18378bd4c7..10ccda38fa97f7e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkHeader.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkHeader component (React Library)
 products:
   - realtime
 ---
-
 A component that houses all the header components.
 
 ## Properties
 
-| Property        | Type                 | Required | Default                 | Description                      |
-| --------------- | -------------------- | -------- | ----------------------- | -------------------------------- |
-| `config`        | `UIConfig1`          | ❌       | `createDefaultConfig()` | Config                           |
-| `disableRender` | `boolean`            | ✅       | -                       | Whether to render the default UI |
-| `iconPack`      | `IconPack1`          | ❌       | `defaultIconPack`       | Icon Pack                        |
-| `meeting`       | `Meeting`            | ✅       | -                       | Meeting                          |
-| `size`          | `Size`               | ✅       | -                       | Size                             |
-| `states`        | `States`             | ✅       | -                       | States                           |
-| `t`             | `RtkI18n`            | ❌       | `useLanguage()`         | Language                         |
-| `variant`       | `'solid' \| 'boxed'` | ✅       | -                       | Variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `disableRender` | `boolean` | ✅ | - | Whether to render the default UI |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'solid' \| 'boxed'` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkHeader />;
+  return <RtkHeader />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkHeader } from "@cloudflare/realtimekit-react-ui";
+import { RtkHeader } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkHeader disableRender={true} meeting={meeting} size="md" />;
+  return (
+    <RtkHeader
+      disableRender={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
index 16a092f54b2dbce..f7283d6288d99a4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIcon.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkIcon component (React Library)
 products:
   - realtime
 ---
-
 An icon component which accepts an svg string and renders it.
 
 ## Properties
 
-| Property  | Type          | Required | Default | Description  |
-| --------- | ------------- | -------- | ------- | ------------ |
-| `icon`    | `string`      | ✅       | -       | Icon         |
-| `size`    | `Size1`       | ✅       | -       | Size         |
-| `variant` | `IconVariant` | ✅       | -       | Icon variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `icon` | `string` | ✅ | - | Icon |
+| `size` | `Size1` | ✅ | - | Size |
+| `variant` | `IconVariant` | ✅ | - | Icon variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
+import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIcon />;
+  return <RtkIcon />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIcon } from "@cloudflare/realtimekit-react-ui";
+import { RtkIcon } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIcon icon="example" size="md" variant="primary" />;
+  return (
+    <RtkIcon
+      icon="example"
+      size="md"
+      variant="primary"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
index c1bb80f2c5f6df1..673fc18b193b110 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkIdleScreen.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkIdleScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen that handles the idle state,
-i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
+ i.e; when you are waiting for data about the meeting, specifically the `meeting` object.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description   |
-| ---------- | ---------- | -------- | ----------------------- | ------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack     |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting       |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIdleScreen />;
+  return <RtkIdleScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkIdleScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkIdleScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkIdleScreen meeting={meeting} />;
+  return (
+    <RtkIdleScreen
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
index 55513c0267caef0..8c0288f2c73bdea 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessage.mdx
@@ -5,41 +5,45 @@ description: API reference for RtkImageMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-image-message` is deprecated and will be removed soon. Use `rtk-image-message-view` instead.
-A component which renders an image message from chat.
+ A component which renders an image message from chat.
 
 ## Properties
 
-| Property      | Type           | Required | Default           | Description                                             |
-| ------------- | -------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`     | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`      | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `ImageMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`         | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`      | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`      | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `ImageMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessage />;
+  return <RtkImageMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkImageMessage isContinued={true} message={imagemessage} now={date} />
-	);
+  return (
+    <RtkImageMessage
+      isContinued={true}
+      message={imagemessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
index 7bbc3cd4d39a23a..c780f5404911db6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageMessageView.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkImageMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders an image message.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description      |
-| ---------- | ----------- | -------- | ----------------- | ---------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack        |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language         |
-| `url`      | `string`    | ✅       | -                 | Url of the image |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `url` | `string` | ✅ | - | Url of the image |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessageView />;
+  return <RtkImageMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageMessageView url="example" />;
+  return (
+    <RtkImageMessageView
+      url="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
index 9df4c2bb772122b..91083a36a5cc7cd 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkImageViewer.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkImageViewer component (React Library)
 products:
   - realtime
 ---
-
 A component which shows an image sent via chat.
 
 ## Properties
 
-| Property   | Type           | Required | Default           | Description   |
-| ---------- | -------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`     | ❌       | `defaultIconPack` | Icon pack     |
-| `image`    | `ImageMessage` | ✅       | -                 | Image message |
-| `size`     | `Size`         | ✅       | -                 | Size          |
-| `t`        | `RtkI18n`      | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `image` | `ImageMessage` | ✅ | - | Image message |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageViewer />;
+  return <RtkImageViewer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkImageViewer } from "@cloudflare/realtimekit-react-ui";
+import { RtkImageViewer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkImageViewer image={imagemessage} size="md" />;
+  return (
+    <RtkImageViewer
+      image={imagemessage}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
index 59bb5a4a42279d0..0fbe8b295b4e90a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkInformationTooltip.mdx
@@ -5,31 +5,35 @@ description: API reference for RtkInformationTooltip component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkInformationTooltip />;
+  return <RtkInformationTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkInformationTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkInformationTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkInformationTooltip iconPack={defaultIconPack} />;
+  return (
+    <RtkInformationTooltip
+      iconPack={defaultIconPack}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
index cb2514eb8f698d8..980d877c6c2be1c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkJoinStage.mdx
@@ -5,39 +5,43 @@ description: API reference for RtkJoinStage component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type              | Required | Default                 | Description    |
-| ------------ | ----------------- | -------- | ----------------------- | -------------- |
-| `config`     | `UIConfig`        | ❌       | `createDefaultConfig()` | UI Config      |
-| `dataConfig` | `ModalDataConfig` | ✅       | -                       | Content Config |
-| `iconPack`   | `IconPack`        | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`    | `Meeting`         | ✅       | -                       | Meeting object |
-| `size`       | `Size`            | ✅       | -                       | Size           |
-| `states`     | `States`          | ✅       | -                       | States object  |
-| `t`          | `RtkI18n`         | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `dataConfig` | `ModalDataConfig` | ✅ | - | Content Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkJoinStage />;
+  return <RtkJoinStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkJoinStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkJoinStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkJoinStage dataConfig={modaldataconfig} meeting={meeting} size="md" />
-	);
+  return (
+    <RtkJoinStage
+      dataConfig={modaldataconfig}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
index bd0118ecce5e460..cbadd40c668ffb5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveButton.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkLeaveButton component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visilibility of the leave confirmation dialog.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description |
-| ---------- | ------------------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size`              | ✅       | -                 | Size        |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language    |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveButton />;
+  return <RtkLeaveButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveButton size="md" variant="button" />;
+  return (
+    <RtkLeaveButton
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
index caaa57aa9b7489a..381df4d5a32d9a8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLeaveMeeting.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkLeaveMeeting component (React Library)
 products:
   - realtime
 ---
-
 A component which allows you to leave a meeting or
-end meeting for all, if you have the permission.
+ end meeting for all, if you have the permission.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveMeeting />;
+  return <RtkLeaveMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLeaveMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkLeaveMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLeaveMeeting meeting={meeting} />;
+  return (
+    <RtkLeaveMeeting
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
index f32e008ce30ba45..c460afe367c3aba 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamIndicator.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkLivestreamIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamIndicator />;
+  return <RtkLivestreamIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkLivestreamIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
index 76bcbcc4f131e9b..f2825122178db2e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamPlayer.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkLivestreamPlayer component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type        | Required | Default           | Description    |
-| ---------- | ----------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting object |
-| `size`     | `Size1`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n1`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamPlayer />;
+  return <RtkLivestreamPlayer />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamPlayer } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamPlayer } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamPlayer meeting={meeting} size="md" />;
+  return (
+    <RtkLivestreamPlayer
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
index bbc41afc7185d64..5a02a6110c65ab6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLivestreamToggle.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkLivestreamToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamToggle />;
+  return <RtkLivestreamToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLivestreamToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkLivestreamToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLivestreamToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkLivestreamToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
index 9477a16d30710b5..eb4e53ce7220d26 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkLogo.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkLogo component (React Library)
 products:
   - realtime
 ---
-
 A component which loads the logo from your config, or via the `logo-url` attribute.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `logoUrl` | `string`   | ✅       | -                       | Logo URL       |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `logoUrl` | `string` | ✅ | - | Logo URL |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
+import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLogo />;
+  return <RtkLogo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkLogo } from "@cloudflare/realtimekit-react-ui";
+import { RtkLogo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkLogo logoUrl="example" meeting={meeting} />;
+  return (
+    <RtkLogo
+      logoUrl="example"
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
index 55fbf4dd7de4c88..b4a60b36bb5affb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMarkdownView.mdx
@@ -5,32 +5,37 @@ description: API reference for RtkMarkdownView component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type     | Required | Default | Description                              |
-| ----------- | -------- | -------- | ------- | ---------------------------------------- |
-| `maxLength` | `number` | ✅       | -       | max length of text to render as markdown |
-| `text`      | `string` | ✅       | -       | raw text to render as markdown           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `maxLength` | `number` | ✅ | - | max length of text to render as markdown |
+| `text` | `string` | ✅ | - | raw text to render as markdown |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMarkdownView />;
+  return <RtkMarkdownView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMarkdownView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMarkdownView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMarkdownView maxLength={42} text="example" />;
+  return (
+    <RtkMarkdownView
+      maxLength={42}
+      text="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
index fc2ab8e84fcd5de..46f187b5651c348 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeeting.mdx
@@ -5,53 +5,53 @@ description: API reference for RtkMeeting component (React Library)
 products:
   - realtime
 ---
-
 A single component which renders an entire meeting UI.
-It loads your preset and renders the UI based on it.
-With this component, you don't have to handle all the states,
-dialogs and other smaller bits of managing the application.
+ It loads your preset and renders the UI based on it.
+ With this component, you don't have to handle all the states,
+ dialogs and other smaller bits of managing the application.
 
 ## Properties
 
-| Property               | Type          | Required | Default            | Description                                                         |
-| ---------------------- | ------------- | -------- | ------------------ | ------------------------------------------------------------------- |
-| `applyDesignSystem`    | `boolean`     | ✅       | -                  | Whether to apply the design system on the document root from config |
-| `config`               | `UIConfig`    | ✅       | -                  | UI Config                                                           |
-| `gridLayout`           | `GridLayout1` | ✅       | -                  | Grid layout                                                         |
-| `iconPack`             | `IconPack`    | ❌       | `defaultIconPack`  | Icon pack                                                           |
-| `leaveOnUnmount`       | `boolean`     | ✅       | -                  | Whether participant should leave when this component gets unmounted |
-| `loadConfigFromPreset` | `boolean`     | ✅       | -                  | Whether to load config from preset                                  |
-| `meeting`              | `Meeting`     | ✅       | -                  | Meeting object                                                      |
-| `mode`                 | `MeetingMode` | ✅       | -                  | Fill type                                                           |
-| `overrides`            | `Overrides`   | ❌       | `defaultOverrides` | UI Kit Overrides                                                    |
-| `showSetupScreen`      | `boolean`     | ✅       | -                  | Whether to show setup screen or not                                 |
-| `size`                 | `Size`        | ✅       | -                  | Size                                                                |
-| `t`                    | `RtkI18n`     | ❌       | `useLanguage()`    | Language                                                            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `applyDesignSystem` | `boolean` | ✅ | - | Whether to apply the design system on the document root from config |
+| `config` | `UIConfig` | ✅ | - | UI Config |
+| `gridLayout` | `GridLayout1` | ✅ | - | Grid layout |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `leaveOnUnmount` | `boolean` | ✅ | - | Whether participant should leave when this component gets unmounted |
+| `loadConfigFromPreset` | `boolean` | ✅ | - | Whether to load config from preset |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `mode` | `MeetingMode` | ✅ | - | Fill type |
+| `overrides` | `Overrides` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeeting />;
+  return <RtkMeeting />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeeting } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeeting } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMeeting
-			applyDesignSystem={true}
-			config={defaultUiConfig}
-			gridLayout={gridlayout1}
-		/>
-	);
+  return (
+    <RtkMeeting
+      applyDesignSystem={true}
+      config={defaultUiConfig}
+      gridLayout={gridlayout1}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
index 8e26823a9775b15..390e091d34851d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMeetingTitle.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkMeetingTitle component (React Library)
 products:
   - realtime
 ---
-
 Displays the title of the meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeetingTitle />;
+  return <RtkMeetingTitle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMeetingTitle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMeetingTitle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMeetingTitle meeting={meeting} />;
+  return (
+    <RtkMeetingTitle
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
index 9ee83f7cee4ea0a..5f5db9ac9f51c5d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenu.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkMenu component (React Library)
 products:
   - realtime
 ---
-
 A menu component.
 
 ## Properties
 
-| Property    | Type        | Required | Default           | Description       |
-| ----------- | ----------- | -------- | ----------------- | ----------------- |
-| `iconPack`  | `IconPack`  | ❌       | `defaultIconPack` | Icon pack         |
-| `offset`    | `number`    | ✅       | -                 | Offset in px      |
-| `placement` | `Placement` | ✅       | -                 | Placement of menu |
-| `size`      | `Size`      | ✅       | -                 | Size              |
-| `t`         | `RtkI18n`   | ❌       | `useLanguage()`   | Language          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `offset` | `number` | ✅ | - | Offset in px |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenu />;
+  return <RtkMenu />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenu } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenu } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenu offset={42} placement={placement} size="md" />;
+  return (
+    <RtkMenu
+      offset={42}
+      placement={placement}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
index e3ed88af47b32ff..07d2090f6869fa5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuItem.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkMenuItem component (React Library)
 products:
   - realtime
 ---
-
 A menu item component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `size`        | `Size`                     | ✅       | -                 | Size        |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuItem />;
+  return <RtkMenuItem />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuItem } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuItem } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuItem menuVariant={"primary" | "secondary"} size="md" />;
+  return (
+    <RtkMenuItem
+      menuVariant={'primary' | 'secondary'}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
index c8535a1fd33ef85..3abcdf3681cf82c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMenuList.mdx
@@ -5,35 +5,39 @@ description: API reference for RtkMenuList component (React Library)
 products:
   - realtime
 ---
-
 A menu list component.
 
 ## Properties
 
-| Property      | Type                       | Required | Default           | Description |
-| ------------- | -------------------------- | -------- | ----------------- | ----------- |
-| `iconPack`    | `IconPack`                 | ❌       | `defaultIconPack` | Icon pack   |
-| `menuVariant` | `'primary' \| 'secondary'` | ✅       | -                 | Variant     |
-| `t`           | `RtkI18n`                  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `menuVariant` | `'primary' \| 'secondary'` | ✅ | - | Variant |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuList />;
+  return <RtkMenuList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMenuList } from "@cloudflare/realtimekit-react-ui";
+import { RtkMenuList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMenuList menuVariant={"primary" | "secondary"} />;
+  return (
+    <RtkMenuList
+      menuVariant={'primary' | 'secondary'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
index 80a9a91264a8c83..a821d60dd934f37 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMessageView.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkMessageView component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                       | Required | Default           | Description                             |
-| ---------------- | -------------------------- | -------- | ----------------- | --------------------------------------- |
-| `actions`        | `MessageAction[]`          | ✅       | -                 | List of actions to show in menu         |
-| `authorName`     | `string`                   | ✅       | -                 | Author display label                    |
-| `avatarUrl`      | `string`                   | ✅       | -                 | Avatar image url                        |
-| `hideAuthorName` | `boolean`                  | ✅       | -                 | Hides author display label              |
-| `hideAvatar`     | `boolean`                  | ✅       | -                 | Hides avatar                            |
-| `hideMetadata`   | `boolean`                  | ✅       | -                 | Hides metadata (time)                   |
-| `iconPack`       | `IconPack1`                | ❌       | `defaultIconPack` | Icon pack                               |
-| `isEdited`       | `boolean`                  | ✅       | -                 | Has the message been edited             |
-| `isSelf`         | `boolean`                  | ✅       | -                 | Is the message sent by the current user |
-| `messageType`    | `Message['type']`          | ✅       | -                 | Type of message                         |
-| `pinned`         | `boolean`                  | ✅       | -                 | Is message pinned                       |
-| `time`           | `Date`                     | ✅       | -                 | Time when message was sent              |
-| `variant`        | `'plain' \| 'bubble'`      | ✅       | -                 | Appearance                              |
-| `viewType`       | `'incoming' \| 'outgoing'` | ✅       | -                 | Render                                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `actions` | `MessageAction[]` | ✅ | - | List of actions to show in menu |
+| `authorName` | `string` | ✅ | - | Author display label |
+| `avatarUrl` | `string` | ✅ | - | Avatar image url |
+| `hideAuthorName` | `boolean` | ✅ | - | Hides author display label |
+| `hideAvatar` | `boolean` | ✅ | - | Hides avatar |
+| `hideMetadata` | `boolean` | ✅ | - | Hides metadata (time) |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isEdited` | `boolean` | ✅ | - | Has the message been edited |
+| `isSelf` | `boolean` | ✅ | - | Is the message sent by the current user |
+| `messageType` | `Message['type']` | ✅ | - | Type of message |
+| `pinned` | `boolean` | ✅ | - | Is message pinned |
+| `time` | `Date` | ✅ | - | Time when message was sent |
+| `variant` | `'plain' \| 'bubble'` | ✅ | - | Appearance |
+| `viewType` | `'incoming' \| 'outgoing'` | ✅ | - | Render |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMessageView />;
+  return <RtkMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMessageView actions={[]} authorName="example" avatarUrl="example" />
-	);
+  return (
+    <RtkMessageView
+      actions={[]}
+      authorName="example"
+      avatarUrl="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
index cc03a1979681184..8a828fa1df70a57 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkMicToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your microphone.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicToggle />;
+  return <RtkMicToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkMicToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
index bddd6410870b69d..7635bf3bc850417 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMicrophoneSelector.mdx
@@ -5,52 +5,51 @@ description: API reference for RtkMicrophoneSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMicrophoneSelector />;
+  return <RtkMicrophoneSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMicrophoneSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkMicrophoneSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkMicrophoneSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkMicrophoneSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
index 2a84e600445f8a4..9797cef0997f626 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMixedGrid.mdx
@@ -5,46 +5,52 @@ description: API reference for RtkMixedGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component which handles screenshares, plugins and participants.
 
 ## Properties
 
-| Property                  | Type          | Required | Default                 | Description                                             |
-| ------------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`             | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`                  | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                     | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`                | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`                | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`                  | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`                 | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`            | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants`      | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `plugins`                 | `RTKPlugin[]` | ✅       | -                       | Active Plugins                                          |
-| `screenShareParticipants` | `Peer[]`      | ✅       | -                       | Screenshare Participants                                |
-| `size`                    | `Size`        | ✅       | -                       | Size                                                    |
-| `states`                  | `States`      | ✅       | -                       | States object                                           |
-| `t`                       | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `plugins` | `RTKPlugin[]` | ✅ | - | Active Plugins |
+| `screenShareParticipants` | `Peer[]` | ✅ | - | Screenshare Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMixedGrid />;
+  return <RtkMixedGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMixedGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkMixedGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMixedGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkMixedGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
index ec75917e7d6794f..2c8f9d6008454df 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMoreToggle.mdx
@@ -5,43 +5,44 @@ description: API reference for RtkMoreToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of a more menu.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeMoreMenu: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeMoreMenu: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description   |
-| ---------- | ---------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`     | ✅       | -                 | Size          |
-| `states`   | `States`   | ✅       | -                 | States object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMoreToggle />;
+  return <RtkMoreToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMoreToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkMoreToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMoreToggle size="md" />;
+  return (
+    <RtkMoreToggle
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
index 9ff1d6062e97f3a..0a61a27b14d57cb 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllButton.mdx
@@ -5,35 +5,41 @@ description: API reference for RtkMuteAllButton component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllButton />;
+  return <RtkMuteAllButton />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllButton } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllButton } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllButton meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkMuteAllButton
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
index de60763a8da782a..6964b04a06fce07 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkMuteAllConfirmation.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkMuteAllConfirmation component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllConfirmation />;
+  return <RtkMuteAllConfirmation />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkMuteAllConfirmation } from "@cloudflare/realtimekit-react-ui";
+import { RtkMuteAllConfirmation } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkMuteAllConfirmation meeting={meeting} />;
+  return (
+    <RtkMuteAllConfirmation
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
index b24255b2688e80e..653d3e71c13c219 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNameTag.mdx
@@ -5,45 +5,45 @@ description: API reference for RtkNameTag component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a participant's name.
 
 ## Properties
 
-| Property        | Type                | Required | Default           | Description                               |
-| --------------- | ------------------- | -------- | ----------------- | ----------------------------------------- |
-| `iconPack`      | `IconPack`          | ❌       | `defaultIconPack` | Icon pack                                 |
-| `isScreenShare` | `boolean`           | ✅       | -                 | Whether it is used in a screen share view |
-| `meeting`       | `Meeting`           | ✅       | -                 | Meeting object                            |
-| `participant`   | `Peer`              | ✅       | -                 | Participant object                        |
-| `size`          | `Size`              | ✅       | -                 | Size                                      |
-| `t`             | `RtkI18n`           | ❌       | `useLanguage()`   | Language                                  |
-| `variant`       | `RtkNameTagVariant` | ✅       | -                 | Name tag variant                          |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Whether it is used in a screen share view |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `RtkNameTagVariant` | ✅ | - | Name tag variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
+import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNameTag />;
+  return <RtkNameTag />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNameTag } from "@cloudflare/realtimekit-react-ui";
+import { RtkNameTag } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNameTag
-			isScreenShare={true}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkNameTag
+      isScreenShare={true}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
index badca357da7d298..cdc9b9d26f6014c 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNetworkIndicator.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkNetworkIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property        | Type        | Required | Default           | Description         |
-| --------------- | ----------- | -------- | ----------------- | ------------------- |
-| `iconPack`      | `IconPack1` | ❌       | `defaultIconPack` | Icon pack           |
-| `isScreenShare` | `boolean`   | ✅       | -                 | Is for screenshare  |
-| `meeting`       | `Meeting`   | ✅       | -                 | Meeting             |
-| `participant`   | `Peer`      | ✅       | -                 | Participant or Self |
-| `t`             | `RtkI18n1`  | ❌       | `useLanguage()`   | Language            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `isScreenShare` | `boolean` | ✅ | - | Is for screenshare |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `participant` | `Peer` | ✅ | - | Participant or Self |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNetworkIndicator />;
+  return <RtkNetworkIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNetworkIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkNetworkIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNetworkIndicator
-			isScreenShare={true}
-			meeting={meeting}
-			participant={participant}
-		/>
-	);
+  return (
+    <RtkNetworkIndicator
+      isScreenShare={true}
+      meeting={meeting}
+      participant={participant}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
index 5aecde35407d99b..011b505c0f96d15 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotification.mdx
@@ -5,41 +5,45 @@ description: API reference for RtkNotification component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a notification.
-You need to remove the element after you receive the
-`rtkNotificationDismiss` event.
+ You need to remove the element after you receive the
+ `rtkNotificationDismiss` event.
 
 ## Properties
 
-| Property       | Type           | Required | Default           | Description             |
-| -------------- | -------------- | -------- | ----------------- | ----------------------- |
-| `iconPack`     | `IconPack`     | ❌       | `defaultIconPack` | Icon pack               |
-| `notification` | `Notification` | ✅       | -                 | Message                 |
-| `paused`       | `boolean`      | ✅       | -                 | Stops timeout when true |
-| `size`         | `Size`         | ✅       | -                 | Size                    |
-| `t`            | `RtkI18n`      | ❌       | `useLanguage()`   | Language                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `notification` | `Notification` | ✅ | - | Message |
+| `paused` | `boolean` | ✅ | - | Stops timeout when true |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotification />;
+  return <RtkNotification />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotification } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotification } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkNotification notification={notification} paused={true} size="md" />
-	);
+  return (
+    <RtkNotification
+      notification={notification}
+      paused={true}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
index b4cf3563bdaf55e..a6479a63c2b3dc3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkNotifications.mdx
@@ -5,40 +5,45 @@ description: API reference for RtkNotifications component (React Library)
 products:
   - realtime
 ---
-
 A component which handles notifications.
-You can configure which notifications you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which notifications you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotifications />;
+  return <RtkNotifications />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkNotifications } from "@cloudflare/realtimekit-react-ui";
+import { RtkNotifications } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkNotifications meeting={meeting} size="md" />;
+  return (
+    <RtkNotifications
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
index f4a1c236a9e1ff3..075d2ad41e4e7f1 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkOverlayModal.mdx
@@ -5,36 +5,40 @@ description: API reference for RtkOverlayModal component (React Library)
 products:
   - realtime
 ---
-
 A confirmation modal.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkOverlayModal />;
+  return <RtkOverlayModal />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkOverlayModal } from "@cloudflare/realtimekit-react-ui";
+import { RtkOverlayModal } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkOverlayModal meeting={meeting} />;
+  return (
+    <RtkOverlayModal
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
index 4efdfe198d33ae2..9c2aa7dd5fa68fa 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPaginatedList.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkPaginatedList component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property         | Type                                                   | Required | Default           | Description                                    |
-| ---------------- | ------------------------------------------------------ | -------- | ----------------- | ---------------------------------------------- |
-| `autoScroll`     | `boolean`                                              | ✅       | -                 | auto scroll list to bottom                     |
-| `createNodes`    | `(data: unknown[])`                                    | ✅       | -                 | Create nodes                                   |
-| `emptyListLabel` | `string`                                               | ✅       | -                 | label to show when empty                       |
-| `fetchData`      | `(timestamp: number, size: number, reversed: boolean)` | ✅       | -                 | Fetch the data                                 |
-| `iconPack`       | `IconPack`                                             | ❌       | `defaultIconPack` | Icon pack                                      |
-| `pageSize`       | `number`                                               | ✅       | -                 | Page Size                                      |
-| `pagesAllowed`   | `number`                                               | ✅       | -                 | Number of pages allowed to be shown            |
-| `rerenderList`   | `()`                                                   | ✅       | -                 | Rerender paginated list                        |
-| `reset`          | `(timestamp?: number)`                                 | ❌       | -                 | Resets the paginated list to a given timestamp |
-| `t`              | `RtkI18n`                                              | ❌       | `useLanguage()`   | Language                                       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `autoScroll` | `boolean` | ✅ | - | auto scroll list to bottom |
+| `createNodes` | `(data: unknown[])` | ✅ | - | Create nodes |
+| `emptyListLabel` | `string` | ✅ | - | label to show when empty |
+| `fetchData` | `(timestamp: number, size: number, reversed: boolean)` | ✅ | - | Fetch the data |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `pageSize` | `number` | ✅ | - | Page Size |
+| `pagesAllowed` | `number` | ✅ | - | Number of pages allowed to be shown |
+| `rerenderList` | `()` | ✅ | - | Rerender paginated list |
+| `reset` | `(timestamp?: number)` | ❌ | - | Resets the paginated list to a given timestamp |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
+import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPaginatedList />;
+  return <RtkPaginatedList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPaginatedList } from "@cloudflare/realtimekit-react-ui";
+import { RtkPaginatedList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkPaginatedList
-			autoScroll={true}
-			createNodes={[]}
-			emptyListLabel="example"
-		/>
-	);
+  return (
+    <RtkPaginatedList
+      autoScroll={true}
+      createNodes={[]}
+      emptyListLabel="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
index 516579dd9a334b1..ccc8cb4e191bc51 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipant.mdx
@@ -5,47 +5,47 @@ description: API reference for RtkParticipant component (React Library)
 products:
   - realtime
 ---
-
 A participant entry component used inside `rtk-participants` which shows data like:
-name, picture and media device status.
-You can perform privileged actions on the participant too.
+ name, picture and media device status.
+ You can perform privileged actions on the participant too.
 
 ## Properties
 
-| Property      | Type                  | Required | Default                 | Description              |
-| ------------- | --------------------- | -------- | ----------------------- | ------------------------ |
-| `config`      | `UIConfig1`           | ❌       | `createDefaultConfig()` | Config object            |
-| `iconPack`    | `IconPack`            | ❌       | `defaultIconPack`       | Icon pack                |
-| `meeting`     | `Meeting`             | ✅       | -                       | Meeting object           |
-| `participant` | `Peer`                | ✅       | -                       | Participant object       |
-| `states`      | `States1`             | ✅       | -                       | States                   |
-| `t`           | `RtkI18n`             | ❌       | `useLanguage()`         | Language                 |
-| `view`        | `ParticipantViewMode` | ✅       | -                       | Show participant summary |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participant` | `Peer` | ✅ | - | Participant object |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantViewMode` | ✅ | - | Show participant summary |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipant />;
+  return <RtkParticipant />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipant } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipant } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipant
-			meeting={meeting}
-			participant={participant}
-			view={participantviewmode}
-		/>
-	);
+  return (
+    <RtkParticipant
+      meeting={meeting}
+      participant={participant}
+      view={participantviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
index 328f0c14986aba0..e8cd175555dcd38 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantCount.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkParticipantCount component (React Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantCount />;
+  return <RtkParticipantCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantCount meeting={meeting} size="md" />;
+  return (
+    <RtkParticipantCount
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
index 91ef45fb563d602..7606fca272f529b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipants.mdx
@@ -5,46 +5,46 @@ description: API reference for RtkParticipants component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property                   | Type                | Required | Default                 | Description     |
-| -------------------------- | ------------------- | -------- | ----------------------- | --------------- |
-| `config`                   | `UIConfig`          | ❌       | `createDefaultConfig()` | Config          |
-| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅       | -                       | Default section |
-| `iconPack`                 | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack       |
-| `meeting`                  | `Meeting`           | ✅       | -                       | Meeting object  |
-| `size`                     | `Size`              | ✅       | -                       | Size            |
-| `states`                   | `States`            | ✅       | -                       | States object   |
-| `t`                        | `RtkI18n`           | ❌       | `useLanguage()`         | Language        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultParticipantsTabId` | `ParticipantsTabId` | ✅ | - | Default section |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipants />;
+  return <RtkParticipants />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipants } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipants } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipants
-			defaultParticipantsTabId={participantstabid}
-			meeting={meeting}
-			size="md"
-		/>
-	);
+  return (
+    <RtkParticipants
+      defaultParticipantsTabId={participantstabid}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
index b758d16591fc32d..8ef488005d52a27 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsAudio.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkParticipantsAudio component (React Library)
 products:
   - realtime
 ---
-
 A component which plays all the audio from participants and screenshares.
 
 ## Properties
 
-| Property             | Type               | Required | Default           | Description                 |
-| -------------------- | ------------------ | -------- | ----------------- | --------------------------- |
-| `iconPack`           | `IconPack`         | ❌       | `defaultIconPack` | Icon pack                   |
-| `meeting`            | `Meeting`          | ✅       | -                 | Meeting object              |
-| `preloadedAudioElem` | `HTMLAudioElement` | ✅       | -                 | Pass existing audio element |
-| `t`                  | `RtkI18n`          | ❌       | `useLanguage()`   | Language                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `preloadedAudioElem` | `HTMLAudioElement` | ✅ | - | Pass existing audio element |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsAudio />;
+  return <RtkParticipantsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsAudio
-			meeting={meeting}
-			preloadedAudioElem={htmlaudioelement}
-		/>
-	);
+  return (
+    <RtkParticipantsAudio
+      meeting={meeting}
+      preloadedAudioElem={htmlaudioelement}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
index 135d60ff19db841..b00d785b2acf701 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageList.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkParticipantsStageList component (React Library
 products:
   - realtime
 ---
-
 A component which lists all participants, with ability to
-run privileged actions on each participant according to your permissions.
+ run privileged actions on each participant according to your permissions.
 
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                          |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------------ |
-| `config`     | `UIConfig`             | ❌       | `createDefaultConfig()` | Config                               |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Stage Participants Count Header |
-| `iconPack`   | `IconPack`             | ❌       | `defaultIconPack`       | Icon pack                            |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                       |
-| `search`     | `string`               | ✅       | -                       | Search                               |
-| `size`       | `Size`                 | ✅       | -                       | Size                                 |
-| `states`     | `States1`              | ✅       | -                       | Meeting object                       |
-| `t`          | `RtkI18n`              | ❌       | `useLanguage()`         | Language                             |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list      |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Stage Participants Count Header |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsStageList />;
+  return <RtkParticipantsStageList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsStageList
-			hideHeader={true}
-			meeting={meeting}
-			search="example"
-		/>
-	);
+  return (
+    <RtkParticipantsStageList
+      hideHeader={true}
+      meeting={meeting}
+      search="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
index 8528f80bb052dd6..4e41381ce80f30a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsStageQueue.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsStageQueue component (React Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsStageQueue />;
+  return <RtkParticipantsStageQueue />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsStageQueue } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsStageQueue } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsStageQueue
-			meeting={meeting}
-			size="md"
-			view={participantsviewmode}
-		/>
-	);
+  return (
+    <RtkParticipantsStageQueue
+      meeting={meeting}
+      size="md"
+      view={participantsviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
index 0301d934942ee7a..9c8fdaf5ece9fe4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsToggle.mdx
@@ -5,46 +5,48 @@ description: API reference for RtkParticipantsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of participants.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "participants";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'participants' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsToggle />;
+  return <RtkParticipantsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkParticipantsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
index a8153f7ffc87a99..2122d23e95a3666 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsViewerList.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkParticipantsViewerList component (React Librar
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property     | Type                   | Required | Default                 | Description                     |
-| ------------ | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`     | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `hideHeader` | `boolean`              | ✅       | -                       | Hide Viewer Count Header        |
-| `iconPack`   | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`    | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `search`     | `string`               | ✅       | -                       | Search                          |
-| `size`       | `Size1`                | ✅       | -                       | Size                            |
-| `t`          | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`       | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `hideHeader` | `boolean` | ✅ | - | Hide Viewer Count Header |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `search` | `string` | ✅ | - | Search |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsViewerList />;
+  return <RtkParticipantsViewerList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsViewerList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsViewerList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsViewerList
-			hideHeader={true}
-			meeting={meeting}
-			search="example"
-		/>
-	);
+  return (
+    <RtkParticipantsViewerList
+      hideHeader={true}
+      meeting={meeting}
+      search="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
index 4649b0bfc0e82fd..3a889887010026a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkParticipantsWaitingList.mdx
@@ -5,42 +5,42 @@ description: API reference for RtkParticipantsWaitingList component (React Libra
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                   | Required | Default                 | Description                     |
-| ---------- | ---------------------- | -------- | ----------------------- | ------------------------------- |
-| `config`   | `UIConfig1`            | ❌       | `createDefaultConfig()` | Config                          |
-| `iconPack` | `IconPack1`            | ❌       | `defaultIconPack`       | Icon pack                       |
-| `meeting`  | `Meeting`              | ✅       | -                       | Meeting object                  |
-| `size`     | `Size1`                | ✅       | -                       | Size                            |
-| `t`        | `RtkI18n1`             | ❌       | `useLanguage()`         | Language                        |
-| `view`     | `ParticipantsViewMode` | ✅       | -                       | View mode for participants list |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `view` | `ParticipantsViewMode` | ✅ | - | View mode for participants list |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkParticipantsWaitingList />;
+  return <RtkParticipantsWaitingList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkParticipantsWaitingList } from "@cloudflare/realtimekit-react-ui";
+import { RtkParticipantsWaitingList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkParticipantsWaitingList
-			meeting={meeting}
-			size="md"
-			view={participantsviewmode}
-		/>
-	);
+  return (
+    <RtkParticipantsWaitingList
+      meeting={meeting}
+      size="md"
+      view={participantsviewmode}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
index d775d0fe83a22f1..3772370f932a5c4 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPermissionsMessage.mdx
@@ -5,37 +5,41 @@ description: API reference for RtkPermissionsMessage component (React Library)
 products:
   - realtime
 ---
-
 A component which shows permission related troubleshooting
-information.
+ information.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon Pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPermissionsMessage />;
+  return <RtkPermissionsMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPermissionsMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkPermissionsMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPermissionsMessage meeting={meeting} />;
+  return (
+    <RtkPermissionsMessage
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
index 3204dca64827f0c..6ec7ca9cc8718b2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector.mdx
@@ -5,33 +5,37 @@ description: API reference for RtkPinnedMessageSelector component (React Library
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPinnedMessageSelector />;
+  return <RtkPinnedMessageSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPinnedMessageSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkPinnedMessageSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPinnedMessageSelector meeting={meeting} />;
+  return (
+    <RtkPinnedMessageSelector
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
index 7fa13266f256c40..2c97be980f7bfe7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPipToggle.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkPipToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default                 | Description    |
-| ---------- | ------------------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig1`         | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                       | Meeting object |
-| `size`     | `Size1`             | ✅       | -                       | Size           |
-| `states`   | `States1`           | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`         | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                       | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPipToggle />;
+  return <RtkPipToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPipToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPipToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPipToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPipToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
index c3e69d48c2363ad..558894132225b7a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginMain.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkPluginMain component (React Library)
 products:
   - realtime
 ---
-
 A component which loads a plugin.
 
 ## Properties
 
-| Property   | Type        | Required | Default           | Description |
-| ---------- | ----------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack`  | ❌       | `defaultIconPack` | Icon pack   |
-| `meeting`  | `Meeting`   | ✅       | -                 | Meeting     |
-| `plugin`   | `RTKPlugin` | ✅       | -                 | Plugin      |
-| `t`        | `RtkI18n`   | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting |
+| `plugin` | `RTKPlugin` | ✅ | - | Plugin |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginMain />;
+  return <RtkPluginMain />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginMain } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginMain } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginMain meeting={meeting} plugin={rtkplugin} />;
+  return (
+    <RtkPluginMain
+      meeting={meeting}
+      plugin={rtkplugin}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
index d965a8cd11d84f3..6deb86e4607c003 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPlugins.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkPlugins component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins from their preset,
-and ability to enable or disable plugins.
+ and ability to enable or disable plugins.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
+import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPlugins />;
+  return <RtkPlugins />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPlugins } from "@cloudflare/realtimekit-react-ui";
+import { RtkPlugins } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPlugins meeting={meeting} size="md" />;
+  return (
+    <RtkPlugins
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
index ea36e607b88f055..68b70c406caf1cc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPluginsToggle.mdx
@@ -5,46 +5,48 @@ description: API reference for RtkPluginsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of plugins.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "plugins";
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'plugins' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginsToggle />;
+  return <RtkPluginsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPluginsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPluginsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPluginsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPluginsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
index 3005624ec80b0f9..aa4fe6fd115a016 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPoll.mdx
@@ -5,40 +5,44 @@ description: API reference for RtkPoll component (React Library)
 products:
   - realtime
 ---
-
 A poll component.
-Shows a poll where a user can vote.
+ Shows a poll where a user can vote.
 
 ## Properties
 
-| Property      | Type                   | Required | Default           | Description        |
-| ------------- | ---------------------- | -------- | ----------------- | ------------------ |
-| `iconPack`    | `IconPack`             | ❌       | `defaultIconPack` | Icon pack          |
-| `permissions` | `RTKPermissionsPreset` | ✅       | -                 | Permissions Object |
-| `poll`        | `Poll`                 | ✅       | -                 | Poll               |
-| `self`        | `string`               | ✅       | -                 | Self ID            |
-| `t`           | `RtkI18n`              | ❌       | `useLanguage()`   | Language           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `permissions` | `RTKPermissionsPreset` | ✅ | - | Permissions Object |
+| `poll` | `Poll` | ✅ | - | Poll |
+| `self` | `string` | ✅ | - | Self ID |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
+import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPoll />;
+  return <RtkPoll />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPoll } from "@cloudflare/realtimekit-react-ui";
+import { RtkPoll } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkPoll permissions={rtkpermissionspreset} poll={poll} self="example" />
-	);
+  return (
+    <RtkPoll
+      permissions={rtkpermissionspreset}
+      poll={poll}
+      self="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
index e875461eed40218..83cc1ae5190f3c2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollForm.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkPollForm component (React Library)
 products:
   - realtime
 ---
-
 A component that lets you create a poll.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollForm />;
+  return <RtkPollForm />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollForm } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollForm } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollForm iconPack={defaultIconPack} t={rtki18n} />;
+  return (
+    <RtkPollForm
+      iconPack={defaultIconPack}
+      t={rtki18n}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
index d6c56afb6b26cca..4277a2b47bfdace 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPolls.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkPolls component (React Library)
 products:
   - realtime
 ---
-
 A component which lists all available plugins a user can access with
-the ability to enable or disable them as per their permissions.
+ the ability to enable or disable them as per their permissions.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
+import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPolls />;
+  return <RtkPolls />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPolls } from "@cloudflare/realtimekit-react-ui";
+import { RtkPolls } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPolls meeting={meeting} size="md" />;
+  return (
+    <RtkPolls
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
index ce797b91301661d..f50a1cdaceb586b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkPollsToggle.mdx
@@ -5,47 +5,49 @@ description: API reference for RtkPollsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of polls.
-You need to pass the `meeting` object to it to see the unread polls count badge.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSidebar: boolean;
-	sidebar: "polls";
-}
-```
+ You need to pass the `meeting` object to it to see the unread polls count badge.
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSidebar: boolean; sidebar: 'polls' }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollsToggle />;
+  return <RtkPollsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkPollsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkPollsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkPollsToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkPollsToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
index 80fd74b508c85d2..5c2762db23494d2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingIndicator.mdx
@@ -5,37 +5,42 @@ description: API reference for RtkRecordingIndicator component (React Library)
 products:
   - realtime
 ---
-
 A component which indicates the recording status of a meeting.
-It will not render anything if no recording is taking place.
+ It will not render anything if no recording is taking place.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingIndicator />;
+  return <RtkRecordingIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkRecordingIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
index 37ff40da4c4e3e2..0f80e38da1040bc 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkRecordingToggle.mdx
@@ -5,41 +5,47 @@ description: API reference for RtkRecordingToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles recording state of a meeting.
-Only a privileged user can perform this action,
-thus the button will not be visible for participants
-who don't have the permission to record a meeting.
+ Only a privileged user can perform this action,
+ thus the button will not be visible for participants
+ who don't have the permission to record a meeting.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description        |
-| ---------- | ------------------- | -------- | ----------------- | ------------------ |
-| `disabled` | `boolean`           | ✅       | -                 | Disable the button |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack          |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object     |
-| `size`     | `Size`              | ✅       | -                 | Size               |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language           |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant            |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `disabled` | `boolean` | ✅ | - | Disable the button |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingToggle />;
+  return <RtkRecordingToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkRecordingToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkRecordingToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkRecordingToggle disabled={true} meeting={meeting} size="md" />;
+  return (
+    <RtkRecordingToggle
+      disabled={true}
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
index f2af8f3196dc19e..52908befd7de5b5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkScreenShareToggle.mdx
@@ -5,38 +5,44 @@ description: API reference for RtkScreenShareToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles your screenshare.
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size`              | ✅       | -                 | Size           |
-| `states`   | `States`            | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkScreenShareToggle />;
+  return <RtkScreenShareToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkScreenShareToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkScreenShareToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkScreenShareToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkScreenShareToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
index 71105173b22229f..2b52d0ae178ce6d 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettings.mdx
@@ -5,38 +5,43 @@ description: API reference for RtkSettings component (React Library)
 products:
   - realtime
 ---
-
 A settings component to see and change your audio/video devices
-as well as see your connection quality.
+ as well as see your connection quality.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettings />;
+  return <RtkSettings />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettings } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettings } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettings meeting={meeting} size="md" />;
+  return (
+    <RtkSettings
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
index 3519e84e54fc498..81dfd8b2b09dd43 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsAudio.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkSettingsAudio component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsAudio />;
+  return <RtkSettingsAudio />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsAudio } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsAudio } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsAudio meeting={meeting} size="md" />;
+  return (
+    <RtkSettingsAudio
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
index d3a027941137787..be09e3aaa6d7c96 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsToggle.mdx
@@ -5,44 +5,46 @@ description: API reference for RtkSettingsToggle component (React Library)
 products:
   - realtime
 ---
-
 A button which toggles visibility of settings module.
-When clicked it emits a `rtkStateUpdate` event with the data:
-
-```ts
-{
-	activeSettings: boolean;
-}
-```
+ When clicked it emits a `rtkStateUpdate` event with the data:
+ ```ts
+ { activeSettings: boolean; }
+ ```
 
 ## Properties
 
-| Property   | Type                | Required | Default           | Description   |
-| ---------- | ------------------- | -------- | ----------------- | ------------- |
-| `iconPack` | `IconPack`          | ❌       | `defaultIconPack` | Icon pack     |
-| `size`     | `Size`              | ✅       | -                 | Size          |
-| `states`   | `States`            | ✅       | -                 | States object |
-| `t`        | `RtkI18n`           | ❌       | `useLanguage()`   | Language      |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsToggle />;
+  return <RtkSettingsToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsToggle size="md" variant="button" />;
+  return (
+    <RtkSettingsToggle
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
index 004752677fc71bb..e8ecedcb858f5f0 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSettingsVideo.mdx
@@ -5,46 +5,50 @@ description: API reference for RtkSettingsVideo component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your camera devices and your video preferences.
-Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
-
-```ts
-{
-	prefs: {
-		mirrorVideo: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for toggling mirroring of self video:
+ ```ts
+ {
+  prefs: {
+    mirrorVideo: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size`     | ✅       | -                 | Size           |
-| `states`   | `States`   | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsVideo />;
+  return <RtkSettingsVideo />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSettingsVideo } from "@cloudflare/realtimekit-react-ui";
+import { RtkSettingsVideo } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSettingsVideo meeting={meeting} size="md" />;
+  return (
+    <RtkSettingsVideo
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
index 9425271184560e0..b7d2b949edf7209 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSetupScreen.mdx
@@ -5,39 +5,44 @@ description: API reference for RtkSetupScreen component (React Library)
 products:
   - realtime
 ---
-
 A screen shown before joining the meeting, where you can edit your display name,
-and media settings.
+ and media settings.
 
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `size`     | `Size`     | ✅       | -                       | Size           |
-| `states`   | `States`   | ✅       | -                       | States object  |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSetupScreen />;
+  return <RtkSetupScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSetupScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkSetupScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSetupScreen meeting={meeting} size="md" />;
+  return (
+    <RtkSetupScreen
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
index a911ce5c3815222..1304726dd69f9a7 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebar.mdx
@@ -5,48 +5,48 @@ description: API reference for RtkSidebar component (React Library)
 products:
   - realtime
 ---
-
 A component which handles the sidebar and
-you can customize which sections you want, and which section you want as the default.
+ you can customize which sections you want, and which section you want as the default.
 
 ## Properties
 
-| Property          | Type                | Required | Default                 | Description                 |
-| ----------------- | ------------------- | -------- | ----------------------- | --------------------------- |
-| `config`          | `UIConfig`          | ❌       | `createDefaultConfig()` | Config                      |
-| `defaultSection`  | `RtkSidebarSection` | ✅       | -                       | Default section             |
-| `enabledSections` | `RtkSidebarTab[]`   | ✅       | -                       | Enabled sections in sidebar |
-| `iconPack`        | `IconPack`          | ❌       | `defaultIconPack`       | Icon pack                   |
-| `meeting`         | `Meeting`           | ✅       | -                       | Meeting object              |
-| `size`            | `Size`              | ✅       | -                       | Size                        |
-| `states`          | `States`            | ✅       | -                       | States object               |
-| `t`               | `RtkI18n`           | ❌       | `useLanguage()`         | Language                    |
-| `view`            | `RtkSidebarView`    | ✅       | -                       | View type                   |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `defaultSection` | `RtkSidebarSection` | ✅ | - | Default section |
+| `enabledSections` | `RtkSidebarTab[]` | ✅ | - | Enabled sections in sidebar |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `view` | `RtkSidebarView` | ✅ | - | View type |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSidebar />;
+  return <RtkSidebar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebar } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSidebar
-			defaultSection={rtksidebarsection}
-			enabledSections={[]}
-			meeting={meeting}
-		/>
-	);
+  return (
+    <RtkSidebar
+      defaultSection={rtksidebarsection}
+      enabledSections={[]}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
index 476c5b291b984ca..01b17c6dd9ffc5a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSidebarUi.mdx
@@ -5,44 +5,44 @@ description: API reference for RtkSidebarUi component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property           | Type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Required | Default         | Description                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------- |
-| `currentTab`       | `string`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ✅       | -               | Default tab to open                      |
-| `focusCloseButton` | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Option to focus close button when opened |
-| `hideCloseAction`  | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Close Action                        |
-| `hideHeader`       | `boolean`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ✅       | -               | Hide Main Header                         |
-| `iconPack`         | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅       | -               | Icon Pack                                |
-| `t`                | `RtkI18n1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ❌       | `useLanguage()` | Language                                 |
-| `tabs`             | `RtkSidebarTab1[]`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ✅       | -               | Tabs                                     |
-| `view`             | `RtkSidebarView1`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ✅       | -               | View                                     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `currentTab` | `string` | ✅ | - | Default tab to open |
+| `focusCloseButton` | `boolean` | ✅ | - | Option to focus close button when opened |
+| `hideCloseAction` | `boolean` | ✅ | - | Hide Close Action |
+| `hideHeader` | `boolean` | ✅ | - | Hide Main Header |
+| `iconPack` | `{ people: string; people_checked: string; chat: string; poll: string; participants: string; rocket: string; call_end: string; share: string; mic_on: string; mic_off: string; video_on: string; video_off: string; share_screen_start: string; share_screen_stop: string; share_screen_person: string; clock: string; dismiss: string; send: string; search: string; more_vertical: string; chevron_down: string; chevron_up: string; chevron_left: string; chevron_right: string; settings: string; wifi: string; speaker: string; speaker_off: string; download: string; full_screen_maximize: string; full_screen_minimize: string; copy: string; attach: string; image: string; emoji_multiple: string; image_off: string; disconnected: string; wand: string; recording: string; subtract: string; stop_recording: string; warning: string; pin: string; pin_off: string; spinner: string; breakout_rooms: string; add: string; shuffle: string; edit: string; delete: string; back: string; save: string; web: string; checkmark: string; spotlight: string; join_stage: string; leave_stage: string; pip_off: string; pip_on: string; signal_1: string; signal_2: string; signal_3: string; signal_4: string; signal_5: string; start_livestream: string; stop_livestream: string; viewers: string; debug: string; info: string; devices: string; horizontal_dots: string; ai_sparkle: string; meeting_ai: string; captionsOn: string; captionsOff: string; play: string; pause: string; fastForward: string; minimize: string; maximize: string; }` | ✅ | - | Icon Pack |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `tabs` | `RtkSidebarTab1[]` | ✅ | - | Tabs |
+| `view` | `RtkSidebarView1` | ✅ | - | View |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSidebarUi />;
+  return <RtkSidebarUi />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSidebarUi } from "@cloudflare/realtimekit-react-ui";
+import { RtkSidebarUi } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSidebarUi
-			currentTab="example"
-			focusCloseButton={true}
-			hideCloseAction={true}
-		/>
-	);
+  return (
+    <RtkSidebarUi
+      currentTab="example"
+      focusCloseButton={true}
+      hideCloseAction={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
index 000057d63bf902c..1a39406c2ae6fc3 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSimpleGrid.mdx
@@ -5,41 +5,47 @@ description: API reference for RtkSimpleGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component which renders only the participants in a simple grid.
 
 ## Properties
 
-| Property       | Type       | Required | Default                 | Description                                             |
-| -------------- | ---------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`  | `string`   | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`       | `UIConfig` | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`          | `number`   | ✅       | -                       | Gap between participant tiles                           |
-| `iconPack`     | `IconPack` | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `meeting`      | `Meeting`  | ✅       | -                       | Meeting object                                          |
-| `participants` | `Peer[]`   | ✅       | -                       | Participants                                            |
-| `size`         | `Size`     | ✅       | -                       | Size                                                    |
-| `states`       | `States`   | ✅       | -                       | States object                                           |
-| `t`            | `RtkI18n`  | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSimpleGrid />;
+  return <RtkSimpleGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSimpleGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSimpleGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSimpleGrid aspectRatio="example" gap={42} meeting={meeting} />;
+  return (
+    <RtkSimpleGrid
+      aspectRatio="example"
+      gap={42}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
index 04e2e6cc9985238..ef6967aefdd7575 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpeakerSelector.mdx
@@ -5,53 +5,52 @@ description: API reference for RtkSpeakerSelector component (React Library)
 products:
   - realtime
 ---
-
 A component which lets to manage your audio devices and audio preferences.
-Emits `rtkStateUpdate` event with data for muting notification sounds:
-
-```ts
-{
-	prefs: {
-		muteNotificationSounds: boolean;
-	}
-}
-```
+ Emits `rtkStateUpdate` event with data for muting notification sounds:
+ ```ts
+ {
+  prefs: {
+    muteNotificationSounds: boolean
+  }
+ }
+ ```
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description    |
-| ---------- | -------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object |
-| `size`     | `Size`               | ✅       | -                 | Size           |
-| `states`   | `States`             | ✅       | -                 | States object  |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `'full' \| 'inline'` | ✅       | -                 | variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `'full' \| 'inline'` | ✅ | - | variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpeakerSelector />;
+  return <RtkSpeakerSelector />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpeakerSelector } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpeakerSelector } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkSpeakerSelector
-			meeting={meeting}
-			size="md"
-			variant={"full" | "inline"}
-		/>
-	);
+  return (
+    <RtkSpeakerSelector
+      meeting={meeting}
+      size="md"
+      variant={'full' | 'inline'}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
index 28454314a99f114..f465d60658ede2a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpinner.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkSpinner component (React Library)
 products:
   - realtime
 ---
-
 A component which shows an animating spinner.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `size`     | `Size1`    | ✅       | -                 | Size        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `size` | `Size1` | ✅ | - | Size |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpinner />;
+  return <RtkSpinner />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpinner } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpinner } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpinner size="md" />;
+  return (
+    <RtkSpinner
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
index 78418e203326306..0bf9ca54bc892c6 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightGrid.mdx
@@ -5,48 +5,53 @@ description: API reference for RtkSpotlightGrid component (React Library)
 products:
   - realtime
 ---
-
 A grid component that renders two lists of participants: `pinnedParticipants` and `participants`.
-You can customize the layout to a `column` view, by default is is `row`.
-
-- Participants from `pinnedParticipants[]` are rendered inside a larger grid.
-- Participants from `participants[]` array are rendered in a smaller grid.
+ You can customize the layout to a `column` view, by default is is `row`.
+ - Participants from `pinnedParticipants[]` are rendered inside a larger grid.
+ - Participants from `participants[]` array are rendered in a smaller grid.
 
 ## Properties
 
-| Property             | Type          | Required | Default                 | Description                                             |
-| -------------------- | ------------- | -------- | ----------------------- | ------------------------------------------------------- |
-| `aspectRatio`        | `string`      | ✅       | -                       | Aspect Ratio of participant tile Format: `width:height` |
-| `config`             | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config                                               |
-| `gap`                | `number`      | ✅       | -                       | Gap between participant tiles                           |
-| `gridSize`           | `GridSize1`   | ✅       | -                       | Grid size                                               |
-| `iconPack`           | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack                                               |
-| `layout`             | `GridLayout1` | ✅       | -                       | Grid Layout                                             |
-| `meeting`            | `Meeting`     | ✅       | -                       | Meeting object                                          |
-| `participants`       | `Peer[]`      | ✅       | -                       | Participants                                            |
-| `pinnedParticipants` | `Peer[]`      | ✅       | -                       | Pinned Participants                                     |
-| `size`               | `Size`        | ✅       | -                       | Size                                                    |
-| `states`             | `States`      | ✅       | -                       | States object                                           |
-| `t`                  | `RtkI18n`     | ❌       | `useLanguage()`         | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `aspectRatio` | `string` | ✅ | - | Aspect Ratio of participant tile  Format: `width:height` |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `gap` | `number` | ✅ | - | Gap between participant tiles |
+| `gridSize` | `GridSize1` | ✅ | - | Grid size |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `participants` | `Peer[]` | ✅ | - | Participants |
+| `pinnedParticipants` | `Peer[]` | ✅ | - | Pinned Participants |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightGrid />;
+  return <RtkSpotlightGrid />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightGrid } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightGrid } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightGrid aspectRatio="example" gap={42} gridSize="md" />;
+  return (
+    <RtkSpotlightGrid
+      aspectRatio="example"
+      gap={42}
+      gridSize="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
index 4777d387761bd9c..6b3cf9e708c5b27 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSpotlightIndicator.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkSpotlightIndicator component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default           | Description    |
-| ---------- | ---------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                 | Meeting object |
-| `size`     | `Size1`    | ✅       | -                 | Size           |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightIndicator />;
+  return <RtkSpotlightIndicator />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSpotlightIndicator } from "@cloudflare/realtimekit-react-ui";
+import { RtkSpotlightIndicator } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSpotlightIndicator meeting={meeting} size="md" />;
+  return (
+    <RtkSpotlightIndicator
+      meeting={meeting}
+      size="md"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
index 317f51dde0bca13..2d45d987a733a92 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStage.mdx
@@ -5,35 +5,40 @@ description: API reference for RtkStage component (React Library)
 products:
   - realtime
 ---
-
 A component used as a stage that commonly houses
-the `grid` and `sidebar` components.
+ the `grid` and `sidebar` components.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description |
-| ---------- | ---------- | -------- | ----------------- | ----------- |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack   |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStage />;
+  return <RtkStage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStage } from "@cloudflare/realtimekit-react-ui";
+import { RtkStage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStage iconPack={defaultIconPack} t={rtki18n} />;
+  return (
+    <RtkStage
+      iconPack={defaultIconPack}
+      t={rtki18n}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
index 348c55faae4ad7a..cb4ca66a237f1fe 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkStageToggle.mdx
@@ -5,36 +5,42 @@ description: API reference for RtkStageToggle component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type                | Required | Default           | Description    |
-| ---------- | ------------------- | -------- | ----------------- | -------------- |
-| `iconPack` | `IconPack1`         | ❌       | `defaultIconPack` | Icon pack      |
-| `meeting`  | `Meeting`           | ✅       | -                 | Meeting object |
-| `size`     | `Size1`             | ✅       | -                 | Size           |
-| `states`   | `States1`           | ✅       | -                 | States         |
-| `t`        | `RtkI18n1`          | ❌       | `useLanguage()`   | Language       |
-| `variant`  | `ControlBarVariant` | ✅       | -                 | Variant        |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size1` | ✅ | - | Size |
+| `states` | `States1` | ✅ | - | States |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language |
+| `variant` | `ControlBarVariant` | ✅ | - | Variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStageToggle />;
+  return <RtkStageToggle />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkStageToggle } from "@cloudflare/realtimekit-react-ui";
+import { RtkStageToggle } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkStageToggle meeting={meeting} size="md" variant="button" />;
+  return (
+    <RtkStageToggle
+      meeting={meeting}
+      size="md"
+      variant="button"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
index d70d8ba438e9132..45b7bebc4f42df5 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkSwitch.mdx
@@ -5,37 +5,43 @@ description: API reference for RtkSwitch component (React Library)
 products:
   - realtime
 ---
-
 A switch component which follows RTK Design System.
 
 ## Properties
 
-| Property   | Type       | Required | Default           | Description                           |
-| ---------- | ---------- | -------- | ----------------- | ------------------------------------- |
-| `checked`  | `boolean`  | ✅       | -                 | Whether the switch is enabled/checked |
-| `disabled` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack` | Icon pack                             |
-| `readonly` | `boolean`  | ✅       | -                 | Whether switch is readonly            |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`   | Language                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `checked` | `boolean` | ✅ | - | Whether the switch is enabled/checked |
+| `disabled` | `boolean` | ✅ | - | Whether switch is readonly |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `readonly` | `boolean` | ✅ | - | Whether switch is readonly |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
+import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSwitch />;
+  return <RtkSwitch />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkSwitch } from "@cloudflare/realtimekit-react-ui";
+import { RtkSwitch } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkSwitch checked={true} disabled={true} readonly={true} />;
+  return (
+    <RtkSwitch
+      checked={true}
+      disabled={true}
+      readonly={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
index d425e9836824989..4b92e54781696ee 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTabBar.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkTabBar component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property    | Type          | Required | Default                 | Description    |
-| ----------- | ------------- | -------- | ----------------------- | -------------- |
-| `activeTab` | `Tab`         | ✅       | -                       | Active tab     |
-| `config`    | `UIConfig`    | ❌       | `createDefaultConfig()` | UI Config      |
-| `iconPack`  | `IconPack`    | ❌       | `defaultIconPack`       | Icon Pack      |
-| `layout`    | `GridLayout1` | ✅       | -                       | Grid Layout    |
-| `meeting`   | `Meeting`     | ✅       | -                       | Meeting object |
-| `size`      | `Size`        | ✅       | -                       | Size           |
-| `states`    | `States`      | ✅       | -                       | States object  |
-| `t`         | `RtkI18n`     | ❌       | `useLanguage()`         | Language       |
-| `tabs`      | `Tab[]`       | ✅       | -                       | Tabs           |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `activeTab` | `Tab` | ✅ | - | Active tab |
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | UI Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon Pack |
+| `layout` | `GridLayout1` | ✅ | - | Grid Layout |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `size` | `Size` | ✅ | - | Size |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `tabs` | `Tab[]` | ✅ | - | Tabs |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
+import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTabBar />;
+  return <RtkTabBar />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTabBar } from "@cloudflare/realtimekit-react-ui";
+import { RtkTabBar } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTabBar activeTab={tab} layout={gridlayout1} meeting={meeting} />;
+  return (
+    <RtkTabBar
+      activeTab={tab}
+      layout={gridlayout1}
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
index 275064c3a0e30cf..b13d5561c20349b 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessage.mdx
@@ -5,39 +5,45 @@ description: API reference for RtkTextMessage component (React Library)
 products:
   - realtime
 ---
-
 @deprecated `rtk-text-message` is deprecated and will be removed soon. Use `rtk-text-message-view` instead.
-A component which renders a text message from chat.
+ A component which renders a text message from chat.
 
 ## Properties
 
-| Property      | Type          | Required | Default           | Description                                             |
-| ------------- | ------------- | -------- | ----------------- | ------------------------------------------------------- |
-| `iconPack`    | `IconPack`    | ❌       | `defaultIconPack` | Icon pack                                               |
-| `isContinued` | `boolean`     | ✅       | -                 | Whether the message is continued by same user           |
-| `message`     | `TextMessage` | ✅       | -                 | Text message object                                     |
-| `now`         | `Date`        | ✅       | -                 | Date object of now, to calculate distance between dates |
-| `showBubble`  | `boolean`     | ✅       | -                 | show message in bubble                                  |
-| `t`           | `RtkI18n`     | ❌       | `useLanguage()`   | Language                                                |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `isContinued` | `boolean` | ✅ | - | Whether the message is continued by same user |
+| `message` | `TextMessage` | ✅ | - | Text message object |
+| `now` | `Date` | ✅ | - | Date object of now, to calculate distance between dates |
+| `showBubble` | `boolean` | ✅ | - | show message in bubble |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessage />;
+  return <RtkTextMessage />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessage } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessage } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessage isContinued={true} message={textmessage} now={date} />;
+  return (
+    <RtkTextMessage
+      isContinued={true}
+      message={textmessage}
+      now={date}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
index 05911d805ffcb0f..181ebc339cd53d8 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTextMessageView.mdx
@@ -5,34 +5,39 @@ description: API reference for RtkTextMessageView component (React Library)
 products:
   - realtime
 ---
-
 A component which renders a text message from chat.
 
 ## Properties
 
-| Property     | Type      | Required | Default | Description                               |
-| ------------ | --------- | -------- | ------- | ----------------------------------------- |
-| `isMarkdown` | `boolean` | ✅       | -       | Renders text as markdown (default = true) |
-| `text`       | `string`  | ✅       | -       | Text message                              |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `isMarkdown` | `boolean` | ✅ | - | Renders text as markdown (default = true) |
+| `text` | `string` | ✅ | - | Text message |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessageView />;
+  return <RtkTextMessageView />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTextMessageView } from "@cloudflare/realtimekit-react-ui";
+import { RtkTextMessageView } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTextMessageView isMarkdown={true} text="example" />;
+  return (
+    <RtkTextMessageView
+      isMarkdown={true}
+      text="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
index c1621ec9cec5946..d2bfb5b64eb3958 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTooltip.mdx
@@ -5,40 +5,46 @@ description: API reference for RtkTooltip component (React Library)
 products:
   - realtime
 ---
-
 Tooltip component which follows RTK Design System.
 
 ## Properties
 
-| Property    | Type             | Required | Default | Description                      |
-| ----------- | ---------------- | -------- | ------- | -------------------------------- |
-| `delay`     | `number`         | ✅       | -       | Delay before showing the tooltip |
-| `disabled`  | `boolean`        | ✅       | -       | Disabled                         |
-| `kind`      | `TooltipKind`    | ✅       | -       | Tooltip kind                     |
-| `label`     | `string`         | ✅       | -       | Tooltip label                    |
-| `open`      | `boolean`        | ✅       | -       | Open                             |
-| `placement` | `Placement`      | ✅       | -       | Placement of menu                |
-| `size`      | `Size`           | ✅       | -       | Size                             |
-| `variant`   | `TooltipVariant` | ✅       | -       | Tooltip variant                  |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `delay` | `number` | ✅ | - | Delay before showing the tooltip |
+| `disabled` | `boolean` | ✅ | - | Disabled |
+| `kind` | `TooltipKind` | ✅ | - | Tooltip kind |
+| `label` | `string` | ✅ | - | Tooltip label |
+| `open` | `boolean` | ✅ | - | Open |
+| `placement` | `Placement` | ✅ | - | Placement of menu |
+| `size` | `Size` | ✅ | - | Size |
+| `variant` | `TooltipVariant` | ✅ | - | Tooltip variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTooltip />;
+  return <RtkTooltip />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTooltip } from "@cloudflare/realtimekit-react-ui";
+import { RtkTooltip } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTooltip delay={42} disabled={true} kind={tooltipkind} />;
+  return (
+    <RtkTooltip
+      delay={42}
+      disabled={true}
+      kind={tooltipkind}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
index bbcf034ad560898..de37a7083168217 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscript.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkTranscript component (React Library)
 products:
   - realtime
 ---
-
 A component which shows a transcript.
-You need to remove the element after you receive the
-`rtkTranscriptDismiss` event.
+ You need to remove the element after you receive the
+ `rtkTranscriptDismiss` event.
 
 ## Properties
 
-| Property     | Type                                   | Required | Default         | Description |
-| ------------ | -------------------------------------- | -------- | --------------- | ----------- |
-| `t`          | `RtkI18n`                              | ❌       | `useLanguage()` | Language    |
-| `transcript` | `Transcript & { renderedId?: string }` | ❌       | -               | Message     |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `transcript` | `Transcript & { renderedId?: string }` | ❌ | - | Message |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscript />;
+  return <RtkTranscript />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscript } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscript } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscript t={rtki18n} transcript="example" />;
+  return (
+    <RtkTranscript
+      t={rtki18n}
+      transcript="example"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
index 42bf35aa1892a1c..f0c0d8559cc445a 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkTranscripts.mdx
@@ -5,38 +5,42 @@ description: API reference for RtkTranscripts component (React Library)
 products:
   - realtime
 ---
-
 A component which handles transcripts.
-You can configure which transcripts you want to see and which ones you want to hear.
-There are also certain limits which you can set as well.
+ You can configure which transcripts you want to see and which ones you want to hear.
+ There are also certain limits which you can set as well.
 
 ## Properties
 
-| Property  | Type       | Required | Default                 | Description    |
-| --------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`  | `UIConfig` | ❌       | `createDefaultConfig()` | Config object  |
-| `meeting` | `Meeting`  | ✅       | -                       | Meeting object |
-| `states`  | `States`   | ✅       | -                       | States object  |
-| `t`       | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config object |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `states` | `States` | ✅ | - | States object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscripts />;
+  return <RtkTranscripts />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkTranscripts } from "@cloudflare/realtimekit-react-ui";
+import { RtkTranscripts } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkTranscripts meeting={meeting} />;
+  return (
+    <RtkTranscripts
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
index 539123ffabfd8ae..ae022070d0bc868 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkUiProvider.mdx
@@ -5,43 +5,43 @@ description: API reference for RtkUiProvider component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property          | Type              | Required | Default            | Description                         |
-| ----------------- | ----------------- | -------- | ------------------ | ----------------------------------- |
-| `config`          | `UIConfig1`       | ✅       | -                  | Config                              |
-| `iconPack`        | `IconPack1`       | ❌       | `defaultIconPack`  | Icon pack                           |
-| `meeting`         | `Meeting \| null` | ❌       | `null`             | Meeting                             |
-| `mode`            | `MeetingMode1`    | ✅       | -                  | Fill type                           |
-| `overrides`       | `Overrides1`      | ❌       | `defaultOverrides` | UI Kit Overrides                    |
-| `showSetupScreen` | `boolean`         | ✅       | -                  | Whether to show setup screen or not |
-| `t`               | `RtkI18n1`        | ❌       | `useLanguage()`    | Language utility                    |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig1` | ✅ | - | Config |
+| `iconPack` | `IconPack1` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting \| null` | ❌ | `null` | Meeting |
+| `mode` | `MeetingMode1` | ✅ | - | Fill type |
+| `overrides` | `Overrides1` | ❌ | `defaultOverrides` | UI Kit Overrides |
+| `showSetupScreen` | `boolean` | ✅ | - | Whether to show setup screen or not |
+| `t` | `RtkI18n1` | ❌ | `useLanguage()` | Language utility |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
+import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkUiProvider />;
+  return <RtkUiProvider />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkUiProvider } from "@cloudflare/realtimekit-react-ui";
+import { RtkUiProvider } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkUiProvider
-			config={defaultUiConfig}
-			mode={meeting}
-			showSetupScreen={true}
-		/>
-	);
+  return (
+    <RtkUiProvider
+      config={defaultUiConfig}
+      mode={meeting}
+      showSetupScreen={true}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
index 1ba972a480e5bf9..6cd926ddcacf256 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkViewerCount.mdx
@@ -5,36 +5,41 @@ description: API reference for RtkViewerCount component (React Library)
 products:
   - realtime
 ---
-
 A component which shows count of total joined participants in a meeting.
 
 ## Properties
 
-| Property   | Type                 | Required | Default           | Description          |
-| ---------- | -------------------- | -------- | ----------------- | -------------------- |
-| `iconPack` | `IconPack`           | ❌       | `defaultIconPack` | Icon pack            |
-| `meeting`  | `Meeting`            | ✅       | -                 | Meeting object       |
-| `t`        | `RtkI18n`            | ❌       | `useLanguage()`   | Language             |
-| `variant`  | `ViewerCountVariant` | ✅       | -                 | Viewer count variant |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
+| `variant` | `ViewerCountVariant` | ✅ | - | Viewer count variant |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkViewerCount />;
+  return <RtkViewerCount />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkViewerCount } from "@cloudflare/realtimekit-react-ui";
+import { RtkViewerCount } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkViewerCount meeting={meeting} variant="primary" />;
+  return (
+    <RtkViewerCount
+      meeting={meeting}
+      variant="primary"
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
index a0e877a59bc623a..5357ad00b4bb2f2 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkVirtualizedParticipantList.mdx
@@ -5,41 +5,41 @@ description: API reference for RtkVirtualizedParticipantList component (React Li
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property             | Type                           | Required | Default | Description                                              |
-| -------------------- | ------------------------------ | -------- | ------- | -------------------------------------------------------- |
-| `bufferedItemsCount` | `number`                       | ✅       | -       | Buffer items to render before and after the visible area |
-| `emptyListElement`   | `HTMLElement`                  | ✅       | -       | Element to render if list is empty                       |
-| `itemHeight`         | `number`                       | ✅       | -       | Height of each item in pixels (assumed fixed)            |
-| `items`              | `Peer1[]`                      | ✅       | -       | Items to be virtualized                                  |
-| `renderItem`         | `(item: Peer1, index: number)` | ✅       | -       | Function to render each item                             |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `bufferedItemsCount` | `number` | ✅ | - | Buffer items to render before and after the visible area |
+| `emptyListElement` | `HTMLElement` | ✅ | - | Element to render if list is empty |
+| `itemHeight` | `number` | ✅ | - | Height of each item in pixels (assumed fixed) |
+| `items` | `Peer1[]` | ✅ | - | Items to be virtualized |
+| `renderItem` | `(item: Peer1, index: number)` | ✅ | - | Function to render each item |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
+import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkVirtualizedParticipantList />;
+  return <RtkVirtualizedParticipantList />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkVirtualizedParticipantList } from "@cloudflare/realtimekit-react-ui";
+import { RtkVirtualizedParticipantList } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return (
-		<RtkVirtualizedParticipantList
-			bufferedItemsCount={42}
-			emptyListElement={htmlelement}
-			itemHeight={42}
-		/>
-	);
+  return (
+    <RtkVirtualizedParticipantList
+      bufferedItemsCount={42}
+      emptyListElement={htmlelement}
+      itemHeight={42}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
index 80ab41447906b03..7a88d11a1ddcc8e 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/RtkWaitingScreen.mdx
@@ -5,34 +5,38 @@ description: API reference for RtkWaitingScreen component (React Library)
 products:
   - realtime
 ---
-
 ## Properties
 
-| Property   | Type       | Required | Default                 | Description    |
-| ---------- | ---------- | -------- | ----------------------- | -------------- |
-| `config`   | `UIConfig` | ❌       | `createDefaultConfig()` | Config         |
-| `iconPack` | `IconPack` | ❌       | `defaultIconPack`       | Icon pack      |
-| `meeting`  | `Meeting`  | ✅       | -                       | Meeting object |
-| `t`        | `RtkI18n`  | ❌       | `useLanguage()`         | Language       |
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `config` | `UIConfig` | ❌ | `createDefaultConfig()` | Config |
+| `iconPack` | `IconPack` | ❌ | `defaultIconPack` | Icon pack |
+| `meeting` | `Meeting` | ✅ | - | Meeting object |
+| `t` | `RtkI18n` | ❌ | `useLanguage()` | Language |
 
 ## Usage Examples
 
 ### Basic Usage
 
 ```tsx
-import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkWaitingScreen />;
+  return <RtkWaitingScreen />;
 }
 ```
 
 ### With Properties
 
 ```tsx
-import { RtkWaitingScreen } from "@cloudflare/realtimekit-react-ui";
+import { RtkWaitingScreen } from '@cloudflare/realtimekit-react-ui';
 
 function MyComponent() {
-	return <RtkWaitingScreen meeting={meeting} />;
+  return (
+    <RtkWaitingScreen
+      meeting={meeting}
+    />
+  );
 }
 ```
+
diff --git a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
index 484d77e089e0389..e278b3204222b09 100644
--- a/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
+++ b/src/content/docs/realtime/realtimekit/ui-kit/api-reference/react/index.mdx
@@ -7,4 +7,4 @@ sidebar:
     hideIndex: true
 products:
   - realtime
----
+---
\ No newline at end of file
diff --git a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
index 97583e8bcbbb2dc..167875d1b34c213 100644
--- a/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
+++ b/src/content/docs/realtime/sfu/calls-vs-sfus.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-import { Aside } from "~/components";
+import { Aside } from "~/components"
 
 ## Cloudflare Realtime vs. Traditional SFUs
 
@@ -31,10 +31,7 @@ Cloudflare Realtime addresses these limitations by leveraging Cloudflare's globa
 - **Decentralized Architecture:** There are no dedicated servers for Realtime. Every server within Cloudflare's network contributes to handling Realtime, ensuring scalability and reliability. This approach mirrors the distributed nature of Cloudflare's products such as 1.1.1.1 DNS or Cloudflare's CDN.
 
 <Aside type="tip">
-	**See it in action:** Explore our [interactive Global SFU
-	visualization](https://realtime-sfu.dev-demos.workers.dev) to see how
-	participants connect to their nearest Cloudflare datacenter and how media
-	flows across the global backbone.
+**See it in action:** Explore our [interactive Global SFU visualization](https://realtime-sfu.dev-demos.workers.dev) to see how participants connect to their nearest Cloudflare datacenter and how media flows across the global backbone.
 </Aside>
 
 ## How Cloudflare Realtime Works
diff --git a/src/content/docs/realtime/sfu/changelog.mdx b/src/content/docs/realtime/sfu/changelog.mdx
index 1c9d09e442ea9d3..e41f539ea385e1c 100644
--- a/src/content/docs/realtime/sfu/changelog.mdx
+++ b/src/content/docs/realtime/sfu/changelog.mdx
@@ -12,4 +12,4 @@ import { ProductReleaseNotes } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/realtime.yaml. --> */}
 
-<ProductReleaseNotes />
+<ProductReleaseNotes />
\ No newline at end of file
diff --git a/src/content/docs/realtime/sfu/datachannels.mdx b/src/content/docs/realtime/sfu/datachannels.mdx
index f60c593ca262bb6..fb486465f76084c 100644
--- a/src/content/docs/realtime/sfu/datachannels.mdx
+++ b/src/content/docs/realtime/sfu/datachannels.mdx
@@ -22,7 +22,7 @@ DataChannels on Cloudflare Realtime can scale up to many subscribers per publish
 
 ### How to use DataChannels
 
-1. Create two Realtime sessions, one for the publisher and one for the subscribers.
+1. Create  two Realtime sessions, one for the publisher and one for the subscribers.
 2. Create a DataChannel by calling /datachannels/new with the location set to "local" and the dataChannelName set to the name of the DataChannel.
 3. Create a DataChannel by calling /datachannels/new with the location set to "remote" and the sessionId set to the sessionId of the publisher.
 4. Use the DataChannel to send data from the publisher to the subscribers.
diff --git a/src/content/docs/realtime/sfu/get-started.mdx b/src/content/docs/realtime/sfu/get-started.mdx
index 43ee74f34fe8975..c629ade1a9f321c 100644
--- a/src/content/docs/realtime/sfu/get-started.mdx
+++ b/src/content/docs/realtime/sfu/get-started.mdx
@@ -10,8 +10,10 @@ products:
 
 :::note[Before you get started:]
 
+
 You must first [create a Cloudflare account](/fundamentals/account/create-account/).
 
+
 :::
 
 ## Create your first app
@@ -19,7 +21,7 @@ You must first [create a Cloudflare account](/fundamentals/account/create-accoun
 Every Realtime App is a separate environment, so you can make one for development, staging and production versions for your product.
 Either using [Dashboard](https://dash.cloudflare.com/?to=/:account/realtime/sfu), or the [API](/api/resources/calls/subresources/sfu/methods/create/) create a Realtime App. When you create a Realtime App, you will get:
 
-- App ID
-- App Secret
+* App ID
+* App Secret
 
 These two combined will allow you to make API Realtime from your backend server to Realtime.
diff --git a/src/content/docs/realtime/sfu/limits.mdx b/src/content/docs/realtime/sfu/limits.mdx
index df32c721be0f051..b68859142236802 100644
--- a/src/content/docs/realtime/sfu/limits.mdx
+++ b/src/content/docs/realtime/sfu/limits.mdx
@@ -12,28 +12,28 @@ Understanding the limits and timeouts of Cloudflare Realtime is crucial for opti
 
 ## Free
 
-- Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
-- Data transfer from your client to Cloudflare is always free of charge.
+* Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
+* Data transfer from your client to Cloudflare is always free of charge.
 
 ## Limits
 
-- **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
+* **API Realtime per Session**: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.
 
-- **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
+* **Tracks per API Call**: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.
 
-- **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
+* **Tracks per Session**: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.
 
 ## Inactivity Timeout
 
-- **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
+* **Track Timeout**: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.
 
 ## PeerConnection Requirements
 
-- **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
+* **Session State**: For any operation on a session (e.g., pulling or pushing tracks), the PeerConnection state must be `connected`. Operations will block for up to 5 seconds awaiting this state before timing out. This ensures that only active and viable sessions are engaged in media transmission.
 
 ## Handling Connectivity Issues
 
-- **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
+* **Internet Connectivity Considerations**: The potential for internet connectivity loss between the client and Cloudflare is an operational reality that must be addressed. Implementing a detection and reconnection strategy is recommended to maintain session continuity. This could involve periodic 'heartbeat' signals to your backend server to monitor connectivity status. Upon detecting connectivity issues, automatically attempting to reconnect and establish a new session is advised. Sessions and tracks will remain available for reuse for 30 seconds before timing out, providing a brief window for reconnection attempts.
 
 Adhering to these limits and understanding the timeout behaviors will help ensure that your applications remain responsive and stable while providing a seamless user experience.
 
@@ -43,18 +43,19 @@ Cloudflare Realtime supports the following codecs:
 
 ### Supported video codecs
 
-- **H264**
-- **H265**
-- **VP8**
-- **VP9**
-- **AV1**
+* **H264**
+* **H265**
+* **VP8**
+* **VP9**
+* **AV1**
 
 ### Supported audio codecs
 
-- **Opus**
-- **G.711 PCM (A-law)**
-- **G.711 PCM (µ-law)**
+* **Opus**
+* **G.711 PCM (A-law)**
+* **G.711 PCM (µ-law)**
 
 :::note
 For external 48kHz PCM support refer to the [WebSocket adapter](/realtime/sfu/media-transport-adapters/websocket-adapter/)
 :::
+
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
index 2edd1740c70cb39..a9a0f3df0ddbf5b 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/index.mdx
@@ -47,7 +47,6 @@ graph LR
 **Adapter instance**: Each connection creates a unique instance with an `adapterId` to manage its lifecycle.
 
 **Location types**:
-
 - `local` (Ingest): Receives media from external endpoints to create new WebRTC tracks
 - `remote` (Stream): Sends media from existing WebRTC tracks to external endpoints
 
diff --git a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
index 818a1d69f4a3779..ea922e873043cc4 100644
--- a/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
+++ b/src/content/docs/realtime/sfu/media-transport-adapters/websocket-adapter.mdx
@@ -206,11 +206,11 @@ POST /v1/apps/{appId}/adapters/websocket/close
 
 ```json
 {
-	"tracks": [
-		{
-			"adapterId": "string"
-		}
-	]
+  "tracks": [
+    {
+      "adapterId": "string"
+    }
+  ]
 }
 ```
 
@@ -242,7 +242,6 @@ message Packet {
 **Ingest mode (buffer)**: Only the `payload` field is used, containing chunks of audio data.
 
 **Stream mode (egress)**:
-
 - For audio frames:
   - `sequenceNumber`: Incremental packet counter
   - `timestamp`: Timestamp for synchronization
@@ -268,14 +267,12 @@ Connects to your WebSocket endpoint:
 ### Message format
 
 #### Buffer mode (ingest)
-
 - **Binary messages**: PCM audio data in chunks
 - **Maximum message size**: 32 KB per WebSocket message
 - **Important**: Account for serialization overhead when chunking audio buffers
 - Send audio in small, frequent chunks rather than large batches
 
-#### Stream mode (egress)
-
+#### Stream mode (egress)  
 - **Binary messages**: Individual frames with metadata (audio or video)
 - Audio frames include:
   - Timestamp information
@@ -333,11 +330,11 @@ Usage counts towards your Cloudflare Realtime free tier of 1,000 GB.
 
 ## Error handling
 
-| Error Code | Description                              |
-| ---------- | ---------------------------------------- |
-| `400`      | Invalid request parameters               |
-| `404`      | Session or track not found               |
-| `503`      | Adapter not found (for close operations) |
+| Error Code | Description |
+|------------|-------------|
+| `400` | Invalid request parameters |
+| `404` | Session or track not found |
+| `503` | Adapter not found (for close operations) |
 
 ## Reference implementations
 
diff --git a/src/content/docs/realtime/sfu/sessions-tracks.mdx b/src/content/docs/realtime/sfu/sessions-tracks.mdx
index 8f88a1a807fd435..0acfcba0d460671 100644
--- a/src/content/docs/realtime/sfu/sessions-tracks.mdx
+++ b/src/content/docs/realtime/sfu/sessions-tracks.mdx
@@ -8,7 +8,7 @@ products:
   - realtime
 ---
 
-Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**, **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
+Cloudflare Realtime offers a simple yet powerful framework for building real-time experiences. At the core of this system are three key concepts: **Applications**,  **Sessions** and **Tracks**. Familiarizing yourself with these concepts is crucial for using Realtime.
 
 ## Application
 
@@ -18,17 +18,17 @@ A Realtime Application is an environment within different Sessions and Tracks ca
 
 A **Session** in Cloudflare Realtime correlates directly to a WebRTC PeerConnection. It represents the establishment of a communication channel between a client and the nearest Cloudflare data center, as determined by Cloudflare's anycast routing. Typically, a client will maintain a single Session, encompassing all communications between the client and Cloudflare.
 
-- **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
-- **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
-- **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
+* **One-to-One Mapping with PeerConnection**: Each Session is a direct representation of a WebRTC PeerConnection, facilitating real-time media data transfer.
+* **Anycast Routing**: The client connects to the closest Cloudflare data center, optimizing latency and performance.
+* **Unified Communication Channel**: A single Session can handle all types of communication between a client and Cloudflare, ensuring streamlined data flow.
 
 ## Tracks
 
 Within a Session, there can be one or more **Tracks**.
 
-- **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
-- **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
-- **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
+* **Tracks map to MediaStreamTrack**: Tracks align with the MediaStreamTrack concept, facilitating audio, video, or data transmission.
+* **Globally Unique Ids**: When you push a track to Cloudflare, it is assigned a unique ID, which can then be used to pull the track into another session elsewhere.
+* **Available globally**: The ability to push and pull tracks is central to what makes Realtime a versatile tool for real-time applications. Each track is available globally to be retrieved from any Session within an App.
 
 ## Realtime as a Programmable "Switchboard"
 
@@ -38,9 +38,9 @@ The analogy of a switchboard is apt for understanding Realtime. Historically, sw
 
 While many SFUs utilize concepts like "rooms" to manage media streams among users, this approach has scalability and flexibility limitations. Cloudflare Realtime opts for a more granular and flexible model with Sessions and Tracks, enabling a wide range of use cases:
 
-- Large-scale remote events, like 'fireside chats' with thousands of participants.
-- Interactive conversations with the ability to bring audience members "on stage."
-- Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
+* Large-scale remote events, like 'fireside chats' with thousands of participants.
+* Interactive conversations with the ability to bring audience members "on stage."
+* Educational applications where an instructor can present to multiple virtual classrooms simultaneously.
 
 ### Presence Protocol vs. Media Flow
 
diff --git a/src/content/docs/realtime/turn/custom-domains.mdx b/src/content/docs/realtime/turn/custom-domains.mdx
index 16baeeb56029ffa..9103a2e08eaf8a9 100644
--- a/src/content/docs/realtime/turn/custom-domains.mdx
+++ b/src/content/docs/realtime/turn/custom-domains.mdx
@@ -12,9 +12,9 @@ Cloudflare Realtime TURN service supports using custom domains for UDP, and TCP
 
 | Protocol      | Custom domains | Primary port | Alternate port |
 | ------------- | -------------- | ------------ | -------------- |
-| STUN over UDP | ✅             | 3478/udp     | 53/udp         |
-| TURN over UDP | ✅             | 3478/udp     | 53 udp         |
-| TURN over TCP | ✅             | 3478/tcp     | 80/tcp         |
+| STUN over UDP | ✅              | 3478/udp     | 53/udp         |
+| TURN over UDP | ✅              | 3478/udp     | 53 udp         |
+| TURN over TCP | ✅              | 3478/tcp     | 80/tcp         |
 | TURN over TLS | No             | 5349/tcp     | 443/tcp        |
 
 ## Setting up a CNAME record
@@ -23,16 +23,20 @@ To use custom domains for TURN, you must create a CNAME DNS record pointing to `
 
 :::caution
 
+
 Do not resolve the address of `turn.cloudflare.com` or `stun.cloudflare.com` or use an IP address as the value you input to your DNS record. Only CNAME records are supported.
 
+
 :::
 
 Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for custom domains.
 
 :::note
 
+
 If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
+
 :::
 
 There is no additional charge to using a custom hostname with Cloudflare Realtime TURN.
diff --git a/src/content/docs/realtime/turn/generate-credentials.mdx b/src/content/docs/realtime/turn/generate-credentials.mdx
index 3f1c3bf4bf971ac..bbb75c2c0e043bf 100644
--- a/src/content/docs/realtime/turn/generate-credentials.mdx
+++ b/src/content/docs/realtime/turn/generate-credentials.mdx
@@ -18,8 +18,8 @@ You should keep your TURN key on the server side (don't share it with the browse
 
 With a TURN key you can:
 
-- Generate TURN credentials that expire
-- Revoke previously issued TURN credentials
+* Generate TURN credentials that expire
+* Revoke previously issued TURN credentials
 
 ## Create credentials
 
@@ -36,9 +36,12 @@ The **201 (Created)** response below can then be passed on to your front-end app
 
 ```json
 {
-	"iceServers": [
+  "iceServers": [
 		{
-			"urls": ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"]
+			"urls": [
+				"stun:stun.cloudflare.com:3478",
+				"stun:stun.cloudflare.com:53"
+			]
 		},
 		{
 			"urls": [
@@ -64,9 +67,12 @@ Use `iceServers` as follows when instantiating the `RTCPeerConnection`:
 
 ```js
 const myPeerConnection = new RTCPeerConnection({
-	iceServers: [
-		{
-			urls: ["stun:stun.cloudflare.com:3478", "stun:stun.cloudflare.com:53"],
+  iceServers: [
+    {
+      urls: [
+				"stun:stun.cloudflare.com:3478",
+				"stun:stun.cloudflare.com:53"
+			]
 		},
 		{
 			urls: [
@@ -75,15 +81,14 @@ const myPeerConnection = new RTCPeerConnection({
 				"turn:turn.cloudflare.com:3478?transport=tcp",
 				"turn:turn.cloudflare.com:80?transport=tcp",
 				"turns:turn.cloudflare.com:5349?transport=tcp",
-				"turns:turn.cloudflare.com:443?transport=tcp",
-			],
-			username:
-				"bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
-			credential:
-				"ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0",
-		},
-	],
+				"turns:turn.cloudflare.com:443?transport=tcp"
+      ],
+			"username": "bc91b63e2b5d759f8eb9f3b58062439e0a0e15893d76317d833265ad08d6631099ce7c7087caabb31ad3e1c386424e3e",
+			"credential": "ebd71f1d3edbc2b0edae3cd5a6d82284aeb5c3b8fdaa9b8e3bf9cec683e0d45fe9f5b44e5145db3300f06c250a15b4a0"
+    },
+  ],
 });
+
 ```
 
 The `ttl` value can be adjusted to expire the short lived key in a certain amount of time. This value should be larger than the time you'd expect the users to use the TURN service. For example, if you're using TURN for a video conferencing app, the value should be set to the longest video call you'd expect to happen in the app.
diff --git a/src/content/docs/realtime/turn/replacing-existing.mdx b/src/content/docs/realtime/turn/replacing-existing.mdx
index 7fdfd0d0da1642f..2ed8f3af74ea916 100644
--- a/src/content/docs/realtime/turn/replacing-existing.mdx
+++ b/src/content/docs/realtime/turn/replacing-existing.mdx
@@ -14,12 +14,12 @@ If you are a existing TURN provider but would like to switch to providing Cloudf
 
 Cloudflare Realtime TURN service can reduce tangible and untangible costs associated with TURN servers:
 
-- Server costs (AWS EC2 etc)
-- Bandwidth costs (Egress, load balancing etc)
-- Time and effort to set up a TURN process and maintenance of server
-- Scaling the servers up and down
-- Maintain the TURN server with security and feature updates
-- Maintain high availability
+* Server costs (AWS EC2 etc)
+* Bandwidth costs (Egress, load balancing etc)
+* Time and effort to set up a TURN process and maintenance of server
+* Scaling the servers up and down
+* Maintain the TURN server with security and feature updates
+* Maintain high availability
 
 ## Recommendations
 
@@ -56,8 +56,8 @@ When billing for TURN usage in your application, it's crucial to understand and
 
 The sampling process in TURN analytics works on two levels:
 
-- At data collection: Usage data points may be sampled if they are generated too quickly.
-- At query time: Additional sampling may occur if the query is too complex or covers a large time range.
+* At data collection: Usage data points may be sampled if they are generated too quickly.
+* At query time: Additional sampling may occur if the query is too complex or covers a large time range.
 
 To ensure accurate billing, write a single query that sums TURN usage per customer per time period, returning a single value. Avoid using queries that list usage for multiple customers simultaneously.
 
@@ -65,16 +65,20 @@ By following these guidelines and understanding how TURN analytics handles sampl
 
 :::note
 
+
 Cloudflare Realtime only bills for traffic from Cloudflare's servers to your client, called `egressBytes`.
 
+
 :::
 
 ### Example queries
 
 :::caution[Incorrect approach example]
 
+
 Querying TURN usage for multiple customers in a single query can lead to inaccurate results. This is because the usage pattern of one customer could affect the sampling rate applied to another customer's data, potentially skewing the results.
 
+
 :::
 
 ```
diff --git a/src/content/docs/realtime/turn/rfc-matrix.mdx b/src/content/docs/realtime/turn/rfc-matrix.mdx
index b2a69b56b7450d0..88bffe6390fe56f 100644
--- a/src/content/docs/realtime/turn/rfc-matrix.mdx
+++ b/src/content/docs/realtime/turn/rfc-matrix.mdx
@@ -12,23 +12,23 @@ products:
 
 | Protocol | Support | Relevant specification                                                                                    |
 | -------- | ------- | --------------------------------------------------------------------------------------------------------- |
-| UDP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TCP      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
-| TLS      | ✅      | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| UDP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TCP      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
+| TLS      | ✅       | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                 |
 | DTLS     | No      | [draft-petithuguenin-tram-turn-dtls-00](http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00) |
 
 ## TURN client to TURN server protocols
 
-| Protocol                                        | Support                                                                                                                               | Relevant specification                                                                                               |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| TURN (base RFC)                                 | ✅                                                                                                                                    | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
+| Protocol                                        | Support                                                                                                                        | Relevant specification                                                                                               |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
+| TURN (base RFC)                                 | ✅                                                                                                                              | [RFC 5766](https://datatracker.ietf.org/doc/html/rfc5766)                                                            |
 | TURN REST API                                   | ✅ (See [FAQ](/realtime/turn/faq/#does-cloudflare-realtime-turn-support-the-expired-ietf-rfc-draft-draft-uberti-behave-turn-rest-00)) | [draft-uberti-behave-turn-rest-00](http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)                      |
-| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                                    | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
-| ALPN support for STUN & TURN                    | ✅                                                                                                                                    | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
-| TURN Bandwidth draft specs                      | No                                                                                                                                    | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
-| TURN-bis (with dual allocation) draft specs     | No                                                                                                                                    | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
-| TCP relaying TURN extension                     | No                                                                                                                                    | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
-| IPv6 extension for TURN                         | No                                                                                                                                    | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
-| oAuth third-party TURN/STUN authorization       | No                                                                                                                                    | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
-| DTLS support (for TURN)                         | No                                                                                                                                    | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
-| Mobile ICE (MICE) support                       | No                                                                                                                                    | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
+| Origin field in TURN (Multi-tenant TURN Server) | ✅                                                                                                                              | [draft-ietf-tram-stun-origin-06](https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)                         |
+| ALPN support for STUN & TURN                    | ✅                                                                                                                              | [RFC 7443](https://datatracker.ietf.org/doc/html/rfc7443)                                                            |
+| TURN Bandwidth draft specs                      | No                                                                                                                             | [draft-thomson-tram-turn-bandwidth-01](http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)              |
+| TURN-bis (with dual allocation) draft specs     | No                                                                                                                             | [draft-ietf-tram-turnbis-04](http://tools.ietf.org/html/draft-ietf-tram-turnbis-04)                                  |
+| TCP relaying TURN extension                     | No                                                                                                                             | [RFC 6062](https://datatracker.ietf.org/doc/html/rfc6062)                                                            |
+| IPv6 extension for TURN                         | No                                                                                                                             | [RFC 6156](https://datatracker.ietf.org/doc/html/rfc6156)                                                            |
+| oAuth third-party TURN/STUN authorization       | No                                                                                                                             | [RFC 7635](https://datatracker.ietf.org/doc/html/rfc7635)                                                            |
+| DTLS support (for TURN)                         | No                                                                                                                             | [draft-petithuguenin-tram-stun-dtls-00](https://datatracker.ietf.org/doc/html/draft-petithuguenin-tram-stun-dtls-00) |
+| Mobile ICE (MICE) support                       | No                                                                                                                             | [draft-wing-tram-turn-mobility-02](http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02)                      |
diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx
index 22b77e10e9ae65d..737fee4c2b7c58b 100644
--- a/src/content/docs/reference-architecture/architectures/sase.mdx
+++ b/src/content/docs/reference-architecture/architectures/sase.mdx
@@ -318,13 +318,13 @@ Organizations may also connect their network locations directly to the Cloudflar
 
 The following table summarizes the different methods of connecting networks to Cloudflare:
 
-| **Use case**                                                                                                                                           | **Recommended**                            | **Alternative solution**                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------- |
-| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)** | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment   |
-| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                         | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
-| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                         | **N/A**                                                                               |
-| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh**                        | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required      |
-| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh**                        | **N/A**                                                                               |
+| **Use case**                                                                                                                                           | **Recommended**                             | **Alternative solution**                                                                                      |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Remote users connecting to applications on private networks in a Zero Trust model (e.g. most VPN replacement scenarios)                                | **Cloudflare Tunnel (with `cloudflared`)**  | **Cloudflare WAN** Alternative option if `cloudflared` not suitable for environment                           |
+| Site-to-site connectivity between branches, headquarters, and data centers                                                                             | **Cloudflare WAN**                          | **Cloudflare Mesh** Alternative option if routing changes cannot be made at perimeter |
+| Egress traffic from physical sites or cloud environments to cloud security inspection (e.g. most common SWG and branch firewall replacement scenarios) | **Cloudflare WAN**                          | **N/A**                                                                                                       |
+| Service-initiated communication with remote users (e.g. AD or SCCM updates, DevOps workflows, VOIP)                                                    | **Cloudflare Mesh** | **Cloudflare WAN** Alternative option if inbound source IP fidelity not required                              |
+| Mesh networking and device-to-device connectivity                                                                                                      | **Cloudflare Mesh** | **N/A**                                                                                                       |
 
 Each of these methods of connecting and routing traffic can be deployed concurrently from any location. The following diagram highlights how different connectivity methods can be used in a single architecture.
 
@@ -343,8 +343,8 @@ Note the following traffic flows:
 _Note: Labels in this image may reflect a previous product name._
 
 <sub>
-	*Note: All of the endpoints connected via Cloudflare Mesh or device agent are
-	automatically assigned IP addresses from the 100.96.0.0/12 address range,
+	*Note: All of the endpoints connected via Cloudflare Mesh or device agent
+	are automatically assigned IP addresses from the 100.96.0.0/12 address range,
 	while endpoints connected to Cloudflare WAN retain their assigned RFC1918
 	private IP addresses. `cloudflared` can be deployed in any of the locations by
 	an application owner to provide hostname-based connectivity to the
diff --git a/src/content/docs/reference-architecture/architectures/security.mdx b/src/content/docs/reference-architecture/architectures/security.mdx
index f773fce4c276399..3d627ba4e4372c4 100644
--- a/src/content/docs/reference-architecture/architectures/security.mdx
+++ b/src/content/docs/reference-architecture/architectures/security.mdx
@@ -527,7 +527,7 @@ Existing private infrastructure can be complex. Cloudflare provides a variety of
 | [Cloudflare WAN](/cloudflare-wan/)                                                                            | IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                                   | Connecting existing network routers to Cloudflare. Allowing all traffic into and out of the network to go through Cloudflare.                                                       |
 | [Cloudflare One Appliance](/cloudflare-wan/configuration/appliance/)                                          | Appliance-based IPsec or GRE tunnel from networking devices to Cloudflare, routing entire network traffic.                                                   | Uses the same technology as Cloudflare WAN; however, instead of using existing networking devices, a dedicated appliance or virtual machine is used — the Cloudflare One Appliance. |
 | [cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/)                                         | Software agent deployed on servers or alongside services like Kubernetes for creating a tunnel for incoming connections to private applications or networks. | IT admins or application owners can easily install this tunnel software to expose their application to the Cloudflare network.                                                      |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                                       | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)           | Software agent deployed on servers for creating a tunnel for incoming and outgoing connections to private applications or networks.                          | Similar to cloudflared, but supports East to West traffic and is often used in place of Cloudflare WAN when there is no ability to create an IPsec tunnel from existing devices.    |
 | [WARP Desktop Agent](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                       | Software agent deployed on user devices, creating a tunnel for traffic to and from private applications and networks.                                        | Connecting end user devices like phones and laptops to be part of the Cloudflare network.                                                                                           |
 | [Cloudflare Network Interconnect](https://www.cloudflare.com/network-services/products/network-interconnect/) | Direct connection between your physical networks and Cloudflare.                                                                                             | When your applications live in the same data centers we operate in, we can connect those networks directly to Cloudflare.                                                           |
 
diff --git a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
index fb6d969b7413b35..7365c6406dda2f5 100644
--- a/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
+++ b/src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx
@@ -485,15 +485,15 @@ Now, you will learn how to secure RDP access as a private IP application:
 
 As mentioned before, private IP applications work because Cloudflare proxies the IP range across its network. The nature of this application necessitates the use of the device client, as unless the user is connected to Cloudflare (and more specifically, unless they can take advantage of the Client-to-Tunnel connectivity), they will not be able to reach non-local RFC 1918 addresses.
 
-| Traffic                                            |                                                                 |
-| :------------------------------------------------- | :-------------------------------------------------------------- |
-| Destination IP                                     | 169.254.255.254                                                 |
-| Destination Port                                   | 3389                                                            |
-| **Identity**                                       |                                                                 |
-| User Group Names                                   | Server Admins                                                   |
-| **Device Posture**                                 |                                                                 |
-| Passed Device Posture Checks                       | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
-| **Action**                                         | Allow                                                           |
+| Traffic                                  |                                                                 |
+| :--------------------------------------- | :-------------------------------------------------------------- |
+| Destination IP                           | 169.254.255.254                                                 |
+| Destination Port                         | 3389                                                            |
+| **Identity**                             |                                                                 |
+| User Group Names                         | Server Admins                                                   |
+| **Device Posture**                       |                                                                 |
+| Passed Device Posture Checks             | WARP Check (Mac OS) (File) Latest Version of macOS (OS version) |
+| **Action**                               | Allow                                                           |
 | **Enforce Cloudflare One Client session duration** | 60m0s                                                           |
 
 Defining the application here is simple, as Cloudflare automatically fills in the IP range, and you need to limit the detected protocol to RDP. However, the rules for private IP applications are slightly different. You will notice they appear as network policies under the Cloudflare Gateway menu, despite managing them in Access. Certain options, such as checking for MFA and external evaluation, do not appear here. However, these attributes can be verified when the user activates their device client and authenticates to their organization.
diff --git a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
index 6b66d65a74db8d4..dc60c3bd546f404 100644
--- a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
+++ b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
@@ -33,15 +33,15 @@ This solution supports subdomains under your own zone while also allowing your c
 
 Before looking at how Cloudflare can be configured to protect your SaaS application through your custom hostnames, it's worth reviewing the benefits of taking this approach.
 
-| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                   |
-| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                           |
-| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                |
-| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                           |
-| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                |
+| Benefit                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Minimized Downtime       | Ensure [minimal downtime](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/#minimize-downtime) not only during custom hostname migrations to Cloudflare for SaaS but also throughout the entire lifecycle of the application.                                                                                                                                                                                                                       |
+| Security and Performance | Extends Cloudflare's [security](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) and [performance](/cloudflare-for-platforms/cloudflare-for-saas/performance/) benefits to end-customers through their custom domains.                                                                                                                                                                                                                                                                               |
+| Auto-Renewal             | Automates the [renewal](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates/) and management process for custom hostname certificates.                                                                                                                                                                                                                                                                                                                    |
+| Apex Proxying            | Supports end-customers using [domain apex](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) (otherwise known as root domain) as custom hostnames. Used where your DNS service doesn't allow [CNAMEs for root domains](/dns/cname-flattening/), instead a [static IP](/byoip/address-maps/#static-ips-or-byoip) is used to allow an A record to be used.                                                                                               |
+| Smart Load Balancing     | Use the load balancer as [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) to steer traffic with [session affinity](/load-balancing/understand-basics/session-affinity/). In the context of Cloudflare for SaaS, a custom origin lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback origin.                                                                                                                    |
 | O2O                      | For end-customers who already proxy traffic through Cloudflare, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) may be required. Generally, it's recommended for those end-customers to [not proxy](/dns/proxy-status/#dns-only-records) the hostnames used by the SaaS provider. If O2O functionality is required, please review the [product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/). |
-| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                            |
+| Regional Services        | Allows [regional traffic management](/data-localization/regional-services/) to comply with data localization requirements.                                                                                                                                                                                                                                                                                                                                                                                                |
 
 ## Products included in this guide
 
diff --git a/src/content/docs/reference-architecture/diagrams/ai/index.mdx b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
index 31b853acdc50598..a86575102d8dcfa 100644
--- a/src/content/docs/reference-architecture/diagrams/ai/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/ai/index.mdx
@@ -12,6 +12,6 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
index b78ee67b330dcc6..65249beeb1e0af4 100644
--- a/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/content-delivery/index.mdx
@@ -12,6 +12,6 @@ products:
   - cache
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
index 52648681f876333..0e82981e3eafb7b 100644
--- a/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
+++ b/src/content/docs/reference-architecture/diagrams/iot/optimizing-and-securing-connected-transportation-systems.mdx
@@ -1,20 +1,7 @@
 ---
 title: Optimizing and securing connected transportation systems
 pcx_content_type: reference-architecture-diagram
-products:
-  [
-    argo-smart-routing,
-    api-shield,
-    cache,
-    ddos-protection,
-    dns-firewall,
-    load-balancing,
-    r2,
-    workers,
-    ssl,
-    waf,
-    workers-ai,
-  ]
+products: [argo-smart-routing, api-shield, cache, ddos-protection, dns-firewall, load-balancing, r2, workers, ssl, waf, workers-ai]
 sidebar:
   order: 1
   label: Connected transportation systems
@@ -42,6 +29,7 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
 2. **Cloudflare anycast network**: Cloudflare uses [anycast](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) networking and is one of the world's most connected and geographically distributed networks. Traffic is routed to the nearest Cloudflare data center, which reduces the number of network hops, dynamically adapts to changing network conditions, and ensures data takes the shortest path to its destination, minimizing latency and maximizing reliability.
 
 3. **Security services**:
+
    1. **API Shield**: Cloudflare's [API Shield](/api-shield/get-started/) protects critical APIs from unauthorized access and abuse, ensuring secure data exchange between connected systems.
    2. **Web Application Firewall (WAF)**: Cloudflare's [WAF](/waf/) helps block malicious traffic and prevent application or API vulnerabilities from being exploited, safeguarding your network, devices and applications.
    3. **DDoS Protection**: Cloudflare's [DDoS protection](/ddos-protection/about/attack-coverage/), covering the network, transport and application layer, prevents volumetric attacks that could compromise the availability of connected systems. By providing multi-layered protection, Cloudflare is able to mitigate a wide variety of DDoS threats. At lower layers, Cloudflare defends against high-volume attacks such as SYN floods, UDP floods, and other types of protocol-based disruptions that can overwhelm network resources. At the application layer, more sophisticated attacks targeting the application itself, such as HTTP floods \- which aim to exhaust server resources and disrupt user-facing services \- are blocked even in the face of [large-scale DDoS attempts](https://blog.cloudflare.com/tag/ddos-reports/).
@@ -49,6 +37,7 @@ Devices connect to Cloudflare's anycast network, which inspects and filters inco
    5. **TLS encryption**: [TLS encryption](/ssl/edge-certificates/) ensures that data exchanged across the network is protected from interception, maintaining data integrity and privacy.
 
 4. **Performance and reliability services**:
+
    1. **Content Delivery Network (CDN)**: [Distribute content](https://www.cloudflare.com/en-gb/learning/cdn/what-is-a-cdn/) efficiently across the network, reducing latency for end users by caching data closer to them.
    2. **Load balancing**: [Distribute incoming traffic](/load-balancing/get-started/quickstart/) across multiple servers or data centers, ensuring optimal resource utilization, preventing single points of failure, and improving the performance of connected systems.
    3. **Cloudflare Workers**: Our serverless compute platform, [Cloudflare Workers](/workers/), allows data processing at the edge, reducing the need for data to travel long distances and significantly reducing latency. Combined with related services like [Workers KV](/kv/get-started/) and [D1](https://www.cloudflare.com/en-gb/developer-platform/products/d1/), Cloudflare's edge-based storage solutions enable efficient data management close to the user. Workers KV allows for quick, read-heavy data access, perfect for caching configurations and frequently used data, while D1 provides a serverless SQL database for more robust storage needs. Additionally, Cloudflare's [Durable Objects](https://blog.cloudflare.com/sqlite-in-durable-objects/) help manage stateful interactions at the edge, facilitating real-time data consistency. These tools together allow for seamless data processing, storage and lazy updates to core services, minimizing back-and-forth to centralized servers and ensuring faster, more efficient performance.
diff --git a/src/content/docs/reference-architecture/diagrams/network/index.mdx b/src/content/docs/reference-architecture/diagrams/network/index.mdx
index 8d297fcb542d684..dab7f9b29c2ac8b 100644
--- a/src/content/docs/reference-architecture/diagrams/network/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/network/index.mdx
@@ -12,6 +12,6 @@ products:
   - magic-transit
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/sase/index.mdx b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
index 5a5bcdc66e7f753..952f8cbb7035014 100644
--- a/src/content/docs/reference-architecture/diagrams/sase/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/sase/index.mdx
@@ -12,6 +12,6 @@ products:
   - cloudflare-one
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/security/index.mdx b/src/content/docs/reference-architecture/diagrams/security/index.mdx
index b6a5e7116f9b9ab..6e7f959a2bf1894 100644
--- a/src/content/docs/reference-architecture/diagrams/security/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/security/index.mdx
@@ -12,6 +12,6 @@ products:
   - waf
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
index 80a5daa8d28537b..be169cd2360397e 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
@@ -1,32 +1,7 @@
 ---
 title: Fullstack applications
 pcx_content_type: reference-architecture-diagram
-products:
-  [
-    ai-gateway,
-    agents,
-    api-shield,
-    bots,
-    containers,
-    d1,
-    ddos-protection,
-    durable-objects,
-    images,
-    kv,
-    logs,
-    pages,
-    pipelines,
-    queues,
-    r2,
-    realtime,
-    ssl,
-    stream,
-    vectorize,
-    waf,
-    workflows,
-    workers,
-    workers-ai,
-  ]
+products: [ai-gateway, agents, api-shield, bots, containers, d1, ddos-protection, durable-objects, images, kv, logs, pages, pipelines, queues, r2, realtime, ssl, stream, vectorize, waf, workflows, workers, workers-ai]
 sidebar:
   order: 1
   label: Fullstack applications
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
index ec24b3e2d1e0920..fd828080d0d13a7 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/index.mdx
@@ -11,6 +11,6 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
index 37a97208f955c57..59502f5c65c9030 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/programmable-platforms.mdx
@@ -94,6 +94,7 @@ Data observability and control is crucial for security. [Outbound Workers](/clou
 1. **Management Interface**: Interact with the platform through GUI, API, or CLI interfaces.
 
 2. **Platform Processing**: Process these interactions to:
+
    - Transform and bundle code
    - Perform security checks
    - Apply configuration
diff --git a/src/content/docs/reference-architecture/diagrams/storage/index.mdx b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
index c1a8deb1e885b1a..bed6aa10ef8f5ae 100644
--- a/src/content/docs/reference-architecture/diagrams/storage/index.mdx
+++ b/src/content/docs/reference-architecture/diagrams/storage/index.mdx
@@ -11,6 +11,6 @@ products:
   - r2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/reference-architecture/implementation-guides/index.mdx b/src/content/docs/reference-architecture/implementation-guides/index.mdx
index 050e352a4e30355..2904c70b1df0a79 100644
--- a/src/content/docs/reference-architecture/implementation-guides/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/index.mdx
@@ -23,4 +23,4 @@ Implementation guides provide [step-by-step instructions](/reference-architectur
 
 ## Application Security
 
-- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
+- [Use mTLS with Cloudflare protected resources](/learning-paths/mtls/concepts/)
\ No newline at end of file
diff --git a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
index 2fdb4a789da4092..5c5f919b63c0538 100644
--- a/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
+++ b/src/content/docs/reference-architecture/implementation-guides/zero-trust/index.mdx
@@ -19,4 +19,4 @@ Zero Trust implementation guides walk you through the steps to deploy a Zero Tru
 - [Secure your Internet traffic and SaaS apps](/learning-paths/secure-internet-traffic/concepts/)
 - [Replace your VPN](/learning-paths/replace-vpn/concepts/)
 - [Deploy Zero Trust Web Access](/learning-paths/clientless-access/concepts/)
-- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
+- [Secure your email with Email security](/learning-paths/secure-your-email/concepts/)
\ No newline at end of file
diff --git a/src/content/docs/registrar/account-options/domain-contact-updates.mdx b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
index 33cc9a043acdbdd..c68e021cdb34a52 100644
--- a/src/content/docs/registrar/account-options/domain-contact-updates.mdx
+++ b/src/content/docs/registrar/account-options/domain-contact-updates.mdx
@@ -12,18 +12,18 @@ It is important that you keep your contact details accurate and up-to-date. [ICA
 
 The contact information you can update includes:
 
-- First name
-- Last name
-- Email
-- Organization
-- Phone
-- Address including City, State/Province, Postal code & Country
+* First name
+* Last name
+* Email
+* Organization
+* Phone
+* Address including City, State/Province, Postal code & Country
 
 To update your registrant contacts:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find **Default contact** and select **Edit**.
 3. Update the relevant information, and select **Save**.
@@ -32,10 +32,10 @@ To update your registrant contacts:
 
 If you change any of the following fields, Cloudflare Registrar will require a Change of Registrant approval before the changes are finalized:
 
-- First name
-- Last name
-- Organization
-- Email address
+* First name
+* Last name
+* Organization
+* Email address
 
 If you update any of the fields mentioned above, Cloudflare Registrar will send an approval email to the current registrant's email address. The approval email contains a link to a web page where the requested change may be viewed and approved or rejected. If the pending change is not approved or rejected within seven days, the request will automatically be canceled.
 
@@ -43,9 +43,11 @@ If you do not update these fields, your contact information is updated immediate
 
 :::caution[Important]
 
+
 After selecting the link in the approval email Cloudflare sends you, you have the option to accept or reject the contact changes. If you select the **Accept** button, your domain will be transfer-locked for 60 days.
 
-If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox _before_ selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
+If you do not want your domain to be locked, be sure to select the **Do not apply 60 day transfer lock** checkbox *before* selecting the **Accept** button. This applies to all supported TLDs, including `.uk`.
+
 
 :::
 
diff --git a/src/content/docs/registrar/account-options/domain-management.mdx b/src/content/docs/registrar/account-options/domain-management.mdx
index 436f7461a485b3f..b00b69c71cdde48 100644
--- a/src/content/docs/registrar/account-options/domain-management.mdx
+++ b/src/content/docs/registrar/account-options/domain-management.mdx
@@ -6,7 +6,7 @@ products:
 description: Manage your registered domains in the dashboard.
 ---
 
-import { DashButton, LinkButton } from "~/components";
+import { DashButton, LinkButton } from "~/components"
 
 ## Domain status
 
@@ -14,9 +14,9 @@ When your domain is registered with Cloudflare, you can review your domain statu
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date.
+2. From **Overview**, scroll down to **Domain Registration** to review the current expiration date. 
 3. Select **Manage domain** to review the Auto-Renew status for your domain.
 
 ## Billing information
@@ -25,7 +25,7 @@ Domain registrations will not appear in the **Active Subscriptions** section of
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to check and select **Manage**.
 3. Refer to **Registration** for information regarding your domain fees. From here, you can also opt to [renew or extend](/registrar/account-options/renew-domains/) your domain registration.
@@ -36,7 +36,7 @@ Cloudflare redacts WHOIS information from your domain by default. However, we do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to edit and select **Manage** > **Contacts**.
 3. Select **Edit** in any of the contacts you previously set up. This allows you to update the contact information for the selected domain only. It will not update the contact information for other domains within the account.
@@ -62,10 +62,10 @@ There may be instances where users may wish to delete a domain prior to expirati
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
-3. If the domain is deletable the button will be active. The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
-4. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
+3. Under the **Configuration** tab on the Manage page you will find a **Delete** button.
+4. If the domain is deletable the button will be active.  The button will be disabled if your domain cannot be deleted and you should refer to the Registrar [FAQ](/registrar/faq/#why-am-i-unable-to-delete-my-registrar-domain).
+5. Once you click the Delete button, you will be presented with a confirmation window. If you proceed, an email will be sent to all users with the Super Admin role in the account. The email contains a deletion authorization token that must be entered into the window which appears to confirm and complete the deletion.
 
 Once all steps are completed, the domain will then be scheduled for deletion. To understand more about the timelines and potential reasons why a domain cannot be deleted, refer to the Registrar [FAQ](/registrar/faq/#domain-deletions).
diff --git a/src/content/docs/registrar/account-options/icloud-domains.mdx b/src/content/docs/registrar/account-options/icloud-domains.mdx
index 51ea04635dec389..7cd576b2342f223 100644
--- a/src/content/docs/registrar/account-options/icloud-domains.mdx
+++ b/src/content/docs/registrar/account-options/icloud-domains.mdx
@@ -17,7 +17,7 @@ You will need an active iCloud+ subscription to add a custom email domain.
 
 If you want to buy a custom email domain, go to your [iCloud](https://www.icloud.com/settings/) settings and scroll down to **Custom Email Domain**.
 
----
+***
 
 ## Log in to Cloudflare
 
@@ -31,7 +31,7 @@ If you had signed up with Apple, signing into Cloudflare is as easy as clicking
 
 If you had signed up with Cloudflare, signing into Cloudflare can be done with your email and password.
 
----
+***
 
 ## Billing information
 
@@ -39,9 +39,9 @@ If you had signed up with Cloudflare, signing into Cloudflare can be done with y
 
 For domain registration, Cloudflare supports the following payment methods:
 
-- Credit Card
-- PayPal
-- Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
+* Credit Card
+* PayPal
+* Apple Pay (available if you have a wallet with a valid payment method and are using an iOS device or Safari on macOS)
 
 For domain renewals, Apple Pay does not currently support recurring payments. You can either add another payment method (Credit Card or PayPal) for automatic renewals or log into [your account](#log-in-to-cloudflare) near the renewal date and use Apple Pay.
 
@@ -51,7 +51,7 @@ Users may see a price estimate in both U.S. Dollars and a local currency. This i
 
 The final payment will be charged in US dollars.
 
----
+***
 
 ## Email issues
 
@@ -67,7 +67,7 @@ If you are not receiving emails intended for your new email address, review your
 
 If your domain has records similar to those listed above and you are still experiencing problems with your new email address, contact [Apple Support](https://support.apple.com/).
 
----
+***
 
 ## Domain website
 
@@ -80,7 +80,7 @@ If you want your domain to be a fully functioning website, you will need to:
 1. **Build your website**: Either using [Cloudflare Pages](/pages/), a website builder, or files hosted on a server.
 2. **Update your Cloudflare DNS**: To direct visitors looking for your domain name to the actual content on your website ([detailed guide](/dns/manage-dns-records/how-to/create-zone-apex/)).
 
----
+***
 
 ## Landing Page
 
@@ -92,16 +92,18 @@ If you do not want to have Landing Page enabled:
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
-2. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
-3. Scroll to Landing Page and select **Disable**.
+3. Find the domain you want to disable Landing Page for, and select **Manage** > **Configuration**.
+4. Scroll to Landing Page and select **Disable**.
 
 You now have Landing Page disabled. The page can also be re-enabled through the same process.
 
 :::note
 
+
 Customers must disable the landing page before they can add DNS records
 to point to a new website.
 
+
 :::
diff --git a/src/content/docs/registrar/account-options/index.mdx b/src/content/docs/registrar/account-options/index.mdx
index 0ad0fed63956d72..c28da7b171d3437 100644
--- a/src/content/docs/registrar/account-options/index.mdx
+++ b/src/content/docs/registrar/account-options/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Explore Cloudflare Registrar account options.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/account-options/inter-account-transfer.mdx b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
index 8089af6ebb59ebd..9ec8ed6c910675e 100644
--- a/src/content/docs/registrar/account-options/inter-account-transfer.mdx
+++ b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
@@ -15,29 +15,28 @@ This process only applies to domains which are registered with Cloudflare Regist
 
 Before proceeding, please be aware of the following:
 
-- WHOIS contact information will be moved as is.
-- No other configuration will be moved.
-- After successful move, the registration will be transfer-locked for 30 days.
-- The target account will become responsible for domain renewals going forward.
+* WHOIS contact information will be moved as is.
+* No other configuration will be moved.
+* After successful move, the registration will be transfer-locked for 30 days.
+* The target account will become responsible for domain renewals going forward.
 
 ## 1. Prepare for the move
 
 Before you request the move, you will need to do the following:
 
-- Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
-- Add the domain as a website to the new account and select a plan.
-- [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
+* Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
+* Add the domain as a website to the new account and select a plan.
+* [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
 
 The following pre-conditions must be met before the domain can be moved:
-
-- The domain must have been registered more than 10 days ago.
-- The domain must be added to the new account as a website and a plan must be selected.
-- The domain must not be administratively locked, such as being locked due to a dispute or court order.
-- The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
-- The registrant email address must be verified.
-- A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
-- DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
-- If the current zone is locked, the lock must be released.
+* The domain must have been registered more than 10 days ago.
+* The domain must be added to the new account as a website and a plan must be selected.
+* The domain must not be administratively locked, such as being locked due to a dispute or court order.
+* The domain must not have any of the following registry statuses: `pendingDelete`, `redemptionPeriod`, or `pendingTransfer`.
+* The registrant email address must be verified.
+* A pending Change of Registrant request cannot be present. If there is a pending request, it should be completed before initiating the move request.
+* DNSSEC must be turned off. It can be re-enabled on the new zone once the move completes.
+* If the current zone is locked, the lock must be released.
 
 ## 2. Submit the move request
 
diff --git a/src/content/docs/registrar/account-options/renew-domains.mdx b/src/content/docs/registrar/account-options/renew-domains.mdx
index 285bff694c78d57..dda7c66958054bd 100644
--- a/src/content/docs/registrar/account-options/renew-domains.mdx
+++ b/src/content/docs/registrar/account-options/renew-domains.mdx
@@ -21,8 +21,10 @@ If you decide you no longer need the domain, [disable auto-renew for your domain
 
 :::note[Note]
 
+
 The first auto-renew attempt will occur approximately 30 days prior to expiration. If you wish to disable auto-renew, do so at least 30 days prior to the expiration date.
 
+
 :::
 
 You can continue to keep your domain registered with Cloudflare for the time remaining until the expiration date. If you decide you want to keep the domain, enable auto-renew at any time prior to expiration.
@@ -33,7 +35,7 @@ If you want your domains to renew automatically, keep the default settings for y
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to automatically renew, and make sure the **Auto-renew** toggle is enabled.
 
@@ -45,8 +47,10 @@ If the renewal fails, you will receive an email notification and Cloudflare will
 
 :::note
 
+
 If you want to delete your domain from Cloudflare, **disable** Auto-Renew first.
 
+
 :::
 
 ## Renew a domain manually
@@ -55,7 +59,7 @@ You can renew a domain at any time. To renew a domain registered with Cloudflare
 
 1. In the Cloudflare dashboard, go to the **Manage domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to renew and select **Manage**.
 3. In **Registration** select **Renew/Extend Domain**.
@@ -68,22 +72,24 @@ Once Cloudflare validates your payment, the status of your domain changes to **R
 
 Once a domain is registered, Registrar sends the following expiration notices to the Super Admin of the domain:
 
-- A monthly email listing all domains set to renew automatically within the next 45 days.
-- A monthly email listing all domains expiring in the next 60-90 days.
+* A monthly email listing all domains set to renew automatically within the next 45 days.
+* A monthly email listing all domains expiring in the next 60-90 days.
 
 In addition to the Super Admin, the following expiration notices are sent to the WHOIS Registrant contact associated with the domain:
 
-- A weekly email listing all domains expiring within the next month.
-- A daily email listing all domains expiring in seven days.
-- An email one day after a domain expires.
-- An email 20 days after the expiration date.
+* A weekly email listing all domains expiring within the next month.
+* A daily email listing all domains expiring in seven days.
+* An email one day after a domain expires.
+* An email 20 days after the expiration date.
 
 :::note
 
+
 If you do not renew your domain before the expiration date, your domain will enter a Redemption Grace Period (RGP) for 30 days. These domains are not deleted and you can restore them to your account, but restoration may require an additional fee. You cannot transfer domains during the RGP.
 
 All renewals are final and Cloudflare will not issue refunds.
 
 When renewing a domain, additional years are always added to the current expiration date regardless of when the renewal takes place.
 
+
 :::
diff --git a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
index 9c7bbb499016c44..b699b2181413945 100644
--- a/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
+++ b/src/content/docs/registrar/account-options/transfer-out-from-cloudflare.mdx
@@ -13,9 +13,9 @@ import { DashButton } from "~/components";
 
 Cloudflare Registrar makes it easy to transfer your domain to another registrar. Be aware that ICANN rules prohibit a domain from being transferred if:
 
-- The domain has been transferred within the last 60 days;
-- The domain was registered within the last 60 days;
-- If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
+* The domain has been transferred within the last 60 days;
+* The domain was registered within the last 60 days;
+* If the WHOIS registrant information has been modified in the last 60 days (even if redacted).
 
 Follow the instructions below to transfer your domain out from Cloudflare.
 
@@ -28,7 +28,7 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 1. In the Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain you want to transfer, and select **Manage**.
 3. Select **Configuration** > **Unlock**.
@@ -37,8 +37,8 @@ Anyone with super-admin and admin permissions for a zone can also manage your do
 
 If you lose your authentication code, you can get a new one by:
 
-- Selecting the **Regenerate** button;
-- Locking the domain and repeating steps 1-6.
+* Selecting the **Regenerate** button;
+* Locking the domain and repeating steps 1-6.
 
 ## 2. Transfer to a new registrar
 
diff --git a/src/content/docs/registrar/account-options/whois-redaction.mdx b/src/content/docs/registrar/account-options/whois-redaction.mdx
index ae936db97b56984..54f84e462053f44 100644
--- a/src/content/docs/registrar/account-options/whois-redaction.mdx
+++ b/src/content/docs/registrar/account-options/whois-redaction.mdx
@@ -20,8 +20,8 @@ Cloudflare’s WHOIS service can be found at [https://rdap.cloudflare.com/](http
 
 WHOIS redaction removes most contact information categorized as personal data (such as registrant name, email address, postal address) from the published WHOIS record for a domain. These fields will read `Data Redacted`. The nameserver, domain lock information, and date records for a domain are still available publicly. The following fields will continue to show in WHOIS, due to ICANN policy:
 
-- Registrant state/province
-- Registrant country
+* Registrant state/province
+* Registrant country
 
 Cloudflare still maintains the authoritative, unredacted, record of your WHOIS data. You can modify this information at any time. Refer to [Registrant contact updates](/registrar/account-options/domain-contact-updates) for more information.
 
diff --git a/src/content/docs/registrar/custom-domain-protection.mdx b/src/content/docs/registrar/custom-domain-protection.mdx
index 7c230831d9ec50c..5175f44c6cba05f 100644
--- a/src/content/docs/registrar/custom-domain-protection.mdx
+++ b/src/content/docs/registrar/custom-domain-protection.mdx
@@ -12,8 +12,8 @@ Cloudflare offers [Custom Domain Protection](https://www.cloudflare.com/products
 
 Custom Domain Protection offers additional safeguard features for registered domains, including:
 
-- **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
-- **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
-- **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
+* **Registry lock**: Cloudflare applies Registry Lock, when available, to all domains registered through Custom Domain Protection. Any changes to a domain requires Cloudflare to first unlock the domain at the registry level.
+* **Out-of-band authentication**: All changes to domain ownership or nameserver information are verified and executed manually based on an authentication process defined by the customer.
+* **No interface**: Custom Domain Protection does not offer an interface, to remove the possibility of domain hijack through a compromised account.
 
 Contact your account team if you are interested in Cloudflare's Custom Domain Protection.
diff --git a/src/content/docs/registrar/get-started/index.mdx b/src/content/docs/registrar/get-started/index.mdx
index adddbd0c163091c..0337c455830ed00 100644
--- a/src/content/docs/registrar/get-started/index.mdx
+++ b/src/content/docs/registrar/get-started/index.mdx
@@ -8,6 +8,6 @@ products:
 description: Set up Client IP Geolocation for your network.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/registrar/get-started/register-domain.mdx b/src/content/docs/registrar/get-started/register-domain.mdx
index 7f46b29e462ccda..b3d8c632b668672 100644
--- a/src/content/docs/registrar/get-started/register-domain.mdx
+++ b/src/content/docs/registrar/get-started/register-domain.mdx
@@ -10,14 +10,15 @@ description: Register a new domain with Cloudflare.
 
 import { DashButton, Render } from "~/components";
 
+
 ## Prerequisites and restrictions
 
 :::note[Cloudflare nameservers]
 All domains acquired via Cloudflare Registrar use Cloudflare nameservers, automatically [protecting and speeding up](/fundamentals/concepts/how-cloudflare-works/) your content or services. You will not be able to change to another DNS provider's nameservers while using Cloudflare Registrar.
 :::
 
-- Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
-- You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
+* Cloudflare Registrar does not currently support internationalized domain names (IDNs), also known as Unicode.
+* You must have a [verified account email address](/fundamentals/user-profiles/verify-email-address/), to transfer or register domains.
 
 <Render file="icann-unverified-email" product="registrar" />
 
@@ -29,14 +30,16 @@ If you are registering a `.us` domain, refer to the [Additional requirements for
 
 1. In the Cloudflare dashboard, go to the **Register domains** page.
 
-   <DashButton url="/?to=/:account/registrar/register" />
+    <DashButton url="/?to=/:account/registrar/register" />
 
 2. In the search box, enter the domain name you wish to register, and select **Search**. You may also enter one or more keywords. The search results will contain a list of suggested domains. If the domain you entered does not appear in the list, this means it is not available for registration.
 
 :::caution[Important]
 
+
 Cloudflare Registrar currently does not support internationalized domain names (IDNs), also known as unicode. For that reason, you cannot search for words with special characters, such as `à`, `ü`, `ç`, among others.
 
+
 :::
 
 3. Select **Purchase** on the domain you wish to register. In rare instances, a domain that is not available for registration may appear in the search results. After selecting **Purchase**, a definitive availability check will be performed to confirm that the domain is actually available for registration.
@@ -49,10 +52,12 @@ Cloudflare Registrar currently does not support internationalized domain names (
 
 :::note
 
+
 If you have previously registered or transferred a domain name, the form will be filled in advance with the information from your default contact. If not, you will need to fill out the form.
 
 It is important that you provide complete and accurate contact information. If you do not follow this recommendation, the domain registration may be suspended and/or canceled.
 
+
 :::
 
 6. In **Payment**, select which type of payment you want to use. If you already have a billing profile, Cloudflare uses this information to automatically fill the form. If there is no billing profile, you need to enter your payment information.
@@ -67,6 +72,8 @@ The registration process may take up to 30 seconds to complete. Once the registr
 
 At this time, you can only use ASCII characters for contact data. If the default contact has non-ASCII characters, you will need to update the domain contact details before proceeding. Cloudflare recommends that you update your default contact information to include ASCII characters only.
 
+
+
 | Field        | Required? | Restrictions                                                                                                                   |
 | ------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
 | First Name   | Yes       | Minimum of two letters.                                                                                                        |
@@ -82,6 +89,8 @@ At this time, you can only use ASCII characters for contact data. If the default
 | Country      | Yes       | You must select one from the drop-down options.                                                                                |
 | Postal Code  | Yes       | Must be a properly formatted postal code.                                                                                      |
 
+
+
 When you register a domain with Cloudflare, your personal information is redacted when permitted by the registry. Refer to [WHOIS redaction](/registrar/account-options/whois-redaction/) for more information.
 
 ## Next steps
diff --git a/src/content/docs/registrar/top-level-domains/uk-domains.mdx b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
index 4ec5d8a00c26f8f..33034fbe090ae38 100644
--- a/src/content/docs/registrar/top-level-domains/uk-domains.mdx
+++ b/src/content/docs/registrar/top-level-domains/uk-domains.mdx
@@ -22,16 +22,22 @@ Cloudflare currently supports the transfer of `.uk`, `co.uk`, `org.uk`, and `me.
 
 1. In the Cloudflare dashboard, go to the **Transfer domains** page.
 
-   <DashButton url="/?to=/:account/registrar/transfer" />
+    <DashButton url="/?to=/:account/registrar/transfer" />
 
-Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain. 2. Select the domains you wish to transfer. 3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process. 4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days. 5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
+Cloudflare will show you a list of domains that are eligible for transfer (see below for restrictions). If you do not see your domain, [add the domain you want to transfer](/fundamentals/manage-domains/add-site/) to your Cloudflare account before you try to transfer your `.uk` domain.
+2. Select the domains you wish to transfer.
+3. Proceed to checkout. Note that there is no fee to transfer a `.uk` domain and an additional year is NOT added during the transfer process.
+4. After checkout, request your current registrar to update the [IPS tag](https://en.wikipedia.org/wiki/Internet_Provider_Security) to `CLOUDFLARE`. If the transfer is not completed within 24 hours, ask your registrar again to update the IPS tag. The transfer will be automatically canceled if not completed within 30 days.
+5. Cloudflare will receive a notice once your registrar updates the IPS tag. After that, we will finish transferring your domain.
 
 :::caution[Warning]
 
+
 If you request your current registrar to update the IPS tag before completing the checkout process, the transfer request will be automatically rejected. You must complete the checkout process before requesting the IPS tag update.
 
 For security reasons, domains transferred to Cloudflare Registrar are locked for 60 days before they can be transferred out to another Registrar.
 
+
 :::
 
 ## Transfer a .UK domain to another registrar
@@ -46,6 +52,8 @@ Your new registrar is responsible for accepting the transfer. Cloudflare has no
 
 :::note
 
+
 If you do not know the IPS tag, contact your new registrar for instructions. Your new registrar may require you to follow some additional steps before starting the transfer process.
 
+
 :::
diff --git a/src/content/docs/registrar/whoisrequests.mdx b/src/content/docs/registrar/whoisrequests.mdx
index 95317e78416dd66..445ca659095fc8e 100644
--- a/src/content/docs/registrar/whoisrequests.mdx
+++ b/src/content/docs/registrar/whoisrequests.mdx
@@ -10,7 +10,7 @@ description: Submit WHOIS disclosure requests to Cloudflare.
 
 This page describes the mechanism and process for submitting a disclosure request to Cloudflare for WHOIS data under Section 10 of the Internet Corporation for Assigned Names and Number's ("ICANN") [Registration Data Policy](https://www.icann.org/en/contracted-parties/consensus-policies/registration-data-policy).
 
-Please read the following instructions carefully.
+Please read the following instructions carefully.  
 
 ## 1. Prepare your request
 
@@ -18,7 +18,7 @@ Your request must include the following elements:
 
 - Your name
 - The requestor's name, mailing address, and email
-- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity. If the latter, identify whether the requestor is an individual, corporation, or government
+- Whether you are making this request on behalf of yourself as an individual or on behalf of another person or entity.  If the latter, identify whether the requestor is an individual, corporation, or government
 - Any power of Attorney statements or similar statements evidencing authorization to act on the requestor's behalf, where applicable and relevant
 - A list of data element values requested by the requestor
 - Information about the legal rights of the requestor and specific rationale and basis for the request
diff --git a/src/content/docs/resource-tagging/get-started.mdx b/src/content/docs/resource-tagging/get-started.mdx
index b9bc956239e99a5..5a8aa68ee493d82 100644
--- a/src/content/docs/resource-tagging/get-started.mdx
+++ b/src/content/docs/resource-tagging/get-started.mdx
@@ -26,13 +26,13 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys
 
 ### Interpreting the response
 
-| Response                                             | Meaning                                                            | Action                                                                                                                                                        |
-| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step.                                                                                                                                     |
-| **403** mentioning "permission" or "role"            | The caller lacks required permissions.                             | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope.                    |
-| **403** mentioning "feature" or "gate"               | Tagging is not enabled for this account.                           | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance.                                                                         |
-| **401 Unauthorized**                                 | Authentication failed.                                             | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header.                                                        |
-| Any other response                                   | Unexpected error.                                                  | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
+| Response | Meaning | Action |
+| --- | --- | --- |
+| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step. |
+| **403** mentioning "permission" or "role" | The caller lacks required permissions. | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope. |
+| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance. |
+| **401 Unauthorized** | Authentication failed. | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header. |
+| Any other response | Unexpected error. | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
 
 ## 2. Create your first tags
 
diff --git a/src/content/docs/resource-tagging/how-to/index.mdx b/src/content/docs/resource-tagging/how-to/index.mdx
index daacb0f1c1aa2d4..8c39e93b47e1641 100644
--- a/src/content/docs/resource-tagging/how-to/index.mdx
+++ b/src/content/docs/resource-tagging/how-to/index.mdx
@@ -7,6 +7,6 @@ head:
     content: How-to guides
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/how-to/manage-tags.mdx b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
index 9625cc22be99763..813ad1a57752b9b 100644
--- a/src/content/docs/resource-tagging/how-to/manage-tags.mdx
+++ b/src/content/docs/resource-tagging/how-to/manage-tags.mdx
@@ -75,9 +75,9 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags?reso
 
 ```json
 {
-	"environment": "production",
-	"team": "platform",
-	"cost-center": "engineering"
+  "environment": "production",
+  "team": "platform",
+  "cost-center": "engineering"
 }
 ```
 
diff --git a/src/content/docs/resource-tagging/reference/error-codes.mdx b/src/content/docs/resource-tagging/reference/error-codes.mdx
index 026f122644541f7..7f1cd73a0d758bf 100644
--- a/src/content/docs/resource-tagging/reference/error-codes.mdx
+++ b/src/content/docs/resource-tagging/reference/error-codes.mdx
@@ -8,19 +8,19 @@ description: Tagging API error codes, causes, and resolutions.
 
 ## Error code reference
 
-| Code   | HTTP status | Message                                        | Likely cause                                           | Resolution                                                                    |
-| ------ | ----------- | ---------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------- |
-| `1002` | 400         | Invalid set payload                            | Request body is malformed or missing required fields   | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
-| `1003` | 400         | `resource_type` and `resource_id` are required | Missing query parameters                               | Include both `resource_type` and `resource_id` in the query string            |
-| `1006` | 400         | Invalid resource type                          | Unsupported resource type                              | Use a [supported resource type](/resource-tagging/reference/resource-types/)  |
-| `1007` | 400         | tag parameter must be in format...             | Tag filter syntax is incorrect                         | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/)   |
-| `1009` | 400         | `tag_key` is required                          | Missing `tag_key` parameter                            | Include the `tag_key` path parameter                                          |
-| `1010` | 400         | too many tag filters (maximum 20)              | More than 20 `tag` query parameters                    | Reduce filters to 20 or fewer, or split across multiple requests              |
-| `1011` | 400         | tag key too long (maximum 256 characters)      | Tag key exceeds 256 characters                         | Shorten the tag key                                                           |
-| `1012` | 400         | tag value too long (maximum 1024 characters)   | Tag value exceeds 1,024 characters                     | Shorten the tag value                                                         |
-| `1013` | 400         | too many OR values in tag filter (maximum 10)  | More than 10 comma-separated values in a single filter | Split into multiple filters                                                   |
-| `1014` | 400         | Invalid tag key                                | Key contains invalid characters                        | Use only letters, digits, `_`, `.`, `-`                                       |
-| `1015` | 400         | Invalid delete payload                         | Delete request body is malformed                       | Verify the body includes `resource_type` and `resource_id`                    |
+| Code | HTTP status | Message | Likely cause | Resolution |
+| --- | --- | --- | --- | --- |
+| `1002` | 400 | Invalid set payload | Request body is malformed or missing required fields | Verify the body is valid JSON with `resource_type`, `resource_id`, and `tags` |
+| `1003` | 400 | `resource_type` and `resource_id` are required | Missing query parameters | Include both `resource_type` and `resource_id` in the query string |
+| `1006` | 400 | Invalid resource type | Unsupported resource type | Use a [supported resource type](/resource-tagging/reference/resource-types/) |
+| `1007` | 400 | tag parameter must be in format... | Tag filter syntax is incorrect | Refer to [tag filtering syntax](/resource-tagging/how-to/filter-resources/) |
+| `1009` | 400 | `tag_key` is required | Missing `tag_key` parameter | Include the `tag_key` path parameter |
+| `1010` | 400 | too many tag filters (maximum 20) | More than 20 `tag` query parameters | Reduce filters to 20 or fewer, or split across multiple requests |
+| `1011` | 400 | tag key too long (maximum 256 characters) | Tag key exceeds 256 characters | Shorten the tag key |
+| `1012` | 400 | tag value too long (maximum 1024 characters) | Tag value exceeds 1,024 characters | Shorten the tag value |
+| `1013` | 400 | too many OR values in tag filter (maximum 10) | More than 10 comma-separated values in a single filter | Split into multiple filters |
+| `1014` | 400 | Invalid tag key | Key contains invalid characters | Use only letters, digits, `_`, `.`, `-` |
+| `1015` | 400 | Invalid delete payload | Delete request body is malformed | Verify the body includes `resource_type` and `resource_id` |
 
 :::note[Error 1007 note]
 The error message text references `:` as the tag filter separator (for example, `key:value`), but the API implementation uses `=` in query parameters (for example, `tag=key=value`). The error message is outdated — always use `=` when constructing tag filters.
diff --git a/src/content/docs/resource-tagging/reference/index.mdx b/src/content/docs/resource-tagging/reference/index.mdx
index 9361dd2c4b8a0cd..6de666492e69204 100644
--- a/src/content/docs/resource-tagging/reference/index.mdx
+++ b/src/content/docs/resource-tagging/reference/index.mdx
@@ -7,6 +7,6 @@ head:
     content: Reference
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/resource-tagging/reference/limits.mdx b/src/content/docs/resource-tagging/reference/limits.mdx
index 85a5ee4696d5f45..350cb2973f6183a 100644
--- a/src/content/docs/resource-tagging/reference/limits.mdx
+++ b/src/content/docs/resource-tagging/reference/limits.mdx
@@ -8,14 +8,14 @@ description: API limits, tag key validation rules, and pagination behavior.
 
 ## API limits
 
-| Limit                         | Value            | Error code |
-| ----------------------------- | ---------------- | ---------- |
-| Maximum tags per account      | 10,000 (beta)    | N/A        |
-| Maximum tag key length        | 256 characters   | `1011`     |
-| Maximum tag value length      | 1,024 characters | `1012`     |
-| Maximum tag filters per query | 20               | `1010`     |
-| Maximum OR values per filter  | 10               | `1013`     |
-| Results per page              | 100 (fixed)      | N/A        |
+| Limit | Value | Error code |
+| --- | --- | --- |
+| Maximum tags per account | 10,000 (beta) | N/A |
+| Maximum tag key length | 256 characters | `1011` |
+| Maximum tag value length | 1,024 characters | `1012` |
+| Maximum tag filters per query | 20 | `1010` |
+| Maximum OR values per filter | 10 | `1013` |
+| Results per page | 100 (fixed) | N/A |
 
 When a limit is exceeded, the API returns `400 Bad Request` with the corresponding error code.
 
@@ -45,16 +45,16 @@ Tag keys must follow these character rules:
 
 ### Examples
 
-| Key           | Valid  | Reason                |
-| ------------- | ------ | --------------------- |
-| `environment` | Yes    | Letters only          |
-| `team_name`   | Yes    | Underscore            |
-| `cost-center` | Yes    | Hyphen                |
-| `owner.email` | Yes    | Period                |
-| `env123`      | Yes    | Letters and digits    |
-| `env name`    | **No** | Contains space        |
-| `team@work`   | **No** | Special character `@` |
-| (empty)       | **No** | Empty string          |
+| Key | Valid | Reason |
+| --- | --- | --- |
+| `environment` | Yes | Letters only |
+| `team_name` | Yes | Underscore |
+| `cost-center` | Yes | Hyphen |
+| `owner.email` | Yes | Period |
+| `env123` | Yes | Letters and digits |
+| `env name` | **No** | Contains space |
+| `team@work` | **No** | Special character `@` |
+| (empty) | **No** | Empty string |
 
 Invalid tag keys return `400 Bad Request` with error code `1014`.
 
@@ -63,7 +63,6 @@ Invalid tag keys return `400 Bad Request` with error code `1014`.
 List endpoints use cursor-based pagination with a fixed page size of 100. The page size is not configurable.
 
 Paginated endpoints:
-
 - `GET /accounts/{account_id}/tags/keys`
 - `GET /accounts/{account_id}/tags/resources`
 - `GET /accounts/{account_id}/tags/values/{tag_key}`
diff --git a/src/content/docs/resource-tagging/reference/resource-types.mdx b/src/content/docs/resource-tagging/reference/resource-types.mdx
index 0d2bab2a3ec669c..65c23a2da688ce7 100644
--- a/src/content/docs/resource-tagging/reference/resource-types.mdx
+++ b/src/content/docs/resource-tagging/reference/resource-types.mdx
@@ -12,51 +12,51 @@ The Tagging API supports the following resource types across account-level and z
 
 Use `/accounts/{account_id}/tags` endpoints for these resource types.
 
-| Resource type              | Required extra fields | Description                      |
-| -------------------------- | --------------------- | -------------------------------- |
-| `account`                  | None                  | The Cloudflare account itself    |
-| `access_application`       | None                  | Access application               |
-| `access_group`             | None                  | Access group                     |
-| `account_ruleset`          | None                  | Account-level ruleset            |
-| `ai_gateway`               | None                  | AI Gateway                       |
-| `alerting_policy`          | None                  | Notification policy              |
-| `alerting_webhook`         | None                  | Notification webhook destination |
-| `cloudflared_tunnel`       | None                  | Cloudflare Tunnel                |
-| `d1_database`              | None                  | D1 database                      |
-| `durable_object_namespace` | None                  | Durable Objects namespace        |
-| `gateway_list`             | None                  | Gateway list                     |
-| `gateway_rule`             | None                  | Gateway rule                     |
-| `image`                    | None                  | Cloudflare Image                 |
-| `kv_namespace`             | None                  | Workers KV namespace             |
-| `load_balancer_monitor`    | None                  | Load Balancer monitor            |
-| `load_balancer_pool`       | None                  | Load Balancer pool               |
-| `pages_project`            | None                  | Pages project                    |
-| `queue`                    | None                  | Queue                            |
-| `r2_bucket`                | None                  | R2 bucket                        |
-| `resource_share`           | None                  | Resource share                   |
-| `stream_live_input`        | None                  | Stream live input                |
-| `stream_video`             | None                  | Stream video                     |
-| `vectorize_index`          | None                  | Vectorize index                  |
-| `worker`                   | None                  | Workers script                   |
-| `worker_version`           | `worker_id`           | Specific version of a Worker     |
+| Resource type | Required extra fields | Description |
+| --- | --- | --- |
+| `account` | None | The Cloudflare account itself |
+| `access_application` | None | Access application |
+| `access_group` | None | Access group |
+| `account_ruleset` | None | Account-level ruleset |
+| `ai_gateway` | None | AI Gateway |
+| `alerting_policy` | None | Notification policy |
+| `alerting_webhook` | None | Notification webhook destination |
+| `cloudflared_tunnel` | None | Cloudflare Tunnel |
+| `d1_database` | None | D1 database |
+| `durable_object_namespace` | None | Durable Objects namespace |
+| `gateway_list` | None | Gateway list |
+| `gateway_rule` | None | Gateway rule |
+| `image` | None | Cloudflare Image |
+| `kv_namespace` | None | Workers KV namespace |
+| `load_balancer_monitor` | None | Load Balancer monitor |
+| `load_balancer_pool` | None | Load Balancer pool |
+| `pages_project` | None | Pages project |
+| `queue` | None | Queue |
+| `r2_bucket` | None | R2 bucket |
+| `resource_share` | None | Resource share |
+| `stream_live_input` | None | Stream live input |
+| `stream_video` | None | Stream video |
+| `vectorize_index` | None | Vectorize index |
+| `worker` | None | Workers script |
+| `worker_version` | `worker_id` | Specific version of a Worker |
 
 ## Zone-level resources
 
 Use `/zones/{zone_id}/tags` endpoints for these resource types.
 
-| Resource type                | Required extra fields   | Description                       |
-| ---------------------------- | ----------------------- | --------------------------------- |
-| `access_application_policy`  | `access_application_id` | Access application policy         |
-| `api_gateway_operation`      | None                    | API Gateway operation             |
-| `custom_certificate`         | None                    | Custom SSL certificate            |
-| `custom_hostname`            | None                    | Custom hostname (SSL for SaaS)    |
-| `dns_record`                 | None                    | DNS record                        |
-| `healthcheck`                | None                    | Health check                      |
-| `load_balancer`              | None                    | Load Balancer                     |
-| `managed_client_certificate` | None                    | Managed client certificate (mTLS) |
-| `worker_route`               | None                    | Worker route                      |
-| `zone`                       | None                    | DNS zone                          |
-| `zone_ruleset`               | None                    | Zone-level ruleset                |
+| Resource type | Required extra fields | Description |
+| --- | --- | --- |
+| `access_application_policy` | `access_application_id` | Access application policy |
+| `api_gateway_operation` | None | API Gateway operation |
+| `custom_certificate` | None | Custom SSL certificate |
+| `custom_hostname` | None | Custom hostname (SSL for SaaS) |
+| `dns_record` | None | DNS record |
+| `healthcheck` | None | Health check |
+| `load_balancer` | None | Load Balancer |
+| `managed_client_certificate` | None | Managed client certificate (mTLS) |
+| `worker_route` | None | Worker route |
+| `zone` | None | DNS zone |
+| `zone_ruleset` | None | Zone-level ruleset |
 
 ## Extra fields
 
diff --git a/src/content/docs/rules/normalization/settings.mdx b/src/content/docs/rules/normalization/settings.mdx
index 7243dde493afff1..5caa0fb2aa550f7 100644
--- a/src/content/docs/rules/normalization/settings.mdx
+++ b/src/content/docs/rules/normalization/settings.mdx
@@ -35,8 +35,8 @@ Default value: _Off_
 
 Configures URLs sent to the origin:
 
-- When enabled, requests sent to the origin are normalized.
-- When disabled, requests sent to the origin are not modified.
+  - When enabled, requests sent to the origin are normalized.
+  - When disabled, requests sent to the origin are not modified.
 
 You can only view and enable this option when **Normalize incoming URLs** is enabled.
 
diff --git a/src/content/docs/rules/snippets/when-to-use.mdx b/src/content/docs/rules/snippets/when-to-use.mdx
index 37954e262869ef1..e86e4a0e07433ec 100644
--- a/src/content/docs/rules/snippets/when-to-use.mdx
+++ b/src/content/docs/rules/snippets/when-to-use.mdx
@@ -86,7 +86,7 @@ Snippets are ideal for fast, cost-free request and response modifications at the
 | Route traffic dynamically between [origin servers](/rules/snippets/examples/serve-different-origin/)                                                                                                          |    ✅    |   ✅    |
 | [Authenticate](/rules/snippets/examples/auth-with-headers/) requests, [pre-sign](/cache/interaction-cloudflare-products/waf-snippets/) URLs, run [A/B testing](/rules/snippets/examples/ab-testing-same-url/) |    ✅    |   ✅    |
 | Define logic using [JavaScript and Web APIs](/workers/languages/javascript/)                                                                                                                                  |    ✅    |   ✅    |
-| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                           |    ❌    |   ✅    |
+| Perform compute-heavy tasks (for example, [AI](/workers-ai/), [image transformations](/images/optimization/transformations/transform-via-workers/))                                                                       |    ❌    |   ✅    |
 | Store persistent data (for example, [KV](/kv/), [Durable Objects](/durable-objects/), and [D1](/d1/))                                                                                                         |    ❌    |   ✅    |
 | Build [APIs](/d1/tutorials/build-a-comments-api/) and [full-stack applications](/pages/framework-guides/deploy-an-astro-site/#video-tutorial)                                                                 |    ❌    |   ✅    |
 | Use TypeScript, Python, Rust, or other programming [languages](/workers/languages/)                                                                                                                           |    ❌    |   ✅    |
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
index d28441888bab606..7167193080e4368 100644
--- a/src/content/docs/rules/transform/managed-transforms/reference.mdx
+++ b/src/content/docs/rules/transform/managed-transforms/reference.mdx
@@ -87,6 +87,7 @@ Turning on [IP geolocation](/network/ip-geolocation/) will send a `cf-ipcountry`
 
 Cloudflare always converts non-ASCII characters to UTF-8 in HTTP request and response header values. This applies to location headers added by the **Add visitor location headers** managed transform.
 
+
 ### Add "True-Client-IP" header
 
 :::note
diff --git a/src/content/docs/ruleset-engine/about/index.mdx b/src/content/docs/ruleset-engine/about/index.mdx
index b2b96116594e34b..4627da09be58e13 100644
--- a/src/content/docs/ruleset-engine/about/index.mdx
+++ b/src/content/docs/ruleset-engine/about/index.mdx
@@ -9,17 +9,18 @@ sidebar:
 head:
   - tag: title
     content: About Ruleset Engine
+
 ---
 
 The Cloudflare Ruleset Engine allows you to create and deploy rules and rulesets. The engine syntax, inspired by the Wireshark Display Filter language, is defined by the [Rules language](/ruleset-engine/rules-language/). Cloudflare uses the Ruleset Engine in different products, allowing you to configure several products using the same basic syntax.
 
 There are several elements involved in the configuration and use of the Ruleset Engine. These elements are:
 
-- [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
-- [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
-- [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
+* [**Phase**](/ruleset-engine/about/phases/): Defines a stage in the life of a request where you can execute rulesets.
+* [**Ruleset**](/ruleset-engine/about/rulesets/): Defines a versioned set of rules. You deploy rulesets to a phase, where they execute.
+* [**Rule**](/ruleset-engine/about/rules/): Defines a filter and an action to perform on incoming requests that match the filter expression. A rule with an `execute` action executes a ruleset.
 
----
+***
 
 ## Get started
 
diff --git a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
index 4ead3afce0027eb..195f92316c007d2 100644
--- a/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
+++ b/src/content/docs/ruleset-engine/managed-rulesets/override-examples/link-override-ddos-l34-rule-sensitivity.mdx
@@ -7,4 +7,5 @@ title: Adjust an L3/4 DDoS rule
 external_link: /ddos-protection/managed-rulesets/network/network-overrides/configure-api/#configure-an-override-for-the-network-layer-ddos-attack-protection-managed-ruleset
 sidebar:
   order: 7
+
 ---
diff --git a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
index 5e0d01303a761d5..4e1b9c1603ab0bf 100644
--- a/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
+++ b/src/content/docs/ruleset-engine/rulesets-api/endpoints.mdx
@@ -34,12 +34,14 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 :::note
 
+
 The Rulesets API endpoints require a value for `{account_id}` or `{zone_id}`.
 
 To retrieve a list of accounts you have access to, use the [List Accounts](/api/resources/accounts/methods/list/) operation. Note the IDs of the accounts you want to manage.
 
 To retrieve a list of zones you have access to, use the [List Zones](/api/resources/zones/methods/list/) operation. Note the IDs of the zones you want to manage.
 
+
 :::
 
 The Cloudflare Rulesets API supports the operations outlined below. Visit the associated links for API endpoints and examples.
@@ -47,235 +49,206 @@ The Cloudflare Rulesets API supports the operations outlined below. Visit the as
 ## List and view rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Method</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">
-					List existing rulesets
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the list of existing rulesets at the account level or at the
-					zone level.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">
-					View a specific ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the properties of the most recent version of a specific
-					ruleset.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
-					List all versions of a ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>Returns a list of all the versions of a ruleset.</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
-					View a specific version of a ruleset
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns the configuration of a specific version of a ruleset,
-					including its rules.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
-					List rules in a managed ruleset with a specific tag
-				</a>
-			</td>
-			<td>
-				<code>GET</code>
-			</td>
-			<td>
-				<p>
-					Returns a list of all the rules in a managed ruleset with a specific
-					tag.
-				</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Method</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-existing-rulesets">List existing rulesets</a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the list of existing rulesets at the account level or at the zone level.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset">View a specific ruleset</a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the properties of the most recent version of a specific ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-all-versions-of-a-ruleset">
+          List all versions of a ruleset
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns a list of all the versions of a ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#view-a-specific-version-of-a-ruleset">
+          View a specific version of a ruleset
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns the configuration of a specific version of a ruleset, including its rules.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/view/#list-rules-in-a-managed-ruleset-with-a-specific-tag">
+          List rules in a managed ruleset with a specific tag
+        </a>
+      </td>
+      <td>
+        <code>GET</code>
+      </td>
+      <td>
+        <p>Returns a list of all the rules in a managed ruleset with a specific tag.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Create rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
-			</td>
-			<td>
-				<code>POST</code>
-			</td>
-			<td>
-				<p>Creates a new ruleset or a new phase entry point.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/create/">Create a ruleset</a>
+      </td>
+      <td>
+        <code>POST</code>
+      </td>
+      <td>
+        <p>Creates a new ruleset or a new phase entry point.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Update and deploy rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/update/">
-					Update or deploy a ruleset
-				</a>
-			</td>
-			<td>
-				<code>PUT</code>
-			</td>
-			<td>
-				<p>
-					Updates the basic properties of a ruleset and the list of rules in the
-					ruleset.
-					<br />
-					Allows you to configure the execution of managed rulesets.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/add-rule/">
-					Add a rule to a ruleset
-				</a>
-			</td>
-			<td>
-				<code>POST</code>
-			</td>
-			<td>
-				<p>
-					Adds a single rule to an existing ruleset.
-					<br />
-					Allows you to add a single rule without having to include all the
-					existing ruleset rules in the request.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/update-rule/">
-					Update a rule in a ruleset
-				</a>
-			</td>
-			<td>
-				<code>PATCH</code>
-			</td>
-			<td>
-				<p>
-					Updates the definition of a single rule within a ruleset.
-					<br />
-					Allows you to change the order of a rule in a ruleset.
-				</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete-rule/">
-					Delete a rule in a ruleset
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes a single rule in a ruleset.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/update/">Update or deploy a ruleset</a>
+      </td>
+      <td>
+        <code>PUT</code>
+      </td>
+      <td>
+        <p>
+          Updates the basic properties of a ruleset and the list of rules in the ruleset.
+          <br />
+          Allows you to configure the execution of managed rulesets.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/add-rule/">Add a rule to a ruleset</a>
+      </td>
+      <td>
+        <code>POST</code>
+      </td>
+      <td>
+        <p>
+          Adds a single rule to an existing ruleset.
+          <br />
+          Allows you to add a single rule without having to include all the existing ruleset rules
+          in the request.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/update-rule/">Update a rule in a ruleset</a>
+      </td>
+      <td>
+        <code>PATCH</code>
+      </td>
+      <td>
+        <p>
+          Updates the definition of a single rule within a ruleset.
+          <br />
+          Allows you to change the order of a rule in a ruleset.
+        </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete-rule/">Delete a rule in a ruleset</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes a single rule in a ruleset.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
 ## Delete rulesets
 
 <table>
-	<thead>
-		<tr>
-			<th>Operation</th>
-			<th>Verb</th>
-			<th>Notes</th>
-		</tr>
-	</thead>
-	<tbody style="vertical-align:top">
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">
-					Delete a ruleset
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes all the versions of a ruleset.</p>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				<a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">
-					Delete a ruleset version
-				</a>
-			</td>
-			<td>
-				<code>DELETE</code>
-			</td>
-			<td>
-				<p>Deletes a specific version of a ruleset.</p>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+      <th>Operation</th>
+      <th>Verb</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody style="vertical-align:top">
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset">Delete a ruleset</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes all the versions of a ruleset.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <a href="/ruleset-engine/rulesets-api/delete/#delete-ruleset-version">Delete a ruleset version</a>
+      </td>
+      <td>
+        <code>DELETE</code>
+      </td>
+      <td>
+        <p>Deletes a specific version of a ruleset.</p>
+      </td>
+    </tr>
+  </tbody>
 </table>
diff --git a/src/content/docs/sandbox/bridge/http-api.mdx b/src/content/docs/sandbox/bridge/http-api.mdx
index ba425ec0d9cf393..8454191fa57021e 100644
--- a/src/content/docs/sandbox/bridge/http-api.mdx
+++ b/src/content/docs/sandbox/bridge/http-api.mdx
@@ -28,10 +28,10 @@ When `SANDBOX_API_KEY` is not configured, authentication is skipped for local de
 
 The bridge serves its own API documentation:
 
-| Method | Route              | Description                          |
-| ------ | ------------------ | ------------------------------------ |
-| `GET`  | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
-| `GET`  | `/v1/openapi`      | Interactive HTML documentation.      |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/openapi.json` | Machine-readable OpenAPI 3.1 schema. |
+| `GET` | `/v1/openapi` | Interactive HTML documentation. |
 
 Both routes accept authentication via Bearer header or `?token=` query parameter.
 
@@ -39,25 +39,25 @@ When running locally with `npm run dev`, open `http://localhost:8787/v1/openapi`
 
 ## Sandbox lifecycle
 
-| Method   | Route                     | Description                                                   |
-| -------- | ------------------------- | ------------------------------------------------------------- |
-| `POST`   | `/v1/sandbox`             | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`.       |
-| `DELETE` | `/v1/sandbox/:id`         | Destroy the sandbox container. Returns `204`.                 |
-| `GET`    | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox` | Create a new sandbox. Returns `{"id": "<sandbox-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id` | Destroy the sandbox container. Returns `204`. |
+| `GET` | `/v1/sandbox/:id/running` | Check container liveness. Returns `{"running": true\|false}`. |
 
 ## Command execution
 
-| Method | Route                  | Description                                           |
-| ------ | ---------------------- | ----------------------------------------------------- |
+| Method | Route | Description |
+|---|---|---|
 | `POST` | `/v1/sandbox/:id/exec` | Run a command. Response is an SSE stream (see below). |
 
 The `/exec` endpoint accepts a JSON body:
 
 ```json
 {
-	"argv": ["sh", "-lc", "echo hello"],
-	"timeout_ms": 10000,
-	"cwd": "/workspace"
+  "argv": ["sh", "-lc", "echo hello"],
+  "timeout_ms": 10000,
+  "cwd": "/workspace"
 }
 ```
 
@@ -69,27 +69,27 @@ Each element of the `argv` array is escaped using ANSI-C `$'...'` quoting before
 
 The response is a `text/event-stream` with the following event types:
 
-| Event    | Data                          | Description                        |
-| -------- | ----------------------------- | ---------------------------------- |
-| `stdout` | Base64-encoded chunk          | Standard output from the command.  |
-| `stderr` | Base64-encoded chunk          | Standard error from the command.   |
-| `exit`   | `{"exit_code": N}`            | Command completed. Terminal event. |
-| `error`  | `{"error": "…", "code": "…"}` | Command failed. Terminal event.    |
+| Event | Data | Description |
+|---|---|---|
+| `stdout` | Base64-encoded chunk | Standard output from the command. |
+| `stderr` | Base64-encoded chunk | Standard error from the command. |
+| `exit` | `{"exit_code": N}` | Command completed. Terminal event. |
+| `error` | `{"error": "…", "code": "…"}` | Command failed. Terminal event. |
 
 ## File operations
 
-| Method | Route                    | Description                                                                  |
-| ------ | ------------------------ | ---------------------------------------------------------------------------- |
-| `GET`  | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`).                 |
-| `PUT`  | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/sandbox/:id/file/*` | Read a file. Returns raw bytes (`application/octet-stream`). |
+| `PUT` | `/v1/sandbox/:id/file/*` | Write a file. Request body is raw bytes. Returns `{"ok": true}`. Max 32 MiB. |
 
 The file path is encoded in the URL after `/file/`. All paths must resolve within `/workspace`. Path traversal attempts (for example, `../../etc/passwd`) are rejected.
 
 ## Workspace persistence
 
-| Method | Route                     | Description                                                        |
-| ------ | ------------------------- | ------------------------------------------------------------------ |
-| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes.    |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/persist` | Serialize `/workspace` to a tar archive. Returns raw tar bytes. |
 | `POST` | `/v1/sandbox/:id/hydrate` | Populate `/workspace` from a tar archive sent as the request body. |
 
 The `/persist` endpoint accepts an optional `excludes` query parameter — a comma-separated list of relative paths to exclude from the archive.
@@ -98,10 +98,10 @@ The `/hydrate` endpoint accepts a raw tar payload up to 32 MiB.
 
 ## Bucket mounts
 
-| Method | Route                     | Description                                         |
-| ------ | ------------------------- | --------------------------------------------------- |
-| `POST` | `/v1/sandbox/:id/mount`   | Mount an S3-compatible bucket as a local directory. |
-| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket.                |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/mount` | Mount an S3-compatible bucket as a local directory. |
+| `POST` | `/v1/sandbox/:id/unmount` | Unmount a previously mounted bucket. |
 
 The `/mount` endpoint accepts a JSON body. Two flows are supported:
 
@@ -111,12 +111,12 @@ Omit `endpoint` and pass the Worker R2 binding name in `bucket`:
 
 ```json
 {
-	"bucket": "MY_BUCKET",
-	"mountPath": "/mnt/data",
-	"options": {
-		"readOnly": false,
-		"prefix": "/subdir"
-	}
+  "bucket": "MY_BUCKET",
+  "mountPath": "/mnt/data",
+  "options": {
+    "readOnly": false,
+    "prefix": "/subdir"
+  }
 }
 ```
 
@@ -126,17 +126,17 @@ For an explicit S3-compatible endpoint mount, include `endpoint` and optionally
 
 ```json
 {
-	"bucket": "my-r2-bucket",
-	"mountPath": "/mnt/data",
-	"options": {
-		"endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
-		"readOnly": false,
-		"prefix": "/subdir",
-		"credentials": {
-			"accessKeyId": "...",
-			"secretAccessKey": "..."
-		}
-	}
+  "bucket": "my-r2-bucket",
+  "mountPath": "/mnt/data",
+  "options": {
+    "endpoint": "https://ACCOUNT_ID.r2.cloudflarestorage.com",
+    "readOnly": false,
+    "prefix": "/subdir",
+    "credentials": {
+      "accessKeyId": "...",
+      "secretAccessKey": "..."
+    }
+  }
 }
 ```
 
@@ -144,10 +144,10 @@ When `endpoint` is provided, `bucket` means the remote bucket name. Credentials
 
 ## Sessions
 
-| Method   | Route                          | Description                                         |
-| -------- | ------------------------------ | --------------------------------------------------- |
-| `POST`   | `/v1/sandbox/:id/session`      | Create a session. Returns `{"id": "<session-id>"}`. |
-| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`.                    |
+| Method | Route | Description |
+|---|---|---|
+| `POST` | `/v1/sandbox/:id/session` | Create a session. Returns `{"id": "<session-id>"}`. |
+| `DELETE` | `/v1/sandbox/:id/session/:sid` | Delete a session. Returns `204`. |
 
 Sessions isolate working directory, environment variables, and command execution state within a sandbox. Pass the `Session-Id` header on `/exec`, `/file/*`, and `/pty` requests to scope them to a session.
 
@@ -155,35 +155,35 @@ When no `Session-Id` header is provided, requests use the sandbox default sessio
 
 ## Terminal (PTY)
 
-| Method | Route                 | Description                         |
-| ------ | --------------------- | ----------------------------------- |
-| `GET`  | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/sandbox/:id/pty` | Upgrade to a WebSocket PTY session. |
 
 Query parameters:
 
-| Parameter | Type   | Default | Description                              |
-| --------- | ------ | ------- | ---------------------------------------- |
-| `cols`    | number | `80`    | Terminal width in columns.               |
-| `rows`    | number | `24`    | Terminal height in rows.                 |
-| `shell`   | string | —       | Shell binary (for example, `/bin/bash`). |
-| `session` | string | —       | Session ID for session-scoped PTY.       |
+| Parameter | Type | Default | Description |
+|---|---|---|---|
+| `cols` | number | `80` | Terminal width in columns. |
+| `rows` | number | `24` | Terminal height in rows. |
+| `shell` | string | — | Shell binary (for example, `/bin/bash`). |
+| `session` | string | — | Session ID for session-scoped PTY. |
 
 The WebSocket carries binary frames for terminal I/O and JSON text frames for control messages:
 
-| Direction        | Frame type  | Content                                                                        |
-| ---------------- | ----------- | ------------------------------------------------------------------------------ |
-| Client to server | Binary      | UTF-8 encoded keystrokes.                                                      |
-| Server to client | Binary      | Terminal output including ANSI escape sequences.                               |
+| Direction | Frame type | Content |
+|---|---|---|
+| Client to server | Binary | UTF-8 encoded keystrokes. |
+| Server to client | Binary | Terminal output including ANSI escape sequences. |
 | Client to server | Text (JSON) | Control messages (for example, `{"type": "resize", "cols": 120, "rows": 30}`). |
-| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`).                                    |
+| Server to client | Text (JSON) | Status messages (`ready`, `exit`, `error`). |
 
 ## Warm pool
 
-| Method | Route                         | Description                     |
-| ------ | ----------------------------- | ------------------------------- |
-| `GET`  | `/v1/pool/stats`              | Current pool statistics.        |
-| `POST` | `/v1/pool/prime`              | Start the warm pool alarm loop. |
-| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers.  |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/v1/pool/stats` | Current pool statistics. |
+| `POST` | `/v1/pool/prime` | Start the warm pool alarm loop. |
+| `POST` | `/v1/pool/shutdown-prewarmed` | Stop all idle warm containers. |
 
 The warm pool pre-starts sandbox containers so new sessions boot instantly. Configure it with environment variables in `wrangler.jsonc`:
 
@@ -201,9 +201,9 @@ A cron trigger (`* * * * *`) primes the pool automatically after deployment. Set
 
 ## Health check
 
-| Method | Route     | Description                                             |
-| ------ | --------- | ------------------------------------------------------- |
-| `GET`  | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
+| Method | Route | Description |
+|---|---|---|
+| `GET` | `/health` | Unauthenticated liveness probe. Returns `{"ok": true}`. |
 
 ## Related resources
 
diff --git a/src/content/docs/sandbox/concepts/containers.mdx b/src/content/docs/sandbox/concepts/containers.mdx
index e1a711233feb34b..dd9a725669a262e 100644
--- a/src/content/docs/sandbox/concepts/containers.mdx
+++ b/src/content/docs/sandbox/concepts/containers.mdx
@@ -30,18 +30,16 @@ apt-get update && apt-get install -y redis-server
 The container provides a standard Linux filesystem. You can read and write anywhere you have permissions.
 
 **Standard directories**:
-
 - `/workspace` - Default working directory for user code
 - `/tmp` - Temporary files
 - `/home` - User home directory
 - `/usr/bin`, `/usr/local/bin` - Executable binaries
 
 **Example**:
-
 ```typescript
-await sandbox.writeFile("/workspace/app.py", 'print("Hello")');
-await sandbox.writeFile("/tmp/cache.json", "{}");
-await sandbox.exec("ls -la /workspace");
+await sandbox.writeFile('/workspace/app.py', 'print("Hello")');
+await sandbox.writeFile('/tmp/cache.json', '{}');
+await sandbox.exec('ls -la /workspace');
 ```
 
 ## Process management
@@ -49,23 +47,20 @@ await sandbox.exec("ls -la /workspace");
 Processes run as you'd expect in a regular Linux environment.
 
 **Foreground processes** (`exec()`):
-
 ```typescript
-const result = await sandbox.exec("npm test");
+const result = await sandbox.exec('npm test');
 // Waits for completion, returns output
 ```
 
 **Background processes** (`startProcess()`):
-
 ```typescript
-const process = await sandbox.startProcess("node server.js");
+const process = await sandbox.startProcess('node server.js');
 // Returns immediately, process runs in background
 ```
 
 ## Network capabilities
 
 **Outbound connections** work:
-
 ```bash
 curl https://api.example.com/data
 pip install requests
@@ -73,10 +68,9 @@ npm install express
 ```
 
 **Inbound connections** require port exposure:
-
 ```typescript
 const { hostname } = new URL(request.url);
-await sandbox.startProcess("python -m http.server 8000");
+await sandbox.startProcess('python -m http.server 8000');
 const exposed = await sandbox.exposePort(8000, { hostname });
 console.log(exposed.url); // Public URL
 ```
@@ -86,7 +80,6 @@ When using `wrangler dev`, you must add `EXPOSE` directives to your Dockerfile f
 :::
 
 **Localhost** works within sandbox:
-
 ```bash
 redis-server &      # Start server
 redis-cli ping      # Connect locally
@@ -95,18 +88,15 @@ redis-cli ping      # Connect locally
 ## Security
 
 **Between sandboxes** (isolated):
-
 - Each sandbox is a separate container
 - Filesystem, memory and network are all isolated
 
 **Within sandbox** (shared):
-
 - All processes see the same files
 - Processes can communicate with each other
 - Environment variables are session-scoped
 
 To run untrusted code, use separate sandboxes per user:
-
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
@@ -114,7 +104,6 @@ const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ## Limitations
 
 **Cannot**:
-
 - Load kernel modules or access host hardware
 
 ## Related resources
diff --git a/src/content/docs/sandbox/concepts/preview-urls.mdx b/src/content/docs/sandbox/concepts/preview-urls.mdx
index 43eecbf9c151321..7fdf50c71ce90b4 100644
--- a/src/content/docs/sandbox/concepts/preview-urls.mdx
+++ b/src/content/docs/sandbox/concepts/preview-urls.mdx
@@ -24,9 +24,9 @@ const req = await fetch(`${tunnel.url}/api/users`); // => GET http://localhost:8
 
 Cloudflare Tunnel support currently has the following limitations:
 
-- No control over generated URL.
-- No authentication mechanism beyond randomly generated URL.
-- Each URL uses an additional `cloudflared` process on the sandbox.
+ - No control over generated URL.
+ - No authentication mechanism beyond randomly generated URL.
+ - Each URL uses an additional `cloudflared` process on the sandbox.
 
 :::note[Production requires custom domain]
 We are working on production deployments, custom hostnames and authentication for Cloudflare Tunnel support. In the mean time we recommend using `exposePort()` and `proxyToSandbox()` documented below under [Production usage, stable URLs and custom domains](#).
diff --git a/src/content/docs/sandbox/concepts/sandboxes.mdx b/src/content/docs/sandbox/concepts/sandboxes.mdx
index cd86f4ac0b8f21d..e0828106d246dbd 100644
--- a/src/content/docs/sandbox/concepts/sandboxes.mdx
+++ b/src/content/docs/sandbox/concepts/sandboxes.mdx
@@ -126,8 +126,8 @@ try {
 Containers with [`keepAlive: true`](/sandbox/configuration/sandbox-options/#keepalive) require explicit management since they do not timeout automatically:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, "persistent-task", {
-	keepAlive: true,
+const sandbox = getSandbox(env.Sandbox, 'persistent-task', {
+  keepAlive: true
 });
 
 // Later, when done with long-running work
diff --git a/src/content/docs/sandbox/concepts/security.mdx b/src/content/docs/sandbox/concepts/security.mdx
index 9954cb9833e9732..5c15d8d4295ba00 100644
--- a/src/content/docs/sandbox/concepts/security.mdx
+++ b/src/content/docs/sandbox/concepts/security.mdx
@@ -36,7 +36,7 @@ For complete isolation, use separate sandboxes per user:
 const userSandbox = getSandbox(env.Sandbox, `user-${userId}`);
 
 // Bad - Users sharing one sandbox
-const shared = getSandbox(env.Sandbox, "shared");
+const shared = getSandbox(env.Sandbox, 'shared');
 // Users can read each other's files!
 ```
 
@@ -53,12 +53,12 @@ await sandbox.exec(`cat ${filename}`);
 // User could input: "file.txt; rm -rf /"
 
 // Safe - validate input
-const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, "");
+const filename = userInput.replace(/[^a-zA-Z0-9._-]/g, '');
 await sandbox.exec(`cat ${filename}`);
 
 // Better - use file API
-await sandbox.writeFile("/tmp/input", userInput);
-await sandbox.exec("cat /tmp/input");
+await sandbox.writeFile('/tmp/input', userInput);
+await sandbox.exec('cat /tmp/input');
 ```
 
 ## Authentication
@@ -69,16 +69,16 @@ Sandbox IDs provide basic access control but aren't cryptographically secure. Ad
 
 ```typescript
 export default {
-	async fetch(request: Request, env: Env): Promise<Response> {
-		const userId = await authenticate(request);
-		if (!userId) {
-			return new Response("Unauthorized", { status: 401 });
-		}
-
-		// User can only access their sandbox
-		const sandbox = getSandbox(env.Sandbox, userId);
-		return Response.json({ authorized: true });
-	},
+  async fetch(request: Request, env: Env): Promise<Response> {
+    const userId = await authenticate(request);
+    if (!userId) {
+      return new Response('Unauthorized', { status: 401 });
+    }
+
+    // User can only access their sandbox
+    const sandbox = getSandbox(env.Sandbox, userId);
+    return Response.json({ authorized: true });
+  }
 };
 ```
 
@@ -125,18 +125,15 @@ Use environment variables, not hardcoded secrets:
 
 ```typescript
 // Bad - hardcoded in file
-await sandbox.writeFile(
-	"/workspace/config.js",
-	`
+await sandbox.writeFile('/workspace/config.js', `
   const API_KEY = 'sk_live_abc123';
-`,
-);
+`);
 
 // Good - use environment variables
-await sandbox.startProcess("node app.js", {
-	env: {
-		API_KEY: env.API_KEY, // From Worker environment binding
-	},
+await sandbox.startProcess('node app.js', {
+  env: {
+    API_KEY: env.API_KEY,  // From Worker environment binding
+  }
 });
 ```
 
@@ -144,10 +141,10 @@ Clean up temporary sensitive data:
 
 ```typescript
 try {
-	await sandbox.writeFile("/tmp/sensitive.txt", secretData);
-	await sandbox.exec("python process.py /tmp/sensitive.txt");
+  await sandbox.writeFile('/tmp/sensitive.txt', secretData);
+  await sandbox.exec('python process.py /tmp/sensitive.txt');
 } finally {
-	await sandbox.deleteFile("/tmp/sensitive.txt");
+  await sandbox.deleteFile('/tmp/sensitive.txt');
 }
 ```
 
@@ -181,34 +178,30 @@ This pattern is useful when accessing GitHub for private repository operations,
 ## Best practices
 
 **Use separate sandboxes for isolation**:
-
 ```typescript
 const sandbox = getSandbox(env.Sandbox, `user-${userId}`);
 ```
 
 **Validate all inputs**:
-
 ```typescript
-const safe = input.replace(/[^a-zA-Z0-9._-]/g, "");
+const safe = input.replace(/[^a-zA-Z0-9._-]/g, '');
 await sandbox.exec(`command ${safe}`);
 ```
 
 **Use environment variables for secrets**:
-
 ```typescript
-await sandbox.startProcess("node app.js", {
-	env: { API_KEY: env.API_KEY },
+await sandbox.startProcess('node app.js', {
+  env: { API_KEY: env.API_KEY }
 });
 ```
 
 **Clean up temporary resources**:
-
 ```typescript
 try {
-	const sandbox = getSandbox(env.Sandbox, sessionId);
-	await sandbox.exec("npm test");
+  const sandbox = getSandbox(env.Sandbox, sessionId);
+  await sandbox.exec('npm test');
 } finally {
-	await sandbox.destroy();
+  await sandbox.destroy();
 }
 ```
 
diff --git a/src/content/docs/sandbox/concepts/sessions.mdx b/src/content/docs/sandbox/concepts/sessions.mdx
index dd054b3036ce8f7..1697cf6e8795d7f 100644
--- a/src/content/docs/sandbox/concepts/sessions.mdx
+++ b/src/content/docs/sandbox/concepts/sessions.mdx
@@ -18,14 +18,14 @@ Sessions are bash shell execution contexts within a sandbox. Think of them like
 Every sandbox has a default session that maintains shell state between commands while the container is active:
 
 ```typescript
-const sandbox = getSandbox(env.Sandbox, "my-sandbox");
+const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
 
 // These commands run in the default session
 await sandbox.exec("cd /app");
-await sandbox.exec("pwd"); // Output: /app
+await sandbox.exec("pwd");  // Output: /app
 
 await sandbox.exec("export MY_VAR=hello");
-await sandbox.exec("echo $MY_VAR"); // Output: hello
+await sandbox.exec("echo $MY_VAR");  // Output: hello
 ```
 
 Working directory, environment variables, and exported variables carry over between commands. This state resets if the container restarts due to inactivity.
@@ -36,7 +36,7 @@ The container automatically creates sessions on first use. If you reference a no
 
 ```typescript
 // This session doesn't exist yet
-const result = await sandbox.exec("echo hello", { sessionId: "new-session" });
+const result = await sandbox.exec('echo hello', { sessionId: 'new-session' });
 // Container automatically creates 'new-session' with defaults:
 // - cwd: '/workspace'
 // - env: {} (empty)
@@ -47,15 +47,15 @@ This behavior is particularly relevant after deleting a session:
 ```typescript
 // Create and configure a session
 const session = await sandbox.createSession({
-	id: "temp",
-	env: { MY_VAR: "value" },
+  id: 'temp',
+  env: { MY_VAR: 'value' }
 });
 
 // Delete the session
-await sandbox.deleteSession("temp");
+await sandbox.deleteSession('temp');
 
 // Using the same session ID again works - auto-created with defaults
-const result = await sandbox.exec("echo $MY_VAR", { sessionId: "temp" });
+const result = await sandbox.exec('echo $MY_VAR', { sessionId: 'temp' });
 // Output: (empty) - MY_VAR is not set in the freshly created session
 ```
 
@@ -67,15 +67,15 @@ Create additional sessions for isolated shell contexts:
 
 ```typescript
 const buildSession = await sandbox.createSession({
-	id: "build",
-	env: { NODE_ENV: "production" },
-	cwd: "/build",
+  id: "build",
+  env: { NODE_ENV: "production" },
+  cwd: "/build"
 });
 
 const testSession = await sandbox.createSession({
-	id: "test",
-	env: { NODE_ENV: "test" },
-	cwd: "/test",
+  id: "test",
+  env: { NODE_ENV: "test" },
+  cwd: "/test"
 });
 
 // Different shell contexts
@@ -87,8 +87,8 @@ You can also set a default command timeout for all commands in a session:
 
 ```typescript
 const session = await sandbox.createSession({
-	id: "ci",
-	commandTimeoutMs: 30000, // 30s timeout for all commands
+  id: "ci",
+  commandTimeoutMs: 30000 // 30s timeout for all commands
 });
 
 await session.exec("npm test"); // Times out after 30s if still running
@@ -101,27 +101,24 @@ Individual commands can override the session timeout with the `timeout` option o
 Each session has its own:
 
 **Shell environment**:
-
 ```typescript
 await session1.exec("export MY_VAR=hello");
-await session2.exec("echo $MY_VAR"); // Empty - different shell
+await session2.exec("echo $MY_VAR");  // Empty - different shell
 ```
 
 **Working directory**:
-
 ```typescript
 await session1.exec("cd /workspace/project1");
-await session2.exec("pwd"); // Different working directory
+await session2.exec("pwd");  // Different working directory
 ```
 
 **Environment variables** (set via `createSession` options):
-
 ```typescript
 const session1 = await sandbox.createSession({
-	env: { API_KEY: "key-1" },
+  env: { API_KEY: 'key-1' }
 });
 const session2 = await sandbox.createSession({
-	env: { API_KEY: "key-2" },
+  env: { API_KEY: 'key-2' }
 });
 ```
 
@@ -130,47 +127,42 @@ const session2 = await sandbox.createSession({
 All sessions in a sandbox share:
 
 **Filesystem**:
-
 ```typescript
-await session1.writeFile("/workspace/file.txt", "data");
-await session2.readFile("/workspace/file.txt"); // Can read it
+await session1.writeFile('/workspace/file.txt', 'data');
+await session2.readFile('/workspace/file.txt');  // Can read it
 ```
 
 **Processes**:
-
 ```typescript
-await session1.startProcess("node server.js");
-await session2.listProcesses(); // Sees the server
+await session1.startProcess('node server.js');
+await session2.listProcesses();  // Sees the server
 ```
 
 ## When to use sessions
 
 **Use sessions when**:
-
 - You need isolated shell state for different tasks
 - Running parallel operations with different environments
 - Keeping AI agent credentials separate from app runtime
 
 **Example - separate dev and runtime environments**:
-
 ```typescript
 // Phase 1: AI agent writes code (with API keys)
 const devSession = await sandbox.createSession({
-	id: "dev",
-	env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY },
+  id: "dev",
+  env: { ANTHROPIC_API_KEY: env.ANTHROPIC_API_KEY }
 });
 await devSession.exec('ai-tool "build a web server"');
 
 // Phase 2: Run the code (without API keys)
 const appSession = await sandbox.createSession({
-	id: "app",
-	env: { PORT: "3000" },
+  id: "app",
+  env: { PORT: "3000" }
 });
 await appSession.exec("node server.js");
 ```
 
 **Use separate sandboxes when**:
-
 - You need complete isolation (untrusted code)
 - Different users require fully separated environments
 - Independent resource allocation is needed
@@ -180,31 +172,28 @@ await appSession.exec("node server.js");
 ### Session cleanup
 
 **Clean up temporary sessions** to free resources while keeping the sandbox running:
-
 ```typescript
 try {
-	const session = await sandbox.createSession({ id: "temp" });
-	await session.exec("command");
+  const session = await sandbox.createSession({ id: 'temp' });
+  await session.exec('command');
 } finally {
-	await sandbox.deleteSession("temp");
+  await sandbox.deleteSession('temp');
 }
 ```
 
 **Default session cannot be deleted**:
-
 ```typescript
 // This throws an error
-await sandbox.deleteSession("default");
+await sandbox.deleteSession('default');
 // Error: Cannot delete default session. Use sandbox.destroy() instead.
 ```
 
 ### Filesystem isolation
 
 **Sessions share filesystem** - file operations affect all sessions:
-
 ```typescript
 // Bad - affects all sessions
-await session.exec("rm -rf /workspace/*");
+await session.exec('rm -rf /workspace/*');
 
 // For untrusted code isolation, use separate sandboxes
 const userSandbox = getSandbox(env.Sandbox, userId);
diff --git a/src/content/docs/sandbox/configuration/environment-variables.mdx b/src/content/docs/sandbox/configuration/environment-variables.mdx
index 2bd802277756cba..522821f21e1c931 100644
--- a/src/content/docs/sandbox/configuration/environment-variables.mdx
+++ b/src/content/docs/sandbox/configuration/environment-variables.mdx
@@ -18,10 +18,10 @@ These environment variables configure how the Sandbox SDK behaves. Set these as
 
 ### SANDBOX_TRANSPORT
 
-|             |                           |
-| ----------- | ------------------------- |
-| **Type**    | `"http"` \| `"websocket"` |
-| **Default** | `"http"`                  |
+| | |
+|---|---|
+| **Type** | `"http"` \| `"websocket"` |
+| **Default** | `"http"` |
 
 Controls the transport protocol for SDK-to-container communication. WebSocket transport multiplexes all operations over a single persistent connection, avoiding [subrequest limits](/workers/platform/limits/#subrequests) when performing many SDK operations per request.
 
@@ -39,10 +39,10 @@ See [Transport modes](/sandbox/configuration/transport/) for a complete guide in
 
 ### COMMAND_TIMEOUT_MS
 
-|             |                         |
-| ----------- | ----------------------- |
-| **Type**    | `number` (milliseconds) |
-| **Default** | None (no timeout)       |
+| | |
+|---|---|
+| **Type** | `number` (milliseconds) |
+| **Default** | None (no timeout) |
 
 Sets a global default timeout for every `exec()` call. When set, any command that exceeds this duration raises an error on the caller side and closes the connection.
 
@@ -95,9 +95,9 @@ await sandbox.setEnvVars({
 
 ```typescript
 await sandbox.setEnvVars({
-	API_KEY: "new-key", // Sets API_KEY
-	OLD_SECRET: undefined, // Unsets OLD_SECRET
-	DEBUG_MODE: null, // Unsets DEBUG_MODE
+	API_KEY: 'new-key',     // Sets API_KEY
+	OLD_SECRET: undefined,  // Unsets OLD_SECRET
+	DEBUG_MODE: null        // Unsets DEBUG_MODE
 });
 ```
 
@@ -153,12 +153,12 @@ The Sandbox SDK supports unsetting environment variables by passing `undefined`
 ```typescript
 await sandbox.setEnvVars({
 	// Set new values
-	API_KEY: "new-key",
+	API_KEY: 'new-key',
 	DATABASE_URL: env.DATABASE_URL,
 
 	// Unset variables (removes them from the environment)
 	OLD_API_KEY: undefined,
-	TEMP_TOKEN: null,
+	TEMP_TOKEN: null
 });
 ```
 
@@ -172,7 +172,7 @@ await sandbox.setEnvVars({
 
 ```typescript
 // Use a temporary token
-await sandbox.setEnvVars({ TEMP_TOKEN: "abc123" });
+await sandbox.setEnvVars({ TEMP_TOKEN: 'abc123' });
 await sandbox.exec('curl -H "Authorization: $TEMP_TOKEN" api.example.com');
 
 // Clean up the token
@@ -184,8 +184,8 @@ await sandbox.setEnvVars({ TEMP_TOKEN: undefined });
 ```typescript
 await sandbox.setEnvVars({
 	API_KEY: env.API_KEY,
-	DEBUG_MODE: env.NODE_ENV === "development" ? "true" : undefined,
-	PROFILING: env.ENABLE_PROFILING ? "true" : undefined,
+	DEBUG_MODE: env.NODE_ENV === 'development' ? 'true' : undefined,
+	PROFILING: env.ENABLE_PROFILING ? 'true' : undefined
 });
 ```
 
diff --git a/src/content/docs/sandbox/configuration/transport.mdx b/src/content/docs/sandbox/configuration/transport.mdx
index 18e5f33fc1b515d..dce27bacce1ff87 100644
--- a/src/content/docs/sandbox/configuration/transport.mdx
+++ b/src/content/docs/sandbox/configuration/transport.mdx
@@ -22,6 +22,7 @@ The Sandbox SDK supports three transport modes for communication between the Dur
 - **NEW: RPC transport** - All SDK operations are multiplexed over a single persistent WebSocket connection. Will replace HTTP as the default transport in future. Available since 0.9.1.
 - **Deprecated: WebSocket transport** - All SDK operations are multiplexed over a single persistent WebSocket. Superseded by RPC transport which uses an improved protocol.
 
+
 ## When to use RPC transport
 
 Use the RPC transport when your Worker or Durable Object makes many SDK operations per request. This avoids hitting [subrequest limits](/workers/platform/limits/#subrequests).
@@ -111,13 +112,11 @@ No application code changes are needed. The SDK automatically uses the configure
 ### Connection lifecycle
 
 **HTTP transport:**
-
 - Creates a new HTTP request for each SDK operation
 - No persistent connection
 - Each request is independent and stateless
 
 **RPC transport:**
-
 - Establishes a WebSocket connection on the first SDK operation
 - Maintains the persistent connection for all subsequent operations
 - Connection is closed when the sandbox sleeps or is evicted
@@ -137,7 +136,6 @@ Your code remains identical regardless of transport mode.
 All transports provide identical error handling behavior. The SDK automatically retries on transient errors (like 503 responses) with exponential backoff.
 
 WebSocket-specific behavior:
-
 - Connection failures trigger automatic reconnection
 - The SDK transparently handles WebSocket disconnections
 - In-flight operations are not lost during reconnection
@@ -156,6 +154,7 @@ Switching between transports requires no code changes.
 Using the `rpc` transport requires version 0.9.1 or newer. If you are using an older version of the Sandbox SDK upgrade and deploy your application with the newer `@cloudflare/sandbox` and image first. Otherwise there will be issues with newer SDK clients attempting to connect to older sandboxes that do not support the new transport.
 :::
 
+
 Add `SANDBOX_TRANSPORT` to your `wrangler.jsonc`:
 
 <WranglerConfig>
diff --git a/src/content/docs/sandbox/guides/production-deployment.mdx b/src/content/docs/sandbox/guides/production-deployment.mdx
index c0f0ed75abf6508..27c08a0c143f74a 100644
--- a/src/content/docs/sandbox/guides/production-deployment.mdx
+++ b/src/content/docs/sandbox/guides/production-deployment.mdx
@@ -24,11 +24,10 @@ The `.workers.dev` domain does not support wildcard subdomains, so production de
 If your worker runs on a subdomain (for example, `sandbox.yourdomain.com`), preview URLs become second-level wildcards like `*.sandbox.yourdomain.com`. Cloudflare's Universal SSL only covers first-level wildcards (`*.yourdomain.com`), so you need a certificate covering `*.sandbox.yourdomain.com`. Without it, preview URLs will fail with TLS handshake errors.
 
 You have three options:
-
 - **Deploy on the apex domain** (`yourdomain.com`) so preview URLs stay at the first level (`*.yourdomain.com`), which Universal SSL covers automatically. This is the simplest option.
 - **Use [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/)** ($10/month) to provision a certificate for `*.sandbox.yourdomain.com` through the Cloudflare dashboard.
 - **Upload a custom certificate** from a provider like [Let's Encrypt](https://letsencrypt.org/) (free). Generate a wildcard certificate for `*.sandbox.yourdomain.com` using the DNS-01 challenge, then upload it via the Cloudflare dashboard under **SSL/TLS > Edge Certificates > [Custom Certificates](/ssl/edge-certificates/custom-certificates/)**. You will need to renew it before expiry.
-  :::
+:::
 
 ## Prerequisites
 
@@ -43,7 +42,7 @@ You have three options:
 In the Cloudflare dashboard, go to your domain and create an A record:
 
 - **Type**: A
-- **Name**: \* (wildcard)
+- **Name**: * (wildcard)
 - **IPv4 address**: 192.0.2.0
 - **Proxy status**: Proxied (orange cloud)
 
@@ -88,8 +87,8 @@ Test that preview URLs work:
 // Extract hostname from request
 const { hostname } = new URL(request.url);
 
-const sandbox = getSandbox(env.Sandbox, "test-sandbox");
-await sandbox.startProcess("python -m http.server 8080");
+const sandbox = getSandbox(env.Sandbox, 'test-sandbox');
+await sandbox.startProcess('python -m http.server 8080');
 const exposed = await sandbox.exposePort(8080, { hostname });
 
 console.log(exposed.url);
diff --git a/src/content/docs/sandbox/platform/pricing.mdx b/src/content/docs/sandbox/platform/pricing.mdx
index cf39a5eba58829c..cc9fe5632a5b833 100644
--- a/src/content/docs/sandbox/platform/pricing.mdx
+++ b/src/content/docs/sandbox/platform/pricing.mdx
@@ -13,7 +13,6 @@ Sandbox SDK pricing is determined by the underlying [Containers](/containers/) p
 ## Containers Pricing
 
 Refer to [Containers pricing](/containers/pricing/) for complete details on:
-
 - vCPU, memory, and disk usage rates
 - Network egress pricing
 - Instance types and their costs
@@ -21,7 +20,6 @@ Refer to [Containers pricing](/containers/pricing/) for complete details on:
 ## Related Pricing
 
 When using Sandbox, you'll also be billed for:
-
 - [Workers](/workers/platform/pricing/) - Handles incoming requests to your sandbox
 - [Durable Objects](/durable-objects/platform/pricing/) - Powers each sandbox instance
 - [Workers Logs](/workers/observability/logs/workers-logs/#pricing) - Optional observability (if enabled)
diff --git a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
index 5e0e4d91dfa660e..992afa80321cc03 100644
--- a/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
+++ b/src/content/docs/sandbox/tutorials/ai-code-executor.mdx
@@ -25,7 +25,6 @@ An API that accepts questions like "What's the 100th Fibonacci number?", uses Cl
 <Render file="prereqs" product="workers" />
 
 You'll also need:
-
 - An [Anthropic API key](https://console.anthropic.com/) for Claude
 - [Docker](https://www.docker.com/) running locally
 
@@ -53,11 +52,11 @@ Install the Anthropic SDK:
 
 Replace the contents of `src/index.ts`:
 
-````typescript
-import { getSandbox, type Sandbox } from "@cloudflare/sandbox";
-import Anthropic from "@anthropic-ai/sdk";
+```typescript
+import { getSandbox, type Sandbox } from '@cloudflare/sandbox';
+import Anthropic from '@anthropic-ai/sdk';
 
-export { Sandbox } from "@cloudflare/sandbox";
+export { Sandbox } from '@cloudflare/sandbox';
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -66,10 +65,7 @@ interface Env {
 
 export default {
 	async fetch(request: Request, env: Env): Promise<Response> {
-		if (
-			request.method !== "POST" ||
-			new URL(request.url).pathname !== "/execute"
-		) {
+		if (request.method !== 'POST' || new URL(request.url).pathname !== '/execute') {
 			return new Response('POST /execute with { "question": "your question" }');
 		}
 
@@ -77,74 +73,65 @@ export default {
 			const { question } = await request.json();
 
 			if (!question) {
-				return Response.json(
-					{ error: "Question is required" },
-					{ status: 400 },
-				);
+				return Response.json({ error: 'Question is required' }, { status: 400 });
 			}
 
 			// Use Claude to generate Python code
 			const anthropic = new Anthropic({ apiKey: env.ANTHROPIC_API_KEY });
 			const codeGeneration = await anthropic.messages.create({
-				model: "claude-sonnet-4-5",
+				model: 'claude-sonnet-4-5',
 				max_tokens: 1024,
-				messages: [
-					{
-						role: "user",
-						content: `Generate Python code to answer: "${question}"
+				messages: [{
+					role: 'user',
+					content: `Generate Python code to answer: "${question}"
 
 Requirements:
 - Use only Python standard library
 - Print the result using print()
 - Keep code simple and safe
 
-Return ONLY the code, no explanations.`,
-					},
-				],
+Return ONLY the code, no explanations.`
+				}],
 			});
 
-			const generatedCode =
-				codeGeneration.content[0]?.type === "text"
-					? codeGeneration.content[0].text
-					: "";
+			const generatedCode = codeGeneration.content[0]?.type === 'text'
+				? codeGeneration.content[0].text
+				: '';
 
 			if (!generatedCode) {
-				return Response.json(
-					{ error: "Failed to generate code" },
-					{ status: 500 },
-				);
+				return Response.json({ error: 'Failed to generate code' }, { status: 500 });
 			}
 
 			// Strip markdown code fences if present
 			const cleanCode = generatedCode
-				.replace(/^```python?\n?/, "")
-				.replace(/\n?```\s*$/, "")
+				.replace(/^```python?\n?/, '')
+				.replace(/\n?```\s*$/, '')
 				.trim();
 
 			// Execute the code in a sandbox
-			const sandbox = getSandbox(env.Sandbox, "demo-user");
-			await sandbox.writeFile("/tmp/code.py", cleanCode);
-			const result = await sandbox.exec("python /tmp/code.py");
+			const sandbox = getSandbox(env.Sandbox, 'demo-user');
+			await sandbox.writeFile('/tmp/code.py', cleanCode);
+			const result = await sandbox.exec('python /tmp/code.py');
 
 			return Response.json({
 				success: result.success,
 				question,
 				code: generatedCode,
 				output: result.stdout,
-				error: result.stderr,
+				error: result.stderr
 			});
+
 		} catch (error: any) {
 			return Response.json(
-				{ error: "Internal server error", message: error.message },
-				{ status: 500 },
+				{ error: 'Internal server error', message: error.message },
+				{ status: 500 }
 			);
 		}
 	},
 };
-````
+```
 
 **How it works:**
-
 1. Receives a question via POST to `/execute`
 2. Uses Claude to generate Python code
 3. Writes code to `/tmp/code.py` in the sandbox
@@ -189,11 +176,11 @@ Response:
 
 ```json
 {
-	"success": true,
-	"question": "What is the 10th Fibonacci number?",
-	"code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
-	"output": "55\n",
-	"error": ""
+  "success": true,
+  "question": "What is the 10th Fibonacci number?",
+  "code": "def fibonacci(n):\n    if n <= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\nprint(fibonacci(10))",
+  "output": "55\n",
+  "error": ""
 }
 ```
 
@@ -241,7 +228,6 @@ curl -X POST https://ai-code-executor.YOUR_SUBDOMAIN.workers.dev/execute \
 ## What you built
 
 You created an AI code execution system that:
-
 - Accepts natural language questions
 - Generates Python code with Claude
 - Executes code securely in isolated sandboxes
diff --git a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
index 13784a7bf7fb634..5497b602e6f0f38 100644
--- a/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
+++ b/src/content/docs/sandbox/tutorials/analyze-data-with-ai.mdx
@@ -119,27 +119,24 @@ export default {
 			}
 
 			async function streamToBase64(stream) {
-				const blob = await new Response(stream).blob();
-				const buffer = await blob.arrayBuffer();
-				const bytes = new Uint8Array(buffer);
-
-				// Convert to base64
-				let binary = "";
-				for (let i = 0; i < bytes.length; i++) {
-					binary += String.fromCharCode(bytes[i]);
-				}
-				return btoa(binary);
+			  const blob = await new Response(stream).blob();
+			  const buffer = await blob.arrayBuffer();
+			  const bytes = new Uint8Array(buffer);
+
+			  // Convert to base64
+			  let binary = '';
+			  for (let i = 0; i < bytes.length; i++) {
+			    binary += String.fromCharCode(bytes[i]);
+			  }
+			  return btoa(binary);
 			}
 
 			// Check for generated chart
 			let chart = null;
 			try {
-				const { content, mimeType } = await sandbox.readFile(
-					"/workspace/chart.png",
-					{
-						encoding: "none",
-					},
-				);
+				const { content, mimeType } = await sandbox.readFile("/workspace/chart.png", {
+					encoding: "none"
+				});
 				chart = `data:${mimeType};base64,${await streamToBase64(content)}`;
 			} catch {
 				// No chart generated
diff --git a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
index cc84853855df6ca..1a964dfdb7b13da 100644
--- a/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
+++ b/src/content/docs/sandbox/tutorials/automated-testing-pipeline.mdx
@@ -39,15 +39,9 @@ cd test-pipeline
 Replace `src/index.ts`:
 
 ```typescript
-import {
-	getSandbox,
-	proxyToSandbox,
-	parseSSEStream,
-	type Sandbox,
-	type ExecEvent,
-} from "@cloudflare/sandbox";
+import { getSandbox, proxyToSandbox, parseSSEStream, type Sandbox, type ExecEvent } from '@cloudflare/sandbox';
 
-export { Sandbox } from "@cloudflare/sandbox";
+export { Sandbox } from '@cloudflare/sandbox';
 
 interface Env {
 	Sandbox: DurableObjectNamespace<Sandbox>;
@@ -59,39 +53,34 @@ export default {
 		const proxyResponse = await proxyToSandbox(request, env);
 		if (proxyResponse) return proxyResponse;
 
-		if (request.method !== "POST") {
-			return new Response(
-				'POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }',
-			);
+		if (request.method !== 'POST') {
+			return new Response('POST { "repoUrl": "https://github.com/owner/repo", "branch": "main" }');
 		}
 
 		try {
 			const { repoUrl, branch } = await request.json();
 
 			if (!repoUrl) {
-				return Response.json({ error: "repoUrl required" }, { status: 400 });
+				return Response.json({ error: 'repoUrl required' }, { status: 400 });
 			}
 
 			const sandbox = getSandbox(env.Sandbox, `test-${Date.now()}`);
 
 			try {
 				// Clone repository
-				console.log("Cloning repository...");
+				console.log('Cloning repository...');
 				let cloneUrl = repoUrl;
-
-				if (env.GITHUB_TOKEN && cloneUrl.includes("github.com")) {
-					cloneUrl = cloneUrl.replace(
-						"https://",
-						`https://${env.GITHUB_TOKEN}@`,
-					);
+				
+				if (env.GITHUB_TOKEN && cloneUrl.includes('github.com')) {
+					cloneUrl = cloneUrl.replace('https://', `https://${env.GITHUB_TOKEN}@`);
 				}
 
 				await sandbox.gitCheckout(cloneUrl, {
 					...(branch && { branch }),
 					depth: 1,
-					targetDir: "repo",
+					targetDir: 'repo'
 				});
-				console.log("Repository cloned");
+				console.log('Repository cloned');
 
 				// Detect project type
 				const projectType = await detectProjectType(sandbox);
@@ -100,42 +89,38 @@ export default {
 				// Install dependencies
 				const installCmd = getInstallCommand(projectType);
 				if (installCmd) {
-					console.log("Installing dependencies...");
-					const installStream = await sandbox.execStream(
-						`cd /workspace/repo && ${installCmd}`,
-					);
-
+					console.log('Installing dependencies...');
+					const installStream = await sandbox.execStream(`cd /workspace/repo && ${installCmd}`);
+					
 					let installExitCode = 0;
 					for await (const event of parseSSEStream<ExecEvent>(installStream)) {
-						if (event.type === "stdout" || event.type === "stderr") {
+						if (event.type === 'stdout' || event.type === 'stderr') {
 							console.log(event.data);
-						} else if (event.type === "complete") {
+						} else if (event.type === 'complete') {
 							installExitCode = event.exitCode;
 						}
 					}
-
+					
 					if (installExitCode !== 0) {
 						return Response.json({
 							success: false,
-							error: "Install failed",
-							exitCode: installExitCode,
+							error: 'Install failed',
+							exitCode: installExitCode
 						});
 					}
-					console.log("Dependencies installed");
+					console.log('Dependencies installed');
 				}
 
 				// Run tests
-				console.log("Running tests...");
+				console.log('Running tests...');
 				const testCmd = getTestCommand(projectType);
-				const testStream = await sandbox.execStream(
-					`cd /workspace/repo && ${testCmd}`,
-				);
-
+				const testStream = await sandbox.execStream(`cd /workspace/repo && ${testCmd}`);
+				
 				let testExitCode = 0;
 				for await (const event of parseSSEStream<ExecEvent>(testStream)) {
-					if (event.type === "stdout" || event.type === "stderr") {
+					if (event.type === 'stdout' || event.type === 'stderr') {
 						console.log(event.data);
-					} else if (event.type === "complete") {
+					} else if (event.type === 'complete') {
 						testExitCode = event.exitCode;
 					}
 				}
@@ -145,11 +130,13 @@ export default {
 					success: testExitCode === 0,
 					exitCode: testExitCode,
 					projectType,
-					message: testExitCode === 0 ? "All tests passed" : "Tests failed",
+					message: testExitCode === 0 ? 'All tests passed' : 'Tests failed'
 				});
+
 			} finally {
 				await sandbox.destroy();
 			}
+
 		} catch (error: any) {
 			return Response.json({ error: error.message }, { status: 500 });
 		}
@@ -158,46 +145,38 @@ export default {
 
 async function detectProjectType(sandbox: any): Promise<string> {
 	try {
-		await sandbox.readFile("/workspace/repo/package.json");
-		return "nodejs";
+		await sandbox.readFile('/workspace/repo/package.json');
+		return 'nodejs';
 	} catch {}
 
 	try {
-		await sandbox.readFile("/workspace/repo/requirements.txt");
-		return "python";
+		await sandbox.readFile('/workspace/repo/requirements.txt');
+		return 'python';
 	} catch {}
 
 	try {
-		await sandbox.readFile("/workspace/repo/go.mod");
-		return "go";
+		await sandbox.readFile('/workspace/repo/go.mod');
+		return 'go';
 	} catch {}
 
-	return "unknown";
+	return 'unknown';
 }
 
 function getInstallCommand(projectType: string): string {
 	switch (projectType) {
-		case "nodejs":
-			return "npm install";
-		case "python":
-			return "pip install -r requirements.txt || pip install -e .";
-		case "go":
-			return "go mod download";
-		default:
-			return "";
+		case 'nodejs': return 'npm install';
+		case 'python': return 'pip install -r requirements.txt || pip install -e .';
+		case 'go': return 'go mod download';
+		default: return '';
 	}
 }
 
 function getTestCommand(projectType: string): string {
 	switch (projectType) {
-		case "nodejs":
-			return "npm test";
-		case "python":
-			return "python -m pytest || python -m unittest discover";
-		case "go":
-			return "go test ./...";
-		default:
-			return 'echo "Unknown project type"';
+		case 'nodejs': return 'npm test';
+		case 'python': return 'python -m pytest || python -m unittest discover';
+		case 'go': return 'go test ./...';
+		default: return 'echo "Unknown project type"';
 	}
 }
 ```
@@ -224,10 +203,10 @@ You will see progress logs in the wrangler console, and receive a JSON response:
 
 ```json
 {
-	"success": true,
-	"exitCode": 0,
-	"projectType": "nodejs",
-	"message": "All tests passed"
+  "success": true,
+  "exitCode": 0,
+  "projectType": "nodejs",
+  "message": "All tests passed"
 }
 ```
 
@@ -246,7 +225,6 @@ npx wrangler secret put GITHUB_TOKEN
 ## What you built
 
 An automated testing pipeline that:
-
 - Clones Git repositories
 - Detects project type (Node.js, Python, Go)
 - Installs dependencies automatically
diff --git a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
index fc519d4cc81608a..022b3803088764b 100644
--- a/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
+++ b/src/content/docs/sandbox/tutorials/claude-managed-agents.mdx
@@ -19,10 +19,7 @@ Cloudflare provides a self-managed environment for [Claude Managed Agents](https
 
 This integration ships as an open-source deployment template. Fork the repo, deploy it to your Cloudflare account, and customize it as needed.
 
-<LinkButton
-	variant="secondary"
-	href="https://github.com/cloudflare/claude-managed-agents"
->
+<LinkButton variant="secondary" href="https://github.com/cloudflare/claude-managed-agents">
 	Get Started
 </LinkButton>
 
@@ -69,15 +66,15 @@ You need a Workers Paid plan or Enterprise account. [Containers](/containers/) (
 
 The repository includes detailed documentation on each capability:
 
-| Topic                                                                                                                                    | What it covers                                                                                                                                                   |
-| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md)   | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings                                                                             |
-| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md)               | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing                               |
-| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md)           | Pick the best agent execution environment                                                                                                                        |
-| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md)                                         | Give agents their own email addresses and sending abilities                                                                                                      |
-| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md)                 | Observable agent browser interactions with Browser Run                                                                                                           |
-| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md)                         | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
-| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md)                     | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend                                                                                            |
-| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types                                                                                                                      |
-| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md)                                       | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses                               |
-| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md)                                 | Secure access to the CMA control plane                                                                                                                           |
+| Topic | What it covers |
+| --- | --- |
+| [Connecting to private services](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/connecting-to-private-services.md) | Reach services in other clouds, on-prem, or on your laptop with Workers VPC bindings |
+| [Applying egress policies](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/applying-egress-policies.md) | Inject credentials and lock down agent sessions. Set up allow/deny lists, header injection, custom Worker proxies, and VPC routing |
+| [Isolate vs VM-based sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/isolate-vs-vm-sandboxes.md) | Pick the best agent execution environment |
+| [Agent email](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/agent-email.md) | Give agents their own email addresses and sending abilities |
+| [Browser rendering tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/browser-rendering-tools.md) | Observable agent browser interactions with Browser Run |
+| [Adding custom tools](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/adding-custom-tools.md) | New tools are declared in a single file — [`src/tools/custom-tools.ts`](https://github.com/cloudflare/claude-managed-agents/blob/main/src/tools/custom-tools.ts) |
+| [Customizing sandboxes](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/customizing-sandboxes.md) | Change `Dockerfile` and `instance_type` knobs for the MicroVM backend |
+| [Snapshots and state persistence](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/snapshots-and-state-persistence.md) | State persistence across both sandbox types |
+| [Architecture](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/architecture.md) | Request lifecycle from webhook ingress through dispatch to either sandbox backend, and every Worker binding the control plane uses |
+| [Securing access](https://github.com/cloudflare/claude-managed-agents/blob/main/docs/securing-access.md) | Secure access to the CMA control plane |
diff --git a/src/content/docs/sandbox/tutorials/code-review-bot.mdx b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
index 98052e0f745d6e9..daeeff910905556 100644
--- a/src/content/docs/sandbox/tutorials/code-review-bot.mdx
+++ b/src/content/docs/sandbox/tutorials/code-review-bot.mdx
@@ -108,7 +108,9 @@ export default {
 			) {
 				console.log(`Starting review for PR #${payload.pull_request.number}`);
 				// Use waitUntil to ensure the review completes even after response is sent
-				ctx.waitUntil(reviewPullRequest(payload, env).catch(console.error));
+				ctx.waitUntil(
+					reviewPullRequest(payload, env).catch(console.error),
+				);
 				return Response.json({ message: "Review started" });
 			}
 
diff --git a/src/content/docs/secrets-store/audit-logs.mdx b/src/content/docs/secrets-store/audit-logs.mdx
index 90f826135f55949..144a24543be86f5 100644
--- a/src/content/docs/secrets-store/audit-logs.mdx
+++ b/src/content/docs/secrets-store/audit-logs.mdx
@@ -17,4 +17,4 @@ sidebar:
   - A boolean `"value_modified": true` is presented when the secret value is edited.
 - Delete
 
-For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
+For information on how to access and use audit logs, refer to [Fundamentals](/fundamentals/account/account-security/review-audit-logs/).
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/index.mdx b/src/content/docs/secrets-store/index.mdx
index e2ed5d0af9f4441..4d1e230e37ff9e9 100644
--- a/src/content/docs/secrets-store/index.mdx
+++ b/src/content/docs/secrets-store/index.mdx
@@ -16,8 +16,7 @@ head:
 import { Description, Plan } from "~/components";
 
 <Description>
-	Encrypt and store sensitive information as secrets that are securely reusable
-	across your account.
+Encrypt and store sensitive information as secrets that are securely reusable across your account.
 </Description>
 
 <Plan id="secrets_store.properties.availability.summary" />
diff --git a/src/content/docs/secrets-store/integrations/ai-gateway.mdx b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
index af789df84d1a0c0..918c8bcfa39217c 100644
--- a/src/content/docs/secrets-store/integrations/ai-gateway.mdx
+++ b/src/content/docs/secrets-store/integrations/ai-gateway.mdx
@@ -8,4 +8,4 @@ external_link: /ai-gateway/configuration/bring-your-own-keys/
 sidebar:
   order: 3
   label: AI Gateway
----
+---
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/integrations/index.mdx b/src/content/docs/secrets-store/integrations/index.mdx
index a5ce8b0cbe2a887..64d5175c5fd2e82 100644
--- a/src/content/docs/secrets-store/integrations/index.mdx
+++ b/src/content/docs/secrets-store/integrations/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/manage-secrets/how-to.mdx b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
index cb9d42efdc308d9..2fd99158d2495e9 100644
--- a/src/content/docs/secrets-store/manage-secrets/how-to.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/how-to.mdx
@@ -155,4 +155,4 @@ Refer to [Secrets Store API](/api/resources/secrets_store/) for the full API doc
 	method="DELETE"
 />
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/docs/secrets-store/manage-secrets/index.mdx b/src/content/docs/secrets-store/manage-secrets/index.mdx
index e9a5f2e3ffdfc0c..17a01164f12187d 100644
--- a/src/content/docs/secrets-store/manage-secrets/index.mdx
+++ b/src/content/docs/secrets-store/manage-secrets/index.mdx
@@ -28,4 +28,4 @@ If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler)
 - [Create a secret](/secrets-store/manage-secrets/how-to/#create-a-secret)
 - [Duplicate a secret](/secrets-store/manage-secrets/how-to/#duplicate-a-secret)
 - [Edit a secret](/secrets-store/manage-secrets/how-to/#edit-a-secret)
-- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
+- [Delete a secret](/secrets-store/manage-secrets/how-to/#delete-a-secret)
\ No newline at end of file
diff --git a/src/content/docs/security-center/brand-protection.mdx b/src/content/docs/security-center/brand-protection.mdx
index 064f17815b2cfeb..3a021e91ce70f25 100644
--- a/src/content/docs/security-center/brand-protection.mdx
+++ b/src/content/docs/security-center/brand-protection.mdx
@@ -54,7 +54,7 @@ To start searching for new domains that might be trying to impersonate your bran
 
 5. To export all matches from a saved query, select your **Query name** > select the three dots > **Export matches**.
 
-In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the **Show dismissed matches** toggle in the Cloudflare dashboard.
+In the section **Monitor Strings**, you can check all the string queries that you selected to monitor. You can delete, clone, or create notifications for a string query. Refer to [Brand Protection Alerts](#brand-protection-alerts) to set up notifications. You can also dismiss any domain matched in the query if you have investigated and deemed it benign or a false positive. Users can still access their previously dismissed matches by turning on the  **Show dismissed matches** toggle in the Cloudflare dashboard.
 
 ### Logo search (AI-powered)
 
diff --git a/src/content/docs/security-center/changelog.mdx b/src/content/docs/security-center/changelog.mdx
index 889cbe1b2ec6c7b..1c92506953963cf 100644
--- a/src/content/docs/security-center/changelog.mdx
+++ b/src/content/docs/security-center/changelog.mdx
@@ -16,20 +16,20 @@ import { ProductChangelog } from "~/components";
 
 ## 2025-02-03
 
-- Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
+* Security Center now has a role called Brand Protection. This role gives you access to the Brand Protection feature on the API and Cloudflare dashboard. Brand Protection role also gives you access to the Investigate platform, where you can consume the Threat Intel API and URL scanner API calls.
 
 ## 2025-01-20
 
-- On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
+* On the URL scanner, customers who search for a report will now get a list of all reports related to that specific hostname. A hash is also available in the security report. By selecting the hash, the dashboard will list reports containing the same hash.
 
 ## 2024-09-23
 
-- Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
+* Customers can now export all matches from a saved query. Select your **Query name** > select the three dots > **Export matches**.
 
 ## 2024-09-19
 
-- Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
+* Customers can now create a `security.txt` file file to provide the security research team with a standardized way to report vulnerabilities.
 
 ## 2024-07-22
 
-- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
+* Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
diff --git a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
index e90c084b944a737..6749f8a8b7ee551 100644
--- a/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
+++ b/src/content/docs/security-center/cloudforce-one/cloudforce-one.mdx
@@ -7,4 +7,5 @@ products:
 external_link: https://www.cloudflare.com/threat-intelligence/
 sidebar:
   order: 10
+
 ---
diff --git a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
index 33bd1dd3898a1bd..55fbf7081e51889 100644
--- a/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
+++ b/src/content/docs/security-center/cloudforce-one/open-port-scanning.mdx
@@ -10,7 +10,9 @@ sidebar:
     text: Beta
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
+
+
 
 Open Port Scanning allows [Magic Transit](/magic-transit/) and [Bring your Own IPs](/byoip/) users to efficiently monitor IP ranges for security vulnerabilities. This API enables users to scan their designated IP ranges, detect any open ports, and receive daily notifications regarding newly opened ports.
 
@@ -19,24 +21,24 @@ You can access this feature via the [API](/api/resources/cloudforce_one/subresou
 ## Prerequisites
 
 - Cloudforce One Administrator, Administrator and Super Administrator roles.
-- Account token: **Custom API Token** > **Cloudforce One:Edit**.
+- Account token: **Custom API Token** >  **Cloudforce One:Edit**. 
 
 To create a custom API token:
 
 1. From the [Cloudflare dashboard](https://dash.cloudflare.com/profile/api-tokens/), go to **My Profile** > **API Tokens** for user tokens. Go to **Create Custom Token** > **Get started**.
 2. Enter a **Token name**, for example, `Open Port Scanning`.
 3. In **Permissions**:
-   - Choose **Account**.
-   - Select **Cloudforce One** as the account.
-   - Choose **Edit** access.
+    - Choose **Account**.
+    - Select **Cloudforce One** as the account.
+    - Choose **Edit** access.
 4. In Client IP Address Filtering:
-   - In **Operator**, select `is in`.
-   - In **Value**, enter a valid IP address.
+    - In **Operator**, select `is in`.
+    - In **Value**, enter a valid IP address.
 5. Select **Continue to summary**.
 6. Review the token, then select **Create Token**.
 
 :::note
-The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules.
+The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce One team recommends you to allowlist these IPs in your rules. 
 :::
 
 ## Configure Open Port Scanning
@@ -44,56 +46,150 @@ The Open Port Scanner will run from a predetermined set of IPs. The Cloudforce O
 To configure Open Port Scanning, follow these steps:
 
 1. **Create a new scan config**:
-   - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
-   - **Frequency**: Enter the scan frequency in days.
-   - **Ports**: Select the ports to scan. Choose among:
-     - All
-     - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
-     - List of specific ports
+    - **IPs**: Enter the IP ranges you wish to monitor. Ensure that the ranges are correctly formatted to avoid scanning errors. The API will validate if the IPs requested are onboarded to Cloudflare and associated to the account belonging to the API token used.
+    - **Frequency**: Enter the scan frequency in days.
+    - **Ports**: Select the ports to scan. Choose among:
+        - All
+        - Default (refer to [Default ports](/security-center/cloudforce-one/open-port-scanning/#default-ports) for a comprehensive list)
+        - List of specific ports
 2. **Scan IPs**: Initiate the scanning process. The system will analyze the specified IP ranges to identify any open ports.
 3. **Generate list of open ports**: Once the scan is complete, the API will generate a list of detected open ports for review and action.
-4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude any ports that do not require immediate attention.
+4. **Select open ports to list**: Choose which open ports you would like to be notified about. You can exclude  any ports that do not require immediate attention.
 5. **View differences from previous scan**: The API will highlight any changes in open ports since the last scan, allowing you to quickly assess new vulnerabilities.
-6. **Stop scanning**: If necessary, you can stop the scanning process at any time.
-7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open.
+6. **Stop scanning**: If necessary, you can stop  the scanning process at any time.
+7. **Set up alerts**: Configure alerts for specific ports of interest. You will be notified immediately via email or webhook if any of these designated ports become newly open. 
 
 :::note[Beta feature notice]
 Open Port Scanning feature is currently in closed beta. The Cloudforce One team appreciates your feedback as the team works to enhance its functionality and user experience.
-If you want to subscribe to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
+If you want to subscribe  to this feature or participate in the beta program, [join our closed beta for Port Scanning](https://www.cloudflare.com/lp/open-port-scanning-beta/).
 :::
 
 ## Default ports
 
 <Details header="List of default ports">
-	- `80` - `631` - `161` - `137` - `123` - `138` - `1434` - `445` - `135` - `67`
-	- `23` - `53` - `443` - `21` - `139` - `22` - `500` - `68` - `520` - `1900` -
-	`25` - `4500` - `514` - `49152` - `162` - `69` - `5353` - `111` - `49154` -
-	`3389` - `110` - `1701` - `998` - `996` - `997` - `999` - `3283` - `49153` -
-	`445` - `1812` - `136` - `139` - `143` - `53` - `2222` - `135` - `3306` -
-	`2049` - `32768` - `5060` - `8080` - `1025` - `1433` - `3456` - `80` - `1723`
-	- `111` - `995` - `993` - `20031` - `1026` - `7` - `5900` - `1646` - `1645` -
-	`593` - `1025` - `518` - `2048` - `626` - `1027` - `587` - `177` - `1719` -
-	`427` - `497` - `8888` - `4444` - `1023` - `65024` - `199` - `19` - `9` -
-	`49193` - `1029` - `1720` - `49` - `465` - `88` - `1028` - `17185` - `1718` -
-	`49186` - `548` - `113` - `81` - `6001` - `2000` - `10000` - `31337`
+- `80`
+- `631`
+- `161`
+- `137`
+- `123`
+- `138`
+- `1434`
+- `445`
+- `135`
+- `67`
+- `23`
+- `53`
+- `443`
+- `21`
+- `139`
+- `22`
+- `500`
+- `68`
+- `520`
+- `1900`
+- `25`
+- `4500`
+- `514`
+- `49152`
+- `162`
+- `69`
+- `5353`
+- `111`
+- `49154`
+- `3389`
+- `110`
+- `1701`
+- `998`
+- `996`
+- `997`
+- `999`
+- `3283`
+- `49153`
+- `445`
+- `1812`
+- `136`
+- `139`
+- `143`
+- `53`
+- `2222`
+- `135`
+- `3306`
+- `2049`
+- `32768`
+- `5060`
+- `8080`
+- `1025`
+- `1433`
+- `3456`
+- `80`
+- `1723`
+- `111`
+- `995`
+- `993`
+- `20031`
+- `1026`
+- `7`
+- `5900`
+- `1646`
+- `1645`
+- `593`
+- `1025`
+- `518`
+- `2048`
+- `626`
+- `1027`
+- `587`
+- `177`
+- `1719`
+- `427`
+- `497`
+- `8888`
+- `4444`
+- `1023`
+- `65024`
+- `199`
+- `19`
+- `9`
+- `49193`
+- `1029`
+- `1720`
+- `49`
+- `465`
+- `88`
+- `1028`
+- `17185`
+- `1718`
+- `49186`
+- `548`
+- `113`
+- `81`
+- `6001`
+- `2000`
+- `10000`
+- `31337`
 </Details>
 
 ## Frequently Asked Questions
 
 1. What IPs will the scan come from?
-   - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
-   - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
-   - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241`
+
+    - `2a09:bac0:1008:5000:1000:0000:0000:0050/104.30.128.13`
+    - `2a09:bac0:1008:5000:1000:0000:0000:0048/104.30.129.33`
+    - `2001:19f0:1000:2941:5400:4ff:fe70:2a7a/140.82.60.241` 
 
 2. Can the Port Scanner bypass other security rules configured?
-   - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
+
+    - The Cloudforce One team asks customers to ensure they allow the IPs for the scanner to run correctly.
 
 3. How long do scans take?
-   - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
+
+    - Depending on the number of IP addresses and number of ports scanned, scans can take between a few minutes and up to 10 hours.
 
 4. Can I stop automatic scanning?
-   - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
+
+    - Yes, you can decide at any point to stop scan and restart scans when it is convenient for you.
 
 5. What are the limitations for the scans?
-   - Scans are limited to ranges of up to 5,000 IPs.
-   - The API scans both IPv4 and IPv6 IP addresses.
+
+    - Scans are limited to ranges of up to 5,000 IPs.
+    - The API scans both IPv4 and IPv6 IP addresses.
\ No newline at end of file
diff --git a/src/content/docs/security-center/investigate/change-categorization.mdx b/src/content/docs/security-center/investigate/change-categorization.mdx
index bc56bde0cf28d7a..c2efde74687cbbf 100644
--- a/src/content/docs/security-center/investigate/change-categorization.mdx
+++ b/src/content/docs/security-center/investigate/change-categorization.mdx
@@ -6,6 +6,7 @@ products:
   - security-center
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/docs/security-center/investigate/index.mdx b/src/content/docs/security-center/investigate/index.mdx
index 6a3e0202c62c662..f63c519b1be248a 100644
--- a/src/content/docs/security-center/investigate/index.mdx
+++ b/src/content/docs/security-center/investigate/index.mdx
@@ -6,6 +6,7 @@ products:
   - security-center
 sidebar:
   order: 6
+
 ---
 
 :::note[User permission]
diff --git a/src/content/docs/security-center/investigate/investigate-threats.mdx b/src/content/docs/security-center/investigate/investigate-threats.mdx
index 8056b226555f5c8..48ce56a091e23fd 100644
--- a/src/content/docs/security-center/investigate/investigate-threats.mdx
+++ b/src/content/docs/security-center/investigate/investigate-threats.mdx
@@ -6,9 +6,10 @@ products:
   - security-center
 sidebar:
   order: 3
+
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Users can investigate the details of an IP address, domain name, URL, or Autonomous System Number (ASN). You can find the Investigate feature in your Cloudflare account's Security Center and in [Cloudflare Radar](https://radar.cloudflare.com/scan).
 
@@ -105,4 +106,4 @@ To download a report:
    <DashButton url="/?to=/:account/security-center/investigate" />
 
 2. Enter your domain and select **Search**.
-3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
+3. Once the report has been generated, select **Download** and choose between **Download HAR** or **Download JSON**.
\ No newline at end of file
diff --git a/src/content/docs/security-center/investigate/scan-limits.mdx b/src/content/docs/security-center/investigate/scan-limits.mdx
index 00c9e0921faf0d5..4a87a3ad19d63d5 100644
--- a/src/content/docs/security-center/investigate/scan-limits.mdx
+++ b/src/content/docs/security-center/investigate/scan-limits.mdx
@@ -5,13 +5,17 @@ products:
   - security-center
 head: []
 description: Limits
+
 ---
 
 URL scans are limited by search history, Public and Unlisted visibility, and requests per second across different Cloudflare plans.
 
+
+
 | Cloudflare Plan    | Search history | Public scans (per month) | Unlisted scans (per month) | Rate limit       |
 | ------------------ | -------------- | ------------------------ | -------------------------- | ---------------- |
 | **Free / Radar**   | last 50 scans  | 5,000                    | none                       | 1 per 10 seconds |
 | **Self serve**     | 30 days        | 5,000                    | 500                        | 1 per 10 seconds |
 | **Enterprise**     | 12 months      | 10,000                   | 5,000                      | 12 per second    |
 | **Cloudforce One** | Unlimited      | 75,000                   | 20,000                     | 12 per second    |
+
diff --git a/src/content/docs/security/overview.mdx b/src/content/docs/security/overview.mdx
index 91001dcbbfba6db..544b227b7e54dfc 100644
--- a/src/content/docs/security/overview.mdx
+++ b/src/content/docs/security/overview.mdx
@@ -24,11 +24,10 @@ The Security overview page displays:
 
 ## Security action items
 
-**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity.
-
-- **Action item types**:
-  - Suspicious activity
-  - Security insight
+**Security action items** shows you insights and recommendations related to misconfigurations, exposed infrastructure, and suspicious activity. 
+  - **Action item types**:
+    - Suspicious activity
+    - Security insight
 - **Criticality**: Your action items are ranked by the highest criticality, showing critical first, moderate, and low respectively.
 - **Filters**: You can filter your action items by Criticality, Insight Type, and Security Category.
   - Criticality:
@@ -36,20 +35,20 @@ The Security overview page displays:
     - Moderate
     - Critical
   - Insight Types:
-    - Suspicious activity
-    - Exposed infrastructure
-    - Insecure configuration
+    - Suspicious activity 
+    - Exposed infrastructure 
+    - Insecure configuration 
     - Configuration suggestion
     - Compliance Violation
     - Email Security
     - Weak Authentication
-  - Security Category:
+  - Security Category: 
     - Web application exploits
     - AI exploits
-    - DDoS attacks
-    - Bot traffic
-    - API abuse
-    - Client-side abuse
+    - DDoS attacks 
+    - Bot traffic 
+    - API abuse 
+    - Client-side abuse 
     - Fraud
 - **Review**: Review your security action items for more detailed information and recommended actions to resolve.
 - **Load more**: View the full list of security action items.
@@ -72,14 +71,14 @@ Archiving a detected suspicious activity will only archive that item from the se
 
 To view when an action item’s status was changed and the rationale provided for that change, use the following API commands to retrieve audit logs:
 
-| Method | Path                                                                      | Description                                      |
-| ------ | ------------------------------------------------------------------------- | ------------------------------------------------ |
-| `GET`  | `/api/accounts/{accountID}/insights/audit-log`                            | List all audit logs for an account               |
-| `GET`  | `/api/accounts/{accountID}/insights/{insightID}/audit-log`                | List audit logs for a specific issue             |
-| `GET`  | `/api/accounts/{accountID}/issues/audit-log`                              | List all audit logs for account issues           |
-| `GET`  | `/api/accounts/{accountID}/issues/{insightID}/audit-log`                  | List all audit logs for a specific issue         |
-| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log`             | List all audit logs for a domain                 |
-| `GET`  | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
+| Method | Path | Description |
+| ------ | ---- | ----------- |
+| `GET` | `/api/accounts/{accountID}/insights/audit-log` | List all audit logs for an account |
+| `GET` | `/api/accounts/{accountID}/insights/{insightID}/audit-log` | List audit logs for a specific issue |
+| `GET` | `/api/accounts/{accountID}/issues/audit-log` | List all audit logs for account issues |
+| `GET` | `/api/accounts/{accountID}/issues/{insightID}/audit-log` | List all audit logs for a specific issue |
+| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/audit-log` | List all audit logs for a domain |
+| `GET` | `/api/accounts/{accountID}/zones/{zoneID}/insights/{insightID}/audit-log` | List audit logs for a specific issue in a domain |
 
 Refer to our [Security Center API documentation](/api/resources/security_center) to review the action item audit logs by account, domain, or a specific `issue_id`.
 
@@ -94,4 +93,4 @@ View the patterns and highlights from your domain's traffic in the past 30 days.
 The Cloudflare dashboard displays:
 
 - **Monthly requests**: View the monthly requests and traffic that has been mitigated by Cloudflare.
-- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
+- **How you compare to your peers**: For enterprise plans, understand how your security posture compares to others in your industry protected by Cloudflare.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/concepts/index.mdx b/src/content/docs/smart-shield/concepts/index.mdx
index 12403e47aa9a979..1120c7c003aa4c3 100644
--- a/src/content/docs/smart-shield/concepts/index.mdx
+++ b/src/content/docs/smart-shield/concepts/index.mdx
@@ -13,4 +13,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/concepts/network-diagram.mdx b/src/content/docs/smart-shield/concepts/network-diagram.mdx
index 307591a0ae523f1..3eec884e62a0d79 100644
--- a/src/content/docs/smart-shield/concepts/network-diagram.mdx
+++ b/src/content/docs/smart-shield/concepts/network-diagram.mdx
@@ -16,4 +16,4 @@ Requests from visitors first reach a nearby lower-tier data center. For static (
 
 For dynamic (non-cacheable) requests, [Argo Smart Routing](/smart-shield/configuration/argo/) finds the fastest network path to your origin. Between Cloudflare's upper-tier data centers and your origin, [connection reuse](/smart-shield/concepts/connection-reuse/) packages multiple requests into a single connection, reducing the total number of connections your origin handles.
 
-[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
+[Health Checks](/smart-shield/configuration/health-checks/) run from multiple data centers to monitor whether your origin is online and responsive. [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/) provide reserved IP addresses for traffic from Cloudflare to your origin, allowing you to restrict your origin firewall to a small allowlist.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/argo.mdx b/src/content/docs/smart-shield/configuration/argo.mdx
index 0d1fcae78001d37..16a4fce8d7e97be 100644
--- a/src/content/docs/smart-shield/configuration/argo.mdx
+++ b/src/content/docs/smart-shield/configuration/argo.mdx
@@ -18,4 +18,4 @@ Available with Smart Shield + Argo and Smart Shield Advanced.
 
 Cloudflare provides analytics to show the performance benefits of Argo Smart Routing.
 
-<Render file="argo-analytics" product="smart-shield" />
+<Render file="argo-analytics" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
index 3e14a1542d4343a..14f71bac0cc40fc 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/analytics.mdx
@@ -14,9 +14,9 @@ tags:
 import { Render } from "~/components";
 
 <Render
-	file="cache-reserve-analytics"
-	product="cache"
+  file="cache-reserve-analytics"
+  product="cache"
 	params={{
 		conditional: "smart-shield-tile",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
index 9c1e9769086a7e3..8eeb03f8661c785 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/index.mdx
@@ -40,4 +40,4 @@ You can remove all data stored in Cache Reserve. In most cases, deletion takes a
 
 :::note
 If you want to purge your cache instead, refer to [cache configurations](/cache/how-to/purge-cache/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
index 40b660890f6f6f9..5d0b8457ad806be 100644
--- a/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
+++ b/src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx
@@ -13,4 +13,7 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="cache-reserve-operations" product="cache" />
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
index 4af2a88245d5455..6b011755c7d6d69 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/connection-forwarding.mdx
@@ -38,7 +38,7 @@ flowchart LR
 
 If the server does not have access to an applicable IP, the following options are checked and the first that is possible will take place:
 
-- Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
+* Another server in the same data center has access to an applicable IP and the connection is forwarded to that server.
 
 ```mermaid
 flowchart LR
@@ -55,7 +55,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-- Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
+* Another data center in the same location has access to an applicable IP and the connection is forwarded to that data center.
 
 ```mermaid
 flowchart LR
@@ -77,7 +77,7 @@ flowchart LR
         Y --egress--> C
 ```
 
-- Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
+* Another data center in a different location has access to an applicable IP. The closest location is selected and connection is forwarded to that location.
 
 ```mermaid
 flowchart LR
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
index 44ef7eec5859bde..c7f7d638be9549d 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/index.mdx
@@ -14,4 +14,4 @@ import { DirectoryListing } from "~/components";
 
 Refer to the pages below to understand how Dedicated CDN Egress IPs work.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
index 2275ff704685684..4ed679361eb9526 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx
@@ -24,9 +24,9 @@ Dedicated CDN Egress IPs was formerly known as Cloudflare Aegis ([release blog p
 
 With Dedicated CDN Egress IPs, you can:
 
-- Lock down your network firewall to only allow traffic from your dedicated IPs.
-- Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
-- Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
+* Lock down your network firewall to only allow traffic from your dedicated IPs.
+* Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
+* Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
 
 ## Scope
 
@@ -40,4 +40,4 @@ Dedicated CDN Egress IPs are included within [BGP advertisement over CNI](/netwo
 
 <DirectoryListing />
 
-[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
+[^1]: From Cloudflare to your origin. Refer to [how it works](/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips/) for details.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
index 7e7eb7f4fe8699d..bf1bd852f10c57a 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/ips-utilization.mdx
@@ -16,7 +16,7 @@ Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data and monitor
 
 <Render file="concurrent-connections-explainer" product="smart-shield" />
 
-Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the [example](#example) below for a quickstart.
+Refer to the [GraphQL Analytics API documentation](/analytics/graphql-api/getting-started/) for further guidance, or consider the  [example](#example) below for a quickstart.
 
 ## GraphQL schema
 
@@ -25,19 +25,19 @@ The specific schema to get Dedicated CDN Egress IPs data is called `aegisIpUtili
 You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions:
 
 - `datetimeFiveMinutes` <Type text="time" />
-  - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
+    - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
 
 - `popName` <Type text="string" />
-  - The Cloudflare point of presence (PoP). For example, `sjc`.
+    - The Cloudflare point of presence (PoP). For example, `sjc`.
 
 - `egressIp` <Type text="string" />
-  - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
+    - Your assigned Dedicated CDN Egress IP. For example, `192.0.2.1`.
 
 - `origin` <Type text="string" />
-  - Origin IP and port. For example, `203.0.113.150:443`.
+    - Origin IP and port. For example, `203.0.113.150:443`.
 
 - `popUtilizationKey` <Type text="string" />
-  - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
+    - The Cloudflare point of presence (PoP), the Dedicated CDN Egress IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.
 
 ## Example
 
@@ -47,100 +47,100 @@ You can also select the button at the bottom to use this query for your account
 
 ```graphql graphql-api-explorer "popName: "<CLOUDFLARE_POP>"" "egressIp: "<YOUR_EGRESS_IP>"" "origin: "<ORIGIN_IP_AND_PORT>""
 query AegisIpUtilizationQuery(
-	$accountTag: string
-	$datetimeStart: string
-	$datetimeEnd: string
+  $accountTag: string
+  $datetimeStart: string
+  $datetimeEnd: string
 ) {
-	viewer {
-		utilization: accounts(filter: { accountTag: $accountTag }) {
-			avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				avg {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					popName: "<CLOUDFLARE_POP>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					egressIp: "<YOUR_EGRESS_IP>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-
-			filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
-				limit: 100
-				filter: {
-					datetimeFiveMinutes_geq: $datetimeStart
-					datetimeFiveMinutes_leq: $datetimeEnd
-					origin: "<ORIGIN_IP_AND_PORT>"
-				}
-				orderBy: [datetimeFiveMinutes_ASC]
-			) {
-				max {
-					utilization
-				}
-				dimensions {
-					datetimeFiveMinutes
-					popUtilizationKey
-				}
-			}
-		}
-	}
+  viewer {
+    utilization: accounts(filter: { accountTag: $accountTag }) {
+      avgByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        avg {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      maxByPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterPopUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          popName: "<CLOUDFLARE_POP>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterIPUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          egressIp: "<YOUR_EGRESS_IP>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+
+      filterOriginUtilization: aegisIpUtilizationAdaptiveGroups(
+        limit: 100
+        filter: {
+          datetimeFiveMinutes_geq: $datetimeStart
+          datetimeFiveMinutes_leq: $datetimeEnd
+          origin: "<ORIGIN_IP_AND_PORT>"
+        }
+        orderBy: [datetimeFiveMinutes_ASC]
+      ) {
+        max {
+          utilization
+        }
+        dimensions {
+          datetimeFiveMinutes
+          popUtilizationKey
+        }
+      }
+    }
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
index da17ba92284032c..f36cbde97e071bb 100644
--- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
+++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx
@@ -63,4 +63,4 @@ Workers subrequests — requests from one Worker to another — are expected to
 
 For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
 
-[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
+[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
index 2ff26322bf71a01..121427dcf85f924 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/analytics.mdx
@@ -15,4 +15,7 @@ import { Render } from "~/components";
 
 Use Health Checks analytics to debug possible origin issues.
 
-<Render file="health-checks-analytics" product="smart-shield" />
+<Render
+  file="health-checks-analytics"
+	product="smart-shield"
+/>
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/index.mdx b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
index 0f3fdf5c2c0f9a7..ca2d659d7d5eb14 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/index.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/index.mdx
@@ -24,4 +24,4 @@ Available for Pro, Business, and Enterprise customers in all Smart Shield packag
 
 ## Further reading
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
index 07cacf201721425..292d644b16b754d 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/setup.mdx
@@ -20,8 +20,8 @@ Refer to the section below to learn how to manage your Smart Shield health check
 3. For Health Checks, select **Manage**.
 4. Select **Create** or find an existing health check and select **Edit**.
 5. Fill out the form or edit existing values, paying special attention to:
-   - The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
-   - **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
+   * The values for **Interval** and **Check regions**, because decreasing the **Interval** and increasing **Check regions** may increase the load on your origin server.
+   * **Retries**, which specify the number of retries to attempt in case of a timeout before marking the origin as unhealthy.
 6. Select **Save and Deploy**.
 
 ## Configure alerts
diff --git a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
index e269a8febaf8111..5a42572ca2e935b 100644
--- a/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
+++ b/src/content/docs/smart-shield/configuration/health-checks/zone-lockdown.mdx
@@ -15,4 +15,4 @@ tags:
 
 import { Render } from "~/components";
 
-<Render file="zone-lockdown" product="smart-shield" />
+<Render file="zone-lockdown" product="smart-shield" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/index.mdx b/src/content/docs/smart-shield/configuration/index.mdx
index 6244ba2195424e8..9a1b637e55751a5 100644
--- a/src/content/docs/smart-shield/configuration/index.mdx
+++ b/src/content/docs/smart-shield/configuration/index.mdx
@@ -12,4 +12,4 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
index 49cf513c617947e..9073a8017865420 100644
--- a/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx
@@ -16,4 +16,4 @@ import { Render } from "~/components";
 Available with Smart Shield Advanced.
 :::
 
-<Render file="regional-tiered-cache" product="cache" />
+<Render file="regional-tiered-cache" product="cache" />
\ No newline at end of file
diff --git a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
index 9b9c6760721cd54..f7fafaa47aea6a9 100644
--- a/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
+++ b/src/content/docs/smart-shield/configuration/smart-tiered-cache.mdx
@@ -18,4 +18,4 @@ Available in all Smart Shield packages.
 
 With data centers around the world, Cloudflare caches content very close to end users. However, if a piece of content is not in cache, the Cloudflare data centers must contact the origin server to receive the cacheable content. Tiered cache works by dividing Cloudflare's data centers into a hierarchy of lower-tiers and upper-tiers, where only upper-tiers can ask your origin for content.
 
-<Render file="smart-tiered-cache" product="cache" />
+<Render file="smart-tiered-cache" product="cache" />
\ No newline at end of file
diff --git a/src/content/docs/spectrum/about/byoip.mdx b/src/content/docs/spectrum/about/byoip.mdx
index 3e3fb82322e59aa..b574fc12e5048f2 100644
--- a/src/content/docs/spectrum/about/byoip.mdx
+++ b/src/content/docs/spectrum/about/byoip.mdx
@@ -5,18 +5,22 @@ description: Use your own IP addresses with Spectrum applications.
 products:
   - spectrum
 weight: 0
+
 ---
 
-import { APIRequest, Render } from "~/components";
+import { APIRequest, Render } from "~/components"
 
 When creating a Spectrum application, Cloudflare normally assigns an arbitrary IP from Cloudflare’s IP pool to your application. If you want to be explicit in your network setup or use your own IP addresses, BYOIP with Spectrum allows you to do just that.
 
 BYOIP stands for [Bring Your Own IP](/byoip/). If you own an IP prefix you can migrate it to Cloudflare. After migration, Cloudflare broadcasts your IP prefix and traffic is routed to the global Cloudflare network. However, without configuration, Cloudflare will not know how to handle this traffic. The last step is to add Spectrum applications for all applications that you wish to protect with the IP addresses you want associated with them.
 
+
 :::caution
 
+
 When switching from non-BYOIP to BYOIP, if you are already using a Spectrum application, you need to delete your configurations and recreate new ones.
 
+
 :::
 
 The smallest prefixes that Cloudflare currently supports is /24 for IPv4 and /48 for IPv6.
@@ -31,22 +35,22 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 
 ```json
 {
-	"id": "4590376cf2994d72cee36828ec4eff19",
-	"protocol": "tcp/22",
-	"dns": {
-		"type": "ADDRESS",
-		"name": "ssh.example.com"
-	},
-	"origin_direct": ["tcp://192.0.2.1:22"],
-	"ip_firewall": true,
-	"proxy_protocol": false,
-	"spp": false,
-	"tls": "off",
-	"traffic_type": "direct",
-	"edge_ips": {
-		"type": "static",
-		"ips": ["198.51.100.10", "2001:DB8::1"]
-	}
+  "id": "4590376cf2994d72cee36828ec4eff19",
+  "protocol": "tcp/22",
+  "dns": {
+    "type": "ADDRESS",
+    "name": "ssh.example.com"
+  },
+  "origin_direct": ["tcp://192.0.2.1:22"],
+  "ip_firewall": true,
+  "proxy_protocol": false,
+  "spp": false,
+  "tls": "off",
+  "traffic_type": "direct",
+  "edge_ips": {
+    "type": "static",
+    "ips": ["198.51.100.10", "2001:DB8::1"]
+  }
 }
 ```
 
@@ -55,20 +59,25 @@ To use an IP, it must be assigned to a Spectrum app to create the appropriate A
 In the example below, the application routes traffic through Cloudflare’s HTTP pipeline, including WAF, Workers and CDN functionality.
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		protocol: "tcp/80",
-		dns: {
-			type: "ADDRESS",
-			name: "www.example.com",
-		},
-		origin_direct: ["tcp://192.0.2.1:80"],
-		tls: "off",
-		traffic_type: "http",
-		edge_ips: {
-			type: "static",
-			ips: ["198.51.100.10", "2001:DB8::1"],
-		},
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    protocol: "tcp/80",
+    dns: {
+      type: "ADDRESS",
+      name: "www.example.com"
+    },
+    origin_direct: [
+      "tcp://192.0.2.1:80"
+    ],
+    tls: "off",
+    traffic_type: "http",
+    edge_ips: {
+      type: "static",
+      ips: [
+        "198.51.100.10",
+        "2001:DB8::1"
+      ]
+    }
+  }}
 />
diff --git a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
index 30cfcf85e672028..21f55d4cd8281c7 100644
--- a/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
+++ b/src/content/docs/spectrum/about/ddos-for-spectrum.mdx
@@ -5,6 +5,7 @@ description: Layer 3 and 4 DDoS protection for TCP and UDP Spectrum applications
 products:
   - spectrum
 weight: 0
+
 ---
 
 Spectrum provides DDoS Protection at layers 3-4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/), that is against TCP and UDP based DDoS attacks.
diff --git a/src/content/docs/spectrum/about/ftp.mdx b/src/content/docs/spectrum/about/ftp.mdx
index 68f7e8ff116275c..1d666adace4bcc4 100644
--- a/src/content/docs/spectrum/about/ftp.mdx
+++ b/src/content/docs/spectrum/about/ftp.mdx
@@ -13,15 +13,17 @@ Enabling Spectrum for FTP is not straightforward due to the implementation of th
 
 :::note
 
+
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
+
 :::
 
 ## How FTP Operates
 
 FTP leverages two different sockets, one for issuing commands and the other for actual data transfer. The control socket takes care of users logging in and sending commands, and the data socket is where directory listings and files actually get transferred.
 
-There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects _back_ to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
+There are two ways in which client and server can establish a data socket: active and passive. In active mode, the server connects *back* to the client on a port that they have specified, which can create issues where clients are behind an NAT. The alternative is passive mode, where the server opens an extra port that the client then connects to. For an overview of active versus passive FTP, refer to [Active FTP vs. Passive FTP, a Definitive Explanation](http://slacksite.com/other/ftp.html).
 
 In passive mode, the FTP server communicates a port that the client should connect to, which is done on the control socket via a PASV command. By default, the FTP server responds with the IP address that it is listening on. This scenario is fine for servers running directly on a public-facing IP but creates issues when a server is behind an NAT, firewall, or Cloudflare Spectrum.
 
@@ -29,7 +31,7 @@ Alternatively, more modern FTP server software supports [FTP extensions](https:/
 
 ## What Does and Does Not Work
 
-Spectrum is able to protect servers serving FTP traffic in _passive mode only_. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
+Spectrum is able to protect servers serving FTP traffic in *passive mode only*. Active mode is not supported due to the fact that the origin server sees the Spectrum IP as being the client instead of the actual client IP. When the client issues a PORT command with their own IP, the FTP server rejects because the two addresses do not match.
 
 Passive mode in combination with EPSV works out of the box with no origin-side configuration required. Note that the client must also support EPSV for this to work. Traditional passive mode with PASV is possible with minimal origin-side configuration (see below, Protecting an FTP server with Spectrum)
 
@@ -69,14 +71,14 @@ Example configuration for [vsftpd](https://security.appspot.com/vsftpd.html):
 
 To use Spectrum TCP to proxy and protect FTPS, specifically ProFTPD, the following example configuration is recommended:
 
-- **Control Port**: Port 21
-- **Data Ports**: Port ranges 50000-50500
+* **Control Port**: Port 21
+* **Data Ports**: Port ranges 50000-50500
 
 On the ProFTPD server side use the following example configuration:
 
-- `MasqueradeAddress`: `www.example.com`
-- `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
-- `PassivePorts`: `50000-50500`
+* `MasqueradeAddress`: `www.example.com`
+* `AllowForeignAddress`: You can use the option `on` to allow all IPs, but it is recommended to only allow [Cloudflare IP](/fundamentals/concepts/cloudflare-ip-addresses/#allow-cloudflare-ip-addresses).
+* `PassivePorts`: `50000-50500`
 
 For more details, refer to the [ProFTPD documentation](http://www.proftpd.org/docs/modules/mod_core.html).
 
diff --git a/src/content/docs/spectrum/about/index.mdx b/src/content/docs/spectrum/about/index.mdx
index 79bf764731996bb..a45de1bbf3080f6 100644
--- a/src/content/docs/spectrum/about/index.mdx
+++ b/src/content/docs/spectrum/about/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information about concepts related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/about/static-ip.mdx b/src/content/docs/spectrum/about/static-ip.mdx
index 9ad484844461329..f075127c3337700 100644
--- a/src/content/docs/spectrum/about/static-ip.mdx
+++ b/src/content/docs/spectrum/about/static-ip.mdx
@@ -5,9 +5,10 @@ description: Assign persistent IP addresses to your Spectrum applications.
 products:
   - spectrum
 weight: 0
+
 ---
 
-import { APIRequest, Render } from "~/components";
+import { APIRequest, Render } from "~/components"
 
 When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.
 
@@ -28,30 +29,35 @@ Once you get your static IP from Cloudflare, you can use it via API, just like [
 When creating a Spectrum application through the API, specify the static IPs that you have been provided. See, for instance, the API example below that creates an application routing traffic through Cloudflare’s HTTP pipeline.
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		protocol: "tcp/80",
-		dns: {
-			type: "ADDRESS",
-			name: "www.example.com",
-		},
-		origin_direct: ["tcp://192.0.2.1:80"],
-		tls: "off",
-		traffic_type: "http",
-		edge_ips: {
-			type: "static",
-			ips: ["198.51.100.10", "2001:DB8::1"],
-		},
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    protocol: "tcp/80",
+    dns: {
+      type: "ADDRESS",
+      name: "www.example.com"
+    },
+    origin_direct: [
+      "tcp://192.0.2.1:80"
+    ],
+    tls: "off",
+    traffic_type: "http",
+    edge_ips: {
+      type: "static",
+      ips: [
+        "198.51.100.10",
+        "2001:DB8::1"
+      ]
+    }
+  }}
 />
 
 ## Check your static IPs
 
 <Render
-	file="check-leased-ips"
+  file="check-leased-ips"
 	product="byoip"
 	params={{
-		product: "static IPs for Spectrum",
+		product: "static IPs for Spectrum"
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/docs/spectrum/glossary.mdx b/src/content/docs/spectrum/glossary.mdx
index e858503baad6ca3..5dfed742cc6ccb5 100644
--- a/src/content/docs/spectrum/glossary.mdx
+++ b/src/content/docs/spectrum/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - spectrum
 sidebar:
   order: 7
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Spectrum documentation.
 
diff --git a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
index bed4a42932be361..3961a4766160937 100644
--- a/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
+++ b/src/content/docs/spectrum/how-to/enable-proxy-protocol.mdx
@@ -5,6 +5,7 @@ description: Pass client IP information to your origin using Proxy protocol v1 o
 products:
   - spectrum
 weight: 0
+
 ---
 
 import { DashButton } from "~/components";
@@ -15,8 +16,10 @@ Some services you run may require knowledge of the true client IP. In those case
 
 :::note
 
+
 This feature requires an Enterprise plan. If you would like to upgrade, contact your account team.
 
+
 :::
 
 ## Enable Proxy Protocol v1 for TCP
diff --git a/src/content/docs/spectrum/how-to/index.mdx b/src/content/docs/spectrum/how-to/index.mdx
index 8edbdf1ca9239c5..9f660cc61eee6f5 100644
--- a/src/content/docs/spectrum/how-to/index.mdx
+++ b/src/content/docs/spectrum/how-to/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information on completing Spectrum related tasks, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/protocols-per-plan.mdx b/src/content/docs/spectrum/protocols-per-plan.mdx
index b82fd38bf63e579..6ae364f5a9f92e8 100644
--- a/src/content/docs/spectrum/protocols-per-plan.mdx
+++ b/src/content/docs/spectrum/protocols-per-plan.mdx
@@ -6,9 +6,10 @@ products:
   - spectrum
 sidebar:
   order: 2
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 On this table, you have information about which protocols are available per plan.
 
diff --git a/src/content/docs/spectrum/reference/analytics.mdx b/src/content/docs/spectrum/reference/analytics.mdx
index 3f021a4dd31e9fb..8ad2a392de6915f 100644
--- a/src/content/docs/spectrum/reference/analytics.mdx
+++ b/src/content/docs/spectrum/reference/analytics.mdx
@@ -9,10 +9,12 @@ tags:
   - Analytics
 ---
 
-import { Render, APIRequest } from "~/components";
+import { Render, APIRequest } from "~/components"
 
 Cloudflare measures the following metrics for every connection.
 
+
+
 | Metric         | Name                                | Example | Unit                 |
 | -------------- | ----------------------------------- | ------- | -------------------- |
 | count          | Count of total events               | `1000`  | Count                |
@@ -23,10 +25,14 @@ Cloudflare measures the following metrics for every connection.
 | duration90th   | 90th percentile connection duration | `1.0`   | Time in milliseconds |
 | duration99th   | 99th percentile connection duration | `1.0`   | Time in milliseconds |
 
+
+
 ## Additional dimensions
 
 You can divide your analytics further by the following dimensions.
 
+
+
 | Dimension | Name                          | Example                                                              |
 | --------- | ----------------------------- | -------------------------------------------------------------------- |
 | event     | Connection Event              | `connect`, `progress`, `disconnect`, `originError`, `clientFiltered` |
@@ -34,10 +40,14 @@ You can divide your analytics further by the following dimensions.
 | coloName  | Colo Name                     | `SFO`                                                                |
 | ipVersion | IP version used by the client | `4`, `6`                                                             |
 
+
+
 ## Operators for filtering
 
 Use the operators below to filter data.
 
+
+
 | Operator | Name                     | URL Encoded |
 | -------- | ------------------------ | ----------- |
 | `==`     | Equals                   | `%3D%3D`    |
@@ -47,6 +57,8 @@ Use the operators below to filter data.
 | `>=`     | Greater than or equal to | `%3E%3D`    |
 | `<=`     | Less than or equal to    | `%3C%3D`    |
 
+
+
 <Render file="api-combine-filters" product="fundamentals" />
 
 ## Analytics request structure
@@ -56,26 +68,26 @@ Use the operators below to filter data.
 /api/v4/zones/{zone_id}/spectrum/analytics/events/bytime?metrics=METRICS&dimensions=DIMENSIONS&filters=FILTERS&since=FROM_TS&sort=SORT&until=TO_TS&limit=LIMIT
 ```
 
-- METRICS is one or more metrics (such as count) to compute
-- DIMENSIONS can be used to break down the data by given attributes
-- FILTERS used to filter rows by one or more dimensions (see Filters section below)
-- SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
-- TO_TS is that end of time interval to query, defaults to current time
-- FROM_TS is that start of time interval to query, defaults to TO_TS - 6 hours
-- STEP is used to select time series resolution when using endpoint:
-- auto or omitted - selects time step most appropriate to time interval
-  - year
-  - quarter
-  - month
-  - week
-  - day
-  - hour
+* METRICS is one or more metrics (such as count) to compute
+* DIMENSIONS can be used to break down the data by given attributes
+* FILTERS used to filter rows by one or more dimensions (see Filters section below)
+* SORT is the sort order for the result set; sort fields must be included in METRICS or DIMENSIONS
+* TO\_TS is that end of time interval to query, defaults to current time
+* FROM\_TS is that start of time interval to query, defaults to TO\_TS - 6 hours
+* STEP is used to select time series resolution when using endpoint:
+* auto or omitted - selects time step most appropriate to time interval
+  * year
+  * quarter
+  * month
+  * week
+  * day
+  * hour
 
 ## Analytics query example
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/analytics/events/summary"
-	method="GET"
+  path="/zones/{zone_id}/spectrum/analytics/events/summary"
+  method="GET"
 />
 
 Refer to the [Spectrum API documentation](/api/resources/spectrum/subresources/analytics/subresources/aggregates/subresources/currents/methods/get/) for more examples of API requests.
diff --git a/src/content/docs/spectrum/reference/index.mdx b/src/content/docs/spectrum/reference/index.mdx
index 2f5495921b7c522..1cb17fdcb764a75 100644
--- a/src/content/docs/spectrum/reference/index.mdx
+++ b/src/content/docs/spectrum/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information related to Spectrum, refer to the sections below.
 
diff --git a/src/content/docs/spectrum/reference/layer-7-analytics.mdx b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
index ed2b0717d749251..ac15ed1aa946651 100644
--- a/src/content/docs/spectrum/reference/layer-7-analytics.mdx
+++ b/src/content/docs/spectrum/reference/layer-7-analytics.mdx
@@ -6,7 +6,7 @@ products:
   - spectrum
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Even when you have Spectrum enabled to handle Layer 4 traffic (for example, TCP/UDP connections), you may still notice traffic in your Layer 7 (L7) analytics dashboard. This is due to the way Cloudflare's Layer 7 <GlossaryTooltip term="content delivery network (CDN)">CDN</GlossaryTooltip>
  and Spectrum handle customer identity differently.
@@ -42,4 +42,4 @@ This means traffic for this hostname undergoes the standard Layer 7 CDN products
 
 If you want to prevent traffic for Layer-4-only Spectrum hostnames from being proxied through Layer 7 to your origin (including unwanted scans or requests), we recommend implementing a Layer 7 WAF (Web Application Firewall) rule. This rule can block traffic directed at specific hostnames or ports, ensuring that only legitimate traffic reaches your Spectrum service.
 
-For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
+For example, you can create a WAF rule to block requests to `spectrum.example.com` unless they originate from a Spectrum IP or a customer's Spectrum BYOIP. The traffic will still be logged in Layer 7 Analytics, including WAF Security Events, but this prevents it from arriving at the wrong address and looping through the CDN a second time.
\ No newline at end of file
diff --git a/src/content/docs/spectrum/reference/logs.mdx b/src/content/docs/spectrum/reference/logs.mdx
index e5c27ce81e5be5e..0ee954278aec0d5 100644
--- a/src/content/docs/spectrum/reference/logs.mdx
+++ b/src/content/docs/spectrum/reference/logs.mdx
@@ -19,6 +19,8 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 
 ## Status Codes
 
+
+
 | Code | Description                                                                                        |
 | ---- | -------------------------------------------------------------------------------------------------- |
 | 0    | Connection was opened successfully.                                                                |
@@ -50,3 +52,4 @@ Spectrum [log events](/logs/logpush/logpush-job/datasets/) can be configured thr
 | 533  | Internal error while resolving origin to an IP.                                                    |
 | 540  | The client/edge TLS handshake failed due to an invalid configuration.                              |
 | 999  | Unknown connection error.                                                                          |
+
diff --git a/src/content/docs/spectrum/reference/settings-by-plan.mdx b/src/content/docs/spectrum/reference/settings-by-plan.mdx
index 9865188065dbb98..c243f1c03952069 100644
--- a/src/content/docs/spectrum/reference/settings-by-plan.mdx
+++ b/src/content/docs/spectrum/reference/settings-by-plan.mdx
@@ -5,12 +5,19 @@ description: Spectrum API fields and settings available by Cloudflare plan.
 products:
   - spectrum
 weight: 0
+
 ---
 
+
+
 Certain fields in Spectrum request and response bodies require an Enterprise plan. To upgrade your plan, contact your account team.
 
 Spectrum properties requiring an Enterprise plan:
 
+
+
+
+
 | Name                 | Type    | Description                                                                                                                                                                                                                                                                                                              | Example                                                    |
 | -------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
 | `origin_dns`         | object  | Method and parameters used to discover the origin server address via DNS. Valid record types are `A`, `AAAA`, `SRV` and empty (both `A` and `AAA`).<br />A request must contain either an `origin_dns` parameter or an `origin_direct` parameter. When both are specified the service returns an `HTTP 400 Bad Request`. | `origin_dns: {type: A, name: mqtt.example.com, ttl: 1200}` |
@@ -18,6 +25,11 @@ Spectrum properties requiring an Enterprise plan:
 | `proxy_protocol`     | string  | Enables Proxy Protocol to the origin. Spectrum supports `v1`, `v2`, and `simple` proxy protocols. Refer to [Proxy Protocol](/spectrum/how-to/enable-proxy-protocol/) for more details.                                                                                                                                   | `off`                                                      |
 | `ip_firewall`        | boolean | Enables IP Access rules for this application.                                                                                                                                                                                                                                                                            | `true`                                                     |
 | `tls`                | string  | Type of TLS termination for the application. Options are `off` (default, also known as Passthrough), `flexible`, `full`, and `strict`. Refer to [Configuration Options](/spectrum/reference/configuration-options/) for descriptions of each.                                                                            | `full`                                                     |
-| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic_type set to `direct`.                                                                                                                                                                                   | `true`                                                     |
+| `argo_smart_routing` | boolean | Enables Argo Smart Routing for the application. Note that it is only available for TCP applications with traffic\_type set to `direct`.                                                                                                                                                                                  | `true`                                                     |
+
+
+
+
 
 Review the [Spectrum API documentation](/api/resources/spectrum/subresources/apps/methods/list/) for example API requests.
+
diff --git a/src/content/docs/speed/aim.mdx b/src/content/docs/speed/aim.mdx
index 95fc9acbd18a0d7..c8139eed9a0013a 100644
--- a/src/content/docs/speed/aim.mdx
+++ b/src/content/docs/speed/aim.mdx
@@ -4,6 +4,7 @@ description: Measure real-world internet quality metrics for your visitors.
 products:
   - speed
 title: Aggregated Internet Measurement
+
 ---
 
 Aggregated Internet Measurement (AIM) helps you understand your Internet quality to identify scenarios that your Internet connection is good or bad for. Typically, an Internet speed test provides you with upload and download speeds, which may not always provide a holistic view of your Internet quality.
@@ -14,28 +15,28 @@ AIM uses a scoring rubric that assigns point values based on speed tests to help
 
 AIM analyzes the following metrics to generate your score:
 
-- Latency
-- Packet Loss
-- Download
-- Upload
-- Loaded Latency
-- Jitter
+* Latency
+* Packet Loss
+* Download
+* Upload
+* Loaded Latency
+* Jitter
 
-After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC. These scores will indicate how good your Internet is in each of these scenarios.
+After the test is run and a point value is assigned to each metric, the points are translated to a network score for streaming, gaming, and webchat/RTC.  These scores will indicate how good your Internet is in each of these scenarios.
 
 The possible network scores are:
 
-- Bad
-- Poor
-- Average
-- Good
-- Great
+* Bad
+* Poor
+* Average
+* Good
+* Great
 
 ## Improve your network score
 
 You have a few options to help improve network scores.
 
-- **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
-- **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
-- **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
-- **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
+* **Switch to a wired connection.** When possible, switch to a wired connection instead of wireless to avoid performance issues due to radio interference and signal strength.
+* **Move closer to your router.** If you are unable to use a wired connection, try to move closer to your wireless router. Signal strength drops as you move away from your wireless router and a weaker signal means poorer connectivity. Keep in mind that any objects or materials between you and your wireless router can also have a negative impact on signal strength.
+* **Upgrade your router.** Ensure you are using a router capable of handling smarter queueing with hardware that will not fall over under load.
+* **Contact your ISP.** If you’re using a wired connection or have a good connection to your wireless router and are still seeing issues, you may have issues with your Internet connection and should reach out to your ISP.
diff --git a/src/content/docs/speed/glossary.mdx b/src/content/docs/speed/glossary.mdx
index 2fb9f99dba9493c..fc3634a28e51568 100644
--- a/src/content/docs/speed/glossary.mdx
+++ b/src/content/docs/speed/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Cloudflare Speed documentation.
 products:
   - speed
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Speed documentation.
 
diff --git a/src/content/docs/speed/observatory/dashboard.mdx b/src/content/docs/speed/observatory/dashboard.mdx
index 6a18975aceb0150..1017a25218c61a5 100644
--- a/src/content/docs/speed/observatory/dashboard.mdx
+++ b/src/content/docs/speed/observatory/dashboard.mdx
@@ -40,10 +40,11 @@ The **Network Performance** section shows timing data that can help pinpoint whe
 
 - **Time to First Byte (TTFB)**: Measures the time between the initial request and the first byte of the response.
 - **Time to Last Byte (TTLB) Breakdown**: Provides a breakdown of response phases:
-  - DNS resolution time
-  - TCP connection time
-  - Request processing time at the server
-  - Response transfer time
+
+    - DNS resolution time
+    - TCP connection time
+    - Request processing time at the server
+    - Response transfer time
 
 This breakdown helps identify whether delays are caused by DNS, connection setup, server processing, or response delivery.
 
@@ -76,4 +77,4 @@ Use the Speed Overview dashboard to:
 - Track **Core Web Vitals** to ensure a good user experience.
 - Analyze **Network Performance** to identify latency bottlenecks.
 - Diagnose errors with **HTTP Traffic** insights.
-- Confirm site reliability using **Synthetic Monitoring** results.
+- Confirm site reliability using **Synthetic Monitoring** results.
\ No newline at end of file
diff --git a/src/content/docs/speed/observatory/rum-beacon.mdx b/src/content/docs/speed/observatory/rum-beacon.mdx
index 8e343c58ee410d5..66c0e8035856ce1 100644
--- a/src/content/docs/speed/observatory/rum-beacon.mdx
+++ b/src/content/docs/speed/observatory/rum-beacon.mdx
@@ -8,6 +8,7 @@ tags:
   - Privacy
 sidebar:
   order: 4
+ 
 ---
 
 The RUM beacon is a JavaScript snippet that runs when a Cloudflare customer enables RUM through [Web Analytics](/web-analytics/) or [Observatory](/speed/observatory/). This script runs in users' browsers when they visit the customer's site, and its purpose is to collect performance-related data, for example, page load time, and send it to Cloudflare's systems for processing. This [data](/web-analytics/data-metrics/) is then presented to the customer, providing valuable insights into the website's performance and usage.
@@ -16,7 +17,7 @@ The RUM beacon script can be enabled into a webpage in two ways:
 
 - **One-click setup**: For [sites proxied through Cloudflare](/web-analytics/get-started/#sites-proxied-through-cloudflare) that have Web Analytics enabled, the snippet can be _automatically_ injected into pages as the HTML response passes through Cloudflare's edge network to the browser by simply enabling the automatic injection option.
 
-- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML.
+- **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML. 
 
 ## Data collection
 
@@ -24,36 +25,36 @@ Once downloaded to the browser, the RUM beacon script runs as JavaScript in the
 
 The data collected from the browser is summarized in the table below:
 
-| Field                  | Example                                                                                                              | Description                                  | How it is collected                                                                                                                                                                                                                                                                                       |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pageloadId`           | 0c698922-8d60-40bf-85ac-7982b5f8034d                                                                                 | The unique ID for the page.                  | Generated in the browser code.                                                                                                                                                                                                                                                                            |
-| `referrer`             | https://cfrumtest.com/                                                                                               | The referring page URL.                      | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
-| `startTime`            | 1693488419352                                                                                                        | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                                                                                                                                                                         |
-| `memory`               | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }`                               | Measures memory heap size.                   | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                                                                                                                                                                                    |
-| `timings`              | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming)                    | Timing data.                                 | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)                                                                                                                                                           |
-| `timingV2`             | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data.                      | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
-| `resources`            | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)     | Resource timing data.                        | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                                                                                                                                                                    |
-| `firstPaint`           | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)           | Paint timing data.                           | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming)                                                                                                                                                                                          |
-| `firstContentfulPaint` | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `FCP`                  | 209                                                                                                                  | First Contentful Paint metric.               | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `LCP`                  | 209                                                                                                                  | Largest Contentful Paint metric.             | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `CLS`                  | 0.001                                                                                                                | Cumulative Layout Shift metric.              | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-|  |
-| `TTFB`                 | 0.03                                                                                                                 | Time to First Byte metric.                   | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `INP`                  | 1.23                                                                                                                 | Interaction to Next Paint metric.            | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                                                                                                                                                                                                        |
-| `landingPath`          | https://cfrumtest.com/                                                                                               | The landing page URL.                        | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                                                                                                                                                               |
+| Field      | Example  | Description  | How it is collected    |
+|------------|----------|--------------|------------------------|
+| `pageloadId`  | 0c698922-8d60-40bf-85ac-7982b5f8034d  | The unique ID for the page. | Generated in the browser code.  |
+| `referrer`    | https://cfrumtest.com/ | The referring page URL. | If it is a multi-page application (MPA), then it is generated from [document.referrer](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. |
+| `startTime`  | 1693488419352  | Baseline for performance-related timestamps. | [performance.timeOrigin](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)                                                        |
+| `memory` | `{ totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 }` | Measures memory heap size. | [performance.memory](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated)                                              |
+| `timings` | Object of [PerformanceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming) | Timing data. | [performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when `timingV2` is unavailable)     |
+| `timingV2` | Array of [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType)                                   |
+| `resources`  | Array of [PerformanceResourceTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | Resource timing data.  | [performance.getEntriesByType("resource")](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming)                                     |
+| `firstPaint` | Array of [PerformancePaintTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | Paint timing data. | [performance.getEntriesByType("paint")](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) |
+| `firstContentfulPaint` | 209  | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1] |
+| `FCP`        | 209 | First Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `LCP`        | 209 | Largest Contentful Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `CLS`        | 0.001 | Cumulative Layout Shift metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+                                                           |
+| `TTFB`       | 0.03 | Time to First Byte metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `INP`        | 1.23 | Interaction to Next Paint metric. | [web-vitals module](https://www.npmjs.com/package/web-vitals) [^1]                                                           |
+| `landingPath`| https://cfrumtest.com/  | The landing page URL. | [performance.getEntriesByType("navigation")](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | 
 
 ## Data processing
 
 RUM data is generally processed at the nearest Cloudflare data center based on how the incoming request is routed. This is determined by a number of factors including [Anycast](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) and [Unimog](https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/). Since RUM data does not use location services, it may be processed in a different country or region from where it originated. Although the RUM service receives the client/source IP address from the beacon as part of normal HTTP request handling process, it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs.
 
-## Privacy information
+## Privacy information 
 
 The RUM beacon script does not store any data in the browser or access any storage data, such as [cookies](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie), [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage), [sessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage), IP address, or [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB). The data we collect is performance data from the browser performance [APIs](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API). This performance data is ephemeral and only relates to the current webpage that is being viewed. If the user refreshes their browser, all the previous performance data is gone and new performance data starts being available. This data is not stored or accessed from anywhere on the device, it is only available as in-memory data.
 
 ## RUM excluding EEA/EU
 
-Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.
+Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for users connecting to a Cloudflare data center located in the following countries (ISO codes): AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB.   
 
 Free customers have RUM enabled automatically, with EU traffic excluded, and can switch it off if they prefer. Customers on other plans may enable RUM as needed.
 
@@ -63,4 +64,5 @@ Free customers have RUM enabled automatically, with EU traffic excluded, and can
 
     </div>
 
-[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
+
+[^1]: The web-vitals module is an open-source module written by Google. It does not access any type of storage on the browser.
\ No newline at end of file
diff --git a/src/content/docs/speed/observatory/run-speed-test.mdx b/src/content/docs/speed/observatory/run-speed-test.mdx
index 5ae182cbf4eb09c..b86b5c58655a186 100644
--- a/src/content/docs/speed/observatory/run-speed-test.mdx
+++ b/src/content/docs/speed/observatory/run-speed-test.mdx
@@ -50,19 +50,20 @@ RUM uses a lightweight JavaScript beacon to collect the information Observatory
 Quota limits for the number of tests you can run per month are currently the following:
 
 | Plan       | One-off tests | Recurring tests | Frequency of recurring tests |
-| ---------- | ------------- | --------------- | ---------------------------- |
+|------------|---------------|-----------------|------------------------------|
 | Pro        | 50            | 5               | Daily                        |
 | Business   | 100           | 10              | Daily                        |
 | Enterprise | 150           | 15              | Daily                        |
 
 **Available Regions (all plans):**
 
-| Region              | Region                 | Region                  |
-| ------------------- | ---------------------- | ----------------------- |
-| Iowa, USA           | Hamina, Finland        | Changhua County, Taiwan |
-| South Carolina, USA | Madrid, Spain          | Tokyo, Japan            |
-| North Virginia, USA | St. Ghislain, Belgium  | Osaka, Japan            |
-| Dallas, USA         | Eemshaven, Netherlands | Jurong West, Singapore  |
-| Oregon, USA         | Milan, Italy           | Sydney, Australia       |
-| London, England     | Paris, France          | Mumbai, India           |
-| Frankfurt, Germany  | Tel Aviv, Israel       | São Paulo, Brazil       |
+| Region                | Region              | Region             |
+|------------------------|---------------------|--------------------|
+| Iowa, USA             | Hamina, Finland     | Changhua County, Taiwan |
+| South Carolina, USA   | Madrid, Spain       | Tokyo, Japan       |
+| North Virginia, USA   | St. Ghislain, Belgium | Osaka, Japan      |
+| Dallas, USA           | Eemshaven, Netherlands | Jurong West, Singapore |
+| Oregon, USA           | Milan, Italy        | Sydney, Australia  |
+| London, England       | Paris, France       | Mumbai, India      |
+| Frankfurt, Germany    | Tel Aviv, Israel    | São Paulo, Brazil  |
+
diff --git a/src/content/docs/speed/observatory/test-results.mdx b/src/content/docs/speed/observatory/test-results.mdx
index c6bf699af5e19a6..a9b42c82085bb1a 100644
--- a/src/content/docs/speed/observatory/test-results.mdx
+++ b/src/content/docs/speed/observatory/test-results.mdx
@@ -6,6 +6,7 @@ products:
 title: Understand test results
 sidebar:
   order: 3
+
 ---
 
 The test result page shows you how your website performed regarding several key industry metrics. Some of these metrics are presented for synthetic tests and the real user monitoring, and others only apply to synthetic tests or only to real user monitoring.
@@ -35,19 +36,19 @@ These metrics result from the synthetic tests.
 
 These metrics are collected as part of the real user data, as they require real user interaction with a page.
 
-| Metric                                                  | Definition                                                                                                                 |
-| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page. |
+| Metric                                                  | Definition                                                                                                                                                                       |
+| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Interaction to Next Paint ([INP](https://web.dev/inp/)) | Aims to represent a page's overall responsiveness by measuring all click, tap, and keyboard interactions made with a page.                                                       |
 
 Refer to [Data and metrics](/web-analytics/data-metrics/) for more information about the metrics you can find in the Real User Monitoring dashboard. You can find details about [Core Web Vitals](/web-analytics/data-metrics/core-web-vitals/), the debug view and the data collected.
 
 ## Network monitoring metrics
 
-| Metric                                                     | Definition                                                                                                        |
-| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Wait Time                                                  | Measures the time spent waiting for the server to send back the first byte of a response after a request is made. |
-| Load Time                                                  | Measures the total time it takes for a web page to fully load in a user’s browser from the network.               |
-| Time to First Byte ([TTFB](https://web.dev/articles/ttfb)) | Measures the duration between initiating a web page request and receiving the first byte from the server.         |
-| Server Response Time                                       | Measures the time it takes for a server to respond to a request from a user's browser.                            |
-| Connect Time                                               | Measures the time taken to establish a connection between the user's browser and the web server.                  |
-| TLS Time                                                   | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.       |
+| Metric                                            | Definition                                                                                                          |
+| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| Wait Time | Measures the time spent waiting for the server to send back the first byte of a response after a request is made.                                           |
+| Load Time | Measures the total time it takes for a web page to fully load in a user’s browser from the network.                                                         |
+| Time to First Byte ([TTFB](https://web.dev/articles/ttfb))  | Measures the duration between initiating a web page request and receiving the first byte from the server. |
+| Server Response Time | Measures the time it takes for a server to respond to a request from a user's browser.                                                           |
+| Connect Time | Measures the time taken to establish a connection between the user's browser and the web server.                                                         | 
+| TLS Time | Measures the time required to complete the TLS/SSL handshake between the user's browser and the web server.                                                  | 
\ No newline at end of file
diff --git a/src/content/docs/speed/optimization/content/apo.mdx b/src/content/docs/speed/optimization/content/apo.mdx
index f706bab097e8e8c..bf378bf7685846b 100644
--- a/src/content/docs/speed/optimization/content/apo.mdx
+++ b/src/content/docs/speed/optimization/content/apo.mdx
@@ -7,4 +7,5 @@ title: Automatic Platform Optimization
 external_link: /automatic-platform-optimization/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/content/compression.mdx b/src/content/docs/speed/optimization/content/compression.mdx
index e021ae803ef2b55..93ad3418e9054de 100644
--- a/src/content/docs/speed/optimization/content/compression.mdx
+++ b/src/content/docs/speed/optimization/content/compression.mdx
@@ -22,9 +22,9 @@ Cloudflare compresses content in two ways: between Cloudflare and your website v
 In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.
 
 <Stream
-	id="9103750883217fcb9274666fd57ebac1"
-	title="Content compression"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
+  id="9103750883217fcb9274666fd57ebac1"
+  title="Content compression"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/386f9df0-25fc-4d2a-07fa-6dd3497d2e00/public"
 />
 
 :::note
diff --git a/src/content/docs/speed/optimization/content/early-hints.mdx b/src/content/docs/speed/optimization/content/early-hints.mdx
index f40d05197e0f6de..3263897899e5f21 100644
--- a/src/content/docs/speed/optimization/content/early-hints.mdx
+++ b/src/content/docs/speed/optimization/content/early-hints.mdx
@@ -7,4 +7,5 @@ title: Early Hints
 external_link: /cache/advanced-configuration/early-hints/
 sidebar:
   order: 5
+
 ---
diff --git a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
index 778b154ef43acac..b5627175aec2342 100644
--- a/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
+++ b/src/content/docs/speed/optimization/content/fonts/troubleshooting.mdx
@@ -28,10 +28,7 @@ To test that the Fonts feature is working correctly, follow these steps:
 For the feature to work, the response HTML (when the feature is disabled) must include a link tag with `href` pointing to `fonts.googleapis.com`. You can check this on the browser by viewing the source code of the webpage. As an example of what to look for, the following link tag is for the Roboto Google Font:
 
 ```html
-<link
-	href="https://fonts.googleapis.com/css2?family=Roboto&display=swap"
-	rel="stylesheet"
-/>
+<link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">
 ```
 
 If the tag does not exist in the HTML, but you are still sure that your page is using Google Fonts, it might be that your hosting provider is optimizing your Google Fonts on the server. This can prevent Cloudflare Fonts from working properly.
diff --git a/src/content/docs/speed/optimization/content/index.mdx b/src/content/docs/speed/optimization/content/index.mdx
index e1a5decf41e6b26..a778f875d6059cc 100644
--- a/src/content/docs/speed/optimization/content/index.mdx
+++ b/src/content/docs/speed/optimization/content/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
index 115046f10c28f12..148e6cc5d93b485 100644
--- a/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
+++ b/src/content/docs/speed/optimization/content/rocket-loader/ignore-javascripts.mdx
@@ -23,13 +23,15 @@ Rocket Loader will still optimize the loading of all other scripts on the page.
 
 :::note
 
+
 If Rocket Loader is only impacting a specific page, use a [Configuration Rule](/rules/configuration-rules/) to exclude that page by URL.
 
+
 :::
 
 ## Limitations
 
-- Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
-- If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
-- The `data-cfasync` attribute must be added before the `src` attribute.
-- Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
+* Adding this attribute within JavaScript will not work if you wish to exclude the script from Rocket Loader.
+* If the script you want Rocket Loader to ignore has dependency on other JavaScript(s) on the page, those dependencies must also have the `data-cfasync="false"` attribute.
+* The `data-cfasync` attribute must be added before the `src` attribute.
+* Rocket Loader will recognize the tag when either single or double quotes are placed around the attribute value.
diff --git a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
index e17a32a6e8a3b82..8b56ec1c37765c8 100644
--- a/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
+++ b/src/content/docs/speed/optimization/content/shared-dictionaries.mdx
@@ -43,11 +43,11 @@ Shared dictionaries work when all of the following are true:
 
 The protocol uses two new request and response headers and two new content encodings:
 
-| Header                           | Direction        | Purpose                                                                                             |
-| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- |
+| Header                           | Direction        | Purpose                                                                                            |
+| -------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
 | `Use-As-Dictionary`              | Origin → browser | Marks a response as usable as a dictionary for future requests matching the supplied `match` value. |
-| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.            |
-| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).      |
+| `Available-Dictionary`           | Browser → origin | Advertises the SHA-256 hash of a dictionary the browser already has for the request URL.           |
+| `Content-Encoding: dcb` or `dcz` | Origin → browser | Delta-compressed against the advertised dictionary, using Brotli (`dcb`) or Zstandard (`dcz`).     |
 
 The first response for a versioned asset includes `Use-As-Dictionary`, and the browser stores the response. On subsequent requests for assets matching the pattern, the browser sends `Available-Dictionary: :<sha256>:` and adds `dcb, dcz` to `Accept-Encoding`. Your origin compresses the new asset against the dictionary and returns it with `Content-Encoding: dcb` or `dcz`. The browser uses its stored copy to reconstruct the full response.
 
diff --git a/src/content/docs/speed/optimization/content/smart-hints.mdx b/src/content/docs/speed/optimization/content/smart-hints.mdx
index 9df2f2740a81901..74a30be29625c81 100644
--- a/src/content/docs/speed/optimization/content/smart-hints.mdx
+++ b/src/content/docs/speed/optimization/content/smart-hints.mdx
@@ -7,4 +7,5 @@ title: Smart Hints
 external_link: https://blog.cloudflare.com/smart-hints/
 sidebar:
   order: 8
+
 ---
diff --git a/src/content/docs/speed/optimization/content/speed-brain.mdx b/src/content/docs/speed/optimization/content/speed-brain.mdx
index 979f0002e29fc50..e0de7cbfe69f617 100644
--- a/src/content/docs/speed/optimization/content/speed-brain.mdx
+++ b/src/content/docs/speed/optimization/content/speed-brain.mdx
@@ -10,13 +10,7 @@ sidebar:
 description: Learn how Speed Brain enhances web performance by prefetching likely next pages, improving metrics like LCP and TTFB.
 ---
 
-import {
-	FeatureTable,
-	TabItem,
-	Tabs,
-	APIRequest,
-	DashButton,
-} from "~/components";
+import { FeatureTable, TabItem, Tabs, APIRequest, DashButton } from "~/components";
 
 Speed Brain is a tool for improving web page performance by prefetching the most likely next navigation.
 
@@ -117,6 +111,7 @@ You can also configure Speed Brain using Terraform. For more details, refer to t
 ## Caveats
 
 - Since prefetch responses are not guaranteed to be rendered by the browser, Speed Brain includes two safeguards to minimize the risk of [unsafe prefetching](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#unsafe_prefetching):
+
   - Speed Brain will not prefetch on routes that run Workers. Without this safeguard, prefetch requests could inadvertently run Worker logic that assumes the incoming request is a normal (that is, not a prefetch) request. An example of this could be an incrementing page view counter running in a Worker. A page view counter should not increment if the page is not actually rendered in the browser.
 
   - Prefetch requests will never reach origin servers. Prefetch requests only serve content that is stored in Cloudflare’s Cache. If the content is not in Cache, the prefetch request will not continue to origin servers. Without this safeguard, origin server state could be modified despite the prefetch response not being rendered in the browser. An example of this could be a prefetch `GET` request to a sign-out URL inadvertently triggering a sign-out action on the server.
diff --git a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
index e125fcbbe0254bf..274ba87dc345bae 100644
--- a/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/content/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Optimization issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/image-resizing.mdx b/src/content/docs/speed/optimization/images/image-resizing.mdx
index 6594df5754962d0..5e5c8613ef540aa 100644
--- a/src/content/docs/speed/optimization/images/image-resizing.mdx
+++ b/src/content/docs/speed/optimization/images/image-resizing.mdx
@@ -7,4 +7,5 @@ title: Image Resizing
 external_link: /images/optimization/transformations/overview/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/images/index.mdx b/src/content/docs/speed/optimization/images/index.mdx
index c079cac0a17b480..d027767b2a3faf5 100644
--- a/src/content/docs/speed/optimization/images/index.mdx
+++ b/src/content/docs/speed/optimization/images/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/polish.mdx b/src/content/docs/speed/optimization/images/polish.mdx
index 631c4cbe263d8c9..c529447865e7b61 100644
--- a/src/content/docs/speed/optimization/images/polish.mdx
+++ b/src/content/docs/speed/optimization/images/polish.mdx
@@ -7,4 +7,5 @@ title: Polish
 external_link: /images/polish/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
index cb64aa9539c46b7..1f8d029c7d93ae9 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Image issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
index fb72840fc7b149a..9ac31a532e60906 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/multiple-optimizations.mdx
@@ -5,6 +5,7 @@ products:
   - speed
 source: https://support.cloudflare.com/hc/en-us/articles/200168046-Will-Cloudflare-s-image-optimization-features-help-if-I-m-already-optimizing-images-
 title: Image optimization on optimized images
+
 ---
 
 Cloudflare's [image optimization features](/speed/optimization/images/) will likely not help much if you are already optimizing your images in some way (Smush.it, etc.).
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
index ce279de1efcba70..26bdaff52e6866e 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/polish.mdx
@@ -6,4 +6,5 @@ products:
 title: Polish statuses
 external_link: /images/polish/cf-polished-statuses/
 weight: 0
+
 ---
diff --git a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
index 12268c9dc18cddc..ed4e61afdf15934 100644
--- a/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
+++ b/src/content/docs/speed/optimization/images/troubleshooting/troubleshooting-missing-images.mdx
@@ -15,9 +15,9 @@ If images are missing from your website, other Cloudflare features may be interf
 To troubleshoot:
 
 1. Perform one of the following actions:
-   - [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
-   - [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
-   - Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 
+   * [Purge cache](/cache/how-to/purge-cache) for the URL of the missing image file.
+   * [Temporarily pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/).
+   * Disable [Rocket Loader](/speed/optimization/content/rocket-loader/enable/).
 2. Retest the image load in a private browser tab.
 3. If the issue is not fixed, try another of the actions suggested in Step 1.
diff --git a/src/content/docs/speed/optimization/index.mdx b/src/content/docs/speed/optimization/index.mdx
index 83b3fba317047d6..bd80c971ba9878a 100644
--- a/src/content/docs/speed/optimization/index.mdx
+++ b/src/content/docs/speed/optimization/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The Optimization section will show you a list of Cloudflare products that are recommended for enhancing your website's performance.
 
diff --git a/src/content/docs/speed/optimization/measurement.mdx b/src/content/docs/speed/optimization/measurement.mdx
index 89a7f989f4b71dc..016533a4dd1986e 100644
--- a/src/content/docs/speed/optimization/measurement.mdx
+++ b/src/content/docs/speed/optimization/measurement.mdx
@@ -6,6 +6,7 @@ products:
 title: Measurement
 sidebar:
   order: 2
+
 ---
 
 Enable measurement to track your traffic in a privacy-first manner, optimizing your site's speed tools. To access this feature, you need to enable [Web Analytics](/web-analytics/) on your website. This analytics tool leverages [Real User Measurement](/speed/observatory/run-speed-test/#enable-real-user-monitoring-rum) (RUM) data, providing insights based on actual user interactions to enhance site performance effectively.
diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx
index 13e54b4c22eaedd..74d4e0a9ae7f530 100644
--- a/src/content/docs/speed/optimization/protocol/http2.mdx
+++ b/src/content/docs/speed/optimization/protocol/http2.mdx
@@ -56,10 +56,10 @@ The origin web server may be sending improperly formatted HTTP response headers.
 
 #### Resolution
 
-Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements:
+Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements: 
 
 - [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5)
-- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1)
+- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) 
 - [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1)
 
 ### Compression issues
diff --git a/src/content/docs/speed/optimization/protocol/index.mdx b/src/content/docs/speed/optimization/protocol/index.mdx
index 094dadd43d13cf2..fdfe4aa14eb11b1 100644
--- a/src/content/docs/speed/optimization/protocol/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/index.mdx
@@ -8,8 +8,9 @@ sidebar:
   order: 4
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
index 957822a95ff61cf..45783c25f400853 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/enhanced-http2-prioritization-ios-safari.mdx
@@ -4,6 +4,7 @@ description: Fix Enhanced HTTP/2 Prioritization issues on iOS and Safari.
 products:
   - speed
 title: Enhanced HTTP/2 Prioritization negatively affects iOS/Safari devices
+
 ---
 
 Occasionally, [Enhanced HTTP/2 Prioritization](/speed/optimization/protocol/enhanced-http2-prioritization/) can negatively affect the experience of visitors using Safari on macOS or any browser on iOS.
@@ -16,8 +17,10 @@ If visitors using using Safari on macOS or any browser on iOS are experiencing i
 
 :::note
 
+
 Sometimes, [HTTP/2](/speed/optimization/protocol/http2/) will cause **Enhanced HTTP/2 Prioritization** to be re-enabled automatically.
 
 If you notice this happening, also disable **HTTP/2**.
 
+
 :::
diff --git a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
index 804f216d9cf3f8c..0d6974f96123177 100644
--- a/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
+++ b/src/content/docs/speed/optimization/protocol/troubleshooting/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting Protocol optimization issues
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/speed/optimization/recommendations.mdx b/src/content/docs/speed/optimization/recommendations.mdx
index aac4598f71a5531..1367d8efb7789e2 100644
--- a/src/content/docs/speed/optimization/recommendations.mdx
+++ b/src/content/docs/speed/optimization/recommendations.mdx
@@ -6,6 +6,7 @@ products:
 title: Recommendations
 sidebar:
   order: 1
+
 ---
 
 In the **Recommendations** tab, with one click you can enable all the recommended settings available for your plan. You can enable all the recommended settings at once or you can also just enable the ones you want.
diff --git a/src/content/docs/speed/smart-shield.mdx b/src/content/docs/speed/smart-shield.mdx
index 9fc997ea18add10..76f0af22755c9f7 100644
--- a/src/content/docs/speed/smart-shield.mdx
+++ b/src/content/docs/speed/smart-shield.mdx
@@ -7,4 +7,5 @@ title: Smart Shield
 sidebar:
   order: 4
 external_link: /smart-shield/
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/speed/troubleshooting.mdx b/src/content/docs/speed/troubleshooting.mdx
index 6f7d78e7f34c259..1a73653e90dc280 100644
--- a/src/content/docs/speed/troubleshooting.mdx
+++ b/src/content/docs/speed/troubleshooting.mdx
@@ -7,15 +7,12 @@ title: Troubleshooting
 hideChildren: true
 sidebar:
   order: 20
+
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 The following topics are useful for troubleshooting Speed issues.
 
-<ResourcesBySelector
-	directory="speed"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="speed" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
+
diff --git a/src/content/docs/ssl/changelog.mdx b/src/content/docs/ssl/changelog.mdx
index 96577c758525512..c96ac0914a9da7c 100644
--- a/src/content/docs/ssl/changelog.mdx
+++ b/src/content/docs/ssl/changelog.mdx
@@ -16,7 +16,7 @@ import { ProductChangelog } from "~/components";
 
 ## 2024-10-18
 
-**New cloudflare_branding flag allows hostnames with over 64 characters for all CAs**
+**New cloudflare\_branding flag allows hostnames with over 64 characters for all CAs**
 
 To order certificates for hostnames longer than 64 characters, customers can now use the `cloudflare_branding` flag when ordering a certificate via [API](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/create/). Setting `cloudflare_branding` to `true` will cause `sni.cloudflaressl.com` to be used as the common name, while the long hostname is added as part of the subject alternative name (SAN).
 
@@ -24,4 +24,4 @@ To order certificates for hostnames longer than 64 characters, customers can now
 
 **SSL.com available with ACM and SSL for SaaS**
 
-SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
+SSL.com is one of the [certificate authorities](/ssl/reference/certificate-authorities/) that Cloudflare partners with. SSL.com is now available as an option to customers with Advanced Certificate Manager (ACM) or SSL for SaaS. Consider our [reference documentation](/ssl/reference/certificate-authorities/#sslcom) for details.
\ No newline at end of file
diff --git a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
index 129b0ea9d7b037b..fda3782b24250c6 100644
--- a/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/forward-a-client-certificate.mdx
@@ -15,4 +15,4 @@ import { Render } from "~/components";
 
 <Render file="add-client-certificate-rfc9440" product="ssl" />
 
-<Render file="forward-client-certificate" product="ssl" />
+<Render file="forward-client-certificate" product="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
index c362c3ea0cbfc69..20bc4a82a73822d 100644
--- a/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
+++ b/src/content/docs/ssl/client-certificates/revoke-client-certificate.mdx
@@ -6,6 +6,7 @@ products:
 title: Revoke a client certificate
 sidebar:
   order: 8
+
 ---
 
 import { DashButton } from "~/components";
@@ -25,8 +26,10 @@ It is not possible to permanently delete client certificates generated with the
 
 :::caution[Important]
 
+
 After revoking a certificate, you must update any mTLS rules that check for the presence of a client certificate so that they block all requests that include a revoked certificate.
 
 For more information, refer to [Check for revoked certificates](/api-shield/security/mtls/configure/#check-for-revoked-certificates).
 
+
 :::
diff --git a/src/content/docs/ssl/concepts.mdx b/src/content/docs/ssl/concepts.mdx
index 074f33eaa264a9e..2f0333d5ec7c728 100644
--- a/src/content/docs/ssl/concepts.mdx
+++ b/src/content/docs/ssl/concepts.mdx
@@ -25,9 +25,9 @@ Since [Cloudflare's global network](https://www.cloudflare.com/network/) is at t
 The [edge certificates](/ssl/edge-certificates/) are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the [Cloudflare Dashboard](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
 
 <Stream
-	id="fe9344af4ab476bf81f4447000f36db66"
-	title="SSL/TLS concepts"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
+  id="fe9344af4ab476bf81f4447000f36db66"
+  title="SSL/TLS concepts"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/7ee0dbb2-bb61-450f-645c-508eb369c100/public"
 />
 
 ### Origin certificate
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
index c4d44c211b0ec09..18550b308521f31 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
@@ -30,9 +30,9 @@ If you are a SaaS provider looking to restrict cipher suites for connections to
 
 Custom cipher suites is a hostname-level setting, which implies that:
 
-- When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
-- The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
-- If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
+* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
+* The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
+* If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
 
 ## Scope
 
@@ -50,4 +50,4 @@ This documentation only refers to connections [between clients and the Cloudflar
 
 Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hostname-priority/) to determine which setting to apply.
 
-ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
+ECDSA cipher suites are prioritized over RSA, and Cloudflare preserves the specified cipher suites in the order they are set. This means that, if both ECDSA and RSA are used, Cloudflare presents the ECDSA ciphers first - in the order they were set - and then the RSA ciphers, also in the order they were set.
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
index c8b458d6184c218..7aae1bb58f1bbd9 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx
@@ -16,31 +16,31 @@ tags:
 
 Cloudflare supports the following cipher suites by default. If needed, you can [restrict your website or application](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) to only use specific cipher suites.
 
-| Cipher name                      | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name                                     |
-| -------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------- |
-| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02b]    | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256       |
-| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca9]    | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 |
-| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02f]    | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256         |
-| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xcca8]    | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   |
-| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc023]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256       |
-| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                                              | \[0xc009]    | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA          |
-| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc027]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256         |
-| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc013]    | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA            |
-| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                                              | \[0x9c]      | TLS_RSA_WITH_AES_128_GCM_SHA256               |
-| AES128-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3c]      | TLS_RSA_WITH_AES_128_CBC_SHA256               |
-| AES128-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x2f]      | TLS_RSA_WITH_AES_128_CBC_SHA                  |
-| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc02c]    | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384       |
-| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc024]    | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384       |
-| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                                                          | \[0xc030]    | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384         |
-| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                                                  | \[0xc028]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384         |
-| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                                              | \[0xc014]    | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA            |
-| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                                              | \[0x9d]      | TLS_RSA_WITH_AES_256_GCM_SHA384               |
-| AES256-SHA256                    | TLS 1.2          | Legacy                                                                                              | \[0x3d]      | TLS_RSA_WITH_AES_256_CBC_SHA256               |
-| AES256-SHA                       | TLS 1.0          | Legacy                                                                                              | \[0x35]      | TLS_RSA_WITH_AES_256_CBC_SHA                  |
-| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                                              | \[0x0a]      | TLS_RSA_WITH_3DES_EDE_CBC_SHA                 |
-| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x01} | TLS_AES_128_GCM_SHA256                        |
-| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x02} | TLS_AES_256_GCM_SHA384                        |
-| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                                                          | \{0x13,0x03} | TLS_CHACHA20_POLY1305_SHA256                  |
+| Cipher name | Minimum protocol | [Security recommendation](/ssl/edge-certificates/additional-options/cipher-suites/recommendations/) | Cipher suite | IANA name |
+| -------------------------------- | ---------------- | ------------------------------------------------------------------------ | ------------ | --------------------------------------------------- |
+| ECDHE-ECDSA-AES128-GCM-SHA256    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02b]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256      |
+| ECDHE-ECDSA-CHACHA20-POLY1305    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca9]    | TLS\_ECDHE\_ECDSA\_WITH\_CHACHA20\_POLY1305\_SHA256 |
+| ECDHE-RSA-AES128-GCM-SHA256      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02f]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256        |
+| ECDHE-RSA-CHACHA20-POLY1305      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xcca8]    | TLS\_ECDHE\_RSA\_WITH\_CHACHA20\_POLY1305\_SHA256   |
+| ECDHE-ECDSA-AES128-SHA256        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc023]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256      |
+| ECDHE-ECDSA-AES128-SHA           | TLS 1.0          | Legacy                                                                   | \[0xc009]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA         |
+| ECDHE-RSA-AES128-SHA256          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc027]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256        |
+| ECDHE-RSA-AES128-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc013]    | TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA           |
+| AES128-GCM-SHA256                | TLS 1.2          | Legacy                                                                   | \[0x9c]      | TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256               |
+| AES128-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3c]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256               |
+| AES128-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x2f]      | TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA                  |
+| ECDHE-ECDSA-AES256-GCM-SHA384    | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc02c]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384      |
+| ECDHE-ECDSA-AES256-SHA384        | TLS 1.2          | Compatible, Legacy                                                       | \[0xc024]    | TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384      |
+| ECDHE-RSA-AES256-GCM-SHA384      | TLS 1.2          | Modern, Compatible, Legacy                                               | \[0xc030]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384        |
+| ECDHE-RSA-AES256-SHA384          | TLS 1.2          | Compatible, Legacy                                                       | \[0xc028]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384        |
+| ECDHE-RSA-AES256-SHA             | TLS 1.0          | Legacy                                                                   | \[0xc014]    | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA           |
+| AES256-GCM-SHA384                | TLS 1.2          | Legacy                                                                   | \[0x9d]      | TLS\_RSA\_WITH\_AES\_256\_GCM\_SHA384               |
+| AES256-SHA256                    | TLS 1.2          | Legacy                                                                   | \[0x3d]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256               |
+| AES256-SHA                       | TLS 1.0          | Legacy                                                                   | \[0x35]      | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA                  |
+| DES-CBC3-SHA                     | TLS 1.0          | Legacy                                                                   | \[0x0a]      | TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA                 |
+| AEAD-AES128-GCM-SHA256 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x01}  | TLS\_AES\_128\_GCM\_SHA256                          |
+| AEAD-AES256-GCM-SHA384 \*        | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x02}  | TLS\_AES\_256\_GCM\_SHA384                          |
+| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3          | Modern, Compatible, Legacy                                               | \{0x13,0x03}  | TLS\_CHACHA20\_POLY1305\_SHA256                     |
 
 :::note[* TLS 1.3 minimum protocol]
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
index 186ef035f3bc82f..33d50ea3a037245 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 11
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Once you set up SSL/TLS on your application, you can adjust the following settings on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page:
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
index c5f7c351636e7ea..cb0cd6575e94980 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
@@ -8,14 +8,7 @@ sidebar:
   order: 13
 ---
 
-import {
-	FeatureTable,
-	TabItem,
-	Tabs,
-	APIRequest,
-	Render,
-	DashButton,
-} from "~/components";
+import { FeatureTable, TabItem, Tabs, APIRequest, Render, DashButton } from "~/components";
 
 Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer.
 
@@ -93,13 +86,13 @@ Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hos
 In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and authentication placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
 <APIRequest
-	path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
-	method="PUT"
-	json={{
-		value: "1.2",
+  path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
+  method="PUT"
+  json={{
+		"value": "1.2"
 	}}
 	parameters={{
-		setting_id: "min_tls_version",
+		setting_id: "min_tls_version"
 	}}
 />
 
@@ -107,6 +100,7 @@ In the following example, the minimum TLS version for a specific hostname will b
 
 If you are a SaaS provider looking to configure minimum TLS version for your custom hostnames, refer to the Cloudflare for SaaS [TLS management](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version).
 
+
 ## Test supported TLS versions
 
-<Render file="test-tls-version" product="ssl" />
+<Render file="test-tls-version" product="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
index f302408667237f8..0e4362cf11468cb 100644
--- a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
+++ b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx
@@ -10,14 +10,7 @@ tags:
   - TLS
 ---
 
-import {
-	Details,
-	FeatureTable,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { Details, FeatureTable, Render, TabItem, Tabs, DashButton } from "~/components";
 
 TLS 1.3 enables the latest version of the TLS protocol (when supported) for improved security and performance.
 
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
index 9de3f9a1b2d4d87..4a643427148e0dc 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/api-commands.mdx
@@ -6,15 +6,19 @@ products:
 title: API commands
 sidebar:
   order: 5
+
 ---
 
 Use the following API commands to manage advanced certificates. If you are using our API for the first time, review our [API documentation](/fundamentals/api/).
 
-| Command                                                                                                                                                        | Method   | Endpoint                                             | Additional notes                                                                            |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                                                | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
-| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                                                              | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                  |
-| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                                                   | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
+
+
+| Command                                                                                                                                                 | Method   | Endpoint                                             | Additional notes                                                                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| [Order advanced certificate](/api/resources/ssl/subresources/certificate_packs/methods/create/)                                     | `POST`   | `zones/<<ZONE_ID>>/ssl/certificate_packs/order`      |                                                                                             |
+| [Restart certificate validation](/api/resources/ssl/subresources/certificate_packs/methods/edit/)                | `PATCH`  | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     | For a Certificate Pack in a `validation_timed_out` status.                                                                                             |
+| [Delete certificate pack](/api/resources/ssl/subresources/certificate_packs/methods/delete/)                                       | `DELETE` | `zones/<<ZONE_ID>>/ssl/certificate_packs/<<ID>>`     |                                                                                             |
 | [List certificate packs in a zone](/api/resources/ssl/subresources/certificate_packs/methods/list/)                                                            | `GET`    | `zones/<<ZONE_ID>>/ssl/certificate_packs?status=all` | This API call returns all certificate packs for a domain (Universal, Custom, and Advanced). |
 | List Cipher Suite settings: [Get zone setting](/api/resources/zones/subresources/settings/methods/get/) with `ciphers` as the setting name in the URI path     | `GET`    | `zones/<<ZONE_ID>>/settings/ciphers`                 |                                                                                             |
 | Change Cipher Suite settings: [Edit zone setting](/api/resources/zones/subresources/settings/methods/edit/) with `ciphers` as the setting name in the URI path | `PATCH`  | `zones/<<ZONE_ID>>/settings/ciphers`                 | To restore default settings, send a blank array in the `value` parameter.                   |
+
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
index 6261626f47813e8..8bb9170bb3e5e55 100644
--- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
@@ -10,13 +10,7 @@ description: Learn how to create, delete and perform other operations to manage
   your Cloudflare Advanced SSL certificates.
 ---
 
-import {
-	AvailableNotifications,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { AvailableNotifications, Render, TabItem, Tabs, DashButton } from "~/components";
 
 ## Create a certificate
 
diff --git a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
index 9612b1b4e300149..cd1a9df4c9a9acd 100644
--- a/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
+++ b/src/content/docs/ssl/edge-certificates/backup-certificates.mdx
@@ -6,9 +6,10 @@ products:
 title: Backup certificates
 sidebar:
   order: 9
+
 ---
 
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 If Cloudflare is providing [authoritative DNS](/dns/zone-setups/full-setup/) for your domain, Cloudflare will issue a backup [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for every standard Universal certificate issued.
 
diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx
index d8baa4eef05cff2..81472be5e1532d4 100644
--- a/src/content/docs/ssl/edge-certificates/caa-records.mdx
+++ b/src/content/docs/ssl/edge-certificates/caa-records.mdx
@@ -77,3 +77,4 @@ Check CAA at all levels of your CNAME chain:
 dig yourdomain.com CAA +short
 dig cname-target.com CAA +short
 ```
+
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
index 96fb56d94da1db3..cc1c3b4df79dbed 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/bundling-methodologies.mdx
@@ -6,6 +6,7 @@ products:
 title: Bundle methodologies
 sidebar:
   order: 4
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -42,4 +43,4 @@ The related value for the `bundle_method` parameter when using the [API](/api/re
 
 User-defined allows you to paste your own certificate chain and present that bundle to clients. If you are using a self-signed certificate (not recommended), you must use this mode.
 
-The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
+The related value for the `bundle_method` parameter when using the [API](/api/resources/custom_certificates/methods/create/) is `force`.
\ No newline at end of file
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
index 450b178703c442c..b6e2aa56fcc596a 100644
--- a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
+++ b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
@@ -8,9 +8,10 @@ sidebar:
 head: []
 description: Learn how renewal and expiration work when using Cloudflare Custom
   SSL certificates.
+
 ---
 
-import { GlossaryTooltip, DashButton } from "~/components";
+import { GlossaryTooltip, DashButton } from "~/components"
 
 ## Renew custom certificates
 
diff --git a/src/content/docs/ssl/edge-certificates/ech.mdx b/src/content/docs/ssl/edge-certificates/ech.mdx
index f41c594d329fe41..0fbfdfc7d498d82 100644
--- a/src/content/docs/ssl/edge-certificates/ech.mdx
+++ b/src/content/docs/ssl/edge-certificates/ech.mdx
@@ -35,7 +35,7 @@ In practice, this means that any intermediary that is looking at your traffic wi
 
 In the example below, a user is visiting `example.com`. Without ECH, any intermediate networks will be able to detect the website being accessed by the user. With ECH, the visible information will be limited to `cloudflare-ech.com` instead.
 
-<br />
+<br/>
 
 ```mermaid
 flowchart LR
@@ -46,7 +46,7 @@ A(User visits <code>example.com</code>)
     A -- Without ECH  --> D(intermediaries see <code>example.com</code>)-->B(Cloudflare)
 ```
 
-<br />
+<br/>
 
 For more details about ECH protocol technology, refer to our [introductory blog](https://blog.cloudflare.com/encrypted-client-hello/).
 
diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
index 01b85e22786233d..1f5ef82895c17f4 100644
--- a/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
+++ b/src/content/docs/ssl/edge-certificates/geokey-manager/supported-options.mdx
@@ -31,7 +31,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 | WEUR        | Western Europe        |
 | WNAM        | Western North America |
 
----
+***
 
 ## Available countries
 
@@ -39,7 +39,7 @@ For customers with Geo Key Manager v2, you can use the `policy` parameter to spe
 
 Examples of supported countries are Japan, Canada, India, and Australia.
 
----
+***
 
 ## Highest security data centers
 
diff --git a/src/content/docs/ssl/edge-certificates/index.mdx b/src/content/docs/ssl/edge-certificates/index.mdx
index e7cf9b2a13c1a4d..ffb763f9a56da56 100644
--- a/src/content/docs/ssl/edge-certificates/index.mdx
+++ b/src/content/docs/ssl/edge-certificates/index.mdx
@@ -22,7 +22,7 @@ This behavior occurs when all of the following conditions are true:
 
 - The zone is on a [subdomain setup](/dns/zone-setups/subdomain-setup/).
 - The certificate has a subject or SAN that is a wildcard for the zone's parent domain.
-  :::
+:::
 
 ## Use cases
 
diff --git a/src/content/docs/ssl/edge-certificates/staging-environment.mdx b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
index 19eb3fbbdf32035..339031829e8da8c 100644
--- a/src/content/docs/ssl/edge-certificates/staging-environment.mdx
+++ b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
@@ -8,21 +8,22 @@ sidebar:
   order: 8
   badge:
     text: Beta
+
 ---
 
-import { FeatureTable, DashButton } from "~/components";
+import { FeatureTable, DashButton } from "~/components"
 
 Use your certificate staging environment to test new custom (modern) certificates before pushing them to your production environment. This process helps you solve potential certificate problems **before** there's an incident, such as when:
 
-- You make a mistake when uploading a new custom certificate.
-- You misunderstand the order of your certificates.
-- Clients have previously pinned your custom certificate, causing a TLS termination error.
+* You make a mistake when uploading a new custom certificate.
+* You misunderstand the order of your certificates.
+* Clients have previously pinned your custom certificate, causing a TLS termination error.
 
 ## Availability
 
 <FeatureTable id="ssl.staging_environment" />
 
----
+***
 
 ## Use your staging environment
 
@@ -48,9 +49,9 @@ curl --resolve <HOSTNAME>:<PORT>:<STAGING_IP> https://<HOSTNAME> -iv
 
 You should confirm whether:
 
-- TLS termination is successful.
-- The right certificate is being served at the edge.
-- Any clients are pinning the old certificate.
+* TLS termination is successful.
+* The right certificate is being served at the edge.
+* Any clients are pinning the old certificate.
 
 ### 3. Push certificate to production
 
@@ -77,7 +78,7 @@ If you roll out a custom (modern) certificate to production and encounter issues
 3. Select **Deactivate**.
 4. Select **Push to Staging**.
 
----
+***
 
 ## Limitations
 
@@ -89,5 +90,5 @@ Currently, staging environments are only available to Enterprise customers parti
 
 At the moment, staging environments have limited functionality:
 
-- Only custom (modern) certificates
-- Only accessed via the dashboard
+* Only custom (modern) certificates
+* Only accessed via the dashboard
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
index 70ebac7297e8244..3104afffd410349 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/alerts.mdx
@@ -9,15 +9,13 @@ sidebar:
 head:
   - tag: title
     content: Alerts for Universal SSL
+
 ---
 
-import { AvailableNotifications, Render } from "~/components";
+import { AvailableNotifications, Render } from "~/components"
 
 You can configure alerts to receive notifications for changes in your certificates.
 
-<AvailableNotifications
-	product="SSL/TLS"
-	notificationFilter="Universal SSL Alert"
-/>
+<AvailableNotifications product="SSL/TLS" notificationFilter="Universal SSL Alert" />
 
 <Render file="get-started" product="notifications" />
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
index 818182201a137ed..b594fc5113be2e0 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
@@ -25,11 +25,13 @@ To avoid errors with your domain, either [upload a custom certificate](/ssl/edge
 If you disable Universal SSL, you may experience errors with the following scenarios:
 
 - **Enabled features**:
+
   - [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/)
   - [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/)
   - [Opportunistic Encryption](/ssl/edge-certificates/additional-options/opportunistic-encryption/)
 
 - **Other setups**:
+
   - [Page Rules](/rules/page-rules/) that redirect traffic to HTTPS
   - HTTP to HTTPS redirects at your origin web server
 
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
index e18e34ce743050c..9caba32b58ee4c2 100644
--- a/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
+++ b/src/content/docs/ssl/edge-certificates/universal-ssl/troubleshooting.mdx
@@ -17,10 +17,10 @@ If a certificate issuance times out, Cloudflare tells you where in the chain of
 
 To resolve timeout issues, try one or more of the following options:
 
-- Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
-- [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
-- Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
-- Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
+* Change the **Proxy status** of related DNS records to **DNS only** (gray-clouded) and wait at least a minute. Then, change the **Proxy status** back to **Proxied** (orange-clouded).
+* [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) and wait at least a minute. Then, re-enable Universal SSL.
+* Send a PATCH request to the [validation endpoint](/api/resources/ssl/subresources/verification/methods/edit/) using the same [DCV method](/ssl/edge-certificates/changing-dcv-method/) (API only). Make sure that the `--data` field is not empty in your request.
+* Review your domain control validation (DCV). Changing the DCV method will restart certificate issuance.
 
 ## Delete certificates
 
diff --git a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
index 08f0a67ed984db2..f525157d8b998f3 100644
--- a/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/configuration/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Get started with Keyless SSL
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 The way you set up Keyless SSL depends on how you route traffic to your keyless server.
 
diff --git a/src/content/docs/ssl/keyless-ssl/glossary.mdx b/src/content/docs/ssl/keyless-ssl/glossary.mdx
index ac939b4a2946953..e64a45f3d972083 100644
--- a/src/content/docs/ssl/keyless-ssl/glossary.mdx
+++ b/src/content/docs/ssl/keyless-ssl/glossary.mdx
@@ -9,6 +9,7 @@ head:
   - tag: title
     content: Glossary | Keyless SSL
 description: Learn more about the common terms related to Keyless SSL.
+
 ---
 
 ## Cloudflare Keyless SSL key server (“key server”)
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
index 3804977bcd01432..0ca6a0fe976beb8 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm.mdx
@@ -69,6 +69,7 @@ brew install azure-cli
    ```
 
 4. If the key server is running in an Azure VM in the same account, use **Managed services** for authorization:
+
    1. Enable managed services on the VM in the UI.
    2. Give your service user (associated with your VM) HSM sign permissions
 
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
index 18a3cbbad52b8b7..df9caf0b486ccaf 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm.mdx
@@ -14,4 +14,4 @@ You can use Cloudflare Keyless SSL with [Fortanix Data Security Manager (DSM)](h
 
 You must have a [Data Security Manager Enterprise Tier](https://www.fortanix.com/start-your-free-trial) and set up a group and an application assigned to the group.
 
-For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
+For detailed guidance, follow the tutorial in the [Fortanix documentation](https://support.fortanix.com/docs/fortanix-data-security-manager-with-cloudflare-integration#50-configure-fortanix-dsm). This guide is based on the Keyless SSL [public DNS](/ssl/keyless-ssl/configuration/public-dns/) option and has been tested using a virtual machine (VM) deployed to Azure running Ubuntu 22.04.3 LTS.
\ No newline at end of file
diff --git a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
index a28200144687ee8..fd448a9791cb833 100644
--- a/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/hardware-security-modules/index.mdx
@@ -6,11 +6,12 @@ products:
 title: Hardware security modules
 sidebar:
   order: 2
+
 ---
 
 In addition to private keys stored on disk, Keyless SSL supports keys stored in a Hardware Security Module (HSM) via the PKCS#11 standard. Keyless uses PKCS#11 for signing and decrypting payloads without having direct access to the private keys.
 
----
+***
 
 ## Why use Keyless SSL with an HSM?
 
@@ -18,7 +19,7 @@ Hardware Security Modules (HSMs) facilitate a higher level of protection for you
 
 Moreover, many HSMs are also capable of generating keys and producing cryptographically secure randomness. Some are purpose-built to perform cryptographic computations more efficiently.
 
----
+***
 
 ## Communicating using PKCS#11
 
@@ -44,4 +45,4 @@ Also, the following cloud HSM offerings have been tested with Keyless SSL:
 - [Azure Managed HSM](/ssl/keyless-ssl/hardware-security-modules/azure-managed-hsm/)
 - [Fortanix DSM](/ssl/keyless-ssl/hardware-security-modules/fortanix-dsm/)
 - [IBM Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/ibm-cloud-hsm/)
-- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
+- [Google Cloud HSM](/ssl/keyless-ssl/hardware-security-modules/google-cloud-hsm/)
\ No newline at end of file
diff --git a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
index f2176ee72e743cd..459196f2dd78e7d 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/high-availability.mdx
@@ -6,6 +6,7 @@ products:
 title: High availability
 sidebar:
   order: 3
+
 ---
 
 The Cloudflare Keyless SSL server runs as a single binary with minimal dependencies and is designed to be robust and reliable. However, the network between your key server and Cloudflare may not be, which could prevent new TLS connections.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/index.mdx b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
index 78c6fba61f6ed5e..4c22ae751c29b2c 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/index.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Reference — Keyless SSL
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more information on Keyless SSL, refer to the following resources:
 
diff --git a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
index b0c023f66fe907a..08105e84ad0afe6 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/keyless-delegation.mdx
@@ -8,6 +8,7 @@ tags:
   - TLS
 sidebar:
   order: 7
+
 ---
 
 Keyless Delegation is Cloudflare's implementation of the emerging delegated credentials standard ([RFC 9345](https://www.rfc-editor.org/rfc/rfc9345.html)). When you upload a certificate for use with Keyless that has the special extension permitting the use of delegated credentials, Cloudflare will automatically produce a delegated credential and use it at the edge with clients that support this feature. The handshakes will complete without the extra latency induced by reaching back to the Keyless Server, and there are [additional advantages to flexibility in algorithm choice](https://blog.cloudflare.com/keyless-delegation/).
diff --git a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
index 292a3c66bcec5c5..0e9d1a59aa73910 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/metrics.mdx
@@ -6,10 +6,13 @@ products:
 title: Key server metrics
 sidebar:
   order: 5
+
 ---
 
 The gokeyless key server exposes a [Prometheus](https://prometheus.io/) metrics endpoint that you can use to monitor signing performance, error rates, connection health, and certificate expiry. This endpoint can also be scraped by the OpenTelemetry Collector Prometheus receiver, making the metrics available to any OpenTelemetry-compatible backend.
 
+
+
 ## Metrics endpoint
 
 By default, metrics are served at:
@@ -28,24 +31,24 @@ The endpoint serves only `/metrics`. There are no additional HTTP endpoints such
 
 All histogram metrics share the same bucket configuration: 15 exponential buckets starting at 100 microseconds, doubling each step up to approximately 1.64 seconds, plus a final `+Inf` bucket.
 
-| Bucket | Upper bound            |
-| ------ | ---------------------- |
-| 1      | 100 µs                 |
-| 2      | 200 µs                 |
-| 3      | 400 µs                 |
-| 4      | 800 µs                 |
-| 5      | 1.6 ms                 |
-| 6      | 3.2 ms                 |
-| 7      | 6.4 ms                 |
-| 8      | 12.8 ms                |
-| 9      | 25.6 ms                |
-| 10     | 51.2 ms                |
-| 11     | 102 ms                 |
-| 12     | 205 ms                 |
-| 13     | 410 ms                 |
-| 14     | 819 ms                 |
-| 15     | ~1.64 s                |
-| +Inf   | Anything above ~1.64 s |
+| Bucket | Upper bound |
+| --- | --- |
+| 1 | 100 µs |
+| 2 | 200 µs |
+| 3 | 400 µs |
+| 4 | 800 µs |
+| 5 | 1.6 ms |
+| 6 | 3.2 ms |
+| 7 | 6.4 ms |
+| 8 | 12.8 ms |
+| 9 | 25.6 ms |
+| 10 | 51.2 ms |
+| 11 | 102 ms |
+| 12 | 205 ms |
+| 13 | 410 ms |
+| 14 | 819 ms |
+| 15 | ~1.64 s |
+| +Inf | Anything above ~1.64 s |
 
 :::note
 When using a hardware security module (HSM) with a PKCS#11 session pool, the pool wait timeout is hardcoded at 10 seconds. A pool exhaustion event will therefore always appear in the `+Inf` bucket. Spikes in `+Inf` observations on signing operations with `error="cryptography error"` are a direct indicator of PKCS#11 session pool saturation.
@@ -66,45 +69,45 @@ The `opcode` label uses the full constant name from the gokeyless protocol.
 
 #### RSA operations
 
-| `opcode` label       | Wire value | Description                                                                   |
-| -------------------- | ---------- | ----------------------------------------------------------------------------- |
-| `OpRSADecrypt`       | `0x01`     | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3)     |
-| `OpRSASignMD5SHA1`   | `0x02`     | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
-| `OpRSASignSHA1`      | `0x03`     | RSA PKCS#1 v1.5 signature over SHA1                                           |
-| `OpRSASignSHA224`    | `0x04`     | RSA PKCS#1 v1.5 signature over SHA224                                         |
-| `OpRSASignSHA256`    | `0x05`     | RSA PKCS#1 v1.5 signature over SHA256                                         |
-| `OpRSASignSHA384`    | `0x06`     | RSA PKCS#1 v1.5 signature over SHA384                                         |
-| `OpRSASignSHA512`    | `0x07`     | RSA PKCS#1 v1.5 signature over SHA512                                         |
-| `OpRSAPSSSignSHA256` | `0x35`     | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3           |
-| `OpRSAPSSSignSHA384` | `0x36`     | RSASSA-PSS signature over SHA384                                              |
-| `OpRSAPSSSignSHA512` | `0x37`     | RSASSA-PSS signature over SHA512                                              |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpRSADecrypt` | `0x01` | RSA raw decryption — used in TLS RSA key exchange (deprecated in TLS 1.3) |
+| `OpRSASignMD5SHA1` | `0x02` | RSA PKCS#1 v1.5 signature over MD5+SHA1 combined hash — TLS 1.0/1.1 handshake |
+| `OpRSASignSHA1` | `0x03` | RSA PKCS#1 v1.5 signature over SHA1 |
+| `OpRSASignSHA224` | `0x04` | RSA PKCS#1 v1.5 signature over SHA224 |
+| `OpRSASignSHA256` | `0x05` | RSA PKCS#1 v1.5 signature over SHA256 |
+| `OpRSASignSHA384` | `0x06` | RSA PKCS#1 v1.5 signature over SHA384 |
+| `OpRSASignSHA512` | `0x07` | RSA PKCS#1 v1.5 signature over SHA512 |
+| `OpRSAPSSSignSHA256` | `0x35` | RSASSA-PSS signature over SHA256 — primary RSA operation in TLS 1.3 |
+| `OpRSAPSSSignSHA384` | `0x36` | RSASSA-PSS signature over SHA384 |
+| `OpRSAPSSSignSHA512` | `0x37` | RSASSA-PSS signature over SHA512 |
 
 #### ECDSA operations
 
-| `opcode` label       | Wire value | Description                                                      |
-| -------------------- | ---------- | ---------------------------------------------------------------- |
-| `OpECDSASignMD5SHA1` | `0x12`     | ECDSA signature over MD5+SHA1 combined hash                      |
-| `OpECDSASignSHA1`    | `0x13`     | ECDSA signature over SHA1                                        |
-| `OpECDSASignSHA224`  | `0x14`     | ECDSA signature over SHA224                                      |
-| `OpECDSASignSHA256`  | `0x15`     | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
-| `OpECDSASignSHA384`  | `0x16`     | ECDSA signature over SHA384                                      |
-| `OpECDSASignSHA512`  | `0x17`     | ECDSA signature over SHA512                                      |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpECDSASignMD5SHA1` | `0x12` | ECDSA signature over MD5+SHA1 combined hash |
+| `OpECDSASignSHA1` | `0x13` | ECDSA signature over SHA1 |
+| `OpECDSASignSHA224` | `0x14` | ECDSA signature over SHA224 |
+| `OpECDSASignSHA256` | `0x15` | ECDSA signature over SHA256 — most common in TLS 1.2 and TLS 1.3 |
+| `OpECDSASignSHA384` | `0x16` | ECDSA signature over SHA384 |
+| `OpECDSASignSHA512` | `0x17` | ECDSA signature over SHA512 |
 
 #### Other signing
 
-| `opcode` label  | Wire value | Description                                                                  |
-| --------------- | ---------- | ---------------------------------------------------------------------------- |
-| `OpEd25519Sign` | `0x18`     | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpEd25519Sign` | `0x18` | Ed25519 signature over an arbitrary-length payload (not a pre-hashed digest) |
 
 #### Sealing and infrastructure operations
 
-| `opcode` label | Wire value | Description                                                                                           |
-| -------------- | ---------- | ----------------------------------------------------------------------------------------------------- |
-| `OpSeal`       | `0x21`     | Encrypt a blob using the server's sealing key — used for TLS session tickets                          |
-| `OpUnseal`     | `0x22`     | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated  |
-| `OpRPC`        | `0x23`     | Execute a named function registered on the server. Available to all connection types                  |
-| `OpCustom`     | `0x24`     | Execute a custom function set in the server configuration. Available to unrestricted connections only |
-| `OpPing`       | `0xF1`     | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved      |
+| `opcode` label | Wire value | Description |
+| --- | --- | --- |
+| `OpSeal` | `0x21` | Encrypt a blob using the server's sealing key — used for TLS session tickets |
+| `OpUnseal` | `0x22` | Decrypt a blob previously encrypted by `OpSeal`. Returns `ErrExpired` if the sealing key has rotated |
+| `OpRPC` | `0x23` | Execute a named function registered on the server. Available to all connection types |
+| `OpCustom` | `0x24` | Execute a custom function set in the server configuration. Available to unrestricted connections only |
+| `OpPing` | `0xF1` | Health check — the server echoes the payload back as `OpPong` with no HSM or key lookup involved |
 
 ---
 
@@ -121,15 +124,15 @@ This metric does not include time a request spends waiting for a connection sema
 
 Opcodes are grouped into coarser categories for this label:
 
-| `type` label | Opcodes included                                                  |
-| ------------ | ----------------------------------------------------------------- |
-| `rsa`        | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*`             |
-| `ecdsa`      | All `OpECDSASign*`                                                |
-| `ed25519`    | `OpEd25519Sign`                                                   |
-| `rpc`        | `OpRPC`                                                           |
-| `custom`     | `OpCustom`                                                        |
-| `other`      | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
-| `unknown`    | Any unrecognised opcode byte                                      |
+| `type` label | Opcodes included |
+| --- | --- |
+| `rsa` | `OpRSADecrypt`, all `OpRSASign*`, all `OpRSAPSSSign*` |
+| `ecdsa` | All `OpECDSASign*` |
+| `ed25519` | `OpEd25519Sign` |
+| `rpc` | `OpRPC` |
+| `custom` | `OpCustom` |
+| `other` | `OpSeal`, `OpUnseal`, `OpPing`, `OpPong`, `OpResponse`, `OpError` |
+| `unknown` | Any unrecognised opcode byte |
 
 :::note
 `OpPing` is grouped into `other` alongside `OpSeal` and `OpUnseal`. Ping round-trip latency cannot be separated from seal and unseal operation latency in this metric.
@@ -139,20 +142,20 @@ Opcodes are grouped into coarser categories for this label:
 
 For successful requests the value is `no error`. All other values indicate a failed operation.
 
-| `error` label                                       | Description                             | Common cause                                                                                          |
-| --------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| `no error`                                          | Operation completed successfully        | —                                                                                                     |
-| `cryptography error`                                | HSM or signing operation failed         | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
-| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result           | Key not loaded in keystore, incorrect SKI in request                                                  |
-| `read failure`                                      | I/O read error during the operation     | Disk error reading key file                                                                           |
-| `version mismatch`                                  | Protocol version not supported          | Client and server version skew                                                                        |
-| `bad opcode`                                        | Unknown opcode received                 | `OpCustom` sent with no custom handler configured                                                     |
-| `unexpected opcode`                                 | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request                                         |
-| `malformed message`                                 | TLV parse failure                       | Corrupt or truncated packet                                                                           |
-| `internal error`                                    | Non-cryptographic server-side failure   | Sealer is nil, RPC dispatch error                                                                     |
-| `certificate not found`                             | Certificate lookup failed               | Certificate not loaded                                                                                |
-| `sealing key expired`                               | `OpUnseal` blob is too old to decrypt   | TLS session ticket key rotation — blob sealed with a key that has since been retired                  |
-| `remote configuration error`                        | Remote key server is misconfigured      | Key points to an unreachable or misconfigured remote key server                                       |
+| `error` label | Description | Common cause |
+| --- | --- | --- |
+| `no error` | Operation completed successfully | — |
+| `cryptography error` | HSM or signing operation failed | PKCS#11 session pool exhaustion (`resource pool timed out`), HSM returned an error, key type mismatch |
+| `key not found due to no matching SKI/SNI/ServerIP` | Key lookup returned no result | Key not loaded in keystore, incorrect SKI in request |
+| `read failure` | I/O read error during the operation | Disk error reading key file |
+| `version mismatch` | Protocol version not supported | Client and server version skew |
+| `bad opcode` | Unknown opcode received | `OpCustom` sent with no custom handler configured |
+| `unexpected opcode` | A response opcode was used as a request | Client sent `OpPong`, `OpResponse`, or `OpError` as a request |
+| `malformed message` | TLV parse failure | Corrupt or truncated packet |
+| `internal error` | Non-cryptographic server-side failure | Sealer is nil, RPC dispatch error |
+| `certificate not found` | Certificate lookup failed | Certificate not loaded |
+| `sealing key expired` | `OpUnseal` blob is too old to decrypt | TLS session ticket key rotation — blob sealed with a key that has since been retired |
+| `remote configuration error` | Remote key server is misconfigured | Key points to an unreachable or misconfigured remote key server |
 
 ---
 
@@ -194,16 +197,16 @@ It is **not** recorded for `OpPing`, `OpSeal`, `OpUnseal`, `OpRPC`, or `OpCustom
 
 Counts connection-level transport failures. This metric reflects problems at the network or TLS layer — it does not count signing errors or key lookup failures, which are reported in the `error` label of the duration histograms.
 
-| Scenario                                             | Counted? |
-| ---------------------------------------------------- | -------- |
-| TLS handshake failure                                | No       |
-| Client disconnected before TLS handshake (EOF)       | No       |
-| Failure determining connection trust level after TLS | Yes      |
-| Non-EOF read error on an established connection      | Yes      |
-| Write error when delivering a response               | Yes      |
-| Read timeout — graceful connection drain             | No       |
-| Signing error, including PKCS#11 pool timeout        | No       |
-| Key not found                                        | No       |
+| Scenario | Counted? |
+| --- | --- |
+| TLS handshake failure | No |
+| Client disconnected before TLS handshake (EOF) | No |
+| Failure determining connection trust level after TLS | Yes |
+| Non-EOF read error on an established connection | Yes |
+| Write error when delivering a response | Yes |
+| Read timeout — graceful connection drain | No |
+| Signing error, including PKCS#11 pool timeout | No |
+| Key not found | No |
 
 ---
 
@@ -215,19 +218,18 @@ Counts connection-level transport failures. This metric reflects problems at the
 Reports the expiration time (`NotAfter`) of each certificate loaded by the key server as a Unix timestamp. One time series is emitted per certificate.
 
 This metric is updated:
-
 - At startup, for the server authentication certificate (`auth_cert`) and the Cloudflare CA certificate (`cloudflare_ca_cert`).
 - On each successful inbound TLS connection, for the peer certificates presented by the connecting client.
 
-| Label       | Description                                                                              |
-| ----------- | ---------------------------------------------------------------------------------------- |
-| `source`    | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
-| `serial_no` | Certificate serial number                                                                |
-| `cn`        | Subject Common Name                                                                      |
-| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names                            |
-| `ca`        | `1` if the certificate is a CA certificate, `0` otherwise                                |
-| `server`    | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise                   |
-| `client`    | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise                   |
+| Label | Description |
+| --- | --- |
+| `source` | File path for startup certs; `listener: <addr>` for peer certs from incoming connections |
+| `serial_no` | Certificate serial number |
+| `cn` | Subject Common Name |
+| `hostnames` | Sorted, comma-separated list of DNS Subject Alternative Names |
+| `ca` | `1` if the certificate is a CA certificate, `0` otherwise |
+| `server` | `1` if the certificate includes `ExtKeyUsageServerAuth`, `0` otherwise |
+| `client` | `1` if the certificate includes `ExtKeyUsageClientAuth`, `0` otherwise |
 
 :::note
 `server_utilization` is a registered `GaugeVec` metric that is never written to by the key server. Because no label values are ever set, it emits no time series in the `/metrics` output at all. Do not use it.
diff --git a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
index 4edb4db09bab546..22b7833a2be107e 100644
--- a/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
+++ b/src/content/docs/ssl/keyless-ssl/reference/scaling-and-benchmarking.mdx
@@ -6,6 +6,7 @@ products:
 title: Scaling and benchmarking
 sidebar:
   order: 4
+
 ---
 
 Cloudflare's Keyless SSL technology was designed to scale to accommodate any sized workload using vertical and horizontal scaling, and pre-computation techniques wherever possible, such as ECDSA. The goals of the architectural design of the key server are to minimize latency while maximizing signing operations per second.
@@ -14,7 +15,7 @@ Each key server uses a worker pool model, with incoming client connections handl
 
 Where needed, multiple key servers can be deployed and balanced between using your preferred ingress load balancing configuration. For full high availability, make sure to deploy sufficient key servers to handle twice the expected workload.
 
----
+***
 
 ## Key type
 
@@ -24,7 +25,7 @@ ECDSA signing can be broken down into two steps. Since the first step — genera
 
 Additional details can be found in the [gokeyless server readme file](https://github.com/cloudflare/gokeyless#readme) file.
 
----
+***
 
 ## Benchmarks
 
diff --git a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
index 725673be1dbd8c2..4f8047f3f0bc964 100644
--- a/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
+++ b/src/content/docs/ssl/keyless-ssl/upgrading-your-key-server.mdx
@@ -6,6 +6,7 @@ products:
 title: Upgrade your key server
 sidebar:
   order: 4
+
 ---
 
 Periodically, you may need to update your key server when using Cloudflare's Keyless SSL.
@@ -24,6 +25,8 @@ To upgrade your key server:
 
 :::caution
 
+
 If you are running a [high availability configuration](/ssl/keyless-ssl/reference/high-availability/), upgrade one server at a time as new TLS connections will fail to terminate at Cloudflare's global network without a functioning key server.
 
+
 :::
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
index bda18f6939d8966..c8ca40f070b5e2a 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/global.mdx
@@ -24,9 +24,10 @@ Global, [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/
 - Make sure your zone is using an [SSL/TLS encryption mode](/ssl/origin-configuration/ssl-modes/) of **Full** or higher.
 
 - Consider your security and certificate needs:
-  - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
 
-  - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
+   - The Cloudflare-provided certificate is not exclusive to your account. It only guarantees that a request is coming from the Cloudflare network. If you need stricter security, set up [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) AOP with your own certificate instead.
+
+   - Global AOP is applied to all proxied hostnames on your zone, including [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) configured on a Cloudflare for SaaS zone. If you need a different AOP certificate for different custom hostnames, use [per-hostname AOP](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
 
 ## 1. Download the Cloudflare certificate
 
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
index 5ab7622aa6b0069..d2d6befaa600c0d 100644
--- a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx
@@ -11,8 +11,9 @@ sidebar:
 head:
   - tag: title
     content: Set up Authenticated Origin Pulls
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
index 8a042656568dd34..051fcf061c534ca 100644
--- a/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
+++ b/src/content/docs/ssl/origin-configuration/cipher-suites.mdx
@@ -28,19 +28,19 @@ The list order is based on how the cipher suites appear in the [ClientHello](htt
 
 | Cipher name                        | TLS 1.0 | TLS 1.1 | TLS 1.2 | TLS 1.3 |
 | ---------------------------------- | ------- | ------- | ------- | ------- |
-| AEAD-AES128-GCM-SHA256 [^1]        | ❌      | ❌      | ❌      | ✅      |
-| AEAD-AES256-GCM-SHA384 [^1]        | ❌      | ❌      | ❌      | ✅      |
-| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌      | ❌      | ❌      | ✅      |
-| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES128-GCM-SHA256        | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES128-SHA               | ✅      | ✅      | ✅      | ❌      |
-| AES128-GCM-SHA256                  | ❌      | ❌      | ✅      | ❌      |
-| AES128-SHA                         | ✅      | ✅      | ✅      | ❌      |
-| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES256-GCM-SHA384        | ❌      | ❌      | ✅      | ❌      |
-| ECDHE-RSA-AES256-SHA384            | ❌      | ❌      | ✅      | ❌      |
-| AES256-SHA                         | ✅      | ✅      | ✅      | ❌      |
-| DES-CBC3-SHA                       | ✅      | ❌      | ❌      | ❌      |
+| AEAD-AES128-GCM-SHA256 [^1]        | ❌       | ❌       | ❌       | ✅       |
+| AEAD-AES256-GCM-SHA384 [^1]        | ❌       | ❌       | ❌       | ✅       |
+| AEAD-CHACHA20-POLY1305-SHA256 [^1] | ❌       | ❌       | ❌       | ✅       |
+| ECDHE-ECDSA-AES128-GCM-SHA256      | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES128-GCM-SHA256        | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES128-SHA               | ✅       | ✅       | ✅       | ❌       |
+| AES128-GCM-SHA256                  | ❌       | ❌       | ✅       | ❌       |
+| AES128-SHA                         | ✅       | ✅       | ✅       | ❌       |
+| ECDHE-ECDSA-AES256-GCM-SHA384      | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES256-GCM-SHA384        | ❌       | ❌       | ✅       | ❌       |
+| ECDHE-RSA-AES256-SHA384            | ❌       | ❌       | ✅       | ❌       |
+| AES256-SHA                         | ✅       | ✅       | ✅       | ❌       |
+| DES-CBC3-SHA                       | ✅       | ❌       | ❌       | ❌       |
 
 ### TLS 1.3 cipher suites
 
@@ -67,4 +67,4 @@ ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RS
 ssl_prefer_server_ciphers on;
 ```
 
-[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
+[^1]: Refer to [TLS 1.3 cipher suites](#tls-13-cipher-suites) for details.
\ No newline at end of file
diff --git a/src/content/docs/ssl/origin-configuration/index.mdx b/src/content/docs/ssl/origin-configuration/index.mdx
index ca68ac364da293b..aac15f2f4132e15 100644
--- a/src/content/docs/ssl/origin-configuration/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn more about SSL/TLS protection options for your origin servers:
 
diff --git a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
index 6669b3202cadc81..b417523729d50b6 100644
--- a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
+++ b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx
@@ -64,7 +64,7 @@ If the user does not have **API Access**, this error is returned.
 
 Make sure that the user creating the certificate has access to the API. You can check in the account **Members** page.
 
-<DashButton url="/?to=/:account/members" />
+   <DashButton url="/?to=/:account/members" />
 
 - The default setting for the account is specified in the card **Enable API Access**.
 - Specific user API Access (which can override the default setting) is presented after selecting the user in the list of members.
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
index c19aaa19e4e96d1..087e14efa75240d 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
@@ -16,9 +16,9 @@ import { Stream, Render, TabItem, Tabs } from "~/components";
 When you set your encryption mode to **Full**, Cloudflare allows HTTPS connections between your visitor and Cloudflare and makes connections to the origin using the scheme requested by the visitor. If your visitor uses `http`, then Cloudflare connects to the origin using plaintext HTTP and vice versa.
 
 <Stream
-	id="a1e79096a2b042e0525a8543c232279a"
-	title="Configure Full encryption mode"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
+  id="a1e79096a2b042e0525a8543c232279a"
+  title="Configure Full encryption mode"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/c0c41f09-2d73-4ee5-8b71-dbb271ed1800/public"
 />
 
 ## Use when
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
index ffbf39cb4685b3c..d914207fd292d04 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
@@ -45,7 +45,7 @@ Automatic SSL/TLS leverages advanced methods developed by the SSL/TLS Recommende
 Automatic SSL/TLS will not change your setting to a less secure encryption mode. For example, if your origin certificate expires, the encryption mode will not change from **Full (strict)** to **Full**. You must ensure the validity of your origin SSL/TLS configuration at all times.
 :::
 
-Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode. If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
+Automatic upgrades are applied gradually. Automatic SSL/TLS begins to upgrade the domain by starting with just 1% of its traffic. If no issues are found, the new SSL/TLS encryption mode is applied to traffic in 10% increments until 100% of traffic uses the recommended mode.  If origin connectivity fails during this process, Cloudflare aborts the upgrade, immediately rolls traffic back to the previous mode, and logs the failure. Once 100% of traffic has been successfully upgraded with no TLS-related errors, the domain's SSL/TLS setting is permanently updated.
 
 Flexible → Full/Strict transitions are handled with extra caution since the origin scheme change (HTTP → HTTPS) alters cache keys. In this case, the ramp-up may proceed more slowly to allow cache warm-up before resuming standard increments.
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
index 44f4f531ad50fd4..60489481ea636f2 100644
--- a/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
+++ b/src/content/docs/ssl/origin-configuration/ssl-modes/ssl-only-origin-pull.mdx
@@ -23,11 +23,12 @@ When you set your encryption mode to **Strict (SSL-Only Origin Pull)**, connecti
 The certificate presented by the origin will be validated the same as with [Full (strict) mode](/ssl/origin-configuration/ssl-modes/full-strict/).
 
 <Stream
-	id="f407072cb5b4837c8c3a58a69cde90b5"
-	title="Configure Strict encryption mode"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
+  id="f407072cb5b4837c8c3a58a69cde90b5"
+  title="Configure Strict encryption mode"
+  thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/28f00d39-6aee-4a42-c688-e37021bcb000/public"
 />
 
+
 ## Use when
 
 You want the most secure configuration available for your origin, you are an Enterprise customer, and you meet the requirements for [**Full (strict)** mode](/ssl/origin-configuration/ssl-modes/full-strict/).
diff --git a/src/content/docs/ssl/reference/all-features.mdx b/src/content/docs/ssl/reference/all-features.mdx
index e4526a1b070534c..83243c2d35356e9 100644
--- a/src/content/docs/ssl/reference/all-features.mdx
+++ b/src/content/docs/ssl/reference/all-features.mdx
@@ -7,12 +7,13 @@ sidebar:
   order: 9
 head: []
 description: Review information on all Cloudflare SSL/TLS features and their availability.
+
 ---
 
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
 Cloudflare provides the following features for different [plans](https://www.cloudflare.com/plans/).
 
 ## Features
 
-<ProductFeatures id="ssl" />
+<ProductFeatures id="ssl" />
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/browser-compatibility.mdx b/src/content/docs/ssl/reference/browser-compatibility.mdx
index 964b497ae00d5c6..a7af16592d73bd7 100644
--- a/src/content/docs/ssl/reference/browser-compatibility.mdx
+++ b/src/content/docs/ssl/reference/browser-compatibility.mdx
@@ -8,6 +8,7 @@ sidebar:
 head: []
 description: Review information about browser compatibility for the different
   Cloudflare SSL/TLS offerings.
+
 ---
 
 Cloudflare attempts to provide compatibility for as wide a range of user agents (browsers, API clients, etc.) as possible. However, the specific set of supported clients can vary depending on the different SSL/TLS certificate types, your visitor's [browser version](#non-sni-support), and the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that issues the certificate.
@@ -30,13 +31,13 @@ Although [SNI extensions](https://www.cloudflare.com/learning/ssl/what-is-sni/)
 
 To support non-SNI requests, you can:
 
-- [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
+* [Upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate) and specify a value of `Legacy` for its client support.
 
   Note that `Legacy` custom certificates are not compatible with [BYOIP](/byoip/) and that, unlike [Universal SSL](/ssl/edge-certificates/universal-ssl/) or [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/), Cloudflare does not manage issuance and renewal for [custom certificates](/ssl/edge-certificates/custom-certificates/).
 
-- (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
+* (BYOIP customers only) Enterprise customers can choose to bring their own IP prefix to the Cloudflare network and [specify the default SNI used for any non-SNI handshake in the address map](/byoip/address-maps/setup/#non-sni-support).
 
-- (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
+* (Paid plans only) [Contact Cloudflare Support](/support/contacting-cloudflare-support/) and request a set of non-SNI IPs for your zone.
 
 ## HTTPS records
 
@@ -54,4 +55,4 @@ If you need HTTPS records without Universal SSL, you can manually add them, but
 
 Cloudflare's OCSP implementation uses HTTP/1.1 by default for plain HTTP connections.
 
-For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
+For HTTPS connections, the client automatically attempts to use HTTP/2 if the server supports it through the TLS ALPN (Application-Layer Protocol Negotiation) extension. If HTTP/2 is not available or supported by the server, it will fall back to HTTP/1.1.
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
index 455857836c90c94..2c27bca6871ec0e 100644
--- a/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
+++ b/src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx
@@ -7,13 +7,14 @@ sidebar:
   order: 4
 head: []
 description: Learn about how Cloudflare decides which certificate and associated SSL/TLS settings to apply to individual hostnames.
+
 ---
 
 import { GlossaryTooltip } from "~/components";
 
 When a new certificate is created, Cloudflare first deploys the certificate and then serves it.
 
----
+***
 
 ## Certificate deployment
 
@@ -41,17 +42,17 @@ For any given hostname, Cloudflare uses the following order to determine which c
 In this case, when the certificate with the closest expiration date is renewed, it will then become the one with the latest expiration date and get presented.
 :::
 
----
+***
 
 ## Certificate presentation
 
 Cloudflare uses the following order to determine the certificate and settings used during a TLS handshake:
 
-1. **SNI match**: Certificates and settings that match the SNI hostname _exactly_ take precedence.
+1. **SNI match**: Certificates and settings that match the SNI hostname *exactly* take precedence.
 2. **SNI wildcard match**: If there is not an exact match between the hostname and SNI hostname, Cloudflare uses certificates and settings that match an SNI wildcard.
 3. **IP address**: If no SNI is presented, Cloudflare uses certificate based on the IP address (the hostname can support TLS handshakes made without SNI).
 
----
+***
 
 ## Hostname priority
 
@@ -60,11 +61,13 @@ When multiple <GlossaryTooltip term="proxy status">proxied DNS records</Glossary
 Cloudflare determines this priority in the following order, assuming each record exists and is proxied (orange-clouded):
 
 1. **Exact hostname match**:
+
    1. [New custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) (belonging to a SaaS provider)
    2. [Legacy custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning/) (belonging to a SaaS provider)
    3. [DNS](/dns/proxy-status/) (belonging to the logical DNS zone)
 
 2. **Wildcard hostname match**:
+
    1. DNS (belonging to the logical DNS zone)
    2. New custom hostname (belonging to a SaaS provider)
 
@@ -76,9 +79,9 @@ If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudf
 
 Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`. Customer2 is a SaaS provider that creates and successfully [verifies the new custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/) `shop.example.com`. Afterward, traffic starts routing over Customer2's zone:
 
-- If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
-- If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
-- If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
+* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
+* If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
+* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
 
 #### Scenario 2
 
diff --git a/src/content/docs/ssl/reference/certificate-authorities.mdx b/src/content/docs/ssl/reference/certificate-authorities.mdx
index 07206f1e5b03d00..0acd5bbcd68336c 100644
--- a/src/content/docs/ssl/reference/certificate-authorities.mdx
+++ b/src/content/docs/ssl/reference/certificate-authorities.mdx
@@ -137,4 +137,4 @@ The following table lists the CAA record content for each CA:
 | SSL.com               | `ssl.com`                            |
 | Sectigo               | `sectigo.com`                        |
 
-[^1]: A payment gateway used with some ecommerce plugins.
+[^1]: A payment gateway used with some ecommerce plugins.
\ No newline at end of file
diff --git a/src/content/docs/ssl/reference/certificate-pinning.mdx b/src/content/docs/ssl/reference/certificate-pinning.mdx
index 0c8cf4aa06ead76..ab7622846e0f1d2 100644
--- a/src/content/docs/ssl/reference/certificate-pinning.mdx
+++ b/src/content/docs/ssl/reference/certificate-pinning.mdx
@@ -7,6 +7,7 @@ sidebar:
   order: 8
 head: []
 description: Learn why Cloudflare does not support HTTP public key pinning (HPKP) and consider an alternative solution to prevent certificate misissuance.
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
index 0886b9f6b8540b5..bf7f12feedcf976 100644
--- a/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
+++ b/src/content/docs/ssl/reference/cloudflare-and-cve-2019-1559.mdx
@@ -5,6 +5,7 @@ products:
   - ssl
 source: https://support.cloudflare.com/hc/en-us/articles/4422920018317-Cloudflare-and-CVE-2019-1559
 title: Cloudflare and CVE-2019-1559
+
 ---
 
 The [GOLDENDOODLE and Zombie POODLE attacks](https://www.tripwire.com/state-of-security/vulnerability-management/zombie-poodle-goldendoodle/) affect applications that use certain cipher suites associated with TLS 1.2.
@@ -19,6 +20,6 @@ Even though your application is not vulnerable to CVE-2019-1559, some security s
 
 To remove these warnings, refer to [Customize cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) and exclude the following ciphers:
 
-- `ECDHE-ECDSA-AES256-SHA384`
-- `ECDHE-ECDSA-AES128-SHA256`
-- `ECDHE-RSA-AES256-SHA384`
+* `ECDHE-ECDSA-AES256-SHA384`
+* `ECDHE-ECDSA-AES128-SHA256`
+* `ECDHE-RSA-AES256-SHA384`
diff --git a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
index d90f31506bc85cd..c2b34ec0ba65fc4 100644
--- a/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
+++ b/src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx
@@ -34,31 +34,31 @@ Refer to [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum
 
 There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:
 
-- Header compression in TLS
-- Header compression in SPDY 3.1
-- RC4
-- SSL 3.0
-- Renegotiation with clients
-- DHE ciphersuites
-- Export-grade ciphers
+* Header compression in TLS
+* Header compression in SPDY 3.1
+* RC4
+* SSL 3.0
+* Renegotiation with clients
+* DHE ciphersuites
+* Export-grade ciphers
 
 Cloudflare mitigations protect against several attacks:
 
-- CRIME
-- BREACH
-- POODLE
-- RC4 Cryptographic Weaknesses
-- SSL Renegotiation Attack
-- Protocol Downgrade Attacks
-- FREAK
-- LogJam
-- 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
+* CRIME
+* BREACH
+* POODLE
+* RC4 Cryptographic Weaknesses
+* SSL Renegotiation Attack
+* Protocol Downgrade Attacks
+* FREAK
+* LogJam
+* 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
 
 Cloudflare provides additional mitigations for:
 
-- Heartbleed
-- Lucky Thirteen
-- CCS injection vulnerability
+* Heartbleed
+* Lucky Thirteen
+* CCS injection vulnerability
 
 Cloudflare has patched all servers against these vulnerabilities. Also, the [Cloudflare Web Application Firewall](/waf/) has managed rules that mitigate several of these vulnerabilities including Heartbleed and ShellShock.
 
@@ -70,5 +70,5 @@ Security scans that note the presence of ROBOT while on Cloudflare are a false p
 
 A vulnerability in the use of the Triple DES (3DES) encryption algorithm in the Transport Layer Security (TLS) protocol. Sweet32 is currently a proof of concept attack, there are no known examples of this in the wild. Cloudflare has manually mitigated the vulnerability for TLS 1.0 in the following manner:
 
-- The attacker must collect 32GB of data from a single TLS session.
-- Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
+* The attacker must collect 32GB of data from a single TLS session.
+* Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected.
diff --git a/src/content/docs/ssl/reference/index.mdx b/src/content/docs/ssl/reference/index.mdx
index 09459738c3be6af..cdb3e27983cc833 100644
--- a/src/content/docs/ssl/reference/index.mdx
+++ b/src/content/docs/ssl/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 For more on Cloudflare SSL/TLS, refer to these articles:
 
diff --git a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
index dac25cb8479e6f3..99bfb37d1c5d06d 100644
--- a/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/entrust-distrust.mdx
@@ -34,13 +34,14 @@ This means that Entrust certificates will be issued using SSL.com roots.
 
 Since Cloudflare also [partners with SSL.com](/ssl/reference/certificate-authorities/), you can switch from uploading custom certificates to using Cloudflare-managed certificates. This change brings the following advantages:
 
-- Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
-- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
-- Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
-- If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
+* Use [Advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) to have more control and flexibility while also benefitting from automatic renewals.
+* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) to automatically issue certificates for your [proxied hostnames](/dns/proxy-status/).
+* Use [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to reduce manual intervention when renewing certificates for [partial (CNAME) setup](/dns/zone-setups/partial-setup/) zones.
+* If you are a SaaS provider, extend the benefits of automatic renewals to your customers by specifying SSL.com as the certificate authority when [creating](/api/resources/custom_hostnames/methods/create/) or [editing](/api/resources/custom_hostnames/methods/edit/) your custom hostnames (API only).
 
 ## More resources
 
-- [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
-- [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
-- [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
+* [Use Cloudflare with SSL.com certificates](/ssl/reference/certificate-authorities/)
+* [Google Security Blog](https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html)
+* [Entrust TLS Certificate Information Center](https://www.entrust.com/tls-certificate-information-center)
+
diff --git a/src/content/docs/ssl/reference/migration-guides/index.mdx b/src/content/docs/ssl/reference/migration-guides/index.mdx
index a2d9c7e09c8f5eb..c7d41fe832e31ba 100644
--- a/src/content/docs/ssl/reference/migration-guides/index.mdx
+++ b/src/content/docs/ssl/reference/migration-guides/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 6
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 These guides walk you through the migration processes associated with various changes in Cloudflare's SSL/TLS infrastructure.
 
diff --git a/src/content/docs/ssl/reference/protocols.mdx b/src/content/docs/ssl/reference/protocols.mdx
index 5fc1e33f6ac60f0..4431c3f94d47833 100644
--- a/src/content/docs/ssl/reference/protocols.mdx
+++ b/src/content/docs/ssl/reference/protocols.mdx
@@ -13,10 +13,10 @@ tags:
 
 Cloudflare supports the following TLS protocols:
 
-- TLS 1.0
-- TLS 1.1
-- TLS 1.2
-- TLS 1.3
+* TLS 1.0
+* TLS 1.1
+* TLS 1.2
+* TLS 1.3
 
 TLS 1.0 is the [version that Cloudflare sets by default](/ssl/edge-certificates/additional-options/minimum-tls/) for all customers using certificate-based encryption.
 
@@ -42,12 +42,12 @@ TLS 1.3 has become widely adopted. As a general rule, Cloudflare recommends sett
 
 However, not all browser versions support TLS 1.2 and above. Depending on your particular business situation, this may present some limitations in using stronger encryption standards:
 
-- Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
+* Consider using TLS 1.0 or 1.1 for sites with a broad user base, particularly non-transactional sites. In this way, you minimize the possibility that some clients cannot connect to your site securely.
 
-- For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
+* For a narrow user base and sites that run internal applications or business and productivity applications, Cloudflare recommends TLS 1.2. These sites might already have more stringent security requirements or might be subject to [PCI compliance](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/). You also need to ensure that your users upgrade to a TLS 1.2 compliant browser.
 
 ## Related resources
 
-- [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
-- [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
-- [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
+* [PCI compliance and vulnerabilities mitigation](/ssl/reference/compliance-and-vulnerabilities/)
+* [Transport Layer Security](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/)
+* [PCI Security Standards Council](https://www.pcisecuritystandards.org/)
diff --git a/src/content/docs/ssl/saas.mdx b/src/content/docs/ssl/saas.mdx
index fcce7104fc2969a..3e85a7dff75970e 100644
--- a/src/content/docs/ssl/saas.mdx
+++ b/src/content/docs/ssl/saas.mdx
@@ -7,4 +7,5 @@ title: Cloudflare for SaaS
 external_link: /cloudflare-for-platforms/cloudflare-for-saas/
 sidebar:
   order: 7
+
 ---
diff --git a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
index 3061e3715c16c1c..e7e9028c7ed7c8e 100644
--- a/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/general-ssl-errors.mdx
@@ -171,4 +171,4 @@ When clicking `Approve Certificate` on a Certificate Approval renewal email, you
 
 ### Resolution
 
-Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
+Check the status of the certificate on the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/:zone/ssl-tls). If the status is `Active`, you can disregard this email and the error message.
\ No newline at end of file
diff --git a/src/content/docs/ssl/troubleshooting/index.mdx b/src/content/docs/ssl/troubleshooting/index.mdx
index d6196df82ab4540..098ba6ffb1eb8d0 100644
--- a/src/content/docs/ssl/troubleshooting/index.mdx
+++ b/src/content/docs/ssl/troubleshooting/index.mdx
@@ -10,15 +10,11 @@ sidebar:
 head:
   - tag: title
     content: Troubleshooting
+
 ---
 
-import { ResourcesBySelector } from "~/components";
+import { ResourcesBySelector } from "~/components"
 
 For FAQs and other troubleshooting information, refer to the following resources:
 
-<ResourcesBySelector
-	directory="ssl"
-	types={["faq", "troubleshooting"]}
-	filterables={["pcx_content_type"]}
-	showDescriptions={false}
-/>
+<ResourcesBySelector directory="ssl" types={["faq", "troubleshooting"]} filterables={["pcx_content_type"]} showDescriptions={false} />
diff --git a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
index 8499af2e2c86769..5b2b86f88806a9d 100644
--- a/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
+++ b/src/content/docs/ssl/troubleshooting/mixed-content-errors.mdx
@@ -10,6 +10,7 @@ sidebar:
 learning_center:
   title: What is mixed content?
   link: https://www.cloudflare.com/learning/ssl/what-is-mixed-content/
+
 ---
 
 Domains added to Cloudflare receive SSL certificates and can serve traffic over HTTPS. However, after starting to use Cloudflare, some customers notice missing content or page rendering issues when they first serve HTTPS traffic.
@@ -20,7 +21,7 @@ Normally, if your website loads all resources securely over HTTPS, visitors obse
 
 This indicates your site has a working SSL certificate and all resources loaded by the site are loaded over HTTPS. The green lock assures visitors that their connection is safe. One of the [symptoms of mixed content](#symptoms-of-mixed-content-occurrence) is that different icons appear instead of the green lock icon.
 
----
+***
 
 ## Symptoms of mixed content occurrence
 
@@ -30,8 +31,8 @@ Most modern browsers block HTTP requests on secure HTTPS pages. Blocked content
 
 Each web browser uses different methods to warn visitors about mixed content on a website, potentially including:
 
-- A yellow triangle or information symbol beside the URL bar
-- Messages mentioning "secure content"
+* A yellow triangle or information symbol beside the URL bar
+* Messages mentioning "secure content"
 
 ### **Console logs**
 
@@ -45,7 +46,7 @@ For mixed content errors, the browser refuses to load the resources over an inse
 
 Information on using the browser’s debug tools to locate these issues are found in the documentation for [Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content) and [Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content). Alternatively, you can view your page source and find specific references of *http\://* for paths to other resources.
 
----
+***
 
 ## Resolution
 
@@ -59,12 +60,12 @@ There are two methods to resolve mixed content errors.
 
 ### WordPress users
 
-Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the _Automatic HTTPS rewrites_ option within the plugin.
+Cloudflare recommends WordPress users to install the [Cloudflare WordPress plugin](https://wordpress.org/plugins/cloudflare/) and enable the *Automatic HTTPS rewrites* option within the plugin.
 
----
+***
 
 ## Related resources
 
-- [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
-- [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
-- [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
+* [Debugging mixed content in Chrome](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content)
+* [Debugging mixed content in Firefox](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)
+* [Community Tip - Fixing mixed content errors](https://community.cloudflare.com/t/community-tip-fixing-mixed-content-errors/42476)
diff --git a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
index 759b5d1a646ae8d..3ffbddefe30f522 100644
--- a/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
+++ b/src/content/docs/ssl/troubleshooting/version-cipher-mismatch.mdx
@@ -14,11 +14,7 @@ description: Learn how to troubleshoot ERR_SSL_VERSION_OR_CIPHER_MISMATCH when
 
 import { Stream, Render } from "~/components";
 
-<Stream
-	id="03e51d8a6f9a15e16969b8cc117d9225"
-	title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
-	thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public"
-/>
+<Stream id="03e51d8a6f9a15e16969b8cc117d9225" title="ERR_SSL_VERSION_OR_CIPHER_MISMATCH" thumbnail="https://imagedelivery.net/xDOJvHcv1KwTQn6S-BGFIw/5183edaa-5d65-4344-adda-37f2cbe69c00/public" />
 
 After you [add a new domain](/fundamentals/manage-domains/add-site/) to Cloudflare, your visitors' browsers might display one of the following errors:
 
diff --git a/src/content/docs/stream/edit-videos/adding-captions.mdx b/src/content/docs/stream/edit-videos/adding-captions.mdx
index 1cadfef74b3cd32..a5d5afcbca787ae 100644
--- a/src/content/docs/stream/edit-videos/adding-captions.mdx
+++ b/src/content/docs/stream/edit-videos/adding-captions.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 5
 products:
   - stream
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -148,15 +149,15 @@ Example response:
 
 ```json
 {
-	"result": {
-		"language": "en",
-		"label": "English (auto-generated)",
-		"generated": true,
-		"status": "inprogress"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "language": "en",
+    "label": "English (auto-generated)",
+    "generated": true,
+    "status": "inprogress"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -252,15 +253,15 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-	"result": {
-		"language": "en",
-		"label": "English",
-		"generated": false,
-		"status": "ready"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "language": "en",
+    "label": "English",
+    "generated": false,
+    "status": "ready"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -338,23 +339,23 @@ See the full [Workers Stream binding API reference](/stream/manage-video-library
 
 ```json
 {
-	"result": [
-		{
-			"language": "en",
-			"label": "English (auto-generated)",
-			"generated": true,
-			"status": "inprogress"
-		},
-		{
-			"language": "de",
-			"label": "Deutsch",
-			"generated": false,
-			"status": "ready"
-		}
-	],
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": [
+    {
+      "language": "en",
+      "label": "English (auto-generated)",
+      "generated": true,
+      "status": "inprogress"
+    },
+    {
+      "language": "de",
+      "label": "Deutsch",
+      "generated": false,
+      "status": "ready"
+    }
+  ],
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
@@ -370,7 +371,7 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/<VIDEO_UID>/ca
 
 ### Example response to get the caption file for a video
 
-```text
+``` text
 WEBVTT
 
 1
@@ -457,25 +458,25 @@ deleted.
 
 ```json
 {
-	"result": "",
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": "",
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 ## Limitations
 
-- A video must be uploaded before a caption can be attached to it. In the following
+* A video must be uploaded before a caption can be attached to it. In the following
   example URLs, the video's ID is referenced as `media_id`.
-- Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
+* Stream only supports [WebVTT](https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API)
   formatted caption files. If you have a differently formatted caption file,
   use [a tool to convert your file to WebVTT](https://subtitletools.com/convert-to-vtt-online)
   prior to uploading it.
-- Videos may include several language captions, but each language must be unique.
+* Videos may include several language captions, but each language must be unique.
   For example, a video may have English, French, and German captions associated
   with it, but it cannot have two French captions.
-- Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
+* Each caption file is limited to 10 MB in size. [Contact support](/support/contacting-cloudflare-support/)
   if you need to upload a larger file.
 
 ## Most common language codes
@@ -504,4 +505,4 @@ deleted.
 | pl            | Polish           |
 | uk            | Ukrainian        |
 | my            | Burmese          |
-| th            | Thai             |
+| th            | Thai             |
\ No newline at end of file
diff --git a/src/content/docs/stream/edit-videos/player-enhancements.mdx b/src/content/docs/stream/edit-videos/player-enhancements.mdx
index 17a4d16c0a03c04..c439bce5564db4f 100644
--- a/src/content/docs/stream/edit-videos/player-enhancements.mdx
+++ b/src/content/docs/stream/edit-videos/player-enhancements.mdx
@@ -4,8 +4,8 @@ title: Add player enhancements
 description: Customize the Cloudflare Stream player with branding, logos, and share links.
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 With player enhancements, you can modify your video player to incorporate elements of your branding such as your logo, and customize additional options to present to your viewers.
@@ -14,10 +14,10 @@ The player enhancements are automatically applied to videos using the Stream Pla
 
 ## Properties
 
-- `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
-- `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
-- `channel_link`: The URL users will be directed to when selecting the logo from the video player.
-- `logo`: A valid HTTPS URL for the image of your logo.
+* `title`: The title that appears when viewers hover over the video. The title may differ from the file name of the video.
+* `share_link`: Provides the user with a click-to-copy option to easily share the video URL. This is commonly set to the URL of the page that the video is embedded on.
+* `channel_link`: The URL users will be directed to when selecting the logo from the video player.
+* `logo`: A valid HTTPS URL for the image of your logo.
 
 ## Customize your own player
 
@@ -61,6 +61,6 @@ You can also pull the JSON by using the endpoint below.
    <DashButton url="/?to=/:account/stream/videos" />
 
 2. Select a video from the list to edit it.
-3. Select the **Public Details** tab.
-4. From **Public Details**, enter information in the text fields for the properties you want to set.
-5. When you are done, select **Save**.
+4. Select the **Public Details** tab.
+5. From **Public Details**, enter information in the text fields for the properties you want to set.
+6. When you are done, select **Save**.
diff --git a/src/content/docs/stream/examples/dash-js.mdx b/src/content/docs/stream/examples/dash-js.mdx
index 734287e03dbb82d..08404220937a1dd 100644
--- a/src/content/docs/stream/examples/dash-js.mdx
+++ b/src/content/docs/stream/examples/dash-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and the DASH reference
   player (dash.js)
 tags:
diff --git a/src/content/docs/stream/examples/hls-js.mdx b/src/content/docs/stream/examples/hls-js.mdx
index db446e6987ec0c9..aeb76104307a2ce 100644
--- a/src/content/docs/stream/examples/hls-js.mdx
+++ b/src/content/docs/stream/examples/hls-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and the HLS reference
   player (hls.js)
 tags:
@@ -24,12 +25,12 @@ products:
 		<video id="video"></video>
 		<script>
 			if (Hls.isSupported()) {
-				const video = document.getElementById("video");
+				const video = document.getElementById('video');
 				const hls = new Hls();
 				hls.attachMedia(video);
 				hls.on(Hls.Events.MEDIA_ATTACHED, () => {
 					hls.loadSource(
-						"https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+						'https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8'
 					);
 				});
 			}
diff --git a/src/content/docs/stream/examples/index.mdx b/src/content/docs/stream/examples/index.mdx
index 53469dcc7069b34..8fb98577e0d6f90 100644
--- a/src/content/docs/stream/examples/index.mdx
+++ b/src/content/docs/stream/examples/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 hideChildren: true
 pcx_content_type: navigation
 title: Examples
diff --git a/src/content/docs/stream/examples/obs-from-scratch/index.mdx b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
index 6eab955a0b28cfb..ca8948b5ccc2a81 100644
--- a/src/content/docs/stream/examples/obs-from-scratch/index.mdx
+++ b/src/content/docs/stream/examples/obs-from-scratch/index.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up and start your first Live Stream using OBS (Open Broadcaster
   Software) Studio
 pcx_content_type: example
diff --git a/src/content/docs/stream/examples/rtmps_playback.mdx b/src/content/docs/stream/examples/rtmps_playback.mdx
index c614726f2680f0a..206b7ad224a4c78 100644
--- a/src/content/docs/stream/examples/rtmps_playback.mdx
+++ b/src/content/docs/stream/examples/rtmps_playback.mdx
@@ -17,10 +17,9 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the RTMPS _playback_ key for your live input from either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/srt_playback.mdx b/src/content/docs/stream/examples/srt_playback.mdx
index 3b5100f826b36a3..86ff42d0f0555d5 100644
--- a/src/content/docs/stream/examples/srt_playback.mdx
+++ b/src/content/docs/stream/examples/srt_playback.mdx
@@ -17,10 +17,9 @@ import { Render, DashButton } from "~/components";
 <Render file="prereqs_first_start_live_streaming" product="stream" />
 
 Copy the SRT Playback URL for your live input from either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
 - The [Stream API](/stream/stream-live/start-stream-live/#use-the-api)
 
diff --git a/src/content/docs/stream/examples/stream-player.mdx b/src/content/docs/stream/examples/stream-player.mdx
index a948e755d04215e..b542eeb0bb0f3c4 100644
--- a/src/content/docs/stream/examples/stream-player.mdx
+++ b/src/content/docs/stream/examples/stream-player.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with the Cloudflare Stream Player
 tags:
   - Playback
@@ -18,12 +19,12 @@ products:
 	<head> </head>
 	<body>
 		<div style="position: relative; padding-top: 56.25%;">
-			<iframe
-				src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-				style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-				allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-				allowfullscreen="true"
-			></iframe>
+		<iframe
+			src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+			style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+			allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+			allowfullscreen="true"
+		></iframe>
 		</div>
 	</body>
 </html>
diff --git a/src/content/docs/stream/examples/video-js.mdx b/src/content/docs/stream/examples/video-js.mdx
index e6a2aad84dcfd9f..e8fbb571e4df8ae 100644
--- a/src/content/docs/stream/examples/video-js.mdx
+++ b/src/content/docs/stream/examples/video-js.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and Video.js
 tags:
   - Playback
@@ -31,7 +32,7 @@ products:
 		</video-js>
 
 		<script>
-			const vid = document.getElementById("vid1");
+			const vid = document.getElementById('vid1');
 			const player = videojs(vid);
 		</script>
 	</body>
diff --git a/src/content/docs/stream/examples/vidstack.mdx b/src/content/docs/stream/examples/vidstack.mdx
index fee573dfe355731..50ee3a7e270f9f3 100644
--- a/src/content/docs/stream/examples/vidstack.mdx
+++ b/src/content/docs/stream/examples/vidstack.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of video playback with Cloudflare Stream and Vidstack
 tags:
   - Playback
@@ -18,13 +19,13 @@ products:
 There's a few options to choose from when getting started with Vidstack, follow any of the links
 below to get setup. You can replace the player `src` with `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8` to test Cloudflare Stream.
 
-- [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
-- [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
-- [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
-- [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
-- [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
-- [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
-- [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
+* [Angular](https://www.vidstack.io/docs/player/getting-started/installation/angular?provider=video)
+* [React](https://www.vidstack.io/docs/player/getting-started/installation/react?provider=video)
+* [Svelte](https://www.vidstack.io/docs/player/getting-started/installation/svelte?provider=video)
+* [Vue](https://www.vidstack.io/docs/player/getting-started/installation/vue?provider=video)
+* [Solid](https://www.vidstack.io/docs/player/getting-started/installation/solid?provider=video)
+* [Web Components](https://www.vidstack.io/docs/player/getting-started/installation/web-components?provider=video)
+* [CDN](https://www.vidstack.io/docs/player/getting-started/installation/cdn?provider=video)
 
 ## Examples
 
diff --git a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
index 84765138fc82658..67fd72638c29427 100644
--- a/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
+++ b/src/content/docs/stream/getting-analytics/fetching-bulk-analytics.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - stream
 ---
-
 import { DashButton } from "~/components";
 
 Stream provides analytics about both live video and video uploaded to Stream, via the GraphQL API described below, as well as on the Stream **Analytics** page of the Cloudflare dashboard.
diff --git a/src/content/docs/stream/getting-analytics/index.mdx b/src/content/docs/stream/getting-analytics/index.mdx
index ddc5d2b46f2d12e..0b87d38fd44efbc 100644
--- a/src/content/docs/stream/getting-analytics/index.mdx
+++ b/src/content/docs/stream/getting-analytics/index.mdx
@@ -6,21 +6,20 @@ sidebar:
   order: 8
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 Stream provides server-side analytics that can be used to:
 
-- Identify most viewed video content in your app or platform.
-- Identify where content is viewed from and when it is viewed.
-- Understand which creators on your platform are publishing the most viewed content, and analyze trends.
+* Identify most viewed video content in your app or platform.
+* Identify where content is viewed from and when it is viewed.
+* Understand which creators on your platform are publishing the most viewed content, and analyze trends.
 
 You can access data on either:
-
 - The Stream **Analytics** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/analytics" />
+   <DashButton url="/?to=/:account/stream/analytics" />
 
 - The [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics).
 
diff --git a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
index 2f19eae42ea7fc3..b4650f2f9bc28c2 100644
--- a/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
+++ b/src/content/docs/stream/getting-analytics/live-viewer-count.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 2
 products:
   - stream
+
 ---
 
 The Stream player has full support for live viewer counts by default. To get the viewer count for live videos for use with third party players, make a `GET` request to the `/views` endpoint.
diff --git a/src/content/docs/stream/manage-video-library/index.mdx b/src/content/docs/stream/manage-video-library/index.mdx
index b4ece17f01bbf40..f1c87b325b33406 100644
--- a/src/content/docs/stream/manage-video-library/index.mdx
+++ b/src/content/docs/stream/manage-video-library/index.mdx
@@ -9,3 +9,4 @@ sidebar:
 products:
   - stream
 ---
+
diff --git a/src/content/docs/stream/manage-video-library/searching.mdx b/src/content/docs/stream/manage-video-library/searching.mdx
index 78979f3e8fe99a6..385d98f5df957d0 100644
--- a/src/content/docs/stream/manage-video-library/searching.mdx
+++ b/src/content/docs/stream/manage-video-library/searching.mdx
@@ -4,6 +4,7 @@ title: Search for videos
 description: Search your Cloudflare Stream video library by name using the Stream API.
 products:
   - stream
+
 ---
 
 You can search for videos by name through the Stream API by adding a `search` query parameter to the [list media files](/api/resources/stream/methods/list/) endpoint.
diff --git a/src/content/docs/stream/stream-api.mdx b/src/content/docs/stream/stream-api.mdx
index 3cb2866bfef54bb..14a6a735991b555 100644
--- a/src/content/docs/stream/stream-api.mdx
+++ b/src/content/docs/stream/stream-api.mdx
@@ -7,4 +7,5 @@ sidebar:
   order: 11
 products:
   - stream
+
 ---
diff --git a/src/content/docs/stream/stream-live/custom-domains.mdx b/src/content/docs/stream/stream-live/custom-domains.mdx
index 9d386faca81de66..cbea1246aae4f56 100644
--- a/src/content/docs/stream/stream-live/custom-domains.mdx
+++ b/src/content/docs/stream/stream-live/custom-domains.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 3
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 With custom ingest domains, you can configure your RTMPS feeds to use an ingest URL that you specify instead of using `live.cloudflare.com.`
@@ -21,6 +21,7 @@ Custom Ingest Domains cannot be configured for domains with [zone holds](/fundam
 
 :::
 
+
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
 
    <DashButton url="/?to=/:account/stream/inputs" />
diff --git a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
index 6cc5f62c4cb10f5..de3dd780bfe12a4 100644
--- a/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
+++ b/src/content/docs/stream/stream-live/download-stream-live-videos.mdx
@@ -9,16 +9,18 @@ sidebar:
   order: 4
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 You can enable downloads for live stream videos from the Cloudflare dashboard. Videos are available for download after they enter the **Ready** state.
 
 :::note
 
+
 Downloadable MP4s are only available for live recordings under four hours. Live recordings exceeding four hours can be played at a later time but cannot be downloaded as an MP4.
 
+
 :::
 
 1. In the Cloudflare dashboard, go to the **Live inputs** page.
diff --git a/src/content/docs/stream/stream-live/dvr-for-live.mdx b/src/content/docs/stream/stream-live/dvr-for-live.mdx
index 3bcb1c067f39da8..47ae2985c0d2fce 100644
--- a/src/content/docs/stream/stream-live/dvr-for-live.mdx
+++ b/src/content/docs/stream/stream-live/dvr-for-live.mdx
@@ -13,14 +13,14 @@ manifest URL.
 
 ## Stream Player
 
-```html title="Stream Player embed format"
+``` html title="Stream Player embed format"
 <div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
+  <iframe
+    src="https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/iframe?dvrEnabled=true"
+    style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+    allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+    allowfullscreen="true"
+  ></iframe>
 </div>
 ```
 
@@ -37,7 +37,7 @@ When DVR mode is enabled the Stream Player will:
 
 ## HLS manifest for custom players
 
-```text title="HLS manifest URL format"
+``` text title="HLS manifest URL format"
 https://customer-<CODE>.cloudflarestream.com/<INPUT_ID|VIDEO_ID>/manifest/video.m3u8?dvrEnabled=true
 ```
 
diff --git a/src/content/docs/stream/stream-live/index.mdx b/src/content/docs/stream/stream-live/index.mdx
index 7baf513e8a40a50..3234ba97f8bbef7 100644
--- a/src/content/docs/stream/stream-live/index.mdx
+++ b/src/content/docs/stream/stream-live/index.mdx
@@ -9,6 +9,7 @@ sidebar:
   order: 4
 products:
   - stream
+
 ---
 
 Cloudflare Stream lets you or your users [stream live video](https://www.cloudflare.com/learning/video/what-is-live-streaming/), and play live video in your website or app, without managing and configuring any of your own infrastructure.
@@ -36,7 +37,7 @@ With ABR, client video players need to be provided with estimates of how much ba
 
 ### How it works
 
-If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution. This ensures that as many viewers as possible view the highest quality level.
+If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS and DASH manifests will be lower —  a stream like this has a low bitrate and requires relatively little bandwidth, even at high resolution.  This ensures that as many viewers as possible view the highest quality level.
 
 Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the manifest will be higher — a stream like this has a high bitrate and requires more bandwidth. This ensures that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
 
@@ -58,7 +59,7 @@ After the live stream ends, you can [replay live stream recordings](/stream/stre
 
 Stream Live is billed identically to the rest of Cloudflare Stream.
 
-- You pay $5 per 1000 minutes of recorded video.
-- You pay $1 per 1000 minutes of delivered video.
+* You pay $5 per 1000 minutes of recorded video.
+* You pay $1 per 1000 minutes of delivered video.
 
 All Stream Live videos are automatically recorded. There is no additional cost for encoding and packaging live videos.
diff --git a/src/content/docs/stream/stream-live/live-instant-clipping.mdx b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
index 7c329e9302fd291..900ea4ee817bc3f 100644
--- a/src/content/docs/stream/stream-live/live-instant-clipping.mdx
+++ b/src/content/docs/stream/stream-live/live-instant-clipping.mdx
@@ -10,8 +10,10 @@ Stream supports generating clips of live streams and recordings so creators and
 
 :::note[Note:]
 
+
 Clipping works differently for uploaded / on-demand videos. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
 
+
 :::
 
 ## Prerequisites
@@ -30,12 +32,18 @@ To help users replay and seek recent content, request a preview manifest by addi
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID||INPUT_ID>/manifest/video.m3u8?duration=5m
 ```
 
-- `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
+
+
+* `duration` string duration of the preview, up to 5 minutes as either a number of seconds ("30s") or minutes ("3m")
+
 
 When the preview manifest is delivered, inspect the headers for two properties:
 
-- `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the _broadcast_ start time, not the _preview_ start time.
-- `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an _input_ ID because the clip URL should reference the _video_ ID.
+
+
+* `preview-start-seconds` float seconds into the start of the live stream or recording that the preview manifest starts. Useful in applications that allow a user to select a range from the preview because the clip will need to reference its offset from the *broadcast* start time, not the *preview* start time.
+* `stream-media-id` string the video ID of the live stream or recording. Useful in applications that render the player using an *input* ID because the clip URL should reference the *video* ID.
+
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -51,44 +59,38 @@ let currentPreviewVideoID;
 
 // Override the pLoader (playlist loader) to read the manifest headers:
 class pLoader extends Hls.DefaultConfig.loader {
-	constructor(config) {
-		super(config);
-		var load = this.load.bind(this);
-		this.load = function (context, config, callbacks) {
-			if (context.type == "manifest") {
-				var onSuccess = callbacks.onSuccess;
-				// copy the existing onSuccess handler to fire it later.
-
-				callbacks.onSuccess = function (
-					response,
-					stats,
-					context,
-					networkDetails,
-				) {
-					// The fourth argument here is undocumented in HLS.js but contains
-					// the response object for the manifest fetch, which gives us headers:
-
-					currentPreviewStart = parseFloat(
-						networkDetails.getResponseHeader("preview-start-seconds"),
-					);
-					// Save the start time of the preview manifest
-
-					currentPreviewVideoID =
-						networkDetails.getResponseHeader("stream-media-id");
-					// Save the video ID in case the preview was loaded with an input ID
-
-					onSuccess(response, stats, context);
-					// And fire the existing success handler.
-				};
-			}
-			load(context, config, callbacks);
-		};
-	}
+  constructor(config) {
+    super(config);
+    var load = this.load.bind(this);
+    this.load = function (context, config, callbacks) {
+      if (context.type == 'manifest') {
+        var onSuccess = callbacks.onSuccess;
+        // copy the existing onSuccess handler to fire it later.
+
+        callbacks.onSuccess = function (response, stats, context, networkDetails) {
+          // The fourth argument here is undocumented in HLS.js but contains
+          // the response object for the manifest fetch, which gives us headers:
+
+          currentPreviewStart =
+            parseFloat(networkDetails.getResponseHeader('preview-start-seconds'));
+          // Save the start time of the preview manifest
+
+          currentPreviewVideoID =
+            networkDetails.getResponseHeader('stream-media-id');
+          // Save the video ID in case the preview was loaded with an input ID
+
+          onSuccess(response, stats, context);
+          // And fire the existing success handler.
+        };
+      }
+      load(context, config, callbacks);
+    };
+  }
 }
 
 // Specify the new loader class when setting up HLS
 const hls = new Hls({
-	pLoader: pLoader,
+  pLoader: pLoader,
 });
 ```
 
@@ -100,8 +102,11 @@ To play a clip of a live stream or recording, request a clip manifest with a dur
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/manifest/clip.m3u8?time=600s&duration=30s
 ```
 
-- `time` string start time of the clip in seconds, from the start of the live stream or recording
-- `duration` string duration of the clip in seconds, up to 60 seconds max
+
+
+* `time` string start time of the clip in seconds, from the start of the live stream or recording
+* `duration` string duration of the clip in seconds, up to 60 seconds max
+
 
 This manifest can be played and seeked using any HLS-compatible player.
 
@@ -113,6 +118,8 @@ An MP4 of the clip can also be generated dynamically to be saved and shared on o
 https://customer-<CODE>.cloudflarestream.com/<VIDEO_ID>/clip.mp4?time=600s&duration=30s&filename=clip.mp4
 ```
 
-- `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
-- `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
-- `filename` string _(optional)_ a filename for the clip
+
+
+* `time` string start time of the clip in seconds, from the start of the live stream or recording (example: "500s")
+* `duration` string duration of the clip in seconds, up to 60 seconds max (example: "60s")
+* `filename` string *(optional)* a filename for the clip
diff --git a/src/content/docs/stream/stream-live/simulcasting.mdx b/src/content/docs/stream/stream-live/simulcasting.mdx
index 0f88a8a94fd31ff..e5f03f9003c3432 100644
--- a/src/content/docs/stream/stream-live/simulcasting.mdx
+++ b/src/content/docs/stream/stream-live/simulcasting.mdx
@@ -9,8 +9,8 @@ sidebar:
   order: 5
 products:
   - stream
----
 
+---
 import { DashButton } from "~/components";
 
 Simulcasting lets you forward your live stream to third-party platforms such as Twitch, YouTube, Facebook, Twitter, and more. You can simulcast to up to 50 concurrent destinations from each live input. To begin simulcasting, select an input and add one or more Outputs.
@@ -28,32 +28,30 @@ https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/live_inputs/<I
 
 ```json title="Response"
 {
-	"result": {
-		"uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
-		"url": "rtmp://a.rtmp.youtube.com/live2",
-		"streamKey": "<redacted>"
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "uid": "6f8339ed45fe87daa8e7f0fe4e4ef776",
+    "url": "rtmp://a.rtmp.youtube.com/live2",
+    "streamKey": "<redacted>"
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 ## Control when you start and stop simulcasting
 
 You can enable and disable individual live outputs with either:
-
 - The **Live inputs** page of the Cloudflare dashboard.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
-
+   <DashButton url="/?to=/:account/stream/inputs" />
 - [The API](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/update/)
 
 This allows you to:
 
-- Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
-- Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
-- Give your own users manual control over when they go live to specific simulcasting destinations.
+* Start a live stream, but wait to start simulcasting to YouTube and Twitch until right before the content begins.
+* Stop simulcasting before the live stream ends, to encourage viewers to transition from a third-party service like YouTube or Twitch to a direct live stream.
+* Give your own users manual control over when they go live to specific simulcasting destinations.
 
 When a live output is disabled, video is not simulcast to the live output, even when actively streaming to the corresponding live input.
 
@@ -70,11 +68,11 @@ By default, all live outputs are enabled.
 
 ## Manage outputs
 
-| Command                                                                                                                                      | Method   | Endpoint                                                                                        |
-| -------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------- |
-| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)                                                                 | `GET`    | `accounts/:account_identifier/stream/live_inputs`                                               |
-| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/)                                                             | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier`                        |
-| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET`    | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs`                     |
-| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/)                                      | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
+| Command                                                                  | Method   | Endpoint                                                                 |
+| ------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------ |
+| [List outputs](/api/resources/stream/subresources/live_inputs/methods/list/)      | `GET`    | `accounts/:account_identifier/stream/live_inputs`                        |
+| [Delete outputs](/api/resources/stream/subresources/live_inputs/methods/delete/) | `DELETE` | `accounts/:account_identifier/stream/live_inputs/:live_input_identifier` |
+| [List All Outputs Associated With A Specified Live Input](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/list/) | `GET` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs` |
+| [Delete An Output](/api/resources/stream/subresources/live_inputs/subresources/outputs/methods/delete/) | `DELETE` | `/accounts/{account_id}/stream/live_inputs/{live_input_identifier}/outputs/{output_identifier}` |
 
 If the associated live input is already retransmitting to this output when you make the `DELETE` request, that output will be disconnected within 30 seconds.
diff --git a/src/content/docs/stream/stream-live/start-stream-live.mdx b/src/content/docs/stream/stream-live/start-stream-live.mdx
index 7c32e2b8b669da8..0f114459ebb8755 100644
--- a/src/content/docs/stream/stream-live/start-stream-live.mdx
+++ b/src/content/docs/stream/stream-live/start-stream-live.mdx
@@ -22,7 +22,6 @@ After you subscribe to Stream, you can create Live Inputs in Dash or via the API
 ## Use the dashboard
 
 **Step 1:** In the Cloudflare dashboard, go to the **Live inputs** page and create a live input.
-
 <DashButton url="/?to=/:account/stream/inputs" />
 
 ![Create live input field from dashboard](~/assets/images/stream/create-live-input-from-stream-dashboard.png)
diff --git a/src/content/docs/stream/stream-live/troubleshooting.mdx b/src/content/docs/stream/stream-live/troubleshooting.mdx
index 48973fe852b3b32..d82985f4c5dfeff 100644
--- a/src/content/docs/stream/stream-live/troubleshooting.mdx
+++ b/src/content/docs/stream/stream-live/troubleshooting.mdx
@@ -7,8 +7,7 @@ sidebar:
 products:
   - stream
 ---
-
-import { Details, DashButton } from "~/components";
+import {Details, DashButton } from "~/components"
 
 In addition to following the live stream troubleshooting steps in this guide, make sure that your video settings align with [Cloudflare live stream recommendations](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If you use OBS, you can also check these [OBS-specific recommendations](/stream/examples/obs-from-scratch/#6-optional-optimize-settings).
 
@@ -24,37 +23,29 @@ If your live stream is buffering, freezing, experiencing latency issues, or havi
 
 3. Look at your **Keyframe Interval** chart.
 
-   It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform. \* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
-   - If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
+	It should be a consistent flat line that stays between 2s and 8s. If you see an inconsistent or wavy line, or a line that is consistently below 2s or above 8s, adjust the keyframe interval (also called GOP size) in your software or service used to send the stream to Cloudflare. The exact steps for editing those settings will depend on your platform.
+			* Start by setting the keyframe interval to 4s. If playback is stable but latency is still too high, lower it to 2s. If you are experiencing buffering or freezing in playback, increase it to 8s.
+
+	  	* If the keyframe interval is "variable" or "automatic", change it to a specific number instead, like 4s.
 
-   <Details header="What is a keyframe interval?">
-   	The keyframe interval (also called GOP size) is a measurement of how often
-   	keyframes are sent to Stream. A shorter keyframe interval requires more
-   	Internet bandwidth on the broadcast side, but can reduce glass-to-glass
-   	latency. A longer keyframe requires less Internet bandwidth and can reduce
-   	buffering and freezing, but can increase glass-to-glass latency.
-   </Details>
+	<Details header="What is a keyframe interval?">
+	The keyframe interval (also called GOP size) is a measurement of how often keyframes are sent to Stream. A shorter keyframe interval requires more Internet bandwidth on the broadcast side, but can reduce glass-to-glass latency. A longer keyframe requires less Internet bandwidth and can reduce buffering and freezing, but can increase glass-to-glass latency.
+	</Details>
 
-4. Look at your **Upload-to-Duration Ratio** chart.
+3. Look at your **Upload-to-Duration Ratio** chart.
 
-   It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
-   - [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
+	It should be a consistent flat line below 90%. If you see an inconsistent or wavy line, or a line that is consistently above 100%, try the following troubleshooting steps:
+    * [Check that your Internet upload speed](https://speed.cloudflare.com/) is at least 20 Mbps. If it is below 20 Mbps, use common troubleshooting steps such as restarting your router, using an Ethernet connection instead of Wi-Fi, or contacting your Internet service provider.
 
-   - Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
-     - If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
-     - If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
+    * Check the video bitrate setting in the software or service you use to send the stream to Cloudflare.
+	   * If it is "variable", change it to "constant" with a specific number, like 8 Mbps.
+	   * If it is above 15 Mbps, lower it to 8 Mbps or 70% of your Internet speed, whichever is lower.
 
-   - Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
+    * Follow the steps above (the keyframe interval steps) to _increase_ the keyframe interval in the software or service you use to send the stream to Cloudflare.
 
-   <Details header="What is the upload-to-duration ratio?">
-   	The upload-to-duration ratio is a measurement of how long it takes to
-   	upload a part of the stream compared to how long that part would take to
-   	play. A ratio of less than 100% means that the stream is uploading at least
-   	as fast as it would take to play, so most users should not experience
-   	buffering or freezing. A ratio of 100% or more means that your video is
-   	uploading slower than it would take to play, so it is likely that most
-   	users will experience buffering and freezing.
-   </Details>
+	<Details header="What is the upload-to-duration ratio?">
+	The upload-to-duration ratio is a measurement of how long it takes to upload a part of the stream compared to how long that part would take to play. A ratio of less than 100% means that the stream is uploading at least as fast as it would take to play, so most users should not experience buffering or freezing. A ratio of 100% or more means that your video is uploading slower than it would take to play, so it is likely that most users will experience buffering and freezing.
+	</Details>
 
 ## Encoder failing to connect or keeps disconnecting
 
@@ -64,22 +55,22 @@ If your encoder shows a connection error such as "Failed to connect to server" o
 
 - Verify that the live input is enabled. A live input that is _disabled_ will reject all incoming connections. You can enable or disable a live input from the **Live inputs** page in the Dashboard or via the API using the `enabled` property.
 
-  <DashButton url="/?to=/:account/stream/inputs" />
+   <DashButton url="/?to=/:account/stream/inputs" />
 
-  ```bash
-  curl -X GET \
-  --header "Authorization: Bearer <API_TOKEN>" \
-  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
-  ```
+   ```bash
+   curl -X GET \
+   --header "Authorization: Bearer <API_TOKEN>" \
+   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id}
+   ```
 
-  If `enabled` is `false` in the response, update the live input to enable it:
+   If `enabled` is `false` in the response, update the live input to enable it:
 
-  ```bash
-  curl --request PUT \
-  https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
-  --header "Authorization: Bearer <API_TOKEN>" \
-  --data '{"enabled": true}'
-  ```
+   ```bash
+   curl --request PUT \
+   https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
+   --header "Authorization: Bearer <API_TOKEN>" \
+   --data '{"enabled": true}'
+   ```
 
 - If you use [Live Webhooks](/stream/stream-live/webhooks/), check for a `live_input.errored` event. The webhook payload includes an [error code](/stream/stream-live/webhooks/#error-codes) that can help you troubleshoot the specific cause.
 
@@ -93,4 +84,4 @@ If your encoder is connected and the dashboard shows a green **Connected** statu
 
 - Verify that your encoder is sending [AAC audio](/stream/stream-live/start-stream-live/#recommendations-requirements-and-limitations). If it is not, set your encoder's settings to AAC explicitly.
 
-- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to _variable_ or _automatic_, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
+- Verify that your encoder is sending keyframes at a fixed interval between two and eight seconds. If the keyframe interval is set to *variable* or *automatic*, change it to a specific value such as four seconds. For more details, refer to the keyframe information in the [Buffering, freezing, and latency](#buffering-freezing-and-latency) section above.
\ No newline at end of file
diff --git a/src/content/docs/stream/stream-live/webhooks.mdx b/src/content/docs/stream/stream-live/webhooks.mdx
index 2f298bf7ca81d9d..b80693318e6d6cb 100644
--- a/src/content/docs/stream/stream-live/webhooks.mdx
+++ b/src/content/docs/stream/stream-live/webhooks.mdx
@@ -8,7 +8,7 @@ products:
   - stream
 ---
 
-import { AvailableNotifications, DashButton } from "~/components";
+import { AvailableNotifications,DashButton } from "~/components"
 
 Stream Live offers webhooks to notify your service when an Input connects, disconnects, or encounters an error with Stream Live.
 
@@ -40,15 +40,15 @@ Webhooks works differently for uploaded / on-demand videos. For more information
 
 ```json title="Example webhook payload"
 {
-	"name": "Live Webhook Test",
-	"text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
-	"data": {
-		"notification_name": "Stream Live Input",
-		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-		"event_type": "live_input.disconnected",
-		"updated_at": "2022-01-13T11:43:41.855717910Z"
-	},
-	"ts": 1642074233
+  "name": "Live Webhook Test",
+  "text": "Notification type: Stream Live Input\nInput ID: eb222fcca08eeb1ae84c981ebe8aeeb6\nEvent type: live_input.disconnected\nUpdated at: 2022-01-13T11:43:41.855717910Z",
+  "data": {
+    "notification_name": "Stream Live Input",
+    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+    "event_type": "live_input.disconnected",
+    "updated_at": "2022-01-13T11:43:41.855717910Z"
+  },
+  "ts": 1642074233
 }
 ```
 
@@ -58,30 +58,30 @@ If there are issues detected with the input, the `event_type` will be `live_inpu
 
 ## Error codes
 
-- `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
-- `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
-- `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
-- `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
-- `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
+* `ERR_GOP_OUT_OF_RANGE` – The input GOP size or keyframe interval is out of range.
+* `ERR_UNSUPPORTED_VIDEO_CODEC` – The input video codec is unsupported for the protocol used.
+* `ERR_UNSUPPORTED_AUDIO_CODEC` – The input audio codec is unsupported for the protocol used.
+* `ERR_STORAGE_QUOTA_EXHAUSTED` – The account storage quota has been exceeded. Delete older content or purchase additional storage.
+* `ERR_MISSING_SUBSCRIPTION` – Unauthorized to start a live stream. Check subscription or log into Dash for details.
 
 ```json title="Example live_input.errored webhook payload"
 {
-	"name": "Live Webhook Test",
-	"text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
-	"data": {
-		"notification_name": "Stream Live Input",
-		"input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
-		"event_type": "live_input.errored",
-		"updated_at": "2024-07-09T18:07:51.077371662Z",
-		"live_input_errored": {
-			"error": {
-				"code": "ERR_GOP_OUT_OF_RANGE",
-				"message": "Input GOP size or keyframe interval is out of range."
-			},
-			"video_codec": "",
-			"audio_codec": ""
-		}
-	},
-	"ts": 1720548474
+  "name": "Live Webhook Test",
+  "text": "Notification type: Stream Live Input\nInput ID: 2c28dd2cc444cb77578c4840b51e43a8\nEvent type: live_input.errored\nUpdated at: 2024-07-09T18:07:51.077371662Z\nError Code: ERR_GOP_OUT_OF_RANGE\nError Message: Input GOP size or keyframe interval is out of range.\nVideo Codec: \nAudio Codec: ",
+  "data": {
+    "notification_name": "Stream Live Input",
+    "input_id": "eb222fcca08eeb1ae84c981ebe8aeeb6",
+    "event_type": "live_input.errored",
+    "updated_at": "2024-07-09T18:07:51.077371662Z",
+    "live_input_errored": {
+      "error": {
+        "code": "ERR_GOP_OUT_OF_RANGE",
+        "message": "Input GOP size or keyframe interval is out of range."
+      },
+      "video_codec": "",
+      "audio_codec": ""
+    }
+  },
+  "ts": 1720548474,
 }
 ```
diff --git a/src/content/docs/stream/transform-videos/bindings.mdx b/src/content/docs/stream/transform-videos/bindings.mdx
index 8d5cd162e0df120..5e17fac1f2f59de 100644
--- a/src/content/docs/stream/transform-videos/bindings.mdx
+++ b/src/content/docs/stream/transform-videos/bindings.mdx
@@ -13,6 +13,7 @@ products:
 
 import { WranglerConfig, InlineBadge } from "~/components";
 
+
 A [binding](/workers/runtime-apis/bindings/) connects your [Worker](/workers/) to external resources on the Developer Platform, like [Media Transformations](/stream/transform-videos/), [R2 buckets](/r2/buckets/), or [KV namespaces](/kv/concepts/kv-namespaces/).
 
 You can bind the Media Transformations API to your Worker to transform, resize, and extract content from videos without requiring them to be accessible through a URL.
@@ -154,8 +155,8 @@ export default {
 		const frame = await env.MEDIA.input(video.body)
 			.transform({ width: 720 })
 			.output({
-				mode: "frame",
-				time: "3s",
+				mode: 'frame',
+				time: '3s',
 			})
 			.response();
 
@@ -165,10 +166,13 @@ export default {
 			prompt: "Generate a caption for this image",
 			max_tokens: 512,
 		};
-		const response = await env.AI.run("@cf/unum/uform-gen2-qwen-500m", payload);
+		const response = await env.AI.run(
+			"@cf/unum/uform-gen2-qwen-500m",
+			payload
+		);
 		return new Response(JSON.stringify(response));
-	},
-};
+	}
+}
 ```
 
 ### Extract audio
@@ -210,22 +214,28 @@ export default {
 		const audio = await env.MEDIA.input(video.body)
 			.transform()
 			.output({
-				mode: "audio",
-			})
+				mode: 'audio',
+				})
 			.response();
 
 		// Prepare and run Workers AI inference
 		const payload = {
 			audio: [...new Uint8Array(await audio.arrayBuffer())],
 		};
-		const response = await env.AI.run("@cf/openai/whisper", payload);
+		const response = await env.AI.run(
+			"@cf/openai/whisper",
+			payload
+		);
 
 		// response will have props {text, word_count, vtt, words}
-		return new Response(JSON.stringify(response, null, 2), {
-			headers: { "Content-Type": "application/json" },
-		});
-	},
-};
+		return new Response(
+			JSON.stringify(response, null, 2),
+			{
+				headers: {'Content-Type': 'application/json'}
+			}
+		);
+	}
+}
 ```
 
 ### Store transformed output in R2
diff --git a/src/content/docs/stream/transform-videos/index.mdx b/src/content/docs/stream/transform-videos/index.mdx
index 1d9dfe55c0bc0b1..cd79ead8f896bd9 100644
--- a/src/content/docs/stream/transform-videos/index.mdx
+++ b/src/content/docs/stream/transform-videos/index.mdx
@@ -7,15 +7,17 @@ sidebar:
 products:
   - stream
 ---
-
 import { DashButton } from "~/components";
 
 :::note[Media Transformations is now GA:]
 
+
 Billing for Media Transformations began on November 1st, 2025.
 
+
 :::
 
+
 You can optimize and manipulate videos stored _outside_ of Cloudflare Stream with Media Transformations. Transformed videos and images are served from one of your zones on Cloudflare.
 
 To transform a video or image, you must [enable transformations](/stream/transform-videos/#getting-started) for your zone. If your zone already has Image Transformations enabled, you can also optimize videos with Media Transformations.
diff --git a/src/content/docs/stream/uploading-videos/index.mdx b/src/content/docs/stream/uploading-videos/index.mdx
index 8d01549e5d26ccf..1e357b50c36f54c 100644
--- a/src/content/docs/stream/uploading-videos/index.mdx
+++ b/src/content/docs/stream/uploading-videos/index.mdx
@@ -12,15 +12,17 @@ Before you upload your video, review the options for uploading a video, supporte
 
 ## Upload options
 
-| Upload method                                                              | When to use                                                                             |
-| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
-| [Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)       | Upload videos from the Stream Dashboard without writing any code.                       |
-| [Upload with a link](/stream/uploading-videos/upload-via-link/)            | Upload videos using a link, such as an S3 bucket or content management system.          |
-| [Upload video file](/stream/uploading-videos/upload-video-file/)           | Upload videos stored on a computer.                                                     |
-| [Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/) | Allows end users of your website or app to upload videos directly to Cloudflare Stream. |
+| Upload method	| When to use |
+|---------------|-------------|
+|[Stream Dashboard](https://dash.cloudflare.com/?to=/:account/stream)| Upload videos from the Stream Dashboard without writing any code.
+|[Upload with a link](/stream/uploading-videos/upload-via-link/)| Upload videos using a link, such as an S3 bucket or content management system.
+|[Upload video file](/stream/uploading-videos/upload-video-file/)| Upload videos stored on a computer.
+|[Direct creator uploads](/stream/uploading-videos/direct-creator-uploads/)| Allows end users of your website or app to upload videos directly to Cloudflare Stream.
+
 
 ## Supported video formats
 
+
 :::note
 Files must be less than 30 GB, and content should be encoded and uploaded in the same frame rate it was recorded.
 :::
diff --git a/src/content/docs/stream/uploading-videos/player-api.mdx b/src/content/docs/stream/uploading-videos/player-api.mdx
index afe17603c50c36e..ba0c652f2710a62 100644
--- a/src/content/docs/stream/uploading-videos/player-api.mdx
+++ b/src/content/docs/stream/uploading-videos/player-api.mdx
@@ -22,82 +22,103 @@ Multiple attributes can be used together, added one after each other like this:
 
 ## Supported attributes
 
-- `autoplay` boolean
-  - Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
+* `autoplay` boolean
+
+  * Tells the browser to immediately start downloading the video and play it as soon as it can. Note that mobile browsers generally do not support this attribute, the user must tap the screen to begin video playback. Please consider mobile users or users with Internet usage limits as some users do not have unlimited Internet access before using this attribute.
 
   :::note
   To disable video autoplay, the `autoplay` attribute needs to be removed altogether as this attribute. Setting `autoplay="false"` will not work; the video will autoplay if the attribute is there in the `<stream>` tag.
 
 In addition, some browsers now prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, see [new video policies for iOS](https://webkit.org/blog/6784/new-video-policies-for-ios/).
-:::
+  :::
+
+* `controls` boolean
+
+  * Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
+
+* `height` integer
+
+  * The height of the video's display area, in CSS pixels.
 
-- `controls` boolean
-  - Shows the default video controls such as buttons for play/pause, volume controls. You may choose to build buttons and controls that work with the player. [See an example.](/stream/viewing-videos/using-own-player/)
+* `loop` boolean
 
-- `height` integer
-  - The height of the video's display area, in CSS pixels.
+  * A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
 
-- `loop` boolean
-  - A Boolean attribute; if included in the HTML tag, player will, automatically seek back to the start upon reaching the end of the video.
+* `muted` boolean
 
-- `muted` boolean
-  - A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
+  * A Boolean attribute which indicates the default setting of the audio contained in the video. If set, the audio will be initially silenced.
 
-- `preload` string | null
-  - This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
+* `preload` string | null
+
+  * This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. You may choose to include this attribute as a boolean attribute without a value, or you may specify the value `preload="auto"` to preload the beginning of the video. Not including the attribute or using `preload="metadata"` will just load the metadata needed to start video playback when requested.
 
   :::note
   The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
   :::
 
-- `poster` string
-  - A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
+* `poster` string
+
+  * A URL for an image to be shown before the video is started or while the video is downloading. If this attribute is not specified, a thumbnail image of the video is shown.
+
+* `src` string
 
-- `src` string
-  - The video id from the video you've uploaded to Cloudflare Stream should be included here.
+  * The video id from the video you've uploaded to Cloudflare Stream should be included here.
 
-- `width` integer
-  - The width of the video's display area, in CSS pixels.
+* `width` integer
+
+  * The width of the video's display area, in CSS pixels.
 
 ## Methods
 
-- `play()` Promise
-  - Start video playback.
+* `play()` Promise
+
+  * Start video playback.
+
+* `pause()` null
 
-- `pause()` null
-  - Pause video playback.
+  * Pause video playback.
 
 ## Properties
 
-- `autoplay`
-  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+* `autoplay`
 
-- `controls`
-  - Sets or returns whether the video should display controls (like play/pause etc.)
+  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
-- `currentTime`
-  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+* `controls`
 
-- `duration` readonly
-  - Returns the duration of the video in seconds.
+  * Sets or returns whether the video should display controls (like play/pause etc.)
 
-- `ended` readonly
-  - Returns whether the video has ended.
+* `currentTime`
 
-- `loop`
-  - Sets or returns whether the video should start over when it reaches the end
+  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
 
-- `muted`
-  - Sets or returns whether the audio should be played with the video
+* `duration` readonly
 
-- `paused` readonly
-  - Returns whether the video is paused
+  * Returns the duration of the video in seconds.
 
-- `preload`
-  - Sets or returns whether the video should be preloaded upon element load.
+* `ended` readonly
 
-- `volume`
-  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+  * Returns whether the video has ended.
+
+* `loop`
+
+  * Sets or returns whether the video should start over when it reaches the end
+
+* `muted`
+
+  * Sets or returns whether the audio should be played with the video
+
+* `paused` readonly
+
+  * Returns whether the video is paused
+
+* `preload`
+
+  * Sets or returns whether the video should be preloaded upon element load.
+
+* `volume`
+
+  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -105,78 +126,102 @@ In addition, some browsers now prevent videos with audio from playing automatica
 
 Stream supports most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-- `abort`
-  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
+* `abort`
+
+  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `canplay`
-  - Sent when enough data is available that the media can be played, at least for a couple of frames.
+* `canplay`
 
-- `canplaythrough`
-  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+  * Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `durationchange`
-  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+* `canplaythrough`
 
-- `ended`
-  - Sent when playback completes.
+  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-- `error`
-  - Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+* `durationchange`
 
-- `loadeddata`
-  - The first frame of the media has finished loading.
+  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-- `loadedmetadata`
-  - The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
+* `ended`
 
-- `loadstart`
-  - Sent when loading of the media begins.
+  * Sent when playback completes.
 
-- `pause`
-  - Sent when the playback state is changed to paused (paused property is true).
+* `error`
 
-- `play`
-  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+  * Sent when an error occurs. (for example, the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-- `playing`
-  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+* `loadeddata`
 
-- `progress`
-  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+  * The first frame of the media has finished loading.
 
-- `ratechange`
-  - Sent when the playback speed changes.
+* `loadedmetadata`
 
-- `seeked`
-  - Sent when a seek operation completes.
+   * The media's metadata has finished loading; all attributes now contain as much useful information as they are going to.
 
-- `seeking`
-  - Sent when a seek operation begins.
+* `loadstart`
 
-- `stalled`
-  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+  * Sent when loading of the media begins.
 
-- `suspend`
-  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+* `pause`
 
-- `timeupdate`
-  - The time indicated by the element's currentTime attribute has changed.
+  * Sent when the playback state is changed to paused (paused property is true).
 
-- `volumechange`
-  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+* `play`
 
-- `waiting`
-  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
+  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+
+* `playing`
+
+  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+
+* `progress`
+
+  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+
+* `ratechange`
+
+  * Sent when the playback speed changes.
+
+* `seeked`
+
+  * Sent when a seek operation completes.
+
+* `seeking`
+
+  * Sent when a seek operation begins.
+
+* `stalled`
+
+  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+
+* `suspend`
+
+  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+
+* `timeupdate`
+
+  * The time indicated by the element's currentTime attribute has changed.
+
+* `volumechange`
+
+  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+
+* `waiting`
+
+  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-- `stream-adstart`
-  - Fires when `ad-url` attribute is present and the ad begins playback
+* `stream-adstart`
+
+  * Fires when `ad-url` attribute is present and the ad begins playback
+
+* `stream-adend`
+
+  * Fires when `ad-url` attribute is present and the ad finishes playback
 
-- `stream-adend`
-  - Fires when `ad-url` attribute is present and the ad finishes playback
+* `stream-adtimeout`
 
-- `stream-adtimeout`
-  - Fires when `ad-url` attribute is present and the ad took too long to load.
+  * Fires when `ad-url` attribute is present and the ad took too long to load.
diff --git a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
index 44e7fb9660de859..aff3f05547c7c42 100644
--- a/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
+++ b/src/content/docs/stream/uploading-videos/resumable-uploads.mdx
@@ -176,21 +176,27 @@ The tus protocol allows you to add optional parameters in the [`Upload-Metadata`
 Setting arbitrary metadata values in the `Upload-Metadata` header sets values in the [meta key in Stream API](/api/resources/stream/methods/list/).
 
 - `name`
+
   - Setting this key will set `meta.name` in the API and display the value as the name of the video in the dashboard.
 
 - `requiresignedurls`
+
   - If this key is present, the video playback for this video will be required to use signed URLs after upload.
 
 - `scheduleddeletion`
+
   - Specifies a date and time when a video will be deleted. After a video is deleted, it is no longer viewable and no longer counts towards storage for billing. The specified date and time cannot be earlier than 30 days or later than 1,096 days from the video's created timestamp.
 
 - `allowedorigins`
+
   - An array of strings listing origins allowed to display the video. This will set the [allowed origins setting](/stream/viewing-videos/securing-your-stream/#security-considerations) for the video.
 
 - `thumbnailtimestamppct`
+
   - Specify the default thumbnail [timestamp percentage](/stream/viewing-videos/displaying-thumbnails/). Note that percentage is a floating point value between 0.0 and 1.0.
 
 - `watermark`
+
   - The watermark profile UID.
 
 ## Set creator property
diff --git a/src/content/docs/stream/uploading-videos/upload-via-link.mdx b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
index 2b140c2dc1d2686..1d7071ca08fb038 100644
--- a/src/content/docs/stream/uploading-videos/upload-via-link.mdx
+++ b/src/content/docs/stream/uploading-videos/upload-via-link.mdx
@@ -8,7 +8,11 @@ products:
   - stream
 ---
 
-import { Tabs, TabItem, LinkButton } from "~/components";
+import {
+	Tabs,
+	TabItem,
+	LinkButton,
+} from "~/components"
 
 If you have videos stored in a cloud storage bucket, you can pass a HTTP link for the file, and Stream will fetch the file on your behalf.
 
@@ -104,45 +108,45 @@ You can optionally use [webhooks](/stream/manage-video-library/using-webhooks/)
 
 ```json {3,6}
 {
-	"result": {
-		"uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
-		"thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
-		"thumbnailTimestampPct": 0,
-		"readyToStream": false,
-		"status": {
-			"state": "downloading"
-		},
-		"meta": {
-			"downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
-			"name": "My First Stream Video"
-		},
-		"created": "2020-10-16T20:20:17.872170843Z",
-		"modified": "2020-10-16T20:20:17.872170843Z",
-		"size": 9032701,
-		"preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
-		"allowedOrigins": [],
-		"requireSignedURLs": false,
-		"uploaded": "2020-10-16T20:20:17.872170843Z",
-		"uploadExpiry": null,
-		"maxSizeBytes": 0,
-		"maxDurationSeconds": 0,
-		"duration": -1,
-		"input": {
-			"width": -1,
-			"height": -1
-		},
-		"playback": {
-			"hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
-			"dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
-		},
-		"watermark": null
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "uid": "6b9e68b07dfee8cc2d116e4c51d6a957",
+    "thumbnail": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg",
+    "thumbnailTimestampPct": 0,
+    "readyToStream": false,
+    "status": {
+      "state": "downloading"
+    },
+    "meta": {
+      "downloaded-from": "https://storage.googleapis.com/zaid-test/Watermarks%20Demo/cf-ad-original.mp4",
+      "name": "My First Stream Video"
+    },
+    "created": "2020-10-16T20:20:17.872170843Z",
+    "modified": "2020-10-16T20:20:17.872170843Z",
+    "size": 9032701,
+    "preview": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/watch",
+    "allowedOrigins": [],
+    "requireSignedURLs": false,
+    "uploaded": "2020-10-16T20:20:17.872170843Z",
+    "uploadExpiry": null,
+    "maxSizeBytes": 0,
+    "maxDurationSeconds": 0,
+    "duration": -1,
+    "input": {
+      "width": -1,
+      "height": -1
+    },
+    "playback": {
+      "hls": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.m3u8",
+      "dash": "https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/manifest/video.mpd"
+    },
+    "watermark": null
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
 After the video is uploaded, you can use the video `uid` shown in the example response above to play the video using the [Stream video player](/stream/viewing-videos/using-the-stream-player/).
 
-If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
+If you are using your own player or rendering the video in a mobile app, refer to [using your own player](/stream/viewing-videos/using-the-stream-player/using-the-player-api/).
\ No newline at end of file
diff --git a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
index 1aa988048c1fe40..cc8a1491f78e4b0 100644
--- a/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
+++ b/src/content/docs/stream/viewing-videos/displaying-thumbnails.mdx
@@ -10,8 +10,10 @@ products:
 
 :::note
 
+
 Stream thumbnails are not supported for videos with non-square pixels.
 
+
 :::
 
 ## Use Case 1: Generating a thumbnail on-the-fly
@@ -20,32 +22,29 @@ A thumbnail from your video can be generated using a special link where you spec
 
 `https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270`
 
-<img
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270"
-	alt="Example of thumbnail image generated from example video"
-/>
+<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.jpg?time=1s&height=270" alt="Example of thumbnail image generated from example video" />
 
 Using the `poster` query parameter in the embed URL, you can set a thumbnail to any time in your video. If [signed URLs](/stream/viewing-videos/securing-your-stream/) are required, you must use a signed URL instead of video UIDs.
 
 ```html
 <iframe
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-	style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-	allowfullscreen="true"
+  src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/iframe?poster=https%3A%2F%2Fcustomer-f33zs165nr7gyfy4.cloudflarestream.com%2F6b9e68b07dfee8cc2d116e4c51d6a957%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
+  style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
+  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+  allowfullscreen="true"
 ></iframe>
 ```
 
 Supported URL attributes are:
 
-- **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
-- **`height`** (default `640`)
-- **`width`** (default `640`)
-- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  - **`crop`** cut parts of the video that doesn't fit in the given size
-  - **`clip`** preserve the entire frame and decrease the size of the image within given size
-  - **`scale`** distort the image to fit the given size
-  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+* **`time`** (default `0s`, configurable) time from the video for example `8m`, `5m2s`
+* **`height`** (default `640`)
+* **`width`** (default `640`)
+* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  * **`crop`** cut parts of the video that doesn't fit in the given size
+  * **`clip`** preserve the entire frame and decrease the size of the image within given size
+  * **`scale`** distort the image to fit the given size
+  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
 
 ## Use Case 2: Set the default thumbnail timestamp using the API
 
@@ -68,20 +67,17 @@ Stream supports animated GIFs as thumbnails. Viewing animated thumbnails does no
 
 ` https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s`
 
-<img
-	src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s"
-	alt="Animated gif example, generated on-demand from Cloudflare Stream"
-/>
+<img src="https://customer-f33zs165nr7gyfy4.cloudflarestream.com/6b9e68b07dfee8cc2d116e4c51d6a957/thumbnails/thumbnail.gif?time=1s&height=200&duration=4s" alt="Animated gif example, generated on-demand from Cloudflare Stream" />
 
 Supported URL attributes for animated thumbnails are:
 
-- **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
-- **`height`** (default `640`)
-- **`width`** (default `640`)
-- **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
-  - **`crop`** cut parts of the video that doesn't fit in the given size
-  - **`clip`** preserve the entire frame and decrease the size of the image within given size
-  - **`scale`** distort the image to fit the given size
-  - **`fill`** preserve the entire frame and fill the rest of the requested size with black background
-- **`duration`** (default `5s`)
-- **`fps`** (default `8`)
+* **`time`** (default `0s`) time from the video for example `8m`, `5m2s`
+* **`height`** (default `640`)
+* **`width`** (default `640`)
+* **`fit`** (default `crop`) to clarify what to do when requested height and width does not match the original upload, which should be one of:
+  * **`crop`** cut parts of the video that doesn't fit in the given size
+  * **`clip`** preserve the entire frame and decrease the size of the image within given size
+  * **`scale`** distort the image to fit the given size
+  * **`fill`** preserve the entire frame and fill the rest of the requested size with black background
+* **`duration`** (default `5s`)
+* **`fps`** (default `8`)
diff --git a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
index 979b5f8d99e2f35..0ae5a7967717599 100644
--- a/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
+++ b/src/content/docs/stream/viewing-videos/using-the-stream-player/using-the-player-api.mdx
@@ -15,103 +15,134 @@ To use this SDK, add an additional `<script>` tag to your website:
 ```html
 <!-- You can use styles and CSS on this iframe element where the video player will appear -->
 <iframe
-	src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
-	style="border: none"
-	height="720"
-	width="1280"
-	allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-	allowfullscreen="true"
-	id="stream-player"
+  src="https://customer-<CODE>.cloudflarestream.com/<VIDEO_UID>/iframe"
+  style="border: none"
+  height="720"
+  width="1280"
+  allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
+  allowfullscreen="true"
+  id="stream-player"
 ></iframe>
 
 <script src="https://embed.cloudflarestream.com/embed/sdk.latest.js"></script>
 
 <!-- Your JavaScript code below-->
 <script>
-	const player = Stream(document.getElementById("stream-player"));
-	player.addEventListener("play", () => {
-		console.log("playing!");
-	});
-	player.play().catch(() => {
-		console.log("playback failed, muting to try again");
-		player.muted = true;
-		player.play();
-	});
+  const player = Stream(document.getElementById('stream-player'));
+  player.addEventListener('play', () => {
+    console.log('playing!');
+  });
+  player.play().catch(() => {
+    console.log('playback failed, muting to try again');
+    player.muted = true;
+    player.play();
+  });
 </script>
 ```
 
 ## Methods
 
-- `play()` Promise
-  - Start video playback.
 
-- `pause()` null
-  - Pause video playback.
+
+* `play()` Promise
+
+  * Start video playback.
+
+* `pause()` null
+
+  * Pause video playback.
+
+
 
 ## Properties
 
-- `autoplay` boolean
-  - Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
+
+
+* `autoplay` boolean
+
+  * Sets or returns whether the autoplay attribute was set, allowing video playback to start upon load.
 
 :::note
 
+
 Some browsers prevent videos with audio from playing automatically. You may add the `mute` attribute to allow your videos to autoplay. For more information, review the [iOS video policies](https://webkit.org/blog/6784/new-video-policies-for-ios/).
 
+
 :::
 
-- `buffered` TimeRanges readonly
-  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+* `buffered` TimeRanges readonly
+
+  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-- `controls` boolean
-  - Sets or returns whether the video should display controls (like play/pause etc.)
+* `controls` boolean
 
-- `currentTime` integer
-  - Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+  * Sets or returns whether the video should display controls (like play/pause etc.)
 
-- `defaultTextTrack`
-  - Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
+* `currentTime` integer
+
+  * Returns the current playback time in seconds. Setting this value seeks the video to a new time.
+
+* `defaultTextTrack`
+
+  * Will initialize the player with the specified language code's text track enabled. The value should be the BCP-47 language code that was used to [upload the text track](/stream/edit-videos/adding-captions/). If the specified language code has no captions available, the player will behave as though no language code had been provided.
 
 :::note
 
-This will _only_ work once during initialization. Beyond that point the user has full control over their text track settings.
+
+This will *only* work once during initialization. Beyond that point the user has full control over their text track settings.
+
 
 :::
 
-- `duration` integer readonly
-  - Returns the duration of the video in seconds.
+* `duration` integer readonly
+
+  * Returns the duration of the video in seconds.
+
+* `ended` boolean readonly
+
+  * Returns whether the video has ended.
+
+* `letterboxColor` string
+
+  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
+
+* `loop` boolean
+
+  * Sets or returns whether the video should start over when it reaches the end
 
-- `ended` boolean readonly
-  - Returns whether the video has ended.
+* `muted` boolean
 
-- `letterboxColor` string
-  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to the letterboxing/pillarboxing of the player's UI. This can be set to `transparent` to avoid letterboxing/pillarboxing when not in fullscreen mode.
+  * Sets or returns whether the audio should be played with the video
 
-- `loop` boolean
-  - Sets or returns whether the video should start over when it reaches the end
+* `paused` boolean readonly
 
-- `muted` boolean
-  - Sets or returns whether the audio should be played with the video
+  * Returns whether the video is paused
 
-- `paused` boolean readonly
-  - Returns whether the video is paused
+* `played` TimeRanges readonly
 
-- `played` TimeRanges readonly
-  - An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
+  * An object conforming to the TimeRanges interface. This object is normalized, which means that ranges are ordered, don't overlap, aren't empty, and don't touch (adjacent ranges are folded into one bigger range).
 
-- `preload` boolean
-  - Sets or returns whether the video should be preloaded upon element load.
+* `preload` boolean
+
+  * Sets or returns whether the video should be preloaded upon element load.
 
 :::note
 
+
 The `<video>` element does not force the browser to follow the value of this attribute; it is a mere hint. Even though the `preload="none"` option is a valid HTML5 attribute, Stream player will always load some metadata to initialize the player. The amount of data loaded in this case is negligible.
 
+
 :::
 
-- `primaryColor` string
-  - Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
+* `primaryColor` string
+
+  * Any valid [CSS color value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value) provided will be applied to certain elements of the player's UI.
+
+* `volume` float
+
+  * Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
+
 
-- `volume` float
-  - Sets or returns volume from 0.0 (silent) to 1.0 (maximum value)
 
 ## Events
 
@@ -119,78 +150,109 @@ The `<video>` element does not force the browser to follow the value of this att
 
 We support most of the [standardized media element events](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events).
 
-- `abort`
-  - Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `canplay`
-  - Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `canplaythrough`
-  - Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
+* `abort`
 
-- `durationchange`
-  - The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
+  * Sent when playback is aborted; for example, if the media is playing and is restarted from the beginning, this event is sent.
 
-- `ended`
-  - Sent when playback completes.
+* `canplay`
 
-- `error`
-  - Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
+  * Sent when enough data is available that the media can be played, at least for a couple of frames.
 
-- `loadeddata`
-  - The first frame of the media has finished loading.
+* `canplaythrough`
 
-- `loadedmetadata`
-  - The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
+  * Sent when the entire media can be played without interruption, assuming the download rate remains at least at the current level. It will also be fired when playback is toggled between paused and playing. Note: Manually setting the currentTime will eventually fire a canplaythrough event in firefox. Other browsers might not fire this event.
 
-- `loadstart`
-  - Sent when loading of the media begins.
+* `durationchange`
 
-- `pause`
-  - Sent when the playback state is changed to paused (paused property is true).
+  * The metadata has loaded or changed, indicating a change in duration of the media. This is sent, for example, when the media has loaded enough that the duration is known.
 
-- `play`
-  - Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+* `ended`
 
-- `playing`
-  - Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+  * Sent when playback completes.
 
-- `progress`
-  - Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+* `error`
 
-- `ratechange`
-  - Sent when the playback speed changes.
+  * Sent when an error occurs. (e.g. the video has not finished encoding yet, or the video fails to load due to an incorrect signed URL)
 
-- `seeked`
-  - Sent when a seek operation completes.
+* `loadeddata`
 
-- `seeking`
-  - Sent when a seek operation begins.
+  * The first frame of the media has finished loading.
 
-- `stalled`
-  - Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+* `loadedmetadata`
 
-- `suspend`
-  - Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+  * The media's metadata has finished loading; all attributes now contain as much useful information as they're going to.
 
-- `timeupdate`
-  - The time indicated by the element's currentTime attribute has changed.
+* `loadstart`
+
+  * Sent when loading of the media begins.
+
+* `pause`
+
+  * Sent when the playback state is changed to paused (paused property is true).
+
+* `play`
+
+  * Sent when the playback state is no longer paused, as a result of the play method, or the autoplay attribute.
+
+* `playing`
+
+  * Sent when the media has enough data to start playing, after the play event, but also when recovering from being stalled, when looping media restarts, and after seeked, if it was playing before seeking.
+
+* `progress`
+
+  * Sent periodically to inform interested parties of progress downloading the media. Information about the current amount of the media that has been downloaded is available in the media element's buffered attribute.
+
+* `ratechange`
+
+  * Sent when the playback speed changes.
+
+* `seeked`
+
+  * Sent when a seek operation completes.
+
+* `seeking`
+
+  * Sent when a seek operation begins.
+
+* `stalled`
+
+  * Sent when the user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
+
+* `suspend`
+
+  * Sent when loading of the media is suspended; this may happen either because the download has completed or because it has been paused for any other reason.
+
+* `timeupdate`
+
+  * The time indicated by the element's currentTime attribute has changed.
+
+* `volumechange`
+
+  * Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
+
+* `waiting`
+
+  * Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
-- `volumechange`
-  - Sent when the audio volume changes (both when the volume is set and when the muted attribute is changed).
 
-- `waiting`
-  - Sent when the requested operation (such as playback) is delayed pending the completion of another operation (such as a seek).
 
 ### Non-standard Events
 
 Non-standard events are prefixed with `stream-` to distinguish them from standard events.
 
-- `stream-adstart`
-  - Fires when `ad-url` attribute is present and the ad begins playback
 
-- `stream-adend`
-  - Fires when `ad-url` attribute is present and the ad finishes playback
 
-- `stream-adtimeout`
-  - Fires when `ad-url` attribute is present and the ad took too long to load.
+* `stream-adstart`
+
+  * Fires when `ad-url` attribute is present and the ad begins playback
+
+* `stream-adend`
+
+  * Fires when `ad-url` attribute is present and the ad finishes playback
+
+* `stream-adtimeout`
+
+  * Fires when `ad-url` attribute is present and the ad took too long to load.
+
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
index e65a1289cbbf95e..4d5dded596a44eb 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/deprecated-apis.mdx
@@ -14,7 +14,7 @@ The purpose of Deprecated API content is to communicate that Cloudflare no longe
 
 instructional, straightforward
 
-## content_type
+## content\_type
 
 `reference`
 
@@ -24,7 +24,7 @@ instructional, straightforward
 
 **Deprecated endpoint name**: Must match what existed in the non-deprecated [Endpoint](/style-guide/api-content-strategy/api-content-types/endpoints/).
 
-**Context**: Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
+**Context**:  Brief description of what is happening, why Cloudflare is deprecating this endpoint, and any other important information. Avoid using time-bound descriptors (today, tomorrow, in one week, etc). Instead, be specific when including dates.
 
 **Replacement**: A description of and/or link to the alternative endpoint OR an explanation as to why Cloudflare is removing the capability of that endpoint.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
index 6529edfc70b1ed6..f73e8c33466bbfe 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/endpoints.mdx
@@ -18,19 +18,21 @@ An endpoint is used to make HTTPS requests, and the `GET`, `POST`, `PUT`, `PATCH
 
 :::note
 
+
 The required components apply to newly created endpoints. Existing endpoints will **not** be modified.
 
+
 :::
 
 **Title**: Title of the endpoint using sentence casing (first word capitalized). The titles do not use punctuation marks at the end of the title. Simple cases usually take one of the following forms:
 
 Endpoints that act on/return a single item: verb + indefinite article + singular resource name.
 
-- Example: Get a list item
+* Example: Get a list item
 
 Endpoints that act on/return a collection of items: verb + plural resource name.
 
-- Example: Get list items
+* Example: Get list items
 
 **Description**: Describes what the endpoint does or how it should be used. Use punctuation at the end of the description.
 
@@ -52,11 +54,11 @@ When writing the titles and descriptions, keep our voice and tone in mind. Be co
 
 Below are some examples of endpoint titles and descriptions for reference:
 
-- **Get domain**: Fetches a single domain.
-- **List workers**: Fetches a list of uploaded workers.
-- **List pools**: Lists configured pools.
-- **Create waiting room**: Creates a new waiting room.
-- **Update health check**: Updates configured health checks.
+* **Get domain**: Fetches a single domain.
+* **List workers**: Fetches a list of uploaded workers.
+* **List pools**: Lists configured pools.
+* **Create waiting room**: Creates a new waiting room.
+* **Update health check**: Updates configured health checks.
 
 ## Example
 
@@ -68,4 +70,4 @@ Below are some examples of endpoint titles and descriptions for reference:
 
 **Method**: `GET`
 
-**Endpoint**: user/audit_logs
+**Endpoint**: user/audit\_logs
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
index 59e3387e3c346d0..5b998bffe2e51f0 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
index aebb7c2e49d8230..a31e895ce8f45c1 100644
--- a/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/api-content-types/parameters.mdx
@@ -46,7 +46,7 @@ Below are some examples of parameter descriptions for reference:
 
 **version**: The Cloudflare One Client version.
 
-**per_page**: Sets the maximum number of requested results.
+**per\_page**: Sets the maximum number of requested results.
 
 **enabled**: Enables or disable a load balancer.
 
diff --git a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
index c24e2857250568e..26a17b8a4f34fc5 100644
--- a/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
+++ b/src/content/docs/style-guide/api-content-strategy/guidelines-for-curl-commands.mdx
@@ -21,9 +21,9 @@ To automatically incorporate our conventions into your examples, use:
 
 Use long parameter names for clarity:
 
-- `--header` (instead of `-H`)
-- `--request` (when needed, instead of `-X`)
-- `--data` (instead of `-d`)
+* `--header` (instead of `-H`)
+* `--request` (when needed, instead of `-X`)
+* `--data` (instead of `-d`)
 
 You do not need to use the `--url` parameter since it is the main cURL parameter. Also, the URL does not need to be enclosed in double quotes (`""`), except if it contains a `?` character (that is, when it includes a query string).
 
@@ -45,9 +45,9 @@ If you must suggest the use of this tool, you can add a link to the [Make API ca
 
 ### Preliminary notes
 
-- Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
-- Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
-- Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
+* Make sure not to use typographical or smart quotes in a cURL command, or the command will fail.
+* Placeholders in the URL should follow the same format as in the API documentation: `$ZONE_ID`
+* Placeholders in the request body (that is, the data included in a `POST`/`PUT`/`PATCH` request) should use [angle brackets](/style-guide/formatting/code-conventions-and-format/#angle-brackets---and--): `<RULE_ID>`
 
 The same placeholder name should correspond to the same value – use different placeholder names for different ID values. You can use the same request placeholders in the response, if they should match the values in the request.
 
@@ -149,7 +149,7 @@ Enclose the JSON payload ( the `--data` command-line argument) in single quotes
 
 The recommended way of escaping a single quote inside the body is the following (assuming the user will run the command in a bash-like terminal):
 
-- Replace the single quote `'` with `'\''`
+* Replace the single quote `'` with `'\''`
 
 Which means "close string, add escaped single quote, begin string again".
 
@@ -203,28 +203,28 @@ A response starts either with an object (`{ ... }`) or a list (`[ ... ]`). The i
 (}|])
 ```
 
-- If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
-- Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
+* If there are IDs that were obtained using a previous command, or if their exact value is not relevant in the current context, use a placeholder (for example, `<RULE_ID>`) instead of the ID. The same placeholder name should correspond to the same value. Use different placeholder names for different ID values.
+* Response excerpts or snippets containing the most relevant parts of the response body should mention that they do not correspond to the entire response.
 
 ### Full response example
 
 ```json
 {
-	"result": {
-		"id": "<RULE_ID>",
-		"paused": false,
-		"description": "do not challenge login from office",
-		"action": "allow",
-		"priority": null,
-		"filter": {
-			"id": "<FILTER_ID>",
-			"expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
-			"paused": false,
-			"description": "Login from office"
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "<RULE_ID>",
+    "paused": false,
+    "description": "do not challenge login from office",
+    "action": "allow",
+    "priority": null,
+    "filter": {
+      "id": "<FILTER_ID>",
+      "expression": "ip.src in {2400:cb00::/32 2803:f800::/32 2c0f:f248::/32 2a06:98c0::/29} and (http.request.uri.path ~ \"^.*/wp-login.php$\" or http.request.uri.path ~ \"^.*/xmlrpc.php$\")",
+      "paused": false,
+      "description": "Login from office"
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
diff --git a/src/content/docs/style-guide/components/anchor-heading.mdx b/src/content/docs/style-guide/components/anchor-heading.mdx
index 3a3195eb29ef0a3..22d6bd5d8b60e19 100644
--- a/src/content/docs/style-guide/components/anchor-heading.mdx
+++ b/src/content/docs/style-guide/components/anchor-heading.mdx
@@ -17,11 +17,7 @@ The `AnchorHeading` component defines headings. Specifically, `AnchorHeading` pe
 ```mdx live
 import { AnchorHeading } from "~/components";
 
-<AnchorHeading
-	title="How to use AnchorHeading"
-	slug="use-anchorheading"
-	depth={2}
-/>
+<AnchorHeading title="How to use AnchorHeading" slug="use-anchorheading" depth={2} />
 ```
 
 Markdown files (including partials) have this behavior by default, applied via rehype plugins. Therefore, the `AnchorHeading` component is usually only required when writing headings yourself inside components, or when working on non-markdown files.
@@ -29,8 +25,7 @@ Markdown files (including partials) have this behavior by default, applied via r
 To override the ID given to a heading within Markdown, add an MDX comment at the end of the line:
 
 ```mdx live
-## foo {/* bar */}
-
+## foo {/*bar*/}
 {/* HTML: <h2 id="bar">foo</h2> */}
 ```
 
@@ -38,4 +33,4 @@ To override the ID given to a heading within Markdown, add an MDX comment at the
 
 The `AnchorHeading` component emulates the behavior of the [`rehype-slug`](https://github.com/rehypejs/rehype-slug) and the [`rehype-autolink-headings`](https://github.com/rehypejs/rehype-autolink-headings). It adds an `id` based on the output of [`github-slugger`](https://github.com/Flet/github-slugger/) to the heading, as well as adding a button to copy a link to that particular heading.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/available-notifications.mdx b/src/content/docs/style-guide/components/available-notifications.mdx
index ef0ad606272bc27..52d9d0e9f2ec6d7 100644
--- a/src/content/docs/style-guide/components/available-notifications.mdx
+++ b/src/content/docs/style-guide/components/available-notifications.mdx
@@ -14,19 +14,14 @@ import { AvailableNotifications } from "~/components";
 
 <AvailableNotifications product="Traffic Monitoring" />
 <AvailableNotifications
-	product="dns"
-	notificationFilter="Secondary DNS all Primaries Failing"
+    product="dns"
+    notificationFilter="Secondary DNS all Primaries Failing"
 />
 ```
 
 ## Notifications
 
-import { Code } from "~/components";
-import glossary from "~/content/notifications/index.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/notifications/index.yaml?raw"
 
-<Code
-	title="/src/content/notifications/index.yaml"
-	code={glossary}
-	lang="yaml"
-	wrap={true}
-/>
+<Code title="/src/content/notifications/index.yaml" code={glossary} lang="yaml" wrap={true} />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/description.mdx b/src/content/docs/style-guide/components/description.mdx
index 75456e07bf8c711..4d91bb6f10f8f27 100644
--- a/src/content/docs/style-guide/components/description.mdx
+++ b/src/content/docs/style-guide/components/description.mdx
@@ -8,7 +8,9 @@ products:
 ---
 
 ```mdx live
-import { Description } from "~/components";
+import { Description } from "~/components"
 
-<Description>Hello, world!</Description>
-```
+<Description>
+    Hello, world!
+</Description>
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/example.mdx b/src/content/docs/style-guide/components/example.mdx
index 2d3de76617e19e9..eb0ba2069a80284 100644
--- a/src/content/docs/style-guide/components/example.mdx
+++ b/src/content/docs/style-guide/components/example.mdx
@@ -10,13 +10,17 @@ products:
 Use the `<Example>` component to add a box around some content. This can be useful when you want to demonstrate or showcase something without it being confused by the surrounding text.
 
 ```mdx live
-import { Example } from "~/components";
+import { Example } from "~/components"
 
-<Example>Hello, world!</Example>
+<Example>
+    Hello, world!
+</Example>
 
-{/_
-`title` is an optional string which customizes the title of your example card
-_/}
+{/*
+    `title` is an optional string which customizes the title of your example card
+*/}
 
-<Example title="Hello world">Hello, world!</Example>
-```
+<Example title="Hello world">
+    Hello, world!
+</Example>
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/feature-table.mdx b/src/content/docs/style-guide/components/feature-table.mdx
index c839be1febca17e..7018dd906b70056 100644
--- a/src/content/docs/style-guide/components/feature-table.mdx
+++ b/src/content/docs/style-guide/components/feature-table.mdx
@@ -14,7 +14,7 @@ If the feature information includes an `Availability` row and you would like to
 This component pulls information from the `index.json` file in `src/content/plans/`.
 
 ```mdx live
-import { FeatureTable } from "~/components";
+import { FeatureTable } from "~/components"
 
 <FeatureTable id="analytics.logpush" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/feature.mdx b/src/content/docs/style-guide/components/feature.mdx
index 1b795ccb977fbf1..ce6073fbff74c41 100644
--- a/src/content/docs/style-guide/components/feature.mdx
+++ b/src/content/docs/style-guide/components/feature.mdx
@@ -12,15 +12,15 @@ The `<Feature>` component lists features available in the product and provides a
 The header parameter supplies the feature name and the href parameter supplies the link to the feature. Text wrapped in the component supplies the description.
 
 ```mdx
-import { Feature } from "~/components";
+import { Feature } from "~/components"
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-	Hello, world!
+   Hello, world!
 </Feature>
 ```
 
-import { Feature } from "~/components";
+import { Feature } from "~/components"
 
 <Feature header="Astro" href="/style-guide/components/feature/">
-	Hello, world!
+   Hello, world!
 </Feature>
diff --git a/src/content/docs/style-guide/components/glossary-definition.mdx b/src/content/docs/style-guide/components/glossary-definition.mdx
index 7a95c0d7c2a7584..379a96198932f4f 100644
--- a/src/content/docs/style-guide/components/glossary-definition.mdx
+++ b/src/content/docs/style-guide/components/glossary-definition.mdx
@@ -12,18 +12,14 @@ Use the this component to add extra information to an existing glossary entry. `
 ## Component
 
 ```mdx live
-import { GlossaryDefinition } from "~/components";
+import { GlossaryDefinition } from "~/components"
 
 <GlossaryDefinition term="example" prepend="The definition for example is: " />
 ```
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
 
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/glossary-tooltip.mdx b/src/content/docs/style-guide/components/glossary-tooltip.mdx
index 8f0e06da3c09d3d..0efadd82370ed12 100644
--- a/src/content/docs/style-guide/components/glossary-tooltip.mdx
+++ b/src/content/docs/style-guide/components/glossary-tooltip.mdx
@@ -22,11 +22,7 @@ import { GlossaryTooltip } from "~/components"
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
-
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
+
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/glossary.mdx b/src/content/docs/style-guide/components/glossary.mdx
index df05ad6c06dab82..1bf06744eadfba7 100644
--- a/src/content/docs/style-guide/components/glossary.mdx
+++ b/src/content/docs/style-guide/components/glossary.mdx
@@ -14,18 +14,14 @@ Create the glossary entries in a file dedicated to your product. These YAML file
 ## Component
 
 ```mdx live
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 <Glossary />
 ```
 
 ## Glossary
 
-import { Code } from "~/components";
-import glossary from "~/content/glossary/style-guide.yaml?raw";
+import { Code } from "~/components"
+import glossary from "~/content/glossary/style-guide.yaml?raw"
 
-<Code
-	title="/src/content/glossary/style-guide.yaml"
-	code={glossary}
-	lang="yaml"
-/>
+<Code title="/src/content/glossary/style-guide.yaml" code={glossary} lang="yaml" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/inline-badge.mdx b/src/content/docs/style-guide/components/inline-badge.mdx
index 6e49dc901618e2c..b0c325af0bf4068 100644
--- a/src/content/docs/style-guide/components/inline-badge.mdx
+++ b/src/content/docs/style-guide/components/inline-badge.mdx
@@ -12,18 +12,17 @@ products:
 Our current recommendation is to avoid inline badges, since they may hurt readability.
 
 Guidelines:
-
 - Mention beta/alpha/early access in the feature's main documentation page (use the [`<Badge>`](/style-guide/components/badges/) component for this purpose).
 - If an additional reference is needed in the middle of the text, use "(beta)", with no special formatting, after the feature name.
 - For instructions related to the feature (such as instructions on turning the feature on or off), you may mention again it's in beta, and also include "(beta)" in the side nav.
-  :::
+:::
 
 ## Component
 
 To adopt this styling in a React component, apply the `sl-badge` class to a `span` element.
 
 ```mdx live
-import { InlineBadge } from "~/components";
+import { InlineBadge } from '~/components';
 
 ### Alpha <InlineBadge preset="alpha" />
 
@@ -45,24 +44,24 @@ Either `preset` or `text` and `variant` must be specified.
 ### Presets
 
 - `alpha`
-  - **Text**: `Alpha`
-  - **Variant** `success`
+    - **Text**: `Alpha`
+    - **Variant** `success`
 
 - `beta`
-  - **Text**: `Beta`
-  - **Variant** `caution`
+    - **Text**: `Beta`
+    - **Variant** `caution`
 
 - `deprecated`
-  - **Text**: `Deprecated`
-  - **Variant** `danger`
+    - **Text**: `Deprecated`
+    - **Variant** `danger`
 
 - `early-access`
-  - **Text**: `Early Access`
-  - **Variant** `note`
+    - **Text**: `Early Access`
+    - **Variant** `note`
 
 - `legacy`
-  - **Text**: `Legacy`
-  - **Variant** `danger`
+    - **Text**: `Legacy`
+    - **Variant** `danger`
 
 ### Text
 
@@ -71,16 +70,16 @@ Any string.
 ### Variant
 
 - `note`
-  - **Color**: Blue
+    - **Color**: Blue
 
 - `tip`
-  - **Color**: Purple
+    - **Color**: Purple
 
 - `danger`
-  - **Color**: Red
+    - **Color**: Red
 
 - `caution`
-  - **Color**: Orange
+    - **Color**: Orange
 
 - `success`
-  - **Color**: Green
+    - **Color**: Green
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/link-cards.mdx b/src/content/docs/style-guide/components/link-cards.mdx
index 0adc8e6059e72d6..da6aaeafc9831a0 100644
--- a/src/content/docs/style-guide/components/link-cards.mdx
+++ b/src/content/docs/style-guide/components/link-cards.mdx
@@ -8,21 +8,21 @@ products:
 ---
 
 ```mdx live wrap
-import { CardGrid, LinkCard } from "~/components";
+import { CardGrid, LinkCard } from "~/components"
 
 <LinkCard
-	title="foo"
-	description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-	href="/style-guide/components/link-cards/"
+    title="foo"
+    description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+    href="/style-guide/components/link-cards/"
 />
 
 <CardGrid>
-	{[...Array(4).keys()].map(() => (
-		<LinkCard
-			title="foo"
-			description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
-			href="/style-guide/components/link-cards/"
-		/>
-	))}
+{[...Array(4).keys()].map(() => (
+    <LinkCard
+        title="foo"
+        description="Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam bibendum nulla et accumsan sodales."
+        href="/style-guide/components/link-cards/"
+    />
+))}
 </CardGrid>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/list-tutorials.mdx b/src/content/docs/style-guide/components/list-tutorials.mdx
index c67b80ab5057fa1..c225a6b23e4a78c 100644
--- a/src/content/docs/style-guide/components/list-tutorials.mdx
+++ b/src/content/docs/style-guide/components/list-tutorials.mdx
@@ -15,4 +15,4 @@ import { ListTutorials } from "~/components";
 
 ## Associated content types
 
-- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
+- [Tutorial](/style-guide/documentation-content-strategy/content-types/tutorial/)
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/package-managers.mdx b/src/content/docs/style-guide/components/package-managers.mdx
index 4c5f8298b9152d9..7b9c3137bd4b3b3 100644
--- a/src/content/docs/style-guide/components/package-managers.mdx
+++ b/src/content/docs/style-guide/components/package-managers.mdx
@@ -10,7 +10,7 @@ products:
 This component is provided by the [`starlight-package-managers` package.](https://github.com/HiDeoo/starlight-package-managers)
 
 ```mdx live
-import { PackageManagers } from "~/components";
+import { PackageManagers } from "~/components"
 
 <PackageManagers pkg="wrangler" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/pages-build-preset.mdx b/src/content/docs/style-guide/components/pages-build-preset.mdx
index 3480c8339307db2..976dc1433f725e5 100644
--- a/src/content/docs/style-guide/components/pages-build-preset.mdx
+++ b/src/content/docs/style-guide/components/pages-build-preset.mdx
@@ -8,8 +8,8 @@ products:
 ---
 
 ```mdx live
-import { PagesBuildPreset } from "~/components";
+import { PagesBuildPreset } from "~/components"
 
 <PagesBuildPreset framework="gatsby" />
 <PagesBuildPreset framework="next-js" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/plan.mdx b/src/content/docs/style-guide/components/plan.mdx
index 1b1457fa37ceb98..07b591b1274a686 100644
--- a/src/content/docs/style-guide/components/plan.mdx
+++ b/src/content/docs/style-guide/components/plan.mdx
@@ -14,8 +14,9 @@ To specify a special feature use `<Plan id="<FIRST_PRODUCT>.<SECOND-PRODUCT>.pro
 
 Refer to the examples below for more information.
 
+
 ```mdx live
-import { Plan } from "~/components";
+import { Plan } from "~/components"
 
 <Plan type="all" />
 <Plan type="paid" />
@@ -26,4 +27,4 @@ import { Plan } from "~/components";
 <Plan type="workers-all" />
 <Plan type="workers-paid" />
 <Plan id="web3.ethereum.properties.availability.summary" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/product-availability-text.mdx b/src/content/docs/style-guide/components/product-availability-text.mdx
index 77e2bca0cf78b1d..83689f8bbba4207 100644
--- a/src/content/docs/style-guide/components/product-availability-text.mdx
+++ b/src/content/docs/style-guide/components/product-availability-text.mdx
@@ -19,10 +19,10 @@ Cloud Connector <ProductAvailabilityText product="cloud-connector" /> allows you
 
 ## Props
 
-| Prop          | Type     | Required | Default  | Description                                                                                                |
-| ------------- | -------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------- |
-| `product`     | `string` | Yes      | —        | Product slug matching a file in `src/content/directory/`.                                                  |
-| `parentheses` | `string` | No       | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `product` | `string` | Yes | — | Product slug matching a file in `src/content/directory/`. |
+| `parentheses` | `string` | No | `"true"` | When `"true"`, wraps the output in parentheses (for example, `(Beta)`). Set to `"false"` for the raw text. |
 
 ## Behavior
 
diff --git a/src/content/docs/style-guide/components/product-features.mdx b/src/content/docs/style-guide/components/product-features.mdx
index bea56b72ab74c5e..199e0ded2498a76 100644
--- a/src/content/docs/style-guide/components/product-features.mdx
+++ b/src/content/docs/style-guide/components/product-features.mdx
@@ -10,7 +10,6 @@ products:
 Use when you need to list all available features within a product grouping inside of the `index.json` file in `src/content/plans/`. For the id property, specify the product object you want to use.
 
 ```mdx live
-import { ProductFeatures } from "~/components";
+import { ProductFeatures } from "~/components"
 
-<ProductFeatures id="dns" />
-```
+<ProductFeatures id="dns" />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/related-product.mdx b/src/content/docs/style-guide/components/related-product.mdx
index 99c45329075a2a1..8de8d8c11cdca07 100644
--- a/src/content/docs/style-guide/components/related-product.mdx
+++ b/src/content/docs/style-guide/components/related-product.mdx
@@ -17,11 +17,10 @@ Use in Overview pages.
 import { RelatedProduct } from "~/components";
 
 <RelatedProduct header="R2" href="/r2/" product="r2">
-	Store large amounts of unstructured data without the costly egress bandwidth
-	fees associated with typical cloud storage services.
+    Store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.
 </RelatedProduct>
 
 <RelatedProduct header="Images" href="/images/" product="images">
-	A suite of products tailored to your image-processing needs.
+    A suite of products tailored to your image-processing needs.
 </RelatedProduct>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/rule-id.mdx b/src/content/docs/style-guide/components/rule-id.mdx
index f5b213de131b2bc..d2a33c41ef0ebd7 100644
--- a/src/content/docs/style-guide/components/rule-id.mdx
+++ b/src/content/docs/style-guide/components/rule-id.mdx
@@ -8,7 +8,7 @@ products:
 ---
 
 ```mdx live
-import { RuleID } from "~/components";
+import { RuleID } from "~/components"
 
 <RuleID id="abcdefghijklmnopqrstuvwxyz" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/steps.mdx b/src/content/docs/style-guide/components/steps.mdx
index a8ad45e2b122573..26b09c984dee440 100644
--- a/src/content/docs/style-guide/components/steps.mdx
+++ b/src/content/docs/style-guide/components/steps.mdx
@@ -15,4 +15,4 @@ import { Steps } from "~/components"
 2. Wrap your numbered list in the `Steps` components
 3. Done!
 </Steps>
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
index 7208cf19466a58c..824d45bb57c3001 100644
--- a/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
+++ b/src/content/docs/style-guide/components/subtract-ip-calculator.mdx
@@ -40,7 +40,7 @@ An optional object containing `base` (`string`) and `subtract` (`string[]`) prop
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
 	}}
 />
 
@@ -51,7 +51,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 	client:load
 	defaults={{
 		base: "10.0.0.0/8",
-		subtract: ["10.0.0.0/24", "10.32.0.0/11"],
+		subtract: ["10.0.0.0/24", "10.32.0.0/11"]
 	}}
 />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/type-highlighting.mdx b/src/content/docs/style-guide/components/type-highlighting.mdx
index 26f7c06002aa2bb..a95852acfc7dc55 100644
--- a/src/content/docs/style-guide/components/type-highlighting.mdx
+++ b/src/content/docs/style-guide/components/type-highlighting.mdx
@@ -32,4 +32,4 @@ import { Type, MetaInfo } from "~/components";
   - The name of your service.
 - `local` <Type text="boolean" /> <MetaInfo text="(default: true) optional" />
   - If the service should run locally or not.
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/usage.mdx b/src/content/docs/style-guide/components/usage.mdx
index b1548e52b571c45..337c49995287617 100644
--- a/src/content/docs/style-guide/components/usage.mdx
+++ b/src/content/docs/style-guide/components/usage.mdx
@@ -11,4 +11,4 @@ import { ComponentsUsage } from "~/components";
 
 This page contains a breakdown of each component and the pages where they are used.
 
-<ComponentsUsage />
+<ComponentsUsage />
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/wrangler-namespace.mdx b/src/content/docs/style-guide/components/wrangler-namespace.mdx
index 6ebac49e56a3019..fab2bbf305de528 100644
--- a/src/content/docs/style-guide/components/wrangler-namespace.mdx
+++ b/src/content/docs/style-guide/components/wrangler-namespace.mdx
@@ -32,4 +32,4 @@ import { WranglerNamespace } from "~/components";
 - `namespace` <Type text="string" /> <MetaInfo text="required" />
   - The namespace to pull the related commands from (`d1`, `hyperdrive`).
 - `headingLevel` <Type text="boolean" /> <MetaInfo text="(default: 2) optional" />
-  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
+  - The heading level that the commands should be added at on the page, i.e `2` for `h2`.
\ No newline at end of file
diff --git a/src/content/docs/style-guide/components/youtube.mdx b/src/content/docs/style-guide/components/youtube.mdx
index b7dd62471b86ad2..8b24f0d71780445 100644
--- a/src/content/docs/style-guide/components/youtube.mdx
+++ b/src/content/docs/style-guide/components/youtube.mdx
@@ -7,12 +7,12 @@ products:
   - style-guide
 ---
 
-import { YouTube } from "~/components";
+import { YouTube } from "~/components"
 
 <YouTube id="XHvmX3FhTwU" />
 
 ```mdx
-import { YouTube } from "~/components";
+import { YouTube } from "~/components"
 
 <YouTube id="XHvmX3FhTwU" />
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/style-guide/contributions.mdx b/src/content/docs/style-guide/contributions.mdx
index 26f56188f64db34..5921a50b9de6eba 100644
--- a/src/content/docs/style-guide/contributions.mdx
+++ b/src/content/docs/style-guide/contributions.mdx
@@ -2,27 +2,23 @@
 title: Contributions
 description: Learn how to contribute to the Cloudflare Docs.
 sidebar:
-  order: 1
+    order: 1
 products:
   - style-guide
 ---
-
 import { Details } from "~/components";
 
 The [Cloudflare Docs](https://developers.cloudflare.com/) are open source and hosted on the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs) on GitHub. This means that anyone, including those who are not part of the Cloudflare organization, can contribute to them. We welcome all suggestions that help keep our docs high quality and up to date.
 
 To contribute to our docs, you will need to [create an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) (if you do not have one already) and log in. Then you have three options:
-
-- [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
-- [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
-- [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
+* [GitHub issue](#create-a-github-issue): Quickly submit a general suggestion.
+* [Quick edit (edit button)](#quick-edit): Quickly create a pull request. This is best if you want to edit a single page in your web browser and do not need to preview your changes.
+* [Full development](#full-development): Create a pull request. This is best if you want to edit multiple pages and preview your changes. This can be done in your web browser (with [Codespaces](https://docs.github.com/codespaces)) or on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)).
 
 In addition to using the [Cloudflare Style Guide](/style-guide/) for guidance on grammar and style, we recommend browsing our [components](/style-guide/components/) to add additional formatting such as buttons, tabs, and collapsible sections.
 
 ## Create a GitHub issue
-
 To create a GitHub issue:
-
 1. [Log in to GitHub](https://github.com/login) and go to the [cloudflare-docs repository](https://github.com/cloudflare/cloudflare-docs).
 2. Select **Issues** and then **New issue**.
 3. Select the issue type, fill out the form, and select **Create**.
@@ -30,63 +26,53 @@ To create a GitHub issue:
 [Learn more about creating GitHub issues.](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue)
 
 ## Quick edit
-
 To quickly create a pull request using the edit button:
-
 1. [Log in to GitHub](https://github.com/login).
 2. Go to the page you want to edit in the [Cloudflare Docs](https://developers.cloudflare.com/)
 3. Select <Details header="**Edit** or **Edit page**">Every page in the Cloudflare Docs (including this one) has an **Edit** button on the right sidebar and an **Edit page** button on the very bottom of the page.
-   ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
-   The page's Markdown opens.
-   :::note
-   The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
-   :::
+ ![Edit icon](~/assets/images/style-guide/ui-elements/edit.png)</Details>
+The page's Markdown opens.
+	:::note
+	The first time you create a pull request in the cloudflare-docs repo, you will see a GitHub landing page that says "You need to fork this repository to propose changes." Select **Fork this repository**. All of your future pull requests for cloudflare-docs will write to a new branch on your fork.
+	:::
 4. Make your edits and select **Commit changes**.
 5. In the form, update the **Commit message** with the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 6. Update the **Extended description** with more details about what you changed and why. The more details, the better.
 7. Select **Propose changes** > **Create pull request** > **Create pull request** again.
 
 ## Full development
-
 To edit and create a pull request with the [full development workflow](https://docs.github.com/en/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace):
-
 1. [Log in to GitHub](https://github.com/login) and [fork the cloudflare-docs repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
 2. If you are editing in your web browser (with [Codespaces](https://docs.github.com/en/codespaces)), move on to step 3.
-   <br />
-   If you are editing on your local machine (with [Visual Studio
-   Code](https://code.visualstudio.com/)): * (Required) Install
-   [Node.js](https://nodejs.org/en) (version 24 or later). * (Recommended, but
-   not required) Install [Volta](https://volta.sh/) for easier package
-   management. * (Required) [Clone the fork to your local
-   machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
+<br/>If you are editing on your local machine (with [Visual Studio Code](https://code.visualstudio.com/)):
+	* (Required) Install [Node.js](https://nodejs.org/en) (version 24 or later).
+	* (Recommended, but not required) Install [Volta](https://volta.sh/) for easier package management.
+	* (Required) [Clone the fork to your local machine.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
 3. Create a branch from your fork (or from your clone).
-4. Make your edits.
-   :::note[Preview your edits]
-   To preview your edits, you need to install `pnpm`.
-
-```bash
-pnpm install
-```
-
+3. Make your edits.
+:::note[Preview your edits]
+To preview your edits, you need to install `pnpm`.
+ ```bash
+ pnpm install
+ ```
 Then, run `pnpm run dev`.
-
-```bash
-pnpm run dev
-```
-
+ ```bash
+ pnpm run dev
+ ```
 A link will appear in the terminal, `https://localhost:1111/`, where you can preview your edits. This link automatically updates with any new edits you make.
-::: 5. Commit your changes. 6. Push your commits to your branch and then back to your fork. 7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
+:::
+5. Commit your changes.
+6. Push your commits to your branch and then back to your fork.
+7. Return to GitHub and create a pull request from your committed changes. In the description form, add the product you changed in brackets and a brief description of your changes. For example “[Images] Fixed broken link."
 
 ## After you create an issue or PR
-
 After you create an issue or PR, a member of the Cloudflare organization will review your suggestion. Here is what to expect:
-
-- A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
-- If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
-- If your changes are approved:
-  - For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
-  - For GitHub PRs, the Cloudflare member will merge your PR.
-- If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
+* A member of the Cloudflare organization may tag others for technical or content reviews or feedback.
+* If your suggestion requires more information, a member of the Cloudflare organization may comment with a follow-up or clarification question. If they add the `more-information-needed` tag, the issue or pull request will automatically close if you do not respond within 14 days.
+* If your changes are approved:
+	* For GitHub issues, a Cloudflare member might create and link a new pull request that addresses your request. When they merge the PR, they will also close your issue.
+	* For GitHub PRs, the Cloudflare member will merge your PR.
+* If your suggestion is not approved, the Cloudflare member will respond with the reasoning and close your issue or PR.
 
 Thank you for contributing to our open-source ecosystem and being a part of the Cloudflare community.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
index 38e5c2fa935864f..899c473a810e03e 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/dynamic-lists.mdx
@@ -18,9 +18,9 @@ When at all possible, Cloudflare seeks to avoid creating static representations
 
 Potential examples include:
 
-- Exhaustive listing of fields
-- Replicating API content in developer docs
-- Maintaining lists of potential options in the UI (i.e., Alert types)
-- Verified Bots
+* Exhaustive listing of fields
+* Replicating API content in developer docs
+* Maintaining lists of potential options in the UI (i.e., Alert types)
+* Verified Bots
 
 The preferred approach would be speak more generally to the categories or specific, high-value fields.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
index f02e3493fdef2c0..335031ce0afc95f 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/examples.mdx
@@ -12,12 +12,14 @@ A code sample or line of text that shows the specific structure of a request/res
 
 :::note
 
+
 If you are unsure about when to categorize something as an example or tutorial, remember:
 
 Examples are a component attribute and are typically a snippet of code a user might copy and paste to run a task. Examples should not have multiple steps. A tutorial might contain an example, but an example will not contain a tutorial.
 
 Tutorials are a content type, typically longer form, and contain multiple steps to help users connect products to real-world scenarios.
 
+
 :::
 
 ## Used in
@@ -34,9 +36,9 @@ Explain what the code sample does in a short sentence.
 
 These could include:
 
-- Example requests and responses
-- Example inputs and outputs
-- Field values for UI and/or API
+* Example requests and responses
+* Example inputs and outputs
+* Field values for UI and/or API
 
 ## Additional information
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
index d2ac5552b440a7c..eb6cc09d35a217d 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/glossary-entry.mdx
@@ -56,16 +56,21 @@ entries:
 Relevant values include the following:
 
 - `productName` string required
+
   - Core product associated with this file. Should always match the same formatting / styling used in `associated_products`.
 
 - `entries` object required
+
   - `term` string required
+
     - The glossary term itself.
 
   - `general_definition` string required
+
     - Definition of the term. Should be general enough to apply to multiple products. Should also start with a lowercase letter unless starting with a proper noun.
 
   - `associated_products` array optional
+
     - If the term is associated with other products. Any names used should correspond to the `productName` of that associated file.
 
 ### Usage
@@ -104,9 +109,11 @@ Is a quoted definition that comes from:
 Properties are:
 
 - `term` string required
+
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
+
   - Text to add before a definition.
 
 #### Glossary tooltip
@@ -122,12 +129,15 @@ Here's a <GlossaryTooltip term="active zone">tooltip</GlossaryTooltip> example.
 Properties are:
 
 - `term` string required
+
   - Should match a term within an existing glossary YAML file.
 
 - `prepend` string optional
+
   - Text to add before a definition.
 
 - `link` string optional
+
   - Wraps the inner text in a markdown link, similar to normal markdown formatting.
 
 Because of space limitations, the tooltip will always default to the short definition of a term, meaning the definition text before the first line break.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
index 6027b8e869f159d..0e75f19c6dc5e99 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
index c412e4ff4c12769..017decd9096ef80 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/intended-audience.mdx
@@ -28,15 +28,15 @@ This reference architecture is designed for IT or security professionals with so
 
 To build a stronger baseline understanding of Cloudflare, we recommend the following resources:
 
-- What is Cloudflare? | Website (5 minute read) or video (2 minutes)
-- Solution Brief: Cloudflare One (3 minute read)
-- Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
-- Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
+* What is Cloudflare? | Website (5 minute read) or video (2 minutes)
+* Solution Brief: Cloudflare One (3 minute read)
+* Whitepaper: Reference Architecture for Internet-Native Transformation (10 minute read)
+* Blog: Zero Trust, SASE, and SSE: foundational concepts for your next-generation network (14 minute read)
 
 Those who read this reference architecture will learn:
 
-- How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
-- How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
-- How to plan for deploying Cloudflare One
+* How Cloudflare One protects an organization’s employees, devices, applications, data, and networks
+* How Cloudflare One fits into your existing infrastructure, and how to approach migration to a SASE architecture
+* How to plan for deploying Cloudflare One
 
 While this document examines Cloudflare One at a technical level, it does not offer fine detail about every product in the platform. Instead, it looks at how all the services in Cloudflare One enable networking and network security to be consolidated on one architecture. Visit the developer documentation for further information specific to a product area or use case.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
index aa2c818fd681979..5935c28d4a85d09 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/links.mdx
@@ -44,15 +44,15 @@ Cross-links between related pages create a navigable knowledge graph. When an AI
 
 Every page with a `pcx_content_type` should include links to related pages in its **Related resources** section. Use the following table to determine which content types to link to from each page.
 
-| Content type    | Must link to                                                                 |
-| --------------- | ---------------------------------------------------------------------------- |
-| Concept         | Related how-to or get-started page; related reference page                   |
-| How-to          | Prerequisite concept page; relevant configuration page; troubleshooting page |
-| Get started     | Next-level how-to pages; product overview page                               |
-| Troubleshooting | Related how-to page; relevant configuration page                             |
-| Configuration   | Parent how-to or get-started page; relevant concept page                     |
-| Reference       | Related concept page; how-to pages that use the reference                    |
-| Tutorial        | Related product overview; prerequisite get-started page                      |
+| Content type | Must link to |
+| --- | --- |
+| Concept | Related how-to or get-started page; related reference page |
+| How-to | Prerequisite concept page; relevant configuration page; troubleshooting page |
+| Get started | Next-level how-to pages; product overview page |
+| Troubleshooting | Related how-to page; relevant configuration page |
+| Configuration | Parent how-to or get-started page; relevant concept page |
+| Reference | Related concept page; how-to pages that use the reference |
+| Tutorial | Related product overview; prerequisite get-started page |
 
 Links should be bidirectional. If a concept page links to a how-to, the how-to should link back to the concept page. This ensures that users (and AI systems) can traverse between pages in either direction.
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
index 6bd0cb8c746ca6e..7971b04fd461597 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/mathematical-operations.mdx
@@ -20,7 +20,7 @@ If an operation occurs inside of a code block, use the formatting associated wit
 
 ## Example
 
-| Correct             | Incorrect         |
-| ------------------- | ----------------- |
-| 25 / 30             | 25/30             |
+| Correct                       | Incorrect         |
+| ----------------------------- | ----------------- |
+| 25 / 30                       | 25/30             |
 | `𝑒(𝑎𝑃,𝑏𝑄)=𝑒(𝑃,𝑄)𝑎𝑏` | e(aP,bQ)=e(P,Q)ab |
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
index 365813c38ea3809..dd344888b67b5bd 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/next-steps.mdx
@@ -20,9 +20,9 @@ One to two sentences
 
 It should answer:
 
-- What happens now?
-- What was the end result of the procedure?
-- What do users do next?
+* What happens now?
+* What was the end result of the procedure?
+* What do users do next?
 
 ## Cross-linking
 
diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
index 59f4a527a66fde9..f17397285f578bf 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/notes-tips-warnings.mdx
@@ -52,7 +52,7 @@ Use a warning to alert a reader to behavior that could impact the security of a
 
 ## Recommendations
 
-- **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
-- **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
-- **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
-- **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
+* **An aside should not contain too much content**, since it breaks the normal text flow. For example, up to 3 paragraphs or bulleted lists up to 3 items. If you need to include more content, consider creating a documentation section "Important notes" or similar.
+* **Use asides sparingly.** Each section should not have more than one aside of the same type. The only exception is a possible availability disclaimer right after the heading.
+* **Asides inside task step instructions should not have a header.** They take too much space and the background color is enough to distinguish the aside content from regular text.
+* **Use a `note` aside to state the restricted availability of a feature** (for example, "Only available for customers on an Enterprise plan.") at the beginning of a page, without a header.
diff --git a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
index f696235502bd1f7..b0d981549ac0adf 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/information-architecture.mdx
@@ -14,10 +14,10 @@ The information architecture (IA) of the Cloudflare developer documentation foll
 
 At launch, Cloudflare Developer Platform products are recommended to include the following high-level sections. The following is a recommended guideline based on standard user journey flow (Learn, Get started, Configure, Test, Deploy, Asses, Maintain, etc.) and is intended to serve as a helpful reference to the documentation writer and collaborators. Depending on the product and as products mature, the IA may grow out of this structure or differ from this structure based on what you can do with the product. For an example of a more mature product that differs from this IA, refer to the [Cloudflare Stream documentation](/stream/).
 
-- [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
-- [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
-- [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
-- Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
-- [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
-- [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
-- Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
+* [Overview](/style-guide/documentation-content-strategy/content-types/overview/)
+* [Get started](/style-guide/documentation-content-strategy/content-types/get-started/)
+* [Configuration](/style-guide/documentation-content-strategy/content-types/configuration/) - Steps that come after getting started, including features (like Cron Triggers and Smart Placement for Workers) or the delta between getting started and your desired state. As a product matures, content in **Configuration** might expand into its own top-level sections.
+* Observability - Information about testing, metrics, analytics, local development, etc. Alternative title: **Testing & Observability**.
+* [Reference](/style-guide/documentation-content-strategy/content-types/reference/)
+* [Concepts](/style-guide/documentation-content-strategy/content-types/concept/)
+* Platform - Section unique to Developer Platform products that includes Pricing, Limits, Storage options, Changelog, Betas, and Known issues pages.
diff --git a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
index 5ec373d9988218e..1b38177313b1f44 100644
--- a/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
+++ b/src/content/docs/style-guide/formatting/code-conventions-and-format.mdx
@@ -80,9 +80,9 @@ In nested menus, use bold for the word not the symbol.
 
 Example: **Dashboard** > **This** > **That**
 
-## _Italics_
+## *Italics*
 
-Use _italics_ when referring to an option that customers can select from, like in dropdown menus.
+Use *italics* when referring to an option that customers can select from, like in dropdown menus.
 
 Do not use italics when referring to the state of a toggle - for example, enabled/disabled should not be italicized.
 
@@ -94,32 +94,32 @@ Text in this font denotes text or characters that you should enter from the keyb
 
 ### Examples of elements we monospace
 
-| Element                                                    | Example                                                                                                                                                                                      |
-| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                                                                                                         |
-| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                                                                                                                |
-| API commands                                               | The endpoint supports `GET` for JSON format.                                                                                                                                                 |
-| Terminal commands                                          | Run the command `wrangler login`.                                                                                                                                                            |
-| Attribute names and values                                 | `type`, `name`                                                                                                                                                                               |
-| Class names                                                | `button-primary`                                                                                                                                                                             |
-| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                                                                                                     |
-| Data types                                                 | (`string`, `number`, `int64`)                                                                                                                                                                |
-| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                                                                                                           |
-| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink. |
-| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                                                                                                    |
-| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                                                                                                           |
-| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                                                                                                       |
-| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                                                                                                            |
-| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                                                                                                              |
-| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                                                                                                        |
-| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx.                                                                                   |
-| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                                                                                                         |
-| HTTP header names                                          | `Content-Length`                                                                                                                                                                             |
-| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                                                                                                                 |
-| IAM role names                                             | `roles/storage.admin`                                                                                                                                                                        |
-| Language keywords                                          | `in`, `await`                                                                                                                                                                                |
-| Method and function names                                  | `handleRequest`                                                                                                                                                                              |
-| Namespace aliases                                          | `numpy`                                                                                                                                                                                      |
-| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                                                                                                           |
-| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                                                                                                       |
-| Text input                                                 | `"Hello Worker"`                                                                                                                                                                             |
+| Element                                                    | Example                                                                                                    |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| IP addresses and ranges                                    | Change your system + DNS servers to use `127.0.1.1`.                                                       |
+| Port numbers                                               | Requests are redirected through the HTTP service (port `80`).                                              |
+| API commands                                               | The endpoint supports `GET` for JSON format.                                                               |
+| Terminal commands                                          | Run the command `wrangler login`.                                                                          |
+| Attribute names and values                                 | `type`, `name`                                                                                             |
+| Class names                                                | `button-primary`                                                                                           |
+| Command-line utility names                                 | `wrangler`, `npm`, `node`, `cloudflared`                                                                   |
+| Data types                                                 | (`string`, `number`, `int64`)                                                                              |
+| Defined (constant) values for an element or attribute      | `<A_BINDING_NAME>`                                                                                         |
+| DNS record types                                           | The bot will default to looking for `AAAA` records. <br/>However, you may use regular formatting (for example, AAAA) if there are multiple inline occurrences or if the text is a hyperlink.  |
+| Enum (enumerator) names (depending on language)            | `type ContentTypeMapElem`                                                                                  |
+| Environment variable names                                 | `<A_BINDING_NAME>`                                                                                         |
+| Element names, including angle brackets (XML and HTML).    | `<div>`, `<form>`, `<input>`, `<code>`                                                                     |
+| Filenames, filename extensions (if used), and paths        | `wrangler.toml`, `wrangler.jsonc`                                                                        |
+| Folders and directories                                    | `~/Downloads/Cloudflare_CA.crt`                                                                            |
+| HTTP verbs                                                 | `POST`, `GET`, `HEAD`, `PUT`,`DELETE`                                                                      |
+| HTTP status codes                                          | `400`, `200`, `500`<br/>However, error ranges using `x` placeholders should not be monospaced: 5xx, 1xxxx. |
+| HTTP content-type values                                   | `text/html`, `application/javascript; charset=utf-8`                                                       |
+| HTTP header names                                          | `Content-Length`                                                                                           |
+| URLs that are used as input or output in commands and code | `VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com`                                               |
+| IAM role names                                             | `roles/storage.admin`                                                                                      |
+| Language keywords                                          | `in`, `await`                                                                                              |
+| Method and function names                                  | `handleRequest`                                                                                            |
+| Namespace aliases                                          | `numpy`                                                                                                    |
+| Placeholder variables                                      | `<YOUR_BUILD_DIR>`                                                                                         |
+| Query parameter names and values                           | `/api/v4/{account_id}`                                                                                     |
+| Text input                                                 | `"Hello Worker"`                                                                                           |
diff --git a/src/content/docs/style-guide/formatting/dates-and-times.mdx b/src/content/docs/style-guide/formatting/dates-and-times.mdx
index 70172f50376d6b5..ab9f427759fec31 100644
--- a/src/content/docs/style-guide/formatting/dates-and-times.mdx
+++ b/src/content/docs/style-guide/formatting/dates-and-times.mdx
@@ -10,9 +10,9 @@ products:
 
 To account for internationalization and inclusivity of all locales, use the ISO-8601 (YYYY-MM-DD hh:mm:ss) standard when writing dates and times as much as possible.
 
-In general, documentation should strive to represent universal truth, not
-something time-bound. This is why semgrep may flag uses of explicit dates
-or month names or years because often become out-of-date and not be
+In general, documentation should strive to represent universal truth, not 
+something time-bound. This is why semgrep may flag uses of explicit dates 
+or month names or years because often become out-of-date and not be 
 revised later.
 
 ## Blogs
diff --git a/src/content/docs/style-guide/formatting/external-references.mdx b/src/content/docs/style-guide/formatting/external-references.mdx
index 49120127e781b06..19253920fd68de6 100644
--- a/src/content/docs/style-guide/formatting/external-references.mdx
+++ b/src/content/docs/style-guide/formatting/external-references.mdx
@@ -11,9 +11,9 @@ When referencing external resources, ensure that you are linking to a trustworth
 
 For general websites, consider the following recommendations about the link text:
 
-- Use the website name if you are linking to the home page.
-- Use the page name if you are linking to a specific page.
-- Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
+* Use the website name if you are linking to the home page.
+* Use the page name if you are linking to a specific page.
+* Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
 When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
diff --git a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
index 7ef14947ec6845d..316c3540dcbba9d 100644
--- a/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
+++ b/src/content/docs/style-guide/formatting/file-types-and-extensions.mdx
@@ -8,8 +8,8 @@ products:
 
 You can refer both to file types and file extensions in documentation:
 
-- File types: Accepted file formats are JSON and YAML.
-- File extensions: Upload the `.txt` file to the dashboard.
+* File types: Accepted file formats are JSON and YAML.
+* File extensions: Upload the `.txt` file to the dashboard.
 
 When referring to a specific file type, always use regular text formatting, write the file type in uppercase, and avoid the initial dot (you are referring to the file type, not the file extension).
 
@@ -17,7 +17,7 @@ When referring to a specific extension, always monospace the file, include a dot
 
 Additional examples:
 
-- The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
-- Additionally, this plist can be wrapped in a `.mobileconfig` file.
-- If you would like to test how this feature works, here is a sample `.csv` file.
-- Concatenate the string to a text-based `.pem` file.
+* The accepted file formats are YAML (files with a `.yml` or `.yaml` file extension) and JSON (files with a `.json` file extension).
+* Additionally, this plist can be wrapped in a `.mobileconfig` file.
+* If you would like to test how this feature works, here is a sample `.csv` file.
+* Concatenate the string to a text-based `.pem` file.
diff --git a/src/content/docs/style-guide/formatting/index.mdx b/src/content/docs/style-guide/formatting/index.mdx
index 7ec4a59dacb722c..8c1d56e0c307810 100644
--- a/src/content/docs/style-guide/formatting/index.mdx
+++ b/src/content/docs/style-guide/formatting/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/keyboard-keys.mdx b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
index 9dad67aca460e95..d9faeed37a3cd77 100644
--- a/src/content/docs/style-guide/formatting/keyboard-keys.mdx
+++ b/src/content/docs/style-guide/formatting/keyboard-keys.mdx
@@ -14,20 +14,16 @@ products:
 ## Formatting keyboard shortcuts
 
 When telling readers what keyboard shortcuts to use to achieve a result:
-
 - Place the keyboard shortcut in between backticks (monospace formatting)
 - Use uppercase letters with the abbreviated version of the key (`CTRL` instead of `CONTROL`, `CMD` instead of `COMMAND`for example)
 - Wrap the complete keyboard shortcut in between backticks, including the plus sign:
-  - **Do**:
-
-  ```mdx
-  `CTRL + C`
-  ```
-
-  - **Don't**:
-
-  ```mdx
-  `CTRL` + `C`
-  ```
-
-- Do not use the old `<kbd></kbd>` component
+	- **Do**:
+	```mdx
+	`CTRL + C`
+	```
+
+	- **Don't**:
+	```mdx
+	`CTRL` + `C`
+	```
+- Do not use the old `<kbd></kbd>` component
\ No newline at end of file
diff --git a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
index 02c81845f3a290b..382bab58c8d7d78 100644
--- a/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
+++ b/src/content/docs/style-guide/formatting/notes-and-other-notation-types.mdx
@@ -9,7 +9,6 @@ products:
 When adding a note to a page, always use this special note formatting. There are three types of formatted notes: `note`, `caution`, and `tip`.
 
 Here is some additional information about notes:
-
 - The color of the note depends on the type of note: `note` is blue, `caution` is yellow, and `tip` is purple.
 - For every note type, the header text is optional.
 - All note types can contain text and additional formatting like lists, code blocks, and images.
diff --git a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
index 96a4801c772e1e3..5085765a1f2090b 100644
--- a/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
+++ b/src/content/docs/style-guide/formatting/numbers-and-units-of-measurement.mdx
@@ -10,26 +10,26 @@ products:
 
 In body text, spell out whole numbers from zero through nine.
 
-- Example: We have added three more servers.
+* Example: We have added three more servers.
 
 For numbers greater than or equal to 10, use digits.
 
-- Example: The message is 32 bytes long, \[...]
+* Example: The message is 32 bytes long, \[...]
 
 For analytics, display metrics with numerals.
 Use commas for numbers with more than 3 digits (no spaces). Note the differences in numerical punctuation for translation.
 
-- 300
-- 1,000
-- 7,465
+* 300
+* 1,000
+* 7,465
 
 ## Using k to indicate thousands
 
 Do not put a space between the number and k.
 
-Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for _kilobytes_.
+Add a noun to indicate what the number measures, and to make clear that you are not using k as an abbreviation for *kilobytes*.
 
-- Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
+* Example: On this plan, you are limited to 55k download operations and 20k upload operations per day.
 
 ## Units of measurement
 
@@ -45,14 +45,14 @@ Many CPU architectures either do not allow execution of the machine code, which
 
 In general, only abbreviate units of measurements when they modify specific quantities/numbers. When you need to abbreviate them:
 
-| ✅    | ❌     | Rationale                                              |
+| ✅     | ❌      | Rationale                                              |
 | ----- | ------ | ------------------------------------------------------ |
 | 10 m  | 10m    | Always include a space between the number and the unit |
 | 10 cm | 10 cms | Unit symbols should unaltered in the plural.           |
 
 **Always include a space between a numerical value and the corresponding unit of measurement.** Although both formats are widely used, the metric system standardized the use of a space before a unit of measurement and should be used as a guideline to keep content consistent and clear.
 
-| ✅                                               | ❌                                          | Rationale                                                                                                   |
+| ✅                                                | ❌                                           | Rationale                                                                                                   |
 | ------------------------------------------------ | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
 | 128 GB                                           | 128 gb, 128gb, 128GB                        | Units of measurement should always be capitalized and spaced out from their corresponding numerical values. |
 | This network has a capacity of over **30 Tbps.** | This network has a capacity of over 30Tbps. | Adding a space between ‘30’ and ‘Tbps’ makes this sentence easier to read.                                  |
diff --git a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
index 25c6ca97daeed00..e44f43ed36fdc50 100644
--- a/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
+++ b/src/content/docs/style-guide/formatting/product-name-and-pluralization.mdx
@@ -10,5 +10,5 @@ Product names should follow a noun-verb agreement such that the verb is singular
 
 Examples:
 
-- Cloudflare Pages enables/allows.
-- Cloudflare Workers executes/propagates.
+* Cloudflare Pages enables/allows.
+* Cloudflare Workers executes/propagates.
diff --git a/src/content/docs/style-guide/formatting/structure/index.mdx b/src/content/docs/style-guide/formatting/structure/index.mdx
index 3498fa8f873c716..e2f981f9d22a682 100644
--- a/src/content/docs/style-guide/formatting/structure/index.mdx
+++ b/src/content/docs/style-guide/formatting/structure/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/formatting/structure/lists.mdx b/src/content/docs/style-guide/formatting/structure/lists.mdx
index 35a60f4a49b706c..94571bd31ee8c27 100644
--- a/src/content/docs/style-guide/formatting/structure/lists.mdx
+++ b/src/content/docs/style-guide/formatting/structure/lists.mdx
@@ -8,15 +8,15 @@ products:
 
 There are three types of lists:
 
-- Bulleted lists for unordered items
-- Numbered lists for ordered items
-- Embedded lists for items within a sentence
+* Bulleted lists for unordered items
+* Numbered lists for ordered items
+* Embedded lists for items within a sentence
 
 Here are some tips when creating lists:
 
-- Keep list items parallel
-- Start numbered lists with a command (imperative verb)
-- Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
+* Keep list items parallel
+* Start numbered lists with a command (imperative verb)
+* Consistently punctuate by using appropriate sentence + punctuation within the list (periods for full sentences, etc.)
 
 ## Bullet points
 
@@ -25,37 +25,26 @@ Bullet points help the reader's eye focus on a list of important elements.
 However, as with any other aspect of writing, they should be used mindfully. Below is a list of when you should and should not resort to bullet points.
 
 <table>
-	<thead>
-		<tr>
-			<th>❌ Do not use bullet points</th>
-			<th>✅ Use bullet points</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>
-				To outline <b>processes</b> (prefer numbered lists)
-			</td>
-			<td>
-				To list <b>facts</b>
-			</td>
-		</tr>
-		<tr>
-			<td>
-				To explain your reasoning (it is a blog post, not a list of system
-				requirements)
-			</td>
-			<td>
-				To list <b>data</b>
-			</td>
-		</tr>
-		<tr>
-			<td>-</td>
-			<td>
-				To list <b>options</b>
-			</td>
-		</tr>
-	</tbody>
+  <thead>
+    <tr>
+        <th>❌ Do not use bullet points</th>
+        <th>✅ Use bullet points</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+        <td>To outline <b>processes</b> (prefer numbered lists)</td>
+        <td>To list <b>facts</b></td>
+    </tr>
+    <tr>
+        <td>To explain your reasoning (it is a blog post, not a list of system requirements)</td>
+        <td>To list <b>data</b></td>
+    </tr>
+    <tr>
+        <td>-</td>
+        <td>To list <b>options</b></td>
+    </tr>
+    </tbody>
 </table>
 
 ## Bulleted lists
@@ -66,8 +55,8 @@ Do not punctuate bullet points unless each item is a full sentence.
 
 If bullet point items are followed by a description, use a colon after the heading and capitalize the description. For example,
 
-- **Item 1**: Description 1
-- **Item 2**: Description 2
+* **Item 1**: Description 1
+* **Item 2**: Description 2
 
 For bullet points, try to stick to the "six-pack" rule: no more than six bullets, each made up of six words or less.
 
@@ -78,14 +67,14 @@ Refer to [The best way to use bullet points](https://thewritinghabit.blog/2016/0
 When you find yourself creating a list of bullet points, go through this checklist:
 
 1. Do all bullet points belong together?
-   - Check that all the elements in the list are logically connected.
+   * Check that all the elements in the list are logically connected.
 2. Do I have more three or more bullet points, but less than six?
-   - Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
+   * Readers get lost when reading long lists; at the same time, if you have less than three elements to list, is it necessary to use bullet points?
 3. Are all bullet points shorter than three lines of text?
-   - Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
+   * Bullet points should not be used as section headers. If you have excessively long bullet points, consider breaking up the list into several subsections.
 4. Is punctuation consistent?
-   - End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
+   * End all elements of a bulleted list with a period if each element is a full sentence; do not add any punctuation if you are just listing nouns or parameters.
 5. Do all bullet points start with the most important word we want the reader to remember?
-   - Make sure the "head" of your bullet point is not hiding after a long circumlocution.
+   * Make sure the "head" of your bullet point is not hiding after a long circumlocution.
 6. Do all bullet points start with the same part of speech?
-   - If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
+   * If your bullet points start with verbs, make sure all verbs are in the same mood/tense.
diff --git a/src/content/docs/style-guide/formatting/structure/tables.mdx b/src/content/docs/style-guide/formatting/structure/tables.mdx
index 7a79ef760d68e39..d43a5fa3787672b 100644
--- a/src/content/docs/style-guide/formatting/structure/tables.mdx
+++ b/src/content/docs/style-guide/formatting/structure/tables.mdx
@@ -12,14 +12,14 @@ Using tables to simplify content and data provides a comprehensive way to arrang
 
 Here are some tips when creating tables:
 
-- Label column headers.
-- Label row headers if appropriate.
-- Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
-- Avoid too much text.
-- Aim for parallelism within the column.
-- Keep tables as simple and as small as possible.
-- Sort rows in a logical order. If no logical order exists, use alphabetical order.
-- <Render file="table-guidelines" product="style-guide" />
+* Label column headers.
+* Label row headers if appropriate.
+* Avoid merged cells. When cells are merged, it impacts how a screen reader navigates the page.
+* Avoid too much text.
+* Aim for parallelism within the column.
+* Keep tables as simple and as small as possible.
+* Sort rows in a logical order. If no logical order exists, use alphabetical order.
+* <Render file="table-guidelines" product="style-guide" />
 
 ## Introductory sentences
 
@@ -29,25 +29,25 @@ When referring to a table, use a phrase like "the following table" or "the prece
 
 ## Column headings
 
-- Use sentence case.
-- Write concise headings that clearly describe the column content.
-- Do not end column headings with punctuation, including periods, ellipses, or colons.
-- Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
+* Use sentence case.
+* Write concise headings that clearly describe the column content.
+* Do not end column headings with punctuation, including periods, ellipses, or colons.
+* Use the `th` element for column headings in HTML tables. Include the `scope` attribute for accessibility.
 
 ```html
 <thead>
-	<tr>
-		<th scope="col">Name</th>
-		<th scope="col">Description</th>
-	</tr>
+  <tr>
+    <th scope="col">Name</th>
+    <th scope="col">Description</th>
+  </tr>
 </thead>
 ```
 
 ## Table placement
 
-- Place each table directly after the sentence that introduces it.
-- Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
-- If a table has footnotes, place them immediately after the table.
+* Place each table directly after the sentence that introduces it.
+* Do not place a table in the middle of a numbered procedure. Place the table immediately after the relevant step.
+* If a table has footnotes, place them immediately after the table.
 
 ## Table captions
 
@@ -62,9 +62,9 @@ In Markdown, place the caption as a bold line immediately before the table:
 ```markdown
 **Table 1.** Supported DNS record types
 
-| Type | Description                      |
-| ---- | -------------------------------- |
-| A    | Maps a domain to an IPv4 address |
+| Type | Description |
+| --- | --- |
+| A | Maps a domain to an IPv4 address |
 | AAAA | Maps a domain to an IPv6 address |
 ```
 
@@ -72,22 +72,19 @@ In HTML, use the `caption` element as the first child of the `table` element:
 
 ```html
 <table>
-	<caption>
-		<b>Table 1.</b>
-		Supported DNS record types
-	</caption>
-	<thead>
-		<tr>
-			<th scope="col">Type</th>
-			<th scope="col">Description</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>A</td>
-			<td>Maps a domain to an IPv4 address</td>
-		</tr>
-	</tbody>
+  <caption><b>Table 1.</b> Supported DNS record types</caption>
+  <thead>
+    <tr>
+      <th scope="col">Type</th>
+      <th scope="col">Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A</td>
+      <td>Maps a domain to an IPv4 address</td>
+    </tr>
+  </tbody>
 </table>
 ```
 
@@ -97,8 +94,8 @@ Tables display pieces of information that have some sort of relationship.
 
 Example:
 
-- Dates and descriptions, like a changelog
-- A list of products with attributes
+* Dates and descriptions, like a changelog
+* A list of products with attributes
 
 ## When not to use tables
 
@@ -142,7 +139,7 @@ The rendered output looks like this:
 | Syntax    | Description |    Test Text |
 | :-------- | :---------: | -----------: |
 | Header    |    Title    | Here is this |
-| Paragraph |    Text     |     And more |
+| Paragraph |     Text    |     And more |
 
 ## Formatting text in tables
 
diff --git a/src/content/docs/style-guide/frontmatter/sidebar.mdx b/src/content/docs/style-guide/frontmatter/sidebar.mdx
index b28d8a5f1d52ccb..ec8a552cab6f221 100644
--- a/src/content/docs/style-guide/frontmatter/sidebar.mdx
+++ b/src/content/docs/style-guide/frontmatter/sidebar.mdx
@@ -215,5 +215,5 @@ sidebar:
 
 ### Automatic "Beta" badges
 
-A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status.
-This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`.
+A "Beta" badge is automatically added to sidebar links and groups whose URL matches a directory entry with a "Beta" availability status. 
+This badge is **not** controlled by frontmatter — it is derived from the product availability data associated with the entry in `src/content/directory/`. 
diff --git a/src/content/docs/style-guide/grammar/index.mdx b/src/content/docs/style-guide/grammar/index.mdx
index c7d3f0ea3544cd9..d70d2ce818eea88 100644
--- a/src/content/docs/style-guide/grammar/index.mdx
+++ b/src/content/docs/style-guide/grammar/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
index bffb664c1bd3269..3241618b639da6b 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/abbreviations.mdx
@@ -6,7 +6,7 @@ products:
   - style-guide
 ---
 
-Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word _acronym_ to refer to both).
+Abbreviations include acronyms, initialisms, shortened words, and contractions (in most contexts, the technical distinction between acronyms and initialisms is not relevant; it is fine to use the word *acronym* to refer to both).
 
 ## Long and short versions of a word
 
@@ -16,7 +16,7 @@ The short versions of the words are not abbreviations, and if you use them, you
 
 If you are not sure whether a word is an abbreviation or just a short version of a longer word, here is a list of [common abbreviations](https://abbreviations.yourdictionary.com/articles/list-of-commonly-used-abbreviations.html). If that does not settle the issue, use the speaking test: if you speak the short version as a word ("This is a demo version of the product"), you can usually treat it as a word and not an abbreviation.
 
-If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer _applications_ on Cloudflare for Teams are not shortened to _apps_. Depending on the use case, application might be the preferred term, especially due to translation.
+If a standard term in the Cloudflare dashboard is the long version of a word, use that over the shorter version to maintain consistency and distinctions. For example, customer *applications* on Cloudflare for Teams are not shortened to *apps*. Depending on the use case, application might be the preferred term, especially due to translation.
 
 ## When to spell out a term
 
@@ -24,28 +24,28 @@ In general, when an abbreviation is likely to be unfamiliar to the audience, spe
 
 If the first mention of a term occurs in a heading or title, you can use the abbreviation and then spell out the abbreviation in the first paragraph that follows the heading or title.
 
-When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out _application programming interface_. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
+When deciding to spell out a term, consider your audience. If the majority of your audience is likely to recognize and understand the term, then you do not need to spell it out. For example, if you are writing documentation for developers that references an API, you do not need to spell out *application programming interface*. However, if you are explaining the general concept of an API to someone with no programming experience, spelling out the abbreviation can be helpful.
 
-In some cases, spelling out a term does not help the reader understand the term. For example, writing out _portable document format_ does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
+In some cases, spelling out a term does not help the reader understand the term. For example, writing out *portable document format* does not help the reader understand what a PDF document is. In those cases, do not spell out the term.
 
 The following abbreviations rarely need to be spelled out:
 
-- API
-- DVD
-- File formats such as PDF or XML
-- HTML
-- PC
-- RAM
-- REST
-- Units of measure such as MB or GB
-- URL
-- USB
+* API
+* DVD
+* File formats such as PDF or XML
+* HTML
+* PC
+* RAM
+* REST
+* Units of measure such as MB or GB
+* URL
+* USB
 
 ## Abbreviations not to use
 
 Prefer English terms over Latin abbreviations. Do not use i.e. or e.g. Instead, use **that is** or **for example**, respectively.
 
-One exception: avoid both _etc._ and _and so on_ wherever possible, but if you really need to use one, use _etc._ Always include the period, even if a comma follows immediately after.
+One exception: avoid both *etc.* and *and so on* wherever possible, but if you really need to use one, use *etc.* Always include the period, even if a comma follows immediately after.
 
 Do not use Internet slang abbreviations such as tl;dr, IMO, FYI, or others.
 
@@ -55,16 +55,16 @@ Use the most common form of a word. If the full spelled-out word is common and e
 
 Follow these guidelines:
 
-- Do not use periods with acronyms or initialisms.
-- Put a period at the end of a shortened word, except for date and time abbreviations.
-- If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
-- Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
+* Do not use periods with acronyms or initialisms.
+* Put a period at the end of a shortened word, except for date and time abbreviations.
+* If you write or say an abbreviation as a word (for example, app or sync), do not put a period after it.
+* Do not use a period with an abbreviation for the name of a country, US state, or the District of Columbia (DC).
 
 ## i.e. vs e.g.
 
 While similar, these two Latin abbreviations carry very different meanings.
 
-- **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
-  - The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
-- **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
-  - Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
+* **i.e.** stands for **id est**. Quite literally, it means "that is" (that = id, est = is). It can be replaced with "that is" or "in other words".
+  * The median compression ratio achieved by Gzip was 0.65% (**i.e.**, the page was reduced to 0.65% of its size).
+* **e.g.** stands for **exempli gratia**. Use this when introducing examples for something you have just mentioned. It can be replaced with "for example", or "like".
+  * Cloudflare products (**e.g.**, Zero Trust, Magic Transit, etc.) offer network security and reliability.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
index 3d4836341a01f1b..1b9979cc0ba573e 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/acronyms.mdx
@@ -6,10 +6,10 @@ products:
   - style-guide
 ---
 
-**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
+**Define new and unfamiliar terms.** Acronyms and abbreviations can have an adverse effect on clarity, voice, and SEO. When writing or editing, some  terms might be unfamiliar to some or all of the audience. When you spot a such an unfamiliar term, take one of the following tactics:
 
-- If the term already exists, link to a good existing explanation.
+* If the term already exists, link to a good existing explanation.
 
-- If your document is introducing the term, define the term.
+* If your document is introducing the term, define the term.
 
-- **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
+* **Do not use periods in acronyms.** Acronyms are usually pronounced as their own word (like “QUIC”); for that reason, we do not place periods  between each letter. Although initialisms are slightly different from acronyms — like “VPN” or “TLS,” they cannot be pronounced as their own word  — we format them in the same way as proper acronyms in order to maintain consistency throughout our written content.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
index ca1c548ad846c7e..fbbcad12c379e14 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/capitalization.mdx
@@ -10,7 +10,7 @@ products:
 
 Each product, service, and feature should be properly spelled and capitalized when used in any content, both to ensure consistency across all channels and to differentiate common performance and security technologies (for example: load balancing, bot management, and web application firewalls) from specific Cloudflare solutions (for example: Cloudflare Load Balancing, Cloudflare Bot Management, and Cloudflare Web Application Firewall).
 
-| ✅                                                                                                                                                          | ❌                                                                                                                                               | Rationale                                                                                                                                   |
+| ✅                                                                                                                                                           | ❌                                                                                                                                                | Rationale                                                                                                                                   |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | This interactive demo provides three different scenarios on how to utilize **Cloudflare Rate Limiting** to protect your endpoints from suspicious requests. | This interactive demo provides three different scenarios on how to utilize **rate limiting** to protect your endpoints from suspicious requests. | This demo is specific to a Cloudflare product (Cloudflare Rate Limiting), not a tutorial on utilizing generic rate limiting.                |
 | The **Cloudflare Web Application Firewall (WAF)** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.       | Our **web application firewall** sits on the same anycast network that powers our global CDN, HTTP/2, and web optimization features.             | Cloudflare Web Application Firewall (WAF) is a specific product we offer and should be capitalized and identified with the Cloudflare name. |
@@ -19,109 +19,75 @@ Each product, service, and feature should be properly spelled and capitalized wh
 
 **When to use Waiting Room capitalized and singular:**
 
-- Naming the product: _Waiting Room keeps wait times low by dynamically managing traffic._
-- Page title: _Access Waiting Room_
-- Preceded by “Cloudflare”: _Cloudflare Waiting Room allows organizations to…_
-- Preceding a feature name: _Waiting Room Event Scheduling_
+* Naming the product: *Waiting Room keeps wait times low by dynamically managing traffic.*
+* Page title: *Access Waiting Room*
+* Preceded by “Cloudflare”: *Cloudflare Waiting Room allows organizations to…*
+* Preceding a feature name: *Waiting Room Event Scheduling*
 
 **When to waiting room(s) lower-case and in singular or plural:**
 
-- Used as an object: _Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room._
-- Capitalize only the first word when at the beginning of a sentence: _Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated._
-- Capitalize only the first word when it is the title of a subsection: _### Waiting room template_
+* Used as an object: *Your waiting room will begin queueing all visitors and will not allow any visitors to the path protected by your waiting room.*
+* Capitalize only the first word when at the beginning of a sentence:  *Waiting rooms are enabled on all subpaths, meaning you might be sending more traffic to your waiting room than anticipated.*
+* Capitalize only the first word when it is the title of a subsection: *### Waiting room template*
 
 ## Common capitalization conventions
 
 <table>
-	<tr>
-		<th style="width:20%">✅</th>
-		<th style="width:20%">❌</th>
-		<th>Rationale</th>
-	</tr>
-	<tr>
-		<td>CAPTCHA, reCAPTCHA</td>
-		<td>Captcha, captcha, recaptcha, Recaptcha</td>
-		<td>
-			A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are
-			not bots.
-		</td>
-	</tr>
-	<tr>
-		<td>cloud</td>
-		<td>Cloud, "cloud"</td>
-		<td>
-			The <b>cloud</b> is a network of remote servers used to store and maintain
-			data.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>DDoS</td>
-		<td>ddos, DDOS</td>
-		<td>
-			A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a
-			targeted server.
-		</td>
-	</tr>
-	<tr>
-		<td>denial-of-service (DoS)</td>
-		<td>
-			denial of service, Denial-of-Service, Denial-Of-Service, Denial of
-			Service, dos, Dos, DOS
-		</td>
-		<td>
-			DDoS is a type of <b>DoS</b> attack.
-		</td>
-	</tr>
-	<tr>
-		<td>Enterprise, enterprise</td>
-		<td>ent, ENT</td>
-		<td>
-			Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or
-			a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise
-			customers are enterprise companies, but not all enterprises are Enterprise
-			customers.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>Internet</td>
-		<td>internet</td>
-		<td>
-			Disabling this option may cause all devices to lose <b>Internet</b>{" "}
-			connectivity.
-		</td>
-	</tr>
-	<tr>
-		<td>SSL</td>
-		<td>ssl</td>
-		<td>
-			<b>SSL</b> is an encryption-based Internet security protocol.
-		</td>
-	</tr>
-	<tr>
-		<td>TLS</td>
-		<td>tls</td>
-		<td>
-			<b>TLS</b> is a security protocol designed to facilitate privacy and data
-			security for communications over the Internet..
-		</td>
-	</tr>
-	<tr>
-		<td>WAF</td>
-		<td>waf</td>
-		<td>
-			<b>WAF</b> is a security system that helps protect web applications by
-			filtering and monitoring HTTP traffic between a web application and the
-			Internet.{" "}
-		</td>
-	</tr>
-	<tr>
-		<td>Zero Trust</td>
-		<td>zero trust</td>
-		<td>
-			<b>Cloudflare</b> Access is a Zero Trust solution that secures inbound
-			connections to your protected applications.
-		</td>
-	</tr>
+  <tr>
+    <th style="width:20%">✅</th>
+    <th style="width:20%">❌</th>
+    <th>Rationale</th>
+  </tr>
+  <tr>
+    <td>CAPTCHA, reCAPTCHA</td>
+    <td>Captcha, captcha, recaptcha, Recaptcha</td>
+    <td>A <b>CAPTCHA</b> is a puzzle used to challenge users and ensure they are not bots.</td>
+  </tr>
+  <tr>
+    <td>cloud</td>
+    <td>Cloud, "cloud"</td>
+    <td>The <b>cloud</b> is a network of remote servers used to store and maintain data. </td>
+  </tr>
+  <tr>
+    <td>DDoS</td>
+    <td>ddos, DDOS</td>
+    <td>A <b>DDoS</b> attack is a malicious attempt to disrupt normal traffic of a targeted server.</td>
+  </tr>
+  <tr>
+    <td>denial-of-service (DoS)</td>
+    <td>denial of service, Denial-of-Service, Denial-Of-Service, Denial of Service, dos, Dos, DOS</td>
+    <td>DDoS is a type of <b>DoS</b> attack.</td>
+  </tr>
+  <tr>
+    <td>Enterprise, enterprise</td>
+    <td>ent, ENT</td>
+    <td>Capitalized - Refers to the official Cloudflare <b>Enterprise</b> Plan or a customer on the <b>Enterprise</b> plan. Sentence-case - All Enterprise customers are enterprise companies, but not all enterprises are Enterprise customers. </td>
+  </tr>
+  <tr>
+    <td>Internet</td>
+    <td>internet</td>
+    <td>Disabling this option may cause all devices to lose <b>Internet</b> connectivity.</td>
+  </tr>
+  <tr>
+    <td>SSL</td>
+    <td>ssl</td>
+    <td><b>SSL</b> is an encryption-based Internet security protocol.</td>
+  </tr>
+  <tr>
+    <td>TLS</td>
+    <td>tls</td>
+    <td><b>TLS</b> is a security protocol designed to facilitate privacy and data security for communications over the Internet..</td>
+  </tr>
+  <tr>
+    <td>WAF</td>
+    <td>waf</td>
+    <td><b>WAF</b> is a security system that helps protect web applications by filtering and monitoring HTTP traffic between a web application and the Internet. </td>
+  </tr>
+  <tr>
+    <td>Zero Trust</td>
+    <td>zero trust</td>
+    <td><b>Cloudflare</b> Access is a Zero Trust solution that secures inbound connections to your protected applications.</td>
+  </tr>
 </table>
 
 ## Headings
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
index e7f8868af4430c8..1e61e8bfdd8ecf5 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/compound-words.mdx
@@ -11,34 +11,31 @@ products:
 Whitespace is used in our blog posts and product content. For the sake of consistency, follow these conventions when using them:
 
 <table>
-	<tr>
-		<th style="width:20%">✅</th>
-		<th style="width:20%">❌</th>
-		<th>Example</th>
-	</tr>
-	<tr>
-		<td>nameserver</td>
-		<td>name servers</td>
-		<td>Change your nameservers to Cloudflare's.</td>
-	</tr>
-	<tr>
-		<td>hostname</td>
-		<td>host name</td>
-		<td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
-	</tr>
-	<tr>
-		<td>data center</td>
-		<td>datacenter</td>
-		<td>
-			Cloudflare updates the new setting across all of our data centers around
-			the world.
-		</td>
-	</tr>
-	<tr>
-		<td>checkbox</td>
-		<td>check box</td>
-		<td>Select the Transfer lock checkbox before continuing the setup.</td>
-	</tr>
+  <tr>
+    <th style="width:20%">✅</th>
+    <th style="width:20%">❌</th>
+    <th>Example</th>
+  </tr>
+  <tr>
+    <td>nameserver</td>
+    <td>name servers</td>
+    <td>Change your nameservers to Cloudflare's.</td>
+  </tr>
+  <tr>
+    <td>hostname</td>
+    <td>host name</td>
+    <td>Add a *. SAN (wildcard) to the custom hostname certificate.</td>
+  </tr>
+  <tr>
+    <td>data center</td>
+    <td>datacenter</td>
+    <td>Cloudflare updates the new setting across all of our data centers around the world.</td>
+  </tr>
+  <tr>
+    <td>checkbox</td>
+    <td>check box</td>
+    <td>Select the Transfer lock checkbox before continuing the setup.</td>
+  </tr>
 </table>
 
 When using compound words that have a preposition in them (think log in, or set up), they should be written as two separate words when they are verbs, and as one word when they are nouns.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
index 72a9ab7762531bd..fdb9214b95f5fc2 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/contractions.mdx
@@ -6,4 +6,4 @@ products:
   - style-guide
 ---
 
-Avoid using contractions such as _don't_, _won't_, and _can't_.
+Avoid using contractions such as *don't*, *won't*, and *can't*.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
index 72d3c0deacba961..dd8d05d847d9506 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
index 76a0418aeb4ab62..deb7014e128ee54 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/nouns-and-pronouns.mdx
@@ -14,7 +14,7 @@ Make sure it is clear who or what pronouns are in reference to. Pronouns act as
 
 Substitute "we" or "I" with "Cloudflare" if you need to represent Cloudflare. You do not need to use "we" constantly. However, use it when it is the best choice grammatically.
 
-| ✅                                                          | ❌                                                                |
+| ✅                                                           | ❌                                                                 |
 | ----------------------------------------------------------- | ----------------------------------------------------------------- |
 | Cloudflare recommends you submit image or plain text files. | We recommend closing your files before you restart your computer. |
 
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
index 5f490a47e38f572..187e021787a2e58 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/possessives.mdx
@@ -8,4 +8,4 @@ products:
 
 In general, avoid the 's construction to show possession by an inanimate object as doing so personifies the object.
 
-Example: _the device's address_.
+Example: *the device's address*.
diff --git a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
index 8e3704dfdac8622..10c8af546776d4a 100644
--- a/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
+++ b/src/content/docs/style-guide/grammar/parts-of-speech/prepositions.mdx
@@ -8,6 +8,6 @@ products:
 
 You can put a preposition at the end of a sentence, but do not do it often. Your sentences can sound stilted if you try to avoid putting the preposition at the end.
 
-| ✅                                                    | ❌                                                         |
+| ✅                                                     | ❌                                                          |
 | ----------------------------------------------------- | ---------------------------------------------------------- |
 | Open the application you are submitting an image for. | Open the application for which you are submitting an icon. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
index 39a5939c88506d9..415d78fa7023e8f 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/commas.mdx
@@ -18,6 +18,6 @@ Example: After you open the file, save it to your desktop with a different name.
 
 Use the Oxford comma. The Oxford comma should break up lists of three or more items in a sentence.
 
-Example: Stream for Free, Pro, and Business plans
+Example:  Stream for Free, Pro, and Business plans
 
 Without the Oxford comma, readers might misunderstand this header as free streaming for Pro and Business plans.
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
index 6e37346b1c896c4..2773cd5a9e97ed4 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/dashes.mdx
@@ -14,9 +14,9 @@ Dashes look like hyphens, but are wider. An em dash is the widest type of dash.
 
 Examples:
 
-- The most up-to-date software can be found here.
+* The most up-to-date software can be found here.
 
-- It takes 24-48 hours for the data to upload.
+* It takes 24-48 hours for the data to upload.
 
 :::note
 
@@ -26,7 +26,7 @@ Never include whitespaces around a hyphen.
 
 Additional examples:
 
-| ✅                                                                                                                   | ❌                                                                                                                   | Rationale                                                                                                                                                                                 |
+| ✅                                                                                                                    | ❌                                                                                                                    | Rationale                                                                                                                                                                                 |
 | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Protect your Internet property from common vulnerabilities with our enterprise-class Web Application Firewall (WAF). | Protect your Internet property from common vulnerabilities with our enterprise class Web Application Firewall (WAF). | ‘Enterprise-class’ refers to the ability of something to scale with and handle the needs of large enterprises. A hyphen is necessary because the compound modifier comes before the noun. |
 | Our WAF is enterprise class.                                                                                         | Our WAF is enterprise-class.                                                                                         | ‘Enterprise class’ modifies ‘WAF.’ A hyphen is not necessary because the compound modifier comes after the noun.                                                                          |
@@ -35,17 +35,17 @@ Additional examples:
 
 **Use em dashes to break up thoughts within a single sentence.** Em dashes (—) or double dashes (--) with spaces around them may be used to break up thoughts within a sentence. Single dashes (-), or hyphens, are commonly used to write compound words/modifiers and should never be used to break up thoughts in this way.
 
-- Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
+* Shortcut for Mac users: Hold down Shift and Option keys, then press the Minus key
 
-- Shortcut for PC users: Hold down the Alt key and type 0151
+* Shortcut for PC users: Hold down the Alt key and type 0151
 
 Dashes are used in pairs (in place of parenthesis) or alone (in place of a semicolon or colon).
 
 Examples:
 
-- Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
+* Cookies provide saved information about a user’s session to establish a “state” — in most cases, identity — as your browser makes a request.
 
-- Embed yourself in the team — the best results will come when trust is built.
+* Embed yourself in the team — the best results will come when trust is built.
 
 :::note
 
@@ -54,7 +54,7 @@ Following AP style guides, and to improve readability, we include whitespaces be
 
 Additional examples:
 
-| ✅                                                                                                                                                 | ❌                                                                                                                                               | Rationale                                                                                                                                                      |
+| ✅                                                                                                                                                  | ❌                                                                                                                                                | Rationale                                                                                                                                                      |
 | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | The app has made security and privacy core to the company’s mission — and that is why it chose Cloudflare to provide an extra layer of protection. | The app has made security and privacy core to the company’s mission—and that is why it chose Cloudflare to provide an extra layer of protection. | An em dash with spaces on both sides is the appropriate way to distinguish the offset phrase at the end of this sentence.                                      |
 | ACME has always looked deeply into two sources of traffic -- organic and direct traffic.                                                           | ACME has always looked deeply into two sources of traffic - organic and direct traffic.                                                          | A double dash is the appropriate way to clarify different types of traffic at the end of this sentence. A hyphen should not be used in place of a double dash. |
diff --git a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
index 6c7364bfdbb410d..d73f721061e8356 100644
--- a/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
+++ b/src/content/docs/style-guide/grammar/punctuation-marks-and-symbols/index.mdx
@@ -8,6 +8,6 @@ products:
   - style-guide
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/style-guide/how-we-docs/our-site.mdx b/src/content/docs/style-guide/how-we-docs/our-site.mdx
index 22522e9cde5ff47..99ca2d006472130 100644
--- a/src/content/docs/style-guide/how-we-docs/our-site.mdx
+++ b/src/content/docs/style-guide/how-we-docs/our-site.mdx
@@ -28,6 +28,7 @@ We use [Starlight](https://starlight.astro.build/) for our docs, which is a free
 
 Astro's [component overrides](https://starlight.astro.build/guides/overriding-components/) and [plugins](https://starlight.astro.build/resources/plugins/) system were a big part of us [choosing this framework](https://blog.cloudflare.com/open-source-all-the-way-down-upgrading-our-developer-documentation/) and have exponentially increased our [site's capabilities](/style-guide/components/) (without much extra work).
 
+
 ## Builds
 
 We use [GitHub Actions](https://github.com/features/actions) to build our site, which is then [hosted](#hosting) on Cloudflare.
diff --git a/src/content/docs/style-guide/how-we-docs/reviews.mdx b/src/content/docs/style-guide/how-we-docs/reviews.mdx
index 26cc6567c416368..da23b24233aa04c 100644
--- a/src/content/docs/style-guide/how-we-docs/reviews.mdx
+++ b/src/content/docs/style-guide/how-we-docs/reviews.mdx
@@ -25,14 +25,14 @@ For pull requests, we use a specific [GitHub action](https://github.com/cloudfla
 - [Label products](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-products/): We add labels for the top-level product folder, which helps writers scan incoming pull requests and see which are relevant to them.
 - [Label size](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/actions/label-size/): We add labels for the size of the pull request, which helps writers see the relative size of the difference. It's not a perfect measure, but we use the lines changed to estimate the size of the pull request:
 
-  <GitHubCode
-  	repo="cloudflare/cloudflare-docs"
-  	file=".github/actions/label-size/index.ts"
-  	commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
-  	lines="20-36"
-  	lang="ts"
-  	code={{ title: "label-size.ts" }}
-  />
+	<GitHubCode
+		repo="cloudflare/cloudflare-docs"
+		file=".github/actions/label-size/index.ts"
+		commit="3dd03fdad79b2663631a6530794dfd1ad15bdc03"
+		lines="20-36"
+		lang="ts"
+		code={{ title: "label-size.ts" }}
+	/>
 
 - [Assign codeowners](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/assign-pr): We use our [CODEOWNERS](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/CODEOWNERS) file to automatically assign people to pull requests based on the files changed. This assignment helps writers scan and filter to see which pull requests are relevant to them.
 
@@ -42,6 +42,7 @@ For issues, we use a similar [GitHub action](https://github.com/cloudflare/cloud
 
 Our [script](https://github.com/cloudflare/cloudflare-docs/tree/production/.github/actions/issue-label-assign) treats issues because usually they contain links to our site instead of files within the repository. We grab the associated links in the issue description fields and then use those to assign writers (again based on `CODEOWNERS`) and add product labels.
 
+
 ## Streamline reviews
 
 To streamline reviews, we use several automations to help solve common reviewer issues.
@@ -67,7 +68,7 @@ We have a specific part of [CI](https://github.com/cloudflare/cloudflare-docs/bl
 
 ### What changed?
 
-We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub).
+We use a [GitHub action](https://github.com/cloudflare/cloudflare-docs/blob/production/.github/workflows/publish-preview.yml) to publish preview builds for every commit on a pull request (and [comment those links](https://github.com/cloudflare/cloudflare-docs/tree/production/bin/post-preview-url-comment) on the pull request). This action ensures that reviewers can see exactly what the site and content will look like when they're rendered (and not just look at the changed markdown in GitHub). 
 
 We are in the process of migrating to [Workers Builds](/workers/ci-cd/builds/git-integration/github-integration/), which provides that functionality natively.
 
@@ -103,4 +104,4 @@ This workflow - we hope - balances the needs our of team with a healthy respect
 
 We intentionally avoid the [`stale` workflow](https://github.com/github/docs/blob/main/.github/workflows/stale.yml) that closes pull requests or issues that have been inactive for a specific period of time.
 
-In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
+In our opinion, this workflow causes more friction and frustration than it solves. Just because something has been around for a year doesn't mean it's not still relevant.
\ No newline at end of file
diff --git a/src/content/docs/support/contacting-cloudflare-support.mdx b/src/content/docs/support/contacting-cloudflare-support.mdx
index 657813bb6f05df5..ac84963b72ae9f0 100644
--- a/src/content/docs/support/contacting-cloudflare-support.mdx
+++ b/src/content/docs/support/contacting-cloudflare-support.mdx
@@ -39,7 +39,7 @@ As a Cloudflare customer, you can contact Cloudflare for support via the communi
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------- | ----------- | ----------- |
 | [Community](https://community.cloudflare.com/)<br/>Join the community to ask basic troubleshooting questions and to view the latest resources (such as tips for resolving common issues and configuration guidance). | Yes        | Yes      | Recommended | Recommended |
 | [Discord](https://discord.cloudflare.com/)<br/>Join the Discord community to ask basic troubleshooting questions (mainly focused on the Developer Platform).                                                         | Yes        | Yes      | Recommended | Recommended |
-| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]      |
+| [Support case](#getting-help-with-an-issue)<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                   | Yes        | Yes      | Yes         | No[^1]        |
 | **Chat**<br/>Use to troubleshoot specific issues or errors. Response times depend on your plan.                                                                                                                      | Yes        | Yes      | No          | No          |
 | **Emergency Phone** <br/>Use phone support to reach out during emergencies such as site outages or DDoS attacks.                                                                                                     | Yes        | No       | No          | No          |
 
@@ -83,12 +83,7 @@ In both cases, you will also need your **Unique Customer ID** (refer to [Finding
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton
-	href="https://dash.cloudflare.com/?to=/:account/support"
-	icon="external"
->
-	Go to Support
-</LinkButton>
+<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -102,12 +97,7 @@ Your Unique Customer ID is required when calling the emergency phone line, regar
 
 1. In the Cloudflare dashboard, go to the **Support** page and select the account you are calling about.
 
-<LinkButton
-	href="https://dash.cloudflare.com/?to=/:account/support"
-	icon="external"
->
-	Go to Support
-</LinkButton>
+<LinkButton href="https://dash.cloudflare.com/?to=/:account/support" icon="external">Go to Support</LinkButton>
 
 2. Click on the **Emergency hotline** tile.
 
@@ -141,21 +131,21 @@ To submit a support case, follow these steps:
 5. Enter a detailed summary of the issue you’re experiencing.
 
 6. Complete the case submission fields as completely as possible with the following information. _(**Please note** that missing information will increase the time it takes to resolve your issue and our team may not be able to investigate without enough information. Please review [Gathering information for troubleshooting sites](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) and make sure you include all needed information.)_
-   \- A detailed description of the issue with the following information:
-   - Timestamp (UTC)
-   - ZoneName/ZoneID
-   - Problem frequency
-   - Steps to reproduce the issue, with actual results vs expected results
-     \- Any necessary information for a technical investigation
-   - A description of the actual results vs expected results
-   - Steps to reproduce the issue, with example URLs 
-   - Exact error messages
-   - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
-   - Screenshots
-   - Relevant logs from the origin web server
-   - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
-     \- Priority level, impact to service / production
-     \- Any collaborators whom you wish to be cc'd on the case
+    \- A detailed description of the issue with the following information:
+    - Timestamp (UTC)
+    - ZoneName/ZoneID
+    - Problem frequency
+    - Steps to reproduce the issue, with actual results vs expected results
+      \- Any necessary information for a technical investigation
+    - A description of the actual results vs expected results
+    - Steps to reproduce the issue, with example URLs 
+    - Exact error messages
+    - [HAR files](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#generate-a-har-file)
+    - Screenshots
+    - Relevant logs from the origin web server
+    - Output from [test tools](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/) such as MTR, traceroute, dig/nslookup, and cURL
+      \- Priority level, impact to service / production
+      \- Any collaborators whom you wish to be cc'd on the case
 
 7. Click **Submit Case**.
 
diff --git a/src/content/docs/support/index.mdx b/src/content/docs/support/index.mdx
index 113e68d713a7601..d6fc7fa654994ef 100644
--- a/src/content/docs/support/index.mdx
+++ b/src/content/docs/support/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
index 318aef05f182daf..f4dcbec1ff8594c 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx
@@ -15,14 +15,14 @@ When you switch a theme or customise a theme within the WordPress admin panel, t
 
 Automatic Cache Management uses native hooks built into WordPress. The Cloudflare WordPress plugin purges the following cache URLs:
 
-- deleted_post
-- edit_post
-- delete_attachment
-- autoptimize_action_cachepurged (for compatibility with the Autoptimize WordPress plugin)
-- switch_theme
-- customize_save_after
-
----
+* deleted\_post
+* edit\_post
+* delete\_attachment
+* autoptimize\_action\_cachepurged (for compatibility with the Autoptimize WordPress plugin)
+* switch\_theme
+* customize\_save\_after
+
+***
 
 ## Enable Automatic Cache Management
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
index 0993a2e99b86ad7..9a95b6b8ff0e658 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx
@@ -9,7 +9,7 @@ products:
 
 HTTP/2 Server Push allows a website to push content to a browser, without having to wait for the HTML of one page to render first. In conjunction with the concurrency support built into HTTP/2, Server Push is able to dramatically reduce the amount of requests needed to load your website.
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733367/http2-server-push-2.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733367/http2-server-push-2.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-http2_server_push_2.png)
 
@@ -23,12 +23,12 @@ define('CLOUDFLARE_HTTP2_SERVER_PUSH_ACTIVE', true);
 
 You should insert this line above where it says *"/\* That's all, stop editing! Happy blogging. \*/*", like follows:|
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005733547/Screen_Shot_2017-02-09_at_16.09.31.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005733547/Screen\_Shot\_2017-02-09\_at\_16.09.31.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2017_02_09_at_16_09_31.png)
 
 You should then start to see requests coming in which are initiated through Server Push, for example, in the Network tab of Chrome Development Tools you should see some assets have "Push" as the initiator:
 
-![Old URL: https://support.cloudflare.com/hc/en-us/article_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
+![Old URL: https://support.cloudflare.com/hc/en-us/article\_attachments/115005787688/Screen-Shot-2016-04-26-at-15-08-59.png
 Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
 ](~/assets/images/support/hc-import-screen_shot_2016_04_26_at_15_08_59.png)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
index bd0724c70711abf..2f68ed6b392d2da 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/improving-web-security-for-content-management-systems-like-wordpress.mdx
@@ -11,7 +11,7 @@ Content Management Systems make it easy to create, update, and manage content. H
 
 There are many Cloudflare features that can be used for preventing such attacks, but they can also disrupt normal administrative processes such as logging in or uploading images. With proper configuration, you can protect your site from attacks without losing important functionality.
 
----
+***
 
 ## Stage One: Improve Site Security
 
@@ -29,13 +29,13 @@ The [WAF Managed Rulesets](/waf/managed-rules/) are pre-configured rulesets that
 
 While the feature to customize these managed rulesets required a paid plan, the [Free Cloudflare Managed Ruleset](https://blog.cloudflare.com/waf-for-everyone/#the-free-cloudflare-managed-ruleset) is automatically deployed on any new Cloudflare zone. This ruleset is specially designed to reduce false positives to a minimum across a very broad range of traffic types. As of today, the ruleset contains the following rules:
 
-- Log4J rules matching payloads in the URI and HTTP headers;
-- Shellshock rules;
-- Rules matching very common WordPress exploits;
+* Log4J rules matching payloads in the URI and HTTP headers;
+* Shellshock rules;
+* Rules matching very common WordPress exploits;
 
 Additionally, you can configure many aspects of the [OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/), including the anomaly threshold, paranoia level, and individual rules. One good practice is to ensure any rules related to XSS and SQL injection are enabled.
 
----
+***
 
 ## Stage Two: Restore Administrative Functions
 
@@ -56,12 +56,12 @@ Next, you can use this information to create a Skip Rule that excludes only the
 
 It is recommended to make this rule as tightly defined as possible, particularly without the additional protections listed below. While the exact content will be site-specific, some possible fields to use are:
 
-- IP Source Address
-- AS Num
-- Cookie
-- User Agent
+* IP Source Address
+* AS Num
+* Cookie
+* User Agent
 
-Make sure to apply the rule _only_ to the admin portion of your CMS. With WordPress for example, you can set a condition like '_URI Path contains /wp-admin/_'.
+Make sure to apply the rule *only* to the admin portion of your CMS. With WordPress for example, you can set a condition like '*URI Path contains /wp-admin/*'.
 
 Any of these fields can be spoofed, so this is not a security measure on its own. The purpose is to restore administrative functions only to conditions that may need them, while using other tools and features (including strong passwords on your CMS logins!) to secure access.
 
@@ -77,7 +77,7 @@ After this is complete, you will want to create a similar rule for any rulesets
 
 Make sure to set your Skip rules to be at a higher priority than the Execute rules.
 
----
+***
 
 ## Stage Three: Restrict Access
 
@@ -102,7 +102,7 @@ Do the following:
 3. [Enable mTLS](/ssl/client-certificates/enable-mtls/) by adding the correct host.
 4. In **SSL/TLS** > **Client Certificates**, select **Create mTLS Rule**.
 5. Under **When incoming requests match**, enter a value for the **URI Path** field to narrow the rule scope to the admin section, otherwise you will block your visitors from accessing the public content.
-6. Set the rule to _Block_ any requests made to your admin panel if the client certificate is not verified.
+6. Set the rule to *Block* any requests made to your admin panel if the client certificate is not verified.
 7. Select **Deploy**. This creates a WAF custom rule that checks all requests to the admin section for a valid client certificate.
 
 **Note:** If you have issues getting your certificate to verify, try accessing the page in a private window. If it works, the previous successful TLS state may be cached in your browser.
@@ -113,13 +113,13 @@ Rate limiting rules can help protect your login page from an attacker trying to
 
 Rate Limiting Rules are now available unmetered, on all plans. For more information, refer to the [developer documentation](/waf/rate-limiting-rules/).
 
----
+***
 
 ## Resources
 
-- [WAF Managed Rules](/waf/managed-rules/)
-- [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
-- [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
-- [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
-- [Client certificates](/ssl/client-certificates/)
-- [Rate limiting rules](/waf/rate-limiting-rules/)
+* [WAF Managed Rules](/waf/managed-rules/)
+* [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
+* [Configure a custom rule with the Skip action](/waf/custom-rules/skip/)
+* [Zero Trust Services](https://www.cloudflare.com/plans/zero-trust-services/)
+* [Client certificates](/ssl/client-certificates/)
+* [Rate limiting rules](/waf/rate-limiting-rules/)
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
index a520969018400e2..7f619ce81d0c809 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Content Management System (CMS) support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
index b1a0aaaa794a451..72cf2b3808b2ec2 100644
--- a/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
+++ b/src/content/docs/support/third-party-software/content-management-system-cms/what-settings-are-applied-when-i-click-optimize-cloudflare-for-wordpress-in-cloudflares-wordpress-plugin.mdx
@@ -14,16 +14,16 @@ If you are using [Cloudflare's WordPress plugin](/automatic-platform-optimizatio
 
 ![Cloudflare's one-click configuration WordPress plugin.](~/assets/images/support/dash-optimize_wordpress.png)
 
-| **Setting**                 | **Value**                          |
-| --------------------------- | ---------------------------------- |
-| Caching level               | Standard                           |
-| Browser Cache TTL           | 4 hours                            |
-| Always Online               | On                                 |
-| Development Mode            | Disabled                           |
-| IPV6 Compatibility          | On                                 |
-| WebSockets                  | On                                 |
-| IP Geolocation              | On                                 |
-| Email Address Obfuscation   | On                                 |
-| Hotlink Protection          | Off                                |
-| Image optimization (Polish) | Off (unless on Pro or higher plan) |
-| Rocket Loader               | Off                                |
+| **Setting**                            | **Value**                          |
+| -------------------------------------- | ---------------------------------- |
+| Caching level                          | Standard                           |
+| Browser Cache TTL                      | 4 hours                            |
+| Always Online                          | On                                 |
+| Development Mode                       | Disabled                           |
+| IPV6 Compatibility                     | On                                 |
+| WebSockets                             | On                                 |
+| IP Geolocation                         | On                                 |
+| Email Address Obfuscation              | On                                 |
+| Hotlink Protection                     | Off                                |
+| Image optimization (Polish)            | Off (unless on Pro or higher plan) |
+| Rocket Loader                          | Off                                |
diff --git a/src/content/docs/support/third-party-software/forum-software/index.mdx b/src/content/docs/support/third-party-software/forum-software/index.mdx
index a3bd9f78a0ca9a2..6b8e3da66053d73 100644
--- a/src/content/docs/support/third-party-software/forum-software/index.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Forum Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
index 0669bac8222e466..1b3e0496d4d3820 100644
--- a/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
+++ b/src/content/docs/support/third-party-software/forum-software/using-cloudflare-with-various-forums-vbulletin-xenforo-mybb.mdx
@@ -13,14 +13,14 @@ Many widely used forum platforms are compatible with Cloudflare.
 
 These include:
 
-- [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
-- vBulletin
-- Xenforo
-- MyBB
+* [Discourse](https://community.cloudflare.com/t/using-discourse-with-cloudflare-best-practices/602890)
+* vBulletin
+* Xenforo
+* MyBB
 
 If you have a forum using these platforms, you can increase its speed and safety by adding Cloudflare.
 
----
+***
 
 ## Steps
 
diff --git a/src/content/docs/support/third-party-software/index.mdx b/src/content/docs/support/third-party-software/index.mdx
index 64ef43df834abe9..b79e7fe82f69cfc 100644
--- a/src/content/docs/support/third-party-software/index.mdx
+++ b/src/content/docs/support/third-party-software/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Third-Party Software support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/index.mdx b/src/content/docs/support/third-party-software/others/index.mdx
index d253e19c2efccb6..70b8ce2974da5f2 100644
--- a/src/content/docs/support/third-party-software/others/index.mdx
+++ b/src/content/docs/support/third-party-software/others/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Others support-focused material.
 
diff --git a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
index a32fb2d6902eb8f..4cbb158f3f19295 100644
--- a/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
+++ b/src/content/docs/support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare.mdx
@@ -13,7 +13,7 @@ Cloudflare launched Bandwidth Alliance in 2018 – a group of forward-looking cl
 
 Cloudflare customers using Azure can lower their egress bills between Cloudflare and Azure via [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/virtual-network/routing-preference-overview).
 
----
+***
 
 ## How to
 
@@ -31,9 +31,9 @@ To lower your data transfer costs from Azure and Cloudflare: 
 
 For additional details, refer to [Configure network routing preference for Azure Storage](https://docs.microsoft.com/en-us/azure/storage/common/configure-network-routing-preference?tabs=azure-portal) and [Microsoft Routing Preference](https://docs.microsoft.com/en-us/azure/storage/common/network-routing-preference).
 
----
+***
 
 ## Related resources
 
-- [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
-- [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
+* [Microsoft Azure data transfer announcement](https://blog.cloudflare.com/discounted-egress-for-cloudflare-customers-from-microsoft-azure-is-now-available/) (blog)
+* [Bandwidth Alliance](https://www.cloudflare.com/bandwidth-alliance/)
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
index f5af757c7bdc872..3a30b097d7d9ced 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account.mdx
@@ -26,7 +26,7 @@ This process will allow us to link your account inside our new support system.
 
 If you are a free account customer, you do not have access to this feature, but you can get assistance in many other ways:
 
-- By joining the conversation in our [Community forums](https://community.cloudflare.com/).
-- By joining our [Discord server](https://discord.cloudflare.com/).
-- By checking out our [Documentation](/).
-- By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
+* By joining the conversation in our [Community forums](https://community.cloudflare.com/).
+* By joining our [Discord server](https://discord.cloudflare.com/).
+* By checking out our [Documentation](/).
+* By visiting the [Cloudflare Help Center](https://support.cloudflare.com/). There you will find our most frequently asked questions, steps to issue resolution, and more.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
index 2a8ae8a1e746734..a1ec1b9e2b99753 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
@@ -23,18 +23,18 @@ customers due to security and liability concerns.
 
 Use this table to quickly identify which troubleshooting method to use based on your issue:
 
-| Issue Type                     | Recommended Tool                                                                    | When to Use                                               |
-| ------------------------------ | ----------------------------------------------------------------------------------- | --------------------------------------------------------- |
-| Page not loading correctly     | [HAR file](#generate-a-har-file)                                                    | Visual issues, broken elements, slow page loads           |
-| JavaScript errors              | [Console log](#export-console-log)                                                  | CORS errors, scripts failing, browser-side errors         |
-| Protocol errors (QUIC/HTTP2)   | [NetLog dump](#capture-a-netlog-dump)                                               | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR`     |
-| Slow response times            | [curl (performance)](#performance)                                                  | Measuring latency, TLS handshake times                    |
-| HTTP errors (5xx, 4xx)         | [curl (HTTP errors)](#http-errors)                                                  | Determining if errors originate from Cloudflare or origin |
-| Caching issues                 | [curl (caching)](#caching)                                                          | Cache misses, stale content, cache headers                |
-| SSL/TLS certificate issues     | [curl (SSL/TLS)](#ssltls-certificates)                                              | Certificate errors, TLS version issues                    |
-| Connection timeouts/drops      | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr)                         | Network path issues, latency between hops                 |
-| Packet loss, connection resets | [Packet capture](#run-packet-captures)                                              | Layer 3/4 issues, SSL handshake failures                  |
-| Identifying serving location   | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests        |
+| Issue Type | Recommended Tool | When to Use |
+|------------|------------------|-------------|
+| Page not loading correctly | [HAR file](#generate-a-har-file) | Visual issues, broken elements, slow page loads |
+| JavaScript errors | [Console log](#export-console-log) | CORS errors, scripts failing, browser-side errors |
+| Protocol errors (QUIC/HTTP2) | [NetLog dump](#capture-a-netlog-dump) | `ERR_QUIC_PROTOCOL_ERROR`, `ERR_HTTP2_PROTOCOL_ERROR` |
+| Slow response times | [curl (performance)](#performance) | Measuring latency, TLS handshake times |
+| HTTP errors (5xx, 4xx) | [curl (HTTP errors)](#http-errors) | Determining if errors originate from Cloudflare or origin |
+| Caching issues | [curl (caching)](#caching) | Cache misses, stale content, cache headers |
+| SSL/TLS certificate issues | [curl (SSL/TLS)](#ssltls-certificates) | Certificate errors, TLS version issues |
+| Connection timeouts/drops | [Traceroute](#perform-a-traceroute) / [MTR](#perform-a-mtr) | Network path issues, latency between hops |
+| Packet loss, connection resets | [Packet capture](#run-packet-captures) | Layer 3/4 issues, SSL handshake failures |
+| Identifying serving location | [Cloudflare data center](#identify-the-cloudflare-data-center-serving-your-request) | Determine which Cloudflare PoP is serving requests |
 
 ---
 
@@ -53,7 +53,7 @@ A HTTP Archive (HAR) records all web browser requests including the request and
 :::caution
 
 A HAR file can include sensitive details such as passwords, payment
-information, and private keys.
+information, and private keys. 
 
 Remove sensitive information using a [HAR Sanitizer](https://har-sanitizer.pages.dev/).
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
index 75fdc9854918fee..2d097e0a9229ebd 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
@@ -6,6 +6,6 @@ products:
   - support
 ---
 
-Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability.
+Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability. 
 
 In instances where performance and reliability are in conflict, our systems are designed to prioritize a stable connection over a local one.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
index 256522df2decdc4..058aa4d051dd35b 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for General Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
index 738bb5db1983575..acc27ba05615fa5 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/not-receiving-cloudflare-emails.mdx
@@ -8,18 +8,18 @@ products:
 
 This article may help if you are unable to receive transactional emails from Cloudflare. These types of email include:
 
-- email verification
-- forgot / reset password
-- any other type of automated notification generated by the Cloudflare dashboard
+* email verification
+* forgot / reset password
+* any other type of automated notification generated by the Cloudflare dashboard
 
 If you are expecting but not receiving these emails from Cloudflare, review the following.
 
 ## Causes
 
-- Your email address is incorrect or mistyped in the Cloudflare dashboard
-- Your email server or mailbox is not working
-- Your mail server or software is filtering or blocking messages from Cloudflare
-- Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
+* Your email address is incorrect or mistyped in the Cloudflare dashboard
+* Your email server or mailbox is not working
+* Your mail server or software is filtering or blocking messages from Cloudflare
+* Your mail server previously bounced too many messages from Cloudflare, resulting in email delivery no longer being attempted
 
 ## Solution
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
index d7bbd6cd5dbd72d..3a81d5514edb8f9 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/service-disruption.mdx
@@ -6,17 +6,17 @@ products:
   - support
 ---
 
-Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare.
+Cloudflare has observed that Internet Service Providers (ISPs) within Russia are systematically throttling traffic to websites and services, including those protected by Cloudflare. 
 
 This appears to restrict data transfer to approximately 16 KB per connection, which renders most websites, including those of our customers, inaccessible or unusable for visitors from Russia.
 
 What to expect with your website:
 
-- This is not due to a misconfiguration of your Cloudflare settings.
+- This is not due to a misconfiguration of your Cloudflare settings. 
 - You will likely see a significant drop in traffic from users in Russia in your Cloudflare Analytics.
 - Your visitors in Russia may experience connection failures or sites that do not load properly.
-- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users.
+- As these actions are taken at the ISP level within Russia, we do not have the ability to restore Internet connectivity for Russia-based users. 
 
 If you are a Cloudflare enterprise customer, contact your account team for further assistance.
 
-For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/).
+For further details, refer to the [Russian Internet users are unable to access the open Internet blog post](https://blog.cloudflare.com/russian-internet-users-are-unable-to-access-the-open-internet/). 
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
index eeef01c3bebc4e4..37ece0e92f767e7 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/third-party-load-balancers.mdx
@@ -30,15 +30,15 @@ F5 session cookies can have arbitrary names but typically follow a specific form
 
 - Without encryption (trivially decoded to show origin server IP and port):
 
-  ```txt
-  BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
-  ```
+   ```txt
+   BIGipCookie=16908480.16415.0000;path=/; Httponly; Secure
+   ```
 
 - With encryption:
 
-  ```txt
-  BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
-  ```
+   ```txt
+   BIGipCookie=TS019a202c=01625f1893a7d6e4b2c1a0f98e7d6c5b4a3f2e1d; path=/; Httponly; Secure
+   ```
 
 #### 2. Test for the issue
 
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
index e47931dd17c1429..78c13a35999c2b2 100644
--- a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
+++ b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
@@ -9,46 +9,46 @@ products:
 
 Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
 
----
+***
 
 ## Disable Anti-bot modules
 
 Search engine crawlers' requests, when proxied through Cloudflare, can be blocked by anti-bot modules installed on your origin server. Try disabling any anti-bot modules to prevent your origin from blocking these requests.
 
----
+***
 
 ## Adjust Google and Bing crawl rates
 
 To optimize CDN performance, Google and Bing assign special crawl rates to websites that use CDN services in order. Special crawl rates do not negatively affect Search Engine Optimization (SEO) and Search Engine Results Pages (SERPs). To change your crawl rates for Bing and Google, follow the guides below:
 
-- Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
-- Change your Bing crawl rate via guidance from Bing’s documentation:
-  - [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
-  - [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
+* Change the Google crawl rate by [reviewing Google’s documentation](https://support.google.com/webmasters/answer/48620?hl=en).
+* Change your Bing crawl rate via guidance from Bing’s documentation:
+  * [Bing Crawl Control](https://www.bing.com/webmasters/help/?topicid=55a30303)
+  * [Crawl Delay and the Bing Crawler](https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot)
 
----
+***
 
 ## Prevent crawl errors
 
 Review the following recommendations to prevent crawler errors:
 
-- Monitor the performance and availability of your website using a third-party tool:
-  - [StatusCake](http://www.statuscake.com/)
-  - [Pingdom](http://www.pingdom.com/)
-  - [Monitor.Us](http://www.monitor.us/)
-  - [Updown](https://updown.io/)
+* Monitor the performance and availability of your website using a third-party tool:
+  * [StatusCake](http://www.statuscake.com/)
+  * [Pingdom](http://www.pingdom.com/)
+  * [Monitor.Us](http://www.monitor.us/)
+  * [Updown](https://updown.io/)
 
-- Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
+* Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
 
   Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
 
-- Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
+* Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
 
-- Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
+* Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
 
 Google uses a [variety of User-Agents](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers) to crawl your website. You can [test your `robots.txt` via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
 
-- Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
+* Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi` via `robots.txt`:
 
 `Disallow: /cdn-cgi/`
 
@@ -57,10 +57,10 @@ Google uses a [variety of User-Agents](https://developers.google.com/search/docs
 Errors for `cdn-cgi` do not impact site rankings.
 :::
 
-- Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943).
-- [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
+* Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
+* [Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
 
----
+***
 
 ## Troubleshoot crawl errors
 
@@ -107,7 +107,7 @@ If the above troubleshooting steps do not resolve your crawl errors, follow the
 3. Click **Download** to export the list of errors as a `.csv` file.
 4. Provide the downloaded `.csv` file to Cloudflare support.
 
----
+***
 
 ## Related resources
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
index fd1f90255a9adde..f5f8373a02c6fde 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx
@@ -15,7 +15,7 @@ For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
 
 ### Common use cases
 
-A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing.
+A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. 
 For example:
 
 - If the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
index b62f398bfdbf194..6f67fbca6e007e6 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx
@@ -21,4 +21,4 @@ If the client resends the request with the same credentials and the challenge re
 
 ### Cloudflare-specific information
 
-When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
+When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
index 5ab48647ac86db3..dc315ae8a719b89 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx
@@ -19,4 +19,4 @@ For example, if a client requests content in a specific language or character se
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
+Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
index dd4f38c4aa51099..8083045fa4bc840 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx
@@ -18,4 +18,4 @@ This error typically occurs in environments where a proxy server is used as an i
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
+Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
index f2e5da4a9064ce3..5b3115cc744996f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx
@@ -21,4 +21,4 @@ This error typically occurs when a client fails to send a complete request withi
 
 If a `408` error occurs on a Cloudflare-powered site, it is most often being proxied from the origin. In these cases, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly.
 
-Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
+Cloudflare may return a `408` error response if public client requests to our network exceed certain internally-defined timeouts. These timeouts are configured as a protective measure and cannot be changed.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
index c0098ba91b387b4..87e414554c0bf55 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx
@@ -22,4 +22,4 @@ This error typically happens with a `PUT` request when multiple clients are atte
 
 ### Cloudflare-specific information
 
-Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
+Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
index 17e6ee5ff4d269a..efdb6f72bdc5fe1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx
@@ -23,4 +23,4 @@ This status is commonly applied to deprecated content, such as outdated pages or
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
+Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
index 47fe8d6954c39bd..2bbf1fafa9e5767 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx
@@ -19,4 +19,4 @@ This status code can occur in various scenarios, such as when a client sends an
 
 ### Cloudflare-specific information
 
-Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
+Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
index 11efe2add1f92d6..6c46a3195a74a9e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx
@@ -19,4 +19,4 @@ One common use case for the `412 Precondition Failed` status code is version con
 
 ### Cloudflare-specific information
 
-Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
+Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
index effc3539c4d9e6a..df0769a0b4bfd44 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx
@@ -27,4 +27,4 @@ The upload limit for the Cloudflare API depends on your plan. If you exceed this
 
 Keep in mind, customers can reduce the **Maximum Upload Size** from the zone's **Network** page which can cause a `413`.
 
-If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
+If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
index c6b7876ce046cf3..d27ba07b657f86b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx
@@ -19,4 +19,4 @@ For example, if a client is attempting a `GET` request with an unusually long UR
 
 ### Cloudflare-specific information
 
-Cloudflare will generate a `414` response if the URI length exceeds 32KB.
+Cloudflare will generate a `414` response if the URI length exceeds 32KB.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
index bf00d11dff44238..62c07d24e2e5251 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx
@@ -19,4 +19,4 @@ This error can happen when a client requests a byte range outside the bounds of
 
 ### Cloudflare-specific information
 
-Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
+Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
index 711500dca7e9bae..5ad66dd00072ced 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx
@@ -19,4 +19,4 @@ Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify
 
 ### Cloudflare-specific information
 
-Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
+Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
index 7d4d40af9d2bd76..995be774a343c75 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx
@@ -32,3 +32,4 @@ Cloudflare applies rate limiting to requests for R2 managed public buckets acces
 #### Website end users
 
 Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
index 7a3792b883d662c..4d7d15261e11b47 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx
@@ -19,4 +19,4 @@ This occurs when access to a resource is blocked due to court orders, copyright
 
 ### Cloudflare-specific information
 
-Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
+Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
index c2a6601666766b7..d9e3fe99f491207 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx
@@ -15,7 +15,7 @@ products:
 
 ## Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), which can be useful to investigate HTTP Errors.
 
@@ -27,6 +27,7 @@ For a complete description of this error refer to the [Error 400](/support/troub
 
 For a complete description of this error refer to the [Error 401](/support/troubleshooting/http-status-codes/4xx-client-error/error-401/) page.
 
+
 ## 402 Payment Required
 
 The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231).
@@ -35,6 +36,7 @@ The `402 Payment Required` status code is reserved for future use and is not yet
 
 For a complete description of this error refer to the [Error 403](/support/troubleshooting/http-status-codes/4xx-client-error/error-403/) page.
 
+
 ## 404 Not Found
 
 For a complete description of this error refer to the [Error 404](/support/troubleshooting/http-status-codes/4xx-client-error/error-404/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
index 18167b8092b1b9b..36deca809c49e5c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10028.mdx
@@ -20,4 +20,4 @@ This error occurs when there are duplicate list items in a single operation to a
 
 ### Resolution
 
-You need to remove the duplicate item and try again.
+You need to remove the duplicate item and try again.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
index 107785e0dccf2ec..ec68460a428d719 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10043.mdx
@@ -20,4 +20,4 @@ This error occurs when the source URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the source URL.
+You need to use a shorter URL as the source URL.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
index c5307d8789975fb..687c3022a1391f4 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10044.mdx
@@ -20,4 +20,4 @@ This error occurs when the target URL value of a URL redirect is too long. The m
 
 ### Resolution
 
-You need to use a shorter URL as the target URL.
+You need to use a shorter URL as the target URL.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
index e061d57515adeb3..16221ebbff83170 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10045.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
index 16897ff09f53dfb..263401952d5dc31 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10046.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL provided for a URL redirect is not valid,
 
 ### Resolution
 
-You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
+You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
index 1bc04c5dadad755..ba1cd6d9d14c953 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10047.mdx
@@ -17,4 +17,4 @@ This error occurs when you specify a URL redirect status code that is not suppor
 
 ### Resolution
 
-Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
+Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
index a68813f6502ebc5..5d066ea9c0d5f2c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10048.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve path suffix** option in a redir
 
 ### Resolution
 
-Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
+Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
index 085dc2ea7f596d2..343a60e375b1269 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10049.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect has an invalid scheme, w
 
 ### Resolution
 
-Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
index 172b34e6b076576..e037df5b8d6fdca 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10050.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a user info com
 
 ### Resolution
 
-You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
index a7ea0e0f82e50c6..e4399c78df33671 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10051.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect does not include an auth
 
 ### Resolution
 
-Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
+Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
index 371faef69c84269..36d65f8b2d2d541 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10052.mdx
@@ -17,4 +17,4 @@ This error occurs when the source URL of a URL redirect includes a port (for exa
 
 ### Resolution
 
-Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
+Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
index c0c9c3440aa4398..4cacdc75502b532 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10055.mdx
@@ -17,4 +17,4 @@ This error occurs when you enable the **Preserve query string** option of a URL
 
 ### Resolution
 
-To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
+To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
index 1198b1552a6e89e..d6b879890b89165 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10056.mdx
@@ -20,4 +20,4 @@ This error occurs when different types of list items (such as IP addresses, host
 Remove the list items that do not apply to the list type. This means:
 
 - Removing IP addresses from a request to add items to a Bulk Redirect List.
-- Removing URL redirects from a request to add items to an IP list.
+- Removing URL redirects from a request to add items to an IP list.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
index 6c39cf94fee9dc4..158e45e84a4d659 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10058.mdx
@@ -21,4 +21,4 @@ Make sure you are adding the items to the correct list:
 
 - Custom lists with IP addresses (IP lists) can only contain IP addresses as list items.
 - Custom lists with hostnames can only contain hostnames as list items.
-- Bulk Redirect Lists can only contain URL redirects as list items.
+- Bulk Redirect Lists can only contain URL redirects as list items.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
index 7d137ba67522622..37a293ffd69b91e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10059.mdx
@@ -17,4 +17,4 @@ This error occurs when you have more than the maximum number of URL redirects wi
 
 ### Resolution
 
-Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
+Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
index 617ad8ff0c6f421..eb841ff74628814 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060.mdx
@@ -17,4 +17,4 @@ This error occurs when the target URL of a URL redirect does not include a schem
 
 ### Resolution
 
-Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
+Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
index 1b97c64adc8da93..c47d1c3dccc0286 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/index.md
@@ -76,4 +76,4 @@ For a complete description of this error refer to the [Error 10059](/support/tro
 
 ## Error 10060: Missing scheme in redirect target URL
 
-For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
+For a complete description of this error refer to the [Error 10060](/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/error-10060/) page.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
index 23d789e3acc15d7..ed56fe2d03d4b5c 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000.mdx
@@ -27,4 +27,4 @@ Cloudflare halted the request for one of the following reasons:
 
 - If an A record within your Cloudflare DNS app points to a [Cloudflare IP address](https://www.cloudflare.com/ips/), update the IP address to your origin web server IP address. Reach out to your hosting provider if you need help obtaining the origin IP address.
 - There is a reverse-proxy at your origin that sends the request back through the Cloudflare proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.
-- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
+- If your domain points to a SaaS provider that uses Cloudflare, contact the SaaS provider to verify that a custom hostname is properly configured for your domain. The error originates from the provider's Cloudflare account, not yours.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
index 2c3f226dc6e792c..ccc795620204019 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002.mdx
@@ -1,13 +1,13 @@
 ---
 pcx_content_type: troubleshooting
-title: Error 1002
+title: Error 1002 
 source: null
 description: Troubleshoot Cloudflare 1002 error code.
 products:
   - support
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 ## Error 1002: DNS points to Prohibited IP
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
index 23dc25e82509737..e1345953169f933 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1004.mdx
@@ -19,3 +19,4 @@ This error indicates that the host is not configured to serve web traffic.
 ### Resolution
 
 If the issue persists beyond five minutes, [contact Cloudflare Support](/support/contacting-cloudflare-support/).
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
index 3f1e6d6819b72b2..0927129b5cce7e1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1009.mdx
@@ -19,3 +19,4 @@ The owner of the website (for example, `example.com`) has banned the country or
 
 - If you are a site visitor, contact the site owner and ask them to allow your IP address.
 - If you are the site owner, ensure that the reported IP address is allowed under the [IP Access rules](/waf/tools/ip-access-rules/) security feature.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
index 8c178fd7a6ca6f1..1f107b8f72b7f05 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
@@ -22,5 +22,6 @@ Another common cause is connecting a custom domain to an R2 bucket, where the do
 - To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/).
 - To allow connecting to a R2 bucket with a custom domain, disable the [zone hold](/fundamentals/account/account-security/zone-holds/) feature on the custom domain target zone to resolve the 1014 error.
 - To allow connections to an R2 bucket whose zone is banned:
+
   - First, check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one).
   - Second, make sure that you have no unpaid invoice(s), as you will not be able to enable any new services until [any outstanding balance](/billing/manage/pay-invoices-overdue-balances/) is addressed. If this does not resolve the issue, contact your account team.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
index 27a7f8ca892a5ae..9b401eee437c5d7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1035.mdx
@@ -27,4 +27,4 @@ For example, the following URI path rewrite expression is not valid:
 
 To fix the expression above, add a `/` prefix:
 
-`concat("/", lower(ip.src.country), http.request.uri.path)`
+`concat("/", lower(ip.src.country), http.request.uri.path)`
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
index a07128b006e1a78..8ca43a2009913cf 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1040.mdx
@@ -18,3 +18,4 @@ You are trying to modify an HTTP header that Request Header Transform Rules cann
 ### Resolution
 
 Make sure you are not trying to modify one of the [reserved HTTP request headers](/rules/transform/request-header-modification/#important-remarks).
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
index ca8eb720fb9b8ca..1468ee4c28b0408 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1102.mdx
@@ -57,3 +57,4 @@ To avoid exceeding memory limits:
 
 - [Error 1101](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1101/) - Workers JavaScript runtime exception
 - [Error 503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503/) - Service temporarily unavailable (can be caused by Workers CPU or memory limits)
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
index 064d799dd10135c..a31eb60f8fa2f99 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/index.mdx
@@ -32,6 +32,7 @@ For a complete description of this error refer to the [Error 1000](/support/trou
 
 For a complete description of this error refer to the [Error 1001](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/) page.
 
+
 ## Error 1002: DNS points to Prohibited IP
 
 For a complete description of this error refer to the [Error 1002: DNS points to Prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1002/#error-1002-dns-points-to-prohibited-ip) page.
@@ -84,10 +85,12 @@ For a complete description of this error refer to the [Error 1014](/support/trou
 
 For a complete description of this error refer to the [Error 1015](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1015/) page.
 
+
 ## Error 1016: Origin DNS error
 
 For a complete description of this error refer to the [Error 1016](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016/) page.
 
+
 ## Error 1018: Could not find host
 
 For a complete description of this error refer to the [Error 1018](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1018/) page.
@@ -151,3 +154,4 @@ For a complete description of this error refer to the [Error 1104](/support/trou
 ## Error 1200: Cache connection limit
 
 For a complete description of this error refer to the [Error 1200](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1200/) page.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
index aa184c991eb318f..137fd47bdd00bcb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-501.mdx
@@ -18,4 +18,4 @@ Cloudflare Workers returns a `501` error when a request uses an HTTP method that
 
 ### Resolution
 
-- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
+- Update the client to use a valid, standard [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods).
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
index 4f5ba4cb59b6c1d..f03079632ed610b 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503.mdx
@@ -52,10 +52,10 @@ If you are using Workers, check the Workers dashboard for error logs and resourc
 
 Use the error page content to determine whether a 503 was generated by Cloudflare or your origin server:
 
-| Signal                                                              | Interpretation                                                                                                                     |
-| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| Error page HTML contains `cloudflare` or `cloudflare-nginx`         | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
-| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly                                                                                             |
+| Signal | Interpretation |
+|--------|---------------|
+| Error page HTML contains `cloudflare` or `cloudflare-nginx` | Generated by Cloudflare — refer to [503 Error with cloudflare or cloudflare-nginx](#503-error-with-cloudflare-or-cloudflare-nginx) |
+| Error page HTML does not contain `cloudflare` or `cloudflare-nginx` | Your origin generated the 503 directly |
 
 ### Cloudflare-generated 503
 
@@ -64,3 +64,4 @@ A Cloudflare-generated 503 indicates a connectivity issue in a Cloudflare data c
 ### Origin-generated 503
 
 If your origin generated a 503, check origin server logs for signs of overload: CPU/memory saturation, exhausted connection pool, or application-level maintenance mode.
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
index c5e17a3afac58f5..1ce4d0ddda9a4a1 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx
@@ -68,3 +68,4 @@ To distinguish between the two, check the `CacheStatus` field in the same log re
 Do not conclude your origin returned a 5xx error solely because `OriginResponseStatus = 0`. Always check `CacheStatus` first to determine whether Cloudflare contacted the origin at all.
 
 :::
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
index a49d78dbb7cbe12..1759ae0d321392e 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522.mdx
@@ -21,6 +21,7 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 ### Resolution
 
 - Contact your hosting provider and share the [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist in troubleshooting these common causes:
+
   - [Cloudflare IP addresses](https://www.cloudflare.com/ips/) are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider allows **all Cloudflare IP ranges** (most common cause). You can use a [Cloudflare WAF Custom Rule](/waf/custom-rules/use-cases/block-by-geographical-location/) if you need to restrict traffic from geographical locations.
   - An overloaded or offline origin web server drops incoming requests.
   - [Keepalives](http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html) are disabled at the origin web server.
@@ -31,8 +32,9 @@ Two different timeouts cause HTTP error `522` depending on when they occur betwe
 
 - If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a `522` error. Consider using a [Route](/workers/configuration/routing/), targeting another hostname, or enabling the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) instead.
 
-- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`.
+- If you are using [Origin Rules](/rules/origin-rules/), make sure the resulting hostname can be resolved. For example, if your Origin Rule point to a Worker route, a `522` error will be returned if the hostname for this route is an A record pointing to a reserved address such as `100::` or `192.0.2.0`. 
 
 - If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before [contacting Cloudflare support](/support/contacting-cloudflare-support/):
+
   - An [MTR or traceroute](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#perform-a-traceroute) from your origin web server to a [Cloudflare IP address](http://www.cloudflare.com/ips) that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
   - Details from the hosting provider's investigation, such as pertinent logs or conversations with the hosting provider.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
index b075caaba321bfa..b67257eb3168ed7 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
@@ -18,6 +18,7 @@ The error `524` occurs if the origin web server acknowledges (ACK) the resource
 
 Error `524` can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/) (or 6.5 seconds in the case of [Cloudflare Images](/images/)). This timeout cannot be adjusted.
 
+
 ### Resolution at your origin
 
 Here are the options we suggest to work around this issue:
@@ -30,7 +31,7 @@ Here are the options we suggest to work around this issue:
 
 :::note
 
-Logging request response time at your origin web server may help identify the cause of resource slowness.
+Logging request response time at your origin web server may help identify the cause of resource slowness. 
 Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as [Apache](http://httpd.apache.org/docs/current/mod/mod_log_config.html) or [Nginx](http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format).
 :::
 
@@ -41,7 +42,7 @@ Here are some other actions you can take on the Cloudflare side:
 - If you regularly run HTTP requests that take over 120 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
 - Enterprise customers can increase the `524` timeout up to 6,000 seconds:
   - If your content can be cached, you can create a [Cache Rule](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only) with the `Proxy Read Timeout` setting. The content needs to be cacheable for the rule to be triggered, but does not need to be cached.
-  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/).
+  - You can increase the `proxy_read_timeout` setting for the whole zone using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/). 
 
 :::note
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
index 1e57ec517869150..5278dcbd17ebc5f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525.mdx
@@ -43,4 +43,4 @@ If `525` errors occur intermittently, review the origin web server error logs to
 
 - [Review the cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/) used by your server to ensure they are compatible with Cloudflare.
 
-- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
+- Check your server's error logs from the timestamps when `525` errors occur to identify any issues causing the connection to be reset during the SSL handshake.
\ No newline at end of file
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
index 1bd602ef3df5764..d438cc1893edcbb 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/index.mdx
@@ -46,7 +46,7 @@ To view Error Analytics:
 
 ### Log Explorer
 
-[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform.
+[Log Explorer](/log-explorer/) provides access to Cloudflare logs with all the context available within the Cloudflare platform. 
 You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search.
 Log explorer [allows to build queries](/log-explorer/log-search/) filtering for specific Ray ID, which can be useful to investigate HTTP Errors.
 
@@ -72,6 +72,7 @@ For a complete description of this error refer to the [Error 503](/support/troub
 
 For a complete description of this error refer to the [Error 520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/) page.
 
+
 ## Error 521: web server is down
 
 For a complete description of this error refer to the [Error 521](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) page.
@@ -84,14 +85,17 @@ For a complete description of this error refer to the [Error 522](/support/troub
 
 For a complete description of this error refer to the [Error 523](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) page.
 
+
 ## Error 524: a timeout occurred
 
 For a complete description of this error refer to the [Error 524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) page.
 
+
 ## Error 525: SSL handshake failed
 
 For a complete description of this error refer to the [Error 525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/) page.
 
+
 ## Error 526: invalid SSL certificate
 
 For a complete description of this error refer to the [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) page.
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
index ec947473bacdc11..f0c29b1fb117d8a 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-error-headers.mdx
@@ -28,8 +28,9 @@ Reproduce the error and inspect response headers using one of:
 
 ## Using cf-error-type for diagnosis
 
-| `cf-error-type` prefix | Origin              | Next step                                              |
-| ---------------------- | ------------------- | ------------------------------------------------------ |
-| `1xxx`                 | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
-| `1101` / `1102`        | Workers runtime     | Check `wrangler tail` for the exception                |
-| `52x`                  | Origin connectivity | Check origin server is up and reachable                |
+| `cf-error-type` prefix | Origin | Next step |
+|---|---|---|
+| `1xxx` | DNS / routing layer | Check DNS records; verify no Cloudflare IP in A record |
+| `1101` / `1102` | Workers runtime | Check `wrangler tail` for the exception |
+| `52x` | Origin connectivity | Check origin server is up and reachable |
+
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
index 6c1c9d2be8a69d7..01c72d0bc87c34f 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for HTTP Status Codes support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/index.mdx b/src/content/docs/support/troubleshooting/index.mdx
index 03006375415d51d..d81e4565fde34b9 100644
--- a/src/content/docs/support/troubleshooting/index.mdx
+++ b/src/content/docs/support/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Troubleshooting support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
index 09b614cc99e93e2..3594cec54c60318 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/index.mdx
@@ -8,7 +8,7 @@ products:
   - support
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Below you will find links to the relevant sections for Restoring Visitor IPs support-focused material.
 
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
index e1a34f3e2f2c079..dd9d3148e61c91c 100644
--- a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
+++ b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
@@ -216,7 +216,7 @@ Use the [`ngx_http_realip_module` Nginx module](http://nginx.org/en/docs/http/ng
 
 ```
 #example IP address
-set_real_ip_from 192.0.2.1;
+set_real_ip_from 192.0.2.1; 
 
 #use any of the following two
 
@@ -463,7 +463,6 @@ For more details, refer to [Custom header original IP detection extension](https
 If you are running an application behind [Caddy](https://caddyserver.com/) that relies on the `X-Forwarded-For` header, you can configure Caddy to override the header with Cloudflare's [CF-Connecting-IP header](/fundamentals/reference/http-headers/#cf-connecting-ip).
 
 It is advised that you also only accept traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/); otherwise, the header could be spoofed. That's why, in the second example, we handle this as part of the Caddy configuration. Alternatively, you can handle this at the firewall level, which is usually easier to automate. If you already have a firewall or other measure in place to ensure this, your Caddyfile could look like this:
-
 ```txt title="Caddyfile"
 https://example.com {
     reverse_proxy localhost:8080 {
@@ -474,7 +473,6 @@ https://example.com {
 ```
 
 If you want Caddy to handle only accepting traffic from [Cloudflare's IP addresses](https://www.cloudflare.com/ips/), you can use a configuration like this one:
-
 ```txt title="Caddyfile"
 https://example.com {
     # Restrict access to Cloudflare IPs (https://www.cloudflare.com/ips/)
@@ -496,7 +494,6 @@ https://example.com {
     }
 }
 ```
-
 ---
 
 ## Related Resources
diff --git a/src/content/docs/tenant/how-to/index.mdx b/src/content/docs/tenant/how-to/index.mdx
index 5b478d437d47b4b..036aa6d32db9c09 100644
--- a/src/content/docs/tenant/how-to/index.mdx
+++ b/src/content/docs/tenant/how-to/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/tenant/index.mdx b/src/content/docs/tenant/index.mdx
index a9bea30e67a18fc..f669fc53278a372 100644
--- a/src/content/docs/tenant/index.mdx
+++ b/src/content/docs/tenant/index.mdx
@@ -19,7 +19,7 @@ These APIs are built into our Client v4 API library to provide a streamlined onb
 
 As you dive into the Tenant API, take advantage of the following resources:
 
-- [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
-- [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
-- [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
-- [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
+* [Tenant structure](/tenant/structure/) explains some basic ideas behind the Tenant API and how it works.
+* [Get started](/tenant/get-started/) provides the quickest path to get your customer accounts up and running.
+* [How to](/tenant/how-to/) offers step-by-step instructions for specific tasks.
+* [Reference topics](/tenant/reference/) contains detailed information about the Tenant API, including a list of available zone and account-level subscriptions.
diff --git a/src/content/docs/tenant/reference/index.mdx b/src/content/docs/tenant/reference/index.mdx
index cc579a35dcc72f4..ed9d4e28bbe4895 100644
--- a/src/content/docs/tenant/reference/index.mdx
+++ b/src/content/docs/tenant/reference/index.mdx
@@ -8,6 +8,6 @@ products:
   - tenant
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/terraform/advanced-topics/best-practices.mdx b/src/content/docs/terraform/advanced-topics/best-practices.mdx
index 8bc08838c5a7125..e3dd89c7e78f2e0 100644
--- a/src/content/docs/terraform/advanced-topics/best-practices.mdx
+++ b/src/content/docs/terraform/advanced-topics/best-practices.mdx
@@ -189,8 +189,10 @@ Using modules also increases the difficulty of debugging or reproducing issues a
 
 :::caution
 
+
 This advice also applies to [Terraform dynamic blocks](https://www.terraform.io/language/expressions/dynamic-blocks) that allow you to do logic in your HCL. Since these dynamic blocks are always evaluated, you can get yourself into situations where you have logic bugs in your configuration (and making the end result unreproducible).
 
+
 :::
 
 ## Migrate resources into Terraform
diff --git a/src/content/docs/terraform/how-to/create-partial-zone.mdx b/src/content/docs/terraform/how-to/create-partial-zone.mdx
index b6532b8ca83d6a4..7ddc5bbf8335cb9 100644
--- a/src/content/docs/terraform/how-to/create-partial-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-partial-zone.mdx
@@ -39,7 +39,6 @@ resource "cloudflare_zone" "subdomain_example_com" {
 ```
 
 Then, in a new Terraform plan and apply cycle, upgrade the zone to a Business plan or higher:
-
 ```hcl
 resource "cloudflare_zone_subscription" "example_zone_subscription" {
   zone_id = cloudflare_zone.subdomain_example_com.id
@@ -73,4 +72,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Partial zone setup](/dns/zone-setups/partial-setup/)
 - [Convert a full zone to partial](/dns/zone-setups/conversions/convert-full-to-partial/)
-- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
+- [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
\ No newline at end of file
diff --git a/src/content/docs/terraform/how-to/create-secondary-zone.mdx b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
index ab90c9a7bf683c7..df90ad68810ec8a 100644
--- a/src/content/docs/terraform/how-to/create-secondary-zone.mdx
+++ b/src/content/docs/terraform/how-to/create-secondary-zone.mdx
@@ -13,9 +13,7 @@ products:
 ---
 
 A [subdomain zone](/dns/zone-setups/subdomain-setup/) lets you manage a subdomain in a separate Cloudflare zone from the parent domain. This is useful for access control and team management. This guide shows how to automate the setup using the [Cloudflare Terraform provider](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs). It is only available for Enterprise accounts
-
 > NOTE: subdomain setup is only available for Enterprise accounts
-
 ## Prerequisites
 
 - Terraform installed. Refer to [Get started](/terraform/installing/).
@@ -45,4 +43,4 @@ Refer to the [cloudflare_zone docs](https://registry.terraform.io/providers/clou
 
 - [Subdomain setup](/dns/zone-setups/subdomain-setup/)
 - [`cloudflare_zone` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone)
-- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
+- [`cloudflare_dns_record` resource](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record)
\ No newline at end of file
diff --git a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
index 4fe8686bb0585da..2ab6af754503c16 100644
--- a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
+++ b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx
@@ -24,4 +24,4 @@ Use this:
 
 ```txt "zones[0]"
 zone_id = data.cloudflare_zones.example_com.zones[0].id`
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/terraform/tutorial/index.mdx b/src/content/docs/terraform/tutorial/index.mdx
index 0a16482753a93c7..9eb9b90d3aaf527 100644
--- a/src/content/docs/terraform/tutorial/index.mdx
+++ b/src/content/docs/terraform/tutorial/index.mdx
@@ -10,41 +10,41 @@ products:
 
 Before you begin, [install Terraform](/terraform/installing/). Each tutorial builds on the previous, so you should complete the tutorials in the order shown below.
 
-:::note
+:::note 
 If you are upgrading from v4, review the [migration guide](https://github.com/cloudflare/terraform-provider-cloudflare/blob/main/docs/guides/version-5-upgrade.md) for breaking changes.
 :::
 
 ## [1 – Initialize Terraform](/terraform/tutorial/initialize-terraform/)
 
-- Brief introduction.
-- Introduction of `terraform init`, `plan`, `apply`, and `show`.
-- Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
+* Brief introduction.
+* Introduction of `terraform init`, `plan`, `apply`, and `show`.
+* Resource covered: [`cloudflare_dns_record`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/dns_record) (DNS record).
 
 ## [2 – Track your history](/terraform/tutorial/track-history/)
 
-- Store Cloudflare configuration in source control.
+* Store Cloudflare configuration in source control.
 
 ## [3 – Configure HTTPS settings](/terraform/tutorial/configure-https-settings/)
 
-- Modify zone settings.
-- Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
+* Modify zone settings.
+* Resource covered: [`cloudflare_zone_setting`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_setting).
 
 ## [4 – Improve performance and reliability](/terraform/tutorial/use-load-balancing/)
 
-- Add load balancing rules.
-- Resources covered:
-  - [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
-  - [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
-  - [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
+* Add load balancing rules.
+* Resources covered:
+  * [`cloudflare_load_balancer`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer)
+  * [`cloudflare_load_balancer_pool`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_pool)
+  * [`cloudflare_load_balancer_monitor`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/load_balancer_monitor)
 
 ## [5 – Add exceptions with page rules](/terraform/tutorial/add-page-rules/)
 
-- Add page rule.
-- Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
-- Increase security level for a specific URL: `/expensive-db-call`.
-- Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
+* Add page rule.
+* Resource covered: [`cloudflare_page_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule).
+* Increase security level for a specific URL: `/expensive-db-call`.
+* Add a redirect (URL forward) with a `301` status code from `/old-location.php` to `/expensive-db-call`.
 
 ## [6 – Revert configuration](/terraform/tutorial/revert-configuration/)
 
-- Review change history.
-- Roll back changes.
+* Review change history.
+* Roll back changes.
diff --git a/src/content/docs/time-services/index.mdx b/src/content/docs/time-services/index.mdx
index e0533cac714f018..28cf018d1d9c55a 100644
--- a/src/content/docs/time-services/index.mdx
+++ b/src/content/docs/time-services/index.mdx
@@ -12,7 +12,7 @@ products:
 description: Synchronize time with Cloudflare NTP, NTS, and Roughtime.
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Learn more about Cloudflare’s suite of time services.
 
diff --git a/src/content/docs/time-services/roughtime/index.mdx b/src/content/docs/time-services/roughtime/index.mdx
index fa744d4dd0b4954..c63fcd5c61e6ed3 100644
--- a/src/content/docs/time-services/roughtime/index.mdx
+++ b/src/content/docs/time-services/roughtime/index.mdx
@@ -16,7 +16,7 @@ Endpoints on the Internet often synchronize their clocks using the [Network Time
 
 As a result, a man-in-the-middle attacker can easily influence a victim’s clock. By moving them back in time, the attacker can, for example, force a victim to accept an expired (and possibly compromised) TLS certificate or session ticket.
 
-For many applications, _precise_ network time is not essential. It is sufficient to have _accurate_ time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
+For many applications, *precise* network time is not essential. It is sufficient to have *accurate* time to mitigate these kinds of attacks, such as within 10 seconds of real time. This observation is the primary motivation behind Roughtime.
 
 ## Next steps
 
diff --git a/src/content/docs/time-services/roughtime/recipes.mdx b/src/content/docs/time-services/roughtime/recipes.mdx
index c7873f7d93f6904..47cfdd6f2bd8e21 100644
--- a/src/content/docs/time-services/roughtime/recipes.mdx
+++ b/src/content/docs/time-services/roughtime/recipes.mdx
@@ -21,28 +21,28 @@ formatted as a JSON object. For example:
 
 ```json
 {
-	"servers": [
-		{
-			"name": "Cloudflare-Roughtime-2",
-			"publicKeyType": "ed25519",
-			"publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
-			"addresses": [
-				{
-					"protocol": "udp",
-					"address": "roughtime.cloudflare.com:2003"
-				}
-			]
-		}
-	]
+  "servers": [
+    {
+      "name": "Cloudflare-Roughtime-2",
+      "publicKeyType": "ed25519",
+      "publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
+      "addresses": [
+        {
+          "protocol": "udp",
+          "address": "roughtime.cloudflare.com:2003"
+        }
+      ]
+    }
+  ]
 }
 ```
 
-It includes each server's _root public key_. When the server starts, it
-generates an _online_ public/secret key pair. The root secret key is used to create a _delegation_ for the online public key and the online secret key is used to sign the response.
+It includes each server's *root public key*. When the server starts, it
+generates an *online* public/secret key pair. The root secret key is used to create a *delegation* for the online public key and the online secret key is used to sign the response.
 
 The delegation serves the same function as a traditional [X.509 certificate](https://en.wikipedia.org/wiki/X.509) on the web. The client first uses the root public key to verify the delegation, then uses the online public key to verify the response.
 
-Because the response is _auditable_, the protocol makes each client accountable to provide accurate time.
+Because the response is *auditable*, the protocol makes each client accountable to provide accurate time.
 
 The configuration also encodes the type of signature algorithm used by the
 server (currently only [Ed25519](https://en.wikipedia.org/wiki/EdDSA) is supported). Lastly, the configuration contains a list of addresses where the service can be reached and which transport protocol to use to reach them (currently only UDP is supported).
diff --git a/src/content/docs/time-services/tos.mdx b/src/content/docs/time-services/tos.mdx
index 3045d87449c98de..919e1a6c1d5e131 100644
--- a/src/content/docs/time-services/tos.mdx
+++ b/src/content/docs/time-services/tos.mdx
@@ -8,4 +8,4 @@ products:
 description: Cloudflare Time Services terms of use.
 ---
 
-By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
+By using Cloudflare's suite of time services, you agree to [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/).
\ No newline at end of file
diff --git a/src/content/docs/tunnel/advanced/origin-parameters.mdx b/src/content/docs/tunnel/advanced/origin-parameters.mdx
index 8b0a1173bb017e7..765569e743882e5 100644
--- a/src/content/docs/tunnel/advanced/origin-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/origin-parameters.mdx
@@ -13,13 +13,11 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/origin-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/tunnel/advanced/local-management/configuration-file/",
-		kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
-		validatingJwtURL:
-			"/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/",
-	}}
+  file="tunnel/origin-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
+    kubectlTutorialURL: "/cloudflare-one/tutorials/kubectl/",
+    validatingJwtURL: "/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json/"
+  }}
 />
diff --git a/src/content/docs/tunnel/advanced/run-parameters.mdx b/src/content/docs/tunnel/advanced/run-parameters.mdx
index 61f30d9abf493ba..3024141c055de62 100644
--- a/src/content/docs/tunnel/advanced/run-parameters.mdx
+++ b/src/content/docs/tunnel/advanced/run-parameters.mdx
@@ -13,17 +13,15 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel/run-parameters"
-	product="cloudflare-one"
-	params={{
-		configurationFileURL:
-			"/tunnel/advanced/local-management/configuration-file/",
-		metricsURL: "/tunnel/monitoring/#metrics",
-		usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
-		tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
-		tunnelPermissionsURL:
-			"/tunnel/advanced/local-management/tunnel-permissions/",
-		createRemoteTunnelURL: "/tunnel/get-started/",
-		faqURL: "/tunnel/troubleshooting/",
-	}}
+  file="tunnel/run-parameters"
+  product="cloudflare-one"
+  params={{
+    configurationFileURL: "/tunnel/advanced/local-management/configuration-file/",
+    metricsURL: "/tunnel/monitoring/#metrics",
+    usageMetricsURL: "/tunnel/monitoring/#cloudflared-metrics",
+    tunnelWithFirewallURL: "/tunnel/configuration/#us-region-configuration",
+    tunnelPermissionsURL: "/tunnel/advanced/local-management/tunnel-permissions/",
+    createRemoteTunnelURL: "/tunnel/get-started/",
+    faqURL: "/tunnel/troubleshooting/"
+  }}
 />
diff --git a/src/content/docs/tunnel/changelog.mdx b/src/content/docs/tunnel/changelog.mdx
index dd0771082a7b9ac..9a0b8f86b225617 100644
--- a/src/content/docs/tunnel/changelog.mdx
+++ b/src/content/docs/tunnel/changelog.mdx
@@ -12,4 +12,7 @@ import { ProductChangelog } from "~/components";
 
 {/* <!-- All changelog entries live in src/content/changelog/tunnel/. */}
 
-<ProductChangelog product="tunnel" hideEntry="2024-06-16-cloudflare-one" />
+<ProductChangelog
+	product="tunnel"
+	hideEntry="2024-06-16-cloudflare-one"
+/>
\ No newline at end of file
diff --git a/src/content/docs/tunnel/deployment-guides/terraform.mdx b/src/content/docs/tunnel/deployment-guides/terraform.mdx
index cc28a315060b536..13890c8c111c1c4 100644
--- a/src/content/docs/tunnel/deployment-guides/terraform.mdx
+++ b/src/content/docs/tunnel/deployment-guides/terraform.mdx
@@ -80,6 +80,7 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr
 
 ### Create a startup script
 
+
 <Render file="terraform/startup-script" product="cloudflare-one" />
 
 ## 6. Deploy Terraform
diff --git a/src/content/docs/tunnel/downloads/system-requirements.mdx b/src/content/docs/tunnel/downloads/system-requirements.mdx
index df9a49384ea6c6e..252a3704e2bda8c 100644
--- a/src/content/docs/tunnel/downloads/system-requirements.mdx
+++ b/src/content/docs/tunnel/downloads/system-requirements.mdx
@@ -17,11 +17,7 @@ import { Render, TunnelCalculator } from "~/components";
 Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availability) on two dedicated hosts per location with a minimum of 4 GB RAM and 4 CPU cores. Allocate 50,000 ports per host.
 
 ## Port configuration
-
-<Render
-	file="tunnel/availability/port-configuration"
-	product="cloudflare-one"
-/>
+<Render file="tunnel/availability/port-configuration" product="cloudflare-one" />
 
 ## ulimits (Linux and macOS)
 
@@ -30,7 +26,6 @@ Run a `cloudflared` [replica](/tunnel/configuration/#replicas-and-high-availabil
 ## Capacity calculator
 
 To estimate tunnel capacity requirements for your deployment:
-
 1. Use the [metrics endpoint](/tunnel/monitoring/#cloudflared-metrics) to measure `cloudflared_tcp_total_sessions` and `cloudflared_udp_total_sessions`.
 2. Compute the average **TCP requests per second** by dividing `cloudflared_tcp_total_sessions` by total time.
 3. Compute the average **Non-DNS UDP requests per second** by dividing `cloudflared_udp_total_sessions` by total time.
diff --git a/src/content/docs/tunnel/troubleshooting.mdx b/src/content/docs/tunnel/troubleshooting.mdx
index 06fba9a65a218a4..0c02d1a8ecf4b9a 100644
--- a/src/content/docs/tunnel/troubleshooting.mdx
+++ b/src/content/docs/tunnel/troubleshooting.mdx
@@ -121,7 +121,6 @@ As a quick test, run:
 ```sh
 curl -v https://region1.v2.argotunnel.com:7844
 ```
-
 If the connection hangs, traffic is being dropped between your host and Cloudflare.
 
 To test if `cloudflared` can connect on port `7844`, run:
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
index b2a3eaa4e14958f..51b265f76e5f1f0 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/any-hostname.mdx
@@ -7,6 +7,7 @@ products:
 sidebar:
   order: 4
   label: Any Hostname
+
 ---
 
 The Any Hostname feature removes the requirement to specify hostnames during widget creation, allowing widgets to function on any domain.
@@ -23,37 +24,31 @@ When using the Any Hostname feature, it is essential to implement additional val
 
 ```js title="Example response"
 async function validateTurnstileWithHostname(token, expectedHostnames = []) {
-	const response = await fetch(
-		"https://challenges.cloudflare.com/turnstile/v0/siteverify",
-		{
-			method: "POST",
-			headers: { "Content-Type": "application/json" },
-			body: JSON.stringify({
-				secret: process.env.TURNSTILE_SECRET,
-				response: token,
-			}),
-		},
-	);
-
-	const result = await response.json();
-
-	if (!result.success) {
-		return { valid: false, error: "Token validation failed" };
-	}
-
-	// Additional hostname validation when using Any Hostname
-	if (
-		expectedHostnames.length > 0 &&
-		!expectedHostnames.includes(result.hostname)
-	) {
-		return {
-			valid: false,
-			error: "Hostname not in allowed list",
-			hostname: result.hostname,
-		};
-	}
-
-	return { valid: true, data: result };
+  const response = await fetch('https://challenges.cloudflare.com/turnstile/v0/siteverify', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      secret: process.env.TURNSTILE_SECRET,
+      response: token
+    })
+  });
+
+  const result = await response.json();
+
+  if (!result.success) {
+    return { valid: false, error: 'Token validation failed' };
+  }
+
+  // Additional hostname validation when using Any Hostname
+  if (expectedHostnames.length > 0 && !expectedHostnames.includes(result.hostname)) {
+    return { 
+      valid: false, 
+      error: 'Hostname not in allowed list',
+      hostname: result.hostname 
+    };
+  }
+
+  return { valid: true, data: result };
 }
 ```
 
@@ -63,12 +58,10 @@ Use `action` and `cData` parameters to track widget usage sources.
 
 ```html
 <!-- Widget with tracking information -->
-<div
-	class="cf-turnstile"
-	data-sitekey="your-site-key"
-	data-action="customer-portal"
-	data-cdata="tenant-123"
-></div>
+<div class="cf-turnstile" 
+     data-sitekey="your-site-key"
+     data-action="customer-portal"
+     data-cdata="tenant-123"></div>
 ```
 
 ---
@@ -80,4 +73,4 @@ The Any Hostname feature is particularly valuable for customers with:
 - Large domain portfolios with many domains to manage individually.
 - Dynamic subdomain creation and frequently create subdomains or customer-specific domains.
 - Multi-tenant applications such as SaaS platforms serving multiple customer domains.
-- Development environments that test across various staging and development domains.
+- Development environments that test across various staging and development domains.
\ No newline at end of file
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
index a54d5062f8d33e7..2ec95bf7163dc6f 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx
@@ -6,9 +6,10 @@ products:
   - turnstile
 sidebar:
   order: 2
+
 ---
 
-import { DashButton, Steps, Tabs, TabItem, Details } from "~/components";
+import { DashButton, Steps, Tabs, TabItem, Details } from "~/components"
 
 Hostname management controls where your Turnstile widgets can be used by specifying which domains are authorized to load and execute your widgets. This security measure prevents unauthorized use of your widgets on domains that you do not control.
 
@@ -35,7 +36,7 @@ The following formats are not valid and will not be accepted:
 - Schemes such as `http://example.com` or `https://example.com`
 - Ports such as `example.com:443` or `subdomain.example.com:8080`
 - Paths such as `example.com/path` or `subdomain.example.com/login`
-  :::
+:::
 
 ### Subdomain behavior
 
diff --git a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
index c8b59dade309ca5..eaa623056629f2a 100644
--- a/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
+++ b/src/content/docs/turnstile/additional-configuration/hostname-management/pre-clearance.mdx
@@ -8,6 +8,7 @@ tags:
   - Cookies
 sidebar:
   order: 3
+
 ---
 
 [Pre-clearance](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) allows Turnstile to issue clearance cookies that can be used across your Cloudflare-protected domains. This feature requires specific hostname configuration for proper functionality.
@@ -16,18 +17,18 @@ sidebar:
 
 For pre-clearance to work correctly, you must:
 
-1. Use a registered Cloudflare zone.
-
-   The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones.
-
-2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance.
+1. Use a registered Cloudflare zone. 
 
-   The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile.
+    The hostname must be a zone registered in your Cloudflare account. When configuring your widget via the dashboard, you can select from existing zones. 
 
-   For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`.
+2. Select the registered Cloudflare zone with intended WAF rule to set pre-clearance. 
+    
+    The zone you select must contain the WAF rule you wish to set pre-clearance through Turnstile. 
+    
+    For example, if you have `example.com` and `app.example.com` as registered zones and you want to have Turnstile issue pre-clearance for `app.example.com`, you must select `app.example.com`. 
 
 ## Validation
 
 The clearance cookie `cf_clearance` will only be accepted on domains that match the widget's configured hostnames, are registered as zones in your Cloudflare account, and have challenges enabled through Cloudflare's security settings.
 
-If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
+If pre-clearance is configured incorrectly, clearance cookies may become invalid and lead to additional challenge requests.
\ No newline at end of file
diff --git a/src/content/docs/turnstile/additional-configuration/index.mdx b/src/content/docs/turnstile/additional-configuration/index.mdx
index c1dd255c43c229e..fa53423d1ca145e 100644
--- a/src/content/docs/turnstile/additional-configuration/index.mdx
+++ b/src/content/docs/turnstile/additional-configuration/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile's additional configurations:
 
diff --git a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
index ff23f12fc0c683d..f4882feb0c77f50 100644
--- a/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
+++ b/src/content/docs/turnstile/additional-configuration/pre-clearance-support.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile
 sidebar:
   order: 3
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/turnstile/concepts/challenges.mdx b/src/content/docs/turnstile/concepts/challenges.mdx
index 2049cf0d9334a17..fa67c9f121a081a 100644
--- a/src/content/docs/turnstile/concepts/challenges.mdx
+++ b/src/content/docs/turnstile/concepts/challenges.mdx
@@ -7,4 +7,5 @@ products:
 external_link: /cloudflare-challenges/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/turnstile/concepts/index.mdx b/src/content/docs/turnstile/concepts/index.mdx
index f8bdd001acb61db..4545231c8047916 100644
--- a/src/content/docs/turnstile/concepts/index.mdx
+++ b/src/content/docs/turnstile/concepts/index.mdx
@@ -8,10 +8,11 @@ sidebar:
   order: 3
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile's concepts:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/extensions/google-firebase.mdx b/src/content/docs/turnstile/extensions/google-firebase.mdx
index 7ecd2d24ede91af..2456c9d7c189b62 100644
--- a/src/content/docs/turnstile/extensions/google-firebase.mdx
+++ b/src/content/docs/turnstile/extensions/google-firebase.mdx
@@ -10,9 +10,10 @@ tags:
 sidebar:
   order: 2
   label: Google Firebase
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 Turnstile is [available as an extension](https://extensions.dev/extensions/cloudflare/cloudflare-turnstile-app-check-provider) with [Google's Firebase](https://firebase.google.com/) platform as an [App Check](https://firebase.google.com/docs/app-check) provider. You can leverage Cloudflare Turnstile's bot detection and challenge capabilities to ensure that requests to your Firebase backend services are verified and only authentic human visitors can interact with your application.
 
@@ -118,25 +119,25 @@ const expressApp = express();
 const firebaseApp = initializeApp();
 
 const appCheckVerification = async (req, res, next) => {
-	const appCheckToken = req.header("X-Firebase-AppCheck");
+    const appCheckToken = req.header("X-Firebase-AppCheck");
 
-	if (!appCheckToken) {
-		res.status(401);
-		return next("Unauthorized");
-	}
+    if (!appCheckToken) {
+        res.status(401);
+        return next("Unauthorized");
+    }
 
-	try {
-		const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
+    try {
+        const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);
 
-		// If verifyToken() succeeds, continue with the next middleware function in the stack.
-		return next();
-	} catch (err) {
-		res.status(401);
-		return next("Unauthorized");
-	}
-};
+        // If verifyToken() succeeds, continue with the next middleware function in the stack.
+        return next();
+    } catch (err) {
+        res.status(401);
+        return next("Unauthorized");
+    }
+}
 
 expressApp.get("/yourApiEndpoint", [appCheckVerification], (req, res) => {
-	// Handle request.
+    // Handle request.
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/extensions/index.mdx b/src/content/docs/turnstile/extensions/index.mdx
index e7d4e7afeae3a2f..2649807908e1165 100644
--- a/src/content/docs/turnstile/extensions/index.mdx
+++ b/src/content/docs/turnstile/extensions/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 9
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile extensions:
 
diff --git a/src/content/docs/turnstile/extensions/pages-plugin.mdx b/src/content/docs/turnstile/extensions/pages-plugin.mdx
index 963a6bb4dee2004..e3a41748a59f3ca 100644
--- a/src/content/docs/turnstile/extensions/pages-plugin.mdx
+++ b/src/content/docs/turnstile/extensions/pages-plugin.mdx
@@ -7,4 +7,5 @@ title: Pages Plugin
 external_link: /pages/functions/plugins/turnstile/
 sidebar:
   order: 1
+
 ---
diff --git a/src/content/docs/turnstile/extensions/waiting-room.mdx b/src/content/docs/turnstile/extensions/waiting-room.mdx
index 1153676741e4dc1..474416b1df638c3 100644
--- a/src/content/docs/turnstile/extensions/waiting-room.mdx
+++ b/src/content/docs/turnstile/extensions/waiting-room.mdx
@@ -7,4 +7,5 @@ title: Waiting Room Analytics
 external_link: /waiting-room/waiting-room-analytics/#turnstile-widget-traffic
 sidebar:
   order: 3
+
 ---
diff --git a/src/content/docs/turnstile/get-started/widget-management/api.mdx b/src/content/docs/turnstile/get-started/widget-management/api.mdx
index 9c0738b7d0d5cda..4342df29d7ee58e 100644
--- a/src/content/docs/turnstile/get-started/widget-management/api.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/api.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - REST API
 sidebar:
-  order: 2
-  label: API
+    order: 2
+    label: API
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Use the [Cloudflare API](/api/resources/turnstile/) for programmatic widget management and automation.
 
@@ -25,44 +25,47 @@ Before you begin, you must have:
 ### Create a widget via the API
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets"
-	method="POST"
-	json={{
-		domains: ["example.com"],
-		mode: "managed",
-		name: "My Example Turnstile Widget",
-	}}
+  path="/accounts/{account_id}/challenges/widgets"
+  method="POST"
+  json={{
+    domains: ["example.com"],
+    mode: "managed",
+    name: "My Example Turnstile Widget",
+  }}
 />
 
 ### Manage widgets via the API
 
-<APIRequest path="/accounts/{account_id}/challenges/widgets" method="GET" />
-
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="GET"
+  path="/accounts/{account_id}/challenges/widgets"
+  method="GET"
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="PUT"
-	json={{
-		domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
-		mode: "invisible",
-		name: "blog.cloudflare.com login form",
-		clearance_level: "interactive",
-	}}
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="GET"
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
-	method="POST"
-	json={{
-		invalidate_immediately: false,
-	}}
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="PUT"
+  json={{
+    domains: ["203.0.113.1", "cloudflare.com", "blog.example.com"],
+    mode: "invisible",
+    name: "blog.cloudflare.com login form",
+    clearance_level: "interactive",
+  }}
 />
 
 <APIRequest
-	path="/accounts/{account_id}/challenges/widgets/{sitekey}"
-	method="DELETE"
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}/rotate_secret"
+  method="POST"
+  json={{
+    invalidate_immediately: false,
+  }}
 />
+
+<APIRequest
+  path="/accounts/{account_id}/challenges/widgets/{sitekey}"
+  method="DELETE"
+/>
\ No newline at end of file
diff --git a/src/content/docs/turnstile/get-started/widget-management/index.mdx b/src/content/docs/turnstile/get-started/widget-management/index.mdx
index 70a4816c948455b..bcb9b3c62a9e45f 100644
--- a/src/content/docs/turnstile/get-started/widget-management/index.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/index.mdx
@@ -11,8 +11,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about managing Turnstile widgets:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
index 22a01e0fa0389de..d39317f90ca363c 100644
--- a/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
+++ b/src/content/docs/turnstile/get-started/widget-management/terraform.mdx
@@ -7,11 +7,11 @@ products:
 tags:
   - Terraform
 sidebar:
-  order: 3
-  label: Terraform
+    order: 3
+    label: Terraform
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Manage Turnstile widgets as code using Terraform for version control and automated deployments.
 
@@ -153,7 +153,7 @@ locals {
 
 resource "cloudflare_turnstile_widget" "app_widget" {
   for_each = local.environments
-
+  
   account_id = var.account_id
   name       = "App Widget - ${each.key}"
   domains    = each.value.domains
@@ -195,4 +195,4 @@ cf-terraforming generate \
 ```shell title="Import existing widget"
 terraform import cloudflare_turnstile_widget.existing_widget \
   $ACCOUNT_ID/$WIDGET_SITEKEY
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/migration/hcaptcha.mdx b/src/content/docs/turnstile/migration/hcaptcha.mdx
index bbe32fd8f917c8d..87ff8fe69db29c4 100644
--- a/src/content/docs/turnstile/migration/hcaptcha.mdx
+++ b/src/content/docs/turnstile/migration/hcaptcha.mdx
@@ -46,7 +46,7 @@ Turnstile supports:
 
 - the `render()` call
 - hCaptcha invisible mode with the `execute()` call
-  :::
+:::
 
 ## Server-side integration
 
diff --git a/src/content/docs/turnstile/reference/index.mdx b/src/content/docs/turnstile/reference/index.mdx
index 0f952082dda1ea1..ed8c7d7668f0cc2 100644
--- a/src/content/docs/turnstile/reference/index.mdx
+++ b/src/content/docs/turnstile/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 10
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about Turnstile:
 
diff --git a/src/content/docs/turnstile/reference/supported-browsers.mdx b/src/content/docs/turnstile/reference/supported-browsers.mdx
index 837dbda385d3c26..28bdb4eb396bfad 100644
--- a/src/content/docs/turnstile/reference/supported-browsers.mdx
+++ b/src/content/docs/turnstile/reference/supported-browsers.mdx
@@ -7,4 +7,5 @@ title: Supported browsers
 external_link: /cloudflare-challenges/reference/supported-browsers/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/turnstile/reference/supported-languages.mdx b/src/content/docs/turnstile/reference/supported-languages.mdx
index 8263d260812b2fd..f0338658d106a98 100644
--- a/src/content/docs/turnstile/reference/supported-languages.mdx
+++ b/src/content/docs/turnstile/reference/supported-languages.mdx
@@ -8,6 +8,7 @@ tags:
   - Localization
 sidebar:
   order: 3
+
 ---
 
 Turnstile supports `auto` (default), which uses the visitor's browser language if it is supported. You can also explicitly set the widget's language using the [client-side configuration attribute](/turnstile/get-started/client-side-rendering/#configurations) to one listed on the table below:
diff --git a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
index 8b37a576667565e..12e1785bd51cc86 100644
--- a/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
+++ b/src/content/docs/turnstile/reference/turnstile-privacy-addendum.mdx
@@ -7,4 +7,5 @@ title: Turnstile Privacy Addendum
 external_link: https://www.cloudflare.com/turnstile-privacy-policy/
 sidebar:
   order: 2
+
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
index b38f8de49356b2c..6a51837058ce17d 100644
--- a/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
+++ b/src/content/docs/turnstile/troubleshooting/challenge-solve-issues.mdx
@@ -7,4 +7,5 @@ title: Challenge solve issues
 external_link: /cloudflare-challenges/troubleshooting/challenge-solve-issues/
 sidebar:
   order: 4
+
 ---
diff --git a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
index e0c9bc9938840cc..fd6c9090b063095 100644
--- a/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/client-side-errors/index.mdx
@@ -9,21 +9,22 @@ tags:
   - JavaScript
 sidebar:
   order: 3
+
 ---
 
 import { Tabs, TabItem } from "~/components";
 
-There are instances where Turnstile may encounter problems, invoking the `error-callback`.
+There are instances where Turnstile may encounter problems, invoking the `error-callback`. 
 
-These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures.
+These problems can range from network connectivity issues and browser compatibility problems to configuration errors and challenge failures. 
 
-When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues.
+When errors occur, implementing proper error handling ensures your visitors receive helpful feedback and your application can recover from temporary issues. 
 
 Refer to the [Error codes](/turnstile/troubleshooting/client-side-errors/error-codes/) for troubleshooting guidance to address specific error conditions.
 
 ## Error handling
 
-The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur.
+The `error-callback` option for explicitly rendering widgets and the `data-error-callback` attribute for implicit rendering provides a JavaScript callback to handle potential errors that occur. 
 
 This callback mechanism gives you complete control over how errors are presented to visitors and allows you to implement custom recovery strategies tailored to your application's needs.
 
@@ -57,30 +58,28 @@ An error callback will retrieve an error code as its first parameter. This error
 
 ```js wrap
 function handleTurnstileError(errorCode) {
-	const errorFamily = Math.floor(errorCode / 1000);
-
-	switch (errorFamily) {
-		case 100:
-			showMessage("Please refresh the page and try again.");
-			break;
-		case 110:
-			showMessage("Configuration error. Please contact support.");
-			break;
-		case 300:
-		case 600:
-			showMessage(
-				"Security check failed. Please try refreshing or using a different browser.",
-			);
-			break;
-		default:
-			showMessage("An unexpected error occurred. Please try again.");
-	}
+  const errorFamily = Math.floor(errorCode / 1000);
+  
+  switch(errorFamily) {
+    case 100:
+      showMessage('Please refresh the page and try again.');
+      break;
+    case 110:
+      showMessage('Configuration error. Please contact support.');
+      break;
+    case 300:
+    case 600:
+      showMessage('Security check failed. Please try refreshing or using a different browser.');
+      break;
+    default:
+      showMessage('An unexpected error occurred. Please try again.');
+  }
 }
 ```
 
 ## Retry
 
-By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention.
+By default, Turnstile will automatically retry upon encountering a problem, which helps handle transient network issues or temporary service disruptions without requiring user intervention. 
 
 This automatic retry mechanism is useful for [mobile visitors](/turnstile/get-started/mobile-implementation/) who may experience intermittent connectivity or visitors on networks with occasional stability issues.
 
@@ -89,34 +88,34 @@ When subsequent failures due to retries are observed, the error callback can be
 ```js wrap
 let retryCount = 0;
 
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	"error-callback": function (errorCode) {
-		retryCount++;
-
-		if (retryCount <= 2) {
-			console.log(`Turnstile retry attempt ${retryCount}`);
-			return false; // Let Turnstile handle the retry
-		} else {
-			showPersistentErrorMessage(errorCode);
-			return true; // We'll handle it from here
-		}
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  'error-callback': function(errorCode) {
+    retryCount++;
+    
+    if (retryCount <= 2) {
+      console.log(`Turnstile retry attempt ${retryCount}`);
+      return false; // Let Turnstile handle the retry
+    } else {
+      showPersistentErrorMessage(errorCode);
+      return true; // We'll handle it from here
+    }
+  }
 });
 ```
 
 You can adjust the retry behavior by setting the retry value to `never` instead of the default `auto`. This will result in Turnstile not automatically retrying, giving you control over when and how recovery attempts are made. If there is any issue or error verifying the visitor, the widget will not retry and will remain in the respective failure state until you take manual action.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	retry: "never",
-	"error-callback": function (errorCode) {
-		// You control all retry logic
-		setTimeout(() => {
-			turnstile.reset("#my-widget");
-		}, 3000);
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  retry: 'never',
+  'error-callback': function(errorCode) {
+    // You control all retry logic
+    setTimeout(() => {
+      turnstile.reset('#my-widget');
+    }, 3000);
+  }
 });
 ```
 
@@ -125,11 +124,11 @@ You may call `turnstile.reset()` in the corresponding `error-callback` to manual
 The interval between retries for Turnstile can be configured by the `retry-interval` option, allowing you to optimize retry timing for your visitors’ typical network conditions. A longer interval may be more appropriate for visitors on slower or less reliable connections, while shorter intervals work well in environments with typically stable connectivity.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	retry: "auto",
-	"retry-interval": 8000, // Wait 8 seconds between retries
-	"error-callback": handleError,
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  retry: 'auto',
+  'retry-interval': 8000, // Wait 8 seconds between retries
+  'error-callback': handleError
 });
 ```
 
@@ -142,23 +141,23 @@ For instance, in a scenario where the Turnstile widget is implemented within a f
 In such instances, the `timeout-callback` of the widget is activated, enabling the widget to reset itself as needed and provide appropriate guidance. This callback allows you to implement user-friendly timeout handling, such as highlighting the Turnstile widget, displaying a notification, or automatically refreshing the challenge.
 
 ```js wrap
-turnstile.render("#my-widget", {
-	sitekey: "your-sitekey",
-	callback: function (token) {
-		console.log("Challenge completed successfully");
-	},
-	"timeout-callback": function () {
-		console.log("Challenge timed out - user action required");
-		document.getElementById("challenge-notice").textContent =
-			"Please complete the security check above to continue.";
-
-		// Optionally highlight the widget
-		document.getElementById("my-widget").style.border = "2px solid orange";
-	},
-	"expired-callback": function () {
-		console.log("Token expired - challenge needs refresh");
-		document.getElementById("challenge-notice").textContent =
-			"Security check expired. Please try again.";
-	},
+turnstile.render('#my-widget', {
+  sitekey: 'your-sitekey',
+  callback: function(token) {
+    console.log('Challenge completed successfully');
+  },
+  'timeout-callback': function() {
+    console.log('Challenge timed out - user action required');
+    document.getElementById('challenge-notice').textContent = 
+      'Please complete the security check above to continue.';
+    
+    // Optionally highlight the widget
+    document.getElementById('my-widget').style.border = '2px solid orange';
+  },
+  'expired-callback': function() {
+    console.log('Token expired - challenge needs refresh');
+    document.getElementById('challenge-notice').textContent = 
+      'Security check expired. Please try again.';
+  }
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/turnstile/troubleshooting/index.mdx b/src/content/docs/turnstile/troubleshooting/index.mdx
index 62155e4b61f1542..9732a59701eb192 100644
--- a/src/content/docs/turnstile/troubleshooting/index.mdx
+++ b/src/content/docs/turnstile/troubleshooting/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 8
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Refer to the following pages for more information about troubleshooting Turnstile:
 
diff --git a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
index ce67d78a5431377..50d1cebeb5a11e6 100644
--- a/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
+++ b/src/content/docs/turnstile/troubleshooting/rotate-secret-key.mdx
@@ -6,9 +6,10 @@ products:
   - turnstile
 sidebar:
   order: 2
+
 ---
 
-import { GlossaryTooltip, DashButton, Steps } from "~/components";
+import { GlossaryTooltip, DashButton, Steps } from "~/components"
 
 You can rotate the <GlossaryTooltip term="secret key">secret key</GlossaryTooltip> using the following steps:
 
diff --git a/src/content/docs/turnstile/troubleshooting/testing.mdx b/src/content/docs/turnstile/troubleshooting/testing.mdx
index 41f98655c15fd16..32e507a1005bb68 100644
--- a/src/content/docs/turnstile/troubleshooting/testing.mdx
+++ b/src/content/docs/turnstile/troubleshooting/testing.mdx
@@ -9,9 +9,10 @@ tags:
 sidebar:
   order: 1
   label: Testing
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Use dummy sitekeys and secret keys to test your Turnstile implementation without triggering real challenges that would interfere with automated testing suites.
 
@@ -26,23 +27,23 @@ Dummy keys solve this by providing predictable, controlled responses that work w
 
 ## Test sitekeys
 
-| Sitekey                    | Behavior                     | Widget Type | Use case                             |
-| -------------------------- | ---------------------------- | ----------- | ------------------------------------ |
-| `1x00000000000000000000AA` | Always passes                | Visible     | Test successful form submissions     |
-| `2x00000000000000000000AB` | Always fails                 | Visible     | Test error handling and retry logic  |
-| `1x00000000000000000000BB` | Always passes                | Invisible   | Test invisible widget success flows  |
-| `2x00000000000000000000BB` | Always fails                 | Invisible   | Test invisible widget error handling |
-| `3x00000000000000000000FF` | Forces interactive challenge | Visible     | Test user interaction scenarios      |
+| Sitekey | Behavior | Widget Type | Use case |
+| ------- | -------- | ----------- | -------- |
+| `1x00000000000000000000AA` | Always passes | Visible | Test successful form submissions |
+| `2x00000000000000000000AB` | Always fails | Visible | Test error handling and retry logic |
+| `1x00000000000000000000BB` | Always passes | Invisible | Test invisible widget success flows |
+| `2x00000000000000000000BB` | Always fails | Invisible | Test invisible widget error handling |
+| `3x00000000000000000000FF` | Forces interactive challenge | Visible | Test user interaction scenarios |
 
 ## Test secret keys
 
 Use these secret keys for server-side validation testing:
 
-| Secret key                            | Behavior                            | Use case                         |
-| ------------------------------------- | ----------------------------------- | -------------------------------- |
-| `1x0000000000000000000000000000000AA` | Always passes validation            | Test successful token validation |
-| `2x0000000000000000000000000000000AA` | Always fails validation             | Test validation error handling   |
-| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling    |
+| Secret key | Behavior | Use case |
+| ---------- | -------- | -------- |
+| `1x0000000000000000000000000000000AA` | Always passes validation | Test successful token validation |
+| `2x0000000000000000000000000000000AA` | Always fails validation | Test validation error handling |
+| `3x0000000000000000000000000000000AA` | Returns "token already spent" error | Test duplicate token handling |
 
 ---
 
@@ -77,10 +78,9 @@ Replace your production secret key with a test secret key.
 
 ```js
 // Environment-based configuration
-const SECRET_KEY =
-	process.env.NODE_ENV === "production"
-		? process.env.TURNSTILE_SECRET_KEY
-		: "1x0000000000000000000000000000000AA";
+const SECRET_KEY = process.env.NODE_ENV === 'production' 
+  ? process.env.TURNSTILE_SECRET_KEY 
+  : '1x0000000000000000000000000000000AA';
 
 // Use in validation
 const validation = await validateTurnstile(token, SECRET_KEY);
@@ -96,7 +96,7 @@ Set up different keys for different environments.
 TURNSTILE_SITEKEY=1x00000000000000000000AA
 TURNSTILE_SECRET_KEY=1x0000000000000000000000000000000AA
 
-# .env.test
+# .env.test  
 TURNSTILE_SITEKEY=2x00000000000000000000AB
 TURNSTILE_SECRET_KEY=2x0000000000000000000000000000000AA
 
@@ -126,26 +126,27 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ```json title="Success response"
 {
-	"success": true,
-	"challenge_ts": "2022-02-28T15:14:30.096Z",
-	"hostname": "localhost",
-	"error-codes": [],
-	"action": "test",
-	"cdata": "test-data"
+  "success": true,
+  "challenge_ts": "2022-02-28T15:14:30.096Z",
+  "hostname": "localhost",
+  "error-codes": [],
+  "action": "test",
+  "cdata": "test-data"
 }
 ```
 
 ```json title="Failure response"
 {
-	"success": false,
-	"error-codes": ["invalid-input-response"]
+  "success": false,
+  "error-codes": ["invalid-input-response"]
 }
+
 ```
 
 ```json title="Token already redeemed"
 {
-	"success": false,
-	"error-codes": ["timeout-or-duplicate"]
+  "success": false,
+  "error-codes": ["timeout-or-duplicate"]
 }
 ```
 
@@ -153,8 +154,8 @@ Production secret keys will reject the dummy token. You must also use a dummy se
 
 ## Testing scenarios
 
-| Test sitekey               | Test secret key                       | <div style="width:200px">Test case</div>                             |
-| -------------------------- | ------------------------------------- | -------------------------------------------------------------------- |
-| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation.        |
-| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail.                                   |
-| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
+| Test sitekey | Test secret key | <div style="width:200px">Test case</div> |
+| ------------ | --------------- | --------- |
+| `1x00000000000000000000AA` | `1x0000000000000000000000000000000AA` | This combination will always result in successful validation. |
+| `2x00000000000000000000AB` | `2x0000000000000000000000000000000AA` | This combination will always fail. |
+| `1x00000000000000000000AA` | `3x0000000000000000000000000000000AA` | This combination will always fail with "timeout-or-duplicate" error. |
\ No newline at end of file
diff --git a/src/content/docs/turnstile/turnstile-analytics/index.mdx b/src/content/docs/turnstile/turnstile-analytics/index.mdx
index 1ad2a0c6a7bcde0..b580a70e9a92a88 100644
--- a/src/content/docs/turnstile/turnstile-analytics/index.mdx
+++ b/src/content/docs/turnstile/turnstile-analytics/index.mdx
@@ -9,9 +9,10 @@ sidebar:
   order: 5
 description: Use Turnstile Analytics to view the number of challenges issued,
   the challenge solve rate, and the metrics of issued challenges.
+
 ---
 
-import { Render, DirectoryListing, DashButton } from "~/components";
+import { Render, DirectoryListing, DashButton } from "~/components"
 
 Turnstile Analytics shows widget statistics across traffic dimensions like hostname, country, browser, and IP address. Use these metrics to identify where challenge activity is highest and whether specific sources are failing or bypassing challenges.
 
@@ -37,4 +38,4 @@ The metrics show changes in the solve rate, widget traffic, and top actions for
 
 Refer to the pages below for more information about Turnstile Analytics:
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
index a4a5ca21b6e199c..6a6c10bc60370a8 100644
--- a/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
+++ b/src/content/docs/turnstile/tutorials/excluding-turnstile-from-e2e-tests.mdx
@@ -28,11 +28,10 @@ For more details, refer to the [testing documentation](/turnstile/troubleshootin
 :::caution
 
 Never use test credentials in production. Always ensure:
-
 - Test credentials are only used in test environments.
 - Production credentials are properly protected.
 - Your deployment process prevents test credentials from reaching production.
-  :::
+:::
 
 ## Implementation
 
@@ -41,27 +40,26 @@ The key to implementing test-environment detection is identifying test requests
 ```typescript
 // Detect test environments using IP addresses or headers
 function isTestEnvironment(request) {
-	const testIPs = ["127.0.0.1", "::1"];
-	const isTestIP = testIPs.includes(request.ip);
-	const hasTestHeader =
-		request.headers["x-test-environment"] === "secret-token";
+  const testIPs = ['127.0.0.1', '::1'];
+  const isTestIP = testIPs.includes(request.ip);
+  const hasTestHeader = request.headers['x-test-environment'] === 'secret-token';
 
-	return isTestIP || hasTestHeader;
+  return isTestIP || hasTestHeader;
 }
 
 // Use the appropriate credentials based on the environment
 function getTurnstileCredentials(request) {
-	if (isTestEnvironment(request)) {
-		return {
-			sitekey: "1x00000000000000000000AA",
-			secretKey: "1x0000000000000000000000000000000AA",
-		};
-	}
-
-	return {
-		sitekey: process.env.TURNSTILE_SITE_KEY,
-		secretKey: process.env.TURNSTILE_SECRET_KEY,
-	};
+  if (isTestEnvironment(request)) {
+    return {
+      sitekey: '1x00000000000000000000AA',
+      secretKey: '1x0000000000000000000000000000000AA'
+    };
+  }
+
+  return {
+    sitekey: process.env.TURNSTILE_SITE_KEY,
+    secretKey: process.env.TURNSTILE_SECRET_KEY
+  };
 }
 ```
 
@@ -70,9 +68,9 @@ function getTurnstileCredentials(request) {
 When rendering your page, inject the appropriate sitekey based on the environment:
 
 ```typescript
-app.get("/your-form", (req, res) => {
-	const { sitekey } = getTurnstileCredentials(req);
-	res.render("form", { sitekey });
+app.get('/your-form', (req, res) => {
+  const { sitekey } = getTurnstileCredentials(req);
+  res.render('form', { sitekey });
 });
 ```
 
@@ -114,16 +112,16 @@ For Cypress or similar E2E testing frameworks:
 ```typescript
 // Set test header for all test requests
 beforeEach(() => {
-	cy.intercept("*", (req) => {
-		req.headers["x-test-environment"] = "secret-token";
-	});
+  cy.intercept('*', (req) => {
+    req.headers['x-test-environment'] = 'secret-token';
+  });
 });
 
 // Your test can now interact with the form normally
-it("submits form successfully", () => {
-	cy.visit("/your-form");
-	cy.get("form").submit();
-	// Turnstile will automatically pass verification
+it('submits form successfully', () => {
+  cy.visit('/your-form');
+  cy.get('form').submit();
+  // Turnstile will automatically pass verification
 });
 ```
 
diff --git a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
index 865dade6b1b9bde..cd516941cbdc5e1 100644
--- a/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
+++ b/src/content/docs/turnstile/tutorials/fraud-detection-with-ephemeral-ids.mdx
@@ -27,7 +27,7 @@ Traditional IP-based detection fails because each request appears to come from a
 - You must have basic familiarity with Turnstile integration. Refer to [Get started with Turnstile](/turnstile/get-started/) for more information.
 
 :::caution[Ephemeral IDs are not guaranteed to be unique]
-Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID.
+Not every unique device will produce a unique Ephemeral ID. Privacy-focused devices and browsers (such as iPhones and Safari) limit the signals available for fingerprinting, which means multiple legitimate users may share the same Ephemeral ID. 
 
 Use Ephemeral IDs to detect high-volume abuse patterns, not to uniquely identify individual devices. Always set detection thresholds high enough to avoid false positives.
 :::
@@ -241,4 +241,4 @@ Ephemeral IDs are privacy-preserving. They are scoped to your account, short-liv
 
 - [Ephemeral IDs](/turnstile/additional-configuration/ephemeral-id/)
 - [Server-side validation](/turnstile/get-started/server-side-validation/)
-- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
+- [Integrate Turnstile, WAF, and Bot Management](/turnstile/tutorials/integrating-turnstile-waf-and-bot-management/)
\ No newline at end of file
diff --git a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
index ebc66f19cfe4972..c7a73ce8527faa1 100644
--- a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
+++ b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
@@ -85,13 +85,7 @@ Add the Turnstile widget to your existing login form:
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input
-		type="password"
-		id="password"
-		placeholder="Password"
-		autocomplete="off"
-		required
-	/>
+	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
diff --git a/src/content/docs/use-cases/e-commerce/performance.mdx b/src/content/docs/use-cases/e-commerce/performance.mdx
index 82a7e010f0ab221..7c7d4fc51d1f3db 100644
--- a/src/content/docs/use-cases/e-commerce/performance.mdx
+++ b/src/content/docs/use-cases/e-commerce/performance.mdx
@@ -51,4 +51,4 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 2. [Set up Cloudflare Images](/images/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
 4. [Configure Zaraz](/zaraz/get-started/)
-5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
+5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
diff --git a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
index a073c15a2066185..9a2ebfe22516874 100644
--- a/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
+++ b/src/content/docs/use-cases/solutions/encrypt-all-keep-site-secure.mdx
@@ -11,29 +11,21 @@ sidebar:
 
 import { DashButton, Render, Steps, TabItem, Tabs } from "~/components";
 
-HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages:
+HTTPS on Cloudflare involves two separate connections: visitor to Cloudflare, and Cloudflare to your origin server. Both must be encrypted for end-to-end security. This guide walks through five stages: 
 
 1. Configure your SSL/TLS encryption mode.
 2. Redirect all HTTP requests to HTTPS.
 3. Harden your HTTPS setup with minimum TLS versions and HSTS.
 4. Monitor third-party scripts on your pages.
-5. Verify your configuration.
+5. Verify your configuration. 
 
 The core workflow is available on Free, Pro, and Business plans.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Client-Side Security is the exception: it is configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Client-Side Security is the exception: it is configured at the account level." }} />
 
 ## Configure your SSL/TLS encryption mode
 
 Your SSL/TLS encryption mode controls how Cloudflare connects to your origin server. For end-to-end encryption, use **Full (strict)** — it encrypts both connections and verifies your origin certificate. For a detailed comparison of all available modes, refer to [Encryption modes](/ssl/origin-configuration/ssl-modes/).
-
 ### Check your current mode
 
 <Steps>
@@ -83,7 +75,6 @@ If your origin already has a valid certificate from a publicly trusted certifica
 9. Select **OK**.
 
 </Steps>
-
 :::note
 For details about working with certificates programmatically, refer to [API calls](/ssl/origin-configuration/origin-ca/#api-calls).
 :::
@@ -101,7 +92,6 @@ For details about working with certificates programmatically, refer to [API call
 4. Enable SSL and port `443` at your origin web server.
 
 </Steps>
-
 :::note
 If you do not see your server listed, search the [DigiCert documentation](https://www.digicert.com/search-results) or contact your hosting provider.
 :::
@@ -119,15 +109,13 @@ After installing a valid certificate on your origin server, set the encryption m
 <Render file="change-encryption-mode-api" product="ssl" />
 
 </TabItem> </Tabs>
-
 :::caution
 If your site shows a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) after changing the encryption mode, your origin certificate may not meet the requirements for Full (strict). The certificate must be unexpired, issued by a trusted CA or Cloudflare Origin CA, and contain a Common Name (CN) or Subject Alternative Name (SAN) that matches your hostname. For redirect loop issues, refer to [ERR_TOO_MANY_REDIRECTS](/ssl/troubleshooting/too-many-redirects/).
 :::
 
 ## Redirect all HTTP requests to HTTPS
 
-Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this:
-
+Even with an active edge certificate, visitors can still access resources over unsecured HTTP connections. Two settings work together to fix this: 
 1. Always Use HTTPS redirects HTTP requests to HTTPS
 2. Automatic HTTPS Rewrites fixes mixed content references in your page HTML
 
@@ -166,7 +154,6 @@ If only some parts of your application can support HTTPS traffic, do not turn on
 </Steps>
 
 </TabItem> </Tabs>
-
 ### Turn on Automatic HTTPS Rewrites
 
 Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resource URLs in your page HTML to HTTPS. This is useful for sites where you do not control all asset URLs, such as CMS-hosted content or embedded third-party resources.
@@ -188,7 +175,6 @@ Automatic HTTPS Rewrites prevents mixed content errors by rewriting HTTP resourc
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `automatic_https_rewrites` as the setting name in the URI path, and the `value` parameter set to `"on"`.
 
 </TabItem> </Tabs>
-
 :::note
 Automatic HTTPS Rewrites does not rewrite all HTTP URLs. Some passive content (such as images) may not be rewritten, which can still cause mixed content warnings. For details on how rewrites work and troubleshooting, refer to [Automatic HTTPS Rewrites](/ssl/edge-certificates/additional-options/automatic-https-rewrites/) and [Mixed content errors](/ssl/troubleshooting/mixed-content-errors/).
 :::
@@ -218,7 +204,6 @@ TLS 1.0 and 1.1 have known vulnerabilities and are no longer considered secure.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `min_tls_version` as the setting name in the URI path, and the `value` parameter set to `"1.2"`.
 
 </TabItem> </Tabs>
-
 :::note[Per-hostname minimum TLS version requires Advanced Certificate Manager]
 To set minimum TLS versions for individual hostnames instead of the entire zone, refer to [Per-hostname setup](/ssl/edge-certificates/additional-options/minimum-tls/#per-hostname). This requires an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription.
 :::
@@ -244,7 +229,6 @@ TLS 1.3 provides faster handshakes and improved security over TLS 1.2.
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `tls_1_3` as the setting name in the URI path, and the `value` parameter set to `"on"`. To also turn on 0-RTT (Zero Round Trip Time Resumption), set the value to `"zrt"`.
 
 </TabItem> </Tabs>
-
 ### Turn on HSTS
 
 HTTP Strict Transport Security (HSTS) adds a response header that tells browsers to connect to your site over HTTPS only, even if a link or redirect tries to send them over HTTP. HSTS protects against protocol downgrade attacks.
@@ -288,7 +272,6 @@ Before turning on HSTS, confirm these prerequisites:
 Send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `security_header` as the setting name in the URI path, and specify the `value` object that includes your HSTS settings.
 
 </TabItem> </Tabs>
-
 ### Review your cipher suites
 
 Cloudflare's default cipher suites provide strong encryption for most sites. You do not need to change them unless a security audit or compliance requirement specifies particular cipher configurations.
@@ -316,7 +299,6 @@ HTTPS encrypts data in transit, but third-party scripts loaded by your pages can
 3. Turn on **Continuous script monitoring**.
 
 </Steps>
-
 ### Review detected resources
 
 After turning on monitoring, it may take some time for Cloudflare to generate a list of detected scripts on your domain.
@@ -332,7 +314,6 @@ After turning on monitoring, it may take some time for Cloudflare to generate a
 3. Review the list of detected scripts. Check for unknown or unexpected scripts from domains you do not recognize.
 
 </Steps>
-
 Depending on your Cloudflare plan, you may also be able to review connections made by scripts and check them for malicious activity. For setup details, refer to [Get started with client-side security](/client-side-security/get-started/).
 
 :::note[Content security rules require Client-Side Security Advanced]
diff --git a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
index 0e5abbc0284d7c9..4cfed58dfe9b42a 100644
--- a/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
+++ b/src/content/docs/use-cases/solutions/protect-sensitive-forms-fraud-abuse.mdx
@@ -15,14 +15,7 @@ import { Render, Steps, DashButton } from "~/components";
 
 Contact, registration, and checkout forms are common targets for automated abuse. This guide covers form protection: verifying that visitors are human, limiting repeated submissions, and blocking known attack patterns. The core workflow uses features available on all plans. Pro and Business plan features are included as callouts.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Add Turnstile to your forms
 
@@ -42,18 +35,14 @@ Add the Turnstile script and widget `div` element to each form you want to prote
 
 ```html
 <form id="contact-form" action="/submit" method="POST">
-	<input type="text" name="name" placeholder="Name" required />
-	<input type="email" name="email" placeholder="Email" required />
-	<textarea name="message" placeholder="Message" required></textarea>
-	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
-	<button type="submit">Submit</button>
+  <input type="text" name="name" placeholder="Name" required />
+  <input type="email" name="email" placeholder="Email" required />
+  <textarea name="message" placeholder="Message" required></textarea>
+  <div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
+  <button type="submit">Submit</button>
 </form>
 
-<script
-	src="https://challenges.cloudflare.com/turnstile/v0/api.js"
-	async
-	defer
-></script>
+<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
 ```
 
 The widget renders in the form and generates a token when the visitor passes verification. The token is included in the form submission as the `cf-turnstile-response` field.
@@ -68,26 +57,26 @@ Call the Siteverify API before processing any form submission:
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
 async function validateTurnstile(token, remoteip) {
-	try {
-		const response = await fetch(
-			"https://challenges.cloudflare.com/turnstile/v0/siteverify",
-			{
-				method: "POST",
-				headers: { "Content-Type": "application/json" },
-				body: JSON.stringify({
-					secret: SECRET_KEY,
-					response: token,
-					remoteip: remoteip,
-				}),
-			},
-		);
-
-		const result = await response.json();
-		return result;
-	} catch (error) {
-		console.error("Turnstile validation error:", error);
-		return { success: false, "error-codes": ["internal-error"] };
-	}
+  try {
+    const response = await fetch(
+      "https://challenges.cloudflare.com/turnstile/v0/siteverify",
+      {
+        method: "POST",
+        headers: { "Content-Type": "application/json" },
+        body: JSON.stringify({
+          secret: SECRET_KEY,
+          response: token,
+          remoteip: remoteip,
+        }),
+      },
+    );
+
+    const result = await response.json();
+    return result;
+  } catch (error) {
+    console.error("Turnstile validation error:", error);
+    return { success: false, "error-codes": ["internal-error"] };
+  }
 }
 ```
 
@@ -127,17 +116,7 @@ The **Request rate analysis** tab in Security Analytics displays request rate di
 
 Create a rule that limits how many times a single IP address can submit to your form endpoint within a given period. Adjust the path, threshold, and period for your site.
 
-<Render
-	file="create-rate-limiting-rule"
-	product="waf"
-	params={{
-		ruleName: "Rate limit contact form submissions",
-		expression:
-			'(http.request.uri.path eq "/contact" and http.request.method eq "POST")',
-		expressionHelp: 'Replace "/contact" with your form endpoint path.',
-		threshold: "5",
-	}}
-/>
+<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit contact form submissions", expression: '(http.request.uri.path eq "/contact" and http.request.method eq "POST")', expressionHelp: 'Replace "/contact" with your form endpoint path.', threshold: "5" }} />
 
 :::note
 Rate limiting rule parameters (counting characteristics, periods, number of rules) vary by plan. For the full availability matrix, refer to [Rate limiting rules](/waf/rate-limiting-rules/#availability).
diff --git a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
index e1db4f92ef75e8b..cfa61e65fe47d61 100644
--- a/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
+++ b/src/content/docs/use-cases/solutions/stop-account-takeover-attacks.mdx
@@ -11,18 +11,16 @@ sidebar:
   label: Stop account takeover
 ---
 
-import { Steps, DashButton, GlossaryTooltip, Render } from "~/components";
+import {
+  Steps,
+  DashButton,
+  GlossaryTooltip,
+  Render,
+} from "~/components";
 
 When your site has login pages, you need to decide how to verify that visitors are human, how aggressively to limit failed attempts, and which request patterns to block. This guide covers five stages: enforce HTTPS, turn on bot protection, add [Turnstile](/turnstile/) to your login form, create Application Security [rate limiting rules](/waf/rate-limiting-rules/) and [custom rules](/waf/custom-rules/) for suspicious patterns, and monitor for ongoing attacks using [SSL/TLS](/ssl/) transport security and [Cloudflare bot solutions](/bots/). The core workflow covers features available on Free, Pro, and Business plans. Enterprise features such as leaked credentials custom detection locations and Bot Management custom rules are included as callouts.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Enforce HTTPS to protect credentials in transit
 
@@ -100,17 +98,10 @@ You need both the sitekey and secret key in the following steps.
 #### 2. Add the client-side snippet
 
 Add the Turnstile script and widget container to your login form. Replace `<YOUR-SITE-KEY>` with the sitekey from the previous step.
-
 ```html
 <form id="login-form">
 	<input type="text" id="username" placeholder="Username" required />
-	<input
-		type="password"
-		id="password"
-		placeholder="Password"
-		autocomplete="off"
-		required
-	/>
+	<input type="password" id="password" placeholder="Password" autocomplete="off" required />
 	<div class="cf-turnstile" data-sitekey="<YOUR-SITE-KEY>"></div>
 	<button type="submit">Log in</button>
 </form>
@@ -127,7 +118,6 @@ The widget renders inside the `div` and produces a token when the visitor passes
 #### 3. Validate the token on your server
 
 Before processing the form submission, send the token to the Turnstile siteverify endpoint to confirm the visitor passed the challenge.
-
 ```js title="server.js"
 const SECRET_KEY = "<YOUR-SECRET-KEY>";
 
@@ -166,7 +156,6 @@ For the complete response format, error codes, and examples in other languages,
 #### Test your implementation
 
 Turnstile provides test site keys that return predictable results without contacting the Siteverify API.
-
 - **Always passes**: Use site key `1x00000000000000000000AA` and secret key `1x0000000000000000000000000000000AA` to simulate a successful challenge.
 - **Always blocks**: Use site key `2x00000000000000000000AB` and secret key `2x0000000000000000000000000000000AA` to simulate a failed challenge.
 - **Forces interactive challenge**: Use site key `3x00000000000000000000FF` to test the interactive challenge flow.
@@ -183,18 +172,7 @@ The following example creates a rate limiting rule that issues a Managed Challen
 Managed Challenge and other [challenge types](/cloudflare-challenges/challenge-types/challenge-pages/) require an HTML response to render. They do not work for non-HTML responses such as AJAX/XHR requests, which are common on login endpoints that use single-page applications (SPAs) or API-based authentication. If your login flow uses AJAX, consider using [Turnstile Pre-Clearance](/turnstile/additional-configuration/pre-clearance-support/) instead.
 :::
 
-<Render
-	file="create-rate-limiting-rule"
-	product="waf"
-	params={{
-		ruleName: "Rate limit login endpoint",
-		expression:
-			'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"',
-		expressionHelp:
-			"Replace `example.com` with your domain and `/login` with your login endpoint path.",
-		threshold: "5",
-	}}
-/>
+<Render file="create-rate-limiting-rule" product="waf" params={{ ruleName: "Rate limit login endpoint", expression: 'http.host eq "example.com" and http.request.uri.path eq "/login" and http.request.method eq "POST"', expressionHelp: 'Replace `example.com` with your domain and `/login` with your login endpoint path.', threshold: "5" }} />
 
 :::note
 (Optional) To count only failed login attempts instead of all matching requests, Business plan and above users can add a separate counting expression under **Increment counter when**:
@@ -342,7 +320,7 @@ Enterprise customers with Bot Management get additional tools for login protecti
 - **Custom rules with bot scores**: combine `cf.bot_management.score` with login path matching for precise control. Refer to [Custom rules for bot protection](/bots/additional-configurations/custom-rules/).
 - **Account takeover detections**: monitor suspicious login volume and failure rates using detection IDs in custom rules and rate limiting rules. Refer to [Account takeover detections](/bots/additional-configurations/detection-ids/account-takeover-detections/).
 - **Account Abuse Protection** (Early Access): detect account fraud patterns beyond credential stuffing. Refer to [Account Abuse Protection](/bots/account-abuse-protection/).
-  :::
+:::
 
 ## Monitor for ongoing compromise attempts
 
diff --git a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
index 82e2fbcd9c90854..df0cbabb8f7a2aa 100644
--- a/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
+++ b/src/content/docs/use-cases/solutions/stop-malicious-bots.mdx
@@ -14,14 +14,7 @@ import { Tabs, TabItem, Steps, Render, DashButton } from "~/components";
 
 The right defense against malicious bot traffic depends on the traffic patterns on your site and your plan. This guide covers a layered approach using [Cloudflare Bots](/bots/), [Cloudflare Application Security](/waf/) (also known as Web Application Firewall or WAF), and [Turnstile](/turnstile/), from baseline protection to targeted custom rules. The core workflow uses features on Free, Pro, and Business plans, with callouts for Enterprise options.
 
-<Render
-	file="domain-scope-note"
-	product="use-cases"
-	params={{
-		exception:
-			"Turnstile is the exception: widgets are configured at the account level.",
-	}}
-/>
+<Render file="domain-scope-note" product="use-cases" params={{ exception: "Turnstile is the exception: widgets are configured at the account level." }} />
 
 ## Review your bot traffic
 
diff --git a/src/content/docs/use-cases/web-apps/performance.mdx b/src/content/docs/use-cases/web-apps/performance.mdx
index 8fa2bc53968700d..f3ac9b09881123e 100644
--- a/src/content/docs/use-cases/web-apps/performance.mdx
+++ b/src/content/docs/use-cases/web-apps/performance.mdx
@@ -39,9 +39,10 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn
 
 - **Edge logic** - Run custom performance optimizations at the edge, such as HTML rewriting and dynamic content assembly, without round-trips to your origin
 
+
 ## Get started
 
 1. [Configure Cache Rules](/cache/how-to/cache-rules/)
 2. [Enable Argo Smart Routing](/argo-smart-routing/get-started/)
 3. [Enable Speed optimizations](/speed/optimization/)
-4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
+4. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/)
\ No newline at end of file
diff --git a/src/content/docs/vectorize/best-practices/index.mdx b/src/content/docs/vectorize/best-practices/index.mdx
index b5663efc9edfdd9..de610d3a68aed70 100644
--- a/src/content/docs/vectorize/best-practices/index.mdx
+++ b/src/content/docs/vectorize/best-practices/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/best-practices/list-vectors.mdx b/src/content/docs/vectorize/best-practices/list-vectors.mdx
index 0c5754e5d12cfb3..d623e334eb65385 100644
--- a/src/content/docs/vectorize/best-practices/list-vectors.mdx
+++ b/src/content/docs/vectorize/best-practices/list-vectors.mdx
@@ -43,7 +43,6 @@ To see recently added or removed vectors, you must start a new list-vectors requ
 ### Response structure
 
 Each response includes:
-
 - `count`: Number of vectors returned in this response
 - `totalCount`: Total number of vectors in the index
 - `isTruncated`: Whether there are more vectors available
@@ -71,4 +70,4 @@ wrangler vectorize list-vectors my-index --count=1000
 wrangler vectorize list-vectors my-index --count=1000 --cursor="<cursor-from-response>"
 
 # Repeat until no more results
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/vectorize/demos.mdx b/src/content/docs/vectorize/demos.mdx
index f98a71856f7f16a..d908b0b5883751d 100644
--- a/src/content/docs/vectorize/demos.mdx
+++ b/src/content/docs/vectorize/demos.mdx
@@ -8,7 +8,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, ResourcesBySelector } from "~/components";
+import { GlossaryTooltip, ResourcesBySelector } from "~/components"
 
 Learn how you can use Vectorize within your existing architecture.
 
@@ -16,11 +16,4 @@ Learn how you can use Vectorize within your existing architecture.
 
 Explore the following <GlossaryTooltip term="reference architecture">reference architectures</GlossaryTooltip> that use Vectorize:
 
-<ResourcesBySelector
-	types={[
-		"reference-architecture",
-		"design-guide",
-		"reference-architecture-diagram",
-	]}
-	products={["vectorize"]}
-/>
+<ResourcesBySelector types={["reference-architecture","design-guide","reference-architecture-diagram"]} products={["vectorize"]} />
diff --git a/src/content/docs/vectorize/examples/agents.mdx b/src/content/docs/vectorize/examples/agents.mdx
index e9bd2deab309881..c7eb3790d39040b 100644
--- a/src/content/docs/vectorize/examples/agents.mdx
+++ b/src/content/docs/vectorize/examples/agents.mdx
@@ -9,4 +9,4 @@ description: Build AI-powered Agents on Cloudflare
 products:
   - vectorize
   - agents
----
+---
\ No newline at end of file
diff --git a/src/content/docs/vectorize/examples/index.mdx b/src/content/docs/vectorize/examples/index.mdx
index f5b3b57929be9d3..b7aaf4f768acdcd 100644
--- a/src/content/docs/vectorize/examples/index.mdx
+++ b/src/content/docs/vectorize/examples/index.mdx
@@ -11,7 +11,7 @@ products:
   - vectorize
 ---
 
-import { GlossaryTooltip, DirectoryListing } from "~/components";
+import { GlossaryTooltip, DirectoryListing } from "~/components"
 
 Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Vectorize.
 
diff --git a/src/content/docs/vectorize/get-started/index.mdx b/src/content/docs/vectorize/get-started/index.mdx
index 44c0cdc6b7ec9e3..2ea3f1ce7462b31 100644
--- a/src/content/docs/vectorize/get-started/index.mdx
+++ b/src/content/docs/vectorize/get-started/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/platform/index.mdx b/src/content/docs/vectorize/platform/index.mdx
index 0dde65d6a58df96..1be91e4d2f5aaf8 100644
--- a/src/content/docs/vectorize/platform/index.mdx
+++ b/src/content/docs/vectorize/platform/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/vectorize/reference/index.mdx b/src/content/docs/vectorize/reference/index.mdx
index 8f496dea995d462..f297e13f34d84b6 100644
--- a/src/content/docs/vectorize/reference/index.mdx
+++ b/src/content/docs/vectorize/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - vectorize
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/about.mdx b/src/content/docs/version-management/about.mdx
index 1587b66c14e88d6..6c6e429bda9459d 100644
--- a/src/content/docs/version-management/about.mdx
+++ b/src/content/docs/version-management/about.mdx
@@ -9,7 +9,7 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Version Management works through a combination of **environments** and **versions**.
 
@@ -47,7 +47,7 @@ stateDiagram-v2
 
 ## Environments
 
-<Render file="environment-definition" product="version-management" /> <br />
+<Render file="environment-definition" product="version-management" /> <br/>
 
 After you [enable](/version-management/how-to/enable/) version management, you will have the ability to create default environments:
 
@@ -59,7 +59,7 @@ To send traffic to specific environments, send requests to that environment that
 
 ## Versions
 
-<Render file="version-definition" product="version-management" /> <br />
+<Render file="version-definition" product="version-management" /> <br/>
 
 <Render file="enable-default-creation" product="version-management" />
 
diff --git a/src/content/docs/version-management/how-to/compare-versions.mdx b/src/content/docs/version-management/how-to/compare-versions.mdx
index 1b6ec4ea51148f4..587f8e9dea1faed 100644
--- a/src/content/docs/version-management/how-to/compare-versions.mdx
+++ b/src/content/docs/version-management/how-to/compare-versions.mdx
@@ -19,7 +19,7 @@ To compare versions:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management** > **Comparisons**.
diff --git a/src/content/docs/version-management/how-to/environments.mdx b/src/content/docs/version-management/how-to/environments.mdx
index 9c26342241ce248..7b1de502b4273a7 100644
--- a/src/content/docs/version-management/how-to/environments.mdx
+++ b/src/content/docs/version-management/how-to/environments.mdx
@@ -9,43 +9,44 @@ products:
   - version-management
 ---
 
-import { DashButton, Render } from "~/components";
+import { DashButton, Render } from "~/components"
 
 <Render file="environment-definition" product="version-management" />
 
----
+***
 
 ## Create environment
 
 <Render file="enable-default-creation" product="version-management" />
 
-<Render file="create-environment-situation" product="version-management" />
-<br />
+<Render file="create-environment-situation" product="version-management" /> <br/>
 
 To create a new environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Go to **Environments**.
 4. Select **Create Environment**.
 5. Provide the following information:
 
-- **Environment Name**: A unique, descriptive name for the environment.
-- [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
-- **Initial position**: Controls where this environment should be in your testing process.
+* **Environment Name**: A unique, descriptive name for the environment.
+* [**Traffic filter**](/version-management/reference/traffic-filters/): Limits which requests are sent to this environment.
+* **Initial position**: Controls where this environment should be in your testing process.
 
 6. Select **Create**.
 
 :::note
 
+
 You can only adjust the [**Read-only Environment**](/version-management/reference/read-only-environments/) configuration after an environment has been created.
 
+
 :::
 
----
+***
 
 ## Edit environment
 
@@ -53,7 +54,7 @@ To edit an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -61,7 +62,7 @@ To edit an environment:
 5. Make any required changes.
 6. Select **Save**.
 
----
+***
 
 ## Change environment version
 
@@ -73,7 +74,7 @@ For more details on the flow of versions and environments, refer to [How it work
 
 Promotion moves a version from a lower-ranked environment to the next highest one.
 
-<Render file="promote-version" product="version-management" /> <br />
+<Render file="promote-version" product="version-management" /> <br/>
 
 ### Roll back a version
 
@@ -83,13 +84,13 @@ To roll back a version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
 4. On a specific environment, select **Roll back**.
 
----
+***
 
 ## Delete environment
 
@@ -97,7 +98,7 @@ To delete an environment:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. Select **Environments**.
@@ -106,6 +107,8 @@ To delete an environment:
 
 :::note
 
+
 You cannot delete your **Production** environment.
 
+
 :::
diff --git a/src/content/docs/version-management/how-to/index.mdx b/src/content/docs/version-management/how-to/index.mdx
index 688bebd5f8faf4c..94f85edeb05a853 100644
--- a/src/content/docs/version-management/how-to/index.mdx
+++ b/src/content/docs/version-management/how-to/index.mdx
@@ -3,7 +3,7 @@ title: How to
 pcx_content_type: navigation
 sidebar:
   order: 4
-  group:
+  group: 
     hideIndex: true
 
 description: Guides for managing versions and environments.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/how-to/versions.mdx b/src/content/docs/version-management/how-to/versions.mdx
index df497bbd391bd24..2bacb859b39b82d 100644
--- a/src/content/docs/version-management/how-to/versions.mdx
+++ b/src/content/docs/version-management/how-to/versions.mdx
@@ -25,7 +25,7 @@ To create a new version:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **Clone**. This will copy over all configurations from that version.
@@ -78,7 +78,7 @@ To view metrics:
 
 1. In the Cloudflare dashboard, go to the **Account home** page and select your account and zone.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **Version Management**.
 3. On an existing version, select **View Metrics**.
diff --git a/src/content/docs/version-management/reference/available-configurations.mdx b/src/content/docs/version-management/reference/available-configurations.mdx
index bf748224eda2e08..d9d33c1d24d8f15 100644
--- a/src/content/docs/version-management/reference/available-configurations.mdx
+++ b/src/content/docs/version-management/reference/available-configurations.mdx
@@ -9,22 +9,24 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When you use Version Management, you can edit various configurations, such as [WAF custom rules](/waf/custom-rules/) and [Cache](/cache/).
 
 Generally, you are allowed to edit all zone-level configurations except for the following:
 
-- [DNS](/dns/)
-- [Spectrum](/spectrum/)
-- Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
-- [Zero Trust](/cloudflare-one/) and Access policies
-- [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
+* [DNS](/dns/)
+* [Spectrum](/spectrum/)
+* Traffic ([Load Balancing](/load-balancing/), [Waiting Rooms](/waiting-room/), Health Checks, and more)
+* [Zero Trust](/cloudflare-one/) and Access policies
+* [SSL certificates](/ssl/edge-certificates/) (though you can test these with a separate [staging certificates](/ssl/edge-certificates/staging-environment/) feature)
 
 :::note
 
+
 For the most up-to-date list of these configurations, start [editing configurations within a version](/version-management/how-to/versions/#change-configurations-in-a-version) in the Cloudflare dashboard.
 
+
 :::
 
 ## Limitations
diff --git a/src/content/docs/version-management/reference/index.mdx b/src/content/docs/version-management/reference/index.mdx
index 042d6149a274f5b..38759a3843efde4 100644
--- a/src/content/docs/version-management/reference/index.mdx
+++ b/src/content/docs/version-management/reference/index.mdx
@@ -3,7 +3,7 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 5
-  group:
+  group: 
     hideIndex: true
 
 description: Reference information for AI Crawl Control.
@@ -11,6 +11,6 @@ products:
   - version-management
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/version-management/reference/read-only-environments.mdx b/src/content/docs/version-management/reference/read-only-environments.mdx
index 36c12fc21a35a82..b6e45386b17cec4 100644
--- a/src/content/docs/version-management/reference/read-only-environments.mdx
+++ b/src/content/docs/version-management/reference/read-only-environments.mdx
@@ -9,15 +9,14 @@ products:
   - version-management
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 When an environment is read-only, versions deployed to this environment will permanently become read-only. This configuration protects sensitive environments from accidental changes.
 
 **Version Zero** is an exception to this rule and is always editable.
 
-<Render file="production-read-only-default" product="version-management" />
-<br />
+<Render file="production-read-only-default" product="version-management" /> <br/>
 
-For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** _after_ your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
+For similar reasons, some organizations may make **Staging** a read-only environment. Otherwise, another member of your account could make changes to a version in **Staging** *after* your organization has performed the validation tests prior to promoting to **Production**. Without having a read-only **Staging** environment, this change could be released into **Production** without testing and might cause an issue with live traffic.
 
 To change the read-only status of an environment, [edit the environment](/version-management/how-to/environments/#edit-environment).
diff --git a/src/content/docs/waf/custom-rules/create-dashboard.mdx b/src/content/docs/waf/custom-rules/create-dashboard.mdx
index a48edb1f3026c30..5e974d601239c71 100644
--- a/src/content/docs/waf/custom-rules/create-dashboard.mdx
+++ b/src/content/docs/waf/custom-rules/create-dashboard.mdx
@@ -15,6 +15,7 @@ head:
 
 import { Render, Tabs, TabItem, Steps, DashButton } from "~/components";
 
+
 <Tabs syncKey="dashNewNav"> <TabItem label="New dashboard" icon="rocket">
 
 <Steps>
diff --git a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
index 6775abcaf7788d7..749a72275225954 100644
--- a/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
+++ b/src/content/docs/waf/custom-rules/use-cases/sequence-custom-rules.mdx
@@ -10,4 +10,4 @@ import { Render } from "~/components";
 
 You can build an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
 
-<Render file="sequence-custom-rules" product="api-shield" />
+<Render file="sequence-custom-rules" product="api-shield" />
\ No newline at end of file
diff --git a/src/content/docs/waf/glossary.mdx b/src/content/docs/waf/glossary.mdx
index f7ce048d441c2e7..e777165a6bf1999 100644
--- a/src/content/docs/waf/glossary.mdx
+++ b/src/content/docs/waf/glossary.mdx
@@ -6,9 +6,10 @@ products:
   - waf
 sidebar:
   order: 17
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's WAF documentation.
 
diff --git a/src/content/docs/waf/managed-rules/index.mdx b/src/content/docs/waf/managed-rules/index.mdx
index dcdce6b4f353b4b..d24fec1853393e0 100644
--- a/src/content/docs/waf/managed-rules/index.mdx
+++ b/src/content/docs/waf/managed-rules/index.mdx
@@ -81,3 +81,4 @@ This means a rule with a terminal action (such as Block or Managed Challenge) in
 ### WAF exceptions
 
 WAF exceptions (skip rules) are rules with a `skip` action deployed to the `http_request_firewall_managed` phase entry-point ruleset. They are evaluated in list order within the entry-point ruleset — a skip rule only bypasses `execute` rules listed after it. Place exceptions before the managed ruleset execute rules they are intended to skip. For more information, refer to [WAF exceptions](/waf/managed-rules/waf-exceptions/).
+
diff --git a/src/content/docs/waf/tools/index.mdx b/src/content/docs/waf/tools/index.mdx
index 93bf5ec8fba60f0..2547f0abc231788 100644
--- a/src/content/docs/waf/tools/index.mdx
+++ b/src/content/docs/waf/tools/index.mdx
@@ -12,6 +12,7 @@ sidebar:
 
 import { DirectoryListing } from "~/components";
 
+
 The Cloudflare WAF offers the following additional tools:
 
 <DirectoryListing />
diff --git a/src/content/docs/waf/tools/privacy-pass.mdx b/src/content/docs/waf/tools/privacy-pass.mdx
index 253f4e8bd646159..dce774674951b17 100644
--- a/src/content/docs/waf/tools/privacy-pass.mdx
+++ b/src/content/docs/waf/tools/privacy-pass.mdx
@@ -7,6 +7,7 @@ source: https://support.cloudflare.com/hc/en-us/articles/115001992652-Using-Priv
 title: Privacy Pass
 tags:
   - Privacy
+
 ---
 
 [Privacy Pass](https://datatracker.ietf.org/wg/privacypass/about/) specifies an extensible protocol for creating and redeeming anonymous and transferable tokens. Its specification is maintained by the IETF.
@@ -14,7 +15,7 @@ Cloudflare provides "Silk - Privacy Pass Client". This is a Chrome and Firefox b
 
 For instance, a visitor IP address with poor reputation may receive a Cloudflare challenge page before gaining access to a Cloudflare-protected website. Privacy Pass allows the visitor to solve a challenge with or without interaction, depending on the device. Solving this challenge is coordinated with a third party attester in such a way that Cloudflare does not see the attestation method or the interaction, preserving visitors' privacy while maintaining a high level of security.
 
----
+***
 
 ## Set up Privacy Pass
 
@@ -22,12 +23,12 @@ For instance, a visitor IP address with poor reputation may receive a Cloudflare
 
 Your end users should download the Privacy Pass extension for either Google Chrome or Firefox:
 
-- [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
-- [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
+* [Chrome extension](https://chrome.google.com/webstore/detail/privacy-pass/ajhmfdgkijocedmfjonnpjfojldioehi)
+* [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/)
 
 The Privacy Pass code is [available on GitHub](https://github.com/cloudflare/pp-browser-extension). You can report any issues in this repository.
 
----
+***
 
 ## Support for Privacy Pass v1 (legacy)
 
diff --git a/src/content/docs/waf/troubleshooting/faq.mdx b/src/content/docs/waf/troubleshooting/faq.mdx
index a3a09ba5996df45..d7e6a3b09ec4447 100644
--- a/src/content/docs/waf/troubleshooting/faq.mdx
+++ b/src/content/docs/waf/troubleshooting/faq.mdx
@@ -34,7 +34,6 @@ If you are using a regular expression, it is recommended that you test it with a
 If you have [SSL/TLS certificates](/ssl/) managed by Cloudflare, every time a certificate is issued or renewed, a [domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/dcv-flow/) must happen. When a certificate is in `pending_validation` state and there are valid DCV tokens in place, some Cloudflare security features such as [custom rules](/waf/custom-rules/) and [Managed Rules](/waf/managed-rules/) will be automatically disabled on specific DCV paths (for example, `/.well-known/pki-validation/` and `/.well-known/acme-challenge/`).
 
 These automatic bypasses do not appear in [Trace](/rules/trace-request/) results.
-
 ### Why have I been blocked?
 
 Cloudflare may block requests when it detects activity that could be unsafe. Common reasons include:
diff --git a/src/content/docs/waiting-room/about.mdx b/src/content/docs/waiting-room/about.mdx
index 85b25d1bb61107e..ae5c646b790822d 100644
--- a/src/content/docs/waiting-room/about.mdx
+++ b/src/content/docs/waiting-room/about.mdx
@@ -6,9 +6,10 @@ products:
   - waiting-room
 sidebar:
   order: 2
+
 ---
 
-import { LinkButton, Render } from "~/components";
+import { LinkButton, Render } from "~/components"
 
 Waiting Room queues visitors when your traffic approaches a previously defined threshold that might otherwise bring an application down.
 
@@ -20,6 +21,7 @@ Once you have [created and activated a waiting room](/waiting-room/get-started/)
 
 - If a page is not experiencing heavy traffic, a visitor accesses the page directly.
 - If page traffic approaches a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
+
   - Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
   - While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
   - When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
@@ -45,4 +47,4 @@ The other factor is the Waiting Room state, which is maintained at the local dat
 
 The Waiting Room state is updated with global information every few seconds. We have a pipeline set up in Cloudflare [Durable Objects](/durable-objects/) that ensures changes in traffic get propagated around the world. This architecture ensures that we do not introduce additional latency, as well as that we are making decisions with as near-time accuracy as possible.
 
-For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
+For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).
\ No newline at end of file
diff --git a/src/content/docs/waiting-room/additional-options/create-events.mdx b/src/content/docs/waiting-room/additional-options/create-events.mdx
index 6fba618cbc22dd8..123834ddd12dbc3 100644
--- a/src/content/docs/waiting-room/additional-options/create-events.mdx
+++ b/src/content/docs/waiting-room/additional-options/create-events.mdx
@@ -6,6 +6,7 @@ products:
 title: Create scheduled events
 sidebar:
   order: 4
+
 ---
 
 When you want to customize the behavior of a waiting room for a specific period of time — such as changing the queueing method or increasing the total active users — set up a **scheduled event**. You can do this from the dashboard or via the API.
@@ -20,7 +21,7 @@ Only some customers can support scheduled events with their waiting rooms. For m
 
 1. Within your application, go to **Traffic** > **Waiting Room**.
 
-2. Expand a waiting room and select **Schedule event**.
+2. Expand a waiting room  and select **Schedule event**.
 
 3. Customize the details for your event: name the event, add a description (optional), and select a Start Date Time and an End Date Time.
 
@@ -64,21 +65,23 @@ If you are using a [custom template](/waiting-room/how-to/customize-waiting-room
 
 :::note
 
+
 If you need to create overlapping events, use different waiting rooms.
 
+
 :::
 
 ### Parameters
 
 Though most parameters are identical to those in a regular waiting room, there are a few unique to creating an event. For a complete list of event settings, please refer to [Create an Event](/api/resources/waiting_rooms/subresources/events/methods/create/).
 
-- `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
-- `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
-- `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
-- `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
-- `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
-- `description`: A text description providing more detail about the event.
-- `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
+* `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
+* `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
+* `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
+* `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
+* `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
+* `description`: A text description providing more detail about the event.
+* `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's typical configuration.
 
 ### Queueing methods
 
@@ -96,8 +99,8 @@ Users who reach your application **during the prequeue period** are [randomly as
 
 To set up a "lottery", include the [following parameters](#parameters) in your API request:
 
-- `prequeue_start_time`
-- `shuffle_at_event_start`
+* `prequeue_start_time`
+* `shuffle_at_event_start`
 
 ## Preview an event configuration
 
@@ -122,12 +125,12 @@ Follow these steps if you would like to deploy a scheduled maintenance page, wit
 1. [Create a waiting room](/waiting-room/how-to/create-waiting-room/) with [Passthrough](/waiting-room/reference/queueing-methods/#passthrough) queueing method enabled.
 2. Create a waiting room event for this room with [Reject](/waiting-room/reference/queueing-methods/#reject) queueing method enabled.
 
-After the scheduled event has ended, users will have access to your site. You can end the maintenance window before the scheduled event is over by setting the event to disabled.
+After the scheduled event has ended, users will have access to your site.  You can end the maintenance window before the scheduled event is over by setting the event to disabled.
 
 ## Other API commands
 
-| Function                                                                                | Command  |
-| --------------------------------------------------------------------------------------- | -------- |
-| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)      | `GET`    |
+| Function                                                          | Command  |
+| ----------------------------------------------------------------- | -------- |
+| [Get event details](/api/resources/waiting_rooms/subresources/events/methods/get/)   | `GET`    |
 | [List scheduled events](/api/resources/waiting_rooms/subresources/events/methods/list/) | `GET`    |
-| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)        | `DELETE` |
+| [Delete event](/api/resources/waiting_rooms/subresources/events/methods/delete/)         | `DELETE` |
diff --git a/src/content/docs/waiting-room/additional-options/index.mdx b/src/content/docs/waiting-room/additional-options/index.mdx
index bd77dc9b14cc6ad..92470e9cc3b208c 100644
--- a/src/content/docs/waiting-room/additional-options/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Beyond [creating a waiting room](/waiting-room/get-started/), you may want to further customize how your waiting room functions.
 
diff --git a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
index 8eac756e51d27f1..bd9c6161eebc229 100644
--- a/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
+++ b/src/content/docs/waiting-room/additional-options/ssl-for-saas.mdx
@@ -6,6 +6,7 @@ products:
 title: Combine with Cloudflare for SaaS
 sidebar:
   order: 7
+
 ---
 
 If your application is using a custom hostname — meaning your SaaS provider is using [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) — your application can support a waiting room.
diff --git a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
index c39b032cfdb8839..0f15a5bf0d091f7 100644
--- a/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
+++ b/src/content/docs/waiting-room/additional-options/waiting-room-rules/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Waiting Room Rules
 sidebar:
   order: 10
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In this section, we will list the Waiting Room rules available.
 
diff --git a/src/content/docs/waiting-room/api-reference.mdx b/src/content/docs/waiting-room/api-reference.mdx
index 893bc601dbd2942..b91d98532f5c31c 100644
--- a/src/content/docs/waiting-room/api-reference.mdx
+++ b/src/content/docs/waiting-room/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/waiting_rooms/methods/list/
 sidebar:
   order: 10
+
 ---
diff --git a/src/content/docs/waiting-room/glossary.mdx b/src/content/docs/waiting-room/glossary.mdx
index aa5be06af954401..5e0ec50ac37db3d 100644
--- a/src/content/docs/waiting-room/glossary.mdx
+++ b/src/content/docs/waiting-room/glossary.mdx
@@ -4,9 +4,10 @@ pcx_content_type: glossary
 description: Definitions for terms used across Waiting Room documentation.
 products:
   - waiting-room
+
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Waiting Room documentation.
 
diff --git a/src/content/docs/waiting-room/how-to/control-user-session.mdx b/src/content/docs/waiting-room/how-to/control-user-session.mdx
index 9f585b420804aa8..a8981dcd2100717 100644
--- a/src/content/docs/waiting-room/how-to/control-user-session.mdx
+++ b/src/content/docs/waiting-room/how-to/control-user-session.mdx
@@ -8,13 +8,13 @@ sidebar:
   order: 4
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Adjust these settings to control how long a user can hold their place on your site after leaving the waiting room.
 
 ## Session duration
 
-Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes. Each new request restarts a user’s time to stay active equal to **session duration**.
+Once on your site, a user is considered active as long as they make an HTTP request to any URL covered by your waiting room once every **session duration** minutes.  Each new request restarts a user’s time to stay active equal to **session duration**. 
 
 ## Disable session renewal to limit browsing time
 
@@ -24,9 +24,9 @@ You can limit each user’s time on your site to only one session duration by ch
 
 To terminate a user's session when they perform a specific action, you can send a command to the waiting room using an HTTP header on the response from your origin. This command tells the waiting room to revoke the session of the user associated with the current response. This allows spots to open up more dynamically and may increase throughput from your queue.
 
-To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard.
+To enable this feature in the Cloudflare Dashboard, check the box next to Allow session termination via origin commands from the dashboard. 
 To enable this feature through the [Cloudflare API](/api/resources/waiting_rooms/methods/update/), update the `enabled_origin_commands` property to include the value `”revoke”` in the list of enabled origin commands.
-
+ 
 Then, to return a revocation origin command and revoke the user's session associated with the current request, add the `Cf-Waiting-Room-Command: revoke` HTTP header to the response from your origin.
 
 To get the number of sessions revoked, you can query `sessionsRevoked` metrics from your [Waiting Room analytics](/waiting-room/waiting-room-analytics/#graphql-analytics) data via GraphQL API.
diff --git a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
index f826cb8f5c312f5..ea279a612cbaf63 100644
--- a/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/edit-delete-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
 title: Edit and delete waiting rooms
 sidebar:
   order: 5
+
 ---
 
 import { APIRequest } from "~/components";
@@ -40,36 +41,36 @@ For details about updating an active waiting room, refer to [Best practices](/wa
 [Replace](https://api.cloudflare.com#waiting-room-update-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="PUT"
-	json={{
-		name: "webshop-waiting-room",
-		host: "example.com",
-		new_users_per_minute: 200,
-		total_active_users: 300,
-	}}
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="PUT"
+  json={{
+    name: "webshop-waiting-room",
+    host: "example.com",
+    new_users_per_minute: 200,
+    total_active_users: 300
+  }}
 />
 
 [Update](https://api.cloudflare.com#waiting-room-patch-waiting-room) a configured waiting room by appending the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="PATCH"
-	json={{
-		name: "webshop-waiting-room",
-		host: "example.com",
-		new_users_per_minute: 200,
-		total_active_users: 300,
-	}}
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="PATCH"
+  json={{
+    name: "webshop-waiting-room",
+    host: "example.com",
+    new_users_per_minute: 200,
+    total_active_users: 300
+  }}
 />
 
-You only need to include the fields you want to update in the payload of the PATCH request.
 
+You only need to include the fields you want to update in the payload of the PATCH request.
 ### Delete a waiting room
 
 Delete a waiting room by appending the following endpoint in the [Waiting Room API](https://api.cloudflare.com#waiting-room-delete-waiting-room) to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="DELETE"
-/>
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="DELETE"
+/>
\ No newline at end of file
diff --git a/src/content/docs/waiting-room/how-to/index.mdx b/src/content/docs/waiting-room/how-to/index.mdx
index 38bb6f03248845f..be1f971a0c6909b 100644
--- a/src/content/docs/waiting-room/how-to/index.mdx
+++ b/src/content/docs/waiting-room/how-to/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Common tasks
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 When working with Cloudflare Waiting Room, you will commonly perform the following tasks:
 
diff --git a/src/content/docs/waiting-room/how-to/json-response.mdx b/src/content/docs/waiting-room/how-to/json-response.mdx
index 71bc059dc58e13a..4851e4a1a5bc96a 100644
--- a/src/content/docs/waiting-room/how-to/json-response.mdx
+++ b/src/content/docs/waiting-room/how-to/json-response.mdx
@@ -65,11 +65,13 @@ In a browser environment, the page automatically refreshes every `refreshInterva
 These are some of the places where the JSON-friendly response can be consumed (this list is not exhaustive):
 
 1. In a mobile app traffic
+
    - **Integrate Waiting Room variables** – Create a new template in your mobile app to receive the JSON response. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Allow cookies** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your mobile app will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Consume JSON data** - Make a request to the Waiting Room endpoint with the `Accept: application/json` header.
 
 2. Inside Cloudflare Workers (or in your own backend service)
+
    - **Integrate Waiting Room variables** – Expect a JSON response in your backend API. For a full list of these variables, refer to the `json_response_enabled` parameter in the [Cloudflare API docs](/api/resources/waiting_rooms/methods/create/).
    - **Include cookies in the request header** – As mentioned above, a waiting room [requires cookies](/waiting-room/reference/waiting-room-cookie/), and your backend API will need to support cookies. For ease of use, consider using a cookie manager like [CookieJar](https://pkg.go.dev/net/http#CookieJar).
    - **Enable JSON response** - Via the dashboard or via the API.
diff --git a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
index 00fa24999781e3f..f17f0406cc79484 100644
--- a/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/monitor-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
 title: Monitor waiting room status
 sidebar:
   order: 3
+
 ---
 
 import { APIRequest } from "~/components";
@@ -22,37 +23,37 @@ Open the **Waiting Room** dashboard to view the list of your waiting rooms.
 
 The **Status** column displays the current state of the waiting room:
 
-- **Not queueing**:
-  - Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
-  - Shows estimated number of users in the application.
-- **Queueing**:
-  - Waiting room enabled and sending visitors to waiting room.
-  - Shows estimated number of users in the queue.
-  - On hover, shows maximum wait time expected for users.
-- **Disabled**: The waiting room is suspended.
-- **Queue-all**:
-  - Forces all traffic to queue in the waiting room.
-  - On hover, shows estimated number of users in the queue.
+* **Not queueing**:
+  * Waiting room enabled, but has not reached traffic threshold to send visitors to waiting room.
+  * Shows estimated number of users in the application.
+* **Queueing**:
+  * Waiting room enabled and sending visitors to waiting room.
+  * Shows estimated number of users in the queue.
+  * On hover, shows maximum wait time expected for users.
+* **Disabled**: The waiting room is suspended.
+* **Queue-all**:
+  * Forces all traffic to queue in the waiting room.
+  * On hover, shows estimated number of users in the queue.
 
 ## Status in the API
 
 [Check whether traffic is queueing in a configured waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) by appending the following endpoint to the Cloudflare API base URL:
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
-	method="GET"
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}/status"
+  method="GET"
 />
 
 The response is:
 
-- `queueing` if visitors are currently queueing in the waiting room.
-- `not_queueing` if the room is empty or if the waiting room is suspended.
+* `queueing` if visitors are currently queueing in the waiting room.
+* `not_queueing` if the room is empty or if the waiting room is suspended.
 
 To check whether a configured waiting room is suspended or whether the traffic is force-queued to the waiting room, append the following endpoint to the Cloudflare API base URL.
 
 <APIRequest
-	path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
-	method="GET"
+  path="/zones/{zone_id}/waiting_rooms/{waiting_room_id}"
+  method="GET"
 />
 
 The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/get/) for a configured waiting room:
@@ -87,13 +88,13 @@ The endpoint above [fetches all settings](/api/resources/waiting_rooms/methods/g
 
 The value of `suspended` indicates whether a waiting room is activated or suspended:
 
-- `false`: The waiting room is activated.
-- `true`: The waiting room is suspended.
+* `false`: The waiting room is activated.
+* `true`: The waiting room is suspended.
 
 The value of `queue_all` indicates whether all traffic is forced to queue in the waiting room:
 
-- `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
-- `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
+* `false`: Visitors are diverted to the waiting room only if traffic exceeds the configured threshold.
+* `true`: All traffic is forced to queue in the waiting room, and no traffic passes from the waiting room to the origin.
 
 ## Queueing activation
 
@@ -107,5 +108,5 @@ To help prevent a waiting room from active queueing, increase the values for `ne
 
 :::note
 
-Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products.
+Note that Waiting Room is designed to handle legitimate traffic. If you notice frequent or abnormal queueing behavior, ensure that you are properly handling malicious and automated traffic using Cloudflare security products. 
 :::
diff --git a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
index 3f4ca5fb6eafa52..d8e1e831c020a7e 100644
--- a/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
+++ b/src/content/docs/waiting-room/how-to/place-waiting-room.mdx
@@ -6,6 +6,7 @@ products:
   - waiting-room
 sidebar:
   order: 2
+
 ---
 
 When [configuring a waiting room](/waiting-room/how-to/create-waiting-room/), you need to indicate which pages the waiting room will cover.
@@ -20,8 +21,8 @@ You cannot add any hostname and path combinations already configured for another
 
 A single waiting room can be applied to multiple custom hostnames as long as the following is true:
 
-- The apex domain is the same between the custom hostnames
-- Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
+* The apex domain is the same between the custom hostnames
+* Each custom hostname is [configured explicitly](#custom-hostnames) in SSL for SaaS setup.
 
 ## Custom hostnames
 
diff --git a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
index 5039172c35fa4e8..3876ca31bccde46 100644
--- a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
+++ b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
@@ -6,6 +6,7 @@ products:
 title: Access Waiting Room
 sidebar:
   order: 1
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,6 @@ Use Cloudflare Waiting Room to create a holding area where users can queue to ac
 
 To access Waiting Room on the Cloudflare dashboard, go to the **Waiting Room** page.
 
-<DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
+   <DashButton url="/?to=/:account/:zone/traffic/waiting-rooms" />
 
 Use the dashboard to [create, edit, update, and delete](/waiting-room/how-to/) waiting rooms.
diff --git a/src/content/docs/waiting-room/plans.mdx b/src/content/docs/waiting-room/plans.mdx
index a4041473cdfc940..29189c6fe19e6d5 100644
--- a/src/content/docs/waiting-room/plans.mdx
+++ b/src/content/docs/waiting-room/plans.mdx
@@ -10,9 +10,10 @@ sidebar:
 head:
   - tag: title
     content: Features by plan type
+
 ---
 
-import { FeatureTable, Render } from "~/components";
+import { FeatureTable, Render } from "~/components"
 
 The features available for a waiting room depend on your plan type. You can only have **one plan** per zone.
 
diff --git a/src/content/docs/waiting-room/reference/configuration-settings.mdx b/src/content/docs/waiting-room/reference/configuration-settings.mdx
index 0d6c313160fc12b..20481e7adaee0c6 100644
--- a/src/content/docs/waiting-room/reference/configuration-settings.mdx
+++ b/src/content/docs/waiting-room/reference/configuration-settings.mdx
@@ -7,18 +7,15 @@ products:
 title: Configuration settings
 sidebar:
   order: 2
+
 ---
 
-import { Description, LinkButton } from "~/components";
+import { Description, LinkButton } from "~/components"
 
 You can customize a variety of options for your waiting rooms.
 
-<LinkButton variant="primary" href="#dashboard-settings">
-	Dashboard settings
-</LinkButton>
-<LinkButton variant="secondary" href="#additional-details">
-	Additional details
-</LinkButton>
+ <LinkButton variant="primary" href="#dashboard-settings">Dashboard settings</LinkButton> <LinkButton variant="secondary" href="#additional-details">Additional details</LinkButton>
+
 
 ## Dashboard settings
 
diff --git a/src/content/docs/waiting-room/reference/index.mdx b/src/content/docs/waiting-room/reference/index.mdx
index 386e738762a9e82..4567f07d6834f80 100644
--- a/src/content/docs/waiting-room/reference/index.mdx
+++ b/src/content/docs/waiting-room/reference/index.mdx
@@ -8,9 +8,10 @@ sidebar:
   order: 7
   group:
     hideIndex: true
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Use the following reference information when setting up and deploying your waiting rooms:
 
diff --git a/src/content/docs/waiting-room/reference/waiting-room-api.mdx b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
index 9d57a00c62e2a34..cd9d3e20bb3a293 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-api.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-api.mdx
@@ -4,6 +4,7 @@ description: API commands for managing waiting rooms.
 products:
   - waiting-room
 title: API commands
+
 ---
 
 Cloudflare Waiting Room redirect visitors to virtual waiting rooms when they are trying to access web pages that have high volumes of traffic.
@@ -24,17 +25,17 @@ For help with endpoints and pagination, refer to [Getting Started: Endpoints](/f
 
 ## Manage your waiting room
 
-| Operation                                                           | Method + URL stub                                             | Notes                              |
-| ------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
-| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)    | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
-| [Create waiting room](/api/resources/waiting_rooms/methods/create/) | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
-| [Waiting room details](/api/resources/waiting_rooms/methods/get/)   | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
-| [Update waiting room](/api/resources/waiting_rooms/methods/update/) | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
-| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/) | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
-| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)    | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
+| Operation                                                                 | Method + URL stub                                             | Notes                              |
+| ------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------- |
+| [List waiting rooms](/api/resources/waiting_rooms/methods/list/)     | `GET zones/{:zone_identifier}/waiting_rooms`                  | List all waiting rooms for a zone. |
+| [Create waiting room](/api/resources/waiting_rooms/methods/create/)   | `POST zones/{:zone_identifier}/waiting_rooms`                 | Create a waiting room.             |
+| [Waiting room details](/api/resources/waiting_rooms/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Fetch a waiting room.              |
+| [Update waiting room](/api/resources/waiting_rooms/methods/update/)   | `PUT zones/{:zone_identifier}/waiting_rooms/{:identifier}`    | Update a waiting room.             |
+| [Delete waiting room](/api/resources/waiting_rooms/methods/delete/)   | `DELETE zones/{:zone_identifier}/waiting_rooms/{:identifier}` | Delete a waiting room.             |
+| [Patch waiting room](/api/resources/waiting_rooms/methods/edit/)     | `PATCH zones/{:zone_identifier}/waiting_rooms/{:identifier}`  | Patch a configured waiting room.   |
 
 ## Fetch the current status of a waiting room
 
-| Operation                                                                                                   | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
-| ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Operation                                                                                        | Method + URL stub                                                 | Notes                                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [Get the current status of a waiting room](/api/resources/waiting_rooms/subresources/statuses/methods/get/) | `GET zones/{:zone_identifier}/waiting_rooms/{:identifier}/status` | <ul><li>Returns <code>queueing</code> if the queue is activated (clients are put in the waiting room).</li><li>Returns <code>not\_queueing</code> if the queue is not activated or if the waiting room is suspended.</li></ul> |
diff --git a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
index 999050767f022fd..fc575945d64c011 100644
--- a/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
+++ b/src/content/docs/waiting-room/reference/waiting-room-cookie.mdx
@@ -12,22 +12,24 @@ A waiting room only uses the `__cfwaitingroom` cookie when a visitor requests ac
 
 :::caution[Important:]
 
+
 Cloudflare Waiting Room requires the `__cfwaitingroom` cookie. When a waiting room is actively queueing, users cannot visit that host and path combination without enabling cookies.
 
+
 :::
 
 ## Cookie function
 
 The `__cfwaitingroom` cookie is used to:
 
-- Track a user's position in the waiting room queue and serve them in the correct order.
-- Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
-- To allow re-entry for a period of time (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
+* Track a user's position in the waiting room queue and serve them in the correct order.
+* Monitor each visitor's duration in the application to provide an [accurate entry time](#estimated-wait-time-fifo-queueing-method) to visitors queueing in the waiting room.
+* To allow re-entry for a period of time (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)) without going back in the waiting room.
 
 ## Cookie expiration time
 
-- While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
-- When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session_duration](/waiting-room/reference/configuration-settings/#session-duration)).
+* While a visitor stays in a waiting room, `__cfwaitingroom` cookie expiration is always set to five minutes, but renews every 20 seconds automatically as long as the visitor does not close the tab or leaves your application.
+* When the visitor accesses the application, the `__cfwaitingroom` cookie expires after an interval (specified by [session\_duration](/waiting-room/reference/configuration-settings/#session-duration)).
 
 ## Customize cookie name
 
diff --git a/src/content/docs/waiting-room/troubleshooting.mdx b/src/content/docs/waiting-room/troubleshooting.mdx
index 0ff28fdedd01e62..79df5d5298f08bd 100644
--- a/src/content/docs/waiting-room/troubleshooting.mdx
+++ b/src/content/docs/waiting-room/troubleshooting.mdx
@@ -7,16 +7,17 @@ title: FAQ
 structured_data: true
 sidebar:
   order: 11
+
 ---
 
 Below you will find answers to our most commonly asked questions about the Waiting Room.
 
-- [Configuration](#configuration)
-- [Features and products](#features-and-products)
-- [User behavior](#user-behavior)
-- [Monitor your waiting room](#monitor-your-waiting-room)
+* [Configuration](#configuration)
+* [Features and products](#features-and-products)
+* [User behavior](#user-behavior)
+* [Monitor your waiting room](#monitor-your-waiting-room)
 
----
+***
 
 ## Configuration
 
@@ -24,6 +25,7 @@ Below you will find answers to our most commonly asked questions about the Waiti
 
 Yes. For more details, refer to [Customize a waiting room](/waiting-room/how-to/customize-waiting-room/).
 
+
 ### Why does my waiting room look different than how I designed it?
 
 If you have [customized your waiting room template](/waiting-room/how-to/customize-waiting-room):
@@ -33,8 +35,10 @@ If you have [customized your waiting room template](/waiting-room/how-to/customi
 
 :::note[Note]
 
+
 Only Enterprise customers can customize the appearance of their waiting room.
 
+
 :::
 
 ### What can I update when my waiting room is actively queueing?
@@ -43,51 +47,69 @@ You can update a [waiting room's template](/waiting-room/how-to/customize-waitin
 
 You can also update the [configuration settings](/waiting-room/reference/configuration-settings) of a waiting room, but only make these changes when necessary. These changes may impact the estimated wait time shown to end users and cause unnecessary confusion.
 
+
+
+
 ## Features and products
 
 ### Which features are included in my Waiting Room plan?
 
 To check which features are available to different plan types, refer to [Plans](/waiting-room/plans/).
 
+
+
 ### How does Waiting Room interact with other Cloudflare products?
 
 Some Cloudflare products run before a waiting room acts on traffic:
 
-- DDoS Mitigation
-- Web Application Firewall (WAF)
-- Bot Management
-- Page Rules
+* DDoS Mitigation
+* Web Application Firewall (WAF)
+* Bot Management
+* Page Rules
 
 Other Cloudflare products run after a waiting room acts on traffic:
 
-- Workers
+* Workers
+
+
+
 
 ## User behavior
 
+
 ### What happens if a user refreshes their tab when in a waiting room?
 
 A manual tab refresh has no effect on a user's position in your waiting room.
 
 However, if they close their tab and then try to access the application again during active queueing, they will lose their spot and have to go to the back of the queue.
 
+
 ### What happens if a queued user leaves the queue?
 
 When a user joins the queue, they are placed into a bucket which is their general position in line. When a user leaves the queue (closes the browser or tab), their place in line is held for five minutes after the last refresh. This grace period allows users to keep their position in line if they experience a brief disconnection. After five minutes, the grace period expires and they are no longer counted as waiting in the queue.
 
+
+
 ## Monitor your waiting room
 
+
 ### Why do I observe a few users being queued in the dashboard?
 
+
 Some users might be queued before your waiting room reaches is limit due to architectural designs. For more details on the behavior and how to fix it, refer to [​​Queueing activation](/waiting-room/how-to/monitor-waiting-room#queueing-activation).
 
+
+
 ### Why are some users not being queued in my waiting room?
 
+
 If you notice users not being queued to your waiting room, make sure the path you defined exactly matches the path of your website.
 
 The path is case-sensitive, so if you have a waiting room set up for `/Black-Friday-Sale` and users go to `/black-friday-sale`, they will bypass your waiting room.
 
 For more details, refer to [Best practices](/waiting-room/reference/best-practices).
 
+
 ### Why are users being blocked from entering my waiting room?
 
 If you have Rate Limiting, check your [rate limiting rules](/waf/rate-limiting-rules/).
@@ -96,15 +118,17 @@ The Waiting Room queue page refreshes every 20 seconds by populating the refresh
 
 Your user also might not have [cookies](/waiting-room/reference/waiting-room-cookie) enabled. If they do not enable cookies and your waiting room is actively queueing traffic, they will not reach your endpoint until the queueing stops.
 
+
 ### Why is the estimated wait time increasing for some users?
 
 Estimated wait times may increase if the rate of users leaving your site decreases. The estimated wait time is updated upon each page refresh based on the most recently available information about the rate of slots opening up on your site and the number of users ahead of the user in line. To make this increase less likely, you could limit the amount of time users are allowed to spend on your site by disabling session renewal. Be aware that, if you change your traffic settings, estimated wait times will change as well.
 
+
 ### Why is `new users per minute` low when there is capacity available?
 
 The `new users per minute` metric tracks how many users were accepted to the origin in the last minute. It is only incremented when a queued user refreshes and is accepted to the origin. If the waiting room queueing method is set to `fifo`, we will wait until all queued users in a minute-based bucket are accepted before moving to the next bucket. If many of the users in a bucket have abandoned the queue, then the waiting room must wait until their place in line expires before moving on to the next bucket. This can cause `new users per minute` to be low when only a small percentage of queued users are actually still waiting.
 
-This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting them in an infinite queue.
+This is often noticed if there is a large amount of automated traffic which does not handle cookies properly. Since bots usually do not persist cookies from one request to the next, they end up counting as multiple inactive users in the queue and prevent full utilization of available slots. For this reason, we recommend leveraging [Bots Management](/bots/) products to keep bots out of the queue. Waiting Room Advanced customers can try our [Turnstile](/turnstile/) integration, which prevents bots from clogging the line by putting  them in an infinite queue.
 
 ### Why are my Waiting Room analytics and Google analytics not matching?
 
@@ -118,8 +142,8 @@ Another key difference is that Waiting Room runs on requests made to the origin,
 
 ### Why did my traffic exceed the New Users Per Minute threshold?
 
-Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally.
+Waiting Room is a distributed system, and achieving perfect global counting in real time is challenging due to the time required for state propagation across data centers worldwide. The budgeting logic is structured around both data center-specific and global budgets. Data center budgets are allocated based on the historical traffic received by each data center, while global budgets (a portion of the total available budget) are maintained to allow new users to enter from any data center globally. 
 
 In the case of a rapid spike — rising to several thousand users within a minute — the global state propagation process takes approximately two minutes, resulting in a delay before all data centers become aware of the spike. If this information is not disseminated quickly enough to other locations, temporary overshooting may occur, particularly when lower limits are in place.
 
-This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
+This occurs because the portion of the budget reserved for new users to enter a data center is equally available to all data centers. Until the usage of this budget is synchronized across all data centers, each data center may consume a portion that collectively exceeds 100% of the global budget allocated for new users.
\ No newline at end of file
diff --git a/src/content/docs/warp-client/get-started/linux.mdx b/src/content/docs/warp-client/get-started/linux.mdx
index 5d816a7dfe1846d..8aaf86985cb9983 100644
--- a/src/content/docs/warp-client/get-started/linux.mdx
+++ b/src/content/docs/warp-client/get-started/linux.mdx
@@ -78,20 +78,19 @@ To enable [WARP+ Unlimited](/warp-client/warp-modes/#warp-unlimited) on Linux, y
 2. Go to **Settings** > **Account** and copy the **Key** value.
 3. On your Linux device, run the following command:
 
-   ```sh
-   warp-cli registration license <KEY>
-   ```
-
+	```sh
+	warp-cli registration license <KEY>
+	```
 4. Verify the new registration:
 
-   ```sh
-   warp-cli registration show
-   ```
+	```sh
+	warp-cli registration show
+	```
 
-   ```sh output
-   Account type: Unlimited
-   ...
-   ```
+	```sh output
+	Account type: Unlimited
+	...
+	```
 
 Your WARP+ Unlimited subscription is now active on this device.
 
diff --git a/src/content/docs/warp-client/known-issues-and-faq.mdx b/src/content/docs/warp-client/known-issues-and-faq.mdx
index 3f43023c46ff622..b4e0b7837fc2175 100644
--- a/src/content/docs/warp-client/known-issues-and-faq.mdx
+++ b/src/content/docs/warp-client/known-issues-and-faq.mdx
@@ -7,6 +7,7 @@ products:
 structured_data: true
 sidebar:
   order: 5
+
 ---
 
 Below you will find answers to our most commonly asked questions regarding the WARP client. If you cannot find the answer you are looking for, refer to the [community page](https://community.cloudflare.com/) to explore more resources.
@@ -15,9 +16,9 @@ Below you will find answers to our most commonly asked questions regarding the W
 
 As our [Network Map](https://www.cloudflare.com/network/) shows, we have locations all over the globe. However, in the Advanced Connection stats of our application, you may notice that the server you are connecting to is not necessarily the one physically closest to your location. This can be due to a number of reasons:
 
-- We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
-- Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
-- Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
+* We work hard to prevent it, but sometimes your nearest server might be having problems. [Check the system status](https://www.cloudflarestatus.com/?_ga=2.155811579.1117044671.1600983837-1079355427.1599074097) for more information.
+* Your Internet provider may choose to route traffic along an alternate path for reasons such as cost savings, reliability, or other infrastructure concerns.
+* Not all Cloudflare locations are WARP enabled. We are constantly evaluating performance and how users are connecting, bringing more servers online with WARP all the time.
 
 ## Does WARP reveal my IP address to websites I visit?
 
@@ -35,6 +36,7 @@ Cloudflare WARP is in part powered by [1.1.1.1](/1.1.1.1/), the world's fastest
 
 Cloudflare WARP and the 1.1.1.1 with WARP applications go through performance testing that includes battery, network and CPU on a regular basis. In addition, both applications are used by millions of users worldwide that help us stay on top of issues across a wide variety of devices, networks, sites and applications.
 
+
 ## What is the version of .NET Framework required for the Windows client?
 
 The WARP client for Windows requires .NET Framework version 4.7.2 or later to be installed on your computer.
diff --git a/src/content/docs/warp-client/legal/3rdparty.mdx b/src/content/docs/warp-client/legal/3rdparty.mdx
index 26189309784c944..10a5097703b90b5 100644
--- a/src/content/docs/warp-client/legal/3rdparty.mdx
+++ b/src/content/docs/warp-client/legal/3rdparty.mdx
@@ -5,13 +5,14 @@ pcx_content_type: reference
 description: Third-party licenses used in the WARP client.
 products:
   - warp-client
+
 ---
 
 Following is the third party license information for our desktop applications. License information for our iOS and Android clients can be found in-app.
 
 ## Windows
 
-- ### NetSparkle
+* ### NetSparkle
 
 Copyright (c) 2020 Deadpikle
 
@@ -19,7 +20,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### Reactive Extensions
+* ### Reactive Extensions
 
 Copyright (c) .NET Foundation and Contributors
 
@@ -27,7 +28,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### NLog
+* ### NLog
 
 Copyright (c) 2016, NLog
 
@@ -39,7 +40,7 @@ Redistribution and use in source and binary forms, with or without modification,
 
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### Visual Studio App Center SDK for .NET
+* ### Visual Studio App Center SDK for .NET
 
 Copyright (c) Microsoft Corporation
 
@@ -49,9 +50,9 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### Font-Awesome-WPF
+* ### Font-Awesome-WPF
 
 Copyright (c) 2014-2016 charri
 
@@ -61,7 +62,7 @@ The above copyright notice and this permission notice shall be included in all c
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### WpfScreenHelper
+* ### WpfScreenHelper
 
 Copyright (c) 2014 Michael Denny
 
@@ -73,7 +74,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ## Mac
 
-- ### Sparkle
+* ### Sparkle
 
 Copyright (c) 2006-2013 Andy Matuschak.
 Copyright (c) 2009-2013 Elgato Systems GmbH.
@@ -88,7 +89,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### ITSwitch
+* ### ITSwitch
 
 Copyright 2014 Ilija Tovilo
 
@@ -98,7 +99,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-- ### Visual Studio App Center SDK for Apple platforms
+* ### Visual Studio App Center SDK for Apple platforms
 
 Copyright (c) Microsoft Corporation
 
@@ -108,7 +109,7 @@ MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-THE SOFTWARE IS PROVIDED _AS IS_, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ## Rust
 
@@ -118,21 +119,22 @@ This section lists the licenses of the projects used in cargo-about.
 
 Overview of licenses:
 
-- [MIT](#mit-license) (54)
-- [Apache](#apache-license-20) (41)
-- [BSD](#bsd-3-clause-new-or-revised-license) (8)
-- [BSD](#bsd-2-clause-simplified-license) (3)
-- [ISC](#isc-license) (3)
-- [BSD](#bsd-zero-clause-license) (2)
-- [Mozilla](#mozilla-public-license-20) (2)
-- [OpenSSL](#openssl-license) (1)
+* [MIT](#mit-license) (54)
+* [Apache](#apache-license-20) (41)
+* [BSD](#bsd-3-clause-new-or-revised-license) (8)
+* [BSD](#bsd-2-clause-simplified-license) (3)
+* [ISC](#isc-license) (3)
+* [BSD](#bsd-zero-clause-license) (2)
+* [Mozilla](#mozilla-public-license-20) (2)
+* [OpenSSL](#openssl-license) (1)
 
 All license text:
 
-- ### BSD Zero Clause License
+* ### BSD Zero Clause License
 
   #### Used by:
-  - [managed](https://github.com/m-labs/rust-managed.git)
+
+  * [managed](https://github.com/m-labs/rust-managed.git)
 
   Copyright (C) 2017 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -147,10 +149,11 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### BSD Zero Clause License
+* ### BSD Zero Clause License
 
   #### Used by:
-  - [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
+
+  * [smoltcp](https://github.com/smoltcp-rs/smoltcp.git)
 
   Copyright (C) 2016 [whitequark@whitequark.org](mailto:whitequark@whitequark.org)
 
@@ -165,135 +168,136 @@ All license text:
   AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
   OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [addr](https://github.com/addr-rs/addr)
-  - [addr2line](https://github.com/gimli-rs/addr2line)
-  - [anyhow](https://github.com/dtolnay/anyhow)
-  - [arc-swap](https://github.com/vorner/arc-swap)
-  - [async-trait](https://github.com/dtolnay/async-trait)
-  - [autocfg](https://github.com/cuviper/autocfg)
-  - [backoff](https://github.com/ihrwein/backoff)
-  - [backtrace](https://github.com/rust-lang/backtrace-rs)
-  - [base64](https://github.com/marshallpierce/rust-base64)
-  - [bitflags](https://github.com/bitflags/bitflags)
-  - [bumpalo](https://github.com/fitzgen/bumpalo)
-  - [bzip2](https://github.com/alexcrichton/bzip2-rs)
-  - [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
-  - [cache-padded](https://github.com/stjepang/cache-padded)
-  - [cc](https://github.com/alexcrichton/cc-rs)
-  - [cfg-if](https://github.com/alexcrichton/cfg-if)
-  - [concurrent-queue](https://github.com/stjepang/concurrent-queue)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [core-foundation-sys](https://github.com/servo/core-foundation-rs)
-  - [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
-  - [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
-  - [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
-  - [ct-logs](https://github.com/ctz/ct-logs)
-  - [either](https://github.com/bluss/either)
-  - [errno](https://github.com/lambda-fairy/rust-errno)
-  - [error-chain](https://github.com/rust-lang-nursery/error-chain)
-  - [event-listener](https://github.com/stjepang/event-listener)
-  - [flate2](https://github.com/rust-lang/flate2-rs)
-  - [fnv](https://github.com/servo/rust-fnv)
-  - [form_urlencoded](https://github.com/servo/rust-url)
-  - [gcc](https://github.com/alexcrichton/gcc-rs)
-  - [getopts](https://github.com/rust-lang/getopts)
-  - [gimli](https://github.com/gimli-rs/gimli)
-  - [hashbrown](https://github.com/rust-lang/hashbrown)
-  - [heck](https://github.com/withoutboats/heck)
-  - [hermit-abi](https://github.com/hermitcore/libhermit-rs)
-  - [httparse](https://github.com/seanmonstar/httparse)
-  - [hyper-rustls](https://github.com/ctz/hyper-rustls)
-  - [idna](https://github.com/servo/rust-url/)
-  - [indexmap](https://github.com/bluss/indexmap)
-  - [itoa](https://github.com/dtolnay/itoa)
-  - [jni](https://github.com/jni-rs/jni-rs)
-  - [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
-  - [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs)
-  - [libc](https://github.com/rust-lang/libc)
-  - [lock_api](https://github.com/Amanieu/parking_lot)
-  - [match_cfg](https://github.com/gnzlbg/match_cfg)
-  - [mime](https://github.com/hyperium/mime)
-  - [miow](https://github.com/yoshuawuyts/miow)
-  - [num](https://github.com/rust-num/num)
-  - [num](https://github.com/rust-num/num)
-  - [num-bigint](https://github.com/rust-num/num-bigint)
-  - [num-complex](https://github.com/rust-num/num-complex)
-  - [num-complex](https://github.com/rust-num/num-complex)
-  - [num-integer](https://github.com/rust-num/num-integer)
-  - [num-iter](https://github.com/rust-num/num-iter)
-  - [num-rational](https://github.com/rust-num/num-rational)
-  - [num-rational](https://github.com/rust-num/num-rational)
-  - [num-traits](https://github.com/rust-num/num-traits)
-  - [num_cpus](https://github.com/seanmonstar/num_cpus)
-  - [object](https://github.com/gimli-rs/object)
-  - [once_cell](https://github.com/matklad/once_cell)
-  - [openssl-probe](https://github.com/alexcrichton/openssl-probe)
-  - [parking_lot](https://github.com/Amanieu/parking_lot)
-  - [parking_lot_core](https://github.com/Amanieu/parking_lot)
-  - [paste](https://github.com/dtolnay/paste)
-  - [percent-encoding](https://github.com/servo/rust-url/)
-  - [pfctl](https://github.com/mullvad/pfctl-rs)
-  - [pkg-config](https://github.com/rust-lang/pkg-config-rs)
-  - [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
-  - [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
-  - [proc-macro2](https://github.com/alexcrichton/proc-macro2)
-  - [quote](https://github.com/dtolnay/quote)
-  - [regex](https://github.com/rust-lang/regex)
-  - [regex-syntax](https://github.com/rust-lang/regex)
-  - [reqwest](https://github.com/seanmonstar/reqwest)
-  - [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
-  - [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
-  - [rustversion](https://github.com/dtolnay/rustversion)
-  - [scopeguard](https://github.com/bluss/scopeguard)
-  - [sct](https://github.com/ctz/sct.rs)
-  - [secret-service](https://github.com/hwchen/secret-service-rs.git)
-  - [semver](https://github.com/dtolnay/semver)
-  - [serde](https://github.com/serde-rs/serde)
-  - [serde_derive](https://github.com/serde-rs/serde)
-  - [serde_json](https://github.com/serde-rs/json)
-  - [serde_repr](https://github.com/dtolnay/serde-repr)
-  - [signal-hook-registry](https://github.com/vorner/signal-hook)
-  - [size_format](https://github.com/aticu/size_format)
-  - [slog](https://github.com/slog-rs/slog)
-  - [slog-async](https://github.com/slog-rs/async)
-  - [slog-scope](https://github.com/slog-rs/scope)
-  - [slog-stdlog](https://github.com/slog-rs/stdlog)
-  - [slog-term](https://github.com/slog-rs/term)
-  - [smallvec](https://github.com/servo/rust-smallvec)
-  - [socket2](https://github.com/alexcrichton/socket2-rs)
-  - [socket2](https://github.com/rust-lang/socket2)
-  - [syn](https://github.com/dtolnay/syn)
-  - [tempfile](https://github.com/Stebalien/tempfile)
-  - [term](https://github.com/Stebalien/term)
-  - [thiserror](https://github.com/dtolnay/thiserror)
-  - [thiserror-impl](https://github.com/dtolnay/thiserror)
-  - [thread_local](https://github.com/Amanieu/thread_local-rs)
-  - [time](https://github.com/time-rs/time)
-  - [toml](https://github.com/alexcrichton/toml-rs)
-  - [tungstenite](https://github.com/snapview/tungstenite-rs)
-  - [unicode-bidi](https://github.com/servo/unicode-bidi)
-  - [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
-  - [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
-  - [unicode-width](https://github.com/unicode-rs/unicode-width)
-  - [unicode-xid](https://github.com/unicode-rs/unicode-xid)
-  - [url](https://github.com/servo/rust-url)
-  - [version_check](https://github.com/SergioBenitez/version_check)
-  - [wasi](https://github.com/bytecodealliance/wasi)
-  - [wasi](https://github.com/bytecodealliance/wasi)
-  - [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
-  - [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
-  - [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
-  - [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
-  - [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
-  - [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
-  - [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
+
+  * [addr](https://github.com/addr-rs/addr)
+  * [addr2line](https://github.com/gimli-rs/addr2line)
+  * [anyhow](https://github.com/dtolnay/anyhow)
+  * [arc-swap](https://github.com/vorner/arc-swap)
+  * [async-trait](https://github.com/dtolnay/async-trait)
+  * [autocfg](https://github.com/cuviper/autocfg)
+  * [backoff](https://github.com/ihrwein/backoff)
+  * [backtrace](https://github.com/rust-lang/backtrace-rs)
+  * [base64](https://github.com/marshallpierce/rust-base64)
+  * [bitflags](https://github.com/bitflags/bitflags)
+  * [bumpalo](https://github.com/fitzgen/bumpalo)
+  * [bzip2](https://github.com/alexcrichton/bzip2-rs)
+  * [bzip2-sys](https://github.com/alexcrichton/bzip2-rs)
+  * [cache-padded](https://github.com/stjepang/cache-padded)
+  * [cc](https://github.com/alexcrichton/cc-rs)
+  * [cfg-if](https://github.com/alexcrichton/cfg-if)
+  * [concurrent-queue](https://github.com/stjepang/concurrent-queue)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [core-foundation-sys](https://github.com/servo/core-foundation-rs)
+  * [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam)
+  * [crossbeam-queue](https://github.com/crossbeam-rs/crossbeam)
+  * [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam)
+  * [ct-logs](https://github.com/ctz/ct-logs)
+  * [either](https://github.com/bluss/either)
+  * [errno](https://github.com/lambda-fairy/rust-errno)
+  * [error-chain](https://github.com/rust-lang-nursery/error-chain)
+  * [event-listener](https://github.com/stjepang/event-listener)
+  * [flate2](https://github.com/rust-lang/flate2-rs)
+  * [fnv](https://github.com/servo/rust-fnv)
+  * [form\_urlencoded](https://github.com/servo/rust-url)
+  * [gcc](https://github.com/alexcrichton/gcc-rs)
+  * [getopts](https://github.com/rust-lang/getopts)
+  * [gimli](https://github.com/gimli-rs/gimli)
+  * [hashbrown](https://github.com/rust-lang/hashbrown)
+  * [heck](https://github.com/withoutboats/heck)
+  * [hermit-abi](https://github.com/hermitcore/libhermit-rs)
+  * [httparse](https://github.com/seanmonstar/httparse)
+  * [hyper-rustls](https://github.com/ctz/hyper-rustls)
+  * [idna](https://github.com/servo/rust-url/)
+  * [indexmap](https://github.com/bluss/indexmap)
+  * [itoa](https://github.com/dtolnay/itoa)
+  * [jni](https://github.com/jni-rs/jni-rs)
+  * [js-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys)
+  * [lazy\_static](https://github.com/rust-lang-nursery/lazy-static.rs)
+  * [libc](https://github.com/rust-lang/libc)
+  * [lock\_api](https://github.com/Amanieu/parking_lot)
+  * [match\_cfg](https://github.com/gnzlbg/match_cfg)
+  * [mime](https://github.com/hyperium/mime)
+  * [miow](https://github.com/yoshuawuyts/miow)
+  * [num](https://github.com/rust-num/num)
+  * [num](https://github.com/rust-num/num)
+  * [num-bigint](https://github.com/rust-num/num-bigint)
+  * [num-complex](https://github.com/rust-num/num-complex)
+  * [num-complex](https://github.com/rust-num/num-complex)
+  * [num-integer](https://github.com/rust-num/num-integer)
+  * [num-iter](https://github.com/rust-num/num-iter)
+  * [num-rational](https://github.com/rust-num/num-rational)
+  * [num-rational](https://github.com/rust-num/num-rational)
+  * [num-traits](https://github.com/rust-num/num-traits)
+  * [num\_cpus](https://github.com/seanmonstar/num_cpus)
+  * [object](https://github.com/gimli-rs/object)
+  * [once\_cell](https://github.com/matklad/once_cell)
+  * [openssl-probe](https://github.com/alexcrichton/openssl-probe)
+  * [parking\_lot](https://github.com/Amanieu/parking_lot)
+  * [parking\_lot\_core](https://github.com/Amanieu/parking_lot)
+  * [paste](https://github.com/dtolnay/paste)
+  * [percent-encoding](https://github.com/servo/rust-url/)
+  * [pfctl](https://github.com/mullvad/pfctl-rs)
+  * [pkg-config](https://github.com/rust-lang/pkg-config-rs)
+  * [proc-macro-hack](https://github.com/dtolnay/proc-macro-hack)
+  * [proc-macro-nested](https://github.com/dtolnay/proc-macro-hack)
+  * [proc-macro2](https://github.com/alexcrichton/proc-macro2)
+  * [quote](https://github.com/dtolnay/quote)
+  * [regex](https://github.com/rust-lang/regex)
+  * [regex-syntax](https://github.com/rust-lang/regex)
+  * [reqwest](https://github.com/seanmonstar/reqwest)
+  * [rustc-demangle](https://github.com/alexcrichton/rustc-demangle)
+  * [rustls-native-certs](https://github.com/ctz/rustls-native-certs)
+  * [rustversion](https://github.com/dtolnay/rustversion)
+  * [scopeguard](https://github.com/bluss/scopeguard)
+  * [sct](https://github.com/ctz/sct.rs)
+  * [secret-service](https://github.com/hwchen/secret-service-rs.git)
+  * [semver](https://github.com/dtolnay/semver)
+  * [serde](https://github.com/serde-rs/serde)
+  * [serde\_derive](https://github.com/serde-rs/serde)
+  * [serde\_json](https://github.com/serde-rs/json)
+  * [serde\_repr](https://github.com/dtolnay/serde-repr)
+  * [signal-hook-registry](https://github.com/vorner/signal-hook)
+  * [size\_format](https://github.com/aticu/size_format)
+  * [slog](https://github.com/slog-rs/slog)
+  * [slog-async](https://github.com/slog-rs/async)
+  * [slog-scope](https://github.com/slog-rs/scope)
+  * [slog-stdlog](https://github.com/slog-rs/stdlog)
+  * [slog-term](https://github.com/slog-rs/term)
+  * [smallvec](https://github.com/servo/rust-smallvec)
+  * [socket2](https://github.com/alexcrichton/socket2-rs)
+  * [socket2](https://github.com/rust-lang/socket2)
+  * [syn](https://github.com/dtolnay/syn)
+  * [tempfile](https://github.com/Stebalien/tempfile)
+  * [term](https://github.com/Stebalien/term)
+  * [thiserror](https://github.com/dtolnay/thiserror)
+  * [thiserror-impl](https://github.com/dtolnay/thiserror)
+  * [thread\_local](https://github.com/Amanieu/thread_local-rs)
+  * [time](https://github.com/time-rs/time)
+  * [toml](https://github.com/alexcrichton/toml-rs)
+  * [tungstenite](https://github.com/snapview/tungstenite-rs)
+  * [unicode-bidi](https://github.com/servo/unicode-bidi)
+  * [unicode-normalization](https://github.com/unicode-rs/unicode-normalization)
+  * [unicode-segmentation](https://github.com/unicode-rs/unicode-segmentation)
+  * [unicode-width](https://github.com/unicode-rs/unicode-width)
+  * [unicode-xid](https://github.com/unicode-rs/unicode-xid)
+  * [url](https://github.com/servo/rust-url)
+  * [version\_check](https://github.com/SergioBenitez/version_check)
+  * [wasi](https://github.com/bytecodealliance/wasi)
+  * [wasi](https://github.com/bytecodealliance/wasi)
+  * [wasm-bindgen](https://github.com/rustwasm/wasm-bindgen)
+  * [wasm-bindgen-backend](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/backend)
+  * [wasm-bindgen-futures](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/futures)
+  * [wasm-bindgen-macro](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro)
+  * [wasm-bindgen-macro-support](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro-support)
+  * [wasm-bindgen-shared](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/shared)
+  * [web-sys](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
 
     ```
                           Apache License
@@ -302,6 +306,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -500,10 +505,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [adler](https://github.com/jonas-schievink/adler.git)
+
+  * [adler](https://github.com/jonas-schievink/adler.git)
 
     ```
                           Apache License
@@ -512,6 +518,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -710,32 +717,33 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [aes](https://github.com/RustCrypto/block-ciphers)
-  - [aes-soft](https://github.com/RustCrypto/block-ciphers)
-  - [aesni](https://github.com/RustCrypto/block-ciphers)
-  - [block-buffer](https://github.com/RustCrypto/utils)
-  - [block-buffer](https://github.com/RustCrypto/utils)
-  - [block-modes](https://github.com/RustCrypto/block-ciphers)
-  - [block-padding](https://github.com/RustCrypto/utils)
-  - [block-padding](https://github.com/RustCrypto/utils)
-  - [byte-tools](https://github.com/RustCrypto/utils)
-  - [cipher](https://github.com/RustCrypto/traits)
-  - [cpufeatures](https://github.com/RustCrypto/utils)
-  - [crypto-mac](https://github.com/RustCrypto/traits)
-  - [crypto-mac](https://github.com/RustCrypto/traits)
-  - [digest](https://github.com/RustCrypto/traits)
-  - [digest](https://github.com/RustCrypto/traits)
-  - [fake-simd](https://github.com/RustCrypto/utils)
-  - [hmac](https://github.com/RustCrypto/MACs)
-  - [hmac](https://github.com/RustCrypto/MACs)
-  - [opaque-debug](https://github.com/RustCrypto/utils)
-  - [opaque-debug](https://github.com/RustCrypto/utils)
-  - [sha-1](https://github.com/RustCrypto/hashes)
-  - [sha2](https://github.com/RustCrypto/hashes)
-  - [sha2](https://github.com/RustCrypto/hashes)
+
+  * [aes](https://github.com/RustCrypto/block-ciphers)
+  * [aes-soft](https://github.com/RustCrypto/block-ciphers)
+  * [aesni](https://github.com/RustCrypto/block-ciphers)
+  * [block-buffer](https://github.com/RustCrypto/utils)
+  * [block-buffer](https://github.com/RustCrypto/utils)
+  * [block-modes](https://github.com/RustCrypto/block-ciphers)
+  * [block-padding](https://github.com/RustCrypto/utils)
+  * [block-padding](https://github.com/RustCrypto/utils)
+  * [byte-tools](https://github.com/RustCrypto/utils)
+  * [cipher](https://github.com/RustCrypto/traits)
+  * [cpufeatures](https://github.com/RustCrypto/utils)
+  * [crypto-mac](https://github.com/RustCrypto/traits)
+  * [crypto-mac](https://github.com/RustCrypto/traits)
+  * [digest](https://github.com/RustCrypto/traits)
+  * [digest](https://github.com/RustCrypto/traits)
+  * [fake-simd](https://github.com/RustCrypto/utils)
+  * [hmac](https://github.com/RustCrypto/MACs)
+  * [hmac](https://github.com/RustCrypto/MACs)
+  * [opaque-debug](https://github.com/RustCrypto/utils)
+  * [opaque-debug](https://github.com/RustCrypto/utils)
+  * [sha-1](https://github.com/RustCrypto/hashes)
+  * [sha2](https://github.com/RustCrypto/hashes)
+  * [sha2](https://github.com/RustCrypto/hashes)
 
     ```
                           Apache License
@@ -744,6 +752,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -940,16 +949,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ascii](https://github.com/tomprogrammer/rust-ascii)
+
+  * [ascii](https://github.com/tomprogrammer/rust-ascii)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1150,14 +1161,15 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [async-channel](https://github.com/smol-rs/async-channel)
-  - [ipconfig](https://github.com/liranringel/ipconfig)
-  - [log](https://github.com/rust-lang/log)
-  - [safemem](https://github.com/abonander/safemem)
-  - [uuid](https://github.com/uuid-rs/uuid)
+
+  * [async-channel](https://github.com/smol-rs/async-channel)
+  * [ipconfig](https://github.com/liranringel/ipconfig)
+  * [log](https://github.com/rust-lang/log)
+  * [safemem](https://github.com/abonander/safemem)
+  * [uuid](https://github.com/uuid-rs/uuid)
 
     ```
                           Apache License
@@ -1166,6 +1178,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1364,30 +1377,32 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [cesu8](https://github.com/emk/cesu8-rs)
-  - [ident_case](https://github.com/TedDriggs/ident_case)
-  - [ioctl-sys](https://github.com/jmesmon/ioctl)
-  - [psl](https://github.com/addr-rs/psl)
-  - [psl-types](https://github.com/addr-rs/psl-types)
-  - [rustls](https://github.com/ctz/rustls)
-  - [security-framework](https://github.com/kornelski/rust-security-framework)
-  - [security-framework](https://github.com/kornelski/rust-security-framework)
-  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  - [security-framework-sys](https://github.com/kornelski/rust-security-framework)
-  - [system-configuration](https://github.com/mullvad/system-configuration-rs)
-  - [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
-  - [tinyvec_macros](https://github.com/Soveu/tinyvec_macros)
-  - [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
-  - [winapi-x86_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+
+  * [cesu8](https://github.com/emk/cesu8-rs)
+  * [ident\_case](https://github.com/TedDriggs/ident_case)
+  * [ioctl-sys](https://github.com/jmesmon/ioctl)
+  * [psl](https://github.com/addr-rs/psl)
+  * [psl-types](https://github.com/addr-rs/psl-types)
+  * [rustls](https://github.com/ctz/rustls)
+  * [security-framework](https://github.com/kornelski/rust-security-framework)
+  * [security-framework](https://github.com/kornelski/rust-security-framework)
+  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  * [security-framework-sys](https://github.com/kornelski/rust-security-framework)
+  * [system-configuration](https://github.com/mullvad/system-configuration-rs)
+  * [system-configuration-sys](https://github.com/mullvad/system-configuration-rs)
+  * [tinyvec\_macros](https://github.com/Soveu/tinyvec_macros)
+  * [winapi-i686-pc-windows-gnu](https://github.com/retep998/winapi-rs)
+  * [winapi-x86\_64-pc-windows-gnu](https://github.com/retep998/winapi-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
@@ -1409,6 +1424,7 @@ All license text:
   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
 
   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
   2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
 
   3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
@@ -1455,10 +1471,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [chrono](https://github.com/chronotope/chrono)
+
+  * [chrono](https://github.com/chronotope/chrono)
 
   Rust-chrono is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2]. Copyright (c) 2014--2017, Kang Seonghoon and
@@ -1698,23 +1715,24 @@ All license text:
   limitations under the License.
   ```
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [crc32fast](https://github.com/srijs/rust-crc32fast)
-  - [derive_builder](https://github.com/colin-kiegel/rust-derive-builder)
-  - [derive_builder_core](https://github.com/colin-kiegel/rust-derive-builder)
-  - [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
-  - [hex](https://github.com/KokaKiwi/rust-hex)
-  - [jni-sys](https://github.com/sfackler/rust-jni-sys)
-  - [log-panics](https://github.com/sfackler/rust-log-panics)
-  - [quick-error](http://github.com/tailhook/quick-error)
-  - [resolv-conf](http://github.com/tailhook/resolv-conf)
-  - [trust-dns-https](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
-  - [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
-  - [unreachable](https://github.com/reem/rust-unreachable.git)
+
+  * [crc32fast](https://github.com/srijs/rust-crc32fast)
+  * [derive\_builder](https://github.com/colin-kiegel/rust-derive-builder)
+  * [derive\_builder\_core](https://github.com/colin-kiegel/rust-derive-builder)
+  * [enum-as-inner](https://github.com/bluejekyll/enum-as-inner)
+  * [hex](https://github.com/KokaKiwi/rust-hex)
+  * [jni-sys](https://github.com/sfackler/rust-jni-sys)
+  * [log-panics](https://github.com/sfackler/rust-log-panics)
+  * [quick-error](http://github.com/tailhook/quick-error)
+  * [resolv-conf](http://github.com/tailhook/resolv-conf)
+  * [trust-dns-https](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-proto](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-resolver](https://github.com/bluejekyll/trust-dns)
+  * [trust-dns-rustls](https://github.com/bluejekyll/trust-dns)
+  * [unreachable](https://github.com/reem/rust-unreachable.git)
 
     ```
                              Apache License
@@ -1723,6 +1741,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -1923,16 +1942,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dbus](https://github.com/diwic/dbus-rs)
+
+  * [dbus](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2133,17 +2154,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dbus](https://github.com/diwic/dbus-rs)
-  - [libdbus-sys](https://github.com/diwic/dbus-rs)
+
+  * [dbus](https://github.com/diwic/dbus-rs)
+  * [libdbus-sys](https://github.com/diwic/dbus-rs)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2344,10 +2367,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [deadqueue](https://github.com/bikeshedder/deadqueue)
+
+  * [deadqueue](https://github.com/bikeshedder/deadqueue)
 
     ```
                              Apache License
@@ -2356,6 +2380,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2556,12 +2581,13 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [diff](https://github.com/utkarshkukreti/diff.rs)
-  - [ipnetwork](https://github.com/achanda/ipnetwork)
-  - [winapi](https://github.com/retep998/winapi-rs)
+
+  * [diff](https://github.com/utkarshkukreti/diff.rs)
+  * [ipnetwork](https://github.com/achanda/ipnetwork)
+  * [winapi](https://github.com/retep998/winapi-rs)
 
     ```
                              Apache License
@@ -2570,6 +2596,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2770,13 +2797,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [dirs](https://github.com/soc/dirs-rs)
-  - [dirs-next](https://github.com/xdg-rs/dirs)
-  - [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
-  - [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
+
+  * [dirs](https://github.com/soc/dirs-rs)
+  * [dirs-next](https://github.com/xdg-rs/dirs)
+  * [dirs-sys](https://github.com/dirs-dev/dirs-sys-rs)
+  * [dirs-sys-next](https://github.com/xdg-rs/dirs/tree/master/dirs-sys)
 
     ```
                           Apache License
@@ -2785,6 +2813,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -2954,11 +2983,12 @@ All license text:
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [encoding_rs](https://github.com/hsivonen/encoding_rs)
-  - [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
+
+  * [encoding\_rs](https://github.com/hsivonen/encoding_rs)
+  * [line-wrap](https://bitbucket.org/marshallpierce/line-wrap-rs/src)
 
     ```
                              Apache License
@@ -2967,6 +2997,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3167,10 +3198,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [err-derive](https://gitlab.com/torkleyy/err-derive)
+
+  * [err-derive](https://gitlab.com/torkleyy/err-derive)
 
     ```
                              Apache License
@@ -3179,6 +3211,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3379,18 +3412,19 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [futures](https://github.com/rust-lang/futures-rs)
-  - [futures-channel](https://github.com/rust-lang/futures-rs)
-  - [futures-core](https://github.com/rust-lang/futures-rs)
-  - [futures-executor](https://github.com/rust-lang/futures-rs)
-  - [futures-io](https://github.com/rust-lang/futures-rs)
-  - [futures-macro](https://github.com/rust-lang/futures-rs)
-  - [futures-sink](https://github.com/rust-lang/futures-rs)
-  - [futures-task](https://github.com/rust-lang/futures-rs)
-  - [futures-util](https://github.com/rust-lang/futures-rs)
+
+  * [futures](https://github.com/rust-lang/futures-rs)
+  * [futures-channel](https://github.com/rust-lang/futures-rs)
+  * [futures-core](https://github.com/rust-lang/futures-rs)
+  * [futures-executor](https://github.com/rust-lang/futures-rs)
+  * [futures-io](https://github.com/rust-lang/futures-rs)
+  * [futures-macro](https://github.com/rust-lang/futures-rs)
+  * [futures-sink](https://github.com/rust-lang/futures-rs)
+  * [futures-task](https://github.com/rust-lang/futures-rs)
+  * [futures-util](https://github.com/rust-lang/futures-rs)
 
     ```
                           Apache License
@@ -3399,6 +3433,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3598,19 +3633,20 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [getrandom](https://github.com/rust-random/getrandom)
-  - [getrandom](https://github.com/rust-random/getrandom)
-  - [rand](https://github.com/rust-random/rand)
-  - [rand](https://github.com/rust-random/rand)
-  - [rand_chacha](https://github.com/rust-random/rand)
-  - [rand_chacha](https://github.com/rust-random/rand)
-  - [rand_core](https://github.com/rust-random/rand)
-  - [rand_core](https://github.com/rust-random/rand)
-  - [rand_hc](https://github.com/rust-random/rand)
-  - [rand_hc](https://github.com/rust-random/rand)
+
+  * [getrandom](https://github.com/rust-random/getrandom)
+  * [getrandom](https://github.com/rust-random/getrandom)
+  * [rand](https://github.com/rust-random/rand)
+  * [rand](https://github.com/rust-random/rand)
+  * [rand\_chacha](https://github.com/rust-random/rand)
+  * [rand\_chacha](https://github.com/rust-random/rand)
+  * [rand\_core](https://github.com/rust-random/rand)
+  * [rand\_core](https://github.com/rust-random/rand)
+  * [rand\_hc](https://github.com/rust-random/rand)
+  * [rand\_hc](https://github.com/rust-random/rand)
 
     ```
                           Apache License
@@ -3619,6 +3655,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -3817,10 +3854,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [hkdf](https://github.com/RustCrypto/KDFs/)
+
+  * [hkdf](https://github.com/RustCrypto/KDFs/)
 
     ```
                           Apache License
@@ -3829,6 +3867,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4025,10 +4064,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [http](https://github.com/hyperium/http)
+
+  * [http](https://github.com/hyperium/http)
 
     ```
                           Apache License
@@ -4037,6 +4077,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4235,16 +4276,18 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [httpdate](https://github.com/pyfisch/httpdate)
+
+  * [httpdate](https://github.com/pyfisch/httpdate)
 
   Apache License
   Version 2.0, January 2004
   [http://www.apache.org/licenses/](http://www.apache.org/licenses/)
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
   "License" shall mean the terms and conditions for use, reproduction,
@@ -4303,6 +4346,7 @@ All license text:
   "Contributor" shall mean Licensor and any individual or Legal Entity
   on behalf of whom a Contribution has been received by Licensor and
   subsequently incorporated within the Work.
+
   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
@@ -4366,6 +4410,7 @@ All license text:
   for any such Derivative Works as a whole, provided Your use,
   reproduction, and distribution of the Work otherwise complies with
   the conditions stated in this License.
+
   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
@@ -4439,10 +4484,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
+
+  * [io-kit-sys](https://github.com/jtakakura/io-kit-rs)
 
     ```
                              Apache License
@@ -4451,6 +4497,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4652,10 +4699,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ipnet](https://github.com/krisprice/ipnet)
+
+  * [ipnet](https://github.com/krisprice/ipnet)
 
     ```
                              Apache License
@@ -4664,6 +4712,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -4864,10 +4913,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [keyring](https://github.com/hwchen/keyring-rs.git)
+
+  * [keyring](https://github.com/hwchen/keyring-rs.git)
 
     ```
                           Apache License
@@ -4876,6 +4926,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5074,13 +5125,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
-  - [lru-cache](https://github.com/contain-rs/lru-cache)
-  - [process_path](https://github.com/wesleywiser/process_path)
-  - [vec_map](https://github.com/contain-rs/vec-map)
+
+  * [linked-hash-map](https://github.com/contain-rs/linked-hash-map)
+  * [lru-cache](https://github.com/contain-rs/lru-cache)
+  * [process\_path](https://github.com/wesleywiser/process_path)
+  * [vec\_map](https://github.com/contain-rs/vec-map)
 
     ```
                           Apache License
@@ -5089,6 +5141,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5287,13 +5340,14 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [miniz_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
-  - [pin-project](https://github.com/taiki-e/pin-project)
-  - [pin-project-internal](https://github.com/taiki-e/pin-project)
-  - [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
+
+  * [miniz\_oxide](https://github.com/Frommi/miniz_oxide/tree/master/miniz_oxide)
+  * [pin-project](https://github.com/taiki-e/pin-project)
+  * [pin-project-internal](https://github.com/taiki-e/pin-project)
+  * [pin-project-lite](https://github.com/taiki-e/pin-project-lite)
 
     ```
                              Apache License
@@ -5302,6 +5356,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5473,10 +5528,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ntapi](https://github.com/MSxDOS/ntapi)
+
+  * [ntapi](https://github.com/MSxDOS/ntapi)
 
     ```
                              Apache License
@@ -5485,6 +5541,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5685,10 +5742,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
+
+  * [pin-utils](https://github.com/rust-lang-nursery/pin-utils)
 
     ```
                           Apache License
@@ -5697,6 +5755,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -5895,10 +5954,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
+
+  * [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion)
 
     ```
                           Apache License
@@ -5907,6 +5967,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6103,10 +6164,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
+
+  * [proc-macro-error](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6115,6 +6177,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6313,10 +6376,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
+
+  * [proc-macro-error-attr](https://gitlab.com/CreepySkeleton/proc-macro-error)
 
     ```
                           Apache License
@@ -6325,6 +6389,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6523,10 +6588,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [remove_dir_all](https://github.com/XAMPPRocky/remove_dir_all.git)
+
+  * [remove\_dir\_all](https://github.com/XAMPPRocky/remove_dir_all.git)
 
     ```
                           Apache License
@@ -6535,6 +6601,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -6722,10 +6789,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [rolling-file](https://github.com/Axcient/rolling-file-rs)
+
+  * [rolling-file](https://github.com/Axcient/rolling-file-rs)
 
   rolling-file is dual-licensed under The MIT License \[1] and
   Apache 2.0 License \[2].
@@ -6966,10 +7034,11 @@ All license text:
   limitations under the License.
   ```
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [ryu](https://github.com/dtolnay/ryu)
+
+  * [ryu](https://github.com/dtolnay/ryu)
 
     ```
                              Apache License
@@ -6978,6 +7047,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7178,11 +7248,12 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [serde_urlencoded](https://github.com/nox/serde_urlencoded)
-  - [utf-8](https://github.com/SimonSapin/rust-utf8)
+
+  * [serde\_urlencoded](https://github.com/nox/serde_urlencoded)
+  * [utf-8](https://github.com/SimonSapin/rust-utf8)
 
     ```
                           Apache License
@@ -7191,6 +7262,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7362,10 +7434,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [tinyvec](https://github.com/Lokathor/tinyvec)
+
+  * [tinyvec](https://github.com/Lokathor/tinyvec)
 
     ```
                              Apache License
@@ -7374,6 +7447,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7574,10 +7648,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [tokio-rustls](https://github.com/tokio-rs/tls)
+
+  * [tokio-rustls](https://github.com/tokio-rs/tls)
 
     ```
                           Apache License
@@ -7586,6 +7661,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7784,10 +7860,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [typenum](https://github.com/paholg/typenum)
+
+  * [typenum](https://github.com/paholg/typenum)
 
     ```
                           Apache License
@@ -7796,6 +7873,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -7994,10 +8072,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [webbrowser](https://github.com/amodm/webbrowser-rs)
+
+  * [webbrowser](https://github.com/amodm/webbrowser-rs)
 
   Copyright (c) 2015 Amod Malviya
 
@@ -8024,6 +8103,7 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8195,10 +8275,11 @@ All license text:
 
   END OF TERMS AND CONDITIONS
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [widestring](https://github.com/starkat99/widestring-rs.git)
+
+  * [widestring](https://github.com/starkat99/widestring-rs.git)
 
     ```
                           Apache License
@@ -8207,6 +8288,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8405,10 +8487,11 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [windows-service](https://github.com/mullvad/windows-service-rs)
+
+  * [windows-service](https://github.com/mullvad/windows-service-rs)
 
     ```
                           Apache License
@@ -8417,6 +8500,7 @@ All license text:
     ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8615,14 +8699,16 @@ All license text:
   See the License for the specific language governing permissions and
   limitations under the License.
 
-- ### Apache License 2.0
+* ### Apache License 2.0
 
   #### Used by:
-  - [winlog](https://gitlab.com/arbitrix/winlog)
+
+  * [winlog](https://gitlab.com/arbitrix/winlog)
 
   This software is licensed under either of
-  - Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
-  - MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
+
+  * Apache License, Version 2.0 ([http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+  * MIT license ([http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT))
 
   at your option.
 
@@ -8633,6 +8719,7 @@ All license text:
   ```
 
   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
   1. Definitions.
 
      "License" shall mean the terms and conditions for use, reproduction,
@@ -8855,15 +8942,17 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [ip_network](https://github.com/JakubOnderka/ip_network)
+
+  * [ip\_network](https://github.com/JakubOnderka/ip_network)
 
   Copyright (c) 2017, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8881,15 +8970,17 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [ip_network_table](https://github.com/JakubOnderka/ip_network_table)
+
+  * [ip\_network\_table](https://github.com/JakubOnderka/ip_network_table)
 
   Copyright (c) 2018, Jakub Onderka
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright notice,
@@ -8907,17 +8998,19 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 2-Clause "Simplified" License
+* ### BSD 2-Clause "Simplified" License
 
   #### Used by:
-  - [mach](https://github.com/fitzgen/mach)
-  - [mach](https://github.com/fitzgen/mach)
+
+  * [mach](https://github.com/fitzgen/mach)
+  * [mach](https://github.com/fitzgen/mach)
 
   Copyright (c) 2015, Nick Fitzgerald
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -8936,11 +9029,12 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [app-center](https://github.com/vkrasnov/appcenter-rs)
-  - [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
+
+  * [app-center](https://github.com/vkrasnov/appcenter-rs)
+  * [codesign-verify](https://github.com/vkrasnov/codesign-verify-rs)
 
   BSD 3-Clause License
 
@@ -8949,6 +9043,7 @@ All license text:
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -8971,10 +9066,11 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [boringtun](https://github.com/cloudflare/boringtun)
+
+  * [boringtun](https://github.com/cloudflare/boringtun)
 
   Copyright (c) 2019 Cloudflare, Inc. All rights reserved.
 
@@ -8988,10 +9084,11 @@ All license text:
 
   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [etherparse](https://github.com/JulianSchmid/etherparse)
+
+  * [etherparse](https://github.com/JulianSchmid/etherparse)
 
   BSD 3-Clause License
 
@@ -9023,16 +9120,18 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [instant](https://github.com/sebcrozet/instant)
+
+  * [instant](https://github.com/sebcrozet/instant)
 
   Copyright (c) 2019, Sébastien Crozet
   All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9055,15 +9154,17 @@ All license text:
   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [nel](https://crates.io/crates/nel/0.1.4)
+
+  * [nel](https://crates.io/crates/nel/0.1.4)
 
   Copyright 2021 Cloudflare, Inc. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without modification,
   are permitted provided that the following conditions are met:
+
   1. Redistributions of source code must retain the above copyright notice, this
      list of conditions and the following disclaimer.
 
@@ -9086,16 +9187,18 @@ All license text:
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [subtle](https://github.com/dalek-cryptography/subtle)
+
+  * [subtle](https://github.com/dalek-cryptography/subtle)
 
   Copyright (c) 2016-2017 Isis Agora Lovecruft, Henry de Valence. All rights reserved.
 
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
+
   1. Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
 
@@ -9119,10 +9222,11 @@ All license text:
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### BSD 3-Clause "New" or "Revised" License
+* ### BSD 3-Clause "New" or "Revised" License
 
   #### Used by:
-  - [webpki](https://github.com/briansmith/webpki)
+
+  * [webpki](https://github.com/briansmith/webpki)
 
   // Copyright 2015 The Chromium Authors. All rights reserved.
   //
@@ -9152,10 +9256,11 @@ All license text:
   // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   // Copyright 2017 Brian Smith.
   //
@@ -9171,7 +9276,7 @@ All license text:
   // OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
   // CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-  \#\[macro_use]
+  \#\[macro\_use]
   pub mod constant;
 
   \#\[cfg(feature = "alloc")]
@@ -9179,10 +9284,11 @@ All license text:
 
   pub mod montgomery;
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [untrusted](https://github.com/briansmith/untrusted)
+
+  * [untrusted](https://github.com/briansmith/untrusted)
 
   // Copyright 2015-2016 Brian Smith.
   //
@@ -9198,10 +9304,11 @@ All license text:
   // ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
   // OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 
-- ### ISC License
+* ### ISC License
 
   #### Used by:
-  - [webpki](https://github.com/briansmith/webpki)
+
+  * [webpki](https://github.com/briansmith/webpki)
 
   Except as otherwise noted, this project is licensed under the following
   (ISC-style) terms:
@@ -9223,14 +9330,15 @@ All license text:
   The files under third-party/chromium are licensed as described in
   third-party/chromium/LICENSE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [aho-corasick](https://github.com/BurntSushi/aho-corasick)
-  - [byteorder](https://github.com/BurntSushi/byteorder)
-  - [memchr](https://github.com/BurntSushi/memchr)
-  - [regex-automata](https://github.com/BurntSushi/regex-automata)
-  - [walkdir](https://github.com/BurntSushi/walkdir)
+
+  * [aho-corasick](https://github.com/BurntSushi/aho-corasick)
+  * [byteorder](https://github.com/BurntSushi/byteorder)
+  * [memchr](https://github.com/BurntSushi/memchr)
+  * [regex-automata](https://github.com/BurntSushi/regex-automata)
+  * [walkdir](https://github.com/BurntSushi/walkdir)
 
   The MIT License (MIT)
 
@@ -9254,10 +9362,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ansi_term](https://crates.io/crates/ansi_term)
+
+  * [ansi\_term](https://crates.io/crates/ansi_term)
 
   The MIT License (MIT)
 
@@ -9281,10 +9390,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ansi_term](https://github.com/ogham/rust-ansi-term)
+
+  * [ansi\_term](https://github.com/ogham/rust-ansi-term)
 
   The MIT License (MIT)
 
@@ -9308,10 +9418,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [atty](https://github.com/softprops/atty)
+
+  * [atty](https://github.com/softprops/atty)
 
   Copyright (c) 2015-2019 Doug Tangren
 
@@ -9334,10 +9445,11 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [bytes](https://github.com/tokio-rs/bytes)
+
+  * [bytes](https://github.com/tokio-rs/bytes)
 
   Copyright (c) 2018 Carl Lerche
 
@@ -9365,10 +9477,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [clap](https://github.com/clap-rs/clap)
+
+  * [clap](https://github.com/clap-rs/clap)
 
   The MIT License (MIT)
 
@@ -9392,10 +9505,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [combine](https://github.com/Marwes/combine)
+
+  * [combine](https://github.com/Marwes/combine)
 
   The MIT License (MIT)
 
@@ -9419,12 +9533,13 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [darling](https://github.com/TedDriggs/darling)
-  - [darling_core](https://github.com/TedDriggs/darling)
-  - [darling_macro](https://github.com/TedDriggs/darling)
+
+  * [darling](https://github.com/TedDriggs/darling)
+  * [darling\_core](https://github.com/TedDriggs/darling)
+  * [darling\_macro](https://github.com/TedDriggs/darling)
 
   MIT License
 
@@ -9448,10 +9563,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [data-encoding](https://github.com/ia0/data-encoding)
+
+  * [data-encoding](https://github.com/ia0/data-encoding)
 
   The MIT License (MIT)
 
@@ -9476,16 +9592,17 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [dispatch](http://github.com/SSheldon/rust-dispatch)
-  - [netlink-packet-core](https://github.com/little-dude/netlink)
-  - [netlink-packet-route](https://github.com/little-dude/netlink)
-  - [netlink-packet-utils](https://github.com/little-dude/netlink)
-  - [netlink-sys](https://github.com/little-dude/netlink)
-  - [tokio-macros](https://github.com/tokio-rs/tokio)
-  - [void](https://github.com/reem/rust-void.git)
+
+  * [dispatch](http://github.com/SSheldon/rust-dispatch)
+  * [netlink-packet-core](https://github.com/little-dude/netlink)
+  * [netlink-packet-route](https://github.com/little-dude/netlink)
+  * [netlink-packet-utils](https://github.com/little-dude/netlink)
+  * [netlink-sys](https://github.com/little-dude/netlink)
+  * [tokio-macros](https://github.com/tokio-rs/tokio)
+  * [void](https://github.com/reem/rust-void.git)
 
   MIT License
 
@@ -9495,10 +9612,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
+
+  * [doc-comment](https://github.com/GuillaumeGomez/doc-comment)
 
   MIT License
 
@@ -9522,10 +9640,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
+
+  * [errno-dragonfly](https://github.com/mneumann/errno-dragonfly-rs)
 
   MIT License
 
@@ -9549,10 +9668,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [generic-array](https://github.com/fizyk20/generic-array.git)
+
+  * [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9576,10 +9696,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [generic-array](https://github.com/fizyk20/generic-array.git)
+
+  * [generic-array](https://github.com/fizyk20/generic-array.git)
 
   The MIT License (MIT)
 
@@ -9603,10 +9724,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [h2](https://github.com/hyperium/h2)
+
+  * [h2](https://github.com/hyperium/h2)
 
   Copyright (c) 2017 h2 authors
 
@@ -9634,10 +9756,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [hostname](https://github.com/svartalf/hostname)
+
+  * [hostname](https://github.com/svartalf/hostname)
 
   MIT License
 
@@ -9662,10 +9785,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [http-body](https://github.com/hyperium/http-body)
+
+  * [http-body](https://github.com/hyperium/http-body)
 
   Copyright (c) 2019 Hyper Contributors
 
@@ -9693,10 +9817,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [hyper](https://github.com/hyperium/hyper)
+
+  * [hyper](https://github.com/hyperium/hyper)
 
   Copyright (c) 2014-2021 Sean McArthur
 
@@ -9718,10 +9843,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ip_network_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
+
+  * [ip\_network\_table-deps-treebitmap](https://github.com/JakubOnderka/treebitmap)
 
   Copyright (c) 2016 Hroi Sigurdsson
 
@@ -9749,10 +9875,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [iprange](https://github.com/sticnarf/iprange-rs)
+
+  * [iprange](https://github.com/sticnarf/iprange-rs)
 
   MIT License
 
@@ -9776,10 +9903,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
+
+  * [libproc](https://github.com/andrewdavidmackenzie/libproc-rs)
 
   The MIT License
 
@@ -9802,10 +9930,11 @@ All license text:
   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [matchers](https://github.com/hawkw/matchers)
+
+  * [matchers](https://github.com/hawkw/matchers)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -9827,10 +9956,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [matches](https://github.com/SimonSapin/rust-std-candidates)
+
+  * [matches](https://github.com/SimonSapin/rust-std-candidates)
 
   Copyright (c) 2014-2016 Simon Sapin
 
@@ -9858,10 +9988,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [memoffset](https://github.com/Gilnaa/memoffset)
+
+  * [memoffset](https://github.com/Gilnaa/memoffset)
 
   Copyright (c) 2017 Gilad Naaman
 
@@ -9883,10 +10014,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [mio](https://github.com/tokio-rs/mio)
+
+  * [mio](https://github.com/tokio-rs/mio)
 
   Copyright (c) 2014 Carl Lerche and other MIO contributors
 
@@ -9908,10 +10040,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [nix](https://github.com/nix-rust/nix)
+
+  * [nix](https://github.com/nix-rust/nix)
 
   The MIT License (MIT)
 
@@ -9935,10 +10068,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [plist](https://github.com/ebarnard/rust-plist/)
+
+  * [plist](https://github.com/ebarnard/rust-plist/)
 
   Copyright (c) 2015 Edward Barnard
 
@@ -9960,10 +10094,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [powershell_script](https://github.com/cfsamson/powershell-script)
+
+  * [powershell\_script](https://github.com/cfsamson/powershell-script)
 
   The MIT License (MIT)
 
@@ -9975,10 +10110,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [redox_syscall](https://gitlab.redox-os.org/redox-os/syscall)
+
+  * [redox\_syscall](https://gitlab.redox-os.org/redox-os/syscall)
 
   Copyright (c) 2017 Redox OS Developers
 
@@ -10003,10 +10139,11 @@ All license text:
   OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
   WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [redox_users](https://gitlab.redox-os.org/redox-os/users)
+
+  * [redox\_users](https://gitlab.redox-os.org/redox-os/users)
 
   The MIT License (MIT)
 
@@ -10030,10 +10167,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   The MIT License (MIT)
 
@@ -10058,11 +10196,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [same-file](https://github.com/BurntSushi/same-file)
-  - [winapi-util](https://github.com/BurntSushi/winapi-util)
+
+  * [same-file](https://github.com/BurntSushi/same-file)
+  * [winapi-util](https://github.com/BurntSushi/winapi-util)
 
   The MIT License (MIT)
 
@@ -10086,10 +10225,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [schannel](https://github.com/steffengy/schannel-rs)
+
+  * [schannel](https://github.com/steffengy/schannel-rs)
 
   Copyright (c) 2015 steffengy
 
@@ -10099,10 +10239,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
+
+  * [serde-xml-rs](https://github.com/RReverser/serde-xml-rs)
 
   MIT License
 
@@ -10126,10 +10267,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sharded-slab](https://github.com/hawkw/sharded-slab)
+
+  * [sharded-slab](https://github.com/hawkw/sharded-slab)
 
   Copyright (c) 2019 Eliza Weisman
 
@@ -10151,10 +10293,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [slab](https://github.com/tokio-rs/slab)
+
+  * [slab](https://github.com/tokio-rs/slab)
 
   Copyright (c) 2019 Carl Lerche
 
@@ -10182,10 +10325,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [smbios-lib](https://github.com/jrgerber/smbios-lib)
+
+  * [smbios-lib](https://github.com/jrgerber/smbios-lib)
 
   MIT License
 
@@ -10209,11 +10353,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [spin](https://github.com/mvdnes/spin-rs.git)
-  - [zip](https://github.com/zip-rs/zip.git)
+
+  * [spin](https://github.com/mvdnes/spin-rs.git)
+  * [zip](https://github.com/zip-rs/zip.git)
 
   The MIT License (MIT)
 
@@ -10237,11 +10382,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [strsim](https://github.com/dguo/strsim-rs)
-  - [strsim](https://github.com/dguo/strsim-rs)
+
+  * [strsim](https://github.com/dguo/strsim-rs)
+  * [strsim](https://github.com/dguo/strsim-rs)
 
   The MIT License (MIT)
 
@@ -10266,10 +10412,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [synstructure](https://github.com/mystor/synstructure)
+
+  * [synstructure](https://github.com/mystor/synstructure)
 
   Copyright 2016 Nika Layzell
 
@@ -10279,10 +10426,11 @@ All license text:
 
   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sys-info](https://github.com/FillZpp/sys-info-rs)
+
+  * [sys-info](https://github.com/FillZpp/sys-info-rs)
 
   The MIT License (MIT)
 
@@ -10306,10 +10454,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
+
+  * [sysinfo](https://github.com/GuillaumeGomez/sysinfo)
 
   The MIT License (MIT)
 
@@ -10333,10 +10482,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [take_mut](https://github.com/Sgeo/take_mut)
+
+  * [take\_mut](https://github.com/Sgeo/take_mut)
 
   The MIT License (MIT)
 
@@ -10360,10 +10510,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [textwrap](https://github.com/mgeisler/textwrap)
+
+  * [textwrap](https://github.com/mgeisler/textwrap)
 
   MIT License
 
@@ -10387,11 +10538,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tokio](https://github.com/tokio-rs/tokio)
-  - [tokio-util](https://github.com/tokio-rs/tokio)
+
+  * [tokio](https://github.com/tokio-rs/tokio)
+  * [tokio-util](https://github.com/tokio-rs/tokio)
 
   Copyright (c) 2021 Tokio Contributors
 
@@ -10419,10 +10571,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
+
+  * [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite)
 
   Copyright (c) 2017 Daniel Abramov
   Copyright (c) 2017 Alexey Galakhov
@@ -10445,10 +10598,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [totp-lite](https://github.com/fosskers/totp-lite)
+
+  * [totp-lite](https://github.com/fosskers/totp-lite)
 
   MIT License
 
@@ -10472,10 +10626,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tower-service](https://github.com/tower-rs/tower)
+
+  * [tower-service](https://github.com/tower-rs/tower)
 
   Copyright (c) 2019 Tower Contributors
 
@@ -10503,16 +10658,17 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [tracing](https://github.com/tokio-rs/tracing)
-  - [tracing-appender](https://github.com/tokio-rs/tracing)
-  - [tracing-attributes](https://github.com/tokio-rs/tracing)
-  - [tracing-core](https://github.com/tokio-rs/tracing)
-  - [tracing-log](https://github.com/tokio-rs/tracing)
-  - [tracing-serde](https://github.com/tokio-rs/tracing)
-  - [tracing-subscriber](https://github.com/tokio-rs/tracing)
+
+  * [tracing](https://github.com/tokio-rs/tracing)
+  * [tracing-appender](https://github.com/tokio-rs/tracing)
+  * [tracing-attributes](https://github.com/tokio-rs/tracing)
+  * [tracing-core](https://github.com/tokio-rs/tracing)
+  * [tracing-log](https://github.com/tokio-rs/tracing)
+  * [tracing-serde](https://github.com/tokio-rs/tracing)
+  * [tracing-subscriber](https://github.com/tokio-rs/tracing)
 
   Copyright (c) 2019 Tokio Contributors
 
@@ -10540,10 +10696,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [try-lock](https://github.com/seanmonstar/try-lock)
+
+  * [try-lock](https://github.com/seanmonstar/try-lock)
 
   Copyright (c) 2018 Sean McArthur
   Copyright (c) 2016 Alex Crichton
@@ -10566,10 +10723,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [want](https://github.com/seanmonstar/want)
+
+  * [want](https://github.com/seanmonstar/want)
 
   Copyright (c) 2018-2019 Sean McArthur
 
@@ -10591,12 +10749,13 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [winreg](https://github.com/gentoo90/winreg-rs)
-  - [winreg](https://github.com/gentoo90/winreg-rs)
-  - [winreg](https://github.com/gentoo90/winreg-rs)
+
+  * [winreg](https://github.com/gentoo90/winreg-rs)
+  * [winreg](https://github.com/gentoo90/winreg-rs)
+  * [winreg](https://github.com/gentoo90/winreg-rs)
 
   Copyright (c) 2015 Igor Shaula
 
@@ -10618,10 +10777,11 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [winres](https://github.com/mxre/winres)
+
+  * [winres](https://github.com/mxre/winres)
 
   Copyright 2016 Max Resch
 
@@ -10649,10 +10809,11 @@ All license text:
   IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
   DEALINGS IN THE SOFTWARE.
 
-- ### MIT License
+* ### MIT License
 
   #### Used by:
-  - [xml-rs](https://github.com/netvl/xml-rs)
+
+  * [xml-rs](https://github.com/netvl/xml-rs)
 
   The MIT License (MIT)
 
@@ -10676,10 +10837,12 @@ All license text:
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
   SOFTWARE.
 
-- ### Mozilla Public License 2.0
+* ### Mozilla Public License 2.0
 
   #### Used by:
-  - [cbindgen](https://github.com/eqrion/cbindgen/)
+
+  * [cbindgen](https://github.com/eqrion/cbindgen/)
+
   1. Definitions
 
   ***
@@ -10766,6 +10929,7 @@ All license text:
   whether by contract or otherwise, or (b) ownership of more than
   fifty percent (50%) of the outstanding shares or beneficial
   ownership of such entity.
+
   2. License Grants and Conditions
 
   ***
@@ -10837,6 +11001,7 @@ All license text:
 
   Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
   in Section 2.1.
+
   3. Responsibilities
 
   ***
@@ -10899,6 +11064,7 @@ All license text:
   indemnity or liability terms You offer. You may include additional
   disclaimers of warranty and limitations of liability specific to any
   jurisdiction.
+
   4. Inability to Comply Due to Statute or Regulation
 
   ***
@@ -10912,6 +11078,7 @@ All license text:
   Software under this License. Except to the extent prohibited by statute
   or regulation, such description must be sufficiently detailed for a
   recipient of ordinary skill to be able to understand it.
+
   5. Termination
 
   ***
@@ -10947,6 +11114,7 @@ All license text:
 
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \* \* \* 7. Limitation of Liability \* \* -------------------------- \* \* \* \* Under no circumstances and under no legal theory, whether tort \* \* (including negligence), contract, or otherwise, shall any \* \* Contributor, or anyone who distributes Covered Software as \* \* permitted above, be liable to You for any direct, indirect, \* \* special, incidental, or consequential damages of any character \* \* including, without limitation, damages for lost profits, loss of \* \* goodwill, work stoppage, computer failure or malfunction, or any \* \* and all other commercial damages or losses, even if such party \* \* shall have been informed of the possibility of such damages. This \* \* limitation of liability shall not apply to liability for death or \* \* personal injury resulting from such party's negligence to the \* \* extent applicable law prohibits such limitation. Some \* \* jurisdictions do not allow the exclusion or limitation of \* \* incidental or consequential damages, so this exclusion and \* \* limitation may not apply to You. \* \* \*
   \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
+
   8. Litigation
 
   ***
@@ -10957,6 +11125,7 @@ All license text:
   jurisdiction, without reference to its conflict-of-law provisions.
   Nothing in this Section shall prevent a party's ability to bring
   cross-claims or counter-claims.
+
   9. Miscellaneous
 
   ***
@@ -10967,6 +11136,7 @@ All license text:
   necessary to make it enforceable. Any law or regulation which provides
   that the language of a contract shall be construed against the drafter
   shall not be used to construe this License against a Contributor.
+
   10. Versions of the License
 
   ***
@@ -11018,12 +11188,14 @@ All license text:
   This Source Code Form is "Incompatible With Secondary Licenses", as
   defined by the Mozilla Public License, v. 2.0.
 
-- ### Mozilla Public License 2.0
+* ### Mozilla Public License 2.0
 
   #### Used by:
-  - [webpki-roots](https://github.com/ctz/webpki-roots)
+
+  * [webpki-roots](https://github.com/ctz/webpki-roots)
 
   Mozilla Public License Version 2.0
+
   1. Definitions
 
      1.1. "Contributor" means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.
@@ -11181,10 +11353,11 @@ All license text:
    This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0.
   ```
 
-- ### OpenSSL License
+* ### OpenSSL License
 
   #### Used by:
-  - [ring](https://github.com/briansmith/ring)
+
+  * [ring](https://github.com/briansmith/ring)
 
   /\* Copyright (C) 1995-1998 Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)) \* All rights reserved. \* \* This package is an SSL implementation written \* by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)). \* The implementation was written so as to conform with Netscapes SSL. \* \* This library is free for commercial and non-commercial use as long as \* the following conditions are aheared to. The following conditions \* apply to all code found in this distribution, be it the RC4, RSA, \* lhash, DES, etc., code; not just the SSL code. The SSL documentation \* included with this distribution is covered by the same copyright terms \* except that the holder is Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com)). \* \* Copyright remains Eric Young's, and as such any Copyright notices in \* the code are not to be removed. \* If this package is used in a product, Eric Young should be given attribution \* as the author of the parts of the library used. \* This can be in the form of a textual message at program startup or \* in documentation (online or textual) provided with the package. \* \* Redistribution and use in source and binary forms, with or without \* modification, are permitted provided that the following conditions \* are met: \* 1. Redistributions of source code must retain the copyright \* notice, this list of conditions and the following disclaimer. \* 2. Redistributions in binary form must reproduce the above copyright \* notice, this list of conditions and the following disclaimer in the \* documentation and/or other materials provided with the distribution. \* 3. All advertising materials mentioning features or use of this software \* must display the following acknowledgement: \* "This product includes cryptographic software written by \* Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com))" \* The word 'cryptographic' can be left out if the rouines from the library \* being used are not cryptographic related :-). \* 4. If you include any Windows specific code (or a derivative thereof) from \* the apps directory (application code) you must include an acknowledgement: \* "This product includes software written by Tim Hudson ([tjh@cryptsoft.com](mailto:tjh@cryptsoft.com))" \* \* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG \`\`AS IS'' AND \* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE \* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE \* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE \* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL \* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS \* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) \* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT \* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY \* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF \* SUCH DAMAGE. \* \* The licence and distribution terms for any publically available version or \* derivative of this code cannot be changed. i.e. this code cannot simply be \* copied and put under another distribution licence \* \[including the GNU Public Licence.]
   \*/
diff --git a/src/content/docs/warp-client/legal/index.mdx b/src/content/docs/warp-client/legal/index.mdx
index 2a3706602febaf7..eda71adda87c679 100644
--- a/src/content/docs/warp-client/legal/index.mdx
+++ b/src/content/docs/warp-client/legal/index.mdx
@@ -7,8 +7,9 @@ title: Legal
 hideChildren: true
 sidebar:
   order: 6
+
 ---
 
-- [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
-- [Application Terms of Service](https://www.cloudflare.com/application/terms/)
-- [Third party licenses](/warp-client/legal/3rdparty/)
+* [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/)
+* [Application Terms of Service](https://www.cloudflare.com/application/terms/)
+* [Third party licenses](/warp-client/legal/3rdparty/)
diff --git a/src/content/docs/warp-client/privacy.mdx b/src/content/docs/warp-client/privacy.mdx
index b9d5bb1a7061d21..92288d9c01bb7c0 100644
--- a/src/content/docs/warp-client/privacy.mdx
+++ b/src/content/docs/warp-client/privacy.mdx
@@ -8,6 +8,7 @@ tags:
   - Privacy
 sidebar:
   order: 4
+
 ---
 
 The WARP Client application uses a VPN profile and/or service that enables us to intercept and secure your DNS queries and to transmit data from your device through the Cloudflare network, depending on the services you have enabled. We only collect limited DNS query and traffic data (excluding payload) that is sent to our network when you have the app enabled on your device. All information is handled in accordance with our [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/).
diff --git a/src/content/docs/web-analytics/configuration-options/filters.mdx b/src/content/docs/web-analytics/configuration-options/filters.mdx
index 8ad627a79b2582d..27174f2f041e941 100644
--- a/src/content/docs/web-analytics/configuration-options/filters.mdx
+++ b/src/content/docs/web-analytics/configuration-options/filters.mdx
@@ -5,6 +5,7 @@ products:
 title: Filters
 head: []
 description: Learn how to use filters in Cloudflare Web Analytics.
+
 ---
 
 import { DashButton } from "~/components";
@@ -24,4 +25,4 @@ To filter the data shown on Web Analytics:
 
 - By default, Web Analytics shows data for the previous 24 hours. Adjust the time range using the dropdown menu above the graph.
 - Select and drag the cursor on the graph to choose a custom time period.
-- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
+- Scroll below the graph to view detailed breakdowns, for instance of top visits by country or by device type.
\ No newline at end of file
diff --git a/src/content/docs/web-analytics/configuration-options/index.mdx b/src/content/docs/web-analytics/configuration-options/index.mdx
index 4a728a05e606d7f..390e5e32d1c7476 100644
--- a/src/content/docs/web-analytics/configuration-options/index.mdx
+++ b/src/content/docs/web-analytics/configuration-options/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Configuration options
 sidebar:
   order: 4
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Customize your Web Analytics views by using filters and rules.
 
diff --git a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
index 4766dc07ffc8926..0b5369d3af5186b 100644
--- a/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
+++ b/src/content/docs/web-analytics/data-metrics/core-web-vitals.mdx
@@ -6,6 +6,7 @@ products:
 title: Core Web Vitals
 sidebar:
   order: 3
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,8 +15,10 @@ import { DashButton } from "~/components";
 
 :::note
 
+
 Core Web Vitals is currently only supported in Chromium browsers, with Safari and Firefox coming soon.
 
+
 :::
 
 ## Access Core Web Vitals
@@ -29,7 +32,7 @@ To access Core Web Vitals:
 
 2. Select your website and select **Core Web Vitals**.
 
-### Core Web Vitals metrics
+###  Core Web Vitals metrics
 
 Core Web Vitals is divided into three main sections, each one with information about a specific feature that affects user experience:
 
diff --git a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
index 407d22e05366193..503d9caaf70f22e 100644
--- a/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
+++ b/src/content/docs/web-analytics/data-metrics/data-origin-and-collection.mdx
@@ -11,7 +11,7 @@ tags:
   - Privacy
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Web Analytics relies on the `performance.getEntriesByType('navigation')` object to collect metrics about page load performance. If Navigation Timing Level 2 is not supported, then [`performance.timing` (Level 1)](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) is used.
 
diff --git a/src/content/docs/web-analytics/data-metrics/dimensions.mdx b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
index 2f8158417df0f8f..3caceecb45f0a80 100644
--- a/src/content/docs/web-analytics/data-metrics/dimensions.mdx
+++ b/src/content/docs/web-analytics/data-metrics/dimensions.mdx
@@ -6,6 +6,7 @@ products:
 title: Dimensions
 sidebar:
   order: 4
+
 ---
 
 Dimensions are the labels used to describe different types of metrics or data. For example, **Referer** is the data collected from external links referring visits to a page, while **Browser** shows which browsers accessed your website.
@@ -27,14 +28,14 @@ Below you can find a list of the different dimensions you can use to filter Web
 
 ## Navigation types
 
-| Type                    | Cache hit? | Explanation                                                                                                                                                                                                                                                                                                                                                |
-| ----------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                              |
-| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                  |
-| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                    |
-| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document.                                                                                                                                                                                                     |
-| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document.                                                                                                                                                                                               |
-| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                                                                   |
+| Type                    | Cache hit? | Explanation |
+| ----------------------- | ---------- | ----------- |
+| Navigate                | ❌         | The visitor clicked a link or submitted a form but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
+| Navigate Cache          | ✅         | The visitor clicked a link or submitted a form and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Navigate Prefetch Cache | ✅         | The visitor clicked a link or submitted a form and the document has been prefetched into the browsers HTTP cache, so no network request was necessary for the document. |
+| Prerender               | ✅         | The visitor clicked a link or submitted a form but the browser had already prerendered the page, so no network request was necessary for the document. |
+| Reload                  | ❌         | The visitor reloaded the page but the document was either not found or stale in the browsers HTTP cache, so a network request was made to load the document. |
+| Reload Cache            | ✅         | The visitor reloaded the page and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
 | Back-forward            | ❌         | The visitor used the back/forward buttons/gestures in their browser but the previously-loaded document either not found or stale in the browsers HTTP cache OR a feature was used which prevents using the cache (refer to the explanation in [Back/forward cache](https://web.dev/articles/bfcache)), so a network request was made to load the document. |
-| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document.                                                                                                                                                             |
-| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity.                                                                                                                                                                                                                                                       |
+| Back-forward Cache      | ✅         | The visitor used the back/forward buttons/gestures in their browser and the document was found and fresh within the browsers HTTP cache, so no network request was necessary for the document. |
+| Restore                 | ✅         | The browser was able to restore this page, for example when a tab has been paused due to inactivity. |
diff --git a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
index d3db219922bbfb9..65577424b5e1480 100644
--- a/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
+++ b/src/content/docs/web-analytics/data-metrics/high-level-metrics.mdx
@@ -6,13 +6,14 @@ products:
 title: High-level metrics
 sidebar:
   order: 1
+
 ---
 
 Understanding the key metrics in web analytics is essential for optimizing your website’s performance and user experience. Here are the high-level metrics tracked by Cloudflare Web Analytics:
 
-- **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
-- **Page views** - A successful HTTP response with a content-type of HTML.
-- **Page load time** - The total amount of time required to load the page.
-- **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
+* **Visits** - A page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
+* **Page views** - A successful HTTP response with a content-type of HTML.
+* **Page load time** - The total amount of time required to load the page.
+* **[Core Web Vitals](https://www.cloudflare.com/learning/performance/what-are-core-web-vitals/)** - Higher-level metrics designed by Google to capture the user experience more completely.
 
 ![Web Analytics overview page](~/assets/images/web-analytics/dash-web_analytics-overview.png)
diff --git a/src/content/docs/web-analytics/data-metrics/index.mdx b/src/content/docs/web-analytics/data-metrics/index.mdx
index 7295662b2a7dd44..701245c37266099 100644
--- a/src/content/docs/web-analytics/data-metrics/index.mdx
+++ b/src/content/docs/web-analytics/data-metrics/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Data and metrics
 sidebar:
   order: 5
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 In this section, you can find information about the data and metrics available in Web Analytics.
 
diff --git a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
index 17d8640e8fe0887..ed4e1dedbe02b6b 100644
--- a/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
+++ b/src/content/docs/web-analytics/data-metrics/page-load-time-summary.mdx
@@ -6,6 +6,7 @@ products:
 title: Page load time
 sidebar:
   order: 2
+
 ---
 
 Page load time summary gives you an overview of how long your web page takes to load, broken down by area. To access Page load time:
diff --git a/src/content/docs/web-analytics/faq.mdx b/src/content/docs/web-analytics/faq.mdx
index 50db67fa11ae9e8..57b722a62fab5d6 100644
--- a/src/content/docs/web-analytics/faq.mdx
+++ b/src/content/docs/web-analytics/faq.mdx
@@ -123,11 +123,11 @@ For manual embedding, this script instead connects to `cloudflareinsights.com`,
 connect-src [...existing values...] cloudflareinsights.com
 ```
 
-### How can I enforce Subresource Integrity (SRI) with the JS beacon?
+### How can I enforce Subresource Integrity (SRI) with the JS beacon? 
 
 If you're using the automated injection (i.e. not the manually-embedded script approach mentioned above), Cloudflare automatically includes an `integrity` attribute in the `<script>`. This ensures the script will only execute if a local hash of its downloaded contents match the integrity hash supplied in the HTML.
 
-Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure
+Unfortunately, if you're using the manually-embedded script approach, there is no current way to safely apply an `integrity` attribute because we do not support version-pinning our beacon script. We do this because it ensures we can release periodic updates to maintain security, address bugs and ensure 
 
 ### Can I use the same JS Snippet for a different domain?
 
@@ -159,11 +159,11 @@ When aggregating metrics in the Cloudflare Dashboard or querying the GraphQL API
 
 Note: the GraphQL API exposes a `sampleInterval` field to indicate which level of sampling has been applied to the query.
 
-- The beacon script will fire on every pageview.
-- The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
-- We store the unsampled data for 7 days.
-- We also aggregate it down so it's around 10% of the original volume for long-term storage.
-- Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
+* The beacon script will fire on every pageview.
+* The data ingestion pipeline does not apply sampling—every received beacon will be recorded.
+* We store the unsampled data for 7 days.
+* We also aggregate it down so it's around 10% of the original volume for long-term storage.
+* Sites with very low traffic volumes are sampled to greater percentages to maintain high confidence in aggregate figures.
 
 ### Can I see server-side analytics by URL?
 
diff --git a/src/content/docs/web-analytics/get-started/rum-beacon.mdx b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
index 675f6808ea47e52..11ec40779ef5cee 100644
--- a/src/content/docs/web-analytics/get-started/rum-beacon.mdx
+++ b/src/content/docs/web-analytics/get-started/rum-beacon.mdx
@@ -5,4 +5,5 @@ products:
   - web-analytics
 title: RUM beacon for Web Analytics
 external_link: /speed/observatory/rum-beacon/
----
+
+---
\ No newline at end of file
diff --git a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
index 9ae208a6c8ea4c5..6b3368cab792483 100644
--- a/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
+++ b/src/content/docs/web-analytics/get-started/web-analytics-spa.mdx
@@ -21,9 +21,9 @@ If you want to disable the automatic tracking for SPAs, you can do so by adding
 
 ```html
 <script
-	defer
-	src="https://static.cloudflareinsights.com/beacon.min.js"
-	data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
+  defer
+  src="https://static.cloudflareinsights.com/beacon.min.js"
+  data-cf-beacon=' {"token": "42e216b9090ru59384ygu891dce9eecde", "spa": false} '
 ></script>
 ```
 
@@ -33,7 +33,7 @@ If you are using Google Tag Manager (GTM), you can disable SPA tracking by passi
 
 ```html
 <script
-	defer
-	src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
+  defer
+  src="https://static.cloudflareinsights.com/beacon.min.js?token=42e216b9090ru59384ygu891dce9eecde&spa=false"
 ></script>
 ```
diff --git a/src/content/docs/web-analytics/limits.mdx b/src/content/docs/web-analytics/limits.mdx
index 8a2772d9e9f328e..cc30789f0796155 100644
--- a/src/content/docs/web-analytics/limits.mdx
+++ b/src/content/docs/web-analytics/limits.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Web Analytics - Limits
+
 ---
 
 Cloudflare limits the number of sites for which you can track web analytics, as well as the number of rules allowed for each plan type. Refer to the following tables for more information.
diff --git a/src/content/docs/web3/about.mdx b/src/content/docs/web3/about.mdx
index 12c2faf886781b6..e71d0319dd669a7 100644
--- a/src/content/docs/web3/about.mdx
+++ b/src/content/docs/web3/about.mdx
@@ -29,4 +29,4 @@ Only available for gateways to EVM-based chains, such as [Ethereum](/web3/how-to
 
 Write operations submit new data to the network. For example, sending a transaction or deploying a smart contract. The gateway forwards your request to one of Cloudflare's Ethereum nodes, which places the transaction in its mempool (a queue of pending transactions waiting to be included in a block).
 
-From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
+From there, the network's validators select transactions from the mempool, group them into a block, and reach consensus on the block's validity. Once the block is accepted, it becomes part of the permanent blockchain record. The gateway returns a transaction ID so your application can track the result.
\ No newline at end of file
diff --git a/src/content/docs/web3/api-reference.mdx b/src/content/docs/web3/api-reference.mdx
index 6580ba64f458124..a71630e4616b775 100644
--- a/src/content/docs/web3/api-reference.mdx
+++ b/src/content/docs/web3/api-reference.mdx
@@ -7,4 +7,5 @@ title: API reference
 external_link: /api/resources/web3/subresources/hostnames/methods/list/
 sidebar:
   order: 6
+
 ---
diff --git a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
index 8fa017a894a1131..e8c6ae241ad289f 100644
--- a/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/concepts/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Concepts - Ethereum Gateways
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 As you get started with Cloudflare's Ethereum Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ethereum-gateway/reference/index.mdx b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
index 2bb1163debfdf53..0ac05bf3f8fd5a3 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - Ethereum
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
index ae20777dcb9b048..424052aeb898254 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/kill-switches.mdx
@@ -6,6 +6,7 @@ products:
 title: Kill Switches
 sidebar:
   order: 6
+
 ---
 
 When writing contracts, be especially careful to write secure code and include a
@@ -15,7 +16,7 @@ the smart contract that can be exploited, this can lead to the theft of
 resources from the smart contract or from other individuals.
 
 This was brought into sharp focus during the [infamous DAO
-incident](<https://en.wikipedia.org/wiki/The_DAO_(organization)>). The DAO smart
+incident](https://en.wikipedia.org/wiki/The_DAO_\(organization\)). The DAO smart
 contract acted as a complex, decentralized venture capital fund and held Ether
 worth $250 million at its peak collected from a group of investors. Hackers
 exploited vulnerabilities in the smart contract, stealing $50 million worth of
@@ -23,7 +24,7 @@ Ether.
 
 Because there is no way to undo transactions in Ether, there was a highly
 controversial “hard fork," where the majority of the community agreed to accept
-a block that contained an _irregular state change_ that essentially drained all
+a block that contained an *irregular state change* that essentially drained all
 DAO funds into a special “WithdrawDAO” recovery contract. By convincing enough
 miners to accept this irregular block as valid, the DAO was able to return
 investors funds. However, not everyone agreed with the chain, with those who
@@ -58,7 +59,7 @@ trustworthiness.
 The trust placed in consensus-based algorithms is based on the assumption that
 most people are honest, or more accurately that no sufficiently large subset of
 people can be made to collude to produce a malicious outcome. This is the
-_democratisation of trust_. In the DAO attack, a majority of nodes agreed to
+*democratisation of trust*. In the DAO attack, a majority of nodes agreed to
 accept an irregular state transition. This effectively undid the damage of the
 attack, and shows how, at least in the world of blockchain, perception is
 reality. Because most people “believed" -- accepted this irregular block, it
diff --git a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
index a786977025d3db2..fe72e9e11b576ae 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/rinkeby-deprecation.mdx
@@ -8,6 +8,7 @@ tags:
   - Migration
 sidebar:
   order: 5
+
 ---
 
 Though Cloudflare's Ethereum Gateway launched with support for the Rinkeby testnet, Rinkeby did not run through [The Merge](https://ethereum.org/en/upgrades/merge/) and - as a result - will no longer be a reliable staging environment for mainnet.
@@ -35,20 +36,20 @@ curl https://web3-trial.cloudflare-eth.com/v1/rinkeby \
 
 ```js title="Previous JS Fetch API" {2}
 await fetch(
-	new Request("https://web3-trial.cloudflare-eth.com/v1/rinkeby", {
-		method: "POST",
-		body: JSON.stringify({
-			jsonrpc: "2.0",
-			method: "eth_getBlockByNumber",
-			params: ["0x2244", true],
-			id: 1,
-		}),
-		headers: {
-			"Content-Type": "application/json",
-		},
-	}),
-).then((resp) => {
-	return resp.json();
+  new Request('https://web3-trial.cloudflare-eth.com/v1/rinkeby', {
+    method: 'POST',
+    body: JSON.stringify({
+      jsonrpc: '2.0',
+      method: 'eth_getBlockByNumber',
+      params: ['0x2244', true],
+      id: 1,
+    }),
+    headers: {
+      'Content-Type': 'application/json',
+    },
+  })
+).then(resp => {
+  return resp.json();
 });
 ```
 
@@ -67,19 +68,19 @@ curl https://web3-trial.cloudflare-eth.com/v1/sepolia \
 
 ```js title="New JS Fetch API" {2}
 await fetch(
-	new Request("https://web3-trial.cloudflare-eth.com/v1/sepolia", {
-		method: "POST",
-		body: JSON.stringify({
-			jsonrpc: "2.0",
-			method: "eth_getBlockByNumber",
-			params: ["0x2244", true],
-			id: 1,
-		}),
-		headers: {
-			"Content-Type": "application/json",
-		},
-	}),
-).then((resp) => {
-	return resp.json();
+  new Request('https://web3-trial.cloudflare-eth.com/v1/sepolia', {
+    method: 'POST',
+    body: JSON.stringify({
+      jsonrpc: '2.0',
+      method: 'eth_getBlockByNumber',
+      params: ['0x2244', true],
+      id: 1,
+    }),
+    headers: {
+      'Content-Type': 'application/json',
+    },
+  })
+).then(resp => {
+  return resp.json();
 });
 ```
diff --git a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
index dbc5a494061f6e0..b4932918c9e909b 100644
--- a/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
+++ b/src/content/docs/web3/ethereum-gateway/reference/supported-networks.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Supported networks - Ethereum Gateway
+
 ---
 
 Currently, Cloudflare Ethereum gateways support [interacting with](/web3/how-to/use-ethereum-gateway/) the following networks.
diff --git a/src/content/docs/web3/how-to/index.mdx b/src/content/docs/web3/how-to/index.mdx
index f6ebb1af9d9b691..09b45998630efc4 100644
--- a/src/content/docs/web3/how-to/index.mdx
+++ b/src/content/docs/web3/how-to/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Web3 - How to
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
index d15b08583b61f0b..3987b7170bde027 100644
--- a/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
+++ b/src/content/docs/web3/how-to/use-ipfs-gateway.mdx
@@ -6,6 +6,7 @@ products:
 title: Use IPFS gateway
 sidebar:
   order: 2
+
 ---
 
 Once you have an IPFS gateway — meaning that you [create a new gateway](/web3/how-to/manage-gateways/#create-a-gateway) with a `target` of **IPFS** — you can get data from the IPFS network by using a URL.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
index f4449ce98f8c009..46ac314920cbb5a 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/dnslink.mdx
@@ -8,6 +8,7 @@ tags:
   - DNS
 sidebar:
   order: 4
+
 ---
 
 When you set up a gateway with a DNSLink record, that gateway is restricted to a particular piece of content — either a specific Content Identifier (CID) or an Interplanetary Name Service (IPNS) hostname. This is called a restricted gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
index 77d6c15618f0cde..1f800c90518ab08 100644
--- a/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/concepts/index.mdx
@@ -9,9 +9,10 @@ sidebar:
 head:
   - tag: title
     content: Concepts - IPFS Gateway
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 As you get started with Cloudflare's IPFS Gateway, you may want to read through the following concepts.
 
diff --git a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
index 754e32b96952c90..b47002eb8b4134b 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/automated-deployment.mdx
@@ -6,12 +6,13 @@ products:
 title: Automated deployments
 sidebar:
   order: 6
+
 ---
 
 Static sites are easy to deploy automatically. The code of the site is usually kept in a Git repository and deployed by pushing the latest commit to a repository that's connected to a Continuous Integration service like [Travis CI](https://travis-ci.org/), or by pushing to a repository directly on the server and activating a post-receive hook. Either way, the production version of the site is built and then copied into the serving path of an Apache or NGINX instance.
 
 IPFS usually fits into these systems: instead of copying the production version of a website into the serving path of an HTTP server, you would upload the same files to an IPFS node and update your DNS records with the new hash. There are several tools that help with different parts of this:
 
-- [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
-- [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
-- [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
+* [ipfs-deploy](https://github.com/agentofuser/ipfs-deploy) helps upload data to a third-party pinning providers and automatically update Cloudflare-managed DNS records.
+* [dnslink-cloudflare](https://github.com/ipfs-shipyard/dnslink-cloudflare) is a script to programmatically update DNSLink records. This can be run with the `-Q` flag of `ipfs add` that only outputs the top-level hash.
+* [Fission's IPFS support](https://guide.fission.codes/developers/custom-domains/using-cloudflare-ipfs-gateway) lets you use the Fission IPFS app publishing system from the CLI or from GitHub Actions, while using Cloudflare-managed DNS and gateway.
diff --git a/src/content/docs/web3/ipfs-gateway/reference/index.mdx b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
index 10c80255fdf7a98..c69067dd176b415 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/index.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - IPFS
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
index 81ab323e9cf901a..574f2ebad732b96 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/peering-with-content-providers.mdx
@@ -6,6 +6,7 @@ products:
 title: Peering
 sidebar:
   order: 5
+
 ---
 
 If you are running an IPFS node that serves many requests - like a public HTTP gateway - you may be able to speed up queries by maintaining long-lived connections to nodes that provide a large volume of data.
@@ -14,57 +15,81 @@ This process is known as **Peering** and you can tell IPFS to prioritize Cloudfl
 
 ```json
 {
-	"Peering": {
-		"Peers": [
-			{
-				"ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
-				"Addrs": ["/dnsaddr/node-1.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
-				"Addrs": ["/dnsaddr/node-2.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
-				"Addrs": ["/dnsaddr/node-3.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
-				"Addrs": ["/dnsaddr/node-4.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
-				"Addrs": ["/dnsaddr/node-5.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
-				"Addrs": ["/dnsaddr/node-6.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
-				"Addrs": ["/dnsaddr/node-7.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
-				"Addrs": ["/dnsaddr/node-8.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
-				"Addrs": ["/dnsaddr/node-9.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
-				"Addrs": ["/dnsaddr/node-10.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
-				"Addrs": ["/dnsaddr/node-11.ingress.cloudflare-ipfs.com"]
-			},
-			{
-				"ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
-				"Addrs": ["/dnsaddr/node-12.ingress.cloudflare-ipfs.com"]
-			}
-		]
-	}
+  "Peering": {
+    "Peers": [
+      {
+        "ID": "QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE",
+        "Addrs": [
+          "/dnsaddr/node-1.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z",
+        "Addrs": [
+          "/dnsaddr/node-2.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa",
+        "Addrs": [
+          "/dnsaddr/node-3.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx",
+        "Addrs": [
+          "/dnsaddr/node-4.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ",
+        "Addrs": [
+          "/dnsaddr/node-5.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G",
+        "Addrs": [
+          "/dnsaddr/node-6.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3",
+        "Addrs": [
+          "/dnsaddr/node-7.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP",
+        "Addrs": [
+          "/dnsaddr/node-8.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi",
+        "Addrs": [
+          "/dnsaddr/node-9.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx",
+        "Addrs": [
+          "/dnsaddr/node-10.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5",
+        "Addrs": [
+          "/dnsaddr/node-11.ingress.cloudflare-ipfs.com"
+        ]
+      },
+      {
+        "ID": "QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev",
+        "Addrs": [
+          "/dnsaddr/node-12.ingress.cloudflare-ipfs.com"
+        ]
+      }
+    ]
+  }
 }
 ```
diff --git a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
index 9ae156f2b234174..f66712b07d379ed 100644
--- a/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
+++ b/src/content/docs/web3/ipfs-gateway/reference/updating-for-ipfs.mdx
@@ -6,13 +6,14 @@ products:
 title: Using IPFS with your website
 sidebar:
   order: 5
+
 ---
 
 Though it is not required, it is strongly recommended that websites hosted on IPFS use only relative links, unless linking to a different domain. This is because data can be accessed in many different (but ultimately equivalent) ways:
 
-- From your custom domain: `https://ipfs.tech/index.html`
-- From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
-- By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
+* From your custom domain: `https://ipfs.tech/index.html`
+* From a gateway: `https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html`
+* By immutable hash: `https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html`
 
 Using only relative links within a web application supports all of these at once, and gives the most flexibility to the user. The exact method for switching to relative links, if you do not use them already, depends on the framework you use.
 
diff --git a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
index 658a32e0017e5e9..b76805532e21a27 100644
--- a/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
+++ b/src/content/docs/web3/ipfs-gateway/troubleshooting.mdx
@@ -8,6 +8,7 @@ tags:
   - Debugging
 sidebar:
   order: 11
+
 ---
 
 ## Cloudflare-specific
diff --git a/src/content/docs/web3/reference/gateway-dns-records.mdx b/src/content/docs/web3/reference/gateway-dns-records.mdx
index 44ce03c721e9985..c7ca135a158f53d 100644
--- a/src/content/docs/web3/reference/gateway-dns-records.mdx
+++ b/src/content/docs/web3/reference/gateway-dns-records.mdx
@@ -8,12 +8,13 @@ tags:
   - DNS
 sidebar:
   order: 1
+
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), Cloudflare automatically creates and adds records to your Cloudflare DNS so your gateway can receive and route traffic appropriately:
 
-- **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
-- **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
+* **Ethereum gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ethereum.cloudflare.com`.
+* **IPFS gateways**: Creates a [proxied](/dns/proxy-status/) `CNAME` record pointing your hostname to `ipfs.cloudflare.com` and a `TXT` record with the value specified for its [DNSLink](/web3/ipfs-gateway/concepts/dnslink/#how-is-it-used-with-cloudflare).
 
 These records cannot be edited within Cloudflare DNS. To make edits, you will have to [edit the gateway configuration](/web3/how-to/manage-gateways/#edit-a-gateway) itself.
 
diff --git a/src/content/docs/web3/reference/gateway-status.mdx b/src/content/docs/web3/reference/gateway-status.mdx
index b8f41477bb010ac..f48cc0df30a6a4e 100644
--- a/src/content/docs/web3/reference/gateway-status.mdx
+++ b/src/content/docs/web3/reference/gateway-status.mdx
@@ -6,6 +6,7 @@ products:
 title: Gateway status
 sidebar:
   order: 2
+
 ---
 
 Once you [create a gateway](/web3/how-to/manage-gateways/#create-a-gateway), it can have one of several statuses.
diff --git a/src/content/docs/web3/reference/index.mdx b/src/content/docs/web3/reference/index.mdx
index d5e84b5cb473800..000a9dc1764b37c 100644
--- a/src/content/docs/web3/reference/index.mdx
+++ b/src/content/docs/web3/reference/index.mdx
@@ -9,8 +9,9 @@ sidebar:
 head:
   - tag: title
     content: Reference - Web3 Gateways
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/web3/reference/migration-guide.mdx b/src/content/docs/web3/reference/migration-guide.mdx
index aa20fe71fbcb5ac..438c79c9d19f639 100644
--- a/src/content/docs/web3/reference/migration-guide.mdx
+++ b/src/content/docs/web3/reference/migration-guide.mdx
@@ -8,13 +8,14 @@ tags:
   - Migration
 sidebar:
   order: 4
+
 ---
 
 As announced in [our blog post](https://blog.cloudflare.com/ea-web3-gateways/), Cloudflare is deprecating legacy hostnames that point to our public gateway endpoints at `cloudflare-eth.com` and `cloudflare-ipfs.com`.
 
 If you created a hostname pointing to these gateways during the [private beta](https://blog.cloudflare.com/announcing-web3-gateways/), you should migrate to use our new Web3 gateways to avoid a disruption in service.
 
----
+***
 
 ## Migration guide
 
diff --git a/src/content/docs/workers-ai/agents.mdx b/src/content/docs/workers-ai/agents.mdx
index b54052a2ddfb2a5..6987307dd6a54f5 100644
--- a/src/content/docs/workers-ai/agents.mdx
+++ b/src/content/docs/workers-ai/agents.mdx
@@ -9,12 +9,9 @@ sidebar:
   order: 7
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
-<div style={{ textAlign: "center", marginBottom: "2rem" }}>
-	<p>
-		Build AI assistants that can perform complex tasks on behalf of your users
-		using Cloudflare Workers AI and Agents.
-	</p>
-	<LinkButton href="/agents/">Go to Agents documentation</LinkButton>
-</div>
+<div style={{ textAlign: 'center', marginBottom: '2rem' }}>
+  <p>Build AI assistants that can perform complex tasks on behalf of your users using Cloudflare Workers AI and Agents.</p>
+  <LinkButton href="/agents/">Go to Agents documentation</LinkButton>
+</div>
\ No newline at end of file
diff --git a/src/content/docs/workers-ai/api-reference.mdx b/src/content/docs/workers-ai/api-reference.mdx
index d4399b2cedbf0b1..62cc80dfcec7e8a 100644
--- a/src/content/docs/workers-ai/api-reference.mdx
+++ b/src/content/docs/workers-ai/api-reference.mdx
@@ -7,4 +7,5 @@ products:
   - workers-ai
 sidebar:
   order: 9
+
 ---
diff --git a/src/content/docs/workers-ai/configuration/bindings.mdx b/src/content/docs/workers-ai/configuration/bindings.mdx
index 679ad1f230931bf..51750be8e394b68 100644
--- a/src/content/docs/workers-ai/configuration/bindings.mdx
+++ b/src/content/docs/workers-ai/configuration/bindings.mdx
@@ -43,27 +43,33 @@ To configure a Workers AI binding in your Pages Function, you must use the Cloud
 `async env.AI.run()` runs a model. Takes a model as the first parameter, and an object as the second parameter.
 
 ```javascript
-const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
-	prompt: "What is the origin of the phrase 'Hello, World'",
+const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
+    prompt: "What is the origin of the phrase 'Hello, World'"
 });
 ```
 
 **Parameters**
 
-- `model` <Type text="string" /> <MetaInfo text="required" />
-  - The model to run.
+
+
+* `model` <Type text="string" /> <MetaInfo text="required" />
+
+  * The model to run.
 
   **Supported options**
-  - `stream` <Type text="boolean" /> <MetaInfo text="optional" />
-    - Returns a stream of results as they are available.
+
+  * `stream` <Type text="boolean" /> <MetaInfo text="optional" />
+    * Returns a stream of results as they are available.
+
+
 
 ```javascript
-const answer = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
-	prompt: "What is the origin of the phrase 'Hello, World'",
-	stream: true,
+const answer = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
+    prompt: "What is the origin of the phrase 'Hello, World'",
+    stream: true
 });
 
 return new Response(answer, {
-	headers: { "content-type": "text/event-stream" },
+    headers: { "content-type": "text/event-stream" }
 });
 ```
diff --git a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
index 9daadf9eb13e568..fe7d83c834c46c7 100644
--- a/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
+++ b/src/content/docs/workers-ai/configuration/hugging-face-chat-ui.mdx
@@ -14,9 +14,9 @@ Use Workers AI with [Chat UI](https://github.com/huggingface/chat-ui?tab=readme-
 
 You will need the following:
 
-- A [Cloudflare account](https://dash.cloudflare.com)
-- Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
-- An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
+* A [Cloudflare account](https://dash.cloudflare.com)
+* Your [Account ID](/fundamentals/account/find-account-and-zone-ids/)
+* An [API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id) for Workers AI
 
 ## Setup
 
@@ -28,20 +28,20 @@ When setting up your models, specify the `cloudflare` endpoint.
 
 ```json
 {
-	"name": "nousresearch/hermes-2-pro-mistral-7b",
-	"tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
-	"parameters": {
-		"stop": ["<|im_end|>"]
-	},
-	"endpoints": [
-		{
-			"type": "cloudflare",
-			// optionally specify these if not included in .env.local
-			"accountId": "your-account-id",
-			"apiToken": "your-api-token"
-			//
-		}
-	]
+  "name" : "nousresearch/hermes-2-pro-mistral-7b",
+  "tokenizer": "nousresearch/hermes-2-pro-mistral-7b",
+  "parameters": {
+    "stop": ["<|im_end|>"]
+  },
+  "endpoints" : [
+    {
+      "type": "cloudflare",
+      // optionally specify these if not included in .env.local
+      "accountId": "your-account-id",
+      "apiToken": "your-api-token"
+      //
+    }
+  ]
 }
 ```
 
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
index defd31249419534..1f531e7b4d8115a 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/fetch.mdx
@@ -20,7 +20,7 @@ To do so a `getWeather` function is defined that is passed to the LLM as tool.
 The `getWeather`function extracts the user's location from the request and calls the external weather API via the Workers' [`Fetch API`](/workers/runtime-apis/fetch/) and returns the result.
 
 ```ts title="Embedded function calling example with fetch()"
-import { runWithTools } from "@cloudflare/ai-utils";
+import { runWithTools } from '@cloudflare/ai-utils';
 
 type Env = {
 	AI: Ai;
@@ -31,14 +31,14 @@ export default {
 		// Define function
 		const getWeather = async (args: { numDays: number }) => {
 			const { numDays } = args;
-			// Location is extracted from request based on
-			// https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
-			const lat = request.cf?.latitude;
-			const long = request.cf?.longitude;
+      // Location is extracted from request based on
+      // https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
+      const lat = request.cf?.latitude
+      const long = request.cf?.longitude
 
-			// Interpolate values for external API call
+      // Interpolate values for external API call
 			const response = await fetch(
-				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`,
+				`https://api.open-meteo.com/v1/forecast?latitude=${lat}&longitude=${long}&daily=temperature_2m_max,precipitation_sum&timezone=GMT&forecast_days=${numDays}`
 			);
 			return response.text();
 		};
@@ -46,37 +46,35 @@ export default {
 		const response = await runWithTools(
 			env.AI,
 			// Model with function calling support
-			"@hf/nousresearch/hermes-2-pro-mistral-7b",
+			'@hf/nousresearch/hermes-2-pro-mistral-7b',
 			{
 				// Messages
 				messages: [
 					{
-						role: "user",
-						content: "What the weather like the next 5 days? Respond as text",
+						role: 'user',
+						content: 'What the weather like the next 5 days? Respond as text',
 					},
 				],
 				// Definition of available tools the AI model can leverage
 				tools: [
 					{
-						name: "getWeather",
-						description: "Get the weather for the next [numDays] days",
+						name: 'getWeather',
+						description: 'Get the weather for the next [numDays] days',
 						parameters: {
-							type: "object",
+							type: 'object',
 							properties: {
-								numDays: {
-									type: "numDays",
-									description: "number of days for the weather forecast",
-								},
+								numDays: { type: 'numDays', description: 'number of days for the weather forecast' },
 							},
-							required: ["numDays"],
+							required: ['numDays'],
 						},
 						// reference to previously defined function
 						function: getWeather,
 					},
 				],
-			},
+			}
 		);
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
+
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
index 1f3842dcb258da4..f70be9e51f5b064 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/kv.mdx
@@ -12,7 +12,6 @@ description: Learn how to use Cloudflare Workers AI to interact with KV storage,
 Interact with persistent storage to retrieve or store information enables for powerful use cases.
 
 In this example we show how embedded function calling can interact with other resources on the Cloudflare Developer Platform with a few lines of code.
-
 ## Pre-Requisites
 
 For this example to work, you need to provision a [KV](/kv/) namespace first. To do so, follow the [KV - Get started ](/kv/get-started/) guide.
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
index 0d5b64aae3a9a86..99f3b4077c79279 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/examples/openapi.mdx
@@ -15,54 +15,54 @@ Oftentimes APIs are defined and documented via [OpenAPI specification](https://s
 In this example the LLM will describe the a Github user, based Github's API and its OpenAPI spec.
 
 ```ts title="Embedded function calling example from OpenAPI Spec"
-import { createToolsFromOpenAPISpec, runWithTools } from "@cloudflare/ai-utils";
+import { createToolsFromOpenAPISpec, runWithTools } from '@cloudflare/ai-utils';
 
 type Env = {
 	AI: Ai;
 };
 
-const APP_NAME = "cf-fn-calling-example-app";
+const APP_NAME = 'cf-fn-calling-example-app';
 
 export default {
 	async fetch(request, env, ctx) {
 		const toolsFromOpenAPISpec = [
 			// You can pass the OpenAPI spec link or contents directly
 			...(await createToolsFromOpenAPISpec(
-				"https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json",
+				'https://gist.githubusercontent.com/mchenco/fd8f20c8f06d50af40b94b0671273dc1/raw/f9d4b5cd5944cc32d6b34cad0406d96fd3acaca6/partial_api.github.com.json',
 				{
 					overrides: [
 						{
 							matcher: ({ url }) => {
-								return url.hostname === "api.github.com";
+								return url.hostname === 'api.github.com';
 							},
 							// for all requests on *.github.com, we'll need to add a User-Agent.
 							values: {
 								headers: {
-									"User-Agent": APP_NAME,
+									'User-Agent': APP_NAME,
 								},
 							},
 						},
 					],
-				},
+				}
 			)),
 		];
 
 		const response = await runWithTools(
 			env.AI,
-			"@hf/nousresearch/hermes-2-pro-mistral-7b",
+			'@hf/nousresearch/hermes-2-pro-mistral-7b',
 			{
 				messages: [
 					{
-						role: "user",
-						content:
-							"Who is cloudflare on Github and how many repos does the organization have?",
+						role: 'user',
+						content: 'Who is cloudflare on Github and how many repos does the organization have?',
 					},
 				],
 				tools: toolsFromOpenAPISpec,
-			},
+			}
 		);
 
 		return new Response(JSON.stringify(response));
 	},
 } satisfies ExportedHandler<Env>;
+
 ```
diff --git a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
index c246533acd9ad9b..559cf113e209a3a 100644
--- a/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
+++ b/src/content/docs/workers-ai/features/function-calling/embedded/index.mdx
@@ -13,7 +13,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare has a unique [embedded function calling](https://blog.cloudflare.com/embedded-function-calling) feature that allows you to execute function code alongside your tool call inference. Our npm package [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) is the developer toolkit to get started.
 
@@ -21,8 +21,10 @@ Embedded function calling can be used to easily make complex agents that interac
 
 :::caution[REST API support]
 
+
 Embedded function calling depends on features native to the Workers platform. This means that embedded function calling is only supported via [Cloudflare Workers](/workers-ai/get-started/workers-wrangler/), not via the [REST API](/workers-ai/get-started/rest-api/).
 
+
 :::
 
 ## Resources
diff --git a/src/content/docs/workers-ai/get-started/dashboard.mdx b/src/content/docs/workers-ai/get-started/dashboard.mdx
index e22a698bbeddce6..2ba3fce6dbc68cc 100644
--- a/src/content/docs/workers-ai/get-started/dashboard.mdx
+++ b/src/content/docs/workers-ai/get-started/dashboard.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Follow this guide to create a Workers AI application using the Cloudflare dashboard.
 
@@ -26,12 +26,11 @@ To create a Workers AI application:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Under **Select a template**, select **LLM Chat App**.
 4. Select **Deploy**.
 5. Name your Worker, then select **Create and deploy**.
-6. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
+5. Preview your Worker at its provided [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain.
 
 ## Development
 
diff --git a/src/content/docs/workers-ai/get-started/index.mdx b/src/content/docs/workers-ai/get-started/index.mdx
index a6eeb86d18d02ef..707509ca784b6a0 100644
--- a/src/content/docs/workers-ai/get-started/index.mdx
+++ b/src/content/docs/workers-ai/get-started/index.mdx
@@ -8,7 +8,7 @@ products:
   - workers-ai
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 There are several options to build your Workers AI projects on Cloudflare. To get started, choose your preferred method:
 
@@ -16,6 +16,8 @@ There are several options to build your Workers AI projects on Cloudflare. To ge
 
 :::note
 
+
 These examples are geared towards creating new Workers AI projects. For help adding Workers AI to an existing Worker, refer to [Workers Bindings](/workers-ai/configuration/bindings/).
 
+
 :::
diff --git a/src/content/docs/workers-ai/get-started/rest-api.mdx b/src/content/docs/workers-ai/get-started/rest-api.mdx
index bd2a6f0630db0aa..e25c56fa87f355a 100644
--- a/src/content/docs/workers-ai/get-started/rest-api.mdx
+++ b/src/content/docs/workers-ai/get-started/rest-api.mdx
@@ -11,7 +11,7 @@ products:
   - workers-ai
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 This guide will instruct you through setting up and deploying your first Workers AI project. You will use the Workers AI REST API to experiment with a large language model (LLM).
 
@@ -28,7 +28,6 @@ To get these values:
 1. In the Cloudflare dashboard, go to the **Workers AI** page.
 
    <DashButton url="/?to=/:account/ai/workers-ai" />
-
 2. Select **Use REST API**.
 3. Get your API token:
    1. Select **Create a Workers AI API Token**.
diff --git a/src/content/docs/workers-ai/guides/agents.mdx b/src/content/docs/workers-ai/guides/agents.mdx
index 86751d6187c1375..1e57ab991facb86 100644
--- a/src/content/docs/workers-ai/guides/agents.mdx
+++ b/src/content/docs/workers-ai/guides/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workers-ai
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
index 3b27b14dfda0ebb..bc3a24a9954b382 100644
--- a/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/explore-code-generation-using-deepseek-coder-models.mdx
@@ -14,7 +14,9 @@ products:
   - workers-ai
 ---
 
-import { YouTube } from "~/components";
+
+
+import { YouTube } from "~/components"
 
 A handy way to explore all of the models available on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -24,7 +26,7 @@ You can [download the DeepSeek Coder notebook](/workers-ai/static/documentation/
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
----
+***
 
 ## Exploring Code Generation Using DeepSeek Coder
 
@@ -227,8 +229,8 @@ if __name__ == '__main__':
 
 In this test case, we have two tests:
 
-- `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
-- `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
+* `test_full_name` tests the `full_name` method when the user has both a first name and a last name.
+* `test_default_last_name` tests the `full_name` method when the user only has a first name and the last name is set to "Mc" + first name.
 
 If all these tests pass, it means that the `full_name` method is working as expected. If any of these tests fail, it
 
@@ -344,9 +346,9 @@ display(Markdown(f"""
 
 ```json
 {
-	"firstName": "Craig",
-	"lastName": "Dennis",
-	"numKids": 2,
-	"interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
+  "firstName": "Craig",
+  "lastName": "Dennis",
+  "numKids": 2,
+  "interests": ["AI", "Cloudflare", "Tacos", "Burritos"]
 }
 ```
diff --git a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
index bb75cb0837843ae..3ca61769775d494 100644
--- a/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
+++ b/src/content/docs/workers-ai/guides/tutorials/how-to-choose-the-right-text-generation-model.mdx
@@ -17,7 +17,9 @@ products:
   - workers-ai
 ---
 
-import { YouTube } from "~/components";
+
+
+import { YouTube } from "~/components"
 
 A great way to explore the models that are available to you on [Workers AI](/workers-ai) is to use a [Jupyter Notebook](https://jupyter.org/).
 
@@ -27,7 +29,7 @@ You can [download the Workers AI Text Generation Exploration notebook](/workers-
 
 [comment]: <> "The markdown below is auto-generated from https://github.com/craigsdennis/notebooks-cloudflare-workers-ai"
 
----
+***
 
 ## How to Choose The Right Text Generation Model
 
@@ -146,7 +148,7 @@ questions = [
 speed_date(models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -170,9 +172,9 @@ speed_date(models, questions)
 
 *Generated in *3.63* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -192,9 +194,9 @@ speed_date(models, questions)
 
 *Generated in *4.33* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -214,9 +216,9 @@ speed_date(models, questions)
 
 *Generated in *3.15* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -240,9 +242,9 @@ Remember, these are just a few examples, and your use cases may vary depending o
 
 *Generated in *2.92* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -270,7 +272,7 @@ That's me in a nutshell! I'm ready to help with a wide range of tasks, so feel f
 
 *Generated in *10.28* seconds*
 
----
+***
 
 ### Language Translation
 
@@ -297,7 +299,7 @@ questions = [f"""Translate "{phrase}" from "English" to "{language}" """
 speed_date(proud_translator_models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -387,9 +389,9 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *3.44* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -465,7 +467,7 @@ Please note that this translation is not perfect, as it still retains the origin
 
 *Generated in *1.51* seconds*
 
----
+***
 
 ### Information Retrieval and Summarization
 
@@ -491,7 +493,7 @@ questions = [f"""Summarize the book "{book}" into a few sentences. Ensure to inc
 speed_date(proud_summarizers, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -519,9 +521,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *8.34* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/neural-chat-7b-v3-1-awq
 
@@ -543,9 +545,9 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.04* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -567,7 +569,7 @@ Of course! I'd be happy to help you with that. Here's my summary of "Goodnight M
 
 *Generated in *4.66* seconds*
 
----
+***
 
 ### Content Creation
 
@@ -589,7 +591,7 @@ questions = [
 speed_date(proud_content_creator_models, questions)
 ```
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -625,9 +627,9 @@ I hope these suggestions help! Let me know if you have any other questions or if
 
 *Generated in *1.13* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/zephyr-7b-beta-awq
 
@@ -657,9 +659,9 @@ Tagline: "Say goodbye to cable chaos and hello to a clutter-free workspace with
 
 *Generated in *1.33* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/llama-2-13b-chat-awq
 
@@ -700,15 +702,15 @@ Sure, here's a headline for a blog on why you should use me specifically over ot
 
 Here's a brief summary of why I stand out from other models:
 
-- Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
-- Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
-- Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
+* Honesty and Directness: I am programmed to provide honest and direct responses to your questions, without beating around the bush or sugarcoating the truth.
+* Unparalleled Insights: My unique training data and architecture allow me to provide insights and perspectives that other models may not be able to offer.
+* Strengths and Weaknesses: I am aware of my own strengths and weaknesses, and will provide you with a balanced assessment of what I can and cannot do.
 
 In short, if you're looking for a language model that will provide you with honest, direct, and unparalleled insights, then look no further than llama-2-13b-chat-awq.
 
 *Generated in *10.24* seconds*
 
----
+***
 
 ### Text Classification
 
@@ -739,7 +741,7 @@ sentiment_questions = [sentiment_prompt_template.format(text=comment) for commen
 speed_date(proud_classifiers, sentiment_questions)
 ```
 
----
+***
 
 #### @hf/thebloke/openhermes-2.5-mistral-7b-awq
 
@@ -785,9 +787,9 @@ The sentiment of the text is positive.
 
 *Generated in *0.89* seconds*
 
----
+***
 
----
+***
 
 #### @hf/thebloke/mistral-7b-instruct-v0.1-awq
 
@@ -831,4 +833,4 @@ The sentiment of the text is positive.
 
 *Generated in *1.93* seconds*
 
----
+***
diff --git a/src/content/docs/workers-ai/platform/data-usage.mdx b/src/content/docs/workers-ai/platform/data-usage.mdx
index bab6821ff99f590..9b29840f9db5768 100644
--- a/src/content/docs/workers-ai/platform/data-usage.mdx
+++ b/src/content/docs/workers-ai/platform/data-usage.mdx
@@ -19,7 +19,7 @@ Your inputs (e.g., text prompts, image submissions, audio files, etc.), outputs
 
 For Workers AI:
 
-- You own, and are responsible for, all of your Customer Content.
-- Cloudflare does not make your Customer Content available to any other Cloudflare customer.
-- Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
-- Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
+* You own, and are responsible for, all of your Customer Content.
+* Cloudflare does not make your Customer Content available to any other Cloudflare customer.
+* Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.
+* Your Customer Content for Workers AI may be stored by Cloudflare if you specifically use a storage service (e.g., R2, KV, DO, Vectorize, etc.) in conjunction with Workers AI.
diff --git a/src/content/docs/workers-ai/platform/pricing.mdx b/src/content/docs/workers-ai/platform/pricing.mdx
index 474edbfe1bdd8fb..fd38831c6ee17fc 100644
--- a/src/content/docs/workers-ai/platform/pricing.mdx
+++ b/src/content/docs/workers-ai/platform/pricing.mdx
@@ -35,38 +35,38 @@ The Price in Tokens column is equivalent to the Price in Neurons column - the di
 
 ## LLM model pricing
 
-| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                        |
-| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
-| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                 |
-| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
-| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                               |
-| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                               |
-| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                                |
-| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                                |
-| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
-| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                                |
-| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                                |
-| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                               |
-| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                 |
-| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                                |
-| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                                |
-| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
-| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                                |
-| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                 |
-| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                                |
-| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
-| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                                |
-| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                 |
-| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                 |
-| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                               |
-| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens  |
+| Model                                        | Price in Tokens                                                                                   | Price in Neurons                                                                                                       |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| @cf/meta/llama-3.2-1b-instruct               | $0.027 per M input tokens <br/> $0.201 per M output tokens                                        | 2457 neurons per M input tokens <br/> 18252 neurons per M output tokens                                                |
+| @cf/meta/llama-3.2-3b-instruct               | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-8b-instruct-fp8-fast      | $0.045 per M input tokens <br/> $0.384 per M output tokens                                        | 4119 neurons per M input tokens <br/> 34868 neurons per M output tokens                                                |
+| @cf/meta/llama-3.2-11b-vision-instruct       | $0.049 per M input tokens <br/> $0.676 per M output tokens                                        | 4410 neurons per M input tokens <br/> 61493 neurons per M output tokens                                                |
+| @cf/meta/llama-3.1-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
+| @cf/meta/llama-3.3-70b-instruct-fp8-fast     | $0.293 per M input tokens <br/> $2.253 per M output tokens                                        | 26668 neurons per M input tokens <br/> 204805 neurons per M output tokens                                              |
+| @cf/deepseek-ai/deepseek-r1-distill-qwen-32b | $0.497 per M input tokens <br/> $4.881 per M output tokens                                        | 45170 neurons per M input tokens <br/> 443756 neurons per M output tokens                                              |
+| @cf/mistral/mistral-7b-instruct-v0.1         | $0.110 per M input tokens <br/> $0.190 per M output tokens                                        | 10000 neurons per M input tokens <br/> 17300 neurons per M output tokens                                               |
+| @cf/mistralai/mistral-small-3.1-24b-instruct | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct               | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct-fp8           | $0.152 per M input tokens <br/> $0.287 per M output tokens                                        | 13778 neurons per M input tokens <br/> 26128 neurons per M output tokens                                               |
+| @cf/meta/llama-3.1-8b-instruct-awq           | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
+| @cf/meta/llama-3-8b-instruct                 | $0.282 per M input tokens <br/> $0.827 per M output tokens                                        | 25608 neurons per M input tokens <br/> 75147 neurons per M output tokens                                               |
+| @cf/meta/llama-3-8b-instruct-awq             | $0.123 per M input tokens <br/> $0.266 per M output tokens                                        | 11161 neurons per M input tokens <br/> 24215 neurons per M output tokens                                               |
+| @cf/meta/llama-2-7b-chat-fp16                | $0.556 per M input tokens <br/> $6.667 per M output tokens                                        | 50505 neurons per M input tokens <br/> 606061 neurons per M output tokens                                              |
+| @cf/meta/llama-guard-3-8b                    | $0.484 per M input tokens <br/> $0.030 per M output tokens                                        | 44003 neurons per M input tokens <br/> 2730 neurons per M output tokens                                                |
+| @cf/meta/llama-4-scout-17b-16e-instruct      | $0.270 per M input tokens <br/> $0.850 per M output tokens                                        | 24545 neurons per M input tokens <br/> 77273 neurons per M output tokens                                               |
+| @cf/google/gemma-3-12b-it                    | $0.345 per M input tokens <br/> $0.556 per M output tokens                                        | 31371 neurons per M input tokens <br/> 50560 neurons per M output tokens                                               |
+| @cf/qwen/qwq-32b                             | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
+| @cf/qwen/qwen2.5-coder-32b-instruct          | $0.660 per M input tokens <br/> $1.000 per M output tokens                                        | 60000 neurons per M input tokens <br/> 90909 neurons per M output tokens                                               |
+| @cf/qwen/qwen3-30b-a3b-fp8                   | $0.051 per M input tokens <br/> $0.335 per M output tokens                                        | 4625 neurons per M input tokens <br/> 30475 neurons per M output tokens                                                |
+| @cf/openai/gpt-oss-120b                      | $0.350 per M input tokens <br/> $0.750 per M output tokens                                        | 31818 neurons per M input tokens <br/> 68182 neurons per M output tokens                                               |
+| @cf/openai/gpt-oss-20b                       | $0.200 per M input tokens <br/> $0.300 per M output tokens                                        | 18182 neurons per M input tokens <br/> 27273 neurons per M output tokens                                               |
+| @cf/aisingapore/gemma-sea-lion-v4-27b-it     | $0.351 per M input tokens <br/> $0.555 per M output tokens                                        | 31876 neurons per M input tokens <br/> 50488 neurons per M output tokens                                               |
+| @cf/ibm-granite/granite-4.0-h-micro          | $0.017 per M input tokens <br/> $0.112 per M output tokens                                        | 1542 neurons per M input tokens <br/> 10158 neurons per M output tokens                                                |
+| @cf/zai-org/glm-4.7-flash                    | $0.060 per M input tokens <br/> $0.400 per M output tokens                                        | 5500 neurons per M input tokens <br/> 36400 neurons per M output tokens                                                |
+| @cf/nvidia/nemotron-3-120b-a12b              | $0.500 per M input tokens <br/> $1.500 per M output tokens                                        | 45455 neurons per M input tokens <br/> 136364 neurons per M output tokens                                              |
+| @cf/moonshotai/kimi-k2.5                     | $0.600 per M input tokens <br/> $0.100 per M cached input tokens <br/> $3.000 per M output tokens | 54545 neurons per M input tokens <br/> 9091 neurons per M cached input tokens <br/> 272727 neurons per M output tokens |
 | @cf/moonshotai/kimi-k2.6                     | $0.950 per M input tokens <br/> $0.160 per M cached input tokens <br/> $4.000 per M output tokens | 86364 neurons per M input tokens <br/> 14545 neurons per M cached input tokens <br/> 363636 neurons per M output tokens |
-| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                 |
+| @cf/google/gemma-4-26b-a4b-it                | $0.100 per M input tokens <br/> $0.300 per M output tokens                                        | 9091 neurons per M input tokens <br/> 27273 neurons per M output tokens                                                |
 
 ## Embeddings model pricing
 
diff --git a/src/content/docs/workers-vpc/configuration/index.mdx b/src/content/docs/workers-vpc/configuration/index.mdx
index e669ed279505b79..aee79d0d23cdc78 100644
--- a/src/content/docs/workers-vpc/configuration/index.mdx
+++ b/src/content/docs/workers-vpc/configuration/index.mdx
@@ -12,4 +12,4 @@ products:
 
 import { DirectoryListing } from "~/components";
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
index da1a8323544eed5..e5d02896289509c 100644
--- a/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
+++ b/src/content/docs/workers-vpc/configuration/vpc-services/terraform.mdx
@@ -128,7 +128,6 @@ resource "cloudflare_connectivity_directory_service" "my_database" {
 ```
 
 Valid values for `cert_verification_mode` are:
-
 - `verify_full` (default)
 - `verify_ca`
 - `disabled`
diff --git a/src/content/docs/workers-vpc/examples/private-api.mdx b/src/content/docs/workers-vpc/examples/private-api.mdx
index 09e90435cc172fe..48bc4d0013d7733 100644
--- a/src/content/docs/workers-vpc/examples/private-api.mdx
+++ b/src/content/docs/workers-vpc/examples/private-api.mdx
@@ -87,9 +87,7 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch data from internal API and process it before returning
-			const response = await env.INTERNAL_API.fetch(
-				"http://10.0.1.50:8080/api/data",
-			);
+			const response = await env.INTERNAL_API.fetch("http://10.0.1.50:8080/api/data");
 
 			// Use the response of the private API to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
index 3312f993bec679d..12fb5230fee07fe 100644
--- a/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
+++ b/src/content/docs/workers-vpc/examples/private-s3-bucket.mdx
@@ -125,9 +125,7 @@ export default {
 	async fetch(request, env, ctx) {
 		try {
 			// Fetch a file from the private S3 bucket via VPC endpoint
-			const response = await env.S3_STORAGE.fetch(
-				"https://s3.us-west-2.amazonaws.com/my-bucket/data.json",
-			);
+			const response = await env.S3_STORAGE.fetch("https://s3.us-west-2.amazonaws.com/my-bucket/data.json");
 
 			// Use the response from S3 to perform more logic in Workers, before returning the final response
 			return response;
diff --git a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
index 60995de99ab8b3c..6bc0349de2f2609 100644
--- a/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
+++ b/src/content/docs/workers-vpc/examples/route-across-private-services.mdx
@@ -72,19 +72,15 @@ export default {
 		const url = new URL(request.url);
 
 		// Route to internal services
-		if (url.pathname.startsWith("/api/users")) {
-			const response = await env.USER_SERVICE.fetch(
-				"https://user-api.internal.example.com" + url.pathname,
-			);
+		if (url.pathname.startsWith('/api/users')) {
+			const response = await env.USER_SERVICE.fetch("https://user-api.internal.example.com" + url.pathname);
 			return response;
-		} else if (url.pathname.startsWith("/api/orders")) {
-			const response = await env.ORDER_SERVICE.fetch(
-				"https://orders-api.internal.example.com" + url.pathname,
-			);
+		} else if (url.pathname.startsWith('/api/orders')) {
+			const response = await env.ORDER_SERVICE.fetch("https://orders-api.internal.example.com" + url.pathname);
 			return response;
 		}
 
-		return new Response("Not Found", { status: 404 });
+		return new Response('Not Found', { status: 404 });
 	},
 };
 ```
@@ -111,3 +107,4 @@ curl https://api-gateway.workers.dev/api/orders
 - Implement [rate limiting](/durable-objects/api/)
 - Set up [monitoring and alerting](/analytics/analytics-engine/)
 - Explore [other examples](/workers-vpc/examples/)
+
diff --git a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
index 42c63e8209e1e50..570cd2dcec2d850 100644
--- a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
+++ b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx
@@ -53,7 +53,6 @@ When you merge the PR, Workers Builds will update your build and deploy commands
 If Workers Builds detects a mismatch between your Worker name in the Cloudflare dashboard and the `name` field in your Wrangler configuration file, it will create a pull request to fix the conflict.
 
 This can happen when:
-
 - You rename your Worker in the dashboard but not in your config file
 - You connect a repository that was previously used with a different Worker
 - The `name` field in your config does not match the connected Worker
diff --git a/src/content/docs/workers/ci-cd/builds/build-caching.mdx b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
index 603f75d3db137a1..83e4dd1c9c17496 100644
--- a/src/content/docs/workers/ci-cd/builds/build-caching.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
@@ -35,15 +35,15 @@ Some frameworks provide a cache directory that is typically populated by the fra
 
 The following frameworks support build output caching:
 
-| Framework  | Directories cached                            |
-| ---------- | --------------------------------------------- |
-| Astro      | `node_modules/.astro`                         |
-| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build` |
-| Eleventy   | `.cache`                                      |
-| Gatsby     | `.cache`, `public`                            |
-| Next.js    | `.next/cache`                                 |
-| Nuxt       | `node_modules/.cache/nuxt`                    |
-| SvelteKit  | `node_modules/.cache/imagetools`              |
+| Framework  | Directories cached                                          |
+| ---------- | ----------------------------------------------------------- |
+| Astro      | `node_modules/.astro`                                       |
+| Docusaurus | `node_modules/.cache`, `.docusaurus`, `build`               |
+| Eleventy   | `.cache`                                                    |
+| Gatsby     | `.cache`, `public`                                          |
+| Next.js    | `.next/cache`                                               |
+| Nuxt       | `node_modules/.cache/nuxt`                                  |
+| SvelteKit  | `node_modules/.cache/imagetools`                            |
 
 :::note
 [Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers.
diff --git a/src/content/docs/workers/ci-cd/builds/build-image.mdx b/src/content/docs/workers/ci-cd/builds/build-image.mdx
index 0daab950f2f9c35..828b464902269e7 100644
--- a/src/content/docs/workers/ci-cd/builds/build-image.mdx
+++ b/src/content/docs/workers/ci-cd/builds/build-image.mdx
@@ -91,6 +91,7 @@ Workers Builds are run in the following environment:
 | **Build Environment** | Ubuntu 24.04 |
 | **Architecture**      | x86_64       |
 
+
 ## Build Image Policy
 
 ### Preinstalled Software Updates
@@ -101,7 +102,6 @@ Preinstalled software (languages and tools) will be updated before reaching end-
 - **Major version updates**: Updated to the next stable long-term support (LTS) version with 3 months’ notice.
 
 **How you'll be notified (for changes requiring notice):**
-
 - [Cloudflare Changelog](https://developers.cloudflare.com/changelog/)
 - Dashboard notifications for projects that will receive the update
 - Email notifications to project owners
@@ -111,6 +111,5 @@ To maintain a specific version and avoid automatic updates, [override the defaul
 ### Best Practices
 
 To avoid unexpected build failures:
-
 - **Monitor announcements** via the [Cloudflare Changelog](https://developers.cloudflare.com/changelog/), dashboard notifications, and email
-- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
+- **Pin specific versions** of critical preinstalled software by [overriding default versions](/workers/ci-cd/builds/build-image/#overriding-default-versions)
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
index 6d533ab9b2cede9..032d023592e4d4f 100644
--- a/src/content/docs/workers/ci-cd/builds/configuration.mdx
+++ b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -8,13 +8,7 @@ products:
   - workers
 ---
 
-import {
-	DirectoryListing,
-	Render,
-	Tabs,
-	TabItem,
-	DashButton,
-} from "~/components";
+import { DirectoryListing, Render, Tabs, TabItem, DashButton } from "~/components";
 
 When connecting your Git repository to your Worker, you can customize the configurations needed to build and deploy your Worker.
 
@@ -41,7 +35,7 @@ Note that when you update and save build settings, the updated settings will be
 | **Git repository**                                                                                                    | Choose the Git repository you would like to connect your Worker to.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | **Git branch**                                                                                                        | Select the branch you would like Cloudflare to listen to for new commits. This will be defaulted to `main`.                                                                                                                                                                                                                                                                                                                                                                            |
 | **Build command** _(Optional)_                                                                                        | Set a build command if your project requires a build step (e.g. `npm run build`). This is necessary, for example, when using a [front-end framework](/workers/ci-cd/builds/configuration/#framework-support) such as Next.js or Remix.                                                                                                                                                                                                                                                 |
-| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                         |
+| **[Deploy command](/workers/ci-cd/builds/configuration/#deploy-command)**                                             | The deploy command lets you set the [specific Wrangler command](/workers/wrangler/commands/general/#deploy) used to deploy your Worker. Your deploy command will default to `npx wrangler deploy` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                                                 |
 | **[Non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command)** | Set a command to run when executing [a build for commit on a non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds). This will default to `npx wrangler versions upload` but you may customize this command. Workers Builds will use the Wrangler version set in your `package json`.                                                                                                                                                    |
 | **Root directory** _(Optional)_                                                                                       | Specify the path to your project. The root directory defines where the build command will be run and can be helpful in [monorepos](/workers/ci-cd/builds/advanced-setups/#monorepos) to isolate a specific project within the repository for builds.                                                                                                                                                                                                                                   |
 | **[API token](/workers/ci-cd/builds/configuration/#api-token)** _(Optional)_                                          | The API token is used to authenticate your build request and authorize the upload and deployment of your Worker to Cloudflare. By default, Cloudflare will automatically generate an API token for your account when using Workers Builds, and continue to use this API token for all subsequent builds. Alternatively, you can [create your own API token](/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication/#generate-tokens), or select one that you already own. |
@@ -134,4 +128,4 @@ The following system environment variables are injected by default (but can be o
 | `WORKERS_CI`            | `1`                             | Changing build behaviour when run on Workers Builds versus locally                      |
 | `WORKERS_CI_BUILD_UUID` | `<build-uuid-of-current-build>` | Passing the Build UUID along to custom workflows                                        |
 | `WORKERS_CI_COMMIT_SHA` | `<sha1-hash-of-current-commit>` | Passing current commit ID to error reporting, for example, Sentry                       |
-| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
+| `WORKERS_CI_BRANCH`     | `<branch-name-from-push-event`  | Customizing build based on branch, for example, disabling debug logging on `production` |
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
index 6438ba7c4ac10cf..19c36e00c988216 100644
--- a/src/content/docs/workers/ci-cd/builds/index.mdx
+++ b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -7,7 +7,6 @@ sidebar:
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets you connect a new or existing Worker to a GitHub or GitLab repository, enabling automated builds and deployments for your Worker on push.
@@ -17,7 +16,6 @@ The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets yo
 ### Connect a new Worker
 
 To create a new Worker and connect it to a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -32,7 +30,6 @@ To create a new Worker and connect it to a GitHub or GitLab repository:
 ### Connect an existing Worker
 
 To connect an existing Worker to a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -74,15 +71,14 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 ## Disconnecting builds
 
 To disconnect a Worker from a GitHub or GitLab repository:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
 2. Select the Worker you want to disconnect from a repository.
-3. Select **Settings** and then **Builds**.
-4. Select **Disconnect**.
+4. Select **Settings** and then **Builds**.
+5. Select **Disconnect**.
 
 If you want to switch to a different repository for your Worker, you must first disable builds, then reconnect to select the new repository.
 
-To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
+To disable automatic deployments while still allowing builds to run automatically and save as [versions](/workers/configuration/versions-and-deployments/) (without promoting them to an active deployment), update your deploy command to: `npx wrangler versions upload`.
\ No newline at end of file
diff --git a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
index b5fe2e420f07c48..12161e725454792 100644
--- a/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
+++ b/src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx
@@ -8,19 +8,19 @@ products:
   - workers
 ---
 
-Workers Builds has the following limits.
+Workers Builds has the following limits. 
 
-| Metric                            | Free plan                              | Paid plans                                 |
-| --------------------------------- | -------------------------------------- | ------------------------------------------ |
-| **Build minutes**                 | 3,000 per month                        | 6,000 per month (then, +$0.005 per minute) |
-| **Concurrent builds**             | 1                                      | 6                                          |
-| **Build timeout**                 | 20 minutes                             | 20 minutes                                 |
-| **Deploy Hooks**                  | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account     |
-| **CPU**                           | 2 vCPU                                 | 4 vCPU                                     |
-| **Memory**                        | 8 GB                                   | 8 GB                                       |
-| **Disk space**                    | 20 GB                                  | 20 GB                                      |
-| **Environment variables**         | 64                                     | 64                                         |
-| **Size per environment variable** | 5 KB                                   | 5 KB                                       |
+| Metric                | Free plan       | Paid plans                                 |
+| --------------------- | --------------- | ------------------------------------------ |
+| **Build minutes**     | 3,000 per month | 6,000 per month (then, +$0.005 per minute) |
+| **Concurrent builds** | 1               | 6                                          |
+| **Build timeout**     | 20 minutes      | 20 minutes                                 |
+| **Deploy Hooks**      | 10/min per Worker, 100/min per account | 10/min per Worker, 100/min per account |
+| **CPU**               | 2 vCPU          | 4 vCPU                                     |
+| **Memory**            | 8 GB            | 8 GB                                       |
+| **Disk space**        | 20 GB           | 20 GB                                      |
+| **Environment variables**  | 64              | 64                                        |
+| **Size per environment variable**  | 5 KB            | 5 KB                                       |
 
 ## Definitions
 
diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
index 34a4b8f9fba5a10..19e65105b5e0d03 100644
--- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
+++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx
@@ -35,7 +35,6 @@ On Wrangler v3 and up, Workers Builds automatically matches the name of the conn
 `✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. wrangler deploy path/to/script) or the main config field.`
 
 If you see this error, a Wrangler configuration file is likely missing from the root directory. Navigate to **Settings** > **Build** > **Build Configuration** to update the root directory, or add a [Wrangler configuration file](/workers/wrangler/configuration/) to the specified directory.
-
 ### Incorrect account_id
 
 `Could not route to /client/v4/accounts/<Account ID>/workers/services/<Worker name>, perhaps your object identifier is invalid? [code: 7003]`
diff --git a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
index f67f5ae1685a419..2eae230b3612062 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
@@ -5,7 +5,6 @@ description: Integrate Workers development into your existing GitHub Actions wor
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitHub Actions](https://github.com/marketplace/actions/deploy-to-cloudflare-workers-with-wrangler). Here is how you can set up your GitHub Actions workflow.
@@ -21,7 +20,6 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
 ### API token
 
 To create an API token to authenticate Wrangler in your CI job:
-
 1. In the Cloudflare dashboard, go to the **Account API tokens** page.
 
    <DashButton url="/?to=/:account/api-tokens" />
diff --git a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
index 713a4dfc47d7707..ad35eea9bad7ff5 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
@@ -5,7 +5,6 @@ description: Integrate Workers development into your existing GitLab Pipelines w
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 You can deploy Workers with [GitLab CI/CD](https://docs.gitlab.com/ee/ci/pipelines/index.html). Here is how you can set up your Gitlab CI/CD pipeline.
diff --git a/src/content/docs/workers/configuration/integrations/index.mdx b/src/content/docs/workers/configuration/integrations/index.mdx
index e9f73b20e932138..23a188bf0e4e94c 100644
--- a/src/content/docs/workers/configuration/integrations/index.mdx
+++ b/src/content/docs/workers/configuration/integrations/index.mdx
@@ -14,24 +14,24 @@ One of the key features of Cloudflare Workers is the ability to integrate with o
 
 Cloudflare Workers offers several types of integrations, including:
 
-- [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
-- [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
-- [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
+* [Databases](/workers/databases/): Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
+* [APIs](/workers/configuration/integrations/apis/): Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
+* [Third-party services](/workers/configuration/integrations/external-services/): Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.
 
 ## How to use integrations
 
 To use any of the available integrations:
 
-- Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
-- In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
-- Use the provided APIs and functions to connect to the integration and access its data or functionality.
-- Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
+* Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
+* In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
+* Use the provided APIs and functions to connect to the integration and access its data or functionality.
+* Store necessary secrets and keys using secrets via [`wrangler secret put <KEY>`](/workers/wrangler/commands/general/#secret).
 
 ## Tips and best practices
 
 To help you get the most out of using integrations with Cloudflare Workers:
 
-- Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
-- Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
-- Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
-- Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
+* Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
+* Use [caching](/workers/reference/how-the-cache-works) to improve performance and reduce the load on an external service.
+* Split your Workers into service-oriented architecture using [Service bindings](/workers/runtime-apis/bindings/service-bindings/) to make your application more modular, easier to maintain, and more performant.
+* Use [Custom Domains](/workers/configuration/routing/custom-domains/) when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.
diff --git a/src/content/docs/workers/configuration/routing/custom-domains.mdx b/src/content/docs/workers/configuration/routing/custom-domains.mdx
index dccd631d43e8638..be78f27efb57efa 100644
--- a/src/content/docs/workers/configuration/routing/custom-domains.mdx
+++ b/src/content/docs/workers/configuration/routing/custom-domains.mdx
@@ -14,7 +14,7 @@ Custom Domains allow you to connect your Worker to a domain or subdomain, withou
 
 Custom Domains are routes to a domain or subdomain (such as `example.com` or `shop.example.com`) within a Cloudflare zone where the Worker is the origin.
 
-Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with. If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
+Custom Domains are recommended if you want to connect your Worker to the Internet and do not have an application server that you want to always communicate with.  If you do have external dependencies, you can create a `Request` object with the target URI, and use `fetch()` to reach out.
 
 Custom Domains can stack on top of each other. For example, if you have Worker A attached to `app.example.com` and Worker B attached to `api.example.com`, Worker A can call `fetch()` on `api.example.com` and invoke Worker B.
 
@@ -33,8 +33,10 @@ Custom Domains can be attached to your Worker via the Cloudflare dashboard, [Wra
 
 :::caution
 
+
 You cannot create a Custom Domain on a hostname with an existing CNAME DNS record or on a zone you do not own.
 
+
 :::
 
 ### Set up a Custom Domain in the dashboard
@@ -75,6 +77,8 @@ To configure a Custom Domain in your [Wrangler configuration file](/workers/wran
 
 To configure multiple Custom Domains:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -102,8 +106,8 @@ On the same zone, if a Worker is attempting to communicate with a target Worker
 
 For example, consider the following scenario, where both Workers are running on the `example.com` Cloudflare zone:
 
-- `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
-- `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
+* `worker-a` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `auth.example.com/*`.
+* `worker-b` running on the [route](/workers/configuration/routing/routes/#set-up-a-route) `shop.example.com/*`.
 
 If `worker-a` sends a fetch request to `worker-b`, the request will fail, because of the limitation on same-zone fetch requests. `worker-a` must have a service binding to `worker-b` for this request to resolve.
 
@@ -111,9 +115,9 @@ If `worker-a` sends a fetch request to `worker-b`, the request will fail, becaus
 export default {
 	fetch(request) {
 		// This will fail
-		return fetch("https://shop.example.com");
-	},
-};
+		return fetch("https://shop.example.com")
+	}
+}
 ```
 
 However, if `worker-b` was instead set up to run on the Custom Domain `shop.example.com`, the fetch request would succeed.
@@ -138,15 +142,15 @@ For example, consider the following workflow:
 ```js title="auth-worker" {8}
 export default {
 	fetch(request) {
-		const url = new URL(request.url);
-		if (url.searchParams.get("auth") !== "SECRET_TOKEN") {
-			return new Response(null, { status: 401 });
+		const url = new URL(request.url)
+		if(url.searchParams.get("auth") !== "SECRET_TOKEN") {
+			return new Response(null, { status: 401 })
 		} else {
 			// This will invoke `api-worker`
-			return fetch(request);
+			return fetch(request)
 		}
-	},
-};
+	}
+}
 ```
 
 ## Certificates
@@ -162,10 +166,10 @@ Because Custom Domains require an exact hostname match, a Worker attached to `ex
 - [Redirect from www to root](/rules/url-forwarding/examples/redirect-www-to-root/)
 - [Redirect from root to www](/rules/url-forwarding/examples/redirect-root-to-www/)
 
-You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting _from_, so that Cloudflare can apply the redirect rule.
+You also need a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the hostname you are redirecting *from*, so that Cloudflare can apply the redirect rule.
 
-- For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
-- For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+  - For www to root: Add a proxied DNS `A` record for `www` pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
+  - For root to www: Add a proxied DNS `A` record for your root domain pointing to `192.0.2.0`, or a proxied `AAAA` record pointing to `100::`
 
 :::note
 `192.0.2.0` (A record) and `100::` (AAAA record) are [reserved placeholder addresses](/dns/manage-dns-records/how-to/create-dns-records/#originless-setups) for originless setups. Because the DNS record is proxied, requests never reach this address — Cloudflare intercepts them and applies your redirect rule.
@@ -220,4 +224,4 @@ To migrate the route `example.com/*` in your [Wrangler configuration file](/work
    </WranglerConfig>
 
 4. Run `npx  wrangler deploy` to create the Custom Domain your Worker will run on.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/workers/configuration/routing/routes.mdx b/src/content/docs/workers/configuration/routing/routes.mdx
index 977bc4da059df0f..867c38239a1de4e 100644
--- a/src/content/docs/workers/configuration/routing/routes.mdx
+++ b/src/content/docs/workers/configuration/routing/routes.mdx
@@ -95,6 +95,8 @@ Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `z
 
 To add multiple routes:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -192,12 +194,12 @@ Because `*` matches zero or more of **any character** (not just subdomains), `*e
 
 The following examples illustrate the difference between `*example.com/*` and `*.example.com/*`:
 
-| Request URL                    | `*example.com/*` | `*.example.com/*` |
-| ------------------------------ | ---------------- | ----------------- |
-| `https://example.com/`         | Matches          | Does not match    |
-| `https://www.example.com/path` | Matches          | Matches           |
-| `https://myexample.com/`       | Matches          | Does not match    |
-| `https://not-example.com/`     | Does not match   | Does not match    |
+| Request URL | `*example.com/*` | `*.example.com/*` |
+|---|---|---|
+| `https://example.com/` | Matches | Does not match |
+| `https://www.example.com/path` | Matches | Matches |
+| `https://myexample.com/` | Matches | Does not match |
+| `https://not-example.com/` | Does not match | Does not match |
 
 #### Paths may optionally end with `*`
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-existing.mdx b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
index 005eac692d1bd1f..5ec6aea9c3faf4a 100644
--- a/src/content/docs/workers/configuration/sites/start-from-existing.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-existing.mdx
@@ -40,16 +40,16 @@ To deploy a pre-existing static site project, start with a pre-generated site. W
 2. Add your site's build/output directory to the Wrangler file:
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "site": {
-          "bucket": "./public" // <-- Add your build directory name here.
-        }
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "site": {
+       "bucket": "./public" // <-- Add your build directory name here.
+     }
+   }
+   ```
+
+   </WranglerConfig>
 
    The default directories for the most popular static site generators are listed below:
    - Hugo: `public`
@@ -138,14 +138,14 @@ async function handleEvent(event) {
 6. Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone. Add a `route` property to the Wrangler file.
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "route": "https://example.com/*"
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "route": "https://example.com/*"
+   }
+   ```
+
+   </WranglerConfig>
 
    :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
index 4406df19ce0437c..8dd326cda0b305d 100644
--- a/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-scratch.mdx
@@ -55,39 +55,39 @@ The template project contains the following files and directories:
 - Change the `name` property to the name of your project:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "$schema": "./node_modules/wrangler/config-schema.json",
-      "name": "my-site"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "$schema": "./node_modules/wrangler/config-schema.json",
+    "name": "my-site"
+  }
+  ```
+
+  </WranglerConfig>
 
 - Consider updating`compatibility_date` to today's date to get access to the most recent Workers features:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "compatibility_date": "yyyy-mm-dd"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "compatibility_date": "yyyy-mm-dd"
+  }
+  ```
+
+  </WranglerConfig>
 
 - Deploy your site to a [custom domain](/workers/configuration/routing/custom-domains/) that you own and have already attached as a Cloudflare zone:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-      "route": "https://example.com/*"
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+    "route": "https://example.com/*"
+  }
+  ```
+
+  </WranglerConfig>
 
   :::note
 
diff --git a/src/content/docs/workers/configuration/sites/start-from-worker.mdx b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
index 78314e60913a490..55e9d74a41f69f7 100644
--- a/src/content/docs/workers/configuration/sites/start-from-worker.mdx
+++ b/src/content/docs/workers/configuration/sites/start-from-worker.mdx
@@ -24,16 +24,16 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st
 2. Add configuration to your Wrangler file to point to it.
 
    <WranglerConfig>
-   
-      ```jsonc
-      {
-        "site": {
-          "bucket": "./public" // Add the directory with your static assets!
-        }
-      }
-      ```
-   
-      </WranglerConfig>
+
+   ```jsonc
+   {
+     "site": {
+       "bucket": "./public" // Add the directory with your static assets!
+     }
+   }
+   ```
+
+   </WranglerConfig>
 
 3. Install the `@cloudflare/kv-asset-handler` package in your project:
 
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
index c5f131c4787fd9c..c32f452efe28734 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
@@ -6,7 +6,6 @@ description: Upload versions of Workers and create deployments to release new ve
 products:
   - workers
 ---
-
 import { DashButton } from "~/components";
 
 Versions track changes to your Worker. Deployments configure how those changes are deployed to your traffic.
@@ -108,3 +107,4 @@ Refer to [Migrate from Service Workers to ES modules](/workers/reference/migrate
 ### Durable Object migrations
 
 Uploading a version with [Durable Object migrations](/durable-objects/reference/durable-objects-migrations/) is not supported. Use [`wrangler deploy`](/workers/wrangler/commands/workers/#deploy) if you are applying a [Durable Object migration](/durable-objects/reference/durable-objects-migrations/).
+
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
index 49bb0247b41f32f..6e0adad52574968 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/version-overrides.mdx
@@ -65,9 +65,9 @@ If you forward the original request object, the override header carries through
 ```js
 // The override header from the inbound request is forwarded to the downstream Worker.
 export default {
-	async fetch(request, env) {
-		return env.MY_SERVICE.fetch(request);
-	},
+  async fetch(request, env) {
+    return env.MY_SERVICE.fetch(request);
+  },
 };
 ```
 
@@ -76,15 +76,15 @@ Alternatively, you can set an override header explicitly:
 ```js
 // Replace the version ID with the target version from `wrangler versions list`.
 export default {
-	async fetch(request, env) {
-		const response = await env.MY_SERVICE.fetch("https://example.com/", {
-			headers: {
-				"Cloudflare-Workers-Version-Overrides":
-					'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
-			},
-		});
-		return response;
-	},
+  async fetch(request, env) {
+    const response = await env.MY_SERVICE.fetch("https://example.com/", {
+      headers: {
+        "Cloudflare-Workers-Version-Overrides":
+          'my-downstream-worker="dc8dcd28-271b-4367-9840-6c244f84cb40"',
+      },
+    });
+    return response;
+  },
 };
 ```
 
diff --git a/src/content/docs/workers/configuration/workers-with-page-rules.mdx b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
index b50db0cc22a9f9c..f165f162646c204 100644
--- a/src/content/docs/workers/configuration/workers-with-page-rules.mdx
+++ b/src/content/docs/workers/configuration/workers-with-page-rules.mdx
@@ -32,39 +32,43 @@ If you are experiencing Page Rule errors when running Workers, contact your Clou
 
 The following Page Rules may not work as expected when an incoming request is matched to a Worker route:
 
-- Always Online
-- [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
-- [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
-- [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
-- [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
-- [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
-- [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
-- Disable Apps
-- [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
-- [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
-- [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
-- [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
-- Host Header Override
-- [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
-- [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
-- [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
-- [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
-- [SSL](/workers/configuration/workers-with-page-rules/#ssl)
+* Always Online
+* [Always Use HTTPS](/workers/configuration/workers-with-page-rules/#always-use-https)
+* [Automatic HTTPS Rewrites](/workers/configuration/workers-with-page-rules/#automatic-https-rewrites)
+* [Browser Cache TTL](/workers/configuration/workers-with-page-rules/#browser-cache-ttl)
+* [Browser Integrity Check](/workers/configuration/workers-with-page-rules/#browser-integrity-check)
+* [Cache Deception Armor](/workers/configuration/workers-with-page-rules/#cache-deception-armor)
+* [Cache Level](/workers/configuration/workers-with-page-rules/#cache-level)
+* Disable Apps
+* [Disable Zaraz](/workers/configuration/workers-with-page-rules/#disable-zaraz)
+* [Edge Cache TTL](/workers/configuration/workers-with-page-rules/#edge-cache-ttl)
+* [Email Obfuscation](/workers/configuration/workers-with-page-rules/#email-obfuscation)
+* [Forwarding URL](/workers/configuration/workers-with-page-rules/#forwarding-url)
+* Host Header Override
+* [IP Geolocation Header](/workers/configuration/workers-with-page-rules/#ip-geolocation-header)
+* [Origin Cache Control](/workers/configuration/workers-with-page-rules/#origin-cache-control)
+* [Rocket Loader](/workers/configuration/workers-with-page-rules/#rocket-loader)
+* [Security Level](/workers/configuration/workers-with-page-rules/#security-level)
+* [SSL](/workers/configuration/workers-with-page-rules/#ssl)
 
 This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.
 
 :::caution[Testing]
 
+
 Due to ongoing changes to the Workers runtime, detailed documentation on how these rules will be affected are updated following testing.
 
+
 :::
 
 To learn what these Page Rules do, refer to [Page Rules](/rules/page-rules/).
 
 :::note[Same zone versus other zone]
 
+
 A same zone subrequest is a request the Worker makes to an orange-clouded hostname in the same zone the Worker runs on. Depending on your DNS configuration, any request that falls outside that definition may be considered an other zone request by the Cloudflare network.
 
+
 :::
 
 ### Always Use HTTPS
@@ -133,11 +137,11 @@ A same zone subrequest is a request the Worker makes to an orange-clouded hostna
 
 ### Email Obfuscation
 
-| Source | Target     | Behavior       |
-| ------ | ---------- | -------------- |
-| Client | Worker     | Rule Ignored   |
-| Worker | Same Zone  | Rule Respected |
-| Worker | Other Zone | Rule Ignored   |
+| Source     | Target     | Behavior       |
+| -------------------------|------------|------------|
+| Client     | Worker     | Rule Ignored   |
+| Worker     | Same Zone  | Rule Respected |
+| Worker     | Other Zone | Rule Ignored   |
 
 ### Forwarding URL
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
index 39d7ac436e98f44..ddd98b108387e07 100644
--- a/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/supabase.mdx
@@ -12,9 +12,9 @@ import { Render, PackageManagers, Tabs, TabItem } from "~/components";
 
 :::note
 
-The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client.
+The Supabase client (`@supabase/supabase-js`) provides access to Supabase's various features, including database access. If you need access to all of the Supabase client functionality, use the Supabase client. 
 
-If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/).
+If you want to connect directly to the Supabase Postgres database, connect using [Hyperdrive](/hyperdrive). Hyperdrive can provide lower latencies because it performs the database connection setup and connection pooling across Cloudflare's network. Hyperdrive supports native database drivers, libraries, and ORMs, and is included in all [Workers plans](/hyperdrive/platform/pricing/). Learn more about Hyperdrive in [How Hyperdrive Works](/hyperdrive/concepts/how-hyperdrive-works/). 
 
 :::
 
diff --git a/src/content/docs/workers/databases/third-party-integrations/turso.mdx b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
index a144bb3ba616abd..8467e1c8801cf6a 100644
--- a/src/content/docs/workers/databases/third-party-integrations/turso.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/turso.mdx
@@ -92,7 +92,7 @@ To set up an integration with Turso:
    ```sh
    # Get your database URL
    turso db show my-db --url
-
+   
    # Create an authentication token
    turso db tokens create my-db
    ```
@@ -103,8 +103,8 @@ To set up an integration with Turso:
    # Add the database URL as a secret
    npx wrangler secret put TURSO_URL
    # When prompted, paste your database URL
-
-   # Add the authentication token as a secret
+   
+   # Add the authentication token as a secret  
    npx wrangler secret put TURSO_AUTH_TOKEN
    # When prompted, paste your authentication token
    ```
diff --git a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
index e34c59345e8275b..ebdc513a162cfd2 100644
--- a/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/upstash.mdx
@@ -17,6 +17,7 @@ To set up an integration with Upstash:
 1. You need an existing Upstash database to connect to. [Create an Upstash database](https://docs.upstash.com/redis#create-a-database) or [load data from an existing database to Upstash](https://docs.upstash.com/redis/howto/connectclient).
 
 2. Insert some data to your Upstash database. You can add data to your Upstash database in two ways:
+
    - Use the CLI directly from your Upstash console.
    - Alternatively, install [redis-cli](https://redis.io/docs/getting-started/installation/) locally and run the following commands.
 
@@ -52,7 +53,7 @@ To set up an integration with Upstash:
    # Add the Upstash Redis URL as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_URL
    # When prompted, paste your Upstash Redis REST URL
-
+   
    # Add the Upstash Redis token as a secret
    npx wrangler secret put UPSTASH_REDIS_REST_TOKEN
    # When prompted, paste your Upstash Redis REST token
diff --git a/src/content/docs/workers/databases/third-party-integrations/xata.mdx b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
index a7bcec8e02894d4..31cf393a9843646 100644
--- a/src/content/docs/workers/databases/third-party-integrations/xata.mdx
+++ b/src/content/docs/workers/databases/third-party-integrations/xata.mdx
@@ -10,6 +10,7 @@ import { Render, TabItem, Tabs } from "~/components";
 
 [Xata](https://xata.io) is a PostgreSQL database platform designed to help developers operate and scale databases with enhanced productivity and performance. Xata provides features like instant copy-on-write database branches, zero-downtime schema changes, data anonymization, AI-powered performance monitoring, and BYOC.
 
+
 :::note
 
 You can connect to Xata using [Hyperdrive](/hyperdrive), which provides connection pooling and reduces the amount of round trips required to create a secure connection from Workers to your database.
diff --git a/src/content/docs/workers/development-testing/multi-workers.mdx b/src/content/docs/workers/development-testing/multi-workers.mdx
index c90270083c2c91e..42e37c1197aff58 100644
--- a/src/content/docs/workers/development-testing/multi-workers.mdx
+++ b/src/content/docs/workers/development-testing/multi-workers.mdx
@@ -22,11 +22,11 @@ We recommend this approach as the default for most development workflows as it e
 You can run multiple Workers in a single dev command by passing multiple configuration files to your dev server:
 
 **Using Wrangler**
-
+   
 <PackageManagers
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./app/wrangler.jsonc -c ./api/wrangler.jsonc"
 />
 
 The first config (`./app/wrangler.jsonc`) is treated as the primary Worker, exposed at `http://localhost:8787`. Additional configs (e.g. `./api/wrangler.jsonc`) run as auxiliary Workers, available via service bindings or tail consumers from the primary Worker.
@@ -40,16 +40,16 @@ import { defineConfig } from "vite";
 import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
-	plugins: [
-		cloudflare({
-			configPath: "./app/wrangler.jsonc",
-			auxiliaryWorkers: [
-				{
-					configPath: "./api/wrangler.jsonc",
-				},
-			],
-		}),
-	],
+  plugins: [
+    cloudflare({
+      configPath: "./app/wrangler.jsonc",
+      auxiliaryWorkers: [
+        {
+          configPath: "./api/wrangler.jsonc",
+        },
+      ],
+    }),
+  ],
 });
 ```
 
@@ -68,17 +68,17 @@ Then run:
 You can also run each Worker in separate dev commands, each with its own terminal and configuration.
 
 <PackageManagers
-	comment="Terminal 1"
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./app/wrangler.jsonc"
+  comment="Terminal 1"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./app/wrangler.jsonc"
 />
 
 <PackageManagers
-	comment="Terminal 2"
-	type="exec"
-	pkg="wrangler"
-	args="dev -c ./api/wrangler.jsonc"
+  comment="Terminal 2"
+  type="exec"
+  pkg="wrangler"
+  args="dev -c ./api/wrangler.jsonc"
 />
 
 These Workers run in different dev commands but can still communicate with each other via service bindings or tail consumers **regardless of whether they are started with `wrangler dev` or `vite dev`**.
diff --git a/src/content/docs/workers/development-testing/testing.mdx b/src/content/docs/workers/development-testing/testing.mdx
index c5a0a61aa1c1e8c..d085cb4f503f58c 100644
--- a/src/content/docs/workers/development-testing/testing.mdx
+++ b/src/content/docs/workers/development-testing/testing.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 7
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/development-testing/vite-plugin.mdx b/src/content/docs/workers/development-testing/vite-plugin.mdx
index 60632a1db291f01..f11a1758026f45d 100644
--- a/src/content/docs/workers/development-testing/vite-plugin.mdx
+++ b/src/content/docs/workers/development-testing/vite-plugin.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 1
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx
index e61fa08d45b3e14..1a033e8825cce5d 100644
--- a/src/content/docs/workers/examples/103-early-hints.mdx
+++ b/src/content/docs/workers/examples/103-early-hints.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Allow a client to request static assets while waiting for the HTML response.
 tags:
   - Middleware
@@ -15,7 +16,6 @@ reviewed: 2022-08-12
 products:
   - workers
 ---
-
 import { DashButton, Steps, TabItem, Tabs } from "~/components";
 
 If you want to get started quickly, click on the button below.
diff --git a/src/content/docs/workers/examples/ab-testing.mdx b/src/content/docs/workers/examples/ab-testing.mdx
index bf57cc1256414cd..28b72e57b042734 100644
--- a/src/content/docs/workers/examples/ab-testing.mdx
+++ b/src/content/docs/workers/examples/ab-testing.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set up an A/B test by controlling what response is served based on
   cookies. This version supports passing the request through to test and control
   on the origin, bypassing random assignment.
diff --git a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
index 79830e09a3e34f0..3947c1f80350fb6 100644
--- a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
+++ b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Access custom Cloudflare properties and control how Cloudflare features
   are applied to every request.
 tags:
diff --git a/src/content/docs/workers/examples/aggregate-requests.mdx b/src/content/docs/workers/examples/aggregate-requests.mdx
index 05f04def29f8b17..4666d5fd1baf002 100644
--- a/src/content/docs/workers/examples/aggregate-requests.mdx
+++ b/src/content/docs/workers/examples/aggregate-requests.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send two GET request to two urls and aggregates the responses into one
   response.
 tags:
diff --git a/src/content/docs/workers/examples/alter-headers.mdx b/src/content/docs/workers/examples/alter-headers.mdx
index 129e244ab485ac0..cec4c62a5d08212 100644
--- a/src/content/docs/workers/examples/alter-headers.mdx
+++ b/src/content/docs/workers/examples/alter-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Example of how to add, change, or delete headers sent in a request or
   returned in a response.
 tags:
diff --git a/src/content/docs/workers/examples/auth-with-headers.mdx b/src/content/docs/workers/examples/auth-with-headers.mdx
index cf1ff87eee06ec7..4903f1f12598379 100644
--- a/src/content/docs/workers/examples/auth-with-headers.mdx
+++ b/src/content/docs/workers/examples/auth-with-headers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Allow or deny a request based on a known pre-shared key in a header.
   This is not meant to replace the WebCrypto API.
 tags:
diff --git a/src/content/docs/workers/examples/basic-auth.mdx b/src/content/docs/workers/examples/basic-auth.mdx
index c4dbb71353b6c7f..84e8be086b49095 100644
--- a/src/content/docs/workers/examples/basic-auth.mdx
+++ b/src/content/docs/workers/examples/basic-auth.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Shows how to restrict access using the HTTP Basic schema.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/block-on-tls.mdx b/src/content/docs/workers/examples/block-on-tls.mdx
index c6edd048d5fafdc..43831741eb75193 100644
--- a/src/content/docs/workers/examples/block-on-tls.mdx
+++ b/src/content/docs/workers/examples/block-on-tls.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Inspects the incoming request's TLS version and blocks if under TLSv1.2.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/bulk-origin-proxy.mdx b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
index 943e7b6c4e8fea0..6760d74eafdc8fb 100644
--- a/src/content/docs/workers/examples/bulk-origin-proxy.mdx
+++ b/src/content/docs/workers/examples/bulk-origin-proxy.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Resolve requests to your domain to a set of proxy third-party origin URLs.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/bulk-redirects.mdx b/src/content/docs/workers/examples/bulk-redirects.mdx
index f6c5d881a4b4ef6..623d39afaf43402 100644
--- a/src/content/docs/workers/examples/bulk-redirects.mdx
+++ b/src/content/docs/workers/examples/bulk-redirects.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Redirect requests to certain URLs based on a mapped object to the
   request's URL.
 tags:
diff --git a/src/content/docs/workers/examples/cache-api.mdx b/src/content/docs/workers/examples/cache-api.mdx
index 34e592721b3174c..3bb0c1b6578703f 100644
--- a/src/content/docs/workers/examples/cache-api.mdx
+++ b/src/content/docs/workers/examples/cache-api.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the Cache API to store responses in Cloudflare's cache.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-post-request.mdx b/src/content/docs/workers/examples/cache-post-request.mdx
index 3c7f7548bf22aef..2fb05d6f62ead04 100644
--- a/src/content/docs/workers/examples/cache-post-request.mdx
+++ b/src/content/docs/workers/examples/cache-post-request.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Cache POST requests using the Cache API.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/cache-tags.mdx b/src/content/docs/workers/examples/cache-tags.mdx
index 248effca15f46bc..0a85395341521d5 100644
--- a/src/content/docs/workers/examples/cache-tags.mdx
+++ b/src/content/docs/workers/examples/cache-tags.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send Additional Cache Tags using Workers
 tags:
   - Caching
diff --git a/src/content/docs/workers/examples/cache-using-fetch.mdx b/src/content/docs/workers/examples/cache-using-fetch.mdx
index b3f9f1cd60b870c..2270d27f236d16a 100644
--- a/src/content/docs/workers/examples/cache-using-fetch.mdx
+++ b/src/content/docs/workers/examples/cache-using-fetch.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Determine how to cache a resource by setting TTLs, custom cache keys,
   and cache headers in a fetch request.
 tags:
@@ -563,6 +564,6 @@ When `no-cache` is supplied the cache is forced to revalidate the currently cach
 origin.
 
 ```js
-fetch(request, { cache: "no-store" });
-fetch(request, { cache: "no-cache" });
+fetch(request, { cache: 'no-store'});
+fetch(request, { cache: 'no-cache'});
 ```
diff --git a/src/content/docs/workers/examples/conditional-response.mdx b/src/content/docs/workers/examples/conditional-response.mdx
index 0772d216c56f507..f6b109c19de1a2f 100644
--- a/src/content/docs/workers/examples/conditional-response.mdx
+++ b/src/content/docs/workers/examples/conditional-response.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Return a response based on the incoming request's URL, HTTP method,
   User Agent, IP address, ASN or device type.
 tags:
diff --git a/src/content/docs/workers/examples/cors-header-proxy.mdx b/src/content/docs/workers/examples/cors-header-proxy.mdx
index c6eacdd133464f7..8335f92850f2e62 100644
--- a/src/content/docs/workers/examples/cors-header-proxy.mdx
+++ b/src/content/docs/workers/examples/cors-header-proxy.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Add the necessary CORS headers to a third party API response.
 tags:
   - Security
@@ -715,3 +716,4 @@ return response.json()
 }
 ```
 </TabItem> </Tabs>
+
diff --git a/src/content/docs/workers/examples/country-code-redirect.mdx b/src/content/docs/workers/examples/country-code-redirect.mdx
index 19a10589a4fb622..ca3af654f791168 100644
--- a/src/content/docs/workers/examples/country-code-redirect.mdx
+++ b/src/content/docs/workers/examples/country-code-redirect.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Redirect a response based on the country code in the header of a visitor.
 tags:
   - Redirects
diff --git a/src/content/docs/workers/examples/data-loss-prevention.mdx b/src/content/docs/workers/examples/data-loss-prevention.mdx
index ce5c655a6d71251..8483ccab86121e9 100644
--- a/src/content/docs/workers/examples/data-loss-prevention.mdx
+++ b/src/content/docs/workers/examples/data-loss-prevention.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Protect sensitive data to prevent data loss, and send alerts to a
   webhooks server in the event of a data breach.
 tags:
diff --git a/src/content/docs/workers/examples/debugging-logs.mdx b/src/content/docs/workers/examples/debugging-logs.mdx
index 33128a13520e036..ac22a6f78f37918 100644
--- a/src/content/docs/workers/examples/debugging-logs.mdx
+++ b/src/content/docs/workers/examples/debugging-logs.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send debugging information in an errored response to a logging service.
 tags:
   - Debugging
diff --git a/src/content/docs/workers/examples/extract-cookie-value.mdx b/src/content/docs/workers/examples/extract-cookie-value.mdx
index 2d1e1e7afa6b59d..26eeba1adfb4182 100644
--- a/src/content/docs/workers/examples/extract-cookie-value.mdx
+++ b/src/content/docs/workers/examples/extract-cookie-value.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Given the cookie name, get the value of a cookie. You can also use
   cookies for A/B testing.
 tags:
diff --git a/src/content/docs/workers/examples/fetch-json.mdx b/src/content/docs/workers/examples/fetch-json.mdx
index ea574ed80ffa5a5..e803fee74e049cb 100644
--- a/src/content/docs/workers/examples/fetch-json.mdx
+++ b/src/content/docs/workers/examples/fetch-json.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send a GET request and read in JSON from the response. Use to fetch
   external data.
 pcx_content_type: example
diff --git a/src/content/docs/workers/examples/geolocation-app-weather.mdx b/src/content/docs/workers/examples/geolocation-app-weather.mdx
index 903b1906ea7da65..da915f46349f806 100644
--- a/src/content/docs/workers/examples/geolocation-app-weather.mdx
+++ b/src/content/docs/workers/examples/geolocation-app-weather.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Fetch weather data from an API using the user's geolocation data.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-custom-styling.mdx b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
index 9010b98d7034c34..9e5888fbd2a51de 100644
--- a/src/content/docs/workers/examples/geolocation-custom-styling.mdx
+++ b/src/content/docs/workers/examples/geolocation-custom-styling.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Personalize website styling based on localized user time.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/geolocation-hello-world.mdx b/src/content/docs/workers/examples/geolocation-hello-world.mdx
index 9e9f01f835ea0c3..ca32cc280b07052 100644
--- a/src/content/docs/workers/examples/geolocation-hello-world.mdx
+++ b/src/content/docs/workers/examples/geolocation-hello-world.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Get all geolocation data fields and display them in HTML.
 tags:
   - Geolocation
diff --git a/src/content/docs/workers/examples/hot-link-protection.mdx b/src/content/docs/workers/examples/hot-link-protection.mdx
index b0773924fca66d4..4a7d1a997e16191 100644
--- a/src/content/docs/workers/examples/hot-link-protection.mdx
+++ b/src/content/docs/workers/examples/hot-link-protection.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Block other websites from linking to your content. This is useful for
   protecting images.
 tags:
diff --git a/src/content/docs/workers/examples/modify-request-property.mdx b/src/content/docs/workers/examples/modify-request-property.mdx
index fe5199d30781dab..7b0dff4cea7b789 100644
--- a/src/content/docs/workers/examples/modify-request-property.mdx
+++ b/src/content/docs/workers/examples/modify-request-property.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Create a modified request with edited properties based off of an
   incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/modify-response.mdx b/src/content/docs/workers/examples/modify-response.mdx
index 75b8731aae95371..6638180c480b268 100644
--- a/src/content/docs/workers/examples/modify-response.mdx
+++ b/src/content/docs/workers/examples/modify-response.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Fetch and modify response properties which are immutable by creating a
   copy first.
 tags:
diff --git a/src/content/docs/workers/examples/multiple-cron-triggers.mdx b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
index 70ffa53d857fde0..52d717075365808 100644
--- a/src/content/docs/workers/examples/multiple-cron-triggers.mdx
+++ b/src/content/docs/workers/examples/multiple-cron-triggers.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Set multiple Cron Triggers on three different schedules.
 tags:
   - Middleware
diff --git a/src/content/docs/workers/examples/openai-sdk-streaming.mdx b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
index 4a56649266440a9..20dc1d448fe2b7e 100644
--- a/src/content/docs/workers/examples/openai-sdk-streaming.mdx
+++ b/src/content/docs/workers/examples/openai-sdk-streaming.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the OpenAI v4 SDK to stream responses from OpenAI.
 tags:
   - AI
diff --git a/src/content/docs/workers/examples/post-json.mdx b/src/content/docs/workers/examples/post-json.mdx
index c14f7e3a5c83c6a..6b01ab31537684d 100644
--- a/src/content/docs/workers/examples/post-json.mdx
+++ b/src/content/docs/workers/examples/post-json.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send a POST request with JSON data. Use to share data with external servers.
 tags:
   - JSON
diff --git a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
index 0204a2732ca6e07..c18930609c886b2 100644
--- a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
+++ b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Protect against timing attacks by safely comparing values using
   `timingSafeEqual`.
 tags:
diff --git a/src/content/docs/workers/examples/read-post.mdx b/src/content/docs/workers/examples/read-post.mdx
index 6ec581eff46a60c..c805138d150cb88 100644
--- a/src/content/docs/workers/examples/read-post.mdx
+++ b/src/content/docs/workers/examples/read-post.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Serve an HTML form, then read POST requests. Use also to read JSON or
   POST data from an incoming request.
 tags:
diff --git a/src/content/docs/workers/examples/return-html.mdx b/src/content/docs/workers/examples/return-html.mdx
index 065b623759cdcc6..3cd587b30a97fae 100644
--- a/src/content/docs/workers/examples/return-html.mdx
+++ b/src/content/docs/workers/examples/return-html.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Deliver an HTML page from an HTML string directly inside the Worker script.
 demo: https://returning-html.workers-sites-examples.workers.dev
 tags:
diff --git a/src/content/docs/workers/examples/rewrite-links.mdx b/src/content/docs/workers/examples/rewrite-links.mdx
index e20265b28ed4a5b..cd10efbb5239087 100644
--- a/src/content/docs/workers/examples/rewrite-links.mdx
+++ b/src/content/docs/workers/examples/rewrite-links.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Rewrite URL links in HTML using the HTMLRewriter. This is useful for
   JAMstack websites.
 tags:
diff --git a/src/content/docs/workers/examples/signing-requests.mdx b/src/content/docs/workers/examples/signing-requests.mdx
index 7d98b2922d35a5f..f1e685251d8fc52 100644
--- a/src/content/docs/workers/examples/signing-requests.mdx
+++ b/src/content/docs/workers/examples/signing-requests.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Verify a signed request using the HMAC and SHA-256 algorithms or return a 403.
 tags:
   - Security
diff --git a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
index 6f97419c267b833..d20ca8a4a5aa54b 100644
--- a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
+++ b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Inject [Turnstile](/turnstile/) implicitly into HTML elements using the
   HTMLRewriter runtime API.
 tags:
diff --git a/src/content/docs/workers/examples/websockets.mdx b/src/content/docs/workers/examples/websockets.mdx
index 84e5dc0f892523c..cd919a2ecbdd2e4 100644
--- a/src/content/docs/workers/examples/websockets.mdx
+++ b/src/content/docs/workers/examples/websockets.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Use the WebSockets API to communicate in real time with your Cloudflare Workers.
 tags:
   - WebSockets
@@ -81,9 +82,9 @@ async fn fetch(req: HttpRequest, _env: Env, _ctx: Context) -> Result<worker::Res
 ```
 
 </TabItem> </Tabs>
-
 After you have appropriately checked for the `Upgrade` header, you can create a new instance of `WebSocketPair`, which contains server and client WebSockets. One of these WebSockets should be handled by the Workers function and the other should be returned as part of a `Response` with the [`101` status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/101), indicating the request is switching protocols:
 
+
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
@@ -135,6 +136,7 @@ The `WebSocketPair` constructor returns an Object, with the `0` and `1` keys eac
 
 In order to begin communicating with the `client` WebSocket in your Worker, call `accept` on the `server` WebSocket. This will tell the Workers runtime that it should listen for WebSocket data and keep the connection open with your `client` WebSocket:
 
+
 <Tabs syncKey="workersExamples"> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
diff --git a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
index bf7151b9c2d494c..8311463a2303071 100644
--- a/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
+++ b/src/content/docs/workers/framework-guides/ai-and-agents/index.mdx
@@ -10,14 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers with AI & agent
-	frameworks.
+Create full-stack applications deployed to Cloudflare Workers with AI & agent frameworks.
 </Description>
 
-<DirectoryListing
-	folder="workers/framework-guides/ai-and-agents"
-	maxDepth={2}
-/>
+<DirectoryListing folder="workers/framework-guides/ai-and-agents" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/apis/index.mdx b/src/content/docs/workers/framework-guides/apis/index.mdx
index e3e0997d8023893..7c65dfc89d5ab12 100644
--- a/src/content/docs/workers/framework-guides/apis/index.mdx
+++ b/src/content/docs/workers/framework-guides/apis/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers using APIs.
+Create full-stack applications deployed to Cloudflare Workers using APIs.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/apis" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/index.mdx b/src/content/docs/workers/framework-guides/index.mdx
index 7c7d795d9e3aa13..e7fd39e00a6aecf 100644
--- a/src/content/docs/workers/framework-guides/index.mdx
+++ b/src/content/docs/workers/framework-guides/index.mdx
@@ -11,10 +11,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack applications deployed to Cloudflare Workers.
+Create full-stack applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides" maxDepth={4} />
+<DirectoryListing folder="workers/framework-guides" maxDepth={4}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
index f7fc7a59d1511ee..03a98d1fc26641a 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/expo.mdx
@@ -5,4 +5,4 @@ pcx_content_type: navigation
 external_link: https://docs.expo.dev/eas/hosting/reference/worker-runtime/
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
index be6cede9f5c8287..6cc8183f77ec8c3 100644
--- a/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/mobile-apps/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack mobile applications deployed to Cloudflare Workers.
+Create full-stack mobile applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/mobile-apps" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/astro.mdx b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
index b90f2936598dcff..a1e4aaf3e9ea768 100644
--- a/src/content/docs/workers/framework-guides/web-apps/astro.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/astro.mdx
@@ -87,27 +87,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Astro"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: "dist/_worker.js/index.js",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: ./dist, binding: ASSETS",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: "dist/_worker.js/index.js" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: ./dist, binding: ASSETS" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{
-			label: "adapter",
-			file: "astro.config.mjs",
-			value: "@astrojs/cloudflare",
-		},
+		{ label: "adapter", file: "astro.config.mjs", value: "@astrojs/cloudflare" },
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/index.mdx b/src/content/docs/workers/framework-guides/web-apps/index.mdx
index 87009d6003a290e..cb372caec51f847 100644
--- a/src/content/docs/workers/framework-guides/web-apps/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/index.mdx
@@ -10,10 +10,13 @@ products:
   - workers
 ---
 
-import { Description, DirectoryListing } from "~/components";
+import {
+	Description,
+	DirectoryListing
+} from "~/components";
 
 <Description>
-	Create full-stack web applications deployed to Cloudflare Workers.
+Create full-stack web applications deployed to Cloudflare Workers.
 </Description>
 
-<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2} />
+<DirectoryListing folder="workers/framework-guides/web-apps" maxDepth={2}/>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
index 0cd619c91b471d7..db924f15079e094 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/analog.mdx
@@ -24,21 +24,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Analog"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
index c12d9db29798dfc..8dbf8a2eccef565 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/angular.mdx
@@ -29,11 +29,7 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Angular"
 	configs={[
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/browser",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/browser" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
index b098122622c408a..6f0ab43afa2d870 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/docusaurus.mdx
@@ -75,6 +75,7 @@ Docusaurus is designed to be easy to use and customizable, making it a popular c
 
 If your Docusaurus project is entirely pre-rendered (which it usually is), follow these steps:
 
+
 <Steps>
 1.  **Add a Wrangler configuration file.**
 
@@ -115,3 +116,4 @@ If your Docusaurus project is entirely pre-rendered (which it usually is), follo
 Bindings are a way to connect your Docusaurus project to other Cloudflare services, enabling you to store and retrieve data within your application.
 
 <Render file="frameworks-bindings" product="workers" />
+
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
index 8373da96cbbdb96..5b69a489c1fe3d0 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/hono.mdx
@@ -33,6 +33,8 @@ import {
 
 [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create/deploy-to-workers&repository=https://github.com/cloudflare/templates/tree/main/vite-react-template)
 
+
+
 ## What is Hono?
 
 [Hono](https://hono.dev/) is an ultra-fast, lightweight framework for building web applications, and works fantastically with Cloudflare Workers.
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
index 2c8eb7ea43bc8ed..eb6f1cd2cdff605 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/index.mdx
@@ -8,4 +8,4 @@ sidebar:
     hideIndex: true
 products:
   - workers
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
index bf3f6b53620a121..775117671401c50 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/nuxt.mdx
@@ -29,21 +29,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Nuxt"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "preset", file: "nuxt.config.ts", value: "cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
index 0b4849166b7c4fc..520223f8048b1ce 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/solid.mdx
@@ -33,21 +33,9 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="Solid Start"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".output/server/index.mjs",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .output/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".output/server/index.mjs" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .output/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
diff --git a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
index 6d8e6bedc97a74c..11a06ef6dfe2634 100644
--- a/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/more-web-frameworks/waku.mdx
@@ -30,16 +30,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Waku"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/worker.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/public",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/public" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -97,4 +89,4 @@ You can serve static assets in your Waku application by adding them to the `./pu
 
 During the build process, Waku copies `.js`, `.css`, `.html`, and `.txt` files from this directory into the final assets output. `.txt` files are used for storing data used by Server Components that are rendered at build time.
 
-<Render file="workers-assets-routing-summary" product="workers" />
+<Render file="workers-assets-routing-summary" product="workers" />
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
index 59f1211f42978e5..7218158dad2f5ea 100644
--- a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx
@@ -29,6 +29,8 @@ import {
 
 This is a simple getting started guide. For detailed documentation on how to use the Cloudflare OpenNext adapter, visit the [OpenNext website](https://opennext.js.org/cloudflare).
 
+
+
 ## What is Next.js?
 
 [Next.js](https://nextjs.org/) is a [React](https://react.dev/) framework for building full stack applications.
@@ -41,23 +43,23 @@ You can deploy your Next.js app to Cloudflare Workers using the OpenNext adapter
 
 Most Next.js features are supported by the Cloudflare OpenNext adapter:
 
-| Feature                               | Cloudflare adapter   | Notes                                                       |
-| ------------------------------------- | -------------------- | ----------------------------------------------------------- |
-| App Router                            | 🟢 supported         |                                                             |
-| Pages Router                          | 🟢 supported         |                                                             |
-| Route Handlers                        | 🟢 supported         |                                                             |
-| React Server Components               | 🟢 supported         |                                                             |
-| Static Site Generation (SSG)          | 🟢 supported         |                                                             |
-| Server-Side Rendering (SSR)           | 🟢 supported         |                                                             |
-| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                             |
-| Server Actions                        | 🟢 supported         |                                                             |
-| Response streaming                    | 🟢 supported         |                                                             |
-| asynchronous work with `next/after`   | 🟢 supported         |                                                             |
-| Middleware                            | 🟢 supported         |                                                             |
-| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/)                 |
-| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                              |
-| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js               |
-| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported |
+| Feature                               | Cloudflare adapter   | Notes                                                                        |
+| ------------------------------------- | -------------------- | ---------------------------------------------------------------------------- |
+| App Router                            | 🟢 supported         |                                                                              |
+| Pages Router                          | 🟢 supported         |                                                                              |
+| Route Handlers                        | 🟢 supported         |                                                                              |
+| React Server Components               | 🟢 supported         |                                                                              |
+| Static Site Generation (SSG)          | 🟢 supported         |                                                                              |
+| Server-Side Rendering (SSR)           | 🟢 supported         |                                                                              |
+| Incremental Static Regeneration (ISR) | 🟢 supported         |                                                                              |
+| Server Actions                        | 🟢 supported         |                                                                              |
+| Response streaming                    | 🟢 supported         |                                                                              |
+| asynchronous work with `next/after`   | 🟢 supported         |                                                                              |
+| Middleware                            | 🟢 supported         |                                                                              |
+| Image optimization                    | 🟢 supported         | Supported via [Cloudflare Images](/images/) |
+| Partial Prerendering (PPR)            | 🟢 supported         | PPR is experimental in Next.js                                               |
+| Composable Caching ('use cache')      | 🟢 supported         | Composable Caching is experimental in Next.js                                |
+| Node.js in Middleware                 | ⚪ not yet supported | Node.js middleware introduced in 15.2 are not yet supported                  |
 
 ## Deploy a new Next.js project on Workers
 
@@ -131,16 +133,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Next.js"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: ".open-next/worker.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .open-next/assets",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .open-next/assets" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 		{ label: "adapter", file: "package.json", value: "@opennextjs/cloudflare" },
 	]}
diff --git a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
index a69d19964c7156c..226dd6d9fc4c19e 100644
--- a/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/redwoodsdk.mdx
@@ -96,4 +96,4 @@ RedwoodSDK is a framework for building server-side web applications on Cloudflar
 
 	The first time you run the command it might fail and ask you to create a workers.dev subdomain. Go to the dashboard and open the Workers menu. Opening the Workers landing page for the first time will create a workers.dev subdomain automatically.
 
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
index 0c4e1f8d44d8645..16233bdaac9a5ea 100644
--- a/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx
@@ -31,27 +31,11 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 <AutoconfigDiagram
 	framework="SvelteKit"
 	configs={[
-		{
-			label: "main",
-			file: "wrangler.jsonc",
-			value: ".svelte-kit/cloudflare/_worker.js",
-		},
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: .svelte-kit/cloudflare",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "main", file: "wrangler.jsonc", value: ".svelte-kit/cloudflare/_worker.js" },
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: .svelte-kit/cloudflare" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
-		{
-			label: "adapter",
-			file: "svelte.config.js",
-			value: "@sveltejs/adapter-cloudflare",
-		},
+		{ label: "adapter", file: "svelte.config.js", value: "@sveltejs/adapter-cloudflare" },
 	]}
 />
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vike.mdx b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
index 6218d56b5d4a81a..27dd268608448ee 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vike.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vike.mdx
@@ -10,12 +10,13 @@ products:
 ---
 
 import { AutoconfigDiagram, Steps, PackageManagers } from "~/components";
-import { Tabs, TabItem } from "@astrojs/starlight/components";
+import { Tabs, TabItem } from '@astrojs/starlight/components';
 
 You can deploy your [Vike](https://vike.dev) app to Cloudflare using the Vike extension [`vike-photon`](https://vike.dev/vike-photon).
 
 All app types (SSR/SPA/SSG) are supported.
 
+
 :::tip[Already have a Vike project?]
 Run `wrangler deploy` in a project without a Wrangler configuration file and Wrangler will automatically detect Vike, generate the necessary configuration, and deploy your project.
 
@@ -28,16 +29,8 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 	framework="Vike"
 	configs={[
 		{ label: "main", file: "wrangler.jsonc", value: "dist/server/index.js" },
-		{
-			label: "assets",
-			file: "wrangler.jsonc",
-			value: "directory: dist/client",
-		},
-		{
-			label: "compatibility_flags",
-			file: "wrangler.jsonc",
-			value: "nodejs_compat",
-		},
+		{ label: "assets", file: "wrangler.jsonc", value: "directory: dist/client" },
+		{ label: "compatibility_flags", file: "wrangler.jsonc", value: "nodejs_compat" },
 		{ label: "observability", file: "wrangler.jsonc", value: "enabled: true" },
 	]}
 />
@@ -50,6 +43,7 @@ Learn more about [automatic project configuration](/workers/framework-guides/aut
 
 Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `vike-photon` with `@photonjs/cloudflare`.
 
+
 ## Add to existing app
 
 <Steps>
@@ -98,29 +92,31 @@ Use [vike.dev/new](https://vike.dev/new) to scaffold a new Vike app that uses `v
 To access Cloudflare APIs (such as [D1](/d1/) and [KV](/kv/)), use [bindings](/workers/runtime-apis/bindings/) which are available via the `env` object [imported from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global).
 
 ```ts
-import { env } from "cloudflare:workers";
+import { env } from 'cloudflare:workers'
 // Key-value store
-env.KV.get("my-key");
+env.KV.get('my-key')
 // Environment variable
-env.LOG_LEVEL;
+env.LOG_LEVEL
 // ...
 ```
 
 > Example of using Cloudflare D1:
->
 > <PackageManagers
 > 	type="create"
 > 	pkg="vike@latest"
 > 	args="--react --hono --drizzle --cloudflare"
 > />
-> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an
-> ORM.
+> Or go to [vike.dev/new](https://vike.dev/new) and select `Cloudflare` with an ORM.
 
 ## TypeScript
 
 If you use TypeScript, run [`wrangler types`](/workers/wrangler/commands/general/#types) whenever you change your Cloudflare configuration to update the `worker-configuration.d.ts` file.
 
-<PackageManagers type="exec" pkg="wrangler" args="types" />
+<PackageManagers
+	type="exec"
+	pkg="wrangler"
+	args="types"
+/>
 
 Then commit:
 
diff --git a/src/content/docs/workers/framework-guides/web-apps/vue.mdx b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
index 155e8df3c77be19..e3f18d090e9e901 100644
--- a/src/content/docs/workers/framework-guides/web-apps/vue.mdx
+++ b/src/content/docs/workers/framework-guides/web-apps/vue.mdx
@@ -34,9 +34,9 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
 	args="my-vue-app --framework=vue"
 />
 
-		 <Details header="How is this project set up?">
-    			Below is a simplified file tree of the project.
-    			<FileTree>
+    		 <Details header="How is this project set up?">
+        			Below is a simplified file tree of the project.
+        			<FileTree>
     						- my-vue-app
     							- src/
     									- App.vue
@@ -47,17 +47,17 @@ To use `create-cloudflare` to create a new Vue project with Workers Assets, run
     							- wrangler.jsonc
         			</FileTree>
 
-    			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
-    			In this file:
-    					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
-    					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
-    					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
+        			`wrangler.jsonc` is your [Wrangler configuration file](/workers/wrangler/configuration/).
+        			In this file:
+        					- `main` points to `server/index.ts`. This is your Worker, which is going to act as your backend API.
+        					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
+        					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
+    						`vite.config.ts` is set up to use the [Cloudflare Vite plugin](/workers/vite-plugin/). This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
-						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
-    		</Details>
+    						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
+    						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
+        		</Details>
 
 ## 2. Develop locally with the [Cloudflare Vite plugin](/workers/vite-plugin/)
 
diff --git a/src/content/docs/workers/get-started/dashboard.mdx b/src/content/docs/workers/get-started/dashboard.mdx
index 93f5ddc844d62d9..927871405d844f0 100644
--- a/src/content/docs/workers/get-started/dashboard.mdx
+++ b/src/content/docs/workers/get-started/dashboard.mdx
@@ -29,15 +29,14 @@ To get started with a new Workers application:
 
    <DashButton url="/?to=/:account/workers-and-pages" />
 
-2. Select **Create application**. From here, you can:
-   - Select from the gallery of production-ready templates
-   - Import an existing Git repository on your own account
-   - Let Cloudflare clone and bootstrap a public repository containing a Workers application.
+3. Select **Create application**. From here, you can:
+    * Select from the gallery of production-ready templates
+    * Import an existing Git repository on your own account
+    * Let Cloudflare clone and bootstrap a public repository containing a Workers application.
 3. Once you have connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and select **Deploy**.
 4. Cloudflare will kick off a new build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain.
 
 ## Continue development
-
 Applications started in the dashboard are set up with Git to help kickstart your development workflow. To continue developing on your repository, you can run:
 
 ```bash
@@ -61,8 +60,8 @@ git commit -m "your message"
 git push origin main
 ```
 
-To do more:
 
+To do more:
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.
diff --git a/src/content/docs/workers/get-started/quickstarts.mdx b/src/content/docs/workers/get-started/quickstarts.mdx
index 5b4c0d7dd74919f..c4c9aaa383a02c3 100644
--- a/src/content/docs/workers/get-started/quickstarts.mdx
+++ b/src/content/docs/workers/get-started/quickstarts.mdx
@@ -1,4 +1,5 @@
 ---
+
 pcx_content_type: get-started
 title: Templates
 sidebar:
diff --git a/src/content/docs/workers/languages/javascript/index.mdx b/src/content/docs/workers/languages/javascript/index.mdx
index ad25a7a59321ff9..a2697d4edad3d26 100644
--- a/src/content/docs/workers/languages/javascript/index.mdx
+++ b/src/content/docs/workers/languages/javascript/index.mdx
@@ -8,15 +8,16 @@ products:
   - workers
 ---
 
+
 The Workers platform is designed to be [JavaScript standards compliant](https://ecma-international.org/publications-and-standards/standards/ecma-262/) and web-interoperable, and supports JavaScript standards, as defined by [TC39](https://tc39.es/) (ECMAScript). Wherever possible, it uses web platform APIs, so that code can be reused across client and server, as well as across [WinterCG](https://wintercg.org/) JavaScript runtimes.
 
 Refer to [Runtime APIs](/workers/runtime-apis/) for more information on specific JavaScript APIs available in Workers.
 
 ### Resources
 
-- [Getting Started](/workers/get-started/guide/)
-- [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
-- [TypeScript type definitions](https://github.com/cloudflare/workers-types)
-- [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
-- [Tutorials](/workers/tutorials/)
-- [Examples](/workers/examples/?languages=JavaScript)
+* [Getting Started](/workers/get-started/guide/)
+* [Quickstarts](/workers/get-started/quickstarts/) – More example repos to use as a basis for your projects
+* [TypeScript type definitions](https://github.com/cloudflare/workers-types)
+* [JavaScript and web standard APIs](/workers/runtime-apis/web-standards/)
+* [Tutorials](/workers/tutorials/)
+* [Examples](/workers/examples/?languages=JavaScript)
diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx
index 57b1c75a4621975..d45ef218a482019 100644
--- a/src/content/docs/workers/observability/errors.mdx
+++ b/src/content/docs/workers/observability/errors.mdx
@@ -15,21 +15,22 @@ Review Workers errors and exceptions.
 
 When a Worker running in production has an error that prevents it from returning a response, the client will receive an error page with an error code, defined as follows:
 
-| Error code | Meaning                                                                                                                                                                                                                                                             |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `1101`     | Worker threw a JavaScript exception.                                                                                                                                                                                                                                |
-| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                                                                                                                                               |
-| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                                                                                                                                             |
-| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                                                                                                                                               |
-| `1021`     | Worker has requested a host it cannot access.                                                                                                                                                                                                                       |
-| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                                                                                                                                           |
-| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                                                                                                                                                   |
-| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                                                                                                                                          |
+| Error code | Meaning                                                                                                                                         |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `1101`     | Worker threw a JavaScript exception.                                                                                                            |
+| `1102`     | Worker exceeded [CPU time limit](/workers/platform/limits/#cpu-time).                                                                           |
+| `1103`     | The owner of this worker needs to contact [Cloudflare Support](/support/contacting-cloudflare-support/)                                         |
+| `1019`     | Worker hit [loop limit](#loop-limit).                                                                                                           |
+| `1021`     | Worker has requested a host it cannot access.                                                                                                   |
+| `1022`     | Cloudflare has failed to route the request to the Worker.                                                                                       |
+| `1024`     | Worker cannot make a subrequest to a Cloudflare-owned IP address.                                                                               |
+| `1027`     | Worker exceeded free tier [daily request limit](/workers/platform/limits/#daily-requests).                                                       |
 | `1042`     | Worker tried to fetch from another Worker on the same zone, which is only [supported](/workers/runtime-apis/fetch/) when the [`global_fetch_strictly_public` compatibility flag](/workers/configuration/compatibility-flags/#global-fetch-strictly-public) is used. |
-| `10162`    | Module has an unsupported Content-Type.                                                                                                                                                                                                                             |
+| `10162`    | Module has an unsupported Content-Type.                                                                                                         |
 
 Other `11xx` errors generally indicate a problem with the Workers runtime itself. Refer to the [status page](https://www.cloudflarestatus.com) if you are experiencing an error.
 
+
 ### Loop limit
 
 A Worker cannot call itself or another Worker more than 16 times. In order to prevent infinite loops between Workers, the [`CF-EW-Via`](/fundamentals/reference/http-headers/#cf-ew-via) header's value is an integer that indicates how many invocations are left. Every time a Worker is invoked, the integer will decrement by 1. If the count reaches zero, a [`1019`](#error-pages-generated-by-workers) error is returned.
@@ -190,23 +191,23 @@ If you need to share state across requests, consider using [Durable Objects](/du
 
 These errors occur when a Worker is uploaded or modified.
 
-| Error code | Meaning                                                                                                                     |
-| ---------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `10006`    | Could not parse your Worker's code.                                                                                         |
-| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                   |
-| `10015`    | Account is not entitled to use Workers.                                                                                     |
-| `10016`    | Invalid Worker name.                                                                                                        |
-| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.         |
-| `10026`    | Could not parse request body.                                                                                               |
-| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size).                               |
-| `10035`    | Multiple attempts to modify a resource at the same time                                                                     |
-| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                       |
-| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                    |
-| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                 |
-| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables). |
-| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                       |
-| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                    |
-| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.          |
+| Error code | Meaning                                                                                                                         |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `10006`    | Could not parse your Worker's code.                                                                                             |
+| `10007`    | Worker or [workers.dev subdomain](/workers/configuration/routing/workers-dev/) not found.                                       |
+| `10015`    | Account is not entitled to use Workers.                                                                                         |
+| `10016`    | Invalid Worker name.                                                                                                            |
+| `10021`    | Validation Error. Refer to [Validation Errors](/workers/observability/errors/#validation-errors-10021) for details.             |
+| `10026`    | Could not parse request body.                                                                                                   |
+| `10027`    | The uploaded Worker exceeded the [Worker size limits](/workers/platform/limits/#worker-size). |
+| `10035`    | Multiple attempts to modify a resource at the same time                                                                         |
+| `10037`    | An account has exceeded the number of [Workers allowed](/workers/platform/limits/#number-of-workers).                           |
+| `10052`    | A [binding](/workers/runtime-apis/bindings/) is uploaded without a name.                                                        |
+| `10054`    | A environment variable or secret exceeds the [size limit](/workers/platform/limits/#environment-variables).                     |
+| `10055`    | The number of environment variables or secrets exceeds the [limit/Worker](/workers/platform/limits/#environment-variables).     |
+| `10056`    | [Binding](/workers/runtime-apis/bindings/) not found.                                                                           |
+| `10068`    | The uploaded Worker has no registered [event handlers](/workers/runtime-apis/handlers/).                                        |
+| `10069`    | The uploaded Worker contains [event handlers](/workers/runtime-apis/handlers/) unsupported by the Workers runtime.              |
 
 ### Validation Errors (10021)
 
@@ -235,7 +236,6 @@ Runtime errors will occur within the runtime, do not throw up an error page, and
 ## Identify errors: Workers Metrics
 
 To review whether your application is experiencing any downtime or returning any errors:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
index 105fea21b7e83dc..586b51c9eed17af 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx
@@ -8,11 +8,10 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Axiom is a serverless log analytics platform that helps you store, search, and analyze massive amounts of data. By exporting your Cloudflare Workers application telemetry to Axiom, you can:
-
-- Store and query logs and traces at scale
+- Store and query logs and traces at scale 
 - Create dashboards and alerts to monitor your Workers
 
 ![Trace view with timing information displayed on a timeline](~/assets/images/workers-observability/axiom-example.png)
@@ -30,7 +29,6 @@ Before you begin, ensure you have:
 ## Step 1: Create a dataset
 
 If you don't already have a dataset to send data to:
-
 1. Log in to your [Axiom account](https://app.axiom.co/)
 2. Navigate to **Datasets** in the left sidebar
 3. Click **New Dataset**
@@ -58,7 +56,6 @@ Now you'll create destinations in the Cloudflare dashboard that point to Axiom.
 ### Axiom OTLP endpoints
 
 Axiom provides separate OTLP endpoints for traces and logs:
-
 - **Traces**: `https://api.axiom.co/v1/traces`
 - **Logs**: `https://api.axiom.co/v1/logs`
 
@@ -70,13 +67,13 @@ Axiom provides separate OTLP endpoints for traces and logs:
    - **Destination Name**: `axiom-traces` (or any descriptive name)
    - **Destination Type**: Select **Traces**
    - **OTLP Endpoint**: `https://api.axiom.co/v1/traces` (or `/v1/logs`)
-   - **Custom Headers**: Add two required headers:
-     - Authentication header
-       - Header name: `Authorization`
-       - Header value: `Bearer <your-api-token>`
-     - Dataset header:
+   - **Custom Headers**: Add two required headers: 
+     -  Authentication header 
+        - Header name: `Authorization`
+        - Header value: `Bearer <your-api-token>` 
+     - Dataset header: 
        - Header name: `X-Axiom-Dataset`
-       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`)
+       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`) 
 4. Click **Save**
 
 ## Step 3: Configure your Worker
@@ -107,5 +104,6 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Axiom.
+It may take a few minutes after deployment for data to appear in Axiom. 
 :::
+
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
index 996992e42bfb4d6..8592f3ba188c813 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
@@ -7,11 +7,9 @@ sidebar:
 products:
   - workers
 ---
-
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Grafana Cloud is a fully managed observability platform that provides visualization, alerting, and analytics for your telemetry data. By exporting your Cloudflare Workers telemetry to Grafana Cloud, you can:
-
 - Visualize distributed traces in **Grafana Tempo** to understand request flows and performance bottlenecks
 - Query and analyze logs in **Grafana Loki** alongside your traces
 
@@ -32,25 +30,24 @@ Before you begin, ensure you have:
 2. From your organization's home page, navigate to **Connections** → **Add new connection**
 3. Search for "OpenTelemetry" and select **OpenTelemetry (OTLP)**
 4. Select **Quickstart** then select **JavaScript**
-5. Click **Create a new token**
-6. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
-7. Click on **Close** without copying the token
-8. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
+6. Click **Create a new token**
+7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
+8. Click on **Close** without copying the token
+9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
 
-## Step 2: Set up destination
 
+## Step 2: Set up destination 
 1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
 2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
-3. From Grafana, copy your Otel endpoint, auth header, and auth value
-
-- Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs)
-- Your custom header should include:
-  - Your auth header name `Authorization`
-  - Your auth header value `Basic MTMxxx...`
+3. From Grafana, copy your Otel endpoint, auth header, and auth value 
+  * Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs) 
+  * Your custom header should include: 
+      * Your auth header name `Authorization`
+      * Your auth header value `Basic MTMxxx...`
 
 ## Step 3: Configure your Worker
 
-With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
+With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export. 
 
 <WranglerConfig>
 
@@ -73,8 +70,8 @@ With your destination created in the Cloudflare dashboard, update your Worker's
 
 </WranglerConfig>
 
-After updating your configuration, deploy your Worker for the changes to take effect.
+After updating your configuration, deploy your Worker for the changes to take effect. 
 
 :::note
-It may take a few minutes after deployment for data to appear in Grafana Cloud.
+It may take a few minutes after deployment for data to appear in Grafana Cloud. 
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
index 9b00d57e583249b..847f103352c625f 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx
@@ -8,10 +8,9 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Honeycomb is an observability platform built for high-cardinality data that helps you understand and debug your applications. By exporting your Cloudflare Workers application telemetry to Honeycomb, you can:
-
 - Visualize traces to understand request flows and identify performance bottlenecks
 - Query and analyze logs with unlimited dimensionality across any attribute
 - Create custom queries and dashboards to monitor your Workers
@@ -45,12 +44,11 @@ The API key will look something like: `hcaik_01hq...`
 
 ## Step 2: Configure Cloudflare destinations
 
-Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb.
+Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb. 
 
 ### Honeycomb OTLP endpoints
 
 Honeycomb provides separate OTLP endpoints for traces and logs:
-
 - **Traces**: `https://api.honeycomb.io/v1/traces`
 - **Logs**: `https://api.honeycomb.io/v1/logs`
 
@@ -109,5 +107,5 @@ With your destinations created in the Cloudflare dashboard, update your Worker's
 After updating your configuration, deploy your Worker for the changes to take effect.
 
 :::note
-It may take a few minutes after deployment for data to appear in Honeycomb.
+It may take a few minutes after deployment for data to appear in Honeycomb. 
 :::
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
index fbafabca9cdfc0f..fd45dd3b86981fd 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx
@@ -25,18 +25,18 @@ You can export the following types of telemetry data:
 
 Below are common OTLP endpoint formats for popular observability providers. Refer to your provider's documentation for specific details and authentication requirements.
 
-| Provider                                                                                          | Traces Endpoint                                              | Logs Endpoint                                                |
-| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)                   | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
-| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/)           | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
-| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)                        | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
-| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                           | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
-| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)                         | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
-| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)                       | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
-| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)                        | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
-| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/)  | `https://otlp.nr-data.net/v1/traces`                         | `https://otlp.nr-data.net/v1/logs`                           |
-| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp`          | N/A                                                          |
-| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp)                          | `http://splunk.internal:4318/v1/traces`                      | `http://splunk.internal:4318/v1/logs`                        |
+| Provider                                                                                | Traces Endpoint                                              | Logs Endpoint                                                |
+| --------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/)         | `https://api.honeycomb.io/v1/traces`                         | `https://api.honeycomb.io/v1/logs`                           |
+| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`   | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
+| [**Firetiger**](https://docs.firetiger.com/ingest/cloudflare-workers.html)              | `https://ingest.cloud.firetiger.com/v1/traces`               | `https://ingest.cloud.firetiger.com/v1/logs`                 |
+| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/)                 | `https://api.axiom.co/v1/traces`                             | `https://api.axiom.co/v1/logs`                               |
+| [**Sentry**](/workers/observability/exporting-opentelemetry-data/sentry/)               | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces` | `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`   |
+| [**PostHog**](/workers/observability/exporting-opentelemetry-data/posthog/)             | Not supported                                                | `https://{REGION}.i.posthog.com/i/v1/logs`                   |
+| [**Datadog**](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/)              | Coming soon, pending release from Datadog                    | `https://otlp.{SITE}.datadoghq.com/v1/logs`                  |
+| [**New Relic**](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/) | `https://otlp.nr-data.net/v1/traces` | `https://otlp.nr-data.net/v1/logs` |
+| [**Splunk Observability**](https://dev.splunk.com/observability/reference/api/ingest_data/latest) | `https://ingest.{REALM}.signalfx.com/v2/trace/otlp` | N/A |
+| [**Splunk Platform**](https://github.com/splunk/splunk-connect-for-otlp) | `http://splunk.internal:4318/v1/traces` | `http://splunk.internal:4318/v1/logs` |
 
 :::note[Authentication]
 Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.
@@ -109,11 +109,11 @@ After creating a destination, you can monitor its health and delivery status in
 
 ### Status indicators
 
-| Status                  | Description                                                             | Troubleshooting                                                                                                |
-| ----------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
-| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                                |
+| Status                  | Description                                                             | Troubleshooting                                                                                               |
+| ----------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| **Last: n minutes ago** | Data was recently delivered successfully.                               |                                                                                                               |
 | **Never run**           | No data has been delivered to this destination.                         | •Check if your Worker is receiving traffic <br /> • Review sampling rates (low rates generate less data)<br /> |
-| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                      |
+| **Error**               | An error occurred while attempting to deliver data to this destination. | • Verify OTLP endpoint URL is correct<br />• Check authentication headers are valid<br />                     |
 
 ## Limits and pricing
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
index 69002849ba8e0f1..0f42b67c6bb7168 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/posthog.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 PostHog is a product analytics platform that helps you understand user behavior and debug issues. By exporting your Cloudflare Workers application telemetry to PostHog, you can:
 
@@ -41,10 +41,10 @@ The API key should look something like: `phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 PostHog has different endpoints depending on your data region:
 
-| Region           | Logs Endpoint                        |
-| ---------------- | ------------------------------------ |
+| Region | Logs Endpoint |
+| ------ | ------------- |
 | **US** (default) | `https://us.i.posthog.com/i/v1/logs` |
-| **EU**           | `https://eu.i.posthog.com/i/v1/logs` |
+| **EU** | `https://eu.i.posthog.com/i/v1/logs` |
 
 You can find your region in your PostHog project settings or by checking the URL when logged into PostHog (either `us.posthog.com` or `eu.posthog.com`).
 
@@ -104,7 +104,6 @@ Once your Worker is deployed and receiving traffic:
 3. Your Worker logs will appear with severity levels, timestamps, and attributes
 
 You can filter logs by:
-
 - **Severity level** (trace, debug, info, warn, error, fatal)
 - **Time range**
 - **Custom attributes** added to your log entries
@@ -116,25 +115,25 @@ You can add custom attributes to your logs using standard `console` methods with
 
 ```javascript
 export default {
-	async fetch(request, env) {
-		// Basic logging
-		console.log("Processing request");
-
-		// Logs with additional context
-		console.info("User action", {
-			userId: "user_123",
-			action: "api_call",
-			path: new URL(request.url).pathname,
-		});
-
-		// Error logging with details
-		console.error("Request failed", {
-			error: "Connection timeout",
-			retryCount: 3,
-		});
-
-		return new Response("OK");
-	},
+  async fetch(request, env) {
+    // Basic logging
+    console.log("Processing request");
+
+    // Logs with additional context
+    console.info("User action", {
+      userId: "user_123",
+      action: "api_call",
+      path: new URL(request.url).pathname
+    });
+
+    // Error logging with details
+    console.error("Request failed", {
+      error: "Connection timeout",
+      retryCount: 3
+    });
+
+    return new Response("OK");
+  }
 };
 ```
 
diff --git a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
index 1c602ea7225b551..57d0992698f5e67 100644
--- a/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
+++ b/src/content/docs/workers/observability/exporting-opentelemetry-data/sentry.mdx
@@ -8,10 +8,9 @@ products:
   - workers
 ---
 
-import { WranglerConfig } from "~/components";
+import {WranglerConfig} from "~/components";
 
 Sentry is a software monitoring tool that helps developers identify and debug performance issues and errors. From end-to-end distributed tracing to performance monitoring, Sentry provides code-level observability that makes it easy to diagnose issues and learn continuously about your application code health across systems and services. By exporting your Cloudflare Workers application telemetry to Sentry, you can:
-
 - Query logs and traces in Sentry
 - Create custom alerts and dashboards to monitor your Workers
 
@@ -38,7 +37,6 @@ If you don't already have a Sentry project to send data to, you'll need to creat
 ## Step 2: Get your Sentry OTLP endpoints
 
 Sentry provides separate OTLP endpoints for traces and logs which you can use to send your telemetry data to Sentry.
-
 - **Traces**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`
 - **Logs**: `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`
 
@@ -59,24 +57,23 @@ To set up a destination in the Cloudflare dashboard, navigate to your Cloudflare
 ### Traces Destination
 
 To configure your traces destination, click **Add destination** and configure the following:
-
-- **Destination Name**: `sentry-traces` (or any descriptive name)
-- **Destination Type**: Select **Traces**
-- **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
-- **Custom Headers**: Add the Sentry authentication header:
-  - Header name: `x-sentry-auth`
-  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
+   - **Destination Name**: `sentry-traces` (or any descriptive name)
+   - **Destination Type**: Select **Traces**
+   - **OTLP Endpoint**: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
+   - **Custom Headers**: Add the Sentry authentication header:
+     - Header name: `x-sentry-auth`
+     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ### Logs destination
 
 To configure your logs destination, click **Add destination** and configure the following:
+   - **Destination Name**: `sentry-logs` (or any descriptive name)
+   - **Destination Type**: Select **Logs**
+   - **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
+   - **Custom Headers**: Add the Sentry authentication header:
+     - Header name: `x-sentry-auth`
+     - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
-- **Destination Name**: `sentry-logs` (or any descriptive name)
-- **Destination Type**: Select **Logs**
-- **OTLP Endpoint**: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
-- **Custom Headers**: Add the Sentry authentication header:
-  - Header name: `x-sentry-auth`
-  - Header value: `sentry sentry_key={SENTRY_PUBLIC_KEY}` where `{SENTRY_PUBLIC_KEY}` is your Sentry project's public key
 
 ## Step 4: Configure your Worker
 
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 2b21d8e285a2a6b..72b1c12297f3d02 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -17,8 +17,10 @@ import { WranglerConfig, DashButton } from "~/components";
 
 :::caution
 
+
 Workers Trace Events Logpush is not available for zones on the [Cloudflare China Network](/china-network/).
 
+
 :::
 
 ## Verify your Logpush access
@@ -28,7 +30,6 @@ Minimum required Wrangler version: 2.2.0. Check your version by running `wrangle
 :::
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
-
 1. In the Cloudflare dashboard, go to the **Members** page.
 
    <DashButton url="/?to=/:account/members" />
@@ -42,7 +43,6 @@ Alternatively, create a new [API token](/fundamentals/api/get-started/create-tok
 ### Via the Cloudflare dashboard
 
 To create a Logpush job in the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Logpush** page.
 
    <DashButton url="/?to=/:account/logs" />
@@ -117,7 +117,6 @@ curl --request PUT \
 ### Dashboard
 
 To enable Logpush logging via the dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
@@ -148,30 +147,30 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-	"Exceptions": [
-		{
-			"Name": "SampleError",
-			"Message": "something went wrong",
-			"TimestampMs": 0
-		},
-		{
-			"Name": "AuthError",
-			"Message": "unable to process request authentication from client",
-			"TimestampMs": 1
-		}
-	],
-	"Logs": [
-		{
-			"Level": "log",
-			"Message": ["Hello "],
-			"TimestampMs": 0
-		},
-		{
-			"Level": "log",
-			"Message": ["World!"],
-			"TimestampMs": 0
-		}
-	]
+  "Exceptions": [
+    {
+      "Name": "SampleError",
+      "Message": "something went wrong",
+      "TimestampMs": 0
+    },
+    {
+      "Name": "AuthError",
+      "Message": "unable to process request authentication from client",
+      "TimestampMs": 1
+    },
+  ],
+  "Logs": [
+    {
+      "Level": "log",
+      "Message": ["Hello "],
+      "TimestampMs": 0
+    },
+    {
+      "Level": "log",
+      "Message": ["World!"],
+      "TimestampMs": 0
+    }
+  ]
 }
 ```
 
@@ -179,24 +178,24 @@ To illustrate this, suppose our Logpush event looks like the JSON below and the
 
 ```json
 {
-	"Exceptions": [
-		{
-			"name": "SampleError",
-			"message": "something went wrong",
-			"TimestampMs": 0
-		},
-		{
-			"name": "AuthError",
-			"message": "unable to <<<Logpush: exception messages truncated>>>",
-			"TimestampMs": 1
-		}
-	],
-	"Logs": [
-		{
-			"Level": "log",
-			"Message": ["<<<Logpush: messages truncated>>>"],
-			"TimestampMs": 0
-		}
-	]
+  "Exceptions": [
+    {
+      "name": "SampleError",
+      "message": "something went wrong",
+      "TimestampMs": 0
+    },
+    {
+      "name": "AuthError",
+      "message": "unable to <<<Logpush: exception messages truncated>>>",
+      "TimestampMs": 1
+    },
+  ],
+  "Logs": [
+    {
+      "Level": "log",
+      "Message": ["<<<Logpush: messages truncated>>>"],
+      "TimestampMs": 0
+    }
+  ]
 }
 ```
diff --git a/src/content/docs/workers/observability/logs/real-time-logs.mdx b/src/content/docs/workers/observability/logs/real-time-logs.mdx
index 32ea43c6b2fedf7..65b48530222963a 100644
--- a/src/content/docs/workers/observability/logs/real-time-logs.mdx
+++ b/src/content/docs/workers/observability/logs/real-time-logs.mdx
@@ -25,7 +25,6 @@ Real-time logs are not available for zones on the [Cloudflare China Network](/ch
 ## View logs from the dashboard
 
 To view real-time logs associated with any deployed Worker using the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
index 88e00843194056a..1f162b257fc1d15 100644
--- a/src/content/docs/workers/observability/logs/workers-logs.mdx
+++ b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -53,7 +53,7 @@ You must add the observability setting for your Worker to write logs to Workers
 
 [Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for an environment named `staging`: 1. Add the following configuration below `[env.staging]`
 
-<WranglerConfig>
+    <WranglerConfig>
 
     ```jsonc
     {
@@ -70,8 +70,8 @@ You must add the observability setting for your Worker to write logs to Workers
 
     </WranglerConfig>
 
-2. Deploy your Worker with `npx wrangler deploy -e staging`
-3. Repeat step 1 and 2 for each environment.
+    2. Deploy your Worker with `npx wrangler deploy -e staging`
+    3. Repeat step 1 and 2 for each environment.
 
 ## View logs from the dashboard
 
diff --git a/src/content/docs/workers/observability/metrics-and-analytics.mdx b/src/content/docs/workers/observability/metrics-and-analytics.mdx
index 3f270c3f47959fb..ef28c321eb02f2a 100644
--- a/src/content/docs/workers/observability/metrics-and-analytics.mdx
+++ b/src/content/docs/workers/observability/metrics-and-analytics.mdx
@@ -54,7 +54,6 @@ Subrequests are requests triggered by calling `fetch` from within a Worker. A su
 ### Wall time per execution
 
 <GlossaryTooltip term="wall-clock time">Wall time</GlossaryTooltip> represents
-
 the elapsed time in milliseconds between the start of a Worker invocation, and
 when the Workers runtime determines that no more JavaScript needs to run.
 Specifically, wall time per execution chart measures the wall time that the
diff --git a/src/content/docs/workers/observability/source-maps.mdx b/src/content/docs/workers/observability/source-maps.mdx
index 20d213c75c986ae..2872e097f8f75a0 100644
--- a/src/content/docs/workers/observability/source-maps.mdx
+++ b/src/content/docs/workers/observability/source-maps.mdx
@@ -45,8 +45,10 @@ You can then view the stack trace when streaming [real-time logs](/workers/obser
 
 :::note
 
+
 The source map is retrieved after your Worker invocation completes — it's an asynchronous process that does not impact your Worker's CPU utilization or performance. Source maps are not accessible inside the Worker at runtime, if you `console.log()` the [stack property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/stack) within a Worker, you will not get a deobfuscated stack trace.
 
+
 :::
 
 When Cloudflare attempts to remap a stack trace to the Worker's source map, it does so line-by-line, remapping as much as possible. If a line of the stack trace cannot be remapped for any reason, Cloudflare will leave that line of the stack trace unchanged, and continue to the next line of the stack trace.
@@ -57,9 +59,10 @@ When Cloudflare attempts to remap a stack trace to the Worker's source map, it d
 Minimum required Wrangler version for source maps: 3.46.0. Check your version by running `wrangler --version`.
 :::
 
-| Description             | Limit         |
-| ----------------------- | ------------- |
-| Maximum Source Map Size | 15 MB gzipped |
+
+| Description                    | Limit         |
+| ------------------------------ | ------------- |
+| Maximum Source Map Size        | 15 MB gzipped |
 
 ## Example
 
@@ -85,6 +88,6 @@ With **source maps uploaded**: all methods reference the correct files and line
 
 ## Related resources
 
-- [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
-- [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
-- [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
+* [Tail Workers](/workers/observability/logs/logpush/) - Learn how to attach Tail Workers to transform your logs and send them to HTTP endpoints.
+* [Real-time logs](/workers/observability/logs/real-time-logs/) - Learn how to capture Workers logs in real-time.
+* [RPC error handling](/workers/runtime-apis/rpc/error-handling/) - Learn how exceptions are handled over RPC (Remote Procedure Call).
diff --git a/src/content/docs/workers/platform/betas.mdx b/src/content/docs/workers/platform/betas.mdx
index e151ed5f512fd42..99cebde932f6ce9 100644
--- a/src/content/docs/workers/platform/betas.mdx
+++ b/src/content/docs/workers/platform/betas.mdx
@@ -12,11 +12,11 @@ products:
 
 These are the current alphas and betas relevant to the Cloudflare Workers platform.
 
-- **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
-- Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
+* **Public alphas and betas are openly available**, but may have limitations and caveats due to their early stage of development.
+* Private alphas and betas require explicit access to be granted. Refer to the documentation to join the relevant product waitlist.
 
 | Product                                           | Private Beta | Public Beta | More Info                                                                   |
 | ------------------------------------------------- | ------------ | ----------- | --------------------------------------------------------------------------- |
-| Email Workers                                     |              | ✅          | [Docs](/email-routing/email-workers/)                                       |
-| Green Compute                                     |              | ✅          | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
-| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅          | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
+| Email Workers                                     |              | ✅           | [Docs](/email-routing/email-workers/)                                       |
+| Green Compute                                     |              | ✅           | [Blog](https://blog.cloudflare.com/earth-day-2022-green-compute-open-beta/) |
+| [TCP Sockets](/workers/runtime-apis/tcp-sockets/) |              | ✅           | [Docs](/workers/runtime-apis/tcp-sockets)                                   |
diff --git a/src/content/docs/workers/platform/built-with-cloudflare.mdx b/src/content/docs/workers/platform/built-with-cloudflare.mdx
index 42aafcb95946784..b9ae5fb6977f6da 100644
--- a/src/content/docs/workers/platform/built-with-cloudflare.mdx
+++ b/src/content/docs/workers/platform/built-with-cloudflare.mdx
@@ -45,4 +45,4 @@ The Built with Cloudflare button is an SVG and can be embedded anywhere. Use the
 https://workers.cloudflare.com/built-with-cloudflare.svg
 ```
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/docs/workers/platform/changelog/historical-changelog.mdx b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
index 6ecdf4d3609fbdb..0b2cbd209519aa6 100644
--- a/src/content/docs/workers/platform/changelog/historical-changelog.mdx
+++ b/src/content/docs/workers/platform/changelog/historical-changelog.mdx
@@ -16,374 +16,374 @@ This page tracks changes made to Cloudflare Workers before 2023. For a view of m
 
 ## 2022-12-16
 
-- Conditional `PUT` requests have been fixed in the R2 bindings API.
+* Conditional `PUT` requests have been fixed in the R2 bindings API.
 
 ## 2022-12-02
 
-- Queues no longer support calling `send()` with an undefined JavaScript value as the message.
+* Queues no longer support calling `send()` with an undefined JavaScript value as the message.
 
 ## 2022-11-30
 
-- The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
-- Extended the R2 binding API to include support for multipart uploads.
+* The DOMException constructor has been updated to align better with the standard specification. Specifically, the message and name arguments can now be any JavaScript value that is coercible into a string (previously, passing non-string values would throw).
+* Extended the R2 binding API to include support for multipart uploads.
 
 ## 2022-11-17
 
-- V8 update: 10.6 → 10.8
+* V8 update: 10.6 → 10.8
 
 ## 2022-11-02
 
-- Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
+* Implemented `toJSON()` for R2Checksums so that it is usable with `JSON.stringify()`.
 
 ## 2022-10-21
 
-- The alarm retry limit will no longer apply to errors that are our fault.
-- Compatibility dates have been added for multiple flags including the new streams implementation.
-- `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
+* The alarm retry limit will no longer apply to errors that are our fault.
+* Compatibility dates have been added for multiple flags including the new streams implementation.
+* `DurableObjectStorage` has a new method `sync()` that provides a way for a Worker to wait for its writes (including those performed with `allowUnconfirmed`) to be synchronized with storage.
 
 ## 2022-10-10
 
-- Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
-- `console.log` now prints more information about certain objects, for example Promises.
-- The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
+* Fixed a bug where if an ES-modules-syntax script exported an array-typed value from the top-level module, the upload API would refuse it with a [`500` error](https://community.cloudflare.com/t/community-tip-fixing-error-500-internal-server-error/44453).
+* `console.log` now prints more information about certain objects, for example Promises.
+* The Workers Runtime is now built from the Open Source code in: [GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers](https://github.com/cloudflare/workerd).
 
 ## 2022-09-16
 
-- R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
-- Allow deleting multiple keys at once in R2 bindings.
-- Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
-- User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
-- Updated V8 to 10.6.
+* R2 `put` bindings options can now have an `onlyIf` field similar to `get` that does a conditional upload.
+* Allow deleting multiple keys at once in R2 bindings.
+* Added support for SHA-1, SHA-256, SHA-384, SHA-512 checksums in R2 `put` options.
+* User-specified object checksums will now be available in the R2 `get/head` bindings response. MD5 is included by default for non-multipart uploaded objects.
+* Updated V8 to 10.6.
 
 ## 2022-08-12
 
-- A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
-- When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
-- Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
-- Validation errors during Worker upload for module scripts now include correct line and column numbers.
-- Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
+* A `Headers` object with the `range` header can now be used for range within `R2GetOptions` for the `get` R2 binding.
+* When headers are used for `onlyIf` within `R2GetOptions` for the `get` R2 binding, they now correctly compare against the second granularity. This allows correctly round-tripping to the browser and back. Additionally, `secondsGranularity` is now an option that can be passed into options constructed by hand to specify this when constructing outside Headers for the same effect.
+* Fixed the TypeScript type of `DurableObjectState.id` in [@cloudflare/workers-types](https://github.com/cloudflare/workers-types) to always be a `DurableObjectId`.
+* Validation errors during Worker upload for module scripts now include correct line and column numbers.
+* Bugfix, Profiling tools and flame graphs via Chrome’s debug tools now properly report information.
 
 ## 2022-07-08
 
-- Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
+* Workers Usage Report and Workers Weekly Summary have been disabled due to scaling issues with the service.
 
 ## 2022-06-24
 
-- `wrangler dev` in global network preview mode now supports scheduling alarms.
-- R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
-- Some Web Cryptography API error messages include more information now.
-- Updated V8 from 10.2 to 10.3.
+* `wrangler dev` in global network preview mode now supports scheduling alarms.
+* R2 GET requests made with the `range` option now contain the returned range in the `GetObject`’s `range` parameter.
+* Some Web Cryptography API error messages include more information now.
+* Updated V8 from 10.2 to 10.3.
 
 ## 2022-06-18
 
-- Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
-- The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
+* Cron trigger events on Worker scripts using the old `addEventListener` syntax are now treated as failing if there is no event listener registered for `scheduled` events.
+* The `durable_object_alarms` flag no longer needs to be explicitly provided to use DO alarms.
 
 ## 2022-06-09
 
-- No externally-visible changes.
+* No externally-visible changes.
 
 ## 2022-06-03
 
-- It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
-- Preview in Quick Edit now correctly uses the correct R2 bindings.
-- Updated V8 from 10.1 to 10.2.
+* It is now possible to create standard `TransformStream` instances that can perform transformations on the data. Because this changes the behavior of the default `new TransformStream()` with no arguments, the `transformstream_enable_standard_constructor` compatibility flag is required to enable.
+* Preview in Quick Edit now correctly uses the correct R2 bindings.
+* Updated V8 from 10.1 to 10.2.
 
 ## 2022-05-26
 
-- The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
-- R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
+* The static `Response.json()` method can be used to initialize a Response object with a JSON-serialized payload (refer to [whatwg/fetch #1392](https://github.com/whatwg/fetch/pull/1392)).
+* R2 exceptions being thrown now have the `error` code appended in the message in parenthesis. This is a stop-gap until we are able to explicitly add the code property on the thrown `Error` object.
 
 ## 2022-05-19
 
-- R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
-- ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
-- Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
-- R2: Better runtime support for additional ranges.
-- R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
+* R2 bindings: `contentEncoding`, `contentLanguage`, and `cacheControl` are now correctly rendered.
+* ReadableStream `pipeTo` and `pipeThrough` now support cancellation using `AbortSignal`.
+* Calling `setAlarm()` in a DO with no `alarm()` handler implemented will now throw instead of failing silently. Calling `getAlarm()` when no `alarm()` handler is currently implemented will return null, even if an alarm was previously set on an old version of the DO class, as no execution will take place.
+* R2: Better runtime support for additional ranges.
+* R2 bindings now support ranges that have an `offset` and an optional `length`, a `length` and an optional `offset`, or a `suffix` (returns the last `N` bytes of a file).
 
 ## 2022-05-12
 
-- Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
-- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-- Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
-- R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
-- R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
-- Added `startAfter` option to the `list()` method in the Durable Object storage API.
+* Fix R2 bindings saving cache-control under content-language and rendering cache-control under content-language.
+* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+* Fix R2 bindings which did not correctly handle error messages from R2, resulting in `internal error` being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+* R2 bindings: if the onlyIf condition results in a precondition failure or a not modified result, the object is returned without a body instead of returning null.
+* R2 bindings: sha1 is removed as an option because it was not actually hooked up to anything. TBD on additional checksum options beyond md5.
+* Added `startAfter` option to the `list()` method in the Durable Object storage API.
 
 ## 2022-05-05
 
-- `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
-- Fix generated types for Date.
-- Fix R2 bindings list without options to use the default list limit instead of never returning any results.
-- Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
+* `Response.redirect(url)` will no longer coalesce multiple consecutive slash characters appearing in the URL’s path.
+* Fix generated types for Date.
+* Fix R2 bindings list without options to use the default list limit instead of never returning any results.
+* Fix R2 bindings did not correctly handle error messages from R2, resulting in internal error being thrown. Also fix behavior for get throwing an exception on a non-existent key instead of returning null. `R2Error` is removed for the time being and will be reinstated at some future time TBD.
 
 ## 2022-04-29
 
-- Minor V8 update: 10.0 → 10.1.
-- R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
+* Minor V8 update: 10.0 → 10.1.
+* R2 public beta bindings are the default regardless of compat date or flags. Internal beta bindings customers should transition to public beta bindings as soon as possible. A back compatibility flag is available if this is not immediately possible. After some lag, new scripts carrying the `r2_public_beta_bindings` compatibility flag will stop accepting to be published until that flag is removed.
 
 ## 2022-04-22
 
-- Major V8 update: 9.9 → 10.0.
+* Major V8 update: 9.9 → 10.0.
 
 ## 2022-04-14
 
-- Performance and stability improvements.
+* Performance and stability improvements.
 
 ## 2022-04-08
 
-- The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
-- R2 error responses now include better details.
+* The AES-GCM implementation that is part of the Web Cryptography API now returns a friendlier error explaining that 0-length IVs are not allowed.
+* R2 error responses now include better details.
 
 ## 2022-03-24
 
-- A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
-- When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
-- The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
+* A new compatibility flag has been introduced, `minimal_subrequests` , which removes some features that were unintentionally being applied to same-zone `fetch()` calls. The flag will default to enabled on Tuesday, 2022-04-05, and is described in [Workers `minimal_subrequests` compatibility flag](/workers/configuration/compatibility-flags/#minimal-subrequests).
+* When creating a `Response` with JavaScript-backed ReadableStreams, the `Body` mixin functions (e.g. `await response.text()` ) are now implemented.
+* The `IdentityTransformStream` creates a byte-oriented `TransformStream` implementation that simply passes bytes through unmodified. The readable half of the `TransformStream` supports BYOB-reads. It is important to note that `IdentityTransformStream` is identical to the current non-spec compliant `TransformStream` implementation, which will be updated soon to conform to the WHATWG Stream Standard. All current uses of `new TransformStream()` should be replaced with `new IdentityTransformStream()` to avoid potentially breaking changes later.
 
 ## 2022-03-17
 
-- The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
-- When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
-- Fix R2 publish date rendering.
-- Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
-- When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
+* The standard [ByteLengthQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/ByteLengthQueuingStrategy) and [CountQueuingStrategy](https://developer.mozilla.org/en-US/docs/Web/API/CountQueuingStrategy) classes are now available.
+* When the `capture_async_api_throws` flag is set, built-in Cloudflare-specific and Web Platform Standard APIs that return Promises will no longer throw errors synchronously and will instead return rejected promises. Exception is given with fatal errors such as out of memory errors.
+* Fix R2 publish date rendering.
+* Fix R2 bucket binding .get populating contentRange with garbage. contentRange is now undefined as intended.
+* When using JavaScript-backed `ReadableStream`, it is now possible to use those streams with `new Response()`.
 
 ## 2022-03-11
 
-- Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
-- Implementations of `CompressionStream` and `DecompressionStream` are now available.
+* Fixed a bug where the key size was not counted when determining how many write units to charge for a Durable Object single-key `put()`. This may result in future writes costing one write unit more than past writes when the key is large enough to bump the total write size up above the next billing unit threshold of 4096 bytes. Multi-key `put()` operations have always properly counted the key size when determining billable write units.
+* Implementations of `CompressionStream` and `DecompressionStream` are now available.
 
 ## 2022-03-04
 
-- Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
-- With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
-- A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
-- The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
-- An implementation of `URLPattern` is now available.
+* Initial pipeTo/pipeThrough support on ReadableStreams constructed using the new `ReadableStream()` constructor is now available.
+* With the `global_navigator` compatibility flag set, the `navigator.userAgent` property can be used to detect when code is running within the Workers environment.
+* A bug in the new URL implementation was fixed when setting the value of a `URLSearchParam`.
+* The global `addEventListener` and dispatchEvent APIs are now available when using module syntax.
+* An implementation of `URLPattern` is now available.
 
 ## 2022-02-25
 
-- The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
-- Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
-- Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
+* The `TextDecoder` class now supports the full range of text encodings defined by the WHATWG Encoding Standard.
+* Both global `fetch()` and durable object `fetch()` now throw a TypeError when they receive a WebSocket in response to a request without the “Upgrade: websocket” header.
+* Durable Objects users may now store up to 50 GB of data across the objects in their account by default. As before, if you need more storage than that you can contact us for an increase.
 
 ## 2022-02-18
 
-- `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
+* `TextDecoder` now supports Windows-1252 labels (aka ASCII): [Encoding API Encodings - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API/Encodings).
 
 ## 2022-02-11
 
-- WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
+* WebSocket message sends were erroneously not respecting Durable Object output gates as described in the [I/O gate blog post](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/). That bug has now been fixed, meaning that WebSockets will now never send a message under the assumption that a storage write has succeeded unless that write actually has succeeded.
 
 ## 2022-02-05
 
-- Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
-- `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
-- A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
+* Fixed bug causing WebSockets to Durable Objects to occasionally hang when the script implementing both a Worker and a Durable Object is re-deployed with new code.
+* `crypto.getRandomValues` now supports BigInt64Array and BigUint64Array.
+* A new implementation of the standard URL implementation is available. Use `url_standard` feature flag to enable the spec-compliant URL API implementation.
 
 ## 2022-01-28
 
-- No user-visible changes.
+* No user-visible changes.
 
 ## 2022-01-20
 
-- Updated V8: 9.7 → 9.8.
+* Updated V8: 9.7 → 9.8.
 
 ## 2022-01-17
 
-- `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
-- Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
+* `HTMLRewriter` now supports inspecting and modifying end tags, not just start tags.
+* Fixed bug where Durable Objects experiencing a transient CPU overload condition would cause in-progress requests to be unable to return a response (appearing as an indefinite hang from the client side), even after the overload condition clears.
 
 ## 2022-01-07
 
-- The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
+* The `workers_api_getters_setters_on_prototype` configuration flag corrects the way Workers attaches property getters and setters to API objects so that they can be properly subclassed.
 
 ## 2021-12-22
 
-- Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
+* Async iteration (using `for` and `await`) on instances of `ReadableStream` is now available.
 
 ## 2021-12-10
 
-- Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
-- `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
-- Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
-- `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
-- Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
-- Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
+* Raised the max value size in Durable Object storage from 32 KiB to 128 KiB.
+* `AbortSignal.timeout(delay)` returns an `AbortSignal` that will be triggered after the given number of milliseconds.
+* Preview implementations of the new `ReadableStream` and new `WritableStream` constructors are available behind the `streams_enable_constructors` feature flag.
+* `crypto.DigestStream` is a non-standard extension to the crypto API that supports generating a hash digest from streaming data. The `DigestStream` itself is a `WritableStream` that does not retain the data written into it; instead, it generates a digest hash automatically when the flow of data has ended. The same hash algorithms supported by `crypto.subtle.digest()` are supported by the `crypto.DigestStream`.
+* Added early support for the `scheduler.wait()` API, which is [going through the WICG standardization process](https://github.com/WICG/scheduling-apis), to provide an `await`-able alternative to `setTimeout()`.
+* Fixed bug in `deleteAll` in Durable Objects containing more than 10000 keys that could sometimes cause incomplete data deletion and/or hangs.
 
 ## 2021-12-02
 
-- The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
-- Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
+* The Streams spec requires that methods returning promises must not throw synchronous errors. As part of the effort of making the Streams implementation more spec compliant, we are converting a number of sync throws to async rejections.
+* Major V8 update: 9.6 → 9.7. See [V8 release v9.7 · V8](https://v8.dev/blog/v8-release-97) for more details.
 
 ## 2021-11-19
 
-- Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
-- Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
-- [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
+* Durable Object stubs that receive an overload exception will be permanently broken to match the behavior of other exception types.
+* Fixed issue where preview service claimed Let’s Encrypt certificates were expired.
+* [`structuredClone()`](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone) is now supported.
 
 ## 2021-11-12
 
-- The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
-- Unhandled rejection warnings will be printed to the inspector console.
+* The `AbortSignal` object has a new `reason` property indicating the reason for the cancellation. The reason can be specified when the `AbortSignal` is triggered or created.
+* Unhandled rejection warnings will be printed to the inspector console.
 
 ## 2021-11-05
 
-- Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
-- Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams_byob_reader_detaches_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
+* Upgrade to V8 9.6. This adds support for WebAssembly reference types. Refer to the [V8 release v9.6 · V8](https://v8.dev/blog/v8-release-96) for more details.
+* Streams: When using the BYOB reader, the `ArrayBuffer` of the provided TypedArray should be detached, per the Streams spec. Because Workers was not previously enforcing that rule, and changing to comply with the spec could breaking existing code, a new compatibility flag, [streams\_byob\_reader\_detaches\_buffer](https://github.com/cloudflare/cloudflare-docs/pull/2644), has been introduced that will be enabled by default on 2021-11-10. User code should never try to reuse an `ArrayBuffer` that has been passed in to a BYOB readers `read()` method. The more recently added extension method `readAtLeast()` will always detach the `ArrayBuffer` and is unaffected by the compatibility flag setting.
 
 ## 2021-10-21
 
-- Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
-- The `unhandledrejection` and `rejectionhandled` events are now supported.
-- The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
-- Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
-- The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
+* Added support for the `signal` option in `EventTarget.addEventListener()`, to remove an event listener in response to an `AbortSignal`.
+* The `unhandledrejection` and `rejectionhandled` events are now supported.
+* The `ReadableStreamDefaultReader` and `ReadableStreamBYOBReader` constructors are now supported.
+* Added non-standard `ReadableStreamBYOBReader` method `.readAtLeast(size, buffer)` that can be used to return a buffer with at least `size` bytes. The `buffer` parameter must be an `ArrayBufferView`. Behavior is identical to `.read()` except that at least `size` bytes are read, only returning fewer if EOF is encountered. One final call to `.readAtLeast()` is still needed to get back a `done = true` value.
+* The compatibility flags `formdata_parser_supports_files`, `fetch_refuses_unknown_protocols`, and `durable_object_fetch_requires_full_url` have been scheduled to be turned on by default as of 2021-11-03, 2021-11-10, and 2021-11-10, respectively. For more details, refer to [Compatibility Dates](/workers/configuration/compatibility-dates/)
 
 ## 2021-10-14
 
-- `request.signal` will always return an `AbortSignal`.
-- Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
-- Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
+* `request.signal` will always return an `AbortSignal`.
+* Cloudflare Workers’ integration with Chrome DevTools profiling now more accurately reports the line numbers and time elapsed. Previously, the line numbers were shown as one line later then the actual code, and the time shown would be proportional but much longer than the actual time used.
+* Upgrade to v8 9.5. Refer to [V8 release v9.5 · V8](https://v8.dev/blog/v8-release-95) for more details.
 
 ## 2021-09-24
 
-- The `AbortController` and `AbortSignal` objects are now available.
-- The Web Platform `queueMicrotask` API is now available.
-- It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
-- The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
-- Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
-- The `Event` object now supports most standard methods and properties.
-- V8 updated from 9.3 to 9.4.
+* The `AbortController` and `AbortSignal` objects are now available.
+* The Web Platform `queueMicrotask` API is now available.
+* It is now possible to use new `EventTarget()` and to create custom `EventTarget` subclasses.
+* The `once` option is now supported on `addEventTarget` to register event handlers that will be invoked only once.
+* Per the HTML specification, a listener passed in to the `addEventListener` function is allowed to either be a function or an object with a `handleEvent` member function. Previously, Workers only supported the function option, now it supports both.
+* The `Event` object now supports most standard methods and properties.
+* V8 updated from 9.3 to 9.4.
 
 ## 2021-09-03
 
-- The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
-- Durable Objects are now scheduled more evenly around a colocation (colo).
+* The `crypto.randomUUID()` method can be used to generate a new random version 4 UUID.
+* Durable Objects are now scheduled more evenly around a colocation (colo).
 
 ## 2021-08-05
 
-- No user-facing changes. Just bug fixes & internal maintenance.
+* No user-facing changes. Just bug fixes & internal maintenance.
 
 ## 2021-07-30
 
-- Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
-- Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
+* Fixed a hang in Durable Objects when reading more than 16MB of data at once (for example, with a large `list()` operation).
+* Added a new compatibility flag `html_rewriter_treats_esi_include_as_void_tag` which causes `HTMLRewriter` to treat `<esi:include>` and `<esi:comment>` as void tags, such that they are considered to have neither an end tag nor nested content. To opt a worker into the new behavior, you must use Wrangler v1.19.0 or newer and specify the flag in `wrangler.toml`. Refer to the [Wrangler compatibility flag notes](https://github.com/cloudflare/wrangler-legacy/pull/2009) for details.
 
 ## 2021-07-23
 
-- Performance and stability improvements.
+* Performance and stability improvements.
 
 ## 2021-07-16
 
-- Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
-- Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
-- Durable Object constructors may now initiate I/O, such as `fetch()` calls.
-- Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
-- In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
+* Workers can now make up to 1000 subrequests to Durable Objects from a within a single request invocation, up from the prior limit of 50.
+* Major changes to Durable Objects implementation, the details of which will be the subject of an upcoming blog post. In theory, the changes should not harm existing apps, except to make them faster. Let your account team know if you observe anything unusual or report your issue in the [Workers Discord](https://discord.cloudflare.com).
+* Durable Object constructors may now initiate I/O, such as `fetch()` calls.
+* Added Durable Objects `state.blockConcurrencyWhile()` API useful for delaying delivery of requests and other events while performing some critical state-affecting task. For example, this can be used to perform start-up initialization in an object’s constructor.
+* In Durable Objects, the callback passed to `storage.transaction()` can now return a value, which will be propagated as the return value of the `transaction()` call.
 
 ## 2021-07-13
 
-- The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
+* The preview service now prints a warning in the devtools console when a script uses `Response/Request.clone()` but does not read one of the cloned bodies. Such a situation forces the runtime to buffer the entire message body in memory, which reduces performance. [Find an example here](https://cloudflareworkers.com/#823fbe463bfafd5a06bcfeabbdf5eeae:https://tutorial.cloudflareworkers.com).
 
 ## 2021-07-01
 
-- Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
-- Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
+* Fixed bug where registering the same exact event listener method twice on the same event type threw an internal error.
+* Add support for the `.forEach()` method for `Headers`, `URLSearchParameters`, and `FormData`.
 
 ## 2021-06-27
 
-- WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
+* WebCrypto: Implemented non-standard Ed25519 operation (algorithm NODE-ED25519, curve name NODE-ED25519). The Ed25519 implementation differs from NodeJS’s in that raw import/export of private keys is disallowed, per parity with ECDSA/ECDH.
 
 ## 2021-06-17
 
 Changes this week:
 
-- Updated V8 from 9.1 to 9.2.
-- `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
+* Updated V8 from 9.1 to 9.2.
+* `wrangler tail` now works on Durable Objects. Note that logs from long-lived WebSockets will not be visible until the WebSocket is closed.
 
 ## 2021-06-11
 
 Changes this week:
 
-- Turn on V8 Sparkplug compiler.
-- Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
+* Turn on V8 Sparkplug compiler.
+* Durable Objects that are finishing up existing requests after their code is updated will be disconnected from the persistent storage API, to maintain the invariant that only a single instance ever has access to persistent storage for a given Durable Object.
 
 ## 2021-06-04
 
 Changes this week:
 
-- WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
-- `request.cf` is no longer missing when writing Workers using modules syntax.
+* WebCrypto: We now support the “raw” import/export format for ECDSA/ECDH public keys.
+* `request.cf` is no longer missing when writing Workers using modules syntax.
 
 ## 2021-05-14
 
 Changes this week:
 
-- Improve error messages coming from the WebCrypto API.
-- Updated V8: 9.0 → 9.1
+* Improve error messages coming from the WebCrypto API.
+* Updated V8: 9.0 → 9.1
 
 Changes in an earlier release:
 
-- WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
-- WebCrypto: Add support for RSA-OAEP
-- WebCrypto: HKDF implemented.
-- Fix recently-introduced backwards clock jumps in Durable Objects.
-- `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
+* WebCrypto: Implement JWK export for RSA, ECDSA, & ECDH.
+* WebCrypto: Add support for RSA-OAEP
+* WebCrypto: HKDF implemented.
+* Fix recently-introduced backwards clock jumps in Durable Objects.
+* `WebCrypto.generateKey()`, when asked to generate a key pair with algorithm RSA-PSS, would instead return a key pair using algorithm RSASSA-PKCS1-v1\_5. Although the key structure is the same, the signature algorithms differ, and therefore, signatures generated using the key would not be accepted by a correct implementation of RSA-PSS, and vice versa. Since this would be a pretty obvious problem, but no one ever reported it to us, we guess that currently, no one is using this functionality on Workers.
 
 ## 2021-04-29
 
 Changes this week:
 
-- WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
-- The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
+* WebCrypto: Implemented `wrapKey()` / `unwrapKey()` for AES algorithms.
+* The arguments to `WebSocket.close()` are now optional, as the standard says they should be.
 
 ## 2021-04-23
 
 Changes this week:
 
-- In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
-- For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
-- When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
-- Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
-- When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
-- When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-- When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
-- `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
+* In the WebCrypto API, encrypt and decrypt operations are now supported for the “AES-CTR” encryption algorithm.
+* For Durable Objects, CPU time limits are now enforced on the object level rather than the request level. Each time a new request arrives, the time limit is “topped up” to 500ms. After the (free) beta period ends and Durable Objects becomes generally available, we will increase this to 30 seconds.
+* When a Durable Object exceeds its CPU time limit, the entire object will be discarded and recreated. Previously, we allowed subrequest requests to continue using the same object, but this was dangerous because hitting the CPU time limit can leave the object in an inconsistent state.
+* Long running Durable Objects are given more subrequest quota as additional WebSocket messages are sent to them, to avoid the problem of a long-running Object being unable to make any more subrequests after it has been held open by a particular WebSocket for a while.
+* When a Durable Object’s code is updated, or when its isolate is reset due to exceeding the memory limit, all stubs pointing to the object will become invalidated and have to be recreated. This is consistent with what happens when the CPU time is exceeded, or when stubs become disconnected due to random network errors. This behavior is useful, as apps can now assume that two messages sent to the same stub will be delivered to exactly the same live instance (if they are delivered at all). Apps which do not care about this property should recreate their stubs for every request; there is no performance penalty from doing so.
+* When a Durable Object’s isolate exceeds its memory limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+* When a Durable Object exceeds its CPU time limit, an exception with an explanatory message will now be thrown to the caller, instead of “internal error”.
+* `wrangler tail` now reports CPU-time-exceeded exceptions with an explanatory message instead of “internal error”.
 
 ## 2021-04-19
 
 Changes since the last post on 3/26:
 
-- Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
-- Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
-- Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
-- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-- Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
-- WebCrypto: Key derivation for ECDH.
-- WebCrypto: Support ECDH key generation & import.
-- WebCrypto: Support ECDSA key generation.
-- Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
-- Improved exception messages thrown by the WebCrypto API somewhat.
-- `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
-- `passThroughOnException` is now available under the ctx argument to module handlers
-- Reliability improvements for Durable Objects
-- Reliability improvements for Durable Objects persistent storage API
-- `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
+* Cron Triggers now have a 15 minute wall time limit, in addition to the existing CPU time limit. (Previously, there was no limit, so a cron trigger that spent all its time waiting for I/O could hang forever.)
+* Our WebCrypto implementation now supports importing and exporting HMAC and AES keys in JWK format.
+* Our WebCrypto implementation now supports AES key generation for CTR, CBC, and KW modes. AES-CTR encrypt/decrypt and AES-KW key wrapping/unwrapping support will land in a later release.
+* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+* Errors on script upload will now be properly reported for module-based scripts, instead of appearing as a ReferenceError.
+* WebCrypto: Key derivation for ECDH.
+* WebCrypto: Support ECDH key generation & import.
+* WebCrypto: Support ECDSA key generation.
+* Fixed bug where `crypto.subtle.encrypt()` on zero-length inputs would sometimes throw an exception.
+* Improved exception messages thrown by the WebCrypto API somewhat.
+* `waitUntil` is now supported for module Workers. An additional argument called ‘ctx’ is passed after ‘env’, and `waitUntil` is a method on ‘ctx’.
+* `passThroughOnException` is now available under the ctx argument to module handlers
+* Reliability improvements for Durable Objects
+* Reliability improvements for Durable Objects persistent storage API
+* `ScheduledEvent.cron` is now set to the original cron string that the event was scheduled for.
 
 ## 2021-03-26
 
 Changes this week:
 
-- Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
+* Existing WebSocket connections to Durable Objects will now be forcibly disconnected on code updates, in order to force clients to connect to the instance running the new code.
 
 ## 2021-03-11
 
 New this week:
 
-- When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
+* When the Workers Runtime itself reloads due to us deploying a new version or config change, we now preload high-traffic Workers in the new instance of the runtime before traffic cuts over. This ensures that users do not observe cold starts for these Workers due to the upgrade, and also fixes a low rate of spurious 503 errors that we had previously been seeing due to overload during such reloads.
 
 (It looks like no release notes were posted the last few weeks, but there were no new user-visible changes to report.)
 
@@ -391,56 +391,56 @@ New this week:
 
 Changes this week:
 
-- In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
-- A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
+* In the preview mode of the dashboard, a Worker that fails during startup will now return a 500 response, rather than getting the default passthrough behavior, which was making it harder to notice when a Worker was failing.
+* A Durable Object’s ID is now provided to it in its constructor. It can be accessed off of the `state` provided as the constructor’s first argument, as in `state.id`.
 
 ## 2021-02-05
 
 New this week:
 
-- V8 has been updated from 8.8 to 8.9.
-- During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
+* V8 has been updated from 8.8 to 8.9.
+* During a `fetch()`, if the destination server commits certain HTTP protocol errors, such as returning invalid (unparsable) headers, we now throw an exception whose description explains the problem, rather than an “internal error”.
 
 New last week (forgot to post):
 
-- Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
+* Added support for `waitUntil()` in Durable Objects. It is a method on the state object passed to the Durable Object class’s constructor.
 
 ## 2021-01-22
 
 New in the past week:
 
-- Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
+* Fixed a bug which caused scripts with WebAssembly modules to hang when using devtools in the preview service.
 
 ## 2021-01-14
 
 Changes this week:
 
-- Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
+* Implemented File and Blob APIs, which can be used when constructing FormData in outgoing requests. Unfortunately, FormData from incoming requests at this time will still use strings even when file metadata was present, in order to avoid breaking existing deployed Workers. We will find a way to fix that in the future.
 
 ## 2021-01-07
 
 Changes this week:
 
-- No user-visible changes.
+* No user-visible changes.
 
 Changes in the prior release:
 
-- Fixed delivery of WebSocket “error” events.
-- Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
+* Fixed delivery of WebSocket “error” events.
+* Fixed a rare bug where a WritableStream could be garbage collected while it still had writes queued, causing those writes to be lost.
 
 ## 2020-12-10
 
 Changes this week:
 
-- Major V8 update: 8.7.220.29 -> 8.8.278.8
+* Major V8 update: 8.7.220.29 -> 8.8.278.8
 
 ## 2019-09-19
 
 Changes this week:
 
-- Unannounced new feature. (Stay tuned.)
-- Enforced new limit on concurrent subrequests (see below).
-- Stability improvements.
+* Unannounced new feature. (Stay tuned.)
+* Enforced new limit on concurrent subrequests (see below).
+* Stability improvements.
 
 **Concurrent Subrequest Limit**
 
@@ -472,129 +472,129 @@ We chose the limit of 6 concurrent connections based on the fact that Chrome enf
 
 Changes this week:
 
-- Durable Objects storage API now supports listing keys by prefix.
-- Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
-- `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
-- Fixed off-by-one line numbers in Worker exceptions.
-- Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
-- Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
+* Durable Objects storage API now supports listing keys by prefix.
+* Improved error message when a single request performs more than 1000 KV operations to make clear that a per-request limit was reached, not a global rate limit.
+* `wrangler dev` previews should now honor non-default resource limits, for example, longer CPU limits for those in the Workers Unbound beta.
+* Fixed off-by-one line numbers in Worker exceptions.
+* Exceptions thrown in a Durable Object’s `fetch()` method are now tunneled to its caller.
+* Fixed a bug where a large Durable Object response body could cause the Durable Object to become unresponsive.
 
 ## 2020-11-13
 
 Changes over the past week:
 
-- `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
-- Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
+* `ReadableStream.cancel()` and `ReadableStream.getReader().cancel()` now take an optional, instead of a mandatory, argument, to conform with the Streams spec.
+* Fixed an error that occurred when a WASM module declared that it wanted to grow larger than 128MB. Instead, the actual memory usage of the module is monitored and an error is thrown if it exceeds 128MB used.
 
 ## 2020-11-05
 
 Changes this week:
 
-- Major V8 update: 8.6 -> 8.7
-- Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
+* Major V8 update: 8.6 -> 8.7
+* Limit the maximum number of Durable Objects keys that can be changed in a single transaction to 128.
 
 ## 2020-10-05
 
 We had our usual weekly release last week, but:
 
-- No user-visible changes.
+* No user-visible changes.
 
 ## 2020-09-24
 
 Changes this week:
 
-- Internal changes to support upcoming features.
+* Internal changes to support upcoming features.
 
 Also, a change from the 2020-09-08 release that it seems we forgot to post:
 
-- V8 major update: 8.5 -> 8.6
+* V8 major update: 8.5 -> 8.6
 
 ## 2020-08-03
 
 Changes last week:
 
-- Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
-- Upgraded V8 from 8.4 to 8.5.
+* Fixed a regression which could cause `HTMLRewriter.transform()` to throw spurious “The parser has stopped.” errors.
+* Upgraded V8 from 8.4 to 8.5.
 
 ## 2020-07-09
 
 Changes this week:
 
-- Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
-- Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
+* Fixed a regression in HTMLRewriter: [https://github.com/cloudflare/lol-html/issues/50](https://github.com/cloudflare/lol-html/issues/50)
+* Common HTTP method names passed to `fetch()` or `new Request()` are now case-insensitive as required by the Fetch API spec.
 
 Changes last week (… forgot to post):
 
-- `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
+* `setTimeout`/`setInterval` can now take additional arguments which will be passed on to the callback, as required by the spec. (Few people use this feature today because it’s usually much easier to use lambda captures.)
 
 Changes the week before last (… also… forgot to post… we really need to code up a bot for this):
 
-- The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
+* The HTMLRewriter now supports the `:nth-child` , `:first-child` , `:nth-of-type` , and `:first-of-type` selectors.
 
 ## 2020-05-15
 
 Changes this week:
 
-- Implemented API for yet-to-be-announced new feature.
+* Implemented API for yet-to-be-announced new feature.
 
 ## 2020-04-20
 
 Looks like we forgot to post release notes for a couple weeks. Releases still are happening weekly as always, but the “post to the community” step is insufficiently automated…
 4/2 release:
 
-- Fixed a source of long garbage collection paused in memory limit enforcement.
+* Fixed a source of long garbage collection paused in memory limit enforcement.
 
 4/9 release:
 
-- No publicly-visible changes.
+* No publicly-visible changes.
 
 4/16 release:
 
-- In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
+* In preview, we now log a warning when attempting to construct a `Request` or `Response` whose body is of type `FormData` but with the `Content-Type` header overridden. Such bodies would not be parseable by the receiver.
 
 ## 2020-03-26
 
 New this week:
 
-- Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
+* Certain “internal errors” that could be thrown when using the Cache API are now reported with human-friendly error messages. For example, `caches.default.match("not a URL")` now throws a TypeError.
 
 ## 2020-02-28
 
 New from the past two weeks:
 
-- Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
-- Major V8 update: 8.0 -> 8.1
-- Minor bug fixes.
+* Fixed a bug in the preview service where the CPU time limiter was overly lenient for the first several requests handled by a newly-started worker. The same bug actually exists in production as well, but we are much more cautious about fixing it there, since doing so might break live sites. If you find your worker now exceeds CPU time limits in preview, then it is likely exceeding time limits in production as well, but only appearing to work because the limits are too lenient for the first few requests. Such Workers will eventually fail in production, too (and always have), so it is best to fix the problem in preview before deploying.
+* Major V8 update: 8.0 -> 8.1
+* Minor bug fixes.
 
 ## 2020-02-13
 
 Changes over the last couple weeks:
 
-- Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
-- Performance and stability improvements.
+* Fixed a bug where if two differently-named scripts within the same account had identical content and were deployed to the same zone, they would be treated as the “same Worker”, meaning they would share the same isolate and global variables. This only applied between Workers on the same zone, so was not a security threat, but it caused confusion. Now, two differently-named Worker scripts will never be considered the same Worker even if they have identical content.
+* Performance and stability improvements.
 
 ## 2020-01-24
 
 It has been a while since we posted release notes, partly due to the holidays. Here is what is new over the past month:
 
-- Performance and stability improvements.
-- A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
-- Updated V8 7.9 -> 8.0.
+* Performance and stability improvements.
+* A rare source of `daemonDown` errors when processing bursty traffic over HTTP/2 has been eliminated.
+* Updated V8 7.9 -> 8.0.
 
 ## 2019-12-12
 
 New this week:
 
-- We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
-- Fixed a significant source of daemonDown (1105) errors.
+* We now pass correct line and column numbers more often when reporting exceptions to the V8 inspector. There remain some cases where the reported line and column numbers will be wrong.
+* Fixed a significant source of daemonDown (1105) errors.
 
 ## 2019-12-06
 
 Runtime release notes covering the past few weeks:
 
-- Increased total per-request `Cache.put()` limit to 5GiB.
-- Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
-- Added a helpful error message explaining AES decryption failures.
-- Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
-- More “internal errors” were converted to useful user-facing errors.
-- Stability improvements and bug fixes.
+* Increased total per-request `Cache.put()` limit to 5GiB.
+* Increased individual `Cache.put()` limits to the lesser of 5GiB or the zone’s normal [cache limits](/cache/concepts/default-cache-behavior/).
+* Added a helpful error message explaining AES decryption failures.
+* Some overload errors were erroneously being reported as daemonDown (1105) errors. They have been changed to exceededCpu (1102) errors, which better describes their cause.
+* More “internal errors” were converted to useful user-facing errors.
+* Stability improvements and bug fixes.
diff --git a/src/content/docs/workers/platform/changelog/index.mdx b/src/content/docs/workers/platform/changelog/index.mdx
index dd80529874c454a..c4945fcbdae6f6c 100644
--- a/src/content/docs/workers/platform/changelog/index.mdx
+++ b/src/content/docs/workers/platform/changelog/index.mdx
@@ -17,7 +17,7 @@ import { ProductReleaseNotes } from "~/components";
 
 This changelog details meaningful changes made to Workers across the Cloudflare dashboard, Wrangler, the API, and the workerd runtime. These changes are not configurable.
 
-This is _different_ from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
+This is *different* from [compatibility dates](/workers/configuration/compatibility-dates/) and [compatibility flags](/workers/configuration/compatibility-flags/), which let you explicitly opt-in to or opt-out of specific changes to the Workers Runtime.
 
 {/* <!-- Actual content lives in /src/content/release-notes/workers.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx
index 38a84a62e234adb..7e4e69499728faa 100644
--- a/src/content/docs/workers/platform/known-issues.mdx
+++ b/src/content/docs/workers/platform/known-issues.mdx
@@ -14,7 +14,7 @@ Below are some known bugs and issues to be aware of when using Cloudflare Worker
 
 ## Route specificity
 
-- When defining route specificity, a trailing `/*` in your pattern may not act as expected.
+* When defining route specificity, a trailing `/*` in your pattern may not act as expected.
 
 Consider two different Workers, each deployed to the same zone. Worker A is assigned the `example.com/images/*` route and Worker B is given the `example.com/images*` route pattern. With these in place, here are how the following URLs will be resolved:
 
@@ -44,11 +44,11 @@ When adding a wildcard on a subdomain, here are how the following URLs will be r
 
 ## wrangler dev
 
-- When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
+* When running `wrangler dev --remote`, all outgoing requests are given the `cf-workers-preview-token` header, which Cloudflare recognizes as a preview request. This applies to the entire Cloudflare network, so making HTTP requests to other Cloudflare zones is currently discarded for security reasons. To enable a workaround, insert the following code into your Worker script:
 
 ```js
 const request = new Request(url, incomingRequest);
-request.headers.delete("cf-workers-preview-token");
+request.headers.delete('cf-workers-preview-token');
 return await fetch(request);
 ```
 
@@ -90,11 +90,11 @@ For Workers subrequests, requests can only be made to URLs, not to IP addresses
 For example, in the zone `example.com` create a record of type `A` with the name `server` and value `192.0.2.1`, and then use:
 
 ```js
-await fetch("http://server.example.com");
+await fetch('http://server.example.com')
 ```
 
 Do not use:
 
 ```js
-await fetch("http://192.0.2.1");
+await fetch('http://192.0.2.1')
 ```
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
index 929570df6454101..d306aaec2558390 100644
--- a/src/content/docs/workers/platform/pricing.mdx
+++ b/src/content/docs/workers/platform/pricing.mdx
@@ -27,9 +27,9 @@ All [Pages Functions](/pages/functions/) are billed as Workers. All pricing and
 
 Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, contact your Account Manager.
 
-|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                      |
+|              | Requests<sup>1, 2, 3</sup>                                         | Duration                        | CPU time                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------ | ------------------------------------------------------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Free**     | 100,000 per day                                                    | No charge for duration          | 10 milliseconds of CPU time per invocation                                                                                                                                                                                                                                                                                                                                                                |
 | **Standard** | 10 million included per month <br /> +$0.30 per additional million | No charge or limit for duration | 30 million CPU milliseconds included per month<br /> +$0.02 per additional million CPU milliseconds<br /><br/> Max of [5 minutes of CPU time](/workers/platform/limits/#account-plan-limits) per invocation (default: 30 seconds)<br /> Max of 15 minutes of CPU time per [Cron Trigger](/workers/configuration/cron-triggers/) or [Queue Consumer](/queues/configuration/javascript-apis/#consumer) invocation |
 
 <sup>1</sup> Inbound requests to your Worker. Cloudflare does not bill for
diff --git a/src/content/docs/workers/reference/how-the-cache-works.mdx b/src/content/docs/workers/reference/how-the-cache-works.mdx
index fb3c5d8662710f6..53aad4dd28b3f81 100644
--- a/src/content/docs/workers/reference/how-the-cache-works.mdx
+++ b/src/content/docs/workers/reference/how-the-cache-works.mdx
@@ -17,9 +17,11 @@ Cloudflare Workers run before the cache but can also be utilized to modify asset
 Conceptually, there are two ways to interact with Cloudflare’s Cache using a Worker:
 
 - Call to [`fetch()`](/workers/runtime-apis/fetch/) in a Workers script. Requests proxied through Cloudflare are cached even without Workers according to a zone’s default or configured behavior (for example, static assets like files ending in `.jpg` are cached by default). Workers can further customize this behavior by:
+
   - Setting Cloudflare cache rules (that is, operating on the `cf` object of a [request](/workers/runtime-apis/request/)).
 
 - Store responses using the [Cache API](/workers/runtime-apis/cache/) from a Workers script. This allows caching responses that did not come from an origin and also provides finer control by:
+
   - Customizing cache behavior of any asset by setting headers such as `Cache-Control` on the response passed to `cache.put()`.
 
   - Caching responses generated by the Worker itself through `cache.put()`.
@@ -60,9 +62,11 @@ A("You have a Worker script that runs on <code>https://</code><code>example.com/
 Assets stored in the cache through [Cache API](/workers/runtime-apis/cache/) operations can be purged in a couple of ways:
 
 - Call `cache.delete` within a Worker to invalidate the cache for the asset with a matching request variable.
+
   - Assets purged in this way are only purged locally to the data center the Worker runtime was executed.
 
 - To purge an asset globally, use the standard [cache purge options](/cache/how-to/purge-cache/). Based on cache API implementation, not all cache purge endpoints function for purging assets stored by the Cache API.
+
   - All assets on a zone can be purged by using the [Purge Everything](/cache/how-to/purge-cache/purge-everything/) cache operation. This purge will remove all assets associated with a Cloudflare zone from cache in all data centers regardless of the method set.
 
   - [Cache Tags](/cache/how-to/purge-cache/purge-by-tags/#add-cache-tag-http-response-headers) can be added to requests dynamically in a Worker by calling `response.headers.append()` and appending `Cache-Tag` values dynamically to that request. Once set, those tags can be used to selectively purge assets from cache without invalidating all cached assets on a zone.
diff --git a/src/content/docs/workers/reference/how-workers-works.mdx b/src/content/docs/workers/reference/how-workers-works.mdx
index 8d93ed5dfa09491..4a44795d4bf2054 100644
--- a/src/content/docs/workers/reference/how-workers-works.mdx
+++ b/src/content/docs/workers/reference/how-workers-works.mdx
@@ -9,7 +9,7 @@ products:
   - workers
 ---
 
-import { Render, WorkersIsolateDiagram } from "~/components";
+import { Render, WorkersIsolateDiagram } from "~/components"
 
 Though Cloudflare Workers behave similarly to [JavaScript](https://www.cloudflare.com/learning/serverless/serverless-javascript/) in the browser or in Node.js, there are a few differences in how you have to think about your code. Under the hood, the Workers runtime uses the [V8 engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/) — the same engine used by Chromium and Node.js. The Workers runtime also implements many of the standard [APIs](/workers/runtime-apis/) available in most modern browsers.
 
@@ -27,13 +27,13 @@ The three largest differences are: Isolates, Compute per Request, and Distribute
 
 <Render file="isolate-description" product="workers" />
 
-<WorkersIsolateDiagram />
+<WorkersIsolateDiagram/>
 
 A given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons:
 
-- Resource limitations on the machine.
-- A suspicious script - anything seen as trying to break out of the isolate sandbox.
-- Individual [resource limits](/workers/platform/limits/).
+* Resource limitations on the machine.
+* A suspicious script - anything seen as trying to break out of the isolate sandbox.
+* Individual [resource limits](/workers/platform/limits/).
 
 Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingency.
 
@@ -52,6 +52,6 @@ Because there is no guarantee that any two user requests will be routed to the s
 
 ## Related resources
 
-- [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
-- [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
-- [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
+* [`fetch()` handler](/workers/runtime-apis/handlers/fetch/) - Review how incoming HTTP requests to a Worker are passed to the `fetch()` handler.
+* [Request](/workers/runtime-apis/request/) - Learn how incoming HTTP requests are passed to the `fetch()` handler.
+* [Workers limits](/workers/platform/limits/) - Learn about Workers limits including Worker size, startup time, and more.
diff --git a/src/content/docs/workers/reference/protocols.mdx b/src/content/docs/workers/reference/protocols.mdx
index bd089af6329ec22..fe7f15baf21e464 100644
--- a/src/content/docs/workers/reference/protocols.mdx
+++ b/src/content/docs/workers/reference/protocols.mdx
@@ -10,10 +10,10 @@ products:
 
 Cloudflare Workers support the following protocols and interfaces:
 
-| Protocol               | Inbound                                                                                                                                                                                                                                                                                                         | Outbound                                                                                        |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                              | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                   |
-| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                            | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/) |
-| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                                                                                                            |                                                                                                 |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                 |
-| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                 | [Email Workers](/email-routing/email-workers/)                                                  |
+| Protocol               | Inbound                                                                                                                                                                                                                                                                                                          | Outbound                                                                                                     |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| **HTTP / HTTPS**       | Handle incoming HTTP requests using the [`fetch()` handler](/workers/runtime-apis/handlers/fetch/)                                                                                                                                                                                                               | Make HTTP subrequests using the [`fetch()` API](/workers/runtime-apis/fetch/)                                |
+| **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
+| **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/)                                                                                                                           |                                     |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
+| **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |
diff --git a/src/content/docs/workers/reference/security-model.mdx b/src/content/docs/workers/reference/security-model.mdx
index d79f5a740d88d0d..f45407e36b6b093 100644
--- a/src/content/docs/workers/reference/security-model.mdx
+++ b/src/content/docs/workers/reference/security-model.mdx
@@ -7,7 +7,7 @@ products:
   - workers
 ---
 
-import { WorkersArchitectureDiagram } from "~/components";
+import { WorkersArchitectureDiagram } from "~/components"
 
 This article includes an overview of Cloudflare security architecture, and then addresses two frequently asked about issues: V8 bugs and Spectre.
 
@@ -25,7 +25,7 @@ For more details, refer to [this talk](https://www.infoq.com/presentations/cloud
 
 Beginning with a quick overview of the Workers runtime architecture:
 
-<WorkersArchitectureDiagram />
+<WorkersArchitectureDiagram/>
 
 There are two fundamental parts of designing a code sandbox: secure isolation and API design.
 
@@ -172,7 +172,7 @@ In Workers, you can get the current time using the JavaScript Date API by callin
 ```js
 let start = Date.now();
 for (let i = 0; i < 1e6; i++) {
-	doSpectreAttack();
+  doSpectreAttack();
 }
 let end = Date.now();
 ```
diff --git a/src/content/docs/workers/runtime-apis/bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/index.mdx
index c395b7d9593aa09..a1b72465e91fb65 100644
--- a/src/content/docs/workers/runtime-apis/bindings/index.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/index.mdx
@@ -121,37 +121,38 @@ Bindings are located on the `env` object, which can be accessed in several ways:
   [DurableObject](/durable-objects/), and [Workflow](/workflows/):
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-    ```js
-    export class MyDurableObject extends DurableObject {
-    	async sayHello() {
-    		return `Hi, ${this.env.NAME}!`;
-    	}
-    }
-    ```
-    </TabItem> <TabItem label="Python" icon="seti:python">
-    ```python
-    from workers import WorkerEntrypoint, Response
-  
-    class Default(WorkerEntrypoint):
-    	async def fetch(self, request):
-    		return Response(f"Hi {self.env.NAME}")
-    ```
-    </TabItem></Tabs>
+  ```js
+  export class MyDurableObject extends DurableObject {
+  	async sayHello() {
+  		return `Hi, ${this.env.NAME}!`;
+  	}
+  }
+  ```
+  </TabItem> <TabItem label="Python" icon="seti:python">
+  ```python
+  from workers import WorkerEntrypoint, Response
+
+  class Default(WorkerEntrypoint):
+  	async def fetch(self, request):
+  		return Response(f"Hi {self.env.NAME}")
+  ```
+  </TabItem></Tabs>
+
 
 * It can be imported from `cloudflare:workers`:
 
   <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
-    ```js
-    import { env } from "cloudflare:workers";
-    console.log(`Hi, ${env.Name}`);
-    ```
-    </TabItem> <TabItem label="Python" icon="seti:python">
-    ```python
-    from workers import import_from_javascript
-    env = import_from_javascript("cloudflare:workers").env
-    print(f"Hi, {env.NAME}")
-    ```
-    </TabItem></Tabs>
+  ```js
+  import { env } from "cloudflare:workers";
+  console.log(`Hi, ${env.Name}`);
+  ```
+  </TabItem> <TabItem label="Python" icon="seti:python">
+  ```python
+  from workers import import_from_javascript
+  env = import_from_javascript("cloudflare:workers").env
+  print(f"Hi, {env.NAME}")
+  ```
+  </TabItem></Tabs>
 
 ### Importing `env` as a global
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
index 6354459443f42ff..90cbad356d0ff57 100644
--- a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx
@@ -6,16 +6,16 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components";
+import { TabItem, Tabs, WranglerConfig } from "~/components"
 
 The Rate Limiting API lets you define rate limits and write code around them in your Worker.
 
 You can use it to enforce:
 
-- Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
-- Different rate limits for different types of customers or users (ex: free vs. paid)
-- Resource-specific or path-specific limits (ex: limit per API route)
-- Any combination of the above
+* Rate limits that are applied after your Worker starts, only once a specific part of your code is reached
+* Different rate limits for different types of customers or users (ex: free vs. paid)
+* Resource-specific or path-specific limits (ex: limit per API route)
+* Any combination of the above
 
 The Rate Limiting API is backed by the same infrastructure that serves [rate limiting rules](/waf/rate-limiting-rules/).
 
@@ -96,13 +96,15 @@ export default {
 
 The `limit()` API accepts a single argument — a configuration object with the `key` field.
 
-- The key you provide can be any `string` value.
-- A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
+* The key you provide can be any `string` value.
+* A common pattern is to define your key by combining a string that uniquely identifies the actor initiating the request (ex: a user ID or customer ID) and a string that identifies a specific resource (ex: a particular API route).
 
 You can define and configure multiple rate limiting configurations per Worker, which allows you to define different limits against incoming request and/or user parameters as needed to protect your application or upstream APIs.
 
 For example, here is how you can define two rate limiting configurations for free and paid tier users:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -137,12 +139,12 @@ For example, here is how you can define two rate limiting configurations for fre
 
 A rate limiting binding has the following settings:
 
-| Setting         | Type     | Description                                                                                                                                                                                                                                     |
-| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `namespace_id`  | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
-| `simple`        | `object` | The rate limit configuration. `simple` is the only supported type.                                                                                                                                                                              |
-| `simple.limit`  | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`.                                                                                                                                                               |
-| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`.                                                                                                                                                                 |
+| Setting | Type | Description |
+| --- | --- | --- |
+| `namespace_id` | `string` | A string containing a positive integer that uniquely defines this rate limiting namespace within your Cloudflare account (for example, `"1001"`). Although the value must be a valid integer, it is specified as a string. This is intentional. |
+| `simple` | `object` | The rate limit configuration. `simple` is the only supported type. |
+| `simple.limit` | `number` | The number of allowed requests (or calls to `limit()`) within the given `period`. |
+| `simple.period` | `number` | The duration of the rate limit window, in seconds. Must be either `10` or `60`. |
 
 :::note
 Two rate limiting bindings that share the same `namespace_id` — even across different Workers on the same account — share the same rate limit counters for a given key. This is intentional and allows you to enforce a single rate limit across multiple Workers.
@@ -176,19 +178,19 @@ For example, to apply a rate limit of 1500 requests per minute, you would define
 
 The `key` passed to the `limit` function, that determines what to rate limit on, should represent a unique characteristic of a user or class of user that you wish to rate limit.
 
-- Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
-- It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
+* Good choices include API keys in `Authorization` HTTP headers, URL paths or routes, specific query parameters used by your application, and/or user IDs and tenant IDs. These are all stable identifiers and are unlikely to change from request-to-request.
+* It is not recommended to use IP addresses or locations (regions or countries), since these can be shared by many users in many valid cases. You may find yourself unintentionally rate limiting a wider group of users than you intended by rate limiting on these keys.
 
 ```ts
 // Recommended: use a key that represents a specific user or class of user
-const url = new URL(req.url);
-const userId = url.searchParams.get("userId") || "";
-const { success } = await env.MY_RATE_LIMITER.limit({ key: userId });
+const url = new URL(req.url)
+const userId = url.searchParams.get("userId") || ""
+const { success } = await env.MY_RATE_LIMITER.limit({ key: userId })
 
 // Not recommended:  many users may share a single IP, especially on mobile networks
 // or when using privacy-enabling proxies
-const ipAddress = req.headers.get("cf-connecting-ip") || "";
-const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress });
+const ipAddress = req.headers.get("cf-connecting-ip") || ""
+const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })
 ```
 
 ## Locality
@@ -206,7 +208,7 @@ The underlying counters are cached on the same machine that your Worker runs in,
 This means that while in your code you `await` a call to the `limit()` method:
 
 ```javascript
-const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId });
+const { success } = await env.MY_RATE_LIMITER.limit({ key: customerId })
 ```
 
 You are not waiting on a network request. You can use the Rate Limiting API without introducing any meaningful latency to your Worker.
@@ -221,11 +223,11 @@ For example, if many requests come in to your Worker in a single Cloudflare loca
 
 Rate limiting bindings are not currently visible in the Cloudflare dashboard. To monitor rate-limited requests from your Worker:
 
-- **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
-- **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
+* **[Workers Observability](/workers/observability/)** — Use [Workers Logs](/workers/observability/logs/workers-logs/) and [Traces](/workers/observability/traces/) to observe HTTP 429 responses returned by your Worker when rate limits are exceeded.
+* **[Workers Analytics Engine](/analytics/analytics-engine/)** — Add an Analytics Engine binding to your Worker and emit custom data points (for example, a `rate_limited` event) when `limit()` returns `{ success: false }`. This lets you build dashboards and query rate limiting metrics over time.
 
 ## Examples
 
-- [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
-- [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
-- [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
+* [`@elithrar/workers-hono-rate-limit`](https://github.com/elithrar/workers-hono-rate-limit) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application.
+* [`@hono-rate-limiter/cloudflare`](https://github.com/rhinobase/hono-rate-limiter) — Middleware that lets you easily add rate limits to routes in your [Hono](https://hono.dev/) application, with multiple data stores to choose from.
+* [`hono-cf-rate-limit`](https://github.com/bytaesu/hono-cf-rate-limit) — Middleware for Hono applications that applies rate limiting in Cloudflare Workers, powered by Wrangler’s built-in features.
diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
index 153b3d20f4de2f8..a30129269dd55d9 100644
--- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/http.mdx
@@ -30,14 +30,16 @@ For example, consider the following Worker that implements a [`fetch()` handler]
 
 ```js
 export default {
-	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
-	},
-};
+  async fetch(request, env, ctx) {
+    return new Response("Hello World!");
+  }
+}
 ```
 
 The following Worker declares a binding to the Worker above:
 
+
+
 <WranglerConfig>
 
 ```jsonc
@@ -72,12 +74,12 @@ If you construct a new request manually, rather than forwarding an existing one,
 
 ```js
 export default {
-	async fetch(request, env) {
-		// provide a valid URL
-		let newRequest = new Request("https://valid-url.com", { method: "GET" });
-		let response = await env.WORKER_B.fetch(newRequest);
-		return response;
-	},
+  async fetch(request, env) {
+    // provide a valid URL
+    let newRequest = new Request("https://valid-url.com", { method: "GET" });
+    let response = await env.WORKER_B.fetch(newRequest);
+    return response;
+  }
 };
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/bindings/stream.mdx b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
index f07806aa6308be8..8614dfafc2d517e 100644
--- a/src/content/docs/workers/runtime-apis/bindings/stream.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/stream.mdx
@@ -4,4 +4,5 @@ title: Stream
 external_link: /stream/manage-video-library/bindings/
 head: []
 description: Upload, manage, and deliver video with Cloudflare Stream.
+
 ---
diff --git a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
index f6647c550ce60aa..53634f635526565 100644
--- a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
+++ b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx
@@ -15,7 +15,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs, WranglerConfig } from "~/components";
+import { TabItem, Tabs, WranglerConfig } from "~/components"
 
 The version metadata binding can be used to access metadata associated with a [version](/workers/configuration/versions-and-deployments/#versions) from inside the Workers runtime.
 
diff --git a/src/content/docs/workers/runtime-apis/cache.mdx b/src/content/docs/workers/runtime-apis/cache.mdx
index 6347b07bd87cc61..cc26647ff0a0df2 100644
--- a/src/content/docs/workers/runtime-apis/cache.mdx
+++ b/src/content/docs/workers/runtime-apis/cache.mdx
@@ -30,7 +30,7 @@ This individualized zone cache object differs from Cloudflare’s Global CDN. Fo
 
 :::
 
----
+***
 
 ## Accessing Cache
 
@@ -44,7 +44,7 @@ await cache.match(request);
 You may create and manage additional Cache instances via the [`caches.open`](https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage/open) method.
 
 ```js
-let myCache = await caches.open("custom:cache");
+let myCache = await caches.open('custom:cache');
 await myCache.match(request);
 ```
 
@@ -56,28 +56,28 @@ When using the cache API, avoid overriding the hostname in cache requests, as th
 // recommended approach: use your Worker hostname to ensure efficient caching
 request.url = "https://your-Worker-hostname.com/";
 
-let myCache = await caches.open("custom:cache");
+let myCache = await caches.open('custom:cache');
 let response = await myCache.match(request);
 ```
 
 :::
 
----
+***
 
 ## Headers
 
 Our implementation of the Cache API respects the following HTTP headers on the response passed to `put()`:
 
-- `Cache-Control`
-  - Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
-- `Cache-Tag`
-  - Allows resource purging by tag(s) later.
-- `ETag`
-  - Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
-- `Expires` string
-  - A string that specifies when the resource becomes invalid.
-- `Last-Modified`
-  - Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
+* `Cache-Control`
+  * Controls caching directives. This is consistent with [Cloudflare Cache-Control Directives](/cache/concepts/cache-control#cache-control-directives). Refer to [Edge TTL](/cache/how-to/configure-cache-status-code#edge-ttl) for a list of HTTP response codes and their TTL when `Cache-Control` directives are not present.
+* `Cache-Tag`
+  * Allows resource purging by tag(s) later.
+* `ETag`
+  * Allows `cache.match()` to evaluate conditional requests with `If-None-Match`.
+* `Expires` string
+  * A string that specifies when the resource becomes invalid.
+* `Last-Modified`
+  * Allows `cache.match()` to evaluate conditional requests with `If-Modified-Since`.
 
 This differs from the web browser Cache API as they do not honor any headers on the request or response.
 
@@ -89,7 +89,7 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 
 :::
 
----
+***
 
 ## Methods
 
@@ -99,8 +99,9 @@ Use the `Cache-Control` method to store the response without the `Set-Cookie` he
 cache.put(request, response);
 ```
 
-- <code>put(request, response)</code> : Promise
-  - Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
+* <code>put(request, response)</code> : Promise
+
+  * Attempts to add a response to the cache, using the given request as the key. Returns a promise that resolves to `undefined` regardless of whether the cache successfully stored the response.
 
 :::note
 
@@ -110,19 +111,20 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 
 #### Parameters
 
-- `request` string | Request
-  - Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
+* `request` string | Request
 
-- `response` Response
-  - A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
+  * Either a string or a [`Request`](/workers/runtime-apis/request/) object to serve as the key. If a string is passed, it is interpreted as the URL for a new Request object.
+
+* `response` Response
+  * A [`Response`](/workers/runtime-apis/response/) object to store under the given key.
 
 #### Invalid parameters
 
 `cache.put` will throw an error if:
 
-- The `request` passed is a method other than `GET`.
-- The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
-- The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
+* The `request` passed is a method other than `GET`.
+* The `response` passed has a `status` of [`206 Partial Content`](https://www.webfx.com/web-development/glossary/http-status-codes/what-is-a-206-status-code/).
+* The `response` passed contains the header `Vary: *`. The value of the `Vary` header is an asterisk (`*`). Refer to the [Cache API specification](https://w3c.github.io/ServiceWorker/#cache-put) for more information.
 
 #### Errors
 
@@ -134,34 +136,40 @@ The `stale-while-revalidate` and `stale-if-error` directives are not supported w
 cache.match(request, options);
 ```
 
-- <code>match(request, options)</code> : Promise`<Response | undefined>`
-  - Returns a promise wrapping the response object keyed to that request.
+* <code>match(request, options)</code> : Promise`<Response | undefined>`
+
+  * Returns a promise wrapping the response object keyed to that request.
 
 :::note
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
 :::
 
+
 #### Parameters
 
-- `request` string | Request
-  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+* `request` string | Request
 
-- `options`
-  - Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
+  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+
+* `options`
+  * Can contain one possible property: `ignoreMethod` (Boolean). When `true`, the request is considered to be a `GET` request regardless of its actual value.
 
 Unlike the browser Cache API, Cloudflare Workers do not support the `ignoreSearch` or `ignoreVary` options on `match()`. You can accomplish this behavior by removing query strings or HTTP headers at `put()` time.
 
 Our implementation of the Cache API respects the following HTTP headers on the request passed to `match()`:
 
-- `Range`
-  - Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
+* `Range`
+
+  * Results in a `206` response if a matching response with a Content-Length header is found. Your Cloudflare cache always respects range requests, even if an `Accept-Ranges` header is on the response.
+
+* `If-Modified-Since`
 
-- `If-Modified-Since`
-  - Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
+  * Results in a `304` response if a matching response is found with a `Last-Modified` header with a value before the time specified in `If-Modified-Since`.
 
-- `If-None-Match`
-  - Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
+* `If-None-Match`
+
+  * Results in a `304` response if a matching response is found with an `ETag` header with a value that matches a value in `If-None-Match`.
 
 :::note
 
@@ -180,12 +188,12 @@ If you use Cloudflare Logs, you may see these `504` responses with the `RequestS
 cache.delete(request, options);
 ```
 
-- <code>delete(request, options)</code> : Promise`<boolean>`
+* <code>delete(request, options)</code> : Promise`<boolean>`
 
 Deletes the `Response` object from the cache and returns a `Promise` for a Boolean response:
 
-- `true`: The response was cached but is now deleted
-- `false`: The response was not in the cache at the time of deletion.
+* `true`: The response was cached but is now deleted
+* `false`: The response was not in the cache at the time of deletion.
 
 :::caution[Global purges]
 
@@ -195,17 +203,18 @@ The `cache.delete` method only purges content of the cache in the data center th
 
 #### Parameters
 
-- `request` string | Request
-  - The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
+* `request` string | Request
 
-- `options` object
-  - Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+  * The string or [`Request`](/workers/runtime-apis/request/) object used as the lookup key. Strings are interpreted as the URL for a new `Request` object.
 
----
+* `options` object
+  * Can contain one possible property: `ignoreMethod` (Boolean). Consider the request method a GET regardless of its actual value.
+
+***
 
 ## Related resources
 
-- [How the cache works](/workers/reference/how-the-cache-works/)
-- [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
-- [Example: using the Cache API](/workers/examples/cache-api/)
-- [Example: caching POST requests](/workers/examples/cache-post-request/)
+* [How the cache works](/workers/reference/how-the-cache-works/)
+* [Example: Cache using `fetch()`](/workers/examples/cache-using-fetch/)
+* [Example: using the Cache API](/workers/examples/cache-api/)
+* [Example: caching POST requests](/workers/examples/cache-post-request/)
diff --git a/src/content/docs/workers/runtime-apis/console.mdx b/src/content/docs/workers/runtime-apis/console.mdx
index f1861458031b416..6ed3997531c52a7 100644
--- a/src/content/docs/workers/runtime-apis/console.mdx
+++ b/src/content/docs/workers/runtime-apis/console.mdx
@@ -18,39 +18,39 @@ The table below enumerates each method, and the extent to which it is supported
 
 All methods noted as "✅ supported" have the following behavior:
 
-- They will be written to the console in local dev (`npx wrangler@latest dev`)
-- They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
-- They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
+* They will be written to the console in local dev (`npx wrangler@latest dev`)
+* They will appear in live logs, when tailing logs in the dashboard or running [`wrangler tail`](https://developers.cloudflare.com/workers/observability/log-from-workers/#use-wrangler-tail)
+* They will create entries in the `logs` field of [Tail Worker](https://developers.cloudflare.com/workers/observability/tail-workers/) events and [Workers Trace Events](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/workers_trace_events/), which can be pushed to a destination of your choice via [Logpush](https://developers.cloudflare.com/workers/observability/logpush/).
 
 All methods noted as "🟡 partial support" have the following behavior:
 
-- In both production and local development the method can be safely called, but will do nothing (no op)
-- In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
+* In both production and local development the method can be safely called, but will do nothing (no op)
+* In the [Workers Playground](https://workers.cloudflare.com/playground), Quick Editor in the Workers dashboard, and remote preview mode (`wrangler dev --remote`) calling the method will behave as expected, print to the console, etc.
 
 Refer to [Log from Workers](https://developers.cloudflare.com/workers/observability/log-from-workers/) for more on debugging and adding logs to Workers.
 
 | Method                                                                                                         | Behavior                                                                                           |
 | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                       |
-| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                       |
-| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                       |
-| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                       |
-| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                       |
+| [`console.debug()`](https://developer.mozilla.org/en-US/docs/Web/API/console/debug_static)                     | ✅ supported                                                                                        |
+| [`console.error()`](https://developer.mozilla.org/en-US/docs/Web/API/console/error_static)                     | ✅ supported                                                                                        |
+| [`console.info()`](https://developer.mozilla.org/en-US/docs/Web/API/console/info_static)                       | ✅ supported                                                                                        |
+| [`console.log()`](https://developer.mozilla.org/en-US/docs/Web/API/console/log_static)                         | ✅ supported                                                                                        |
+| [`console.warn()`](https://developer.mozilla.org/en-US/docs/Web/API/console/warn_static)                       | ✅ supported                                                                                        |
 | [`console.clear()`](https://developer.mozilla.org/en-US/docs/Web/API/console/clear_static)                     | 🟡 partial support                                                                                 |
 | [`console.count()`](https://developer.mozilla.org/en-US/docs/Web/API/console/count_static)                     | 🟡 partial support                                                                                 |
 | [`console.group()`](https://developer.mozilla.org/en-US/docs/Web/API/console/group_static)                     | 🟡 partial support                                                                                 |
 | [`console.table()`](https://developer.mozilla.org/en-US/docs/Web/API/console/table_static)                     | 🟡 partial support                                                                                 |
 | [`console.trace()`](https://developer.mozilla.org/en-US/docs/Web/API/console/trace_static)                     | 🟡 partial support                                                                                 |
-| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                           |
-| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                           |
-| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                           |
-| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                           |
-| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                           |
-| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                           |
-| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                           |
-| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                           |
-| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                           |
-| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                           |
-| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                           |
-| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                           |
+| [`console.assert()`](https://developer.mozilla.org/en-US/docs/Web/API/console/assert_static)                   | ⚪ no op                                                                                            |
+| [`console.countReset()`](https://developer.mozilla.org/en-US/docs/Web/API/console/countreset_static)           | ⚪ no op                                                                                            |
+| [`console.dir()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dir_static)                         | ⚪ no op                                                                                            |
+| [`console.dirxml()`](https://developer.mozilla.org/en-US/docs/Web/API/console/dirxml_static)                   | ⚪ no op                                                                                            |
+| [`console.groupCollapsed()`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupcollapsed_static)   | ⚪ no op                                                                                            |
+| [`console.groupEnd`](https://developer.mozilla.org/en-US/docs/Web/API/console/groupend_static)                 | ⚪ no op                                                                                            |
+| [`console.profile()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profile_static)                 | ⚪ no op                                                                                            |
+| [`console.profileEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/profileend_static)           | ⚪ no op                                                                                            |
+| [`console.time()`](https://developer.mozilla.org/en-US/docs/Web/API/console/time_static)                       | ⚪ no op                                                                                            |
+| [`console.timeEnd()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timeend_static)                 | ⚪ no op                                                                                            |
+| [`console.timeLog()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timelog_static)                 | ⚪ no op                                                                                            |
+| [`console.timeStamp()`](https://developer.mozilla.org/en-US/docs/Web/API/console/timestamp_static)             | ⚪ no op                                                                                            |
 | [`console.createTask()`](https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces) | 🔴 Will throw an exception in production, but works in local dev, Quick Editor, and remote preview |
diff --git a/src/content/docs/workers/runtime-apis/encoding.mdx b/src/content/docs/workers/runtime-apis/encoding.mdx
index 1c2d6dd741d8730..7f2f363e0232ea5 100644
--- a/src/content/docs/workers/runtime-apis/encoding.mdx
+++ b/src/content/docs/workers/runtime-apis/encoding.mdx
@@ -24,15 +24,24 @@ let encoder = new TextEncoder();
 
 ### Properties
 
-- `encoder.encoding` DOMString read-only
-  - The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
+
+
+* `encoder.encoding` DOMString read-only
+  * The name of the encoder as a string describing the method the `TextEncoder` uses (always `utf-8`).
+
+
 
 ### Methods
 
-- <code>encode(inputUSVString)</code> : Uint8Array
-  - Encodes a string input.
 
----
+
+* <code>encode(inputUSVString)</code> : Uint8Array
+
+  * Encodes a string input.
+
+
+
+***
 
 ## TextDecoder
 
@@ -50,16 +59,25 @@ let decoder = new TextDecoder();
 
 ### Properties
 
-- `decoder.encoding` DOMString read-only
-  - The name of the decoder that describes the method the `TextDecoder` uses.
 
-- `decoder.fatal` boolean read-only
-  - Indicates if the error mode is fatal.
 
-- `decoder.ignoreBOM` boolean read-only
-  - Indicates if the byte-order marker is ignored.
+* `decoder.encoding` DOMString read-only
+
+  * The name of the decoder that describes the method the `TextDecoder` uses.
+
+* `decoder.fatal` boolean read-only
+
+  * Indicates if the error mode is fatal.
+
+* `decoder.ignoreBOM` boolean read-only
+  * Indicates if the byte-order marker is ignored.
+
+
 
 ### Methods
 
-- `decode()` : DOMString
-  - Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
+
+
+* `decode()` : DOMString
+  * Decodes using the method specified in the `TextDecoder` object. Learn more at [MDN’s `TextDecoder` documentation](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder/decode).
+
diff --git a/src/content/docs/workers/runtime-apis/eventsource.mdx b/src/content/docs/workers/runtime-apis/eventsource.mdx
index e8678e44d07dd79..789989011083673 100644
--- a/src/content/docs/workers/runtime-apis/eventsource.mdx
+++ b/src/content/docs/workers/runtime-apis/eventsource.mdx
@@ -19,8 +19,12 @@ The [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource
 let eventSource = new EventSource(url, options);
 ```
 
-- `url` USVString - The URL to which to connect.
-- `options` EventSourceInit - An optional dictionary containing any optional settings.
+
+
+* `url` USVString - The URL to which to connect.
+* `options` EventSourceInit - An optional dictionary containing any optional settings.
+
+
 
 By default, the `EventSource` will use the global `fetch()` function under the
 covers to make requests. If you need to use a different fetch implementation as
@@ -28,10 +32,10 @@ provided by a Cloudflare Workers binding, you can pass the `fetcher` option:
 
 ```js
 export default {
-	async fetch(req, env) {
-		let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
-		// ...
-	},
+  async fetch(req, env) {
+    let eventSource = new EventSource(url, { fetcher: env.MYFETCHER });
+    // ...
+  }
 };
 ```
 
@@ -39,34 +43,49 @@ Note that the `fetcher` option is a Cloudflare Workers specific extension.
 
 ### Properties
 
-- `eventSource.url` USVString read-only
-  - The URL of the event source.
-- `eventSource.readyState` USVString read-only
-  - The state of the connection.
-- `eventSource.withCredentials` Boolean read-only
-  - A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
+
+
+* `eventSource.url` USVString read-only
+  * The URL of the event source.
+* `eventSource.readyState` USVString read-only
+  * The state of the connection.
+* `eventSource.withCredentials` Boolean read-only
+  * A Boolean indicating whether the `EventSource` object was instantiated with cross-origin (CORS) credentials set (`true`), or not (`false`).
+
+
 
 ### Methods
 
-- `eventSource.close()`
-  - Closes the connection.
-- `eventSource.onopen`
-  - An event handler called when a connection is opened.
-- `eventSource.onmessage`
-  - An event handler called when a message is received.
-- `eventSource.onerror`
-  - An event handler called when an error occurs.
+
+
+* `eventSource.close()`
+  * Closes the connection.
+* `eventSource.onopen`
+  * An event handler called when a connection is opened.
+* `eventSource.onmessage`
+  * An event handler called when a message is received.
+* `eventSource.onerror`
+  * An event handler called when an error occurs.
+
+
 
 ### Events
 
-- `message`
-  - Fired when a message is received.
-- `open`
-  - Fired when the connection is opened.
-- `error`
-  - Fired when an error occurs.
+
+
+* `message`
+  * Fired when a message is received.
+* `open`
+  * Fired when the connection is opened.
+* `error`
+  * Fired when an error occurs.
+
+
 
 ### Class Methods
 
-- <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
-  - This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
+
+
+* <code>EventSource.from(readableStreamReadableStream) : EventSource</code>
+  * This is a Cloudflare Workers specific extension that creates a new `EventSource` object from an existing `ReadableStream`. Such an instance does not initiate a new connection but instead attaches to the provided stream.
+
diff --git a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
index 17256889d32d9bb..afee782db35b496 100644
--- a/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/fetch.mdx
@@ -13,27 +13,36 @@ Incoming HTTP requests to a Worker are passed to the `fetch()` handler as a [`Re
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
+		return new Response('Hello World!');
 	},
 };
 ```
 
 :::note
 
+
 The Workers runtime does not support `XMLHttpRequest` (XHR). Learn the difference between `XMLHttpRequest` and `fetch()` in the [MDN](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) documentation.
 
+
 :::
 
 ### Parameters
 
-- `request` Request
-  - The incoming HTTP request.
 
-- `env` object
-  - The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
 
-- <code>ctx.waitUntil(promisePromise)</code> : void
-  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
+* `request` Request
+
+  * The incoming HTTP request.
+
+* `env` object
+
+  * The [bindings](/workers/runtime-apis/bindings/) available to the Worker. As long as the [environment](/workers/wrangler/environments/) has not changed, the same object (equal by identity) may be passed to multiple requests. You can also [import `env` from `cloudflare:workers`](/workers/runtime-apis/bindings/#importing-env-as-a-global) to access bindings from anywhere in your code.
+
+* <code>ctx.waitUntil(promisePromise)</code> : void
+
+  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil).
+
+* <code>ctx.passThroughOnException()</code> : void
+
+  * Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
 
-- <code>ctx.passThroughOnException()</code> : void
-  - Refer to [`passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception).
diff --git a/src/content/docs/workers/runtime-apis/handlers/index.mdx b/src/content/docs/workers/runtime-apis/handlers/index.mdx
index 0ce1d48c75d798b..f62e15838d7d289 100644
--- a/src/content/docs/workers/runtime-apis/handlers/index.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/index.mdx
@@ -9,14 +9,14 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Handlers are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker. For example, the `fetch()` handler receives an HTTP request, and can return a response:
 
 ```js
 export default {
 	async fetch(request, env, ctx) {
-		return new Response("Hello World!");
+		return new Response('Hello World!');
 	},
 };
 ```
diff --git a/src/content/docs/workers/runtime-apis/handlers/tail.mdx b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
index b95fc4c33d0ffea..7c6fbbaa19a19ad 100644
--- a/src/content/docs/workers/runtime-apis/handlers/tail.mdx
+++ b/src/content/docs/workers/runtime-apis/handlers/tail.mdx
@@ -18,124 +18,170 @@ To configure a Tail Worker, refer to [Tail Workers documentation](/workers/obser
 
 ```js
 export default {
-	async tail(events, env, ctx) {
-		fetch("<YOUR_ENDPOINT>", {
-			method: "POST",
-			body: JSON.stringify(events),
-		});
-	},
-};
+  async tail(events, env, ctx) {
+    fetch("<YOUR_ENDPOINT>", {
+      method: "POST",
+      body: JSON.stringify(events),
+    })
+  }
+}
 ```
 
 ### Parameters
 
-- `events` array
-  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
 
-- `env` object
-  - An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
 
-- `ctx` object
-  - An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
+* `events` array
+
+  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the User Worker.
+
+* `env` object
+
+  * An object containing the bindings associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/), such as KV namespaces and Durable Objects.
+
+* `ctx` object
+  * An object containing the context associated with your Worker using [ES modules format](/workers/reference/migrate-to-module-workers/). Currently, this object just contains the `waitUntil` function.
+
+
 
 ### Properties
 
-- `event.type` string
-  - The type of event. This will always return `"tail"`.
 
-- `event.traces` array
-  - An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
 
-- <code>event.waitUntil(promisePromise)</code> : void
-  - Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
+* `event.type` string
+
+  * The type of event. This will always return `"tail"`.
+
+* `event.traces` array
+
+  * An array of [`TailItems`](/workers/runtime-apis/handlers/tail/#tailitems). One `TailItem` is collected for each event that triggers a Worker. For Workers for Platforms customers with a Tail Worker installed on the dynamic dispatch Worker, `events` will contain two elements: one for the dynamic dispatch Worker and one for the user Worker.
+
+* <code>event.waitUntil(promisePromise)</code> : void
+
+  * Refer to [`waitUntil`](/workers/runtime-apis/context/#waituntil). Note that unlike fetch event handlers, tail handlers do not return a value, so this is the only way for trace Workers to do asynchronous work.
+
+
 
 ### `TailItems`
 
 #### Properties
 
-- `scriptName` string
-  - The name of the producer script.
-
-- `event` object
-  - Contains information about the Worker’s triggering event.
-    - For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
-    - For other event types: `null`, currently.
-
-- `eventTimestamp` number
-  - Measured in epoch time.
-
-- `logs` array
-  - An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
-
-- `exceptions` array
-  - An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
-
-- `outcome` string
-  - The outcome of the Worker invocation, one of:
-    - `unknown`: outcome status was not set.
-    - `ok`: The worker invocation succeeded.
-    - `exception`: An unhandled exception was thrown. This can happen for many reasons, including:
-      - An uncaught JavaScript exception.
-      - A fetch handler that does not result in a Response.
-      - An internal error.
-    - `exceededCpu`: The Worker invocation exceeded either its CPU limits.
-    - `exceededMemory`: The Worker invocation exceeded memory limits.
-    - `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
-    - `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
-    - `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
+
+
+* `scriptName` string
+
+  * The name of the producer script.
+
+* `event` object
+
+  * Contains information about the Worker’s triggering event.
+    * For fetch events: a [`FetchEventInfo` object](/workers/runtime-apis/handlers/tail/#fetcheventinfo)
+    * For other event types: `null`, currently.
+
+* `eventTimestamp` number
+
+  * Measured in epoch time.
+
+* `logs` array
+
+  * An array of [TailLogs](/workers/runtime-apis/handlers/tail/#taillog).
+
+* `exceptions` array
+
+  * An array of [`TailExceptions`](/workers/runtime-apis/handlers/tail/#tailexception). A single Worker invocation might result in multiple unhandled exceptions, since a Worker can register multiple asynchronous tasks.
+
+* `outcome` string
+
+  * The outcome of the Worker invocation, one of:
+    * `unknown`: outcome status was not set.
+    * `ok`: The worker invocation succeeded.
+    * `exception`: An unhandled exception was thrown.  This can happen for many reasons, including:
+      * An uncaught JavaScript exception.
+      * A fetch handler that does not result in a Response.
+      * An internal error.
+    * `exceededCpu`: The Worker invocation exceeded either its CPU limits.
+    * `exceededMemory`: The Worker invocation exceeded memory limits.
+    * `scriptNotFound`: An internal error from difficulty retrieving the Worker script.
+    * `canceled`: The worker invocation was canceled before it completed. Commonly because the client disconnected before a response could be sent.
+    * `responseStreamDisconnected`: The response stream was disconnected during deferred proxying. Happens when either the client or server hangs up early.
+
+
 
 :::note[Outcome is not the same as HTTP status.]
 
 Outcome is equivalent to the exit status of a script and an indicator of whether it has fully run to completion. A Worker outcome may differ from a response code if, for example:
 
-- a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
-- a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
+* a script successfully processes a request but is logically designed to return a `4xx`/`5xx` response.
+* a script sends a successful `200` response but an asynchronous task registered via `waitUntil()` later exceeds CPU or memory limits.
   :::
 
 ### `FetchEventInfo`
 
 #### Properties
 
-- `request` object
-  - A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
 
-- `response` object
-  - A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
+
+* `request` object
+
+  * A [`TailRequest` object](/workers/runtime-apis/handlers/tail/#tailrequest).
+
+* `response` object
+
+  * A [`TailResponse` object](/workers/runtime-apis/handlers/tail/#tailresponse).
+
 
 ### `TailRequest`
 
 #### Properties
 
-- `cf` object
-  - Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
 
-- `headers` object
-  - Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
 
-- `method` string
-  - The HTTP request method.
+* `cf` object
+
+  * Contains the data from [`IncomingRequestCfProperties`](/workers/runtime-apis/request/#incomingrequestcfproperties).
+
+* `headers` object
+
+  * Header name/value entries (redacted by default). Header names are lowercased, and the values associated with duplicate header names are concatenated, with the string `", "` (comma space) interleaved, similar to [the Fetch standard](https://fetch.spec.whatwg.org/#concept-header-list-get).
+
+* `method` string
+
+  * The HTTP request method.
+
+* `url` string
+
+  * The HTTP request URL (redacted by default).
+
 
-- `url` string
-  - The HTTP request URL (redacted by default).
 
 #### Methods
 
-- `getUnredacted()` object
-  - Returns a TailRequest object with unredacted properties
+
+
+* `getUnredacted()` object
+
+  * Returns a TailRequest object with unredacted properties
+
+
 
 Some of the properties of `TailRequest` are redacted by default to make it harder to accidentally record sensitive information, like user credentials or API tokens. The redactions use heuristic rules, so they are subject to false positives and negatives. Clients can call `getUnredacted()` to bypass redaction, but they should always be careful about what information is retained, whether using the redaction or not.
 
-- Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
-- URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
-- Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
-- Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
+* Header redaction: The header value will be the string `“REDACTED”` when the (case-insensitive) header name is `cookie`/`set-cookie` or contains a substring `"auth”`, `“key”`, `“secret”`, `“token”`, or `"jwt"`.
+* URL redaction: For each greedily matched substring of ID characters (a-z, A-Z, 0-9, '+', '-', '\_') in the URL, if it meets the following criteria for a hex or base-64 ID, the substring will be replaced with the string `“REDACTED”`.
+* Hex ID: Contains 32 or more hex digits, and contains only hex digits and separators ('+', '-', '\_')
+* Base-64 ID: Contains 21 or more characters, and contains at least two uppercase, two lowercase, and two digits.
 
 ### `TailResponse`
 
 #### Properties
 
-- `status` number
-  - The HTTP status code.
+
+
+* `status` number
+
+  * The HTTP status code.
+
+
 
 ### `TailLog`
 
@@ -143,14 +189,20 @@ Records information sent to console functions.
 
 #### Properties
 
-- `timestamp` number
-  - Measured in epoch time.
 
-- `level` string
-  - A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
 
-- `message` object
-  - The array of parameters passed to the console function.
+* `timestamp` number
+
+  * Measured in epoch time.
+
+* `level` string
+
+  * A string indicating the console function that was called. One of: `debug`, `info`, `log`, `warn`, `error`.
+
+* `message` object
+
+  * The array of parameters passed to the console function.
+
 
 ### `TailException`
 
@@ -158,15 +210,22 @@ Records an unhandled exception that occurred during the Worker invocation.
 
 #### Properties
 
-- `timestamp` number
-  - Measured in epoch time.
 
-- `name` string
-  - The error type (For example,`Error`, `TypeError`, etc.).
 
-- `message` object
-  - The error description (For example, `"x" is not a function`).
+* `timestamp` number
+
+  * Measured in epoch time.
+
+* `name` string
+
+  * The error type (For example,`Error`, `TypeError`, etc.).
+
+* `message` object
+
+  * The error description (For example, `"x" is not a function`).
+
+
 
 ## Related resources
 
-- [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
+* [Tail Workers](/workers/observability/logs/tail-workers/) - Configure a Tail Worker to receive information about the execution of other Workers.
diff --git a/src/content/docs/workers/runtime-apis/headers.mdx b/src/content/docs/workers/runtime-apis/headers.mdx
index f7a50f6ec116fc8..5fd387aafea782c 100644
--- a/src/content/docs/workers/runtime-apis/headers.mdx
+++ b/src/content/docs/workers/runtime-apis/headers.mdx
@@ -17,16 +17,16 @@ When a header name possesses multiple values, those values will be concatenated
 ```js
 let headers = new Headers();
 
-headers.get("x-foo"); //=> null
+headers.get('x-foo'); //=> null
 
-headers.set("x-foo", "123");
-headers.get("x-foo"); //=> "123"
+headers.set('x-foo', '123');
+headers.get('x-foo'); //=> "123"
 
-headers.set("x-foo", "hello");
-headers.get("x-foo"); //=> "hello"
+headers.set('x-foo', 'hello');
+headers.get('x-foo'); //=> "hello"
 
-headers.append("x-foo", "world");
-headers.get("x-foo"); //=> "hello, world"
+headers.append('x-foo', 'world');
+headers.get('x-foo'); //=> "hello, world"
 ```
 
 ## Differences
@@ -61,6 +61,7 @@ console.log(headers.getAll("Set-Cookie"));
 
 In Cloudflare Workers, the `Headers.get` method returns a [`USVString`](https://mdn2.netlify.app/en-us/docs/web/api/usvstring/) instead of a [`ByteString`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String), which is specified by the web standard. For most scenarios, this should have no noticeable effect. To compare the differences between these two string classes, refer to this [Playground example](https://workers.cloudflare.com/playground#LYVwNgLglgDghgJwgegGYHsHALQBM4RwDcABAEbogB2+CAngLzbMutvvsCMALAJx-cAzAHZeANkG8AHAAZOU7t2EBWAEy9eqsXNWdOALg5HjbHv34jxk2fMUr1m7Z12cAsACgAwuioQApr7YACJQAM4w6KFQ0D76JBhYeATEJFRwwH4MAERQNH4AHgB0AFahWaSoUGAB6Zk5eUWlWR7evgEQ2AAqdDB+cXAwMGBQAMYEUD7IxXAAbnChIwiwEADUwOi44H4eHgURSCS4fqhw4BAkAN7uAJDzdFQj8X4QIwAWABQIfgCOIH6hEAAlJcbtdqucxucGCQsoBeDcAXHtZUHgkggCCoKSeAgkaFUPwAdxInQKEAAog8Nn4EO9AYUAiNKe9IYDkc8SPTKbgsVCSABlCBLKgAc0KqAQ6GAnleiG8R3ehQVaIx3JZoIZVFC6GqhTA6CF7yynVeYRIJrgJAAqryAGr8wVCkj46KvEjmyH6LIAGhIzLVPk12t1+sNxtCprD5oAQnR-Hbcg6nRAXW7sT5LZ0AGLYKQe70co5cgiq67XZDIEgACT8cCOCAjXxIoRAg0iflwJAg6EdmAA1iQfGA6I7nSRo7GBfHQt6yGj+yAEKCy6bgEM-BlfOM0yBQv9LTa48LQoUiaHUiSSMM8cOwGASDBBec4Ivy-jEFR466KLOk2FCqzzq81a1mGuIEpWQFUqE7wXDC+ZttgkJZHEcGFucAC+xbXF8EDzlQZ6EgASv8EQan4BpSn4Ix9pQ5xJn4JAAAatAGfgMa6NAdoBJBEeE-r0YBNaQR2XY7vRdFzhAMCzgyK6IGE-qFF6lwkAJwEkBhNxoe4aEeCYelGGYAiWBI0hyAoShqBoWg6HoLQ+P4gQhLxUQxFQcQJDg+CEKQaQZNkGSEF5cDlPEVQ1H5WRkLqZDNF49ntF0PR9K6gzDJCExUFMmpUDs7gXFkwBwLkAD66ybNUSH1EcjRlDp7j6Q1rCGRYogmTY5n2FZTguMwHhAA).
 
+
 ## Cloudflare headers
 
 Cloudflare sets a number of its own custom headers on incoming requests and outgoing responses. While some may be used for its own tracking and bookkeeping, many of these can be useful to your own applications – or Workers – too.
@@ -69,5 +70,5 @@ For a list of documented Cloudflare request headers, refer to [Cloudflare HTTP h
 
 ## Related resources
 
-- [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
-- [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
+* [Logging headers to console](/workers/examples/logging-headers/) - Review how to log headers in the console.
+* [Cloudflare HTTP headers](/fundamentals/reference/http-headers/) - Contains a list of specific headers that Cloudflare adds.
\ No newline at end of file
diff --git a/src/content/docs/workers/runtime-apis/messagechannel.mdx b/src/content/docs/workers/runtime-apis/messagechannel.mdx
index dc8e4475fe3ec30..34a69e18a8ca1ac 100644
--- a/src/content/docs/workers/runtime-apis/messagechannel.mdx
+++ b/src/content/docs/workers/runtime-apis/messagechannel.mdx
@@ -19,10 +19,10 @@ currently limited to uses with a single Worker instance. This means that you can
 const { port1, port2 } = new MessageChannel();
 
 port2.onmessage = (event) => {
-	console.log("Received message:", event.data);
+	console.log('Received message:', event.data);
 };
 
-port2.postMessage("Hello from port2!");
+port2.postMessage('Hello from port2!');
 ```
 
 Any value that can be used with the `structuredClone(...)` API can be sent over the port.
@@ -31,13 +31,13 @@ Any value that can be used with the `structuredClone(...)` API can be sent over
 
 There are a number of key limitations to the `MessageChannel` API in Workers:
 
-- Transfer lists are currently not supported. This means that you will not be able to transfer
+* Transfer lists are currently not supported. This means that you will not be able to transfer
   ownership of objects like `ArrayBuffer` or `MessagePort` between ports.
-- The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
+* The `MessagePort` is not yet serializable. This means that you cannot send a `MessagePort` object
   through the `postMessage` method or via JSRPC calls.
-- The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
+* The `'messageerror'` event is only partially supported. If the `'onmessage'` handler throws an
   error, the `'messageerror'` event will be triggered, however, it will not be triggered when there
-  are errors serializing or deserializing the message data. Instead, the error will be thrown when
-  the `postMessage` method is called on the sending port.
-- The `'close'` event will be emitted on both ports when one of the ports is closed, however it
+	are errors serializing or deserializing the message data. Instead, the error will be thrown when
+	the `postMessage` method is called on the sending port.
+* The `'close'` event will be emitted on both ports when one of the ports is closed, however it
   will not be emitted when the Worker is terminated or when one of the ports is garbage collected.
diff --git a/src/content/docs/workers/runtime-apis/nodejs/util.mdx b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
index 7a797483bdc8683..2e7372f4d555bc0 100644
--- a/src/content/docs/workers/runtime-apis/nodejs/util.mdx
+++ b/src/content/docs/workers/runtime-apis/nodejs/util.mdx
@@ -35,16 +35,16 @@ await promisifiedFoo(args);
 Similarly to `promisify`, `callbackify` converts a Promise-returning async function into a Node.js-style callback function:
 
 ```js
-import { callbackify } from "node:util";
+import { callbackify } from 'node:util';
 
 async function foo(args) {
-	throw new Error("boom");
+  throw new Error('boom');
 }
 
 const callbackifiedFoo = callbackify(foo);
 
 callbackifiedFoo(args, (err, value) => {
-	if (err) throw err;
+  if (err) throw err;
 });
 ```
 
diff --git a/src/content/docs/workers/runtime-apis/performance.mdx b/src/content/docs/workers/runtime-apis/performance.mdx
index f8c14e1b3cc76b2..0465b6db640c78a 100644
--- a/src/content/docs/workers/runtime-apis/performance.mdx
+++ b/src/content/docs/workers/runtime-apis/performance.mdx
@@ -21,7 +21,7 @@ When Workers are deployed to Cloudflare, as a security measure to [mitigate agai
 ```typescript title="Time is frozen — start will have the exact same value as end."
 const start = performance.now();
 for (let i = 0; i < 1e6; i++) {
-	// do expensive work
+  // do expensive work
 }
 const end = performance.now();
 const timing = end - start; // 0
diff --git a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
index acf48ac5f2c6e48..a0677b887aebf4c 100644
--- a/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/error-handling.mdx
@@ -18,9 +18,9 @@ An exception thrown by an RPC method implementation will propagate to the caller
 
 ### Unsupported error types
 
-- If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
-- The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
-- Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
+* If an [`AggregateError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError) is thrown by an RPC method, it is not propagated back to the caller.
+* The [`SuppressedError`](https://github.com/tc39/proposal-explicit-resource-management?tab=readme-ov-file#the-suppressederror-error) type from the Explicit Resource Management proposal is not currently implemented or supported in Workers.
+* Own properties of error objects, such as the [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, are not propagated back to the caller
 
 ## Additional properties
 
diff --git a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
index 5bb6019d5d24910..2a80b67db3d88e2 100644
--- a/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
+++ b/src/content/docs/workers/runtime-apis/rpc/reserved-methods.mdx
@@ -16,7 +16,7 @@ Some method names are reserved or have special semantics.
 
 ## Special Methods
 
-For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does _not_ apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
+For backwards compatibility, when extending `WorkerEntrypoint` or `DurableObject`, the following method names have special semantics. Note that this does *not* apply to `RpcTarget`. On `RpcTarget`, these methods work like any other RPC method.
 
 ### `fetch()`
 
@@ -36,12 +36,12 @@ The `connect()` method of the `WorkerEntrypoint` class is reserved for opening a
 
 The following method (or property) names may not be used as RPC methods on any RPC type (including `WorkerEntrypoint`, `DurableObject`, and `RpcTarget`):
 
-- `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
-- `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
+* `dup`: This is reserved for duplicating a stub. Refer to the [RPC Lifecycle](/workers/runtime-apis/rpc/lifecycle) docs to learn more about `dup()`.
+* `constructor`: This name has special meaning for JavaScript classes. It is not intended to be called as a method, so it is not allowed over RPC.
 
 The following methods are disallowed only on `WorkerEntrypoint` and `DurableObject`, but allowed on `RpcTarget`. These methods have historically had special meaning to Durable Objects, where they are used to handle certain system-generated events.
 
-- `alarm`
-- `webSocketMessage`
-- `webSocketClose`
-- `webSocketError`
+* `alarm`
+* `webSocketMessage`
+* `webSocketClose`
+* `webSocketError`
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
index 8ec8b621e64213b..72512cc6f9f0f85 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestream.mdx
@@ -13,33 +13,47 @@ A `ReadableStream` is returned by the `readable` property inside [`TransformStre
 
 ## Properties
 
-- `locked` boolean
-  - A Boolean value that indicates if the readable stream is locked to a reader.
+
+
+* `locked` boolean
+  * A Boolean value that indicates if the readable stream is locked to a reader.
+
+
 
 ## Methods
 
-- <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
-  - Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
 
-- <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
-  - Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
+
+* <code>pipeTo(destinationWritableStream, optionsPipeToOptions)</code> : Promise\<void>
+
+  * Pipes the readable stream to a given writable stream `destination` and returns a promise that is fulfilled when the `write` operation succeeds or rejects it if the operation fails.
+
+* <code>getReader(optionsObject)</code> : ReadableStreamDefaultReader
+
+  * Gets an instance of `ReadableStreamDefaultReader` and locks the `ReadableStream` to that reader instance. This method accepts an object argument indicating options. The only supported option is `mode`, which can be set to `byob` to create a [`ReadableStreamBYOBReader`](/workers/runtime-apis/streams/readablestreambyobreader/), as shown here:
 
 ```js
-let reader = readable.getReader({ mode: "byob" });
+let reader = readable.getReader({ mode: 'byob' });
 ```
 
+
+
 ### `PipeToOptions`
 
-- `preventClose` bool
-  - When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
 
-- `preventAbort` bool
-  - When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
 
----
+* `preventClose` bool
+
+  * When `true`, closure of the source `ReadableStream` will not cause the destination `WritableStream` to be closed.
+
+* `preventAbort` bool
+
+  * When `true`, errors in the source `ReadableStream` will no longer abort the destination `WritableStream`. `pipeTo` will return a rejected promise with the error from the source or any error that occurred while aborting the destination.
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
-- [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
+* [Streams](/workers/runtime-apis/streams/)
+* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+* [MDN’s `ReadableStream` documentation](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
index c8a67b7ecf18fec..cff8e9257521f97 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreambyobreader.mdx
@@ -24,41 +24,50 @@ A `ReadableStreamBYOBReader` is not instantiated via its constructor. Rather, it
 
 ```js
 const { readable, writable } = new TransformStream();
-const reader = readable.getReader({ mode: "byob" });
+const reader = readable.getReader({ mode: 'byob' });
 ```
 
----
+***
 
 ## Methods
 
-- <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-  - Returns a promise with the next available chunk of data read into a passed-in buffer.
 
-- <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
-  - Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read. The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
-    - If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
-    - If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
-    - If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
-    - If the stream errors, the promise rejects.
-    - `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
 
----
+* <code>read(bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+
+  * Returns a promise with the next available chunk of data read into a passed-in buffer.
+
+* <code>readAtLeast(minElements, bufferArrayBufferView)</code> : Promise\<ReadableStreamBYOBReadResult>
+
+  * Returns a promise with the next available chunk of data read into a passed-in buffer. The promise will not resolve until at least `minElements` elements have been read.  The element size is determined by `bufferArrayBufferView`, for example 4 bytes per element for a `Uint32Array`. However, fewer than `minElements` elements may be returned if the end of the stream is reached or the underlying stream is closed. Specifically:
+
+    * If `minElements` or more elements are available, the promise resolves with `{ value: <buffer view sized to bytes read>, done: false }`.
+    * If the stream ends after some data has been read but fewer than `minElements` elements, the promise resolves with the partial data: `{ value: <buffer view sized to bytes actually read>, done: false }`. The next call to `read` or `readAtLeast` will then return `{ value: undefined, done: true }`.
+    * If the stream ends with zero bytes available (that is, the stream is already at EOF), the promise resolves with `{ value: <zero-length view>, done: true }`.
+    * If the stream errors, the promise rejects.
+    * `minElements` must be at least 1, and `minElements * elementSize` must not exceed the byte length of `bufferArrayBufferView`, or the promise rejects with a `TypeError`. For a `Uint8Array`, element size is 1, so `minElements` is effectively a byte count.
+
+
+
+***
 
 ## Common issues
 
 :::caution[Warning]
 
+
 `read` provides no control over the minimum number of bytes that should be read into the buffer. Even if you allocate a 1 MiB buffer, the kernel is perfectly within its rights to fulfill this read with a single byte, whether or not an EOF immediately follows.
 
 In practice, the Workers team has found that `read` typically fills only 1% of the provided buffer.
 
 `readAtLeast` is a non-standard extension to the Streams API which allows users to specify that at least `minElements` elements must be read into the buffer before resolving the read. For a `Uint8Array` (the most common case), each element is one byte, so `minElements` is effectively a byte count. If the stream ends before `minElements` elements are available, the partial data that was read is still returned rather than throwing an error — refer to the [`readAtLeast` method documentation above](#methods) for the full details.
 
+
 :::
 
----
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
+* [Streams](/workers/runtime-apis/streams/)
+* [Background about BYOB readers in the Streams API WHATWG specification](https://streams.spec.whatwg.org/#byob-readers)
diff --git a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
index 41d4eaf45b54a02..72a05a4edd97f20 100644
--- a/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/readablestreamdefaultreader.mdx
@@ -23,32 +23,44 @@ const { readable, writable } = new TransformStream();
 const reader = readable.getReader();
 ```
 
----
+***
 
 ## Properties
 
-- `reader.closed` : Promise
-  - A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
+
+
+* `reader.closed` : Promise
+
+  * A promise indicating if the reader is closed. The promise is fulfilled when the reader stream closes and is rejected if there is an error in the stream.
+
+
 
 ## Methods
 
-- `read()` : Promise
-  - A promise that returns the next available chunk of data being passed through the reader queue.
 
-- <code>cancel(reasonstringoptional)</code> : void
-  - Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
+
+* `read()` : Promise
+
+  * A promise that returns the next available chunk of data being passed through the reader queue.
+
+* <code>cancel(reasonstringoptional)</code> : void
+
+  * Cancels the stream. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying source’s cancel algorithm -- if this readable stream is one side of a [`TransformStream`](/workers/runtime-apis/streams/transformstream/), then its cancel algorithm causes the transform’s writable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet read is lost.
   :::
 
-- `releaseLock()` : void
-  - Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+* `releaseLock()` : void
 
----
+  * Releases the lock on the readable stream. A lock cannot be released if the reader has pending read operations. A `TypeError` is thrown and the reader remains locked.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Readable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#rs-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
index 46c9e41542ea8b0..029a878e9e847be 100644
--- a/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/transformstream.mdx
@@ -13,7 +13,7 @@ A transform stream consists of a pair of streams: a writable stream, known as it
 
 Workers currently only implements an identity transform stream, a type of transform stream which forwards all chunks written to its writable side to its readable side, without any changes.
 
----
+***
 
 ## Constructor
 
@@ -21,17 +21,26 @@ Workers currently only implements an identity transform stream, a type of transf
 let { readable, writable } = new TransformStream();
 ```
 
-- `TransformStream()` TransformStream
-  - Returns a new identity transform stream.
+
+
+* `TransformStream()` TransformStream
+
+  * Returns a new identity transform stream.
+
+
 
 ## Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## `IdentityTransformStream`
 
@@ -45,17 +54,26 @@ The `IdentityTransformStream` readable side supports [bring your own buffer (BYO
 let { readable, writable } = new IdentityTransformStream();
 ```
 
-- `IdentityTransformStream()` IdentityTransformStream
-  - Returns a new identity transform stream.
+
+
+* `IdentityTransformStream()` IdentityTransformStream
+
+  * Returns a new identity transform stream.
+
+
 
 ### Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## `FixedLengthStream`
 
@@ -67,20 +85,29 @@ The `FixedLengthStream` is a specialization of `IdentityTransformStream` that li
 let { readable, writable } = new FixedLengthStream(1000);
 ```
 
-- `FixedLengthStream(length)` FixedLengthStream
-  - Returns a new identity transform stream.
-  - `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
+
+
+* `FixedLengthStream(length)` FixedLengthStream
+
+  * Returns a new identity transform stream.
+  * `length` maybe a `number` or `bigint` with a maximum value of `2^53 - 1`.
+
+
 
 ### Properties
 
-- `readable` ReadableStream
-  - An instance of a `ReadableStream`.
-- `writable` WritableStream
-  - An instance of a `WritableStream`.
 
----
+
+* `readable` ReadableStream
+  * An instance of a `ReadableStream`.
+* `writable` WritableStream
+  * An instance of a `WritableStream`.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
+* [Streams](/workers/runtime-apis/streams/)
+* [Transform Streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#transform-stream)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
index 1040f59de92975c..799ddf11156ada5 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestream.mdx
@@ -15,9 +15,9 @@ A typical way to write to a `WritableStream` is to pipe a [`ReadableStream`](/wo
 
 ```js
 readableStream
-	.pipeTo(writableStream)
-	.then(() => console.log("All data successfully written!"))
-	.catch((e) => console.error("Something went wrong!", e));
+  .pipeTo(writableStream)
+  .then(() => console.log('All data successfully written!'))
+  .catch(e => console.error('Something went wrong!', e));
 ```
 
 To write to a `WritableStream` directly, you must use its writer.
@@ -31,25 +31,36 @@ Refer to the [WritableStreamDefaultWriter](/workers/runtime-apis/streams/writabl
 
 ## Properties
 
-- `locked` boolean
-  - A Boolean value to indicate if the writable stream is locked to a writer.
+
+
+* `locked` boolean
+
+  * A Boolean value to indicate if the writable stream is locked to a writer.
+
+
 
 ## Methods
 
-- <code>abort(reasonstringoptional)</code> : Promise\<void>
-  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+
+
+* <code>abort(reasonstringoptional)</code> : Promise\<void>
+
+  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-- `getWriter()` : WritableStreamDefaultWriter
-  - Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+* `getWriter()` : WritableStreamDefaultWriter
 
----
+  * Gets an instance of `WritableStreamDefaultWriter` and locks the `WritableStream` to that writer instance.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
index fda65a4afb87bbd..9778261db7f5088 100644
--- a/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
+++ b/src/content/docs/workers/runtime-apis/streams/writablestreamdefaultwriter.mdx
@@ -18,57 +18,71 @@ A writer is used when you want to write directly to a [`WritableStream`](/worker
 
 ```js
 function writeArrayToStream(array, writableStream) {
-	const writer = writableStream.getWriter();
-	array.forEach((chunk) => writer.write(chunk).catch(() => {}));
+  const writer = writableStream.getWriter();
+  array.forEach(chunk => writer.write(chunk).catch(() => {}));
 
-	return writer.close();
+  return writer.close();
 }
 
 writeArrayToStream([1, 2, 3, 4, 5], writableStream)
-	.then(() => console.log("All done!"))
-	.catch((e) => console.error("Error with the stream: " + e));
+  .then(() => console.log('All done!'))
+  .catch(e => console.error('Error with the stream: ' + e));
 ```
 
 ## Properties
 
-- `writer.desiredSize` int
-  - The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
 
-- `writer.closed` Promise\<void>
-  - A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
+
+* `writer.desiredSize` int
+
+  * The size needed to fill the stream’s internal queue, as an integer. Always returns 1, 0 (if the stream is closed), or `null` (if the stream has errors).
+
+* `writer.closed` Promise\<void>
+
+  * A promise that indicates if the writer is closed. The promise is fulfilled when the writer stream is closed and rejected if there is an error in the stream.
+
+
 
 ## Methods
 
-- <code>abort(reasonstringoptional)</code> : Promise\<void>
-  - Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
+
+
+* <code>abort(reasonstringoptional)</code> : Promise\<void>
+
+  * Aborts the stream. This method returns a promise that fulfills with a response `undefined`. `reason` is an optional human-readable string indicating the reason for cancellation. `reason` will be passed to the underlying sink’s abort algorithm. If this writable stream is one side of a [TransformStream](/workers/runtime-apis/streams/transformstream/), then its abort algorithm causes the transform’s readable side to become errored with `reason`.
 
   :::caution[Warning]
 
   Any data not yet written is lost upon abort.
   :::
 
-- `close()` : Promise\<void>
-  - Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
+* `close()` : Promise\<void>
+
+  * Attempts to close the writer. Remaining writes finish processing before the writer is closed. This method returns a promise fulfilled with `undefined` if the writer successfully closes and processes the remaining writes, or rejected on any error.
 
-- `releaseLock()` : void
-  - Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
+* `releaseLock()` : void
+
+  * Releases the writer’s lock on the stream. Once released, the writer is no longer active. You can call this method before all pending `write(chunk)` calls are resolved. This allows you to queue a `write` operation, release the lock, and begin piping into the writable stream from another source, as shown in the example below.
 
 ```js
 let writer = writable.getWriter();
 // Write a preamble.
-writer.write(new TextEncoder().encode("foo bar"));
+writer.write(new TextEncoder().encode('foo bar'));
 // While that’s still writing, pipe the rest of the body from somewhere else.
 writer.releaseLock();
 await someResponse.body.pipeTo(writable);
 ```
 
-- <code>write(chunkany)</code> : Promise\<void>
-  - Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
-  - The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+* <code>write(chunkany)</code> : Promise\<void>
 
----
+  * Writes a chunk of data to the writer and returns a promise that resolves if the operation succeeds.
+  * The underlying stream may accept fewer kinds of type than `any`, it will throw an exception when encountering an unexpected type.
+
+
+
+***
 
 ## Related resources
 
-- [Streams](/workers/runtime-apis/streams/)
-- [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
+* [Streams](/workers/runtime-apis/streams/)
+* [Writable streams in the WHATWG Streams API specification](https://streams.spec.whatwg.org/#ws-model)
diff --git a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
index ef899b752b54415..be6e3593489cb39 100644
--- a/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
+++ b/src/content/docs/workers/runtime-apis/tcp-sockets.mdx
@@ -29,132 +29,143 @@ The `connect()` function returns a TCP socket, with both a [readable](/workers/r
 `connect()` is provided as a [Runtime API](/workers/runtime-apis/), and is accessed by importing the `connect` function from `cloudflare:sockets`. This process is similar to how one imports built-in modules in Node.js. Refer to the following codeblock for an example of creating a TCP socket, writing to it, and returning the readable side of the socket as a response:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from 'cloudflare:sockets';
 
 export default {
-	async fetch(req): Promise<Response> {
-		const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
-		const url = new URL(req.url);
-
-		try {
-			const socket = connect(gopherAddr);
-
-			const writer = socket.writable.getWriter();
-			const encoder = new TextEncoder();
-			const encoded = encoder.encode(url.pathname + "\r\n");
-			await writer.write(encoded);
-			await writer.close();
-
-			return new Response(socket.readable, {
-				headers: { "Content-Type": "text/plain" },
-			});
-		} catch (error) {
-			return new Response("Socket connection failed: " + error, {
-				status: 500,
-			});
-		}
-	},
+  async fetch(req): Promise<Response> {
+    const gopherAddr = { hostname: "gopher.floodgap.com", port: 70 };
+    const url = new URL(req.url);
+
+    try {
+      const socket = connect(gopherAddr);
+
+      const writer = socket.writable.getWriter()
+      const encoder = new TextEncoder();
+      const encoded = encoder.encode(url.pathname + "\r\n");
+      await writer.write(encoded);
+      await writer.close();
+
+      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
+    } catch (error) {
+      return new Response("Socket connection failed: " + error, { status: 500 });
+    }
+  }
 } satisfies ExportedHandler;
 ```
 
-- <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
-  - `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
+
+
+* <code>connect(address: SocketAddress | string, options?: optional SocketOptions)</code> : `Socket`
+  * `connect()` accepts either a URL string or [`SocketAddress`](/workers/runtime-apis/tcp-sockets/#socketaddress) to define the hostname and port number to connect to, and an optional configuration object, [`SocketOptions`](/workers/runtime-apis/tcp-sockets/#socketoptions). It returns an instance of a [`Socket`](/workers/runtime-apis/tcp-sockets/#socket).
+
 
 ### `SocketAddress`
 
-- `hostname` string
-  - The hostname to connect to. Example: `cloudflare.com`.
 
-- `port` number
-  - The port number to connect to. Example: `5432`.
+
+* `hostname` string
+  * The hostname to connect to. Example: `cloudflare.com`.
+
+* `port` number
+  * The port number to connect to. Example: `5432`.
+
+
 
 ### `SocketOptions`
 
-- `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
-  - Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
-  - `off` — Do not use TLS.
-  - `on` — Use TLS.
-  - `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
 
-- `allowHalfOpen` boolean — Defaults to `false`
-  - Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
-  - This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
+
+* `secureTransport` "off" | "on" | "starttls" — Defaults to `off`
+  * Specifies whether or not to use [TLS](https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/) when creating the TCP socket.
+  * `off` — Do not use TLS.
+  * `on` — Use TLS.
+  * `starttls` — Do not use TLS initially, but allow the socket to be upgraded to use TLS by calling [`startTls()`](/workers/runtime-apis/tcp-sockets/#opportunistic-tls-starttls).
+
+* `allowHalfOpen` boolean — Defaults to `false`
+  * Defines whether the writable side of the TCP socket will automatically close on end-of-file (EOF). When set to `false`, the writable side of the TCP socket will automatically close on EOF. When set to `true`, the writable side of the TCP socket will remain open on EOF.
+  * This option is similar to that offered by the Node.js [`net` module](https://nodejs.org/api/net.html) and allows interoperability with code which utilizes it.
+
+
 
 ### `SocketInfo`
 
-- `remoteAddress` string | null
-  - The address of the remote peer the socket is connected to. May not always be set.
 
-- `localAddress` string | null
-  - The address of the local network endpoint for this socket. May not always be set.
+
+* `remoteAddress` string | null
+  * The address of the remote peer the socket is connected to. May not always be set.
+
+* `localAddress` string | null
+  * The address of the local network endpoint for this socket. May not always be set.
+
+
 
 ### `Socket`
 
-- <code>readable</code> : ReadableStream
-  - Returns the readable side of the TCP socket.
 
-- <code>writable</code> : WritableStream
-  - Returns the writable side of the TCP socket.
-  - The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
 
-- `opened` `Promise<SocketInfo>`
-  - This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
+* <code>readable</code> : ReadableStream
+  * Returns the readable side of the TCP socket.
+
+* <code>writable</code> : WritableStream
+  * Returns the writable side of the TCP socket.
+  * The `WritableStream` returned only accepts chunks of `Uint8Array` or its views.
+
+* `opened` `Promise<SocketInfo>`
+  * This promise is resolved when the socket connection is established and is rejected if the socket encounters an error.
+
+* `closed` `Promise<void>`
+  * This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
+
+* `close()` `Promise<void>`
+  * Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
-- `closed` `Promise<void>`
-  - This promise is resolved when the socket is closed and is rejected if the socket encounters an error.
+* <code>startTls()</code> : Socket
+  * Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
-- `close()` `Promise<void>`
-  - Closes the TCP socket. Both the readable and writable streams are forcibly closed.
 
-- <code>startTls()</code> : Socket
-  - Upgrades an insecure socket to a secure one that uses TLS, returning a new [Socket](/workers/runtime-apis/tcp-sockets#socket). Note that in order to call `startTls()`, you must set [`secureTransport`](/workers/runtime-apis/tcp-sockets/#socketoptions) to `starttls` when initially calling `connect()` to create the socket.
 
 ## Opportunistic TLS (StartTLS)
 
 Many TCP-based systems, including databases and email servers, require that clients use opportunistic TLS (otherwise known as [StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS)) when connecting. In this pattern, the client first creates an insecure TCP socket, without TLS, and then upgrades it to a secure TCP socket, that uses TLS. The `connect()` API simplifies this by providing a method, `startTls()`, which returns a new `Socket` instance that uses TLS:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from "cloudflare:sockets"
 
 const address = {
-	hostname: "example-postgres-db.com",
-	port: 5432,
+  hostname: "example-postgres-db.com",
+  port: 5432
 };
 const socket = connect(address, { secureTransport: "starttls" });
 const secureSocket = socket.startTls();
 ```
 
-- `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
-- Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
-- `startTls()` should only be called once on an existing socket.
+* `startTls()` can only be called if `secureTransport` is set to `starttls` when creating the initial TCP socket.
+* Once `startTls()` is called, the initial socket is closed and can no longer be read from or written to. In the example above, anytime after `startTls()` is called, you would use the newly created `secureSocket`. Any existing readers and writers based off the original socket will no longer work. You must create new readers and writers from the newly created `secureSocket`.
+* `startTls()` should only be called once on an existing socket.
 
 ## Handle errors
 
 To handle errors when creating a new TCP socket, reading from a socket, or writing to a socket, wrap these calls inside [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) statement blocks. The following example opens a connection to Google.com, initiates a HTTP request, and returns the response. If this fails and throws an exception, it returns a [`500`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-500/) response:
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from 'cloudflare:sockets';
 const connectionUrl = { hostname: "google.com", port: 80 };
-export interface Env {}
+export interface Env { }
 export default {
-	async fetch(req, env, ctx): Promise<Response> {
-		try {
-			const socket = connect(connectionUrl);
-			const writer = socket.writable.getWriter();
-			const encoder = new TextEncoder();
-			const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
-			await writer.write(encoded);
-			await writer.close();
-
-			return new Response(socket.readable, {
-				headers: { "Content-Type": "text/plain" },
-			});
-		} catch (error) {
-			return new Response(`Socket connection failed: ${error}`, {
-				status: 500,
-			});
-		}
-	},
+  async fetch(req, env, ctx): Promise<Response> {
+    try {
+      const socket = connect(connectionUrl);
+      const writer = socket.writable.getWriter();
+      const encoder = new TextEncoder();
+      const encoded = encoder.encode("GET / HTTP/1.0\r\n\r\n");
+      await writer.write(encoded);
+      await writer.close();
+
+      return new Response(socket.readable, { headers: { "Content-Type": "text/plain" } });
+    } catch (error) {
+      return new Response(`Socket connection failed: ${error}`, { status: 500 });
+    }
+  }
 } satisfies ExportedHandler<Env>;
 ```
 
@@ -163,7 +174,7 @@ export default {
 You can close a TCP connection by calling `close()` on the socket. This will close both the readable and writable sides of the socket.
 
 ```typescript
-import { connect } from "cloudflare:sockets";
+import { connect } from "cloudflare:sockets"
 
 const socket = connect({ hostname: "my-url.com", port: 70 });
 const reader = socket.readable.getReader();
@@ -175,11 +186,11 @@ const reader = socket.readable.getReader(); // This fails
 
 ## Considerations
 
-- Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
-- TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
-- Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
-- By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
-- Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
+* Outbound TCP sockets to [Cloudflare IP ranges](https://www.cloudflare.com/ips/) are blocked.
+* TCP sockets cannot be created in global scope and shared across requests. You should always create TCP sockets within a handler (ex: [`fetch()`](/workers/get-started/guide/#3-write-code), [`scheduled()`](/workers/runtime-apis/handlers/scheduled/), [`queue()`](/queues/configuration/javascript-apis/#consumer)) or [`alarm()`](/durable-objects/api/alarms/).
+* Each open TCP socket counts towards the maximum number of [open connections](/workers/platform/limits/#simultaneous-open-connections) that can be simultaneously open.
+* By default, Workers cannot create outbound TCP connections on port `25` to send email to SMTP mail servers. [Cloudflare Email Workers](/email-routing/email-workers/) provides APIs to process and forward email.
+* Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/). Currently, it is not possible to make an inbound TCP connection to your Worker, for example, by using the `CONNECT` HTTP method.
 
 ## Troubleshooting
 
diff --git a/src/content/docs/workers/runtime-apis/web-crypto.mdx b/src/content/docs/workers/runtime-apis/web-crypto.mdx
index 5bb7cee5fad993b..9e3a0f0faaaf9f3 100644
--- a/src/content/docs/workers/runtime-apis/web-crypto.mdx
+++ b/src/content/docs/workers/runtime-apis/web-crypto.mdx
@@ -8,7 +8,7 @@ products:
   - workers
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 ## Background
 
@@ -19,13 +19,13 @@ Performing cryptographic operations using the Web Crypto API is significantly fa
 The Web Crypto API is implemented through the `SubtleCrypto` interface, accessible via the global `crypto.subtle` binding. A simple example of calculating a digest (also known as a hash) is:
 
 ```js
-const myText = new TextEncoder().encode("Hello world!");
+const myText = new TextEncoder().encode('Hello world!');
 
 const myDigest = await crypto.subtle.digest(
-	{
-		name: "SHA-256",
-	},
-	myText, // The data you want to hash as an ArrayBuffer
+  {
+    name: 'SHA-256',
+  },
+  myText // The data you want to hash as an ArrayBuffer
 );
 
 console.log(new Uint8Array(myDigest));
@@ -38,17 +38,27 @@ Some common uses include [signing requests](/workers/examples/signing-requests/)
 The Web Crypto API differs significantly from the [Node.js Crypto API](/workers/runtime-apis/nodejs/crypto/). If you are working with code that relies on the Node.js Crypto API, you can use it by enabling the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/).
 :::
 
----
+***
 
 ## Constructors
 
-- <code>crypto.DigestStream(algorithm)</code> DigestStream
-  - A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
+
+
+* <code>crypto.DigestStream(algorithm)</code> DigestStream
+
+  * A non-standard extension to the `crypto` API that supports generating a hash digest from streaming data. The `DigestStream` itself is a [`WritableStream`](/workers/runtime-apis/streams/writablestream/) that does not retain the data written into it. Instead, it generates a hash digest automatically when the flow of data has ended.
+
+
 
 ### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+
 
 ### Usage
 
@@ -112,16 +122,27 @@ export default {
 
 ## Methods
 
-- <code>crypto.randomUUID()</code> : string
-  - Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
 
-- <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
-  - Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
+
+* <code>crypto.randomUUID()</code> : string
+
+  * Generates a new random (version 4) UUID as defined in [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122.txt).
+
+* <code>crypto.getRandomValues(bufferArrayBufferView)</code> : ArrayBufferView
+
+  * Fills the passed <code>ArrayBufferView</code> with cryptographically sound random values and returns the <code>buffer</code>.
+
+
 
 ### Parameters
 
-- <code>buffer</code>ArrayBufferView
-  - Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
+
+
+* <code>buffer</code>ArrayBufferView
+
+  * Must be an Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | BigInt64Array | BigUint64Array.
+
+
 
 ## SubtleCrypto Methods
 
@@ -129,219 +150,358 @@ These methods are all accessed via [`crypto.subtle`](https://developer.mozilla.o
 
 ### encrypt
 
-- <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
+
+
+* <code>encrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the encrypted data corresponding to the clear text, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>BufferSource
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>BufferSource
+
+
 
 ### decrypt
 
-- <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
+
+
+* <code>decrypt(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the clear data corresponding to the ciphertext, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>BufferSource
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/decrypt#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>BufferSource
+
+
 
 ### sign
 
-- <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
+
+
+* <code>sign(algorithm, key, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with the signature corresponding to the text, algorithm, and key given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>data</code>ArrayBuffer
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>data</code>ArrayBuffer
+
+
 
 ### verify
 
-- <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
-  - Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
+
+
+* <code>verify(algorithm, key, signature, data)</code> : Promise\<boolean>
+
+  * Returns a Promise that fulfills with a Boolean value indicating if the signature given as a parameter matches the text, algorithm, and key that are also given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>signature</code>ArrayBuffer
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/verify#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>signature</code>ArrayBuffer
+
+* <code>data</code>ArrayBuffer
+
 
-- <code>data</code>ArrayBuffer
 
 ### digest
 
-- <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
+
+
+* <code>digest(algorithm, data)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with a digest generated from the algorithm and text given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>string | object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
 
-- <code>data</code>ArrayBuffer
+
+* <code>algorithm</code>string | object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest#Syntax).
+
+* <code>data</code>ArrayBuffer
+
+
 
 ### generateKey
 
-- <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
-  - Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
+
+
+* <code>generateKey(algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey> | Promise\<CryptoKeyPair>
+
+  * Returns a Promise that fulfills with a newly-generated `CryptoKey`, for symmetrical algorithms, or a `CryptoKeyPair`, containing two newly generated keys, for asymmetrical algorithms. For example, to generate a new AES-GCM key:
 
   ```js
   let keyPair = await crypto.subtle.generateKey(
-  	{
-  		name: "AES-GCM",
-  		length: 256,
-  	},
-  	true,
-  	["encrypt", "decrypt"],
+    {
+      name: 'AES-GCM',
+      length: 256,
+    },
+    true,
+    ['encrypt', 'decrypt']
   );
   ```
 
+
+
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Syntax).
+
+
 
 ### deriveKey
 
-- <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
+
+
+* <code>deriveKey(algorithm, baseKey, derivedKeyAlgorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Returns a Promise that fulfills with a newly generated `CryptoKey` derived from the base key and specific algorithm given as parameters.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
 
-- <code>baseKeyCryptoKey</code>
 
-- <code>derivedKeyAlgorithmobject</code>
-  - Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+
+* <code>baseKeyCryptoKey</code>
+
+* <code>derivedKeyAlgorithmobject</code>
+
+  * Defines the algorithm the derived key will be used for in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax).
+
+* <code>extractablebool</code>
+
+* <code>keyUsagesArray</code>
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
-- <code>extractablebool</code>
 
-- <code>keyUsagesArray</code>
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#Syntax)
 
 ### deriveBits
 
-- <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
-  - Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
+
+
+* <code>deriveBits(algorithm, baseKey, length)</code> : Promise\<ArrayBuffer>
+
+  * Returns a Promise that fulfills with a newly generated buffer of pseudo-random bits derived from the base key and specific algorithm given as parameters. It returns a Promise which will be fulfilled with an `ArrayBuffer` containing the derived bits. This method is very similar to `deriveKey()`, except that `deriveKey()` returns a `CryptoKey` object rather than an `ArrayBuffer`. Essentially, `deriveKey()` is composed of `deriveBits()` followed by `importKey()`.
+
+
 
 #### Parameters
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
 
-- <code>baseKey</code>CryptoKey
 
-- <code>length</code>int
-  - Length of the bit string to derive.
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveBits#Syntax).
+
+* <code>baseKey</code>CryptoKey
+
+* <code>length</code>int
+
+  * Length of the bit string to derive.
+
+
 
 ### importKey
 
-- <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
+
+
+* <code>importKey(format, keyData, algorithm, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Transform a key from some external, portable format into a `CryptoKey` for use with the Web Crypto API.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
 
-- <code>keyData</code>ArrayBuffer
 
-- <code>algorithm</code>object
-  - Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+* <code>format</code>string
+
+  * Describes [the format of the key to be imported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+
+* <code>keyData</code>ArrayBuffer
+
+* <code>algorithm</code>object
+
+  * Describes the algorithm to be used, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/importKey#Syntax)
 
 ### exportKey
 
-- <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
-  - Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
+
+
+* <code>exportKey(formatstring, keyCryptoKey)</code> : Promise\<ArrayBuffer>
+
+  * Transform a `CryptoKey` into a portable format, if the `CryptoKey` is `extractable`.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
 
-- <code>key</code>CryptoKey
+
+* <code>format</code>string
+
+  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/exportKey#Syntax).
+
+* <code>key</code>CryptoKey
+
+
 
 ### wrapKey
 
-- <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
-  - Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
+
+
+* <code>wrapKey(format, key, wrappingKey, wrapAlgo)</code> : Promise\<ArrayBuffer>
+
+  * Transform a `CryptoKey` into a portable format, and then encrypt it with another key. This renders the `CryptoKey` suitable for storage or transmission in untrusted environments.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
 
-- <code>key</code>CryptoKey
 
-- <code>wrappingKey</code>CryptoKey
+* <code>format</code>string
+
+  * Describes the [format in which the key will be exported](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax) before being encrypted.
+
+* <code>key</code>CryptoKey
+
+* <code>wrappingKey</code>CryptoKey
+
+* <code>wrapAlgo</code>object
+
+  * Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
+
 
-- <code>wrapAlgo</code>object
-  - Describes the algorithm to be used to encrypt the exported key, including any required parameters, in [an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/wrapKey#Syntax).
 
 ### unwrapKey
 
-- <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
-  - Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
+
+
+* <code>unwrapKey(format, key, unwrappingKey, unwrapAlgo, <br/> unwrappedKeyAlgo, extractable, keyUsages)</code> : Promise\<CryptoKey>
+
+  * Transform a key that was wrapped by `wrapKey()` back into a `CryptoKey`.
+
+
 
 #### Parameters
 
-- <code>format</code>string
-  - Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
 
-- <code>key</code>CryptoKey
 
-- <code>unwrappingKey</code>CryptoKey
+* <code>format</code>string
+
+  * Described the [data format of the key to be unwrapped](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>key</code>CryptoKey
+
+* <code>unwrappingKey</code>CryptoKey
 
-- <code>unwrapAlgo</code>object
-  - Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+* <code>unwrapAlgo</code>object
 
-- <code>unwrappedKeyAlgo</code>object
-  - Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+  * Describes the algorithm that was used to encrypt the wrapped key, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>unwrappedKeyAlgo</code>object
+
+  * Describes the key to be unwrapped, [in an algorithm-specific format](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax).
+
+* <code>extractable</code>bool
+
+* <code>keyUsages</code>Array
+
+  * An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
-- <code>extractable</code>bool
 
-- <code>keyUsages</code>Array
-  - An Array of strings indicating the [possible usages of the new key](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/unwrapKey#Syntax)
 
 ### timingSafeEqual
 
-- <code>timingSafeEqual(a, b)</code> : bool
-  - Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
+
+
+* <code>timingSafeEqual(a, b)</code> : bool
+
+  * Compare two buffers in a way that is resistant to timing attacks. This is a non-standard extension to the Web Crypto API.
+
+
 
 #### Parameters
 
-- <code>a</code>ArrayBuffer | TypedArray
 
-- <code>b</code>ArrayBuffer | TypedArray
+
+* <code>a</code>ArrayBuffer | TypedArray
+
+* <code>b</code>ArrayBuffer | TypedArray
+
+
 
 ### Supported algorithms
 
@@ -351,6 +511,8 @@ A checkmark (✓) indicates that this feature is believed to be fully supported
 An x (✘) indicates that this feature is part of the specification but not implemented.<br/>
 If a feature only implements the operation partially, details are listed.
 
+
+
 | Algorithm                                          | sign()<br/>verify() | encrypt()<br/>decrypt() | digest() | deriveBits()<br/>deriveKey() | generateKey() | wrapKey()<br/>unwrapKey() | exportKey() | importKey() |
 | :------------------------------------------------- | :------------------ | :---------------------- | :------- | :--------------------------- | :------------ | :------------------------ | :---------- | :---------- |
 | RSASSA PKCS1 v1.5                                  | ✓                   |                         |          |                              | ✓             |                           | ✓           | ✓           |
@@ -374,27 +536,24 @@ If a feature only implements the operation partially, details are listed.
 | HKDF                                               |                     |                         |          | ✓                            |               |                           |             | ✓           |
 | PBKDF2                                             |                     |                         |          | ✓                            |               |                           |             | ✓           |
 
+
+
 **Footnotes:**
 
-1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves
-   API](https://wicg.github.io/webcrypto-secure-curves).
+1. <a name="footnote-1"></a> Algorithms as specified in the [Secure Curves API](https://wicg.github.io/webcrypto-secure-curves).
 
-2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the
-   Ed25519 curve in addition to the Secure Curves version. Since this algorithm
-   is non-standard, note the following while using it:
-   - Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
-   - Unlike NodeJS, Cloudflare will not support raw import of private keys.
-   - The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
+2. <a name="footnote-2"></a> Legacy non-standard EdDSA is supported for the Ed25519 curve in addition to the Secure Curves version. Since this algorithm is non-standard, note the following while using it:
 
-3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is
-   supported in Cloudflare Workers for interacting with legacy systems that
-   require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for
-   security.
+   * Use <code>NODE-ED25519</code> as the algorithm and `namedCurve` parameters.
+   * Unlike NodeJS, Cloudflare will not support raw import of private keys.
+   * The algorithm implementation may change over time. While Cloudflare cannot guarantee it at this time, Cloudflare will strive to maintain backward compatibility and compatibility with NodeJS's behavior. Any notable compatibility notes will be communicated in release notes and via this developer documentation.
 
----
+3. <a name="footnote-3"></a> MD5 is not part of the WebCrypto standard but is supported in Cloudflare Workers for interacting with legacy systems that require MD5. MD5 is considered a weak algorithm. Do not rely upon MD5 for security.
+
+***
 
 ## Related resources
 
-- [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
-- [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
-- [Example: signing requests](/workers/examples/signing-requests/)
+* [SubtleCrypto documentation on MDN](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto)
+* [SubtleCrypto documentation as part of the W3C Web Crypto API specification](https://www.w3.org/TR/WebCryptoAPI//#subtlecrypto-interface)
+* [Example: signing requests](/workers/examples/signing-requests/)
diff --git a/src/content/docs/workers/runtime-apis/webassembly/index.mdx b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
index 492c0ae788ec4ea..d4a1cb8a2d546a5 100644
--- a/src/content/docs/workers/runtime-apis/webassembly/index.mdx
+++ b/src/content/docs/workers/runtime-apis/webassembly/index.mdx
@@ -9,18 +9,18 @@ products:
   - workers
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 [WebAssembly](https://webassembly.org/) (abbreviated Wasm) allows you to compile languages like [Rust](/workers/languages/rust/), Go, or C to a binary format that can run in a wide variety of environments, including [web browsers](https://developer.mozilla.org/en-US/docs/WebAssembly#browser_compatibility), Cloudflare Workers, and other WebAssembly runtimes.
 
 You can use WebAssembly to:
 
-- Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
-  :::note
-  `WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
-  :::
+* Execute code written in a language other than JavaScript, via `WebAssembly.instantiate()`.
+	:::note
+		`WebAssembly.instantiate()` only supports pre-compiled modules as documented in the [web-standards documentation](/workers/runtime-apis/web-standards/#javascript-standards).
+	:::
 
-- Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
+* Write an entire Cloudflare Worker in Rust, using bindings that make Workers' JavaScript APIs available directly from your Rust code.
 
 Most programming languages can be compiled to Wasm, although support varies across languages and compilers. Guides are available for the following languages:
 
@@ -50,5 +50,5 @@ WASI is an earlier and more rapidly evolving set of standards than Wasm. WASI su
 
 ### Resources on WebAssembly
 
-- [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
-- [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
+* [Serverless Rust with Cloudflare Workers](https://blog.cloudflare.com/cloudflare-workers-as-a-serverless-rust-platform/)
+* [WebAssembly on Cloudflare Workers](https://blog.cloudflare.com/webassembly-on-cloudflare-workers/)
diff --git a/src/content/docs/workers/runtime-apis/websockets.mdx b/src/content/docs/workers/runtime-apis/websockets.mdx
index bf31fea43cc174c..6178ac08aa6b4b7 100644
--- a/src/content/docs/workers/runtime-apis/websockets.mdx
+++ b/src/content/docs/workers/runtime-apis/websockets.mdx
@@ -14,8 +14,10 @@ WebSockets allow you to communicate in real time with your Cloudflare Workers se
 
 :::note
 
+
 If your application needs to coordinate among multiple WebSocket connections, such as a chat room or game match, you will need clients to send messages to a single-point-of-coordination. Durable Objects provide a single-point-of-coordination for Cloudflare Workers, and are often used in parallel with WebSockets to persist state over multiple clients and connections. In this case, refer to [Durable Objects](/durable-objects/) to get started, and prefer using the Durable Objects' extended [WebSockets API](/durable-objects/best-practices/websockets/).
 
+
 :::
 
 ## Constructor
@@ -37,97 +39,148 @@ let [client, server] = Object.values(new WebSocketPair());
 
 ### accept
 
-- <code>accept(options?)</code>
-  - Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
+
+
+* <code>accept(options?)</code>
+
+  * Accepts the WebSocket connection and begins terminating requests for the WebSocket on Cloudflare's global network. This effectively enables the Workers runtime to begin responding to and handling WebSocket requests.
 
 #### Parameters
 
-- `options` object optional
-  - An optional configuration object with the following properties:
-    - `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
+
+
+* `options` object optional
+
+  * An optional configuration object with the following properties:
+
+    * `allowHalfOpen` boolean optional — When `true`, the runtime will not automatically send a reciprocal Close frame when a Close frame is received from the peer. Instead, `readyState` remains `CLOSING` until you explicitly call `close()`. This is useful for [WebSocket proxying](#close-behavior) where you need to coordinate the close across both sides of the proxy. Defaults to `false`.
+
+
 
 ### addEventListener
 
-- <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
-  - Add callback functions to be executed when an event has occurred on the WebSocket.
+
+
+* <code>addEventListener(eventWebSocketEvent, callbackFunctionFunction)</code>
+
+  * Add callback functions to be executed when an event has occurred on the WebSocket.
+
+
 
 #### Parameters
 
-- `event` WebSocketEvent
-  - The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
 
-- <code>callbackFunction(messageMessage)</code> Function
-  - A function to be called when the WebSocket responds to a specific event.
+
+* `event` WebSocketEvent
+
+  * The WebSocket event (refer to [Events](/workers/runtime-apis/websockets/#events)) to listen to.
+
+* <code>callbackFunction(messageMessage)</code> Function
+
+  * A function to be called when the WebSocket responds to a specific event.
+
+
 
 ### close
 
-- <code>close(codenumber, reasonstring)</code>
-  - Close the WebSocket connection.
+
+
+* <code>close(codenumber, reasonstring)</code>
+
+  * Close the WebSocket connection.
+
+
 
 #### Parameters
 
-- <code>codeinteger</code> optional
-  - An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
 
-- <code>reasonstring</code> optional
-  - A human-readable string indicating why the WebSocket connection was closed.
+
+* <code>codeinteger</code> optional
+
+  * An integer indicating the close code sent by the server. This should match an option from the [list of status codes](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#status_codes) provided by the WebSocket spec.
+
+* <code>reasonstring</code> optional
+
+  * A human-readable string indicating why the WebSocket connection was closed.
+
+
 
 ### send
 
-- <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
-  - Send a message to the other WebSocket in this WebSocket pair.
+
+
+* <code>send(messagestring | ArrayBuffer | ArrayBufferView)</code>
+
+  * Send a message to the other WebSocket in this WebSocket pair.
+
+
 
 #### Parameters
 
-- <code>messagestring</code>
-  - The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
 
----
+
+* <code>messagestring</code>
+
+  * The message to send down the WebSocket connection to the corresponding client. This should be a string or something coercible into a string; for example, strings and numbers will be simply cast into strings, but objects and arrays should be cast to JSON strings using <code>JSON.stringify</code>, and parsed in the client.
+
+
+
+***
 
 ## Properties
 
 ### readyState
 
-- `readyState` number
-  - Returns the current state of the WebSocket connection. Possible values:
+* `readyState` number
 
-    | Constant               | Value | Description                                      |
-    | ---------------------- | ----- | ------------------------------------------------ |
-    | `WebSocket.CONNECTING` | `0`   | The connection is not yet open.                  |
-    | `WebSocket.OPEN`       | `1`   | The connection is open and ready to communicate. |
-    | `WebSocket.CLOSING`    | `2`   | The connection is in the process of closing.     |
-    | `WebSocket.CLOSED`     | `3`   | The connection is closed.                        |
+  * Returns the current state of the WebSocket connection. Possible values:
+
+    | Constant | Value | Description |
+    | --- | --- | --- |
+    | `WebSocket.CONNECTING` | `0` | The connection is not yet open. |
+    | `WebSocket.OPEN` | `1` | The connection is open and ready to communicate. |
+    | `WebSocket.CLOSING` | `2` | The connection is in the process of closing. |
+    | `WebSocket.CLOSED` | `3` | The connection is closed. |
 
 ### binaryType
 
-- `binaryType` string
-  - Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+* `binaryType` string
 
----
+  * Controls how binary frames received on this WebSocket are surfaced to the `message` event. Valid values are `"blob"` and `"arraybuffer"`. The value is consulted when each incoming binary frame is dispatched, so assigning a new value affects subsequent messages only. The default is controlled by the [`websocket_standard_binary_type`](/workers/configuration/compatibility-flags/#websocket-standard-binary-type) compatibility flag. Refer to [Binary messages](#binary-messages) for details.
+
+***
 
 ## Events
 
-- <code>close</code>* An event indicating the WebSocket has closed. The
-  `CloseEvent` includes `code` (number), `reason` (string), and `wasClean`
-  (boolean) properties.
 
-- <code>error</code>* An event indicating there was an error with the WebSocket.
 
-- <code>message</code>
-  - An event indicating a new message received from the client, including the data passed by the client.
+* <code>close</code>
+  * An event indicating the WebSocket has closed. The `CloseEvent` includes `code` (number), `reason` (string), and `wasClean` (boolean) properties.
+
+* <code>error</code>
+  * An event indicating there was an error with the WebSocket.
+
+* <code>message</code>
+  * An event indicating a new message received from the client, including the data passed by the client.
+
+
 
 :::note
-WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes). If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
+WebSocket messages received by a Worker have a size limit of 32 MiB (33,554,432 bytes).  If a larger message is sent, the WebSocket will be automatically closed with a `1009` "Message is too large" response.
 :::
 
 ## Types
 
 ### Message
 
-- `data` any - The data passed back from the other WebSocket in your pair.
-- `type` string - Defaults to `message`.
 
----
+
+* `data` any - The data passed back from the other WebSocket in your pair.
+* `type` string - Defaults to `message`.
+
+
+
+***
 
 ## Close behavior
 
@@ -137,10 +190,10 @@ If you still call `close()` inside the `close` event handler, the call is silent
 
 ```js
 server.addEventListener("close", (event) => {
-	// readyState is already CLOSED — no need to call server.close().
-	console.log(server.readyState); // WebSocket.CLOSED
-	console.log(event.code); // 1000
-	console.log(event.wasClean); // true
+  // readyState is already CLOSED — no need to call server.close().
+  console.log(server.readyState); // WebSocket.CLOSED
+  console.log(event.code);        // 1000
+  console.log(event.wasClean);    // true
 });
 ```
 
@@ -152,12 +205,12 @@ The automatic close behavior can interfere with WebSocket proxying, where a Work
 server.accept({ allowHalfOpen: true });
 
 server.addEventListener("close", (event) => {
-	// readyState is still CLOSING here, giving you time
-	// to coordinate the close on the other side.
-	console.log(server.readyState); // WebSocket.CLOSING
+  // readyState is still CLOSING here, giving you time
+  // to coordinate the close on the other side.
+  console.log(server.readyState); // WebSocket.CLOSING
 
-	// Manually close when ready.
-	server.close(event.code, "done");
+  // Manually close when ready.
+  server.close(event.code, "done");
 });
 ```
 
@@ -171,7 +224,7 @@ WebSockets created with `new WebSocket(url)` always auto-reply to Close frames a
 
 On compatibility dates before `2026-04-07` (or with the `web_socket_manual_reply_to_close` flag), receiving a Close frame leaves the WebSocket in `CLOSING` state, and your code must call `close()` to complete the handshake. Failing to do so can result in `1006` abnormal closure errors on the client.
 
----
+***
 
 ## Binary messages
 
@@ -183,7 +236,7 @@ The `binaryType` property itself is always available. To opt back into `ArrayBuf
 
 ```js
 const resp = await fetch("https://example.com", {
-	headers: { Upgrade: "websocket" },
+  headers: { Upgrade: "websocket" },
 });
 const ws = resp.webSocket;
 
@@ -192,11 +245,11 @@ ws.binaryType = "arraybuffer";
 ws.accept();
 
 ws.addEventListener("message", (event) => {
-	if (typeof event.data === "string") {
-		// Text frame.
-	} else {
-		// event.data is an ArrayBuffer because we set binaryType above.
-	}
+  if (typeof event.data === "string") {
+    // Text frame.
+  } else {
+    // event.data is an ArrayBuffer because we set binaryType above.
+  }
 });
 ```
 
@@ -223,9 +276,9 @@ This flag has no effect on the Durable Object hibernatable WebSocket [`webSocket
 
 :::
 
----
+***
 
 ## Related resources
 
-- [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
-- [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
+* [Mozilla Developer Network's (MDN) documentation on the WebSocket class](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
+* [Our WebSocket template for building applications on Workers using WebSockets](https://github.com/cloudflare/websocket-template)
diff --git a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
index 0ba52cb42d3e81a..31e081797dd1ada 100644
--- a/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
+++ b/src/content/docs/workers/static-assets/routing/full-stack-application.mdx
@@ -14,7 +14,10 @@ Full-stack applications are web applications which are span both the client and
 
 The following full-stack frameworks are natively supported by Workers:
 
-<DirectoryListing folder="workers/framework-guides/web-apps" tag="full-stack" />
+<DirectoryListing
+	folder="workers/framework-guides/web-apps"
+	tag="full-stack"
+/>
 <DirectoryListing
 	folder="workers/framework-guides/web-apps/more-web-frameworks"
 	tag="full-stack"
diff --git a/src/content/docs/workers/testing/miniflare/storage/cache.md b/src/content/docs/workers/testing/miniflare/storage/cache.md
index c7c385b4cbe8025..78aac412fb542af 100644
--- a/src/content/docs/workers/testing/miniflare/storage/cache.md
+++ b/src/content/docs/workers/testing/miniflare/storage/cache.md
@@ -86,9 +86,7 @@ console.log(await res.text()); // 2
 You can programmatically purge all entries from a cache using the `purgeCache` method on the `Miniflare` instance. This is useful during development when cached assets need to be cleared without restarting the instance:
 
 ```js
-const mf = new Miniflare({
-	/* options */
-});
+const mf = new Miniflare({ /* options */ });
 
 // Purge the default cache and get the number of entries purged
 const count = await mf.purgeCache();
diff --git a/src/content/docs/workers/testing/vitest-integration/recipes.mdx b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
index d125b33d9e53931..79fb21b23ea73f1 100644
--- a/src/content/docs/workers/testing/vitest-integration/recipes.mdx
+++ b/src/content/docs/workers/testing/vitest-integration/recipes.mdx
@@ -30,4 +30,4 @@ Recipes are examples that help demonstrate how to write unit tests and integrati
 - [Resolving modules with Vite Dependency Pre-Bundling](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/module-resolution)
 - [Mocking Workers AI and Vectorize bindings in unit tests](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/ai-vectorize)
 - [Tests using the Images binding](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/images)
-- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
+- [Tests mocking Workers Assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
\ No newline at end of file
diff --git a/src/content/docs/workers/vite-plugin/tutorial.mdx b/src/content/docs/workers/vite-plugin/tutorial.mdx
index ef7f05b8c086add..c5b6e9446a92aa4 100644
--- a/src/content/docs/workers/vite-plugin/tutorial.mdx
+++ b/src/content/docs/workers/vite-plugin/tutorial.mdx
@@ -205,7 +205,6 @@ This opts out of interpreting the `Sec-Fetch-Mode` header.
 ```
 
 </WranglerConfig>
-
 :::
 
 ### Call the API from the client
diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx
index ccabcb8262755a1..8b28f295cdc13b8 100644
--- a/src/content/docs/workers/wrangler/api.mdx
+++ b/src/content/docs/workers/wrangler/api.mdx
@@ -50,7 +50,9 @@ const result = await experimental_generateTypes(options);
 ### Parameters
 
 - `options` <Type text="object" /> <MetaInfo text="optional" />
+
   - Optional options object mirroring the `wrangler types` CLI flags:
+
     - `config` `string | string[]`
 
       Path to the Wrangler configuration file to use. Can be an array for multi-config type resolution.
@@ -88,15 +90,19 @@ const result = await experimental_generateTypes(options);
 `experimental_generateTypes()` returns a `Promise` resolving to an object containing the following fields:
 
 - `content` `string`
+
   - Combined formatted output containing all generated sections, including headers and both env and runtime types.
 
 - `env` `string | null`
+
   - Generated environment and bindings types, or `null` when env types are excluded.
 
 - `path` `string`
+
   - Target declaration file path associated with this generation run.
 
 - `runtime` `string | null`
+
   - Generated runtime types, or `null` when runtime types are excluded.
 
 ### Usage
@@ -500,22 +506,22 @@ The bindings supported by `getPlatformProxy` are:
     For example, you might have the following binding in a Wrangler configuration file read by `getPlatformProxy`.
 
     <WranglerConfig>
-                
-                    ```jsonc
-                    {
-                      "durable_objects": {
-                        "bindings": [
-                          {
-                            "name": "MyDurableObject",
-                            "class_name": "MyDurableObject",
-                            "script_name": "external-do-worker"
-                          }
-                        ]
+            
+                ```jsonc
+                {
+                  "durable_objects": {
+                    "bindings": [
+                      {
+                        "name": "MyDurableObject",
+                        "class_name": "MyDurableObject",
+                        "script_name": "external-do-worker"
                       }
-                    }
-                    ```
-                
-                    </WranglerConfig>
+                    ]
+                  }
+                }
+                ```
+            
+                </WranglerConfig>
 
     You will need to declare your Durable Object `"MyDurableObject"` in another Worker, called `external-do-worker` in this example.
 
@@ -535,14 +541,14 @@ The bindings supported by `getPlatformProxy` are:
     That Worker also needs a Wrangler configuration file that looks like this:
 
     <WranglerConfig>
-                        ```json
-                        {
-                        	"name": "external-do-worker",
-                        	"main": "src/index.ts",
-                        	"compatibility_date": "XXXX-XX-XX"
-                        }
-                        ```
-                        </WranglerConfig>
+                    ```json
+                    {
+                    	"name": "external-do-worker",
+                    	"main": "src/index.ts",
+                    	"compatibility_date": "XXXX-XX-XX"
+                    }
+                    ```
+                    </WranglerConfig>
 
     If you are not using RPC with your Durable Object, you can run a separate Wrangler dev session alongside your framework development server.
 
diff --git a/src/content/docs/workers/wrangler/commands/r2.mdx b/src/content/docs/workers/wrangler/commands/r2.mdx
index fb437a18a9717a9..60266e3b8e29b81 100644
--- a/src/content/docs/workers/wrangler/commands/r2.mdx
+++ b/src/content/docs/workers/wrangler/commands/r2.mdx
@@ -10,6 +10,7 @@ import { Render } from "~/components";
 
 Manage your [R2](/r2/) configurations using Wrangler.
 
+
 <Render file="wrangler-commands/r2" product="workers" />
 
 ## R2 SQL
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
index d19eda7c7872fca..f32639e194e9391 100644
--- a/src/content/docs/workers/wrangler/configuration.mdx
+++ b/src/content/docs/workers/wrangler/configuration.mdx
@@ -1839,26 +1839,26 @@ A common example of using a redirected configuration is where a custom build too
 - First, the user writes code that uses Cloudflare Workers resources, configured via a user's Wrangler configuration file like the following:
 
   <WranglerConfig>
-  
-    ```jsonc
-    {
-    	"$schema": "./node_modules/wrangler/config-schema.json",
-    	"name": "my-worker",
-    	"main": "src/index.ts",
-    	"vars": {
-    		"MY_VARIABLE": "production variable",
-    	},
-    	"env": {
-    		"staging": {
-    			"vars": {
-    				"MY_VARIABLE": "staging variable",
-    			},
-    		},
-    	},
-    }
-    ```
-  
-    </WranglerConfig>
+
+  ```jsonc
+  {
+  	"$schema": "./node_modules/wrangler/config-schema.json",
+  	"name": "my-worker",
+  	"main": "src/index.ts",
+  	"vars": {
+  		"MY_VARIABLE": "production variable",
+  	},
+  	"env": {
+  		"staging": {
+  			"vars": {
+  				"MY_VARIABLE": "staging variable",
+  			},
+  		},
+  	},
+  }
+  ```
+
+  </WranglerConfig>
 
   This configuration points `main` at the user's code entry-point and defines the `MY_VARIABLE` variable in two different environments.
 
@@ -1872,8 +1872,8 @@ A common example of using a redirected configuration is where a custom build too
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>
-    	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
-    </FileTree>
+  	- dist - index.js - wrangler.jsonc - .wrangler - deploy - config.json
+  </FileTree>
 
 The generated `dist/wrangler.jsonc` might contain:
 
@@ -1896,4 +1896,4 @@ And the `.wrangler/deploy/config.json` contains the path to the generated config
 {
 	"configPath": "../../dist/wrangler.jsonc"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/workers/wrangler/custom-builds.mdx b/src/content/docs/workers/wrangler/custom-builds.mdx
index e22e4bc6c269534..0b63ae3bd2a8037 100644
--- a/src/content/docs/workers/wrangler/custom-builds.mdx
+++ b/src/content/docs/workers/wrangler/custom-builds.mdx
@@ -21,12 +21,15 @@ Wrangler runs [esbuild](https://esbuild.github.io/) by default as part of the `d
 Custom builds are configured by adding a `[build]` section in your [Wrangler configuration file](/workers/wrangler/configuration/), and using the following options for configuring your custom build.
 
 - `command` <Type text="string" /> <MetaInfo text="optional" />
+
   - The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used. This command will be run as part of `wrangler dev` and `npx wrangler deploy`.
 
 - `cwd` <Type text="string" /> <MetaInfo text="optional" />
+
   - The directory in which the command is executed.
 
 - `watch_dir` <Type text="string | string\[]" /> <MetaInfo text="optional" />
+
   - The directory to watch for changes while using `wrangler dev`. Defaults to the current working directory.
 
 Example:
@@ -51,12 +54,12 @@ When Wrangler runs your custom build command, it sets the `WRANGLER_COMMAND` env
 
 The possible values are:
 
-| Value             | Wrangler command triggered |
-| ----------------- | -------------------------- |
-| `dev`             | `wrangler dev`             |
-| `deploy`          | `wrangler deploy`          |
-| `versions upload` | `wrangler versions upload` |
-| `types`           | `wrangler types`           |
+| Value              | Wrangler command triggered               |
+| ------------------ | ---------------------------------------- |
+| `dev`              | `wrangler dev`                           |
+| `deploy`           | `wrangler deploy`                        |
+| `versions upload`  | `wrangler versions upload`               |
+| `types`            | `wrangler types`                         |
 
 For example, you can use this to apply different build settings for development and production:
 
diff --git a/src/content/docs/workers/wrangler/deprecations.mdx b/src/content/docs/workers/wrangler/deprecations.mdx
index ab606324004172b..3b4d23ccc8c99eb 100644
--- a/src/content/docs/workers/wrangler/deprecations.mdx
+++ b/src/content/docs/workers/wrangler/deprecations.mdx
@@ -83,89 +83,82 @@ This no longer has any effect, after the [rollout of Workers Standard Pricing](h
 
 Wrangler v2 introduces new fields for configuration and new features for developing and deploying a Worker, while deprecating some redundant fields.
 
-- `wrangler.toml` is no longer mandatory.
-- `dev` and `publish` accept CLI arguments.
-- `tail` can be run on arbitrary Worker names.
-- `init` creates a project boilerplate.
-- JSON bindings for `vars`.
-- Local mode for `wrangler dev`.
-- Module system (for both modules and service worker format Workers).
-- DevTools.
-- TypeScript support.
-- Sharing development environment on the Internet.
-- Wider platform compatibility.
-- Developer hotkeys.
-- Better configuration validation.
+* `wrangler.toml` is no longer mandatory.
+* `dev` and `publish` accept CLI arguments.
+* `tail` can be run on arbitrary Worker names.
+* `init` creates a project boilerplate.
+* JSON bindings for `vars`.
+* Local mode for `wrangler dev`.
+* Module system (for both modules and service worker format Workers).
+* DevTools.
+* TypeScript support.
+* Sharing development environment on the Internet.
+* Wider platform compatibility.
+* Developer hotkeys.
+* Better configuration validation.
 
 The following video describes some of the major changes in Wrangler v2, and shows you how Wrangler v2 can help speed up your workflow.
 
-<div style="position: relative; padding-top: 56.25%;">
-	<iframe
-		src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600"
-		style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;"
-		allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
-		allowfullscreen="true"
-	></iframe>
-</div>
+<div style="position: relative; padding-top: 56.25%;"><iframe src="https://iframe.videodelivery.net/6ce3c7bd51288e1e8439f50ad63eda1d?poster=https%3A%2F%2Fcloudflarestream.com%2F6ce3c7bd51288e1e8439f50ad63eda1d%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600" style="border: none; position: absolute; top: 0; left: 0; height: 100%; width: 100%;" allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;" allowfullscreen="true"></iframe></div>
 
 ### Common deprecations
 
 Refer to the following list for common fields that are no longer required.
 
-- `type` is no longer required. Wrangler will infer the correct project type automatically.
-- `zone_id` is no longer required. It can be deduced from the routes directly.
-- `build.upload.format` is no longer used. The format is now inferred automatically from the code.
-- `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
-- `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
-- `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
+* `type` is no longer required. Wrangler will infer the correct project type automatically.
+* `zone_id` is no longer required. It can be deduced from the routes directly.
+* `build.upload.format` is no longer used. The format is now inferred automatically from the code.
+* `build.upload.main` and `build.upload.dir` are no longer required. Use the top level `main` field, which now serves as the entry-point for the Worker.
+* `site.entry-point` is no longer required. The entry point should be specified through the `main` field.
+* `webpack_config` and `webpack` properties are no longer supported. Refer to [Migrate webpack projects from Wrangler version 1](/workers/wrangler/migration/v1-to-v2/eject-webpack/).
   Here are the Wrangler v1 commands that are no longer supported:
-- `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
-- `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
-- `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
-- `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
-- `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
+* `wrangler preview` - Use the `wrangler dev` command, for running your worker in your local environment.
+* `wrangler generate` - If you want to use a starter template, clone its GitHub repository and manually initialize it.
+* `wrangler route` - Routes are defined in the [Wrangler configuration file](/workers/wrangler/configuration/).
+* `wrangler report` - If you find a bug, report it at [Wrangler issues](https://github.com/cloudflare/workers-sdk/issues/new/choose).
+* `wrangler build` - If you wish to access the output from bundling your Worker, use `wrangler deploy --outdir=path/to/output`.
 
 #### New fields
 
 These are new fields that can be added to your [Wrangler configuration file](/workers/wrangler/configuration/).
 
-- **`main`**: `string`, optional
+* **`main`**: `string`, optional
 
   The `main` field is used to specify an entry point to the Worker. It may be in the established service worker format, or the newer, preferred modules format. An entry point is now explicitly required, and can be configured either via the `main` field, or passed directly as a command line, for example, `wrangler dev index.js`. This field replaces the legacy `build.upload.main` field (which only applied to modules format Workers).
 
-- **`rules`**: `array`, optional
+* **`rules`**: `array`, optional
 
   The `rules` field is an array of mappings between module types and file patterns. It instructs Wrangler to interpret specific files differently than JavaScript. For example, this is useful for reading text-like content as text files, or compiled WASM as ready to instantiate and execute. These rules can apply to Workers of both the established service worker format, and the newer modules format. This field replaces the legacy `build.upload.rules` field (which only applied to modules format Workers).
 
-{/\* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
+{/* <!-- - **`legacy_env`**: _boolean_, optional. default: `true`
 
-The `legacy_env` field toggles how environments are handled by `wrangler`.
+  The `legacy_env` field toggles how environments are handled by `wrangler`.
 
-- When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
-- When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
-  Read more at (ref:)[] --> \*/}
+  - When `legacy_env` is `true`, it uses the legacy-style environments, where each environment is treated as a separate Worker in the dashboard, and environment names are appended to the `name` when published.
+  - When `legacy_env` is `false`, it uses the newer service environments, where scripts for a given Worker are grouped under the same script name in the Cloudflare Workers dashboard, and environments are subdomains for a given published script (when `workers_dev = true`).
+    Read more at (ref:)[] --> */}
 
-{/\* <!-- - **`services`**: TODO
+{/* <!-- - **`services`**: TODO
 
 - **`node-compat`**: TODO
 
-- **`public`**: TODO --> \*/}
+- **`public`**: TODO --> */}
 
 #### Non-mandatory fields
 
 A few configuration fields which were previously required, are now optional in particular situations. They can either be inferred, or added as an optimization. No fields are required anymore when starting with Wrangler v2, and you can gradually add configuration as the need arises.
 
-- **`name`**: `string`
+* **`name`**: `string`
 
   The `name` configuration field is now not required for `wrangler dev`, or any of the `wrangler kv:*` commands. Further, it can also be passed as a command line argument as `--name <name>`. It is still required for `wrangler deploy`.
 
-- **`account_id`**: `string`
+* **`account_id`**: `string`
 
   The `account_id` field is not required for any of the commands. Any relevant commands will check if you are logged in, and if not, will prompt you to log in. Once logged in, it will use your account ID and will not prompt you again until your login session expires. If you have multiple account IDs, you will be presented with a list of accounts to choose from.
 
   You can still configure `account_id` in your Wrangler file, or as an environment variable `CLOUDFLARE_ACCOUNT_ID`. This makes startup faster and bypasses the list of choices if you have multiple IDs. The `CLOUDFLARE_API_TOKEN` environment variable is also useful for situations where it is not possible to login interactively. To learn more, visit [Running in CI/CD](/workers/ci-cd/external-cicd/).
 
-- **`workers_dev`** `boolean`, default: `true` when no routes are present
+* **`workers_dev`** `boolean`, default: `true` when no routes are present
 
   The `workers_dev` field is used to indicate that the Worker should be published to a `*.workers.dev` subdomain. For example, for a Worker named `my-worker` and a previously configured `*.workers.dev` subdomain `username`, the Worker will get published to `my-worker.username.workers.dev.com`. This field is not mandatory, and defaults to `true` when `route` or `routes` are not configured. When routes are present, it defaults to `false`. If you want to neither publish it to a `*.workers.dev` subdomain nor any routes, set `workers_dev` to `false`. This useful when you are publishing a Worker as a standalone service that can only be accessed from another Worker with (`services`).
 
@@ -173,26 +166,27 @@ A few configuration fields which were previously required, are now optional in p
 
 A few configuration fields are deprecated, but their presence is not a breaking change yet. It is recommended to read the warning messages and follow the instructions to migrate to the new configuration. They will be removed and stop working in a future version.
 
-- **`zone_id`**: `string`, deprecated
+* **`zone_id`**: `string`, deprecated
 
   The `zone_id` field is deprecated and will be removed in a future release. It is now inferred from `route`/`routes`, and optionally from `dev.host` when using `wrangler dev`. This also makes it simpler to deploy a single Worker to multiple domains.
 
-- **`build.upload`**: `object`, deprecated
+* **`build.upload`**: `object`, deprecated
 
   The `build.upload` field is deprecated and will be removed in a future release. Its usage results in a warning with suggestions on rewriting the configuration file to remove the warnings.
-  - `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
-  - `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
-  - `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
+
+  * `build.upload.main`/`build.upload.dir` are replaced by the `main` fields and are applicable to both service worker format and modules format Workers.
+  * `build.upload.rules` is replaced by the `rules` field and is applicable to both service worker format and modules format Workers.
+  * `build.upload.format` is no longer specified and is automatically inferred by `wrangler`.
 
 #### Deprecated fields (breaking)
 
 A few configuration fields are deprecated and will not work as expected anymore. It is recommended to read the error messages and follow the instructions to migrate to the new configuration.
 
-- **`site.entry-point`**: `string`, deprecated
+* **`site.entry-point`**: `string`, deprecated
 
   The `site.entry-point` configuration was used to specify an entry point for Workers with a `[site]` configuration. This has been replaced by the top-level `main` field.
 
-- **`type`**: `rust` | `javascript` | `webpack`, deprecated
+* **`type`**: `rust` | `javascript` | `webpack`, deprecated
 
   The `type` configuration was used to specify the type of Worker. It has since been made redundant and is now inferred from usage. If you were using `type = "webpack"` (and the optional `webpack_config` field), you should read the [webpack migration guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to modify your project and use a custom build instead.
 
@@ -232,11 +226,11 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 ### Other deprecated behavior
 
-- Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
+* Cloudflare dashboard-defined routes will not be added alongside Wrangler-defined routes. Wrangler-defined routes are the `route` or `routes` key in your `wrangler.toml`. If both are defined, only routes defined in `wrangler.toml` will be valid. To manage routes via the Cloudflare dashboard only, remove any `route` and `routes` keys from and add `workers_dev = false` to your Wrangler file.
 
-- Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
+* Wrangler will no longer use `index.js` in the directory where `wrangler dev` is called as the entry point to a Worker. Use the `main` configuration field, or explicitly pass it as a command line argument, for example: `wrangler dev index.js`.
 
-- Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
+* Wrangler will no longer assume that bare specifiers are file names if they are not represented as a path. For example, in a folder like so:
 
   ```
   project
@@ -250,7 +244,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
   import SomeDependency from "some-dependency.js";
 
   addEventListener("fetch", (event) => {
-  	// ...
+    // ...
   });
   ```
 
@@ -265,8 +259,8 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Commands
 
-| Command     | v1  | v2  | Notes                                          |
-| ----------- | --- | --- | ---------------------------------------------- |
+| Command     | v1 | v2 | Notes                                          |
+| ----------- | -- | -- | ---------------------------------------------- |
 | `publish`   | ✅  | ✅  |                                                |
 | `dev`       | ✅  | ✅  |                                                |
 | `preview`   | ✅  | ❌  | Removed, use `dev` instead.                    |
@@ -277,7 +271,7 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 | `route`     | ✅  | ❌  | Removed, use `publish` instead.                |
 | `tail`      | ✅  | ✅  |                                                |
 | `kv`        | ✅  | ✅  |                                                |
-| `r2`        | 🚧  | ✅  | Introduced in Wrangler v1.19.8.                |
+| `r2`        | 🚧 | ✅  | Introduced in Wrangler v1.19.8.                |
 | `pages`     | ❌  | ✅  |                                                |
 | `config`    | ✅  | ❓  |                                                |
 | `login`     | ✅  | ✅  |                                                |
@@ -288,15 +282,15 @@ Routes are specified in the [Wrangler configuration file](/workers/wrangler/conf
 
 #### Configuration
 
-| Property              | v1  | v2  | Notes                                                                                           |
-| --------------------- | --- | --- | ----------------------------------------------------------------------------------------------- |
+| Property              | v1 | v2 | Notes                                                                                                                                            |
+| --------------------- | -- | -- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `type = "webpack"`    | ✅  | ❌  | Removed, refer to [this guide](/workers/wrangler/migration/v1-to-v2/eject-webpack/) to migrate. |
-| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                  |
-| `type = "javascript"` | ✅  | 🚧  | No longer required, can be omitted.                                                             |
+| `type = "rust"`       | ✅  | ❌  | Removed, use [`workers-rs`](https://github.com/cloudflare/workers-rs) instead.                                                                   |
+| `type = "javascript"` | ✅  | 🚧 | No longer required, can be omitted.                                                                                                              |
 
 #### Features
 
-| Feature    | v1  | v2  | Notes                                                                                                                                                                                                 |
-| ---------- | --- | --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Feature    | v1 | v2 | Notes                                                                                                                                                                                                 |
+| ---------- | -- | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | TypeScript | ❌  | ✅  | You can give wrangler a TypeScript file, and it will automatically transpile it to JavaScript using [`esbuild`](https://github.com/evanw/esbuild) under-the-hood.                                     |
 | Local mode | ❌  | ✅  | `wrangler dev --local` will run your Worker on your local machine instead of on our network. This is powered by [Miniflare](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare/). |
diff --git a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
index 6f633bb98248e76..8092bb1422993dd 100644
--- a/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
+++ b/src/content/docs/workers/wrangler/migration/update-v2-to-v3.mdx
@@ -12,8 +12,10 @@ There are no special instructions for migrating from Wrangler v2 to v3. You shou
 
 :::caution
 
+
 If you tried to update to Wrangler v3 prior to v3.3, you may have experienced some compatibility issues with older operating systems. Please try again with the latest v3 where those have been resolved.
 
+
 :::
 
 ## Deprecations
diff --git a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
index a700b3c6cef0bbc..5c0712ab06b89e5 100644
--- a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
+++ b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
@@ -12,13 +12,7 @@ products:
   - workers
 ---
 
-import {
-	Render,
-	Type,
-	MetaInfo,
-	WranglerConfig,
-	DashButton,
-} from "~/components";
+import { Render, Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
 
 <Render file="wrangler-v1-deprecation" product="workers" />
 
diff --git a/src/content/docs/workflows/build/index.mdx b/src/content/docs/workflows/build/index.mdx
index d37b306c71a2e1e..317e4c6fd68d3d8 100644
--- a/src/content/docs/workflows/build/index.mdx
+++ b/src/content/docs/workflows/build/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/build/test-workflows.mdx b/src/content/docs/workflows/build/test-workflows.mdx
index 8752df04fd942ab..bf533e4a14be140 100644
--- a/src/content/docs/workflows/build/test-workflows.mdx
+++ b/src/content/docs/workflows/build/test-workflows.mdx
@@ -7,4 +7,4 @@ sidebar:
   order: 11
 products:
   - workflows
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workflows/examples/agents.mdx b/src/content/docs/workflows/examples/agents.mdx
index dabdf0389fd185b..4395885fbb20f1b 100644
--- a/src/content/docs/workflows/examples/agents.mdx
+++ b/src/content/docs/workflows/examples/agents.mdx
@@ -8,4 +8,4 @@ head: []
 description: Build AI-powered Agents on Cloudflare
 products:
   - workflows
----
+---
\ No newline at end of file
diff --git a/src/content/docs/workflows/examples/backup-d1.mdx b/src/content/docs/workflows/examples/backup-d1.mdx
index 1ef6fc225a7cfea..a22c45b46fda50d 100644
--- a/src/content/docs/workflows/examples/backup-d1.mdx
+++ b/src/content/docs/workflows/examples/backup-d1.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Export a D1 database into R2 storage with Workflows
 products: [d1, r2]
 tags:
diff --git a/src/content/docs/workflows/examples/send-invoices.mdx b/src/content/docs/workflows/examples/send-invoices.mdx
index 88c4d7c81871595..290cf8159582787 100644
--- a/src/content/docs/workflows/examples/send-invoices.mdx
+++ b/src/content/docs/workflows/examples/send-invoices.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Send invoice when shopping cart is checked out and paid for
 products: [d1, email-routing]
 tags:
diff --git a/src/content/docs/workflows/examples/twilio.mdx b/src/content/docs/workflows/examples/twilio.mdx
index 08df323ebf3258d..f9a9331974d6ad1 100644
--- a/src/content/docs/workflows/examples/twilio.mdx
+++ b/src/content/docs/workflows/examples/twilio.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Integrate Workflows with Twilio. Learn how to receive and send text messages and phone calls via APIs and Webhooks.
 products: [workers]
 pcx_content_type: example
diff --git a/src/content/docs/workflows/examples/wait-for-event.mdx b/src/content/docs/workflows/examples/wait-for-event.mdx
index 0e46962c459c1ab..95cc28394e9e6ec 100644
--- a/src/content/docs/workflows/examples/wait-for-event.mdx
+++ b/src/content/docs/workflows/examples/wait-for-event.mdx
@@ -1,4 +1,5 @@
 ---
+
 summary: Implement a Cloudflare Workflow that processes user-uploaded images, awaits human approval, and performs AI-based image tagging upon approval.
 tags:
   - Typescript
@@ -12,7 +13,7 @@ products:
   - workflows
 ---
 
-import { GitHubCode, WranglerConfig } from "~/components";
+import {  GitHubCode, WranglerConfig } from "~/components"
 
 This example demonstrates how to use the `waitForEvent()` API in Cloudflare Workflows to introduce a human-in-the-loop step. The Workflow is triggered by an image upload, during which metadata is stored in a D1 database. The Workflow then waits for user approval, and upon approval, it uses Workers AI to generate image tags, which are stored in the database. An accompanying Next.js frontend application facilitates the image upload and approval process.
 
@@ -44,12 +45,12 @@ The `index.ts` file defines the core logic of the Cloudflare Workflow responsibl
 For the complete implementation of the `index.ts` file, please refer to the [GitHub repository](https://github.com/cloudflare/docs-examples/blob/main/workflows/waitForEvent/workflow/src/index.ts).
 
 <GitHubCode
-	repo="cloudflare/docs-examples"
-	file="workflows/waitForEvent/workflow/src/index.ts"
-	commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
-	lang="ts"
+  repo="cloudflare/docs-examples"
+  file="workflows/waitForEvent/workflow/src/index.ts"
+  commit="43b2d19fc9f1098d5138871d06d0b47f0f9c6a43"
+  lang="ts"
 	lines="17-57"
-	useTypeScriptExample={true}
+  useTypeScriptExample={true}
 />
 
 ## Workflow wrangler.jsonc
diff --git a/src/content/docs/workflows/observability/index.mdx b/src/content/docs/workflows/observability/index.mdx
index 8a5a7d7938f5dfc..9fb63d677e9caec 100644
--- a/src/content/docs/workflows/observability/index.mdx
+++ b/src/content/docs/workflows/observability/index.mdx
@@ -5,11 +5,11 @@ pcx_content_type: navigation
 sidebar:
   order: 5
   group:
-    hideIndex: true
+   hideIndex: true
 products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/python/bindings.mdx b/src/content/docs/workflows/python/bindings.mdx
index a861b88223cc0f3..ea31fe2f488a996 100644
--- a/src/content/docs/workflows/python/bindings.mdx
+++ b/src/content/docs/workflows/python/bindings.mdx
@@ -153,7 +153,7 @@ class Default(WorkerEntrypoint):
 Send an event to a workflow instance.
 
 - <code>send_event(options)</code>* `type` - the type of event to send to the
-  workflow instance. \* `payload` - the payload to send to the workflow instance.
+  workflow instance. * `payload` - the payload to send to the workflow instance.
 
 ```python
 from pyodide.ffi import to_js
diff --git a/src/content/docs/workflows/reference/changelog.mdx b/src/content/docs/workflows/reference/changelog.mdx
index 00df519b89f7276..beba6e99cb7a9fe 100644
--- a/src/content/docs/workflows/reference/changelog.mdx
+++ b/src/content/docs/workflows/reference/changelog.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: changelog
-title: Release notes
+title: Release notes 
 description: Latest release notes and changes for Cloudflare Workflows.
 release_notes_file_name:
   - workflows
@@ -10,7 +10,7 @@ products:
   - workflows
 ---
 
-import { ProductReleaseNotes } from "~/components";
+import { ProductReleaseNotes } from "~/components"
 
 {/* <!-- Actual content lives in /data/changelogs/workflows.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
diff --git a/src/content/docs/workflows/reference/glossary.mdx b/src/content/docs/workflows/reference/glossary.mdx
index c6bc3d0908b0a9d..e19733552053c95 100644
--- a/src/content/docs/workflows/reference/glossary.mdx
+++ b/src/content/docs/workflows/reference/glossary.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Glossary } from "~/components";
+import { Glossary } from "~/components"
 
 Review the definitions for terms used across Cloudflare's Workflows documentation.
 
diff --git a/src/content/docs/workflows/reference/index.mdx b/src/content/docs/workflows/reference/index.mdx
index 6df95f6daddcdc4..89abc260ef45793 100644
--- a/src/content/docs/workflows/reference/index.mdx
+++ b/src/content/docs/workflows/reference/index.mdx
@@ -10,6 +10,6 @@ products:
   - workflows
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/workflows/reference/pricing.mdx b/src/content/docs/workflows/reference/pricing.mdx
index 283b87cdbd8653d..db0a2a5aa7c5f2e 100644
--- a/src/content/docs/workflows/reference/pricing.mdx
+++ b/src/content/docs/workflows/reference/pricing.mdx
@@ -8,7 +8,7 @@ products:
   - workflows
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 :::note
 
@@ -18,19 +18,19 @@ Workflows is included in both the Free and Paid [Workers plans](/workers/platfor
 
 Workflows pricing is identical to [Workers Standard pricing](/workers/platform/pricing/#workers) and are billed on three dimensions:
 
-- **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
-- **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
-- **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
+* **CPU time**: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
+* **Requests** (invocations): the number of Workflow invocations. [Subrequests](/workers/platform/limits/#subrequests) made from a Workflow do not incur additional request costs.
+* **Storage**: the total amount of storage (measured in GB) persisted by your Workflows.
 
 A Workflow that is waiting on a response to an API call, paused as a result of calling `step.sleep`, or otherwise idle, does not incur CPU time.
 
 ### Workflows Pricing
 
-| Unit                | Workers Free                                                                        | Workers Paid                                                                                   |
-| ------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers) | 10 million included per month + $0.30 per additional million                                   |
-| CPU time (ms)       | 10 milliseconds of CPU time per invocation                                          | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
-| Storage (GB-mo)     | 1GB                                                                                 | 1GB included per month + $0.20/ GB-month                                                       |
+| Unit | Workers Free | Workers Paid |
+|------|--------------|--------------|
+| Requests (millions) | 100,000 per day ([shared with Workers requests](/workers/platform/pricing/#workers)| 10 million included per month + $0.30 per additional million	|
+| CPU time (ms) | 10 milliseconds of CPU time per invocation | 30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds |
+| Storage (GB-mo) | 1GB | 1GB included per month + $0.20/ GB-month |
 
 :::note[CPU limits]
 
@@ -48,10 +48,10 @@ Storage billing for Workflows will go live on September 15th, 2025.
 
 Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to [Durable Objects SQL storage](/durable-objects/platform/pricing/#sqlite-storage-backend). A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).
 
-- Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
-- By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
-- When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
-- Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
+* Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
+* By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [30 days on the Paid plan](/workflows/reference/limits/).
+* When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the [`retention` option in `WorkflowInstanceCreateOptions`](/workflows/build/workers-api/#workflowinstancecreateoptions) for more information.
+* Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/workflows/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
 
 An instance that attempts to store state when your have reached the storage limit on the Free plan will cause an error to be thrown.
 
diff --git a/src/content/docs/workflows/reference/wrangler-commands.mdx b/src/content/docs/workflows/reference/wrangler-commands.mdx
index 2ad49f1ed36f4a1..b80050771f16411 100644
--- a/src/content/docs/workflows/reference/wrangler-commands.mdx
+++ b/src/content/docs/workflows/reference/wrangler-commands.mdx
@@ -8,6 +8,6 @@ products:
   - workflows
 ---
 
-import { WranglerNamespace } from "~/components";
+import {WranglerNamespace} from "~/components";
 
-<WranglerNamespace namespace="workflows" />
+<WranglerNamespace namespace="workflows"/>
diff --git a/src/content/docs/workflows/videos.mdx b/src/content/docs/workflows/videos.mdx
index 8d5a6926d7c97fa..0b45561d7cdf80d 100644
--- a/src/content/docs/workflows/videos.mdx
+++ b/src/content/docs/workflows/videos.mdx
@@ -11,9 +11,9 @@ products:
 import { CardGrid, LinkCard } from "~/components";
 
 <CardGrid>
-	<LinkCard
-		title="Build an application using Cloudflare Workflows"
-		description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
-		href="/learning-paths/workflows-course/series/workflows-1/"
-	/>
+    <LinkCard
+        title="Build an application using Cloudflare Workflows"
+        description="In this series, we introduce Cloudflare Workflows and the term 'Durable Execution' which comes from the desire to run applications that can resume execution from where they left off, even if the underlying host or compute fails."
+        href="/learning-paths/workflows-course/series/workflows-1/"
+    />
 </CardGrid>
diff --git a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
index e537c733bce84dd..07719d8b84e7244 100644
--- a/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
+++ b/src/content/docs/zaraz/advanced/datalayer-compatibility.mdx
@@ -6,6 +6,7 @@ products:
 title: Data layer compatibility mode
 sidebar:
   order: 3
+
 ---
 
 Cloudflare Zaraz offers backwards compatibility with the `dataLayer` function found in tag management software, used to track events and other parameters. This way you can keep your current implementation and Cloudflare Zaraz will automatically collect your events.
@@ -27,10 +28,10 @@ Events will only be sent to Zaraz if your pushed object includes an `event` key.
 
 ```js
 dataLayer.push({
-	event: "purchase",
-	price: "24",
-	currency: "USD",
-	transactionID: "12345678",
+  event: 'purchase',
+  price: '24',
+  currency: 'USD',
+  transactionID: '12345678',
 });
 ```
 
@@ -40,6 +41,6 @@ Because Zaraz converts the `dataLayer.push()` call to `zaraz.track()`, creating
 
 | Rule type    | Variable name | Match operation | Match string |
 | ------------ | ------------- | --------------- | ------------ |
-| _Match rule_ | _Event Name_  | _Equals_        | `purchase`   |
+| *Match rule* | *Event Name*  | *Equals*        | `purchase`   |
 
 We do not recommend using `dataLayer`. However, as many websites employ it, Cloudflare Zaraz has this automatic translation layer that converts it to `zaraz.track()`.
diff --git a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
index 359716b4e8520a1..571d8120641dd8c 100644
--- a/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
+++ b/src/content/docs/zaraz/advanced/domains-not-proxied.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: Use Zaraz on domains not proxied by Cloudflare
+
 ---
 
 You can load Zaraz on domains that are not proxied through Cloudflare. However, you will need to create a separate domain, or subdomain, proxied by Cloudflare (also [known as orange-clouded](https://community.cloudflare.com/t/step-3-enabling-the-orange-cloud/52715) domains), and load the script from it:
diff --git a/src/content/docs/zaraz/advanced/google-consent-mode.mdx b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
index 730a6cf363a3bba..32b7951c7c0b104 100644
--- a/src/content/docs/zaraz/advanced/google-consent-mode.mdx
+++ b/src/content/docs/zaraz/advanced/google-consent-mode.mdx
@@ -6,6 +6,7 @@ products:
 title: Google Consent Mode
 sidebar:
   order: 4
+
 ---
 
 ## Background
@@ -14,7 +15,7 @@ sidebar:
 
 You can also use Google Analytics and Google Ads without cookies by selecting **Permissions** and disabling **Access client key-value store**.
 
----
+***
 
 ## Consent Mode v2
 
@@ -27,12 +28,12 @@ Often websites will want to set a default consent status that denies all categor
 If that is not what your website needs, and instead you want to set the default consent status in a more granular way, use the reserved `google_consent_default` property:
 
 ```js
-zaraz.set("google_consent_default", {
-	ad_storage: "denied",
-	ad_user_data: "denied",
-	ad_personalization: "denied",
-	analytics_storage: "denied",
-});
+zaraz.set("google_consent_default",  {
+  'ad_storage': 'denied',
+  'ad_user_data': 'denied',
+  'ad_personalization': 'denied',
+  'analytics_storage': 'denied'
+})
 ```
 
 After the above code is executed, the consent status will be saved to `localStorage` and will be included with every subsequent Zaraz event.
@@ -44,12 +45,12 @@ Note that the code should be included as part of your website HTML code, usually
 After the user has provided their consent preferences you can set the new status using the reserved `google_consent_update` property. If you are using the Zaraz Consent Management Platform, you can use the [Consent Choices Updated event](/zaraz/consent-management/api/#consent-choices-updated) to know when to update the Google Consent status.
 
 ```js
-zaraz.set("google_consent_update", {
-	ad_storage: "granted",
-	ad_user_data: "denied",
-	ad_personalization: "granted",
-	analytics_storage: "denied",
-});
+zaraz.set("google_consent_update",  {
+  'ad_storage': 'granted',
+  'ad_user_data': 'denied',
+  'ad_personalization': 'granted',
+  'analytics_storage': 'denied'
+})
 ```
 
 All subsequent events will include the information about both the default and the updated consent status.
diff --git a/src/content/docs/zaraz/advanced/import-export.mdx b/src/content/docs/zaraz/advanced/import-export.mdx
index 578d82719d2e9dc..450eddcbc977e9a 100644
--- a/src/content/docs/zaraz/advanced/import-export.mdx
+++ b/src/content/docs/zaraz/advanced/import-export.mdx
@@ -6,6 +6,7 @@ products:
 title: Configuration Import & Export
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To export your Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Advanced**.
 3. Click "Export" to download your configuration.
 
@@ -27,15 +27,16 @@ To export your Zaraz configuration:
 
 :::caution
 
+
 Importing a Zaraz configuration replaces your existing configuration, meaning that any information you did not back up could be lost. Consider exporting your existing configuration before importing a new one.
 
+
 :::
 
 To import a Zaraz configuration:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Advanced**.
 3. Click **Browse** to select your configuration file, and **Import** to import it.
diff --git a/src/content/docs/zaraz/advanced/index.mdx b/src/content/docs/zaraz/advanced/index.mdx
index 1b0c3fd82039d96..9b8a538527e1ac3 100644
--- a/src/content/docs/zaraz/advanced/index.mdx
+++ b/src/content/docs/zaraz/advanced/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Advanced options
 sidebar:
   order: 7
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
index 568da28f0043abf..7e825c97731546d 100644
--- a/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
+++ b/src/content/docs/zaraz/advanced/load-custom-managed-component.mdx
@@ -60,8 +60,7 @@ As with regular tools, it is recommended that you [create the triggers](/zaraz/c
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > [**Third-party tools**](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/tools-config/tools/catalog).
 3. Select **Add new tool** and choose **Custom Managed Component** from the tools library page. Select **Continue** to confirm your selection.
 4. In **Select Custom MC**, choose a Custom Managed Component that you have deployed to your account, such as `custom-mc-my-new-counter-mc`. Select **Continue**.
diff --git a/src/content/docs/zaraz/advanced/load-selectively.mdx b/src/content/docs/zaraz/advanced/load-selectively.mdx
index 1d02673007eda4d..f9384c91755a2cc 100644
--- a/src/content/docs/zaraz/advanced/load-selectively.mdx
+++ b/src/content/docs/zaraz/advanced/load-selectively.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Zaraz selectively
 sidebar:
   order: 1
+
 ---
 
 You can use [Configuration Rules](/rules/configuration-rules/) to load Zaraz selectively on specific URLs or subdomains. Configuration Rules can also be used to block Zaraz from loading based on cookies, IP addresses or anything else related to a request.
@@ -14,6 +15,8 @@ Refer to [Configuration Rules](/rules/configuration-rules/) documentation to lea
 
 :::note
 
+
 If you need to block one or more actions from firing in a tool, Cloudflare recommends you use [Blocking Triggers](/zaraz/advanced/blocking-triggers/) instead of Configuration Rules.
 
+
 :::
diff --git a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
index ce72a802d046457..d8ca835447f24d1 100644
--- a/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
+++ b/src/content/docs/zaraz/advanced/load-zaraz-manually.mdx
@@ -6,6 +6,7 @@ products:
 title: Load Zaraz manually
 sidebar:
   order: 5
+
 ---
 
 By default, if your domain is proxied by Cloudflare, Zaraz will automatically inject itself to HTML pages in your site. This makes it easier to get up and running quickly. However, you might want to load Zaraz manually, for example to test Zaraz on specific pages first.
@@ -20,13 +21,13 @@ With the script, your page HTML should be similar to the following:
 
 ```html
 <html>
-	<head>
-		….
-		<script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
-	</head>
-	<body>
-		…
-	</body>
+  <head>
+    ….
+    <script src="/cdn-cgi/zaraz/i.js" referrerpolicy="origin"></script>
+  </head>
+  <body>
+    …
+  </body>
 </html>
 ```
 
diff --git a/src/content/docs/zaraz/advanced/using-jsonata.mdx b/src/content/docs/zaraz/advanced/using-jsonata.mdx
index 82292524bfe52e4..925c0718866321c 100644
--- a/src/content/docs/zaraz/advanced/using-jsonata.mdx
+++ b/src/content/docs/zaraz/advanced/using-jsonata.mdx
@@ -6,6 +6,7 @@ products:
 title: Using JSONata
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To use JSONata inside Zaraz, follow these steps:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Go to **Tools configuration** > **Tools**.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -38,22 +38,23 @@ Converting a string to lowercase is useful if you want to compare it to somethin
 Assuming you are using `zaraz.ecommerce()` to send the cart content like this:
 
 ```js
-zaraz.track("Product List Viewed", {
-	products: [
-		{
-			sku: "2671033",
-			name: "V-neck T-shirt",
-			price: 14.99,
-			quantity: 3,
-		},
-		{
-			sku: "2671034",
-			name: "T-shirt",
-			price: 10.99,
-			quantity: 2,
-		},
-	],
-});
+zaraz.track('Product List Viewed',
+  {  products:
+    [
+    {
+      sku: '2671033',
+      name: 'V-neck T-shirt',
+      price: 14.99,
+      quantity: 3
+    },{
+      sku: '2671034',
+      name: 'T-shirt',
+      price: 10.99,
+      quantity: 2
+    },
+    ],
+  }
+);
 ```
 
 If the field in which you want to show the sum, you will enter `{{ $sum(client.products.(price * quantity)) }}`. This will multiply the price of each product by its quantity, and then sum up the total.
diff --git a/src/content/docs/zaraz/consent-management/api.mdx b/src/content/docs/zaraz/consent-management/api.mdx
index cfbaa929889d835..b6feadf8eef42a1 100644
--- a/src/content/docs/zaraz/consent-management/api.mdx
+++ b/src/content/docs/zaraz/consent-management/api.mdx
@@ -6,6 +6,7 @@ products:
 title: Consent API
 sidebar:
   order: 3
+
 ---
 
 ## Background
@@ -14,7 +15,7 @@ The Consent API allows you to programmatically control all aspects of the Consen
 
 Using the Consent API, you can integrate Zaraz Consent preferences with an external Consent Management Platform, customize your consent modal, or restrict consent management to users in specific regions.
 
----
+***
 
 ## Events
 
@@ -24,8 +25,9 @@ It can be useful to know when the Consent API is fully loaded on the page so tha
 
 ```js
 document.addEventListener("zarazConsentAPIReady", () => {
-	// do things with the Consent API
+  // do things with the Consent API
 });
+
 ```
 
 ### `Consent Choices Updated`
@@ -34,26 +36,34 @@ This event is fired every time the user makes changes to their consent preferenc
 
 ```js
 document.addEventListener("zarazConsentChoicesUpdated", () => {
-	// read the new consent preferences using `zaraz.consent.getAll();` and do things with it
+  // read the new consent preferences using `zaraz.consent.getAll();` and do things with it
 });
+
 ```
 
----
+***
 
 ## Properties
 
 The following are properties of the `zaraz.consent` object.
 
-- `modal` boolean
-  - Get or set the current visibility status of the consent modal dialog.
 
-- `purposes` object read-only
-  - An object containing all configured purposes, with their ID, name, description, and order.
 
-- `APIReady` boolean read-only
-  - Indicates whether the Consent API is currently available on the page.
+* `modal` boolean
 
----
+  * Get or set the current visibility status of the consent modal dialog.
+
+* `purposes` object read-only
+
+  * An object containing all configured purposes, with their ID, name, description, and order.
+
+* `APIReady` boolean read-only
+
+  * Indicates whether the Consent API is currently available on the page.
+
+
+
+***
 
 ## Methods
 
@@ -63,18 +73,27 @@ The following are properties of the `zaraz.consent` object.
 zaraz.consent.get(purposeId);
 ```
 
-- <code>get(purposeId)</code> : `boolean | undefined`
+
+
+* <code>get(purposeId)</code> : `boolean | undefined`
+
+
 
 Get the current consent status for a purpose using the purpose ID.
 
-- `true`: The consent was granted.
-- `false`: The consent was not granted.
-- `undefined`: The purpose does not exist.
+* `true`: The consent was granted.
+* `false`: The consent was not granted.
+* `undefined`: The purpose does not exist.
 
 #### Parameters
 
-- `purposeId` string
-  - The ID representing the Purpose.
+
+
+* `purposeId` string
+
+  * The ID representing the Purpose.
+
+
 
 ### `Set`
 
@@ -82,14 +101,23 @@ Get the current consent status for a purpose using the purpose ID.
 zaraz.consent.set(consentPreferences);
 ```
 
-- <code>set(consentPreferences)</code> : `undefined`
+
+
+* <code>set(consentPreferences)</code> : `undefined`
+
+
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-- `consentPreferences` object
-  - a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
+
+
+* `consentPreferences` object
+
+  * a `{ purposeId: boolean }` object describing the purposes you want to set and their respective consent status.
+
+
 
 ### `Get All`
 
@@ -97,7 +125,11 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.getAll();
 ```
 
-- <code>getAll()</code> : `{ purposeId: boolean }`
+
+
+* <code>getAll()</code> : `{ purposeId: boolean }`
+
+
 
 Returns an object with the consent status of all purposes.
 
@@ -107,14 +139,23 @@ Returns an object with the consent status of all purposes.
 zaraz.consent.setAll(consentStatus);
 ```
 
-- <code>setAll(consentStatus)</code> : `undefined`
+
+
+* <code>setAll(consentStatus)</code> : `undefined`
+
+
 
 Set the consent status for all purposes at once.
 
 #### Parameters
 
-- `consentStatus` boolean
-  - Indicates whether the consent was granted or not.
+
+
+* `consentStatus` boolean
+
+  * Indicates whether the consent was granted or not.
+
+
 
 ### `Get All Checkboxes`
 
@@ -122,7 +163,11 @@ Set the consent status for all purposes at once.
 zaraz.consent.getAllCheckboxes();
 ```
 
-- <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
+
+
+* <code>getAllCheckboxes()</code> : `{ purposeId: boolean }`
+
+
 
 Returns an object with the checkbox status of all purposes.
 
@@ -132,14 +177,23 @@ Returns an object with the checkbox status of all purposes.
 zaraz.consent.setCheckboxes(checkboxesStatus);
 ```
 
-- <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
+
+
+* <code>setCheckboxes(checkboxesStatus)</code> : `undefined`
+
+
 
 Set the consent status for some purposes using the purpose ID.
 
 #### Parameters
 
-- `checkboxesStatus` object
-  - a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
+
+
+* `checkboxesStatus` object
+
+  * a `{ purposeId: boolean }` object describing the checkboxes you want to set and their respective checked status.
+
+
 
 ### `Set All Checkboxes`
 
@@ -147,14 +201,23 @@ Set the consent status for some purposes using the purpose ID.
 zaraz.consent.setAllCheckboxes(checkboxStatus);
 ```
 
-- <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
+
+
+* <code>setAllCheckboxes(checkboxStatus)</code> : `undefined`
+
+
 
 Set the `checkboxStatus` status for all purposes in the consent modal at once.
 
 #### Parameters
 
-- `checkboxStatus` boolean
-  - Indicates whether the purposes should be marked as checked or not.
+
+
+* `checkboxStatus` boolean
+
+  * Indicates whether the purposes should be marked as checked or not.
+
+
 
 ### `Send queued events`
 
@@ -162,7 +225,11 @@ Set the `checkboxStatus` status for all purposes in the consent modal at once.
 zaraz.consent.sendQueuedEvents();
 ```
 
-- <code>sendQueuedEvents()</code> : `undefined`
+
+
+* <code>sendQueuedEvents()</code> : `undefined`
+
+
 
 If some Pageview-based events were not sent due to a lack of consent, they can be sent using this method after consent was granted.
 
@@ -174,35 +241,32 @@ You can combine multiple features of Zaraz to effectively disable Consent Manage
 
 ```html
 <script>
-	function getCookie(name) {
-		const value = `; ${document.cookie}`;
-		return value?.split(`; ${name}=`)[1]?.split(";")[0];
-	}
-
-	function handleZarazConsentAPIReady() {
-		const consent_cookie = getCookie("cf_consent");
-		const isEUCountry = "{{system.device.location.isEUCountry}}" === "1";
-		if (!consent_cookie) {
-			if (isEUCountry) {
-				zaraz.consent.modal = true;
-			} else {
-				zaraz.consent.setAll(true);
-				zaraz.consent.sendQueuedEvents();
-			}
-		}
-	}
-
-	if (zaraz.consent?.APIReady) {
-		handleZarazConsentAPIReady();
-	} else {
-		document.addEventListener(
-			"zarazConsentAPIReady",
-			handleZarazConsentAPIReady,
-		);
-	}
+function getCookie(name) {
+  const value = `; ${document.cookie}`
+  return value?.split(`; ${name}=`)[1]?.split(";")[0]
+}
+
+function handleZarazConsentAPIReady() {
+  const consent_cookie = getCookie("cf_consent")
+  const isEUCountry = "{{system.device.location.isEUCountry}}" === "1"
+  if (!consent_cookie) {
+    if (isEUCountry) {
+      zaraz.consent.modal = true
+    } else {
+      zaraz.consent.setAll(true)
+      zaraz.consent.sendQueuedEvents()
+    }
+  }
+}
+
+if (zaraz.consent?.APIReady) {
+  handleZarazConsentAPIReady()
+} else {
+  document.addEventListener("zarazConsentAPIReady", handleZarazConsentAPIReady)
+}
 </script>
 ```
 
-Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf_consent" in the snippet above.
+Note: If you've customized the cookie name for the Consent Manager, use that customized name instead of "cf\_consent"  in the snippet above.
 
 By letting this Custom HTML tool to run without consent requirements, the modal will appear to all EU visitors, while for other visitors consent will be automatically granted. The `{{ system.device.location.isEUCountry }}` property will be `1` if the visitor is from an EU country and `0` otherwise. You can use any other property or variable to customize the Consent Management behavior in a similar manner, such as `{{ system.device.location.country }}` to restrict consent checks based on country code.
diff --git a/src/content/docs/zaraz/consent-management/custom-css.mdx b/src/content/docs/zaraz/consent-management/custom-css.mdx
index 7827dbae8fb4745..719f2839cf27872 100644
--- a/src/content/docs/zaraz/consent-management/custom-css.mdx
+++ b/src/content/docs/zaraz/consent-management/custom-css.mdx
@@ -6,6 +6,7 @@ products:
 title: Custom CSS
 sidebar:
   order: 2
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,5 @@ You can add custom CSS to the Zaraz Consent Management Platform, to make the con
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Find the **Custom CSS** section, and add your custom CSS code as you would on any other HTML editor.
diff --git a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
index 1a442cb85828653..39e50481db06ef5 100644
--- a/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
+++ b/src/content/docs/zaraz/consent-management/enable-consent-management.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Enable the Consent Management platform (CMP)
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Turn on **Enable Consent Management**.
 3. In **Consent modal text** fill in any legal information required in your country. Use HTML code to format your information as you would in any other HTML editor.
 4. Under **Purposes**, select **Add new Purpose**. Give your new purpose a name and a description. Purposes are the reasons for using third-party tools in your website.
@@ -31,8 +31,7 @@ In your Zaraz consent settings, you can add your consent modal text and purposes
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Select a default language of your choice. The default setting is English.
 3. In **Consent modal text** and **Purposes**, you can select different languages and add translations.
 
@@ -45,7 +44,7 @@ Below is an example that forces the language shown to be American English.
 
 ```html
 <script>
-	zaraz.set("__zarazConsentLanguage", "en-US");
+  zaraz.set('__zarazConsentLanguage', 'en-US')
 </script>
 ```
 
diff --git a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
index 57e58eba4bb79c1..0ab62c99c732fa1 100644
--- a/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
+++ b/src/content/docs/zaraz/consent-management/iab-tcf-compliance.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: IAB Transparency & Consent Framework Compliance
+
 ---
 
 import { DashButton } from "~/components";
@@ -21,8 +22,7 @@ Using the Zaraz Consent Management Platform in IAB TCF Compliance Mode is is opt
 
 1. In the Cloudflare dashboard, go to the **Consent** page.
 
-   <DashButton url="/?to=/:account/tag-management/consent" />
-
+	<DashButton url="/?to=/:account/tag-management/consent" />
 2. Check the **Use IAB TCF compliant modal** option.
 3. Under the **Assign purposes to tools** section, add vendor details to every tool that was not automatically assigned.
 4. Press **Save**.
diff --git a/src/content/docs/zaraz/consent-management/index.mdx b/src/content/docs/zaraz/consent-management/index.mdx
index 577214eacbb7f26..57e7e5e3a28277f 100644
--- a/src/content/docs/zaraz/consent-management/index.mdx
+++ b/src/content/docs/zaraz/consent-management/index.mdx
@@ -11,9 +11,10 @@ sidebar:
 head:
   - tag: title
     content: Zaraz Consent Management platform
+
 ---
 
-Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
+Zaraz provides a Consent Management platform (CMP) to help you address and manage required consents under the European [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) and the [Directive on privacy and electronic communications](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219\&from=EN#tocId7). This consent platform lets you easily create a consent modal for your website based on the tools you have configured. With Zaraz CMP, you can make sure Zaraz only loads tools under the umbrella of the specific purposes your users have agreed to.
 
 The consent modal added to your website is concise and gives your users an easy way to opt-in to any purposes of data processing your tools need.
 
@@ -21,12 +22,12 @@ The consent modal added to your website is concise and gives your users an easy
 
 The Zaraz Consent Management platform (CMP) has a **Purposes** section. This is where you will have to create purposes for the third-party tools your website uses. To better understand the terms involved in dealing with personal data, refer to these definitions:
 
-- **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
-- **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
+* **Purpose**: The reason you are loading a given tool on your website, such as to track conversions or improve your website’s layout based on behavior tracking. One purpose can be assigned to many tools, but one tool can be assigned only to one purpose.
+* **Consent**: An affirmative action that the user makes, required to store and access cookies (or other persistent data, like `LocalStorage`) on the users’ computer/browser.
 
 :::note
 
-All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in.
+All tools use consent as a legal basis. This is due to the fact that they all use cookies that are not strictly necessary for the website’s correct operation. Due to this, all purposes are opt-in. 
 :::
 
 ## Purposes and tools
@@ -35,19 +36,19 @@ When you add a new tool to your website, Zaraz does not assign any purpose to it
 
 The user’s consent preferences are stored within a first-party cookie. This cookie is a JSON file that maps the purposes’ ID to a `true`/`false`/missing value:
 
-- `true` value: The user gave consent.
-- `false`value: The user refused consent.
-- Missing value: The user has not made a choice yet.
+* `true` value: The user gave consent.
+* `false`value: The user refused consent.
+* Missing value: The user has not made a choice yet.
 
 :::caution[Important]
 
-Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR.
+Cloudflare cannot recommend nor assign by default any specific purpose for your tools. It is your responsibility to properly assign tools to purposes if you need to comply with GDPR. 
 :::
 
 ## Important things to note
 
-- Purposes that have no tools assigned will not show up in the CMP modal.
-- If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
-- Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
-- If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
-- On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
+* Purposes that have no tools assigned will not show up in the CMP modal.
+* If a tool is assigned to a purpose, it will not run unless the user gives consent for the purpose the tool is assigned for.
+* Once your website loads for a given user for the first time, all the triggers you have configured for tools that are waiting for consent are cached in the browser. Then, they will be fired when/if the user gives consent, so they are not lost.
+* If the user visits your website for the first time, the consent modal will automatically show up. This also happens if the user has previously visited your website, but in the meantime you have enabled CMP.
+* On subsequent visits, the modal will not show up. You can make the modal show up by calling the function `zaraz.showConsentModal()` — for example, by binding it to a button.
diff --git a/src/content/docs/zaraz/custom-actions/additional-fields.mdx b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
index f0bf936140a3a71..76436e214d13c6c 100644
--- a/src/content/docs/zaraz/custom-actions/additional-fields.mdx
+++ b/src/content/docs/zaraz/custom-actions/additional-fields.mdx
@@ -6,6 +6,7 @@ products:
 title: Additional fields
 sidebar:
   order: 5
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ Adding an additional field to an action will attach it to this action only, and
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool with the action you want to add the additional field to, and select **Edit**.
 4. Select the action you wish to modify.
@@ -36,8 +36,7 @@ Adding an additional field to the tool sets it as a default field for all of the
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select **Tools Configuration** > **Third-party tools**.
 3. Locate the third-party tool where you want to add the field, and select **Edit**.
 4. Select **Settings** > **Add Field**.
diff --git a/src/content/docs/zaraz/custom-actions/create-action.mdx b/src/content/docs/zaraz/custom-actions/create-action.mdx
index fbb05627895c834..7d01b943b05425e 100644
--- a/src/content/docs/zaraz/custom-actions/create-action.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-action.mdx
@@ -16,8 +16,7 @@ To create an action, first [add a third-party tool](/zaraz/get-started/). If you
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate the tool you want to configure an action for, and select **Edit**.
 4. Under Custom actions select **Create action**.
diff --git a/src/content/docs/zaraz/custom-actions/create-trigger.mdx b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
index 200485ee7f7263e..7d7d8c141b3ade7 100644
--- a/src/content/docs/zaraz/custom-actions/create-trigger.mdx
+++ b/src/content/docs/zaraz/custom-actions/create-trigger.mdx
@@ -14,8 +14,7 @@ Triggers define the conditions under which a tool will start an action. Since a
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Select the **Triggers** tab.
 4. Select **Create trigger**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
index 8e83ceeaf6c5a71..38a7dae5ee8f9a5 100644
--- a/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-tools-and-actions.mdx
@@ -6,14 +6,14 @@ products:
 title: Edit tools and actions
 sidebar:
   order: 6
----
 
+---
 import { DashButton } from "~/components";
 
-1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
+1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools**.
 3. Under **Third-party tools**, locate your tool and select **Edit**.
 
@@ -23,8 +23,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select the **Enabled** toggle.
 
@@ -32,8 +31,7 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate the tool you wan to edit and select **Edit**.
 4. Find the action you want to change state, and enable or disable it with the toggle.
@@ -42,7 +40,6 @@ On this page you will be able to edit settings related to the tool, add actions,
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Third-party tools**, locate your tool and select **Delete**.
diff --git a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
index 23abf7eee383799..2e9e13f08691d48 100644
--- a/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
+++ b/src/content/docs/zaraz/custom-actions/edit-triggers.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a trigger
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Edit**.
 
@@ -26,7 +26,6 @@ You can edit every field related to the trigger, as well as add new trigger rule
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Under **Triggers**, locate your trigger and select **Delete**.
diff --git a/src/content/docs/zaraz/embeds.mdx b/src/content/docs/zaraz/embeds.mdx
index 72ce24521d03833..d2a6e58612bd5d4 100644
--- a/src/content/docs/zaraz/embeds.mdx
+++ b/src/content/docs/zaraz/embeds.mdx
@@ -6,6 +6,7 @@ products:
 title: Embeds
 sidebar:
   order: 6
+
 ---
 
 import { DashButton } from "~/components";
@@ -18,8 +19,7 @@ To add an Embed to Your Website:
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration**.
 3. Click "add new tool" and activate the desired tools on your Cloudflare Zaraz dashboard.
 4. Add a placeholder in your HTML, specifying the necessary attributes. For a generic embed, the snippet looks like this:
@@ -43,10 +43,7 @@ Replace `tweet-id` with the actual tweet ID for the content you wish to embed.
 ### Instagram embed
 
 ```html
-<instagram-post
-	post-url="https://www.instagram.com/p/ABC/"
-	captions="true"
-></instagram-post>
+<instagram-post post-url="https://www.instagram.com/p/ABC/" captions="true"></instagram-post>
 ```
 
 Replace `post-url` with the actual URL for the content you wish to embed. To include posts captions set captions attribute to `true`.
diff --git a/src/content/docs/zaraz/get-started.mdx b/src/content/docs/zaraz/get-started.mdx
index 69973cb72ac66dc..682f7f02cc686a6 100644
--- a/src/content/docs/zaraz/get-started.mdx
+++ b/src/content/docs/zaraz/get-started.mdx
@@ -18,8 +18,7 @@ You can add new third-party tools and load them into your website through the Cl
 
 1. In the Cloudflare dashboard, go to the **Tag Setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. If you have already added a tool before, select **Third-party tools** and click on **Add new tool**.
 3. Choose a tool from the tools catalog. Select **Continue** to confirm your selection.
 4. In **Set up**, configure the settings for your new tool. The information you need to enter will depend on the tool you choose. If you want to use any dynamic properties or variables, select the `+` sign in the drop-down menu next to the relevant field.
diff --git a/src/content/docs/zaraz/history/index.mdx b/src/content/docs/zaraz/history/index.mdx
index 98f0e09c733046c..a86038b87af35fc 100644
--- a/src/content/docs/zaraz/history/index.mdx
+++ b/src/content/docs/zaraz/history/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Versions & History
 sidebar:
   order: 8
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Zaraz can work in real-time. In this mode, every change you make is instantly published. You can also enable [Preview & Publish mode](/zaraz/history/preview-mode/), which allows you to test your changes before you commit to them.
 
diff --git a/src/content/docs/zaraz/history/versions.mdx b/src/content/docs/zaraz/history/versions.mdx
index d5c71f8201e3f9d..0ee58afc9464854 100644
--- a/src/content/docs/zaraz/history/versions.mdx
+++ b/src/content/docs/zaraz/history/versions.mdx
@@ -6,10 +6,12 @@ products:
 title: Versions
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
 
+
 Version History enables you to keep track of all the Zaraz configuration changes made in your website. With Version History you can also revert changes to previous settings should there be a problem.
 
 To access Version History you need to enable [Preview & Publish mode](/zaraz/history/preview-mode/) first. Then, you can access Version History under **Zaraz** > **History**.
@@ -18,12 +20,11 @@ To access Version History you need to enable [Preview & Publish mode](/zaraz/his
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-   <DashButton url="/?to=/:account/tag-management/history" />
-
-2. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
-   - Date of change
-   - User who made the change
-   - Description of the change
+	<DashButton url="/?to=/:account/tag-management/history" />
+3. If this is your first time using this feature, this page will be empty. Otherwise, you will have a list of changes made to your account with the following information:
+   * Date of change
+   * User who made the change
+   * Description of the change
 
 ## Revert changes
 
@@ -31,8 +32,7 @@ Version History enables you to revert any changes made to your Zaraz settings.
 
 1. In the Cloudflare dashboard, go to the **History** page.
 
-   <DashButton url="/?to=/:account/tag-management/history" />
-
+	<DashButton url="/?to=/:account/tag-management/history" />
 2. Find the changes you want to revert, and select **Restore**.
 3. Confirm you want to revert your changes.
 4. Select **Publish** to publish your changes.
diff --git a/src/content/docs/zaraz/http-events-api.mdx b/src/content/docs/zaraz/http-events-api.mdx
index a4e94957e49f0cd..657a00899b82342 100644
--- a/src/content/docs/zaraz/http-events-api.mdx
+++ b/src/content/docs/zaraz/http-events-api.mdx
@@ -9,6 +9,7 @@ sidebar:
 head:
   - tag: title
     content: HTTP Events API
+
 ---
 
 import { DashButton } from "~/components";
@@ -23,8 +24,7 @@ To enable the API endpoint:
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Under **Endpoints** > **HTTP Events API**, set your desired path. Remember the path is relative to your domain, and it must start with a `/`.
 
 :::caution[Important]
@@ -37,25 +37,25 @@ The endpoint you have configured for the API will receive `POST` requests with a
 
 ```json
 {
-	"events": [
-		{
-			"client": {
-				"__zarazTrack": "transaction successful",
-				"value": "200"
-			}
-		}
-	]
+  "events": [
+    {
+      "client": {
+        "__zarazTrack": "transaction successful",
+        "value": "200"
+      }
+    }
+  ]
 }
 ```
 
 The payload must contain an `events` array. Each Event Object in this array corresponds to one event you want Zaraz to process. The above example is similar to calling `zaraz.track('transaction successful', { value: "200" })` using the Web API.
 
-The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a _Track Property_ in the Zaraz dashboard.
+The Event Object holds the `client` object, in which you can pass information about the event itself. Every key you include in the Event Object will be available as a *Track Property* in the Zaraz dashboard.
 
 There are two reserved keys:
 
-- `__zarazTrack`: The value of this key will be available as _Event Name_. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
-- `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
+* `__zarazTrack`: The value of this key will be available as *Event Name*. This is what you will usually build your triggers around. In the above example, setting this to `transaction successful` is the same as [using the Web API](/zaraz/web-api/track/) and calling `zaraz.track("transaction successful")`.
+* `__zarazEcommerce`: This key needs to be set to `true` if you want Zaraz to process the event as an e-commerce event.
 
 ### The `system` key
 
@@ -65,41 +65,41 @@ The same payload from before will resemble the following example, when we add th
 
 ```json
 {
-	"events": [
-		{
-			"client": {
-				"__zarazTrack": "transaction successful",
-				"value": "200"
-			},
-			"system": {
-				"page": {
-					"url": "https://example.com",
-					"title": "My website"
-				},
-				"device": {
-					"language": "en-US",
-					"ip": "192.168.0.1"
-				}
-			}
-		}
-	]
+  "events": [
+    {
+      "client": {
+        "__zarazTrack": "transaction successful",
+        "value": "200"
+      },
+      "system": {
+        "page": {
+          "url": "https://example.com",
+          "title": "My website"
+        },
+        "device": {
+          "language": "en-US",
+          "ip": "192.168.0.1"
+        }
+      }
+    }
+  ]
 }
 ```
 
 For all available system keys, refer to the table below:
 
-| Property                   | Type   | Description                                                                                |
-| -------------------------- | ------ | ------------------------------------------------------------------------------------------ |
-| `system.cookies`           | Object | A key-value object holding cookies from the device associated with the event.              |
-| `system.device.ip`         | String | The IP address of the device associated with the event.                                    |
-| `system.device.resolution` | String | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
-| `system.device.viewport`   | String | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
-| `system.device.language`   | String | The language code used by the device associated with the event.                            |
-| `system.device.user-agent` | String | The `User-Agent` string of the device associated with the event.                           |
-| `system.page.title`        | String | The title of the page associated with the event.                                           |
-| `system.page.url`          | String | The URL of the page associated with the event.                                             |
-| `system.page.referrer`     | String | The URL of the referrer page in the time the event took place.                             |
-| `system.page.encoding`     | String | The encoding of the page associated with the event.                                        |
+| Property                   | Type  | Description                                                                                |
+| -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------ |
+| `system.cookies`           | Object                         | A key-value object holding cookies from the device associated with the event.              |
+| `system.device.ip`         | String                         | The IP address of the device associated with the event.                                    |
+| `system.device.resolution` | String                         | The screen resolution of the device associated with the event, in a `WIDTHxHEIGHT` format. |
+| `system.device.viewport`   | String                         | The viewport of the device associated with the event, in a `WIDTHxHEIGHT` format.          |
+| `system.device.language`   | String                         | The language code used by the device associated with the event.                            |
+| `system.device.user-agent` | String                         | The `User-Agent` string of the device associated with the event.                           |
+| `system.page.title`        | String                         | The title of the page associated with the event.                                           |
+| `system.page.url`          | String                         | The URL of the page associated with the event.                                             |
+| `system.page.referrer`     | String                         | The URL of the referrer page in the time the event took place.                             |
+| `system.page.encoding`     | String                         | The encoding of the page associated with the event.                                        |
 
 :::note
 
@@ -112,11 +112,11 @@ For each Event Object in your payload, Zaraz will respond with a Result Object.
 
 Depending on what tools you are loading using Zaraz, the body of the response coming from the API might include information you will want to process. This is because some tools do not have a complete server-side implementation and still depend on cookies, client-side JavaScript or similar mechanisms. Each Result Object can include the following information:
 
-| Result key | Description                                                     |
-| ---------- | --------------------------------------------------------------- |
-| `fetch`    | Fetch requests that tools want to send from the user browser.   |
-| `execute`  | JavaScript code that tools want to execute in the user browser. |
-| `return`   | Information that tools return.                                  |
-| `cookies`  | Cookies that tools want to set for the user.                    |
+| Result key | Description |
+| --- | --- |
+| `fetch` | Fetch requests that tools want to send from the user browser. |
+| `execute` | JavaScript code that tools want to execute in the user browser. |
+| `return` | Information that tools return. |
+| `cookies` | Cookies that tools want to set for the user. |
 
 You do not have to process the information above, but some tools might depend on this to work properly. You can start using the HTTP Events API without processing the information in the table above, and adjust accordingly later.
diff --git a/src/content/docs/zaraz/monitoring/index.mdx b/src/content/docs/zaraz/monitoring/index.mdx
index 89a3c69828ab590..7d60ca7c1291ea9 100644
--- a/src/content/docs/zaraz/monitoring/index.mdx
+++ b/src/content/docs/zaraz/monitoring/index.mdx
@@ -18,9 +18,8 @@ To use Zaraz Monitoring:
 
 1. In the Cloudflare dashboard, go to the **Monitoring** page.
 
-   <DashButton url="/?to=/:account/tag-management/monitoring" />
-
-2. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
+	<DashButton url="/?to=/:account/tag-management/monitoring" />
+3. Select one of the options (Loads, Events, Triggers, Actions). Zaraz Monitoring will show you how the traffic for that section evolved for the time period selected.
 
 ## Zaraz Monitoring options
 
diff --git a/src/content/docs/zaraz/pricing-info.mdx b/src/content/docs/zaraz/pricing-info.mdx
index 1ca41a948098035..dca9b6076413d78 100644
--- a/src/content/docs/zaraz/pricing-info.mdx
+++ b/src/content/docs/zaraz/pricing-info.mdx
@@ -6,6 +6,7 @@ products:
 title: Pricing
 sidebar:
   order: 15
+
 ---
 
 import { DashButton } from "~/components";
@@ -17,15 +18,13 @@ All Zaraz features and tools are always available on all accounts. Learn more ab
 ## The Zaraz Event unit
 
 One Zaraz Event is an event you are sending to Zaraz, whether that is a page view, a `zaraz.track` event, or similar. You can easily see the total number of Zaraz Events you are currently using on the **Monitoring** page of the Cloudflare dashboard:
-
-<DashButton url="/?to=/:account/tag-management/monitoring" />
+   <DashButton url="/?to=/:account/tag-management/monitoring" />
 
 ## Enabling Zaraz Paid
 
 1. In the Cloudflare dashboard, go to the **Zaraz plans** page.
 
-   <DashButton url="/?to=/:account/tag-management/plans" />
-
+	<DashButton url="/?to=/:account/tag-management/plans" />
 2. Click the **Enable Zaraz usage billing** button and follow the instructions.
 
 ## Using Zaraz Free
diff --git a/src/content/docs/zaraz/reference/context.mdx b/src/content/docs/zaraz/reference/context.mdx
index 6f7df19926f9b1a..bda539074da4906 100644
--- a/src/content/docs/zaraz/reference/context.mdx
+++ b/src/content/docs/zaraz/reference/context.mdx
@@ -6,6 +6,7 @@ products:
 title: Zaraz Context
 sidebar:
   order: 10
+
 ---
 
 The Zaraz Context is a versatile object that provides a set of configurable properties for Zaraz, a web analytics tool for tracking user behavior on websites. These properties can be accessed and utilized across various components, including [Worker Variables](/zaraz/variables/worker-variables/) and [JSONata expressions](/zaraz/advanced/using-jsonata/).
@@ -16,6 +17,8 @@ System properties, which are automatically collected by Zaraz, provide insights
 
 ### Page information
 
+
+
 | Property               | Type   | Description                                                                                                     |
 | ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------- |
 | `system.page.query`    | Object | Key-Value object containing all query parameters in the current URL.                                            |
@@ -35,6 +38,8 @@ The keys inside the `system.cookies` are the cookies name. The property `system.
 
 ### Device information
 
+
+
 | Property                                   | Type   | Description                                                                                                              |
 | ------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------ |
 | `system.device.ip`                         | String | Visitor incoming IP address.                                                                                             |
@@ -71,6 +76,8 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ### Miscellaneous
 
+
+
 | Property                            | Type   | Description                           |
 | ----------------------------------- | ------ | ------------------------------------- |
 | `system.misc.random`                | Number | Random number unique to each request. |
@@ -80,6 +87,8 @@ The keys inside the `system.clientKV` object are formatted as Tool ID, underscor
 
 ## Event properties
 
+
+
 | Property              | Type   | Description                                                                                                                                                                                                                                                          |
 | --------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `client.__zarazTrack` | String | Returns the name of the event sent using the Track method of the Web API. Refer to [Zaraz Track](/zaraz/web-api/track/) for more information.                                                                                                                        |
diff --git a/src/content/docs/zaraz/reference/index.mdx b/src/content/docs/zaraz/reference/index.mdx
index 11447093e6b50dc..3b3f9005d879c9c 100644
--- a/src/content/docs/zaraz/reference/index.mdx
+++ b/src/content/docs/zaraz/reference/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Reference
 sidebar:
   order: 9
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/reference/properties-reference.mdx b/src/content/docs/zaraz/reference/properties-reference.mdx
index abecfe520bf0280..a6ac0acf199d0b1 100644
--- a/src/content/docs/zaraz/reference/properties-reference.mdx
+++ b/src/content/docs/zaraz/reference/properties-reference.mdx
@@ -4,8 +4,8 @@ description: Built-in properties available in Zaraz events.
 products:
   - zaraz
 title: Properties reference
----
 
+---
 import { DashButton } from "~/components";
 
 Cloudflare Zaraz offers properties that you can use when configuring the product. They are helpful to send data to a third-party tool or to create triggers as they have context about a specific user's browser session and the actions they take on the website. Below is a list of the properties you can access from the Cloudflare dashboard and their values.
@@ -14,69 +14,69 @@ Cloudflare Zaraz offers properties that you can use when configuring the product
 
 | Property               | Description                                                                                                                                                                                                                                          |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| _Event Name_           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
-| _Track Property name:_ | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
+| *Event Name*           | Returns the name of the event sent using the Track method of the Web API. Refer to the [Track method](/zaraz/web-api/track/) for more information.                                                                                                   |
+| *Track Property name:* | Returns the value of a `zaraz.track()` `eventProperties` key. The key can either be directly used in `zaraz.track()` or set using `zaraz.set()`. Set the name of your key here. Refer to the [Set method](/zaraz/web-api/set/) for more information. |
 
 ## Page Properties
 
 | Property                  | Description                                                                                                            |
 | ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| _Page character encoding_ | Returns the document character encoding from `document.characterSet`.                                                  |
-| _Page referrer_           | Returns the page referrer from `document.referrer`.                                                                    |
-| _Page title_              | Returns the page title.                                                                                                |
-| _Query param name:_       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
-| _URL_                     | Returns a string containing the entire URL.                                                                            |
-| _URL base domain_         | Returns the base domain part of the URL, without any subdomains.                                                       |
-| _URL host_                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
-| _URL hostname_            | Returns the domain of the URL.                                                                                         |
-| _URL origin_              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
-| _URL password_            | Returns the password specified before the domain name.                                                                 |
-| _URL pathname_            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
-| _URL port_                | Returns the port number of the URL.                                                                                    |
-| _URL protocol scheme_     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
-| _URL query parameters_    | Returns query parameters provided, beginning with the leading `?` character.                                           |
-| _URL username_            | Returns the username specified before the domain name.                                                                 |
+| *Page character encoding* | Returns the document character encoding from `document.characterSet`.                                                  |
+| *Page referrer*           | Returns the page referrer from `document.referrer`.                                                                    |
+| *Page title*              | Returns the page title.                                                                                                |
+| *Query param name:*       | Returns the value of a URL query parameter. When you choose this variable, you need to set the name of your parameter. |
+| *URL*                     | Returns a string containing the entire URL.                                                                            |
+| *URL base domain*         | Returns the base domain part of the URL, without any subdomains.                                                       |
+| *URL host*                | Returns the domain (that is, the hostname) followed by a `:` and the port of the URL (if a port was specified).        |
+| *URL hostname*            | Returns the domain of the URL.                                                                                         |
+| *URL origin*              | Returns the origin of the URL — that is, its scheme, domain, and port.                                                 |
+| *URL password*            | Returns the password specified before the domain name.                                                                 |
+| *URL pathname*            | Returns the path of the URL, including the initial `/`. Does not include the query string or fragment.                 |
+| *URL port*                | Returns the port number of the URL.                                                                                    |
+| *URL protocol scheme*     | Returns the protocol scheme of the URL, including the final `:`.                                                       |
+| *URL query parameters*    | Returns query parameters provided, beginning with the leading `?` character.                                           |
+| *URL username*            | Returns the username specified before the domain name.                                                                 |
 
 ## Cookies
 
 | Property       | Description                                           |
 | -------------- | ----------------------------------------------------- |
-| _Cookie name:_ | Returns cookies obtained from the browser `document`. |
+| *Cookie name:* | Returns cookies obtained from the browser `document`. |
 
 ## Device properties
 
 | Property                   | Description                                                 |
 | -------------------------- | ----------------------------------------------------------- |
-| _Browser engine_           | Returns the type of browser engine (for example, `WebKit`). |
-| _Browser engine version_   | Returns the version of the browser’s engine.                |
-| _Browser name_             | Returns the browser’s name.                                 |
-| _Browser version_          | Returns the browser’s version.                              |
-| _Device CPU_               | Returns the device’s CPU.                                   |
-| _Device IP address_        | Returns the incoming IP address.                            |
-| _Device language_          | Returns the language used.                                  |
-| _Device screen resolution_ | Returns the screen resolution of the device.                |
-| _Device type_              | Returns the type of device used (for example, `iPhone`).    |
-| _Device viewport_          | Returns the visible web page area in user’s device.         |
-| _Operating system name_    | Returns the operating system.                               |
-| _Operating system version_ | Returns the version of the operating system.                |
-| _User-agent string_        | Returns the browser’s user agent.                           |
+| *Browser engine*           | Returns the type of browser engine (for example, `WebKit`). |
+| *Browser engine version*   | Returns the version of the browser’s engine.                |
+| *Browser name*             | Returns the browser’s name.                                 |
+| *Browser version*          | Returns the browser’s version.                              |
+| *Device CPU*               | Returns the device’s CPU.                                   |
+| *Device IP address*        | Returns the incoming IP address.                            |
+| *Device language*          | Returns the language used.                                  |
+| *Device screen resolution* | Returns the screen resolution of the device.                |
+| *Device type*              | Returns the type of device used (for example, `iPhone`).    |
+| *Device viewport*          | Returns the visible web page area in user’s device.         |
+| *Operating system name*    | Returns the operating system.                               |
+| *Operating system version* | Returns the version of the operating system.                |
+| *User-agent string*        | Returns the browser’s user agent.                           |
 
 ## Device location
 
 | Property       | Description                                                                                                                                                                       |
 | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| _City_         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
-| _Continent_    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
-| _Country_ code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
-| _EU_ country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
-| _Region_       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
-| _Region_ code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
-| _Timezone_     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
+| *City*         | Returns the city of the incoming request. For example, `Lisbon`.                                                                                                                  |
+| *Continent*    | Returns the continent of the incoming request. For example, `EU`                                                                                                                  |
+| *Country* code | Returns the country code of the incoming request. For example, `PT`.                                                                                                              |
+| *EU* country   | Returns a `1` if the country of the incoming request is in the European Union, and a `0` if it is not.                                                                            |
+| *Region*       | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) name for the first level region associated with the IP address of the incoming request. For example, `Lisbon`. |
+| *Region* code  | Returns the [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) region code associated with the IP address of the incoming request. For example, `11`.                         |
+| *Timezone*     | Returns the timezone of the incoming request. For example, `Europe/Lisbon`.                                                                                                       |
 
 ## Miscellaneous
 
 | Property                   | Description                                     |
 | -------------------------- | ----------------------------------------------- |
-| _Random number_            | Returns a random number unique to each request. |
-| _Timestamp (milliseconds)_ | Returns the Unix time in milliseconds.          |
-| _Timestamp (seconds)_      | Returns the Unix time in seconds.               |
+| *Random number*            | Returns a random number unique to each request. |
+| *Timestamp (milliseconds)* | Returns the Unix time in milliseconds.          |
+| *Timestamp (seconds)*      | Returns the Unix time in seconds.               |
diff --git a/src/content/docs/zaraz/reference/settings.mdx b/src/content/docs/zaraz/reference/settings.mdx
index 40f857c4d333de9..886095c024fe466 100644
--- a/src/content/docs/zaraz/reference/settings.mdx
+++ b/src/content/docs/zaraz/reference/settings.mdx
@@ -13,7 +13,7 @@ import { Plan, DashButton } from "~/components";
 
 To configure Zaraz's general settings, go to the **Settings** page in the Cloudflare dashboard:
 
-<DashButton url="/?to=/:account/tag-management/settings" />
+   <DashButton url="/?to=/:account/tag-management/settings" />
 
 Make sure you save your changes, by selecting the **Save** button after making them.
 
@@ -45,15 +45,15 @@ When you toggle Single Page Application support off, the `pageview` trigger will
 
 Zaraz offers privacy settings you can configure, such as:
 
-- **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
+* **Remove URL query parameters**: Removes all query parameters from URLs. For example, `https://example.com/?q=hello` becomes `https://example.com/`.
 
-- **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
+* **Trim IP addresses**: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
 
-- **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
+* **Clean User Agent strings**: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
 
-- **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
+* **Remove external referrers**: Hides the page referrers URL if the hostname is different from the website's.
 
-- **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
+* **Cookie domain**: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on `foo.example.com`, the cookies will be saved on `example.com`. You can change this behavior and configure the cookies to be saved on `foo.example.com` by entering a custom domain here.
 
 ## Injection
 
@@ -93,9 +93,9 @@ Choose whether to prevent Zaraz from loading on suspected bot-initiated requests
 
 The options are:
 
-- **Block none**: Load Zaraz for all requests, even if those come from bots.
-- **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
-- **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
+* **Block none**: Load Zaraz for all requests, even if those come from bots.
+* **Block automated only**: Prevent Zaraz from loading on requests from requests in the [**Automated** category](/bots/concepts/bot-score/#bot-groupings).
+* **Block automated and likely automated**: Prevent Zaraz from loading on requests from requests in the [**Automated** and **Likely Automated** category](/bots/concepts/bot-score/#bot-groupings).
 
 ### Context Enricher
 
diff --git a/src/content/docs/zaraz/reference/supported-tools.mdx b/src/content/docs/zaraz/reference/supported-tools.mdx
index e20ce7495b724b0..1b388c261cd4ea2 100644
--- a/src/content/docs/zaraz/reference/supported-tools.mdx
+++ b/src/content/docs/zaraz/reference/supported-tools.mdx
@@ -7,6 +7,7 @@ title: Third-party tools
 head:
   - tag: title
     content: Supported tools
+
 ---
 
 Cloudflare Zaraz supports the following third-party tools:
diff --git a/src/content/docs/zaraz/variables/create-variables.mdx b/src/content/docs/zaraz/variables/create-variables.mdx
index cfce350ba75324b..7e4f9894f49c848 100644
--- a/src/content/docs/zaraz/variables/create-variables.mdx
+++ b/src/content/docs/zaraz/variables/create-variables.mdx
@@ -20,8 +20,7 @@ For example, instead of typing a specific user ID in multiple fields, you can cr
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Variables**.
 3. Select **Create variable**, and give it a name.
 4. In **Variable type** select between `String`, `Masked variable` or `Worker` from the drop-down menu. Use `Masked variable` when you have a private value that you do not want to share, such as an API token.
diff --git a/src/content/docs/zaraz/variables/edit-variables.mdx b/src/content/docs/zaraz/variables/edit-variables.mdx
index 0c30678d2adc6e5..2225f830ff4de41 100644
--- a/src/content/docs/zaraz/variables/edit-variables.mdx
+++ b/src/content/docs/zaraz/variables/edit-variables.mdx
@@ -9,14 +9,14 @@ sidebar:
 head:
   - tag: title
     content: Edit a variable
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Variables**.
 3. Locate the variable you want to edit, and select **Edit** to make your changes.
 4. Select **Save** to save your edits.
@@ -29,8 +29,7 @@ You cannot delete a variable being used in tools or triggers.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Go to **Tools Configuration** > **Third-party tools**.
 3. Locate any tools using the variable, and delete the variable from those tools.
 4. Select **Zaraz** > **Tools Configuration** > **Triggers**.
diff --git a/src/content/docs/zaraz/variables/index.mdx b/src/content/docs/zaraz/variables/index.mdx
index 98febbeb0a587f0..2201ce391be6a3a 100644
--- a/src/content/docs/zaraz/variables/index.mdx
+++ b/src/content/docs/zaraz/variables/index.mdx
@@ -6,8 +6,9 @@ products:
 title: Variables
 sidebar:
   order: 6
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 <DirectoryListing />
diff --git a/src/content/docs/zaraz/variables/worker-variables.mdx b/src/content/docs/zaraz/variables/worker-variables.mdx
index 57b8bfa416f7617..3b80fe43170c522 100644
--- a/src/content/docs/zaraz/variables/worker-variables.mdx
+++ b/src/content/docs/zaraz/variables/worker-variables.mdx
@@ -6,6 +6,7 @@ products:
 title: Worker Variables
 sidebar:
   order: 10
+
 ---
 
 import { DashButton } from "~/components";
@@ -24,8 +25,7 @@ To create a new Worker in the Cloudflare dashboard:
 
 1. In the Cloudflare dashboard, go to the **Workers and Pages** page.
 
-   <DashButton url="/?to=/:account/workers-and-pages" />
-
+	<DashButton url="/?to=/:account/workers-and-pages" />
 2. Select **Create application**.
 3. Give a name to your Worker and select **Deploy**.
 4. Select **Edit code**.
@@ -35,17 +35,17 @@ You have now created a basic Worker that responds with "Hello world." If you use
 Zaraz forwards the Zaraz Context object to your Worker as a JSON payload with a POST request. You can access any property like this:
 
 ```js
-const { system, client } = await request.json();
+const { system, client } = await request.json()
 
 /* System parameters */
-system.page.url.href; // URL of the current page
-system.page.query.gclid; // Value of the gclid query parameter
-system.device.resolution; // Device screen resolution
-system.device.language; // Browser preferred language
+system.page.url.href // URL of the current page
+system.page.query.gclid // Value of the gclid query parameter
+system.device.resolution // Device screen resolution
+system.device.language // Browser preferred language
 
 /* Zaraz Track values */
-client.value; // value from `zaraz.track("foo", {value: "bar"})`
-client.products[0].name; // name of the first product in an ecommerce call
+client.value // value from `zaraz.track("foo", {value: "bar"})`
+client.products[0].name // name of the first product in an ecommerce call
 ```
 
 Keep reading for more complete examples of different use cases or refer to [Zaraz Context](/zaraz/reference/context/).
@@ -56,8 +56,7 @@ Once your Worker is published, configuring a Worker Variable is easy.
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select the domain for which you want to configure variables.
 3. Select the **Variables** tab.
 4. Select **Create variable**.
@@ -72,8 +71,7 @@ To use your Worker Variable:
 
 1. In the Cloudflare dashboard, go to the **Tag setup** page.
 
-   <DashButton url="/?to=/:account/tag-management/zaraz" />
-
+	<DashButton url="/?to=/:account/tag-management/zaraz" />
 2. Select the domain for which you want to configure variables.
 3. Select **Edit** next to a tool that you have already configured.
 4. Select an action or add a new one.
@@ -88,11 +86,11 @@ Assuming we are sending a list of products in a cart, like this:
 
 ```js
 zaraz.ecommerce("Cart Viewed", {
-	products: [
-		{ name: "shirt", price: "50" },
-		{ name: "jacket", price: "20" },
-		{ name: "hat", price: "30" },
-	],
+  products: [
+    { name: "shirt", price: "50" },
+    { name: "jacket", price: "20" },
+    { name: "hat", price: "30" },
+  ],
 });
 ```
 
@@ -100,18 +98,18 @@ Calculating the sum can be done like this:
 
 ```js
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		// Get an array of all prices
-		const productsPrices = client.products.map((p) => p.price);
+    // Get an array of all prices
+    const productsPrices = client.products.map((p) => p.price);
 
-		// Calculate the sum
-		const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
+    // Calculate the sum
+    const sum = productsPrices.reduce((partialSum, a) => partialSum + a, 0);
 
-		return new Response(sum);
-	},
+    return new Response(sum);
+  },
 };
 ```
 
@@ -121,20 +119,20 @@ Zaraz exposes all cookies automatically under the `system.cookies` object, so th
 
 ```js
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		// Get the value of the cookie "login-cookie"
-		const cookieValue = system.cookies["login-cookie"];
+    // Get the value of the cookie "login-cookie"
+    const cookieValue = system.cookies["login-cookie"];
 
-		const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
-			method: POST,
-			body: cookieValue,
-		});
+    const userId = await fetch("https://example.com/api/getUserIdFromCookie", {
+      method: POST,
+      body: cookieValue,
+    });
 
-		return new Response(userId);
-	},
+    return new Response(userId);
+  },
 };
 ```
 
@@ -150,23 +148,23 @@ You can access this property and hash it like this:
 
 ```js
 async function digestMessage(message) {
-	const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
-	const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
-	const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
-	const hashHex = hashArray
-		.map((b) => b.toString(16).padStart(2, "0"))
-		.join(""); // convert bytes to hex string
-	return hashHex;
+  const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
+  const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
+  const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
+  const hashHex = hashArray
+    .map((b) => b.toString(16).padStart(2, "0"))
+    .join(""); // convert bytes to hex string
+  return hashHex;
 }
 
 export default {
-	async fetch(request, env) {
-		// Parse the Zaraz Context object
-		const { system, client } = await request.json();
+  async fetch(request, env) {
+    // Parse the Zaraz Context object
+    const { system, client } = await request.json();
 
-		const { email } = client;
+    const { email } = client;
 
-		return new Response(await digestMessage(email));
-	},
+    return new Response(await digestMessage(email));
+  },
 };
 ```
diff --git a/src/content/docs/zaraz/web-api/debug-mode.mdx b/src/content/docs/zaraz/web-api/debug-mode.mdx
index 3e17a55399dfbf2..a2110d8626e7f2c 100644
--- a/src/content/docs/zaraz/web-api/debug-mode.mdx
+++ b/src/content/docs/zaraz/web-api/debug-mode.mdx
@@ -6,6 +6,7 @@ products:
 title: Debug mode
 sidebar:
   order: 4
+
 ---
 
 import { DashButton } from "~/components";
@@ -15,14 +16,13 @@ You can set this cookie manually or via the `zaraz.debug` helper function availa
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Copy your **Debug Key**.
 3. Open a web browser and access its Developer Tools. For example, to access Developer Tools in Google Chrome, select **View** > **Developer** > **Developer Tools**.
 4. Select the **Console** pane and enter the following command to create a debug cookie:
 
    ```js
-   zaraz.debug("YOUR_DEBUG_KEY");
+   zaraz.debug("YOUR_DEBUG_KEY")
    ```
 
 Zaraz’s debug mode is now enabled. A pop-up window will show up with the debugger information. To exit debug mode, remove the cookie by typing `zaraz.debug()` in the console pane of the browser.
diff --git a/src/content/docs/zaraz/web-api/ecommerce.mdx b/src/content/docs/zaraz/web-api/ecommerce.mdx
index 94708e09a23b5eb..47b9b8b44b53c60 100644
--- a/src/content/docs/zaraz/web-api/ecommerce.mdx
+++ b/src/content/docs/zaraz/web-api/ecommerce.mdx
@@ -31,8 +31,7 @@ You do not need to map e-commerce events to triggers. Zaraz automatically forwar
 
 1. In the Cloudflare dashboard, go to the **Settings** page.
 
-   <DashButton url="/?to=/:account/tag-management/settings" />
-
+	<DashButton url="/?to=/:account/tag-management/settings" />
 2. Enable **E-commerce tracking**.
 3. Select **Save**.
 4. Go to **Zaraz** > **Tools Configuration** > **Third-party tools**.
diff --git a/src/content/docs/zaraz/web-api/index.mdx b/src/content/docs/zaraz/web-api/index.mdx
index be94552a3782c97..15b544bb65b4744 100644
--- a/src/content/docs/zaraz/web-api/index.mdx
+++ b/src/content/docs/zaraz/web-api/index.mdx
@@ -6,9 +6,10 @@ products:
 title: Web API
 sidebar:
   order: 3
+
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Zaraz provides a client-side web API that you can use anywhere inside the `<body>` tag of a page.
 
diff --git a/src/content/docs/zaraz/web-api/set.mdx b/src/content/docs/zaraz/web-api/set.mdx
index 447578481222c7a..0d9f29ac5943204 100644
--- a/src/content/docs/zaraz/web-api/set.mdx
+++ b/src/content/docs/zaraz/web-api/set.mdx
@@ -9,26 +9,27 @@ sidebar:
 head:
   - tag: title
     content: zaraz.set
+
 ---
 
 You can use `zaraz.set()` anywhere inside the `<body>` tag of a page:
 
 ```js
-zaraz.set(key, value, [options]);
+zaraz.set(key, value, [options])
 ```
 
 Set is useful if you want to make a variable available in all your events without manually setting it every time you are using `zaraz.track()`. For the purpose of this example, assume users in your system have a unique identifier that you want to send to your tools. You might have many `zaraz.track()` calls all sharing this one parameter:
 
 ```js
-zaraz.track("form completed", { userId: "ABC-123" });
+zaraz.track("form completed", {userId: "ABC-123"})
 ```
 
 ```js
-zaraz.track("button clicked", { userId: "ABC-123", value: 200 });
+zaraz.track("button clicked", {userId: "ABC-123", value: 200})
 ```
 
 ```js
-zaraz.track("cart viewed", { items: 3, userId: "ABC-123" });
+zaraz.track("cart viewed", {items: 3, userId: "ABC-123"})
 ```
 
 Here, all the events are collecting the `userId` key, and the code for setting that key repeats itself. With `zaraz.set()` you can avoid repetition by setting the key once when the page loads. Zaraz will then attach this key to all future `zaraz.track()` calls.
@@ -38,23 +39,23 @@ Using the above data as the example, if you use `zaraz.set("userId", "ABC-123")`
 Another example:
 
 ```js
-zaraz.set("product_name", "t-shirt", { scope: "page" });
+zaraz.set('product_name', 't-shirt', {scope: 'page'})
 ```
 
-Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable _Track Property name:_, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
+Keys that are sent using `zaraz.set()` can be used inside tool actions exactly like keys in the `eventProperties` of `zaraz.track()`. So, the above `product` key is accessible through the Cloudflare dashboard with the variable *Track Property name:*, and setting its name as `product_name`. Zaraz will then replace it with `t-shirt`.
 
 ![Example of how to create a variable with the Set method, tracking t-shirts](~/assets/images/zaraz/set.png)
 
 The `[options]` argument is an optional object and can include a `scope` property that has a string value. This property determines the lifetime of this key, meaning for how long Zaraz should keep attaching it to `zaraz.track()` calls. Allowed values are:
 
-- `page`: To set the key for the context of the current page only.
-- `session`: To make the key last the whole session.
-- `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
+* `page`: To set the key for the context of the current page only.
+* `session`: To make the key last the whole session.
+* `persist`: To save the key across sessions. This is the default mode and uses `localStorage` to save the value.
 
 In the previous example, `{scope: 'page'}` makes the `product_name` property available to all `zaraz.track()` calls in the current page, but will not affect calls after visitors navigate to other pages.
 
 To unset a variable, set it to `undefined`. The variable will then be removed from all scopes it was included in, and will not be automatically sent with future `zaraz.track` calls. For example:
 
 ```js
-zaraz.set("product_name", undefined);
+zaraz.set('product_name', undefined)
 ```
diff --git a/src/content/partials/1.1.1.1/captive-portals.mdx b/src/content/partials/1.1.1.1/captive-portals.mdx
index 7d4223b076a5f3f..9a22c3361ba00f0 100644
--- a/src/content/partials/1.1.1.1/captive-portals.mdx
+++ b/src/content/partials/1.1.1.1/captive-portals.mdx
@@ -12,4 +12,4 @@ If you are experiencing connectivity issues related to captive portals:
 2. Connect to the Wi-Fi network.
 3. Once the connection has been established, re-add the static IP addresses or enable the 1.1.1.1 app.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/agents/unique-agents.mdx b/src/content/partials/agents/unique-agents.mdx
index bd157735e3ad07f..d3f96c7f9fa15e9 100644
--- a/src/content/partials/agents/unique-agents.mdx
+++ b/src/content/partials/agents/unique-agents.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
@@ -10,4 +11,4 @@ This allows you to avoid synchronizing state across requests: if an Agent instan
 
 If the client disconnects, you can always route the client back to the exact same Agent and pick up where they left off.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ai-crawl-control/plan-comparison.mdx b/src/content/partials/ai-crawl-control/plan-comparison.mdx
index a03e263b7030fed..f56f51d865fe7c5 100644
--- a/src/content/partials/ai-crawl-control/plan-comparison.mdx
+++ b/src/content/partials/ai-crawl-control/plan-comparison.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                               |
-| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)                   |
-| Maximum 24-hour analytics window                                                                                              | Configurable analytics timeframes                                                                                                                  |
-| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
+| All plans                                                                                                                     | Enterprise plans with Bot Management                                                                                                       |
+| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| AI crawler detection via [user agent strings](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) | Advanced AI crawler detection via [Bot Management detection ID](/bots/reference/bot-management-variables/#ruleset-engine-fields)           |
+| Maximum 24-hour analytics window                                                                                              |  Configurable analytics timeframes                                                                                                      |
+| Allow/block controls                                                                                                          | Allow/block controls, and the ability to charge AI crawlers using [pay per crawl](/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/) |
\ No newline at end of file
diff --git a/src/content/partials/ai-gateway/analytics-dashboard.mdx b/src/content/partials/ai-gateway/analytics-dashboard.mdx
index 5dbb03ea869ad8b..9c812ba529cb5bb 100644
--- a/src/content/partials/ai-gateway/analytics-dashboard.mdx
+++ b/src/content/partials/ai-gateway/analytics-dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To view analytics in the dashboard:
diff --git a/src/content/partials/ai-gateway/logging.mdx b/src/content/partials/ai-gateway/logging.mdx
index 9522593e0222102..ae7983b75652584 100644
--- a/src/content/partials/ai-gateway/logging.mdx
+++ b/src/content/partials/ai-gateway/logging.mdx
@@ -1,7 +1,6 @@
 ---
 {}
 ---
-
 import { DashButton } from "~/components";
 
 To change the default log configuration in the dashboard:
diff --git a/src/content/partials/ai-gateway/universal-gateway-example.mdx b/src/content/partials/ai-gateway/universal-gateway-example.mdx
index 6950494e7677012..c0bbda990100faa 100644
--- a/src/content/partials/ai-gateway/universal-gateway-example.mdx
+++ b/src/content/partials/ai-gateway/universal-gateway-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```bash title="Request"
diff --git a/src/content/partials/ai-search/rest-api-auth.mdx b/src/content/partials/ai-search/rest-api-auth.mdx
index afc3a5199d0f9b0..84c53bc88b43199 100644
--- a/src/content/partials/ai-search/rest-api-auth.mdx
+++ b/src/content/partials/ai-search/rest-api-auth.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 All requests require an API token with **AI Search:Edit** and **AI Search:Run** permissions.
 
diff --git a/src/content/partials/analytics/customer_metadata_boundary_error.mdx b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
index 892e43f082a7c02..aa5a25eabdfe090 100644
--- a/src/content/partials/analytics/customer_metadata_boundary_error.mdx
+++ b/src/content/partials/analytics/customer_metadata_boundary_error.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 If you encounter a message on the dashboard indicating that your data is unavailable due to your account's Metadata Boundary configuration, this is because you are trying to access data that is not stored in your region (that is, you are in the US and trying to access data that is only stored in the EU, or vice versa). If you receive this error message while being in the region where your data is stored, there are two potential reasons why you might get this message:
 
-- Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
+* Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.
 
-- If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
+* If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.
diff --git a/src/content/partials/analytics/network-analytics-requirements.mdx b/src/content/partials/analytics/network-analytics-requirements.mdx
index 509b51ff43b0ffd..972d6cea688b524 100644
--- a/src/content/partials/analytics/network-analytics-requirements.mdx
+++ b/src/content/partials/analytics/network-analytics-requirements.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 :::note[Requirements]
 
 Network Analytics requires the following:
 
-- A Cloudflare Enterprise plan.
-- Cloudflare Magic Transit or Spectrum.
-- Cloudflare WAN.
+* A Cloudflare Enterprise plan.
+* Cloudflare Magic Transit or Spectrum.
+* Cloudflare WAN.
   :::
diff --git a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
index bc1a23a14f531b7..d2dfe96892e93b6 100644
--- a/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
+++ b/src/content/partials/analytics/network-analytics-v1-deprecation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Network Analytics v1 (NAv1) is now deprecated.** For more information on Network Analytics v2 (NAv2), refer to [Cloudflare Network Analytics](/analytics/network-analytics/).
diff --git a/src/content/partials/api-shield/label-methodology.mdx b/src/content/partials/api-shield/label-methodology.mdx
index 96af54686fabef0..72400e85c006187 100644
--- a/src/content/partials/api-shield/label-methodology.mdx
+++ b/src/content/partials/api-shield/label-methodology.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-| 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. |
+| 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. |
diff --git a/src/content/partials/api-shield/mtls-api-shield-support.mdx b/src/content/partials/api-shield/mtls-api-shield-support.mdx
index 1588524b353a3c5..0224d99943797f8 100644
--- a/src/content/partials/api-shield/mtls-api-shield-support.mdx
+++ b/src/content/partials/api-shield/mtls-api-shield-support.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/api-shield/mtls-create-rule.mdx b/src/content/partials/api-shield/mtls-create-rule.mdx
index 8385e54de0b19d4..ac25847bffa79f2 100644
--- a/src/content/partials/api-shield/mtls-create-rule.mdx
+++ b/src/content/partials/api-shield/mtls-create-rule.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Steps, DashButton } from "~/components";
+import { Steps, DashButton } from "~/components"
 
 <Steps>
 1. In the Cloudflare dashboard, go to **Client Certificates** page.
@@ -15,4 +16,4 @@ import { Steps, DashButton } from "~/components";
 6. Select **Deploy** to make the rule active.
 </Steps>
 
-Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
+Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.
\ No newline at end of file
diff --git a/src/content/partials/api-shield/rate-limit-user.mdx b/src/content/partials/api-shield/rate-limit-user.mdx
index d47e2e46b45069e..9cdc3591641dfcf 100644
--- a/src/content/partials/api-shield/rate-limit-user.mdx
+++ b/src/content/partials/api-shield/rate-limit-user.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ### Rate limit by user (JWT claim)
diff --git a/src/content/partials/api-shield/required-session-identifiers.mdx b/src/content/partials/api-shield/required-session-identifiers.mdx
index 59e54427d1d871b..a1f6276e094c00c 100644
--- a/src/content/partials/api-shield/required-session-identifiers.mdx
+++ b/src/content/partials/api-shield/required-session-identifiers.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You must have specific entitlements to configure session identifiers or cookies as a form of identifiers, such as an Enterprise subscription, for features such as [API Discovery](/api-shield/security/api-discovery/), [Sequence Mitigation](/api-shield/security/sequence-mitigation/) or [rate limiting recommendations](/api-shield/security/volumetric-abuse-detection/), and to see results in [Sequence Analytics](/api-shield/security/sequence-analytics/) and [Authentication Posture](/api-shield/security/authentication-posture/).
diff --git a/src/content/partials/api-shield/sequence-mitigation-availability.mdx b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
index 94c7f150023934f..38bbe706bb998a3 100644
--- a/src/content/partials/api-shield/sequence-mitigation-availability.mdx
+++ b/src/content/partials/api-shield/sequence-mitigation-availability.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
+Sequence mitigation is currently in a closed beta and is only available for Enterprise customers. If you would like to be included in the beta, contact your account team.
\ No newline at end of file
diff --git a/src/content/partials/api-shield/session-identifiers.mdx b/src/content/partials/api-shield/session-identifiers.mdx
index ef978913a8fe1cf..4e517b779b2b3a9 100644
--- a/src/content/partials/api-shield/session-identifiers.mdx
+++ b/src/content/partials/api-shield/session-identifiers.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 While not strictly required, it is recommended that you configure your <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> when getting started with API Shield. When Cloudflare inspects your API traffic for individual sessions, we can offer more tools for visibility, management, and control.
 
@@ -10,4 +11,4 @@ If you are unsure of the session identifiers that your API uses, consult with yo
 
 Session identifiers should uniquely identify API clients. A common session identifier for API traffic is the `Authorization` header. When a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) is used by the API for client authentication, its value may change over time. You can use a claim value inside the JWT such as `sub` or `email` as a session ID to uniquely identify the session over time.
 
-If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
+If your API uses the `Authorization` header on more than 1% of successful requests to your zone, Cloudflare will automatically set it as the API Shield session identifier.
\ No newline at end of file
diff --git a/src/content/partials/billing/two-payment-methods.mdx b/src/content/partials/billing/two-payment-methods.mdx
index 9db0c042394f0a1..fcd2e4ffca05097 100644
--- a/src/content/partials/billing/two-payment-methods.mdx
+++ b/src/content/partials/billing/two-payment-methods.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/bots/about-plan-considerations.mdx b/src/content/partials/bots/about-plan-considerations.mdx
index dbee048b258ff34..13c3ff7327eaed5 100644
--- a/src/content/partials/bots/about-plan-considerations.mdx
+++ b/src/content/partials/bots/about-plan-considerations.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 Bot Fight Mode and Super Bot Fight Mode use the same underlying technology that powers our [Bot Management](https://www.cloudflare.com/products/bot-management/) product. Specifically, these products:
 
-- Protect entire domains without endpoint restrictions
-- Cannot be customized, adjusted, or reconfigured via WAF custom rules
+* Protect entire domains without endpoint restrictions
+* Cannot be customized, adjusted, or reconfigured via WAF custom rules
 
 Although these products are designed to fight malicious actors on the Internet, they may challenge API or mobile app traffic. For more granular control, upgrade to [Bot Management for Enterprise](/bots/plans/bm-subscription/).
diff --git a/src/content/partials/bots/analytics-features.mdx b/src/content/partials/bots/analytics-features.mdx
index 5c8c8cc61b1b641..8b21959f185efd0 100644
--- a/src/content/partials/bots/analytics-features.mdx
+++ b/src/content/partials/bots/analytics-features.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare uses adaptive bitrate technology to show sampled data — most customers will see a 1-10% sample depending on how much information they are trying to view. Tooltips on the page will display the current sample rate.
diff --git a/src/content/partials/bots/bfm-change-notice.mdx b/src/content/partials/bots/bfm-change-notice.mdx
index e4fb1dd54926f1a..d7474bab9acd502 100644
--- a/src/content/partials/bots/bfm-change-notice.mdx
+++ b/src/content/partials/bots/bfm-change-notice.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Change notice for Super Bot Fight Mode rulesets]
diff --git a/src/content/partials/bots/bm-analytics-features.mdx b/src/content/partials/bots/bm-analytics-features.mdx
index 9af38b36aca085c..7dc1163ab88af8d 100644
--- a/src/content/partials/bots/bm-analytics-features.mdx
+++ b/src/content/partials/bots/bm-analytics-features.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 For a full tour of Bot Analytics, see [our blog post](https://blog.cloudflare.com/introducing-bot-analytics/). At a high level, the tool includes:
 
-- **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on _automated_ and _likely automated_ traffic.
-- **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
-- **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
-- **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
+* **Requests by bot score**: View your total domain traffic and segment it vertically by traffic type. Keep an eye on *automated* and *likely automated* traffic.
+* **Bot score distribution**: View the number of requests assigned a bot score 1 through 99.
+* **Bot score source**: Identify the most common detection engines used to score your traffic. Hover over a tooltip to learn more about each engine.
+* **Top requests by attribute**: View more detailed information on specific IP addresses and other characteristics.
 
 Bot Analytics shows up to one week of data at a time and can display data up to 30 days old. Bot Analytics displays data in real time in most cases.
diff --git a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
index 4a7b8ba166882b8..792c3896e90dbdb 100644
--- a/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
+++ b/src/content/partials/bots/bot-settings-vs-custom-rules.mdx
@@ -6,13 +6,13 @@
 
 The following features are handled automatically in **Security Settings** and do not require custom rules:
 
-| Feature                                         | Handled by bot settings | Requires custom rules                                    |
-| ----------------------------------------------- | ----------------------- | -------------------------------------------------------- |
-| Block or challenge definitely automated traffic | Yes                     | Only for path-specific or threshold-tuned rules          |
-| Block or challenge likely automated traffic     | Not available on Pro    | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
-| Allow or block verified bots                    | Yes                     | No                                                       |
-| Block AI crawlers                               | Yes                     | Only to target individual AI crawlers                    |
-| Protect static resources                        | Yes                     | No                                                       |
-| Optimize for WordPress                          | Yes                     | No                                                       |
+| Feature | Handled by bot settings | Requires custom rules |
+| --- | --- | --- |
+| Block or challenge definitely automated traffic | Yes | Only for path-specific or threshold-tuned rules |
+| Block or challenge likely automated traffic | Not available on Pro | Yes, with [Bot Management](/bots/plans/bm-subscription/) |
+| Allow or block verified bots | Yes | No |
+| Block AI crawlers | Yes | Only to target individual AI crawlers |
+| Protect static resources | Yes | No |
+| Optimize for WordPress | Yes | No |
 
-For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
+For more details on when custom rules are needed, refer to [custom rules](/bots/additional-configurations/custom-rules/).
\ No newline at end of file
diff --git a/src/content/partials/bots/bots-ad.mdx b/src/content/partials/bots/bots-ad.mdx
index f690a31c6f51ec3..da728dfe8e0016d 100644
--- a/src/content/partials/bots/bots-ad.mdx
+++ b/src/content/partials/bots/bots-ad.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Deprecation notice]
diff --git a/src/content/partials/bots/bots-cookie.mdx b/src/content/partials/bots/bots-cookie.mdx
index 62c2872d9a483c0..43bda678f796566 100644
--- a/src/content/partials/bots/bots-cookie.mdx
+++ b/src/content/partials/bots/bots-cookie.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare uses the `__cf_bm` cookie to smooth out the <GlossaryTooltip term="bot score">bot score</GlossaryTooltip> and reduce false positives for actual user sessions.
 
diff --git a/src/content/partials/bots/bots-heuristics.mdx b/src/content/partials/bots/bots-heuristics.mdx
index be4df17066ad18c..4cd143b9744bd18 100644
--- a/src/content/partials/bots/bots-heuristics.mdx
+++ b/src/content/partials/bots/bots-heuristics.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
+The **Heuristics** engine processes all requests. Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints.
\ No newline at end of file
diff --git a/src/content/partials/bots/bots-jsd.mdx b/src/content/partials/bots/bots-jsd.mdx
index 7256269923ab642..0db49de66e6f82f 100644
--- a/src/content/partials/bots/bots-jsd.mdx
+++ b/src/content/partials/bots/bots-jsd.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The [**JavaScript Detections (JSD)**](/bots/additional-configurations/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines.
diff --git a/src/content/partials/bots/bots-ml.mdx b/src/content/partials/bots/bots-ml.mdx
index a14e20442d1ecca..df1136f568be04c 100644
--- a/src/content/partials/bots/bots-ml.mdx
+++ b/src/content/partials/bots/bots-ml.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
 The **Machine Learning (ML)** engine accounts for the majority of all detections, distinguishing between human and bot traffic. This approach leverages our global network, which proxies billions of requests daily, to identify both automated and human traffic.
 
-The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99).
+The ML system uses a supervised machine learning methodology to determine the final Bot Score (1–99). 
 
 The core model relies on the following process:
 
 - Input Variables (X): Various request features (headers, session characteristics, and browser signals) collected from traffic across the Cloudflare network.
 - Output Variable (Y): The predicted probability that a client is human (such as the probability of successfully solving a Challenge). This probability is mapped to the final 1–99 Bot Score.
 
-We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
+We constantly train the ML engine on a periodic basis using vast, anonymized data to ensure it remains accurate and adapts to new threats. Customers can analyze the request features used by these models via their own logs, such as Cloudflare [Logpull](/logs/logpull/) or [Logpush](/logs/logpush/).
\ No newline at end of file
diff --git a/src/content/partials/bots/buttons-plan-pages.mdx b/src/content/partials/bots/buttons-plan-pages.mdx
index fcacd4331504ccc..f4bb5390173d743 100644
--- a/src/content/partials/bots/buttons-plan-pages.mdx
+++ b/src/content/partials/bots/buttons-plan-pages.mdx
@@ -1,18 +1,8 @@
 ---
 {}
+
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton } from "~/components"
 
-<LinkButton variant="primary" href="/bots/plans/free/">
-	Free
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/pro/">
-	Pro
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/biz-and-ent/">
-	Business
-</LinkButton>
-<LinkButton variant="primary" href="/bots/plans/bm-subscription/">
-	Bot Management for Enterprise
-</LinkButton>
+ <LinkButton variant="primary" href="/bots/plans/free/">Free</LinkButton> <LinkButton variant="primary" href="/bots/plans/pro/">Pro</LinkButton> <LinkButton variant="primary" href="/bots/plans/biz-and-ent/">Business</LinkButton> <LinkButton variant="primary" href="/bots/plans/bm-subscription/">Bot Management for Enterprise</LinkButton>
diff --git a/src/content/partials/bots/content-security-policy-limitation.mdx b/src/content/partials/bots/content-security-policy-limitation.mdx
index e42c9647319100a..f62345793fe5368 100644
--- a/src/content/partials/bots/content-security-policy-limitation.mdx
+++ b/src/content/partials/bots/content-security-policy-limitation.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from '~/components';
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip>, you need to take additional steps to implement JavaScript Detections:
 
@@ -15,4 +16,4 @@ If you have a <GlossaryTooltip term="content security policy (CSP)">Content Secu
 :::caution[Warning]
 
 JavaScript Detections is not supported with `nonce` set via `<meta>` tags.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/bots/disable-cf-bm-cookie.mdx b/src/content/partials/bots/disable-cf-bm-cookie.mdx
index 3e1a4f6255413c8..a19d23bd96c3778 100644
--- a/src/content/partials/bots/disable-cf-bm-cookie.mdx
+++ b/src/content/partials/bots/disable-cf-bm-cookie.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can disable the `__cf_bm` cookie using the `bm_cookie_enabled` field [via the API](/api/resources/bot_management/methods/update/).
diff --git a/src/content/partials/bots/endpoint-label-warning.mdx b/src/content/partials/bots/endpoint-label-warning.mdx
index 1d94ff8d3590322..3e0748847f1cfbc 100644
--- a/src/content/partials/bots/endpoint-label-warning.mdx
+++ b/src/content/partials/bots/endpoint-label-warning.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: endpoint
+
 ---
 
 :::caution[Login {props.one} endpoints]
-Not all login {props.one} endpoints are automatically detected.
+Not all login {props.one} endpoints are automatically detected. 
 
-Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized.
+Cloudflare evaluates and automatically detects your website or application's login {props.one} endpoint, but non-traditional login {props.one} endpoints may not be recognized. 
 
 For example, if you have a non-traditional login endpoint, you should label it with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/). Once you have applied the `cf-log-in` label, Cloudflare will use the labeled endpoint for account takeover detection decisions.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/bots/execution-order.mdx b/src/content/partials/bots/execution-order.mdx
index 4d3aa8ec0155216..458ad91c88f6909 100644
--- a/src/content/partials/bots/execution-order.mdx
+++ b/src/content/partials/bots/execution-order.mdx
@@ -7,4 +7,4 @@ flowchart LR
 accTitle: Super Bot Fight Mode and custom rules execution order diagram
 accDescr: This diagram details the execution order of custom rules before Super Bot Fight Mode managed rules.
 A[Custom rules] --> B[Block AI bots<br>managed rule] --> C[Other SBFM managed rules]
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/bots/flexible-sbfm.mdx b/src/content/partials/bots/flexible-sbfm.mdx
index d5c7abc133997b6..207bbda9d1f29ee 100644
--- a/src/content/partials/bots/flexible-sbfm.mdx
+++ b/src/content/partials/bots/flexible-sbfm.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-In parts of your site where you want bot traffic, you can use the [_Skip_ action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
+In parts of your site where you want bot traffic, you can use the [*Skip* action](/waf/custom-rules/skip/) in [WAF custom rules](/waf/custom-rules/) to specify where Super Bot Fight Mode should not run.
 
 You can use the [Rules language](/ruleset-engine/rules-language/) and its [operators](/ruleset-engine/rules-language/operators/) and [fields](/ruleset-engine/rules-language/fields/) in custom rules to configure a scoped rule for approved automated traffic in Super Bot Fight Mode.
diff --git a/src/content/partials/bots/ja3-ja4-null.mdx b/src/content/partials/bots/ja3-ja4-null.mdx
index e8829ace2150293..68bc0569df18296 100644
--- a/src/content/partials/bots/ja3-ja4-null.mdx
+++ b/src/content/partials/bots/ja3-ja4-null.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or empty in logs under specific circumstances:
@@ -8,4 +9,4 @@ The JA3 or JA4 fingerprint is an SSL/TLS-based identifier and can be null or emp
 - The field may be empty when a [Worker](/workers/) sends a request to a zone that is either internal to Cloudflare's network (O2O traffic that is not proxied) or to a third-party origin, or when a Worker is routing traffic to the target zone.
 - The fingerprints may be absent when Bot Management itself is skipped for a request, as the feature is responsible for calculating and populating these values.
 
-Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
+Generally, [O2O traffic](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/) should include JA3 or JA4 fingerprints unless a Worker is used to route traffic from the eyeball (client-facing) zone to the target zone.
\ No newline at end of file
diff --git a/src/content/partials/bots/jsd-availability.mdx b/src/content/partials/bots/jsd-availability.mdx
index 3306814fd548d25..57c501ca55fd5a0 100644
--- a/src/content/partials/bots/jsd-availability.mdx
+++ b/src/content/partials/bots/jsd-availability.mdx
@@ -1,5 +1,6 @@
 ---
 inputParameters: planType;;enablement
+
 ---
 
-For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
+For {props.planType} customers, [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) is {props.enablement}.
\ No newline at end of file
diff --git a/src/content/partials/bots/plan-get-started.mdx b/src/content/partials/bots/plan-get-started.mdx
index 3e26918905eccd4..ab81f675f77e822 100644
--- a/src/content/partials/bots/plan-get-started.mdx
+++ b/src/content/partials/bots/plan-get-started.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To get started, review our [setup guides](/bots/get-started/). If you have any questions, visit the [community](https://community.cloudflare.com/) to engage with other Cloudflare users.
diff --git a/src/content/partials/bots/plan-intro.mdx b/src/content/partials/bots/plan-intro.mdx
index 0b5da491920a683..e2f77067f05bc6d 100644
--- a/src/content/partials/bots/plan-intro.mdx
+++ b/src/content/partials/bots/plan-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To learn more about features and functionality, select a plan.
diff --git a/src/content/partials/bots/sequence-rules.mdx b/src/content/partials/bots/sequence-rules.mdx
index f1469b3b97b7941..5a37ee6b8ddf181 100644
--- a/src/content/partials/bots/sequence-rules.mdx
+++ b/src/content/partials/bots/sequence-rules.mdx
@@ -1,9 +1,6 @@
 ---
 inputParameters: addLink;;Link
+
 ---
 
-<a href={props.two}>{props.one}</a> uses cookies to track the order of requests
-a user has made and the time between requests and makes them available via
-[Cloudflare Rules](/rules/). This allows you to write rules that match valid or
-invalid sequences. The specific cookies used to validate sequences are called
-sequence cookies.
+<a href={props.two}>{props.one}</a> uses cookies to track the order of requests a user has made and the time between requests and makes them available via [Cloudflare Rules](/rules/). This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
diff --git a/src/content/partials/bots/signals-intelligence-and-ja4.mdx b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
index 5f9750c2e03b2f8..d4985540fd03195 100644
--- a/src/content/partials/bots/signals-intelligence-and-ja4.mdx
+++ b/src/content/partials/bots/signals-intelligence-and-ja4.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 If you want to use JA4 fingerprints and Signals Intelligence, your Workers script must be able to handle the absence of any field in the array, including:
 
-- The possibility that the JA4 fingerprint could be missing.
-- The possibility that the `ja4Signals` array could be missing.
-- Results with `NaN` or `Infinity` values will be excluded from the array.
+* The possibility that the JA4 fingerprint could be missing.
+* The possibility that the `ja4Signals` array could be missing.
+* Results with `NaN` or `Infinity` values will be excluded from the array.
diff --git a/src/content/partials/bots/verified-bots.mdx b/src/content/partials/bots/verified-bots.mdx
index 641b00e41848448..643ff4708ca88c8 100644
--- a/src/content/partials/bots/verified-bots.mdx
+++ b/src/content/partials/bots/verified-bots.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare maintains an internal directory of [verified bot](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/) that are associated with search engine optimization (SEO), website monitoring, and more.
diff --git a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
index 6674b5b0b076f4f..d6d1aa6348cc9ab 100644
--- a/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
+++ b/src/content/partials/browser-run/improve-blurry-screenshot-resolution.mdx
@@ -3,14 +3,13 @@
 If you set a large viewport width and height, your screenshot may appear blurry or pixelated. This can happen if your browser's default `deviceScaleFactor` (which defaults to 1) is not high enough for the viewport.
 
 To fix this, increase the value of the `deviceScaleFactor`.
-
 ```json
 {
-	"url": "https://cloudflare.com/",
-	"viewport": {
-		"width": 3600,
-		"height": 2400,
-		"deviceScaleFactor": 2
-	}
+  "url": "https://cloudflare.com/",
+  "viewport": {
+    "width": 3600,
+    "height": 2400,
+    "deviceScaleFactor": 2
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/byoip/cloudflare-asn-callout.mdx b/src/content/partials/byoip/cloudflare-asn-callout.mdx
index c2e64662ef201ba..c4c4f51e5e3f276 100644
--- a/src/content/partials/byoip/cloudflare-asn-callout.mdx
+++ b/src/content/partials/byoip/cloudflare-asn-callout.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Use Cloudflare's ASN]
 The process described on this page only supports using Cloudflare's ASN (AS13335). If you must announce the prefixes under your own ASN, contact your account team.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/byoip/loa.mdx b/src/content/partials/byoip/loa.mdx
index 6f4223cd8341462..c4320799ddc0c7b 100644
--- a/src/content/partials/byoip/loa.mdx
+++ b/src/content/partials/byoip/loa.mdx
@@ -35,4 +35,4 @@ Regards,
 [COMPANY NAME]
 [COMPANY ADDRESS]
 [COMPANY STAMP]
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/byoip/validate-prefix-endpoint.mdx b/src/content/partials/byoip/validate-prefix-endpoint.mdx
index 3d0fbbd3b42c0d2..096f54fc687f97e 100644
--- a/src/content/partials/byoip/validate-prefix-endpoint.mdx
+++ b/src/content/partials/byoip/validate-prefix-endpoint.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
diff --git a/src/content/partials/cache/cache-reserve-billing-note.mdx b/src/content/partials/cache/cache-reserve-billing-note.mdx
index 6f0fbe8ec743390..1d60713a3590fee 100644
--- a/src/content/partials/cache/cache-reserve-billing-note.mdx
+++ b/src/content/partials/cache/cache-reserve-billing-note.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 The billable quantity is rounded up to the nearest million.
 
+
 :::
diff --git a/src/content/partials/cache/cache-reserve-eligibility.mdx b/src/content/partials/cache/cache-reserve-eligibility.mdx
index 426e01aee0d369e..4222abac1e72533 100644
--- a/src/content/partials/cache/cache-reserve-eligibility.mdx
+++ b/src/content/partials/cache/cache-reserve-eligibility.mdx
@@ -7,4 +7,4 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 - Be cacheable, according to Cloudflare's standard [cacheability factors](/cache/).
 - Have a freshness time-to-live (TTL) of at least 10 hours (set by any means such as Cache-Control / [CDN-Cache-Control](/cache/concepts/cache-control/) origin response headers, [Edge Cache TTL](/cache/how-to/edge-browser-cache-ttl/#edge-cache-ttl), [Cache TTL By Status](/cache/how-to/configure-cache-status-code/), or [Cache Rules](/cache/how-to/cache-rules/)),
 - Have a Content-Length response header.
-- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
+- When using [Image transformations](/images/optimization/hosted-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-intro.mdx b/src/content/partials/cache/cache-reserve-intro.mdx
index d4dd113880b158a..e2f420e60a81457 100644
--- a/src/content/partials/cache/cache-reserve-intro.mdx
+++ b/src/content/partials/cache/cache-reserve-intro.mdx
@@ -4,4 +4,4 @@
 
 Cache Reserve is a large, persistent data store [implemented on top of R2](/r2/). By pushing a single button in the dashboard, your website's cacheable content will be written to Cache Reserve.
 
-In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
+In the same way that Tiered Cache builds a hierarchy of caches between your visitors and your origin, Cache Reserve serves as the ultimate upper-tier cache, that will reserve storage space for your assets for as long as you want. This ensures that your content is served from cache longer, shielding your origin from unneeded egress fees.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-limits.mdx b/src/content/partials/cache/cache-reserve-limits.mdx
index a8fa9e8ea8c5d44..e98031a3e1fb9ba 100644
--- a/src/content/partials/cache/cache-reserve-limits.mdx
+++ b/src/content/partials/cache/cache-reserve-limits.mdx
@@ -7,4 +7,4 @@
 - [Vary for images](/cache/advanced-configuration/vary-for-images/) is currently not compatible with Cache Reserve.
 - Requests to [R2 public buckets linked to a zone's domain](/r2/buckets/public-buckets/) will not use Cache Reserve. Enabling Cache Reserve for the connected zone will use Cache Reserve only for requests not destined for the R2 bucket.
 - Cache Reserve makes requests for uncompressed content directly from the origin. Unlike the standard Cloudflare CDN, Cache Reserve does not include the `Accept-Encoding: gzip` header when sending requests to the origin.
-- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
+- Cache Reserve is bypassed when using the Cloudflare [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup.
\ No newline at end of file
diff --git a/src/content/partials/cache/cache-reserve-operations.mdx b/src/content/partials/cache/cache-reserve-operations.mdx
index ebbfac04358fb8a..7d9ec8cabea8443 100644
--- a/src/content/partials/cache/cache-reserve-operations.mdx
+++ b/src/content/partials/cache/cache-reserve-operations.mdx
@@ -22,4 +22,4 @@ Other purge methods, such as purge by tag, host, prefix, or purge everything wil
 
 :::note
 Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cache/edge-ttl.mdx b/src/content/partials/cache/edge-ttl.mdx
index 02f8bc5af24dabe..1a84b61e6d0f948 100644
--- a/src/content/partials/cache/edge-ttl.mdx
+++ b/src/content/partials/cache/edge-ttl.mdx
@@ -12,4 +12,4 @@ By default, Cloudflare caches certain HTTP response codes with the following Ed
 | 302, 303         | 20m         |
 | 404, 410         | 3m          |
 
-All other status codes are not cached by default.
+All other status codes are not cached by default.
\ No newline at end of file
diff --git a/src/content/partials/cache/regional-tiered-cache.mdx b/src/content/partials/cache/regional-tiered-cache.mdx
index 84f6ff7440bd316..2da23da74a44c6f 100644
--- a/src/content/partials/cache/regional-tiered-cache.mdx
+++ b/src/content/partials/cache/regional-tiered-cache.mdx
@@ -4,4 +4,4 @@
 
 Regional Tiered Cache provides an additional layer of caching for customers who have a global traffic footprint and want to serve content faster by avoiding network latency when there is a cache `MISS` in a lower-tier, resulting in an upper-tier fetch in a data center located far away.
 
-Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
+Regional Tiered Cache instructs Cloudflare to check a regional hub data center near the lower tier before going to the upper tier that may be outside of the region.
\ No newline at end of file
diff --git a/src/content/partials/cache/smart-tiered-cache.mdx b/src/content/partials/cache/smart-tiered-cache.mdx
index 4cadd0acc82f9d2..f7feae4ba341a37 100644
--- a/src/content/partials/cache/smart-tiered-cache.mdx
+++ b/src/content/partials/cache/smart-tiered-cache.mdx
@@ -14,4 +14,4 @@ While Smart Tiered Cache selects one Upper Tier per origin, when using Load Bala
 
 #### Caveats
 
-You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
+You need to be careful when updating your origin IPs/DNS records while Smart Tiered Cache is enabled. Depending on the changes made, it may cause the existing assigned upper tiers to change, resulting in an increased `MISS` rate as cache is refilled in the new upper tiers. If the origin is switched to a network behind anycast, it will significantly reduce the effectiveness of Smart Tiered Cache unless you set a [cloud region hint](/cache/how-to/tiered-cache/#set-a-cloud-region-hint).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
index 38bc50594dca1b0..d395290564350e8 100644
--- a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
+++ b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
@@ -7,4 +8,4 @@
 [JavaScript detections](/bots/additional-configurations/javascript-detections/) are stored in the `cf_clearance` cookie.
 
 The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
index 3e1cf935e85c7fd..a4d3b6a8833f777 100644
--- a/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
+++ b/src/content/partials/cloudflare-challenges/create-challenge-page.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/).
+You can implement a Challenge Page to your website or application by creating a [WAF custom rule](/waf/custom-rules/). 
 
-Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/).
+Challenges are triggered by a rule in the [Web Application Firewall (WAF)](/waf/), [Bot Management](/bots/), or [Rate limiting](/waf/rate-limiting-rules/). 
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
index 6b6ee7d8e7a6954..ecd1e00cd105b61 100644
--- a/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/apex-proxying-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With [apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/), SaaS customers need to create an `A` record for their hostname that points to the IP prefix allocated to the SaaS provider's account.
@@ -10,6 +11,8 @@ example.com.  60  IN  A   192.0.2.1
 
 :::note
 
+
 For [BYOIP](/byoip/) customers, Cloudflare automatically enables the Apex Proxy Access feature on your BYOIP block, which allows Custom Hostnames to be activated via [Apex proxying](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/#apex-proxying) when Authoritative DNS for a customer's hostname targets any IP addresses in your BYOIP block.
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
index e442ded8479e150..cc1caa4a35ce4a3 100644
--- a/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
+++ b/src/content/partials/cloudflare-for-platforms/cname-target-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Most customers will have a `CNAME` target, which requires their customers to create a `CNAME` record similar to:
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
index b778c86451909e7..c72ac1bf7f7c156 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-api.mdx
@@ -1,10 +1,12 @@
 ---
 {}
+
 ---
 
 1. To create a custom hostname using the API, use the [Create Custom Hostname](/api/resources/custom_hostnames/methods/create/) endpoint.
-   - You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
 
-2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`. It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
+   * You can leave the `certificate_authority` parameter empty to set it to "default CA". With this option, Cloudflare checks the CAA records before requesting the certificates, which helps ensure the certificates can be issued from the CA.
+
+2. For the newly created custom hostname, the `POST` response may not return the DCV validation token `validation_records`.  It is recommended to make a second [`GET` command](/api/resources/custom_hostnames/methods/list/) (with a delay) to retrieve these details.
 
 The response contains the complete definition of the new custom hostname.
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
index 6c4d2491a949000..e70192ef25ae6e5 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx
@@ -1,12 +1,15 @@
 ---
 {}
+
 ---
 
 :::note[Default behavior]
 
+
 When you create a custom hostname:
 
-- If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
-- If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
+* If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
+* If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
+
 
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
index 0e5a5aff297fbc1..5734dd54f9b5277 100644
--- a/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/create-custom-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,10 +11,10 @@ import { DashButton } from "~/components";
 
 2. Select **Add Custom Hostname**.
 3. Add your customer's hostname `app.customer.com` and set the relevant options, including:
-   - The [minimum TLS version](/ssl/reference/protocols/).
-   - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
-   - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
-   - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
-   - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
-   - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
+    - The [minimum TLS version](/ssl/reference/protocols/).
+    - Defining whether you want to use a certificate provided by Cloudflare or [upload a custom certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/).
+    - Selecting the [certificate authority (CA)](/ssl/reference/certificate-authorities/) that will issue the certificate.
+    - Choosing the [validation method](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+    - Whether you want to **Enable wildcard**, which adds a `*.<custom-hostname>` SAN to the custom hostname certificate. For more details, refer to [Hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
+    - Choosing a value for [Custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
 4. Select **Add Custom Hostname**.
diff --git a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
index 2d204cd4201372c..8d09df2ede8e363 100644
--- a/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/custom-origin-server-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 A **custom origin server** lets you send traffic from one or more custom hostnames to somewhere besides your default proxy fallback, such as:
 
-- `soap.stores.com` goes to `origin1.com`
-- `towel.stores.com` goes to `origin2.com`
+* `soap.stores.com` goes to `origin1.com`
+* `towel.stores.com` goes to `origin2.com`
diff --git a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
index de24df450fd2452..dd9e0a9dbf02a89 100644
--- a/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
+++ b/src/content/partials/cloudflare-for-platforms/delete-custom-hostname-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
index b93ff80e6e1c8a8..f75a9b302889462 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-initial-setup-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you first [enable](/cloudflare-for-platforms/cloudflare-for-saas/start/enable/) Cloudflare for SaaS, you need to perform a few steps prior to creating any custom hostnames.
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
index cfac6c51968d0bb..d0487c9804e2705 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs } from "~/components"
 
 You need to perform the following steps for each custom hostname.
 
@@ -49,6 +50,8 @@ To create a custom hostname:
 
 :::note
 
+
 <Render file="issue-certs-preamble" product="cloudflare-for-platforms" />
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
index 76408b768cb0721..e69030364c61734 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-prereqs.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: planReqs
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 ## Before you begin
 
@@ -13,5 +14,5 @@ Before you start creating custom hostnames:
 3. Review the [Hostname prioritization guidelines](/ssl/reference/certificate-and-hostname-priority/#hostname-priority). Wildcard custom hostnames behave differently than an exact hostname match.
 4. (optional) Review the following documentation:
 
-- [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
-- [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
+* [API documentation](/fundamentals/api/) (if you have not worked with the Cloudflare API before).
+* [Certificate validation](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/).
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
index 35edd6886fe0424..82d0fca0621c733 100644
--- a/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/get-started-service-continuation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your customer is also using Cloudflare for their domain, they should keep their DNS record pointing to your SaaS provider in place for as long as they want to use your service.
diff --git a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
index ea5860cd4a1012d..93a809da7f02598 100644
--- a/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/http-dcv-situation.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 Specific (non-wildcard) custom hostnames can use [HTTP based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/http/) for certificate renewals, as long as:
 
-- The hostname is pointing to the SaaS provider.
-- The hostname's traffic is proxying through the Cloudflare network.
+* The hostname is pointing to the SaaS provider.
+* The hostname's traffic is proxying through the Cloudflare network.
 
 If your custom hostnames do not meet these requirements, use another validation method.
diff --git a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
index 7f9762bab2589d4..3bb70a1297de1a6 100644
--- a/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/issue-certs-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For each custom hostname, Cloudflare issues two certificates bundled in chains that maximize browser compatibility (unless you [upload custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/uploading-certificates/)).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
index 1e684db0ea49bf0..1d723d8f9826ad2 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-compatibility.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
 
-- [Caching](/cache/)
-- [Workers](/workers/)
-- [Rules](/rules/)
+* [Caching](/cache/)
+* [Workers](/workers/)
+* [Rules](/rules/)
 
 For a full list of compatible products and potential limitations, refer to [Product compatibility](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/).
diff --git a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
index 1e0fb535dd18bf6..343e065d9148425 100644
--- a/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
+++ b/src/content/partials/cloudflare-for-platforms/provider-guide-zone-hold.mdx
@@ -9,4 +9,4 @@ If your own Cloudflare zone is on the Enterprise plan, you have access to the [z
 
 To successfully activate the custom hostname on {props.providerName}, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to {props.providerName}, only the subfeature titled **Also prevent Subdomains** needs to be temporarily disabled.
 
-Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
+Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/regional-services.mdx b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
index c636d4b3c92b405..ee7ffcc908b6aac 100644
--- a/src/content/partials/cloudflare-for-platforms/regional-services.mdx
+++ b/src/content/partials/cloudflare-for-platforms/regional-services.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you have [regional services](/data-localization/regional-services/) set up for your custom hostnames, Cloudflare always uses the processing region associated with your DNS target record (instead of the processing region of any [custom origins](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/)).
diff --git a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
index 092651f810975a3..b4bb3909a232e68 100644
--- a/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
+++ b/src/content/partials/cloudflare-for-platforms/saas-customer-churn.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your SaaS domain is also a [domain using Cloudflare](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/), you can use your Cloudflare DNS to remove your domain from your SaaS provider.
diff --git a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
index 22b6eab5814cf27..d99a28f10dcf5ed 100644
--- a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
+++ b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
+Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
index f92949ab320cc09..b78a7aab90c363e 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-create-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you [create a new hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/issue-certificates/) and choose this validation method, you will see the following values after a few seconds:
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
index 0d895b1350d6147..7c01800301e8819 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare's network to your customers via their own custom or vanity domains.
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
index cc44b4ab26564b0..44c1c73202134c3 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-plan-limitation.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Only certain customers have access to this feature. For more details, see the [Plans page](/cloudflare-for-platforms/cloudflare-for-saas/plans/).
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
index 6d0ccd57fab6aec..86394cc77e6b615 100644
--- a/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
+++ b/src/content/partials/cloudflare-for-platforms/ssl-for-saas-validate-patch.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you would like to request an immediate recheck, [rather than wait for the next retry](/ssl/edge-certificates/changing-dcv-method/validation-backoff-schedule/), send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) with the same values as your initial `POST` request.
diff --git a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
index 04ae68397c36d17..39515e01e4e3b0a 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-dcv-situation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Wildcard custom hostnames require TXT-based validation. As the SaaS provider, you have two options for wildcard custom hostname certificate renewals:
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
index 50ebce2cda146e9..37093f6529689dd 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can access these tokens using the API with the [`GET` custom hostnames endpoint](/api/resources/custom_hostnames/methods/list/).
@@ -8,46 +9,46 @@ For example, here are two tokens highlighted in the API response for a **wildcar
 
 ```json title="Response" {11,12,13,14,15,16,17,18,19,20,21,22}
 {
-	"result": [
-		{
-			"id": "<HOSTNAME_ID>",
-			"hostname": "<HOSTNAME>",
-			"ssl": {
-				"id": "<CERTIFICATE_ID>",
-				"type": "dv",
-				"method": "txt",
-				"status": "pending_validation",
-				"validation_records": [
-					{
-						"status": "pending",
-						"txt_name": "_acme-challenge.<HOSTNAME>",
-						"txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
-					},
-					{
-						"status": "pending",
-						"txt_name": "_acme-challenge.<HOSTNAME>",
-						"txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
-					}
-				],
-				"settings": {
-					"min_tls_version": "1.0"
-				},
-				"bundle_method": "ubiquitous",
-				"wildcard": true,
-				"certificate_authority": "google"
-			},
-			"status": "pending",
-			"ownership_verification": {
-				"type": "txt",
-				"name": "_cf-custom-hostname.<HOSTNAME>",
-				"value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-			},
-			"ownership_verification_http": {
-				"http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
-				"http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
-			},
-			"created_at": "2022-10-06T19:35:33.143257Z"
-		}
-	]
+  "result": [
+    {
+      "id": "<HOSTNAME_ID>",
+      "hostname": "<HOSTNAME>",
+      "ssl": {
+        "id": "<CERTIFICATE_ID>",
+        "type": "dv",
+        "method": "txt",
+        "status": "pending_validation",
+        "validation_records": [
+          {
+            "status": "pending",
+            "txt_name": "_acme-challenge.<HOSTNAME>",
+            "txt_value": "gESljTB8fBT1mIuoEASU0qcK-oTd46baarnU_ZGjJIY"
+          },
+          {
+            "status": "pending",
+            "txt_name": "_acme-challenge.<HOSTNAME>",
+            "txt_value": "Pd8ViwX8KuA78kLbQHGmdEh4tQSpHBRxiNuJOYStEC0"
+          }
+        ],
+        "settings": {
+          "min_tls_version": "1.0"
+        },
+        "bundle_method": "ubiquitous",
+        "wildcard": true,
+        "certificate_authority": "google"
+      },
+      "status": "pending",
+      "ownership_verification": {
+        "type": "txt",
+        "name": "_cf-custom-hostname.<HOSTNAME>",
+        "value": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+      },
+      "ownership_verification_http": {
+        "http_url": "http://<HOSTNAME>/.well-known/cf-custom-hostname-challenge/fabdf93c-a4ce-4075-9f3f-c553a5f93bed",
+        "http_body": "ac4a9a9d-5469-44cb-9d76-cea7541c9ff8"
+      },
+      "created_at": "2022-10-06T19:35:33.143257Z"
+    }
+  ]
 }
 ```
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
index b813a3302da20ca..1b2e4694b7a24a3 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
index 88015281280b9e2..45dff2d23eddc00 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_post.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 Your customers should place these at their authoritative DNS provider under the `"_acme-challenge"` DNS label. Once these TXT records are in place, validation and certificate issuance will automatically complete.
 
 :::note
 
+
 These tokens are different than the hostname validation tokens.
 
+
 :::
diff --git a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
index b28cac12e8c8a6e..ff44799c97955f9 100644
--- a/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
+++ b/src/content/partials/cloudflare-for-platforms/txt-validation_preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 These tokens can be fetched through the API or the dashboard when the certificates are in a [pending validation](/ssl/reference/certificate-statuses/#new-certificates) state during custom hostname creation or during certificate renewals.
diff --git a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
index df573c1be7cd67a..62c3d6a6525d69f 100644
--- a/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
+++ b/src/content/partials/cloudflare-for-platforms/update-dcv-method.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your hostname is using another validation method, you will need to [update](/api/resources/custom_hostnames/methods/edit/) the `"method"` field in the SSL object to be `"txt"`.
diff --git a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
index a7d0a8eb53a6049..e0c4b7896a69330 100644
--- a/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
+++ b/src/content/partials/cloudflare-for-platforms/wildcard-hostname-reqs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To validate a certificate on a wildcard custom hostname, you should either set up [Delegated DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv/) or [TXT-based DCV](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt/).
diff --git a/src/content/partials/cloudflare-one/access/access-block-page.mdx b/src/content/partials/cloudflare-one/access/access-block-page.mdx
index 42cdfd762ed89a7..0330f3335eae871 100644
--- a/src/content/partials/cloudflare-one/access/access-block-page.mdx
+++ b/src/content/partials/cloudflare-one/access/access-block-page.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 **Custom block pages**: Choose what users will see when they are denied access to the application.
 
-- **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
-- **Redirect URL**: Redirect to the specified website.
-- **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
+* **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
+* **Redirect URL**: Redirect to the specified website.
+* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.
diff --git a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
index ed3f8e126327b44..8c24f29e8151dc8 100644
--- a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
+++ b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx
@@ -11,15 +11,14 @@ params:
 
 4. In **Certificate content**, paste the contents of your root CA.
 
-   If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
+	If the client certificate is directly signed by the root CA, you only need to upload the root. If the client certificate is signed by an intermediate certificate, you must upload the entire CA chain (intermediate and root). For example:
+	```txt
+	-----BEGIN CERTIFICATE-----
+	<intermediate.pem>
+	-----END CERTIFICATE-----
+	-----BEGIN CERTIFICATE-----
+	<rootCA.pem>
+	-----END CERTIFICATE-----
+	```
 
-   ```txt
-   -----BEGIN CERTIFICATE-----
-   <intermediate.pem>
-   -----END CERTIFICATE-----
-   -----BEGIN CERTIFICATE-----
-   <rootCA.pem>
-   -----END CERTIFICATE-----
-   ```
-
-   { props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
+	{ props.product === "access" && (<> Do not include any SSL/TLS server certificates; Access only uses the CA chain to verify the connection between the user's device and Cloudflare. </>)}
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/add-target.mdx b/src/content/partials/cloudflare-one/access/add-target.mdx
index e96d8060689cd6f..744e5212117cbde 100644
--- a/src/content/partials/cloudflare-one/access/add-target.mdx
+++ b/src/content/partials/cloudflare-one/access/add-target.mdx
@@ -3,22 +3,15 @@ params:
   - protocol
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	Details,
-	APIRequest,
-	GlossaryTooltip,
-} from "~/components";
+import { Tabs, TabItem, Render, Details, APIRequest, GlossaryTooltip } from "~/components";
 
 A target represents a single resource in your infrastructure (such as a server, Kubernetes cluster, database, or container) that users will connect to through Cloudflare.
 
 {
-props.protocol === "rdp" ? (
-<p> Create a target for each Windows machine that requires RDP access.
+  props.protocol === "rdp" ? (
+		<p> Create a target for each Windows machine that requires RDP access.
 To create a new target:</p>) :
-(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
+	(<p>Targets are protocol-agnostic, meaning that you do not need to define a new target for each protocol that runs on the server. To create a new target: </p>)
 }
 
 <Tabs syncKey="dashPlusAPI">
@@ -93,4 +86,4 @@ The following example requires Cloudflare provider version `>=4.45.0`.
 </TabItem>
 </Tabs>
 
-Next, create an Access application to secure the target.
+Next, create an Access application to secure the target.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/app-launcher.mdx b/src/content/partials/cloudflare-one/access/app-launcher.mdx
index b4f2bad751637b9..7e555517f94da72 100644
--- a/src/content/partials/cloudflare-one/access/app-launcher.mdx
+++ b/src/content/partials/cloudflare-one/access/app-launcher.mdx
@@ -54,8 +54,8 @@ To show an Access application in the App Launcher:
 
 6.  In **Application domains**, choose a domain to use for the App Launcher link.
 
-7.  (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
+7. (Optional) In **Tags**, add [custom tags](/cloudflare-one/reusable-components/tags/) so that users can more easily find the application in their App Launcher.
 
 ## Customize App Launcher appearance
 
-To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
+To customize the App Launcher with your own branding, messages, and links, refer to the [Custom pages documentation](/cloudflare-one/reusable-components/custom-pages/app-launcher-customization/).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx
index f34af47cbd7d9e0..5090f69c89745fd 100644
--- a/src/content/partials/cloudflare-one/access/bookmarks.mdx
+++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With Cloudflare One, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
@@ -55,4 +56,4 @@ If you attempt to assign a policy that uses an unsupported feature, the dashboar
 
 :::tip[Device posture policies]
 To show bookmarks only to users on managed devices, assign a policy that requires device posture checks (such as [Require Gateway](/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway/)). The bookmark will only appear in the App Launcher for users whose devices satisfy the posture requirements.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/create-service-token.mdx b/src/content/partials/cloudflare-one/access/create-service-token.mdx
index 1fa69e143298c53..048dfc0204abc20 100644
--- a/src/content/partials/cloudflare-one/access/create-service-token.mdx
+++ b/src/content/partials/cloudflare-one/access/create-service-token.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Tabs, TabItem, Details, APIRequest } from "~/components";
+import { Tabs, TabItem, Details, APIRequest } from '~/components';
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
index 5eafbf7d586642f..ad31a3a9469c5c2 100644
--- a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx
@@ -4,7 +4,7 @@ params:
   - supportgroups?
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Identity providers**.
 
@@ -14,12 +14,12 @@ import { Markdown } from "~/components";
 
 4. (Optional) Configure the following settings:
 
-- **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
-- **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
-- **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
-  - _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
-  - _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
-  - _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
+* **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/).
+* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
+* **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
+	- _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/team-and-resources/users/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client [device profiles](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/); Access will read the user's updated identity when they reauthenticate.
+	- _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [Cloudflare One Client session policies](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions/). Access will read the user's updated group membership when they reauthenticate.
+	- _No action_: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
 
 5. Select **Regenerate Secret**. Copy the **SCIM Endpoint** and **SCIM Secret**. You will need to enter these values into {props.idp}.
 
diff --git a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
index 4b7ad4e06edeccf..7c3cd7116b2f389 100644
--- a/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
+++ b/src/content/partials/cloudflare-one/access/entra-id-terraform.mdx
@@ -2,6 +2,7 @@
 {}
 ---
 
+
 ```tf
 resource "cloudflare_zero_trust_access_identity_provider" "microsoft_entra_id" {
 	account_id = var.cloudflare_account_id
diff --git a/src/content/partials/cloudflare-one/access/idp-integration.mdx b/src/content/partials/cloudflare-one/access/idp-integration.mdx
index 183354135c18212..d72214326c20f10 100644
--- a/src/content/partials/cloudflare-one/access/idp-integration.mdx
+++ b/src/content/partials/cloudflare-one/access/idp-integration.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, Tabs, TabItem } from "~/components";
+import {Render, Tabs, TabItem} from "~/components"
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -33,4 +33,4 @@ import { Render, Tabs, TabItem } from "~/components";
 
 		<Render file="access/idp-integration-note" product="cloudflare-one" params={{verb: "use" }} />
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
index d87a8bf152d7198..1963b122d60ac7e 100644
--- a/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
+++ b/src/content/partials/cloudflare-one/access/isolation-prereqs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Your browser must [allow third-party cookies](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/#allow-third-party-cookies-in-the-browser) on the application domain.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
index 6383efe24af3bc3..0c88cd0f401e32d 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/miro-sso.mdx
@@ -1,12 +1,13 @@
 ---
 inputParameters: uiLocation;;stepIntro
+
 ---
 
 1. In Miro, select your profile picture > **Settings** > <strong>{props.one}</strong>.
 2. Turn on **SSO/SAML**.
 3. Fill in the following fields:
-   - **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
-   - **Key x509 Certificate**: Public key from application configuration in Cloudflare One
+   * **SAML Sign-in URL**: SSO endpoint from application configuration in Cloudflare One
+   * **Key x509 Certificate**: Public key from application configuration in Cloudflare One
 4. In **Domain**, enter the domain you want to configure SSO for and select **Enter**.
 5. {props.two} an email address from that domain and select **send verification**.
 6. Once you receive a verification email, select the link in the email, then select **Save**. When the domain is successfully configured, the **VERIFY EMAIL** label next to the domain in the SSO/SAML configuration page will disappear.
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
index ef59bdce1e4d853..ae78bb666c48d5b 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/saas-sessions.mdx
@@ -4,4 +4,4 @@ params:
   - token
 ---
 
-{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
+{props.session} only control the front door to a SaaS app; Access does not control how long the user can stay in the SaaS app itself. For example, if the user logs out of the SaaS app and then comes back to it, a valid {props.token} allows them to re-authenticate without another login. The SaaS app issues its own authorization cookie that manages the user's session within the app.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
index 8d954a610155794..4c14a8d7ee82fc2 100644
--- a/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
+++ b/src/content/partials/cloudflare-one/access/saas-apps/salesforce-sso.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Enable Cloudflare Access as an identity provider on your Salesforce domain:
diff --git a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
index 9ef968d9aade80a..0aaa9e7f0ecc8c3 100644
--- a/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
+++ b/src/content/partials/cloudflare-one/access/scim-requires-login.mdx
@@ -4,4 +4,4 @@
 
 :::note
 New users must first [register the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/) or authenticate to an Access application before SCIM provisioning can begin.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
index eab1fcef7940eb3..3407640eddab5ff 100644
--- a/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
+++ b/src/content/partials/cloudflare-one/access/secure-tunnel-with-access.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To secure your origin, you must validate the [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/) issued by Cloudflare Access. Token validation ensures that any requests which bypass Cloudflare Access (for example, due to a network misconfiguration) are rejected.
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
index 58d1b77d29be1f9..759ae3cd92c090e 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/advanced-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - [**Cross-Origin Resource Sharing (CORS) settings**](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors/)
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
index 4e0f540d68c6438..abb27fd686a9a68 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/browser-rendering-policies.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::note
 Ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
index 6ff71b18c02ad6d..c7820c683885328 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/generic-public-app.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Access controls** > **Applications**.
 
@@ -12,29 +13,21 @@ import { Render } from "~/components";
 
 4. Select **Add public hostname**.
 
-5. <Render
-   	file="access/self-hosted-app/choose-domain"
-   	product="cloudflare-one"
-   />
+5. <Render file="access/self-hosted-app/choose-domain" product="cloudflare-one" />
 
 6. <Render file="access/add-access-policies" product="cloudflare-one" />
 
-7. <Render
-   	file="access/access-choose-idps"
-   	product="cloudflare-one"
-   	params={{ appType: "public" }}
-   />
+7. <Render file="access/access-choose-idps" product="cloudflare-one" params={{ appType: "public" }}/>
 
 8. <Render file="access/configure-independent-mfa" product="cloudflare-one" />
 
 9. <Render file="access/session-duration" product="cloudflare-one" />
 
 10. (Optional) Go to the **Additional settings** tab to customize the application experience:
-    - **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
-    - <Render file="access/access-block-page" product="cloudflare-one" />
-      <Render
-      	file="access/self-hosted-app/advanced-settings"
-      	product="cloudflare-one"
-      />
+
+	- **App Launcher customization**: Configure how this application appears to users in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/).
+	- <Render file="access/access-block-page" product="cloudflare-one" />
+	<Render file="access/self-hosted-app/advanced-settings" product="cloudflare-one" />
 
 11. Select **Create**.
+
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
index 427717a9cdab7ee..9c4a7b36eb13bf2 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx
@@ -1,14 +1,14 @@
 ---
 {}
----
 
+---
 When using Access self-hosted applications, the majority of Cloudflare products will be compatible with your application.
 
 However, the following products are not supported:
 
-- [Automatic Platform Optimization](/automatic-platform-optimization)
-- [Zaraz](/zaraz)
-- [Google tag gateway for advertisers](/google-tag-gateway)
+* [Automatic Platform Optimization](/automatic-platform-optimization)
+* [Zaraz](/zaraz)
+* [Google tag gateway for advertisers](/google-tag-gateway)
 
 You can disable Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain.
 
diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
index af5476bb1880972..1f73a0a13cfd29a 100644
--- a/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
+++ b/src/content/partials/cloudflare-one/access/self-hosted-app/ssh-sessions.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
+Cloudflare does not control the length of an active SSH, VNC, or RDP session. [Application session durations](/cloudflare-one/access-controls/access-settings/session-management/) determine the window in which a user can initiate a new connection or refresh an existing one.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/session-duration.mdx b/src/content/partials/cloudflare-one/access/session-duration.mdx
index 77ec2d4a99238d0..ac75de0b9aa9cfa 100644
--- a/src/content/partials/cloudflare-one/access/session-duration.mdx
+++ b/src/content/partials/cloudflare-one/access/session-duration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 In **Session Duration**, choose how often the user's [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token/) should expire.
diff --git a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
index 21858eabcee3e1e..c53f9130b03a46d 100644
--- a/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
+++ b/src/content/partials/cloudflare-one/access/short-lived-certs-intro.mdx
@@ -3,6 +3,6 @@ params:
   - intro
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
+{props.intro} traditional SSH keys with short-lived certificates issued to your users based on the token generated by their Access login. In traditional models, users generate an SSH key pair and administrators grant access to individual SSH servers by deploying their users' public keys to those servers. These SSH keys can remain unchanged on these servers for months or years. Cloudflare Access removes the burden of managing SSH keys, while also improving security by replacing long-lived SSH keys with ephemeral SSH certificates.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/access/tags.mdx b/src/content/partials/cloudflare-one/access/tags.mdx
index 77a811446a51a56..0afe99bdc346ec1 100644
--- a/src/content/partials/cloudflare-one/access/tags.mdx
+++ b/src/content/partials/cloudflare-one/access/tags.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can label an Access application with up to 25 custom tags. End users can then filter the applications in their [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) by their tags.
diff --git a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
index bfb96fb10ada920..90d56df296e1cc3 100644
--- a/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
+++ b/src/content/partials/cloudflare-one/access/verify-scim-provisioning.mdx
@@ -6,4 +6,4 @@ import { Render } from "~/components";
 
 To check if user identities were updated in Cloudflare One, view your [SCIM provisioning logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/).
 
-<Render file="access/scim-requires-login" product="cloudflare-one" />
+<Render file="access/scim-requires-login" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/aws-resolver.mdx b/src/content/partials/cloudflare-one/aws-resolver.mdx
index 9c47b138f5d989e..9a9d914decd40c5 100644
--- a/src/content/partials/cloudflare-one/aws-resolver.mdx
+++ b/src/content/partials/cloudflare-one/aws-resolver.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 Avoid configuring your [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) or [Resolver Policy](/cloudflare-one/traffic-policies/resolver-policies/) to direct all `*.amazonaws.com` DNS resolution via AWS Route 53 Resolver.
 
 Some AWS endpoints (such as `ssm.us-east-1.amazonaws.com`) are public AWS endpoints that are not resolvable via internal VPC resolution. This can break AWS Console features for users on the Cloudflare One Client.
 
-Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
+Only route specific Route 53 zones, or VPC Endpoints (such as `vpce.amazonaws.com`), through the internal VPC resolver.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
index ddceb27b9e24102..e908569bbffc1cf 100644
--- a/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
+++ b/src/content/partials/cloudflare-one/casb/casb-dlp-integrations.mdx
@@ -12,3 +12,4 @@
 - [Microsoft 365 Copilot](/cloudflare-one/integrations/cloud-and-saas/microsoft-365/m365-copilot/)
 - [OpenAI](/cloudflare-one/integrations/cloud-and-saas/openai/)
 - [Anthropic](/cloudflare-one/integrations/cloud-and-saas/anthropic/)
+
diff --git a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
index e478a5a5da68b5d..aada7498182b020 100644
--- a/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
+++ b/src/content/partials/cloudflare-one/casb/microsoft/m365-copilot-findings.mdx
@@ -8,4 +8,4 @@ Detect DLP matches in content used and shared within Microsoft's artificial inte
 | --------------------------------------------------------- | -------------------------------------- | -------- |
 | Microsoft: Copilot Referenced File with DLP Profile match | `fa7b06bd-cf63-41fc-9afa-a20598f7a52d` | High     |
 | Microsoft: Copilot AI Response with DLP Profile match     | `176b9299-0cee-4bbb-9c59-b18611228454` | High     |
-| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
+| Microsoft: Copilot User Prompt with DLP Profile match     | `1c5f1cdf-3e08-4a83-baf9-fc8e123877ab` | High     |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/choose-team-name.mdx b/src/content/partials/cloudflare-one/choose-team-name.mdx
index 4d29a981f28db0a..a8d57921a2efb06 100644
--- a/src/content/partials/cloudflare-one/choose-team-name.mdx
+++ b/src/content/partials/cloudflare-one/choose-team-name.mdx
@@ -2,6 +2,7 @@ import { GlossaryTooltip } from "~/components";
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
 
+
 2. On the onboarding screen, choose a <GlossaryTooltip term="team name">team name</GlossaryTooltip>. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry.
 
    You can find your team name in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Settings**.
diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
index 65c136e3d2c2438..fe7557d47652954 100644
--- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**.
-2. Turn on **Allow users to open a remote browser without the device client**.
+2. Turn on **Allow users to open a remote browser without the device client**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
index 69056d8ee6f20d8..7323f05d09189c0 100644
--- a/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
+++ b/src/content/partials/cloudflare-one/dex/notifications-intro.mdx
@@ -1 +1 @@
-Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
+Administrators can receive alerts when Cloudflare detects connectivity issues with the Cloudflare One Client or degraded application performance. Notifications can be delivered via email, webhook, and third-party services.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
index 8305079a6f89537..65a8f00486b5bc1 100644
--- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
+++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx
@@ -16,7 +16,7 @@ To capture data from a remote device:
      :::note
      **Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test.
      :::
-     {props.bestPractice}
+		 {props.bestPractice}
 4. Select **Run diagnostics**.
 
 DEX will now send capture requests to the configured devices. If the Cloudflare One Client is disconnected, the capture will time out after 10 minutes.
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
index fea35b13ae26ba6..83843ecfc58460f 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -21,8 +22,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -32,4 +34,4 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 
 12. Review your settings and select **Submit**.
 
-13. Select **Done**.
+13. Select **Done**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
index d4376f9c0f71649..ca5f0f65140cc17 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -21,8 +22,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 9. Select **Next**.
 
@@ -41,8 +43,9 @@ To create <GlossaryTooltip term="Quarantine policies">quarantine policies</Gloss
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
-    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
+    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
 18. Select **Next**.
 
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
index b2310b379b92a16..a2bfdd54a9efbbb 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/m365-use-case-configure-quarantine-notifications.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To configure quarantine notifications:
diff --git a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
index 01fe2f78cef538f..8e7f70186f96377 100644
--- a/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
+++ b/src/content/partials/cloudflare-one/email-security/deployment/set-up-mx-inline-step.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
+Now that you have completed the prerequisite steps, set up MX/Inline on the Cloudflare dashboard. Refer to [Set up MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) for the next steps.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
index d49c114294cdce6..3ff7a31c494d759 100644
--- a/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
+++ b/src/content/partials/cloudflare-one/email-security/dispositions-and-attributes.mdx
@@ -1,10 +1,10 @@
 - **Malicious**: Traffic associated with active threat campaigns. Malicious messages invoked multiple phishing verdict triggers and met thresholds for bad behavior.
-  - **Recommendation**: Block.
+    - **Recommendation**: Block.
 - **Spam**: Traffic associated with non-malicious, commercial campaigns.
-  - **Recommendation**: Route to existing Spam quarantine folder.
+    - **Recommendation**: Route to existing Spam quarantine folder.
 - **Bulk**: Traffic often associated with newsletters or marketing campaigns. Refer to [Graymail](https://en.wikipedia.org/wiki/Graymail_%28email%29) for more details.
-  - **Recommendation**: Monitor or tag.
+    - **Recommendation**: Monitor or tag.
 - **Suspicious**: Traffic associated with phishing campaigns (and is under further analysis by our automated systems).
-  - **Recommendation**: Research these messages internally to evaluate legitimacy.
+    - **Recommendation**: Research these messages internally to evaluate legitimacy.
 - **Spoof**: Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) or has mismatching `Envelope From` and `Header From` values.
-  - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
+    - **Recommendation**: Block after investigating (can be triggered by third-party mail services).
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
index 2edeb49998378d2..23143351441d03b 100644
--- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx
+++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx
@@ -2,17 +2,17 @@ When you configure your domain, the Cloudflare dashboard will display you the fo
 
 - **Domain**: Domain name. Refer to [Manage domains](/cloudflare-one/email-security/setup/manage-domains/) to learn how to add, filter, and delete domains.
 - **Configured method**: The deployment method you used to configure your domain. Depending on how you decided to configure Email security, the dashboard will display:
-  - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
-  - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
-  - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
-- **Status**: Status indicates the state of the configuration.
-  - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
-  - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
+    - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record.
+    - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare.
+    - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records).
+- **Status**: Status indicates the state of the configuration. 
+    - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly.
+    - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/).
 - **Service address**: This is the email address you will use to send a copy of your email.
 - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**.
 - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration:
-  1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
-  2. Locate your integration, select **Configure**, then select **Edit**.
-  3. Rename your integration, then select **Save**.
+    1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**.
+    2. Locate your integration, select **Configure**, then select **Edit**.
+    3. Rename your integration, then select **Save**. 
 - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured.
-- **Date added**: Date when the domain was added.
+- **Date added**: Date when the domain was added.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
index 5ea5ae3a83f02f1..33c6c6c71c6243a 100644
--- a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
+++ b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
+[Enable logs](/cloudflare-one/insights/logs/logpush/email-security-logs/) to send detection data to an endpoint of your choice.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
index 40c2ac71b068bec..49cd1e994f8a9f8 100644
--- a/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
+++ b/src/content/partials/cloudflare-one/email-security/onboarding-prerequisites.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up)
 - A [Zero Trust organization](/cloudflare-one/setup/#2-create-a-zero-trust-organization)
-- A domain to protect
+- A domain to protect
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
index b06118fd3a052a0..9a1bdd00693b775 100644
--- a/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
+++ b/src/content/partials/cloudflare-one/gateway/add-logo-image.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can include an external logo image to display on your custom block page. The block page resizes all images to 146x146 pixels. The URL must be valid and no longer than 2048 characters. Accepted file types include SVG, PNG, JPEG, and GIF.
diff --git a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
index bbbfc69bd059ecb..eec835ed93e198e 100644
--- a/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
+++ b/src/content/partials/cloudflare-one/gateway/debugging-policies.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies**.
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
index 046196f5fdbf1e2..ea9c95d04ff8dfe 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-cgnat-ips.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
 - **IPv4**: `100.80.0.0/16`
-- **IPv6**: `2606:4700:0cf1:4000::/64`
+- **IPv6**: `2606:4700:0cf1:4000::/64`
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
index 30af62814f0f3df..7aafd3c92aef6de 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx
@@ -4,13 +4,13 @@
 
 import { Render, Details, GlossaryTooltip } from "~/components";
 
-| On-ramp method                                                                             | Compatibility |
-| ------------------------------------------------------------------------------------------ | ------------- |
-| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) | ✅            |
-| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)               | ✅            |
-| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                             | ✅            |
-| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)                    | ✅            |
-| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                           | 🚧[^1]        |
+| On-ramp method                                                                                      | Compatibility |
+| --------------------------------------------------------------------------------------------------- | ------------- |
+| [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)                                            | ✅            |
+| [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/)                        | ✅            |
+| [Browser Isolation](/cloudflare-one/remote-browser-isolation/)                                      | ✅            |
+| [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) | ✅            |
+| [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/)                                              | 🚧[^1]        |
 
 [^1]: Not compatible with [ECMP routing](/cloudflare-wan/reference/traffic-steering/#equal-cost-multi-path-routing). For hostname-based routing to work, DNS queries and the resulting network traffic must reach Cloudflare over the same IPsec/GRE tunnel. <br/>
 
diff --git a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
index d1f4b0b967db2ba..a639506c0b67a66 100644
--- a/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-import { Render, GlossaryTooltip } from "~/components";
+import { Render, GlossaryTooltip } from "~/components"
 
 In your WARP [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel.  Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode):
 
 - **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
 - **Include mode**: Add Split Tunnel entries for the following IP addresses:
-  <Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
+	 	<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
index 0dbf6f82fe6cd31..07c7d64a068b757 100644
--- a/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
+++ b/src/content/partials/cloudflare-one/gateway/enable-tls-decryption.mdx
@@ -28,4 +28,4 @@ import { TabItem, Tabs } from "~/components";
 	}
 	```
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
index 91940427f366679..1615bd27d784c47 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/do-not-inspect-applications.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 | Selector    | Operator | Value            | Action         |
 | ----------- | -------- | ---------------- | -------------- |
-| Application | in       | _Do Not Inspect_ | Do Not Inspect |
+| Application | in       | *Do Not Inspect* | Do Not Inspect |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
index 24521accd2be220..a55001b8df4ac2c 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/egress-destination-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | Policy name                 | Selector       | Operator | Value            | Egress method                   |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
index 7584fb41e2afe19..4e453523e39abb5 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-allow.mdx
@@ -2,7 +2,7 @@
 inputParameters: selector;;value
 ---
 
-| Selector         | Operator      | Value                      | Logic | Action |
-| ---------------- | ------------- | -------------------------- | ----- | ------ |
-| {props.selector} | in            | <code>{props.value}</code> | And   | Allow  |
-| User Email       | matches regex | `.*@example.com`           |       |        |
+| Selector       | Operator      | Value            | Logic | Action |
+| -------------- | ------------- | ---------------- | ----- | ------ |
+| {props.selector} | in          | <code>{props.value}</code>   | And   | Allow  |
+| User Email     | matches regex | `.*@example.com` |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
index 77ace8200c34cdf..3b9f11e6ef1ca2b 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-block.mdx
@@ -4,4 +4,4 @@
 
 | Selector       | Operator | Value        | Action |
 | -------------- | -------- | ------------ | ------ |
-| Destination IP | in       | `10.0.0.0/8` | Block  |
+| Destination IP | in       | `10.0.0.0/8` | Block  |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
index 1ed03e7aa407058..293b0d23be0ff03 100644
--- a/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/policies/restrict-access-to-private-networks-dns.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-| Selector   | Operator      | Value                 | Logic | Action |
-| ---------- | ------------- | --------------------- | ----- | ------ |
-| Host       | in            | `wiki.internal.local` | And   | Allow  |
-| User Email | matches regex | `.*@example.com`      |       |        |
+| Selector       | Operator      | Value            | Logic | Action |
+| -------------- | ------------- | ---------------- | ----- | ------ |
+| Host           | in            | `wiki.internal.local`   | And   | Allow  |
+| User Email     | matches regex | `.*@example.com` |       |        |
diff --git a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
index a7c16e3c1d91ed9..b23ff64f7475ed7 100644
--- a/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
+++ b/src/content/partials/cloudflare-one/gateway/resolver-policies-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Resolver policies](/cloudflare-one/traffic-policies/resolver-policies/) provide similar functionality to Local Domain Fallback but occur in Cloudflare Gateway rather than on the local device. This option is recommended if you want more granular control over private DNS resolution. For example, you can ensure that all users in a specific geography use the private DNS server closest to them, ensure that specific conditions are met before resolving private DNS traffic, and apply [Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/) to private DNS traffic.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
index 5a6e380d089015d..64bfa9b16dc161a 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/category-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When using an Allow or Block action, you can optionally [block IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category) or [filter categories for `CNAME` records](/cloudflare-one/traffic-policies/domain-categories/#ignore-cname-domain-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
index a9531e7748ee785..9fb4a6872e220df 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/destination-country.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 The country that the request is destined for. Geolocation is determined from the target IP address. To specify a country, enter its [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                            | API example                                  |
-| ---------------------------------- | -------------------------------------------- |
+| UI name                            | API example              |
+| ---------------------------------- | ------------------------ |
 | Destination Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
index 335ee3ee0daeeca..00723a3e876eb59 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/device-posture.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With the Device Posture selector, admins can use signals from end-user devices to secure access to their internal and external resources. For example, a security admin can choose to limit all access to internal applications based on whether specific software is installed on a device and/or if the device or software are configured in a particular way.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
index 76e61efb71ed111..843d9ab425e324b 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/dns-resolver-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to DNS queries that arrived to your Gateway Resolver IP address aligned with a registered DNS location. For most Gateway customers, this is an IPv4 anycast address and policies created using this IPv4 address will apply to all DNS locations. However, each DNS location has a dedicated IPv6 address and some Gateway customers have been supplied with a dedicated IPv4 address — these both can be used to apply policies to specific registered DNS locations.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
index 526e97d2d3911fd..272bcfbd3b2eb4f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/doh-subdomain.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to match against DNS queries that arrive via DNS-over-HTTPS (DoH) destined for the DoH endpoint configured for each DNS location. For example, you can use a DNS location with a DoH endpoint of `abcdefg.cloudflare-gateway.com` by choosing the DoH Subdomain selector and inputting a value of `abcdefg`.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
index 4f8461929b76d11..05b18f7f521327c 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/oidc-claims.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-| UI name     | API example                                                    |
-| ----------- | -------------------------------------------------------------- |
+| UI name     | API example                                     |
+| ----------- | ----------------------------------------------- |
 | OIDC Claims | `any(identity.oidc_claims[*] == "\"department=engineering\"")` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
index 588a6399b52dfb6..e61b2a18a69b641 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/protocol.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The protocol used to send the packet.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
index 21ddf4a78052f03..8c09fe7735b8ada 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/query-record-type.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to choose the DNS resource record type that you would like to apply policies against. For example, you can match `A` records for a domain but not `MX` records.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
index aa08d0cb5aaa69a..16aa0c58ae0be8d 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/security-categories.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to match domains (and optionally, [IP addresses](/cloudflare-one/traffic-policies/domain-categories/#filter-traffic-by-resolved-ip-category)) belonging to specific [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories).
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
index cfc4e49bf7dcc14..f770cd8258d370f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-dns.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  | Evaluation phase      |
-| ----------------------------- | -------------------------------------------- | --------------------- |
+| UI name                       | API example              | Evaluation phase      |
+| ----------------------------- | ------------------------ | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
index 18542f3726a8e3e..bea70cb9423860e 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country-http.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  |
-| ----------------------------- | -------------------------------------------- |
+| UI name                       | API example              |
+| ----------------------------- | ------------------------ |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
index cfc4e49bf7dcc14..f770cd8258d370f 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-country.mdx
@@ -1,11 +1,12 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Geolocation is determined from the device's public IP address (typically assigned by the user's ISP). To specify a country, enter its [ISO 3166-1 Alpha-2 code](https://www.iso.org/obp/ui/#search/code/) in the **Value** field.
 
-| UI name                       | API example                                  | Evaluation phase      |
-| ----------------------------- | -------------------------------------------- | --------------------- |
+| UI name                       | API example              | Evaluation phase      |
+| ----------------------------- | ------------------------ | --------------------- |
 | Source Country IP Geolocation | <code>{props.one}.geo.country == "RU"</code> | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
index 2d8b06452ef3050..135f98ad365bdf1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-dns.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
index 2d8b06452ef3050..135f98ad365bdf1 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/source-ip-resolver.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use this selector to apply policies to the source IP address of DNS queries. For example, this could be the WAN IP address of the stub resolver used by your organization to send queries to Gateway.
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
index 593bd93476a3680..fee81be8110d5cb 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example value                           |
-| -------------- | ------------------------------------------- |
+| UI name    | API example value                           |
+| ---------- | ------------------------------------------- |
 | {props.UIname} | `identity.email == "user-name@company.com"` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
index 7d9c06487f8bece..f1b4aa99de07338 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-email.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                                          |
-| -------------- | ---------------------------------------------------- |
-| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.email == "contractors@company.com"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
index 458d7606be62bb1..719a72bec8720a8 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-ids.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                                    |
-| -------------- | ---------------------------------------------- |
-| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.id == "12jf495bhjd7893ml09o"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
index 7d5f097e94c6fa9..35fe7cc1e898bed 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-group-names.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                             |
-| -------------- | --------------------------------------- |
-| {props.UIname} | `identity.groups.name == "\"finance\""` |
+| UI name          | API example                                       |
+| ---------------- | ------------------------------------------------- |
+| {props.UIname} | `identity.groups.name == "\"finance\""` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
index 444ae920411c5ae..209566937c34f20 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/user-name.mdx
@@ -3,6 +3,6 @@ params:
   - UIname
 ---
 
-| UI name        | API example                    |
-| -------------- | ------------------------------ |
-| {props.UIname} | `identity.name == "user-name"` |
+| UI name   | API example                    |
+| --------- | ------------------------------ |
+| {props.UIname}  | `identity.name == "user-name"` |
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
index 253f211beb4c83e..bd7de5ffe296634 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-dns.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name           | API example                                                                                                    | Evaluation phase      |
-| ----------------- | -------------------------------------------------------------------------------------------------------------- | --------------------- |
-| User Email        | `identity.email == "user@example.com"`                                                                         | Before DNS resolution |
-| User Name         | `identity.name == "Test User"`                                                                                 | Before DNS resolution |
-| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   | Before DNS resolution |
-| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               | Before DNS resolution |
-| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       | Before DNS resolution |
-| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
+| UI name         | API example                                                                                | Evaluation phase      |
+| --------------- | ------------------------------------------------------------------------------------------ | --------------------- |
+| User Email      | `identity.email == "user@example.com"`                                                     | Before DNS resolution |
+| User Name       | `identity.name == "Test User"`                                                             | Before DNS resolution |
+| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               | Before DNS resolution |
+| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           | Before DNS resolution |
+| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  | Before DNS resolution |
+| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` | Before DNS resolution |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
index e18e640ce352a0d..e963ab12286d3ee 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users-http.mdx
@@ -6,11 +6,11 @@ import { Render } from "~/components";
 
 Use these selectors to match against identity attributes.
 
-| UI name           | API example                                                                                                    |
-| ----------------- | -------------------------------------------------------------------------------------------------------------- |
-| User Email        | `identity.email == "user@example.com"`                                                                         |
-| User Name         | `identity.name == "Test User"`                                                                                 |
-| User Group IDs    | `any(identity.groups[*].id in {"group_id"})`                                                                   |
-| User Group Names  | `any(identity.groups[*].name in {"group_name"})`                                                               |
-| User Group Emails | `any(identity.groups[*].email in {"group@example.com"})`                                                       |
-| SAML Attributes   | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
+| UI name         | API example                                                                                |
+| --------------- | ------------------------------------------------------------------------------------------ |
+| User Email      | `identity.email == "user@example.com"`                                                     |
+| User Name       | `identity.name == "Test User"`                                                             |
+| User Group IDs  | `any(identity.groups[*].id in {"group_id"})`                                               |
+| User Group Names| `any(identity.groups[*].name in {"group_name"})`                                           |
+| User Group Emails| `any(identity.groups[*].email in {"group@example.com"})`                                  |
+| SAML Attributes | `any(identity.saml_attributes["http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"] in {"Test User"})` |
diff --git a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
index 8e62f876db500b1..ce7d5d89de6d711 100644
--- a/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
+++ b/src/content/partials/cloudflare-one/gateway/selectors/users.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
 Identity-based selectors include:
 
-- **SAML Attributes**
-- **User Email**
-- **User Group Emails**
-- **User Group IDs**
-- **User Group Names**
-- **User Name**
+* **SAML Attributes**
+* **User Email**
+* **User Group Emails**
+* **User Group IDs**
+* **User Group Names**
+* **User Name**
 
 To use identity-based selectors, enable **Traffic and DNS mode** in the Cloudflare One Client and enroll your user in your organization. For more information, refer to [Identity-based policies](/cloudflare-one/traffic-policies/identity-selectors/).
diff --git a/src/content/partials/cloudflare-one/gateway/value.mdx b/src/content/partials/cloudflare-one/gateway/value.mdx
index 8ba2eb6529409da..a438bb02fbddee1 100644
--- a/src/content/partials/cloudflare-one/gateway/value.mdx
+++ b/src/content/partials/cloudflare-one/gateway/value.mdx
@@ -17,8 +17,8 @@ Regular expressions are evaluated using Rust. The Rust implementation is slightl
 
 If you want to match multiple values, you can use the pipe symbol (`|`) as an OR operator. You do not need to use an escape character (`\`) before the pipe symbol. For example, the following expression evaluates to true when the {props.selectordescription} matches either <code>{props.valueOne}</code> or <code>{props.valueTwo}</code>:
 
-| Selector         | Operator         | Value                                               |
-| ---------------- | ---------------- | --------------------------------------------------- |
+| Selector    | Operator        | Value          |
+| ----------- | --------------- | -------------- |
 | {props.selector} | {props.operator} | <code>{props.valueOne}&#124;{props.valueTwo}</code> |
 
 In addition to regular expressions, you can use [logical operators](#logical-operators) to match multiple values.
diff --git a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
index c8d77f235da0dee..d14d28f9b8b9303 100644
--- a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
+++ b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Posture checks** > **Service provider checks**.
 2. Select **Add a check**.
diff --git a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
index 251164d2d766ee4..38dd06ceea2f117 100644
--- a/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
+++ b/src/content/partials/cloudflare-one/posture/prereqs-warp-is-deployed.mdx
@@ -1,5 +1,6 @@
 ---
 inputParameters: param1
+
 ---
 
 Cloudflare One Client is [deployed](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) on the device. For a list of supported modes and operating systems, refer to <a href={props.link}>{props.name}</a>.
diff --git a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
index 5927c815e59262a..41541ce5b9dac6d 100644
--- a/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
+++ b/src/content/partials/cloudflare-one/ssh/decrypt-ssh-log.mdx
@@ -4,8 +4,8 @@
 
 To decrypt the log, follow the instructions in the [SSH Logging CLI repository](https://github.com/cloudflare/ssh-log-cli/). In the following example, `sshkey` is the private key that matches the public key uploaded to Cloudflare.
 
-```sh
-./ssh-log-cli decrypt -i sshlog -k sshkey
-```
+   ```sh
+   ./ssh-log-cli decrypt -i sshlog -k sshkey
+   ```
 
-This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
+   This command outputs a `sshlog-decrypted.zip` file with the decrypted logs.
diff --git a/src/content/partials/cloudflare-one/ssh/public-key.mdx b/src/content/partials/cloudflare-one/ssh/public-key.mdx
index 67338a0b2b7b927..6cdb18030f52db0 100644
--- a/src/content/partials/cloudflare-one/ssh/public-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/public-key.mdx
@@ -16,9 +16,9 @@
 
 3. In the `ca.pub` file, paste the public key without any modifications.
 
-   ```txt title="ca.pub"
-   ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
-   ```
+	```txt title="ca.pub"
+	ecdsa-sha2-nistp256 <redacted> open-ssh-ca@cloudflareaccess.org
+	```
 
    The `ca.pub` file can hold multiple keys, listed one per line. Empty lines and comments starting with `#` are also allowed.
 
diff --git a/src/content/partials/cloudflare-one/ssh/restart-server.mdx b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
index ea942613d292e20..4e91c37de63e2e5 100644
--- a/src/content/partials/cloudflare-one/ssh/restart-server.mdx
+++ b/src/content/partials/cloudflare-one/ssh/restart-server.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Tabs, TabItem, Render } from "~/components";
+import { Tabs, TabItem, Render } from "~/components"
 
 Once you have modified your `sshd` configuration, reload the SSH service on the remote machine for the changes to take effect.
 
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
index edd0dc07d1ee8a5..5117c9c548cc54c 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 :::note
 
 Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
index 667604bc9b6a4ef..15141e1a16ba29f 100644
--- a/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
+++ b/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx
@@ -43,4 +43,4 @@ import { Render, Details, APIRequest, Tabs, TabItem } from "~/components";
 4. Copy the `public_key` value returned in the response.
 
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
index fbcdf62609e8975..35834d8c2063b23 100644
--- a/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
+++ b/src/content/partials/cloudflare-one/ssh/upload-ssh-key.mdx
@@ -3,7 +3,7 @@ params:
   - note
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 To log SSH commands, you will need to generate an HPKE key pair and upload the public key to Cloudflare.
 
diff --git a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
index be9833c0d225c55..2492eb7979d2109 100644
--- a/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/cloudflare-resources.mdx
@@ -14,161 +14,161 @@ The following configuration will modify settings in your Cloudflare account.
 
 2.  Add the following resources to `Cloudflare-config.tf`:
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            ```tf
-    
-            # Creates a new remotely-managed tunnel for the GCP VM.
-            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-            	account_id    = var.cloudflare_account_id
-            	name          = "Terraform GCP tunnel"
-            	config_src    = "cloudflare"
-            }
-    
-            # Reads the token used to run the tunnel on the server.
-            data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
-            	account_id 	= var.cloudflare_account_id
-            	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            }
-    
-            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-            resource "cloudflare_dns_record" "http_app" {
-            	zone_id = var.cloudflare_zone_id
-            	name    = "http_app"
-            	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
-            	type    = "CNAME"
-            	ttl     = 1
-            	proxied = true
-            }
-    
-            # Configures tunnel with a published application for clientless access.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-            	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            	account_id = var.cloudflare_account_id
-            	config     = {
-            		ingress 	= [
-            			{
-            				hostname = "http_app.${var.cloudflare_zone}"
-            				service  = "http://httpbin:80"
-            			},
-            			{
-            				service  = "http_status:404"
-            			}
-            		]
-            	}
-            }
-    
-            # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
-            account_id         = var.cloudflare_account_id
-            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            network            = google_compute_instance.http_server.network_interface.0.network_ip
-            comment            = "Example tunnel route"
-            }
-    
-            # Creates a reusable Access policy.
-            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-            	account_id   = var.cloudflare_account_id
-            	name         = "Allow email addresses"
-            	decision     = "allow"
-            	include      = [
-            		{
-            			email = {
-            				email = var.cloudflare_email
-            			}
-            		},
-            		{
-            			email_domain = {
-            				domain = "@example.com"
-            			}
-            		}
-            	]
-            }
-    
-            # Creates an Access application to control who can connect to the public hostname.
-            resource "cloudflare_zero_trust_access_application" "http_app" {
-            	account_id       = var.cloudflare_account_id
-            	type             = "self_hosted"
-            	name             = "Access application for http_app.${var.cloudflare_zone}"
-            	domain           = "http_app.${var.cloudflare_zone}"
-            	policies = [
-            		{
-            			id = cloudflare_zero_trust_access_policy.allow_emails.id
-            			precedence = 1
-            		}
-            	]
-            }
-            ```
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            # Generates a 32-byte secret for the tunnel.
-            resource "random_bytes" "tunnel_secret" {
-            	byte_length = 32
-            }
-    
-            # Creates a new remotely-managed tunnel for the GCP VM.
-            resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
-            	account_id = var.cloudflare_account_id
-            	name       = "Terraform GCP tunnel"
-            	secret     = random_bytes.tunnel_secret.base64
-            }
-    
-            # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
-            resource "cloudflare_record" "http_app" {
-            	zone_id = var.cloudflare_zone_id
-            	name    = "http_app"
-            	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
-            	type    = "CNAME"
-            	proxied = true
-            }
-    
-            # Configures tunnel with a published application for clientless access.
-            resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
-            	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            	account_id = var.cloudflare_account_id
-            	config {
-            		ingress_rule {
-            			hostname = "${cloudflare_record.http_app.hostname}"
-            			service  = "http://httpbin:80"
-            		}
-            		ingress_rule {
-            			service  = "http_status:404"
-            		}
-            	}
-            }
-    
-            # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
-            resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
-            account_id         = var.cloudflare_account_id
-            tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
-            network            = google_compute_instance.http_server.network_interface.0.network_ip
-            comment            = "Example tunnel route"
-            }
-    
-            # Creates an Access application to control who can connect to the public hostname.
-            resource "cloudflare_zero_trust_access_application" "http_app" {
-            	account_id          = var.cloudflare_account_id
-            	name             = "Access application for http_app.${var.cloudflare_zone}"
-            	domain           = "http_app.${var.cloudflare_zone}"
-            }
-    
-            # Creates a (legacy) Access policy for the Access application.
-            resource "cloudflare_zero_trust_access_policy" "allow_emails" {
-            	application_id = cloudflare_zero_trust_access_application.http_app.id
-            	account_id        = var.cloudflare_account_id
-            	name           = "Example policy for http_app.${var.cloudflare_zone}"
-            	precedence     = "1"
-            	decision       = "allow"
-            	include {
-            		email = [var.cloudflare_email]
-            	}
-            }
-            ```
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        ```tf
+
+        # Creates a new remotely-managed tunnel for the GCP VM.
+        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+        	account_id    = var.cloudflare_account_id
+        	name          = "Terraform GCP tunnel"
+        	config_src    = "cloudflare"
+        }
+
+        # Reads the token used to run the tunnel on the server.
+        data "cloudflare_zero_trust_tunnel_cloudflared_token" "gcp_tunnel_token" {
+        	account_id 	= var.cloudflare_account_id
+        	tunnel_id 	= cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        }
+
+        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+        resource "cloudflare_dns_record" "http_app" {
+        	zone_id = var.cloudflare_zone_id
+        	name    = "http_app"
+        	content = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id}.cfargotunnel.com"
+        	type    = "CNAME"
+        	ttl     = 1
+        	proxied = true
+        }
+
+        # Configures tunnel with a published application for clientless access.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+        	tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        	account_id = var.cloudflare_account_id
+        	config     = {
+        		ingress 	= [
+        			{
+        				hostname = "http_app.${var.cloudflare_zone}"
+        				service  = "http://httpbin:80"
+        			},
+        			{
+        				service  = "http_status:404"
+        			}
+        		]
+        	}
+        }
+
+        # (Optional) Routes internal IP of GCP instance through the tunnel for private network access using WARP.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_route" "example_tunnel_route" {
+        account_id         = var.cloudflare_account_id
+        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        network            = google_compute_instance.http_server.network_interface.0.network_ip
+        comment            = "Example tunnel route"
+        }
+
+        # Creates a reusable Access policy.
+        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+        	account_id   = var.cloudflare_account_id
+        	name         = "Allow email addresses"
+        	decision     = "allow"
+        	include      = [
+        		{
+        			email = {
+        				email = var.cloudflare_email
+        			}
+        		},
+        		{
+        			email_domain = {
+        				domain = "@example.com"
+        			}
+        		}
+        	]
+        }
+
+        # Creates an Access application to control who can connect to the public hostname.
+        resource "cloudflare_zero_trust_access_application" "http_app" {
+        	account_id       = var.cloudflare_account_id
+        	type             = "self_hosted"
+        	name             = "Access application for http_app.${var.cloudflare_zone}"
+        	domain           = "http_app.${var.cloudflare_zone}"
+        	policies = [
+        		{
+        			id = cloudflare_zero_trust_access_policy.allow_emails.id
+        			precedence = 1
+        		}
+        	]
+        }
+        ```
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        # Generates a 32-byte secret for the tunnel.
+        resource "random_bytes" "tunnel_secret" {
+        	byte_length = 32
+        }
+
+        # Creates a new remotely-managed tunnel for the GCP VM.
+        resource "cloudflare_zero_trust_tunnel_cloudflared" "gcp_tunnel" {
+        	account_id = var.cloudflare_account_id
+        	name       = "Terraform GCP tunnel"
+        	secret     = random_bytes.tunnel_secret.base64
+        }
+
+        # Creates the CNAME record that routes http_app.${var.cloudflare_zone} to the tunnel.
+        resource "cloudflare_record" "http_app" {
+        	zone_id = var.cloudflare_zone_id
+        	name    = "http_app"
+        	content   = "${cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.cname}"
+        	type    = "CNAME"
+        	proxied = true
+        }
+
+        # Configures tunnel with a published application for clientless access.
+        resource "cloudflare_zero_trust_tunnel_cloudflared_config" "gcp_tunnel_config" {
+        	tunnel_id = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        	account_id = var.cloudflare_account_id
+        	config {
+        		ingress_rule {
+        			hostname = "${cloudflare_record.http_app.hostname}"
+        			service  = "http://httpbin:80"
+        		}
+        		ingress_rule {
+        			service  = "http_status:404"
+        		}
+        	}
+        }
+
+        # (Optional) Route internal IP of GCP instance through the tunnel for private network access using WARP.
+        resource "cloudflare_zero_trust_tunnel_route" "example_tunnel_route" {
+        account_id         = var.cloudflare_account_id
+        tunnel_id          = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.id
+        network            = google_compute_instance.http_server.network_interface.0.network_ip
+        comment            = "Example tunnel route"
+        }
+
+        # Creates an Access application to control who can connect to the public hostname.
+        resource "cloudflare_zero_trust_access_application" "http_app" {
+        	account_id          = var.cloudflare_account_id
+        	name             = "Access application for http_app.${var.cloudflare_zone}"
+        	domain           = "http_app.${var.cloudflare_zone}"
+        }
+
+        # Creates a (legacy) Access policy for the Access application.
+        resource "cloudflare_zero_trust_access_policy" "allow_emails" {
+        	application_id = cloudflare_zero_trust_access_application.http_app.id
+        	account_id        = var.cloudflare_account_id
+        	name           = "Example policy for http_app.${var.cloudflare_zone}"
+        	precedence     = "1"
+        	decision       = "allow"
+        	include {
+        		email = [var.cloudflare_email]
+        	}
+        }
+        ```
+        </TabItem>
+        </Tabs>
 
 To learn more about these resources, refer to the [Cloudflare provider documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
diff --git a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
index e21650fa17456a6..4eca7f0c1b7957c 100644
--- a/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
+++ b/src/content/partials/cloudflare-one/terraform/gcp-resources.mdx
@@ -14,88 +14,88 @@ The following configuration defines the specifications for the GCP virtual machi
 
 2.  Add the following content to `GCP-config.tf`:
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            ```tf
-            # OS the server will use
-            data "google_compute_image" "image" {
-            	family  = "ubuntu-2204-lts"
-            	project = "ubuntu-os-cloud"
-            }
-    
-            # GCP Instance resource
-            resource "google_compute_instance" "http_server" {
-            	name         = "test"
-            	machine_type = var.machine_type
-            	zone         = var.zone
-            	tags         = []
-            	boot_disk {
-            		initialize_params {
-            			image = data.google_compute_image.image.self_link
-            		}
-            	}
-    
-            	network_interface {
-            		network = "default"
-            		access_config {
-            			//Ephemeral IP
-            		}
-            	}
-            	// Optional config to make instance ephemeral
-            /*  scheduling {
-            		preemptible       = true
-            		automatic_restart = false
-            	} */
-    
-            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-            		{
-            			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
-            		})
-            }
-            ```
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            # OS the server will use
-            data "google_compute_image" "image" {
-            	family  = "ubuntu-2204-lts"
-            	project = "ubuntu-os-cloud"
-            }
-    
-            # GCP Instance resource
-            resource "google_compute_instance" "http_server" {
-            	name         = "test"
-            	machine_type = var.machine_type
-            	zone         = var.zone
-            	tags         = []
-            	boot_disk {
-            		initialize_params {
-            			image = data.google_compute_image.image.self_link
-            		}
-            	}
-    
-            	network_interface {
-            		network = "default"
-            		access_config {
-            			//Ephemeral IP
-            		}
-            	}
-            	// Optional config to make instance ephemeral
-            /*  scheduling {
-            		preemptible       = true
-            		automatic_restart = false
-            	} */
-    
-            	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
-            	metadata_startup_script = templatefile("./install-tunnel.tftpl",
-            		{
-            			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
-            		})
-            }
-            ```
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        ```tf
+        # OS the server will use
+        data "google_compute_image" "image" {
+        	family  = "ubuntu-2204-lts"
+        	project = "ubuntu-os-cloud"
+        }
+
+        # GCP Instance resource
+        resource "google_compute_instance" "http_server" {
+        	name         = "test"
+        	machine_type = var.machine_type
+        	zone         = var.zone
+        	tags         = []
+        	boot_disk {
+        		initialize_params {
+        			image = data.google_compute_image.image.self_link
+        		}
+        	}
+
+        	network_interface {
+        		network = "default"
+        		access_config {
+        			//Ephemeral IP
+        		}
+        	}
+        	// Optional config to make instance ephemeral
+        /*  scheduling {
+        		preemptible       = true
+        		automatic_restart = false
+        	} */
+
+        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+        		{
+        			tunnel_token = data.cloudflare_zero_trust_tunnel_cloudflared_token.gcp_tunnel_token.token
+        		})
+        }
+        ```
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        # OS the server will use
+        data "google_compute_image" "image" {
+        	family  = "ubuntu-2204-lts"
+        	project = "ubuntu-os-cloud"
+        }
+
+        # GCP Instance resource
+        resource "google_compute_instance" "http_server" {
+        	name         = "test"
+        	machine_type = var.machine_type
+        	zone         = var.zone
+        	tags         = []
+        	boot_disk {
+        		initialize_params {
+        			image = data.google_compute_image.image.self_link
+        		}
+        	}
+
+        	network_interface {
+        		network = "default"
+        		access_config {
+        			//Ephemeral IP
+        		}
+        	}
+        	// Optional config to make instance ephemeral
+        /*  scheduling {
+        		preemptible       = true
+        		automatic_restart = false
+        	} */
+
+        	// Pass the tunnel token to the GCP server so that the server can install and run the tunnel upon startup.
+        	metadata_startup_script = templatefile("./install-tunnel.tftpl",
+        		{
+        			tunnel_token = cloudflare_zero_trust_tunnel_cloudflared.gcp_tunnel.tunnel_token
+        		})
+        }
+        ```
+        </TabItem>
+        </Tabs>
diff --git a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
index 5afae47ec52d2f1..cda294b702f2e15 100644
--- a/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers-v5.mdx
@@ -25,4 +25,4 @@ provider "google" {
 }
 provider "random" {
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/terraform/providers.mdx b/src/content/partials/cloudflare-one/terraform/providers.mdx
index 962ef714f4ec1c3..113455091a647e1 100644
--- a/src/content/partials/cloudflare-one/terraform/providers.mdx
+++ b/src/content/partials/cloudflare-one/terraform/providers.mdx
@@ -14,41 +14,41 @@ You will need to declare the [providers](https://registry.terraform.io/browse/pr
 
 2.  Add the following providers to `providers.tf`. The `random` provider is used to generate a tunnel secret.
 
-    <Tabs syncKey="dashPlusAPI">
-            <TabItem label="Terraform (v5)">
-    
-            <Render file="terraform/providers-v5" product="cloudflare-one" />
-    
-            </TabItem>
-            <TabItem label="Terraform (v4)">
-    
-            ```tf
-            terraform {
-            	required_providers {
-            		cloudflare = {
-            			source = "cloudflare/cloudflare"
-            			version = ">= 4.40.0, < 5.0.0"
-            		}
-            		google = {
-            			source = "hashicorp/google"
-            		}
-            		random = {
-            			source = "hashicorp/random"
-            		}
-            	}
-            	required_version = ">= 1.2"
-            }
-    
-            # Providers
-            provider "cloudflare" {
-            	api_token    = var.cloudflare_token
-            }
-            provider "google" {
-            	project    = var.gcp_project_id
-            }
-            provider "random" {
-            }
-            ```
-    
-            </TabItem>
-            </Tabs>
+        <Tabs syncKey="dashPlusAPI">
+        <TabItem label="Terraform (v5)">
+
+        <Render file="terraform/providers-v5" product="cloudflare-one" />
+
+        </TabItem>
+        <TabItem label="Terraform (v4)">
+
+        ```tf
+        terraform {
+        	required_providers {
+        		cloudflare = {
+        			source = "cloudflare/cloudflare"
+        			version = ">= 4.40.0, < 5.0.0"
+        		}
+        		google = {
+        			source = "hashicorp/google"
+        		}
+        		random = {
+        			source = "hashicorp/random"
+        		}
+        	}
+        	required_version = ">= 1.2"
+        }
+
+        # Providers
+        provider "cloudflare" {
+        	api_token    = var.cloudflare_token
+        }
+        provider "google" {
+        	project    = var.gcp_project_id
+        }
+        provider "random" {
+        }
+        ```
+
+        </TabItem>
+        </Tabs>
diff --git a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
index 6abc149ee79e338..a68729e1c588fba 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/browser-isolation.mdx
@@ -3,37 +3,31 @@ Review common troubleshooting scenarios for Cloudflare Browser Isolation.
 ## Connectivity and sessions
 
 ### No Browsers Available
-
 If you encounter a `No Browsers Available` alert, please file feedback via the Cloudflare One Client. This error typically indicates a temporary capacity issue in the data center or a connectivity problem between your client and the remote browser.
 
 ### Maximum Sessions Reached
-
 This alert appears if your device attempts to establish more than two concurrent remote browser instances. A browser isolation session is shared across all tabs and windows within the same browser (for example, all Chrome tabs share one session). You can use two different browsers (such as Chrome and Firefox) concurrently, but opening a third will trigger this alert. To release a session, close all tabs and windows in one of your local browsers.
 
 ## Rendering and performance
 
 ### WebGL Rendering Error
-
 Cloudflare Browser Isolation uses Network Vector Rendering (NVR), which does not support WebGL (Web Graphics Library) in all environments. If a website requires WebGL and your device lacks the necessary hardware resources in the virtualized environment, you may see a rendering error.
 
 To resolve this, try enabling software rasterization in your browser:
-
 1. Go to `chrome://flags/#override-software-rendering-list`.
-2. Set **Override software rendering list** to _Enabled_.
+2. Set **Override software rendering list** to *Enabled*.
 3. Select **Relaunch**.
 
 ### Blank screen on Windows
-
 On Windows devices, Clientless Web Isolation may load with a blank screen if there is a conflict between browser mDNS settings and Windows IGMP configuration.
 
-| IGMPLevel    | WebRTC Anonymization | Result          |
-| ------------ | -------------------- | --------------- |
-| 0 (disabled) | Enabled / Default    | ❌ Blank screen |
-| 0 (disabled) | Disabled             | ✅ Works        |
-| 2 (enabled)  | Enabled / Default    | ✅ Works        |
+| IGMPLevel | WebRTC Anonymization | Result |
+| --------- | -------------------- | ------ |
+| 0 (disabled) | Enabled / Default | ❌ Blank screen |
+| 0 (disabled) | Disabled | ✅ Works |
+| 2 (enabled) | Enabled / Default | ✅ Works |
 
 To fix this, either disable **Anonymize local IPs exposed by WebRTC** in your browser flags or ensure `IGMPLevel` is enabled (set to `2`) in your Windows network settings.
 
 ### Rendering issues (CSS/Images)
-
 If a website displays incorrectly (for example, broken CSS or missing images), it may indicate that the remote browser is unable to fetch specific resources from the origin server. Check your [Gateway HTTP logs](/cloudflare-one/traffic-policies/troubleshooting/) for any blocked subresources that might be required by the page.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
index ea6662dd6b23a61..812e31a9e577986 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/casb.mdx
@@ -3,17 +3,13 @@ Use this guide to troubleshoot common issues with Cloud Access Security Broker (
 ## Security findings
 
 ### Findings not appearing
-
 If you do not see findings for an integrated application:
-
 - **Wait for scan**: Initial scans can take up to 24 hours depending on the size of the application.
 - **Permissions**: Ensure the account used to integrate the application has the necessary administrative permissions.
 - **Enabled status**: Verify that the integration is enabled in the Zero Trust dashboard.
 
 ### False positives
-
 If CASB flags a configuration that is intended for your organization:
-
 1. Go to **CASB** &gt; **Findings**.
 2. Select the finding and choose **Dismiss**.
 3. Provide a reason for dismissal to help refine future scans.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
index b0b9af1de6363da..d9f76c11a762d23 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/dex.mdx
@@ -3,7 +3,6 @@ Review common troubleshooting scenarios for Digital Experience Monitoring (DEX).
 ## Data visibility
 
 ### No data displayed for certain users
-
 If you do not see DEX data for specific users in your organization, verify the following:
 
 - **Client version**: Ensure the users are running a version of the Cloudflare One Client that supports DEX.
@@ -11,13 +10,11 @@ If you do not see DEX data for specific users in your organization, verify the f
 - **Traffic routing**: DEX requires that traffic to Cloudflare's orchestration API is not blocked by local firewalls or SSL-inspecting proxies.
 
 ### Fleet status not updating
-
 The Fleet status dashboard can take several minutes to reflect changes in device connectivity. If a device remains in an incorrect state, try disconnecting and reconnecting the Cloudflare One Client to force a status update.
 
 ## Remote captures
 
 ### Remote capture fails to start
-
 Remote captures require the Cloudflare One Client to be connected and able to communicate with the Cloudflare control plane. If a capture fails to start:
 
 - Verify the device status in the Zero Trust dashboard.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
index 500c1dc89b9f0c0..77aac5be079b8ae 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx
@@ -4,51 +4,44 @@ Review common troubleshooting scenarios for Cloudflare Email Security.
 
 Email Security identifies threats using detections that result in a final disposition. You can inspect email headers to understand why a specific disposition was applied.
 
-| Attribute           | Description                                                                                                                                 |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list.                                                                                          |
-| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain.                                                                                          |
-| `NEW_DOMAIN_LINK`   | The email contains links to a newly registered domain.                                                                                      |
-| `ENCRYPTED`         | The email message is encrypted.                                                                                                             |
-| `BEC`               | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
+| Attribute | Description |
+| --------- | ----------- |
+| `CUSTOM_BLOCK_LIST` | Matches a value defined in your custom block list. |
+| `NEW_DOMAIN_SENDER` | The email was sent from a newly registered domain. |
+| `NEW_DOMAIN_LINK` | The email contains links to a newly registered domain. |
+| `ENCRYPTED` | The email message is encrypted. |
+| `BEC` | The sender address is in your [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). |
 
 ## Detections and reclassification
 
 ### Handle a false positive
-
-A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam.
+A false positive occurs when a legitimate email is incorrectly flagged as malicious or spam. 
 
 **Solution**:
-
 1. In the Email Security dashboard, go to **Investigation**.
 2. Find the email and select **Submit for reclassification**.
 3. Choose the correct disposition (for example, `Clean`).
 4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) list.
 
 ### Handle a false negative
-
 A false negative occurs when a malicious email is not detected by Email Security.
 
 **Solution**:
-
 1. Ensure the email actually passed through Email Security by checking for the `X-CFEmailSecurity-Disposition` header.
 2. Submit the email for reclassification in the dashboard. This is the preferred method for reporting missed detections.
 
 ## Authentication errors
 
 ### DMARC failures
-
 Email Security may mark an email as **SPAM** if it fails DMARC authentication and the sending domain has a `p=reject` or `p=quarantine` policy.
 
 **Solution**:
-
 - Ask the sender to fix their DMARC/SPF/DKIM records.
 - Configure an [Acceptable Sender](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) entry to suppress the failure for that specific sender.
 
 ## Delivery issues
 
 ### Emails are delayed or not arriving
-
 If emails are not being delivered or are arriving with significant latency:
 
 1. **Check MX records**: Ensure your [MX records](/cloudflare-one/email-security/setup/) are correctly configured and pointing to Cloudflare.
diff --git a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
index 9aa7ada94a6a62d..a5dd284025e9f77 100644
--- a/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
+++ b/src/content/partials/cloudflare-one/troubleshooting/gateway.mdx
@@ -3,11 +3,9 @@ This guide helps you troubleshoot common issues with Cloudflare Gateway policies
 ## Blocked websites and connectivity
 
 ### A website is blocked incorrectly
-
 If you believe a domain has been incorrectly blocked by Gateway's security categories or threat intelligence, you can use the [Cloudflare Radar categorization feedback form](https://radar.cloudflare.com/categorization-feedback/) to request a review.
 
 ### Error 526: Invalid SSL certificate
-
 Gateway presents a **526** error page when it cannot establish a secure connection to the origin. This typically occurs in two cases:
 
 - **Untrusted origin certificate**: The certificate presented by the origin server is expired, revoked, or issued by an unknown authority.
@@ -16,17 +14,14 @@ Gateway presents a **526** error page when it cannot establish a secure connecti
 For more information, refer to [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ### Error 502: Bad Gateway
-
 This issue can occur when communicating with an origin that partially supports HTTP/2. If the origin requests a downgrade to HTTP/1.1 (for example, via a `RST_STREAM` frame with `HTTP_1_1_REQUIRED`), Gateway will not automatically reissue the request over HTTP/1.1 and will instead return a `502 Bad Gateway`. To resolve this, disable HTTP/2 at the origin server.
 
 ### Untrusted certificate warnings
-
 If users see certificate warnings for every page, ensure that the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) is installed and trusted on their devices. This is required for Gateway to inspect HTTPS traffic.
 
 ## Dashboard and analytics
 
 ### Gateway analytics not displayed
-
 If you do not see analytics on the Gateway Overview page:
 
 - **Verify DNS traffic**: Ensure your devices are actually sending queries to Gateway. Check your [DNS locations](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) and verify the source IPv4 address.
@@ -131,8 +126,8 @@ To resolve this issue:
 
 You have configured Gateway to resolve internal hostnames, but users are unable to access them. For example, a user connected to the Cloudflare One Client tries to access an internal service like `jira.mycompany.local`, but the DNS query fails.
 
-| Common causes                              | Solution                                                                                                                                                                                                                                       |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                                               |
+| Common causes                              | Solution                                                                                                                                                                                                                  |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Missing or incorrect resolver policy       | Go to **Traffic policies** &gt; **Resolver policies**. Create a policy that matches your internal domain suffix and forwards queries to your internal DNS servers' IP addresses.                                             |
 | Split Tunnel excludes the private IP range | If your internal resources are in a private IP range (such as `10.0.0.0/8`), that range must be included in the tunnel. If it is in the Exclude list of your Split Tunnel configuration, the Cloudflare One Client will not proxy the traffic. |
-| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                                           |
+| Local Domain Fallback misconfiguration     | Use resolver policies for corporate DNS. Only use Local Domain Fallback for domains specific to a user's immediate physical network.                                                                                      |
diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
index 0a544adaa854c9b..bec8b880edeb7cc 100644
--- a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Render } from "~/components";
@@ -8,4 +9,4 @@ A `1033` error indicates your tunnel is not connected to Cloudflare's network be
 
 First, review whether your tunnel is listed as `Active` in the [Cloudflare dashboard](https://dash.cloudflare.com/) by going to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status:
 
-<Render file="tunnel/tunnel-status" product="cloudflare-one" />
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
index b4d07916659c2d7..cf11d2740614eac 100644
--- a/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/account-scoped-roles.mdx
@@ -1,12 +1,11 @@
 ---
 {}
+
 ---
 
 Minimum permissions needed to create, delete, and configure tunnels for an account:
-
 - [Cloudflare Access](/cloudflare-one/roles-permissions/)
 
 Additional permissions needed to [route traffic to a public hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) and to be able to perform `cloudflared login`:
-
 - [DNS](/fundamentals/manage-members/roles/)
-- [Load Balancer](/fundamentals/manage-members/roles/)
+- [Load Balancer](/fundamentals/manage-members/roles/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
index 49599f43b544a2f..7df9b2e5a62c416 100644
--- a/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/add-published-application.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To add a published application when creating a new tunnel:
@@ -7,16 +8,16 @@ To add a published application when creating a new tunnel:
 1. Go to the **Published applications** tab.
 
 2. Enter a subdomain and select a **Domain** from the drop-down menu. Specify any subdomain or path information.
-   :::note
-   If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
-   :::
+	:::note
+	If you add a multi-level subdomain (more than one level of subdomain), you must [order an Advanced Certificate for the hostname](/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#i-see-this-site-cant-provide-a-secure-connection).
+	:::
 
 3. Under **Service**, choose a [service type](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/protocols/) and specify its URL. For example,
-   - **Type**: _HTTP_
-   - **URL**: `localhost:8000`
+	- **Type**: _HTTP_
+	- **URL**: `localhost:8000`
 
 4. Under **Additional application settings**, specify any [parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/origin-parameters/) you would like to add to your tunnel configuration.
 
    ![Example of a published application route in the Cloudflare One dashboard](~/assets/images/cloudflare-one/connections/connect-apps/published-app.png)
 
-5. Select **Save**.
+5. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
index 10f16e4d43c7afe..b070a82d446402e 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/cloudflared-replicas-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
index ceda180a2994ca9..00915193311f7b7 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/load-balancer-tcp-monitors.mdx
@@ -5,9 +5,10 @@ params:
 
 TCP monitors are not supported for tunnel endpoints. Instead, create a health check endpoint on the `cloudflared` host and use an HTTPS monitor. For example, you can use `cloudflared` to return a fixed HTTP status response:
 
-1. <a href={props.publishedAppRouteURL}>Add a published application route</a>
-   for the health check: - **Hostname**: `health-check.example.com` - **Service
-   Type**: _HTTP_STATUS_ - **HTTP Status Code**: `200`
+1. <a href={props.publishedAppRouteURL}>Add a published application route</a> for the health check:
+   - **Hostname**: `health-check.example.com`
+   - **Service Type**: _HTTP_STATUS_
+   - **HTTP Status Code**: `200`
 2. [Create a monitor](/load-balancing/monitors/create-monitor/) with these settings:
    - **Type**: _HTTPS_
    - **Path**: `/`
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
index a96ead9f4e833cc..f61bde5fb1a3556 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-baseline.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
-- Size each host with minimum 4GB of RAM and 4 CPU cores.
-- Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
+* Run a [`cloudflared` replica](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/#cloudflared-replicas) on two dedicated host machines per network location. Using two hosts enables server-side redundancy and traffic balancing.
+* Size each host with minimum 4GB of RAM and 4 CPU cores.
+* Allocate 50,000 [ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/#number-of-ports) to the `cloudflared` process on each host.
 
 This setup is usually sufficient to handle traffic from 8,000 users (4,000 per host).
diff --git a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
index 399600466878e2a..e38f3ea59068e4a 100644
--- a/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/availability/tunnel-capacity-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Unlike legacy VPNs where throughput is determined by the server's memory, CPU and other hardware specifications, Cloudflare Tunnel throughput is primarily limited by the number of ports configured in system software. Therefore, when sizing your `cloudflared` server, the most important element is sizing the available ports on the machine to reflect the expected throughput of TCP and UDP traffic.
diff --git a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
index d3d57f5ddd564cf..c4aa95aa270a7b2 100644
--- a/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/catch-all-policy.mdx
@@ -3,3 +3,4 @@
 ---
 
 To prevent Cloudflare One Client users from accessing your entire private network, we recommend creating a [catch-all Gateway block policy](/learning-paths/replace-vpn/build-policies/create-policy/#catch-all-policy) for your private IP space. You can then layer on higher priority Allow policies (in either Access or Gateway) which grant users access to specific applications or IPs.
+
diff --git a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
index 836d5c4e7335fae..32bad08d6a11538 100644
--- a/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx
@@ -1,4 +1,5 @@
 ---
+
 ---
 
 In your device profile, configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) goes through the WARP tunnel. Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode). For example, if your devices use the default `100.96.0.0/12` range:
diff --git a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
index c90519fd3fb9a8e..6c082731f7502d1 100644
--- a/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/create-tunnel.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
@@ -18,4 +19,4 @@
 
    ![Connector appearing in the UI after cloudflared has run](~/assets/images/cloudflare-one/connections/connect-apps/connector.png)
 
-8. Select **Next**.
+8. Select **Next**.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
index 4836708c394928a..0f7caefc4aa0c56 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Create a Cloudflare Tunnel in Cloudflare One and run the tunnel on the {props.one}.
 
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
index 061651ac15df2a8..2f6208021fb86bc 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx
@@ -11,17 +11,17 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 2.  In the **CIDR** tab, enter the **Private IP address** of your {props.resourceName} (for example, <code>{props.exampleIp}</code>). You can expand the IP range later if necessary.
 3.  In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through the Cloudflare One Client. For example, if you are using Split Tunnels in **Exclude** mode, delete <code>{props.splitTunnelCidr}</code>. We recommend re-adding the IPs that are not explicitly used by your {props.resourceName}.
 
-    To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
-    
-    <SubtractIPCalculator
-    	client:load
-    	defaults={{
-    		base: props.splitTunnelCidr,
-    		subtract: props.calcExclude
-    	}}
-    />
-    
-    Add the results back to your Split Tunnel Exclude mode list.
+        To determine which IP addresses to re-add, subtract your {props.resourceName} IPs from <code>{props.splitTunnelCidr}</code>:
+
+        <SubtractIPCalculator
+        	client:load
+        	defaults={{
+        		base: props.splitTunnelCidr,
+        		subtract: props.calcExclude
+        	}}
+        />
+
+        Add the results back to your Split Tunnel Exclude mode list.
 
 4.  To test on a user device:
     1. [Log in to the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/).
diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
index 170049a7ac5f7c8..9e70a1198bb9fb7 100644
--- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-public-hostname.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Published applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) allow anyone on the Internet to connect to HTTP resources hosted on your virtual private cloud (VPC). To add a published application for your Cloudflare Tunnel:
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
index 6980de61dec14cf..4f15318c29c1162 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/docker.mdx
@@ -24,30 +24,15 @@ params:
 
    ```json
    {
-   	"tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
-   	"connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
-   	"connections": [
-   		{ "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167" },
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.200.113",
-   			"index": 1
-   		},
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.192.47",
-   			"index": 2
-   		},
-   		{
-   			"isConnected": true,
-   			"protocol": 1,
-   			"edgeAddress": "198.41.200.73",
-   			"index": 3
-   		}
-   	],
-   	"icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
+     "tunnelID": "ef96b330-a7f5-4bce-a00e-827ce5be077f",
+     "connectorID": "d236670a-9f74-422f-adf1-030f5c5f0523",
+     "connections": [
+       { "isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.167"},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.113", "index": 1},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.192.47", "index": 2},
+       {"isConnected": true, "protocol": 1, "edgeAddress": "198.41.200.73", "index": 3}
+     ],
+     "icmp_sources": ["192.168.1.243", "fe80::c59:bd4a:e815:ed6"]
    }
    ```
 
diff --git a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
index af11a9afb297c8f..35a23d38040988e 100644
--- a/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/diagnostics/tunnel-diag-file.mdx
@@ -8,18 +8,18 @@ params:
 
 The `cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.
 
-| File name                | Description                                                                              | Instance  |
-| ------------------------ | ---------------------------------------------------------------------------------------- | --------- |
+| File name                | Description                                                                                                                                                  | Instance  |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
 | `cli-configuration.json` | <a href={props.runParametersURL}>Tunnel run parameters</a> used when starting the tunnel | diagnosee |
-| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                          | diagnosee |
-| `configuration.json`     | Tunnel configuration parameters                                                          | diagnosee |
-| `goroutine.pprof`        | goroutine profile made available by `pprof`                                              | diagnosee |
-| `heap.pprof`             | heap profile made available by `pprof`                                                   | diagnosee |
-| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis       | diagnosee |
-| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                      | diagnoser |
-| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                       | diagnoser |
-| `systeminformation.json` | Operating system information and resource usage                                          | diagnosee |
-| `task-result.json`       | Result of each diagnostic task                                                           | diagnoser |
-| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                              | diagnosee |
+| `cloudflared_logs.txt`   | <a href={props.logsURL}>Tunnel log file</a>[^1]                                                                    | diagnosee |
+| `configuration.json`     | Tunnel configuration parameters                                                                                                                              | diagnosee |
+| `goroutine.pprof`        | goroutine profile made available by `pprof`                                                                                                                  | diagnosee |
+| `heap.pprof`             | heap profile made available by `pprof`                                                                                                                       | diagnosee |
+| `metrics.txt`            | Snapshot of <a href={props.metricsURL}>Tunnel metrics</a> at the time of diagnosis               | diagnosee |
+| `network.txt`            | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                          | diagnoser |
+| `raw-network.txt`        | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6                                                                                           | diagnoser |
+| `systeminformation.json` | Operating system information and resource usage                                                                                                              | diagnosee |
+| `task-result.json`       | Result of each diagnostic task                                                                                                                               | diagnoser |
+| `tunnelstate.json`       | Tunnel connections at the time of diagnosis                                                                                                                  | diagnosee |
 
 [^1]: If the log file is blank, you may need to <a href={props.loglevelURL}>set `--loglevel` to `debug`</a> when you start the tunnel. The `--loglevel` parameter is only required if you ran the tunnel from the CLI using a `cloudflared tunnel run` command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes.
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
index e8c007b9d69d74c..2f2327ca51fb9e4 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-cloudflare-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Published applications inherit the Cloudflare settings for their hostname, including [cache rules](/cache/how-to/cache-rules/), [WAF rules](/waf/), and other [Rules](/rules/) configurations. You can change these settings for each hostname in the [Cloudflare dashboard](https://dash.cloudflare.com/).
diff --git a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
index 6e023ea0564f577..f3c26351bc152ee 100644
--- a/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/dns-records-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you create a tunnel, Cloudflare generates a subdomain at `<UUID>.cfargotunnel.com`. You point a CNAME record at this subdomain to route traffic from your hostname to the tunnel.
diff --git a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
index 5fb221e26749de9..ad172f22cfae0ee 100644
--- a/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/grpc-support.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Tunnel supports gRPC traffic via [private subnet routing](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/). Public hostname deployments are not currently supported.
diff --git a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
index 91d158683723dd9..da5faccbdab0cc8 100644
--- a/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/hostname-format-restrictions.mdx
@@ -5,16 +5,13 @@
 import { Details } from "~/components";
 
 <Details header="Hostname format restrictions">
-	- **Character limit:** Must be less than 255 characters. - **Supported
-	wildcards:** A single wildcard (`*`) is allowed, and it must represent a full
-	DNS label. Example: `*.internal.local` - **Unsupported wildcards:** The
-	following wildcard formats are not supported: - Partial wildcards such as
-	`*-dev.internal.local` or `dev-*.internal.local`. - Wildcards in the middle,
-	such as `foo*bar.internal.local` or `foo.*.internal.local`. - Multiple
-	wildcards in the hostname, such as `*.*.internal.local`. - **Wildcard
-	trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`)
-	is assumed. For example, `*.internal.local` is saved as `internal.local` but
-	will match all subdomains at the wildcard level (covers `foo.internal.local`
-	but not `foo.bar.internal.local`). - **Dot trimming:** Leading and ending dots
-	(`.`) are allowed but trimmed off.
+- **Character limit:** Must be less than 255 characters.
+- **Supported wildcards:** A single wildcard (`*`) is allowed, and it must represent a full DNS label.
+			Example: `*.internal.local`
+- **Unsupported wildcards:** The following wildcard formats are not supported:
+		- Partial wildcards such as `*-dev.internal.local` or `dev-*.internal.local`.
+		- Wildcards in the middle, such as `foo*bar.internal.local` or `foo.*.internal.local`.
+		- Multiple wildcards in the hostname, such as `*.*.internal.local`.
+- **Wildcard trimming**: Leading wildcards (`*`) are trimmed off and an implicit dot (`.`) is assumed. For example, `*.internal.local` is saved as `internal.local` but will match all subdomains at the wildcard level (covers `foo.internal.local` but not `foo.bar.internal.local`).
+- **Dot trimming:** Leading and ending dots (`.`) are allowed but trimmed off.
 </Details>
diff --git a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
index 660cd5d5f759ab9..221f41fda76b716 100644
--- a/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/install-and-run-tunnel.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Tabs, TabItem } from "~/components";
@@ -46,4 +47,4 @@ import { Tabs, TabItem } from "~/components";
         	docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <TUNNEL_TOKEN>
         	```
 
-</TabItem>  </Tabs>
+</TabItem>  </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
index 4fdc32d904e2241..3e1b6567d49585d 100644
--- a/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/locally-managed/tunnel-permissions.mdx
@@ -12,16 +12,16 @@ Tunnel permissions determine who can run and manage a Cloudflare Tunnel. Two fil
 
 Refer to the table below for a comparison between the two files and the purposes for which they are intended.
 
-|                         | Account certificate                                                                                        | Tunnel credential                                         |
-| ----------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
-| **File name**           | `cert.pem`                                                                                                 | `<TUNNEL-UUID>.json`                                      |
-| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account                               | Authenticates the tunnel it is associated with            |
-| **Scope**               | Account-wide                                                                                               | Tunnel-specific                                           |
-| **File type**           | `.pem`                                                                                                     | `.json`                                                   |
-| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                                                  | <a href={props.defaultDirectoryURL}>Default directory</a> |
-| **Issued when running** | `cloudflared tunnel login`                                                                                 | `cloudflared tunnel create <NAME>`                        |
-| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate) | Does not expire                                           |
-| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)                                       | Run a tunnel. Create a config file.                       |
+|                         | Account certificate                                                          | Tunnel credential                                         |
+| ----------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------- |
+| **File name**           | `cert.pem`                                                                   | `<TUNNEL-UUID>.json`                                      |
+| **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account | Authenticates the tunnel it is associated with            |
+| **Scope**               | Account-wide                                                                 | Tunnel-specific                                           |
+| **File type**           | `.pem`                                                                       | `.json`                                                   |
+| **Stored in**           | <a href={props.defaultDirectoryURL}>Default directory</a>                    | <a href={props.defaultDirectoryURL}>Default directory</a> |
+| **Issued when running** | `cloudflared tunnel login`                                                   | `cloudflared tunnel create <NAME>`                        |
+| **Valid for**           | At least 10 years, and the service token it contains is valid until [revoked](#revoke-account-certificate)  | Does not expire                                           |
+| **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)         | Run a tunnel. Create a config file.                       |
 
 ## Tunnel ownership
 
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
index c3f3293198255e7..6c50a4d38d46d4a 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/filter-logs.mdx
@@ -9,8 +9,8 @@ You can filter logs by event type (`--event`), event level (`--level`), or sampl
 cloudflared tail --level debug <UUID>
 ```
 
-| Flag         | Description                                                                                                                         | Allowed values                            | Default value |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
-| `--event`    | Filter by the type of event / request.                                                                                              | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
+| Flag         | Description                                                                                                                                                                                           | Allowed values                            | Default value |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------- |
+| `--event`    | Filter by the type of event / request.                                                                                                                                                                | `cloudflared`, `http`, `tcp`, `udp`       | All events    |
 | `--level`    | Return logs at this level and above. Works independently of the <a href={props.loglevelURL}>`--loglevel`</a> setting on the server. | `debug`, `info`, `warn`, `error`, `fatal` | `debug`       |
-| `--sampling` | Sample a fraction of the total logs.                                                                                                | Number from `0.0` to `1.0`                | `1.0`         |
+| `--sampling` | Sample a fraction of the total logs.                                                                                                                                                                  | Number from `0.0` to `1.0`                | `1.0`         |
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
index 7e5b276368ef811..9199c7ed894a76f 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx
@@ -3,6 +3,7 @@
 
 import { GlossaryTooltip } from "~/components";
 
+
 Dashboard log streams are only available for <GlossaryTooltip term="remotely-managed tunnel">remotely-managed tunnels</GlossaryTooltip>. To stream tunnel logs from the dashboard:
 
 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Connectors** > **Cloudflare Tunnels**.
diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
index c5d8a1638544701..323c86b55d57992 100644
--- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-on-server.mdx
@@ -12,3 +12,4 @@ To enable logs, <a href={props.runParametersURL}>run the tunnel</a> using the `-
 ```sh
 cloudflared tunnel --loglevel info --logfile cloudflared.log run <UUID>
 ```
+
diff --git a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
index bdc546346c31fc1..4e0fc2c84e7e66e 100644
--- a/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/metrics/cloudflared.mdx
@@ -19,7 +19,7 @@
 | `cloudflared_tunnel_tunnel_authenticate_success`    | Number of successful tunnel authentication events.                                                         | COUNTER |                                            |
 | `cloudflared_tunnel_tunnel_register_success`        | Number of successful tunnel registrations.                                                                 | COUNTER | `rpcName`                                  |
 | `cloudflared_udp_active_sessions`                   | Concurrent number of UDP sessions that are being proxied to any origin.                                    | GAUGE   |                                            |
-| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER |                                            |
+| `cloudflared_udp_total_sessions`                    | Total number of UDP sessions that have been proxied to any origin.                                         | COUNTER   |                                            |
 | `coredns_panics_total`                              | Number of panics.                                                                                          | COUNTER |                                            |
 | `quic_client_closed_connections`                    | Number of connections that have been closed.                                                               | COUNTER |                                            |
 | `quic_client_latest_rtt`                            | Latest round-trip time (RTT) measured on a connection.                                                     | GAUGE   | `conn_index`                               |
diff --git a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
index 1b6b39f6f1a5fda..000cf30ab14fdcb 100644
--- a/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/origin-parameters.mdx
@@ -132,8 +132,8 @@ When `true`, Happy Eyeballs is disabled.
 `cloudflared` starts a proxy server to translate HTTP traffic into TCP when proxying, for example, SSH or RDP.
 This configures what type of proxy will be started. Valid options are:
 
-- `""` for the regular proxy
-- `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
+* `""` for the regular proxy
+* `"socks"` for a SOCKS5 proxy. Refer to the <a href={props.kubectlTutorialURL}>tutorial on connecting through Cloudflare Access using kubectl</a> for more information.
 
 ### proxyAddress
 
diff --git a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
index 53e2484f9439265..2fd27a10bd6f00a 100644
--- a/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/package-manager.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
+You can check if `cloudflared` was installed by a package manager by running `ls -la /usr/local/etc/cloudflared/` and looking for `.installedFromPackageManager` in the output.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
index b0e9a72f30f6267..9bed10dd3b8e8ea 100644
--- a/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/protocols-table.mdx
@@ -6,19 +6,19 @@ params:
 
 The table below lists the service types you can route to a public hostname. Non-HTTP services require [installing `cloudflared` on the client](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/) for end users to connect.
 
-| Service type | Description                                                                                                                                                                                                                                                                                                                                                    | Example `service` value               |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
-| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP.                                                                                                                                                                                                                                                                                           | `http://localhost:8000`               |
-| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates.                                                                                                                                                                               | `https://localhost:8000`              |
-| UNIX         | Same as HTTP, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                          | `unix:/home/production/echo.sock`     |
-| UNIX + TLS   | Same as HTTPS, but uses a Unix socket.                                                                                                                                                                                                                                                                                                                         | `unix+tls:/home/production/echo.sock` |
-| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead.                     | `tcp://localhost:2222`                |
-| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22`                  |
-| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/).                                                                                                                                    | `rdp://localhost:3389`                |
-| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access).                                                                                                                     | `smb://localhost:445`                 |
-| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code.                                                                                                                                                                                                                                                                                                        | `http_status:404`                     |
-| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address.                                                                                                                                                                                                                                                                             | `bastion`                             |
-| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only).                                                                                                                                                                                                                  | `hello_world`                         |
+| Service type | Description | Example `service` value |
+| ------------ | ----------- | ----------------------- |
+| HTTP         | Proxies incoming HTTPS requests to your local web service over HTTP. | `http://localhost:8000` |
+| HTTPS        | Proxies incoming HTTPS requests directly to your local web service. You can <a href={props.disableTlsVerificationURL}>disable TLS verification</a> for self-signed certificates. | `https://localhost:8000` |
+| UNIX         | Same as HTTP, but uses a Unix socket. | `unix:/home/production/echo.sock` |
+| UNIX + TLS   | Same as HTTPS, but uses a Unix socket. | `unix+tls:/home/production/echo.sock` |
+| TCP          | Streams TCP over a WebSocket connection. End users run `cloudflared access tcp` to [connect](/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/arbitrary-tcp/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) instead. | `tcp://localhost:2222` |
+| SSH          | Streams SSH over a WebSocket connection. End users run `cloudflared access ssh` to [connect](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-cloudflared-authentication/). For long-lived connections, use [Client-to-Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/) instead. | `ssh://localhost:22` |
+| RDP          | Streams RDP over a WebSocket connection. For more information, refer to [Connect to RDP with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-cloudflared-authentication/). | `rdp://localhost:3389` |
+| SMB          | Streams SMB over a WebSocket connection. For more information, refer to [Connect to SMB with client-side cloudflared](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/smb/#connect-to-smb-server-with-cloudflared-access). | `smb://localhost:445` |
+| HTTP_STATUS  | Responds to all requests with a fixed HTTP status code. | `http_status:404` |
+| BASTION      | Allows `cloudflared` to act as a jump host, providing access to any local address. | `bastion` |
+| HELLO_WORLD  | Test server for validating your Cloudflare Tunnel connection (for <a href={props.locallyManagedTunnelsURL}>locally managed tunnels</a> only). | `hello_world` |
 
 ## IPv6 service addresses
 
diff --git a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
index effd28c88ed8811..05449ecd0346b32 100644
--- a/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/run-parameters.mdx
@@ -171,9 +171,9 @@ Specifies the path to a <a href={props.configurationFileURL}>configuration file<
 Requires `cloudflared` version 2025.7.0 or later.
 :::
 
-| Syntax                                                                 | Environment Variable        |
-| ---------------------------------------------------------------------- | --------------------------- |
-| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>` | `TUNNEL_DNS_RESOLVER_ADDRS` |
+| Syntax                                                                    | Environment Variable        |
+| ------------------------------------------------------------------------- | --------------------------- |
+| `cloudflared tunnel run --dns-resolver-addrs <IP:PORT> <UUID or NAME>`    | `TUNNEL_DNS_RESOLVER_ADDRS` |
 
 Specifies custom DNS resolver addresses for `cloudflared` to use instead of the host machine's default resolvers. Each address must be in `ip:port` format — providing an IP address without a port will cause `cloudflared` to fail to start. You can specify multiple resolvers by repeating the flag. For example,
 
diff --git a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
index a0e19ac3f17e0f6..0a7bafc56310b6d 100644
--- a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
@@ -2,9 +2,9 @@
 {}
 ---
 
-| Status       | Meaning                                                                                                                                                                                                                                                                                                                                | Recommended Action                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Healthy**  | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                                                                                                                                                                                                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **Inactive** | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                                                                                                                                                                                                   | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel). |
-| **Down**     | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                                                                                                                                                                                                       | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                                                                                           |
-| **Degraded** | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic. | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                                            |
+| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
+| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel-api/#4-install-and-run-the-tunnel).                           |
+| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` [service](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/as-a-service/) or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
+| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` [logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
index a868e4cec7f75c4..a8aee795acbec88 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-cli-target-list.mdx
@@ -16,4 +16,4 @@ warp-cli target list
 ├──────────────────────────────────────┼──────────┼───────┼───────────────────────┼──────────────────────┼────────────┤
 │ 01943cff-6130-7989-8bff-cbc02b59a2b1 │ SSH      │ 80    │ hostname: az-target   │ 172.16.0.0 (b1net)   │ alice, bob │
 ╰──────────────────────────────────────┴──────────┴───────┴───────────────────────┴──────────────────────┴────────────╯
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
index 9fd296c4c4257a5..612d5ce51183c58 100644
--- a/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
+++ b/src/content/partials/cloudflare-one/tunnel/warp-to-tunnel-route-ips.mdx
@@ -3,42 +3,42 @@ params:
   - one
 ---
 
-import { Markdown, Details, Tabs, TabItem } from "~/components";
+import { Markdown, Details, Tabs, TabItem} from "~/components";
 import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx";
 
 By default, WARP excludes traffic bound for [RFC 1918 space](https://datatracker.ietf.org/doc/html/rfc1918), which are IP addresses typically used in private networks and not reachable from the Internet. In order for the Cloudflare One Client to send traffic to your <Markdown text={props.one}/>, you must configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/) so that the IP/CIDR of your <Markdown text={props.one}/> routes through the Cloudflare One Client.
 
 1. First, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include** mode.
 2. Edit your Split Tunnel routes depending on the mode:
-   <Tabs> <TabItem label="Exclude IPs and domains">
-   
-   		If you are using **Exclude** mode:
-   
-   		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
-   
-   		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
-   
-   		You can use the following calculator to determine which IP addresses to re-add:
-   
-   			<SubtractIPCalculator
-   				client:load
-   				defaults={{
-   					base: "172.16.0.0/12",
-   					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
-   				}}
-   			/>
-   		<Details header="Calculator instructions" open = {true}>
-   		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
-   		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
-   		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
-   		</Details>
-   
-   		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
-   
-   
-      </TabItem> <TabItem label="Include IPs and domains">
-   		If you are using **Include** mode:
-   		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
-   		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
-   
-      </TabItem> </Tabs>
+  	<Tabs> <TabItem label="Exclude IPs and domains">
+
+		If you are using **Exclude** mode:
+
+		a. [Delete the route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#remove-a-route) containing your <Markdown text={props.one}/>'s IP/CIDR range. For example, if your network uses the default AWS range of `172.31.0.0/16`, delete `172.16.0.0/12`.
+
+		b. [Re-add IP/CIDR ranges](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) that are not explicitly used by your <Markdown text={props.one}/>. For the AWS example above, you would add new entries for `172.16.0.0/13`, `172.24.0.0/14`, `172.28.0.0/15`, and `172.30.0.0/16`. This ensures that only traffic to `172.31.0.0/16` routes through the Cloudflare One Client.
+
+		You can use the following calculator to determine which IP addresses to re-add:
+
+			<SubtractIPCalculator
+				client:load
+				defaults={{
+					base: "172.16.0.0/12",
+					subtract: ["172.31.0.0/16", `172.28.0.0/15`]
+				}}
+			/>
+		<Details header="Calculator instructions" open = {true}>
+		1. In **Base CIDR**, enter the RFC 1918 range that you deleted from Split Tunnels.
+		2. In **Subtracted CIDRs**, enter the IP/CIDR range used by your <Markdown text={props.one}/>.
+		3. Re-add the calculator results to your Split Tunnel Exclude mode list.
+		</Details>
+
+		By tightening the private IP range included in the Cloudflare One Client, you reduce the risk of breaking a user's [access to local resources](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#allow-users-to-enable-local-network-exclusion).
+
+
+   </TabItem> <TabItem label="Include IPs and domains">
+		If you are using **Include** mode:
+		1. Add the required [Zero Trust domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
+		2. [Add a route](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to include your <Markdown text={props.one}/>'s IP/CIDR range.
+
+   </TabItem> </Tabs>
diff --git a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
index aed1dc57c84005a..88879da57d19361 100644
--- a/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-notification-lag.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-It may take up to 10 minutes for newly updated settings to propagate to devices.
+It may take up to 10 minutes for newly updated settings to propagate to devices.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
index cc4a288a0d916a4..885e29755b6d368 100644
--- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
+++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105`
diff --git a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
index dfc8ccca98273c3..0f9cabfed41c022 100644
--- a/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
+++ b/src/content/partials/cloudflare-one/warp/device-enrollment-mtls.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components";
+import { GlossaryTooltip, Tabs, TabItem, Render, Details } from "~/components"
 
 <Details header="Certificate requirements">
-	<Render file="byo-ca-mtls-cert-requirements" product="ssl" />
+   <Render file="byo-ca-mtls-cert-requirements" product="ssl" />
 </Details>
 
 To check for an mTLS certificate:
@@ -80,4 +81,4 @@ To check for an mTLS certificate:
 
 5. On your device, add the client certificate to the [system keychain](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/#test-in-the-browser).
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
index 4c9ebbf7bef15c0..565425c2df7ac87 100644
--- a/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
+++ b/src/content/partials/cloudflare-one/warp/enroll-ios-android.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 1. [Download](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and install the Cloudflare One Agent app.
 2. Launch the Cloudflare One Agent app.
diff --git a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
index 18e8ab3a2beb429..0c7940a4582c545 100644
--- a/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
+++ b/src/content/partials/cloudflare-one/warp/ldf-best-practice.mdx
@@ -8,4 +8,4 @@ import { GlossaryTooltip } from "~/components";
 
 If your DNS server can be configured to connect to a Cloudflare <GlossaryTooltip term="on-ramp">on-ramp</GlossaryTooltip>, Cloudflare recommends using Gateway Resolver policies rather than Local Domain Fallback. Gateway Resolver policies provide more visibility by allowing you to log and review DNS traffic.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
index cb7f6b23c978461..65cc25e27b64395 100644
--- a/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
+++ b/src/content/partials/cloudflare-one/warp/managed-networks-sha-256.mdx
@@ -12,4 +12,4 @@ The output will look something like:
 
 ```txt
 SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8662
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
index b54554c4a3ae864..77582cb8d22f063 100644
--- a/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
+++ b/src/content/partials/cloudflare-one/warp/manually-reauth.mdx
@@ -6,4 +6,4 @@ To manually refresh your Cloudflare Access session and update your group informa
 
 `https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/refresh-identity`
 
-Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
+Reauthenticating resets your [session duration](/cloudflare-one/access-controls/access-settings/session-management/) and fetches the latest group information from the organization's IdP.
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
index 81e72731b5d5abf..9df1996bb09d5b3 100644
--- a/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
+++ b/src/content/partials/cloudflare-one/warp/mdm-policy-file.mdx
@@ -1,16 +1,13 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Refer to our [managed deployment instructions](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/) and create a `.plist`, `mdm.xml`, or `.msi` policy file based on your organization's software management tool.
 
-<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we
-recommend that your policy file only contain the organization name and
-potentially the onboarding flag, [relying on the
-dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/)
-to configure the remaining device settings.
+<Render file="warp/mdm-dash-conflict" product="cloudflare-one" /> Therefore, we recommend that your policy file only contain the organization name and potentially the onboarding flag, [relying on the dashboard](/learning-paths/secure-internet-traffic/configure-device-agent/device-profiles/) to configure the remaining device settings.
 
 ```xml
 <dict>
diff --git a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
index 324b01831d1d350..40d23df27682b3c 100644
--- a/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
+++ b/src/content/partials/cloudflare-one/warp/os-version-semver.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::note
 
 The OS version must be specified as a valid [Semver](https://semver.org/). For example, if your device is running OS version `1.2`, you must enter `1.2.0`.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
index 591e817aebaf97a..e7611c019caec78 100644
--- a/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
+++ b/src/content/partials/cloudflare-one/warp/sha-256-fingerprint.mdx
@@ -22,4 +22,4 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
 
 <Render file="warp/managed-networks-sha-256" product="cloudflare-one"/>
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
index bee309cd06764e9..84e14c59cd4278e 100644
--- a/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
+++ b/src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx
@@ -115,9 +115,9 @@ Avoid vague descriptions and include scenario, timestamps, and steps taken to tr
   <>
     <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p>
 
-<p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
+    <p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
 
-<p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
+    <p>The <code>sshd_config</code> file and <code>ssh -vvv alice@10.116.0.3</code> output are attached. The tunnel status is Healthy in the Cloudflare dashboard, and Access authentication logs show a successful <code>Access granted</code> decision.</p>
 
   </>
 ) : props.tunnelMode ? (
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
index 3a4377564d2f4ff..d2177c9f8dc51ca 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/linux.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
-|                            |                                                                                                               |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| **OS version**             | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
-| **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                                                             |
-| **HD space**               | 75 MB                                                                                                         |
-| **Memory**                 | 35 MB                                                                                                         |
-| **Network interface type** | Wi-Fi or LAN                                                                                                  |
-| **MTU**                    | 1381 bytes recommended [^2]                                                                                   |
+|                       |                                                                               |
+| --------------------- | ----------------------------------------------------------------------------- |
+| **OS version**        | CentOS 8, RHEL 8, RHEL 9 [^1], Debian 12, Debian 13, Fedora 34, Fedora 35, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS |
+| **Processor**         | AMD64 / x86-64 or ARM64 / AArch64                                   |
+| **HD space**          | 75 MB                                                                         |
+| **Memory**            | 35 MB                                                                         |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^2] |
 
 [^1]: On RHEL 9 and later, enable the [Extra Packages for Enterprise Linux (EPEL)](https://docs.fedoraproject.org/en-US/epel/) repository (`sudo dnf install epel-release`) before installing `cloudflare-warp`. EPEL provides dependencies required by the client UI.
 
-[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^2]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
index 8742afdde17d699..48053016ac259ca 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/macOS.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-|                            |                                                                    |
-| -------------------------- | ------------------------------------------------------------------ |
-| **OS version**             | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+ |
-| **Processor**              | Intel or M series                                                  |
-| **HD space**               | 75 MB                                                              |
-| **Memory**                 | 35 MB                                                              |
-| **Network interface type** | Wi-Fi or LAN                                                       |
-| **MTU**                    | 1381 bytes recommended [^1]                                        |
+|                       |                                                   |
+| --------------------- | ------------------------------------------------- |
+| **OS version**        | Sonoma 14.0+, Sequoia 15.1+ (15.0.x is not supported), Tahoe 26.0+                                 |
+| **Processor**         | Intel or M series   |
+| **HD space**          | 75 MB                                             |
+| **Memory**            | 35 MB                                             |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^1] |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
index 8c0f46bf3c6c5ae..7f1dfe65c468ba2 100644
--- a/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
+++ b/src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
-|                            |                                                                      |
-| -------------------------- | -------------------------------------------------------------------- |
-| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11 |
+|                            |                                                   |
+| -------------------------- | ------------------------------------------------- |
+| **OS version**             | Windows 10 LTSC, Windows 11, Windows 365 Cloud PC running Windows 11                           |
 | **Processor**              | AMD64 / x86-64 or ARM64 / AArch64                                    |
-| **.NET Framework version** | 4.7.2 or later                                                       |
-| **HD space**               | 184 MB                                                               |
-| **Memory**                 | 3 MB                                                                 |
-| **Network interface type** | Wi-Fi or LAN                                                         |
-| **MTU**                    | 1381 bytes recommended [^1]                                          |
+| **.NET Framework version** | 4.7.2 or later                                    |
+| **HD space**               | 184 MB                                            |
+| **Memory**                 | 3 MB                                              |
+| **Network interface type**  | Wi-Fi or LAN |
+| **MTU** | 1381 bytes recommended [^1] |
 
-[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
+[^1]: Minimum 1281 bytes with [Path MTU Discovery](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/)
\ No newline at end of file
diff --git a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
index f13c7f8da379164..168c80b4c6089fd 100644
--- a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
+++ b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx
@@ -1,17 +1,19 @@
 ---
 {}
+
 ---
 
 Perform these steps in the [Cloudflare dashboard](https://dash.cloudflare.com/) under **Zero Trust** > **Team & Resources** > **Devices** > **Device profiles** > **General profiles**.
 
 1. Set your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) to **Exclude IPs and domains**.
 2. [Add the following entries](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to your Split Tunnel Exclude list:
-   - Private IP address range exposed by your third-party VPN client. For example,
+
+   * Private IP address range exposed by your third-party VPN client. For example,
      | Selector | Value |
      | -------- | ----- |
-     | IP Address | `172.16.0.0/12` |
+     | IP Address   | `172.16.0.0/12` |
      |
-   - Server that your third-party VPN client connects to. For example,
+   * Server that your third-party VPN client connects to. For example,
      | Selector | Value |
      | -------- | ----- |
-     | Domain | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
+     | Domain   | `*.cvpn-endpoint-xxxxx.prod.clientvpn.us-west-2.amazonaws.com` |
diff --git a/src/content/partials/cloudflare-one/warp/warp-modes.mdx b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
index fe4dbbfb81edeea..ed493a08759ce6b 100644
--- a/src/content/partials/cloudflare-one/warp/warp-modes.mdx
+++ b/src/content/partials/cloudflare-one/warp/warp-modes.mdx
@@ -4,8 +4,8 @@
 
 Each client mode offers a different set of Zero Trust features.
 
-| Client mode                                                                                                                                          | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
+| Client mode                                                                                                                                   | DNS Filtering | Network Filtering | HTTP Filtering | Service mode (displayed in `warp-cli settings`) |
+| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------- | -------------- | ----------------------------------------------- |
 | [**Traffic and DNS mode (default)**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-and-dns-mode-default) | ✅            | ✅                | ✅             | `WarpWithDnsOverHttps`                          |
 | [**DNS only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode)                                 | ✅            | ❌                | ❌             | `DnsOverHttps`                                  |
 | [**Traffic only mode**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#traffic-only-mode)                         | ❌            | ✅                | ✅             | `TunnelOnly`                                    |
diff --git a/src/content/partials/containers/instance-types.mdx b/src/content/partials/containers/instance-types.mdx
index 0c7e58181689b5f..705a0f3c5970555 100644
--- a/src/content/partials/containers/instance-types.mdx
+++ b/src/content/partials/containers/instance-types.mdx
@@ -1,8 +1,8 @@
 | Instance Type | vCPU | Memory  | Disk  |
-| ------------- | ---- | ------- | ----- |
+| ------------- | ---- | ------  | ----  |
 | lite          | 1/16 | 256 MiB | 2 GB  |
 | basic         | 1/4  | 1 GiB   | 4 GB  |
 | standard-1    | 1/2  | 4 GiB   | 8 GB  |
 | standard-2    | 1    | 6 GiB   | 12 GB |
 | standard-3    | 2    | 8 GiB   | 16 GB |
-| standard-4    | 4    | 12 GiB  | 20 GB |
+| standard-4    | 4    | 12 GiB  | 20 GB |
\ No newline at end of file
diff --git a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
index b0f0987a817dc7c..ea530442f741999 100644
--- a/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
+++ b/src/content/partials/d1/d1-do-supported-sqlite-extensions.mdx
@@ -1,6 +1,6 @@
 ---
 params:
-  - product
+- product
 ---
 
 {props.product} a subset of SQLite extensions for added functionality, including:
@@ -9,4 +9,4 @@ params:
 - [JSON extension](https://www.sqlite.org/json1.html) for JSON functions and operators.
 - [Math functions](https://sqlite.org/lang_mathfunc.html).
 
-Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
+Refer to the [source code](https://github.com/cloudflare/workerd/blob/4c42a4a9d3390c88e9bd977091c9d3395a6cd665/src/workerd/util/sqlite.c%2B%2B#L269) for the full list of supported functions.
\ No newline at end of file
diff --git a/src/content/partials/d1/generate-d1-api-token.mdx b/src/content/partials/d1/generate-d1-api-token.mdx
index 2c13c1ba8b60e3d..700bee2bfb563e9 100644
--- a/src/content/partials/d1/generate-d1-api-token.mdx
+++ b/src/content/partials/d1/generate-d1-api-token.mdx
@@ -21,4 +21,4 @@ import { Steps, DashButton } from "~/components";
 </Steps>
 
 - Refer to [Create API token](/fundamentals/api/get-started/create-token/) for more information on creating API tokens through the Cloudflare dashboard.
-- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
+- Refer to [Create tokens via API](/fundamentals/api/how-to/create-via-api/) for more information on creating API tokens through API.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
index 18b1bdc17d3c358..5c559f1e70ee53e 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
+Cloudflare's Advanced DNS Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), provides stateful protection against DNS-based DDoS attacks, specifically sophisticated and fully randomized DNS attacks such as [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/).
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
index 2cba0a9f642281c..9a44876d0af0d32 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/dns-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
+[Create a rule](/ddos-protection/advanced-ddos-systems/how-to/create-rule/#create-an-advanced-dns-protection-rule) to enable Advanced DNS Protection.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
index 54dbbb22ddac8c5..1393b132f8df703 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/mt-advanced-ddos-systems-onboarding.mdx
@@ -6,4 +6,4 @@
 Advanced TCP and DNS Protection systems are automatically enabled in `Monitor` mode with the default thresholds for new Magic Transit customers and their [authorized prefixes](/magic-transit/how-to/advertise-prefixes/).
 
 Magic Transit customers can also enable the Advanced DDoS systems when the prefixes are ready, change the sensitivity level, or adjust the thresholds by contacting their account team.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
index bd07b8b43cb7890..3b2d7e3139d2b5a 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-protection-intro.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
+Cloudflare's Advanced TCP Protection, powered by [`flowtrackd`](https://blog.cloudflare.com/announcing-flowtrackd/), is a stateful TCP inspection engine used to detect and mitigate sophisticated out-of-state TCP attacks such as randomized and spoofed ACK floods or SYN and SYN-ACK floods.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
index e6d886f65e51b05..2c4124f1e232eee 100644
--- a/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
+++ b/src/content/partials/ddos-protection/advanced-ddos/tcp-setup.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
+[Create a global configuration](/ddos-protection/advanced-ddos-systems/overview/#rules) to set up SYN Flood and Out-of-state TCP rules and filters for Advanced TCP Protection.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
index 4a2843a4d9281c2..a66db33424c00e8 100644
--- a/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
+++ b/src/content/partials/ddos-protection/alerts-and-reports-independent.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DDoS reports and DDoS alerts are independent: DDoS reports will include information about any attacks for which you received DDoS alerts.
diff --git a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
index e752ea9ae03f6d5..b98f5547923a93c 100644
--- a/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
+++ b/src/content/partials/ddos-protection/allowlist-ip-spoofing.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 :::caution[Important]
 
+
 Prefixes in the allowlist will be vulnerable to <GlossaryTooltip term="IP spoofing">IP spoofing</GlossaryTooltip> attacks. If an attacker can guess the source IP addresses you have allowlisted, their packets will be allowlisted.
 
+
 :::
diff --git a/src/content/partials/ddos-protection/atp-filter-definition.mdx b/src/content/partials/ddos-protection/atp-filter-definition.mdx
index 523d17768055849..12d6e288ceadf95 100644
--- a/src/content/partials/ddos-protection/atp-filter-definition.mdx
+++ b/src/content/partials/ddos-protection/atp-filter-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
+A filter modifies Advanced TCP Protection's [execution mode](/ddos-protection/advanced-ddos-systems/concepts/#mode) — monitoring, mitigation (enabled), or disabled — for all incoming packets matching an expression.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
index a961f5d75580c97..856694a96d0c99c 100644
--- a/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
+++ b/src/content/partials/ddos-protection/atp-filters-rules-precedence.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/ddos-protection/create-notification.mdx b/src/content/partials/ddos-protection/create-notification.mdx
index 8a4ea2addd089cb..d198471ab167dd0 100644
--- a/src/content/partials/ddos-protection/create-notification.mdx
+++ b/src/content/partials/ddos-protection/create-notification.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Steps, DashButton } from "~/components";
diff --git a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
index b78cd219dfc2f48..6b49ed03060ba7f 100644
--- a/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
+++ b/src/content/partials/ddos-protection/ddos-attack-coverage.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
-| OSI Layer   | Ruleset / Feature                                                                                        | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| ----------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| L3/4        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                       | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
-| L3/4        | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1] | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| L7 (DNS)    | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1] | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| L7 (HTTP/S) | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                   | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| OSI Layer       | Ruleset / Feature                                                                                                      | Example of covered DDoS attack vectors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| --------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| L3/4            | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/)                                     | ACK floods<br/>BitTorrent reflection attack<br/>Carpet Bombing attacks<br/>CHARGEN reflection attacks<br/>DNS amplification attack<br/>DNS Garbage Flood<br/>DNS NXDOMAIN flood<br/>DNS Query flood<br/>DTLS amplification attacks<br/>ESP flood<br/>GRE floods<br/><GlossaryTooltip term="ICMP">ICMP</GlossaryTooltip> flood attack<br/>Jenkins amplification attacks<br/>Lantronix reflection attacks<br/>mDNS DDoS attacks<br/>Memcached amplification attacks<br/>Mirai and Mirai-variant L3/4 attacks<br/>MSSQL reflection attacks<br/>NetBios DDoS attacks<br/>Out of state TCP attacks<br/>Protocol violation attacks<br/>QUIC flood attack<br/>Quote of the Day (QOTD) reflection attacks<br/>RST flood<br/>SIP attacks<br/>SNMP flood attack<br/>SPSS reflection attacks<br/>SSDP reflection attacks<br/>SYN floods<br/>SYN-ACK reflection attack<br/>TeamSpeak 3 floods<br/>Ubiquity reflection attacks<br/>UDP flood attack<br/>VxWorks DDoS attacks<br/><br/>For more DNS protection options, refer to [Getting additional DNS protection](/ddos-protection/about/attack-coverage/#getting-additional-dns-protection). |
+| L3/4            | [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) [^1]               | Fully randomized and spoofed ACK floods, SYN floods, SYN-ACK reflection attacks, and other sophisticated TCP-based DDoS attacks                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| L7 (DNS)        | [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) [^1]               | Sophisticated and fully randomized DNS attacks, including Water Torture attacks, Random-prefix attacks, and DNS laundering attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| L7 (HTTP/S)     | [HTTP DDoS Attack Protection](/ddos-protection/managed-rulesets/http/)                                                 | Cache busting attacks<br/>Carpet Bombing attacks<br/>HTTP Continuation flood<br/>HTTP flood attack<br/>HTTP/2 MadeYouReset<br/>HTTP/2 Rapid Reset<br/>HULK attack<br/>Known DDoS botnets<br/>LOIC attack<br/>Mirai and Mirai-variant HTTP attacks<br/>Slowloris attack<br/>TLS/SSL exhaustion attacks<br/>TLS/SSL negotiation attacks<br/>WordPress pingback attack<br/>                                                                                                                                                                                                                                                  |
 
 [^1]: Available to Magic Transit customers.
diff --git a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
index ebb6dc3d1dbdf51..6bd97998baead60 100644
--- a/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
+++ b/src/content/partials/ddos-protection/log-and-monitor-behavior-link.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
+Refer to the [Analytics documentation](/analytics/network-analytics/configure/displayed-data/#view-logged-or-monitored-traffic) for more information on how to view logged or monitored traffic.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
index a85897a7a575038..ffcd4438247f2b1 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details, Render, Steps, DashButton } from "~/components";
+import { Details, Render, Steps, DashButton } from "~/components"
 
 <Steps>
   1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
@@ -35,4 +35,4 @@ import { Details, Render, Steps, DashButton } from "~/components";
       - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
       :::
   8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
-</Steps>
+</Steps>
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
index 03910e37301db8a..b32f56a8b16d56e 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/evaluation-behavior.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Create multiple rules in the `ddos_l7` phase entry point ruleset to define different overrides for different sets of incoming requests. Set each rule expression according to the traffic whose HTTP DDoS protection you wish to customize.
 
-Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
+Rules in the phase entry point ruleset, where you create overrides, are evaluated in order until there is a match for a rule expression and sensitivity level, and Cloudflare will apply the first rule that matches the request. Therefore, the rule order in the entry point ruleset is very important.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
index 9b1cf47c23bbb2e..21e80e11b8adc25 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Highly targeted rules for mitigating DDoS attacks with a high confidence rate. These rules are read-only — you cannot override their sensitivity level or action.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
index fcc5ea826e263dc..3168c30b815a38a 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/read-only-rules-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The managed ruleset includes some read-only rules that you cannot override.
diff --git a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
index 0c3e48d1a2ab57c..6f4476224899bd4 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/sensitivity-level-reference.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 API property name: `"sensitivity_level"`.
@@ -10,15 +11,15 @@ The available sensitivity levels are:
 
 | UI value          | API value   |
 | ----------------- | ----------- |
-| _High_            | `"default"` |
-| _Medium_          | `"medium"`  |
-| _Low_             | `"low"`     |
-| _Essentially Off_ | `"eoff"`    |
+| *High*            | `"default"` |
+| *Medium*          | `"medium"`  |
+| *Low*             | `"low"`     |
+| *Essentially Off* | `"eoff"`    |
 
-The default sensitivity level is _High_.
+The default sensitivity level is *High*.
 
-In most cases, when you select the _Essentially Off_ sensitivity level the rule will not trigger for any of the selected actions, including _Log_. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
+In most cases, when you select the *Essentially Off* sensitivity level the rule will not trigger for any of the selected actions, including *Log*. However, if the attack is extremely large, Cloudflare's protection systems will still trigger the rule's mitigation action to protect Cloudflare's network.
 
-_Essentially Off_ means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+*Essentially Off* means that we have set an exceptionally low sensitivity level so in most cases traffic will not be mitigated for you. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
 
-**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
+**Log** means that requests will not be mitigated but only logged and shown on the dashboard. However, attack traffic will be mitigated at exceptional levels to ensure the safety and stability of the Cloudflare network.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
index 2b38abe2e55abcf..72d2abd12cf1632 100644
--- a/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
+++ b/src/content/partials/ddos-protection/managed-rulesets/test-rules-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Rules used for testing the detection, mitigation, and alerting capabilities of Cloudflare's DDoS protection products.
diff --git a/src/content/partials/ddos-protection/override-example.mdx b/src/content/partials/ddos-protection/override-example.mdx
index c25df1b5a153d19..4e8d68a92360f5f 100644
--- a/src/content/partials/ddos-protection/override-example.mdx
+++ b/src/content/partials/ddos-protection/override-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Example
@@ -13,33 +14,33 @@ A DDoS managed ruleset contains the following managed rules:
 The following ruleset overrides have been configured:
 
 - **Ruleset override A**
-  - **Managed rule 1** is set to `block`
+   - **Managed rule 1** is set to `block`
 - **Ruleset override B**
-  - The action of the entire ruleset (or _all managed rules_) is set to `Managed Challenge`
-  - **Managed rule 1** is set to `log`
-  - **Managed rule 2** is set to `log`
+   - The action of the entire ruleset (or *all managed rules*) is set to `Managed Challenge`
+   - **Managed rule 1** is set to `log`
+   - **Managed rule 2** is set to `log`
 - **Ruleset override C**
-  - **Managed rule 3** is set to `log`
+   - **Managed rule 3** is set to `log`
 
-### Use case
+### Use case 
 
 A DDoS attack was detected on **managed rules 1**, **2**, and **3**, and has generated a mitigation rule.
 
-- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules.
+- Since **managed rule 1** matches **ruleset override A**, Cloudflare will `block` the attacks and not proceed with the rest of the rules. 
 
 - **Managed rule 2** does not match **ruleset override A**, so Cloudflare proceeds to **ruleset override B**. <br /> **Ruleset override B** matches both all managed rules and **managed rule 2**, but specificity takes precedence. It does not `challenge` and instead proceeds with `log` since it matches the most specific managed rule.
 
-- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets _all managed rules_ to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
+- **Managed rule 3** does not match **ruleset override A**, so Cloudflare proceeds to **rule override B**. Since **ruleset override B** sets *all managed rules* to `challenge`, then Cloudflare does not proceed to **ruleset override C**.
 
 An additional dimension to take into account is Cloudflare’s DDoS systems will apply a given rule override only if its conditions are met — which includes the Sensitivity level. So, while it needs to match and modify the correct managed rule (or everything in the case of all managed rules above), it also has to meet the specified Sensitivity level of the rule.
 
 - **Rule override A**
-  - _All managed rules_ are set to `challenge` at low sensitivity
+   - *All managed rules* are set to `challenge` at low sensitivity
 
 - **Rule override B**
-  - **Managed rule 1** is set to `log` at default sensitivity
+   - **Managed rule 1** is set to `log` at default sensitivity
 
 You receive a small attack below the threshold for low sensitivity, but above the threshold for high sensitivity on **managed rule 1**.
 
-- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate.
-- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
+- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate. 
+- **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.
\ No newline at end of file
diff --git a/src/content/partials/ddos-protection/override-logic.mdx b/src/content/partials/ddos-protection/override-logic.mdx
index a4cde6e1c07ac0b..b9ff54257029827 100644
--- a/src/content/partials/ddos-protection/override-logic.mdx
+++ b/src/content/partials/ddos-protection/override-logic.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
 When Cloudflare's DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection managed ruleset. Each mitigation rule is generated from a single managed rule.
 
-All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches.
+All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches. 
 
-You can create only one ruleset override that can contain one or multiple rule overrides.
+You can create only one ruleset override that can contain one or multiple rule overrides. 
 
 :::note
 Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanced-ddos-systems/overview/) add-on can create up to 10 ruleset overrides.
@@ -14,4 +15,4 @@ Enterprise customers with the [Advanced DDoS Protection](/ddos-protection/advanc
 
 A rule override instructs the DDoS system on the action it should take against the attack according to its matching managed rule.
 
-However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override.
+However, within a rule override, specificity matters and the DDoS system will choose the more specific configuration. A rule override takes precedence over the ruleset override. 
\ No newline at end of file
diff --git a/src/content/partials/dmarc-management/domain-spoofing.mdx b/src/content/partials/dmarc-management/domain-spoofing.mdx
index 789d26bbd41acbb..f67efe27497fedf 100644
--- a/src/content/partials/dmarc-management/domain-spoofing.mdx
+++ b/src/content/partials/dmarc-management/domain-spoofing.mdx
@@ -10,6 +10,8 @@ Without email authentication records, anyone can send email that appears to come
 
 :::note
 
+
 For additional background on email security records, refer to the [introductory blog post](https://blog.cloudflare.com/tackling-email-spoofing/).
 
+
 :::
diff --git a/src/content/partials/dns/a-aaaa-definition.mdx b/src/content/partials/dns/a-aaaa-definition.mdx
index 7871b0c522c087c..382543d232d0715 100644
--- a/src/content/partials/dns/a-aaaa-definition.mdx
+++ b/src/content/partials/dns/a-aaaa-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [A and AAAA records](https://www.cloudflare.com/learning/dns/dns-records/dns-a-record/) map a domain name to one or multiple IPv4 or IPv6 address(es).
diff --git a/src/content/partials/dns/acns-tcns-byoip.mdx b/src/content/partials/dns/acns-tcns-byoip.mdx
index d54a916972d3a46..0184972c95cb464 100644
--- a/src/content/partials/dns/acns-tcns-byoip.mdx
+++ b/src/content/partials/dns/acns-tcns-byoip.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::note
 
diff --git a/src/content/partials/dns/acns-tcns-conditions.mdx b/src/content/partials/dns/acns-tcns-conditions.mdx
index 8ffad8ef38a32d5..910dee1af8bb028 100644
--- a/src/content/partials/dns/acns-tcns-conditions.mdx
+++ b/src/content/partials/dns/acns-tcns-conditions.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2;;param3
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-- {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
-- [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
+* {props.three} can create up to five different {props.one} custom nameserver sets. Each nameserver set must have between two and five different nameserver names (`ns_name`), and each name cannot belong to more than one set. For example, if `ns1.example.com` is part of `ns_set 1` it cannot be part of `ns_set 2` or vice versa.
+* [Subdomain setup](/dns/zone-setups/subdomain-setup/) or [reverse zones](/dns/additional-options/reverse-zones/) can use {props.one} custom nameservers as long as they use a different nameserver set (`ns_set`) than their parent, child, or any other zone in their direct hierarchy tree.
diff --git a/src/content/partials/dns/acns-tcns-intro.mdx b/src/content/partials/dns/acns-tcns-intro.mdx
index 4089262cc29499c..d75bd29c06d9035 100644
--- a/src/content/partials/dns/acns-tcns-intro.mdx
+++ b/src/content/partials/dns/acns-tcns-intro.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1;;param2;;param3;;param4;;param5
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 {props.one} custom nameservers ({props.two}CNS) allow you to define {props.three}-level custom nameservers and use them for different {props.four} within a Cloudflare {props.five}.
 
diff --git a/src/content/partials/dns/aname-alias-callout.mdx b/src/content/partials/dns/aname-alias-callout.mdx
index e958df71d713e10..6751169d5c78778 100644
--- a/src/content/partials/dns/aname-alias-callout.mdx
+++ b/src/content/partials/dns/aname-alias-callout.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's [CNAME flattening](/dns/cname-flattening/)[^1] allows you to create CNAME records at your [zone apex](/dns/concepts/#zone-apex), removing the need for those other record types.
 
-[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
+[^1]: A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to.
\ No newline at end of file
diff --git a/src/content/partials/dns/api-field-definitions.mdx b/src/content/partials/dns/api-field-definitions.mdx
index 2629350da26de28..af7ea90d28101b2 100644
--- a/src/content/partials/dns/api-field-definitions.mdx
+++ b/src/content/partials/dns/api-field-definitions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For field definitions, refer to the [API documentation](/api/resources/dns/subresources/records/methods/create/) (visible once you select the record type under the request body specification).
diff --git a/src/content/partials/dns/cname-definition.mdx b/src/content/partials/dns/cname-definition.mdx
index 324c92c3d9865a3..ac977bc79ea7fe9 100644
--- a/src/content/partials/dns/cname-definition.mdx
+++ b/src/content/partials/dns/cname-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [CNAME records](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/) map a domain name to another (canonical) domain name. They can be used to resolve other record types present on the target domain name.
diff --git a/src/content/partials/dns/cname-flattening-callout.mdx b/src/content/partials/dns/cname-flattening-callout.mdx
index 000688fb842401b..030fec534c89c49 100644
--- a/src/content/partials/dns/cname-flattening-callout.mdx
+++ b/src/content/partials/dns/cname-flattening-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If a CNAME target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the CNAME record itself will not be returned directly.
diff --git a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
index 6c9b25d037c6bfd..2d6ccf3c0e1d1b4 100644
--- a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
+++ b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::caution[Subdomain setup]
 If you also use subdomain setup[^1], consider the [available combinations](/dns/zone-setups/subdomain-setup/setup/#available-setups) and whether your zone conversion could have any implications.
 :::
 
-[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
+[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`).
\ No newline at end of file
diff --git a/src/content/partials/dns/dns-errors-ts-action.mdx b/src/content/partials/dns/dns-errors-ts-action.mdx
index 4d2f0fe2811d7d4..9dfa15e76d1dfa6 100644
--- a/src/content/partials/dns/dns-errors-ts-action.mdx
+++ b/src/content/partials/dns/dns-errors-ts-action.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: errorName
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 If you experience <code>{props.one}</code> errors with a newly activated domain, review your DNS settings in the Cloudflare dashboard.
 
diff --git a/src/content/partials/dns/dns-errors-ts-intro.mdx b/src/content/partials/dns/dns-errors-ts-intro.mdx
index d1d1d3950aaa5fa..cb332968acfcf3d 100644
--- a/src/content/partials/dns/dns-errors-ts-intro.mdx
+++ b/src/content/partials/dns/dns-errors-ts-intro.mdx
@@ -1,13 +1,16 @@
 ---
 inputParameters: errorName
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 If you or your visitors experience <code>{props.one}</code> errors after you [activate your domain on Cloudflare](/dns/zone-setups/full-setup/setup/), review your DNS records in Cloudflare.
 
 :::note
 
+
 If your domain is added to Cloudflare by a hosting partner, manage your DNS records via the hosting partner.
 
+
 :::
diff --git a/src/content/partials/dns/dns-nxdomain-warning.mdx b/src/content/partials/dns/dns-nxdomain-warning.mdx
index a0aa3e538b03546..d9b592cdc25513c 100644
--- a/src/content/partials/dns/dns-nxdomain-warning.mdx
+++ b/src/content/partials/dns/dns-nxdomain-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
-If you activate your domain on Cloudflare _without_ setting up the correct DNS records for your domain, your visitors may experience [DNS_PROBE_FINISHED_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
+
+If you activate your domain on Cloudflare *without* setting up the correct DNS records for your domain, your visitors may experience [DNS\_PROBE\_FINISHED\_NXDOMAIN](/dns/troubleshooting/dns-probe-finished-nxdomain/) errors.
+
 
 :::
diff --git a/src/content/partials/dns/dns-record-steps.mdx b/src/content/partials/dns/dns-record-steps.mdx
index 8ab4783d7d17bee..058a0bf5c7cacfd 100644
--- a/src/content/partials/dns/dns-record-steps.mdx
+++ b/src/content/partials/dns/dns-record-steps.mdx
@@ -4,13 +4,7 @@ params:
   - example
 ---
 
-import {
-	Tabs,
-	TabItem,
-	Render,
-	GlossaryTooltip,
-	DashButton,
-} from "~/components";
+import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
@@ -33,4 +27,4 @@ Use the [Create DNS Record API endpoint](/api/resources/dns/subresources/records
     - To point to an IPv6 address, select **AAAA Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the IPv6 address for the field `content`.
     - To point to a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (such as `your-site.host.example.com`), select **CNAME Record**, use {props.name} (<code>{props.example}</code>) for the field `name`, and use the fully qualified domain name for the field `content`.
 </TabItem>
-</Tabs>
+</Tabs>
\ No newline at end of file
diff --git a/src/content/partials/dns/dns-scan-intro.mdx b/src/content/partials/dns/dns-scan-intro.mdx
index e54726a33bab66b..8901df100607fa7 100644
--- a/src/content/partials/dns/dns-scan-intro.mdx
+++ b/src/content/partials/dns/dns-scan-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/dns-scan-note.mdx b/src/content/partials/dns/dns-scan-note.mdx
index eff151ba8112ac8..636218d0b27de88 100644
--- a/src/content/partials/dns/dns-scan-note.mdx
+++ b/src/content/partials/dns/dns-scan-note.mdx
@@ -1,5 +1,5 @@
 ---
 {}
----
 
+---
 If you add a zone via the [API](/api/resources/zones/methods/create/), you can manually invoke the quick scan with the [Trigger DNS Records Scan endpoint](/api/resources/dns/subresources/records/methods/scan_trigger/).
diff --git a/src/content/partials/dns/dnssec-auto-add.mdx b/src/content/partials/dns/dnssec-auto-add.mdx
index 692574c3903a3ce..c59ce7dadf53c5d 100644
--- a/src/content/partials/dns/dnssec-auto-add.mdx
+++ b/src/content/partials/dns/dnssec-auto-add.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Note:]
 
+
 Cloudflare automatically adds **DS** records for domains using Cloudflare Registrar or those using `.ch` and `.cz` top-level domains.
 
+
 :::
diff --git a/src/content/partials/dns/dnssec-cloudflare-steps.mdx b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
index 97e0be8c4a00e2d..d066c3e5a606e96 100644
--- a/src/content/partials/dns/dnssec-cloudflare-steps.mdx
+++ b/src/content/partials/dns/dnssec-cloudflare-steps.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/dns/dnssec-definition.mdx b/src/content/partials/dns/dnssec-definition.mdx
index e286d2e3f82b1ed..8e4f721549a3dcd 100644
--- a/src/content/partials/dns/dnssec-definition.mdx
+++ b/src/content/partials/dns/dnssec-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS Security Extensions (DNSSEC) adds an extra layer of authentication to DNS, ensuring requests are not routed to a spoofed domain.
diff --git a/src/content/partials/dns/dnssec-enabled-migration.mdx b/src/content/partials/dns/dnssec-enabled-migration.mdx
index 34be4c281d852e9..2baa9a405746770 100644
--- a/src/content/partials/dns/dnssec-enabled-migration.mdx
+++ b/src/content/partials/dns/dnssec-enabled-migration.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If your previous provider allows you to add DNSKEY records on the zone apex and use these records in responses to DNS queries, refer to this [migration tutorial](/dns/dnssec/dnssec-active-migration/) to learn how to migrate a zone with DNSSEC enabled.
 
+
 :::
diff --git a/src/content/partials/dns/dnssec-registrar-steps.mdx b/src/content/partials/dns/dnssec-registrar-steps.mdx
index bb870033de61d09..60a42cb75248c8b 100644
--- a/src/content/partials/dns/dnssec-registrar-steps.mdx
+++ b/src/content/partials/dns/dnssec-registrar-steps.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
-Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called _ECDSA Curve P-256 with SHA-256_.
+Add the **DS** record to your registrar. If Algorithm 13 - Cloudflare's preferred cipher choice - is not listed by your registrar, it may also be called *ECDSA Curve P-256 with SHA-256*.
 
 <Render file="dnssec-providers" product="dns" />
diff --git a/src/content/partials/dns/export-dns-records.mdx b/src/content/partials/dns/export-dns-records.mdx
index 1c63cb825b5f494..1f8697f19614b35 100644
--- a/src/content/partials/dns/export-dns-records.mdx
+++ b/src/content/partials/dns/export-dns-records.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
diff --git a/src/content/partials/dns/internal-dns-beta-note.mdx b/src/content/partials/dns/internal-dns-beta-note.mdx
index 5f59566c426a379..5d69d57445eafa7 100644
--- a/src/content/partials/dns/internal-dns-beta-note.mdx
+++ b/src/content/partials/dns/internal-dns-beta-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/internal-dns-view-conditions.mdx b/src/content/partials/dns/internal-dns-view-conditions.mdx
index 864542fca83a966..b28ccc739a2b0fc 100644
--- a/src/content/partials/dns/internal-dns-view-conditions.mdx
+++ b/src/content/partials/dns/internal-dns-view-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - DNS views can be empty, with no [internal zones](/dns/internal-dns/internal-zones/) linked to them.
@@ -7,5 +8,4 @@
 - Each internal DNS zone name must be unique within a given DNS view.
 - Each DNS view name must be unique within a given Cloudflare account.
 
-<sup>1</sup> DNS zones that contain public DNS records and are accessible by
-public resolvers.
+<sup>1</sup> DNS zones that contain public DNS records and are accessible by public resolvers.
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-reference-zone-api.mdx b/src/content/partials/dns/internal-reference-zone-api.mdx
index 830c568f97e562c..05e1180d9227406 100644
--- a/src/content/partials/dns/internal-reference-zone-api.mdx
+++ b/src/content/partials/dns/internal-reference-zone-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -9,12 +10,14 @@ In the following example, internal zone A (ID `8a904aeb565c42cfa207d98f6edea2f3`
 <APIRequest
 	path="/zones/{zone_id}/dns_settings"
 	method="PATCH"
-	json={{
-		internal_dns: {
-			reference_zone_id: "8e64c6fb4b514f3faf64de81efc11e51",
-		},
-	}}
+	json={
+		{
+    "internal_dns": {
+        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51"
+    }
+		}
+	}
 	parameters={{
 		zone_id: "8a904aeb565c42cfa207d98f6edea2f3",
 	}}
-/>
+/>
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-reference-zone-intro.mdx b/src/content/partials/dns/internal-reference-zone-intro.mdx
index 94e58c8e201d0d8..71d7c7621b8fda4 100644
--- a/src/content/partials/dns/internal-reference-zone-intro.mdx
+++ b/src/content/partials/dns/internal-reference-zone-intro.mdx
@@ -5,9 +5,10 @@ params:
 
 During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain.
 
+
 { props.conditional === "get-started-link" && (
-<p>
-For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
-</p>
-)
-}
+	<p>
+	For details, refer to <a href="/dns/internal-dns/internal-zones/reference-zones/">reference zones</a>.
+	</p>
+	)
+}
\ No newline at end of file
diff --git a/src/content/partials/dns/internal-zones-conditions.mdx b/src/content/partials/dns/internal-zones-conditions.mdx
index 33e00fe187436c9..64201918a6fb264 100644
--- a/src/content/partials/dns/internal-zones-conditions.mdx
+++ b/src/content/partials/dns/internal-zones-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
@@ -8,5 +9,4 @@
 - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
 - Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`).
 
-<sup>1</sup> Logical groupings of internal DNS zones that are referenced by
-Gateway resolver policies to define how a specific query should be resolved.
+<sup>1</sup> Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved.
\ No newline at end of file
diff --git a/src/content/partials/dns/linked-peers-limit.mdx b/src/content/partials/dns/linked-peers-limit.mdx
index c18d3fb2b701548..07cf4abcd9e4cc3 100644
--- a/src/content/partials/dns/linked-peers-limit.mdx
+++ b/src/content/partials/dns/linked-peers-limit.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The maximum number of linked peers per zone is 30.
diff --git a/src/content/partials/dns/minimize-downtime-tip.mdx b/src/content/partials/dns/minimize-downtime-tip.mdx
index ca7fae767a4d48c..b13c26fb8eaa702 100644
--- a/src/content/partials/dns/minimize-downtime-tip.mdx
+++ b/src/content/partials/dns/minimize-downtime-tip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
+If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/performance/minimize-downtime/).
\ No newline at end of file
diff --git a/src/content/partials/dns/mix-proxied-and-unproxied.mdx b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
index c028f99ad6ccb3b..8b12a1d041c6e54 100644
--- a/src/content/partials/dns/mix-proxied-and-unproxied.mdx
+++ b/src/content/partials/dns/mix-proxied-and-unproxied.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If you have multiple `A/AAAA` records on the same name and at least one of them is proxied, Cloudflare will treat all `A/AAAA` records on this name as being proxied.
 
+
 :::
diff --git a/src/content/partials/dns/nameserver-preamble.mdx b/src/content/partials/dns/nameserver-preamble.mdx
index 5b17906420c1020..96bf1107d118e88 100644
--- a/src/content/partials/dns/nameserver-preamble.mdx
+++ b/src/content/partials/dns/nameserver-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
diff --git a/src/content/partials/dns/nameservers-registrar-callout.mdx b/src/content/partials/dns/nameservers-registrar-callout.mdx
index afcec9106f1f765..efdd668bfb70fc7 100644
--- a/src/content/partials/dns/nameservers-registrar-callout.mdx
+++ b/src/content/partials/dns/nameservers-registrar-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Cloudflare Registrar]
diff --git a/src/content/partials/dns/ns-advanced-vs-custom.mdx b/src/content/partials/dns/ns-advanced-vs-custom.mdx
index 42e1cfe62cc3fb3..085c0ab10e67144 100644
--- a/src/content/partials/dns/ns-advanced-vs-custom.mdx
+++ b/src/content/partials/dns/ns-advanced-vs-custom.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The advantages that come with Foundation DNS [advanced nameservers](/dns/foundation-dns/advanced-nameservers/) are currently not available for [custom nameservers](/dns/nameservers/custom-nameservers/). Make sure you only use one at a time.
diff --git a/src/content/partials/dns/ns-set-omission-callout.mdx b/src/content/partials/dns/ns-set-omission-callout.mdx
index aceb7ef494144c3..4255ed43dcb62dd 100644
--- a/src/content/partials/dns/ns-set-omission-callout.mdx
+++ b/src/content/partials/dns/ns-set-omission-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/ns-static-ips.mdx b/src/content/partials/dns/ns-static-ips.mdx
index f7cb24564edd03d..33542f81098b4ae 100644
--- a/src/content/partials/dns/ns-static-ips.mdx
+++ b/src/content/partials/dns/ns-static-ips.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The IPs assigned to each nameserver are static, meaning they will not change without notification.
+The IPs assigned to each nameserver are static, meaning they will not change without notification.
\ No newline at end of file
diff --git a/src/content/partials/dns/ns-update-providers.mdx b/src/content/partials/dns/ns-update-providers.mdx
index 207b9774b87ee74..4619e0f648cd65c 100644
--- a/src/content/partials/dns/ns-update-providers.mdx
+++ b/src/content/partials/dns/ns-update-providers.mdx
@@ -1,41 +1,42 @@
 ---
 {}
+
 ---
 
 This is not an exhaustive list of provider-specific instructions, but the following links may be helpful:
 
-- [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
-- [101Domain](https://help.101domain.com/kb/managing-name-server-records)
-- [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
-- [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
-- [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
-- [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
-- [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
-- [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
-- [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
-- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
-- [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
-- [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
-- [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
-- [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
-- [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
-- [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
-- [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
-- [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
-- [HostMonster](https://my.hostmonster.com/cgi/help/222)
-- [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
-- [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
-- [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
-- [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
-- [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
-- [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
-- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
-- [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
-- [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
-- [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
-- [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
-- [Register](https://www.register.com/knowledge)
-- [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
-- [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
-- [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
-- [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
+* [Ionos](https://www.ionos.com/help/domains/using-your-own-name-servers/using-your-own-name-servers-for-a-domain/)
+* [101Domain](https://help.101domain.com/kb/managing-name-server-records)
+* [Amazon](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing)
+* [Blacknight](https://help.blacknight.com/hc/articles/4413036322321-How-do-I-change-the-nameservers-for-my-domain)
+* [BlueHost](https://www.bluehost.com/help/article/custom-nameservers)
+* [DirectNIC](https://directnic.com/knowledge/article/33:how%2Bdo%2Bi%2Bmodify%2Bname%2Bservers%2Bfor%2Bmy%2Bdomain%2Bname%253F)
+* [DNSMadeEasy](http://www.dnsmadeeasy.com/support/faq/)
+* [Domain.com](https://www.domain.com/help/article/domain-management-how-to-update-nameservers)
+* [Dotster](https://www.dotster.com/help/article/domain-management-how-to-update-nameservers)
+* [DreamHost](https://help.dreamhost.com/hc/en-us/articles/360038897151)
+* [EasyDNS](https://kb.easydns.com/knowledge/settingchanging-nameservers/)
+* [Enom](https://help.enom.com/hc/en-us/articles/115000486451-Nameservers-NS)
+* [Fast Domain](https://www.fastdomain.com/hosting/help/transfer_client_start)
+* [FlokiNET](https://billing.flokinet.is/index.php?rp=/knowledgebase/57/Nameserver-and-DNS-records.html)
+* [Gandi](https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html)
+* [GoDaddy](https://www.godaddy.com/help/change-nameservers-for-your-domain-names-664)
+* [HostGator](https://www.hostgator.com/help/article/changing-name-servers)
+* [Hostico](https://hostico.ro/docs/setarea-nameserverelor-din-contul-de-client-hostico/)
+* [HostMonster](https://my.hostmonster.com/cgi/help/222)
+* [Hover](https://support.hover.com/support/solutions/articles/201000064742-changing-your-domain-nameservers)
+* [Internetdbs](https://faq.internetbs.net/hc/en-gb/articles/4516921367837-How-to-update-Nameservers-for-a-domain)
+* [iPage](https://www.ipage.com/help/article/domain-management-how-to-update-nameservers)
+* [MelbourneIT](https://support.melbourneit.au/docs/how-do-i-manage-my-dns-on-cpanel)
+* [Moniker](https://support.moniker.com/hc/en-gb/articles/10101271418653-How-to-update-Nameservers-for-a-domain)
+* [Name.com](https://www.name.com/support/articles/205934457-registering-custom-nameservers)
+* [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers-for-my-domain)
+* [Network Solutions](https://www.networksolutions.com/manage-it/edit-nameservers.jsp)
+* [OVH](https://docs.ovh.com/gb/en/domains/web_hosting_general_information_about_dns_servers/#step-2-edit-your-domains-dns-servers)
+* [Porkbun](https://kb.porkbun.com/article/22-how-to-change-your-nameservers)
+* [Rackspace](https://support.rackspace.com/how-to/rackspace-name-servers/)
+* [Register](https://www.register.com/knowledge)
+* [Squarespace](https://support.squarespace.com/hc/articles/4404183898125-Nameservers-and-DNSSEC-for-Squarespace-managed-domains#toc-open-the-domain-s-advanced-settings)
+* [Site5](https://kb.site5.com/dns-2/custom-nameservers/)
+* [Softlayer](https://cloud.ibm.com/docs/dns?topic=dns-add-edit-or-delete-custom-name-servers-for-a-domain)
+* [Yola](https://helpcenter.yola.com/hc/articles/360012492660-Changing-your-name-servers)
diff --git a/src/content/partials/dns/onboard-warning.mdx b/src/content/partials/dns/onboard-warning.mdx
index 883289d67398e5e..cd609c994c7516f 100644
--- a/src/content/partials/dns/onboard-warning.mdx
+++ b/src/content/partials/dns/onboard-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you [add a domain](/fundamentals/manage-domains/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
diff --git a/src/content/partials/dns/partial-setup-definition.mdx b/src/content/partials/dns/partial-setup-definition.mdx
index d429d6c760396ab..d4a185c7c288b4c 100644
--- a/src/content/partials/dns/partial-setup-definition.mdx
+++ b/src/content/partials/dns/partial-setup-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 A CNAME setup (also known as partial setup) allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
 
diff --git a/src/content/partials/dns/random-prefix-attack-definition.mdx b/src/content/partials/dns/random-prefix-attack-definition.mdx
index 3a4378c97f94a4e..421e48350e97627 100644
--- a/src/content/partials/dns/random-prefix-attack-definition.mdx
+++ b/src/content/partials/dns/random-prefix-attack-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Random prefix attacks are when someone sends a lot of traffic to subdomains that are highly unlikely to exist (`12345.example.com`, `abcdefg.example.com`), but are still associated with your main domain (`example.com`).
diff --git a/src/content/partials/dns/records-name-field.mdx b/src/content/partials/dns/records-name-field.mdx
index ed19a6fb9b2d987..ed33e8cf7fea2e3 100644
--- a/src/content/partials/dns/records-name-field.mdx
+++ b/src/content/partials/dns/records-name-field.mdx
@@ -3,7 +3,7 @@
 ---
 
 - **Name**: A subdomain or the zone apex (`@`).
-  - The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
-  - DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
-  - There is no requirement to start with a letter or end with a letter or digit.
-  - Underscores are valid in DNS and commonly used for service records.
+	- The name must be composed of labels of 63 characters or less (`label1.label2.label3`), where the fully qualified domain name (`label1.label2.label3.example.com`) does not exceed 253 characters.
+	- DNS labels can contain any octet (byte value). However, for compatibility with hostnames and TLS certificates, it is recommended to use only letters, digits, and hyphens (LDH rule). This is not a DNS protocol requirement, meaning DNS will work even if you do not follow these conventions.
+	- There is no requirement to start with a letter or end with a letter or digit.
+	- Underscores are valid in DNS and commonly used for service records.
diff --git a/src/content/partials/dns/recover-deleted-domain.mdx b/src/content/partials/dns/recover-deleted-domain.mdx
index dd9da29b1c18d12..04ea32052b4199c 100644
--- a/src/content/partials/dns/recover-deleted-domain.mdx
+++ b/src/content/partials/dns/recover-deleted-domain.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/manage-domains/add-site/) just like you would for a new domain.
diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx
index 8a76949a59dd2f5..3addd6a512c230f 100644
--- a/src/content/partials/dns/secondary-conversion-unlink.mdx
+++ b/src/content/partials/dns/secondary-conversion-unlink.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -11,4 +12,4 @@ import { DashButton } from "~/components";
 2. Under **DNS Zone Transfers**, and select **Manage linked peers**.
 3. Unlink the peer and select **Save**.
 
-At this point, your zone will be read-only.
+At this point, your zone will be read-only.
\ No newline at end of file
diff --git a/src/content/partials/dns/secondary-dns-override.mdx b/src/content/partials/dns/secondary-dns-override.mdx
index e85867604e92094..3479cba6efadd24 100644
--- a/src/content/partials/dns/secondary-dns-override.mdx
+++ b/src/content/partials/dns/secondary-dns-override.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Normal incoming zone transfers only provide DNS resolution. If you also want your traffic to benefit from Cloudflare's performance and security features, you need to [set up Secondary DNS Override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/).
diff --git a/src/content/partials/dns/ssltls-subdomains.mdx b/src/content/partials/dns/ssltls-subdomains.mdx
index 65f7bae8f4f3cc0..7509364e5359f30 100644
--- a/src/content/partials/dns/ssltls-subdomains.mdx
+++ b/src/content/partials/dns/ssltls-subdomains.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your main domain is using Cloudflare's [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/), that certificate also covers all first-level subdomains (`blog.example.com`).
diff --git a/src/content/partials/dns/subdomain-customization.mdx b/src/content/partials/dns/subdomain-customization.mdx
index ca49fdca438e461..b3d2fc5d81bd5a3 100644
--- a/src/content/partials/dns/subdomain-customization.mdx
+++ b/src/content/partials/dns/subdomain-customization.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to customize Cloudflare settings for individual subdomains, your approach will vary depending on your plan.
diff --git a/src/content/partials/dns/third-party-caveat.mdx b/src/content/partials/dns/third-party-caveat.mdx
index aa50c4ed3da9acf..32f0740937afdaf 100644
--- a/src/content/partials/dns/third-party-caveat.mdx
+++ b/src/content/partials/dns/third-party-caveat.mdx
@@ -1,11 +1,14 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::note
 
+
 When you [add records to Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/), those records should be [DNS-only (unproxied)](/dns/proxy-status/#dns-only-records) until {props.one} verifies your domain. Then, you can switch your DNS records to **Proxied**.
 
+
 :::
diff --git a/src/content/partials/dns/tsig-create-api.mdx b/src/content/partials/dns/tsig-create-api.mdx
index 240a4ecc1800410..0ca5c0a9ba3903e 100644
--- a/src/content/partials/dns/tsig-create-api.mdx
+++ b/src/content/partials/dns/tsig-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create a TSIG using the API, send a [POST](/api/resources/dns/subresources/zone_transfers/subresources/tsigs/methods/create/) request.
diff --git a/src/content/partials/dns/tsig-create-dash.mdx b/src/content/partials/dns/tsig-create-dash.mdx
index df306405d917d0e..b93345590415a34 100644
--- a/src/content/partials/dns/tsig-create-dash.mdx
+++ b/src/content/partials/dns/tsig-create-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -13,7 +14,7 @@ To create a TSIG using the dashboard:
 2. Go to **DNS Settings**.
 3. Under **DNS Zone Transfers**, for **TSIG**, select **Create**.
 4. Enter the following information:
-   - **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
-   - **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
-   - **Algorithm**: Choose a TSIG signing algorithm.
+   * **TSIG name**: The name of the TSIG object using domain name syntax (more details in [RFC 8945 section 4.2](https://datatracker.ietf.org/doc/html/rfc8945#section-4.2)).
+   * **Secret (optional)**: Get a shared secret to add to your third-party nameservers. If left blank, this field generates a random secret.
+   * **Algorithm**: Choose a TSIG signing algorithm.
 5. Select **Create**.
diff --git a/src/content/partials/dns/tsig-definition.mdx b/src/content/partials/dns/tsig-definition.mdx
index be7c2d62be93667..74fe88b3a4ddd3a 100644
--- a/src/content/partials/dns/tsig-definition.mdx
+++ b/src/content/partials/dns/tsig-definition.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 A Transaction Signature (TSIG) authenticates communication between a primary and secondary DNS server.
 
diff --git a/src/content/partials/dns/tsig-name-match.mdx b/src/content/partials/dns/tsig-name-match.mdx
index dffb08898eb97bf..ffaa6bc70ebfc62 100644
--- a/src/content/partials/dns/tsig-name-match.mdx
+++ b/src/content/partials/dns/tsig-name-match.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/dns/why-disable-dnssec.mdx b/src/content/partials/dns/why-disable-dnssec.mdx
index 2b37d7c7fa26608..57db63f976fd9d8 100644
--- a/src/content/partials/dns/why-disable-dnssec.mdx
+++ b/src/content/partials/dns/why-disable-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When your domain has [DNSSEC enabled](https://www.cloudflare.com/learning/dns/dns-security/#what-is-dnssec), your DNS provider digitally signs all your DNS records. This action prevents anyone else from issuing false DNS records on your behalf and redirecting traffic intended for your domain.
diff --git a/src/content/partials/dns/zone-defaults-exceptions.mdx b/src/content/partials/dns/zone-defaults-exceptions.mdx
index 1e74b26d026a49a..5005703713f7f89 100644
--- a/src/content/partials/dns/zone-defaults-exceptions.mdx
+++ b/src/content/partials/dns/zone-defaults-exceptions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones, nor zones that existed previously and are being revived.
diff --git a/src/content/partials/dns/zone-file-size-limit.mdx b/src/content/partials/dns/zone-file-size-limit.mdx
index 71afea606b6bc17..4873764d6189ff0 100644
--- a/src/content/partials/dns/zone-file-size-limit.mdx
+++ b/src/content/partials/dns/zone-file-size-limit.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The zone file size limit is 256 KiB (262144 bytes).
diff --git a/src/content/partials/durable-objects/api-async-kv-legacy.mdx b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
index a2698461e2eebcd..1ef05ec94c61a03 100644
--- a/src/content/partials/durable-objects/api-async-kv-legacy.mdx
+++ b/src/content/partials/durable-objects/api-async-kv-legacy.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Type, MetaInfo, AnchorHeading } from "~/components";
+import {Type, MetaInfo, AnchorHeading} from "~/components";
 
 <AnchorHeading title="get" slug="do-kv-async-get" depth={3} />
 
@@ -107,4 +107,4 @@ The `put()` method returns a `Promise`, but most applications can discard this p
   - Same as the option to [`get()`](#do-kv-async-get), above.
 
 - `noCache` <Type text ='boolean' />
-  - Same as the option to [`get()`](#do-kv-async-get), above.
+  - Same as the option to [`get()`](#do-kv-async-get), above.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-storage-alarms.mdx b/src/content/partials/durable-objects/api-storage-alarms.mdx
index 1014b07d6080c01..8deccef0d3d08f2 100644
--- a/src/content/partials/durable-objects/api-storage-alarms.mdx
+++ b/src/content/partials/durable-objects/api-storage-alarms.mdx
@@ -27,4 +27,4 @@ import { Type, MetaInfo, Render } from "~/components";
 
 #### Supported options
 
-- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
+- `setAlarm()` and `deleteAlarm()` support the same options as [`put()`](#do-kv-async-put), but without `noCache`.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-storage-other-methods.mdx b/src/content/partials/durable-objects/api-storage-other-methods.mdx
index 50cc1584f88f26d..05bf6d643f93346 100644
--- a/src/content/partials/durable-objects/api-storage-other-methods.mdx
+++ b/src/content/partials/durable-objects/api-storage-other-methods.mdx
@@ -39,4 +39,4 @@ import { Type, MetaInfo } from "~/components";
 - `sync()`: <Type text='Promise' />
   - Synchronizes any pending writes to disk.
 
-  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
+  - This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/api-sync-kv.mdx b/src/content/partials/durable-objects/api-sync-kv.mdx
index 84a39a044b3d293..816f231f927d279 100644
--- a/src/content/partials/durable-objects/api-sync-kv.mdx
+++ b/src/content/partials/durable-objects/api-sync-kv.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Type, MetaInfo } from "~/components";
+import {Type, MetaInfo} from "~/components";
 
 ### `get`
 
diff --git a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
index c869d21821c71a3..ea25a405ba4567b 100644
--- a/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
+++ b/src/content/partials/durable-objects/do-faq-metrics-and-analytics.mdx
@@ -2,8 +2,8 @@
 {}
 ---
 
-import { GlossaryTooltip, WranglerConfig } from "~/components";
+import {GlossaryTooltip, WranglerConfig} from "~/components";
 
 ### How can I identify which Durable Object instance generated a log entry?
 
-You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
+You can use `$workers.durableObjectId` to identify the specific Durable Object instance that generated the log entry.
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/do-plans-note.mdx b/src/content/partials/durable-objects/do-plans-note.mdx
index 3c7cb86f3649773..36771fa0ccba055 100644
--- a/src/content/partials/durable-objects/do-plans-note.mdx
+++ b/src/content/partials/durable-objects/do-plans-note.mdx
@@ -9,4 +9,4 @@ Durable Objects are available both on Workers Free and Workers Paid plans.
 - **Workers Paid plan**: Durable Objects with either SQLite storage backend or [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) are available.
 
 If you wish to downgrade from a Workers Paid plan to a Workers Free plan, you must first ensure that you have deleted all Durable Object namespaces with the key-value storage backend.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/durable-objects-sql.mdx b/src/content/partials/durable-objects/durable-objects-sql.mdx
index b13e5deb71af0d6..43eb7777f652040 100644
--- a/src/content/partials/durable-objects/durable-objects-sql.mdx
+++ b/src/content/partials/durable-objects/durable-objects-sql.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
 [SQL API](/durable-objects/api/sqlite-storage-api/#exec) examples below use the following SQL schema:
 
@@ -10,114 +10,102 @@ import { Details } from "~/components";
 import { DurableObject } from "cloudflare:workers";
 
 export class MyDurableObject extends DurableObject {
-	sql: SqlStorage;
-	constructor(ctx: DurableObjectState, env: Env) {
-		super(ctx, env);
-		this.sql = ctx.storage.sql;
+  sql: SqlStorage
+  constructor(ctx: DurableObjectState, env: Env) {
+    super(ctx, env);
+    this.sql = ctx.storage.sql;
 
-		this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
+    this.sql.exec(`CREATE TABLE IF NOT EXISTS artist(
       artistid    INTEGER PRIMARY KEY,
       artistname  TEXT
     );INSERT INTO artist (artistid, artistname) VALUES
       (123, 'Alice'),
       (456, 'Bob'),
-      (789, 'Charlie');`);
-	}
+      (789, 'Charlie');`
+    );
+  }
 }
 ```
 
 Iterate over query results as row objects:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist;");
+  let cursor = this.sql.exec("SELECT * FROM artist;");
 
-for (let row of cursor) {
-	// Iterate over row object and do something
-}
+  for (let row of cursor) {
+    // Iterate over row object and do something
+  }
 ```
 
 Convert query results to an array of row objects:
-
 ```ts
-// Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
-let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
-// OR
-let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
-// OR
-let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
+  // Return array of row objects: [{"artistid":123,"artistname":"Alice"},{"artistid":456,"artistname":"Bob"},{"artistid":789,"artistname":"Charlie"}]
+  let resultsArray1 = this.sql.exec("SELECT * FROM artist;").toArray();
+  // OR
+  let resultsArray2 = Array.from(this.sql.exec("SELECT * FROM artist;"));
+  // OR
+  let resultsArray3 = [...this.sql.exec("SELECT * FROM artist;")]; // JavaScript spread syntax
 ```
 
 Convert query results to an array of row values arrays:
-
 ```ts
-// Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
-let cursor = this.sql.exec("SELECT * FROM artist;");
-let resultsArray = cursor.raw().toArray();
-
-// Returns ["artistid","artistname"]
-let columnNameArray = this.sql
-	.exec("SELECT * FROM artist;")
-	.columnNames.toArray();
+  // Returns [[123,"Alice"],[456,"Bob"],[789,"Charlie"]]
+  let cursor = this.sql.exec("SELECT * FROM artist;");
+  let resultsArray = cursor.raw().toArray();
+
+  // Returns ["artistid","artistname"]
+  let columnNameArray = this.sql.exec("SELECT * FROM artist;").columnNames.toArray();
 ```
 
 Get first row object of query results:
-
 ```ts
-// Returns {"artistid":123,"artistname":"Alice"}
-let firstRow = this.sql
-	.exec("SELECT * FROM artist ORDER BY artistname DESC;")
-	.toArray()[0];
+  // Returns {"artistid":123,"artistname":"Alice"}
+  let firstRow = this.sql.exec("SELECT * FROM artist ORDER BY artistname DESC;").toArray()[0];
 ```
 
 Check if query results have exactly one row:
-
 ```ts
-// returns error
-this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
+  // returns error
+  this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;").one();
 
-// returns { artistid: 123, artistname: 'Alice' }
-let oneRow = this.sql
-	.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice")
-	.one();
+  // returns { artistid: 123, artistname: 'Alice' }
+  let oneRow = this.sql.exec("SELECT * FROM artist WHERE artistname = ?;", "Alice").one()
 ```
 
 Returned cursor behavior:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-let result = cursor.next();
-if (!result.done) {
-	console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
-} else {
-	// query returned zero results
-}
-
-let remainingRows = cursor.toArray();
-console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+  let result = cursor.next();
+  if (!result.done) {
+    console.log(result.value); // prints { artistid: 123, artistname: 'Alice' }
+  } else {
+    // query returned zero results
+  }
+
+  let remainingRows = cursor.toArray();
+  console.log(remainingRows); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 Returned cursor and `raw()` iterator iterate over the same query results:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
-let result = cursor.raw().next();
+  let cursor = this.sql.exec("SELECT * FROM artist ORDER BY artistname ASC;");
+  let result = cursor.raw().next();
 
-if (!result.done) {
-	console.log(result.value); // prints [ 123, 'Alice' ]
-} else {
-	// query returned zero results
-}
+  if (!result.done) {
+    console.log(result.value); // prints [ 123, 'Alice' ]
+  } else {
+    // query returned zero results
+  }
 
-console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
+  console.log(cursor.toArray()); // prints [{ artistid: 456, artistname: 'Bob' },{ artistid: 789, artistname: 'Charlie' }]
 ```
 
 `sql.exec().rowsRead()`:
-
 ```ts
-let cursor = this.sql.exec("SELECT * FROM artist;");
-cursor.next();
-console.log(cursor.rowsRead); // prints 1
+  let cursor = this.sql.exec("SELECT * FROM artist;");
+  cursor.next()
+  console.log(cursor.rowsRead); // prints 1
 
-cursor.toArray(); // consumes remaining cursor
-console.log(cursor.rowsRead); // prints 3
+  cursor.toArray(); // consumes remaining cursor
+  console.log(cursor.rowsRead); // prints 3
 ```
+
diff --git a/src/content/partials/durable-objects/recommend-sqlite-do.mdx b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
index 0d406290b88226e..dea8504982d30c4 100644
--- a/src/content/partials/durable-objects/recommend-sqlite-do.mdx
+++ b/src/content/partials/durable-objects/recommend-sqlite-do.mdx
@@ -8,4 +8,4 @@ Cloudflare recommends all new Durable Object namespaces use the [SQLite storage
 Additionally, SQLite-backed Durable Objects allow you to store more types of data (such as tables), and offer Point In Time Recovery API which can restore a Durable Object's embedded SQLite database contents (both SQL data and key-value data) to any point in the past 30 days.
 
 The [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) remains for backwards compatibility, and a migration path from KV storage backend to SQLite storage backend for existing Durable Object namespaces will be available in the future.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/durable-objects/what-are-durable-objects.mdx b/src/content/partials/durable-objects/what-are-durable-objects.mdx
index 82e992b0b2297d9..15b96c85f0f37a6 100644
--- a/src/content/partials/durable-objects/what-are-durable-objects.mdx
+++ b/src/content/partials/durable-objects/what-are-durable-objects.mdx
@@ -7,4 +7,4 @@ A Durable Object is a special kind of [Cloudflare Worker](/workers/) which uniqu
 - Each Durable Object has a **globally-unique name**, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together.
 - Each Durable Object has some **durable storage** attached. Since this storage lives together with the object, it is strongly consistent yet fast to access.
 
-Therefore, Durable Objects enable **stateful** serverless applications.
+Therefore, Durable Objects enable **stateful** serverless applications.
\ No newline at end of file
diff --git a/src/content/partials/email-routing/email-routing-definition.mdx b/src/content/partials/email-routing/email-routing-definition.mdx
index 6359302158f6bd7..b3fc4db641ed951 100644
--- a/src/content/partials/email-routing/email-routing-definition.mdx
+++ b/src/content/partials/email-routing/email-routing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Email Routing is designed to simplify the way you create and manage email addresses, without needing to keep an eye on additional mailboxes. With Email Routing, you can create any number of custom email addresses to use in situations where you do not want to share your primary email address, such as when you subscribe to a new service or newsletter. Emails are then routed to your preferred email inbox, without you ever having to expose your primary email address.
diff --git a/src/content/partials/email-routing/enable-create-worker.mdx b/src/content/partials/email-routing/enable-create-worker.mdx
index 0d37ad3ba5aaa03..240b23f507f76ab 100644
--- a/src/content/partials/email-routing/enable-create-worker.mdx
+++ b/src/content/partials/email-routing/enable-create-worker.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 4. (Optional) Enter a descriptive Email Worker name in **Create a worker name**.
diff --git a/src/content/partials/email-routing/send-emails-workers-intro.mdx b/src/content/partials/email-routing/send-emails-workers-intro.mdx
index e71d08e38f239f7..0e3bcc4027b1122 100644
--- a/src/content/partials/email-routing/send-emails-workers-intro.mdx
+++ b/src/content/partials/email-routing/send-emails-workers-intro.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: lastSentence
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 You can send an email about your Worker's activity from your Worker to an email address verified on [Email Routing](/email-routing/setup/email-routing-addresses/#destination-addresses). This is useful for when you want to know about certain types of events being triggered, for example.
 
diff --git a/src/content/partials/email-routing/types-bindings.mdx b/src/content/partials/email-routing/types-bindings.mdx
index 5d33d135b31a988..a15b5284b492f9d 100644
--- a/src/content/partials/email-routing/types-bindings.mdx
+++ b/src/content/partials/email-routing/types-bindings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/email-security/add-user.mdx b/src/content/partials/email-security/add-user.mdx
index 274d07c1c67b2ae..b36f104c9f96b1f 100644
--- a/src/content/partials/email-security/add-user.mdx
+++ b/src/content/partials/email-security/add-user.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: childParentInfo
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 1. Log in to the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/) {props.one}.
 2. Go to **Settings** (the gear icon).
diff --git a/src/content/partials/email-security/auto-retraction.mdx b/src/content/partials/email-security/auto-retraction.mdx
index aba4b1ad99db360..bbaf21ca8a016d6 100644
--- a/src/content/partials/email-security/auto-retraction.mdx
+++ b/src/content/partials/email-security/auto-retraction.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: hardRetract
+
 ---
 
-import { GlossaryTooltip, Markdown } from "~/components";
+import { GlossaryTooltip, Markdown } from "~/components"
 
 You can set up auto-retraction to automatically move messages matching certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to specific folders within a user's mailbox.
 
@@ -17,11 +18,12 @@ To set up automatic retraction:
 4. Select **Edit**.
 
 5. For each disposition, choose which folder the message should be sent to:
-   - **No Action**: Do not move the message.
-   - **Junk Email**: Sends the message to the junk or spam email folder.
-   - **Trash**: Sends the message to the trash or deleted items email folder.
-   - **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
-   - **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
+
+   * **No Action**: Do not move the message.
+   * **Junk Email**: Sends the message to the junk or spam email folder.
+   * **Trash**: Sends the message to the trash or deleted items email folder.
+   * **Soft Delete — user recoverable** (Microsoft only): Sends the message to the user's **Deleted Items** folder. Messages can be recovered by the user.
+   * **Hard Delete — admin recoverable**: Completely deletes messages from a user's inbox. {props.one}
 
 6. Select **Update Auto-retract Settings**.
 
@@ -31,5 +33,5 @@ Email Security (formerly Area 1) is continuously gathering new information about
 
 You can enable two options:
 
-- **Post Delivery Response**: Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
-- **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
+* **Post Delivery Response**:  Email Security (formerly Area 1) will continue to re-evaluate emails already delivered to your users' inboxes at a fixed time interval in search for phishing sites or campaigns not previously known to Cloudflare. If any email messages fitting these new criteria are found, Email Security (formerly Area 1) retracts them. Rescans occur at a five minute, 12 hour, and 24 hour intervals.
+* **Phish Submission Response**: Email Security (formerly Area 1) will retract emails already delivered that are reported by your users as phishing, and are found to be malicious by Email Security (formerly Area 1). Retraction will occur according to your configuration.
\ No newline at end of file
diff --git a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
index 5c8fd8d25359499..06080642f1da59c 100644
--- a/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-compromise-list.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Now that Email Security (formerly Area 1) has been authorized to access and retrieve directory information, you will need to configure the Business Email Compromise list.
diff --git a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
index 423c5edd0ddce5b..d13f48b4b6e1ecd 100644
--- a/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
+++ b/src/content/partials/email-security/bec-directory-guide-secondary-email.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When the Business Email Compromise list is configured, Email Security (formerly Area 1) will enforce the proper match of the sender’s display name and email address. Any variation from this strict requirement will raise a detection event. The reason of detection will be `Protected Name <NAME> should not appear as <non-configured email address>`.
diff --git a/src/content/partials/email-security/contact-support.mdx b/src/content/partials/email-security/contact-support.mdx
index b4a2c7c68ef7575..5378b3ab6111c21 100644
--- a/src/content/partials/email-security/contact-support.mdx
+++ b/src/content/partials/email-security/contact-support.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::caution[Access to Area 1]
 Beginning October 1, 2025, access and support for Email Security (formerly Area 1) will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
index fb9b79de16a89ea..5d3c830d646535b 100644
--- a/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/bcc-table-geographic-locations.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
 Select from the following BCC addresses to process email in the correct geographic location.
 
-| Host                                                                   | Location                | Note                                                                                                               |
+| Host                                        | Location                | Note                                                                                                               |
 | ---------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `<customer_name>@journaling.mxrecord.io`                               | US                      | Best option to ensure all email traffic processing happens US data centers.                                        |
-| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
-| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.        |
+| `<customer_name>@journaling.mailstream-eu-primary.mxrecord.io`         | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.           |
+| `<customer_name>@journaling.mailstream-eu1.mxrecord.io`                | EU                      | Best option to ensure all email traffic processing happens within the EU without backup to US data centers.      |
 | `<customer_name>@journaling.mailstream-bom.mxrecord.mx`                | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
-| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
+| `<customer_name>@journaling.mailstream-india-primary.mxrecord.mx`      | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                            |
+| `<customer_name>@journaling.mailstream-asia.mxrecord.mx`               | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.                                                            |
 | `<customer_name>@journaling.mailstream-syd.area1.cloudflare.net`       | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
 | `<customer_name>@journaling.mailstream-australia.area1.cloudflare.net` | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
diff --git a/src/content/partials/email-security/deployment/mx-deployment-values.mdx b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
index 6c51818a2f48130..7159d1c82e5849e 100644
--- a/src/content/partials/email-security/deployment/mx-deployment-values.mdx
+++ b/src/content/partials/email-security/deployment/mx-deployment-values.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | MX Priority | Host                             |
diff --git a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
index 0486462814a3d07..c4e31a82c6cc983 100644
--- a/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
+++ b/src/content/partials/email-security/deployment/mx-geographic-locations.mdx
@@ -1,17 +1,18 @@
 ---
 {}
+
 ---
 
 When configuring the Email Security (formerly Area 1) MX records, it is important to configure hosts with the correct MX priority. This will allow mail flows to the preferred hosts and fail over as needed.
 
 Choose from the following Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
 
-| Host                                                                                                                             | Location                | Note                                                                                                               |
-| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                              |
-| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.             |
-| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.                                           |
-| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                              |
-| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.        |
-| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                       |
-| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup. |
+| Host                                                                                                                             | Location                | Note                                                                                                                                                                                  |
+| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <un><li>`mailstream-central.mxrecord.mx`</li> <li>`mailstream-east.mxrecord.io`</li> <li>`mailstream-west.mxrecord.io`</li></un> | US                      | Best option to ensure all email traffic processing happens in the US.                                                                                                                 |
+| `mailstream-eu1.mxrecord.io`                                                                                                     | EU                      | Best option to ensure all email traffic processing happens in Germany, with backup to US data centers.                                                                              |
+| `mailstream-bom.mxrecord.mx`                                                                                                     | India                   | Best option to ensure all email traffic processing happens within India.
+| `mailstream-india-primary.mxrecord.mx`                                                                                           | India                   | Same as `mailstream-bom.mxrecord.mx`, with backup to US data centers.                                                                                                               |
+| `mailstream-asia.mxrecord.mx`                                                                                                    | India                   | Best option to ensure all email traffic processing happens in India, with Australia data centers as backup.
+| `mailstream-syd.area1.cloudflare.net`                                                                                            | Australia / New Zealand | Best option to ensure all email traffic processing happens within Australia.                                                                                                          |
+| `mailstream-australia-primary.area1.cloudflare.net`                                                                              | Australia / New Zealand | Best option to ensure all email traffic processing happens in Australia, with India and US data centers as backup.                                                                    |
diff --git a/src/content/partials/email-security/deployment/o365-gcc.mdx b/src/content/partials/email-security/deployment/o365-gcc.mdx
index 452dc5782964883..94afd5f4a9ae9d6 100644
--- a/src/content/partials/email-security/deployment/o365-gcc.mdx
+++ b/src/content/partials/email-security/deployment/o365-gcc.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
index 7e6a508dd4c5951..2de2cfae20b80ed 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-1-3-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create quarantine policies:
@@ -19,8 +20,9 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to request a message to be released from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to request a message to be released from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
index e797688ae2d418e..ffd9e7b6f9ee7a9 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-2-4-create-quarantine-policy.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create quarantine policies:
@@ -19,8 +20,9 @@ To create quarantine policies:
 7. Select **Next**.
 
 8. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-   - In **Select release action preference**, choose _Allow recipients to release a message from quarantine_.
-   - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+   * In **Select release action preference**, choose *Allow recipients to release a message from quarantine*.
+   * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
    ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-allow-message-release.png)
 
@@ -41,8 +43,9 @@ To create quarantine policies:
 16. Select **Next**.
 
 17. In **Recipient message access**, select **Set specific access (Advanced)**, and then:
-    - In **Select release action preference**, from the drop-down menu, choose _Allow recipients to request a message to be released from quarantine_.
-    - In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
+
+    * In **Select release action preference**, from the drop-down menu, choose *Allow recipients to request a message to be released from quarantine*.
+    * In **Select additional actions recipients can take on quarantined messages**, select the **Delete** and **Preview** checkboxes.
 
     ![Configure the Recipient message access as stated in the step above](~/assets/email-security/static/flexible-partial-images/o365-area1-mx/step8-request-message-release.png)
 
diff --git a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
index 8acc6ea1e36ac83..075e0dfe8e17426 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-configure-domain.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: quarantinePolicy
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 You first need to configure the domains you are onboarding on the Email Security (formerly Area 1) dashboard. To configure your domains:
 
@@ -11,9 +12,9 @@ You first need to configure the domains you are onboarding on the Email Security
 3. Go to **Email configuration** > **Domains & Routing** > **Domains**.
 4. Make sure each domain you are onboarding has been added.
 5. For each domain you are configuring, select **...** > **Edit**, and set the following options:
-   - **Domain** - `<YOUR_DOMAIN>`.
-   - **Configured as** - `MX Records`.
-   - **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
-   - **IP Restrictions** - Leave this field empty.
-   - **Outbound TLS** - `Forward all messages over TLS`.
-   - **Quarantine Policy** - {props.one}
+   * **Domain** - `<YOUR_DOMAIN>`.
+   * **Configured as** - `MX Records`.
+   * **Forwarding to** - This should match the expected MX record for each domain in your [Office 365 account](https://admin.microsoft.com/#/Domains/).
+   * **IP Restrictions** - Leave this field empty.
+   * **Outbound TLS** - `Forward all messages over TLS`.
+   * **Quarantine Policy** - {props.one}
diff --git a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
index 5ecfa3d112baa85..0f3c8996e8dba65 100644
--- a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
+++ b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx
@@ -1,9 +1,10 @@
 ---
 inputParameters: ruleName;;ruleWords;;doFollowing;;img;;ruleName2;;ruleWords2;;doFollowing2;;img2
+
 ---
 
-import { Image } from "astro:assets";
-import { GlossaryTooltip, Markdown } from "~/components";
+import { Image } from 'astro:assets';
+import { GlossaryTooltip, Markdown } from "~/components"
 
 To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Email Security:
 
@@ -14,15 +15,16 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 3. Select **Add a Rule** > **Create a new rule**.
 
 4. Set the following rule conditions:
-   - **Name**: _{props.one}_.
-   - **Apply this rule if**: _The message headers_ > _includes any of these words_.
-     - **Enter text**: `X-Area1Security-Disposition` > **Save**.
-     - **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
-   - **Apply this rule if**: Select **+** to add a second condition.
-   - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-   - **Do the following** - _{props.three}_.
 
-{/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
+   * **Name**: *{props.one}*.
+   * **Apply this rule if**: *The message headers* > *includes any of these words*.
+     * **Enter text**: `X-Area1Security-Disposition` > **Save**.
+     * **Enter words**: <code>{props.two}</code> > **Add** > **Save**.
+   * **Apply this rule if**: Select **+** to add a second condition.
+   * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+   * **Do the following** - *{props.three}*.
+
+ {/* todo <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.four}`} alt="set rule conditions" /> */}
 
 5. Select **Next**.
 
@@ -35,15 +37,16 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 9. Select **Add a Rule** > **Create a new rule**.
 
 10. Set the following rule conditions:
-    - **Name**: _{props.five}_.
-    - **Apply this rule if**: _The message headers_ > _includes any of these words_.
-      - **Enter text**: `X-Area1Security-Disposition` > **Save**.
-      - **Enter words**: _{props.six}_ > **Add** > **Save**.
-    - **Apply this rule if**: Select **+** to add a second condition.
-    - **And**: _The sender_ > _IP address is in any of these ranges or exactly matches_ > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
-    - **Do the following**: _{props.seven}_.
 
-{/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
+    * **Name**: *{props.five}*.
+    * **Apply this rule if**: *The message headers* > *includes any of these words*.
+      * **Enter text**: `X-Area1Security-Disposition` > **Save**.
+      * **Enter words**: *{props.six}* > **Add** > **Save**.
+    * **Apply this rule if**: Select **+** to add a second condition.
+    * **And**: *The sender* > *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/).
+    * **Do the following**: *{props.seven}*.
+
+ {/* todo   <Image src={`~/assets/email-security/static/flexible-partial-images/o365-area1-mx/${props.eight}`} alt="set rule conditions" /> */}
 
 11. Select **Next**.
 
@@ -51,4 +54,4 @@ To create the transport rules that will send emails with certain <GlossaryToolti
 
 13. Review your settings and select **Finish** > **Done**.
 
-14. Select the rule _{props.five}_ you have just created, and select **Enable**.
+14. Select the rule *{props.five}* you have just created, and select **Enable**.
diff --git a/src/content/partials/email-security/deployment/setup-api-overview.mdx b/src/content/partials/email-security/deployment/setup-api-overview.mdx
index 749c98c3bfc1b4a..42cb0c0bf4e1c36 100644
--- a/src/content/partials/email-security/deployment/setup-api-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-api-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Email Security after they have already reached a user's inbox.
@@ -12,18 +13,18 @@ Then, through on integrations with your email provider, Email Security can [retr
 
 When you choose API deployment, you get the following benefits:
 
-- Easy protection for complex email architectures, without requiring any change to mailflow operations.
-- Agentless deployment for Microsoft 365 and Gmail.
-- The initial email protection measures offered by your current email provider.
+* Easy protection for complex email architectures, without requiring any change to mailflow operations.
+* Agentless deployment for Microsoft 365 and Gmail.
+* The initial email protection measures offered by your current email provider.
 
 ## Limitations
 
 However, API deployment also has the following disadvantages:
 
-- Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
-- Email Security requires read and write access to mailboxes.
-- Requires API support from your email provider (does not typically support on-premise providers).
-- Your email provider may throttle API requests from Email Security.
-- Detection rates may be lower if multiple solutions exist.
-- Messages cannot be modified or quarantined.
-- Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
+* Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
+* Email Security requires read and write access to mailboxes.
+* Requires API support from your email provider (does not typically support on-premise providers).
+* Your email provider may throttle API requests from Email Security.
+* Detection rates may be lower if multiple solutions exist.
+* Messages cannot be modified or quarantined.
+* Certain URL rewrite schemes cannot be decoded (for example, Mimecast).
diff --git a/src/content/partials/email-security/deployment/setup-inline-overview.mdx b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
index 70fac3460c076fb..a7473c6318abaea 100644
--- a/src/content/partials/email-security/deployment/setup-inline-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-inline-overview.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 With an **Inline deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), Email Security evaluates email messages before they reach a user's inbox.
 
@@ -14,11 +15,11 @@ More technically, Email Security becomes a hop in the <GlossaryTooltip term="SMT
 
 When you choose an inline deployment, you get the following benefits:
 
-- Messages are processed and physically blocked before delivery to a user's mailbox.
-- Your deployment is simpler, because any complex processing can happen downstream and without modification.
-- Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
-- Email Security can offer high availability and adaptive message pooling.
-- You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
+* Messages are processed and physically blocked before delivery to a user's mailbox.
+* Your deployment is simpler, because any complex processing can happen downstream and without modification.
+* Email Security can [modify delivered messages](/email-security/email-configuration/email-policies/text-addons/), adding subject or body mark-ups.
+* Email Security can offer high availability and adaptive message pooling.
+* You can set up advanced handling downstream for non-quarantined messages with [added `X-headers`](/email-security/reference/dispositions-and-attributes/).
 
 ## Limitations
 
diff --git a/src/content/partials/email-security/deployment/setup-overview.mdx b/src/content/partials/email-security/deployment/setup-overview.mdx
index 272608e20f764f3..d8963b1ca171ef2 100644
--- a/src/content/partials/email-security/deployment/setup-overview.mdx
+++ b/src/content/partials/email-security/deployment/setup-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you configure Email Security (formerly Area 1) Email Security to protect your organization, you can choose between two main setup architectures: Inline and API.
diff --git a/src/content/partials/email-security/email-security-description.mdx b/src/content/partials/email-security/email-security-description.mdx
index a613aab3d39121a..f65277d146ce070 100644
--- a/src/content/partials/email-security/email-security-description.mdx
+++ b/src/content/partials/email-security/email-security-description.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 <GlossaryTooltip term="phishing">Phishing</GlossaryTooltip> is the root cause of upwards of 90% of breaches that lead to financial loss and brand damage. Email Security (formerly Area 1) is a cloud-native service that stops phishing attacks across all threat vectors either at the [edge](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/) or in the cloud.
 
diff --git a/src/content/partials/email-security/outbound-email.mdx b/src/content/partials/email-security/outbound-email.mdx
index b7cc2413e883e96..1ed881d40a0dd1b 100644
--- a/src/content/partials/email-security/outbound-email.mdx
+++ b/src/content/partials/email-security/outbound-email.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/email-security/rename-area1-to-ces.mdx b/src/content/partials/email-security/rename-area1-to-ces.mdx
index ab1890e42fc4e97..4e5b20b1df6b4ea 100644
--- a/src/content/partials/email-security/rename-area1-to-ces.mdx
+++ b/src/content/partials/email-security/rename-area1-to-ces.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Area 1 has been renamed]
diff --git a/src/content/partials/email-security/search.mdx b/src/content/partials/email-security/search.mdx
index 6e314af0ce256bd..2a9c170e7e24c0e 100644
--- a/src/content/partials/email-security/search.mdx
+++ b/src/content/partials/email-security/search.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 1. **Detections only** is enabled by default. This means that the system will only search through and display emails that Email Security (formerly Area 1) has marked with a detection <GlossaryTooltip term="disposition" link="/email-security/reference/dispositions-and-attributes/">disposition</GlossaryTooltip>. If you prefer to search through and view all emails that have been processed by Email Security, whether they are marked with a detection disposition or not, disable this option.
 2. The **All detections** drop-down menu allows you to refine your search by detection disposition. This menu will be disabled if **Detections only** is not selected.
 3. By default, the search results are limited to the previous 30 days. Select **Last 30 days** to change this setting.
 4. (Optional) You can download the results from your search in CSV format. The CSV file is capped at 1,000 rows.
 5. The system returns a list of emails that fit your search criteria, and will inform you if there are emails similar to the ones found. If Email Security finds emails similar to the ones returned by your query, select **Show** to display them. Otherwise, select **View** on the email you are interested in. This will show you more information about that particular email, such as:
-   - Disposition (if any)
-   - Email status (for example `Quarantined`)
-   - Sender details (for example, IP address)
+   * Disposition (if any)
+   * Email status (for example `Quarantined`)
+   * Sender details (for example, IP address)
diff --git a/src/content/partials/email-security/service-addresses.mdx b/src/content/partials/email-security/service-addresses.mdx
index 5440ee7231acb79..6e22907a82f13d1 100644
--- a/src/content/partials/email-security/service-addresses.mdx
+++ b/src/content/partials/email-security/service-addresses.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/email-security/sso-enforcement.mdx b/src/content/partials/email-security/sso-enforcement.mdx
index 8ff51749311a532..bf094a37f8a0fc8 100644
--- a/src/content/partials/email-security/sso-enforcement.mdx
+++ b/src/content/partials/email-security/sso-enforcement.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
-- **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
-- **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
-- **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
+* **None**: This setting allows each user to choose SSO, or username and password plus <GlossaryTooltip term="two-factor authentication (2FA)">2FA</GlossaryTooltip> (this is the recommended setting while testing SSO).
+* **Admin**: This setting will force only the administrator account to use SSO. The user that enables this setting will still be able to log in using username and password plus 2FA. This is a backup, so that your organization does not get locked out of the portal in emergencies.
+* **Non-Admin Only**: This option will require that all `Read only` and `Read & Write` users use SSO to access the portal. Admins will still have the option to use either SSO or username and password plus 2FA.
diff --git a/src/content/partials/fundamentals/account-audit-logs-definition.mdx b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
index 524d5179caa2fed..f8c6c30b76e700a 100644
--- a/src/content/partials/fundamentals/account-audit-logs-definition.mdx
+++ b/src/content/partials/fundamentals/account-audit-logs-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Audit logs summarize the history of changes made within your Cloudflare account. Audit logs include account level actions like login, as well as zone configuration changes.
@@ -8,6 +9,8 @@ Audit Logs are available on all plan types and are captured for both individual
 
 :::note
 
+
 Most beta features will not appear in audit logs until they are out of beta.
 
+
 :::
diff --git a/src/content/partials/fundamentals/account-manage-active-sessions.mdx b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
index 68aba8bba607b09..4be15fc6addf57f 100644
--- a/src/content/partials/fundamentals/account-manage-active-sessions.mdx
+++ b/src/content/partials/fundamentals/account-manage-active-sessions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 In the Cloudflare dashboard, you can view a list of active sessions associated with your email address.
@@ -10,8 +11,10 @@ If you notice any suspicious activity, you can also revoke any active sessions.
 
 :::note
 
+
 By default, the session timeout for the Cloudflare dashboard is 72 hours without any activity.
 
 Some customers can also enforce single-sign on (SSO) by [adding a Dashboard SSO application](/fundamentals/manage-members/dashboard-sso/).
 
+
 :::
diff --git a/src/content/partials/fundamentals/account-member-manage-limitation.mdx b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
index 67c9f962a22856f..9d7535b542de061 100644
--- a/src/content/partials/fundamentals/account-member-manage-limitation.mdx
+++ b/src/content/partials/fundamentals/account-member-manage-limitation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/user-profiles/verify-email-address/).
diff --git a/src/content/partials/fundamentals/api-change-api-key.mdx b/src/content/partials/fundamentals/api-change-api-key.mdx
index 06ec545d2f3cd2a..215b04ead3be1e3 100644
--- a/src/content/partials/fundamentals/api-change-api-key.mdx
+++ b/src/content/partials/fundamentals/api-change-api-key.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ If your API key might be compromised, change your API key:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **API Tokens**.
 3. In the **API Keys** section, find your key.
diff --git a/src/content/partials/fundamentals/api-combine-filters.mdx b/src/content/partials/fundamentals/api-combine-filters.mdx
index 01c8e615b939694..6e4a1b16a8df9cf 100644
--- a/src/content/partials/fundamentals/api-combine-filters.mdx
+++ b/src/content/partials/fundamentals/api-combine-filters.mdx
@@ -1,15 +1,18 @@
 ---
 {}
+
 ---
 
 Combine filters using `OR` and `AND` boolean logic:
 
-- `AND` takes precedence over `OR` in all expressions.
-- The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
-- The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
+* `AND` takes precedence over `OR` in all expressions.
+* The `OR` operator is defined using a comma `,` or the `OR` keyword surrounded by whitespace.
+* The `AND` operator is defined using a semicolon `;` or the `AND` keyword surrounded by whitespace.
 
   :::note
 
+
   Note that the semicolon is a reserved character in URLs ([RFC 1738](https://www.rfc-editor.org/rfc/rfc1738)) and should be percent-encoded as `%3B`.
 
+
   :::
diff --git a/src/content/partials/fundamentals/api-filter-operators.mdx b/src/content/partials/fundamentals/api-filter-operators.mdx
index 57f6d12acfe8282..fd3a372b4041816 100644
--- a/src/content/partials/fundamentals/api-filter-operators.mdx
+++ b/src/content/partials/fundamentals/api-filter-operators.mdx
@@ -1,14 +1,18 @@
 ---
 inputParameters: param1;;param2;;param3;;param4
+
 ---
 
-import { Markdown } from "~/components";
 
-| Operator | Name                     | Example                                  | Description                                                                                  | URL Encoded |
-| -------- | ------------------------ | ---------------------------------------- | -------------------------------------------------------------------------------------------- | ----------- |
-| `==`     | Equals                   | <code>{props.one}=={props.two}</code>    | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.           | `%3D%3D`    |
-| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code> | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>. | `!%3D`      |
-| `>`      | Greater than             | `dimension>1000`                         | Return results where a dimension is greater than `1000`.                                     | `%3E`       |
-| `<`      | Less than                | `dimension<1000`                         | Return results where a dimension is less than `1000`.                                        | `%3C`       |
-| `>=`     | Greater than or equal to | `dimension>=1000`                        | Return results where a dimension is greater than or equal to `1000`.                         | `%3E%3D`    |
-| `<=`     | Less than or equal to    | `dimension<=1000`                        | Return results where a dimension is less than or equal to `1000`.                            | `%3C%3D`    |
+
+import { Markdown } from "~/components"
+
+| Operator | Name                     | Example           | Description                                                          | URL Encoded |
+| -------- | ------------------------ | ----------------- | -------------------------------------------------------------------- | ----------- |
+| `==`     | Equals                   | <code>{props.one}=={props.two}</code>          | Return results where <code>{props.one}</code> is exactly <code>{props.two}</code>.                           | `%3D%3D`    |
+| `!=`     | Does not equal           | <code>{props.three}!={props.four}</code>         | Return results where <code>{props.three}</code> is different from <code>{props.four}</code>.                    | `!%3D`      |
+| `>`      | Greater than             | `dimension>1000`  | Return results where a dimension is greater than `1000`.             | `%3E`       |
+| `<`      | Less than                | `dimension<1000`  | Return results where a dimension is less than `1000`.                | `%3C`       |
+| `>=`     | Greater than or equal to | `dimension>=1000` | Return results where a dimension is greater than or equal to `1000`. | `%3E%3D`    |
+| `<=`     | Less than or equal to    | `dimension<=1000` | Return results where a dimension is less than or equal to `1000`.    | `%3C%3D`    |
+
diff --git a/src/content/partials/fundamentals/api-rate-limits.mdx b/src/content/partials/fundamentals/api-rate-limits.mdx
index 37822f640908916..09202c8b7845f04 100644
--- a/src/content/partials/fundamentals/api-rate-limits.mdx
+++ b/src/content/partials/fundamentals/api-rate-limits.mdx
@@ -6,16 +6,16 @@ params:
 import { AnchorHeading } from "~/components";
 
 {props.showHeading && (
-<AnchorHeading title="API token limits" depth={2} />
+	<AnchorHeading title="API token limits" depth={2} />
 )}
 
-| Type                              | Limit                               |
-| --------------------------------- | ----------------------------------- |
-| Client API per user/account token | 1200/5 minutes                      |
-| Client API per IP                 | 200/second                          |
-| GraphQL                           | Varies by query cost. Max 320/5 min |
-| User API token quota              | 50                                  |
-| Account API token quota           | 500                                 |
+| Type                    | Limit                               |
+| ----------------------- | ----------------------------------- |
+| Client API per user/account token     | 1200/5 minutes        |
+| Client API per IP       | 200/second                          |
+| GraphQL                 | Varies by query cost. Max 320/5 min |
+| User API token quota    | 50                                  |
+| Account API token quota | 500                                 |
 
 :::note
 The global rate limit for the Cloudflare API is 1,200 requests per five minute period per user, and applies cumulatively regardless of whether the request is made via the dashboard, API key, or API token.
diff --git a/src/content/partials/fundamentals/api-using-api.mdx b/src/content/partials/fundamentals/api-using-api.mdx
index e5ae32ba9e53c09..b1ca2470c79d58c 100644
--- a/src/content/partials/fundamentals/api-using-api.mdx
+++ b/src/content/partials/fundamentals/api-using-api.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 Using the Cloudflare API requires authentication so that Cloudflare knows who is making requests and what permissions you have. [Create an API token](/fundamentals/api/get-started/create-token/) to grant access to the API to perform actions.
 
 :::note
 
+
 You can also authenticate with [API keys](/fundamentals/api/get-started/keys/), but these keys have [several limitations](/fundamentals/api/get-started/keys/#limitations) that make them less secure than API tokens. Whenever possible, use API tokens to interact with the Cloudflare API.
 
+
 :::
diff --git a/src/content/partials/fundamentals/audit-log-api.mdx b/src/content/partials/fundamentals/audit-log-api.mdx
index 6d53ba9530aa6e7..ce209127d72ff3f 100644
--- a/src/content/partials/fundamentals/audit-log-api.mdx
+++ b/src/content/partials/fundamentals/audit-log-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To get audit logs from the Cloudflare API, send a [GET request](/api/resources/audit_logs/methods/list/).
diff --git a/src/content/partials/fundamentals/create-account-best-practices.mdx b/src/content/partials/fundamentals/create-account-best-practices.mdx
index efc376dfbf7bcdb..8a878be2c868221 100644
--- a/src/content/partials/fundamentals/create-account-best-practices.mdx
+++ b/src/content/partials/fundamentals/create-account-best-practices.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you are creating an account for your team or a business, we recommend choosing an email alias or distribution list for your **Email**, such as `cloudflare@example.com`.
diff --git a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
index 24617a79253e1c1..5c9104ac3a59f7b 100644
--- a/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
+++ b/src/content/partials/fundamentals/cybersafe-cipa-subcategories.mdx
@@ -1,35 +1,36 @@
 ---
 {}
+
 ---
 
 Cloudflare’s recommended CIPA rule blocks the following content subcategories:
 
-- Adult Themes
-- Alcohol
-- Anonymizer
-- Brand Embedding
-- Child Abuse
-- Command and Control & Botnet
-- Cryptomining
-- DGA Domains
-- DNS Tunneling
-- Drugs
-- Gambling
-- Hacking
-- Malware
-- Militancy, Hate & Extremism
-- Nudity
-- P2P
-- Phishing
-- Pornography
-- Private IP Address
-- Profanity
-- Questionable Activities
-- School Cheating
-- Spam
-- Spyware
-- Tobacco
-- Violence
-- Weapons
+* Adult Themes
+* Alcohol
+* Anonymizer
+* Brand Embedding
+* Child Abuse
+* Command and Control & Botnet
+* Cryptomining
+* DGA Domains
+* DNS Tunneling
+* Drugs
+* Gambling
+* Hacking
+* Malware
+* Militancy, Hate & Extremism
+* Nudity
+* P2P
+* Phishing
+* Pornography
+* Private IP Address
+* Profanity
+* Questionable Activities
+* School Cheating
+* Spam
+* Spyware
+* Tobacco
+* Violence
+* Weapons
 
 Review the [domain categories](/cloudflare-one/traffic-policies/domain-categories/) for more information.
diff --git a/src/content/partials/fundamentals/cybersafe-configuration.mdx b/src/content/partials/fundamentals/cybersafe-configuration.mdx
index 97c5c85cf1bc3fe..e8654c6c41b1e83 100644
--- a/src/content/partials/fundamentals/cybersafe-configuration.mdx
+++ b/src/content/partials/fundamentals/cybersafe-configuration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To facilitate compliance with CIPA requirements, administrators can [enable a single filtering policy option](/cloudflare-one/traffic-policies/dns-policies/common-policies/#turn-on-cipa-filter). This includes applying the required filter categories to block access to unwanted or harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-description.mdx b/src/content/partials/fundamentals/cybersafe-description.mdx
index a3f8e1c475bbb46..431d708d46e714b 100644
--- a/src/content/partials/fundamentals/cybersafe-description.mdx
+++ b/src/content/partials/fundamentals/cybersafe-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/sites/default/files/childrens_internet_protection_act_cipa.pdf) is a federal law enacted by the United States Congress to address concerns about children's access to inappropriate or harmful content over the Internet. CIPA requires K-12 schools and libraries that receive certain federal funding to implement Internet safety measures to protect minors from harmful online content.
diff --git a/src/content/partials/fundamentals/cybersafe-requirements.mdx b/src/content/partials/fundamentals/cybersafe-requirements.mdx
index e6be7dae9a66a9c..833e37f87f33941 100644
--- a/src/content/partials/fundamentals/cybersafe-requirements.mdx
+++ b/src/content/partials/fundamentals/cybersafe-requirements.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 CIPA mandates that K-12 schools and libraries adopt Internet safety policies that include measures to block or filter access to specific categories of content. These categories encompass a wide range of topics that could be harmful or inappropriate for minors. Compliance with these requirements helps ensure that students' online experiences are safer and more secure.
diff --git a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
index 9973f9748eda869..2e2f41f8016c234 100644
--- a/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
+++ b/src/content/partials/fundamentals/cybersafe-school-eligibility.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 This program is only available to eligible school districts. To be eligible, Project Cybersafe School participants must be:
 
-- K-12 public school districts located in the United States.
-- Up to 2,500 students in the district.
+* K-12 public school districts located in the United States.
+* Up to 2,500 students in the district.
diff --git a/src/content/partials/fundamentals/idp-group-deprecation.mdx b/src/content/partials/fundamentals/idp-group-deprecation.mdx
index baaae6c04591975..05821b931796237 100644
--- a/src/content/partials/fundamentals/idp-group-deprecation.mdx
+++ b/src/content/partials/fundamentals/idp-group-deprecation.mdx
@@ -1,7 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 **Important Update:** Cloudflare now supports native User Groups for enhanced access control. This new feature replaces the previous method of directly assigning Cloudflare roles based on IdP group mappings (identified by the pattern `CF-<accountID> - <Role Name>`), which is deprecated as of June 2nd, 2025. SCIM Virtual Groups will reach end-of-life on December 2, 2025. Update your SCIM configurations using the instructions below to utilize User Groups for seamless provisioning.
 :::
+
+
+
+
diff --git a/src/content/partials/fundamentals/lists-import-notes.mdx b/src/content/partials/fundamentals/lists-import-notes.mdx
index 1325dd37dc9b03c..7b084592eb99561 100644
--- a/src/content/partials/fundamentals/lists-import-notes.mdx
+++ b/src/content/partials/fundamentals/lists-import-notes.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 Cloudflare will apply the following rules when you add items to an existing list (either manually or via CSV file):
 
-- Do not remove any existing list items before updating/adding items.
-- Update items that were already in the list.
-- Add items that were not present in the list.
+* Do not remove any existing list items before updating/adding items.
+* Update items that were already in the list.
+* Add items that were not present in the list.
diff --git a/src/content/partials/fundamentals/new-token-warning.mdx b/src/content/partials/fundamentals/new-token-warning.mdx
index 794191bf0e51bba..ebba0665c1f6103 100644
--- a/src/content/partials/fundamentals/new-token-warning.mdx
+++ b/src/content/partials/fundamentals/new-token-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Warning]
 
+
 The token secret is **only shown once**. Do not store the secret in plaintext where others can access it. Anyone with this token can perform the authorized actions against the resources that the token has access to.
 
+
 :::
diff --git a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
index 707af55fc2d4d48..8339d260cd8f0fd 100644
--- a/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
+++ b/src/content/partials/fundamentals/pseudo-ipv4-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If **Pseudo IPv4** is set to `Overwrite Headers` - Cloudflare overwrites the existing `Cf-Connecting-IP` and `X-Forwarded-For` headers with a pseudo IPv4 address while preserving the real IPv6 address in `CF-Connecting-IPv6` header.
diff --git a/src/content/partials/fundamentals/revoke-active-sessions.mdx b/src/content/partials/fundamentals/revoke-active-sessions.mdx
index fc8a9e0c4c296c9..07d956a61afdf20 100644
--- a/src/content/partials/fundamentals/revoke-active-sessions.mdx
+++ b/src/content/partials/fundamentals/revoke-active-sessions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,7 +11,7 @@ To revoke a session:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Go to **My Profile** > **Sessions**.
 3. On a specific section, click **Revoke**.
diff --git a/src/content/partials/fundamentals/ubb-recommendation.mdx b/src/content/partials/fundamentals/ubb-recommendation.mdx
index d05b58438eb70b2..ec055f77df645ca 100644
--- a/src/content/partials/fundamentals/ubb-recommendation.mdx
+++ b/src/content/partials/fundamentals/ubb-recommendation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,15 +11,16 @@ To set up those notifications:
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-   <DashButton url="/?to=/:account/notifications" />
+      <DashButton url="/?to=/:account/notifications" />
 
 2. On **Alert Type** of **Usage Based Billing**, click **Select**.
 
 3. Fill out the following information:
-   - **Name**
-   - **Product**
-   - **Notification limit** (exact metric will vary based on product)
-   - **Notification email**
+
+   * **Name**
+   * **Product**
+   * **Notification limit** (exact metric will vary based on product)
+   * **Notification email**
 
    :::note
    Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/).
diff --git a/src/content/partials/fundamentals/user-permissions-table.mdx b/src/content/partials/fundamentals/user-permissions-table.mdx
index 0a4067fc83f026d..5bcacf794820b2f 100644
--- a/src/content/partials/fundamentals/user-permissions-table.mdx
+++ b/src/content/partials/fundamentals/user-permissions-table.mdx
@@ -1,14 +1,15 @@
 ---
 inputParameters: editWord
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
-| Name                     | Description                                                                                  |
-| ------------------------ | -------------------------------------------------------------------------------------------- |
-| API Tokens Read          | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).         |
-| API Tokens {props.one}   | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).        |
-| Memberships Read         | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
-| Memberships {props.one}  | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
-| User Details Read        | Grants read access to user details.                                                          |
-| User Details {props.one} | Grants write access to user details.                                                         |
+| Name              | Description                                                                                        |
+| ----------------- | -------------------------------------------------------------------------------------------------- |
+| API Tokens Read   | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/).               |
+| API Tokens {props.one}     | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/).              |
+| Memberships Read  | Grants read access to a user's [account memberships](/fundamentals/manage-members/manage/).  |
+| Memberships {props.one}    | Grants write access to a user's [account memberships](/fundamentals/manage-members/manage/). |
+| User Details Read | Grants read access to user details.                                                                |
+| User Details {props.one}   | Grants write access to user details.                                                               |
diff --git a/src/content/partials/fundamentals/user-profiles.mdx b/src/content/partials/fundamentals/user-profiles.mdx
index 5f074fa4484f104..95d7406967bb114 100644
--- a/src/content/partials/fundamentals/user-profiles.mdx
+++ b/src/content/partials/fundamentals/user-profiles.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/user-profiles/customize-account/#notifications) and [Language preferences](/fundamentals/user-profiles/customize-account/#language).
 
-To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
+To access your profile, select the user icon and then **My Profile** from any page within the [Cloudflare dashboard](https://dash.cloudflare.com).
\ No newline at end of file
diff --git a/src/content/partials/fundamentals/view-audit-log.mdx b/src/content/partials/fundamentals/view-audit-log.mdx
index ea0694e788fe9fc..34f479029436066 100644
--- a/src/content/partials/fundamentals/view-audit-log.mdx
+++ b/src/content/partials/fundamentals/view-audit-log.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -14,6 +15,8 @@ You can search these audit logs by user email or domain and filter by date range
 
 :::note
 
+
 Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Logpush](/logs/logpush/) to make sure Audit Logs are always available and stored externally.
 
+
 :::
diff --git a/src/content/partials/fundamentals/what-is-cloudflare.mdx b/src/content/partials/fundamentals/what-is-cloudflare.mdx
index 7321651a4cf4000..6db16b67782d1fc 100644
--- a/src/content/partials/fundamentals/what-is-cloudflare.mdx
+++ b/src/content/partials/fundamentals/what-is-cloudflare.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Stream } from "~/components";
+import { Stream } from "~/components"
 
 Cloudflare is one of the world's largest [connectivity cloud networks](https://blog.cloudflare.com/welcome-to-connectivity-cloud). Today, anyone with an Internet presence can have faster and more secure websites and applications thanks to Cloudflare. This includes bloggers, businesses, and even non-profits.
 
diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
index 7f8df8ff66b23e8..17b0e04547941b8 100644
--- a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
+++ b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) is occurring. No other error codes will trigger a zero-downtime failover operation.
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
index 94ebfc3d69ff887..a0936f417ad77a4 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-binding.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
@@ -29,7 +30,9 @@ Specifically:
 - The binding must be [a valid JavaScript variable name](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#variables). For example, `binding = "hyperdrive"` or `binding = "productionDB"` would both be valid names for the binding.
 - Your binding is available in your Worker at `env.<BINDING_NAME>`.
 
-If you wish to use a local database during development, you can add a `localConnectionString` to your Hyperdrive configuration with the connection string of your database:
+
+If you wish to use a local database during development, you can add a `localConnectionString` to your  Hyperdrive configuration with the connection string of your database:
+
 
 <WranglerConfig>
 
@@ -51,4 +54,4 @@ If you wish to use a local database during development, you can add a `localConn
 
 Learn more about setting up [Hyperdrive for local development](/hyperdrive/configuration/local-development/).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
index 55f58eb3fdaebda..2bccc59303de979 100644
--- a/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
+++ b/src/content/partials/hyperdrive/create-hyperdrive-config.mdx
@@ -2,14 +2,7 @@
 {}
 ---
 
-import {
-	DashButton,
-	WranglerConfig,
-	Render,
-	Tabs,
-	TabItem,
-	Steps,
-} from "~/components";
+import { DashButton, WranglerConfig, Render, Tabs, TabItem, Steps } from "~/components";
 
 To configure Hyperdrive, you will need:
 
diff --git a/src/content/partials/hyperdrive/pooling-mode.mdx b/src/content/partials/hyperdrive/pooling-mode.mdx
index ca988038c32fd15..a06f46f412dcfe7 100644
--- a/src/content/partials/hyperdrive/pooling-mode.mdx
+++ b/src/content/partials/hyperdrive/pooling-mode.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool.
diff --git a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
index f4895b5eecb79bb..b1275de22aeb7e2 100644
--- a/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
+++ b/src/content/partials/hyperdrive/use-postgres-js-to-make-query.mdx
@@ -37,7 +37,7 @@ export default {
 			// If you are not using array types in your Postgres schema, disable `fetch_types` to avoid an additional round-trip (unnecessary latency)
 			fetch_types: false,
 
-			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.
+			// This is set to true by default, but certain query generators such as Kysely or queries using sql.unsafe() will set this to false. Hyperdrive will not cache prepared statements when this option is set to false and will require additional round-trips.  
 			prepare: true,
 		});
 
diff --git a/src/content/partials/learning-paths/cache-basic-diagram.mdx b/src/content/partials/learning-paths/cache-basic-diagram.mdx
index c44a888cabcaa1e..6555ff5ad8fcf75 100644
--- a/src/content/partials/learning-paths/cache-basic-diagram.mdx
+++ b/src/content/partials/learning-paths/cache-basic-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/learning-paths/cache-optimization.mdx b/src/content/partials/learning-paths/cache-optimization.mdx
index 48c74235eb911f9..890676e0f865216 100644
--- a/src/content/partials/learning-paths/cache-optimization.mdx
+++ b/src/content/partials/learning-paths/cache-optimization.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 A few ways to optimize Cloudflare caching include:
 
-- Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
-- Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
-- Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
+* Creating [cache rules](/cache/how-to/cache-rules/) to customize the cache properties of specific HTTP requests.
+* Enabling the [Tiered Cache](/cache/how-to/tiered-cache/) feature, which dramatically increases cache hit ratios.
+* Reviewing our other various [configuration options](/cache/get-started/), which may vary based on your plan and application setup.
diff --git a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
index 6dba0749cadcf88..f15999e994d4aec 100644
--- a/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-additional-resources.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Related content**
@@ -9,4 +10,4 @@ For additional resources on the China Network, refer to the following resources:
     - [Cloudflare China Network](/china-network/)
     - [CDN Global Acceleration (formerly China Express)](/china-network/concepts/global-acceleration/)
     - [Internet Content Provider (ICP)](/china-network/concepts/icp/)
-    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
+    - [Authoritative DNS in mainland China](/china-network/concepts/china-dns/)
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/china-network-overview-navigation.mdx b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
index 6e6fee7c6c5dfbd..5e5f0c651602e6f 100644
--- a/src/content/partials/learning-paths/china-network-overview-navigation.mdx
+++ b/src/content/partials/learning-paths/china-network-overview-navigation.mdx
@@ -1,19 +1,20 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: How to speed up your web traffic inside mainland China"
-		description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
-		href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
-		description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
-		href="/learning-paths/china-network-overview/series/china-express-overview-2/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: How to speed up your web traffic inside mainland China"
+          description="This video discusses the main features of Cloudflare's China Network, including how the China Network works, improving availability and response times with caching, in-country China name servers, and compliance with ICP regulations."
+          href="/learning-paths/china-network-overview/series/china-network-main-features-1/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 2: How to accelerate dynamic traffic outside of mainland China"
+          description="This video discusses Cloudflare's CDN Global Acceleration (formerly China Express), including solutions for high latency on dynamic content, accelerating API calls, accessing Cloudflare One services like the Cloudflare One Client and Cloudflare WAN from within mainland China, and securely connecting private enterprise networks."
+          href="/learning-paths/china-network-overview/series/china-express-overview-2/"
+        />              
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
index b825a923b79a986..80b90de36b0e2f6 100644
--- a/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
+++ b/src/content/partials/learning-paths/cloudflare-tunnels-origin-description.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) connects your resources to Cloudflare without a publicly routable IP address, by creating an outbound-only connections to Cloudflare’s global network.
 
-- **Security**: Very secure.
-- **Availability**: All customers.
-- **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
+* **Security**: Very secure.
+* **Availability**: All customers.
+* **Challenges**: Requires installing the `cloudflared` daemon on origin server or virtual machine.
diff --git a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
index 95cf4f8cf529595..7b1ca7fcfce93d8 100644
--- a/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
+++ b/src/content/partials/learning-paths/ddos-definition-and-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A distributed denial-of-service (DDoS) attack is where a large number of computers or devices, usually controlled by a single attacker, attempt to access a website or online service all at once. This flood of traffic can overwhelm the website's origin servers, causing the site to slow down or even crash.
@@ -17,4 +18,4 @@ sequenceDiagram;
     Origin Server-->>User: Unable to respond to user requests
 ```
 
-<br />
+<br/>
diff --git a/src/content/partials/learning-paths/email-record-origin-ip.mdx b/src/content/partials/learning-paths/email-record-origin-ip.mdx
index 5b5f2c45e1b9e18..94b82b3791865f7 100644
--- a/src/content/partials/learning-paths/email-record-origin-ip.mdx
+++ b/src/content/partials/learning-paths/email-record-origin-ip.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If possible, do not host a mail service on the same server as the web resource you want to protect, since emails sent to non-existent addresses get bounced back to the attacker and reveal the mail server IP address.
diff --git a/src/content/partials/learning-paths/r2-series-navigation.mdx b/src/content/partials/learning-paths/r2-series-navigation.mdx
index 612ab4b973072ca..fdf03a46c5a8df9 100644
--- a/src/content/partials/learning-paths/r2-series-navigation.mdx
+++ b/src/content/partials/learning-paths/r2-series-navigation.mdx
@@ -1,33 +1,34 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Getting started with R2"
-		description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
-		href="/learning-paths/r2-intro/series/r2-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: Public buckets"
-		description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
-		href="/learning-paths/r2-intro/series/r2-2/"
-	/>
-	<LinkCard
-		title="Watch Episode 3: S3 API compatibility"
-		description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
-		href="/learning-paths/r2-intro/series/r2-3/"
-	/>
-	<LinkCard
-		title="Watch Episode 4: Migrating your bucket data"
-		description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
-		href="/learning-paths/r2-intro/series/r2-4/"
-	/>
-	<LinkCard
-		title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
-		description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
-		href="/learning-paths/r2-intro/series/r2-5/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Getting started with R2"
+          description="In this video, you'll learn how to use Cloudflare R2 to store and manage data with no egress fees, supporting use cases like media, web assets, backups, and static site hosting."
+          href="/learning-paths/r2-intro/series/r2-1/"
+        />          
+      <LinkCard
+          title="Watch Episode 2: Public buckets"
+          description="This video outlines how to configure public buckets in R2, which are private by default, to enable public Internet access. It presents two methods for setting up public access: using a custom domain or a Cloudflare managed subdomain."
+          href="/learning-paths/r2-intro/series/r2-2/"
+        />    
+      <LinkCard
+          title="Watch Episode 3: S3 API compatibility"
+          description="In this video, you'll learn how to use S3 API commands and tools with R2, set up and configure R2 for S3 API compatibility, and integrate R2 into your existing workflows with minimal changes."
+          href="/learning-paths/r2-intro/series/r2-3/"
+        />    
+      <LinkCard
+          title="Watch Episode 4: Migrating your bucket data"
+          description="In this video, you will learn how to use Cloudflare R2's data migration tools to transfer data from other cloud providers such as Amazon S3 and Google Cloud Storage to R2."
+          href="/learning-paths/r2-intro/series/r2-4/"
+        />    
+      <LinkCard
+          title="Watch Episode 5: Accessing your bucket from Cloudflare Workers"
+          description="In this video, you will build a serverless file API using Cloudflare Workers and R2 by setting up a project, securing uploads, enabling caching, and deploying the application."
+          href="/learning-paths/r2-intro/series/r2-5/"
+        />                                    
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/sase-series-navigation.mdx b/src/content/partials/learning-paths/sase-series-navigation.mdx
index 67412cf58413313..c9ac5dace4ee296 100644
--- a/src/content/partials/learning-paths/sase-series-navigation.mdx
+++ b/src/content/partials/learning-paths/sase-series-navigation.mdx
@@ -1,38 +1,40 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: The evolution of corporate networks"
-		description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
-		href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 2: Stop hosting your own VPN service"
-		description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
-		href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 3: Secure remote access to your critical infrastructure"
-		description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
-		href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 4: Connect and secure from any network to anywhere"
-		description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: The evolution of corporate networks"
+          description="In this video, we provide a Cloudflare SASE platform overview and how it has been designed to revolutionize the corporate network."
+          href="/learning-paths/sase-overview-course/series/evolution-corporate-networks-1/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 2: Stop hosting your own VPN service"
+          description="In this video, we discuss the Cloudflare SASE platform and how it can replace your traditional VPN appliances."
+          href="/learning-paths/sase-overview-course/series/stop-hosting-own-vpn-service-2/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 3: Secure remote access to your critical infrastructure"
+          description="In this video, learn how Cloudflare's SASE platform leverages a modern ZTNA service to implement zero trust principles for accessing your critical infrastructure."
+          href="/learning-paths/sase-overview-course/series/secure-remote-access-to-critical-infrastructure-3/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 4: Connect and secure from any network to anywhere"
+          description="In this video, we discuss how to connect any network to Cloudflare to any other network and the Internet. Learn how this improves security and performance for your networks and applications. 
   "
-		href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
-	/>
-
-	<LinkCard
-		title="Watch Episode 5: Protect your users from Internet risks"
-		description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
-		href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
-	/>
-</CardGrid>
+          href="/learning-paths/sase-overview-course/series/connect-secure-from-any-network-to-anywhere-4/"
+        />
+        
+      <LinkCard
+          title="Watch Episode 5: Protect your users from Internet risks"
+          description="In this video, we will explore how Cloudflare's Secure Web Gateway (SWG) helps keep users and devices safe by filtering and inspecting Internet traffic in real time."
+          href="/learning-paths/sase-overview-course/series/protect-users-from-internet-risks-5/"
+      />                           
+        
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/warp-series-navigation.mdx b/src/content/partials/learning-paths/warp-series-navigation.mdx
index af1eed7e2a23691..30d3c3c2090ec52 100644
--- a/src/content/partials/learning-paths/warp-series-navigation.mdx
+++ b/src/content/partials/learning-paths/warp-series-navigation.mdx
@@ -1,18 +1,19 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
-		description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
-		href="/learning-paths/warp-overview-course/series/warp-basics-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: WARP diagnostic logs"
-		description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
-		href="/learning-paths/warp-overview-course/series/warp-basics-2/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Understand and troubleshoot Cloudflare WARP"
+          description="In this episode, we explain the core features of the Cloudflare WARP client and how to troubleshoot common issues."
+          href="/learning-paths/warp-overview-course/series/warp-basics-1/"
+        />              
+      <LinkCard
+          title="Watch Episode 2: WARP diagnostic logs"
+          description="In this episode, we explain how to troubleshoot Cloudflare WARP by analyzing diagnostic logs and understand how the client connects in different modes."
+          href="/learning-paths/warp-overview-course/series/warp-basics-2/"
+        />                   
+    </CardGrid>
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/workflows-series-navigation.mdx b/src/content/partials/learning-paths/workflows-series-navigation.mdx
index f037d68638048ed..3aef6a36002ba88 100644
--- a/src/content/partials/learning-paths/workflows-series-navigation.mdx
+++ b/src/content/partials/learning-paths/workflows-series-navigation.mdx
@@ -1,23 +1,24 @@
 ---
 {}
+
 ---
 
 import { CardGrid, LinkCard, Card } from "~/components";
 
-<CardGrid>
-	<LinkCard
-		title="Watch Episode 1: Understand Cloudflare Workflows"
-		description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
-		href="/learning-paths/workflows-course/series/workflows-1/"
-	/>
-	<LinkCard
-		title="Watch Episode 2: Monitor and batch your website data"
-		description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
-		href="/learning-paths/workflows-course/series/workflows-2/"
-	/>
-	<LinkCard
-		title="Watch Episode 3: Use cron triggers to develop time-aware applications"
-		description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
-		href="/learning-paths/workflows-course/series/workflows-3/"
-	/>
-</CardGrid>
+ <CardGrid>
+      <LinkCard
+          title="Watch Episode 1: Understand Cloudflare Workflows"
+          description="In this episode, we introduce Cloudflare Workflows, which provides durable execution capabilities, allowing developers to create reliable, repeatable workflows that run in the background."
+          href="/learning-paths/workflows-course/series/workflows-1/"
+        />          
+      <LinkCard
+          title="Watch Episode 2: Monitor and batch your website data"
+          description="In this episode, we describe how Workflows can be used to process batches of data, ensuring each item in the batch goes through a defined process with reliable execution."
+          href="/learning-paths/workflows-course/series/workflows-2/"
+        />    
+      <LinkCard
+          title="Watch Episode 3: Use cron triggers to develop time-aware applications"
+          description="In this episode, we review Workflows ability to explicitly schedule tasks using cron triggers and pause execution with `step.sleep` allows developers to build sophisticated, time-aware applications."
+          href="/learning-paths/workflows-course/series/workflows-3/"
+        />                          
+    </CardGrid>
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
index 1432141f867394c..634c2666bff6d5b 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-restricted-users.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Restrict access for users included in an <GlossaryTooltip term="identity provider">identity provider (IdP)</GlossaryTooltip> user group for risky users. This policy ensures your security team can restrict traffic for users of whom malicious or suspicious activity was detected.
diff --git a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
index 39d1803880c83b2..060cde6c1160533 100644
--- a/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
+++ b/src/content/partials/learning-paths/zero-trust/blocklist-security-categories.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Block [security categories](/cloudflare-one/traffic-policies/domain-categories/#security-categories), such as **Command and Control & Botnet** and **Malware**, based on Cloudflare's threat intelligence.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
index 0a419a55b8b121b..b9a22f0fb157e40 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The Cloudflare One Client (known as the Cloudflare One Agent in mobile app stores) encrypts designated traffic from a user's device to Cloudflare's global network. In this learning path, we will first define all of your parameters and deployment rules, and then we will install and connect the client. If you prefer to start the client download now, refer to [Download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/).
diff --git a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
index 01f20205751345a..087954988839621 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-device-agent-objectives.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-- Define which users can connect devices to your Zero Trust instance.
-- Configure global and device-specific settings for the Cloudflare One Client.
-- Route user traffic through Cloudflare Gateway.
-- Route domains to a private DNS server, if required.
+* Define which users can connect devices to your Zero Trust instance.
+* Configure global and device-specific settings for the Cloudflare One Client.
+* Route user traffic through Cloudflare Gateway.
+* Route domains to a private DNS server, if required.
diff --git a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
index f358209dc42676a..21e92853d18e27b 100644
--- a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
+++ b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render} from "~/components"
 
 An <GlossaryTooltip term="identity provider" link="https://www.cloudflare.com/learning/access-management/what-is-an-identity-provider/">identity provider (IdP)</GlossaryTooltip> stores and manages users' digital identities. You can integrate your existing identity provider with Cloudflare Zero Trust in order to manage user access to your private network. This requires configuration both in Cloudflare and with the identity provider itself.
 
diff --git a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
index 5317428531592d0..6af7493ea8d2e78 100644
--- a/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/connect-devices-objectives.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Manually deploy the Cloudflare One Client on a test device.
-- Create an automated script to use with your organization's managed deployment tool.
-- View user traffic in Zero Trust.
+* Manually deploy the Cloudflare One Client on a test device.
+* Create an automated script to use with your organization's managed deployment tool.
+* View user traffic in Zero Trust.
diff --git a/src/content/partials/learning-paths/zero-trust/create-list.mdx b/src/content/partials/learning-paths/zero-trust/create-list.mdx
index db39846de4a243f..f5cc8a1e77768f5 100644
--- a/src/content/partials/learning-paths/zero-trust/create-list.mdx
+++ b/src/content/partials/learning-paths/zero-trust/create-list.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Gateway supports creating [lists](/cloudflare-one/reusable-components/lists/) of IPs, hostnames, or other entries to reference in your policies.
 
diff --git a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
index d1c2be740c04bb1..5f2f956a234b5a0 100644
--- a/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/device-enrollment-permissions.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Device enrollment permissions determine which users can connect new devices to your organization's Cloudflare Zero Trust instance. Once the user registers their device, the Cloudflare One Client will store their identity token and use it to authenticate to services in your private network.
 
diff --git a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
index af96e5d35431904..d7a5d2a680983d6 100644
--- a/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
+++ b/src/content/partials/learning-paths/zero-trust/email-dispositions.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
-| Disposition | Description                                                                                                                                                                                                                                                                                                                                                                                                                             | Recommendation                                                             |     |
-| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --- |
-| MALICIOUS   | Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                                                                                                                                                                                                                                                                                           | Block                                                                      |     |
-| SUSPICIOUS  | Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                                                                                                                                                                                                                                                                                                                    | Research these messages internally to evaluate legitimacy.                 |     |
-| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |     |
-| SPAM        | Traffic associated with non-malicious, commercial campaigns.                                                                                                                                                                                                                                                                                                                                                                            | Route to existing Spam quarantine folder.                                  |     |
-| BULK        | Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.                                                                                                                                                                                                              | Monitor or tag                                                             |     |
+| Disposition | Description                                                                                                                                                                                  | Recommendation                                                             |   |
+|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---|
+| MALICIOUS   |                                 Traffic invoked multiple phishing verdict triggers, met thresholds for bad behavior, and is associated with active campaigns.                                |                                    Block                                   |   |
+| SUSPICIOUS  |                                             Traffic associated with phishing campaigns (and is under further analysis by our automated systems).                                             |         Research these messages internally to evaluate legitimacy.         |   |
+| SPOOF       | Traffic associated with phishing campaigns that is either non-compliant with your email authentication policies ([SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)), or have mismatching Envelope From and Header From values. | Block after investigating (can be triggered by third-party mail services). |   |
+| SPAM        |                                                                 Traffic associated with non-malicious, commercial campaigns.                                                                 |                  Route to existing Spam quarantine folder.                 |   |
+| BULK        |       Traffic associated with [Graymail](https://en.wikipedia.org/wiki/Graymail), that falls in between the definitions of SPAM and SUSPICIOUS. For example, a marketing email that intentionally obscures its unsubscribe link.       |                               Monitor or tag                               |   |
\ No newline at end of file
diff --git a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
index 8a8dcfab6f7c924..e6800e57f7aafd3 100644
--- a/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
+++ b/src/content/partials/learning-paths/zero-trust/enable-proxy-intro.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 With Cloudflare Gateway, you can log and filter DNS, network, and HTTP traffic from devices running the Cloudflare One Client. This includes traffic to the public Internet and traffic directed to your private network. DNS filtering is enabled by default since the Cloudflare One Client sends DNS queries to Cloudflare's public DNS resolver, [1.1.1.1](/1.1.1.1/). To enable network and HTTP filtering, you will need to allow Cloudflare Gateway to proxy that traffic.
diff --git a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
index 4c1e0192bd1e400..fd8de62a9baadd6 100644
--- a/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
+++ b/src/content/partials/learning-paths/zero-trust/initial-setup-objectives.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Set up a Cloudflare account.
-- Create a Zero Trust organization to manage your devices and policies.
-- Configure an identity provider (IdP) for user authentication.
+* Set up a Cloudflare account.
+* Create a Zero Trust organization to manage your devices and policies.
+* Configure an identity provider (IdP) for user authentication.
diff --git a/src/content/partials/learning-paths/zero-trust/install-agent.mdx b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
index c0b8798b2485485..50221f53efc84d9 100644
--- a/src/content/partials/learning-paths/zero-trust/install-agent.mdx
+++ b/src/content/partials/learning-paths/zero-trust/install-agent.mdx
@@ -1,32 +1,32 @@
 ---
 inputParameters: WARPsuccess
+
 ---
 
-import { Details, Markdown, Render } from "~/components";
+import { Details, Markdown, Render } from "~/components"
 
 Most admins test by manually downloading the Cloudflare One Client and enrolling in your organization's Cloudflare Zero Trust instance.
 
 ## Install the Cloudflare One Client
 
-1.  First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
-2.  If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
-
-    <Render file="warp/client-orchestration-ips" product="cloudflare-one" />
+1. First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the Cloudflare One Client.
+2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the following destinations:
+  	<Render file="warp/client-orchestration-ips" product="cloudflare-one" />
 
-    For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
+	For more information, refer to [WARP with firewall](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
 
-3.  Manually install the Cloudflare One Client on the device.
+3. Manually install the Cloudflare One Client on the device.
 
-        <Details header="Window, macOS, and Linux">
+		<Details header="Window, macOS, and Linux">
 
-        <Render file="warp/enroll-desktop" product="cloudflare-one" />
+		<Render file="warp/enroll-desktop" product="cloudflare-one" />
 
-        </Details>
+		</Details>
 
-        <Details header="iOS, Android, and ChromeOS">
+		<Details header="iOS, Android, and ChromeOS">
 
-        <Render file="warp/enroll-ios-android" product="cloudflare-one" />
+		<Render file="warp/enroll-ios-android" product="cloudflare-one" />
 
-        </Details>
+		</Details>
 
 The Cloudflare One Client should show as **Connected**. {props.one}
diff --git a/src/content/partials/learning-paths/zero-trust/mdm.mdx b/src/content/partials/learning-paths/zero-trust/mdm.mdx
index 042067aab0fd199..d928a456aa181ac 100644
--- a/src/content/partials/learning-paths/zero-trust/mdm.mdx
+++ b/src/content/partials/learning-paths/zero-trust/mdm.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 <Render file="warp/mdm-intro" product="cloudflare-one" />
 
diff --git a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
index d3ea3aaab5d3ff0..eb80c75bd1fbfa8 100644
--- a/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
+++ b/src/content/partials/learning-paths/zero-trust/split-tunnel-settings.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render} from "~/components"
 
 Split tunnel settings determine which traffic the Cloudflare One Client does and does not proxy.
 
 The Cloudflare One Client offers two different split tunnel modes:
 
-- If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
-- If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
+* If you intend to send all internal and external destination traffic through Cloudflare's global network, opt for **Exclude IPs and domains** mode. This mode will proxy everything through the WARP tunnel with the exception of IPs and hosts defined explicitly within the Split Tunnel list.
+* If you intend to only use the Cloudflare One Client to proxy private destination traffic, you can operate in **Include IPs and domains** mode, in which you explicitly define which IP ranges and domains should be included in the WARP routing table.
 
 ## Update Split Tunnels mode
 
diff --git a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
index 21f27878f44c392..5e3a0df5f6c077b 100644
--- a/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
+++ b/src/content/partials/learning-paths/zero-trust/validate-traffic-in-gateway.mdx
@@ -1,13 +1,10 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 To validate that Cloudflare is receiving traffic from a user device:
 
-<Render
-	file="gateway/verify-connectivity"
-	product="cloudflare-one"
-	params={{ one: "DNS", two: "queries" }}
-/>
+<Render file="gateway/verify-connectivity" product="cloudflare-one" params={{ one: "DNS", two: "queries" }} />
diff --git a/src/content/partials/load-balancing/components-knowledge-callout.mdx b/src/content/partials/load-balancing/components-knowledge-callout.mdx
index b8493c88bd03af8..75cdfecec22253a 100644
--- a/src/content/partials/load-balancing/components-knowledge-callout.mdx
+++ b/src/content/partials/load-balancing/components-knowledge-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This guide assumes you are familiar with the Cloudflare [Load Balancing components](/load-balancing/understand-basics/load-balancing-components/).
diff --git a/src/content/partials/load-balancing/custom-rules-definition.mdx b/src/content/partials/load-balancing/custom-rules-definition.mdx
index 49889fc8bc61ee2..87c37f08ebba3d4 100644
--- a/src/content/partials/load-balancing/custom-rules-definition.mdx
+++ b/src/content/partials/load-balancing/custom-rules-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom load balancing rules let you customize the behavior of your load balancer based on the characteristics of a request.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
index b05bdc170e119f5..2a826379296653d 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-benefits.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your load balancer is attached to a hostname used for an [`MX` or `SRV` record](/load-balancing/additional-options/additional-dns-records/) — and not an `A`, `AAAA`, or `CNAME` record — its proxy mode should be **DNS-only**.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
index 07047a05eddeed8..85d6c2a3775c9cf 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 DNS-only load balancers route traffic by returning specific IP addresses in response to a client's DNS query.
diff --git a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
index ebcffa45dd9ce22..bc03d3b58635b6d 100644
--- a/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
+++ b/src/content/partials/load-balancing/dns-load-balancing-limitations.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 In comparison to proxied, layer 7 load balancing, DNS-only load balancing:
 
-- Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
-- Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
-- Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
-- Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
-- Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
-- Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
-- Does not support [Private Network Load Balancing](/load-balancing/private-network/).
+* Does not hide the IP addresses of your endpoints, leaving them vulnerable to DDoS attacks.
+* Performs slower failover and less accurate routing, because it has to rely on DNS resolvers and cache settings.
+* Cannot integrate with other Cloudflare features such as caching, Workers, and the WAF.
+* Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
+* Does not support [session affinity](/load-balancing/understand-basics/session-affinity/). Alternatively, you can use [DNS persistence](/load-balancing/additional-options/dns-persistence/).
+* Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
+* Does not support [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
index b5888a2b8e97651..5a380e226cc7c4b 100644
--- a/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
+++ b/src/content/partials/load-balancing/endpoints-introduction-callout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Since load balancing targets are not limited to origin web servers, the term `endpoints` has been introduced. Refer to [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-other-terms/) for its use in the context of Cloudflare offerings, and to [load balancing concepts](/load-balancing/understand-basics/load-balancing-components/) or [Reference Architecture](/reference-architecture/architectures/load-balancing/) for use case examples.
diff --git a/src/content/partials/load-balancing/fallback-pools.mdx b/src/content/partials/load-balancing/fallback-pools.mdx
index bac40469f252c71..49f0595e95dc999 100644
--- a/src/content/partials/load-balancing/fallback-pools.mdx
+++ b/src/content/partials/load-balancing/fallback-pools.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This pool is meant to be the pool of last resort, meaning that its health is not taken into account when directing traffic.
diff --git a/src/content/partials/load-balancing/health-check-diagram.mdx b/src/content/partials/load-balancing/health-check-diagram.mdx
index 6b2bfb5560e0f49..568033512858810 100644
--- a/src/content/partials/load-balancing/health-check-diagram.mdx
+++ b/src/content/partials/load-balancing/health-check-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/health-check-regions.mdx b/src/content/partials/load-balancing/health-check-regions.mdx
index 85b94acbc34ab57..cb98a0bc269813a 100644
--- a/src/content/partials/load-balancing/health-check-regions.mdx
+++ b/src/content/partials/load-balancing/health-check-regions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For each option selected in a pool's **Health Monitor Regions**, Cloudflare sends health monitor requests from three separate data centers in that region.
diff --git a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
index aa5e650fec2b99b..e1379917600272c 100644
--- a/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-4-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Layer 4 load balancers route traffic by forwarding traffic to certain ports or IP addresses.
@@ -8,6 +9,8 @@ Cloudflare currently only supports layer 4 load balancing as part of [Cloudflare
 
 :::note
 
+
 Since Spectrum operates at the TCP level, it does not have the information to support features like [session affinity](/load-balancing/understand-basics/session-affinity/), [custom rules](/load-balancing/additional-options/load-balancing-rules/), or caching.
 
+
 :::
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
index 5d6045bd0ac9477..9dfc53ccb56e590 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 In comparison to DNS-only load balancing, layer 7 load balancing:
 
-- Protects endpoints from DDoS attacks by hiding their IP addresses.
-- Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
-- Integrates with other Cloudflare features such as caching, Workers, and the WAF.
-- Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
-- Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
-- More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
-- Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
+* Protects endpoints from DDoS attacks by hiding their IP addresses.
+* Offers faster failover and more accurate routing, which can otherwise be affected by DNS caching.
+* Integrates with other Cloudflare features such as caching, Workers, and the WAF.
+* Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
+* Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
+* More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
+* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
diff --git a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
index 78f4d9da0758f11..120a77b9f1486a4 100644
--- a/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
+++ b/src/content/partials/load-balancing/layer-7-load-balancing-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Layer 7 load balancers direct traffic to specific endpoints based on information present in each HTTP/HTTPS request (HTTP headers, URI, cookies, type of data, etc.).
diff --git a/src/content/partials/load-balancing/load-balancer-create-api.mdx b/src/content/partials/load-balancing/load-balancer-create-api.mdx
index 9110fc3325a87d9..8dbe3ed3d7b8337 100644
--- a/src/content/partials/load-balancing/load-balancer-create-api.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -8,89 +9,91 @@ For a full list of properties, refer to [Create Load Balancer](/api/resources/lo
 
 :::note
 
+
 Since load balancers only exist on a zone — and not an account — you may need to get the zone `id` with the [List Zones](/api/resources/zones/methods/list/) command.
 
+
 :::
 
 <APIRequest
-	path="/zones/{zone_id}/load_balancers"
-	method="POST"
-	json={{
-		description: "Load Balancer for lb.example.com",
-		name: "lb.example.com",
-		enabled: true,
-		ttl: 30,
-		fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
-		default_pools: [
-			"17b5962d775c646f3f9725cbc7a53df4",
-			"9290f38c5d07c2e2f4df57b1f61d4196",
-			"00920f38ce07c2e2f4df50b1f61d4194",
-		],
-		proxied: true,
-		steering_policy: "random_steering",
-		session_affinity: "cookie",
-		session_affinity_attributes: {
-			samesite: "Auto",
-			secure: "Auto",
-			drain_duration: 100,
-			zero_downtime_failover: "sticky",
-		},
-		session_affinity_ttl: 5000,
-		adaptive_routing: {
-			failover_across_pools: true,
-		},
-		location_strategy: {
-			prefer_ecs: "always",
-			mode: "resolver_ip",
-		},
-		random_steering: {
-			pool_weights: {
-				de90f38ced07c2e2f4df50b1f61d4194: 0.3,
-				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5,
-			},
-			default_weight: 0.2,
-		},
-	}}
+  path="/zones/{zone_id}/load_balancers"
+  method="POST"
+  json={{
+    description: "Load Balancer for lb.example.com",
+    name: "lb.example.com",
+    enabled: true,
+    ttl: 30,
+    fallback_pool: "17b5962d775c646f3f9725cbc7a53df4",
+    default_pools: [
+      "17b5962d775c646f3f9725cbc7a53df4",
+      "9290f38c5d07c2e2f4df57b1f61d4196",
+      "00920f38ce07c2e2f4df50b1f61d4194"
+    ],
+    proxied: true,
+    steering_policy: "random_steering",
+    session_affinity: "cookie",
+    session_affinity_attributes: {
+      samesite: "Auto",
+      secure: "Auto",
+      drain_duration: 100,
+      zero_downtime_failover: "sticky"
+    },
+    session_affinity_ttl: 5000,
+    adaptive_routing: {
+      failover_across_pools: true
+    },
+    location_strategy: {
+      prefer_ecs: "always",
+      mode: "resolver_ip"
+    },
+    random_steering: {
+      pool_weights: {
+        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+      },
+      default_weight: 0.2
+    }
+  }}
 />
 
 The response contains the complete definition of the new load balancer.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "699d98642c564d2e855e9661899b7252",
-		"created_on": "2021-01-01T05:20:00.12345Z",
-		"modified_on": "2021-01-01T05:20:00.12345Z",
-		"description": "Load Balancer for lb.example.com",
-		"name": "lb.example.com",
-		"enabled": true,
-		"ttl": 30,
-		"fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
-		"default_pools": [
-			"17b5962d775c646f3f9725cbc7a53df4",
-			"9290f38c5d07c2e2f4df57b1f61d4196",
-			"00920f38ce07c2e2f4df50b1f61d4194"
-		],
-		"proxied": true,
-		"steering_policy": "random_steering",
-		"session_affinity": "cookie",
-		"session_affinity_attributes": {
-			"samesite": "Auto",
-			"secure": "Auto",
-			"drain_duration": 100,
-			"zero_downtime_failover": "sticky"
-		},
-		"session_affinity_ttl": 5000,
-		"random_steering": {
-			"pool_weights": {
-				"de90f38ced07c2e2f4df50b1f61d4194": 0.3,
-				"9290f38c5d07c2e2f4df57b1f61d4196": 0.5
-			},
-			"default_weight": 0.2
-		}
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "699d98642c564d2e855e9661899b7252",
+    "created_on": "2021-01-01T05:20:00.12345Z",
+    "modified_on": "2021-01-01T05:20:00.12345Z",
+    "description": "Load Balancer for lb.example.com",
+    "name": "lb.example.com",
+    "enabled": true,
+    "ttl": 30,
+    "fallback_pool": "17b5962d775c646f3f9725cbc7a53df4",
+    "default_pools": [
+      "17b5962d775c646f3f9725cbc7a53df4",
+      "9290f38c5d07c2e2f4df57b1f61d4196",
+      "00920f38ce07c2e2f4df50b1f61d4194"
+    ],
+    "proxied": true,
+    "steering_policy": "random_steering",
+    "session_affinity": "cookie",
+    "session_affinity_attributes": {
+      "samesite": "Auto",
+      "secure": "Auto",
+      "drain_duration": 100,
+      "zero_downtime_failover": "sticky"
+    },
+    "session_affinity_ttl": 5000,
+    "random_steering": {
+      "pool_weights": {
+        "de90f38ced07c2e2f4df50b1f61d4194": 0.3,
+        "9290f38c5d07c2e2f4df57b1f61d4196": 0.5
+      },
+      "default_weight": 0.2
+    }
+  }
 }
 ```
diff --git a/src/content/partials/load-balancing/load-balancer-create.mdx b/src/content/partials/load-balancing/load-balancer-create.mdx
index d0b76484eaea2e6..0eddd6c4f2e92bb 100644
--- a/src/content/partials/load-balancing/load-balancer-create.mdx
+++ b/src/content/partials/load-balancing/load-balancer-create.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create a Public or a Private load balancer in the dashboard:
@@ -8,31 +9,31 @@ To create a Public or a Private load balancer in the dashboard:
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Public load balancer**
+2. On the **Load Balancer Setup**, select **Public load balancer** 
 
-3. Choose the website to which you want to add this load balancer.
+3. Choose the website to which you want to add this load balancer. 
 
 4. On the **Hostname** page:
-   - Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
-   - From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
-   - Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
-   - Add a description for your load balancer.
-   - If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
-   - If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
+   * Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
+   * From the **Data Localization** dropdown, select the [region](/data-localization/how-to/load-balancing/#regional-services) you would like to use on your domain.
+   * Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
+   * Add a description for your load balancer. 
+   * If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
+   * If you want [Adaptive Routing](/load-balancing/understand-basics/adaptive-routing/), toggle the **Adaptive Routing** switch.
 
 5. Select **Next**.
 
 6. On the **Add a Pool** page:
-   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 7. Select **Next**.
 
 8. On the **Monitors** page:
-   - Review the monitors attached to your pools.
-   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   * Review the monitors attached to your pools.
+   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 9. Select **Next**.
 
@@ -43,28 +44,28 @@ To create a Public or a Private load balancer in the dashboard:
 12. Select **Next**.
 
 13. On the **Review** page:
-    - Review your configuration and make any changes.
-    - Choose whether to **Save as Draft** or **Save and Deploy**.
+    * Review your configuration and make any changes.
+    * Choose whether to **Save as Draft** or **Save and Deploy**.
 
-### Create a Private load balancer
+### Create a Private load balancer 
 
 1. Go to **Load Balancing** and select **Create load balancer**.
 
-2. On the **Load Balancer Setup**, select **Private load balancer**
+2. On the **Load Balancer Setup**, select **Private load balancer** 
 
 3. Associate your load balancer with either a Cloudflare private IP or a specified IP address and create a description for your load balancer.
 
 4. On the **Add a Pool** page:
-   - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
-   - If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
-   - If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
-   - If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
+   * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
+   * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
+   * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
+   * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
 5. Select **Next**.
 
 6. On the **Monitors** page:
-   - Review the monitors attached to your pools.
-   - If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
+   * Review the monitors attached to your pools.
+   * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
 7. Select **Next**.
 
@@ -73,5 +74,5 @@ To create a Public or a Private load balancer in the dashboard:
 9. Select **Next**.
 
 10. On the **Review** page:
-    - Review your configuration and make any changes.
-    - Choose whether to **Save as Draft** or **Save and Deploy**.
+    * Review your configuration and make any changes.
+    * Choose whether to **Save as Draft** or **Save and Deploy**.
diff --git a/src/content/partials/load-balancing/load-balancer-definition.mdx b/src/content/partials/load-balancing/load-balancer-definition.mdx
index e955489d0848da8..7c7f1e2775cb3b6 100644
--- a/src/content/partials/load-balancing/load-balancer-definition.mdx
+++ b/src/content/partials/load-balancing/load-balancer-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.) or IP address.
diff --git a/src/content/partials/load-balancing/load-balancing-diagram.mdx b/src/content/partials/load-balancing/load-balancing-diagram.mdx
index bc43dd9c4d9b564..8f66f37a89cdc36 100644
--- a/src/content/partials/load-balancing/load-balancing-diagram.mdx
+++ b/src/content/partials/load-balancing/load-balancing-diagram.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```mermaid
diff --git a/src/content/partials/load-balancing/monitor-create-api.mdx b/src/content/partials/load-balancing/monitor-create-api.mdx
index cc778566aa44003..d1d69939d9bd159 100644
--- a/src/content/partials/load-balancing/monitor-create-api.mdx
+++ b/src/content/partials/load-balancing/monitor-create-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { APIRequest } from "~/components";
@@ -7,61 +8,65 @@ import { APIRequest } from "~/components";
 For a full list of monitor properties, refer to [Create Monitor](/api/resources/load_balancers/subresources/monitors/methods/create/). If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
 <APIRequest
-	path="/accounts/{account_id}/load_balancers/monitors"
-	method="POST"
-	json={{
-		type: "https",
-		description: "Login page monitor",
-		method: "GET",
-		path: "/health",
-		header: {
-			Host: ["example.com"],
-			"X-App-ID": ["abc123"],
-		},
-		port: 8080,
-		timeout: 3,
-		retries: 0,
-		interval: 90,
-		expected_body: "alive",
-		expected_codes: "2xx",
-		follow_redirects: true,
-		allow_insecure: true,
-		consecutive_up: 3,
-		consecutive_down: 2,
-		probe_zone: "example.com",
-	}}
+  path="/accounts/{account_id}/load_balancers/monitors"
+  method="POST"
+  json={{
+    type: "https",
+    description: "Login page monitor",
+    method: "GET",
+    path: "/health",
+    header: {
+      Host: ["example.com"],
+      "X-App-ID": ["abc123"]
+    },
+    port: 8080,
+    timeout: 3,
+    retries: 0,
+    interval: 90,
+    expected_body: "alive",
+    expected_codes: "2xx",
+    follow_redirects: true,
+    allow_insecure: true,
+    consecutive_up: 3,
+    consecutive_down: 2,
+    probe_zone: "example.com"
+  }}
 />
 
 The response contains the complete definition of the new monitor.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": ":monitor-id",
-		"created_on": "2021-01-01T05:20:00.12345Z",
-		"modified_on": "2021-01-01T05:20:00.12345Z",
-		"type": "https",
-		"description": "Login page monitor",
-		"method": "GET",
-		"path": "/health",
-		"header": {
-			"Host": ["example.com"],
-			"X-App-ID": ["abc123"]
-		},
-		"port": 8080,
-		"timeout": 3,
-		"retries": 0,
-		"interval": 90,
-		"expected_body": "alive",
-		"expected_codes": "2xx",
-		"follow_redirects": true,
-		"allow_insecure": true,
-		"consecutive_up": 3,
-		"consecutive_down": 2,
-		"probe_zone": "example.com"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": ":monitor-id",
+    "created_on": "2021-01-01T05:20:00.12345Z",
+    "modified_on": "2021-01-01T05:20:00.12345Z",
+    "type": "https",
+    "description": "Login page monitor",
+    "method": "GET",
+    "path": "/health",
+    "header": {
+      "Host": [
+        "example.com"
+      ],
+      "X-App-ID": [
+        "abc123"
+      ]
+    },
+    "port": 8080,
+    "timeout": 3,
+    "retries": 0,
+    "interval": 90,
+    "expected_body": "alive",
+    "expected_codes": "2xx",
+    "follow_redirects": true,
+    "allow_insecure": true,
+    "consecutive_up": 3,
+    "consecutive_down": 2,
+    "probe_zone": "example.com"
+  }
 }
 ```
diff --git a/src/content/partials/load-balancing/monitor-create.mdx b/src/content/partials/load-balancing/monitor-create.mdx
index cba41c6a75cd948..e886aac579f8934 100644
--- a/src/content/partials/load-balancing/monitor-create.mdx
+++ b/src/content/partials/load-balancing/monitor-create.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can create a monitor within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Monitors** tab:
 
diff --git a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
index 000c0980eda9bc6..203ada096f2b360 100644
--- a/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
+++ b/src/content/partials/load-balancing/monitor-health-check-regions-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **All Data Centers (Enterprise only)**
@@ -16,8 +17,10 @@ Three health monitor probes are sent from each specified region within the pool
 
 :::caution
 
+
 Because of how Cloudflare checks health from [multiple regions](#health-monitor-regions), adding multiple regions — or choosing to check health from **All Data Centers** — can send a lot of traffic to your endpoint.
 
 The same problem can occur when setting low values for a monitor's **Interval**.
 
-:::
+
+:::
\ No newline at end of file
diff --git a/src/content/partials/load-balancing/monitor-prepare-server.mdx b/src/content/partials/load-balancing/monitor-prepare-server.mdx
index 40b7618385d0835..cac096756d634a6 100644
--- a/src/content/partials/load-balancing/monitor-prepare-server.mdx
+++ b/src/content/partials/load-balancing/monitor-prepare-server.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Make sure that your firewall or web server does not block or rate limit your configured health monitors or requests associated with [Cloudflare IP addresses](https://www.cloudflare.com/ips).
@@ -8,6 +9,8 @@ Each health monitor has the HTTP user-agent of `"Mozilla/5.0 (compatible; Cloudf
 
 :::caution
 
+
 If you know that your endpoint is healthy but Load Balancing is reporting it as unhealthy, refer to our [Monitor troubleshooting guide](/load-balancing/troubleshooting/load-balancing-faq/#why-is-my-endpoint-or-pool-considered-unhealthy).
 
+
 :::
diff --git a/src/content/partials/load-balancing/monitor-settings-basic.mdx b/src/content/partials/load-balancing/monitor-settings-basic.mdx
index 48d2f9414f6707b..61c55dcb0698619 100644
--- a/src/content/partials/load-balancing/monitor-settings-basic.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-basic.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- **Type**: The protocol to use for health monitors
-  - _Non-enterprise customers_: Choose **HTTP**, **HTTPS**, or **TCP**.
-  - _Enterprise customers_: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
-- **Path**: The endpoint path to run health monitor requests against
-- **Port**: The destination port for health monitors
+* **Type**: The protocol to use for health monitors
+  * *Non-enterprise customers*: Choose **HTTP**, **HTTPS**, or **TCP**.
+  * *Enterprise customers*: Choose **HTTP**, **HTTPS**, **TCP**, **UDP ICMP**, **ICMP Ping**, or **SMTP**.
+* **Path**: The endpoint path to run health monitor requests against
+* **Port**: The destination port for health monitors
diff --git a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
index d6ca1888d5c5948..5ea1696866dbf6b 100644
--- a/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
+++ b/src/content/partials/load-balancing/monitor-settings-consecutive.mdx
@@ -1,11 +1,14 @@
 ---
 {}
+
 ---
 
 :::note[Note]
 
+
 To increase confidence in pool status, you can also increase the `consecutive_up` and `consecutive_down` fields when [creating a monitor with the API](/api/resources/load_balancers/subresources/monitors/methods/create/).
 
 To become healthy or unhealthy, monitored endpoints must pass this health monitor request the consecutive number of times specified in these parameters.
 
+
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-definition.mdx b/src/content/partials/load-balancing/origin-steering-definition.mdx
index 41f06c64c7d903e..ff95cda09a041f0 100644
--- a/src/content/partials/load-balancing/origin-steering-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-definition.mdx
@@ -1,16 +1,19 @@
 ---
 {}
+
 ---
 
 Endpoint steering customizes how each [pool](/load-balancing/pools/) distributes requests to its associated endpoints.
 
 These distributions are a combination of two properties:
 
-- The endpoint steering [policy](#policies) chosen for your pool.
-- The [weights](#weights) assigned to each endpoint.
+* The endpoint steering [policy](#policies) chosen for your pool.
+* The [weights](#weights) assigned to each endpoint.
 
 :::note
 
+
 If an endpoint [becomes unhealthy](/load-balancing/understand-basics/health-details/), your pool will also re-balance traffic according to its endpoint steering policy.
 
+
 :::
diff --git a/src/content/partials/load-balancing/origin-steering-policies.mdx b/src/content/partials/load-balancing/origin-steering-policies.mdx
index 3588f6aa482ccc6..f1231eacca1c19e 100644
--- a/src/content/partials/load-balancing/origin-steering-policies.mdx
+++ b/src/content/partials/load-balancing/origin-steering-policies.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you [create a pool](/load-balancing/pools/create-pool/), you have to choose an option for **Endpoint Steering**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
index 04b243f9c170afd..02f56f65d616a1b 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The weight assigned to an endpoint controls the percentage of pool traffic sent to that endpoint. By default, all endpoints within a pool have a weight of **1**.
diff --git a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
index 55e5f89bf7d1d0a..003b326d282ef75 100644
--- a/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
+++ b/src/content/partials/load-balancing/origin-steering-weights-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you choose **Hash** for your **Endpoint Steering** or enable [session affinity](/load-balancing/understand-basics/session-affinity/), these options can affect traffic distribution.
diff --git a/src/content/partials/load-balancing/pool-create.mdx b/src/content/partials/load-balancing/pool-create.mdx
index 198bbcd758d3fd7..c6b72f1a6076a14 100644
--- a/src/content/partials/load-balancing/pool-create.mdx
+++ b/src/content/partials/load-balancing/pool-create.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 You can create a pool within the [load balancer workflow](/load-balancing/load-balancers/create-load-balancer/) or in the **Pools** tab:
 
@@ -11,22 +12,24 @@ You can create a pool within the [load balancer workflow](/load-balancing/load-b
 2. Select the **Pools** tab and then **Create pool**.
 
 3. For your pool, enter the following information:
-   - A name (must be unique)
-   - A description to provide more detail on the name
-   - A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
+   * A name (must be unique)
+   * A description to provide more detail on the name
+   * A choice for [**Endpoint Steering**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/), which affects how your pool routes traffic to each endpoint
 
 4. For each endpoint, enter the following information:
-   - A name (must be unique)
-   - The endpoint address or associated hostname
-   - (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
-   - A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
-   - (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
-   - (Optional) The destination port to which the traffic will be served.
+   * A name (must be unique)
+   * The endpoint address or associated hostname
+   * (Optional) A [**Virtual Network**](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
+   * A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
+   * (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
+   * (Optional) The destination port to which the traffic will be served.
 
 :::note[Note]
 
+
 If your endpoint is a website or application hosted on [Cloudflare Pages](/pages/), you will need to fill in the host header field with the project domain for it to resolve correctly.
 
+
 :::
 
 5. Repeat this process for additional endpoints in the pool.
@@ -34,9 +37,9 @@ If your endpoint is a website or application hosted on [Cloudflare Pages](/pages
 6. (Optional) Set up coordinates for [Proximity Steering](/load-balancing/understand-basics/traffic-steering/steering-policies/proximity-steering/) on the pool.
 
 7. On the pool, update the following information:
-   - **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
-   - **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
-   - **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
-   - **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
+   * **Health Threshold**: <Render file="pool-health-threshold" product="load-balancing" />
+   * **Monitor**: Attach a [monitor](/load-balancing/monitors/create-monitor/)
+   * **Health Monitor Regions**: Choose whether to check pool health from [multiple locations](/load-balancing/monitors/#health-monitor-regions), which increases accuracy but can lead to probe traffic to your endpoint
+   * **Pool Notifications**: You can set up new alerts - and view existing alerts - to be notified when pools are enabled or disabled, or pools or endpoints have changes in their [health status](/load-balancing/understand-basics/health-details/).
 
 8. When finished, select **Save**.
diff --git a/src/content/partials/load-balancing/pool-health-threshold.mdx b/src/content/partials/load-balancing/pool-health-threshold.mdx
index ef2bac2c25ed613..825e481e8f68a55 100644
--- a/src/content/partials/load-balancing/pool-health-threshold.mdx
+++ b/src/content/partials/load-balancing/pool-health-threshold.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered _Healthy_ and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
+The Health Threshold is the number of healthy endpoints for the pool as a whole to be considered *Healthy* and receive traffic based on pool order in a load balancer. Increasing this number makes the pool more reliable, but also more likely to become unhealthy.
diff --git a/src/content/partials/load-balancing/region-mapping.mdx b/src/content/partials/load-balancing/region-mapping.mdx
index 1bd65acff2b56cc..128fad39ca78170 100644
--- a/src/content/partials/load-balancing/region-mapping.mdx
+++ b/src/content/partials/load-balancing/region-mapping.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 | Region code | Region name            |
diff --git a/src/content/partials/load-balancing/route-production-traffic.mdx b/src/content/partials/load-balancing/route-production-traffic.mdx
index 5da9c7169712872..3e1b688df82eeb7 100644
--- a/src/content/partials/load-balancing/route-production-traffic.mdx
+++ b/src/content/partials/load-balancing/route-production-traffic.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Now that you have set up your load balancer and verified everything is working correctly, you can put the load balancer on a live domain or subdomain:
@@ -7,11 +8,13 @@ Now that you have set up your load balancer and verified everything is working c
 1. If you update your pools and monitors, review the pool health again to make sure everything is working as expected.
 2. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 3. Configure your load balancer to receive production traffic, which could involve either:
-   - Editing the **Hostname** of your existing load balancer.
-   - Updating the `CNAME` record sending traffic to your load balancer.
+   * Editing the **Hostname** of your existing load balancer.
+   * Updating the `CNAME` record sending traffic to your load balancer.
 
 :::note
 
+
 If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [origin rule](/rules/origin-rules/features/#dns-record).
 
+
 :::
diff --git a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
index 8c0d3b883dc0ee3..b6398dd605663ec 100644
--- a/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
+++ b/src/content/partials/load-balancing/session-affinity-by-cookie-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Session affinity automatically directs requests from the same client to the same endpoint:
@@ -24,8 +25,8 @@ Session affinity automatically directs requests from the same client to the same
      end
 ```
 
-<br />
+<br/>
 
-All cookie-based sessions default to 23 hours unless you set a custom session _Time to live_ (TTL).
+All cookie-based sessions default to 23 hours unless you set a custom session *Time to live* (TTL).
 
 The session cookie is secure when [Always Use HTTPS](/ssl/edge-certificates/additional-options/always-use-https/) is enabled. Additionally, HttpOnly is always enabled for the cookie to prevent cross-site scripting attacks.
diff --git a/src/content/partials/load-balancing/session-affinity-definition.mdx b/src/content/partials/load-balancing/session-affinity-definition.mdx
index 5b2531052f2e4ae..457703c7c032ae8 100644
--- a/src/content/partials/load-balancing/session-affinity-definition.mdx
+++ b/src/content/partials/load-balancing/session-affinity-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When you enable session affinity, your load balancer directs all requests from a particular end user to a specific endpoint. This continuity preserves information about the user session — such as items in their shopping cart — that might otherwise be lost if requests were spread out among multiple servers.
diff --git a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
index 4daefe6d4a289dd..dfe52808eb3b9c0 100644
--- a/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
+++ b/src/content/partials/load-balancing/spectrum-lb-limitations.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
+* Load Balancing [session affinity](/load-balancing/understand-basics/session-affinity/), [failover across pools](/load-balancing/understand-basics/adaptive-routing/#failover-across-pools), and [custom rules](/load-balancing/additional-options/load-balancing-rules/) are not supported by Spectrum.
 
-- UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
+* UDP health checks are only available with public monitoring. TCP can be used with both public and private monitoring.
diff --git a/src/content/partials/load-balancing/test-domain-setup.mdx b/src/content/partials/load-balancing/test-domain-setup.mdx
index 88b53616839ade6..8a7c754c580a135 100644
--- a/src/content/partials/load-balancing/test-domain-setup.mdx
+++ b/src/content/partials/load-balancing/test-domain-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Instead of starting on your production domain, you likely should create a load balancer on a test or staging domain. This may involve temporary changes to your monitors and pools, depending on your infrastructure setup.
diff --git a/src/content/partials/load-balancing/traffic-steering-definition.mdx b/src/content/partials/load-balancing/traffic-steering-definition.mdx
index 84b6a196eba9451..471d03f63fbe154 100644
--- a/src/content/partials/load-balancing/traffic-steering-definition.mdx
+++ b/src/content/partials/load-balancing/traffic-steering-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Global traffic steering policies decide how a load balancer routes traffic to attached and healthy pools.
diff --git a/src/content/partials/load-balancing/unexpected-health-statuses.mdx b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
index 9bd3a6cad5b730a..cc03b813fa18383 100644
--- a/src/content/partials/load-balancing/unexpected-health-statuses.mdx
+++ b/src/content/partials/load-balancing/unexpected-health-statuses.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 If you notice that healthy pools are being marked unhealthy:
 
-- Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
-- Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
+* Review [how endpoints and pools become unhealthy](/load-balancing/understand-basics/health-details/).
+* Refer to the [Troubleshooting section](/load-balancing/troubleshooting/).
diff --git a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
index d0ec34fe725e179..8e1a71d8ff5616f 100644
--- a/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
+++ b/src/content/partials/load-balancing/unhealthy-pool-traffic-distribution.mdx
@@ -1,11 +1,13 @@
 ---
 {}
+
 ---
 
 When a pool reaches **Critical** health, your load balancer will begin diverting traffic according to its [Traffic steering policy](/load-balancing/understand-basics/traffic-steering/steering-policies/):
 
-- **Off**:
-  - If the active pool becomes unhealthy, traffic goes to the next pool in order.
-  - If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
+* **Off**:
+
+  * If the active pool becomes unhealthy, traffic goes to the next pool in order.
+  * If an inactive pool becomes unhealthy, traffic continues to go to the active pool (but would skip over the unhealthy pool in the failover order).
 
-- **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
+* **All other methods**: Traffic is distributed across all remaining pools according to the traffic steering policy.
diff --git a/src/content/partials/logs/check-log-retention.mdx b/src/content/partials/logs/check-log-retention.mdx
index 13b4c54b32aacc3..6a5b9c2e8254154 100644
--- a/src/content/partials/logs/check-log-retention.mdx
+++ b/src/content/partials/logs/check-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/disable-log-retention.mdx b/src/content/partials/logs/disable-log-retention.mdx
index f13215928cc87a1..3a89db7ac7c39e0 100644
--- a/src/content/partials/logs/disable-log-retention.mdx
+++ b/src/content/partials/logs/disable-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-log-retention.mdx b/src/content/partials/logs/enable-log-retention.mdx
index 46ea7dc9617f844..7d9a9ac4a7a3e7c 100644
--- a/src/content/partials/logs/enable-log-retention.mdx
+++ b/src/content/partials/logs/enable-log-retention.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs, APIRequest } from "~/components";
diff --git a/src/content/partials/logs/enable-logpush-job.mdx b/src/content/partials/logs/enable-logpush-job.mdx
index f571da2cfbdba5a..9c86c3c83faa49b 100644
--- a/src/content/partials/logs/enable-logpush-job.mdx
+++ b/src/content/partials/logs/enable-logpush-job.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
 
 1. In the Cloudflare dashboard, go to the **Logpush** page at the account or or domain (also known as zone) level.
-
+ 
    For account: <DashButton url="/?to=/:account/logs" />
-
+ 
    For domain (also known as zone): <DashButton url="/?to=/:account/:zone/analytics/logs" />
 
 2. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
diff --git a/src/content/partials/logs/enable-read-permissions.mdx b/src/content/partials/logs/enable-read-permissions.mdx
index 0782c628cb0ea41..b2b55619a3f5903 100644
--- a/src/content/partials/logs/enable-read-permissions.mdx
+++ b/src/content/partials/logs/enable-read-permissions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Ensure **Log Share** permissions are enabled, before attempting to read or configure a Logpush job. For more information refer to the [Roles section](/logs/logpush/permissions/#roles).
diff --git a/src/content/partials/logs/filtering-limitations.mdx b/src/content/partials/logs/filtering-limitations.mdx
index 1f28334e5fc8c7b..2d32cc7f88aa921 100644
--- a/src/content/partials/logs/filtering-limitations.mdx
+++ b/src/content/partials/logs/filtering-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note[Note]
diff --git a/src/content/partials/networking-services/account-id-api-key.mdx b/src/content/partials/networking-services/account-id-api-key.mdx
index ae09eb187dd2510..c2532c7e6b0a36c 100644
--- a/src/content/partials/networking-services/account-id-api-key.mdx
+++ b/src/content/partials/networking-services/account-id-api-key.mdx
@@ -1,18 +1,16 @@
 ---
 {}
+
 ---
 
 import { Markdown } from "~/components";
 
-{/\*
-Conditional rendering based on showSiteId prop:
-
-- When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
-- When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
+{/* 
+  Conditional rendering based on showSiteId prop:
+  - When showSiteId=true (NetFlow page): "To export NetFlow statistics, you will need your [account ID] and [API token], as well as the `site_id` associated with your Cloudflare One Appliance."
+  - When showSiteId=false/undefined (other pages): "You will need your [account ID] and [API token] to use the API."
   The ternaries only render the differing prefix and suffix to avoid content duplication.
-  \*/}
-  :::note
-  <Markdown
-  	text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`}
-  />
-  :::
+*/}
+:::note
+<Markdown text={`${props.showSiteId ? "To export NetFlow statistics, you" : "You"} will need your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/account-owned-tokens/)${props.showSiteId ? ", as well as the \`site_id\` associated with your Cloudflare One Appliance" : " to use the API"}.`} />
+:::
diff --git a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
index e7f64d2d3b9bca3..665ea039cad5541 100644
--- a/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
+++ b/src/content/partials/networking-services/analytics/set-thresholds-site-health.mdx
@@ -9,4 +9,4 @@ When you set up an alert for your site, you will be notified when there is an is
 To set up health alerts:
 
 1. Configure <a href={props.magicTunnelHcsURL}>Tunnel health alerts</a> across all of the tunnels associated with each {props.productName} site.
-2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
+2. After configuring Tunnel health alerts, any {props.productName} site with a tunnel (on-ramp) that is outside of its SLO threshold will be labeled unhealthy in Network map and Traffic overview.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/analytics/site-analytics.mdx b/src/content/partials/networking-services/analytics/site-analytics.mdx
index 03a99eb68bf605b..5f9269dba906210 100644
--- a/src/content/partials/networking-services/analytics/site-analytics.mdx
+++ b/src/content/partials/networking-services/analytics/site-analytics.mdx
@@ -7,45 +7,51 @@ params:
   - setGeoCoordinatesURL
 ---
 
-import { Details, Markdown, DashButton } from "~/components";
+
+
+import { Details, Markdown, DashButton } from "~/components"
 
 After adding your sites, the {props.networkOverviewPageName} section of the dashboard provides a summary of the connectivity status and traffic analytics for all your sites. This is a great place to start if you receive a Cloudflare WAN alert, need to begin the troubleshooting process, or are performing routine monitoring. <Markdown text={props.instructions} />
 
 {props.networkOverviewPageName} has the following data types available:
 
 <Details header="Geographic map summary">
-	- [Aggregate Cloudflare WAN site health](#site-health) - [Cloudflare WAN
-	availability status for sites](#no-status-available) - [Cloudflare WAN site
-	geographic location](#no-location-set)
+	- [Aggregate Cloudflare WAN site health](#site-health)
+	- [Cloudflare WAN availability status for sites](#no-status-available)
+	- [Cloudflare WAN site geographic location](#no-location-set)
 </Details>
 
 <Details header="Cloudflare WAN site data table">
-	- Site Name - Site Health - Site Tunnel Names - Site Tunnel Statuses - Site
-	Traffic Sent - Site Traffic Received
+	- Site Name
+	- Site Health
+	- Site Tunnel Names
+	- Site Tunnel Statuses
+	- Site Traffic Sent
+	- Site Traffic Received
 </Details>
 
 <Details header="Cloudflare WAN site data">
-	- Traffic Sent by Tunnel - Traffic Received by Tunnel
+	- Traffic Sent by Tunnel
+	- Traffic Received by Tunnel
 </Details>
 
 To start using network overview:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **${props.networkOverviewPageName}**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    <DashButton url="/?to=/:account/networking-insights/health" />
-    </>
+	<>
 
+	<DashButton url="/?to=/:account/networking-insights/health" />
+	</>
 )
 }
 
@@ -77,6 +83,7 @@ The status of a site refers to its health. If your sites show a **No status avai
 
 The dashboard displays the number of sites with no location set, meaning sites for which you did not set up a geographic location. To add a location to a site, find the site you want to add location to, and select **no location set** to edit its location settings. Refer to <a href={props.setGeoCoordinatesURL}>Set geographic coordinates</a> for more information.
 
+
 ### Traffic overview
 
 Traffic overview aggregates all Cloudflare WAN sites configured in your account. Here, you can check summary information about each site like:
@@ -84,4 +91,4 @@ Traffic overview aggregates all Cloudflare WAN sites configured in your account.
 - Site status
 - Traffic sent and received
 
-Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
+Select one of your sites to have access to a more detailed view of its traffic, including traffic by tunnel.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
index 9388b0a604a3311..fb6b8b613c66bea 100644
--- a/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
+++ b/src/content/partials/networking-services/cloudflare-one-connectivity-options.mdx
@@ -30,7 +30,7 @@ The following table provides a high-level comparison of all connectivity options
 | [Cloudflare Tunnel](#cloudflare-tunnel) | HTTP/2, QUIC | Off-ramp only | Software daemon (`cloudflared`) on server | Exposing private applications without a public IP |
 | [Cloudflare One Client](#cloudflare-one-client) | MASQUE (default), WireGuard | Bidirectional | Client software on end-user devices | Securing remote workforce devices |
 | [Cloudflare Mesh](#cloudflare-mesh) | MASQUE | Bidirectional | Software client on Linux host | Connecting sites with IoT or VoIP devices |
-| [DNS locations](#dns-locations) | DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration | Filtering DNS traffic without device agents |
+| [DNS locations](#dns-locations) |  DNS (DoH, DoT, IPv4/IPv6) | On-ramp only | DNS resolver configuration  | Filtering DNS traffic without device agents |
 | [Proxy endpoints](#proxy-endpoints) | HTTP/HTTPS | On-ramp only | Browser PAC file configuration | Filtering web traffic without device agents |
 | [Clientless Web Isolation](#clientless-web-isolation) | HTTP/HTTPS | On-ramp only | Prefixed URL with Access authentication | Secure web access for unmanaged devices |
 | [GRE tunnels](#gre-tunnels) | GRE | Bidirectional | Network tunnel from router or firewall | Connecting sites with existing network hardware |
@@ -97,9 +97,9 @@ DNS locations allow you to filter DNS traffic from networks without deploying th
 
 DNS locations support multiple endpoint types:
 
-- **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
-- **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
-- **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
+* **IPv4/IPv6**: Standard DNS resolution using Cloudflare's resolver IPs
+* **DNS over HTTPS (DoH)**: Encrypted DNS queries over HTTPS
+* **DNS over TLS (DoT)**: Encrypted DNS queries over TLS
 
 Use DNS locations when you need to filter DNS traffic for an entire office or network, per device without installing agents on devices, or integrate with existing network infrastructure.
 
@@ -119,8 +119,8 @@ Proxy endpoints allow you to apply Cloudflare Gateway HTTP policies without inst
 
 Cloudflare One supports two types of proxy endpoints:
 
-- **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
-- **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
+* **Authorization endpoints**: Use Cloudflare Access for identity-based authentication
+* **Source IP endpoints**: Authorize traffic based on originating IP address (Enterprise only)
 
 Use proxy endpoints when you need to filter web traffic without device agents, integrate with existing proxy infrastructure, or deploy Gateway alongside other security tools.
 
@@ -283,7 +283,7 @@ The connectivity options on this page connect your private infrastructure, sites
 
 - **Non-HTTP traffic** (TCP/UDP protocols such as gaming, email, or custom services) — refer to [Spectrum](/spectrum/).
 - **Network-level DDoS protection** (for on-premises, cloud-hosted, and hybrid networks) — refer to [Magic Transit](/magic-transit/).
-  :::
+:::
 
 ### Cloudflare One recommendations by team
 
@@ -301,14 +301,14 @@ The team driving your Cloudflare One connectivity project influences which optio
 
 Cloudflare Mesh and Cloudflare One Appliance both provide site-level connectivity, but serve different deployment scenarios.
 
-| Aspect                | Cloudflare Mesh                                                                                                         | Cloudflare One Appliance                                                           |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
-| **Protocol**          | MASQUE                                                                                                                  | IPsec                                                                              |
-| **Deployment model**  | Software on Linux host (can run alongside other workloads)                                                              | Dedicated hardware appliance or virtual machine                                    |
-| **Best for**          | Cloud VPCs, development environments, smaller deployments with an available Linux host                                  | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
-| **Platform support**  | Linux only (x86_64, ARM64). Currently in beta.                                                                          | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox)                |
-| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site                                     |
-| **Management**        | Configured as a device in the Cloudflare One Client settings                                                            | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning      |
+| Aspect | Cloudflare Mesh | Cloudflare One Appliance |
+| ---- | ---- | ---- |
+| **Protocol** | MASQUE | IPsec |
+| **Deployment model** | Software on Linux host (can run alongside other workloads) | Dedicated hardware appliance or virtual machine |
+| **Best for** | Cloud VPCs, development environments, smaller deployments with an available Linux host | Enterprise branch offices, data centers, sites requiring high throughput (1 Gbps+) |
+| **Platform support** | Linux only (x86_64, ARM64). Currently in beta. | Hardware appliance (Dell VEP1460) or virtual (VMware ESXi, Proxmox) |
+| **High availability** | [Active-passive replicas](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/) for nodes with routes | Supported through multiple connectors per site |
+| **Management** | Configured as a device in the Cloudflare One Client settings | Centralized through the Cloudflare WAN dashboard with zero-touch provisioning |
 
 Use Cloudflare Mesh when you need lightweight, software-only connectivity for cloud workloads or sites where a Linux host is available. Use Cloudflare One Appliance when you need enterprise-grade throughput, high availability, or integration with existing network infrastructure.
 
@@ -457,8 +457,7 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)
 - [Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/)
 - [Cloudflare WAN](/cloudflare-wan/)
-- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of
-  supported on-ramps
+- <a href={props.onRampsURL}>WAN Connectors on-ramps</a> - Full list of supported on-ramps
 - [Multi-Cloud Networking](/multi-cloud-networking/) - Automate cloud VPC connectivity
 - [Magic Transit](/magic-transit/)
 - <a href={props.connectorURL}>Cloudflare One Appliance</a>
@@ -468,4 +467,4 @@ This pattern serves organizations with strict compliance requirements that prohi
 - [Proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) - Filter web traffic using PAC files
 - [Clientless Web Isolation](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/) - Secure web access without device agents
 
-For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/).
+For implementation guidance on combining Cloudflare One connectivity options, refer to the [SASE reference architecture](/reference-architecture/architectures/sase/). 
diff --git a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
index d436a168d8d8c4c..18c9671ea9ce7f4 100644
--- a/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/custom-ike-id-ipsec.mdx
@@ -15,11 +15,10 @@ VeloCloud has a high availability mechanism that allows customers to specify one
 Cloudflare WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for `<account_id>`, `<tunnel_id>`, and the FQDN wildcard before running the API call.
 
 <CURL
-	url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
-	method="PATCH"
-	json={{
-		custom_remote_identities: {
-			fqdn_id: "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com",
-		},
-	}}
+  url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
+  method="PATCH"
+  json={{
+    "custom_remote_identities":
+			{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
+  }}
 />
diff --git a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
index ae7c5d5a52b3fa7..c7cfca556c7a735 100644
--- a/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/get-started.mdx
@@ -64,17 +64,11 @@ The list of prerequisites below is only for customers planning to connect manual
 
 ##### GRE tunnels as off-ramp
 
-<Render
-	file="cloudflare-wan/mtu-mss/mss-clamping-gre"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/mtu-mss/mss-clamping-gre" product="networking-services" />
 
 ##### IPsec tunnels
 
-<Render
-	file="cloudflare-wan/mtu-mss/mss-clamping-ipsec"
-	product="networking-services"
-/>
+<Render file="cloudflare-wan/mtu-mss/mss-clamping-ipsec" product="networking-services"/>
 
 :::caution[Important]
 Refer to your device documentation to check if it sets IPsec MSS clamping automatically. If that is not the case and you are using IPsec inside GRE, you have to set MSS clamp manually.
@@ -87,4 +81,4 @@ Refer to <a href={props.mtuReferenceURL}>Maximum transmission unit and maximum s
 <Render
 	file="prerequisites/router-vendor-guidelines-mss-settings-origin"
 	product="networking-services"
-/>
+/>
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
index 027327c70df8bf4..fc3cadd24324184 100644
--- a/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/load-balancing.mdx
@@ -6,4 +6,4 @@ If your network has multiple paths to the same destination — for example, redu
 
 Cloudflare WAN (formerly Magic WAN) uses Private Network Load Balancing, which balances traffic across your private network endpoints. It supports both on-ramping (traffic entering Cloudflare's network) and off-ramping (traffic exiting to your sites).
 
-Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
+Refer to [Private Network Load Balancing](/load-balancing/private-network/) for more information about the feature and how to set it up. Before using this feature, [enable Load Balancing](/load-balancing/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
index 031870b0e53efd0..361286f6db723bf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/reference/device-compatibility.mdx
@@ -24,41 +24,41 @@ params:
   - oracleUrl
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) is compatible with any device that supports <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> with the <a href={props.supportedConfigurationParametersUrl}>supported configuration parameters</a> or supports <GlossaryTooltip term="GRE tunnel">GRE</GlossaryTooltip>.
 
 The matrix below includes example devices and links to the integration guides.
 
-| Appliance                                                                   | GRE tunnel                    | IPsec tunnel                  |
-| --------------------------------------------------------------------------- | ----------------------------- | ----------------------------- |
-| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a>                   | ✅                            | ✅                            |
-| Cisco ASA                                                                   | Compatibility on roadmap      | Specifications compatible[^1] |
-| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a>                              | ✅                            | ✅                            |
-| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a>   | -                             | ✅                            |
-| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>                              | ✅                            | ✅                            |
-| <a href={props.fortinetUrl}>Fortinet</a>                                    | Specifications compatible[^1] | ✅                            |
-| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a>                  | -                             | ✅                            |
-| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a>  | Specifications compatible[^1] | ✅                            |
-| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅                            |
-| <a href={props.pfsenseUrl}>pfSense</a>                                      | ✅                            | ✅                            |
-| Prisma SD-WAN (Palo Alto)                                                   | Specifications compatible[^1] | Specifications compatible[^1] |
-| Riverbed                                                                    | Specifications compatible[^1] | Specifications compatible[^1] |
-| <a href={props.sonicwallUrl}>SonicWall</a>                                  | -                             | ✅                            |
-| <a href={props.sophosFirewallUrl}>Sophos Firewall</a>                       | ✅                            | ✅                            |
-| <a href={props.strongswanUrl}>strongSwan</a>                                | -                             | ✅                            |
-| <a href={props.ubiquitiUrl}>Ubiquiti</a>                                    | -                             | ✅                            |
-| <a href={props.velocloudUrl}>Velocloud</a>                                  | -                             | ✅                            |
-| Versa                                                                       | Specifications compatible[^1] | Compatibility on roadmap      |
-| <a href={props.vyosUrl}>VyOS</a>                                            | ✅                            | ✅                            |
-| <a href={props.yamahaUrl}>Yamaha RTX Router</a>                             | -                             | ✅                            |
+| Appliance | GRE tunnel | IPsec tunnel |
+| --- | --- | --- |
+| <a href={props.arubaEdgeconnectUrl}>Aruba EdgeConnect</a> |✅ | ✅ |
+| Cisco ASA | Compatibility on roadmap | Specifications compatible[^1] |
+| <a href={props.ciscoIosXeUrl}>Cisco IOS XE</a> | ✅ | ✅ |
+| <a href={props.ciscoMerakiStaticUrl}>Cisco Meraki MX (static routing)</a> | - | ✅ |
+| <a href={props.ciscoSdWanUrl}>Cisco SD-WAN</a>  | ✅ | ✅ |
+| <a href={props.fortinetUrl}>Fortinet</a>| Specifications compatible[^1] | ✅ |
+| <a href={props.fitelnetUrl}>Furukawa Electric FITELnet</a> | - | ✅ |
+| <a href={props.juniperUrl}>HPE Juniper Networking SRX Series Firewalls</a> | Specifications compatible[^1] | ✅ |
+| <a href={props.paloAltoUrl}>Palo Alto Networks Next-Generation Firewall</a> | Specifications compatible[^1] | ✅ |
+| <a href={props.pfsenseUrl}>pfSense</a>| ✅ | ✅ |
+| Prisma SD-WAN (Palo Alto) | Specifications compatible[^1] | Specifications compatible[^1] |
+| Riverbed  | Specifications compatible[^1] | Specifications compatible[^1] |
+| <a href={props.sonicwallUrl}>SonicWall</a>| - | ✅ |
+| <a href={props.sophosFirewallUrl}>Sophos Firewall</a> | ✅ | ✅ |
+| <a href={props.strongswanUrl}>strongSwan</a> | - | ✅ |
+| <a href={props.ubiquitiUrl}>Ubiquiti</a> | - | ✅ |
+| <a href={props.velocloudUrl}>Velocloud</a> | - | ✅ |
+| Versa  | Specifications compatible[^1] | Compatibility on roadmap |
+| <a href={props.vyosUrl}>VyOS</a>| ✅ | ✅ |
+| <a href={props.yamahaUrl}>Yamaha RTX Router</a> | - | ✅ |
 
-| VPN                                                           | GRE tunnel | IPsec tunnel |
-| ------------------------------------------------------------- | ---------- | ------------ |
-| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | -          | ✅           |
-| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>         | -          | ✅           |
-| <a href={props.azureUrl}>Azure VPN Gateway</a>                | -          | ✅           |
-| <a href={props.googleUrl}>GCP Cloud VPN</a>                   | -          | ✅           |
-| <a href={props.oracleUrl}>Oracle Cloud</a>                    | -          | ✅           |
+| VPN | GRE tunnel | IPsec tunnel |
+| --- | --- | --- |
+| <a href={props.alibabaCloudUrl}>Alibaba Cloud VPN Gateway</a> | - | ✅ |
+| <a href={props.awsUrl}>Amazon AWS Transit Gateway</a>          | - | ✅ |
+| <a href={props.azureUrl}>Azure VPN Gateway</a>                 | - | ✅ |
+| <a href={props.googleUrl}>GCP Cloud VPN</a>                    | - | ✅ |
+| <a href={props.oracleUrl}>Oracle Cloud</a> 										| - | ✅ |
 
 [^1]: Specifications compatible per vendor documentation
diff --git a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
index 2b8dae020681cee..2c7ce55ec60f37e 100644
--- a/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/security-filters.mdx
@@ -7,4 +7,4 @@ Once your traffic flows through Cloudflare's network, you can apply security pol
 
 **[Cloudflare Network Firewall](/cloudflare-network-firewall/)** filters traffic at layers 3 and 4 of the [OSI model](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/) — the network and transport layers. You can allow or block traffic based on packet characteristics such as source and destination IP addresses, ports, protocols, and packet length. All Cloudflare WAN customers have <a href="/cloudflare-network-firewall/plans/">automatic access to Cloudflare Network Firewall</a>.
 
-**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
+**[Cloudflare Gateway]({props.gatewayURL})** inspects traffic at higher layers, including DNS queries, network sessions, and HTTP requests. Use Gateway to set up policies that control Internet-bound traffic and access to your private network infrastructure. Refer to <a href={props.gatewayURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a> to learn how to filter Cloudflare WAN traffic with Gateway policies.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
index d4b5c75a6d6e558..51ffc512d5a6a49 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/aws.mdx
@@ -37,7 +37,7 @@ Additionally, you also need to configure the necessary route table entries for t
 
 5. Take note of the **IP address** you chose, as this corresponds to the customer endpoint IP that you will need to configure on the Cloudflare side of the IPsec tunnel.
 
-6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**. You will need it to create the IPsec tunnel on Cloudflare's side.
+6. The number of options for the VPN connection will expand. Take note of the **Pre-shared key**.  You will need it to create the IPsec tunnel on Cloudflare's side.
 
 7. In **Inside IPv4 CIDR**, AWS enforces that only a `/30` block within the `169.254.0.0/16` range can be used. To accommodate this, Cloudflare supports a subset of this IP block. Namely, Cloudflare supports `169.254.240.0/20` to be assigned as the IPsec tunnel's (internal) interface IPs. This example will use `169.254.244.0/30` as the CIDR block for the IPsec tunnel: `169.254.244.1` for the AWS side of the tunnel, and `169.254.244.2` for the Cloudflare side of the tunnel.
 
@@ -84,7 +84,7 @@ After configuring the AWS transit gateway VPN connection and the tunnel as menti
 
 ### Static routes
 
-The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of `192.168.192.0/26`, you should use it as the prefix for your static route.
+The static route in Cloudflare WAN should point to the appropriate virtual machine (VM) subnet you created inside your AWS virtual private cloud. For example, if your VM has a subnet of  `192.168.192.0/26`, you should use it as the prefix for your static route.
 
 To create a static route:
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
index 58bcc4e8130ad91..2683c003c5db069 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/azure-virtual-wan.mdx
@@ -36,7 +36,7 @@ Using traditional hub and spoke terminology, a Virtual WAN Hub deployed within a
 4. Select **Create**. Note that the deployment time for the vWAN Hub and VPN Gateway may take 30 minutes or more.
 5. After the VPN Gateway has finished provisioning, go to **Virtual WAN** > **Hubs** > **Your vHub** > **Connectivity** > **VPN (Site to site)**.
 6. In the **Essentials** dropdown select the VPN Gateway listed.
-7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
+7. Select the JSON View for the VPN Gateway and take note of the JSON attributes at the paths `properties.ipConfigurations[0].publicIpAddress` and  `properties.ipConfigurations[1].publicIpAddress`. These will be the customer endpoints needed when configuring IPsec tunnels for Cloudflare WAN.
 
 ### 3. Create a VPN site
 
@@ -128,17 +128,17 @@ To create a **VPN Gateway Connection**:
 Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the <a href={props.cloudflareDocumentationUrl}>Cloudflare documentation</a>.
 
 1. **PSK**: Provide the PSK generated by Cloudflare for your IPsec tunnels.
-2. **Protocol**: _IKEv2_
-3. **IPsec**: _Custom_
+2. **Protocol**: *IKEv2*
+3. **IPsec**: *Custom*
    1. **IPsec SA lifetime in seconds**: 28800
    2. **IKE Phase 1**
-      1. **Encryption**: _AES256_
-      2. **Integrity/PRF**: _SHA256_
-      3. **DH Group**: _ECP384_
+      1. **Encryption**: *AES256*
+      2. **Integrity/PRF**: *SHA256*
+      3. **DH Group**: *ECP384*
    3. **IKE Phase 2(IPsec)**
-      1. **IPsec Encryption**: _AES256_
-      2. **IPsec Integrity**: _SHA256_
-      3. **PFS Group**: _ECP384_
+      1. **IPsec Encryption**: *AES256*
+      2. **IPsec Integrity**: *SHA256*
+      3. **PFS Group**: *ECP384*
    4. **Propagate Default Route:** **Disable**
    5. **Use policy based traffic selector**: **Disable**
    6. **Connection mode**: **Initiator Only**
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
index 07fb95463263fea..9a13c91be0214a0 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fitelnet.mdx
@@ -201,6 +201,7 @@ Use the CLI to configure these settings:
 ip route 192.168.1.0 255.255.255.0 tunnel 2
 ```
 
+
 ## Connection test
 
 ### IPsec status
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
index 64e945e0798b80d..b19e899b9966bbf 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/fortinet.mdx
@@ -42,10 +42,12 @@ By default, the static routes are defined with the priority set to `100`. Cloudf
 
 1. Follow the <a href={props.configureStaticRoutesUrl}>Configure static routes</a> instructions to create a static route.
 2. For the first route, ensure the following settings are defined:
+
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).
 
 3. For the second route, ensure the following settings are defined:
+
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the second IPsec tunnel defined in the previous section.
    - **Tunnel/Next hop**: Select your second tunnel (Tunnel 02 of 02).
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
index c9dfa4d0c897b6d..74c35ae14467fa1 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/juniper.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ## Test Environment
 
-| **Field**   | **Value**              |
-| ----------- | ---------------------- |
-| Vendor      | HPE Juniper Networking |
-| Model       | SRX 320                |
-| Release     | JUNOS 23.4R2-S3.9      |
-| Date Tested | March 2026             |
+| **Field**                          | **Value**                                      |
+| ---------------------------------- | ---------------------------------------------- |
+| Vendor                             | HPE Juniper Networking                         |
+| Model                              | SRX 320                                        |
+| Release                            | JUNOS 23.4R2-S3.9                              |
+| Date Tested                        | March 2026                                     |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**       |
-| ---------------------------------- | --------------- |
-| Traffic Selection Criteria         | Route-Based VPN |
-| Routing                            | Static          |
-| Redundant Tunnels                  | Yes             |
-| Tunnel Load Balancing              | Active/Active   |
-| IKE Version                        | IKEv2           |
-| Authentication                     | Pre-Shared Key  |
-| Anti-Replay Protection             | Disabled        |
-| NAT Traversal (NAT-T)              | Not Tested      |
-| NAT-T Port                         | Not Applicable  |
-| Phase 1 - DH-Group                 | Group 20        |
-| Phase 1 - Encryption               | AES-256-CBC     |
-| Phase 1 - Authentication/Integrity | SHA-256         |
-| Phase 2 - DH-Group                 | Group 20        |
-| Phase 2 - Transport                | ESP             |
-| Phase 2 - Encryption               | AES-256-CBC     |
+| **Field**                          | **Value**                                      |
+| ---------------------------------- | ---------------------------------------------- |
+| Traffic Selection Criteria         | Route-Based VPN                                |
+| Routing                            | Static                                         |
+| Redundant Tunnels                  | Yes                                            |
+| Tunnel Load Balancing              | Active/Active                                  |
+| IKE Version                        | IKEv2                                          |
+| Authentication                     | Pre-Shared Key                                 |
+| Anti-Replay Protection             | Disabled                                       |
+| NAT Traversal (NAT-T)              | Not Tested                                     |
+| NAT-T Port                         | Not Applicable                                 |
+| Phase 1 - DH-Group                 | Group 20                                       |
+| Phase 1 - Encryption               | AES-256-CBC                                    |
+| Phase 1 - Authentication/Integrity | SHA-256                                        |
+| Phase 2 - DH-Group                 | Group 20                                       |
+| Phase 2 - Transport                | ESP                                            |
+| Phase 2 - Encryption               | AES-256-CBC                                    |
 
 ## Cloudflare WAN and HPE Juniper Networking SRX Series Firewalls - Configuration Settings
 
@@ -46,92 +46,92 @@ This guide provides step-by-step instructions for configuring HPE Juniper Networ
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_01     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.0/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 162.159.135.1     |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_01                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 162.159.135.1                                  |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`      |
+| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_02     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.2/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 172.64.135.1      |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_02                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 172.64.135.1                                   |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`      |
+| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
 
 ## Customer Premise Equipment - HPE Juniper Networking
 
-| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| WAN Interface     | ge-0/0/0.0          | ge-0/0/0.0          |
-| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
-| Security Zone     | untrust             | untrust             |
+| **WAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| WAN Interface                       | ge-0/0/0.0            | ge-0/0/0.0            |
+| IP Address                          | 203.0.113.100/24      | 203.0.113.100/24      |
+| Security Zone                       | untrust               | untrust               |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ---------------------------------- | ------------------- | ------------------- |
-| Tunnel interface                   | st0.1               | st0.2               |
-| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
-| Security Zone                      | cloudflare          | cloudflare          |
+| **Virtual Tunnel Interface (VTI)**  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| Tunnel interface                    | st0.1                 | st0.2                 |
+| IP Address                          | 169.254.250.1/31      | 169.254.250.3/31      |
+| Security Zone                       | cloudflare            | cloudflare            |
 
-| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| LAN Interface     | ge-0/0/1.0          | ge-0/0/1.0          |
-| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
-| Security Zone     | trust               | trust               |
+| **LAN Interface**                   | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ----------------------------------- | --------------------- | --------------------- |
+| LAN Interface                       | ge-0/0/1.0            | ge-0/0/1.0            |
+| IP Address                          | 192.168.125.1/24      | 192.168.125.1/24      |
+| Security Zone                       | trust                 | trust                 |
 
 ### HPE Juniper Networking SRX Object Names
 
-| **Element**                        | **Object Hierarchy**             | **Name**                        |
-| ---------------------------------- | -------------------------------- | ------------------------------- |
-| Security Zone - Trust              | [ security zones security-zone ] | trust                           |
-| Security Zone - Untrust            | [ security zones security-zone ] | untrust                         |
-| Security Zone - Cloudflare WAN     | [ security zones security-zone ] | cloudflare                      |
-| IKE Proposal (only one required)   | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
-| IKE Policy - Tunnel 1              | [ security ike policy ]          | cf-wan-ike-pol-01               |
-| IKE Policy - Tunnel 2              | [ security ike policy ]          | cf-wan-ike-pol-02               |
-| IKE Gateway - Tunnel 1             | [ security ike gateway ]         | cf-wan-ike-gw-01                |
-| IKE Gateway - Tunnel 2             | [ security ike gateway ]         | cf-wan-ike-gw-02                |
-| IPsec Proposal (only one required) | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
-| IPsec Policy (only one required)   | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
-| IPsec Tunnel - Tunnel 1            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
-| IPsec Tunnel - Tunnel 2            | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
+| **Element**                          | **Object Hierarchy**             | **Name**                        |
+| ------------------------------------ | -------------------------------- | ------------------------------- |
+| Security Zone - Trust                | [ security zones security-zone ] | trust                           |
+| Security Zone - Untrust              | [ security zones security-zone ] | untrust                         |
+| Security Zone - Cloudflare WAN       | [ security zones security-zone ] | cloudflare                      |
+| IKE Proposal (only one required)     | [ security ike proposal ]        | ike-aes256cbc-sha256-dh20       |
+| IKE Policy - Tunnel 1                | [ security ike policy ]          | cf-wan-ike-pol-01               |
+| IKE Policy - Tunnel 2                | [ security ike policy ]          | cf-wan-ike-pol-02               |
+| IKE Gateway - Tunnel 1               | [ security ike gateway ]         | cf-wan-ike-gw-01                |
+| IKE Gateway - Tunnel 2               | [ security ike gateway ]         | cf-wan-ike-gw-02                |
+| IPsec Proposal (only one required)   | [ security ipsec proposal ]      | esp-aes256cbc-sha256-128        |
+| IPsec Policy (only one required)     | [ security ipsec policy ]        | ipsec-aes256cbc-sha256-128-dh20 |
+| IPsec Tunnel - Tunnel 1              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-01             |
+| IPsec Tunnel - Tunnel 2              | [ security ipsec vpn ]           | cf-wan-ipsec-vpn-02             |
 
 ## Assumptions
 
@@ -216,7 +216,7 @@ Configure the following:
 Define an IKE Proposal with the following settings:
 
 | **Attribute**            | **Value**       |
-| ------------------------ | --------------- |
+| ------------------------ | ----------------|
 | authentication-method    | pre-shared-keys |
 | dh-group                 | group20         |
 | authentication-algorithm | sha256          |
@@ -356,13 +356,13 @@ _Perform in Configuration Mode_
 
 The following example allows all source & destination IPs, ports, and protocols/services between `cloudflare` and `trust` as well as between `trust` and `cloudflare`.
 
-| **Attribute**       | **Value**     |
-| ------------------- | ------------- |
-| source-address      | any           |
-| destination-address | any           |
-| application         | any           |
-| action              | permit        |
-| log                 | session-close |
+| **Attribute**            | **Value**     |
+| ------------------------ | ------------- |
+| source-address           | any           |
+| destination-address      | any           |
+| application              | any           |
+| action                   | permit        |
+| log                      | session-close |
 
 ```txt
 set security policies from-zone cloudflare to-zone trust policy cloudflare-to-trust-permit match source-address any
@@ -389,18 +389,18 @@ This example assumes traffic originating from 192.168.125.0/24 (ingress interfac
 Implementing Filter-Based Forwarding (FBF) requires four steps:
 
 1. Create a Forwarding Routing Instance
-   - Think of the Routing Instance as a "bucket" containing an alternate routing table
-   - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
+    - Think of the Routing Instance as a "bucket" containing an alternate routing table
+    - The Routing Instance contains the destination prefix(es) and next hop addresses (VTI on Cloudflare side of the tunnels)
 2. Create a Firewall Filter
-   - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
-   - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
+    - Think of a Firewall Filter as the "brain" that determines which packets to send to the "bucket"
+    - The Firewall Filter acts as a "classifier" that identifies the traffic you want to divert to the Routing Instance
 3. Configure the RIB Group and Bind Routes
-   - Think of this as the "bridge" that copies interface routes to the "bucket"
-   - The Routing Instance is not part of the default routing table.
-   - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
+    - Think of this as the "bridge" that copies interface routes to the "bucket"
+    - The Routing Instance is not part of the default routing table.
+    - This step instructs the SRX how to reach directly connected networks and resolve next-hops found in the main table (`inet.0`) and the Cloudflare WAN Routing Instance's routing table `CF_WAN_RI.inet.0`
 4. Apply the Firewall Filter to the ingress traffic interface(s)
-   - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
-   - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
+    - Think of this as the "trigger" that starts processing packets as they enter the ingress interface
+    - As traffic ingresses the interface(s) to which it is applied, traffic is processed in a top-down fashion
 
 #### Define a Routing Instance
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
index e64b5b02cda5941..51757cc2dd241e8 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/oracle.mdx
@@ -11,16 +11,15 @@ This tutorial shows how to configure IPsec (Internet Protocol Security) between
 You need a pre-shared key to establish the IPsec tunnel. You can use the following code to create a random key:
 
 ```js
-const a = new Uint8Array(48);
-crypto.getRandomValues(a);
-let base64String = btoa(String.fromCharCode.apply(null, a));
+		const a = new Uint8Array(48);
+		crypto.getRandomValues(a);
+		let base64String = btoa(String.fromCharCode.apply(null, a));
 
-base64String = base64String
-	.replace(/\+/g, "")
-	.replace(/\//g, "")
-	.replace(/=/g, "");
+		base64String = base64String.replace(/\+/g, '')
+								   .replace(/\//g, '')
+								   .replace(/=/g, '');
 
-console.log(base64String.substring(0, 32));
+		console.log(base64String.substring(0, 32));
 ```
 
 :::caution
@@ -59,28 +58,28 @@ You can try this code in the [Workers playground](https://workers.cloudflare.com
    - **Dynamic routing gateways (DRG)**: Select the DRG you created in step 2.
    - **Routes to your on-premises network**: Enter a CIDR (Classless Inter-Domain Routing) range you want to route to Cloudflare WAN.
    - **Tunnel 1**
-     - **Name**: Enter a name.
-     - Select **Provide custom shared secret**.
-     - Enter the **pre-shared key** you created in the Prerequisites section.
-     - **IKE (Internet Key Exchange) version**: **IKEv2**
-     - **Routing type**: **Static routing**
-     - **IPv4 inside tunnel interface - CPE**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
-     - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
-       1. Select **Show advanced options**
-       2. Select **Phase one (ISAKMP) configuration**
-          - Select **Set custom configurations**
-          - **Custom encryption algorithm**: **AES_256_CBC**
-          - **Custom authentication algorithm**: **SHA2_256**
-          - **Custom Diffie-Hellman group**: **GROUP20**
-          - **IKE session key lifetime in seconds**: **86400**
-       3. Select **Phase two (IPsec) configuration**
-          - Select **Set custom configurations**
-          - **Custom encryption algorithm**: **AES_256_CBC**
-          - **HMAC (Hash-based Message Authentication Code)\_SHA2_256_128**: **HMAC_SHA2_256_128**
-          - **IPsec session key lifetime in seconds**: **28800**
-          - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
-   - **Tunnel 2**
-     - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
+      - **Name**: Enter a name.
+      - Select **Provide custom shared secret**.
+      - Enter the **pre-shared key** you created in the Prerequisites section.
+      - **IKE (Internet Key Exchange) version**: **IKEv2**
+      - **Routing type**: **Static routing**
+      - **IPv4 inside tunnel interface - CPE**:  Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `10.200.1.0/31`.
+      - **IPv4 inside tunnel interface - Oracle**: Enter the internal tunnel IP on the Oracle side of the IPsec tunnel. In this example, it is `10.200.1.1/31`. This matches with the Cloudflare side for this tunnel.
+         1. Select **Show advanced options**
+         2. Select **Phase one (ISAKMP) configuration**
+            - Select **Set custom configurations**
+            - **Custom encryption algorithm**: **AES_256_CBC**
+            - **Custom authentication algorithm**: **SHA2_256**
+            - **Custom Diffie-Hellman group**: **GROUP20**
+            - **IKE session key lifetime in seconds**: **86400**
+         3. Select **Phase two (IPsec) configuration**
+            - Select **Set custom configurations**
+            - **Custom encryption algorithm**: **AES_256_CBC**
+            - **HMAC (Hash-based Message Authentication Code)_SHA2_256_128**: **HMAC_SHA2_256_128**
+            - **IPsec session key lifetime in seconds**: **28800**
+            - **Perfect forward secrecy Diffie-Hellman group**: **GROUP20**
+    - **Tunnel 2**
+      - Repeat these steps for Tunnel 2. Select the right IP for **IPv4 inside tunnel interface - CPE (Customer-Premises Equipment)**: `10.200.2.0/31` and **IPv4 inside tunnel interface - Oracle**: `10.200.2.1/31`
 4. Select **Create IPsec connection**
 
 ## Cloudflare WAN
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
index 81fe83217616d1d..34b5e4bec7deae3 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/palo-alto.mdx
@@ -11,32 +11,32 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ## Test Environment
 
-| **Field**   | **Value**          |
-| ----------- | ------------------ |
-| Vendor      | Palo Alto Networks |
-| Model       | PA-440             |
-| Release     | PAN-OS 11.2.8      |
-| Date Tested | March 2026         |
+| **Field**                          | **Value**                                  |
+| ---------------------------------- | ------------------------------------------ |
+| Vendor                             | Palo Alto Networks                         |
+| Model                              | PA-440                                     |
+| Release                            | PAN-OS 11.2.8                              |
+| Date Tested                        | March 2026                                 |
 
 ## IKE/IPsec Crypto & Relevant Settings
 
-| **Field**                          | **Value**       |
-| ---------------------------------- | --------------- |
-| Traffic Selection Criteria         | Route-Based VPN |
-| Routing                            | Static          |
-| Redundant Tunnels                  | Yes             |
-| Tunnel Load Balancing              | Active/Active   |
-| IKE Version                        | IKEv2           |
-| Authentication                     | Pre-Shared Key  |
-| Anti-Replay Protection             | Disabled        |
-| NAT Traversal (NAT-T)              | Not Tested      |
-| NAT-T Port                         | Not Applicable  |
-| Phase 1 - DH-Group                 | Group 20        |
-| Phase 1 - Encryption               | AES-256-CBC     |
-| Phase 1 - Authentication/Integrity | SHA-256         |
-| Phase 2 - DH-Group                 | Group 20        |
-| Phase 2 - Transport                | ESP             |
-| Phase 2 - Encryption               | AES-256-CBC     |
+| **Field**                          | **Value**                                  |
+| ---------------------------------- | ------------------------------------------ |
+| Traffic Selection Criteria         | Route-Based VPN                            |
+| Routing                            | Static                                     |
+| Redundant Tunnels                  | Yes                                        |
+| Tunnel Load Balancing              | Active/Active                              |
+| IKE Version                        | IKEv2                                      |
+| Authentication                     | Pre-Shared Key                             |
+| Anti-Replay Protection             | Disabled                                   |
+| NAT Traversal (NAT-T)              | Not Tested                                 |
+| NAT-T Port                         | Not Applicable                             |
+| Phase 1 - DH-Group                 | Group 20                                   |
+| Phase 1 - Encryption               | AES-256-CBC                                |
+| Phase 1 - Authentication/Integrity | SHA-256                                    |
+| Phase 2 - DH-Group                 | Group 20                                   |
+| Phase 2 - Transport                | ESP                                        |
+| Phase 2 - Encryption               | AES-256-CBC                                |
 
 ## Cloudflare WAN and Palo Alto Networks NGFW - Configuration Settings
 
@@ -46,85 +46,85 @@ This guide provides step-by-step instructions for configuring Palo Alto Networks
 
 ### Cloudflare WAN - Tunnel 01 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_01     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.0/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 162.159.135.1     |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_01                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.0/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 162.159.135.1                                  |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `bf6c493d03<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T1-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `bf6c493d03<REDACTED>.ipsec.cloudflare.com`    |
+| Pre-shared key                       | Cloudflare-WAN-T1-PSK-1234!                    |
 
 ### Cloudflare WAN - Tunnel 02 of 02
 
-| **Attribute**                     | **Value/Address** |
-| --------------------------------- | ----------------- |
-| Name (required)                   | CF_WAN_TUN_02     |
-| Description                       | ---               |
-| IPv4 Interface Address (required) | 169.254.250.2/31  |
-| IPv6 Interface Address            | ---               |
-| Customer Endpoint                 | 203.0.113.100     |
-| Cloudflare Endpoint               | 172.64.135.1      |
-| Tunnel health checks              | True              |
-| Rate                              | Medium            |
-| **Type**                          | **Request**       |
-| **Direction**                     | **Bidirectional** |
-| Target                            | Default           |
-| ---                               | ---               |
-| Turn on replay protection         | False             |
-| **Automatic return routing**      | **True**          |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| Name (required)                      | CF_WAN_TUN_02                                  |
+| Description                          | ---                                            |
+| IPv4 Interface Address (required)    | 169.254.250.2/31                               |
+| IPv6 Interface Address               | ---                                            |
+| Customer Endpoint                    | 203.0.113.100                                  |
+| Cloudflare Endpoint                  | 172.64.135.1                                   |
+| Tunnel health checks                 | True                                           |
+| Rate                                 | Medium                                         |
+| **Type**                             | **Request**                                    |
+| **Direction**                        | **Bidirectional**                              |
+| Target                               | Default                                        |
+| ---                                  | ---                                            |
+| Turn on replay protection            | False                                          |
+| **Automatic return routing**         | **True**                                       |
 
 - IKE Identity and Pre-shared Key (obtained after tunnel creation):
 
-| **Attribute**  | **Value/Address**                           |
-| -------------- | ------------------------------------------- |
-| FQDN ID        | `0287844e9d<REDACTED>.ipsec.cloudflare.com` |
-| Pre-shared key | Cloudflare-WAN-T2-PSK-1234!                 |
+| **Attribute**                        | **Value/Address**                              |
+| ------------------------------------ | ---------------------------------------------- |
+| FQDN ID                              | `0287844e9d<REDACTED>.ipsec.cloudflare.com`    |
+| Pre-shared key                       | Cloudflare-WAN-T2-PSK-1234!                    |
 
 ## Customer Premise Equipment - Palo Alto Networks
 
-| **WAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| WAN Interface     | ethernet1/1         | ethernet1/1         |
-| IP Address        | 203.0.113.100/24    | 203.0.113.100/24    |
-| Security Zone     | untrust             | untrust             |
+| **WAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| WAN Interface                      | ethernet1/1           | ethernet1/1           |
+| IP Address                         | 203.0.113.100/24      | 203.0.113.100/24      |
+| Security Zone                      | untrust               | untrust               |
 
-| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ---------------------------------- | ------------------- | ------------------- |
-| Tunnel interface                   | tunnel.1            | tunnel.2            |
-| IP Address                         | 169.254.250.1/31    | 169.254.250.3/31    |
-| Security Zone                      | cloudflare          | cloudflare          |
+| **Virtual Tunnel Interface (VTI)** | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| Tunnel interface                   | tunnel.1              | tunnel.2              |
+| IP Address                         | 169.254.250.1/31      | 169.254.250.3/31      |
+| Security Zone                      | cloudflare            | cloudflare            |
 
-| **LAN Interface** | **Tunnel 01 of 02** | **Tunnel 02 of 02** |
-| ----------------- | ------------------- | ------------------- |
-| LAN Interface     | ethernet1/2         | ethernet1/2         |
-| IP Address        | 192.168.125.1/24    | 192.168.125.1/24    |
-| Security Zone     | trust               | trust               |
+| **LAN Interface**                  | **Tunnel 01 of 02**   | **Tunnel 02 of 02**   |
+| ---------------------------------- | --------------------- | --------------------- |
+| LAN Interface                      | ethernet1/2           | ethernet1/2           |
+| IP Address                         | 192.168.125.1/24      | 192.168.125.1/24      |
+| Security Zone                      | trust                 | trust                 |
 
 ### Palo Alto Networks NGFW Object Names
 
-| **Role**                           | **Label/Name**       | **Address**                 |
-| ---------------------------------- | -------------------- | --------------------------- |
-| CPE Security Zone - Trust          | Zone                 | trust                       |
-| CPE Security Zone - Untrust        | Zone                 | untrust                     |
-| CPE Security Zone - Cloudflare WAN | Zone                 | cloudflare                  |
-| CPE IKE Crypto Profile Name        | IKE Crypto Profile   | ike-aes256cbc-sha256-dh20   |
-| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile | ipsec-aes256cbc-sha256-dh20 |
+| **Role**                           | **Label/Name**            | **Address**                 |
+| ---------------------------------- | ------------------------- | --------------------------- |
+| CPE Security Zone - Trust          | Zone                      | trust                       |
+| CPE Security Zone - Untrust        | Zone                      | untrust                     |
+| CPE Security Zone - Cloudflare WAN | Zone                      | cloudflare                  |
+| CPE IKE Crypto Profile Name        | IKE Crypto Profile        | ike-aes256cbc-sha256-dh20   |
+| CPE IPsec Crypto Profile Name      | IPsec Crypto Profile      | ipsec-aes256cbc-sha256-dh20 |
 
 ## Assumptions
 
@@ -271,12 +271,12 @@ Repeat steps for tunnel 2
 
 Define an IKE Crypto Profile with the following settings:
 
-| **Attribute**  | **Value**   |
-| -------------- | ----------- |
-| hash           | sha256      |
-| dh-group       | group20     |
-| encryption     | aes-256-cbc |
-| lifetime hours | 8           |
+| **Attribute**   | **Value**   |
+| --------------- | ----------- |
+| hash            | sha256      |
+| dh-group        | group20     |
+| encryption      | aes-256-cbc |
+| lifetime hours  | 8           |
 
 ###### CLI
 
@@ -639,10 +639,10 @@ Gateway ID      Peer-Address       Gateway Name       Role SN    Algorithm
 
 ```txt
 IKEv2 IPSec Child SAs
-Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST
-------------                   ----     ------                     --       ------   ---- -------  -------- -----    --
-cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature
-cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature
+Gateway Name                   TnID     Tunnel                     ID       Parent   Role SPI(in)  SPI(out) MsgID    ST              
+------------                   ----     ------                     --       ------   ---- -------  -------- -----    --              
+cf-wan-ike-gw-01               1        cf-wan-ipsec-tun-01        452741   97       Init B7D055D3 4CB26B43 00000001 Mature           
+cf-wan-ike-gw-02               2        cf-wan-ipsec-tun-02        452742   98       Init B4629A07 165D416C 00000001 Mature           
 
 Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 ```
@@ -652,7 +652,7 @@ Show IKEv2 SA: Total 2 gateways found. 2 ike sa found.
 Use [test](https://docs.paloaltonetworks.com/network-security/ipsec-vpn/administration/troubleshooting/troubleshooting-site-to-site-vpn-issues-using-cli) commands to force Phase 1 and Phase 2 security associations:
 
 ```txt
-admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01
+admin@panfw01> test vpn ike-sa gateway cf-wan-ike-gw-01 
 
 Start time: Mar.30 21:23:23
 Initiate 1 IKE SA.
@@ -664,7 +664,7 @@ Initiate 1 IKE SA.
 ```
 
 ```txt
-admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01
+admin@panfw01> test vpn ipsec-sa tunnel cf-wan-ipsec-tun-01 
 
 Start time: Mar.30 21:26:50
 Initiate 1 IPSec SA for tunnel cf-wan-ipsec-tun-01.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
index 20b793688afdc79..7aff703eec495a2 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/sophos-firewall.mdx
@@ -11,6 +11,7 @@ import { Render } from "~/components";
 This tutorial shows you how to use Cloudflare WAN (formerly Magic WAN) with the following versions of the Sophos Firewall:
 
 - **Sophos form factor tested:**
+
   - Sophos Firewall XGS and XG series hardware
   - Sophos Firewall virtual appliance on VMware
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
index 29458f09ea57950..4a09ab7e89822a7 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/velocloud.mdx
@@ -195,7 +195,7 @@ Once the Edge device is added, you should land on the **Device** tab.
 
 #### User Defined WAN Link
 
-Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result, the WAN Link must be specified.
+Note the indicator next to **GE3**. The steps in the Profile section disabled **Auto WAN Link Detection**. As a result,  the WAN Link must be specified.
 
 ![Note the indicator next to GE3.](~/assets/images/cloudflare-wan/third-party/velocloud/image2.png)
 
@@ -215,7 +215,7 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 5. Select the **Network Service** defined earlier. For example, `Magic_WAN_vc-edge-03`.
 6. In the **Action** column, select the **+** button, and configure the following options:
    1. **Public WAN Link**: Choose the Public WAN Link (refer to User-Defined WAN Link)
-   2. **Local Identification Type**: _FQDN_
+   2. **Local Identification Type**: *FQDN*
    3. **Local Identification**: Enter the FQDN specified when configuring Cloudflare WAN IPsec tunnels through the Custom FQDN IKE ID API endpoint.
    4. **PSK**: Enter the Pre-Shared Key. Ensure you use the same PSK for both Cloudflare WAN IPsec tunnels.
    5. **Destination Primary Public IP**: Pre-populated from the Network Service defined earlier.
@@ -227,8 +227,8 @@ Note the indicator next to **GE3**. The steps in the Profile section disabled **
 
 Configure the **Site Subnets** to facilitate:
 
-- Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
-- Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
+* Routing traffic from one Cloudflare WAN site to other Cloudflare WAN sites.
+* Ensure Cloudflare WAN IPsec tunnel health checks perform optimally.
 
 1. Go to **Configure** > **Network Services**.
 2. Expand the **Non SD-WAN Destinations through Edge** section.
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
index 948613cef1331b1..fae8475cf53be20 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/viptela.mdx
@@ -37,32 +37,32 @@ To create a Secure Internet Gateway (SIG) using vManage:
 1. From **Cisco vManage** under **Configuration**, select **Generic** and **Add Tunnel**.
 2. The table below shows the setting fields and their options.
 
-| Setting             | Type/Detail                           |
-| ------------------- | ------------------------------------- |
+| Setting             | Type/Detail                               |
+| ------------------- | ----------------------------------------- |
 | **Global Template** | Factory_Default_Global_CISCO_Template |
-| **Cisco Banner**    | Factory_Default_Retail_Banner         |
-| **Policy**          | Branch-Local-Policy                   |
+| **Cisco Banner**    | Factory_Default_Retail_Banner          |
+| **Policy**          | Branch-Local-Policy                       |
 
 **Transport & Management VPN settings**
 
-| Setting                           | Type/Detail                     |
-| --------------------------------- | ------------------------------- |
-| **Cisco VPN 0**                   | GCP-Branch-VPN0                 |
-| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template         |
-| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC |
-| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface              |
-| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01  |
+| Setting                           | Type/Detail                         |
+| --------------------------------- | ----------------------------------- |
+| **Cisco VPN 0**                   | GCP-Branch-VPN0                     |
+| **Cisco Secure Internet Gateway** | Branch-SIG-GRE-Template             |
+| **Cisco VPN Interface Ethernet**  | GCP-Branch-Public-Internet-TLOC     |
+| **Cisco VPN Interface Ethernet**  | GCP-VPN0-Interface                  |
+| **Cisco VPN 512**                 | Default_AWS_TGW_CSR_VPN512_V01 |
 
 **Basic Information settings**
 
-| Setting            | Type/Detail                             |
-| ------------------ | --------------------------------------- |
+| Setting            | Type/Detail                                 |
+| ------------------ | ------------------------------------------- |
 | **Cisco System**   | Default_BootStrap_Cisco_System_Template |
-| **Cisco Logging**  | Default_Logging_Cisco_V01               |
-| **Cisco AAA**      | AWS-Branch-AAA-Template                 |
-| **Cisco BFD**      | Default_BFD_Cisco-V01                   |
-| **Cisco OMP**      | Default*AWS_TGW_CSR_OMP_IPv46*...       |
-| **Cisco Security** | Default_Security_Cisco_V01              |
+| **Cisco Logging**  | Default_Logging_Cisco_V01                |
+| **Cisco AAA**      | AWS-Branch-AAA-Template                     |
+| **Cisco BFD**      | Default_BFD_Cisco-V01                     |
+| **Cisco OMP**      | Default_AWS_TGW_CSR_OMP_IPv46_...     |
+| **Cisco Security** | Default_Security_Cisco_V01               |
 
 When creating the Feature Template, you can choose values that apply globally or that are device specific. For example, the **Tunnel Source IP Address**, **Interface Name** and fields from **Update Tunnel** are device specific and should be chosen accordingly.
 
diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
index 82717dcc274bcdf..017633fb496566a 100644
--- a/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/third-party/yamaha.mdx
@@ -22,19 +22,19 @@ Before proceeding, ensure that you have the anycast IPs assigned to your account
 ### IPsec tunnels
 
 1. Follow the <a href={props.addTunnelsUrl}>Add tunnels</a> instructions to create the required IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
-   - **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
-   - **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
-   - **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
-   - **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
-   - **Health check rate**: _Medium_.
-   - **Health check type**: _Request_.
-   - **Health check direction**: _Bidirectional_.
-   - **Health check target**: _Default_.
-   - **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
-   - **Replay protection**: Do not check the box, to keep this disabled.
+	- **Tunnel name**: Enter your tunnel name. In this example, it is `RTX840-vpn01`.
+	- **Interface address**: Enter the internal tunnel IP on the Cloudflare side of the IPsec tunnel. In this example, it is `172.30.223.2/31`.
+	- **Customer endpoint**: Enter the WAN IP address of your RTX router. In our example, this is `194.xx.xx.xx`. This is the fixed public IPv4 address you get from your ISP for your internet service.
+	- **Cloudflare endpoint**: One of the Cloudflare anycast IP addresses assigned to your account.
+	- **Health check rate**: _Medium_.
+	- **Health check type**: _Request_.
+	- **Health check direction**: _Bidirectional_.
+	- **Health check target**: _Default_.
+	- **Pre-shared key**: Select **Use my own pre-shared key** and paste a secure key of your own.
+	- **Replay protection**: Do not check the box, to keep this disabled.
 
 2. After you create your tunnel, the Cloudflare dashboard will load a list of tunnels set up for your account. Select the IPsec tunnel you have just created, and check the following setting:
-   - **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
+	- **FQDN ID**: Copy this ID and save it. You will need it when configuring the IPsec tunnel on your RTX router.
 
 ### Static routes
 
@@ -214,4 +214,4 @@ IKE keepalive:
 [Status]: OK
 
 [Next send]: 1 sec after
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
index e49fb208f2bd10f..7639f10f685149d 100644
--- a/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/wan-transformation.mdx
@@ -36,13 +36,13 @@ On-premises network and security appliances require manual firmware updates, pat
 
 ## Compare WAN approaches
 
-|                 | Traditional WAN (MPLS)                                                                                | SD-WAN                                                                                             | Cloudflare One                                                                                                   |
-| --------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing.   | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling.  |
-| **Cost model**  | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment.            | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model.                    |
-| **Agility**     | Weeks to months to provision new circuits. Rigid topology changes.                                    | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection.                              |
-| **Security**    | Security applied at central data center or per-site firewalls.                                        | Varies by vendor. Some offer integrated security, others require separate appliances.              | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
-| **Management**  | Separate management for WAN circuits, routers, and security appliances.                               | Single console for WAN, but security often managed separately.                                     | Single dashboard for network connectivity, routing, firewall rules, and security policies.                       |
+| | Traditional WAN (MPLS) | SD-WAN | Cloudflare One |
+|---|---|---|---|
+| **Performance** | Predictable but limited to circuit capacity. High latency for cloud-bound traffic due to backhauling. | Improved path selection across multiple links. Still relies on branch appliances for processing. | Traffic routed to the nearest Cloudflare data center. Cloud-bound traffic egresses locally without backhauling. |
+| **Cost model** | High fixed costs. Multi-year contracts for private circuits. Per-site hardware investment. | Lower circuit costs (uses Internet links). Per-site appliance licensing and hardware costs remain. | Internet circuit costs only. No per-site hardware required (optional). Pay-as-you-grow model. |
+| **Agility** | Weeks to months to provision new circuits. Rigid topology changes. | Faster site deployment over Internet circuits. Still requires appliance staging and configuration. | Connect a new site in minutes. Tunnels auto-establish from any Internet connection. |
+| **Security** | Security applied at central data center or per-site firewalls. | Varies by vendor. Some offer integrated security, others require separate appliances. | Integrated security at every data center — firewall, secure web gateway, and Zero Trust policies applied inline. |
+| **Management** | Separate management for WAN circuits, routers, and security appliances. | Single console for WAN, but security often managed separately. | Single dashboard for network connectivity, routing, firewall rules, and security policies. |
 
 ## Plan your migration
 
@@ -78,11 +78,7 @@ Organizations that start with Cloudflare WAN for site-to-site connectivity and p
 
 ## Next steps
 
-- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the
-  Cloudflare One Appliance or a third-party device.
-- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all
-  Cloudflare One connectivity options and choose the right combination for your
-  deployment.
-- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported
-  on-ramps for connecting your networks.
+- <a href={props.getStartedUrl}>Get started</a>: Set up Cloudflare WAN with the Cloudflare One Appliance or a third-party device.
+- <a href={props.connectivityOptionsUrl}>Connectivity options</a>: Compare all Cloudflare One connectivity options and choose the right combination for your deployment.
+- <a href={props.onRampsUrl}>On-ramps</a>: Review the full list of supported on-ramps for connecting your networks.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the architecture of Cloudflare One as a SASE platform.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
index 67d32f2a51ebbf2..233eb735ada557b 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/gateway.mdx
@@ -21,9 +21,7 @@ params:
 
 import { Render } from "~/components";
 
-<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web
-Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress
-traffic.
+<a href={props.gatewayURL}>Cloudflare Gateway</a>, our comprehensive Secure Web Gateway, allows you to set up policies to inspect DNS, network, HTTP, and egress traffic.
 
 You can apply network and HTTP Gateway policies alongside <a href="/cloudflare-network-firewall/">Cloudflare Network Firewall</a> policies (for L3/4 traffic filtering) to Internet-bound traffic or private traffic entering the Cloudflare network through Cloudflare WAN (formerly Magic WAN). Additionally, you can configure Gateway to [resolve DNS queries](#dns-filtering) from Cloudflare WAN.
 
@@ -130,9 +128,9 @@ Source ports are fixed to `1024`-`65535` and cannot be overridden.
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
 
 ## Test Gateway integration
 
@@ -143,7 +141,6 @@ If you are still testing Gateway and Cloudflare is not your default route, confi
 Confirm there is an entry for the test in <a href={props.gatewayLogsURL}>HTTP Gateway Activity Logs</a>.
 
 Verify the following details:
-
 - **Destination IP**: Should be the public IP address of `ifconfig.me`.
 - **Source IP**: Should be the private (WAN) address of the host with the browser.
 - **Outbound connection**: Should be sourced from a Cloudflare WAN IP address, not any public IP address that Cloudflare might be advertising on your behalf.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
index 05ee41c0b931606..ca49d64696b2380 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/overview.mdx
@@ -1,8 +1,8 @@
 ---
-{}
+ {}
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) provides site-to-site connectivity and packet-level security through [Cloudflare Network Firewall](/cloudflare-network-firewall/). The Cloudflare One integrations below extend that foundation with identity-aware security — user-level access policies through [Cloudflare Access](/cloudflare-one/access-controls/), secure Internet egress through [Cloudflare Gateway](/cloudflare-one/traffic-policies/), and device-level routing through the [Cloudflare One Client (formerly WARP)](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/).
 
@@ -10,4 +10,4 @@ Review the tutorials to learn how to use Cloudflare WAN with these Cloudflare On
 
 <DirectoryListing />
 
-If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
+If you want a deep dive into key architecture and functionalities aspects of Cloudflare One, and learn more about Cloudflare WAN and its structure, refer to [Evolving to a SASE architecture with Cloudflare](/reference-architecture/architectures/sase/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
index f80c67cfd5709c5..00c200fe13cb9b3 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/security-services.mdx
@@ -19,9 +19,7 @@ Cloudflare WAN carries three types of traffic, and different security services a
 
 ### Cloudflare Network Firewall
 
-<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides
-packet-level filtering at layers 3 and 4. You define allow or block rules based
-on IP addresses, ports, and protocols.
+<a href={props.networkFirewallURL}>Cloudflare Network Firewall</a> provides packet-level filtering at layers 3 and 4. You define allow or block rules based on IP addresses, ports, and protocols.
 
 - **Applies to**: inbound, outbound, and east-west traffic
 - **Included with**: Cloudflare WAN by default for [standard features](/cloudflare-network-firewall/plans/)
@@ -76,16 +74,16 @@ AI visibility is not a separate inline security service. It is an analytics feat
 
 ## Use-case mapping
 
-| Traffic scenario                                     | Recommended services                                          |
-| ---------------------------------------------------- | ------------------------------------------------------------- |
-| Block traffic between sites by IP, port, or protocol | Network Firewall                                              |
-| Filter DNS queries from branch offices               | Gateway DNS policies                                          |
-| Block malware downloads from branch offices          | Gateway HTTP policies                                         |
-| Prevent sensitive data uploads to the Internet       | DLP (via Gateway HTTP policies)                               |
-| Isolate risky web browsing from branch users         | Browser Isolation (via Gateway HTTP policies)                 |
-| Detect and block unsanctioned SaaS applications      | CASB + Gateway HTTP policies                                  |
-| Monitor employee AI tool usage                       | AI Security Report (via Gateway)                              |
-| Protect against DDoS on customer-owned IPs           | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
+| Traffic scenario | Recommended services |
+|---|---|
+| Block traffic between sites by IP, port, or protocol | Network Firewall |
+| Filter DNS queries from branch offices | Gateway DNS policies |
+| Block malware downloads from branch offices | Gateway HTTP policies |
+| Prevent sensitive data uploads to the Internet | DLP (via Gateway HTTP policies) |
+| Isolate risky web browsing from branch users | Browser Isolation (via Gateway HTTP policies) |
+| Detect and block unsanctioned SaaS applications | CASB + Gateway HTTP policies |
+| Monitor employee AI tool usage | AI Security Report (via Gateway) |
+| Protect against DDoS on customer-owned IPs | Network Firewall (inbound) + [Magic Transit](/magic-transit/) |
 
 ## How services compose
 
@@ -101,12 +99,7 @@ This means you can layer multiple security services on the same traffic flow wit
 
 ## Next steps
 
-- <a href={props.gatewaySetupURL}>
-  	Connect to Cloudflare Gateway with Cloudflare WAN
-  </a>
-  : Detailed setup guide for Gateway integration with WAN traffic.
-- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure
-  packet-level filtering rules.
+- <a href={props.gatewaySetupURL}>Connect to Cloudflare Gateway with Cloudflare WAN</a>: Detailed setup guide for Gateway integration with WAN traffic.
+- <a href={props.networkFirewallURL}>Cloudflare Network Firewall</a>: Configure packet-level filtering rules.
 - [SASE reference architecture](/reference-architecture/architectures/sase/): Explore the full architecture of Cloudflare One as a SASE platform.
-- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your
-  migration from traditional WAN to Cloudflare.
+- <a href={props.wanTransformationURL}>WAN transformation</a>: Plan your migration from traditional WAN to Cloudflare.
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
index ef33bc683575a8e..41ddc29de0c6c15 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/tunnel.mdx
@@ -8,7 +8,7 @@ params:
   - arrURL
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 Cloudflare WAN (formerly Magic WAN) can work together with <a href="/cloudflare-one/networks/connectors/cloudflare-tunnel/">Cloudflare Tunnel</a> to provide easy access between your networks and applications.
 
@@ -30,12 +30,12 @@ To route the same prefix to different destinations, use separate [virtual networ
 
 Cloudflare reserves the following IP ranges for Zero Trust services:
 
-| IP range         | Purpose                                                                                              |
-| ---------------- | ---------------------------------------------------------------------------------------------------- |
-| `100.64.0.0/12`  | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/)       |
-| `100.96.0.0/12`  | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
-| `100.80.0.0/16`  | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/)             |
-| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/)                                           |
+| IP range | Purpose |
+| --- | --- |
+| `100.64.0.0/12` | [Cloudflare Source IPs](/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/) |
+| `100.96.0.0/12` | [Device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/) |
+| `100.80.0.0/16` | [Initial resolved IPs](/cloudflare-one/traffic-policies/egress-policies/host-selectors/) |
+| `100.112.0.0/16` | [Private Load Balancers](/load-balancing/private-network/) |
 
 Do not configure routes that overlap with these reserved ranges.
 
@@ -51,8 +51,7 @@ Longest-prefix-match routing is the default route selection method. Other mechan
 
 ### Automatic Return Routing (ARR)
 
-<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for
-return traffic.
+<a href={props.arrURL}>Automatic Return Routing</a> bypasses route lookup for return traffic.
 
 When ARR is enabled:
 
@@ -89,6 +88,7 @@ To verify that a `cloudflared` tunnel works correctly with your Cloudflare WAN c
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
+
diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
index 425405bded13584..02de971802f7fa9 100644
--- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
+++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx
@@ -73,9 +73,9 @@ You must log out and log back in with at least one device to ensure the configur
 	params={{
 		greIpsecURL: props.greIpsecURL,
 		warpURL: props.warpURL,
-		tracerouteURL: props.tracerouteURL,
-	}}
-/>
+		tracerouteURL: props.tracerouteURL
+		}}
+	/>
 
 ## Double encapsulation
 
@@ -91,8 +91,7 @@ To learn which IP addresses and UDP ports you should exclude to accomplish this,
 	file="mconn/network-options/app-aware-policies/warp-traffic"
 	product="networking-services"
 	params={{
-		warpFirewallURL:
-			"/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/",
+		warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 	}}
 />
 
diff --git a/src/content/partials/networking-services/cni-product-use-cases.mdx b/src/content/partials/networking-services/cni-product-use-cases.mdx
index 5d902dd611989d8..1e1079f2de90aec 100644
--- a/src/content/partials/networking-services/cni-product-use-cases.mdx
+++ b/src/content/partials/networking-services/cni-product-use-cases.mdx
@@ -4,12 +4,13 @@
 
 CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications.
 
-|                                                                                                                                                                                                         | Dataplane v1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Dataplane v2                                                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Supported.                                                                                                                                                                |
-| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare.                                              | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
-| **Cloudflare WAN and Zero Trust** <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds.                      | Supported with a GRE tunnel established over the interconnect circuit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Supported.                                                                                                                                                                |
-| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence).                                                                                                             | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP.                                                                                                                                                                                                                                                                              | Not supported.                                                                                                                                                            |
-| **Application Security and Performance** <br /> Improve the performance and security of your web applications                                                                                           | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
+
+|  | Dataplane v1 | Dataplane v2 |
+| ---- | ---- | ---- |
+| **Magic Transit Direct Server Return (DSR)** <br /> Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Cloudflare WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. |
+| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
 
 For more details refer to the [prerequisites section](/network-interconnect/get-started/#prerequisites).
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
index 3776c9a7c06a1bd..4b05caa926f685e 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-bandwidth-graphql.mdx
@@ -104,5 +104,4 @@ curl https://api.cloudflare.com/client/v4/graphql \
 ```
 
 [^1]: For details, refer to [Authenticate with a Cloudflare API key](/analytics/graphql-api/getting-started/authentication/api-key-auth/).
-
-[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
+[^2]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
index 40149b5bcec5005..0471540ec9e7cb8 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-endpoint-health-checks.mdx
@@ -17,13 +17,13 @@ You need the following to query endpoint health check data:
 
 The following parameters are some of the most common ones in the `filter` object:
 
-| Parameter      | Description                                                                                                                                                                                                                                             |
-| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `date_geq`     | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
-| `date_leq`     | _(Optional)_ End date for the query. Uses the same format as `date_geq`.                                                                                                                                                                                |
-| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions.                                                                                                  |
-| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format.                                                                                                                                                                                                          |
-| `limit`        | Maximum number of result groups to return.                                                                                                                                                                                                              |
+| Parameter | Description |
+| :---- | :---- |
+| `date_geq` | Start date for the query in `YYYY-MM-DD` format (for example, `2026-01-01`). When used with a date-based truncation dimension, returns results from this date onward. You can also use a full ISO 8601 timestamp (for example, `2026-01-01T00:00:00Z`). |
+| `date_leq` | _(Optional)_ End date for the query. Uses the same format as `date_geq`. |
+| `datetime_geq` | _(Optional)_ Start timestamp in ISO 8601 format (for example, `2026-01-01T00:00:00Z`). Use instead of `date_geq` for time-based truncation dimensions. |
+| `datetime_leq` | _(Optional)_ End timestamp in ISO 8601 format. |
+| `limit` | Maximum number of result groups to return. |
 
 You can also filter on any dimension listed in the [Available dimensions](#available-dimensions) table. Append an operator suffix to the dimension name to create a filter — for example, `endpoint_in` to filter by a list of endpoints, or `checkType_neq` to exclude a specific check type. Using a dimension name without a suffix filters for equality. For the full list of supported operators, refer to [Filtering](/analytics/graphql-api/features/filtering/).
 
@@ -31,28 +31,28 @@ You can also filter on any dimension listed in the [Available dimensions](#avail
 
 You can query the following dimensions in the `dimensions` field:
 
-| Dimension                | Description                                                                      |
-| :----------------------- | :------------------------------------------------------------------------------- |
-| `checkId`                | The unique ID of the configured health check.                                    |
-| `checkType`              | The type of health check (for example, `icmp`).                                  |
-| `endpoint`               | The IP address of the endpoint being checked.                                    |
-| `name`                   | The name assigned to the health check when configured (may be empty if not set). |
-| `date`                   | Event timestamp truncated to the day.                                            |
-| `datetime`               | Full event timestamp.                                                            |
-| `datetimeMinute`         | Event timestamp truncated to the minute.                                         |
-| `datetimeFiveMinutes`    | Event timestamp truncated to five-minute intervals.                              |
-| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals.                                |
-| `datetimeHalfOfHour`     | Event timestamp truncated to 30-minute intervals.                                |
-| `datetimeHour`           | Event timestamp truncated to the hour.                                           |
+| Dimension | Description |
+| :---- | :---- |
+| `checkId` | The unique ID of the configured health check. |
+| `checkType` | The type of health check (for example, `icmp`). |
+| `endpoint` | The IP address of the endpoint being checked. |
+| `name` | The name assigned to the health check when configured (may be empty if not set). |
+| `date` | Event timestamp truncated to the day. |
+| `datetime` | Full event timestamp. |
+| `datetimeMinute` | Event timestamp truncated to the minute. |
+| `datetimeFiveMinutes` | Event timestamp truncated to five-minute intervals. |
+| `datetimeFifteenMinutes` | Event timestamp truncated to 15-minute intervals. |
+| `datetimeHalfOfHour` | Event timestamp truncated to 30-minute intervals. |
+| `datetimeHour` | Event timestamp truncated to the hour. |
 
 ### Available metrics
 
-| Metric               | Description                                       |
-| :------------------- | :------------------------------------------------ |
-| `count`              | Total number of health check events in the group. |
-| `sum.total`          | Total number of health check probes sent.         |
-| `sum.failures`       | Number of failed health check probes.             |
-| `avg.lossPercentage` | Average calculated loss percentage (0-100).       |
+| Metric | Description |
+| :---- | :---- |
+| `count` | Total number of health check events in the group. |
+| `sum.total` | Total number of health check probes sent. |
+| `sum.failures` | Number of failed health check probes. |
+| `avg.lossPercentage` | Average calculated loss percentage (0-100). |
 
 ### API call
 
@@ -111,43 +111,43 @@ https://api.cloudflare.com/client/v4/graphql \
 
 ```json
 {
-	"data": {
-		"viewer": {
-			"accounts": [
-				{
-					"magicEndpointHealthCheckAdaptiveGroups": [
-						{
-							"count": 288,
-							"dimensions": {
-								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-								"checkType": "icmp",
-								"datetimeFiveMinutes": "2026-01-21T12:00:00Z",
-								"endpoint": "103.21.244.100"
-							},
-							"sum": {
-								"failures": 0,
-								"total": 288
-							}
-						},
-						{
-							"count": 288,
-							"dimensions": {
-								"checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
-								"checkType": "icmp",
-								"datetimeFiveMinutes": "2026-01-21T12:05:00Z",
-								"endpoint": "103.21.244.100"
-							},
-							"sum": {
-								"failures": 2,
-								"total": 288
-							}
-						}
-					]
-				}
-			]
-		}
-	},
-	"errors": null
+  "data": {
+    "viewer": {
+      "accounts": [
+        {
+          "magicEndpointHealthCheckAdaptiveGroups": [
+            {
+              "count": 288,
+              "dimensions": {
+                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+                "checkType": "icmp",
+                "datetimeFiveMinutes": "2026-01-21T12:00:00Z",
+                "endpoint": "103.21.244.100"
+              },
+              "sum": {
+                "failures": 0,
+                "total": 288
+              }
+            },
+            {
+              "count": 288,
+              "dimensions": {
+                "checkId": "90b478c7-bb51-4640-b94b-2c3050e9fa00",
+                "checkType": "icmp",
+                "datetimeFiveMinutes": "2026-01-21T12:05:00Z",
+                "endpoint": "103.21.244.100"
+              },
+              "sum": {
+                "failures": 2,
+                "total": 288
+              }
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "errors": null
 }
 ```
 
diff --git a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
index f9f5e61e69a7e7b..f224c2ab01efe75 100644
--- a/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
+++ b/src/content/partials/networking-services/graphql/query-magic-transit-health-checks.mdx
@@ -97,4 +97,4 @@ https://api.cloudflare.com/client/v4/graphql \
 #=> }
 ```
 
-[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
+[^1]: For details, refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
\ No newline at end of file
diff --git a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
index 630b17ac37eb812..1240490c155138a 100644
--- a/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
+++ b/src/content/partials/networking-services/ipsec-logs-troubleshooting.mdx
@@ -40,7 +40,7 @@ Authentication failures in Phase 1 indicate a PSK mismatch. To resolve:
 
 1. Go to **Connectors** and select your tunnel.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select **Generate new PSK**.
 3. Copy the new PSK exactly — do not add extra spaces or characters.
@@ -72,9 +72,9 @@ Disable anti-replay protection on your tunnel endpoint, or set the replay window
 
 #### Health check type incompatible with stateful firewall
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default _Reply_ health check packets because no matching ICMP request exists in their session table.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the default *Reply* health check packets because no matching ICMP request exists in their session table.
 
-Change the health check type from _Reply_ to _Request_. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
+Change the health check type from *Reply* to *Request*. For detailed steps, refer to <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>.
 
 #### ISP blocking health check return path
 
@@ -128,7 +128,7 @@ Use IPsec logs to monitor tunnel activity during the key-exchange phase of the I
 
 1. Go to the **Logpush** page.
 
-   <DashButton url="/?to=/:account/logs" />
+	<DashButton url="/?to=/:account/logs" />
 
 2. Select **Create a Logpush job**.
 3. Select **IPsec logs** as your dataset.
diff --git a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
index 57fe9ec9026d18b..01689291e53b1c2 100644
--- a/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
+++ b/src/content/partials/networking-services/magic-transit/advertise-prefixes.mdx
@@ -12,9 +12,8 @@ If you are using a Cloudflare IP, you do not need to advertise your prefixes.
 You must [put the appropriate MSS clamps](#set-maximum-segment-size) in place before [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) changes are made. Failure to apply an MSS clamp can result in dropped packets and hard-to-debug connectivity issues.
 
 Also, when using [Cloudflare Network Interconnect](/magic-transit/network-interconnect/) with Magic Transit you must set the following MSS clamp sizes to accommodate additional overhead:
-
 - GRE tunnels over CNI with Dataplane v1: 1476 bytes
 - CNI with Dataplane v2 / CNI with Dataplane v1 with a maximum transmission unit (MTU) size of 1500 bytes handoff does not require an MSS clamp.
 
 MSS clamps are used to backhaul data from the data center where traffic is ingested (close to the end user) to the facility with the CNI link.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
index 2eab7b7b67f803a..c10384b93e929ca 100644
--- a/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
+++ b/src/content/partials/networking-services/magic-transit/cloudflare-ips.mdx
@@ -3,19 +3,19 @@ params:
   - mtLpCreateTunnel
   - mtLpStaticRoute
   - mtLpBgpPeering
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 To use Magic Transit, you need to own a publicly routable IP address block with a minimum size of `/24`. If you do not own a `/24` address block, you can use Magic Transit with a Cloudflare-owned IP address. This option is helpful if you do not meet the `/24` prefix length requirements or want to protect a smaller network.
 
 To protect your network with a Cloudflare IP address, contact your account manager. After you receive your IP address:
 
 - <a href={props.mtLpCreateTunnel}>Create a tunnel</a>.
-- <a href={props.mtLpStaticRoute}>Set up static routes</a> or
-  <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
+- <a href={props.mtLpStaticRoute}>Set up static routes</a> or <a href={props.mtLpBgpPeering}>BGP peering (beta)</a>.
 - [Configure health checks](/magic-transit/network-health/run-endpoint-health-checks/).
 - Confirm you properly configured [tunnel](/magic-transit/network-health/update-tunnel-health-checks-frequency/) and endpoint health checks.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.
 
-When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
+When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency">Letter of Agency (LOA)</GlossaryTooltip>. When using Cloudflare-leased IPs, Cloudflare automatically enables [Magic Transit Egress](/magic-transit/reference/egress/), which routes your egress traffic to Cloudflare instead of the Internet. Set up policy-based routing on your end to ensure return traffic routes properly.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
index df51d0077eac1b3..312b1d8e17bf88c 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-gre.mdx
@@ -5,9 +5,11 @@
 The MSS value depends on how your network is set up.
 
 - **Magic Transit ingress-only traffic (DSR):**
+
   - **On your edge router transit ports**: Set a TCP MSS clamp to a maximum of 1,436 bytes.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: Apply the MSS clamp on the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce the current value by 24 bytes.
 
 - **For Magic Transit ingress + egress traffic:**
+
   - **On the Magic Transit GRE tunnel internal interface**: Meaning where the Magic Transit egress traffic will traverse. Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 24 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
index 9724b74d99a9784..ca0dc864b8bd976 100644
--- a/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
+++ b/src/content/partials/networking-services/magic-transit/mtu-mss/mss-clamping-ipsec.mdx
@@ -5,9 +5,11 @@
 For IPsec tunnels, the value you need to specify depends on how your network is set up. The MSS clamping value is lower than for GRE tunnels because the physical interface sees IPsec-encrypted [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/), not TCP packets, and MSS clamping does not apply to those.
 
 - **Magic Transit ingress-only traffic (DSR):**
+
   - **On your edge router transit ports**: Set the TCP MSS clamp to 1,436 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the GRE-terminating router) to reduce its current value by 140 bytes.
 
 - **Magic Transit ingress + egress traffic:**
+
   - **On your edge router**: Apply this on your Magic Transit IPsec tunnel internal interface (that is, where the Magic Transit egress traffic will traverse). Your devices may do this automatically once the tunnel is configured, but it depends on your devices. Set the TCP MSS clamp to 1,360 bytes maximum.
   - **On any IPsec/GRE tunnels with third parties on your Magic Transit prefix**: On the internal tunnel interface (most likely on a separate firewall behind the IPsec-terminating device in your premises) to reduce its current value by 140 bytes.
diff --git a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
index 5768c1e380eceba..b760409416dfd6f 100644
--- a/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
+++ b/src/content/partials/networking-services/magic-transit/safely-withdraw-byoip-prefix.mdx
@@ -18,8 +18,8 @@ The following steps outline the recommended multi-step draining process to achie
 2. **Wait for global BGP convergence**: Allow a period of time (typically five to ten minutes) for the new native advertisement to propagate fully across the global routing table, and for routes to converge. This passive waiting period ensures that the majority of traffic has shifted to your local network before the next step.
 3. **Signal BGP withdrawal from the Cloudflare edge**: Once you have verified that traffic has successfully drained, use one of the BGP control methods to stop the advertisement of the prefix from the Cloudflare edge.
 
-   :::caution[ISP route refresh delays may impact traffic]
-   Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
-   :::
+	:::caution[ISP route refresh delays may impact traffic]
+	Cloudflare's action to withdraw the route is near-instantaneous across our global network. However, Cloudflare has no control over how quickly external ISPs refresh their BGP tables after the withdrawal.
+	:::
 
-4. The draining process is complete.
+4. The draining process is complete.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/magic-user-role.mdx b/src/content/partials/networking-services/magic-user-role.mdx
index 72715ce73e544d4..5f688524a5b726f 100644
--- a/src/content/partials/networking-services/magic-user-role.mdx
+++ b/src/content/partials/networking-services/magic-user-role.mdx
@@ -12,7 +12,7 @@ For example, if multiple teams manage different Cloudflare products on the same
 
 1. Go to the **Members** page.
 
-   <DashButton url="/?to=/:account/members" />
+	 <DashButton url="/?to=/:account/members" />
 
 2. Under **Members**, enter an existing user's name and select **Search**.
 3. Expand the menu at the end of the user row.
diff --git a/src/content/partials/networking-services/mconn/device-metrics.mdx b/src/content/partials/networking-services/mconn/device-metrics.mdx
index 278ab4d0b610b62..a2fad49b670b4f3 100644
--- a/src/content/partials/networking-services/mconn/device-metrics.mdx
+++ b/src/content/partials/networking-services/mconn/device-metrics.mdx
@@ -13,59 +13,59 @@ For example:
 
 ```graphql graphql-api-explorer
 query telemetry(
-	$accountTag: string
-	$snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
-	$snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
-	$snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
-	$limit: int64!
+  $accountTag: string
+  $snapshotsFilter: AccountMconnTelemetrySnapshotsAdaptiveGroupsFilter_InputObject!
+  $snapshotMountsFilter: AccountMconnTelemetrySnapshotMountsAdaptiveGroupsFilter_InputObject!
+  $snapshotThermalsFilter: AccountMconnTelemetrySnapshotThermalsAdaptiveGroupsFilter_InputObject!
+  $limit: int64!
 ) {
-	viewer {
-		accounts(filter: { accountTag: $accountTag }) {
-			snapshots: mconnTelemetrySnapshots(
-				filter: $snapshotsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC]
-			) {
-				max {
-					cpuCount
-					loadAverage1m
-					memoryFreeBytes
-					memoryTotalBytes
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-			snapshotMounts: mconnTelemetrySnapshotMounts(
-				filter: $snapshotMountsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC]
-			) {
-				max {
-					availableBytes
-					totalBytes
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-			snapshotThermals: mconnTelemetrySnapshotThermals(
-				filter: $snapshotThermalsFilter
-				limit: $limit
-				orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
-			) {
-				max {
-					currentCelsius
-				}
-				dimensions {
-					connectorId
-					datetimeFiveMinutes
-				}
-			}
-		}
-	}
+  viewer {
+    accounts(filter: { accountTag: $accountTag }) {
+      snapshots: mconnTelemetrySnapshots(
+        filter: $snapshotsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC]
+      ) {
+        max {
+          cpuCount
+          loadAverage1m
+          memoryFreeBytes
+          memoryTotalBytes
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+      snapshotMounts: mconnTelemetrySnapshotMounts(
+        filter: $snapshotMountsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC]
+      ) {
+        max {
+          availableBytes
+          totalBytes
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+      snapshotThermals: mconnTelemetrySnapshotThermals(
+        filter: $snapshotThermalsFilter
+        limit: $limit
+        orderBy: [datetimeFiveMinutes_DESC, connectorId_DESC]
+      ) {
+        max {
+          currentCelsius
+        }
+        dimensions {
+          connectorId
+          datetimeFiveMinutes
+        }
+      }
+    }
+  }
 }
 ```
 
@@ -75,4 +75,4 @@ The metric `average CPU load` is unique and distinctly different from `CPU utili
 
 CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the Cloudflare One Appliance CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
 
-Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
+Cloudflare is still evaluating the typical CPU load operating range on the Cloudflare One Appliance. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Cloudflare One Appliance performance if the average CPU load is consistently above 100%.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/licence-keys.mdx b/src/content/partials/networking-services/mconn/licence-keys.mdx
index 19fc13fb15ac9ea..762bbc9168a849d 100644
--- a/src/content/partials/networking-services/mconn/licence-keys.mdx
+++ b/src/content/partials/networking-services/mconn/licence-keys.mdx
@@ -3,6 +3,8 @@ params:
   - virtualConnectorName
 ---
 
+
+
 :::note
 You cannot use the same license key twice, or reuse a key once the virtual machine has been registered with Cloudflare. You need a new key from your account team for every new {props.virtualConnectorName}.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
index 5ed0d70f3420a55..720da967d7f0d34 100644
--- a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
@@ -7,4 +7,4 @@ params:
 Before you can activate your Cloudflare One Appliance (formerly Magic WAN Connector), you need to follow Cloudflare's instructions regarding DHCP. For instructions, refer to:
 
 - The <a href={props.hardwareConnectorURL}>hardware version of Cloudflare One Appliance</a>
-- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
+- The <a href={props.virtualConnectorURL}>virtual version of Cloudflare One Appliance</a>
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
index 69bcf5dfd06bb9d..abb2c35e51bfd08 100644
--- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -3,38 +3,38 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
-    `}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. From the list, find the Cloudflare One Appliance you want to deactivate > select the three dots next to it > **Edit**.
+	`}
+	inline={false}
+	/>
+	</>
 )
-} 4. In **Status**, select _Deactivated_ from the drop-down menu. 5. Select **Update**.
+}
+4. In **Status**, select _Deactivated_ from the drop-down menu.
+5. Select **Update**.
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index e2cb63fb178ba6b..0946f2695192a8a 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -12,4 +12,4 @@ The default password for Cloudflare One Appliance is the serial number (also kno
 
 The default password for Virtual Appliance is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
 
-For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
+For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
index 20bffc12db414cc..b11277c02a77557 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -8,33 +8,34 @@ import { DashButton, Markdown } from "~/components";
 In **Basic information**, you can change the name and description of your Cloudflare One Appliance (formerly Magic WAN Connector).
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**. 4. In **Basic information** make the necessary changes. 5. Select **Save**.
+}
+3. Find the Cloudflare One Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. In **Basic information** make the necessary changes.
+5. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
index 16e6075ed0b533e..f71c11c0de55a12 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -6,32 +6,36 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Connectors** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**. 5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**. 6. Make the necessary changes. 7. Select **Save**.
+}
+3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**.
+5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**.
+6. Make the necessary changes.
+7. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
index e0c56079072bb08..7a5e68df4e8f5b2 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
@@ -6,35 +6,35 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a> > **Insights**.
 		2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on.
 		3. Select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-<Markdown
-text={`
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/networking-insights/health" />
+				<Markdown
+	text={`
 		3. Find the site you want to make changes on > select the three dots next to it > **Edit**.
 		4. In **Basic information**, make changes to the site's name, description, and geographic coordinates.
 		5. In **On-ramps**, add new on-ramps to your site. You can also remove existing ones.
 		`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
index 79373537351ff1d..267156ca7a1e2d3 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -8,33 +8,35 @@ import { DashButton, Markdown } from "~/components";
 You can only add or remove applications to Breakout traffic and Prioritized traffic. To add or remove applications:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**. 4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**. 5. Select **Add** to add a new application. 6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
+}
+3. Find the Appliance that you want to edit > select the three dots next to it > **Edit**.
+4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**.
+5. Select **Add** to add a new application.
+6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
index 6a9d81008d379c6..c8f54f97a753b77 100644
--- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -3,7 +3,7 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 Cloudflare One Appliance (formerly Magic WAN Connector) communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
@@ -18,34 +18,33 @@ There are three symbols for the heartbeat signal that allow you to quickly check
 ### Access Cloudflare One Appliance's heartbeat
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 		3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Go to the **Connectors** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
-    `}
-    inline={false}
-    />
-    </>
-
+	inline={false}
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
+
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. From the list, find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare.
+	`}
+	inline={false}
+	/>
+	</>
 )
 }
diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
index e0ac8962997b44f..b94efb16efe2c31 100644
--- a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
@@ -3,43 +3,42 @@ params:
   - dashName
 ---
 
-import { DashButton, Markdown } from "~/components";
+import { DashButton, Markdown } from '~/components';
 
 The Interrupt window defines when Cloudflare One Appliance (formerly Magic WAN Connector) can update its systems. When Cloudflare One Appliance is updating, this may result in an interruption to existing connections. Set up a time window that minimizes disruption to your sites.
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks** > **Connectors**.
 		2. In **Appliances** > **Appliances**, select the Cloudflare One Appliance for which you want to set up the update window > **Edit**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
+	<>
 
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
-    `}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		3. Find the Cloudflare One Appliance you want to set up the update window for > **Edit**.
+	`}
+	inline={false}
+	/>
+	</>
 )
-} 3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
-
-- **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
-- **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
-- **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
+}
+3. In **Interrupt window**, select the most appropriate time for the Cloudflare One Appliance to update its systems:
+   - **Timezone**: Select the time zone for the Cloudflare One Appliance to update.
+   - **Start time**: Choose an hour for the Cloudflare One Appliance to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
+   - **Duration**: Duration indicates the time window during which the Cloudflare One Appliance is scheduled to update. For example, if you configure your Cloudflare One Appliance to update at `22:00` and specify a **Duration** of `4 hours`, the Cloudflare One Appliance will attempt to update within the four-hour period following `22:00`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
index 622bec3086c2415..ad72dcbe7fe8d77 100644
--- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
@@ -9,27 +9,30 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag
 
 {/* Dashboard steps for CF1 Cloudflare WAN (Cloudflare One dashboard) */}
 { props.dashName === "CF1 Cloudflare WAN" && (
-<>
-<ol>
-<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
-<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
-</ol>
-</>
+	<>
+	<ol>
+		<li>Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to <strong>Networks</strong>.</li>
+		<li>Go to <strong>Connectors</strong> &gt; <strong>Appliances</strong>, and select <strong>Register an appliance</strong>.</li>
+	</ol>
+	</>
 )
 }
 
 {/* Dashboard steps for Cloudflare WAN (standalone dashboard) */}
 { props.dashName !== "CF1 Cloudflare WAN" && (
-<>
-<ol>
-<li>Go to the <strong>Connectors</strong> page.
-<br />
-<DashButton url="/?to=/:account/magic-networks/connections" />
-</li>
-<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
-</ol>
-</>
+	<>
+	<ol>
+		<li>Go to the <strong>Connectors</strong> page.
+			<br />
+			<DashButton url="/?to=/:account/magic-networks/connections" />
+		</li>
+		<li>In the <strong>Appliances</strong> tab &gt; <strong>Appliances</strong>, select <strong>Register an appliance</strong>.</li>
+	</ol>
+	</>
 )
-} 3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard. 4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account. 5. Select **Register appliance**.
+}
+3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Cloudflare One Appliance you are adding to the dashboard.
+4. (Optional) Select **Add** under **Serial number** to add multiple Cloudflare One Appliances at once to your account.
+5. Select **Register appliance**.
 
-Your device is now registered with your account.
+Your device is now registered with your account.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
index b9ba61db220dfb4..fa154fec8acde27 100644
--- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx
@@ -6,7 +6,6 @@ params:
 import { DashButton, Markdown } from "~/components";
 
 When adding or removing Cloudflare One Appliances (formerly Magic WAN Connectors), you need to be aware of the difference between the physical device and its profile.
-
 - The physical device is the hardware at your site.
 - The profile contains the configuration that allows the device to connect to Cloudflare, including your WANs, LANs, traffic steering, and LAN policies.
 
@@ -15,69 +14,67 @@ You can have more than one Cloudflare One Appliance in one profile if you initia
 ## Remove a profile
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Profiles**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to **Appliances** > **Profiles**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to **Appliances** > **Profiles**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
+}
+3. Find the profile that you want to edit > select the three dots next to it > **Delete**.
 
 ## Remove a physical device
 
 To remove a Cloudflare One Appliance from your account:
 
 { props.dashName === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+		<Markdown
+	text={`
 		1. Log in to <a href="https://one.dash.cloudflare.com/">Cloudflare One</a>, and go to **Networks**.
 		2. Go to **Connectors** > **Appliances** > **Appliances**.
 	`}
-inline={false}
-/>
-</>
+	inline={false}
+	/>
+	</>
 ) : (
-<>
-
+	<>
 <Markdown
 	text={`
 		1. Go to the **Connectors** page.
 		`}
 	inline={false}
-/>
-<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    	<Markdown
-    text={`
-    	2. Go to the **Appliances** tab > **Appliances**.
-    	`}
-    inline={false}
-    />
-    </>
+	/>
+		<DashButton url="/?to=/:account/magic-networks/connections" />
 
+		<Markdown
+	text={`
+		2. Go to the **Appliances** tab > **Appliances**.
+		`}
+	inline={false}
+	/>
+	</>
 )
-} 3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
+}
+3. Find the Cloudflare One Appliance that you want to delete > select the three dots next to it > **Delete**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 58394a01819ac0d..5dc4a5441cd0fde 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -16,7 +16,7 @@ params:
   - networkSegmentationURL
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components"
 
 The Cloudflare One Appliance (formerly Magic WAN Connector) software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
 
@@ -91,14 +91,11 @@ When a failover occurs, traffic is moved to the new active node. It could take u
 
 This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
 
-<Render
-	file="mconn/wan-two-tunnels"
-	product="networking-services"
-	params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }}
-/>
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Cloudflare One Appliance", dashName: props.dashName }} />
 
 When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in Cloudflare One Appliance routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 
+
 Creating several WAN connections also means Cloudflare One Appliance can failover between circuits according to their health.
 
 ### High-capacity use cases
@@ -111,7 +108,7 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ### WAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using Virtual Appliance, this needs to correspond to the virtual network interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
 - **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. For details on how Cloudflare calculates priorities, refer to <a href={props.trafficSteeringURL}>Traffic steering</a>.
 - **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. For details, refer to <a href={props.hcFrequencyURL}>Update tunnel health checks frequency</a>.
@@ -119,9 +116,9 @@ If you do not have more than one anycast IP configured in your account, and you
 
 ## LAN settings
 
-- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br /> If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
+- **Interface number:** When using the hardware version of Cloudflare One Appliance, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. For details on supported hardware, refer to <a href={props.sfpURL}>SFP+ port information</a>. <br />  If you are using the Virtual Appliance, this needs to correspond to the virtual LAN interface on the Virtual Appliance instance you have set up in your virtual machine.
 - **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Cloudflare One Appliance. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
-- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
+- **Static addressing:** Configures the type of IP addressing for your Appliance. Depending on your use case, this is where you configure your LAN interface IP address, or enable  DHCP server or DHCP relay. For details, refer to <a href={props.dhcpURL}>DHCP options</a>.
 - **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
 - **Routed subnets:** Configures additional subnets behind a layer 3 router. For details, refer to <a href={props.routedSubnetsURL}>Routed subnets</a>.
 
@@ -129,4 +126,4 @@ If you do not have more than one anycast IP configured in your account, and you
 
 Depending on your use case, you can define policies in your Cloudflare One Appliance to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
-For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
+For details, refer to <a href={props.networkSegmentationURL}>Network segmentation</a>.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index d64025ffaf32777..7eb868cf827fa41 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -7,64 +7,53 @@ params:
   - dashName
 ---
 
-import {
-	APIRequest,
-	Aside,
-	AnchorHeading,
-	CURL,
-	DashButton,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-} from "~/components";
+import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
 
 { props.magicWord === "breakout" && (
-<>
-<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
-<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-</>
-)
+	<>
+		<p>Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Cloudflare One Appliance (formerly Magic WAN Connector) can detect. This can take several minutes.</p>
+		<Aside type="caution">Breakout traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+	</>
+	)
 }
 
 { props.magicWord === "prioritized" && (
-<>
-<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
-<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
-<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
-</>
-)
+	<>
+		<p>Prioritized traffic allows you to define which applications Cloudflare One Appliance (formerly Magic WAN Connector) should process first. Applications not in the list will be queued behind prioritized traffic.</p>
+		<p>Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.</p>
+		<Aside type="caution">Prioritized traffic will not work for applications that use DNS-over-HTTPS.</Aside>
+	</>
+	)
 }
 
 { props.magicWord === "breakout" && (
-<>
-<pre class="mermaid">
-{`
-flowchart LR
-accTitle: Breakout traffic flow
-accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
-a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
-
-    		a-- Breakout traffic ---d(Application1) & e(Application2) --> c
-
-    		classDef orange fill:#f48120,color: black
-    		class a,b orange
-    		`}
-    	</pre>
-    	<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
-    	<Aside type="note" title="A note on security">
-    	<Markdown
-    	text={`
-    	We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
+	<>
+		<pre class="mermaid">
+			{`
+			flowchart LR
+			accTitle: Breakout traffic flow
+			accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
+			a(Cloudflare One Appliance) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
+
+			a-- Breakout traffic ---d(Application1) & e(Application2) --> c
+
+			classDef orange fill:#f48120,color: black
+			class a,b orange
+			`}
+		</pre>
+		<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
+		<Aside type="note" title="A note on security">
+		<Markdown
+		text={`
+		We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.
 
     For details on how Cloudflare routes traffic, refer to <a href="${props.trafficSteeringURL}">Traffic steering</a>.
-    	`}
-    	inline={false}
-    	/>
-    	</Aside>
-    </>
-    )
-
+		`}
+		inline={false}
+		/>
+		</Aside>
+	</>
+	)
 }
 
 ## Add an application to your account
@@ -75,28 +64,28 @@ To add applications to your account:
 
 Send a `POST` request to add new apps to your account.
 
-    <APIRequest
-    path="/accounts/{account_id}/magic/apps"
-    method="POST"
-    json={{
+	<APIRequest
+	path="/accounts/{account_id}/magic/apps"
+	method="POST"
+	json={{
     "managed_app_id": "<APP_ID>",
     "name": "<APP_NAME>",
     "type": "<APP_TYPE>",
-    }}
-    />
-
-    ```json output
-    {
-    	"result": {
-    		"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
-    		"name": "<APP_NAME>",
-    		"type": "<APP_TYPE>",
-    	},
-    	"success": true,
-    	"errors": [],
-    	"messages": []
-    }
-    ```
+	}}
+	/>
+
+	```json output
+	{
+		"result": {
+			"account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
+			"name": "<APP_NAME>",
+			"type": "<APP_TYPE>",
+		},
+		"success": true,
+		"errors": [],
+		"messages": []
+	}
+	```
 
 You can now add this new app to the {props.featureName} list in your Cloudflare One Appliance.
 
@@ -326,88 +315,87 @@ You need to delete {props.featureName} applications for each of your existing si
 </TabItem> </Tabs>
 
 { props.magicWord === "breakout" && (
-<>
-<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
-
-    	<Markdown
-    	text={`
+	<>
+		<AnchorHeading title="Designate WAN ports for breakout apps" depth={2} />
 
+		<Markdown
+		text={`
 You can pin applications to a specific WAN port in Cloudflare One Appliance when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, Cloudflare One Appliance automatically fails over to a standard configured WAN port priority.
 
 With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
 
 To pin applications to a WAN port:
-`}
-inline={false}
-/>
-
-    	{ props.dashName === "CF1 Cloudflare WAN" ? (
-    		<>
-    			<Markdown
-    		text={`
-    			1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
-    			2. Go to **Connectors** > **Appliances** > **Profiles**.
-    			3. Select the Cloudflare One Appliance you want to configure > **Edit**.
-    		`}
-    		inline={false}
-    		/>
-    		</>
-    	) : (
-    		<>
-    		<Markdown
-    			text={`
-    				1. Go to the **Connectors** page.
-    				`}
-    			inline={false}
-    			/>
-    				<DashButton url="/?to=/:account/magic-networks/connections" />
-
-    				<Markdown
-    			text={`
-    				2. Go to the **Appliances** tab > **Profiles**.
-    				`}
-    			inline={false}
-    			/>
-    			<Markdown
-    		text={`
-    			3. Select your Appliance > **Edit**.
-    		`}
-    		inline={false}
-    		/>
-    		</>
-    	)
-    	}
-    	<Markdown
-    	text={`
-    	4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
-    	5. Select the three dots next to it > **Edit application traffic**.
-    	6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
-    	7. Select **Save**.
-    	`}
-    	inline={false}
-    	/>
-    </>
-
+		`}
+		inline={false}
+		/>
+
+		{ props.dashName === "CF1 Cloudflare WAN" ? (
+			<>
+				<Markdown
+			text={`
+				1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
+				2. Go to **Connectors** > **Appliances** > **Profiles**.
+				3. Select the Cloudflare One Appliance you want to configure > **Edit**.
+			`}
+			inline={false}
+			/>
+			</>
+		) : (
+			<>
+			<Markdown
+				text={`
+					1. Go to the **Connectors** page.
+					`}
+				inline={false}
+				/>
+					<DashButton url="/?to=/:account/magic-networks/connections" />
+
+					<Markdown
+				text={`
+					2. Go to the **Appliances** tab > **Profiles**.
+					`}
+				inline={false}
+				/>
+				<Markdown
+			text={`
+				3. Select your Appliance > **Edit**.
+			`}
+			inline={false}
+			/>
+			</>
+		)
+		}
+		<Markdown
+		text={`
+		4. In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
+		5. Select the three dots next to it > **Edit application traffic**.
+		6. From the **Preferred breakout port** drop-down menu, select the WAN port you want to assign to the applications.
+		7. Select **Save**.
+		`}
+		inline={false}
+		/>
+	</>
 )
 }
 
+
 {props.magicWord === "breakout" && (
-<>
-<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
-</>
-)
+	<>
+		<Render	file="mconn/network-options/app-aware-policies/netflow" product="networking-services" />
+	</>
+	)
 }
 
 { props.magicWord === "breakout" && (
-<>
-<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
-<Render
-file="mconn/network-options/app-aware-policies/warp-traffic"
-product="networking-services"
-params={{
+	<>
+	<AnchorHeading title="Cloudflare One Client traffic" depth={2} />
+		<Render
+			file="mconn/network-options/app-aware-policies/warp-traffic"
+			product="networking-services"
+			params={{
 				warpFirewallURL: "/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/"
 			}}
-/>
-</>
-)
-}
+			/>
+	</>
+	)
+}
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
index 126ebd7f08071e4..70f81778279f769 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/netflow.mdx
@@ -14,11 +14,7 @@ The Cloudflare One Appliance uses NetFlow v9 to export flow data for breakout tr
 
 ### Enable NetFlow exports
 
-<Render
-	file="account-id-api-key"
-	product="networking-services"
-	params={{ showSiteId: true }}
-/>
+<Render file="account-id-api-key" product="networking-services" params={{ showSiteId: true }} />
 
 1. Send a `PUT` request to the Netflow configuration endpoint for your site.
 2. In the JSON body request, you must include the `collector_ip` parameter. To export traffic statistics to Network Flow, use the IP address `162.159.65.1`. This is the only field required to enable the feature.
@@ -29,12 +25,11 @@ Minimal configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		collector_ip: "162.159.65.1",
+		"collector_ip": "162.159.65.1"
 	}}
 />
 
 3. You can customize the configuration by adding optional fields to the JSON payload. These fields include:
-
 - `collector_port`: The UDP port for the collector. The default is `2055`.
 - `sampling_rate`: The rate at which packets are sampled.
 - `active_timeout`: The timeout for active flows in seconds.
@@ -46,11 +41,11 @@ Full configuration example:
 	url="https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config"
 	method="PUT"
 	json={{
-		collector_ip: "162.159.65.1",
-		collector_port: 2055,
-		sampling_rate: 100,
-		active_timeout: 60,
-		inactive_timeout: 30,
+		"collector_ip": "162.159.65.1",
+		"collector_port": 2055,
+		"sampling_rate": 100,
+		"active_timeout": 60,
+		"inactive_timeout": 30
 	}}
 />
 
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
index f3203bf58619f2c..1d2567a03ec9803 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
@@ -4,7 +4,7 @@ params:
   - appTypesGatewayURL
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing } from "~/components"
 
 Standard traffic policies match on network-layer attributes like IP addresses and port ranges. Application-aware policies go further — they identify traffic by the application generating it, so you can make routing and security decisions based on what the traffic is, not just where it is going.
 
@@ -19,4 +19,5 @@ With application-aware policies, you can:
 
 For details, refer to the following pages:
 
-<DirectoryListing />
+
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
index 4ef40f59c1c2bc9..a00df21396023ca 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -5,14 +5,7 @@ params:
   - cfVsCoreDashNamingMwanCni
 ---
 
-import {
-	APIRequest,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
 
 DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, Cloudflare One Appliance (formerly Magic WAN Connector) forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
index 3a9c1d021abc578..94056a78a61e391 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
@@ -3,14 +3,7 @@ params:
   - dashName
 ---
 
-import {
-	APIRequest,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-	DashButton,
-} from "~/components";
+import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
 
 When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN Connector) can also act as a DHCP server in your network. To enable this feature:
 
diff --git a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
index dfd266a24e6682a..000cfd917c0229e 100644
--- a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
@@ -63,3 +63,4 @@ For step-by-step instructions to configure a LAN and supply a static NAT prefix,
 
 - <a href={props.hardConnectorURL}>Configure hardware Appliance</a>
 - <a href={props.virtualConnectorURL}>Configure Virtual Appliance</a>
+
diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
index 079bcbe7f92895c..6243e2b3a08d8e5 100644
--- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -5,14 +5,7 @@ params:
   - virtualConnectorURL
 ---
 
-import {
-	APIRequest,
-	DashButton,
-	Markdown,
-	Render,
-	TabItem,
-	Tabs,
-} from "~/components";
+import { APIRequest, DashButton, Markdown, Render, TabItem, Tabs } from "~/components";
 
 You can define policies in your Cloudflare One Appliance (formerly Magic WAN Connector) to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
 
diff --git a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
index 22273d0546df33d..9509f4c9fe5a7d6 100644
--- a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
@@ -44,7 +44,7 @@ Blue represents directly-attached subnets, and red represents routed subnets.
 	`}
 </pre>
 
-<br />
+<br/>
 
 To add a routed subnet to your LAN, you need:
 
diff --git a/src/content/partials/networking-services/mconn/overview.mdx b/src/content/partials/networking-services/mconn/overview.mdx
index 0aaac9276dd0f51..7ac69fc4e47b806 100644
--- a/src/content/partials/networking-services/mconn/overview.mdx
+++ b/src/content/partials/networking-services/mconn/overview.mdx
@@ -19,4 +19,4 @@ Either option ensures the best possible connectivity to the closest Cloudflare n
 
 Review this section to learn how to configure and deploy {props.hardwareProductName}.
 
-<DirectoryListing />
+<DirectoryListing />
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
index 3c1e9c89c2d55cc..1680225d6dfcefe 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
@@ -19,11 +19,7 @@ Cloudflare customers can inspect metrics for a specific Cloudflare One Appliance
 
 To find the information above and start troubleshooting your Cloudflare One Appliance:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 
 ### Performance analytics
 
@@ -37,11 +33,7 @@ In Performance analytics you can review your Cloudflare One Appliance's performa
 
 To access performance analytics:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **Performance analytics**.
 
 ### Port analytics
@@ -53,11 +45,7 @@ Port analytics gives you access to information related to the packets sent and r
 
 The dashboard provides this information for all active ports in your Cloudflare One Appliance. To access port analytics:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **Port analytics**.
 
 ### Event logs
@@ -83,22 +71,15 @@ Use Event logs to identify general patterns and changes over time. This is usefu
 
 To access event logs:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
-4. Select **Events**. 5. You can filter results by specific events, and by time.
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
+4. Select **Events**.
+5. You can filter results by specific events, and by time.
 
 ### DHCP leasing
 
 The DHCP leasing section identifies DHCP assigned leases and their expiration dates. To access DHCP leasing:
 
-<Render
-	file="mconn/troubleshooting/troubleshooting-steps"
-	product="networking-services"
-	params={{ dashName: props.dashName }}
-/>
+<Render file="mconn/troubleshooting/troubleshooting-steps"	product="networking-services" params={{ dashName: props.dashName }} />
 4. Select **DHCP leasing**.
 
 ## Troubleshooting tips
diff --git a/src/content/partials/networking-services/mconn/vlan-tagging.mdx b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
index 787946548bcc7a4..d13dfd1e5a4f2a6 100644
--- a/src/content/partials/networking-services/mconn/vlan-tagging.mdx
+++ b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
@@ -17,4 +17,4 @@ Use VLAN ID <code>0</code> when:
 You can also configure subinterfaces on the {props.virtualConnectorName} by associating the network interface with a Port Group or Distributed Port Group trunk and specifying a VLAN ID in addition to the port associated with the network interface (VLAN ID <code>1</code>-<code>4094</code>).
 
 Refer to <Markdown text={props.url} /> for more information.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
index bce930a2152d57d..304d1616c387e6a 100644
--- a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
+++ b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
@@ -4,4 +4,4 @@ params:
   - dashName
 ---
 
-When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
+When you have more than one anycast IP configured in your account (set up during your Cloudflare WAN (formerly Magic WAN) onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
index 5419d89b875b933..3bf575d2cf83e7d 100644
--- a/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
+++ b/src/content/partials/networking-services/mnm-auto-advertisement-notifications.mdx
@@ -11,4 +11,4 @@ You will receive the status of the advertisement for each prefix with the follow
 - **Delayed**: The prefix cannot currently be advertised but will attempt advertisement. After the prefix can be advertised, a new notification is sent with the updated status.
 - **Locked**: The prefix is locked and cannot be advertised.
 - **Could not Advertise**: Cloudflare was unable to advertise the prefix. This status can occur for multiple reasons, but usually occurs when you are not allowed to advertise a prefix.
-- **Error**: A general error occurred during prefix advertisement.
+- **Error**: A general error occurred during prefix advertisement.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
index 7b58e1a58a4bed2..0090ebe938488ea 100644
--- a/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
+++ b/src/content/partials/networking-services/mnm-magic-transit-integration.mdx
@@ -17,19 +17,15 @@ After Magic Transit activates and your traffic flows through Cloudflare, Cloudfl
 The following diagrams illustrate this process:
 
 <Width size="large">
-	![The diagram shows the flow of traffic when you send flow data from your
-	network to Cloudflare for
-	analysis.](~/assets/images/network-flow/1-flowdata.png)
+	![The diagram shows the flow of traffic when you send flow data from your network to Cloudflare for analysis.](~/assets/images/network-flow/1-flowdata.png)
 </Width>
 
 <Width size="large">
-	![Cloudflare automatically notifies you when Cloudflare detects an attack
-	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
+	![Cloudflare automatically notifies you when Cloudflare detects an attack	based on your flow data.](~/assets/images/network-flow/2-flowdata.png)
 </Width>
 
 <Width size="large">
-	![You can create rules to activate Magic Transit automatically, to protect
-	your IP addresses from a DDoS
+	![You can create rules to activate Magic Transit automatically, to protect your IP addresses from a DDoS
 	attack.](~/assets/images/network-flow/3-flowdata.png)
 </Width>
 
diff --git a/src/content/partials/networking-services/mnm/faqs.mdx b/src/content/partials/networking-services/mnm/faqs.mdx
index b0208fe02c88cf2..b4a27eb520e6d6c 100644
--- a/src/content/partials/networking-services/mnm/faqs.mdx
+++ b/src/content/partials/networking-services/mnm/faqs.mdx
@@ -6,7 +6,7 @@ If you cannot find your answer here, refer to the [community page](https://commu
 
 ## I am getting an "Invalid account settings request body: account name format contains illegal characters or is not supported" error when trying to create a rule.
 
-This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
+This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 
diff --git a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
index 46c472367567090..cd765351f8a8f43 100644
--- a/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
+++ b/src/content/partials/networking-services/mnm/routers/sflow-config.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 Configure your router to export <GlossaryTooltip term="sFlow">sFlow</GlossaryTooltip> data to Cloudflare's network for analysis in Network Flow (formerly Magic Network Monitoring). sFlow is a network monitoring protocol that samples network traffic to provide visibility into your network's performance and traffic patterns.
 
diff --git a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
index c117433d7d663dc..4cbd7f7fa55f513 100644
--- a/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx
@@ -8,14 +8,14 @@ To use dynamic threshold rules, you must send NetFlow or sFlow data to Cloudflar
 
 ## Rule configuration fields
 
-| Field                  | Description                                                                                                                                                                                                                                                                                                                                              |
-| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                               |
-| **Rule type**          | zscore                                                                                                                                                                                                                                                                                                                                                   |
-| **Target**             | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                                          |
-| **Sensitivity**        | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic.                                                                                                                                                                             |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | zscore |
+| **Target** | Can be defined in either bits per second or packets per second. |
+| **Sensitivity** | Controls how easily traffic anomalies trigger alerts. Available values: low, medium, and high. Higher sensitivity triggers alerts on smaller deviations from normal traffic. |
 | **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. Network Flow supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/network-flow/rules/#rule-auto-advertisement). |
-| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section.                                                                      |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes) section. |
 
 ## API documentation
 
@@ -33,4 +33,4 @@ Z = (X - μ) / σ
 
 - `X` = Current traffic value.
 - `μ` = Mean traffic value over the long window.
-- `σ` = Standard deviation over the long window.
+- `σ` = Standard deviation over the long window.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/overview.mdx b/src/content/partials/networking-services/mnm/rules/overview.mdx
index f604442b91f7228..64c496cc2672375 100644
--- a/src/content/partials/networking-services/mnm/rules/overview.mdx
+++ b/src/content/partials/networking-services/mnm/rules/overview.mdx
@@ -25,7 +25,7 @@ If you get the following error when trying to create a rule:
 
 `Invalid account settings request body: account name format contains illegal characters or is not supported`
 
-Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, `` ` ``.
+Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
 Refer to [Account name](/fundamentals/account/create-account/#account-name) to learn how to change your account name.
 :::
diff --git a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
index 2a6ee954fa33c84..cc8a9232c23298e 100644
--- a/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
+++ b/src/content/partials/networking-services/mnm/rules/rule-notifications.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { Render, DashButton } from "~/components";
+import { Render, DashButton } from "~/components"
 
 Network Flow (formerly Magic Network Monitoring) can notify you by email, webhook, or PagerDuty when a rule is triggered. When a rule detects a traffic anomaly, notifications alert your team so you can respond — or, if you use Magic Transit with auto-advertisement, Cloudflare can begin mitigating the attack automatically.
 
@@ -16,19 +16,16 @@ For more information on the notification platform, refer to [Notifications docum
 
 ## Notification configuration fields
 
-| Field                      | Description                                                       |
-| :------------------------- | :---------------------------------------------------------------- |
-| **Notification name**      | A label to identify this notification in your notifications list. |
-| **Description (optional)** | The description of the notification.                              |
-| **Webhooks**               | One or more webhooks to deliver the notification to.              |
-| **Notification email**     | One or more email addresses to deliver the notification to.       |
+| Field | Description |
+| :---- | :---- |
+| **Notification name** | A label to identify this notification in your notifications list. |
+| **Description (optional)** | The description of the notification. |
+| **Webhooks** | One or more webhooks to deliver the notification to. |
+| **Notification email** | One or more email addresses to deliver the notification to. |
 
 ## Rule Auto-Advertisement notifications
 
-<Render
-	file="mnm-auto-advertisement-notifications"
-	product="networking-services"
-/>
+<Render file="mnm-auto-advertisement-notifications" product="networking-services" />
 
 ## Configure rule notifications
 
@@ -44,4 +41,4 @@ To configure notifications for Network Flow rules:
    - **Network Flow: Volumetric Attack** - for static threshold and dynamic threshold notifications
    - **Network Flow: DDoS Attack** - for sFlow DDoS attack notifications
 5. Fill in the notification configuration details.
-6. Select **Save**.
+6. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
index bec5f1386000a0d..b3e8a3d3bc9f6f8 100644
--- a/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
+++ b/src/content/partials/networking-services/mnm/rules/s-flow-ddos-attack.mdx
@@ -12,13 +12,13 @@ To send sFlow data to Cloudflare, your router must support sFlow exports. Refer
 
 ## Rule configuration fields
 
-| Field                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**          | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                                                                                                                                                                                                                              |
-| **Rule type**          | advanced_ddos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| **Prefix Match**       | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
-| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement).                                                                                                                                                                                                                                                  |
-| **Rule IP prefix**     | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes).                                                                                                                                                                                                                                                                    |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | advanced_ddos |
+| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. <br/><br/>**Subnet** (recommended): Automatically advertise if the attacked IPs are within a subnet of a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Exact**: Automatically advertise if the attacked IPs are an exact match with a public IP prefix that can be advertised by Magic Transit.<br/><br/>**Supernet**: Automatically advertise if the attacked IPs are a supernet of a public IP prefix that can be advertised by Magic Transit. |
+| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more, refer to [Auto-advertisement](/network-flow/rules/#rule-auto-advertisement). |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, refer to [Rule IP prefixes](/network-flow/rules/#rule-ip-prefixes). |
 
 ## API documentation
 
@@ -26,4 +26,4 @@ Refer to the [Rules API documentation](/api/resources/magic_network_monitoring/s
 
 ## Tune the sFlow DDoS alert thresholds
 
-You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
+You can tune the thresholds of your sFlow DDoS alerts in the dashboard and via the Cloudflare API by following the [Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/) guide.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
index 6f3111db0f8feab..8f00ec41f108d69 100644
--- a/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
+++ b/src/content/partials/networking-services/mnm/rules/static-threshold.mdx
@@ -10,15 +10,15 @@ To use static threshold rules, you must send NetFlow or sFlow data to Cloudflare
 
 ## Rule configuration fields
 
-| Field                   | Description                                                                                                                                                                                                                                                                                                                    |
-| :---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Rule name**           | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters.                                                                                                                                                     |
-| **Rule type**           | threshold                                                                                                                                                                                                                                                                                                                      |
-| **Rule threshold type** | Can be defined in either bits per second or packets per second.                                                                                                                                                                                                                                                                |
-| **Rule threshold**      | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum.                                                                                                                                       |
-| **Rule duration**       | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes.                                                                                                                                         |
-| **Auto-advertisement**  | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
-| **Rule IP prefix**      | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes).                                                                                                          |
+| Field | Description |
+| :---- | :---- |
+| **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. |
+| **Rule type** | threshold |
+| **Rule threshold type** | Can be defined in either bits per second or packets per second. |
+| **Rule threshold** | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum. |
+| **Rule duration** | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes. |
+| **Auto-advertisement** | If you are a Magic Transit On Demand customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Network Flow (formerly Magic Network Monitoring) supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](#rule-auto-advertisement). |
+| **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more, refer to [Rule IP prefixes](#rule-ip-prefixes). |
 
 ## API documentation
 
@@ -45,9 +45,9 @@ When you first configure Network Flow, you may not know the typical traffic patt
 This lets you collect baseline traffic data without receiving alerts. After configuring your initial rules, monitor for alerts and review traffic in Network Flow Analytics. Over time, update each rule's threshold based on historical traffic data.
 
 | Threshold type | Recommended rule threshold to collect initial data |
-| :------------- | :------------------------------------------------- |
-| Bits           | 10 Gbps (10,000,000,000 bits per second)           |
-| Packets        | 10 Mpps (10,000,000 packets per second)            |
+| :---- 				 | :---- 																						  |
+| Bits 					 | 10 Gbps (10,000,000,000 bits per second) 					|
+| Packets 			 | 10 Mpps (10,000,000 packets per second) 						|
 
 #### Setting the appropriate threshold
 
@@ -64,9 +64,9 @@ To find the maximum non-attack traffic for a one minute time interval over the p
 2. Select **Add filter**.
 3. In **New filter**, use the drop-down menus to create the following filter:
 
-| Field             | Operator | Rule name     |
-| :---------------- | :------- | :------------ |
-| _Monitoring Rule_ | _equals_ | `<RULE_NAME>` |
+| Field 						| Operator | Rule name 			|
+| :---- 						| :---- 	 | :---- 		 			|
+| _Monitoring Rule_ | _equals_ | `<RULE_NAME>`  |
 
 Once the rule filter is selected in Network Flow Analytics, you can check the historical traffic volume data for the rule over the selected time period. Cloudflare recommends reviewing historical data in seven-day increments, since that is the largest window that shows one-hour time intervals. To select a custom seven-day range, go to the top right corner of Network Flow analytics, open the time window drop-down menu, and select **Custom range**.
 
@@ -80,4 +80,4 @@ Your IP prefixes may experience inconsistent spikes across one-minute intervals.
 
 ### Adjusting rules over time
 
-After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
+After updating your first set of thresholds based on historical data, monitor for Network Flow alerts to verify the thresholds are appropriate. Adjust thresholds and duration over time to find the right alert sensitivity for your network environment.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
index 87ca7eb4eb1d41c..db70332705ae2dc 100644
--- a/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
+++ b/src/content/partials/networking-services/mnm/tutorials/graphql-analytics.mdx
@@ -2,6 +2,7 @@
 {}
 ---
 
+
 import { GlossaryTooltip, DashButton } from "~/components";
 
 Use the GraphQL Analytics API to retrieve Network Flow (formerly Magic Network Monitoring) <GlossaryTooltip term="flow data">flow data</GlossaryTooltip>.
diff --git a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
index 2849ce921c3e6a5..1afc04ea7741587 100644
--- a/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
+++ b/src/content/partials/networking-services/prerequisites/router-vendor-guidelines-mss-settings-origin.mdx
@@ -6,7 +6,7 @@ Instructions to adjust MSS by applying MSS clamps vary depending on the vendor o
 
 The following table lists several commonly used router vendors with links to MSS clamping instructions:
 
-| Router device | URL                                                                                                                                                                                    |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Router device | URL |
+| ---					  | --- |
 | Cisco         | [TCP IP Adjust MSS](https://www.cisco.com/en/US/docs/ios-xml/ios/ipapp/command/ip_tcp_adjust-mss_through_ip_wccp_web-cache_accelerated.html#GUID-68044D35-A53E-42C1-A7AB-9236333DA8C4) |
-| Juniper       | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html)                                           |
+| Juniper | [TCP MSS - Edit System](https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tcp-mss-edit-system.html) |
diff --git a/src/content/partials/networking-services/reference/longest-prefix-match.mdx b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
index 98fb9a953cd67de..562deeae9654317 100644
--- a/src/content/partials/networking-services/reference/longest-prefix-match.mdx
+++ b/src/content/partials/networking-services/reference/longest-prefix-match.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
+Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) always takes precedence over a less specific one (like `/29`), regardless of tunnel priority — unless you remove the more specific route.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
index 660c84eea51122e..4b89061153d1dcb 100644
--- a/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
+++ b/src/content/partials/networking-services/reference/traffic-steering-region-codes.mdx
@@ -4,14 +4,14 @@
 
 Cloudflare has nine geographic regions:
 
-| Region code | Region                |
-| ----------- | --------------------- |
-| `AFR`       | Africa                |
-| `APAC`      | Asia Pacific          |
-| `EEUR`      | Eastern Europe        |
-| `ENAM`      | Eastern North America |
-| `ME`        | Middle East           |
-| `OC`        | Oceania               |
-| `SAM`       | South America         |
-| `WEUR`      | Western Europe        |
-| `WNAM`      | Western North America |
+| Region code | Region |
+| ----- | ----- |
+| `AFR` | Africa |
+| `APAC` | Asia Pacific |
+| `EEUR` | Eastern Europe |
+| `ENAM` | Eastern North America |
+| `ME` | Middle East |
+| `OC` | Oceania |
+| `SAM` | South America |
+| `WEUR` | Western Europe |
+| `WNAM` | Western North America |
diff --git a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
index 666d6fb81f454a0..4dddd911617f979 100644
--- a/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
+++ b/src/content/partials/networking-services/reference/tunnel-health-checks.mdx
@@ -21,8 +21,7 @@ A tunnel health check probe travels from Cloudflare to the tunnel origin, then r
 	file="tunnel-health/health-checks-compatible-cmb-eu"
 	product="networking-services"
 	params={{
-		productName:
-			props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN",
+		productName: props.magicWord === "Magic Transit" ? "Magic Transit" : "Cloudflare WAN"
 	}}
 />
 
@@ -114,12 +113,12 @@ To avoid control plane policies enforced by the origin network, you can set tunn
 
 ### Summary table with tunnel health check probe types
 
-|      Attribute      |     Type      |        Unidirectional health checks        |                  Bidirectional health checks                  |
-| :-----------------: | :-----------: | :----------------------------------------: | :-----------------------------------------------------------: |
-|   Source Address    | Request Style |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
-| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-|   Source Address    |  Reply Style  | Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
-| Destination Address |  Reply Style  |   Cloudflare Address (Publicly Routable)   |       Cloudflare Interface Address (Privately Routable)       |
+| Attribute 					| Type 					| Unidirectional health checks | Bidirectional health checks |
+| :---: 							| :---: 				| :---: 											 | :---: 											 |
+| Source Address 			| Request Style | Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
+| Destination Address | Request Style | Origin Tunnel Endpoint (Publicly Routable) |Origin Interface Address (Privately Routable) / Custom Target |
+| Source Address 			| Reply Style		| Origin Tunnel Endpoint (Publicly Routable) | Origin Interface Address (Privately Routable) / Custom Target |
+| Destination Address | Reply Style 	| Cloudflare Address (Publicly Routable) | Cloudflare Interface Address (Privately Routable) |
 
 ### Graphics summarizing health check types
 
@@ -224,10 +223,9 @@ accDescr: Shows the flow of a unidirectional echo reply health check from Cloudf
 	product="networking-services"
 	params={{
 		mFirewallName: "Cloudflare Network Firewall rules",
-		mFirewallURL:
-			"/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks",
+		mFirewallURL: "/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks"
 	}}
-/>
+	/>
 
 Every Cloudflare data center configured to process your traffic sends tunnel health check probes. The rate at which Cloudflare sends these probes varies based on tunnel and location. You can tune this rate on a per-tunnel basis by modifying the `health_check` rate with the <a href={props.changeHealthCheckRate}>API or the dashboard</a>. You can set the rate as _low_, _mid_, or _high_, with _mid_ being the default.
 
@@ -235,6 +233,7 @@ The actual rate formula considers the number of servers in a Cloudflare data cen
 
 When a probe attempt fails for a <a href={props.probeHealth}>healthy tunnel</a>, each server detecting the failure quickly probes up to two more times to obtain an accurate result. Cloudflare does the same if a tunnel has been down and probes start returning success. Because Cloudflare global network servers send probes up to every second, your network will receive several hundred health check packets per second. Each Cloudflare data center sends only one health check packet as part of a probe, representing a relatively trivial amount of traffic.
 
+
 ## Health state and prioritization
 
 There are three tunnel health states: healthy, degraded, and down.
@@ -306,4 +305,4 @@ Suppose the connectivity issue that set Tunnel 1 health to down becomes resolved
 
 When all three probes return successfully, {props.productName} transitions the tunnel from down to degraded. As part of this transition, Cloudflare reduces the priority penalty for that route so that its priority becomes `500,100`. Because Tunnel 2 has a priority of `200`, traffic continues to flow over Tunnel 2.
 
-Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
+Global network servers continue probing Tunnel 1. When the health check failure rate drops below 0.1% for a five-minute period, {props.productName} sets tunnel status to healthy. Cloudflare fully restores Tunnel 1's routing priority to `100`, and traffic steering returns the data flow to Tunnel 1.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/routing/anycast-warning.mdx b/src/content/partials/networking-services/routing/anycast-warning.mdx
index 581fa4d4006258c..4a70b0d9c18b322 100644
--- a/src/content/partials/networking-services/routing/anycast-warning.mdx
+++ b/src/content/partials/networking-services/routing/anycast-warning.mdx
@@ -4,4 +4,4 @@
 
 :::caution[Anycast routing]
 Cloudflare uses anycast to route traffic. Anycast is a network addressing and routing method that routes incoming requests to different locations. Traffic can arrive at a different geographic location than expected. Not all requests go to the closest data center because Internet routing and peering relationships are complex, and Cloudflare optimizes for performance and reliability.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/routing/bgp-config-steps.mdx b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
index 49bffd5bd2831f1..ddf3fa73d94cc70 100644
--- a/src/content/partials/networking-services/routing/bgp-config-steps.mdx
+++ b/src/content/partials/networking-services/routing/bgp-config-steps.mdx
@@ -10,16 +10,16 @@ import { Aside, Markdown } from "~/components";
 5. <Markdown text={props.locateText} />
 6. In **Customer device ASN**, enter the ASN for your network.
 
-   { props.magicWord !== "Magic Transit" && (
-   <>
-   <Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
-   </>
-   )
-   }
+	{ props.magicWord !== "Magic Transit" && (
+		<>
+		<Aside type="note">Multiple tunnels or interconnects with the same ASN will not exchange routes if standard BGP loop prevention is enabled. Consider using a different ASN per session, or enabling duplicate ASNs (like Cisco's <code>allowas-in</code> feature) to exchange routes between networks. </Aside>
+		</>
+		)
+	}
 
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations and is not a security mechanism.
 8. (Optional) In **Additional Advertised prefix list**, input any additional prefixes you want to advertise alongside your existing routes. Leave this blank if you do not want to advertise extra routes. Typical prefixes to configure here include:
-   - A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
-   - A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
-     { props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
+	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
+	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#return-traffic-routing).
+	{ props.magicWord !== "Magic Transit" && (<Markdown text={`- A route to \`100.64.0.0/12\`, the portion of CGNAT space [used by default for Cloudflare Source IPs](${props.magicWord === "CF1 Cloudflare WAN" ? "/cloudflare-one/networks/connectors/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/" : "/cloudflare-wan/configuration/how-to/configure-cloudflare-source-ips/"}).`} inline={false} />)}
 9. Select **Save**.
diff --git a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
index b45261be84bfb8e..2c65310f9047a4a 100644
--- a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
+++ b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
@@ -7,7 +7,6 @@ params:
 import { APIRequest, DashButton, Tabs, TabItem } from "~/components";
 
 You can configure the source IP address range used by Cloudflare whenever a Cloudflare service, such as Cloudflare Load Balancing, sends traffic to a Cloudflare One private network. This address range is referred to as the Cloudflare Source IP Prefix (or `cloudflare_source` subnet type in the API).
-
 - IPv4 traffic is sourced from `100.64.0.0/12`. This range is configurable.
 - IPv6 traffic is sourced from `2606:4700:cf1:5000::/64`. This range is not configurable.
 
@@ -26,7 +25,6 @@ You must configure routes in your network so that response traffic for these sou
 ## Prerequisites
 
 Before you begin, ensure that:
-
 - You have Cloudflare One <a href={props.unifiedRoutingLink}>Unified Routing (beta)</a>. If your account is not yet on Unified Routing, contact your account team to discuss migration and availability.
 - You have [Cloudflare One Networks Write](/fundamentals/api/reference/permissions/) permission.
 - Your desired new network range meets the following requirements:
diff --git a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
index d22d6e489c92663..17e4497d25e28e8 100644
--- a/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
+++ b/src/content/partials/networking-services/routing/mcn-cloudflare-wan-on-ramps.mdx
@@ -37,7 +37,7 @@ Choose this option if you have a single VPC in your cloud to connect to Cloudfla
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -74,7 +74,7 @@ When you configure a hub on-ramp, Cloudflare always manages the VPN tunnel betwe
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -105,7 +105,7 @@ You have successfully created your Cloudflare WAN on-ramp. However, on-ramp crea
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select **Add new on-ramp**.
@@ -156,7 +156,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, select **Add new on-ramp** and begin the **Create a Cloudflare WAN cloud on-ramp** workflow following the standard steps.
@@ -169,7 +169,7 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the on-ramp you want to download > select the three dots > **Download as Terraform**.
@@ -186,7 +186,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to edit.
@@ -203,7 +203,7 @@ After setting up your on-ramps, you need to update your network security groups
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. Select the on-ramp you want to delete.
@@ -227,7 +227,7 @@ To override the defaults with custom prefixes:
 
 1. Go to the **Routes** page.
 
-   <DashButton url="/?to=/:account/magic-networks/routes" />
+	<DashButton url="/?to=/:account/magic-networks/routes" />
 
 2. Select **WAN configuration**.
 3. Scroll to **Propagated routes to cloud networks**.
@@ -244,7 +244,7 @@ You can view estimated costs associated with your cloud resources in the Cloudfl
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. Select the **Cloud (beta)** tab.
 3. In **Cloud on-ramps**, find the cloud on-ramp for which you want to check the estimated costs > select the three dots > **Associated Resources**.
diff --git a/src/content/partials/networking-services/sites/sites-brief.mdx b/src/content/partials/networking-services/sites/sites-brief.mdx
index cea114893c8546c..b562aa89e9a4045 100644
--- a/src/content/partials/networking-services/sites/sites-brief.mdx
+++ b/src/content/partials/networking-services/sites/sites-brief.mdx
@@ -5,4 +5,4 @@ params:
 
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that Cloudflare notifies you when there are issues with the site's on-ramps.
 
-Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
+Refer to <a href={props.sitesURL}>Set up a site</a> for more information.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx
index ab902ad3cbb22b4..e49acf781ff2f8d 100644
--- a/src/content/partials/networking-services/sites/sites.mdx
+++ b/src/content/partials/networking-services/sites/sites.mdx
@@ -13,7 +13,6 @@ import { Markdown, Render, DashButton } from "~/components";
 Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to quickly check the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
 
 To use a site, start by setting up your on-ramps. On-ramps can be:
-
 - <a href={props.greIpsecTunnelsURL}>GRE or IPsec tunnels</a>
 - <a href={props.connectorURL}>{props.connectorName}</a>
 - Direct <a href={props.cniURL}>CNI link</a>
@@ -23,9 +22,9 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo
 ## Add a site
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview**, select **Add site**.
@@ -39,36 +38,35 @@ text={`
 		11. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
 		12. Select **Complete setup** to finish setting up your site.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-
-    	<Markdown
-    	text={`
-    	2. In **Network overview**, select **Add a site**.
-    	3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
-    	4. Select **Create and continue**.
-    	5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
-    	6. Select **Continue**.
-    	7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
-    	8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
-    	9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-    	10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
-    	11. Select **Complete setup** to finish setting up your site.
-    	`}
-    	inline={false}
-    />
-    </>
-
+		inline={false}
+	/>
+	<DashButton url="/?to=/:account/networking-insights/health" />
+
+		<Markdown
+		text={`
+		2. In **Network overview**, select **Add a site**.
+		3. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created.
+		4. Select **Create and continue**.
+		5. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might include on-ramps available on other locations.
+		6. Select **Continue**.
+		7. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
+		8. In **Tunnel Health Check Alert** > **Notification name**, enter a name for the site's alert.
+		9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
+		10. In **Alert sensitivity level** define the threshold for Tunnel health alerts to be fired. For details, refer to [How Cloudflare calculates Tunnel health alerts](/cloudflare-wan/reference/how-cloudflare-calculates-tunnel-health-alerts/).
+		11. Select **Complete setup** to finish setting up your site.
+		`}
+		inline={false}
+	/>
+	</>
 )
 }
 
@@ -84,13 +82,10 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 	params={{
 		instructions: "",
 		magicWord: props.magicWord,
-		networkOverviewPageName:
-			props.magicWord === "CF1 Cloudflare WAN"
-				? "Network visibility"
-				: "Network overview",
+		networkOverviewPageName: props.magicWord === "CF1 Cloudflare WAN" ? "Network visibility" : "Network overview",
 		magicTunnelHcsURL: props.magicTunnelHcsURL,
-		setGeoCoordinatesURL: "#set-geographic-coordinates",
-	}}
+		setGeoCoordinatesURL: "#set-geographic-coordinates"
+		}}
 />
 
 ---
@@ -100,9 +95,9 @@ Your site is now set up. If you have other sites you need to set up, repeat the
 ### Add or remove on-ramps
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/).
 		2. Go to **Insights** > **Network visibility**.
 		3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
@@ -110,32 +105,31 @@ text={`
 		5. Select **Add** to add a new on-ramp.
 		6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-
-    <DashButton url="/?to=/:account/networking-insights/health" />
+		inline={false}
+	/>
 
-    <Markdown
-    	text={`
-    	2. Go to **Network overview** > **Traffic overview**.
-    	3. Find your site > select the three dots in front of it > **Edit**.
-    	3. Select **On-ramps**.
-    	4. Select **Add** to add a new on-ramp.
-    	5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
-    	`}
-    	inline={false}
-    />
-    </>
+	<DashButton url="/?to=/:account/networking-insights/health" />
 
+	<Markdown
+		text={`
+		2. Go to **Network overview** > **Traffic overview**.
+		3. Find your site > select the three dots in front of it > **Edit**.
+		3. Select **On-ramps**.
+		4. Select **Add** to add a new on-ramp.
+		5. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
+		`}
+		inline={false}
+	/>
+	</>
 )
 }
 
@@ -144,34 +138,36 @@ inline={false}
 If you add geographic coordinates to your site, it will appear in the Network map. To set up or edit geographic coordinates to an existing site:
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to **Insights** > **Network visibility**.
 		2. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Go to the **Network health** page.
 		`}
-inline={false}
-/>
-<DashButton url="/?to=/:account/networking-insights/health" />
-<Markdown
-text={`
+		inline={false}
+	/>
+	<DashButton url="/?to=/:account/networking-insights/health" />
+		<Markdown
+		text={`
 		2. Go to **Network overview** > **Traffic overview**.
 		3. Find your site > select the three dots in front of it > **Edit**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 )
-} 3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates. 4. Select **Save**.
+}
+3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
+4. Select **Save**.
 
 ### Set thresholds for site health
 
@@ -180,6 +176,6 @@ inline={false}
 	product="networking-services"
 	params={{
 		productName: "Cloudflare WAN",
-		magicTunnelHcsURL: props.magicTunnelHcsURL,
+		magicTunnelHcsURL: props.magicTunnelHcsURL
 	}}
 />
diff --git a/src/content/partials/networking-services/troubleshoot-connectivity.mdx b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
index 3c84b2a29e2bedd..9a288f95f8861fd 100644
--- a/src/content/partials/networking-services/troubleshoot-connectivity.mdx
+++ b/src/content/partials/networking-services/troubleshoot-connectivity.mdx
@@ -74,7 +74,7 @@ You can identify which data centers handle your traffic by using **Network Analy
 
 1. Go to the **Network Analytics** page.
 
-   <DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
+	<DashButton url="/?to=/:account/networking-insights/analytics/network-analytics/transport-analytics" />
 
 2. Select **Add filter** and filter traffic by your source IP addresses to isolate your traffic.
 3. Under **Packets summary**, select the **Source data center** tab. If the tab is not visible, select the three-dot menu (`...`) to reveal additional view options and select **Source data center**.
@@ -112,13 +112,8 @@ If you have worked through this guide and cannot resolve the issue, gather the f
 
 ## Related resources
 
-- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve
-  common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
-- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose
-  routing and BGP issues that affect traffic delivery.
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
-  Monitor tunnel status per data center.
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
-  details on how health checks work.
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic
-  patterns over time.
+- <a href={props.tunnelHealthLink}>Troubleshoot tunnel health</a>: Resolve common tunnel health issues (flapping, IPsec errors, stateful firewall drops).
+- <a href={props.routingBgpLink}>Troubleshoot routing and BGP</a>: Diagnose routing and BGP issues that affect traffic delivery.
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Monitor tunnel status per data center.
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on how health checks work.
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Analyze traffic patterns over time.
diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
index f91d7cf6d89d54e..33f16ff7be38ee7 100644
--- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
+++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
@@ -8,13 +8,7 @@ params:
   - magicWord?
 ---
 
-import {
-	Aside,
-	AnchorHeading,
-	DashButton,
-	GlossaryTooltip,
-	Markdown,
-} from "~/components";
+import { Aside, AnchorHeading, DashButton, GlossaryTooltip, Markdown } from "~/components";
 
 The Cloudflare dashboard monitors the health of all <GlossaryTooltip term="anycast">anycast</GlossaryTooltip> tunnels on your account that route traffic from Cloudflare to your origin network.
 
@@ -29,9 +23,9 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr
 ## Check tunnel health
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
@@ -40,34 +34,33 @@ text={`
 			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
 		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    	<Markdown
-    		text={`
-    		1. Go to the **Network health** page.
-    			`}
-    		inline={false}
-    	/>
-
-    	<DashButton url="/?to=/:account/networking-insights/health" />
-
-    	<Markdown
-    		text={`
-    		2. Select the **Connector health** tab.
-    		3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
-    		4. Find the tunnel you want to inspect, select the three dots next to it, and select:
-    			- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
-    			- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
-    		5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
-    		`}
-    		inline={false}
-    	/>
-    </>
-
+	<>
+
+		<Markdown
+			text={`
+			1. Go to the **Network health** page.
+				`}
+			inline={false}
+		/>
+
+		<DashButton url="/?to=/:account/networking-insights/health" />
+
+		<Markdown
+			text={`
+			2. Select the **Connector health** tab.
+			3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+			4. Find the tunnel you want to inspect, select the three dots next to it, and select:
+				- **Create alert**: Opens the ${props.notificationsPath} so you can create specific alerts for that tunnel when specific conditions are met.
+				- **Network Analytics**: Opens the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
+			5. Alternatively, from the list of tunnels, select the tunnel you want to inspect to access details about it.
+			`}
+			inline={false}
+		/>
+	</>
 )
 }
 
@@ -76,50 +69,48 @@ inline={false}
 You can drill down into a specific tunnel to check its health status and other information.
 
 { props.magicWord === "CF1 Cloudflare WAN" ? (
-<>
-<Markdown
-text={`
+	<>
+	<Markdown
+		text={`
 		1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
 		2. Go to **Network health** > **WAN connector health**.
 		`}
-inline={false}
-/>
-</>
+		inline={false}
+	/>
+	</>
 ) : (
-<>
-
-    <Markdown
-    		text={`
-    		1. Go to the **Network health** page.
-    			`}
-    		inline={false}
-    	/>
+	<>
 
-    <DashButton url="/?to=/:account/networking-insights/health" />
+	<Markdown
+			text={`
+			1. Go to the **Network health** page.
+				`}
+			inline={false}
+		/>
 
-    <Markdown
-    		text={`
+	<DashButton url="/?to=/:account/networking-insights/health" />
 
+	<Markdown
+			text={`
 2. Select the **Connector health** tab.
-   `}
-   inline={false}
-   />
-   </>
-   )
-   }
+			`}
+			inline={false}
+		/>
+	</>
+)
+}
+
 
 3. Find and select the tunnel you want to inspect.
 
 The next view displays detailed information about the tunnel, including:
-
 - Status information
-  - Up: More than 80% of health checks pass.
-  - Degraded: More than 40% of health checks pass.
-  - Down: Less than 40% of health checks pass.
+	- Up: More than 80% of health checks pass.
+	- Degraded: More than 40% of health checks pass.
+	- Down: Less than 40% of health checks pass.
 - Health checks passed in the last hour
 - Traffic volume in the last hour
 
 If you select the three dots in front of the tunnel you want to inspect, you have access to the following tools:
-
 - Packet captures: Collect <a href={props.packetCaptures}>packet level data for your traffic</a>
 - Network Analytics: Leverage real-time insights into <a href={props.networkAnalytics}>network analytics</a>.
diff --git a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
index 40f78d258f68ce4..7b2222fb7119eaf 100644
--- a/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
+++ b/src/content/partials/networking-services/tunnel-health/health-checks-compatible-cmb-eu.mdx
@@ -5,4 +5,4 @@ params:
 
 :::note
 {props.productName} customers with [Customer Metadata Boundary](/data-localization/metadata-boundary/) enabled for the European Union can access GRE, IPsec, and CNI (Cloudflare Network Interconnect) health check and traffic volume data in the Cloudflare dashboard and through the API. This ensures that customers who need to be General Data Protection Regulation (GDPR) compliant can access all {props.productName} features.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
index a4314a796e274e0..d9eecdf681026ce 100644
--- a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
+++ b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
@@ -8,14 +8,14 @@ params:
 ---
 
 import {
-	APIRequest,
-	Code,
-	Details,
-	GlossaryTooltip,
-	Render,
-	Tabs,
-	TabItem,
-	DashButton,
+  APIRequest,
+  Code,
+  Details,
+  GlossaryTooltip,
+  Render,
+  Tabs,
+  TabItem,
+  DashButton,
 } from "~/components";
 
 You can configure Tunnel Health Alerts (formerly Magic Tunnel health alerts) to receive email, webhook, and PagerDuty notifications when the percentage of successful <GlossaryTooltip term="tunnel health-check">health checks</GlossaryTooltip> for an IPsec/GRE tunnel drops below the selected <a href={props.magicTunnelHealthCheckCalculation}>service-level objective (SLO)</a>.
@@ -42,14 +42,14 @@ Currently, there are seven SLO threshold values that you can configure through t
 The SLO threshold for Tunnel health alerts is the percentage of successful health checks for each IPsec/GRE tunnel in the alert:
 
 | Alert Sensitivity Level | SLO threshold |
-| ----------------------- | ------------- |
-| Minimum                 | 95.0          |
-| Very low                | 96.0          |
-| Low                     | 97.0          |
-| Medium                  | 98.0          |
-| High                    | 99.0          |
-| Very high               | 99.5          |
-| Maximum                 | 99.9          |
+| --- 										| --- 					|
+| Minimum 								| 95.0 					|
+| Very low 								| 96.0					|
+| Low 										| 97.0 					|
+| Medium 									| 98.0 					|
+| High 										| 99.0 					|
+| Very high 							| 99.5					|
+| Maximum 								| 99.9					|
 
 The time it takes to receive alerts depends on the sensitivity level you configure for your SLO thresholds. Higher sensitivity levels notify you faster when a tunnel's health degrades, but they may also trigger alerts for brief or minor disruptions. Lower sensitivity levels reduce the chance of false alarms but may delay notifications for less severe issues.
 
@@ -57,6 +57,7 @@ While the underlying detection timing remains consistent across sensitivity leve
 
 For details, refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Tunnel health alerts</a>.
 
+
 ## Set up Tunnel Health Alerts
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
index be3e95d154d505a..87ae557ab8ac1a5 100644
--- a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
@@ -5,4 +5,4 @@ params:
 
 Cloudflare One Appliance (formerly Magic WAN Connector) also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare through HTTPS and lets Cloudflare know that the Cloudflare One Appliance in question is connected to the Internet and reachable.
 
-Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
+Refer to <a href={props.heartbeatURL}>Heartbeat</a> to learn more.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
index a3df68499495d50..83373e4b20668f6 100644
--- a/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/troubleshoot-tunnel-health.mdx
@@ -19,15 +19,15 @@ This guide helps you diagnose and resolve common tunnel health issues with {prop
 
 Use the following table to match your symptom to the most likely cause and first action:
 
-| Symptom                                           | Most likely cause                                         | First action                                                                                                                                        |
-| :------------------------------------------------ | :-------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Tunnel shows Down, never becomes healthy          | Configuration mismatch or firewall blocking IKE           | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures).                    |
-| Dashboard shows "100% degraded" for some colos    | Normal — this is a state indicator, not packet loss       | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard).              |
-| Tunnel flaps between healthy and unhealthy        | Anti-replay protection or rekey disruption                | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops).                      |
-| Health checks fail but traffic flows normally     | Stateful firewall dropping health check probes            | Change health check type from _Reply_ to _Request_. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
-| Health checks fail on policy-based VPN tunnels    | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
-| All tunnels degraded or down in a specific region | Network path issue between that region and your network   | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare.                                                          |
-| All tunnels degraded or down globally             | Issue at your network edge                                | Check your tunnel endpoint router and upstream connectivity.                                                                                        |
+| Symptom | Most likely cause | First action |
+| :------ | :---------------- | :----------- |
+| Tunnel shows Down, never becomes healthy | Configuration mismatch or firewall blocking IKE | Check IPsec parameters and firewall rules. Refer to [IPsec tunnel establishment failures](#ipsec-tunnel-establishment-failures). |
+| Dashboard shows "100% degraded" for some colos | Normal — this is a state indicator, not packet loss | Check if affected colos carry your traffic. Refer to [Understanding degraded status](#understanding-degraded-status-in-the-dashboard). |
+| Tunnel flaps between healthy and unhealthy | Anti-replay protection or rekey disruption | Disable anti-replay protection on your router. Refer to [IPsec tunnel instability](#ipsec-tunnel-instability-or-packet-drops). |
+| Health checks fail but traffic flows normally | Stateful firewall dropping health check probes | Change health check type from *Reply* to *Request*. Refer to [Tunnel shows Down but traffic is flowing](#tunnel-shows-down-but-traffic-is-flowing). |
+| Health checks fail on policy-based VPN tunnels | Reply health checks fall outside tunnel traffic selectors | Use Request-style health checks with a loopback target. Refer to [Policy-based VPN health check failures](#policy-based-vpn-health-check-failures). |
+| All tunnels degraded or down in a specific region | Network path issue between that region and your network | Check ISP connectivity. Use traceroute or MTR from your tunnel endpoint toward Cloudflare. |
+| All tunnels degraded or down globally | Issue at your network edge | Check your tunnel endpoint router and upstream connectivity. |
 
 ### What you can check
 
@@ -46,7 +46,7 @@ Use the following table to match your symptom to the most likely cause and first
 
 If you are experiencing tunnel health issues, check these items first:
 
-1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from _Reply_ to _Request_.
+1. **Health check type**: If using a stateful firewall (such as Palo Alto Networks, Check Point, Cisco, or Fortinet), change health check type from *Reply* to *Request*.
 2. **Anti-replay protection**: Disable anti-replay protection on your router, or set the replay window to `0`.
 3. **MTU settings**: Verify MTU is set correctly (typically `1476` for GRE, `1400`-`1450` for IPsec).
 4. **IPsec parameters**: Confirm your cryptographic parameters match <a href={props.tunnelsConfigLink}>Cloudflare's supported configuration</a>.
@@ -59,11 +59,11 @@ If you are experiencing tunnel health issues, check these items first:
 
 The [Network health](https://dash.cloudflare.com/?to=/:account/networking-insights/health) page in the Cloudflare dashboard displays three tunnel health states:
 
-| State        | Dashboard display                         | Technical threshold                                                |
-| :----------- | :---------------------------------------- | :----------------------------------------------------------------- |
-| **Healthy**  | More than 80% of health checks pass       | Less than 0.1% failure rate                                        |
+| State | Dashboard display | Technical threshold |
+| :---- | :---- | :---- |
+| **Healthy** | More than 80% of health checks pass | Less than 0.1% failure rate |
 | **Degraded** | Between 40% and 80% of health checks pass | At least 0.1% failures in last five minutes (minimum two failures) |
-| **Down**     | Less than 40% of health checks pass       | All health checks failed (at least three samples in last second)   |
+| **Down** | Less than 40% of health checks pass | All health checks failed (at least three samples in last second) |
 
 The dashboard shows tunnel health as measured from each Cloudflare data center where your traffic lands. It is normal to see some locations reporting degraded status due to Internet path issues. Focus on locations that show traffic in the **Traffic volume (1h)** column.
 
@@ -122,16 +122,16 @@ For instructions on monitoring tunnel status, refer to <a href={props.checkHealt
 
 **Health check type:**
 
-| Type                | Behavior                              | When to use                                                         |
-| :------------------ | :------------------------------------ | :------------------------------------------------------------------ |
-| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls                          |
-| **Request**         | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
+| Type | Behavior | When to use |
+| :---- | :---- | :---- |
+| **Reply** (default) | Cloudflare sends an ICMP reply packet | Simple networks without stateful firewalls |
+| **Request** | Cloudflare sends an ICMP echo request | Networks with stateful firewalls (recommended for most deployments) |
 
 **Health check direction:**
 
-| Direction          | Behavior                                              | Default for                          |
-| :----------------- | :---------------------------------------------------- | :----------------------------------- |
-| **Bidirectional**  | Probe and response both traverse the tunnel           | Cloudflare WAN (formerly Magic WAN)  |
+| Direction | Behavior | Default for |
+| :---- | :---- | :--- |
+| **Bidirectional** | Probe and response both traverse the tunnel | Cloudflare WAN (formerly Magic WAN) |
 | **Unidirectional** | Probe traverses tunnel; response returns via Internet | Magic Transit (direct server return) |
 
 :::note
@@ -152,23 +152,23 @@ Unidirectional health checks can be unreliable because intermediate network devi
 
 #### Cause
 
-Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP _Reply_ packets as health check probes.
+Stateful firewalls (such as Palo Alto Networks, Check Point, Cisco, and Fortinet) drop the health check packets. By default, Cloudflare sends ICMP *Reply* packets as health check probes.
 
-Stateful firewalls inspect these packets and look for a matching ICMP _Request_ in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
+Stateful firewalls inspect these packets and look for a matching ICMP *Request* in their session table. When no matching request exists, firewalls drop the reply as "out-of-state".
 
 #### Solution
 
-Change the health check type from _Reply_ to _Request_:
+Change the health check type from *Reply* to *Request*:
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on the affected tunnel.
-3. Under **Health check type**, change from _Reply_ to _Request_.
+3. Under **Health check type**, change from *Reply* to *Request*.
 4. Select **Update tunnel**.
 
-When you use _Request_ style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
+When you use *Request* style health checks, Cloudflare sends an ICMP echo request. Your firewall's stateful inspection engine recognizes this as a legitimate request and automatically permits the ICMP reply response.
 
 :::note
 If your firewall drops ICMP request packets as well, verify that your firewall policy permits ICMP traffic on the tunnel interface.
@@ -190,21 +190,21 @@ Cloudflare Network Firewall processes all traffic, including Cloudflare's health
 
 #### Solution
 
-Add an allow rule for ICMP traffic from Cloudflare IP addresses _before_ any block rules:
+Add an allow rule for ICMP traffic from Cloudflare IP addresses *before* any block rules:
 
 1. Go to the **Firewall policies** page.
 
-   <DashButton url="/?to=/:account/network-security/magic_firewall" />
+	<DashButton url="/?to=/:account/network-security/magic_firewall" />
 
 2. Create a new policy with the following parameters:
 
-| Field        | Value                                               |
-| :----------- | :-------------------------------------------------- |
-| **Action**   | Allow                                               |
-| **Protocol** | ICMP                                                |
-| **Source**   | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
+| Field | Value |
+| :---- | :---- |
+| **Action** | Allow |
+| **Protocol** | ICMP |
+| **Source** | [Cloudflare IP ranges](https://cloudflare.com/ips/) |
 
-3. Position this rule _before_ any rules that block ICMP traffic.
+3. Position this rule *before* any rules that block ICMP traffic.
 
 For more information, refer to [Cloudflare Network Firewall rules and endpoint health checks](/cloudflare-network-firewall/about/ruleset-logic/#cloudflare-network-firewall-rules-and-magic-transit-endpoint-health-checks).
 
@@ -246,7 +246,7 @@ Enable replay protection in the Cloudflare dashboard. This routes all tunnel tra
 
 1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
 
 2. In **IPsec/GRE tunnels**, select **Edit** on your IPsec tunnel.
 3. Enable **Replay protection**.
@@ -294,11 +294,13 @@ This behavior is expected and the tunnel will automatically recover. To minimize
 2. **Increase rekey intervals**: Configure longer SA lifetimes on your tunnel endpoint to reduce rekey frequency. Common values are 8-24 hours for IKE SA and 1-8 hours for IPsec SA.
 
 3. **Adjust health check sensitivity**: If brief degradation during rekeys triggers alerts, consider lowering the health check rate:
+
    1. Go to the **Connectors** page.
 
-   <DashButton url="/?to=/:account/magic-networks/connections" />
+	<DashButton url="/?to=/:account/magic-networks/connections" />
+
    2. In **IPsec/GRE tunnels**, select **Edit** on the tunnel.
-   3. Change **Health check rate** to _Low_.
+   3. Change **Health check rate** to *Low*.
 
 4. **Stagger rekey times**: If you have multiple tunnels, configure different SA lifetimes so they do not rekey simultaneously.
 
@@ -350,12 +352,12 @@ For detailed information on how bidirectional health checks work, refer to <a hr
 
 IPsec tunnel establishment can fail due to several configuration mismatches:
 
-| Issue                         | Symptom                                         |
-| :---------------------------- | :---------------------------------------------- |
+| Issue | Symptom |
+| :---- | :---- |
 | **Crypto parameter mismatch** | IKE negotiation fails with "no proposal chosen" |
-| **Incorrect PSK**             | Authentication failures in Phase 1              |
-| **Wrong IKE ID format**       | Authentication failures despite correct PSK     |
-| **Firewall blocking IKE**     | No IKE traffic reaches Cloudflare               |
+| **Incorrect PSK** | Authentication failures in Phase 1 |
+| **Wrong IKE ID format** | Authentication failures despite correct PSK |
+| **Firewall blocking IKE** | No IKE traffic reaches Cloudflare |
 
 #### Solution
 
@@ -363,22 +365,24 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 
    **Phase 1 (IKE)**
 
-| Parameter      | Supported values            |
-| :------------- | :-------------------------- |
-| IKE version    | IKEv2 only                  |
-| Encryption     | AES-GCM-16, AES-CBC-256     |
-| Authentication | SHA-256, SHA-384, SHA-512   |
-| DH Group       | DH group 14, 15, 16, 19, 20 |
 
-**Phase 2 (IPsec)**
+| Parameter | Supported values |
+| :---- | :---- |
+| IKE version | IKEv2 only |
+| Encryption | AES-GCM-16, AES-CBC-256 |
+| Authentication | SHA-256, SHA-384, SHA-512 |
+| DH Group | DH group 14, 15, 16, 19, 20 |
+
+   **Phase 2 (IPsec)**
 
-| Parameter      | Supported values            |
-| :------------- | :-------------------------- |
-| Encryption     | AES-GCM-16, AES-CBC-256     |
-| Authentication | SHA-256, SHA-512            |
-| PFS Group      | DH group 14, 15, 16, 19, 20 |
+| Parameter | Supported values |
+| :---- | :---- |
+| Encryption | AES-GCM-16, AES-CBC-256 |
+| Authentication | SHA-256, SHA-512 |
+| PFS Group | DH group 14, 15, 16, 19, 20 |
 
 2. **Verify the Pre-Shared Key (PSK):**
+
    - Regenerate the PSK in the Cloudflare dashboard
    - Copy the new PSK exactly (no extra spaces or characters)
    - Update your router with the new PSK
@@ -386,6 +390,7 @@ IPsec tunnel establishment can fail due to several configuration mismatches:
 3. **Check the IKE ID format:** Cloudflare uses FQDN format for the IKE ID. Ensure your router is configured to accept an FQDN peer identity. The FQDN is displayed in the tunnel details in the Cloudflare dashboard.
 
 4. **Verify firewall rules:** Ensure your edge firewall permits:
+
    - UDP port `500` (IKE)
    - UDP port `4500` (IKE NAT-T)
    - IP protocol `50` (ESP)
@@ -410,7 +415,7 @@ Additionally, some firewalls (such as Check Point) may flag Reply-style health c
 
 #### Solution
 
-1. Change the health check type from _Reply_ to _Request_.
+1. Change the health check type from *Reply* to *Request*.
 2. Configure a loopback address on your tunnel endpoint as the health check target. The target must be:
    - Routable from the tunnel endpoint
    - Covered by the tunnel's traffic selectors (encryption domain)
@@ -426,13 +431,13 @@ Policy-based tunnels use a separate Child SA for each set of traffic selectors.
 
 ### Common vendor-specific issues
 
-| Vendor                 | Common issue                             | Solution                                                   |
-| :--------------------- | :--------------------------------------- | :--------------------------------------------------------- |
-| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to _Request_; disable anti-replay |
-| **Cisco Meraki**       | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **AWS VPN Gateway**    | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **VeloCloud**          | Cannot disable anti-replay               | Enable replay protection in Cloudflare dashboard           |
-| **Check Point**        | Out-of-state packet drops                | Change health check type to _Request_                      |
+| Vendor | Common issue | Solution |
+| :---- | :---- | :---- |
+| **Palo Alto Networks** | Health checks fail with default settings | Change health check type to *Request*; disable anti-replay |
+| **Cisco Meraki** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **AWS VPN Gateway** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **VeloCloud** | Cannot disable anti-replay | Enable replay protection in Cloudflare dashboard |
+| **Check Point** | Out-of-state packet drops | Change health check type to *Request* |
 
 ---
 
@@ -479,13 +484,8 @@ Collect output from these commands (syntax varies by vendor):
 
 ## Resources
 
-- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical
-  details on health check behavior
-- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay
-  must be disabled
-- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel
-  setup instructions
-- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>:
-  Dashboard navigation guide
-- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis
-  tools
+- <a href={props.tunnelHealthChecksLink}>Tunnel health checks</a>: Technical details on health check behavior
+- <a href={props.antiReplayLink}>Anti-replay protection</a>: Why anti-replay must be disabled
+- <a href={props.configureTunnelsLink}>Configure tunnel endpoints</a>: Tunnel setup instructions
+- <a href={props.checkHealthDashLink}>Check tunnel health in the dashboard</a>: Dashboard navigation guide
+- <a href={props.networkAnalyticsLink}>Network Analytics</a>: Traffic analysis tools
\ No newline at end of file
diff --git a/src/content/partials/networking-services/virtual-networks-concept.mdx b/src/content/partials/networking-services/virtual-networks-concept.mdx
index 5f791ebd1962872..bec7de23f758195 100644
--- a/src/content/partials/networking-services/virtual-networks-concept.mdx
+++ b/src/content/partials/networking-services/virtual-networks-concept.mdx
@@ -84,21 +84,18 @@ The same CIDR (`10.0.0.0/8`) can exist in each virtual network because they are
 
 Each virtual network maintains its own routing table. Routes added to one virtual network do not appear in another virtual network routing table. However, if traffic does not match a route in the selected virtual network, Cloudflare may fall back to the default virtual network routing table for WAN routes.
 
-<Markdown
-	text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`}
-	inline={false}
-/>
+<Markdown text={`You can add entries to a virtual network routing table through static route configuration or routes learned from BGP peering (beta). Static routes are available for all connection types. BGP peering is currently available over CNI and IPsec/GRE tunnels (beta). For more information on how routes are prioritized within a virtual network, refer to [Traffic steering](${props.trafficSteeringURL}).`} inline={false} />
 
 ## Virtual networks across Cloudflare
 
 Virtual network support varies by product:
 
-| Product               | Virtual network support   | Details                                                              |
-| --------------------- | ------------------------- | -------------------------------------------------------------------- |
-| Cloudflare Tunnel     | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
-| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection  |
-| Cloudflare Mesh       | Not currently supported   | —                                                                    |
-| Cloudflare WAN        | Default only              | All IPsec, GRE, and CNI connections use the default virtual network  |
+| Product | Virtual network support | Details |
+| --- | --- | --- |
+| Cloudflare Tunnel | Multiple virtual networks | Assign CIDR routes to a virtual network when configuring your tunnel |
+| Cloudflare One Client | Multiple virtual networks | Users land in a virtual network based on policy or client selection |
+| Cloudflare Mesh | Not currently supported | — |
+| Cloudflare WAN | Default only | All IPsec, GRE, and CNI connections use the default virtual network |
 
 ## The default virtual network
 
@@ -123,26 +120,14 @@ If you are familiar with cloud networking concepts, a virtual network is analogo
 
 ## Create and manage virtual networks
 
-<Markdown
-	text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`}
-	inline={false}
-/>
+<Markdown text={`To create and configure virtual networks, refer to [Virtual networks (Tunnel configuration)](${props.tunnelConfigURL}).`} inline={false} />
 
-<Markdown
-	text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`}
-	inline={false}
-/>
+<Markdown text={`To configure which routes belong to which virtual network, refer to [Add routes](${props.addRoutesURL}).`} inline={false} />
 
-<Markdown
-	text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`}
-	inline={false}
-/>
+<Markdown text={`To add static routes or configure BGP peering within the Cloudflare Virtual Network routing table, refer to [Configure routes](${props.configureRoutesURL}).`} inline={false} />
 
 ## Related resources
 
-<Markdown
-	text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
+<Markdown text={`- [Private networks](${props.privateNetworksURL}) — Connect your infrastructure to Cloudflare
 - [Routes](${props.routesURL}) — Define IP and hostname routes through your connectors
-- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`}
-	inline={false}
-/>
+- [Traffic steering](${props.trafficSteeringURL}) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network`} inline={false} />
diff --git a/src/content/partials/notifications/get-started.mdx b/src/content/partials/notifications/get-started.mdx
index 829b54d50c6d7ad..00b7b4ec3a8f058 100644
--- a/src/content/partials/notifications/get-started.mdx
+++ b/src/content/partials/notifications/get-started.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Refer to [Cloudflare Notifications](/notifications/get-started/) for more information on how to set up an alert.
diff --git a/src/content/partials/pages/c3-adapter.mdx b/src/content/partials/pages/c3-adapter.mdx
index 32d2a3499fce337..a38fe66ad454db8 100644
--- a/src/content/partials/pages/c3-adapter.mdx
+++ b/src/content/partials/pages/c3-adapter.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If using [`create-cloudflare` (C3)](https://www.npmjs.com/package/create-cloudflare), you can bypass adding an adapter as C3 automatically installs any necessary adapters and configures them when creating your project.
 
+
 :::
diff --git a/src/content/partials/pages/c3-run-command-no-directory.mdx b/src/content/partials/pages/c3-run-command-no-directory.mdx
index 193d0bcd558150b..a64961aff54a926 100644
--- a/src/content/partials/pages/c3-run-command-no-directory.mdx
+++ b/src/content/partials/pages/c3-run-command-no-directory.mdx
@@ -4,8 +4,5 @@
 
 import { PackageManagers } from "~/components";
 
-<PackageManagers
-	type="create"
-	pkg="cloudflare@latest"
-	args="--platform=pages"
-/>
+<PackageManagers type="create" pkg="cloudflare@latest" args="--platform=pages"/>
+
diff --git a/src/content/partials/pages/cli-precedence-over-file.mdx b/src/content/partials/pages/cli-precedence-over-file.mdx
index b2bc3188eee261f..11a0cb2f0ebfdd4 100644
--- a/src/content/partials/pages/cli-precedence-over-file.mdx
+++ b/src/content/partials/pages/cli-precedence-over-file.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If a binding is specified in a [Wrangler configuration file](/workers/wrangler/configuration/) and via a command-line argument, the command-line argument takes precedence.
 
+
 :::
diff --git a/src/content/partials/pages/custom-domain-steps.mdx b/src/content/partials/pages/custom-domain-steps.mdx
index 20c18cb6fc838aa..fee5e4c0dbb152c 100644
--- a/src/content/partials/pages/custom-domain-steps.mdx
+++ b/src/content/partials/pages/custom-domain-steps.mdx
@@ -9,7 +9,6 @@ To add a custom domain:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Custom domains**.
 3. Select **Set up a domain**.
 4. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
index 953960ee01038c9..62859ea9b7e533e 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-no-preset.mdx
@@ -9,7 +9,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
index b8561649554de9d..f70be8044a5cf71 100644
--- a/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
+++ b/src/content/partials/pages/deploy-to-pages-steps-with-preset.mdx
@@ -10,7 +10,6 @@ To deploy your site to Pages:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application**.
 3. Select the **Pages** tab.
 4. Select **Import an existing Git repository**.
diff --git a/src/content/partials/pages/do-note.mdx b/src/content/partials/pages/do-note.mdx
index 6490baa6181c199..44f90d7ff7a4785 100644
--- a/src/content/partials/pages/do-note.mdx
+++ b/src/content/partials/pages/do-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You must create a Durable Object Worker and bind it to your Pages project using the Cloudflare dashboard or your Pages project's [Wrangler configuration file](/pages/functions/wrangler-configuration/). You cannot create and deploy a Durable Object within a Pages project.
diff --git a/src/content/partials/pages/framework-guides/create-gh-repo.mdx b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
index 8e6a0ec2e677e3a..7d4f7ac729dd198 100644
--- a/src/content/partials/pages/framework-guides/create-gh-repo.mdx
+++ b/src/content/partials/pages/framework-guides/create-gh-repo.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Create a new GitHub repository by visiting [repo.new](https://repo.new). After creating a new repository, go to your newly created project directory to prepare and push your local application to GitHub by running the following commands in your terminal:
diff --git a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
index 9f8e802cee2e978..46eb8a378cb57e1 100644
--- a/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
+++ b/src/content/partials/pages/framework-guides/create-github-repository-prefix.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Create a GitHub repository
diff --git a/src/content/partials/pages/framework-guides/git-integration.mdx b/src/content/partials/pages/framework-guides/git-integration.mdx
index ce38fa80e780d15..b904fe727721313 100644
--- a/src/content/partials/pages/framework-guides/git-integration.mdx
+++ b/src/content/partials/pages/framework-guides/git-integration.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Render } from "~/components";
+import { Render } from "~/components"
 
 ## Git integration
 
diff --git a/src/content/partials/pages/framework-guides/learn-more.mdx b/src/content/partials/pages/framework-guides/learn-more.mdx
index 875e06f11937b9d..412a7475b5f45d7 100644
--- a/src/content/partials/pages/framework-guides/learn-more.mdx
+++ b/src/content/partials/pages/framework-guides/learn-more.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: deployedTarget
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 ## Learn more
 
diff --git a/src/content/partials/pages/get-started-git-connect-pages.mdx b/src/content/partials/pages/get-started-git-connect-pages.mdx
index e2b68a6f9b7f3cc..9f0e08f89c4e2e7 100644
--- a/src/content/partials/pages/get-started-git-connect-pages.mdx
+++ b/src/content/partials/pages/get-started-git-connect-pages.mdx
@@ -9,17 +9,18 @@ Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitl
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select **Create application** > **Pages** > **Connect to Git**.
 
 You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/).
 
 :::note
 
+
 Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages.
 
 If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages.
 
+
 :::
 
 ### Select your GitHub repository
@@ -28,4 +29,4 @@ You can select a GitHub project from your personal account or an organization yo
 
 ### Select your GitLab repository
 
-If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
+If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported.
\ No newline at end of file
diff --git a/src/content/partials/pages/get-started-git-manage-site.mdx b/src/content/partials/pages/get-started-git-manage-site.mdx
index 6be5dbe386c0e10..0aa235c6ce61425 100644
--- a/src/content/partials/pages/get-started-git-manage-site.mdx
+++ b/src/content/partials/pages/get-started-git-manage-site.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import {DashButton} from "~/components";
 
 After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments.
 
@@ -15,15 +15,16 @@ To delete your Pages project:
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project > **Settings** > **Delete project**.
 
 :::caution
 
+
 For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions.
 
 For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings.
 
+
 :::
 
 ## Advanced project settings
@@ -32,6 +33,6 @@ In the **Settings** section, you can configure advanced settings, such as changi
 
 ## Related resources
 
-- Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
-- Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
-- Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
+* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
+* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
+* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).
\ No newline at end of file
diff --git a/src/content/partials/pages/git-integration-warning.mdx b/src/content/partials/pages/git-integration-warning.mdx
index 29972cbf983d1e4..fe22fd4c858b9dd 100644
--- a/src/content/partials/pages/git-integration-warning.mdx
+++ b/src/content/partials/pages/git-integration-warning.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Git integration]
 
+
 Currently, you cannot add Git integration to existing Pages applications. If you have already deployed your application, you need to create a new Pages application in order to add Git integration to it.
 
+
 :::
diff --git a/src/content/partials/pages/prod-branch-update.mdx b/src/content/partials/pages/prod-branch-update.mdx
index cc5195454fc9ea4..09fee36fe5dc103 100644
--- a/src/content/partials/pages/prod-branch-update.mdx
+++ b/src/content/partials/pages/prod-branch-update.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your project is a [Direct Upload](/pages/get-started/direct-upload/) project, you will not have the option to configure production branch controls. To update your production branch, you will need to manually call the [Update Project](/api/resources/pages/subresources/projects/methods/edit/) endpoint in the API.
diff --git a/src/content/partials/pages/tutorials-before-you-start.mdx b/src/content/partials/pages/tutorials-before-you-start.mdx
index 828e29a27d7e760..054f3014bbb4e20 100644
--- a/src/content/partials/pages/tutorials-before-you-start.mdx
+++ b/src/content/partials/pages/tutorials-before-you-start.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Before you continue
diff --git a/src/content/partials/pages/web-analytics-setup.mdx b/src/content/partials/pages/web-analytics-setup.mdx
index 5b7a79ede654b56..0c4d814773e0860 100644
--- a/src/content/partials/pages/web-analytics-setup.mdx
+++ b/src/content/partials/pages/web-analytics-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -7,7 +8,6 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your Pages project.
 3. Go to **Metrics** and select **Enable** under Web Analytics.
 
diff --git a/src/content/partials/queues/enable-queues.mdx b/src/content/partials/queues/enable-queues.mdx
index 2abc709865461de..5d055261c9dc78a 100644
--- a/src/content/partials/queues/enable-queues.mdx
+++ b/src/content/partials/queues/enable-queues.mdx
@@ -12,6 +12,6 @@ To enable Queues:
 
 1. In the Cloudflare dashboard, go to the **Queues** page.
 
-   <DashButton url="/?to=/:account/workers/queues" />
+	 <DashButton url="/?to=/:account/workers/queues" />
 
 2. Select **Enable Queues**.
diff --git a/src/content/partials/queues/event-subscriptions/access-events.mdx b/src/content/partials/queues/event-subscriptions/access-events.mdx
index 9f74f1279bcec9a..fc76184e339a0ed 100644
--- a/src/content/partials/queues/event-subscriptions/access-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/access-events.mdx
@@ -6,20 +6,20 @@ Triggered when an application is created.
 
 ```json
 {
-	"type": "cf.access.application.created",
-	"source": {
-		"type": "access"
-	},
-	"payload": {
-		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "My Application"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.access.application.created",
+  "source": {
+    "type": "access"
+  },
+  "payload": {
+    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "My Application"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when an application is deleted.
 
 ```json
 {
-	"type": "cf.access.application.deleted",
-	"source": {
-		"type": "access"
-	},
-	"payload": {
-		"id": "app-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "My Application"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.access.application.deleted",
+  "source": {
+    "type": "access"
+  },
+  "payload": {
+    "id": "app-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "My Application"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
index e25f2024c3d7d08..520d32a2d17b86f 100644
--- a/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/artifacts-events.mdx
@@ -8,27 +8,27 @@ Triggered when a repository is created.
 
 ```json
 {
-	"type": "cf.artifacts.repo.created",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "0tvugavnogssnwzk",
-		"defaultBranch": "main",
-		"description": "My Artifacts repository",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:46.833Z",
-		"updatedAt": "2026-05-18T15:53:46.833Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:48.187Z"
-	}
+  "type": "cf.artifacts.repo.created",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "0tvugavnogssnwzk",
+    "defaultBranch": "main",
+    "description": "My Artifacts repository",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:46.833Z",
+    "updatedAt": "2026-05-18T15:53:46.833Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:48.187Z"
+  }
 }
 ```
 
@@ -40,27 +40,27 @@ Triggered when a repository is deleted.
 
 ```json
 {
-	"type": "cf.artifacts.repo.deleted",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "0tvugavnogssnwzk",
-		"defaultBranch": "main",
-		"description": "My Artifacts repository",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:46.833Z",
-		"updatedAt": "2026-05-18T15:53:46.833Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:59.914Z"
-	}
+  "type": "cf.artifacts.repo.deleted",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "0tvugavnogssnwzk",
+    "defaultBranch": "main",
+    "description": "My Artifacts repository",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:46.833Z",
+    "updatedAt": "2026-05-18T15:53:46.833Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:59.914Z"
+  }
 }
 ```
 
@@ -72,29 +72,29 @@ Triggered when a repository is forked.
 
 ```json
 {
-	"type": "cf.artifacts.repo.forked",
-	"source": {
-		"type": "artifacts",
-		"namespace": "source-namespace",
-		"repoName": "source-repo"
-	},
-	"payload": {
-		"namespace": "target-namespace",
-		"repoName": "target-repo",
-		"repoId": "5ankv1vhl4xnw7wq",
-		"defaultBranch": "main",
-		"description": "Fork of source-repo",
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:52.384Z",
-		"updatedAt": "2026-05-18T15:53:54.579Z",
-		"lastPushAt": null
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:54.641Z"
-	}
+  "type": "cf.artifacts.repo.forked",
+  "source": {
+    "type": "artifacts",
+    "namespace": "source-namespace",
+    "repoName": "source-repo"
+  },
+  "payload": {
+    "namespace": "target-namespace",
+    "repoName": "target-repo",
+    "repoId": "5ankv1vhl4xnw7wq",
+    "defaultBranch": "main",
+    "description": "Fork of source-repo",
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:52.384Z",
+    "updatedAt": "2026-05-18T15:53:54.579Z",
+    "lastPushAt": null
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:54.641Z"
+  }
 }
 ```
 
@@ -106,29 +106,29 @@ Triggered when a repository is imported from an external Git remote.
 
 ```json
 {
-	"type": "cf.artifacts.repo.imported",
-	"source": {
-		"type": "artifacts",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"repoId": "d7nd72k964cv9kub",
-		"defaultBranch": "main",
-		"description": null,
-		"readOnly": false,
-		"createdAt": "2026-05-18T15:53:54.864Z",
-		"updatedAt": "2026-05-18T15:53:57.737Z",
-		"lastPushAt": null,
-		"sourceUrl": "https://github.com/example/repo.git",
-		"branch": "main"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:58.195Z"
-	}
+  "type": "cf.artifacts.repo.imported",
+  "source": {
+    "type": "artifacts",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "repoId": "d7nd72k964cv9kub",
+    "defaultBranch": "main",
+    "description": null,
+    "readOnly": false,
+    "createdAt": "2026-05-18T15:53:54.864Z",
+    "updatedAt": "2026-05-18T15:53:57.737Z",
+    "lastPushAt": null,
+    "sourceUrl": "https://github.com/example/repo.git",
+    "branch": "main"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:58.195Z"
+  }
 }
 ```
 
@@ -142,42 +142,44 @@ Triggered when commits are pushed to a repository.
 
 ```json
 {
-	"type": "cf.artifacts.repo.pushed",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {
-		"ref": "refs/heads/main",
-		"before": "abc123def456abc123def456abc123def456abc1",
-		"after": "def789ghi012def789ghi012def789ghi012def7",
-		"commits": [
-			{
-				"id": "def789ghi012def789ghi012def789ghi012def7",
-				"message": "Fix bug in authentication",
-				"messageTruncated": false,
-				"timestamp": "2025-05-01T02:48:57.000Z",
-				"author": {
-					"name": "Developer Name",
-					"email": "developer@example.com"
-				},
-				"committer": {
-					"name": "Developer Name",
-					"email": "developer@example.com"
-				},
-				"parents": ["abc123def456abc123def456abc123def456abc1"]
-			}
-		],
-		"totalCommitsCount": 1,
-		"commitsTruncated": false
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.artifacts.repo.pushed",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {
+    "ref": "refs/heads/main",
+    "before": "abc123def456abc123def456abc123def456abc1",
+    "after": "def789ghi012def789ghi012def789ghi012def7",
+    "commits": [
+      {
+        "id": "def789ghi012def789ghi012def789ghi012def7",
+        "message": "Fix bug in authentication",
+        "messageTruncated": false,
+        "timestamp": "2025-05-01T02:48:57.000Z",
+        "author": {
+          "name": "Developer Name",
+          "email": "developer@example.com"
+        },
+        "committer": {
+          "name": "Developer Name",
+          "email": "developer@example.com"
+        },
+        "parents": [
+          "abc123def456abc123def456abc123def456abc1"
+        ]
+      }
+    ],
+    "totalCommitsCount": 1,
+    "commitsTruncated": false
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -189,19 +191,19 @@ Triggered when a repository is cloned.
 
 ```json
 {
-	"type": "cf.artifacts.repo.cloned",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:51.358Z"
-	}
+  "type": "cf.artifacts.repo.cloned",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {},
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:51.358Z"
+  }
 }
 ```
 
@@ -213,19 +215,19 @@ Triggered when updates are fetched from a repository.
 
 ```json
 {
-	"type": "cf.artifacts.repo.fetched",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "my-namespace",
-		"repoName": "my-repo"
-	},
-	"payload": {},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-18T15:53:51.358Z"
-	}
+  "type": "cf.artifacts.repo.fetched",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "my-namespace",
+    "repoName": "my-repo"
+  },
+  "payload": {},
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-18T15:53:51.358Z"
+  }
 }
 ```
 
@@ -237,23 +239,23 @@ Triggered when a repo-scoped token is created. Includes the token ID, scope, and
 
 ```json
 {
-	"type": "cf.artifacts.repo.token.created",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "default",
-		"repoName": "token-evt-repo"
-	},
-	"payload": {
-		"tokenId": "7ngdf3ww3u84t33x",
-		"scope": "read",
-		"expiresAt": "2026-05-20T16:58:14.548Z"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-20T16:58:14.548Z"
-	}
+  "type": "cf.artifacts.repo.token.created",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "default",
+    "repoName": "token-evt-repo"
+  },
+  "payload": {
+    "tokenId": "7ngdf3ww3u84t33x",
+    "scope": "read",
+    "expiresAt": "2026-05-20T16:58:14.548Z"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-20T16:58:14.548Z"
+  }
 }
 ```
 
@@ -265,20 +267,20 @@ Triggered when a repo-scoped token is revoked. Includes the token ID.
 
 ```json
 {
-	"type": "cf.artifacts.repo.token.revoked",
-	"source": {
-		"type": "artifacts.repo",
-		"namespace": "default",
-		"repoName": "token-evt-repo"
-	},
-	"payload": {
-		"tokenId": "7ngdf3ww3u84t33x"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2026-05-20T16:58:14.548Z"
-	}
+  "type": "cf.artifacts.repo.token.revoked",
+  "source": {
+    "type": "artifacts.repo",
+    "namespace": "default",
+    "repoName": "token-evt-repo"
+  },
+  "payload": {
+    "tokenId": "7ngdf3ww3u84t33x"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "0ab4c7b45a39491ba5da2973f3d093a6",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2026-05-20T16:58:14.548Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/kv-events.mdx b/src/content/partials/queues/event-subscriptions/kv-events.mdx
index e824a2a4d79909a..41f5c1399c2dda4 100644
--- a/src/content/partials/queues/event-subscriptions/kv-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/kv-events.mdx
@@ -6,20 +6,20 @@ Triggered when a namespace is created.
 
 ```json
 {
-	"type": "cf.kv.namespace.created",
-	"source": {
-		"type": "kv"
-	},
-	"payload": {
-		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "my-kv-namespace"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.kv.namespace.created",
+  "source": {
+    "type": "kv"
+  },
+  "payload": {
+    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "my-kv-namespace"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,19 +31,19 @@ Triggered when a namespace is deleted.
 
 ```json
 {
-	"type": "cf.kv.namespace.deleted",
-	"source": {
-		"type": "kv"
-	},
-	"payload": {
-		"id": "ns-12345678-90ab-cdef-1234-567890abcdef",
-		"name": "my-kv-namespace"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.kv.namespace.deleted",
+  "source": {
+    "type": "kv"
+  },
+  "payload": {
+    "id": "ns-12345678-90ab-cdef-1234-567890abcdef",
+    "name": "my-kv-namespace"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/r2-events.mdx b/src/content/partials/queues/event-subscriptions/r2-events.mdx
index 30261e144e2610c..b50d8c3a1c19d49 100644
--- a/src/content/partials/queues/event-subscriptions/r2-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/r2-events.mdx
@@ -6,22 +6,22 @@ Triggered when a bucket is created.
 
 ```json
 {
-	"type": "cf.r2.bucket.created",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"jurisdiction": "default",
-		"location": "WNAM",
-		"storageClass": "Standard"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.r2.bucket.created",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "jurisdiction": "default",
+    "location": "WNAM",
+    "storageClass": "Standard"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -33,19 +33,19 @@ Triggered when a bucket is deleted.
 
 ```json
 {
-	"type": "cf.r2.bucket.deleted",
-	"source": {
-		"type": "r2"
-	},
-	"payload": {
-		"name": "my-bucket",
-		"jurisdiction": "default"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.r2.bucket.deleted",
+  "source": {
+    "type": "r2"
+  },
+  "payload": {
+    "name": "my-bucket",
+    "jurisdiction": "default"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
index 0cb885462b37f7b..4cae246e7055fa3 100644
--- a/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/super-slurper-events.mdx
@@ -6,33 +6,33 @@ Triggered when a migration job starts.
 
 ```json
 {
-	"type": "cf.superSlurper.job.started",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"overwrite": true,
-		"pathPrefix": "migrations/",
-		"source": {
-			"provider": "s3",
-			"bucket": "source-bucket",
-			"region": "us-east-1",
-			"endpoint": "s3.amazonaws.com"
-		},
-		"destination": {
-			"provider": "r2",
-			"bucket": "destination-bucket",
-			"jurisdiction": "default"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.started",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "overwrite": true,
+    "pathPrefix": "migrations/",
+    "source": {
+      "provider": "s3",
+      "bucket": "source-bucket",
+      "region": "us-east-1",
+      "endpoint": "s3.amazonaws.com"
+    },
+    "destination": {
+      "provider": "r2",
+      "bucket": "destination-bucket",
+      "jurisdiction": "default"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -44,19 +44,19 @@ Triggered when a migration job pauses.
 
 ```json
 {
-	"type": "cf.superSlurper.job.paused",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.paused",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -68,19 +68,19 @@ Triggered when a migration job resumes.
 
 ```json
 {
-	"type": "cf.superSlurper.job.resumed",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.resumed",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -92,23 +92,23 @@ Triggered when a migration job finishes.
 
 ```json
 {
-	"type": "cf.superSlurper.job.completed",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"totalObjectsCount": 1000,
-		"skippedObjectsCount": 10,
-		"migratedObjectsCount": 980,
-		"failedObjectsCount": 10
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.completed",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "totalObjectsCount": 1000,
+    "skippedObjectsCount": 10,
+    "migratedObjectsCount": 980,
+    "failedObjectsCount": 10
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -120,23 +120,23 @@ Triggered when a migration job is manually aborted.
 
 ```json
 {
-	"type": "cf.superSlurper.job.aborted",
-	"source": {
-		"type": "superSlurper"
-	},
-	"payload": {
-		"id": "job-12345678-90ab-cdef-1234-567890abcdef",
-		"totalObjectsCount": 1000,
-		"skippedObjectsCount": 100,
-		"migratedObjectsCount": 500,
-		"failedObjectsCount": 50
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.aborted",
+  "source": {
+    "type": "superSlurper"
+  },
+  "payload": {
+    "id": "job-12345678-90ab-cdef-1234-567890abcdef",
+    "totalObjectsCount": 1000,
+    "skippedObjectsCount": 100,
+    "migratedObjectsCount": 500,
+    "failedObjectsCount": 50
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -148,19 +148,19 @@ Triggered when an object is migrated.
 
 ```json
 {
-	"type": "cf.superSlurper.job.object.migrated",
-	"source": {
-		"type": "superSlurper.job",
-		"jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"payload": {
-		"key": "migrations/file.txt"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.superSlurper.job.object.migrated",
+  "source": {
+    "type": "superSlurper.job",
+    "jobId": "job-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "payload": {
+    "key": "migrations/file.txt"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
index e9422149256d246..fbdfca03358751d 100644
--- a/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/vectorize-events.mdx
@@ -6,24 +6,24 @@ Triggered when an index is created.
 
 ```json
 {
-	"type": "cf.vectorize.index.created",
-	"source": {
-		"type": "vectorize"
-	},
-	"payload": {
-		"name": "my-vector-index",
-		"description": "Index for embeddings",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"modifiedAt": "2025-05-01T02:48:57.132Z",
-		"dimensions": 1536,
-		"metric": "cosine"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.vectorize.index.created",
+  "source": {
+    "type": "vectorize"
+  },
+  "payload": {
+    "name": "my-vector-index",
+    "description": "Index for embeddings",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "modifiedAt": "2025-05-01T02:48:57.132Z",
+    "dimensions": 1536,
+    "metric": "cosine"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -35,18 +35,18 @@ Triggered when an index is deleted.
 
 ```json
 {
-	"type": "cf.vectorize.index.deleted",
-	"source": {
-		"type": "vectorize"
-	},
-	"payload": {
-		"name": "my-vector-index"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.vectorize.index.deleted",
+  "source": {
+    "type": "vectorize"
+  },
+  "payload": {
+    "name": "my-vector-index"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
index c28ded25de74231..0353629c8d35492 100644
--- a/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-ai-events.mdx
@@ -6,20 +6,20 @@ Triggered when a batch request is queued.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.queued",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.queued",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -31,20 +31,20 @@ Triggered when a batch request has completed.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.succeeded",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.succeeded",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -56,22 +56,22 @@ Triggered when a batch request has failed.
 
 ```json
 {
-	"type": "cf.workersAi.model.batch.failed",
-	"source": {
-		"type": "workersAi.model",
-		"modelName": "@cf/baai/bge-base-en-v1.5"
-	},
-	"payload": {
-		"requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
-		"message": "Model execution failed",
-		"internalCode": 5001,
-		"httpCode": 500
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersAi.model.batch.failed",
+  "source": {
+    "type": "workersAi.model",
+    "modelName": "@cf/baai/bge-base-en-v1.5"
+  },
+  "payload": {
+    "requestId": "req-12345678-90ab-cdef-1234-567890abcdef",
+    "message": "Model execution failed",
+    "internalCode": 5001,
+    "httpCode": 500
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
index c0f0508d1e6468e..5a30ffa88665135 100644
--- a/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workers-builds-events.mdx
@@ -6,39 +6,39 @@ Triggered when a build starts.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.started",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "running",
-		"buildOutcome": null,
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": null,
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.started",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "running",
+    "buildOutcome": null,
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": null,
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -50,39 +50,39 @@ Triggered when a build fails.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.failed",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "failed",
-		"buildOutcome": "failure",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:50:00.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.failed",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "failed",
+    "buildOutcome": "failure",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:50:00.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -94,39 +94,39 @@ Triggered when a build is canceled.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.canceled",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "canceled",
-		"buildOutcome": "canceled",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:49:30.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.canceled",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "canceled",
+    "buildOutcome": "canceled",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:49:30.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -138,38 +138,38 @@ Triggered when a build succeeds.
 
 ```json
 {
-	"type": "cf.workersBuilds.worker.build.succeeded",
-	"source": {
-		"type": "workersBuilds.worker",
-		"workerName": "my-worker"
-	},
-	"payload": {
-		"buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
-		"status": "success",
-		"buildOutcome": "success",
-		"createdAt": "2025-05-01T02:48:57.132Z",
-		"initializingAt": "2025-05-01T02:48:58.132Z",
-		"runningAt": "2025-05-01T02:48:59.132Z",
-		"stoppedAt": "2025-05-01T02:50:15.132Z",
-		"buildTriggerMetadata": {
-			"buildTriggerSource": "push_event",
-			"branch": "main",
-			"commitHash": "abc123def456",
-			"commitMessage": "Fix bug in authentication",
-			"author": "developer@example.com",
-			"buildCommand": "npm run build",
-			"deployCommand": "wrangler deploy",
-			"rootDirectory": "/",
-			"repoName": "my-worker-repo",
-			"providerAccountName": "github-user",
-			"providerType": "github"
-		}
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workersBuilds.worker.build.succeeded",
+  "source": {
+    "type": "workersBuilds.worker",
+    "workerName": "my-worker"
+  },
+  "payload": {
+    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
+    "status": "success",
+    "buildOutcome": "success",
+    "createdAt": "2025-05-01T02:48:57.132Z",
+    "initializingAt": "2025-05-01T02:48:58.132Z",
+    "runningAt": "2025-05-01T02:48:59.132Z",
+    "stoppedAt": "2025-05-01T02:50:15.132Z",
+    "buildTriggerMetadata": {
+      "buildTriggerSource": "push_event",
+      "branch": "main",
+      "commitHash": "abc123def456",
+      "commitMessage": "Fix bug in authentication",
+      "author": "developer@example.com",
+      "buildCommand": "npm run build",
+      "deployCommand": "wrangler deploy",
+      "rootDirectory": "/",
+      "repoName": "my-worker-repo",
+      "providerAccountName": "github-user",
+      "providerType": "github"
+    }
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/queues/event-subscriptions/workflows-events.mdx b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
index 6c814481a6dbed4..3df38e1c77de3c5 100644
--- a/src/content/partials/queues/event-subscriptions/workflows-events.mdx
+++ b/src/content/partials/queues/event-subscriptions/workflows-events.mdx
@@ -6,21 +6,21 @@ Triggered when an instance was created and is awaiting execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.queued",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.queued",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -32,21 +32,21 @@ Triggered when an instance starts or resumes execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.started",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.started",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -58,21 +58,21 @@ Triggered when an instance pauses execution.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.paused",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.paused",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -84,21 +84,21 @@ Triggered when an instance step throws an error.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.errored",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.errored",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -110,21 +110,21 @@ Triggered when an instance is manually terminated.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.terminated",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.terminated",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
 
@@ -136,20 +136,20 @@ Triggered when an instance finishes execution successfully.
 
 ```json
 {
-	"type": "cf.workflows.workflow.instance.completed",
-	"source": {
-		"type": "workflows.workflow",
-		"workflowName": "my-workflow"
-	},
-	"payload": {
-		"versionId": "v1",
-		"instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
-	},
-	"metadata": {
-		"accountId": "f9f79265f388666de8122cfb508d7776",
-		"eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
-		"eventSchemaVersion": 1,
-		"eventTimestamp": "2025-05-01T02:48:57.132Z"
-	}
+  "type": "cf.workflows.workflow.instance.completed",
+  "source": {
+    "type": "workflows.workflow",
+    "workflowName": "my-workflow"
+  },
+  "payload": {
+    "versionId": "v1",
+    "instanceId": "inst-12345678-90ab-cdef-1234-567890abcdef"
+  },
+  "metadata": {
+    "accountId": "f9f79265f388666de8122cfb508d7776",
+    "eventSubscriptionId": "1830c4bb612e43c3af7f4cada31fbf3f",
+    "eventSchemaVersion": 1,
+    "eventTimestamp": "2025-05-01T02:48:57.132Z"
+  }
 }
 ```
diff --git a/src/content/partials/r2/custom-domain-steps.mdx b/src/content/partials/r2/custom-domain-steps.mdx
index 1b858090ebc584b..f5c65596995f046 100644
--- a/src/content/partials/r2/custom-domain-steps.mdx
+++ b/src/content/partials/r2/custom-domain-steps.mdx
@@ -7,7 +7,6 @@ import { DashButton } from "~/components";
 1. In the Cloudflare dashboard, go to the **R2 object storage** page.
 
    <DashButton url="/?to=/:account/r2/overview" />
-
 2. Select your bucket.
 3. Select **Settings**.
 4. Under **Custom Domains**, select **Add**.
diff --git a/src/content/partials/r2/link-to-workers-r2-api.mdx b/src/content/partials/r2/link-to-workers-r2-api.mdx
index 22e4c599d0521ab..c18ac02fda8ef0a 100644
--- a/src/content/partials/r2/link-to-workers-r2-api.mdx
+++ b/src/content/partials/r2/link-to-workers-r2-api.mdx
@@ -4,4 +4,4 @@
 
 ## Other resources
 
-For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
+For information on R2 Workers Binding API, refer to [R2 Workers API reference](/r2/api/workers/workers-api-reference/).
\ No newline at end of file
diff --git a/src/content/partials/r2/migrator-etag-caveat.mdx b/src/content/partials/r2/migrator-etag-caveat.mdx
index 134d0b7745e8eea..5b40fec510b86ec 100644
--- a/src/content/partials/r2/migrator-etag-caveat.mdx
+++ b/src/content/partials/r2/migrator-etag-caveat.mdx
@@ -1,8 +1,9 @@
 ---
 inputParameters: param1
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 While R2's ETag generation is compatible with S3's during the regular course of operations, ETags are not guaranteed to be equal when an object is migrated using {props.one}.
 {props.one} makes autonomous decisions about the operations it uses when migrating objects to optimize for performance and network usage. It may choose to migrate an object in multiple parts, which affects [ETag calculation](/r2/objects/upload-objects/#etags).
diff --git a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
index 1bdda7b3e476265..3767632424c95a7 100644
--- a/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/create-your-own-ui-examples.mdx
@@ -1,13 +1,12 @@
 ---
 {}
----
 
+---
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
-
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/create-your-own-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/create-your-own-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/create-your-own-ui)
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
index f74bb9079e70dd4..c50d7c9cec90a22 100644
--- a/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
+++ b/src/content/partials/realtime/realtimekit/common/default-meeting-examples.mdx
@@ -1,13 +1,12 @@
 ---
 {}
----
 
+---
 ### Code Examples
 
 If you prefer to learn by seeing examples, please check out the respective example repositories.
 
 #### Web Examples
-
 - [Web Components](https://github.com/cloudflare/realtimekit-web-examples/tree/main/html-examples/examples/default-meeting-ui)
 - [React](https://github.com/cloudflare/realtimekit-web-examples/tree/main/react-examples/examples/default-meeting-ui)
-- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
+- [Angular](https://github.com/cloudflare/realtimekit-web-examples/tree/main/angular-examples/examples/default-meeting-ui)
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
index 87e72e9cc2d11a8..59cb825253d7aa7 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-close-breakout.mdx
@@ -1,22 +1,21 @@
 ---
 {}
----
 
+---
 ```js
 await meeting.connectedMeetings.deleteMeetings([
-	"MEETING_ID_TO_CLOSE_1",
-	"MEETING_ID_TO_CLOSE_2",
+  "MEETING_ID_TO_CLOSE_1",
+  "MEETING_ID_TO_CLOSE_2",
 ]);
 ```
-
 This would also trigger `stateUpdate` event updating the list of breakout rooms & participants.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
-	console.log("stateUpdate", { meetings, parentMeeting });
+meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
+  console.log("stateUpdate", {meetings, parentMeeting});
 });
 
 // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
 console.log("Meetings List", meeting.connectedMeetings.meetings);
 console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
index 7c577d42c671773..f4af17e0a5883c0 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-creation-sdk-api.mdx
@@ -1,20 +1,15 @@
 ---
 {}
----
 
+---
 ```js
 const breakoutRooms = await meeting.connectedMeetings.createMeetings([
-	{ title: "Breakout Room 1" },
-	{ title: "Breakout Room 2" },
-	{ title: "Breakout Room 3" },
+  { title: "Breakout Room 1" },
+  { title: "Breakout Room 2" },
+  { title: "Breakout Room 3" },
 ]);
 
-console.log(
-	"Created Breakout Rooms: ",
-	breakoutRooms
-		.map((room) => "Id:: " + room.id + " --- Title:: " + room.title)
-		.join("\n"),
-);
+console.log("Created Breakout Rooms: ", breakoutRooms.map((room) => "Id:: " + room.id + " --- Title:: " + room.title).join("\n"));
 ```
 
-`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
+`breakoutRooms` is an array of basic meeting information such as id and title. You can use the `id` of these objects to move participants to the breakout room.
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
index 3047851f75d834f..dfde78c93ff676c 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-fetch-meetings-sdk-api.mdx
@@ -1,10 +1,10 @@
 ---
 {}
+
 ---
 
 ```js
-const breakoutRoomsInfo =
-	await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
 ```
 
 `breakoutRoomsInfo` is an object containing the list of breakout rooms and their participants, along with details of the parent meeting.
@@ -14,11 +14,11 @@ This data can be used to display the list of breakout rooms & participants in th
 You can also listen to `stateUpdate` event to get the latest list of breakout rooms & participants, as they are updated in real-time.
 
 ```js
-meeting.connectedMeetings.on("stateUpdate", ({ meetings, parentMeeting }) => {
-	console.log("stateUpdate", { meetings, parentMeeting });
+meeting.connectedMeetings.on("stateUpdate", ({meetings, parentMeeting}) => {
+  console.log("stateUpdate", {meetings, parentMeeting});
 
-	// Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
-	console.log("Meetings List", meeting.connectedMeetings.meetings);
-	console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
+  // Alternatively, you can access the meetings and parentMeeting from the connectedMeetings object
+  console.log("Meetings List", meeting.connectedMeetings.meetings);
+  console.log("Parent Meeting", meeting.connectedMeetings.parentMeeting);
 });
 ```
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
index f77df15d7e5faa7..e10a85c8c58bf11 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-handle-breakout-events.mdx
@@ -1,16 +1,13 @@
 ---
 {}
+
 ---
 
 ```js
 // Listen to changingMeeting event to show a custom UI to indicate that a meeting switch is happening
 meeting.connectedMeetings.on("changingMeeting", (meetingId) => {
-	console.log(
-		"Switching to breakout room or main meeting with id: " + meetingId,
-	);
-	console.log(
-		"Show a Custom UI to indicate that a meeting switch is happening",
-	);
+	console.log("Switching to breakout room or main meeting with id: " + meetingId);
+	console.log("Show a Custom UI to indicate that a meeting switch is happening");
 });
 
 // Listen to meetingChanged event to update the meeting object reference
@@ -18,4 +15,4 @@ meeting.connectedMeetings.on("meetingChanged", (newMeeting) => {
 	console.log("Switched to breakout room or main meeting");
 	console.log("Every action now should be performed on this meeting");
 });
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
index fbd4d918d2faf36..be50df93029763f 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-participant-sdk-api.mdx
@@ -1,21 +1,20 @@
 ---
 {}
----
 
+---
 ```js
 // Retrieve list of breakout rooms & participants
-const breakoutRoomsInfo =
-	await meeting.connectedMeetings.getConnectedMeetings();
+const breakoutRoomsInfo = await meeting.connectedMeetings.getConnectedMeetings();
 
 /*
- * You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
- * Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
- */
+* You can retrieve meetingIds and participantIds from the breakoutRoomsInfo object.
+* Based on where the participant currently is, you can decide the sourceMeetingId and targetMeetingId.
+*/
 
 // Move participants to breakout rooms
 const response = await meeting.connectedMeetings.moveParticipants(
-	"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-	"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-	["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
+  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+  ["PARTICIPANT_ID_1", "PARTICIPANT_ID_2"], // participantIds, array of participant ids to be moved
 );
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
index 66e13a506f735ec..1491da6d62c305b 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-move-preset-participant-sdk-api.mdx
@@ -1,12 +1,11 @@
 ---
 {}
----
 
+---
 ```js
-const response =
-	await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
-		"SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
-		"TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
-		[{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
-	);
-```
+const response = await meeting.connectedMeetings.moveParticipantsWithCustomPreset(
+  "SOURCE_MEETING_ID", // sourceMeetingId, meeting id where participants are currently in
+  "TARGET_MEETING_ID", // targetMeetingId, meeting id where participants are to be moved
+  [{ presetId: "PRESET_ID_1" }, { presetId: "PRESET_ID_2" }], // array of objects with presetId field
+);
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
index 796eed925700f90..40805bd8dd7ae50 100644
--- a/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
+++ b/src/content/partials/realtime/realtimekit/web/breakout-room-permission-check.mdx
@@ -1,24 +1,20 @@
 ---
 {}
----
 
+---
 ```js
 // Check if breakout rooms are supported
-const areBreakoutRoomsSupported =
-	meeting.connectedMeetings.supportsConnectedMeetings;
+const areBreakoutRoomsSupported = meeting.connectedMeetings.supportsConnectedMeetings;
 
 // Check if any breakout rooms are already created
 const areBreakoutRoomsActive = meeting.connectedMeetings.isActive;
 
 // Check if the current participant has permission to create breakout rooms
-const hasPermissionToCreateBreakoutRooms =
-	meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
+const hasPermissionToCreateBreakoutRooms = meeting.self.permissions.connectedMeetings.canAlterConnectedMeetings;
 
 // Check if the current participant has permission to switch to parent meeting
-const hasPermissionToSwitchToParentMeeting =
-	meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
+const hasPermissionToSwitchToParentMeeting = meeting.self.permissions.connectedMeetings.canSwitchToParentMeeting;
 
 // Check if the current participant has permission to switch to connected meeting
-const hasPermissionToSwitchToConnectedMeeting =
-	meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
-```
+const hasPermissionToSwitchToConnectedMeeting = meeting.self.permissions.connectedMeetings.canSwitchConnectedMeetings;
+```
\ No newline at end of file
diff --git a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
index e3f7d0532664f23..7ecbc3317f46d23 100644
--- a/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
+++ b/src/content/partials/realtime/realtimekit/web/language-pack-json.mdx
@@ -1,417 +1,417 @@
 ---
 {}
----
 
+---
 ```json
 {
-	"about_call": "About Call",
-	"screen": "Screen",
-	"camera": "Camera",
-	"leave": "Leave",
-	"dismiss": "Dismiss",
-	"logo": "Logo",
-	"page": "Page",
-	"more": "More",
-	"page.prev": "Previous Page",
-	"page.next": "Next Page",
-	"layout": "Layout",
-	"layout.auto": "Auto Layout",
-	"settings": "Settings",
-	"file": "File",
-	"image": "Image",
-	"connection": "Connection",
-	"leave_confirmation": "Are you sure you want to leave the call?",
-	"cancel": "Cancel",
-	"yes": "Yes",
-	"(you)": "(you)",
-	"you": "You",
-	"everyone": "Everyone",
-	"to": "To",
-	"mute": "Mute",
-	"kick": "Kick",
-	"pin": "Pin",
-	"pinned": "Pinned",
-	"accept": "Accept",
-	"unpin": "Unpin",
-	"pip_on": "Show PiP",
-	"pip_off": "Hide PiP",
-	"viewers": "Viewers",
-	"join": "Join",
-	"joined": "Joined",
-	"create": "Create",
-	"close": "Close",
-	"ask": "Ask",
-	"type": "Type",
-	"activate": "Activate",
-	"requests": "Requests",
-	"mic_off": "Mic Off",
-	"disable_mic": "Disable Mic",
-	"mic_on": "Mic On",
-	"enable_mic": "Enable Mic",
-	"audio": "Audio",
-	"test": "Test",
-	"minimize": "Hide Tile",
-	"maximize": "Show Tile",
-	"mute_all": "Mute all",
-	"mute_all.description": "Everyone else in the meeting will be muted.",
-	"mute_all.header": "Are you sure?",
-	"mute_all.allow_unmute": "Allow others to unmute",
-	"video_off": "Video Off",
-	"disable_video": "Disable Video",
-	"video_on": "Video On",
-	"enable_video": "Enable Video",
-	"video": "Video",
-	"offline": "You're offline",
-	"offline.description": "Please ensure that you are connected to the internet.",
-	"disconnected": "You haven't joined the meeting.",
-	"failed": "You've been disconnected",
-	"failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
-	"disconnected.description": "Please join the meeting in order to see and interact with other participants.",
-	"participants": "Participants",
-	"participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
-	"participants.empty_list": "It looks like nobody is here.",
-	"participants.no_pending_requests": "There are no pending requests.",
-	"participants.turn_off_video": "Turn off video",
-	"polls": "Polls",
-	"polls.by": "Poll by",
-	"polls.question": "Poll Question",
-	"polls.question.placeholder": "What is your poll for?",
-	"polls.answers": "Answers",
-	"polls.option": "Add an option.",
-	"polls.option.placeholder": "Enter an option",
-	"polls.results.anon": "Anonymous",
-	"polls.results.hide": "Hide results before voting",
-	"polls.create": "Create Poll",
-	"polls.cancel": "Cancel Poll Creation",
-	"polls.empty": "No polls available",
-	"polls.errors.question_required": "Question is required.",
-	"polls.errors.empty_option": "Empty options not allowed.",
-	"screenshare": "Screen Share",
-	"screenshare.min_preview": "Minimize Preview",
-	"screenshare.max_preview": "Expand Preview",
-	"screenshare.shared": "Your screen is being shared.",
-	"screenshare.start": "Share Screen",
-	"screenshare.stop": "Stop Sharing",
-	"screenshare.error.unknown": "An error occurred while starting screenshare.",
-	"screenshare.error.max_count": "Maximum screen share limit reached.",
-	"plugins": "Plugins",
-	"perm_denied": "Permission denied by browser.",
-	"perm_denied.audio": "Mic Permission denied by browser",
-	"perm_denied.video": "Camera Permission denied by browser",
-	"perm_denied.screenshare": "Screenshare Permission denied by browser",
-	"perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
-	"perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
-	"perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
-	"perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
-	"perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
-	"perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
-	"perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
-	"perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
-	"perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
-	"perm_sys_denied": "Permission denied by system",
-	"perm_sys_denied.audio": "Mic permission denied by system",
-	"perm_sys_denied.video": "Camera permission denied by system",
-	"perm_sys_denied.screenshare": "Screenshare permission denied by system",
-	"perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
-	"perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
-	"perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
-	"perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
-	"perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
-	"perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
-	"perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
-	"perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
-	"perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
-	"perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
-	"perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
-	"perm_could_not_start": "Could not capture device.",
-	"perm_could_not_start.audio": "Unable to start your Microphone",
-	"perm_could_not_start.video": "Unable to start your Camera",
-	"perm_could_not_start.screenshare": "Unable to start your Screenshare",
-	"perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
-	"perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
-	"perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
-	"full_screen": "Full Screen",
-	"full_screen.exit": "Exit Full Screen",
-	"waitlist.header_title": "Waiting",
-	"waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
-	"waitlist.deny_request": "Deny request",
-	"waitlist.accept_request": "Accept request",
-	"waitlist.accept_all": "Accept all",
-	"stage_request.header_title": "Join Stage Requests",
-	"stage_request.deny_request": "Deny request",
-	"stage_request.accept_request": "Accept request",
-	"stage_request.accept_all": "Accept all",
-	"stage_request.deny_all": "Deny all",
-	"stage_request.approval_pending": "Pending",
-	"stage_request.denied": "Denied",
-	"stage_request.request": "Join stage",
-	"stage_request.requested": "Requested",
-	"stage_request.cancel_request": "Cancel request",
-	"stage_request.leave_stage": "Leave stage",
-	"stage_request.request_tip": "Request to join the discussion",
-	"stage_request.leave_tip": "Leave the stage",
-	"stage_request.pending_tip": "Request pending",
-	"stage_request.denied_tip": "Rejected request",
-	"stage.empty_host": "The stage is empty",
-	"stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
-	"stage.empty_viewer": "There is no one on stage",
-	"stage.remove_from_stage": "Remove from stage",
-	"stage.invited_notification": "has been invited to join stage.",
-	"stage.add_to_stage": "Invite to stage",
-	"stage.join_title": "Join Stage",
-	"stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
-	"stage.join_cancel": "Cancel",
-	"stage.join_confirm": "Join",
-	"setup_screen.join_in_as": "Joining as",
-	"setup_screen.your_name": "Your name",
-	"stage.reconnecting": "Reconnecting...",
-	"recording.label": "REC",
-	"recording.indicator": "This meeting is being recorded.",
-	"recording.started": "This meeting is being recorded.",
-	"recording.stopped": "Recording for this meeting has been stopped.",
-	"recording.paused": "Recording for this meeting has been paused.",
-	"recording.error.start": "Error while starting recording.",
-	"recording.error.stop": "Error while stopping recording",
-	"recording.error.resume": "Error while resuming recording",
-	"recording.start": "Start Recording",
-	"recording.stop": "Stop Recording",
-	"recording.resume": "Resume Recording",
-	"recording.starting": "Starting",
-	"recording.stopping": "Stopping",
-	"recording.loading": "Loading",
-	"recording.idle": "Record",
-	"audio_playback": "Play Audio",
-	"audio_playback.title": "Allow Audio Playback",
-	"audio_playback.description": "In order to play audio properly on your device, click the button below.",
-	"breakout_rooms": "Breakout Rooms",
-	"breakout_rooms.room_config_header": "Create Breakout",
-	"breakout_rooms.join_breakout_header": "Join Breakout",
-	"breakout_rooms.empty": "Nobody here yet.",
-	"breakout_rooms.delete": "Delete Room",
-	"breakout_rooms.switch": "Switch",
-	"breakout_rooms.main_room": "Main Room",
-	"breakout_rooms.shuffle_participants": "Shuffle Participants",
-	"breakout_rooms.deselect": "Deselect",
-	"breakout_rooms.selected": "selected",
-	"breakout_rooms.num_of_rooms": "No. of Rooms",
-	"breakout_rooms.approx": "Approx.",
-	"breakout_rooms.participants_per_room": "participants/room",
-	"breakout_rooms.division_text": "when equally divided.",
-	"breakout_rooms.start_breakout": "Start Breakout",
-	"breakout_rooms.close_breakout": "Close Breakout",
-	"breakout_rooms.update_breakout": "Update Breakout",
-	"breakout_rooms.discard_changes": "Discard Changes",
-	"breakout_rooms.room": "Room",
-	"breakout_rooms.rooms": "Rooms",
-	"breakout_rooms.room_name": "Room Name",
-	"breakout_rooms.edit_room_name": "Edit Room Name",
-	"breakout_rooms.save_room_name": "Save Room Name",
-	"breakout_rooms.add_room": "Add",
-	"breakout_rooms.add_room_brief": "Add Room",
-	"breakout_rooms.select_all": "Select all",
-	"breakout_rooms.unassign_all": "Unassign all",
-	"breakout_rooms.assign": "Assign",
-	"breakout_rooms.assign_participants": "Assign Participants",
-	"breakout_rooms.none_assigned": "No participants assigned yet",
-	"breakout_rooms.drag_drop_participants": "Drag and drop participants",
-	"breakout_rooms.click_drop_participants": "Click here to assign",
-	"breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
-	"breakout_rooms.status.select_room": "Select a room to assign",
-	"breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
-	"breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
-	"breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
-	"breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
-	"breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
-	"breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
-	"breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
-	"breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
-	"breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
-	"breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
-	"breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
-	"breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
-	"breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
-	"breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
-	"breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
-	"breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
-	"breakout_rooms.all_assigned": "All participants have been assigned",
-	"breakout_rooms.empty_main_room": "No more participants in the main room.",
-	"breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
-	"breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
-	"ai": "AI",
-	"ai.meeting_ai": "MeetingAI",
-	"ai.home": "Home",
-	"ai.transcriptions": "Transcriptions",
-	"ai.personal": "Personal",
-	"ai.caption_view": "Caption View",
-	"ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
-	"ai.chat.summarise": "Hey AI, summarise this call",
-	"ai.chat.agenda": "Hey AI, what is today's agenda?",
-	"search": "Search",
-	"search.could_not_find": "Couldn't find a participant with the specified name or ID.",
-	"search.empty": "It looks like nobody is here.",
-	"end": "End Meeting",
-	"end.all": "End meeting for all",
-	"ended": "The meeting ended.",
-	"ended.rejected": "Your request to join the meeting was denied.",
-	"ended.left": "You left the meeting.",
-	"ended.kicked": "You were removed from the meeting.",
-	"ended.disconnected": "The call ended because the connection was lost.",
-	"ended.network": "Please check your internet connection and try again.",
-	"ended.unauthorized": "You are not authorized to join this meeting.",
-	"network": "Network",
-	"network.reconnecting": "Connection lost. Trying to reconnect.",
-	"network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
-	"network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
-	"network.leaving": "Automatically leaving the meeting in 10 seconds.",
-	"network.restored": "Connection restored",
-	"network.delay": "Taking too long to reconnect.",
-	"network.lost": "Connection lost",
-	"network.lost_extended": "Connection lost. Please check your network connection.",
-	"livestream": "Livestream",
-	"livestream.indicator": "This meeting is being livestreamed.",
-	"livestream.skip": "Skip to Live",
-	"livestream.idle": "Waiting to go live.",
-	"livestream.starting": "Livestream is starting...",
-	"livestream.stopping": "Livestream is stopping...",
-	"livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
-	"livestream.error.not_supported": "Player not supported.",
-	"livestream.error.not_found": "Playback URL not found.",
-	"livestream.error.unknown": "An unknown error occurred.",
-	"livestream.error.sync": "Could not sync livestream please try again later.",
-	"livestream.error.start": "Error while starting livestream.",
-	"livestream.error.stop": "Error while stopping livestream.",
-	"livestream.go_live": "Go Live",
-	"livestream.end_live": "End Live",
-	"livestream.error": "Error",
-	"cta.help": "Need help on how to do this?",
-	"cta.continue": "Ignore",
-	"cta.reload": "Reload",
-	"cta.confirmation": "Are you sure?",
-	"cta.system_settings": "Open Settings",
-	"remote_access.empty": "There are no remote requests, yet.",
-	"remote_access.requests": "The following people have requested remote control to your screen share.",
-	"remote_access.allow": "Please select whom you want to give access to.",
-	"remote_access.grant": "Grant access",
-	"remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
-	"chat": "Chat",
-	"chat.new": "New",
-	"chat.max_limit_warning": "Max Character Limit",
-	"chat.rate_limit_error": "Please wait before you can send another message",
-	"chat.new_channel": "Create new channel",
-	"chat.channel_name": "Enter channel name",
-	"chat.member_name": "Enter member name",
-	"chat.add_members": "Add members",
-	"chat.delete_msg": "Delete",
-	"chat.edit_msg": "Edit",
-	"chat.send_msg": "Send message",
-	"chat.send_attachment": "Drop files/images to send",
-	"chat.send_img": "Send an image",
-	"chat.send_file": "Send a file",
-	"chat.send_emoji": "Send an emoji",
-	"chat.update_msg": "Update message",
-	"chat.channel_members": "Channel Members",
-	"chat.img.loading": "Loading image",
-	"chat.error.img_not_found": "Image not found",
-	"chat.error.empty_results": "Couldn't find a member with the specified name.",
-	"chat.img.shared_by": "Shared by",
-	"chat.reply": "Reply",
-	"chat.message_placeholder": "Message..",
-	"chat.click_to_send": "Click to send as message",
-	"chat.search_msgs": "Search messages",
-	"chat.search_conversations": "Search conversations",
-	"chat.start_conversation": "Start a conversation..",
-	"chat.empty_search": "No messages found",
-	"chat.empty_channel": "Send a message to get started",
-	"chat.cancel_upload": "Cancel upload",
-	"chat.view_chats": "View chats",
-	"chat.everyone": "everyone",
-	"chat.pinned_msgs": "Pinned messages",
-	"chat.toggle_pinned_msgs": "Toggle pinned messages",
-	"date.today": "Today",
-	"date.yesterday": "Yesterday",
-	"date.sunday": "Sunday",
-	"date.monday": "Monday",
-	"date.tuesday": "Tuesday",
-	"date.wednesday": "Wednesday",
-	"date.thursday": "Thursday",
-	"date.friday": "Friday",
-	"date.saturday": "Saturday",
-	"list.empty": "No items found",
-	"grid.listening": "Listening",
-	"transcript.off": "Turn off Transcripts",
-	"transcript.on": "Turn on Transcripts",
-	"settings.notification_sound": "Notification sound",
-	"settings.microphone_input": "Microphone",
-	"settings.speaker_output": "Speaker",
-	"settings.mirror_video": "Mirror my Video",
-	"settings.camera_off": "Camera is off",
-	"dialog.close": "Close dialog",
-	"notifications.joined": "just joined",
-	"notifications.left": "left",
-	"notifications.requesting_to_join_meeting": "is requesting to join the meeting",
-	"notifications.requested_to_join_stage": "has requested to join stage",
-	"notifications.joined_stage": "has joined stage",
-	"notifications.request_to_join_accepted": "Request to join accepted",
-	"notifications.request_to_join_rejected": "Request to join rejected",
-	"notifications.accept": "Accept",
-	"notifications.new_poll_created_by": "New poll created by",
-	"notifications.connected_to": "Connected to",
-	"notifications.plugin_switched_to": "Plugin switched to",
-	"notifications.remote_control_requested": "has requested for remote control",
-	"notifications.remote_control_request_sent": "Sent remote control request to",
-	"notifications.remote_control_request_accepted": "has granted remote control",
-	"notifications.remote_control_granted": "Granted remote control to",
-	"notifications.remote_control_terminated": "Existing remote control has been terminated",
-	"debugger.troubleshooting.label": "Troubleshooting",
-	"debugger.quality.good": "Good",
-	"debugger.quality.average": "Average",
-	"debugger.quality.poor": "Poor",
-	"debugger.stats.bitrate.label": "Bitrate",
-	"debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
-	"debugger.stats.packet_loss.label": "Packet Loss",
-	"debugger.stats.packet_loss.description": "Amount of data lost during transfer",
-	"debugger.stats.jitter.label": "Jitter",
-	"debugger.stats.jitter.description": "Variance or fluctuation in latency",
-	"debugger.stats.cpu_limitations.label": "CPU Limitations",
-	"debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
-	"debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
-	"debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
-	"debugger.audio.label": "Audio",
-	"debugger.audio.troubleshooting.label": "Audio Troubleshooting",
-	"debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.audio.messages.enable_media": "Please enable mic to see the report.",
-	"debugger.audio.sections.network_media": "Network & Media",
-	"debugger.video.label": "Video",
-	"debugger.video.troubleshooting.label": "Video Troubleshooting",
-	"debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.video.messages.enable_media": "Please enable camera to see the report.",
-	"debugger.video.sections.network_media": "Network & Media",
-	"debugger.screenshare.label": "Screenshare",
-	"debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
-	"debugger.screenshare.sections.network_media": "Network & Media",
-	"debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
-	"debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
-	"debugger.system.label": "System",
-	"debugger.system.troubleshooting.label": "System Troubleshooting",
-	"debugger.system.sections.battery": "Battery",
-	"debugger.system.battery.level.label": "Battery Level",
-	"debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
-	"debugger.system.battery.charging.label": "Battery Charging Status",
-	"debugger.system.battery.charging.description": "A device running on power performs optimally.",
-	"debugger.system.battery.charging.is_charging": "Charging",
-	"debugger.system.battery.charging.is_not_charging": "Not charging"
+  "about_call": "About Call",
+  "screen": "Screen",
+  "camera": "Camera",
+  "leave": "Leave",
+  "dismiss": "Dismiss",
+  "logo": "Logo",
+  "page": "Page",
+  "more": "More",
+  "page.prev": "Previous Page",
+  "page.next": "Next Page",
+  "layout": "Layout",
+  "layout.auto": "Auto Layout",
+  "settings": "Settings",
+  "file": "File",
+  "image": "Image",
+  "connection": "Connection",
+  "leave_confirmation": "Are you sure you want to leave the call?",
+  "cancel": "Cancel",
+  "yes": "Yes",
+  "(you)": "(you)",
+  "you": "You",
+  "everyone": "Everyone",
+  "to": "To",
+  "mute": "Mute",
+  "kick": "Kick",
+  "pin": "Pin",
+  "pinned": "Pinned",
+  "accept": "Accept",
+  "unpin": "Unpin",
+  "pip_on": "Show PiP",
+  "pip_off": "Hide PiP",
+  "viewers": "Viewers",
+  "join": "Join",
+  "joined": "Joined",
+  "create": "Create",
+  "close": "Close",
+  "ask": "Ask",
+  "type": "Type",
+  "activate": "Activate",
+  "requests": "Requests",
+  "mic_off": "Mic Off",
+  "disable_mic": "Disable Mic",
+  "mic_on": "Mic On",
+  "enable_mic": "Enable Mic",
+  "audio": "Audio",
+  "test": "Test",
+  "minimize": "Hide Tile",
+  "maximize": "Show Tile",
+  "mute_all": "Mute all",
+  "mute_all.description": "Everyone else in the meeting will be muted.",
+  "mute_all.header": "Are you sure?",
+  "mute_all.allow_unmute": "Allow others to unmute",
+  "video_off": "Video Off",
+  "disable_video": "Disable Video",
+  "video_on": "Video On",
+  "enable_video": "Enable Video",
+  "video": "Video",
+  "offline": "You're offline",
+  "offline.description": "Please ensure that you are connected to the internet.",
+  "disconnected": "You haven't joined the meeting.",
+  "failed": "You've been disconnected",
+  "failed.description": "We could not connect you back to the meeting room. Please try rejoining the meeting.",
+  "disconnected.description": "Please join the meeting in order to see and interact with other participants.",
+  "participants": "Participants",
+  "participants.errors.empty_results": "Couldn't find a participant with the specified name or ID.",
+  "participants.empty_list": "It looks like nobody is here.",
+  "participants.no_pending_requests": "There are no pending requests.",
+  "participants.turn_off_video": "Turn off video",
+  "polls": "Polls",
+  "polls.by": "Poll by",
+  "polls.question": "Poll Question",
+  "polls.question.placeholder": "What is your poll for?",
+  "polls.answers": "Answers",
+  "polls.option": "Add an option.",
+  "polls.option.placeholder": "Enter an option",
+  "polls.results.anon": "Anonymous",
+  "polls.results.hide": "Hide results before voting",
+  "polls.create": "Create Poll",
+  "polls.cancel": "Cancel Poll Creation",
+  "polls.empty": "No polls available",
+  "polls.errors.question_required": "Question is required.",
+  "polls.errors.empty_option": "Empty options not allowed.",
+  "screenshare": "Screen Share",
+  "screenshare.min_preview": "Minimize Preview",
+  "screenshare.max_preview": "Expand Preview",
+  "screenshare.shared": "Your screen is being shared.",
+  "screenshare.start": "Share Screen",
+  "screenshare.stop": "Stop Sharing",
+  "screenshare.error.unknown": "An error occurred while starting screenshare.",
+  "screenshare.error.max_count": "Maximum screen share limit reached.",
+  "plugins": "Plugins",
+  "perm_denied": "Permission denied by browser.",
+  "perm_denied.audio": "Mic Permission denied by browser",
+  "perm_denied.video": "Camera Permission denied by browser",
+  "perm_denied.screenshare": "Screenshare Permission denied by browser",
+  "perm_denied.audio.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Microphone' permission is checked",
+  "perm_denied.video.chrome.message": "In the top navigation bar, click on the icon left to the URL and ensure  'Camera' permission is checked",
+  "perm_denied.screenshare.chrome.message": "Under Chrome settings, navigate to 'Privacy and Security > Site Settings > Permissions'. Select 'Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.safari.message": "Under Safari settings, navigate to 'Websites > Microphone', provide permission and reload this application.",
+  "perm_denied.video.safari.message": "Under Safari settings, navigate to 'Websites > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.safari.message": "Under Safari settings, navigate to 'Websites > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.microsoft edge.message": "Under Edge settings, navigate to 'Site Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Microphone', provide permission and reload this application.",
+  "perm_denied.video.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Camera', provide permission and reload this application.",
+  "perm_denied.screenshare.firefox.message": "Under Firefox settings, navigate to 'Privacy and Security > Permissions > Screenshare', provide permission and reload this application.",
+  "perm_denied.audio.others.message": "From your browser settings, enable 'Microphone' permissions and reload this application.",
+  "perm_denied.video.others.message": "From your browser settings, enable 'Camera' permissions and reload this application.",
+  "perm_denied.screenshare.others.message": "From your browser settings, enable 'Screenshare' permissions and reload this application.",
+  "perm_sys_denied": "Permission denied by system",
+  "perm_sys_denied.audio": "Mic permission denied by system",
+  "perm_sys_denied.video": "Camera permission denied by system",
+  "perm_sys_denied.screenshare": "Screenshare permission denied by system",
+  "perm_sys_denied.audio.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Microphone'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.video.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Camera'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.screenshare.macos.message": "Open Apple Menu, Navigate to 'System Settings > Privacy & Security > Screenshare'. Allow access to your browser and reload this application.",
+  "perm_sys_denied.audio.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Microphone', allow access to your browser and reload this application.",
+  "perm_sys_denied.video.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Camera', allow access to your browser and reload this application.",
+  "perm_sys_denied.screenshare.ios.message": "On your iPhone, navigate to 'Settings > Privacy > Screenshare', allow access to your browser and reload this application.",
+  "perm_sys_denied.audio.windows.message": "Go to windows settings, select 'Settings > Privacy > Microphone'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.video.windows.message": "Go to windows settings, select 'Settings > Privacy > Camera'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.screenshare.windows.message": "Go to windows settings, select 'Settings > Privacy > Screenshare'. Allow permissions to your browser and reload this application.",
+  "perm_sys_denied.audio.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Microphone permissions and reload this application.",
+  "perm_sys_denied.video.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Camera permissions and reload this application.",
+  "perm_sys_denied.screenshare.android.message": "On your device, navigate to 'Settings > Apps'. Select your browser, allow Screenshare permissions and reload this application.",
+  "perm_sys_denied.audio.others.message": "Navigate to your system settings. Allow 'Microphone' permissions for your browser and reload this application.",
+  "perm_sys_denied.video.others.message": "Navigate to your system settings. Allow 'Camera' permissions for your browser and reload this application.",
+  "perm_sys_denied.screenshare.others.message": "Navigate to your system settings. Allow 'Screenshare' permissions for your browser and reload this application.",
+  "perm_could_not_start": "Could not capture device.",
+  "perm_could_not_start.audio": "Unable to start your Microphone",
+  "perm_could_not_start.video": "Unable to start your Camera",
+  "perm_could_not_start.screenshare": "Unable to start your Screenshare",
+  "perm_could_not_start.audio.message": "Looks like the system could not capture your microphone. Please restart your device or upgrade your browser to fix this.",
+  "perm_could_not_start.video.message": "Looks like the system could not capture your camera. Please restart your device or upgrade your browser to fix this.",
+  "perm_could_not_start.screenshare.message": "Looks like the system could not capture your screenshare. Please restart your device or upgrade your browser to fix this.",
+  "full_screen": "Full Screen",
+  "full_screen.exit": "Exit Full Screen",
+  "waitlist.header_title": "Waiting",
+  "waitlist.body_text": "You are in the waiting room, the host will let you in soon.",
+  "waitlist.deny_request": "Deny request",
+  "waitlist.accept_request": "Accept request",
+  "waitlist.accept_all": "Accept all",
+  "stage_request.header_title": "Join Stage Requests",
+  "stage_request.deny_request": "Deny request",
+  "stage_request.accept_request": "Accept request",
+  "stage_request.accept_all": "Accept all",
+  "stage_request.deny_all": "Deny all",
+  "stage_request.approval_pending": "Pending",
+  "stage_request.denied": "Denied",
+  "stage_request.request": "Join stage",
+  "stage_request.requested": "Requested",
+  "stage_request.cancel_request": "Cancel request",
+  "stage_request.leave_stage": "Leave stage",
+  "stage_request.request_tip": "Request to join the discussion",
+  "stage_request.leave_tip": "Leave the stage",
+  "stage_request.pending_tip": "Request pending",
+  "stage_request.denied_tip": "Rejected request",
+  "stage.empty_host": "The stage is empty",
+  "stage.empty_host_summary": "You are off stage. You can manage stage request from the participants tab.",
+  "stage.empty_viewer": "There is no one on stage",
+  "stage.remove_from_stage": "Remove from stage",
+  "stage.invited_notification": "has been invited to join stage.",
+  "stage.add_to_stage": "Invite to stage",
+  "stage.join_title": "Join Stage",
+  "stage.join_summary": "You are about to join the stage, your video & audio as shown above will be visible to all participants.",
+  "stage.join_cancel": "Cancel",
+  "stage.join_confirm": "Join",
+  "setup_screen.join_in_as": "Joining as",
+  "setup_screen.your_name": "Your name",
+  "stage.reconnecting": "Reconnecting...",
+  "recording.label": "REC",
+  "recording.indicator": "This meeting is being recorded.",
+  "recording.started": "This meeting is being recorded.",
+  "recording.stopped": "Recording for this meeting has been stopped.",
+  "recording.paused": "Recording for this meeting has been paused.",
+  "recording.error.start": "Error while starting recording.",
+  "recording.error.stop": "Error while stopping recording",
+  "recording.error.resume": "Error while resuming recording",
+  "recording.start": "Start Recording",
+  "recording.stop": "Stop Recording",
+  "recording.resume": "Resume Recording",
+  "recording.starting": "Starting",
+  "recording.stopping": "Stopping",
+  "recording.loading": "Loading",
+  "recording.idle": "Record",
+  "audio_playback": "Play Audio",
+  "audio_playback.title": "Allow Audio Playback",
+  "audio_playback.description": "In order to play audio properly on your device, click the button below.",
+  "breakout_rooms": "Breakout Rooms",
+  "breakout_rooms.room_config_header": "Create Breakout",
+  "breakout_rooms.join_breakout_header": "Join Breakout",
+  "breakout_rooms.empty": "Nobody here yet.",
+  "breakout_rooms.delete": "Delete Room",
+  "breakout_rooms.switch": "Switch",
+  "breakout_rooms.main_room": "Main Room",
+  "breakout_rooms.shuffle_participants": "Shuffle Participants",
+  "breakout_rooms.deselect": "Deselect",
+  "breakout_rooms.selected": "selected",
+  "breakout_rooms.num_of_rooms": "No. of Rooms",
+  "breakout_rooms.approx": "Approx.",
+  "breakout_rooms.participants_per_room": "participants/room",
+  "breakout_rooms.division_text": "when equally divided.",
+  "breakout_rooms.start_breakout": "Start Breakout",
+  "breakout_rooms.close_breakout": "Close Breakout",
+  "breakout_rooms.update_breakout": "Update Breakout",
+  "breakout_rooms.discard_changes": "Discard Changes",
+  "breakout_rooms.room": "Room",
+  "breakout_rooms.rooms": "Rooms",
+  "breakout_rooms.room_name": "Room Name",
+  "breakout_rooms.edit_room_name": "Edit Room Name",
+  "breakout_rooms.save_room_name": "Save Room Name",
+  "breakout_rooms.add_room": "Add",
+  "breakout_rooms.add_room_brief": "Add Room",
+  "breakout_rooms.select_all": "Select all",
+  "breakout_rooms.unassign_all": "Unassign all",
+  "breakout_rooms.assign": "Assign",
+  "breakout_rooms.assign_participants": "Assign Participants",
+  "breakout_rooms.none_assigned": "No participants assigned yet",
+  "breakout_rooms.drag_drop_participants": "Drag and drop participants",
+  "breakout_rooms.click_drop_participants": "Click here to assign",
+  "breakout_rooms.status.assign_multiple": "Assign multiple participants at once by clicking and selecting them",
+  "breakout_rooms.status.select_room": "Select a room to assign",
+  "breakout_rooms.ephemeral_status.participants_assigned": "Participants assigned",
+  "breakout_rooms.ephemeral_status.participants_assigned_randomly": "Participants assigned randomly",
+  "breakout_rooms.ephemeral_status.changes_discarded": "Changes discarded",
+  "breakout_rooms.confirm_modal.start_breakout.header": "Start breakout rooms?",
+  "breakout_rooms.confirm_modal.start_breakout.content": "Once started, all participants will be moved to their assigned rooms.",
+  "breakout_rooms.confirm_modal.start_breakout.cancelText": "No, go back",
+  "breakout_rooms.confirm_modal.start_breakout.ctaText": "Yes, start",
+  "breakout_rooms.confirm_modal.close_breakout.header": "Close breakout rooms?",
+  "breakout_rooms.confirm_modal.close_breakout.content": "All breakout rooms will be closed & participants will be moved back to the main room.",
+  "breakout_rooms.confirm_modal.close_breakout.ctaText": "Yes, close breakout",
+  "breakout_rooms.move_reason.started_msg": "Starting breakout rooms...",
+  "breakout_rooms.move_reason.started_desc": "You are being moved to your assigned room",
+  "breakout_rooms.move_reason.closed_msg": "Closing Breakout rooms...",
+  "breakout_rooms.move_reason.closed_desc": "You are being moved back to the main room",
+  "breakout_rooms.move_reason.switch_room": "Joining Breakout Room...",
+  "breakout_rooms.move_reason.switch_main_room": "Joining Main Room...",
+  "breakout_rooms.all_assigned": "All participants have been assigned",
+  "breakout_rooms.empty_main_room": "No more participants in the main room.",
+  "breakout_rooms.leave_confirmation": "Are you sure you want to leave the call? You are in a breakout room, you can join the main room too.",
+  "breakout_rooms.leave_confirmation.main_room_btn": "Go back to main room",
+  "ai": "AI",
+  "ai.meeting_ai": "MeetingAI",
+  "ai.home": "Home",
+  "ai.transcriptions": "Transcriptions",
+  "ai.personal": "Personal",
+  "ai.caption_view": "Caption View",
+  "ai.chat.tooltip": "This conversation will just be visible to you and not to others in the call.",
+  "ai.chat.summarise": "Hey AI, summarise this call",
+  "ai.chat.agenda": "Hey AI, what is today's agenda?",
+  "search": "Search",
+  "search.could_not_find": "Couldn't find a participant with the specified name or ID.",
+  "search.empty": "It looks like nobody is here.",
+  "end": "End Meeting",
+  "end.all": "End meeting for all",
+  "ended": "The meeting ended.",
+  "ended.rejected": "Your request to join the meeting was denied.",
+  "ended.left": "You left the meeting.",
+  "ended.kicked": "You were removed from the meeting.",
+  "ended.disconnected": "The call ended because the connection was lost.",
+  "ended.network": "Please check your internet connection and try again.",
+  "ended.unauthorized": "You are not authorized to join this meeting.",
+  "network": "Network",
+  "network.reconnecting": "Connection lost. Trying to reconnect.",
+  "network.delay_extended": "Taking too long to reconnect. Please check your network connection.",
+  "network.disconnected": "Could not reconnect. Please leave the meeting and try refreshing the window.",
+  "network.leaving": "Automatically leaving the meeting in 10 seconds.",
+  "network.restored": "Connection restored",
+  "network.delay": "Taking too long to reconnect.",
+  "network.lost": "Connection lost",
+  "network.lost_extended": "Connection lost. Please check your network connection.",
+  "livestream": "Livestream",
+  "livestream.indicator": "This meeting is being livestreamed.",
+  "livestream.skip": "Skip to Live",
+  "livestream.idle": "Waiting to go live.",
+  "livestream.starting": "Livestream is starting...",
+  "livestream.stopping": "Livestream is stopping...",
+  "livestream.waiting_on_manual_ingestion": "Please ingest livestream media.",
+  "livestream.error.not_supported": "Player not supported.",
+  "livestream.error.not_found": "Playback URL not found.",
+  "livestream.error.unknown": "An unknown error occurred.",
+  "livestream.error.sync": "Could not sync livestream please try again later.",
+  "livestream.error.start": "Error while starting livestream.",
+  "livestream.error.stop": "Error while stopping livestream.",
+  "livestream.go_live": "Go Live",
+  "livestream.end_live": "End Live",
+  "livestream.error": "Error",
+  "cta.help": "Need help on how to do this?",
+  "cta.continue": "Ignore",
+  "cta.reload": "Reload",
+  "cta.confirmation": "Are you sure?",
+  "cta.system_settings": "Open Settings",
+  "remote_access.empty": "There are no remote requests, yet.",
+  "remote_access.requests": "The following people have requested remote control to your screen share.",
+  "remote_access.allow": "Please select whom you want to give access to.",
+  "remote_access.grant": "Grant access",
+  "remote_access.indicator": "Any plugin or screenshare you switch to will sync the change across the meeting",
+  "chat": "Chat",
+  "chat.new": "New",
+  "chat.max_limit_warning": "Max Character Limit",
+  "chat.rate_limit_error": "Please wait before you can send another message",
+  "chat.new_channel": "Create new channel",
+  "chat.channel_name": "Enter channel name",
+  "chat.member_name": "Enter member name",
+  "chat.add_members": "Add members",
+  "chat.delete_msg": "Delete",
+  "chat.edit_msg": "Edit",
+  "chat.send_msg": "Send message",
+  "chat.send_attachment": "Drop files/images to send",
+  "chat.send_img": "Send an image",
+  "chat.send_file": "Send a file",
+  "chat.send_emoji": "Send an emoji",
+  "chat.update_msg": "Update message",
+  "chat.channel_members": "Channel Members",
+  "chat.img.loading": "Loading image",
+  "chat.error.img_not_found": "Image not found",
+  "chat.error.empty_results": "Couldn't find a member with the specified name.",
+  "chat.img.shared_by": "Shared by",
+  "chat.reply": "Reply",
+  "chat.message_placeholder": "Message..",
+  "chat.click_to_send": "Click to send as message",
+  "chat.search_msgs": "Search messages",
+  "chat.search_conversations": "Search conversations",
+  "chat.start_conversation": "Start a conversation..",
+  "chat.empty_search": "No messages found",
+  "chat.empty_channel": "Send a message to get started",
+  "chat.cancel_upload": "Cancel upload",
+  "chat.view_chats": "View chats",
+  "chat.everyone": "everyone",
+  "chat.pinned_msgs": "Pinned messages",
+  "chat.toggle_pinned_msgs": "Toggle pinned messages",
+  "date.today": "Today",
+  "date.yesterday": "Yesterday",
+  "date.sunday": "Sunday",
+  "date.monday": "Monday",
+  "date.tuesday": "Tuesday",
+  "date.wednesday": "Wednesday",
+  "date.thursday": "Thursday",
+  "date.friday": "Friday",
+  "date.saturday": "Saturday",
+  "list.empty": "No items found",
+  "grid.listening": "Listening",
+  "transcript.off": "Turn off Transcripts",
+  "transcript.on": "Turn on Transcripts",
+  "settings.notification_sound": "Notification sound",
+  "settings.microphone_input": "Microphone",
+  "settings.speaker_output": "Speaker",
+  "settings.mirror_video": "Mirror my Video",
+  "settings.camera_off": "Camera is off",
+  "dialog.close": "Close dialog",
+  "notifications.joined": "just joined",
+  "notifications.left": "left",
+  "notifications.requesting_to_join_meeting": "is requesting to join the meeting",
+  "notifications.requested_to_join_stage": "has requested to join stage",
+  "notifications.joined_stage": "has joined stage",
+  "notifications.request_to_join_accepted": "Request to join accepted",
+  "notifications.request_to_join_rejected": "Request to join rejected",
+  "notifications.accept": "Accept",
+  "notifications.new_poll_created_by": "New poll created by",
+  "notifications.connected_to": "Connected to",
+  "notifications.plugin_switched_to": "Plugin switched to",
+  "notifications.remote_control_requested": "has requested for remote control",
+  "notifications.remote_control_request_sent": "Sent remote control request to",
+  "notifications.remote_control_request_accepted": "has granted remote control",
+  "notifications.remote_control_granted": "Granted remote control to",
+  "notifications.remote_control_terminated": "Existing remote control has been terminated",
+  "debugger.troubleshooting.label": "Troubleshooting",
+  "debugger.quality.good": "Good",
+  "debugger.quality.average": "Average",
+  "debugger.quality.poor": "Poor",
+  "debugger.stats.bitrate.label": "Bitrate",
+  "debugger.stats.bitrate.description": "Data transmitted per second, affects quality and file size.",
+  "debugger.stats.packet_loss.label": "Packet Loss",
+  "debugger.stats.packet_loss.description": "Amount of data lost during transfer",
+  "debugger.stats.jitter.label": "Jitter",
+  "debugger.stats.jitter.description": "Variance or fluctuation in latency",
+  "debugger.stats.cpu_limitations.label": "CPU Limitations",
+  "debugger.stats.cpu_limitations.description": "CPU limitations can impact WebRTC call quality and performance.",
+  "debugger.stats.bandwidth_limitations.label": "Bandwidth Limitations",
+  "debugger.stats.bandwidth_limitations.description": "Slow internet speeds can degrade video quality.",
+  "debugger.audio.label": "Audio",
+  "debugger.audio.troubleshooting.label": "Audio Troubleshooting",
+  "debugger.audio.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.audio.messages.enable_media": "Please enable mic to see the report.",
+  "debugger.audio.sections.network_media": "Network & Media",
+  "debugger.video.label": "Video",
+  "debugger.video.troubleshooting.label": "Video Troubleshooting",
+  "debugger.video.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.video.messages.enable_media": "Please enable camera to see the report.",
+  "debugger.video.sections.network_media": "Network & Media",
+  "debugger.screenshare.label": "Screenshare",
+  "debugger.screenshare.troubleshooting.label": "Screenshare Troubleshooting",
+  "debugger.screenshare.sections.network_media": "Network & Media",
+  "debugger.screenshare.messages.generating_report": "Generating report. Please wait for a few seconds.",
+  "debugger.screenshare.messages.enable_media": "Please share screen to see the report.",
+  "debugger.system.label": "System",
+  "debugger.system.troubleshooting.label": "System Troubleshooting",
+  "debugger.system.sections.battery": "Battery",
+  "debugger.system.battery.level.label": "Battery Level",
+  "debugger.system.battery.level.description": "A low battery charge may result in reduced performance.",
+  "debugger.system.battery.charging.label": "Battery Charging Status",
+  "debugger.system.battery.charging.description": "A device running on power performs optimally.",
+  "debugger.system.battery.charging.is_charging": "Charging",
+  "debugger.system.battery.charging.is_not_charging": "Not charging"
 }
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/reference-architecture/description-of-design-guides.mdx b/src/content/partials/reference-architecture/description-of-design-guides.mdx
index cedea82e2560037..ebf33568632639f 100644
--- a/src/content/partials/reference-architecture/description-of-design-guides.mdx
+++ b/src/content/partials/reference-architecture/description-of-design-guides.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Design guides take your knowledge from a reference architecture and walk through the conceptual decisions and directions you should take to implement a specific solution. They do not replace our product documentation, but instead provide guidance on the decisions you should make given a certain solution you are trying to deploy.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
index 8756e82c2b9cbe2..6a2206f3b86ff23 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architecture-diagrams.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
index 8756e82c2b9cbe2..6a2206f3b86ff23 100644
--- a/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
+++ b/src/content/partials/reference-architecture/description-of-ref-architectures.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Reference architecture documents and diagrams are designed to provide a foundational knowledge of the Cloudflare platform and products. Building on the information in these documents, you can architect software solutions based on your specific context and needs.
diff --git a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
index 24ca75fa6ed1a30..a5d6d6bb9b81e53 100644
--- a/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
+++ b/src/content/partials/reference-architecture/what-is-cloudflare-link.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-- What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
+* What is Cloudflare? | [Website](https://www.cloudflare.com/what-is-cloudflare/) (5 minute read) or [video](https://youtu.be/XHvmX3FhTwU?feature=shared) (2 minutes)
diff --git a/src/content/partials/registrar/email-verification.mdx b/src/content/partials/registrar/email-verification.mdx
index 2b72b0b433a4f42..4dd91c56e47bc07 100644
--- a/src/content/partials/registrar/email-verification.mdx
+++ b/src/content/partials/registrar/email-verification.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 If you have an [unverified account email address](/fundamentals/user-profiles/verify-email-address/), you will not be able to transfer or register domains. Verify your account email address before proceeding.
 
+
 :::
diff --git a/src/content/partials/registrar/enable-dnssec.mdx b/src/content/partials/registrar/enable-dnssec.mdx
index 83ac4c6b7219453..237935a506b128b 100644
--- a/src/content/partials/registrar/enable-dnssec.mdx
+++ b/src/content/partials/registrar/enable-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ Cloudflare Registrar offers one-click DNSSEC activation for free to all customer
 
 1. In Cloudflare dashboard, go to the **Manage Domains** page.
 
-   <DashButton url="/?to=/:account/registrar/domains" />
+    <DashButton url="/?to=/:account/registrar/domains" />
 
 2. Find the domain that you want to activate DNSSEC and select **Manage**.
 3. Select **Configuration** > **Enable DNSSEC**. If DNSSEC was previously activated, select **Disable DNSSEC** to disable it.
diff --git a/src/content/partials/registrar/icann-unverified-email.mdx b/src/content/partials/registrar/icann-unverified-email.mdx
index 296e965a96cf9c5..665b423fb7c437c 100644
--- a/src/content/partials/registrar/icann-unverified-email.mdx
+++ b/src/content/partials/registrar/icann-unverified-email.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 :::note
 
 If you purchased your domain through Cloudflare Registrar, [ICANN](https://www.icann.org/) requires you to verify your registrant email address. If your email is unverified or if the verification has expired, ICANN places a hold on the domain and replaces your nameservers with parking server nameservers (NS). Once you complete verification, your nameservers are automatically restored.
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/registrar/requirements.mdx b/src/content/partials/registrar/requirements.mdx
index 1178776bde7f938..23d333ecb86aba7 100644
--- a/src/content/partials/registrar/requirements.mdx
+++ b/src/content/partials/registrar/requirements.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Requirements
diff --git a/src/content/partials/registrar/restrictions.mdx b/src/content/partials/registrar/restrictions.mdx
index b34956aeb7039bd..57a9452a3ab5a69 100644
--- a/src/content/partials/registrar/restrictions.mdx
+++ b/src/content/partials/registrar/restrictions.mdx
@@ -1,20 +1,20 @@
 ---
 {}
+
 ---
 
 ## Restrictions
 
 To transfer your domain, it must meet the following requirements:
 
-- ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
-- Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
+* ICANN rules prohibit a domain from being transferred if it has been registered or previously transferred within the last 60 days or if the WHOIS Registrant contact information was modified in the last 60 days (even if redacted).
+* Your account at your current registrar must be active. If your domain has expired, you may be able to transfer the domain. If the domain is in the `RedemptionPeriod` you will likely need to restore the domain first before the transfer can proceed.
   :::caution
 
   The transfer of an expired domain may result in an additional year NOT being added during the transfer.
   :::
-
-- Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
-- Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
-- Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
+* Your domain cannot be an internationalized domain name (IDNs) as Cloudflare does not currently support them. These domains are also known as unicode.
+* Domains that have a status of `serverHold`, `serverTransferProhibited`, `pendingDelete`, `pendingTransfer`, or `RedemptionPeriod` may not be transferred.
+* Domains that have a status of `clientTransferProhibited` (Transfer Lock) will not show as available for transfer. You will have to unlock the domain at your current registrar before being able to proceed.
 
 If your domain is listed as available for transfer in the Cloudflare dashboard, these restrictions have already been checked.
diff --git a/src/content/partials/registrar/verify-dnssec.mdx b/src/content/partials/registrar/verify-dnssec.mdx
index f5182b94b5a1559..cc9f05e4a7120d0 100644
--- a/src/content/partials/registrar/verify-dnssec.mdx
+++ b/src/content/partials/registrar/verify-dnssec.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When DNSSEC has been successfully applied to your domain, Cloudflare shows you a confirmed status. Go to [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) in the Cloudflare dashboard, and scroll down to **DNSSEC**.
diff --git a/src/content/partials/rules/configuration-rule-link-to-examples.mdx b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
index 037eaeef781404b..1ff0517f5389e04 100644
--- a/src/content/partials/rules/configuration-rule-link-to-examples.mdx
+++ b/src/content/partials/rules/configuration-rule-link-to-examples.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Refer to [Create a configuration rule via API](/rules/configuration-rules/create-api/#example-requests) for complete API examples.
diff --git a/src/content/partials/rules/configuration-rule-promotion.mdx b/src/content/partials/rules/configuration-rule-promotion.mdx
index 6519187465e5160..3ae68e3cf154e68 100644
--- a/src/content/partials/rules/configuration-rule-promotion.mdx
+++ b/src/content/partials/rules/configuration-rule-promotion.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 To use this feature on specific hostnames - instead of across your entire zone - use a [configuration rule](/rules/configuration-rules/).
 
+
 :::
diff --git a/src/content/partials/rules/error-pages-list.mdx b/src/content/partials/rules/error-pages-list.mdx
index 7ab22e20464a19f..e3245503608f21c 100644
--- a/src/content/partials/rules/error-pages-list.mdx
+++ b/src/content/partials/rules/error-pages-list.mdx
@@ -11,3 +11,4 @@ import { Details } from "~/components";
 - 1000 class errors
 - Managed challenge / I'm Under Attack Mode
 - Rate limiting block
+
diff --git a/src/content/partials/rules/page-rules-migration.mdx b/src/content/partials/rules/page-rules-migration.mdx
index 88530db810e2ac1..49184a9b7fddd3a 100644
--- a/src/content/partials/rules/page-rules-migration.mdx
+++ b/src/content/partials/rules/page-rules-migration.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/rules/rules-creation-workflow.mdx b/src/content/partials/rules/rules-creation-workflow.mdx
index 457e137376878ed..c5c10393f7fe7b5 100644
--- a/src/content/partials/rules/rules-creation-workflow.mdx
+++ b/src/content/partials/rules/rules-creation-workflow.mdx
@@ -11,6 +11,7 @@ Follow this workflow to create {props.ruleName} for a given zone via API:
 1. Use the [List zone rulesets](/api/resources/rulesets/methods/list/) operation to check if there is already a ruleset for the <code>{props.phaseName}</code> phase at the zone level.
 
 2. If the phase ruleset does not exist, create it using the [Create a zone ruleset](/api/resources/rulesets/methods/create/) operation. In the new ruleset properties, set the following values:
+
    - **kind**: `zone`
    - **phase**: <code>{props.phaseName}</code>
 
diff --git a/src/content/partials/rules/rules-templates.mdx b/src/content/partials/rules/rules-templates.mdx
index 327ddbb7e03e964..15707947ed21c52 100644
--- a/src/content/partials/rules/rules-templates.mdx
+++ b/src/content/partials/rules/rules-templates.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
-Cloudflare provides you with rules templates for common use cases.
+Cloudflare provides you with rules templates for common use cases. 
 
 1. In the Cloudflare dashboard, go to the Rules **Overview** page.
 
    <DashButton url="/?to=/:account/:zone/rules/overview" />
 
-2. Select **Templates**, and then select one of the available templates.
+2. Select **Templates**, and then select one of the available templates. 
 
 You can also refer to the [Examples gallery](/rules/examples/) in the developer docs.
diff --git a/src/content/partials/rules/terraform-additional-resources.mdx b/src/content/partials/rules/terraform-additional-resources.mdx
index 38d3d167a3b1839..d12cb288e5d11d2 100644
--- a/src/content/partials/rules/terraform-additional-resources.mdx
+++ b/src/content/partials/rules/terraform-additional-resources.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 ## Additional resources
 
 For additional guidance on using Terraform with Cloudflare, refer to the following resources:
 
-- [Terraform documentation](/terraform/)
-- [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
+* [Terraform documentation](/terraform/)
+* [Cloudflare Provider for Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) (reference documentation)
diff --git a/src/content/partials/rules/transform/header-valid-names.mdx b/src/content/partials/rules/transform/header-valid-names.mdx
index 0e72fbaa66dee00..f286e2ab339e6cc 100644
--- a/src/content/partials/rules/transform/header-valid-names.mdx
+++ b/src/content/partials/rules/transform/header-valid-names.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
-- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-- The following special characters: `-` and `_`
+* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+* The following special characters: `-` and `_`
diff --git a/src/content/partials/rules/transform/header-valid-values.mdx b/src/content/partials/rules/transform/header-valid-values.mdx
index 9daf4a9a76a4e18..540ff31d7a51c22 100644
--- a/src/content/partials/rules/transform/header-valid-values.mdx
+++ b/src/content/partials/rules/transform/header-valid-values.mdx
@@ -1,6 +1,7 @@
 ---
 {}
+
 ---
 
-- Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
-- The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
+* Alphanumeric characters: `a`-`z`, `A`-`Z`, and `0`-`9`
+* The following special characters: ``_ :;.,\/"'?!(){}[]@<>=-+*#$&`|~^%``
diff --git a/src/content/partials/ruleset-engine/max-expression-length.mdx b/src/content/partials/ruleset-engine/max-expression-length.mdx
index 59d99f613473f9c..e8881c097a0cb0c 100644
--- a/src/content/partials/ruleset-engine/max-expression-length.mdx
+++ b/src/content/partials/ruleset-engine/max-expression-length.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The maximum length of a rule expression is 4,096 characters.
diff --git a/src/content/partials/ruleset-engine/rule-position-values.mdx b/src/content/partials/ruleset-engine/rule-position-values.mdx
index c83ff42bfcf11a3..aed905dee8894cd 100644
--- a/src/content/partials/ruleset-engine/rule-position-values.mdx
+++ b/src/content/partials/ruleset-engine/rule-position-values.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
-- `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
+* `"before": "<RULE_ID>"` — Places the rule before rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the first rule in the ruleset.
 
-- `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
+* `"after": "<RULE_ID>"` — Places the rule after rule `<RULE_ID>`. Use this argument with an empty rule ID value (`""`) to set the rule as the last rule in the ruleset.
 
-- `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
+* `"index": <POSITION_NUMBER>` — Places the rule in the exact position specified by the integer number `<POSITION_NUMBER>`. Position numbers start with `1`. Existing rules in the ruleset from the specified position number onward are shifted one position (no rule is overwritten). For example, when you place a rule in position <var>n</var> using `index`, existing rules with index <var>n</var>, <var>n</var>+1, <var>n</var>+2, and so on, are shifted one position — their new position will be <var>n</var>+1, <var>n</var>+2, <var>n</var>+3, and so forth. If the index is out of range, the method returns a `400` HTTP status code.
 
 :::caution[Important]
 
diff --git a/src/content/partials/security-center/brand-protection-alerts.mdx b/src/content/partials/security-center/brand-protection-alerts.mdx
index 30a6ad5713d7bad..71e7f9d688bd180 100644
--- a/src/content/partials/security-center/brand-protection-alerts.mdx
+++ b/src/content/partials/security-center/brand-protection-alerts.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Brand Protection integrates with Cloudflare's ANS (Alerts Notification Service) to provide configurable alerts when new domains are detected.
diff --git a/src/content/partials/security-center/brand-protection-definition.mdx b/src/content/partials/security-center/brand-protection-definition.mdx
index 6707a12034c0016..be50db0bf8b3b06 100644
--- a/src/content/partials/security-center/brand-protection-definition.mdx
+++ b/src/content/partials/security-center/brand-protection-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Brand Protection allows you to proactively identify and mitigate domain impersonation and phishing attacks. By monitoring newly registered domains and visual assets across the Internet, Cloudflare helps protect your brand's reputation and prevents your customers or employees from submitting sensitive information to fraudulent sites.
@@ -8,4 +9,4 @@ Common threats include:
 
 - [Typosquatting](https://en.wikipedia.org/wiki/Typosquatting): For example, typing `cloudfalre.com` instead of `cloudflare.com`.
 - Concatenation of services (`cloudflare-service.com`) often registered by attackers to trick unsuspecting victims into submitting private information such as passwords.
-- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
+- [Homoglyph attacks](https://en.wikipedia.org/wiki/IDN_homograph_attack) that use lookalike characters to trick unsuspecting victims.
\ No newline at end of file
diff --git a/src/content/partials/security-center/scan-frequency.mdx b/src/content/partials/security-center/scan-frequency.mdx
index d5d4a4b4bfe5c98..78e170a9f3c6a81 100644
--- a/src/content/partials/security-center/scan-frequency.mdx
+++ b/src/content/partials/security-center/scan-frequency.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you enable Security Insights, Cloudflare performs scans automatically. Paying customers (as defined in the table below) are re-scanned daily and can trigger a scan manually:
@@ -7,4 +8,4 @@ Once you enable Security Insights, Cloudflare performs scans automatically. Payi
 | Plan                                      | Scan Frequency | On-Demand |
 | ----------------------------------------- | -------------- | --------- |
 | Accounts on a Free, Pro, or Business plan | Every 7 days   | Yes       |
-| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
+| Accounts on an Enterprise plan            | Every 3 days   | Yes       |
\ No newline at end of file
diff --git a/src/content/partials/security-center/scan-properties.mdx b/src/content/partials/security-center/scan-properties.mdx
index cb96cf4aa2a437c..aa07143a1e7c4f7 100644
--- a/src/content/partials/security-center/scan-properties.mdx
+++ b/src/content/partials/security-center/scan-properties.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-- **Severity**: The security risk of the insight. The severity values are: _Moderate_, _High_, and _Critical_. The higher the severity level, the higher the risk of threat to your environment.
-- **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
-- **Risk**: A description of the risk associated with not addressing the issue.
-- **Type**: The insight category.
+* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment.
+* **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability.
+* **Risk**: A description of the risk associated with not addressing the issue.
+* **Type**: The insight category.
diff --git a/src/content/partials/security-center/security-insights-definition.mdx b/src/content/partials/security-center/security-insights-definition.mdx
index b41a47d43774aa0..caeb5d26174c035 100644
--- a/src/content/partials/security-center/security-insights-definition.mdx
+++ b/src/content/partials/security-center/security-insights-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Security Insights provides you with a list of insights, covering different areas of your Cloudflare environment, such as: Cloudflare account settings, DNS record configurations, SSL/TLS certificates configurations, Cloudflare Access configurations and Cloudflare WAF configurations.
diff --git a/src/content/partials/smart-shield/argo-analytics.mdx b/src/content/partials/smart-shield/argo-analytics.mdx
index de75df8e6e26cee..32f48959a9305a7 100644
--- a/src/content/partials/smart-shield/argo-analytics.mdx
+++ b/src/content/partials/smart-shield/argo-analytics.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
+Analytics collects data based on the time-to-first-byte (TTFB) from your origin to the Cloudflare network. TTFB is the delay between when Cloudflare sends a request to your server and when it receives the first byte in response. Argo Smart Routing optimizes your server's network transit time to minimize this delay.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/argo-intro.mdx b/src/content/partials/smart-shield/argo-intro.mdx
index 32ea358182d40ac..268b8495d8fe135 100644
--- a/src/content/partials/smart-shield/argo-intro.mdx
+++ b/src/content/partials/smart-shield/argo-intro.mdx
@@ -6,5 +6,5 @@ params:
 Argo Smart Routing detects real-time network issues and routes your web traffic across the most efficient network path, avoiding congestion.
 
 { props.conditional === "dedicated-argo-tile" && (
-<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
+	<p>This results in faster loading times, increased reliability, and reduced costs. These benefits are most apparent for users farthest from your origin server.</p>
 )}
diff --git a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
index 3d8aa0a11fe62e8..9fa952b07643f85 100644
--- a/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
+++ b/src/content/partials/smart-shield/concurrent-connections-explainer.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
+Each Dedicated CDN Egress IP can support 40,000 concurrent connections per origin IP port. For example, if you have one dedicated IP and two origins (A and B), this single IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/dcei-pool-requirements.mdx b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
index ac278f7e6a42db8..7cafa55a6d95d3e 100644
--- a/src/content/partials/smart-shield/dcei-pool-requirements.mdx
+++ b/src/content/partials/smart-shield/dcei-pool-requirements.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
+Each dedicated egress pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs. Also, a single BYOIP prefix can be used for either CDN ingress or CDN egress, but not both.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-analytics.mdx b/src/content/partials/smart-shield/health-checks-analytics.mdx
index 6a9a9c84165553c..2983c5deb95bc9f 100644
--- a/src/content/partials/smart-shield/health-checks-analytics.mdx
+++ b/src/content/partials/smart-shield/health-checks-analytics.mdx
@@ -194,4 +194,4 @@ If the failure cannot be classified as any other type of failure mentioned above
 
 #### Solution
 
-Contact [Cloudflare support](/support/contacting-cloudflare-support/).
+Contact [Cloudflare support](/support/contacting-cloudflare-support/).
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-intro.mdx b/src/content/partials/smart-shield/health-checks-intro.mdx
index 5d9ab876a0af7ce..ed843ebdf208147 100644
--- a/src/content/partials/smart-shield/health-checks-intro.mdx
+++ b/src/content/partials/smart-shield/health-checks-intro.mdx
@@ -4,4 +4,4 @@
 
 A health check is a service that runs on Cloudflare's edge network to monitor whether an origin server is online. This allows you to view the health of your origin servers even if there is only one origin or you do not yet need to balance traffic across your infrastructure.
 
-Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
+Health Checks support various configurations to hone in on what you can check, including response codes, protocol types, and intervals. You can specify a particular path if an origin server serves multiple applications or check a larger subset of response codes for your staging environment. All of these options allow you to properly target your Health Check, providing a precise picture of what is wrong with an origin server.
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/health-checks-regions.mdx b/src/content/partials/smart-shield/health-checks-regions.mdx
index 4c0e494eaeec2e9..bbbbdb12d2c0ec9 100644
--- a/src/content/partials/smart-shield/health-checks-regions.mdx
+++ b/src/content/partials/smart-shield/health-checks-regions.mdx
@@ -12,8 +12,8 @@ The Internet is not the same everywhere around the world and your users may not
 
 Analytics are presented at two levels:
 
-- Regional Aggregates: Combined results from the three data centers within a specific region.
-- Global Aggregates: Total results across all configured regions and data centers.
+* Regional Aggregates: Combined results from the three data centers within a specific region.
+* Global Aggregates: Total results across all configured regions and data centers.
 
 In the event log, entries are labeled by region or as **Global**. We do not provide granular data for individual data centers.
 
diff --git a/src/content/partials/smart-shield/smart-shield-callout.mdx b/src/content/partials/smart-shield/smart-shield-callout.mdx
index 706d52242176099..15c3e70be832e5a 100644
--- a/src/content/partials/smart-shield/smart-shield-callout.mdx
+++ b/src/content/partials/smart-shield/smart-shield-callout.mdx
@@ -4,4 +4,4 @@
 
 :::note[Smart Shield]
 This functionality is now offered as part of Cloudflare's origin server safeguard, Smart Shield. [Learn more](/smart-shield/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/smart-shield/zone-lockdown.mdx b/src/content/partials/smart-shield/zone-lockdown.mdx
index 5181bf0878bc7b3..77215453e523f54 100644
--- a/src/content/partials/smart-shield/zone-lockdown.mdx
+++ b/src/content/partials/smart-shield/zone-lockdown.mdx
@@ -18,7 +18,7 @@ To bypass zone lockdown using a WAF custom rule:
 
    To allow a specific Health Check, verify if the user agent contains the first 16 characters of the Health Check ID.
 
-3. Set the action to _Skip_ and the corresponding feature to **Zone Lockdown** under **More components to skip**.
+3. Set the action to *Skip* and the corresponding feature to **Zone Lockdown** under **More components to skip**.
 
 ### Via the API
 
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
index a743f57b374347a..d19bdad602512e2 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-api.mdx
@@ -1,49 +1,50 @@
 ---
 {}
+
 ---
 
-import { APIRequest } from "~/components";
+import { APIRequest } from "~/components"
 
 Below is a curl example and the associated data being posted to the API.
 
 **API example:**
 
 <APIRequest
-	path="/zones/{zone_id}/spectrum/apps"
-	method="POST"
-	json={{
-		dns: {
-			type: "CNAME",
-			name: "spectrum-cname.example.com",
-		},
-		ip_firewall: false,
-		protocol: "tcp/22",
-		proxy_protocol: "off",
-		tls: "off",
-		origin_dns: {
-			name: "cname-to-origin.example.com",
-			ttl: 1200,
-		},
-		origin_port: 22,
-	}}
+  path="/zones/{zone_id}/spectrum/apps"
+  method="POST"
+  json={{
+    dns: {
+      type: "CNAME",
+      name: "spectrum-cname.example.com"
+    },
+    ip_firewall: false,
+    protocol: "tcp/22",
+    proxy_protocol: "off",
+    tls: "off",
+    origin_dns: {
+      name: "cname-to-origin.example.com",
+      ttl: 1200
+    },
+    origin_port: 22
+  }}
 />
 
 **Example data:**
 
 ```json
 {
-	"dns": {
-		"type": "CNAME",
-		"name": "spectrum-cname.example.com"
-	},
-	"ip_firewall": false,
-	"protocol": "tcp/22",
-	"proxy_protocol": "off",
-	"tls": "off",
-	"origin_dns": {
-		"name": "cname-to-origin.example.com",
-		"ttl": 1200
-	},
-	"origin_port": 22
+  "dns": {
+    "type": "CNAME",
+    "name": "spectrum-cname.example.com"
+  },
+  "ip_firewall": false,
+  "protocol": "tcp/22",
+  "proxy_protocol": "off",
+  "tls": "off",
+  "origin_dns": {
+    "name": "cname-to-origin.example.com",
+    "ttl": 1200
+  },
+  "origin_port": 22
 }
 ```
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
index 2e354499765aa68..7bca9b160ea79e7 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { DashButton } from "~/components";
+import { DashButton } from "~/components"
 
 1. In the Cloudflare dashboard, go to the **Spectrum** page.
 
diff --git a/src/content/partials/speed/rocket-loader-csp.mdx b/src/content/partials/speed/rocket-loader-csp.mdx
index 415fe7be153ccd2..5f9b9948eb37a16 100644
--- a/src/content/partials/speed/rocket-loader-csp.mdx
+++ b/src/content/partials/speed/rocket-loader-csp.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip } from "~/components"
 
 If you have a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> in place for your domain, you will need to [update your headers](/fundamentals/reference/policies-compliances/content-security-policies/#product-requirements) to support Rocket Loader.
diff --git a/src/content/partials/speed/user-agents.mdx b/src/content/partials/speed/user-agents.mdx
index f5ce8588ee1bd80..c0837b69232398f 100644
--- a/src/content/partials/speed/user-agents.mdx
+++ b/src/content/partials/speed/user-agents.mdx
@@ -1,17 +1,19 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 For **IPv6** Cloudflare Observatory tests originate from **ASN 15169** or **ASN 132892** and are generated with the following user agents:
 
-- Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
-- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
+* Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
+* Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
 
 For **IPv4** Cloudflare Observatory tests originate from **ASN 396982** and are generated with the following user agents:
 
-- Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
-- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
+* Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0
+* Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0
 
 :::
diff --git a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
index 684249cf2e95c7c..f31818fcb7c6970 100644
--- a/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
+++ b/src/content/partials/ssl/acm-ca-hostnames-conditions.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The available options for **Validation method** and **Certificate Validity Period** may vary depending on the certificate authority you choose and the hostnames that you include in your Advanced certificate order.
diff --git a/src/content/partials/ssl/acm-definition.mdx b/src/content/partials/ssl/acm-definition.mdx
index b7e35411b9f6074..dd03df9af1b9a04 100644
--- a/src/content/partials/ssl/acm-definition.mdx
+++ b/src/content/partials/ssl/acm-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Use advanced certificates when you want something more customizable than [Universal SSL](/ssl/edge-certificates/universal-ssl/) but still want the convenience of SSL certificate issuance and renewal.
diff --git a/src/content/partials/ssl/acm-validate-cert.mdx b/src/content/partials/ssl/acm-validate-cert.mdx
index 9927c34e5e8158d..28d8bc6f0d5532f 100644
--- a/src/content/partials/ssl/acm-validate-cert.mdx
+++ b/src/content/partials/ssl/acm-validate-cert.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 To check whether your certificates have been validated and reissued:
 
-- **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
-- **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
+* **Dashboard**: Find the certificate(s) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page and make sure that the **Status** is **Active**.
+* **API**: Send a [`GET`](/api/resources/ssl/subresources/certificate_packs/methods/list/) request and confirm that your certificate(s) have `"status": "active"`.
diff --git a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
index dff294bdc66047e..1d472785e89e8e2 100644
--- a/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
+++ b/src/content/partials/ssl/aop-per-hostname-upload-cert.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```bash
@@ -23,4 +24,4 @@ curl --silent \
 --header "X-Auth-Email: $MYAUTHEMAIL" \
 --header "X-Auth-Key: $MYAUTHKEY" \
 --data "$request_body"
-```
+```
\ No newline at end of file
diff --git a/src/content/partials/ssl/caa-records-added-by-cf.mdx b/src/content/partials/ssl/caa-records-added-by-cf.mdx
index 5ff6ca31c6bf4b5..1a4489c3befb910 100644
--- a/src/content/partials/ssl/caa-records-added-by-cf.mdx
+++ b/src/content/partials/ssl/caa-records-added-by-cf.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare adds CAA records automatically in the following situations:
@@ -10,7 +11,7 @@ Cloudflare adds CAA records automatically in the following situations:
 These records make sure Cloudflare can still issue Universal certificates on your behalf.
 
 :::note[Subdomain zones caveat]
-CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) - with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
+CAA records are inherited. This means that, if you are using a [subdomain setup](/dns/zone-setups/subdomain-setup/) -  with `subdomain.example.com` on Cloudflare but `example.com` on a different DNS provider -, you should make sure that the parent domain (`example.com`) either has CAA records that allow [Cloudflare's partner CAs](/ssl/reference/certificate-authorities/), or has no CAA records at all.
 :::
 
 If Cloudflare has automatically added CAA records on your behalf, these records will not appear in the Cloudflare dashboard. However, if you run a command line query using `dig`, you can see any existing CAA records, including those added by Cloudflare (replacing `example.com` with your own domain on Cloudflare):
diff --git a/src/content/partials/ssl/caa-records-definition.mdx b/src/content/partials/ssl/caa-records-definition.mdx
index fd0343ee0ae9acb..0154a3d0a0fc6b4 100644
--- a/src/content/partials/ssl/caa-records-definition.mdx
+++ b/src/content/partials/ssl/caa-records-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A Certificate Authority Authorization (CAA) DNS record specifies which certificate authorities (CAs) are allowed to issue certificates for a domain. This record reduces the chance of unauthorized certificate issuance and promotes standardization across your organization.
diff --git a/src/content/partials/ssl/change-encryption-mode-api.mdx b/src/content/partials/ssl/change-encryption-mode-api.mdx
index c9c759459aa123f..56ae28c0a1ced82 100644
--- a/src/content/partials/ssl/change-encryption-mode-api.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To adjust your encryption mode with the API, send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `ssl` as the setting name in the URI path, and the `value` parameter set to your desired setting (`off`, `flexible`, `full`, `strict`, or `origin_pull`).
diff --git a/src/content/partials/ssl/change-encryption-mode-dash.mdx b/src/content/partials/ssl/change-encryption-mode-dash.mdx
index a831eabba8bed79..e7e6afa2c5c9740 100644
--- a/src/content/partials/ssl/change-encryption-mode-dash.mdx
+++ b/src/content/partials/ssl/change-encryption-mode-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/cipher-suites-api-linkout.mdx b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
index 630e79915c01b64..ceda6f3443c4a1f 100644
--- a/src/content/partials/ssl/cipher-suites-api-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-api-linkout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
+If you are customizing cipher suites via API, refer to [Steps and API examples](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api/#steps-and-api-examples) for a snippet you can copy with the formatted array.
\ No newline at end of file
diff --git a/src/content/partials/ssl/cipher-suites-definition.mdx b/src/content/partials/ssl/cipher-suites-definition.mdx
index 659728684c4e279..eea7fc621379f4f 100644
--- a/src/content/partials/ssl/cipher-suites-definition.mdx
+++ b/src/content/partials/ssl/cipher-suites-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cipher suites are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/) (and therefore separate from the [SSL/TLS protocol](/ssl/reference/protocols/)).
diff --git a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
index 308d5f6b820a7d9..8d202297dd8d513 100644
--- a/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
+++ b/src/content/partials/ssl/cipher-suites-saas-linkout.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
+For guidance around custom hostnames, refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites).
\ No newline at end of file
diff --git a/src/content/partials/ssl/ciphers-api-general-notes.mdx b/src/content/partials/ssl/ciphers-api-general-notes.mdx
index 3461784c3991163..431555f3a04bc82 100644
--- a/src/content/partials/ssl/ciphers-api-general-notes.mdx
+++ b/src/content/partials/ssl/ciphers-api-general-notes.mdx
@@ -1,7 +1,7 @@
 ---
 {}
----
 
+---
 To configure cipher suites per hostname, replace the first two lines by the following:
 
 ```bash
diff --git a/src/content/partials/ssl/cname-cert-verification.mdx b/src/content/partials/ssl/cname-cert-verification.mdx
index 1af431ba8e62f82..6803cb1241595a9 100644
--- a/src/content/partials/ssl/cname-cert-verification.mdx
+++ b/src/content/partials/ssl/cname-cert-verification.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare contacts one of our certificate authority (CA) providers and asks them to issue certificates for the specified hostname. The CA will then inform Cloudflare that we need to demonstrate control of this hostname by returning a `$DCV_TOKEN` at a specified `$DCV_FILENAME`; both the token and the filename are randomly generated by the CA and not known to Cloudflare ahead of time.
diff --git a/src/content/partials/ssl/csr-definition.mdx b/src/content/partials/ssl/csr-definition.mdx
index a77784b8eeb8a0f..c3f8ebb7fdbce8c 100644
--- a/src/content/partials/ssl/csr-definition.mdx
+++ b/src/content/partials/ssl/csr-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Generate a Certificate Signing Request (CSR) to get a custom certificate from the Certificate Authority (CA) of your choice while maintaining control of the private key on Cloudflare. The private key associated with the CSR will be generated by Cloudflare and will never leave our network.
diff --git a/src/content/partials/ssl/custom-cert-ciphers.mdx b/src/content/partials/ssl/custom-cert-ciphers.mdx
index bba82764fc568eb..3f3a5f7954778d6 100644
--- a/src/content/partials/ssl/custom-cert-ciphers.mdx
+++ b/src/content/partials/ssl/custom-cert-ciphers.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before deploying custom certificates to Cloudflare's global network, Cloudflare automatically groups the certificates into certificate packs.
@@ -8,6 +9,6 @@ A certificate pack is a group of certificates that share the same set of hostnam
 
 Each pack can include up to three certificates, one from each of the following signature algorithms:
 
-- `SHA-2/RSA`
-- `SHA-2/ECDSA`
-- `SHA-1/RSA`
+* `SHA-2/RSA`
+* `SHA-2/ECDSA`
+* `SHA-1/RSA`
diff --git a/src/content/partials/ssl/custom-cert-openssl-commands.mdx b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
index 7bcbf7ba02b6ffc..547be3cbf37680a 100644
--- a/src/content/partials/ssl/custom-cert-openssl-commands.mdx
+++ b/src/content/partials/ssl/custom-cert-openssl-commands.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 1. Run the following command to generate a 4096-bit RSA private key, using AES-256 encryption. Enter a passphrase when prompted.
diff --git a/src/content/partials/ssl/custom-certificates-definition.mdx b/src/content/partials/ssl/custom-certificates-definition.mdx
index 8b65b18a079f395..64d10e717e0b1ed 100644
--- a/src/content/partials/ssl/custom-certificates-definition.mdx
+++ b/src/content/partials/ssl/custom-certificates-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom certificates are meant for Business and Enterprise customers who want to use their own SSL certificates.
diff --git a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
index fd1a1fad0352eb7..7cf70fd8b8e6960 100644
--- a/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
+++ b/src/content/partials/ssl/custom-origin-trust-store-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Custom Origin Trust Store allows you to upload certificate authorities (CAs) that Cloudflare will use to authenticate connections to your origin server. Use this feature to override the default trust store with your preferred CA or CAs.
diff --git a/src/content/partials/ssl/dcv-certificate-renewal.mdx b/src/content/partials/ssl/dcv-certificate-renewal.mdx
index 77fff64fa5de773..966d6f3d11cb207 100644
--- a/src/content/partials/ssl/dcv-certificate-renewal.mdx
+++ b/src/content/partials/ssl/dcv-certificate-renewal.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
 Even if you manually handle DCV when issuing certificates in a [partial DNS setup](/dns/zone-setups/partial-setup/), at certificate renewal, Cloudflare will attempt to automatically perform DCV via HTTP.
 
 If all of the following conditions are confirmed at the first attempt, the renewal happens automatically via [HTTP](/ssl/edge-certificates/changing-dcv-method/methods/http/).
 
-- Hostnames are proxied.
-- Hostnames on the certificate resolve to the IPs assigned to the zone.
-- The certificate does not contain wildcards.
+* Hostnames are proxied.
+* Hostnames on the certificate resolve to the IPs assigned to the zone.
+* The certificate does not contain wildcards.
 
 :::note
 To automatically renew certificates that do not meet the referred criteria, consider using [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/).
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/dcv-conflicting-records.mdx b/src/content/partials/ssl/dcv-conflicting-records.mdx
index e932ebc41dd7175..c6a89d7d1f55c86 100644
--- a/src/content/partials/ssl/dcv-conflicting-records.mdx
+++ b/src/content/partials/ssl/dcv-conflicting-records.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Remove previous TXT records]
@@ -10,4 +11,4 @@ Existing TXT records for `_acme-challenge` will conflict with the delegated DCV
 _acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
 ```
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/dcv-definition.mdx b/src/content/partials/ssl/dcv-definition.mdx
index c5748e6902bfec1..88a6cd79a67b650 100644
--- a/src/content/partials/ssl/dcv-definition.mdx
+++ b/src/content/partials/ssl/dcv-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before a certificate authority (CA) will issue a certificate for a domain, the requester must prove they have control over that domain. This process is known as domain control validation (DCV).
diff --git a/src/content/partials/ssl/dcv-invalid-token-situations.mdx b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
index 785d89543fd4097..d705eaac712405c 100644
--- a/src/content/partials/ssl/dcv-invalid-token-situations.mdx
+++ b/src/content/partials/ssl/dcv-invalid-token-situations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Tokens may also become invalid upon validation failure. For more details, refer to [Domain control validation flow](/ssl/edge-certificates/changing-dcv-method/dcv-flow/#dcv-tokens).
diff --git a/src/content/partials/ssl/dcv-path-security.mdx b/src/content/partials/ssl/dcv-path-security.mdx
index eb4a9601201193b..5501d6eb5a3f734 100644
--- a/src/content/partials/ssl/dcv-path-security.mdx
+++ b/src/content/partials/ssl/dcv-path-security.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 When your certificate is in `pending_validation` and valid tokens are in place, some security features targeting your zone's path for `/.well-known/*` can be automatically bypassed.
diff --git a/src/content/partials/ssl/dcv-renewal-fallback.mdx b/src/content/partials/ssl/dcv-renewal-fallback.mdx
index 662ad6b134f61e1..fd0e39d48edac6e 100644
--- a/src/content/partials/ssl/dcv-renewal-fallback.mdx
+++ b/src/content/partials/ssl/dcv-renewal-fallback.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If any one of the conditions is not met, the certificate renewal falls back to your chosen method and you will need to [repeat the DCV process](/ssl/edge-certificates/changing-dcv-method/methods/txt/#get-dcv-values) manually.
diff --git a/src/content/partials/ssl/dcv-validate-patch.mdx b/src/content/partials/ssl/dcv-validate-patch.mdx
index 173f9e888cce376..26c6cda69d9927a 100644
--- a/src/content/partials/ssl/dcv-validate-patch.mdx
+++ b/src/content/partials/ssl/dcv-validate-patch.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To request an immediate recheck, send another [PATCH request](/api/resources/ssl/subresources/verification/methods/edit/) with the same `validation_method` as your current validation method.
diff --git a/src/content/partials/ssl/encryption-mode-definition.mdx b/src/content/partials/ssl/encryption-mode-definition.mdx
index 22d2c160d68d3b2..145f8a9e7617a8f 100644
--- a/src/content/partials/ssl/encryption-mode-definition.mdx
+++ b/src/content/partials/ssl/encryption-mode-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Your zone's **SSL/TLS Encryption Mode** controls how Cloudflare manages two connections: one between your visitors and Cloudflare, and the other between Cloudflare and your origin server.
diff --git a/src/content/partials/ssl/enforce-https-recommendation.mdx b/src/content/partials/ssl/enforce-https-recommendation.mdx
index 3bedac422468cc2..9c7faf843ba079a 100644
--- a/src/content/partials/ssl/enforce-https-recommendation.mdx
+++ b/src/content/partials/ssl/enforce-https-recommendation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Even if your application has an active edge certificate, visitors can still access resources over unsecured HTTP connections.
diff --git a/src/content/partials/ssl/error-rate-limiting.mdx b/src/content/partials/ssl/error-rate-limiting.mdx
index 239593e80b8d7b9..ba85796a11af004 100644
--- a/src/content/partials/ssl/error-rate-limiting.mdx
+++ b/src/content/partials/ssl/error-rate-limiting.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 As mentioned in [Certificate authorities](/ssl/reference/certificate-authorities/), specific CAs may have their own limitations. If you use Let’s Encrypt and receive the error below, it means you hit the [duplicate certificate limit](https://letsencrypt.org/docs/duplicate-certificate-limit/) imposed by Let's Encrypt.
diff --git a/src/content/partials/ssl/generic-validation-process.mdx b/src/content/partials/ssl/generic-validation-process.mdx
index e67dc0bfa07e1cb..0b3edf72e02fea2 100644
--- a/src/content/partials/ssl/generic-validation-process.mdx
+++ b/src/content/partials/ssl/generic-validation-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/geokey-manager-v1.mdx b/src/content/partials/ssl/geokey-manager-v1.mdx
index c2a97612cff66a7..38388aa647932b8 100644
--- a/src/content/partials/ssl/geokey-manager-v1.mdx
+++ b/src/content/partials/ssl/geokey-manager-v1.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 The first version of Geo Key Manager supports 3 regions: U.S., E.U., and a set of High Security Data Centers. If you would like to restrict your private key to another country or region, [apply for the closed beta](https://www.cloudflare.com/lp/geo-key-manager/) of the new version.
diff --git a/src/content/partials/ssl/get-started-additional-features.mdx b/src/content/partials/ssl/get-started-additional-features.mdx
index e975392ac50b3c9..9e7f8fdb53fbfc6 100644
--- a/src/content/partials/ssl/get-started-additional-features.mdx
+++ b/src/content/partials/ssl/get-started-additional-features.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 After you have chosen your encryption mode and enforced HTTPS connections, evaluate the following settings:
 
-- [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
-- [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
-- [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
+* [Edge certificates](/ssl/edge-certificates/additional-options/): Customize different aspects of your edge certificates, from enabling **Opportunistic Encryption** to specifying a **Minimum TLS Version**.
+* [Authenticated origin pull](/ssl/origin-configuration/authenticated-origin-pull/): Ensure all requests to your origin server originate from the Cloudflare network.
+* [Notifications](/notifications/notification-available/): Set up alerts related to certificate validation status, issuance, renewal, and expiration.
diff --git a/src/content/partials/ssl/http-cname-validation-process.mdx b/src/content/partials/ssl/http-cname-validation-process.mdx
index 33d5cd00e2c0499..f5e56eee7eb0688 100644
--- a/src/content/partials/ssl/http-cname-validation-process.mdx
+++ b/src/content/partials/ssl/http-cname-validation-process.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If you want to use a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/), you will need to edit the `validation_method` [via the API](/api/resources/ssl/subresources/verification/methods/edit/) and specify your chosen validation method.
diff --git a/src/content/partials/ssl/http-to-txt-schedule.mdx b/src/content/partials/ssl/http-to-txt-schedule.mdx
index 94368fb7c494aae..7081625d6110114 100644
--- a/src/content/partials/ssl/http-to-txt-schedule.mdx
+++ b/src/content/partials/ssl/http-to-txt-schedule.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 - 90-days certificates: after failing for 15 days
 - 30-days certificates: after failing for 7 days
-- 14-days certificates: after failing for 3 days
+- 14-days certificates: after failing for 3 days
\ No newline at end of file
diff --git a/src/content/partials/ssl/keyless-ssl-definition.mdx b/src/content/partials/ssl/keyless-ssl-definition.mdx
index 7199cc1bbca9e0a..12b1d3ad53d80e7 100644
--- a/src/content/partials/ssl/keyless-ssl-definition.mdx
+++ b/src/content/partials/ssl/keyless-ssl-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Keyless SSL allows security-conscious clients to upload their own custom certificates and benefit from Cloudflare, but without exposing their TLS private keys.
diff --git a/src/content/partials/ssl/keyless-tunnel-setup.mdx b/src/content/partials/ssl/keyless-tunnel-setup.mdx
index fc296217a5ba2fd..ff09dc073729618 100644
--- a/src/content/partials/ssl/keyless-tunnel-setup.mdx
+++ b/src/content/partials/ssl/keyless-tunnel-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 This process differs depending on whether you are using the [command line](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/create-local-tunnel/) or the [Cloudflare dashboard](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/).
diff --git a/src/content/partials/ssl/keyless-upload-preamble.mdx b/src/content/partials/ssl/keyless-upload-preamble.mdx
index ae8cfa436a5f20f..1c57296ce980ad0 100644
--- a/src/content/partials/ssl/keyless-upload-preamble.mdx
+++ b/src/content/partials/ssl/keyless-upload-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Before your key servers can be configured, you must next upload the corresponding SSL certificates to Cloudflare’s edge. During TLS termination, Cloudflare will present these certificates to connecting browsers and then (for non-resumed sessions) communicate with the specified key server to complete the handshake.
diff --git a/src/content/partials/ssl/origin-ca-pause-error.mdx b/src/content/partials/ssl/origin-ca-pause-error.mdx
index 282af35186d78e9..a3d2919fcdfbca3 100644
--- a/src/content/partials/ssl/origin-ca-pause-error.mdx
+++ b/src/content/partials/ssl/origin-ca-pause-error.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
 
-Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
+Site visitors may see untrusted certificate errors if you [pause Cloudflare](/fundamentals/manage-domains/pause-cloudflare/) or <GlossaryTooltip term="proxy status">disable proxying</GlossaryTooltip> on subdomains that use Cloudflare origin CA certificates. These certificates only encrypt traffic between Cloudflare and your origin server, not traffic from client browsers to your origin.
\ No newline at end of file
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
index ee3c0a0ba7c5962..5ce503fae04a18f 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-nonwildcard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { GlossaryTooltip } from "~/components";
@@ -10,9 +11,10 @@ This applies to customers using [Universal](/ssl/edge-certificates/universal-ssl
 
 If one of the hostnames on the certificate is not proxying traffic through Cloudflare, certificate issuance and renewal will vary based on the type of certificate you are using:
 
-- **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
-- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+* **Universal**: Perform DCV using one of the available [methods](/ssl/edge-certificates/changing-dcv-method/methods/).
+* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+
 
 :::tip
 If all hostnames are proxied and non-wildcard but you are using [TXT](/ssl/edge-certificates/changing-dcv-method/methods/txt/) as DCV method for advanced certificates, also consider [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) to simplify the process.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
index 59e04d484d2bc13..c506b1aaf0cbe6b 100644
--- a/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
+++ b/src/content/partials/ssl/partial-zone-acm-dcv-wildcard.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 For wildcard hostname certificates, certificate issuance and renewal varies based on the type of certificate you are using:
 
-- **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
-- **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
+* **Universal**: Perform DCV using [TXT validation method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
+* **Advanced**: In most cases, you can opt for [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/), which greatly simplifies certificate management.
 
 If you cannot use Delegated DCV, you need to use [TXT based DCV](/ssl/edge-certificates/changing-dcv-method/methods/txt/) for certificate issuance and renewal. This means you will need to place one TXT DCV token for every hostname on the certificate. If one or more of the hostnames on the certificate fails to validate, the certificate will not be issued or renewed.
 
diff --git a/src/content/partials/ssl/ssl-mode-errors.mdx b/src/content/partials/ssl/ssl-mode-errors.mdx
index 2182e11414cdb4f..6c4766d72ecd2c2 100644
--- a/src/content/partials/ssl/ssl-mode-errors.mdx
+++ b/src/content/partials/ssl/ssl-mode-errors.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Depending on your origin configuration, you may have to adjust settings to avoid [Mixed Content errors](/ssl/troubleshooting/mixed-content-errors/) or [redirect loops](/ssl/troubleshooting/too-many-redirects/).
diff --git a/src/content/partials/ssl/ssl-mode-no-aop.mdx b/src/content/partials/ssl/ssl-mode-no-aop.mdx
index de73f0f75904e95..4818962513eef71 100644
--- a/src/content/partials/ssl/ssl-mode-no-aop.mdx
+++ b/src/content/partials/ssl/ssl-mode-no-aop.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Authenticated Origin Pull](/ssl/origin-configuration/authenticated-origin-pull/) does not work when your [**SSL/TLS encryption mode**](/ssl/origin-configuration/ssl-modes/) is set to **Off** or **Flexible**.
diff --git a/src/content/partials/ssl/ssl-recommender-post-setup.mdx b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
index c20c95e8c8d9494..f742c710a2e813c 100644
--- a/src/content/partials/ssl/ssl-recommender-post-setup.mdx
+++ b/src/content/partials/ssl/ssl-recommender-post-setup.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 Once enabled, the SSL/TLS Recommender runs an origin scan using the user agent `Cloudflare-SSLDetector` and ignores your `robots.txt` file (except for rules explicitly targeting the user agent).
 
 Based on this initial scan, the Recommender may decide that you could use a stronger [SSL encryption mode](/ssl/origin-configuration/ssl-modes/). It will never recommend a weaker option than what is currently configured.
 
-If so, it will send the application owner an email with the recommended option and add a _Recommended by Cloudflare_ tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
+If so, it will send the application owner an email with the recommended option and add a *Recommended by Cloudflare* tag to that option on the **SSL/TLS** page. You are not required to use this recommendation.
 
 If you do not receive an email, keep your current **SSL encryption mode**.
diff --git a/src/content/partials/ssl/ssl-recommender-prereqs.mdx b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
index 54a2fb9f09c8532..5a469237108799e 100644
--- a/src/content/partials/ssl/ssl-recommender-prereqs.mdx
+++ b/src/content/partials/ssl/ssl-recommender-prereqs.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 To make sure you do not inadvertently block the **SSL/TLS Recommender**, review your settings to make sure your domain:
 
-- Is accessible.
-- Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
-- Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
+* Is accessible.
+* Is not blocking requests from our bot (which uses a user agent of `Cloudflare-SSLDetector`).
+* Does not have any active, SSL-specific [Page Rules](/rules/page-rules/) or [Configuration rules](/rules/configuration-rules/).
diff --git a/src/content/partials/ssl/test-tls-version.mdx b/src/content/partials/ssl/test-tls-version.mdx
index 7795c23bee8e13c..610dd99b691b6f9 100644
--- a/src/content/partials/ssl/test-tls-version.mdx
+++ b/src/content/partials/ssl/test-tls-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To test supported TLS versions, attempt a request to your website or application while specifying a TLS version.
@@ -16,4 +17,4 @@ If the TLS version you are testing is blocked by Cloudflare, the TLS handshake i
 
 :::note
 Local VPN or a device security client may prevent insecure connections using legacy protocols like TLS 1.0. Make sure to disable such network or security client before running the test on your device.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
index 39ab2370be87926..40fff440b9fdfbe 100644
--- a/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
+++ b/src/content/partials/ssl/tls-1.3-cipher-limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You cannot set specific TLS 1.3 ciphers. Instead, you can enable [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) for your entire zone and Cloudflare will use [all applicable TLS 1.3 cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites/). In combination with this, you can still [disable weak cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/) for TLS 1.0-1.2.
diff --git a/src/content/partials/ssl/total-tls-character-limitation.mdx b/src/content/partials/ssl/total-tls-character-limitation.mdx
index 958bf51b7fa1f6c..2f4bd6c578be433 100644
--- a/src/content/partials/ssl/total-tls-character-limitation.mdx
+++ b/src/content/partials/ssl/total-tls-character-limitation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
-Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
+Total TLS certificates follow the Common Name (CN) restriction of 64 characters ([RFC 5280](https://www.rfc-editor.org/rfc/rfc5280.html)). If you have a hostname that exceeds this length, you can create an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) via API to cover it.
\ No newline at end of file
diff --git a/src/content/partials/ssl/txt-validation-api.mdx b/src/content/partials/ssl/txt-validation-api.mdx
index 26ae11200ce4d88..cdf1f38f24b2fcc 100644
--- a/src/content/partials/ssl/txt-validation-api.mdx
+++ b/src/content/partials/ssl/txt-validation-api.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 You can access these tokens using the API with the [`GET` request](/api/resources/ssl/subresources/certificate_packs/methods/get/) and including `status=pending_validation` as a request parameter.
@@ -8,31 +9,31 @@ For example, here are two tokens highlighted in the API response for a wildcard
 
 ```json title="Response" {13,14,15,16,17,18,19,20,21,22,23,24}
 {
-	"result": [
-		{
-			"id": "<CERTIFICATE_ID>",
-			"type": "advanced",
-			"hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
-			"primary_certificate": "0",
-			"status": "pending_validation",
-			"certificates": [],
-			"created_on": "2022-10-12T21:46:21.979150Z",
-			"validity_days": 90,
-			"validation_method": "txt",
-			"validation_records": [
-				{
-					"status": "pending",
-					"txt_name": "_acme-challenge.<DOMAIN>.com",
-					"txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
-				},
-				{
-					"status": "pending",
-					"txt_name": "_acme-challenge.<DOMAIN>.com",
-					"txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
-				}
-			],
-			"certificate_authority": "google"
-		}
-	]
+  "result": [
+    {
+      "id": "<CERTIFICATE_ID>",
+      "type": "advanced",
+      "hosts": ["*.<DOMAIN>.com", "<DOMAIN>.com"],
+      "primary_certificate": "0",
+      "status": "pending_validation",
+      "certificates": [],
+      "created_on": "2022-10-12T21:46:21.979150Z",
+      "validity_days": 90,
+      "validation_method": "txt",
+      "validation_records": [
+        {
+          "status": "pending",
+          "txt_name": "_acme-challenge.<DOMAIN>.com",
+          "txt_value": "lXLOcN6cPv0nproViNcUHcahD9TrIPlNgdwesj0pYpk"
+        },
+        {
+          "status": "pending",
+          "txt_name": "_acme-challenge.<DOMAIN>.com",
+          "txt_value": "O0o8VgJu_OGu-T30_cvT-4xO5ZX1_2WsVNUrpUKE6ns"
+        }
+      ],
+      "certificate_authority": "google"
+    }
+  ]
 }
 ```
diff --git a/src/content/partials/ssl/txt-validation-dashboard.mdx b/src/content/partials/ssl/txt-validation-dashboard.mdx
index af46b2c550b4575..e32eed0b158c9b1 100644
--- a/src/content/partials/ssl/txt-validation-dashboard.mdx
+++ b/src/content/partials/ssl/txt-validation-dashboard.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/ssl/txt-validation-definition.mdx b/src/content/partials/ssl/txt-validation-definition.mdx
index adb5d6e522dfef2..01de109728d2ed3 100644
--- a/src/content/partials/ssl/txt-validation-definition.mdx
+++ b/src/content/partials/ssl/txt-validation-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 TXT record validation requires the creation of a TXT record in the hostname's authoritative DNS.
diff --git a/src/content/partials/ssl/txt-validation-preamble.mdx b/src/content/partials/ssl/txt-validation-preamble.mdx
index f373dcb972851f5..93faafe1adf5447 100644
--- a/src/content/partials/ssl/txt-validation-preamble.mdx
+++ b/src/content/partials/ssl/txt-validation-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you [create a new certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#create-a-certificate) and choose the validation method of **TXT**, your tokens will be ready after a few seconds.
diff --git a/src/content/partials/ssl/universal-ssl-enable-full.mdx b/src/content/partials/ssl/universal-ssl-enable-full.mdx
index 4eae263d68c1083..ccc7dd4e0694511 100644
--- a/src/content/partials/ssl/universal-ssl-enable-full.mdx
+++ b/src/content/partials/ssl/universal-ssl-enable-full.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For domains on a [primary setup (full)](/dns/zone-setups/full-setup/)[^1], your domain should **automatically** receive its Universal SSL certificate within **15 minutes to 24 hours** of domain activation[^2].
diff --git a/src/content/partials/ssl/universal-ssl-validity.mdx b/src/content/partials/ssl/universal-ssl-validity.mdx
index 10512702dea5b86..ab44a9287adf96f 100644
--- a/src/content/partials/ssl/universal-ssl-validity.mdx
+++ b/src/content/partials/ssl/universal-ssl-validity.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For Universal certificates, Cloudflare controls the validity periods and certificate authorities (CAs), making sure that renewal always occur.
@@ -8,4 +9,4 @@ For Universal certificates, Cloudflare controls the validity periods and certifi
 If you are on a [CNAME setup (partial)](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup), make sure [Domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/) is configured correctly. Refer to [Troubleshooting DCV](/ssl/edge-certificates/changing-dcv-method/troubleshooting/) for further help.
 :::
 
-Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
+Universal certificates have a 90-day validity period. The auto renewal period starts 30 days before expiration.
\ No newline at end of file
diff --git a/src/content/partials/ssl/ussl-limitations-solutions.mdx b/src/content/partials/ssl/ussl-limitations-solutions.mdx
index 3fdeeda79faea70..ee503a418a8aacd 100644
--- a/src/content/partials/ssl/ussl-limitations-solutions.mdx
+++ b/src/content/partials/ssl/ussl-limitations-solutions.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 To prevent insecure connections on a multi-level subdomain, do one of the following:
 
-- Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
-- Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
-- Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
+* Enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/), which automatically issues individual certificates to your proxied hostnames not covered by a Universal certificate.
+* Order an [Advanced Certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) covering the subdomain.
+* Upload a [Custom Certificate](/ssl/edge-certificates/custom-certificates/) covering the subdomain.
 
 If none of these solutions work, you could also remove the multi-level subdomain.
diff --git a/src/content/partials/ssl/ussl-limitations-table.mdx b/src/content/partials/ssl/ussl-limitations-table.mdx
index 7d391d48177e70e..f2f932a5a2b1a7e 100644
--- a/src/content/partials/ssl/ussl-limitations-table.mdx
+++ b/src/content/partials/ssl/ussl-limitations-table.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 By default, Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) only cover your apex domain and one level of subdomain.
diff --git a/src/content/partials/ssl/validation-level-note.mdx b/src/content/partials/ssl/validation-level-note.mdx
index 2eb371ceb102413..03bd8c76025c290 100644
--- a/src/content/partials/ssl/validation-level-note.mdx
+++ b/src/content/partials/ssl/validation-level-note.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Certificates issued through Cloudflare - [Universal](/ssl/edge-certificates/universal-ssl/), [Advanced](/ssl/edge-certificates/advanced-certificate-manager/), and [Custom Hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/) certificates - are Domain Validated (DV). You can [upload a custom certificate](/ssl/edge-certificates/custom-certificates/) if your organization needs OV or EV certificates.
diff --git a/src/content/partials/stream/android_playback_code_snippet.mdx b/src/content/partials/stream/android_playback_code_snippet.mdx
index e60e829108231a9..6962729cc8a9fce 100644
--- a/src/content/partials/stream/android_playback_code_snippet.mdx
+++ b/src/content/partials/stream/android_playback_code_snippet.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```kotlin
diff --git a/src/content/partials/stream/chromecast_limitations.mdx b/src/content/partials/stream/chromecast_limitations.mdx
index e7a4b69eed6c016..0aa204b3ebbd6bb 100644
--- a/src/content/partials/stream/chromecast_limitations.mdx
+++ b/src/content/partials/stream/chromecast_limitations.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/stream/ios_playback_code_snippet.mdx b/src/content/partials/stream/ios_playback_code_snippet.mdx
index f9d23f1f2ea17d1..5b446692c4df2da 100644
--- a/src/content/partials/stream/ios_playback_code_snippet.mdx
+++ b/src/content/partials/stream/ios_playback_code_snippet.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ```swift
diff --git a/src/content/partials/stream/prereqs.mdx b/src/content/partials/stream/prereqs.mdx
index abc70769ba595b1..3c8c70289c8042a 100644
--- a/src/content/partials/stream/prereqs.mdx
+++ b/src/content/partials/stream/prereqs.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Before you can play videos, you must first [upload a video to Cloudflare Stream](/stream/uploading-videos/) or be [actively streaming to a live input](/stream/stream-live)
 
+
 :::
diff --git a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
index 4359b8da3c410e2..aa189ea437225d8 100644
--- a/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
+++ b/src/content/partials/stream/prereqs_first_start_live_streaming.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Before you can play live video, you must first be [actively streaming to a live input](/stream/stream-live/start-stream-live).
 
+
 :::
diff --git a/src/content/partials/stream/srt-supported-modes.mdx b/src/content/partials/stream/srt-supported-modes.mdx
index 2355744270cb533..e265ce9ecd07404 100644
--- a/src/content/partials/stream/srt-supported-modes.mdx
+++ b/src/content/partials/stream/srt-supported-modes.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 Stream only supports the SRT caller mode, which is responsible for broadcasting a live stream after a connection is established.
 
+
 :::
diff --git a/src/content/partials/style-guide/directory-listing-definition.mdx b/src/content/partials/style-guide/directory-listing-definition.mdx
index 3fe2c759e1c53cc..e301ae54c2538d0 100644
--- a/src/content/partials/style-guide/directory-listing-definition.mdx
+++ b/src/content/partials/style-guide/directory-listing-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
+Use `<DirectoryListing />` to display the directory of a specific folder, which appears as a list of links.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/icons.mdx b/src/content/partials/style-guide/icons.mdx
index e7565605607107d..0ff4d9b2bdff1b2 100644
--- a/src/content/partials/style-guide/icons.mdx
+++ b/src/content/partials/style-guide/icons.mdx
@@ -3,4 +3,4 @@ params:
   - component
 ---
 
-Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
+Optionally, you can choose a corresponding icon from Starlight’s [Icons](https://starlight.astro.build/reference/icons/#all-icons) for {props.component}.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/public-stats-definition.mdx b/src/content/partials/style-guide/public-stats-definition.mdx
index 5c337b32e6019f3..0feedc632bbe330 100644
--- a/src/content/partials/style-guide/public-stats-definition.mdx
+++ b/src/content/partials/style-guide/public-stats-definition.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
+The `PublicStats` component allows you to reference specific values about Cloudflare's network without maintaining those values in multiple files.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/tab-guidance.mdx b/src/content/partials/style-guide/tab-guidance.mdx
index 0c4938e1fd9a2ce..bbabd5ac6d12ff3 100644
--- a/src/content/partials/style-guide/tab-guidance.mdx
+++ b/src/content/partials/style-guide/tab-guidance.mdx
@@ -2,6 +2,6 @@
 {}
 ---
 
-The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section.
+The primary answer or core instruction should always appear in the main content flow, not exclusively inside a tab or collapsible section. 
 
-Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
+Use tabs for platform-specific variations (for example, Dashboard versus API versus Terraform) only after stating the general concept. Use Details for supplementary information, not for the primary answer.
\ No newline at end of file
diff --git a/src/content/partials/style-guide/table-guidelines.mdx b/src/content/partials/style-guide/table-guidelines.mdx
index 5095d31cef3b176..add12c6f1f8fea9 100644
--- a/src/content/partials/style-guide/table-guidelines.mdx
+++ b/src/content/partials/style-guide/table-guidelines.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
+Introduce tables with a complete sentence that describes the purpose of the table because not all screen readers preannounce tables. The introductory sentence can end with a colon or a period; usually a colon if it immediately precedes the table, and usually a period if there's more material (such as a note paragraph) between the introduction and the table.
\ No newline at end of file
diff --git a/src/content/partials/support/2fa-enable.mdx b/src/content/partials/support/2fa-enable.mdx
index dcde0ef633ea1f1..f93e4811432751f 100644
--- a/src/content/partials/support/2fa-enable.mdx
+++ b/src/content/partials/support/2fa-enable.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 We recommend that all Cloudflare user account holders enable two-factor authentication (2FA) to keep your accounts secure. 
diff --git a/src/content/partials/support/2fa-overview.mdx b/src/content/partials/support/2fa-overview.mdx
index ef795a849728569..566f562331ebb06 100644
--- a/src/content/partials/support/2fa-overview.mdx
+++ b/src/content/partials/support/2fa-overview.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Two-factor authentication (2FA) allows user account owners to add an additional layer of login security to Cloudflare accounts. This additional authentication step requires you to provide both something you know, such as a Cloudflare password, and something you have, such as an authentication code from a mobile device.
diff --git a/src/content/partials/tenant/account-definition.mdx b/src/content/partials/tenant/account-definition.mdx
index 9ad1c4090b9bb5a..02febfffaee6f3b 100644
--- a/src/content/partials/tenant/account-definition.mdx
+++ b/src/content/partials/tenant/account-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An entity that contains various settings, users, and resources (zones, Zero Trust applications, Workers).
diff --git a/src/content/partials/tenant/account-details-preamble.mdx b/src/content/partials/tenant/account-details-preamble.mdx
index f43626e1f450432..67723262e1208c1 100644
--- a/src/content/partials/tenant/account-details-preamble.mdx
+++ b/src/content/partials/tenant/account-details-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An [**Account**](/tenant/glossary/#account) will contain various settings, resources, and subscriptions to products for users. Each Tenant can have multiple associated accounts.
diff --git a/src/content/partials/tenant/account-details.mdx b/src/content/partials/tenant/account-details.mdx
index beac7c19ba854a0..0fe39346e3d974f 100644
--- a/src/content/partials/tenant/account-details.mdx
+++ b/src/content/partials/tenant/account-details.mdx
@@ -1,20 +1,27 @@
 ---
 {}
+
 ---
 
+
+
 To retrieve a list of accounts associated with a Tenant details, send a `GET` request to the `/tenants/{tenant_id}/accounts` endpoint. You can find the Tenant tag and all Tenants associated with the user with the [**Tenant Details**](/tenant/how-to/get-tenant-details/) API. The Tenant Accounts API also requires pagination passed as query parameters:
 
-- `page` number
-  - Page number of accounts list response, indexed from 1
+* `page` number
+
+  * Page number of accounts list response, indexed from 1
+
+* `per_page` number
+
+  * Number of accounts to display per page
+
+* `order` string
+  * (optional) Order by a specific column, has to be a valid top-level key from the response
 
-- `per_page` number
-  - Number of accounts to display per page
+  * `direction` number
+    * (optional) 0 for ascending or 1 for descending, is 0 by default
 
-- `order` string
-  - (optional) Order by a specific column, has to be a valid top-level key from the response
 
-  - `direction` number
-    - (optional) 0 for ascending or 1 for descending, is 0 by default
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/tenants/{tenant_id}/accounts?page=1&per_page=10" \
diff --git a/src/content/partials/tenant/account-preamble.mdx b/src/content/partials/tenant/account-preamble.mdx
index e1243d170a99457..f8b3baf7f3775a0 100644
--- a/src/content/partials/tenant/account-preamble.mdx
+++ b/src/content/partials/tenant/account-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Each customer or team that uses Cloudflare should have their own account. This ensures proper security and access of resources. Each account acts as a container of zones and other resources. Depending on your needs, you may even provision multiple accounts for a single customer or team.
diff --git a/src/content/partials/tenant/create-account-api.mdx b/src/content/partials/tenant/create-account-api.mdx
index 0783c47157f77f3..7c40a5a7b6cd770 100644
--- a/src/content/partials/tenant/create-account-api.mdx
+++ b/src/content/partials/tenant/create-account-api.mdx
@@ -1,39 +1,51 @@
 ---
 {}
+
 ---
 
+
+
 To create an account using the API, make a `POST` request to the `/accounts` endpoint and include the following values:
 
-- `name` string
-  - The name of the account that is displayed in the Cloudflare dashboard.
+* `name` string
 
-- `type` enum
-  - Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
+  * The name of the account that is displayed in the Cloudflare dashboard.
 
-- `unit` object
-  - Information related to the tenant unit.
+* `type` enum
 
-  - `id` string
-    - (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
+  * Valid values are `standard` (default) and `enterprise`. For self-serve customers, use `standard`. For enterprise customers, use `enterprise`.
+
+* `unit` object
+  * Information related to the tenant unit.
+
+  * `id` string
+    * (optional) ID of the unit to create this account on. Needs to be specified if user administers multiple tenants. Unit ID is the `unit_tag` from your [tenant details](/tenant/how-to/get-tenant-details/).
 
 ### Know-Your-Customer (optional)
 
 All KYC parameters are text fields, have a 120 character limit, and are optional unless enforced by the Tenant.
 
-- `business_name` string
-  - (optional) The name of the business associated with this account.
+* `business_name` string
+
+  * (optional) The name of the business associated with this account.
+
+* `business_address` string
+
+  * (optional) The address of the business associated with this account.
+
+* `business_email` string
+
+  * (optional) The email of the business associated with this account.
+
+* `business_phone` string
+
+  * (optional) The phone number of the business associated with this account.
 
-- `business_address` string
-  - (optional) The address of the business associated with this account.
+* `external_metadata` string
 
-- `business_email` string
-  - (optional) The email of the business associated with this account.
+  * (optional) External metadata for this account.
 
-- `business_phone` string
-  - (optional) The phone number of the business associated with this account.
 
-- `external_metadata` string
-  - (optional) External metadata for this account.
 
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/accounts" \
@@ -50,17 +62,17 @@ A successful request will return an HTTP status of `200` and the following respo
 
 ```json title="Response"
 {
-	"result": {
-		"id": "2bab6ace8c72ed3f09b9eca6db1396bb",
-		"name": "<ACCOUNT_NAME>",
-		"type": "standard",
-		"settings": {
-			"enforce_twofactor": false
-		}
-	},
-	"success": true,
-	"errors": [],
-	"messages": []
+  "result": {
+    "id": "2bab6ace8c72ed3f09b9eca6db1396bb",
+    "name": "<ACCOUNT_NAME>",
+    "type": "standard",
+    "settings": {
+      "enforce_twofactor": false
+    }
+  },
+  "success": true,
+  "errors": [],
+  "messages": []
 }
 ```
 
diff --git a/src/content/partials/tenant/create-account-dash.mdx b/src/content/partials/tenant/create-account-dash.mdx
index b419db913d27be1..5ac799f25ff0d84 100644
--- a/src/content/partials/tenant/create-account-dash.mdx
+++ b/src/content/partials/tenant/create-account-dash.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To create an account under your tenant using the dashboard:
diff --git a/src/content/partials/tenant/create-account-subscription.mdx b/src/content/partials/tenant/create-account-subscription.mdx
index 5de32a989695839..3079c476a2951ff 100644
--- a/src/content/partials/tenant/create-account-subscription.mdx
+++ b/src/content/partials/tenant/create-account-subscription.mdx
@@ -1,17 +1,25 @@
 ---
 {}
+
 ---
 
+
+
 To create an account subscription, send a [POST](/api/resources/accounts/subresources/subscriptions/methods/create/) request to the `/accounts/{account_id}/subscriptions` endpoint and include the following values:
 
-- `rate_plan` object
-  - Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
+* `rate_plan` object
+
+  * Contains the account subscription corresponding to a specific add-on service. For a list of available values, refer to [Available subscriptions](/tenant/reference/subscriptions/).
+
+* `component_values` array
+
+  * Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
+
+* `frequency` string
+
+  * How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-- `component_values` array
-  - Additional services depending on your reseller agreement, such as additional endpoints for load balancing or additional seats for Cloudflare Zero Trust. If not included, the subscription includes the default values associated with each purchase.
 
-- `frequency` string
-  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
 ```bash title="Request"
 curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/subscriptions' \
diff --git a/src/content/partials/tenant/create-zone-subscription.mdx b/src/content/partials/tenant/create-zone-subscription.mdx
index bf71f6c38a3b69f..4535e906db668f5 100644
--- a/src/content/partials/tenant/create-zone-subscription.mdx
+++ b/src/content/partials/tenant/create-zone-subscription.mdx
@@ -1,19 +1,27 @@
 ---
 {}
+
 ---
 
+
+
 To create a zone subscription, typically used to upgrade a zone's plan from `PARTNERS_FREE` to a paid [Zone plan](/tenant/reference/subscriptions/#zone-plans), send a [POST](/api/resources/zones/subresources/subscriptions/methods/create/) request to the `/zones/{zone_id}/subscription` endpoint and include the following values:
 
-- `rate_plan` object
-  - Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
+* `rate_plan` object
+
+  * Contains the zone plan corresponding to what customers would order in the dashboard. For a list of available values, refer to [Zone subscriptions](/tenant/reference/subscriptions/#zone-plans).
+
+* `component_values` array
+
+  * Additional services depending on your reseller agreement, such as additional `page_rules`.
+
+* `frequency` string
+
+  * How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-- `component_values` array
-  - Additional services depending on your reseller agreement, such as additional `page_rules`.
 
-- `frequency` string
-  - How often the subscription is renewed automatically (defaults to `"monthly"`).
 
-```bash title="Request (without `component_values`)"
+```bash title="Request (without &#x60;component_values&#x60;)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
@@ -25,7 +33,7 @@ curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 }'
 ```
 
-```bash title="Request (with `component_values`)"
+```bash title="Request (with &#x60;component_values&#x60;)"
 curl 'https://api.cloudflare.com/client/v4/zones/{zone_id}/subscription' \
 --header "Authorization: Bearer <API_TOKEN>" \
 --header "Content-Type: application/json" \
diff --git a/src/content/partials/tenant/resource-definition.mdx b/src/content/partials/tenant/resource-definition.mdx
index ccd4f6b5cf492d4..e8eb77e0f94146a 100644
--- a/src/content/partials/tenant/resource-definition.mdx
+++ b/src/content/partials/tenant/resource-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A resource is an entity owned by an account, which could be a zone/domain, a Workers instance, or a Zero Trust application.
diff --git a/src/content/partials/tenant/tenant-admin-definition.mdx b/src/content/partials/tenant/tenant-admin-definition.mdx
index 93e8c088ed8bd38..fad90445024fac8 100644
--- a/src/content/partials/tenant/tenant-admin-definition.mdx
+++ b/src/content/partials/tenant/tenant-admin-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once you sign a partner agreement with Cloudflare, we create a special Tenant account and then add your user to that account as a **Tenant admin**. Cloudflare can add multiple users as Tenant admins upon request.
diff --git a/src/content/partials/tenant/tenant-definition.mdx b/src/content/partials/tenant/tenant-definition.mdx
index c3f7cca0a2e8b7d..750a5387fbdb3c1 100644
--- a/src/content/partials/tenant/tenant-definition.mdx
+++ b/src/content/partials/tenant/tenant-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A **Tenant** is a special type of Cloudflare account that contains other accounts and resources.
diff --git a/src/content/partials/tenant/tenant-details-preamble.mdx b/src/content/partials/tenant/tenant-details-preamble.mdx
index a54abfd6e57347a..d1b84c3b3cbac7c 100644
--- a/src/content/partials/tenant/tenant-details-preamble.mdx
+++ b/src/content/partials/tenant/tenant-details-preamble.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A [**Tenant Admin**](/tenant/glossary/#tenant-admin)'s unit and membership details will be used for access of resources and all Tenant operations on the API. The unit ID (`unit_tag`), for example, can be used to create an account on a specific unit.
diff --git a/src/content/partials/tenant/tenant-details.mdx b/src/content/partials/tenant/tenant-details.mdx
index 9ee665e4b7dff30..131ba5be5b9e779 100644
--- a/src/content/partials/tenant/tenant-details.mdx
+++ b/src/content/partials/tenant/tenant-details.mdx
@@ -1,9 +1,14 @@
 ---
 {}
+
 ---
 
+
+
 To retrieve tenant details, send a `GET` request to the `/user/tenants` endpoint:
 
+
+
 ```bash title="Request"
 curl "https://api.cloudflare.com/client/v4/user/tenants" \
 --header "X-Auth-Email: <EMAIL>" \
diff --git a/src/content/partials/tenant/user-definition.mdx b/src/content/partials/tenant/user-definition.mdx
index a7bb17ad18df033..6b17b01a9d90808 100644
--- a/src/content/partials/tenant/user-definition.mdx
+++ b/src/content/partials/tenant/user-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A member of a Cloudflare account with their own user profile and [an associated role](/fundamentals/manage-members/roles/) that specifies their privileges within that account.
diff --git a/src/content/partials/terraform/create-r2-buckets.mdx b/src/content/partials/terraform/create-r2-buckets.mdx
index 3e04904347b494d..13c5a4d7689c5d6 100644
--- a/src/content/partials/terraform/create-r2-buckets.mdx
+++ b/src/content/partials/terraform/create-r2-buckets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { TabItem, Tabs } from "~/components";
diff --git a/src/content/partials/terraform/find-ids-managed-rulesets.mdx b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
index f096359f08c52fb..e93b48bff9fb814 100644
--- a/src/content/partials/terraform/find-ids-managed-rulesets.mdx
+++ b/src/content/partials/terraform/find-ids-managed-rulesets.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy the managed rulesets.
 
-- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
 
 The deployment of managed rulesets via Terraform requires that you use the ruleset IDs. To find the IDs of managed rulesets, use the [List account rulesets](/api/resources/rulesets/methods/list/) operation. The response will include the description and IDs of existing managed rulesets.
diff --git a/src/content/partials/terraform/find-ids.mdx b/src/content/partials/terraform/find-ids.mdx
index 989917bed7dc690..25181bac1db4ec9 100644
--- a/src/content/partials/terraform/find-ids.mdx
+++ b/src/content/partials/terraform/find-ids.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 The Terraform configurations provided in this page need the zone ID (or account ID) of the zone/account where you will deploy rulesets.
 
-- To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
-- To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
+* To retrieve the list of accounts you have access to, including their IDs, use the [List accounts](/api/resources/accounts/methods/list/) operation.
+* To retrieve the list of zones you have access to, including their IDs, use the [List zones](/api/resources/zones/methods/list/) operation.
diff --git a/src/content/partials/terraform/import-delete-existing-rulesets.mdx b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
index b31987c47c68650..3b1d669425223b3 100644
--- a/src/content/partials/terraform/import-delete-existing-rulesets.mdx
+++ b/src/content/partials/terraform/import-delete-existing-rulesets.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
 Terraform assumes that it has complete control over account and zone rulesets. If you already have rulesets configured in your account or zone, do one of the following:
 
-- [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
-- Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
+* [Import existing rulesets to Terraform](/terraform/advanced-topics/import-cloudflare-resources/) using the `cf-terraforming` tool. Recent versions of the tool can generate resource definitions for existing rulesets and import their configuration to Terraform state.
+* Start from scratch by [deleting existing rulesets](/ruleset-engine/rulesets-api/delete/#delete-ruleset) (account and zone rulesets with `"kind": "root"` and `"kind": "zone"`, respectively) and then defining your rulesets configuration in Terraform.
diff --git a/src/content/partials/terraform/v4-code-snippets.mdx b/src/content/partials/terraform/v4-code-snippets.mdx
index 485490e7bf66300..99de18e73442fe3 100644
--- a/src/content/partials/terraform/v4-code-snippets.mdx
+++ b/src/content/partials/terraform/v4-code-snippets.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 :::note
 Terraform code snippets below refer to the v4 SDK only.
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/terraform/v5-code-snippets.mdx b/src/content/partials/terraform/v5-code-snippets.mdx
index 65ddb58c386e133..4bd83b42ff17813 100644
--- a/src/content/partials/terraform/v5-code-snippets.mdx
+++ b/src/content/partials/terraform/v5-code-snippets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::note
diff --git a/src/content/partials/time-services/ntp-definition.mdx b/src/content/partials/time-services/ntp-definition.mdx
index df9e63e8a5ab83d..76dc31d5a57dd6a 100644
--- a/src/content/partials/time-services/ntp-definition.mdx
+++ b/src/content/partials/time-services/ntp-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [Network Time Protocol](https://tools.ietf.org/html/rfc1305) (NTP) is an Internet protocol designed to synchronize time between computer systems communicating over unreliable and variable-latency network paths. Cloudflare offers its version of NTP for free so you can use our [global anycast network](https://www.cloudflare.com/network/) to synchronize time from our closest server.
diff --git a/src/content/partials/turnstile/challenge-behavior.mdx b/src/content/partials/turnstile/challenge-behavior.mdx
index ff0bebf920921ee..f60a738f5071a3e 100644
--- a/src/content/partials/turnstile/challenge-behavior.mdx
+++ b/src/content/partials/turnstile/challenge-behavior.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare issues challenges through the [Challenge Platform](/cloudflare-challenges/), which is the same underlying technology powering [Turnstile](/turnstile/).
diff --git a/src/content/partials/turnstile/privacy-policy.mdx b/src/content/partials/turnstile/privacy-policy.mdx
index 061f021d37cc27a..cc7c482ea104785 100644
--- a/src/content/partials/turnstile/privacy-policy.mdx
+++ b/src/content/partials/turnstile/privacy-policy.mdx
@@ -2,4 +2,4 @@
 {}
 ---
 
-As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
+As a condition of enabling invisible mode, you must reference Cloudflare's [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) in your own privacy policy.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/proxied-hostnames.mdx b/src/content/partials/turnstile/proxied-hostnames.mdx
index e9d1fd903e735be..e8beeab649b6d39 100644
--- a/src/content/partials/turnstile/proxied-hostnames.mdx
+++ b/src/content/partials/turnstile/proxied-hostnames.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 If your hostname is proxied through Cloudflare, visitors may experience challenges on your webpages.
diff --git a/src/content/partials/turnstile/security-requirements.mdx b/src/content/partials/turnstile/security-requirements.mdx
index 2569ee7839e2ca3..7a31837435e6e89 100644
--- a/src/content/partials/turnstile/security-requirements.mdx
+++ b/src/content/partials/turnstile/security-requirements.mdx
@@ -1,7 +1,9 @@
 ---
 {}
+
 ---
 
+
 - Server-side validation is mandatory. It is critical to enforce Turnstile tokens with the Siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. You must call Siteverify to complete your Turnstile configuration. Otherwise, it is incomplete and will result in zeroes for token validation when viewing your metrics in [Turnstile Analytics](/turnstile/turnstile-analytics/).
 
 - Tokens expire after 300 seconds (5 minutes). Each token can only be validated once. Expired or used tokens must be replaced with fresh challenges.
diff --git a/src/content/partials/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/siteverify-warning.mdx
index 979c06c7a94acd4..4e5b0a232868dfd 100644
--- a/src/content/partials/turnstile/siteverify-warning.mdx
+++ b/src/content/partials/turnstile/siteverify-warning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 :::caution[Warning]
diff --git a/src/content/partials/turnstile/siteverify.mdx b/src/content/partials/turnstile/siteverify.mdx
index 775e57ebf87175b..59ba0e6f92f190a 100644
--- a/src/content/partials/turnstile/siteverify.mdx
+++ b/src/content/partials/turnstile/siteverify.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
 It is important to [call the Siteverify API](/turnstile/get-started/server-side-validation/). Without calling Siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
 
 - Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
 - Tokens expire after five minutes. Validation must occur within this window to be effective.
-- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
+- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/test-secret-key.mdx b/src/content/partials/turnstile/test-secret-key.mdx
index 142da6b947bd3e3..67d4fb5139a1840 100644
--- a/src/content/partials/turnstile/test-secret-key.mdx
+++ b/src/content/partials/turnstile/test-secret-key.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 You can test the dummy token generated with testing sitekey via Siteverify API with the testing secret key. Your production secret keys will reject dummy tokens.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/test-sitekey.mdx b/src/content/partials/turnstile/test-sitekey.mdx
index 5bb6f0697d38eaf..5ecb3a3c4062605 100644
--- a/src/content/partials/turnstile/test-sitekey.mdx
+++ b/src/content/partials/turnstile/test-sitekey.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
 You can test your Turnstile widget on your webpage without triggering an actual Cloudflare Challenge by using a testing sitekey.
 
-Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
+Refer to [Testing](/turnstile/troubleshooting/testing/) for more information.
\ No newline at end of file
diff --git a/src/content/partials/turnstile/troubleshooting-steps.mdx b/src/content/partials/turnstile/troubleshooting-steps.mdx
index 471234502a31d07..8e9ff7625e051fb 100644
--- a/src/content/partials/turnstile/troubleshooting-steps.mdx
+++ b/src/content/partials/turnstile/troubleshooting-steps.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 1. Verify your browser compatibility.
-   - Turnstile supports all major browsers, except Internet Explorer.
-   - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
-   - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
+    - Turnstile supports all major browsers, except Internet Explorer.
+    - Ensure your browser is up to date. For more information, refer to our [Supported browsers](/cloudflare-challenges/reference/supported-browsers/).
+    - Run a test on the [compatibility checking tool](https://browser-compat.turnstile.workers.dev/).
 2. Disable your browser extensions.
-   - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
-   - Temporarily disable all extensions and reload the page.
+    - Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
+    - Temporarily disable all extensions and reload the page.
 3. Enable JavaScript.
-   - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
+    - Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
 4. Try Incognito or Private mode.
-   - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
+    - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
 5. Test another browser or device.
-   - Switch to a different browser or device to see if the issue is specific to your current setup.
+    - Switch to a different browser or device to see if the issue is specific to your current setup.
 6. Avoid VPNs or proxies.
-   - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
+    - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
 7. Switch to a different network.
-   - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
+    - Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
diff --git a/src/content/partials/turnstile/widget-components.mdx b/src/content/partials/turnstile/widget-components.mdx
index a72f62cd2d99b6f..36da69ec11fc53f 100644
--- a/src/content/partials/turnstile/widget-components.mdx
+++ b/src/content/partials/turnstile/widget-components.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 Each widget gets its own unique sitekey and secret key pair, and options for configurations.
 
-| Component      | Description                                                  |
-| -------------- | ------------------------------------------------------------ |
-| Sitekey        | Public key used to invoke the Turnstile widget on your site. |
-| Secret key     | Private key used for server-side token validation.           |
-| Configurations | Mode, hostnames, appearance settings, and other options.     |
+| Component | Description |
+| --- | --- |
+| Sitekey | Public key used to invoke the Turnstile widget on your site. |
+| Secret key | Private key used for server-side token validation. |
+| Configurations | Mode, hostnames, appearance settings, and other options. |
diff --git a/src/content/partials/vectorize/vectorize-ga.mdx b/src/content/partials/vectorize/vectorize-ga.mdx
index 78ba16f7ac1273b..efd48735d4aac5d 100644
--- a/src/content/partials/vectorize/vectorize-ga.mdx
+++ b/src/content/partials/vectorize/vectorize-ga.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Vectorize is now Generally Available]
 
+
 To report bugs or give feedback, go to the [#vectorize Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
+
 :::
diff --git a/src/content/partials/vectorize/vectorize-pricing.mdx b/src/content/partials/vectorize/vectorize-pricing.mdx
index 8ff2bf6036a4c2c..9281365f50e95ed 100644
--- a/src/content/partials/vectorize/vectorize-pricing.mdx
+++ b/src/content/partials/vectorize/vectorize-pricing.mdx
@@ -2,10 +2,10 @@
 {}
 ---
 
-|                                     | [Workers Free](/workers/platform/pricing/#workers) | [Workers Paid](/workers/platform/pricing/#workers)                              |
-| ----------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------- |
-| **Total queried vector dimensions** | 30 million queried vector dimensions / month       | First 50 million queried vector dimensions / month included + $0.01 per million |
-| **Total stored vector dimensions**  | 5 million stored vector dimensions                 | First 10 million stored vector dimensions + $0.05 per 100 million               |
+|                                     | [Workers Free](/workers/platform/pricing/#workers)       | [Workers Paid](/workers/platform/pricing/#workers)                              |
+| ----------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------- |
+| **Total queried vector dimensions** | 30 million queried vector dimensions / month             | First 50 million queried vector dimensions / month included + $0.01 per million |
+| **Total stored vector dimensions**  | 5 million stored vector dimensions                       | First 10 million stored vector dimensions + $0.05 per 100 million               |
 
 ### Calculating vector dimensions
 
diff --git a/src/content/partials/version-management/create-environment-situation.mdx b/src/content/partials/version-management/create-environment-situation.mdx
index f6971602bd7ee8d..63f1307158b6f24 100644
--- a/src/content/partials/version-management/create-environment-situation.mdx
+++ b/src/content/partials/version-management/create-environment-situation.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Based on your organization's needs, you may need to create additional environments to test and roll out changes.
diff --git a/src/content/partials/version-management/edit-version.mdx b/src/content/partials/version-management/edit-version.mdx
index 39944dba67d8e50..385307cecb41c36 100644
--- a/src/content/partials/version-management/edit-version.mdx
+++ b/src/content/partials/version-management/edit-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,12 +11,12 @@ To change between different versions of your zone:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and a domain that has version management. The Global Configuration of your domain will load.
 3. Go to the product or feature you wish to modify.
-   - **If the product or feature is available for versioning**: The last version you were working on will load.
-   - **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
+   * **If the product or feature is available for versioning**: The last version you were working on will load.
+   * **If the product or feature is NOT available for versioning**: Your Global Configuration will load, and any changes you make will impact live traffic.
 4. Ensure that the configuration or version displayed in the domain summary bar is the one you would like to work on. If not, select the version in the domain summary bar to open the version switcher.
 
 :::note
diff --git a/src/content/partials/version-management/enable-default-creation.mdx b/src/content/partials/version-management/enable-default-creation.mdx
index 8e98769c2ae8675..e4ea2ec7726c964 100644
--- a/src/content/partials/version-management/enable-default-creation.mdx
+++ b/src/content/partials/version-management/enable-default-creation.mdx
@@ -1,16 +1,19 @@
 ---
 {}
+
 ---
 
 Once you [enable](/version-management/how-to/enable/) Version Management, Cloudflare will automatically create:
 
-- **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
-- **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
+* **Version Zero**, think about this as the configuration of your current zone. Once default environments are created, Version Zero is automatically deployed to them, guaranteeing no disruption in your live traffic. This Version is also permanently editable. In case you decide to disable Zone Versioning, Version Zero will become your zone again.
+* **Global Configuration**, you can find all the configurations here that are not supported by Version Management.
 
 :::caution[Important]
 
+
 Any changes made to the **Global Configuration** will immediately apply to your zone and all versions of your zone, affecting live traffic.
 
+
 :::
 
 On the Environments page, you can create default environments for **Production**, **Staging**, and **Development**.
diff --git a/src/content/partials/version-management/enable-versioning.mdx b/src/content/partials/version-management/enable-versioning.mdx
index 12ef04c2c918b0e..0602c8e8c03f543 100644
--- a/src/content/partials/version-management/enable-versioning.mdx
+++ b/src/content/partials/version-management/enable-versioning.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -10,7 +11,7 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
@@ -18,6 +19,8 @@ To enable [Version Management](https://dash.cloudflare.com/?to=/:account/:zone/v
 
 :::note
 
+
 If you cannot enable Version Management, make sure your zone, account, and user meet the [requirements](/version-management/#requirements).
 
+
 :::
diff --git a/src/content/partials/version-management/environment-defaults.mdx b/src/content/partials/version-management/environment-defaults.mdx
index 572b0f7b00346e2..896a639507362a4 100644
--- a/src/content/partials/version-management/environment-defaults.mdx
+++ b/src/content/partials/version-management/environment-defaults.mdx
@@ -1,7 +1,8 @@
 ---
 {}
+
 ---
 
-- **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
-- **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
-- **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
+* **Development**: Meant to validate that changes work correctly. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name, the `Edge Server IP` is a specific value, and the request contains a cookie with `development=true`.
+* **Staging**: Meant to test changes before sending them to **Production**. The default [traffic filters](/version-management/reference/traffic-filters/) are that the `cf.zone.name` matches your zone name and the `Edge Server IP` is a specific value.
+* **Production**: Meant to hold all configurations applied to your zone. You cannot edit the [traffic filters](/version-management/reference/traffic-filters/) - which are just that the `cf.zone.name` is equal to your zone's name - and cannot delete this environment. This environment has a read-only check enabled, so versions promoted to this environment will become read-only as well.
diff --git a/src/content/partials/version-management/environment-definition.mdx b/src/content/partials/version-management/environment-definition.mdx
index 378169d4dcb3cba..8219f760421603b 100644
--- a/src/content/partials/version-management/environment-definition.mdx
+++ b/src/content/partials/version-management/environment-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 An environment is a place to test different versions of your zone configurations.
diff --git a/src/content/partials/version-management/production-read-only-default.mdx b/src/content/partials/version-management/production-read-only-default.mdx
index 9f1294d9a8e859c..309f5eee6b6b858 100644
--- a/src/content/partials/version-management/production-read-only-default.mdx
+++ b/src/content/partials/version-management/production-read-only-default.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 **Production** is a read-only environment by default. This means that any version associated with **Production** also becomes read-only. This configuration prevents another member of your account from accidentally editing the version associated with your live traffic. You can change this configuration by editing the environment.
diff --git a/src/content/partials/version-management/promote-version.mdx b/src/content/partials/version-management/promote-version.mdx
index 953f69ab8ea0963..9fa55abd7e19289 100644
--- a/src/content/partials/version-management/promote-version.mdx
+++ b/src/content/partials/version-management/promote-version.mdx
@@ -1,14 +1,16 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
 
+
 To promote a version:
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/test-version.mdx b/src/content/partials/version-management/test-version.mdx
index 26ffc6023ca8be6..30f9c66058586c5 100644
--- a/src/content/partials/version-management/test-version.mdx
+++ b/src/content/partials/version-management/test-version.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
@@ -8,7 +9,7 @@ Once you have made changes to a version, apply that version to your lowest-ranke
 
 1. Log in to the Cloudflare dashboard.
 
-   <DashButton url="/?to=/:account/home" />
+    <DashButton url="/?to=/:account/home" />
 
 2. Select your account and zone.
 3. Go to **Version Management**.
diff --git a/src/content/partials/version-management/version-definition.mdx b/src/content/partials/version-management/version-definition.mdx
index 23ed20a7ece8e28..32f24171ac0cc3f 100644
--- a/src/content/partials/version-management/version-definition.mdx
+++ b/src/content/partials/version-management/version-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A version is a collection of configurations related to your zone, such as WAF custom rules and [other optimization configurations](/version-management/reference/available-configurations/).
diff --git a/src/content/partials/waf/api-create-ruleset-with-rule.mdx b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
index 18ec3b89654dcc2..04b31a71d329c75 100644
--- a/src/content/partials/waf/api-create-ruleset-with-rule.mdx
+++ b/src/content/partials/waf/api-create-ruleset-with-rule.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To define a specific position for the new rule, include a `position` object in the request body according to the guidelines in [Change the order of a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/#change-the-order-of-a-rule-in-a-ruleset).
diff --git a/src/content/partials/waf/list-advantages.mdx b/src/content/partials/waf/list-advantages.mdx
index d6d8663d04e3c6e..d5fed7a8acd3fbc 100644
--- a/src/content/partials/waf/list-advantages.mdx
+++ b/src/content/partials/waf/list-advantages.mdx
@@ -1,10 +1,11 @@
 ---
 {}
+
 ---
 
-- When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
-- When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
-- Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
+* When creating a rule, using a list is easier and less error-prone than adding a long list of items such as IP addresses to a rule expression.
+* When updating a set of rules that target the same group of IP addresses (or hostnames), using an IP list (or a hostname list) is easier and less error prone than editing multiple rules.
+* Lists are easier to read and more informative, particularly when you use descriptive names for your lists.
 
 When you update the content of a list, any rules that use the list are automatically updated, so you can make a single change to your list rather than modify rules individually.
 
diff --git a/src/content/partials/waf/managed-lists.mdx b/src/content/partials/waf/managed-lists.mdx
index aebc0ae400a11c4..8b6a68a42f9fb86 100644
--- a/src/content/partials/waf/managed-lists.mdx
+++ b/src/content/partials/waf/managed-lists.mdx
@@ -6,8 +6,8 @@
 | ----------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
 | Cloudflare Open Proxies                         | `cf.open_proxies`   | IP addresses of known open HTTP and SOCKS proxy endpoints, which are frequently used to launch attacks and hide attackers identity. |
 | Cloudflare Anonymizers                          | `cf.anonymizer`     | IP addresses of known anonymizers (Open SOCKS Proxies, VPNs, and TOR nodes).                                                        |
-| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers.                                                                                                  |
+| Cloudflare VPNs                                 | `cf.vpn`            | IP addresses of known VPN servers. |
 | Cloudflare Malware                              | `cf.malware`        | IP addresses of known sources of malware.                                                                                           |
 | Cloudflare Botnets, Command and Control Servers | `cf.botnetcc`       | IP addresses of known botnet command-and-control servers.                                                                           |
 
-<br />
+<br />
\ No newline at end of file
diff --git a/src/content/partials/waf/open-ports-blocked-traffic.mdx b/src/content/partials/waf/open-ports-blocked-traffic.mdx
index e360487eafc6582..98358a33d289ffd 100644
--- a/src/content/partials/waf/open-ports-blocked-traffic.mdx
+++ b/src/content/partials/waf/open-ports-blocked-traffic.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Due to the nature of Cloudflare's anycast network, ports other than `80` and `443` will be open so that Cloudflare can serve traffic for other customers on these ports. In general, Cloudflare makes available several different products on [Cloudflare IPs](https://www.cloudflare.com/ips), so you can expect tools like Netcat and security scanners to report these non-standard ports as open in specific conditions. If you have questions on security compliance, review [Cloudflare's certifications and compliance resources](https://www.cloudflare.com/en-gb/trust-hub/compliance-resources/) and contact your Cloudflare enterprise account manager for more information.
diff --git a/src/content/partials/waf/rate-limiting-best-practices.mdx b/src/content/partials/waf/rate-limiting-best-practices.mdx
index 0ef94060427faa0..5f059b73120f923 100644
--- a/src/content/partials/waf/rate-limiting-best-practices.mdx
+++ b/src/content/partials/waf/rate-limiting-best-practices.mdx
@@ -1,9 +1,10 @@
 ---
 {}
+
 ---
 
-- [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
-- [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
-- [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
-- [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
-- [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
+* [Enforce granular access control](/waf/rate-limiting-rules/best-practices/#enforcing-granular-access-control) to resources. Includes access control based on criteria such as user agent, IP address, referrer, host, country, and world region.
+* [Protect against credential stuffing](/waf/rate-limiting-rules/best-practices/#protecting-against-credential-stuffing) and account takeover attacks.
+* [Limit the number of operations](/waf/rate-limiting-rules/best-practices/#limiting-the-number-of-operations) performed by individual clients. Includes preventing scraping by bots, accessing sensitive data, bulk creation of new accounts, and programmatic buying in ecommerce platforms.
+* [Protect REST APIs](/waf/rate-limiting-rules/best-practices/#protecting-rest-apis) from resource exhaustion (targeted DDoS attacks) and resources from abuse in general.
+* [Protect GraphQL APIs](/waf/rate-limiting-rules/best-practices/#protecting-graphql-apis) by preventing server overload and limiting the number of operations.
diff --git a/src/content/partials/waf/rate-limiting-rule-parameters.mdx b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
index ecbeba6002d94e2..00a4d92d21e6462 100644
--- a/src/content/partials/waf/rate-limiting-rule-parameters.mdx
+++ b/src/content/partials/waf/rate-limiting-rule-parameters.mdx
@@ -1,14 +1,15 @@
 ---
 {}
+
 ---
 
-- An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
-- An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
+* An [expression](/ruleset-engine/rules-language/expressions/) that specifies the criteria you are matching traffic on using the [Rules language](/ruleset-engine/rules-language/).
+* An [action](/ruleset-engine/rules-language/actions/) that specifies what to perform when there is a match for the rule and any additional conditions are met. In the case of rate limiting rules, the action occurs when the rate reaches the specified limit.
 
 Besides these two parameters, rate limiting rules require the following additional parameters:
 
-- **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
-- **Period**: The period of time to consider (in seconds) when evaluating the rate.
-- **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
-- **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
-- **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
+* **Characteristics**: The set of parameters that define how Cloudflare tracks the rate for this rule.
+* **Period**: The period of time to consider (in seconds) when evaluating the rate.
+* **Requests per period**: The number of requests over the period of time that will trigger the rate limiting rule.
+* **Duration** (or mitigation timeout): Once the rate is reached, the rate limiting rule blocks further requests for the period of time defined in this field.
+* **Action behavior**: By default, Cloudflare will apply the rule action for the configured duration (or mitigation timeout), regardless of the request rate during this period. Some Enterprise customers can configure the rule to [throttle requests](/waf/rate-limiting-rules/parameters/#with-the-following-behavior) over the maximum rate, allowing incoming requests when the rate is lower than the configured limit.
diff --git a/src/content/partials/waf/rules-next-steps-table.mdx b/src/content/partials/waf/rules-next-steps-table.mdx
index b2513ef838112da..8f12446af3318fa 100644
--- a/src/content/partials/waf/rules-next-steps-table.mdx
+++ b/src/content/partials/waf/rules-next-steps-table.mdx
@@ -6,9 +6,9 @@ params:
 
 import { Markdown } from "~/components";
 
-| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                       |
+| Task                      | Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List all rules in ruleset | <p>Use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name to obtain the list of configured {props.rulesType} and their IDs.</p><p>For more information, refer to [View a specific ruleset](/ruleset-engine/rulesets-api/view/#view-a-specific-ruleset).</p>                                                                                                     |
 | Update a rule             | <p>Use the [Update a zone ruleset rule](/api/resources/rulesets/methods/update/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Update a rule in a ruleset](/ruleset-engine/rulesets-api/update-rule/).</p> |
 | Delete a rule             | <p>Use the [Delete a zone ruleset rule](/api/resources/rulesets/methods/delete/) operation.</p><p>You will need to provide the ruleset ID and the rule ID. To obtain these IDs, you can use the [Get a zone entry point ruleset](/api/resources/rulesets/subresources/phases/methods/get/) operation with the <code>{props.phaseName}</code> phase name.</p><p>For more information, refer to [Delete a rule in a ruleset](/ruleset-engine/rulesets-api/delete-rule/).</p> |
 
diff --git a/src/content/partials/waiting-room/change-queueing-method.mdx b/src/content/partials/waiting-room/change-queueing-method.mdx
index 3a7226abca98756..3ff0fa35e97cda9 100644
--- a/src/content/partials/waiting-room/change-queueing-method.mdx
+++ b/src/content/partials/waiting-room/change-queueing-method.mdx
@@ -1,14 +1,17 @@
 ---
 {}
+
 ---
 
 Though you can change your [queueing method](/waiting-room/reference/queueing-methods/), it may affect users if your waiting room is actively queueing:
 
-- **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
-- **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
+* **From FIFO to Random**: Users will no longer be ordered based on their cookie timestamp, which may affect the displayed wait time.
+* **From Random to FIFO**: Users will be ordered based on their cookie timestamp, meaning any new users move to the end of the FIFO queue.
 
 :::note
 
+
 If you change the queueing method from FIFO > Random > FIFO, users will be ordered by their original entry time.
 
+
 :::
diff --git a/src/content/partials/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/queue-all.mdx
index fe401b22131a2d6..f8625465ac3beeb 100644
--- a/src/content/partials/waiting-room/queue-all.mdx
+++ b/src/content/partials/waiting-room/queue-all.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To queue all visitors prior to a time-based offering, set up a pre-queue as part of a [waiting room event](/waiting-room/additional-options/create-events/#create-an-event-from-the-dashboard).
diff --git a/src/content/partials/waiting-room/queue-some.mdx b/src/content/partials/waiting-room/queue-some.mdx
index 373a1bf37d6b081..a2ae7dd6d08055a 100644
--- a/src/content/partials/waiting-room/queue-some.mdx
+++ b/src/content/partials/waiting-room/queue-some.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 To queue visitors only when necessary:
diff --git a/src/content/partials/warp-client/modes-options.mdx b/src/content/partials/warp-client/modes-options.mdx
index 2965f0ed7c28f20..9582cee987393f3 100644
--- a/src/content/partials/warp-client/modes-options.mdx
+++ b/src/content/partials/warp-client/modes-options.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## WARP modes
@@ -22,11 +23,11 @@ Beyond the two modes of operation, the WARP app lets you configure additional op
 
 The following is a list of options you can configure in the **Connection** tab:
 
-- **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
-- **DNS Protocol**: The available options depend on the WARP mode you have enabled:
-  - **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
-  - **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
-  - **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
-- **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
+* **Disable for all Wi-Fi / wired networks**: Check the box corresponding to the network where you want to prevent WARP from working on.
+* **DNS Protocol**: The available options depend on the WARP mode you have enabled:
+  * **WARP**: Only available when you have the WARP mode enabled. All DNS traffic encrypted and [sent to Cloudflare's global network](/warp-client/warp-modes/#1111-with-warp).
+  * **HTTPS**: All DNS traffic is sent outside the tunnel via [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/).
+  * **TLS**: All DNS traffic is sent outside the tunnel via [encrypted TLS](/1.1.1.1/encryption/dns-over-tls/).
+* **1.1.1.1 for Families**: Allows you to [enable 1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) and choose between blocking malware, or blocking malware and adult content.
 
 For the **Advanced** options, refer to [Exclude or include network traffic with WARP](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/) for more information.
diff --git a/src/content/partials/web-analytics/web-analytics-definition.mdx b/src/content/partials/web-analytics/web-analytics-definition.mdx
index 1b6186550086a2c..1e5015687b288cc 100644
--- a/src/content/partials/web-analytics/web-analytics-definition.mdx
+++ b/src/content/partials/web-analytics/web-analytics-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Web Analytics provides free, privacy-first analytics for your website without changing your DNS or using Cloudflare’s proxy. Cloudflare Web Analytics helps you understand the performance of your web pages as experienced by your site visitors.
diff --git a/src/content/partials/web-analytics/web-analytics-notifications.mdx b/src/content/partials/web-analytics/web-analytics-notifications.mdx
index b0d9f16da41095b..6c43aff254d6a41 100644
--- a/src/content/partials/web-analytics/web-analytics-notifications.mdx
+++ b/src/content/partials/web-analytics/web-analytics-notifications.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Web Analytics uses Cloudflare's Notification service. When enabled, Web Analytics sends you a weekly report with aggregate visits, page views and median page load time for all your sites, so you can monitor their performance.
diff --git a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
index 859414aab8041e6..083546fd2a119b7 100644
--- a/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
+++ b/src/content/partials/web-analytics/web-analytics-proxied-setup.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { DashButton } from "~/components";
diff --git a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
index f57d62227d76b86..e713539e0af17a5 100644
--- a/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
+++ b/src/content/partials/web-analytics/web-analytics-troubleshooting.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 For Cloudflare to automatically add the JavaScript snippet, your pages need to have valid HTML.
@@ -19,7 +20,9 @@ For Web Analytics to correctly insert the JavaScript snippet, you would need val
 		<title>Title</title>
 	</head>
 	<body>
+
 		<p>Hello world.</p>
+
 	</body>
 </html>
 ```
diff --git a/src/content/partials/web3/cloudflare-settings.mdx b/src/content/partials/web3/cloudflare-settings.mdx
index c557eb6be68904f..652075c6ca43719 100644
--- a/src/content/partials/web3/cloudflare-settings.mdx
+++ b/src/content/partials/web3/cloudflare-settings.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Once your gateway becomes [active](/web3/reference/gateway-status/), you can customize the Cloudflare settings associated with your hostname.
diff --git a/src/content/partials/web3/create-gateway-api.mdx b/src/content/partials/web3/create-gateway-api.mdx
index 8b00c7b740ad9b5..e1952e8378a32e6 100644
--- a/src/content/partials/web3/create-gateway-api.mdx
+++ b/src/content/partials/web3/create-gateway-api.mdx
@@ -1,11 +1,12 @@
 ---
 {}
+
 ---
 
 To create a gateway using the API, send a [`POST`](/api/resources/web3/subresources/hostnames/methods/create/) request that includes the following parameters:
 
-- `name`: The hostname that will point to the target gateway via a `CNAME` record.
-- `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
+* `name`: The hostname that will point to the target gateway via a `CNAME` record.
+* `target`: The gateway target for the hostname (`ethereum`, `ipfs`, `ipfs_universal_path`).
 
 If you need help with API authentication, refer to [Cloudflare API documentation](/fundamentals/api/).
 
@@ -26,18 +27,18 @@ The response contains the complete definition of the new gateway.
 
 ```json title="Response"
 {
-	"success": true,
-	"errors": [],
-	"messages": [],
-	"result": {
-		"id": "<WEB3_GATEWAY_ID>",
-		"name": "gateway.example.com",
-		"description": "This is my IPFS gateway.",
-		"status": "active",
-		"target": "ipfs",
-		"dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
-		"created_on": "<CREATED_ON_DATE>",
-		"modified_on": "<MODIFIED_ON_DATE>"
-	}
+  "success": true,
+  "errors": [],
+  "messages": [],
+  "result": {
+    "id": "<WEB3_GATEWAY_ID>",
+    "name": "gateway.example.com",
+    "description": "This is my IPFS gateway.",
+    "status": "active",
+    "target": "ipfs",
+    "dnslink": "/ipns/onboarding.ipfs.cloudflare.com",
+    "created_on": "<CREATED_ON_DATE>",
+    "modified_on": "<MODIFIED_ON_DATE>"
+  }
 }
 ```
diff --git a/src/content/partials/web3/pricing-page-reference.mdx b/src/content/partials/web3/pricing-page-reference.mdx
index 80deb4fcdfdd040..28fa234c7caadd1 100644
--- a/src/content/partials/web3/pricing-page-reference.mdx
+++ b/src/content/partials/web3/pricing-page-reference.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note
 
+
 For more pricing details, refer to the [Web3 product page](https://www.cloudflare.com/application-services/products/web3/).
 
+
 :::
diff --git a/src/content/partials/workers-ai/custom_requirements.mdx b/src/content/partials/workers-ai/custom_requirements.mdx
index dfdd8c4a50439f7..8a34dddf8cb8d82 100644
--- a/src/content/partials/workers-ai/custom_requirements.mdx
+++ b/src/content/partials/workers-ai/custom_requirements.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Custom requirements]
 
+
 If you have custom requirements like private custom models or higher limits, complete the [Custom Requirements Form](https://forms.gle/axnnpGDb6xrmR31T6). Cloudflare will contact you with next steps.
 
+
 :::
diff --git a/src/content/partials/workers-ai/file_issues.mdx b/src/content/partials/workers-ai/file_issues.mdx
index 0e250e4dcc7c3b7..3f30780c51c35ed 100644
--- a/src/content/partials/workers-ai/file_issues.mdx
+++ b/src/content/partials/workers-ai/file_issues.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::caution[Workers AI is now Generally Available]
 
+
 To report bugs or give feedback, go to the [#workers-ai Discord channel](https://discord.cloudflare.com). If you are having issues with Wrangler, report issues in the [Wrangler GitHub repository](https://github.com/cloudflare/workers-sdk/issues/new/choose).
 
+
 :::
diff --git a/src/content/partials/workers-ai/openai-compatibility.mdx b/src/content/partials/workers-ai/openai-compatibility.mdx
index e245b363ffe1571..64bc69da90146c0 100644
--- a/src/content/partials/workers-ai/openai-compatibility.mdx
+++ b/src/content/partials/workers-ai/openai-compatibility.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Workers AI supports OpenAI compatible endpoints for [text generation](/workers-ai/models/) (`/v1/chat/completions`) and [text embedding models](/workers-ai/models/) (`/v1/embeddings`). This allows you to use the same code as you would for your OpenAI commands, but swap in Workers AI easily.
diff --git a/src/content/partials/workers-vpc/create-tunnel-steps.mdx b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
index 4ec8b8731f765c2..9c0aef59ee08b46 100644
--- a/src/content/partials/workers-vpc/create-tunnel-steps.mdx
+++ b/src/content/partials/workers-vpc/create-tunnel-steps.mdx
@@ -1,7 +1,7 @@
 ---
 {}
----
 
+---
 import { Steps } from "~/components";
 
 <Steps>
diff --git a/src/content/partials/workers-vpc/required-roles.mdx b/src/content/partials/workers-vpc/required-roles.mdx
index be0cad6ee37c062..0af2217c4362e96 100644
--- a/src/content/partials/workers-vpc/required-roles.mdx
+++ b/src/content/partials/workers-vpc/required-roles.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Workers VPC uses the following account roles:
diff --git a/src/content/partials/workers/ai-local-usage-charges.mdx b/src/content/partials/workers/ai-local-usage-charges.mdx
index 392a77552fc2ac9..0747f627b173468 100644
--- a/src/content/partials/workers/ai-local-usage-charges.mdx
+++ b/src/content/partials/workers/ai-local-usage-charges.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Workers AI local development usage charges]
 
+
 Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
 
+
 :::
diff --git a/src/content/partials/workers/c3-definition.mdx b/src/content/partials/workers/c3-definition.mdx
index 06920a6667d56af..5cad05a047d4f02 100644
--- a/src/content/partials/workers/c3-definition.mdx
+++ b/src/content/partials/workers/c3-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 [C3 (create-cloudflare-cli)](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare) is a command-line tool designed to help you set up and deploy new applications to Cloudflare. In addition to speed, it leverages officially developed templates for Workers and framework-specific setup guides to ensure each new application that you set up follows Cloudflare and any third-party best practices for deployment on the Cloudflare network.
diff --git a/src/content/partials/workers/compute-per-request.mdx b/src/content/partials/workers/compute-per-request.mdx
index 3114c34331ad0a5..78671c444b721be 100644
--- a/src/content/partials/workers/compute-per-request.mdx
+++ b/src/content/partials/workers/compute-per-request.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs } from "~/components"
 
 Most Workers are a variation on the default Workers flow:
 
diff --git a/src/content/partials/workers/content_and_contentoptions.mdx b/src/content/partials/workers/content_and_contentoptions.mdx
index d033ded8e7aef53..0cd4835706f96a9 100644
--- a/src/content/partials/workers/content_and_contentoptions.mdx
+++ b/src/content/partials/workers/content_and_contentoptions.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Content and ContentOptions]
 
+
 Refer to [Global types](/workers/runtime-apis/html-rewriter/#global-types) for more information on `Content` and `ContentOptions`.
 
+
 :::
diff --git a/src/content/partials/workers/dash-creation-next-steps.mdx b/src/content/partials/workers/dash-creation-next-steps.mdx
index 7e62d21c0a45c4d..3a4659d03dc4f7e 100644
--- a/src/content/partials/workers/dash-creation-next-steps.mdx
+++ b/src/content/partials/workers/dash-creation-next-steps.mdx
@@ -13,7 +13,6 @@ Once you have created your Worker script, you can edit and deploy your Worker us
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
-
 2. Select your application.
 3. Select **Edit Code**.
 
diff --git a/src/content/partials/workers/env_and_secrets.mdx b/src/content/partials/workers/env_and_secrets.mdx
index 60002bb1713e2d1..7efe87d33bc8f1b 100644
--- a/src/content/partials/workers/env_and_secrets.mdx
+++ b/src/content/partials/workers/env_and_secrets.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Compare secrets and environment variables
diff --git a/src/content/partials/workers/envvar-example.mdx b/src/content/partials/workers/envvar-example.mdx
index 1a778eee6e6cefa..a3680630114446c 100644
--- a/src/content/partials/workers/envvar-example.mdx
+++ b/src/content/partials/workers/envvar-example.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/partials/workers/fetch-html-example-js.mdx b/src/content/partials/workers/fetch-html-example-js.mdx
index 132f5b1a1063882..4e19efbae720a72 100644
--- a/src/content/partials/workers/fetch-html-example-js.mdx
+++ b/src/content/partials/workers/fetch-html-example-js.mdx
@@ -1,16 +1,17 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		/**
-		 * Replace `remote` with the host you wish to send requests to
-		 */
-		const remote = "https://example.com";
+  async fetch(request) {
+    /**
+     * Replace `remote` with the host you wish to send requests to
+     */
+    const remote = "https://example.com";
 
-		return await fetch(remote, request);
-	},
+    return await fetch(remote, request);
+  },
 };
 ```
diff --git a/src/content/partials/workers/get-started-dash.mdx b/src/content/partials/workers/get-started-dash.mdx
index c04cc67a0123925..63f3c464720f5e4 100644
--- a/src/content/partials/workers/get-started-dash.mdx
+++ b/src/content/partials/workers/get-started-dash.mdx
@@ -1,11 +1,10 @@
 ---
 {}
----
 
+---
 import { DashButton } from "~/components";
 
 To create your first Worker using the Cloudflare dashboard:
-
 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
    <DashButton url="/?to=/:account/workers-and-pages" />
diff --git a/src/content/partials/workers/isolate-cpu-flexibility.mdx b/src/content/partials/workers/isolate-cpu-flexibility.mdx
index e8cd1b510fbfbe6..2b2c293912bb364 100644
--- a/src/content/partials/workers/isolate-cpu-flexibility.mdx
+++ b/src/content/partials/workers/isolate-cpu-flexibility.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Each [isolate](/workers/reference/how-workers-works/#isolates) has some built-in flexibility to allow for cases where your Worker infrequently runs over the configured limit. If your Worker starts hitting the limit consistently, its execution will be terminated according to the limit configured.
diff --git a/src/content/partials/workers/isolate-description.mdx b/src/content/partials/workers/isolate-description.mdx
index a70b5337ab358ab..48b5a2edfba0141 100644
--- a/src/content/partials/workers/isolate-description.mdx
+++ b/src/content/partials/workers/isolate-description.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 A single instance of the runtime can run hundreds or thousands of isolates, seamlessly switching between them. Each isolate's memory is completely isolated, so each piece of code is protected from other untrusted or user-written code on the runtime. Isolates are also designed to start very quickly. Instead of creating a virtual machine for each function, an isolate is created within an existing environment. This model eliminates the cold starts of the virtual machine model.
diff --git a/src/content/partials/workers/limits_increase.mdx b/src/content/partials/workers/limits_increase.mdx
index fd226c8f5cbf150..e5fa0351f7a8510 100644
--- a/src/content/partials/workers/limits_increase.mdx
+++ b/src/content/partials/workers/limits_increase.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Need a higher limit?]
 
+
 To request an adjustment to a limit, complete the [Limit Increase Request Form](https://forms.gle/ukpeZVLWLnKeixDu7). If the limit can be increased, Cloudflare will contact you with next steps.
 
+
 :::
diff --git a/src/content/partials/workers/nodejs-compat-howto.mdx b/src/content/partials/workers/nodejs-compat-howto.mdx
index 40e11bbb98811e6..2dee652a3cb15d3 100644
--- a/src/content/partials/workers/nodejs-compat-howto.mdx
+++ b/src/content/partials/workers/nodejs-compat-howto.mdx
@@ -1,9 +1,11 @@
 ---
 {}
+
 ---
 
 :::note
 
 To enable built-in Node.js APIs and polyfills, add the nodejs_compat compatibility flag to your [Wrangler configuration file](/workers/wrangler/configuration/). This also enables nodejs_compat_v2 as long as your compatibility date is 2024-09-23 or later. [Learn more about the Node.js compatibility flag and v2](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
 
+
 :::
diff --git a/src/content/partials/workers/playground-callout.mdx b/src/content/partials/workers/playground-callout.mdx
index c854466893a08ef..571ac3076e049f8 100644
--- a/src/content/partials/workers/playground-callout.mdx
+++ b/src/content/partials/workers/playground-callout.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Try the Playground]
 
+
 The quickest way to experiment with Cloudflare Workers is in the [Playground](https://workers.cloudflare.com/playground). The Playground does not require any setup. It is an instant way to preview and test a Worker directly in the browser.
 
+
 :::
diff --git a/src/content/partials/workers/prereqs.mdx b/src/content/partials/workers/prereqs.mdx
index 3d041a42f4203a5..70c0d166cb8f710 100644
--- a/src/content/partials/workers/prereqs.mdx
+++ b/src/content/partials/workers/prereqs.mdx
@@ -1,15 +1,13 @@
 ---
 {}
+
 ---
 
-import { Details } from "~/components";
+import { Details } from "~/components"
 
 1. Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up/workers-and-pages).
 2. Install [`Node.js`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
 
 <Details header="Node.js version manager">
-	Use a Node version manager like [Volta](https://volta.sh/) or
-	[nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change
-	Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed
-	later in this guide, requires a Node version of `16.17.0` or later.
+Use a Node version manager like [Volta](https://volta.sh/) or [nvm](https://github.com/nvm-sh/nvm) to avoid permission issues and change Node.js versions. [Wrangler](/workers/wrangler/install-and-update/), discussed later in this guide, requires a Node version of `16.17.0` or later.
 </Details>
diff --git a/src/content/partials/workers/redirect-example-js.mdx b/src/content/partials/workers/redirect-example-js.mdx
index 9b764fa66e236ce..b5b219d970896c9 100644
--- a/src/content/partials/workers/redirect-example-js.mdx
+++ b/src/content/partials/workers/redirect-example-js.mdx
@@ -1,13 +1,14 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const destinationURL = "https://example.com";
-		const statusCode = 301;
-		return Response.redirect(destinationURL, statusCode);
-	},
+  async fetch(request) {
+    const destinationURL = "https://example.com";
+    const statusCode = 301;
+    return Response.redirect(destinationURL, statusCode);
+  },
 };
 ```
diff --git a/src/content/partials/workers/remote-binding-note.mdx b/src/content/partials/workers/remote-binding-note.mdx
index 14a8b741425af69..f05321bd7cd36e3 100644
--- a/src/content/partials/workers/remote-binding-note.mdx
+++ b/src/content/partials/workers/remote-binding-note.mdx
@@ -6,4 +6,4 @@
 
 To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. Learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/workers/request-dot-clone-warning.mdx b/src/content/partials/workers/request-dot-clone-warning.mdx
index 5371525c77f704e..5e9640d3f34d8d2 100644
--- a/src/content/partials/workers/request-dot-clone-warning.mdx
+++ b/src/content/partials/workers/request-dot-clone-warning.mdx
@@ -9,4 +9,4 @@ The body of a [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request
 To avoid errors, create a clone of the Request object with `request.clone()` for each subsequent attempt to access a Request's body.
 Keep in mind that Workers have a [memory limit of 128 MB per Worker](/workers/platform/limits/#memory) and loading particularly large files into a Worker's memory multiple times may reach this limit. To ensure memory usage does not reach this limit, consider using [Streams](/workers/runtime-apis/streams/).
 
-:::
+:::
\ No newline at end of file
diff --git a/src/content/partials/workers/respond-another-site-example-js.mdx b/src/content/partials/workers/respond-another-site-example-js.mdx
index 1e55c7a658919ba..05c6f264b81aa7f 100644
--- a/src/content/partials/workers/respond-another-site-example-js.mdx
+++ b/src/content/partials/workers/respond-another-site-example-js.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		function MethodNotAllowed(request) {
-			return new Response(`Method ${request.method} not allowed.`, {
-				status: 405,
-				headers: {
-					Allow: "GET",
-				},
-			});
-		}
-		// Only GET requests work with this proxy.
-		if (request.method !== "GET") return MethodNotAllowed(request);
-		return fetch(`https://example.com`);
-	},
+  async fetch(request) {
+    function MethodNotAllowed(request) {
+      return new Response(`Method ${request.method} not allowed.`, {
+        status: 405,
+        headers: {
+          Allow: "GET",
+        },
+      });
+    }
+    // Only GET requests work with this proxy.
+    if (request.method !== "GET") return MethodNotAllowed(request);
+    return fetch(`https://example.com`);
+  },
 };
 ```
diff --git a/src/content/partials/workers/return-html-example-js.mdx b/src/content/partials/workers/return-html-example-js.mdx
index 41b5a8db682bcdc..24bed7993c20042 100644
--- a/src/content/partials/workers/return-html-example-js.mdx
+++ b/src/content/partials/workers/return-html-example-js.mdx
@@ -1,21 +1,22 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const html = `<!DOCTYPE html>
+  async fetch(request) {
+    const html = `<!DOCTYPE html>
 		<body>
 		  <h1>Hello World</h1>
 		  <p>This markup was generated by a Cloudflare Worker.</p>
 		</body>`;
 
-		return new Response(html, {
-			headers: {
-				"content-type": "text/html;charset=UTF-8",
-			},
-		});
-	},
+    return new Response(html, {
+      headers: {
+        "content-type": "text/html;charset=UTF-8",
+      },
+    });
+  },
 };
 ```
diff --git a/src/content/partials/workers/return-json-example-js.mdx b/src/content/partials/workers/return-json-example-js.mdx
index e81939c499570ad..5222c0a889a5073 100644
--- a/src/content/partials/workers/return-json-example-js.mdx
+++ b/src/content/partials/workers/return-json-example-js.mdx
@@ -1,15 +1,16 @@
 ---
 {}
+
 ---
 
 ```js playground
 export default {
-	async fetch(request) {
-		const data = {
-			hello: "world",
-		};
+  async fetch(request) {
+    const data = {
+      hello: "world",
+    };
 
-		return Response.json(data);
-	},
+    return Response.json(data);
+  },
 };
 ```
diff --git a/src/content/partials/workers/service-binding-rpc-example.mdx b/src/content/partials/workers/service-binding-rpc-example.mdx
index 0e2f10a6dad4f77..1f67ca0636f4dea 100644
--- a/src/content/partials/workers/service-binding-rpc-example.mdx
+++ b/src/content/partials/workers/service-binding-rpc-example.mdx
@@ -77,6 +77,7 @@ Worker A can declare a [binding](/workers/runtime-apis/bindings) to Worker B:
 
 Making it possible for Worker A to call the `add()` method from Worker B:
 
+
 <Tabs syncKey="workersExamples">
 
 <TypeScriptExample omitTabs={true}>
diff --git a/src/content/partials/workers/storage-products-table.mdx b/src/content/partials/workers/storage-products-table.mdx
index 47d0a3281d70912..9b832c39da70b20 100644
--- a/src/content/partials/workers/storage-products-table.mdx
+++ b/src/content/partials/workers/storage-products-table.mdx
@@ -2,14 +2,14 @@
 {}
 ---
 
-| Use-case                                  | Product                                          | Ideal for                                                                                                                                              |
-| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Key-value storage                         | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                                                            |
-| Object storage / blob storage             | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.                                        |
-| Accelerate a Postgres or MySQL database   | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                               |
-| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage. |
-| Lightweight SQL database                  | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                                                           |
-| Task processing, batching and messaging   | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks.                                                          |
-| Vector search & embeddings queries        | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.                           |
-| Streaming ingestion                       | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying                         |
-| Time-series metrics                       | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL.                                |
+| Use-case | Product                                          | Ideal for                                                                                                               |
+| ------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
+| Key-value storage | [Workers KV](/kv/)                               | Configuration data, service routing metadata, personalization (A/B testing)                                             |
+| Object storage / blob storage | [R2](/r2/)                                       | User-facing web assets, images, machine learning and training datasets, analytics datasets, log and event data.         |
+| Accelerate a Postgres or MySQL database | [Hyperdrive](/hyperdrive/)                       | Connecting to an existing database in a cloud or on-premise using your existing database drivers & ORMs.                                                            |
+| Global coordination & stateful serverless | [Durable Objects](/durable-objects/)             | Building collaborative applications; global coordination across clients; real-time WebSocket applications; strongly consistent, transactional storage.  |
+| Lightweight SQL database | [D1](/d1/)                                       | Relational data, including user profiles, product listings and orders, and/or customer data.                            |
+| Task processing, batching and messaging | [Queues](/queues/)                               | Background job processing (emails, notifications, APIs), message queuing, and deferred tasks. |
+| Vector search & embeddings queries | [Vectorize](/vectorize/)                         | Storing [embeddings](/workers-ai/models/?tasks=Text+Embeddings) from AI models for semantic search and classification tasks.  |
+| Streaming ingestion | [Pipelines](/pipelines/)                         | Streaming data ingestion and processing, including clickstream analytics, telemetry/log data, and structured data for querying |
+| Time-series metrics | [Analytics Engine](/analytics/analytics-engine/) | Write and query high-cardinality time-series data, usage metrics, and service-level telemetry using Workers and/or SQL. |
\ No newline at end of file
diff --git a/src/content/partials/workers/testing-pages-functions.mdx b/src/content/partials/workers/testing-pages-functions.mdx
index 2d921130e88652f..568cbc85bd23a01 100644
--- a/src/content/partials/workers/testing-pages-functions.mdx
+++ b/src/content/partials/workers/testing-pages-functions.mdx
@@ -1,9 +1,12 @@
 ---
 {}
+
 ---
 
 :::note[Pages Functions]
 
+
 The content described on this page is also applicable to [Pages Functions](/pages/functions/). Pages Functions are Cloudflare Workers and can be thought of synonymously with Workers in this context.
 
+
 :::
diff --git a/src/content/partials/workers/tutorials-before-you-start.mdx b/src/content/partials/workers/tutorials-before-you-start.mdx
index bb2f002bb183c96..b33c0af2815ddef 100644
--- a/src/content/partials/workers/tutorials-before-you-start.mdx
+++ b/src/content/partials/workers/tutorials-before-you-start.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 ## Before you start
diff --git a/src/content/partials/workers/workers_logs_pricing.mdx b/src/content/partials/workers/workers_logs_pricing.mdx
index 7e8c152265137aa..8772eec1debdf90 100644
--- a/src/content/partials/workers/workers_logs_pricing.mdx
+++ b/src/content/partials/workers/workers_logs_pricing.mdx
@@ -1,12 +1,13 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 Workers Logs is included in both the Free and Paid [Workers plans](/workers/platform/pricing/).
 
-|                  | Log Events Written                                                 | Retention |
-| ---------------- | ------------------------------------------------------------------ | --------- |
-| **Workers Free** | 200,000 per day                                                    | 3 Days    |
-| **Workers Paid** | 20 million included per month <br /> +$0.60 per additional million | 7 Days    |
+|                    | Log Events Written                                                 | Retention  |
+| ------------------ | ------------------------------------------------------------------ | ---------- |
+| **Workers Free**   | 200,000 per day                                                    | 3 Days     |
+| **Workers Paid**   | 20 million included per month <br /> +$0.60 per additional million | 7 Days     |
diff --git a/src/content/partials/workers/wrangler-commands/containers.mdx b/src/content/partials/workers/wrangler-commands/containers.mdx
index aa5f7677a4557ba..e04e280d72c1783 100644
--- a/src/content/partials/workers/wrangler-commands/containers.mdx
+++ b/src/content/partials/workers/wrangler-commands/containers.mdx
@@ -202,14 +202,14 @@ wrangler containers instances 12345678-abcd-1234-abcd-123456789abc --json
 
 ```json output
 [
-	{
-		"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
-		"name": "worker-12",
-		"state": "running",
-		"location": "sfo06",
-		"version": 3,
-		"created": "2025-06-01T12:00:00Z"
-	}
+  {
+    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+    "name": "worker-12",
+    "state": "running",
+    "location": "sfo06",
+    "version": 3,
+    "created": "2025-06-01T12:00:00Z"
+  }
 ]
 ```
 
diff --git a/src/content/partials/workers/wrangler-commands/r2-sql.mdx b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
index 5c20b7b51c03454..17cd10b4c69f8c1 100644
--- a/src/content/partials/workers/wrangler-commands/r2-sql.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2-sql.mdx
@@ -2,14 +2,7 @@
 {}
 ---
 
-import {
-	Render,
-	AnchorHeading,
-	Type,
-	MetaInfo,
-	WranglerCommand,
-	WranglerNamespace,
-} from "~/components";
+import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand, WranglerNamespace } from "~/components";
 
 :::note
 
@@ -17,4 +10,4 @@ R2 SQL is currently in open beta. Report R2 SQL bugs in [GitHub](https://github.
 
 :::
 
-<WranglerCommand command="r2 sql query" headingLevel={3} />
+<WranglerCommand command="r2 sql query" headingLevel={3} />
\ No newline at end of file
diff --git a/src/content/partials/workers/wrangler-commands/r2.mdx b/src/content/partials/workers/wrangler-commands/r2.mdx
index 692fb87d223e3e1..3046ac2f72125bb 100644
--- a/src/content/partials/workers/wrangler-commands/r2.mdx
+++ b/src/content/partials/workers/wrangler-commands/r2.mdx
@@ -2,13 +2,7 @@
 {}
 ---
 
-import {
-	Render,
-	AnchorHeading,
-	Type,
-	MetaInfo,
-	WranglerCommand,
-} from "~/components";
+import { Render, AnchorHeading, Type, MetaInfo, WranglerCommand } from "~/components";
 
 ## `r2 bucket`
 
@@ -19,24 +13,21 @@ Interact with buckets in an R2 store.
 The `r2 bucket` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 bucket create" headingLevel={3} />
+<WranglerCommand command="r2 bucket create" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket info" headingLevel={3} />
+<WranglerCommand command="r2 bucket info" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket list" headingLevel={3} />
+<WranglerCommand command="r2 bucket list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket catalog get" headingLevel={3} />
+<WranglerCommand command="r2 bucket catalog get" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog compaction enable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog compaction enable" headingLevel={3}/>
 
 Examples:
 
@@ -48,10 +39,7 @@ npx wrangler r2 bucket catalog compaction enable my-bucket --token <TOKEN>
 npx wrangler r2 bucket catalog compaction enable my-bucket my-namespace my-table --target-size 256
 ```
 
-<WranglerCommand
-	command="r2 bucket catalog compaction disable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog compaction disable" headingLevel={3}/>
 
 Examples:
 
@@ -62,66 +50,60 @@ npx wrangler r2 bucket catalog compaction disable my-bucket
 # Disable table-level compaction
 npx wrangler r2 bucket catalog compaction disable my-bucket my-namespace my-table
 ```
+<WranglerCommand command="r2 bucket catalog snapshot-expiration enable" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog snapshot-expiration enable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket catalog snapshot-expiration disable" headingLevel={3}/>
 
-<WranglerCommand
-	command="r2 bucket catalog snapshot-expiration disable"
-	headingLevel={3}
-/>
+<WranglerCommand command="r2 bucket cors set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors set" headingLevel={3} />
+<WranglerCommand command="r2 bucket cors delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket cors list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket cors list" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket dev-url get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket dev-url get" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain add" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain update" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain update" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain get" headingLevel={3} />
+<WranglerCommand command="r2 bucket domain list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket domain list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle add" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lifecycle set" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock add" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock add" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock remove" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock remove" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock list" headingLevel={3} />
+<WranglerCommand command="r2 bucket lock set" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket lock set" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification create" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification create" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification delete" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification delete" headingLevel={3} />
+<WranglerCommand command="r2 bucket notification list" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket notification list" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy enable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy enable" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy disable" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy disable" headingLevel={3} />
+<WranglerCommand command="r2 bucket sippy get" headingLevel={3}/>
 
-<WranglerCommand command="r2 bucket sippy get" headingLevel={3} />
 
 ## `r2 object`
 
@@ -132,8 +114,8 @@ Interact with R2 objects.
 The `r2 object` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
 :::
 
-<WranglerCommand command="r2 object get" headingLevel={3} />
+<WranglerCommand command="r2 object get" headingLevel={3}/>
 
-<WranglerCommand command="r2 object put" headingLevel={3} />
+<WranglerCommand command="r2 object put" headingLevel={3}/>
 
-<WranglerCommand command="r2 object delete" headingLevel={3} />
+<WranglerCommand command="r2 object delete" headingLevel={3}/>
\ No newline at end of file
diff --git a/src/content/partials/workflows/workflows-type-parameters.mdx b/src/content/partials/workflows/workflows-type-parameters.mdx
index 37e0134270468b8..0ad91e5f88a4fcf 100644
--- a/src/content/partials/workflows/workflows-type-parameters.mdx
+++ b/src/content/partials/workflows/workflows-type-parameters.mdx
@@ -1,8 +1,9 @@
 ---
 {}
+
 ---
 
-import { Markdown } from "~/components";
+import { Markdown } from "~/components"
 
 :::caution
 
diff --git a/src/content/partials/zaraz/zaraz-definition.mdx b/src/content/partials/zaraz/zaraz-definition.mdx
index 2b5e8f884cd31f7..b17ee4fa2792f6f 100644
--- a/src/content/partials/zaraz/zaraz-definition.mdx
+++ b/src/content/partials/zaraz/zaraz-definition.mdx
@@ -1,5 +1,6 @@
 ---
 {}
+
 ---
 
 Cloudflare Zaraz gives you complete control over third-party tools and services for your website, and allows you to offload them to Cloudflare's edge, improving the speed and security of your website. With Cloudflare Zaraz you can load tools such as analytics tools, advertising pixels and scripts, chatbots, marketing automation tools, and more, in the most optimized way.
diff --git a/src/pages/agent-setup/index.astro b/src/pages/agent-setup/index.astro
index e5e4a7adc39235c..9c6aa0f8bc91720 100644
--- a/src/pages/agent-setup/index.astro
+++ b/src/pages/agent-setup/index.astro
@@ -24,59 +24,29 @@ const props = {
 
 <StarlightPage {...props}>
 	<p class="agent-setup-lede">
-		Install an agent of your choice, connect Cloudflare <a
-			href="https://github.com/cloudflare/skills"
-			target="_blank"
-			rel="noopener noreferrer">Skills &nearr;</a
-		> and <a
-			href="https://blog.cloudflare.com/code-mode-mcp/"
-			target="_blank"
-			rel="noopener noreferrer">Code Mode API &nearr;</a
-		> and <a
-			href="https://github.com/cloudflare/mcp-server-cloudflare"
-			target="_blank"
-			rel="noopener noreferrer">domain-specific &nearr;</a
-		> MCP servers, and start deploying to Cloudflare from your editor or terminal.
+		Install an agent of your choice, connect Cloudflare <a href="https://github.com/cloudflare/skills" target="_blank" rel="noopener noreferrer">Skills &nearr;</a> and <a href="https://blog.cloudflare.com/code-mode-mcp/" target="_blank" rel="noopener noreferrer">Code Mode API &nearr;</a> and <a href="https://github.com/cloudflare/mcp-server-cloudflare" target="_blank" rel="noopener noreferrer">domain-specific &nearr;</a> MCP servers, and start deploying to Cloudflare from your editor or terminal.
 	</p>
 
 	<div class="agent-setup-paths not-content">
 		<!-- Left: quick path -->
-		<div
-			class="agent-setup-path agent-setup-path--quick"
-			style="flex-basis: 60%;"
-		>
+		<div class="agent-setup-path agent-setup-path--quick" style="flex-basis: 60%;">
 			<p class="agent-setup-path-eyebrow">Quick setup</p>
 			<p class="agent-setup-path-title">Already have an agent?</p>
-			<p class="agent-setup-path-desc">
-				Paste this into any AI coding agent to install Cloudflare agent tooling
-				in one step.
-			</p>
-			<PromptCopyBlock
-				text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md"
-				hideLabel
-			/>
+			<p class="agent-setup-path-desc">Paste this into any AI coding agent to install Cloudflare agent tooling in one step.</p>
+			<PromptCopyBlock text="Fetch https://developers.cloudflare.com/agent-setup/prompt.md" hideLabel />
 		</div>
 		<!-- Right: manual path -->
 		<div class="agent-setup-path agent-setup-path--manual">
 			<p class="agent-setup-path-eyebrow">Manual setup</p>
 			<p class="agent-setup-path-title">New to AI agents?</p>
-			<p class="agent-setup-path-desc">
-				Pick an agent, follow step-by-step setup instructions, compare
-				capabilities, and learn about the Cloudflare tools available to you.
-			</p>
-			<a href="#pick-your-agent" class="agent-setup-path-cta"
-				>Browse agents &darr;</a
-			>
+			<p class="agent-setup-path-desc">Pick an agent, follow step-by-step setup instructions, compare capabilities, and learn about the Cloudflare tools available to you.</p>
+			<a href="#pick-your-agent" class="agent-setup-path-cta">Browse agents &darr;</a>
 		</div>
 	</div>
 
 	<hr />
 
-	<div
-		class="agent-setup-section-header"
-		style="margin-top: 3.25rem;"
-		id="pick-your-agent"
-	>
+	<div class="agent-setup-section-header" style="margin-top: 3.25rem;" id="pick-your-agent">
 		<h2>Pick your agent</h2>
 		<p>Select an agent to get step-by-step setup instructions.</p>
 	</div>
@@ -138,6 +108,10 @@ const props = {
 		border-color: var(--color-cl1-gray-2);
 	}
 
+
+
+
+
 	.agent-setup-path-eyebrow {
 		font-size: 0.75rem;
 		font-weight: 700;
@@ -178,4 +152,5 @@ const props = {
 		text-decoration: underline;
 		text-underline-offset: 2px;
 	}
+
 </style>
diff --git a/src/pages/plans.astro b/src/pages/plans.astro
index e46fb3945ae4d16..38f964ff6dac9d9 100644
--- a/src/pages/plans.astro
+++ b/src/pages/plans.astro
@@ -120,8 +120,8 @@ import { ProductFeatures } from "~/components";
 			<strong>Developer products</strong>: Refer to the <a
 				href="https://www.cloudflare.com/plans/developer-platform/"
 				>Developer Platform pricing page</a
-			> or individual <a href="/directory/">product docs</a> to learn more about plans
-			and pricing.
+			> or individual <a href="/directory/">product docs</a> to learn more about
+			plans and pricing.
 		</li>
 		<li>
 			<strong>Zero Trust products</strong>: Refer to the <a